[pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.034 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.081 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById ==> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.112 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.115 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.115 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.134 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.159 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.159 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 13:23:39.185 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:43.499 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:43.500 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:43.520 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.275 DEBUG 4952 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.276 DEBUG 4952 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.294 DEBUG 4952 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.294 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.295 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.579 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.583 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Preparing: select DISTINCT a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join asso_product_patent i on i.patent_no=a.patentno WHERE i.product_id =? order by a.patentno LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.583 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Parameters: 43(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.868 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.904 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.904 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.923 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.927 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.927 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.945 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.959 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:48.959 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.114 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.115 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.116 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.134 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.143 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.143 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.161 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.169 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.169 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.186 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.198 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.198 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.219 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.221 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.221 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.240 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.247 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.248 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.266 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.274 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.275 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.292 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.294 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.294 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.312 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.314 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.314 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.332 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.339 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.339 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.358 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.379 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Preparing: SELECT id,datetime,status,simplestatus,content,remark,pid AS patentId FROM os_patent_affair WHERE (pid = ?) ORDER BY datetime DESC [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.380 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.486 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentAffairMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.488 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.488 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_STATUS(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.508 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 56 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.520 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.521 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.541 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.551 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.551 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:49.569 DEBUG 4952 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:59.921 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 13:25:59.921 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.208 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.209 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Preparing: select DISTINCT a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join asso_product_patent i on i.patent_no=a.patentno WHERE i.product_id =? order by a.patentno LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.209 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Parameters: 43(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.495 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.497 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.497 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.515 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.516 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.516 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.534 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.535 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.535 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.690 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.691 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.691 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.709 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.710 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.711 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.729 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.730 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.731 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.748 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.749 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.750 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.771 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.772 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.772 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.789 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.790 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.791 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.809 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.809 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.809 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.828 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.829 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.829 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.847 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.848 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.848 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.865 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.866 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.866 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.885 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.886 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Preparing: SELECT id,datetime,status,simplestatus,content,remark,pid AS patentId FROM os_patent_affair WHERE (pid = ?) ORDER BY datetime DESC [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.887 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.993 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAffairMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.994 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:00.995 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_STATUS(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.014 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 56 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.015 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.015 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.034 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.035 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.035 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:01.053 DEBUG 4952 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:06.532 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ? AND a.`name` LIKE concat("%", ?, "%")) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:06.533 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer), 一(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:06.815 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:06.816 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Preparing: select DISTINCT a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join asso_product_patent i on i.patent_no=a.patentno WHERE i.product_id =? and a.`name` like concat("%", ?, "%") order by a.patentno LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:06.816 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Parameters: 43(Integer), 一(String), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.101 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.102 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.103 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.120 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.121 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.121 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.139 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.141 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.141 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.297 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.298 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.298 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.316 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.317 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.318 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.335 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.336 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.336 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.354 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.355 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.355 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.376 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.377 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.377 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.394 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.395 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.396 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.413 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.414 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.415 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.432 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.433 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.433 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.451 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.452 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.452 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.470 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.471 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.471 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.489 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.490 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Preparing: SELECT id,datetime,status,simplestatus,content,remark,pid AS patentId FROM os_patent_affair WHERE (pid = ?) ORDER BY datetime DESC [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.490 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.596 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentAffairMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.597 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.597 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_STATUS(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.617 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 56 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.618 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.619 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.637 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.638 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.639 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:07.656 DEBUG 4952 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:10.051 DEBUG 4952 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:10.052 DEBUG 4952 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 13:26:10.070 DEBUG 4952 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:16.979 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ? AND a.`name` LIKE concat("%", ?, "%")) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:16.980 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer), 一(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.264 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.265 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Preparing: select DISTINCT a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join asso_product_patent i on i.patent_no=a.patentno WHERE i.product_id =? and a.`name` like concat("%", ?, "%") order by a.patentno LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.266 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Parameters: 43(Integer), 一(String), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.548 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.549 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.550 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.566 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.567 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.567 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.583 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.584 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.585 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.736 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.737 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.737 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.754 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.755 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.755 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.771 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.772 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.772 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.788 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.789 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.790 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.809 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.809 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.810 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.827 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.827 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.828 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.844 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.845 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.845 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.861 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.862 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.862 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.878 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.881 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.882 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.898 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.899 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.899 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.915 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.916 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Preparing: SELECT id,datetime,status,simplestatus,content,remark,pid AS patentId FROM os_patent_affair WHERE (pid = ?) ORDER BY datetime DESC [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:17.916 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.021 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentAffairMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.022 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.022 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_STATUS(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.039 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 56 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.040 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.041 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 18785(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.057 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.058 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.058 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:18.074 DEBUG 4952 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:29.965 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoStructurePatentMapper.selectObjs ==> Preparing: SELECT patent_no FROM asso_structure_patent WHERE (project_id = ? AND patent_no IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:29.965 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoStructurePatentMapper.selectObjs ==> Parameters: 43(Integer), CN111243486A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:29.982 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoStructurePatentMapper.selectObjs <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:29.983 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.delete ==> Preparing: DELETE FROM asso_product_patent WHERE (product_id = ? AND patent_no IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:29.984 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.delete ==> Parameters: 43(Integer), CN111243486A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.015 DEBUG 4952 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.405 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ? AND a.`name` LIKE concat("%", ?, "%")) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.405 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer), 一(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.422 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.423 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.423 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 13:34:30.439 DEBUG 4952 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.284 DEBUG 23536 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.303 DEBUG 23536 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.325 DEBUG 23536 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.480 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.481 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.484 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.485 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 37(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.487 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.488 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.488 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 37(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.489 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.490 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.490 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.491 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.492 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.493 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.494 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.494 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.495 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 38(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.496 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.497 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.497 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 38(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.498 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.500 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.501 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 39(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.502 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.503 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.503 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 39(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.504 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.505 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.505 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.507 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.508 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.509 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.510 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.511 DEBUG 23536 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.858 DEBUG 23536 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.859 DEBUG 23536 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: QUERY_GROUP(String), ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.867 DEBUG 23536 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 50 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.995 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_thematic a WHERE (a.id IN (SELECT tid FROM os_distribution_doing WHERE uid = ?) OR a.creat_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.995 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Parameters: 1(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:32.997 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.001 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id,a.product_id,a.structure_id,a.is_category, u.`name` as create_name, (select count(*) from os_thematic_file where zid = a.id and type = 1) as report_num from os_thematic a left join os_distribution u on u.id = a.creat_id WHERE (a.id in (select tid from os_distribution_doing where uid=? ) or a.creat_id = ? ) order by a.`create_time` desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.002 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Parameters: 1(Integer), 1(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.005 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.051 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.052 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.055 DEBUG 23536 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.122 DEBUG 23536 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.122 DEBUG 23536 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.123 DEBUG 23536 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.186 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a WHERE a.id in (select tid from os_distribution_doing where uid=? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.187 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.188 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.210 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.211 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.215 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.217 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.218 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:33.220 DEBUG 23536 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.202 DEBUG 23536 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.202 DEBUG 23536 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.204 DEBUG 23536 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.220 DEBUG 23536 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.221 DEBUG 23536 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.223 DEBUG 23536 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.230 DEBUG 23536 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.230 DEBUG 23536 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.231 DEBUG 23536 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.232 DEBUG 23536 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.233 DEBUG 23536 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.234 DEBUG 23536 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.235 DEBUG 23536 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.236 DEBUG 23536 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 249(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:10:39.238 DEBUG 23536 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:07.744 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:07.745 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Parameters: 249(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:07.746 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:07.755 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Preparing: SELECT id,uid AS userId,tenantId,tid AS projectId,addtime AS createTime,remark,type FROM os_distribution_doing WHERE (tid = ? AND uid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:07.755 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Parameters: 249(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:07.757 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectUserMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:08.266 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.insert ==> Preparing: INSERT INTO os_task ( type, uid, ctime, tid, mfields, mun, status, filename, filesize, downexcel, old_name ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:08.267 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.insert ==> Parameters: 1(Integer), 1(Integer), 1681974668(Integer), 249(Integer), 0(Integer), 99(Integer), 0(Integer), d56bdfdc923c4bb9b5d178b900fe2b2a.XLSX(String), 6093542(Long), \20230420\d56bdfdc923c4bb9b5d178b900fe2b2a.XLSX(String), 手机-美国.XLSX(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:08.275 DEBUG 23536 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:08.603 DEBUG 23536 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:08.604 DEBUG 23536 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:08.606 DEBUG 23536 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.724 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.725 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.727 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.735 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.736 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal system, mobile terminal, external device, and input/output method of mobile terminal(String), 移动终端系统、移动终端、外部设备以及移动终端的输入/输出方法(String), US20100093394A1(String), A mobile terminal system including a mobile terminal and an external device is provided. The mobile terminal includes a first external device interface to output screen information to the external device and to receive operation information from the external device. The external device includes a display section to display and output the screen information, a user input section used when a user inputs the operation information on the mobile terminal, and a second external device interface to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 提供了一种移动终端系统,包括移动终端和外部设备。 移动终端包括第一外部设备接口以将屏幕信息输出到外部设备并从外部设备接收操作信息。 外部设备包括用于显示和输出屏幕信息的显示部分、当用户在移动终端上输入操作信息时使用的用户输入部分、以及用于从移动终端接收屏幕信息并输出的第二外部设备接口。 向移动终端发送通过用户输入部分输入的操作信息。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), US12/578279(String), 1255363200(Integer), US20100093394A1(String), 1271260800(Integer), 美国(String), 2(Integer), JP(String), 3(Integer), 15(Integer), US20010052798A1 | US20030034898A1 | US20040051499A1 | US20060077046A1 | US20060082818A1 | US20060220878A1 | US20070030881A1 | US20080179963A1 | US20080239408A1 | US20090086105A1 | US20110136541A1 | US5847447A | US6781635B1 | US7976394B2 | US8004615B2(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.747 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.754 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.755 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.756 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.768 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.769 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ce892a194a454e17912c61bd11227081.png(String), 184950(Integer), ce892a194a454e17912c61bd11227081.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.778 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.780 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.780 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.782 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.789 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.789 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal system, mobile terminal, external device, and input/output method of mobile terminal(String), 移动终端系统、移动终端、外部设备以及移动终端的输入/输出方法(String), US20100093394A1(String), A mobile terminal system including a mobile terminal and an external device is provided. The mobile terminal includes a first external device interface to output screen information to the external device and to receive operation information from the external device. The external device includes a display section to display and output the screen information, a user input section used when a user inputs the operation information on the mobile terminal, and a second external device interface to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 提供了一种移动终端系统,包括移动终端和外部设备。 移动终端包括第一外部设备接口以将屏幕信息输出到外部设备并从外部设备接收操作信息。 外部设备包括用于显示和输出屏幕信息的显示部分、当用户在移动终端上输入操作信息时使用的用户输入部分、以及用于从移动终端接收屏幕信息并输出的第二外部设备接口。 向移动终端发送通过用户输入部分输入的操作信息。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), US12/578279(String), 1255363200(Integer), US20100093394A1(String), 1271260800(Integer), 美国(String), 2(Integer), 2(Integer), JP(String), 3(Integer), 15(Integer), US20010052798A1 | US20030034898A1 | US20040051499A1 | US20060077046A1 | US20060082818A1 | US20060220878A1 | US20070030881A1 | US20080179963A1 | US20080239408A1 | US20090086105A1 | US20110136541A1 | US5847447A | US6781635B1 | US7976394B2 | US8004615B2(String), \20230420\ce892a194a454e17912c61bd11227081.png(String), 15(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.797 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.804 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.805 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.806 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.811 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.812 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 1. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 1.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.813 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 2. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 2.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 0(Integer), 1(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.814 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 3. The mobile terminal system according to claim 2,wherein the coil provided in the first external device interface is a coil for power reception,the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coils.(String), 3.根据权利要求2所述的移动终端系统,其中第一外部设备接口中设置的线圈为受电线圈,第二外部设备接口中设置的线圈为电力传输线圈,以及利用线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.814 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 4. The mobile terminal system according to claim 1 or 2,wherein the mobile terminal is a mobile phone, andthe screen information is video data or still image data received through a mobile phone network.(String), 4.根据权利要求1或2所述的移动终端系统,其中移动终端为手机,屏幕信息是通过手机网络接收到的视频数据或静止图像数据。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.815 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 5. The mobile terminal system according to claim 1 or 3,wherein the first and second external device interfaces perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and also reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 5.根据权利要求1或3所述的移动终端系统,其中第一和第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.816 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 6. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 6.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.816 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 7. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 7.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.816 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 8. The mobile terminal according to claim 7,wherein the coil provided in the first external device interface is a coil for power reception, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the first external device interface and a coil for power transmission provided in the second external device interface.(String), 8.根据权利要求7所述的移动终端,其中第一外部设备接口中设置的线圈为受电线圈,利用第一外部设备接口中设置的线圈与第二外部设备接口中设置的电力传输线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.817 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 9. The mobile terminal according to claim 6 or 8,wherein the first external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 9.根据权利要求6或8所述的移动终端,其中第一外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.817 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 10. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda display section which outputs the screen information received from the mobile terminal.(String), 10.一种在如权利要求1所述的移动终端系统中运行的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.817 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 11. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; anda display section which outputs the screen information received from the mobile terminal.(String), 11.一种运行在如权利要求1所述的移动终端系统中的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.818 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 12. The external device according to claim 11,wherein the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the second external device interface and a coil for power reception provided in the first external device interface.(String), 12.根据权利要求11所述的外部设备,其中第二外部设备接口中设置的线圈为电力传输线圈,以及利用设置在第二外部设备接口中的线圈与设置在第一外部设备接口中的用于受电的线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.818 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 13. The external device according to claim 10 or 12,wherein the second external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 13.根据权利要求10或12所述的外部设备,其中第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.818 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 14. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 14.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.818 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 15. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 15.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 1(Integer), 14(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.944 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.945 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.946 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.947 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.950 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184950(Integer), BACKGROUND OF THE INVENTION [0001]1. Field of the Invention [0002]The present invention relates to a mobile terminal system including a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal, a mobile terminal, an external device, and an input/output method of the mobile terminal. In particular, the present invention relates to a mobile terminal system which outputs image data and sound data received in a mobile terminal to the outside through an external device and which allows the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0003]2. Description of the Related Art [0004]Mobile phones have succeeded the carphones pioneered as a mobile communications system, and have rapidly spread since the 1990s as the terminals become small, light, and inexpensive and the service charges become low. Moreover, with the spread of computers and the development of broadband network techniques including the Internet, E-mail and web search/access can be performed on mobile phones and various applications, such as music or video reproduction and games, can be executed. [0005]However, although the range of application of mobile phones is diversified, there are many restrictions in input and output since a portable size is necessary for mobile phones. For example, the screen size is diagonally about 5 to 10 cm. In this case, high-resolution display causes problems in visibility, for example, characters with the same font size become very small, even though the resolution is increasing due to the development of flat panel manufacturing technology in recent years. [0006]Furthermore, an input section provided in the mobile phone generally has only a numeric keypad of 0 to 9, keys by which up and down and left and right input operations are possible, and some other keys. Compared with a keyboard of a personal computer provided with 60 to 100 keys, the number of keys of the mobile phone is small and the input operation is also difficult. [0007]In recent years, the mobile phone with tens of keys similar to the QWERTY type keyboard has also appeared. However, each of the keys is small due to the portability restriction on the device size. For this reason, the input operation is still difficult. [0008]In order to cope with such a problem, a method of connecting a mobile phone to an external device with a relatively large screen or an input device which is easy to perform an input operation may be considered. [0009]For example, a display processing system using a mobile terminal is proposed. In the display processing system, an image displayed on a liquid crystal screen of a mobile phone can be displayed on a television screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2001-352373). [0010]In addition, a screen display device which has an entry for connecting a mobile phone is proposed. The screen display device displays image data received in the mobile phone on a large screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2002-116843). [0011]In addition, a mobile phone with a separate monitor is proposed. The mobile phone displays data displayed on a monitor built in the mobile phone or downloaded display data on the separate monitor (for example, refer to Japanese Unexamined Patent Application Publication No. 2003-78597). [0012]However, in order to transmit or receive data by connecting a mobile phone to an external device, a plurality of signal transmission lines for input/output of a video signal, input/output of a sound signal, input/output of a user operation signal, and the like is necessary (refer to FIG. 10). That is, for the connection between the mobile phone and the external device, a plurality of cables is used for video, sound, and user operation or a plug cable having a terminal with many poles is used. In the former case where a plurality of cables is used, the connection and disconnection operations of the cables are troublesome for the user. Moreover, in the latter method of using the plug cable, there is a problem that it becomes difficult to secure the place for disposing the plug in the main body of the small mobile phone as the number of poles increases. In addition, problems also occur such as the device becoming expensive due to the cost of components, such as connectors, and difficulty in obtaining a contact point between the connectors with sufficient strength. [0013]In addition, when the classification of input or output signal changes with the model of the mobile phone, the number of poles of the plug also changes. In this case, the connectors for the external device are not compatible among different models, which is inconvenient. SUMMARY OF THE INVENTION [0014]In view of the above, it is desirable to provide a mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0015]In addition, it is desirable to provide a mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0016]According to a first embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0017]The “system” referred to herein means a logical group of a plurality of devices (or functional modules for realizing specific functions), and it does not matter whether the devices or the functional modules exist in a single housing. [0018]According to a second embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0019]Here, according to a third embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the power supply, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0020]In addition, according to a fourth embodiment of the present invention, the mobile terminal may be a mobile phone, and the screen information may be video data or still image data received through a mobile phone network. [0021]In addition, according to a fifth embodiment of the present invention, the first and second external device interfaces may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0022]In addition, according to a sixth embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0023]In addition, according to a seventh embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0024]Here, according to an eighth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0025]In addition, according to a ninth embodiment of the present invention, the first external device interface of the mobile terminal may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0026]In addition, according to a tenth embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a display section which outputs the screen information received from the mobile terminal. [0027]In addition, according to an eleventh embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; and a display section which outputs the screen information received from the mobile terminal. [0028]Here, according to a twelfth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0029]In addition, according to a thirteenth embodiment of the present invention, the second external device interface of the external device may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0030]In addition, according to a fourteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0031]In addition, according to a fifteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0032]According to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0033]Moreover, according to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0034]According to the first to third, sixth to eighth, tenth to twelfth, fourteenth, and fifteenth embodiments of the present invention, the received data can be displayed on the large screen and the mobile terminal can be operated by the input from an easy-to-use keyboard simply by placing the mobile terminal, in which the size of the display device or input device is not sufficient, on the external device. [0035]In addition, according to the fourth embodiment of the present invention, video data or still image data downloaded from the Internet to the mobile phone can be displayed using the large screen of the external device. [0036]In addition, according to the fifth, ninth, and thirteenth embodiments of the present invention, transmission using a small number of contact points is performed between the mobile phone and the external device. This is advantageous in that the connection interface is simplified, the component cost for the connection section is reduced, the device is small-sized, and deterioration of the contact point is prevented. These effects can be further improved by applying wireless connection, such as electric field transmission, to the connection interface. [0037]Moreover, according to the embodiments of the present invention, since it is sufficient to provide a simple connection interface with an external device, restrictions in the design can be reduced. [0038]Additional purposes, characteristics, and advantages of the present invention will be apparent from the detailed description made in the following embodiment of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS [0039]FIG. 1 is a diagram schematically illustrating the configuration of a mobile terminal system according to an embodiment of the present invention; [0040]FIG. 2 is a diagram illustrating an example of the configuration of transmitting the parallel data serially; [0041]FIG. 3 is a characteristic curve illustrating the frequency spectrum of a signal on a power line; [0042]FIG. 4A is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0043]FIG. 4B is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0044]FIG. 5 is a diagram illustrating a write sequence example of a bus in a mobile phone and a bus in an external device when performing a write operation from the mobile phone to an LCD of the external device; [0045]FIG. 6 is a diagram illustrating a read sequence example of a bus in the mobile phone and a bus in the external device when performing an operation of reading the input information on a keyboard of the external device from the mobile phone; [0046]FIG. 7 is a diagram illustrating an interrupt sequence example of the bus in the mobile phone and the bus in the external device when an interrupt occurs on the keyboard of the external device; [0047]FIG. 8 is a diagram illustrating a format example of a transmission frame between the mobile phone and the external device; [0048]FIG. 9 is an illustration of an application image of the mobile terminal system shown in FIG. 1; and [0049]FIG. 10 is a diagram illustrating an example of the configuration of a past mobile terminal system. DESCRIPTION OF THE PREFERRED EMBODIMENTS [0050]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. [0051]FIG. 1 is a schematic diagram illustrating the configuration of a mobile terminal system according to an embodiment of the present invention. The system shown in FIG. 1 includes a mobile phone, which receives image data and sound data, and an external device, which outputs the image data and the sound data to the outside or which is used when a user operates the mobile phone. [0052]A mobile phone 100 includes a processor 101, various input/output devices 104 to 106, and an external device interface 107 for interfacing with an external device 120. Moreover, although the mobile phone 100 includes circuit modules for radio communications and the like, they are not shown because they are not directly related with the gist of the present invention. [0053]The processor 101 is connected to the various input/output devices 104 to 106 by a bus signal line group 110, a chip select signal 111, and an interrupt signal 112. [0054]The bus signal line group 110 includes signal lines, such as address, data, and enable. In addition to the various input/output devices 104 to 106, the bus signal line group 110 is also connected to the external device interface 107. [0055]The chip select signal 111 is a signal which is used when the processor 101 selects a circuit chip of one of the various input/output devices 104 to 106 through a bus interface 102. In addition, the interrupt signal 112 is a signal, which is used when the various input/output devices 104 to 106 notify the processor 101 of the occurrence of an event, and is input to an interrupt controller 103. The chip select signal 111 and the interrupt signal 112 are prepared in a quantity equal to the number of input/output devices and are also connected to the external device interface 107. [0056]First, an operation on the side of the mobile phone 100 will be described. [0057]When outputting data to the screen of an LCD 104, the processor 101 outputs image data to the LCD 104 using the bus interface 102. When outputting the data to the LCD 104, the bus interface 102 enables the chip select signal 111 connected to the LCD 104 so that the LCD 104 receives the image data from the processor 101 and displays the data on the screen. For example, video data or still image data downloaded through the mobile phone network from a web site on the Internet can be displayed on the screen of the LCD 104. [0058]In addition, also when outputting data to a speaker 105 or other output devices (not shown), the processor 101 similarly enables only the chip select signal 111 connected to the corresponding output device so that the output device receives the data from the processor 101 and reproduces and outputs the data. For example, sound data, such as music, downloaded through the mobile phone network from a web site on the Internet can be reproduced in the speaker 105. [0059]On the other hand, when there is a user input operation on a keyboard 106, the keyboard 106 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. The processor 101 which has received the interrupt receives the data, which has been input on the keyboard 106, through the bus 110. In this case, the bus interface 102 enables the chip select signal 111 connected to the keyboard 106 so that the keyboard 106 can output the data to the bus 110 and the processor 101 can receive the data. [0060]In addition, the same is true for the cases where an input operation has been performed by other input devices (not shown). That is, the input device generates an interrupt in response to the user input operation and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. On the other hand, the bus interface 102 enables the chip select signal 111 connected to the corresponding input device so that the input device outputs the data to the bus 110 and the processor 101 receives the data. [0061]Having described the data input/output operations between the input/output devices 104 to 106 and the processor 101, it may be understood that read and write operations of common registers for each input/output device are similarly realized by the above-described bus access method. [0062]In the system shown in FIG. 1, the mobile phone 100 is connected to the external device 120 through the external device interfaces 107 and 121. The external device 120 includes various enhanced input/output devices as user interfaces, such as an LCD 122 with a relatively large screen, a multi-channel speaker 123, and a large-sized keyboard 124 with tens of keys, such as alphanumeric keys. In addition, although not shown, the external device 120 may have a charge function for the mobile phone 100. [0063]In the past, a method of using a plug cable was commonly adopted for connection between a mobile phone and an external device. In this case, however, there are some problems as already stated. On the other hand, in the present embodiment, the external device interfaces 107 and 121 perform parallel-to-serial conversion of the address information and data information transmitted through the bus and then transmit this information under the conditions in which it is superimposed on a power interface 113. For this reason, neither the number of cables nor the number of poles of the plug is increased. [0064]Next, a method of transmitting and receiving data under the conditions in which the external device 120 is connected to the mobile phone 100 will be described. [0065]First, the case where the screen information of the mobile phone 100 is output to the external device 120 will be described. [0066]The bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the external device interface 107 can receive from the processor 101 the data to be displayed on the screen. In this case, it is assumed that the chip select signal 111 includes the classification indicating that transmitted data is screen information. [0067]The external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. [0068]The external device interface 121 of the external device 120 includes a bus interface function (not shown) and an interrupt controller function (not shown). In addition, the external device interface 121 converts the serial data, which has been received from the mobile phone 100 through the power interface 113, into parallel data to thereby restore it as the same data as in the mobile phone 100 which includes the classification of the chip select signal 111, the address information, and the data information. Then, the external device interface 121 transmits the data to the LCD 122 through a bus 133 by enabling a chip select signal 131 connected to the LCD 122. Thus, the LCD 122 displays and reproduces the same screen information as in the mobile phone 100. For example, video data or still image data downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be displayed on the screen of the LCD 122 in the external device 120. [0069]Moreover, the same is true for the case where the other output information on the side of the mobile phone 100 is output to the external device 120. [0070]For example, when the sound information is output to the external device 120, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the data for sound output is transmitted from the processor 101 to the external device interface 107. In this case, the chip select signal 111 includes the classification indicating that the transmitted data is sound information. Then, the external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. On the other hand, the external device interface 121 of the external device 120 reproduces the same data as in the mobile phone 100 by performing serial-to-parallel conversion of the classification of the received chip select signal 111, the address information, and the data information and then transmits the data to the speaker 123 through the bus 133 by enabling the chip select signal 131 connected to the speaker 123. Thus, the speaker 123 reproduces and outputs the same sound information as in the mobile phone 100. For example, sound data, such as music, downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be reproduced in the speaker 123 of the external device 120. [0071]Next, a processing operation when a user input operation is performed using an input device of the external device 120 will be described. [0072]For example, when there is a user input operation on the keyboard 124, the keyboard 124 generates an interrupt and notifies the external device interface 121 through an interrupt signal 132. [0073]Upon receiving the interrupt signal, the external device interface 121 receives the data input on the keyboard 124 through the bus 133 by enabling the chip select signal 131 connected to the keyboard 124. Then, the external device interface 121 performs parallel-to-serial conversion of the classification of the chip select signal 131 and the address information and data information transmitted through the bus 132 and transmits such data to the power interface 113. [0074]Then, the external device interface 107 of the mobile phone 100 converts the serial data, which has been received from the external device 120 through the power interface 113, into parallel data to thereby restore it as the same data as in the external device 120 which includes the classification of the chip select signal 131, the address information, and the data information. In addition, the external device interface 107 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. [0075]When the processor 101 receives the interrupt, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107. In response to this, the external device interface 107 outputs the data to the bus 110. Thus, the processor 101 can receive the data input by the keyboard 124 of the external device 120. [0076]Moreover, the same is true for the case where other input information on the side of the external device 120 (String), 发明背景 [0001] 一、发明领域 [0002] 本发明涉及一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,移动终端,外部设备,以及输入/输出 移动端的方法。 具体地,本发明涉及一种移动终端系统,其通过外部设备向外部输出在移动终端中接收到的图像数据和声音数据,并且允许通过外部设备在移动终端上执行用户操作, 移动终端、外部设备和移动终端的输入/输出方法。 [0003] 二、相关技术说明 [0004] 移动电话作为移动通信系统的先驱,继承了车载电话的先河,随着终端的小型化、轻量化、低价化和服务费的降低,从1990年代开始迅速普及。 此外,随着计算机的普及和包括因特网在内的宽带网络技术的发展,可以在手机上进行电子邮件和网络搜索/访问,并且可以执行各种应用,例如音乐或视频播放和游戏。 [0005] 然而,虽然手机的应用范围多种多样,但由于手机需要便携的尺寸,因此在输入和输出方面存在很多限制。 例如,屏幕尺寸对角线约5至10厘米。 在这种情况下,尽管近年来由于平板制造技术的发展分辨率越来越高,但高分辨率显示会导致可见性问题,例如,相同字体大小的字符变得非常小。 [0006] 另外,手机中设置的输入部分一般只有0到9的数字键盘,以及可以进行上下左右输入操作的按键,以及其他一些按键。 与个人电脑的键盘有60到100个按键相比,手机的按键数量少,输入操作也比较困难。 [0007] 近几年,也出现了类似QWERTY键盘的几十个按键的手机。 然而,由于设备大小的便携性限制,每个密钥都很小。 为此,输入操作还是有难度的。 [0008] 为了解决这样的问题,可以考虑将移动电话连接到具有相对大屏幕的外部设备或易于执行输入操作的输入设备的方法。 [0009] 例如,提出了使用移动终端的显示处理系统。 在显示处理系统中,显示在移动电话的液晶屏幕上的图像可以显示在电视屏幕上(例如,参考日本未审查专利申请公开No.2001-352373)。 [0010] 此外,还提出了一种屏幕显示装置,其具有用于连接手机的入口。 屏幕显示设备在大屏幕上显示在移动电话中接收到的图像数据(例如,参考日本未审查专利申请公开No.2002-116843)。 [0011] 此外,还提出了一种带有独立显示器的移动电话。 移动电话显示在移动电话内置的监视器上显示的数据或在单独的监视器上下载的显示数据(例如,参考日本未审查专利申请公开No.2003-78597)。 [0012]然而,为了通过将移动电话连接到外部设备来发送或接收数据,用于视频信号的输入/输出、声音信号的输入/输出、用户操作信号的输入/输出的多条信号传输线 ,等等是必要的(参考图10)。 也就是说,对于移动电话和外部设备之间的连接,使用多根电缆用于视频、声音和用户操作,或者使用具有多极端子的插头电缆。 在使用多根电缆的前一种情况下,电缆的连接和断开操作对用户来说很麻烦。 此外,在后一种使用插头电缆的方法中,随着极数的增加,存在难以确保小型移动电话主体中用于布置插头的位置的问题。 此外,还存在由于连接器等部件的成本而导致装置变得昂贵、连接器之间的接触点难以获得足够强度的问题。 [0013] 另外,随着手机型号不同,输入或输出信号的分类发生变化时,插头的极数也会发生变化。 在这种情况下,外部设备的连接器在不同型号之间不兼容,这很不方便。 发明内容 [0014] 鉴于上述情况,期望提供一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如手机,以及连接到移动终端并能够输出图像数据的外部设备。 以及移动终端中接收到的声音数据通过外部设备发送到外部并允许用户通过外部设备在移动终端上执行操作、移动终端、外部设备以及移动设备的输入/输出方法 终端。 [0015] 此外,期望提供一种移动终端系统,其中移动终端和外部设备通过具有简单配置的接口相互连接,使得在移动终端中接收的图像数据和声音数据可以输出到 外部设备通过外部设备可以在移动终端上进行用户操作、移动终端、外部设备和移动终端的输入/输出方法。 [0016] 根据本发明第一实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作。 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0017] 这里所说的“系统”是指多个设备(或实现特定功能的功能模块)的逻辑集合,与设备或功能模块是否存在于一个外壳内无关。 [0018]根据本发明的第二实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0019] 这里,根据本发明的第三实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 即,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括电力电缆上传输的电流信号,还包括用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0020] 另外,根据本发明的第四实施例,移动终端可以是手机,屏幕信息可以是通过手机网络接收的视频数据或静止图像数据。 [0021] 此外,根据本发明的第五实施例,第一和第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据 通过对接收到的数据进行串并转换。 [0022] 此外,根据本发明的第六实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0023] 此外,根据本发明的第七实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0024]这里,根据本发明的第八实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0025] 此外,根据本发明的第九实施例,移动终端的第一外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0026] 此外,根据本发明的第十实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用。 终端; 第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电; 显示部分输出从移动终端接收的屏幕信息。 [0027] 此外,根据本发明的第十一实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用该用户输入部分。 终端; 第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息; 显示部分输出从移动终端接收的屏幕信息。 [0028] 这里,根据本发明的第十二实施例,第一外部设备接口中设置的线圈可以是用于电力接收的线圈,第二外部设备接口中设置的线圈可以是电力传输线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0029] 此外,根据本发明的第十三实施例,外部设备的第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在电力信号上,并且可以再现叠加在电源信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0030]另外,根据本发明的第十四实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0031] 另外,根据本发明第十五实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0032] 根据本发明的实施例,可以提供出色的移动终端系统,其包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,并且能够 将在移动终端中接收到的图像数据和声音数据通过外部设备输出到外部,并允许用户通过外部设备在移动终端上进行操作,移动终端,外部设备,输入/输出 移动端的方法。 [0033] 此外,根据本发明的实施例,可以提供出色的移动终端系统,其中移动终端和外部设备通过具有简单配置的接口彼此连接,使得接收到的图像数据和声音数据 移动终端中的信息可以通过外部设备输出到外部,用户可以通过外部设备对移动终端进行操作,移动终端,外部设备,移动终端的输入/输出方法。 [0034] 根据本发明的第一至第三、第六至第八、第十至第十二、第十四和第十五实施例,可以在大屏幕上显示接收到的数据,并且可以通过来自易于操作的输入来操作移动终端。 - 只需将显示设备或输入设备的尺寸不够大的移动终端放在外部设备上即可使用键盘。 [0035] 此外,根据本发明的第四实施例,可以使用外部设备的大屏幕来显示从互联网下载到移动电话的视频数据或静止图像数据。 [0036]此外,根据本发明的第五、第九和第十三实施例,在移动电话和外部设备之间执行使用少量接触点的传输。 这是有利的,因为简化了连接接口,降低了连接部分的组件成本,设备尺寸小,并且防止了接触点的劣化。 通过对连接接口应用无线连接,例如电场传输,可以进一步改善这些效果。 [0037] 此外,根据本发明的实施例,由于提供简单的与外部设备的连接接口就足够了,因此可以减少设计上的限制。 [0038] 本发明的其他目的、特征和优点将通过以下结合附图对本发明的实施例的详细描述而显而易见。 附图的简要说明 [0039] 图1是表示本发明的一个实施方式的移动终端系统的概略结构的图。 [0040] 图2是表示串行发送并行数据的结构例的图。 [0041] 图3是电力线上信号的频谱特性曲线。 [0042] 图4A是表示串行地发送并行数据的串行器的另一例的图。 [0043] 图4B是表示串行地发送并行数据的串行器的另一例的图。 [0044] 图5是表示从移动电话向外部设备的LCD进行写入时的移动电话内的总线和外部设备的总线的写入顺序例的图。 [0045] 图6是表示进行从移动电话读取外部设备的键盘的输入信息的操作时的移动电话内的总线和外部设备的总线的读取顺序例的图。 [0046] 图7是表示在外部设备的键盘上发生中断时的移动电话内的总线和外部设备内的总线的中断时序例的图。 [0047] 图8是表示移动电话与外部设备之间的传输帧的格式例的图。 [0048] 图9为图1所示的移动终端系统的应用程序图像示意图。 和 [0049] 图10是表示以往的便携终端系统的结构例的图。 优选实施例的描述 [0050] 在下文中,将参考附图描述本发明的实施例。 [0051] 图1是图示根据本发明实施例的移动终端系统的配置的示意图。 图1所示的系统包括接收图像数据和声音数据的移动电话,以及将图像数据和声音数据输出到外部或者当用户操作移动电话时使用的外部设备。 [0052] 一部手机 100 包括一个处理器 101 , 各种输入输出设备 104 到 106 , 和一个外部设备接口 107 用于连接外部设备 120 . 而且,虽然手机 100 包括无线电通信等电路模块,由于与本发明的主旨无直接关系,故未图示。 [0053] 处理器 101 连接到各种输入/输出设备 104 到 106 通过总线信号线组 110 , 片选信号 111 , 和一个中断信号 112 . [0054] 总线信号线组 110 包括信号线,例如地址、数据和启用。 除了各种输入/输出设备 104 到 106 ,总线信号线组 110 也连接到外部设备接口 107 . [0055] 片选信号 111 是处理器使用的信号 101 选择各种输入/输出设备之一的电路芯片 104 到 106 通过总线接口 102 . 此外,中断信号 112 是信号,在各种输入/输出设备时使用 104 到 106 通知处理者 101 一个事件的发生,并被输入到一个中断控制器 103 . 片选信号 111 和中断信号 112 准备了与输入/输出设备数量相等的数量,并连接到外部设备接口 107 . [0056] 一、手机端的一个操作 100 将被描述。 [0057] 将数据输出到 LCD 屏幕时 104 , 处理器 101 输出图像数据到LCD 104 使用总线接口 102 . 向 LCD 输出数据时 104 , 总线接口 102 启用片选信号 111 连接到液晶显示器 104 这样液晶显示器 104 从处理器接收图像数据 101 并将数据显示在屏幕上。 例如,通过手机网络从 Internet 上的网站下载的视频数据或静止图像数据可以显示在 LCD 的屏幕上 104 . [0058] 此外,当向扬声器输出数据时 105 或其他输出设备(未显示),处理器 101 同样只启用片选信号 111 连接到相应的输出设备,以便输出设备接收来自处理器的数据 101 并再现和输出数据。 例如,可以在扬声器中再现通过手机网络从互联网网站下载的音乐等声音数据 105 . [0059] 另一方面,当用户在键盘上进行输入操作时 106 , 键盘 106 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . 处理器 101 接收到中断 接收到键盘输入的数据 106 , 通过公交车 110 . 在这种情况下,总线接口 102 启用片选信号 111 连接到键盘 106 这样键盘 106 可以将数据输出到总线 110 和处理器 101 可以接收数据。 [0060] 另外,对于由其他输入设备(未图示)进行了输入操作的情况也是同样的。 即输入设备响应用户输入操作产生中断,通知中断控制器 103 处理器的 101 通过中断信号 112 . 另一方面,总线接口 102 启用片选信号 111 连接到相应的输入设备,使输入设备输出数据到总线 110 和处理器 101 接收数据。 [0061] 描述了输入/输出设备之间的数据输入/输出操作 104 到 106 和处理器 101 可以理解,对于每个输入/输出设备的公共寄存器的读写操作是通过上述总线访问方法类似地实现的。 [0062] 在图1所示的系统中,手机 100 连接到外部设备 120 通过外部设备接口 107 和 121 . 外部设备 120 包括各种增强型输入/输出设备作为用户界面,例如 LCD 122 屏幕比较大,多声道喇叭 123 , 和一个大尺寸的键盘 124 带有数十个键,例如字母数字键。 此外,虽然没有显示,外部设备 120 可能有手机充电功能 100 . [0063]以往,手机与外部设备的连接通常采用插头线的方式。 然而,在这种情况下,存在已经提到的一些问题。 另一方面,在本实施例中,外部设备接口 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些信息 113 . 为此,既没有增加电缆的数量,也没有增加插头的极数。 [0064] 接下来介绍一种在外部设备不可用的情况下发送和接收数据的方法 120 已连接手机 100 将被描述。 [0065] 一、手机屏幕信息的情况 100 输出到外部设备 120 将被描述。 [0066] 总线接口 102 启用片选信号 111 连接到外部设备接口 107 使外部设备接口 107 可以从处理器接收 101 要显示在屏幕上的数据。 在这种情况下,假定片选信号 111 包括指示传输的数据是屏幕信息的分类。 [0067] 外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . [0068] 外部设备接口 121 外部设备的 120 包括总线接口功能(未显示)和中断控制器功能(未显示)。 此外,外部设备接口 121 转换从手机接收到的串口数据 100 通过电源接口 113 , 转化为并行数据从而恢复为与手机中相同的数据 100 其中包括片选信号的分类 111 、地址信息和数据信息。 然后,外部设备接口 121 将数据传输到 LCD 122 通过公共汽车 133 通过使能片选信号 131 连接到液晶显示器 122 . 因此,液晶 122 显示和再现与手机相同的屏幕信息 100 . 例如,从互联网网站下载到手机的视频数据或静止图像数据 100 通过手机网络可以显示在液晶屏上 122 在外部设备中 120 . [0069] 而且,其他手机端输出信息的情况也是如此 100 输出到外部设备 120 . [0070] 例如,当声音信息输出到外部设备时 120 , 总线接口 102 启用片选信号 111 连接到外部设备接口 107 以便声音输出的数据从处理器传输 101 到外部设备接口 107 . 在这种情况下,片选信号 111 包括指示传输的数据是声音信息的分类。 然后,外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . 另一方面,外部设备接口 121 外部设备的 120 再现与手机中相同的数据 100 通过对接收到的片选信号进行分类串并转换 111 ,地址信息,数据信息,然后将数据传输给扬声器 123 通过公共汽车 133 通过使能片选信号 131 连接到扬声器 123 . 因此,演讲者123 再现和输出与手机相同的声音信息 100 . 例如,从互联网上的网站下载到手机中的音乐等声音数据 100 通过手机网络可以在音箱中重现 123 外部设备的 120 . [0071] 接下来,使用外部设备的输入设备进行用户输入操作时的处理操作 120 将被描述。 [0072] 例如,当键盘上有用户输入操作时 124 , 键盘 124 产生中断并通知外部设备接口 121 通过中断信号 132 . [0073] 接收到中断信号后,外部设备接口 121 接收键盘输入的数据 124 通过公共汽车 133 通过使能片选信号 131 连接到键盘 124 . 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0074] 然后,外部设备接口 107 手机的 100 转换从外部设备接收到的串行数据 120 通过电源接口 113 , 转换为并行数据,从而将其恢复为与外部设备中相同的数据 120 其中包括片选信号的分类 131 、地址信息和数据信息。 此外,外部设备接口 107 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . [0075] 当处理器 101 接收到中断,总线接口 102 启用片选信号 111 连接到外部设备接口 107 . 响应于此,外部设备接口 107 将数据输出到总线 110 . 因此,处理器 101 可以接收键盘输入的数据 124 外部设备的 120 . [0076] 此外,对于外部设备侧的其他输入信息的情况也是如此 120 被输入到手机 100 . [0077] 即输入设备响应用户输入操作等产生中断通知给外部设备接口 121 . 接收到中断信号后,外部设备接口 121 通过总线接收数据 133 通过使能片选信号 131 连接到相应的输入设备。 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0078] 外部设备接口 107 手机的 100 对片选信号的分类进行串并转换 131 、地址信息、从外部设备接收到的数据信息 120 ,从而恢复与外部设备中相同的数据 120 . 此外,外部设备接口 107 通知中断控制器 103 处理器的 101 通过中断信号 112 有来自外部设备的输入 120 . 然后,总线接口 102 启用片选信号 111 连接到外部设备 120 这样处理器 101 从外部设备接收输入数据 120 . [0079] 描述了输入/输出设备之间的数据输入/输出操作 122 到 124 外部设备的 120 和处理器 101 手机的 100,可以理解为外部设备的每个输入/输出设备的公共寄存器的读写操作 120 通过上述总线访问方法类似地实现。 [0080] 在本实施例中,手机与手机之间的接口 100 和外部设备 120 通过采用外部设备接口的方法简化了 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些数据 113 . [0081] 图2例示了串行传输并行数据的配置示例。 图2所示的传输系统包括串行器 200 和反序列化器 210 它们通过电源线相互连接 220 作为电源接口 113 . 假设这对序列化器 200 和反序列化器 210 双向设置于外部设备接口 107 手机的 100 和外部设备接口 121 外部设备的 120 . [0082] 序列化器 200 包括一个 PS(并行到串行)转换器 201 将并行信号转换为串行信号,PLL 部分 202 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 203 通过向串行信号添加标头等来执行编码,时序控制器 204 它控制传输时间,和一个司机 205 . [0083] 另一方面,反序列化器 210 包括一个接收器 212 , 解码器 213 它通过从报头、时钟恢复 (CR) 部分检测数据的头部来解码编码数据 214 它使用参考时钟 (Ref. CLK)、SP(串行到并行)转换器从接收到的数据中提取时钟 215 它将串行信号转换为原始并行信号,以及一个时序控制器 216 它控制接收时间。 [0084] 因此,输入到串行器的并行数据 P-DATA 和用于串行数据的时钟 P-CLK 200 转换为串行信号,通过解串器恢复为原来的并行数据P-DATA和时钟P-CLK 210 . [0085] 在图 2 所示的示例中,电源线 220 用作传输线,在叠加在电源线上的条件下传输串行信号 220 从外部设备 120 到手机 100 . 叠加部分 206 将传输信号叠加在用于供电的功率信号上。 基本上,叠加部分 206 将传输信号与电源线耦合 220 通过一个电容器并将电源信号与电源线耦合 220 通过扼流圈。 [0086] 到达解串器的传输信号 210 通过电源线 220 通过分离部分与电源信号分离 212 . 类似于叠加部分 206 , 在分离部分 211 ,在通过电容器切断直流分量之后提取传输信号,并且通过扼流圈从传输信号中切断功率信号。 [0087] 此外,可以提及曼彻斯特编码作为编码器中应用的编码方法的示例 203 和解码器 213. 在曼彻斯特编码中,当传输一个二进制值“0”时,它在位段中间由高电平变为低电平。 另一方面,当传输二进制值“1”时,它在比特部分的中间从低电平相反地变为高电平。 换言之,在曼彻斯特编码中,通过两次扩展频带来去除传输信号的DC分量。 由于曼彻斯特码的优点在于不包括直流分量并且容易提取时钟,因此认为曼彻斯特码适合与具有直流分量的电力叠加在同一传输线上。 电力线上信号的频谱 220 如图3所示。在图3中,附图标记 301 表示曼彻斯特码的频谱。 已知曼彻斯特码可以在不包括直流分量的情况下与功率信号一起传输。 [0088] 串行传输并行数据的串行器和解串行器的另一配置示例在图4A和4B中示出。 [0089] 序列化器 400 包括一个PS转换器 401 将并行信号转换为串行信号,PLL 部分 402 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 403 通过向串行信号添加标头等来执行编码,时序控制器 404 它控制传输时间,和一个司机 405 . 编码器编码的串行信号 403 被传输到一个线圈 406 通过司机 405 然后传输到解串器 410 通过线圈之间的电磁耦合。 [0090] 另一方面,反序列化器 410 包括一个线圈 411 它与线圈进行电磁耦合 406 在序列化器的一侧 400 , 一个差分接收器 412 , 放大器 413 放大由电磁耦合降低的信号电平,解码器 414 它从报头中检测数据的头部并对编码数据进行解码,时钟恢复(CR)部分 415 它使用参考时钟 (Ref. CLK)、SP 转换器从接收到的数据中提取时钟 416 它将串行信号转换为原始并行信号,以及一个时序控制器 417 它控制接收时间。 [0091] 当采用图2或图4A、4B所示的串行传输作为电源接口时 113 连接外部设备 120 和手机 100 相互之间,可以将数据叠加在电源信号上,并且可以在从外部设备进行充电的同时进行数据传输 120 到手机 100 . 此外,根据图4A和4B所示的串行传输方法,可以使用线圈在电场中传输数据。 结果,由于可以通过无线连接发送和接收数据,因此连接外部设备的电缆 120 用手机 100 变得不必要。 [0092] 接下来是手机之间进行数据收发时的总线访问操作 100 和外部设备 120 将被描述。 下面根据美国英特尔公司的80总线架构来描述总线访问操作。 然而,本发明不限于此。 [0093] 图 5 说明了总线的写入序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 从手机执行写入操作时 100 到液晶显示器 122 外部设备的 120 . [0094] 在手机里 100 ,处理器断言(启用)具有 LCD 分类的片选信号 101 . 随后,总线上的写信号 110 由处理器断言 101 然后将写数据传输到总线 110 . [0095] 通过这样的操作,数据被写入外部设备接口 107 手机的100 . 然后,外部设备接口 107 将请求写入的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0096] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 随后,外部设备接口 121 断言连接到 LCD 的片选信号 122 , 断言总线上的写信号 133 ,然后将写数据传输到总线 110 . 因此,将数据写入LCD 122 被执行。 结果,液晶 122 可以显示和再现与手机相同的屏幕信息 100 . [0097] 此外,可以理解为在每个移动电话中执行相同的总线写入序列 100 和外部设备 120 同样在手机输出其他信息的情况下 100 写入外部设备 120 . [0098] 图 6 说明了总线的读取序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 执行读取键盘输入信息的操作时 124 外部设备的 120 从手机 100 . [0099] 在手机里 100 ,具有键盘分类的片选信号被断言,然后总线上的读取信号 110 由处理器断言 101 . 然后,外部设备接口 107 手机的 100 将请求读取的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0100] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 然后,外部设备接口 121 断言连接到键盘的片选信号 124 然后在总线上断言读取信号 133 . 然后,键盘 124 将输入数据传输到总线 110 . [0101] 从键盘读取数据后 124 , 外接设备接口 121 将数据转换成串口数据串口传输给手机 100 通过电源接口 113 . [0102] 外部设备接口 107 手机的 100 提取键盘上的输入数据 124 通过将接收到的串行数据转换成并行数据,然后传输到总线 110 在读信号被断言的期间。 因此,处理器 101 可以从键盘读取输入数据 124 外部设备的 120 . [0103] 此外,可以理解,在每个移动电话中执行相同的总线读取序列 100 和外部设备 120 同样在外部设备的其他输入信息的情况下 120 在手机中读取 100 . [0104] 图 7 说明了总线的中断序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 当键盘发生中断时 124 外部设备的 120 . [0105] 键盘 124 断言中断信号 132 当中断发生时。 外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113. 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 断言中断信号 112 . [0106] 处理器收到中断信号后 101 根据上述过程执行总线访问(读或写)。 例如,总线接口 102 启用片选信号 111 连接到外部设备接口 107 , 这样处理器 101 读取键盘上的输入数据 124 从外部设备 120 通过公共汽车 110 . [0107] 随后,当键盘 124 否定中断信号 132 通过释放中断,外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113 . [0108] 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 否定中断信号 112 . 结果在手机端也释放了键盘中断 100 . [0109] 图 8 说明了移动电话之间的传输帧的格式示例 100 和外部设备 120 . [0110] 图8所示的传输帧在报头部分包括数据类型、设备类型和数据长度字段。 [0111] 数据类型字段长度为2位,用于区分传输帧对应的读、写、中断发生和中断释放。 例如0×00表示读,0×01表示写,0×02表示中断。 [0112] 设备类型字段,长度为2比特,用于区分传输帧是对哪个设备的读或写请求,或者是区分传输帧是来自哪个设备的中断发生或释放请求。 例如0×00表示LCD,0×01表示键盘,0×02表示扬声器。 [0113] 数据长度字段具有1个字节的长度,并且传输帧的数据(有效载荷)部分的长度例如以比特数来描述。 [0114] 此外,位 0 到最后一位连接在传输帧的数据部分。 [0115] 此外,图8所示的传输帧格式只是一个例子,本发明不限于此。 可以使用根据应用本发明的系统适当定义的任何传输帧格式。 此外,传输帧中可以包括使用校验和的错误检测和错误纠正等功能。 [0116] 图9是图1所示的移动终端系统的应用程序图像的图示。 [0117] 外部设备 901 包括液晶显示器 901 带有相对较大的屏幕和键盘 903 使用 QWERTY 排列中的所有键。 通过放置手机 904 在连接部分 902 , 手机屏幕 904 可以显示在LCD上 901 和手机 904 可以通过键盘上的用户输入进行操作 903 . [0118] 一个联络点 905 与手机连接 904 在连接部分提供 902 , 这样手机 904 可以充电,可以通过触点进行数据传输 905 . [0119] 然而,当如图 4A 和 4B 所示执行使用线圈的电场传输时,接触点 905 外部设备之间 900 和手机 904不存在,通过线圈进行通信 906 在外部设备中提供 900 . [0120] 本申请包含与 2008 年 10 月 15 日向日本专利局提交的日本优先权专利申请 JP 2008-266856 中公开的主题相关的主题,其全部内容通过引用并入本文。 [0121] 本领域技术人员应当理解,可以根据设计要求和其他因素进行各种修改、组合、子组合和变更,只要它们在所附权利要求或其等同物的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:10.968 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.189 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.190 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.191 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.194 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.195 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.196 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.197 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.197 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.224 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.227 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.228 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.229 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.231 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.231 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270633(Integer), CN101729662A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.251 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.251 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.252 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270633(Integer), CN101729662B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.267 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.267 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.268 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270633(Integer), JP2010098484A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.285 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.286 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.286 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270633(Integer), JP4893722B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.296 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.297 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.297 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270633(Integer), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.307 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.308 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.308 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100093394A1(String), US20100093394A1(String), 1271260800(Integer), 270633(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.319 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.332 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.333 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), HIDAKA, ISAO(String), 索尼公司(String), HIDAKA ISAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.334 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.342 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.343 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 0(Integer), 1681974671(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.351 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.353 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.353 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.355 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.355 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.356 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 184950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.362 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.363 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.364 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HIDAKA, ISAO(String), HIDAKA ISAO(String), 0(Integer), 1681974671(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.371 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.372 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.373 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184950(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.373 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.374 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.374 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75899(Integer), 2(Integer), 184950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.392 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.394 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.395 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.396 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.397 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.398 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.399 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.401 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.402 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75899(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.403 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.412 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.412 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.413 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.414 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.415 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.422 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.444 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.444 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.446 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.454 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.454 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.455 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.456 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.456 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.466 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.469 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.469 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10075579B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.471 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.471 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.472 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, user interface method in the mobile terminal, and cover of the mobile terminal(String), 移动终端、移动终端中的用户界面方法及移动终端的外壳(String), US10075579B2(String), A mobile terminal, a method in the mobile terminal, and a cover of the mobile terminal are provided for processing input. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined, and a second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area while the cover is closed over the touch screen is detected and the first input as a first control command is processed.(String), 本 发明提供一种移动终端、移动终端中的方法及移动终端的外壳,用于处理输入。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域,并定义了与封面的非窗口区域对应的移动终端的触摸屏的第二区域。 检测当盖板在触摸屏上关闭时第二区域中的第一输入,并且处理作为第一控制命令的第一输入。(String), US14/603760(String), 1421942400(Integer), US10075579B2(String), 1536595200(Integer), 1536595200(Integer), 美国(String), 4(Integer), KR(String), 7(Integer), 40(Integer), JP2006277739A | JP2008097966A | KR101285669B1 | KR1020080108839A | KR1020110025939A | KR1020130004769A | KR200464076Y1 | KR2020120005719U | US20040248621A1 | US20080062348A1 | US20100238119A1 | US20110065474A1 | US20110260980A1 | US20120098760A1 | US20120250241A1 | US20130083465A1 | US20130109435A1 | US20130181935A1 | US20130300679A1 | US20140073377A1 | US20140128131A1 | US20140185206A1 | US20140198070A1 | US20140204511A1 | US20140274214A1 | US20140292589A1 | US20140357330A1 | US20150105128A1 | US20150138021A1 | US20150155903A1 | US20150229754A1 | US20150280770A1 | US20160154512A1 | US20160277053A1 | US9307129B2 | WO2001028190A1(String), 31(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.479 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.481 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.481 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.483 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.484 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.484 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ddaac83156eb49188b3f861ae7fc9738.png(String), 184951(Integer), ddaac83156eb49188b3f861ae7fc9738.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.492 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.493 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.493 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.494 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.495 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.496 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, user interface method in the mobile terminal, and cover of the mobile terminal(String), 移动终端、移动终端中的用户界面方法及移动终端的外壳(String), US10075579B2(String), A mobile terminal, a method in the mobile terminal, and a cover of the mobile terminal are provided for processing input. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined, and a second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area while the cover is closed over the touch screen is detected and the first input as a first control command is processed.(String), 本 发明提供一种移动终端、移动终端中的方法及移动终端的外壳,用于处理输入。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域,并定义了与封面的非窗口区域对应的移动终端的触摸屏的第二区域。 检测当盖板在触摸屏上关闭时第二区域中的第一输入,并且处理作为第一控制命令的第一输入。(String), US14/603760(String), 1421942400(Integer), US10075579B2(String), 1536595200(Integer), 1536595200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 7(Integer), 40(Integer), JP2006277739A | JP2008097966A | KR101285669B1 | KR1020080108839A | KR1020110025939A | KR1020130004769A | KR200464076Y1 | KR2020120005719U | US20040248621A1 | US20080062348A1 | US20100238119A1 | US20110065474A1 | US20110260980A1 | US20120098760A1 | US20120250241A1 | US20130083465A1 | US20130109435A1 | US20130181935A1 | US20130300679A1 | US20140073377A1 | US20140128131A1 | US20140185206A1 | US20140198070A1 | US20140204511A1 | US20140274214A1 | US20140292589A1 | US20140357330A1 | US20150105128A1 | US20150138021A1 | US20150155903A1 | US20150229754A1 | US20150280770A1 | US20160154512A1 | US20160277053A1 | US9307129B2 | WO2001028190A1(String), \20230420\ddaac83156eb49188b3f861ae7fc9738.png(String), 31(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.507 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.508 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.508 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.509 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.515 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.516 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 1. A method of processing input in a mobile terminal, the method comprising:identifying a first area of a touch screen of the mobile terminal corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 1.一种在移动终端中处理输入的方法,该方法包括:通过接收来自外壳的信息识别移动终端的触摸屏的第一区域对应于外壳的窗口区域和触摸屏的第二区域对应于外壳的非窗口区域;检测触摸屏上方的移动终端盖板是否合上;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.516 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 2. The method of claim 1, further comprising determining a type of the cover, wherein the first area and the second area are defined according to the type of the cover.(String), 2.如权利要求1所述的方法,还包括判断封面的类型,其中第一区域与第二区域是根据封面的类型定义的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.517 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 3. The method of claim 1, further comprising determining whether an event has occurred, while the cover is closed over the touch screen of the mobile terminal, wherein the first area and the second area are defined according to occurrence of the event.(String), 3.如权利要求1所述的方法,还包括在移动终端的触摸屏上盖合上时判断事件是否发生,其中第一区域和第二区域是根据事件的发生定义的。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.517 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 4. The method of claim 1, further comprising:detecting a third input in the first area while the cover is closed over the touch screen;processing the third input as a third control command; anddetecting a fourth input in the second area while the cover is closed over the touch screen; and processing the fourth input as a fourth control command,wherein the third input and the fourth input are of a same type, which is different from that of the first input and the second input.(String), 4.如权利要求1所述的方法,还包括:在触摸屏上盖合上时检测第一区域中的第三输入;将第三输入处理为第三控制命令;和在触摸屏上盖合上时检测第二区域中的第四输入;并将第四输入处理为第四控制命令,其中,第三输入与第四输入为同一类型,与第一输入与第二输入不同。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.517 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 5. The method of claim 1, further comprising receiving cover type information from the cover.(String), 5.如权利要求1所述的方法,还包括从封面接收封面类型信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.517 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 6. The method of claim 5, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 6.如权利要求5所述的方法,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.517 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 7. The method of claim 1, further comprising activating a part of the touch screen according to the first and second areas, while the cover is closed over the touch screen.(String), 7.如权利要求1所述的方法,还包括根据第一区域和第二区域激活触摸屏的一部分,同时关闭触摸屏上的盖体。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.518 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 8. The method of claim 1, further comprising, when the cover is closed over the touch screen, activating a screen of the first area and a touch sensing area of the second area.(String), 8.如权利要求1所述的方法,还包括,当盖合于触控屏幕上时,激活第一区域的屏幕和第二区域的触控感应区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.518 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 9. The method of claim 1, wherein processing the first input comprises displaying information in the first area according to the first input detected in the second area.(String), 9.如权利要求1所述的方法,其中处理第一输入包括根据在第二区域中检测到的第一输入在第一区域中显示信息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.518 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 10. The method of claim 9, wherein the information comprises at least one of music play information, a camera preview, busy call information, and information about at least one application.(String), 10.如权利要求9所述的方法,其中该信息包括音乐播放信息、相机预览、忙音信息和至少一个应用程序的信息中的至少一种。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.518 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 11. A mobile terminal comprising:a touch screen; anda processor configured to:identify a first area of the touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detect whether the cover of the mobile terminal is closed over the touch screen,detect an input in the touch screen while the cover is closed over the touch screen, determine whether the input is a first input in the first area or a second input in the second area, process a first control command according to the first input in the first area, and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 11.移动终端包括:触摸屏;和处理器配置为:通过接收来自外壳的信息,识别对应于移动终端外壳的窗口区域的触摸屏的第一区域和对应于外壳的非窗口区域的触摸屏的第二区域;检测触摸屏上方移动终端的盖板是否合上,在触摸屏上盖合上时检测触摸屏中的输入,判断输入是第一区域中的第一输入还是第二区域中的第二输入,根据第一区域中的第一输入处理第一控制命令第一区域,以及根据第二区域中的第二输入的第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.518 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 12. The mobile terminal of claim 11, wherein the non-window area of the cover includes a keypad configured to apply a key input, and the processor is further configured to detect the key input applied through the keypad of the non-window area of the cover in the second area.(String), 12.如权利要求11所述的移动终端,其中所述盖板的非窗口区域包括键盘,用于进行键输入,所述处理器还用于在所述第二区域中检测通过所述盖板的非窗口区域的键板施加的键输入。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.519 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 13. The mobile terminal of claim 12, wherein the processor is further configured to receive a text input as a result of detecting the key input through the keypad and control execution of a function according to the text input.(String), 13.如权利要求12所述的移动终端,其中处理器还被配置为接收作为检测通过小键盘的键输入的结果的文本输入,并根据文本输入控制功能的执行。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.519 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 14. The mobile terminal of claim 11, further comprising a receiver configured to receive cover type information from the cover,wherein the processor is further configured to check the cover type information about the cover and define the first and second areas according to the cover type information.(String), 14.如权利要求11所述的移动终端,还包括接收器,配置为从封面接收封面类型信息,其中,处理器还用于检查封面的封面类型信息,并根据封面类型信息定义第一区域和第二区域。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.519 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 15. The mobile terminal of claim 14, further comprising a memory configured to store the cover type information.(String), 15.如权利要求14所述的移动终端,还包括存储器,用于存储封面类型信息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.519 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 16. The mobile terminal of claim 14, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 16.如权利要求14所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.520 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 17. The mobile terminal of claim 11, wherein the window area of the cover is transparent or semi-transparent and the non-window area of the cover is opaque.(String), 17.如权利要求11所述的移动终端,其中盖板开窗区为透明或半透明,盖板非开窗区为不透明。(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.520 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 18. The mobile terminal of claim 11, wherein the processor is further configured to set different touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen.(String), 18.如权利要求11所述的移动终端,其中处理器还被配置为在触摸屏的第一区域和第二区域设置不同的触摸输入灵敏度以感测触摸输入。(String), 1(Integer), 17(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.520 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 19. The mobile terminal of claim 11, wherein the processor is further configured to set touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen according to whether the cover is closed over the touch screen.(String), 19.如权利要求11所述的移动终端,其中处理器还被配置为根据触摸屏上的盖子是否关闭来设置用于感测触摸屏的第一区域和第二区域中的触摸输入的触摸输入灵敏度。(String), 1(Integer), 18(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.520 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 20. The mobile terminal of claim 11, further comprising a battery packet disposed inside a rear surface of the mobile terminal,wherein the touch screen is formed on a front surface of the mobile terminal, andwherein the cover comprises:a battery cover unit provided on the rear surface of the mobile terminal, for protecting the battery packet; anda front cover unit connected to the battery cover unit, for covering the touch screen of the mobile terminal.(String), 20.如权利要求11所述的移动终端,还包括电池包设置在移动终端的后表面内,其中,触摸屏形成在移动终端的前表面上,并且其中,覆盖物包括:电池盖单元,设置在移动终端的背面,用于保护电池包;和前盖单元,与电池盖单元连接,用于盖住移动终端的触摸屏。(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.521 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 21. The mobile terminal of claim 11, wherein the cover comprises:a front cover unit configured to cover a front surface of the mobile terminal;a rear cover unit configured to cover a rear surface of the mobile terminal; anda connection unit configured to connect the front cover unit to the rear cover unit.(String), 21.如权利要求11所述的移动终端,其中封面包括:前盖单元,被配置为覆盖移动终端的前表面;后盖单元,被配置为覆盖移动终端的后表面;和连接单元被配置为将前盖单元连接到后盖单元。(String), 1(Integer), 20(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.521 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 22. The mobile terminal of claim 11, further comprising a magnetic force sensor configured to sense a change of an external magnetic force,wherein the processor is further configured to control the touch screen according to the change of the external magnetic force sensed by the magnetic force sensor.(String), 22.如权利要求11所述的移动终端,还包括磁力传感器,配置为感测外部磁力的变化,其中,处理器还用于根据磁力传感器感应到的外部磁力的变化控制触摸屏。(String), 1(Integer), 21(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.521 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 23. A mobile terminal comprising:a cover including a transparent or semi-transparent window area and an opaque non-window area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, for covering a touch screen of the mobile terminal;the touch screen including a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of a front cover unit of the cover; anda processor configured to:identify the first area of the touch screen corresponding to the window area of the cover of the mobile terminal and the second area of the touch screen corresponding to the non-window area of the cover by receiving information from the cover;control the touch screen to display a visual object on a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, wherein one of the visual object and another visual object are not displayed on a second area of the touch screen corresponding to a non-window area of the cover while the cover is closed over the touch screen,activate touch sensing for the second area of the touch screen while the cover is closed over the touch screen,control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the cover is closed over the touch screen.(String), 23.移动终端包括:覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域,覆盖物包括被配置为向移动终端应用多个有区别的键输入的键盘,用于覆盖移动终端的触摸屏;触摸屏包括对应于盖体的窗口区域的第一区域和对应于盖体的非窗口区域的第二区域,其中键盘包括雕刻或印刷在盖体的外表面上的多个区别键。封面的封面单元;和处理器配置为:通过接收外壳的信息识别移动终端外壳窗口区域对应的触摸屏第一区域和外壳非窗口区域对应的触摸屏第二区域;控制触摸屏在触摸屏的与移动终端的外壳的窗口区域对应的第一区域上显示视觉对象,其中在触摸的第二区域上不显示视觉对象和另一个视觉对象中的一个盖板关闭时对应于盖板非窗口区域的屏幕覆盖在触摸屏上,当盖子在触摸屏上关闭时,激活触摸屏第二区域的触摸感应,根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时盖子在触摸屏上方关闭。(String), 0(Integer), 22(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.521 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 24. The mobile terminal of claim 23, wherein the processor is further configured to receive cover type information from the cover.(String), 24.如权利要求23所述的移动终端,其中处理器还被配置为从封面接收封面类型信息。(String), 1(Integer), 23(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.521 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 25. The mobile terminal of claim 24, wherein the processor is further configured to check the cover type information and determine the first area and the second area of the touch screen according to the cover type information.(String), 25.如权利要求24所述的移动终端,其中处理器还用于检查覆盖物类型信息,并根据覆盖物类型信息确定触摸屏的第一区域和第二区域。(String), 1(Integer), 24(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.522 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 26. The mobile terminal of claim 24, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 26.如权利要求24所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 25(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.522 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 27. A cover for a mobile terminal, comprising:a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal; anda rear cover unit configured to cover a rear surface of the mobile terminal,wherein the front cover unit includes a transparent or semi-transparent window area and an opaque non-window area,a cover type information provider configured to provide cover type information to the mobile terminal, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover, andwherein the non-window area of the front cover unit includes an input area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of the front cover unit.(String), 27.一种移动终端的外壳,包括:前盖单元被配置为覆盖形成在移动终端的前表面上的触摸屏;和后盖单元,被配置为覆盖移动终端的后表面,其中,前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域,封面类型信息提供器,被配置为向移动终端提供封面类型信息,其中,封面类型信息包括关于封面的窗口区域的大小和位置中的至少一项的信息以及关于大小和位置中的至少一项的信息。盖子的非窗口区域的位置,以及其中,前盖单元的非窗口区域包括输入区域,输入区域包括配置为向移动终端应用多个不同的键输入的小键盘,并且当前盖单元覆盖移动终端的触摸屏时,通过非窗口区域的输入区域向触摸屏施加输入,其中键盘包括雕刻到或印刷在前盖单元的外表面上的多个有区别的键。(String), 0(Integer), 26(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.522 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 28. The cover of claim 27, wherein the front cover unit comprises a magnetic force applier configured to generate a magnetic force.(String), 28.权利要求27的覆盖物,其中前盖单元包括配置成产生磁力的磁力施加器。(String), 1(Integer), 27(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.522 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 29. The cover of claim 27, wherein the input applied through the non-window area is applied in a part of the non-window area visually distinguished from another part of the non-window area.(String), 29.权利要求27的覆盖物,其中通过非窗口区域施加的输入被施加在非窗口区域的一部分中,在视觉上与非窗口区域的另一部分区别开来。(String), 1(Integer), 28(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.523 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 30. The cover of claim 27, wherein at least a part of the non-window area is formed of at least one of conductive silicon, an anti-static electric material, and silver nylon.(String), 30.权利要求27的覆盖物,其中非窗口区域的至少一部分由导电硅、抗静电材料和银尼龙中的至少一种形成。(String), 1(Integer), 29(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.523 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 31. An article of manufacture for processing input in a mobile terminal, comprising a non-transitory machine readable medium containing one or more programs which when executed implement the steps of:identify a first area of a touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;activating touch sensing for the second area of the touch screen while the cover is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are of a same gesture type, andwherein the first control command and the second control command are different control command.(String), 31.一种用于处理移动终端输入的制品,包括包含一个或多个程序的非暂时性机器可读介质,这些程序在执行时执行以下步骤:通过接收来自外壳的信息识别移动终端的外壳的窗口区域对应的触摸屏的第一区域和外壳的非窗口区域对应的触摸屏的第二区域;检测触摸屏上方的移动终端盖板是否合上;当盖子关闭在触摸屏上方时,激活触摸屏的第二区域的触摸感应;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 30(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.776 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.776 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.777 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.777 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.780 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184951(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to a Korean patent application filed in the Korean Intellectual Property Office on Feb. 11, 2014 and assigned Serial No. 10-2014-0015272, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal, and more particularly, to a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal. [0004]2. Description of the Related Art [0005]Mobile terminals such as, for example, smartphones, Personal Computers (PCs), tablets, and the like, provide various useful functions to users through many applications. [0006]Such mobile terminals are evolving to enable users to use various types of information through the various functions. [0007]In general, a cover is configured so as to cover an entire display formed on the front surface of a mobile terminal. Since the screen of the display is covered with the cover, a user may not use the display screen. SUMMARY OF THE INVENTION [0008]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal, which even though the mobile terminal is covered with the cover, enable a user to view at least a part of a display screen of the mobile terminal. [0009]Another aspect of the present invention is to provide a mobile terminal, a UI method in the mobile terminal, and a cover of the mobile terminal, which provide a window area to show a part of a display screen of the mobile terminal when the cover covers the display screen of the mobile terminal and which enable a user to identify an area of the display screen corresponding to the window area of the cover so that display on the area corresponding to the window area of the cover may be controlled in various manners. [0010]In accordance with an aspect of the present invention, a method is provided for processing input in a mobile terminal. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined. A second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area is detected while the cover is closed over the touch screen. The first input is processed as a first control command. [0011]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a touch screen and a processor. The processor is configured to define a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, to define a second area of the touch screen corresponding to a non-window area of the cover, to detect a first input in the second area while the cover is closed over the touch screen, and to process the first input as a first control command. [0012]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a cover including a transparent or semi-transparent window area and an opaque non-window area, for covering a touch screen of the mobile terminal. The mobile terminal also includes a touch screen that includes a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover. The mobile terminal further includes a processor configured to control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the touch screen is covered with the cover. [0013]In accordance with another aspect of the present invention, a cover for a mobile terminal is provided that includes a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal. The cover also includes a rear cover unit configured to cover a rear surface of the mobile terminal. The front cover unit includes a transparent or semi-transparent window area and an opaque non-window area. The non-window area of the front cover unit includes an input area. and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area. [0014]In accordance with another aspect of the present invention, an article of manufacture is provided for processing input in a mobile terminal. The article of manufacture includes a machine readable medium containing one or more programs which when executed implement the steps of: defining a first area of the touch screen corresponding to a window area of a cover of the mobile terminal; defining a second area of the touch screen corresponding to a non-window area of the cover; detecting a first input in the second area while the cover is closed over the touch screen; and processing the first input as a first control command. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0016]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention; [0017]FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention; [0018]FIG. 2B is a diagram illustrating a rear surface of a cover of a mobile terminal, according to an embodiment of the present invention; [0019]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention; [0020]FIGS. 4A and 4B are diagrams illustrating configurations of a front cover unit, according to embodiments of the present invention; [0021]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention; [0022]FIG. 6 is a diagram illustrating an operation for determining whether a mobile terminal is covered with a cover, according to an embodiment of the present invention; [0023]FIG. 7 is a block diagram of a mobile terminal, according to an embodiment of the present invention; [0024]FIG. 8 is a flowchart illustrating a UI operation using a first area and a second area defined on a touch screen, respectively corresponding to a window area and a cover input area of a cover, in a mobile terminal, according to an embodiment of the present invention; [0025]FIGS. 9, 10, 11, and 12 are diagrams illustrating touch screen areas defined for various types of covers, according to embodiments of the present invention; [0026]FIG. 13 is a diagram illustrating touch inputs, according to an embodiment of the present invention; [0027]FIG. 14 is a flowchart illustrating an operation for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0028]FIGS. 15A and 15B are diagrams illustrating screens for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0029]FIG. 16 is a flowchart illustrating an operation for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0030]FIG. 17 is a diagram illustrating a screen for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0031]FIG. 18 is a flowchart illustrating an operation for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0032]FIGS. 19A, 19B, 20A, and 20B are diagrams illustrating screens for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0033]FIG. 21 is a flowchart illustrating an operation for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0034]FIGS. 22A, 22B, 23A, and 23B are diagrams illustrating screens for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0035]FIGS. 24A, 24B, and 24C are diagrams illustrating a cover having a keypad formed on it according to another embodiment of the present invention; [0036]FIG. 25 is a diagram illustrating a keypad formed on a front cover unit, according to an embodiment of the present invention; [0037]FIGS. 26A, 26B, and 26C are diagrams illustrating keys formed on a front cover unit, according to an embodiment of the present invention; [0038]FIGS. 27A and 27B are diagrams illustrating a full screen and a mini screen respectively, according to an embodiment of the present invention; [0039]FIGS. 28A, 28B, 28C, 28D, and 28E are diagrams illustrating mini screens of 1st to 5th types, respectively, according to an embodiment of the present invention; [0040]FIGS. 29A, 29B, 29C, 29D, and 29E are diagrams illustrating mini screens of 6th to 10th types, according to an embodiment of the present invention; [0041]FIGS. 30A and 30B are diagrams illustrating mini screens of 11th and 12th types, according to an embodiment of the present invention; [0042]FIG. 31 is a diagram illustrating a mini screen of a 13th type, according to an embodiment of the present invention; [0043]FIGS. 32A and 32B are diagrams illustrating a method for controlling display of a mini screen, according to an embodiment of the present invention; [0044]FIGS. 33A, 33B, 33C, 34A, 34B, 34C, 34D, and 34E are diagrams illustrating operations triggered by text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0045]FIGS. 35A, 35B, 35C, 35D, and 35E are diagrams illustrating operations triggered by different types of text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0046]FIGS. 36A, 36B, 36C, 36D, and 36E are diagrams illustrating an operation for performing a call function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0047]FIGS. 37A, 37B, and 37C are diagrams illustrating an operation for performing a message function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0048]FIGS. 38A, 38B, 38C, 38D, 38E, 38F, and 38G are diagrams illustrating operations for performing various application functions, upon selection of applications on a mini screen while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0049]FIGS. 39A and 39B are diagrams illustrating an application requiring a text input, according to an embodiment of the present invention; and [0050]FIGS. 40A and 40B are diagrams illustrating a cover open request message displayed while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0051]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0052]The terms and words used in the following description are not limited to the meanings provided in a standard dictionary, but, are merely used to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the disclosure. [0053]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0054]Use of the term “substantially” means that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those of skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide. [0055]A mobile terminal according to various embodiments of the present invention may be embodied as an electronic device equipped with a display, such as, for example, a touch screen that can be covered with a cover. For example, the mobile terminal may be any of a video phone, a mobile phone, a smartphone, an International Mobile Telecommunication 2000 (IMT 2000) terminal, a Wideband Code Division Multiple Access (WCDMA) terminal, a Universal Mobile Telecommunication System (UMTS) terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a Digital Multimedia Broadcasting (DMB) terminal, an e-book reader, a laptop Personal Computer (PC), a tablet PC, a digital camera, and the like. [0056]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention. FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention. FIG. 2B is a diagram illustrating the rear surface of a cover of a mobile terminal, according to an embodiment of the present invention. [0057]Referring to FIGS. 1A, 1B, 2A, and 2B, a mobile terminal 100 may be engaged with a cover 200. A display device that displays screens for multiple functions, for example, a touch screen 140 is provided on a front surface of the mobile terminal 100. A bezel 102 is formed around at least a part of the periphery of the touch screen 140 on the front surface of the mobile terminal 100. A home button 105, a speaker, a camera, a sensor, and the like, may be formed in the bezel 102. A battery 170 is mounted on a rear surface of the mobile terminal 100 to supply power to the mobile terminal 100. The battery 170 may be detachably formed on the rear surface of the mobile terminal 100, or may be built in the mobile terminal 100 so that a user may not remove the battery 170 from the mobile terminal 100. A rear cover unit 220 is provided on the rear surface of the mobile terminal 100. Connection ports 180 are provided on the rear surface of the mobile terminal 100, inside the rear cover unit 220, for electrical connection. The rear cover unit 220 is able to be engaged with the rear surface of the mobile terminal 100, covering the battery 170. The cover 200 is configured to cover at least a part of the front surface of the mobile terminal 100. When the cover 200 covers the front surface of the mobile terminal 100, a front cover unit 210 covers at least a part of the touch screen 140. Further, when the cover 200 covers the front surface of the mobile terminal 100, the front cover unit 210 covers at least a part of the bezel 102. When the front cover unit 210 covers at least a part of the touch screen 140, the remaining part of the touch screen 140 is exposed outwardly through a window area 201a formed in the front cover unit 210. The mobile terminal 100 may control display of content such as, for example, a clock, text, a number, a caller number, a user environment setting, or the like, in the part of the touch screen 140 exposed through the window area 201a of the front cover unit 210. [0058]The front cover unit 210 of the cover 200 may be flipped open or closed. When the front cover unit 210 of the cover 200 is opened, the entire area of the touch screen 140 of the mobile terminal 100 is exposed outward, as illustrated in FIG. 1A. If the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 of the mobile terminal 100 is covered with the front cover unit 210, as illustrated in FIG. 1B. Referring to FIG. 1B, when the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 corresponding to the window area 201a is exposed outward, while the remaining part of the touch screen 140 is covered. [0059]Further, when the front cover unit 210 of the cover 200 is closed, a part (for example, a speaker) formed in the bezel 102 of the mobile terminal 100 is exposed outwardly through an opening 201b formed in the front cover unit 210. While only one opening 201b is shown in FIG. 1B, a plurality of openings may be formed in the front cover unit 210 so that even though the front cover unit 210 is closed, a plurality of parts (for example, a speaker, a camera, and the like) formed in the bezel 102 may be exposed outwardly through the plurality of openings. [0060]Referring to FIGS. 2A and 2B, the cover 200 includes the front cover unit 210 and the rear cover unit 220. The cover 200 further includes a connection unit 203 interposed between the front cover unit 210 and the rear cover unit 220, for connecting the front cover unit 210 to the rear cover unit 220. The connection unit 203 may cover a part of a side surface of the mobile terminal 100. [0061]The front cover unit 210 covers the front surface of the mobile terminal 100 and includes the window area, or screen projector, 201a to expose a part of the touch screen 140. The window area 201a may be formed of a transparent or semi-transparent material or may be formed into an opening in the front cover unit 210 so that when the cover 200 covers the front surface of the mobile terminal 100, a user may view information displayed on the touch screen 140 through the window area 201a. Accordingly, the user may view information displayed on the touch screen 140 inside the front cover unit 210 through the window area 201a from outside of the front cover unit 210. Therefore, even though the front cover unit 210 is closed, the user may view short information displayed on the touch screen 140 through the window area 201a and may enter a user command through the front cover unit 210 to execute a function related to the displayed information. The rear cover unit 220 is formed as a battery cover 220a in FIG. 2B, by way of example. Referring to FIG. 2B, the rear cover unit 220 covers the rear surface of the mobile terminal 100. The rear cover unit 220 may be mounted fixedly or detachably on the rear surface of the mobile terminal 100. The front cover unit 210 may be connected to a side surface of the rear cover unit 220. The connection unit 203 may be formed between the front cover unit 210 and the rear cover unit 220. In this case, the connection unit 203 may have one side surface connected to a side surface of the rear cover unit 220 and the other side surface connected to a side surface of the front cover unit 210. The rear cover unit 220 and the front cover unit 210 may be bent upon the connection unit 203. The rear cover unit 220 is engaged with the rear surface of the mobile terminal 100. When the front cover unit 210 is flipped closed, the rear cover unit 220 surrounds at least a part of a side surface of the mobile terminal 100. Thus, the mobile terminal 100 may not slip off from the cover 200. In addition, a connector unit 202a is formed in the rear cover unit 220. The connector unit 202a provides cover type information about the cover 200. The cover type information may include information about the position of a window area and an input area formed in the front cover unit 210 of the cover 200. The connector unit 202a may provide the cover type information about the cover 200 to the mobile terminal 100 by electrically connecting to the connection ports 180 formed on the rear surface of the mobile terminal 100. For example, a plurality of connection ports 181 and 182 may be formed on the rear surface of the mobile terminal 100. The connector unit 202a of the cover 200 may be electrically engaged with at least one of the connection ports 181 and 182. The mobile terminal 100 may identify the type of the cover 200 depending on whether the connector unit 202a of the cover 200 is connected to both or one of the connection ports 181 and 182. In another example, irrespective of which connection port the connector unit 202a of the cover 200 is connected to, the mobile terminal 100 may identify the type of the cover 200. [0062]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention. [0063]In FIG. 3, the rear cover unit 220 is formed as a rear case 220b. Referring to FIG. 3, the cover 200 includes the front cover unit 210, the connection unit 203, and the rear case 220b. The mobile terminal 100 may be fixedly inserted in the rear case 220b. The mobile terminal 100 with a battery cover 220a engaged with its rear surface may be inserted in the rear case 220b. [0064]The rear case 220b includes a base 221, at least one sidewall 222 formed along the periphery of the base 221, and a catching portion 223. The sidewall 222 is formed substantially straight up and perpendicular from the plane of the base 221. A bottom of the sidewall 220 is connected to the base 221 and the catching portion 223 is formed in an upper end of the sidewall 222. An inner space defined by the base 221 and the sidewall 222 has a size and a shape corresponding to the size and shape of the mobile terminal 100. If the mobile terminal 100 is accommodated in the inner space, the catching portion 223 may prevent slip-off of the mobile terminal 100 from the inner space. The front cover unit 210 is connected to one side surface of the rear case 220b. The connection unit 203 may be formed between the front cover unit 210 and the rear case 220b. In this case, the connection unit 203 has one side surface connected to a side surface of the rear case 220b and the other side surface connected to a side surface of the front cover unit 210. The rear case 220b and the front cover unit 210 may be bent upon the connection unit 203. [0065]If the window area 201a and the input area 201b are formed at predetermined positions on the front cover unit 210 of the cover 200, when the cover 200 is closed, the mobile terminal 100 may display information through the window area 201a and receive a user input through the input area 201b despite having no knowledge of cover type information about the cover 200. [0066]In an embodiment of the present invention, a cover type information transmitter 224 may further be formed in the cover 200 for providing cover type information about the cover 200 to the mobile terminal 100 via short-range communication. The cover type information transmitter 224 may transmit the cover type information about the cover 200 to the mobile terminal 100 by a short-range communication scheme such as, for example, Near Field Communication (NFC), Radio Frequency Identification (RFID), Bluetooth, Wireless Fidelity (WiFi) Direct, or the like. The mobile terminal 100 may then identify the type of the cover 200 based on the cover type information received from the cover 100 by the short-range communication scheme. [0067]While it has been described above, with reference to FIG. 3, that the rear cover unit 220 of the cover 200 is configured as a case, the shapes of the rear cover unit 220 and the connection unit 203 may be changed as long as the front cover unit 210 is detachably mounted to the mobile terminal 100 and flipped open or closed. [0068]FIGS. 4A and 4B are diagrams illustrating configurations of the front cover unit, according to embodiments of the present invention. FIG. 4A illustrates the window area 201a formed of a transparent or semi-transparent material in the front cover unit 210, and FIG. 4B illustrates the window area 201a formed into a cutout opening in the front cover unit 210. [0069]Referring to FIG. 4A, the front cover unit 210 includes an outer member 211a, an inner member 212a, and a transparent member 213a. The outer member 211a, which forms an outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. An outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms an inner surface of the front cover unit 210, is engaged with a bottom surface of the transparent member 213a, while a bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. An inner hole 2121 is formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The transparent member 213a is interposed between the outer member 211a and the inner member 212a and brings the outer hole 2111 and the inner hole 212 into close contact. A first area defined at a predetermined position of the touch screen 140, for example, in an upper part of the touch screen 140 may be exposed outwardly through the transparent member 213a, the outer hole 2111, and the inner hole 2121. That is, even though the first area of the touch screen 140 is covered with the front cover unit 210, the transparent member 213a may be formed of a material containing a transparent or semi-transparent material so that the user may view information displayed in the first area of the touch screen 140 through the window area 201a. For example, the transparent member 213a may be formed of a transparent or semi-transparent film. The transparent member 213a is larger is size than the window area 201a. In FIG. 4A, the transparent member 213a is as large as the outer member 211a and the inner member 212a. The transparent member 213a may be formed of a material containing a conductive material such as, for example, conductive silicon. Further, the outer member 211a, the inner member 212a, and the transparent member 213a may be formed of a material containing at least one of an anti-static electricity material, silver, and nylon fabric. Accordingly, upon receipt of a touch input in the window area 201a from the user, the touch input may be sensed in the first area of the touch screen 140 corresponding to the window area 201a. For example, when a call is incoming, a notification indicating the call incoming is displayed at a position of the touch screen 140 corresponding to the window area 201a. If the user touches the window area 201a or manipulates a predetermined key, for example, a side key, the call may be connected immediately. [0070]Referring to FIG. 4B, the front cover unit 210 includes the outer member 211a and the inner member 212a to define the window area 201a and cover the touch screen 140, for protection. The outer member 211a, which forms the outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. The outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms the inner surface of the front cover unit 210, is engaged with a bottom surface of the outer member 211a, while the bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. The inner hole 2121 may be formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The outer hole 2111 and the inner hole 2121 are formed having the same size. An opening formed by the outer hole 2111 and the inner hole 2121 may form the window area 201a. Therefore, even though the first area of the touch screen 140 is covered with the front cover unit 210, the user may view information displayed on the touch screen 140 through the opening of the window area 201a. Further, the user may apply a touch input to the touch screen 140 through the window area 201a. Then the mobile terminal 100 may sense the touch input in the first area of the touch screen 140 corresponding to the window area 201a. [0071]In an embodiment of the present invention, the remaining area of the front cover unit 210, except the window area 201a, is a non-window area. At least a part of the non-window area may be defined as an input area (hereinafter, referred to as a ‘cover input area’) in which a user input may be applied. For example, the whole non-window area may be the cover input area. Or a predetermined part of the non-window area may be the cover input area. The cover input area may refer to an area in which a touch input on the outer surface of the outer member 211a can be detected by the touch screen 140, with the front cover unit 210 covering the touch screen 140. Therefore, a user gesture made in the cover input area corresponding to at least a part of the non-window area may be sensed by the touch screen 140. [0072]For example, when the user makes a user gesture in the cover input area of the front cover unit 210, the user gesture may be sensed in a second area of the touch screen 140 corresponding to the cover input area. In various embodiments of the present invention, the window area 201a of the front cover unit 210 may be formed in a first cover area of the front cover unit 210 and the non-window area may be formed in a second cover area other than the first cover area in the front cover unit 210. [0073]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention. [0074]Referring to FIG. 5A, a window area 511 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 511, is defined as a non-window area 521 in a first-type cover, according to an embodiment of the present invention. The whole non-window area 521 may be a cover input area in the first-type cover. [0075]Referring to FIG. 5B, a window area 512 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 512, is defined as the non-window area 521 in a second-type cover, according to an embodiment of the present invention. In the second-type cover, an area of a predetermined size in the non-window area 521 under the window area 512 may be defined as a cover input area 522. In FIG. 5B, the cover input area 522 may be substantially as wide as the window area 512 along a horizontal direction and may extend up to the vicinity of the window area 512 and down to the vicinity of a bottom end of the front cover unit 210. Accordingly, for example, the cover input area 522 may occupy most of the non-window area 521 under the window area 512. [0076]Referring to FIG. 5C, a window area 513 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 513, is defined as the non-window area 521 in a third-type cover, according to an embodiment the present invention. In the third-type cover, a small area at a center of the non-(String), 优先 [0001] 本申请根据 35 U.S.C. § 119(a) 于 2014 年 2 月 11 日向韩国知识产权局提交并转让序列号 10-2014-0015272 的韩国专利申请,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及一种移动终端,更具体地,涉及一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳。 [0004] 2.相关技术的描述 [0005] 诸如智能手机、个人计算机(PC)、平板电脑等的移动终端通过许多应用程序向用户提供各种有用的功能。 [0006] 这样的移动终端正在发展以使用户能够通过各种功能使用各种类型的信息。 [0007] 通常,盖被配置为覆盖形成在移动终端的前表面上的整个显示器。 由于显示器的屏幕被覆盖物覆盖,用户可能不使用显示屏幕。 发明内容 [0008] 做出本发明以至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面提供了一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳,即使移动终端被外壳覆盖,也使得用户能够查看 移动终端的显示屏的至少一部分。 [0009] 本发明的另一方面在于提供一种移动终端、移动终端中的UI方法以及移动终端的封面,当封面覆盖时,提供窗口区域以显示移动终端的显示屏幕的一部分。 移动终端的显示屏,使用户能够识别与封面的窗口区域对应的显示屏的区域,从而可以以各种方式控制在与封面的窗口区域对应的区域上的显示。 [0010] 根据本发明的一个方面,提供了一种用于在移动终端中处理输入的方法。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域。 定义了移动终端的触摸屏上与封面的非窗口区域对应的第二区域。 当盖子在触摸屏上关闭时,检测到第二区域中的第一输入。 第一输入被处理为第一控制命令。 [0011] 根据本发明的另一方面,提供了一种包括触摸屏和处理器的移动终端。 处理器用于定义触摸屏的第一区域对应于移动终端的封面的窗口区域, 定义触摸屏的第二区域对应于封面的非窗口区域, 检测第一 合上触摸屏时在第二区域输入,并将第一输入处理为第一控制命令。 [0012] 根据本发明的另一方面,提供了一种移动终端,其包括用于覆盖移动终端的触摸屏的覆盖物,该覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域。 该移动终端还包括触摸屏,该触摸屏包括与封面的窗口区域对应的第一区域和与封面的非窗口区域对应的第二区域。 移动终端还包括处理器,被配置为根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时触摸屏被覆盖物覆盖。 [0013]根据本发明的另一方面,提供了一种用于移动终端的盖,其包括被配置为覆盖形成在移动终端的前表面上的触摸屏的前盖单元。 盖还包括被配置为覆盖移动终端的后表面的后盖单元。 前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域。 前盖单元的非窗口区域包括输入区域。 在前盖单元覆盖移动终端的触摸屏的同时,通过非窗口区域的输入区域对触摸屏进行输入。 [0014] 根据本发明的另一方面,提供了一种用于处理移动终端中的输入的制品。 所述制品包括包含一个或多个程序的机器可读介质,所述程序在执行时实现以下步骤: 定义与移动终端的封面的窗口区域相对应的触摸屏的第一区域; 定义触摸屏的第二区域,对应于盖板的非窗口区域; 当盖板合上触摸屏时,检测第二区域中的第一输入; 处理第一输入作为第一控制命令。 附图的简要说明 [0015] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0016] 图 附图说明图1A和图1B是示出了根据本发明实施例的与盖子接合的移动终端的外部透视图; [0017] 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图; [0018] 如图。 图2B是示出根据本发明实施例的移动终端机盖的背面的图; [0019] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图; [0020] 图 图4A和4B是示出根据本发明实施例的前盖单元的构造的图; [0021] 图 图5A、5B、5C和5D是示出根据本发明实施例的各种类型的盖的图; [0022] 如图。 图6是说明根据本发明的一个实施例的确定移动终端是否被覆盖物覆盖的操作的图。 [0023] 如图。 图7是根据本发明实施例的移动终端的框图; [0024] 如图。 图8是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的分别对应于封面的窗口区域和封面输入区域的第一区域和第二区域的UI操作的流程图 ; [0025] 图 图9、10、11和12是示出根据本发明实施例的为各种类型的封面定义的触摸屏区域的图; [0026] 如图。 图13是说明根据本发明的实施例的触摸输入的图; [0027] 如图。 图14是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制音乐播放信息的操作的流程图; [0028] 图 图15A和15B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制音乐播放信息的屏幕的图; [0029] 如图。 图16是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的操作的流程图; [0030] 如图。 图17是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的屏幕的图; [0031]如图。 图18是示出根据本发明实施例的使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的操作的流程图; [0032] 图 图19A、19B、20A和20B是示出了根据本发明的实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的屏幕的图; [0033] 如图。 图21是示出根据本发明的实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制应用程序的操作的流程图; [0034] 图 图22A、22B、23A和23B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制应用的屏幕的图; [0035] 图 图24A、24B和24C是示出根据本发明另一实施例的具有形成在其上的小键盘的盖的图; [0036] 如图。 图25是示出根据本发明实施例的形成在前盖单元上的小键盘的图; [0037] 图 图26A、26B和26C是图示根据本发明实施例的形成在前盖单元上的键的图; [0038] 图 图27A和27B是分别示出了根据本发明实施例的全屏和小屏幕的图; [0039] 图 图28A、28B、28C、28D和28E是图解1的迷你屏幕的图。 st 到 5 th 分别根据本发明的一个实施例的类型; [0040] 图 图29A、29B、29C、29D和29E是图解说明6的迷你屏幕的图 th 到 10 th 类型,根据本发明的一个实施例; [0041] 图 图30A和30B是图解说明11的迷你屏幕的图 th 和 12 th 类型,根据本发明的一个实施例; [0042] 如图。 图31是说明13的小屏幕的图 th 类型,根据本发明的一个实施例; [0043] 图 图32A和32B是图示根据本发明实施例的用于控制迷你屏幕的显示的方法的图; [0044] 图 图33A、33B、33C、34A、34B、34C、34D和34E是示出根据本发明实施例的通过移动终端中的封面单元的小键盘由文本输入触发的操作的图; [0045] 图 图35A、35B、35C、35D和35E是图示根据本发明实施例的通过移动终端中的封面单元的键盘的不同类型的文本输入触发的操作的图; [0046] 图 图36A、36B、36C、36D和36E是示出在移动终端中在前盖单元关闭的同时通过前盖单元的小屏幕或键盘接收输入时执行呼叫功能的操作的图 ,根据本发明的一个实施例; [0047] 图 图37A、图37B和图37C是示出在移动终端中前盖单元关闭时,在通过前盖单元的小屏幕或键盘接收输入时执行消息功能的操作的图。 本发明的实施例; [0048] 图 图38A、图38B、图38C、图38D、​​图38E、图38F和图38G是示出根据本发明实施例的在移动终端中在前盖单元关闭的同时在迷你屏幕上选择应用时执行各种应用功能的操作的图。 本发明; [0049] 图 图39A和39B是图示根据本发明实施例的需要文本输入的应用程序的图; 和 [0050] 图 图40A和40B是示出根据本发明实施例的在移动终端中前盖单元关闭时显示的盖打开请求消息的图。 本发明实施方案的详细说明 [0051]下面结合附图对本发明实施例进行详细描述。 尽管它们在不同的附图中示出,但是相同或相似的部件可以用相同或相似的附图标记表示。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0052] 以下描述中使用的术语和词语不限于标准字典中提供的含义,而仅用于使本公开内容能够清晰一致地理解。 因此,本领域技术人员应该清楚,提供本发明实施例的以下描述仅用于说明目的,而不是用于限制本公开的目的。 [0053] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0054] 使用术语“基本上”是指不需要精确地实现所列举的特性、参数或值,而是偏差或变化,包括例如公差、测量误差、测量精度限制和本领域技术人员已知的其他因素。 该技术可能以不排除该特性旨在提供的效果的数量出现。 [0055] 根据本发明的各种实施例的移动终端可以被实施为配备有显示器的电子设备,例如,可以用盖子覆盖的触摸屏。 例如,移动终端可以是可视电话、移动电话、智能手机、国际移动电信2000(IMT 2000)终端、宽带码分多址(WCDMA)终端、通用移动电信系统(UMTS)中的任何一种。 ) 终端、个人数字助理 (PDA)、便携式多媒体播放器 (PMP)、数字多媒体广播 (DMB) 终端、电子书阅读器、膝上型个人电脑 (PC)、平板电脑、数码相机、 之类的。 [0056] 图 图1A和1B是示出根据本发明实施例的与盖接合的移动终端的外部透视图的图。 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图。 如图。 图2B是图示根据本发明实施例的移动终端的盖的后表面的图。 [0057] 参考图。 参考图1A、1B、2A和2B,移动终端 100 可能与盖子接合 200 . 显示多种功能的屏幕的显示设备,例如触摸屏 140 设置在移动终端的正面 100 . 一个挡板 102 围绕触摸屏的外围的至少一部分形成 140 在移动终端的正面 100 . 一个主页按钮 105 、扬声器、照相机、传感器等可以形成在边框中 102 . 一块电池 170 安装在移动终端的背面 100 给移动终端供电 100 . 电池 170 可以可拆卸地形成在移动终端的背面 100 ,或者可以内置在移动端 100 以免用户取出电池 170 从移动终端 100 . 后盖单元 220 设置在移动终端的背面 100 . 连接端口 180 设置在移动终端的背面 100 , 后盖单元内部 220 , 用于电气连接。 后盖单元 220 能够与移动终端的背面接合 100 , 覆盖电池 170 . 封面 200 被配置为覆盖移动终端的前表面的至少一部分 100 . 当封面 200 覆盖移动终端的正面 100 , 一个前盖单元 210 至少覆盖触摸屏的一部分 140 . 此外,当封面 200覆盖移动终端的正面 100 , 前盖单元 210 至少覆盖挡板的一部分 102 . 当前盖单元 210 至少覆盖触摸屏的一部分 140 ,触摸屏的剩余部分 140 通过窗口区域向外暴露 201 a 形成在前盖单元中 210 . 移动终端 100 可以控制内容的显示,例如时钟、文本、数字、呼叫者号码、用户环境设置等,在触摸屏的部分中 140 通过窗口区域暴露 201 a 前盖单元的 210 . [0058] 前盖单元 210 封面的 200 可以翻转打开或关闭。 当前盖单元 210 封面的 200 打开时,触摸屏的整个区域 140 移动终端的 100 外露,如图所示。 1A。 如果前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 移动终端的 100 被前盖单元盖住 210 ,如图所示。 1B。 参考图。 1B、当前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 对应窗口区域 201 a 外露,而触摸屏的其余部分 140 被覆盖。 [0059] 此外,当前盖单元 210 封面的 200 封闭,形成在边框中的一部分(例如,扬声器) 102 移动终端的 100 通过开口向外暴露 201 b 形成在前盖单元中 210 . 虽然只有一个开口 201 b 如图所示。 如图1B所示,可以在前盖单元中形成多个开口 210 这样即使前盖单元 210 封闭,在边框中形成多个部件(例如,扬声器、相机等) 102 可以通过多个开口向外暴露。 [0060] 参考图。 2A和2B,盖 200 包括前盖单元 210 和后盖单元 220 . 封面 200 还包括连接单元 203 夹在前盖单元之间 210 和后盖单元 220 , 用于连接前盖单元 210 到后盖单元 220 . 连接单元 203 可以覆盖移动终端侧面的一部分 100 . [0061] 前盖单元 210 覆盖移动终端的正面 100 并包括窗口区域或屏幕投影仪, 201 a 露出触摸屏的一部分 140 . 窗口区域 201 a 可以由透明或半透明材料形成,或者可以形成在前盖单元中的开口中 210 这样当封面 200 覆盖移动终端的正面 100 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域 201 a . 因此,用户可以查看显示在触摸屏上的信息 140 前盖单元内部 210 通过窗口区域 201 a 从前盖单元外部 210 . 因此,即使前盖单元 210 关闭时,用户可以查看触摸屏上显示的简短信息 140 通过窗口区域 201 a 并且可以通过前盖单元输入用户命令 210 执行与显示信息相关的功能。 后盖单元 220 形成为电池盖 220 a 在图 例如,图2B。 参考图。 2B、后盖单元 220 覆盖移动终端的背面 100 . 后盖单元 220 可以固定或可拆卸地安装在移动终端的背面 100 . 前盖单元 210 可以连接到后盖单元的侧表面220 . 连接单元 203 可以形成在前盖单元之间 210 和后盖单元 220 . 在这种情况下,连接单元 203 可以具有连接到后盖单元的侧表面的一个侧表面 220 另一个侧面连接到前盖单元的侧面 210 . 后盖单元 220 和前盖单元 210 可能弯曲在连接单元上 203 . 后盖单元 220 与移动终端的背面接合 100 . 当前盖单元 210 翻转关闭,后盖单元 220 包围移动终端的侧表面的至少一部分 100 . 因此,移动终端 100 不能从封面上滑落 200 . 此外,连接器单元 202 a 形成在后盖单元中 220 . 连接器单元 202 a 提供有关封面的封面类型信息 200 . 封面类型信息可以包括关于形成在前封面单元中的窗口区域和输入区域的位置的信息 210 封面的 200 . 连接器单元 202 a 可以提供关于封面的封面类型信息 200 到移动终端 100 通过电连接到连接端口 180 形成在移动终端的背面 100 . 例如,多个连接端口 181 和 182 可以形成在移动终端的背面 100 . 连接器单元 202 a 封面的 200 可以与至少一个连接端口电接合 181 和 182 . 移动终端 100 可以识别封面的类型 200 取决于连接器单元是否 202 a 封面的 200 连接到两个或一个连接端口 181 和 182 . 在另一个示例中,无论连接器单元是哪个连接端口 202 a 封面的 200 连接到移动终端 100 可以识别封面的类型 200 . [0062] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图。 [0063] 在图。 3、后盖单元 220 形成为后壳 220 b . 参考图。 3、封面 200 包括前盖单元 210 , 连接单元 203 , 和后壳 220 b . 移动终端 100 可固定插入后壳 220 b . 移动终端 100 带电池盖 220 a 与其后表面啮合可以插入后壳 220 b. [0064] 后壳 220 b 包括一个基地 221 , 至少一个侧壁 222 沿底座周边形成 221 , 和一个捕捉部分 223 . 侧壁 222 形成为基本上笔直向上并垂直于基部的平面 221 . 侧壁的底部 220 连接到底座 221 和捕捉部分 223 形成于侧壁的上端 222 . 由底座定义的内部空间 221 和侧壁 222 具有与移动终端的大小和形状相对应的大小和形状 100 . 如果移动端 100 容纳在内部空间中的抓持部分 223 可防止移动终端滑落 100 从内部空间。 前盖单元 210 连接到后壳的一侧表面 220 b . 连接单元 203 可以形成在前盖单元之间 210 和后壳 220 b . 在这种情况下,连接单元 203 具有连接到后壳的侧面的一个侧面 220 b 另一个侧面连接到前盖单元的侧面 210 . 后壳 220 b 和前盖单元 210 可能弯曲在连接单元上 203 . [0065] 如果窗口区域 201 a 和输入区域 201 b 形成在前盖单元上的预定位置 210 封面的 200 , 当覆盖 200 关闭,移动端 100 可以通过窗口区域显示信息 201 a 并通过输入区域接收用户输入 201 b 尽管不知道关于封面的封面类型信息 200 . [0066] 在本发明的一个实施例中,一种覆盖式信息发送器 224 可以进一步形成在盖中 200 用于提供有关封面的封面类型信息 200 到移动终端 100 通过短距离通信。 盖式信息发射器 224 可以传输关于封面的封面类型信息 200 到移动终端 100 通过短距离通信方案,例如近场通信(NFC)、射频识别(RFID)、蓝牙、无线保真(WiFi) Direct等。 移动终端 100 然后可以识别封面的类型 200 基于从封面收到的封面类型信息 100 通过短距离通信方案。 [0067] 虽然上面已经描述了,但参考图1。 3、即后盖单元 220 封面的 200 配置为外壳,后盖单元的形状 220 和连接单元 203 只要前盖单元可以更改 210 可拆卸地安装在移动终端上 100 并翻转打开或关闭。 [0068] 图 图4A和4B是图示根据本发明实施例的前盖单元的配置的图。 如图。 图4A说明了窗口区域 201 a 在前盖单元中由透明或半透明材料制成 210 ,和图。 图4B图示了窗口区域 201 a 在前盖单元中形成一个切口 210 . [0069] 参考图。 4A、前盖单元 210 包括一个外部成员 211 a , 一个内部成员 212 a , 和一个透明的成员 213 a . 外部成员 211 a ,其形成前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 一个外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,其形成前盖单元的内表面 210 ,与透明构件的底面接合 213 a ,而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 一个内孔 2121 形成在内构件的位置 212 a 对应外孔 2111 , 定义窗口区域 201 a . 透明成员 213 a 夹在外构件之间 211 a 和内部成员 212 a 并带来外孔 2111 和内孔 212 密切接触。 第一区域定义在触摸屏的预定位置 140 ,例如,在触摸屏的上部 140 可以通过透明构件向外暴露 213 a , 外孔 2111 , 和内孔 2121 . 也就是说,即使触摸屏的第一个区域 140被前盖单元盖住 210 , 透明构件 213 a 可以由包含透明或半透明材料的材料形成,以便用户可以查看显示在触摸屏的第一区域中的信息 140 通过窗口区域 201 a . 例如,透明构件 213 a 可以由透明或半透明膜形成。 透明成员 213 a 大于窗口区域的大小 201 a . 在图。 4A、透明件 213 a 与外部成员一样大 211 a 和内部成员 212 a . 透明成员 213 a 可以由包含导电材料的材料形成,例如导电硅。 此外,外部构件 211 a , 内部成员 212 a , 和透明构件 213 a 可以由包含抗静电材料、银和尼龙织物中的至少一种的材料形成。 因此,当在窗口区域中接收到触摸输入时 201 a 来自用户的触摸输入可以在触摸屏的第一区域中被感测到 140 对应窗口区域 201 a . 例如,当有来电时,在触摸屏的位置显示来电的通知 140 对应窗口区域 201 a . 如果用户触摸窗口区域 201 a 或者操作预定键,例如侧键,可以立即接通通话。 [0070] 参考图。 4B、前盖单元 210 包括外部成员 211 a 和内部成员 212 a 定义窗口区域 201 a 并覆盖触摸屏 140 ,为了保护。 外部成员 211 a ,它形成了前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,它形成前盖单元的内表面 210 ,与外构件的底面接合 211 a , 而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 内孔 2121 可以形成在内部构件的位置处 212 a 对应外孔 2111 , 定义窗口区域 201 a . 外孔 2111 和内孔 2121 形成具有相同的尺寸。 由外孔形成的开口 2111 和内孔 2121 可以形成窗口区域 201 a . 因此,即使触摸屏的第一区域 140 被前盖单元盖住 210 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域的开口 201 a . 此外,用户可以将触摸输入应用到触摸屏 140 通过窗口区域 201 a . 然后是移动端 100 可以感应触摸屏第一区域的触摸输入 140 对应窗口区域 201 a. [0071] 在本发明的一个实施例中,前盖单元的剩余区域 210 , 除了窗口区域 201 a, 是非窗口区域。 非窗口区域的至少一部分可以被定义为可以应用用户输入的输入区域(以下称为“覆盖输入区域”)。 例如,整个非窗口区域可以是封面输入区域。 或者,非窗口区域的预定部分可以是封面输入区域。 覆盖输入区域可以是指在外部构件的外表面上进行触摸输入的区域 211 a 可通过触摸屏检测 140 , 带前盖单元 210 覆盖触摸屏 140 . 因此,在对应于至少部分非窗口区域的覆盖输入区域中做出的用户手势可以被触摸屏感测到 140 . [0072] 例如,当用户在封面单元的封面输入区域中做出用户手势时 210 ,可以在触摸屏的第二区域中感测到用户手势 140 对应于封面输入区域。 在本发明的各个实施例中,窗口区域 201 a 前盖单元的 210 可以形成在前盖单元的第一盖区域中 210 并且非窗口区域可以形成在前盖单元中除第一覆盖区域之外的第二覆盖区域中 210 . [0073] 图 图5A、5B、5C和5D是图示根据本发明实施例的各种类型的盖的图。 [0074] 参考图。 5A、窗口区域 511 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 511 , 定义为非窗口区域 521 在根据本发明的一个实施例的第一种盖子中。 整个非窗口区域 521 可以是第一类封面中的封面输入区域。 [0075] 参考图。 5B、窗口区域 512 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 512 , 定义为非窗口区域 521 在根据本发明的一个实施例的第二种盖中。 在第二种盖板中,非窗区域中的预定大小的区域 521 窗下区域 512 可以定义为一个覆盖输入区域 522 . 在图。 5B、覆盖输入区域 522 可以基本上与窗口区域一样宽 512 沿水平方向并可能延伸到窗口区域附近 512 并向下至前盖单元的底端附近 210 . 因此,例如,封面输入区域 522 可能占据大部分非窗口区域 521 窗下区域 512 . [0076] 参考图。 5C、窗口区域 513 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 513 , 定义为非窗口区域 521 在根据本发明的一个实施例的第三种盖子中。 第三种封面中,非窗口区域中心的一小块区域 521 窗下区域 513 可以定义为一个覆盖输入区域 523 . 封面输入区 523 在第三类覆盖中小于覆盖输入区域 522 以第二类封面为例。 [0077] 参考图。 5D,一个窗口区域 514 在前盖单元的右侧部分拉长 210 沿前盖单元的长度方向 210 ,以及前盖单元的剩余区域 210 , 除了窗口区域 514 , 定义为非窗口区域 521 在根据本发明的实施例的第四类盖中。 封面输入区 524 在非窗口区域的一部分定义 521 在窗口区域的左侧 514 . [0078] 而单个窗口区域 511 , 512 , 513 , 和 514 形成在前盖单元中 210在图 参照图5A、5B、5C和5D,作为示例,可以改变窗口区域的位置或数量。 例如,窗口区域 511 , 512 , 513 , 和 514 可以设置在前盖单元的中心 210 或者可以沿水平方向拉长。 因此窗口区域的位置 511 , 512 , 513 , 和 514 可能会有所不同。 虽然已经描述了在前盖单元中定义了一个窗口区域 210 在本发明的实施例中,可以在前盖单元中定义多个窗口区域 210 ,根据本发明的各种实施例。 此外,至少一部分非窗口区域 521 可用作覆盖输入区域。 例如,整个或部分非窗口区域 521 可以定义为覆盖输入区域。 在覆盖输入区域中进行的用户手势(例如,触摸输入)的输入时,可以在触摸屏的第二区域中检测到用户手势 140 对应于封面输入区域。 [0079] 移动终端 100 可以将窗口区域与封面单元中的封面输入区域区分开来 210 ,根据上述各种类型的封面。 因此,移动端 100 可以定义触摸屏上的第一和第二区域 140 对应前盖单元的窗口区域和封面输入区域 210 , 分别。 [0080] 在本发明的各个实施例中,前盖单元 210 移动终端的 100 可能会覆盖触摸屏 140 在移动终端的正面 100 和移动终端 100 可判断是否触摸屏 140 已被前盖单元盖住 210 . [0081] 如图。 图6是示出根据本发明实施例的用于确定移动终端是否被覆盖物覆盖的操作的图。 [0082] 参考图。 6、封面 200 包括一个磁力施加器 691 , 在前盖单元的内部 210 ,提供有关封面的封面类型信息 200 . [0083] 磁力施加器 691 例如,可以是永磁体并且可以施加磁力。 磁力施加器 691 可以产生对应于封面类型信息的磁力。 [0084] 例如,如果前盖单元 210 覆盖移动终端的正面 100 , 一个传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 , 和移动终端 100 可确定前盖单元是否 210 已经覆盖了移动终端的正面 100 基于磁力传感器的传感结果 692 传感器单元 160 . 此外,当前盖单元 210 覆盖移动终端的正面 100 , 传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 对应封面类型信息,移动端 100 可以确定封面的封面类型信息 200 基于磁力传感器的传感结果 692 传感器单元 160 . [0085] 在本发明的一个实施例中,触摸屏 140 移动终端的 100 可以独立显示屏幕并感知触摸。 移动终端 100 可以激活触摸屏的显示屏 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . 或者手机端 100 可以激活触摸屏的触摸感应区域 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . [0086] 例如,如果前盖单元 210 没有覆盖触摸屏 140 , 移动端 100 可以激活触摸屏的全屏显示 140 以及触摸屏的全触摸感应区域。 [0087] 另一方面,如果前盖单元 210 已经覆盖了触摸屏 140 , 移动端 100 可以在触摸屏的显示屏上激活第一区域的信息显示和触摸感应,仅对第二区域进行触摸感应 140 . 在这种情况下,可以在触摸屏的显示屏幕中停用除第一和第二区域之外的剩余区域 140 . [0088] 移动终端 100 可以从封面类型信息提供者那里接收封面类型信息 710 封面的 200 . 封面类型信息提供者 710 可能是连接器单元之一 202 a ,盖式信息发射器 224 , 和磁力施加器 691 . [0089] 如图。 图7是移动终端的框图 100 ,根据本发明的一个实施例。 [0090] 参考图。 7、移动端 100 包括一个控制器 110 , 一个通讯单元 120 , 一段记忆 130 , 触摸屏 140 , 和一个输入/输出 (I/O) 单元 150 . [0091] 控制器 110 包括一个中央处理器 (CPU) 111 . 控制器 110 可以包括数字信号处理器(DSP)并且可以被称为处理器。 控制器 110 包括一个只读存储器 (ROM) 112 用于存储控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 用于存储从移动终端外部接收的信号或数据 100 或用作移动终端执行操作的内存空间 100 . 中央处理器 111 可以包括一个或多个核心。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线互连。 控制器 110 可以控制通信单元 120 , 记忆 130 , 触摸屏 140 , 和 I/O 单元 150 . 例如,控制器 110 可为移动终端提供整体控制 100 并且可以控制上述组件之间的信号流。 [0092] 控制器 110 可以区分前盖单元中的窗口区域和封面输入区域 210 封面的 200 根据封面的类型 200 . 因此,控制器 110 可以在触摸屏上定义第一和第二区域 140 ,对应前盖单元的窗口区域和封面输入区域 210 . [0093] 当前盖单元 210 关闭,从而覆盖触摸屏 140 , 控制器 110 可以激活触摸屏的第一和第二区域 140 , 同时停用触摸屏的剩余区域 140 . 因此,控制器 110 可以检测到触摸屏的第一和第二区域的用户手势输入 140 通过前盖单元 210 . [0094] 控制器 110 可以控制触摸屏不同区域的不同触摸输入灵敏度的设置 140 . 例如,控制器 110 可以在触摸屏的第二区域设置更大的触摸输入灵敏度 140 比在触摸屏的第一个区域 140 . 例如,如果前盖单元 210 关闭,控制器 110 可以将触摸屏的第二区域的触摸输入灵敏度设置为大于第一区域的触摸输入灵敏度 140 . 触摸屏第一区和第二区的触摸输入灵敏度 140 可以设置为足够大以容纳触摸屏 140 检测在前盖单元上做出的用户手势 210 , 即使前盖单元 210 覆盖触摸屏 140 . [0095] 此外,控制器 110可以控制设置不同的触摸输入灵敏度,以根据前盖单元是否在触摸屏的第一和第二区域中感测触摸输入 210 覆盖触摸屏 140 . 例如,如果封面 200 不覆盖触摸屏 140 , 控制器 110 可以控制整个触摸屏上相同的触摸输入灵敏度的设置 140 . 另一方面,如果前盖单元 210 覆盖触摸屏 140 , 控制器 110 可以控制在第二区域中设置比在第一区域中更高的触摸输入灵敏度。 因此,即使当窗口区域比非窗口区域厚或窗口区域在非窗口区域关闭时打开,也可以正常感测到第二区域的触摸输入。 控制器 110 可以识别封面的类型 200 并判断前盖单元是否 210 覆盖触摸屏的显示屏 140 通过传感器单元接收封面类型信息 160 , 连接端口 180 ,或封面类型信息接收器 190 . 控制器 110 可以定义区域,例如包括对应于前盖单元的窗口区域的第一区域 210 第二区域对应于前盖单元的盖输入区域 210 , 在触摸屏上 140 根据封面类型。 例如,虽然封面 200 前盖单元的 210 覆盖触摸屏的显示屏 140 , 控制器 110 可以确定是否发生了事件。 当事件发生时,控制器 110 可在触摸屏上定义 140 ,区域包括例如第一区域对应于封面的窗口区域 200 ,例如,前盖单元 210 第二个区域对应于封面的封面输入区域 200 ,例如,前盖单元 210 . 事件可以包括预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 可能还有许多其他事件。 该事件可以是任何事件,只要它触发在显示屏幕上包括第一和第二区域的区域的定义。 [0096] 通讯单元 120 可连接移动终端 100 通过一根或多根天线连接到外部设备,并且可以与外部设备进行通信。 外部设备可以包括另一设备、便携式电话、智能手机、平板PC和服务器。 通讯单元 120 可以包括各种通信模块,例如移动通信模块、NFC模块、蓝牙模块等,并且可以通过各种通信方案例如移动通信、NFC、蓝牙等与外部设备进行通信。 喜欢。 [0097] 例如,移动终端 100 可以向便携式电话、智能手机、平板电脑或具有输入到移动终端的电话号码的其他设备发送无线信号或从其接收无线信号 100 ,用于通过移动通信模块进行语音通话、视频通话、短消息服务(SMS)或多媒体消息服务(MMS)。 此外,移动终端 100 可以通过NFC模块或蓝牙模块从外部设备接收信息。 在本发明的各个实施例中,通信单元 120 除了NFC模块和蓝牙模块之外,还可以包括无线局域网(WLAN)模块和另一短程通信模块中的至少一个,并且可以通过WLAN模块和短程通信中的至少一个接收信息 模块。 WLAN模块可以在控制器的控制下连接到互联网 110在安装了无线接入点 (AP) 的地方。 WLAN模块可以支持电气和电子工程师协会(IEEE)的WLAN标准IEEE802.11x。 短距离通信模块可以在移动终端之间进行短距离无线通信 100 和控制器控制下的外部设备 110 . 短距离通信可以符合红外数据协会(IrDA)等。 [0098] 记忆 130 可根据控制器的操作存储输入/输出信号或数据 110 , 通讯单元 120 , 触摸屏 140 , 和 I/O 单元 150 , 在控制器的控制下 110 . 记忆 130 可以存储多个用于控制移动终端的程序 100 或控制器 110 、多个应用程序以及用于执行各种功能的程序和数据。 [0099] 术语“存储器”可能包括 ROM 112 和内存 113 控制器内 110 ,或安装在移动终端上的存储卡(例如,安全数字(SD)卡、记忆棒等) 100 . 记忆 130 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)、固态驱动器(SSD)等。 [0100] 记忆 130 可以是机器可读介质(例如,计算机可读介质)。 机器可读介质可以定义为向机器提供数据以便机器可以执行特定功能的介质。 机器可读介质可以是存储介质。 记忆 130 可以包括非易失性介质和易失性介质。 所有这些媒体都应该是一种类型,可以为向机器读取命令的物理设备提供可检测的命令。 机器可读介质包括但不限于软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、光盘中的至少一种。 穿孔卡、纸带、RAM、可编程 ROM (PROM)、可擦除 PROM (EPROM) 和 Flash-EPROM。 在本发明的一个实施例中,存储器 130 可以存储封面类型信息。 [0101] 触摸屏 140 可以向用户提供各种图形用户界面(GUI)。 例如,触摸屏 140 可以通过用户的身体部位(例如,手指)或触摸输入单元接收各种手势输入,包括至少一个触摸输入或接近输入 158 (例如,一支笔)。 触摸屏 140 例如,可以实现为电阻型、电容型、电磁共振(EMR)型或它们的组合。 [0102] 在本发明的一个实施例中,触摸屏 140 可以在控制器的控制下显示应用程序的执行屏幕、消息屏幕、消息写入屏幕、消息接收屏幕等 110 . 此外,触摸屏 140 可以在显示屏的预定部分区域显示信息,例如触摸屏的第一区域 140 对应窗口区域 201 a ,而不在第一区域以外的区域显示信息。 [0103] 输入输出模块 150 包括一个按钮 152 , 麦克风 154 , 扬声器 156 , 和输入单元 158 , I/O 模块 150 不受限制。 可以提供光标控件,例如鼠标、轨迹球、操纵杆或光标方向键,用于与控制器通信 110 以及用于控制触摸屏上的光标移动 140 . [0104] 一个或多个按钮 152 可在移动终端中提供 100 并且可以向控制器提供与用户的按压相对应的各种输入信号 110 . [0105] 麦克风 154 可以接收来自各种声源的语音或声音,并在控制器的控制下将接收到的语音或声音转换为电信号 110 . [0106] 演讲者 156可以将与各种信号(例如,无线信号、广播信号、数字音频文件、数字视频文件等)对应的声音与应用程序的执行一起输出到移动终端的外部 100 在控制器的控制下 110 . [0107] 输入单元 158 可以是被配置为插入并保存在移动终端内部的设备或对象 100 ,或者单独配置。 在前一种情况下,输入单元 158 可以从移动终端中取出或插入移动终端 100 . 输入单元 158 可以是用户的手指,也可以是触控笔(以下简称笔)等输入工具,可以通过接近或触摸触摸屏来输入用户手势 140 . [0108] 移动终端 100 还可以包括传感器单元 160 . 传感器单元 160 可以包括至少一个磁力传感器 692 . 传感器单元 160 可以感应到永磁体施加的磁力 691 封面的 200 . [0109] 移动终端 100 还可以包括连接端口 180 . 连接端口 180 可以连接到连接器单元 202 a 封面的 200 . 一旦连接端口 180 连接到连接器单元 202 a , 连接端口 180 可能会收到有关封面的封面类型信息 200 从连接器单元 202 a. [0110] 移动终端 100 还可以包括封面类型信息接收器 190 . 封面式信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 . 如果覆盖类型信息接收器 190 被配置为短距离通信模块,当前盖单元 210 覆盖移动终端的正面 100 , 覆盖类型信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 , 和控制器 110 可确定前盖单元是否 210 覆盖触摸屏 140 基于从封面类型信息接收器接收的封面类型信息 190 . [0111] 如图。 图8是示出使用定义在触摸屏上的第一区域和第二区域的UI操作的流程图 140 ,分别对应封面的窗口区域和封面输入区域 200 在移动端 100 ,根据本发明的一个实施例。 [0112] 参考图。 8、移动端 100 标识封面的封面类型 200 , 在步 810 . 例如,控制器 110 移动终端的 100 可以识别封面的封面类型 200 通过感应从盖子施加的磁力 200 或通过接收有关封面的封面类型信息 200 从封面 200 . 关于封面的封面类型信息 200 可以包括关于在封面上定义的窗口区域和封面输入区域的位置信息 200 . 关于封面的封面类型信息 200 可能包括封面标识符 (ID) 和控制器 110 可以确定封面的窗口区域和封面输入区域的位置 200 使用封面 ID。 在这种情况下,关于窗口区域的位置和封面的封面输入区域的信息 200 各种封面ID可以预先存储在内存中 130 . 封面类型信息还可以包括关于封面的大小和位置中的至少一项的信息 200 以及封面的非窗口区域的位置 200 . [0113] 在步骤 820 , 控制器 110 确定触摸屏的触摸屏区域 140 包括对应于盖的窗口区域的第一区域 200 以及对应于封面的封面输入区域的第二区域 200 ,基于关于封面的封面类型信息200 . [0114] 带前盖单元 210 封面的 200 关闭,控制器 110 判断触摸屏上是否输入了用户手势 140 通过前盖单元 210 , 在步 830 . [0115] 如果在触摸屏的第二区域检测到用户手势 140 对应前盖单元的封面输入区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 在一步 840 . [0116] 如果在触摸屏的第一区域检测到用户手势 140 对应前盖单元的窗口区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 , 在步 850 . [0117] 例如,使用触摸屏 140 移动终端的 100 用前盖单元盖住 210 , 控制器 110 可以判断移动终端是否发生了事件 100 并且可以在触摸屏的第一区域显示与事件对应的信息 140 对应前盖单元的窗口区域 210 . 控制器 110 根据对触摸屏的第二区域的用户手势输入执行预定操作 140 ,对应前盖单元的封面输入区域 210 . 事件可以包括例如预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 这些事件纯粹是示范性的。 本领域技术人员可以清楚地理解,触发触摸屏第一区域显示信息的各种事件 140 在触摸屏的第二区域接收用户手势 140 可以实施。 [0118] 此外,例如,控制器 110 可以在触摸屏的显示画面中识别窗口区域对应的第一区域和覆盖输入区域对应的第二区域 140 ,基于关于封面的封面类型信息,并且可以激活第一区域作为信息显示区域和第二区域作为触摸输入区域。 这里,也可以在第一区域中感测触摸输入。 [0119] 图 图9、图10和图11是图示根据本发明实施例的用于各种类型的盖子的触摸屏区域的配置的图。 [0120] 参考图。 9、窗口区 910 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 920 , 和整个非窗口区域 920 是封面中的封面输入区域 200 ,根据本发明的一个实施例。 [0121] 在本实施例中,移动终端 100 激活第一区域 911 对应窗口区域 910 和第二个区域 921 对应非窗口区域 920 ,即触摸屏屏幕上的覆盖输入区域 140 . 可以显示信息并且可以在第一区域中感测触摸输入 911 ,而可以感测到触摸输入但信息可能不会显示在第二区域中 921 . [0122] 参考图。 10、窗口区 1010 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1020 ,以及一个覆盖输入区域 1030 在非窗口区域的一部分定义 1020 窗下区域 1010 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1011 对应窗口区域 1010 和第二个区域 1031对应覆盖输入区域 1030 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1011 ,而在第二区域中可以感测到触摸输入 1031 . 也可以在第一区域中感测到触摸输入 1011 . [0123] 参考图。 11、窗口区 1110 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1120 ,以及一个覆盖输入区域 1130 在非窗口区域的一部分定义 1120 窗下区域 1110 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1111 对应窗口区域 1110 和第二个区域 1131 对应覆盖输入区域 1130 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1111 ,而在第二区域中可以感测到触摸输入 1131 . 也可以在第一区域中感测到触摸输入 1111 . [0124] 参考图。 12、窗口区 1210 定义在前盖单元的右侧 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1220 ,以及一个覆盖输入区域 1230 在非窗口区域的一部分定义 1220 在窗口区域的左侧 1210 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1211 对应窗口区域 1210 和第二个区域 1231 对应覆盖输入区域 1230 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1211 ,而在第二区域中可以感测到触摸输入 1231 . 也可以在第一区域中感测到触摸输入 1211 . [0125] 在本发明的实施例中,可以以各种方式应用触摸输入。 如图。 图13是图示根据本发明实施例的触摸输入的图。 参考图。 参照图13,触摸输入可以包括双击、向上滑动或(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.799 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.803 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.803 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.804 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.804 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.804 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10075579B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.811 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.812 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.813 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.814 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.814 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.815 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), AU2015216023A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.822 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.823 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.823 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), CN104834353A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.839 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.839 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.840 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), CN104834353B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.847 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.847 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.848 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), EP2905681A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.859 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.860 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.860 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), EP2905681B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.872 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.872 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.872 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), JP2017511919A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.882 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.882 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.883 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), KR1020150094231A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.892 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.894 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.895 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), KR102245289B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.903 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.903 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.903 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), US10075579B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.913 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.913 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.914 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), US20150229754A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.923 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.924 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.924 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270634(Integer), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.936 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.936 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.936 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10075579B2(String), US10075579B2(String), 1536595200(Integer), 270634(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.948 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.949 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.949 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.950 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.951 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.951 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 0(Integer), 1681974671(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.958 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.959 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.959 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.960 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.961 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.961 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.970 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.971 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.971 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 0(Integer), 1681974671(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.981 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.982 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.982 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184951(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.983 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.983 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.984 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75901(Integer), 2(Integer), 184951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.993 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.994 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.994 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.995 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.996 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.996 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.997 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.998 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:11.999 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75901(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.000 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.001 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.001 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.002 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.002 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.003 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.010 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.011 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.011 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.013 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.014 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.014 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.015 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.016 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.016 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.023 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.025 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.026 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.027 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.029 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.029 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, mobile terminal auxiliary device and method for controlling the same(String), 移动终端、移动终端辅助装置及其控制方法(String), US9749858B2(String), Methods and apparatuses are provided for controlling a mobile terminal and a mobile terminal auxiliary device. Information on at least one of the mobile terminal and the mobile terminal auxiliary device and security-related information on the at least one of the mobile terminal and the mobile terminal auxiliary device are stored. It is determined whether the mobile terminal and the mobile terminal auxiliary device exist within a predetermined available distance. If the mobile terminal and the mobile terminal auxiliary device exist within the predetermined available distance, it is determined whether the mobile terminal or the mobile terminal auxiliary device has been registered by using the stored information.(String), 提供了一种移动终端的控制方法和装置以及移动终端辅助设备。 存储关于移动终端和移动终端辅助设备至少之一的信息以及关于移动终端和移动终端辅助设备至少之一的安全相关信息。 确定移动终端和移动终端辅助设备是否存在于预定的可用距离内。 如果移动终端和移动终端辅助设备存在于预定可用距离内,则使用存储的信息判断移动终端或移动终端辅助设备是否已经注册。(String), US14/509670(String), 1412697600(Integer), US9749858B2(String), 1503936000(Integer), 1503936000(Integer), 美国(String), 4(Integer), KR(String), 2(Integer), 16(Integer), US20020111138A1 | US20080287062A1 | US20110173447A1 | US20120139879A1 | US20120206555A1 | US20120258665A1 | US20120281686A1 | US20120322376A1 | US20130143499A1 | US20130257777A1 | US20140115690A1 | US20140298672A1 | US20140378056A1 | US9154954B2 | US9179310B2 | US9398133B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.039 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.040 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.040 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.041 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.042 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.042 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7246d80a9bd1486393381e6236a7b9ae.png(String), 184952(Integer), 7246d80a9bd1486393381e6236a7b9ae.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.049 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.050 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.050 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.051 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.053 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.053 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, mobile terminal auxiliary device and method for controlling the same(String), 移动终端、移动终端辅助装置及其控制方法(String), US9749858B2(String), Methods and apparatuses are provided for controlling a mobile terminal and a mobile terminal auxiliary device. Information on at least one of the mobile terminal and the mobile terminal auxiliary device and security-related information on the at least one of the mobile terminal and the mobile terminal auxiliary device are stored. It is determined whether the mobile terminal and the mobile terminal auxiliary device exist within a predetermined available distance. If the mobile terminal and the mobile terminal auxiliary device exist within the predetermined available distance, it is determined whether the mobile terminal or the mobile terminal auxiliary device has been registered by using the stored information.(String), 提供了一种移动终端的控制方法和装置以及移动终端辅助设备。 存储关于移动终端和移动终端辅助设备至少之一的信息以及关于移动终端和移动终端辅助设备至少之一的安全相关信息。 确定移动终端和移动终端辅助设备是否存在于预定的可用距离内。 如果移动终端和移动终端辅助设备存在于预定可用距离内,则使用存储的信息判断移动终端或移动终端辅助设备是否已经注册。(String), US14/509670(String), 1412697600(Integer), US9749858B2(String), 1503936000(Integer), 1503936000(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 16(Integer), US20020111138A1 | US20080287062A1 | US20110173447A1 | US20120139879A1 | US20120206555A1 | US20120258665A1 | US20120281686A1 | US20120322376A1 | US20130143499A1 | US20130257777A1 | US20140115690A1 | US20140298672A1 | US20140378056A1 | US9154954B2 | US9179310B2 | US9398133B2(String), \20230420\7246d80a9bd1486393381e6236a7b9ae.png(String), 20(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.064 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.065 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.065 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.066 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.068 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.068 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 1. A method for controlling a mobile terminal auxiliary device, the method comprising:storing information on at least one mobile terminal and security-related information on each of the at least one mobile terminal;determining whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal; andif the mobile terminal exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile terminal.(String), 1.一种移动终端辅助设备的控制方法,该方法包括:存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;根据移动终端发射的信号强度,判断移动终端是否存在于移动终端辅助设备的预定可用范围内;和如果移动终端在预定可用范围内,则解除移动终端的锁定状态,包括显示锁定图像。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.069 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 2. The method of claim 1, wherein determining whether the mobile terminal exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 2.如权利要求1所述的方法,其中判断移动终端是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端是否在预定可用范围内。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.069 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 3. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;receiving, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal;comparing the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 3.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;从移动终端接收关于触摸信号在移动终端的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端辅助设备的触摸信号的时间进行比较;和如果触摸时间信息与检测到移动终端辅助设备的触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.069 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 4. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;transmitting, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device; andreceiving, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 4.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;和从移动终端接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.069 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 5. The method of claim 1, further comprising:determining whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device; andif the mobile terminal does not exist within the predetermined connection range, deleting information on the mobile terminal.(String), 5.如权利要求1所述的方法,还包括:判断移动终端是否存在于移动终端辅助设备的预定连接范围内;和如果预定连接范围内不存在移动终端,则删除移动终端上的信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.069 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 6. A method for controlling a mobile terminal, the method comprising:storing information on at least one mobile terminal auxiliary device;determining whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device; andif the mobile terminal auxiliary device exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile device.(String), 6.一种移动终端的控制方法,该方法包括:在至少一个移动终端辅助设备上存储信息;根据移动终端辅助设备发送的信号强度判断移动终端辅助设备是否存在于距移动终端预定可用范围内;和如果移动终端辅助设备存在于预定可用范围内,则解除移动设备的锁定状态,包括显示锁定图像。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.069 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 7. The method of claim 6, wherein determining whether the mobile terminal auxiliary device exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal auxiliary device exists within the predetermined available range, when the use signal is detected.(String), 7.如权利要求6所述的方法,其中判断移动终端辅助设备是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.070 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 8. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;receiving, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device;comparing the received touch time information with a time when the touch signal of the mobile terminal is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 8.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端触摸信号的时间进行比较;和若触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.070 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 9. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;transmitting, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal; andreceiving, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 9.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息;和从移动终端辅助设备接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.070 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 10. The method of claim 6, further comprising:determining whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal; andif the mobile terminal auxiliary device does not exist within the predetermined connection range, deleting information on the mobile terminal auxiliary device.(String), 10.如权利要求6所述的方法,还包括:判断移动终端辅助设备是否存在于移动终端的预定连接范围内;和如果预定连接范围内不存在移动终端辅助设备,则删除移动终端辅助设备的信息。11、一种移动终端辅助设备包括:与至少一个移动终端通信的通信单元;存储器,存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;和控制器,基于从移动终端发送的信号的强度确定移动终端是否存在于移动终端辅助设备的预定可用范围内,并且如果是则释放移动终端的锁定状态,包括显示锁定图像移动终端存在于预定的可用范围内。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.070 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 11. A mobile terminal auxiliary device comprising:a communication unit that communicates with at least one mobile terminal;a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal; anda controller that determines whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal exists within the predetermined available range.(String), 12.如权利要求11所述的装置,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端是否存在于预定可用范围内。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.070 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 12. The device of claim 11, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 13.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,从移动终端接收触摸时间信息,检测移动终端触摸信号的时间,将接收到的触摸时间信息与触摸发生的时间进行比较检测到移动终端辅助设备的信号,如果触摸时间信息与检测到移动终端辅助设备触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸设备。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.071 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 13. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, receive, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal, compare the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 14.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,并从移动终端接收触摸时间信息移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.071 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 14. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, transmit, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, and receive, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 15.如权利要求11所述的装置,其中控制器控制判断移动终端是否存在于移动终端辅助设备的预定连接范围内,如果移动终端不存在于预定连接范围内,则删除移动终端上的信息。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.071 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 15. The device of claim 11, wherein the controller controls to determine whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device, and if the mobile terminal does not exist within the predetermined connection range, delete information on the mobile terminal.(String), 16.移动终端包括:通信单元,与至少一个移动终端辅助设备进行通信;存储器,存储关于至少一个移动终端辅助设备的信息;和控制器,基于从移动终端辅助设备发送的信号强度确定移动终端辅助设备是否存在于距移动终端的预定可用范围内,并释放移动终端的锁定状态,包括显示锁定图像如果移动终端辅助设备存在于预定可用范围内,则终端。(String), 1(Integer), 14(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.071 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 16. A mobile terminal comprising:a communication unit that communicates with at least one mobile terminal auxiliary device;a memory that stores information on the at least one mobile terminal auxiliary device; anda controller that determines whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal auxiliary device exists within the predetermined available range.(String), 17.如权利要求16所述的移动终端,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.071 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 17. The mobile terminal of claim 16, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal auxiliary device exists within the predetermined available range when the use signal is detected.(String), 18.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,将接收到的触摸时间信息与触摸时间进行比较。检测到移动终端的触摸信号,如果触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.071 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 18. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, receive, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, compare the received touch time information with a time when the touch signal of the mobile terminal is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 19.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息,并从移动终端辅助设备接收触摸时间信息。移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.072 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 19. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, transmit, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal, and receive, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 20.如权利要求16所述的移动终端,其中控制器判断移动终端辅助设备是否存在于移动终端的预定连接范围内,如果移动终端辅助设备不存在于预定连接范围内,则控制删除关于移动终端辅助设备的信息。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.072 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.072 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 20. The mobile terminal of claim 16, wherein the controller determines whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal, and if the mobile terminal auxiliary device does not exist within the predetermined connection range, controls to delete information on the mobile terminal auxiliary device.(String), 1(Integer), 19(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.251 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.251 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.252 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.252 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.253 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184952(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to Korean Patent Application No. 10-2013-0119737, filed on Oct. 8, 2013, the content of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal and a mobile terminal auxiliary device, and more particularly, to a control method by which security related functions of the mobile terminal can be executed without an additional authentication process by registration between the mobile terminal and the mobile terminal auxiliary device. [0004]2. Description of the Related Art [0005]Terminals are classified into mobile/portable terminals and stationary terminals according to their mobility. Mobile terminals are divided into handheld terminals and vehicle mount terminals according to whether a user can carry the terminals. [0006]Terminals have been implemented with multimedia players that have multiple functions such as, for example, photographing still images or moving images, reproducing music files or movie files, playing games, receiving broadcasts, or the like. [0007]In order to support and strengthen the functions of the terminals, structures and/or software of the terminals can be improved. [0008]In addition, various terminal auxiliary devices have been used for convenient use of the terminals. Particularly, electronic pens, such as styluses, may be used as terminal auxiliary devices. [0009]The terminal and the pen are connected with each other wirelessly or using a wire, and the terminal receives a user input by using the pen. Therefore, the user can input specific texts, symbols, images, or the like more easily, accurately and faster. [0010]Pens are widely used in the terminals as accessories. Further, with the improvement of technology, the pens can transfer more precise illustrations and designs of a user to electronic devices. [0011]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0012]As shown in FIG. 1A, when a user touches specific contents such as, for example, a memo, a schedule, an email, or a diary, which are displayed in a display unit of a mobile terminal 100, by using a mobile terminal auxiliary device, such as, for example, an electronic pen 150, an operation of pre-viewing the corresponding contents may be executed. The touch of the electronic pen 150 may be performed by a proximity touch and/or a contact touch. [0013]In addition, as shown in FIG. 1B, when the mobile terminal auxiliary device, for example, the electronic pen 150, which is connected with the mobile terminal, is taken out from the mobile terminal while a screen 110 of the mobile terminal is turned off, the mobile terminal may be configured to automatically switch to a locked image 120. Here, the locked image means an image followed by a waiting image in which the mobile terminal can be used. That is, the mobile terminal may wait for instructions for releasing security, such as a password input of a user. When the user inputs the instruction for releasing security, the locked state of the mobile terminal may be released, and the mobile terminal may switch to the waiting image to thereby execute operations thereof. [0014]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0015]Referring to FIG. 2A, in contents 210 such as, for example, a memo, when other people's accesses are restricted through a locking setup by a user, a preview function by the mobile terminal auxiliary device 150 of FIG. 1A may be deactivated. That is, in the case of a memo that is set to be locked, although someone touches the corresponding contents by the mobile terminal auxiliary device, the preview function may not be executed unless the password is entered by the user. [0016]In addition, as shown in FIG. 2B, although a locked image 230 is displayed by taking out the mobile terminal auxiliary device from the mobile terminal while a screen 220 of the mobile terminal is turned off, the terminal may be switched to an available state, i.e., the waiting state, only by inputting the instruction for releasing security, such as by entering the password by the user. [0017]Further, although not shown in the drawings, even while using the mobile terminal by the mobile terminal auxiliary device, for example, the electronic pen, if the mobile terminal does not continuously receive usage instruction inputs, i.e., the touch signal inputs, the screen of the mobile terminal will be turned off soon and the security function will be resumed. [0018]Furthermore, even though the user obtains the authority to access the contents or releases the locked state of the mobile terminal through the security process, if the mobile terminal is not used for a while or it is required to be turned off and then turned on, the user is required to repeat the security process. SUMMARY OF THE INVENTION [0019]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal auxiliary device that may be authenticated through a security process when it is connected with a mobile terminal, so that repetition of the security process may be removed when the mobile terminal auxiliary device is required to be used afterwards, to thereby enhance the usability of the mobile terminal. [0020]Another aspect of the present invention provides convenience in using applications, which can be used only by the process of logging on or releasing a locked state by means of a mobile terminal auxiliary device. [0021]An additional aspect of the present invention prevents a screen of a mobile terminal from being turned off or a locked state from being resumed during the use of the mobile terminal, by continuously checking the use of the mobile terminal using a low power technology without an additional operation of a mobile terminal auxiliary device. [0022]A further aspect of the present invention allows, when a user wishes to use each of a plurality of mobile terminals, or authentication is required, the user to control each mobile terminal by the authenticated mobile terminal auxiliary device and use the mobile terminal without the security checking process to thereby provide convenient use thereof. [0023]Another aspect of the present invention allows each mobile terminal to identify the user through the corresponding mobile terminal auxiliary device, and a UI of the mobile terminal to be configured with specific values predefined according to the setup or user's desire. [0024]In accordance with an aspect of the present invention, a method is provided for controlling a mobile terminal auxiliary device. Information on at least one mobile terminal and security-related information on each of the at least one mobile terminal are stored. It is determined whether a mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device. If the mobile terminal exists within the predetermined available distance, it is determined whether the mobile terminal has been registered by using the stored information on the at least one mobile terminal. If the mobile terminal has been registered, security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, is transmitted to the mobile terminal. [0025]In accordance with another aspect of the present invention, a method is provided for controlling a mobile terminal. Information on at least one mobile terminal auxiliary device is stored. It is determined whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal. If the mobile terminal auxiliary device exists within the predetermined available distance, it is determined whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device. If the mobile terminal auxiliary device has been registered, predetermined security-related information is applied according to the mobile terminal auxiliary device. [0026]In accordance with another aspect of the present invention, a mobile terminal auxiliary device is provided that includes a communication unit that communicates with at least one mobile terminal, and a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal. The mobile terminal auxiliary device also includes a controller that determines whether the mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device, determines whether the mobile terminal has been registered by using the stored information on at least one mobile terminal if the mobile terminal exists within the predetermined available distance, and controls the communication unit to transmit security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, to the mobile terminal, if the mobile terminal has been registered. [0027]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a communication unit that communicates with at least one mobile terminal auxiliary device, and a memory that stores information on the at least one mobile terminal auxiliary device. The mobile terminal also includes a controller that determines whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal, determines whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device if the mobile terminal auxiliary device exists within the predetermined available distance, and controls to apply predetermined security-related information according to the mobile terminal auxiliary device if the mobile terminal auxiliary device has been registered. BRIEF DESCRIPTION OF THE DRAWINGS [0028]The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0029]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0030]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0031]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention; [0032]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention; [0033]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention; [0034]FIG. 6 is a flowchart illustrating the operation of a mobile terminal auxiliary device, according to an embodiment of the present invention; [0035]FIG. 7 is a flowchart illustrating the operation of a mobile terminal, according to an embodiment of the present invention; [0036]FIGS. 8A and 8B are diagrams illustrating registration between a mobile terminal and a mobile terminal auxiliary device and the operation thereof, according to an embodiment of the present invention; [0037]FIGS. 9A and 9B are diagrams illustrating an available distance, according to an embodiment of the present invention; [0038]FIG. 10 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to an embodiment of the present invention; [0039]FIG. 11 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to another embodiment of the present invention; [0040]FIG. 12 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in used by a mobile terminal, according to an embodiment of the present invention; [0041]FIG. 13 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by a mobile terminal, according to another embodiment of the present invention; [0042]FIGS. 14A-14C are diagrams illustrating a determination of whether a mobile terminal auxiliary device has been used, according to an embodiment of the present invention; [0043]FIGS. 15A-15D are diagrams illustrating uses of mobile terminals and mobile terminal auxiliary devices, according to an embodiment of the present invention; [0044]FIG. 16 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal auxiliary device and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0045]FIG. 17 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0046]FIG. 18 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to an embodiment of the present invention; and [0047]FIG. 19 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to another embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0048]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0049]Hereinafter, a mobile terminal associated with the present invention will be described in detail with reference to drawings. The suffixes of component elements used in the following descriptions, such as, a “module” and a “unit”, are assigned or used together only for ease of description, but they do not have distinguishing meanings or roles. [0050]A mobile terminal described in the embodiments of the present invention may be embodied as a portable phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation terminal, and the like. However, it is apparent to those skilled in the art that a configuration according to embodiments of the present invention are also applied to a stationary terminal such as, for example, a digital TV, a desktop computer, and the like. [0051]Mobile terminal auxiliary devices of the embodiments of the present invention may include electronic pens, such as styluses, which can communicate with a mobile terminal. In addition, it is obvious for those skilled in the art that the mobile terminal auxiliary devices of the present invention may be applied to stationary terminals such as TVs, desktop computers, or the like, as well as the mobile terminals. [0052]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention. [0053]A mobile terminal auxiliary device 300 includes a communication unit 310, a memory 320, and a controller 330. The mobile terminal auxiliary device is not limited to the elements of FIG. 3, and it may further include other elements, or some of the elements may be omitted. For example, the mobile terminal auxiliary device 300 may further include an output unit, such as, for example, an audio output module, an alarm unit, and a display unit, and a user input unit for receiving a user input. [0054]The communication unit 310 may include at least one module enabling wireless communication between the mobile terminal auxiliary device 300 and a mobile terminal. For example, the communication unit 310 may include a short-range communication module for near field communication. Here, the short-range communication technology may adopt Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra wideband (UWB), ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a Bluetooth (BT) module and a Bluetooth low energy (BLE) module. [0055]The communication unit 310 may allow the mobile terminal auxiliary device 300 and the mobile terminal to register with each other by communicating with the mobile terminal, as described in greater detail below. [0056]The memory 320 may store programs for processing and controlling of the controller 330 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like). The memory 320 may store frequency of use for the data. [0057]The memory 320 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., a secure digital (SD) memory, an XD memory, or the like), a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a programmable ROM (PROM), a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal auxiliary device 300 may operate in relation to a web storage for providing a storage function of the memory 320 on the Internet. [0058]In general, the controller 330 controls overall operations of the mobile terminal auxiliary device 300. For example, the controller 330 may control to perform an operation of registering the mobile terminal auxiliary device 300 and the mobile terminal with each other. In addition, in the case of using the mobile terminal auxiliary device 300 through authentication between the mobile terminal and the mobile terminal auxiliary device 300, the controller 330 may control to use the mobile terminal without an additional security checking process, which is described in greater detail below. [0059]The mobile terminal auxiliary device 300 may further include a user input unit. The user input unit generates input data for controlling operations of the mobile terminal auxiliary device by a user. The user input unit may include at least one of buttons provided on the front, back, or side surface of the mobile terminal auxiliary device, touch sensors (a pressure type/a capacitive type), keypads, dome switches, jog wheels, jog switches, or the like, but it is not limited thereto. [0060]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention. [0061]The mobile terminal auxiliary device, according to an embodiment of the present invention, may be embodied as an electronic pen 400, such as a stylus. The electronic pen 400 includes a communication unit 410, a memory 420, a controller 430, a touch recognition unit 440, and the like, but it is not limited thereto. For example, the electronic pen 400 may further include a power supply, such as a battery 450, and the power supply may receive external power and internal power to be supplied to each element to operate under the control of the controller 430. The power supply may include at least one of connection ports, a power supply controller, and a charge monitoring unit, as well as the battery 450. [0062]The communication unit 410 may include at least one module enabling wireless communication between the electronic pen 400 and a mobile terminal. According to an embodiment of the present invention, the communication unit 410 may include at least one of a BT module or a BLE module. [0063]The communication unit 410 may allow the electronic pen 400 and the mobile terminal to be registered with respect to each other by communicating with the mobile terminal, as described in greater detail below. [0064]The memory 420 may store programs for processing and controlling of the controller 430 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like), as described in detail above. [0065]In general, the controller 430 controls overall operations of the electronic pen 400. For example, the controller 430 may control to perform an operation of registering the electronic pen 400 and the mobile terminal with each other. In addition, in the case of using the electronic pen 400 through authentication between the mobile terminal and the electronic pen 400, the controller 430 may control to use the mobile terminal without an additional security checking process, as described in detail below. [0066]The touch recognition unit 440 may recognize touch signals of the electronic pen 400. When the touch signal of the electronic pen 400 is input, the controller 430 controls to perform a predetermined operation according to the touch signal input. According to an embodiment of the present invention, in addition to the touch recognition unit 440, the electronic pen 400 may further include a user input unit for generating input data of a user. The user input unit may include at least one of buttons provided on the side surface of the electronic pen, a keypad, a dome switch, a jog wheel, a jog switch, or the like, but it is not limited thereto. [0067]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention. [0068]A mobile terminal 500 includes a communication unit 510, a memory 520, a controller 530, a user input unit 540, and an output unit 550. The elements shown in FIG. 5 are not essential to the mobile terminal, and the mobile terminal may further include other elements, or some of the elements may be omitted. [0069]The communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and a wireless communication system, or the mobile terminal 500 and a network where the mobile terminal 500 is located. In addition, the communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and the mobile terminal auxiliary device. For example, the communication unit 510 may include a broadcast receiving module, a mobile communication module, a wireless Internet module, a short-range communication module, a location information module, and the like. [0070]The broadcast receiving module receives broadcast signals and/or broadcast-related information from external broadcast management servers through broadcasting channels. The broadcasting channels may include a satellite channel and a ground wave channel. At least two broadcast receiving modules may be provided in the mobile terminal 500 to concurrently receive broadcasts through at least two broadcasting channels or to switch between at least two broadcasting channels. [0071]The mobile communication module transmits and receives wireless signals to and from at least one of base stations, other terminals, and servers in mobile communication networks, such as, for example, global system for mobile communication (GSM), code division multiple access (CDMA), wideband CDMA (WCDMA) (but not limited thereto). The wireless signals may include voice call signals, video call signals, or various data according to transmission and reception of text/multimedia messages. [0072]The wireless Internet module for connecting the wireless Internet may be built in the mobile terminal 500 or externally provided. The wireless Internet may utilize the technologies of wireless LAN (WLAN), Wi-Fi, wireless broadband (Wibro), world interoperability for microwave access (Wimax), high speed downlink packet access (HSDPA), GSM, CDMA, WCDMA, long term evolution (LTE), or the like. [0073]The wireless Internet connection through Wibro, HSDPA, GSM, CDMA, WCDMA, and LTE is made by wireless mobile communication networks. Accordingly, the wireless Internet module that connects with the wireless Internet through the mobile communication networks may be regarded as a type of mobile communication module. [0074]The short-range communication module refers to a module for near field communication. The short-range communication technology may adopt BT, RFID, IrDA, UWB, ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a BT module and a BLE module. [0075]The user input unit 540 generates input data for controlling operations of the mobile terminal by a user. The user input unit 540 may include buttons 543 on the front, back or side surface of the mobile terminal 500, and a touch sensor (a pressure type/a capacitive type) 545. The user input unit 540 may further include keypads, dome switches, jog wheels, jog switches, or the like. [0076]The output unit 550 may generate outputs related to a sense of sight, a sense of hearing, or a sense of touch, and includes a display unit 555, but it is not limited thereto. For example, the output unit 550 may include an audio output module, an alarm module, and a haptic module. [0077]The display unit 555 displays (outputs) information processed in the mobile terminal 500. For example, when the mobile terminal 500 is in a phone call mode, the display unit 555 displays a user interface (UI) or a graphic user interface (GUI) related to the phone call. When the mobile terminal 500 is in a video call mode or photographing mode, the display unit 555 displays images, which are photographed and/or received, using the UI or the GUI. [0078]The display unit 555 may include at least one of a liquid crystal display (LCD), a thin film transistor-LCD (TFT LCD), an organic light-emitting diode (OLED), a flexible display, and a 3D display. [0079]Some of the above displays may be configured to be transparent or light-penetrable in order to view the outside therethrough, which are called transparent displays, typically, including transparent OLEDs (TOLEDs). The back structure of the display unit 555 may be also configured to be light-penetrable. According to the above structure, a user can see objects behind the terminal through the area of the display unit 555 of the terminal. [0080]Two or more display units 555 may be provided according to the type of mobile terminal 500. For example, a plurality of display units may be arranged to be spaced from each other or to be integral on the same plane, or may be disposed on different planes in the mobile terminal 500. [0081]In the case of the display unit 555 and the touch sensor 545, which are formed in a layer structure or integrally (hereinafter, referred to as a “touch screen”), the display unit 555 may be used as the input device as well as the output device. The touch sensor may be formed to be a laminate with the display unit 555 in the case of, for example, touch films, touch sheets, touch pads, or the like, or may be integrally formed with the display unit 555. [0082]The touch sensor may be configured to convert the change of pressure acting on the specific portion of the display unit 555 or the change of capacitance generating on the specific portion of the display unit 555 to electric signals. The touch sensor may be configured to detect the touch pressure as well as the touch point and the touch area. [0083]Upon a touch input on the touch sensor, the corresponding signals are transmitted to a touch controller. The touch controller processes the signals and transmits the corresponding data to the controller 530. Accordingly, the controller 530 may recognize which area of the display unit 555 has been touched. [0084]Although not shown in the drawing, a proximity sensor may be disposed inside or around the touch screen of the mobile terminal 500. The proximity sensor may detect objects approaching a predetermined detection surface, or objects around the proximity sensor, by using an electromagnetic field force or an infrared ray without mechanical contacts. The proximity sensor has a long life span and various utilization compared to a contact type sensor. [0085]The proximity sensor may include a transparent photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillating proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor an infrared proximity sensor, or the like. [0086]Hereinafter, for convenience of explanation, the term “proximity touch” may refer to an operation in which a pointer approaches the touch screen where the proximity sensor is installed to be thereby recognized without a contact, and the term “contact touch” may refer to an operation of touching of the pointer on the screen. A proximity touch point of the pointer on the touch screen may denote the point on the screen which vertically corresponds to the location of the pointer in the state of the proximity touch. Hereinafter, the term “touch” may encompass the proximity touch as well as the contact touch. [0087]According to an embodiment of the present invention, the proximity touch may include a hovering input. [0088]The proximity sensor detects the proximity touch and a proximity touch pattern (e.g., a proximity touch distance, a proximity touch direction, a proximity touch speed, a proximity touch time, a proximity touch point, a proximity touch movement state, or the like). Information corresponding to the detected proximity touch and the proximity touch pattern may be displayed on the touch screen. [0089]The memory 520 may store programs for processing and controlling of the controller 530 and perform a function of temporarily storing input/output data (e.g., a telephone number list, messages, audio, still images, moving images, information on the mobile terminal, identification information on the mobile terminal, information on the mobile terminal auxiliary device, security related information, or the like). The memory 520 may store frequency of use for the data. [0090]In addition, the memory 520 may store data on various vibrations and sounds, which are output upon the touch input on the touch screen. [0091]The memory 520 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD memory, an XD memory, or the like), a RAM, an SRAM, a ROM, an EEPROM, a PROM, a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal 500 may operate in relation to a web storage for providing a storage function of the memory 520 on the Internet. [0092]The mobile terminal 500 may further include an audio/video (A/V) input unit for inputting audio signals or video signals, and a sensing unit for generating sensing signals to sense the current state of the mobile terminal 500, such as, for example, the opening/closing state of the mobile terminal 500, the location of the mobile terminal 500, contact of users, directions of the mobile terminal, and acceleration/deceleration of the mobile terminal, and to thereby control operations of the mobile terminal 500. [0093]In addition, the mobile terminal 500 may include an interface unit that plays a role of a path for all external devices connected with the mobile terminal 500. The interface unit receives data or power from the external devices and transfers the same to each element of the mobile terminal 500. The interface unit also allows data to be transmitted to the external devices from the mobile terminal 500. For example, the interface unit may include a wireless/wired headset port, an external charge port, a wireless/wired data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, or the like. [0094]In addition, the mobile terminal 500 may further include a power supply that receives external power and internal power and supplies the same to each element for operations under the control of the controller(String), 优先 [0001] 本申请根据 35 U.S.C. 要求优先权 2013 年 10 月 8 日提交的韩国专利申请号 10-2013-0119737 的 §119(a),其内容通过引用并入本文。 发明背景 [0002] 一、发明领域 [0003] [0001] 本发明总体上涉及移动终端和移动终端辅助设备,并且更具体地,涉及一种控制方法,通过该方法可以执行移动终端的安全相关功能而无需通过移动终端和移动终端之间的注册的附加认证过程 终端辅助设备。 [0004] 二、相关技术说明 [0005] 终端根据其移动性分为移动/便携终端和固定终端。 移动终端根据用户是否可以携带终端分为手持终端和车载终端。 [0006] 终端已经实现了具有多种功能的多媒体播放器,例如拍摄静止图像或运动图像、再现音乐文件或电影文件、玩游戏、接收广播等。 [0007] 为了支持和加强终端的功能,可以改进终端的结构和/或软件。 [0008] 此外,为了方便终端的使用,还使用了各种终端辅助设备。 特别地,电子笔,例如手写笔,可以用作终端辅助设备。 [0009] 终端和笔通过无线或有线方式相互连接,终端通过笔接收用户输入。 因此,用户可以更方便、更准确、更快速地输入特定的文字、符号、图像等。 [0010] 笔作为配件广泛应用于终端。 此外,随着技术的进步,笔可以将用户更精确的插图和设计转移到电子设备上。 [0011] 图1A和1B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0012] 如图1A所示,当用户触摸移动终端的显示单元中显示的特定内容,例如备忘录、日程、电子邮件或日记时 100 ,通过使用移动终端辅助设备,例如电子笔 150 ,可以执行预览相应内容的操作。 电子笔的触感 150 可以通过接近触摸和/或接触触摸来执行。 [0013] 另外,如图1B所示,当移动终端辅助设备,例如电子笔 150 ,与移动终端连接,从移动终端中取出,同时屏幕 110 关闭移动终端,移动终端可配置为自动切换到锁定图像 120 . 这里,锁定图像是指跟随有移动终端可以使用的等待图像的图像。 也就是说,移动终端可以等待解除安全的指令,例如用户的密码输入。 当用户输入解锁指令时,可以解除移动终端的锁定状态,移动终端可以切换到等待画面,从而执行其操作。 [0014] 图2A和2B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0015] 参考图2A,在内容 210 例如备忘录,当用户通过锁定设置限制他人访问时,移动终端辅助设备的预览功能 150 可以停用图1A的。 也就是说,在设置为锁定的备忘录的情况下,即使有人通过移动终端辅助设备触摸了相应的内容,也可能无法执行预览功能,除非用户输入密码。 [0016] 此外,如图 2B 所示,虽然锁定图像 230 通过从移动终端中取出移动终端辅助设备来显示,同时屏幕 220移动终端关机后,用户只需输入解除安全的指令,如输入密码,即可将终端切换到可用状态,即等待状态。 [0017] 此外,虽然未在附图中示出,但是即使在通过移动终端辅助设备例如电子笔使用移动终端时,如果移动终端没有持续接收到使用指令输入,即触摸信号输入,则屏幕 移动终端的 将很快关闭并恢复安全功能。 [0018] 进一步地,即使用户通过安全过程获得了访问内容的权限或者解除了移动终端的锁定状态,如果移动终端暂时不使用或者需要关机再开机, 用户需要重复安全过程。 发明内容 [0019] 做出本发明以至少解决上述问题和/或缺点并且提供至少下述优点。 相应地,本发明的一个方面提供了一种移动终端辅助设备,在与移动终端连接时,可以通过安全流程进行认证,从而在需要移动终端辅助设备时,可以免去重复的安全流程。 之后使用,从而提高移动终端的可用性。 [0020] 本发明的另一个方面提供了使用应用程序的便利性,仅通过移动终端辅助设备登录或解除锁定状态的过程就可以使用这些应用程序。 [0021] 本发明的另一方面通过使用低功率技术持续检查移动终端的使用而无需额外的额外的,防止移动终端的屏幕在移动终端的使用期间被关闭或锁定状态被恢复 移动终端辅助设备的操作。 [0022] 本发明的另一方面允许,当用户希望使用多个移动终端中的每一个,或者需要认证时,用户通过认证的移动终端辅助设备控制每个移动终端并且在没有安全性的情况下使用移动终端 检查过程,从而提供方便的使用。 [0023] 本发明的另一个方面允许每个移动终端通过相应的移动终端辅助设备来识别用户,并且移动终端的UI被配置有根据设置或用户期望预定义的特定值。 [0024] 根据本发明的一方面,提供了一种移动终端辅助设备的控制方法。 存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息。 判断移动终端辅助设备在预定可用距离内是否存在移动终端。 如果移动终端存在于预定可用距离内,则利用存储的至少一个移动终端的信息判断移动终端是否已经注册。 如果移动终端已经注册,则从存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息被发送到移动终端。 [0025] 根据本发明的另一方面,提供了一种用于控制移动终端的方法。 存储至少一个移动终端辅助设备的信息。 判断移动终端的预定可用距离内是否存在移动终端辅助设备。 如果移动终端辅助设备存在于预定可用距离内,则通过至少一个移动终端辅助设备的信息判断移动终端辅助设备是否已经注册。 如果移动终端辅助设备已经注册,则根据移动终端辅助设备应用预定的安全相关信息。 [0026]根据本发明的另一个方面,提供了一种移动终端辅助设备,包括与至少一个移动终端通信的通信单元,以及存储关于至少一个移动终端的信息和关于移动终端的安全相关信息的存储器。 每个至少一个移动终端。 移动终端辅助设备还包括控制器,判断移动终端是否存在于距离移动终端辅助设备的预定可用距离内,如果移动终端是移动终端,则使用存储在至少一个移动终端上的信息判断移动终端是否已经注册。 终端存在于预定可用距离内,并且控制通信单元将存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息发送到移动终端,如果移动终端具有 已注册。 [0027] 根据本发明的另一方面,提供了一种移动终端,包括与至少一个移动终端辅助设备通信的通信单元,以及存储关于至少一个移动终端辅助设备的信息的存储器。 移动终端还包括控制器,确定移动终端辅助设备是否存在于距移动终端的预定可用距离内,如果是,则使用关于至少一个移动终端辅助设备的信息确定移动终端辅助设备是否已经注册。 移动终端辅助设备存在于预定可用距离内,如果移动终端辅助设备已经注册,则根据移动终端辅助设备控制应用预定安全相关信息。 附图的简要说明 [0028] [0010] 结合附图,通过以下详细描述,本发明的上述和其他方面、特征和优点将更加明显,其中: [0029] 图1A和1B是说明通过使用移动终端辅助设备来操作移动终端的图; [0030] 图2A和2B是说明通过使用移动终端辅助设备来操作移动终端的图; [0031] 图3是示出根据本发明实施例的移动终端辅助设备的框图; [0032] 图4是示出根据本发明实施例的电子笔的框图; [0033] 图5是示出根据本发明实施例的移动终端的框图; [0034] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图; [0035] 图7是示出根据本发明实施例的移动终端的操作的流程图; [0036] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的示图; [0037] 图9A和9B是说明根据本发明实施例的可用距离的图; [0038] 图10是本发明一个实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0039] 图11是本发明另一实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0040] 图12是示出根据本发明实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0041] 图13是示出根据本发明另一实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0042]图14A-14C是根据本发明实施例的判断移动终端辅助设备是否被使用的示意图。 [0043] 图15A-15D是图示根据本发明的实施例的移动终端和移动终端辅助设备的使用的图; [0044] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0045] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0046] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图; 和 [0047] 图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 本发明实施例的详细描述 [0048] 下面结合附图详细描述本发明的实施例。 相同或相似的组件可由相同或相似的附图标记指示,尽管它们在不同的附图中示出。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0049] 在下文中,将参考附图详细描述与本发明相关联的移动终端。 下文描述中所使用的组成元件的后缀,例如“模块”、“单元”,只是为了描述的方便而指定或一起使用,并不具有区分的含义或作用。 [0050] 本发明实施例中描述的移动终端可以实现为便携式电话、智能电话、膝上型计算机、数字广播终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、导航仪 终端等。 然而,对于本领域技术人员显而易见的是,根据本发明的实施例的配置也适用于固定终端,例如数字电视、台式计算机等。 [0051] 本发明实施例的移动终端辅助设备可以包括可以与移动终端通信的电子笔,例如手写笔。 另外,对于本领域技术人员来说显而易见的是,本发明的移动终端辅助装置可以应用于电视、台式电脑等固定终端,也可以应用于移动终端。 [0052] 图3是图示根据本发明实施例的移动终端辅助设备的框图。 [0053] 一种移动终端辅助设备 300 包括一个通信单元 310 , 一段记忆 320 , 和一个控制器 330 . 移动终端辅助设备不限于图3中的元件,还可以包括其他元件,或者可以省略部分元件。 例如移动端辅助设备 300 还可以包括输出单元,例如音频输出模块、警报单元和显示单元,以及用于接收用户输入的用户输入单元。 [0054] 通信单元 310 可以包括至少一个实现移动终端辅助设备之间无线通信的模块 300 和移动终端。 例如,通信单元 310可以包括用于近场通信的短程通信模块。 这里,短距离通信技术可以采用蓝牙、射频识别(RFID)、红外数据协会(IrDA)、超宽带(UWB)、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是蓝牙(BT)模块和蓝牙低功耗(BLE)模块中的至少一种。 [0055] 通信单元 310 可允许移动终端辅助设备 300 移动终端通过与移动终端通信相互注册,如下面更详细的描述。 [0056] 记忆 320 可以存储用于控制器处理和控制的程序 330 并执行暂时存储输入/输出数据(例如,移动终端信息、移动终端识别信息、移动终端辅助设备识别信息、安全相关信息等)的功能。 记忆 320 可以存储数据的使用频率。 [0057] 记忆 320 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,安全数字(SD)存储器、XD存储器等)、随机存储器的至少一种存储介质 存取存储器(RAM)、静态随机存取存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁存储器、磁盘和光盘 . 移动终端辅助设备 300 可关于网络存储操作以提供存储器的存储功能 320 在网上。 [0058] 一般来说,控制器 330 控制移动终端辅助设备的整体操作 300 . 例如,控制器 330 可以控制执行注册移动终端辅助设备的操作 300 和移动终端相互连接。 另外,在使用移动终端辅助设备的情况下 300 通过移动终端与移动终端辅助设备之间的鉴权 300 , 控制器 330 可以控制使用移动终端而无需额外的安全检查过程,这在下面更详细地描述。 [0059] 移动终端辅助设备 300 还可以包括用户输入单元。 用户输入单元生成用于控制用户对移动终端辅助设备的操作的输入数据。 用户输入单元可以包括设置在移动终端辅助设备的前表面、后表面或侧表面上的按钮、触摸传感器(压力型/电容型)、小键盘、圆顶开关、滚轮、滚轮中的至少一个 等,但不限于此。 [0060] 图4是示出根据本发明实施例的电子笔的框图。 [0061] 根据本发明实施例的移动终端辅助设备可以具体化为电子笔 400 ,例如手写笔。 电子笔 400 包括一个通信单元 410 , 一段记忆 420 , 一个控制器 430 , 一个触摸识别单元 440 等,但不限于此。 例如,电子笔 400 还可以包括电源,例如电池 450 ,电源可以接收外部电源和内部电源供应给每个元件以在控制器的控制下运行 430 . 电源可以包括连接端口、电源控制器和充电监控单元中的至少一个,以及电池 450 . [0062] 通信单元 410 可包括至少一个模块,使电子笔之间能够进行无线通信 400 和移动终端。 根据本发明的一个实施例,通信单元 410 可以包括BT模块或BLE模块中的至少一个。 [0063] 通信单元 410 可以让电子笔 400移动终端通过与移动终端通信进行相互注册,如下面更详细的描述。 [0064] 记忆 420 可以存储用于控制器处理和控制的程序 430 并执行临时存储输入/输出数据(例如,关于移动终端的信息、关于移动终端的标识信息、关于移动终端辅助设备的标识信息、安全相关信息等)的功能,如上文详细描述的 . [0065] 一般来说,控制器 430 控制电子笔的整体操作 400 . 例如,控制器 430 可控制执行注册电子笔的操作 400 和移动终端相互连接。 另外,在使用电子笔的情况下 400 通过移动终端与电子笔之间的认证 400 , 控制器 430 可以控制使用移动终端而无需额外的安全检查过程,如下面详细描述的。 [0066] 触摸识别单元 440 可以识别电子笔的触摸信号 400 . 当电子笔的触摸信号 400 是输入,控制器 430 控制根据触摸信号输入执行预定操作。 根据本发明的一个实施例,除了触摸识别单元 440 , 电子笔 400 还可以包括用于生成用户的输入数据的用户输入单元。 用户输入单元可包括设置在电子笔的侧面上的按钮、小键盘、圆顶开关、滚轮、滚轮开关等中的至少一个,但不限于此。 [0067] 图5是图示根据本发明实施例的移动终端的框图。 [0068] 移动终端 500 包括一个通信单元 510 , 一段记忆 520 , 一个控制器 530 , 一个用户输入单元 540 , 和一个输出单元 550 . 图5所示的元件不是移动终端所必需的,移动终端还可以包括其他元件,或者可以省略一些元件。 [0069] 通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 和无线通信系统,或移动终端 500 以及移动终端所在的网络 500 位于。 此外,通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 以及移动终端辅助设备。 例如,通信单元 510 可以包括广播接收模块、移动通信模块、无线上网模块、近距离通信模块、位置信息模块等。 [0070] 广播接收模块通过广播频道从外部广播管理服务器接收广播信号和/或广播相关信息。 广播频道可以包括卫星频道和地面波频道。 移动终端中可以设置至少两个广播接收模块 500 通过至少两个广播频道同时接收广播或者在至少两个广播频道之间切换。 [0071] 移动通信模块向移动通信网络(例如全球移动通信系统(GSM)、码分多址(CDMA) )、宽带码分多址(WCDMA)(但不限于此)。 根据文本/多媒体消息的发送和接收,无线信号可以包括语音呼叫信号、视频呼叫信号或各种数据。 [0072] 移动终端中可以内置无线上网模块,用于连接无线上网 500或外部提供。 无线互联网可能利用无线局域网(WLAN)、Wi-Fi、无线宽带(Wibro)、全球微波接入互操作性(Wimax)、高速下行链路分组接入(HSDPA)、GSM、CDMA、WCDMA、长期 演进(LTE)等。 [0073] 通过 Wibro、HSDPA、GSM、CDMA、WCDMA 和 LTE 的无线互联网连接是由无线移动通信网络实现的。 因此,通过移动通信网络与无线互联网连接的无线互联网模块可以被认为是一种移动通信模块。 [0074] 近距离通信模块是指用于近场通信的模块。 短距离通信技术可以采用BT、RFID、IrDA、UWB、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是BT模块和BLE模块中的至少一种。 [0075] 用户输入单元 540 生成用于控制用户对移动终端的操作的输入数据。 用户输入单元 540 可能包括按钮 543 在移动终端的正面、背面或侧面 500 和触摸传感器(压力式/电容式) 545 . 用户输入单元 540 还可以包括小键盘、圆顶开关、滚轮、滚轮等。 [0076] 输出单元 550 可以产生与视觉、听觉或触觉相关的输出,并且包括显示单元 555 ,但不限于此。 例如,输出单元 550 可以包括音频输出模块、警报模块和触觉模块。 [0077] 显示单元 555 显示(输出)移动端处理的信息 500 . 例如,当移动端 500 处于通话模式时,显示单元 555 显示与电话呼叫相关的用户界面 (UI) 或图形用户界面 (GUI)。 当移动端 500 处于视频通话模式或拍照模式时,显示单元 555 使用 UI 或 GUI 显示拍摄和/或接收的图像。 [0078] 显示单元 555 可以包括液晶显示器(LCD)、薄膜晶体管-LCD(TFT LCD)、有机发光二极管(OLED)、柔性显示器和3D显示器中的至少一种。 [0079] 上述显示器中的一些可以被配置为透明或透光的以通过其观察外部,这被称为透明显示器,典型地包括透明有机发光二极管(TOLED)。 显示单元背面结构 555 也可以配置为透光的。 根据上述结构,用户可以通过显示单元的区域看到终端后面的物体。 555 终端。 [0080] 两个或多个显示单元 555 可根据移动终端类型提供 500 . 例如,多个显示单元可以相互间隔设置,也可以一体设置在同一平面上,也可以设置在移动终端的不同平面上。 500 . [0081] 在显示单元的情况下 555 和触摸传感器 545 ,它们以层结构或一体形成(以下称为“触摸屏”),显示单元 555 既可以作为输入设备,也可以作为输出设备。 触摸传感器可以形成为与显示单元的层压体 555 在例如触摸膜、触摸片、触摸板等的情况下,或者可以与显示单元一体形成 555 . [0082] 触摸传感器可以被配置为转换作用在显示单元的特定部分上的压力变化 555 或显示单元特定部分产生的电容变化 555 到电信号。 触摸传感器可以被配置为检测触摸压力以及触摸点和触摸面积。 [0083]在触摸传感器上有触摸输入时,相应的信号被传输到触摸控制器。 触摸控制器处理信号并将相应的数据传输给控制器 530 . 因此,控制器 530 可以识别显示单元的哪个区域 555 被感动了。 [0084] 虽然未在图中示出,但是接近传感器可以设置在移动终端的触摸屏内部或周围 500 . 接近传感器可以在没有机械接触的情况下通过使用电磁场力或红外线来检测接近预定检测表面的物体或接近传感器周围的物体。 与接触式传感器相比,接近传感器具有较长的使用寿命和多种用途。 [0085] 接近传感器可以包括透明光电传感器、直接反射光电传感器、镜面反射光电传感器、高频振荡接近传感器、电容式接近传感器、磁性接近传感器、红外接近传感器等。 [0086] 在下文中,为了便于解释,术语“接近触摸”可以指指针接近安装有接近传感器的触摸屏从而在没有接触的情况下被识别的操作,术语“接触触摸”可以指代 指针在屏幕上的触摸操作。 指针在触摸屏上的接近触摸点可以表示接近触摸状态下指针在屏幕上垂直对应的位置的点。 在下文中,术语“触摸”可以包括接近触摸以及接触触摸。 [0087] 根据本发明的实施例,接近触摸可以包括悬停输入。 [0088] 接近传感器检测接近触摸和接近触摸模式(例如,接近触摸距离、接近触摸方向、接近触摸速度、接近触摸时间、接近触摸点、接近触摸移动状态等) . 可以在触摸屏上显示与检测到的接近触摸和接近触摸模式相对应的信息。 [0089] 记忆 520 可以存储用于控制器处理和控制的程序 530 并执行临时存储输入/输出数据(例如,电话号码列表、消息、音频、静止图像、运动图像、关于移动终端的信息、关于移动终端的识别信息、关于移动终端辅助设备的信息、 安全相关信息等)。 记忆 520 可以存储数据的使用频率。 [0090] 此外,内存 520 可以存储关于在触摸屏上的触摸输入时输出的各种振动和声音的数据。 [0091] 记忆 520 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,SD存储器、XD存储器等)、RAM、SRAM的至少一种存储介质, ROM、EEPROM、PROM、磁存储器、磁盘和光盘。 手机端 500 可关于网络存储操作以提供存储器的存储功能 520 在网上。 [0092] 手机端 500 还可以包括用于输入音频信号或视频信号的音频/视频(A/V)输入单元,以及用于产生感测信号以感测移动终端的当前状态的感测单元 500 ,例如,移动终端的打开/关闭状态 500 , 移动端的位置 500 、用户的接触、移动终端的方向、移动终端的加减速,从而控制移动终端的操作 500 . [0093] 此外,移动端 500 可以包括接口单元,该接口单元为与移动终端连接的所有外部设备起到通路的作用 500 . 接口单元从外部设备接收数据或电源,并将其传输到移动终端的每个元素 500. 接口单元还允许数据从移动终端传输到外部设备 500 . 例如,接口单元可以包括无线/有线耳机端口、外部充电端口、无线/有线数据端口、存储卡端口、用于连接具有识别模块的设备的端口、音频输入/输出端口(I /O)端口、视频I/O端口、耳机端口等。 [0094] 此外,移动端 500 还可以包括电源,其接收外部电源和内部电源并将其提供给每个元件以在控制器的控制下运行 530 . 电源可以包括例如电池、连接端口、电源控制器和充电监控单元。 [0095] 电池可以是可充电的内置型,并且可以结合到终端的主体以可拆卸地充电。 连接端口可以是外部充电器电连接到的接口之一,以便提供用于电池充电的电力。 [0096] 上述实施例可以通过使用例如软件、硬件或其组合由计算机可读或等效介质来实现。 [0097] 在硬件方面,本发明实施例可以采用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理器件(DSPD)、可编程逻辑器件(PLD)中的至少一种来实现, 现场可编程门阵列 (FPGA)、处理器、控制器、微控制器、微处理器或用于执行其他功能的电气单元。 本发明的一些实施例可以通过控制器来实现 530 . [0098] 在软件方面,本发明实施例的流程和功能可以通过单独的软件模块来实现。 每个软件模块可以执行这里描述的至少一个功能和操作。 软件代码可以由合适的程序语言编写的软件应用程序来实现。 软件代码可以存储在内存中 520 并且可以由控制器执行 530 . [0099] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图。 [0100] 参见图6,在步骤 610 ,移动终端辅助设备的控制器控制将至少一个移动终端的信息存储在存储器中。 即,移动终端辅助设备通过移动终端辅助设备与移动终端之间的注册,存储有至少一个要使用该移动终端辅助设备的移动终端的信息。 当用户试图通过使用移动终端辅助设备连接已注册的移动终端时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0101] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0102] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行鉴权的情况下,控制移动终端辅助设备存储该信息。 移动终端。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入安全信息例如预定密码来识别用户,然后移动终端发送其自身的信息。 将自己的识别信息发送给移动终端辅助设备。 然后,移动终端辅助设备将接收到的移动终端的标识信息存储在存储器中。 [0103]移动终端的信息例如是移动终端的标识或随机生成的固有号码,但不限于此。 [0104] 根据本发明的一个实施例,移动终端辅助设备与移动终端之间的注册由单独的服务器执行。 例如,当移动终端和移动终端辅助设备通过近距离通信连接时,通过输入预定的安全信息来识别用户,然后移动终端辅助设备将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端辅助设备将移动终端的信息发送给服务器,或者移动终端将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 然后,在通过与移动终端或移动终端辅助设备的无线和有线通信使用移动终端或移动终端辅助设备的情况下,服务器发送关于这些设备是否已经注册到彼此的信息。 [0105] 根据本发明的一个实施例,在步骤 610 ,移动终端辅助设备还存储有至少一个移动终端的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端辅助设备存储移动终端设置信息以允许用户根据用户的期望设置移动终端或内容。 [0106] 返回参考图6,在步骤 620 ,移动终端辅助设备的控制器判断在预定可用距离内是否存在移动终端。 根据本发明的实施例,移动终端辅助设备通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端是否存在于预定可用距离内。 信号强度例如是接收信号强度指示符(RSSI)。 [0107] 根据本发明的一个实施例,当检测到使用移动终端辅助设备的信号时,移动终端辅助设备测量信号强度。 例如,当通过包括在移动终端辅助设备中的用户输入单元输入用户指令时,控制器确定移动终端是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0108] 如果移动终端存在于预定可用距离内,则移动终端辅助设备的控制器基于步骤中存储的至少一个移动终端的信息来判断检测到的移动终端是否为已注册的移动终端 610 . 例如,移动终端辅助设备的控制器判断是否在步骤中检测到移动终端的标识信息 620与移动终端辅助设备的存储器中存储的移动终端的标识信息相同。 可选地,控制器判断是否为随机生成的内在数,该内在数存储在步骤检测到的移动终端中 620 与随机生成的固有数相同,存储在移动终端辅助设备的内存中。 [0109] 根据本发明的一个实施例,如果检测到的移动终端是已注册的移动终端,则控制器向移动终端发送安全相关信息,步骤 640 . [0110] 图中示出了安全相关信息存储在移动终端辅助设备中,但本发明不限于此。 例如,移动终端可以在移动终端与移动终端辅助设备注册的过程中存储安全相关信息,步骤 610 . 或者,安全相关信息可以存储在服务器中。 在这种情况下,步骤 640 ,其中安全相关信息被发送到移动终端,可以被省略。 [0111] 图7是示出根据本发明实施例的移动终端的操作的流程图。 [0112] 参见图7,在步骤 710 ,移动终端的控制器控制在存储器中存储关于至少一个移动终端辅助设备的信息。 即,移动终端通过移动终端辅助设备与移动终端之间的注册,存储至少一个移动终端辅助设备的信息,该移动终端辅助设备将与移动终端进行注册。 当用户试图通过使用移动终端辅助设备与移动终端连接时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0113] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0114] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行认证的情况下,控制移动终端将该信息存储在移动终端上。 终端辅助设备。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入预定密码等安全信息来识别用户,然后移动终端辅助设备发送自己的标识 信息到移动终端。 然后,移动终端将接收到的移动终端辅助设备的标识信息存储在存储器中。 [0115] 移动终端辅助设备的信息例如为移动终端辅助设备的标识或随机生成的固有编号,但不限于此。 [0116]根据本发明的一个实施例,移动终端辅助设备和移动终端之间的注册也可以由单独的服务器进行,​​如上面关于图6所描述的。例如,当移动终端和移动终端 辅助设备通过短距离通信相互连接,通过输入预定的安全信息来识别用户,然后移动终端将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端将移动终端辅助设备的信息发送给服务器,或者移动终端辅助设备将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 此外,在通过与移动终端和移动终端辅助设备的无线和有线通信来使用移动终端或移动终端辅助设备的情况下,服务器发送关于设备是否已经相互注册的信息。 [0117] 根据本发明的一个实施例,在步骤 710 ,移动终端还存储有至少一个移动终端辅助设备的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端存储移动终端设置信息以允许用户根据移动终端辅助设备根据用户的期望设置移动终端或内容。 [0118] 再参考图7,在步骤 720 ,移动终端的控制器判断预定可用距离内是否存在移动终端辅助设备。 根据本发明的实施例,移动终端通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端辅助设备是否存在于预定可用距离内。 信号的强度例如是RSSI。 [0119] 根据本发明的一个实施例,当检测到使用移动终端的信号时,由移动终端测量信号强度。 例如,当通过包括在移动终端中的用户输入单元输入用户指令时,控制器确定移动终端辅助设备是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0120] 如果移动终端辅助设备存在于预定可用距离内,则在步骤 730 ,移动终端的控制器根据步骤中存储的至少一个移动终端辅助设备的信息,判断检测到的移动终端辅助设备是否为已注册的移动终端辅助设备 710 . 例如,移动终端的控制器判断是否在步骤中检测到移动终端辅助设备的标识信息 720与移动终端辅助设备的标识信息相同,存储在移动终端的内存中。 或者,控制器判断是否为随机生成的固有数,存储在步骤检测到的移动终端辅助设备中 720 与随机生成的固有数相同,存储在移动终端的内存中。 [0121] 在步 740 ,移动终端应用存储在步骤中的移动终端辅助设备上的安全相关信息 710 . [0122] 图中示出了安全相关信息存储在移动终端中,但本发明不限于此。 根据本发明的一个实施例,移动终端辅助设备或服务器存储移动终端辅助设备的安全相关信息。 若确定步骤中检测到的移动终端辅助设备 720 为注册的移动端辅助设备,在步骤 730 、 移动终端的通信单元接收来自移动终端辅助设备或服务器的安全相关信息。 移动终端的控制器应用接收到的安全相关信息。 [0123] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的图。 图9A和9B是图示根据本发明实施例的可用距离的图。 [0124] 参考图8A,移动终端之间的注册 800 以及移动终端辅助设备 850 被处理。 根据本发明的一个实施例,移动终端辅助设备 850 具体表现为电子笔,包括手写笔。 [0125] 移动端之间的注册 800 以及移动终端辅助设备 850 移动端通信时触发 800 以及移动终端辅助设备 850 首次制作,例如,通过 BT 或 BTLE 模块的短距离通信。 [0126] 根据本发明的一个实施例,移动终端之间的注册过程 800 以及移动终端辅助设备 850 执行,当注册移动终端辅助设备的消息 850 输入到移动端 800 . 注册移动终端辅助设备的消息以弹窗形式显示,但不限于此,消息可以为移动终端按键输入的形式。 [0127] 移动端之间的注册流程 800 以及移动终端辅助设备 850 执行,当移动终端辅助设备通过移动终端认证时 800 通过安全信息对用户进行标识,如图8A所示。 例如,当在移动终端中输入预定密码或特定图案时 800 , 移动端之间的注册 800 以及移动终端辅助设备 850 被处理。 [0128] 移动端之间注册时 800 以及移动终端辅助设备 850 处理完毕,移动端 800 在移动终端辅助设备上存储信息 850 . 移动端 800 接收移动终端的标识信息 800 从移动端辅助设备 850 通过通信单元。 另外,根据本发明的一个实施例,移动终端辅助设备 850 在移动端存储信息 800 . 移动终端辅助设备 850 接收移动终端辅助设备的识别信息 850 从移动端 800 通过通信单元。 或者,根据本发明的一个实施例,移动终端 800以及移动终端辅助设备 850 存储随机生成的相同内在数。 [0129] 根据本发明的一个实施例,移动终端和移动终端辅助设备之间的注册是由单独的服务器进行的,这在上面参考图6和图7进行了详细描述。 [0130] 存储的信息包括移动终端的安全相关信息 800 或移动终端辅助设备 850 . 即该信息中包含解除移动终端锁定状态的密码 800 或移动终端辅助设备 850 、特定应用程序的密码以及电子邮件和 SNS 的登录信息。 例如,当多个移动终端辅助设备 850 已注册到移动终端 800 , 移动端 800 对已注册的移动终端辅助设备的使用进行不同的限制 850 . 即移动端 800 不允许第一移动终端辅助设备访问特定应用,而允许第二移动终端辅助设备访问所有应用。 当第一移动终端辅助设备注册到移动终端时,存储用于限制第一移动终端辅助设备访问特定应用的安全信息。 进一步地,当第二移动终端辅助设备注册到移动终端时,存储允许第二移动终端辅助设备访问所有应用的安全信息。 [0131] 如图8B所示,如果移动终端 800 以及移动终端辅助设备 850 位于预定的可用距离内 870 , 它们可能相互关联。 [0132] 根据本发明的一个实施例,移动终端 800 以及移动终端辅助设备 850 通过通信单元中包含的短距离通信模块测量信号强度,判断移动终端是否 800 以及移动终端辅助设备 850 存在于预定可用距离内 870 基于测量的信号。 测量信号强度,当移动终端辅助设备有信号使用时 850 或移动端 800 根据本发明的实施例,检测到。 [0133] 如图9A所示,移动终端 900 测量移动终端辅助设备的通信信号强度 950 . RSSI 是通过短距离通信模块测量的。 根据本发明的一个实施例,它被配置为即使移动终端 900 以及移动终端辅助设备 950 存在于连接距离内 980 他们之间可以通过短距离通信进行通信,只有当移动终端时,他们才能真正相互连接 900 以及移动终端辅助设备 950 存在于预定的可用距离内 970 . 因此,第二个连接装置 960 无法与移动端连接 900 . [0134] 如图9B所示,由于信号强度根据与移动终端的距离而降低 900 , 判断移动终端辅助设备是否 950 存在于预定可用距离内 970 从移动端 900 通过测量信号的强度。 [0135] 如移动端辅助设备 950 存在于可用距离之外 980 , 移动端 900 以及移动终端辅助设备 950 完全断开连接。 根据本发明实施例,确定移动终端辅助设备 950 丢失,如下面更详细的描述。 [0136] 回到图8B,如果移动终端 800以及移动终端辅助设备 850 存在于预定可用距离内 870 , 移动端 800 以及移动终端辅助设备 850 确定它们是否已经相对于彼此注册,如上文关于图6和图7所述。 [0137] 如果确定移动端 800 以及移动终端辅助设备 850 已经相互注册,移动端 800 基于移动终端上的安全相关信息使用 800 或移动终端辅助设备 850 . [0138] 图10是示出根据本发明实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0139] 根据本发明的一个实施例,移动终端辅助设备体现为包括触摸传感器的电子笔。 在移动终端与移动终端辅助设备接触的情况下,确定移动终端和移动终端辅助设备正在使用中。 [0140] 即使移动终端辅助设备输入了触摸信号,移动终端辅助设备的控制器也无法判断移动终端辅助设备触摸了哪个物体。 也就是说,即使移动终端辅助设备在移动终端以外的物体上进行触摸,然后通过触摸输入单元输入触摸信号,移动终端辅助设备也不能识别物体,而是感应到触摸信号。 只要。 [0141] 同样,当移动终端接收到包括触摸传感器的触摸屏上的触摸信号时,移动终端无法确定是哪个物体触摸了触摸屏。 也就是说,即使是移动终端的触摸屏上的触摸信号,也可能是移动终端辅助设备以外的其他指针,例如手指输入的触摸信号。 在这种情况下,移动终端仅确定触摸点,而不能确定哪个物体产生触摸信号。 [0142] 相应地,为了判断移动终端辅助设备是否被使用,需要预先判断移动终端上的触摸是否是由移动终端辅助设备进行的。 [0143] 参见图10,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1010 . 控制器提取关于触摸信号的检测的时间信息。 [0144] 在步 1020 ,移动终端辅助设备从移动终端接收移动终端检测到触摸信号的时间的触摸时间信息。 即,当触摸信号也输入到移动终端时,移动终端将输入触摸信号的时间信息发送给移动终端辅助设备,移动终端辅助设备接收该信息。 [0145] 在步 1030 ,移动终端辅助设备比较步骤中接收到的移动终端检测到的触摸信号的时间信息 1020 ,带有step的移动终端辅助设备中检测到触摸信号的时间信息 1010 . 即,移动终端辅助设备判断触摸信号在移动终端辅助设备中的输入时间与触摸信号在移动终端中的输入时间是否相同。 [0146] 如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间不同,则确定输入到移动终端辅助设备的触摸信号是触摸产生的,而不是触摸产生的。 移动终端,而是其他带有移动终端辅助设备的对象。 [0147]如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间相同,则控制器确定移动终端辅助设备触摸到移动终端,进而移动终端。 辅助设备正在使用中。 [0148] 此外,虽然未在图中示出,但是根据本发明的实施例,移动终端辅助设备将确定结果发送到移动终端。 [0149] 图11是示出根据本发明另一实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0150] 参见图11,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1110 . 控制器提取关于触摸信号检测的时间信息。 [0151] 在步 1120 ,移动终端辅助设备将检测到触摸信号的时间信息发送给移动终端。 另外,移动终端辅助设备从移动终端接收移动终端辅助设备是否触摸移动终端的信息,步骤 1130 . [0152] 在图11的实施例中,与图10的实施例不同的是,移动终端判断移动终端辅助设备是否被使用过。 另外,移动终端用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端辅助设备。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端被配置为不向移动终端辅助设备发送单独的响应信号。 [0153] 移动终端辅助设备在步骤中利用接收到的信息判断移动终端辅助设备是否已经针对移动终端使用过 1130 . [0154] 图12是示出根据本发明实施例的确定移动终端辅助设备是否被移动终端使用的流程图。 [0155] 参见图12,移动终端检测针对移动终端的触摸信号,步骤 1210 . 控制器提取关于触摸信号的检测的时间信息。 [0156] 在步 1220 ,移动终端从移动终端辅助设备接收到移动终端辅助设备检测到触摸信号的时间信息。 即,当移动终端辅助设备也输入了触摸信号时,移动终端辅助设备向移动终端发送触摸信号输入时间的信息,移动终端接收该信息。 [0157] 在步 1230 ,移动终端比对步骤中接收到的移动终端辅助设备检测到的触摸信号的时间信息 1220 , 与检测移动终端辅助设备触摸信号的时间信息同步 1210 . 即移动终端可以判断触摸信号在移动终端中的输入时间与触摸信号在移动终端辅助设备中的输入时间是否相同。 [0158] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间不同,则确定移动终端辅助设备中的触摸信号是触摸产生的,而不是移动终端产生的。 终端,而是与移动终端辅助设备的其他对象。 [0159] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间相同,则移动终端的控制器确定移动终端辅助设备触摸了移动终端, 步骤 1240,则该移动终端辅助设备正在使用中。 [0160] 此外,根据本发明的实施例,移动终端将确定结果发送到移动终端辅助设备。 [0161] 图13是示出根据本发明另一实施例的确定移动终端是否辅助移动终端的流程图。 [0162] 参见图13,移动终端检测移动终端的触摸信号,步骤 1310 . 此时,控制器提取触摸信号检测的时间信息。 [0163] 在步 1320 ,移动终端将检测到触摸信号的时间信息发送给移动终端辅助设备。 另外,移动终端从移动终端辅助设备接收移动终端辅助设备是否触摸了移动终端的信息,步骤 1330 . [0164] 在图13的实施例中,与图12的实施例不同的是,移动终端辅助设备判断移动终端辅助设备是否被使用过。 另外,移动终端辅助设备用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端辅助设备被配置为不向移动终端发送单独的响应信号。 [0165] 移动终端利用接收到的信息判断移动终端辅助设备是否针对移动终端使用过, 1330 . [0166] 图14A-14C是图示根据本发明实施例的确定移动终端辅助设备是否已经被使用的图。 [0167] 参见图14A,移动终端辅助设备 1450 移动终端屏幕进入预定可用距离内 1400 被关闭。 移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于预定的可用距离内。 比如移动端 1400 通过与移动终端辅助设备的近距离通信测量RSSI 1450 , 判断移动端辅助设备是否 1450 基于信号的测量强度,存在于预定可用距离内。 [0168] 即使是移动端 1400 以及移动终端辅助设备 1450 存在于预定的可用距离内,根据本发明的一个实施例,移动终端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 仅当移动终端辅助设备存在于预定可用距离内时 1450 正在使用中。 [0169] 如图14B所示,根据参考图10至图13描述的方法确定移动终端辅助设备的使用。 [0170] 例如,当移动终端辅助设备 1450 触摸移动终端 1400 , 移动端辅助设备 1450 检测触摸信号。 移动终端辅助设备 1450 提取触摸信号检测的时间信息。 此外,移动终端 1400 还提取移动终端辅助设备触摸时检测到触摸信号的时间信息 1450 . [0171] 移动终端辅助设备 1450 传输检测到移动终端辅助设备触摸信号的信​​息 1450 到手机端 1400. 或者,根据本发明的一个实施例,移动终端 1400 传输检测到移动终端触摸信号的信​​息 1400 到移动端辅助设备 1450 . [0172] 手机端 1400 比较触摸信号输入到移动终端辅助设备的时间 1450 ,从移动终端辅助设备接收 1450 , 随着触摸信号输入到移动端的时间 1400 . 或者,根据本发明的一个实施例,移动终端辅助设备 1450 比较触摸信号输入到移动端的时间 1400 , 从移动端接收 1400 , 随着触摸信号输入到移动终端辅助设备的时间 1450 . [0173] 如果触摸信号输入到移动终端 1400 以及移动终端辅助设备 1450 同时,移动端的控制器 1400 或移动终端辅助设备 1450 确定移动终端辅助设备 1450 触动了移动端 1400 . [0174] 随后,移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 和移动端 1400 ,它们存在于预定的可用距离内,已经相对于彼此注册。 如果确定移动端 1400 以及移动终端辅助设备 1450 已经相对于彼此注册,如图14C所示,移动终端 1400 可以通过应用预定的安全相关信息将其转为使用状态。 [0175] 根据本发明的一个实施例,移动终端后 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于可用距离内,若移动终端辅助设备 1450 存在于可用距离内,判断是否存在移动终端辅助设备 1450 正在使用中。 [0176] 例如,即使是移动终端辅助设备 1450 在移动终端的可用距离内被检测到 1400 ,如果是移动端辅助设备 1450 未使用时,无需判断是否为移动终端辅助设备 1450 已注册。 反之,如果移动终端辅助设备 1450 正在使用中,应判断是否为移动终端辅助设备 1450 已注册。 据此,移动终端 1400 判断移动端辅助设备是否 1450 判断是否为移动终端辅助设备后注册的 1450 是否存在于可用距离内以及检测到的移动终端辅助设备是否存在 1450 正在使用中。 [0177] 图15A-15D是图示根据本发明实施例的移动终端和移动终端辅助设备的使用的图。 [0178] 参考图15A,一个用户针对一个移动终端使用一个移动终端辅助设备。 用户根据他或她的需要配置移动终端。 相应地,在移动终端与移动终端辅助设备之间的注册过程中,可以将包括移动终端的设置信息在内的安全相关信息存储在移动终端或移动终端辅助设备中。 之后,当用户通过移动终端辅助设备使用移动终端时,根据预先存储的设置信息对移动终端进行配置,从而使用户能够方便地使用移动终端。 [0179]或者,如图15B所示,一个用户可以通过使用一个移动终端辅助设备来使用多个移动终端。 用户在多个移动终端上使用具有一致性的特定信息。 因此,根据本发明的实施例,用户在移动终端辅助设备中存储他或她想要的包括设置信息的安全信息。 另外,当用户从第一移动终端切换到第二移动终端时,用户根据存储在移动终端辅助设备中的设置信息配置和使用第二移动终端。 [0180] 如图15C所示,多个用户通过各自的移动终端辅助设备使用一个移动终端。 用户在保护隐私的同时与其他用户共享移动终端的内容。 相应地,每个用户在移动终端辅助设备中存储包括密码的安全相关信息,该密码防止其他人查看他或她在移动终端中的私人信息。 备选地,可以配置为将安全相关信息存储在移动终端中,并且仅当预定的移动终端辅助设备与移动终端连接时才去激活安全。 [0181] 如图15D所示,多个用户通过多个移动终端辅助设备使用多个移动终端。 在这种情况下,用户在多个移动终端上使用一致的特定信息,并在保护隐私的同时与其他用户共享移动终端的内容。 在这种情况下,每个用户在移动终端辅助设备中存储安全相关信息,包括他或她想要的设置信息和防止其他人查看他或她在移动终端中的私人信息的密码。 根据本发明实施例,安全相关信息存储在移动终端中。 [0182] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图。 [0183] 参见图16,在步骤 1610 ,移动终端辅助设备判断注册的移动终端是否存在预定的连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0184] 如果预定连接距离内不存在移动终端,则确定移动终端辅助设备与移动终端断开连接,移动终端辅助设备删除内存中存储的移动终端信息, 步骤 1630 . [0185] 根据本发明的一个实施例,当确定在连接距离内不存在已注册的移动终端时,移动终端辅助设备判断在预定断开参考时间内是否检测到移动终端,步骤 1620 . 即,移动终端辅助设备判断移动终端是否在预定断开参考时间内不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端,则移动终端辅助设备删除正在运行的移动终端的信息 1630 . [0186] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除移动终端辅助设备中存储的第一移动终端的信息。 [0187]然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 此时,移动终端辅助设备在第一移动终端断开连接后,判断第二移动终端是否连接断开参考时间 1620 . 判断结果为,如果第二移动终端在预定的参考时间内连接上,则移动终端辅助设备不删除第一移动终端的信息,而是保留第一移动终端的信息。 [0188] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户使用多个移动终端的流程图。 [0189] 参见图17,在步骤 1710 ,移动终端判断注册的移动终端辅助设备是否存在预定连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定的连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0190] 若预定连接距离内不存在移动终端辅助设备,则确定移动终端辅助设备与移动终端断开连接,移动终端删除内存中存储的移动终端辅助设备信息, 步 1730 . [0191] 根据本发明的一个实施例,当确定连接距离内不存在已注册的移动终端辅助设备时,移动终端判断是否在预定断开参考时间内检测到移动终端辅助设备。 也就是说,移动终端可以判断在预定断开参考时间内移动终端辅助设备是否不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端辅助设备,则移动终端删除正在运行的移动终端辅助设备的信息 1730 . [0192] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除第一移动终端中存储的移动终端辅助设备信息。 [0193] 然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 第一移动终端在与第一移动终端断开后,判断移动终端辅助设备是否与第二移动终端连接,步骤 1720 . 判断结果为,若移动终端附属设备与第二移动终端连接,则第一移动终端不删除,而是保留移动终端附属设备的信息。 [0194]第一移动终端从服务器接收移动终端辅助设备是否与第二移动终端连接的信息。 也就是说,当移动终端辅助设备与至少一个移动终端相互注册时,服务器存储至少一个移动终端与移动终端辅助设备的注册状态信息。 另外,移动终端或移动终端辅助设备周期性或特定事件发生时,向服务器发送移动终端辅助设备与哪个移动终端连接以及移动终端辅助设备是否在使用中的信息。 进一步地,服务器存储接收到的移动终端辅助设备和移动终端的使用状态信息。 [0195] 如果确定移动终端辅助设备与所有移动终端断开连接,不再使用,根据本发明实施例,移动终端和移动终端辅助设备的注册状态信息 被删除。 根据本发明的一个实施例,服务器向移动终端或移动终端辅助设备发送注销指令。 之后,接收到注销指令的移动终端或移动终端附属设备删除存储在移动终端附属设备或移动终端上的信息。 [0196] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图。 [0197] 参考图18,服务器 1830 管理移动终端辅助设备相互注册信息 1850 以及至少一台移动终端 1810 和/或 1820 . [0198] 移动终端辅助设备 1850 离开第二移动终端的可用距离区域 1820 , 而移动端辅助设备 1850 与第二移动终端结合使用 1820 . 随后,移动终端辅助设备 1850 进入第一移动终端的可用距离区域 1810 与第一移动终端连接 1810 用来。 [0199] 移动终端 1810 和 1820 传输是否与移动终端辅助设备连接的信息 1850 到服务器 1830 . 服务器 1830 从移动终端接收关于连接状态的信息 1810 和 1820 , 并存储相同的。 [0200] 根据本发明的一个实施例,第二移动终端 1820 接收到移动终端辅助设备的信息 1850 与第二移动终端断开连接 1820 , 但它与第一​​移动终端连接 1810 , 从服务器 1830 . 即第二移动终端 1820 确定移动终端辅助设备 1850 未丢失但与第一移动终端连接 1810 在使用中。 因此,第二移动终端 1820 不删除但维护移动终端辅助设备上的信息 1850 . [0201] 然而,虽然未在图中示出,但是当移动终端辅助设备 1850 连第一个移动终端都没有连接 1810 , 第二移动端 1820 接收到移动终端辅助设备的信息 1850 从服务器断开所有移动终端 1830 . 第二移动终端 1820 确定移动终端辅助设备 1850 丢失了。 第二移动终端 1820 删除移动终端辅助设备信息 1850 以及与安全相关的信息。 第一个移动终端 1820 同时删除移动端辅助设备信息 1850 以及与安全相关的信息。 [0202]图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 [0203] 参见图19,移动终端辅助设备 1950 管理关于至少一个移动终端的注册信息 1910 或者 1920 . [0204] 移动终端辅助设备 1950 确定与移动终端的连接状态 1910 和 1920 . [0205] 例如移动端辅助设备 1950 离开第二移动终端的可用距离区域 1920 而移动终端辅助设备 1950 与第二移动终端结合使用 1920 . 随后,移动终端辅助设备 1950 进入第一移动终端的可用距离区域 1910 从而与第一移动终端连接 1910 用来。 [0206] 根据本发明的一个实施例,移动终端辅助设备 1950 判断移动端辅助设备是否 1950 与第一移动终端连接 1910 在预定的断开时间内。 即如果移动终端辅助设备 1950 与第二移动终端断开连接 1920 , 并与第一移动终端相连 1910 , 移动端辅助设备 1950 不认为丢失。 据此,移动终端辅助设备 1950 不删除但维护移动终端上的信息 1910 和 1920 以及与安全相关的信息。 [0207] 然而,当移动终端辅助设备 1950 连第一个移动终端都没有连接 1910 , 移动端辅助设备 1950 因未与任何移动终端连接,确定丢失。 移动终端辅助设备 1950 删除手机端信息 1910 和 1920 ,以及与安全相关的信息。 [0208] 根据本发明的一个实施例,在移动终端中注册移动终端辅助设备时,可以将电子邮件、SNS等应用程序的账户信息存储在移动终端辅助设备的内存中。 移动终端辅助设备在使用移动终端时,移动终端辅助设备可以将存储的账户信息发送给移动终端。 移动终端可以根据接收到的账号信息,自动登录对应的账号,无需输入登录密码。 [0209] 或者,根据本发明的一个实施例,移动终端辅助设备存储移动终端锁定状态解除的信息。 此时,在通过移动终端辅助设备的特定按键开启移动终端的显示单元,并通过移动终端辅助设备触摸移动终端的显示单元的情况下,移动终端可以 无需输入密码即可转换为等待模式。 [0210] 另外,根据本发明的一个实施例,在移动终端和移动终端辅助设备在使用过程中持续测量RSSI,从而可以判断移动终端辅助设备是否存在于预定的可用距离内。 如果判断结果为移动终端辅助设备在可用距离内,则确定移动终端辅助设备正在使用中,从而可以控制移动终端的显示单元保持开启。 [0211] 根据本发明的一个实施例,在使用移动终端进行支付时,使用已注册的移动终端辅助设备可以很容易地批准支付,或者只有通过签名等安全过程才能批准支付。 通过已注册的移动终端辅助设备进行。 [0212]此外,根据本发明的一个实施例,通过输入单元放大或缩小显示在移动终端的显示单元上的特定对象,例如移动终端辅助设备上的按钮。 [0213] 此外,根据本发明的实施例,所描述的方法可以通过记录有程序的记录介质中的计算机可读代码来实现。 计算机可读介质包括其中存储有计算机系统可读数据的所有类型的记录设备。 计算机可读记录介质可以包括ROM、RAM、CD-ROM、磁带、软盘、光学数据存储器等。 计算机可读记录介质可以以载波的形式实现(例如,通过互联网传输)。 计算机可以包括终端的控制器或移动终端辅助设备的控制器。 [0214] 对于本领域的技术人员来说显而易见的是,在不脱离本发明的范围和本质特征的情况下可以进行各种修改。 [0215] 虽然本发明已参照其某些实施例进行了展示和描述,但本领域技术人员将理解,在不脱离本发明所定义的精神和范围的情况下,可以在其中进行形式和细节的各种改变 附加索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.272 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.274 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.274 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.275 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.276 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.276 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.277 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.277 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.278 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.287 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.287 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.287 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.288 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.289 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.289 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270635(Integer), KR1020150041337A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.299 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.299 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.299 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270635(Integer), KR102138034B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.309 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.310 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.310 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270635(Integer), US20150099486A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.320 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.320 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.320 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270635(Integer), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.332 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.333 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.333 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9749858B2(String), US9749858B2(String), 1503936000(Integer), 270635(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.342 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.343 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.343 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.345 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.347 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.347 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.348 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.349 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.349 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.350 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.351 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.351 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.358 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.358 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.359 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.360 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.361 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.362 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184952(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.363 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.364 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.364 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.371 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.372 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.372 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.373 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.373 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.374 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.375 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.375 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.376 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.376 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.377 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.378 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.379 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.379 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.379 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.386 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.387 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.388 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.389 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.390 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.390 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.391 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.391 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.392 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.399 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.402 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.402 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.404 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.405 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.406 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Multi-standby mobile terminal and method of performing conference call using the same(String), 多待移动终端及使用该移动终端进行电话会议的方法(String), US20090186607A1(String), A multi-standby mobile terminal and a method for performing a conference call using the same are provided. The method of performing a conference call includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal, requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network, and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 提供了一种多待移动终端和使用该多待移动终端进行电话会议的方法。 执行电话会议的方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端是多待移动终端,通过第三者请求与第二移动终端的通信。 移动终端存在于第二无线通信网络中,并且通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议,当 通信请求为电话会议请求,将合成声音信号发送给第三移动终端。(String), US12/346068(String), 1230566400(Integer), US20090186607A1(String), 1248278400(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 9(Integer), US20030072421A1 | US20030092433A1 | US20060291419A1 | US20070082699A1 | US20070111743A1 | US20090291675A1 | US6904023B2 | US7869806B2 | US8244228B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.416 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.417 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.417 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.419 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.420 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.420 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d29be91abe97477fbbbd52cb18b5bda8.png(String), 184953(Integer), d29be91abe97477fbbbd52cb18b5bda8.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.429 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.430 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.430 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.432 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.432 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.433 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Multi-standby mobile terminal and method of performing conference call using the same(String), 多待移动终端及使用该移动终端进行电话会议的方法(String), US20090186607A1(String), A multi-standby mobile terminal and a method for performing a conference call using the same are provided. The method of performing a conference call includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal, requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network, and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 提供了一种多待移动终端和使用该多待移动终端进行电话会议的方法。 执行电话会议的方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端是多待移动终端,通过第三者请求与第二移动终端的通信。 移动终端存在于第二无线通信网络中,并且通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议,当 通信请求为电话会议请求,将合成声音信号发送给第三移动终端。(String), US12/346068(String), 1230566400(Integer), US20090186607A1(String), 1248278400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 9(Integer), US20030072421A1 | US20030092433A1 | US20060291419A1 | US20070082699A1 | US20070111743A1 | US20090291675A1 | US6904023B2 | US7869806B2 | US8244228B1(String), \20230420\d29be91abe97477fbbbd52cb18b5bda8.png(String), 20(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.442 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.442 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.443 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.444 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.445 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.445 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 1. A multi-standby mobile terminal comprising:a first communication module for forming a communication channel with a first wireless communication network;a second communication module for forming a communication channel with a second wireless communication network; anda first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and for outputting the synthesized sound signal to the second communication module.(String), 1.一种进行电话会议的方法,该方法包括:连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端包括多待移动终端;通过存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信;和当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成为第二移动终端的第一混音器中的合成声音信号来执行电话会议,以及将合成后的声音信号发送给第三移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.445 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 2. The multi-standby mobile terminal of claim 1, further comprising a second audio mixer for synthesizing sound signals, input from the first communication module and the second communication module, to a synthesized sound signal, and outputting the synthesized sound signal to a speaker.(String), 12.如权利要求11所述的方法,其中电话会议的执行还包括如果第一移动终端和第二移动终端之间的通信终止,则终止第三混音器的功能。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.446 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 3. The multi-standby mobile terminal of claim 2, further comprising a third audio mixer for synthesizing sound signals, input from the second communication module and the microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the first communication module.(String), 13.如权利要求11所述的方法,其中进行电话会议还包括将从第一移动终端和第三移动终端输入的声音信号合成为第二移动终端的第二混音器中的合成声音信号,并将合成声音信号输出到第二移动终端的扬声器移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.446 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 4. The multi-standby mobile terminal of claim 1, further comprising:a first antenna for transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and for receiving a frequency to be used for the GSM wireless communication network; anda second antenna for transmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and for receiving a frequency to be used for the CDMA wireless communication network.(String), 14.如权利要求11所述的方法,还包括:通过全球移动通信系统(GSM)无线通信网络发送和接收声音信号和数据,并接收用于GSM无线通信网络的频率;和通过码分多址(CDMA)无线通信网络发送和接收声音信号和数据,以及接收要用于CDMA无线通信网络的频率。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.446 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 5. The multi-standby mobile terminal of claim 4, wherein the first communication module forms the communication channel with the GSM wireless communication network and transmits and receives a wireless signal to and from a first mobile terminal.(String), 15.如权利要求14所述的方法,其中第一无线通信网络包括GSM无线通信网络并且向第一移动终端发送无线信号以及从第一移动终端接收无线信号。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.446 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 6. The multi-standby mobile terminal of claim 4, wherein the second communication module forms the communication channel with the CDMA wireless communication network and transmits and receives a wireless signal to and from a third mobile terminal.(String), 16.如权利要求14所述的方法,其中第二无线通信网络包括CDMA无线通信网络并且向第三移动终端发送无线信号以及从第三移动终端接收无线信号。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.447 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 7. The multi-standby mobile terminal of claim 5, wherein the first communication module demodulates a wireless signal received from the first mobile terminal and modulates the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 17.如权利要求15所述的方法,还包括对从第一移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第三移动终端的合成声音信号进行调制。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.447 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 8. The multi-standby mobile terminal of claim 6, wherein the second communication module demodulates a wireless signal received from the third mobile terminal and modulates a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 18.如权利要求16所述的方法,还包括对从第三移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第一移动终端的合成声音信号进行调制。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.447 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 9. The multi-standby mobile terminal of claim 3, further comprising a controller for terminating a function of the first audio mixer, if communication through the second communication module terminates.(String), 19.如权利要求13所述的方法,其中进行电话会议包括将从第二移动终端和第三移动终端输入的声音信号在第二移动终端的第三混音器中合成为合成声音信号,并将合成声音信号发送给第一移动终端。(String), 1(Integer), 8(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.447 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 10. The multi-standby mobile terminal of claim 9, wherein the controller terminates a function of the third audio mixer, if communication through the first communication module terminates.(String), 20.如权利要求19所述的方法,其中电话会议的执行还包括如果第二移动终端和第三移动终端之间的通信终止,则终止第一混音器的功能。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.447 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.448 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 11. A method for performing a conference call, the method comprising:connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal comprises a multi-standby mobile terminal;requesting communication with the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; andperforming a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.448 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 12. The method of claim 11, wherein the performing of the conference call further comprises terminating a function of the third audio mixer, if communication between the first mobile terminal and the second mobile terminal terminates.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.448 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 13. The method of claim 11, wherein the performing of the conference call further comprises synthesizing sound signals input from the first mobile terminal and the third mobile terminal, to a synthesized sound signal in a second audio mixer of the second mobile terminal and outputting the synthesized sound signal to a speaker of the second mobile terminal.(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.448 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 14. The method of claim 11, further comprising:transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and receiving a frequency to be used for the GSM wireless communication network; andtransmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and receiving a frequency to be used for the CDMA wireless communication network.(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.448 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 15. The method of claim 14, wherein the first wireless communication network comprises the GSM wireless communication network and transmits and receives a wireless signal to and from the first mobile terminal.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.448 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 16. The method of claim 14, wherein the second wireless communication network comprises the CDMA wireless communication network and transmits and receives a wireless signal to and from the third mobile terminal.(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.449 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 17. The method of claim 15, further comprising demodulating a wireless signal received from the first mobile terminal and modulating the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.449 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 18. The method of claim 16, further comprising demodulating a wireless signal received from the third mobile terminal and modulating a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.449 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 19. The method of claim 13, wherein the performing of the conference call comprises synthesizing sound signals input from the second mobile terminal and the third mobile terminal, to a synthesized sound signal in a third audio mixer of the second mobile terminal and transmitting the synthesized sound signal to the first mobile terminal.(String), 1(Integer), 18(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.449 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 20. The method of claim 19, wherein the performing of the conference call further comprises terminating a function of the first audio mixer, if communication between the second mobile terminal and the third mobile terminal terminates.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.606 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.606 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.607 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.608 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.608 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184953(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Jan. 17, 2008 in the Korean Intellectual Property Office and assigned Serial No. 10-2008-0005296, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same. More particularly, the present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same that enable a communication connection between several mobile terminals existing in different wireless communication networks. [0004]2. Description of the Related Art [0005]Due to rapid technology development, mobile terminals having various functions, such as voice communication, short message service, audiovisual communication, an electronic scheduler and Internet, are now available. A multi-standby mobile terminal that can perform a communication connection with two or more wireless communication networks, such as a dual-standby mobile terminal that supports a Code Division Multiple Access (CDMA) wireless communication network and a Global System for Mobile communication (GSM) wireless communication network, is now provided. The dual-standby mobile terminal may be in a communication standby state in both a CDMA wireless communication network service area and a GSM wireless communication network service area. That is, in a state where the dual-standby mobile terminal is connected for communication with a mobile terminal using a CDMA wireless communication network, the dual-standby mobile terminal can receive a communication request from a mobile terminal using a GSM wireless communication network and be connected with the mobile terminal for communication. [0006]A mobile terminal service provider provides, as an additional service, a conference call function in which several persons can simultaneously form a communication channel and perform a phone conference. [0007]A conventional multi-standby mobile terminal cannot perform a conference call. However, the conventional multi-standby mobile terminal can only perform simultaneous standby and individual communication with mobile terminals using different wireless communication networks. [0008]Therefore, a need exists for a method and apparatus that enable a multi-standby mobile terminal to perform a conference call using different wireless communication networks. SUMMARY OF THE INVENTION [0009]An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a multi-standby mobile terminal and a method for performing a conference call using the same that enable mobile terminals in different wireless communication networks to perform a conference call. [0010]In accordance with an aspect of the present invention, a multi-standby mobile terminal is provided. The mobile terminal includes a first communication module for forming a communication channel with a first wireless communication network, a second communication module for forming a communication channel with a second wireless communication network, and a first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the second communication module. [0011]In accordance with another aspect of the present invention, a method of performing a conference call is provided. The method includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal; requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal. [0012]Other aspects, disadvantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0014]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention; [0015]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention; and [0016]FIG. 3 is a flowchart illustrating a method for performing a conference call according to an exemplary embodiment of the present invention. [0017]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0018]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0019]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0020]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0021]In the following description, a dual-standby mobile terminal that can perform a communication connection with a CDMA wireless communication network and a GSM wireless communication network, such as a multi-standby mobile terminal, are described. However, the present invention is not limited thereto. That is, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a communication connection with various wireless communication networks, such as a General Packet Radio Service (GPRS), an Enhanced Data GSM Environment (EDGE), a Universal Mobile Telecommunications System (UMTS) and a Wideband Code Division Multiple Access (WCDMA). [0022]A configuration of a multi-standby mobile terminal according to an exemplary embodiment of the present invention and a method of performing a conference call using the multi-standby mobile terminal are described with reference to the accompanying drawings. [0023]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0024]Referring to FIG. 1, a first mobile terminal 100 is a mobile terminal for supporting a GSM wireless communication network 150, a third mobile terminal 300 is a mobile terminal for supporting a CDMA wireless communication network 350 and a second mobile terminal 200 is a multi-standby mobile terminal for supporting both the GSM and CDMA wireless communication networks 150 and 350. The first mobile terminal 100 and the third mobile terminal 300 may also be a multi-standby mobile terminal. [0025]In the following description, in a state where the first mobile terminal 100 and the second mobile terminal 200 are connected for communication, if the third mobile terminal 300 requests communication between several persons, it is assumed that the second mobile terminal 200 may perform a conference call function. That is, in a state where the second mobile terminal 200 and the first mobile terminal 100 are connected for communication using the GSM wireless communication network 150, the third mobile terminal 300 may request, through the CDMA wireless communication network 350, communication between several persons to the second mobile terminal 200. Alternatively, the second mobile terminal 200 may request communication between several persons to the third mobile terminal 300. In this case, a conference call function of the second mobile terminal 200 is activated. Thus, communication between the first mobile terminal 100, the second mobile terminal 200 and the third mobile terminal 300 may be performed. [0026]A conference call function of the second mobile terminal 200 is described later with reference to FIG. 2. [0027]When a conference call function is activated, if a sound signal of the first mobile terminal 100 is transmitted to the second mobile terminal 200, the second mobile terminal 200 synthesizes its own sound signal and a sound signal of the first mobile terminal 100 using an audio mixer and transmits the synthesized sound signal to the third mobile terminal 300. That is, the third mobile terminal 300 may receive sound signals of the second mobile terminal 200 and the first mobile terminal 100 through the synthesized sound signal. [0028]Similarly, if a sound signal of the third mobile terminal 300 is transmitted to the second mobile terminal 200, the second mobile terminal 200 may synthesize its own sound signal and a sound signal of the third mobile terminal 300 using an audio mixer. The second mobile terminal 200 then transmits the synthesized sound signal to the first mobile terminal 100. That is, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300 through the synthesized sound signal. [0029]The second mobile terminal 200 synthesizes a sound signal transmitted from the first mobile terminal 100 and a sound signal transmitted from the third mobile terminal 300 using the audio mixer and outputs the synthesized sound signal through a speaker (SPK) of the second mobile terminal 200. Thereby, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300, the second mobile terminal 200 may receive sound signals of the first mobile terminal 100 and the third mobile terminal 300, and the third mobile terminal 300 may receive sound signals of the first mobile terminal 100 and the second mobile terminal 200. Thus, a conference call may be performed. [0030]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0031]FIG. 2 illustrates, as the multi-standby mobile terminal 200 according to an exemplary embodiment of the present invention, a dual-standby mobile terminal that may perform a communication connection with the GSM wireless communication network and the CDMA wireless communication network. However, the multi-standby mobile terminal of the present invention is not limited to the dual-standby mobile terminal. [0032]The dual-standby mobile terminal may have slots in which a CDMA card and a GSM card are mounted or one slot for mounting a dual card in which a CDMA card and a GSM card are integrated. [0033]Referring to FIG. 2, a dual-standby mobile terminal (hereinafter, the second mobile terminal 200) according to an exemplary embodiment of the present invention includes a first antenna 401, a second antenna 402, a first communication module 410, a second communication module 420, a controller 450 and an audio mixer 460 including a first audio mixer 461, a second audio mixer 462 and a third audio mixer 463. [0034]The first antenna 401 transmits and receives a sound signal and data through the GSM wireless communication network 150 and receives a frequency to be used for the GSM wireless communication network 150. [0035]The second antenna 402 transmits and receives a sound signal and data through the CDMA wireless communication network 350 and receives a frequency to be used for the CDMA wireless communication network 350. [0036]FIG. 2 illustrates the first antenna 401 and the second antenna 402 as separate antennas. However the first antenna 401 and the second antenna 402 may be formed as one antenna. When the first antenna 401 and the second antenna 402 are formed as one antenna, the dual-standby mobile terminal 200 includes a means for dividing a frequency band into a CDMA frequency band and a GSM frequency band. For example, the dual-standby mobile terminal 200 divides a signal received by the antenna using a duplexer (not shown) into signals of a CDMA frequency band and signals of a GSM frequency band. The dual-standby mobile terminal 200 transmits the signal of the GSM frequency band to the first communication module 410 and the signal of the CDMA frequency band to the second communication module 420. [0037]The first communication module 410 and the second communication module 420 each include a transmission/reception signal divider (not shown) for dividing a transmission/reception signal, a Radio Frequency (RF) transmitter (not shown) for up-converting a frequency of a signal to be transmitted and amplifying the signal, an RF receiver (not shown) for low-noise amplifying a received signal and down-converting a frequency of the signal and a modem for modulating and demodulating a sound signal. [0038]Hereinafter, for convenience of description, it is assumed that the first communication module 410 forms a communication channel with the GSM wireless communication network 150 and transmits and receives a wireless signal to and from the first mobile terminal 100 using a GSM wireless communication method. Also, the second communication module 420 forms a communication channel with the CDMA wireless communication network 350 and transmits and receives a wireless signal to and from the third mobile terminal 300 using a CDMA wireless communication method. [0039]The first communication module 410 demodulates a wireless signal received from the first mobile terminal 100 and modulates a sound signal input from a microphone (MIC) of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the first communication module 410 modulates a sound signal of the second mobile terminal 200 and a sound signal of the third mobile terminal 300 synthesized in the audio mixer 460 and transmits the modulated sound signal to the first mobile terminal 100. [0040]The second communication module 420 demodulates a wireless signal received from the third mobile terminal 300 and modulates a sound signal input from the MIC of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the second communication module 420 modulates a sound signal of the second mobile terminal 200 and a sound signal of the first mobile terminal 100 synthesized in the audio mixer 460 and transmits the modulated sound signal to the third mobile terminal 300. [0041]The controller 450 controls general operations of the second mobile terminal 200 and a signal flow of elements of the second mobile terminal 200. More particularly, the controller 450 controls the first communication module 410 and the second communication module 420. In more detail, the controller 450 controls the first communication module 410 and the second communication module 420 to perform a communication connection with the GSM communication network 150 and CDMA communication network 350, respectively. When a communication connection request is received by the first communication module 410 or the second communication module 420, the controller 450 activates the corresponding first communication module 410 or second communication module 420 to perform communication. [0042]Further, in a state where the first mobile terminal 100 and the second mobile terminal 200 perform communication through the GSM wireless communication network 150, if the third mobile terminal 300 requests communication between several persons through the CDMA wireless communication network 350, the controller 450 of the second mobile terminal 200 performs a conference call function. If a communication request received from the third mobile terminal 300 is not a request for communication between several persons, the controller 450 performs an individual communication function. That is, in order to perform individual communication with the third mobile terminal 300, the controller 450 terminates functions other than a communication connection function of the first communication module 410. Further, the controller 450 controls the audio mixer 460 to block transmission and reception of a sound signal to and from the first mobile terminal 100. [0043]Similarly, in order to perform individual communication with the first mobile terminal 100, the controller 450 terminates functions other than a communication connection function of the second communication module 420, and blocks transmission and reception of a sound signal to and from the third mobile terminal 300. [0044]The controller 450 may perform a conference call function for activating both the first communication module 410 and the second communication module 420. Specifically, when the controller 450 activates both the first communication module 410 and the second communication module 420, a sound signal of the first mobile terminal 100 is modulated in the second mobile terminal 200, the modulated sound signal is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the third mobile terminal 300. Likewise, a sound signal of the third mobile terminal 300 is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the first mobile terminal 100. Thereby, a conference call for voice communication between mobile terminals in different wireless communication networks is performed. [0045]When the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0046]While performing a conference call, when communication with either the first mobile terminal 100 or the third mobile terminal 300 terminates, the controller 450 controls a conference call termination function of the audio mixer 460. A detailed description thereof is described later. [0047]The controller 450 may be included in the first communication module 410 or in the second communication module 420. In this case, the communication module 410 or 420 including the controller 450 becomes a main communication module and controls signal flows of the entire system, including the signal flows of another communication module. [0048]When performing a conference call, the first audio mixer 461 synthesizes a sound signal of the first mobile terminal 100 received from the first communication module 410 and a sound signal received from the MIC of the second mobile terminal 200. The first audio mixer 461 outputs the synthesized sound signal to the second communication module 420. The synthesized sound signal output to the second communication module 420 is modulated and transmitted to the third mobile terminal 300 via the second antenna 402. That is, when performing a conference call, a sound signal of the first mobile terminal 100 is input to the first audio mixer 461, via the first communication module 410 of the second mobile terminal 200, and synthesized by the first audio mixer 461 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the second communication module 420 of the second mobile terminal 200 and transmitted to the third mobile terminal 300 through the second antenna 402. [0049]While performing a conference call, when communication with the third mobile terminal 300 terminates, the first audio mixer 461 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the first audio mixer 461 is activated only when performing communication with the third mobile terminal 300. [0050]The second audio mixer 462 synthesizes a sound signal of the first mobile terminal 100 output from the first communication module 410 and a sound signal of the third mobile terminal 300 output from the second communication module 420. The synthesized sound signal is output through a speaker (SPK) of the second mobile terminal 200. The SPK may be mounted on the mobile terminal or may be an earphone of the mobile terminal or a separate audio speaker receiving the synthesized sound signal. [0051]The third audio mixer 463 synthesizes a sound signal of the third mobile terminal 300 received from the second communication module 420 and a sound signal received from the MIC of the second mobile terminal 200. The third audio mixer 463 outputs the synthesized sound signal to the first communication module 410. The synthesized sound signal output to the first communication module 410 is modulated and transmitted to the first mobile terminal 100, via the first antenna 401. That is, when performing a conference call, a sound signal of the third mobile terminal 300 is input to the third audio mixer 463 via the second communication module 420 of the second mobile terminal 200 and synthesized by the third audio mixer 463 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the first communication module 410 of the second mobile terminal 200 and transmitted to the first mobile terminal 100 from the first antenna 401. [0052]While performing a conference call, when communication with the first mobile terminal 100 terminates, the third audio mixer 463 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the third audio mixer 463 is activated only when performing communication with the first mobile terminal 100. [0053]FIG. 3 is a flowchart illustrating a method of performing a conference call according to an exemplary embodiment of the present invention. [0054]Referring to FIGS. 1 to 3, the first mobile terminal 100 and the second mobile terminal 200 are connected for communication through the GSM wireless communication network 150 in step S500. In this case, the second mobile terminal 200 transmits and receives a wireless signal to and from the first mobile terminal 100 from the first antenna 401 and the first communication module 410. [0055]The controller 450 of the second mobile terminal 200 controls the second communication module 420 to await a communication connection request. Further, when forming a communication channel with the first mobile terminal 100, the controller 450 of the second mobile terminal 200 activates the second audio mixer 462 and the third audio mixer 463 and sustains the first audio mixer 461 in an inactive state. Specifically, when the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 of the second mobile terminal 200 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0056]The third mobile terminal 300 requests communication to the second mobile terminal 200 through the CDMA wireless communication network 350 in step S502. Although not shown in FIG. 3, alternatively the second mobile terminal 200 may request communication to the third mobile terminal 300 through the CDMA wireless communication network 350. [0057]When a communication request from the third mobile terminal 300 is received, the controller 450 of the second mobile terminal 200 notifies the reception of a communication request to a user of the second mobile terminal 200, by controlling a display unit to display that a communication connection request from another wireless communication network is received or by outputting a reception sound, for example. [0058]The second mobile terminal 200 determines whether a conference call is to be performed according to the communication request received from the CDMA wireless communication network 350 in step S504. [0059]If a conference call is not to be performed, the second mobile terminal 200 performs individual communication with either the first mobile terminal 100 or the third mobile terminal 300, according to the user's selection in step S506. The individual communication is performed by controlling the first communication module 410 and the second communication module 420. For example, when individual communication with the first mobile terminal 100 is intended, the controller 450 of the second mobile terminal 200 controls to sustain only a communication connection state of the second communication module 420 and to turn off other functions. [0060]If it is determined that a conference call is to be performed in step S504, the second mobile terminal 200 activates a conference call function in step S508. The controller 450 activates both the first communication module 410 and the second communication module 420 of the second mobile terminal 200, and activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0061]The second mobile terminal 200 is connected for communication with the third mobile terminal 300 in the CDMA wireless communication network 350 in step S510, thereby forming a conference call with the first mobile terminal 100 and the third mobile terminal 300. [0062]When forming a conference call between the first mobile terminal 100 and the third mobile terminal 300, the first audio mixer 461 of the second mobile terminal 200 synthesizes a sound signal of the first mobile terminal 100 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the second communication module 420. The output sound signal of the first mobile terminal 100 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the third mobile terminal 100 from the second antenna 402. [0063]The third audio mixer 463 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the first communication module 410. The output sound signal of the third mobile terminal 300 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the first mobile terminal 100 from the first antenna 401. [0064]The second audio mixer 462 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the first mobile terminal 100. The second audio mixer 462 outputs the synthesized sound signal through the SPK of the second mobile terminal 200. [0065]While performing a conference call, when communication between the first mobile terminal 100 and the second mobile terminal 200 terminates, the controller 450 of the second mobile terminal 200 terminates functions of the third audio mixer 463 in order to prevent unnecessary power consumption. Alternatively, when communication between the second mobile terminal 200 and the third mobile terminal 300terminates, the controller 450 of the second mobile terminal 200 terminates functions of the first audio mixer 461 in order to prevent unnecessary power consumption. [0066]As described above, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a conference call with mobile terminals using different wireless communication networks. Thus, a conference call may be performed without subscribing to an additional service. Accordingly, user convenience may be improved. [0067]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.(String), 优先 [0001] 此申请根据 35 U.S.C. 2008 年 1 月 17 日向韩国知识产权局提交并转让序列号为 10-2008-0005296 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种多待移动终端以及使用该多待移动终端进行电话会议的方法。 更具体地,本发明涉及一种多待移动终端以及使用该多待移动终端执行电话会议的方法,其使得存在于不同无线通信网络中的多个移动终端之间能够进行通信连接。 [0004] 2.相关技术的描述 [0005] 由于技术的快速发展,具有多种功能的移动终端,例如语音通信、短消息服务、视听通信、电子日程安排和互联网已经面世。 可以与两个或多个无线通信网络进行通信连接的多待移动终端,例如支持码分多址(CDMA)无线通信网络和全球移动通信系统(GSM)的双待移动终端 ) 无线通信网络,现提供。 双待移动终端在CDMA无线通信网络服务区和GSM无线通信网络服务区都可以处于通信待机状态。 即,在双待移动终端与使用CDMA无线通信网络的移动终端进行通信连接的状态下,双待移动终端可以接收来自使用GSM无线通信网络的移动终端的通信请求,并且 与移动终端连接进行通信。 [0006] 移动终端服务提供商作为附加服务提供电话会议功能,其中几个人可以同时形成通信信道并进行电话会议。 [0007] 传统的多待移动终端无法进行电话会议。 然而,传统的多待机移动终端只能与使用不同无线通信网络的移动终端进行同时待机和单独通信。 [0008] 因此,需要一种使多待移动终端能够使用不同的无线通信网络进行电话会议的方法和装置。 发明内容 [0009] 本发明的一个方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一方面在于提供一种多待移动终端以及使用该多待移动终端进行电话会议的方法,使得不同无线通信网络中的移动终端能够进行电话会议。 [0010] 根据本发明的一个方面,提供了一种多待移动终端。 该移动终端包括用于与第一无线通信网络形成通信信道的第一通信模块、用于与第二无线通信网络形成通信信道的第二通信模块、以及用于合成声音信号的第一混音器,从第一无线通信网络输入。 通信模块和麦克风,以合成声音信号,并将合成声音信号输出到第二通信模块。 [0011]根据本发明的另一方面,提供了一种执行电话会议的方法。 该方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中,第二移动终端是多待移动终端; 由存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信; 当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议, 将合成的声音信号发送给第三移动终端。 [0012] 本发明的其他方面、缺点和显着特征对于本领域技术人员而言将从以下详细描述中变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0013] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0014] 如图。 附图说明图1是示出根据本发明示例性实施例的使用多待移动终端的电话会议系统的图; [0015] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图; 和 [0016] 如图。 图3是示出根据本发明示例性实施例的用于执行电话会议的方法的流程图。 [0017] 在整个附图中,应当注意,相同的附图标记用于描述相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0018] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,省略了对众所周知的功能和结构的描述。 [0019] 以下描述和权利要求中使用的术语和词语不限于书目含义,而是仅由发明人使用以实现对本发明的清晰和一致的理解。 因此,本领域技术人员应该清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0020] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0021] 在以下描述中,描述了可以与CDMA无线通信网络和GSM无线通信网络进行通信连接的双待移动终端,例如多待移动终端。 然而,本发明不限于此。 即,根据本发明示例性实施例的多待机移动终端可以执行与各种无线通信网络的通信连接,例如通用分组无线服务(GPRS)、增强型数据GSM环境(EDGE)、通用 移动电信系统 (UMTS) 和宽带码分多址 (WCDMA)。 [0022]参照附图描述根据本发明示例性实施例的多待移动终端的配置以及使用多待移动终端执行电话会议的方法。 [0023] 如图。 图1是图示根据本发明示例性实施例的使用多待移动终端的电话会议系统的图。 [0024] 参考图。 1、第一个移动终端 100 是支持GSM无线通信网络的移动终端 150 ,第三个移动终端 300 是支持CDMA无线通信网络的移动终端 350 和第二个移动终端 200 是支持GSM和CDMA无线通信网络的多待机移动终端 150 和 350 . 第一个移动终端 100 第三个移动终端 300 也可以是多待移动终端。 [0025] 在下面的描述中,在第一移动终端 100 第二移动终端 200 连接进行通信,如果第三个移动终端 300 请求多人之间的通信,假设第二个移动终端 200 可以执行电话会议功能。 即,在第二移动终端 200 和第一个移动终端 100 使用 GSM 无线通信网络进行通信 150 , 第三个移动终端 300 可通过 CDMA 无线通信网络请求 350 , 几个人之间的通信到第二个移动终端 200 . 或者,第二移动终端 200 可以向第三移动终端请求多人之间的通信 300 . 在这种情况下,第二移动终端的电话会议功能 200 被激活。 这样,第一移动终端之间的通信 100 ,第二个移动终端 200 第三个移动终端 300 可以执行。 [0026] 第二移动终端的电话会议功能 200 稍后将参考图10进行描述。 2. [0027] 开启电话会议功能时,如果第一移动终端的声音信号 100 发送到第二移动终端 200 ,第二个移动终端 200 合成自己的声音信号和第一移动终端的声音信号 100 使用混音器将合成的声音信号发送给第三移动终端 300 . 即第三移动终端 300 可以接收第二移动终端的声音信号 200 和第一个移动终端 100 通过合成的声音信号。 [0028] 同理,如果第三移动终端的声音信号 300 发送到第二移动终端 200 ,第二个移动终端 200 可以合成自己的声音信号和第三移动终端的声音信号 300 使用音频混音器。 第二个移动终端 200 然后将合成的声音信号发送给第一移动终端 100 . 即第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 通过合成的声音信号。 [0029] 第二个移动终端 200 合成从第一移动终端发送的声音信号 100 第三移动终端发送的声音信号 300 使用音频混合器并通过第二移动终端的扬声器(SPK)输出合成的声音信号 200 . 由此,第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 ,第二个移动终端 200 可以接收第一移动终端的声音信号 100 第三个移动终端 300 ,以及第三个移动终端 300 可以接收第一移动终端的声音信号 100 第二移动终端200 . 因此,可以执行电话会议。 [0030] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图。 [0031] 如图。 如图2所示,作为多待移动终端 200 根据本发明的示例性实施例,提供一种可以与GSM无线通信网络和CDMA无线通信网络进行通信连接的双待移动终端。 然而,本发明的多待移动终端不限于双待移动终端。 [0032] 双待移动终端可以具有安装CDMA卡和GSM卡的插槽,或者一个用于安装集成了CDMA卡和GSM卡的双卡的插槽。 [0033] 参考图。 2、双待移动终端(以下简称第二移动终端 200 )根据本发明的示例性实施例包括第一天线 401 ,第二根天线 402 ,第一通信模块 410 ,第二个通信模块 420 , 一个控制器 450 和一个混音器 460 包括第一个混音器 461 ,第二个音频混音器 462 和第三个混音器 463 . [0034] 第一个天线 401 通过 GSM 无线通信网络发送和接收声音信号和数据 150 并接收用于GSM无线通信网络的频率 150 . [0035] 第二个天线 402 通过CDMA无线通信网络发送和接收声音信号和数据 350 并接收用于CDMA无线通信网络的频率 350 . [0036] 如图。 图2说明了第一天线 401 和第二根天线 402 作为单独的天线。 但是第一个天线 401 和第二根天线 402 可以形成为一个天线。 当第一根天线 401 和第二根天线 402 组成一根天线,双待移动终端 200 包括用于将频带划分为CDMA频带和GSM频带的装置。 例如双待移动终端 200 使用双工器(未示出)将天线接收到的信号分成CDMA频带的信号和GSM频带的信号。 双待移动终端 200 将GSM频段的信号传输给第一通信模块 410 以及CDMA频段的信号到第二通信模块 420 . [0037] 第一通讯模块 410 第二通信模块 420 每个都包括用于划分发送/接收信号的发送/接收信号分配器(未示出)、用于对要发送的信号的频率进行上变频和放大信号的射频(RF)发送器(未示出)、RF 接收器(未示出)用于低噪声放大接收信号并下变频信号的频率,以及用于调制和解调声音信号的调制解调器。 [0038] 以下,为了描述方便,假设第一通信模块 410 与GSM无线通信网络形成通信通道 150 向第一移动终端发送和从第一移动终端接收无线信号 100 使用GSM无线通信方法。 此外,第二通信模块 420 与CDMA无线通信网络形成通信通道 350 向第三移动终端发送和从第三移动终端接收无线信号 300 使用CDMA无线通信方法。 [0039] 第一通讯模块 410 解调从第一移动终端接收到的无线信号 100 调制从第二移动终端的麦克风(MIC)输入的声音信号 200 到无线信号。 更具体地,在进行电话会议时,第一通信模块 410 调制第二移动终端的声音信号200 第三移动终端的声音信号 300 在混音器中合成 460 将调制后的声音信号发送给第一移动终端 100 . [0040] 第二通讯模块 420 解调从第三移动终端接收的无线信号 300 调制从第二移动终端的MIC输入的声音信号 200 到无线信号。 更具体地说,当进行电话会议时,第二通信模块 420 调制第二移动终端的声音信号 200 以及第一移动终端的声音信号 100 在混音器中合成 460 将调制后的声音信号发送给第三移动终端 300 . [0041] 控制器 450 控制第二移动终端的一般操作 200 第二移动终端的元件的信号流 200 . 更具体地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 . 更详细地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 与 GSM 通信网络进行通信连接 150 和CDMA通信网络 350 , 分别。 当第一通信模块接收到通信连接请求时 410 或第二通信模块 420 , 控制器 450 激活相应的第一通信模块 410 或第二个通信模块 420 进行通信。 [0042] 进一步地,在第一移动终端 100 第二移动终端 200 通过GSM无线通信网络进行通信 150 ,如果是第三个移动终端 300 通过 CDMA 无线通信网络请求多人之间的通信 350 , 控制器 450 第二个移动终端 200 执行电话会议功能。 如果收到来自第三移动终端的通信请求 300 不是几个人之间的通信请求,控制器 450 执行单独的通信功能。 即,为了与第三移动终端进行单独通信 300 , 控制器 450 终止第一通信模块的通信连接功能以外的功能 410 . 此外,控制器 450 控制音频混音器 460 阻止与第一移动终端之间的声音信号的发送和接收 100 . [0043] 类似地,为了与第一移动终端进行单独的通信 100 , 控制器 450 终止第二通信模块的通信连接功能以外的功能 420 ,并阻止与第三移动终端之间的声音信号的发送和接收 300 . [0044] 控制器 450 可以执行电话会议功能以激活第一通信模块 410 第二通信模块 420 . 具体来说,当控制器 450 激活第一个通信模块 410 第二通信模块 420 ,第一移动终端的声音信号 100 在第二个移动终端中调制 200 ,调制后的声音信号与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第三移动终端 300 . 同样,第三移动终端的声音信号 300 与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第一移动终端 100 . 从而,在不同无线通信网络中的移动终端之间进行语音通信的电话会议。 [0045] 当第一个移动终端 100第二移动终端 200 执行单独的通信,控制器 450 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0046] 在进行电话会议时,与第一移动终端中的任一个通信时 100 或者第三个移动终端 300 终止,控制器 450 控制混音器的电话会议终止功能 460 . 稍后描述其详细描述。 [0047] 控制器 450 可以包括在第一通信模块中 410 或在第二个通讯模块中 420 . 在这种情况下,通信模块 410 或者 420 包括控制器 450 成为主要的通信模块,控制整个系统的信号流,包括另一个通信模块的信号流。 [0048] 进行电话会议时,第一个混音器 461 合成第一移动终端的声音信号 100 从第一通信模块接收 410 以及从第二移动终端的MIC接收到的声音信号 200 . 第一个混音器 461 将合成的声音信号输出到第二通信模块 420 . 合成声音信号输出至第二通信模块 420 调制后发送到第三移动终端 300 通过第二根天线 402 . 即在进行电话会议时,第一移动终端的声音信号 100 输入到第一个混音器 461 ,通过第一通讯模块 410 第二个移动终端 200 ,并由第一个混音器合成 461 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第二通信模块 420 第二个移动终端 200 并传送至第三移动终端 300 通过第二根天线 402 . [0049] 进行电话会议时,与第三移动终端通信时 300 终止,第一个混音器 461 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第一混音器 461 仅在与第三移动终端进行通信时激活 300 . [0050] 第二个混音器 462 合成第一移动终端的声音信号 100 第一个通信模块的输出 410 第三移动终端的声音信号 300 第二通信模块的输出 420 . 合成的声音信号通过第二移动终端的扬声器(SPK)输出 200 . SPK可以安装在移动终端上,也可以是移动终端的耳机或接收合成声音信号的单独的音频扬声器。 [0051] 第三个混音器 463 合成第三移动终端的声音信号 300 从第二通信模块接收 420 以及从第二移动终端的MIC接收到的声音信号 200 . 第三个混音器 463 将合成的声音信号输出到第一通信模块 410 . 合成声音信号输出至第一通讯模块 410 被调制并发送到第一移动终端 100 ,通过第一根天线 401 . 即在进行电话会议时,第三移动终端的声音信号 300 输入到第三个混音器 463 通过第二个通信模块 420 第二个移动终端 200并由第三个混音器合成 463 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第一通信模块 410 第二个移动终端 200 并传送至第一移动终端 100 从第一根天线 401 . [0052] 在进行电话会议时,与第一移动终端通信时 100 终止,第三个混音器 463 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第三混音器 463 仅在与第一移动终端进行通信时激活 100 . [0053] 如图。 图3是示出根据本发明示例性实施例的执行电话会议的方法的流程图。 [0054] 参考图。 1到3、第一移动终端 100 第二移动终端 200 通过 GSM 无线通信网络连接进行通信 150 在步骤 S 500 . 在这种情况下,第二移动终端 200 向第一移动终端发送和从第一移动终端接收无线信号 100 从第一根天线 401 和第一通信模块 410 . [0055] 控制器 450 第二个移动终端 200 控制第二通信模块 420 等待通信连接请求。 此外,当与第一移动终端形成通信信道时 100 , 控制器 450 第二个移动终端 200 激活第二个混音器 462 和第三个混音器 463 并维持第一个混音器 461 处于非活动状态。 具体地,当第一移动终端 100 第二移动终端 200 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 第二个移动终端 200 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0056] 第三个移动终端 300 请求与第二移动终端的通信 200 通过CDMA无线通信网络 350 在步骤 S 502 . 尽管图 1 中未显示。 3、备选第二个移动终端 200 可以请求与第三移动终端的通信 300 通过CDMA无线通信网络 350 . [0057] 当来自第三移动终端的通信请求时 300 收到,控制器 450 第二个移动终端 200 通知第二移动终端的用户接收到通信请求 200 例如,通过控制显示单元显示接收到来自另一无线通信网络的通信连接请求或者通过输出接收声音。 [0058] 第二个移动终端 200 根据从CDMA无线通信网络接收到的通信请求,确定是否进行电话会议 350 在步骤 S 504 . [0059] 如果不进行电话会议,则第二移动终端 200 与第一移动终端进行单独通信 100 或者第三个移动终端 300 ,根据用户在步骤S中的选择 506 . 通过控制第一通信模块进行单独通信 410 第二通信模块 420 . 例如,当与第一移动终端单独通信时 100旨在,控制器 450 第二个移动终端 200 控制以仅维持第二通信模块的通信连接状态 420 并关闭其他功能。 [0060] 如果在步骤S中确定要进行电话会议 504 ,第二个移动终端 200 在步骤 S 中激活电话会议功能 508 . 控制器 450 激活第一个通信模块 410 第二通信模块 420 第二个移动终端 200 , 并激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0061] 第二个移动终端 200 连接用于与第三移动终端通信 300 在CDMA无线通信网络中 350 在步骤 S 510 ,从而与第一移动终端形成电话会议 100 第三个移动终端 300 . [0062] 第一移动终端之间进行电话会议时 100 第三个移动终端 300 , 第一个混音器 461 第二个移动终端 200 合成第一移动终端的声音信号 100 第二移动终端的声音信号 200 并将合成声音信号输出至第二通信模块 420 . 第一移动终端的输出声音信号 100 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第三移动终端 100 从第二根天线 402 . [0063] 第三个混音器 463 第二个移动终端 200 合成第三移动终端的声音信号 300 第二移动终端的声音信号 200 并将合成声音信号输出至第一通讯模块 410 . 第三移动终端的输出声音信号 300 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第一移动终端 100 从第一根天线 401 . [0064] 第二个混音器 462 第二个移动终端 200 合成第三移动终端的声音信号 300 以及第一移动终端的声音信号 100 . 第二个混音器 462 通过第二移动终端的SPK输出合成的声音信号 200 . [0065] 在进行电话会议时,在第一移动终端之间进行通信时 100 第二移动终端 200 终止,控制器 450 第二个移动终端 200 终止第三个混音器的功能 463 以防止不必要的功耗。 或者,当第二移动终端之间进行通信时 200 第三个移动终端 300 终止,控制器 450 第二个移动终端 200 终止第一个混音器的功能 461 以防止不必要的功耗。 [0066] 如上所述,根据本发明示例性实施例的多待机移动终端可以与使用不同无线通信网络的移动终端进行电话会议。 因此,可以在不订阅附加服务的情况下执行电话会议。 因此,可以提高用户便利性。 [0067] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.623 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.624 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.625 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.626 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.626 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.627 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.627 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.628 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.628 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.635 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.635 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.636 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.637 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.637 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.637 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270636(Integer), CN101489322A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.647 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.648 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.648 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270636(Integer), EP2081370A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.657 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.658 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.658 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270636(Integer), KR1020090079379A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.668 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.668 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.669 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270636(Integer), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.679 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.683 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.683 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20090186607A1(String), US20090186607A1(String), 1248278400(Integer), 270636(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.690 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.691 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.691 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.693 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.693 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.693 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.695 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.695 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.695 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.697 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.697 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.698 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.708 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.710 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.710 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 0(Integer), 1681974672(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.720 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.721 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.721 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184953(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.722 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.723 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.723 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75902(Integer), 2(Integer), 184953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.730 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.731 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.731 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.732 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.732 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.732 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.733 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.734 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.734 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.735 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.736 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.736 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.737 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.737 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.738 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.744 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.745 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.746 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.747 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.748 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.748 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.749 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.750 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.750 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.757 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.759 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.759 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120276924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.761 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.762 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.762 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: System and method for positioning mobile terminal, and mobile terminal(String), 移动终端定位系统、方法及移动终端(String), US20120276924A1(String), The disclosure discloses a method for positioning a mobile terminal, which comprises: a server sends a push notification to a mobile terminal; the mobile terminal performs self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal, and sends the geographical position information to the server; the server receives and displays the geographical position information sent by the mobile terminal. The disclosure also discloses a system for positioning a mobile terminal for implementing the method for positioning a mobile terminal and a mobile terminal. With such method and device, the server can be used to send a push notification to the mobile terminal after a user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal.(String), 本发明公开了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端收到推送通知后进行自我定位,获取移动终端的地理位置信息,并将地理位置信息发送给服务器。 服务器接收并显示移动终端发送的地理位置信息。 本发明还公开了一种用于实现上述移动终端定位方法的移动终端定位系统及移动终端。 通过这样的方法和装置,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位其地理位置信息,并将地理位置信息发送至服务器,以帮助用户检索移动终端。(String), US13/519896(String), 1279468800(Integer), US20120276924A1(String), 1351699200(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 4(Integer), US20070015505A1 | US20080293397A1 | US20080320573A1 | US20120142329A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.771 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.772 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.772 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.774 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.775 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.775 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d20859c7323c40019282ca6df673e47f.png(String), 184954(Integer), d20859c7323c40019282ca6df673e47f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.784 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.784 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.785 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.786 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.787 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.787 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System and method for positioning mobile terminal, and mobile terminal(String), 移动终端定位系统、方法及移动终端(String), US20120276924A1(String), The disclosure discloses a method for positioning a mobile terminal, which comprises: a server sends a push notification to a mobile terminal; the mobile terminal performs self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal, and sends the geographical position information to the server; the server receives and displays the geographical position information sent by the mobile terminal. The disclosure also discloses a system for positioning a mobile terminal for implementing the method for positioning a mobile terminal and a mobile terminal. With such method and device, the server can be used to send a push notification to the mobile terminal after a user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal.(String), 本发明公开了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端收到推送通知后进行自我定位,获取移动终端的地理位置信息,并将地理位置信息发送给服务器。 服务器接收并显示移动终端发送的地理位置信息。 本发明还公开了一种用于实现上述移动终端定位方法的移动终端定位系统及移动终端。 通过这样的方法和装置,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位其地理位置信息,并将地理位置信息发送至服务器,以帮助用户检索移动终端。(String), US13/519896(String), 1279468800(Integer), US20120276924A1(String), 1351699200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 4(Integer), US20070015505A1 | US20080293397A1 | US20080320573A1 | US20120142329A1(String), \20230420\d20859c7323c40019282ca6df673e47f.png(String), 16(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.796 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.797 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.797 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.799 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 1. A method for positioning a mobile terminal, comprising:sending, by a server, a push notification to a mobile terminal;performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal;sending, by the mobile terminal, the geographical position information to the server; andreceiving and outputting, by the server, the geographical position information sent by the mobile terminal.(String), 1.根据权利要求9所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 2. The method according to claim 1, further comprising: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal,sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andperforming, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command.(String), 12.根据权利要求2所述的方法,还包括:在服务器向移动终端发送推送通知的步骤之前,移动终端在检测到SIM卡被更换后,向服务器发送移动终端的国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息正在启动。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 3. The method according to claim 1, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 13.根据权利要求12所述的方法,还包括:服务器根据接收到的移动终端的IMEI与IMSI的匹配信息,更新之前的移动终端的IMEI与IMSI的匹配信息,并进一步判断更新后的IMEI是否为在服务器注册的移动终端的IMEI。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 4. The method according to claim 3, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 14.根据权利要求6所述的系统,其中移动终端还包括SIM卡检测模块和匹配信息发送模块,其中SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 5. A system for positioning a mobile terminal, comprising a server and a mobile terminal, whereinthe server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; andthe mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 15.根据权利要求14所述的系统,其中服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前移动终端的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为移动终端在服务器注册的IMEI.16.根据权利要求10所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 6. The system according to claim 5, whereinthe server is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andthe mobile terminal further comprises a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 7. The system according to claim 5, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 8. The system according to claim 7, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 9. A mobile terminal, comprising a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 10. The mobile terminal according to claim 9, further comprising a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 11. The mobile terminal according to claim 9, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 12. The method according to claim 2, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 13. The method according to claim 12, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 14. The system according to claim 6, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 13(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 15. The system according to claim 14, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 16. The mobile terminal according to claim 10, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.928 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.928 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.929 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.930 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.930 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184954(Integer), TECHNICAL FIELD [0001]The disclosure relates to the technology of mobile communications, particularly to a system and method for positioning a mobile terminal and to a mobile terminal. BACKGROUND [0002]With the continuous development of mobile communication technologies, a mobile terminal, such as a mobile phone, a Personal Digital Assistant (PDA) and the like is no longer used as a simple communication tool only. Because the above mobile terminal has advantages of small volume, easiness in taking, convenience in use and the like, it has gradually become a personal information storage carrier for the user. Many users of the mobile terminal get used to storing important personal information involving personal information security, such as contacts, photos, schedules and the like in the mobile terminal. [0003]After the mobile terminal is lost, its operator cannot help the user retrieve the lost mobile terminal because the operator only provides Subscriber Identity Module (SIM) card loss reporting and re-issuing services, and cannot provide specific position information of the mobile terminal. SUMMARY [0004]The disclosure mainly aims to provide a system and method for positioning a mobile terminal, and also provide a mobile terminal, with which geographical position information of a lost mobile terminal can be provided to a user to help the user retrieve the mobile terminal. [0005]The disclosure provides a method for positioning a mobile terminal, which comprises: sending, by a server, a push notification to a mobile terminal; performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal; sending, by the mobile terminal, the geographical position information to the server; and receiving and outputting, by the server, the geographical position information sent by the mobile terminal. [0006]Preferably, the method may further comprise: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal, sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and performing, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command. [0007]Preferably, the method may further comprise: before the step of sending, by the server, the push notification to the mobile terminal, sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started. [0008]Preferably, the method may further comprise: updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0009]A system for positioning a mobile terminal, comprises a server and a mobile terminal, wherein the server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; and the mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0010]Preferably, the server may be further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command. [0011]Preferably, the mobile terminal may further comprise a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, wherein the SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; and the matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed. [0012]Preferably, the server may be further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0013]A mobile terminal comprises a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0014]Preferably, the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server. [0015]Preferably, the mobile terminal may further comprise: a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; and a matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed. [0016]With the system and method for positioning a mobile terminal, and the mobile terminal provided by the disclosure, the server can be used to send a push notification to the mobile terminal after the user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0017]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure; [0018]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure; [0019]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure; [0020]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure; [0021]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure; and [0022]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0023]The achievement of the purpose of the disclosure, functional characteristics and advantages of the disclosure will be described with reference to the embodiments and drawings in detail. DETAILED DESCRIPTION [0024]The technical solution of the disclosure is described below with reference to the drawings of the description and the specific embodiments in detail. [0025]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure. [0026]After a mobile terminal is lost, when a finder or a thief does not turn off the mobile terminal, its user logs in a server in time to report loss, and registers an International Mobile Equipment Identity (IMEI) of the mobile terminal. As shown in FIG. 1, a method for protecting data in a mobile terminal of the disclosure comprises the following steps. [0027]Step S101: a server sends a push notification to a mobile terminal. [0028]In this embodiment, the push notification can be sent to the mobile terminal through the server so as to notify the mobile terminal to be positioned via the push notification. In addition, the mobile terminal is registered with an inbound network connection for a positioning program, and the mobile terminal monitors whether the push notification sent by the monitoring mobile terminal is received on the registered inbound network connection. The inbound network connection is registered for the positioning program in a static registration manner or a dynamic registration manner. The static registration will be taken as an example in this embodiment for description. [0029]The server inquires an International Mobile Subscriber Identity (IMSI) of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends the push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0030]Furthermore, a Java Application Description (JAD) file of the mobile terminal is further provided with the MIDlet-Push-<1>attribute, for example the attribute is set as: [0031]MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; after the attribute is added, it indicates a connection protocol adopted is a Short Messaging Service (SMS) protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0032]Step S102: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0033]In the embodiment, the positioning program is a location Application Programming Interface (API) for Java 2 Micro Edition (J2ME) program, which meets Java Specification Request (JSR) 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a Global Positioning System (GPS), a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0034]Step S103: the mobile terminal sends the geographical position information to the server. [0035]In the embodiment, the geographical position information comprises longitude and latitude information of the mobile terminal. [0036]Step S104: the server receives and displays the geographical position information sent by the mobile terminal. [0037]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0038]Step S105: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0039]In the embodiment, the server sends a Lock And Wipe Management Object (LAWMO) command to the mobile terminal according to a Device Management (DM) protocol defined by Open Mobile Alliance (OMA). The server sends the locking command to the mobile terminal through the device management protocol in a Synchronization Markup Language (SyncML) protocol set. [0040]Step S106: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S105 and step S106 are not the necessary steps. [0041]In the embodiment, the server can be used to send the push notification to the mobile terminal after the user finds the mobile terminal is lost; the mobile terminal positions the geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. [0042]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure. [0043]When a mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change a Subscriber Identity Module (SIM) card, when the finder or the thief turns on the mobile terminal again, the mobile terminal will protect data based on the following steps. [0044]Step S201: the mobile terminal detects whether an SIM card is changed after being started; if yes, turn to step S202; otherwise, turn to step S205. [0045]In the embodiment, after the mobile terminal is started, it automatically starts the SIM card verification kit to verify whether the IMSI of the SIM card is changed; if yes, it indicates the SIM card of the mobile terminal is changed. The method for automatically starting the SIM card detection function after startup is as follows: [0046]the MIDlet-1-Type:autostart attribute is added in the Java application description file of the terminal, and meanwhile an autostart permission is also added in the Java application description file in the specific format of: [0047]MIDlet-Permissions:javax.microedition.midlet.AutoStart Permission. [0048]Step S202: the mobile terminal sends matching information between an IMEI and an IMSI to the server. [0049]In the embodiment, the mobile terminal sends matching information between an IMEI and an IMSI to a server through a short message. [0050]Step S203: the server updates the matching information between the IMEI and the IMSI of the mobile terminal. [0051]In the embodiment, after receiving the short message, the server updates the matching information between the IMEI and the IMSI of the mobile terminal through modifying an IMSI number corresponding to the IMEI of the mobile terminal. [0052]Step S204: the server judges whether the updated IMEI is an IMEI of the mobile terminal registered at the server; if yes, turn to step S205; otherwise, the flow is terminated. [0053]Step S205: the server sends a push notification to the mobile terminal. [0054]In the embodiment, the server inquires an IMSI number of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends a push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0055]In addition, the Java application description file of the mobile terminal is provided with the MIDlet-Push-<1>attribute, which is: [0056]MIDlet-Push-1:sms://:8080, MIDletLocation, 13900000000. After the attribute is added, it indicates a connection protocol adopted is an SMS protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0057]Step S206: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0058]In the embodiment, the positioning program is a location API for J2ME program, which meets JSR 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a GPS, a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0059]Step S207: the mobile terminal sends the geographical position information to the server. [0060]In the embodiment, the geographical position information comprises at least longitude and latitude information of the mobile terminal. [0061]Step S208: the server receives and displays the geographical position information sent by the mobile terminal. [0062]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0063]Step S209: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0064]In the embodiment, the server sends an LAWMO command to the mobile terminal according to a device management protocol defined by open mobile alliance. The server sends the locking command to the mobile terminal through the device management protocol in a SyncML protocol set. [0065]Step S210: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S209 and step S210 are not the necessary steps. [0066]In the embodiment, when the mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal; the mobile terminal positions geographical position information thereof after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal. Therefore, data in the lost mobile terminal is prevented from being leaked, and personal information security of the user is ensured. [0067]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure. [0068]The system for positioning a mobile terminal comprises a server 10 and a mobile terminal 20, wherein the mobile terminal 20 comprises a positioning module 201. [0069]The server is configured to send a push notification to the mobile terminal 20, and to receive geographical position information sent by the mobile terminal 20; the positioning module 201 is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal 20, and to send the geographical position information to the server 10. [0070]In the embodiment, the server 10 can be used to send a push notification to the mobile terminal 20 after the user finds that the mobile terminal 20 is lost. The mobile terminal 20 locates geographical position information thereof through the positioning module 201 and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. [0071]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure. [0072]The server 10 is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol. Besides the positioning module 201, the mobile terminal 20 further comprises a locking module 205 and a deleting module 204, an SIM card detecting module 202 and a matching information sending module 203. [0073]The locking module 205 is configured to lock the mobile terminal 20 after receiving the locking command. The deleting module 204 is configured to delete data in a memory after receiving the deleting command. The SIM card detecting module 202 is configured to detect whether an SIM card of the mobile terminal is changed. The matching information sending module 203 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card is changed. [0074]The server 10 is further configured to update the matching information between the IMEI and the IMSI of the mobile terminal 20 registered at the server after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server 10. [0075]In the embodiment, after the mobile terminal 20 is lost, if a finder or a thief turns off the mobile terminal 20 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 20 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 20 is changed; if the SIM card is not changed, the server 10 is directly used to send a push notification to the mobile terminal 20; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 20; the mobile terminal 20 positions geographical position information thereof through the positioning module 201 after receiving the push notification, and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. Therefore, data in the mobile terminal 20 is prevented from being leaked, and personal information security of the user is ensured. [0076]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure. [0077]The mobile terminal 30 comprises a positioning module 301, which is configured to perform self-positioning after receiving a push notification to acquire geographical position information regarding the mobile terminal 30, and send the geographical position information to a server. [0078]In the embodiment, the server can be used to send a push notification to the mobile terminal 30 after the user finds that the mobile terminal 30 is lost. The mobile terminal 30 positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal 30. [0079]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0080]Besides the positioning module 301, the mobile terminal 40 further comprises a locking module 302, a deleting module 303, an SIM card detecting module 304, and a matching information sending module 305. [0081]The locking module 302 is configured to lock the mobile terminal 40 after receiving a locking command sent by a server; the deleting module 303 is configured to delete data in a memory after receiving a deleting command sent by the server. The SIM card detecting module 304 is configured to detect whether an SIM card is changed. The matching information sending module 305 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card of the mobile terminal is changed. [0082]In the embodiment, after the mobile terminal 40 is lost, if a finder or a thief turns off the mobile terminal 40 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 40 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 40 is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal 40; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 40; the mobile terminal 40 positions geographical position information thereof through the positioning module 301 after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal 40. Therefore, data in the mobile terminal 40 is prevented from being leaked, and personal information security of the user is ensured. [0083]The above is only the preferred embodiment of the disclosure and not intended to limit the scope of the patent, and any equivalent structure or equivalent flow transformation based on the description and drawings of the disclosure, which is directly or indirectly applied in other related technical fields shall fall within the scope of patent protection of the disclosure.(String), 技术领域 [0001] 本发明涉及移动通信技术,尤其涉及一种移动终端定位系统、方法及移动终端。 背景 [0002] 随着移动通信技术的不断发展,移动终端,如手机、个人数字助理(Personal Digital Assistant,PDA)等,不再仅仅是一种简单的通信工具。 由于上述移动终端具有体积小、携带方便、使用方便等优点,逐渐成为用户个人信息的存储载体。 很多移动终端的用户习惯于在移动终端中存储联系人、照片、日程等涉及个人信息安全的重要个人信息。 [0003] 移动终端丢失后,其运营商无法帮助用户找回丢失的移动终端,因为运营商仅提供SIM卡挂失和补发服务,无法提供移动终端的具体位置信息。 概括 [0004] 本发明的主要目的在于提供一种移动终端的定位系统及方法,还提供一种移动终端,能够将丢失的移动终端的地理位置信息提供给用户,以帮助用户找回移动终端。 [0005] 本发明提供了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端接收到推送通知后进行自定位,获取移动终端的地理位置信息; 移动终端向服务器发送地理位置信息; 服务器接收并输出移动终端发送的地理位置信息。 [0006] 优选地,该方法还包括: 在服务器接收并输出移动终端发送的地理位置信息的步骤之后,服务器根据移动终端发送锁定命令和/或删除命令。 设备管理协议; 移动终端在接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 [0007] 优选地,该方法还包括: 在服务器向移动终端发送推送通知之前,移动终端发送国际移动设备识别码(IMEI)与国际移动用户识别码的匹配信息。 移动终端(IMSI)在启动后检测到SIM卡被更换时发送给服务器。 [0008] 优选地,该方法还包括:服务器根据接收到的移动终端的IMEI和IMSI的匹配信息更新之前的移动终端的IMEI和IMSI的匹配信息,进一步判断, 服务器,更新后的IMEI是否为在服务器注册的移动终端的IMEI。 [0009] 一种移动终端定位系统,包括服务器和移动终端,服务器用于向移动终端发送推送通知,并接收移动终端发送的地理位置信息; 移动终端还包括定位模块,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0010] 优选地,服务器还可以用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 移动终端还可以包括锁定模块和删除模块,锁定模块用于接收到锁定命令后锁定移动终端。 删除模块,用于接收到删除命令后,删除移动终端内存中的数据。 [0011] 优选地,所述移动终端还包括SIM卡检测模块和匹配信息发送模块,所述SIM卡检测模块用于检测所述移动终端的SIM卡是否被更换。 匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。 [0012] 优选地,服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为注册的移动终端的IMEI 在服务器上。 [0013] 一种移动终端,包括定位模块,用于接收到服务器的推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0014] 优选地,所述移动终端还包括锁定模块和删除模块,所述锁定模块用于接收到所述服务器发送的锁定命令后,锁定所述移动终端。 删除模块,用于接收到服务器发送的删除命令后,删除移动终端内存中的数据。 [0015] 优选地,所述移动终端还包括: SIM卡检测模块,用于检测所述移动终端的SIM卡是否被更换; 匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码(IMEI)和国际移动用户识别码(IMSI)的匹配信息。 [0016] 本发明提供的移动终端定位系统、方法及移动终端,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 附图的简要说明 [0017] 图1为本发明移动终端数据保护方法实施例的流程示意图; [0018] 图2为本发明移动终端数据保护方法另一实施例的流程示意图; [0019] 图3示出了本发明移动终端定位系统实施例的结构示意图; [0020] 图4为本发明移动终端定位系统另一实施例的结构示意图; [0021] 图5示出了本发明移动终端一个实施例的结构示意图; 和 [0022] 图6示出了本发明移动终端另一实施例的结构示意图。 [0023] 本发明目的的实现、功能特点和优点将结合实施例和附图进行详细说明。 详细说明 [0024] 下面结合说明书附图和具体实施例对本发明的技术方案进行详细说明。 [0025] 图1示出了本发明移动终端数据保护方法实施例的流程示意图。 [0026] 移动终端丢失后,当捡到者或小偷没有关闭移动终端时,其用户及时登录服务器挂失,并注册移动终端的国际移动设备识别码(IMEI)。 如图1所示,本发明的移动终端中的数据保护方法包括以下步骤。 [0027] 脚步 101:服务器向移动终端发送推送通知。 [0028] 本实施例中,可以通过服务器向移动终端发送推送通知,以通过推送通知通知移动终端进行定位。 另外,移动终端注册有定位程序的入站网络连接,移动终端监听是否在注册的入站网络连接上接收到监控移动终端发送的推送通知。 入站网络连接以静态注册方式或动态注册方式注册到定位程序。 本实施例以静态注册为例进行说明。 [0029] 服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI,根据IMSI号码获取移动终端的手机号码,然后发送推送通知给 移动终端根据手机号码要求移动终端进行定位。 [0030] 进一步地,移动终端的JAD文件中还设置有MIDlet-Push-<1>属性,例如该属性设置为: [0031] MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; 添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation,推送通知的有效源为服务器 13900000000个数。除了SMS协议之外,本发明当然还可以使用传输控制协议或用户数据报协议,本发明对此不作限制。 [0032] 脚步 102 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0033] 在本实施例中,定位程序为Java 2 Micro Edition(J2ME)程序的定位应用程序编程接口(API),其符合Java Specification Request(JSR)179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以利用基于全球定位系统(Global Positioning System,简称GPS)的卫星定位方法、蜂窝网络的定位方法、或者基于蓝牙的近距离定位方法,或者可以结合上述方法 礼貌。 [0034] 脚步 103 :移动终端向服务器发送地理位置信息。 [0035] 在本实施例中,地理位置信息包括移动终端的经纬度信息。 [0036] 脚步 104 :服务器接收并显示移动终端发送的地理位置信息。 [0037] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0038] 脚步 105 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0039] 在该实施例中,服务器根据开放移动联盟(OMA)定义的设备管理(DM)协议向移动终端发送锁定和擦除管理对象(LAWMO)命令。 服务器通过同步标记语言(SyncML)协议集中的设备管理协议向移动终端发送锁定命令。 [0040] 脚步 106 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S105 和步骤S 106 不是必要的步骤。 [0041] 本实施例中,可以通过服务器在用户发现移动终端丢失后向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 [0042] 图2示出了本发明移动终端数据保护方法另一实施例的流程示意图。 [0043] 当移动终端丢失时,如果捡到者或小偷因电池电量低或想更换用户身份模块(SIM)卡而关闭移动终端,当捡到者或小偷再次打开移动终端时, 移动端将按照以下步骤保护数据。 [0044] 脚步 201 :移动终端开机后检测SIM卡是否被更换; 如果是,转步骤S 202 ; 否则转步骤S 205 . [0045] 本实施例中,移动终端启动后,自动启动SIM卡验证工具,验证SIM卡的IMSI是否发生变化; 如果是,则说明移动终端的SIM卡已更换。 开机后自动启动SIM卡检测功能的方法如下: [0046] 在终端的Java应用描述文件中增加了MIDlet-1-Type:autostart属性,同时在Java应用描述文件中也增加了自动启动权限,具体格式为: [0047] MIDlet-权限:javax.microedition.midlet.AutoStart 权限。 [0048] 脚步 202 :移动终端向服务器发送IMEI和IMSI的匹配信息。 [0049] 本实施例中,移动终端通过短消息向服务器发送IMEI和IMSI的匹配信息。 [0050] 脚步 203 :服务器更新移动终端IMEI和IMSI的匹配信息。 [0051] 本实施例中,服务器接收到短消息后,通过修改移动终端的IMEI对应的IMSI号,更新IMEI与移动终端的IMSI的匹配信息。 [0052] 脚步 204 :服务器判断更新后的IMEI是否为在服务器注册的移动终端的IMEI; 如果是,转步骤S 205 ; 否则,流程终止。 [0053] 脚步 205 :服务器向移动端发送推送通知。 [0054] 在本实施例中,服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI号码,根据IMSI号码获取移动终端的手机号码,然后向客户端发送推送通知。 移动终端根据手机号码要求移动终端进行定位。 [0055] 另外,在移动端的Java应用描述文件中设置了MIDlet-Push-<1>属性,即: [0056] MIDlet-Push-1:sms://:8080,MIDletLocation,13900000000。添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation, 推送通知的有效来源为号码为13900000000的服务器。 除了SMS协议之外,本发明当然还可以采用传输控制协议或用户数据报协议,本发明对此不做限制。 [0057] 脚步 206 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0058]在本实施例中,定位程序为J2ME程序的定位API,符合JSR 179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以采用基于GPS的卫星定位方法、蜂窝网络的定位方法或基于蓝牙的近距离定位方法,也可以结合上述方式。 [0059] 脚步 207 :移动终端向服务器发送地理位置信息。 [0060] 在本实施例中,地理位置信息至少包括移动终端的经纬度信息。 [0061] 脚步 208 :服务器接收并显示移动终端发送的地理位置信息。 [0062] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0063] 脚步 209 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0064] 本实施例中,服务器根据开放移动联盟定义的设备管理协议向移动终端发送LAWMO命令。 服务器通过SyncML协议集中的设备管理协议向移动终端发送锁定命令。 [0065] 脚步 210 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S 209 和步骤S 210 不是必要的步骤。 [0066] 在本实施例中,当移动终端丢失时,如果捡到者或小偷因电池电量低或想换SIM卡而关闭移动终端,当捡到者或小偷再次打开移动终端时,手机 终端首先验证移动终端的SIM卡是否被更换; 若SIM卡未更换,则直接通过服务器向移动终端发送推送通知。 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知。 移动终端接收到推送通知后定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户检索移动终端。 从而避免了丢失移动终端中的数据泄露,保证了用户的个人信息安全。 [0067] 图3示出了本发明移动终端定位系统实施例的结构示意图。 [0068] 一种移动终端定位系统,包括服务器 10 和移动终端 20 , 其中移动终端 20 包括一个定位模块 201 . [0069] 服务器配置为向移动终端发送推送通知 20 ,接收移动终端发送的地理位置信息 20 ; 定位模块 201 用于接收到推送通知后进行自定位,以获取移动终端的地理位置信息 20 ,并将地理位置信息发送给服务器 10 . [0070] 在本实施例中,服务器 10 可用于向移动端发送推送通知 20 用户发现移动端后 20 丢失了。 移动端 20 通过定位模块定位其地理位置信息 201 并将地理位置信息发送给服务器 10帮助用户找回移动终端 20 . [0071] 图4示出了本发明移动终端定位系统另一实施例的结构示意图。 [0072] 服务器 10 还用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 除了定位模块 201 , 移动端 20 还包括锁定模块 205 和一个删除模块 204 , SIM卡检测模块 202 以及匹配的信息发送模块 203 . [0073] 锁定模块 205 配置为锁定移动端 20 收到锁定命令后。 删除模块 204 用于接收到删除命令后删除内存中的数据。 SIM卡检测模块 202 用于检测移动终端的SIM卡是否被更换。 匹配信息发送模块 203 用于在更换SIM卡时向服务器发送IMEI和IMSI的匹配信息。 [0074] 服务器 10 还用于更新移动终端的IMEI与IMSI的匹配信息 20 接收到IMEI与IMSI的匹配信息后在服务器注册,判断更新后的IMEI是否为在服务器注册的移动终端的IMEI 10 . [0075] 在本实施例中,移动终端后 20 丢失,如果发现者或小偷关闭移动终端 20 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 20 再次,移动终端首先验证移动终端的SIM卡是否为 20 已更改; 如果SIM卡没换过,服务器 10 直接用于向移动端发送推送通知 20 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 20 ; 移动终端 20 通过定位模块定位其地理位置信息 201 收到推送通知后,将地理位置信息发送给服务器 10 帮助用户找回移动终端 20 . 因此,移动终端中的数据 20 防止泄露,保障用户个人信息安全。 [0076] 图5示出了本发明移动终端一个实施例的结构示意图。 [0077] 移动端 30 包括一个定位模块 301 ,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息 30 ,并将地理位置信息发送给服务器。 [0078] 在本实施例中,服务器可以用于向移动终端发送推送通知 30 用户发现移动端后 30 丢失了。 移动端 30 对其地理位置信息进行定位,并将地理位置信息发送给服务器,以帮助用户检索移动终端 30 . [0079] 图6示出了本发明移动终端另一实施例的结构示意图。 [0080] 除了定位模块 301 , 移动端 40 还包括锁定模块 302 , 删除模块 303 , SIM卡检测模块 304 , 以及匹配的信息发送模块 305 . [0081] 锁定模块 302 配置为锁定移动端 40 收到服务器发送的锁定命令后; 删除模块 303 用于接收到服务器发送的删除命令后,删除内存中的数据。 SIM卡检测模块 304用于检测SIM卡是否被更换。 匹配信息发送模块 305 用于当移动终端的SIM卡更换时,向服务器发送IMEI和IMSI的匹配信息。 [0082] 在本实施例中,移动终端后 40 丢失,如果发现者或小偷关闭移动终端 40 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 40 再次,移动终端首先验证移动终端的SIM卡是否为 40 已更改; 若SIM卡未更换,则直接使用服务器向移动终端发送推送通知 40 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 40 ; 移动终端 40 通过定位模块定位其地理位置信息 301 收到推送通知后,将地理位置信息发送给服务器,帮助用户找回移动终端 40 . 因此,移动终端中的数据 40 防止泄露,保障用户个人信息安全。 [0083] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的范围,任何基于本发明的说明书和附图所作的等效结构或等效流程变换,直接或间接应用于其他相关技术领域 落入本发明的专利保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.945 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.946 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.946 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.947 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.948 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.948 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.949 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.949 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.949 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120276924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.956 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.957 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.957 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.958 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.958 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.958 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270637(Integer), CN101835143A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.968 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.969 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.969 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270637(Integer), EP2509375A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.979 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.979 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.980 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270637(Integer), EP2509375A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.991 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.992 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:12.992 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270637(Integer), US20120276924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.006 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.006 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.006 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270637(Integer), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.018 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.018 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.018 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120276924A1(String), US20120276924A1(String), 1351699200(Integer), 270637(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.030 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.030 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.030 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LI, JINMIN(String), XU, LING(String), SHI(String), YUE, HUI(String), 中兴通讯股份有限公司(String), LI JINMIN(String), XU LING(String), 德世股份有限公司(String), YUE HUI(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.033 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.034 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.034 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 0(Integer), 1681974673(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.041 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.042 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.042 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.043 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.043 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.043 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.053 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.054 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.054 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LI, JINMIN(String), LI JINMIN(String), 0(Integer), 1681974673(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.066 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.068 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.068 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: XU, LING(String), XU LING(String), 0(Integer), 1681974673(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.079 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.079 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.080 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHI(String), 德世股份有限公司(String), 0(Integer), 1681974673(Integer), 1(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.091 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.092 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.093 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: YUE, HUI(String), YUE HUI(String), 0(Integer), 1681974673(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.105 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.107 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.107 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.109 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.110 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.110 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75904(Integer), 2(Integer), 184954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.119 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.119 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.120 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75905(Integer), 2(Integer), 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.131 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.132 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.132 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75906(Integer), 2(Integer), 184954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.149 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.150 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.150 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75907(Integer), 2(Integer), 184954(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.159 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.160 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.161 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.162 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.162 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.163 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.164 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.165 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.166 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75904(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.167 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.168 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.168 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.169 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.169 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.169 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.176 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.177 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.178 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.179 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.180 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.180 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.181 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.182 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.182 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.193 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.196 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.196 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.198 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.198 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.199 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method of providing Karaoke service to mobile terminals using a wireless connection between the mobile terminals(String), 使用移动终端之间的无线连接向移动终端提供卡拉OK服务的方法(String), US7142807B2(String), A method of providing a Karaoke service to mobile terminals through wireless connection between them. The mobile terminals are grouped as a service group and one of them is designated as a master mobile terminal and the other mobile terminals as slave mobile terminals. The master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service content to be received from the Karaoke service provider in all the mobile terminals of the service group. If the master mobile terminal transmits a play command to the slave mobile terminals, all the mobile terminals start to play Karaoke music according to the service contents.(String), 一种通过移动终端之间的无线连接向移动终端提供卡拉OK服务的方法。 移动终端被分组为一个服务组,其中一个被指定为主移动终端,而其他移动终端被指定为从移动终端。 主移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制从服务组的所有移动终端中的卡拉OK服务提供商接收的服务内容。 如果主移动终端向从移动终端发送播放命令,则所有移动终端根据服务内容开始播放卡拉OK音乐。(String), US10/761970(String), 1074614400(Integer), US7142807B2(String), 1164643200(Integer), 1164643200(Integer), 美国(String), 4(Integer), KR(String), 3(Integer), 9(Integer), JP2000122671A | US5588842A | US5689081A | US5691494A | US5824934A | US5885085A | US6062868A | US6074215A | USRE37131E1(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.212 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.212 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.212 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.214 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.215 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.215 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\dace07ac660849f9b8287cf66a6ac63a.png(String), 184955(Integer), dace07ac660849f9b8287cf66a6ac63a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.224 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.225 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.225 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.226 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.227 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.227 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of providing Karaoke service to mobile terminals using a wireless connection between the mobile terminals(String), 使用移动终端之间的无线连接向移动终端提供卡拉OK服务的方法(String), US7142807B2(String), A method of providing a Karaoke service to mobile terminals through wireless connection between them. The mobile terminals are grouped as a service group and one of them is designated as a master mobile terminal and the other mobile terminals as slave mobile terminals. The master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service content to be received from the Karaoke service provider in all the mobile terminals of the service group. If the master mobile terminal transmits a play command to the slave mobile terminals, all the mobile terminals start to play Karaoke music according to the service contents.(String), 一种通过移动终端之间的无线连接向移动终端提供卡拉OK服务的方法。 移动终端被分组为一个服务组,其中一个被指定为主移动终端,而其他移动终端被指定为从移动终端。 主移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制从服务组的所有移动终端中的卡拉OK服务提供商接收的服务内容。 如果主移动终端向从移动终端发送播放命令,则所有移动终端根据服务内容开始播放卡拉OK音乐。(String), US10/761970(String), 1074614400(Integer), US7142807B2(String), 1164643200(Integer), 1164643200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 3(Integer), 9(Integer), JP2000122671A | US5588842A | US5689081A | US5691494A | US5824934A | US5885085A | US6062868A | US6074215A | USRE37131E1(String), \20230420\dace07ac660849f9b8287cf66a6ac63a.png(String), 15(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.238 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.238 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.238 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.240 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.241 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.241 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 1. A method of providing a Karaoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals having a wireless connection function to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating all other mobile terminals as slave mobile terminals;connecting the master mobile terminal to a Karaoke service provider through a mobile communication network and controlling service content to be received from theKaraoke service provider in all the mobile terminals of the service group; and playing Karaoke music according to the service content by all the mobile terminals in the service group when the master mobile terminal transmits a play command to the slave mobile terminals, wherein the master and slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 1.一种通过无线连接向移动终端提供卡拉OK服务的方法,包括步骤:将移动终端与具有无线连接功能的移动终端分组为一个服务组,以接收卡拉OK业务;指定其中一个移动终端为主移动终端;将所有其他移动终端指定为从属移动终端;通过移动通信网络将主移动终端连接到卡拉OK服务提供商,并控制从主移动终端接收的服务内容服务组所有移动终端中的卡拉OK服务商;主移动终端向从移动终端发送播放命令时,服务组内的所有移动终端根据服务内容播放卡拉OK音乐,其中主从移动终端根据导频时钟信号进行同步在播放步骤中同时播放。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.241 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 2. The method of claim 1, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 2.如权利要求1所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.241 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 3. The method of claim 1, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 3.如权利要求1所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.241 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 4. The method of claim 1, wherein the step of controlling the service content to be received comprises the steps of:searching for the service content from the Karaoke service provider;transmitting information about the service content to the slave mobile terminals in the service group; andreceiving the service content from the Karaoke service provider according to the service content information in the master mobile terminal and the slave mobile terminals to receive.(String), 4.如权利要求1所述的方法,其中控制接收服务内容的步骤包括:从卡拉OK服务提供商处搜索服务内容;向服务组中的从属移动终端发送服务内容信息;和主移动终端和从移动终端根据服务内容信息从卡拉OK服务商处接收服务内容。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.241 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 5. The method of claim 1, wherein the step of controlling the service content comprises the steps of:searching for the service content from the Karaoke service provider;receiving the service content from the Karaoke service provider in the master mobile terminal; andtransmitting the service content from the master mobile terminal to the slave mobile terminals by wireless connections between the master mobile terminal and the slave mobile terminals.(String), 5.如权利要求1所述的方法,其中控制服务内容的步骤包括以下步骤:从卡拉OK服务提供商处搜索服务内容;在主移动终端中接收来自卡拉OK服务提供商的服务内容;和通过主移动终端和从移动终端之间的无线连接将主移动终端的业务内容传输到从移动终端。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.242 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 6. A method of providing a Kraoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating the other mobile terminals as slave mobile terminals;receiving, in the slave mobile terminals, service contents from a Karaoke service provider under control of the master mobile terminal; andplaying Karaoke music according to the service contents if the slave mobile terminals receive a play command from the master mobile terminal, wherein the master and the slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 6.一种通过无线连接向移动终端提供Kraoke服务的方法,包括步骤:将移动终端与接收卡拉OK业务的移动终端分组为一个业务组;指定其中一个移动终端为主移动终端;指定其他移动终端为从移动终端;从属移动终端接收主移动终端控制下的卡拉OK服务商的服务内容;和如果从移动终端接收到主移动终端的播放命令,则根据业务内容播放卡拉OK音乐,其中在播放步骤中,主从移动终端根据导频时钟信号同步同步播放。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.242 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 7. The method of claim 6, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 7.如权利要求6所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.242 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 8. The method of claim 6, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 8.如权利要求6所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.242 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 9. The method of claim 6, wherein the step ofreceiving the service contents, comprises the steps of:transmitting information about the service contents from the Karaoke service provider to the slave mobile terminals through the master mobile terminal; andconnecting the slave mobile terminals to the Karaoke service provider and transmitting the service contents to the slave mobile terminal.(String), 9.如权利要求6所述的方法,其中的步骤接收服务内容,包括以下步骤:将卡拉OK服务商的服务内容信息通过主移动终端传输给从移动终端;和将从移动终端连接到卡拉OK服务提供商,并将服务内容传输到从移动终端。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.242 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 10. The method of claim 6, wherein the slave mobile terminals receive the service contents from the master mobile terminal by the wireless connection.(String), 10.如权利要求6所述的方法,其中从移动终端通过无线连接从主移动终端接收服务内容。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.242 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 11. The method of claim 6, wherein the slave mobile terminals are further grouped as a predetermined number of sub-service groups according to a number of channels.(String), 11.如权利要求6所述的方法,其中从属移动终端根据频道数进一步分组为预定数量的子业务组。(String), 1(Integer), 10(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.243 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 12. The method of claim 11, wherein each of the sub-service groups receives different sound data and plays Karaoke music according to the sound data.(String), 12.如权利要求11所述的方法,其中每个子服务组接收不同的声音数据,并根据声音数据播放卡拉OK音乐。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.243 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 13. The method of claim 12, wherein the sound data is from one of a left channel and a right channel for stereo sound.(String), 13.如权利要求12所述的方法,其中声音数据来自立体声的左声道和右声道之一。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.243 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 14. The method of claim 12, wherein the sound data is from one of channels for digital surround sound 5.1.(String), 14.如权利要求12所述的方法,其中声音数据来自数字环绕声5.1的通道之一。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.243 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 15. The method of claim 12, wherein the sound data is from one of a predetermined number of sound sources divided from multiple sound sources.(String), 15.如权利要求12所述的方法,其中声音数据来自多个声源划分的预定数量的声源之一。(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.362 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.362 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.363 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.363 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.364 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184955(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119 to an application entitled “Method of Providing Karaoke Service to Mobile Terminals Using Wireless Connection between the Mobile Terminals” filed in the Korean Industrial Property Office on Feb. 13, 2003 and assigned Serial No. 2003-8989, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a method of providing a service through a mobile terminal, and in particular, to a method of providing a Karaoke service to a mobile terminal, and providing a computer-readable recording medium to record a program thereon for performing the Karaoke service method. [0004]2. Description of the Related Art [0005]Due to its portability and convenience, the mobile terminal has emerged as a necessity in daily living. Commonly, mobile terminals are equipped with a variety of functions including phonebook and scheduler. Accordingly, they serve as a personal information manager in addition to a means for making phone calls. 2.5th generation mobile terminals, based on IS (International Standard)-95C, and 3rd generation mobile terminals such as IMT (International Mobile Communication)-2000 terminals provide additional multimedia service for personal entertainment purposes. [0006]A Karaoke function, a type of personal entertainment service, plays songs across various genres with lyrics and animation through a mobile terminal. FIG. 1 illustrates a mobile communication system for providing a conventional Karaoke service. Referring to FIG. 1, the Karaoke service is provided over a typical mobile communication network. Hence, the Karaoke service is provided directly from a service provider (SP) over the mobile communication network rather than a service from the mobile communication network itself. [0007]The mobile communication system is comprised of a mobile terminal 11 for receiving the Karaoke service over the mobile communication network, a home location register (HLR) 12 and an authentication center (AC) 13 for providing the registration information of the mobile terminal 11, a mobile communication network 14 for connecting SPs to users, and a Karaoke SP 15 for providing the Karaoke service. [0008]In operation, the user of the mobile terminal 11 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 then authenticates the user through the HLR 12 and the AC 13 and provides the audio data stored in its database to the user. The mobile terminal 11 plays the song with its lyric displayed using the received audio data, enabling the user to sing along. [0009]In general, a user enjoys Karaoke music with others rather than alone. The volume of music that a single mobile terminal plays depends on its speaker and is usually not loud enough for a plurality of users to enjoy the music. In addition, no matter how good the speaker is, it cannot offer enough volume for them with the single sound source. [0010]In view of diverse voice services and rapid changes in their formats, the Karaoke SP 15 attempts to attract mobile subscribers with new features such as accompaniment with multichannel surround sound effects including stereo, or accompaniment with higher-note polyphonic sound through the existing mobile terminal limited to a 40-note polyphonic sound capacity. However, with the service deployment depending on the performance of an individual mobile terminal in the conventional technology, the benefits of those services are often elusive. SUMMARY OF THE INVENTION [0011]It is, therefore, an object of the present invention to provide a Karaoke service method using wireless connections between mobile terminals that are equipped with a Karaoke function, for playing music accompaniment concurrently through the mobile terminals by synchronizing them, and a computer-readable recording medium for recording a program thereon for performing the Karaoke service. [0012]It is another object of the present invention to provide a Karaoke service method for playing music with a high volume, surround sound effects, and various sound sources. [0013]The above and other objects are achieved by providing a method of providing a Karaoke service to a mobile terminal through wireless connections, and a computer-readable recording medium having a program thereon to perform the Karaoke service. [0014]According to one aspect of the present invention, in the Karaoke service method, the mobile terminal is grouped as a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group. The master mobile terminal transmits a play command to the slave mobile terminals, and all the mobile terminals start to play Karaoke music according to the service contents. [0015]According to another aspect of the present invention, in the Karaoke service method, a mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal. Upon receiving a play command from a master mobile terminal, it starts to play Karaoke music according to the service contents. [0016]According to a further aspect of the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. In the first function, a mobile terminal is grouped in a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal in the first function is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group in the second function. The master mobile terminal transmits a play command to the slave mobile terminals, and then all the mobile terminals start to play Karaoke music according to the service contents in the third function. [0017]According to still another aspect o the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. The program performs first, second, and third functions. In the first function, the mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and is designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal in the second function. Upon receiving a play command from the master mobile terminal, a slave mobile terminal starts to play Karaoke music according to the service contents in the third function. BRIEF DESCRIPTION OF THE DRAWINGS [0018]The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which: [0019]FIG. 1 illustrates a mobile communication system that provides a conventional Karaoke service to a mobile terminal; [0020]FIG. 2 illustrates the configuration of a mobile communication system that provides a Karaoke service to a plurality of mobile terminals through wireless connections between them according to an embodiment of the present invention; [0021]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention; [0022]FIG. 4 illustrates examples of screen displays in a mobile terminal for receiving the Karaoke service through wireless connection with other mobile terminals according to the embodiment of the present invention; and [0023]FIGS. 5A and 5B illustrate embodiments of contents reception for the Karaoke service through wireless connections with other mobile terminals according to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0024]Preferred embodiments of the present invention will be described in detail herein below with reference to the accompanying drawings. In the following description, well-known functions and constructions are not described in detail since they would obscure the invention in unnecessary detail. [0025]FIG. 2 illustrates a mobile communication system for providing a Karaoke service to mobile terminals through wireless connections between them according to an embodiment of the present invention. Referring to FIG. 2, the mobile communication system is comprised of a master mobile terminal 21 that receives the Karaoke service over a mobile communication network 14, slave mobile terminals 22 connected to the master mobile terminal 21, for receiving the same Karaoke service, the HLR 12 and the SC 13 for providing registration information for the mobile terminals 21 and 22, the mobile communication network 14 for connecting SPs to mobile subscribers, and a Karaoke SP 15 for providing a Karaoke service. [0026]In operation, the master mobile terminal 21 is connected to the slave mobile terminals 22, forming a service group. The user of the master mobile terminal 21 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 authenticates the user through the HLR 12 and the AC 13 and transmits the audio data to the master mobile terminal 21 and the slave mobile terminals 22. When the master mobile terminal 21 transmits a play command to the slave mobile terminals 22, the master and slave mobile terminals 21 and 22 start to simultaneously play the song, displaying its lyrics using the audio data, enabling users sing along. [0027]This method of providing the Karaoke service to mobile terminals by synchronizing them will be described below with reference to FIG. 3. [0028]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention. Referring to FIG. 3, the mobile terminals equipped with the functions of wireless Internet browsing, Karaoke music playing, and wireless connection are grouped in a service group in step 31. The wireless connections refer to connections between mobile terminals by Bluetooth, IRDA (Infrared Data Association), or wireless LAN (Local Area Network). The service group, corresponding to a working group in a PC (Personal Computer) network, is set by assigning the same wireless connection address to the mobile terminals. Thus, interference from other mobile terminals having a different wireless connection address is avoided. [0029]In step 32, one of the mobile terminals in the service group is designated as a mater mobile terminal with the other mobile terminals designated as slave terminals. The designation of master and slave MT's will be described in more detail hereinbelow with reference to FIG. 4. [0030]FIG. 4 illustrates examples of screen displays related to the Karaoke service in a mobile terminal according to the embodiment of the present invention. Referring to FIG. 4, a service group window 41 displays a wireless connection address assigned commonly to mobile terminals in the same service group, and a mobile terminal state window 42 displays the state of the mobile terminal, i.e., master or slave. [0031]To provide the Karaoke service in various modes, a slave grouping can be further divided into a slave channel 1, a slave channel 2, etc. If the Karaoke SP provides multichannel sound, that is, the audio is divided into discrete channels, center, left front, right front, left rear, and right rear, slave channel 1 outputs one of the channels such as the right channel for stereo sound or the left rear channel for digital surround sound 5.1, slave channel 2 outputs another channel, and the other channels output their respective channel sound. When sound from multiple sound sources is divided into 16- to 40-note polyphonic sounds, each channel may output its assigned sounds. [0032]The mobile terminal state is set to “master” only for a master mobile terminal. The master mobile terminal can remotely control the Internet and Karaoke functions of the slave mobile terminals through the wireless connections between them. [0033]Returning to FIG. 3, after the master mobile terminal 21 selects a song and requests the song from the Karaoke SP 15 through the mobile communication network 14, the master and slave mobile terminals 21 and 22 receive service contents related to the song from the Karaoke SP 15 in step 33. The contents reception is carried out in two ways, which will be described later with reference to FIGS. 5A and 5B. [0034]When the master mobile terminal 21 sends a play command to the slave mobile terminals 22 through wireless connection, for example, by Bluetooth, IRDA, or wireless LAN, all the mobile terminals 21 and 22 in the service group start to play the song simultaneously, synchronized according to a pilot channel clock signal in step 34. [0035]Upon request for a call setup for any mobile terminal in the service group during the music accompaniment playing, the mobile terminal is released from synchronization and connected to a call. The call setup request acts as an interrupt to the Karaoke service. [0036]FIGS. 5A and 5B illustrate embodiments of the contents reception in the Karaoke service using wireless connection between mobile terminals according to the present invention. Referring to FIG. 5A, a mobile terminal 51 is designated as a master and mobile terminals 52 are designated as slaves in a service group. After the service group is set in step 31 and the master and slave mobile terminals 51 and 52 are designated in step 32, the mobile terminals 51 and 52 receive service contents (i.e., Karaoke audio data) from the Karaoke SP 15 in step 33 in FIG. 4. [0037]Describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in the Karaoke SP 15 through the mobile communication network 14 in step 501 and transmits a contents receive command to the slave mobile terminals 52 in step 502. Since the master mobile terminal 51 can remotely control the wireless Internet function of the slave mobile terminals 52, the master mobile terminal 51 and the slave mobile terminals 52 under the control of the master mobile terminal 51 receive the same service contents in step 503. [0038]Referring to FIG. 5B, describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in step504 and receives receive service contents from the Karaoke SP 15 through the mobile communication network 14 in step 505. The master mobile terminal 51 then transmits the service contents to the slave mobile terminals by wireless connection in step 506. [0039]The contents receiving method illustrated in FIG. 5A enables each mobile terminal to receive a different channel or a different sound source since master and slave mobile terminals all access the Karaoke SP. If the SP prohibits content duplication and reproduction, retransmission of the service contents from the master mobile terminal to the slave mobile terminals is not permitted. In this sense, the method of FIG. 5A is useful. When accessing the SP, each slave mobile terminal transmits a packet indicating a slave channel to receive corresponding channel contents. [0040]Alternatively, rates for using service contents are saved and the same data can be broadcast to mobile terminals in the same service group in the content receiving method illustrated in FIG. 5B. [0041]As described above, the present invention offers the following benefits: (1) provision of Karaoke music with high volume, surround sound effects, and multiple sound sources improves the quality of the Karaoke service; (2) since a plurality of mobile terminals download the same audio data from an SP and users enjoy the Karaoke service through their mobile terminals together rather than alone, the number of service connections is increased and the novel service deployment attracts more customers from an SP's point of view; (3) the extension of the use of wireless data communication between mobile terminals enables mobile terminal manufacturers to create new customer demands; and (4) a program for carrying out the Karaoke service can be written on a computer-readable recording medium (e.g., CD ROM, RAM, floppy disk, hard disk, and optomagnetic disk). [0042]While the present invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. § 119 于 2003 年 2 月 13 日向韩国工业产权局提交的题为“使用移动终端之间的无线连接向移动终端提供卡拉 OK 服务的方法”的申请,编号为 2003-8989,其内容为 通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明总体上涉及一种通过移动终端提供服务的方法,具体地,涉及一种向移动终端提供卡拉OK服务的方法,以及提供一种计算机可读记录介质以在其上记录用于执行该服务的程序的计算机可读记录介质。 卡拉OK服务方法。 [0004] 2.相关技术的描述 [0005] 由于其便携性和便利性,移动终端已成为日常生活中的必需品。 通常,移动终端配备有电话簿、日程安排等多种功能。 因此,除了拨打电话之外,它们还充当个人信息管理器。 2.5 th 一代移动终端,基于IS(国际标准)-95C,和3 rd 一代移动终端,例如 IMT(国际移动通信)-2000 终端,为个人娱乐目的提供额外的多媒体服务。 [0006] 卡拉OK功能是一种个人娱乐服务,通过移动终端播放带有歌词和动画的各种类型的歌曲。 如图。 图1图示了用于提供传统卡拉OK服务的移动通信系统。 参考图。 如图1所示,卡拉OK服务是通过典型的移动通信网络提供的。 因此,卡拉OK服务是直接从移动通信网络上的服务提供商(SP)提供的,而不是来自移动通信网络本身的服务。 [0007] 移动通信系统由移动终端组成 11 为了通过移动通信网络接收卡拉 OK 服务,归属位置寄存器 (HLR) 12 和认证中心(AC) 13 用于提供移动终端的注册信息 11 , 移动通信网络 14 用于将 SP 连接到用户,以及卡拉 OK SP 15 提供卡拉OK服务。 [0008] 在操作中,移动终端的用户 11 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 然后通过 HLR 对用户进行身份验证 12 和交流 13 并将存储在其数据库中的音频数据提供给用户。 移动终端 11 使用接收到的音频数据播放带有歌词的歌曲,使用户能够跟着唱。 [0009] 一般而言,用户与他人而不是单独一起享受卡拉OK音乐。 单个移动终端播放的音乐音量取决于其扬声器,并且通常不足以让多个用户欣赏音乐。 另外,再好的音箱,单声源也无法为他们提供足够的音量。 [0010] 鉴于语音服务的多样化和格式的快速变化,卡拉 OK SP 15 试图通过新功能来吸引移动用户,例如伴奏包括立体声在内的多声道环绕声效果,或通过现有的仅限于 40 音符复音容量的移动终端伴奏更高音符的复音。 然而,在传统技术中,服务部署依赖于单个移动终端的性能,这些服务的好处往往难以捉摸。 发明内容 [0011] 因此,本发明的一个目的是提供一种卡拉OK服务方法,该方法使用配备有卡拉OK功能的移动终端之间的无线连接,通过移动终端同步来同时播放音乐伴奏,以及一种计算机可读记录。 用于在其上记录用于执行卡拉OK服务的程序的介质。 [0012]本发明的另一目的在于提供一种卡拉OK服务方法,用于播放具有高音量、环绕声效果和多种音源的音乐。 [0013] 通过提供一种通过无线连接向移动终端提供卡拉OK服务的方法,以及其上具有用于执行卡拉OK服务的程序的计算机可读记录介质来实现上述和其他目的。 [0014] 根据本发明的一个方面,在卡拉OK服务方法中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容。 主移动终端向从移动终端发送播放命令,所有移动终端根据服务内容开始播放卡拉OK音乐。 [0015] 根据本发明的另一方面,在卡拉OK服务方法中,将移动终端与移动终端分组在服务组中以接收卡拉OK服务,并指定为服务组中的主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 主移动终端收到播放指令后,根据服务内容开始播放卡拉OK音乐。 [0016] 根据本发明的另一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 在第一功能中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 在第一功能中被指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并在第二功能中控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容 . 主移动终端向从移动终端发送播放命令,然后所有移动终端根据第三功能中的服务内容开始播放卡拉OK音乐。 [0017] 根据本发明的又一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 该程序执行第一、第二和第三功能。 在第一个功能中,将移动终端与移动终端分组在一个服务组中以接收卡拉OK服务,并在服务组中将移动终端指定为主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在第二功能中在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 从移动终端接收到主移动终端的播放命令后,根据第三功能中的服务内容开始播放卡拉OK音乐。 附图的简要说明 [0018] 本发明的上述和其他目的、特征和优点将在以下结合附图的详细描述中变得更加明显,其中: [0019] 如图。 附图说明图1示出了向移动终端提供传统卡拉OK服务的移动通信系统; [0020]如图。 图2示出了根据本发明实施例的通过多个移动终端之间的无线连接向多个移动终端提供卡拉OK服务的移动通信系统的配置。 [0021] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 [0022] 如图。 图4示出了根据本发明实施例的通过与其他移动终端的无线连接来接收卡拉OK服务的移动终端中的屏幕显示示例。 和 [0023] 图 图5A和5B示出了根据本发明通过与其他移动终端的无线连接来接收卡拉OK服务的内容的实施例。 优选实施例的详细说明 [0024] 下面结合附图对本发明的优选实施例进行详细说明。 在以下描述中,没有详细描述众所周知的功能和结构,因为它们会以不必要的细节模糊本发明。 [0025] 如图。 图2图示了根据本发明实施例的用于通过移动终端之间的无线连接向移动终端提供卡拉OK服务的移动通信系统。 参考图。 2、移动通信系统由主移动终端组成 21 通过移动通信网络接收卡拉 OK 服务的 14 , 从移动终端 22 连接到主移动终端 21 ,为了接收相同的卡拉 OK 服务,HLR 12 和 SC 13 为移动终端提供注册信息 21 和 22 , 移动通信网络 14 用于将 SP 连接到移动用户,以及卡拉 OK SP 15 提供卡拉 OK 服务。 [0026] 在操作中,主移动终端 21 连接到从移动终端 22 ,形成服务群。 主移动终端用户 21 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 通过 HLR 对用户进行身份验证 12 和交流 13 并将音频数据传输到主移动终端 21 和从移动终端 22 . 当主控移动终端 21 向从移动终端发送播放命令 22 ,主从移动终端 21 和 22 开始同时播放歌曲,使用音频数据显示歌词,让用户跟着唱。 [0027] 下面将参照图3描述通过同步移动终端向移动终端提供卡拉OK服务的这种方法。 3. [0028] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 参考图。 3、将具备无线上网浏览、卡拉OK音乐播放、无线连接功能的移动终端分步归入一个服务组 31 . 无线连接是指移动终端之间通过蓝牙、IRDA(红外数据协会)或无线LAN(局域网)的连接。 通过为移动终端分配相同的无线连接地址来设置服务组,对应于PC(个人计算机)网络中的工作组。 因此,避免了来自具有不同无线连接地址的其他移动终端的干扰。 [0029] 在步骤 32 ,服务组中的一个移动终端被指定为主移动终端,其他移动终端被指定为从终端。 下文将参考图1更详细地描述主MT和从MT的指定。 4. [0030]如图。 图4图示了根据本发明实施例的移动终端中与卡拉OK服务相关的屏幕显示的示例。 参考图。 4、一个服务组窗口 41 显示同一服务组内移动终端通用分配的无线连接地址,移动终端状态窗口 42 显示移动终端的状态,即主或从。 [0031] 为了提供各种模式的卡拉OK服务,一个从属分组可以进一步划分为一个从属频道 1 , 从属通道 2 等。如果Karaoke SP提供多声道声音,即音频分为离散声道,中、左前、右前、左后、右后,从声道 1 输出其中一个声道,例如用于立体声的右声道或用于数字环绕声的左后声道 5 . 1 , 从通道 2 输出另一个通道,其他通道输出各自通道的声音。 当来自多个声源的声音被分成 16 到 40 音符的复音时,每个通道都可以输出其分配的声音。 [0032] 移动终端状态仅针对主移动终端设置为“主”。 主移动终端可以通过它们之间的无线连接远程控制从移动终端的上网和卡拉OK功能。 [0033] 返回图。 3、掌握移动端后 21 选择一首歌曲并向卡拉 OK SP 请求歌曲 15 通过移动通信网络 14 ,主从移动终端 21 和 22 从卡拉 OK SP 接收与歌曲相关的服务内容 15 在一步 33 . 内容接收以两种方式进行,这将在后面参考图3和图4进行描述。 参见图 5A 和 5B。 [0034] 当主控移动终端 21 向从移动终端发送播放命令 22 通过无线连接,例如通过蓝牙、IRDA或无线局域网,所有移动终端 21 和 22 在服务组中同时开始播放歌曲,根据一个导频通道时钟信号同步 34 . [0035] 在音乐伴奏播放期间,在服务组中的任何移动终端请求建立呼叫时,移动终端从同步中释放并连接到呼叫。 呼叫建立请求充当卡拉 OK 服务的中断。 [0036] 图 图5A和5B示出了根据本发明的使用移动终端之间的无线连接的卡拉OK服务中的内容接收的实施例。 参考图。 5A、移动终端 51 被指定为主机和移动终端 52 被指定为服务组中的从属设备。 步骤中设置服务组后 31 以及主从移动终端 51 和 52 在步骤中指定 32 , 移动终端 51 和 52 从卡拉 OK SP 接收服务内容(即卡拉 OK 音频数据) 15 在一步 33 在图 4. [0037] 描述步骤 33 更详细地说,主移动终端 51 从卡拉 OK SP 中的音乐数据库中选择一首歌曲 15 通过移动通信网络 14 在一步 501 向从移动终端发送内容接收命令 52 在一步 502 . 自主移动端 51 可远程控制从属移动终端的无线上网功能 52 ,主移动终端 51 和从移动终端 52 在主移动终端的控制下 51 在步骤中接收相同的服务内容 503 . [0038] 参考图。 5B,描述步骤 33 更详细地说,主移动终端 51 在步骤中从音乐数据库中选择一首歌曲 504 并从卡拉 OK SP 接收接收服务内容 15 通过移动通信网络 14 在一步 505 . 主控移动终端 51然后在步骤中通过无线连接将服务内容传输到从移动终端 506 . [0039] 图1所示的内容接收方法。 由于主移动终端和从移动终端都访问卡拉OK SP,因此图5A使每个移动终端能够接收不同的频道或不同的声源。 如果SP禁止内容复制和再现,则不允许将服务内容从主移动终端重传到从移动终端。 在这个意义上,图1的方法。 5A很有用。 在接入SP时,每个从移动终端发送一个指示从信道的分组以接收相应的信道内容。 [0040] 或者,在图1所示的内容接收方法中,可以保存使用服务内容的费率并将相同的数据广播到相同服务组中的移动终端。 5B。 [0041] 如上所述,本发明提供以下益处: (1)提供具有高音量、环绕声效果和多声源的卡拉OK音乐,提高了卡拉OK服务的质量。 (2)由于多个移动终端从一个SP下载相同的音频数据,用户通过他们的移动终端一起而不是单独享受卡拉OK服务,增加了服务连接的数量,新颖的业务部署吸引了更多来自SP的客户 观点看法; (3)移动终端之间无线数据通信使用的延伸,使移动终端制造商能够创造新的客户需求; (4)可以将用于进行卡拉OK服务的程序写入计算机可读取的记录介质(例如CD ROM、RAM、软盘、硬盘、光磁盘)上。 [0042] 尽管本发明已经参照其某些优选实施例进行了展示和描述,但本领域技术人员将理解,在不背离所定义的本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变 根据所附权利要求。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.376 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.377 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.377 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.378 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.379 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.380 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.380 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.381 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.381 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.389 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.389 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.389 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.390 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.391 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.391 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270638(Integer), CN1295910C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.399 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.399 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.399 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270638(Integer), CN1522010A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.409 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.409 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.410 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270638(Integer), KR100532288B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.420 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.420 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.420 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270638(Integer), KR1020040073057A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.432 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.432 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.432 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270638(Integer), US20040162062A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.441 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.442 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.442 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270638(Integer), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.451 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.451 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.451 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7142807B2(String), US7142807B2(String), 1164643200(Integer), 270638(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.462 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.463 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.463 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.466 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.467 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.467 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.468 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.469 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.469 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.470 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.470 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.470 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.477 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.478 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.478 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.479 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.480 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.480 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184955(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.482 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.482 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.482 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.490 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.490 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.490 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.491 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.492 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.492 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.493 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.494 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.494 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.495 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.496 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.497 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.498 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.498 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.499 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.509 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.510 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.510 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.511 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.512 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.512 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.514 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.514 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.515 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.522 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.524 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.524 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.526 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.527 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.527 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method of changing standby order of waiting mobile terminals in mobile terminal(String), 移动终端中更改等待移动终端待机顺序的方法(String), US7801528B2(String), A method for changing a standby order of waiting mobile terminals includes displaying a standby order of a plurality of mobile terminals according to an audiovisual communication request order when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal, sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a standby order change request, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message, and displaying the changed standby order.(String), 一种用于改变等待移动终端的待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求,而第一移动终端时,根据视听通信请求顺序显示多个移动终端的待机顺序。 与第二移动终端进行视听通信,当第一移动终端接收到待机指令变更请求时,从第一移动终端向移动通信网络发送待机指令变更请求消息,当第一移动终端接收到待机指令变更请求时,变更第一移动终端的待机指令。 移动终端从移动通信网络接收对应于待机命令更改请求消息的待机命令更改完成消息,并显示更改后的待机命令。(String), US11/769201(String), 1182873600(Integer), US7801528B2(String), 1284998400(Integer), 1284998400(Integer), 美国(String), 4(Integer), KR(String), 2(Integer), 12(Integer), KR1020000042764A | KR1020050017736A | KR1020050053912A | KR1020070012088A | US20020009987A1 | US20030104830A1 | US20060223593A1 | US20080132254A1(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.542 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.542 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.543 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.544 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.545 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.545 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c7dbf48333d84ccf9e1e049edb0e723c.png(String), 184956(Integer), c7dbf48333d84ccf9e1e049edb0e723c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.556 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.557 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.557 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.558 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.559 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.559 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of changing standby order of waiting mobile terminals in mobile terminal(String), 移动终端中更改等待移动终端待机顺序的方法(String), US7801528B2(String), A method for changing a standby order of waiting mobile terminals includes displaying a standby order of a plurality of mobile terminals according to an audiovisual communication request order when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal, sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a standby order change request, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message, and displaying the changed standby order.(String), 一种用于改变等待移动终端的待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求,而第一移动终端时,根据视听通信请求顺序显示多个移动终端的待机顺序。 与第二移动终端进行视听通信,当第一移动终端接收到待机指令变更请求时,从第一移动终端向移动通信网络发送待机指令变更请求消息,当第一移动终端接收到待机指令变更请求时,变更第一移动终端的待机指令。 移动终端从移动通信网络接收对应于待机命令更改请求消息的待机命令更改完成消息,并显示更改后的待机命令。(String), US11/769201(String), 1182873600(Integer), US7801528B2(String), 1284998400(Integer), 1284998400(Integer), 美国(String), 2(Integer), 4(Integer), KR(String), 2(Integer), 12(Integer), KR1020000042764A | KR1020050017736A | KR1020050053912A | KR1020070012088A | US20020009987A1 | US20030104830A1 | US20060223593A1 | US20080132254A1(String), \20230420\c7dbf48333d84ccf9e1e049edb0e723c.png(String), 17(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.567 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.567 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.568 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.569 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.570 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.570 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 1. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals, according to the order in which the audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a request to change the standby order;changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message; anddisplaying the changed standby order.(String), 1.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序,而第一移动终端终端与第二移动终端进行视听通信;当第一移动终端接收到待机顺序变更请求时,第一移动终端向移动通信网络发送待机顺序变更请求消息;当第一移动终端从移动通信网络接收到与待机顺序变更请求消息对应的待机顺序变更完成消息时,变更第一移动终端的待机顺序;和显示更改后的待机顺序。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.570 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 2. The method of claim 1, further comprising:changing the standby order at the mobile communication network in response to the standby order change request message sent by the first mobile terminal.(String), 2.如权利要求1所述的方法,还包括:响应于第一移动终端发送的待机顺序改变请求消息,改变移动通信网络处的待机顺序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 3. The method of claim 2, further comprising sending the changed standby order to the first mobile terminal through the mobile communication network.(String), 3.如权利要求2所述的方法,还包括通过移动通信网络向第一移动终端发送变更后的待机指令。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 4. The method of claim 1, further comprising performing audiovisual communication with another mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 4.如权利要求1所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与另一移动终端进行视听通信。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 5. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals according to the order in which audiovisual communication request orders of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals;changing the standby order if the first mobile terminal approves the requested change of the standby order; anddisplaying the changed standby order.(String), 5.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求命令的顺序显示多个移动终端的待机顺序,而第一移动终端与第二移动终端进行视听通信;当第一移动终端接收到多个移动终端中的第三移动终端的待机顺序变更请求消息时,判断第一移动终端是否同意请求的待机顺序变更;如果第一移动终端同意请求更改备用订单,则更改备用订单;和显示更改后的待机顺序。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 6. The method of claim 5, wherein determining whether the first mobile terminal approves the requested change of the standby order comprises:receiving the standby order change request message of the third mobile terminal from a mobile communication network; andsending a standby order change approval message to the mobile communication network when the standby order change request is approved in response to the received standby order change request message.(String), 6.如权利要求5所述的方法,其中判断第一移动终端是否同意请求的待机顺序变更包括:从移动通信网络接收第三移动终端的待机顺序变更请求消息;和当响应于接收到的备用订单变更请求消息批准备用订单变更请求时,向移动通信网络发送备用订单变更批准消息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 7. The method of claim 6, wherein changing the standby order comprises:receiving a standby order change completion message from the mobile communication network; andchanging the standby order according to the standby order change completion message.(String), 7.如权利要求6所述的方法,其中更改备用订单包括:接收来自移动通信网络的备用订单变更完成消息;和根据备用订单变更完成消息变更备用订单。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 8. The method of claim 6, wherein receiving the standby order change request message of the third mobile terminal comprises:sending a standby order change request message from the third mobile terminal to the mobile communication network; andreceiving the standby order change request message of the third mobile terminal from the mobile communication network in the first mobile terminal.(String), 8.如权利要求6所述的方法,其中接收第三移动终端的待机顺序变更请求消息包括:第三移动终端向移动通信网络发送待机顺序变更请求消息;和第一移动终端中从移动通信网络接收第三移动终端的待机顺序变更请求消息。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.571 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 9. The method of claim 8, wherein changing the standby order comprises:receiving the standby order change approval message sent from the first mobile terminal in the mobile communication network; andchanging the standby order.(String), 9.如权利要求8所述的方法,其中更改备用订单包括:接收移动通信网络中的第一移动终端发送的备用订单变更批准消息;和更改待机顺序。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.572 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 10. The method of claim 9, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal.(String), 10.如权利要求9所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端发送待机顺序改变完成消息。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.572 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 11. The method of claim 8, wherein the standby order change request message sent from the third mobile terminal is sent by the mobile communication network to the first mobile terminal and to a fourth mobile terminal of the plurality of mobile terminals.(String), 11.如权利要求8所述的方法,其中第三移动终端发送的待机顺序变更请求消息由移动通信网络发送给第一移动终端和多个移动终端中的第四移动终端。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.572 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 12. The method of claim 11, wherein changing the standby order comprises:receiving response messages to the standby order change request message from the first mobile terminal and from the fourth mobile terminal in the communication network; andchanging the standby order.(String), 12.如权利要求11所述的方法,其中更改备用订单包括:从通信网络中的第一移动终端和第四移动终端接收对待机顺序改变请求消息的响应消息;和更改待机顺序。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.572 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 13. The method of claim 12, wherein the mobile communication network changes the standby order according to the response messages if the response messages received from the first mobile terminal and from the fourth mobile terminal are identical.(String), 13.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息相同,则移动通信网络根据响应消息改变待机顺序。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.572 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 14. The method of claim 12, wherein the mobile communication network changes the standby order according to the response message of the first mobile terminal if the response messages received from the first mobile terminal and from the fourth mobile terminal are not identical.(String), 14.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息不相同,则移动通信网络根据第一移动终端的响应消息改变待机顺序。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.572 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 15. The method of claim 14, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal, the third mobile terminal, and the fourth mobile terminal.(String), 15.如权利要求14所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端、第三移动终端和第四移动终端发送待机顺序改变完成消息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.573 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 16. The method of claim 12, wherein the response message to the standby order change request message is one of a standby order change approval message and a standby order change non-approval message.(String), 16.如权利要求12所述的方法,其中备用订单变更请求消息的响应消息为备用订单变更批准消息和备用订单变更不批准消息之一。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.573 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 17. The method of claim 5, further comprising performing audiovisual communication with a mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 17.如权利要求5所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与移动终端进行视听通信。(String), 1(Integer), 16(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.704 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.704 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.705 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.705 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.706 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184956(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority from and the benefit of Korean Patent Application No. 10-2007-0004601, filed on Jan. 16, 2007, which is hereby incorporated by reference for all purposes as if fully set forth herein. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method of providing an audiovisual communication service in a mobile terminal, and more particularly, to a method of changing a standby order of waiting mobile terminals in a mobile terminal. [0004]2. Discussion of the Background [0005]As technology of mobile terminals has developed, an improved mobile terminal having a camera unit using an H.324M protocol including an H.245 protocol that allows for audiovisual communication has been provided. [0006]In conventional audiovisual communication technology, when a first mobile terminal receives a request for audiovisual communication from a third mobile terminal while the first mobile terminal is performing audiovisual communication with a second mobile terminal, the first mobile terminal stores information about the third mobile terminal. Thereafter, when the first mobile terminal ends audiovisual communication with the second mobile terminal, the first mobile terminal displays information about the third mobile terminal and performs audiovisual communication with the third mobile terminal. [0007]However, in the conventional audiovisual communication technology, even when the third mobile terminal urgently requests audiovisual communication with the first mobile terminal, the third mobile terminal may have to wait until the first mobile terminal ends audiovisual communication with the second mobile terminal. SUMMARY OF THE INVENTION [0008]The present invention provides a method of changing a standby order of at least two mobile terminals requesting audiovisual communication while a first mobile terminal is performing audiovisual communication. [0009]The present invention further provides a method of changing a standby order of mobile terminals in a standby state according to a standby order change request received from one of at least two mobile terminals waiting for audiovisual communication with the first mobile terminal while the first mobile terminal is performing audiovisual communication. [0010]The present invention further provides a method of displaying information about a mobile terminal requesting audiovisual communication while a first mobile terminal is performing audiovisual communication with a second mobile terminal. [0011]Additional features of the invention will be set forth in the description which follow, and in part will be apparent from the description, or may be learned by practice of the invention. [0012]The present invention discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, sending a standby order change request message to a mobile communication network from the first mobile terminal when the first mobile terminal receives a request to change the standby order, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message corresponding to the standby order change request message, and displaying the changed standby order. [0013]The present invention also discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals, changing the standby order if the first mobile terminal approves the requested change of the standby order, and displaying the changed standby order. [0014]It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. [0016]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0017]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0018]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0019]FIG. 4 is a flowchart showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0020]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0021]FIG. 6 is a flowchart showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0022]FIG. 7 is a message flow diagram showing another method of performing audiovisual communication with waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS [0023]The invention is described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements. [0024]It will be understood that when an element or layer is referred to as being “on” or “connected to” another element or layer, it can be directly on or directly connected to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on” or “directly connected to” another element or layer, there are no intervening elements or layers present. [0025]Exemplary embodiments according to the present invention exemplify a mobile terminal that includes a camera unit and is capable of performing audiovisual communication. That is, a mobile terminal according to exemplary embodiments of the present invention may include an information communication device or multimedia device, such as a mobile communication terminal, a mobile phone, a Personal Digital Assistant (PDA), a smart phone, or a notebook computer, that includes a camera unit and is capable of performing audiovisual communication, and applications thereof. [0026]Exemplary embodiments according to the present invention exemplify audiovisual communication. However, the present exemplary embodiments are not limited to audiovisual communication and may be applied to voice communication. [0027]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0028]Referring to FIG. 1, the system includes a first mobile terminal 100, a second mobile terminal 200, a third mobile terminal 300, a fourth mobile terminal 400, and a mobile communication network 500. [0029]The first mobile terminal may perform audiovisual communication with the second mobile terminal 200 and may receive a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400 while performing audiovisual communication with the second mobile terminal 200. A configuration of the first mobile terminal 100 is described with reference to FIG. 2, and the same configuration may also be applied to the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 and thus, individual descriptions thereof are omitted. [0030]The mobile communication network 500 includes a node to perform the function of a base station, a radio access network (RAN), which is a sub system of the node, a mobile switching center (MSC)/visitor location register (VLR) corresponding to a core network of a circuit switched domain, a home location register (HLR), and a gateway MSC. [0031]The MSC manages call control and mobility of the first mobile terminal 100, and the VLR and the HLR make up a matching device of subscriber information and register and manage information about mobile terminals belonging to the mobile communication network 500 including the first mobile terminal 100. [0032]In the following description, the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 belong to the same mobile communication network 500. However the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 may belong to different mobile communication networks and may be connected through different gateway MSCs. However, it is assumed that a series of processes performed in the RAN, MSC/VLR, HLR, and gateway MSC are performed in the mobile communication network 500. [0033]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0034]Referring to FIG. 2, the mobile terminal 100 includes a radio frequency (RF) unit 101, an input unit 103, a controller 105, a camera unit 107, an image processor 109, a display unit 111, a memory unit 113, and an audio unit 115. [0035]The RF unit 101 performs general wireless communication with the second mobile terminal 200, the third mobile terminal 300, the fourth mobile terminal 400, and the mobile communication network 500. For example, the RF unit 101 transmits and receives voice data, character messages, and multimedia messages using the mobile communication network 500. The RF unit 101 sends image data acquired from the camera unit 107 of the first mobile terminal 100 to the second mobile terminal 200 when the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 200. The RF unit 101 further receives image data acquired by the camera unit of the second mobile terminal 200 and image data acquired by the camera units of the third mobile terminal 300 and the fourth mobile terminal 400 requesting audiovisual communication. The image data of the second mobile terminal 200 may be still and/or moving picture data, and the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be still and/or moving image data. Further, when the third mobile terminal 300 and the fourth mobile terminal 400 perform audiovisual communication with the first mobile terminal 100, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may change to moving picture data. [0036]The input unit 103 may include a general keypad. The input unit 103 may include a touch screen, a touch pad, and a scroll wheel. The input unit 103 receives a user manipulation signal to control operation of the first mobile terminal 100 and provides the manipulation signal to the controller 105. [0037]The controller 105 controls the general operation of the first mobile terminal 100. Particularly, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200, receives a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400, and sets a standby order of audiovisual communication requests. The controller 105 displays image data (namely, image data of a user of the second mobile terminal 200) of the second mobile terminal 200 performing audiovisual communication in the display unit 111. The controller 105 displays image data from each mobile terminal requesting audiovisual communication, in the order in which the audiovisual communication requests were received, on the display unit 111 of the first terminal 100. [0038]In more detail, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be image data mapped to the corresponding mobile terminal and stored in a phone book (not shown) of the first mobile terminal 100. The image data may also be image data acquired by camera units of the third mobile terminal 300 and the fourth mobile terminal 400 when requesting audiovisual communication and may be sent with the request for audiovisual communication. The controller 105 may display the image data of the third mobile terminal 300 and the fourth mobile terminal 400 with thumb-nail type still image data. The controller 105 may also display image data of the second mobile terminal 200, with which the first mobile terminal 100 is performing audiovisual communication, including moving picture data. [0039]The controller 105 sends a standby order change request message REQ_MSG from the first mobile terminal 100 to the mobile communication network 500 through the RF unit 101, receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the changed standby order in the display unit 111. [0040]The controller 105 further receives a standby order change request message REQ_MSG from the mobile terminal having the highest standby position through the mobile communication network 500 and sends a standby order change approval message ACC_MSG to the mobile communication network 500 through the RF unit 101. Thereafter, the controller 105 receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the standby order in the display unit 111. [0041]When the controller 105 determines that the first mobile terminal 100 has ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 controls the RF unit 101 to perform audiovisual communication with the mobile terminal having the highest standby position. In the exemplary embodiments, to “end” the audiovisual communication is to terminate a communication channel formed to perform audiovisual communication with the second mobile terminal 200, and to “convert” an audiovisual communication state to a standby state is to convert to a standby state in order to perform audiovisual communication with another mobile terminal while maintaining the communication channel formed to perform audiovisual communication with the second mobile terminal 200. [0042]The camera unit 107 generates a user's image data to send through the RF unit 101. The camera unit 107 includes an image sensor to convert a photo signal of a subject to an analog signal and a signal processor to convert the analog signal to a digital signal. That is, the camera unit 107 converts a photo signal collected through a lens to a digital signal and generates image data with the converted digital signal. [0043]The image processor 109 processes image data generated in the camera unit 107 and image data received through the RF unit 101 into a format corresponding to the display unit 111. [0044]The controller 105 controls the display unit 111 to display various operation states, operation results, and other information from the units of the first mobile terminal 100. The display unit 111 may include a display device such as a liquid crystal display (LCD), organic light emitting diodes (OLED), or a plasma display panel (PDP). [0045]The display unit 111 displays image data input through the RF unit 101 and the camera unit 107 and processed in the image processor 109 in real time, thereby performing audiovisual communication or displaying a photographed image. [0046]The memory unit 113 stores information (for example, information about a setting state and a menu) related to operation of a program allowing the controller 105 to control the first mobile terminal 100. The memory unit 113 stores the standby order of the third mobile terminal 300 and the fourth mobile terminal 400. The memory unit 113 stores image data received from the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400, and may also store image data mapped to a corresponding terminal in a phone book (not shown) of the first mobile terminal 100. [0047]The audio unit 115 converts an analog audio signal that is input through a microphone MIC to a digital signal, provides the digital signal to the controller 105, converts a digital audio signal that is output from the controller 105 into an analog audio signal, and reproduces the analog audio signal through a speaker SPK. [0048]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0049]Referring to FIGS. 3A and 3B, while the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 100 (S301), the mobile communication network 500 receives a request for audiovisual communication from the third mobile terminal 300 (S303). At step S301, the first mobile terminal 100 is in an audiovisual communication state, the camera unit 107 of the first mobile terminal 100 acquires an image of a user of the first mobile terminal 100, the image processor 109 processes the user image, the display unit 111 displays the user image, and the microphone MIC and the speaker SPK are converted to an operation state. [0050]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S305). [0051]The third mobile terminal 300 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S307). If the third mobile terminal 300 sustains an audiovisual communication standby state, the third mobile terminal 300 sends a standby state sustenance message to the mobile communication network 500 (S309). [0052]Thereafter, the mobile communication network 500 sends information about the third mobile terminal 300 to the first mobile terminal 100 (S311) and forms a communication channel between the first mobile terminal 100 and the third mobile terminal 300. The information about the third mobile terminal 300 may include contact information and image data of the third mobile terminal 300. [0053]The mobile communication network 500 receives a request for audiovisual communication from the fourth mobile terminal 400 (S313), and sends a message regarding the state of the first mobile terminal 100 to the fourth mobile terminal 400 to notify the fourth mobile terminal 400 that the first mobile terminal 100 is performing audiovisual communication (S315). [0054]The fourth mobile terminal 400 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S317). If the fourth mobile terminal 400 sustains an audiovisual communication standby state, the fourth mobile terminal 400 sends a standby state sustenance message to the mobile communication network 500 (S319). [0055]Thereafter, the mobile communication network 500 sends information about the fourth mobile terminal 400 to the first mobile terminal 100 (S321) and forms a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400. The information about the fourth mobile terminal 400 may include contact information and image data of the fourth mobile terminal 400. [0056]The first mobile terminal 100 determines that a communication channel between the first mobile terminal 100 and the third mobile terminal 300 was formed at step S311, and that a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400 is formed at step S321. [0057]Thereafter, the first mobile terminal 100 sets and displays a standby order of the mobile terminals that have requested audiovisual communication by listing the mobile terminals in the order in which their requests were received (S323). In the present exemplary embodiment, because the third mobile terminal 300 requested audiovisual communication earlier than the fourth mobile terminal 400, the third mobile terminal 300 has the highest standby position. [0058]When the first mobile terminal 100 wants to change the displayed standby order (S325), the first mobile terminal 100 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S327). The request to change the standby order is input by selecting image data of the third mobile terminal 300 and the fourth mobile terminal 400 displayed in a change mode or a standby order. [0059]The mobile communication network 500 receives the standby order change request message REQ_MSG and changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 (S329). [0060]The mobile communication network 500 temporarily stores the changed standby order (S331) and sends a standby order change completion message RES_MSG informing the first mobile terminal 100 of the standby order change of the third mobile terminal 300 and the fourth mobile terminal 400 (S333). [0061]The first mobile terminal 100 changes and displays the standby order according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S335). [0062]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S337), the mobile communication network 500 refers to the changed standby order that was temporarily stored at step 331 (S339) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S341). [0063]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S343). [0064]FIG. 4 is a flowchart showing a method of changing the standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0065]Referring to FIG. 4, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200 (S401). The controller 105 displays moving picture data received in real time from the second mobile terminal 200 in the display unit 111. When the mobile terminal 100 receives a request for audiovisual communication from at least one mobile terminal while performing audiovisual communication (S403), the controller 105 determines whether the number of the mobile terminals requesting audiovisual communication is at least two (S405). [0066]If there are at least two mobile terminals requesting audiovisual communication, the controller 105 sets a standby order according to the order in which the requests for audiovisual communication were received and displays the set standby order on the display unit 111 (S407). The controller 105 displays image data received from the mobile terminals requesting audiovisual communication or image data mapped to a phone number of the mobile terminals and stored in a phone book (not shown) on the display unit 111 in the order in which their audiovisual communication requests were received. [0067]The controller 105 determines whether the set standby order has changed (S409). If the set standby order has not change, the process continues at step S419. [0068]If the set standby order has changed, the controller 105 controls the RF unit 101 to send a message REQ_MSG requesting that the standby order of the mobile terminals (here, the third mobile terminal 300 and the fourth mobile terminal 400) be changed through the mobile communication network 500 (S411). [0069]Thereafter, the controller 105 receives a standby order change completion message RES_MSG sent from the mobile communication network 500 through the RF unit 101 (S415). The controller 105 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the received standby order change completion message RES_MSG and displays the changed standby order on the display unit 111 (S417). [0070]The controller 105 determines whether the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S419). If the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 determines whether mobile terminals waiting for audiovisual communication exist, and if mobile terminals waiting for audiovisual communication exist, the first mobile terminal 100 performs audiovisual communication with the mobile terminal having the highest standby position (S421). The first mobile terminal 100 may perform audiovisual communication with the fourth mobile terminal 400, whose standby order position is changed to the highest position at step S417, or with the third mobile terminal 300, which has the highest position in the standby order set at step S407. [0071]If the number of the mobile terminals requesting audiovisual communication is not at least two at step 405, the controller 105 determines whether the first mobile terminal 100 has either ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state (S423). When the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the first mobile terminal 100 performs audiovisual communication with the mobile terminal requesting audiovisual communication (S425). [0072]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0073]Referring to FIGS. 5A and 5B, steps S501 to S523 of FIG. 5A are substantially the same as steps S301 to S323 of FIG. 3A and thus description thereof is omitted. [0074]If the fourth mobile terminal 400 having a standby order position that is lower than that of the third mobile terminal 300 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S525), the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100 (S527), and the mobile communication network 500 sends the standby order change request message REQ_MSG to the third mobile terminal 300 (S529). The standby order change request message REQ_MSG may be sent by the fourth mobile terminal 400 at the same time the fourth mobile terminal 400 sends an audiovisual communication request message to the mobile communication network 500 at step S513. [0075]The first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG (S531), and the third mobile terminal 300 approves the change of the standby order in response to the standby order change request message REQ_MSG (S533). [0076]The first mobile terminal 100 then sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S535), and the third mobile terminal 300 sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S537). [0077]The mobile communication network 500 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change approval message ACC_MSG received from the first mobile terminal 100 at step S535 and from the third mobile terminal 300 at step S537 (S539). [0078]The mobile communication network 500 temporarily stores a changed standby order (S541) and sends a standby order change completion message RES_MSG to the first mobile terminal 100(S543), the third mobile terminal 300 (S545), and the fourth mobile terminal 400(S547). [0079]The first mobile terminal 100 changes and displays the standby order set at the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S549). [0080]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S551), the mobile communication network 500 refers to the changed standby order temporarily stored at step S541 (S553) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S555). [0081]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S557). [0082]Another method of changing a standby order of waiting mobile terminals according to another exemplary embodiment of the present invention (not shown in the Figures) is described as follows. [0083]When the mobile communication network 500 receives a standby order change request message REQ_MSG from the fourth mobile terminal 400, the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100. [0084]Thereafter, if the first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG, the first mobile terminal 100 sends a standby order change approval message ACC_MSG confirming the approval to the mobile communication network 500. When th(String), 相关申请的交叉引用 [0001] 本申请要求于 2007 年 1 月 16 日提交的韩国专利申请号 10-2007-0004601 的优先权和权益,其在此通过引用并入所有目的,就好像在此完全阐述一样。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种在移动终端中提供视听通信服务的方法,更具体地,涉及一种在移动终端中改变等待移动终端的待机顺序的方法。 [0004] 2. 背景讨论 [0005] 随着移动终端技术的发展,已经提供了一种改进的移动终端,其具有使用H.324M协议的相机单元,该H.324M协议包括允许视听通信的H.245协议。 [0006] 在传统的视听通信技术中,当第一移动终端在与第二移动终端进行视听通信时,当第一移动终端接收到来自第三移动终端的视听通信请求时,第一移动终端存储关于第三移动终端的信息。 之后,当第一移动终端结束与第二移动终端的视听通信时,第一移动终端显示第三移动终端的信息,并与第三移动终端进行视听通信。 [0007] 然而,在现有的视听通信技术中,即使第三移动终端紧急请求与第一移动终端进行视听通信,第三移动终端也可能不得不等待,直到第一移动终端结束与第二移动终端的视听通信。 发明内容 [0008] 本发明提供了一种在第一移动终端正在执行视听通信时改变请求视听通信的至少两个移动终端的待机顺序的方法。 [0009] 本发明还提供了一种根据从等待与第一移动终端进行视听通信的至少两个移动终端之一接收到的待机顺序改变请求来改变处于待机状态的移动终端的待机顺序的方法,同时第一移动终端是 进行视听交流。 [0010] 本发明还提供了一种在第一移动终端正在与第二移动终端进行视听通信时显示关于请求视听通信的移动终端的信息的方法。 [0011] 本发明的附加特征将在随后的描述中阐述,并且部分地从描述中变得显而易见,或者可以通过本发明的实践来了解。 [0012] 本发明公开了一种用于在移动通信系统中改变待机顺序的方法,包括当第一移动终端时,根据接收到多个移动终端的视听通信请求的顺序,显示多个移动终端的待机顺序。 当第一移动终端正在与第二移动终端进行视听通信时,终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到来自第一移动终端的待机命令更改请求消息到移动通信网络时 请求更改待机命令,当第一移动终端接收到与待机命令更改请求消息对应的待机命令更改完成消息时,在第一移动终端更改待机命令,并显示更改后的待机命令。 [0013]本发明还公开了一种在移动通信系统中改变待机顺序的方法,包括根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序。 当第一移动终端与第二移动终端进行视听通信时,移动终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到待机时,确定第一移动终端是否批准请求的待机顺序变更 所述多个移动终端中的第三移动终端的订单更改请求消息,如果第一移动终端批准请求的待机订单更改,则更改待机订单,并显示更改后的待机订单。 [0014] 应当理解,前面的一般描述和下面的详细描述都是示例性和解释性的,并且旨在提供对所要求保护的本发明的进一步解释。 附图的简要说明 [0015] 附图被包括以提供对本发明的进一步理解并且被并入并构成本说明书的一部分,它们说明了本发明的实施例,并且与描述一起用于解释本发明的原理。 [0016] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0017] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0018] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0019] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0020] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0021] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0022] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 图示实施例的详细说明 [0023] 下文参照附图更全面地描述本发明,其中示出了本发明的实施例。 然而,本发明可以以许多不同的形式来体现,并且不应被解释为限于这里阐述的实施例。 相反,提供这些实施例是为了使本公开是彻底的,并且将向本领域技术人员充分传达本发明的范围。 在附图中,为了清楚起见,可能夸大了层和区域的尺寸和相对尺寸。 图中相同的附图标记表示相同的元件。 [0024] 应当理解,当一个元件或层被称为“在”另一个元件或层上或“连接到”另一个元件或层时,它可以直接在另一个元件或层上或直接连接到另一个元件或层,或者中间的元件或层可以是 当下。 相反,当一个元素被称为“直接在”或“直接连接到”另一个元素或层时,不存在中间的元素或层。 [0025]根据本发明的示例性实施例举例说明了包括照相机单元并且能够执行视听通信的移动终端。 也就是说,根据本发明示例性实施例的移动终端可以包括信息通信设备或多媒体设备,例如移动通信终端、移动电话、个人数字助理(PDA)、智能电话或笔记本电脑 包括照相机单元并能够进行视听通信的计算机及其应用。 [0026] 根据本发明的示例性实施例举例说明了视听通信。 然而,本示例性实施例不限于视听通信并且可以应用于语音通信。 [0027] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0028] 参考图。 1、系统包括第一移动终端 100 ,第二个移动终端 200 ,第三个移动终端 300 ,第四个移动终端 400 , 和一个移动通信网络 500 . [0029] 第一移动终端可以与第二移动终端进行视听通信 200 并且可以接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 在与第二移动终端进行视听通信的同时 200 . 第一移动终端的配置 100 参照图1描述。 如图2所示,同样的配置也可以应用于第二移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 因此,省略其个别描述。 [0030] 移动通信网络 500 包括执行基站功能的节点、作为节点的子系统的无线接入网络 (RAN)、对应于一个核心网络的移动交换中心 (MSC)/访问者位置寄存器 (VLR) 电路交换域、归属位置寄存器 (HLR) 和网关 MSC。 [0031] MSC管理第一移动终端的呼叫控制和移动性 100 ,VLR和HLR组成用户信息匹配装置,注册和管理属于移动通信网络的移动终端信息 500 包括第一移动终端 100 . [0032] 在下面的描述中,第一移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 属于同一个移动通信网络 500 . 然而第一款移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 可能属于不同的移动通信网络,可能通过不同的网关MSC连接。 然而,假设在移动通信网络中执行在RAN、MSC/VLR、HLR和网关MSC中执行的一系列处理 500 . [0033] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0034] 参考图。 2、移动端 100 包括一个射频 (RF) 单元 101 , 一个输入单元 103 , 一个控制器 105 , 一个相机单元 107 , 图像处理器 109 , 一个显示单元 111 , 一个记忆单元 113 , 和一个音频单元 115 . [0035] 射频单元 101 与第二移动终端进行一般无线通信 200 , 第三个移动终端 300 ,第四个移动终端 400 , 和移动通信网络 500 . 例如,射频单元 101 使用移动通信网络发送和接收语音数据、字符消息和多媒体消息 500 . 射频单元 101 发送从相机单元获取的图像数据 107第一个移动终端 100 到第二个移动终端 200 当第一个移动终端 100 与第二移动终端进行视听通信 200 . 射频单元 101 还接收第二移动终端的摄像单元获取的图像数据 200 第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 请求视听通信。 第二移动终端的图像数据 200 可以是静止和/或运动图像数据,第三移动终端的图像数据 300 和第四个移动终端 400 可以是静止和/或运动图像数据。 进一步地,当第三移动终端 300 和第四个移动终端 400 与第一移动终端进行视听通信 100 ,第三个移动终端的图像数据 300 和第四个移动终端 400 可能会更改为运动图像数据。 [0036] 输入单元 103 可能包括一个通用键盘。 输入单元 103 可以包括触摸屏、触摸板和滚轮。 输入单元 103 接收用户操作信号以控制第一移动终端的操作 100 并向控制器提供操纵信号 105 . [0037] 控制器 105 控制第一移动终端的一般操作 100 . 特别是控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 ,接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 ,并设置视听通信请求的待机顺序。 控制器 105 显示图像数据(即第二移动终端用户的图像数据) 200 )的第二个移动终端 200 在显示单元中进行视听通信 111 . 控制器 105 在显示单元上按照接收到视听通信请求的顺序显示来自请求视听通信的每个移动终端的图像数据 111 第一个终端的 100 . [0038] 更详细地说,第三移动终端的图像数据 300 和第四个移动终端 400 可以是映射到对应的移动终端并存储在第一移动终端的电话簿(未示出)中的图像数据 100 . 图像数据也可以是第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 当请求视听通信时,可能会与视听通信请求一起发送。 控制器 105 可以显示第三移动终端的图像数据 300 和第四个移动终端 400 缩略图类型的静止图像数据。 控制器 105 还可以显示第二移动终端的图像数据 200 ,其中第一款移动终端 100 正在执行视听通信,包括运动图像数据。 [0039] 控制器 105 从第一移动终端发送备用订单更改请求消息REQ_MSG 100 到移动通信网络 500 通过射频单元 101 ,接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面中显示更改后的待机顺序 111 . [0040] 控制器 105 进一步通过移动通信网络从具有最高待机位置的移动终端接收待机顺序更改请求消息REQ_MSG 500 向移动通信网络发送待命订单变更批准消息ACC_MSG 500 通过射频单元 101 . 此后,控制器 105 接收来自移动通信网络的备用订单更改完成消息RES_MSG 500通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面显示待机命令 111 . [0041] 当控制器 105 确定第一移动终端 100 已结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 控制射频单元 101 与待机位置最高的移动终端进行视听通信。 在示例性实施例中,“结束”视听通信是终止形成用于与第二移动终端进行视听通信的通信信道 200 ,并且将视听通信状态“转换”为待机状态是为了在保持与第二移动终端执行视听通信而形成的通信信道的同时,转换为待机状态以便与另一个移动终端执行视听通信。 200 . [0042] 相机单元 107 生成用户的图像数据以通过射频单元发送 101 . 相机单元 107 包括将对象的照片信号转换为模拟信号的图像传感器和将模拟信号转换为数字信号的信号处理器。 也就是相机单元 107 将通过镜头采集的照片信号转换为数字信号,并利用转换后的数字信号生成图像数据。 [0043] 图像处理器 109 处理相机单元中生成的图像数据 107 和通过射频单元接收的图像数据 101 转换成与显示单元对应的格式 111 . [0044] 控制器 105 控制显示单元 111 显示第一移动终端各单元的各种操作状态、操作结果等信息 100 . 显示单元 111 液晶显示器(LCD)、有机发光二极管(OLED)或等离子体显示面板(PDP)等显示装置可以包括显示装置。 [0045] 显示单元 111 显示通过射频单元输入的图像数据 101 和相机单元 107 并在图像处理器中处理 109 实时,从而进行视听通信或显示拍摄的图像。 [0046] 记忆单元 113 存储与允许控制器的程序的操作有关的信息(例如,关于设置状态和菜单的信息) 105 控制第一移动终端 100 . 记忆单元 113 存储第三移动终端的待机指令 300 和第四个移动终端 400 . 记忆单元 113 存储从第二移动终端接收的图像数据 200 , 第三个移动终端 300 ,以及第四个移动终端 400 ,并且还可以将映射到对应终端的图像数据存储在第一移动终端的电话簿(未示出)中 100 . [0047] 音频单元 115 将通过麦克风 MIC 输入的模拟音频信号转换为数字信号,将数字信号提供给控制器 105 , 转换从控制器输出的数字音频信号 105 转换成模拟音频信号,并通过扬声器SPK再现模拟音频信号。 [0048] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0049] 参考图。 参照图3A和3B,同时第一移动终端 100 与第二移动终端进行视听通信 100 (S 301 )、移动通信网络 500 接收来自第三移动终端的视听通信请求 300 (S 303 )。 在步骤 S 301 ,第一款移动终端 100 处于视听通信状态,摄像单元 107 第一个移动终端100 获取第一移动终端用户的图像 100 , 图像处理器 109 处理用户图像,显示单元 111 显示用户图像,并将麦克风MIC和扬声器SPK转换为操作状态。 [0050] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三终端 300 那是第一个移动终端 100 正在进行视听交流(S 305 )。 [0051] 第三个移动终端 300 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 307 )。 如果是第三个移动终端 300 第三移动终端保持视听通信待机状态 300 向移动通信网络发送待机状态维持消息 500 (S 309 )。 [0052] 此后,移动通信网络 500 发送关于第三个移动终端的信息 300 到第一移动终端 100 (S 311 )并形成第一移动终端之间的通信通道 100 第三个移动终端 300 . 第三移动终端信息 300 可以包括第三移动终端的联系方式和图像数据 300 . [0053] 移动通信网络 500 接收来自第四移动终端的视听通信请求 400 (S 313 ),并发送有关第一移动终端状态的消息 100 到第四个移动终端 400 通知第四移动终端 400 那是第一个移动终端 100 正在进行视听交流(S 315 )。 [0054] 第四款移动终端 400 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 317 )。 如果第四个移动终端 400 第四移动终端保持视听通信待机状态 400 向移动通信网络发送待机状态维持消息 500 (S 319 )。 [0055] 此后,移动通信网络 500 发送第四个移动终端的信息 400 到第一移动终端 100 (S 321 )并形成第一移动终端之间的通信通道 100 和第四个移动终端 400 . 第四移动终端信息 400 可以包括第四移动终端的联系信息和图像数据 400 . [0056] 第一个移动终端 100 确定第一移动终端之间的通信信道 100 第三个移动终端 300 在步骤 S 形成 311 ,以及第一移动终端之间的通信信道 100 和第四个移动终端 400 在步骤 S 形成 321 . [0057] 此后,第一移动终端 100 通过按照接收到请求的顺序列出移动终端,设置并显示请求视听通信的移动终端的待机顺序(S 323 )。 在本示例性实施例中,由于第三移动终端 300 在第四台移动终端之前请求视听通信 400 , 第三个移动终端 300 具有最高的待机位置。 [0058] 当第一个移动终端 100 想要更改显示的待机顺序(S 325 ),第一款移动终端 100 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 327 )。 通过选择第三移动终端的图像数据输入更改待机顺序的请求 300和第四个移动终端 400 以更改模式或待机顺序显示。 [0059] 移动通信网络 500 接收待机顺序变更请求消息REQ_MSG,变更第三移动终端的待机顺序 300 和第四个移动终端 400 (S 329 )。 [0060] 移动通信网络 500 临时存储更改后的待机订单(S 331 )并发送备用订单变更完成消息RES_MSG通知第一移动终端 100 第三个移动终端的待机订单变更 300 和第四个移动终端 400 (S 333 )。 [0061] 第一个移动终端 100 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG更改并显示待机命令 500 (S 335 )。 [0062] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 337 )、移动通信网络 500 指在步骤中临时存储的已更改的备用订单 331 (S 339 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 341 )。 [0063] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 343 )。 [0064] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0065] 参考图。 4、控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 (S 401 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . 当移动端 100 在执行视听通信时从至少一个移动终端接收视听通信请求(S 403 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 405 )。 [0066] 如果有至少两个移动终端请求视听通信,则控制器 105 根据接收视听通信请求的顺序设置待机命令,并在显示单元上显示设置的待机命令 111 (S 407 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0067] 控制器 105 判断设置的待机顺序是否改变(S 409 )。 如果设置的待机顺序没有改变,则过程继续到步骤S 419 . [0068] 如果设置的待机顺序发生了变化,控制器 105 控制射频单元 101 发送消息REQ_MSG,请求移动终端(这里是第三个移动终端)的待机命令 300 和第四个移动终端 400 ) 通过移动通信网络进行更改 500 (S 411 )。 [0069] 此后,控制器 105 接收移动通信网络发送的备用订单变更完成消息RES_MSG 500 通过射频单元 101 (S 415 )。 控制器 105更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据接收到的待机指令变更完成消息RES_MSG,在人机界面上显示变更后的待机指令 111 (S 417 )。 [0070] 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 419 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 421 )。 第一个移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单位置在步骤 S 更改为最高位置 417 ,或与第三个移动终端 300 ,它在步骤 S 中设置的待机顺序中的最高位置 407 . [0071] 如果在步骤中请求视听通信的移动终端的数量不是至少两个 405 , 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 423 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 425 )。 [0072] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0073] 参考图。 参见图5A和5B,步骤S 501 到 S 523 图。 图5A与步骤S基本相同 301 到 S 323 图。 与图3A相同,因此省略其描述。 [0074] 如果第四个移动终端 400 待机订单仓位低于第三移动终端 300 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 525 )、移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 (S 527 ) 和移动通信网络 500 向第三移动终端发送备用订单变更请求消息REQ_MSG 300 (S 529 )。 待命订单变更请求消息REQ_MSG可以由第四移动终端发送 400 同时第四个移动终端 400 向移动通信网络发送视听通信请求消息 500 在步骤 S 513 . [0075] 第一个移动终端 100 响应备用订单更改请求消息REQ_MSG(S 531 ),以及第三个移动终端 300 响应备用订单更改请求消息REQ_MSG(S 533 )。 [0076] 第一个移动终端 100 然后向移动通信网络发送备用订单更改批准消息ACC_MSG 500 确认批准备用订单的更改(S 535 ),以及第三个移动终端 300 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500确认批准备用订单的更改(S 537 )。 [0077] 移动通信网络 500 更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据从第一移动终端接收到的待命订单变更批准消息ACC_MSG 100 在步骤 S 535 并从第三个移动终端 300 在步骤 S 537 (S 539 )。 [0078] 移动通信网络 500 临时存储更改的备用订单(S 541 )并向第一移动终端发送备用订单变更完成消息RES_MSG 100 (S 543 ),第三个移动终端 300 (S 545 )、第四个移动终端 400 (S 547 )。 [0079] 第一个移动终端 100 更改并显示在第三个移动终端设置的待机指令 300 和第四个移动终端 400 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG 500 (S 549 )。 [0080] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 551 )、移动通信网络 500 指的是在步骤 S 临时存储的更改后的待机命令 541 (S 553 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 555 )。 [0081] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 557 )。 [0082] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0083] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 . [0084] 此后,如果第一移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG批准待命订单变更 100 向移动通信网络发送确认批准的备用订单更改批准消息ACC_MSG 500 . 当移动通信网络 500 接收待命订单变更批准消息ACC_MSG,移动通信网络 500 相应地更改备用顺序。 移动通信网络 500 暂存变更后的待命订单,并向第一移动终端发送待命订单变更完成消息RES_MSG 100 . [0085] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0086] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 第三个移动终端 300 . 如果第一个移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 100 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . 如果是第三个移动终端 300第三移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . [0087] 当至少一个第一移动终端 100 第三个移动终端 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 , 移动通信网络 500 不改变待命订单,向第一移动终端发送待命订单变更不批准消息N_ACC_MSG 100 , 第三个移动终端 300 ,以及第四个移动终端 400 . [0088] 进一步地,如果第一移动终端 100 批准备用订单和第三个移动终端的更改 300 在接收到来自移动通信网络的待命订单更改不批准消息N_ACC_MSG时,响应待命订单更改请求消息REQ_MSG不批准待命订单的更改 500 通知它待机顺序没有改变,因为第三个移动终端 300 不批准备用订单变更,第一个移动端 100 可以向移动通信网络发送备用订单更改请求消息REQ_MSG 500 从而可以强制改变第三移动终端的待机顺序 300 和第四个移动终端 400 . [0089] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0090] 参考图。 6、控制器 105 控制射频单元 101 让第一个移动终端 100 与第二移动终端进行视听通信 200 (S 601 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . [0091] 当控制器 105 在进行视听通信时从至少一个移动终端接收视听通信请求(S 603 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 605 )。 [0092] 如果有至少两个移动终端请求视听通信,则控制器 105 在视听通信请求命令中设置待机命令并在显示单元中显示该命令 111 (S 607 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0093] 如果控制器 105 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 (S 609 ), 控制器 105 判断移动端是否 100 响应备用订单更改请求消息,批准备用订单的更改(S 611 )。 如果移动端 100 不批准备用订单的变更,流程继续步骤S 619 . [0094] 如果移动端 100 批准备用订单的更改,控制器 105 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500 (S 613 )。 [0095] 控制器 105 判断移动端是否 100 从移动通信网络接收备用订单更改完成消息RES_MSG 500 (S 615 )。 如果移动端 100 未收到来自移动通信网络的备用订单更改完成消息 RES_MSG 500 , 过程在步骤 S 继续 619 . 如果移动端 100接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 , 控制器 105 根据接收到的待机命令更改完成消息RES_MSG更改待机命令,并在人机界面显示更改后的待机命令 111 (S 617 )。 [0096] 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 619 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 621 )。 例如,第一移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单仓位已在步骤 S 变为最高仓位 617 ,或与第三个移动终端 300 在步骤 S 中设置的待机顺序中的最高位置 607 . [0097] 如果在步骤S请求视听通信的移动终端的数量不是至少两个 605 , 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 623 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 625 )。 [0098] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 [0099] 参考图。 7、同时第一移动终端 100 与第二移动终端进行视听通信 200 通过移动通信网络 500 (S 701 )、移动通信网络 500 接收与第一移动终端进行视听通信的请求 100 从第三个移动终端 300 (S 703 )。 [0100] 移动通信网络 500 形成第一移动终端之间的通信通道 100 第三个移动终端 300 并发送关于第三移动终端的信息 300 连同对第一移动终端的视听通信请求 100 (S 705 )。 第三移动终端信息 300 可以是第三移动终端的用户信息(例如电话号码) 300 和/或包括第三移动终端的图像数据的信息 300 . [0101] 第一个移动终端 100 显示从第三移动终端接收到的图像数据 300 (S 707 )。 第一个移动终端 100 可以进一步显示消息(例如弹出窗口)以批准与第三移动终端的视听通信的连接 300 . [0102] 如果第一个移动终端 100 批准与第三个移动终端的视听通信 300 (S 709 )、移动通信网络 500 结束第一移动终端之间的视听通信 100 第二移动终端 200或者转换第一移动终端之间的视听通信状态 100 第二移动终端 200 到待机状态(S 711 )。 此后,移动通信网络 500 实现第一移动终端之间的视听通信 100 第三个移动终端 300 (S 713 )。 [0103] 如上所述,根据本发明,通过在第一移动终端与第二移动终端执行视听通信时改变至少两个请求视听通信的移动终端的待机顺序,可以与选择的请求视听的移动终端执行视听通信 通信,可以为第一移动终端的用户提供更大的便利。 [0104] 此外,通过在第一移动终端与第二移动终端进行视听通信的同时,根据从请求视听通信的至少两个移动终端中的具有较低待机位置的移动终端接收到的用于改变待机命令的请求来改变待机命令, 可以与选择的请求视听通信的移动终端进行视听通信,这可以为具有较低待机位置的待机状态的移动终端的用户提供更大的便利。 [0105] 另外,通过在第一移动终端与第二移动终端进行视听通信的同时显示关于请求视听通信的移动终端的信息,用户可以容易地检查处于待机状态的移动终端。 [0106] 对于本领域的技术人员来说,在不脱离本发明的精神或范围的情况下,可以对本发明进行各种修改和变化是显而易见的。 因此,本发明旨在覆盖本发明的修改和变化,只要它们落入所附权利要求及其等同物的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.723 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.724 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.724 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.725 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.726 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.726 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.727 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.727 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.727 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.739 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.739 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.739 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.740 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.741 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.741 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270639(Integer), KR100790787B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.752 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.752 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.752 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270639(Integer), US20080171563A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.761 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.762 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.762 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270639(Integer), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.773 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.774 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.774 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7801528B2(String), US7801528B2(String), 1284998400(Integer), 270639(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.786 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.786 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.787 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.788 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.789 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.789 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.790 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.791 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.791 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.792 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.792 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.792 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.800 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.801 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.802 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184956(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.803 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.803 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.803 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.813 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.814 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.814 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.816 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.816 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.816 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.817 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.817 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.817 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.819 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.819 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.819 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.820 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.820 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.820 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.827 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.828 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.828 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.829 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.830 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.830 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.831 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.831 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.831 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.841 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.843 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.843 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.845 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.845 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.846 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method for obtaining location information about mobile terminal(String), 移动终端及获取移动终端位置信息的方法(String), US9451580B2(String), The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal. The method for obtaining location information about the mobile terminal comprises: turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal.(String), 本发明实施例提供一种移动终端及获取移动终端位置信息的方法。 获取移动终端位置信息的方法包括:打开移动终端的卫星定位模块,获取移动终端当前位置信息后关闭卫星定位模块,并将当前位置信息作为初始位置信息。 ; 移动终端的传感模块采集移动终端的运动信息,并根据该运动信息计算移动终端的位移变化量; 根据初始位置信息和移动终端的位移变化,获取移动终端的实际位置信息。(String), US14/436195(String), 1374163200(Integer), US9451580B2(String), 1474300800(Integer), 1474300800(Integer), 美国(String), 4(Integer), CN(String), 5(Integer), 27(Integer), CN101464155A | CN102169182A | CN102243315A | CN102901975A | CN1914517A | JP1988108285A | JP1989278879A | JP1990212713A | JP1991237788A | JP1994111196A | JP1995001210A | JP2001059738A | JP2002255664A | JP2006242578A | JP2006279266A | JP2008063815A | JP2008067681A | JP2010038712A | JP2010038798A | JP2010120968A | JP2011149925A | JP2011164089A | JP2011176576A | JP2013029915A | US20100253503A1 | US20130102268A1 | US20160007405A1(String), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.855 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.856 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.856 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.857 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.859 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.859 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\59bc2e0104f340cb872fb749b140af6e.png(String), 184957(Integer), 59bc2e0104f340cb872fb749b140af6e.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.868 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.869 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.869 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.870 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.871 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.871 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for obtaining location information about mobile terminal(String), 移动终端及获取移动终端位置信息的方法(String), US9451580B2(String), The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal. The method for obtaining location information about the mobile terminal comprises: turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal.(String), 本发明实施例提供一种移动终端及获取移动终端位置信息的方法。 获取移动终端位置信息的方法包括:打开移动终端的卫星定位模块,获取移动终端当前位置信息后关闭卫星定位模块,并将当前位置信息作为初始位置信息。 ; 移动终端的传感模块采集移动终端的运动信息,并根据该运动信息计算移动终端的位移变化量; 根据初始位置信息和移动终端的位移变化,获取移动终端的实际位置信息。(String), US14/436195(String), 1374163200(Integer), US9451580B2(String), 1474300800(Integer), 1474300800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 5(Integer), 27(Integer), CN101464155A | CN102169182A | CN102243315A | CN102901975A | CN1914517A | JP1988108285A | JP1989278879A | JP1990212713A | JP1991237788A | JP1994111196A | JP1995001210A | JP2001059738A | JP2002255664A | JP2006242578A | JP2006279266A | JP2008063815A | JP2008067681A | JP2010038712A | JP2010038798A | JP2010120968A | JP2011149925A | JP2011164089A | JP2011176576A | JP2013029915A | US20100253503A1 | US20130102268A1 | US20160007405A1(String), \20230420\59bc2e0104f340cb872fb749b140af6e.png(String), 10(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.878 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.879 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.879 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.880 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.888 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.888 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Parameters: 1835(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.889 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.892 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Preparing: UPDATE os_task SET type=?, uid=?, ctime=?, tid=?, mfields=?, mun=?, endtime=?, status=?, filename=?, filesize=?, downexcel=?, old_name=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.892 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Parameters: 1(Integer), 1(Integer), 1681974668(Integer), 249(Integer), 0(Integer), 99(Integer), 1681974673(Integer), 3(Integer), d56bdfdc923c4bb9b5d178b900fe2b2a.XLSX(String), 6093542(Long), \20230420\d56bdfdc923c4bb9b5d178b900fe2b2a.XLSX(String), 手机-美国.XLSX(String), 1835(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:11:13.899 DEBUG 23536 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:48.854 DEBUG 3548 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:48.871 DEBUG 3548 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:48.890 DEBUG 3548 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.006 DEBUG 3548 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.007 DEBUG 3548 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.008 DEBUG 3548 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.033 DEBUG 3548 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.034 DEBUG 3548 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.035 DEBUG 3548 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.038 DEBUG 3548 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.039 DEBUG 3548 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 249(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.042 DEBUG 3548 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.286 DEBUG 3548 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.287 DEBUG 3548 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.288 DEBUG 3548 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.302 DEBUG 3548 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.302 DEBUG 3548 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:20:49.303 DEBUG 3548 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:09.744 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:09.744 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Parameters: 249(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:09.746 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:09.754 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Preparing: SELECT id,uid AS userId,tenantId,tid AS projectId,addtime AS createTime,remark,type FROM os_distribution_doing WHERE (tid = ? AND uid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:09.755 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Parameters: 249(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:09.756 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:10.397 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert ==> Preparing: INSERT INTO os_task ( type, uid, ctime, tid, mfields, mun, status, filename, filesize, downexcel, old_name ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:10.398 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert ==> Parameters: 1(Integer), 1(Integer), 1681975270(Integer), 249(Integer), 0(Integer), 99(Integer), 0(Integer), c64b1db2b53e45ae99c88b5258f47f34.XLSX(String), 6093542(Long), \20230420\c64b1db2b53e45ae99c88b5258f47f34.XLSX(String), 手机-美国.XLSX(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:10.407 DEBUG 3548 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:10.739 DEBUG 3548 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:10.739 DEBUG 3548 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:10.742 DEBUG 3548 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.785 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.786 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.791 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.799 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.800 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.809 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.811 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.811 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ebb4576c73f94c0ebb9726d03b07e2ce.png(String), 184950(Integer), ebb4576c73f94c0ebb9726d03b07e2ce.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.820 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.828 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.829 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.831 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.842 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.843 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal system, mobile terminal, external device, and input/output method of mobile terminal(String), 移动终端系统、移动终端、外部设备以及移动终端的输入/输出方法(String), US20100093394A1(String), A mobile terminal system including a mobile terminal and an external device is provided. The mobile terminal includes a first external device interface to output screen information to the external device and to receive operation information from the external device. The external device includes a display section to display and output the screen information, a user input section used when a user inputs the operation information on the mobile terminal, and a second external device interface to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 提供了一种移动终端系统,包括移动终端和外部设备。 移动终端包括第一外部设备接口以将屏幕信息输出到外部设备并从外部设备接收操作信息。 外部设备包括用于显示和输出屏幕信息的显示部分、当用户在移动终端上输入操作信息时使用的用户输入部分、以及用于从移动终端接收屏幕信息并输出的第二外部设备接口。 向移动终端发送通过用户输入部分输入的操作信息。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), US12/578279(String), 1255363200(Integer), US20100093394A1(String), 1271260800(Integer), 美国(String), 2(Integer), 2(Integer), JP(String), 3(Integer), 15(Integer), US20010052798A1 | US20030034898A1 | US20040051499A1 | US20060077046A1 | US20060082818A1 | US20060220878A1 | US20070030881A1 | US20080179963A1 | US20080239408A1 | US20090086105A1 | US20110136541A1 | US5847447A | US6781635B1 | US7976394B2 | US8004615B2(String), \20230420\ebb4576c73f94c0ebb9726d03b07e2ce.png(String), 15(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.852 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.862 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.863 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:12.873 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.961 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.962 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 1. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 1.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.963 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 2. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 2.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 0(Integer), 1(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.964 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 3. The mobile terminal system according to claim 2,wherein the coil provided in the first external device interface is a coil for power reception,the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coils.(String), 3.根据权利要求2所述的移动终端系统,其中第一外部设备接口中设置的线圈为受电线圈,第二外部设备接口中设置的线圈为电力传输线圈,以及利用线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.964 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 4. The mobile terminal system according to claim 1 or 2,wherein the mobile terminal is a mobile phone, andthe screen information is video data or still image data received through a mobile phone network.(String), 4.根据权利要求1或2所述的移动终端系统,其中移动终端为手机,屏幕信息是通过手机网络接收到的视频数据或静止图像数据。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.965 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 5. The mobile terminal system according to claim 1 or 3,wherein the first and second external device interfaces perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and also reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 5.根据权利要求1或3所述的移动终端系统,其中第一和第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.966 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 6. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 6.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.967 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 7. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 7.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.967 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 8. The mobile terminal according to claim 7,wherein the coil provided in the first external device interface is a coil for power reception, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the first external device interface and a coil for power transmission provided in the second external device interface.(String), 8.根据权利要求7所述的移动终端,其中第一外部设备接口中设置的线圈为受电线圈,利用第一外部设备接口中设置的线圈与第二外部设备接口中设置的电力传输线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.967 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 9. The mobile terminal according to claim 6 or 8,wherein the first external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 9.根据权利要求6或8所述的移动终端,其中第一外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.968 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 10. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda display section which outputs the screen information received from the mobile terminal.(String), 10.一种在如权利要求1所述的移动终端系统中运行的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.968 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 11. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; anda display section which outputs the screen information received from the mobile terminal.(String), 11.一种运行在如权利要求1所述的移动终端系统中的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.968 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 12. The external device according to claim 11,wherein the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the second external device interface and a coil for power reception provided in the first external device interface.(String), 12.根据权利要求11所述的外部设备,其中第二外部设备接口中设置的线圈为电力传输线圈,以及利用设置在第二外部设备接口中的线圈与设置在第一外部设备接口中的用于受电的线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.969 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 13. The external device according to claim 10 or 12,wherein the second external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 13.根据权利要求10或12所述的外部设备,其中第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.969 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 14. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 14.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:21.969 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 15. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 15.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 1(Integer), 14(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.113 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.114 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.121 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.122 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.122 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111521(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.129 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.130 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.133 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184950(Integer), BACKGROUND OF THE INVENTION [0001]1. Field of the Invention [0002]The present invention relates to a mobile terminal system including a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal, a mobile terminal, an external device, and an input/output method of the mobile terminal. In particular, the present invention relates to a mobile terminal system which outputs image data and sound data received in a mobile terminal to the outside through an external device and which allows the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0003]2. Description of the Related Art [0004]Mobile phones have succeeded the carphones pioneered as a mobile communications system, and have rapidly spread since the 1990s as the terminals become small, light, and inexpensive and the service charges become low. Moreover, with the spread of computers and the development of broadband network techniques including the Internet, E-mail and web search/access can be performed on mobile phones and various applications, such as music or video reproduction and games, can be executed. [0005]However, although the range of application of mobile phones is diversified, there are many restrictions in input and output since a portable size is necessary for mobile phones. For example, the screen size is diagonally about 5 to 10 cm. In this case, high-resolution display causes problems in visibility, for example, characters with the same font size become very small, even though the resolution is increasing due to the development of flat panel manufacturing technology in recent years. [0006]Furthermore, an input section provided in the mobile phone generally has only a numeric keypad of 0 to 9, keys by which up and down and left and right input operations are possible, and some other keys. Compared with a keyboard of a personal computer provided with 60 to 100 keys, the number of keys of the mobile phone is small and the input operation is also difficult. [0007]In recent years, the mobile phone with tens of keys similar to the QWERTY type keyboard has also appeared. However, each of the keys is small due to the portability restriction on the device size. For this reason, the input operation is still difficult. [0008]In order to cope with such a problem, a method of connecting a mobile phone to an external device with a relatively large screen or an input device which is easy to perform an input operation may be considered. [0009]For example, a display processing system using a mobile terminal is proposed. In the display processing system, an image displayed on a liquid crystal screen of a mobile phone can be displayed on a television screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2001-352373). [0010]In addition, a screen display device which has an entry for connecting a mobile phone is proposed. The screen display device displays image data received in the mobile phone on a large screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2002-116843). [0011]In addition, a mobile phone with a separate monitor is proposed. The mobile phone displays data displayed on a monitor built in the mobile phone or downloaded display data on the separate monitor (for example, refer to Japanese Unexamined Patent Application Publication No. 2003-78597). [0012]However, in order to transmit or receive data by connecting a mobile phone to an external device, a plurality of signal transmission lines for input/output of a video signal, input/output of a sound signal, input/output of a user operation signal, and the like is necessary (refer to FIG. 10). That is, for the connection between the mobile phone and the external device, a plurality of cables is used for video, sound, and user operation or a plug cable having a terminal with many poles is used. In the former case where a plurality of cables is used, the connection and disconnection operations of the cables are troublesome for the user. Moreover, in the latter method of using the plug cable, there is a problem that it becomes difficult to secure the place for disposing the plug in the main body of the small mobile phone as the number of poles increases. In addition, problems also occur such as the device becoming expensive due to the cost of components, such as connectors, and difficulty in obtaining a contact point between the connectors with sufficient strength. [0013]In addition, when the classification of input or output signal changes with the model of the mobile phone, the number of poles of the plug also changes. In this case, the connectors for the external device are not compatible among different models, which is inconvenient. SUMMARY OF THE INVENTION [0014]In view of the above, it is desirable to provide a mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0015]In addition, it is desirable to provide a mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0016]According to a first embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0017]The “system” referred to herein means a logical group of a plurality of devices (or functional modules for realizing specific functions), and it does not matter whether the devices or the functional modules exist in a single housing. [0018]According to a second embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0019]Here, according to a third embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the power supply, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0020]In addition, according to a fourth embodiment of the present invention, the mobile terminal may be a mobile phone, and the screen information may be video data or still image data received through a mobile phone network. [0021]In addition, according to a fifth embodiment of the present invention, the first and second external device interfaces may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0022]In addition, according to a sixth embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0023]In addition, according to a seventh embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0024]Here, according to an eighth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0025]In addition, according to a ninth embodiment of the present invention, the first external device interface of the mobile terminal may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0026]In addition, according to a tenth embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a display section which outputs the screen information received from the mobile terminal. [0027]In addition, according to an eleventh embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; and a display section which outputs the screen information received from the mobile terminal. [0028]Here, according to a twelfth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0029]In addition, according to a thirteenth embodiment of the present invention, the second external device interface of the external device may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0030]In addition, according to a fourteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0031]In addition, according to a fifteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0032]According to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0033]Moreover, according to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0034]According to the first to third, sixth to eighth, tenth to twelfth, fourteenth, and fifteenth embodiments of the present invention, the received data can be displayed on the large screen and the mobile terminal can be operated by the input from an easy-to-use keyboard simply by placing the mobile terminal, in which the size of the display device or input device is not sufficient, on the external device. [0035]In addition, according to the fourth embodiment of the present invention, video data or still image data downloaded from the Internet to the mobile phone can be displayed using the large screen of the external device. [0036]In addition, according to the fifth, ninth, and thirteenth embodiments of the present invention, transmission using a small number of contact points is performed between the mobile phone and the external device. This is advantageous in that the connection interface is simplified, the component cost for the connection section is reduced, the device is small-sized, and deterioration of the contact point is prevented. These effects can be further improved by applying wireless connection, such as electric field transmission, to the connection interface. [0037]Moreover, according to the embodiments of the present invention, since it is sufficient to provide a simple connection interface with an external device, restrictions in the design can be reduced. [0038]Additional purposes, characteristics, and advantages of the present invention will be apparent from the detailed description made in the following embodiment of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS [0039]FIG. 1 is a diagram schematically illustrating the configuration of a mobile terminal system according to an embodiment of the present invention; [0040]FIG. 2 is a diagram illustrating an example of the configuration of transmitting the parallel data serially; [0041]FIG. 3 is a characteristic curve illustrating the frequency spectrum of a signal on a power line; [0042]FIG. 4A is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0043]FIG. 4B is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0044]FIG. 5 is a diagram illustrating a write sequence example of a bus in a mobile phone and a bus in an external device when performing a write operation from the mobile phone to an LCD of the external device; [0045]FIG. 6 is a diagram illustrating a read sequence example of a bus in the mobile phone and a bus in the external device when performing an operation of reading the input information on a keyboard of the external device from the mobile phone; [0046]FIG. 7 is a diagram illustrating an interrupt sequence example of the bus in the mobile phone and the bus in the external device when an interrupt occurs on the keyboard of the external device; [0047]FIG. 8 is a diagram illustrating a format example of a transmission frame between the mobile phone and the external device; [0048]FIG. 9 is an illustration of an application image of the mobile terminal system shown in FIG. 1; and [0049]FIG. 10 is a diagram illustrating an example of the configuration of a past mobile terminal system. DESCRIPTION OF THE PREFERRED EMBODIMENTS [0050]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. [0051]FIG. 1 is a schematic diagram illustrating the configuration of a mobile terminal system according to an embodiment of the present invention. The system shown in FIG. 1 includes a mobile phone, which receives image data and sound data, and an external device, which outputs the image data and the sound data to the outside or which is used when a user operates the mobile phone. [0052]A mobile phone 100 includes a processor 101, various input/output devices 104 to 106, and an external device interface 107 for interfacing with an external device 120. Moreover, although the mobile phone 100 includes circuit modules for radio communications and the like, they are not shown because they are not directly related with the gist of the present invention. [0053]The processor 101 is connected to the various input/output devices 104 to 106 by a bus signal line group 110, a chip select signal 111, and an interrupt signal 112. [0054]The bus signal line group 110 includes signal lines, such as address, data, and enable. In addition to the various input/output devices 104 to 106, the bus signal line group 110 is also connected to the external device interface 107. [0055]The chip select signal 111 is a signal which is used when the processor 101 selects a circuit chip of one of the various input/output devices 104 to 106 through a bus interface 102. In addition, the interrupt signal 112 is a signal, which is used when the various input/output devices 104 to 106 notify the processor 101 of the occurrence of an event, and is input to an interrupt controller 103. The chip select signal 111 and the interrupt signal 112 are prepared in a quantity equal to the number of input/output devices and are also connected to the external device interface 107. [0056]First, an operation on the side of the mobile phone 100 will be described. [0057]When outputting data to the screen of an LCD 104, the processor 101 outputs image data to the LCD 104 using the bus interface 102. When outputting the data to the LCD 104, the bus interface 102 enables the chip select signal 111 connected to the LCD 104 so that the LCD 104 receives the image data from the processor 101 and displays the data on the screen. For example, video data or still image data downloaded through the mobile phone network from a web site on the Internet can be displayed on the screen of the LCD 104. [0058]In addition, also when outputting data to a speaker 105 or other output devices (not shown), the processor 101 similarly enables only the chip select signal 111 connected to the corresponding output device so that the output device receives the data from the processor 101 and reproduces and outputs the data. For example, sound data, such as music, downloaded through the mobile phone network from a web site on the Internet can be reproduced in the speaker 105. [0059]On the other hand, when there is a user input operation on a keyboard 106, the keyboard 106 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. The processor 101 which has received the interrupt receives the data, which has been input on the keyboard 106, through the bus 110. In this case, the bus interface 102 enables the chip select signal 111 connected to the keyboard 106 so that the keyboard 106 can output the data to the bus 110 and the processor 101 can receive the data. [0060]In addition, the same is true for the cases where an input operation has been performed by other input devices (not shown). That is, the input device generates an interrupt in response to the user input operation and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. On the other hand, the bus interface 102 enables the chip select signal 111 connected to the corresponding input device so that the input device outputs the data to the bus 110 and the processor 101 receives the data. [0061]Having described the data input/output operations between the input/output devices 104 to 106 and the processor 101, it may be understood that read and write operations of common registers for each input/output device are similarly realized by the above-described bus access method. [0062]In the system shown in FIG. 1, the mobile phone 100 is connected to the external device 120 through the external device interfaces 107 and 121. The external device 120 includes various enhanced input/output devices as user interfaces, such as an LCD 122 with a relatively large screen, a multi-channel speaker 123, and a large-sized keyboard 124 with tens of keys, such as alphanumeric keys. In addition, although not shown, the external device 120 may have a charge function for the mobile phone 100. [0063]In the past, a method of using a plug cable was commonly adopted for connection between a mobile phone and an external device. In this case, however, there are some problems as already stated. On the other hand, in the present embodiment, the external device interfaces 107 and 121 perform parallel-to-serial conversion of the address information and data information transmitted through the bus and then transmit this information under the conditions in which it is superimposed on a power interface 113. For this reason, neither the number of cables nor the number of poles of the plug is increased. [0064]Next, a method of transmitting and receiving data under the conditions in which the external device 120 is connected to the mobile phone 100 will be described. [0065]First, the case where the screen information of the mobile phone 100 is output to the external device 120 will be described. [0066]The bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the external device interface 107 can receive from the processor 101 the data to be displayed on the screen. In this case, it is assumed that the chip select signal 111 includes the classification indicating that transmitted data is screen information. [0067]The external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. [0068]The external device interface 121 of the external device 120 includes a bus interface function (not shown) and an interrupt controller function (not shown). In addition, the external device interface 121 converts the serial data, which has been received from the mobile phone 100 through the power interface 113, into parallel data to thereby restore it as the same data as in the mobile phone 100 which includes the classification of the chip select signal 111, the address information, and the data information. Then, the external device interface 121 transmits the data to the LCD 122 through a bus 133 by enabling a chip select signal 131 connected to the LCD 122. Thus, the LCD 122 displays and reproduces the same screen information as in the mobile phone 100. For example, video data or still image data downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be displayed on the screen of the LCD 122 in the external device 120. [0069]Moreover, the same is true for the case where the other output information on the side of the mobile phone 100 is output to the external device 120. [0070]For example, when the sound information is output to the external device 120, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the data for sound output is transmitted from the processor 101 to the external device interface 107. In this case, the chip select signal 111 includes the classification indicating that the transmitted data is sound information. Then, the external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. On the other hand, the external device interface 121 of the external device 120 reproduces the same data as in the mobile phone 100 by performing serial-to-parallel conversion of the classification of the received chip select signal 111, the address information, and the data information and then transmits the data to the speaker 123 through the bus 133 by enabling the chip select signal 131 connected to the speaker 123. Thus, the speaker 123 reproduces and outputs the same sound information as in the mobile phone 100. For example, sound data, such as music, downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be reproduced in the speaker 123 of the external device 120. [0071]Next, a processing operation when a user input operation is performed using an input device of the external device 120 will be described. [0072]For example, when there is a user input operation on the keyboard 124, the keyboard 124 generates an interrupt and notifies the external device interface 121 through an interrupt signal 132. [0073]Upon receiving the interrupt signal, the external device interface 121 receives the data input on the keyboard 124 through the bus 133 by enabling the chip select signal 131 connected to the keyboard 124. Then, the external device interface 121 performs parallel-to-serial conversion of the classification of the chip select signal 131 and the address information and data information transmitted through the bus 132 and transmits such data to the power interface 113. [0074]Then, the external device interface 107 of the mobile phone 100 converts the serial data, which has been received from the external device 120 through the power interface 113, into parallel data to thereby restore it as the same data as in the external device 120 which includes the classification of the chip select signal 131, the address information, and the data information. In addition, the external device interface 107 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. [0075]When the processor 101 receives the interrupt, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107. In response to this, the external device interface 107 outputs the data to the bus 110. Thus, the processor 101 can receive the data input by the keyboard 124 of the external device 120. [0076]Moreover, the same is true for the case where other input information on the side of the external device 120 (String), 发明背景 [0001] 一、发明领域 [0002] 本发明涉及一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,移动终端,外部设备,以及输入/输出 移动端的方法。 具体地,本发明涉及一种移动终端系统,其通过外部设备向外部输出在移动终端中接收到的图像数据和声音数据,并且允许通过外部设备在移动终端上执行用户操作, 移动终端、外部设备和移动终端的输入/输出方法。 [0003] 二、相关技术说明 [0004] 移动电话作为移动通信系统的先驱,继承了车载电话的先河,随着终端的小型化、轻量化、低价化和服务费的降低,从1990年代开始迅速普及。 此外,随着计算机的普及和包括因特网在内的宽带网络技术的发展,可以在手机上进行电子邮件和网络搜索/访问,并且可以执行各种应用,例如音乐或视频播放和游戏。 [0005] 然而,虽然手机的应用范围多种多样,但由于手机需要便携的尺寸,因此在输入和输出方面存在很多限制。 例如,屏幕尺寸对角线约5至10厘米。 在这种情况下,尽管近年来由于平板制造技术的发展分辨率越来越高,但高分辨率显示会导致可见性问题,例如,相同字体大小的字符变得非常小。 [0006] 另外,手机中设置的输入部分一般只有0到9的数字键盘,以及可以进行上下左右输入操作的按键,以及其他一些按键。 与个人电脑的键盘有60到100个按键相比,手机的按键数量少,输入操作也比较困难。 [0007] 近几年,也出现了类似QWERTY键盘的几十个按键的手机。 然而,由于设备大小的便携性限制,每个密钥都很小。 为此,输入操作还是有难度的。 [0008] 为了解决这样的问题,可以考虑将移动电话连接到具有相对大屏幕的外部设备或易于执行输入操作的输入设备的方法。 [0009] 例如,提出了使用移动终端的显示处理系统。 在显示处理系统中,显示在移动电话的液晶屏幕上的图像可以显示在电视屏幕上(例如,参考日本未审查专利申请公开No.2001-352373)。 [0010] 此外,还提出了一种屏幕显示装置,其具有用于连接手机的入口。 屏幕显示设备在大屏幕上显示在移动电话中接收到的图像数据(例如,参考日本未审查专利申请公开No.2002-116843)。 [0011] 此外,还提出了一种带有独立显示器的移动电话。 移动电话显示在移动电话内置的监视器上显示的数据或在单独的监视器上下载的显示数据(例如,参考日本未审查专利申请公开No.2003-78597)。 [0012]然而,为了通过将移动电话连接到外部设备来发送或接收数据,用于视频信号的输入/输出、声音信号的输入/输出、用户操作信号的输入/输出的多条信号传输线 ,等等是必要的(参考图10)。 也就是说,对于移动电话和外部设备之间的连接,使用多根电缆用于视频、声音和用户操作,或者使用具有多极端子的插头电缆。 在使用多根电缆的前一种情况下,电缆的连接和断开操作对用户来说很麻烦。 此外,在后一种使用插头电缆的方法中,随着极数的增加,存在难以确保小型移动电话主体中用于布置插头的位置的问题。 此外,还存在由于连接器等部件的成本而导致装置变得昂贵、连接器之间的接触点难以获得足够强度的问题。 [0013] 另外,随着手机型号不同,输入或输出信号的分类发生变化时,插头的极数也会发生变化。 在这种情况下,外部设备的连接器在不同型号之间不兼容,这很不方便。 发明内容 [0014] 鉴于上述情况,期望提供一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如手机,以及连接到移动终端并能够输出图像数据的外部设备。 以及移动终端中接收到的声音数据通过外部设备发送到外部并允许用户通过外部设备在移动终端上执行操作、移动终端、外部设备以及移动设备的输入/输出方法 终端。 [0015] 此外,期望提供一种移动终端系统,其中移动终端和外部设备通过具有简单配置的接口相互连接,使得在移动终端中接收的图像数据和声音数据可以输出到 外部设备通过外部设备可以在移动终端上进行用户操作、移动终端、外部设备和移动终端的输入/输出方法。 [0016] 根据本发明第一实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作。 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0017] 这里所说的“系统”是指多个设备(或实现特定功能的功能模块)的逻辑集合,与设备或功能模块是否存在于一个外壳内无关。 [0018]根据本发明的第二实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0019] 这里,根据本发明的第三实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 即,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括电力电缆上传输的电流信号,还包括用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0020] 另外,根据本发明的第四实施例,移动终端可以是手机,屏幕信息可以是通过手机网络接收的视频数据或静止图像数据。 [0021] 此外,根据本发明的第五实施例,第一和第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据 通过对接收到的数据进行串并转换。 [0022] 此外,根据本发明的第六实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0023] 此外,根据本发明的第七实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0024]这里,根据本发明的第八实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0025] 此外,根据本发明的第九实施例,移动终端的第一外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0026] 此外,根据本发明的第十实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用。 终端; 第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电; 显示部分输出从移动终端接收的屏幕信息。 [0027] 此外,根据本发明的第十一实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用该用户输入部分。 终端; 第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息; 显示部分输出从移动终端接收的屏幕信息。 [0028] 这里,根据本发明的第十二实施例,第一外部设备接口中设置的线圈可以是用于电力接收的线圈,第二外部设备接口中设置的线圈可以是电力传输线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0029] 此外,根据本发明的第十三实施例,外部设备的第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在电力信号上,并且可以再现叠加在电源信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0030]另外,根据本发明的第十四实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0031] 另外,根据本发明第十五实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0032] 根据本发明的实施例,可以提供出色的移动终端系统,其包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,并且能够 将在移动终端中接收到的图像数据和声音数据通过外部设备输出到外部,并允许用户通过外部设备在移动终端上进行操作,移动终端,外部设备,输入/输出 移动端的方法。 [0033] 此外,根据本发明的实施例,可以提供出色的移动终端系统,其中移动终端和外部设备通过具有简单配置的接口彼此连接,使得接收到的图像数据和声音数据 移动终端中的信息可以通过外部设备输出到外部,用户可以通过外部设备对移动终端进行操作,移动终端,外部设备,移动终端的输入/输出方法。 [0034] 根据本发明的第一至第三、第六至第八、第十至第十二、第十四和第十五实施例,可以在大屏幕上显示接收到的数据,并且可以通过来自易于操作的输入来操作移动终端。 - 只需将显示设备或输入设备的尺寸不够大的移动终端放在外部设备上即可使用键盘。 [0035] 此外,根据本发明的第四实施例,可以使用外部设备的大屏幕来显示从互联网下载到移动电话的视频数据或静止图像数据。 [0036]此外,根据本发明的第五、第九和第十三实施例,在移动电话和外部设备之间执行使用少量接触点的传输。 这是有利的,因为简化了连接接口,降低了连接部分的组件成本,设备尺寸小,并且防止了接触点的劣化。 通过对连接接口应用无线连接,例如电场传输,可以进一步改善这些效果。 [0037] 此外,根据本发明的实施例,由于提供简单的与外部设备的连接接口就足够了,因此可以减少设计上的限制。 [0038] 本发明的其他目的、特征和优点将通过以下结合附图对本发明的实施例的详细描述而显而易见。 附图的简要说明 [0039] 图1是表示本发明的一个实施方式的移动终端系统的概略结构的图。 [0040] 图2是表示串行发送并行数据的结构例的图。 [0041] 图3是电力线上信号的频谱特性曲线。 [0042] 图4A是表示串行地发送并行数据的串行器的另一例的图。 [0043] 图4B是表示串行地发送并行数据的串行器的另一例的图。 [0044] 图5是表示从移动电话向外部设备的LCD进行写入时的移动电话内的总线和外部设备的总线的写入顺序例的图。 [0045] 图6是表示进行从移动电话读取外部设备的键盘的输入信息的操作时的移动电话内的总线和外部设备的总线的读取顺序例的图。 [0046] 图7是表示在外部设备的键盘上发生中断时的移动电话内的总线和外部设备内的总线的中断时序例的图。 [0047] 图8是表示移动电话与外部设备之间的传输帧的格式例的图。 [0048] 图9为图1所示的移动终端系统的应用程序图像示意图。 和 [0049] 图10是表示以往的便携终端系统的结构例的图。 优选实施例的描述 [0050] 在下文中,将参考附图描述本发明的实施例。 [0051] 图1是图示根据本发明实施例的移动终端系统的配置的示意图。 图1所示的系统包括接收图像数据和声音数据的移动电话,以及将图像数据和声音数据输出到外部或者当用户操作移动电话时使用的外部设备。 [0052] 一部手机 100 包括一个处理器 101 , 各种输入输出设备 104 到 106 , 和一个外部设备接口 107 用于连接外部设备 120 . 而且,虽然手机 100 包括无线电通信等电路模块,由于与本发明的主旨无直接关系,故未图示。 [0053] 处理器 101 连接到各种输入/输出设备 104 到 106 通过总线信号线组 110 , 片选信号 111 , 和一个中断信号 112 . [0054] 总线信号线组 110 包括信号线,例如地址、数据和启用。 除了各种输入/输出设备 104 到 106 ,总线信号线组 110 也连接到外部设备接口 107 . [0055] 片选信号 111 是处理器使用的信号 101 选择各种输入/输出设备之一的电路芯片 104 到 106 通过总线接口 102 . 此外,中断信号 112 是信号,在各种输入/输出设备时使用 104 到 106 通知处理者 101 一个事件的发生,并被输入到一个中断控制器 103 . 片选信号 111 和中断信号 112 准备了与输入/输出设备数量相等的数量,并连接到外部设备接口 107 . [0056] 一、手机端的一个操作 100 将被描述。 [0057] 将数据输出到 LCD 屏幕时 104 , 处理器 101 输出图像数据到LCD 104 使用总线接口 102 . 向 LCD 输出数据时 104 , 总线接口 102 启用片选信号 111 连接到液晶显示器 104 这样液晶显示器 104 从处理器接收图像数据 101 并将数据显示在屏幕上。 例如,通过手机网络从 Internet 上的网站下载的视频数据或静止图像数据可以显示在 LCD 的屏幕上 104 . [0058] 此外,当向扬声器输出数据时 105 或其他输出设备(未显示),处理器 101 同样只启用片选信号 111 连接到相应的输出设备,以便输出设备接收来自处理器的数据 101 并再现和输出数据。 例如,可以在扬声器中再现通过手机网络从互联网网站下载的音乐等声音数据 105 . [0059] 另一方面,当用户在键盘上进行输入操作时 106 , 键盘 106 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . 处理器 101 接收到中断 接收到键盘输入的数据 106 , 通过公交车 110 . 在这种情况下,总线接口 102 启用片选信号 111 连接到键盘 106 这样键盘 106 可以将数据输出到总线 110 和处理器 101 可以接收数据。 [0060] 另外,对于由其他输入设备(未图示)进行了输入操作的情况也是同样的。 即输入设备响应用户输入操作产生中断,通知中断控制器 103 处理器的 101 通过中断信号 112 . 另一方面,总线接口 102 启用片选信号 111 连接到相应的输入设备,使输入设备输出数据到总线 110 和处理器 101 接收数据。 [0061] 描述了输入/输出设备之间的数据输入/输出操作 104 到 106 和处理器 101 可以理解,对于每个输入/输出设备的公共寄存器的读写操作是通过上述总线访问方法类似地实现的。 [0062] 在图1所示的系统中,手机 100 连接到外部设备 120 通过外部设备接口 107 和 121 . 外部设备 120 包括各种增强型输入/输出设备作为用户界面,例如 LCD 122 屏幕比较大,多声道喇叭 123 , 和一个大尺寸的键盘 124 带有数十个键,例如字母数字键。 此外,虽然没有显示,外部设备 120 可能有手机充电功能 100 . [0063]以往,手机与外部设备的连接通常采用插头线的方式。 然而,在这种情况下,存在已经提到的一些问题。 另一方面,在本实施例中,外部设备接口 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些信息 113 . 为此,既没有增加电缆的数量,也没有增加插头的极数。 [0064] 接下来介绍一种在外部设备不可用的情况下发送和接收数据的方法 120 已连接手机 100 将被描述。 [0065] 一、手机屏幕信息的情况 100 输出到外部设备 120 将被描述。 [0066] 总线接口 102 启用片选信号 111 连接到外部设备接口 107 使外部设备接口 107 可以从处理器接收 101 要显示在屏幕上的数据。 在这种情况下,假定片选信号 111 包括指示传输的数据是屏幕信息的分类。 [0067] 外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . [0068] 外部设备接口 121 外部设备的 120 包括总线接口功能(未显示)和中断控制器功能(未显示)。 此外,外部设备接口 121 转换从手机接收到的串口数据 100 通过电源接口 113 , 转化为并行数据从而恢复为与手机中相同的数据 100 其中包括片选信号的分类 111 、地址信息和数据信息。 然后,外部设备接口 121 将数据传输到 LCD 122 通过公共汽车 133 通过使能片选信号 131 连接到液晶显示器 122 . 因此,液晶 122 显示和再现与手机相同的屏幕信息 100 . 例如,从互联网网站下载到手机的视频数据或静止图像数据 100 通过手机网络可以显示在液晶屏上 122 在外部设备中 120 . [0069] 而且,其他手机端输出信息的情况也是如此 100 输出到外部设备 120 . [0070] 例如,当声音信息输出到外部设备时 120 , 总线接口 102 启用片选信号 111 连接到外部设备接口 107 以便声音输出的数据从处理器传输 101 到外部设备接口 107 . 在这种情况下,片选信号 111 包括指示传输的数据是声音信息的分类。 然后,外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . 另一方面,外部设备接口 121 外部设备的 120 再现与手机中相同的数据 100 通过对接收到的片选信号进行分类串并转换 111 ,地址信息,数据信息,然后将数据传输给扬声器 123 通过公共汽车 133 通过使能片选信号 131 连接到扬声器 123 . 因此,演讲者123 再现和输出与手机相同的声音信息 100 . 例如,从互联网上的网站下载到手机中的音乐等声音数据 100 通过手机网络可以在音箱中重现 123 外部设备的 120 . [0071] 接下来,使用外部设备的输入设备进行用户输入操作时的处理操作 120 将被描述。 [0072] 例如,当键盘上有用户输入操作时 124 , 键盘 124 产生中断并通知外部设备接口 121 通过中断信号 132 . [0073] 接收到中断信号后,外部设备接口 121 接收键盘输入的数据 124 通过公共汽车 133 通过使能片选信号 131 连接到键盘 124 . 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0074] 然后,外部设备接口 107 手机的 100 转换从外部设备接收到的串行数据 120 通过电源接口 113 , 转换为并行数据,从而将其恢复为与外部设备中相同的数据 120 其中包括片选信号的分类 131 、地址信息和数据信息。 此外,外部设备接口 107 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . [0075] 当处理器 101 接收到中断,总线接口 102 启用片选信号 111 连接到外部设备接口 107 . 响应于此,外部设备接口 107 将数据输出到总线 110 . 因此,处理器 101 可以接收键盘输入的数据 124 外部设备的 120 . [0076] 此外,对于外部设备侧的其他输入信息的情况也是如此 120 被输入到手机 100 . [0077] 即输入设备响应用户输入操作等产生中断通知给外部设备接口 121 . 接收到中断信号后,外部设备接口 121 通过总线接收数据 133 通过使能片选信号 131 连接到相应的输入设备。 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0078] 外部设备接口 107 手机的 100 对片选信号的分类进行串并转换 131 、地址信息、从外部设备接收到的数据信息 120 ,从而恢复与外部设备中相同的数据 120 . 此外,外部设备接口 107 通知中断控制器 103 处理器的 101 通过中断信号 112 有来自外部设备的输入 120 . 然后,总线接口 102 启用片选信号 111 连接到外部设备 120 这样处理器 101 从外部设备接收输入数据 120 . [0079] 描述了输入/输出设备之间的数据输入/输出操作 122 到 124 外部设备的 120 和处理器 101 手机的 100,可以理解为外部设备的每个输入/输出设备的公共寄存器的读写操作 120 通过上述总线访问方法类似地实现。 [0080] 在本实施例中,手机与手机之间的接口 100 和外部设备 120 通过采用外部设备接口的方法简化了 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些数据 113 . [0081] 图2例示了串行传输并行数据的配置示例。 图2所示的传输系统包括串行器 200 和反序列化器 210 它们通过电源线相互连接 220 作为电源接口 113 . 假设这对序列化器 200 和反序列化器 210 双向设置于外部设备接口 107 手机的 100 和外部设备接口 121 外部设备的 120 . [0082] 序列化器 200 包括一个 PS(并行到串行)转换器 201 将并行信号转换为串行信号,PLL 部分 202 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 203 通过向串行信号添加标头等来执行编码,时序控制器 204 它控制传输时间,和一个司机 205 . [0083] 另一方面,反序列化器 210 包括一个接收器 212 , 解码器 213 它通过从报头、时钟恢复 (CR) 部分检测数据的头部来解码编码数据 214 它使用参考时钟 (Ref. CLK)、SP(串行到并行)转换器从接收到的数据中提取时钟 215 它将串行信号转换为原始并行信号,以及一个时序控制器 216 它控制接收时间。 [0084] 因此,输入到串行器的并行数据 P-DATA 和用于串行数据的时钟 P-CLK 200 转换为串行信号,通过解串器恢复为原来的并行数据P-DATA和时钟P-CLK 210 . [0085] 在图 2 所示的示例中,电源线 220 用作传输线,在叠加在电源线上的条件下传输串行信号 220 从外部设备 120 到手机 100 . 叠加部分 206 将传输信号叠加在用于供电的功率信号上。 基本上,叠加部分 206 将传输信号与电源线耦合 220 通过一个电容器并将电源信号与电源线耦合 220 通过扼流圈。 [0086] 到达解串器的传输信号 210 通过电源线 220 通过分离部分与电源信号分离 212 . 类似于叠加部分 206 , 在分离部分 211 ,在通过电容器切断直流分量之后提取传输信号,并且通过扼流圈从传输信号中切断功率信号。 [0087] 此外,可以提及曼彻斯特编码作为编码器中应用的编码方法的示例 203 和解码器 213. 在曼彻斯特编码中,当传输一个二进制值“0”时,它在位段中间由高电平变为低电平。 另一方面,当传输二进制值“1”时,它在比特部分的中间从低电平相反地变为高电平。 换言之,在曼彻斯特编码中,通过两次扩展频带来去除传输信号的DC分量。 由于曼彻斯特码的优点在于不包括直流分量并且容易提取时钟,因此认为曼彻斯特码适合与具有直流分量的电力叠加在同一传输线上。 电力线上信号的频谱 220 如图3所示。在图3中,附图标记 301 表示曼彻斯特码的频谱。 已知曼彻斯特码可以在不包括直流分量的情况下与功率信号一起传输。 [0088] 串行传输并行数据的串行器和解串行器的另一配置示例在图4A和4B中示出。 [0089] 序列化器 400 包括一个PS转换器 401 将并行信号转换为串行信号,PLL 部分 402 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 403 通过向串行信号添加标头等来执行编码,时序控制器 404 它控制传输时间,和一个司机 405 . 编码器编码的串行信号 403 被传输到一个线圈 406 通过司机 405 然后传输到解串器 410 通过线圈之间的电磁耦合。 [0090] 另一方面,反序列化器 410 包括一个线圈 411 它与线圈进行电磁耦合 406 在序列化器的一侧 400 , 一个差分接收器 412 , 放大器 413 放大由电磁耦合降低的信号电平,解码器 414 它从报头中检测数据的头部并对编码数据进行解码,时钟恢复(CR)部分 415 它使用参考时钟 (Ref. CLK)、SP 转换器从接收到的数据中提取时钟 416 它将串行信号转换为原始并行信号,以及一个时序控制器 417 它控制接收时间。 [0091] 当采用图2或图4A、4B所示的串行传输作为电源接口时 113 连接外部设备 120 和手机 100 相互之间,可以将数据叠加在电源信号上,并且可以在从外部设备进行充电的同时进行数据传输 120 到手机 100 . 此外,根据图4A和4B所示的串行传输方法,可以使用线圈在电场中传输数据。 结果,由于可以通过无线连接发送和接收数据,因此连接外部设备的电缆 120 用手机 100 变得不必要。 [0092] 接下来是手机之间进行数据收发时的总线访问操作 100 和外部设备 120 将被描述。 下面根据美国英特尔公司的80总线架构来描述总线访问操作。 然而,本发明不限于此。 [0093] 图 5 说明了总线的写入序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 从手机执行写入操作时 100 到液晶显示器 122 外部设备的 120 . [0094] 在手机里 100 ,处理器断言(启用)具有 LCD 分类的片选信号 101 . 随后,总线上的写信号 110 由处理器断言 101 然后将写数据传输到总线 110 . [0095] 通过这样的操作,数据被写入外部设备接口 107 手机的100 . 然后,外部设备接口 107 将请求写入的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0096] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 随后,外部设备接口 121 断言连接到 LCD 的片选信号 122 , 断言总线上的写信号 133 ,然后将写数据传输到总线 110 . 因此,将数据写入LCD 122 被执行。 结果,液晶 122 可以显示和再现与手机相同的屏幕信息 100 . [0097] 此外,可以理解为在每个移动电话中执行相同的总线写入序列 100 和外部设备 120 同样在手机输出其他信息的情况下 100 写入外部设备 120 . [0098] 图 6 说明了总线的读取序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 执行读取键盘输入信息的操作时 124 外部设备的 120 从手机 100 . [0099] 在手机里 100 ,具有键盘分类的片选信号被断言,然后总线上的读取信号 110 由处理器断言 101 . 然后,外部设备接口 107 手机的 100 将请求读取的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0100] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 然后,外部设备接口 121 断言连接到键盘的片选信号 124 然后在总线上断言读取信号 133 . 然后,键盘 124 将输入数据传输到总线 110 . [0101] 从键盘读取数据后 124 , 外接设备接口 121 将数据转换成串口数据串口传输给手机 100 通过电源接口 113 . [0102] 外部设备接口 107 手机的 100 提取键盘上的输入数据 124 通过将接收到的串行数据转换成并行数据,然后传输到总线 110 在读信号被断言的期间。 因此,处理器 101 可以从键盘读取输入数据 124 外部设备的 120 . [0103] 此外,可以理解,在每个移动电话中执行相同的总线读取序列 100 和外部设备 120 同样在外部设备的其他输入信息的情况下 120 在手机中读取 100 . [0104] 图 7 说明了总线的中断序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 当键盘发生中断时 124 外部设备的 120 . [0105] 键盘 124 断言中断信号 132 当中断发生时。 外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113. 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 断言中断信号 112 . [0106] 处理器收到中断信号后 101 根据上述过程执行总线访问(读或写)。 例如,总线接口 102 启用片选信号 111 连接到外部设备接口 107 , 这样处理器 101 读取键盘上的输入数据 124 从外部设备 120 通过公共汽车 110 . [0107] 随后,当键盘 124 否定中断信号 132 通过释放中断,外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113 . [0108] 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 否定中断信号 112 . 结果在手机端也释放了键盘中断 100 . [0109] 图 8 说明了移动电话之间的传输帧的格式示例 100 和外部设备 120 . [0110] 图8所示的传输帧在报头部分包括数据类型、设备类型和数据长度字段。 [0111] 数据类型字段长度为2位,用于区分传输帧对应的读、写、中断发生和中断释放。 例如0×00表示读,0×01表示写,0×02表示中断。 [0112] 设备类型字段,长度为2比特,用于区分传输帧是对哪个设备的读或写请求,或者是区分传输帧是来自哪个设备的中断发生或释放请求。 例如0×00表示LCD,0×01表示键盘,0×02表示扬声器。 [0113] 数据长度字段具有1个字节的长度,并且传输帧的数据(有效载荷)部分的长度例如以比特数来描述。 [0114] 此外,位 0 到最后一位连接在传输帧的数据部分。 [0115] 此外,图8所示的传输帧格式只是一个例子,本发明不限于此。 可以使用根据应用本发明的系统适当定义的任何传输帧格式。 此外,传输帧中可以包括使用校验和的错误检测和错误纠正等功能。 [0116] 图9是图1所示的移动终端系统的应用程序图像的图示。 [0117] 外部设备 901 包括液晶显示器 901 带有相对较大的屏幕和键盘 903 使用 QWERTY 排列中的所有键。 通过放置手机 904 在连接部分 902 , 手机屏幕 904 可以显示在LCD上 901 和手机 904 可以通过键盘上的用户输入进行操作 903 . [0118] 一个联络点 905 与手机连接 904 在连接部分提供 902 , 这样手机 904 可以充电,可以通过触点进行数据传输 905 . [0119] 然而,当如图 4A 和 4B 所示执行使用线圈的电场传输时,接触点 905 外部设备之间 900 和手机 904不存在,通过线圈进行通信 906 在外部设备中提供 900 . [0120] 本申请包含与 2008 年 10 月 15 日向日本专利局提交的日本优先权专利申请 JP 2008-266856 中公开的主题相关的主题,其全部内容通过引用并入本文。 [0121] 本领域技术人员应当理解,可以根据设计要求和其他因素进行各种修改、组合、子组合和变更,只要它们在所附权利要求或其等同物的范围内。(String), 111521(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.142 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.151 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.151 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.153 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.156 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.156 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.157 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.160 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.161 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.163 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.164 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.164 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), CN101729662A(String), 1046961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.166 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.166 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.166 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), CN101729662B(String), 1046962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.167 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.168 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.168 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), JP2010098484A(String), 1046963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.169 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.170 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.170 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), JP4893722B2(String), 1046964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.171 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.172 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.172 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), US20100093394A1(String), 1046965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.173 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.174 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.174 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100093394A1(String), US20100093394A1(String), 1271260800(Integer), 270633(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.176 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.190 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.190 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), HIDAKA, ISAO(String), 索尼公司(String), HIDAKA ISAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.192 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.202 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.202 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.203 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.213 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.214 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.214 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 184950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.225 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.228 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.231 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HIDAKA, ISAO(String), HIDAKA ISAO(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75899(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.233 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.234 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.235 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184950(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.244 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.244 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.245 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75899(Integer), 2(Integer), 184950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.253 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.255 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.255 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.257 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.258 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.258 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.260 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.262 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.262 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75899(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.264 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.271 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.271 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.272 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.293 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.293 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.295 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.302 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.303 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.310 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.311 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.311 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.320 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.325 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.326 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10075579B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.329 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.330 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.330 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.342 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.343 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.343 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\a45fe2f081c9415c99663120a78e5046.png(String), 184951(Integer), a45fe2f081c9415c99663120a78e5046.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.355 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.356 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.356 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.358 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.359 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.359 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, user interface method in the mobile terminal, and cover of the mobile terminal(String), 移动终端、移动终端中的用户界面方法及移动终端的外壳(String), US10075579B2(String), A mobile terminal, a method in the mobile terminal, and a cover of the mobile terminal are provided for processing input. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined, and a second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area while the cover is closed over the touch screen is detected and the first input as a first control command is processed.(String), 本 发明提供一种移动终端、移动终端中的方法及移动终端的外壳,用于处理输入。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域,并定义了与封面的非窗口区域对应的移动终端的触摸屏的第二区域。 检测当盖板在触摸屏上关闭时第二区域中的第一输入,并且处理作为第一控制命令的第一输入。(String), US14/603760(String), 1421942400(Integer), US10075579B2(String), 1536595200(Integer), 1536595200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 7(Integer), 40(Integer), JP2006277739A | JP2008097966A | KR101285669B1 | KR1020080108839A | KR1020110025939A | KR1020130004769A | KR200464076Y1 | KR2020120005719U | US20040248621A1 | US20080062348A1 | US20100238119A1 | US20110065474A1 | US20110260980A1 | US20120098760A1 | US20120250241A1 | US20130083465A1 | US20130109435A1 | US20130181935A1 | US20130300679A1 | US20140073377A1 | US20140128131A1 | US20140185206A1 | US20140198070A1 | US20140204511A1 | US20140274214A1 | US20140292589A1 | US20140357330A1 | US20150105128A1 | US20150138021A1 | US20150155903A1 | US20150229754A1 | US20150280770A1 | US20160154512A1 | US20160277053A1 | US9307129B2 | WO2001028190A1(String), \20230420\a45fe2f081c9415c99663120a78e5046.png(String), 31(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.367 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.367 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.367 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:22.379 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 31 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.886 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.887 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 1. A method of processing input in a mobile terminal, the method comprising:identifying a first area of a touch screen of the mobile terminal corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 1.一种在移动终端中处理输入的方法,该方法包括:通过接收来自外壳的信息识别移动终端的触摸屏的第一区域对应于外壳的窗口区域和触摸屏的第二区域对应于外壳的非窗口区域;检测触摸屏上方的移动终端盖板是否合上;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.888 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 2. The method of claim 1, further comprising determining a type of the cover, wherein the first area and the second area are defined according to the type of the cover.(String), 2.如权利要求1所述的方法,还包括判断封面的类型,其中第一区域与第二区域是根据封面的类型定义的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.888 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 3. The method of claim 1, further comprising determining whether an event has occurred, while the cover is closed over the touch screen of the mobile terminal, wherein the first area and the second area are defined according to occurrence of the event.(String), 3.如权利要求1所述的方法,还包括在移动终端的触摸屏上盖合上时判断事件是否发生,其中第一区域和第二区域是根据事件的发生定义的。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 4. The method of claim 1, further comprising:detecting a third input in the first area while the cover is closed over the touch screen;processing the third input as a third control command; anddetecting a fourth input in the second area while the cover is closed over the touch screen; and processing the fourth input as a fourth control command,wherein the third input and the fourth input are of a same type, which is different from that of the first input and the second input.(String), 4.如权利要求1所述的方法,还包括:在触摸屏上盖合上时检测第一区域中的第三输入;将第三输入处理为第三控制命令;和在触摸屏上盖合上时检测第二区域中的第四输入;并将第四输入处理为第四控制命令,其中,第三输入与第四输入为同一类型,与第一输入与第二输入不同。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 5. The method of claim 1, further comprising receiving cover type information from the cover.(String), 5.如权利要求1所述的方法,还包括从封面接收封面类型信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 6. The method of claim 5, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 6.如权利要求5所述的方法,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 7. The method of claim 1, further comprising activating a part of the touch screen according to the first and second areas, while the cover is closed over the touch screen.(String), 7.如权利要求1所述的方法,还包括根据第一区域和第二区域激活触摸屏的一部分,同时关闭触摸屏上的盖体。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 8. The method of claim 1, further comprising, when the cover is closed over the touch screen, activating a screen of the first area and a touch sensing area of the second area.(String), 8.如权利要求1所述的方法,还包括,当盖合于触控屏幕上时,激活第一区域的屏幕和第二区域的触控感应区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.890 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 9. The method of claim 1, wherein processing the first input comprises displaying information in the first area according to the first input detected in the second area.(String), 9.如权利要求1所述的方法,其中处理第一输入包括根据在第二区域中检测到的第一输入在第一区域中显示信息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.890 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 10. The method of claim 9, wherein the information comprises at least one of music play information, a camera preview, busy call information, and information about at least one application.(String), 10.如权利要求9所述的方法,其中该信息包括音乐播放信息、相机预览、忙音信息和至少一个应用程序的信息中的至少一种。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.890 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 11. A mobile terminal comprising:a touch screen; anda processor configured to:identify a first area of the touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detect whether the cover of the mobile terminal is closed over the touch screen,detect an input in the touch screen while the cover is closed over the touch screen, determine whether the input is a first input in the first area or a second input in the second area, process a first control command according to the first input in the first area, and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 11.移动终端包括:触摸屏;和处理器配置为:通过接收来自外壳的信息,识别对应于移动终端外壳的窗口区域的触摸屏的第一区域和对应于外壳的非窗口区域的触摸屏的第二区域;检测触摸屏上方移动终端的盖板是否合上,在触摸屏上盖合上时检测触摸屏中的输入,判断输入是第一区域中的第一输入还是第二区域中的第二输入,根据第一区域中的第一输入处理第一控制命令第一区域,以及根据第二区域中的第二输入的第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.890 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 12. The mobile terminal of claim 11, wherein the non-window area of the cover includes a keypad configured to apply a key input, and the processor is further configured to detect the key input applied through the keypad of the non-window area of the cover in the second area.(String), 12.如权利要求11所述的移动终端,其中所述盖板的非窗口区域包括键盘,用于进行键输入,所述处理器还用于在所述第二区域中检测通过所述盖板的非窗口区域的键板施加的键输入。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 13. The mobile terminal of claim 12, wherein the processor is further configured to receive a text input as a result of detecting the key input through the keypad and control execution of a function according to the text input.(String), 13.如权利要求12所述的移动终端,其中处理器还被配置为接收作为检测通过小键盘的键输入的结果的文本输入,并根据文本输入控制功能的执行。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 14. The mobile terminal of claim 11, further comprising a receiver configured to receive cover type information from the cover,wherein the processor is further configured to check the cover type information about the cover and define the first and second areas according to the cover type information.(String), 14.如权利要求11所述的移动终端,还包括接收器,配置为从封面接收封面类型信息,其中,处理器还用于检查封面的封面类型信息,并根据封面类型信息定义第一区域和第二区域。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 15. The mobile terminal of claim 14, further comprising a memory configured to store the cover type information.(String), 15.如权利要求14所述的移动终端,还包括存储器,用于存储封面类型信息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 16. The mobile terminal of claim 14, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 16.如权利要求14所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 17. The mobile terminal of claim 11, wherein the window area of the cover is transparent or semi-transparent and the non-window area of the cover is opaque.(String), 17.如权利要求11所述的移动终端,其中盖板开窗区为透明或半透明,盖板非开窗区为不透明。(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.892 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 18. The mobile terminal of claim 11, wherein the processor is further configured to set different touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen.(String), 18.如权利要求11所述的移动终端,其中处理器还被配置为在触摸屏的第一区域和第二区域设置不同的触摸输入灵敏度以感测触摸输入。(String), 1(Integer), 17(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.892 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 19. The mobile terminal of claim 11, wherein the processor is further configured to set touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen according to whether the cover is closed over the touch screen.(String), 19.如权利要求11所述的移动终端,其中处理器还被配置为根据触摸屏上的盖子是否关闭来设置用于感测触摸屏的第一区域和第二区域中的触摸输入的触摸输入灵敏度。(String), 1(Integer), 18(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.892 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 20. The mobile terminal of claim 11, further comprising a battery packet disposed inside a rear surface of the mobile terminal,wherein the touch screen is formed on a front surface of the mobile terminal, andwherein the cover comprises:a battery cover unit provided on the rear surface of the mobile terminal, for protecting the battery packet; anda front cover unit connected to the battery cover unit, for covering the touch screen of the mobile terminal.(String), 20.如权利要求11所述的移动终端,还包括电池包设置在移动终端的后表面内,其中,触摸屏形成在移动终端的前表面上,并且其中,覆盖物包括:电池盖单元,设置在移动终端的背面,用于保护电池包;和前盖单元,与电池盖单元连接,用于盖住移动终端的触摸屏。(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.892 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 21. The mobile terminal of claim 11, wherein the cover comprises:a front cover unit configured to cover a front surface of the mobile terminal;a rear cover unit configured to cover a rear surface of the mobile terminal; anda connection unit configured to connect the front cover unit to the rear cover unit.(String), 21.如权利要求11所述的移动终端,其中封面包括:前盖单元,被配置为覆盖移动终端的前表面;后盖单元,被配置为覆盖移动终端的后表面;和连接单元被配置为将前盖单元连接到后盖单元。(String), 1(Integer), 20(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.893 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 22. The mobile terminal of claim 11, further comprising a magnetic force sensor configured to sense a change of an external magnetic force,wherein the processor is further configured to control the touch screen according to the change of the external magnetic force sensed by the magnetic force sensor.(String), 22.如权利要求11所述的移动终端,还包括磁力传感器,配置为感测外部磁力的变化,其中,处理器还用于根据磁力传感器感应到的外部磁力的变化控制触摸屏。(String), 1(Integer), 21(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.893 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 23. A mobile terminal comprising:a cover including a transparent or semi-transparent window area and an opaque non-window area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, for covering a touch screen of the mobile terminal;the touch screen including a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of a front cover unit of the cover; anda processor configured to:identify the first area of the touch screen corresponding to the window area of the cover of the mobile terminal and the second area of the touch screen corresponding to the non-window area of the cover by receiving information from the cover;control the touch screen to display a visual object on a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, wherein one of the visual object and another visual object are not displayed on a second area of the touch screen corresponding to a non-window area of the cover while the cover is closed over the touch screen,activate touch sensing for the second area of the touch screen while the cover is closed over the touch screen,control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the cover is closed over the touch screen.(String), 23.移动终端包括:覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域,覆盖物包括被配置为向移动终端应用多个有区别的键输入的键盘,用于覆盖移动终端的触摸屏;触摸屏包括对应于盖体的窗口区域的第一区域和对应于盖体的非窗口区域的第二区域,其中键盘包括雕刻或印刷在盖体的外表面上的多个区别键。封面的封面单元;和处理器配置为:通过接收外壳的信息识别移动终端外壳窗口区域对应的触摸屏第一区域和外壳非窗口区域对应的触摸屏第二区域;控制触摸屏在触摸屏的与移动终端的外壳的窗口区域对应的第一区域上显示视觉对象,其中在触摸的第二区域上不显示视觉对象和另一个视觉对象中的一个盖板关闭时对应于盖板非窗口区域的屏幕覆盖在触摸屏上,当盖子在触摸屏上关闭时,激活触摸屏第二区域的触摸感应,根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时盖子在触摸屏上方关闭。(String), 0(Integer), 22(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.893 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 24. The mobile terminal of claim 23, wherein the processor is further configured to receive cover type information from the cover.(String), 24.如权利要求23所述的移动终端,其中处理器还被配置为从封面接收封面类型信息。(String), 1(Integer), 23(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.893 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 25. The mobile terminal of claim 24, wherein the processor is further configured to check the cover type information and determine the first area and the second area of the touch screen according to the cover type information.(String), 25.如权利要求24所述的移动终端,其中处理器还用于检查覆盖物类型信息,并根据覆盖物类型信息确定触摸屏的第一区域和第二区域。(String), 1(Integer), 24(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 26. The mobile terminal of claim 24, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 26.如权利要求24所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 25(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 27. A cover for a mobile terminal, comprising:a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal; anda rear cover unit configured to cover a rear surface of the mobile terminal,wherein the front cover unit includes a transparent or semi-transparent window area and an opaque non-window area,a cover type information provider configured to provide cover type information to the mobile terminal, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover, andwherein the non-window area of the front cover unit includes an input area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of the front cover unit.(String), 27.一种移动终端的外壳,包括:前盖单元被配置为覆盖形成在移动终端的前表面上的触摸屏;和后盖单元,被配置为覆盖移动终端的后表面,其中,前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域,封面类型信息提供器,被配置为向移动终端提供封面类型信息,其中,封面类型信息包括关于封面的窗口区域的大小和位置中的至少一项的信息以及关于大小和位置中的至少一项的信息。盖子的非窗口区域的位置,以及其中,前盖单元的非窗口区域包括输入区域,输入区域包括配置为向移动终端应用多个不同的键输入的小键盘,并且当前盖单元覆盖移动终端的触摸屏时,通过非窗口区域的输入区域向触摸屏施加输入,其中键盘包括雕刻到或印刷在前盖单元的外表面上的多个有区别的键。(String), 0(Integer), 26(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 28. The cover of claim 27, wherein the front cover unit comprises a magnetic force applier configured to generate a magnetic force.(String), 28.权利要求27的覆盖物,其中前盖单元包括配置成产生磁力的磁力施加器。(String), 1(Integer), 27(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 29. The cover of claim 27, wherein the input applied through the non-window area is applied in a part of the non-window area visually distinguished from another part of the non-window area.(String), 29.权利要求27的覆盖物,其中通过非窗口区域施加的输入被施加在非窗口区域的一部分中,在视觉上与非窗口区域的另一部分区别开来。(String), 1(Integer), 28(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 30. The cover of claim 27, wherein at least a part of the non-window area is formed of at least one of conductive silicon, an anti-static electric material, and silver nylon.(String), 30.权利要求27的覆盖物,其中非窗口区域的至少一部分由导电硅、抗静电材料和银尼龙中的至少一种形成。(String), 1(Integer), 29(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:25.895 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 31. An article of manufacture for processing input in a mobile terminal, comprising a non-transitory machine readable medium containing one or more programs which when executed implement the steps of:identify a first area of a touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;activating touch sensing for the second area of the touch screen while the cover is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are of a same gesture type, andwherein the first control command and the second control command are different control command.(String), 31.一种用于处理移动终端输入的制品,包括包含一个或多个程序的非暂时性机器可读介质,这些程序在执行时执行以下步骤:通过接收来自外壳的信息识别移动终端的外壳的窗口区域对应的触摸屏的第一区域和外壳的非窗口区域对应的触摸屏的第二区域;检测触摸屏上方的移动终端盖板是否合上;当盖子关闭在触摸屏上方时,激活触摸屏的第二区域的触摸感应;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 30(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.165 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.166 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.173 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.174 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.174 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111522(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.182 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.182 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.185 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184951(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to a Korean patent application filed in the Korean Intellectual Property Office on Feb. 11, 2014 and assigned Serial No. 10-2014-0015272, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal, and more particularly, to a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal. [0004]2. Description of the Related Art [0005]Mobile terminals such as, for example, smartphones, Personal Computers (PCs), tablets, and the like, provide various useful functions to users through many applications. [0006]Such mobile terminals are evolving to enable users to use various types of information through the various functions. [0007]In general, a cover is configured so as to cover an entire display formed on the front surface of a mobile terminal. Since the screen of the display is covered with the cover, a user may not use the display screen. SUMMARY OF THE INVENTION [0008]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal, which even though the mobile terminal is covered with the cover, enable a user to view at least a part of a display screen of the mobile terminal. [0009]Another aspect of the present invention is to provide a mobile terminal, a UI method in the mobile terminal, and a cover of the mobile terminal, which provide a window area to show a part of a display screen of the mobile terminal when the cover covers the display screen of the mobile terminal and which enable a user to identify an area of the display screen corresponding to the window area of the cover so that display on the area corresponding to the window area of the cover may be controlled in various manners. [0010]In accordance with an aspect of the present invention, a method is provided for processing input in a mobile terminal. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined. A second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area is detected while the cover is closed over the touch screen. The first input is processed as a first control command. [0011]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a touch screen and a processor. The processor is configured to define a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, to define a second area of the touch screen corresponding to a non-window area of the cover, to detect a first input in the second area while the cover is closed over the touch screen, and to process the first input as a first control command. [0012]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a cover including a transparent or semi-transparent window area and an opaque non-window area, for covering a touch screen of the mobile terminal. The mobile terminal also includes a touch screen that includes a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover. The mobile terminal further includes a processor configured to control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the touch screen is covered with the cover. [0013]In accordance with another aspect of the present invention, a cover for a mobile terminal is provided that includes a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal. The cover also includes a rear cover unit configured to cover a rear surface of the mobile terminal. The front cover unit includes a transparent or semi-transparent window area and an opaque non-window area. The non-window area of the front cover unit includes an input area. and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area. [0014]In accordance with another aspect of the present invention, an article of manufacture is provided for processing input in a mobile terminal. The article of manufacture includes a machine readable medium containing one or more programs which when executed implement the steps of: defining a first area of the touch screen corresponding to a window area of a cover of the mobile terminal; defining a second area of the touch screen corresponding to a non-window area of the cover; detecting a first input in the second area while the cover is closed over the touch screen; and processing the first input as a first control command. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0016]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention; [0017]FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention; [0018]FIG. 2B is a diagram illustrating a rear surface of a cover of a mobile terminal, according to an embodiment of the present invention; [0019]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention; [0020]FIGS. 4A and 4B are diagrams illustrating configurations of a front cover unit, according to embodiments of the present invention; [0021]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention; [0022]FIG. 6 is a diagram illustrating an operation for determining whether a mobile terminal is covered with a cover, according to an embodiment of the present invention; [0023]FIG. 7 is a block diagram of a mobile terminal, according to an embodiment of the present invention; [0024]FIG. 8 is a flowchart illustrating a UI operation using a first area and a second area defined on a touch screen, respectively corresponding to a window area and a cover input area of a cover, in a mobile terminal, according to an embodiment of the present invention; [0025]FIGS. 9, 10, 11, and 12 are diagrams illustrating touch screen areas defined for various types of covers, according to embodiments of the present invention; [0026]FIG. 13 is a diagram illustrating touch inputs, according to an embodiment of the present invention; [0027]FIG. 14 is a flowchart illustrating an operation for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0028]FIGS. 15A and 15B are diagrams illustrating screens for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0029]FIG. 16 is a flowchart illustrating an operation for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0030]FIG. 17 is a diagram illustrating a screen for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0031]FIG. 18 is a flowchart illustrating an operation for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0032]FIGS. 19A, 19B, 20A, and 20B are diagrams illustrating screens for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0033]FIG. 21 is a flowchart illustrating an operation for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0034]FIGS. 22A, 22B, 23A, and 23B are diagrams illustrating screens for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0035]FIGS. 24A, 24B, and 24C are diagrams illustrating a cover having a keypad formed on it according to another embodiment of the present invention; [0036]FIG. 25 is a diagram illustrating a keypad formed on a front cover unit, according to an embodiment of the present invention; [0037]FIGS. 26A, 26B, and 26C are diagrams illustrating keys formed on a front cover unit, according to an embodiment of the present invention; [0038]FIGS. 27A and 27B are diagrams illustrating a full screen and a mini screen respectively, according to an embodiment of the present invention; [0039]FIGS. 28A, 28B, 28C, 28D, and 28E are diagrams illustrating mini screens of 1st to 5th types, respectively, according to an embodiment of the present invention; [0040]FIGS. 29A, 29B, 29C, 29D, and 29E are diagrams illustrating mini screens of 6th to 10th types, according to an embodiment of the present invention; [0041]FIGS. 30A and 30B are diagrams illustrating mini screens of 11th and 12th types, according to an embodiment of the present invention; [0042]FIG. 31 is a diagram illustrating a mini screen of a 13th type, according to an embodiment of the present invention; [0043]FIGS. 32A and 32B are diagrams illustrating a method for controlling display of a mini screen, according to an embodiment of the present invention; [0044]FIGS. 33A, 33B, 33C, 34A, 34B, 34C, 34D, and 34E are diagrams illustrating operations triggered by text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0045]FIGS. 35A, 35B, 35C, 35D, and 35E are diagrams illustrating operations triggered by different types of text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0046]FIGS. 36A, 36B, 36C, 36D, and 36E are diagrams illustrating an operation for performing a call function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0047]FIGS. 37A, 37B, and 37C are diagrams illustrating an operation for performing a message function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0048]FIGS. 38A, 38B, 38C, 38D, 38E, 38F, and 38G are diagrams illustrating operations for performing various application functions, upon selection of applications on a mini screen while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0049]FIGS. 39A and 39B are diagrams illustrating an application requiring a text input, according to an embodiment of the present invention; and [0050]FIGS. 40A and 40B are diagrams illustrating a cover open request message displayed while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0051]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0052]The terms and words used in the following description are not limited to the meanings provided in a standard dictionary, but, are merely used to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the disclosure. [0053]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0054]Use of the term “substantially” means that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those of skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide. [0055]A mobile terminal according to various embodiments of the present invention may be embodied as an electronic device equipped with a display, such as, for example, a touch screen that can be covered with a cover. For example, the mobile terminal may be any of a video phone, a mobile phone, a smartphone, an International Mobile Telecommunication 2000 (IMT 2000) terminal, a Wideband Code Division Multiple Access (WCDMA) terminal, a Universal Mobile Telecommunication System (UMTS) terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a Digital Multimedia Broadcasting (DMB) terminal, an e-book reader, a laptop Personal Computer (PC), a tablet PC, a digital camera, and the like. [0056]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention. FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention. FIG. 2B is a diagram illustrating the rear surface of a cover of a mobile terminal, according to an embodiment of the present invention. [0057]Referring to FIGS. 1A, 1B, 2A, and 2B, a mobile terminal 100 may be engaged with a cover 200. A display device that displays screens for multiple functions, for example, a touch screen 140 is provided on a front surface of the mobile terminal 100. A bezel 102 is formed around at least a part of the periphery of the touch screen 140 on the front surface of the mobile terminal 100. A home button 105, a speaker, a camera, a sensor, and the like, may be formed in the bezel 102. A battery 170 is mounted on a rear surface of the mobile terminal 100 to supply power to the mobile terminal 100. The battery 170 may be detachably formed on the rear surface of the mobile terminal 100, or may be built in the mobile terminal 100 so that a user may not remove the battery 170 from the mobile terminal 100. A rear cover unit 220 is provided on the rear surface of the mobile terminal 100. Connection ports 180 are provided on the rear surface of the mobile terminal 100, inside the rear cover unit 220, for electrical connection. The rear cover unit 220 is able to be engaged with the rear surface of the mobile terminal 100, covering the battery 170. The cover 200 is configured to cover at least a part of the front surface of the mobile terminal 100. When the cover 200 covers the front surface of the mobile terminal 100, a front cover unit 210 covers at least a part of the touch screen 140. Further, when the cover 200 covers the front surface of the mobile terminal 100, the front cover unit 210 covers at least a part of the bezel 102. When the front cover unit 210 covers at least a part of the touch screen 140, the remaining part of the touch screen 140 is exposed outwardly through a window area 201a formed in the front cover unit 210. The mobile terminal 100 may control display of content such as, for example, a clock, text, a number, a caller number, a user environment setting, or the like, in the part of the touch screen 140 exposed through the window area 201a of the front cover unit 210. [0058]The front cover unit 210 of the cover 200 may be flipped open or closed. When the front cover unit 210 of the cover 200 is opened, the entire area of the touch screen 140 of the mobile terminal 100 is exposed outward, as illustrated in FIG. 1A. If the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 of the mobile terminal 100 is covered with the front cover unit 210, as illustrated in FIG. 1B. Referring to FIG. 1B, when the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 corresponding to the window area 201a is exposed outward, while the remaining part of the touch screen 140 is covered. [0059]Further, when the front cover unit 210 of the cover 200 is closed, a part (for example, a speaker) formed in the bezel 102 of the mobile terminal 100 is exposed outwardly through an opening 201b formed in the front cover unit 210. While only one opening 201b is shown in FIG. 1B, a plurality of openings may be formed in the front cover unit 210 so that even though the front cover unit 210 is closed, a plurality of parts (for example, a speaker, a camera, and the like) formed in the bezel 102 may be exposed outwardly through the plurality of openings. [0060]Referring to FIGS. 2A and 2B, the cover 200 includes the front cover unit 210 and the rear cover unit 220. The cover 200 further includes a connection unit 203 interposed between the front cover unit 210 and the rear cover unit 220, for connecting the front cover unit 210 to the rear cover unit 220. The connection unit 203 may cover a part of a side surface of the mobile terminal 100. [0061]The front cover unit 210 covers the front surface of the mobile terminal 100 and includes the window area, or screen projector, 201a to expose a part of the touch screen 140. The window area 201a may be formed of a transparent or semi-transparent material or may be formed into an opening in the front cover unit 210 so that when the cover 200 covers the front surface of the mobile terminal 100, a user may view information displayed on the touch screen 140 through the window area 201a. Accordingly, the user may view information displayed on the touch screen 140 inside the front cover unit 210 through the window area 201a from outside of the front cover unit 210. Therefore, even though the front cover unit 210 is closed, the user may view short information displayed on the touch screen 140 through the window area 201a and may enter a user command through the front cover unit 210 to execute a function related to the displayed information. The rear cover unit 220 is formed as a battery cover 220a in FIG. 2B, by way of example. Referring to FIG. 2B, the rear cover unit 220 covers the rear surface of the mobile terminal 100. The rear cover unit 220 may be mounted fixedly or detachably on the rear surface of the mobile terminal 100. The front cover unit 210 may be connected to a side surface of the rear cover unit 220. The connection unit 203 may be formed between the front cover unit 210 and the rear cover unit 220. In this case, the connection unit 203 may have one side surface connected to a side surface of the rear cover unit 220 and the other side surface connected to a side surface of the front cover unit 210. The rear cover unit 220 and the front cover unit 210 may be bent upon the connection unit 203. The rear cover unit 220 is engaged with the rear surface of the mobile terminal 100. When the front cover unit 210 is flipped closed, the rear cover unit 220 surrounds at least a part of a side surface of the mobile terminal 100. Thus, the mobile terminal 100 may not slip off from the cover 200. In addition, a connector unit 202a is formed in the rear cover unit 220. The connector unit 202a provides cover type information about the cover 200. The cover type information may include information about the position of a window area and an input area formed in the front cover unit 210 of the cover 200. The connector unit 202a may provide the cover type information about the cover 200 to the mobile terminal 100 by electrically connecting to the connection ports 180 formed on the rear surface of the mobile terminal 100. For example, a plurality of connection ports 181 and 182 may be formed on the rear surface of the mobile terminal 100. The connector unit 202a of the cover 200 may be electrically engaged with at least one of the connection ports 181 and 182. The mobile terminal 100 may identify the type of the cover 200 depending on whether the connector unit 202a of the cover 200 is connected to both or one of the connection ports 181 and 182. In another example, irrespective of which connection port the connector unit 202a of the cover 200 is connected to, the mobile terminal 100 may identify the type of the cover 200. [0062]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention. [0063]In FIG. 3, the rear cover unit 220 is formed as a rear case 220b. Referring to FIG. 3, the cover 200 includes the front cover unit 210, the connection unit 203, and the rear case 220b. The mobile terminal 100 may be fixedly inserted in the rear case 220b. The mobile terminal 100 with a battery cover 220a engaged with its rear surface may be inserted in the rear case 220b. [0064]The rear case 220b includes a base 221, at least one sidewall 222 formed along the periphery of the base 221, and a catching portion 223. The sidewall 222 is formed substantially straight up and perpendicular from the plane of the base 221. A bottom of the sidewall 220 is connected to the base 221 and the catching portion 223 is formed in an upper end of the sidewall 222. An inner space defined by the base 221 and the sidewall 222 has a size and a shape corresponding to the size and shape of the mobile terminal 100. If the mobile terminal 100 is accommodated in the inner space, the catching portion 223 may prevent slip-off of the mobile terminal 100 from the inner space. The front cover unit 210 is connected to one side surface of the rear case 220b. The connection unit 203 may be formed between the front cover unit 210 and the rear case 220b. In this case, the connection unit 203 has one side surface connected to a side surface of the rear case 220b and the other side surface connected to a side surface of the front cover unit 210. The rear case 220b and the front cover unit 210 may be bent upon the connection unit 203. [0065]If the window area 201a and the input area 201b are formed at predetermined positions on the front cover unit 210 of the cover 200, when the cover 200 is closed, the mobile terminal 100 may display information through the window area 201a and receive a user input through the input area 201b despite having no knowledge of cover type information about the cover 200. [0066]In an embodiment of the present invention, a cover type information transmitter 224 may further be formed in the cover 200 for providing cover type information about the cover 200 to the mobile terminal 100 via short-range communication. The cover type information transmitter 224 may transmit the cover type information about the cover 200 to the mobile terminal 100 by a short-range communication scheme such as, for example, Near Field Communication (NFC), Radio Frequency Identification (RFID), Bluetooth, Wireless Fidelity (WiFi) Direct, or the like. The mobile terminal 100 may then identify the type of the cover 200 based on the cover type information received from the cover 100 by the short-range communication scheme. [0067]While it has been described above, with reference to FIG. 3, that the rear cover unit 220 of the cover 200 is configured as a case, the shapes of the rear cover unit 220 and the connection unit 203 may be changed as long as the front cover unit 210 is detachably mounted to the mobile terminal 100 and flipped open or closed. [0068]FIGS. 4A and 4B are diagrams illustrating configurations of the front cover unit, according to embodiments of the present invention. FIG. 4A illustrates the window area 201a formed of a transparent or semi-transparent material in the front cover unit 210, and FIG. 4B illustrates the window area 201a formed into a cutout opening in the front cover unit 210. [0069]Referring to FIG. 4A, the front cover unit 210 includes an outer member 211a, an inner member 212a, and a transparent member 213a. The outer member 211a, which forms an outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. An outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms an inner surface of the front cover unit 210, is engaged with a bottom surface of the transparent member 213a, while a bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. An inner hole 2121 is formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The transparent member 213a is interposed between the outer member 211a and the inner member 212a and brings the outer hole 2111 and the inner hole 212 into close contact. A first area defined at a predetermined position of the touch screen 140, for example, in an upper part of the touch screen 140 may be exposed outwardly through the transparent member 213a, the outer hole 2111, and the inner hole 2121. That is, even though the first area of the touch screen 140 is covered with the front cover unit 210, the transparent member 213a may be formed of a material containing a transparent or semi-transparent material so that the user may view information displayed in the first area of the touch screen 140 through the window area 201a. For example, the transparent member 213a may be formed of a transparent or semi-transparent film. The transparent member 213a is larger is size than the window area 201a. In FIG. 4A, the transparent member 213a is as large as the outer member 211a and the inner member 212a. The transparent member 213a may be formed of a material containing a conductive material such as, for example, conductive silicon. Further, the outer member 211a, the inner member 212a, and the transparent member 213a may be formed of a material containing at least one of an anti-static electricity material, silver, and nylon fabric. Accordingly, upon receipt of a touch input in the window area 201a from the user, the touch input may be sensed in the first area of the touch screen 140 corresponding to the window area 201a. For example, when a call is incoming, a notification indicating the call incoming is displayed at a position of the touch screen 140 corresponding to the window area 201a. If the user touches the window area 201a or manipulates a predetermined key, for example, a side key, the call may be connected immediately. [0070]Referring to FIG. 4B, the front cover unit 210 includes the outer member 211a and the inner member 212a to define the window area 201a and cover the touch screen 140, for protection. The outer member 211a, which forms the outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. The outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms the inner surface of the front cover unit 210, is engaged with a bottom surface of the outer member 211a, while the bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. The inner hole 2121 may be formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The outer hole 2111 and the inner hole 2121 are formed having the same size. An opening formed by the outer hole 2111 and the inner hole 2121 may form the window area 201a. Therefore, even though the first area of the touch screen 140 is covered with the front cover unit 210, the user may view information displayed on the touch screen 140 through the opening of the window area 201a. Further, the user may apply a touch input to the touch screen 140 through the window area 201a. Then the mobile terminal 100 may sense the touch input in the first area of the touch screen 140 corresponding to the window area 201a. [0071]In an embodiment of the present invention, the remaining area of the front cover unit 210, except the window area 201a, is a non-window area. At least a part of the non-window area may be defined as an input area (hereinafter, referred to as a ‘cover input area’) in which a user input may be applied. For example, the whole non-window area may be the cover input area. Or a predetermined part of the non-window area may be the cover input area. The cover input area may refer to an area in which a touch input on the outer surface of the outer member 211a can be detected by the touch screen 140, with the front cover unit 210 covering the touch screen 140. Therefore, a user gesture made in the cover input area corresponding to at least a part of the non-window area may be sensed by the touch screen 140. [0072]For example, when the user makes a user gesture in the cover input area of the front cover unit 210, the user gesture may be sensed in a second area of the touch screen 140 corresponding to the cover input area. In various embodiments of the present invention, the window area 201a of the front cover unit 210 may be formed in a first cover area of the front cover unit 210 and the non-window area may be formed in a second cover area other than the first cover area in the front cover unit 210. [0073]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention. [0074]Referring to FIG. 5A, a window area 511 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 511, is defined as a non-window area 521 in a first-type cover, according to an embodiment of the present invention. The whole non-window area 521 may be a cover input area in the first-type cover. [0075]Referring to FIG. 5B, a window area 512 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 512, is defined as the non-window area 521 in a second-type cover, according to an embodiment of the present invention. In the second-type cover, an area of a predetermined size in the non-window area 521 under the window area 512 may be defined as a cover input area 522. In FIG. 5B, the cover input area 522 may be substantially as wide as the window area 512 along a horizontal direction and may extend up to the vicinity of the window area 512 and down to the vicinity of a bottom end of the front cover unit 210. Accordingly, for example, the cover input area 522 may occupy most of the non-window area 521 under the window area 512. [0076]Referring to FIG. 5C, a window area 513 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 513, is defined as the non-window area 521 in a third-type cover, according to an embodiment the present invention. In the third-type cover, a small area at a center of the non-(String), 优先 [0001] 本申请根据 35 U.S.C. § 119(a) 于 2014 年 2 月 11 日向韩国知识产权局提交并转让序列号 10-2014-0015272 的韩国专利申请,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及一种移动终端,更具体地,涉及一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳。 [0004] 2.相关技术的描述 [0005] 诸如智能手机、个人计算机(PC)、平板电脑等的移动终端通过许多应用程序向用户提供各种有用的功能。 [0006] 这样的移动终端正在发展以使用户能够通过各种功能使用各种类型的信息。 [0007] 通常,盖被配置为覆盖形成在移动终端的前表面上的整个显示器。 由于显示器的屏幕被覆盖物覆盖,用户可能不使用显示屏幕。 发明内容 [0008] 做出本发明以至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面提供了一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳,即使移动终端被外壳覆盖,也使得用户能够查看 移动终端的显示屏的至少一部分。 [0009] 本发明的另一方面在于提供一种移动终端、移动终端中的UI方法以及移动终端的封面,当封面覆盖时,提供窗口区域以显示移动终端的显示屏幕的一部分。 移动终端的显示屏,使用户能够识别与封面的窗口区域对应的显示屏的区域,从而可以以各种方式控制在与封面的窗口区域对应的区域上的显示。 [0010] 根据本发明的一个方面,提供了一种用于在移动终端中处理输入的方法。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域。 定义了移动终端的触摸屏上与封面的非窗口区域对应的第二区域。 当盖子在触摸屏上关闭时,检测到第二区域中的第一输入。 第一输入被处理为第一控制命令。 [0011] 根据本发明的另一方面,提供了一种包括触摸屏和处理器的移动终端。 处理器用于定义触摸屏的第一区域对应于移动终端的封面的窗口区域, 定义触摸屏的第二区域对应于封面的非窗口区域, 检测第一 合上触摸屏时在第二区域输入,并将第一输入处理为第一控制命令。 [0012] 根据本发明的另一方面,提供了一种移动终端,其包括用于覆盖移动终端的触摸屏的覆盖物,该覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域。 该移动终端还包括触摸屏,该触摸屏包括与封面的窗口区域对应的第一区域和与封面的非窗口区域对应的第二区域。 移动终端还包括处理器,被配置为根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时触摸屏被覆盖物覆盖。 [0013]根据本发明的另一方面,提供了一种用于移动终端的盖,其包括被配置为覆盖形成在移动终端的前表面上的触摸屏的前盖单元。 盖还包括被配置为覆盖移动终端的后表面的后盖单元。 前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域。 前盖单元的非窗口区域包括输入区域。 在前盖单元覆盖移动终端的触摸屏的同时,通过非窗口区域的输入区域对触摸屏进行输入。 [0014] 根据本发明的另一方面,提供了一种用于处理移动终端中的输入的制品。 所述制品包括包含一个或多个程序的机器可读介质,所述程序在执行时实现以下步骤: 定义与移动终端的封面的窗口区域相对应的触摸屏的第一区域; 定义触摸屏的第二区域,对应于盖板的非窗口区域; 当盖板合上触摸屏时,检测第二区域中的第一输入; 处理第一输入作为第一控制命令。 附图的简要说明 [0015] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0016] 图 附图说明图1A和图1B是示出了根据本发明实施例的与盖子接合的移动终端的外部透视图; [0017] 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图; [0018] 如图。 图2B是示出根据本发明实施例的移动终端机盖的背面的图; [0019] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图; [0020] 图 图4A和4B是示出根据本发明实施例的前盖单元的构造的图; [0021] 图 图5A、5B、5C和5D是示出根据本发明实施例的各种类型的盖的图; [0022] 如图。 图6是说明根据本发明的一个实施例的确定移动终端是否被覆盖物覆盖的操作的图。 [0023] 如图。 图7是根据本发明实施例的移动终端的框图; [0024] 如图。 图8是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的分别对应于封面的窗口区域和封面输入区域的第一区域和第二区域的UI操作的流程图 ; [0025] 图 图9、10、11和12是示出根据本发明实施例的为各种类型的封面定义的触摸屏区域的图; [0026] 如图。 图13是说明根据本发明的实施例的触摸输入的图; [0027] 如图。 图14是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制音乐播放信息的操作的流程图; [0028] 图 图15A和15B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制音乐播放信息的屏幕的图; [0029] 如图。 图16是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的操作的流程图; [0030] 如图。 图17是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的屏幕的图; [0031]如图。 图18是示出根据本发明实施例的使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的操作的流程图; [0032] 图 图19A、19B、20A和20B是示出了根据本发明的实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的屏幕的图; [0033] 如图。 图21是示出根据本发明的实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制应用程序的操作的流程图; [0034] 图 图22A、22B、23A和23B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制应用的屏幕的图; [0035] 图 图24A、24B和24C是示出根据本发明另一实施例的具有形成在其上的小键盘的盖的图; [0036] 如图。 图25是示出根据本发明实施例的形成在前盖单元上的小键盘的图; [0037] 图 图26A、26B和26C是图示根据本发明实施例的形成在前盖单元上的键的图; [0038] 图 图27A和27B是分别示出了根据本发明实施例的全屏和小屏幕的图; [0039] 图 图28A、28B、28C、28D和28E是图解1的迷你屏幕的图。 st 到 5 th 分别根据本发明的一个实施例的类型; [0040] 图 图29A、29B、29C、29D和29E是图解说明6的迷你屏幕的图 th 到 10 th 类型,根据本发明的一个实施例; [0041] 图 图30A和30B是图解说明11的迷你屏幕的图 th 和 12 th 类型,根据本发明的一个实施例; [0042] 如图。 图31是说明13的小屏幕的图 th 类型,根据本发明的一个实施例; [0043] 图 图32A和32B是图示根据本发明实施例的用于控制迷你屏幕的显示的方法的图; [0044] 图 图33A、33B、33C、34A、34B、34C、34D和34E是示出根据本发明实施例的通过移动终端中的封面单元的小键盘由文本输入触发的操作的图; [0045] 图 图35A、35B、35C、35D和35E是图示根据本发明实施例的通过移动终端中的封面单元的键盘的不同类型的文本输入触发的操作的图; [0046] 图 图36A、36B、36C、36D和36E是示出在移动终端中在前盖单元关闭的同时通过前盖单元的小屏幕或键盘接收输入时执行呼叫功能的操作的图 ,根据本发明的一个实施例; [0047] 图 图37A、图37B和图37C是示出在移动终端中前盖单元关闭时,在通过前盖单元的小屏幕或键盘接收输入时执行消息功能的操作的图。 本发明的实施例; [0048] 图 图38A、图38B、图38C、图38D、​​图38E、图38F和图38G是示出根据本发明实施例的在移动终端中在前盖单元关闭的同时在迷你屏幕上选择应用时执行各种应用功能的操作的图。 本发明; [0049] 图 图39A和39B是图示根据本发明实施例的需要文本输入的应用程序的图; 和 [0050] 图 图40A和40B是示出根据本发明实施例的在移动终端中前盖单元关闭时显示的盖打开请求消息的图。 本发明实施方案的详细说明 [0051]下面结合附图对本发明实施例进行详细描述。 尽管它们在不同的附图中示出,但是相同或相似的部件可以用相同或相似的附图标记表示。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0052] 以下描述中使用的术语和词语不限于标准字典中提供的含义,而仅用于使本公开内容能够清晰一致地理解。 因此,本领域技术人员应该清楚,提供本发明实施例的以下描述仅用于说明目的,而不是用于限制本公开的目的。 [0053] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0054] 使用术语“基本上”是指不需要精确地实现所列举的特性、参数或值,而是偏差或变化,包括例如公差、测量误差、测量精度限制和本领域技术人员已知的其他因素。 该技术可能以不排除该特性旨在提供的效果的数量出现。 [0055] 根据本发明的各种实施例的移动终端可以被实施为配备有显示器的电子设备,例如,可以用盖子覆盖的触摸屏。 例如,移动终端可以是可视电话、移动电话、智能手机、国际移动电信2000(IMT 2000)终端、宽带码分多址(WCDMA)终端、通用移动电信系统(UMTS)中的任何一种。 ) 终端、个人数字助理 (PDA)、便携式多媒体播放器 (PMP)、数字多媒体广播 (DMB) 终端、电子书阅读器、膝上型个人电脑 (PC)、平板电脑、数码相机、 之类的。 [0056] 图 图1A和1B是示出根据本发明实施例的与盖接合的移动终端的外部透视图的图。 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图。 如图。 图2B是图示根据本发明实施例的移动终端的盖的后表面的图。 [0057] 参考图。 参考图1A、1B、2A和2B,移动终端 100 可能与盖子接合 200 . 显示多种功能的屏幕的显示设备,例如触摸屏 140 设置在移动终端的正面 100 . 一个挡板 102 围绕触摸屏的外围的至少一部分形成 140 在移动终端的正面 100 . 一个主页按钮 105 、扬声器、照相机、传感器等可以形成在边框中 102 . 一块电池 170 安装在移动终端的背面 100 给移动终端供电 100 . 电池 170 可以可拆卸地形成在移动终端的背面 100 ,或者可以内置在移动端 100 以免用户取出电池 170 从移动终端 100 . 后盖单元 220 设置在移动终端的背面 100 . 连接端口 180 设置在移动终端的背面 100 , 后盖单元内部 220 , 用于电气连接。 后盖单元 220 能够与移动终端的背面接合 100 , 覆盖电池 170 . 封面 200 被配置为覆盖移动终端的前表面的至少一部分 100 . 当封面 200 覆盖移动终端的正面 100 , 一个前盖单元 210 至少覆盖触摸屏的一部分 140 . 此外,当封面 200覆盖移动终端的正面 100 , 前盖单元 210 至少覆盖挡板的一部分 102 . 当前盖单元 210 至少覆盖触摸屏的一部分 140 ,触摸屏的剩余部分 140 通过窗口区域向外暴露 201 a 形成在前盖单元中 210 . 移动终端 100 可以控制内容的显示,例如时钟、文本、数字、呼叫者号码、用户环境设置等,在触摸屏的部分中 140 通过窗口区域暴露 201 a 前盖单元的 210 . [0058] 前盖单元 210 封面的 200 可以翻转打开或关闭。 当前盖单元 210 封面的 200 打开时,触摸屏的整个区域 140 移动终端的 100 外露,如图所示。 1A。 如果前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 移动终端的 100 被前盖单元盖住 210 ,如图所示。 1B。 参考图。 1B、当前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 对应窗口区域 201 a 外露,而触摸屏的其余部分 140 被覆盖。 [0059] 此外,当前盖单元 210 封面的 200 封闭,形成在边框中的一部分(例如,扬声器) 102 移动终端的 100 通过开口向外暴露 201 b 形成在前盖单元中 210 . 虽然只有一个开口 201 b 如图所示。 如图1B所示,可以在前盖单元中形成多个开口 210 这样即使前盖单元 210 封闭,在边框中形成多个部件(例如,扬声器、相机等) 102 可以通过多个开口向外暴露。 [0060] 参考图。 2A和2B,盖 200 包括前盖单元 210 和后盖单元 220 . 封面 200 还包括连接单元 203 夹在前盖单元之间 210 和后盖单元 220 , 用于连接前盖单元 210 到后盖单元 220 . 连接单元 203 可以覆盖移动终端侧面的一部分 100 . [0061] 前盖单元 210 覆盖移动终端的正面 100 并包括窗口区域或屏幕投影仪, 201 a 露出触摸屏的一部分 140 . 窗口区域 201 a 可以由透明或半透明材料形成,或者可以形成在前盖单元中的开口中 210 这样当封面 200 覆盖移动终端的正面 100 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域 201 a . 因此,用户可以查看显示在触摸屏上的信息 140 前盖单元内部 210 通过窗口区域 201 a 从前盖单元外部 210 . 因此,即使前盖单元 210 关闭时,用户可以查看触摸屏上显示的简短信息 140 通过窗口区域 201 a 并且可以通过前盖单元输入用户命令 210 执行与显示信息相关的功能。 后盖单元 220 形成为电池盖 220 a 在图 例如,图2B。 参考图。 2B、后盖单元 220 覆盖移动终端的背面 100 . 后盖单元 220 可以固定或可拆卸地安装在移动终端的背面 100 . 前盖单元 210 可以连接到后盖单元的侧表面220 . 连接单元 203 可以形成在前盖单元之间 210 和后盖单元 220 . 在这种情况下,连接单元 203 可以具有连接到后盖单元的侧表面的一个侧表面 220 另一个侧面连接到前盖单元的侧面 210 . 后盖单元 220 和前盖单元 210 可能弯曲在连接单元上 203 . 后盖单元 220 与移动终端的背面接合 100 . 当前盖单元 210 翻转关闭,后盖单元 220 包围移动终端的侧表面的至少一部分 100 . 因此,移动终端 100 不能从封面上滑落 200 . 此外,连接器单元 202 a 形成在后盖单元中 220 . 连接器单元 202 a 提供有关封面的封面类型信息 200 . 封面类型信息可以包括关于形成在前封面单元中的窗口区域和输入区域的位置的信息 210 封面的 200 . 连接器单元 202 a 可以提供关于封面的封面类型信息 200 到移动终端 100 通过电连接到连接端口 180 形成在移动终端的背面 100 . 例如,多个连接端口 181 和 182 可以形成在移动终端的背面 100 . 连接器单元 202 a 封面的 200 可以与至少一个连接端口电接合 181 和 182 . 移动终端 100 可以识别封面的类型 200 取决于连接器单元是否 202 a 封面的 200 连接到两个或一个连接端口 181 和 182 . 在另一个示例中,无论连接器单元是哪个连接端口 202 a 封面的 200 连接到移动终端 100 可以识别封面的类型 200 . [0062] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图。 [0063] 在图。 3、后盖单元 220 形成为后壳 220 b . 参考图。 3、封面 200 包括前盖单元 210 , 连接单元 203 , 和后壳 220 b . 移动终端 100 可固定插入后壳 220 b . 移动终端 100 带电池盖 220 a 与其后表面啮合可以插入后壳 220 b. [0064] 后壳 220 b 包括一个基地 221 , 至少一个侧壁 222 沿底座周边形成 221 , 和一个捕捉部分 223 . 侧壁 222 形成为基本上笔直向上并垂直于基部的平面 221 . 侧壁的底部 220 连接到底座 221 和捕捉部分 223 形成于侧壁的上端 222 . 由底座定义的内部空间 221 和侧壁 222 具有与移动终端的大小和形状相对应的大小和形状 100 . 如果移动端 100 容纳在内部空间中的抓持部分 223 可防止移动终端滑落 100 从内部空间。 前盖单元 210 连接到后壳的一侧表面 220 b . 连接单元 203 可以形成在前盖单元之间 210 和后壳 220 b . 在这种情况下,连接单元 203 具有连接到后壳的侧面的一个侧面 220 b 另一个侧面连接到前盖单元的侧面 210 . 后壳 220 b 和前盖单元 210 可能弯曲在连接单元上 203 . [0065] 如果窗口区域 201 a 和输入区域 201 b 形成在前盖单元上的预定位置 210 封面的 200 , 当覆盖 200 关闭,移动端 100 可以通过窗口区域显示信息 201 a 并通过输入区域接收用户输入 201 b 尽管不知道关于封面的封面类型信息 200 . [0066] 在本发明的一个实施例中,一种覆盖式信息发送器 224 可以进一步形成在盖中 200 用于提供有关封面的封面类型信息 200 到移动终端 100 通过短距离通信。 盖式信息发射器 224 可以传输关于封面的封面类型信息 200 到移动终端 100 通过短距离通信方案,例如近场通信(NFC)、射频识别(RFID)、蓝牙、无线保真(WiFi) Direct等。 移动终端 100 然后可以识别封面的类型 200 基于从封面收到的封面类型信息 100 通过短距离通信方案。 [0067] 虽然上面已经描述了,但参考图1。 3、即后盖单元 220 封面的 200 配置为外壳,后盖单元的形状 220 和连接单元 203 只要前盖单元可以更改 210 可拆卸地安装在移动终端上 100 并翻转打开或关闭。 [0068] 图 图4A和4B是图示根据本发明实施例的前盖单元的配置的图。 如图。 图4A说明了窗口区域 201 a 在前盖单元中由透明或半透明材料制成 210 ,和图。 图4B图示了窗口区域 201 a 在前盖单元中形成一个切口 210 . [0069] 参考图。 4A、前盖单元 210 包括一个外部成员 211 a , 一个内部成员 212 a , 和一个透明的成员 213 a . 外部成员 211 a ,其形成前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 一个外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,其形成前盖单元的内表面 210 ,与透明构件的底面接合 213 a ,而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 一个内孔 2121 形成在内构件的位置 212 a 对应外孔 2111 , 定义窗口区域 201 a . 透明成员 213 a 夹在外构件之间 211 a 和内部成员 212 a 并带来外孔 2111 和内孔 212 密切接触。 第一区域定义在触摸屏的预定位置 140 ,例如,在触摸屏的上部 140 可以通过透明构件向外暴露 213 a , 外孔 2111 , 和内孔 2121 . 也就是说,即使触摸屏的第一个区域 140被前盖单元盖住 210 , 透明构件 213 a 可以由包含透明或半透明材料的材料形成,以便用户可以查看显示在触摸屏的第一区域中的信息 140 通过窗口区域 201 a . 例如,透明构件 213 a 可以由透明或半透明膜形成。 透明成员 213 a 大于窗口区域的大小 201 a . 在图。 4A、透明件 213 a 与外部成员一样大 211 a 和内部成员 212 a . 透明成员 213 a 可以由包含导电材料的材料形成,例如导电硅。 此外,外部构件 211 a , 内部成员 212 a , 和透明构件 213 a 可以由包含抗静电材料、银和尼龙织物中的至少一种的材料形成。 因此,当在窗口区域中接收到触摸输入时 201 a 来自用户的触摸输入可以在触摸屏的第一区域中被感测到 140 对应窗口区域 201 a . 例如,当有来电时,在触摸屏的位置显示来电的通知 140 对应窗口区域 201 a . 如果用户触摸窗口区域 201 a 或者操作预定键,例如侧键,可以立即接通通话。 [0070] 参考图。 4B、前盖单元 210 包括外部成员 211 a 和内部成员 212 a 定义窗口区域 201 a 并覆盖触摸屏 140 ,为了保护。 外部成员 211 a ,它形成了前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,它形成前盖单元的内表面 210 ,与外构件的底面接合 211 a , 而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 内孔 2121 可以形成在内部构件的位置处 212 a 对应外孔 2111 , 定义窗口区域 201 a . 外孔 2111 和内孔 2121 形成具有相同的尺寸。 由外孔形成的开口 2111 和内孔 2121 可以形成窗口区域 201 a . 因此,即使触摸屏的第一区域 140 被前盖单元盖住 210 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域的开口 201 a . 此外,用户可以将触摸输入应用到触摸屏 140 通过窗口区域 201 a . 然后是移动端 100 可以感应触摸屏第一区域的触摸输入 140 对应窗口区域 201 a. [0071] 在本发明的一个实施例中,前盖单元的剩余区域 210 , 除了窗口区域 201 a, 是非窗口区域。 非窗口区域的至少一部分可以被定义为可以应用用户输入的输入区域(以下称为“覆盖输入区域”)。 例如,整个非窗口区域可以是封面输入区域。 或者,非窗口区域的预定部分可以是封面输入区域。 覆盖输入区域可以是指在外部构件的外表面上进行触摸输入的区域 211 a 可通过触摸屏检测 140 , 带前盖单元 210 覆盖触摸屏 140 . 因此,在对应于至少部分非窗口区域的覆盖输入区域中做出的用户手势可以被触摸屏感测到 140 . [0072] 例如,当用户在封面单元的封面输入区域中做出用户手势时 210 ,可以在触摸屏的第二区域中感测到用户手势 140 对应于封面输入区域。 在本发明的各个实施例中,窗口区域 201 a 前盖单元的 210 可以形成在前盖单元的第一盖区域中 210 并且非窗口区域可以形成在前盖单元中除第一覆盖区域之外的第二覆盖区域中 210 . [0073] 图 图5A、5B、5C和5D是图示根据本发明实施例的各种类型的盖的图。 [0074] 参考图。 5A、窗口区域 511 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 511 , 定义为非窗口区域 521 在根据本发明的一个实施例的第一种盖子中。 整个非窗口区域 521 可以是第一类封面中的封面输入区域。 [0075] 参考图。 5B、窗口区域 512 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 512 , 定义为非窗口区域 521 在根据本发明的一个实施例的第二种盖中。 在第二种盖板中,非窗区域中的预定大小的区域 521 窗下区域 512 可以定义为一个覆盖输入区域 522 . 在图。 5B、覆盖输入区域 522 可以基本上与窗口区域一样宽 512 沿水平方向并可能延伸到窗口区域附近 512 并向下至前盖单元的底端附近 210 . 因此,例如,封面输入区域 522 可能占据大部分非窗口区域 521 窗下区域 512 . [0076] 参考图。 5C、窗口区域 513 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 513 , 定义为非窗口区域 521 在根据本发明的一个实施例的第三种盖子中。 第三种封面中,非窗口区域中心的一小块区域 521 窗下区域 513 可以定义为一个覆盖输入区域 523 . 封面输入区 523 在第三类覆盖中小于覆盖输入区域 522 以第二类封面为例。 [0077] 参考图。 5D,一个窗口区域 514 在前盖单元的右侧部分拉长 210 沿前盖单元的长度方向 210 ,以及前盖单元的剩余区域 210 , 除了窗口区域 514 , 定义为非窗口区域 521 在根据本发明的实施例的第四类盖中。 封面输入区 524 在非窗口区域的一部分定义 521 在窗口区域的左侧 514 . [0078] 而单个窗口区域 511 , 512 , 513 , 和 514 形成在前盖单元中 210在图 参照图5A、5B、5C和5D,作为示例,可以改变窗口区域的位置或数量。 例如,窗口区域 511 , 512 , 513 , 和 514 可以设置在前盖单元的中心 210 或者可以沿水平方向拉长。 因此窗口区域的位置 511 , 512 , 513 , 和 514 可能会有所不同。 虽然已经描述了在前盖单元中定义了一个窗口区域 210 在本发明的实施例中,可以在前盖单元中定义多个窗口区域 210 ,根据本发明的各种实施例。 此外,至少一部分非窗口区域 521 可用作覆盖输入区域。 例如,整个或部分非窗口区域 521 可以定义为覆盖输入区域。 在覆盖输入区域中进行的用户手势(例如,触摸输入)的输入时,可以在触摸屏的第二区域中检测到用户手势 140 对应于封面输入区域。 [0079] 移动终端 100 可以将窗口区域与封面单元中的封面输入区域区分开来 210 ,根据上述各种类型的封面。 因此,移动端 100 可以定义触摸屏上的第一和第二区域 140 对应前盖单元的窗口区域和封面输入区域 210 , 分别。 [0080] 在本发明的各个实施例中,前盖单元 210 移动终端的 100 可能会覆盖触摸屏 140 在移动终端的正面 100 和移动终端 100 可判断是否触摸屏 140 已被前盖单元盖住 210 . [0081] 如图。 图6是示出根据本发明实施例的用于确定移动终端是否被覆盖物覆盖的操作的图。 [0082] 参考图。 6、封面 200 包括一个磁力施加器 691 , 在前盖单元的内部 210 ,提供有关封面的封面类型信息 200 . [0083] 磁力施加器 691 例如,可以是永磁体并且可以施加磁力。 磁力施加器 691 可以产生对应于封面类型信息的磁力。 [0084] 例如,如果前盖单元 210 覆盖移动终端的正面 100 , 一个传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 , 和移动终端 100 可确定前盖单元是否 210 已经覆盖了移动终端的正面 100 基于磁力传感器的传感结果 692 传感器单元 160 . 此外,当前盖单元 210 覆盖移动终端的正面 100 , 传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 对应封面类型信息,移动端 100 可以确定封面的封面类型信息 200 基于磁力传感器的传感结果 692 传感器单元 160 . [0085] 在本发明的一个实施例中,触摸屏 140 移动终端的 100 可以独立显示屏幕并感知触摸。 移动终端 100 可以激活触摸屏的显示屏 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . 或者手机端 100 可以激活触摸屏的触摸感应区域 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . [0086] 例如,如果前盖单元 210 没有覆盖触摸屏 140 , 移动端 100 可以激活触摸屏的全屏显示 140 以及触摸屏的全触摸感应区域。 [0087] 另一方面,如果前盖单元 210 已经覆盖了触摸屏 140 , 移动端 100 可以在触摸屏的显示屏上激活第一区域的信息显示和触摸感应,仅对第二区域进行触摸感应 140 . 在这种情况下,可以在触摸屏的显示屏幕中停用除第一和第二区域之外的剩余区域 140 . [0088] 移动终端 100 可以从封面类型信息提供者那里接收封面类型信息 710 封面的 200 . 封面类型信息提供者 710 可能是连接器单元之一 202 a ,盖式信息发射器 224 , 和磁力施加器 691 . [0089] 如图。 图7是移动终端的框图 100 ,根据本发明的一个实施例。 [0090] 参考图。 7、移动端 100 包括一个控制器 110 , 一个通讯单元 120 , 一段记忆 130 , 触摸屏 140 , 和一个输入/输出 (I/O) 单元 150 . [0091] 控制器 110 包括一个中央处理器 (CPU) 111 . 控制器 110 可以包括数字信号处理器(DSP)并且可以被称为处理器。 控制器 110 包括一个只读存储器 (ROM) 112 用于存储控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 用于存储从移动终端外部接收的信号或数据 100 或用作移动终端执行操作的内存空间 100 . 中央处理器 111 可以包括一个或多个核心。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线互连。 控制器 110 可以控制通信单元 120 , 记忆 130 , 触摸屏 140 , 和 I/O 单元 150 . 例如,控制器 110 可为移动终端提供整体控制 100 并且可以控制上述组件之间的信号流。 [0092] 控制器 110 可以区分前盖单元中的窗口区域和封面输入区域 210 封面的 200 根据封面的类型 200 . 因此,控制器 110 可以在触摸屏上定义第一和第二区域 140 ,对应前盖单元的窗口区域和封面输入区域 210 . [0093] 当前盖单元 210 关闭,从而覆盖触摸屏 140 , 控制器 110 可以激活触摸屏的第一和第二区域 140 , 同时停用触摸屏的剩余区域 140 . 因此,控制器 110 可以检测到触摸屏的第一和第二区域的用户手势输入 140 通过前盖单元 210 . [0094] 控制器 110 可以控制触摸屏不同区域的不同触摸输入灵敏度的设置 140 . 例如,控制器 110 可以在触摸屏的第二区域设置更大的触摸输入灵敏度 140 比在触摸屏的第一个区域 140 . 例如,如果前盖单元 210 关闭,控制器 110 可以将触摸屏的第二区域的触摸输入灵敏度设置为大于第一区域的触摸输入灵敏度 140 . 触摸屏第一区和第二区的触摸输入灵敏度 140 可以设置为足够大以容纳触摸屏 140 检测在前盖单元上做出的用户手势 210 , 即使前盖单元 210 覆盖触摸屏 140 . [0095] 此外,控制器 110可以控制设置不同的触摸输入灵敏度,以根据前盖单元是否在触摸屏的第一和第二区域中感测触摸输入 210 覆盖触摸屏 140 . 例如,如果封面 200 不覆盖触摸屏 140 , 控制器 110 可以控制整个触摸屏上相同的触摸输入灵敏度的设置 140 . 另一方面,如果前盖单元 210 覆盖触摸屏 140 , 控制器 110 可以控制在第二区域中设置比在第一区域中更高的触摸输入灵敏度。 因此,即使当窗口区域比非窗口区域厚或窗口区域在非窗口区域关闭时打开,也可以正常感测到第二区域的触摸输入。 控制器 110 可以识别封面的类型 200 并判断前盖单元是否 210 覆盖触摸屏的显示屏 140 通过传感器单元接收封面类型信息 160 , 连接端口 180 ,或封面类型信息接收器 190 . 控制器 110 可以定义区域,例如包括对应于前盖单元的窗口区域的第一区域 210 第二区域对应于前盖单元的盖输入区域 210 , 在触摸屏上 140 根据封面类型。 例如,虽然封面 200 前盖单元的 210 覆盖触摸屏的显示屏 140 , 控制器 110 可以确定是否发生了事件。 当事件发生时,控制器 110 可在触摸屏上定义 140 ,区域包括例如第一区域对应于封面的窗口区域 200 ,例如,前盖单元 210 第二个区域对应于封面的封面输入区域 200 ,例如,前盖单元 210 . 事件可以包括预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 可能还有许多其他事件。 该事件可以是任何事件,只要它触发在显示屏幕上包括第一和第二区域的区域的定义。 [0096] 通讯单元 120 可连接移动终端 100 通过一根或多根天线连接到外部设备,并且可以与外部设备进行通信。 外部设备可以包括另一设备、便携式电话、智能手机、平板PC和服务器。 通讯单元 120 可以包括各种通信模块,例如移动通信模块、NFC模块、蓝牙模块等,并且可以通过各种通信方案例如移动通信、NFC、蓝牙等与外部设备进行通信。 喜欢。 [0097] 例如,移动终端 100 可以向便携式电话、智能手机、平板电脑或具有输入到移动终端的电话号码的其他设备发送无线信号或从其接收无线信号 100 ,用于通过移动通信模块进行语音通话、视频通话、短消息服务(SMS)或多媒体消息服务(MMS)。 此外,移动终端 100 可以通过NFC模块或蓝牙模块从外部设备接收信息。 在本发明的各个实施例中,通信单元 120 除了NFC模块和蓝牙模块之外,还可以包括无线局域网(WLAN)模块和另一短程通信模块中的至少一个,并且可以通过WLAN模块和短程通信中的至少一个接收信息 模块。 WLAN模块可以在控制器的控制下连接到互联网 110在安装了无线接入点 (AP) 的地方。 WLAN模块可以支持电气和电子工程师协会(IEEE)的WLAN标准IEEE802.11x。 短距离通信模块可以在移动终端之间进行短距离无线通信 100 和控制器控制下的外部设备 110 . 短距离通信可以符合红外数据协会(IrDA)等。 [0098] 记忆 130 可根据控制器的操作存储输入/输出信号或数据 110 , 通讯单元 120 , 触摸屏 140 , 和 I/O 单元 150 , 在控制器的控制下 110 . 记忆 130 可以存储多个用于控制移动终端的程序 100 或控制器 110 、多个应用程序以及用于执行各种功能的程序和数据。 [0099] 术语“存储器”可能包括 ROM 112 和内存 113 控制器内 110 ,或安装在移动终端上的存储卡(例如,安全数字(SD)卡、记忆棒等) 100 . 记忆 130 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)、固态驱动器(SSD)等。 [0100] 记忆 130 可以是机器可读介质(例如,计算机可读介质)。 机器可读介质可以定义为向机器提供数据以便机器可以执行特定功能的介质。 机器可读介质可以是存储介质。 记忆 130 可以包括非易失性介质和易失性介质。 所有这些媒体都应该是一种类型,可以为向机器读取命令的物理设备提供可检测的命令。 机器可读介质包括但不限于软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、光盘中的至少一种。 穿孔卡、纸带、RAM、可编程 ROM (PROM)、可擦除 PROM (EPROM) 和 Flash-EPROM。 在本发明的一个实施例中,存储器 130 可以存储封面类型信息。 [0101] 触摸屏 140 可以向用户提供各种图形用户界面(GUI)。 例如,触摸屏 140 可以通过用户的身体部位(例如,手指)或触摸输入单元接收各种手势输入,包括至少一个触摸输入或接近输入 158 (例如,一支笔)。 触摸屏 140 例如,可以实现为电阻型、电容型、电磁共振(EMR)型或它们的组合。 [0102] 在本发明的一个实施例中,触摸屏 140 可以在控制器的控制下显示应用程序的执行屏幕、消息屏幕、消息写入屏幕、消息接收屏幕等 110 . 此外,触摸屏 140 可以在显示屏的预定部分区域显示信息,例如触摸屏的第一区域 140 对应窗口区域 201 a ,而不在第一区域以外的区域显示信息。 [0103] 输入输出模块 150 包括一个按钮 152 , 麦克风 154 , 扬声器 156 , 和输入单元 158 , I/O 模块 150 不受限制。 可以提供光标控件,例如鼠标、轨迹球、操纵杆或光标方向键,用于与控制器通信 110 以及用于控制触摸屏上的光标移动 140 . [0104] 一个或多个按钮 152 可在移动终端中提供 100 并且可以向控制器提供与用户的按压相对应的各种输入信号 110 . [0105] 麦克风 154 可以接收来自各种声源的语音或声音,并在控制器的控制下将接收到的语音或声音转换为电信号 110 . [0106] 演讲者 156可以将与各种信号(例如,无线信号、广播信号、数字音频文件、数字视频文件等)对应的声音与应用程序的执行一起输出到移动终端的外部 100 在控制器的控制下 110 . [0107] 输入单元 158 可以是被配置为插入并保存在移动终端内部的设备或对象 100 ,或者单独配置。 在前一种情况下,输入单元 158 可以从移动终端中取出或插入移动终端 100 . 输入单元 158 可以是用户的手指,也可以是触控笔(以下简称笔)等输入工具,可以通过接近或触摸触摸屏来输入用户手势 140 . [0108] 移动终端 100 还可以包括传感器单元 160 . 传感器单元 160 可以包括至少一个磁力传感器 692 . 传感器单元 160 可以感应到永磁体施加的磁力 691 封面的 200 . [0109] 移动终端 100 还可以包括连接端口 180 . 连接端口 180 可以连接到连接器单元 202 a 封面的 200 . 一旦连接端口 180 连接到连接器单元 202 a , 连接端口 180 可能会收到有关封面的封面类型信息 200 从连接器单元 202 a. [0110] 移动终端 100 还可以包括封面类型信息接收器 190 . 封面式信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 . 如果覆盖类型信息接收器 190 被配置为短距离通信模块,当前盖单元 210 覆盖移动终端的正面 100 , 覆盖类型信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 , 和控制器 110 可确定前盖单元是否 210 覆盖触摸屏 140 基于从封面类型信息接收器接收的封面类型信息 190 . [0111] 如图。 图8是示出使用定义在触摸屏上的第一区域和第二区域的UI操作的流程图 140 ,分别对应封面的窗口区域和封面输入区域 200 在移动端 100 ,根据本发明的一个实施例。 [0112] 参考图。 8、移动端 100 标识封面的封面类型 200 , 在步 810 . 例如,控制器 110 移动终端的 100 可以识别封面的封面类型 200 通过感应从盖子施加的磁力 200 或通过接收有关封面的封面类型信息 200 从封面 200 . 关于封面的封面类型信息 200 可以包括关于在封面上定义的窗口区域和封面输入区域的位置信息 200 . 关于封面的封面类型信息 200 可能包括封面标识符 (ID) 和控制器 110 可以确定封面的窗口区域和封面输入区域的位置 200 使用封面 ID。 在这种情况下,关于窗口区域的位置和封面的封面输入区域的信息 200 各种封面ID可以预先存储在内存中 130 . 封面类型信息还可以包括关于封面的大小和位置中的至少一项的信息 200 以及封面的非窗口区域的位置 200 . [0113] 在步骤 820 , 控制器 110 确定触摸屏的触摸屏区域 140 包括对应于盖的窗口区域的第一区域 200 以及对应于封面的封面输入区域的第二区域 200 ,基于关于封面的封面类型信息200 . [0114] 带前盖单元 210 封面的 200 关闭,控制器 110 判断触摸屏上是否输入了用户手势 140 通过前盖单元 210 , 在步 830 . [0115] 如果在触摸屏的第二区域检测到用户手势 140 对应前盖单元的封面输入区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 在一步 840 . [0116] 如果在触摸屏的第一区域检测到用户手势 140 对应前盖单元的窗口区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 , 在步 850 . [0117] 例如,使用触摸屏 140 移动终端的 100 用前盖单元盖住 210 , 控制器 110 可以判断移动终端是否发生了事件 100 并且可以在触摸屏的第一区域显示与事件对应的信息 140 对应前盖单元的窗口区域 210 . 控制器 110 根据对触摸屏的第二区域的用户手势输入执行预定操作 140 ,对应前盖单元的封面输入区域 210 . 事件可以包括例如预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 这些事件纯粹是示范性的。 本领域技术人员可以清楚地理解,触发触摸屏第一区域显示信息的各种事件 140 在触摸屏的第二区域接收用户手势 140 可以实施。 [0118] 此外,例如,控制器 110 可以在触摸屏的显示画面中识别窗口区域对应的第一区域和覆盖输入区域对应的第二区域 140 ,基于关于封面的封面类型信息,并且可以激活第一区域作为信息显示区域和第二区域作为触摸输入区域。 这里,也可以在第一区域中感测触摸输入。 [0119] 图 图9、图10和图11是图示根据本发明实施例的用于各种类型的盖子的触摸屏区域的配置的图。 [0120] 参考图。 9、窗口区 910 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 920 , 和整个非窗口区域 920 是封面中的封面输入区域 200 ,根据本发明的一个实施例。 [0121] 在本实施例中,移动终端 100 激活第一区域 911 对应窗口区域 910 和第二个区域 921 对应非窗口区域 920 ,即触摸屏屏幕上的覆盖输入区域 140 . 可以显示信息并且可以在第一区域中感测触摸输入 911 ,而可以感测到触摸输入但信息可能不会显示在第二区域中 921 . [0122] 参考图。 10、窗口区 1010 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1020 ,以及一个覆盖输入区域 1030 在非窗口区域的一部分定义 1020 窗下区域 1010 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1011 对应窗口区域 1010 和第二个区域 1031对应覆盖输入区域 1030 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1011 ,而在第二区域中可以感测到触摸输入 1031 . 也可以在第一区域中感测到触摸输入 1011 . [0123] 参考图。 11、窗口区 1110 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1120 ,以及一个覆盖输入区域 1130 在非窗口区域的一部分定义 1120 窗下区域 1110 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1111 对应窗口区域 1110 和第二个区域 1131 对应覆盖输入区域 1130 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1111 ,而在第二区域中可以感测到触摸输入 1131 . 也可以在第一区域中感测到触摸输入 1111 . [0124] 参考图。 12、窗口区 1210 定义在前盖单元的右侧 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1220 ,以及一个覆盖输入区域 1230 在非窗口区域的一部分定义 1220 在窗口区域的左侧 1210 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1211 对应窗口区域 1210 和第二个区域 1231 对应覆盖输入区域 1230 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1211 ,而在第二区域中可以感测到触摸输入 1231 . 也可以在第一区域中感测到触摸输入 1211 . [0125] 在本发明的实施例中,可以以各种方式应用触摸输入。 如图。 图13是图示根据本发明实施例的触摸输入的图。 参考图。 参照图13,触摸输入可以包括双击、向上滑动或(String), 111522(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.195 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.196 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.196 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.198 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.199 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.199 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.200 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.201 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.201 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.203 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 11 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.203 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.204 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), AU2015216023A1(String), 1046966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), CN104834353A(String), 1046967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.206 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.206 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.207 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), CN104834353B(String), 1046968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.208 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.208 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.209 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), EP2905681A1(String), 1046969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.210 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.211 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.211 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), EP2905681B1(String), 1046970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.212 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.212 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.213 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), JP2017511919A(String), 1046971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.214 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.214 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.215 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), KR1020150094231A(String), 1046972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.216 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.217 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.217 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), KR102245289B1(String), 1046973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.218 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.218 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.218 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), US10075579B2(String), 1046974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.219 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.219 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.220 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), US20150229754A1(String), 1046975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.221 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.221 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.221 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), WO2015122661A1(String), 1046976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.223 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.223 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.223 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10075579B2(String), US10075579B2(String), 1536595200(Integer), 270634(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.224 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.225 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.226 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.227 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.228 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.228 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.229 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.230 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.230 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.244 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.244 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.244 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.262 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.263 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.263 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.265 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.266 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.266 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184951(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.286 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.287 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.287 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.305 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.306 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.306 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.307 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.307 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.307 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.309 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.309 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.309 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.311 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.312 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.312 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.313 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.314 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.314 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.315 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.316 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.316 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.332 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.333 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.333 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.359 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.361 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.361 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.364 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.365 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.365 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.372 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.373 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.373 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d488590504c2428180b9f6356c214e3b.png(String), 184952(Integer), d488590504c2428180b9f6356c214e3b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.382 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.383 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.383 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.385 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.385 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, mobile terminal auxiliary device and method for controlling the same(String), 移动终端、移动终端辅助装置及其控制方法(String), US9749858B2(String), Methods and apparatuses are provided for controlling a mobile terminal and a mobile terminal auxiliary device. Information on at least one of the mobile terminal and the mobile terminal auxiliary device and security-related information on the at least one of the mobile terminal and the mobile terminal auxiliary device are stored. It is determined whether the mobile terminal and the mobile terminal auxiliary device exist within a predetermined available distance. If the mobile terminal and the mobile terminal auxiliary device exist within the predetermined available distance, it is determined whether the mobile terminal or the mobile terminal auxiliary device has been registered by using the stored information.(String), 提供了一种移动终端的控制方法和装置以及移动终端辅助设备。 存储关于移动终端和移动终端辅助设备至少之一的信息以及关于移动终端和移动终端辅助设备至少之一的安全相关信息。 确定移动终端和移动终端辅助设备是否存在于预定的可用距离内。 如果移动终端和移动终端辅助设备存在于预定可用距离内,则使用存储的信息判断移动终端或移动终端辅助设备是否已经注册。(String), US14/509670(String), 1412697600(Integer), US9749858B2(String), 1503936000(Integer), 1503936000(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 16(Integer), US20020111138A1 | US20080287062A1 | US20110173447A1 | US20120139879A1 | US20120206555A1 | US20120258665A1 | US20120281686A1 | US20120322376A1 | US20130143499A1 | US20130257777A1 | US20140115690A1 | US20140298672A1 | US20140378056A1 | US9154954B2 | US9179310B2 | US9398133B2(String), \20230420\d488590504c2428180b9f6356c214e3b.png(String), 20(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.393 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.394 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.394 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:26.403 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.418 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.419 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 1. A method for controlling a mobile terminal auxiliary device, the method comprising:storing information on at least one mobile terminal and security-related information on each of the at least one mobile terminal;determining whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal; andif the mobile terminal exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile terminal.(String), 1.一种移动终端辅助设备的控制方法,该方法包括:存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;根据移动终端发射的信号强度,判断移动终端是否存在于移动终端辅助设备的预定可用范围内;和如果移动终端在预定可用范围内,则解除移动终端的锁定状态,包括显示锁定图像。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.420 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 2. The method of claim 1, wherein determining whether the mobile terminal exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 2.如权利要求1所述的方法,其中判断移动终端是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端是否在预定可用范围内。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.420 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 3. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;receiving, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal;comparing the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 3.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;从移动终端接收关于触摸信号在移动终端的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端辅助设备的触摸信号的时间进行比较;和如果触摸时间信息与检测到移动终端辅助设备的触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.420 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 4. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;transmitting, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device; andreceiving, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 4.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;和从移动终端接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.421 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 5. The method of claim 1, further comprising:determining whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device; andif the mobile terminal does not exist within the predetermined connection range, deleting information on the mobile terminal.(String), 5.如权利要求1所述的方法,还包括:判断移动终端是否存在于移动终端辅助设备的预定连接范围内;和如果预定连接范围内不存在移动终端,则删除移动终端上的信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.421 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 6. A method for controlling a mobile terminal, the method comprising:storing information on at least one mobile terminal auxiliary device;determining whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device; andif the mobile terminal auxiliary device exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile device.(String), 6.一种移动终端的控制方法,该方法包括:在至少一个移动终端辅助设备上存储信息;根据移动终端辅助设备发送的信号强度判断移动终端辅助设备是否存在于距移动终端预定可用范围内;和如果移动终端辅助设备存在于预定可用范围内,则解除移动设备的锁定状态,包括显示锁定图像。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.421 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 7. The method of claim 6, wherein determining whether the mobile terminal auxiliary device exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal auxiliary device exists within the predetermined available range, when the use signal is detected.(String), 7.如权利要求6所述的方法,其中判断移动终端辅助设备是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.422 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 8. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;receiving, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device;comparing the received touch time information with a time when the touch signal of the mobile terminal is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 8.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端触摸信号的时间进行比较;和若触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.423 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 9. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;transmitting, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal; andreceiving, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 9.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息;和从移动终端辅助设备接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.423 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 10. The method of claim 6, further comprising:determining whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal; andif the mobile terminal auxiliary device does not exist within the predetermined connection range, deleting information on the mobile terminal auxiliary device.(String), 10.如权利要求6所述的方法,还包括:判断移动终端辅助设备是否存在于移动终端的预定连接范围内;和如果预定连接范围内不存在移动终端辅助设备,则删除移动终端辅助设备的信息。11、一种移动终端辅助设备包括:与至少一个移动终端通信的通信单元;存储器,存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;和控制器,基于从移动终端发送的信号的强度确定移动终端是否存在于移动终端辅助设备的预定可用范围内,并且如果是则释放移动终端的锁定状态,包括显示锁定图像移动终端存在于预定的可用范围内。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.424 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 11. A mobile terminal auxiliary device comprising:a communication unit that communicates with at least one mobile terminal;a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal; anda controller that determines whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal exists within the predetermined available range.(String), 12.如权利要求11所述的装置,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端是否存在于预定可用范围内。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.427 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 12. The device of claim 11, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 13.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,从移动终端接收触摸时间信息,检测移动终端触摸信号的时间,将接收到的触摸时间信息与触摸发生的时间进行比较检测到移动终端辅助设备的信号,如果触摸时间信息与检测到移动终端辅助设备触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸设备。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.427 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 13. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, receive, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal, compare the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 14.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,并从移动终端接收触摸时间信息移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.428 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 14. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, transmit, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, and receive, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 15.如权利要求11所述的装置,其中控制器控制判断移动终端是否存在于移动终端辅助设备的预定连接范围内,如果移动终端不存在于预定连接范围内,则删除移动终端上的信息。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.625 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 15. The device of claim 11, wherein the controller controls to determine whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device, and if the mobile terminal does not exist within the predetermined connection range, delete information on the mobile terminal.(String), 16.移动终端包括:通信单元,与至少一个移动终端辅助设备进行通信;存储器,存储关于至少一个移动终端辅助设备的信息;和控制器,基于从移动终端辅助设备发送的信号强度确定移动终端辅助设备是否存在于距移动终端的预定可用范围内,并释放移动终端的锁定状态,包括显示锁定图像如果移动终端辅助设备存在于预定可用范围内,则终端。(String), 1(Integer), 14(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.629 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 16. A mobile terminal comprising:a communication unit that communicates with at least one mobile terminal auxiliary device;a memory that stores information on the at least one mobile terminal auxiliary device; anda controller that determines whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal auxiliary device exists within the predetermined available range.(String), 17.如权利要求16所述的移动终端,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.630 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 17. The mobile terminal of claim 16, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal auxiliary device exists within the predetermined available range when the use signal is detected.(String), 18.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,将接收到的触摸时间信息与触摸时间进行比较。检测到移动终端的触摸信号,如果触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.630 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 18. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, receive, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, compare the received touch time information with a time when the touch signal of the mobile terminal is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 19.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息,并从移动终端辅助设备接收触摸时间信息。移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.631 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 19. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, transmit, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal, and receive, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 20.如权利要求16所述的移动终端,其中控制器判断移动终端辅助设备是否存在于移动终端的预定连接范围内,如果移动终端辅助设备不存在于预定连接范围内,则控制删除关于移动终端辅助设备的信息。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.645 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.646 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 20. The mobile terminal of claim 16, wherein the controller determines whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal, and if the mobile terminal auxiliary device does not exist within the predetermined connection range, controls to delete information on the mobile terminal auxiliary device.(String), 1(Integer), 19(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.922 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.923 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.961 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.961 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.962 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111523(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.972 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.972 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.973 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184952(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to Korean Patent Application No. 10-2013-0119737, filed on Oct. 8, 2013, the content of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal and a mobile terminal auxiliary device, and more particularly, to a control method by which security related functions of the mobile terminal can be executed without an additional authentication process by registration between the mobile terminal and the mobile terminal auxiliary device. [0004]2. Description of the Related Art [0005]Terminals are classified into mobile/portable terminals and stationary terminals according to their mobility. Mobile terminals are divided into handheld terminals and vehicle mount terminals according to whether a user can carry the terminals. [0006]Terminals have been implemented with multimedia players that have multiple functions such as, for example, photographing still images or moving images, reproducing music files or movie files, playing games, receiving broadcasts, or the like. [0007]In order to support and strengthen the functions of the terminals, structures and/or software of the terminals can be improved. [0008]In addition, various terminal auxiliary devices have been used for convenient use of the terminals. Particularly, electronic pens, such as styluses, may be used as terminal auxiliary devices. [0009]The terminal and the pen are connected with each other wirelessly or using a wire, and the terminal receives a user input by using the pen. Therefore, the user can input specific texts, symbols, images, or the like more easily, accurately and faster. [0010]Pens are widely used in the terminals as accessories. Further, with the improvement of technology, the pens can transfer more precise illustrations and designs of a user to electronic devices. [0011]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0012]As shown in FIG. 1A, when a user touches specific contents such as, for example, a memo, a schedule, an email, or a diary, which are displayed in a display unit of a mobile terminal 100, by using a mobile terminal auxiliary device, such as, for example, an electronic pen 150, an operation of pre-viewing the corresponding contents may be executed. The touch of the electronic pen 150 may be performed by a proximity touch and/or a contact touch. [0013]In addition, as shown in FIG. 1B, when the mobile terminal auxiliary device, for example, the electronic pen 150, which is connected with the mobile terminal, is taken out from the mobile terminal while a screen 110 of the mobile terminal is turned off, the mobile terminal may be configured to automatically switch to a locked image 120. Here, the locked image means an image followed by a waiting image in which the mobile terminal can be used. That is, the mobile terminal may wait for instructions for releasing security, such as a password input of a user. When the user inputs the instruction for releasing security, the locked state of the mobile terminal may be released, and the mobile terminal may switch to the waiting image to thereby execute operations thereof. [0014]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0015]Referring to FIG. 2A, in contents 210 such as, for example, a memo, when other people's accesses are restricted through a locking setup by a user, a preview function by the mobile terminal auxiliary device 150 of FIG. 1A may be deactivated. That is, in the case of a memo that is set to be locked, although someone touches the corresponding contents by the mobile terminal auxiliary device, the preview function may not be executed unless the password is entered by the user. [0016]In addition, as shown in FIG. 2B, although a locked image 230 is displayed by taking out the mobile terminal auxiliary device from the mobile terminal while a screen 220 of the mobile terminal is turned off, the terminal may be switched to an available state, i.e., the waiting state, only by inputting the instruction for releasing security, such as by entering the password by the user. [0017]Further, although not shown in the drawings, even while using the mobile terminal by the mobile terminal auxiliary device, for example, the electronic pen, if the mobile terminal does not continuously receive usage instruction inputs, i.e., the touch signal inputs, the screen of the mobile terminal will be turned off soon and the security function will be resumed. [0018]Furthermore, even though the user obtains the authority to access the contents or releases the locked state of the mobile terminal through the security process, if the mobile terminal is not used for a while or it is required to be turned off and then turned on, the user is required to repeat the security process. SUMMARY OF THE INVENTION [0019]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal auxiliary device that may be authenticated through a security process when it is connected with a mobile terminal, so that repetition of the security process may be removed when the mobile terminal auxiliary device is required to be used afterwards, to thereby enhance the usability of the mobile terminal. [0020]Another aspect of the present invention provides convenience in using applications, which can be used only by the process of logging on or releasing a locked state by means of a mobile terminal auxiliary device. [0021]An additional aspect of the present invention prevents a screen of a mobile terminal from being turned off or a locked state from being resumed during the use of the mobile terminal, by continuously checking the use of the mobile terminal using a low power technology without an additional operation of a mobile terminal auxiliary device. [0022]A further aspect of the present invention allows, when a user wishes to use each of a plurality of mobile terminals, or authentication is required, the user to control each mobile terminal by the authenticated mobile terminal auxiliary device and use the mobile terminal without the security checking process to thereby provide convenient use thereof. [0023]Another aspect of the present invention allows each mobile terminal to identify the user through the corresponding mobile terminal auxiliary device, and a UI of the mobile terminal to be configured with specific values predefined according to the setup or user's desire. [0024]In accordance with an aspect of the present invention, a method is provided for controlling a mobile terminal auxiliary device. Information on at least one mobile terminal and security-related information on each of the at least one mobile terminal are stored. It is determined whether a mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device. If the mobile terminal exists within the predetermined available distance, it is determined whether the mobile terminal has been registered by using the stored information on the at least one mobile terminal. If the mobile terminal has been registered, security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, is transmitted to the mobile terminal. [0025]In accordance with another aspect of the present invention, a method is provided for controlling a mobile terminal. Information on at least one mobile terminal auxiliary device is stored. It is determined whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal. If the mobile terminal auxiliary device exists within the predetermined available distance, it is determined whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device. If the mobile terminal auxiliary device has been registered, predetermined security-related information is applied according to the mobile terminal auxiliary device. [0026]In accordance with another aspect of the present invention, a mobile terminal auxiliary device is provided that includes a communication unit that communicates with at least one mobile terminal, and a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal. The mobile terminal auxiliary device also includes a controller that determines whether the mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device, determines whether the mobile terminal has been registered by using the stored information on at least one mobile terminal if the mobile terminal exists within the predetermined available distance, and controls the communication unit to transmit security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, to the mobile terminal, if the mobile terminal has been registered. [0027]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a communication unit that communicates with at least one mobile terminal auxiliary device, and a memory that stores information on the at least one mobile terminal auxiliary device. The mobile terminal also includes a controller that determines whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal, determines whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device if the mobile terminal auxiliary device exists within the predetermined available distance, and controls to apply predetermined security-related information according to the mobile terminal auxiliary device if the mobile terminal auxiliary device has been registered. BRIEF DESCRIPTION OF THE DRAWINGS [0028]The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0029]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0030]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0031]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention; [0032]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention; [0033]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention; [0034]FIG. 6 is a flowchart illustrating the operation of a mobile terminal auxiliary device, according to an embodiment of the present invention; [0035]FIG. 7 is a flowchart illustrating the operation of a mobile terminal, according to an embodiment of the present invention; [0036]FIGS. 8A and 8B are diagrams illustrating registration between a mobile terminal and a mobile terminal auxiliary device and the operation thereof, according to an embodiment of the present invention; [0037]FIGS. 9A and 9B are diagrams illustrating an available distance, according to an embodiment of the present invention; [0038]FIG. 10 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to an embodiment of the present invention; [0039]FIG. 11 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to another embodiment of the present invention; [0040]FIG. 12 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in used by a mobile terminal, according to an embodiment of the present invention; [0041]FIG. 13 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by a mobile terminal, according to another embodiment of the present invention; [0042]FIGS. 14A-14C are diagrams illustrating a determination of whether a mobile terminal auxiliary device has been used, according to an embodiment of the present invention; [0043]FIGS. 15A-15D are diagrams illustrating uses of mobile terminals and mobile terminal auxiliary devices, according to an embodiment of the present invention; [0044]FIG. 16 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal auxiliary device and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0045]FIG. 17 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0046]FIG. 18 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to an embodiment of the present invention; and [0047]FIG. 19 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to another embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0048]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0049]Hereinafter, a mobile terminal associated with the present invention will be described in detail with reference to drawings. The suffixes of component elements used in the following descriptions, such as, a “module” and a “unit”, are assigned or used together only for ease of description, but they do not have distinguishing meanings or roles. [0050]A mobile terminal described in the embodiments of the present invention may be embodied as a portable phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation terminal, and the like. However, it is apparent to those skilled in the art that a configuration according to embodiments of the present invention are also applied to a stationary terminal such as, for example, a digital TV, a desktop computer, and the like. [0051]Mobile terminal auxiliary devices of the embodiments of the present invention may include electronic pens, such as styluses, which can communicate with a mobile terminal. In addition, it is obvious for those skilled in the art that the mobile terminal auxiliary devices of the present invention may be applied to stationary terminals such as TVs, desktop computers, or the like, as well as the mobile terminals. [0052]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention. [0053]A mobile terminal auxiliary device 300 includes a communication unit 310, a memory 320, and a controller 330. The mobile terminal auxiliary device is not limited to the elements of FIG. 3, and it may further include other elements, or some of the elements may be omitted. For example, the mobile terminal auxiliary device 300 may further include an output unit, such as, for example, an audio output module, an alarm unit, and a display unit, and a user input unit for receiving a user input. [0054]The communication unit 310 may include at least one module enabling wireless communication between the mobile terminal auxiliary device 300 and a mobile terminal. For example, the communication unit 310 may include a short-range communication module for near field communication. Here, the short-range communication technology may adopt Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra wideband (UWB), ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a Bluetooth (BT) module and a Bluetooth low energy (BLE) module. [0055]The communication unit 310 may allow the mobile terminal auxiliary device 300 and the mobile terminal to register with each other by communicating with the mobile terminal, as described in greater detail below. [0056]The memory 320 may store programs for processing and controlling of the controller 330 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like). The memory 320 may store frequency of use for the data. [0057]The memory 320 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., a secure digital (SD) memory, an XD memory, or the like), a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a programmable ROM (PROM), a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal auxiliary device 300 may operate in relation to a web storage for providing a storage function of the memory 320 on the Internet. [0058]In general, the controller 330 controls overall operations of the mobile terminal auxiliary device 300. For example, the controller 330 may control to perform an operation of registering the mobile terminal auxiliary device 300 and the mobile terminal with each other. In addition, in the case of using the mobile terminal auxiliary device 300 through authentication between the mobile terminal and the mobile terminal auxiliary device 300, the controller 330 may control to use the mobile terminal without an additional security checking process, which is described in greater detail below. [0059]The mobile terminal auxiliary device 300 may further include a user input unit. The user input unit generates input data for controlling operations of the mobile terminal auxiliary device by a user. The user input unit may include at least one of buttons provided on the front, back, or side surface of the mobile terminal auxiliary device, touch sensors (a pressure type/a capacitive type), keypads, dome switches, jog wheels, jog switches, or the like, but it is not limited thereto. [0060]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention. [0061]The mobile terminal auxiliary device, according to an embodiment of the present invention, may be embodied as an electronic pen 400, such as a stylus. The electronic pen 400 includes a communication unit 410, a memory 420, a controller 430, a touch recognition unit 440, and the like, but it is not limited thereto. For example, the electronic pen 400 may further include a power supply, such as a battery 450, and the power supply may receive external power and internal power to be supplied to each element to operate under the control of the controller 430. The power supply may include at least one of connection ports, a power supply controller, and a charge monitoring unit, as well as the battery 450. [0062]The communication unit 410 may include at least one module enabling wireless communication between the electronic pen 400 and a mobile terminal. According to an embodiment of the present invention, the communication unit 410 may include at least one of a BT module or a BLE module. [0063]The communication unit 410 may allow the electronic pen 400 and the mobile terminal to be registered with respect to each other by communicating with the mobile terminal, as described in greater detail below. [0064]The memory 420 may store programs for processing and controlling of the controller 430 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like), as described in detail above. [0065]In general, the controller 430 controls overall operations of the electronic pen 400. For example, the controller 430 may control to perform an operation of registering the electronic pen 400 and the mobile terminal with each other. In addition, in the case of using the electronic pen 400 through authentication between the mobile terminal and the electronic pen 400, the controller 430 may control to use the mobile terminal without an additional security checking process, as described in detail below. [0066]The touch recognition unit 440 may recognize touch signals of the electronic pen 400. When the touch signal of the electronic pen 400 is input, the controller 430 controls to perform a predetermined operation according to the touch signal input. According to an embodiment of the present invention, in addition to the touch recognition unit 440, the electronic pen 400 may further include a user input unit for generating input data of a user. The user input unit may include at least one of buttons provided on the side surface of the electronic pen, a keypad, a dome switch, a jog wheel, a jog switch, or the like, but it is not limited thereto. [0067]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention. [0068]A mobile terminal 500 includes a communication unit 510, a memory 520, a controller 530, a user input unit 540, and an output unit 550. The elements shown in FIG. 5 are not essential to the mobile terminal, and the mobile terminal may further include other elements, or some of the elements may be omitted. [0069]The communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and a wireless communication system, or the mobile terminal 500 and a network where the mobile terminal 500 is located. In addition, the communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and the mobile terminal auxiliary device. For example, the communication unit 510 may include a broadcast receiving module, a mobile communication module, a wireless Internet module, a short-range communication module, a location information module, and the like. [0070]The broadcast receiving module receives broadcast signals and/or broadcast-related information from external broadcast management servers through broadcasting channels. The broadcasting channels may include a satellite channel and a ground wave channel. At least two broadcast receiving modules may be provided in the mobile terminal 500 to concurrently receive broadcasts through at least two broadcasting channels or to switch between at least two broadcasting channels. [0071]The mobile communication module transmits and receives wireless signals to and from at least one of base stations, other terminals, and servers in mobile communication networks, such as, for example, global system for mobile communication (GSM), code division multiple access (CDMA), wideband CDMA (WCDMA) (but not limited thereto). The wireless signals may include voice call signals, video call signals, or various data according to transmission and reception of text/multimedia messages. [0072]The wireless Internet module for connecting the wireless Internet may be built in the mobile terminal 500 or externally provided. The wireless Internet may utilize the technologies of wireless LAN (WLAN), Wi-Fi, wireless broadband (Wibro), world interoperability for microwave access (Wimax), high speed downlink packet access (HSDPA), GSM, CDMA, WCDMA, long term evolution (LTE), or the like. [0073]The wireless Internet connection through Wibro, HSDPA, GSM, CDMA, WCDMA, and LTE is made by wireless mobile communication networks. Accordingly, the wireless Internet module that connects with the wireless Internet through the mobile communication networks may be regarded as a type of mobile communication module. [0074]The short-range communication module refers to a module for near field communication. The short-range communication technology may adopt BT, RFID, IrDA, UWB, ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a BT module and a BLE module. [0075]The user input unit 540 generates input data for controlling operations of the mobile terminal by a user. The user input unit 540 may include buttons 543 on the front, back or side surface of the mobile terminal 500, and a touch sensor (a pressure type/a capacitive type) 545. The user input unit 540 may further include keypads, dome switches, jog wheels, jog switches, or the like. [0076]The output unit 550 may generate outputs related to a sense of sight, a sense of hearing, or a sense of touch, and includes a display unit 555, but it is not limited thereto. For example, the output unit 550 may include an audio output module, an alarm module, and a haptic module. [0077]The display unit 555 displays (outputs) information processed in the mobile terminal 500. For example, when the mobile terminal 500 is in a phone call mode, the display unit 555 displays a user interface (UI) or a graphic user interface (GUI) related to the phone call. When the mobile terminal 500 is in a video call mode or photographing mode, the display unit 555 displays images, which are photographed and/or received, using the UI or the GUI. [0078]The display unit 555 may include at least one of a liquid crystal display (LCD), a thin film transistor-LCD (TFT LCD), an organic light-emitting diode (OLED), a flexible display, and a 3D display. [0079]Some of the above displays may be configured to be transparent or light-penetrable in order to view the outside therethrough, which are called transparent displays, typically, including transparent OLEDs (TOLEDs). The back structure of the display unit 555 may be also configured to be light-penetrable. According to the above structure, a user can see objects behind the terminal through the area of the display unit 555 of the terminal. [0080]Two or more display units 555 may be provided according to the type of mobile terminal 500. For example, a plurality of display units may be arranged to be spaced from each other or to be integral on the same plane, or may be disposed on different planes in the mobile terminal 500. [0081]In the case of the display unit 555 and the touch sensor 545, which are formed in a layer structure or integrally (hereinafter, referred to as a “touch screen”), the display unit 555 may be used as the input device as well as the output device. The touch sensor may be formed to be a laminate with the display unit 555 in the case of, for example, touch films, touch sheets, touch pads, or the like, or may be integrally formed with the display unit 555. [0082]The touch sensor may be configured to convert the change of pressure acting on the specific portion of the display unit 555 or the change of capacitance generating on the specific portion of the display unit 555 to electric signals. The touch sensor may be configured to detect the touch pressure as well as the touch point and the touch area. [0083]Upon a touch input on the touch sensor, the corresponding signals are transmitted to a touch controller. The touch controller processes the signals and transmits the corresponding data to the controller 530. Accordingly, the controller 530 may recognize which area of the display unit 555 has been touched. [0084]Although not shown in the drawing, a proximity sensor may be disposed inside or around the touch screen of the mobile terminal 500. The proximity sensor may detect objects approaching a predetermined detection surface, or objects around the proximity sensor, by using an electromagnetic field force or an infrared ray without mechanical contacts. The proximity sensor has a long life span and various utilization compared to a contact type sensor. [0085]The proximity sensor may include a transparent photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillating proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor an infrared proximity sensor, or the like. [0086]Hereinafter, for convenience of explanation, the term “proximity touch” may refer to an operation in which a pointer approaches the touch screen where the proximity sensor is installed to be thereby recognized without a contact, and the term “contact touch” may refer to an operation of touching of the pointer on the screen. A proximity touch point of the pointer on the touch screen may denote the point on the screen which vertically corresponds to the location of the pointer in the state of the proximity touch. Hereinafter, the term “touch” may encompass the proximity touch as well as the contact touch. [0087]According to an embodiment of the present invention, the proximity touch may include a hovering input. [0088]The proximity sensor detects the proximity touch and a proximity touch pattern (e.g., a proximity touch distance, a proximity touch direction, a proximity touch speed, a proximity touch time, a proximity touch point, a proximity touch movement state, or the like). Information corresponding to the detected proximity touch and the proximity touch pattern may be displayed on the touch screen. [0089]The memory 520 may store programs for processing and controlling of the controller 530 and perform a function of temporarily storing input/output data (e.g., a telephone number list, messages, audio, still images, moving images, information on the mobile terminal, identification information on the mobile terminal, information on the mobile terminal auxiliary device, security related information, or the like). The memory 520 may store frequency of use for the data. [0090]In addition, the memory 520 may store data on various vibrations and sounds, which are output upon the touch input on the touch screen. [0091]The memory 520 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD memory, an XD memory, or the like), a RAM, an SRAM, a ROM, an EEPROM, a PROM, a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal 500 may operate in relation to a web storage for providing a storage function of the memory 520 on the Internet. [0092]The mobile terminal 500 may further include an audio/video (A/V) input unit for inputting audio signals or video signals, and a sensing unit for generating sensing signals to sense the current state of the mobile terminal 500, such as, for example, the opening/closing state of the mobile terminal 500, the location of the mobile terminal 500, contact of users, directions of the mobile terminal, and acceleration/deceleration of the mobile terminal, and to thereby control operations of the mobile terminal 500. [0093]In addition, the mobile terminal 500 may include an interface unit that plays a role of a path for all external devices connected with the mobile terminal 500. The interface unit receives data or power from the external devices and transfers the same to each element of the mobile terminal 500. The interface unit also allows data to be transmitted to the external devices from the mobile terminal 500. For example, the interface unit may include a wireless/wired headset port, an external charge port, a wireless/wired data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, or the like. [0094]In addition, the mobile terminal 500 may further include a power supply that receives external power and internal power and supplies the same to each element for operations under the control of the controller(String), 优先 [0001] 本申请根据 35 U.S.C. 要求优先权 2013 年 10 月 8 日提交的韩国专利申请号 10-2013-0119737 的 §119(a),其内容通过引用并入本文。 发明背景 [0002] 一、发明领域 [0003] [0001] 本发明总体上涉及移动终端和移动终端辅助设备,并且更具体地,涉及一种控制方法,通过该方法可以执行移动终端的安全相关功能而无需通过移动终端和移动终端之间的注册的附加认证过程 终端辅助设备。 [0004] 二、相关技术说明 [0005] 终端根据其移动性分为移动/便携终端和固定终端。 移动终端根据用户是否可以携带终端分为手持终端和车载终端。 [0006] 终端已经实现了具有多种功能的多媒体播放器,例如拍摄静止图像或运动图像、再现音乐文件或电影文件、玩游戏、接收广播等。 [0007] 为了支持和加强终端的功能,可以改进终端的结构和/或软件。 [0008] 此外,为了方便终端的使用,还使用了各种终端辅助设备。 特别地,电子笔,例如手写笔,可以用作终端辅助设备。 [0009] 终端和笔通过无线或有线方式相互连接,终端通过笔接收用户输入。 因此,用户可以更方便、更准确、更快速地输入特定的文字、符号、图像等。 [0010] 笔作为配件广泛应用于终端。 此外,随着技术的进步,笔可以将用户更精确的插图和设计转移到电子设备上。 [0011] 图1A和1B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0012] 如图1A所示,当用户触摸移动终端的显示单元中显示的特定内容,例如备忘录、日程、电子邮件或日记时 100 ,通过使用移动终端辅助设备,例如电子笔 150 ,可以执行预览相应内容的操作。 电子笔的触感 150 可以通过接近触摸和/或接触触摸来执行。 [0013] 另外,如图1B所示,当移动终端辅助设备,例如电子笔 150 ,与移动终端连接,从移动终端中取出,同时屏幕 110 关闭移动终端,移动终端可配置为自动切换到锁定图像 120 . 这里,锁定图像是指跟随有移动终端可以使用的等待图像的图像。 也就是说,移动终端可以等待解除安全的指令,例如用户的密码输入。 当用户输入解锁指令时,可以解除移动终端的锁定状态,移动终端可以切换到等待画面,从而执行其操作。 [0014] 图2A和2B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0015] 参考图2A,在内容 210 例如备忘录,当用户通过锁定设置限制他人访问时,移动终端辅助设备的预览功能 150 可以停用图1A的。 也就是说,在设置为锁定的备忘录的情况下,即使有人通过移动终端辅助设备触摸了相应的内容,也可能无法执行预览功能,除非用户输入密码。 [0016] 此外,如图 2B 所示,虽然锁定图像 230 通过从移动终端中取出移动终端辅助设备来显示,同时屏幕 220移动终端关机后,用户只需输入解除安全的指令,如输入密码,即可将终端切换到可用状态,即等待状态。 [0017] 此外,虽然未在附图中示出,但是即使在通过移动终端辅助设备例如电子笔使用移动终端时,如果移动终端没有持续接收到使用指令输入,即触摸信号输入,则屏幕 移动终端的 将很快关闭并恢复安全功能。 [0018] 进一步地,即使用户通过安全过程获得了访问内容的权限或者解除了移动终端的锁定状态,如果移动终端暂时不使用或者需要关机再开机, 用户需要重复安全过程。 发明内容 [0019] 做出本发明以至少解决上述问题和/或缺点并且提供至少下述优点。 相应地,本发明的一个方面提供了一种移动终端辅助设备,在与移动终端连接时,可以通过安全流程进行认证,从而在需要移动终端辅助设备时,可以免去重复的安全流程。 之后使用,从而提高移动终端的可用性。 [0020] 本发明的另一个方面提供了使用应用程序的便利性,仅通过移动终端辅助设备登录或解除锁定状态的过程就可以使用这些应用程序。 [0021] 本发明的另一方面通过使用低功率技术持续检查移动终端的使用而无需额外的额外的,防止移动终端的屏幕在移动终端的使用期间被关闭或锁定状态被恢复 移动终端辅助设备的操作。 [0022] 本发明的另一方面允许,当用户希望使用多个移动终端中的每一个,或者需要认证时,用户通过认证的移动终端辅助设备控制每个移动终端并且在没有安全性的情况下使用移动终端 检查过程,从而提供方便的使用。 [0023] 本发明的另一个方面允许每个移动终端通过相应的移动终端辅助设备来识别用户,并且移动终端的UI被配置有根据设置或用户期望预定义的特定值。 [0024] 根据本发明的一方面,提供了一种移动终端辅助设备的控制方法。 存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息。 判断移动终端辅助设备在预定可用距离内是否存在移动终端。 如果移动终端存在于预定可用距离内,则利用存储的至少一个移动终端的信息判断移动终端是否已经注册。 如果移动终端已经注册,则从存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息被发送到移动终端。 [0025] 根据本发明的另一方面,提供了一种用于控制移动终端的方法。 存储至少一个移动终端辅助设备的信息。 判断移动终端的预定可用距离内是否存在移动终端辅助设备。 如果移动终端辅助设备存在于预定可用距离内,则通过至少一个移动终端辅助设备的信息判断移动终端辅助设备是否已经注册。 如果移动终端辅助设备已经注册,则根据移动终端辅助设备应用预定的安全相关信息。 [0026]根据本发明的另一个方面,提供了一种移动终端辅助设备,包括与至少一个移动终端通信的通信单元,以及存储关于至少一个移动终端的信息和关于移动终端的安全相关信息的存储器。 每个至少一个移动终端。 移动终端辅助设备还包括控制器,判断移动终端是否存在于距离移动终端辅助设备的预定可用距离内,如果移动终端是移动终端,则使用存储在至少一个移动终端上的信息判断移动终端是否已经注册。 终端存在于预定可用距离内,并且控制通信单元将存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息发送到移动终端,如果移动终端具有 已注册。 [0027] 根据本发明的另一方面,提供了一种移动终端,包括与至少一个移动终端辅助设备通信的通信单元,以及存储关于至少一个移动终端辅助设备的信息的存储器。 移动终端还包括控制器,确定移动终端辅助设备是否存在于距移动终端的预定可用距离内,如果是,则使用关于至少一个移动终端辅助设备的信息确定移动终端辅助设备是否已经注册。 移动终端辅助设备存在于预定可用距离内,如果移动终端辅助设备已经注册,则根据移动终端辅助设备控制应用预定安全相关信息。 附图的简要说明 [0028] [0010] 结合附图,通过以下详细描述,本发明的上述和其他方面、特征和优点将更加明显,其中: [0029] 图1A和1B是说明通过使用移动终端辅助设备来操作移动终端的图; [0030] 图2A和2B是说明通过使用移动终端辅助设备来操作移动终端的图; [0031] 图3是示出根据本发明实施例的移动终端辅助设备的框图; [0032] 图4是示出根据本发明实施例的电子笔的框图; [0033] 图5是示出根据本发明实施例的移动终端的框图; [0034] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图; [0035] 图7是示出根据本发明实施例的移动终端的操作的流程图; [0036] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的示图; [0037] 图9A和9B是说明根据本发明实施例的可用距离的图; [0038] 图10是本发明一个实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0039] 图11是本发明另一实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0040] 图12是示出根据本发明实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0041] 图13是示出根据本发明另一实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0042]图14A-14C是根据本发明实施例的判断移动终端辅助设备是否被使用的示意图。 [0043] 图15A-15D是图示根据本发明的实施例的移动终端和移动终端辅助设备的使用的图; [0044] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0045] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0046] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图; 和 [0047] 图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 本发明实施例的详细描述 [0048] 下面结合附图详细描述本发明的实施例。 相同或相似的组件可由相同或相似的附图标记指示,尽管它们在不同的附图中示出。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0049] 在下文中,将参考附图详细描述与本发明相关联的移动终端。 下文描述中所使用的组成元件的后缀,例如“模块”、“单元”,只是为了描述的方便而指定或一起使用,并不具有区分的含义或作用。 [0050] 本发明实施例中描述的移动终端可以实现为便携式电话、智能电话、膝上型计算机、数字广播终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、导航仪 终端等。 然而,对于本领域技术人员显而易见的是,根据本发明的实施例的配置也适用于固定终端,例如数字电视、台式计算机等。 [0051] 本发明实施例的移动终端辅助设备可以包括可以与移动终端通信的电子笔,例如手写笔。 另外,对于本领域技术人员来说显而易见的是,本发明的移动终端辅助装置可以应用于电视、台式电脑等固定终端,也可以应用于移动终端。 [0052] 图3是图示根据本发明实施例的移动终端辅助设备的框图。 [0053] 一种移动终端辅助设备 300 包括一个通信单元 310 , 一段记忆 320 , 和一个控制器 330 . 移动终端辅助设备不限于图3中的元件,还可以包括其他元件,或者可以省略部分元件。 例如移动端辅助设备 300 还可以包括输出单元,例如音频输出模块、警报单元和显示单元,以及用于接收用户输入的用户输入单元。 [0054] 通信单元 310 可以包括至少一个实现移动终端辅助设备之间无线通信的模块 300 和移动终端。 例如,通信单元 310可以包括用于近场通信的短程通信模块。 这里,短距离通信技术可以采用蓝牙、射频识别(RFID)、红外数据协会(IrDA)、超宽带(UWB)、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是蓝牙(BT)模块和蓝牙低功耗(BLE)模块中的至少一种。 [0055] 通信单元 310 可允许移动终端辅助设备 300 移动终端通过与移动终端通信相互注册,如下面更详细的描述。 [0056] 记忆 320 可以存储用于控制器处理和控制的程序 330 并执行暂时存储输入/输出数据(例如,移动终端信息、移动终端识别信息、移动终端辅助设备识别信息、安全相关信息等)的功能。 记忆 320 可以存储数据的使用频率。 [0057] 记忆 320 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,安全数字(SD)存储器、XD存储器等)、随机存储器的至少一种存储介质 存取存储器(RAM)、静态随机存取存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁存储器、磁盘和光盘 . 移动终端辅助设备 300 可关于网络存储操作以提供存储器的存储功能 320 在网上。 [0058] 一般来说,控制器 330 控制移动终端辅助设备的整体操作 300 . 例如,控制器 330 可以控制执行注册移动终端辅助设备的操作 300 和移动终端相互连接。 另外,在使用移动终端辅助设备的情况下 300 通过移动终端与移动终端辅助设备之间的鉴权 300 , 控制器 330 可以控制使用移动终端而无需额外的安全检查过程,这在下面更详细地描述。 [0059] 移动终端辅助设备 300 还可以包括用户输入单元。 用户输入单元生成用于控制用户对移动终端辅助设备的操作的输入数据。 用户输入单元可以包括设置在移动终端辅助设备的前表面、后表面或侧表面上的按钮、触摸传感器(压力型/电容型)、小键盘、圆顶开关、滚轮、滚轮中的至少一个 等,但不限于此。 [0060] 图4是示出根据本发明实施例的电子笔的框图。 [0061] 根据本发明实施例的移动终端辅助设备可以具体化为电子笔 400 ,例如手写笔。 电子笔 400 包括一个通信单元 410 , 一段记忆 420 , 一个控制器 430 , 一个触摸识别单元 440 等,但不限于此。 例如,电子笔 400 还可以包括电源,例如电池 450 ,电源可以接收外部电源和内部电源供应给每个元件以在控制器的控制下运行 430 . 电源可以包括连接端口、电源控制器和充电监控单元中的至少一个,以及电池 450 . [0062] 通信单元 410 可包括至少一个模块,使电子笔之间能够进行无线通信 400 和移动终端。 根据本发明的一个实施例,通信单元 410 可以包括BT模块或BLE模块中的至少一个。 [0063] 通信单元 410 可以让电子笔 400移动终端通过与移动终端通信进行相互注册,如下面更详细的描述。 [0064] 记忆 420 可以存储用于控制器处理和控制的程序 430 并执行临时存储输入/输出数据(例如,关于移动终端的信息、关于移动终端的标识信息、关于移动终端辅助设备的标识信息、安全相关信息等)的功能,如上文详细描述的 . [0065] 一般来说,控制器 430 控制电子笔的整体操作 400 . 例如,控制器 430 可控制执行注册电子笔的操作 400 和移动终端相互连接。 另外,在使用电子笔的情况下 400 通过移动终端与电子笔之间的认证 400 , 控制器 430 可以控制使用移动终端而无需额外的安全检查过程,如下面详细描述的。 [0066] 触摸识别单元 440 可以识别电子笔的触摸信号 400 . 当电子笔的触摸信号 400 是输入,控制器 430 控制根据触摸信号输入执行预定操作。 根据本发明的一个实施例,除了触摸识别单元 440 , 电子笔 400 还可以包括用于生成用户的输入数据的用户输入单元。 用户输入单元可包括设置在电子笔的侧面上的按钮、小键盘、圆顶开关、滚轮、滚轮开关等中的至少一个,但不限于此。 [0067] 图5是图示根据本发明实施例的移动终端的框图。 [0068] 移动终端 500 包括一个通信单元 510 , 一段记忆 520 , 一个控制器 530 , 一个用户输入单元 540 , 和一个输出单元 550 . 图5所示的元件不是移动终端所必需的,移动终端还可以包括其他元件,或者可以省略一些元件。 [0069] 通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 和无线通信系统,或移动终端 500 以及移动终端所在的网络 500 位于。 此外,通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 以及移动终端辅助设备。 例如,通信单元 510 可以包括广播接收模块、移动通信模块、无线上网模块、近距离通信模块、位置信息模块等。 [0070] 广播接收模块通过广播频道从外部广播管理服务器接收广播信号和/或广播相关信息。 广播频道可以包括卫星频道和地面波频道。 移动终端中可以设置至少两个广播接收模块 500 通过至少两个广播频道同时接收广播或者在至少两个广播频道之间切换。 [0071] 移动通信模块向移动通信网络(例如全球移动通信系统(GSM)、码分多址(CDMA) )、宽带码分多址(WCDMA)(但不限于此)。 根据文本/多媒体消息的发送和接收,无线信号可以包括语音呼叫信号、视频呼叫信号或各种数据。 [0072] 移动终端中可以内置无线上网模块,用于连接无线上网 500或外部提供。 无线互联网可能利用无线局域网(WLAN)、Wi-Fi、无线宽带(Wibro)、全球微波接入互操作性(Wimax)、高速下行链路分组接入(HSDPA)、GSM、CDMA、WCDMA、长期 演进(LTE)等。 [0073] 通过 Wibro、HSDPA、GSM、CDMA、WCDMA 和 LTE 的无线互联网连接是由无线移动通信网络实现的。 因此,通过移动通信网络与无线互联网连接的无线互联网模块可以被认为是一种移动通信模块。 [0074] 近距离通信模块是指用于近场通信的模块。 短距离通信技术可以采用BT、RFID、IrDA、UWB、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是BT模块和BLE模块中的至少一种。 [0075] 用户输入单元 540 生成用于控制用户对移动终端的操作的输入数据。 用户输入单元 540 可能包括按钮 543 在移动终端的正面、背面或侧面 500 和触摸传感器(压力式/电容式) 545 . 用户输入单元 540 还可以包括小键盘、圆顶开关、滚轮、滚轮等。 [0076] 输出单元 550 可以产生与视觉、听觉或触觉相关的输出,并且包括显示单元 555 ,但不限于此。 例如,输出单元 550 可以包括音频输出模块、警报模块和触觉模块。 [0077] 显示单元 555 显示(输出)移动端处理的信息 500 . 例如,当移动端 500 处于通话模式时,显示单元 555 显示与电话呼叫相关的用户界面 (UI) 或图形用户界面 (GUI)。 当移动端 500 处于视频通话模式或拍照模式时,显示单元 555 使用 UI 或 GUI 显示拍摄和/或接收的图像。 [0078] 显示单元 555 可以包括液晶显示器(LCD)、薄膜晶体管-LCD(TFT LCD)、有机发光二极管(OLED)、柔性显示器和3D显示器中的至少一种。 [0079] 上述显示器中的一些可以被配置为透明或透光的以通过其观察外部,这被称为透明显示器,典型地包括透明有机发光二极管(TOLED)。 显示单元背面结构 555 也可以配置为透光的。 根据上述结构,用户可以通过显示单元的区域看到终端后面的物体。 555 终端。 [0080] 两个或多个显示单元 555 可根据移动终端类型提供 500 . 例如,多个显示单元可以相互间隔设置,也可以一体设置在同一平面上,也可以设置在移动终端的不同平面上。 500 . [0081] 在显示单元的情况下 555 和触摸传感器 545 ,它们以层结构或一体形成(以下称为“触摸屏”),显示单元 555 既可以作为输入设备,也可以作为输出设备。 触摸传感器可以形成为与显示单元的层压体 555 在例如触摸膜、触摸片、触摸板等的情况下,或者可以与显示单元一体形成 555 . [0082] 触摸传感器可以被配置为转换作用在显示单元的特定部分上的压力变化 555 或显示单元特定部分产生的电容变化 555 到电信号。 触摸传感器可以被配置为检测触摸压力以及触摸点和触摸面积。 [0083]在触摸传感器上有触摸输入时,相应的信号被传输到触摸控制器。 触摸控制器处理信号并将相应的数据传输给控制器 530 . 因此,控制器 530 可以识别显示单元的哪个区域 555 被感动了。 [0084] 虽然未在图中示出,但是接近传感器可以设置在移动终端的触摸屏内部或周围 500 . 接近传感器可以在没有机械接触的情况下通过使用电磁场力或红外线来检测接近预定检测表面的物体或接近传感器周围的物体。 与接触式传感器相比,接近传感器具有较长的使用寿命和多种用途。 [0085] 接近传感器可以包括透明光电传感器、直接反射光电传感器、镜面反射光电传感器、高频振荡接近传感器、电容式接近传感器、磁性接近传感器、红外接近传感器等。 [0086] 在下文中,为了便于解释,术语“接近触摸”可以指指针接近安装有接近传感器的触摸屏从而在没有接触的情况下被识别的操作,术语“接触触摸”可以指代 指针在屏幕上的触摸操作。 指针在触摸屏上的接近触摸点可以表示接近触摸状态下指针在屏幕上垂直对应的位置的点。 在下文中,术语“触摸”可以包括接近触摸以及接触触摸。 [0087] 根据本发明的实施例,接近触摸可以包括悬停输入。 [0088] 接近传感器检测接近触摸和接近触摸模式(例如,接近触摸距离、接近触摸方向、接近触摸速度、接近触摸时间、接近触摸点、接近触摸移动状态等) . 可以在触摸屏上显示与检测到的接近触摸和接近触摸模式相对应的信息。 [0089] 记忆 520 可以存储用于控制器处理和控制的程序 530 并执行临时存储输入/输出数据(例如,电话号码列表、消息、音频、静止图像、运动图像、关于移动终端的信息、关于移动终端的识别信息、关于移动终端辅助设备的信息、 安全相关信息等)。 记忆 520 可以存储数据的使用频率。 [0090] 此外,内存 520 可以存储关于在触摸屏上的触摸输入时输出的各种振动和声音的数据。 [0091] 记忆 520 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,SD存储器、XD存储器等)、RAM、SRAM的至少一种存储介质, ROM、EEPROM、PROM、磁存储器、磁盘和光盘。 手机端 500 可关于网络存储操作以提供存储器的存储功能 520 在网上。 [0092] 手机端 500 还可以包括用于输入音频信号或视频信号的音频/视频(A/V)输入单元,以及用于产生感测信号以感测移动终端的当前状态的感测单元 500 ,例如,移动终端的打开/关闭状态 500 , 移动端的位置 500 、用户的接触、移动终端的方向、移动终端的加减速,从而控制移动终端的操作 500 . [0093] 此外,移动端 500 可以包括接口单元,该接口单元为与移动终端连接的所有外部设备起到通路的作用 500 . 接口单元从外部设备接收数据或电源,并将其传输到移动终端的每个元素 500. 接口单元还允许数据从移动终端传输到外部设备 500 . 例如,接口单元可以包括无线/有线耳机端口、外部充电端口、无线/有线数据端口、存储卡端口、用于连接具有识别模块的设备的端口、音频输入/输出端口(I /O)端口、视频I/O端口、耳机端口等。 [0094] 此外,移动端 500 还可以包括电源,其接收外部电源和内部电源并将其提供给每个元件以在控制器的控制下运行 530 . 电源可以包括例如电池、连接端口、电源控制器和充电监控单元。 [0095] 电池可以是可充电的内置型,并且可以结合到终端的主体以可拆卸地充电。 连接端口可以是外部充电器电连接到的接口之一,以便提供用于电池充电的电力。 [0096] 上述实施例可以通过使用例如软件、硬件或其组合由计算机可读或等效介质来实现。 [0097] 在硬件方面,本发明实施例可以采用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理器件(DSPD)、可编程逻辑器件(PLD)中的至少一种来实现, 现场可编程门阵列 (FPGA)、处理器、控制器、微控制器、微处理器或用于执行其他功能的电气单元。 本发明的一些实施例可以通过控制器来实现 530 . [0098] 在软件方面,本发明实施例的流程和功能可以通过单独的软件模块来实现。 每个软件模块可以执行这里描述的至少一个功能和操作。 软件代码可以由合适的程序语言编写的软件应用程序来实现。 软件代码可以存储在内存中 520 并且可以由控制器执行 530 . [0099] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图。 [0100] 参见图6,在步骤 610 ,移动终端辅助设备的控制器控制将至少一个移动终端的信息存储在存储器中。 即,移动终端辅助设备通过移动终端辅助设备与移动终端之间的注册,存储有至少一个要使用该移动终端辅助设备的移动终端的信息。 当用户试图通过使用移动终端辅助设备连接已注册的移动终端时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0101] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0102] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行鉴权的情况下,控制移动终端辅助设备存储该信息。 移动终端。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入安全信息例如预定密码来识别用户,然后移动终端发送其自身的信息。 将自己的识别信息发送给移动终端辅助设备。 然后,移动终端辅助设备将接收到的移动终端的标识信息存储在存储器中。 [0103]移动终端的信息例如是移动终端的标识或随机生成的固有号码,但不限于此。 [0104] 根据本发明的一个实施例,移动终端辅助设备与移动终端之间的注册由单独的服务器执行。 例如,当移动终端和移动终端辅助设备通过近距离通信连接时,通过输入预定的安全信息来识别用户,然后移动终端辅助设备将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端辅助设备将移动终端的信息发送给服务器,或者移动终端将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 然后,在通过与移动终端或移动终端辅助设备的无线和有线通信使用移动终端或移动终端辅助设备的情况下,服务器发送关于这些设备是否已经注册到彼此的信息。 [0105] 根据本发明的一个实施例,在步骤 610 ,移动终端辅助设备还存储有至少一个移动终端的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端辅助设备存储移动终端设置信息以允许用户根据用户的期望设置移动终端或内容。 [0106] 返回参考图6,在步骤 620 ,移动终端辅助设备的控制器判断在预定可用距离内是否存在移动终端。 根据本发明的实施例,移动终端辅助设备通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端是否存在于预定可用距离内。 信号强度例如是接收信号强度指示符(RSSI)。 [0107] 根据本发明的一个实施例,当检测到使用移动终端辅助设备的信号时,移动终端辅助设备测量信号强度。 例如,当通过包括在移动终端辅助设备中的用户输入单元输入用户指令时,控制器确定移动终端是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0108] 如果移动终端存在于预定可用距离内,则移动终端辅助设备的控制器基于步骤中存储的至少一个移动终端的信息来判断检测到的移动终端是否为已注册的移动终端 610 . 例如,移动终端辅助设备的控制器判断是否在步骤中检测到移动终端的标识信息 620与移动终端辅助设备的存储器中存储的移动终端的标识信息相同。 可选地,控制器判断是否为随机生成的内在数,该内在数存储在步骤检测到的移动终端中 620 与随机生成的固有数相同,存储在移动终端辅助设备的内存中。 [0109] 根据本发明的一个实施例,如果检测到的移动终端是已注册的移动终端,则控制器向移动终端发送安全相关信息,步骤 640 . [0110] 图中示出了安全相关信息存储在移动终端辅助设备中,但本发明不限于此。 例如,移动终端可以在移动终端与移动终端辅助设备注册的过程中存储安全相关信息,步骤 610 . 或者,安全相关信息可以存储在服务器中。 在这种情况下,步骤 640 ,其中安全相关信息被发送到移动终端,可以被省略。 [0111] 图7是示出根据本发明实施例的移动终端的操作的流程图。 [0112] 参见图7,在步骤 710 ,移动终端的控制器控制在存储器中存储关于至少一个移动终端辅助设备的信息。 即,移动终端通过移动终端辅助设备与移动终端之间的注册,存储至少一个移动终端辅助设备的信息,该移动终端辅助设备将与移动终端进行注册。 当用户试图通过使用移动终端辅助设备与移动终端连接时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0113] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0114] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行认证的情况下,控制移动终端将该信息存储在移动终端上。 终端辅助设备。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入预定密码等安全信息来识别用户,然后移动终端辅助设备发送自己的标识 信息到移动终端。 然后,移动终端将接收到的移动终端辅助设备的标识信息存储在存储器中。 [0115] 移动终端辅助设备的信息例如为移动终端辅助设备的标识或随机生成的固有编号,但不限于此。 [0116]根据本发明的一个实施例,移动终端辅助设备和移动终端之间的注册也可以由单独的服务器进行,​​如上面关于图6所描述的。例如,当移动终端和移动终端 辅助设备通过短距离通信相互连接,通过输入预定的安全信息来识别用户,然后移动终端将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端将移动终端辅助设备的信息发送给服务器,或者移动终端辅助设备将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 此外,在通过与移动终端和移动终端辅助设备的无线和有线通信来使用移动终端或移动终端辅助设备的情况下,服务器发送关于设备是否已经相互注册的信息。 [0117] 根据本发明的一个实施例,在步骤 710 ,移动终端还存储有至少一个移动终端辅助设备的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端存储移动终端设置信息以允许用户根据移动终端辅助设备根据用户的期望设置移动终端或内容。 [0118] 再参考图7,在步骤 720 ,移动终端的控制器判断预定可用距离内是否存在移动终端辅助设备。 根据本发明的实施例,移动终端通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端辅助设备是否存在于预定可用距离内。 信号的强度例如是RSSI。 [0119] 根据本发明的一个实施例,当检测到使用移动终端的信号时,由移动终端测量信号强度。 例如,当通过包括在移动终端中的用户输入单元输入用户指令时,控制器确定移动终端辅助设备是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0120] 如果移动终端辅助设备存在于预定可用距离内,则在步骤 730 ,移动终端的控制器根据步骤中存储的至少一个移动终端辅助设备的信息,判断检测到的移动终端辅助设备是否为已注册的移动终端辅助设备 710 . 例如,移动终端的控制器判断是否在步骤中检测到移动终端辅助设备的标识信息 720与移动终端辅助设备的标识信息相同,存储在移动终端的内存中。 或者,控制器判断是否为随机生成的固有数,存储在步骤检测到的移动终端辅助设备中 720 与随机生成的固有数相同,存储在移动终端的内存中。 [0121] 在步 740 ,移动终端应用存储在步骤中的移动终端辅助设备上的安全相关信息 710 . [0122] 图中示出了安全相关信息存储在移动终端中,但本发明不限于此。 根据本发明的一个实施例,移动终端辅助设备或服务器存储移动终端辅助设备的安全相关信息。 若确定步骤中检测到的移动终端辅助设备 720 为注册的移动端辅助设备,在步骤 730 、 移动终端的通信单元接收来自移动终端辅助设备或服务器的安全相关信息。 移动终端的控制器应用接收到的安全相关信息。 [0123] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的图。 图9A和9B是图示根据本发明实施例的可用距离的图。 [0124] 参考图8A,移动终端之间的注册 800 以及移动终端辅助设备 850 被处理。 根据本发明的一个实施例,移动终端辅助设备 850 具体表现为电子笔,包括手写笔。 [0125] 移动端之间的注册 800 以及移动终端辅助设备 850 移动端通信时触发 800 以及移动终端辅助设备 850 首次制作,例如,通过 BT 或 BTLE 模块的短距离通信。 [0126] 根据本发明的一个实施例,移动终端之间的注册过程 800 以及移动终端辅助设备 850 执行,当注册移动终端辅助设备的消息 850 输入到移动端 800 . 注册移动终端辅助设备的消息以弹窗形式显示,但不限于此,消息可以为移动终端按键输入的形式。 [0127] 移动端之间的注册流程 800 以及移动终端辅助设备 850 执行,当移动终端辅助设备通过移动终端认证时 800 通过安全信息对用户进行标识,如图8A所示。 例如,当在移动终端中输入预定密码或特定图案时 800 , 移动端之间的注册 800 以及移动终端辅助设备 850 被处理。 [0128] 移动端之间注册时 800 以及移动终端辅助设备 850 处理完毕,移动端 800 在移动终端辅助设备上存储信息 850 . 移动端 800 接收移动终端的标识信息 800 从移动端辅助设备 850 通过通信单元。 另外,根据本发明的一个实施例,移动终端辅助设备 850 在移动端存储信息 800 . 移动终端辅助设备 850 接收移动终端辅助设备的识别信息 850 从移动端 800 通过通信单元。 或者,根据本发明的一个实施例,移动终端 800以及移动终端辅助设备 850 存储随机生成的相同内在数。 [0129] 根据本发明的一个实施例,移动终端和移动终端辅助设备之间的注册是由单独的服务器进行的,这在上面参考图6和图7进行了详细描述。 [0130] 存储的信息包括移动终端的安全相关信息 800 或移动终端辅助设备 850 . 即该信息中包含解除移动终端锁定状态的密码 800 或移动终端辅助设备 850 、特定应用程序的密码以及电子邮件和 SNS 的登录信息。 例如,当多个移动终端辅助设备 850 已注册到移动终端 800 , 移动端 800 对已注册的移动终端辅助设备的使用进行不同的限制 850 . 即移动端 800 不允许第一移动终端辅助设备访问特定应用,而允许第二移动终端辅助设备访问所有应用。 当第一移动终端辅助设备注册到移动终端时,存储用于限制第一移动终端辅助设备访问特定应用的安全信息。 进一步地,当第二移动终端辅助设备注册到移动终端时,存储允许第二移动终端辅助设备访问所有应用的安全信息。 [0131] 如图8B所示,如果移动终端 800 以及移动终端辅助设备 850 位于预定的可用距离内 870 , 它们可能相互关联。 [0132] 根据本发明的一个实施例,移动终端 800 以及移动终端辅助设备 850 通过通信单元中包含的短距离通信模块测量信号强度,判断移动终端是否 800 以及移动终端辅助设备 850 存在于预定可用距离内 870 基于测量的信号。 测量信号强度,当移动终端辅助设备有信号使用时 850 或移动端 800 根据本发明的实施例,检测到。 [0133] 如图9A所示,移动终端 900 测量移动终端辅助设备的通信信号强度 950 . RSSI 是通过短距离通信模块测量的。 根据本发明的一个实施例,它被配置为即使移动终端 900 以及移动终端辅助设备 950 存在于连接距离内 980 他们之间可以通过短距离通信进行通信,只有当移动终端时,他们才能真正相互连接 900 以及移动终端辅助设备 950 存在于预定的可用距离内 970 . 因此,第二个连接装置 960 无法与移动端连接 900 . [0134] 如图9B所示,由于信号强度根据与移动终端的距离而降低 900 , 判断移动终端辅助设备是否 950 存在于预定可用距离内 970 从移动端 900 通过测量信号的强度。 [0135] 如移动端辅助设备 950 存在于可用距离之外 980 , 移动端 900 以及移动终端辅助设备 950 完全断开连接。 根据本发明实施例,确定移动终端辅助设备 950 丢失,如下面更详细的描述。 [0136] 回到图8B,如果移动终端 800以及移动终端辅助设备 850 存在于预定可用距离内 870 , 移动端 800 以及移动终端辅助设备 850 确定它们是否已经相对于彼此注册,如上文关于图6和图7所述。 [0137] 如果确定移动端 800 以及移动终端辅助设备 850 已经相互注册,移动端 800 基于移动终端上的安全相关信息使用 800 或移动终端辅助设备 850 . [0138] 图10是示出根据本发明实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0139] 根据本发明的一个实施例,移动终端辅助设备体现为包括触摸传感器的电子笔。 在移动终端与移动终端辅助设备接触的情况下,确定移动终端和移动终端辅助设备正在使用中。 [0140] 即使移动终端辅助设备输入了触摸信号,移动终端辅助设备的控制器也无法判断移动终端辅助设备触摸了哪个物体。 也就是说,即使移动终端辅助设备在移动终端以外的物体上进行触摸,然后通过触摸输入单元输入触摸信号,移动终端辅助设备也不能识别物体,而是感应到触摸信号。 只要。 [0141] 同样,当移动终端接收到包括触摸传感器的触摸屏上的触摸信号时,移动终端无法确定是哪个物体触摸了触摸屏。 也就是说,即使是移动终端的触摸屏上的触摸信号,也可能是移动终端辅助设备以外的其他指针,例如手指输入的触摸信号。 在这种情况下,移动终端仅确定触摸点,而不能确定哪个物体产生触摸信号。 [0142] 相应地,为了判断移动终端辅助设备是否被使用,需要预先判断移动终端上的触摸是否是由移动终端辅助设备进行的。 [0143] 参见图10,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1010 . 控制器提取关于触摸信号的检测的时间信息。 [0144] 在步 1020 ,移动终端辅助设备从移动终端接收移动终端检测到触摸信号的时间的触摸时间信息。 即,当触摸信号也输入到移动终端时,移动终端将输入触摸信号的时间信息发送给移动终端辅助设备,移动终端辅助设备接收该信息。 [0145] 在步 1030 ,移动终端辅助设备比较步骤中接收到的移动终端检测到的触摸信号的时间信息 1020 ,带有step的移动终端辅助设备中检测到触摸信号的时间信息 1010 . 即,移动终端辅助设备判断触摸信号在移动终端辅助设备中的输入时间与触摸信号在移动终端中的输入时间是否相同。 [0146] 如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间不同,则确定输入到移动终端辅助设备的触摸信号是触摸产生的,而不是触摸产生的。 移动终端,而是其他带有移动终端辅助设备的对象。 [0147]如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间相同,则控制器确定移动终端辅助设备触摸到移动终端,进而移动终端。 辅助设备正在使用中。 [0148] 此外,虽然未在图中示出,但是根据本发明的实施例,移动终端辅助设备将确定结果发送到移动终端。 [0149] 图11是示出根据本发明另一实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0150] 参见图11,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1110 . 控制器提取关于触摸信号检测的时间信息。 [0151] 在步 1120 ,移动终端辅助设备将检测到触摸信号的时间信息发送给移动终端。 另外,移动终端辅助设备从移动终端接收移动终端辅助设备是否触摸移动终端的信息,步骤 1130 . [0152] 在图11的实施例中,与图10的实施例不同的是,移动终端判断移动终端辅助设备是否被使用过。 另外,移动终端用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端辅助设备。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端被配置为不向移动终端辅助设备发送单独的响应信号。 [0153] 移动终端辅助设备在步骤中利用接收到的信息判断移动终端辅助设备是否已经针对移动终端使用过 1130 . [0154] 图12是示出根据本发明实施例的确定移动终端辅助设备是否被移动终端使用的流程图。 [0155] 参见图12,移动终端检测针对移动终端的触摸信号,步骤 1210 . 控制器提取关于触摸信号的检测的时间信息。 [0156] 在步 1220 ,移动终端从移动终端辅助设备接收到移动终端辅助设备检测到触摸信号的时间信息。 即,当移动终端辅助设备也输入了触摸信号时,移动终端辅助设备向移动终端发送触摸信号输入时间的信息,移动终端接收该信息。 [0157] 在步 1230 ,移动终端比对步骤中接收到的移动终端辅助设备检测到的触摸信号的时间信息 1220 , 与检测移动终端辅助设备触摸信号的时间信息同步 1210 . 即移动终端可以判断触摸信号在移动终端中的输入时间与触摸信号在移动终端辅助设备中的输入时间是否相同。 [0158] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间不同,则确定移动终端辅助设备中的触摸信号是触摸产生的,而不是移动终端产生的。 终端,而是与移动终端辅助设备的其他对象。 [0159] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间相同,则移动终端的控制器确定移动终端辅助设备触摸了移动终端, 步骤 1240,则该移动终端辅助设备正在使用中。 [0160] 此外,根据本发明的实施例,移动终端将确定结果发送到移动终端辅助设备。 [0161] 图13是示出根据本发明另一实施例的确定移动终端是否辅助移动终端的流程图。 [0162] 参见图13,移动终端检测移动终端的触摸信号,步骤 1310 . 此时,控制器提取触摸信号检测的时间信息。 [0163] 在步 1320 ,移动终端将检测到触摸信号的时间信息发送给移动终端辅助设备。 另外,移动终端从移动终端辅助设备接收移动终端辅助设备是否触摸了移动终端的信息,步骤 1330 . [0164] 在图13的实施例中,与图12的实施例不同的是,移动终端辅助设备判断移动终端辅助设备是否被使用过。 另外,移动终端辅助设备用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端辅助设备被配置为不向移动终端发送单独的响应信号。 [0165] 移动终端利用接收到的信息判断移动终端辅助设备是否针对移动终端使用过, 1330 . [0166] 图14A-14C是图示根据本发明实施例的确定移动终端辅助设备是否已经被使用的图。 [0167] 参见图14A,移动终端辅助设备 1450 移动终端屏幕进入预定可用距离内 1400 被关闭。 移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于预定的可用距离内。 比如移动端 1400 通过与移动终端辅助设备的近距离通信测量RSSI 1450 , 判断移动端辅助设备是否 1450 基于信号的测量强度,存在于预定可用距离内。 [0168] 即使是移动端 1400 以及移动终端辅助设备 1450 存在于预定的可用距离内,根据本发明的一个实施例,移动终端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 仅当移动终端辅助设备存在于预定可用距离内时 1450 正在使用中。 [0169] 如图14B所示,根据参考图10至图13描述的方法确定移动终端辅助设备的使用。 [0170] 例如,当移动终端辅助设备 1450 触摸移动终端 1400 , 移动端辅助设备 1450 检测触摸信号。 移动终端辅助设备 1450 提取触摸信号检测的时间信息。 此外,移动终端 1400 还提取移动终端辅助设备触摸时检测到触摸信号的时间信息 1450 . [0171] 移动终端辅助设备 1450 传输检测到移动终端辅助设备触摸信号的信​​息 1450 到手机端 1400. 或者,根据本发明的一个实施例,移动终端 1400 传输检测到移动终端触摸信号的信​​息 1400 到移动端辅助设备 1450 . [0172] 手机端 1400 比较触摸信号输入到移动终端辅助设备的时间 1450 ,从移动终端辅助设备接收 1450 , 随着触摸信号输入到移动端的时间 1400 . 或者,根据本发明的一个实施例,移动终端辅助设备 1450 比较触摸信号输入到移动端的时间 1400 , 从移动端接收 1400 , 随着触摸信号输入到移动终端辅助设备的时间 1450 . [0173] 如果触摸信号输入到移动终端 1400 以及移动终端辅助设备 1450 同时,移动端的控制器 1400 或移动终端辅助设备 1450 确定移动终端辅助设备 1450 触动了移动端 1400 . [0174] 随后,移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 和移动端 1400 ,它们存在于预定的可用距离内,已经相对于彼此注册。 如果确定移动端 1400 以及移动终端辅助设备 1450 已经相对于彼此注册,如图14C所示,移动终端 1400 可以通过应用预定的安全相关信息将其转为使用状态。 [0175] 根据本发明的一个实施例,移动终端后 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于可用距离内,若移动终端辅助设备 1450 存在于可用距离内,判断是否存在移动终端辅助设备 1450 正在使用中。 [0176] 例如,即使是移动终端辅助设备 1450 在移动终端的可用距离内被检测到 1400 ,如果是移动端辅助设备 1450 未使用时,无需判断是否为移动终端辅助设备 1450 已注册。 反之,如果移动终端辅助设备 1450 正在使用中,应判断是否为移动终端辅助设备 1450 已注册。 据此,移动终端 1400 判断移动端辅助设备是否 1450 判断是否为移动终端辅助设备后注册的 1450 是否存在于可用距离内以及检测到的移动终端辅助设备是否存在 1450 正在使用中。 [0177] 图15A-15D是图示根据本发明实施例的移动终端和移动终端辅助设备的使用的图。 [0178] 参考图15A,一个用户针对一个移动终端使用一个移动终端辅助设备。 用户根据他或她的需要配置移动终端。 相应地,在移动终端与移动终端辅助设备之间的注册过程中,可以将包括移动终端的设置信息在内的安全相关信息存储在移动终端或移动终端辅助设备中。 之后,当用户通过移动终端辅助设备使用移动终端时,根据预先存储的设置信息对移动终端进行配置,从而使用户能够方便地使用移动终端。 [0179]或者,如图15B所示,一个用户可以通过使用一个移动终端辅助设备来使用多个移动终端。 用户在多个移动终端上使用具有一致性的特定信息。 因此,根据本发明的实施例,用户在移动终端辅助设备中存储他或她想要的包括设置信息的安全信息。 另外,当用户从第一移动终端切换到第二移动终端时,用户根据存储在移动终端辅助设备中的设置信息配置和使用第二移动终端。 [0180] 如图15C所示,多个用户通过各自的移动终端辅助设备使用一个移动终端。 用户在保护隐私的同时与其他用户共享移动终端的内容。 相应地,每个用户在移动终端辅助设备中存储包括密码的安全相关信息,该密码防止其他人查看他或她在移动终端中的私人信息。 备选地,可以配置为将安全相关信息存储在移动终端中,并且仅当预定的移动终端辅助设备与移动终端连接时才去激活安全。 [0181] 如图15D所示,多个用户通过多个移动终端辅助设备使用多个移动终端。 在这种情况下,用户在多个移动终端上使用一致的特定信息,并在保护隐私的同时与其他用户共享移动终端的内容。 在这种情况下,每个用户在移动终端辅助设备中存储安全相关信息,包括他或她想要的设置信息和防止其他人查看他或她在移动终端中的私人信息的密码。 根据本发明实施例,安全相关信息存储在移动终端中。 [0182] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图。 [0183] 参见图16,在步骤 1610 ,移动终端辅助设备判断注册的移动终端是否存在预定的连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0184] 如果预定连接距离内不存在移动终端,则确定移动终端辅助设备与移动终端断开连接,移动终端辅助设备删除内存中存储的移动终端信息, 步骤 1630 . [0185] 根据本发明的一个实施例,当确定在连接距离内不存在已注册的移动终端时,移动终端辅助设备判断在预定断开参考时间内是否检测到移动终端,步骤 1620 . 即,移动终端辅助设备判断移动终端是否在预定断开参考时间内不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端,则移动终端辅助设备删除正在运行的移动终端的信息 1630 . [0186] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除移动终端辅助设备中存储的第一移动终端的信息。 [0187]然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 此时,移动终端辅助设备在第一移动终端断开连接后,判断第二移动终端是否连接断开参考时间 1620 . 判断结果为,如果第二移动终端在预定的参考时间内连接上,则移动终端辅助设备不删除第一移动终端的信息,而是保留第一移动终端的信息。 [0188] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户使用多个移动终端的流程图。 [0189] 参见图17,在步骤 1710 ,移动终端判断注册的移动终端辅助设备是否存在预定连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定的连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0190] 若预定连接距离内不存在移动终端辅助设备,则确定移动终端辅助设备与移动终端断开连接,移动终端删除内存中存储的移动终端辅助设备信息, 步 1730 . [0191] 根据本发明的一个实施例,当确定连接距离内不存在已注册的移动终端辅助设备时,移动终端判断是否在预定断开参考时间内检测到移动终端辅助设备。 也就是说,移动终端可以判断在预定断开参考时间内移动终端辅助设备是否不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端辅助设备,则移动终端删除正在运行的移动终端辅助设备的信息 1730 . [0192] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除第一移动终端中存储的移动终端辅助设备信息。 [0193] 然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 第一移动终端在与第一移动终端断开后,判断移动终端辅助设备是否与第二移动终端连接,步骤 1720 . 判断结果为,若移动终端附属设备与第二移动终端连接,则第一移动终端不删除,而是保留移动终端附属设备的信息。 [0194]第一移动终端从服务器接收移动终端辅助设备是否与第二移动终端连接的信息。 也就是说,当移动终端辅助设备与至少一个移动终端相互注册时,服务器存储至少一个移动终端与移动终端辅助设备的注册状态信息。 另外,移动终端或移动终端辅助设备周期性或特定事件发生时,向服务器发送移动终端辅助设备与哪个移动终端连接以及移动终端辅助设备是否在使用中的信息。 进一步地,服务器存储接收到的移动终端辅助设备和移动终端的使用状态信息。 [0195] 如果确定移动终端辅助设备与所有移动终端断开连接,不再使用,根据本发明实施例,移动终端和移动终端辅助设备的注册状态信息 被删除。 根据本发明的一个实施例,服务器向移动终端或移动终端辅助设备发送注销指令。 之后,接收到注销指令的移动终端或移动终端附属设备删除存储在移动终端附属设备或移动终端上的信息。 [0196] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图。 [0197] 参考图18,服务器 1830 管理移动终端辅助设备相互注册信息 1850 以及至少一台移动终端 1810 和/或 1820 . [0198] 移动终端辅助设备 1850 离开第二移动终端的可用距离区域 1820 , 而移动端辅助设备 1850 与第二移动终端结合使用 1820 . 随后,移动终端辅助设备 1850 进入第一移动终端的可用距离区域 1810 与第一移动终端连接 1810 用来。 [0199] 移动终端 1810 和 1820 传输是否与移动终端辅助设备连接的信息 1850 到服务器 1830 . 服务器 1830 从移动终端接收关于连接状态的信息 1810 和 1820 , 并存储相同的。 [0200] 根据本发明的一个实施例,第二移动终端 1820 接收到移动终端辅助设备的信息 1850 与第二移动终端断开连接 1820 , 但它与第一​​移动终端连接 1810 , 从服务器 1830 . 即第二移动终端 1820 确定移动终端辅助设备 1850 未丢失但与第一移动终端连接 1810 在使用中。 因此,第二移动终端 1820 不删除但维护移动终端辅助设备上的信息 1850 . [0201] 然而,虽然未在图中示出,但是当移动终端辅助设备 1850 连第一个移动终端都没有连接 1810 , 第二移动端 1820 接收到移动终端辅助设备的信息 1850 从服务器断开所有移动终端 1830 . 第二移动终端 1820 确定移动终端辅助设备 1850 丢失了。 第二移动终端 1820 删除移动终端辅助设备信息 1850 以及与安全相关的信息。 第一个移动终端 1820 同时删除移动端辅助设备信息 1850 以及与安全相关的信息。 [0202]图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 [0203] 参见图19,移动终端辅助设备 1950 管理关于至少一个移动终端的注册信息 1910 或者 1920 . [0204] 移动终端辅助设备 1950 确定与移动终端的连接状态 1910 和 1920 . [0205] 例如移动端辅助设备 1950 离开第二移动终端的可用距离区域 1920 而移动终端辅助设备 1950 与第二移动终端结合使用 1920 . 随后,移动终端辅助设备 1950 进入第一移动终端的可用距离区域 1910 从而与第一移动终端连接 1910 用来。 [0206] 根据本发明的一个实施例,移动终端辅助设备 1950 判断移动端辅助设备是否 1950 与第一移动终端连接 1910 在预定的断开时间内。 即如果移动终端辅助设备 1950 与第二移动终端断开连接 1920 , 并与第一移动终端相连 1910 , 移动端辅助设备 1950 不认为丢失。 据此,移动终端辅助设备 1950 不删除但维护移动终端上的信息 1910 和 1920 以及与安全相关的信息。 [0207] 然而,当移动终端辅助设备 1950 连第一个移动终端都没有连接 1910 , 移动端辅助设备 1950 因未与任何移动终端连接,确定丢失。 移动终端辅助设备 1950 删除手机端信息 1910 和 1920 ,以及与安全相关的信息。 [0208] 根据本发明的一个实施例,在移动终端中注册移动终端辅助设备时,可以将电子邮件、SNS等应用程序的账户信息存储在移动终端辅助设备的内存中。 移动终端辅助设备在使用移动终端时,移动终端辅助设备可以将存储的账户信息发送给移动终端。 移动终端可以根据接收到的账号信息,自动登录对应的账号,无需输入登录密码。 [0209] 或者,根据本发明的一个实施例,移动终端辅助设备存储移动终端锁定状态解除的信息。 此时,在通过移动终端辅助设备的特定按键开启移动终端的显示单元,并通过移动终端辅助设备触摸移动终端的显示单元的情况下,移动终端可以 无需输入密码即可转换为等待模式。 [0210] 另外,根据本发明的一个实施例,在移动终端和移动终端辅助设备在使用过程中持续测量RSSI,从而可以判断移动终端辅助设备是否存在于预定的可用距离内。 如果判断结果为移动终端辅助设备在可用距离内,则确定移动终端辅助设备正在使用中,从而可以控制移动终端的显示单元保持开启。 [0211] 根据本发明的一个实施例,在使用移动终端进行支付时,使用已注册的移动终端辅助设备可以很容易地批准支付,或者只有通过签名等安全过程才能批准支付。 通过已注册的移动终端辅助设备进行。 [0212]此外,根据本发明的一个实施例,通过输入单元放大或缩小显示在移动终端的显示单元上的特定对象,例如移动终端辅助设备上的按钮。 [0213] 此外,根据本发明的实施例,所描述的方法可以通过记录有程序的记录介质中的计算机可读代码来实现。 计算机可读介质包括其中存储有计算机系统可读数据的所有类型的记录设备。 计算机可读记录介质可以包括ROM、RAM、CD-ROM、磁带、软盘、光学数据存储器等。 计算机可读记录介质可以以载波的形式实现(例如,通过互联网传输)。 计算机可以包括终端的控制器或移动终端辅助设备的控制器。 [0214] 对于本领域的技术人员来说显而易见的是,在不脱离本发明的范围和本质特征的情况下可以进行各种修改。 [0215] 虽然本发明已参照其某些实施例进行了展示和描述,但本领域技术人员将理解,在不脱离本发明所定义的精神和范围的情况下,可以在其中进行形式和细节的各种改变 附加索赔。(String), 111523(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.996 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.997 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:42.998 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.063 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.065 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.073 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.095 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.096 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.097 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.101 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.102 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.102 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), KR1020150041337A(String), 1046977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.136 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.137 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.137 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), KR102138034B1(String), 1046978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.139 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.139 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.140 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), US20150099486A1(String), 1046979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.141 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.142 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.142 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), US9749858B2(String), 1046980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.143 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.144 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.144 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9749858B2(String), US9749858B2(String), 1503936000(Integer), 270635(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.145 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.147 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.147 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.182 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.184 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.184 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.186 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.187 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.187 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.229 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.230 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.231 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.271 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.272 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.273 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.274 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.275 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.275 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184952(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.282 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.283 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.284 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.292 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.294 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.294 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.295 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.295 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.295 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.296 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.297 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.297 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.351 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.385 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.400 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.402 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.402 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.405 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.407 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.407 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.424 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.424 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.425 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.482 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.486 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.487 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.490 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.492 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.492 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.502 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.504 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.504 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\84594f161ed442aa97901408ecc77732.png(String), 184953(Integer), 84594f161ed442aa97901408ecc77732.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.513 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.514 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.514 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.516 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.517 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.518 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Multi-standby mobile terminal and method of performing conference call using the same(String), 多待移动终端及使用该移动终端进行电话会议的方法(String), US20090186607A1(String), A multi-standby mobile terminal and a method for performing a conference call using the same are provided. The method of performing a conference call includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal, requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network, and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 提供了一种多待移动终端和使用该多待移动终端进行电话会议的方法。 执行电话会议的方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端是多待移动终端,通过第三者请求与第二移动终端的通信。 移动终端存在于第二无线通信网络中,并且通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议,当 通信请求为电话会议请求,将合成声音信号发送给第三移动终端。(String), US12/346068(String), 1230566400(Integer), US20090186607A1(String), 1248278400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 9(Integer), US20030072421A1 | US20030092433A1 | US20060291419A1 | US20070082699A1 | US20070111743A1 | US20090291675A1 | US6904023B2 | US7869806B2 | US8244228B1(String), \20230420\84594f161ed442aa97901408ecc77732.png(String), 20(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.546 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.547 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.549 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:43.570 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.379 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.380 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 1. A multi-standby mobile terminal comprising:a first communication module for forming a communication channel with a first wireless communication network;a second communication module for forming a communication channel with a second wireless communication network; anda first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and for outputting the synthesized sound signal to the second communication module.(String), 1.一种进行电话会议的方法,该方法包括:连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端包括多待移动终端;通过存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信;和当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成为第二移动终端的第一混音器中的合成声音信号来执行电话会议,以及将合成后的声音信号发送给第三移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.380 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 2. The multi-standby mobile terminal of claim 1, further comprising a second audio mixer for synthesizing sound signals, input from the first communication module and the second communication module, to a synthesized sound signal, and outputting the synthesized sound signal to a speaker.(String), 12.如权利要求11所述的方法,其中电话会议的执行还包括如果第一移动终端和第二移动终端之间的通信终止,则终止第三混音器的功能。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.381 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 3. The multi-standby mobile terminal of claim 2, further comprising a third audio mixer for synthesizing sound signals, input from the second communication module and the microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the first communication module.(String), 13.如权利要求11所述的方法,其中进行电话会议还包括将从第一移动终端和第三移动终端输入的声音信号合成为第二移动终端的第二混音器中的合成声音信号,并将合成声音信号输出到第二移动终端的扬声器移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.381 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 4. The multi-standby mobile terminal of claim 1, further comprising:a first antenna for transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and for receiving a frequency to be used for the GSM wireless communication network; anda second antenna for transmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and for receiving a frequency to be used for the CDMA wireless communication network.(String), 14.如权利要求11所述的方法,还包括:通过全球移动通信系统(GSM)无线通信网络发送和接收声音信号和数据,并接收用于GSM无线通信网络的频率;和通过码分多址(CDMA)无线通信网络发送和接收声音信号和数据,以及接收要用于CDMA无线通信网络的频率。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.381 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 5. The multi-standby mobile terminal of claim 4, wherein the first communication module forms the communication channel with the GSM wireless communication network and transmits and receives a wireless signal to and from a first mobile terminal.(String), 15.如权利要求14所述的方法,其中第一无线通信网络包括GSM无线通信网络并且向第一移动终端发送无线信号以及从第一移动终端接收无线信号。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.381 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 6. The multi-standby mobile terminal of claim 4, wherein the second communication module forms the communication channel with the CDMA wireless communication network and transmits and receives a wireless signal to and from a third mobile terminal.(String), 16.如权利要求14所述的方法,其中第二无线通信网络包括CDMA无线通信网络并且向第三移动终端发送无线信号以及从第三移动终端接收无线信号。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.382 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 7. The multi-standby mobile terminal of claim 5, wherein the first communication module demodulates a wireless signal received from the first mobile terminal and modulates the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 17.如权利要求15所述的方法,还包括对从第一移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第三移动终端的合成声音信号进行调制。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.382 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 8. The multi-standby mobile terminal of claim 6, wherein the second communication module demodulates a wireless signal received from the third mobile terminal and modulates a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 18.如权利要求16所述的方法,还包括对从第三移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第一移动终端的合成声音信号进行调制。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.382 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 9. The multi-standby mobile terminal of claim 3, further comprising a controller for terminating a function of the first audio mixer, if communication through the second communication module terminates.(String), 19.如权利要求13所述的方法,其中进行电话会议包括将从第二移动终端和第三移动终端输入的声音信号在第二移动终端的第三混音器中合成为合成声音信号,并将合成声音信号发送给第一移动终端。(String), 1(Integer), 8(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.382 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 10. The multi-standby mobile terminal of claim 9, wherein the controller terminates a function of the third audio mixer, if communication through the first communication module terminates.(String), 20.如权利要求19所述的方法,其中电话会议的执行还包括如果第二移动终端和第三移动终端之间的通信终止,则终止第一混音器的功能。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.383 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.383 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 11. A method for performing a conference call, the method comprising:connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal comprises a multi-standby mobile terminal;requesting communication with the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; andperforming a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.383 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 12. The method of claim 11, wherein the performing of the conference call further comprises terminating a function of the third audio mixer, if communication between the first mobile terminal and the second mobile terminal terminates.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 13. The method of claim 11, wherein the performing of the conference call further comprises synthesizing sound signals input from the first mobile terminal and the third mobile terminal, to a synthesized sound signal in a second audio mixer of the second mobile terminal and outputting the synthesized sound signal to a speaker of the second mobile terminal.(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 14. The method of claim 11, further comprising:transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and receiving a frequency to be used for the GSM wireless communication network; andtransmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and receiving a frequency to be used for the CDMA wireless communication network.(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 15. The method of claim 14, wherein the first wireless communication network comprises the GSM wireless communication network and transmits and receives a wireless signal to and from the first mobile terminal.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 16. The method of claim 14, wherein the second wireless communication network comprises the CDMA wireless communication network and transmits and receives a wireless signal to and from the third mobile terminal.(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 17. The method of claim 15, further comprising demodulating a wireless signal received from the first mobile terminal and modulating the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.384 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 18. The method of claim 16, further comprising demodulating a wireless signal received from the third mobile terminal and modulating a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.385 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 19. The method of claim 13, wherein the performing of the conference call comprises synthesizing sound signals input from the second mobile terminal and the third mobile terminal, to a synthesized sound signal in a third audio mixer of the second mobile terminal and transmitting the synthesized sound signal to the first mobile terminal.(String), 1(Integer), 18(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.385 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 20. The method of claim 19, wherein the performing of the conference call further comprises terminating a function of the first audio mixer, if communication between the second mobile terminal and the third mobile terminal terminates.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.550 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.551 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.556 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.557 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.557 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111524(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.562 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.563 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.564 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184953(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Jan. 17, 2008 in the Korean Intellectual Property Office and assigned Serial No. 10-2008-0005296, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same. More particularly, the present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same that enable a communication connection between several mobile terminals existing in different wireless communication networks. [0004]2. Description of the Related Art [0005]Due to rapid technology development, mobile terminals having various functions, such as voice communication, short message service, audiovisual communication, an electronic scheduler and Internet, are now available. A multi-standby mobile terminal that can perform a communication connection with two or more wireless communication networks, such as a dual-standby mobile terminal that supports a Code Division Multiple Access (CDMA) wireless communication network and a Global System for Mobile communication (GSM) wireless communication network, is now provided. The dual-standby mobile terminal may be in a communication standby state in both a CDMA wireless communication network service area and a GSM wireless communication network service area. That is, in a state where the dual-standby mobile terminal is connected for communication with a mobile terminal using a CDMA wireless communication network, the dual-standby mobile terminal can receive a communication request from a mobile terminal using a GSM wireless communication network and be connected with the mobile terminal for communication. [0006]A mobile terminal service provider provides, as an additional service, a conference call function in which several persons can simultaneously form a communication channel and perform a phone conference. [0007]A conventional multi-standby mobile terminal cannot perform a conference call. However, the conventional multi-standby mobile terminal can only perform simultaneous standby and individual communication with mobile terminals using different wireless communication networks. [0008]Therefore, a need exists for a method and apparatus that enable a multi-standby mobile terminal to perform a conference call using different wireless communication networks. SUMMARY OF THE INVENTION [0009]An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a multi-standby mobile terminal and a method for performing a conference call using the same that enable mobile terminals in different wireless communication networks to perform a conference call. [0010]In accordance with an aspect of the present invention, a multi-standby mobile terminal is provided. The mobile terminal includes a first communication module for forming a communication channel with a first wireless communication network, a second communication module for forming a communication channel with a second wireless communication network, and a first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the second communication module. [0011]In accordance with another aspect of the present invention, a method of performing a conference call is provided. The method includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal; requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal. [0012]Other aspects, disadvantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0014]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention; [0015]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention; and [0016]FIG. 3 is a flowchart illustrating a method for performing a conference call according to an exemplary embodiment of the present invention. [0017]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0018]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0019]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0020]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0021]In the following description, a dual-standby mobile terminal that can perform a communication connection with a CDMA wireless communication network and a GSM wireless communication network, such as a multi-standby mobile terminal, are described. However, the present invention is not limited thereto. That is, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a communication connection with various wireless communication networks, such as a General Packet Radio Service (GPRS), an Enhanced Data GSM Environment (EDGE), a Universal Mobile Telecommunications System (UMTS) and a Wideband Code Division Multiple Access (WCDMA). [0022]A configuration of a multi-standby mobile terminal according to an exemplary embodiment of the present invention and a method of performing a conference call using the multi-standby mobile terminal are described with reference to the accompanying drawings. [0023]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0024]Referring to FIG. 1, a first mobile terminal 100 is a mobile terminal for supporting a GSM wireless communication network 150, a third mobile terminal 300 is a mobile terminal for supporting a CDMA wireless communication network 350 and a second mobile terminal 200 is a multi-standby mobile terminal for supporting both the GSM and CDMA wireless communication networks 150 and 350. The first mobile terminal 100 and the third mobile terminal 300 may also be a multi-standby mobile terminal. [0025]In the following description, in a state where the first mobile terminal 100 and the second mobile terminal 200 are connected for communication, if the third mobile terminal 300 requests communication between several persons, it is assumed that the second mobile terminal 200 may perform a conference call function. That is, in a state where the second mobile terminal 200 and the first mobile terminal 100 are connected for communication using the GSM wireless communication network 150, the third mobile terminal 300 may request, through the CDMA wireless communication network 350, communication between several persons to the second mobile terminal 200. Alternatively, the second mobile terminal 200 may request communication between several persons to the third mobile terminal 300. In this case, a conference call function of the second mobile terminal 200 is activated. Thus, communication between the first mobile terminal 100, the second mobile terminal 200 and the third mobile terminal 300 may be performed. [0026]A conference call function of the second mobile terminal 200 is described later with reference to FIG. 2. [0027]When a conference call function is activated, if a sound signal of the first mobile terminal 100 is transmitted to the second mobile terminal 200, the second mobile terminal 200 synthesizes its own sound signal and a sound signal of the first mobile terminal 100 using an audio mixer and transmits the synthesized sound signal to the third mobile terminal 300. That is, the third mobile terminal 300 may receive sound signals of the second mobile terminal 200 and the first mobile terminal 100 through the synthesized sound signal. [0028]Similarly, if a sound signal of the third mobile terminal 300 is transmitted to the second mobile terminal 200, the second mobile terminal 200 may synthesize its own sound signal and a sound signal of the third mobile terminal 300 using an audio mixer. The second mobile terminal 200 then transmits the synthesized sound signal to the first mobile terminal 100. That is, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300 through the synthesized sound signal. [0029]The second mobile terminal 200 synthesizes a sound signal transmitted from the first mobile terminal 100 and a sound signal transmitted from the third mobile terminal 300 using the audio mixer and outputs the synthesized sound signal through a speaker (SPK) of the second mobile terminal 200. Thereby, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300, the second mobile terminal 200 may receive sound signals of the first mobile terminal 100 and the third mobile terminal 300, and the third mobile terminal 300 may receive sound signals of the first mobile terminal 100 and the second mobile terminal 200. Thus, a conference call may be performed. [0030]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0031]FIG. 2 illustrates, as the multi-standby mobile terminal 200 according to an exemplary embodiment of the present invention, a dual-standby mobile terminal that may perform a communication connection with the GSM wireless communication network and the CDMA wireless communication network. However, the multi-standby mobile terminal of the present invention is not limited to the dual-standby mobile terminal. [0032]The dual-standby mobile terminal may have slots in which a CDMA card and a GSM card are mounted or one slot for mounting a dual card in which a CDMA card and a GSM card are integrated. [0033]Referring to FIG. 2, a dual-standby mobile terminal (hereinafter, the second mobile terminal 200) according to an exemplary embodiment of the present invention includes a first antenna 401, a second antenna 402, a first communication module 410, a second communication module 420, a controller 450 and an audio mixer 460 including a first audio mixer 461, a second audio mixer 462 and a third audio mixer 463. [0034]The first antenna 401 transmits and receives a sound signal and data through the GSM wireless communication network 150 and receives a frequency to be used for the GSM wireless communication network 150. [0035]The second antenna 402 transmits and receives a sound signal and data through the CDMA wireless communication network 350 and receives a frequency to be used for the CDMA wireless communication network 350. [0036]FIG. 2 illustrates the first antenna 401 and the second antenna 402 as separate antennas. However the first antenna 401 and the second antenna 402 may be formed as one antenna. When the first antenna 401 and the second antenna 402 are formed as one antenna, the dual-standby mobile terminal 200 includes a means for dividing a frequency band into a CDMA frequency band and a GSM frequency band. For example, the dual-standby mobile terminal 200 divides a signal received by the antenna using a duplexer (not shown) into signals of a CDMA frequency band and signals of a GSM frequency band. The dual-standby mobile terminal 200 transmits the signal of the GSM frequency band to the first communication module 410 and the signal of the CDMA frequency band to the second communication module 420. [0037]The first communication module 410 and the second communication module 420 each include a transmission/reception signal divider (not shown) for dividing a transmission/reception signal, a Radio Frequency (RF) transmitter (not shown) for up-converting a frequency of a signal to be transmitted and amplifying the signal, an RF receiver (not shown) for low-noise amplifying a received signal and down-converting a frequency of the signal and a modem for modulating and demodulating a sound signal. [0038]Hereinafter, for convenience of description, it is assumed that the first communication module 410 forms a communication channel with the GSM wireless communication network 150 and transmits and receives a wireless signal to and from the first mobile terminal 100 using a GSM wireless communication method. Also, the second communication module 420 forms a communication channel with the CDMA wireless communication network 350 and transmits and receives a wireless signal to and from the third mobile terminal 300 using a CDMA wireless communication method. [0039]The first communication module 410 demodulates a wireless signal received from the first mobile terminal 100 and modulates a sound signal input from a microphone (MIC) of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the first communication module 410 modulates a sound signal of the second mobile terminal 200 and a sound signal of the third mobile terminal 300 synthesized in the audio mixer 460 and transmits the modulated sound signal to the first mobile terminal 100. [0040]The second communication module 420 demodulates a wireless signal received from the third mobile terminal 300 and modulates a sound signal input from the MIC of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the second communication module 420 modulates a sound signal of the second mobile terminal 200 and a sound signal of the first mobile terminal 100 synthesized in the audio mixer 460 and transmits the modulated sound signal to the third mobile terminal 300. [0041]The controller 450 controls general operations of the second mobile terminal 200 and a signal flow of elements of the second mobile terminal 200. More particularly, the controller 450 controls the first communication module 410 and the second communication module 420. In more detail, the controller 450 controls the first communication module 410 and the second communication module 420 to perform a communication connection with the GSM communication network 150 and CDMA communication network 350, respectively. When a communication connection request is received by the first communication module 410 or the second communication module 420, the controller 450 activates the corresponding first communication module 410 or second communication module 420 to perform communication. [0042]Further, in a state where the first mobile terminal 100 and the second mobile terminal 200 perform communication through the GSM wireless communication network 150, if the third mobile terminal 300 requests communication between several persons through the CDMA wireless communication network 350, the controller 450 of the second mobile terminal 200 performs a conference call function. If a communication request received from the third mobile terminal 300 is not a request for communication between several persons, the controller 450 performs an individual communication function. That is, in order to perform individual communication with the third mobile terminal 300, the controller 450 terminates functions other than a communication connection function of the first communication module 410. Further, the controller 450 controls the audio mixer 460 to block transmission and reception of a sound signal to and from the first mobile terminal 100. [0043]Similarly, in order to perform individual communication with the first mobile terminal 100, the controller 450 terminates functions other than a communication connection function of the second communication module 420, and blocks transmission and reception of a sound signal to and from the third mobile terminal 300. [0044]The controller 450 may perform a conference call function for activating both the first communication module 410 and the second communication module 420. Specifically, when the controller 450 activates both the first communication module 410 and the second communication module 420, a sound signal of the first mobile terminal 100 is modulated in the second mobile terminal 200, the modulated sound signal is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the third mobile terminal 300. Likewise, a sound signal of the third mobile terminal 300 is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the first mobile terminal 100. Thereby, a conference call for voice communication between mobile terminals in different wireless communication networks is performed. [0045]When the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0046]While performing a conference call, when communication with either the first mobile terminal 100 or the third mobile terminal 300 terminates, the controller 450 controls a conference call termination function of the audio mixer 460. A detailed description thereof is described later. [0047]The controller 450 may be included in the first communication module 410 or in the second communication module 420. In this case, the communication module 410 or 420 including the controller 450 becomes a main communication module and controls signal flows of the entire system, including the signal flows of another communication module. [0048]When performing a conference call, the first audio mixer 461 synthesizes a sound signal of the first mobile terminal 100 received from the first communication module 410 and a sound signal received from the MIC of the second mobile terminal 200. The first audio mixer 461 outputs the synthesized sound signal to the second communication module 420. The synthesized sound signal output to the second communication module 420 is modulated and transmitted to the third mobile terminal 300 via the second antenna 402. That is, when performing a conference call, a sound signal of the first mobile terminal 100 is input to the first audio mixer 461, via the first communication module 410 of the second mobile terminal 200, and synthesized by the first audio mixer 461 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the second communication module 420 of the second mobile terminal 200 and transmitted to the third mobile terminal 300 through the second antenna 402. [0049]While performing a conference call, when communication with the third mobile terminal 300 terminates, the first audio mixer 461 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the first audio mixer 461 is activated only when performing communication with the third mobile terminal 300. [0050]The second audio mixer 462 synthesizes a sound signal of the first mobile terminal 100 output from the first communication module 410 and a sound signal of the third mobile terminal 300 output from the second communication module 420. The synthesized sound signal is output through a speaker (SPK) of the second mobile terminal 200. The SPK may be mounted on the mobile terminal or may be an earphone of the mobile terminal or a separate audio speaker receiving the synthesized sound signal. [0051]The third audio mixer 463 synthesizes a sound signal of the third mobile terminal 300 received from the second communication module 420 and a sound signal received from the MIC of the second mobile terminal 200. The third audio mixer 463 outputs the synthesized sound signal to the first communication module 410. The synthesized sound signal output to the first communication module 410 is modulated and transmitted to the first mobile terminal 100, via the first antenna 401. That is, when performing a conference call, a sound signal of the third mobile terminal 300 is input to the third audio mixer 463 via the second communication module 420 of the second mobile terminal 200 and synthesized by the third audio mixer 463 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the first communication module 410 of the second mobile terminal 200 and transmitted to the first mobile terminal 100 from the first antenna 401. [0052]While performing a conference call, when communication with the first mobile terminal 100 terminates, the third audio mixer 463 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the third audio mixer 463 is activated only when performing communication with the first mobile terminal 100. [0053]FIG. 3 is a flowchart illustrating a method of performing a conference call according to an exemplary embodiment of the present invention. [0054]Referring to FIGS. 1 to 3, the first mobile terminal 100 and the second mobile terminal 200 are connected for communication through the GSM wireless communication network 150 in step S500. In this case, the second mobile terminal 200 transmits and receives a wireless signal to and from the first mobile terminal 100 from the first antenna 401 and the first communication module 410. [0055]The controller 450 of the second mobile terminal 200 controls the second communication module 420 to await a communication connection request. Further, when forming a communication channel with the first mobile terminal 100, the controller 450 of the second mobile terminal 200 activates the second audio mixer 462 and the third audio mixer 463 and sustains the first audio mixer 461 in an inactive state. Specifically, when the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 of the second mobile terminal 200 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0056]The third mobile terminal 300 requests communication to the second mobile terminal 200 through the CDMA wireless communication network 350 in step S502. Although not shown in FIG. 3, alternatively the second mobile terminal 200 may request communication to the third mobile terminal 300 through the CDMA wireless communication network 350. [0057]When a communication request from the third mobile terminal 300 is received, the controller 450 of the second mobile terminal 200 notifies the reception of a communication request to a user of the second mobile terminal 200, by controlling a display unit to display that a communication connection request from another wireless communication network is received or by outputting a reception sound, for example. [0058]The second mobile terminal 200 determines whether a conference call is to be performed according to the communication request received from the CDMA wireless communication network 350 in step S504. [0059]If a conference call is not to be performed, the second mobile terminal 200 performs individual communication with either the first mobile terminal 100 or the third mobile terminal 300, according to the user's selection in step S506. The individual communication is performed by controlling the first communication module 410 and the second communication module 420. For example, when individual communication with the first mobile terminal 100 is intended, the controller 450 of the second mobile terminal 200 controls to sustain only a communication connection state of the second communication module 420 and to turn off other functions. [0060]If it is determined that a conference call is to be performed in step S504, the second mobile terminal 200 activates a conference call function in step S508. The controller 450 activates both the first communication module 410 and the second communication module 420 of the second mobile terminal 200, and activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0061]The second mobile terminal 200 is connected for communication with the third mobile terminal 300 in the CDMA wireless communication network 350 in step S510, thereby forming a conference call with the first mobile terminal 100 and the third mobile terminal 300. [0062]When forming a conference call between the first mobile terminal 100 and the third mobile terminal 300, the first audio mixer 461 of the second mobile terminal 200 synthesizes a sound signal of the first mobile terminal 100 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the second communication module 420. The output sound signal of the first mobile terminal 100 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the third mobile terminal 100 from the second antenna 402. [0063]The third audio mixer 463 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the first communication module 410. The output sound signal of the third mobile terminal 300 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the first mobile terminal 100 from the first antenna 401. [0064]The second audio mixer 462 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the first mobile terminal 100. The second audio mixer 462 outputs the synthesized sound signal through the SPK of the second mobile terminal 200. [0065]While performing a conference call, when communication between the first mobile terminal 100 and the second mobile terminal 200 terminates, the controller 450 of the second mobile terminal 200 terminates functions of the third audio mixer 463 in order to prevent unnecessary power consumption. Alternatively, when communication between the second mobile terminal 200 and the third mobile terminal 300terminates, the controller 450 of the second mobile terminal 200 terminates functions of the first audio mixer 461 in order to prevent unnecessary power consumption. [0066]As described above, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a conference call with mobile terminals using different wireless communication networks. Thus, a conference call may be performed without subscribing to an additional service. Accordingly, user convenience may be improved. [0067]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.(String), 优先 [0001] 此申请根据 35 U.S.C. 2008 年 1 月 17 日向韩国知识产权局提交并转让序列号为 10-2008-0005296 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种多待移动终端以及使用该多待移动终端进行电话会议的方法。 更具体地,本发明涉及一种多待移动终端以及使用该多待移动终端执行电话会议的方法,其使得存在于不同无线通信网络中的多个移动终端之间能够进行通信连接。 [0004] 2.相关技术的描述 [0005] 由于技术的快速发展,具有多种功能的移动终端,例如语音通信、短消息服务、视听通信、电子日程安排和互联网已经面世。 可以与两个或多个无线通信网络进行通信连接的多待移动终端,例如支持码分多址(CDMA)无线通信网络和全球移动通信系统(GSM)的双待移动终端 ) 无线通信网络,现提供。 双待移动终端在CDMA无线通信网络服务区和GSM无线通信网络服务区都可以处于通信待机状态。 即,在双待移动终端与使用CDMA无线通信网络的移动终端进行通信连接的状态下,双待移动终端可以接收来自使用GSM无线通信网络的移动终端的通信请求,并且 与移动终端连接进行通信。 [0006] 移动终端服务提供商作为附加服务提供电话会议功能,其中几个人可以同时形成通信信道并进行电话会议。 [0007] 传统的多待移动终端无法进行电话会议。 然而,传统的多待机移动终端只能与使用不同无线通信网络的移动终端进行同时待机和单独通信。 [0008] 因此,需要一种使多待移动终端能够使用不同的无线通信网络进行电话会议的方法和装置。 发明内容 [0009] 本发明的一个方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一方面在于提供一种多待移动终端以及使用该多待移动终端进行电话会议的方法,使得不同无线通信网络中的移动终端能够进行电话会议。 [0010] 根据本发明的一个方面,提供了一种多待移动终端。 该移动终端包括用于与第一无线通信网络形成通信信道的第一通信模块、用于与第二无线通信网络形成通信信道的第二通信模块、以及用于合成声音信号的第一混音器,从第一无线通信网络输入。 通信模块和麦克风,以合成声音信号,并将合成声音信号输出到第二通信模块。 [0011]根据本发明的另一方面,提供了一种执行电话会议的方法。 该方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中,第二移动终端是多待移动终端; 由存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信; 当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议, 将合成的声音信号发送给第三移动终端。 [0012] 本发明的其他方面、缺点和显着特征对于本领域技术人员而言将从以下详细描述中变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0013] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0014] 如图。 附图说明图1是示出根据本发明示例性实施例的使用多待移动终端的电话会议系统的图; [0015] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图; 和 [0016] 如图。 图3是示出根据本发明示例性实施例的用于执行电话会议的方法的流程图。 [0017] 在整个附图中,应当注意,相同的附图标记用于描述相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0018] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,省略了对众所周知的功能和结构的描述。 [0019] 以下描述和权利要求中使用的术语和词语不限于书目含义,而是仅由发明人使用以实现对本发明的清晰和一致的理解。 因此,本领域技术人员应该清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0020] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0021] 在以下描述中,描述了可以与CDMA无线通信网络和GSM无线通信网络进行通信连接的双待移动终端,例如多待移动终端。 然而,本发明不限于此。 即,根据本发明示例性实施例的多待机移动终端可以执行与各种无线通信网络的通信连接,例如通用分组无线服务(GPRS)、增强型数据GSM环境(EDGE)、通用 移动电信系统 (UMTS) 和宽带码分多址 (WCDMA)。 [0022]参照附图描述根据本发明示例性实施例的多待移动终端的配置以及使用多待移动终端执行电话会议的方法。 [0023] 如图。 图1是图示根据本发明示例性实施例的使用多待移动终端的电话会议系统的图。 [0024] 参考图。 1、第一个移动终端 100 是支持GSM无线通信网络的移动终端 150 ,第三个移动终端 300 是支持CDMA无线通信网络的移动终端 350 和第二个移动终端 200 是支持GSM和CDMA无线通信网络的多待机移动终端 150 和 350 . 第一个移动终端 100 第三个移动终端 300 也可以是多待移动终端。 [0025] 在下面的描述中,在第一移动终端 100 第二移动终端 200 连接进行通信,如果第三个移动终端 300 请求多人之间的通信,假设第二个移动终端 200 可以执行电话会议功能。 即,在第二移动终端 200 和第一个移动终端 100 使用 GSM 无线通信网络进行通信 150 , 第三个移动终端 300 可通过 CDMA 无线通信网络请求 350 , 几个人之间的通信到第二个移动终端 200 . 或者,第二移动终端 200 可以向第三移动终端请求多人之间的通信 300 . 在这种情况下,第二移动终端的电话会议功能 200 被激活。 这样,第一移动终端之间的通信 100 ,第二个移动终端 200 第三个移动终端 300 可以执行。 [0026] 第二移动终端的电话会议功能 200 稍后将参考图10进行描述。 2. [0027] 开启电话会议功能时,如果第一移动终端的声音信号 100 发送到第二移动终端 200 ,第二个移动终端 200 合成自己的声音信号和第一移动终端的声音信号 100 使用混音器将合成的声音信号发送给第三移动终端 300 . 即第三移动终端 300 可以接收第二移动终端的声音信号 200 和第一个移动终端 100 通过合成的声音信号。 [0028] 同理,如果第三移动终端的声音信号 300 发送到第二移动终端 200 ,第二个移动终端 200 可以合成自己的声音信号和第三移动终端的声音信号 300 使用音频混音器。 第二个移动终端 200 然后将合成的声音信号发送给第一移动终端 100 . 即第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 通过合成的声音信号。 [0029] 第二个移动终端 200 合成从第一移动终端发送的声音信号 100 第三移动终端发送的声音信号 300 使用音频混合器并通过第二移动终端的扬声器(SPK)输出合成的声音信号 200 . 由此,第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 ,第二个移动终端 200 可以接收第一移动终端的声音信号 100 第三个移动终端 300 ,以及第三个移动终端 300 可以接收第一移动终端的声音信号 100 第二移动终端200 . 因此,可以执行电话会议。 [0030] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图。 [0031] 如图。 如图2所示,作为多待移动终端 200 根据本发明的示例性实施例,提供一种可以与GSM无线通信网络和CDMA无线通信网络进行通信连接的双待移动终端。 然而,本发明的多待移动终端不限于双待移动终端。 [0032] 双待移动终端可以具有安装CDMA卡和GSM卡的插槽,或者一个用于安装集成了CDMA卡和GSM卡的双卡的插槽。 [0033] 参考图。 2、双待移动终端(以下简称第二移动终端 200 )根据本发明的示例性实施例包括第一天线 401 ,第二根天线 402 ,第一通信模块 410 ,第二个通信模块 420 , 一个控制器 450 和一个混音器 460 包括第一个混音器 461 ,第二个音频混音器 462 和第三个混音器 463 . [0034] 第一个天线 401 通过 GSM 无线通信网络发送和接收声音信号和数据 150 并接收用于GSM无线通信网络的频率 150 . [0035] 第二个天线 402 通过CDMA无线通信网络发送和接收声音信号和数据 350 并接收用于CDMA无线通信网络的频率 350 . [0036] 如图。 图2说明了第一天线 401 和第二根天线 402 作为单独的天线。 但是第一个天线 401 和第二根天线 402 可以形成为一个天线。 当第一根天线 401 和第二根天线 402 组成一根天线,双待移动终端 200 包括用于将频带划分为CDMA频带和GSM频带的装置。 例如双待移动终端 200 使用双工器(未示出)将天线接收到的信号分成CDMA频带的信号和GSM频带的信号。 双待移动终端 200 将GSM频段的信号传输给第一通信模块 410 以及CDMA频段的信号到第二通信模块 420 . [0037] 第一通讯模块 410 第二通信模块 420 每个都包括用于划分发送/接收信号的发送/接收信号分配器(未示出)、用于对要发送的信号的频率进行上变频和放大信号的射频(RF)发送器(未示出)、RF 接收器(未示出)用于低噪声放大接收信号并下变频信号的频率,以及用于调制和解调声音信号的调制解调器。 [0038] 以下,为了描述方便,假设第一通信模块 410 与GSM无线通信网络形成通信通道 150 向第一移动终端发送和从第一移动终端接收无线信号 100 使用GSM无线通信方法。 此外,第二通信模块 420 与CDMA无线通信网络形成通信通道 350 向第三移动终端发送和从第三移动终端接收无线信号 300 使用CDMA无线通信方法。 [0039] 第一通讯模块 410 解调从第一移动终端接收到的无线信号 100 调制从第二移动终端的麦克风(MIC)输入的声音信号 200 到无线信号。 更具体地,在进行电话会议时,第一通信模块 410 调制第二移动终端的声音信号200 第三移动终端的声音信号 300 在混音器中合成 460 将调制后的声音信号发送给第一移动终端 100 . [0040] 第二通讯模块 420 解调从第三移动终端接收的无线信号 300 调制从第二移动终端的MIC输入的声音信号 200 到无线信号。 更具体地说,当进行电话会议时,第二通信模块 420 调制第二移动终端的声音信号 200 以及第一移动终端的声音信号 100 在混音器中合成 460 将调制后的声音信号发送给第三移动终端 300 . [0041] 控制器 450 控制第二移动终端的一般操作 200 第二移动终端的元件的信号流 200 . 更具体地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 . 更详细地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 与 GSM 通信网络进行通信连接 150 和CDMA通信网络 350 , 分别。 当第一通信模块接收到通信连接请求时 410 或第二通信模块 420 , 控制器 450 激活相应的第一通信模块 410 或第二个通信模块 420 进行通信。 [0042] 进一步地,在第一移动终端 100 第二移动终端 200 通过GSM无线通信网络进行通信 150 ,如果是第三个移动终端 300 通过 CDMA 无线通信网络请求多人之间的通信 350 , 控制器 450 第二个移动终端 200 执行电话会议功能。 如果收到来自第三移动终端的通信请求 300 不是几个人之间的通信请求,控制器 450 执行单独的通信功能。 即,为了与第三移动终端进行单独通信 300 , 控制器 450 终止第一通信模块的通信连接功能以外的功能 410 . 此外,控制器 450 控制音频混音器 460 阻止与第一移动终端之间的声音信号的发送和接收 100 . [0043] 类似地,为了与第一移动终端进行单独的通信 100 , 控制器 450 终止第二通信模块的通信连接功能以外的功能 420 ,并阻止与第三移动终端之间的声音信号的发送和接收 300 . [0044] 控制器 450 可以执行电话会议功能以激活第一通信模块 410 第二通信模块 420 . 具体来说,当控制器 450 激活第一个通信模块 410 第二通信模块 420 ,第一移动终端的声音信号 100 在第二个移动终端中调制 200 ,调制后的声音信号与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第三移动终端 300 . 同样,第三移动终端的声音信号 300 与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第一移动终端 100 . 从而,在不同无线通信网络中的移动终端之间进行语音通信的电话会议。 [0045] 当第一个移动终端 100第二移动终端 200 执行单独的通信,控制器 450 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0046] 在进行电话会议时,与第一移动终端中的任一个通信时 100 或者第三个移动终端 300 终止,控制器 450 控制混音器的电话会议终止功能 460 . 稍后描述其详细描述。 [0047] 控制器 450 可以包括在第一通信模块中 410 或在第二个通讯模块中 420 . 在这种情况下,通信模块 410 或者 420 包括控制器 450 成为主要的通信模块,控制整个系统的信号流,包括另一个通信模块的信号流。 [0048] 进行电话会议时,第一个混音器 461 合成第一移动终端的声音信号 100 从第一通信模块接收 410 以及从第二移动终端的MIC接收到的声音信号 200 . 第一个混音器 461 将合成的声音信号输出到第二通信模块 420 . 合成声音信号输出至第二通信模块 420 调制后发送到第三移动终端 300 通过第二根天线 402 . 即在进行电话会议时,第一移动终端的声音信号 100 输入到第一个混音器 461 ,通过第一通讯模块 410 第二个移动终端 200 ,并由第一个混音器合成 461 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第二通信模块 420 第二个移动终端 200 并传送至第三移动终端 300 通过第二根天线 402 . [0049] 进行电话会议时,与第三移动终端通信时 300 终止,第一个混音器 461 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第一混音器 461 仅在与第三移动终端进行通信时激活 300 . [0050] 第二个混音器 462 合成第一移动终端的声音信号 100 第一个通信模块的输出 410 第三移动终端的声音信号 300 第二通信模块的输出 420 . 合成的声音信号通过第二移动终端的扬声器(SPK)输出 200 . SPK可以安装在移动终端上,也可以是移动终端的耳机或接收合成声音信号的单独的音频扬声器。 [0051] 第三个混音器 463 合成第三移动终端的声音信号 300 从第二通信模块接收 420 以及从第二移动终端的MIC接收到的声音信号 200 . 第三个混音器 463 将合成的声音信号输出到第一通信模块 410 . 合成声音信号输出至第一通讯模块 410 被调制并发送到第一移动终端 100 ,通过第一根天线 401 . 即在进行电话会议时,第三移动终端的声音信号 300 输入到第三个混音器 463 通过第二个通信模块 420 第二个移动终端 200并由第三个混音器合成 463 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第一通信模块 410 第二个移动终端 200 并传送至第一移动终端 100 从第一根天线 401 . [0052] 在进行电话会议时,与第一移动终端通信时 100 终止,第三个混音器 463 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第三混音器 463 仅在与第一移动终端进行通信时激活 100 . [0053] 如图。 图3是示出根据本发明示例性实施例的执行电话会议的方法的流程图。 [0054] 参考图。 1到3、第一移动终端 100 第二移动终端 200 通过 GSM 无线通信网络连接进行通信 150 在步骤 S 500 . 在这种情况下,第二移动终端 200 向第一移动终端发送和从第一移动终端接收无线信号 100 从第一根天线 401 和第一通信模块 410 . [0055] 控制器 450 第二个移动终端 200 控制第二通信模块 420 等待通信连接请求。 此外,当与第一移动终端形成通信信道时 100 , 控制器 450 第二个移动终端 200 激活第二个混音器 462 和第三个混音器 463 并维持第一个混音器 461 处于非活动状态。 具体地,当第一移动终端 100 第二移动终端 200 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 第二个移动终端 200 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0056] 第三个移动终端 300 请求与第二移动终端的通信 200 通过CDMA无线通信网络 350 在步骤 S 502 . 尽管图 1 中未显示。 3、备选第二个移动终端 200 可以请求与第三移动终端的通信 300 通过CDMA无线通信网络 350 . [0057] 当来自第三移动终端的通信请求时 300 收到,控制器 450 第二个移动终端 200 通知第二移动终端的用户接收到通信请求 200 例如,通过控制显示单元显示接收到来自另一无线通信网络的通信连接请求或者通过输出接收声音。 [0058] 第二个移动终端 200 根据从CDMA无线通信网络接收到的通信请求,确定是否进行电话会议 350 在步骤 S 504 . [0059] 如果不进行电话会议,则第二移动终端 200 与第一移动终端进行单独通信 100 或者第三个移动终端 300 ,根据用户在步骤S中的选择 506 . 通过控制第一通信模块进行单独通信 410 第二通信模块 420 . 例如,当与第一移动终端单独通信时 100旨在,控制器 450 第二个移动终端 200 控制以仅维持第二通信模块的通信连接状态 420 并关闭其他功能。 [0060] 如果在步骤S中确定要进行电话会议 504 ,第二个移动终端 200 在步骤 S 中激活电话会议功能 508 . 控制器 450 激活第一个通信模块 410 第二通信模块 420 第二个移动终端 200 , 并激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0061] 第二个移动终端 200 连接用于与第三移动终端通信 300 在CDMA无线通信网络中 350 在步骤 S 510 ,从而与第一移动终端形成电话会议 100 第三个移动终端 300 . [0062] 第一移动终端之间进行电话会议时 100 第三个移动终端 300 , 第一个混音器 461 第二个移动终端 200 合成第一移动终端的声音信号 100 第二移动终端的声音信号 200 并将合成声音信号输出至第二通信模块 420 . 第一移动终端的输出声音信号 100 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第三移动终端 100 从第二根天线 402 . [0063] 第三个混音器 463 第二个移动终端 200 合成第三移动终端的声音信号 300 第二移动终端的声音信号 200 并将合成声音信号输出至第一通讯模块 410 . 第三移动终端的输出声音信号 300 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第一移动终端 100 从第一根天线 401 . [0064] 第二个混音器 462 第二个移动终端 200 合成第三移动终端的声音信号 300 以及第一移动终端的声音信号 100 . 第二个混音器 462 通过第二移动终端的SPK输出合成的声音信号 200 . [0065] 在进行电话会议时,在第一移动终端之间进行通信时 100 第二移动终端 200 终止,控制器 450 第二个移动终端 200 终止第三个混音器的功能 463 以防止不必要的功耗。 或者,当第二移动终端之间进行通信时 200 第三个移动终端 300 终止,控制器 450 第二个移动终端 200 终止第一个混音器的功能 461 以防止不必要的功耗。 [0066] 如上所述,根据本发明示例性实施例的多待机移动终端可以与使用不同无线通信网络的移动终端进行电话会议。 因此,可以在不订阅附加服务的情况下执行电话会议。 因此,可以提高用户便利性。 [0067] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String), 111524(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.571 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.572 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.572 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.574 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.575 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.575 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.576 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.577 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.577 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.578 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.579 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.579 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), CN101489322A(String), 1046981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.580 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.581 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.581 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), EP2081370A1(String), 1046982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.582 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.582 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.583 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), KR1020090079379A(String), 1046983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.584 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.584 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.584 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), US20090186607A1(String), 1046984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.585 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.586 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.586 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20090186607A1(String), US20090186607A1(String), 1248278400(Integer), 270636(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.587 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.588 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.588 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.590 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.591 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.592 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.593 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.594 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.594 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.603 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.603 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.603 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.613 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.614 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.616 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974672(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.617 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.618 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.618 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184953(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.627 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.627 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.628 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75902(Integer), 2(Integer), 184953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.637 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.639 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.639 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.640 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.640 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.641 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.643 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.644 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.644 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.646 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.646 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.646 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.647 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.647 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.648 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.649 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.649 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.649 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.661 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.662 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.662 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.670 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.672 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.672 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120276924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.675 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.676 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.676 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.685 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.687 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.687 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0a6d970781c446068310e44c8df0c3a6.png(String), 184954(Integer), 0a6d970781c446068310e44c8df0c3a6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.698 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.699 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.699 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.700 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.701 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.701 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System and method for positioning mobile terminal, and mobile terminal(String), 移动终端定位系统、方法及移动终端(String), US20120276924A1(String), The disclosure discloses a method for positioning a mobile terminal, which comprises: a server sends a push notification to a mobile terminal; the mobile terminal performs self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal, and sends the geographical position information to the server; the server receives and displays the geographical position information sent by the mobile terminal. The disclosure also discloses a system for positioning a mobile terminal for implementing the method for positioning a mobile terminal and a mobile terminal. With such method and device, the server can be used to send a push notification to the mobile terminal after a user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal.(String), 本发明公开了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端收到推送通知后进行自我定位,获取移动终端的地理位置信息,并将地理位置信息发送给服务器。 服务器接收并显示移动终端发送的地理位置信息。 本发明还公开了一种用于实现上述移动终端定位方法的移动终端定位系统及移动终端。 通过这样的方法和装置,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位其地理位置信息,并将地理位置信息发送至服务器,以帮助用户检索移动终端。(String), US13/519896(String), 1279468800(Integer), US20120276924A1(String), 1351699200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 4(Integer), US20070015505A1 | US20080293397A1 | US20080320573A1 | US20120142329A1(String), \20230420\0a6d970781c446068310e44c8df0c3a6.png(String), 16(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.709 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.710 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.710 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.721 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.722 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.722 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 1. A method for positioning a mobile terminal, comprising:sending, by a server, a push notification to a mobile terminal;performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal;sending, by the mobile terminal, the geographical position information to the server; andreceiving and outputting, by the server, the geographical position information sent by the mobile terminal.(String), 1.根据权利要求9所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.723 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 2. The method according to claim 1, further comprising: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal,sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andperforming, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command.(String), 12.根据权利要求2所述的方法,还包括:在服务器向移动终端发送推送通知的步骤之前,移动终端在检测到SIM卡被更换后,向服务器发送移动终端的国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息正在启动。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.723 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 3. The method according to claim 1, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 13.根据权利要求12所述的方法,还包括:服务器根据接收到的移动终端的IMEI与IMSI的匹配信息,更新之前的移动终端的IMEI与IMSI的匹配信息,并进一步判断更新后的IMEI是否为在服务器注册的移动终端的IMEI。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.723 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 4. The method according to claim 3, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 14.根据权利要求6所述的系统,其中移动终端还包括SIM卡检测模块和匹配信息发送模块,其中SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.723 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 5. A system for positioning a mobile terminal, comprising a server and a mobile terminal, whereinthe server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; andthe mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 15.根据权利要求14所述的系统,其中服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前移动终端的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为移动终端在服务器注册的IMEI.16.根据权利要求10所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.723 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.724 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 6. The system according to claim 5, whereinthe server is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andthe mobile terminal further comprises a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.724 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 7. The system according to claim 5, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.724 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 8. The system according to claim 7, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.724 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 9. A mobile terminal, comprising a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.724 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 10. The mobile terminal according to claim 9, further comprising a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.725 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 11. The mobile terminal according to claim 9, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.725 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 12. The method according to claim 2, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.725 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 13. The method according to claim 12, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.725 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 14. The system according to claim 6, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 13(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.726 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 15. The system according to claim 14, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.726 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 16. The mobile terminal according to claim 10, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.863 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.863 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.868 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.868 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.868 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111525(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.873 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.874 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.874 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184954(Integer), TECHNICAL FIELD [0001]The disclosure relates to the technology of mobile communications, particularly to a system and method for positioning a mobile terminal and to a mobile terminal. BACKGROUND [0002]With the continuous development of mobile communication technologies, a mobile terminal, such as a mobile phone, a Personal Digital Assistant (PDA) and the like is no longer used as a simple communication tool only. Because the above mobile terminal has advantages of small volume, easiness in taking, convenience in use and the like, it has gradually become a personal information storage carrier for the user. Many users of the mobile terminal get used to storing important personal information involving personal information security, such as contacts, photos, schedules and the like in the mobile terminal. [0003]After the mobile terminal is lost, its operator cannot help the user retrieve the lost mobile terminal because the operator only provides Subscriber Identity Module (SIM) card loss reporting and re-issuing services, and cannot provide specific position information of the mobile terminal. SUMMARY [0004]The disclosure mainly aims to provide a system and method for positioning a mobile terminal, and also provide a mobile terminal, with which geographical position information of a lost mobile terminal can be provided to a user to help the user retrieve the mobile terminal. [0005]The disclosure provides a method for positioning a mobile terminal, which comprises: sending, by a server, a push notification to a mobile terminal; performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal; sending, by the mobile terminal, the geographical position information to the server; and receiving and outputting, by the server, the geographical position information sent by the mobile terminal. [0006]Preferably, the method may further comprise: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal, sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and performing, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command. [0007]Preferably, the method may further comprise: before the step of sending, by the server, the push notification to the mobile terminal, sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started. [0008]Preferably, the method may further comprise: updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0009]A system for positioning a mobile terminal, comprises a server and a mobile terminal, wherein the server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; and the mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0010]Preferably, the server may be further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command. [0011]Preferably, the mobile terminal may further comprise a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, wherein the SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; and the matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed. [0012]Preferably, the server may be further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0013]A mobile terminal comprises a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0014]Preferably, the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server. [0015]Preferably, the mobile terminal may further comprise: a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; and a matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed. [0016]With the system and method for positioning a mobile terminal, and the mobile terminal provided by the disclosure, the server can be used to send a push notification to the mobile terminal after the user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0017]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure; [0018]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure; [0019]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure; [0020]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure; [0021]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure; and [0022]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0023]The achievement of the purpose of the disclosure, functional characteristics and advantages of the disclosure will be described with reference to the embodiments and drawings in detail. DETAILED DESCRIPTION [0024]The technical solution of the disclosure is described below with reference to the drawings of the description and the specific embodiments in detail. [0025]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure. [0026]After a mobile terminal is lost, when a finder or a thief does not turn off the mobile terminal, its user logs in a server in time to report loss, and registers an International Mobile Equipment Identity (IMEI) of the mobile terminal. As shown in FIG. 1, a method for protecting data in a mobile terminal of the disclosure comprises the following steps. [0027]Step S101: a server sends a push notification to a mobile terminal. [0028]In this embodiment, the push notification can be sent to the mobile terminal through the server so as to notify the mobile terminal to be positioned via the push notification. In addition, the mobile terminal is registered with an inbound network connection for a positioning program, and the mobile terminal monitors whether the push notification sent by the monitoring mobile terminal is received on the registered inbound network connection. The inbound network connection is registered for the positioning program in a static registration manner or a dynamic registration manner. The static registration will be taken as an example in this embodiment for description. [0029]The server inquires an International Mobile Subscriber Identity (IMSI) of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends the push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0030]Furthermore, a Java Application Description (JAD) file of the mobile terminal is further provided with the MIDlet-Push-<1>attribute, for example the attribute is set as: [0031]MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; after the attribute is added, it indicates a connection protocol adopted is a Short Messaging Service (SMS) protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0032]Step S102: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0033]In the embodiment, the positioning program is a location Application Programming Interface (API) for Java 2 Micro Edition (J2ME) program, which meets Java Specification Request (JSR) 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a Global Positioning System (GPS), a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0034]Step S103: the mobile terminal sends the geographical position information to the server. [0035]In the embodiment, the geographical position information comprises longitude and latitude information of the mobile terminal. [0036]Step S104: the server receives and displays the geographical position information sent by the mobile terminal. [0037]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0038]Step S105: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0039]In the embodiment, the server sends a Lock And Wipe Management Object (LAWMO) command to the mobile terminal according to a Device Management (DM) protocol defined by Open Mobile Alliance (OMA). The server sends the locking command to the mobile terminal through the device management protocol in a Synchronization Markup Language (SyncML) protocol set. [0040]Step S106: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S105 and step S106 are not the necessary steps. [0041]In the embodiment, the server can be used to send the push notification to the mobile terminal after the user finds the mobile terminal is lost; the mobile terminal positions the geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. [0042]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure. [0043]When a mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change a Subscriber Identity Module (SIM) card, when the finder or the thief turns on the mobile terminal again, the mobile terminal will protect data based on the following steps. [0044]Step S201: the mobile terminal detects whether an SIM card is changed after being started; if yes, turn to step S202; otherwise, turn to step S205. [0045]In the embodiment, after the mobile terminal is started, it automatically starts the SIM card verification kit to verify whether the IMSI of the SIM card is changed; if yes, it indicates the SIM card of the mobile terminal is changed. The method for automatically starting the SIM card detection function after startup is as follows: [0046]the MIDlet-1-Type:autostart attribute is added in the Java application description file of the terminal, and meanwhile an autostart permission is also added in the Java application description file in the specific format of: [0047]MIDlet-Permissions:javax.microedition.midlet.AutoStart Permission. [0048]Step S202: the mobile terminal sends matching information between an IMEI and an IMSI to the server. [0049]In the embodiment, the mobile terminal sends matching information between an IMEI and an IMSI to a server through a short message. [0050]Step S203: the server updates the matching information between the IMEI and the IMSI of the mobile terminal. [0051]In the embodiment, after receiving the short message, the server updates the matching information between the IMEI and the IMSI of the mobile terminal through modifying an IMSI number corresponding to the IMEI of the mobile terminal. [0052]Step S204: the server judges whether the updated IMEI is an IMEI of the mobile terminal registered at the server; if yes, turn to step S205; otherwise, the flow is terminated. [0053]Step S205: the server sends a push notification to the mobile terminal. [0054]In the embodiment, the server inquires an IMSI number of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends a push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0055]In addition, the Java application description file of the mobile terminal is provided with the MIDlet-Push-<1>attribute, which is: [0056]MIDlet-Push-1:sms://:8080, MIDletLocation, 13900000000. After the attribute is added, it indicates a connection protocol adopted is an SMS protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0057]Step S206: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0058]In the embodiment, the positioning program is a location API for J2ME program, which meets JSR 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a GPS, a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0059]Step S207: the mobile terminal sends the geographical position information to the server. [0060]In the embodiment, the geographical position information comprises at least longitude and latitude information of the mobile terminal. [0061]Step S208: the server receives and displays the geographical position information sent by the mobile terminal. [0062]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0063]Step S209: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0064]In the embodiment, the server sends an LAWMO command to the mobile terminal according to a device management protocol defined by open mobile alliance. The server sends the locking command to the mobile terminal through the device management protocol in a SyncML protocol set. [0065]Step S210: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S209 and step S210 are not the necessary steps. [0066]In the embodiment, when the mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal; the mobile terminal positions geographical position information thereof after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal. Therefore, data in the lost mobile terminal is prevented from being leaked, and personal information security of the user is ensured. [0067]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure. [0068]The system for positioning a mobile terminal comprises a server 10 and a mobile terminal 20, wherein the mobile terminal 20 comprises a positioning module 201. [0069]The server is configured to send a push notification to the mobile terminal 20, and to receive geographical position information sent by the mobile terminal 20; the positioning module 201 is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal 20, and to send the geographical position information to the server 10. [0070]In the embodiment, the server 10 can be used to send a push notification to the mobile terminal 20 after the user finds that the mobile terminal 20 is lost. The mobile terminal 20 locates geographical position information thereof through the positioning module 201 and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. [0071]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure. [0072]The server 10 is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol. Besides the positioning module 201, the mobile terminal 20 further comprises a locking module 205 and a deleting module 204, an SIM card detecting module 202 and a matching information sending module 203. [0073]The locking module 205 is configured to lock the mobile terminal 20 after receiving the locking command. The deleting module 204 is configured to delete data in a memory after receiving the deleting command. The SIM card detecting module 202 is configured to detect whether an SIM card of the mobile terminal is changed. The matching information sending module 203 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card is changed. [0074]The server 10 is further configured to update the matching information between the IMEI and the IMSI of the mobile terminal 20 registered at the server after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server 10. [0075]In the embodiment, after the mobile terminal 20 is lost, if a finder or a thief turns off the mobile terminal 20 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 20 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 20 is changed; if the SIM card is not changed, the server 10 is directly used to send a push notification to the mobile terminal 20; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 20; the mobile terminal 20 positions geographical position information thereof through the positioning module 201 after receiving the push notification, and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. Therefore, data in the mobile terminal 20 is prevented from being leaked, and personal information security of the user is ensured. [0076]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure. [0077]The mobile terminal 30 comprises a positioning module 301, which is configured to perform self-positioning after receiving a push notification to acquire geographical position information regarding the mobile terminal 30, and send the geographical position information to a server. [0078]In the embodiment, the server can be used to send a push notification to the mobile terminal 30 after the user finds that the mobile terminal 30 is lost. The mobile terminal 30 positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal 30. [0079]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0080]Besides the positioning module 301, the mobile terminal 40 further comprises a locking module 302, a deleting module 303, an SIM card detecting module 304, and a matching information sending module 305. [0081]The locking module 302 is configured to lock the mobile terminal 40 after receiving a locking command sent by a server; the deleting module 303 is configured to delete data in a memory after receiving a deleting command sent by the server. The SIM card detecting module 304 is configured to detect whether an SIM card is changed. The matching information sending module 305 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card of the mobile terminal is changed. [0082]In the embodiment, after the mobile terminal 40 is lost, if a finder or a thief turns off the mobile terminal 40 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 40 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 40 is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal 40; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 40; the mobile terminal 40 positions geographical position information thereof through the positioning module 301 after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal 40. Therefore, data in the mobile terminal 40 is prevented from being leaked, and personal information security of the user is ensured. [0083]The above is only the preferred embodiment of the disclosure and not intended to limit the scope of the patent, and any equivalent structure or equivalent flow transformation based on the description and drawings of the disclosure, which is directly or indirectly applied in other related technical fields shall fall within the scope of patent protection of the disclosure.(String), 技术领域 [0001] 本发明涉及移动通信技术,尤其涉及一种移动终端定位系统、方法及移动终端。 背景 [0002] 随着移动通信技术的不断发展,移动终端,如手机、个人数字助理(Personal Digital Assistant,PDA)等,不再仅仅是一种简单的通信工具。 由于上述移动终端具有体积小、携带方便、使用方便等优点,逐渐成为用户个人信息的存储载体。 很多移动终端的用户习惯于在移动终端中存储联系人、照片、日程等涉及个人信息安全的重要个人信息。 [0003] 移动终端丢失后,其运营商无法帮助用户找回丢失的移动终端,因为运营商仅提供SIM卡挂失和补发服务,无法提供移动终端的具体位置信息。 概括 [0004] 本发明的主要目的在于提供一种移动终端的定位系统及方法,还提供一种移动终端,能够将丢失的移动终端的地理位置信息提供给用户,以帮助用户找回移动终端。 [0005] 本发明提供了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端接收到推送通知后进行自定位,获取移动终端的地理位置信息; 移动终端向服务器发送地理位置信息; 服务器接收并输出移动终端发送的地理位置信息。 [0006] 优选地,该方法还包括: 在服务器接收并输出移动终端发送的地理位置信息的步骤之后,服务器根据移动终端发送锁定命令和/或删除命令。 设备管理协议; 移动终端在接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 [0007] 优选地,该方法还包括: 在服务器向移动终端发送推送通知之前,移动终端发送国际移动设备识别码(IMEI)与国际移动用户识别码的匹配信息。 移动终端(IMSI)在启动后检测到SIM卡被更换时发送给服务器。 [0008] 优选地,该方法还包括:服务器根据接收到的移动终端的IMEI和IMSI的匹配信息更新之前的移动终端的IMEI和IMSI的匹配信息,进一步判断, 服务器,更新后的IMEI是否为在服务器注册的移动终端的IMEI。 [0009] 一种移动终端定位系统,包括服务器和移动终端,服务器用于向移动终端发送推送通知,并接收移动终端发送的地理位置信息; 移动终端还包括定位模块,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0010] 优选地,服务器还可以用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 移动终端还可以包括锁定模块和删除模块,锁定模块用于接收到锁定命令后锁定移动终端。 删除模块,用于接收到删除命令后,删除移动终端内存中的数据。 [0011] 优选地,所述移动终端还包括SIM卡检测模块和匹配信息发送模块,所述SIM卡检测模块用于检测所述移动终端的SIM卡是否被更换。 匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。 [0012] 优选地,服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为注册的移动终端的IMEI 在服务器上。 [0013] 一种移动终端,包括定位模块,用于接收到服务器的推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0014] 优选地,所述移动终端还包括锁定模块和删除模块,所述锁定模块用于接收到所述服务器发送的锁定命令后,锁定所述移动终端。 删除模块,用于接收到服务器发送的删除命令后,删除移动终端内存中的数据。 [0015] 优选地,所述移动终端还包括: SIM卡检测模块,用于检测所述移动终端的SIM卡是否被更换; 匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码(IMEI)和国际移动用户识别码(IMSI)的匹配信息。 [0016] 本发明提供的移动终端定位系统、方法及移动终端,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 附图的简要说明 [0017] 图1为本发明移动终端数据保护方法实施例的流程示意图; [0018] 图2为本发明移动终端数据保护方法另一实施例的流程示意图; [0019] 图3示出了本发明移动终端定位系统实施例的结构示意图; [0020] 图4为本发明移动终端定位系统另一实施例的结构示意图; [0021] 图5示出了本发明移动终端一个实施例的结构示意图; 和 [0022] 图6示出了本发明移动终端另一实施例的结构示意图。 [0023] 本发明目的的实现、功能特点和优点将结合实施例和附图进行详细说明。 详细说明 [0024] 下面结合说明书附图和具体实施例对本发明的技术方案进行详细说明。 [0025] 图1示出了本发明移动终端数据保护方法实施例的流程示意图。 [0026] 移动终端丢失后,当捡到者或小偷没有关闭移动终端时,其用户及时登录服务器挂失,并注册移动终端的国际移动设备识别码(IMEI)。 如图1所示,本发明的移动终端中的数据保护方法包括以下步骤。 [0027] 脚步 101:服务器向移动终端发送推送通知。 [0028] 本实施例中,可以通过服务器向移动终端发送推送通知,以通过推送通知通知移动终端进行定位。 另外,移动终端注册有定位程序的入站网络连接,移动终端监听是否在注册的入站网络连接上接收到监控移动终端发送的推送通知。 入站网络连接以静态注册方式或动态注册方式注册到定位程序。 本实施例以静态注册为例进行说明。 [0029] 服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI,根据IMSI号码获取移动终端的手机号码,然后发送推送通知给 移动终端根据手机号码要求移动终端进行定位。 [0030] 进一步地,移动终端的JAD文件中还设置有MIDlet-Push-<1>属性,例如该属性设置为: [0031] MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; 添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation,推送通知的有效源为服务器 13900000000个数。除了SMS协议之外,本发明当然还可以使用传输控制协议或用户数据报协议,本发明对此不作限制。 [0032] 脚步 102 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0033] 在本实施例中,定位程序为Java 2 Micro Edition(J2ME)程序的定位应用程序编程接口(API),其符合Java Specification Request(JSR)179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以利用基于全球定位系统(Global Positioning System,简称GPS)的卫星定位方法、蜂窝网络的定位方法、或者基于蓝牙的近距离定位方法,或者可以结合上述方法 礼貌。 [0034] 脚步 103 :移动终端向服务器发送地理位置信息。 [0035] 在本实施例中,地理位置信息包括移动终端的经纬度信息。 [0036] 脚步 104 :服务器接收并显示移动终端发送的地理位置信息。 [0037] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0038] 脚步 105 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0039] 在该实施例中,服务器根据开放移动联盟(OMA)定义的设备管理(DM)协议向移动终端发送锁定和擦除管理对象(LAWMO)命令。 服务器通过同步标记语言(SyncML)协议集中的设备管理协议向移动终端发送锁定命令。 [0040] 脚步 106 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S105 和步骤S 106 不是必要的步骤。 [0041] 本实施例中,可以通过服务器在用户发现移动终端丢失后向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 [0042] 图2示出了本发明移动终端数据保护方法另一实施例的流程示意图。 [0043] 当移动终端丢失时,如果捡到者或小偷因电池电量低或想更换用户身份模块(SIM)卡而关闭移动终端,当捡到者或小偷再次打开移动终端时, 移动端将按照以下步骤保护数据。 [0044] 脚步 201 :移动终端开机后检测SIM卡是否被更换; 如果是,转步骤S 202 ; 否则转步骤S 205 . [0045] 本实施例中,移动终端启动后,自动启动SIM卡验证工具,验证SIM卡的IMSI是否发生变化; 如果是,则说明移动终端的SIM卡已更换。 开机后自动启动SIM卡检测功能的方法如下: [0046] 在终端的Java应用描述文件中增加了MIDlet-1-Type:autostart属性,同时在Java应用描述文件中也增加了自动启动权限,具体格式为: [0047] MIDlet-权限:javax.microedition.midlet.AutoStart 权限。 [0048] 脚步 202 :移动终端向服务器发送IMEI和IMSI的匹配信息。 [0049] 本实施例中,移动终端通过短消息向服务器发送IMEI和IMSI的匹配信息。 [0050] 脚步 203 :服务器更新移动终端IMEI和IMSI的匹配信息。 [0051] 本实施例中,服务器接收到短消息后,通过修改移动终端的IMEI对应的IMSI号,更新IMEI与移动终端的IMSI的匹配信息。 [0052] 脚步 204 :服务器判断更新后的IMEI是否为在服务器注册的移动终端的IMEI; 如果是,转步骤S 205 ; 否则,流程终止。 [0053] 脚步 205 :服务器向移动端发送推送通知。 [0054] 在本实施例中,服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI号码,根据IMSI号码获取移动终端的手机号码,然后向客户端发送推送通知。 移动终端根据手机号码要求移动终端进行定位。 [0055] 另外,在移动端的Java应用描述文件中设置了MIDlet-Push-<1>属性,即: [0056] MIDlet-Push-1:sms://:8080,MIDletLocation,13900000000。添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation, 推送通知的有效来源为号码为13900000000的服务器。 除了SMS协议之外,本发明当然还可以采用传输控制协议或用户数据报协议,本发明对此不做限制。 [0057] 脚步 206 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0058]在本实施例中,定位程序为J2ME程序的定位API,符合JSR 179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以采用基于GPS的卫星定位方法、蜂窝网络的定位方法或基于蓝牙的近距离定位方法,也可以结合上述方式。 [0059] 脚步 207 :移动终端向服务器发送地理位置信息。 [0060] 在本实施例中,地理位置信息至少包括移动终端的经纬度信息。 [0061] 脚步 208 :服务器接收并显示移动终端发送的地理位置信息。 [0062] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0063] 脚步 209 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0064] 本实施例中,服务器根据开放移动联盟定义的设备管理协议向移动终端发送LAWMO命令。 服务器通过SyncML协议集中的设备管理协议向移动终端发送锁定命令。 [0065] 脚步 210 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S 209 和步骤S 210 不是必要的步骤。 [0066] 在本实施例中,当移动终端丢失时,如果捡到者或小偷因电池电量低或想换SIM卡而关闭移动终端,当捡到者或小偷再次打开移动终端时,手机 终端首先验证移动终端的SIM卡是否被更换; 若SIM卡未更换,则直接通过服务器向移动终端发送推送通知。 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知。 移动终端接收到推送通知后定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户检索移动终端。 从而避免了丢失移动终端中的数据泄露,保证了用户的个人信息安全。 [0067] 图3示出了本发明移动终端定位系统实施例的结构示意图。 [0068] 一种移动终端定位系统,包括服务器 10 和移动终端 20 , 其中移动终端 20 包括一个定位模块 201 . [0069] 服务器配置为向移动终端发送推送通知 20 ,接收移动终端发送的地理位置信息 20 ; 定位模块 201 用于接收到推送通知后进行自定位,以获取移动终端的地理位置信息 20 ,并将地理位置信息发送给服务器 10 . [0070] 在本实施例中,服务器 10 可用于向移动端发送推送通知 20 用户发现移动端后 20 丢失了。 移动端 20 通过定位模块定位其地理位置信息 201 并将地理位置信息发送给服务器 10帮助用户找回移动终端 20 . [0071] 图4示出了本发明移动终端定位系统另一实施例的结构示意图。 [0072] 服务器 10 还用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 除了定位模块 201 , 移动端 20 还包括锁定模块 205 和一个删除模块 204 , SIM卡检测模块 202 以及匹配的信息发送模块 203 . [0073] 锁定模块 205 配置为锁定移动端 20 收到锁定命令后。 删除模块 204 用于接收到删除命令后删除内存中的数据。 SIM卡检测模块 202 用于检测移动终端的SIM卡是否被更换。 匹配信息发送模块 203 用于在更换SIM卡时向服务器发送IMEI和IMSI的匹配信息。 [0074] 服务器 10 还用于更新移动终端的IMEI与IMSI的匹配信息 20 接收到IMEI与IMSI的匹配信息后在服务器注册,判断更新后的IMEI是否为在服务器注册的移动终端的IMEI 10 . [0075] 在本实施例中,移动终端后 20 丢失,如果发现者或小偷关闭移动终端 20 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 20 再次,移动终端首先验证移动终端的SIM卡是否为 20 已更改; 如果SIM卡没换过,服务器 10 直接用于向移动端发送推送通知 20 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 20 ; 移动终端 20 通过定位模块定位其地理位置信息 201 收到推送通知后,将地理位置信息发送给服务器 10 帮助用户找回移动终端 20 . 因此,移动终端中的数据 20 防止泄露,保障用户个人信息安全。 [0076] 图5示出了本发明移动终端一个实施例的结构示意图。 [0077] 移动端 30 包括一个定位模块 301 ,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息 30 ,并将地理位置信息发送给服务器。 [0078] 在本实施例中,服务器可以用于向移动终端发送推送通知 30 用户发现移动端后 30 丢失了。 移动端 30 对其地理位置信息进行定位,并将地理位置信息发送给服务器,以帮助用户检索移动终端 30 . [0079] 图6示出了本发明移动终端另一实施例的结构示意图。 [0080] 除了定位模块 301 , 移动端 40 还包括锁定模块 302 , 删除模块 303 , SIM卡检测模块 304 , 以及匹配的信息发送模块 305 . [0081] 锁定模块 302 配置为锁定移动端 40 收到服务器发送的锁定命令后; 删除模块 303 用于接收到服务器发送的删除命令后,删除内存中的数据。 SIM卡检测模块 304用于检测SIM卡是否被更换。 匹配信息发送模块 305 用于当移动终端的SIM卡更换时,向服务器发送IMEI和IMSI的匹配信息。 [0082] 在本实施例中,移动终端后 40 丢失,如果发现者或小偷关闭移动终端 40 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 40 再次,移动终端首先验证移动终端的SIM卡是否为 40 已更改; 若SIM卡未更换,则直接使用服务器向移动终端发送推送通知 40 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 40 ; 移动终端 40 通过定位模块定位其地理位置信息 301 收到推送通知后,将地理位置信息发送给服务器,帮助用户找回移动终端 40 . 因此,移动终端中的数据 40 防止泄露,保障用户个人信息安全。 [0083] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的范围,任何基于本发明的说明书和附图所作的等效结构或等效流程变换,直接或间接应用于其他相关技术领域 落入本发明的专利保护范围。(String), 111525(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.882 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.882 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.883 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.884 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.884 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.885 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.886 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.886 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.886 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.887 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.887 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.888 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), CN101835143A(String), 1046985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.889 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), EP2509375A1(String), 1046986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.890 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.891 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), EP2509375A4(String), 1046987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.892 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.893 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.893 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), US20120276924A1(String), 1046988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.894 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), WO2011137605A1(String), 1046989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.895 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.895 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.895 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120276924A1(String), US20120276924A1(String), 1351699200(Integer), 270637(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.896 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.897 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.897 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LI, JINMIN(String), XU, LING(String), SHI(String), YUE, HUI(String), 中兴通讯股份有限公司(String), LI JINMIN(String), XU LING(String), 德世股份有限公司(String), YUE HUI(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.899 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.899 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.899 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.901 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.902 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.902 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.909 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.909 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.910 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.921 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.922 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.923 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.935 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.935 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.935 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75904(Integer), 2(Integer), 184954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.947 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.947 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.948 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75905(Integer), 2(Integer), 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.957 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.958 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.958 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75906(Integer), 2(Integer), 184954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.971 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.972 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.972 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75907(Integer), 2(Integer), 184954(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.980 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.981 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.981 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.982 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.983 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.983 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.984 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.984 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.985 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75904(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.985 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.986 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.986 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.987 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.988 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.988 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.989 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.990 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.990 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.997 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.997 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:46.998 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.007 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.010 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.010 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.012 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.013 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.014 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.023 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.024 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.025 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\88f13d6817ac40659fb3aabe450a4fc5.png(String), 184955(Integer), 88f13d6817ac40659fb3aabe450a4fc5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.035 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.036 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.036 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.037 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.039 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.040 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of providing Karaoke service to mobile terminals using a wireless connection between the mobile terminals(String), 使用移动终端之间的无线连接向移动终端提供卡拉OK服务的方法(String), US7142807B2(String), A method of providing a Karaoke service to mobile terminals through wireless connection between them. The mobile terminals are grouped as a service group and one of them is designated as a master mobile terminal and the other mobile terminals as slave mobile terminals. The master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service content to be received from the Karaoke service provider in all the mobile terminals of the service group. If the master mobile terminal transmits a play command to the slave mobile terminals, all the mobile terminals start to play Karaoke music according to the service contents.(String), 一种通过移动终端之间的无线连接向移动终端提供卡拉OK服务的方法。 移动终端被分组为一个服务组,其中一个被指定为主移动终端,而其他移动终端被指定为从移动终端。 主移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制从服务组的所有移动终端中的卡拉OK服务提供商接收的服务内容。 如果主移动终端向从移动终端发送播放命令,则所有移动终端根据服务内容开始播放卡拉OK音乐。(String), US10/761970(String), 1074614400(Integer), US7142807B2(String), 1164643200(Integer), 1164643200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 3(Integer), 9(Integer), JP2000122671A | US5588842A | US5689081A | US5691494A | US5824934A | US5885085A | US6062868A | US6074215A | USRE37131E1(String), \20230420\88f13d6817ac40659fb3aabe450a4fc5.png(String), 15(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.047 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.048 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.048 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.058 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.059 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.060 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 1. A method of providing a Karaoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals having a wireless connection function to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating all other mobile terminals as slave mobile terminals;connecting the master mobile terminal to a Karaoke service provider through a mobile communication network and controlling service content to be received from theKaraoke service provider in all the mobile terminals of the service group; and playing Karaoke music according to the service content by all the mobile terminals in the service group when the master mobile terminal transmits a play command to the slave mobile terminals, wherein the master and slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 1.一种通过无线连接向移动终端提供卡拉OK服务的方法,包括步骤:将移动终端与具有无线连接功能的移动终端分组为一个服务组,以接收卡拉OK业务;指定其中一个移动终端为主移动终端;将所有其他移动终端指定为从属移动终端;通过移动通信网络将主移动终端连接到卡拉OK服务提供商,并控制从主移动终端接收的服务内容服务组所有移动终端中的卡拉OK服务商;主移动终端向从移动终端发送播放命令时,服务组内的所有移动终端根据服务内容播放卡拉OK音乐,其中主从移动终端根据导频时钟信号进行同步在播放步骤中同时播放。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.060 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 2. The method of claim 1, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 2.如权利要求1所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.060 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 3. The method of claim 1, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 3.如权利要求1所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.060 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 4. The method of claim 1, wherein the step of controlling the service content to be received comprises the steps of:searching for the service content from the Karaoke service provider;transmitting information about the service content to the slave mobile terminals in the service group; andreceiving the service content from the Karaoke service provider according to the service content information in the master mobile terminal and the slave mobile terminals to receive.(String), 4.如权利要求1所述的方法,其中控制接收服务内容的步骤包括:从卡拉OK服务提供商处搜索服务内容;向服务组中的从属移动终端发送服务内容信息;和主移动终端和从移动终端根据服务内容信息从卡拉OK服务商处接收服务内容。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 5. The method of claim 1, wherein the step of controlling the service content comprises the steps of:searching for the service content from the Karaoke service provider;receiving the service content from the Karaoke service provider in the master mobile terminal; andtransmitting the service content from the master mobile terminal to the slave mobile terminals by wireless connections between the master mobile terminal and the slave mobile terminals.(String), 5.如权利要求1所述的方法,其中控制服务内容的步骤包括以下步骤:从卡拉OK服务提供商处搜索服务内容;在主移动终端中接收来自卡拉OK服务提供商的服务内容;和通过主移动终端和从移动终端之间的无线连接将主移动终端的业务内容传输到从移动终端。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 6. A method of providing a Kraoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating the other mobile terminals as slave mobile terminals;receiving, in the slave mobile terminals, service contents from a Karaoke service provider under control of the master mobile terminal; andplaying Karaoke music according to the service contents if the slave mobile terminals receive a play command from the master mobile terminal, wherein the master and the slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 6.一种通过无线连接向移动终端提供Kraoke服务的方法,包括步骤:将移动终端与接收卡拉OK业务的移动终端分组为一个业务组;指定其中一个移动终端为主移动终端;指定其他移动终端为从移动终端;从属移动终端接收主移动终端控制下的卡拉OK服务商的服务内容;和如果从移动终端接收到主移动终端的播放命令,则根据业务内容播放卡拉OK音乐,其中在播放步骤中,主从移动终端根据导频时钟信号同步同步播放。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 7. The method of claim 6, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 7.如权利要求6所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 8. The method of claim 6, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 8.如权利要求6所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 9. The method of claim 6, wherein the step ofreceiving the service contents, comprises the steps of:transmitting information about the service contents from the Karaoke service provider to the slave mobile terminals through the master mobile terminal; andconnecting the slave mobile terminals to the Karaoke service provider and transmitting the service contents to the slave mobile terminal.(String), 9.如权利要求6所述的方法,其中的步骤接收服务内容,包括以下步骤:将卡拉OK服务商的服务内容信息通过主移动终端传输给从移动终端;和将从移动终端连接到卡拉OK服务提供商,并将服务内容传输到从移动终端。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 10. The method of claim 6, wherein the slave mobile terminals receive the service contents from the master mobile terminal by the wireless connection.(String), 10.如权利要求6所述的方法,其中从移动终端通过无线连接从主移动终端接收服务内容。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.061 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 11. The method of claim 6, wherein the slave mobile terminals are further grouped as a predetermined number of sub-service groups according to a number of channels.(String), 11.如权利要求6所述的方法,其中从属移动终端根据频道数进一步分组为预定数量的子业务组。(String), 1(Integer), 10(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.062 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 12. The method of claim 11, wherein each of the sub-service groups receives different sound data and plays Karaoke music according to the sound data.(String), 12.如权利要求11所述的方法,其中每个子服务组接收不同的声音数据,并根据声音数据播放卡拉OK音乐。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.062 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 13. The method of claim 12, wherein the sound data is from one of a left channel and a right channel for stereo sound.(String), 13.如权利要求12所述的方法,其中声音数据来自立体声的左声道和右声道之一。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.062 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 14. The method of claim 12, wherein the sound data is from one of channels for digital surround sound 5.1.(String), 14.如权利要求12所述的方法,其中声音数据来自数字环绕声5.1的通道之一。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.062 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 15. The method of claim 12, wherein the sound data is from one of a predetermined number of sound sources divided from multiple sound sources.(String), 15.如权利要求12所述的方法,其中声音数据来自多个声源划分的预定数量的声源之一。(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.185 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.185 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.189 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.189 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.189 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111526(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.193 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.193 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.194 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184955(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119 to an application entitled “Method of Providing Karaoke Service to Mobile Terminals Using Wireless Connection between the Mobile Terminals” filed in the Korean Industrial Property Office on Feb. 13, 2003 and assigned Serial No. 2003-8989, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a method of providing a service through a mobile terminal, and in particular, to a method of providing a Karaoke service to a mobile terminal, and providing a computer-readable recording medium to record a program thereon for performing the Karaoke service method. [0004]2. Description of the Related Art [0005]Due to its portability and convenience, the mobile terminal has emerged as a necessity in daily living. Commonly, mobile terminals are equipped with a variety of functions including phonebook and scheduler. Accordingly, they serve as a personal information manager in addition to a means for making phone calls. 2.5th generation mobile terminals, based on IS (International Standard)-95C, and 3rd generation mobile terminals such as IMT (International Mobile Communication)-2000 terminals provide additional multimedia service for personal entertainment purposes. [0006]A Karaoke function, a type of personal entertainment service, plays songs across various genres with lyrics and animation through a mobile terminal. FIG. 1 illustrates a mobile communication system for providing a conventional Karaoke service. Referring to FIG. 1, the Karaoke service is provided over a typical mobile communication network. Hence, the Karaoke service is provided directly from a service provider (SP) over the mobile communication network rather than a service from the mobile communication network itself. [0007]The mobile communication system is comprised of a mobile terminal 11 for receiving the Karaoke service over the mobile communication network, a home location register (HLR) 12 and an authentication center (AC) 13 for providing the registration information of the mobile terminal 11, a mobile communication network 14 for connecting SPs to users, and a Karaoke SP 15 for providing the Karaoke service. [0008]In operation, the user of the mobile terminal 11 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 then authenticates the user through the HLR 12 and the AC 13 and provides the audio data stored in its database to the user. The mobile terminal 11 plays the song with its lyric displayed using the received audio data, enabling the user to sing along. [0009]In general, a user enjoys Karaoke music with others rather than alone. The volume of music that a single mobile terminal plays depends on its speaker and is usually not loud enough for a plurality of users to enjoy the music. In addition, no matter how good the speaker is, it cannot offer enough volume for them with the single sound source. [0010]In view of diverse voice services and rapid changes in their formats, the Karaoke SP 15 attempts to attract mobile subscribers with new features such as accompaniment with multichannel surround sound effects including stereo, or accompaniment with higher-note polyphonic sound through the existing mobile terminal limited to a 40-note polyphonic sound capacity. However, with the service deployment depending on the performance of an individual mobile terminal in the conventional technology, the benefits of those services are often elusive. SUMMARY OF THE INVENTION [0011]It is, therefore, an object of the present invention to provide a Karaoke service method using wireless connections between mobile terminals that are equipped with a Karaoke function, for playing music accompaniment concurrently through the mobile terminals by synchronizing them, and a computer-readable recording medium for recording a program thereon for performing the Karaoke service. [0012]It is another object of the present invention to provide a Karaoke service method for playing music with a high volume, surround sound effects, and various sound sources. [0013]The above and other objects are achieved by providing a method of providing a Karaoke service to a mobile terminal through wireless connections, and a computer-readable recording medium having a program thereon to perform the Karaoke service. [0014]According to one aspect of the present invention, in the Karaoke service method, the mobile terminal is grouped as a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group. The master mobile terminal transmits a play command to the slave mobile terminals, and all the mobile terminals start to play Karaoke music according to the service contents. [0015]According to another aspect of the present invention, in the Karaoke service method, a mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal. Upon receiving a play command from a master mobile terminal, it starts to play Karaoke music according to the service contents. [0016]According to a further aspect of the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. In the first function, a mobile terminal is grouped in a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal in the first function is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group in the second function. The master mobile terminal transmits a play command to the slave mobile terminals, and then all the mobile terminals start to play Karaoke music according to the service contents in the third function. [0017]According to still another aspect o the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. The program performs first, second, and third functions. In the first function, the mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and is designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal in the second function. Upon receiving a play command from the master mobile terminal, a slave mobile terminal starts to play Karaoke music according to the service contents in the third function. BRIEF DESCRIPTION OF THE DRAWINGS [0018]The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which: [0019]FIG. 1 illustrates a mobile communication system that provides a conventional Karaoke service to a mobile terminal; [0020]FIG. 2 illustrates the configuration of a mobile communication system that provides a Karaoke service to a plurality of mobile terminals through wireless connections between them according to an embodiment of the present invention; [0021]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention; [0022]FIG. 4 illustrates examples of screen displays in a mobile terminal for receiving the Karaoke service through wireless connection with other mobile terminals according to the embodiment of the present invention; and [0023]FIGS. 5A and 5B illustrate embodiments of contents reception for the Karaoke service through wireless connections with other mobile terminals according to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0024]Preferred embodiments of the present invention will be described in detail herein below with reference to the accompanying drawings. In the following description, well-known functions and constructions are not described in detail since they would obscure the invention in unnecessary detail. [0025]FIG. 2 illustrates a mobile communication system for providing a Karaoke service to mobile terminals through wireless connections between them according to an embodiment of the present invention. Referring to FIG. 2, the mobile communication system is comprised of a master mobile terminal 21 that receives the Karaoke service over a mobile communication network 14, slave mobile terminals 22 connected to the master mobile terminal 21, for receiving the same Karaoke service, the HLR 12 and the SC 13 for providing registration information for the mobile terminals 21 and 22, the mobile communication network 14 for connecting SPs to mobile subscribers, and a Karaoke SP 15 for providing a Karaoke service. [0026]In operation, the master mobile terminal 21 is connected to the slave mobile terminals 22, forming a service group. The user of the master mobile terminal 21 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 authenticates the user through the HLR 12 and the AC 13 and transmits the audio data to the master mobile terminal 21 and the slave mobile terminals 22. When the master mobile terminal 21 transmits a play command to the slave mobile terminals 22, the master and slave mobile terminals 21 and 22 start to simultaneously play the song, displaying its lyrics using the audio data, enabling users sing along. [0027]This method of providing the Karaoke service to mobile terminals by synchronizing them will be described below with reference to FIG. 3. [0028]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention. Referring to FIG. 3, the mobile terminals equipped with the functions of wireless Internet browsing, Karaoke music playing, and wireless connection are grouped in a service group in step 31. The wireless connections refer to connections between mobile terminals by Bluetooth, IRDA (Infrared Data Association), or wireless LAN (Local Area Network). The service group, corresponding to a working group in a PC (Personal Computer) network, is set by assigning the same wireless connection address to the mobile terminals. Thus, interference from other mobile terminals having a different wireless connection address is avoided. [0029]In step 32, one of the mobile terminals in the service group is designated as a mater mobile terminal with the other mobile terminals designated as slave terminals. The designation of master and slave MT's will be described in more detail hereinbelow with reference to FIG. 4. [0030]FIG. 4 illustrates examples of screen displays related to the Karaoke service in a mobile terminal according to the embodiment of the present invention. Referring to FIG. 4, a service group window 41 displays a wireless connection address assigned commonly to mobile terminals in the same service group, and a mobile terminal state window 42 displays the state of the mobile terminal, i.e., master or slave. [0031]To provide the Karaoke service in various modes, a slave grouping can be further divided into a slave channel 1, a slave channel 2, etc. If the Karaoke SP provides multichannel sound, that is, the audio is divided into discrete channels, center, left front, right front, left rear, and right rear, slave channel 1 outputs one of the channels such as the right channel for stereo sound or the left rear channel for digital surround sound 5.1, slave channel 2 outputs another channel, and the other channels output their respective channel sound. When sound from multiple sound sources is divided into 16- to 40-note polyphonic sounds, each channel may output its assigned sounds. [0032]The mobile terminal state is set to “master” only for a master mobile terminal. The master mobile terminal can remotely control the Internet and Karaoke functions of the slave mobile terminals through the wireless connections between them. [0033]Returning to FIG. 3, after the master mobile terminal 21 selects a song and requests the song from the Karaoke SP 15 through the mobile communication network 14, the master and slave mobile terminals 21 and 22 receive service contents related to the song from the Karaoke SP 15 in step 33. The contents reception is carried out in two ways, which will be described later with reference to FIGS. 5A and 5B. [0034]When the master mobile terminal 21 sends a play command to the slave mobile terminals 22 through wireless connection, for example, by Bluetooth, IRDA, or wireless LAN, all the mobile terminals 21 and 22 in the service group start to play the song simultaneously, synchronized according to a pilot channel clock signal in step 34. [0035]Upon request for a call setup for any mobile terminal in the service group during the music accompaniment playing, the mobile terminal is released from synchronization and connected to a call. The call setup request acts as an interrupt to the Karaoke service. [0036]FIGS. 5A and 5B illustrate embodiments of the contents reception in the Karaoke service using wireless connection between mobile terminals according to the present invention. Referring to FIG. 5A, a mobile terminal 51 is designated as a master and mobile terminals 52 are designated as slaves in a service group. After the service group is set in step 31 and the master and slave mobile terminals 51 and 52 are designated in step 32, the mobile terminals 51 and 52 receive service contents (i.e., Karaoke audio data) from the Karaoke SP 15 in step 33 in FIG. 4. [0037]Describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in the Karaoke SP 15 through the mobile communication network 14 in step 501 and transmits a contents receive command to the slave mobile terminals 52 in step 502. Since the master mobile terminal 51 can remotely control the wireless Internet function of the slave mobile terminals 52, the master mobile terminal 51 and the slave mobile terminals 52 under the control of the master mobile terminal 51 receive the same service contents in step 503. [0038]Referring to FIG. 5B, describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in step504 and receives receive service contents from the Karaoke SP 15 through the mobile communication network 14 in step 505. The master mobile terminal 51 then transmits the service contents to the slave mobile terminals by wireless connection in step 506. [0039]The contents receiving method illustrated in FIG. 5A enables each mobile terminal to receive a different channel or a different sound source since master and slave mobile terminals all access the Karaoke SP. If the SP prohibits content duplication and reproduction, retransmission of the service contents from the master mobile terminal to the slave mobile terminals is not permitted. In this sense, the method of FIG. 5A is useful. When accessing the SP, each slave mobile terminal transmits a packet indicating a slave channel to receive corresponding channel contents. [0040]Alternatively, rates for using service contents are saved and the same data can be broadcast to mobile terminals in the same service group in the content receiving method illustrated in FIG. 5B. [0041]As described above, the present invention offers the following benefits: (1) provision of Karaoke music with high volume, surround sound effects, and multiple sound sources improves the quality of the Karaoke service; (2) since a plurality of mobile terminals download the same audio data from an SP and users enjoy the Karaoke service through their mobile terminals together rather than alone, the number of service connections is increased and the novel service deployment attracts more customers from an SP's point of view; (3) the extension of the use of wireless data communication between mobile terminals enables mobile terminal manufacturers to create new customer demands; and (4) a program for carrying out the Karaoke service can be written on a computer-readable recording medium (e.g., CD ROM, RAM, floppy disk, hard disk, and optomagnetic disk). [0042]While the present invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. § 119 于 2003 年 2 月 13 日向韩国工业产权局提交的题为“使用移动终端之间的无线连接向移动终端提供卡拉 OK 服务的方法”的申请,编号为 2003-8989,其内容为 通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明总体上涉及一种通过移动终端提供服务的方法,具体地,涉及一种向移动终端提供卡拉OK服务的方法,以及提供一种计算机可读记录介质以在其上记录用于执行该服务的程序的计算机可读记录介质。 卡拉OK服务方法。 [0004] 2.相关技术的描述 [0005] 由于其便携性和便利性,移动终端已成为日常生活中的必需品。 通常,移动终端配备有电话簿、日程安排等多种功能。 因此,除了拨打电话之外,它们还充当个人信息管理器。 2.5 th 一代移动终端,基于IS(国际标准)-95C,和3 rd 一代移动终端,例如 IMT(国际移动通信)-2000 终端,为个人娱乐目的提供额外的多媒体服务。 [0006] 卡拉OK功能是一种个人娱乐服务,通过移动终端播放带有歌词和动画的各种类型的歌曲。 如图。 图1图示了用于提供传统卡拉OK服务的移动通信系统。 参考图。 如图1所示,卡拉OK服务是通过典型的移动通信网络提供的。 因此,卡拉OK服务是直接从移动通信网络上的服务提供商(SP)提供的,而不是来自移动通信网络本身的服务。 [0007] 移动通信系统由移动终端组成 11 为了通过移动通信网络接收卡拉 OK 服务,归属位置寄存器 (HLR) 12 和认证中心(AC) 13 用于提供移动终端的注册信息 11 , 移动通信网络 14 用于将 SP 连接到用户,以及卡拉 OK SP 15 提供卡拉OK服务。 [0008] 在操作中,移动终端的用户 11 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 然后通过 HLR 对用户进行身份验证 12 和交流 13 并将存储在其数据库中的音频数据提供给用户。 移动终端 11 使用接收到的音频数据播放带有歌词的歌曲,使用户能够跟着唱。 [0009] 一般而言,用户与他人而不是单独一起享受卡拉OK音乐。 单个移动终端播放的音乐音量取决于其扬声器,并且通常不足以让多个用户欣赏音乐。 另外,再好的音箱,单声源也无法为他们提供足够的音量。 [0010] 鉴于语音服务的多样化和格式的快速变化,卡拉 OK SP 15 试图通过新功能来吸引移动用户,例如伴奏包括立体声在内的多声道环绕声效果,或通过现有的仅限于 40 音符复音容量的移动终端伴奏更高音符的复音。 然而,在传统技术中,服务部署依赖于单个移动终端的性能,这些服务的好处往往难以捉摸。 发明内容 [0011] 因此,本发明的一个目的是提供一种卡拉OK服务方法,该方法使用配备有卡拉OK功能的移动终端之间的无线连接,通过移动终端同步来同时播放音乐伴奏,以及一种计算机可读记录。 用于在其上记录用于执行卡拉OK服务的程序的介质。 [0012]本发明的另一目的在于提供一种卡拉OK服务方法,用于播放具有高音量、环绕声效果和多种音源的音乐。 [0013] 通过提供一种通过无线连接向移动终端提供卡拉OK服务的方法,以及其上具有用于执行卡拉OK服务的程序的计算机可读记录介质来实现上述和其他目的。 [0014] 根据本发明的一个方面,在卡拉OK服务方法中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容。 主移动终端向从移动终端发送播放命令,所有移动终端根据服务内容开始播放卡拉OK音乐。 [0015] 根据本发明的另一方面,在卡拉OK服务方法中,将移动终端与移动终端分组在服务组中以接收卡拉OK服务,并指定为服务组中的主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 主移动终端收到播放指令后,根据服务内容开始播放卡拉OK音乐。 [0016] 根据本发明的另一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 在第一功能中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 在第一功能中被指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并在第二功能中控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容 . 主移动终端向从移动终端发送播放命令,然后所有移动终端根据第三功能中的服务内容开始播放卡拉OK音乐。 [0017] 根据本发明的又一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 该程序执行第一、第二和第三功能。 在第一个功能中,将移动终端与移动终端分组在一个服务组中以接收卡拉OK服务,并在服务组中将移动终端指定为主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在第二功能中在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 从移动终端接收到主移动终端的播放命令后,根据第三功能中的服务内容开始播放卡拉OK音乐。 附图的简要说明 [0018] 本发明的上述和其他目的、特征和优点将在以下结合附图的详细描述中变得更加明显,其中: [0019] 如图。 附图说明图1示出了向移动终端提供传统卡拉OK服务的移动通信系统; [0020]如图。 图2示出了根据本发明实施例的通过多个移动终端之间的无线连接向多个移动终端提供卡拉OK服务的移动通信系统的配置。 [0021] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 [0022] 如图。 图4示出了根据本发明实施例的通过与其他移动终端的无线连接来接收卡拉OK服务的移动终端中的屏幕显示示例。 和 [0023] 图 图5A和5B示出了根据本发明通过与其他移动终端的无线连接来接收卡拉OK服务的内容的实施例。 优选实施例的详细说明 [0024] 下面结合附图对本发明的优选实施例进行详细说明。 在以下描述中,没有详细描述众所周知的功能和结构,因为它们会以不必要的细节模糊本发明。 [0025] 如图。 图2图示了根据本发明实施例的用于通过移动终端之间的无线连接向移动终端提供卡拉OK服务的移动通信系统。 参考图。 2、移动通信系统由主移动终端组成 21 通过移动通信网络接收卡拉 OK 服务的 14 , 从移动终端 22 连接到主移动终端 21 ,为了接收相同的卡拉 OK 服务,HLR 12 和 SC 13 为移动终端提供注册信息 21 和 22 , 移动通信网络 14 用于将 SP 连接到移动用户,以及卡拉 OK SP 15 提供卡拉 OK 服务。 [0026] 在操作中,主移动终端 21 连接到从移动终端 22 ,形成服务群。 主移动终端用户 21 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 通过 HLR 对用户进行身份验证 12 和交流 13 并将音频数据传输到主移动终端 21 和从移动终端 22 . 当主控移动终端 21 向从移动终端发送播放命令 22 ,主从移动终端 21 和 22 开始同时播放歌曲,使用音频数据显示歌词,让用户跟着唱。 [0027] 下面将参照图3描述通过同步移动终端向移动终端提供卡拉OK服务的这种方法。 3. [0028] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 参考图。 3、将具备无线上网浏览、卡拉OK音乐播放、无线连接功能的移动终端分步归入一个服务组 31 . 无线连接是指移动终端之间通过蓝牙、IRDA(红外数据协会)或无线LAN(局域网)的连接。 通过为移动终端分配相同的无线连接地址来设置服务组,对应于PC(个人计算机)网络中的工作组。 因此,避免了来自具有不同无线连接地址的其他移动终端的干扰。 [0029] 在步骤 32 ,服务组中的一个移动终端被指定为主移动终端,其他移动终端被指定为从终端。 下文将参考图1更详细地描述主MT和从MT的指定。 4. [0030]如图。 图4图示了根据本发明实施例的移动终端中与卡拉OK服务相关的屏幕显示的示例。 参考图。 4、一个服务组窗口 41 显示同一服务组内移动终端通用分配的无线连接地址,移动终端状态窗口 42 显示移动终端的状态,即主或从。 [0031] 为了提供各种模式的卡拉OK服务,一个从属分组可以进一步划分为一个从属频道 1 , 从属通道 2 等。如果Karaoke SP提供多声道声音,即音频分为离散声道,中、左前、右前、左后、右后,从声道 1 输出其中一个声道,例如用于立体声的右声道或用于数字环绕声的左后声道 5 . 1 , 从通道 2 输出另一个通道,其他通道输出各自通道的声音。 当来自多个声源的声音被分成 16 到 40 音符的复音时,每个通道都可以输出其分配的声音。 [0032] 移动终端状态仅针对主移动终端设置为“主”。 主移动终端可以通过它们之间的无线连接远程控制从移动终端的上网和卡拉OK功能。 [0033] 返回图。 3、掌握移动端后 21 选择一首歌曲并向卡拉 OK SP 请求歌曲 15 通过移动通信网络 14 ,主从移动终端 21 和 22 从卡拉 OK SP 接收与歌曲相关的服务内容 15 在一步 33 . 内容接收以两种方式进行,这将在后面参考图3和图4进行描述。 参见图 5A 和 5B。 [0034] 当主控移动终端 21 向从移动终端发送播放命令 22 通过无线连接,例如通过蓝牙、IRDA或无线局域网,所有移动终端 21 和 22 在服务组中同时开始播放歌曲,根据一个导频通道时钟信号同步 34 . [0035] 在音乐伴奏播放期间,在服务组中的任何移动终端请求建立呼叫时,移动终端从同步中释放并连接到呼叫。 呼叫建立请求充当卡拉 OK 服务的中断。 [0036] 图 图5A和5B示出了根据本发明的使用移动终端之间的无线连接的卡拉OK服务中的内容接收的实施例。 参考图。 5A、移动终端 51 被指定为主机和移动终端 52 被指定为服务组中的从属设备。 步骤中设置服务组后 31 以及主从移动终端 51 和 52 在步骤中指定 32 , 移动终端 51 和 52 从卡拉 OK SP 接收服务内容(即卡拉 OK 音频数据) 15 在一步 33 在图 4. [0037] 描述步骤 33 更详细地说,主移动终端 51 从卡拉 OK SP 中的音乐数据库中选择一首歌曲 15 通过移动通信网络 14 在一步 501 向从移动终端发送内容接收命令 52 在一步 502 . 自主移动端 51 可远程控制从属移动终端的无线上网功能 52 ,主移动终端 51 和从移动终端 52 在主移动终端的控制下 51 在步骤中接收相同的服务内容 503 . [0038] 参考图。 5B,描述步骤 33 更详细地说,主移动终端 51 在步骤中从音乐数据库中选择一首歌曲 504 并从卡拉 OK SP 接收接收服务内容 15 通过移动通信网络 14 在一步 505 . 主控移动终端 51然后在步骤中通过无线连接将服务内容传输到从移动终端 506 . [0039] 图1所示的内容接收方法。 由于主移动终端和从移动终端都访问卡拉OK SP,因此图5A使每个移动终端能够接收不同的频道或不同的声源。 如果SP禁止内容复制和再现,则不允许将服务内容从主移动终端重传到从移动终端。 在这个意义上,图1的方法。 5A很有用。 在接入SP时,每个从移动终端发送一个指示从信道的分组以接收相应的信道内容。 [0040] 或者,在图1所示的内容接收方法中,可以保存使用服务内容的费率并将相同的数据广播到相同服务组中的移动终端。 5B。 [0041] 如上所述,本发明提供以下益处: (1)提供具有高音量、环绕声效果和多声源的卡拉OK音乐,提高了卡拉OK服务的质量。 (2)由于多个移动终端从一个SP下载相同的音频数据,用户通过他们的移动终端一起而不是单独享受卡拉OK服务,增加了服务连接的数量,新颖的业务部署吸引了更多来自SP的客户 观点看法; (3)移动终端之间无线数据通信使用的延伸,使移动终端制造商能够创造新的客户需求; (4)可以将用于进行卡拉OK服务的程序写入计算机可读取的记录介质(例如CD ROM、RAM、软盘、硬盘、光磁盘)上。 [0042] 尽管本发明已经参照其某些优选实施例进行了展示和描述,但本领域技术人员将理解,在不背离所定义的本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变 根据所附权利要求。(String), 111526(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.198 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.199 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.200 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.201 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.201 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.202 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.203 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.203 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.203 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.205 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), CN1295910C(String), 1046990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.206 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.206 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.207 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), CN1522010A(String), 1046991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.208 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.208 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.208 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), KR100532288B1(String), 1046992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.209 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.209 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.209 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), KR1020040073057A(String), 1046993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.210 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.210 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.211 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), US20040162062A1(String), 1046994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.211 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.212 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.212 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), US7142807B2(String), 1046995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.213 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.213 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.214 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7142807B2(String), US7142807B2(String), 1164643200(Integer), 270638(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.215 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.215 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.215 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.217 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.217 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.217 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.218 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.219 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.219 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.226 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.227 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.227 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.236 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.236 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.236 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.238 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.238 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.238 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184955(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.248 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.248 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.248 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.256 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.257 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.257 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.258 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.258 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.258 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.259 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.260 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.261 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.262 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.263 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.263 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.264 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.264 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.264 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.266 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.266 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.266 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.274 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.275 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.275 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.286 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.288 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.289 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.291 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.292 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.292 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.301 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.301 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.303 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\52d3446d3b614497a680822a60296e97.png(String), 184956(Integer), 52d3446d3b614497a680822a60296e97.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.311 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.312 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.312 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.313 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.314 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.314 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of changing standby order of waiting mobile terminals in mobile terminal(String), 移动终端中更改等待移动终端待机顺序的方法(String), US7801528B2(String), A method for changing a standby order of waiting mobile terminals includes displaying a standby order of a plurality of mobile terminals according to an audiovisual communication request order when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal, sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a standby order change request, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message, and displaying the changed standby order.(String), 一种用于改变等待移动终端的待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求,而第一移动终端时,根据视听通信请求顺序显示多个移动终端的待机顺序。 与第二移动终端进行视听通信,当第一移动终端接收到待机指令变更请求时,从第一移动终端向移动通信网络发送待机指令变更请求消息,当第一移动终端接收到待机指令变更请求时,变更第一移动终端的待机指令。 移动终端从移动通信网络接收对应于待机命令更改请求消息的待机命令更改完成消息,并显示更改后的待机命令。(String), US11/769201(String), 1182873600(Integer), US7801528B2(String), 1284998400(Integer), 1284998400(Integer), 美国(String), 2(Integer), 4(Integer), KR(String), 2(Integer), 12(Integer), KR1020000042764A | KR1020050017736A | KR1020050053912A | KR1020070012088A | US20020009987A1 | US20030104830A1 | US20060223593A1 | US20080132254A1(String), \20230420\52d3446d3b614497a680822a60296e97.png(String), 17(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.322 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.323 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.323 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.333 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.334 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.334 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 1. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals, according to the order in which the audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a request to change the standby order;changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message; anddisplaying the changed standby order.(String), 1.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序,而第一移动终端终端与第二移动终端进行视听通信;当第一移动终端接收到待机顺序变更请求时,第一移动终端向移动通信网络发送待机顺序变更请求消息;当第一移动终端从移动通信网络接收到与待机顺序变更请求消息对应的待机顺序变更完成消息时,变更第一移动终端的待机顺序;和显示更改后的待机顺序。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.334 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 2. The method of claim 1, further comprising:changing the standby order at the mobile communication network in response to the standby order change request message sent by the first mobile terminal.(String), 2.如权利要求1所述的方法,还包括:响应于第一移动终端发送的待机顺序改变请求消息,改变移动通信网络处的待机顺序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.334 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 3. The method of claim 2, further comprising sending the changed standby order to the first mobile terminal through the mobile communication network.(String), 3.如权利要求2所述的方法,还包括通过移动通信网络向第一移动终端发送变更后的待机指令。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.335 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 4. The method of claim 1, further comprising performing audiovisual communication with another mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 4.如权利要求1所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与另一移动终端进行视听通信。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.335 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 5. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals according to the order in which audiovisual communication request orders of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals;changing the standby order if the first mobile terminal approves the requested change of the standby order; anddisplaying the changed standby order.(String), 5.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求命令的顺序显示多个移动终端的待机顺序,而第一移动终端与第二移动终端进行视听通信;当第一移动终端接收到多个移动终端中的第三移动终端的待机顺序变更请求消息时,判断第一移动终端是否同意请求的待机顺序变更;如果第一移动终端同意请求更改备用订单,则更改备用订单;和显示更改后的待机顺序。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.335 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 6. The method of claim 5, wherein determining whether the first mobile terminal approves the requested change of the standby order comprises:receiving the standby order change request message of the third mobile terminal from a mobile communication network; andsending a standby order change approval message to the mobile communication network when the standby order change request is approved in response to the received standby order change request message.(String), 6.如权利要求5所述的方法,其中判断第一移动终端是否同意请求的待机顺序变更包括:从移动通信网络接收第三移动终端的待机顺序变更请求消息;和当响应于接收到的备用订单变更请求消息批准备用订单变更请求时,向移动通信网络发送备用订单变更批准消息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.335 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 7. The method of claim 6, wherein changing the standby order comprises:receiving a standby order change completion message from the mobile communication network; andchanging the standby order according to the standby order change completion message.(String), 7.如权利要求6所述的方法,其中更改备用订单包括:接收来自移动通信网络的备用订单变更完成消息;和根据备用订单变更完成消息变更备用订单。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.335 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 8. The method of claim 6, wherein receiving the standby order change request message of the third mobile terminal comprises:sending a standby order change request message from the third mobile terminal to the mobile communication network; andreceiving the standby order change request message of the third mobile terminal from the mobile communication network in the first mobile terminal.(String), 8.如权利要求6所述的方法,其中接收第三移动终端的待机顺序变更请求消息包括:第三移动终端向移动通信网络发送待机顺序变更请求消息;和第一移动终端中从移动通信网络接收第三移动终端的待机顺序变更请求消息。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.335 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 9. The method of claim 8, wherein changing the standby order comprises:receiving the standby order change approval message sent from the first mobile terminal in the mobile communication network; andchanging the standby order.(String), 9.如权利要求8所述的方法,其中更改备用订单包括:接收移动通信网络中的第一移动终端发送的备用订单变更批准消息;和更改待机顺序。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.336 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 10. The method of claim 9, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal.(String), 10.如权利要求9所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端发送待机顺序改变完成消息。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.336 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 11. The method of claim 8, wherein the standby order change request message sent from the third mobile terminal is sent by the mobile communication network to the first mobile terminal and to a fourth mobile terminal of the plurality of mobile terminals.(String), 11.如权利要求8所述的方法,其中第三移动终端发送的待机顺序变更请求消息由移动通信网络发送给第一移动终端和多个移动终端中的第四移动终端。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.336 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 12. The method of claim 11, wherein changing the standby order comprises:receiving response messages to the standby order change request message from the first mobile terminal and from the fourth mobile terminal in the communication network; andchanging the standby order.(String), 12.如权利要求11所述的方法,其中更改备用订单包括:从通信网络中的第一移动终端和第四移动终端接收对待机顺序改变请求消息的响应消息;和更改待机顺序。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.336 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 13. The method of claim 12, wherein the mobile communication network changes the standby order according to the response messages if the response messages received from the first mobile terminal and from the fourth mobile terminal are identical.(String), 13.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息相同,则移动通信网络根据响应消息改变待机顺序。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.336 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 14. The method of claim 12, wherein the mobile communication network changes the standby order according to the response message of the first mobile terminal if the response messages received from the first mobile terminal and from the fourth mobile terminal are not identical.(String), 14.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息不相同,则移动通信网络根据第一移动终端的响应消息改变待机顺序。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.337 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 15. The method of claim 14, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal, the third mobile terminal, and the fourth mobile terminal.(String), 15.如权利要求14所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端、第三移动终端和第四移动终端发送待机顺序改变完成消息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.337 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 16. The method of claim 12, wherein the response message to the standby order change request message is one of a standby order change approval message and a standby order change non-approval message.(String), 16.如权利要求12所述的方法,其中备用订单变更请求消息的响应消息为备用订单变更批准消息和备用订单变更不批准消息之一。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.337 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 17. The method of claim 5, further comprising performing audiovisual communication with a mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 17.如权利要求5所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与移动终端进行视听通信。(String), 1(Integer), 16(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.462 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.462 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.469 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.469 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.470 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111527(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.476 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.476 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.477 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184956(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority from and the benefit of Korean Patent Application No. 10-2007-0004601, filed on Jan. 16, 2007, which is hereby incorporated by reference for all purposes as if fully set forth herein. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method of providing an audiovisual communication service in a mobile terminal, and more particularly, to a method of changing a standby order of waiting mobile terminals in a mobile terminal. [0004]2. Discussion of the Background [0005]As technology of mobile terminals has developed, an improved mobile terminal having a camera unit using an H.324M protocol including an H.245 protocol that allows for audiovisual communication has been provided. [0006]In conventional audiovisual communication technology, when a first mobile terminal receives a request for audiovisual communication from a third mobile terminal while the first mobile terminal is performing audiovisual communication with a second mobile terminal, the first mobile terminal stores information about the third mobile terminal. Thereafter, when the first mobile terminal ends audiovisual communication with the second mobile terminal, the first mobile terminal displays information about the third mobile terminal and performs audiovisual communication with the third mobile terminal. [0007]However, in the conventional audiovisual communication technology, even when the third mobile terminal urgently requests audiovisual communication with the first mobile terminal, the third mobile terminal may have to wait until the first mobile terminal ends audiovisual communication with the second mobile terminal. SUMMARY OF THE INVENTION [0008]The present invention provides a method of changing a standby order of at least two mobile terminals requesting audiovisual communication while a first mobile terminal is performing audiovisual communication. [0009]The present invention further provides a method of changing a standby order of mobile terminals in a standby state according to a standby order change request received from one of at least two mobile terminals waiting for audiovisual communication with the first mobile terminal while the first mobile terminal is performing audiovisual communication. [0010]The present invention further provides a method of displaying information about a mobile terminal requesting audiovisual communication while a first mobile terminal is performing audiovisual communication with a second mobile terminal. [0011]Additional features of the invention will be set forth in the description which follow, and in part will be apparent from the description, or may be learned by practice of the invention. [0012]The present invention discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, sending a standby order change request message to a mobile communication network from the first mobile terminal when the first mobile terminal receives a request to change the standby order, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message corresponding to the standby order change request message, and displaying the changed standby order. [0013]The present invention also discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals, changing the standby order if the first mobile terminal approves the requested change of the standby order, and displaying the changed standby order. [0014]It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. [0016]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0017]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0018]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0019]FIG. 4 is a flowchart showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0020]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0021]FIG. 6 is a flowchart showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0022]FIG. 7 is a message flow diagram showing another method of performing audiovisual communication with waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS [0023]The invention is described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements. [0024]It will be understood that when an element or layer is referred to as being “on” or “connected to” another element or layer, it can be directly on or directly connected to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on” or “directly connected to” another element or layer, there are no intervening elements or layers present. [0025]Exemplary embodiments according to the present invention exemplify a mobile terminal that includes a camera unit and is capable of performing audiovisual communication. That is, a mobile terminal according to exemplary embodiments of the present invention may include an information communication device or multimedia device, such as a mobile communication terminal, a mobile phone, a Personal Digital Assistant (PDA), a smart phone, or a notebook computer, that includes a camera unit and is capable of performing audiovisual communication, and applications thereof. [0026]Exemplary embodiments according to the present invention exemplify audiovisual communication. However, the present exemplary embodiments are not limited to audiovisual communication and may be applied to voice communication. [0027]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0028]Referring to FIG. 1, the system includes a first mobile terminal 100, a second mobile terminal 200, a third mobile terminal 300, a fourth mobile terminal 400, and a mobile communication network 500. [0029]The first mobile terminal may perform audiovisual communication with the second mobile terminal 200 and may receive a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400 while performing audiovisual communication with the second mobile terminal 200. A configuration of the first mobile terminal 100 is described with reference to FIG. 2, and the same configuration may also be applied to the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 and thus, individual descriptions thereof are omitted. [0030]The mobile communication network 500 includes a node to perform the function of a base station, a radio access network (RAN), which is a sub system of the node, a mobile switching center (MSC)/visitor location register (VLR) corresponding to a core network of a circuit switched domain, a home location register (HLR), and a gateway MSC. [0031]The MSC manages call control and mobility of the first mobile terminal 100, and the VLR and the HLR make up a matching device of subscriber information and register and manage information about mobile terminals belonging to the mobile communication network 500 including the first mobile terminal 100. [0032]In the following description, the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 belong to the same mobile communication network 500. However the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 may belong to different mobile communication networks and may be connected through different gateway MSCs. However, it is assumed that a series of processes performed in the RAN, MSC/VLR, HLR, and gateway MSC are performed in the mobile communication network 500. [0033]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0034]Referring to FIG. 2, the mobile terminal 100 includes a radio frequency (RF) unit 101, an input unit 103, a controller 105, a camera unit 107, an image processor 109, a display unit 111, a memory unit 113, and an audio unit 115. [0035]The RF unit 101 performs general wireless communication with the second mobile terminal 200, the third mobile terminal 300, the fourth mobile terminal 400, and the mobile communication network 500. For example, the RF unit 101 transmits and receives voice data, character messages, and multimedia messages using the mobile communication network 500. The RF unit 101 sends image data acquired from the camera unit 107 of the first mobile terminal 100 to the second mobile terminal 200 when the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 200. The RF unit 101 further receives image data acquired by the camera unit of the second mobile terminal 200 and image data acquired by the camera units of the third mobile terminal 300 and the fourth mobile terminal 400 requesting audiovisual communication. The image data of the second mobile terminal 200 may be still and/or moving picture data, and the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be still and/or moving image data. Further, when the third mobile terminal 300 and the fourth mobile terminal 400 perform audiovisual communication with the first mobile terminal 100, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may change to moving picture data. [0036]The input unit 103 may include a general keypad. The input unit 103 may include a touch screen, a touch pad, and a scroll wheel. The input unit 103 receives a user manipulation signal to control operation of the first mobile terminal 100 and provides the manipulation signal to the controller 105. [0037]The controller 105 controls the general operation of the first mobile terminal 100. Particularly, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200, receives a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400, and sets a standby order of audiovisual communication requests. The controller 105 displays image data (namely, image data of a user of the second mobile terminal 200) of the second mobile terminal 200 performing audiovisual communication in the display unit 111. The controller 105 displays image data from each mobile terminal requesting audiovisual communication, in the order in which the audiovisual communication requests were received, on the display unit 111 of the first terminal 100. [0038]In more detail, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be image data mapped to the corresponding mobile terminal and stored in a phone book (not shown) of the first mobile terminal 100. The image data may also be image data acquired by camera units of the third mobile terminal 300 and the fourth mobile terminal 400 when requesting audiovisual communication and may be sent with the request for audiovisual communication. The controller 105 may display the image data of the third mobile terminal 300 and the fourth mobile terminal 400 with thumb-nail type still image data. The controller 105 may also display image data of the second mobile terminal 200, with which the first mobile terminal 100 is performing audiovisual communication, including moving picture data. [0039]The controller 105 sends a standby order change request message REQ_MSG from the first mobile terminal 100 to the mobile communication network 500 through the RF unit 101, receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the changed standby order in the display unit 111. [0040]The controller 105 further receives a standby order change request message REQ_MSG from the mobile terminal having the highest standby position through the mobile communication network 500 and sends a standby order change approval message ACC_MSG to the mobile communication network 500 through the RF unit 101. Thereafter, the controller 105 receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the standby order in the display unit 111. [0041]When the controller 105 determines that the first mobile terminal 100 has ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 controls the RF unit 101 to perform audiovisual communication with the mobile terminal having the highest standby position. In the exemplary embodiments, to “end” the audiovisual communication is to terminate a communication channel formed to perform audiovisual communication with the second mobile terminal 200, and to “convert” an audiovisual communication state to a standby state is to convert to a standby state in order to perform audiovisual communication with another mobile terminal while maintaining the communication channel formed to perform audiovisual communication with the second mobile terminal 200. [0042]The camera unit 107 generates a user's image data to send through the RF unit 101. The camera unit 107 includes an image sensor to convert a photo signal of a subject to an analog signal and a signal processor to convert the analog signal to a digital signal. That is, the camera unit 107 converts a photo signal collected through a lens to a digital signal and generates image data with the converted digital signal. [0043]The image processor 109 processes image data generated in the camera unit 107 and image data received through the RF unit 101 into a format corresponding to the display unit 111. [0044]The controller 105 controls the display unit 111 to display various operation states, operation results, and other information from the units of the first mobile terminal 100. The display unit 111 may include a display device such as a liquid crystal display (LCD), organic light emitting diodes (OLED), or a plasma display panel (PDP). [0045]The display unit 111 displays image data input through the RF unit 101 and the camera unit 107 and processed in the image processor 109 in real time, thereby performing audiovisual communication or displaying a photographed image. [0046]The memory unit 113 stores information (for example, information about a setting state and a menu) related to operation of a program allowing the controller 105 to control the first mobile terminal 100. The memory unit 113 stores the standby order of the third mobile terminal 300 and the fourth mobile terminal 400. The memory unit 113 stores image data received from the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400, and may also store image data mapped to a corresponding terminal in a phone book (not shown) of the first mobile terminal 100. [0047]The audio unit 115 converts an analog audio signal that is input through a microphone MIC to a digital signal, provides the digital signal to the controller 105, converts a digital audio signal that is output from the controller 105 into an analog audio signal, and reproduces the analog audio signal through a speaker SPK. [0048]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0049]Referring to FIGS. 3A and 3B, while the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 100 (S301), the mobile communication network 500 receives a request for audiovisual communication from the third mobile terminal 300 (S303). At step S301, the first mobile terminal 100 is in an audiovisual communication state, the camera unit 107 of the first mobile terminal 100 acquires an image of a user of the first mobile terminal 100, the image processor 109 processes the user image, the display unit 111 displays the user image, and the microphone MIC and the speaker SPK are converted to an operation state. [0050]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S305). [0051]The third mobile terminal 300 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S307). If the third mobile terminal 300 sustains an audiovisual communication standby state, the third mobile terminal 300 sends a standby state sustenance message to the mobile communication network 500 (S309). [0052]Thereafter, the mobile communication network 500 sends information about the third mobile terminal 300 to the first mobile terminal 100 (S311) and forms a communication channel between the first mobile terminal 100 and the third mobile terminal 300. The information about the third mobile terminal 300 may include contact information and image data of the third mobile terminal 300. [0053]The mobile communication network 500 receives a request for audiovisual communication from the fourth mobile terminal 400 (S313), and sends a message regarding the state of the first mobile terminal 100 to the fourth mobile terminal 400 to notify the fourth mobile terminal 400 that the first mobile terminal 100 is performing audiovisual communication (S315). [0054]The fourth mobile terminal 400 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S317). If the fourth mobile terminal 400 sustains an audiovisual communication standby state, the fourth mobile terminal 400 sends a standby state sustenance message to the mobile communication network 500 (S319). [0055]Thereafter, the mobile communication network 500 sends information about the fourth mobile terminal 400 to the first mobile terminal 100 (S321) and forms a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400. The information about the fourth mobile terminal 400 may include contact information and image data of the fourth mobile terminal 400. [0056]The first mobile terminal 100 determines that a communication channel between the first mobile terminal 100 and the third mobile terminal 300 was formed at step S311, and that a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400 is formed at step S321. [0057]Thereafter, the first mobile terminal 100 sets and displays a standby order of the mobile terminals that have requested audiovisual communication by listing the mobile terminals in the order in which their requests were received (S323). In the present exemplary embodiment, because the third mobile terminal 300 requested audiovisual communication earlier than the fourth mobile terminal 400, the third mobile terminal 300 has the highest standby position. [0058]When the first mobile terminal 100 wants to change the displayed standby order (S325), the first mobile terminal 100 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S327). The request to change the standby order is input by selecting image data of the third mobile terminal 300 and the fourth mobile terminal 400 displayed in a change mode or a standby order. [0059]The mobile communication network 500 receives the standby order change request message REQ_MSG and changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 (S329). [0060]The mobile communication network 500 temporarily stores the changed standby order (S331) and sends a standby order change completion message RES_MSG informing the first mobile terminal 100 of the standby order change of the third mobile terminal 300 and the fourth mobile terminal 400 (S333). [0061]The first mobile terminal 100 changes and displays the standby order according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S335). [0062]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S337), the mobile communication network 500 refers to the changed standby order that was temporarily stored at step 331 (S339) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S341). [0063]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S343). [0064]FIG. 4 is a flowchart showing a method of changing the standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0065]Referring to FIG. 4, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200 (S401). The controller 105 displays moving picture data received in real time from the second mobile terminal 200 in the display unit 111. When the mobile terminal 100 receives a request for audiovisual communication from at least one mobile terminal while performing audiovisual communication (S403), the controller 105 determines whether the number of the mobile terminals requesting audiovisual communication is at least two (S405). [0066]If there are at least two mobile terminals requesting audiovisual communication, the controller 105 sets a standby order according to the order in which the requests for audiovisual communication were received and displays the set standby order on the display unit 111 (S407). The controller 105 displays image data received from the mobile terminals requesting audiovisual communication or image data mapped to a phone number of the mobile terminals and stored in a phone book (not shown) on the display unit 111 in the order in which their audiovisual communication requests were received. [0067]The controller 105 determines whether the set standby order has changed (S409). If the set standby order has not change, the process continues at step S419. [0068]If the set standby order has changed, the controller 105 controls the RF unit 101 to send a message REQ_MSG requesting that the standby order of the mobile terminals (here, the third mobile terminal 300 and the fourth mobile terminal 400) be changed through the mobile communication network 500 (S411). [0069]Thereafter, the controller 105 receives a standby order change completion message RES_MSG sent from the mobile communication network 500 through the RF unit 101 (S415). The controller 105 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the received standby order change completion message RES_MSG and displays the changed standby order on the display unit 111 (S417). [0070]The controller 105 determines whether the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S419). If the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 determines whether mobile terminals waiting for audiovisual communication exist, and if mobile terminals waiting for audiovisual communication exist, the first mobile terminal 100 performs audiovisual communication with the mobile terminal having the highest standby position (S421). The first mobile terminal 100 may perform audiovisual communication with the fourth mobile terminal 400, whose standby order position is changed to the highest position at step S417, or with the third mobile terminal 300, which has the highest position in the standby order set at step S407. [0071]If the number of the mobile terminals requesting audiovisual communication is not at least two at step 405, the controller 105 determines whether the first mobile terminal 100 has either ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state (S423). When the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the first mobile terminal 100 performs audiovisual communication with the mobile terminal requesting audiovisual communication (S425). [0072]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0073]Referring to FIGS. 5A and 5B, steps S501 to S523 of FIG. 5A are substantially the same as steps S301 to S323 of FIG. 3A and thus description thereof is omitted. [0074]If the fourth mobile terminal 400 having a standby order position that is lower than that of the third mobile terminal 300 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S525), the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100 (S527), and the mobile communication network 500 sends the standby order change request message REQ_MSG to the third mobile terminal 300 (S529). The standby order change request message REQ_MSG may be sent by the fourth mobile terminal 400 at the same time the fourth mobile terminal 400 sends an audiovisual communication request message to the mobile communication network 500 at step S513. [0075]The first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG (S531), and the third mobile terminal 300 approves the change of the standby order in response to the standby order change request message REQ_MSG (S533). [0076]The first mobile terminal 100 then sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S535), and the third mobile terminal 300 sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S537). [0077]The mobile communication network 500 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change approval message ACC_MSG received from the first mobile terminal 100 at step S535 and from the third mobile terminal 300 at step S537 (S539). [0078]The mobile communication network 500 temporarily stores a changed standby order (S541) and sends a standby order change completion message RES_MSG to the first mobile terminal 100(S543), the third mobile terminal 300 (S545), and the fourth mobile terminal 400(S547). [0079]The first mobile terminal 100 changes and displays the standby order set at the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S549). [0080]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S551), the mobile communication network 500 refers to the changed standby order temporarily stored at step S541 (S553) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S555). [0081]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S557). [0082]Another method of changing a standby order of waiting mobile terminals according to another exemplary embodiment of the present invention (not shown in the Figures) is described as follows. [0083]When the mobile communication network 500 receives a standby order change request message REQ_MSG from the fourth mobile terminal 400, the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100. [0084]Thereafter, if the first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG, the first mobile terminal 100 sends a standby order change approval message ACC_MSG confirming the approval to the mobile communication network 500. When th(String), 相关申请的交叉引用 [0001] 本申请要求于 2007 年 1 月 16 日提交的韩国专利申请号 10-2007-0004601 的优先权和权益,其在此通过引用并入所有目的,就好像在此完全阐述一样。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种在移动终端中提供视听通信服务的方法,更具体地,涉及一种在移动终端中改变等待移动终端的待机顺序的方法。 [0004] 2. 背景讨论 [0005] 随着移动终端技术的发展,已经提供了一种改进的移动终端,其具有使用H.324M协议的相机单元,该H.324M协议包括允许视听通信的H.245协议。 [0006] 在传统的视听通信技术中,当第一移动终端在与第二移动终端进行视听通信时,当第一移动终端接收到来自第三移动终端的视听通信请求时,第一移动终端存储关于第三移动终端的信息。 之后,当第一移动终端结束与第二移动终端的视听通信时,第一移动终端显示第三移动终端的信息,并与第三移动终端进行视听通信。 [0007] 然而,在现有的视听通信技术中,即使第三移动终端紧急请求与第一移动终端进行视听通信,第三移动终端也可能不得不等待,直到第一移动终端结束与第二移动终端的视听通信。 发明内容 [0008] 本发明提供了一种在第一移动终端正在执行视听通信时改变请求视听通信的至少两个移动终端的待机顺序的方法。 [0009] 本发明还提供了一种根据从等待与第一移动终端进行视听通信的至少两个移动终端之一接收到的待机顺序改变请求来改变处于待机状态的移动终端的待机顺序的方法,同时第一移动终端是 进行视听交流。 [0010] 本发明还提供了一种在第一移动终端正在与第二移动终端进行视听通信时显示关于请求视听通信的移动终端的信息的方法。 [0011] 本发明的附加特征将在随后的描述中阐述,并且部分地从描述中变得显而易见,或者可以通过本发明的实践来了解。 [0012] 本发明公开了一种用于在移动通信系统中改变待机顺序的方法,包括当第一移动终端时,根据接收到多个移动终端的视听通信请求的顺序,显示多个移动终端的待机顺序。 当第一移动终端正在与第二移动终端进行视听通信时,终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到来自第一移动终端的待机命令更改请求消息到移动通信网络时 请求更改待机命令,当第一移动终端接收到与待机命令更改请求消息对应的待机命令更改完成消息时,在第一移动终端更改待机命令,并显示更改后的待机命令。 [0013]本发明还公开了一种在移动通信系统中改变待机顺序的方法,包括根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序。 当第一移动终端与第二移动终端进行视听通信时,移动终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到待机时,确定第一移动终端是否批准请求的待机顺序变更 所述多个移动终端中的第三移动终端的订单更改请求消息,如果第一移动终端批准请求的待机订单更改,则更改待机订单,并显示更改后的待机订单。 [0014] 应当理解,前面的一般描述和下面的详细描述都是示例性和解释性的,并且旨在提供对所要求保护的本发明的进一步解释。 附图的简要说明 [0015] 附图被包括以提供对本发明的进一步理解并且被并入并构成本说明书的一部分,它们说明了本发明的实施例,并且与描述一起用于解释本发明的原理。 [0016] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0017] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0018] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0019] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0020] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0021] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0022] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 图示实施例的详细说明 [0023] 下文参照附图更全面地描述本发明,其中示出了本发明的实施例。 然而,本发明可以以许多不同的形式来体现,并且不应被解释为限于这里阐述的实施例。 相反,提供这些实施例是为了使本公开是彻底的,并且将向本领域技术人员充分传达本发明的范围。 在附图中,为了清楚起见,可能夸大了层和区域的尺寸和相对尺寸。 图中相同的附图标记表示相同的元件。 [0024] 应当理解,当一个元件或层被称为“在”另一个元件或层上或“连接到”另一个元件或层时,它可以直接在另一个元件或层上或直接连接到另一个元件或层,或者中间的元件或层可以是 当下。 相反,当一个元素被称为“直接在”或“直接连接到”另一个元素或层时,不存在中间的元素或层。 [0025]根据本发明的示例性实施例举例说明了包括照相机单元并且能够执行视听通信的移动终端。 也就是说,根据本发明示例性实施例的移动终端可以包括信息通信设备或多媒体设备,例如移动通信终端、移动电话、个人数字助理(PDA)、智能电话或笔记本电脑 包括照相机单元并能够进行视听通信的计算机及其应用。 [0026] 根据本发明的示例性实施例举例说明了视听通信。 然而,本示例性实施例不限于视听通信并且可以应用于语音通信。 [0027] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0028] 参考图。 1、系统包括第一移动终端 100 ,第二个移动终端 200 ,第三个移动终端 300 ,第四个移动终端 400 , 和一个移动通信网络 500 . [0029] 第一移动终端可以与第二移动终端进行视听通信 200 并且可以接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 在与第二移动终端进行视听通信的同时 200 . 第一移动终端的配置 100 参照图1描述。 如图2所示,同样的配置也可以应用于第二移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 因此,省略其个别描述。 [0030] 移动通信网络 500 包括执行基站功能的节点、作为节点的子系统的无线接入网络 (RAN)、对应于一个核心网络的移动交换中心 (MSC)/访问者位置寄存器 (VLR) 电路交换域、归属位置寄存器 (HLR) 和网关 MSC。 [0031] MSC管理第一移动终端的呼叫控制和移动性 100 ,VLR和HLR组成用户信息匹配装置,注册和管理属于移动通信网络的移动终端信息 500 包括第一移动终端 100 . [0032] 在下面的描述中,第一移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 属于同一个移动通信网络 500 . 然而第一款移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 可能属于不同的移动通信网络,可能通过不同的网关MSC连接。 然而,假设在移动通信网络中执行在RAN、MSC/VLR、HLR和网关MSC中执行的一系列处理 500 . [0033] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0034] 参考图。 2、移动端 100 包括一个射频 (RF) 单元 101 , 一个输入单元 103 , 一个控制器 105 , 一个相机单元 107 , 图像处理器 109 , 一个显示单元 111 , 一个记忆单元 113 , 和一个音频单元 115 . [0035] 射频单元 101 与第二移动终端进行一般无线通信 200 , 第三个移动终端 300 ,第四个移动终端 400 , 和移动通信网络 500 . 例如,射频单元 101 使用移动通信网络发送和接收语音数据、字符消息和多媒体消息 500 . 射频单元 101 发送从相机单元获取的图像数据 107第一个移动终端 100 到第二个移动终端 200 当第一个移动终端 100 与第二移动终端进行视听通信 200 . 射频单元 101 还接收第二移动终端的摄像单元获取的图像数据 200 第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 请求视听通信。 第二移动终端的图像数据 200 可以是静止和/或运动图像数据,第三移动终端的图像数据 300 和第四个移动终端 400 可以是静止和/或运动图像数据。 进一步地,当第三移动终端 300 和第四个移动终端 400 与第一移动终端进行视听通信 100 ,第三个移动终端的图像数据 300 和第四个移动终端 400 可能会更改为运动图像数据。 [0036] 输入单元 103 可能包括一个通用键盘。 输入单元 103 可以包括触摸屏、触摸板和滚轮。 输入单元 103 接收用户操作信号以控制第一移动终端的操作 100 并向控制器提供操纵信号 105 . [0037] 控制器 105 控制第一移动终端的一般操作 100 . 特别是控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 ,接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 ,并设置视听通信请求的待机顺序。 控制器 105 显示图像数据(即第二移动终端用户的图像数据) 200 )的第二个移动终端 200 在显示单元中进行视听通信 111 . 控制器 105 在显示单元上按照接收到视听通信请求的顺序显示来自请求视听通信的每个移动终端的图像数据 111 第一个终端的 100 . [0038] 更详细地说,第三移动终端的图像数据 300 和第四个移动终端 400 可以是映射到对应的移动终端并存储在第一移动终端的电话簿(未示出)中的图像数据 100 . 图像数据也可以是第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 当请求视听通信时,可能会与视听通信请求一起发送。 控制器 105 可以显示第三移动终端的图像数据 300 和第四个移动终端 400 缩略图类型的静止图像数据。 控制器 105 还可以显示第二移动终端的图像数据 200 ,其中第一款移动终端 100 正在执行视听通信,包括运动图像数据。 [0039] 控制器 105 从第一移动终端发送备用订单更改请求消息REQ_MSG 100 到移动通信网络 500 通过射频单元 101 ,接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面中显示更改后的待机顺序 111 . [0040] 控制器 105 进一步通过移动通信网络从具有最高待机位置的移动终端接收待机顺序更改请求消息REQ_MSG 500 向移动通信网络发送待命订单变更批准消息ACC_MSG 500 通过射频单元 101 . 此后,控制器 105 接收来自移动通信网络的备用订单更改完成消息RES_MSG 500通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面显示待机命令 111 . [0041] 当控制器 105 确定第一移动终端 100 已结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 控制射频单元 101 与待机位置最高的移动终端进行视听通信。 在示例性实施例中,“结束”视听通信是终止形成用于与第二移动终端进行视听通信的通信信道 200 ,并且将视听通信状态“转换”为待机状态是为了在保持与第二移动终端执行视听通信而形成的通信信道的同时,转换为待机状态以便与另一个移动终端执行视听通信。 200 . [0042] 相机单元 107 生成用户的图像数据以通过射频单元发送 101 . 相机单元 107 包括将对象的照片信号转换为模拟信号的图像传感器和将模拟信号转换为数字信号的信号处理器。 也就是相机单元 107 将通过镜头采集的照片信号转换为数字信号,并利用转换后的数字信号生成图像数据。 [0043] 图像处理器 109 处理相机单元中生成的图像数据 107 和通过射频单元接收的图像数据 101 转换成与显示单元对应的格式 111 . [0044] 控制器 105 控制显示单元 111 显示第一移动终端各单元的各种操作状态、操作结果等信息 100 . 显示单元 111 液晶显示器(LCD)、有机发光二极管(OLED)或等离子体显示面板(PDP)等显示装置可以包括显示装置。 [0045] 显示单元 111 显示通过射频单元输入的图像数据 101 和相机单元 107 并在图像处理器中处理 109 实时,从而进行视听通信或显示拍摄的图像。 [0046] 记忆单元 113 存储与允许控制器的程序的操作有关的信息(例如,关于设置状态和菜单的信息) 105 控制第一移动终端 100 . 记忆单元 113 存储第三移动终端的待机指令 300 和第四个移动终端 400 . 记忆单元 113 存储从第二移动终端接收的图像数据 200 , 第三个移动终端 300 ,以及第四个移动终端 400 ,并且还可以将映射到对应终端的图像数据存储在第一移动终端的电话簿(未示出)中 100 . [0047] 音频单元 115 将通过麦克风 MIC 输入的模拟音频信号转换为数字信号,将数字信号提供给控制器 105 , 转换从控制器输出的数字音频信号 105 转换成模拟音频信号,并通过扬声器SPK再现模拟音频信号。 [0048] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0049] 参考图。 参照图3A和3B,同时第一移动终端 100 与第二移动终端进行视听通信 100 (S 301 )、移动通信网络 500 接收来自第三移动终端的视听通信请求 300 (S 303 )。 在步骤 S 301 ,第一款移动终端 100 处于视听通信状态,摄像单元 107 第一个移动终端100 获取第一移动终端用户的图像 100 , 图像处理器 109 处理用户图像,显示单元 111 显示用户图像,并将麦克风MIC和扬声器SPK转换为操作状态。 [0050] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三终端 300 那是第一个移动终端 100 正在进行视听交流(S 305 )。 [0051] 第三个移动终端 300 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 307 )。 如果是第三个移动终端 300 第三移动终端保持视听通信待机状态 300 向移动通信网络发送待机状态维持消息 500 (S 309 )。 [0052] 此后,移动通信网络 500 发送关于第三个移动终端的信息 300 到第一移动终端 100 (S 311 )并形成第一移动终端之间的通信通道 100 第三个移动终端 300 . 第三移动终端信息 300 可以包括第三移动终端的联系方式和图像数据 300 . [0053] 移动通信网络 500 接收来自第四移动终端的视听通信请求 400 (S 313 ),并发送有关第一移动终端状态的消息 100 到第四个移动终端 400 通知第四移动终端 400 那是第一个移动终端 100 正在进行视听交流(S 315 )。 [0054] 第四款移动终端 400 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 317 )。 如果第四个移动终端 400 第四移动终端保持视听通信待机状态 400 向移动通信网络发送待机状态维持消息 500 (S 319 )。 [0055] 此后,移动通信网络 500 发送第四个移动终端的信息 400 到第一移动终端 100 (S 321 )并形成第一移动终端之间的通信通道 100 和第四个移动终端 400 . 第四移动终端信息 400 可以包括第四移动终端的联系信息和图像数据 400 . [0056] 第一个移动终端 100 确定第一移动终端之间的通信信道 100 第三个移动终端 300 在步骤 S 形成 311 ,以及第一移动终端之间的通信信道 100 和第四个移动终端 400 在步骤 S 形成 321 . [0057] 此后,第一移动终端 100 通过按照接收到请求的顺序列出移动终端,设置并显示请求视听通信的移动终端的待机顺序(S 323 )。 在本示例性实施例中,由于第三移动终端 300 在第四台移动终端之前请求视听通信 400 , 第三个移动终端 300 具有最高的待机位置。 [0058] 当第一个移动终端 100 想要更改显示的待机顺序(S 325 ),第一款移动终端 100 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 327 )。 通过选择第三移动终端的图像数据输入更改待机顺序的请求 300和第四个移动终端 400 以更改模式或待机顺序显示。 [0059] 移动通信网络 500 接收待机顺序变更请求消息REQ_MSG,变更第三移动终端的待机顺序 300 和第四个移动终端 400 (S 329 )。 [0060] 移动通信网络 500 临时存储更改后的待机订单(S 331 )并发送备用订单变更完成消息RES_MSG通知第一移动终端 100 第三个移动终端的待机订单变更 300 和第四个移动终端 400 (S 333 )。 [0061] 第一个移动终端 100 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG更改并显示待机命令 500 (S 335 )。 [0062] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 337 )、移动通信网络 500 指在步骤中临时存储的已更改的备用订单 331 (S 339 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 341 )。 [0063] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 343 )。 [0064] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0065] 参考图。 4、控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 (S 401 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . 当移动端 100 在执行视听通信时从至少一个移动终端接收视听通信请求(S 403 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 405 )。 [0066] 如果有至少两个移动终端请求视听通信,则控制器 105 根据接收视听通信请求的顺序设置待机命令,并在显示单元上显示设置的待机命令 111 (S 407 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0067] 控制器 105 判断设置的待机顺序是否改变(S 409 )。 如果设置的待机顺序没有改变,则过程继续到步骤S 419 . [0068] 如果设置的待机顺序发生了变化,控制器 105 控制射频单元 101 发送消息REQ_MSG,请求移动终端(这里是第三个移动终端)的待机命令 300 和第四个移动终端 400 ) 通过移动通信网络进行更改 500 (S 411 )。 [0069] 此后,控制器 105 接收移动通信网络发送的备用订单变更完成消息RES_MSG 500 通过射频单元 101 (S 415 )。 控制器 105更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据接收到的待机指令变更完成消息RES_MSG,在人机界面上显示变更后的待机指令 111 (S 417 )。 [0070] 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 419 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 421 )。 第一个移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单位置在步骤 S 更改为最高位置 417 ,或与第三个移动终端 300 ,它在步骤 S 中设置的待机顺序中的最高位置 407 . [0071] 如果在步骤中请求视听通信的移动终端的数量不是至少两个 405 , 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 423 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 425 )。 [0072] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0073] 参考图。 参见图5A和5B,步骤S 501 到 S 523 图。 图5A与步骤S基本相同 301 到 S 323 图。 与图3A相同,因此省略其描述。 [0074] 如果第四个移动终端 400 待机订单仓位低于第三移动终端 300 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 525 )、移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 (S 527 ) 和移动通信网络 500 向第三移动终端发送备用订单变更请求消息REQ_MSG 300 (S 529 )。 待命订单变更请求消息REQ_MSG可以由第四移动终端发送 400 同时第四个移动终端 400 向移动通信网络发送视听通信请求消息 500 在步骤 S 513 . [0075] 第一个移动终端 100 响应备用订单更改请求消息REQ_MSG(S 531 ),以及第三个移动终端 300 响应备用订单更改请求消息REQ_MSG(S 533 )。 [0076] 第一个移动终端 100 然后向移动通信网络发送备用订单更改批准消息ACC_MSG 500 确认批准备用订单的更改(S 535 ),以及第三个移动终端 300 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500确认批准备用订单的更改(S 537 )。 [0077] 移动通信网络 500 更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据从第一移动终端接收到的待命订单变更批准消息ACC_MSG 100 在步骤 S 535 并从第三个移动终端 300 在步骤 S 537 (S 539 )。 [0078] 移动通信网络 500 临时存储更改的备用订单(S 541 )并向第一移动终端发送备用订单变更完成消息RES_MSG 100 (S 543 ),第三个移动终端 300 (S 545 )、第四个移动终端 400 (S 547 )。 [0079] 第一个移动终端 100 更改并显示在第三个移动终端设置的待机指令 300 和第四个移动终端 400 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG 500 (S 549 )。 [0080] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 551 )、移动通信网络 500 指的是在步骤 S 临时存储的更改后的待机命令 541 (S 553 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 555 )。 [0081] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 557 )。 [0082] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0083] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 . [0084] 此后,如果第一移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG批准待命订单变更 100 向移动通信网络发送确认批准的备用订单更改批准消息ACC_MSG 500 . 当移动通信网络 500 接收待命订单变更批准消息ACC_MSG,移动通信网络 500 相应地更改备用顺序。 移动通信网络 500 暂存变更后的待命订单,并向第一移动终端发送待命订单变更完成消息RES_MSG 100 . [0085] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0086] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 第三个移动终端 300 . 如果第一个移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 100 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . 如果是第三个移动终端 300第三移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . [0087] 当至少一个第一移动终端 100 第三个移动终端 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 , 移动通信网络 500 不改变待命订单,向第一移动终端发送待命订单变更不批准消息N_ACC_MSG 100 , 第三个移动终端 300 ,以及第四个移动终端 400 . [0088] 进一步地,如果第一移动终端 100 批准备用订单和第三个移动终端的更改 300 在接收到来自移动通信网络的待命订单更改不批准消息N_ACC_MSG时,响应待命订单更改请求消息REQ_MSG不批准待命订单的更改 500 通知它待机顺序没有改变,因为第三个移动终端 300 不批准备用订单变更,第一个移动端 100 可以向移动通信网络发送备用订单更改请求消息REQ_MSG 500 从而可以强制改变第三移动终端的待机顺序 300 和第四个移动终端 400 . [0089] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0090] 参考图。 6、控制器 105 控制射频单元 101 让第一个移动终端 100 与第二移动终端进行视听通信 200 (S 601 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . [0091] 当控制器 105 在进行视听通信时从至少一个移动终端接收视听通信请求(S 603 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 605 )。 [0092] 如果有至少两个移动终端请求视听通信,则控制器 105 在视听通信请求命令中设置待机命令并在显示单元中显示该命令 111 (S 607 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0093] 如果控制器 105 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 (S 609 ), 控制器 105 判断移动端是否 100 响应备用订单更改请求消息,批准备用订单的更改(S 611 )。 如果移动端 100 不批准备用订单的变更,流程继续步骤S 619 . [0094] 如果移动端 100 批准备用订单的更改,控制器 105 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500 (S 613 )。 [0095] 控制器 105 判断移动端是否 100 从移动通信网络接收备用订单更改完成消息RES_MSG 500 (S 615 )。 如果移动端 100 未收到来自移动通信网络的备用订单更改完成消息 RES_MSG 500 , 过程在步骤 S 继续 619 . 如果移动端 100接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 , 控制器 105 根据接收到的待机命令更改完成消息RES_MSG更改待机命令,并在人机界面显示更改后的待机命令 111 (S 617 )。 [0096] 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 619 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 621 )。 例如,第一移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单仓位已在步骤 S 变为最高仓位 617 ,或与第三个移动终端 300 在步骤 S 中设置的待机顺序中的最高位置 607 . [0097] 如果在步骤S请求视听通信的移动终端的数量不是至少两个 605 , 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 623 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 625 )。 [0098] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 [0099] 参考图。 7、同时第一移动终端 100 与第二移动终端进行视听通信 200 通过移动通信网络 500 (S 701 )、移动通信网络 500 接收与第一移动终端进行视听通信的请求 100 从第三个移动终端 300 (S 703 )。 [0100] 移动通信网络 500 形成第一移动终端之间的通信通道 100 第三个移动终端 300 并发送关于第三移动终端的信息 300 连同对第一移动终端的视听通信请求 100 (S 705 )。 第三移动终端信息 300 可以是第三移动终端的用户信息(例如电话号码) 300 和/或包括第三移动终端的图像数据的信息 300 . [0101] 第一个移动终端 100 显示从第三移动终端接收到的图像数据 300 (S 707 )。 第一个移动终端 100 可以进一步显示消息(例如弹出窗口)以批准与第三移动终端的视听通信的连接 300 . [0102] 如果第一个移动终端 100 批准与第三个移动终端的视听通信 300 (S 709 )、移动通信网络 500 结束第一移动终端之间的视听通信 100 第二移动终端 200或者转换第一移动终端之间的视听通信状态 100 第二移动终端 200 到待机状态(S 711 )。 此后,移动通信网络 500 实现第一移动终端之间的视听通信 100 第三个移动终端 300 (S 713 )。 [0103] 如上所述,根据本发明,通过在第一移动终端与第二移动终端执行视听通信时改变至少两个请求视听通信的移动终端的待机顺序,可以与选择的请求视听的移动终端执行视听通信 通信,可以为第一移动终端的用户提供更大的便利。 [0104] 此外,通过在第一移动终端与第二移动终端进行视听通信的同时,根据从请求视听通信的至少两个移动终端中的具有较低待机位置的移动终端接收到的用于改变待机命令的请求来改变待机命令, 可以与选择的请求视听通信的移动终端进行视听通信,这可以为具有较低待机位置的待机状态的移动终端的用户提供更大的便利。 [0105] 另外,通过在第一移动终端与第二移动终端进行视听通信的同时显示关于请求视听通信的移动终端的信息,用户可以容易地检查处于待机状态的移动终端。 [0106] 对于本领域的技术人员来说,在不脱离本发明的精神或范围的情况下,可以对本发明进行各种修改和变化是显而易见的。 因此,本发明旨在覆盖本发明的修改和变化,只要它们落入所附权利要求及其等同物的范围内。(String), 111527(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.486 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.487 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.487 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.488 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.488 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.489 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.489 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.490 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.490 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.491 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.491 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.491 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270639(Integer), KR100790787B1(String), 1046996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.493 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.493 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.493 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270639(Integer), US20080171563A1(String), 1046997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.494 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.494 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.494 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270639(Integer), US7801528B2(String), 1046998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.495 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.496 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.496 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7801528B2(String), US7801528B2(String), 1284998400(Integer), 270639(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.497 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.498 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.498 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.500 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.500 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.500 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.501 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.502 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.502 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.511 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.511 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.512 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.523 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.524 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.524 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.525 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.525 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.526 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184956(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.535 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.535 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.536 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.548 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.548 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.548 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.550 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.551 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.551 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.552 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.553 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.553 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.554 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.554 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.555 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.555 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.556 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.556 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.557 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.558 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.558 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.565 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.566 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.566 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.574 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.576 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.576 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.578 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.579 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.579 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.592 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.593 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.593 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\75a9dc5127a643198310ab84237a9bbf.png(String), 184957(Integer), 75a9dc5127a643198310ab84237a9bbf.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.600 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.600 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.600 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.602 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.602 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.602 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for obtaining location information about mobile terminal(String), 移动终端及获取移动终端位置信息的方法(String), US9451580B2(String), The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal. The method for obtaining location information about the mobile terminal comprises: turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal.(String), 本发明实施例提供一种移动终端及获取移动终端位置信息的方法。 获取移动终端位置信息的方法包括:打开移动终端的卫星定位模块,获取移动终端当前位置信息后关闭卫星定位模块,并将当前位置信息作为初始位置信息。 ; 移动终端的传感模块采集移动终端的运动信息,并根据该运动信息计算移动终端的位移变化量; 根据初始位置信息和移动终端的位移变化,获取移动终端的实际位置信息。(String), US14/436195(String), 1374163200(Integer), US9451580B2(String), 1474300800(Integer), 1474300800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 5(Integer), 27(Integer), CN101464155A | CN102169182A | CN102243315A | CN102901975A | CN1914517A | JP1988108285A | JP1989278879A | JP1990212713A | JP1991237788A | JP1994111196A | JP1995001210A | JP2001059738A | JP2002255664A | JP2006242578A | JP2006279266A | JP2008063815A | JP2008067681A | JP2010038712A | JP2010038798A | JP2010120968A | JP2011149925A | JP2011164089A | JP2011176576A | JP2013029915A | US20100253503A1 | US20130102268A1 | US20160007405A1(String), \20230420\75a9dc5127a643198310ab84237a9bbf.png(String), 10(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.610 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.610 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.610 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.613 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.621 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.621 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Parameters: 1836(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.622 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.625 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Preparing: UPDATE os_task SET type=?, uid=?, ctime=?, tid=?, mfields=?, mun=?, endtime=?, status=?, filename=?, filesize=?, downexcel=?, old_name=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.625 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Parameters: 1(Integer), 1(Integer), 1681975270(Integer), 249(Integer), 0(Integer), 99(Integer), 1681975307(Integer), 3(Integer), c64b1db2b53e45ae99c88b5258f47f34.XLSX(String), 6093542(Long), \20230420\c64b1db2b53e45ae99c88b5258f47f34.XLSX(String), 手机-美国.XLSX(String), 1836(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:21:47.632 DEBUG 3548 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.571 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.587 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.606 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.727 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.729 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.730 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.755 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.756 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.758 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.761 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.762 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 249(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:15.765 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:16.014 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:16.015 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:16.016 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:16.029 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:16.030 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:16.031 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:30.906 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:30.906 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Parameters: 249(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:30.908 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:30.916 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Preparing: SELECT id,uid AS userId,tenantId,tid AS projectId,addtime AS createTime,remark,type FROM os_distribution_doing WHERE (tid = ? AND uid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:30.916 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Parameters: 249(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:30.918 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:31.561 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert ==> Preparing: INSERT INTO os_task ( type, uid, ctime, tid, mfields, mun, status, filename, filesize, downexcel, old_name ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:31.562 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert ==> Parameters: 1(Integer), 1(Integer), 1681975531(Integer), 249(Integer), 0(Integer), 99(Integer), 0(Integer), e7f4b27fca7e420d940b1f8bfe612406.XLSX(String), 6093542(Long), \20230420\e7f4b27fca7e420d940b1f8bfe612406.XLSX(String), 手机-美国.XLSX(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:31.571 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:31.901 DEBUG 14812 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:31.901 DEBUG 14812 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:31.903 DEBUG 14812 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8adc42df29884b6da6ef5689040fa4b2.png(String), 184950(Integer), 8adc42df29884b6da6ef5689040fa4b2.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:33.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.019 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal system, mobile terminal, external device, and input/output method of mobile terminal(String), 移动终端系统、移动终端、外部设备以及移动终端的输入/输出方法(String), US20100093394A1(String), A mobile terminal system including a mobile terminal and an external device is provided. The mobile terminal includes a first external device interface to output screen information to the external device and to receive operation information from the external device. The external device includes a display section to display and output the screen information, a user input section used when a user inputs the operation information on the mobile terminal, and a second external device interface to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 提供了一种移动终端系统,包括移动终端和外部设备。 移动终端包括第一外部设备接口以将屏幕信息输出到外部设备并从外部设备接收操作信息。 外部设备包括用于显示和输出屏幕信息的显示部分、当用户在移动终端上输入操作信息时使用的用户输入部分、以及用于从移动终端接收屏幕信息并输出的第二外部设备接口。 向移动终端发送通过用户输入部分输入的操作信息。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), US12/578279(String), 1255363200(Integer), US20100093394A1(String), 1271260800(Integer), 美国(String), 2(Integer), 2(Integer), JP(String), 3(Integer), 15(Integer), US20010052798A1 | US20030034898A1 | US20040051499A1 | US20060077046A1 | US20060082818A1 | US20060220878A1 | US20070030881A1 | US20080179963A1 | US20080239408A1 | US20090086105A1 | US20110136541A1 | US5847447A | US6781635B1 | US7976394B2 | US8004615B2(String), \20230420\8adc42df29884b6da6ef5689040fa4b2.png(String), 15(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 1. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 1.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 2. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 2.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 0(Integer), 1(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 3. The mobile terminal system according to claim 2,wherein the coil provided in the first external device interface is a coil for power reception,the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coils.(String), 3.根据权利要求2所述的移动终端系统,其中第一外部设备接口中设置的线圈为受电线圈,第二外部设备接口中设置的线圈为电力传输线圈,以及利用线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 4. The mobile terminal system according to claim 1 or 2,wherein the mobile terminal is a mobile phone, andthe screen information is video data or still image data received through a mobile phone network.(String), 4.根据权利要求1或2所述的移动终端系统,其中移动终端为手机,屏幕信息是通过手机网络接收到的视频数据或静止图像数据。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 5. The mobile terminal system according to claim 1 or 3,wherein the first and second external device interfaces perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and also reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 5.根据权利要求1或3所述的移动终端系统,其中第一和第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 6. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 6.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 7. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 7.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 8. The mobile terminal according to claim 7,wherein the coil provided in the first external device interface is a coil for power reception, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the first external device interface and a coil for power transmission provided in the second external device interface.(String), 8.根据权利要求7所述的移动终端,其中第一外部设备接口中设置的线圈为受电线圈,利用第一外部设备接口中设置的线圈与第二外部设备接口中设置的电力传输线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 9. The mobile terminal according to claim 6 or 8,wherein the first external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 9.根据权利要求6或8所述的移动终端,其中第一外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 10. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda display section which outputs the screen information received from the mobile terminal.(String), 10.一种在如权利要求1所述的移动终端系统中运行的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 11. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; anda display section which outputs the screen information received from the mobile terminal.(String), 11.一种运行在如权利要求1所述的移动终端系统中的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 12. The external device according to claim 11,wherein the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the second external device interface and a coil for power reception provided in the first external device interface.(String), 12.根据权利要求11所述的外部设备,其中第二外部设备接口中设置的线圈为电力传输线圈,以及利用设置在第二外部设备接口中的线圈与设置在第一外部设备接口中的用于受电的线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 13. The external device according to claim 10 or 12,wherein the second external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 13.根据权利要求10或12所述的外部设备,其中第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 14. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 14.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184950(Integer), 15. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 15.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 1(Integer), 14(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111521(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.209 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.210 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.213 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184950(Integer), BACKGROUND OF THE INVENTION [0001]1. Field of the Invention [0002]The present invention relates to a mobile terminal system including a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal, a mobile terminal, an external device, and an input/output method of the mobile terminal. In particular, the present invention relates to a mobile terminal system which outputs image data and sound data received in a mobile terminal to the outside through an external device and which allows the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0003]2. Description of the Related Art [0004]Mobile phones have succeeded the carphones pioneered as a mobile communications system, and have rapidly spread since the 1990s as the terminals become small, light, and inexpensive and the service charges become low. Moreover, with the spread of computers and the development of broadband network techniques including the Internet, E-mail and web search/access can be performed on mobile phones and various applications, such as music or video reproduction and games, can be executed. [0005]However, although the range of application of mobile phones is diversified, there are many restrictions in input and output since a portable size is necessary for mobile phones. For example, the screen size is diagonally about 5 to 10 cm. In this case, high-resolution display causes problems in visibility, for example, characters with the same font size become very small, even though the resolution is increasing due to the development of flat panel manufacturing technology in recent years. [0006]Furthermore, an input section provided in the mobile phone generally has only a numeric keypad of 0 to 9, keys by which up and down and left and right input operations are possible, and some other keys. Compared with a keyboard of a personal computer provided with 60 to 100 keys, the number of keys of the mobile phone is small and the input operation is also difficult. [0007]In recent years, the mobile phone with tens of keys similar to the QWERTY type keyboard has also appeared. However, each of the keys is small due to the portability restriction on the device size. For this reason, the input operation is still difficult. [0008]In order to cope with such a problem, a method of connecting a mobile phone to an external device with a relatively large screen or an input device which is easy to perform an input operation may be considered. [0009]For example, a display processing system using a mobile terminal is proposed. In the display processing system, an image displayed on a liquid crystal screen of a mobile phone can be displayed on a television screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2001-352373). [0010]In addition, a screen display device which has an entry for connecting a mobile phone is proposed. The screen display device displays image data received in the mobile phone on a large screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2002-116843). [0011]In addition, a mobile phone with a separate monitor is proposed. The mobile phone displays data displayed on a monitor built in the mobile phone or downloaded display data on the separate monitor (for example, refer to Japanese Unexamined Patent Application Publication No. 2003-78597). [0012]However, in order to transmit or receive data by connecting a mobile phone to an external device, a plurality of signal transmission lines for input/output of a video signal, input/output of a sound signal, input/output of a user operation signal, and the like is necessary (refer to FIG. 10). That is, for the connection between the mobile phone and the external device, a plurality of cables is used for video, sound, and user operation or a plug cable having a terminal with many poles is used. In the former case where a plurality of cables is used, the connection and disconnection operations of the cables are troublesome for the user. Moreover, in the latter method of using the plug cable, there is a problem that it becomes difficult to secure the place for disposing the plug in the main body of the small mobile phone as the number of poles increases. In addition, problems also occur such as the device becoming expensive due to the cost of components, such as connectors, and difficulty in obtaining a contact point between the connectors with sufficient strength. [0013]In addition, when the classification of input or output signal changes with the model of the mobile phone, the number of poles of the plug also changes. In this case, the connectors for the external device are not compatible among different models, which is inconvenient. SUMMARY OF THE INVENTION [0014]In view of the above, it is desirable to provide a mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0015]In addition, it is desirable to provide a mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0016]According to a first embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0017]The “system” referred to herein means a logical group of a plurality of devices (or functional modules for realizing specific functions), and it does not matter whether the devices or the functional modules exist in a single housing. [0018]According to a second embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0019]Here, according to a third embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the power supply, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0020]In addition, according to a fourth embodiment of the present invention, the mobile terminal may be a mobile phone, and the screen information may be video data or still image data received through a mobile phone network. [0021]In addition, according to a fifth embodiment of the present invention, the first and second external device interfaces may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0022]In addition, according to a sixth embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0023]In addition, according to a seventh embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0024]Here, according to an eighth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0025]In addition, according to a ninth embodiment of the present invention, the first external device interface of the mobile terminal may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0026]In addition, according to a tenth embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a display section which outputs the screen information received from the mobile terminal. [0027]In addition, according to an eleventh embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; and a display section which outputs the screen information received from the mobile terminal. [0028]Here, according to a twelfth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0029]In addition, according to a thirteenth embodiment of the present invention, the second external device interface of the external device may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0030]In addition, according to a fourteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0031]In addition, according to a fifteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0032]According to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0033]Moreover, according to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0034]According to the first to third, sixth to eighth, tenth to twelfth, fourteenth, and fifteenth embodiments of the present invention, the received data can be displayed on the large screen and the mobile terminal can be operated by the input from an easy-to-use keyboard simply by placing the mobile terminal, in which the size of the display device or input device is not sufficient, on the external device. [0035]In addition, according to the fourth embodiment of the present invention, video data or still image data downloaded from the Internet to the mobile phone can be displayed using the large screen of the external device. [0036]In addition, according to the fifth, ninth, and thirteenth embodiments of the present invention, transmission using a small number of contact points is performed between the mobile phone and the external device. This is advantageous in that the connection interface is simplified, the component cost for the connection section is reduced, the device is small-sized, and deterioration of the contact point is prevented. These effects can be further improved by applying wireless connection, such as electric field transmission, to the connection interface. [0037]Moreover, according to the embodiments of the present invention, since it is sufficient to provide a simple connection interface with an external device, restrictions in the design can be reduced. [0038]Additional purposes, characteristics, and advantages of the present invention will be apparent from the detailed description made in the following embodiment of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS [0039]FIG. 1 is a diagram schematically illustrating the configuration of a mobile terminal system according to an embodiment of the present invention; [0040]FIG. 2 is a diagram illustrating an example of the configuration of transmitting the parallel data serially; [0041]FIG. 3 is a characteristic curve illustrating the frequency spectrum of a signal on a power line; [0042]FIG. 4A is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0043]FIG. 4B is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0044]FIG. 5 is a diagram illustrating a write sequence example of a bus in a mobile phone and a bus in an external device when performing a write operation from the mobile phone to an LCD of the external device; [0045]FIG. 6 is a diagram illustrating a read sequence example of a bus in the mobile phone and a bus in the external device when performing an operation of reading the input information on a keyboard of the external device from the mobile phone; [0046]FIG. 7 is a diagram illustrating an interrupt sequence example of the bus in the mobile phone and the bus in the external device when an interrupt occurs on the keyboard of the external device; [0047]FIG. 8 is a diagram illustrating a format example of a transmission frame between the mobile phone and the external device; [0048]FIG. 9 is an illustration of an application image of the mobile terminal system shown in FIG. 1; and [0049]FIG. 10 is a diagram illustrating an example of the configuration of a past mobile terminal system. DESCRIPTION OF THE PREFERRED EMBODIMENTS [0050]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. [0051]FIG. 1 is a schematic diagram illustrating the configuration of a mobile terminal system according to an embodiment of the present invention. The system shown in FIG. 1 includes a mobile phone, which receives image data and sound data, and an external device, which outputs the image data and the sound data to the outside or which is used when a user operates the mobile phone. [0052]A mobile phone 100 includes a processor 101, various input/output devices 104 to 106, and an external device interface 107 for interfacing with an external device 120. Moreover, although the mobile phone 100 includes circuit modules for radio communications and the like, they are not shown because they are not directly related with the gist of the present invention. [0053]The processor 101 is connected to the various input/output devices 104 to 106 by a bus signal line group 110, a chip select signal 111, and an interrupt signal 112. [0054]The bus signal line group 110 includes signal lines, such as address, data, and enable. In addition to the various input/output devices 104 to 106, the bus signal line group 110 is also connected to the external device interface 107. [0055]The chip select signal 111 is a signal which is used when the processor 101 selects a circuit chip of one of the various input/output devices 104 to 106 through a bus interface 102. In addition, the interrupt signal 112 is a signal, which is used when the various input/output devices 104 to 106 notify the processor 101 of the occurrence of an event, and is input to an interrupt controller 103. The chip select signal 111 and the interrupt signal 112 are prepared in a quantity equal to the number of input/output devices and are also connected to the external device interface 107. [0056]First, an operation on the side of the mobile phone 100 will be described. [0057]When outputting data to the screen of an LCD 104, the processor 101 outputs image data to the LCD 104 using the bus interface 102. When outputting the data to the LCD 104, the bus interface 102 enables the chip select signal 111 connected to the LCD 104 so that the LCD 104 receives the image data from the processor 101 and displays the data on the screen. For example, video data or still image data downloaded through the mobile phone network from a web site on the Internet can be displayed on the screen of the LCD 104. [0058]In addition, also when outputting data to a speaker 105 or other output devices (not shown), the processor 101 similarly enables only the chip select signal 111 connected to the corresponding output device so that the output device receives the data from the processor 101 and reproduces and outputs the data. For example, sound data, such as music, downloaded through the mobile phone network from a web site on the Internet can be reproduced in the speaker 105. [0059]On the other hand, when there is a user input operation on a keyboard 106, the keyboard 106 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. The processor 101 which has received the interrupt receives the data, which has been input on the keyboard 106, through the bus 110. In this case, the bus interface 102 enables the chip select signal 111 connected to the keyboard 106 so that the keyboard 106 can output the data to the bus 110 and the processor 101 can receive the data. [0060]In addition, the same is true for the cases where an input operation has been performed by other input devices (not shown). That is, the input device generates an interrupt in response to the user input operation and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. On the other hand, the bus interface 102 enables the chip select signal 111 connected to the corresponding input device so that the input device outputs the data to the bus 110 and the processor 101 receives the data. [0061]Having described the data input/output operations between the input/output devices 104 to 106 and the processor 101, it may be understood that read and write operations of common registers for each input/output device are similarly realized by the above-described bus access method. [0062]In the system shown in FIG. 1, the mobile phone 100 is connected to the external device 120 through the external device interfaces 107 and 121. The external device 120 includes various enhanced input/output devices as user interfaces, such as an LCD 122 with a relatively large screen, a multi-channel speaker 123, and a large-sized keyboard 124 with tens of keys, such as alphanumeric keys. In addition, although not shown, the external device 120 may have a charge function for the mobile phone 100. [0063]In the past, a method of using a plug cable was commonly adopted for connection between a mobile phone and an external device. In this case, however, there are some problems as already stated. On the other hand, in the present embodiment, the external device interfaces 107 and 121 perform parallel-to-serial conversion of the address information and data information transmitted through the bus and then transmit this information under the conditions in which it is superimposed on a power interface 113. For this reason, neither the number of cables nor the number of poles of the plug is increased. [0064]Next, a method of transmitting and receiving data under the conditions in which the external device 120 is connected to the mobile phone 100 will be described. [0065]First, the case where the screen information of the mobile phone 100 is output to the external device 120 will be described. [0066]The bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the external device interface 107 can receive from the processor 101 the data to be displayed on the screen. In this case, it is assumed that the chip select signal 111 includes the classification indicating that transmitted data is screen information. [0067]The external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. [0068]The external device interface 121 of the external device 120 includes a bus interface function (not shown) and an interrupt controller function (not shown). In addition, the external device interface 121 converts the serial data, which has been received from the mobile phone 100 through the power interface 113, into parallel data to thereby restore it as the same data as in the mobile phone 100 which includes the classification of the chip select signal 111, the address information, and the data information. Then, the external device interface 121 transmits the data to the LCD 122 through a bus 133 by enabling a chip select signal 131 connected to the LCD 122. Thus, the LCD 122 displays and reproduces the same screen information as in the mobile phone 100. For example, video data or still image data downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be displayed on the screen of the LCD 122 in the external device 120. [0069]Moreover, the same is true for the case where the other output information on the side of the mobile phone 100 is output to the external device 120. [0070]For example, when the sound information is output to the external device 120, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the data for sound output is transmitted from the processor 101 to the external device interface 107. In this case, the chip select signal 111 includes the classification indicating that the transmitted data is sound information. Then, the external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. On the other hand, the external device interface 121 of the external device 120 reproduces the same data as in the mobile phone 100 by performing serial-to-parallel conversion of the classification of the received chip select signal 111, the address information, and the data information and then transmits the data to the speaker 123 through the bus 133 by enabling the chip select signal 131 connected to the speaker 123. Thus, the speaker 123 reproduces and outputs the same sound information as in the mobile phone 100. For example, sound data, such as music, downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be reproduced in the speaker 123 of the external device 120. [0071]Next, a processing operation when a user input operation is performed using an input device of the external device 120 will be described. [0072]For example, when there is a user input operation on the keyboard 124, the keyboard 124 generates an interrupt and notifies the external device interface 121 through an interrupt signal 132. [0073]Upon receiving the interrupt signal, the external device interface 121 receives the data input on the keyboard 124 through the bus 133 by enabling the chip select signal 131 connected to the keyboard 124. Then, the external device interface 121 performs parallel-to-serial conversion of the classification of the chip select signal 131 and the address information and data information transmitted through the bus 132 and transmits such data to the power interface 113. [0074]Then, the external device interface 107 of the mobile phone 100 converts the serial data, which has been received from the external device 120 through the power interface 113, into parallel data to thereby restore it as the same data as in the external device 120 which includes the classification of the chip select signal 131, the address information, and the data information. In addition, the external device interface 107 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. [0075]When the processor 101 receives the interrupt, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107. In response to this, the external device interface 107 outputs the data to the bus 110. Thus, the processor 101 can receive the data input by the keyboard 124 of the external device 120. [0076]Moreover, the same is true for the case where other input information on the side of the external device 120 (String), 发明背景 [0001] 一、发明领域 [0002] 本发明涉及一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,移动终端,外部设备,以及输入/输出 移动端的方法。 具体地,本发明涉及一种移动终端系统,其通过外部设备向外部输出在移动终端中接收到的图像数据和声音数据,并且允许通过外部设备在移动终端上执行用户操作, 移动终端、外部设备和移动终端的输入/输出方法。 [0003] 二、相关技术说明 [0004] 移动电话作为移动通信系统的先驱,继承了车载电话的先河,随着终端的小型化、轻量化、低价化和服务费的降低,从1990年代开始迅速普及。 此外,随着计算机的普及和包括因特网在内的宽带网络技术的发展,可以在手机上进行电子邮件和网络搜索/访问,并且可以执行各种应用,例如音乐或视频播放和游戏。 [0005] 然而,虽然手机的应用范围多种多样,但由于手机需要便携的尺寸,因此在输入和输出方面存在很多限制。 例如,屏幕尺寸对角线约5至10厘米。 在这种情况下,尽管近年来由于平板制造技术的发展分辨率越来越高,但高分辨率显示会导致可见性问题,例如,相同字体大小的字符变得非常小。 [0006] 另外,手机中设置的输入部分一般只有0到9的数字键盘,以及可以进行上下左右输入操作的按键,以及其他一些按键。 与个人电脑的键盘有60到100个按键相比,手机的按键数量少,输入操作也比较困难。 [0007] 近几年,也出现了类似QWERTY键盘的几十个按键的手机。 然而,由于设备大小的便携性限制,每个密钥都很小。 为此,输入操作还是有难度的。 [0008] 为了解决这样的问题,可以考虑将移动电话连接到具有相对大屏幕的外部设备或易于执行输入操作的输入设备的方法。 [0009] 例如,提出了使用移动终端的显示处理系统。 在显示处理系统中,显示在移动电话的液晶屏幕上的图像可以显示在电视屏幕上(例如,参考日本未审查专利申请公开No.2001-352373)。 [0010] 此外,还提出了一种屏幕显示装置,其具有用于连接手机的入口。 屏幕显示设备在大屏幕上显示在移动电话中接收到的图像数据(例如,参考日本未审查专利申请公开No.2002-116843)。 [0011] 此外,还提出了一种带有独立显示器的移动电话。 移动电话显示在移动电话内置的监视器上显示的数据或在单独的监视器上下载的显示数据(例如,参考日本未审查专利申请公开No.2003-78597)。 [0012]然而,为了通过将移动电话连接到外部设备来发送或接收数据,用于视频信号的输入/输出、声音信号的输入/输出、用户操作信号的输入/输出的多条信号传输线 ,等等是必要的(参考图10)。 也就是说,对于移动电话和外部设备之间的连接,使用多根电缆用于视频、声音和用户操作,或者使用具有多极端子的插头电缆。 在使用多根电缆的前一种情况下,电缆的连接和断开操作对用户来说很麻烦。 此外,在后一种使用插头电缆的方法中,随着极数的增加,存在难以确保小型移动电话主体中用于布置插头的位置的问题。 此外,还存在由于连接器等部件的成本而导致装置变得昂贵、连接器之间的接触点难以获得足够强度的问题。 [0013] 另外,随着手机型号不同,输入或输出信号的分类发生变化时,插头的极数也会发生变化。 在这种情况下,外部设备的连接器在不同型号之间不兼容,这很不方便。 发明内容 [0014] 鉴于上述情况,期望提供一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如手机,以及连接到移动终端并能够输出图像数据的外部设备。 以及移动终端中接收到的声音数据通过外部设备发送到外部并允许用户通过外部设备在移动终端上执行操作、移动终端、外部设备以及移动设备的输入/输出方法 终端。 [0015] 此外,期望提供一种移动终端系统,其中移动终端和外部设备通过具有简单配置的接口相互连接,使得在移动终端中接收的图像数据和声音数据可以输出到 外部设备通过外部设备可以在移动终端上进行用户操作、移动终端、外部设备和移动终端的输入/输出方法。 [0016] 根据本发明第一实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作。 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0017] 这里所说的“系统”是指多个设备(或实现特定功能的功能模块)的逻辑集合,与设备或功能模块是否存在于一个外壳内无关。 [0018]根据本发明的第二实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0019] 这里,根据本发明的第三实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 即,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括电力电缆上传输的电流信号,还包括用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0020] 另外,根据本发明的第四实施例,移动终端可以是手机,屏幕信息可以是通过手机网络接收的视频数据或静止图像数据。 [0021] 此外,根据本发明的第五实施例,第一和第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据 通过对接收到的数据进行串并转换。 [0022] 此外,根据本发明的第六实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0023] 此外,根据本发明的第七实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0024]这里,根据本发明的第八实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0025] 此外,根据本发明的第九实施例,移动终端的第一外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0026] 此外,根据本发明的第十实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用。 终端; 第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电; 显示部分输出从移动终端接收的屏幕信息。 [0027] 此外,根据本发明的第十一实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用该用户输入部分。 终端; 第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息; 显示部分输出从移动终端接收的屏幕信息。 [0028] 这里,根据本发明的第十二实施例,第一外部设备接口中设置的线圈可以是用于电力接收的线圈,第二外部设备接口中设置的线圈可以是电力传输线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0029] 此外,根据本发明的第十三实施例,外部设备的第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在电力信号上,并且可以再现叠加在电源信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0030]另外,根据本发明的第十四实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0031] 另外,根据本发明第十五实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0032] 根据本发明的实施例,可以提供出色的移动终端系统,其包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,并且能够 将在移动终端中接收到的图像数据和声音数据通过外部设备输出到外部,并允许用户通过外部设备在移动终端上进行操作,移动终端,外部设备,输入/输出 移动端的方法。 [0033] 此外,根据本发明的实施例,可以提供出色的移动终端系统,其中移动终端和外部设备通过具有简单配置的接口彼此连接,使得接收到的图像数据和声音数据 移动终端中的信息可以通过外部设备输出到外部,用户可以通过外部设备对移动终端进行操作,移动终端,外部设备,移动终端的输入/输出方法。 [0034] 根据本发明的第一至第三、第六至第八、第十至第十二、第十四和第十五实施例,可以在大屏幕上显示接收到的数据,并且可以通过来自易于操作的输入来操作移动终端。 - 只需将显示设备或输入设备的尺寸不够大的移动终端放在外部设备上即可使用键盘。 [0035] 此外,根据本发明的第四实施例,可以使用外部设备的大屏幕来显示从互联网下载到移动电话的视频数据或静止图像数据。 [0036]此外,根据本发明的第五、第九和第十三实施例,在移动电话和外部设备之间执行使用少量接触点的传输。 这是有利的,因为简化了连接接口,降低了连接部分的组件成本,设备尺寸小,并且防止了接触点的劣化。 通过对连接接口应用无线连接,例如电场传输,可以进一步改善这些效果。 [0037] 此外,根据本发明的实施例,由于提供简单的与外部设备的连接接口就足够了,因此可以减少设计上的限制。 [0038] 本发明的其他目的、特征和优点将通过以下结合附图对本发明的实施例的详细描述而显而易见。 附图的简要说明 [0039] 图1是表示本发明的一个实施方式的移动终端系统的概略结构的图。 [0040] 图2是表示串行发送并行数据的结构例的图。 [0041] 图3是电力线上信号的频谱特性曲线。 [0042] 图4A是表示串行地发送并行数据的串行器的另一例的图。 [0043] 图4B是表示串行地发送并行数据的串行器的另一例的图。 [0044] 图5是表示从移动电话向外部设备的LCD进行写入时的移动电话内的总线和外部设备的总线的写入顺序例的图。 [0045] 图6是表示进行从移动电话读取外部设备的键盘的输入信息的操作时的移动电话内的总线和外部设备的总线的读取顺序例的图。 [0046] 图7是表示在外部设备的键盘上发生中断时的移动电话内的总线和外部设备内的总线的中断时序例的图。 [0047] 图8是表示移动电话与外部设备之间的传输帧的格式例的图。 [0048] 图9为图1所示的移动终端系统的应用程序图像示意图。 和 [0049] 图10是表示以往的便携终端系统的结构例的图。 优选实施例的描述 [0050] 在下文中,将参考附图描述本发明的实施例。 [0051] 图1是图示根据本发明实施例的移动终端系统的配置的示意图。 图1所示的系统包括接收图像数据和声音数据的移动电话,以及将图像数据和声音数据输出到外部或者当用户操作移动电话时使用的外部设备。 [0052] 一部手机 100 包括一个处理器 101 , 各种输入输出设备 104 到 106 , 和一个外部设备接口 107 用于连接外部设备 120 . 而且,虽然手机 100 包括无线电通信等电路模块,由于与本发明的主旨无直接关系,故未图示。 [0053] 处理器 101 连接到各种输入/输出设备 104 到 106 通过总线信号线组 110 , 片选信号 111 , 和一个中断信号 112 . [0054] 总线信号线组 110 包括信号线,例如地址、数据和启用。 除了各种输入/输出设备 104 到 106 ,总线信号线组 110 也连接到外部设备接口 107 . [0055] 片选信号 111 是处理器使用的信号 101 选择各种输入/输出设备之一的电路芯片 104 到 106 通过总线接口 102 . 此外,中断信号 112 是信号,在各种输入/输出设备时使用 104 到 106 通知处理者 101 一个事件的发生,并被输入到一个中断控制器 103 . 片选信号 111 和中断信号 112 准备了与输入/输出设备数量相等的数量,并连接到外部设备接口 107 . [0056] 一、手机端的一个操作 100 将被描述。 [0057] 将数据输出到 LCD 屏幕时 104 , 处理器 101 输出图像数据到LCD 104 使用总线接口 102 . 向 LCD 输出数据时 104 , 总线接口 102 启用片选信号 111 连接到液晶显示器 104 这样液晶显示器 104 从处理器接收图像数据 101 并将数据显示在屏幕上。 例如,通过手机网络从 Internet 上的网站下载的视频数据或静止图像数据可以显示在 LCD 的屏幕上 104 . [0058] 此外,当向扬声器输出数据时 105 或其他输出设备(未显示),处理器 101 同样只启用片选信号 111 连接到相应的输出设备,以便输出设备接收来自处理器的数据 101 并再现和输出数据。 例如,可以在扬声器中再现通过手机网络从互联网网站下载的音乐等声音数据 105 . [0059] 另一方面,当用户在键盘上进行输入操作时 106 , 键盘 106 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . 处理器 101 接收到中断 接收到键盘输入的数据 106 , 通过公交车 110 . 在这种情况下,总线接口 102 启用片选信号 111 连接到键盘 106 这样键盘 106 可以将数据输出到总线 110 和处理器 101 可以接收数据。 [0060] 另外,对于由其他输入设备(未图示)进行了输入操作的情况也是同样的。 即输入设备响应用户输入操作产生中断,通知中断控制器 103 处理器的 101 通过中断信号 112 . 另一方面,总线接口 102 启用片选信号 111 连接到相应的输入设备,使输入设备输出数据到总线 110 和处理器 101 接收数据。 [0061] 描述了输入/输出设备之间的数据输入/输出操作 104 到 106 和处理器 101 可以理解,对于每个输入/输出设备的公共寄存器的读写操作是通过上述总线访问方法类似地实现的。 [0062] 在图1所示的系统中,手机 100 连接到外部设备 120 通过外部设备接口 107 和 121 . 外部设备 120 包括各种增强型输入/输出设备作为用户界面,例如 LCD 122 屏幕比较大,多声道喇叭 123 , 和一个大尺寸的键盘 124 带有数十个键,例如字母数字键。 此外,虽然没有显示,外部设备 120 可能有手机充电功能 100 . [0063]以往,手机与外部设备的连接通常采用插头线的方式。 然而,在这种情况下,存在已经提到的一些问题。 另一方面,在本实施例中,外部设备接口 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些信息 113 . 为此,既没有增加电缆的数量,也没有增加插头的极数。 [0064] 接下来介绍一种在外部设备不可用的情况下发送和接收数据的方法 120 已连接手机 100 将被描述。 [0065] 一、手机屏幕信息的情况 100 输出到外部设备 120 将被描述。 [0066] 总线接口 102 启用片选信号 111 连接到外部设备接口 107 使外部设备接口 107 可以从处理器接收 101 要显示在屏幕上的数据。 在这种情况下,假定片选信号 111 包括指示传输的数据是屏幕信息的分类。 [0067] 外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . [0068] 外部设备接口 121 外部设备的 120 包括总线接口功能(未显示)和中断控制器功能(未显示)。 此外,外部设备接口 121 转换从手机接收到的串口数据 100 通过电源接口 113 , 转化为并行数据从而恢复为与手机中相同的数据 100 其中包括片选信号的分类 111 、地址信息和数据信息。 然后,外部设备接口 121 将数据传输到 LCD 122 通过公共汽车 133 通过使能片选信号 131 连接到液晶显示器 122 . 因此,液晶 122 显示和再现与手机相同的屏幕信息 100 . 例如,从互联网网站下载到手机的视频数据或静止图像数据 100 通过手机网络可以显示在液晶屏上 122 在外部设备中 120 . [0069] 而且,其他手机端输出信息的情况也是如此 100 输出到外部设备 120 . [0070] 例如,当声音信息输出到外部设备时 120 , 总线接口 102 启用片选信号 111 连接到外部设备接口 107 以便声音输出的数据从处理器传输 101 到外部设备接口 107 . 在这种情况下,片选信号 111 包括指示传输的数据是声音信息的分类。 然后,外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . 另一方面,外部设备接口 121 外部设备的 120 再现与手机中相同的数据 100 通过对接收到的片选信号进行分类串并转换 111 ,地址信息,数据信息,然后将数据传输给扬声器 123 通过公共汽车 133 通过使能片选信号 131 连接到扬声器 123 . 因此,演讲者123 再现和输出与手机相同的声音信息 100 . 例如,从互联网上的网站下载到手机中的音乐等声音数据 100 通过手机网络可以在音箱中重现 123 外部设备的 120 . [0071] 接下来,使用外部设备的输入设备进行用户输入操作时的处理操作 120 将被描述。 [0072] 例如,当键盘上有用户输入操作时 124 , 键盘 124 产生中断并通知外部设备接口 121 通过中断信号 132 . [0073] 接收到中断信号后,外部设备接口 121 接收键盘输入的数据 124 通过公共汽车 133 通过使能片选信号 131 连接到键盘 124 . 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0074] 然后,外部设备接口 107 手机的 100 转换从外部设备接收到的串行数据 120 通过电源接口 113 , 转换为并行数据,从而将其恢复为与外部设备中相同的数据 120 其中包括片选信号的分类 131 、地址信息和数据信息。 此外,外部设备接口 107 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . [0075] 当处理器 101 接收到中断,总线接口 102 启用片选信号 111 连接到外部设备接口 107 . 响应于此,外部设备接口 107 将数据输出到总线 110 . 因此,处理器 101 可以接收键盘输入的数据 124 外部设备的 120 . [0076] 此外,对于外部设备侧的其他输入信息的情况也是如此 120 被输入到手机 100 . [0077] 即输入设备响应用户输入操作等产生中断通知给外部设备接口 121 . 接收到中断信号后,外部设备接口 121 通过总线接收数据 133 通过使能片选信号 131 连接到相应的输入设备。 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0078] 外部设备接口 107 手机的 100 对片选信号的分类进行串并转换 131 、地址信息、从外部设备接收到的数据信息 120 ,从而恢复与外部设备中相同的数据 120 . 此外,外部设备接口 107 通知中断控制器 103 处理器的 101 通过中断信号 112 有来自外部设备的输入 120 . 然后,总线接口 102 启用片选信号 111 连接到外部设备 120 这样处理器 101 从外部设备接收输入数据 120 . [0079] 描述了输入/输出设备之间的数据输入/输出操作 122 到 124 外部设备的 120 和处理器 101 手机的 100,可以理解为外部设备的每个输入/输出设备的公共寄存器的读写操作 120 通过上述总线访问方法类似地实现。 [0080] 在本实施例中,手机与手机之间的接口 100 和外部设备 120 通过采用外部设备接口的方法简化了 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些数据 113 . [0081] 图2例示了串行传输并行数据的配置示例。 图2所示的传输系统包括串行器 200 和反序列化器 210 它们通过电源线相互连接 220 作为电源接口 113 . 假设这对序列化器 200 和反序列化器 210 双向设置于外部设备接口 107 手机的 100 和外部设备接口 121 外部设备的 120 . [0082] 序列化器 200 包括一个 PS(并行到串行)转换器 201 将并行信号转换为串行信号,PLL 部分 202 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 203 通过向串行信号添加标头等来执行编码,时序控制器 204 它控制传输时间,和一个司机 205 . [0083] 另一方面,反序列化器 210 包括一个接收器 212 , 解码器 213 它通过从报头、时钟恢复 (CR) 部分检测数据的头部来解码编码数据 214 它使用参考时钟 (Ref. CLK)、SP(串行到并行)转换器从接收到的数据中提取时钟 215 它将串行信号转换为原始并行信号,以及一个时序控制器 216 它控制接收时间。 [0084] 因此,输入到串行器的并行数据 P-DATA 和用于串行数据的时钟 P-CLK 200 转换为串行信号,通过解串器恢复为原来的并行数据P-DATA和时钟P-CLK 210 . [0085] 在图 2 所示的示例中,电源线 220 用作传输线,在叠加在电源线上的条件下传输串行信号 220 从外部设备 120 到手机 100 . 叠加部分 206 将传输信号叠加在用于供电的功率信号上。 基本上,叠加部分 206 将传输信号与电源线耦合 220 通过一个电容器并将电源信号与电源线耦合 220 通过扼流圈。 [0086] 到达解串器的传输信号 210 通过电源线 220 通过分离部分与电源信号分离 212 . 类似于叠加部分 206 , 在分离部分 211 ,在通过电容器切断直流分量之后提取传输信号,并且通过扼流圈从传输信号中切断功率信号。 [0087] 此外,可以提及曼彻斯特编码作为编码器中应用的编码方法的示例 203 和解码器 213. 在曼彻斯特编码中,当传输一个二进制值“0”时,它在位段中间由高电平变为低电平。 另一方面,当传输二进制值“1”时,它在比特部分的中间从低电平相反地变为高电平。 换言之,在曼彻斯特编码中,通过两次扩展频带来去除传输信号的DC分量。 由于曼彻斯特码的优点在于不包括直流分量并且容易提取时钟,因此认为曼彻斯特码适合与具有直流分量的电力叠加在同一传输线上。 电力线上信号的频谱 220 如图3所示。在图3中,附图标记 301 表示曼彻斯特码的频谱。 已知曼彻斯特码可以在不包括直流分量的情况下与功率信号一起传输。 [0088] 串行传输并行数据的串行器和解串行器的另一配置示例在图4A和4B中示出。 [0089] 序列化器 400 包括一个PS转换器 401 将并行信号转换为串行信号,PLL 部分 402 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 403 通过向串行信号添加标头等来执行编码,时序控制器 404 它控制传输时间,和一个司机 405 . 编码器编码的串行信号 403 被传输到一个线圈 406 通过司机 405 然后传输到解串器 410 通过线圈之间的电磁耦合。 [0090] 另一方面,反序列化器 410 包括一个线圈 411 它与线圈进行电磁耦合 406 在序列化器的一侧 400 , 一个差分接收器 412 , 放大器 413 放大由电磁耦合降低的信号电平,解码器 414 它从报头中检测数据的头部并对编码数据进行解码,时钟恢复(CR)部分 415 它使用参考时钟 (Ref. CLK)、SP 转换器从接收到的数据中提取时钟 416 它将串行信号转换为原始并行信号,以及一个时序控制器 417 它控制接收时间。 [0091] 当采用图2或图4A、4B所示的串行传输作为电源接口时 113 连接外部设备 120 和手机 100 相互之间,可以将数据叠加在电源信号上,并且可以在从外部设备进行充电的同时进行数据传输 120 到手机 100 . 此外,根据图4A和4B所示的串行传输方法,可以使用线圈在电场中传输数据。 结果,由于可以通过无线连接发送和接收数据,因此连接外部设备的电缆 120 用手机 100 变得不必要。 [0092] 接下来是手机之间进行数据收发时的总线访问操作 100 和外部设备 120 将被描述。 下面根据美国英特尔公司的80总线架构来描述总线访问操作。 然而,本发明不限于此。 [0093] 图 5 说明了总线的写入序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 从手机执行写入操作时 100 到液晶显示器 122 外部设备的 120 . [0094] 在手机里 100 ,处理器断言(启用)具有 LCD 分类的片选信号 101 . 随后,总线上的写信号 110 由处理器断言 101 然后将写数据传输到总线 110 . [0095] 通过这样的操作,数据被写入外部设备接口 107 手机的100 . 然后,外部设备接口 107 将请求写入的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0096] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 随后,外部设备接口 121 断言连接到 LCD 的片选信号 122 , 断言总线上的写信号 133 ,然后将写数据传输到总线 110 . 因此,将数据写入LCD 122 被执行。 结果,液晶 122 可以显示和再现与手机相同的屏幕信息 100 . [0097] 此外,可以理解为在每个移动电话中执行相同的总线写入序列 100 和外部设备 120 同样在手机输出其他信息的情况下 100 写入外部设备 120 . [0098] 图 6 说明了总线的读取序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 执行读取键盘输入信息的操作时 124 外部设备的 120 从手机 100 . [0099] 在手机里 100 ,具有键盘分类的片选信号被断言,然后总线上的读取信号 110 由处理器断言 101 . 然后,外部设备接口 107 手机的 100 将请求读取的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0100] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 然后,外部设备接口 121 断言连接到键盘的片选信号 124 然后在总线上断言读取信号 133 . 然后,键盘 124 将输入数据传输到总线 110 . [0101] 从键盘读取数据后 124 , 外接设备接口 121 将数据转换成串口数据串口传输给手机 100 通过电源接口 113 . [0102] 外部设备接口 107 手机的 100 提取键盘上的输入数据 124 通过将接收到的串行数据转换成并行数据,然后传输到总线 110 在读信号被断言的期间。 因此,处理器 101 可以从键盘读取输入数据 124 外部设备的 120 . [0103] 此外,可以理解,在每个移动电话中执行相同的总线读取序列 100 和外部设备 120 同样在外部设备的其他输入信息的情况下 120 在手机中读取 100 . [0104] 图 7 说明了总线的中断序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 当键盘发生中断时 124 外部设备的 120 . [0105] 键盘 124 断言中断信号 132 当中断发生时。 外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113. 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 断言中断信号 112 . [0106] 处理器收到中断信号后 101 根据上述过程执行总线访问(读或写)。 例如,总线接口 102 启用片选信号 111 连接到外部设备接口 107 , 这样处理器 101 读取键盘上的输入数据 124 从外部设备 120 通过公共汽车 110 . [0107] 随后,当键盘 124 否定中断信号 132 通过释放中断,外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113 . [0108] 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 否定中断信号 112 . 结果在手机端也释放了键盘中断 100 . [0109] 图 8 说明了移动电话之间的传输帧的格式示例 100 和外部设备 120 . [0110] 图8所示的传输帧在报头部分包括数据类型、设备类型和数据长度字段。 [0111] 数据类型字段长度为2位,用于区分传输帧对应的读、写、中断发生和中断释放。 例如0×00表示读,0×01表示写,0×02表示中断。 [0112] 设备类型字段,长度为2比特,用于区分传输帧是对哪个设备的读或写请求,或者是区分传输帧是来自哪个设备的中断发生或释放请求。 例如0×00表示LCD,0×01表示键盘,0×02表示扬声器。 [0113] 数据长度字段具有1个字节的长度,并且传输帧的数据(有效载荷)部分的长度例如以比特数来描述。 [0114] 此外,位 0 到最后一位连接在传输帧的数据部分。 [0115] 此外,图8所示的传输帧格式只是一个例子,本发明不限于此。 可以使用根据应用本发明的系统适当定义的任何传输帧格式。 此外,传输帧中可以包括使用校验和的错误检测和错误纠正等功能。 [0116] 图9是图1所示的移动终端系统的应用程序图像的图示。 [0117] 外部设备 901 包括液晶显示器 901 带有相对较大的屏幕和键盘 903 使用 QWERTY 排列中的所有键。 通过放置手机 904 在连接部分 902 , 手机屏幕 904 可以显示在LCD上 901 和手机 904 可以通过键盘上的用户输入进行操作 903 . [0118] 一个联络点 905 与手机连接 904 在连接部分提供 902 , 这样手机 904 可以充电,可以通过触点进行数据传输 905 . [0119] 然而,当如图 4A 和 4B 所示执行使用线圈的电场传输时,接触点 905 外部设备之间 900 和手机 904不存在,通过线圈进行通信 906 在外部设备中提供 900 . [0120] 本申请包含与 2008 年 10 月 15 日向日本专利局提交的日本优先权专利申请 JP 2008-266856 中公开的主题相关的主题,其全部内容通过引用并入本文。 [0121] 本领域技术人员应当理解,可以根据设计要求和其他因素进行各种修改、组合、子组合和变更,只要它们在所附权利要求或其等同物的范围内。(String), 111521(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), CN101729662A(String), 1046961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), CN101729662B(String), 1046962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), JP2010098484A(String), 1046963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), JP4893722B2(String), 1046964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270633(Integer), US20100093394A1(String), 1046965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100093394A1(String), US20100093394A1(String), 1271260800(Integer), 270633(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), HIDAKA, ISAO(String), 索尼公司(String), HIDAKA ISAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 184950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HIDAKA, ISAO(String), HIDAKA ISAO(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75899(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184950(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75899(Integer), 2(Integer), 184950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75899(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10075579B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.430 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.432 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e8eaf10620a141999ef712d533e9c0bd.png(String), 184951(Integer), e8eaf10620a141999ef712d533e9c0bd.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.453 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.454 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, user interface method in the mobile terminal, and cover of the mobile terminal(String), 移动终端、移动终端中的用户界面方法及移动终端的外壳(String), US10075579B2(String), A mobile terminal, a method in the mobile terminal, and a cover of the mobile terminal are provided for processing input. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined, and a second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area while the cover is closed over the touch screen is detected and the first input as a first control command is processed.(String), 本 发明提供一种移动终端、移动终端中的方法及移动终端的外壳,用于处理输入。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域,并定义了与封面的非窗口区域对应的移动终端的触摸屏的第二区域。 检测当盖板在触摸屏上关闭时第二区域中的第一输入,并且处理作为第一控制命令的第一输入。(String), US14/603760(String), 1421942400(Integer), US10075579B2(String), 1536595200(Integer), 1536595200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 7(Integer), 40(Integer), JP2006277739A | JP2008097966A | KR101285669B1 | KR1020080108839A | KR1020110025939A | KR1020130004769A | KR200464076Y1 | KR2020120005719U | US20040248621A1 | US20080062348A1 | US20100238119A1 | US20110065474A1 | US20110260980A1 | US20120098760A1 | US20120250241A1 | US20130083465A1 | US20130109435A1 | US20130181935A1 | US20130300679A1 | US20140073377A1 | US20140128131A1 | US20140185206A1 | US20140198070A1 | US20140204511A1 | US20140274214A1 | US20140292589A1 | US20140357330A1 | US20150105128A1 | US20150138021A1 | US20150155903A1 | US20150229754A1 | US20150280770A1 | US20160154512A1 | US20160277053A1 | US9307129B2 | WO2001028190A1(String), \20230420\e8eaf10620a141999ef712d533e9c0bd.png(String), 31(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 31 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 1. A method of processing input in a mobile terminal, the method comprising:identifying a first area of a touch screen of the mobile terminal corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 1.一种在移动终端中处理输入的方法,该方法包括:通过接收来自外壳的信息识别移动终端的触摸屏的第一区域对应于外壳的窗口区域和触摸屏的第二区域对应于外壳的非窗口区域;检测触摸屏上方的移动终端盖板是否合上;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 2. The method of claim 1, further comprising determining a type of the cover, wherein the first area and the second area are defined according to the type of the cover.(String), 2.如权利要求1所述的方法,还包括判断封面的类型,其中第一区域与第二区域是根据封面的类型定义的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 3. The method of claim 1, further comprising determining whether an event has occurred, while the cover is closed over the touch screen of the mobile terminal, wherein the first area and the second area are defined according to occurrence of the event.(String), 3.如权利要求1所述的方法,还包括在移动终端的触摸屏上盖合上时判断事件是否发生,其中第一区域和第二区域是根据事件的发生定义的。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 4. The method of claim 1, further comprising:detecting a third input in the first area while the cover is closed over the touch screen;processing the third input as a third control command; anddetecting a fourth input in the second area while the cover is closed over the touch screen; and processing the fourth input as a fourth control command,wherein the third input and the fourth input are of a same type, which is different from that of the first input and the second input.(String), 4.如权利要求1所述的方法,还包括:在触摸屏上盖合上时检测第一区域中的第三输入;将第三输入处理为第三控制命令;和在触摸屏上盖合上时检测第二区域中的第四输入;并将第四输入处理为第四控制命令,其中,第三输入与第四输入为同一类型,与第一输入与第二输入不同。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 5. The method of claim 1, further comprising receiving cover type information from the cover.(String), 5.如权利要求1所述的方法,还包括从封面接收封面类型信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 6. The method of claim 5, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 6.如权利要求5所述的方法,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 7. The method of claim 1, further comprising activating a part of the touch screen according to the first and second areas, while the cover is closed over the touch screen.(String), 7.如权利要求1所述的方法,还包括根据第一区域和第二区域激活触摸屏的一部分,同时关闭触摸屏上的盖体。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 8. The method of claim 1, further comprising, when the cover is closed over the touch screen, activating a screen of the first area and a touch sensing area of the second area.(String), 8.如权利要求1所述的方法,还包括,当盖合于触控屏幕上时,激活第一区域的屏幕和第二区域的触控感应区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 9. The method of claim 1, wherein processing the first input comprises displaying information in the first area according to the first input detected in the second area.(String), 9.如权利要求1所述的方法,其中处理第一输入包括根据在第二区域中检测到的第一输入在第一区域中显示信息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 10. The method of claim 9, wherein the information comprises at least one of music play information, a camera preview, busy call information, and information about at least one application.(String), 10.如权利要求9所述的方法,其中该信息包括音乐播放信息、相机预览、忙音信息和至少一个应用程序的信息中的至少一种。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 11. A mobile terminal comprising:a touch screen; anda processor configured to:identify a first area of the touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detect whether the cover of the mobile terminal is closed over the touch screen,detect an input in the touch screen while the cover is closed over the touch screen, determine whether the input is a first input in the first area or a second input in the second area, process a first control command according to the first input in the first area, and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 11.移动终端包括:触摸屏;和处理器配置为:通过接收来自外壳的信息,识别对应于移动终端外壳的窗口区域的触摸屏的第一区域和对应于外壳的非窗口区域的触摸屏的第二区域;检测触摸屏上方移动终端的盖板是否合上,在触摸屏上盖合上时检测触摸屏中的输入,判断输入是第一区域中的第一输入还是第二区域中的第二输入,根据第一区域中的第一输入处理第一控制命令第一区域,以及根据第二区域中的第二输入的第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 12. The mobile terminal of claim 11, wherein the non-window area of the cover includes a keypad configured to apply a key input, and the processor is further configured to detect the key input applied through the keypad of the non-window area of the cover in the second area.(String), 12.如权利要求11所述的移动终端,其中所述盖板的非窗口区域包括键盘,用于进行键输入,所述处理器还用于在所述第二区域中检测通过所述盖板的非窗口区域的键板施加的键输入。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 13. The mobile terminal of claim 12, wherein the processor is further configured to receive a text input as a result of detecting the key input through the keypad and control execution of a function according to the text input.(String), 13.如权利要求12所述的移动终端,其中处理器还被配置为接收作为检测通过小键盘的键输入的结果的文本输入,并根据文本输入控制功能的执行。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 14. The mobile terminal of claim 11, further comprising a receiver configured to receive cover type information from the cover,wherein the processor is further configured to check the cover type information about the cover and define the first and second areas according to the cover type information.(String), 14.如权利要求11所述的移动终端,还包括接收器,配置为从封面接收封面类型信息,其中,处理器还用于检查封面的封面类型信息,并根据封面类型信息定义第一区域和第二区域。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 15. The mobile terminal of claim 14, further comprising a memory configured to store the cover type information.(String), 15.如权利要求14所述的移动终端,还包括存储器,用于存储封面类型信息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 16. The mobile terminal of claim 14, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 16.如权利要求14所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 17. The mobile terminal of claim 11, wherein the window area of the cover is transparent or semi-transparent and the non-window area of the cover is opaque.(String), 17.如权利要求11所述的移动终端,其中盖板开窗区为透明或半透明,盖板非开窗区为不透明。(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 18. The mobile terminal of claim 11, wherein the processor is further configured to set different touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen.(String), 18.如权利要求11所述的移动终端,其中处理器还被配置为在触摸屏的第一区域和第二区域设置不同的触摸输入灵敏度以感测触摸输入。(String), 1(Integer), 17(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 19. The mobile terminal of claim 11, wherein the processor is further configured to set touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen according to whether the cover is closed over the touch screen.(String), 19.如权利要求11所述的移动终端,其中处理器还被配置为根据触摸屏上的盖子是否关闭来设置用于感测触摸屏的第一区域和第二区域中的触摸输入的触摸输入灵敏度。(String), 1(Integer), 18(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 20. The mobile terminal of claim 11, further comprising a battery packet disposed inside a rear surface of the mobile terminal,wherein the touch screen is formed on a front surface of the mobile terminal, andwherein the cover comprises:a battery cover unit provided on the rear surface of the mobile terminal, for protecting the battery packet; anda front cover unit connected to the battery cover unit, for covering the touch screen of the mobile terminal.(String), 20.如权利要求11所述的移动终端,还包括电池包设置在移动终端的后表面内,其中,触摸屏形成在移动终端的前表面上,并且其中,覆盖物包括:电池盖单元,设置在移动终端的背面,用于保护电池包;和前盖单元,与电池盖单元连接,用于盖住移动终端的触摸屏。(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 21. The mobile terminal of claim 11, wherein the cover comprises:a front cover unit configured to cover a front surface of the mobile terminal;a rear cover unit configured to cover a rear surface of the mobile terminal; anda connection unit configured to connect the front cover unit to the rear cover unit.(String), 21.如权利要求11所述的移动终端,其中封面包括:前盖单元,被配置为覆盖移动终端的前表面;后盖单元,被配置为覆盖移动终端的后表面;和连接单元被配置为将前盖单元连接到后盖单元。(String), 1(Integer), 20(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 22. The mobile terminal of claim 11, further comprising a magnetic force sensor configured to sense a change of an external magnetic force,wherein the processor is further configured to control the touch screen according to the change of the external magnetic force sensed by the magnetic force sensor.(String), 22.如权利要求11所述的移动终端,还包括磁力传感器,配置为感测外部磁力的变化,其中,处理器还用于根据磁力传感器感应到的外部磁力的变化控制触摸屏。(String), 1(Integer), 21(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 23. A mobile terminal comprising:a cover including a transparent or semi-transparent window area and an opaque non-window area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, for covering a touch screen of the mobile terminal;the touch screen including a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of a front cover unit of the cover; anda processor configured to:identify the first area of the touch screen corresponding to the window area of the cover of the mobile terminal and the second area of the touch screen corresponding to the non-window area of the cover by receiving information from the cover;control the touch screen to display a visual object on a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, wherein one of the visual object and another visual object are not displayed on a second area of the touch screen corresponding to a non-window area of the cover while the cover is closed over the touch screen,activate touch sensing for the second area of the touch screen while the cover is closed over the touch screen,control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the cover is closed over the touch screen.(String), 23.移动终端包括:覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域,覆盖物包括被配置为向移动终端应用多个有区别的键输入的键盘,用于覆盖移动终端的触摸屏;触摸屏包括对应于盖体的窗口区域的第一区域和对应于盖体的非窗口区域的第二区域,其中键盘包括雕刻或印刷在盖体的外表面上的多个区别键。封面的封面单元;和处理器配置为:通过接收外壳的信息识别移动终端外壳窗口区域对应的触摸屏第一区域和外壳非窗口区域对应的触摸屏第二区域;控制触摸屏在触摸屏的与移动终端的外壳的窗口区域对应的第一区域上显示视觉对象,其中在触摸的第二区域上不显示视觉对象和另一个视觉对象中的一个盖板关闭时对应于盖板非窗口区域的屏幕覆盖在触摸屏上,当盖子在触摸屏上关闭时,激活触摸屏第二区域的触摸感应,根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时盖子在触摸屏上方关闭。(String), 0(Integer), 22(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 24. The mobile terminal of claim 23, wherein the processor is further configured to receive cover type information from the cover.(String), 24.如权利要求23所述的移动终端,其中处理器还被配置为从封面接收封面类型信息。(String), 1(Integer), 23(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 25. The mobile terminal of claim 24, wherein the processor is further configured to check the cover type information and determine the first area and the second area of the touch screen according to the cover type information.(String), 25.如权利要求24所述的移动终端,其中处理器还用于检查覆盖物类型信息,并根据覆盖物类型信息确定触摸屏的第一区域和第二区域。(String), 1(Integer), 24(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 26. The mobile terminal of claim 24, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 26.如权利要求24所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 25(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 27. A cover for a mobile terminal, comprising:a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal; anda rear cover unit configured to cover a rear surface of the mobile terminal,wherein the front cover unit includes a transparent or semi-transparent window area and an opaque non-window area,a cover type information provider configured to provide cover type information to the mobile terminal, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover, andwherein the non-window area of the front cover unit includes an input area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of the front cover unit.(String), 27.一种移动终端的外壳,包括:前盖单元被配置为覆盖形成在移动终端的前表面上的触摸屏;和后盖单元,被配置为覆盖移动终端的后表面,其中,前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域,封面类型信息提供器,被配置为向移动终端提供封面类型信息,其中,封面类型信息包括关于封面的窗口区域的大小和位置中的至少一项的信息以及关于大小和位置中的至少一项的信息。盖子的非窗口区域的位置,以及其中,前盖单元的非窗口区域包括输入区域,输入区域包括配置为向移动终端应用多个不同的键输入的小键盘,并且当前盖单元覆盖移动终端的触摸屏时,通过非窗口区域的输入区域向触摸屏施加输入,其中键盘包括雕刻到或印刷在前盖单元的外表面上的多个有区别的键。(String), 0(Integer), 26(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 28. The cover of claim 27, wherein the front cover unit comprises a magnetic force applier configured to generate a magnetic force.(String), 28.权利要求27的覆盖物,其中前盖单元包括配置成产生磁力的磁力施加器。(String), 1(Integer), 27(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 29. The cover of claim 27, wherein the input applied through the non-window area is applied in a part of the non-window area visually distinguished from another part of the non-window area.(String), 29.权利要求27的覆盖物,其中通过非窗口区域施加的输入被施加在非窗口区域的一部分中,在视觉上与非窗口区域的另一部分区别开来。(String), 1(Integer), 28(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 30. The cover of claim 27, wherein at least a part of the non-window area is formed of at least one of conductive silicon, an anti-static electric material, and silver nylon.(String), 30.权利要求27的覆盖物,其中非窗口区域的至少一部分由导电硅、抗静电材料和银尼龙中的至少一种形成。(String), 1(Integer), 29(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184951(Integer), 31. An article of manufacture for processing input in a mobile terminal, comprising a non-transitory machine readable medium containing one or more programs which when executed implement the steps of:identify a first area of a touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;activating touch sensing for the second area of the touch screen while the cover is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are of a same gesture type, andwherein the first control command and the second control command are different control command.(String), 31.一种用于处理移动终端输入的制品,包括包含一个或多个程序的非暂时性机器可读介质,这些程序在执行时执行以下步骤:通过接收来自外壳的信息识别移动终端的外壳的窗口区域对应的触摸屏的第一区域和外壳的非窗口区域对应的触摸屏的第二区域;检测触摸屏上方的移动终端盖板是否合上;当盖子关闭在触摸屏上方时,激活触摸屏的第二区域的触摸感应;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 30(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111522(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184951(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to a Korean patent application filed in the Korean Intellectual Property Office on Feb. 11, 2014 and assigned Serial No. 10-2014-0015272, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal, and more particularly, to a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal. [0004]2. Description of the Related Art [0005]Mobile terminals such as, for example, smartphones, Personal Computers (PCs), tablets, and the like, provide various useful functions to users through many applications. [0006]Such mobile terminals are evolving to enable users to use various types of information through the various functions. [0007]In general, a cover is configured so as to cover an entire display formed on the front surface of a mobile terminal. Since the screen of the display is covered with the cover, a user may not use the display screen. SUMMARY OF THE INVENTION [0008]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal, which even though the mobile terminal is covered with the cover, enable a user to view at least a part of a display screen of the mobile terminal. [0009]Another aspect of the present invention is to provide a mobile terminal, a UI method in the mobile terminal, and a cover of the mobile terminal, which provide a window area to show a part of a display screen of the mobile terminal when the cover covers the display screen of the mobile terminal and which enable a user to identify an area of the display screen corresponding to the window area of the cover so that display on the area corresponding to the window area of the cover may be controlled in various manners. [0010]In accordance with an aspect of the present invention, a method is provided for processing input in a mobile terminal. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined. A second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area is detected while the cover is closed over the touch screen. The first input is processed as a first control command. [0011]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a touch screen and a processor. The processor is configured to define a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, to define a second area of the touch screen corresponding to a non-window area of the cover, to detect a first input in the second area while the cover is closed over the touch screen, and to process the first input as a first control command. [0012]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a cover including a transparent or semi-transparent window area and an opaque non-window area, for covering a touch screen of the mobile terminal. The mobile terminal also includes a touch screen that includes a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover. The mobile terminal further includes a processor configured to control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the touch screen is covered with the cover. [0013]In accordance with another aspect of the present invention, a cover for a mobile terminal is provided that includes a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal. The cover also includes a rear cover unit configured to cover a rear surface of the mobile terminal. The front cover unit includes a transparent or semi-transparent window area and an opaque non-window area. The non-window area of the front cover unit includes an input area. and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area. [0014]In accordance with another aspect of the present invention, an article of manufacture is provided for processing input in a mobile terminal. The article of manufacture includes a machine readable medium containing one or more programs which when executed implement the steps of: defining a first area of the touch screen corresponding to a window area of a cover of the mobile terminal; defining a second area of the touch screen corresponding to a non-window area of the cover; detecting a first input in the second area while the cover is closed over the touch screen; and processing the first input as a first control command. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0016]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention; [0017]FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention; [0018]FIG. 2B is a diagram illustrating a rear surface of a cover of a mobile terminal, according to an embodiment of the present invention; [0019]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention; [0020]FIGS. 4A and 4B are diagrams illustrating configurations of a front cover unit, according to embodiments of the present invention; [0021]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention; [0022]FIG. 6 is a diagram illustrating an operation for determining whether a mobile terminal is covered with a cover, according to an embodiment of the present invention; [0023]FIG. 7 is a block diagram of a mobile terminal, according to an embodiment of the present invention; [0024]FIG. 8 is a flowchart illustrating a UI operation using a first area and a second area defined on a touch screen, respectively corresponding to a window area and a cover input area of a cover, in a mobile terminal, according to an embodiment of the present invention; [0025]FIGS. 9, 10, 11, and 12 are diagrams illustrating touch screen areas defined for various types of covers, according to embodiments of the present invention; [0026]FIG. 13 is a diagram illustrating touch inputs, according to an embodiment of the present invention; [0027]FIG. 14 is a flowchart illustrating an operation for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0028]FIGS. 15A and 15B are diagrams illustrating screens for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0029]FIG. 16 is a flowchart illustrating an operation for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0030]FIG. 17 is a diagram illustrating a screen for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0031]FIG. 18 is a flowchart illustrating an operation for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0032]FIGS. 19A, 19B, 20A, and 20B are diagrams illustrating screens for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0033]FIG. 21 is a flowchart illustrating an operation for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0034]FIGS. 22A, 22B, 23A, and 23B are diagrams illustrating screens for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0035]FIGS. 24A, 24B, and 24C are diagrams illustrating a cover having a keypad formed on it according to another embodiment of the present invention; [0036]FIG. 25 is a diagram illustrating a keypad formed on a front cover unit, according to an embodiment of the present invention; [0037]FIGS. 26A, 26B, and 26C are diagrams illustrating keys formed on a front cover unit, according to an embodiment of the present invention; [0038]FIGS. 27A and 27B are diagrams illustrating a full screen and a mini screen respectively, according to an embodiment of the present invention; [0039]FIGS. 28A, 28B, 28C, 28D, and 28E are diagrams illustrating mini screens of 1st to 5th types, respectively, according to an embodiment of the present invention; [0040]FIGS. 29A, 29B, 29C, 29D, and 29E are diagrams illustrating mini screens of 6th to 10th types, according to an embodiment of the present invention; [0041]FIGS. 30A and 30B are diagrams illustrating mini screens of 11th and 12th types, according to an embodiment of the present invention; [0042]FIG. 31 is a diagram illustrating a mini screen of a 13th type, according to an embodiment of the present invention; [0043]FIGS. 32A and 32B are diagrams illustrating a method for controlling display of a mini screen, according to an embodiment of the present invention; [0044]FIGS. 33A, 33B, 33C, 34A, 34B, 34C, 34D, and 34E are diagrams illustrating operations triggered by text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0045]FIGS. 35A, 35B, 35C, 35D, and 35E are diagrams illustrating operations triggered by different types of text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0046]FIGS. 36A, 36B, 36C, 36D, and 36E are diagrams illustrating an operation for performing a call function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0047]FIGS. 37A, 37B, and 37C are diagrams illustrating an operation for performing a message function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0048]FIGS. 38A, 38B, 38C, 38D, 38E, 38F, and 38G are diagrams illustrating operations for performing various application functions, upon selection of applications on a mini screen while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0049]FIGS. 39A and 39B are diagrams illustrating an application requiring a text input, according to an embodiment of the present invention; and [0050]FIGS. 40A and 40B are diagrams illustrating a cover open request message displayed while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0051]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0052]The terms and words used in the following description are not limited to the meanings provided in a standard dictionary, but, are merely used to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the disclosure. [0053]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0054]Use of the term “substantially” means that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those of skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide. [0055]A mobile terminal according to various embodiments of the present invention may be embodied as an electronic device equipped with a display, such as, for example, a touch screen that can be covered with a cover. For example, the mobile terminal may be any of a video phone, a mobile phone, a smartphone, an International Mobile Telecommunication 2000 (IMT 2000) terminal, a Wideband Code Division Multiple Access (WCDMA) terminal, a Universal Mobile Telecommunication System (UMTS) terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a Digital Multimedia Broadcasting (DMB) terminal, an e-book reader, a laptop Personal Computer (PC), a tablet PC, a digital camera, and the like. [0056]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention. FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention. FIG. 2B is a diagram illustrating the rear surface of a cover of a mobile terminal, according to an embodiment of the present invention. [0057]Referring to FIGS. 1A, 1B, 2A, and 2B, a mobile terminal 100 may be engaged with a cover 200. A display device that displays screens for multiple functions, for example, a touch screen 140 is provided on a front surface of the mobile terminal 100. A bezel 102 is formed around at least a part of the periphery of the touch screen 140 on the front surface of the mobile terminal 100. A home button 105, a speaker, a camera, a sensor, and the like, may be formed in the bezel 102. A battery 170 is mounted on a rear surface of the mobile terminal 100 to supply power to the mobile terminal 100. The battery 170 may be detachably formed on the rear surface of the mobile terminal 100, or may be built in the mobile terminal 100 so that a user may not remove the battery 170 from the mobile terminal 100. A rear cover unit 220 is provided on the rear surface of the mobile terminal 100. Connection ports 180 are provided on the rear surface of the mobile terminal 100, inside the rear cover unit 220, for electrical connection. The rear cover unit 220 is able to be engaged with the rear surface of the mobile terminal 100, covering the battery 170. The cover 200 is configured to cover at least a part of the front surface of the mobile terminal 100. When the cover 200 covers the front surface of the mobile terminal 100, a front cover unit 210 covers at least a part of the touch screen 140. Further, when the cover 200 covers the front surface of the mobile terminal 100, the front cover unit 210 covers at least a part of the bezel 102. When the front cover unit 210 covers at least a part of the touch screen 140, the remaining part of the touch screen 140 is exposed outwardly through a window area 201a formed in the front cover unit 210. The mobile terminal 100 may control display of content such as, for example, a clock, text, a number, a caller number, a user environment setting, or the like, in the part of the touch screen 140 exposed through the window area 201a of the front cover unit 210. [0058]The front cover unit 210 of the cover 200 may be flipped open or closed. When the front cover unit 210 of the cover 200 is opened, the entire area of the touch screen 140 of the mobile terminal 100 is exposed outward, as illustrated in FIG. 1A. If the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 of the mobile terminal 100 is covered with the front cover unit 210, as illustrated in FIG. 1B. Referring to FIG. 1B, when the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 corresponding to the window area 201a is exposed outward, while the remaining part of the touch screen 140 is covered. [0059]Further, when the front cover unit 210 of the cover 200 is closed, a part (for example, a speaker) formed in the bezel 102 of the mobile terminal 100 is exposed outwardly through an opening 201b formed in the front cover unit 210. While only one opening 201b is shown in FIG. 1B, a plurality of openings may be formed in the front cover unit 210 so that even though the front cover unit 210 is closed, a plurality of parts (for example, a speaker, a camera, and the like) formed in the bezel 102 may be exposed outwardly through the plurality of openings. [0060]Referring to FIGS. 2A and 2B, the cover 200 includes the front cover unit 210 and the rear cover unit 220. The cover 200 further includes a connection unit 203 interposed between the front cover unit 210 and the rear cover unit 220, for connecting the front cover unit 210 to the rear cover unit 220. The connection unit 203 may cover a part of a side surface of the mobile terminal 100. [0061]The front cover unit 210 covers the front surface of the mobile terminal 100 and includes the window area, or screen projector, 201a to expose a part of the touch screen 140. The window area 201a may be formed of a transparent or semi-transparent material or may be formed into an opening in the front cover unit 210 so that when the cover 200 covers the front surface of the mobile terminal 100, a user may view information displayed on the touch screen 140 through the window area 201a. Accordingly, the user may view information displayed on the touch screen 140 inside the front cover unit 210 through the window area 201a from outside of the front cover unit 210. Therefore, even though the front cover unit 210 is closed, the user may view short information displayed on the touch screen 140 through the window area 201a and may enter a user command through the front cover unit 210 to execute a function related to the displayed information. The rear cover unit 220 is formed as a battery cover 220a in FIG. 2B, by way of example. Referring to FIG. 2B, the rear cover unit 220 covers the rear surface of the mobile terminal 100. The rear cover unit 220 may be mounted fixedly or detachably on the rear surface of the mobile terminal 100. The front cover unit 210 may be connected to a side surface of the rear cover unit 220. The connection unit 203 may be formed between the front cover unit 210 and the rear cover unit 220. In this case, the connection unit 203 may have one side surface connected to a side surface of the rear cover unit 220 and the other side surface connected to a side surface of the front cover unit 210. The rear cover unit 220 and the front cover unit 210 may be bent upon the connection unit 203. The rear cover unit 220 is engaged with the rear surface of the mobile terminal 100. When the front cover unit 210 is flipped closed, the rear cover unit 220 surrounds at least a part of a side surface of the mobile terminal 100. Thus, the mobile terminal 100 may not slip off from the cover 200. In addition, a connector unit 202a is formed in the rear cover unit 220. The connector unit 202a provides cover type information about the cover 200. The cover type information may include information about the position of a window area and an input area formed in the front cover unit 210 of the cover 200. The connector unit 202a may provide the cover type information about the cover 200 to the mobile terminal 100 by electrically connecting to the connection ports 180 formed on the rear surface of the mobile terminal 100. For example, a plurality of connection ports 181 and 182 may be formed on the rear surface of the mobile terminal 100. The connector unit 202a of the cover 200 may be electrically engaged with at least one of the connection ports 181 and 182. The mobile terminal 100 may identify the type of the cover 200 depending on whether the connector unit 202a of the cover 200 is connected to both or one of the connection ports 181 and 182. In another example, irrespective of which connection port the connector unit 202a of the cover 200 is connected to, the mobile terminal 100 may identify the type of the cover 200. [0062]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention. [0063]In FIG. 3, the rear cover unit 220 is formed as a rear case 220b. Referring to FIG. 3, the cover 200 includes the front cover unit 210, the connection unit 203, and the rear case 220b. The mobile terminal 100 may be fixedly inserted in the rear case 220b. The mobile terminal 100 with a battery cover 220a engaged with its rear surface may be inserted in the rear case 220b. [0064]The rear case 220b includes a base 221, at least one sidewall 222 formed along the periphery of the base 221, and a catching portion 223. The sidewall 222 is formed substantially straight up and perpendicular from the plane of the base 221. A bottom of the sidewall 220 is connected to the base 221 and the catching portion 223 is formed in an upper end of the sidewall 222. An inner space defined by the base 221 and the sidewall 222 has a size and a shape corresponding to the size and shape of the mobile terminal 100. If the mobile terminal 100 is accommodated in the inner space, the catching portion 223 may prevent slip-off of the mobile terminal 100 from the inner space. The front cover unit 210 is connected to one side surface of the rear case 220b. The connection unit 203 may be formed between the front cover unit 210 and the rear case 220b. In this case, the connection unit 203 has one side surface connected to a side surface of the rear case 220b and the other side surface connected to a side surface of the front cover unit 210. The rear case 220b and the front cover unit 210 may be bent upon the connection unit 203. [0065]If the window area 201a and the input area 201b are formed at predetermined positions on the front cover unit 210 of the cover 200, when the cover 200 is closed, the mobile terminal 100 may display information through the window area 201a and receive a user input through the input area 201b despite having no knowledge of cover type information about the cover 200. [0066]In an embodiment of the present invention, a cover type information transmitter 224 may further be formed in the cover 200 for providing cover type information about the cover 200 to the mobile terminal 100 via short-range communication. The cover type information transmitter 224 may transmit the cover type information about the cover 200 to the mobile terminal 100 by a short-range communication scheme such as, for example, Near Field Communication (NFC), Radio Frequency Identification (RFID), Bluetooth, Wireless Fidelity (WiFi) Direct, or the like. The mobile terminal 100 may then identify the type of the cover 200 based on the cover type information received from the cover 100 by the short-range communication scheme. [0067]While it has been described above, with reference to FIG. 3, that the rear cover unit 220 of the cover 200 is configured as a case, the shapes of the rear cover unit 220 and the connection unit 203 may be changed as long as the front cover unit 210 is detachably mounted to the mobile terminal 100 and flipped open or closed. [0068]FIGS. 4A and 4B are diagrams illustrating configurations of the front cover unit, according to embodiments of the present invention. FIG. 4A illustrates the window area 201a formed of a transparent or semi-transparent material in the front cover unit 210, and FIG. 4B illustrates the window area 201a formed into a cutout opening in the front cover unit 210. [0069]Referring to FIG. 4A, the front cover unit 210 includes an outer member 211a, an inner member 212a, and a transparent member 213a. The outer member 211a, which forms an outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. An outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms an inner surface of the front cover unit 210, is engaged with a bottom surface of the transparent member 213a, while a bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. An inner hole 2121 is formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The transparent member 213a is interposed between the outer member 211a and the inner member 212a and brings the outer hole 2111 and the inner hole 212 into close contact. A first area defined at a predetermined position of the touch screen 140, for example, in an upper part of the touch screen 140 may be exposed outwardly through the transparent member 213a, the outer hole 2111, and the inner hole 2121. That is, even though the first area of the touch screen 140 is covered with the front cover unit 210, the transparent member 213a may be formed of a material containing a transparent or semi-transparent material so that the user may view information displayed in the first area of the touch screen 140 through the window area 201a. For example, the transparent member 213a may be formed of a transparent or semi-transparent film. The transparent member 213a is larger is size than the window area 201a. In FIG. 4A, the transparent member 213a is as large as the outer member 211a and the inner member 212a. The transparent member 213a may be formed of a material containing a conductive material such as, for example, conductive silicon. Further, the outer member 211a, the inner member 212a, and the transparent member 213a may be formed of a material containing at least one of an anti-static electricity material, silver, and nylon fabric. Accordingly, upon receipt of a touch input in the window area 201a from the user, the touch input may be sensed in the first area of the touch screen 140 corresponding to the window area 201a. For example, when a call is incoming, a notification indicating the call incoming is displayed at a position of the touch screen 140 corresponding to the window area 201a. If the user touches the window area 201a or manipulates a predetermined key, for example, a side key, the call may be connected immediately. [0070]Referring to FIG. 4B, the front cover unit 210 includes the outer member 211a and the inner member 212a to define the window area 201a and cover the touch screen 140, for protection. The outer member 211a, which forms the outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. The outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms the inner surface of the front cover unit 210, is engaged with a bottom surface of the outer member 211a, while the bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. The inner hole 2121 may be formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The outer hole 2111 and the inner hole 2121 are formed having the same size. An opening formed by the outer hole 2111 and the inner hole 2121 may form the window area 201a. Therefore, even though the first area of the touch screen 140 is covered with the front cover unit 210, the user may view information displayed on the touch screen 140 through the opening of the window area 201a. Further, the user may apply a touch input to the touch screen 140 through the window area 201a. Then the mobile terminal 100 may sense the touch input in the first area of the touch screen 140 corresponding to the window area 201a. [0071]In an embodiment of the present invention, the remaining area of the front cover unit 210, except the window area 201a, is a non-window area. At least a part of the non-window area may be defined as an input area (hereinafter, referred to as a ‘cover input area’) in which a user input may be applied. For example, the whole non-window area may be the cover input area. Or a predetermined part of the non-window area may be the cover input area. The cover input area may refer to an area in which a touch input on the outer surface of the outer member 211a can be detected by the touch screen 140, with the front cover unit 210 covering the touch screen 140. Therefore, a user gesture made in the cover input area corresponding to at least a part of the non-window area may be sensed by the touch screen 140. [0072]For example, when the user makes a user gesture in the cover input area of the front cover unit 210, the user gesture may be sensed in a second area of the touch screen 140 corresponding to the cover input area. In various embodiments of the present invention, the window area 201a of the front cover unit 210 may be formed in a first cover area of the front cover unit 210 and the non-window area may be formed in a second cover area other than the first cover area in the front cover unit 210. [0073]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention. [0074]Referring to FIG. 5A, a window area 511 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 511, is defined as a non-window area 521 in a first-type cover, according to an embodiment of the present invention. The whole non-window area 521 may be a cover input area in the first-type cover. [0075]Referring to FIG. 5B, a window area 512 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 512, is defined as the non-window area 521 in a second-type cover, according to an embodiment of the present invention. In the second-type cover, an area of a predetermined size in the non-window area 521 under the window area 512 may be defined as a cover input area 522. In FIG. 5B, the cover input area 522 may be substantially as wide as the window area 512 along a horizontal direction and may extend up to the vicinity of the window area 512 and down to the vicinity of a bottom end of the front cover unit 210. Accordingly, for example, the cover input area 522 may occupy most of the non-window area 521 under the window area 512. [0076]Referring to FIG. 5C, a window area 513 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 513, is defined as the non-window area 521 in a third-type cover, according to an embodiment the present invention. In the third-type cover, a small area at a center of the non-(String), 优先 [0001] 本申请根据 35 U.S.C. § 119(a) 于 2014 年 2 月 11 日向韩国知识产权局提交并转让序列号 10-2014-0015272 的韩国专利申请,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及一种移动终端,更具体地,涉及一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳。 [0004] 2.相关技术的描述 [0005] 诸如智能手机、个人计算机(PC)、平板电脑等的移动终端通过许多应用程序向用户提供各种有用的功能。 [0006] 这样的移动终端正在发展以使用户能够通过各种功能使用各种类型的信息。 [0007] 通常,盖被配置为覆盖形成在移动终端的前表面上的整个显示器。 由于显示器的屏幕被覆盖物覆盖,用户可能不使用显示屏幕。 发明内容 [0008] 做出本发明以至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面提供了一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳,即使移动终端被外壳覆盖,也使得用户能够查看 移动终端的显示屏的至少一部分。 [0009] 本发明的另一方面在于提供一种移动终端、移动终端中的UI方法以及移动终端的封面,当封面覆盖时,提供窗口区域以显示移动终端的显示屏幕的一部分。 移动终端的显示屏,使用户能够识别与封面的窗口区域对应的显示屏的区域,从而可以以各种方式控制在与封面的窗口区域对应的区域上的显示。 [0010] 根据本发明的一个方面,提供了一种用于在移动终端中处理输入的方法。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域。 定义了移动终端的触摸屏上与封面的非窗口区域对应的第二区域。 当盖子在触摸屏上关闭时,检测到第二区域中的第一输入。 第一输入被处理为第一控制命令。 [0011] 根据本发明的另一方面,提供了一种包括触摸屏和处理器的移动终端。 处理器用于定义触摸屏的第一区域对应于移动终端的封面的窗口区域, 定义触摸屏的第二区域对应于封面的非窗口区域, 检测第一 合上触摸屏时在第二区域输入,并将第一输入处理为第一控制命令。 [0012] 根据本发明的另一方面,提供了一种移动终端,其包括用于覆盖移动终端的触摸屏的覆盖物,该覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域。 该移动终端还包括触摸屏,该触摸屏包括与封面的窗口区域对应的第一区域和与封面的非窗口区域对应的第二区域。 移动终端还包括处理器,被配置为根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时触摸屏被覆盖物覆盖。 [0013]根据本发明的另一方面,提供了一种用于移动终端的盖,其包括被配置为覆盖形成在移动终端的前表面上的触摸屏的前盖单元。 盖还包括被配置为覆盖移动终端的后表面的后盖单元。 前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域。 前盖单元的非窗口区域包括输入区域。 在前盖单元覆盖移动终端的触摸屏的同时,通过非窗口区域的输入区域对触摸屏进行输入。 [0014] 根据本发明的另一方面,提供了一种用于处理移动终端中的输入的制品。 所述制品包括包含一个或多个程序的机器可读介质,所述程序在执行时实现以下步骤: 定义与移动终端的封面的窗口区域相对应的触摸屏的第一区域; 定义触摸屏的第二区域,对应于盖板的非窗口区域; 当盖板合上触摸屏时,检测第二区域中的第一输入; 处理第一输入作为第一控制命令。 附图的简要说明 [0015] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0016] 图 附图说明图1A和图1B是示出了根据本发明实施例的与盖子接合的移动终端的外部透视图; [0017] 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图; [0018] 如图。 图2B是示出根据本发明实施例的移动终端机盖的背面的图; [0019] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图; [0020] 图 图4A和4B是示出根据本发明实施例的前盖单元的构造的图; [0021] 图 图5A、5B、5C和5D是示出根据本发明实施例的各种类型的盖的图; [0022] 如图。 图6是说明根据本发明的一个实施例的确定移动终端是否被覆盖物覆盖的操作的图。 [0023] 如图。 图7是根据本发明实施例的移动终端的框图; [0024] 如图。 图8是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的分别对应于封面的窗口区域和封面输入区域的第一区域和第二区域的UI操作的流程图 ; [0025] 图 图9、10、11和12是示出根据本发明实施例的为各种类型的封面定义的触摸屏区域的图; [0026] 如图。 图13是说明根据本发明的实施例的触摸输入的图; [0027] 如图。 图14是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制音乐播放信息的操作的流程图; [0028] 图 图15A和15B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制音乐播放信息的屏幕的图; [0029] 如图。 图16是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的操作的流程图; [0030] 如图。 图17是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的屏幕的图; [0031]如图。 图18是示出根据本发明实施例的使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的操作的流程图; [0032] 图 图19A、19B、20A和20B是示出了根据本发明的实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的屏幕的图; [0033] 如图。 图21是示出根据本发明的实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制应用程序的操作的流程图; [0034] 图 图22A、22B、23A和23B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制应用的屏幕的图; [0035] 图 图24A、24B和24C是示出根据本发明另一实施例的具有形成在其上的小键盘的盖的图; [0036] 如图。 图25是示出根据本发明实施例的形成在前盖单元上的小键盘的图; [0037] 图 图26A、26B和26C是图示根据本发明实施例的形成在前盖单元上的键的图; [0038] 图 图27A和27B是分别示出了根据本发明实施例的全屏和小屏幕的图; [0039] 图 图28A、28B、28C、28D和28E是图解1的迷你屏幕的图。 st 到 5 th 分别根据本发明的一个实施例的类型; [0040] 图 图29A、29B、29C、29D和29E是图解说明6的迷你屏幕的图 th 到 10 th 类型,根据本发明的一个实施例; [0041] 图 图30A和30B是图解说明11的迷你屏幕的图 th 和 12 th 类型,根据本发明的一个实施例; [0042] 如图。 图31是说明13的小屏幕的图 th 类型,根据本发明的一个实施例; [0043] 图 图32A和32B是图示根据本发明实施例的用于控制迷你屏幕的显示的方法的图; [0044] 图 图33A、33B、33C、34A、34B、34C、34D和34E是示出根据本发明实施例的通过移动终端中的封面单元的小键盘由文本输入触发的操作的图; [0045] 图 图35A、35B、35C、35D和35E是图示根据本发明实施例的通过移动终端中的封面单元的键盘的不同类型的文本输入触发的操作的图; [0046] 图 图36A、36B、36C、36D和36E是示出在移动终端中在前盖单元关闭的同时通过前盖单元的小屏幕或键盘接收输入时执行呼叫功能的操作的图 ,根据本发明的一个实施例; [0047] 图 图37A、图37B和图37C是示出在移动终端中前盖单元关闭时,在通过前盖单元的小屏幕或键盘接收输入时执行消息功能的操作的图。 本发明的实施例; [0048] 图 图38A、图38B、图38C、图38D、​​图38E、图38F和图38G是示出根据本发明实施例的在移动终端中在前盖单元关闭的同时在迷你屏幕上选择应用时执行各种应用功能的操作的图。 本发明; [0049] 图 图39A和39B是图示根据本发明实施例的需要文本输入的应用程序的图; 和 [0050] 图 图40A和40B是示出根据本发明实施例的在移动终端中前盖单元关闭时显示的盖打开请求消息的图。 本发明实施方案的详细说明 [0051]下面结合附图对本发明实施例进行详细描述。 尽管它们在不同的附图中示出,但是相同或相似的部件可以用相同或相似的附图标记表示。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0052] 以下描述中使用的术语和词语不限于标准字典中提供的含义,而仅用于使本公开内容能够清晰一致地理解。 因此,本领域技术人员应该清楚,提供本发明实施例的以下描述仅用于说明目的,而不是用于限制本公开的目的。 [0053] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0054] 使用术语“基本上”是指不需要精确地实现所列举的特性、参数或值,而是偏差或变化,包括例如公差、测量误差、测量精度限制和本领域技术人员已知的其他因素。 该技术可能以不排除该特性旨在提供的效果的数量出现。 [0055] 根据本发明的各种实施例的移动终端可以被实施为配备有显示器的电子设备,例如,可以用盖子覆盖的触摸屏。 例如,移动终端可以是可视电话、移动电话、智能手机、国际移动电信2000(IMT 2000)终端、宽带码分多址(WCDMA)终端、通用移动电信系统(UMTS)中的任何一种。 ) 终端、个人数字助理 (PDA)、便携式多媒体播放器 (PMP)、数字多媒体广播 (DMB) 终端、电子书阅读器、膝上型个人电脑 (PC)、平板电脑、数码相机、 之类的。 [0056] 图 图1A和1B是示出根据本发明实施例的与盖接合的移动终端的外部透视图的图。 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图。 如图。 图2B是图示根据本发明实施例的移动终端的盖的后表面的图。 [0057] 参考图。 参考图1A、1B、2A和2B,移动终端 100 可能与盖子接合 200 . 显示多种功能的屏幕的显示设备,例如触摸屏 140 设置在移动终端的正面 100 . 一个挡板 102 围绕触摸屏的外围的至少一部分形成 140 在移动终端的正面 100 . 一个主页按钮 105 、扬声器、照相机、传感器等可以形成在边框中 102 . 一块电池 170 安装在移动终端的背面 100 给移动终端供电 100 . 电池 170 可以可拆卸地形成在移动终端的背面 100 ,或者可以内置在移动端 100 以免用户取出电池 170 从移动终端 100 . 后盖单元 220 设置在移动终端的背面 100 . 连接端口 180 设置在移动终端的背面 100 , 后盖单元内部 220 , 用于电气连接。 后盖单元 220 能够与移动终端的背面接合 100 , 覆盖电池 170 . 封面 200 被配置为覆盖移动终端的前表面的至少一部分 100 . 当封面 200 覆盖移动终端的正面 100 , 一个前盖单元 210 至少覆盖触摸屏的一部分 140 . 此外,当封面 200覆盖移动终端的正面 100 , 前盖单元 210 至少覆盖挡板的一部分 102 . 当前盖单元 210 至少覆盖触摸屏的一部分 140 ,触摸屏的剩余部分 140 通过窗口区域向外暴露 201 a 形成在前盖单元中 210 . 移动终端 100 可以控制内容的显示,例如时钟、文本、数字、呼叫者号码、用户环境设置等,在触摸屏的部分中 140 通过窗口区域暴露 201 a 前盖单元的 210 . [0058] 前盖单元 210 封面的 200 可以翻转打开或关闭。 当前盖单元 210 封面的 200 打开时,触摸屏的整个区域 140 移动终端的 100 外露,如图所示。 1A。 如果前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 移动终端的 100 被前盖单元盖住 210 ,如图所示。 1B。 参考图。 1B、当前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 对应窗口区域 201 a 外露,而触摸屏的其余部分 140 被覆盖。 [0059] 此外,当前盖单元 210 封面的 200 封闭,形成在边框中的一部分(例如,扬声器) 102 移动终端的 100 通过开口向外暴露 201 b 形成在前盖单元中 210 . 虽然只有一个开口 201 b 如图所示。 如图1B所示,可以在前盖单元中形成多个开口 210 这样即使前盖单元 210 封闭,在边框中形成多个部件(例如,扬声器、相机等) 102 可以通过多个开口向外暴露。 [0060] 参考图。 2A和2B,盖 200 包括前盖单元 210 和后盖单元 220 . 封面 200 还包括连接单元 203 夹在前盖单元之间 210 和后盖单元 220 , 用于连接前盖单元 210 到后盖单元 220 . 连接单元 203 可以覆盖移动终端侧面的一部分 100 . [0061] 前盖单元 210 覆盖移动终端的正面 100 并包括窗口区域或屏幕投影仪, 201 a 露出触摸屏的一部分 140 . 窗口区域 201 a 可以由透明或半透明材料形成,或者可以形成在前盖单元中的开口中 210 这样当封面 200 覆盖移动终端的正面 100 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域 201 a . 因此,用户可以查看显示在触摸屏上的信息 140 前盖单元内部 210 通过窗口区域 201 a 从前盖单元外部 210 . 因此,即使前盖单元 210 关闭时,用户可以查看触摸屏上显示的简短信息 140 通过窗口区域 201 a 并且可以通过前盖单元输入用户命令 210 执行与显示信息相关的功能。 后盖单元 220 形成为电池盖 220 a 在图 例如,图2B。 参考图。 2B、后盖单元 220 覆盖移动终端的背面 100 . 后盖单元 220 可以固定或可拆卸地安装在移动终端的背面 100 . 前盖单元 210 可以连接到后盖单元的侧表面220 . 连接单元 203 可以形成在前盖单元之间 210 和后盖单元 220 . 在这种情况下,连接单元 203 可以具有连接到后盖单元的侧表面的一个侧表面 220 另一个侧面连接到前盖单元的侧面 210 . 后盖单元 220 和前盖单元 210 可能弯曲在连接单元上 203 . 后盖单元 220 与移动终端的背面接合 100 . 当前盖单元 210 翻转关闭,后盖单元 220 包围移动终端的侧表面的至少一部分 100 . 因此,移动终端 100 不能从封面上滑落 200 . 此外,连接器单元 202 a 形成在后盖单元中 220 . 连接器单元 202 a 提供有关封面的封面类型信息 200 . 封面类型信息可以包括关于形成在前封面单元中的窗口区域和输入区域的位置的信息 210 封面的 200 . 连接器单元 202 a 可以提供关于封面的封面类型信息 200 到移动终端 100 通过电连接到连接端口 180 形成在移动终端的背面 100 . 例如,多个连接端口 181 和 182 可以形成在移动终端的背面 100 . 连接器单元 202 a 封面的 200 可以与至少一个连接端口电接合 181 和 182 . 移动终端 100 可以识别封面的类型 200 取决于连接器单元是否 202 a 封面的 200 连接到两个或一个连接端口 181 和 182 . 在另一个示例中,无论连接器单元是哪个连接端口 202 a 封面的 200 连接到移动终端 100 可以识别封面的类型 200 . [0062] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图。 [0063] 在图。 3、后盖单元 220 形成为后壳 220 b . 参考图。 3、封面 200 包括前盖单元 210 , 连接单元 203 , 和后壳 220 b . 移动终端 100 可固定插入后壳 220 b . 移动终端 100 带电池盖 220 a 与其后表面啮合可以插入后壳 220 b. [0064] 后壳 220 b 包括一个基地 221 , 至少一个侧壁 222 沿底座周边形成 221 , 和一个捕捉部分 223 . 侧壁 222 形成为基本上笔直向上并垂直于基部的平面 221 . 侧壁的底部 220 连接到底座 221 和捕捉部分 223 形成于侧壁的上端 222 . 由底座定义的内部空间 221 和侧壁 222 具有与移动终端的大小和形状相对应的大小和形状 100 . 如果移动端 100 容纳在内部空间中的抓持部分 223 可防止移动终端滑落 100 从内部空间。 前盖单元 210 连接到后壳的一侧表面 220 b . 连接单元 203 可以形成在前盖单元之间 210 和后壳 220 b . 在这种情况下,连接单元 203 具有连接到后壳的侧面的一个侧面 220 b 另一个侧面连接到前盖单元的侧面 210 . 后壳 220 b 和前盖单元 210 可能弯曲在连接单元上 203 . [0065] 如果窗口区域 201 a 和输入区域 201 b 形成在前盖单元上的预定位置 210 封面的 200 , 当覆盖 200 关闭,移动端 100 可以通过窗口区域显示信息 201 a 并通过输入区域接收用户输入 201 b 尽管不知道关于封面的封面类型信息 200 . [0066] 在本发明的一个实施例中,一种覆盖式信息发送器 224 可以进一步形成在盖中 200 用于提供有关封面的封面类型信息 200 到移动终端 100 通过短距离通信。 盖式信息发射器 224 可以传输关于封面的封面类型信息 200 到移动终端 100 通过短距离通信方案,例如近场通信(NFC)、射频识别(RFID)、蓝牙、无线保真(WiFi) Direct等。 移动终端 100 然后可以识别封面的类型 200 基于从封面收到的封面类型信息 100 通过短距离通信方案。 [0067] 虽然上面已经描述了,但参考图1。 3、即后盖单元 220 封面的 200 配置为外壳,后盖单元的形状 220 和连接单元 203 只要前盖单元可以更改 210 可拆卸地安装在移动终端上 100 并翻转打开或关闭。 [0068] 图 图4A和4B是图示根据本发明实施例的前盖单元的配置的图。 如图。 图4A说明了窗口区域 201 a 在前盖单元中由透明或半透明材料制成 210 ,和图。 图4B图示了窗口区域 201 a 在前盖单元中形成一个切口 210 . [0069] 参考图。 4A、前盖单元 210 包括一个外部成员 211 a , 一个内部成员 212 a , 和一个透明的成员 213 a . 外部成员 211 a ,其形成前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 一个外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,其形成前盖单元的内表面 210 ,与透明构件的底面接合 213 a ,而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 一个内孔 2121 形成在内构件的位置 212 a 对应外孔 2111 , 定义窗口区域 201 a . 透明成员 213 a 夹在外构件之间 211 a 和内部成员 212 a 并带来外孔 2111 和内孔 212 密切接触。 第一区域定义在触摸屏的预定位置 140 ,例如,在触摸屏的上部 140 可以通过透明构件向外暴露 213 a , 外孔 2111 , 和内孔 2121 . 也就是说,即使触摸屏的第一个区域 140被前盖单元盖住 210 , 透明构件 213 a 可以由包含透明或半透明材料的材料形成,以便用户可以查看显示在触摸屏的第一区域中的信息 140 通过窗口区域 201 a . 例如,透明构件 213 a 可以由透明或半透明膜形成。 透明成员 213 a 大于窗口区域的大小 201 a . 在图。 4A、透明件 213 a 与外部成员一样大 211 a 和内部成员 212 a . 透明成员 213 a 可以由包含导电材料的材料形成,例如导电硅。 此外,外部构件 211 a , 内部成员 212 a , 和透明构件 213 a 可以由包含抗静电材料、银和尼龙织物中的至少一种的材料形成。 因此,当在窗口区域中接收到触摸输入时 201 a 来自用户的触摸输入可以在触摸屏的第一区域中被感测到 140 对应窗口区域 201 a . 例如,当有来电时,在触摸屏的位置显示来电的通知 140 对应窗口区域 201 a . 如果用户触摸窗口区域 201 a 或者操作预定键,例如侧键,可以立即接通通话。 [0070] 参考图。 4B、前盖单元 210 包括外部成员 211 a 和内部成员 212 a 定义窗口区域 201 a 并覆盖触摸屏 140 ,为了保护。 外部成员 211 a ,它形成了前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,它形成前盖单元的内表面 210 ,与外构件的底面接合 211 a , 而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 内孔 2121 可以形成在内部构件的位置处 212 a 对应外孔 2111 , 定义窗口区域 201 a . 外孔 2111 和内孔 2121 形成具有相同的尺寸。 由外孔形成的开口 2111 和内孔 2121 可以形成窗口区域 201 a . 因此,即使触摸屏的第一区域 140 被前盖单元盖住 210 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域的开口 201 a . 此外,用户可以将触摸输入应用到触摸屏 140 通过窗口区域 201 a . 然后是移动端 100 可以感应触摸屏第一区域的触摸输入 140 对应窗口区域 201 a. [0071] 在本发明的一个实施例中,前盖单元的剩余区域 210 , 除了窗口区域 201 a, 是非窗口区域。 非窗口区域的至少一部分可以被定义为可以应用用户输入的输入区域(以下称为“覆盖输入区域”)。 例如,整个非窗口区域可以是封面输入区域。 或者,非窗口区域的预定部分可以是封面输入区域。 覆盖输入区域可以是指在外部构件的外表面上进行触摸输入的区域 211 a 可通过触摸屏检测 140 , 带前盖单元 210 覆盖触摸屏 140 . 因此,在对应于至少部分非窗口区域的覆盖输入区域中做出的用户手势可以被触摸屏感测到 140 . [0072] 例如,当用户在封面单元的封面输入区域中做出用户手势时 210 ,可以在触摸屏的第二区域中感测到用户手势 140 对应于封面输入区域。 在本发明的各个实施例中,窗口区域 201 a 前盖单元的 210 可以形成在前盖单元的第一盖区域中 210 并且非窗口区域可以形成在前盖单元中除第一覆盖区域之外的第二覆盖区域中 210 . [0073] 图 图5A、5B、5C和5D是图示根据本发明实施例的各种类型的盖的图。 [0074] 参考图。 5A、窗口区域 511 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 511 , 定义为非窗口区域 521 在根据本发明的一个实施例的第一种盖子中。 整个非窗口区域 521 可以是第一类封面中的封面输入区域。 [0075] 参考图。 5B、窗口区域 512 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 512 , 定义为非窗口区域 521 在根据本发明的一个实施例的第二种盖中。 在第二种盖板中,非窗区域中的预定大小的区域 521 窗下区域 512 可以定义为一个覆盖输入区域 522 . 在图。 5B、覆盖输入区域 522 可以基本上与窗口区域一样宽 512 沿水平方向并可能延伸到窗口区域附近 512 并向下至前盖单元的底端附近 210 . 因此,例如,封面输入区域 522 可能占据大部分非窗口区域 521 窗下区域 512 . [0076] 参考图。 5C、窗口区域 513 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 513 , 定义为非窗口区域 521 在根据本发明的一个实施例的第三种盖子中。 第三种封面中,非窗口区域中心的一小块区域 521 窗下区域 513 可以定义为一个覆盖输入区域 523 . 封面输入区 523 在第三类覆盖中小于覆盖输入区域 522 以第二类封面为例。 [0077] 参考图。 5D,一个窗口区域 514 在前盖单元的右侧部分拉长 210 沿前盖单元的长度方向 210 ,以及前盖单元的剩余区域 210 , 除了窗口区域 514 , 定义为非窗口区域 521 在根据本发明的实施例的第四类盖中。 封面输入区 524 在非窗口区域的一部分定义 521 在窗口区域的左侧 514 . [0078] 而单个窗口区域 511 , 512 , 513 , 和 514 形成在前盖单元中 210在图 参照图5A、5B、5C和5D,作为示例,可以改变窗口区域的位置或数量。 例如,窗口区域 511 , 512 , 513 , 和 514 可以设置在前盖单元的中心 210 或者可以沿水平方向拉长。 因此窗口区域的位置 511 , 512 , 513 , 和 514 可能会有所不同。 虽然已经描述了在前盖单元中定义了一个窗口区域 210 在本发明的实施例中,可以在前盖单元中定义多个窗口区域 210 ,根据本发明的各种实施例。 此外,至少一部分非窗口区域 521 可用作覆盖输入区域。 例如,整个或部分非窗口区域 521 可以定义为覆盖输入区域。 在覆盖输入区域中进行的用户手势(例如,触摸输入)的输入时,可以在触摸屏的第二区域中检测到用户手势 140 对应于封面输入区域。 [0079] 移动终端 100 可以将窗口区域与封面单元中的封面输入区域区分开来 210 ,根据上述各种类型的封面。 因此,移动端 100 可以定义触摸屏上的第一和第二区域 140 对应前盖单元的窗口区域和封面输入区域 210 , 分别。 [0080] 在本发明的各个实施例中,前盖单元 210 移动终端的 100 可能会覆盖触摸屏 140 在移动终端的正面 100 和移动终端 100 可判断是否触摸屏 140 已被前盖单元盖住 210 . [0081] 如图。 图6是示出根据本发明实施例的用于确定移动终端是否被覆盖物覆盖的操作的图。 [0082] 参考图。 6、封面 200 包括一个磁力施加器 691 , 在前盖单元的内部 210 ,提供有关封面的封面类型信息 200 . [0083] 磁力施加器 691 例如,可以是永磁体并且可以施加磁力。 磁力施加器 691 可以产生对应于封面类型信息的磁力。 [0084] 例如,如果前盖单元 210 覆盖移动终端的正面 100 , 一个传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 , 和移动终端 100 可确定前盖单元是否 210 已经覆盖了移动终端的正面 100 基于磁力传感器的传感结果 692 传感器单元 160 . 此外,当前盖单元 210 覆盖移动终端的正面 100 , 传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 对应封面类型信息,移动端 100 可以确定封面的封面类型信息 200 基于磁力传感器的传感结果 692 传感器单元 160 . [0085] 在本发明的一个实施例中,触摸屏 140 移动终端的 100 可以独立显示屏幕并感知触摸。 移动终端 100 可以激活触摸屏的显示屏 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . 或者手机端 100 可以激活触摸屏的触摸感应区域 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . [0086] 例如,如果前盖单元 210 没有覆盖触摸屏 140 , 移动端 100 可以激活触摸屏的全屏显示 140 以及触摸屏的全触摸感应区域。 [0087] 另一方面,如果前盖单元 210 已经覆盖了触摸屏 140 , 移动端 100 可以在触摸屏的显示屏上激活第一区域的信息显示和触摸感应,仅对第二区域进行触摸感应 140 . 在这种情况下,可以在触摸屏的显示屏幕中停用除第一和第二区域之外的剩余区域 140 . [0088] 移动终端 100 可以从封面类型信息提供者那里接收封面类型信息 710 封面的 200 . 封面类型信息提供者 710 可能是连接器单元之一 202 a ,盖式信息发射器 224 , 和磁力施加器 691 . [0089] 如图。 图7是移动终端的框图 100 ,根据本发明的一个实施例。 [0090] 参考图。 7、移动端 100 包括一个控制器 110 , 一个通讯单元 120 , 一段记忆 130 , 触摸屏 140 , 和一个输入/输出 (I/O) 单元 150 . [0091] 控制器 110 包括一个中央处理器 (CPU) 111 . 控制器 110 可以包括数字信号处理器(DSP)并且可以被称为处理器。 控制器 110 包括一个只读存储器 (ROM) 112 用于存储控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 用于存储从移动终端外部接收的信号或数据 100 或用作移动终端执行操作的内存空间 100 . 中央处理器 111 可以包括一个或多个核心。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线互连。 控制器 110 可以控制通信单元 120 , 记忆 130 , 触摸屏 140 , 和 I/O 单元 150 . 例如,控制器 110 可为移动终端提供整体控制 100 并且可以控制上述组件之间的信号流。 [0092] 控制器 110 可以区分前盖单元中的窗口区域和封面输入区域 210 封面的 200 根据封面的类型 200 . 因此,控制器 110 可以在触摸屏上定义第一和第二区域 140 ,对应前盖单元的窗口区域和封面输入区域 210 . [0093] 当前盖单元 210 关闭,从而覆盖触摸屏 140 , 控制器 110 可以激活触摸屏的第一和第二区域 140 , 同时停用触摸屏的剩余区域 140 . 因此,控制器 110 可以检测到触摸屏的第一和第二区域的用户手势输入 140 通过前盖单元 210 . [0094] 控制器 110 可以控制触摸屏不同区域的不同触摸输入灵敏度的设置 140 . 例如,控制器 110 可以在触摸屏的第二区域设置更大的触摸输入灵敏度 140 比在触摸屏的第一个区域 140 . 例如,如果前盖单元 210 关闭,控制器 110 可以将触摸屏的第二区域的触摸输入灵敏度设置为大于第一区域的触摸输入灵敏度 140 . 触摸屏第一区和第二区的触摸输入灵敏度 140 可以设置为足够大以容纳触摸屏 140 检测在前盖单元上做出的用户手势 210 , 即使前盖单元 210 覆盖触摸屏 140 . [0095] 此外,控制器 110可以控制设置不同的触摸输入灵敏度,以根据前盖单元是否在触摸屏的第一和第二区域中感测触摸输入 210 覆盖触摸屏 140 . 例如,如果封面 200 不覆盖触摸屏 140 , 控制器 110 可以控制整个触摸屏上相同的触摸输入灵敏度的设置 140 . 另一方面,如果前盖单元 210 覆盖触摸屏 140 , 控制器 110 可以控制在第二区域中设置比在第一区域中更高的触摸输入灵敏度。 因此,即使当窗口区域比非窗口区域厚或窗口区域在非窗口区域关闭时打开,也可以正常感测到第二区域的触摸输入。 控制器 110 可以识别封面的类型 200 并判断前盖单元是否 210 覆盖触摸屏的显示屏 140 通过传感器单元接收封面类型信息 160 , 连接端口 180 ,或封面类型信息接收器 190 . 控制器 110 可以定义区域,例如包括对应于前盖单元的窗口区域的第一区域 210 第二区域对应于前盖单元的盖输入区域 210 , 在触摸屏上 140 根据封面类型。 例如,虽然封面 200 前盖单元的 210 覆盖触摸屏的显示屏 140 , 控制器 110 可以确定是否发生了事件。 当事件发生时,控制器 110 可在触摸屏上定义 140 ,区域包括例如第一区域对应于封面的窗口区域 200 ,例如,前盖单元 210 第二个区域对应于封面的封面输入区域 200 ,例如,前盖单元 210 . 事件可以包括预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 可能还有许多其他事件。 该事件可以是任何事件,只要它触发在显示屏幕上包括第一和第二区域的区域的定义。 [0096] 通讯单元 120 可连接移动终端 100 通过一根或多根天线连接到外部设备,并且可以与外部设备进行通信。 外部设备可以包括另一设备、便携式电话、智能手机、平板PC和服务器。 通讯单元 120 可以包括各种通信模块,例如移动通信模块、NFC模块、蓝牙模块等,并且可以通过各种通信方案例如移动通信、NFC、蓝牙等与外部设备进行通信。 喜欢。 [0097] 例如,移动终端 100 可以向便携式电话、智能手机、平板电脑或具有输入到移动终端的电话号码的其他设备发送无线信号或从其接收无线信号 100 ,用于通过移动通信模块进行语音通话、视频通话、短消息服务(SMS)或多媒体消息服务(MMS)。 此外,移动终端 100 可以通过NFC模块或蓝牙模块从外部设备接收信息。 在本发明的各个实施例中,通信单元 120 除了NFC模块和蓝牙模块之外,还可以包括无线局域网(WLAN)模块和另一短程通信模块中的至少一个,并且可以通过WLAN模块和短程通信中的至少一个接收信息 模块。 WLAN模块可以在控制器的控制下连接到互联网 110在安装了无线接入点 (AP) 的地方。 WLAN模块可以支持电气和电子工程师协会(IEEE)的WLAN标准IEEE802.11x。 短距离通信模块可以在移动终端之间进行短距离无线通信 100 和控制器控制下的外部设备 110 . 短距离通信可以符合红外数据协会(IrDA)等。 [0098] 记忆 130 可根据控制器的操作存储输入/输出信号或数据 110 , 通讯单元 120 , 触摸屏 140 , 和 I/O 单元 150 , 在控制器的控制下 110 . 记忆 130 可以存储多个用于控制移动终端的程序 100 或控制器 110 、多个应用程序以及用于执行各种功能的程序和数据。 [0099] 术语“存储器”可能包括 ROM 112 和内存 113 控制器内 110 ,或安装在移动终端上的存储卡(例如,安全数字(SD)卡、记忆棒等) 100 . 记忆 130 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)、固态驱动器(SSD)等。 [0100] 记忆 130 可以是机器可读介质(例如,计算机可读介质)。 机器可读介质可以定义为向机器提供数据以便机器可以执行特定功能的介质。 机器可读介质可以是存储介质。 记忆 130 可以包括非易失性介质和易失性介质。 所有这些媒体都应该是一种类型,可以为向机器读取命令的物理设备提供可检测的命令。 机器可读介质包括但不限于软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、光盘中的至少一种。 穿孔卡、纸带、RAM、可编程 ROM (PROM)、可擦除 PROM (EPROM) 和 Flash-EPROM。 在本发明的一个实施例中,存储器 130 可以存储封面类型信息。 [0101] 触摸屏 140 可以向用户提供各种图形用户界面(GUI)。 例如,触摸屏 140 可以通过用户的身体部位(例如,手指)或触摸输入单元接收各种手势输入,包括至少一个触摸输入或接近输入 158 (例如,一支笔)。 触摸屏 140 例如,可以实现为电阻型、电容型、电磁共振(EMR)型或它们的组合。 [0102] 在本发明的一个实施例中,触摸屏 140 可以在控制器的控制下显示应用程序的执行屏幕、消息屏幕、消息写入屏幕、消息接收屏幕等 110 . 此外,触摸屏 140 可以在显示屏的预定部分区域显示信息,例如触摸屏的第一区域 140 对应窗口区域 201 a ,而不在第一区域以外的区域显示信息。 [0103] 输入输出模块 150 包括一个按钮 152 , 麦克风 154 , 扬声器 156 , 和输入单元 158 , I/O 模块 150 不受限制。 可以提供光标控件,例如鼠标、轨迹球、操纵杆或光标方向键,用于与控制器通信 110 以及用于控制触摸屏上的光标移动 140 . [0104] 一个或多个按钮 152 可在移动终端中提供 100 并且可以向控制器提供与用户的按压相对应的各种输入信号 110 . [0105] 麦克风 154 可以接收来自各种声源的语音或声音,并在控制器的控制下将接收到的语音或声音转换为电信号 110 . [0106] 演讲者 156可以将与各种信号(例如,无线信号、广播信号、数字音频文件、数字视频文件等)对应的声音与应用程序的执行一起输出到移动终端的外部 100 在控制器的控制下 110 . [0107] 输入单元 158 可以是被配置为插入并保存在移动终端内部的设备或对象 100 ,或者单独配置。 在前一种情况下,输入单元 158 可以从移动终端中取出或插入移动终端 100 . 输入单元 158 可以是用户的手指,也可以是触控笔(以下简称笔)等输入工具,可以通过接近或触摸触摸屏来输入用户手势 140 . [0108] 移动终端 100 还可以包括传感器单元 160 . 传感器单元 160 可以包括至少一个磁力传感器 692 . 传感器单元 160 可以感应到永磁体施加的磁力 691 封面的 200 . [0109] 移动终端 100 还可以包括连接端口 180 . 连接端口 180 可以连接到连接器单元 202 a 封面的 200 . 一旦连接端口 180 连接到连接器单元 202 a , 连接端口 180 可能会收到有关封面的封面类型信息 200 从连接器单元 202 a. [0110] 移动终端 100 还可以包括封面类型信息接收器 190 . 封面式信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 . 如果覆盖类型信息接收器 190 被配置为短距离通信模块,当前盖单元 210 覆盖移动终端的正面 100 , 覆盖类型信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 , 和控制器 110 可确定前盖单元是否 210 覆盖触摸屏 140 基于从封面类型信息接收器接收的封面类型信息 190 . [0111] 如图。 图8是示出使用定义在触摸屏上的第一区域和第二区域的UI操作的流程图 140 ,分别对应封面的窗口区域和封面输入区域 200 在移动端 100 ,根据本发明的一个实施例。 [0112] 参考图。 8、移动端 100 标识封面的封面类型 200 , 在步 810 . 例如,控制器 110 移动终端的 100 可以识别封面的封面类型 200 通过感应从盖子施加的磁力 200 或通过接收有关封面的封面类型信息 200 从封面 200 . 关于封面的封面类型信息 200 可以包括关于在封面上定义的窗口区域和封面输入区域的位置信息 200 . 关于封面的封面类型信息 200 可能包括封面标识符 (ID) 和控制器 110 可以确定封面的窗口区域和封面输入区域的位置 200 使用封面 ID。 在这种情况下,关于窗口区域的位置和封面的封面输入区域的信息 200 各种封面ID可以预先存储在内存中 130 . 封面类型信息还可以包括关于封面的大小和位置中的至少一项的信息 200 以及封面的非窗口区域的位置 200 . [0113] 在步骤 820 , 控制器 110 确定触摸屏的触摸屏区域 140 包括对应于盖的窗口区域的第一区域 200 以及对应于封面的封面输入区域的第二区域 200 ,基于关于封面的封面类型信息200 . [0114] 带前盖单元 210 封面的 200 关闭,控制器 110 判断触摸屏上是否输入了用户手势 140 通过前盖单元 210 , 在步 830 . [0115] 如果在触摸屏的第二区域检测到用户手势 140 对应前盖单元的封面输入区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 在一步 840 . [0116] 如果在触摸屏的第一区域检测到用户手势 140 对应前盖单元的窗口区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 , 在步 850 . [0117] 例如,使用触摸屏 140 移动终端的 100 用前盖单元盖住 210 , 控制器 110 可以判断移动终端是否发生了事件 100 并且可以在触摸屏的第一区域显示与事件对应的信息 140 对应前盖单元的窗口区域 210 . 控制器 110 根据对触摸屏的第二区域的用户手势输入执行预定操作 140 ,对应前盖单元的封面输入区域 210 . 事件可以包括例如预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 这些事件纯粹是示范性的。 本领域技术人员可以清楚地理解,触发触摸屏第一区域显示信息的各种事件 140 在触摸屏的第二区域接收用户手势 140 可以实施。 [0118] 此外,例如,控制器 110 可以在触摸屏的显示画面中识别窗口区域对应的第一区域和覆盖输入区域对应的第二区域 140 ,基于关于封面的封面类型信息,并且可以激活第一区域作为信息显示区域和第二区域作为触摸输入区域。 这里,也可以在第一区域中感测触摸输入。 [0119] 图 图9、图10和图11是图示根据本发明实施例的用于各种类型的盖子的触摸屏区域的配置的图。 [0120] 参考图。 9、窗口区 910 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 920 , 和整个非窗口区域 920 是封面中的封面输入区域 200 ,根据本发明的一个实施例。 [0121] 在本实施例中,移动终端 100 激活第一区域 911 对应窗口区域 910 和第二个区域 921 对应非窗口区域 920 ,即触摸屏屏幕上的覆盖输入区域 140 . 可以显示信息并且可以在第一区域中感测触摸输入 911 ,而可以感测到触摸输入但信息可能不会显示在第二区域中 921 . [0122] 参考图。 10、窗口区 1010 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1020 ,以及一个覆盖输入区域 1030 在非窗口区域的一部分定义 1020 窗下区域 1010 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1011 对应窗口区域 1010 和第二个区域 1031对应覆盖输入区域 1030 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1011 ,而在第二区域中可以感测到触摸输入 1031 . 也可以在第一区域中感测到触摸输入 1011 . [0123] 参考图。 11、窗口区 1110 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1120 ,以及一个覆盖输入区域 1130 在非窗口区域的一部分定义 1120 窗下区域 1110 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1111 对应窗口区域 1110 和第二个区域 1131 对应覆盖输入区域 1130 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1111 ,而在第二区域中可以感测到触摸输入 1131 . 也可以在第一区域中感测到触摸输入 1111 . [0124] 参考图。 12、窗口区 1210 定义在前盖单元的右侧 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1220 ,以及一个覆盖输入区域 1230 在非窗口区域的一部分定义 1220 在窗口区域的左侧 1210 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1211 对应窗口区域 1210 和第二个区域 1231 对应覆盖输入区域 1230 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1211 ,而在第二区域中可以感测到触摸输入 1231 . 也可以在第一区域中感测到触摸输入 1211 . [0125] 在本发明的实施例中,可以以各种方式应用触摸输入。 如图。 图13是图示根据本发明实施例的触摸输入的图。 参考图。 参照图13,触摸输入可以包括双击、向上滑动或(String), 111522(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 11 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), AU2015216023A1(String), 1046966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), CN104834353A(String), 1046967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), CN104834353B(String), 1046968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), EP2905681A1(String), 1046969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), EP2905681B1(String), 1046970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), JP2017511919A(String), 1046971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), KR1020150094231A(String), 1046972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), KR102245289B1(String), 1046973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), US10075579B2(String), 1046974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), US20150229754A1(String), 1046975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270634(Integer), WO2015122661A1(String), 1046976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10075579B2(String), US10075579B2(String), 1536595200(Integer), 270634(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.843 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.843 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.845 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.846 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.846 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184951(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.867 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.872 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2728175eea054587b0b56856d9e4b317.png(String), 184952(Integer), 2728175eea054587b0b56856d9e4b317.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, mobile terminal auxiliary device and method for controlling the same(String), 移动终端、移动终端辅助装置及其控制方法(String), US9749858B2(String), Methods and apparatuses are provided for controlling a mobile terminal and a mobile terminal auxiliary device. Information on at least one of the mobile terminal and the mobile terminal auxiliary device and security-related information on the at least one of the mobile terminal and the mobile terminal auxiliary device are stored. It is determined whether the mobile terminal and the mobile terminal auxiliary device exist within a predetermined available distance. If the mobile terminal and the mobile terminal auxiliary device exist within the predetermined available distance, it is determined whether the mobile terminal or the mobile terminal auxiliary device has been registered by using the stored information.(String), 提供了一种移动终端的控制方法和装置以及移动终端辅助设备。 存储关于移动终端和移动终端辅助设备至少之一的信息以及关于移动终端和移动终端辅助设备至少之一的安全相关信息。 确定移动终端和移动终端辅助设备是否存在于预定的可用距离内。 如果移动终端和移动终端辅助设备存在于预定可用距离内,则使用存储的信息判断移动终端或移动终端辅助设备是否已经注册。(String), US14/509670(String), 1412697600(Integer), US9749858B2(String), 1503936000(Integer), 1503936000(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 16(Integer), US20020111138A1 | US20080287062A1 | US20110173447A1 | US20120139879A1 | US20120206555A1 | US20120258665A1 | US20120281686A1 | US20120322376A1 | US20130143499A1 | US20130257777A1 | US20140115690A1 | US20140298672A1 | US20140378056A1 | US9154954B2 | US9179310B2 | US9398133B2(String), \20230420\2728175eea054587b0b56856d9e4b317.png(String), 20(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.945 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 1. A method for controlling a mobile terminal auxiliary device, the method comprising:storing information on at least one mobile terminal and security-related information on each of the at least one mobile terminal;determining whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal; andif the mobile terminal exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile terminal.(String), 1.一种移动终端辅助设备的控制方法,该方法包括:存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;根据移动终端发射的信号强度,判断移动终端是否存在于移动终端辅助设备的预定可用范围内;和如果移动终端在预定可用范围内,则解除移动终端的锁定状态,包括显示锁定图像。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 2. The method of claim 1, wherein determining whether the mobile terminal exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 2.如权利要求1所述的方法,其中判断移动终端是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端是否在预定可用范围内。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 3. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;receiving, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal;comparing the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 3.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;从移动终端接收关于触摸信号在移动终端的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端辅助设备的触摸信号的时间进行比较;和如果触摸时间信息与检测到移动终端辅助设备的触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 4. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;transmitting, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device; andreceiving, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 4.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;和从移动终端接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 5. The method of claim 1, further comprising:determining whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device; andif the mobile terminal does not exist within the predetermined connection range, deleting information on the mobile terminal.(String), 5.如权利要求1所述的方法,还包括:判断移动终端是否存在于移动终端辅助设备的预定连接范围内;和如果预定连接范围内不存在移动终端,则删除移动终端上的信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 6. A method for controlling a mobile terminal, the method comprising:storing information on at least one mobile terminal auxiliary device;determining whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device; andif the mobile terminal auxiliary device exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile device.(String), 6.一种移动终端的控制方法,该方法包括:在至少一个移动终端辅助设备上存储信息;根据移动终端辅助设备发送的信号强度判断移动终端辅助设备是否存在于距移动终端预定可用范围内;和如果移动终端辅助设备存在于预定可用范围内,则解除移动设备的锁定状态,包括显示锁定图像。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 7. The method of claim 6, wherein determining whether the mobile terminal auxiliary device exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal auxiliary device exists within the predetermined available range, when the use signal is detected.(String), 7.如权利要求6所述的方法,其中判断移动终端辅助设备是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 8. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;receiving, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device;comparing the received touch time information with a time when the touch signal of the mobile terminal is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 8.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端触摸信号的时间进行比较;和若触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 9. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;transmitting, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal; andreceiving, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 9.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息;和从移动终端辅助设备接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 10. The method of claim 6, further comprising:determining whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal; andif the mobile terminal auxiliary device does not exist within the predetermined connection range, deleting information on the mobile terminal auxiliary device.(String), 10.如权利要求6所述的方法,还包括:判断移动终端辅助设备是否存在于移动终端的预定连接范围内;和如果预定连接范围内不存在移动终端辅助设备,则删除移动终端辅助设备的信息。11、一种移动终端辅助设备包括:与至少一个移动终端通信的通信单元;存储器,存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;和控制器,基于从移动终端发送的信号的强度确定移动终端是否存在于移动终端辅助设备的预定可用范围内,并且如果是则释放移动终端的锁定状态,包括显示锁定图像移动终端存在于预定的可用范围内。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 11. A mobile terminal auxiliary device comprising:a communication unit that communicates with at least one mobile terminal;a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal; anda controller that determines whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal exists within the predetermined available range.(String), 12.如权利要求11所述的装置,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端是否存在于预定可用范围内。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 12. The device of claim 11, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 13.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,从移动终端接收触摸时间信息,检测移动终端触摸信号的时间,将接收到的触摸时间信息与触摸发生的时间进行比较检测到移动终端辅助设备的信号,如果触摸时间信息与检测到移动终端辅助设备触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸设备。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 13. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, receive, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal, compare the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 14.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,并从移动终端接收触摸时间信息移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 14. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, transmit, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, and receive, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 15.如权利要求11所述的装置,其中控制器控制判断移动终端是否存在于移动终端辅助设备的预定连接范围内,如果移动终端不存在于预定连接范围内,则删除移动终端上的信息。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 15. The device of claim 11, wherein the controller controls to determine whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device, and if the mobile terminal does not exist within the predetermined connection range, delete information on the mobile terminal.(String), 16.移动终端包括:通信单元,与至少一个移动终端辅助设备进行通信;存储器,存储关于至少一个移动终端辅助设备的信息;和控制器,基于从移动终端辅助设备发送的信号强度确定移动终端辅助设备是否存在于距移动终端的预定可用范围内,并释放移动终端的锁定状态,包括显示锁定图像如果移动终端辅助设备存在于预定可用范围内,则终端。(String), 1(Integer), 14(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 16. A mobile terminal comprising:a communication unit that communicates with at least one mobile terminal auxiliary device;a memory that stores information on the at least one mobile terminal auxiliary device; anda controller that determines whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal auxiliary device exists within the predetermined available range.(String), 17.如权利要求16所述的移动终端,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 17. The mobile terminal of claim 16, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal auxiliary device exists within the predetermined available range when the use signal is detected.(String), 18.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,将接收到的触摸时间信息与触摸时间进行比较。检测到移动终端的触摸信号,如果触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 18. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, receive, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, compare the received touch time information with a time when the touch signal of the mobile terminal is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 19.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息,并从移动终端辅助设备接收触摸时间信息。移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 19. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, transmit, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal, and receive, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 20.如权利要求16所述的移动终端,其中控制器判断移动终端辅助设备是否存在于移动终端的预定连接范围内,如果移动终端辅助设备不存在于预定连接范围内,则控制删除关于移动终端辅助设备的信息。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:34.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184952(Integer), 20. The mobile terminal of claim 16, wherein the controller determines whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal, and if the mobile terminal auxiliary device does not exist within the predetermined connection range, controls to delete information on the mobile terminal auxiliary device.(String), 1(Integer), 19(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111523(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.140 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.140 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184952(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to Korean Patent Application No. 10-2013-0119737, filed on Oct. 8, 2013, the content of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal and a mobile terminal auxiliary device, and more particularly, to a control method by which security related functions of the mobile terminal can be executed without an additional authentication process by registration between the mobile terminal and the mobile terminal auxiliary device. [0004]2. Description of the Related Art [0005]Terminals are classified into mobile/portable terminals and stationary terminals according to their mobility. Mobile terminals are divided into handheld terminals and vehicle mount terminals according to whether a user can carry the terminals. [0006]Terminals have been implemented with multimedia players that have multiple functions such as, for example, photographing still images or moving images, reproducing music files or movie files, playing games, receiving broadcasts, or the like. [0007]In order to support and strengthen the functions of the terminals, structures and/or software of the terminals can be improved. [0008]In addition, various terminal auxiliary devices have been used for convenient use of the terminals. Particularly, electronic pens, such as styluses, may be used as terminal auxiliary devices. [0009]The terminal and the pen are connected with each other wirelessly or using a wire, and the terminal receives a user input by using the pen. Therefore, the user can input specific texts, symbols, images, or the like more easily, accurately and faster. [0010]Pens are widely used in the terminals as accessories. Further, with the improvement of technology, the pens can transfer more precise illustrations and designs of a user to electronic devices. [0011]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0012]As shown in FIG. 1A, when a user touches specific contents such as, for example, a memo, a schedule, an email, or a diary, which are displayed in a display unit of a mobile terminal 100, by using a mobile terminal auxiliary device, such as, for example, an electronic pen 150, an operation of pre-viewing the corresponding contents may be executed. The touch of the electronic pen 150 may be performed by a proximity touch and/or a contact touch. [0013]In addition, as shown in FIG. 1B, when the mobile terminal auxiliary device, for example, the electronic pen 150, which is connected with the mobile terminal, is taken out from the mobile terminal while a screen 110 of the mobile terminal is turned off, the mobile terminal may be configured to automatically switch to a locked image 120. Here, the locked image means an image followed by a waiting image in which the mobile terminal can be used. That is, the mobile terminal may wait for instructions for releasing security, such as a password input of a user. When the user inputs the instruction for releasing security, the locked state of the mobile terminal may be released, and the mobile terminal may switch to the waiting image to thereby execute operations thereof. [0014]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0015]Referring to FIG. 2A, in contents 210 such as, for example, a memo, when other people's accesses are restricted through a locking setup by a user, a preview function by the mobile terminal auxiliary device 150 of FIG. 1A may be deactivated. That is, in the case of a memo that is set to be locked, although someone touches the corresponding contents by the mobile terminal auxiliary device, the preview function may not be executed unless the password is entered by the user. [0016]In addition, as shown in FIG. 2B, although a locked image 230 is displayed by taking out the mobile terminal auxiliary device from the mobile terminal while a screen 220 of the mobile terminal is turned off, the terminal may be switched to an available state, i.e., the waiting state, only by inputting the instruction for releasing security, such as by entering the password by the user. [0017]Further, although not shown in the drawings, even while using the mobile terminal by the mobile terminal auxiliary device, for example, the electronic pen, if the mobile terminal does not continuously receive usage instruction inputs, i.e., the touch signal inputs, the screen of the mobile terminal will be turned off soon and the security function will be resumed. [0018]Furthermore, even though the user obtains the authority to access the contents or releases the locked state of the mobile terminal through the security process, if the mobile terminal is not used for a while or it is required to be turned off and then turned on, the user is required to repeat the security process. SUMMARY OF THE INVENTION [0019]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal auxiliary device that may be authenticated through a security process when it is connected with a mobile terminal, so that repetition of the security process may be removed when the mobile terminal auxiliary device is required to be used afterwards, to thereby enhance the usability of the mobile terminal. [0020]Another aspect of the present invention provides convenience in using applications, which can be used only by the process of logging on or releasing a locked state by means of a mobile terminal auxiliary device. [0021]An additional aspect of the present invention prevents a screen of a mobile terminal from being turned off or a locked state from being resumed during the use of the mobile terminal, by continuously checking the use of the mobile terminal using a low power technology without an additional operation of a mobile terminal auxiliary device. [0022]A further aspect of the present invention allows, when a user wishes to use each of a plurality of mobile terminals, or authentication is required, the user to control each mobile terminal by the authenticated mobile terminal auxiliary device and use the mobile terminal without the security checking process to thereby provide convenient use thereof. [0023]Another aspect of the present invention allows each mobile terminal to identify the user through the corresponding mobile terminal auxiliary device, and a UI of the mobile terminal to be configured with specific values predefined according to the setup or user's desire. [0024]In accordance with an aspect of the present invention, a method is provided for controlling a mobile terminal auxiliary device. Information on at least one mobile terminal and security-related information on each of the at least one mobile terminal are stored. It is determined whether a mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device. If the mobile terminal exists within the predetermined available distance, it is determined whether the mobile terminal has been registered by using the stored information on the at least one mobile terminal. If the mobile terminal has been registered, security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, is transmitted to the mobile terminal. [0025]In accordance with another aspect of the present invention, a method is provided for controlling a mobile terminal. Information on at least one mobile terminal auxiliary device is stored. It is determined whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal. If the mobile terminal auxiliary device exists within the predetermined available distance, it is determined whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device. If the mobile terminal auxiliary device has been registered, predetermined security-related information is applied according to the mobile terminal auxiliary device. [0026]In accordance with another aspect of the present invention, a mobile terminal auxiliary device is provided that includes a communication unit that communicates with at least one mobile terminal, and a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal. The mobile terminal auxiliary device also includes a controller that determines whether the mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device, determines whether the mobile terminal has been registered by using the stored information on at least one mobile terminal if the mobile terminal exists within the predetermined available distance, and controls the communication unit to transmit security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, to the mobile terminal, if the mobile terminal has been registered. [0027]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a communication unit that communicates with at least one mobile terminal auxiliary device, and a memory that stores information on the at least one mobile terminal auxiliary device. The mobile terminal also includes a controller that determines whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal, determines whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device if the mobile terminal auxiliary device exists within the predetermined available distance, and controls to apply predetermined security-related information according to the mobile terminal auxiliary device if the mobile terminal auxiliary device has been registered. BRIEF DESCRIPTION OF THE DRAWINGS [0028]The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0029]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0030]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0031]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention; [0032]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention; [0033]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention; [0034]FIG. 6 is a flowchart illustrating the operation of a mobile terminal auxiliary device, according to an embodiment of the present invention; [0035]FIG. 7 is a flowchart illustrating the operation of a mobile terminal, according to an embodiment of the present invention; [0036]FIGS. 8A and 8B are diagrams illustrating registration between a mobile terminal and a mobile terminal auxiliary device and the operation thereof, according to an embodiment of the present invention; [0037]FIGS. 9A and 9B are diagrams illustrating an available distance, according to an embodiment of the present invention; [0038]FIG. 10 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to an embodiment of the present invention; [0039]FIG. 11 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to another embodiment of the present invention; [0040]FIG. 12 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in used by a mobile terminal, according to an embodiment of the present invention; [0041]FIG. 13 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by a mobile terminal, according to another embodiment of the present invention; [0042]FIGS. 14A-14C are diagrams illustrating a determination of whether a mobile terminal auxiliary device has been used, according to an embodiment of the present invention; [0043]FIGS. 15A-15D are diagrams illustrating uses of mobile terminals and mobile terminal auxiliary devices, according to an embodiment of the present invention; [0044]FIG. 16 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal auxiliary device and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0045]FIG. 17 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0046]FIG. 18 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to an embodiment of the present invention; and [0047]FIG. 19 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to another embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0048]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0049]Hereinafter, a mobile terminal associated with the present invention will be described in detail with reference to drawings. The suffixes of component elements used in the following descriptions, such as, a “module” and a “unit”, are assigned or used together only for ease of description, but they do not have distinguishing meanings or roles. [0050]A mobile terminal described in the embodiments of the present invention may be embodied as a portable phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation terminal, and the like. However, it is apparent to those skilled in the art that a configuration according to embodiments of the present invention are also applied to a stationary terminal such as, for example, a digital TV, a desktop computer, and the like. [0051]Mobile terminal auxiliary devices of the embodiments of the present invention may include electronic pens, such as styluses, which can communicate with a mobile terminal. In addition, it is obvious for those skilled in the art that the mobile terminal auxiliary devices of the present invention may be applied to stationary terminals such as TVs, desktop computers, or the like, as well as the mobile terminals. [0052]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention. [0053]A mobile terminal auxiliary device 300 includes a communication unit 310, a memory 320, and a controller 330. The mobile terminal auxiliary device is not limited to the elements of FIG. 3, and it may further include other elements, or some of the elements may be omitted. For example, the mobile terminal auxiliary device 300 may further include an output unit, such as, for example, an audio output module, an alarm unit, and a display unit, and a user input unit for receiving a user input. [0054]The communication unit 310 may include at least one module enabling wireless communication between the mobile terminal auxiliary device 300 and a mobile terminal. For example, the communication unit 310 may include a short-range communication module for near field communication. Here, the short-range communication technology may adopt Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra wideband (UWB), ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a Bluetooth (BT) module and a Bluetooth low energy (BLE) module. [0055]The communication unit 310 may allow the mobile terminal auxiliary device 300 and the mobile terminal to register with each other by communicating with the mobile terminal, as described in greater detail below. [0056]The memory 320 may store programs for processing and controlling of the controller 330 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like). The memory 320 may store frequency of use for the data. [0057]The memory 320 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., a secure digital (SD) memory, an XD memory, or the like), a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a programmable ROM (PROM), a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal auxiliary device 300 may operate in relation to a web storage for providing a storage function of the memory 320 on the Internet. [0058]In general, the controller 330 controls overall operations of the mobile terminal auxiliary device 300. For example, the controller 330 may control to perform an operation of registering the mobile terminal auxiliary device 300 and the mobile terminal with each other. In addition, in the case of using the mobile terminal auxiliary device 300 through authentication between the mobile terminal and the mobile terminal auxiliary device 300, the controller 330 may control to use the mobile terminal without an additional security checking process, which is described in greater detail below. [0059]The mobile terminal auxiliary device 300 may further include a user input unit. The user input unit generates input data for controlling operations of the mobile terminal auxiliary device by a user. The user input unit may include at least one of buttons provided on the front, back, or side surface of the mobile terminal auxiliary device, touch sensors (a pressure type/a capacitive type), keypads, dome switches, jog wheels, jog switches, or the like, but it is not limited thereto. [0060]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention. [0061]The mobile terminal auxiliary device, according to an embodiment of the present invention, may be embodied as an electronic pen 400, such as a stylus. The electronic pen 400 includes a communication unit 410, a memory 420, a controller 430, a touch recognition unit 440, and the like, but it is not limited thereto. For example, the electronic pen 400 may further include a power supply, such as a battery 450, and the power supply may receive external power and internal power to be supplied to each element to operate under the control of the controller 430. The power supply may include at least one of connection ports, a power supply controller, and a charge monitoring unit, as well as the battery 450. [0062]The communication unit 410 may include at least one module enabling wireless communication between the electronic pen 400 and a mobile terminal. According to an embodiment of the present invention, the communication unit 410 may include at least one of a BT module or a BLE module. [0063]The communication unit 410 may allow the electronic pen 400 and the mobile terminal to be registered with respect to each other by communicating with the mobile terminal, as described in greater detail below. [0064]The memory 420 may store programs for processing and controlling of the controller 430 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like), as described in detail above. [0065]In general, the controller 430 controls overall operations of the electronic pen 400. For example, the controller 430 may control to perform an operation of registering the electronic pen 400 and the mobile terminal with each other. In addition, in the case of using the electronic pen 400 through authentication between the mobile terminal and the electronic pen 400, the controller 430 may control to use the mobile terminal without an additional security checking process, as described in detail below. [0066]The touch recognition unit 440 may recognize touch signals of the electronic pen 400. When the touch signal of the electronic pen 400 is input, the controller 430 controls to perform a predetermined operation according to the touch signal input. According to an embodiment of the present invention, in addition to the touch recognition unit 440, the electronic pen 400 may further include a user input unit for generating input data of a user. The user input unit may include at least one of buttons provided on the side surface of the electronic pen, a keypad, a dome switch, a jog wheel, a jog switch, or the like, but it is not limited thereto. [0067]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention. [0068]A mobile terminal 500 includes a communication unit 510, a memory 520, a controller 530, a user input unit 540, and an output unit 550. The elements shown in FIG. 5 are not essential to the mobile terminal, and the mobile terminal may further include other elements, or some of the elements may be omitted. [0069]The communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and a wireless communication system, or the mobile terminal 500 and a network where the mobile terminal 500 is located. In addition, the communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and the mobile terminal auxiliary device. For example, the communication unit 510 may include a broadcast receiving module, a mobile communication module, a wireless Internet module, a short-range communication module, a location information module, and the like. [0070]The broadcast receiving module receives broadcast signals and/or broadcast-related information from external broadcast management servers through broadcasting channels. The broadcasting channels may include a satellite channel and a ground wave channel. At least two broadcast receiving modules may be provided in the mobile terminal 500 to concurrently receive broadcasts through at least two broadcasting channels or to switch between at least two broadcasting channels. [0071]The mobile communication module transmits and receives wireless signals to and from at least one of base stations, other terminals, and servers in mobile communication networks, such as, for example, global system for mobile communication (GSM), code division multiple access (CDMA), wideband CDMA (WCDMA) (but not limited thereto). The wireless signals may include voice call signals, video call signals, or various data according to transmission and reception of text/multimedia messages. [0072]The wireless Internet module for connecting the wireless Internet may be built in the mobile terminal 500 or externally provided. The wireless Internet may utilize the technologies of wireless LAN (WLAN), Wi-Fi, wireless broadband (Wibro), world interoperability for microwave access (Wimax), high speed downlink packet access (HSDPA), GSM, CDMA, WCDMA, long term evolution (LTE), or the like. [0073]The wireless Internet connection through Wibro, HSDPA, GSM, CDMA, WCDMA, and LTE is made by wireless mobile communication networks. Accordingly, the wireless Internet module that connects with the wireless Internet through the mobile communication networks may be regarded as a type of mobile communication module. [0074]The short-range communication module refers to a module for near field communication. The short-range communication technology may adopt BT, RFID, IrDA, UWB, ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a BT module and a BLE module. [0075]The user input unit 540 generates input data for controlling operations of the mobile terminal by a user. The user input unit 540 may include buttons 543 on the front, back or side surface of the mobile terminal 500, and a touch sensor (a pressure type/a capacitive type) 545. The user input unit 540 may further include keypads, dome switches, jog wheels, jog switches, or the like. [0076]The output unit 550 may generate outputs related to a sense of sight, a sense of hearing, or a sense of touch, and includes a display unit 555, but it is not limited thereto. For example, the output unit 550 may include an audio output module, an alarm module, and a haptic module. [0077]The display unit 555 displays (outputs) information processed in the mobile terminal 500. For example, when the mobile terminal 500 is in a phone call mode, the display unit 555 displays a user interface (UI) or a graphic user interface (GUI) related to the phone call. When the mobile terminal 500 is in a video call mode or photographing mode, the display unit 555 displays images, which are photographed and/or received, using the UI or the GUI. [0078]The display unit 555 may include at least one of a liquid crystal display (LCD), a thin film transistor-LCD (TFT LCD), an organic light-emitting diode (OLED), a flexible display, and a 3D display. [0079]Some of the above displays may be configured to be transparent or light-penetrable in order to view the outside therethrough, which are called transparent displays, typically, including transparent OLEDs (TOLEDs). The back structure of the display unit 555 may be also configured to be light-penetrable. According to the above structure, a user can see objects behind the terminal through the area of the display unit 555 of the terminal. [0080]Two or more display units 555 may be provided according to the type of mobile terminal 500. For example, a plurality of display units may be arranged to be spaced from each other or to be integral on the same plane, or may be disposed on different planes in the mobile terminal 500. [0081]In the case of the display unit 555 and the touch sensor 545, which are formed in a layer structure or integrally (hereinafter, referred to as a “touch screen”), the display unit 555 may be used as the input device as well as the output device. The touch sensor may be formed to be a laminate with the display unit 555 in the case of, for example, touch films, touch sheets, touch pads, or the like, or may be integrally formed with the display unit 555. [0082]The touch sensor may be configured to convert the change of pressure acting on the specific portion of the display unit 555 or the change of capacitance generating on the specific portion of the display unit 555 to electric signals. The touch sensor may be configured to detect the touch pressure as well as the touch point and the touch area. [0083]Upon a touch input on the touch sensor, the corresponding signals are transmitted to a touch controller. The touch controller processes the signals and transmits the corresponding data to the controller 530. Accordingly, the controller 530 may recognize which area of the display unit 555 has been touched. [0084]Although not shown in the drawing, a proximity sensor may be disposed inside or around the touch screen of the mobile terminal 500. The proximity sensor may detect objects approaching a predetermined detection surface, or objects around the proximity sensor, by using an electromagnetic field force or an infrared ray without mechanical contacts. The proximity sensor has a long life span and various utilization compared to a contact type sensor. [0085]The proximity sensor may include a transparent photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillating proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor an infrared proximity sensor, or the like. [0086]Hereinafter, for convenience of explanation, the term “proximity touch” may refer to an operation in which a pointer approaches the touch screen where the proximity sensor is installed to be thereby recognized without a contact, and the term “contact touch” may refer to an operation of touching of the pointer on the screen. A proximity touch point of the pointer on the touch screen may denote the point on the screen which vertically corresponds to the location of the pointer in the state of the proximity touch. Hereinafter, the term “touch” may encompass the proximity touch as well as the contact touch. [0087]According to an embodiment of the present invention, the proximity touch may include a hovering input. [0088]The proximity sensor detects the proximity touch and a proximity touch pattern (e.g., a proximity touch distance, a proximity touch direction, a proximity touch speed, a proximity touch time, a proximity touch point, a proximity touch movement state, or the like). Information corresponding to the detected proximity touch and the proximity touch pattern may be displayed on the touch screen. [0089]The memory 520 may store programs for processing and controlling of the controller 530 and perform a function of temporarily storing input/output data (e.g., a telephone number list, messages, audio, still images, moving images, information on the mobile terminal, identification information on the mobile terminal, information on the mobile terminal auxiliary device, security related information, or the like). The memory 520 may store frequency of use for the data. [0090]In addition, the memory 520 may store data on various vibrations and sounds, which are output upon the touch input on the touch screen. [0091]The memory 520 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD memory, an XD memory, or the like), a RAM, an SRAM, a ROM, an EEPROM, a PROM, a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal 500 may operate in relation to a web storage for providing a storage function of the memory 520 on the Internet. [0092]The mobile terminal 500 may further include an audio/video (A/V) input unit for inputting audio signals or video signals, and a sensing unit for generating sensing signals to sense the current state of the mobile terminal 500, such as, for example, the opening/closing state of the mobile terminal 500, the location of the mobile terminal 500, contact of users, directions of the mobile terminal, and acceleration/deceleration of the mobile terminal, and to thereby control operations of the mobile terminal 500. [0093]In addition, the mobile terminal 500 may include an interface unit that plays a role of a path for all external devices connected with the mobile terminal 500. The interface unit receives data or power from the external devices and transfers the same to each element of the mobile terminal 500. The interface unit also allows data to be transmitted to the external devices from the mobile terminal 500. For example, the interface unit may include a wireless/wired headset port, an external charge port, a wireless/wired data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, or the like. [0094]In addition, the mobile terminal 500 may further include a power supply that receives external power and internal power and supplies the same to each element for operations under the control of the controller(String), 优先 [0001] 本申请根据 35 U.S.C. 要求优先权 2013 年 10 月 8 日提交的韩国专利申请号 10-2013-0119737 的 §119(a),其内容通过引用并入本文。 发明背景 [0002] 一、发明领域 [0003] [0001] 本发明总体上涉及移动终端和移动终端辅助设备,并且更具体地,涉及一种控制方法,通过该方法可以执行移动终端的安全相关功能而无需通过移动终端和移动终端之间的注册的附加认证过程 终端辅助设备。 [0004] 二、相关技术说明 [0005] 终端根据其移动性分为移动/便携终端和固定终端。 移动终端根据用户是否可以携带终端分为手持终端和车载终端。 [0006] 终端已经实现了具有多种功能的多媒体播放器,例如拍摄静止图像或运动图像、再现音乐文件或电影文件、玩游戏、接收广播等。 [0007] 为了支持和加强终端的功能,可以改进终端的结构和/或软件。 [0008] 此外,为了方便终端的使用,还使用了各种终端辅助设备。 特别地,电子笔,例如手写笔,可以用作终端辅助设备。 [0009] 终端和笔通过无线或有线方式相互连接,终端通过笔接收用户输入。 因此,用户可以更方便、更准确、更快速地输入特定的文字、符号、图像等。 [0010] 笔作为配件广泛应用于终端。 此外,随着技术的进步,笔可以将用户更精确的插图和设计转移到电子设备上。 [0011] 图1A和1B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0012] 如图1A所示,当用户触摸移动终端的显示单元中显示的特定内容,例如备忘录、日程、电子邮件或日记时 100 ,通过使用移动终端辅助设备,例如电子笔 150 ,可以执行预览相应内容的操作。 电子笔的触感 150 可以通过接近触摸和/或接触触摸来执行。 [0013] 另外,如图1B所示,当移动终端辅助设备,例如电子笔 150 ,与移动终端连接,从移动终端中取出,同时屏幕 110 关闭移动终端,移动终端可配置为自动切换到锁定图像 120 . 这里,锁定图像是指跟随有移动终端可以使用的等待图像的图像。 也就是说,移动终端可以等待解除安全的指令,例如用户的密码输入。 当用户输入解锁指令时,可以解除移动终端的锁定状态,移动终端可以切换到等待画面,从而执行其操作。 [0014] 图2A和2B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0015] 参考图2A,在内容 210 例如备忘录,当用户通过锁定设置限制他人访问时,移动终端辅助设备的预览功能 150 可以停用图1A的。 也就是说,在设置为锁定的备忘录的情况下,即使有人通过移动终端辅助设备触摸了相应的内容,也可能无法执行预览功能,除非用户输入密码。 [0016] 此外,如图 2B 所示,虽然锁定图像 230 通过从移动终端中取出移动终端辅助设备来显示,同时屏幕 220移动终端关机后,用户只需输入解除安全的指令,如输入密码,即可将终端切换到可用状态,即等待状态。 [0017] 此外,虽然未在附图中示出,但是即使在通过移动终端辅助设备例如电子笔使用移动终端时,如果移动终端没有持续接收到使用指令输入,即触摸信号输入,则屏幕 移动终端的 将很快关闭并恢复安全功能。 [0018] 进一步地,即使用户通过安全过程获得了访问内容的权限或者解除了移动终端的锁定状态,如果移动终端暂时不使用或者需要关机再开机, 用户需要重复安全过程。 发明内容 [0019] 做出本发明以至少解决上述问题和/或缺点并且提供至少下述优点。 相应地,本发明的一个方面提供了一种移动终端辅助设备,在与移动终端连接时,可以通过安全流程进行认证,从而在需要移动终端辅助设备时,可以免去重复的安全流程。 之后使用,从而提高移动终端的可用性。 [0020] 本发明的另一个方面提供了使用应用程序的便利性,仅通过移动终端辅助设备登录或解除锁定状态的过程就可以使用这些应用程序。 [0021] 本发明的另一方面通过使用低功率技术持续检查移动终端的使用而无需额外的额外的,防止移动终端的屏幕在移动终端的使用期间被关闭或锁定状态被恢复 移动终端辅助设备的操作。 [0022] 本发明的另一方面允许,当用户希望使用多个移动终端中的每一个,或者需要认证时,用户通过认证的移动终端辅助设备控制每个移动终端并且在没有安全性的情况下使用移动终端 检查过程,从而提供方便的使用。 [0023] 本发明的另一个方面允许每个移动终端通过相应的移动终端辅助设备来识别用户,并且移动终端的UI被配置有根据设置或用户期望预定义的特定值。 [0024] 根据本发明的一方面,提供了一种移动终端辅助设备的控制方法。 存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息。 判断移动终端辅助设备在预定可用距离内是否存在移动终端。 如果移动终端存在于预定可用距离内,则利用存储的至少一个移动终端的信息判断移动终端是否已经注册。 如果移动终端已经注册,则从存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息被发送到移动终端。 [0025] 根据本发明的另一方面,提供了一种用于控制移动终端的方法。 存储至少一个移动终端辅助设备的信息。 判断移动终端的预定可用距离内是否存在移动终端辅助设备。 如果移动终端辅助设备存在于预定可用距离内,则通过至少一个移动终端辅助设备的信息判断移动终端辅助设备是否已经注册。 如果移动终端辅助设备已经注册,则根据移动终端辅助设备应用预定的安全相关信息。 [0026]根据本发明的另一个方面,提供了一种移动终端辅助设备,包括与至少一个移动终端通信的通信单元,以及存储关于至少一个移动终端的信息和关于移动终端的安全相关信息的存储器。 每个至少一个移动终端。 移动终端辅助设备还包括控制器,判断移动终端是否存在于距离移动终端辅助设备的预定可用距离内,如果移动终端是移动终端,则使用存储在至少一个移动终端上的信息判断移动终端是否已经注册。 终端存在于预定可用距离内,并且控制通信单元将存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息发送到移动终端,如果移动终端具有 已注册。 [0027] 根据本发明的另一方面,提供了一种移动终端,包括与至少一个移动终端辅助设备通信的通信单元,以及存储关于至少一个移动终端辅助设备的信息的存储器。 移动终端还包括控制器,确定移动终端辅助设备是否存在于距移动终端的预定可用距离内,如果是,则使用关于至少一个移动终端辅助设备的信息确定移动终端辅助设备是否已经注册。 移动终端辅助设备存在于预定可用距离内,如果移动终端辅助设备已经注册,则根据移动终端辅助设备控制应用预定安全相关信息。 附图的简要说明 [0028] [0010] 结合附图,通过以下详细描述,本发明的上述和其他方面、特征和优点将更加明显,其中: [0029] 图1A和1B是说明通过使用移动终端辅助设备来操作移动终端的图; [0030] 图2A和2B是说明通过使用移动终端辅助设备来操作移动终端的图; [0031] 图3是示出根据本发明实施例的移动终端辅助设备的框图; [0032] 图4是示出根据本发明实施例的电子笔的框图; [0033] 图5是示出根据本发明实施例的移动终端的框图; [0034] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图; [0035] 图7是示出根据本发明实施例的移动终端的操作的流程图; [0036] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的示图; [0037] 图9A和9B是说明根据本发明实施例的可用距离的图; [0038] 图10是本发明一个实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0039] 图11是本发明另一实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0040] 图12是示出根据本发明实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0041] 图13是示出根据本发明另一实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0042]图14A-14C是根据本发明实施例的判断移动终端辅助设备是否被使用的示意图。 [0043] 图15A-15D是图示根据本发明的实施例的移动终端和移动终端辅助设备的使用的图; [0044] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0045] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0046] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图; 和 [0047] 图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 本发明实施例的详细描述 [0048] 下面结合附图详细描述本发明的实施例。 相同或相似的组件可由相同或相似的附图标记指示,尽管它们在不同的附图中示出。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0049] 在下文中,将参考附图详细描述与本发明相关联的移动终端。 下文描述中所使用的组成元件的后缀,例如“模块”、“单元”,只是为了描述的方便而指定或一起使用,并不具有区分的含义或作用。 [0050] 本发明实施例中描述的移动终端可以实现为便携式电话、智能电话、膝上型计算机、数字广播终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、导航仪 终端等。 然而,对于本领域技术人员显而易见的是,根据本发明的实施例的配置也适用于固定终端,例如数字电视、台式计算机等。 [0051] 本发明实施例的移动终端辅助设备可以包括可以与移动终端通信的电子笔,例如手写笔。 另外,对于本领域技术人员来说显而易见的是,本发明的移动终端辅助装置可以应用于电视、台式电脑等固定终端,也可以应用于移动终端。 [0052] 图3是图示根据本发明实施例的移动终端辅助设备的框图。 [0053] 一种移动终端辅助设备 300 包括一个通信单元 310 , 一段记忆 320 , 和一个控制器 330 . 移动终端辅助设备不限于图3中的元件,还可以包括其他元件,或者可以省略部分元件。 例如移动端辅助设备 300 还可以包括输出单元,例如音频输出模块、警报单元和显示单元,以及用于接收用户输入的用户输入单元。 [0054] 通信单元 310 可以包括至少一个实现移动终端辅助设备之间无线通信的模块 300 和移动终端。 例如,通信单元 310可以包括用于近场通信的短程通信模块。 这里,短距离通信技术可以采用蓝牙、射频识别(RFID)、红外数据协会(IrDA)、超宽带(UWB)、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是蓝牙(BT)模块和蓝牙低功耗(BLE)模块中的至少一种。 [0055] 通信单元 310 可允许移动终端辅助设备 300 移动终端通过与移动终端通信相互注册,如下面更详细的描述。 [0056] 记忆 320 可以存储用于控制器处理和控制的程序 330 并执行暂时存储输入/输出数据(例如,移动终端信息、移动终端识别信息、移动终端辅助设备识别信息、安全相关信息等)的功能。 记忆 320 可以存储数据的使用频率。 [0057] 记忆 320 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,安全数字(SD)存储器、XD存储器等)、随机存储器的至少一种存储介质 存取存储器(RAM)、静态随机存取存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁存储器、磁盘和光盘 . 移动终端辅助设备 300 可关于网络存储操作以提供存储器的存储功能 320 在网上。 [0058] 一般来说,控制器 330 控制移动终端辅助设备的整体操作 300 . 例如,控制器 330 可以控制执行注册移动终端辅助设备的操作 300 和移动终端相互连接。 另外,在使用移动终端辅助设备的情况下 300 通过移动终端与移动终端辅助设备之间的鉴权 300 , 控制器 330 可以控制使用移动终端而无需额外的安全检查过程,这在下面更详细地描述。 [0059] 移动终端辅助设备 300 还可以包括用户输入单元。 用户输入单元生成用于控制用户对移动终端辅助设备的操作的输入数据。 用户输入单元可以包括设置在移动终端辅助设备的前表面、后表面或侧表面上的按钮、触摸传感器(压力型/电容型)、小键盘、圆顶开关、滚轮、滚轮中的至少一个 等,但不限于此。 [0060] 图4是示出根据本发明实施例的电子笔的框图。 [0061] 根据本发明实施例的移动终端辅助设备可以具体化为电子笔 400 ,例如手写笔。 电子笔 400 包括一个通信单元 410 , 一段记忆 420 , 一个控制器 430 , 一个触摸识别单元 440 等,但不限于此。 例如,电子笔 400 还可以包括电源,例如电池 450 ,电源可以接收外部电源和内部电源供应给每个元件以在控制器的控制下运行 430 . 电源可以包括连接端口、电源控制器和充电监控单元中的至少一个,以及电池 450 . [0062] 通信单元 410 可包括至少一个模块,使电子笔之间能够进行无线通信 400 和移动终端。 根据本发明的一个实施例,通信单元 410 可以包括BT模块或BLE模块中的至少一个。 [0063] 通信单元 410 可以让电子笔 400移动终端通过与移动终端通信进行相互注册,如下面更详细的描述。 [0064] 记忆 420 可以存储用于控制器处理和控制的程序 430 并执行临时存储输入/输出数据(例如,关于移动终端的信息、关于移动终端的标识信息、关于移动终端辅助设备的标识信息、安全相关信息等)的功能,如上文详细描述的 . [0065] 一般来说,控制器 430 控制电子笔的整体操作 400 . 例如,控制器 430 可控制执行注册电子笔的操作 400 和移动终端相互连接。 另外,在使用电子笔的情况下 400 通过移动终端与电子笔之间的认证 400 , 控制器 430 可以控制使用移动终端而无需额外的安全检查过程,如下面详细描述的。 [0066] 触摸识别单元 440 可以识别电子笔的触摸信号 400 . 当电子笔的触摸信号 400 是输入,控制器 430 控制根据触摸信号输入执行预定操作。 根据本发明的一个实施例,除了触摸识别单元 440 , 电子笔 400 还可以包括用于生成用户的输入数据的用户输入单元。 用户输入单元可包括设置在电子笔的侧面上的按钮、小键盘、圆顶开关、滚轮、滚轮开关等中的至少一个,但不限于此。 [0067] 图5是图示根据本发明实施例的移动终端的框图。 [0068] 移动终端 500 包括一个通信单元 510 , 一段记忆 520 , 一个控制器 530 , 一个用户输入单元 540 , 和一个输出单元 550 . 图5所示的元件不是移动终端所必需的,移动终端还可以包括其他元件,或者可以省略一些元件。 [0069] 通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 和无线通信系统,或移动终端 500 以及移动终端所在的网络 500 位于。 此外,通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 以及移动终端辅助设备。 例如,通信单元 510 可以包括广播接收模块、移动通信模块、无线上网模块、近距离通信模块、位置信息模块等。 [0070] 广播接收模块通过广播频道从外部广播管理服务器接收广播信号和/或广播相关信息。 广播频道可以包括卫星频道和地面波频道。 移动终端中可以设置至少两个广播接收模块 500 通过至少两个广播频道同时接收广播或者在至少两个广播频道之间切换。 [0071] 移动通信模块向移动通信网络(例如全球移动通信系统(GSM)、码分多址(CDMA) )、宽带码分多址(WCDMA)(但不限于此)。 根据文本/多媒体消息的发送和接收,无线信号可以包括语音呼叫信号、视频呼叫信号或各种数据。 [0072] 移动终端中可以内置无线上网模块,用于连接无线上网 500或外部提供。 无线互联网可能利用无线局域网(WLAN)、Wi-Fi、无线宽带(Wibro)、全球微波接入互操作性(Wimax)、高速下行链路分组接入(HSDPA)、GSM、CDMA、WCDMA、长期 演进(LTE)等。 [0073] 通过 Wibro、HSDPA、GSM、CDMA、WCDMA 和 LTE 的无线互联网连接是由无线移动通信网络实现的。 因此,通过移动通信网络与无线互联网连接的无线互联网模块可以被认为是一种移动通信模块。 [0074] 近距离通信模块是指用于近场通信的模块。 短距离通信技术可以采用BT、RFID、IrDA、UWB、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是BT模块和BLE模块中的至少一种。 [0075] 用户输入单元 540 生成用于控制用户对移动终端的操作的输入数据。 用户输入单元 540 可能包括按钮 543 在移动终端的正面、背面或侧面 500 和触摸传感器(压力式/电容式) 545 . 用户输入单元 540 还可以包括小键盘、圆顶开关、滚轮、滚轮等。 [0076] 输出单元 550 可以产生与视觉、听觉或触觉相关的输出,并且包括显示单元 555 ,但不限于此。 例如,输出单元 550 可以包括音频输出模块、警报模块和触觉模块。 [0077] 显示单元 555 显示(输出)移动端处理的信息 500 . 例如,当移动端 500 处于通话模式时,显示单元 555 显示与电话呼叫相关的用户界面 (UI) 或图形用户界面 (GUI)。 当移动端 500 处于视频通话模式或拍照模式时,显示单元 555 使用 UI 或 GUI 显示拍摄和/或接收的图像。 [0078] 显示单元 555 可以包括液晶显示器(LCD)、薄膜晶体管-LCD(TFT LCD)、有机发光二极管(OLED)、柔性显示器和3D显示器中的至少一种。 [0079] 上述显示器中的一些可以被配置为透明或透光的以通过其观察外部,这被称为透明显示器,典型地包括透明有机发光二极管(TOLED)。 显示单元背面结构 555 也可以配置为透光的。 根据上述结构,用户可以通过显示单元的区域看到终端后面的物体。 555 终端。 [0080] 两个或多个显示单元 555 可根据移动终端类型提供 500 . 例如,多个显示单元可以相互间隔设置,也可以一体设置在同一平面上,也可以设置在移动终端的不同平面上。 500 . [0081] 在显示单元的情况下 555 和触摸传感器 545 ,它们以层结构或一体形成(以下称为“触摸屏”),显示单元 555 既可以作为输入设备,也可以作为输出设备。 触摸传感器可以形成为与显示单元的层压体 555 在例如触摸膜、触摸片、触摸板等的情况下,或者可以与显示单元一体形成 555 . [0082] 触摸传感器可以被配置为转换作用在显示单元的特定部分上的压力变化 555 或显示单元特定部分产生的电容变化 555 到电信号。 触摸传感器可以被配置为检测触摸压力以及触摸点和触摸面积。 [0083]在触摸传感器上有触摸输入时,相应的信号被传输到触摸控制器。 触摸控制器处理信号并将相应的数据传输给控制器 530 . 因此,控制器 530 可以识别显示单元的哪个区域 555 被感动了。 [0084] 虽然未在图中示出,但是接近传感器可以设置在移动终端的触摸屏内部或周围 500 . 接近传感器可以在没有机械接触的情况下通过使用电磁场力或红外线来检测接近预定检测表面的物体或接近传感器周围的物体。 与接触式传感器相比,接近传感器具有较长的使用寿命和多种用途。 [0085] 接近传感器可以包括透明光电传感器、直接反射光电传感器、镜面反射光电传感器、高频振荡接近传感器、电容式接近传感器、磁性接近传感器、红外接近传感器等。 [0086] 在下文中,为了便于解释,术语“接近触摸”可以指指针接近安装有接近传感器的触摸屏从而在没有接触的情况下被识别的操作,术语“接触触摸”可以指代 指针在屏幕上的触摸操作。 指针在触摸屏上的接近触摸点可以表示接近触摸状态下指针在屏幕上垂直对应的位置的点。 在下文中,术语“触摸”可以包括接近触摸以及接触触摸。 [0087] 根据本发明的实施例,接近触摸可以包括悬停输入。 [0088] 接近传感器检测接近触摸和接近触摸模式(例如,接近触摸距离、接近触摸方向、接近触摸速度、接近触摸时间、接近触摸点、接近触摸移动状态等) . 可以在触摸屏上显示与检测到的接近触摸和接近触摸模式相对应的信息。 [0089] 记忆 520 可以存储用于控制器处理和控制的程序 530 并执行临时存储输入/输出数据(例如,电话号码列表、消息、音频、静止图像、运动图像、关于移动终端的信息、关于移动终端的识别信息、关于移动终端辅助设备的信息、 安全相关信息等)。 记忆 520 可以存储数据的使用频率。 [0090] 此外,内存 520 可以存储关于在触摸屏上的触摸输入时输出的各种振动和声音的数据。 [0091] 记忆 520 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,SD存储器、XD存储器等)、RAM、SRAM的至少一种存储介质, ROM、EEPROM、PROM、磁存储器、磁盘和光盘。 手机端 500 可关于网络存储操作以提供存储器的存储功能 520 在网上。 [0092] 手机端 500 还可以包括用于输入音频信号或视频信号的音频/视频(A/V)输入单元,以及用于产生感测信号以感测移动终端的当前状态的感测单元 500 ,例如,移动终端的打开/关闭状态 500 , 移动端的位置 500 、用户的接触、移动终端的方向、移动终端的加减速,从而控制移动终端的操作 500 . [0093] 此外,移动端 500 可以包括接口单元,该接口单元为与移动终端连接的所有外部设备起到通路的作用 500 . 接口单元从外部设备接收数据或电源,并将其传输到移动终端的每个元素 500. 接口单元还允许数据从移动终端传输到外部设备 500 . 例如,接口单元可以包括无线/有线耳机端口、外部充电端口、无线/有线数据端口、存储卡端口、用于连接具有识别模块的设备的端口、音频输入/输出端口(I /O)端口、视频I/O端口、耳机端口等。 [0094] 此外,移动端 500 还可以包括电源,其接收外部电源和内部电源并将其提供给每个元件以在控制器的控制下运行 530 . 电源可以包括例如电池、连接端口、电源控制器和充电监控单元。 [0095] 电池可以是可充电的内置型,并且可以结合到终端的主体以可拆卸地充电。 连接端口可以是外部充电器电连接到的接口之一,以便提供用于电池充电的电力。 [0096] 上述实施例可以通过使用例如软件、硬件或其组合由计算机可读或等效介质来实现。 [0097] 在硬件方面,本发明实施例可以采用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理器件(DSPD)、可编程逻辑器件(PLD)中的至少一种来实现, 现场可编程门阵列 (FPGA)、处理器、控制器、微控制器、微处理器或用于执行其他功能的电气单元。 本发明的一些实施例可以通过控制器来实现 530 . [0098] 在软件方面,本发明实施例的流程和功能可以通过单独的软件模块来实现。 每个软件模块可以执行这里描述的至少一个功能和操作。 软件代码可以由合适的程序语言编写的软件应用程序来实现。 软件代码可以存储在内存中 520 并且可以由控制器执行 530 . [0099] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图。 [0100] 参见图6,在步骤 610 ,移动终端辅助设备的控制器控制将至少一个移动终端的信息存储在存储器中。 即,移动终端辅助设备通过移动终端辅助设备与移动终端之间的注册,存储有至少一个要使用该移动终端辅助设备的移动终端的信息。 当用户试图通过使用移动终端辅助设备连接已注册的移动终端时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0101] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0102] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行鉴权的情况下,控制移动终端辅助设备存储该信息。 移动终端。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入安全信息例如预定密码来识别用户,然后移动终端发送其自身的信息。 将自己的识别信息发送给移动终端辅助设备。 然后,移动终端辅助设备将接收到的移动终端的标识信息存储在存储器中。 [0103]移动终端的信息例如是移动终端的标识或随机生成的固有号码,但不限于此。 [0104] 根据本发明的一个实施例,移动终端辅助设备与移动终端之间的注册由单独的服务器执行。 例如,当移动终端和移动终端辅助设备通过近距离通信连接时,通过输入预定的安全信息来识别用户,然后移动终端辅助设备将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端辅助设备将移动终端的信息发送给服务器,或者移动终端将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 然后,在通过与移动终端或移动终端辅助设备的无线和有线通信使用移动终端或移动终端辅助设备的情况下,服务器发送关于这些设备是否已经注册到彼此的信息。 [0105] 根据本发明的一个实施例,在步骤 610 ,移动终端辅助设备还存储有至少一个移动终端的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端辅助设备存储移动终端设置信息以允许用户根据用户的期望设置移动终端或内容。 [0106] 返回参考图6,在步骤 620 ,移动终端辅助设备的控制器判断在预定可用距离内是否存在移动终端。 根据本发明的实施例,移动终端辅助设备通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端是否存在于预定可用距离内。 信号强度例如是接收信号强度指示符(RSSI)。 [0107] 根据本发明的一个实施例,当检测到使用移动终端辅助设备的信号时,移动终端辅助设备测量信号强度。 例如,当通过包括在移动终端辅助设备中的用户输入单元输入用户指令时,控制器确定移动终端是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0108] 如果移动终端存在于预定可用距离内,则移动终端辅助设备的控制器基于步骤中存储的至少一个移动终端的信息来判断检测到的移动终端是否为已注册的移动终端 610 . 例如,移动终端辅助设备的控制器判断是否在步骤中检测到移动终端的标识信息 620与移动终端辅助设备的存储器中存储的移动终端的标识信息相同。 可选地,控制器判断是否为随机生成的内在数,该内在数存储在步骤检测到的移动终端中 620 与随机生成的固有数相同,存储在移动终端辅助设备的内存中。 [0109] 根据本发明的一个实施例,如果检测到的移动终端是已注册的移动终端,则控制器向移动终端发送安全相关信息,步骤 640 . [0110] 图中示出了安全相关信息存储在移动终端辅助设备中,但本发明不限于此。 例如,移动终端可以在移动终端与移动终端辅助设备注册的过程中存储安全相关信息,步骤 610 . 或者,安全相关信息可以存储在服务器中。 在这种情况下,步骤 640 ,其中安全相关信息被发送到移动终端,可以被省略。 [0111] 图7是示出根据本发明实施例的移动终端的操作的流程图。 [0112] 参见图7,在步骤 710 ,移动终端的控制器控制在存储器中存储关于至少一个移动终端辅助设备的信息。 即,移动终端通过移动终端辅助设备与移动终端之间的注册,存储至少一个移动终端辅助设备的信息,该移动终端辅助设备将与移动终端进行注册。 当用户试图通过使用移动终端辅助设备与移动终端连接时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0113] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0114] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行认证的情况下,控制移动终端将该信息存储在移动终端上。 终端辅助设备。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入预定密码等安全信息来识别用户,然后移动终端辅助设备发送自己的标识 信息到移动终端。 然后,移动终端将接收到的移动终端辅助设备的标识信息存储在存储器中。 [0115] 移动终端辅助设备的信息例如为移动终端辅助设备的标识或随机生成的固有编号,但不限于此。 [0116]根据本发明的一个实施例,移动终端辅助设备和移动终端之间的注册也可以由单独的服务器进行,​​如上面关于图6所描述的。例如,当移动终端和移动终端 辅助设备通过短距离通信相互连接,通过输入预定的安全信息来识别用户,然后移动终端将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端将移动终端辅助设备的信息发送给服务器,或者移动终端辅助设备将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 此外,在通过与移动终端和移动终端辅助设备的无线和有线通信来使用移动终端或移动终端辅助设备的情况下,服务器发送关于设备是否已经相互注册的信息。 [0117] 根据本发明的一个实施例,在步骤 710 ,移动终端还存储有至少一个移动终端辅助设备的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端存储移动终端设置信息以允许用户根据移动终端辅助设备根据用户的期望设置移动终端或内容。 [0118] 再参考图7,在步骤 720 ,移动终端的控制器判断预定可用距离内是否存在移动终端辅助设备。 根据本发明的实施例,移动终端通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端辅助设备是否存在于预定可用距离内。 信号的强度例如是RSSI。 [0119] 根据本发明的一个实施例,当检测到使用移动终端的信号时,由移动终端测量信号强度。 例如,当通过包括在移动终端中的用户输入单元输入用户指令时,控制器确定移动终端辅助设备是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0120] 如果移动终端辅助设备存在于预定可用距离内,则在步骤 730 ,移动终端的控制器根据步骤中存储的至少一个移动终端辅助设备的信息,判断检测到的移动终端辅助设备是否为已注册的移动终端辅助设备 710 . 例如,移动终端的控制器判断是否在步骤中检测到移动终端辅助设备的标识信息 720与移动终端辅助设备的标识信息相同,存储在移动终端的内存中。 或者,控制器判断是否为随机生成的固有数,存储在步骤检测到的移动终端辅助设备中 720 与随机生成的固有数相同,存储在移动终端的内存中。 [0121] 在步 740 ,移动终端应用存储在步骤中的移动终端辅助设备上的安全相关信息 710 . [0122] 图中示出了安全相关信息存储在移动终端中,但本发明不限于此。 根据本发明的一个实施例,移动终端辅助设备或服务器存储移动终端辅助设备的安全相关信息。 若确定步骤中检测到的移动终端辅助设备 720 为注册的移动端辅助设备,在步骤 730 、 移动终端的通信单元接收来自移动终端辅助设备或服务器的安全相关信息。 移动终端的控制器应用接收到的安全相关信息。 [0123] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的图。 图9A和9B是图示根据本发明实施例的可用距离的图。 [0124] 参考图8A,移动终端之间的注册 800 以及移动终端辅助设备 850 被处理。 根据本发明的一个实施例,移动终端辅助设备 850 具体表现为电子笔,包括手写笔。 [0125] 移动端之间的注册 800 以及移动终端辅助设备 850 移动端通信时触发 800 以及移动终端辅助设备 850 首次制作,例如,通过 BT 或 BTLE 模块的短距离通信。 [0126] 根据本发明的一个实施例,移动终端之间的注册过程 800 以及移动终端辅助设备 850 执行,当注册移动终端辅助设备的消息 850 输入到移动端 800 . 注册移动终端辅助设备的消息以弹窗形式显示,但不限于此,消息可以为移动终端按键输入的形式。 [0127] 移动端之间的注册流程 800 以及移动终端辅助设备 850 执行,当移动终端辅助设备通过移动终端认证时 800 通过安全信息对用户进行标识,如图8A所示。 例如,当在移动终端中输入预定密码或特定图案时 800 , 移动端之间的注册 800 以及移动终端辅助设备 850 被处理。 [0128] 移动端之间注册时 800 以及移动终端辅助设备 850 处理完毕,移动端 800 在移动终端辅助设备上存储信息 850 . 移动端 800 接收移动终端的标识信息 800 从移动端辅助设备 850 通过通信单元。 另外,根据本发明的一个实施例,移动终端辅助设备 850 在移动端存储信息 800 . 移动终端辅助设备 850 接收移动终端辅助设备的识别信息 850 从移动端 800 通过通信单元。 或者,根据本发明的一个实施例,移动终端 800以及移动终端辅助设备 850 存储随机生成的相同内在数。 [0129] 根据本发明的一个实施例,移动终端和移动终端辅助设备之间的注册是由单独的服务器进行的,这在上面参考图6和图7进行了详细描述。 [0130] 存储的信息包括移动终端的安全相关信息 800 或移动终端辅助设备 850 . 即该信息中包含解除移动终端锁定状态的密码 800 或移动终端辅助设备 850 、特定应用程序的密码以及电子邮件和 SNS 的登录信息。 例如,当多个移动终端辅助设备 850 已注册到移动终端 800 , 移动端 800 对已注册的移动终端辅助设备的使用进行不同的限制 850 . 即移动端 800 不允许第一移动终端辅助设备访问特定应用,而允许第二移动终端辅助设备访问所有应用。 当第一移动终端辅助设备注册到移动终端时,存储用于限制第一移动终端辅助设备访问特定应用的安全信息。 进一步地,当第二移动终端辅助设备注册到移动终端时,存储允许第二移动终端辅助设备访问所有应用的安全信息。 [0131] 如图8B所示,如果移动终端 800 以及移动终端辅助设备 850 位于预定的可用距离内 870 , 它们可能相互关联。 [0132] 根据本发明的一个实施例,移动终端 800 以及移动终端辅助设备 850 通过通信单元中包含的短距离通信模块测量信号强度,判断移动终端是否 800 以及移动终端辅助设备 850 存在于预定可用距离内 870 基于测量的信号。 测量信号强度,当移动终端辅助设备有信号使用时 850 或移动端 800 根据本发明的实施例,检测到。 [0133] 如图9A所示,移动终端 900 测量移动终端辅助设备的通信信号强度 950 . RSSI 是通过短距离通信模块测量的。 根据本发明的一个实施例,它被配置为即使移动终端 900 以及移动终端辅助设备 950 存在于连接距离内 980 他们之间可以通过短距离通信进行通信,只有当移动终端时,他们才能真正相互连接 900 以及移动终端辅助设备 950 存在于预定的可用距离内 970 . 因此,第二个连接装置 960 无法与移动端连接 900 . [0134] 如图9B所示,由于信号强度根据与移动终端的距离而降低 900 , 判断移动终端辅助设备是否 950 存在于预定可用距离内 970 从移动端 900 通过测量信号的强度。 [0135] 如移动端辅助设备 950 存在于可用距离之外 980 , 移动端 900 以及移动终端辅助设备 950 完全断开连接。 根据本发明实施例,确定移动终端辅助设备 950 丢失,如下面更详细的描述。 [0136] 回到图8B,如果移动终端 800以及移动终端辅助设备 850 存在于预定可用距离内 870 , 移动端 800 以及移动终端辅助设备 850 确定它们是否已经相对于彼此注册,如上文关于图6和图7所述。 [0137] 如果确定移动端 800 以及移动终端辅助设备 850 已经相互注册,移动端 800 基于移动终端上的安全相关信息使用 800 或移动终端辅助设备 850 . [0138] 图10是示出根据本发明实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0139] 根据本发明的一个实施例,移动终端辅助设备体现为包括触摸传感器的电子笔。 在移动终端与移动终端辅助设备接触的情况下,确定移动终端和移动终端辅助设备正在使用中。 [0140] 即使移动终端辅助设备输入了触摸信号,移动终端辅助设备的控制器也无法判断移动终端辅助设备触摸了哪个物体。 也就是说,即使移动终端辅助设备在移动终端以外的物体上进行触摸,然后通过触摸输入单元输入触摸信号,移动终端辅助设备也不能识别物体,而是感应到触摸信号。 只要。 [0141] 同样,当移动终端接收到包括触摸传感器的触摸屏上的触摸信号时,移动终端无法确定是哪个物体触摸了触摸屏。 也就是说,即使是移动终端的触摸屏上的触摸信号,也可能是移动终端辅助设备以外的其他指针,例如手指输入的触摸信号。 在这种情况下,移动终端仅确定触摸点,而不能确定哪个物体产生触摸信号。 [0142] 相应地,为了判断移动终端辅助设备是否被使用,需要预先判断移动终端上的触摸是否是由移动终端辅助设备进行的。 [0143] 参见图10,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1010 . 控制器提取关于触摸信号的检测的时间信息。 [0144] 在步 1020 ,移动终端辅助设备从移动终端接收移动终端检测到触摸信号的时间的触摸时间信息。 即,当触摸信号也输入到移动终端时,移动终端将输入触摸信号的时间信息发送给移动终端辅助设备,移动终端辅助设备接收该信息。 [0145] 在步 1030 ,移动终端辅助设备比较步骤中接收到的移动终端检测到的触摸信号的时间信息 1020 ,带有step的移动终端辅助设备中检测到触摸信号的时间信息 1010 . 即,移动终端辅助设备判断触摸信号在移动终端辅助设备中的输入时间与触摸信号在移动终端中的输入时间是否相同。 [0146] 如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间不同,则确定输入到移动终端辅助设备的触摸信号是触摸产生的,而不是触摸产生的。 移动终端,而是其他带有移动终端辅助设备的对象。 [0147]如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间相同,则控制器确定移动终端辅助设备触摸到移动终端,进而移动终端。 辅助设备正在使用中。 [0148] 此外,虽然未在图中示出,但是根据本发明的实施例,移动终端辅助设备将确定结果发送到移动终端。 [0149] 图11是示出根据本发明另一实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0150] 参见图11,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1110 . 控制器提取关于触摸信号检测的时间信息。 [0151] 在步 1120 ,移动终端辅助设备将检测到触摸信号的时间信息发送给移动终端。 另外,移动终端辅助设备从移动终端接收移动终端辅助设备是否触摸移动终端的信息,步骤 1130 . [0152] 在图11的实施例中,与图10的实施例不同的是,移动终端判断移动终端辅助设备是否被使用过。 另外,移动终端用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端辅助设备。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端被配置为不向移动终端辅助设备发送单独的响应信号。 [0153] 移动终端辅助设备在步骤中利用接收到的信息判断移动终端辅助设备是否已经针对移动终端使用过 1130 . [0154] 图12是示出根据本发明实施例的确定移动终端辅助设备是否被移动终端使用的流程图。 [0155] 参见图12,移动终端检测针对移动终端的触摸信号,步骤 1210 . 控制器提取关于触摸信号的检测的时间信息。 [0156] 在步 1220 ,移动终端从移动终端辅助设备接收到移动终端辅助设备检测到触摸信号的时间信息。 即,当移动终端辅助设备也输入了触摸信号时,移动终端辅助设备向移动终端发送触摸信号输入时间的信息,移动终端接收该信息。 [0157] 在步 1230 ,移动终端比对步骤中接收到的移动终端辅助设备检测到的触摸信号的时间信息 1220 , 与检测移动终端辅助设备触摸信号的时间信息同步 1210 . 即移动终端可以判断触摸信号在移动终端中的输入时间与触摸信号在移动终端辅助设备中的输入时间是否相同。 [0158] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间不同,则确定移动终端辅助设备中的触摸信号是触摸产生的,而不是移动终端产生的。 终端,而是与移动终端辅助设备的其他对象。 [0159] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间相同,则移动终端的控制器确定移动终端辅助设备触摸了移动终端, 步骤 1240,则该移动终端辅助设备正在使用中。 [0160] 此外,根据本发明的实施例,移动终端将确定结果发送到移动终端辅助设备。 [0161] 图13是示出根据本发明另一实施例的确定移动终端是否辅助移动终端的流程图。 [0162] 参见图13,移动终端检测移动终端的触摸信号,步骤 1310 . 此时,控制器提取触摸信号检测的时间信息。 [0163] 在步 1320 ,移动终端将检测到触摸信号的时间信息发送给移动终端辅助设备。 另外,移动终端从移动终端辅助设备接收移动终端辅助设备是否触摸了移动终端的信息,步骤 1330 . [0164] 在图13的实施例中,与图12的实施例不同的是,移动终端辅助设备判断移动终端辅助设备是否被使用过。 另外,移动终端辅助设备用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端辅助设备被配置为不向移动终端发送单独的响应信号。 [0165] 移动终端利用接收到的信息判断移动终端辅助设备是否针对移动终端使用过, 1330 . [0166] 图14A-14C是图示根据本发明实施例的确定移动终端辅助设备是否已经被使用的图。 [0167] 参见图14A,移动终端辅助设备 1450 移动终端屏幕进入预定可用距离内 1400 被关闭。 移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于预定的可用距离内。 比如移动端 1400 通过与移动终端辅助设备的近距离通信测量RSSI 1450 , 判断移动端辅助设备是否 1450 基于信号的测量强度,存在于预定可用距离内。 [0168] 即使是移动端 1400 以及移动终端辅助设备 1450 存在于预定的可用距离内,根据本发明的一个实施例,移动终端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 仅当移动终端辅助设备存在于预定可用距离内时 1450 正在使用中。 [0169] 如图14B所示,根据参考图10至图13描述的方法确定移动终端辅助设备的使用。 [0170] 例如,当移动终端辅助设备 1450 触摸移动终端 1400 , 移动端辅助设备 1450 检测触摸信号。 移动终端辅助设备 1450 提取触摸信号检测的时间信息。 此外,移动终端 1400 还提取移动终端辅助设备触摸时检测到触摸信号的时间信息 1450 . [0171] 移动终端辅助设备 1450 传输检测到移动终端辅助设备触摸信号的信​​息 1450 到手机端 1400. 或者,根据本发明的一个实施例,移动终端 1400 传输检测到移动终端触摸信号的信​​息 1400 到移动端辅助设备 1450 . [0172] 手机端 1400 比较触摸信号输入到移动终端辅助设备的时间 1450 ,从移动终端辅助设备接收 1450 , 随着触摸信号输入到移动端的时间 1400 . 或者,根据本发明的一个实施例,移动终端辅助设备 1450 比较触摸信号输入到移动端的时间 1400 , 从移动端接收 1400 , 随着触摸信号输入到移动终端辅助设备的时间 1450 . [0173] 如果触摸信号输入到移动终端 1400 以及移动终端辅助设备 1450 同时,移动端的控制器 1400 或移动终端辅助设备 1450 确定移动终端辅助设备 1450 触动了移动端 1400 . [0174] 随后,移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 和移动端 1400 ,它们存在于预定的可用距离内,已经相对于彼此注册。 如果确定移动端 1400 以及移动终端辅助设备 1450 已经相对于彼此注册,如图14C所示,移动终端 1400 可以通过应用预定的安全相关信息将其转为使用状态。 [0175] 根据本发明的一个实施例,移动终端后 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于可用距离内,若移动终端辅助设备 1450 存在于可用距离内,判断是否存在移动终端辅助设备 1450 正在使用中。 [0176] 例如,即使是移动终端辅助设备 1450 在移动终端的可用距离内被检测到 1400 ,如果是移动端辅助设备 1450 未使用时,无需判断是否为移动终端辅助设备 1450 已注册。 反之,如果移动终端辅助设备 1450 正在使用中,应判断是否为移动终端辅助设备 1450 已注册。 据此,移动终端 1400 判断移动端辅助设备是否 1450 判断是否为移动终端辅助设备后注册的 1450 是否存在于可用距离内以及检测到的移动终端辅助设备是否存在 1450 正在使用中。 [0177] 图15A-15D是图示根据本发明实施例的移动终端和移动终端辅助设备的使用的图。 [0178] 参考图15A,一个用户针对一个移动终端使用一个移动终端辅助设备。 用户根据他或她的需要配置移动终端。 相应地,在移动终端与移动终端辅助设备之间的注册过程中,可以将包括移动终端的设置信息在内的安全相关信息存储在移动终端或移动终端辅助设备中。 之后,当用户通过移动终端辅助设备使用移动终端时,根据预先存储的设置信息对移动终端进行配置,从而使用户能够方便地使用移动终端。 [0179]或者,如图15B所示,一个用户可以通过使用一个移动终端辅助设备来使用多个移动终端。 用户在多个移动终端上使用具有一致性的特定信息。 因此,根据本发明的实施例,用户在移动终端辅助设备中存储他或她想要的包括设置信息的安全信息。 另外,当用户从第一移动终端切换到第二移动终端时,用户根据存储在移动终端辅助设备中的设置信息配置和使用第二移动终端。 [0180] 如图15C所示,多个用户通过各自的移动终端辅助设备使用一个移动终端。 用户在保护隐私的同时与其他用户共享移动终端的内容。 相应地,每个用户在移动终端辅助设备中存储包括密码的安全相关信息,该密码防止其他人查看他或她在移动终端中的私人信息。 备选地,可以配置为将安全相关信息存储在移动终端中,并且仅当预定的移动终端辅助设备与移动终端连接时才去激活安全。 [0181] 如图15D所示,多个用户通过多个移动终端辅助设备使用多个移动终端。 在这种情况下,用户在多个移动终端上使用一致的特定信息,并在保护隐私的同时与其他用户共享移动终端的内容。 在这种情况下,每个用户在移动终端辅助设备中存储安全相关信息,包括他或她想要的设置信息和防止其他人查看他或她在移动终端中的私人信息的密码。 根据本发明实施例,安全相关信息存储在移动终端中。 [0182] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图。 [0183] 参见图16,在步骤 1610 ,移动终端辅助设备判断注册的移动终端是否存在预定的连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0184] 如果预定连接距离内不存在移动终端,则确定移动终端辅助设备与移动终端断开连接,移动终端辅助设备删除内存中存储的移动终端信息, 步骤 1630 . [0185] 根据本发明的一个实施例,当确定在连接距离内不存在已注册的移动终端时,移动终端辅助设备判断在预定断开参考时间内是否检测到移动终端,步骤 1620 . 即,移动终端辅助设备判断移动终端是否在预定断开参考时间内不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端,则移动终端辅助设备删除正在运行的移动终端的信息 1630 . [0186] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除移动终端辅助设备中存储的第一移动终端的信息。 [0187]然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 此时,移动终端辅助设备在第一移动终端断开连接后,判断第二移动终端是否连接断开参考时间 1620 . 判断结果为,如果第二移动终端在预定的参考时间内连接上,则移动终端辅助设备不删除第一移动终端的信息,而是保留第一移动终端的信息。 [0188] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户使用多个移动终端的流程图。 [0189] 参见图17,在步骤 1710 ,移动终端判断注册的移动终端辅助设备是否存在预定连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定的连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0190] 若预定连接距离内不存在移动终端辅助设备,则确定移动终端辅助设备与移动终端断开连接,移动终端删除内存中存储的移动终端辅助设备信息, 步 1730 . [0191] 根据本发明的一个实施例,当确定连接距离内不存在已注册的移动终端辅助设备时,移动终端判断是否在预定断开参考时间内检测到移动终端辅助设备。 也就是说,移动终端可以判断在预定断开参考时间内移动终端辅助设备是否不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端辅助设备,则移动终端删除正在运行的移动终端辅助设备的信息 1730 . [0192] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除第一移动终端中存储的移动终端辅助设备信息。 [0193] 然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 第一移动终端在与第一移动终端断开后,判断移动终端辅助设备是否与第二移动终端连接,步骤 1720 . 判断结果为,若移动终端附属设备与第二移动终端连接,则第一移动终端不删除,而是保留移动终端附属设备的信息。 [0194]第一移动终端从服务器接收移动终端辅助设备是否与第二移动终端连接的信息。 也就是说,当移动终端辅助设备与至少一个移动终端相互注册时,服务器存储至少一个移动终端与移动终端辅助设备的注册状态信息。 另外,移动终端或移动终端辅助设备周期性或特定事件发生时,向服务器发送移动终端辅助设备与哪个移动终端连接以及移动终端辅助设备是否在使用中的信息。 进一步地,服务器存储接收到的移动终端辅助设备和移动终端的使用状态信息。 [0195] 如果确定移动终端辅助设备与所有移动终端断开连接,不再使用,根据本发明实施例,移动终端和移动终端辅助设备的注册状态信息 被删除。 根据本发明的一个实施例,服务器向移动终端或移动终端辅助设备发送注销指令。 之后,接收到注销指令的移动终端或移动终端附属设备删除存储在移动终端附属设备或移动终端上的信息。 [0196] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图。 [0197] 参考图18,服务器 1830 管理移动终端辅助设备相互注册信息 1850 以及至少一台移动终端 1810 和/或 1820 . [0198] 移动终端辅助设备 1850 离开第二移动终端的可用距离区域 1820 , 而移动端辅助设备 1850 与第二移动终端结合使用 1820 . 随后,移动终端辅助设备 1850 进入第一移动终端的可用距离区域 1810 与第一移动终端连接 1810 用来。 [0199] 移动终端 1810 和 1820 传输是否与移动终端辅助设备连接的信息 1850 到服务器 1830 . 服务器 1830 从移动终端接收关于连接状态的信息 1810 和 1820 , 并存储相同的。 [0200] 根据本发明的一个实施例,第二移动终端 1820 接收到移动终端辅助设备的信息 1850 与第二移动终端断开连接 1820 , 但它与第一​​移动终端连接 1810 , 从服务器 1830 . 即第二移动终端 1820 确定移动终端辅助设备 1850 未丢失但与第一移动终端连接 1810 在使用中。 因此,第二移动终端 1820 不删除但维护移动终端辅助设备上的信息 1850 . [0201] 然而,虽然未在图中示出,但是当移动终端辅助设备 1850 连第一个移动终端都没有连接 1810 , 第二移动端 1820 接收到移动终端辅助设备的信息 1850 从服务器断开所有移动终端 1830 . 第二移动终端 1820 确定移动终端辅助设备 1850 丢失了。 第二移动终端 1820 删除移动终端辅助设备信息 1850 以及与安全相关的信息。 第一个移动终端 1820 同时删除移动端辅助设备信息 1850 以及与安全相关的信息。 [0202]图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 [0203] 参见图19,移动终端辅助设备 1950 管理关于至少一个移动终端的注册信息 1910 或者 1920 . [0204] 移动终端辅助设备 1950 确定与移动终端的连接状态 1910 和 1920 . [0205] 例如移动端辅助设备 1950 离开第二移动终端的可用距离区域 1920 而移动终端辅助设备 1950 与第二移动终端结合使用 1920 . 随后,移动终端辅助设备 1950 进入第一移动终端的可用距离区域 1910 从而与第一移动终端连接 1910 用来。 [0206] 根据本发明的一个实施例,移动终端辅助设备 1950 判断移动端辅助设备是否 1950 与第一移动终端连接 1910 在预定的断开时间内。 即如果移动终端辅助设备 1950 与第二移动终端断开连接 1920 , 并与第一移动终端相连 1910 , 移动端辅助设备 1950 不认为丢失。 据此,移动终端辅助设备 1950 不删除但维护移动终端上的信息 1910 和 1920 以及与安全相关的信息。 [0207] 然而,当移动终端辅助设备 1950 连第一个移动终端都没有连接 1910 , 移动端辅助设备 1950 因未与任何移动终端连接,确定丢失。 移动终端辅助设备 1950 删除手机端信息 1910 和 1920 ,以及与安全相关的信息。 [0208] 根据本发明的一个实施例,在移动终端中注册移动终端辅助设备时,可以将电子邮件、SNS等应用程序的账户信息存储在移动终端辅助设备的内存中。 移动终端辅助设备在使用移动终端时,移动终端辅助设备可以将存储的账户信息发送给移动终端。 移动终端可以根据接收到的账号信息,自动登录对应的账号,无需输入登录密码。 [0209] 或者,根据本发明的一个实施例,移动终端辅助设备存储移动终端锁定状态解除的信息。 此时,在通过移动终端辅助设备的特定按键开启移动终端的显示单元,并通过移动终端辅助设备触摸移动终端的显示单元的情况下,移动终端可以 无需输入密码即可转换为等待模式。 [0210] 另外,根据本发明的一个实施例,在移动终端和移动终端辅助设备在使用过程中持续测量RSSI,从而可以判断移动终端辅助设备是否存在于预定的可用距离内。 如果判断结果为移动终端辅助设备在可用距离内,则确定移动终端辅助设备正在使用中,从而可以控制移动终端的显示单元保持开启。 [0211] 根据本发明的一个实施例,在使用移动终端进行支付时,使用已注册的移动终端辅助设备可以很容易地批准支付,或者只有通过签名等安全过程才能批准支付。 通过已注册的移动终端辅助设备进行。 [0212]此外,根据本发明的一个实施例,通过输入单元放大或缩小显示在移动终端的显示单元上的特定对象,例如移动终端辅助设备上的按钮。 [0213] 此外,根据本发明的实施例,所描述的方法可以通过记录有程序的记录介质中的计算机可读代码来实现。 计算机可读介质包括其中存储有计算机系统可读数据的所有类型的记录设备。 计算机可读记录介质可以包括ROM、RAM、CD-ROM、磁带、软盘、光学数据存储器等。 计算机可读记录介质可以以载波的形式实现(例如,通过互联网传输)。 计算机可以包括终端的控制器或移动终端辅助设备的控制器。 [0214] 对于本领域的技术人员来说显而易见的是,在不脱离本发明的范围和本质特征的情况下可以进行各种修改。 [0215] 虽然本发明已参照其某些实施例进行了展示和描述,但本领域技术人员将理解,在不脱离本发明所定义的精神和范围的情况下,可以在其中进行形式和细节的各种改变 附加索赔。(String), 111523(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), KR1020150041337A(String), 1046977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), KR102138034B1(String), 1046978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), US20150099486A1(String), 1046979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270635(Integer), US9749858B2(String), 1046980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9749858B2(String), US9749858B2(String), 1503936000(Integer), 270635(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184952(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.217 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\6de7864c13fe4f3e98c1b83ec62e8a0a.png(String), 184953(Integer), 6de7864c13fe4f3e98c1b83ec62e8a0a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Multi-standby mobile terminal and method of performing conference call using the same(String), 多待移动终端及使用该移动终端进行电话会议的方法(String), US20090186607A1(String), A multi-standby mobile terminal and a method for performing a conference call using the same are provided. The method of performing a conference call includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal, requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network, and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 提供了一种多待移动终端和使用该多待移动终端进行电话会议的方法。 执行电话会议的方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端是多待移动终端,通过第三者请求与第二移动终端的通信。 移动终端存在于第二无线通信网络中,并且通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议,当 通信请求为电话会议请求,将合成声音信号发送给第三移动终端。(String), US12/346068(String), 1230566400(Integer), US20090186607A1(String), 1248278400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 9(Integer), US20030072421A1 | US20030092433A1 | US20060291419A1 | US20070082699A1 | US20070111743A1 | US20090291675A1 | US6904023B2 | US7869806B2 | US8244228B1(String), \20230420\6de7864c13fe4f3e98c1b83ec62e8a0a.png(String), 20(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 1. A multi-standby mobile terminal comprising:a first communication module for forming a communication channel with a first wireless communication network;a second communication module for forming a communication channel with a second wireless communication network; anda first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and for outputting the synthesized sound signal to the second communication module.(String), 1.一种进行电话会议的方法,该方法包括:连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端包括多待移动终端;通过存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信;和当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成为第二移动终端的第一混音器中的合成声音信号来执行电话会议,以及将合成后的声音信号发送给第三移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 2. The multi-standby mobile terminal of claim 1, further comprising a second audio mixer for synthesizing sound signals, input from the first communication module and the second communication module, to a synthesized sound signal, and outputting the synthesized sound signal to a speaker.(String), 12.如权利要求11所述的方法,其中电话会议的执行还包括如果第一移动终端和第二移动终端之间的通信终止,则终止第三混音器的功能。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 3. The multi-standby mobile terminal of claim 2, further comprising a third audio mixer for synthesizing sound signals, input from the second communication module and the microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the first communication module.(String), 13.如权利要求11所述的方法,其中进行电话会议还包括将从第一移动终端和第三移动终端输入的声音信号合成为第二移动终端的第二混音器中的合成声音信号,并将合成声音信号输出到第二移动终端的扬声器移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 4. The multi-standby mobile terminal of claim 1, further comprising:a first antenna for transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and for receiving a frequency to be used for the GSM wireless communication network; anda second antenna for transmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and for receiving a frequency to be used for the CDMA wireless communication network.(String), 14.如权利要求11所述的方法,还包括:通过全球移动通信系统(GSM)无线通信网络发送和接收声音信号和数据,并接收用于GSM无线通信网络的频率;和通过码分多址(CDMA)无线通信网络发送和接收声音信号和数据,以及接收要用于CDMA无线通信网络的频率。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 5. The multi-standby mobile terminal of claim 4, wherein the first communication module forms the communication channel with the GSM wireless communication network and transmits and receives a wireless signal to and from a first mobile terminal.(String), 15.如权利要求14所述的方法,其中第一无线通信网络包括GSM无线通信网络并且向第一移动终端发送无线信号以及从第一移动终端接收无线信号。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 6. The multi-standby mobile terminal of claim 4, wherein the second communication module forms the communication channel with the CDMA wireless communication network and transmits and receives a wireless signal to and from a third mobile terminal.(String), 16.如权利要求14所述的方法,其中第二无线通信网络包括CDMA无线通信网络并且向第三移动终端发送无线信号以及从第三移动终端接收无线信号。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 7. The multi-standby mobile terminal of claim 5, wherein the first communication module demodulates a wireless signal received from the first mobile terminal and modulates the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 17.如权利要求15所述的方法,还包括对从第一移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第三移动终端的合成声音信号进行调制。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 8. The multi-standby mobile terminal of claim 6, wherein the second communication module demodulates a wireless signal received from the third mobile terminal and modulates a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 18.如权利要求16所述的方法,还包括对从第三移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第一移动终端的合成声音信号进行调制。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 9. The multi-standby mobile terminal of claim 3, further comprising a controller for terminating a function of the first audio mixer, if communication through the second communication module terminates.(String), 19.如权利要求13所述的方法,其中进行电话会议包括将从第二移动终端和第三移动终端输入的声音信号在第二移动终端的第三混音器中合成为合成声音信号,并将合成声音信号发送给第一移动终端。(String), 1(Integer), 8(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 10. The multi-standby mobile terminal of claim 9, wherein the controller terminates a function of the third audio mixer, if communication through the first communication module terminates.(String), 20.如权利要求19所述的方法,其中电话会议的执行还包括如果第二移动终端和第三移动终端之间的通信终止,则终止第一混音器的功能。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 11. A method for performing a conference call, the method comprising:connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal comprises a multi-standby mobile terminal;requesting communication with the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; andperforming a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 12. The method of claim 11, wherein the performing of the conference call further comprises terminating a function of the third audio mixer, if communication between the first mobile terminal and the second mobile terminal terminates.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 13. The method of claim 11, wherein the performing of the conference call further comprises synthesizing sound signals input from the first mobile terminal and the third mobile terminal, to a synthesized sound signal in a second audio mixer of the second mobile terminal and outputting the synthesized sound signal to a speaker of the second mobile terminal.(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 14. The method of claim 11, further comprising:transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and receiving a frequency to be used for the GSM wireless communication network; andtransmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and receiving a frequency to be used for the CDMA wireless communication network.(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 15. The method of claim 14, wherein the first wireless communication network comprises the GSM wireless communication network and transmits and receives a wireless signal to and from the first mobile terminal.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 16. The method of claim 14, wherein the second wireless communication network comprises the CDMA wireless communication network and transmits and receives a wireless signal to and from the third mobile terminal.(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 17. The method of claim 15, further comprising demodulating a wireless signal received from the first mobile terminal and modulating the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 18. The method of claim 16, further comprising demodulating a wireless signal received from the third mobile terminal and modulating a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 19. The method of claim 13, wherein the performing of the conference call comprises synthesizing sound signals input from the second mobile terminal and the third mobile terminal, to a synthesized sound signal in a third audio mixer of the second mobile terminal and transmitting the synthesized sound signal to the first mobile terminal.(String), 1(Integer), 18(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184953(Integer), 20. The method of claim 19, wherein the performing of the conference call further comprises terminating a function of the first audio mixer, if communication between the second mobile terminal and the third mobile terminal terminates.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111524(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184953(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Jan. 17, 2008 in the Korean Intellectual Property Office and assigned Serial No. 10-2008-0005296, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same. More particularly, the present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same that enable a communication connection between several mobile terminals existing in different wireless communication networks. [0004]2. Description of the Related Art [0005]Due to rapid technology development, mobile terminals having various functions, such as voice communication, short message service, audiovisual communication, an electronic scheduler and Internet, are now available. A multi-standby mobile terminal that can perform a communication connection with two or more wireless communication networks, such as a dual-standby mobile terminal that supports a Code Division Multiple Access (CDMA) wireless communication network and a Global System for Mobile communication (GSM) wireless communication network, is now provided. The dual-standby mobile terminal may be in a communication standby state in both a CDMA wireless communication network service area and a GSM wireless communication network service area. That is, in a state where the dual-standby mobile terminal is connected for communication with a mobile terminal using a CDMA wireless communication network, the dual-standby mobile terminal can receive a communication request from a mobile terminal using a GSM wireless communication network and be connected with the mobile terminal for communication. [0006]A mobile terminal service provider provides, as an additional service, a conference call function in which several persons can simultaneously form a communication channel and perform a phone conference. [0007]A conventional multi-standby mobile terminal cannot perform a conference call. However, the conventional multi-standby mobile terminal can only perform simultaneous standby and individual communication with mobile terminals using different wireless communication networks. [0008]Therefore, a need exists for a method and apparatus that enable a multi-standby mobile terminal to perform a conference call using different wireless communication networks. SUMMARY OF THE INVENTION [0009]An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a multi-standby mobile terminal and a method for performing a conference call using the same that enable mobile terminals in different wireless communication networks to perform a conference call. [0010]In accordance with an aspect of the present invention, a multi-standby mobile terminal is provided. The mobile terminal includes a first communication module for forming a communication channel with a first wireless communication network, a second communication module for forming a communication channel with a second wireless communication network, and a first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the second communication module. [0011]In accordance with another aspect of the present invention, a method of performing a conference call is provided. The method includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal; requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal. [0012]Other aspects, disadvantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0014]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention; [0015]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention; and [0016]FIG. 3 is a flowchart illustrating a method for performing a conference call according to an exemplary embodiment of the present invention. [0017]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0018]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0019]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0020]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0021]In the following description, a dual-standby mobile terminal that can perform a communication connection with a CDMA wireless communication network and a GSM wireless communication network, such as a multi-standby mobile terminal, are described. However, the present invention is not limited thereto. That is, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a communication connection with various wireless communication networks, such as a General Packet Radio Service (GPRS), an Enhanced Data GSM Environment (EDGE), a Universal Mobile Telecommunications System (UMTS) and a Wideband Code Division Multiple Access (WCDMA). [0022]A configuration of a multi-standby mobile terminal according to an exemplary embodiment of the present invention and a method of performing a conference call using the multi-standby mobile terminal are described with reference to the accompanying drawings. [0023]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0024]Referring to FIG. 1, a first mobile terminal 100 is a mobile terminal for supporting a GSM wireless communication network 150, a third mobile terminal 300 is a mobile terminal for supporting a CDMA wireless communication network 350 and a second mobile terminal 200 is a multi-standby mobile terminal for supporting both the GSM and CDMA wireless communication networks 150 and 350. The first mobile terminal 100 and the third mobile terminal 300 may also be a multi-standby mobile terminal. [0025]In the following description, in a state where the first mobile terminal 100 and the second mobile terminal 200 are connected for communication, if the third mobile terminal 300 requests communication between several persons, it is assumed that the second mobile terminal 200 may perform a conference call function. That is, in a state where the second mobile terminal 200 and the first mobile terminal 100 are connected for communication using the GSM wireless communication network 150, the third mobile terminal 300 may request, through the CDMA wireless communication network 350, communication between several persons to the second mobile terminal 200. Alternatively, the second mobile terminal 200 may request communication between several persons to the third mobile terminal 300. In this case, a conference call function of the second mobile terminal 200 is activated. Thus, communication between the first mobile terminal 100, the second mobile terminal 200 and the third mobile terminal 300 may be performed. [0026]A conference call function of the second mobile terminal 200 is described later with reference to FIG. 2. [0027]When a conference call function is activated, if a sound signal of the first mobile terminal 100 is transmitted to the second mobile terminal 200, the second mobile terminal 200 synthesizes its own sound signal and a sound signal of the first mobile terminal 100 using an audio mixer and transmits the synthesized sound signal to the third mobile terminal 300. That is, the third mobile terminal 300 may receive sound signals of the second mobile terminal 200 and the first mobile terminal 100 through the synthesized sound signal. [0028]Similarly, if a sound signal of the third mobile terminal 300 is transmitted to the second mobile terminal 200, the second mobile terminal 200 may synthesize its own sound signal and a sound signal of the third mobile terminal 300 using an audio mixer. The second mobile terminal 200 then transmits the synthesized sound signal to the first mobile terminal 100. That is, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300 through the synthesized sound signal. [0029]The second mobile terminal 200 synthesizes a sound signal transmitted from the first mobile terminal 100 and a sound signal transmitted from the third mobile terminal 300 using the audio mixer and outputs the synthesized sound signal through a speaker (SPK) of the second mobile terminal 200. Thereby, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300, the second mobile terminal 200 may receive sound signals of the first mobile terminal 100 and the third mobile terminal 300, and the third mobile terminal 300 may receive sound signals of the first mobile terminal 100 and the second mobile terminal 200. Thus, a conference call may be performed. [0030]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0031]FIG. 2 illustrates, as the multi-standby mobile terminal 200 according to an exemplary embodiment of the present invention, a dual-standby mobile terminal that may perform a communication connection with the GSM wireless communication network and the CDMA wireless communication network. However, the multi-standby mobile terminal of the present invention is not limited to the dual-standby mobile terminal. [0032]The dual-standby mobile terminal may have slots in which a CDMA card and a GSM card are mounted or one slot for mounting a dual card in which a CDMA card and a GSM card are integrated. [0033]Referring to FIG. 2, a dual-standby mobile terminal (hereinafter, the second mobile terminal 200) according to an exemplary embodiment of the present invention includes a first antenna 401, a second antenna 402, a first communication module 410, a second communication module 420, a controller 450 and an audio mixer 460 including a first audio mixer 461, a second audio mixer 462 and a third audio mixer 463. [0034]The first antenna 401 transmits and receives a sound signal and data through the GSM wireless communication network 150 and receives a frequency to be used for the GSM wireless communication network 150. [0035]The second antenna 402 transmits and receives a sound signal and data through the CDMA wireless communication network 350 and receives a frequency to be used for the CDMA wireless communication network 350. [0036]FIG. 2 illustrates the first antenna 401 and the second antenna 402 as separate antennas. However the first antenna 401 and the second antenna 402 may be formed as one antenna. When the first antenna 401 and the second antenna 402 are formed as one antenna, the dual-standby mobile terminal 200 includes a means for dividing a frequency band into a CDMA frequency band and a GSM frequency band. For example, the dual-standby mobile terminal 200 divides a signal received by the antenna using a duplexer (not shown) into signals of a CDMA frequency band and signals of a GSM frequency band. The dual-standby mobile terminal 200 transmits the signal of the GSM frequency band to the first communication module 410 and the signal of the CDMA frequency band to the second communication module 420. [0037]The first communication module 410 and the second communication module 420 each include a transmission/reception signal divider (not shown) for dividing a transmission/reception signal, a Radio Frequency (RF) transmitter (not shown) for up-converting a frequency of a signal to be transmitted and amplifying the signal, an RF receiver (not shown) for low-noise amplifying a received signal and down-converting a frequency of the signal and a modem for modulating and demodulating a sound signal. [0038]Hereinafter, for convenience of description, it is assumed that the first communication module 410 forms a communication channel with the GSM wireless communication network 150 and transmits and receives a wireless signal to and from the first mobile terminal 100 using a GSM wireless communication method. Also, the second communication module 420 forms a communication channel with the CDMA wireless communication network 350 and transmits and receives a wireless signal to and from the third mobile terminal 300 using a CDMA wireless communication method. [0039]The first communication module 410 demodulates a wireless signal received from the first mobile terminal 100 and modulates a sound signal input from a microphone (MIC) of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the first communication module 410 modulates a sound signal of the second mobile terminal 200 and a sound signal of the third mobile terminal 300 synthesized in the audio mixer 460 and transmits the modulated sound signal to the first mobile terminal 100. [0040]The second communication module 420 demodulates a wireless signal received from the third mobile terminal 300 and modulates a sound signal input from the MIC of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the second communication module 420 modulates a sound signal of the second mobile terminal 200 and a sound signal of the first mobile terminal 100 synthesized in the audio mixer 460 and transmits the modulated sound signal to the third mobile terminal 300. [0041]The controller 450 controls general operations of the second mobile terminal 200 and a signal flow of elements of the second mobile terminal 200. More particularly, the controller 450 controls the first communication module 410 and the second communication module 420. In more detail, the controller 450 controls the first communication module 410 and the second communication module 420 to perform a communication connection with the GSM communication network 150 and CDMA communication network 350, respectively. When a communication connection request is received by the first communication module 410 or the second communication module 420, the controller 450 activates the corresponding first communication module 410 or second communication module 420 to perform communication. [0042]Further, in a state where the first mobile terminal 100 and the second mobile terminal 200 perform communication through the GSM wireless communication network 150, if the third mobile terminal 300 requests communication between several persons through the CDMA wireless communication network 350, the controller 450 of the second mobile terminal 200 performs a conference call function. If a communication request received from the third mobile terminal 300 is not a request for communication between several persons, the controller 450 performs an individual communication function. That is, in order to perform individual communication with the third mobile terminal 300, the controller 450 terminates functions other than a communication connection function of the first communication module 410. Further, the controller 450 controls the audio mixer 460 to block transmission and reception of a sound signal to and from the first mobile terminal 100. [0043]Similarly, in order to perform individual communication with the first mobile terminal 100, the controller 450 terminates functions other than a communication connection function of the second communication module 420, and blocks transmission and reception of a sound signal to and from the third mobile terminal 300. [0044]The controller 450 may perform a conference call function for activating both the first communication module 410 and the second communication module 420. Specifically, when the controller 450 activates both the first communication module 410 and the second communication module 420, a sound signal of the first mobile terminal 100 is modulated in the second mobile terminal 200, the modulated sound signal is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the third mobile terminal 300. Likewise, a sound signal of the third mobile terminal 300 is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the first mobile terminal 100. Thereby, a conference call for voice communication between mobile terminals in different wireless communication networks is performed. [0045]When the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0046]While performing a conference call, when communication with either the first mobile terminal 100 or the third mobile terminal 300 terminates, the controller 450 controls a conference call termination function of the audio mixer 460. A detailed description thereof is described later. [0047]The controller 450 may be included in the first communication module 410 or in the second communication module 420. In this case, the communication module 410 or 420 including the controller 450 becomes a main communication module and controls signal flows of the entire system, including the signal flows of another communication module. [0048]When performing a conference call, the first audio mixer 461 synthesizes a sound signal of the first mobile terminal 100 received from the first communication module 410 and a sound signal received from the MIC of the second mobile terminal 200. The first audio mixer 461 outputs the synthesized sound signal to the second communication module 420. The synthesized sound signal output to the second communication module 420 is modulated and transmitted to the third mobile terminal 300 via the second antenna 402. That is, when performing a conference call, a sound signal of the first mobile terminal 100 is input to the first audio mixer 461, via the first communication module 410 of the second mobile terminal 200, and synthesized by the first audio mixer 461 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the second communication module 420 of the second mobile terminal 200 and transmitted to the third mobile terminal 300 through the second antenna 402. [0049]While performing a conference call, when communication with the third mobile terminal 300 terminates, the first audio mixer 461 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the first audio mixer 461 is activated only when performing communication with the third mobile terminal 300. [0050]The second audio mixer 462 synthesizes a sound signal of the first mobile terminal 100 output from the first communication module 410 and a sound signal of the third mobile terminal 300 output from the second communication module 420. The synthesized sound signal is output through a speaker (SPK) of the second mobile terminal 200. The SPK may be mounted on the mobile terminal or may be an earphone of the mobile terminal or a separate audio speaker receiving the synthesized sound signal. [0051]The third audio mixer 463 synthesizes a sound signal of the third mobile terminal 300 received from the second communication module 420 and a sound signal received from the MIC of the second mobile terminal 200. The third audio mixer 463 outputs the synthesized sound signal to the first communication module 410. The synthesized sound signal output to the first communication module 410 is modulated and transmitted to the first mobile terminal 100, via the first antenna 401. That is, when performing a conference call, a sound signal of the third mobile terminal 300 is input to the third audio mixer 463 via the second communication module 420 of the second mobile terminal 200 and synthesized by the third audio mixer 463 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the first communication module 410 of the second mobile terminal 200 and transmitted to the first mobile terminal 100 from the first antenna 401. [0052]While performing a conference call, when communication with the first mobile terminal 100 terminates, the third audio mixer 463 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the third audio mixer 463 is activated only when performing communication with the first mobile terminal 100. [0053]FIG. 3 is a flowchart illustrating a method of performing a conference call according to an exemplary embodiment of the present invention. [0054]Referring to FIGS. 1 to 3, the first mobile terminal 100 and the second mobile terminal 200 are connected for communication through the GSM wireless communication network 150 in step S500. In this case, the second mobile terminal 200 transmits and receives a wireless signal to and from the first mobile terminal 100 from the first antenna 401 and the first communication module 410. [0055]The controller 450 of the second mobile terminal 200 controls the second communication module 420 to await a communication connection request. Further, when forming a communication channel with the first mobile terminal 100, the controller 450 of the second mobile terminal 200 activates the second audio mixer 462 and the third audio mixer 463 and sustains the first audio mixer 461 in an inactive state. Specifically, when the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 of the second mobile terminal 200 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0056]The third mobile terminal 300 requests communication to the second mobile terminal 200 through the CDMA wireless communication network 350 in step S502. Although not shown in FIG. 3, alternatively the second mobile terminal 200 may request communication to the third mobile terminal 300 through the CDMA wireless communication network 350. [0057]When a communication request from the third mobile terminal 300 is received, the controller 450 of the second mobile terminal 200 notifies the reception of a communication request to a user of the second mobile terminal 200, by controlling a display unit to display that a communication connection request from another wireless communication network is received or by outputting a reception sound, for example. [0058]The second mobile terminal 200 determines whether a conference call is to be performed according to the communication request received from the CDMA wireless communication network 350 in step S504. [0059]If a conference call is not to be performed, the second mobile terminal 200 performs individual communication with either the first mobile terminal 100 or the third mobile terminal 300, according to the user's selection in step S506. The individual communication is performed by controlling the first communication module 410 and the second communication module 420. For example, when individual communication with the first mobile terminal 100 is intended, the controller 450 of the second mobile terminal 200 controls to sustain only a communication connection state of the second communication module 420 and to turn off other functions. [0060]If it is determined that a conference call is to be performed in step S504, the second mobile terminal 200 activates a conference call function in step S508. The controller 450 activates both the first communication module 410 and the second communication module 420 of the second mobile terminal 200, and activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0061]The second mobile terminal 200 is connected for communication with the third mobile terminal 300 in the CDMA wireless communication network 350 in step S510, thereby forming a conference call with the first mobile terminal 100 and the third mobile terminal 300. [0062]When forming a conference call between the first mobile terminal 100 and the third mobile terminal 300, the first audio mixer 461 of the second mobile terminal 200 synthesizes a sound signal of the first mobile terminal 100 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the second communication module 420. The output sound signal of the first mobile terminal 100 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the third mobile terminal 100 from the second antenna 402. [0063]The third audio mixer 463 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the first communication module 410. The output sound signal of the third mobile terminal 300 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the first mobile terminal 100 from the first antenna 401. [0064]The second audio mixer 462 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the first mobile terminal 100. The second audio mixer 462 outputs the synthesized sound signal through the SPK of the second mobile terminal 200. [0065]While performing a conference call, when communication between the first mobile terminal 100 and the second mobile terminal 200 terminates, the controller 450 of the second mobile terminal 200 terminates functions of the third audio mixer 463 in order to prevent unnecessary power consumption. Alternatively, when communication between the second mobile terminal 200 and the third mobile terminal 300terminates, the controller 450 of the second mobile terminal 200 terminates functions of the first audio mixer 461 in order to prevent unnecessary power consumption. [0066]As described above, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a conference call with mobile terminals using different wireless communication networks. Thus, a conference call may be performed without subscribing to an additional service. Accordingly, user convenience may be improved. [0067]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.(String), 优先 [0001] 此申请根据 35 U.S.C. 2008 年 1 月 17 日向韩国知识产权局提交并转让序列号为 10-2008-0005296 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种多待移动终端以及使用该多待移动终端进行电话会议的方法。 更具体地,本发明涉及一种多待移动终端以及使用该多待移动终端执行电话会议的方法,其使得存在于不同无线通信网络中的多个移动终端之间能够进行通信连接。 [0004] 2.相关技术的描述 [0005] 由于技术的快速发展,具有多种功能的移动终端,例如语音通信、短消息服务、视听通信、电子日程安排和互联网已经面世。 可以与两个或多个无线通信网络进行通信连接的多待移动终端,例如支持码分多址(CDMA)无线通信网络和全球移动通信系统(GSM)的双待移动终端 ) 无线通信网络,现提供。 双待移动终端在CDMA无线通信网络服务区和GSM无线通信网络服务区都可以处于通信待机状态。 即,在双待移动终端与使用CDMA无线通信网络的移动终端进行通信连接的状态下,双待移动终端可以接收来自使用GSM无线通信网络的移动终端的通信请求,并且 与移动终端连接进行通信。 [0006] 移动终端服务提供商作为附加服务提供电话会议功能,其中几个人可以同时形成通信信道并进行电话会议。 [0007] 传统的多待移动终端无法进行电话会议。 然而,传统的多待机移动终端只能与使用不同无线通信网络的移动终端进行同时待机和单独通信。 [0008] 因此,需要一种使多待移动终端能够使用不同的无线通信网络进行电话会议的方法和装置。 发明内容 [0009] 本发明的一个方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一方面在于提供一种多待移动终端以及使用该多待移动终端进行电话会议的方法,使得不同无线通信网络中的移动终端能够进行电话会议。 [0010] 根据本发明的一个方面,提供了一种多待移动终端。 该移动终端包括用于与第一无线通信网络形成通信信道的第一通信模块、用于与第二无线通信网络形成通信信道的第二通信模块、以及用于合成声音信号的第一混音器,从第一无线通信网络输入。 通信模块和麦克风,以合成声音信号,并将合成声音信号输出到第二通信模块。 [0011]根据本发明的另一方面,提供了一种执行电话会议的方法。 该方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中,第二移动终端是多待移动终端; 由存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信; 当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议, 将合成的声音信号发送给第三移动终端。 [0012] 本发明的其他方面、缺点和显着特征对于本领域技术人员而言将从以下详细描述中变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0013] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0014] 如图。 附图说明图1是示出根据本发明示例性实施例的使用多待移动终端的电话会议系统的图; [0015] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图; 和 [0016] 如图。 图3是示出根据本发明示例性实施例的用于执行电话会议的方法的流程图。 [0017] 在整个附图中,应当注意,相同的附图标记用于描述相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0018] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,省略了对众所周知的功能和结构的描述。 [0019] 以下描述和权利要求中使用的术语和词语不限于书目含义,而是仅由发明人使用以实现对本发明的清晰和一致的理解。 因此,本领域技术人员应该清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0020] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0021] 在以下描述中,描述了可以与CDMA无线通信网络和GSM无线通信网络进行通信连接的双待移动终端,例如多待移动终端。 然而,本发明不限于此。 即,根据本发明示例性实施例的多待机移动终端可以执行与各种无线通信网络的通信连接,例如通用分组无线服务(GPRS)、增强型数据GSM环境(EDGE)、通用 移动电信系统 (UMTS) 和宽带码分多址 (WCDMA)。 [0022]参照附图描述根据本发明示例性实施例的多待移动终端的配置以及使用多待移动终端执行电话会议的方法。 [0023] 如图。 图1是图示根据本发明示例性实施例的使用多待移动终端的电话会议系统的图。 [0024] 参考图。 1、第一个移动终端 100 是支持GSM无线通信网络的移动终端 150 ,第三个移动终端 300 是支持CDMA无线通信网络的移动终端 350 和第二个移动终端 200 是支持GSM和CDMA无线通信网络的多待机移动终端 150 和 350 . 第一个移动终端 100 第三个移动终端 300 也可以是多待移动终端。 [0025] 在下面的描述中,在第一移动终端 100 第二移动终端 200 连接进行通信,如果第三个移动终端 300 请求多人之间的通信,假设第二个移动终端 200 可以执行电话会议功能。 即,在第二移动终端 200 和第一个移动终端 100 使用 GSM 无线通信网络进行通信 150 , 第三个移动终端 300 可通过 CDMA 无线通信网络请求 350 , 几个人之间的通信到第二个移动终端 200 . 或者,第二移动终端 200 可以向第三移动终端请求多人之间的通信 300 . 在这种情况下,第二移动终端的电话会议功能 200 被激活。 这样,第一移动终端之间的通信 100 ,第二个移动终端 200 第三个移动终端 300 可以执行。 [0026] 第二移动终端的电话会议功能 200 稍后将参考图10进行描述。 2. [0027] 开启电话会议功能时,如果第一移动终端的声音信号 100 发送到第二移动终端 200 ,第二个移动终端 200 合成自己的声音信号和第一移动终端的声音信号 100 使用混音器将合成的声音信号发送给第三移动终端 300 . 即第三移动终端 300 可以接收第二移动终端的声音信号 200 和第一个移动终端 100 通过合成的声音信号。 [0028] 同理,如果第三移动终端的声音信号 300 发送到第二移动终端 200 ,第二个移动终端 200 可以合成自己的声音信号和第三移动终端的声音信号 300 使用音频混音器。 第二个移动终端 200 然后将合成的声音信号发送给第一移动终端 100 . 即第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 通过合成的声音信号。 [0029] 第二个移动终端 200 合成从第一移动终端发送的声音信号 100 第三移动终端发送的声音信号 300 使用音频混合器并通过第二移动终端的扬声器(SPK)输出合成的声音信号 200 . 由此,第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 ,第二个移动终端 200 可以接收第一移动终端的声音信号 100 第三个移动终端 300 ,以及第三个移动终端 300 可以接收第一移动终端的声音信号 100 第二移动终端200 . 因此,可以执行电话会议。 [0030] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图。 [0031] 如图。 如图2所示,作为多待移动终端 200 根据本发明的示例性实施例,提供一种可以与GSM无线通信网络和CDMA无线通信网络进行通信连接的双待移动终端。 然而,本发明的多待移动终端不限于双待移动终端。 [0032] 双待移动终端可以具有安装CDMA卡和GSM卡的插槽,或者一个用于安装集成了CDMA卡和GSM卡的双卡的插槽。 [0033] 参考图。 2、双待移动终端(以下简称第二移动终端 200 )根据本发明的示例性实施例包括第一天线 401 ,第二根天线 402 ,第一通信模块 410 ,第二个通信模块 420 , 一个控制器 450 和一个混音器 460 包括第一个混音器 461 ,第二个音频混音器 462 和第三个混音器 463 . [0034] 第一个天线 401 通过 GSM 无线通信网络发送和接收声音信号和数据 150 并接收用于GSM无线通信网络的频率 150 . [0035] 第二个天线 402 通过CDMA无线通信网络发送和接收声音信号和数据 350 并接收用于CDMA无线通信网络的频率 350 . [0036] 如图。 图2说明了第一天线 401 和第二根天线 402 作为单独的天线。 但是第一个天线 401 和第二根天线 402 可以形成为一个天线。 当第一根天线 401 和第二根天线 402 组成一根天线,双待移动终端 200 包括用于将频带划分为CDMA频带和GSM频带的装置。 例如双待移动终端 200 使用双工器(未示出)将天线接收到的信号分成CDMA频带的信号和GSM频带的信号。 双待移动终端 200 将GSM频段的信号传输给第一通信模块 410 以及CDMA频段的信号到第二通信模块 420 . [0037] 第一通讯模块 410 第二通信模块 420 每个都包括用于划分发送/接收信号的发送/接收信号分配器(未示出)、用于对要发送的信号的频率进行上变频和放大信号的射频(RF)发送器(未示出)、RF 接收器(未示出)用于低噪声放大接收信号并下变频信号的频率,以及用于调制和解调声音信号的调制解调器。 [0038] 以下,为了描述方便,假设第一通信模块 410 与GSM无线通信网络形成通信通道 150 向第一移动终端发送和从第一移动终端接收无线信号 100 使用GSM无线通信方法。 此外,第二通信模块 420 与CDMA无线通信网络形成通信通道 350 向第三移动终端发送和从第三移动终端接收无线信号 300 使用CDMA无线通信方法。 [0039] 第一通讯模块 410 解调从第一移动终端接收到的无线信号 100 调制从第二移动终端的麦克风(MIC)输入的声音信号 200 到无线信号。 更具体地,在进行电话会议时,第一通信模块 410 调制第二移动终端的声音信号200 第三移动终端的声音信号 300 在混音器中合成 460 将调制后的声音信号发送给第一移动终端 100 . [0040] 第二通讯模块 420 解调从第三移动终端接收的无线信号 300 调制从第二移动终端的MIC输入的声音信号 200 到无线信号。 更具体地说,当进行电话会议时,第二通信模块 420 调制第二移动终端的声音信号 200 以及第一移动终端的声音信号 100 在混音器中合成 460 将调制后的声音信号发送给第三移动终端 300 . [0041] 控制器 450 控制第二移动终端的一般操作 200 第二移动终端的元件的信号流 200 . 更具体地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 . 更详细地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 与 GSM 通信网络进行通信连接 150 和CDMA通信网络 350 , 分别。 当第一通信模块接收到通信连接请求时 410 或第二通信模块 420 , 控制器 450 激活相应的第一通信模块 410 或第二个通信模块 420 进行通信。 [0042] 进一步地,在第一移动终端 100 第二移动终端 200 通过GSM无线通信网络进行通信 150 ,如果是第三个移动终端 300 通过 CDMA 无线通信网络请求多人之间的通信 350 , 控制器 450 第二个移动终端 200 执行电话会议功能。 如果收到来自第三移动终端的通信请求 300 不是几个人之间的通信请求,控制器 450 执行单独的通信功能。 即,为了与第三移动终端进行单独通信 300 , 控制器 450 终止第一通信模块的通信连接功能以外的功能 410 . 此外,控制器 450 控制音频混音器 460 阻止与第一移动终端之间的声音信号的发送和接收 100 . [0043] 类似地,为了与第一移动终端进行单独的通信 100 , 控制器 450 终止第二通信模块的通信连接功能以外的功能 420 ,并阻止与第三移动终端之间的声音信号的发送和接收 300 . [0044] 控制器 450 可以执行电话会议功能以激活第一通信模块 410 第二通信模块 420 . 具体来说,当控制器 450 激活第一个通信模块 410 第二通信模块 420 ,第一移动终端的声音信号 100 在第二个移动终端中调制 200 ,调制后的声音信号与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第三移动终端 300 . 同样,第三移动终端的声音信号 300 与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第一移动终端 100 . 从而,在不同无线通信网络中的移动终端之间进行语音通信的电话会议。 [0045] 当第一个移动终端 100第二移动终端 200 执行单独的通信,控制器 450 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0046] 在进行电话会议时,与第一移动终端中的任一个通信时 100 或者第三个移动终端 300 终止,控制器 450 控制混音器的电话会议终止功能 460 . 稍后描述其详细描述。 [0047] 控制器 450 可以包括在第一通信模块中 410 或在第二个通讯模块中 420 . 在这种情况下,通信模块 410 或者 420 包括控制器 450 成为主要的通信模块,控制整个系统的信号流,包括另一个通信模块的信号流。 [0048] 进行电话会议时,第一个混音器 461 合成第一移动终端的声音信号 100 从第一通信模块接收 410 以及从第二移动终端的MIC接收到的声音信号 200 . 第一个混音器 461 将合成的声音信号输出到第二通信模块 420 . 合成声音信号输出至第二通信模块 420 调制后发送到第三移动终端 300 通过第二根天线 402 . 即在进行电话会议时,第一移动终端的声音信号 100 输入到第一个混音器 461 ,通过第一通讯模块 410 第二个移动终端 200 ,并由第一个混音器合成 461 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第二通信模块 420 第二个移动终端 200 并传送至第三移动终端 300 通过第二根天线 402 . [0049] 进行电话会议时,与第三移动终端通信时 300 终止,第一个混音器 461 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第一混音器 461 仅在与第三移动终端进行通信时激活 300 . [0050] 第二个混音器 462 合成第一移动终端的声音信号 100 第一个通信模块的输出 410 第三移动终端的声音信号 300 第二通信模块的输出 420 . 合成的声音信号通过第二移动终端的扬声器(SPK)输出 200 . SPK可以安装在移动终端上,也可以是移动终端的耳机或接收合成声音信号的单独的音频扬声器。 [0051] 第三个混音器 463 合成第三移动终端的声音信号 300 从第二通信模块接收 420 以及从第二移动终端的MIC接收到的声音信号 200 . 第三个混音器 463 将合成的声音信号输出到第一通信模块 410 . 合成声音信号输出至第一通讯模块 410 被调制并发送到第一移动终端 100 ,通过第一根天线 401 . 即在进行电话会议时,第三移动终端的声音信号 300 输入到第三个混音器 463 通过第二个通信模块 420 第二个移动终端 200并由第三个混音器合成 463 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第一通信模块 410 第二个移动终端 200 并传送至第一移动终端 100 从第一根天线 401 . [0052] 在进行电话会议时,与第一移动终端通信时 100 终止,第三个混音器 463 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第三混音器 463 仅在与第一移动终端进行通信时激活 100 . [0053] 如图。 图3是示出根据本发明示例性实施例的执行电话会议的方法的流程图。 [0054] 参考图。 1到3、第一移动终端 100 第二移动终端 200 通过 GSM 无线通信网络连接进行通信 150 在步骤 S 500 . 在这种情况下,第二移动终端 200 向第一移动终端发送和从第一移动终端接收无线信号 100 从第一根天线 401 和第一通信模块 410 . [0055] 控制器 450 第二个移动终端 200 控制第二通信模块 420 等待通信连接请求。 此外,当与第一移动终端形成通信信道时 100 , 控制器 450 第二个移动终端 200 激活第二个混音器 462 和第三个混音器 463 并维持第一个混音器 461 处于非活动状态。 具体地,当第一移动终端 100 第二移动终端 200 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 第二个移动终端 200 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0056] 第三个移动终端 300 请求与第二移动终端的通信 200 通过CDMA无线通信网络 350 在步骤 S 502 . 尽管图 1 中未显示。 3、备选第二个移动终端 200 可以请求与第三移动终端的通信 300 通过CDMA无线通信网络 350 . [0057] 当来自第三移动终端的通信请求时 300 收到,控制器 450 第二个移动终端 200 通知第二移动终端的用户接收到通信请求 200 例如,通过控制显示单元显示接收到来自另一无线通信网络的通信连接请求或者通过输出接收声音。 [0058] 第二个移动终端 200 根据从CDMA无线通信网络接收到的通信请求,确定是否进行电话会议 350 在步骤 S 504 . [0059] 如果不进行电话会议,则第二移动终端 200 与第一移动终端进行单独通信 100 或者第三个移动终端 300 ,根据用户在步骤S中的选择 506 . 通过控制第一通信模块进行单独通信 410 第二通信模块 420 . 例如,当与第一移动终端单独通信时 100旨在,控制器 450 第二个移动终端 200 控制以仅维持第二通信模块的通信连接状态 420 并关闭其他功能。 [0060] 如果在步骤S中确定要进行电话会议 504 ,第二个移动终端 200 在步骤 S 中激活电话会议功能 508 . 控制器 450 激活第一个通信模块 410 第二通信模块 420 第二个移动终端 200 , 并激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0061] 第二个移动终端 200 连接用于与第三移动终端通信 300 在CDMA无线通信网络中 350 在步骤 S 510 ,从而与第一移动终端形成电话会议 100 第三个移动终端 300 . [0062] 第一移动终端之间进行电话会议时 100 第三个移动终端 300 , 第一个混音器 461 第二个移动终端 200 合成第一移动终端的声音信号 100 第二移动终端的声音信号 200 并将合成声音信号输出至第二通信模块 420 . 第一移动终端的输出声音信号 100 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第三移动终端 100 从第二根天线 402 . [0063] 第三个混音器 463 第二个移动终端 200 合成第三移动终端的声音信号 300 第二移动终端的声音信号 200 并将合成声音信号输出至第一通讯模块 410 . 第三移动终端的输出声音信号 300 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第一移动终端 100 从第一根天线 401 . [0064] 第二个混音器 462 第二个移动终端 200 合成第三移动终端的声音信号 300 以及第一移动终端的声音信号 100 . 第二个混音器 462 通过第二移动终端的SPK输出合成的声音信号 200 . [0065] 在进行电话会议时,在第一移动终端之间进行通信时 100 第二移动终端 200 终止,控制器 450 第二个移动终端 200 终止第三个混音器的功能 463 以防止不必要的功耗。 或者,当第二移动终端之间进行通信时 200 第三个移动终端 300 终止,控制器 450 第二个移动终端 200 终止第一个混音器的功能 461 以防止不必要的功耗。 [0066] 如上所述,根据本发明示例性实施例的多待机移动终端可以与使用不同无线通信网络的移动终端进行电话会议。 因此,可以在不订阅附加服务的情况下执行电话会议。 因此,可以提高用户便利性。 [0067] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String), 111524(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), CN101489322A(String), 1046981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), EP2081370A1(String), 1046982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), KR1020090079379A(String), 1046983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270636(Integer), US20090186607A1(String), 1046984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20090186607A1(String), US20090186607A1(String), 1248278400(Integer), 270636(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974672(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184953(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75902(Integer), 2(Integer), 184953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120276924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\53f998d511a04124bcd51df3d139cd90.png(String), 184954(Integer), 53f998d511a04124bcd51df3d139cd90.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System and method for positioning mobile terminal, and mobile terminal(String), 移动终端定位系统、方法及移动终端(String), US20120276924A1(String), The disclosure discloses a method for positioning a mobile terminal, which comprises: a server sends a push notification to a mobile terminal; the mobile terminal performs self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal, and sends the geographical position information to the server; the server receives and displays the geographical position information sent by the mobile terminal. The disclosure also discloses a system for positioning a mobile terminal for implementing the method for positioning a mobile terminal and a mobile terminal. With such method and device, the server can be used to send a push notification to the mobile terminal after a user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal.(String), 本发明公开了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端收到推送通知后进行自我定位,获取移动终端的地理位置信息,并将地理位置信息发送给服务器。 服务器接收并显示移动终端发送的地理位置信息。 本发明还公开了一种用于实现上述移动终端定位方法的移动终端定位系统及移动终端。 通过这样的方法和装置,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位其地理位置信息,并将地理位置信息发送至服务器,以帮助用户检索移动终端。(String), US13/519896(String), 1279468800(Integer), US20120276924A1(String), 1351699200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 4(Integer), US20070015505A1 | US20080293397A1 | US20080320573A1 | US20120142329A1(String), \20230420\53f998d511a04124bcd51df3d139cd90.png(String), 16(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.640 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 1. A method for positioning a mobile terminal, comprising:sending, by a server, a push notification to a mobile terminal;performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal;sending, by the mobile terminal, the geographical position information to the server; andreceiving and outputting, by the server, the geographical position information sent by the mobile terminal.(String), 1.根据权利要求9所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 2. The method according to claim 1, further comprising: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal,sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andperforming, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command.(String), 12.根据权利要求2所述的方法,还包括:在服务器向移动终端发送推送通知的步骤之前,移动终端在检测到SIM卡被更换后,向服务器发送移动终端的国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息正在启动。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 3. The method according to claim 1, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 13.根据权利要求12所述的方法,还包括:服务器根据接收到的移动终端的IMEI与IMSI的匹配信息,更新之前的移动终端的IMEI与IMSI的匹配信息,并进一步判断更新后的IMEI是否为在服务器注册的移动终端的IMEI。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 4. The method according to claim 3, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 14.根据权利要求6所述的系统,其中移动终端还包括SIM卡检测模块和匹配信息发送模块,其中SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 5. A system for positioning a mobile terminal, comprising a server and a mobile terminal, whereinthe server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; andthe mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 15.根据权利要求14所述的系统,其中服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前移动终端的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为移动终端在服务器注册的IMEI.16.根据权利要求10所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 6. The system according to claim 5, whereinthe server is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andthe mobile terminal further comprises a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 7. The system according to claim 5, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 8. The system according to claim 7, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 9. A mobile terminal, comprising a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 10. The mobile terminal according to claim 9, further comprising a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 11. The mobile terminal according to claim 9, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 12. The method according to claim 2, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 13. The method according to claim 12, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 14. The system according to claim 6, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 13(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 15. The system according to claim 14, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184954(Integer), 16. The mobile terminal according to claim 10, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111525(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184954(Integer), TECHNICAL FIELD [0001]The disclosure relates to the technology of mobile communications, particularly to a system and method for positioning a mobile terminal and to a mobile terminal. BACKGROUND [0002]With the continuous development of mobile communication technologies, a mobile terminal, such as a mobile phone, a Personal Digital Assistant (PDA) and the like is no longer used as a simple communication tool only. Because the above mobile terminal has advantages of small volume, easiness in taking, convenience in use and the like, it has gradually become a personal information storage carrier for the user. Many users of the mobile terminal get used to storing important personal information involving personal information security, such as contacts, photos, schedules and the like in the mobile terminal. [0003]After the mobile terminal is lost, its operator cannot help the user retrieve the lost mobile terminal because the operator only provides Subscriber Identity Module (SIM) card loss reporting and re-issuing services, and cannot provide specific position information of the mobile terminal. SUMMARY [0004]The disclosure mainly aims to provide a system and method for positioning a mobile terminal, and also provide a mobile terminal, with which geographical position information of a lost mobile terminal can be provided to a user to help the user retrieve the mobile terminal. [0005]The disclosure provides a method for positioning a mobile terminal, which comprises: sending, by a server, a push notification to a mobile terminal; performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal; sending, by the mobile terminal, the geographical position information to the server; and receiving and outputting, by the server, the geographical position information sent by the mobile terminal. [0006]Preferably, the method may further comprise: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal, sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and performing, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command. [0007]Preferably, the method may further comprise: before the step of sending, by the server, the push notification to the mobile terminal, sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started. [0008]Preferably, the method may further comprise: updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0009]A system for positioning a mobile terminal, comprises a server and a mobile terminal, wherein the server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; and the mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0010]Preferably, the server may be further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command. [0011]Preferably, the mobile terminal may further comprise a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, wherein the SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; and the matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed. [0012]Preferably, the server may be further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0013]A mobile terminal comprises a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0014]Preferably, the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server. [0015]Preferably, the mobile terminal may further comprise: a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; and a matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed. [0016]With the system and method for positioning a mobile terminal, and the mobile terminal provided by the disclosure, the server can be used to send a push notification to the mobile terminal after the user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0017]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure; [0018]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure; [0019]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure; [0020]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure; [0021]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure; and [0022]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0023]The achievement of the purpose of the disclosure, functional characteristics and advantages of the disclosure will be described with reference to the embodiments and drawings in detail. DETAILED DESCRIPTION [0024]The technical solution of the disclosure is described below with reference to the drawings of the description and the specific embodiments in detail. [0025]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure. [0026]After a mobile terminal is lost, when a finder or a thief does not turn off the mobile terminal, its user logs in a server in time to report loss, and registers an International Mobile Equipment Identity (IMEI) of the mobile terminal. As shown in FIG. 1, a method for protecting data in a mobile terminal of the disclosure comprises the following steps. [0027]Step S101: a server sends a push notification to a mobile terminal. [0028]In this embodiment, the push notification can be sent to the mobile terminal through the server so as to notify the mobile terminal to be positioned via the push notification. In addition, the mobile terminal is registered with an inbound network connection for a positioning program, and the mobile terminal monitors whether the push notification sent by the monitoring mobile terminal is received on the registered inbound network connection. The inbound network connection is registered for the positioning program in a static registration manner or a dynamic registration manner. The static registration will be taken as an example in this embodiment for description. [0029]The server inquires an International Mobile Subscriber Identity (IMSI) of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends the push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0030]Furthermore, a Java Application Description (JAD) file of the mobile terminal is further provided with the MIDlet-Push-<1>attribute, for example the attribute is set as: [0031]MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; after the attribute is added, it indicates a connection protocol adopted is a Short Messaging Service (SMS) protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0032]Step S102: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0033]In the embodiment, the positioning program is a location Application Programming Interface (API) for Java 2 Micro Edition (J2ME) program, which meets Java Specification Request (JSR) 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a Global Positioning System (GPS), a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0034]Step S103: the mobile terminal sends the geographical position information to the server. [0035]In the embodiment, the geographical position information comprises longitude and latitude information of the mobile terminal. [0036]Step S104: the server receives and displays the geographical position information sent by the mobile terminal. [0037]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0038]Step S105: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0039]In the embodiment, the server sends a Lock And Wipe Management Object (LAWMO) command to the mobile terminal according to a Device Management (DM) protocol defined by Open Mobile Alliance (OMA). The server sends the locking command to the mobile terminal through the device management protocol in a Synchronization Markup Language (SyncML) protocol set. [0040]Step S106: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S105 and step S106 are not the necessary steps. [0041]In the embodiment, the server can be used to send the push notification to the mobile terminal after the user finds the mobile terminal is lost; the mobile terminal positions the geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. [0042]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure. [0043]When a mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change a Subscriber Identity Module (SIM) card, when the finder or the thief turns on the mobile terminal again, the mobile terminal will protect data based on the following steps. [0044]Step S201: the mobile terminal detects whether an SIM card is changed after being started; if yes, turn to step S202; otherwise, turn to step S205. [0045]In the embodiment, after the mobile terminal is started, it automatically starts the SIM card verification kit to verify whether the IMSI of the SIM card is changed; if yes, it indicates the SIM card of the mobile terminal is changed. The method for automatically starting the SIM card detection function after startup is as follows: [0046]the MIDlet-1-Type:autostart attribute is added in the Java application description file of the terminal, and meanwhile an autostart permission is also added in the Java application description file in the specific format of: [0047]MIDlet-Permissions:javax.microedition.midlet.AutoStart Permission. [0048]Step S202: the mobile terminal sends matching information between an IMEI and an IMSI to the server. [0049]In the embodiment, the mobile terminal sends matching information between an IMEI and an IMSI to a server through a short message. [0050]Step S203: the server updates the matching information between the IMEI and the IMSI of the mobile terminal. [0051]In the embodiment, after receiving the short message, the server updates the matching information between the IMEI and the IMSI of the mobile terminal through modifying an IMSI number corresponding to the IMEI of the mobile terminal. [0052]Step S204: the server judges whether the updated IMEI is an IMEI of the mobile terminal registered at the server; if yes, turn to step S205; otherwise, the flow is terminated. [0053]Step S205: the server sends a push notification to the mobile terminal. [0054]In the embodiment, the server inquires an IMSI number of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends a push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0055]In addition, the Java application description file of the mobile terminal is provided with the MIDlet-Push-<1>attribute, which is: [0056]MIDlet-Push-1:sms://:8080, MIDletLocation, 13900000000. After the attribute is added, it indicates a connection protocol adopted is an SMS protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0057]Step S206: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0058]In the embodiment, the positioning program is a location API for J2ME program, which meets JSR 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a GPS, a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0059]Step S207: the mobile terminal sends the geographical position information to the server. [0060]In the embodiment, the geographical position information comprises at least longitude and latitude information of the mobile terminal. [0061]Step S208: the server receives and displays the geographical position information sent by the mobile terminal. [0062]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0063]Step S209: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0064]In the embodiment, the server sends an LAWMO command to the mobile terminal according to a device management protocol defined by open mobile alliance. The server sends the locking command to the mobile terminal through the device management protocol in a SyncML protocol set. [0065]Step S210: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S209 and step S210 are not the necessary steps. [0066]In the embodiment, when the mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal; the mobile terminal positions geographical position information thereof after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal. Therefore, data in the lost mobile terminal is prevented from being leaked, and personal information security of the user is ensured. [0067]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure. [0068]The system for positioning a mobile terminal comprises a server 10 and a mobile terminal 20, wherein the mobile terminal 20 comprises a positioning module 201. [0069]The server is configured to send a push notification to the mobile terminal 20, and to receive geographical position information sent by the mobile terminal 20; the positioning module 201 is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal 20, and to send the geographical position information to the server 10. [0070]In the embodiment, the server 10 can be used to send a push notification to the mobile terminal 20 after the user finds that the mobile terminal 20 is lost. The mobile terminal 20 locates geographical position information thereof through the positioning module 201 and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. [0071]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure. [0072]The server 10 is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol. Besides the positioning module 201, the mobile terminal 20 further comprises a locking module 205 and a deleting module 204, an SIM card detecting module 202 and a matching information sending module 203. [0073]The locking module 205 is configured to lock the mobile terminal 20 after receiving the locking command. The deleting module 204 is configured to delete data in a memory after receiving the deleting command. The SIM card detecting module 202 is configured to detect whether an SIM card of the mobile terminal is changed. The matching information sending module 203 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card is changed. [0074]The server 10 is further configured to update the matching information between the IMEI and the IMSI of the mobile terminal 20 registered at the server after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server 10. [0075]In the embodiment, after the mobile terminal 20 is lost, if a finder or a thief turns off the mobile terminal 20 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 20 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 20 is changed; if the SIM card is not changed, the server 10 is directly used to send a push notification to the mobile terminal 20; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 20; the mobile terminal 20 positions geographical position information thereof through the positioning module 201 after receiving the push notification, and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. Therefore, data in the mobile terminal 20 is prevented from being leaked, and personal information security of the user is ensured. [0076]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure. [0077]The mobile terminal 30 comprises a positioning module 301, which is configured to perform self-positioning after receiving a push notification to acquire geographical position information regarding the mobile terminal 30, and send the geographical position information to a server. [0078]In the embodiment, the server can be used to send a push notification to the mobile terminal 30 after the user finds that the mobile terminal 30 is lost. The mobile terminal 30 positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal 30. [0079]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0080]Besides the positioning module 301, the mobile terminal 40 further comprises a locking module 302, a deleting module 303, an SIM card detecting module 304, and a matching information sending module 305. [0081]The locking module 302 is configured to lock the mobile terminal 40 after receiving a locking command sent by a server; the deleting module 303 is configured to delete data in a memory after receiving a deleting command sent by the server. The SIM card detecting module 304 is configured to detect whether an SIM card is changed. The matching information sending module 305 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card of the mobile terminal is changed. [0082]In the embodiment, after the mobile terminal 40 is lost, if a finder or a thief turns off the mobile terminal 40 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 40 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 40 is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal 40; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 40; the mobile terminal 40 positions geographical position information thereof through the positioning module 301 after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal 40. Therefore, data in the mobile terminal 40 is prevented from being leaked, and personal information security of the user is ensured. [0083]The above is only the preferred embodiment of the disclosure and not intended to limit the scope of the patent, and any equivalent structure or equivalent flow transformation based on the description and drawings of the disclosure, which is directly or indirectly applied in other related technical fields shall fall within the scope of patent protection of the disclosure.(String), 技术领域 [0001] 本发明涉及移动通信技术,尤其涉及一种移动终端定位系统、方法及移动终端。 背景 [0002] 随着移动通信技术的不断发展,移动终端,如手机、个人数字助理(Personal Digital Assistant,PDA)等,不再仅仅是一种简单的通信工具。 由于上述移动终端具有体积小、携带方便、使用方便等优点,逐渐成为用户个人信息的存储载体。 很多移动终端的用户习惯于在移动终端中存储联系人、照片、日程等涉及个人信息安全的重要个人信息。 [0003] 移动终端丢失后,其运营商无法帮助用户找回丢失的移动终端,因为运营商仅提供SIM卡挂失和补发服务,无法提供移动终端的具体位置信息。 概括 [0004] 本发明的主要目的在于提供一种移动终端的定位系统及方法,还提供一种移动终端,能够将丢失的移动终端的地理位置信息提供给用户,以帮助用户找回移动终端。 [0005] 本发明提供了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端接收到推送通知后进行自定位,获取移动终端的地理位置信息; 移动终端向服务器发送地理位置信息; 服务器接收并输出移动终端发送的地理位置信息。 [0006] 优选地,该方法还包括: 在服务器接收并输出移动终端发送的地理位置信息的步骤之后,服务器根据移动终端发送锁定命令和/或删除命令。 设备管理协议; 移动终端在接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 [0007] 优选地,该方法还包括: 在服务器向移动终端发送推送通知之前,移动终端发送国际移动设备识别码(IMEI)与国际移动用户识别码的匹配信息。 移动终端(IMSI)在启动后检测到SIM卡被更换时发送给服务器。 [0008] 优选地,该方法还包括:服务器根据接收到的移动终端的IMEI和IMSI的匹配信息更新之前的移动终端的IMEI和IMSI的匹配信息,进一步判断, 服务器,更新后的IMEI是否为在服务器注册的移动终端的IMEI。 [0009] 一种移动终端定位系统,包括服务器和移动终端,服务器用于向移动终端发送推送通知,并接收移动终端发送的地理位置信息; 移动终端还包括定位模块,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0010] 优选地,服务器还可以用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 移动终端还可以包括锁定模块和删除模块,锁定模块用于接收到锁定命令后锁定移动终端。 删除模块,用于接收到删除命令后,删除移动终端内存中的数据。 [0011] 优选地,所述移动终端还包括SIM卡检测模块和匹配信息发送模块,所述SIM卡检测模块用于检测所述移动终端的SIM卡是否被更换。 匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。 [0012] 优选地,服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为注册的移动终端的IMEI 在服务器上。 [0013] 一种移动终端,包括定位模块,用于接收到服务器的推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0014] 优选地,所述移动终端还包括锁定模块和删除模块,所述锁定模块用于接收到所述服务器发送的锁定命令后,锁定所述移动终端。 删除模块,用于接收到服务器发送的删除命令后,删除移动终端内存中的数据。 [0015] 优选地,所述移动终端还包括: SIM卡检测模块,用于检测所述移动终端的SIM卡是否被更换; 匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码(IMEI)和国际移动用户识别码(IMSI)的匹配信息。 [0016] 本发明提供的移动终端定位系统、方法及移动终端,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 附图的简要说明 [0017] 图1为本发明移动终端数据保护方法实施例的流程示意图; [0018] 图2为本发明移动终端数据保护方法另一实施例的流程示意图; [0019] 图3示出了本发明移动终端定位系统实施例的结构示意图; [0020] 图4为本发明移动终端定位系统另一实施例的结构示意图; [0021] 图5示出了本发明移动终端一个实施例的结构示意图; 和 [0022] 图6示出了本发明移动终端另一实施例的结构示意图。 [0023] 本发明目的的实现、功能特点和优点将结合实施例和附图进行详细说明。 详细说明 [0024] 下面结合说明书附图和具体实施例对本发明的技术方案进行详细说明。 [0025] 图1示出了本发明移动终端数据保护方法实施例的流程示意图。 [0026] 移动终端丢失后,当捡到者或小偷没有关闭移动终端时,其用户及时登录服务器挂失,并注册移动终端的国际移动设备识别码(IMEI)。 如图1所示,本发明的移动终端中的数据保护方法包括以下步骤。 [0027] 脚步 101:服务器向移动终端发送推送通知。 [0028] 本实施例中,可以通过服务器向移动终端发送推送通知,以通过推送通知通知移动终端进行定位。 另外,移动终端注册有定位程序的入站网络连接,移动终端监听是否在注册的入站网络连接上接收到监控移动终端发送的推送通知。 入站网络连接以静态注册方式或动态注册方式注册到定位程序。 本实施例以静态注册为例进行说明。 [0029] 服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI,根据IMSI号码获取移动终端的手机号码,然后发送推送通知给 移动终端根据手机号码要求移动终端进行定位。 [0030] 进一步地,移动终端的JAD文件中还设置有MIDlet-Push-<1>属性,例如该属性设置为: [0031] MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; 添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation,推送通知的有效源为服务器 13900000000个数。除了SMS协议之外,本发明当然还可以使用传输控制协议或用户数据报协议,本发明对此不作限制。 [0032] 脚步 102 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0033] 在本实施例中,定位程序为Java 2 Micro Edition(J2ME)程序的定位应用程序编程接口(API),其符合Java Specification Request(JSR)179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以利用基于全球定位系统(Global Positioning System,简称GPS)的卫星定位方法、蜂窝网络的定位方法、或者基于蓝牙的近距离定位方法,或者可以结合上述方法 礼貌。 [0034] 脚步 103 :移动终端向服务器发送地理位置信息。 [0035] 在本实施例中,地理位置信息包括移动终端的经纬度信息。 [0036] 脚步 104 :服务器接收并显示移动终端发送的地理位置信息。 [0037] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0038] 脚步 105 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0039] 在该实施例中,服务器根据开放移动联盟(OMA)定义的设备管理(DM)协议向移动终端发送锁定和擦除管理对象(LAWMO)命令。 服务器通过同步标记语言(SyncML)协议集中的设备管理协议向移动终端发送锁定命令。 [0040] 脚步 106 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S105 和步骤S 106 不是必要的步骤。 [0041] 本实施例中,可以通过服务器在用户发现移动终端丢失后向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 [0042] 图2示出了本发明移动终端数据保护方法另一实施例的流程示意图。 [0043] 当移动终端丢失时,如果捡到者或小偷因电池电量低或想更换用户身份模块(SIM)卡而关闭移动终端,当捡到者或小偷再次打开移动终端时, 移动端将按照以下步骤保护数据。 [0044] 脚步 201 :移动终端开机后检测SIM卡是否被更换; 如果是,转步骤S 202 ; 否则转步骤S 205 . [0045] 本实施例中,移动终端启动后,自动启动SIM卡验证工具,验证SIM卡的IMSI是否发生变化; 如果是,则说明移动终端的SIM卡已更换。 开机后自动启动SIM卡检测功能的方法如下: [0046] 在终端的Java应用描述文件中增加了MIDlet-1-Type:autostart属性,同时在Java应用描述文件中也增加了自动启动权限,具体格式为: [0047] MIDlet-权限:javax.microedition.midlet.AutoStart 权限。 [0048] 脚步 202 :移动终端向服务器发送IMEI和IMSI的匹配信息。 [0049] 本实施例中,移动终端通过短消息向服务器发送IMEI和IMSI的匹配信息。 [0050] 脚步 203 :服务器更新移动终端IMEI和IMSI的匹配信息。 [0051] 本实施例中,服务器接收到短消息后,通过修改移动终端的IMEI对应的IMSI号,更新IMEI与移动终端的IMSI的匹配信息。 [0052] 脚步 204 :服务器判断更新后的IMEI是否为在服务器注册的移动终端的IMEI; 如果是,转步骤S 205 ; 否则,流程终止。 [0053] 脚步 205 :服务器向移动端发送推送通知。 [0054] 在本实施例中,服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI号码,根据IMSI号码获取移动终端的手机号码,然后向客户端发送推送通知。 移动终端根据手机号码要求移动终端进行定位。 [0055] 另外,在移动端的Java应用描述文件中设置了MIDlet-Push-<1>属性,即: [0056] MIDlet-Push-1:sms://:8080,MIDletLocation,13900000000。添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation, 推送通知的有效来源为号码为13900000000的服务器。 除了SMS协议之外,本发明当然还可以采用传输控制协议或用户数据报协议,本发明对此不做限制。 [0057] 脚步 206 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0058]在本实施例中,定位程序为J2ME程序的定位API,符合JSR 179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以采用基于GPS的卫星定位方法、蜂窝网络的定位方法或基于蓝牙的近距离定位方法,也可以结合上述方式。 [0059] 脚步 207 :移动终端向服务器发送地理位置信息。 [0060] 在本实施例中,地理位置信息至少包括移动终端的经纬度信息。 [0061] 脚步 208 :服务器接收并显示移动终端发送的地理位置信息。 [0062] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0063] 脚步 209 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0064] 本实施例中,服务器根据开放移动联盟定义的设备管理协议向移动终端发送LAWMO命令。 服务器通过SyncML协议集中的设备管理协议向移动终端发送锁定命令。 [0065] 脚步 210 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S 209 和步骤S 210 不是必要的步骤。 [0066] 在本实施例中,当移动终端丢失时,如果捡到者或小偷因电池电量低或想换SIM卡而关闭移动终端,当捡到者或小偷再次打开移动终端时,手机 终端首先验证移动终端的SIM卡是否被更换; 若SIM卡未更换,则直接通过服务器向移动终端发送推送通知。 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知。 移动终端接收到推送通知后定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户检索移动终端。 从而避免了丢失移动终端中的数据泄露,保证了用户的个人信息安全。 [0067] 图3示出了本发明移动终端定位系统实施例的结构示意图。 [0068] 一种移动终端定位系统,包括服务器 10 和移动终端 20 , 其中移动终端 20 包括一个定位模块 201 . [0069] 服务器配置为向移动终端发送推送通知 20 ,接收移动终端发送的地理位置信息 20 ; 定位模块 201 用于接收到推送通知后进行自定位,以获取移动终端的地理位置信息 20 ,并将地理位置信息发送给服务器 10 . [0070] 在本实施例中,服务器 10 可用于向移动端发送推送通知 20 用户发现移动端后 20 丢失了。 移动端 20 通过定位模块定位其地理位置信息 201 并将地理位置信息发送给服务器 10帮助用户找回移动终端 20 . [0071] 图4示出了本发明移动终端定位系统另一实施例的结构示意图。 [0072] 服务器 10 还用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 除了定位模块 201 , 移动端 20 还包括锁定模块 205 和一个删除模块 204 , SIM卡检测模块 202 以及匹配的信息发送模块 203 . [0073] 锁定模块 205 配置为锁定移动端 20 收到锁定命令后。 删除模块 204 用于接收到删除命令后删除内存中的数据。 SIM卡检测模块 202 用于检测移动终端的SIM卡是否被更换。 匹配信息发送模块 203 用于在更换SIM卡时向服务器发送IMEI和IMSI的匹配信息。 [0074] 服务器 10 还用于更新移动终端的IMEI与IMSI的匹配信息 20 接收到IMEI与IMSI的匹配信息后在服务器注册,判断更新后的IMEI是否为在服务器注册的移动终端的IMEI 10 . [0075] 在本实施例中,移动终端后 20 丢失,如果发现者或小偷关闭移动终端 20 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 20 再次,移动终端首先验证移动终端的SIM卡是否为 20 已更改; 如果SIM卡没换过,服务器 10 直接用于向移动端发送推送通知 20 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 20 ; 移动终端 20 通过定位模块定位其地理位置信息 201 收到推送通知后,将地理位置信息发送给服务器 10 帮助用户找回移动终端 20 . 因此,移动终端中的数据 20 防止泄露,保障用户个人信息安全。 [0076] 图5示出了本发明移动终端一个实施例的结构示意图。 [0077] 移动端 30 包括一个定位模块 301 ,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息 30 ,并将地理位置信息发送给服务器。 [0078] 在本实施例中,服务器可以用于向移动终端发送推送通知 30 用户发现移动端后 30 丢失了。 移动端 30 对其地理位置信息进行定位,并将地理位置信息发送给服务器,以帮助用户检索移动终端 30 . [0079] 图6示出了本发明移动终端另一实施例的结构示意图。 [0080] 除了定位模块 301 , 移动端 40 还包括锁定模块 302 , 删除模块 303 , SIM卡检测模块 304 , 以及匹配的信息发送模块 305 . [0081] 锁定模块 302 配置为锁定移动端 40 收到服务器发送的锁定命令后; 删除模块 303 用于接收到服务器发送的删除命令后,删除内存中的数据。 SIM卡检测模块 304用于检测SIM卡是否被更换。 匹配信息发送模块 305 用于当移动终端的SIM卡更换时,向服务器发送IMEI和IMSI的匹配信息。 [0082] 在本实施例中,移动终端后 40 丢失,如果发现者或小偷关闭移动终端 40 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 40 再次,移动终端首先验证移动终端的SIM卡是否为 40 已更改; 若SIM卡未更换,则直接使用服务器向移动终端发送推送通知 40 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 40 ; 移动终端 40 通过定位模块定位其地理位置信息 301 收到推送通知后,将地理位置信息发送给服务器,帮助用户找回移动终端 40 . 因此,移动终端中的数据 40 防止泄露,保障用户个人信息安全。 [0083] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的范围,任何基于本发明的说明书和附图所作的等效结构或等效流程变换,直接或间接应用于其他相关技术领域 落入本发明的专利保护范围。(String), 111525(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), CN101835143A(String), 1046985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), EP2509375A1(String), 1046986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), EP2509375A4(String), 1046987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), US20120276924A1(String), 1046988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270637(Integer), WO2011137605A1(String), 1046989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120276924A1(String), US20120276924A1(String), 1351699200(Integer), 270637(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LI, JINMIN(String), XU, LING(String), SHI(String), YUE, HUI(String), 中兴通讯股份有限公司(String), LI JINMIN(String), XU LING(String), 德世股份有限公司(String), YUE HUI(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75904(Integer), 2(Integer), 184954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75905(Integer), 2(Integer), 184954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75906(Integer), 2(Integer), 184954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75907(Integer), 2(Integer), 184954(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75904(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\956d8c269098424e984732995a571b27.png(String), 184955(Integer), 956d8c269098424e984732995a571b27.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of providing Karaoke service to mobile terminals using a wireless connection between the mobile terminals(String), 使用移动终端之间的无线连接向移动终端提供卡拉OK服务的方法(String), US7142807B2(String), A method of providing a Karaoke service to mobile terminals through wireless connection between them. The mobile terminals are grouped as a service group and one of them is designated as a master mobile terminal and the other mobile terminals as slave mobile terminals. The master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service content to be received from the Karaoke service provider in all the mobile terminals of the service group. If the master mobile terminal transmits a play command to the slave mobile terminals, all the mobile terminals start to play Karaoke music according to the service contents.(String), 一种通过移动终端之间的无线连接向移动终端提供卡拉OK服务的方法。 移动终端被分组为一个服务组,其中一个被指定为主移动终端,而其他移动终端被指定为从移动终端。 主移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制从服务组的所有移动终端中的卡拉OK服务提供商接收的服务内容。 如果主移动终端向从移动终端发送播放命令,则所有移动终端根据服务内容开始播放卡拉OK音乐。(String), US10/761970(String), 1074614400(Integer), US7142807B2(String), 1164643200(Integer), 1164643200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 3(Integer), 9(Integer), JP2000122671A | US5588842A | US5689081A | US5691494A | US5824934A | US5885085A | US6062868A | US6074215A | USRE37131E1(String), \20230420\956d8c269098424e984732995a571b27.png(String), 15(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 1. A method of providing a Karaoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals having a wireless connection function to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating all other mobile terminals as slave mobile terminals;connecting the master mobile terminal to a Karaoke service provider through a mobile communication network and controlling service content to be received from theKaraoke service provider in all the mobile terminals of the service group; and playing Karaoke music according to the service content by all the mobile terminals in the service group when the master mobile terminal transmits a play command to the slave mobile terminals, wherein the master and slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 1.一种通过无线连接向移动终端提供卡拉OK服务的方法,包括步骤:将移动终端与具有无线连接功能的移动终端分组为一个服务组,以接收卡拉OK业务;指定其中一个移动终端为主移动终端;将所有其他移动终端指定为从属移动终端;通过移动通信网络将主移动终端连接到卡拉OK服务提供商,并控制从主移动终端接收的服务内容服务组所有移动终端中的卡拉OK服务商;主移动终端向从移动终端发送播放命令时,服务组内的所有移动终端根据服务内容播放卡拉OK音乐,其中主从移动终端根据导频时钟信号进行同步在播放步骤中同时播放。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 2. The method of claim 1, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 2.如权利要求1所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 3. The method of claim 1, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 3.如权利要求1所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 4. The method of claim 1, wherein the step of controlling the service content to be received comprises the steps of:searching for the service content from the Karaoke service provider;transmitting information about the service content to the slave mobile terminals in the service group; andreceiving the service content from the Karaoke service provider according to the service content information in the master mobile terminal and the slave mobile terminals to receive.(String), 4.如权利要求1所述的方法,其中控制接收服务内容的步骤包括:从卡拉OK服务提供商处搜索服务内容;向服务组中的从属移动终端发送服务内容信息;和主移动终端和从移动终端根据服务内容信息从卡拉OK服务商处接收服务内容。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 5. The method of claim 1, wherein the step of controlling the service content comprises the steps of:searching for the service content from the Karaoke service provider;receiving the service content from the Karaoke service provider in the master mobile terminal; andtransmitting the service content from the master mobile terminal to the slave mobile terminals by wireless connections between the master mobile terminal and the slave mobile terminals.(String), 5.如权利要求1所述的方法,其中控制服务内容的步骤包括以下步骤:从卡拉OK服务提供商处搜索服务内容;在主移动终端中接收来自卡拉OK服务提供商的服务内容;和通过主移动终端和从移动终端之间的无线连接将主移动终端的业务内容传输到从移动终端。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 6. A method of providing a Kraoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating the other mobile terminals as slave mobile terminals;receiving, in the slave mobile terminals, service contents from a Karaoke service provider under control of the master mobile terminal; andplaying Karaoke music according to the service contents if the slave mobile terminals receive a play command from the master mobile terminal, wherein the master and the slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 6.一种通过无线连接向移动终端提供Kraoke服务的方法,包括步骤:将移动终端与接收卡拉OK业务的移动终端分组为一个业务组;指定其中一个移动终端为主移动终端;指定其他移动终端为从移动终端;从属移动终端接收主移动终端控制下的卡拉OK服务商的服务内容;和如果从移动终端接收到主移动终端的播放命令,则根据业务内容播放卡拉OK音乐,其中在播放步骤中,主从移动终端根据导频时钟信号同步同步播放。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 7. The method of claim 6, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 7.如权利要求6所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 8. The method of claim 6, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 8.如权利要求6所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 9. The method of claim 6, wherein the step ofreceiving the service contents, comprises the steps of:transmitting information about the service contents from the Karaoke service provider to the slave mobile terminals through the master mobile terminal; andconnecting the slave mobile terminals to the Karaoke service provider and transmitting the service contents to the slave mobile terminal.(String), 9.如权利要求6所述的方法,其中的步骤接收服务内容,包括以下步骤:将卡拉OK服务商的服务内容信息通过主移动终端传输给从移动终端;和将从移动终端连接到卡拉OK服务提供商,并将服务内容传输到从移动终端。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 10. The method of claim 6, wherein the slave mobile terminals receive the service contents from the master mobile terminal by the wireless connection.(String), 10.如权利要求6所述的方法,其中从移动终端通过无线连接从主移动终端接收服务内容。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 11. The method of claim 6, wherein the slave mobile terminals are further grouped as a predetermined number of sub-service groups according to a number of channels.(String), 11.如权利要求6所述的方法,其中从属移动终端根据频道数进一步分组为预定数量的子业务组。(String), 1(Integer), 10(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 12. The method of claim 11, wherein each of the sub-service groups receives different sound data and plays Karaoke music according to the sound data.(String), 12.如权利要求11所述的方法,其中每个子服务组接收不同的声音数据,并根据声音数据播放卡拉OK音乐。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 13. The method of claim 12, wherein the sound data is from one of a left channel and a right channel for stereo sound.(String), 13.如权利要求12所述的方法,其中声音数据来自立体声的左声道和右声道之一。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 14. The method of claim 12, wherein the sound data is from one of channels for digital surround sound 5.1.(String), 14.如权利要求12所述的方法,其中声音数据来自数字环绕声5.1的通道之一。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:35.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184955(Integer), 15. The method of claim 12, wherein the sound data is from one of a predetermined number of sound sources divided from multiple sound sources.(String), 15.如权利要求12所述的方法,其中声音数据来自多个声源划分的预定数量的声源之一。(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111526(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184955(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119 to an application entitled “Method of Providing Karaoke Service to Mobile Terminals Using Wireless Connection between the Mobile Terminals” filed in the Korean Industrial Property Office on Feb. 13, 2003 and assigned Serial No. 2003-8989, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a method of providing a service through a mobile terminal, and in particular, to a method of providing a Karaoke service to a mobile terminal, and providing a computer-readable recording medium to record a program thereon for performing the Karaoke service method. [0004]2. Description of the Related Art [0005]Due to its portability and convenience, the mobile terminal has emerged as a necessity in daily living. Commonly, mobile terminals are equipped with a variety of functions including phonebook and scheduler. Accordingly, they serve as a personal information manager in addition to a means for making phone calls. 2.5th generation mobile terminals, based on IS (International Standard)-95C, and 3rd generation mobile terminals such as IMT (International Mobile Communication)-2000 terminals provide additional multimedia service for personal entertainment purposes. [0006]A Karaoke function, a type of personal entertainment service, plays songs across various genres with lyrics and animation through a mobile terminal. FIG. 1 illustrates a mobile communication system for providing a conventional Karaoke service. Referring to FIG. 1, the Karaoke service is provided over a typical mobile communication network. Hence, the Karaoke service is provided directly from a service provider (SP) over the mobile communication network rather than a service from the mobile communication network itself. [0007]The mobile communication system is comprised of a mobile terminal 11 for receiving the Karaoke service over the mobile communication network, a home location register (HLR) 12 and an authentication center (AC) 13 for providing the registration information of the mobile terminal 11, a mobile communication network 14 for connecting SPs to users, and a Karaoke SP 15 for providing the Karaoke service. [0008]In operation, the user of the mobile terminal 11 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 then authenticates the user through the HLR 12 and the AC 13 and provides the audio data stored in its database to the user. The mobile terminal 11 plays the song with its lyric displayed using the received audio data, enabling the user to sing along. [0009]In general, a user enjoys Karaoke music with others rather than alone. The volume of music that a single mobile terminal plays depends on its speaker and is usually not loud enough for a plurality of users to enjoy the music. In addition, no matter how good the speaker is, it cannot offer enough volume for them with the single sound source. [0010]In view of diverse voice services and rapid changes in their formats, the Karaoke SP 15 attempts to attract mobile subscribers with new features such as accompaniment with multichannel surround sound effects including stereo, or accompaniment with higher-note polyphonic sound through the existing mobile terminal limited to a 40-note polyphonic sound capacity. However, with the service deployment depending on the performance of an individual mobile terminal in the conventional technology, the benefits of those services are often elusive. SUMMARY OF THE INVENTION [0011]It is, therefore, an object of the present invention to provide a Karaoke service method using wireless connections between mobile terminals that are equipped with a Karaoke function, for playing music accompaniment concurrently through the mobile terminals by synchronizing them, and a computer-readable recording medium for recording a program thereon for performing the Karaoke service. [0012]It is another object of the present invention to provide a Karaoke service method for playing music with a high volume, surround sound effects, and various sound sources. [0013]The above and other objects are achieved by providing a method of providing a Karaoke service to a mobile terminal through wireless connections, and a computer-readable recording medium having a program thereon to perform the Karaoke service. [0014]According to one aspect of the present invention, in the Karaoke service method, the mobile terminal is grouped as a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group. The master mobile terminal transmits a play command to the slave mobile terminals, and all the mobile terminals start to play Karaoke music according to the service contents. [0015]According to another aspect of the present invention, in the Karaoke service method, a mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal. Upon receiving a play command from a master mobile terminal, it starts to play Karaoke music according to the service contents. [0016]According to a further aspect of the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. In the first function, a mobile terminal is grouped in a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal in the first function is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group in the second function. The master mobile terminal transmits a play command to the slave mobile terminals, and then all the mobile terminals start to play Karaoke music according to the service contents in the third function. [0017]According to still another aspect o the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. The program performs first, second, and third functions. In the first function, the mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and is designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal in the second function. Upon receiving a play command from the master mobile terminal, a slave mobile terminal starts to play Karaoke music according to the service contents in the third function. BRIEF DESCRIPTION OF THE DRAWINGS [0018]The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which: [0019]FIG. 1 illustrates a mobile communication system that provides a conventional Karaoke service to a mobile terminal; [0020]FIG. 2 illustrates the configuration of a mobile communication system that provides a Karaoke service to a plurality of mobile terminals through wireless connections between them according to an embodiment of the present invention; [0021]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention; [0022]FIG. 4 illustrates examples of screen displays in a mobile terminal for receiving the Karaoke service through wireless connection with other mobile terminals according to the embodiment of the present invention; and [0023]FIGS. 5A and 5B illustrate embodiments of contents reception for the Karaoke service through wireless connections with other mobile terminals according to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0024]Preferred embodiments of the present invention will be described in detail herein below with reference to the accompanying drawings. In the following description, well-known functions and constructions are not described in detail since they would obscure the invention in unnecessary detail. [0025]FIG. 2 illustrates a mobile communication system for providing a Karaoke service to mobile terminals through wireless connections between them according to an embodiment of the present invention. Referring to FIG. 2, the mobile communication system is comprised of a master mobile terminal 21 that receives the Karaoke service over a mobile communication network 14, slave mobile terminals 22 connected to the master mobile terminal 21, for receiving the same Karaoke service, the HLR 12 and the SC 13 for providing registration information for the mobile terminals 21 and 22, the mobile communication network 14 for connecting SPs to mobile subscribers, and a Karaoke SP 15 for providing a Karaoke service. [0026]In operation, the master mobile terminal 21 is connected to the slave mobile terminals 22, forming a service group. The user of the master mobile terminal 21 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 authenticates the user through the HLR 12 and the AC 13 and transmits the audio data to the master mobile terminal 21 and the slave mobile terminals 22. When the master mobile terminal 21 transmits a play command to the slave mobile terminals 22, the master and slave mobile terminals 21 and 22 start to simultaneously play the song, displaying its lyrics using the audio data, enabling users sing along. [0027]This method of providing the Karaoke service to mobile terminals by synchronizing them will be described below with reference to FIG. 3. [0028]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention. Referring to FIG. 3, the mobile terminals equipped with the functions of wireless Internet browsing, Karaoke music playing, and wireless connection are grouped in a service group in step 31. The wireless connections refer to connections between mobile terminals by Bluetooth, IRDA (Infrared Data Association), or wireless LAN (Local Area Network). The service group, corresponding to a working group in a PC (Personal Computer) network, is set by assigning the same wireless connection address to the mobile terminals. Thus, interference from other mobile terminals having a different wireless connection address is avoided. [0029]In step 32, one of the mobile terminals in the service group is designated as a mater mobile terminal with the other mobile terminals designated as slave terminals. The designation of master and slave MT's will be described in more detail hereinbelow with reference to FIG. 4. [0030]FIG. 4 illustrates examples of screen displays related to the Karaoke service in a mobile terminal according to the embodiment of the present invention. Referring to FIG. 4, a service group window 41 displays a wireless connection address assigned commonly to mobile terminals in the same service group, and a mobile terminal state window 42 displays the state of the mobile terminal, i.e., master or slave. [0031]To provide the Karaoke service in various modes, a slave grouping can be further divided into a slave channel 1, a slave channel 2, etc. If the Karaoke SP provides multichannel sound, that is, the audio is divided into discrete channels, center, left front, right front, left rear, and right rear, slave channel 1 outputs one of the channels such as the right channel for stereo sound or the left rear channel for digital surround sound 5.1, slave channel 2 outputs another channel, and the other channels output their respective channel sound. When sound from multiple sound sources is divided into 16- to 40-note polyphonic sounds, each channel may output its assigned sounds. [0032]The mobile terminal state is set to “master” only for a master mobile terminal. The master mobile terminal can remotely control the Internet and Karaoke functions of the slave mobile terminals through the wireless connections between them. [0033]Returning to FIG. 3, after the master mobile terminal 21 selects a song and requests the song from the Karaoke SP 15 through the mobile communication network 14, the master and slave mobile terminals 21 and 22 receive service contents related to the song from the Karaoke SP 15 in step 33. The contents reception is carried out in two ways, which will be described later with reference to FIGS. 5A and 5B. [0034]When the master mobile terminal 21 sends a play command to the slave mobile terminals 22 through wireless connection, for example, by Bluetooth, IRDA, or wireless LAN, all the mobile terminals 21 and 22 in the service group start to play the song simultaneously, synchronized according to a pilot channel clock signal in step 34. [0035]Upon request for a call setup for any mobile terminal in the service group during the music accompaniment playing, the mobile terminal is released from synchronization and connected to a call. The call setup request acts as an interrupt to the Karaoke service. [0036]FIGS. 5A and 5B illustrate embodiments of the contents reception in the Karaoke service using wireless connection between mobile terminals according to the present invention. Referring to FIG. 5A, a mobile terminal 51 is designated as a master and mobile terminals 52 are designated as slaves in a service group. After the service group is set in step 31 and the master and slave mobile terminals 51 and 52 are designated in step 32, the mobile terminals 51 and 52 receive service contents (i.e., Karaoke audio data) from the Karaoke SP 15 in step 33 in FIG. 4. [0037]Describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in the Karaoke SP 15 through the mobile communication network 14 in step 501 and transmits a contents receive command to the slave mobile terminals 52 in step 502. Since the master mobile terminal 51 can remotely control the wireless Internet function of the slave mobile terminals 52, the master mobile terminal 51 and the slave mobile terminals 52 under the control of the master mobile terminal 51 receive the same service contents in step 503. [0038]Referring to FIG. 5B, describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in step504 and receives receive service contents from the Karaoke SP 15 through the mobile communication network 14 in step 505. The master mobile terminal 51 then transmits the service contents to the slave mobile terminals by wireless connection in step 506. [0039]The contents receiving method illustrated in FIG. 5A enables each mobile terminal to receive a different channel or a different sound source since master and slave mobile terminals all access the Karaoke SP. If the SP prohibits content duplication and reproduction, retransmission of the service contents from the master mobile terminal to the slave mobile terminals is not permitted. In this sense, the method of FIG. 5A is useful. When accessing the SP, each slave mobile terminal transmits a packet indicating a slave channel to receive corresponding channel contents. [0040]Alternatively, rates for using service contents are saved and the same data can be broadcast to mobile terminals in the same service group in the content receiving method illustrated in FIG. 5B. [0041]As described above, the present invention offers the following benefits: (1) provision of Karaoke music with high volume, surround sound effects, and multiple sound sources improves the quality of the Karaoke service; (2) since a plurality of mobile terminals download the same audio data from an SP and users enjoy the Karaoke service through their mobile terminals together rather than alone, the number of service connections is increased and the novel service deployment attracts more customers from an SP's point of view; (3) the extension of the use of wireless data communication between mobile terminals enables mobile terminal manufacturers to create new customer demands; and (4) a program for carrying out the Karaoke service can be written on a computer-readable recording medium (e.g., CD ROM, RAM, floppy disk, hard disk, and optomagnetic disk). [0042]While the present invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. § 119 于 2003 年 2 月 13 日向韩国工业产权局提交的题为“使用移动终端之间的无线连接向移动终端提供卡拉 OK 服务的方法”的申请,编号为 2003-8989,其内容为 通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明总体上涉及一种通过移动终端提供服务的方法,具体地,涉及一种向移动终端提供卡拉OK服务的方法,以及提供一种计算机可读记录介质以在其上记录用于执行该服务的程序的计算机可读记录介质。 卡拉OK服务方法。 [0004] 2.相关技术的描述 [0005] 由于其便携性和便利性,移动终端已成为日常生活中的必需品。 通常,移动终端配备有电话簿、日程安排等多种功能。 因此,除了拨打电话之外,它们还充当个人信息管理器。 2.5 th 一代移动终端,基于IS(国际标准)-95C,和3 rd 一代移动终端,例如 IMT(国际移动通信)-2000 终端,为个人娱乐目的提供额外的多媒体服务。 [0006] 卡拉OK功能是一种个人娱乐服务,通过移动终端播放带有歌词和动画的各种类型的歌曲。 如图。 图1图示了用于提供传统卡拉OK服务的移动通信系统。 参考图。 如图1所示,卡拉OK服务是通过典型的移动通信网络提供的。 因此,卡拉OK服务是直接从移动通信网络上的服务提供商(SP)提供的,而不是来自移动通信网络本身的服务。 [0007] 移动通信系统由移动终端组成 11 为了通过移动通信网络接收卡拉 OK 服务,归属位置寄存器 (HLR) 12 和认证中心(AC) 13 用于提供移动终端的注册信息 11 , 移动通信网络 14 用于将 SP 连接到用户,以及卡拉 OK SP 15 提供卡拉OK服务。 [0008] 在操作中,移动终端的用户 11 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 然后通过 HLR 对用户进行身份验证 12 和交流 13 并将存储在其数据库中的音频数据提供给用户。 移动终端 11 使用接收到的音频数据播放带有歌词的歌曲,使用户能够跟着唱。 [0009] 一般而言,用户与他人而不是单独一起享受卡拉OK音乐。 单个移动终端播放的音乐音量取决于其扬声器,并且通常不足以让多个用户欣赏音乐。 另外,再好的音箱,单声源也无法为他们提供足够的音量。 [0010] 鉴于语音服务的多样化和格式的快速变化,卡拉 OK SP 15 试图通过新功能来吸引移动用户,例如伴奏包括立体声在内的多声道环绕声效果,或通过现有的仅限于 40 音符复音容量的移动终端伴奏更高音符的复音。 然而,在传统技术中,服务部署依赖于单个移动终端的性能,这些服务的好处往往难以捉摸。 发明内容 [0011] 因此,本发明的一个目的是提供一种卡拉OK服务方法,该方法使用配备有卡拉OK功能的移动终端之间的无线连接,通过移动终端同步来同时播放音乐伴奏,以及一种计算机可读记录。 用于在其上记录用于执行卡拉OK服务的程序的介质。 [0012]本发明的另一目的在于提供一种卡拉OK服务方法,用于播放具有高音量、环绕声效果和多种音源的音乐。 [0013] 通过提供一种通过无线连接向移动终端提供卡拉OK服务的方法,以及其上具有用于执行卡拉OK服务的程序的计算机可读记录介质来实现上述和其他目的。 [0014] 根据本发明的一个方面,在卡拉OK服务方法中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容。 主移动终端向从移动终端发送播放命令,所有移动终端根据服务内容开始播放卡拉OK音乐。 [0015] 根据本发明的另一方面,在卡拉OK服务方法中,将移动终端与移动终端分组在服务组中以接收卡拉OK服务,并指定为服务组中的主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 主移动终端收到播放指令后,根据服务内容开始播放卡拉OK音乐。 [0016] 根据本发明的另一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 在第一功能中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 在第一功能中被指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并在第二功能中控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容 . 主移动终端向从移动终端发送播放命令,然后所有移动终端根据第三功能中的服务内容开始播放卡拉OK音乐。 [0017] 根据本发明的又一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 该程序执行第一、第二和第三功能。 在第一个功能中,将移动终端与移动终端分组在一个服务组中以接收卡拉OK服务,并在服务组中将移动终端指定为主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在第二功能中在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 从移动终端接收到主移动终端的播放命令后,根据第三功能中的服务内容开始播放卡拉OK音乐。 附图的简要说明 [0018] 本发明的上述和其他目的、特征和优点将在以下结合附图的详细描述中变得更加明显,其中: [0019] 如图。 附图说明图1示出了向移动终端提供传统卡拉OK服务的移动通信系统; [0020]如图。 图2示出了根据本发明实施例的通过多个移动终端之间的无线连接向多个移动终端提供卡拉OK服务的移动通信系统的配置。 [0021] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 [0022] 如图。 图4示出了根据本发明实施例的通过与其他移动终端的无线连接来接收卡拉OK服务的移动终端中的屏幕显示示例。 和 [0023] 图 图5A和5B示出了根据本发明通过与其他移动终端的无线连接来接收卡拉OK服务的内容的实施例。 优选实施例的详细说明 [0024] 下面结合附图对本发明的优选实施例进行详细说明。 在以下描述中,没有详细描述众所周知的功能和结构,因为它们会以不必要的细节模糊本发明。 [0025] 如图。 图2图示了根据本发明实施例的用于通过移动终端之间的无线连接向移动终端提供卡拉OK服务的移动通信系统。 参考图。 2、移动通信系统由主移动终端组成 21 通过移动通信网络接收卡拉 OK 服务的 14 , 从移动终端 22 连接到主移动终端 21 ,为了接收相同的卡拉 OK 服务,HLR 12 和 SC 13 为移动终端提供注册信息 21 和 22 , 移动通信网络 14 用于将 SP 连接到移动用户,以及卡拉 OK SP 15 提供卡拉 OK 服务。 [0026] 在操作中,主移动终端 21 连接到从移动终端 22 ,形成服务群。 主移动终端用户 21 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 通过 HLR 对用户进行身份验证 12 和交流 13 并将音频数据传输到主移动终端 21 和从移动终端 22 . 当主控移动终端 21 向从移动终端发送播放命令 22 ,主从移动终端 21 和 22 开始同时播放歌曲,使用音频数据显示歌词,让用户跟着唱。 [0027] 下面将参照图3描述通过同步移动终端向移动终端提供卡拉OK服务的这种方法。 3. [0028] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 参考图。 3、将具备无线上网浏览、卡拉OK音乐播放、无线连接功能的移动终端分步归入一个服务组 31 . 无线连接是指移动终端之间通过蓝牙、IRDA(红外数据协会)或无线LAN(局域网)的连接。 通过为移动终端分配相同的无线连接地址来设置服务组,对应于PC(个人计算机)网络中的工作组。 因此,避免了来自具有不同无线连接地址的其他移动终端的干扰。 [0029] 在步骤 32 ,服务组中的一个移动终端被指定为主移动终端,其他移动终端被指定为从终端。 下文将参考图1更详细地描述主MT和从MT的指定。 4. [0030]如图。 图4图示了根据本发明实施例的移动终端中与卡拉OK服务相关的屏幕显示的示例。 参考图。 4、一个服务组窗口 41 显示同一服务组内移动终端通用分配的无线连接地址,移动终端状态窗口 42 显示移动终端的状态,即主或从。 [0031] 为了提供各种模式的卡拉OK服务,一个从属分组可以进一步划分为一个从属频道 1 , 从属通道 2 等。如果Karaoke SP提供多声道声音,即音频分为离散声道,中、左前、右前、左后、右后,从声道 1 输出其中一个声道,例如用于立体声的右声道或用于数字环绕声的左后声道 5 . 1 , 从通道 2 输出另一个通道,其他通道输出各自通道的声音。 当来自多个声源的声音被分成 16 到 40 音符的复音时,每个通道都可以输出其分配的声音。 [0032] 移动终端状态仅针对主移动终端设置为“主”。 主移动终端可以通过它们之间的无线连接远程控制从移动终端的上网和卡拉OK功能。 [0033] 返回图。 3、掌握移动端后 21 选择一首歌曲并向卡拉 OK SP 请求歌曲 15 通过移动通信网络 14 ,主从移动终端 21 和 22 从卡拉 OK SP 接收与歌曲相关的服务内容 15 在一步 33 . 内容接收以两种方式进行,这将在后面参考图3和图4进行描述。 参见图 5A 和 5B。 [0034] 当主控移动终端 21 向从移动终端发送播放命令 22 通过无线连接,例如通过蓝牙、IRDA或无线局域网,所有移动终端 21 和 22 在服务组中同时开始播放歌曲,根据一个导频通道时钟信号同步 34 . [0035] 在音乐伴奏播放期间,在服务组中的任何移动终端请求建立呼叫时,移动终端从同步中释放并连接到呼叫。 呼叫建立请求充当卡拉 OK 服务的中断。 [0036] 图 图5A和5B示出了根据本发明的使用移动终端之间的无线连接的卡拉OK服务中的内容接收的实施例。 参考图。 5A、移动终端 51 被指定为主机和移动终端 52 被指定为服务组中的从属设备。 步骤中设置服务组后 31 以及主从移动终端 51 和 52 在步骤中指定 32 , 移动终端 51 和 52 从卡拉 OK SP 接收服务内容(即卡拉 OK 音频数据) 15 在一步 33 在图 4. [0037] 描述步骤 33 更详细地说,主移动终端 51 从卡拉 OK SP 中的音乐数据库中选择一首歌曲 15 通过移动通信网络 14 在一步 501 向从移动终端发送内容接收命令 52 在一步 502 . 自主移动端 51 可远程控制从属移动终端的无线上网功能 52 ,主移动终端 51 和从移动终端 52 在主移动终端的控制下 51 在步骤中接收相同的服务内容 503 . [0038] 参考图。 5B,描述步骤 33 更详细地说,主移动终端 51 在步骤中从音乐数据库中选择一首歌曲 504 并从卡拉 OK SP 接收接收服务内容 15 通过移动通信网络 14 在一步 505 . 主控移动终端 51然后在步骤中通过无线连接将服务内容传输到从移动终端 506 . [0039] 图1所示的内容接收方法。 由于主移动终端和从移动终端都访问卡拉OK SP,因此图5A使每个移动终端能够接收不同的频道或不同的声源。 如果SP禁止内容复制和再现,则不允许将服务内容从主移动终端重传到从移动终端。 在这个意义上,图1的方法。 5A很有用。 在接入SP时,每个从移动终端发送一个指示从信道的分组以接收相应的信道内容。 [0040] 或者,在图1所示的内容接收方法中,可以保存使用服务内容的费率并将相同的数据广播到相同服务组中的移动终端。 5B。 [0041] 如上所述,本发明提供以下益处: (1)提供具有高音量、环绕声效果和多声源的卡拉OK音乐,提高了卡拉OK服务的质量。 (2)由于多个移动终端从一个SP下载相同的音频数据,用户通过他们的移动终端一起而不是单独享受卡拉OK服务,增加了服务连接的数量,新颖的业务部署吸引了更多来自SP的客户 观点看法; (3)移动终端之间无线数据通信使用的延伸,使移动终端制造商能够创造新的客户需求; (4)可以将用于进行卡拉OK服务的程序写入计算机可读取的记录介质(例如CD ROM、RAM、软盘、硬盘、光磁盘)上。 [0042] 尽管本发明已经参照其某些优选实施例进行了展示和描述,但本领域技术人员将理解,在不背离所定义的本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变 根据所附权利要求。(String), 111526(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.125 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), CN1295910C(String), 1046990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), CN1522010A(String), 1046991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), KR100532288B1(String), 1046992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), KR1020040073057A(String), 1046993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), US20040162062A1(String), 1046994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270638(Integer), US7142807B2(String), 1046995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7142807B2(String), US7142807B2(String), 1164643200(Integer), 270638(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.143 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184955(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.206 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.206 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.208 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.208 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.209 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.209 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.209 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.211 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.211 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.211 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8c89a54fe85b40e5aaf4f81e83c30798.png(String), 184956(Integer), 8c89a54fe85b40e5aaf4f81e83c30798.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.263 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.264 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.264 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of changing standby order of waiting mobile terminals in mobile terminal(String), 移动终端中更改等待移动终端待机顺序的方法(String), US7801528B2(String), A method for changing a standby order of waiting mobile terminals includes displaying a standby order of a plurality of mobile terminals according to an audiovisual communication request order when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal, sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a standby order change request, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message, and displaying the changed standby order.(String), 一种用于改变等待移动终端的待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求,而第一移动终端时,根据视听通信请求顺序显示多个移动终端的待机顺序。 与第二移动终端进行视听通信,当第一移动终端接收到待机指令变更请求时,从第一移动终端向移动通信网络发送待机指令变更请求消息,当第一移动终端接收到待机指令变更请求时,变更第一移动终端的待机指令。 移动终端从移动通信网络接收对应于待机命令更改请求消息的待机命令更改完成消息,并显示更改后的待机命令。(String), US11/769201(String), 1182873600(Integer), US7801528B2(String), 1284998400(Integer), 1284998400(Integer), 美国(String), 2(Integer), 4(Integer), KR(String), 2(Integer), 12(Integer), KR1020000042764A | KR1020050017736A | KR1020050053912A | KR1020070012088A | US20020009987A1 | US20030104830A1 | US20060223593A1 | US20080132254A1(String), \20230420\8c89a54fe85b40e5aaf4f81e83c30798.png(String), 17(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 1. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals, according to the order in which the audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a request to change the standby order;changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message; anddisplaying the changed standby order.(String), 1.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序,而第一移动终端终端与第二移动终端进行视听通信;当第一移动终端接收到待机顺序变更请求时,第一移动终端向移动通信网络发送待机顺序变更请求消息;当第一移动终端从移动通信网络接收到与待机顺序变更请求消息对应的待机顺序变更完成消息时,变更第一移动终端的待机顺序;和显示更改后的待机顺序。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 2. The method of claim 1, further comprising:changing the standby order at the mobile communication network in response to the standby order change request message sent by the first mobile terminal.(String), 2.如权利要求1所述的方法,还包括:响应于第一移动终端发送的待机顺序改变请求消息,改变移动通信网络处的待机顺序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 3. The method of claim 2, further comprising sending the changed standby order to the first mobile terminal through the mobile communication network.(String), 3.如权利要求2所述的方法,还包括通过移动通信网络向第一移动终端发送变更后的待机指令。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 4. The method of claim 1, further comprising performing audiovisual communication with another mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 4.如权利要求1所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与另一移动终端进行视听通信。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 5. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals according to the order in which audiovisual communication request orders of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals;changing the standby order if the first mobile terminal approves the requested change of the standby order; anddisplaying the changed standby order.(String), 5.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求命令的顺序显示多个移动终端的待机顺序,而第一移动终端与第二移动终端进行视听通信;当第一移动终端接收到多个移动终端中的第三移动终端的待机顺序变更请求消息时,判断第一移动终端是否同意请求的待机顺序变更;如果第一移动终端同意请求更改备用订单,则更改备用订单;和显示更改后的待机顺序。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 6. The method of claim 5, wherein determining whether the first mobile terminal approves the requested change of the standby order comprises:receiving the standby order change request message of the third mobile terminal from a mobile communication network; andsending a standby order change approval message to the mobile communication network when the standby order change request is approved in response to the received standby order change request message.(String), 6.如权利要求5所述的方法,其中判断第一移动终端是否同意请求的待机顺序变更包括:从移动通信网络接收第三移动终端的待机顺序变更请求消息;和当响应于接收到的备用订单变更请求消息批准备用订单变更请求时,向移动通信网络发送备用订单变更批准消息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 7. The method of claim 6, wherein changing the standby order comprises:receiving a standby order change completion message from the mobile communication network; andchanging the standby order according to the standby order change completion message.(String), 7.如权利要求6所述的方法,其中更改备用订单包括:接收来自移动通信网络的备用订单变更完成消息;和根据备用订单变更完成消息变更备用订单。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 8. The method of claim 6, wherein receiving the standby order change request message of the third mobile terminal comprises:sending a standby order change request message from the third mobile terminal to the mobile communication network; andreceiving the standby order change request message of the third mobile terminal from the mobile communication network in the first mobile terminal.(String), 8.如权利要求6所述的方法,其中接收第三移动终端的待机顺序变更请求消息包括:第三移动终端向移动通信网络发送待机顺序变更请求消息;和第一移动终端中从移动通信网络接收第三移动终端的待机顺序变更请求消息。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 9. The method of claim 8, wherein changing the standby order comprises:receiving the standby order change approval message sent from the first mobile terminal in the mobile communication network; andchanging the standby order.(String), 9.如权利要求8所述的方法,其中更改备用订单包括:接收移动通信网络中的第一移动终端发送的备用订单变更批准消息;和更改待机顺序。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 10. The method of claim 9, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal.(String), 10.如权利要求9所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端发送待机顺序改变完成消息。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 11. The method of claim 8, wherein the standby order change request message sent from the third mobile terminal is sent by the mobile communication network to the first mobile terminal and to a fourth mobile terminal of the plurality of mobile terminals.(String), 11.如权利要求8所述的方法,其中第三移动终端发送的待机顺序变更请求消息由移动通信网络发送给第一移动终端和多个移动终端中的第四移动终端。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 12. The method of claim 11, wherein changing the standby order comprises:receiving response messages to the standby order change request message from the first mobile terminal and from the fourth mobile terminal in the communication network; andchanging the standby order.(String), 12.如权利要求11所述的方法,其中更改备用订单包括:从通信网络中的第一移动终端和第四移动终端接收对待机顺序改变请求消息的响应消息;和更改待机顺序。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 13. The method of claim 12, wherein the mobile communication network changes the standby order according to the response messages if the response messages received from the first mobile terminal and from the fourth mobile terminal are identical.(String), 13.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息相同,则移动通信网络根据响应消息改变待机顺序。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 14. The method of claim 12, wherein the mobile communication network changes the standby order according to the response message of the first mobile terminal if the response messages received from the first mobile terminal and from the fourth mobile terminal are not identical.(String), 14.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息不相同,则移动通信网络根据第一移动终端的响应消息改变待机顺序。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 15. The method of claim 14, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal, the third mobile terminal, and the fourth mobile terminal.(String), 15.如权利要求14所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端、第三移动终端和第四移动终端发送待机顺序改变完成消息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 16. The method of claim 12, wherein the response message to the standby order change request message is one of a standby order change approval message and a standby order change non-approval message.(String), 16.如权利要求12所述的方法,其中备用订单变更请求消息的响应消息为备用订单变更批准消息和备用订单变更不批准消息之一。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.290 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184956(Integer), 17. The method of claim 5, further comprising performing audiovisual communication with a mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 17.如权利要求5所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与移动终端进行视听通信。(String), 1(Integer), 16(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111527(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184956(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority from and the benefit of Korean Patent Application No. 10-2007-0004601, filed on Jan. 16, 2007, which is hereby incorporated by reference for all purposes as if fully set forth herein. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method of providing an audiovisual communication service in a mobile terminal, and more particularly, to a method of changing a standby order of waiting mobile terminals in a mobile terminal. [0004]2. Discussion of the Background [0005]As technology of mobile terminals has developed, an improved mobile terminal having a camera unit using an H.324M protocol including an H.245 protocol that allows for audiovisual communication has been provided. [0006]In conventional audiovisual communication technology, when a first mobile terminal receives a request for audiovisual communication from a third mobile terminal while the first mobile terminal is performing audiovisual communication with a second mobile terminal, the first mobile terminal stores information about the third mobile terminal. Thereafter, when the first mobile terminal ends audiovisual communication with the second mobile terminal, the first mobile terminal displays information about the third mobile terminal and performs audiovisual communication with the third mobile terminal. [0007]However, in the conventional audiovisual communication technology, even when the third mobile terminal urgently requests audiovisual communication with the first mobile terminal, the third mobile terminal may have to wait until the first mobile terminal ends audiovisual communication with the second mobile terminal. SUMMARY OF THE INVENTION [0008]The present invention provides a method of changing a standby order of at least two mobile terminals requesting audiovisual communication while a first mobile terminal is performing audiovisual communication. [0009]The present invention further provides a method of changing a standby order of mobile terminals in a standby state according to a standby order change request received from one of at least two mobile terminals waiting for audiovisual communication with the first mobile terminal while the first mobile terminal is performing audiovisual communication. [0010]The present invention further provides a method of displaying information about a mobile terminal requesting audiovisual communication while a first mobile terminal is performing audiovisual communication with a second mobile terminal. [0011]Additional features of the invention will be set forth in the description which follow, and in part will be apparent from the description, or may be learned by practice of the invention. [0012]The present invention discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, sending a standby order change request message to a mobile communication network from the first mobile terminal when the first mobile terminal receives a request to change the standby order, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message corresponding to the standby order change request message, and displaying the changed standby order. [0013]The present invention also discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals, changing the standby order if the first mobile terminal approves the requested change of the standby order, and displaying the changed standby order. [0014]It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. [0016]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0017]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0018]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0019]FIG. 4 is a flowchart showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0020]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0021]FIG. 6 is a flowchart showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0022]FIG. 7 is a message flow diagram showing another method of performing audiovisual communication with waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS [0023]The invention is described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements. [0024]It will be understood that when an element or layer is referred to as being “on” or “connected to” another element or layer, it can be directly on or directly connected to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on” or “directly connected to” another element or layer, there are no intervening elements or layers present. [0025]Exemplary embodiments according to the present invention exemplify a mobile terminal that includes a camera unit and is capable of performing audiovisual communication. That is, a mobile terminal according to exemplary embodiments of the present invention may include an information communication device or multimedia device, such as a mobile communication terminal, a mobile phone, a Personal Digital Assistant (PDA), a smart phone, or a notebook computer, that includes a camera unit and is capable of performing audiovisual communication, and applications thereof. [0026]Exemplary embodiments according to the present invention exemplify audiovisual communication. However, the present exemplary embodiments are not limited to audiovisual communication and may be applied to voice communication. [0027]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0028]Referring to FIG. 1, the system includes a first mobile terminal 100, a second mobile terminal 200, a third mobile terminal 300, a fourth mobile terminal 400, and a mobile communication network 500. [0029]The first mobile terminal may perform audiovisual communication with the second mobile terminal 200 and may receive a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400 while performing audiovisual communication with the second mobile terminal 200. A configuration of the first mobile terminal 100 is described with reference to FIG. 2, and the same configuration may also be applied to the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 and thus, individual descriptions thereof are omitted. [0030]The mobile communication network 500 includes a node to perform the function of a base station, a radio access network (RAN), which is a sub system of the node, a mobile switching center (MSC)/visitor location register (VLR) corresponding to a core network of a circuit switched domain, a home location register (HLR), and a gateway MSC. [0031]The MSC manages call control and mobility of the first mobile terminal 100, and the VLR and the HLR make up a matching device of subscriber information and register and manage information about mobile terminals belonging to the mobile communication network 500 including the first mobile terminal 100. [0032]In the following description, the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 belong to the same mobile communication network 500. However the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 may belong to different mobile communication networks and may be connected through different gateway MSCs. However, it is assumed that a series of processes performed in the RAN, MSC/VLR, HLR, and gateway MSC are performed in the mobile communication network 500. [0033]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0034]Referring to FIG. 2, the mobile terminal 100 includes a radio frequency (RF) unit 101, an input unit 103, a controller 105, a camera unit 107, an image processor 109, a display unit 111, a memory unit 113, and an audio unit 115. [0035]The RF unit 101 performs general wireless communication with the second mobile terminal 200, the third mobile terminal 300, the fourth mobile terminal 400, and the mobile communication network 500. For example, the RF unit 101 transmits and receives voice data, character messages, and multimedia messages using the mobile communication network 500. The RF unit 101 sends image data acquired from the camera unit 107 of the first mobile terminal 100 to the second mobile terminal 200 when the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 200. The RF unit 101 further receives image data acquired by the camera unit of the second mobile terminal 200 and image data acquired by the camera units of the third mobile terminal 300 and the fourth mobile terminal 400 requesting audiovisual communication. The image data of the second mobile terminal 200 may be still and/or moving picture data, and the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be still and/or moving image data. Further, when the third mobile terminal 300 and the fourth mobile terminal 400 perform audiovisual communication with the first mobile terminal 100, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may change to moving picture data. [0036]The input unit 103 may include a general keypad. The input unit 103 may include a touch screen, a touch pad, and a scroll wheel. The input unit 103 receives a user manipulation signal to control operation of the first mobile terminal 100 and provides the manipulation signal to the controller 105. [0037]The controller 105 controls the general operation of the first mobile terminal 100. Particularly, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200, receives a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400, and sets a standby order of audiovisual communication requests. The controller 105 displays image data (namely, image data of a user of the second mobile terminal 200) of the second mobile terminal 200 performing audiovisual communication in the display unit 111. The controller 105 displays image data from each mobile terminal requesting audiovisual communication, in the order in which the audiovisual communication requests were received, on the display unit 111 of the first terminal 100. [0038]In more detail, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be image data mapped to the corresponding mobile terminal and stored in a phone book (not shown) of the first mobile terminal 100. The image data may also be image data acquired by camera units of the third mobile terminal 300 and the fourth mobile terminal 400 when requesting audiovisual communication and may be sent with the request for audiovisual communication. The controller 105 may display the image data of the third mobile terminal 300 and the fourth mobile terminal 400 with thumb-nail type still image data. The controller 105 may also display image data of the second mobile terminal 200, with which the first mobile terminal 100 is performing audiovisual communication, including moving picture data. [0039]The controller 105 sends a standby order change request message REQ_MSG from the first mobile terminal 100 to the mobile communication network 500 through the RF unit 101, receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the changed standby order in the display unit 111. [0040]The controller 105 further receives a standby order change request message REQ_MSG from the mobile terminal having the highest standby position through the mobile communication network 500 and sends a standby order change approval message ACC_MSG to the mobile communication network 500 through the RF unit 101. Thereafter, the controller 105 receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the standby order in the display unit 111. [0041]When the controller 105 determines that the first mobile terminal 100 has ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 controls the RF unit 101 to perform audiovisual communication with the mobile terminal having the highest standby position. In the exemplary embodiments, to “end” the audiovisual communication is to terminate a communication channel formed to perform audiovisual communication with the second mobile terminal 200, and to “convert” an audiovisual communication state to a standby state is to convert to a standby state in order to perform audiovisual communication with another mobile terminal while maintaining the communication channel formed to perform audiovisual communication with the second mobile terminal 200. [0042]The camera unit 107 generates a user's image data to send through the RF unit 101. The camera unit 107 includes an image sensor to convert a photo signal of a subject to an analog signal and a signal processor to convert the analog signal to a digital signal. That is, the camera unit 107 converts a photo signal collected through a lens to a digital signal and generates image data with the converted digital signal. [0043]The image processor 109 processes image data generated in the camera unit 107 and image data received through the RF unit 101 into a format corresponding to the display unit 111. [0044]The controller 105 controls the display unit 111 to display various operation states, operation results, and other information from the units of the first mobile terminal 100. The display unit 111 may include a display device such as a liquid crystal display (LCD), organic light emitting diodes (OLED), or a plasma display panel (PDP). [0045]The display unit 111 displays image data input through the RF unit 101 and the camera unit 107 and processed in the image processor 109 in real time, thereby performing audiovisual communication or displaying a photographed image. [0046]The memory unit 113 stores information (for example, information about a setting state and a menu) related to operation of a program allowing the controller 105 to control the first mobile terminal 100. The memory unit 113 stores the standby order of the third mobile terminal 300 and the fourth mobile terminal 400. The memory unit 113 stores image data received from the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400, and may also store image data mapped to a corresponding terminal in a phone book (not shown) of the first mobile terminal 100. [0047]The audio unit 115 converts an analog audio signal that is input through a microphone MIC to a digital signal, provides the digital signal to the controller 105, converts a digital audio signal that is output from the controller 105 into an analog audio signal, and reproduces the analog audio signal through a speaker SPK. [0048]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0049]Referring to FIGS. 3A and 3B, while the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 100 (S301), the mobile communication network 500 receives a request for audiovisual communication from the third mobile terminal 300 (S303). At step S301, the first mobile terminal 100 is in an audiovisual communication state, the camera unit 107 of the first mobile terminal 100 acquires an image of a user of the first mobile terminal 100, the image processor 109 processes the user image, the display unit 111 displays the user image, and the microphone MIC and the speaker SPK are converted to an operation state. [0050]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S305). [0051]The third mobile terminal 300 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S307). If the third mobile terminal 300 sustains an audiovisual communication standby state, the third mobile terminal 300 sends a standby state sustenance message to the mobile communication network 500 (S309). [0052]Thereafter, the mobile communication network 500 sends information about the third mobile terminal 300 to the first mobile terminal 100 (S311) and forms a communication channel between the first mobile terminal 100 and the third mobile terminal 300. The information about the third mobile terminal 300 may include contact information and image data of the third mobile terminal 300. [0053]The mobile communication network 500 receives a request for audiovisual communication from the fourth mobile terminal 400 (S313), and sends a message regarding the state of the first mobile terminal 100 to the fourth mobile terminal 400 to notify the fourth mobile terminal 400 that the first mobile terminal 100 is performing audiovisual communication (S315). [0054]The fourth mobile terminal 400 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S317). If the fourth mobile terminal 400 sustains an audiovisual communication standby state, the fourth mobile terminal 400 sends a standby state sustenance message to the mobile communication network 500 (S319). [0055]Thereafter, the mobile communication network 500 sends information about the fourth mobile terminal 400 to the first mobile terminal 100 (S321) and forms a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400. The information about the fourth mobile terminal 400 may include contact information and image data of the fourth mobile terminal 400. [0056]The first mobile terminal 100 determines that a communication channel between the first mobile terminal 100 and the third mobile terminal 300 was formed at step S311, and that a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400 is formed at step S321. [0057]Thereafter, the first mobile terminal 100 sets and displays a standby order of the mobile terminals that have requested audiovisual communication by listing the mobile terminals in the order in which their requests were received (S323). In the present exemplary embodiment, because the third mobile terminal 300 requested audiovisual communication earlier than the fourth mobile terminal 400, the third mobile terminal 300 has the highest standby position. [0058]When the first mobile terminal 100 wants to change the displayed standby order (S325), the first mobile terminal 100 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S327). The request to change the standby order is input by selecting image data of the third mobile terminal 300 and the fourth mobile terminal 400 displayed in a change mode or a standby order. [0059]The mobile communication network 500 receives the standby order change request message REQ_MSG and changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 (S329). [0060]The mobile communication network 500 temporarily stores the changed standby order (S331) and sends a standby order change completion message RES_MSG informing the first mobile terminal 100 of the standby order change of the third mobile terminal 300 and the fourth mobile terminal 400 (S333). [0061]The first mobile terminal 100 changes and displays the standby order according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S335). [0062]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S337), the mobile communication network 500 refers to the changed standby order that was temporarily stored at step 331 (S339) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S341). [0063]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S343). [0064]FIG. 4 is a flowchart showing a method of changing the standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0065]Referring to FIG. 4, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200 (S401). The controller 105 displays moving picture data received in real time from the second mobile terminal 200 in the display unit 111. When the mobile terminal 100 receives a request for audiovisual communication from at least one mobile terminal while performing audiovisual communication (S403), the controller 105 determines whether the number of the mobile terminals requesting audiovisual communication is at least two (S405). [0066]If there are at least two mobile terminals requesting audiovisual communication, the controller 105 sets a standby order according to the order in which the requests for audiovisual communication were received and displays the set standby order on the display unit 111 (S407). The controller 105 displays image data received from the mobile terminals requesting audiovisual communication or image data mapped to a phone number of the mobile terminals and stored in a phone book (not shown) on the display unit 111 in the order in which their audiovisual communication requests were received. [0067]The controller 105 determines whether the set standby order has changed (S409). If the set standby order has not change, the process continues at step S419. [0068]If the set standby order has changed, the controller 105 controls the RF unit 101 to send a message REQ_MSG requesting that the standby order of the mobile terminals (here, the third mobile terminal 300 and the fourth mobile terminal 400) be changed through the mobile communication network 500 (S411). [0069]Thereafter, the controller 105 receives a standby order change completion message RES_MSG sent from the mobile communication network 500 through the RF unit 101 (S415). The controller 105 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the received standby order change completion message RES_MSG and displays the changed standby order on the display unit 111 (S417). [0070]The controller 105 determines whether the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S419). If the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 determines whether mobile terminals waiting for audiovisual communication exist, and if mobile terminals waiting for audiovisual communication exist, the first mobile terminal 100 performs audiovisual communication with the mobile terminal having the highest standby position (S421). The first mobile terminal 100 may perform audiovisual communication with the fourth mobile terminal 400, whose standby order position is changed to the highest position at step S417, or with the third mobile terminal 300, which has the highest position in the standby order set at step S407. [0071]If the number of the mobile terminals requesting audiovisual communication is not at least two at step 405, the controller 105 determines whether the first mobile terminal 100 has either ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state (S423). When the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the first mobile terminal 100 performs audiovisual communication with the mobile terminal requesting audiovisual communication (S425). [0072]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0073]Referring to FIGS. 5A and 5B, steps S501 to S523 of FIG. 5A are substantially the same as steps S301 to S323 of FIG. 3A and thus description thereof is omitted. [0074]If the fourth mobile terminal 400 having a standby order position that is lower than that of the third mobile terminal 300 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S525), the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100 (S527), and the mobile communication network 500 sends the standby order change request message REQ_MSG to the third mobile terminal 300 (S529). The standby order change request message REQ_MSG may be sent by the fourth mobile terminal 400 at the same time the fourth mobile terminal 400 sends an audiovisual communication request message to the mobile communication network 500 at step S513. [0075]The first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG (S531), and the third mobile terminal 300 approves the change of the standby order in response to the standby order change request message REQ_MSG (S533). [0076]The first mobile terminal 100 then sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S535), and the third mobile terminal 300 sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S537). [0077]The mobile communication network 500 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change approval message ACC_MSG received from the first mobile terminal 100 at step S535 and from the third mobile terminal 300 at step S537 (S539). [0078]The mobile communication network 500 temporarily stores a changed standby order (S541) and sends a standby order change completion message RES_MSG to the first mobile terminal 100(S543), the third mobile terminal 300 (S545), and the fourth mobile terminal 400(S547). [0079]The first mobile terminal 100 changes and displays the standby order set at the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S549). [0080]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S551), the mobile communication network 500 refers to the changed standby order temporarily stored at step S541 (S553) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S555). [0081]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S557). [0082]Another method of changing a standby order of waiting mobile terminals according to another exemplary embodiment of the present invention (not shown in the Figures) is described as follows. [0083]When the mobile communication network 500 receives a standby order change request message REQ_MSG from the fourth mobile terminal 400, the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100. [0084]Thereafter, if the first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG, the first mobile terminal 100 sends a standby order change approval message ACC_MSG confirming the approval to the mobile communication network 500. When th(String), 相关申请的交叉引用 [0001] 本申请要求于 2007 年 1 月 16 日提交的韩国专利申请号 10-2007-0004601 的优先权和权益,其在此通过引用并入所有目的,就好像在此完全阐述一样。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种在移动终端中提供视听通信服务的方法,更具体地,涉及一种在移动终端中改变等待移动终端的待机顺序的方法。 [0004] 2. 背景讨论 [0005] 随着移动终端技术的发展,已经提供了一种改进的移动终端,其具有使用H.324M协议的相机单元,该H.324M协议包括允许视听通信的H.245协议。 [0006] 在传统的视听通信技术中,当第一移动终端在与第二移动终端进行视听通信时,当第一移动终端接收到来自第三移动终端的视听通信请求时,第一移动终端存储关于第三移动终端的信息。 之后,当第一移动终端结束与第二移动终端的视听通信时,第一移动终端显示第三移动终端的信息,并与第三移动终端进行视听通信。 [0007] 然而,在现有的视听通信技术中,即使第三移动终端紧急请求与第一移动终端进行视听通信,第三移动终端也可能不得不等待,直到第一移动终端结束与第二移动终端的视听通信。 发明内容 [0008] 本发明提供了一种在第一移动终端正在执行视听通信时改变请求视听通信的至少两个移动终端的待机顺序的方法。 [0009] 本发明还提供了一种根据从等待与第一移动终端进行视听通信的至少两个移动终端之一接收到的待机顺序改变请求来改变处于待机状态的移动终端的待机顺序的方法,同时第一移动终端是 进行视听交流。 [0010] 本发明还提供了一种在第一移动终端正在与第二移动终端进行视听通信时显示关于请求视听通信的移动终端的信息的方法。 [0011] 本发明的附加特征将在随后的描述中阐述,并且部分地从描述中变得显而易见,或者可以通过本发明的实践来了解。 [0012] 本发明公开了一种用于在移动通信系统中改变待机顺序的方法,包括当第一移动终端时,根据接收到多个移动终端的视听通信请求的顺序,显示多个移动终端的待机顺序。 当第一移动终端正在与第二移动终端进行视听通信时,终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到来自第一移动终端的待机命令更改请求消息到移动通信网络时 请求更改待机命令,当第一移动终端接收到与待机命令更改请求消息对应的待机命令更改完成消息时,在第一移动终端更改待机命令,并显示更改后的待机命令。 [0013]本发明还公开了一种在移动通信系统中改变待机顺序的方法,包括根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序。 当第一移动终端与第二移动终端进行视听通信时,移动终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到待机时,确定第一移动终端是否批准请求的待机顺序变更 所述多个移动终端中的第三移动终端的订单更改请求消息,如果第一移动终端批准请求的待机订单更改,则更改待机订单,并显示更改后的待机订单。 [0014] 应当理解,前面的一般描述和下面的详细描述都是示例性和解释性的,并且旨在提供对所要求保护的本发明的进一步解释。 附图的简要说明 [0015] 附图被包括以提供对本发明的进一步理解并且被并入并构成本说明书的一部分,它们说明了本发明的实施例,并且与描述一起用于解释本发明的原理。 [0016] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0017] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0018] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0019] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0020] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0021] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0022] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 图示实施例的详细说明 [0023] 下文参照附图更全面地描述本发明,其中示出了本发明的实施例。 然而,本发明可以以许多不同的形式来体现,并且不应被解释为限于这里阐述的实施例。 相反,提供这些实施例是为了使本公开是彻底的,并且将向本领域技术人员充分传达本发明的范围。 在附图中,为了清楚起见,可能夸大了层和区域的尺寸和相对尺寸。 图中相同的附图标记表示相同的元件。 [0024] 应当理解,当一个元件或层被称为“在”另一个元件或层上或“连接到”另一个元件或层时,它可以直接在另一个元件或层上或直接连接到另一个元件或层,或者中间的元件或层可以是 当下。 相反,当一个元素被称为“直接在”或“直接连接到”另一个元素或层时,不存在中间的元素或层。 [0025]根据本发明的示例性实施例举例说明了包括照相机单元并且能够执行视听通信的移动终端。 也就是说,根据本发明示例性实施例的移动终端可以包括信息通信设备或多媒体设备,例如移动通信终端、移动电话、个人数字助理(PDA)、智能电话或笔记本电脑 包括照相机单元并能够进行视听通信的计算机及其应用。 [0026] 根据本发明的示例性实施例举例说明了视听通信。 然而,本示例性实施例不限于视听通信并且可以应用于语音通信。 [0027] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0028] 参考图。 1、系统包括第一移动终端 100 ,第二个移动终端 200 ,第三个移动终端 300 ,第四个移动终端 400 , 和一个移动通信网络 500 . [0029] 第一移动终端可以与第二移动终端进行视听通信 200 并且可以接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 在与第二移动终端进行视听通信的同时 200 . 第一移动终端的配置 100 参照图1描述。 如图2所示,同样的配置也可以应用于第二移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 因此,省略其个别描述。 [0030] 移动通信网络 500 包括执行基站功能的节点、作为节点的子系统的无线接入网络 (RAN)、对应于一个核心网络的移动交换中心 (MSC)/访问者位置寄存器 (VLR) 电路交换域、归属位置寄存器 (HLR) 和网关 MSC。 [0031] MSC管理第一移动终端的呼叫控制和移动性 100 ,VLR和HLR组成用户信息匹配装置,注册和管理属于移动通信网络的移动终端信息 500 包括第一移动终端 100 . [0032] 在下面的描述中,第一移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 属于同一个移动通信网络 500 . 然而第一款移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 可能属于不同的移动通信网络,可能通过不同的网关MSC连接。 然而,假设在移动通信网络中执行在RAN、MSC/VLR、HLR和网关MSC中执行的一系列处理 500 . [0033] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0034] 参考图。 2、移动端 100 包括一个射频 (RF) 单元 101 , 一个输入单元 103 , 一个控制器 105 , 一个相机单元 107 , 图像处理器 109 , 一个显示单元 111 , 一个记忆单元 113 , 和一个音频单元 115 . [0035] 射频单元 101 与第二移动终端进行一般无线通信 200 , 第三个移动终端 300 ,第四个移动终端 400 , 和移动通信网络 500 . 例如,射频单元 101 使用移动通信网络发送和接收语音数据、字符消息和多媒体消息 500 . 射频单元 101 发送从相机单元获取的图像数据 107第一个移动终端 100 到第二个移动终端 200 当第一个移动终端 100 与第二移动终端进行视听通信 200 . 射频单元 101 还接收第二移动终端的摄像单元获取的图像数据 200 第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 请求视听通信。 第二移动终端的图像数据 200 可以是静止和/或运动图像数据,第三移动终端的图像数据 300 和第四个移动终端 400 可以是静止和/或运动图像数据。 进一步地,当第三移动终端 300 和第四个移动终端 400 与第一移动终端进行视听通信 100 ,第三个移动终端的图像数据 300 和第四个移动终端 400 可能会更改为运动图像数据。 [0036] 输入单元 103 可能包括一个通用键盘。 输入单元 103 可以包括触摸屏、触摸板和滚轮。 输入单元 103 接收用户操作信号以控制第一移动终端的操作 100 并向控制器提供操纵信号 105 . [0037] 控制器 105 控制第一移动终端的一般操作 100 . 特别是控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 ,接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 ,并设置视听通信请求的待机顺序。 控制器 105 显示图像数据(即第二移动终端用户的图像数据) 200 )的第二个移动终端 200 在显示单元中进行视听通信 111 . 控制器 105 在显示单元上按照接收到视听通信请求的顺序显示来自请求视听通信的每个移动终端的图像数据 111 第一个终端的 100 . [0038] 更详细地说,第三移动终端的图像数据 300 和第四个移动终端 400 可以是映射到对应的移动终端并存储在第一移动终端的电话簿(未示出)中的图像数据 100 . 图像数据也可以是第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 当请求视听通信时,可能会与视听通信请求一起发送。 控制器 105 可以显示第三移动终端的图像数据 300 和第四个移动终端 400 缩略图类型的静止图像数据。 控制器 105 还可以显示第二移动终端的图像数据 200 ,其中第一款移动终端 100 正在执行视听通信,包括运动图像数据。 [0039] 控制器 105 从第一移动终端发送备用订单更改请求消息REQ_MSG 100 到移动通信网络 500 通过射频单元 101 ,接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面中显示更改后的待机顺序 111 . [0040] 控制器 105 进一步通过移动通信网络从具有最高待机位置的移动终端接收待机顺序更改请求消息REQ_MSG 500 向移动通信网络发送待命订单变更批准消息ACC_MSG 500 通过射频单元 101 . 此后,控制器 105 接收来自移动通信网络的备用订单更改完成消息RES_MSG 500通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面显示待机命令 111 . [0041] 当控制器 105 确定第一移动终端 100 已结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 控制射频单元 101 与待机位置最高的移动终端进行视听通信。 在示例性实施例中,“结束”视听通信是终止形成用于与第二移动终端进行视听通信的通信信道 200 ,并且将视听通信状态“转换”为待机状态是为了在保持与第二移动终端执行视听通信而形成的通信信道的同时,转换为待机状态以便与另一个移动终端执行视听通信。 200 . [0042] 相机单元 107 生成用户的图像数据以通过射频单元发送 101 . 相机单元 107 包括将对象的照片信号转换为模拟信号的图像传感器和将模拟信号转换为数字信号的信号处理器。 也就是相机单元 107 将通过镜头采集的照片信号转换为数字信号,并利用转换后的数字信号生成图像数据。 [0043] 图像处理器 109 处理相机单元中生成的图像数据 107 和通过射频单元接收的图像数据 101 转换成与显示单元对应的格式 111 . [0044] 控制器 105 控制显示单元 111 显示第一移动终端各单元的各种操作状态、操作结果等信息 100 . 显示单元 111 液晶显示器(LCD)、有机发光二极管(OLED)或等离子体显示面板(PDP)等显示装置可以包括显示装置。 [0045] 显示单元 111 显示通过射频单元输入的图像数据 101 和相机单元 107 并在图像处理器中处理 109 实时,从而进行视听通信或显示拍摄的图像。 [0046] 记忆单元 113 存储与允许控制器的程序的操作有关的信息(例如,关于设置状态和菜单的信息) 105 控制第一移动终端 100 . 记忆单元 113 存储第三移动终端的待机指令 300 和第四个移动终端 400 . 记忆单元 113 存储从第二移动终端接收的图像数据 200 , 第三个移动终端 300 ,以及第四个移动终端 400 ,并且还可以将映射到对应终端的图像数据存储在第一移动终端的电话簿(未示出)中 100 . [0047] 音频单元 115 将通过麦克风 MIC 输入的模拟音频信号转换为数字信号,将数字信号提供给控制器 105 , 转换从控制器输出的数字音频信号 105 转换成模拟音频信号,并通过扬声器SPK再现模拟音频信号。 [0048] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0049] 参考图。 参照图3A和3B,同时第一移动终端 100 与第二移动终端进行视听通信 100 (S 301 )、移动通信网络 500 接收来自第三移动终端的视听通信请求 300 (S 303 )。 在步骤 S 301 ,第一款移动终端 100 处于视听通信状态,摄像单元 107 第一个移动终端100 获取第一移动终端用户的图像 100 , 图像处理器 109 处理用户图像,显示单元 111 显示用户图像,并将麦克风MIC和扬声器SPK转换为操作状态。 [0050] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三终端 300 那是第一个移动终端 100 正在进行视听交流(S 305 )。 [0051] 第三个移动终端 300 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 307 )。 如果是第三个移动终端 300 第三移动终端保持视听通信待机状态 300 向移动通信网络发送待机状态维持消息 500 (S 309 )。 [0052] 此后,移动通信网络 500 发送关于第三个移动终端的信息 300 到第一移动终端 100 (S 311 )并形成第一移动终端之间的通信通道 100 第三个移动终端 300 . 第三移动终端信息 300 可以包括第三移动终端的联系方式和图像数据 300 . [0053] 移动通信网络 500 接收来自第四移动终端的视听通信请求 400 (S 313 ),并发送有关第一移动终端状态的消息 100 到第四个移动终端 400 通知第四移动终端 400 那是第一个移动终端 100 正在进行视听交流(S 315 )。 [0054] 第四款移动终端 400 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 317 )。 如果第四个移动终端 400 第四移动终端保持视听通信待机状态 400 向移动通信网络发送待机状态维持消息 500 (S 319 )。 [0055] 此后,移动通信网络 500 发送第四个移动终端的信息 400 到第一移动终端 100 (S 321 )并形成第一移动终端之间的通信通道 100 和第四个移动终端 400 . 第四移动终端信息 400 可以包括第四移动终端的联系信息和图像数据 400 . [0056] 第一个移动终端 100 确定第一移动终端之间的通信信道 100 第三个移动终端 300 在步骤 S 形成 311 ,以及第一移动终端之间的通信信道 100 和第四个移动终端 400 在步骤 S 形成 321 . [0057] 此后,第一移动终端 100 通过按照接收到请求的顺序列出移动终端,设置并显示请求视听通信的移动终端的待机顺序(S 323 )。 在本示例性实施例中,由于第三移动终端 300 在第四台移动终端之前请求视听通信 400 , 第三个移动终端 300 具有最高的待机位置。 [0058] 当第一个移动终端 100 想要更改显示的待机顺序(S 325 ),第一款移动终端 100 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 327 )。 通过选择第三移动终端的图像数据输入更改待机顺序的请求 300和第四个移动终端 400 以更改模式或待机顺序显示。 [0059] 移动通信网络 500 接收待机顺序变更请求消息REQ_MSG,变更第三移动终端的待机顺序 300 和第四个移动终端 400 (S 329 )。 [0060] 移动通信网络 500 临时存储更改后的待机订单(S 331 )并发送备用订单变更完成消息RES_MSG通知第一移动终端 100 第三个移动终端的待机订单变更 300 和第四个移动终端 400 (S 333 )。 [0061] 第一个移动终端 100 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG更改并显示待机命令 500 (S 335 )。 [0062] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 337 )、移动通信网络 500 指在步骤中临时存储的已更改的备用订单 331 (S 339 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 341 )。 [0063] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 343 )。 [0064] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0065] 参考图。 4、控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 (S 401 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . 当移动端 100 在执行视听通信时从至少一个移动终端接收视听通信请求(S 403 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 405 )。 [0066] 如果有至少两个移动终端请求视听通信,则控制器 105 根据接收视听通信请求的顺序设置待机命令,并在显示单元上显示设置的待机命令 111 (S 407 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0067] 控制器 105 判断设置的待机顺序是否改变(S 409 )。 如果设置的待机顺序没有改变,则过程继续到步骤S 419 . [0068] 如果设置的待机顺序发生了变化,控制器 105 控制射频单元 101 发送消息REQ_MSG,请求移动终端(这里是第三个移动终端)的待机命令 300 和第四个移动终端 400 ) 通过移动通信网络进行更改 500 (S 411 )。 [0069] 此后,控制器 105 接收移动通信网络发送的备用订单变更完成消息RES_MSG 500 通过射频单元 101 (S 415 )。 控制器 105更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据接收到的待机指令变更完成消息RES_MSG,在人机界面上显示变更后的待机指令 111 (S 417 )。 [0070] 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 419 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 421 )。 第一个移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单位置在步骤 S 更改为最高位置 417 ,或与第三个移动终端 300 ,它在步骤 S 中设置的待机顺序中的最高位置 407 . [0071] 如果在步骤中请求视听通信的移动终端的数量不是至少两个 405 , 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 423 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 425 )。 [0072] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0073] 参考图。 参见图5A和5B,步骤S 501 到 S 523 图。 图5A与步骤S基本相同 301 到 S 323 图。 与图3A相同,因此省略其描述。 [0074] 如果第四个移动终端 400 待机订单仓位低于第三移动终端 300 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 525 )、移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 (S 527 ) 和移动通信网络 500 向第三移动终端发送备用订单变更请求消息REQ_MSG 300 (S 529 )。 待命订单变更请求消息REQ_MSG可以由第四移动终端发送 400 同时第四个移动终端 400 向移动通信网络发送视听通信请求消息 500 在步骤 S 513 . [0075] 第一个移动终端 100 响应备用订单更改请求消息REQ_MSG(S 531 ),以及第三个移动终端 300 响应备用订单更改请求消息REQ_MSG(S 533 )。 [0076] 第一个移动终端 100 然后向移动通信网络发送备用订单更改批准消息ACC_MSG 500 确认批准备用订单的更改(S 535 ),以及第三个移动终端 300 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500确认批准备用订单的更改(S 537 )。 [0077] 移动通信网络 500 更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据从第一移动终端接收到的待命订单变更批准消息ACC_MSG 100 在步骤 S 535 并从第三个移动终端 300 在步骤 S 537 (S 539 )。 [0078] 移动通信网络 500 临时存储更改的备用订单(S 541 )并向第一移动终端发送备用订单变更完成消息RES_MSG 100 (S 543 ),第三个移动终端 300 (S 545 )、第四个移动终端 400 (S 547 )。 [0079] 第一个移动终端 100 更改并显示在第三个移动终端设置的待机指令 300 和第四个移动终端 400 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG 500 (S 549 )。 [0080] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 551 )、移动通信网络 500 指的是在步骤 S 临时存储的更改后的待机命令 541 (S 553 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 555 )。 [0081] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 557 )。 [0082] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0083] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 . [0084] 此后,如果第一移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG批准待命订单变更 100 向移动通信网络发送确认批准的备用订单更改批准消息ACC_MSG 500 . 当移动通信网络 500 接收待命订单变更批准消息ACC_MSG,移动通信网络 500 相应地更改备用顺序。 移动通信网络 500 暂存变更后的待命订单,并向第一移动终端发送待命订单变更完成消息RES_MSG 100 . [0085] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0086] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 第三个移动终端 300 . 如果第一个移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 100 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . 如果是第三个移动终端 300第三移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . [0087] 当至少一个第一移动终端 100 第三个移动终端 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 , 移动通信网络 500 不改变待命订单,向第一移动终端发送待命订单变更不批准消息N_ACC_MSG 100 , 第三个移动终端 300 ,以及第四个移动终端 400 . [0088] 进一步地,如果第一移动终端 100 批准备用订单和第三个移动终端的更改 300 在接收到来自移动通信网络的待命订单更改不批准消息N_ACC_MSG时,响应待命订单更改请求消息REQ_MSG不批准待命订单的更改 500 通知它待机顺序没有改变,因为第三个移动终端 300 不批准备用订单变更,第一个移动端 100 可以向移动通信网络发送备用订单更改请求消息REQ_MSG 500 从而可以强制改变第三移动终端的待机顺序 300 和第四个移动终端 400 . [0089] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0090] 参考图。 6、控制器 105 控制射频单元 101 让第一个移动终端 100 与第二移动终端进行视听通信 200 (S 601 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . [0091] 当控制器 105 在进行视听通信时从至少一个移动终端接收视听通信请求(S 603 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 605 )。 [0092] 如果有至少两个移动终端请求视听通信,则控制器 105 在视听通信请求命令中设置待机命令并在显示单元中显示该命令 111 (S 607 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0093] 如果控制器 105 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 (S 609 ), 控制器 105 判断移动端是否 100 响应备用订单更改请求消息,批准备用订单的更改(S 611 )。 如果移动端 100 不批准备用订单的变更,流程继续步骤S 619 . [0094] 如果移动端 100 批准备用订单的更改,控制器 105 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500 (S 613 )。 [0095] 控制器 105 判断移动端是否 100 从移动通信网络接收备用订单更改完成消息RES_MSG 500 (S 615 )。 如果移动端 100 未收到来自移动通信网络的备用订单更改完成消息 RES_MSG 500 , 过程在步骤 S 继续 619 . 如果移动端 100接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 , 控制器 105 根据接收到的待机命令更改完成消息RES_MSG更改待机命令,并在人机界面显示更改后的待机命令 111 (S 617 )。 [0096] 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 619 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 621 )。 例如,第一移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单仓位已在步骤 S 变为最高仓位 617 ,或与第三个移动终端 300 在步骤 S 中设置的待机顺序中的最高位置 607 . [0097] 如果在步骤S请求视听通信的移动终端的数量不是至少两个 605 , 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 623 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 625 )。 [0098] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 [0099] 参考图。 7、同时第一移动终端 100 与第二移动终端进行视听通信 200 通过移动通信网络 500 (S 701 )、移动通信网络 500 接收与第一移动终端进行视听通信的请求 100 从第三个移动终端 300 (S 703 )。 [0100] 移动通信网络 500 形成第一移动终端之间的通信通道 100 第三个移动终端 300 并发送关于第三移动终端的信息 300 连同对第一移动终端的视听通信请求 100 (S 705 )。 第三移动终端信息 300 可以是第三移动终端的用户信息(例如电话号码) 300 和/或包括第三移动终端的图像数据的信息 300 . [0101] 第一个移动终端 100 显示从第三移动终端接收到的图像数据 300 (S 707 )。 第一个移动终端 100 可以进一步显示消息(例如弹出窗口)以批准与第三移动终端的视听通信的连接 300 . [0102] 如果第一个移动终端 100 批准与第三个移动终端的视听通信 300 (S 709 )、移动通信网络 500 结束第一移动终端之间的视听通信 100 第二移动终端 200或者转换第一移动终端之间的视听通信状态 100 第二移动终端 200 到待机状态(S 711 )。 此后,移动通信网络 500 实现第一移动终端之间的视听通信 100 第三个移动终端 300 (S 713 )。 [0103] 如上所述,根据本发明,通过在第一移动终端与第二移动终端执行视听通信时改变至少两个请求视听通信的移动终端的待机顺序,可以与选择的请求视听的移动终端执行视听通信 通信,可以为第一移动终端的用户提供更大的便利。 [0104] 此外,通过在第一移动终端与第二移动终端进行视听通信的同时,根据从请求视听通信的至少两个移动终端中的具有较低待机位置的移动终端接收到的用于改变待机命令的请求来改变待机命令, 可以与选择的请求视听通信的移动终端进行视听通信,这可以为具有较低待机位置的待机状态的移动终端的用户提供更大的便利。 [0105] 另外,通过在第一移动终端与第二移动终端进行视听通信的同时显示关于请求视听通信的移动终端的信息,用户可以容易地检查处于待机状态的移动终端。 [0106] 对于本领域的技术人员来说,在不脱离本发明的精神或范围的情况下,可以对本发明进行各种修改和变化是显而易见的。 因此,本发明旨在覆盖本发明的修改和变化,只要它们落入所附权利要求及其等同物的范围内。(String), 111527(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.453 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.453 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.453 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270639(Integer), KR100790787B1(String), 1046996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270639(Integer), US20080171563A1(String), 1046997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270639(Integer), US7801528B2(String), 1046998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7801528B2(String), US7801528B2(String), 1284998400(Integer), 270639(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184956(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.519 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.519 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.519 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 184956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b9898d529bdb42f9bcfb80bf8e2ead5b.png(String), 184957(Integer), b9898d529bdb42f9bcfb80bf8e2ead5b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for obtaining location information about mobile terminal(String), 移动终端及获取移动终端位置信息的方法(String), US9451580B2(String), The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal. The method for obtaining location information about the mobile terminal comprises: turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal.(String), 本发明实施例提供一种移动终端及获取移动终端位置信息的方法。 获取移动终端位置信息的方法包括:打开移动终端的卫星定位模块,获取移动终端当前位置信息后关闭卫星定位模块,并将当前位置信息作为初始位置信息。 ; 移动终端的传感模块采集移动终端的运动信息,并根据该运动信息计算移动终端的位移变化量; 根据初始位置信息和移动终端的位移变化,获取移动终端的实际位置信息。(String), US14/436195(String), 1374163200(Integer), US9451580B2(String), 1474300800(Integer), 1474300800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 5(Integer), 27(Integer), CN101464155A | CN102169182A | CN102243315A | CN102901975A | CN1914517A | JP1988108285A | JP1989278879A | JP1990212713A | JP1991237788A | JP1994111196A | JP1995001210A | JP2001059738A | JP2002255664A | JP2006242578A | JP2006279266A | JP2008063815A | JP2008067681A | JP2010038712A | JP2010038798A | JP2010120968A | JP2011149925A | JP2011164089A | JP2011176576A | JP2013029915A | US20100253503A1 | US20130102268A1 | US20160007405A1(String), \20230420\b9898d529bdb42f9bcfb80bf8e2ead5b.png(String), 10(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 1. A method for obtaining location information about a mobile terminal, comprising:turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information;a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information;obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal;wherein, the motion information comprises:acceleration information and initial velocity information;further comprising a correction step to the initial velocity after calculating the initial velocity; wherein, the correction step comprises:judging whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then no need to correct the initial velocity; if not, then re-calculating the initial velocity.(String), 1、一种获取移动终端位置信息的方法,包括:开启移动终端的卫星定位模块,获取到移动终端的当前位置信息后关闭卫星定位模块,将当前位置信息作为初始位置信息。移动终端的感知模块采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量;根据初始位置信息和移动终端的位移变化获取移动终端的实际位置信息;其中,运动信息包括:加速度信息和初速度信息;还包括计算初速度后对初速度进行修正的步骤;其中,校正步骤包括:判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内;如果是,则无需修正初速度;如果不是,则重新计算初始速度。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 2. The method according to claim 1, further comprising: periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal, updating the initial location information, and setting the variation of displacement as zero.(String), 2.根据权利要求1所述的方法,还包括:周期性开启移动终端的卫星定位模块,获取移动终端的当前位置信息,更新初始位置信息,并将位移变化量设置为零。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 3. The method according to claim 2, wherein, the step of periodically turning on the satellite locating module of the mobile terminal comprises:starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value;orjudging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module.(String), 3.根据权利要求2所述的方法,其中,周期性开启移动终端的卫星定位模块的步骤包括:当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块;or判断位移变化量是否达到预设位移阈值;如果是,则打开卫星定位模块。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 4. The method according to claim 1, wherein, the step of collecting the initial velocity information of the mobile terminal comprises:judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period.(String), 4.根据权利要求1所述的方法,其中,采集移动终端的初始速度信息的步骤包括:判断移动终端在初始位置的运动状态;如果处于静止状态,则初速度为零;如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 5. The method according to claim 4, wherein, the step of calculating displacement changing information of the mobile terminal through the motion information comprises:decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; andcalculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction.(String), 5.根据权利要求4所述的方法,其中,通过运动信息计算移动终端的位移变化信息的步骤包括:分解经度方向、纬度方向和高度方向的加速度和初速度;和根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 6. A mobile terminal, comprising a processor, configured to:obtain current location information about the mobile terminal through a satellite locating module comprising a global positioning system (GPS) module or an assisted global positioning system (AGPS) module;turn on the satellite locating module, and turn off the satellite locating module after the information is obtained;collect motion information about the mobile terminal through a sensor, and calculate variation of displacement of the mobile terminal according to the motion information; andobtain actual location information about the mobile terminal through processing the initial location information and the variation of displacement of the mobile terminal;wherein, the motion information comprises: acceleration information and initial velocity information;wherein, the processor is further configured to:judge whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then need not to correct the initial velocity; if not, then re-calculate the initial velocity.(String), 6.移动终端,包括一个处理器,配置为:通过包括全球定位系统(GPS)模块或辅助全球定位系统(AGPS)模块的卫星定位模块获取移动终端的当前位置信息;开启卫星定位模块,获取信息后关闭卫星定位模块;通过传感器采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量;和通过处理初始位置信息和移动终端的位移变化,得到移动终端的实际位置信息;其中,运动信息包括:加速度信息和初速度信息;其中,处理器还用于:判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内;如果是,则无需修正初速度;如果不是,则重新计算初始速度。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 7. The mobile terminal according to claim 6, wherein, the processor is further configured to: control the satellite locating module to periodically turn on to obtain the current location information of the mobile terminal, update the initial location information, and set the variation of displacement as zero.(String), 7.根据权利要求6所述的移动终端,其中,处理器还用于:控制卫星定位模块周期性开启,获取移动终端的当前位置信息,更新初始位置信息,并将位移变化量设置为零。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 8. The mobile terminal according to claim 7, wherein, the processor is configured to periodically turn on the satellite locating module of the mobile terminal by the following mode:starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value;orjudging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module.(String), 8.根据权利要求7所述的移动终端,其中,处理器用于通过以下方式周期性开启移动终端的卫星定位模块:当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块;or判断位移变化量是否达到预设位移阈值;如果是,则打开卫星定位模块。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 9. The mobile terminal according to claim 6, wherein, the processor is configured to collect the initial velocity information of the mobile terminal by the following mode:judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period.(String), 9.根据权利要求6所述的移动终端,其中,处理器,用于通过以下方式采集移动终端的初始速度信息:判断移动终端在初始位置的运动状态;如果处于静止状态,则初速度为零;如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184957(Integer), 10. The mobile terminal according to claim 9, wherein, the processor is configured to calculate the displacement changing information of the mobile terminal by the following mode:decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; andcalculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction.(String), 10.根据权利要求9所述的移动终端,其中,处理器用于通过以下方式计算移动终端的位移变化信息:分解经度方向、纬度方向和高度方向的加速度和初速度;和根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184957(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is the 35 U.S.C. §371 national stage of PCT Application No. PCT/CN2013/079701, filed Jul. 19, 2013, which is herein incorporated by reference in its entirety and which also claims priority to, and the benefit of, Chinese Patent Application No. 201210396171.1, filed Oct. 18, 2012, which is herein incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present document relates to the wireless communication field, and in particular, to a mobile terminal and a method for obtaining location information about a mobile terminal. BACKGROUND [0003]Because of the characteristics, such as all-weather, high-accuracy and automatic measuring, possessed by the global positioning system (GPS) technology, as the advanced measurement means and new productivity, it had already been integrated into various application fields, such as the national economic construction, the national defense construction and the social development. [0004]Along with the end of cold war and the flourishing development of the global economy, the U.S. government announce to cancel the SA policy during the year 2000 to year 2006, on the premise of guaranteeing the U.S.A. national security not at risk, and the GPS civil signal precision is improved in the world wide, and the precision to locate the simple point by using the C/A code is raised to 10 meters from 100 meters, which will further promote the application of the GPS technology, raise the productivity, the working performance, the scientific level and the living quality of people, and stimulate the growth of the GPS market. [0005]The main function of the assisted global positioning system (A-GPS) technology is to be able to provide the high-accuracy location information for the terminal user. After the mobile operator adopts the location service based on the A-GPS locating technology, the terminal user can know the current position of oneself or others conveniently and swiftly, which is especially suitable for the vehicle tracing and the navigation system and the vehicles with special tasks (armor cash carrier, ambulance, fire vehicle, etc.), and is able to increase the vehicle security, the transportation efficiency and the service quality by a large margin. At present, as the domestic mobile communication market is growing day by day, especially along with the coming of the commercial usage of 3G, China Mobile and China Unicom have all made and put out their own A-GPS schemes. [0006]The product functions of the mobile terminals are more and more comprehensive at present, and most mobile terminals have the satellite positioning function, such as the GPS, the A-GPS, etc., and the user can know one's own location at any time. But the satellite locating module, such as the GPS module or the A-GPS module, needs to frequently read the location information along with the movement of the user and the constant change of the location, which leads to the problems, for example, the power consumption of the satellite locating module, such as the GPS module or the A-GPS module, is greater, the data updating will be delayed, etc. SUMMARY [0007]The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal, which can reduce the power consumption of the satellite locating module. [0008]The embodiment of the present document provides a method for obtaining location information about a mobile terminal, comprising: [0009]turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; [0010]a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and [0011]obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal. [0012]Preferably, the method further comprises: periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal, updating the initial location information, and setting the variation of displacement as zero. [0013]Preferably, the step of periodically turning on the satellite locating module of the mobile terminal comprises: [0014]starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value;[0015]or [0016]judging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module. [0017]Preferably, the motion information comprises: acceleration information and initial velocity information. [0018]Preferably, the step of collecting the initial velocity information of the mobile terminal comprises: [0019]judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period. [0020]Preferably, the method further comprises a correction step to the initial velocity after calculating the initial velocity; wherein, [0021]the correction step comprises: [0022]judging whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then no need to correct the initial velocity; if not, then re-calculating the initial velocity. [0023]Preferably, the step of calculating displacement changing information of the mobile terminal through the motion information specifically comprises: [0024]decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; and [0025]calculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction. [0026]The embodiment of the present document provides a mobile terminal, comprising: a satellite locating module, a sensing module, a control module and a location information processing module; wherein, [0027]the satellite locating module is configured to: obtain current location information about the mobile terminal, and transmit the location information to the location information processing module; [0028]the control module is configured to: turn on the satellite locating module, and turn off the satellite locating module after the satellite locating module completes obtaining the information; [0029]the sensing module is configured to: collect motion information about the mobile terminal, and calculate variation of displacement of the mobile terminal according to the motion information, and transmit the variation of displacement to the location information processing module; and [0030]the location information processing module is configured to: obtain actual location information about the mobile terminal through processing the initial location information and the variation of displacement of the mobile terminal. [0031]Preferably, the control module is further configured to: control the satellite locating module periodically turn on to obtain the current location information of the mobile terminal, update the initial location information, and control the sensing module to set the variation of displacement as zero. [0032]Preferably, the satellite locating module is a global positioning system (GPS) module or an assisted global positioning system (AGPS) module. [0033]Preferably, the control module is configured to periodically turn on the satellite locating module of the mobile terminal by the following mode: [0034]starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value; [0035]or [0036]judging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module. [0037]Preferably, the motion information comprises: acceleration information and initial velocity information. [0038]Preferably, the sensing module is configured to collect the initial velocity information of the mobile terminal by the following mode: [0039]judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period. [0040]Preferably, the sensing module is further configured to: [0041]judge whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then need not to correct the initial velocity; if not, then re-calculate the initial velocity. [0042]Preferably, the sensing module is configured to calculate the displacement changing information of the mobile terminal by the following mode: [0043]decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; and [0044]calculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction. [0045]The embodiment of the present document provides a method for obtaining location information about a mobile terminal, which can reduce the power consumption of the module for obtaining the location information about the mobile terminal Wherein, the satellite locating module is turned off after the location information about the mobile terminal is obtained, then the motion information about the mobile terminal is collected through the sensing module of the mobile terminal, and the displacement changing information of the mobile terminal is calculated through the motion information, and then the actual location information is obtained according to the initial location information and the displacement changing information, to reduce the power consumption of the satellite locating module without requirement on obtaining the current location information of the mobile terminal and updating frequently by using the satellite locating module. [0046]In addition, the terminal only needs to calculate the displacement changing information through the motion information about the mobile terminal, and thus calculates the actual location information, which can reduce the appearance of the data update delay and improve the accuracy of the location information after the frequent updating and obtaining the location information are avoided. BRIEF DESCRIPTION OF DRAWINGS [0047]FIG. 1 is a basic flow chart of a method for obtaining location information about a mobile terminal according to embodiment one of the present document. [0048]FIG. 2 is a flow chart of obtaining an initial velocity according to embodiment one of the present document. [0049]FIG. 3 is a diagram of decomposing an acceleration according to embodiment one of the present document. [0050]FIG. 4 is a structure diagram of a mobile terminal according to embodiment one of the present document. PREFERRED EMBODIMENTS OF THE PRESENT DOCUMENT [0051]The embodiment of the present document is described in detail with reference to the accompanying drawings hereinafter. It should be illustrated that, in the case of not conflicting, the embodiments in the present application and features in these embodiments can be combined with each other. [0052]In the embodiment of the present document, the mobile terminal detects the motion state of the terminal itself and calculates the displacement variation information, and then calculates the actual location of the mobile terminal by combining with the initial location information read by the satellite locating module (such as the GPS or the A-GPS module), to prevent the module for obtaining the location information (such as the GPS or the A-GPS module) from frequently reading the current location information of the mobile terminal, reducing the power consumption of the satellite locating module (such as the GPS or the A-GPS module). [0053]The embodiment of the present document is described in detail with reference to the accompanying drawings hereinafter. Embodiment One [0054]Please refer to FIG. 1, a method for obtaining location information about a mobile terminal according to the present embodiment includes the following steps. [0055]In step 101, a satellite locating module of the mobile terminal is turned on, the satellite locating module is turned off after current location information about the mobile terminal is obtained, and the current location information is regarded as initial location information. [0056]In step 102, a sensing module of the mobile terminal collects motion information about the mobile terminal, and calculates variation of displacement of the mobile terminal according to the motion information. [0057]In step 103, actual location information about the mobile terminal is obtained according to the initial location information and the variation of displacement of the mobile terminal. [0058]The method of the present embodiment can further include: periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal, updating the initial location information, and setting the variation of displacement as zero. [0059]The above-mentioned period for turning on the satellite locating module of the mobile terminal can be preset, the displacement variation information of the mobile terminal can be calculated through obtaining the motion information about the mobile terminal and according to the motion information before starting the next period, and then the actual location of the mobile terminal at the corresponding moment is calculated according to the initial location information and the displacement changing information, to reduce the frequency of obtaining the location information and reduce the power consumption of the corresponding module. [0060]In the method for obtaining the location information about the mobile terminal of the present embodiment, the procedure of periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal can include: [0061]starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value; [0062]or [0063]judging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module. [0064]For example, the satellite locating module can be set to turn on every minute to obtain the current location information, and the satellite locating module also can be set to turn on every kilometer to obtain the current location information of the mobile terminal. In this way, the satellite locating module of the mobile terminal is in the closing or dormant state in most of the time, which can reduce the power consumption of the satellite locating module. [0065]The motion information obtained in the above-mentioned step 102 can include: acceleration information and initial velocity information. [0066]The acceleration information obtained in the above-mentioned step 102 can include: the acceleration information of the mobile terminal obtained through the acceleration sensor of the mobile terminal. [0067]There are more and more functions of the mobile terminal at present, which support, on the hardware, the sensors of various applications, such as GPS, acceleration, proximity, electronic compass, etc., and support Wi-Fi, BT, NFC, etc., on the transmission technology; and the GPS (AGPS) has already been widely used on the intelligence terminal devices, such as, the mobile phone, the tablet computer, etc. In the method of the present embodiment, the sensor of the mobile terminal can be utilized to obtain the motion information, such as, the acceleration information and the initial velocity information. [0068]Taking obtaining the location information with the GPS or the AGPS and obtaining the acceleration information with the sensor as the example, the GPS or AGPS module obtains the current location information as the initial location information; when the mobile terminal moves, the sensor obtains the acceleration information and the initial velocity information of the mobile terminal and calculates the variation of displacement, and then can calculate the location information at the corresponding moment according to the initial location information. It is unnecessary for the mobile terminal to use the GPS or AGPS module to obtain the current location information for update again, reducing the frequency of reading the data by the GPS or AGPS module and reducing the power consumption of the module, and the delay of the data update is reduced and the accuracy grade of the location information is improved because the number of updating the data is reduced. [0069]The GPS (AGPS) module generally reads the data once every second, and there is the problem that the power consumption is big and the location update is delayed. The power consumption of the sensor module is generally less than 1/10 of the GPS (AGPS) module. By using the sensor assisted GPS (AGPS) module, the power consumption of the GPS (AGPS) module can be reduced through reducing the frequency of reading the data by the GPS (AGPS) module; and the location information can be updated at a high frequency at the same time, which solves the problem of the data update delay. Regarding the device location read by the GPS (AGPS) module as the original point, the sensor detects the acceleration of the device, calculates the displacement increment of the device, and thus calculates the actual location of the device at the corresponding moment, and updates the location information of the device in time; the GPS (AGPS) module reads the location information again, if it is read successfully, then the initial location of the device is updated (that is, the original point of the last displacement), the displacement increment is set as 0, and the displacement increment is re-calculated, by this circulation. [0070]The above-mentioned obtaining the initial velocity information of the mobile terminal includes: [0071]judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period. [0072]When the satellite locating module of the mobile terminal, during the static state, turns on the satellite locating module, then the initial velocity is zero; if it is in the motion state, it can calculate the final velocity of the last period according to the variation of displacement and the acceleration of the last period, thus obtaining the initial velocity of the present period. [0073]The method of the present embodiment also includes the correction to the initial velocity after calculating the initial velocity. [0074]The correction includes: [0075]judging whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then no need to correct the initial velocity; if not, then re-calculating the initial velocity. [0076]As shown in FIG. 2, the obtaining of the initial velocity V0 can be: judging the motion state of the device by using the sensors, such as, the acceleration sensor, etc. If the device turns on the locating application such as, the GPS, etc. in the static state, then V0 is 0, and the velocity at corresponding moment is calculated in real time and recorded according to the acceleration detected by the sensor. If the locating application, such as the GPS, etc., is turned on when the device moves, the displacement is calculated by using the location information read by the GPS (AGPS) module twice, and the velocity at corresponding moment is calculated by the displacement calculation formula according to the acceleration information of the device detected by the sensor. Errors exist in both of the above-mentioned two situations, and the initial velocity can be corrected constantly by the corresponding policy. For example, when the difference of the location information read by the (AGPS) module and the data calculated by the sensor is greater than a certain threshold value, the corresponding initial velocity is re-calculated according to the location information read by the (AGPS) module this time and the last time and the acceleration information of the device detected by the sensor. In order to reduce the error, when calculating the initial velocity, the time interval of the location information read by the GPS (AGPS) module twice can be reduced to the best. [0077]After obtaining the acceleration information and the initial velocity information, in the above-mentioned step 102, the displacement changing information of the mobile terminal calculated according to the motion information includes: [0078]decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; and [0079]calculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction. [0080]Similarly, taking obtaining the location information with the GPS or the AGPS and obtaining the acceleration information with the sensor as the example, as shown in FIG. 3: the acceleration of the device can be monitored in real time through the sensor, such as, the acceleration, etc., and the acceleration is decomposed into the horizontal plane component (X axle, Y axle direction) and the vertical component (Z axis direction). By combining with the sensors, such as the electronic compass, etc., the coordinates of the sensors, such as the acceleration, etc., can be connected with the earth location coordinate; the acceleration and the initial velocity V0 are decomposed into the longitude and latitude direction and the height direction respectively; the displacement increments of the longitude and latitude direction and the height direction are calculated, and converted into the displacement increments in the longitude and latitude and the altitude direction; and the actual location of the device at the corresponding moment within the time period between the two readings by the GPS (AGPS) module by combining with the initial location of the device (the device location detected by the GPS or the AGPS). The direction sensor, such as, the electronic compass, etc., can also not be used: during the initialization, the relative relation of the coordinate of the sensor, etc., such as, the acceleration, etc., and the earth location coordinate is calculated, the azimuthal variation situation of the device is monitored through the sensor, such as the acceleration, etc., and the relative relation of the coordinate of the sensor, etc., such as, the acceleration, etc., and the earth location coordinate is constantly recorded. [0081]As shown in FIG. 4, corresponding to the above-mentioned method for obtaining location information about a mobile terminal, the present embodiment further provides a mobile terminal, comprising: a satellite locating module, a sensing module, a control module and a location information processing module; wherein, [0082]the satellite locating module is configured to: obtain current location information about the mobile terminal, and transmit the location information to the location information processing module; [0083]the control module is configured to: turn on the satellite locating module, and turn off the satellite locating module after the satellite locating module completes obtaining the information; [0084]the sensing module is configured to: collect motion information about the mobile terminal, and calculate variation of displacement of the mobile terminal according to the motion information, and transmit the variation of displacement to the location information processing module; and [0085]the location information processing module is configured to: obtain actual location information about the mobile terminal through processing the initial location information and the variation of displacement of the mobile terminal. [0086]The above-mentioned control module is further configured to: control the satellite locating module periodically turn on to obtain the current location information of the mobile terminal, update the initial location information, and control the sensing module to set the variation of displacement as zero. [0087]The satellite locating module is a global positioning system (GPS) module or an assisted global positioning system (AGPS) module. [0088]The motion information collection module in the present embodiment can be a sensor. Embodiment Two [0089]Based on the method for obtaining location information about the mobile terminal in the embodiment one, the present embodiment regards configuring the GPS or AGPS module mobile phone as the example. The device location read by the GPS (AGPS) module is used as the original point, the device acceleration is detected by using the acceleration sensor and the electronic compass, the device displacement increment is calculated, and thus the actual location of the device at the corresponding moment is calculated, and the device location information is updated in time. The GPS (AGPS) module reads the location information again, and the initial location of the device is updated (that is, the original point of the previous displacement), the displacement increment is set as 0, and the displacement increment is re-calculated, and circulate in this way. The specific time threshold value or displacement threshold value of the location information read by the GPS (AGPS) module can be set up, to make the reading frequency a bit lower, for example, reading once every minute, which can enable the GPS (AGPS) module in the dormant state with the low power consumption in most of the time. [0090]Obtaining the device motion information mainly includes: obtaining and processing the acceleration, and obtaining the initial velocity. [0091]For the obtaining and processing of the acceleration: [0092]the device acceleration is obtained through the acceleration sensor, the acceleration is decomposed into the horizontal plane component and the vertical component (the present embodiment does not consider the change in the height direction of the device, while only monitors the displacement of the horizontal direction); by combining with the electronic compass, the horizontal component of the acceleration is decomposed into ax and ay in the longitude and latitude direction, that is, X and Y direction; the decomposition diagram of the device acceleration is as FIG. 2. [0093]The frequency of reading the acceleration by using the acceleration sensor is set as reading once every 10 ms, that is, t=10 ms. [0094]The device acceleration is read respectively as: a1, a2, . . . an (it is assumed that the acceleration value is read n times by the acceleration sensor during the two reading periods of the GPS). [0095]The direction components of X-axis are respectively: ax1, ax2 . . . axn. [0096]The direction components of Y-axis are respectively: ay1, ay2 . . . ayn. [0097]For the obtaining of the initial velocity: [0098]the obtaining of the initial velocity V0 is: judging the motion state of the device by using the sensors, such as the acceleration, etc.; if the device in the static state turns on the locating application, such as, the GPS, etc., then V0 is 0, and the velocity at corresponding moment is calculated in real time and recorded according to the acceleration detected by the sensor; if the locating application, such as, the GPS, etc., is turned on when the device moves, the displacement is calculated by using the location information read by the GPS (AGPS) module twice, and then the velocity at corresponding moment is calculated according to the acceleration information of the device detected by the acceleration sensor and the electronic compass. Errors exist in both of the above-mentioned two situations, and the initial velocity can be corrected constantly by the corresponding policy. For example, when the difference of the location information read by the (AGPS) module and the data calculated by the acceleration sensor and the electronic compass is greater than a certain threshold value, the corresponding initial velocity is re-calculated according to the location information read by the (AGPS) this time and the last time and the acceleration information of the device detected by the acceleration sensor and the electronic compass. The obtaining procedure of the device velocity is as FIG. 3. [0099]When the device is under the static state, V0x=V0y=V0=0. [0100]When the device is under the motion state, the gaining mode for the V0x and V0y is as follows: (the conversions of the longitude and latitude unit and the distance unit are involved hereinafter, which are omitted in the present text.) [0101]Assuming that the device locations read by the GPS (AGPS) module twice are at point A and point B respectively, the distance between the two points is AB; the reading frequency of the GPS (AGPS) module is once every minute, that is, the time interval T for reading the point A and point B=60 s; assuming that the frequency of reading the acceleration by using the acceleration sensor is reading once for every 10 ms, that is, t=10 ms. [0102]ABx is the component of the X-axis direction, and ABy is the component of the Y-axis direction, [0103]then: ABx=V0x×Δt+(V0x+½×ax1×Δt)Δt+ . . . (V0x+ax1×Δt+ . . . ½axn×Δt)Δt  ①[0104](ax1, ax2, . . . , axn are the X-axis components of the acceleration values read by the acceleration sensor at different moments within the T period). ABy=V0y×Δt+(V0y+½×ay1×Δt)Δt+ . . . (V0y+ay1×Δt+ . . . ½ayn×Δt)Δt   ②[0105](ay1, ay2, . . . , ayn are the Y-axis components of the acceleration values read by the acceleration sensor at different moments within the T period). [0106]V0x and V0y can be gained through the above ① and ②. [0107]The velocity at the final moment in the T period is the initial velocity of the next T period, that is: [0108]the initial velocity of the X-axis direction in the next T period is: V0x+ax1×Δt+ . . . axn×Δt; [0109]the initial velocity of the Y-axis direction in the next T period is: V0y+ay1×Δt+ . . . ayn×Δt. [0110]The correction policy for the initial velocity: [0111]the displacement increment in the period calculated by the sensor is compared with the location distance read by the GPS (AGPS) module; and if it is greater than 2 m, then the initial velocity is corrected. The correction mode can adopt obtaining the initial velocity again, and the method is the same with the abo(String), 相关申请的交叉引用 [0001] 此应用程序是 35 U.S.C. §371 国家阶段 PCT 申请号 PCT/CN2013/079701,于 2013 年 7 月 19 日提交,其全部内容通过引用并入本文,并要求中国专利申请号 201210396171.1 的优先权和权益, 于 2012 年 10 月 18 日提交,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及无线通信领域,尤其涉及一种移动终端及获取移动终端位置信息的方法。 背景 [0003] 由于全球定位系统(GPS)技术所具有的全天候、高精度、自动测量等特点,作为先进的测量手段和新的生产力,已经融入到各个应用领域,如 国民经济建设、国防建设和社会发展。 [0004] 随着冷战的结束和全球经济的蓬勃发展,美国政府宣布在保证美国国家安全不受威胁的前提下,于2000年至2006年取消SA政策,GPS民用 全球范围内信号精度的提高,利用C/A码定位单点的精度从100米提高到10米,将进一步推动GPS技术的应用,提高生产效率,提高工作效率。 性能、科学水平和人们的生活质量,并刺激 GPS 市场的增长。 [0005] 辅助全球定位系统(A-GPS)技术的主要作用是能够为终端用户提供高精度的位置信息。 移动运营商采用基于A-GPS定位技术的定位服务后,终端用户可以方便快捷地获知自己或他人的当前位置,特别适用于车辆追踪导航系统和特殊车辆。 任务(装甲运钞车、救护车、消防车等),能够大幅提高车辆安全性、运输效率和服务质量。 目前,随着国内移动通信市场的日益壮大,尤其是随着3G商用的到来,中国移动和中国联通都纷纷制定并推出了自己的A-GPS方案。 [0006] 目前移动终端的产品功能越来越全面,大部分移动终端都具有卫星定位功能,如GPS、A-GPS等,用户可以随时知道自己所在的位置。 但是GPS模块或A-GPS模块等卫星定位模块需要随着用户的移动和位置的不断变化而频繁读取位置信息,从而导致问题,例如 GPS模块或A-GPS模块等卫星定位模块功耗较大,数据更新会延迟等。 概括 [0007] 本发明实施例提供一种移动终端及获取移动终端位置信息的方法,能够降低卫星定位模块的功耗。 [0008] 本发明实施例提供了一种获取移动终端位置信息的方法,包括: [0009] 开启移动终端的卫星定位模块,获取到移动终端的当前位置信息后关闭卫星定位模块,将当前位置信息作为初始位置信息。 [0010] 移动终端的感知模块采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量; 和 [0011] 根据初始位置信息和移动终端的位移变化获取移动终端的实际位置信息。 [0012]优选地,该方法还包括:周期性开启移动终端的卫星定位模块,获取移动终端的当前位置信息,更新初始位置信息,并将位移变化量设置为零。 [0013] 优选地,所述周期性开启移动终端的卫星定位模块的步骤包括: [0014] 当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块; [0015]or [0016] 判断位移变化量是否达到预设位移阈值; 如果是,则打开卫星定位模块。 [0017] 优选地,所述运动信息包括:加速度信息和初速度信息。 [0018] 优选地,所述采集移动终端的初始速度信息的步骤包括: [0019] 判断移动终端在初始位置的运动状态; 如果处于静止状态,则初速度为零; 如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。 [0020] 优选地,该方法还包括计算初速度后对初速度进行修正的步骤; 其中, [0021] 校正步骤包括: [0022] 判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内; 如果是,则无需修正初速度; 如果不是,则重新计算初始速度。 [0023] 优选地,通过运动信息计算移动终端的位移变化信息的步骤具体包括: [0024] 分解经度方向、纬度方向和高度方向的加速度和初速度; 和 [0025] 根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。 [0026] 本发明实施例提供了一种移动终端,包括:卫星定位模块、感知模块、控制模块和位置信息处理模块; 其中, [0027] 卫星定位模块,用于获取移动终端当前的位置信息,并将该位置信息发送给位置信息处理模块; [0028] 控制模块用于开启卫星定位模块,在卫星定位模块获取信息完成后关闭卫星定位模块。 [0029] 传感模块,用于采集移动终端的运动信息,根据运动信息计算移动终端的位移变化量,并将位移变化量发送给位置信息处理模块。 和 [0030] 位置信息处理模块,用于通过对初始位置信息和移动终端的位移变化量进行处理,得到移动终端的实际位置信息。 [0031] 优选地,所述控制模块还用于:控制卫星定位模块周期性开启,获取移动终端的当前位置信息,更新初始位置信息,控制传感模块将位移变化量设置为零。 [0032] 优选地,所述卫星定位模块为全球定位系统(GPS)模块或辅助全球定位系统(AGPS)模块。 [0033]优选地,所述控制模块用于通过以下方式周期性开启所述移动终端的卫星定位模块: [0034] 当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块; [0035] 要么 [0036] 判断位移变化量是否达到预设位移阈值; 如果是,则打开卫星定位模块。 [0037] 优选地,所述运动信息包括:加速度信息和初速度信息。 [0038] 优选地,所述传感模块用于通过以下方式采集所述移动终端的初始速度信息: [0039] 判断移动终端在初始位置的运动状态; 如果处于静止状态,则初速度为零; 如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。 [0040] 优选地,所述传感模块还用于: [0041] 判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内; 如果是,则无需修正初速度; 如果不是,则重新计算初始速度。 [0042] 优选地,所述传感模块用于通过以下方式计算所述移动终端的位移变化信息: [0043] 分解经度方向、纬度方向和高度方向的加速度和初速度; 和 [0044] 根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。 [0045] 本发明实施例提供了一种获取移动终端位置信息的方法,能够降低移动终端位置信息获取模块的功耗,其中,卫星定位模块获取到位置信息后关闭。 获取移动终端,然后通过移动终端的传感模块采集移动终端的运动信息,通过运动信息计算移动终端的位移变化信息,然后根据移动终端的实际位置信息得到 对初始位置信息和位移变化信息,不需要使用卫星定位模块获取移动终端的当前位置信息和频繁更新,从而降低卫星定位模块的功耗。 [0046] 另外,终端只需通过移动终端的运动信息计算位移变化信息,从而计算出实际的位置信息,可以减少数据更新延迟的出现,提高定位信息后的准确度。 避免频繁更新和获取位置信息。 附图说明 [0047] 图1为本发明实施例一提供的移动终端位置信息获取方法的基本流程图。 [0048] 图2为本发明实施例一的获取初速度的流程图。 [0049] 图3为本发明实施例一的加速度分解图。 [0050] 图4为本发明实施例一提供的移动终端的结构图。 本文件的优选实施例 [0051]下面结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。 [0052] 本发明实施例中,移动终端检测终端自身的运动状态并计算出位移变化信息,再结合卫星定位模块读取的初始位置信息计算出移动终端的实际位置( 如GPS或A-GPS模块),避免获取位置信息的模块(如GPS或A-GPS模块)频繁读取移动终端当前位置信息,降低功耗 卫星定位模块(如GPS或A-GPS模块)。 [0053] 下面结合附图对本发明实施例进行详细说明。 实施例一 [0054] 请参考图1,本实施例提供的一种获取移动终端位置信息的方法包括以下步骤。 [0055] 在步 101 、打开移动终端的卫星定位模块,获取到移动终端的当前位置信息后关闭卫星定位模块,将当前位置信息作为初始位置信息。 [0056] 在步 102 移动终端的传感模块采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量。 [0057] 在步 103 ,根据初始位置信息和移动终端的位移变化得到移动终端的实际位置信息。 [0058] 本实施例的方法还可以包括:周期性开启移动终端的卫星定位模块,获取移动终端的当前位置信息,更新初始位置信息,并将位移的变化量设置为零。 [0059] 上述开启移动终端卫星定位模块的周期可以预先设置,通过获取移动终端的运动信息,根据该运动信息计算移动终端的位移变化信息,然后再开始下一次启动。 时间段,然后根据初始位置信息和位移变化信息计算移动终端在相应时刻的实际位置,以减少获取位置信息的频率,降低相应模块的功耗。 [0060] 在本实施例的获取移动终端位置信息的方法中,周期性开启移动终端的卫星定位模块获取移动终端当前位置信息的过程可以包括: [0061] 当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块; [0062] 要么 [0063] 判断位移变化量是否达到预设位移阈值; 如果是,则打开卫星定位模块。 [0064] 例如,可以将卫星定位模块设置为每分钟开启一次获取当前位置信息,也可以将卫星定位模块设置为每公里开启一次获取移动终端的当前位置信息。 这样,移动终端的卫星定位模块大部分时间处于关闭或休眠状态,可以降低卫星定位模块的功耗。 [0065] 上述步骤得到的运动信息 102 可以包括:加速度信息和初速度信息。 [0066]上述步骤得到的加速度信息 102 可以包括:通过移动终端的加速度传感器获取的移动终端的加速度信息。 [0067] 目前移动终端的功能越来越多,在硬件上支持各种应用的传感器,如GPS、加速度、接近度、电子罗盘等,支持Wi-Fi、BT、NFC、 等等,关于传输技术; 而GPS(AGPS)已经广泛应用于手机、平板电脑等智能终端设备上。在本实施例的方法中,可以利用移动终端的传感器获取 运动信息,例如加速度信息和初速度信息。 [0068] 以通过GPS或AGPS获取位置信息,通过传感器获取加速度信息为例,GPS或AGPS模块获取当前位置信息作为初始位置信息; 当移动终端移动时,传感器获取移动终端的加速度信息和初始速度信息,计算出位移的变化量,然后根据初始位置信息计算出相应时刻的位置信息。 移动终端无需再使用GPS或AGPS模块获取当前位置信息进行再次更新,减少了GPS或AGPS模块读取数据的频率,降低了模块的功耗,延迟 由于减少了更新数据的次数,减少了数据更新,提高了位置信息的准确度。 [0069] GPS(AGPS)模块一般每秒读取一次数据,存在功耗大和位置更新延迟的问题。 传感器模块的功耗一般小于全球定位系统(AGPS)模块的1/10。 通过使用传感器辅助GPS(AGPS)模块,可以通过降低GPS(AGPS)模块读取数据的频率来降低​​GPS(AGPS)模块的功耗; 并且可以同时高频更新位置信息,解决了数据更新延迟的问题。 以GPS(AGPS)模块读取的设备位置为原点,传感器检测设备的加速度,计算设备的位移增量,从而计算出相应时刻设备的实际位置,并更新 及时获取设备的位置信息; GPS(AGPS)模块再次读取位置信息,如果读取成功,则更新设备的初始位置(即上次位移的原点),位移增量设置为0, 位移增量被重新计算,通过这个循环。 [0070] 上述获取移动终端的初始速度信息包括: [0071] 判断移动终端在初始位置的运动状态; 如果处于静止状态,则初速度为零; 如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。 [0072] 当移动终端的卫星定位模块在静止状态下开启卫星定位模块时,则初速度为零; 如果处于运动状态,则可以根据位移的变化和上一周期的加速度计算出上一周期的终速度,从而得到本周期的初速度。 [0073] 本实施例的方法还包括计算初速度后对初速度的修正。 [0074] 更正包括: [0075]判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内; 如果是,则无需修正初速度; 如果不是,则重新计算初始速度。 [0076] 如图2所示,初始速度V0的获取可以是:通过加速度传感器等传感器判断设备的运动状态。如果设备开启了GPS等定位应用 等在静止状态下,则V0为0,根据传感器检测到的加速度,实时计算并记录相应时刻的速度。 如果设备移动时开启了GPS等定位应用,则利用GPS(AGPS)模块两次读取的位置信息计算位移,并通过 根据传感器检测到的设备加速度信息的位移计算公式。 上述两种情况都存在误差,可以通过相应的策略不断修正初速度。 例如,当(AGPS)模块读取的位置信息与传感器计算的数据的差值大于某个阈值时,根据(AGPS)读取的位置信息重新计算相应的初速度 ) 模块本次和上次以及传感器检测到的设备的加速度信息。 为了减小误差,在计算初速度时,GPS(AGPS)模块两次读取位置信息的时间间隔可以减小到最佳。 [0077] 在获取加速度信息和初速度信息后,在上述步骤中 102 ,根据运动信息计算出的移动终端的位移变化信息包括: [0078] 分解经度方向、纬度方向和高度方向的加速度和初速度; 和 [0079] 根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。 [0080] 类似地,以通过GPS或AGPS获取位置信息,通过传感器获取加速度信息为例,如图3所示:可以通过传感器实时监测设备的加速度,例如, 加速度等,并将加速度分解为水平面分量(X轴、Y轴方向)和垂直分量(Z轴方向)。 结合电子罗盘等传感器,可将加速度等传感器的坐标与地球位置坐标相连接; 加速度和初速度V0分别分解为经纬度方向和高度方向; 计算经纬度方向和高度方向的位移增量,并换算成经纬度和高度方向的位移增量; GPS(AGPS)模块在两次读数之间的时间段内,结合设备的初始位置(GPS或AGPS检测到的设备位置),得到设备在相应时刻的实际位置。 方向传感器,如电子罗盘等,也可以不用:初始化时,传感器坐标等,如加速度等,与地球位置的相对关系 计算坐标,通过传感器监测设备的方位变化情况,如加速度等,以及传感器坐标等的相对关系,如加速度等, 不断记录地球位置坐标。 [0081]如图4所示,对应于上述获取移动终端位置信息的方法,本实施例还提供了一种移动终端,包括:卫星定位模块、感知模块、控制模块和位置信息处理模块。 模块; 其中, [0082] 卫星定位模块,用于获取移动终端当前的位置信息,并将该位置信息发送给位置信息处理模块; [0083] 控制模块用于开启卫星定位模块,在卫星定位模块获取信息完成后关闭卫星定位模块。 [0084] 传感模块,用于采集移动终端的运动信息,根据运动信息计算移动终端的位移变化量,并将位移变化量发送给位置信息处理模块。 和 [0085] 位置信息处理模块,用于通过对初始位置信息和移动终端的位移变化量进行处理,得到移动终端的实际位置信息。 [0086] 上述控制模块还用于:控制卫星定位模块周期性开启,获取移动终端当前位置信息,更新初始位置信息,控制传感模块将位移变化量设置为零。 [0087] 卫星定位模块为全球定位系统(GPS)模块或辅助全球定位系统(AGPS)模块。 [0088] 本实施例中的动作信息采集模块可以是传感器。 实施例二 [0089] 基于实施例一中的获取移动终端位置信息的方法,本实施例以配置GPS或AGPS模块手机为例。 以GPS(AGPS)模块读取的设备位置为原点,利用加速度传感器和电子罗盘检测设备加速度,计算设备位移增量,从而得到设备实际所在位置 计算对应时刻,及时更新设备位置信息。 GPS(AGPS)模块再次读取位置信息,更新设备初始位置(即之前位移的原点),位移增量设置为0,重新计算位移增量 , 并以此方式循环。 可以设置GPS(AGPS)模块读取位置信息的具体时间阈值或位移阈值,使读取频率低一点,例如每分钟读取一次,这样可以使GPS(AGPS) ) 模块大部分时间处于低功耗休眠状态。 [0090] 获取设备运动信息主要包括:获取并处理加速度,获取初始速度。 [0091] 对于加速度的获取和处理: [0092] 通过加速度传感器获取设备加速度,将加速度分解为水平面分量和垂直分量(本实施例不考虑设备高度方向的变化,只监测水平方向的位移) ; 结合电子罗盘,将加速度的水平分量分解为经纬方向即X、Y方向的ax和ay; 设备加速分解图如图2。 [0093] 加速度传感器读取加速度的频率设置为每10ms读取一次,即t=10ms。 [0094] 设备加速度分别读取为:a1,a2,...。 . . an(假设在GPS的两次读取周期内,加速度传感器读取了n次加速度值)。 [0095] X轴的方向分量分别为:ax1,ax2。 . . 斧头。 [0096]Y轴的方向分量分别为:ay1,ay2。 . . 艾恩。 [0097] 为了获得初始速度: [0098] 初始速度V0的获取是:利用加速度等传感器判断设备的运动状态。 如果设备在静止状态下开启GPS等定位应用,则V0为0,根据传感器检测到的加速度,实时计算并记录相应时刻的速度。 如果设备移动时开启了GPS等定位应用,则利用GPS(AGPS)模块两次读取的位置信息计算位移,进而计算出相应时刻的速度 根据加速度传感器和电子罗盘检测到的设备加速度信息。 上述两种情况都存在误差,可以通过相应的策略不断修正初速度。 例如,当(AGPS)模块读取的位置信息与加速度传感器、电子罗盘计算的数据相差大于一定阈值时,根据位置信息重新计算相应的初速度 由(AGPS)读取本次和上次以及加速度传感器和电子罗盘检测到的设备的加速度信息。 设备速度的获取过程如图3所示。 [0099] 当器件处于静态时,V0x=V0y=V0=0。 [0100] 设备处于运动状态时,V0x和V0y的增益方式如下:(下文涉及经纬度单位和距离单位的换算,本文不再赘述。) [0101] 假设GPS(AGPS)模块两次读取到的设备位置分别在A点和B点,两点之间的距离为AB; GPS(AGPS)模块的读取频率为每分钟一次,即读取A点和B点的时间间隔T=60s; 假设加速度传感器读取加速度的频率为每10ms读取一次,即t=10ms。 [0102] ABx为X轴方向的分量,ABy为Y轴方向的分量, [0103] 然后: ABx=V 0 x×Δt +( V 0 x+ ½× 斧头 1×Δ t )Δ t + 。 . . ( V 0 x+轴 1×Δ t+ . . . ½ axn×Δt )Δ t ① [0104](ax1、ax2、...、axn为T周期内不同时刻加速度传感器读取的加速度值的X轴分量)。 ABy=V 0 y×Δt +( V 0 y+ ½× 哎呀 1×Δ t )Δ t + 。 . . ( V 0 y+y 1×Δ t+ . . . ½ ayn×Δt )Δ t ②[0105] (ay1,ay2,...,ayn为T周期内不同时刻加速度传感器读取的加速度值的Y轴分量)。 [0106] V0x和V0y可以通过上面的①和②得到。 [0107] T周期最后时刻的速度为下一个T周期的初速度,即: [0108] 下一个T周期X轴方向初速度为: V 0 x+轴 1×Δ 吨+。 . . axn×Δt; [0109] 下一个T周期Y轴方向初速度为: V 0 y+y 1×Δ 吨+。 . . ayn×Δt。 [0110] 初速度修正策略: [0111] 将传感器计算出的周期内的位移增量与GPS(AGPS)模块读取的定位距离进行比较; 如果大于2m,则修正初速度。 校正方式可以采用重新获取初速度,方法与上述获取初速度的方式相同。 [0112] 获取加速度信息和初速度信息后计算设备的位移增量,然后根据初始位置信息计算设备的实际位置,具体过程如下。 [0113] 在GPS(AGPS)模块的读取周期T内,利用GPS(AGPS)读取周期T开始时读取的位置S0和传感器计算的位移增量ΔS,可以确定设备的位置P : P=S 0+Δ S. [0114]假设Px、Py为器件在X、Y方向的位置; S0x和S0y分别为T周期起点在X、Y方向的初始位置; ΔSx、ΔSy分别为X、Y方向的位移增量。 然后, [0115] 第k次读取加速度时设备的位置为: Px=S 0 x+ΔSx; △ Sx=V 0 x×Δt +( V 0 x+ ½× 斧头 1×Δ t )Δ t + 。 . . ( V 0 x+轴 1×Δ t+ . . . ½ axk×Δt )Δ t; Py=S 0 y+ΔSy; △ Sy=V 0 y×Δt +( V 0 y+ ½× 哎呀 1×Δ t )Δ t + 。 . . ( V 0 y+y 1×Δ t+ . . . ½ ayk×Δt )Δ t. [0116] 每次计算的设备位置信息是实时更新的,设备位置信息的更新频率可达10ms一次。 可以为用户提供连续的运动路径,解决了数据更新延迟等体验问题。 [0117] T周期结束后,GPS(AGPS)模块再次读取设备位置,新读取的设备位置作为下一周期的初始位置。 将新读取的设备位置与传感器计算出的位置进行比较,以决定是否修正初始速度。 [0118] 通过上述方法,可以使GPS(AGPS)模块大部分时间处于低功耗休眠状态,降低GPS(AGPS)模块的功耗; 可以同时高频率更新位置信息,解决数据更新延迟问题。 [0119] 本领域技术人员可以理解,上述方法中的全部或部分步骤可以通过程序指令相关的硬件部件来完成,该程序可以存储在一个计算机可读取存储介质中,例如只读存储器。 可选地,上述实施例中的全部或部分步骤可以由一个或多个集成电路实现。 相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。 本文档不限制任何特定形式的硬件和软件的结合。 [0120] 以上所述是本发明实施例结合优选实施方式所做的详细说明,不能认定本发明实施例的实施只局限于这些说明。 对于本文件所属领域的技术人员来说,在不脱离本文件实施例构思的情况下,还可以做出若干简单的推演或替换,所有推演或替换均应视为体现在本文件的范围内 随附的权利要求。 工业实用性 [0121] 本发明实施例能够降低移动终端位置信息获取模块的功耗。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102901975A(String), JP2016502647A(String), JP6072266B2(String), KR101784860B1(String), KR1020150065783A(String), US20150304985A1(String), US9451580B2(String), WO2013182147A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.690 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.690 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102901975A(String), JP2016502647A(String), JP6072266B2(String), KR101784860B1(String), KR1020150065783A(String), US20150304985A1(String), US9451580B2(String), WO2013182147A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102901975A(String), JP2016502647A(String), JP6072266B2(String), KR101784860B1(String), KR1020150065783A(String), US20150304985A1(String), US9451580B2(String), WO2013182147A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), CN102901975A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.713 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), JP2016502647A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), JP6072266B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), KR101784860B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.742 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.742 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.742 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), KR1020150065783A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), US20150304985A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270640(Integer), WO2013182147A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9451580B2(String), US9451580B2(String), 1474300800(Integer), 270640(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184957(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184957(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184957(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7809352B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for protecting information in a mobile terminal and a mobile terminal(String), 一种移动终端信息保护方法及移动终端(String), US7809352B2(String), A mobile terminal and a method for protecting information in a mobile terminal, the method includes: sending an information protection command to a mobile terminal via current home mobile switching center of the mobile terminal; the mobile terminal receiving and decoding the command, and executing a protection operation on the information in the mobile terminal according to a protection range defined by the command. When the mobile terminal roams, an information protection command is sent to its current home mobile switching center via a home location register for the mobile terminal. When the mobile terminal is powered off, the command is stored in the home location register, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the command. Thus, information to be protected in a mobile telephone may be deleted or locked via remote operation.(String), 一种移动终端及移动终端中的信息保护方法,该方法包括:通过移动终端当前归属的移动交换中心向移动终端发送信息保护命令; 移动终端接收并解码命令,并根据命令定义的保护范围对移动终端中的信息执行保护操作。 当移动终端漫游时,通过移动终端的归属位置寄存器向其当前归属的移动交换中心发送信息保护命令。 当移动终端关机时,该命令存储在归属位置寄存器中,当移动终端再次开机并通知归属位置寄存器时,归属位置寄存器发送该命令。 因此,可以通过远程操作删除或锁定移动电话中需要保护的信息。(String), US11/595882(String), 1163347200(Integer), US7809352B2(String), 1286208000(Integer), 1286208000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 10(Integer), CN1645951A | CN1809097A | KR1020050078741A | US20040038668A1 | US20050170811A1 | US20060293029A1 | US6741851B1 | US7360078B1 | US7539160B2(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.879 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.879 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.879 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184958(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\4194393d3d7b4c8bb1ab796a3c9d817b.png(String), 184958(Integer), 4194393d3d7b4c8bb1ab796a3c9d817b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for protecting information in a mobile terminal and a mobile terminal(String), 一种移动终端信息保护方法及移动终端(String), US7809352B2(String), A mobile terminal and a method for protecting information in a mobile terminal, the method includes: sending an information protection command to a mobile terminal via current home mobile switching center of the mobile terminal; the mobile terminal receiving and decoding the command, and executing a protection operation on the information in the mobile terminal according to a protection range defined by the command. When the mobile terminal roams, an information protection command is sent to its current home mobile switching center via a home location register for the mobile terminal. When the mobile terminal is powered off, the command is stored in the home location register, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the command. Thus, information to be protected in a mobile telephone may be deleted or locked via remote operation.(String), 一种移动终端及移动终端中的信息保护方法,该方法包括:通过移动终端当前归属的移动交换中心向移动终端发送信息保护命令; 移动终端接收并解码命令,并根据命令定义的保护范围对移动终端中的信息执行保护操作。 当移动终端漫游时,通过移动终端的归属位置寄存器向其当前归属的移动交换中心发送信息保护命令。 当移动终端关机时,该命令存储在归属位置寄存器中,当移动终端再次开机并通知归属位置寄存器时,归属位置寄存器发送该命令。 因此,可以通过远程操作删除或锁定移动电话中需要保护的信息。(String), US11/595882(String), 1163347200(Integer), US7809352B2(String), 1286208000(Integer), 1286208000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 10(Integer), CN1645951A | CN1809097A | KR1020050078741A | US20040038668A1 | US20050170811A1 | US20060293029A1 | US6741851B1 | US7360078B1 | US7539160B2(String), \20230420\4194393d3d7b4c8bb1ab796a3c9d817b.png(String), 17(Integer), 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 1. A method for protecting information in a mobile terminal, comprising:sending a plurality of information protection commands to a mobile terminal via current home mobile switching center of the mobile terminal; andthe mobile terminal receiving the information protection commands and executing an operation indicated by the information protection commands on the information in the mobile terminal according to a protection range defined by the information protection commands, wherein the information protection commands includes parameters for defining an information protection range;wherein the information protection commands comprise an information delete command and an information lock command;wherein the mobile terminal locks the information according to the information lock command; andwherein after receiving the information delete command, the mobile terminal deletes the information which was previously locked by the mobile terminal.(String), 1.根据权利要求1所述的移动终端信息保护方法,其中请求执行操作的用户不知道移动终端的位置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 2. The method for protecting information in a mobile terminal according to claim 1, wherein, when the mobile terminal is powered off, the information protection commands are stored in a home location register for the mobile terminal, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the information protection commands.(String), 12.根据权利要求1所述的移动终端信息保护方法,其中请求执行操作的用户不知道移动终端是开机还是关机。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 3. The method for protecting information in a mobile terminal according to claim 2, wherein the method further comprises: after the mobile terminal executes the protection operation, it returns a response of the operation result.(String), 13.移动终端,包括:数据存储单元,用于存储用户保存的信息;信令收发单元,用于接收多个信息保护命令,其中信息保护命令包括定义信息保护范围的参数,信息保护命令包括信息删除命令和信息锁定命令;和信令处理执行单元,用于对从信令收发单元接收到的信息保护命令进行解码,并对数据存储单元中存储的用户信息执行信息保护命令指示的操作,其中,信令处理执行单元对信息进行锁定根据信息锁定命令,移动终端接收到信息删除命令后,删除先前锁定的信息。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 4. The method for protecting information in a mobile terminal according to claim 1, wherein the information protection range comprises at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information.(String), 14.根据权利要求13所述的移动终端,其中数据存储单元包括通讯录存储区、短信存储区、通话记录存储区、笔记本存储区、备忘存储区和备忘存储区中的至少一个。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 5. The method for protecting information in a mobile terminal according to claim 4, wherein the method further comprises: after the mobile terminal executes the protection operation, it returns a response of the operation result.(String), 15.根据权利要求13所述的移动终端,其中信息保护范围包括通讯录、短信、通话记录、笔记本、备忘、备忘等与隐私信息相关的存储区域中的至少一种。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 6. The method for protecting information in a mobile terminal according to claim 1, wherein the method further comprises: after the mobile terminal executes the protection operation, it returns a response of the operation result.(String), 16.一种移动终端信息保护方法,包括:通过移动终端当前的归属呼叫会话控制功能(CSCF)实体向移动终端发送多个信息保护命令;和移动终端接收并解码信息保护命令,并根据信息保护命令定义的保护范围对移动终端中的信息执行信息保护命令指示的操作,其中信息保护命令包括用于定义信息的参数保护范围;其中,信息保护命令包括信息删除命令和信息锁定命令;其中,移动终端根据信息锁定命令对信息进行锁定;和其中,移动终端接收到信息删除命令后,删除移动终端之前锁定的信息。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 7. The method for protecting information in a mobile terminal according to claim 1, wherein the information protection range comprises an address book, a short message record, a call record, a notebook, a memorandum, a reminder note, information stored on a SIM card, or combinations thereof8. The method for protecting information in a mobile terminal according to claim 1, wherein the information protection range comprises some, but not all of: an address book, a short message record, a call record, a notebook, a memorandum, a reminder note, and information stored on a SIM card.(String), 17.根据权利要求16所述的移动终端信息保护方法,其中当移动终端关机时,信息保护命令存储在移动终端的归属用户服务器中,当移动终端再次开机并通知归属用户服务器时,归属用户服务器发送信息保护命令。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 9. The method for protecting information in a mobile terminal according to claim 1, wherein the parameters for defining the information protection range are two bytes in length.(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 10. The method for protecting information in a mobile terminal according to claim 1, wherein the mobile terminal is in a home area and is powered on.(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 11. The method for protecting information in a mobile terminal according to claim 1, wherein a location of the mobile terminal is unknown to a user requesting execution of the operation.(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 12. The method for protecting information in a mobile terminal according to claim 1, wherein whether the mobile terminal is powered on or off is unknown to a user requesting execution of the operation.(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 13. A mobile terminal, comprising:a data storage unit, for storing information saved by a subscriber;a signaling transceiving unit, for receiving a plurality of information protection commands, wherein the information protection commands include parameters for defining an information protection range, the information protection commands comprise an information delete command and an information lock command; anda signaling processing and execution unit, for decoding the information protection commands received from the signaling transceiving unit, and executing an operation indicated by the information protection commands on subscriber information stored in the data storage unit, wherein the signaling processing and execution unit locks the information according to the information lock command, and deletes the information which was previously locked by the mobile terminal after receiving the information delete command.(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 14. The mobile terminal according to claim 13, wherein the data storage unit comprises at least one of an address book storage area, a short message storage area, a call record storage area, a notebook storage area, a memorandum storage area and a reminder note storage area.(String), 1(Integer), 12(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 15. The mobile terminal according to claim 13, wherein the information protection range comprises at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information.(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 16. A method for protecting information in a mobile terminal, comprising:sending a plurality of information protection commands to a mobile terminal via a current home call session control function (CSCF) entity of the mobile terminal; andthe mobile terminal receiving and decoding the information protection commands and executing an operation indicated by the information protection commands on the information in the mobile terminal according to a protection range defined by the information protection commands, wherein the information protection commands includes parameters for defining an information protection range;wherein the information protection commands comprise an information delete command and an information lock command;wherein the mobile terminal locks the information according to the information lock command; andwherein after receiving the information delete command, the mobile terminal deletes the information which was previously locked by the mobile terminal.(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:36.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184958(Integer), 17. The method for protecting information in a mobile terminal according to claim 16, wherein when the mobile terminal is powered off, the information protection commands are stored in a home subscriber server for the mobile terminal, and when the mobile terminal is powered on again and informs the home subscriber server, the home subscriber server sends the information protection commands.(String), 1(Integer), 15(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184958(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the field of communication, in particular, to a method for protecting information in a mobile terminal and a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the continual development of modern mobile communication technology, mobile telephones have been widely used as a kind of convenient communication tool. The continual combination of mobile telephone technology, computer technology and the like makes a mobile telephone integrated with various functions, such as information storage function including address book, short message, notebook and memorandum, which play an important role in our daily life. Such information stored in a mobile telephone is usually personal privacy and it may be very important for the subscriber of the mobile telephone. [0003]Because mobile telephones are small in volume, they are prone to be lost or stolen. When a mobile telephone of a subscriber is stolen or lost unfortunately, the subscriber may report the loss to a service provider via telephone or in a mobile business hall, so that unnecessary economic loss of call charge will be avoided. However, an implicit loss caused by the leakage of private information stored in the mobile telephone cannot be avoided. For example, short messages communicated with customers will leak out trade secret and business information, which will incur heavy economic loss of the subscriber. SUMMARY OF THE INVENTION [0004]The embodiments of the invention provide a method for protecting information in a mobile terminal and a mobile terminal, which may prevent the private information in a mobile terminal from leaking by remote control. [0005]A technical solution according to an embodiment of the present invention is to provide a method for protecting information in a mobile terminal, which includes:[0006]sending an information protection command to a mobile terminal via current home mobile switching center of the mobile terminal; and[0007]the mobile terminal receiving the information protection command and executing an operation indicated by the information protection command on the information in the mobile terminal according to a protection range defined by the information protection command, wherein the information protection command includes parameters for defining an information protection range. [0008]When the mobile terminal is powered off, the information protection command is stored in a home location register for the mobile terminal, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the information protection command. [0009]The information protection range includes at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information. [0010]The information protection command includes at least one of an information delete command and an information lock command. [0011]In the method, after the mobile terminal executes the protection operation, it returns a response of the operation result. [0012]An embodiment of the invention further provides a mobile terminal, which includes:[0013]a data storage unit, for storing information saved by a subscriber;[0014]a signaling transceiving unit, for receiving an information protection command;[0015]a signaling processing and execution unit, for decoding the information protection command received from the signaling transceiving unit, and executing an operation indicated by the information protection command on subscriber information stored in the data storage unit, wherein the information protection command includes parameters for defining an information protection range. [0016]The data storage unit includes at least one of an address book storage area, a short message storage area, a call record storage area, a notebook storage area, a memorandum storage area and a reminder note storage area. [0017]In the mobile terminal according to the embodiment of the invention, the information protection range includes at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information. The information protection command includes at least one of an information delete command and an information lock command. [0018]An embodiment of the invention further provides another method for protecting information in a mobile terminal, which includes:[0019]sending an information protection command to a mobile terminal via a current home call session control function (CSCF) entity of the mobile terminal;[0020]the mobile terminal receiving and decoding the information protection command, and executing an operation indicated by the information protection command on the information in the mobile terminal according to a protection range defined by the information protection command, wherein the information protection command includes parameters for defining an information protection range. [0021]The method further includes: when the mobile terminal is powered off, the information protection command is stored in a home subscriber server for the mobile terminal, and when the mobile terminal is powered on again and informs the home subscriber server, the home subscriber server sends the information protection command. [0022]The mobile terminal and the method for protecting information in the mobile terminal according to the embodiments of the invention may have the following beneficial effects: when a mobile terminal of a subscriber, such as a mobile telephone, is lost, or when information in a terminal needs to be remotely protected (the owner of the terminal cannot operate on it on site) for other reasons, a protection command may be sent to the remote mobile terminal via a maintenance and management system of a mobile switching center or a home location register, and information to be protected in the terminal may be deleted or locked, so that trouble and loss caused by information leakage will be avoided. BRIEF DESCRIPTION OF THE DRAWINGS [0023]FIG. 1 shows a structural diagram of a communication network for realizing information protection in a mobile terminal according to an embodiment of the invention; [0024]FIG. 2 shows a flow chart of the first embodiment of a method for protecting information in a mobile terminal according to the invention; [0025]FIG. 3 shows a flow chart of the second embodiment of a method for protecting information in a mobile terminal according to the invention; [0026]FIG. 4 shows a structural diagram of parameters carried in an information delete command in an embodiment of the invention; [0027]FIG. 5 shows a flow chart of information protection executed in a mobile terminal according to an embodiment of the invention; [0028]FIG. 6 shows an architecture diagram of a multimedia system based on IP according to an embodiment of the invention; [0029]FIG. 7 shows a structural diagram of a communication network of a multimedia system based on IP for realizing information protection in a mobile terminal according to an embodiment of the invention. DETAILED DESCRIPTION OF THE INVENTION [0030]The invention will now be further described in conjunction with the drawings and embodiments of the invention. [0031]FIG. 1 shows a structural diagram of a communication network for realizing information protection in a mobile terminal according to an embodiment of the invention. As shown in FIG. 1, a typical mobile communication network (such as GSM network) mainly includes a mobile station, a base station subsystem, a mobile switching subsystem and an operation and maintenance center, etc. A mobile station, i.e. a mobile terminal 101 of a subscriber, may perform speech encoding, channel encoding, information encryption, information modulation and demodulation, and information transmitting and receiving. For example, in GSM communication system, mobile terminal 101 may be equipped with a Subscriber Identity Module (SIM) card, in which all of the information needed to authenticate a subscriber identity is stored. The mobile terminal 101 cannot access a network until a SIM card is inserted. However, the invention is not limited to such a communication system, and it can also be applied to other communication systems without using SIM cards (GSM system) or UIM cards (CDMA system), such as PHS(Personal handy-phone system) and various foreign communication systems without using subscriber cards. The base station subsystem mainly performs such functions as channel allocation in a coverage area, accessing and paging of a subscriber, and information transmission, etc. The base station subsystem includes a base station transceiver (BTS) 102 directly in communication with the mobile terminal 101 via a wireless interface, and a base station controller (BSC) 103 connected with a mobile switching center (MSC) 104, wherein the base station transceiver 102 is responsible for wireless transmission and the base station controller 103 is responsible for control and management. A base station subsystem usually includes a base station controller and one or more base station transceivers. The base station transceiver 102 may be connected directly with the base station controller 103, or it may also be connected with a remote base station controller via a base station interface equipment. The mobile switching subsystem performs communication switching function and manages a database needed by subscriber data and mobility at the same time. The mobile switching subsystem includes a mobile switching center (MSC) 104, a visitor location register (VLR) 105, a home location register (HLR) 106, an authentication center and an equipment identity register (not shown) etc. The mobile switching center 104 controls mobile terminal 101 within its coverage area, provides processing, control and bearer path for calls and services, and obtains all the data needed to process a subscriber call request from three databases, i.e., the visitor location register 105, the home location register 106 and the authentication center. Similarly, the mobile switching center 104 may update the above databases according to the latest data. The visitor location register 105 stores subscriber data related to the mobile terminals within a controlled area of the mobile switching center 104, wherein the subscriber data includes parameters such as subscriber number, location area information, subscriber status and services available to a subscriber. The visitor location register 105 is a dynamic subscriber database for storing necessary data obtained from the home location register 106 of a mobile subscriber. Once the mobile subscriber leaves a controlled area of the visitor location register, it will be registered in another visitor location register, and the previous visitor location register will cancel data record of the mobile subscriber. The home location register 106 mainly stores two kinds of information: parameters related to mobile subscribers, including such data as mobile subscriber identification number, accessibility, subscriber type, etc., and information related to current locations of mobile subscribers by which call routing to a mobile terminal may be established. Therefore, each mobile subscriber should be registered at its home location register. An operation and maintenance center (OMC) 107, which is provided with an OMC operating platform to realize the man-machine interface of the operation and maintenance center 107, manages the switching entities of the whole mobile communication system. [0032]FIG. 1 shows a schematic diagram of a typical mobile communication network for implementing an embodiment of the invention. However, the invention is not limited to that. The mobile communication network includes various existing mobile communication networks, such as GSM, GPRS, CDMA etc., for example, a multimedia system based on IP shown in FIG. 6. The call session control function (CSCF) entity shown in FIG. 6 acts as a mobile switching center, while the home subscriber server (HSS) acts as an HLR. The messaging function between the CSCF and HSS entities keeps unchanged. In addition, the base station and the base station controller are not shown in FIG. 6, and the structure of a mobile access network under the IMS networking also keeps unchanged. FIG. 7 shows the structure of a communication network of a multimedia system based on IP for realizing information protection in a mobile terminal according to an embodiment of the invention, the principle of which is the same as that in FIG. 1 and will not be described in detail here. The mobile terminal according to the embodiment includes mobile telephone, SIP terminal, personal digital assistant (PDA), mobile business assistant and other handheld terminals that are capable of accessing a mobile communication network for mobile communication. [0033]When a mobile terminal of a subscriber is lost, or when information in a terminal needs to be remotely protected (the owner of the terminal cannot operate on it on site) for other reasons, there exist three cases: the subscriber knows definitely that the terminal is within the home area (not roamed across mobile switching centers) and is powered on; the subscriber does not know whether his/her mobile terminal is within the home area; and the mobile terminal is powered off. [0034]FIG. 2 shows a flow chart of a method for protecting information in a mobile terminal according to an embodiment of the invention in the first case. As shown in FIG. 2, when current home mobile switching center of the mobile terminal is known, the subscriber may send an information delete command to his/her mobile terminal via the mobile switching center, and the mobile terminal will delete related information therein based on the content of the command. The particular steps are as follows: [0035]Firstly, the subscriber requests for a credible identity verification to an authentication center of the mobile communication network, which can be realized by various subscriber identifying methods in the prior art. For example, the subscriber may go to a business hall of the network service provider, and a staff member of the business hall may verify the subscriber identity by verifying the subscriber identity card and then operate via a man-machine platform of the operation and maintenance center. The subscriber may also employ a procedure similar to reporting the loss of a mobile telephone, that is, the subscriber may be verified through his/her service password via telephone. [0036]Then in step 202, the mobile switching center sends an information delete command to the base station controller within its controlled area. The information delete command may contain parameters for defining an operation range of information delete, indicating which information to be deleted. For example, information stored in a mobile telephone, such as address book, short message record, call record, notebook, memorandum, reminder note, etc. and/or information stored in the SIM card of the subscriber, or one or a combination of more than one of the above items may be selected. [0037]In step 204, after the base station controller receives the information delete command from the mobile switching center, it will modulate and transmit the information delete command to an air interface via one or more base station transceivers within its coverage area. [0038]In step 206, the mobile terminal receives the information delete command via a corresponding air interface and deletes data within the specified range as indicated by the information delete command and the parameters contained therein. After the operation is performed, the mobile terminal returns a response message to the base station controller to indicate whether the operation succeeds. [0039]In step 208, after the base station controller receives the response message via one or more base station transceivers connected with it, it passes the response message to the mobile switching center. Then, the mobile switching center may inform the subscriber of the operation response via the man-machine platform of the operation and maintenance center. [0040]If the embodiment is implemented in the network architecture shown in FIG. 6, the mobile switching center or the visitor location register of FIG. 2 will be replaced by the call session control function (CSCF) entity of FIG. 6. [0041]For the second case in which a mobile terminal roams across mobile switching centers, a flow chart of the method for protecting information in a mobile terminal according to an embodiment of the invention is shown in FIG. 3. [0042]Firstly, in step 302, information of the current location and status of the mobile terminal needs to be obtained via a home location register, and an information delete command is sent to the current home mobile switching center of the mobile terminal via the home location register. The information delete command may contain parameters for defining an operation range of information delete, in which information to be deleted is indicated. For example, information stored in a mobile telephone such as address book, short message record, call record, notebook, memorandum, reminder note, etc. and/or information stored in the SIM card of the subscriber, or one or a combination of more than one of the above items may be selected. [0043]Then in step 304, the current home mobile switching center of the mobile terminal transfers the information delete command to a base station controller of its controlled area. [0044]In step 306, the base station controller transmits the information delete command received from the mobile switching center to an air interface via one or more base station transceivers within its coverage area. [0045]In step 308, the mobile terminal receives the information delete command via a corresponding air interface and deletes data within the specified range as indicated by the information delete command and the parameters contained therein. After the operation is performed, the mobile terminal returns a response message to the base station controller to indicate whether the operation succeeds. [0046]Then in step 310, after the base station controller receives the response message via one or more base station transceivers connected with it, it passes the response message to the mobile switching center. [0047]In step 312, the current home mobile switching center of the mobile terminal passes the response message received from its base station controller to the home location register, and the home location register informs the subscriber of the operation response via the man-machine platform of the operation and maintenance center. [0048]Similarly, if information protection is realized in the network architecture shown in FIG. 6 when a mobile terminal roams across mobile switching centers, the mobile switching center or the visitor location register of FIG. 3 should be replaced by the call session control function (CSCF) entity of FIG. 6, and the home location register of FIG. 3 should be replaced by the home subscriber server (HSS) of FIG. 6. [0049]If a mobile terminal is powered off and cannot receive an information delete command when a subscriber requires to delete information in the mobile terminal, an “information delete” flag may be set in a corresponding location in a home location register, which indicates that the mobile terminal needs information protection, and at the same time, parameters and parameter contents related to the information delete command may be stored in the home location register. When the mobile terminal is powered on again, a location update procedure will be triggered and the current home mobile switching center of the mobile terminal will send a message to inform the home location register of the subscriber of the latest location and status of the mobile terminal. At this time, the home location register may start the above information delete operation based on the “information delete” flag and related parameters stored therein. [0050]In the method for protecting information in a mobile terminal according to the embodiment, the information delete command sent to and received and executed by the mobile terminal contains parameters for defining a delete operation range. The parameters may be encoded in various ways. For example, the parameters may be in TLV format, that is, the parameters may comprise parameter name T, parameter length L and parameter content V. FIG. 4 shows one form of such a parameter, wherein Octet 1 refers to parameter name, Octet 2 refers to parameter length and Octet 3 to Octet k refer to parameter content. As a result, one or more contents may be included in the parameter. As for parameter “delete range”, the length of parameter name may be 1 byte, or 3 bytes or the like. For example, it may be set as 0x01, or any other value, so long as it is different from the names of other existing parameters. The length of the parameter may be 0x02, which indicates that the length of the parameter is 2 bytes. It may also be defined longer, for example 3 bytes, so as to represent more parameter contents. The parameter content indicating a “delete range” may be represented by 2 bytes, for example: [0051]byte 10x010x02. . .Mobile TerminalSubscriber CardStorage AreaStorage Areabyte 20x010x020x03. . .Short MessageAddress BookNotebookStorage AreaStorage AreaStorage Area [0052]Parameter content may be in a more compact format or in any other format. For example, parameter content may be compressed in one byte. [0053]The mobile terminal according to an embodiment of the invention mainly includes a signaling transceiving unit, a signaling processing and execution unit, and a data storage unit. The signaling transceiving unit is responsible for receiving a message from an air interface and passing the message command to the signaling processing and execution unit. It is also responsible for processing messages from the signaling processing and execution unit and sending the processed messages to an air interface via wireless signals. The signaling processing and execution unit is responsible for identifying an information delete command from the message received from the signaling transceiving unit, decoding the message, resolving the “delete range” parameter and contents of the parameter therein, performing data delete operation according to the contents of the parameter so as to delete corresponding information in the data storage unit, and creating a response message to be sent to a base station controller. The data storage unit is used to store data saved by the subscriber. the data storage unit includes a mobile terminal storage area and a subscriber card storage area in respect of physical entities for storing, and includes an address book storage area, a short message storage area, a call record storage area, a notebook storage area, a memorandum storage area, and a reminder note storage area, etc. in respect of the contents stored therein. Each storage area in the data storage unit may be added, deleted, modified, queried or locked, etc. After an operation is executed, an execution result will be returned to the invoker. [0054]FIG. 5 shows a flow chart of information protection executed in a mobile terminal according to an embodiment of the invention. As shown in FIG. 5, a particular operation flow in a mobile terminal is as follows: [0055]In step 402, the signaling transceiving unit of the mobile terminal receives an information delete command in the form of wireless signal from a base station transceiver via an air interface, and demodulates the wireless signal. Various message contents are resolved and then passed to the signaling processing and execution unit. [0056]In step 404, after the signaling processing and execution unit identifies the received message as an information delete command, it decodes the message and resolves a parameter “delete range” and the content of the parameter contained therein. [0057]In step 406, the signaling processing and execution unit deletes data in specific storage areas of the data storage unit according to the content of the parameter “delete range”. For example, a deleting operation range indicated in a two-byte parameter content “delete range” of the above example includes “address book storage area”, “short message storage area” and “notebook storage area” of the “mobile terminal storage area” and the “subscriber card storage area”, thus the signaling processing and execution unit will delete the contents of all address books, all short messages and all notebooks in the data storage unit as indicated by the parameter “delete range”. [0058]In step 408, after the deleting operation is performed, the data storage unit returns a data deletion result to the signaling processing and execution unit. [0059]In step 410, the signaling processing and execution unit creates an information delete response message containing the operation result according to the deletion result, and passes the response message to the signaling transceiving unit. [0060]In step 412, the signaling transceiving unit modulates the information delete response message created by the signaling processing and execution unit, and sends it to an air interface in the form of wireless signal. [0061]In another embodiment of the invention, a subscriber may send an information lock command to his/her mobile terminal via a mobile switching center. The mobile terminal locks the related information therein according to parameter contents of the information lock command so as to prevent illegal access. The method for sending an information lock command and the method for processing the information lock command by a mobile terminal according to the embodiment are similar to those for the above information delete command. The information lock command contains parameters for defining a lock range, which can be encoded in similar ways to those for the above information delete command. The information lock command may be used in cases in which a subscriber cannot be sure whether his/her mobile terminal is lost indeed. If it is found out that the mobile terminal is not lost, the subscriber may operate on the mobile terminal to unlock it and regain access to related data. This can be realized in various ways of the prior art. If it is found out that the mobile terminal is lost indeed, then the subscriber may send an information delete command via the mobile switching center to permanently delete the related information in the mobile terminal. [0062]It should be understood that the above detailed description of the particular embodiments is only illustrative of the present invention and should not be construed as limiting the scope of the invention which is defined by the appended claims.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端中的信息保护方法及移动终端。 发明背景 [0002] 随着现代移动通讯技术的不断发展,手机作为一种便捷的通讯工具得到了广泛的应用。 移动电话技术、计算机技术等的不断结合,使得手机集多种功能于一体,例如通讯录、短信、笔记本、备忘录等信息存储功能,在我们的日常生活中扮演着重要的角色。 这些存储在移动电话中的信息通常属于个人隐私,对于移动电话用户而言可能非常重要。 [0003] 由于手机体积小,容易丢失或被盗。 当用户的手机不幸被盗或丢失时,用户可以通过电话或到移动营业厅向服务提供商挂失,从而避免不必要的话费经济损失。 但是,手机中存储的隐私信息泄露所带来的隐性损失是无法避免的。 例如,与客户通信的短信会泄露商业秘密和商业信息,给用户带来巨大的经济损失。 发明内容 [0004] 本发明实施例提供一种移动终端中信息的保护方法及移动终端,能够防止移动终端中的隐私信息被远程控制泄露。 [0005] 本发明实施例提供的技术方案是提供一种移动终端中的信息保护方法,包括: [0006]通过移动终端当前归属移动交换中心向移动终端发送信息保护命令; 和[0007] 移动终端接收信息保护命令,并根据信息保护命令定义的保护范围,对移动终端中的信息执行信息保护命令指示的操作,其中,信息保护命令包括用于定义信息保护范围的参数 . [0008] 当移动终端关机时,信息保护命令存储在移动终端的归属位置寄存器中,当移动终端再次开机并通知归属位置寄存器时,归属位置寄存器发送信息保护命令。 [0009] 信息保护范围包括通讯录、短信、通话记录、笔记本、备忘录、备忘等与隐私信息相关的存储区域中的至少一种。 [0010] 信息保护命令包括信息删除命令和信息锁定命令中的至少一种。 [0011] 该方法中,移动终端执行保护操作后,返回操作结果响应。 [0012] 本发明实施例还提供一种移动终端,包括: [0013] 数据存储单元,用于存储用户保存的信息;[0014] 信令收发单元,用于接收信息保护命令;[0015] 信令处理和执行单元,用于对从信令收发单元接收到的信息保护命令进行解码,并对数据存储单元中存储的用户信息执行信息保护命令指示的操作,其中,信息保护命令包括用于定义 信息保护范围。 [0016] 数据存储单元包括通讯录存储区、短信存储区、通话记录存储区、笔记本存储区、备忘录存储区和备忘存储区中的至少一个。 [0017] 在根据本发明实施例的移动终端中,信息保护范围包括通讯录、短信、通话记录、笔记本、备忘录、备忘和其他与隐私信息相关的存储区域中的至少一种。 信息保护命令包括信息删除命令和信息锁定命令中的至少一种。 [0018] 本发明实施例还提供了另一种移动终端中的信息保护方法,包括: [0019] 通过移动终端当前的归属呼叫会话控制功能(CSCF)实体向移动终端发送信息保护命令;[0020] 移动终端接收并解码信息保护命令,根据信息保护命令定义的保护范围,对移动终端中的信息执行信息保护命令指示的操作,其中,信息保护命令包括用于定义信息保护命令的参数 信息保护范围。 [0021] 该方法还包括:当移动终端关机时,将信息保护命令存储在移动终端的归属用户服务器中,当移动终端再次开机并通知归属用户服务器时,归属用户服务器发送 信息保护命令。 [0022]根据本发明实施例的移动终端及移动终端中的信息保护方法,可以具有以下有益效果:当用户的移动终端如手机丢失时,或者当终端中的信息丢失时。 其他原因需要远程保护(终端所有者不能现场操作),可以通过移动交换中心维护管理系统或归属位置寄存器向远程移动终端发送保护命令, 终端中需要保护的信息可以被删除或锁定,从而避免信息泄露带来的麻烦和损失。 附图的简要说明 [0023] 图1示出了根据本发明实施例的在移动终端中实现信息保护的通信网络的结构图; [0024] 图2为本发明移动终端信息保护方法第一实施例的流程图; [0025] 图3为本发明移动终端信息保护方法第二实施例的流程图; [0026] 图4为本发明实施例中信息删除命令携带的参数结构图; [0027] 图5示出了根据本发明实施例的在移动终端中执行的信息保护的流程图。 [0028] 图6示出了根据本发明实施例的基于IP的多媒体系统的架构图。 [0029] 图7示出了根据本发明实施例的用于在移动终端中实现信息保护的基于IP的多媒体系统的通信网络结构图。 发明详述 [0030] 下面结合附图和实施例对本发明作进一步说明。 [0031] 图1示出了根据本发明实施例的用于在移动终端中实现信息保护的通信网络的结构图。 如图1所示,一个典型的移动通信网络(如GSM网络)主要包括移动台、基站子系统、移动交换子系统和运维中心等。移动台,即移动终端 101 一个用户,可以进行语音编码、信道编码、信息加密、信息调制解调、信息发送和接收。 例如,在 GSM 通信系统中,移动终端 101 可以配备用户身份模块 (SIM) 卡,其中存储了验证用户身份所需的所有信息。 移动端 101 在插入 SIM 卡之前无法访问网络。 但是,本发明不限于这样的通信系统,也可以应用于不使用SIM卡(GSM系统)或UIM卡(CDMA系统)的其他通信系统,例如PHS(Personal handy-phone system)和 不使用用户卡的各种外国通信系统。 基站子系统主要完成覆盖区域内的信道分配、用户接入和寻呼、信息传输等功能。基站子系统包括基站收发信机(BTS) 102 直接与移动终端通信 101 通过无线接口和基站控制器 (BSC) 103 与移动交换中心 (MSC) 相连 104 ,其中基站收发器 102 负责无线传输和基站控制器 103 负责控制和管理。 基站子系统通常包括基站控制器和一个或多个基站收发器。 基站收发器 102 可以直接与基站控制器相连 103,也可以通过基站接口设备与远程基站控制器相连。 移动交换子系统执行通信交换功能,同时管理用户数据和移动性所需的数据库。 移动交换子系统包括移动交换中心(MSC) 104 , 访客位置寄存器 (VLR) 105 , 归属位置寄存器 (HLR) 106 、认证中心和设备身份寄存器(未示出)等。移动交换中心 104 控制移动端 101 在其覆盖范围内,为呼叫和服务提供处理、控制和承载路径,并从访客位置寄存器三个数据库中获取处理用户呼叫请求所需的所有数据 105 , 归属地寄存器 106 和认证中心。 同样,移动交换中心 104 可能会根据最新数据更新上述数据库。 访客位置寄存器 105 在移动交换中心的受控区域内存储与移动终端相关的用户数据 104 其中,用户数据包括用户号码、位置区域信息、用户状态和用户可获得的服务等参数。 访客位置寄存器 105 是一个动态用户数据库,用于存储从归属位置寄存器获得的必要数据 106 一个移动用户。 一旦移动用户离开访问者位置寄存器的控制区域,它将在另一个访问者位置寄存器中注册,之前的访问者位置寄存器将取消该移动用户的数据记录。 家庭位置寄存器 106 主要存储两种信息:与移动用户相关的参数,包括移动用户标识号、可接入性、用户类型等数据,以及与移动用户当前位置相关的信息,通过这些信息可以建立到移动终端的呼叫路由 . 因此,每个移动用户都应该在其归属位置寄存器中进行注册。 运维中心(OMC) 107 ,配备OMC操作平台,实现运维中心人机界面 107 ,管理整个移动通信系统的交换实体。 [0032] 图1示出了用于实施本发明实施例的典型移动通信网络的示意图。 然而,本发明不限于此。 移动通信网络包括现有的各种移动通信网络,例如GSM、GPRS、CDMA等,例如图6所示的基于IP的多媒体系统。图6所示的呼叫会话控制功能(CSCF)实体作为 移动交换中心,而归属用户服务器 (HSS) 充当 HLR。 CSCF和HSS实体之间的消息传递功能保持不变。 另外,图6中没有显示基站和基站控制器,IMS组网下的移动接入网络结构也保持不变。 图7示出了根据本发明实施例的基于IP实现移动终端信息保护的多媒体系统的通信网络结构,其原理与图1相同,在此不再赘述。 细节在这里。 本实施例的移动终端包括移动电话、SIP终端、个人数字助理(Personal Digital Assistant,PDA)、移动商务助理等能够接入移动通信网络进行移动通信的手持终端。 [0033] 当用户的移动终端丢失,或其他原因需要对终端信息进行远程保护(终端所有者无法现场操作)时,存在三种情况: 用户明确知道终端 在家庭区域内(未跨移动交换中心漫游)并且已开机; 用户不知道自己的移动终端是否在归属地范围内; 移动终端关机。 [0034]图2示出了第一种情况下根据本发明实施例的移动终端中的信息保护方法的流程图。 如图2所示,当移动终端当前归属的移动交换中心已知时,用户可以通过移动交换中心向其移动终端发送信息删除命令,移动终端将根据移动终端删除其中的相关信息。 命令的内容。 具体步骤如下: [0035] 首先,用户向移动通信网络的认证中心请求可信身份验证,这可以通过现有技术中的各种用户识别方法来实现。 例如,用户可以前往网络服务提供商的营业厅,营业厅的工作人员可以通过验证用户身份证来验证用户身份,然后通过运维人机平台进行操作。 中央。 用户也可以采用类似手机挂失的流程,即通过电话通过服务密码对用户进行验证。 [0036] 然后一步 202 ,移动交换中心向其控制区域内的基站控制器发送信息删除命令。 信息删除命令中可以包含定义信息删除操作范围的参数,指示删除哪些信息。 例如,手机中存储的通讯录、短信记录、通话记录、笔记本、备忘、备忘等信息和/或用户SIM卡中存储的信息,或其中一种或多种的组合 可以选择以上项目中的一项以上。 [0037] 在步 204 基站控制器接收到来自移动交换中心的信息删除命令后,将信息删除命令调制后通过其覆盖范围内的一个或多个基站收发器发送至空中接口。 [0038] 在步 206 ,移动终端通过相应的空口接收信息删除命令,根据信息删除命令及其中包含的参数,删除指定范围内的数据。 操作完成后,移动终端向基站控制器返回响应消息,指示操作是否成功。 [0039] 在步 208 ,基站控制器通过与之相连的一个或多个基站收发器接收到响应消息后,将响应消息传递给移动交换中心。 然后,移动交换中心可以通过操作维护中心的人机平台将操作响应告知用户。 [0040] 如果该实施例在图6所示的网络架构中实现,则图2的移动交换中心或访问者位置寄存器将被图6的呼叫会话控制功能(CSCF)实体代替。 [0041] 针对移动终端漫游跨越移动交换中心的第二种情况,本发明实施例的移动终端信息保护方法的流程图如图3所示。 [0042] 首先,一步 302 ,需要通过归属位置寄存器获取移动终端的当前位置和状态信息,并通过归属位置寄存器向移动终端的当前归属移动交换中心发送信息删除命令。 信息删除命令中可以包含定义信息删除操作范围的参数,其中指示要删除的信息。 例如,手机中存储的通讯录、短信记录、通话记录、笔记本、备忘、备忘等信息和/或用户SIM卡中存储的信息,或其中一种或多种的组合 可以选择以上项目之一。 [0043] 然后一步 304 ,移动终端的当前归属移动交换中心将信息删除命令传递给其控制区的基站控制器。 [0044] 在步 306,基站控制器通过其覆盖范围内的一个或多个基站收发器,将接收到的来自移动交换中心的信息删除命令发送至空中接口。 [0045] 在步 308 ,移动终端通过相应的空口接收信息删除命令,根据信息删除命令及其中包含的参数,删除指定范围内的数据。 操作完成后,移动终端向基站控制器返回响应消息,指示操作是否成功。 [0046] 然后一步 310 ,基站控制器通过与之相连的一个或多个基站收发器接收到响应消息后,将响应消息传递给移动交换中心。 [0047] 在步 312 ,移动终端的当前归属移动交换中心将从其基站控制器接收到的响应消息传递给归属位置寄存器,归属位置寄存器通过运维人机平台将操作响应通知用户 中央。 [0048] 类似地,如果在图6所示的网络架构中实现移动终端漫游跨移动交换中心时的信息保护,则图3的移动交换中心或访问者位置寄存器应该由呼叫会话控制功能(CSCF)实体代替 图6的归属位置寄存器和图3的归属位置寄存器应该由图6的归属订户服务器(HSS)代替。 [0049] 如果当用户要求删除移动终端中的信息时,移动终端处于关机状态,无法接收到信息删除命令,则可以在归属位置寄存器中的相应位置设置“信息删除”标志,表示该移动终端 终端需要信息保护,同时归属位置寄存器中可以存储与信息删除命令相关的参数和参数内容。 当移动终端再次开机时,将触发位置更新流程,移动终端当前归属移动交换中心发送消息通知用户归属位置寄存器该移动终端的最新位置和状态 . 此时,归属位置寄存器可以根据其中存储的“信息删除”标志和相关参数启动上述信息删除操作。 [0050] 本实施例提供的移动终端中的信息保护方法,向移动终端发送接收并执行的信息删除命令中包含定义删除操作范围的参数。 可以以各种方式对参数进行编码。 例如,参数可以是TLV格式,即参数可以包括参数名称T、参数长度L和参数内容V。图4示出了这种参数的一种形式,其中Octet 1 指参数名,Octet 2 指参数长度和Octet 3 到Octet k 参考参数内容。 结果,参数中可以包括一个或多个内容。 对于参数“删除范围”,参数名的长度可以是1个字节,也可以是3个字节等。 例如,可以设置为0x01,或者其他任何值,只要与其他已有参数的名称不同即可。 参数的长度可以是0x02,表示参数的长度是2个字节。 也可以定义的更长一些,比如3个字节,以表示更多的参数内容。 表示“删除范围”的参数内容可以用2个字节来表示,例如: [0051] 字节 1 0x01 0x02 . . . 手机端 用户卡 储藏区域 储藏区域 字节 2 0x01 0x02 0x03 . . . 短消息 地址簿 笔记本 储藏区域 储藏区域 储藏区域 [0052] 参数内容可以采用更紧凑的格式或任何其他格式。 例如,参数内容可以压缩成一个字节。 [0053]本发明实施例的移动终端主要包括信令收发单元、信令处理执行单元和数据存储单元。 信令收发单元负责从空中接口接收消息,并将消息命令传递给信令处理执行单元。 它还负责处理来自信令处理执行单元的消息,并将处理后的消息通过无线信号发送到空中接口。 信令处理执行单元负责从信令收发单元接收到的报文中识别信息删除命令,对报文进行解码,解析其中的“删除范围”参数和参数内容,根据内容进行数据删除操作 参数删除数据存储单元中的相应信息,并生成响应消息发送给基站控制器。 数据存储单元用于存储用户保存的数据。 数据存储单元包括移动终端存储区和用户卡存储区,就存储物理实体而言,包括通讯录存储区、短信存储区、通话记录存储区、笔记本存储区、 备忘录存储区和备忘存储区等就存储在其中的内容而言。 数据存储单元中的每个存储区域都可以进行增删改查、查询或锁定等操作,执行完一个操作后,会返回一个执行结果给调用者。 [0054] 图5示出了根据本发明实施例的在移动终端中执行的信息保护的流程图。 如图5所示,移动终端中的具体操作流程如下: [0055] 在步 402 移动终端的信令收发单元通过空中接口从基站收发器接收无线信号形式的信息删除命令,并对无线信号进行解调。 解析各种消息内容,然后传递给信令处理和执行单元。 [0056] 在步 404 信令处理与执行单元将接收到的消息识别为信息删除命令后,对该消息进行解码,解析出参数“删除范围”以及其中包含的参数内容。 [0057] 在步 406 、信令处理与执行单元根据参数“删除范围”的内容删除数据存储单元的特定存储区域中的数据。 例如,上述例子的二字节参数内容“删除范围”所指示的删除操作范围包括“移动终端存储区”的“通讯录存储区”、“短信存储区”和“笔记本存储区” ”和“用户卡存储区”,则信令处理执行单元将删除参数“删除范围”所指示的数据存储单元中的所有通讯录、所有短信和所有笔记本的内容。 [0058] 在步 408 ,在执行删除操作后,数据存储单元向信令处理执行单元返回数据删除结果。 [0059] 在步 410 ,信令处理执行单元根据删除结果创建包含操作结果的信息删除响应消息,并将该响应消息传递给信令收发单元。 [0060] 在步 412 、信令收发单元对信令处理执行单元生成的信息删除响应消息进行调制,以无线信号的形式发送至空中接口。 [0061]在本发明的另一个实施例中,用户可以通过移动交换中心向他/她的移动终端发送信息锁定命令。 移动终端根据信息锁定命令的参数内容锁定其中的相关信息,以防止非法访问。 本实施例的移动终端发送信息锁定命令的方法和处理信息锁定命令的方法与上述信息删除命令类似。 信息锁定命令中包含定义锁定范围的参数,其编码方式与上述信息删除命令类似。 信息锁定命令可以用于用户不能确定自己的移动终端是否确实丢失的情况。 如果发现移动终端没有丢失,用户可以在移动终端上操作解锁,重新获取相关数据。 这可以通过现有技术的各种方式来实现。 如果发现移动终端确实丢失,则用户可以通过移动交换中心发送信息删除命令,永久删除移动终端中的相关信息。 [0062] 应当理解,以上对特定实施例的详细描述仅是对本发明的说明,不应被解释为限制由所附权利要求限定的本发明的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN100471312C(String), CN101161006A(String), CN101161006B(String), CN1874596A(String), US20070111728A1(String), US7809352B2(String), WO2007054004A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN100471312C(String), CN101161006A(String), CN101161006B(String), CN1874596A(String), US20070111728A1(String), US7809352B2(String), WO2007054004A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7809352B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN100471312C(String), CN101161006A(String), CN101161006B(String), CN1874596A(String), US20070111728A1(String), US7809352B2(String), WO2007054004A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), CN100471312C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.076 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.076 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), CN101161006A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), CN101161006B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), CN1874596A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.107 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.107 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), US20070111728A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), US7809352B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270641(Integer), WO2007054004A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7809352B2(String), US7809352B2(String), 1286208000(Integer), 270641(Integer), 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.146 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184958(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184958(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.172 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184958(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.183 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75909(Integer), 2(Integer), 184958(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.191 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75909(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.215 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20150067795A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Control method and device for mobile terminal, and mobile terminal(String), 移动终端的控制方法、装置及移动终端(String), US20150067795A1(String), The present invention relates to the field of mobile communications, and provides a control method and device of a mobile terminal, and the mobile terminal. The control method of a mobile terminal comprises: a control device of a mobile terminal receiving a first switching instruction that instructs switching the mobile terminal to a security mode; and the control device of the mobile terminal performing control processing on the mobile terminal according to the first switching instruction, and switching the mobile terminal to the security mode, so that the mobile terminal does not send service data to a base station. The technical solution of the present invention can effectively protect the information security of the mobile terminal.(String), 本发明涉及移动通信领域,提供了一种移动终端的控制方法、装置及移动终端。 一种移动终端的控制方法,包括:移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,使得移动终端不向基站发送业务数据。 本发明的技术方案能够有效保护移动终端的信息安全。(String), US14/391580(String), 1340553600(Integer), US20150067795A1(String), 1425484800(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 9(Integer), CN201515419U | US20050267650A1 | US20100279626A1 | US20110065375A1 | US20110241827A1 | US20120052879A1 | US20120299847A1 | US20150082422A1 | US8126431B2(String), 18(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184959(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\064677ae5cef47d5809aea2682ba0406.png(String), 184959(Integer), 064677ae5cef47d5809aea2682ba0406.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Control method and device for mobile terminal, and mobile terminal(String), 移动终端的控制方法、装置及移动终端(String), US20150067795A1(String), The present invention relates to the field of mobile communications, and provides a control method and device of a mobile terminal, and the mobile terminal. The control method of a mobile terminal comprises: a control device of a mobile terminal receiving a first switching instruction that instructs switching the mobile terminal to a security mode; and the control device of the mobile terminal performing control processing on the mobile terminal according to the first switching instruction, and switching the mobile terminal to the security mode, so that the mobile terminal does not send service data to a base station. The technical solution of the present invention can effectively protect the information security of the mobile terminal.(String), 本发明涉及移动通信领域,提供了一种移动终端的控制方法、装置及移动终端。 一种移动终端的控制方法,包括:移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,使得移动终端不向基站发送业务数据。 本发明的技术方案能够有效保护移动终端的信息安全。(String), US14/391580(String), 1340553600(Integer), US20150067795A1(String), 1425484800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 9(Integer), CN201515419U | US20050267650A1 | US20100279626A1 | US20110065375A1 | US20110241827A1 | US20120052879A1 | US20120299847A1 | US20150082422A1 | US8126431B2(String), \20230420\064677ae5cef47d5809aea2682ba0406.png(String), 18(Integer), 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 1. A control method for a mobile terminal, comprising:receiving, by a control device for the mobile terminal, a first switching instruction which instructs switching the mobile terminal to a security mode; andperforming, by the control device for the mobile terminal, control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station.(String), 1.根据权利要求8所述的移动终端的控制装置,其中第一切换指令携带密码,并且其中,控制模块用于根据预设的关闭密码对第一切换指令携带的密码进行验证,在验证通过后关闭移动终端的上行业务通道。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 2. The control method for the mobile terminal according to claim 1, wherein performing, by the control device for the mobile terminal, control processing on the mobile terminal according to the first switching instruction comprises:disabling, by the control device for the mobile terminal, an uplink service channel of the mobile terminal.(String), 12.根据权利要求10所述的移动终端的控制装置,其中第二切换指令携带密码,并且其中,所述控制模块,用于根据预设的开启密码对所述第二切换指令携带的密码进行验证,在所述第二切换指令携带的密码验证通过后,开启所述移动终端的上行业务通道。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 3. The control method for the mobile terminal according to claim 2, further comprising:after disabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal,prompting, by the control device for the mobile terminal, a user whether to switch the mobile terminal from the security mode to a normal mode when the mobile terminal receives an external signal.(String), 13.移动终端,包括8.根据权利要求7所述的控制装置。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 4. The control method for the mobile terminal according to claim 3, further comprising:after prompting the user whether to switch the mobile terminal from the security mode to the normal mode,receiving, by the control device for the mobile terminal, a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; andenabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode.(String), 14.移动终端,包括9.根据权利要求8所述的控制装置。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 5. The control method for the mobile terminal according to claim 2, wherein the first switching instruction carries a password, andwherein disabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal comprises:verifying, by the control device for the mobile terminal, the password carried by the first switching instruction according to a preset disabling password, and disabling the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification.(String), 15.移动终端,包括10.根据权利要求9所述的控制装置。(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 6. The control method for the mobile terminal according to claim 4, wherein the second switching instruction carries a password, andwherein enabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal comprises:verifying, by the control device for the mobile terminal, the password carried by the second switching instruction according to a preset enabling password, and enabling the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification.(String), 16.移动终端,包括11.根据权利要求10所述的控制装置。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 7. A control device for a mobile terminal, comprising:an input module, configured to receive a first switching instruction which instructs switching the mobile terminal to a security mode; anda control module, configured to perform control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station.(String), 17.移动终端,包括12.根据权利要求11所述的控制装置。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 8. The control device for the mobile terminal according to claim 7, wherein the control module is configured to disable an uplink service channel of the mobile terminal so as to switch the mobile terminal to the security mode.(String), 18.移动终端,包括13.根据权利要求12所述的控制装置。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 9. The control device for the mobile terminal according to claim 8, further comprising:a prompting module, configured to, when the mobile terminal receives an external signal, prompt a user whether to switch the mobile terminal from the security mode to a normal mode.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 10. The control device for the mobile terminal according to claim 9, wherein the input module is further configured to receive a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode, andwherein the control module is further configured to enable an uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 11. The control device for the mobile terminal according to claim 8, wherein the first switching instruction carries a password, andwherein the control module is configured to verify the password carried by the first switching instruction according to a preset disabling password and disable the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification.(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 12. The control device for the mobile terminal according to claim 10, wherein the second switching instruction carries a password, andwherein the control module is configured to verify the password carried by the second switching instruction according to a preset enabling password and enable the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 13. A mobile terminal, comprising the control device according to claim 7.(String), 1(Integer), 12(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 14. A mobile terminal, comprising the control device according to claim 8.(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 15. A mobile terminal, comprising the control device according to claim 9.(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 16. A mobile terminal, comprising the control device according to claim 10.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 17. A mobile terminal, comprising the control device according to claim 11.(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184959(Integer), 18. A mobile terminal, comprising the control device according to claim 12.(String), 1(Integer), 17(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184959(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of communications, and in particular to a control method and a control device for a mobile terminal, and the mobile terminal. BACKGROUND [0002]Along with the increasing popularization of the mobile terminal, the mobile terminal has more and more functions, and thus the mobile terminal has become an essential communication tool for the daily life of a user. [0003]However, with the continuous expansion of a wireless network, the user stores more and more privacy in the mobile terminal, and along with the development of science and technology, there are more and more eavesdropping methods, so that a hacker or a virus may steal information about an individual and a company by controlling the mobile terminal. For example, during a business meeting, if the mobile terminal is carried to a meeting site, although the mobile terminal is set into a silent mode, meeting contents can still be leaked through the mobile terminal, so that the privacy of the individual and secretes of the company are greatly threatened. SUMMARY [0004]A technical problem to be solved by the embodiments of the disclosure is to provide a control method and a control device for a mobile terminal, and the mobile terminal, which can effectively ensure the information security of the mobile terminal. [0005]In order to solve the technical problem above, the embodiments of the disclosure provides the following technical solutions [0006]According to an aspect, a control method for a mobile terminal is provided, including that: [0007]a control device for the mobile terminal receives a first switching instruction which instructs switching the mobile terminal to a security mode; and [0008]the control device for the mobile terminal performs control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0009]Preferably, the step the control device for the mobile terminal performs control processing on the mobile terminal according to the first switching instruction may include that: [0010]the control device for the mobile terminal disables an uplink service channel of the mobile terminal. [0011]Preferably, after the control device for the mobile terminal disables the uplink service channel of the mobile terminal, the method may further include that: [0012]the control device for the mobile terminal prompts, when the mobile terminal receives an external signal, a user whether to switch the mobile terminal from the security mode to a normal mode or not. [0013]Preferably, after the control device prompts the user whether to switch the mobile terminal from the security mode to the normal mode, the method may further include that: [0014]the control device for the mobile terminal receives a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and [0015]the control device for the mobile terminal enables the uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode. [0016]Preferably, the first switching instruction may carry a password, and the step that the control device for the mobile terminal disables the uplink service channel of the mobile terminal may include that: [0017]the control device for the mobile terminal verifies the password carried by the first switching instruction according to a preset disabling password, and disables the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification. [0018]Preferably, the second switching instruction may carry a password, and the step that the control device for the mobile terminal enables the uplink service channel of the mobile terminal may include that: [0019]the control device for the mobile terminal verifies the password carried by the second switching instruction according to a preset enabling password, and enables the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification. [0020]The embodiment of the disclosure also provides a control device for a mobile terminal, including: [0021]an input module, configured to receive a first switching instruction which instructs switching the mobile terminal to a security mode; and [0022]a control module, configured to perform control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0023]Preferably, the control module may be configured to disable an uplink service channel of the mobile terminal so as to switch the mobile terminal to the security mode. [0024]Preferably, the device may further include: [0025]a prompting module, configured to, when the mobile terminal receives an external signal, prompt a user whether to switch the mobile terminal from the security mode to a normal mode or not. [0026]Preferably, the input module may be further configured to receive a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and [0027]the control module may be further configured to enable the uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode. [0028]Preferably, the first switching instruction may carry a password, and [0029]the control module may be configured to verify the password carried by the first switching instruction according to a preset disabling password and disable the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification. [0030]Preferably, the second switching instruction may carry a password, and [0031]the control module may be configured to verify the password carried by the second switching instruction according to a preset enabling password and enable the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification. [0032]The embodiment of the disclosure further provides a mobile terminal, including the above-mentioned control device. [0033]The embodiments of the disclosure have the following beneficial effects that: [0034]in the above solution, under the security mode, the control device for the mobile terminal performs control processing on the mobile terminal to disable the mobile terminal to transmit the service data to the base station and make the mobile terminal only to receive the external signal. The signal transmission operating function of the mobile terminal is disabled, so that the information security of the mobile terminal can be effectively ensured, and the mobile terminal can be prevented from being freely controlled by a hacker or a virus for eavesdropping and stealing the privacy of an individual or secretes of a company. BRIEF DESCRIPTION OF THE DRAWINGS [0035]FIG. 1 is a flowchart of a control method for a mobile terminal according to an embodiment of the disclosure. [0036]FIG. 2 is a structural diagram of a control device for a mobile terminal according to an embodiment of the disclosure. [0037]FIG. 3 is a flowchart of a control method for a mobile terminal according to example 1 of the disclosure. [0038]FIG. 4 is a flowchart of a control method for a mobile terminal according to example 2 of the disclosure. [0039]FIG. 5 is a flowchart of a control method for a mobile terminal according to example 3 of the disclosure. DETAILED DESCRIPTION [0040]In order to make clearer the technical problem to be solved by the embodiments of the disclosure, the technical scheme and the advantages, detailed description will be given below with reference to the drawings and specific embodiments. [0041]For the problem that a hacker or a virus may steal information about an individual and a company by controlling a mobile terminal in the relevant art, the embodiments of the disclosure provide a control method and a control device for the mobile terminal as well as the mobile terminal, which can effectively ensure the information security of the mobile terminal. [0042]FIG. 1 is a flowchart of a control method for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 1, the embodiment includes that: [0043]S101: a control device for the mobile terminal receives a first switching instruction which instructs switching the mobile terminal to a security mode; and [0044]S102: the control device for the mobile terminal performs control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0045]The first switching instruction may be an instruction input by a user of the mobile terminal, or may be an instruction transmitted to the control device for the mobile terminal by external equipment. [0046]The mobile terminal may be disabled to transmit the service data to the base station through many methods: before transmitting the service data to the base station, the mobile terminal is required to perform a series of processing, such as coding and mapping, on the service data, and a certain step can be interrupted to disable the mobile terminal to transmit the service data to the base station. [0047]Preferably, the control device for the mobile terminal may disable the mobile terminal to transmit the service data to the base station by disabling an uplink service channel of the mobile terminal. [0048]Preferably, the control device for the mobile terminal may prompt, when the mobile terminal receives an external signal, the user whether to switch the mobile terminal from the security mode to a normal mode or not. [0049]Preferably, after prompting the user, the control device for the mobile terminal receives a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and the control device for the mobile terminal enables the uplink service channel of the mobile terminal according to the second switching instruction, that is switching the mobile terminal to the normal mode. [0050]Preferably, the first switching instruction may carry a password, and the control device for the mobile terminal verifies the password carried by the first switching instruction according to a preset disabling password and disables the uplink service channel of the mobile terminal after the verification succeeds. [0051]Preferably, the second switching instruction may carry a password, and the control device for the mobile terminal verifies the password carried by the second switching instruction according to a preset enabling password and enables the uplink service channel of the mobile terminal after the verification succeeds. [0052]According to the control method for the mobile terminal in the embodiment of the disclosure, under the security mode, the control device for the mobile terminal performs control processing on the mobile terminal to disable the mobile terminal to transmit the service data to the base station, as a result, the mobile terminal only receives the external signal. Since the signal transmission function of the mobile terminal is disabled, the information security of the mobile terminal can be effectively ensured, and the mobile terminal can be prevented from being freely controlled by the hacker or the virus for eavesdropping and stealing the privacy of the individual and the secretes of the company. [0053]FIG. 2 is a structural diagram of a control device for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 2, the embodiment includes: [0054]an input module 20, configured to receive a first switching instruction which instructs switching the mobile terminal to a security mode; and [0055]a control module 21, configured to perform control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0056]Preferably, the control module 21 is configured to disable an uplink service channel of the mobile terminal so as to switch the mobile terminal to the security mode. [0057]Preferably, the control device further includes: [0058]a prompting module, configured to prompt, when the mobile terminal receives an external signal, a user whether to switch the mobile terminal from the security mode to a normal mode or not. [0059]Preferably, the input module 20 is further configured to receive a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and [0060]the control module 21 is further configured to enable the uplink service channel of the mobile terminal according to the second switching instruction so as to switch the mobile terminal to the normal mode. [0061]Preferably, the first switching instruction carries a password, and [0062]the control module 21 is configured to verify the password carried by the first switching instruction according to a preset disabling password and disable the uplink service channel of the mobile terminal after the verification succeeds. [0063]Preferably, the second switching instruction carries a password, and [0064]the control module 21 is configured to verify the password carried by the second switching instruction according to a preset enabling password and enable the uplink service channel of the mobile terminal after the verification succeeds. [0065]According to the control device for the mobile terminal in the embodiment of the disclosure, under the security mode, the control device for the mobile terminal performs control processing on the mobile terminal to disable the mobile terminal to transmit the service data to the base station, as a result, the mobile terminal only receives the external signal. Since the signal transmission function of the mobile terminal is disabled, the information security of the mobile terminal can be effectively ensured, and the mobile terminal can be prevented from being freely controlled by the hacker or the virus for eavesdropping and stealing the privacy of the individual and the secretes of the company. [0066]The embodiment of the disclosure further provides a mobile terminal, which includes the above-mentioned control device for the mobile terminal. [0067]The control method for the mobile terminal of the disclosure is further described below with reference to specific examples. EXAMPLE 1 [0068]In this example, when the user requires to protect the information security of the mobile terminal, the mobile terminal can be switched to the security mode; and when the user requires to enable the uplink service channel, the mobile terminal is switched to the normal mode. As shown in FIG. 3, the embodiment includes the following steps. [0069]Sa1: the control device in the mobile terminal receives the first switching instruction input by the user, in which the first switching instruction instructs the mobile terminal to be switched to the security mode. Specifically, the control device in the mobile terminal may determine that the user requires to switch the mobile terminal to the security mode according to a key-press operation of the user and switches the mobile terminal to the security mode. [0070]Furthermore, the control device in the mobile terminal may also prompt the user to input a password, verify the password according to a preset disabling password after the user inputs the password, and disable the uplink service channel of the mobile terminal after the password passes verification, and then the mobile terminal is switched to the security mode. If the password input by the user is inconsistent with the preset disabling password, the control device in the mobile terminal does not disable the uplink service channel of the mobile terminal, and the mobile terminal cannot be switched to the security mode. [0071]Sa2: under the security mode, on uplink channels from the mobile terminal to the base station, transmission functions such as voice transmission and data transmission on all service channels, except signalling interaction between the mobile terminal and the base station, are disabled, the mobile terminal is kept in a minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. When the user needs to make a call, reply to a short message or surf the Internet, the control device in the mobile terminal determines that the user needs to use the uplink service channel according to the key-press operation of the user, and prompts the user whether to switch the mobile terminal from the security mode to the normal mode or not. [0072]Sa3: the user inputs the second switching instruction which instructs the mobile terminal to be switched to the normal mode according to the prompting of the control device in the mobile terminal. Specifically, the control device in the mobile terminal determines that the user needs to switch the mobile terminal to the normal mode according to the key-press operation of the user, and switches the mobile terminal to the security mode. [0073]Furthermore, the control device in the mobile terminal may also prompt the user to input the password. After the user inputs the password, the control device in the mobile terminal verifies the password input by the user according to the preset enabling password, enables the uplink service channel of the mobile terminal after the password passes verification, and switches the mobile terminal to the normal mode. If the password input by the user is inconsistent with the preset enabling password, the control device in the mobile terminal does not enable the uplink service channel of the mobile terminal, and the mobile terminal cannot be switched to the normal mode. EXAMPLE 2 [0074]In this example, when the user needs to protect the information security of the mobile terminal, the mobile terminal is switched to the security mode; and when the user needs to answer an incoming call, the mobile terminal is switched to the normal mode. FIG. 4 is a flowchart of receiving an incoming call under the security mode of a mobile terminal, and as shown in FIG. 4, the embodiment includes the following steps. [0075]Sb1: the control device in the mobile terminal controls the mobile terminal to be in the security mode, under which on uplink channels from the mobile terminal to the base station, the function of transmitting voices, data and the like on all service channels, except signalling interaction between the mobile terminal and the base station, is disabled, the mobile terminal is kept in the minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. [0076]Sb2: the mobile terminal receives an incoming call, and the control device in the mobile terminal displays the incoming call to the user, and prompts the user whether to answer the incoming call or not. [0077]Sb3: upon the user selects to answer the incoming call, the control device in the mobile terminal determines whether the user selects to answer the incoming call or not according to an operation of the user. Specifically, the control device in the mobile terminal determines that the user selects to answer the incoming call according to an answer key pressing operation of the user. Thus, the mobile terminal is required to be switched from the security mode to the normal mode for the user to answer the incoming call, the control device in the mobile terminal prompts the user to input the password, compares the password input by the user with the preset enabling password, and enables the uplink service channel of the mobile terminal to switch the mobile terminal to the normal mode if the password input by the user is consistent with the preset enabling password, as a result, the user can answer the incoming call in the normal mode; and if the password input by the user is inconsistent with the preset enabling password, the user cannot answer the incoming call. EXAMPLE 3 [0078]In this example, when the user requires to protect the information security of the mobile terminal, the mobile terminal is switched to the security mode; and when the user needs to reply to a short message, the mobile terminal is switched to the normal mode. FIG. 5 is a flowchart of replying to a received short message under the security mode of a mobile terminal, and as shown in FIG. 5, the embodiment includes the following steps. [0079]Sc1: the control device in the mobile terminal controls the mobile terminal to be in the security mode, under which on uplink channels from the mobile terminal to the base station, the function of transmitting voices, data and the like on all service channels, except signalling interaction between the mobile terminal and the base station, is disabled, the mobile terminal is kept in the minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. [0080]Sc2: the mobile terminal receives the short message, and the user reads the short message. [0081]Sc3: the control device in the mobile terminal determines whether the user selects to reply to the short message or not according to an operation of the user. Specifically, the control device in the mobile terminal determines that the user selects to reply to the short message according to a short message edition key pressing operation of the user. Thus, the mobile terminal is required to be switched from the security mode to the normal mode for the user to reply to the short message. The control device in the mobile terminal prompts the user to input an enabling password, compares the password input by the user with the preset enabling password, and enables the uplink service channel of the mobile terminal to switch the mobile terminal to the normal mode if the password input by the user is consistent with the preset enabling password, and the user can reply to the short message in the normal mode; and if the password input by the user is inconsistent with the preset enabling password, the user cannot reply to the short message. EXAMPLE 4 [0082]In this example, when entering a specific area, the mobile terminal is switched to the security mode; and when the user requires to enable the uplink service channel, the mobile terminal is switched to the normal mode. The embodiment includes the following steps. [0083]Sd1: the control device in the mobile terminal receives the first switching instruction which instructs the mobile terminal to be switched to the security mode. Specifically, when the user enters a specific area such as a meeting room, related equipment in the meeting room transmits the first switching instruction to the control device in the mobile terminal, instructing the mobile terminal to be switched to the security mode. [0084]Sd2: under the security mode, on uplink channels from the mobile terminal to the base station, the function of transmitting voices, data and the like on all service channels, except signalling interaction between the mobile terminal and the base station, is disabled, the mobile terminal is kept in the minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. When the user needs to make a call, reply to a short message or surf the Internet, the control device in the mobile terminal determines that the user needs to use the uplink service channel according to the key-press operation of the user, and prompts the user whether to switch the mobile terminal from the security mode to the normal mode or not. [0085]Sd3: the user inputs the second switching instruction according to the prompting of the control device in the mobile terminal to make the mobile terminal to be switched to the normal mode. Specifically, the control device in the mobile terminal determines that the user needs to switch the mobile terminal to the normal mode according to the key-press operation of the user, and switch the mobile terminal to the security mode. [0086]Furthermore, the control device in the mobile terminal may also prompt the user to input the password. After the user inputs the password, the control device in the mobile terminal verifies the password input by the user according to the preset enabling password, and enables the uplink service channel of the mobile terminal to switch the mobile terminal to the normal mode after the password passes verification. If the password input by the user is inconsistent with the preset enabling password, the control device in the mobile terminal does not enable the uplink service channel of the mobile terminal, the mobile terminal thus cannot be switched to the normal mode. [0087]According to the disclosure, the mobile terminal can be switched from the normal mode to the security mode. Under the security mode, the control device in the mobile terminal disables the uplink service channel of the mobile terminal to make the mobile terminal only to receive the external signal, and the signal transmission function of the mobile terminal is disabled, so that it is able to prevent an axe-grinding person to steal the secretes of the company or the privacy of the individual through the mobile terminal when the user of the mobile terminal is at a meeting or in another important and secrete place, and thus the information security of the mobile terminal can be effectively protected. [0088]Multiple functional parts described in the specification are called modules, so that the independence of implementation modes for the functional parts is specially emphasized. [0089]In the embodiments of the disclosure, the modules may be implemented as software for the convenient execution of various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of a computer instruction, and may for example be structured into an object, a process or a function. However, executable codes of the identified module may not be physically positioned together, but can include different instructions stored at different bits, and these instructions form the module and implement a specified purpose of the module when being logically combined together. [0090]Actually, the executable code module may be a single instruction or multiple instructions, and may even be distributed on different code segments, in different programs and across multiple pieces of memory equipment. Similarly, operating data may be identified in the module, implemented in any proper way and structured in a data structure of any proper type. The operating data may be collected as a single dataset, or may be distributed at different positions (or at different memory equipments), and may at least partially exist on a system or a network as an electronic signal only. [0091]In the case the module may be implemented by means of software, in consideration of the level of a conventional hardware process, for the module which may be implemented by the software, the skilled in the art may construct a hardware circuit to realize a corresponding function of the module without regard to the cost, in which the hardware circuit includes a conventional Very Large Scale Integrated (VLSI) circuit or a gate array and a conventional semiconductor such as a logic chip and a transistor or other discrete components. The module may also be implemented by means of programmable hardware equipment such as a field programmable gate array, a programmable array logic and programmable logic equipment. [0092]In each method embodiment of the disclosure, the sequence number of each step cannot be intended to limit the sequence of the steps, and for the skilled in the art, changes, without paying creative work, in the sequence of the steps also fall within the scope of protection of the disclosure. [0093]The above are only preferred embodiments of the disclosure, it should be noted that the skilled in the art can make various improvements and elaborations without departing from the disclosure, and these improvements and elaborations shall also fall within the scope of protection of the disclosure.(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的控制方法、控制装置及移动终端。 背景 [0002] 随着移动终端的日益普及,移动终端的功能越来越多,移动终端已经成为用户日常生活中必不可少的通讯工具。 [0003] 然而,随着无线网络的不断扩大,用户在移动终端中存储的隐私越来越多,随着科技的发展,窃听手段也越来越多,黑客或病毒可能窃取 通过控制移动终端获取有关个人和公司的信息。 例如,在商务会议中,如果携带移动终端到会场,虽然移动终端设置为静音模式,但仍然可以通过移动终端泄露会议内容,使个人隐私和泄密 公司受到极大的威胁。 概括 [0004] 本发明实施例所要解决的技术问题是提供一种移动终端的控制方法、控制装置及移动终端,能够有效保障移动终端的信息安全。 [0005] 为了解决上述技术问题,本发明实施例提供以下技术方案 [0006] 根据一个方面,提供了一种移动终端的控制方法,包括: [0007] 移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 和 [0008] 移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0009] 优选地,所述移动终端的控制装置根据第一切换指令对移动终端进行控制处理的步骤包括: [0010] 移动终端的控制装置关闭移动终端的上行业务信道。 [0011] 优选地,所述移动终端的控制装置关闭所述移动终端的上行业务信道后,所述方法还包括: [0012] 移动终端控制装置在移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到正常模式。 [0013] 优选地,所述控制装置提示用户是否将移动终端从安全模式切换到正常模式后,所述方法还包括: [0014] 移动终端控制装置接收用户输入的指示将移动终端切换到正常模式的第二切换指令; 和 [0015] 移动终端的控制装置根据第二切换指令开启移动终端的上行业务信道,以将移动终端切换到正常模式。 [0016] 优选地,第一切换指令可以携带密码,移动终端的控制装置关闭移动终端的上行业务信道包括: [0017] 移动终端的控制装置根据预设的关闭密码对第一切换指令携带的密码进行验证,验证通过后关闭移动终端的上行业务通道。 [0018] 优选地,第二切换指令可以携带密码,移动终端的控制装置开启移动终端的上行业务信道的步骤可以包括: [0019]移动终端的控制装置根据预设的开启密码对第二切换指令携带的密码进行验证,验证通过后开启移动终端的上行业务通道。 [0020] 本发明实施例还提供了一种移动终端的控制装置,包括: [0021] 输入模块,用于接收指示将移动终端切换到安全模式的第一切换指令; 和 [0022] 控制模块,用于根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0023] 优选地,控制模块可以用于关闭移动终端的上行业务通道,以将移动终端切换到安全模式。 [0024] 优选地,该装置还可以包括: [0025] 提示模块,用于当移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到普通模式。 [0026] 优选地,所述输入模块还用于接收用户输入的第二切换指令,所述第二切换指令指示将移动终端切换至正常模式。 和 [0027] 控制模块还可以用于根据第二切换指令开启移动终端的上行业务信道,以将移动终端切换到正常模式。 [0028] 优选地,第一切换指令可以携带密码,以及 [0029] 控制模块,可以用于根据预设的关闭密码验证第一切换指令携带的密码,在验证通过后关闭移动终端的上行业务通道。 [0030] 优选地,第二切换指令可以携带密码,以及 [0031] 控制模块,可以用于根据预设的开启密码对第二切换指令携带的密码进行验证,在验证通过后,开启移动终端的上行业务通道。 [0032] 本发明实施例还提供了一种移动终端,包括上述控制装置。 [0033] 本发明实施例具有以下有益效果: [0034] 上述方案中,在安全模式下,移动终端的控制装置对移动终端进行控制处理,禁止移动终端向基站发送业务数据,使移动终端只能接收外部信号。 关闭移动终端的信号传输操作功能,可以有效保障移动终端的信息安全,防止移动终端被黑客或病毒随意控制,窃听窃取用户隐私。 个人或公司的秘密。 附图的简要说明 [0035] 图1是根据本发明实施例的移动终端的控制方法的流程图。 [0036] 图2是根据本发明实施例的移动终端的控制装置的结构图。 [0037] 图3是根据本发明实施例一的移动终端的控制方法的流程图。 [0038] 图4是根据本发明实施例二的移动终端的控制方法的流程图。 [0039] 图5是根据本发明实施例三的移动终端的控制方法的流程图。 详细说明 [0040]为使本发明实施例所要解决的技术问题、技术方案及优点更加清楚,下面将结合附图及具体实施例进行详细说明。 [0041] 针对相关技术中黑客或病毒通过控制移动终端窃取个人和公司信息的问题,本发明实施例提供了一种移动终端的控制方法、控制装置及移动终端。 终端,可有效保障移动终端的信息安全。 [0042] 图1为本发明实施例提供的一种移动终端的控制方法流程图,如图1所示,该实施例包括: [0043] 小号 101 :移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 和 [0044] 小号 102 :移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0045] 第一切换指令可以是移动终端的用户输入的指令,也可以是外部设备向移动终端的控制装置发送的指令。 [0046] 可以通过多种方式使移动终端无法向基站发送业务数据:在向基站发送业务数据之前,需要移动终端对业务进行编码、映射等一系列处理。 数据,可以中断某个步骤,使移动终端不能向基站发送业务数据。 [0047] 优选地,移动终端的控制装置可以通过关闭移动终端的上行业务信道来关闭移动终端向基站发送业务数据。 [0048] 优选地,移动终端的控制装置可以在移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到正常模式。 [0049] 优选地,在提示用户后,移动终端的控制装置接收用户输入的第二切换指令,该第二切换指令指示将移动终端切换到正常模式; 移动终端的控制装置根据第二切换指令开启移动终端的上行业务信道,即将移动终端切换到正常模式。 [0050] 优选地,第一切换指令可以携带密码,移动终端的控制装置根据预设的关闭密码对第一切换指令携带的密码进行验证,验证成功后关闭移动终端的上行业务通道。 [0051] 优选地,第二切换指令可以携带密码,移动终端的控制装置根据预设的开启密码对第二切换指令携带的密码进行验证,验证成功后开启移动终端的上行业务信道。 [0052] 根据本发明实施例的移动终端的控制方法,在安全模式下,移动终端的控制装置对移动终端进行控制处理,禁止移动终端向基站发送业务数据, 结果,移动终端仅接收外部信号。 由于关闭了移动终端的信号传输功能,可以有效保障移动终端的信息安全,防止移动终端被黑客或病毒随意控制,窃听、窃取个人隐私 以及公司的秘密。 [0053] 图2为本发明实施例提供的一种移动终端的控制装置的结构图,如图2所示,该实施例包括: [0054]输入模块 20 , 用于接收指示将移动终端切换到安全模式的第一切换指令; 和 [0055] 一个控制模块 21 ,用于根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0056] 优选地,控制模块 21 用于关闭移动终端的上行业务通道,使移动终端切换到安全模式。 [0057] 优选地,所述控制装置还包括: [0058] 提示模块,用于当移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到普通模式。 [0059] 优选地,输入模块 20 还用于接收用户输入的指示将移动终端切换至正常模式的第二切换指令; 和 [0060] 控制模块 21 还用于根据第二切换指令开启移动终端的上行业务信道,以将移动终端切换到正常模式。 [0061] 优选地,第一切换指令携带密码,以及 [0062] 控制模块 21 用于根据预设的关闭密码验证第一切换指令携带的密码,验证成功后关闭移动终端的上行业务通道。 [0063] 优选地,第二切换指令携带密码,以及 [0064] 控制模块 21 用于根据预设的开启密码对第二切换指令携带的密码进行验证,验证成功后开启移动终端的上行业务通道。 [0065] 根据本发明实施例的移动终端控制装置,在安全模式下,移动终端控制装置对移动终端进行控制处理,以禁止移动终端向基站发送业务数据, 结果,移动终端仅接收外部信号。 由于关闭了移动终端的信号传输功能,可以有效保障移动终端的信息安全,防止移动终端被黑客或病毒随意控制,窃听、窃取个人隐私 以及公司的秘密。 [0066] 本发明实施例还提供了一种移动终端,包括上述的移动终端的控制装置。 [0067] 下面结合具体例子对本发明移动终端的控制方法作进一步说明。 示例 1 [0068] 本例中,当用户需要保护移动终端的信息安全时,可以将移动终端切换到安全模式; 当用户要求开启上行业务信道时,移动终端切换到正常模式。 如图3所示,该实施例包括以下步骤。 [0069] 萨 1 :移动终端中的控制装置接收用户输入的第一切换指令,第一切换指令指示移动终端切换到安全模式。 具体地,移动终端中的控制装置可以根据用户的按键操作确定用户要求将移动终端切换到安全模式,将移动终端切换到安全模式。 [0070]进一步地,移动终端中的控制装置还可以提示用户输入密码,用户输入密码后根据预设的关闭密码验证密码,验证通过后关闭移动终端的上行业务通道。 ,然后移动终端切换到安全模式。 如果用户输入的密码与预设的关闭密码不一致,则移动终端中的控制装置不关闭移动终端的上行业务通道,移动终端不能切换到安全模式。 [0071] 萨 2 :在安全模式下,在移动终端到基站的上行信道上,除移动终端与基站之间的信令交互外,所有业务信道上的语音传输和数据传输等传输功能均被关闭,移动终端 保持最小入网状态,只保留外部信号接收功能,信号发送功能关闭。 当用户需要打电话、回复短信或上网时,移动终端中的控制装置根据用户的按键操作确定用户需要使用上行业务信道,并提示 用户是否将移动终端从安全模式切换到正常模式。 [0072] 萨 3 :用户根据移动终端中的控制装置的提示,输入第二切换指令,指示移动终端切换到正常模式。 具体地,移动终端中的控制装置根据用户的按键操作确定用户需要将移动终端切换到普通模式,将移动终端切换到安全模式。 [0073] 进一步地,移动终端中的控制装置还可以提示用户输入密码。 用户输入密码后,移动终端中的控制装置根据预设的开启密码对用户输入的密码进行验证,密码验证通过后开启移动终端的上行业务通道,将移动终端切换到 正常模式。 如果用户输入的密码与预设的开启密码不一致,则移动终端中的控制装置不开启移动终端的上行业务通道,移动终端无法切换到正常模式。 例 2 [0074] 本例中,当用户需要保护移动终端的信息安全时,将移动终端切换到安全模式; 当用户需要接听来电时,将移动终端切换到正常模式。 图4为移动终端安全模式下接听来电的流程图,如图4所示,本实施例包括以下步骤。 [0075] 锑 1 :移动终端中的控制设备控制移动终端处于安全模式,在该模式下,在移动终端到基站的上行信道上,除了信令之外的所有业务信道上传输语音、数据等的功能 关闭移动终端与基站的交互,移动终端保持最小入网状态,只保留对外信号接收功能,关闭信号发送功能。 [0076] 锑 2 :移动终端收到来电,移动终端中的控制装置将来电显示给用户,并提示用户是否接听来电。 [0077] 锑 3:当用户选择接听来电时,移动终端中的控制装置根据用户的操作判断用户是否选择接听来电。 具体地,移动终端中的控制装置根据用户的接听按键操作确定用户选择接听来电。 因此,用户来电时需要将移动终端从安全模式切换到普通模式,移动终端中的控制装置提示用户输入密码,将用户输入的密码与用户输入的密码进行比对。 预设的开启密码,如果用户输入的密码与预设的开启密码一致,则开启移动终端的上行业务通道,将移动终端切换到正常模式,从而用户可以接听来电 在正常模式下; 如果用户输入的密码与预设的启用密码不一致,则用户无法接听来电。 例 3 [0078] 本例中,当用户需要保护移动终端的信息安全时,将移动终端切换到安全模式; 当用户需要回复短信时,将移动终端切换到正常模式。 图5为移动终端在安全模式下回复收到的短信的流程图,如图5所示,本实施例包括以下步骤。 [0079] 科学 1 :移动终端中的控制设备控制移动终端处于安全模式,在该模式下,在移动终端到基站的上行信道上,除了信令之外的所有业务信道上传输语音、数据等的功能 关闭移动终端与基站的交互,移动终端保持最小入网状态,只保留对外信号接收功能,关闭信号发送功能。 [0080] 科学 2 :移动终端收到短信,用户阅读短信。 [0081] 科学 3 :移动终端中的控制装置根据用户的操作判断用户是否选择回复短信。 具体地,移动终端中的控制装置根据用户的短信编辑按键操作确定用户选择回复短信。 因此,用户回复短信时需要将移动终端从安全模式切换到正常模式。 移动终端中的控制装置提示用户输入开启密码,将用户输入的密码与预设的开启密码进行比对,开启移动终端的上行业务通道,将移动终端切换到正常模式。 用户输入的密码与预设的启用密码一致,用户可以在正常模式下回复短信; 如果用户输入的密码与预设的开启密码不一致,则用户无法回复短信。 例 4 [0082] 本例中,当进入特定区域时,移动终端切换到安全模式; 当用户要求开启上行业务信道时,移动终端切换到正常模式。 该实施例包括以下步骤。 [0083] 标准差 1 :移动终端中的控制装置接收到第一切换指令,指示移动终端切换到安全模式。 具体地,当用户进入会议室等特定区域时,会议室中的相关设备向移动终端中的控制装置发送第一切换指令,指示移动终端切换到安全模式。 [0084] 标准差 2:在安全模式下,在移动终端到基站的上行信道上,除移动终端与基站之间的信令交互外,所有业务信道上传输语音、数据等功能均被关闭,移动终端 终端保持最小入网状态,只保留外部信号接收功能,信号发送功能关闭。 当用户需要打电话、回复短信或上网时,移动终端中的控制装置根据用户的按键操作确定用户需要使用上行业务信道,并提示 用户是否将移动终端从安全模式切换到正常模式。 [0085] 标准差 3 :用户根据移动终端中控制装置的提示输入第二切换指令,使移动终端切换到正常模式。 具体地,移动终端中的控制装置根据用户的按键操作确定用户需要将移动终端切换到普通模式,将移动终端切换到安全模式。 [0086] 进一步地,移动终端中的控制装置还可以提示用户输入密码。 用户输入密码后,移动终端中的控制装置根据预设的开启密码对用户输入的密码进行验证,密码后开启移动终端的上行业务通道,将移动终端切换到正常模式。 通过验证。 如果用户输入的密码与预设的开启密码不一致,则移动终端中的控制装置不开启移动终端的上行业务通道,从而使移动终端无法切换到正常模式。 [0087] 根据本发明,移动终端可以从正常模式切换到安全模式。 在安全模式下,移动终端中的控制装置关闭移动终端的上行业务通道,使移动终端只能接收外部信号,关闭移动终端的信号传输功能,使其能够 当移动终端用户在开会或其他重要隐秘场所时,防止斧磨人通过移动终端窃取公司机密或个人隐私,从而保障公司的信息安全。 移动终端可以得到有效的保护。 [0088] 将规范中描述的多个功能部分称为模块,特别强调功能部分实现方式的独立性。 [0089] 在本发明实施例中,模块可以实现为软件形式,以方便各类处理器的执行。 例如,识别的可执行代码模块可以包括计算机指令的一个或多个物理或逻辑块,并且可以例如被构造成对象、过程或函数。 但是,识别出的模块的可执行代码在物理上不一定是放在一起的,而是可以包括存储在不同位的不同指令,这些指令在逻辑上组合在一起时形成模块并实现模块的特定目的。 [0090] 实际上,可执行代码模块可以是单条指令,也可以是多条指令,甚至可以分布在不同的代码段上,分布在不同的程序中,分布在多个存储设备上。 类似地,操作数据可以在模块中被识别,以任何适当的方式实现并且被构造成任何适当类型的数据结构。 运行数据可以作为单个数据集收集,也可以分布在不同的位置(或不同的存储设备),并且可以至少部分地仅作为电子信号存在于系统或网络上。 [0091]在该模块可以通过软件实现的情况下,考虑到传统硬件工艺的水平,对于可以通过软件实现的模块,本领域技术人员可以构造硬件电路来实现相应的功能 模块的设计不考虑成本,其中硬件电路包括常规的超大规模集成电路(VLSI)电路或门阵列,以及常规的半导体,例如逻辑芯片和晶体管或其他分立元件。 该模块还可以通过现场可编程门阵列、可编程阵列逻辑、可编程逻辑设备等可编程硬件设备实现。 [0092] 在本发明各方法实施例中,各步骤的序号不能用来限定步骤的先后顺序,对于本领域的技术人员而言,在没有做出创造性劳动的情况下,对步骤顺序的改动也属于本发明的范围。 公开的保护范围。 [0093] 以上所述仅为本发明的优选实施例而已,应当知晓,本领域的技术人员在不脱离本发明的前提下,还可以做出各种改进和阐述,这些改进和阐述也应属于本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103379484A(String), CN103379484B(String), EP2840822A1(String), EP2840822A4(String), EP2840822B1(String), MX2014012656A(String), MX337095B(String), US20150067795A1(String), WO2013155790A1(String), WO2013155790A9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103379484A(String), CN103379484B(String), EP2840822A1(String), EP2840822A4(String), EP2840822B1(String), MX2014012656A(String), MX337095B(String), US20150067795A1(String), WO2013155790A1(String), WO2013155790A9(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20150067795A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103379484A(String), CN103379484B(String), EP2840822A1(String), EP2840822A4(String), EP2840822B1(String), MX2014012656A(String), MX337095B(String), US20150067795A1(String), WO2013155790A1(String), WO2013155790A9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), CN103379484A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), CN103379484B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), EP2840822A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), EP2840822A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), EP2840822B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), MX2014012656A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), MX337095B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), US20150067795A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), WO2013155790A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), WO2013155790A9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20150067795A1(String), US20150067795A1(String), 1425484800(Integer), 270642(Integer), 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LIU, JIANTAO(String), 中兴通讯股份有限公司(String), LIU JIANTAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184959(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184959(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIU, JIANTAO(String), LIU JIANTAO(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184959(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75910(Integer), 2(Integer), 184959(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75910(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9078133B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method, system and mobile terminal for configuring and applying locking strategy of mobile terminal(String), 移动终端锁定策略的配置和应用方法、系统及移动终端(String), US9078133B2(String), The disclosure provides a method for configuring a locking strategy of a mobile terminal, comprising: setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal and transmitting the relevant information to the mobile terminal, when the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal; or, inputting, at the mobile terminal, relevant information of a locking strategy which needs to be executed, and storing the inputted relevant information of the locking strategy which needs to be executed. The disclosure further provides a method for applying a locking strategy of a mobile terminal as well as a system and a terminal mobile for configuring a locking strategy of a mobile terminal. According to the technical solutions of the disclosure, the locking strategy of the mobile terminal can be conveniently and flexibly configured.(String), 本发明提供一种移动终端锁定策略的配置方法,包括:在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并将该相关信息发送给移动终端。 ,当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息; 或者,在移动终端输入需要执行的锁定策略的相关信息,并存储输入的需要执行的锁定策略的相关信息。 本发明还提供了一种移动终端锁定策略的应用方法、移动终端锁定策略配置系统和终端手机。 根据本发明的技术方案,可以方便灵活地配置移动终端的锁定策略。(String), US13/880796(String), 1297267200(Integer), US9078133B2(String), 1436198400(Integer), 1436198400(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 11(Integer), CN101163309A | CN1655643A | CN1845622A | KR1020010065039A | KR1020060100086A | US20070050622A1 | US20090203356A1 | US20100255813A1 | US20120094636A1(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184960(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\aaed73da7b93404383066a6e08b0bbb3.png(String), 184960(Integer), aaed73da7b93404383066a6e08b0bbb3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method, system and mobile terminal for configuring and applying locking strategy of mobile terminal(String), 移动终端锁定策略的配置和应用方法、系统及移动终端(String), US9078133B2(String), The disclosure provides a method for configuring a locking strategy of a mobile terminal, comprising: setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal and transmitting the relevant information to the mobile terminal, when the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal; or, inputting, at the mobile terminal, relevant information of a locking strategy which needs to be executed, and storing the inputted relevant information of the locking strategy which needs to be executed. The disclosure further provides a method for applying a locking strategy of a mobile terminal as well as a system and a terminal mobile for configuring a locking strategy of a mobile terminal. According to the technical solutions of the disclosure, the locking strategy of the mobile terminal can be conveniently and flexibly configured.(String), 本发明提供一种移动终端锁定策略的配置方法,包括:在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并将该相关信息发送给移动终端。 ,当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息; 或者,在移动终端输入需要执行的锁定策略的相关信息,并存储输入的需要执行的锁定策略的相关信息。 本发明还提供了一种移动终端锁定策略的应用方法、移动终端锁定策略配置系统和终端手机。 根据本发明的技术方案,可以方便灵活地配置移动终端的锁定策略。(String), US13/880796(String), 1297267200(Integer), US9078133B2(String), 1436198400(Integer), 1436198400(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 11(Integer), CN101163309A | CN1655643A | CN1845622A | KR1020010065039A | KR1020060100086A | US20070050622A1 | US20090203356A1 | US20100255813A1 | US20120094636A1(String), \20230420\aaed73da7b93404383066a6e08b0bbb3.png(String), 11(Integer), 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 1. A method for configuring a locking strategy of a mobile terminal, comprising:setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal;generating an Attention (AT) command according to the relevant information of the locking strategy which needs to be executed by the mobile terminal;transmitting the AT command to the mobile terminal, wherein the AT command comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal; andwhen the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal.(String), 1.根据权利要求2所述的方法,其中存储需要由移动终端执行的锁定策略的相关信息包括:移动终端解析AT指令获取移动终端的锁定策略的相关信息,将相关信息写入固定区域中。移动终端的FLASH并将存储结果发送给锁定策略设置终端;锁定策略设置终端根据存储结果提示锁定策略是否更新成功。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 2. The method according to claim 1, further comprising: when the mobile terminal determines that the mobile terminal is currently locked, prompting to reconfigure a locking strategy via the locking strategy setting terminal.(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 3. The method according to claim 1, wherein storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal parsing the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writing the relevant information in a fixed region of a FLASH of the mobile terminal and transmitting a storage result to the locking strategy setting terminal; the locking strategy setting terminal prompting whether or not the locking strategy is updated successfully according to the storage result.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 4. A method for configuring a locking strategy of a mobile terminal, comprising:inputting, at a mobile terminal, relevant information of a locking strategy which needs to be executed; anda command processing program installed in the mobile terminal in advance parsing the instruction that is received and writing the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal;the FLASH transmitting a storage result to the command processing program of the mobile terminal;the command processing program prompting whether or not the locking strategy is updated successfully according to the storage result.(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 5. The method according to claim 4, wherein inputting, at the mobile terminal, the relevant information the locking strategy which needs to be executed comprises:inputting, in a command receiving program installed in the mobile terminal in advance, the relevant information of the locking strategy which needs to be executed by the mobile terminal;the command receiving program generating an instruction according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmitting the instruction to the command processing program installed in the mobile terminal in advance, wherein the instruction comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 6. A method for applying a locking strategy of a mobile terminal, comprising:obtaining relevant information of a locking strategy which needs to be executed by a mobile terminal, when determining that an ID of a scheme in the relevant information indicates that the locking strategy has been configured, locking the mobile terminal according to the locking strategy corresponding to the relevant information;wherein obtaining the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: during a power-on process of the mobile terminal, a power-on module of the mobile terminal reading the relevant information of the locking strategy which needs to be executed by the mobile terminal, wherein the relevant information of the locking strategy which needs to be executed by the mobile terminal is stored in a fixed region of a FLASH of the mobile terminal;locking the mobile terminal according to the locking strategy corresponding to the relevant information comprises: the power-on module of the mobile terminal finding, in the mobile terminal, the locking strategy corresponding to the relevant information according to the relevant information that is obtained and executing the locking strategy to lock the mobile terminal.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 7. The method according to claim 6, further comprising:when determining that the ID of the scheme in the relevant information indicates that the locking strategy has not been configured, performing a normal power-on process.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 8. A system for configuring a locking strategy of a mobile terminal, wherein the system comprises: a locking strategy setting terminal and a mobile terminal, whereinthe locking strategy setting terminal is configured to set relevant information of a locking strategy which needs to be executed by the mobile terminal, generate an Attention (AT) command according to the relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmit the AT command to the mobile terminal, wherein the AT command comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal;the mobile terminal is configured to, when the mobile terminal determines that the mobile terminal is currently unlocked, store the relevant information of the locking strategy which needs to be executed by the mobile terminal.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 9. The system according to claim 8, whereinthe locking strategy setting terminal is further configured to, when the mobile terminal determines that the mobile terminal is currently locked, prompt to reconfigure a locking strategy via the locking strategy setting terminal.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 10. A mobile terminal for implementing configuration of a locking strategy of a mobile terminal, wherein the mobile terminal comprises: a command receiving program module and a command processing program module, whereinthe command receiving program module is configured for input of relevant information of a locking strategy which needs to be executed;the command processing program module is configured to parse the instruction that is received and writing the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal, receive a storage result from the FLASH, and prompt whether or not the locking strategy is updated successfully according to the storage result.(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184960(Integer), 11. The method according to claim 2, wherein storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal parsing the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writing the relevant information in a fixed region of a FLASH of the mobile terminal and transmitting a storage result to the locking strategy setting terminal; the locking strategy setting terminal prompting whether or not the locking strategy is updated successfully according to the storage result.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184960(Integer), TECHNICAL FIELD [0001]The disclosure relates to a mobile terminal locking technology, and more particularly, to a method, a system and a mobile terminal for configuring and applying a locking strategy of a mobile terminal. BACKGROUND [0002]Currently, more and more mobile terminals are being applied broadly and mobile terminal products can be customized by mobile communication operators according to their requirements. A mobile communication operator may require locking a network, a card or a mobile terminal etc. when customizing a mobile terminal product. Locking the mobile terminal is a special requirement for the mobile terminal and the customized mobile terminal can only use a specific mobile network, or a specific Subscriber Identity Module (SIM) card/Universal Subscriber Identity Module (USIM) card. Locking the card is a special requirement for the card, after the card is locked, it is required that the card can be only used on a certain mobile terminal and cannot be used on other mobile terminals. Locking a network, a card and a mobile terminal can effectively solve problems of secret change of a network by a user, unauthorized distribution of goods and loss of customers etc. [0003]In related technologies, in order to lock a network or a card for the mobile terminal and lock the mobile terminal, a locking strategy is usually written in a mobile terminal when the mobile terminal is researched and developed. Therefore, the locking strategy is fixed and cannot be modified even by a mobile communication operator. With the development of mobile terminal technologies and continuous growth of services of mobile communication operators, the number of users is growing, along with increasing demands of the mobile communication operators. How to increase research and development efficiency, production efficiency and the configuration flexibility for customers to the greatest extent is a problem to be solved. SUMMARY [0004]In view of the above, the disclosure provides a method, a system and a mobile terminal for configuring and applying a locking strategy of a mobile terminal, so that the locking strategy of the mobile terminal can be conveniently and flexibly configured. [0005]The disclosure provides the following technical solution. [0006]The disclosure provides a method for configuring a locking strategy of a mobile terminal, comprising: [0007]setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal and transmitting the relevant information to the mobile terminal; and [0008]when the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0009]In the method above, the method further comprises: when the mobile terminal determines that the mobile terminal is currently locked, prompting to operate over again via the locking strategy setting terminal. [0010]In the method above, setting, at the locking strategy setting terminal, the relevant information of the locking strategy which needs to be executed by the mobile terminal and transmitting the relevant information to the mobile terminal comprises: [0011]inputting, at the locking strategy setting terminal, the relevant information of the locking strategy which needs to be executed by the mobile terminal, generating an Attention (AT) command according to the relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmitting the AT command to the mobile terminal, wherein the AT command comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0012]In the method above, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal parsing the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writing the relevant information in a fixed region of a FLASH of the mobile terminal and transmitting a storage result to the locking strategy setting terminal; the locking strategy setting terminal prompting whether or not the locking strategy is updated successfully according to the storage result. [0013]The disclosure also provides a method for configuring a locking strategy of a mobile terminal, comprising: [0014]inputting, at a mobile terminal, relevant information of a locking strategy which needs to be executed; and [0015]storing the inputted relevant information of the locking strategy which needs to be executed. [0016]In the method above, inputting, at the mobile terminal, the relevant information the locking strategy which needs to be executed comprises: inputting, in a command receiving program installed in the mobile terminal in advance, the relevant information of the locking strategy which needs to be executed by the mobile terminal; the command receiving program generating an instruction according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmitting the instruction to a command processing program installed in the mobile terminal in advance, wherein the instruction comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0017]In the method above, storing the inputted relevant information of the locking strategy which needs to be executed comprises: the command processing program of the mobile terminal parsing the instruction that is received and writing the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal; the FLASH transmitting a storage result to the command processing program of the mobile terminal; the command processing program prompting whether or not the locking strategy is updated successfully according to the storage result. [0018]The disclosure also provides a method for applying a locking strategy of a mobile terminal, comprising: [0019]obtaining relevant information of a locking strategy which needs to be executed by a mobile terminal, when determining that an ID of a scheme in the relevant information indicates that the locking strategy has been configured, locking the mobile terminal according to the locking strategy corresponding to the relevant information. [0020]In the method above, the method further comprises: when determining that the ID of the scheme in the relevant information indicates that the locking strategy has not been configured, performing a normal power-on process. [0021]In the method above, obtaining the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: during a power-on process of the mobile terminal, a power-on module of the mobile terminal reading the relevant information of the locking strategy which needs to be executed by the mobile terminal, wherein the relevant information of the locking strategy which needs to be executed by the mobile terminal is stored in a fixed region of a FLASH of the mobile terminal; [0022]locking the mobile terminal according to the locking strategy corresponding to the relevant information comprises: the power-on module of the mobile terminal finding, in the mobile terminal, the locking strategy corresponding to the relevant information according to the relevant information that is obtained and executing the locking strategy to lock the mobile terminal. [0023]The disclosure also provides a system for configuring a locking strategy of a mobile terminal, comprising: a locking strategy setting terminal and a terminal, wherein the locking strategy setting terminal is configured to set relevant information of a locking strategy which needs to be executed by the mobile terminal and transmit the relevant information to the mobile terminal; [0024]the mobile terminal is configured to, when the mobile terminal determines that the mobile terminal is currently unlocked, store the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0025]In the system above, [0026]the locking strategy setting terminal is further configured to, when the mobile terminal determines that the mobile terminal is currently locked, prompt to operate over again via the locking strategy setting terminal. [0027]The disclosure also provides a mobile terminal for implementing configuration of a locking strategy of a mobile terminal, comprising: a command receiving program module and a command processing program module, wherein [0028]the command receiving program module is configured for input of relevant information of a locking strategy which needs to be executed; [0029]the command processing program module is configured to store, in a memory, the inputted relevant information of the locking strategy which needs to be executed. [0030]The method, system and mobile terminal for configuring and applying a locking strategy of a mobile terminal provided by the disclosure is able to set, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by the mobile terminal, transmit the relevant information to the mobile terminal, and store the relevant information of the locking strategy which needs to be executed by the mobile terminal when the mobile terminal determines that the mobile terminal is currently unlocked. By doing so, the locking strategy of the mobile terminal can be configured in batches without power-on of the mobile terminal. It is safe, simple and convenient during production of the mobile terminal and the mobile terminal can be upgraded easily, thus greatly improving the production efficiency. [0031]The disclosure can also input, at the mobile terminal, the relevant information of the locking strategy which needs to be executed and store the relevant information of the locking strategy which needs to be executed. A mobile communication operator can operate the mobile terminal directly and switch to required locking strategy at any time. [0032]To sum up, the locking strategy of the mobile terminal can be configured flexibly so that the mobile communication operator is able to manage sales and maintenance of the mobile terminal flexibly without modifying the locking strategy by the manufacturer of the mobile terminal, thus effectively lowering research, development and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS [0033]FIG. 1 is a flowchart illustrating a first method for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; [0034]FIG. 2 is a schematic diagram illustrating a graphical user interface of a command transmission program in accordance with an embodiment of the disclosure; [0035]FIG. 3 is a flowchart illustrating a second method for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; [0036]FIG. 4 is a flowchart illustrating a method for realizing application of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; [0037]FIG. 5 is a structural diagram illustrating a system for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; and [0038]FIG. 6 is a structural diagram illustrating a mobile terminal for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS [0039]When a mobile communication operator needs to configure or update a locking strategy of a mobile terminal, two methods for configuring a locking strategy of a mobile terminal in accordance with embodiment of the disclosure can be adopted. The basic principle of the embodiments of the disclosure is that: relevant information of a locking strategy which needs to be executed by a mobile terminal is set at a locking strategy setting terminal and transmitted to the mobile terminal, when the mobile terminal determines that the mobile terminal is currently unlocked, the relevant information of the locking strategy which needs to be executed by the mobile terminal is stored; or, the relevant information of the locking strategy which needs to be executed is inputted at the mobile terminal, and the inputted relevant information of the locking strategy which needs to be executed is stored. [0040]The disclosure is further described below in details according to the accompanying drawings and the embodiments. [0041]A method for configuring a locking strategy of a mobile terminal provided by an embodiment of the disclosure is as shown in FIG. 1 and comprises the following steps. [0042]Step 101: Relevant information of a locking strategy which needs to be executed by a mobile terminal is set at a locking strategy setting terminal and transmitted to the mobile terminal. [0043]More specifically, a command transmission program of the mobile terminal is installed at the locking strategy setting terminal in advance and a graphical user interface of a command transmission program is entered after the installation is completed, wherein the locking strategy setting terminal may be a computer, e.g. a Personal Computer (PC). FIG. 2 is a schematic diagram illustrating a graphical user interface of a command transmission program in accordance with the embodiment of the disclosure. As shown in FIG. 2, the relevant information, i.e. a province and a scheme of the mobile terminal, of the locking strategy which needs to be executed by the mobile terminal is inputted in the graphical user interface of the command transmission program. The province may be expressed by a 2-byte ID which corresponds to a province ID in an Integrate Circuit Card Identity (ICCID) of a SIM/USIM card of the mobile terminal. The scheme is the locking strategy which needs to be executed by the mobile terminal and expressed by a 2-byte ID. Different IDs represent different schemes, therefore the relevant information which needs to be executed by the mobile terminal is actually a 4-byte code. The command transmission program of the locking strategy setting terminal generates an AT command comprising the relevant information according to the relevant information of the locking strategy which needs to be executed by the mobile terminal and transmits the AT command to the mobile terminal via a communication link between the locking strategy setting terminal and the mobile terminal, wherein the communication link may be a physical link such as a Universal Serial Bus (USB) and a Bluetooth. If the USB is applied as the communication link, the mobile terminal does not need to be powered on when the locking strategy of the mobile terminal is configured, and the AT command can be delivered to the mobile terminal by the locking strategy setting terminal. [0044]Step 102: The mobile terminal determines whether or not the mobile terminal is locked currently, if the mobile terminal is unlocked currently, Step 103 is executed, and if the mobile terminal is locked currently, Step 104 is executed. [0045]More specifically, the mobile terminal is in an idle state which may be a power-off state or a state indicating that the mobile terminal is being powered on. After receiving the AT command transmitted by the locking strategy setting terminal, a command processing program of the mobile terminal reads a flag bit of a fixed region of a FLASH in the mobile terminal, determines that the mobile terminal is a mobile terminal with a card lock and a mobile terminal lock according to the flag bit and triggers a card lock and mobile terminal lock verification program of the mobile terminal. The network lock and mobile terminal lock verification program determines whether or not the fixed region of the FLASH in the mobile terminal is null, if so, it represents that the locking strategy has not been configured in the mobile terminal, i.e. the mobile terminal is not locked and Step 103 is performed; otherwise, the locking strategy has been configured in the mobile terminal, i.e. the mobile terminal has been locked, and Step 104 is performed. [0046]Step 103: The mobile terminal stores the received relevant information of the locking strategy which needs to be executed and terminates the current processing flow. [0047]More specifically, the command processing program installed in the mobile terminal in advance parses the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writes the IDs of the province and the locking strategy which needs to be executed by the mobile terminal in the relevant information into the fixed region of the FLASH of the mobile terminal via an interface function. The mobile terminal transmits a storage result to the locking strategy setting terminal via a communication link, wherein the storage result comprises: successful storage and storage failure. The locking strategy setting terminal performs prompting via a display according to the storage result, specifically, the locking strategy setting terminal prompts that the locking strategy is updated successfully if the storage is successful, and prompts that the updating of the locking strategy fails if the storage fails. [0048]Step 104: The mobile terminal prompts to operate over again via the locking strategy setting terminal. [0049]More specifically, when the mobile terminal determines that the mobile terminal is locked, a result that the configuration of the locking strategy fails is transmitted to the locking strategy setting terminal via a communication link, and the locking strategy setting terminal which receives the result prompts that operations need to be performed over again, i.e. the mobile terminal needs to be unlocked first before the locking strategy is configured over again. [0050]FIG. 3 is a flowchart illustrating the second method for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure. As shown in FIG. 3, the method comprises the following steps. [0051]Step 301: Relevant information of a locking strategy which needs to be executed is inputted at a mobile terminal. [0052]More specifically, a command receiving program is installed at the mobile terminal in advance and a graphical user interface of the command receiving program is entered after the installation is completed. The relevant information of the locking strategy which needs to be executed by the mobile terminal is inputted in the graphical user interface. The relevant information comprises a province and a scheme of the mobile terminal, e.g. *983*ZZXX, wherein ZZ is an ID of the scheme which may be any combinations of numbers, e.g. 58 or 59 etc. and is configured to express different schemes; XX expresses an ID of the province and ZZ may be the same for the same province. The command receiving program of the mobile terminal generates an instruction comprising the relevant information according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmits the instruction to a command processing program installed in the mobile terminal in advance. [0053]Step S302: The inputted relevant information of the locking strategy which needs to be executed is stored. [0054]More specifically, the command processing program of the mobile terminal parses the received instruction to obtain the relevant information of the locking strategy which needs to be executed by the mobile terminal, and writes the ID of the province and the locking strategy which needs to be executed by the mobile terminal in the relevant information into a fixed region of a FLASH of the mobile terminal via an interface function, for example, if the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal is *983*5810, then 5810 is written in the fixed region of the FLASH of the mobile terminal. The FLASH transmits a storage result to a command processing program, wherein the storage result comprises: successful storage and storage failure. The command processing program of the mobile terminal performs prompting via a screen according to the storage result, specifically, the command processing program prompts that the locking strategy is updated successfully if the storage is successful, and prompts that the updating of the locking strategy fails if the storage fails. [0055]Based on the method for configuring a locking strategy of a mobile terminal above, an embodiment of the disclosure also provides a method for applying a locking strategy of a mobile terminal. As shown in FIG. 4, the method comprises the following steps. [0056]Step 401: Relevant information of a locking strategy which needs to be executed by a mobile terminal is obtained. [0057]More specifically, during a power-on process of the mobile terminal, a power-on module of the mobile terminal utilizes an interface function to read the relevant information, i.e. a 4-byte code, of the locking strategy which needs to be executed, wherein the relevant information is stored in a fixed region of a FLASH of the mobile terminal. [0058]Step 402: It is determined whether or not an ID of a scheme in the relevant information is 0, if it is not 0, Step 403 is performed, and if it is 0, Step 404 is performed. [0059]More specifically, according to the read relevant information, the power-on module of the mobile terminal determines whether the last two bytes in the relevant information, i.e. the ID of the scheme, is 0, if it is not 0, it represents that the locking strategy of the mobile terminal has been configured and Step 403 is performed; and if it is 0, the locking strategy of the mobile terminal has not been configured and Step 404 is performed. [0060]Step 403: The mobile terminal is locked according to the locking strategy corresponding to the relevant information, and the current processing flow is ended. [0061]More specifically, since the locking strategy of the mobile terminal has been configured, the power-on module of the mobile terminal finds, in the mobile terminal, the locking strategy corresponding to the relevant information according to the obtained relevant information and executes the locking strategy to lock the mobile terminal. Executing the locking strategy to lock the mobile terminal belongs to an existing technology, which will not be repeated here. The locking strategy in the mobile terminal is pre-stored, in a form of a code, in a program of the mobile terminal. There may be one or more locking strategies in the embodiment of the disclosure and switching among different locking strategies of the mobile terminal can be realized using the two methods above. [0062]Step 404: A normal power-on process is performed. [0063]More specifically, since the locking strategy of the mobile terminal is not configured in the mobile terminal, the mobile terminal can be powered on normally. The normal power-on process of the mobile terminal is performed, which belongs to an existing technology and will not be repeated here. [0064]To realize the methods above, an embodiment of the disclosure also provides a system for configuring a locking strategy of a mobile terminal. As shown in FIG. 5, the system comprises: a locking strategy setting terminal 51 and a terminal 52, wherein the locking strategy setting terminal 51 is configured to set relevant information of a locking strategy which needs to be executed by a mobile terminal and transmit the relevant information to the mobile terminal 52; and [0065]the mobile terminal 52 is configured to, when the mobile terminal determines that the mobile terminal is currently unlocked, store the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0066]The locking strategy setting terminal 51 is further configured to, when the mobile terminal 52 determines that the mobile terminal 52 is currently locked, prompt to operate over again. [0067]Setting, at the locking strategy setting terminal 51, the relevant information of the locking strategy which needs to be executed by the mobile terminal and transmitting the relevant information to the mobile terminal 52 comprises: the relevant information of the locking strategy which needs to be executed by the mobile terminal is inputted at the locking strategy setting terminal 51, and according to the relevant information of the locking strategy which needs to be executed by the mobile terminal, an AT command comprising the relevant information is generated and transmitted to the mobile terminal 52. [0068]Storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal 52 parses the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writes the relevant information in a fixed region of a FLASH of the mobile terminal 52 and transmits a storage result to the locking strategy setting terminal 51; the locking strategy setting terminal 51 prompts whether or not the locking strategy is updated successfully according to the storage result. [0069]An embodiment of the disclosure also provides a mobile terminal for implementing configuration of a locking strategy of a mobile terminal. As shown in FIG. 6, the mobile terminal comprises: a command receiving program module 61 and a command processing program module 62, wherein [0070]the command receiving program module 61 is configured for input of relevant information of a locking strategy which needs to be executed; [0071]the command processing program module 62 is configured to store, in a memory, the relevant information of the locking strategy which needs to be executed. [0072]Inputting the relevant information of the locking strategy which needs to be executed comprises: the relevant information of the locking strategy which needs to be executed by the mobile terminal is inputted in the command receiving program module 61 in the mobile terminal; the command receiving program module 61 generates an instruction comprising the relevant information according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal and transmits the instruction to the command processing program module 62 installed in the mobile terminal in advance. [0073]Storing the inputted relevant information of the locking strategy which needs to be executed comprises: the command processing program module 62 of the mobile terminal parses the received instruction and writes the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal; the FLASH transmits a storage result to the command processing program module 61 of the mobile terminal; the command processing program module 62 prompts whether or not the locking strategy is updated successfully according to the storage result. [0074]The above are only preferred embodiments of the disclosure and should not be used for limiting the scope of protection of the disclosure. Any modifications, equivalent replacements, improvements and the like within the principle of the disclosure shall fall within the scope of protection of the disclosure.(String), 技术领域 [0001] 本发明涉及移动终端锁定技术,尤其涉及一种移动终端锁定策略配置及应用的方法、系统及移动终端。 背景 [0002] 目前,越来越多的移动终端得到广泛应用,移动通信运营商可以根据自己的需求定制移动终端产品。 移动通信运营商在定制移动终端产品时,可能会要求锁网、锁卡或移动终端等。 锁定移动终端是对移动终端的特殊要求,定制的移动终端只能使用特定的移动网络,或者特定的SIM卡/USIM卡。 锁卡是对卡的一种特殊要求,卡锁后要求卡只能在某个移动终端上使用,不能在其他移动终端上使用。 锁网、锁卡、锁移动终端,可有效解决用户私自更改网络、擅自配送商品、客户流失等问题。 [0003] 在相关技术中,为了给移动终端锁网或锁卡,从而对移动终端进行锁定,通常在研发移动终端时,会在移动终端中编写锁定策略。 因此,锁定策略是固定的,即使是移动通信运营商也不能修改。 随着移动终端技术的发展和移动通信运营商业务的不断增长,用户数量不断增长,对移动通信运营商的需求也越来越大。 如何最大程度地提高研发效率、生产效率和为客户配置的灵活性,是需要解决的问题。 概括 [0004] 有鉴于此,本发明提供了一种移动终端锁定策略的配置及应用方法、系统及移动终端,能够方便灵活地配置移动终端的锁定策略。 [0005] 本发明提供以下技术方案。 [0006] 本发明提供了一种移动终端的锁定策略配置方法,包括: [0007] 在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并将相关信息发送给移动终端; 和 [0008] 当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息。 [0009] 上述方法中,所述方法还包括: 当移动终端确定移动终端当前处于锁定状态时,通过锁定策略设置终端提示重新操作。 [0010] 上述方法中,在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息并发送给移动终端,包括: [0011] 在锁定策略设置端输入移动端需要执行的锁定策略的相关信息,根据移动端需要执行的锁定策略的相关信息生成AT命令。 终端,向移动终端发送AT指令,AT指令中包含移动终端需要执行的锁定策略的相关信息。 [0012]上述方法中,存储移动终端需要执行的锁定策略的相关信息包括:移动终端解析AT命令获取移动终端的锁定策略的相关信息,将相关信息写入 移动终端FLASH的固定区域,并将存储结果发送给锁定策略设置终端; 锁定策略设置终端根据存储结果提示锁定策略是否更新成功。 [0013] 本发明还提供了一种移动终端的锁定策略配置方法,包括: [0014] 在移动终端输入需要执行的锁定策略的相关信息; 和 [0015] 存储输入的需要执行的锁定策略的相关信息。 [0016] 上述方法中,在移动终端输入需要执行的锁定策略的相关信息包括: 在预先安装在移动终端的命令接收程序中输入需要执行的锁定策略的相关信息。 由移动终端执行; 命令接收程序根据输入的移动终端需要执行的锁定策略的相关信息生成指令,并将该指令发送给预先安装在移动终端中的命令处理程序,其中,该指令包括相关的 移动终端需要执行的锁定策略信息。 [0017] 上述方法中,存储输入的需要执行的锁定策略的相关信息包括:移动终端的命令处理程序解析接收到的指令并写入获取的需要执行的锁定策略的相关信息。 移动终端在移动终端FLASH的固定区域; FLASH将存储结果传输给移动终端的命令处理程序; 命令处理程序根据存储结果提示锁定策略是否更新成功。 [0018] 本发明还提供了一种应用移动终端锁定策略的方法,包括: [0019] 获取移动终端需要执行的锁定策略的相关信息,当确定相关信息中的方案ID表示已经配置了锁定策略时,根据该锁定策略对应的锁定策略对移动终端进行锁定 相关信息。 [0020] 上述方法中,所述方法还包括: 当确定相关信息中方案的ID表示未配置锁定策略时,执行正常开机流程。 [0021] 上述方法中,获取移动终端需要执行的锁定策略的相关信息包括:在移动终端开机过程中,移动终端的开机模块读取锁定策略的相关信息。 需要由移动终端执行的锁定策略,其中需要由移动终端执行的锁定策略的相关信息存储在移动终端的FLASH的固定区域中; [0022] 根据相关信息对应的锁定策略锁定移动终端包括: 移动终端开机模块根据获取的相关信息在移动终端中找到相关信息对应的锁定策略并执行 锁定移动端的锁定策略。 [0023] 本发明还提供了一种移动终端的锁定策略配置系统,包括:锁定策略设置终端和终端,锁定策略设置终端用于设置需要执行的锁定策略的相关信息。 移动终端,并将相关信息传输至移动终端; [0024]移动终端,用于当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息。 [0025] 在上面的系统中, [0026] 锁定策略设置端,还用于当移动终端确定移动终端当前处于锁定状态时,通过锁定策略设置端提示重新操作。 [0027] 本发明还提供了一种移动终端,用于实现移动终端锁定策略的配置,包括:命令接收程序模块和命令处理程序模块,其中, [0028] 命令接收程序模块,用于输入需要执行的锁定策略的相关信息; [0029] 命令处理程序模块,用于将输入的需要执行的锁定策略的相关信息存储在内存中。 [0030] 本发明提供的移动终端锁定策略的配置及应用方法、系统及移动终端,能够在锁定策略设置终端设置移动终端需要执行的锁定策略的相关信息, 将相关信息发送给移动终端,并存储当移动终端确定当前移动终端处于解锁状态时移动终端需要执行的锁定策略的相关信息。 这样,可以在移动终端不开机的情况下,批量配置移动终端的锁定策略。 移动终端生产过程中安全、简单、方便,移动终端升级方便,大大提高了生产效率。 [0031] 本发明还可以在移动终端输入需要执行的锁定策略的相关信息,并存储需要执行的锁定策略的相关信息。 移动通信运营商可以直接操作移动终端,随时切换到需要的锁定策略。 [0032] 综上所述,移动终端的锁定策略可以灵活配置,使得移动通信运营商无需移动终端厂商修改锁定策略,就可以灵活地管理移动终端的销售和维护,从而有效降低研发成本。 、开发和维护成本。 附图的简要说明 [0033] 图1为本发明实施例移动终端锁定策略配置的第一种实现方法流程图; [0034] 图2为根据本发明一实施例的命令传输程序的图形用户界面的示意图。 [0035] 图3为本发明实施例移动终端锁定策略配置的第二种实现方法流程图。 [0036] 图4为本发明实施例移动终端锁定策略应用的实现方法流程图。 [0037] 图5是根据本发明实施例的移动终端的锁定策略配置实现系统结构图。 和 [0038] 图6是根据本发明实施例的实现移动终端锁定策略配置的移动终端结构图。 具体实施方式 [0039]当移动通信运营商需要配置或更新移动终端的锁定策略时,可以采用本发明实施例提供的两种配置移动终端锁定策略的方法。 本发明实施例的基本原理是:当移动终端确定移动终端时,在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并发送给移动终端。 终端当前处于解锁状态,存储移动终端需要执行的锁定策略的相关信息; 或者,在移动终端输入需要执行的锁定策略的相关信息,并存储输入的需要执行的锁定策略的相关信息。 [0040] 下面结合附图及实施例对本发明作进一步详细说明。 [0041] 本发明实施例提供的一种移动终端的锁定策略配置方法如图1所示,包括以下步骤。 [0042] 步 101 :在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并发送给移动终端。 [0043] 更具体的,所述锁定策略设置终端预先安装有移动终端的指令传输程序,安装完成后进入指令传输程序的图形化用户界面,其中所述锁定策略设置终端可以为电脑, 例如 个人计算机 (PC)。 图2为根据本发明实施例的命令传输程序的图形用户界面的示意图。 如图2所示,在命令发送程序的图形用户界面中输入移动终端需要执行的锁定策略的相关信息,即移动终端的省份和方案。 省份可以用2字节的ID表示,该ID对应移动终端的SIM/USIM卡的ICCID中的省份ID。 该方案是移动终端需要执行的锁定策略,用一个2字节的ID表示。 不同的ID代表不同的方案,因此移动终端需要执行的相关信息实际上是一个4字节的代码。 锁定策略设置终端的命令发送程序根据移动终端需要执行的锁定策略的相关信息生成包含相关信息的AT命令,并通过与移动终端之间的通信链路将AT命令发送给移动终端。 锁定策略设置终端和移动终端,其中,所述通信链路可以为通用串行总线(USB)、蓝牙等物理链路。 如果采用USB作为通信链路,则在配置移动终端的锁定策略时,移动终端无需开机,可以通过锁定策略设置终端向移动终端下发AT命令。 [0044] 步 102 :移动终端判断当前移动终端是否处于锁定状态,如果当前移动终端处于解锁状态,步骤 103 被执行,如果当前移动端处于锁定状态,步骤 104 被执行。 [0045]更具体地,移动终端处于空闲状态,空闲状态可以是关机状态或者指示移动终端正在开机的状态。 移动终端的指令处理程序接收到锁定策略设置终端发送的AT指令后,读取移动终端中FLASH固定区域的标志位,确定移动终端为卡锁移动终端 移动终端锁根据标志位触发移动终端的卡锁和移动终端锁验证程序。 网络锁和移动终端锁验证程序判断移动终端FLASH的固定区域是否为空,如果为空,则表示移动终端没有配置锁定策略,即移动终端没有 锁定和步骤 103 执行; 否则,移动端已经配置了锁定策略,即移动端已经被锁定,步骤 104 被执行。 [0046] 步 103 :移动终端存储接收到的需要执行的锁定策略的相关信息,并结束当前处理流程。 [0047] 更具体的,预先安装在移动终端中的指令处理程序解析AT指令获取移动终端锁定策略的相关信息,写入省份ID和需要移动执行的锁定策略 终端中的相关信息通过接口函数存入移动终端FLASH的固定区域。 移动终端通过通信链路向锁定策略设置终端发送存储结果,存储结果包括:存储成功和存储失败。 锁定策略设置终端根据存储结果通过显示器进行提示,具体的,锁定策略设置终端如果存储成功则提示锁定策略更新成功,如果存储失败则提示锁定策略更新失败。 失败。 [0048] 步 104 :移动端通过锁定策略设置端提示重新操作。 [0049] 更具体地,当移动终端确定移动终端被锁定时,通过通信链路向锁定策略设置终端发送锁定策略配置失败的结果,接收到该结果的锁定策略设置终端提示: 需要重新操作,即需要先解锁移动终端,再重新配置锁定策略。 [0050] 图3为本发明实施例移动终端锁定策略配置的第二种实现方法流程图。 如图3所示,该方法包括以下步骤。 [0051] 步 301 :在移动端输入需要执行的锁定策略的相关信息。 [0052] 更具体地,移动终端预先安装命令接收程序,安装完成后进入命令接收程序的图形用户界面。 在图形用户界面中输入移动终端需要执行的锁定策略的相关信息。 相关信息包括移动终端的省份和方案,例如: *983*ZZXX,其中ZZ是方案的ID,可以是数字的任意组合,例如 58或59等,用于表达不同的方案; XX表示省份的ID,同一个省份ZZ可以相同。 移动终端的命令接收程序根据输入的移动终端需要执行的锁定策略的相关信息生成包括相关信息的指令,并将该指令发送给安装在移动终端中的命令处理程序 进步。 [0053] 脚步 302 :存储输入的需要执行的锁定策略的相关信息。 [0054]更具体的,移动终端的命令处理程序解析接收到的指令,得到移动终端需要执行的锁定策略的相关信息,写入省份ID和需要执行的锁定策略 移动终端通过接口函数将相关信息中的相关信息写入移动终端FLASH的固定区域,例如输入移动终端需要执行的锁定策略的相关信息为*983*5810 ,则5810写入移动终端FLASH的固定区域。 FLASH向命令处理程序发送存储结果,存储结果包括:存储成功和存储失败。 移动终端的命令处理程序根据存储结果进行屏幕提示,具体的,如果存储成功则命令处理程序提示锁定策略更新成功,如果存储成功则提示锁定策略更新失败。 存储失败。 [0055] 基于上述移动终端锁定策略的配置方法,本发明实施例还提供了一种移动终端锁定策略的应用方法。 如图4所示,该方法包括以下步骤。 [0056] 步 401 :获取移动终端需要执行的锁定策略的相关信息。 [0057] 具体的,在移动终端开机过程中,移动终端的开机模块通过接口函数读取需要执行的锁定策略的相关信息,即4字节代码, 其中,相关信息存储在移动终端的FLASH的固定区域中。 [0058] 步 402 :判断相关信息中scheme的ID是否为0,如果不为0,则Step 403 执行,如果为0,则Step 404 被执行。 [0059] 具体的,移动终端开机模块根据读取到的相关信息,判断相关信息的最后两个字节,即方案的ID是否为0,如果不为0,则表示 已配置移动端的锁定策略,步骤 403 执行; 为0表示移动端的锁定策略没有配置,步骤 404 被执行。 [0060] 步 403 :根据相关信息对应的锁定策略锁定移动终端,结束本次处理流程。 [0061] 具体的,由于已经配置了移动终端的锁定策略,移动终端的开机模块根据获取的相关信息在移动终端中查找到相关信息对应的锁定策略,并执行锁定策略 锁定移动终端。 执行锁定策略锁定移动终端属于现有技术,在此不再赘述。 移动终端中的锁定策略以代码的形式预先存储在移动终端的程序中。 本发明实施例中的锁定策略可以有一种或多种,​​通过上述两种方法可以实现移动终端不同锁定策略之间的切换。 [0062] 步 404 :执行正常的上电过程。 [0063] 更具体的,由于移动终端中没有配置移动终端的锁定策略,所以移动终端可以正常开机。 进行移动终端的正常开机过程,属于现有技术,在此不再赘述。 [0064] 为实现上述方法,本发明实施例还提供了一种移动终端锁定策略配置系统。 如图5所示,该系统包括:锁定策略设置端 51 和一个终端 52 , 其中锁定策略设置终端 51用于设置移动终端需要执行的锁定策略的相关信息,并将相关信息发送给移动终端 52 ; 和 [0065] 移动端 52 用于当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息。 [0066] 锁定策略设置终端 51 还用于,当移动终端 52 确定移动端 52 当前被锁定,提示重新操作。 [0067] 设置,在锁定策略设置端 51 , 移动端需要执行的锁定策略的相关信息,并将相关信息发送给移动端 52 包括:在锁定策略设置端输入移动终端需要执行的锁定策略的相关信息 51 ,根据移动终端需要执行的锁定策略的相关信息,生成包含相关信息的AT命令发送给移动终端 52 . [0068] 存储移动终端需要执行的锁定策略的相关信息包括:移动终端 52 解析AT指令获取移动终端锁定策略的相关信息,将相关信息写入移动终端FLASH的固定区域 52 并将存储结果发送给锁定策略设置端 51 ; 锁定策略设置终端 51 根据存储结果提示锁定策略是否更新成功。 [0069] 本发明实施例还提供了一种移动终端,用于实现移动终端的锁定策略配置。 如图6所示,该移动终端包括:命令接收程序模块 61 和命令处理程序模块 62 , 其中 [0070] 命令接收程序模块 61 用于输入需要执行的锁定策略的相关信息; [0071] 命令处理程序模块 62 用于在内存中存储需要执行的锁定策略的相关信息。 [0072] 输入需要执行的锁定策略的相关信息包括:在命令接收程序模块中输入移动终端需要执行的锁定策略的相关信息。 61 在移动终端; 命令接收程序模块 61 根据输入的移动终端需要执行的锁定策略的相关信息,生成包括相关信息的指令,并将该指令发送给命令处理程序模块 62 提前安装在移动端。 [0073] 存储输入的需要执行的锁定策略的相关信息包括: 命令处理程序模块 62 移动终端解析接收到的指令,将获取的需要移动终端执行的锁定策略的相关信息写入移动终端FLASH的固定区域; FLASH将存储结果传送给命令处理程序模块 61 移动终端; 命令处理程序模块 62 根据存储结果提示锁定策略是否更新成功。 [0074] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的保护范围。 凡在本发明的原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101977373A(String), EP2632198A1(String), EP2632198A4(String), US20130231089A1(String), US9078133B2(String), WO2012051816A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101977373A(String), EP2632198A1(String), EP2632198A4(String), US20130231089A1(String), US9078133B2(String), WO2012051816A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9078133B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101977373A(String), EP2632198A1(String), EP2632198A4(String), US20130231089A1(String), US9078133B2(String), WO2012051816A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), CN101977373A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), EP2632198A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.830 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.830 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.830 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), EP2632198A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), US20130231089A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), US9078133B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), WO2012051816A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9078133B2(String), US9078133B2(String), 1436198400(Integer), 270643(Integer), 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.883 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZHANG, LI(String), HAN, CHUNYUAN(String), ZHANG, QIANG(String), JI, BAOLING(String), 中兴通讯股份有限公司(String), ZHANG LI(String), HAN CHUNYUAN(String), ZHANG QIANG(String), JI BAOLING(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184960(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184960(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHANG, LI(String), ZHANG LI(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HAN, CHUNYUAN(String), HAN CHUNYUAN(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHANG, QIANG(String), ZHANG QIANG(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: JI, BAOLING(String), JI BAOLING(String), 0(Integer), 1681975537(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184960(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.945 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75911(Integer), 2(Integer), 184960(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75912(Integer), 2(Integer), 184960(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75913(Integer), 2(Integer), 184960(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75914(Integer), 2(Integer), 184960(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75911(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:37.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Keypad battery pack, mobile terminal available for different keypad battery packs, and method of changing keypad of mobile terminal(String), 键盘电池组、可用于不同键盘电池组的移动终端、以及更换移动终端键盘的方法(String), US20080004085A1(String), A keypad battery pack, a mobile terminal available for different keypad battery packs, and a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack are provided. The mobile terminal has a keypad formed on a battery pack as well as on a front surface of the mobile terminal, thereby expanding a keypad-placement area to a rear surface of the mobile terminal. As a result, keys of the keypad are arranged on both surfaces of the mobile terminal, and thus a key arrangement space has room for an additional key, thereby enabling easy adding of a key. Further, the keypads of the mobile terminal are arranged on the rear surface and the front surface according to functions of the keypads, thereby providing a keypad structure suitable for a mobile terminal having an additional function. Further, the mobile terminal may selectively mount a plurality of battery packs having different types and arrangements of keypads.(String), 提供了一种键盘电池组、可用于不同键盘电池组的移动终端、以及通过用不同的电池组更换电池组来改变移动终端的键盘的方法。 移动终端具有形成在电池组上以及移动终端前表面上的小键盘,从而将小键盘放置区域扩展到移动终端的后表面。 结果,小键盘的按键布置在移动终端的两个表面上,因此按键布置空间具有容纳额外按键的空间,从而能够容易地添加按键。 进一步地,移动终端的小键盘根据小键盘的功能设置在后表面和前表面,从而提供适用于具有附加功能的移动终端的小键盘结构。 此外,移动终端可以选择性地安装具有不同类型和排列的键盘的多个电池组。(String), US11/770428(String), 1182960000(Integer), US20080004085A1(String), 1199289600(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 7(Integer), US20020082042A1 | US20030153349A1 | US20030181226A1 | US20030211834A1 | US20060282407A1 | US20070057851A1 | US7571384B1(String), 30(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184961(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c98d11b468834b9bbbf56b52fee223bb.png(String), 184961(Integer), c98d11b468834b9bbbf56b52fee223bb.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Keypad battery pack, mobile terminal available for different keypad battery packs, and method of changing keypad of mobile terminal(String), 键盘电池组、可用于不同键盘电池组的移动终端、以及更换移动终端键盘的方法(String), US20080004085A1(String), A keypad battery pack, a mobile terminal available for different keypad battery packs, and a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack are provided. The mobile terminal has a keypad formed on a battery pack as well as on a front surface of the mobile terminal, thereby expanding a keypad-placement area to a rear surface of the mobile terminal. As a result, keys of the keypad are arranged on both surfaces of the mobile terminal, and thus a key arrangement space has room for an additional key, thereby enabling easy adding of a key. Further, the keypads of the mobile terminal are arranged on the rear surface and the front surface according to functions of the keypads, thereby providing a keypad structure suitable for a mobile terminal having an additional function. Further, the mobile terminal may selectively mount a plurality of battery packs having different types and arrangements of keypads.(String), 提供了一种键盘电池组、可用于不同键盘电池组的移动终端、以及通过用不同的电池组更换电池组来改变移动终端的键盘的方法。 移动终端具有形成在电池组上以及移动终端前表面上的小键盘,从而将小键盘放置区域扩展到移动终端的后表面。 结果,小键盘的按键布置在移动终端的两个表面上,因此按键布置空间具有容纳额外按键的空间,从而能够容易地添加按键。 进一步地,移动终端的小键盘根据小键盘的功能设置在后表面和前表面,从而提供适用于具有附加功能的移动终端的小键盘结构。 此外,移动终端可以选择性地安装具有不同类型和排列的键盘的多个电池组。(String), US11/770428(String), 1182960000(Integer), US20080004085A1(String), 1199289600(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 7(Integer), US20020082042A1 | US20030153349A1 | US20030181226A1 | US20030211834A1 | US20060282407A1 | US20070057851A1 | US7571384B1(String), \20230420\c98d11b468834b9bbbf56b52fee223bb.png(String), 30(Integer), 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 1. A keypad battery pack having a first surface and a second surface and including a battery therein, the keypad battery pack comprising:a keypad formed on the first surface; anda battery terminal formed on the second surface.(String), 1.键盘电池组一个有第一表面和第二表面并且在其中包括电池,键盘电池组包括:形成于第一表面上的键盘;和电池端子形成在第二表面上。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 2. The keypad battery pack of claim 1, wherein the keypad has a 3×4 key arrangement.(String), 2.如权利要求1所述的键盘电池组,其中键盘采用3×4键排列。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 3. The keypad battery pack of claim 1, wherein the keypad has a 5×4 key arrangement.(String), 3.如权利要求1所述的键盘电池组,其中键盘采用5×4键排列。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 4. The keypad battery pack of claim 1, wherein the keypad includes a search key.(String), 4.如权利要求1所述的键盘电池组,其中键盘包括一个搜索键。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 5. The keypad battery pack of claim 1, further comprising a key scan control unit electrically connected to the keypad and the battery terminal for recognizing a specific key input of the keypad.(String), 5.如权利要求1所述的键盘电池组,还包括按键扫描控制单元电性连接于键盘与电池端,用以识别键盘的特定按键输入。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 6. A mobile terminal comprising:a terminal body having a front surface and a rear surface,a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface; anda battery pack having an inner surface contacted with the rear surface of the terminal body and an outer surface facing the same direction as the rear surface of the terminal body, and having a rear keypad formed on the outer surface, wherein the battery pack is mounted on the battery mounting area of the terminal body to be electrically connected to the terminal body.(String), 6.移动端包括:具有前表面和后表面的终端主体,前显示单元形成在前表面上,后显示单元和电池安装区域形成在后表面上;和电池组,其内表面与终端主体的后表面接触,外表面与终端主体的后表面朝向相同的方向,并且具有形成在外表面上的后键盘,其中安装有电池组在终端主体的电池安装区域上以与终端主体电连接。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 7. The mobile terminal of claim 6, wherein the terminal body further comprises a front keypad formed on the front surface.(String), 7.如权利要求6所述的移动终端,其中终端机体还包括形成在前表面上的前键盘。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 8. The mobile terminal of claim 6, wherein the terminal body further comprises a charging terminal formed on the battery mounting area, the battery pack further comprises a battery terminal formed on the inner surface, and the charging terminal and the battery terminal are electrically connected to each other by contact.(String), 8.如权利要求6所述的移动终端,其中终端本体还包括形成在电池安装区上的充电端子,电池组还包括形成在内表面上的电池端子,充电端子与电池端子通过接触电连接。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 9. The mobile terminal of claim 7, wherein a type of the front keypad is different from a type of the rear keypad.(String), 9.如权利要求7所述的移动终端,其中前键盘的类型与后键盘的类型不同。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 10. The mobile terminal of claim 7, wherein at least one of the front keypad and the rear keypad has one of a 3×4 key arrangement and a 5×4 key arrangement.(String), 10.如权利要求7所述的移动终端,其中前键盘和后键盘中的至少一个具有3×4键排列和5×4键排列之一。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 11. The mobile terminal of claim 7, wherein at least one of the front keypad and the rear keypad includes a search key.(String), 11.如权利要求7所述的移动终端,其中前键盘和后键盘中的至少一个包括搜索键。(String), 1(Integer), 10(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 12. The mobile terminal of claim 7, wherein the terminal body further comprises a first key scan control unit electrically connected to the front keypad for recognizing a specific key input.(String), 12.如权利要求7所述的移动终端,其中终端机体还包括第一按键扫描控制单元,电连接到前置键盘,用于识别特定的按​​键输入。(String), 1(Integer), 11(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 13. The mobile terminal of claim 12, wherein the terminal body further comprises a second key scan control unit electrically connected to the rear keypad for recognizing a specific key input.(String), 13.如权利要求12所述的移动终端,其中终端机体还包括第二键扫描控制单元,电连接到后键盘,用于识别特定键输入。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 14. The mobile terminal of claim 12, wherein the battery pack further comprises a second key scan control unit electrically connected to the rear keypad for recognizing a specific key input.(String), 14.如权利要求12所述的移动终端,其中电池组还包括第二按键扫描控制单元,电连接至后键盘,用于识别特定按键输入。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 15. The mobile terminal of claim 8, wherein the charging terminal and the battery terminal each have a serial communication terminal.(String), 15.如权利要求8所述的移动终端,其中充电端和电池端各有一个串行通信端。(String), 1(Integer), 14(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 16. The mobile terminal of claim 6, wherein a size of the front display unit is larger than a size of the rear display unit.(String), 16.如权利要求6所述的移动终端,其中前显示单元的尺寸大于后显示单元的尺寸。(String), 1(Integer), 15(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 17. The mobile terminal of claim 6, wherein the front display unit is formed over an entire front surface of the terminal body.(String), 17.如权利要求6所述的移动终端,其中前显示单元形成在终端机体的整个前表面上。(String), 1(Integer), 16(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 18. A mobile terminal comprising:a terminal body having a front surface and a rear surface,a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface;a first battery pack having an inner surface and an outer surface, mounted on the battery mounting area of the terminal body such that the inner surface is contacted with the rear surface of the terminal body to be electrically connected to the terminal body, and having a first keypad formed on the outer surface facing the same direction as the rear surface of the terminal body; anda second battery pack having an inner surface and an outer surface, and having a second keypad formed on the outer surface that is of a different type from a type of the first keypad.(String), 18.移动终端包括:具有前表面和后表面的终端主体,前显示单元形成在前表面上,后显示单元和电池安装区域形成在后表面上;第一电池组具有内表面和外表面,安装在终端主体的电池安装区域上,使得内表面与终端主体的后表面接触以电连接到终端主体,并且具有第一键盘形成在与终端机身后表面同向的外表面上;和第二电池组具有内表面和外表面,并且具有形成在外表面上的第二键盘,第二键盘的类型与第一键盘的类型不同。(String), 0(Integer), 17(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 19. The mobile terminal of claim 18, wherein the terminal body further comprises a front keypad formed on the front surface.(String), 19.如权利要求18所述的移动终端,其中终端机体还包括形成在前表面上的前键盘。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 20. The mobile terminal of claim 18, wherein the terminal body further comprises a charging terminal formed on the battery mounting area, and each of the first and second battery packs further comprises a battery terminal formed on the respective inner surfaces thereof to be electrically connected to the charging terminal.(String), 20.如权利要求18所述的移动终端,其中终端本体还包括形成在电池安装区上的充电端子,并且第一电池组和第二电池组中的每一个还包括形成在其各自的内表面上以电连接到充电端子的电池端子。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 21. The mobile terminal of claim 19, wherein a type of the front keypad is different from a type of the first keypad and a type of the second keypad.(String), 21.如权利要求19所述的移动终端,其中前键盘的类型不同于第一键盘的类型和第二键盘的类型。(String), 1(Integer), 20(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 22. The mobile terminal of claim 19, wherein the front keypad includes a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and another has a 5×4 key arrangement.(String), 22.如权利要求19所述的移动终端,其中正面键盘包括搜索键,第一键盘和第二键盘中的一个为3×4按键排列,另一个为5×4按键排列。(String), 1(Integer), 21(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 23. The mobile terminal of claim 18, wherein the first keypad and the second keypad each include a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and the other has a 5×4 key arrangement.(String), 23.如权利要求18所述的移动终端,其中第一键盘和第二键盘均包括搜索键,第一键盘和第二键盘中的一个为3×4的按键排列,另一个为5×4的按键排列。(String), 1(Integer), 22(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 24. The mobile terminal of claim 19, wherein the terminal body further comprises a first key scan control unit electrically connected to the front keypad for recognizing a specific key input.(String), 24.如权利要求19所述的移动终端,其中终端机体还包括第一按键扫描控制单元,电连接到前置键盘,用于识别特定的按​​键输入。(String), 1(Integer), 23(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 25. The mobile terminal of claim 24, wherein the terminal body further comprises a second key scan control unit electrically connected to the first keypad or to the second keypad for recognizing a specific key input.(String), 25.如权利要求24所述的移动终端,其中终端机体还包括电连接到第一键盘或第二键盘的第二键扫描控制单元,用于识别特定键输入。(String), 1(Integer), 24(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 26. The mobile terminal of claim 24, wherein the first battery pack further comprises a second key scan control unit electrically connected to the first keypad for recognizing a specific key input, and the second battery pack further comprises a third key scan control unit electrically connected to the second keypad for a specific key input.(String), 26.如权利要求24所述的移动终端,其中第一电池组还包括第二按键扫描控制单元,电性连接第一键盘,用于识别特定按键输入;第二电池组还包括第三按键扫描控制单元,电性连接第二键盘,用于识别特定按键输入。(String), 1(Integer), 25(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 27. The mobile terminal of claim 20, wherein the charging terminal and the battery terminal each have a serial communication terminal.(String), 27.如权利要求20所述的移动终端,其中充电端和电池端各有一个串行通信端。(String), 1(Integer), 26(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 28. The mobile terminal of claim 18, wherein a size of the front display unit is larger than a size of the rear display unit.(String), 28.如权利要求18所述的移动终端,其中前显示单元的尺寸大于后显示单元的尺寸。(String), 1(Integer), 27(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 29. The mobile terminal of claim 18, wherein the front display unit is formed over an entire front surface of the terminal body.(String), 29.如权利要求18所述的移动终端,其中前显示单元形成在终端机体的整个前表面上。30、一种移动终端键盘的更换方法、移动终端有终端机体,其前表面带有前显示单元,后表面带有后显示单元和电池安装区,第一电池组安装在电池安装区上,外表面带有第一键盘,以及第二电池包装具有带第二键盘的外表面,该第二键盘的类型与第一键盘的类型不同,该方法包括:从电池安装区取出第一电池组;和在电池安装区安装第二电池组。(String), 1(Integer), 28(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184961(Integer), 30. A method for changing a keypad of a mobile terminal, the mobile terminal having a terminal body having a front surface with a front display unit and a rear surface with a rear display unit and battery mounting area, a first battery pack mounted on the battery mounting area and having an outer surface with a first keypad, and a second battery pack having an outer surface with a second keypad that is of a different type from a type of the first keypad, the method comprising:removing the first battery pack from the battery mounting area; andmounting the second battery pack on the battery mounting area.(String), 0(Integer), 29(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184961(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to a Korean Patent Application entitled “KEYPAD BATTERY PACK, MOBILE TERMINAL AVAILABLE FOR DIFFERENT KEYPAD BATTERY PACKS, AND METHOD OF CHANGING KEYPAD OF MOBILE TERMINAL” filed in the Korean Intellectual Property Office on Jun. 28, 2006 and assigned Serial No. 2006-0058861, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal, in particular, to a keypad battery pack, a mobile terminal available for different keypad battery packs, and a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack. [0004]2. Description of the Related Art [0005]Mobile terminals, for example mobile phones and Personal Digital Assistants (PDAs), have been remarkably developed and now are widely used in modern life. As use of mobile terminals becomes more common, users' demands have become more varied. Accordingly, mobile terminals have been developed to conveniently provide more functions. For example, mobile terminals are provided with various additional functions such as multimedia, wireless Internet, or digital broadcast transmitting and receiving, as well as common functions such as calling, message transmitting and receiving, or personal information management. [0006]A mobile terminal generally has a keypad as an input means for receiving a user's input. As a mobile terminal is provided with various additional functions, a new key for performing and controlling the additional functions is added to a typical keypad. However, a mobile terminal has a limited keypad-placement area, and thus it is not easy to additionally place a new key on the limited keypad-placement area. [0007]Meanwhile, various keypads are provided for different nations, manufacturers or product types. The types of keypads mainly include 3-×*4 keys of a typical telephone key arrangement and 5×4 keys of a QWERTY key arrangement of a keyboard. Generally, a key arrangement of a keypad is preset in a mobile terminal manufacturing process, and thus it is impossible to change the key arrangement thereafter. In other words, generally a keypad of a mobile terminal has a fixed key arrangement. Thus, if a user having a mobile terminal of a specific key arrangement (for example, 3×4 keys) wants to change to another key arrangement (for example, 5×4 keys), the user must replace the mobile terminal with a new mobile terminal having another key arrangement. SUMMARY OF THE INVENTION [0008]In order to solve the above problems, the present invention expands a keypad-placement area of a mobile terminal, thereby enabling easier addition of keys. [0009]The present invention further provides a keypad structure suitable for a mobile terminal having various additional functions. [0010]The present invention further provides a mobile terminal and method for alternately using keypads having different key arrangements. [0011]The present invention further provides a mobile terminal and method for replacing keypads according to purpose. [0012]The present invention further improves convenience and satisfaction of a user of a mobile terminal. [0013]Typically, a keypad is formed on a front surface of a mobile terminal, and a battery pack is formed on a rear surface of the mobile terminal. The present invention utilizes the rear surface of the mobile terminal, which has previously been used only as a battery pack mounting area, as a keypad-placement area. [0014]Therefore, the present invention provides a keypad battery pack, i.e. a battery pack having a keypad thereon. The present invention further provides a mobile terminal for alternately mounting keypad battery packs of different types. The present invention further provides a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack. [0015]A mobile terminal according to an exemplary embodiment of the present invention includes a terminal body having a front surface and a rear surface, a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface; a battery pack having an inner surface contacted with the rear surface of the terminal body and an outer surface facing the same direction as the rear surface of the terminal body, and having a rear keypad formed on the outer surface, wherein the battery pack is mounted on the battery mounting area of the terminal body to be electrically connected to the terminal body. [0016]The terminal body may further include a front keypad formed on the front surface. The terminal body may further include a charging terminal formed on the battery mounting area, and the battery pack may further include a battery terminal formed on the inner surface, wherein the charging terminal and the battery terminal are electrically connected to each other by contact. [0017]A type of the front keypad may be different from a type of the rear keypad. At least one of the front keypad and the rear keypad may have one of a 3×4 and a 5×4 key arrangement, and may include a search key. [0018]The terminal body may further include a first key scan control unit and a second key scan control unit electrically connected to the front keypad and the rear keypad, respectively, for recognizing a specific key input. Alternatively, the terminal body may further include a first key scan control unit and the battery pack further includes a second key scan control unit. [0019]The charging terminal and the battery terminal may each have a serial communication terminal. A size of the front display unit may be larger than a size of the rear display unit, and the front display unit may be formed over an entire front surface of the terminal body. [0020]A mobile terminal according to another embodiment of the present invention includes a terminal body having a front surface and a rear surface, a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface; a first battery pack having an inner surface and an outer surface mounted on the battery mounting area of the terminal body such that the inner surface is contacted with the rear surface of the terminal body to be electrically connected to the terminal body, and having a first keypad formed on the outer surface facing the same direction as the rear surface of the terminal body; and a second battery pack having an inner surface and an outer surface, and having a second keypad formed on the outer surface that is of a different type from a type of the first keypad. [0021]The terminal body may further include a front keypad formed on the front surface. The terminal body may further include a charging terminal formed on the battery mounting area, and each of the first and second battery packs may further include a battery terminal formed on the respective inner surfaces thereof to be electrically connected to the charging terminal. [0022]A type of the front keypad may be different from a type of the first keypad and a type of the second keypad. The front keypad may include a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and the other has a 5*4 key arrangement. The first keypad and the second keypad may each include a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and the other has a 5×4 key arrangement. [0023]The terminal body may further include a first key scan control unit electrically connected to the front keypad for recognizing a specific key input. The terminal body may further include a second key scan control unit electrically connected to the first keypad or to the second keypad for recognizing a specific key input. Alternatively, the first battery pack may further include a second key scan control unit electrically connected to the first keypad for recognizing a specific key input, and the second battery pack further includes a third key scan control unit electrically connected to the second keypad for recognizing a specific key input. [0024]The charging terminal and the battery terminal may each have a serial communication terminal. A size of the front display unit may be larger than a size of the rear display unit, and the front display unit may be formed over the entire front surface of the terminal body. [0025]According to another exemplary embodiment of the present invention, a method for changing a keypad of a mobile terminal having a terminal body having a front surface with a front display unit and a rear surface with a rear display unit and battery mounting area, a first battery pack mounted on the battery mounting area and having an outer surface with a first keypad, and a second battery pack having an outer surface with a second keypad that is of a different type from a type of the first keypad, includes removing the first battery pack from the battery mounting area; and mounting the second battery pack on the battery mounting area. BRIEF DESCRIPTION OF THE DRAWINGS [0026]The objects, features, and advantages of the present invention will become more apparent from the following detailed description in conjunction with the accompanying drawings, in which: [0027]FIG. 1A is a perspective view illustrating an example of a keypad battery pack in accordance with an exemplary embodiment of the present invention, and FIG. 1B is a perspective view illustrating another example of a keypad battery pack in accordance with an exemplary embodiment of the present invention; [0028]FIG. 2 is a perspective view illustrating a front surface of a mobile terminal having a keypad battery pack in accordance with an exemplary embodiment of the present invention; [0029]FIG. 3A is a perspective view illustrating a rear surface of the mobile terminal having the keypad battery pack of FIG. 2, and FIG. 3B is an exploded perspective view illustrating the rear surface of the mobile terminal having the keypad battery pack of FIG. 2; [0030]FIG. 4A is a perspective view illustrating a front surface of a mobile terminal having a keypad battery pack in accordance with another exemplary embodiment of the present invention, and FIG. 4B is a perspective view illustrating a rear surface of the mobile terminal having the keypad battery pack of FIG. 4A; [0031]FIG. 5 is a perspective view illustrating a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack in accordance with another exemplary embodiment of the present invention; and [0032]FIG. 6 is a block diagram illustrating an internal configuration of a mobile terminal in accordance with another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0033]Exemplary embodiments of the present invention are described with reference to the accompanying drawings in detail. The same reference numbers are used throughout the drawings to refer to the same or like parts. Detailed descriptions of well-known functions and structures incorporated herein may be omitted to avoid obscuring the subject matter of the present invention. [0034]FIG. 1A is a perspective view illustrating an example of a keypad battery pack in accordance with an exemplary embodiment of the present invention, and FIG. 1B is a perspective view illustrating another example of a keypad battery pack in accordance with an exemplary embodiment of the present invention. [0035]As shown in FIGS. 1A and 1B, the keypad battery packs 10 and 20 of the present invention are characterized in that keypads 12 and22 are formed on typical battery packs having batteries (not shown) included therein. For example, the batteries include Lithium-ion (Li-ion) battery cells or Lithium-ion polymer battery cells. The present invention is not directly related to types or internal configurations of batteries and is not limited in this regard. [0036]The battery packs 10 and 20 have first surfaces 11a and 21a and second surfaces 11b and 21b, respectively, and the keypads 12 and 22 are formed on the first surfaces 11a and 12a of the battery packs 10 and 20, respectively. Although not shown in FIGS. 1A and 1B, battery terminals 15 (shown in FIG. 3B) are positioned on the second surfaces 11b and 21b of the battery packs 10 and 20. When the battery packs 10 and 20 are mounted on mobile terminals, the first surfaces 11a and 21a become outer surfaces and the second surfaces 11b and 21b become inner surfaces. [0037]The keypads 12 and 22 of the battery packs 10 and 20 may have a 3×4 key arrangement as shown in FIG. 1a, or a 5×4 key arrangement as shown in FIG. 1b. If required, the keypads 12 and 22 may include a search key (or a direction key). As such, the keypads 12 and 22 of the battery pack 10 and 20 may have different key arrangements and types. In other words, the present invention does not focus on specific types and arrangements of the keypads 12 and 22 of the battery packs 10 and 20. In the present invention, it is important that the keypads 12 and 22 are formed on the battery packs 10 and 20, and that various types and arrangements of the keypads 12 and 22 are applied. [0038]The keypad battery packs 10 and 20 of the present invention may further have a key scan control unit 18 (shown in FIG. 6). As described later, the key scan control unit 18 is electrically connected to the keypads 12 and 22 and the battery terminals 15, and recognizes a specific key input (i.e. which key is pressed) of the keypads 12 and 22. [0039]Hereinafter, a mobile terminal having the keypad battery pack of the present invention is described in detail through exemplary embodiments. [0040]FIG. 2 is a perspective view illustrating a front surface of a mobile terminal 100 having a keypad battery pack 10 in accordance with an exemplary embodiment of the present invention. FIG. 3A is a perspective view illustrating a rear surface 31b of the mobile terminal 100 having the keypad battery pack 10 of FIG. 2, and FIG. 3B is an exploded perspective view illustrating the rear surface 31b of the mobile terminal 100 having the keypad battery pack 10 of FIG. 2. [0041]As shown in FIGS. 2, 3A, and 3B, the mobile terminal 100 includes a terminal body 30 and the battery pack 10. The terminal body 30 has a front surface 31a and a rear surface 31b, and the battery pack 10 has an outer surface 11a and an inner surface 11b corresponding to the first surface 11a and the second surface 11b, respectively, of the battery pack 10 of FIG. 1a. The inner surface 11b of the battery pack 10 is contacted with the rear surface 31b of the terminal body 30, and the outer surface 11a of the battery pack 10 faces the same direction as the rear surface 31b of the terminal body 30. [0042]The front surface 31a of the terminal body 30 has a front display unit 33a and a front keypad 32, and the rear surface 31b of the terminal body 30 has a rear display unit 33b and a battery mounting area 34. The front display unit 33a and the rear display unit 33b may include Liquid Crystal Displays (LCDs). The front display unit 33a and the rear display unit 33b may be equal to or different from each other in size and resolution of a screen. The front keypad 32 shown in FIG. 2 includes a search key and a function key. As shown in FIG. 3B, the battery pack 10 is mounted on the battery mounting area 34, and the battery mounting area 34 has a typical configuration suitable for attaching and detaching the battery pack 10. A push button 36 or another fastening means may be formed at a portion of the battery mounting area for fastening the battery pack 10. [0043]The battery pack 10 is mounted on the battery mounting area 34 of the terminal body 30. The battery pack 10 has a rear keypad 12 formed on the outer surface 11a. The rear keypad 12 shown in FIG. 3A has a 3×4 key arrangement. As shown in FIG. 3B, the inner surface 11b of the battery pack 10 has the aforementioned battery terminal 15, and the battery mounting area 34 of the terminal body 30 has a charging terminal 35. When the battery pack 10 is mounted on the terminal body 30, the battery terminal 15 and the charging terminal 35 are electrically connected to each other by contact. The battery terminal 15 and the charging terminal 35 each have a serial communication terminal. A sill 16 may be formed at a portion of the battery pack 10 corresponding to the push button 36. [0044]A type of the front keypad 32 formed on the front surface 31a of the terminal body 30 is different from a type of the rear keypad 12 of the battery pack 10 mounted on the rear surface 31b of the terminal body 30. For example, as shown in FIGS. 2 and 3A, the front keypad 32 may include a search key, and the rear keypad 12 may have a 3*4 key arrangement. Alternatively, the front keypad 32 may include a search key, and the rear keypad may have a 5×4 key arrangement. Alternatively, the front keypad 32 may have a 3×4 or 5×4 key arrangement, and the rear keypad 12 may include a search key. [0045]As described above, in exemplary embodiments, different types of the front keypad 32 and the rear keypad 12 are arranged on the front surface and the rear surface of the mobile terminal 100. Keys are dispersed on both surfaces of the mobile terminal 100, which reduces a keypad occupation area, compared with a keypad arrangement formed only on one surface of a mobile terminal. In other words, an area available for a keypad is expanded to the rear surface of the mobile terminal 100, and thus the mobile terminal 100 has room for additional keys in a key arrangement space, thereby enabling easier addition of keys. [0046]Such an advantage allows an effective keypad arrangement in the mobile terminal 100 having various additional functions. For example, as shown in FIGS. 2 and 3A, the front surface 31a has the keypad 32 for performing a multimedia function, and the rear surface 31b has the keypad 12 for performing a basic function. By separating the front keypad 32 and the rear keypad 12 and arranging the keypads 32 and 12 on both surfaces of the mobile terminal 100, a key arrangement space of the mobile terminal 100 is effectively utilized and operation of the keypads is facilitated. Further, the keypad 32 for performing a multimedia function has a relatively small number of keys, and thus the size of the corresponding display unit 33a may be increased, thereby improving user satisfaction. [0047]The front surface and the rear surface of the mobile terminal of the present invention may be configured in a different manner to those of the above exemplary embodiment. FIG. 4A is a perspective view illustrating a front surface 131a of a mobile terminal 200 having a keypad battery pack 110 in accordance with another exemplary embodiment of the present invention, and FIG. 4B is a perspective view illustrating a rear surface 131b of the mobile terminal 200 having the keypad battery pack of 110FIG. 4A. [0048]As shown in FIG. 4A, the mobile terminal 200 of this exemplary embodiment includes a terminal body 130 having a front surface 131a with a front display 133a. However, the front surface 131a does not have a front keypad, compared with the above-mentioned exemplary embodiment. As shown in FIG. 4b, the terminal body 130 has a rear surface 131b with a rear display unit 133b, and a battery pack 110 is mounted on the rear surface 131b. The battery pack 110 has an outer surface 111a with a rear keypad 112. Because the front surface 131a of the terminal body 130 does not have a keypad, the rear keypad 112 has a typical configuration of a 3*4 key arrangement with a search key. [0049]As described above, the keypad 112 of the present invention may be formed only on the rear surface 131b of the mobile terminal 200. Accordingly, the front display unit 133a may be expanded to utilize the whole front surface 131a of the mobile terminal 200, and thus may be used as an exclusive display unit of a wide screen for receiving a digital broadcast, such as Digital Media Broadcasting (DMB). The front display 133a may be provided with a typical touch-screen function, and as shown in FIG. 4A, speakers 140a and 140b may be arranged at opposite sides of the front display unit 133a. [0050]Referring to FIGS. 2 and 3A, a key scan control unit (not shown) for recognizing a specific key input may be formed on the terminal body 30 only or on both the terminal body 30 and the battery pack 10. When the key scan control unit is formed on the terminal body 30 only, the terminal body 30 has a first key scan control unit and a second key scan control unit electrically connected to the front keypad 32 and the rear keypad 12, respectively. When the key scan control unit is formed on both the terminal body 30 and the battery pack 10, the terminal body 30 has a first key scan control unit electrically connected to the front keypad 32 and the battery pack 10 has a second key scan control unit electrically connected to the rear keypad 12. In the former case, the second key scan control unit is formed on the terminal body 30, and thus the terminal body 30 and the battery pack 10 may require additional terminals for electrically connecting the rear key pad 12 to the second key scan control unit. In the latter case, the second key scan control unit is formed on the battery pack 10, and thus a key input signal recognized by the key scan control unit may be transmitted to the terminal body 30 through a typical serial communication terminal. [0051]In particular, the mobile terminal 100 of the present invention may use different types of keypad battery packs. Referring to FIGS. 1A and 1B, the keypad battery packs 10 and 20 may be identical in battery type, overall shape and size, but may differ in type of the keypads 12 and 22. Accordingly, the mobile terminal 100 of the present invention may selectively mount the battery packs 10 and 20 having different types of keypads and use keys according to purpose. [0052]Hereinafter, a method for changing a keypad of a mobile terminal by replacing a keypad battery pack with a different keypad battery pack is described in detail through exemplary embodiments. [0053]Hereinafter, the keypad battery pack 10 shown in FIG. 1B is referred to as a first battery pack, and the keypad battery pack 20 shown in FIG. 1B is referred to as a second battery pack. Further, the keypad 32 of the terminal body 30 shown in FIG. 2 is referred to as a front keypad, the keypad 12 of the first battery pack 10 as a first keypad, and the keypad22 of the second battery pack 20 as a second keypad. [0054]FIG. 5 is a perspective view illustrating a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack in accordance with another exemplary embodiment of the present invention. [0055]Referring to FIGS. 2 and 5, when the first battery pack 10 and the second battery pack 20 are alternately mounted on the mobile terminal 100, the front keypad 32, the first keypad 12 and the second keypad 22 are different in types. For example, as shown in the drawings, the front keypad 32 includes a search key, the first keypad 12 has a 3×4 key arrangement, and the second keypad 22 has a 5×4 key arrangement. [0056]When the first battery pack 10 mounted on the mobile terminal 100 is replaced with the second battery pack 20, the first battery pack 10 is first removed from the battery mounting area 34. When the push button 36 of the terminal body 30 is pressed, the push button 36 fastened in the sill 16 of the first battery pack 10 is released to separate the first battery pack 10 from the battery mounting area 34. [0057]Next, the second battery pack 20 is mounted on the battery mounting area 34. When the second battery pack 20 is mounted such that a sill (not shown) of the second battery pack 20 is aligned with the push button 36, the second battery pack 20 is coupled to the terminal body 30. At the same time, a battery terminal (not shown) of the second battery pack 20 and the charging terminal 35 of the terminal body 30 are electrically connected to each other by contact. [0058]A coupling method of the terminal body 30 and the battery pack 20 includes a sliding method or an insertion method, and the present invention is not limited in this regard. [0059]Although the present invention uses three types of keypads 32, 12 and 22, the key scan control unit may be formed in two methods as described above. When the first key scan control unit and the second key scan control unit are both formed on the terminal body 30, a key input of the front keypad 32 is recognized by the first key scan control unit, and a key input of the first keypad 12 or of the second keypad 22, according to which keypad is mounted on the terminal body 30, is recognized by the second key scan control unit. When only the first key scan control unit is formed on the terminal body 30, a key input of the front keypad 32 is recognized by the first key scan control unit, the first battery pack 10 has a second key scan control unit for recognizing a key input of the first keypad 12, and the second battery pack 20 has a third key scan control unit for recognizing a key input of the second keypad 22. [0060]The above-mentioned method of the present invention may be applied to a mobile terminal in which a front surface has a front display unit but no a front keypad. [0061]FIG. 6 is a block diagram illustrating an internal configuration of a mobile terminal in accordance with another exemplary embodiment of the present invention. Referring to FIG. 6, as previously described, the mobile terminal 100 includes the terminal body 30 and the battery pack 10. [0062]The terminal body 30 includes a front keypad 32, a front display unit 33a, a rear display unit 33b, a charging terminal 35, a wireless communication unit 37, a control unit 38 having a first key scan control unit 38a, and a memory unit 39. The battery pack 10 includes a rear keypad 12, a battery terminal 15, a battery 17, and a second key scan control unit 18. Alternatively, the mobile terminal 100 may have only the rear keypad 12 without the front keypad 32. [0063]The front keypad 32 and the rear keypad 12 receive an operation signal of a user for controlling operation of the mobile terminal 100. The front keypad 32 outputs an input signal to the first key scan control unit 38a, and the rear keypad 12 outputs an input signal to the second key scan control unit 18. For example, the front keypad 32 performs a multimedia function, and the rear keypad 12 performs a basic function. [0064]The first key scan control unit 38a recognizes a specific key input of the front keypad 32, and the second key scan control unit 18 recognizes a specific key input of the rear key pad 12. In other words, each of the key scan control units 38a and 18 receives an input signal from the corresponding keypads 32 and 12 and recognizes which key is pressed. In particular, the second key scan control unit 18 recognizes a key input signal, and then outputs the signal to the control unit 38 through the battery terminal 15 and the charging terminal 35. Alternatively, the second key scan control unit 18 may be formed on the terminal body 30 instead of on the battery pack 10. [0065]The control unit 38 controls the whole operation of the mobile terminal 100. In particular, the control unit 38 receives a key input signal from the key scan control units 38a and 18, and controls a corresponding operation. [0066]The front display unit 33a and the rear display unit 33b display various information related to operation of the mobile terminal 100. The front and rear display units 33a and 33b may include LCDs, and their screens may have equal or different size and resolution. For example, when the front keypad 32 consists of only a search key and a function key for performing a multimedia function, a screen size of the front display unit 33a formed on the same surface as the front keypad 32 may be larger than that of the rear display unit 33b. In particular, when the mobile terminal does not have a front keypad, the front display unit 33a may have a size corresponding to that of an entire front surface of the terminal body 30. [0067]The wireless communication unit 37 performs a communication function, i.e. a basic function of the mobile terminal 100. The memory unit 39 stores various programs and data necessary for operation of the mobile terminal 100. [0068]The battery 17 supplies power necessary for operation of the mobile terminal 100, and may be a typical Lithium-ion battery cell. [0069]The charging terminal 35 and the battery terminal 15 are electrically connected to each other by contact. Each of the charging terminal 35 and the battery terminal 15 has positive/negative terminals for power supply and may further have a serial communication terminal for transmitting a key input signal. Alternatively, when the second key scan control unit 18 is formed on the terminal body 30, each of the charging terminal 35 and the battery terminal 15 may further have terminals for transmitting a key scan signal. [0070]As described above, the present invention forms a keypad on a rear surface as well as on a front surface of a mobile terminal, thereby expanding a keypad-placement area to the rear surface of the mobile terminal. Accordingly, keys are arranged on both surfaces of the mobile terminal, and thus the mobile terminal has room for additional keys in a key arrangement space, thereby enabling easer addition of keys. [0071]Further, when keypads are arranged on both surfaces of the mobile terminal, the present invention may effectively disperse the keypads according to function. For example, the present invention may separate a keypad for performing a basic function from a keypad for performing a multimedia function. This may enable effective space utilization and an easy operation of the keypad, thereby improving the convenience of a user. A display unit formed on the same surface as a keypad for performing a multimedia function may thus be expanded, thereby improving the satisfaction of a user. Accordingly, the present invention may provide a keypad structure suitable for a mobile terminal having an additional function such as a multimedia function. [0072]Further, the present invention may form a typical keypad and display unit on only a rear surface of a mobile terminal, on which a battery pack is mounted, and form another display unit on the entire front surface of the mobile terminal. Thus, the present invention may provide a structure of a mobile terminal suitable for an exclusive display unit having a wider screen for receiving a digital broadcast. [0073]Further, the mobile terminal of the present invention may selectively mount a plurality of battery packs having different keypad types and arrangements. Thus, the present invention may replace a keypad with a more suitable keypad according to purpose. [0074]Although exemplary embodiments of the present invention have been described in detail hereinabove, it should be understood that many variations and modifications of the basic inventive concept herein described, which may appear to those skilled in the art, will still fall within the spirit and scope of the exemplary embodiments of the present invention as defined in the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. 2006 年 6 月 28 日在韩国知识产权局提交的题为“KEYPAD BATTERY PACK, MOBILE TERMINAL AVAILABLE FOR DIFFERENT KEYPAD BATTERY PACKS, AND METHOD OF CHANGING KEYPAD OF MOBILE TERMINAL”的韩国专利申请§119(a) 美国专利号2006-0058861,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动终端,尤其涉及一种键盘电池组,一种可用于不同键盘电池组的移动终端,以及一种通过用不同的电池组更换电池组来更换移动终端的键盘的方法。 [0004] 2.相关技术的描述 [0005] 移动终端,例如手机和个人数字助理(PDA),已经得到了长足的发展,现在已经广泛应用于现代生活中。 随着移动终端的使用越来越普遍,用户的需求也越来越多样化。 因此,已经开发了移动终端以方便地提供更多功能。 例如,移动终端具备多媒体、无线互联网、数字广播收发等各种附加功能,以及通话、消息收发、个人信息管理等通用功能。 [0006] 移动终端通常具有小键盘作为用于接收用户输入的输入装置。 由于为移动终端提供了各种附加功能,因此将用于执行和控制附加功能的新键添加到典型的小键盘。 然而,移动终端具有有限的键盘放置区域,因此在有限的键盘放置区域上额外放置新键并不容易。 [0007] 同时,针对不同的国家、制造商或产品类型提供了各种键盘。 键盘的类型主要包括典型电话按键排列的3-×*4键和键盘的QWERTY按键排列的5×4键。 通常,在移动终端的制造过程中,键盘的按键排列方式是预先设定好的,因此之后的按键排列方式是无法改变的。 换言之,通常移动终端的小键盘具有固定的按键排列。 因此,如果具有特定按键排列(例如,3×4按键)的移动终端的用户想要更改为另一种按键排列(例如,5×4按键),则用户必须将移动终端更换为新的按键排列。 具有另一种按键排列的移动终端。 发明内容 [0008] 为了解决上述问题,本发明扩大了移动终端的键盘放置区域,从而能够更容易地添加按键。 [0009] 本发明还提供一种适用于具有各种附加功能的移动终端的键盘结构。 [0010] 本发明还提供一种用于交替使用具有不同按键排列的小键盘的移动终端和方法。 [0011] 本发明还提供了一种根据用途更换键盘的移动终端和方法。 [0012] 本发明进一步提高了移动终端用户的便利性和满意度。 [0013] 通常,键盘形成在移动终端的前表面上,而电池组形成在移动终端的后表面上。 本发明利用以前仅用作电池组安装区域的移动终端的后表面作为键盘放置区域。 [0014] 因此,本发明提供一种键盘电池组,即其上具有键盘的电池组。 本发明还提供一种用于交替安装不同类型的键盘电池组的移动终端。 本发明还提供一种通过用不同的电池组更换电池组来改变移动终端的键盘的方法。 [0015]根据本发明示例性实施例的移动终端包括具有前表面和后表面的终端主体、形成在前表面上的前显示单元、以及形成在后表面上的后显示单元和电池安装区域 ; 电池组,其内表面与终端主体的后表面接触,外表面与终端主体的后表面朝向相同的方向,并具有形成在外表面上的后键盘,其中安装有电池组 在终端本体的电池安装区域上与终端本体电连接。 [0016] 终端主体还可以包括形成在前表面上的前键盘。 端子主体还可以包括形成在电池安装区域上的充电端子,电池组还可以包括形成在内表面上的电池端子,其中充电端子和电池端子通过接触彼此电连接。 [0017] 前键盘的类型可以与后键盘的类型不同。 前小键盘和后小键盘中的至少一个可以具有3×4和5×4键排列之一,并且可以包括搜索键。 [0018] 终端主体还可以包括分别电连接到前键盘和后键盘的第一键扫描控制单元和第二键扫描控制单元,用于识别特定键输入。 或者,终端主体还可以包括第一键扫描控制单元,并且电池组还可以包括第二键扫描控制单元。 [0019] 充电端子和电池端子可以各自具有串行通信端子。 前显示单元的尺寸可以大于后显示单元的尺寸,并且前显示单元可以形成在终端主体的整个前表面上。 [0020] 根据本发明的另一实施例的移动终端包括具有前表面和后表面的终端主体、形成在前表面上的前显示单元、以及形成在后表面上的后显示单元和电池安装区域。 第一电池组具有安装在终端主体的电池安装区域上的内表面和外表面,使得内表面与终端主体的后表面接触以电连接到终端主体,并且具有第一 键盘形成在与终端主体后表面同向的外表面上; 第二电池组,具有内表面和外表面,并且具有形成在外表面上的第二键区,该第二键区的类型与第一键区的类型不同。 [0021] 终端主体还可以包括形成在前表面上的前键盘。 端子主体还可以包括形成在电池安装区域上的充电端子,并且第一电池组和第二电池组中的每一个还可以包括形成在其各自内表面上以电连接到充电端子的电池端子。 [0022] 前键盘的类型可以不同于第一键盘的类型和第二键盘的类型。 前小键盘可以包括搜索键,并且第一小键盘和第二小键盘中的一个具有3×4键排列,另一个具有5×4键排列。 第一小键盘和第二小键盘均可以包括搜索键,并且第一小键盘和第二小键盘中的一个具有3×4键排列,另一个具有5×4键排列。 [0023] 终端主体还可以包括与前键盘电连接的第一键扫描控制单元,用于识别特定键输入。 终端主体还可以包括第二键扫描控制单元,该第二键扫描控制单元电连接到第一键区或第二键区,用于识别特定键输入。 或者,第一电池组还可以包括与第一键区电连接以识别特定键输入的第二键扫描控制单元,并且第二电池组还包括与第二键区电连接以识别特定键输入的第三键扫描控制单元。 特定的键输入。 [0024]充电端子和电池端子可以各自具有串行通信端子。 前显示单元的尺寸可以大于后显示单元的尺寸,并且前显示单元可以形成在终端主体的整个前表面上。 [0025] 根据本发明的另一示例性实施例,一种用于更换具有终端主体的移动终端的键盘的方法,终端主体具有带有前显示单元的前表面和带有后显示单元和电池安装区域的后表面,第一电池 安装在电池安装区域上并具有外表面的第二电池组和第二电池组,第二电池组的外表面具有与第一键盘的类型不同的类型的第二键盘,包括移除第一电池组 从电池安装区域; 将第二个电池组安装在电池安装区。 附图的简要说明 [0026] 本发明的目的、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0027] 如图。 附图说明图1A是示出根据本发明示例性实施例的键盘电池组的示例的透视图。 图1B是示出根据本发明示例性实施例的键盘电池组的另一个示例的透视图; [0028] 如图。 图2是示出根据本发明示例性实施例的具有键盘电池组的移动终端的前表面的透视图; [0029] 如图。 图3A是示出具有图1的键盘电池组的移动终端的后表面的透视图。 2,和图。 图3B是示出具有图1的键盘电池组的移动终端的后表面的分解透视图。 2; [0030] 如图。 图4A是示出了根据本发明另一示例性实施例的具有键盘电池组的移动终端的前表面的透视图。 图4B是示出具有图3的键盘电池组的移动终端的后表面的透视图。 4A; [0031] 如图。 图5是示出根据本发明另一示例性实施例的通过用不同的电池组更换电池组来改变移动终端的键盘的方法的透视图; 和 [0032] 如图。 图6是示出根据本发明另一示例性实施例的移动终端的内部配置的框图。 示例性实施例的详细描述 [0033] 参考附图详细描述了本发明的示例性实施例。 贯穿附图使用相同的参考数字来指代相同或相似的部分。 为了避免混淆本发明的主题,可以省略这里并入的众所周知的功能和结构的详细描述。 [0034] 如图。 附图说明图1A是示出根据本发明示例性实施例的键盘电池组的示例的透视图。 图1B是示出根据本发明示例性实施例的键盘电池组的另一示例的透视图。 [0035] 如图所示。 1A和1B,键盘电池组 10 和 20 本发明的特征在于键盘 12 和 22 形成在其中包括电池(未示出)的典型电池组上。 例如,电池包括锂离子(Li-ion)电池或锂离子聚合物电池。 本发明与电池的类型或内部配置没有直接关系,并且在这方面不受限制。 [0036] 电池组 10 和 20 有第一个表面 11 a 和 21 a 和第二个表面 11 b 和 21 b, 分别和键盘 12 和 22 形成在第一表面上 11 a 和 12 a 电池组10 和 20 , 分别。 虽然未在图 5 中显示。 1A和1B,电池端子 15 (如图3B所示)位于第二表面上 11 b 和 21 b 电池组 10 和 20 . 当电池组 10 和 20 安装在移动终端上,第一表面 11 a 和 21 a 成为外表面和第二表面 11 b 和 21 b 变成内表面。 [0037] 键盘 12 和 22 电池组 10 和 20 可以具有如图3所示的3×4键布置。 1 a, 或如图 3 所示的 5×4 键排列。 1 b. 如果需要,键盘 12 和 22 可能包括搜索键(或方向键)。 因此,键盘 12 和 22 电池组的 10 和 20 可能有不同的键排列和类型。 换言之,本发明不专注于键盘的特定类型和布置 12 和 22 电池组 10 和 20 . 在本发明中,重要的是小键盘 12 和 22 形成在电池组上 10 和 20 ,以及各种类型和排列的键盘 12 和 22 被应用。 [0038] 键盘电池组 10 和 20 本发明还可以具有键扫描控制单元 18 (如图 6 所示)。 如后所述,键扫描控制单元 18 电连接到键盘 12 和 22 和电池端子 15 , 并识别键盘的特定键输入(即按下哪个键) 12 和 22 . [0039] 在下文中,通过示例性实施例详细描述具有本发明的键盘电池组的移动终端。 [0040] 如图。 图2是示出移动终端的前表面的透视图 100 有一个键盘电池组 10 根据本发明的示例性实施例。 如图。 图3A是表示背面的立体图 31 b 移动终端的 100 有键盘电池组 10 图。 2,和图。 图3B是表示背面的分解立体图 31 b 移动终端的 100 有键盘电池组 10 图。 2. [0041] 如图所示。 2、 3 一个,和 3 B、移动端 100 包括一个终端体 30 和电池组 10 . 终端机身 30 有一个前表面 31 a 和后表面 31 b, 和电池组 10 有一个外表面 11 a 和一个内表面 11 b 对应于第一个表面 11 a 和第二个表面 11 b, 分别是电池组 10 图。 1 a. 内表面 11 b 电池组的 10 与后表面接触 31 b 终端体的 30 , 和外表面 11 a 电池组的 10 面向与背面相同的方向 31 b 终端体的 30 . [0042] 前表面 31 a 终端体的 30 有一个前置显示单元 33 a 和一个前键盘 32 , 和后表面 31 b 终端体的 30 有一个后显示单元 33 b 和电池安装区 34 . 前显示单元 33 a 和后显示单元 33 b 可能包括液晶显示器 (LCD)。 前显示单元 33 a 和后显示单元 33 b 屏幕的大小和分辨率可以相同或不同。 前键盘 32如图所示。 图2包括搜索键和功能键。 如图所示。 3B、电池组 10 安装在电池安装区域 34 , 和电池安装区域 34 具有适合连接和拆卸电池组的典型配置 10 . 一个按钮 36 或者可以在电池安装区域的一部分处形成其他紧固装置,用于紧固电池组 10 . [0043] 电池组 10 安装在电池安装区域 34 终端体的 30 . 电池组 10 有一个后键盘 12 形成在外表面上 11 a. 后键盘 12 如图所示。 图3A具有3×4键布置。 如图所示。 3B、内表面 11 b 电池组的 10 具有上述电池端子 15 , 和电池安装区域 34 终端体的 30 有充电终端 35 . 当电池组 10 安装在终端机体上 30 , 电池端子 15 和充电终端 35 通过接触彼此电连接。 电池端子 15 和充电终端 35 每个都有一个串行通讯终端。 窗台 16 可以形成在电池组的一部分 10 对应于按钮 36 . [0044] A型前键盘 32 形成于前表面 31 a 终端体的 30 不同于一种类型的后键盘 12 电池组的 10 安装在背面 31 b 终端体的 30 . 例如,如图所示。 2和3A,前键盘 32 可能包括搜索键和后键盘 12 可能有 3*4 的按键排列。 或者,前键盘 32 可以包括搜索键,并且后键盘可以具有 5×4 键排列。 或者,前键盘 32 可能有 3×4 或 5×4 按键排列,后键盘 12 可能包括搜索关键字。 [0045] 如上所述,在示例性实施例中,不同类型的前键盘 32 和后键盘 12 设置在移动终端的正面和背面 100 . 按键分散在移动终端的两面 100 ,与仅形成在移动终端的一个表面上的键盘布置相比,减小了键盘占用面积。 换言之,可用于键盘的区域被扩展到移动终端的背面 100 ,因此移动终端 100 在按键布置空间中具有额外按键的空间,从而可以更轻松地添加按键。 [0046] 这样的优点允许在移动终端中有效的键盘布置 100 具有各种附加功能。 例如,如图所示。 2和3A,前表面 31 a 有键盘 32 用于执行多媒体功能,以及背面 31 b 有键盘 12 用于执行基本功能。 通过分离前键盘 32 和后键盘 12 并安排键盘 32 和 12 在移动终端的两个表面上 100 ,移动终端的按键排列空间 100 有效利用,方便了键盘的操作。 此外,键盘 32 用于执行多媒体功能的按键数量相对较少,因此相应的显示单元的大小 33 a 可以增加,从而提高用户满意度。 [0047] 本发明的移动终端的前表面和后表面可以以与上述示例性实施例不同的方式配置。 如图。 图4A是表示正面的立体图 131 a 移动终端的 200 有一个键盘电池组 110 根据本发明的另一个示例性实施例,以及 图4B是表示背面的立体图 131b 移动终端的 200 有键盘电池组 110 如图。 4A。 [0048] 如图所示。 4A、移动终端 200 该示例性实施例的包括终端主体 130 具有前表面 131 a 带前置显示屏 133 a. 然而,前表面 131 a 与上述示例性实施例相比,没有前键盘。 如图所示。 4 b, 终端体 130 有一个后表面 131 b 带后显示单元 133 b, 和一个电池组 110 安装在背面 131 b. 电池组 110 有一个外表面 111 a 带后键盘 112 . 因为正面 131 a 终端体的 130 没有键盘,后键盘 112 具有 3*4 键排列和搜索键的典型配置。 [0049] 如上所述,键盘 112 本发明的可仅在后表面上形成 131 b 移动终端的 200 . 因此,前显示单元 133 a 可以扩展以利用整个前表面 131 a 移动终端的 200 ,因此可以用作宽屏幕的专用显示单元,用于接收数字广播,例如数字媒体广播(DMB)。 前显示器 133 a 可以具有典型的触摸屏功能,如图1所示。 4A、扬声器 140 a 和 140 b 可以布置在前显示单元的相对两侧 133 a. [0050] 参考图。 参照图2和3A,用于识别特定键输入的键扫描控制单元(未示出)可以形成在终端主体上 30 仅在终端主体上或在两个终端主体上 30 和电池组 10 . 当键扫描控制单元形成在终端机体上时 30 只是,终端体 30 具有一第一按键扫描控制单元及一第二按键扫描控制单元电性连接至前键盘 32 和后键盘 12 , 分别。 当键扫描控制单元形成在两个终端机身上时 30 和电池组 10 , 终端体 30 具有一第一按键扫描控制单元,电性连接前键盘 32 和电池组 10 具有一第二按键扫描控制单元,电性连接后键盘 12 . 在前一种情况下,第二键扫描控制单元形成在终端主体上 30 ,因此终端体 30 和电池组 10 可能需要额外的端子来电连接后键盘 12 到第二键扫描控制单元。 在后一种情况下,第二键扫描控制单元形成在电池组上 10 ,因此可以将键扫描控制单元识别的键输入信号传输到终端主体 30 通过一个典型的串行通信终端。 [0051] 尤其是移动终端 100 本发明的实施例可以使用不同类型的键盘电池组。 参考图。 1A和1B,键盘电池组 10 和 20 电池类型、整体形状和尺寸可能相同,但键盘类型可能不同 12 和 22 . 因此,移动终端 100 本发明可以选择性地安装电池组 10 和 20 具有不同类型的键盘并根据用途使用按键。 [0052] 在下文中,通过示例性实施例详细描述通过用不同的键盘电池组更换键盘电池组来改变移动终端的键盘的方法。 [0053] 以下,键盘电池组 10 如图所示。 图1B称为第一电池组,键盘电池组 20 如图所示。 图1B的电池组被称为第二电池组。 此外,键盘 32 终端体的 30 如图所示。 2被称为前键盘,键盘12 第一个电池组 10 作为第一个键盘,和键盘 22 第二个电池组 20 作为第二个键盘。 [0054] 如图。 图5是示出根据本发明另一示例性实施例的通过用不同的电池组更换电池组来改变移动终端的键盘的方法的透视图。 [0055] 参考图。 2和5,当第一个电池组 10 和第二个电池组 20 交替安装在移动终端上 100 , 前键盘 32 , 第一个键盘 12 和第二个键盘 22 类型不同。 例如,如图所示,前键盘 32 包括一个搜索键,第一个键盘 12 有一个 3×4 按键排列,第二个键盘 22 有一个 5×4 键排列。 [0056] 当第一个电池组 10 安装在移动终端上 100 更换为第二个电池组 20 ,第一个电池组 10 首先从电池安装区域移除 34 . 当按下按钮 36 终端体的 30 被按下,按钮 36 固定在窗台上 16 第一个电池组 10 被释放以分离第一个电池组 10 从电池安装区域 34 . [0057] 接下来,第二个电池组 20 安装在电池安装区域 34 . 当第二个电池组 20 安装成使得第二电池组的窗台(未示出) 20 与按钮对齐 36 ,第二个电池组 20 耦合到终端机体 30 . 同时,第二电池组的电池端子(未图示) 20 和充电终端 35 终端体的 30 通过接触彼此电连接。 [0058] 一种端子体的耦合方法 30 和电池组 20 包括滑动方式或插入方式,本发明不以此为限。 [0059] 尽管本发明使用三种类型的键盘 32 , 12 和 22 ,键扫描控制单元可以以如上所述的两种方法形成。 当第一按键扫描控制单元和第二按键扫描控制单元均形成在终端机体上时 30 , 前键盘的一键输入 32 被第一按键扫描控制单元识别,并且第一键盘的按键输入 12 或第二个键盘 22 ,根据哪个键盘安装在终端机身上 30 ,由第二键扫描控制单元识别。 当终端主体上仅形成第一键扫描控制单元时 30 , 前键盘的一键输入 32 被第一个按键扫描控制单元识别,第一个电池组 10 具有第二键扫描控制单元,用于识别第一键盘的键输入 12 , 和第二个电池组 20 具有第三键扫描控制单元,用于识别第二键盘的键输入 22 . [0060] 本发明的上述方法可以应用于前表面具有前显示单元但没有前键盘的移动终端。 [0061] 如图。 图6是示出根据本发明另一示例性实施例的移动终端的内部配置的框图。 参考图。 参照图6,如前所述,移动终端 100 包括终端体 30 和电池组 10 . [0062] 终端本体 30 包括一个前键盘 32 , 一个前置显示单元 33 a, 后显示单元 33 b, 一个充电终端 35 , 一个无线通信单元 37 , 一个控制单元 38 具有第一键扫描控制单元 38 a, 和一个内存单元 39 . 电池组 10 包括一个后键盘 12 , 一个电池端子 15 , 一个电池 17,以及第二键扫描控制单元 18 . 或者,移动终端 100 可能只有后键盘 12 没有前键盘 32 . [0063] 前键盘 32 和后键盘 12 接收用户的操作信号,用于控制移动终端的操作 100 . 前键盘 32 向第一键扫描控制单元输出输入信号 38 a, 和后键盘 12 向第二键扫描控制单元输出输入信号 18 . 例如,前键盘 32 执行多媒体功能,后键盘 12 执行基本功能。 [0064] 第一键扫描控制单元 38 a 识别前键盘的特定键输入 32 ,以及第二键扫描控制单元 18 识别后键盘的特定键输入 12 . 换言之,每个键扫描控制单元 38 a 和 18 从相应的键盘接收输入信号 32 和 12 并识别按下了哪个键。 特别地,第二键扫描控制单元 18 识别按键输入信号,然后将信号输出到控制单元 38 通过电池端子 15 和充电终端 35 . 或者,第二键扫描控制单元 18 可以形成在终端本体上 30 而不是在电池组上 10 . [0065] 控制单元 38 控制移动端的整体操作 100 . 特别是控制单元 38 从按键扫描控制单元接收按键输入信号 38 a 和 18 , 并控制相应的操作。 [0066] 前显示单元 33 a 和后显示单元 33 b 显示与移动终端操作相关的各种信息 100 . 前后显示单元 33 a 和 33 b 可能包括 LCD,它们的屏幕可能具有相同或不同的尺寸和分辨率。 例如,当正面键盘 32 仅由一个搜索键和一个用于执行多媒体功能的功能键组成,前显示单元的屏幕尺寸 33 a 形成在与前键盘相同的表面上 32 可能大于后置显示单元 33 b. 特别地,当移动终端没有前置键盘时,前置显示单元 33 a 可以具有与终端主体的整个前表面的尺寸相对应的尺寸 30 . [0067] 无线通信单元 37 执行通信功能,即移动终端的基本功能 100 . 记忆单元 39 存储移动终端操作所需的各种程序和数据 100 . [0068] 电池 17 提供移动终端运行所需的电源 100 ,并且可能是典型的锂离子电池。 [0069] 充电终端 35 和电池端子 15 通过接触彼此电连接。 每个充电端子 35 和电池端子 15 具有用于供电的正/负端子,还可以具有用于传输按键输入信号的串行通信端子。 或者,当第二键扫描控制单元 18 形成在端子本体上 30 , 每个充电端 35 和电池端子 15 还可以具有用于发送键扫描信号的端子。 [0070] 如上所述,本发明在移动终端的后表面以及前表面上形成小键盘,从而将小键盘放置区域扩展到移动终端的后表面。 相应地,在移动终端的两个表面上都布置了按键,因此移动终端在按键布置空间中具有用于额外按键的空间,从而能够更容易地添加按键。 [0071]此外,当键盘布置在移动终端的两个表面上时,本发明可以根据功能有效地分散键盘。 例如,本发明可以将用于执行基本功能的小键盘与用于执行多媒体功能的小键盘分开。 这可以实现有效的空间利用和键盘的简单操作,从而提高用户的便利性。 因此可以扩展形成在与用于执行多媒体功能的小键盘相同的表面上的显示单元,从而提高用户的满意度。 因此,本发明可以提供一种适用于具有诸如多媒体功能的附加功能的移动终端的小键盘结构。 [0072] 此外,本发明可以仅在其上安装有电池组的移动终端的后表面上形成典型的小键盘和显示单元,并且在移动终端的整个前表面上形成另一个显示单元。 因此,本发明可以提供一种适用于具有更宽屏幕的专用显示单元的移动终端结构,用于接收数字广播。 [0073] 此外,本发明的移动终端可以选择性地安装具有不同键盘类型和布置的多个电池组。 因此,本发明可以根据目的用更合适的小键盘代替小键盘。 [0074] 尽管上文已经详细描述了本发明的示例性实施例,但应当理解,对于本领域技术人员来说可能出现的本文描述的基本发明概念的许多变化和修改仍将落入本发明的精神和范围内。 如在所附权利要求中定义的本发明的示例性实施例。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101098534A(String), EP1874008A1(String), KR100757232B1(String), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101098534A(String), EP1874008A1(String), KR100757232B1(String), US20080004085A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101098534A(String), EP1874008A1(String), KR100757232B1(String), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), CN101098534A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), EP1874008A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), KR100757232B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.394 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.394 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20080004085A1(String), US20080004085A1(String), 1199289600(Integer), 270644(Integer), 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.406 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.407 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.407 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184961(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184961(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184961(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184961(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.452 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.452 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.475 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and composite photographing method using multiple mobile terminals(String), 移动终端和使用多个移动终端的合成拍摄方法(String), US20100004020A1(String), A mobile terminal and composite photographing method using multiple mobile terminals are provided. The composite photographing method uses multiple mobile terminals. A master mobile terminal composes an incomplete composite photograph, generates a participant list of slave mobile terminals, and sends the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list. The first slave mobile terminal receives the incomplete composite photograph and participant list, further composes the received composite photograph, determines whether the composed composite photograph is complete, sends, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list, and sends, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing. Hence, several users at distinct locations can jointly produce a composite photograph.(String), 提供了一种移动终端和使用多个移动终端的合成拍摄方法。 复合拍摄方法使用多个移动终端。 主移动终端对不完整的合成照片进行合成,生成从移动终端的参与者列表,并将不完整的合成照片和参与者列表发送给参与者列表中的第一从移动终端。 第一从移动终端接收到不完整的合成照片和参与者列表,进一步对接收到的合成照片进行合成,判断合成的合成照片是否完整,当合成的合成照片不完整时,将合成的合成照片发送给第二从移动终端 在参与者列表中,当合成的合成照片完成后,将合成的合成照片发送给所有参与合成拍摄的移动终端。 因此,不同位置的几个用户可以共同产生合成照片。(String), US12/496149(String), 1246377600(Integer), US20100004020A1(String), 1262793600(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 20(Integer), US20030236830A1 | US20040131278A1 | US20060078173A1 | US20060204032A1 | US20070146798A1 | US20070188626A1 | US20070263995A1 | US20090128644A1 | US20090136225A1 | US20090254572A1 | US20090322788A1 | US20110116679A1 | US5953050A | US6005987A | US6388654B1 | US6900904B1 | US7391910B2 | US7627311B2 | US7734116B2 | US7889381B2(String), 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184962(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\08effeadba7145e0b878acd2462267ee.png(String), 184962(Integer), 08effeadba7145e0b878acd2462267ee.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and composite photographing method using multiple mobile terminals(String), 移动终端和使用多个移动终端的合成拍摄方法(String), US20100004020A1(String), A mobile terminal and composite photographing method using multiple mobile terminals are provided. The composite photographing method uses multiple mobile terminals. A master mobile terminal composes an incomplete composite photograph, generates a participant list of slave mobile terminals, and sends the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list. The first slave mobile terminal receives the incomplete composite photograph and participant list, further composes the received composite photograph, determines whether the composed composite photograph is complete, sends, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list, and sends, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing. Hence, several users at distinct locations can jointly produce a composite photograph.(String), 提供了一种移动终端和使用多个移动终端的合成拍摄方法。 复合拍摄方法使用多个移动终端。 主移动终端对不完整的合成照片进行合成,生成从移动终端的参与者列表,并将不完整的合成照片和参与者列表发送给参与者列表中的第一从移动终端。 第一从移动终端接收到不完整的合成照片和参与者列表,进一步对接收到的合成照片进行合成,判断合成的合成照片是否完整,当合成的合成照片不完整时,将合成的合成照片发送给第二从移动终端 在参与者列表中,当合成的合成照片完成后,将合成的合成照片发送给所有参与合成拍摄的移动终端。 因此,不同位置的几个用户可以共同产生合成照片。(String), US12/496149(String), 1246377600(Integer), US20100004020A1(String), 1262793600(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 20(Integer), US20030236830A1 | US20040131278A1 | US20060078173A1 | US20060204032A1 | US20070146798A1 | US20070188626A1 | US20070263995A1 | US20090128644A1 | US20090136225A1 | US20090254572A1 | US20090322788A1 | US20110116679A1 | US5953050A | US6005987A | US6388654B1 | US6900904B1 | US7391910B2 | US7627311B2 | US7734116B2 | US7889381B2(String), \20230420\08effeadba7145e0b878acd2462267ee.png(String), 22(Integer), 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 1. A composite photographing method using multiple mobile terminals, the method comprising:composing, by a master mobile terminal, an incomplete composite photograph;generating, by a master mobile terminal, a participant list of slave mobile terminals;sending, by the master mobile terminal, the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list;receiving, by the first slave mobile terminal, the incomplete composite photograph and participant list;further composing, by the first slave mobile terminal, the received composite photograph;determining, by the first slave mobile terminal, whether the composed composite photograph is complete;sending, by the first slave mobile terminal, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list; andsending, when the composed composite photograph is complete, by the first slave mobile terminal, the composed composite photograph to all mobile terminals having participated in composite photographing.(String), 1.一种使用多个移动终端的合成拍摄方法,该方法包括:主控移动终端合成一张不完整的合成照片;主移动终端生成从移动终端的参与者列表;主移动终端将不完整合成照片和参会名单发送给参会名单中的第一从移动终端;第一从移动终端接收不完整合成照片和参会人员名单;第一从移动终端对接收到的合成照片进行进一步合成;第一从移动终端判断合成的合成照片是否完整;第一从移动终端在合成合成照片不完整时,将合成合成照片发送给参会者列表中的第二从移动终端;和第一从移动终端在完成合成照片后,将合成照片发送给所有参与合成的移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 2. The method of claim 1, wherein a mobile terminal in a composite shot mode one of composes and further composes a composite photograph by inserting a taken picture into at least one photo-section of the composite photograph.(String), 2.如权利要求1所述的方法,其中移动终端在合成照片模式之一中通过将拍摄的照片插入合成照片的至少一个照片部分来合成并进一步合成合成照片。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 3. The method of claim 2, wherein the second slave mobile terminal comprises a mobile terminal in the participant list that has not yet participated in composite photographing.(String), 3.如权利要求2所述的方法,其中第二从移动终端包括参与列表中尚未参与合影的移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 4. The method of claim 2, wherein each of the mobile terminals participating in composite photographing belongs to the participant list.(String), 4.如权利要求2所述的方法,其中每个参与合影的移动终端都属于参与列表。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 5. The method of claim 1, wherein transmission of a composite photograph is performed through one of a radio frequency module and a short-range wireless module.(String), 5.如权利要求1所述的方法,其中合成照片的传输通过射频模块和近距离无线模块之一进行。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 6. A composite photographing method using multiple mobile terminals, the method comprising:composing, by a master mobile terminal, an incomplete composite photograph;generating, by the master mobile terminal, a participant list of one or more slave mobile terminals;setting, by the master mobile terminal, photo-section information for the slave mobile terminals;sending, by the master mobile terminal, the incomplete composite photograph and photo-section information to slave mobile terminals in the participant list;receiving, by each of the slave mobile terminals, the incomplete composite photograph and photo-section information;further composing, by each of the slave mobile terminals, the received composite photograph utilizing the photo-section information;sending, by each of the slave mobile terminals, the composed composite photograph to the master mobile terminal; andcombining, by the master mobile terminal, the incomplete composite photographs received from the slave mobile terminals together into a complete composite photograph.(String), 6.一种使用多个移动终端的合成拍摄方法,该方法包括:主控移动终端合成一张不完整的合成照片;主移动终端生成一个或多个从移动终端的参与者列表;主移动终端为从移动终端设置照片切片信息;主移动终端向参会名单中的从移动终端发送不完整的合成照片和照片切片信息;各从属移动终端接收不完整合成照片和照片切面信息;各从属移动终端将接收到的合成照片进一步利用照片切面信息进行合成;各从移动终端将合成后的合成照片发送给主移动终端;和主移动终端将从从移动终端接收到的不完整合成照片组合成一张完整合成照片。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 7. The method of claim 6, wherein a mobile terminal in a composite shot mode one of composes and further composes a composite photograph by inserting a taken picture into at least one photo-section of the composite photograph based on the photo-section information.(String), 7.如权利要求6所述的方法,其中移动终端在合成照片模式下,根据照片断面信息,将拍摄的照片插入到合成照片的至少一个照片断面中,合成并进一步合成一张合成照片。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 8. The method of claim 7, further comprising sending, by the master mobile terminal, the complete composite photograph to all mobile terminals participating in composite photographing.(String), 8.如权利要求7所述的方法,还包括主控移动终端将完整的合成照片发送给所有参与合成的移动终端。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 9. The method of claim 7, wherein the incomplete composite photographs from the slave mobile terminals to the master mobile terminal are one of a first type composite photograph including both an image selected in composite shot mode and a taken picture, a second type composite photograph including only a taken picture, and a third type composite photograph including a taken picture and associated photo-section indicator in a selected image.(String), 9.如权利要求7所述的方法,其中从移动终端到主移动终端的不完整合成照片为:第一类合成照片,包括合成拍摄模式下选择的图像和拍摄的照片;第二类合成照片,仅包括拍摄照片;第三类合成照片。类型合成照片,包括所选图像中的拍摄照片和相关照片部分指示符。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 10. The method of claim 9, wherein the incomplete composite photograph from the master mobile terminal to the slave mobile terminals comprises a composite photograph whose photo-section assigned to the master mobile terminal is one of empty and filled with a taken picture.(String), 10.如权利要求9所述的方法,其中主移动终端向从移动终端发送的不完整合成照片包括分配给主移动终端的照片部分为空填充照片的合成照片。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 11. The method of claim 6, wherein transmission of a composite photograph is performed through one of a radio frequency module and a short-range wireless module.(String), 11.如权利要求6所述的方法,其中合成照片的传输通过射频模块和近距离无线模块之一进行。(String), 1(Integer), 10(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 12. A mobile terminal comprising:an input unit for composing a composite photograph and for generating a participant list;a communication unit for transmitting a composite photograph and the participant list; anda control unit for sending a composed incomplete composite photograph and the participant list to a first mobile terminal in the participant list, for further composing, upon reception of an incomplete composite photograph, the received composite photograph, for sending, when the composed composite photograph is incomplete, the composed composite photograph to a second mobile terminal in the participant list, and for sending, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing.(String), 12.移动终端包括:输入单元,用于合成照片和生成参与者列表;用于传输合成照片和参与者列表的通信单元;和控制单元,用于将合成的不完整合成照片和参会者名单发送至参会者列表中的第一移动终端,用于在接收到不完整合成照片后,将接收到的合成照片进一步合成,用于发送,当合成的合成照片为不完整时,将合成后的合成照片发送给参与列表中的第二个移动终端,当合成后的合成照片完成时,将合成后的合成照片发送给所有参与合成的移动终端。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 13. The mobile terminal of claim 12, wherein the input unit comprises:a camera unit for composing a composite photograph in a composite shot mode by taking a picture and inserting the picture into at least one photo-section of the composite photograph; anda key input unit for generating the participant list.(String), 13.如权利要求12所述的移动终端,其中输入单元包括:相机单元,用于通过拍摄一张照片并将该照片插入到合成照片的至少一个照片区中,以合成拍摄模式合成合成照片;和用于生成参与者列表的键输入单元。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 14. The mobile terminal of claim 13, wherein the second mobile terminal comprises a mobile terminal in the participant list that has not yet participated in composite photographing.(String), 14.如权利要求13所述的移动终端,其中第二移动终端包括参与列表中尚未参与合影的移动终端。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 15. The mobile terminal of claim 13, wherein each of the mobile terminals participating in composite photographing belongs to the participant list.(String), 15.如权利要求13所述的移动终端,其中每个参与合影的移动终端都属于参与列表。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 16. The mobile terminal of claim 12, wherein the communication unit comprises one of a radio frequency module and a short-range wireless module.(String), 16.如权利要求12所述的移动终端,其中通信单元包括射频模块和近距离无线模块之一。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 17. A mobile terminal comprising:an input unit for composing a composite photograph, for generating a participant list, and for setting photo-section information assigning photo-sections of a composite photograph to different mobile terminals in the participant list;a communication unit for transmitting a composite photograph and the photo-section information; anda control unit for sending an incomplete composite photograph and the photo-section information to one or more mobile terminals in the participant list, for further composing, upon reception of an incomplete composite photograph from a first mobile terminal, the received composite photograph, for sending the composed composite photograph to the first mobile terminal, and for combining, upon reception of incomplete composite photographs matching with the incomplete composite photograph having been sent, the received incomplete composite photographs into a complete composite photograph.(String), 17.移动终端包括:合成照片输入单元,生成参会名单,并设置参会名单中不同移动终端分配合成照片照片分片的照片分片信息;传输合成照片和照片切片信息的通信单元;和控制单元,用于向参加者列表中的一个或多个移动终端发送不完整合成照片和照片切片信息,用于进一步合成,在接收到来自第一移动终端的不完整合成照片后,接收到的合成照片,用于发送将合成后的合成照片发送给第一移动终端,用于在接收到与已发送的不完整合成照片匹配的不完整合成照片时,将接收到的不完整合成照片合成为完整合成照片。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 18. The mobile terminal of claim 17, wherein the input unit comprises:a camera unit for composing a composite photograph in a composite shot mode by taking a picture and inserting the picture into at least one photo-section of the composite photograph; anda key input unit for generating the participant list and for setting the photo-section information.(String), 18.如权利要求17所述的移动终端,其中输入单元包括:相机单元,用于通过拍摄一张照片并将该照片插入到合成照片的至少一个照片区中,以合成拍摄模式合成合成照片;和按键输入单元,用于生成与会者名单和设置照片切片信息。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 19. The mobile terminal of claim 18, wherein the control unit sends the complete composite photograph to all mobile terminals participating in composite photographing.(String), 19.如权利要求18所述的移动终端,其中控制单元将完整的合成照片发送给所有参与合成的移动终端。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 20. The mobile terminal of claim 18, wherein the incomplete composite photograph sent to the first mobile terminal comprises one of a first type composite photograph including both an image selected in composite shot mode and a taken picture, a second type composite photograph including only a taken picture, and a third type composite photograph including a taken picture and associated photo-section indicator in a selected image.(String), 20.如权利要求18所述的移动终端,其中发送给第一移动终端的不完整合成照片包括:第一类合成照片,包括合成拍摄模式下选择的图像和拍摄的照片;第二类合成照片,仅包括拍摄照片;第三类合成照片,包括所选图像中的已拍摄照片和相关照片部分指示器。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 21. The mobile terminal of claim 20, wherein the incomplete composite photograph sent to mobile terminals in the participant list comprises a composite photograph whose photo-section is one of empty and filled with a taken picture.(String), 21.如权利要求20所述的移动终端,其中与会者列表中发送至移动终端的不完整合成照片包括照片部分为空白且填充有拍摄照片的合成照片。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184962(Integer), 22. The mobile terminal of claim 17, wherein the communication unit comprises one of a radio frequency module and a short-range wireless module.(String), 22.如权利要求17所述的移动终端,其中通信单元包括射频模块和近距离无线模块之一。(String), 1(Integer), 21(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184962(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. § 119(a) of a Korean patent application filed in the Korean Intellectual Property Office on Jul. 2, 2008 and assigned Serial No. 10-2008-0063874, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal. More particularly, the present invention relates to a mobile terminal and composite photographing method using multiple mobile terminals wherein multiple mobile terminals at distinct locations can jointly produce a composite photograph. [0004]2. Description of the Related Art [0005]With electronic components becoming smaller and lighter, modern mobile terminals are becoming increasingly miniaturized. In addition to basic call-handling functions, to satisfy diverse user needs, commercially available mobile terminals have various advanced features including camera-related functions. [0006]A camera-equipped mobile terminal can provide various shot modes including still shot, continuous shot, composite shot, night shot, self-shot, and video shot. More particularly in a composite shot, several pictures are taken and combined into a single composite photograph. Here, multiple pictures are taken by the same mobile terminal. That is, a single mobile terminal can be used to produce a composite photograph. To produce a composite photograph composed of pictures of several persons, these persons may have to be present at the same place and time. [0007]In composite shot mode, a multi-photo framing feature can be used to produce a photograph from multiple separately taken pictures. To use the multi-photo framing feature, these pictures have to be taken by the same mobile terminal, and, if the pictures are related to persons, the persons may have to be present at the same place and time. SUMMARY OF THE INVENTION [0008]An aspect of the present invention is to address the above-mentioned problems and/or disadvantages and to provide at least the advantages described blow. Accordingly, an aspect of the present invention is to provide a mobile terminal and a composite photographing method that enable multiple mobile terminals to jointly produce a composite photograph. [0009]Another aspect of the present invention is to provide a mobile terminal and a composite photographing method that reduce communication costs by utilizing short-range wireless communication to transmit a picture for composite photography. [0010]In accordance with an aspect of the present invention, a composite photographing method using multiple mobile terminals is provided. The method includes composing, by a master mobile terminal, an incomplete composite photograph, generating, by the master mobile terminal, a participant list of slave mobile terminals, sending, by the master mobile terminal, the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list, receiving, by the first slave mobile terminal, the incomplete composite photograph and participant list, further composing, by the first slave mobile terminal, the received composite photograph, determining, by the first slave mobile terminal, whether the composed composite photograph is complete, sending, by the first slave mobile terminal, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list, and sending, when the composed composite photograph is complete, by the first slave mobile terminal, the composed composite photograph to all mobile terminals having participated in composite photographing. [0011]In accordance with another aspect of the present invention, a composite photographing method using multiple mobile terminals is provided. The method includes composing, by a master mobile terminal, an incomplete composite photograph, generating, by the master mobile terminal, a participant list of one or more slave mobile terminals, setting, by the master mobile terminal, photo-section information for the slave mobile terminals, sending, by the master mobile terminal, the incomplete composite photograph and photo-section information to slave mobile terminals in the participant list, receiving, by each of the slave mobile terminals, the incomplete composite photograph and photo-section information, further composing, by each of the slave mobile terminals, the received composite photograph utilizing the photo-section information, sending, by each of the slave mobile terminals, the composed composite photograph to the master mobile terminal, and combining, by the master mobile terminal, the incomplete composite photographs received from the slave mobile terminals together into a complete composite photograph. [0012]In accordance with yet another aspect of the present invention, a mobile terminal is provided. The terminal includes an input unit for composing a composite photograph and for generating a participant list, a communication unit for transmitting a composite photograph and the participant list, and a control unit for sending a composed incomplete composite photograph and the participant list to a first mobile terminal in the participant list, for further composing, upon reception of an incomplete composite photograph, the received composite photograph, for sending, when the composed composite photograph is incomplete, the composed composite photograph to a second mobile terminal in the participant list, and for sending, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing. [0013]In accordance with still another aspect of the present invention, a mobile terminal is provided. The terminal includes an input unit for composing a composite photograph, for generating a participant list, and for setting photo-section information assigning photo-sections of a composite photograph to different mobile terminals in the participant list, a communication unit for transmitting a composite photograph and the photo-section information, and a control unit for sending an incomplete composite photograph and the photo-section information to one or more mobile terminals in the participant list, for further composing, upon reception of an incomplete composite photograph from a first mobile terminal, the received composite photograph, for sending the composed composite photograph to the first mobile terminal, and for combining, upon reception of incomplete composite photographs matching with the incomplete composite photograph having been sent, the received incomplete composite photographs into a complete composite photograph. [0014]In a feature of exemplary embodiments of the present invention, several users at distinct locations can jointly produce a composite photograph, thereby enhancing user convenience. For example, when family members living at distinct locations desire to take a family photograph, a first member carrying a mobile terminal may select a multi-photo frame, take a facial image, insert the facial image in a photo-section of the multi-photo frame, and may send the multi-photo frame to a second member carrying a mobile terminal. Then, the second member may take a facial image, insert the facial image in another photo-section of the multi-photo frame, and may send the multi-photo frame to a third member carrying a mobile terminal. This process can be continued until a final family photograph is produced. [0015]In addition, short-range wireless communication such as Bluetooth and the like can be used to transmit component images of a composite photograph, thereby reducing communication costs. [0016]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 illustrates communication between mobile terminals for composite photographing according to an exemplary embodiment of the present invention. [0019]FIG. 2 is a block diagram illustrating a mobile terminal capable of producing a composite photograph according to an exemplary embodiment of the present invention; [0020]FIG. 3 is a sequence diagram of a first composite photographing method using mobile terminals based on Radio Frequency (RF) communication according to an exemplary embodiment of the present invention; [0021]FIGS. 4A to 4D are screen representations illustrating steps in the first composite photographing method according to an exemplary embodiment of the present invention; [0022]FIG. 5 is a flowchart illustrating the first composite photographing method based on RF communication according to an exemplary embodiment of the present invention; [0023]FIG. 6 is a sequence diagram of the first composite photographing method based on short-range wireless communication according to an exemplary embodiment of the present invention; [0024]FIG. 7 is a sequence diagram of a second composite photographing method using mobile terminals based on RF communication according to an exemplary embodiment of the present invention; [0025]FIGS. 8A to 8D are screen representations illustrating steps in the second composite photographing method according to an exemplary embodiment of the present invention; [0026]FIGS. 9A and 9B illustrate component images transmitted during execution of the second composite photographing method according to an exemplary embodiment of the present invention; [0027]FIG. 10 is a flowchart illustrating the second composite photographing method based on RF communication according to an exemplary embodiment of the present invention; and [0028]FIG. 11 is a sequence diagram of the second composite photographing method based on short-range wireless communication according to an exemplary embodiment of the present invention. [0029]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0030]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0031]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0032]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0033]For the purpose of description, a mobile terminal is used as an example in exemplary embodiments of the present invention, however the present invention is not limited thereto. The mobile terminal of exemplary embodiments of the present invention is a terminal for user convenience, and may be any information and communication appliance or multimedia appliance, such as a mobile terminal, mobile phone, wired/wireless phone, Portable Multimedia Player (PMP), Personal Digital Assistant (PDA), smart phone, and MP3 player. The mobile terminal may include one or both of a radio frequency module and short-range communication module. While a Bluetooth module is described herein as the short-range communication module as an example, any other short-range communication module may be utilized. [0034]FIG. 1 illustrates communication between mobile terminals for composite photographing according to an exemplary embodiment of the present invention. [0035]Referring to FIG. 1, the system for transmission of component images and production of a composite photograph includes a plurality of mobile terminals 100a to 100n, and a Multimedia Message Service Center (MMSC) 200. In FIG. 1, each of the mobile terminals 100a to 100n includes a communication unit (107 in FIG. 2) that is implemented with a Radio Frequency (RF) module. That is, the mobile terminals 100a to 100n communicate with the MMSC 200 using their RF modules. In the flowing description, FIG. 1 is not applied to the case where the mobile terminals 100a to 100n each include a communication unit implemented with a short-range wireless module. FIG. 1 can be applied to the case where the mobile terminals 100a to 100n each include a communication unit implemented with both a short-range wireless module and RF module. [0036]The mobile terminals 100a to 100n each can make a voice call, use a Short Message Service (SMS), Multimedia Message Service (MMS) and Enhanced Message Service (EMS), and include an MP3 player for playback of a desired song. The mobile terminals 100a to 100n each can include a camera unit (101 in FIG. 2) to take a picture of a target object. [0037]One of the mobile terminals 100a to 100n can take a picture through a camera unit for a composite photograph, and send an MMS message containing the taken picture to another one thereof. That is, the first mobile terminal 100a sends to the MMSC 200 an MMS message containing a picture with a request for delivery of the MMS message containing a picture to the second mobile terminal 100b. The MMSC 200 sends a reply to the first mobile terminal 100a, and sends an MMS notification to the second mobile terminal 100b. The second mobile terminal 100b sends a reply to the MMSC 200, connects to the MMSC 200, and retrieves the corresponding MMS message together with information on the first mobile terminal 100a. [0038]In the following description, the first mobile terminal 100a acts as a master mobile terminal that initiates composite photographing by composing an MMS message containing a picture for a composite photograph, and a participant list. The remaining mobile terminals 100b to 100n act as slave mobile terminals that receive an incomplete composite photograph and insert a taken picture into the incomplete composite photograph. The mobile terminal 100n acts as a mobile terminal that produces a final composite photograph by inserting a taken picture into the incomplete composite photograph. [0039]In composite shot mode, the first mobile terminal 100a, which acts as the master mobile terminal, takes a picture, prepares an incomplete composite photograph by inserting the taken picture into a photo-section of the incomplete composite photograph, and generates a list of mobile terminals participating in composite photographing (i.e. a participant list including the mobile terminals 100b to 100n). Then, the first mobile terminal 100a selects a slave mobile terminal in the participant list, for example the second mobile terminal 100b, and sends the incomplete composite photograph, participant list and sender terminal information on the first mobile terminal 100a through the MMSC 200 to the second mobile terminal 100b. Upon reception, the second mobile terminal 100b takes a picture and inserts the taken picture into a photo-section of the received incomplete composite photograph. When the resulting composite photograph has an empty photo-section (i.e. still incomplete), the second mobile terminal 100b selects another mobile terminal in the participant list, for example the third mobile terminal 100c, and sends the incomplete composite photograph, participant list and sender terminal information on the first and second mobile terminals 100a and 100b through the MMSC 200 to the third mobile terminal 100c. [0040]Finally after repeating similar steps, the n-th mobile terminal 100n takes a picture, obtains a complete composite photograph by inserting the picture into a photo-section of the incomplete composite photograph, and sends the complete composite photograph through the MMSC 200 to the mobile terminals 100a to 100n−1 in the participant list. [0041]The mobile terminals 100a to 100n are connected to the MMSC 200 through a mobile communication network 300. The mobile communication network 300 is a wired/wireless communication network, and may be a network using telephone lines, coaxial cables or optical fibers, a packet switched network, an Integrated Services Digital Network (ISDN), a broadband-ISDN, and the like. [0042]The MMSC 200 is a message service system that can provide not only basic services including voice messages and short text messages but also various multimedia services including Internet electronic mails. The MMSC 200 receives a composite photograph from a mobile terminal and sends the received composite photograph to another mobile terminal. The MMSC 200 includes an MMS server 201 and a subscriber database 203. [0043]The MMS server 201 defines roles of components in the MMSC 200, and controls the components. The MMS server 201 handles and stores MMS messages to be transmitted. The subscriber database 203 contains subscriber specific information, and provides information on delivery and rendering schemes for MMS messages. The subscriber specific information may include subscription information and addressing information of users or subscribers. The MMSC 200 may further include an MMS relay for transferring messages between different messaging systems, an MMS message storage for storing messages, and an MMS user agent for displaying final results of a process in the MMS architecture. [0044]Next, a description is given of a mobile terminal for composite photographing. FIG. 2 is a block diagram illustrating a mobile terminal capable of producing a composite photograph according to an exemplary embodiment of the present invention. [0045]Referring to FIG. 2, the mobile terminal includes a camera unit 101, image processing unit 103, display unit 105, communication unit 107, key input unit 109, storage unit 111, and control unit 113. [0046]The camera unit 101 captures an image of a target object and generates a corresponding image signal. The camera unit 101 includes a lens for forming an image, an image sensor for converting an optical signal corresponding to the formed image into an electrical signal, and an image signal processor for converting the analog electrical signal from the image sensor into digital data. More particularly, when in composite shot mode, the camera unit 101 takes a picture to be inserted into a photo-section of a multi-photo frame. The camera unit 101 may take one or more pictures for the multi-photo frame. [0047]The image processing unit 103 generates screen data to display an image signal from the camera unit 101. The image processing unit 103 includes an image codec to compress image data in a preset format or to decompress compressed image data, for display on the display unit 105. [0048]The display unit 105 displays various information related to the state and operation of the mobile terminal. In particular, the display unit 105 displays a screen for a composite photograph during a composite shot mode. The composite photograph may include an image or characters related to an image. In an exemplary embodiment, for a composite photograph, the composite shot mode is entered after activation of the camera unit 101, a multi-photo framing function is selected during composite shot mode, and a picture of a target object is taken. That is, the display unit 105 displays a multi-photo frame during the composite shot mode. The display unit 105 displays a picture that was taken for a photo-section of the multi-photo frame according to a user input. A master mobile terminal initiating composite photographing displays a participant list screen on the display unit 105. [0049]A slave mobile terminal displays a received composite photograph on the display unit 105, and displays, if the received composite photograph is incomplete, an image composition screen according to a user input. That is, the display unit 105 displays a picture that was taken for a selected photo-section of the multi-photo frame. [0050]As described further below, when the communication unit 107 is a short-range wireless module such as a Bluetooth module, in order to send a composite photograph, the display unit 105 displays a list of Bluetooth device addresses found by inquiry and response procedures between Bluetooth-enabled devices. After issuing a remote name request, if remote names of the found devices are available, the display unit 105 displays a list of the remote names. [0051]The communication unit 107 can be implemented as at least one of an RF module and a short-range wireless module to establish a wireless channel. FIGS. 3 and 5 are related to the composite photographing method in the case of the communication unit 107 being implemented as an RF module, and FIG. 6 is related to the composite photographing method in the case of the communication unit 107 being implemented as a short-range wireless module such as a Bluetooth module. The communication unit 107 may be implemented to include both an RF module as a first unit and a short-range wireless module as a second unit. [0052]When the communication unit 107 is implemented as an RF module, it includes an RF transmitter for upconverting the frequency of a signal to be transmitted and amplifying the signal, and an RF receiver for low-noise amplifying a received signal and downconverting the frequency of the received signal. [0053]When the communication unit 107 is implemented as a short-range wireless module, for example, a Bluetooth module, it can connect to a Bluetooth-enabled device through Bluetooth communication. The short-range wireless module may be any wireless module that can establish a short-range wireless channel for signal exchange, such as a Bluetooth module, IrDA module or Zigbee module. [0054]The Bluetooth protocol operates in the Industrial, Scientific and Medical (ISM) band of 2.4 GHz, and this ISM band is a license-free band. Bluetooth employs a 2 MHz wide lower guard band and a 3.5 MHz wide upper guard band to reduce interference. Bluetooth uses frequency hopping with a hopping rate of 1600 hops per second. [0055]The Bluetooth module collects information on discovered Bluetooth-enabled devices. The collected information may include a Bluetooth address (BD_ADDR), which is a device specific address, device class, page scan repetition mode, and clock offset of a connectable device. By issuing a remote name request to each discovered device, the Bluetooth module may receive a user friendly name of the discovered device as a reply. [0056]The key input unit 109 receives an input signal from the user for controlling the operation of the mobile terminal. In particular, the key input unit 109 receives user input signals for selecting the composite shot mode, composing a composite photograph, activating the camera unit 101, selecting a multi-photo frame, taking a picture of a target object, generating a participant list, and selecting a mobile terminal to which the composite photograph is to be sent. [0057]The storage unit 111 stores programs and data necessary for the operation of the mobile terminal. In particular, the storage unit 111 includes a photo-frame section 211 for the composite shot mode after activation of the camera unit 101. The photo-frame section 211 stores composite photographs in the form of a multi-photo frame, as illustrated in FIG. 4A, which includes multiple photo-sections each accommodating a picture. Multi-photo frames may be pre-stored in the storage unit 111 at the manufacturing process, or may be received from the outside. [0058]The control unit 113 controls overall operations of components in the mobile terminal. In particular, the control unit 113 controls the composite photographing function based on multiple mobile terminals. For the first mobile terminal 100a, the control unit 113 composes an incomplete composite photograph and generates a participant list. Here, composition of an incomplete composite photograph indicates insertion of a taken picture into at least one photo-section of a given multi-photo frame during the composite shot mode. This involves selection of a multi-photo frame as illustrated in FIG. 4A, and insertion of a taken picture into a photo-section as illustrated in FIG. 4B. The control unit 113 sends the incomplete composite photograph to a selected mobile terminal in the participant list. [0059]For the second mobile terminal 100b, in response to reception of an incomplete composite photograph, participant list and sender terminal information, the control unit 113 further composes the incomplete composite photograph. After the composition, the incomplete composite photograph may become complete without an empty photo-section in the multi-photo frame, or may remain incomplete with an empty photo-section. When the composite photograph is complete, the control unit 113 sends the complete composite photograph to all the mobile terminals in the participant list, for example, the first mobile terminal 100a. If the composite photograph remains incomplete, the control unit 113 sends the incomplete composite photograph, participant list, and sender terminal information on the first and second mobile terminals 100a and 100b to another mobile terminal in the participant list that has not yet participated in the composite photographing. [0060]For the n-th mobile terminal 100n, in response to reception of an incomplete composite photograph, participant list and sender terminal information, the control unit 113 further composes the incomplete composite photograph. When the composite photograph is complete, the control unit 113 sends the complete composite photograph to all the mobile terminals in the participant list. Here, completeness of a composite photograph may be determined by determining the presence of an empty photo-section in the multi-photo frame. The mobile terminals in the participant list are those mobile terminals that have participated in composite photographing. [0061]When the communication unit 107 is a Bluetooth module, in order to send a composite photograph, the control unit 113 activates the Bluetooth module and controls the Bluetooth module to issue an inquiry to find a Bluetooth-enabled mobile terminal. If a response is received, the Bluetooth module issues a remote name request to the discovered mobile terminal. Upon reception of a response, the control unit 113 lists the user friendly name of the discovered mobile terminal on the display unit 105. Thereafter, the control unit 113 selects one of listed mobile terminals, performs pairing with the selected mobile terminal, establishes a Bluetooth connection to the selected mobile terminal, and sends the composite photograph. [0062]Next, a description is given of a composite photographing method using multiple mobile terminals. FIGS. 3 and 5 are related to the case where the communication unit is implemented as an RF module. FIG. 3 is a sequence diagram of a first composite photographing method using mobile terminals based on RF communication according to an exemplary embodiment of the present invention. FIGS. 4A to 4D are screen representations illustrating steps in the first composite photographing method according to an exemplary embodiment of the present invention. [0063]Referring to FIG. 3, the first mobile terminal 100a composes an MMS message containing a composite photograph, generates a participant list, and selects the second mobile terminal 100b in step S301. In this step, the first mobile terminal 100a composes an incomplete composite photograph. That is, the first mobile terminal 100a inserts a picture that was taken into at least one photo-section of a given multi-photo frame during a composite shot mode. A screen for a composed composite photograph is illustrated in FIG. 4B. The first mobile terminal 100a selects a multi-photo frame as illustrated in FIG. 4A, takes a facial picture of the user or another person, and inserts the picture into a first photo-section 10 as illustrated in FIG. 4B. [0064]Then, the first mobile terminal 100a generates a list of mobile terminals carried by participants of the composite photographing. The participants may be family members of the user of the first mobile terminal 100a. To produce a family photograph for family members at distinct locations, the user of the first mobile terminal 100a takes the facial picture as illustrated in FIG. 4B, generates a participant list of mobile terminals carried by family members, and selects a mobile terminal, for example the second mobile terminal 100b, in the participant list. The participant list may be made through a menu or option key available after composition of the composite photograph. [0065]Thereafter, the first mobile terminal 100a sends, to the MMSC 200, the composed MMS message containing the composite photograph with a request for delivery of composed MMS message containing the composite photograph to the second mobile terminal 100b in step S303. The MMSC 200 sends a reply to the first mobile terminal 100a in step S305. [0066]The MMSC 200 sends an MMS notification to the second mobile terminal 100b in step S307, and the second mobile terminal 100b sends a reply to the MMSC 200 in step S309. [0067]The second mobile terminal 100b connects to the MMSC 200 in step S311, and retrieves the corresponding MMS message together with the participant list and the sender terminal information on the first mobile terminal 100a in step S313. Here, the sender terminal information includes a telephone number of the first mobile terminal 100a. [0068]The second mobile terminal 100b further composes the received composite photograph, and selects the n-th mobile terminal 100n as the recipient for an MMS message containing the composed composite photograph in step S315. The composite photograph composed at this step is illustrated in FIG. 4C. That is, the second mobile terminal 100b receives the composite photograph with the non-empty first photo-section 10 as illustrated in FIG. 4B, and further composes the composite photograph by taking a facial picture and inserting the picture into a second photo-section 20 of the composite photograph as illustrated in FIG. 4C. The second mobile terminal 100b selects the n-th mobile terminal 100n in the participant list as the recipient for the composed composite photograph. [0069]The second mobile terminal 100b sends, to the MMSC 200, an MMS message containing the composite photograph with a request for delivery of the MMS message containing the composite photograph to the n-th mobile terminal 100n in step S317. The MMSC 200 sends a reply to the second mobile terminal 100b in step S319. [0070]The MMSC 200 sends an MMS notification to the n-th mobile terminal 100n in step S321, and the n-th mobile terminal 100n sends a reply to the MMSC 200 in step S323. [0071]The n-th mobile terminal 100n connects to the MMSC 200 in step S325, and retrieves the corresponding MMS message together with the participant list and the sender terminal information on the first and second mobile terminals 100a and 100b in step S327. In the participant list, each listed mobile terminal may have a checkbox. When the second mobile terminal 100b further composes a composite photograph as described above, it can place a checkmark in the associated checkbox and send the composed composite photograph and the participant list to the n-th mobile terminal 100n. In other words, after a mobile terminal further composes a composite photograph, the mobile terminal places a checkmark in the associated checkbox of the partici(String), 优先 [0001] 此申请根据 35 U.S.C. 2008 年 7 月 2 日向韩国知识产权局提交并转让序列号 10-2008-0063874 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动终端。 更具体地,本发明涉及一种移动终端和使用多个移动终端的合成拍摄方法,其中不同位置的多个移动终端可以共同产生合成照片。 [0004] 2.相关技术的描述 [0005] 随着电子元件越来越小、越来越轻,现代移动终端越来越小型化。 除了基本的呼叫处理功能外,为了满足多样化的用户需求,市售的移动终端还具有包括相机相关功能在内的各种高级功能。 [0006] 配备相机的移动终端可以提供多种拍摄模式,包括静止拍摄、连拍、合成拍摄、夜拍、自拍和视频拍摄。 更具体地说,在合成照片中,拍摄几张照片并将其组合成一张合成照片。 这里,多张图片是由同一个移动终端拍摄的。 即,可以使用单个移动终端来产生合成照片。 为了产生由几个人的照片组成的合成照片,这些人可能必须出现在相同的地点和时间。 [0007] 在复合拍摄模式下,可以使用多张照片取景功能从多张单独拍摄的照片中生成一张照片。 要使用多照片取景功能,这些照片必须由同一个移动终端拍摄,并且如果这些照片与人有关,则这些人可能必须在相同的地点和时间出现。 发明内容 [0008] 本发明的一个方面是解决上述问题和/或缺点并提供至少所描述的优点。 因此,本发明的一个方面是提供一种移动终端和合成拍摄方法,使得多个移动终端能够共同产生合成照片。 [0009] 本发明的另一方面在于提供一种移动终端和一种合成拍摄方法,其通过利用短距离无线通信来传输用于合成拍摄的图片来降低通信成本。 [0010] 根据本发明的一个方面,提供了一种使用多个移动终端的合成拍摄方法。 该方法包括:主移动终端合成不完整的合成照片;主移动终端生成从移动终端的参与者列表;主移动终端将不完整的合成照片和参与者列表发送到第一 参与者列表中的从移动终端,第一从移动终端接收不完整的合成照片和参与者列表,第一从移动终端进一步合成接收到的合成照片,第一从移动终端确定是否 合成照片完成时,第一从移动终端在合成照片不完整时,将合成照片发送给参与者列表中的第二从移动终端,当合成照片完成时,发送, 由第一从移动终端将合成的合成照片发送给所有具有同等水平的移动终端 参与复合摄影。 [0011]根据本发明的另一方面,提供了一种使用多个移动终端的合成拍摄方法。 该方法包括由主移动终端合成一张不完整的合成照片,由主移动终端生成一个或多个从移动终端的参与者列表,由主移动终端设置从移动终端的照片片段信息。 移动终端,主移动终端向参与者列表中的从移动终端发送不完整的合成照片和照片部分信息,每个从移动终端接收不完整的合成照片和照片部分信息,进一步 每个从移动终端利用照片片段信息对接收到的合成照片进行合成,每个从移动终端将合成的合成照片发送到主移动终端,并由主移动终端组合, 将从移动终端接收到的不完整的合成照片组合成一张完整的合成照片。 [0012] 根据本发明的又一方面,提供了一种移动终端。 该终端包括用于合成照片并生成参与者列表的输入单元、用于发送合成照片和参与者列表的通信单元、以及用于将合成的不完整合成照片和参与者列表发送到第一移动设备的控制单元 所述参与者列表中的终端, 用于在接收到不完整的合成照片时, 将接收到的合成照片进一步合成, 用于在合成的合成照片不完整时, 将合成的合成照片发送到参与者列表中的第二移动终端, 以及 当合成的合成照片完成后,将合成的合成照片发送给所有参与合成拍摄的移动终端。 [0013] 根据本发明的又一方面,提供了一种移动终端。 该终端包括:输入单元,用于合成照片,生成参与者列表,以及设置照片部分信息,将合成照片的照片片段分配给参与者列表中的不同移动终端;通信单元,用于发送合成照片 以及照片片段信息,以及控制单元,用于在接收到来自第一移动终端的不完整合成照片时,将不完整合成照片和照片片段信息发送到参与者列表中的一个或多个移动终端,以进行进一步合成 ,接收的合成照片,用于将合成的合成照片发送给第一移动终端,用于在接收到与已发送的不完整的合成照片匹配的不完整的合成照片后,将接收到的不完整的合成照片组合成完整的合成照片。 [0014] 在本发明示例性实施例的一个特征中,不同位置的几个用户可以共同产生合成照片,从而提高用户便利性。 例如,当居住在不同地点的家庭成员想要拍摄家庭照片时,携带移动终端的第一成员可以选择多相框,拍摄面部图像,将面部图像插入到多相框的照片部分中。 相框,并可以将多相相框发送给携带移动终端的第二成员。 然后,第二成员可以拍摄人脸图像,将该人脸图像插入到多相框的另一个照片部分中,并可以将多相框发送给携带移动终端的第三成员。 这个过程可以继续进行,直到制作出最终的全家福。 [0015] 另外,可以使用蓝牙等短距离无线通信来传输合成照片的组成图像,从而降低通信成本。 [0016] 本发明的其他方面、优点和显着特征对于本领域技术人员来说将从以下详细描述中变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0017]本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0018] 图1图示了根据本发明示例性实施例的用于合成拍摄的移动终端之间的通信。 [0019] 图2是示出根据本发明示例性实施例的能够产生合成照片的移动终端的框图; [0020] 图3是根据本发明示例性实施例的使用基于射频(RF)通信的移动终端的第一合成拍摄方法的时序图; [0021] 图4A至4D是示出根据本发明示例性实施例的第一合成拍摄方法中的步骤的屏幕表示; [0022] 图5是示出根据本发明示例性实施例的基于RF通信的第一合成拍摄方法的流程图; [0023] 图6是根据本发明示例性实施例的基于短距离无线通信的第一合成拍摄方法的时序图; [0024] 图7是根据本发明示例性实施例的基于RF通信的使用移动终端的第二合成拍摄方法的时序图; [0025] 图8A至8D是示出根据本发明示例性实施例的第二合成拍摄方法中的步骤的屏幕表示; [0026] 图9A和图9B示出了根据本发明示例性实施例的在执行第二合成拍摄方法期间发送的分量图像; [0027] 图10是示出根据本发明示例性实施例的基于RF通信的第二合成拍摄方法的流程图; 和 [0028] 图11是根据本发明示例性实施例的基于短距离无线通信的第二合成拍摄方法的时序图。 [0029] 在整个附图中,应当注意,相似的附图标记用于描绘相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0030] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,省略了对众所周知的功能和结构的描述。 [0031] 以下描述和权利要求中使用的术语和词语不限于书目含义,而是仅由发明人使用以实现对本发明的清晰和一致的理解。 因此,本领域技术人员应该清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0032] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0033]为了描述的目的,在本发明的示例性实施例中使用移动终端作为示例,然而本发明不限于此。 本发明示例性实施例的移动终端为方便用户使用的终端,可以是任何信息通信设备或多媒体设备,例如移动终端、手机、有线/无线电话、便携式多媒体播放器(PMP)、 个人数字助理 (PDA)、智能手机和 MP3 播放器。 移动终端可以包括射频模块和短程通信模块之一或两者。 尽管本文将蓝牙模块描述为作为示例的短距离通信模块,但是可以使用任何其他短距离通信模块。 [0034] 图1图示了根据本发明示例性实施例的用于合成拍摄的移动终端之间的通信。 [0035] 参见图1,该组件图像传输和合成照片制作系统包括多个移动终端 100 a 至 100 n , 和一个多媒体信息服务中心 (MMSC) 200 . 在图1中,每个移动终端 100 a 至 100 n 包括一个通信单元( 107 在图 2) 中,它是用射频 (RF) 模块实现的。 也就是说,移动终端 100 a 至 100 n 与 MMSC 通信 200 使用他们的射频模块。 在流动描述中,图1不应用于移动终端的情况 100 a 至 100 n 每个都包括一个用短距离无线模块实现的通信单元。 图1可以应用于移动终端的情况 100 a 至 100 n 每个都包括一个用短距离无线模块和RF模块实现的通信单元。 [0036] 移动终端 100 a 至 100 n 每个都可以拨打语音电话,使用短消息服务 (SMS)、多媒体消息服务 (MMS) 和增强型消息服务 (EMS),并包括一个用于播放所需歌曲的 MP3 播放器。 移动终端 100 a 至 100 n 每个都可以包括一个摄像头单元( 101 在图 2) 中拍摄目标物体的照片。 [0037] 移动终端之一 100 a 至 100 n 可以通过用于合成照片的照相机单元拍照,并将包含所拍照片的彩信发送给另一方。 即第一移动终端 100 a 发送到 MMSC 200 包含图片的MMS消息,请求将包含图片的MMS消息传送到第二移动终端 100 b . 多媒体信息中心 200 回复第一移动终端 100 a ,并向第二移动终端发送彩信通知 100 b . 第二个移动终端 100 b 向 MMSC 发送回复 200 , 连接到 MMSC 200 ,并检索对应的彩信和第一移动终端的信息 100 a. [0038] 在下面的描述中,第一移动终端 100 a 充当主移动终端,通过编写包含用于合成照片的图片和参与者列表的MMS消息来发起合成拍摄。 剩下的移动终端 100 b 至 100 n 作为从移动终端接收不完整的合成照片并将拍摄的照片插入到不完整的合成照片中。 移动终端 100 n 充当移动终端,通过将拍摄的照片插入到不完整的合成照片中来产生最终的合成照片。 [0039] 合拍模式下,第一款移动端 100 a,作为主移动终端,拍照,通过将拍摄的照片插入到不完整的合成照片的照片部分中来准备不完整的合成照片,并生成参与合成拍摄的移动终端列表(即参与者列表) 包括移动终端 100 b 至 100 n )。 那么,第一移动终端 100 a 在参与者列表中选择一个从移动终端,例如第二个移动终端 100 b ,并在第一移动终端上发送不完整的合成照片、参与者列表和发送者终端信息 100 a 通过 MMSC 200 到第二个移动终端 100 b . 第二个移动终端接收到 100 b 拍摄照片并将拍摄的照片插入接收到的不完整合成照片的照片部分。 当得到的合成照片有一个空的照片部分(即仍然不完整)时,第二移动终端 100 b 在参与者列表中选择另一个移动终端,例如第三个移动终端 100 c ,并在第一和第二移动终端上发送不完整的合成照片、参与者列表和发送者终端信息 100 a 和 100 b 通过 MMSC 200 到第三个移动终端 100 c. [0040] 最后重复类似步骤后,第n个移动终端 100 n 拍照,将图片插入到不完整的合成照片的照片部分,得到完整的合成照片,并通过MMSC发送完整的合成照片 200 到移动终端 100 a 至 100 n− 1 在参与者列表中。 [0041] 移动终端 100 a 至 100 n 连接到 MMSC 200 通过移动通信网络 300 . 移动通信网络 300 是有线/无线通信网络,可以是使用电话线、同轴电缆或光纤的网络、分组交换网络、综合业务数字网络(ISDN)、宽带-ISDN等。 [0042] 多媒体信息中心 200 是一个消息服务系统,不仅可以提供包括语音消息和短文本消息在内的基本服务,还可以提供包括互联网电子邮件在内的各种多媒体服务。 多媒体信息中心 200 从移动终端接收合成照片,并将接收到的合成照片发送到另一个移动终端。 多媒体信息中心 200 包括彩信服务器 201 和订户数据库 203 . [0043] 彩信服务器 201 定义 MMSC 中组件的角色 200 , 并控制组件。 彩信服务器 201 处理和存储要传输的 MMS 消息。 订户数据库 203 包含订户特定信息,并提供有关 MMS 消息的传递和呈现方案的信息。 订户特定信息可以包括订户信息和用户或订户的寻址信息。 多媒体信息中心 200 还可以包括用于在不同消息系统之间传输消息的MMS中继、用于存储消息的MMS消息存储器、以及用于显示MMS体系结构中处理的最终结果的MMS用户代理。 [0044] 接下来,描述用于合成拍摄的移动终端。 图2是示出根据本发明示例性实施例的能够产生合成照片的移动终端的框图。 [0045] 参考图2,移动终端包括相机单元 101 , 图像处理单元 103 , 显示单元 105 , 通讯单元 107 , 按键输入单元 109 , 存储单元 111 , 和控制单元 113 . [0046] 相机单元 101 捕获目标物体的图像并生成相应的图像信号。 相机单元 101包括用于形成图像的镜头、用于将与形成的图像对应的光信号转换为电信号的图像传感器、以及用于将来自图像传感器的模拟电信号转换为数字数据的图像信号处理器。 更具体地说,当处于复合拍摄模式时,相机单元 101 拍摄要插入到多相框的照片部分的照片。 相机单元 101 可以为多相框拍摄一张或多张照片。 [0047] 图像处理单元 103 生成屏幕数据以显示来自相机单元的图像信号 101 . 图像处理单元 103 包括图像编解码器,用于以预设格式压缩图像数据或解压缩压缩的图像数据,以在显示单元上显示 105 . [0048] 显示单元 105 显示与移动终端的状态和操作相关的各种信息。 特别是显示单元 105 在合成拍摄模式期间显示合成照片的屏幕。 合成照片可以包括图像或与图像相关的字符。 在示例性实施例中,对于合成照片,在激活相机单元之后进入合成拍摄模式 101 ,在合成拍摄模式下选择多照片取景功能,对目标物体进行拍照。 也就是显示单元 105 在合成拍摄模式中显示多张相框。 显示单元 105 显示根据用户输入为多相框的照片部分拍摄的照片。 发起合成拍摄的主移动终端在显示单元上显示参与者列表屏幕 105 . [0049] 从移动终端在显示单元上显示接收到的合成照片 105 ,并且如果接收到的合成照片不完整,则根据用户输入显示图像合成屏幕。 也就是显示单元 105 显示为多相框的选定照片部分拍摄的照片。 [0050] 如下文进一步描述的,当通信单元 107 是蓝牙模块等短距离无线模块,为了发送合成照片,显示单元 105 显示通过蓝牙设备之间的查询和响应过程找到的蓝牙设备地址列表。 发出远程名称请求后,如果找到的设备的远程名称可用,则显示单元 105 显示远程名称列表。 [0051] 通讯单元 107 可以实现为RF模块和短距离无线模块中的至少一种以建立无线信道。 图3和图5涉及通信单元情况下的合成拍摄方法 107 以RF模块实现,图6为通信单元情况下的复合拍照方法 107 被实现为短距离无线模块,例如蓝牙模块。 通讯单元 107 可以实施为包括作为第一单元的RF模块和作为第二单元的短距离无线模块。 [0052] 当通讯单元 107 被实现为RF模块,它包括用于对要发送的信号的频率进行上变频和放大信号的RF发射器,以及用于对接收信号进行低噪声放大和对接收信号的频率进行下变频的RF接收器。 [0053] 当通讯单元 107 被实现为短距离无线模块,例如蓝牙模块,它可以通过蓝牙通信连接到具有蓝牙功能的设备。 近距离无线模块可以是蓝牙模块、IrDA模块或Zigbee模块等任何能够建立近距离无线信道进行信号交换的无线模块。 [0054] 蓝牙协议在 2.4 GHz 的工业、科学和医疗 (ISM) 频段中运行,该 ISM 频段是免许可频段。 蓝牙采用 2 MHz 宽的下保护频带和 3.5 MHz 宽的上保护频带来减少干扰。 蓝牙使用跳频,跳频为每秒 1600 跳。 [0055]蓝牙模块收集有关发现的蓝牙设备的信息。 收集的信息可以包括蓝牙地址(BD_ADDR),它是设备特定地址、设备类别、页面扫描重复模式和可连接设备的时钟偏移。 通过向每个发现的设备发出远程名称请求,蓝牙模块可以接收发现的设备的用户友好名称作为回复。 [0056] 按键输入单元 109 接收来自用户的输入信号,用于控制移动终端的操作。 特别是按键输入单元 109 接收用于选择合成拍摄模式、合成照片、激活相机单元的用户输入信号 101 ,选择多相框,对目标对象进行拍照,生成参与者列表,选择要发送合成照片的移动终端。 [0057] 存储单元 111 存储移动终端操作所需的程序和数据。 特别是存储单元 111 包括一个相框部分 211 用于激活相机单元后的合成拍摄模式 101 . 相框部分 211 如图4A所示,它以多相框的形式存储合成照片,其包括多个照片部分,每个照片部分容纳一张图片。 多张相框可预先存储在存储单元中 111 在制造过程中,或可能从外部接收。 [0058] 控制单元 113 控制移动终端中组件的整体操作。 特别是控制单元 113 控制基于多个移动终端的合成拍照功能。 对于第一个移动终端 100 a , 控制单元 113 合成一张不完整的合成照片并生成参与者列表。 这里,不完整合成照片的合成表示在合成拍摄模式期间将拍摄的照片插入给定多照片帧的至少一个照片部分。 这包括选择如图4A所示的多照片帧,以及将拍摄的图片插入到如图4B所示的照片部分中。 控制单元 113 将不完整的合成照片发送到参与者列表中选定的移动终端。 [0059] 对于第二个移动终端 100 b ,响应于接收到不完整的合成照片、参与者列表和发送者终端信息,控制单元 113 进一步构成不完整的合成照片。 在合成之后,不完整的合成照片可能在多相框中没有空白的照片部分而变得完整,或者可能保持不完整的有空白的照片部分。 合成照片完成后,控制单元 113 将完整的合成照片发送给参与者列表中的所有移动终端,例如第一台移动终端 100 a . 如果合成照片仍然不完整,控制单元 113 在第一和第二移动终端上发送不完整的合成照片、参与者列表和发送者终端信息 100 a 和 100 b 发送到参与者列表中尚未参与合成拍摄的另一个移动终端。 [0060] 对于第n个移动终端 100 n ,响应于接收到不完整的合成照片、参与者列表和发送者终端信息,控制单元 113 进一步构成不完整的合成照片。 合成照片完成后,控制单元 113 将完整的合成照片发送到参与者列表中的所有移动终端。 这里,可以通过确定多照片帧中是否存在空白照片部分来确定合成照片的完整性。 参与列表中的移动终端为参与过合成拍摄的移动终端。 [0061] 当通讯单元 107 是蓝牙模块,为了发送合成照片,控制单元 113激活蓝牙模块并控制蓝牙模块发出查询以查找具有蓝牙功能的移动终端。 如果接收到响应,蓝牙模块向发现的移动终端发出远程名称请求。 收到响应后,控制单元 113 在显示单元上列出发现的移动终端的用户友好名称 105 . 此后,控制单元 113 选择列出的移动终端之一,与选择的移动终端进行配对,与选择的移动终端建立蓝牙连接,并发送合成照片。 [0062] 接下来,描述使用多个移动终端的合成拍摄方法。 图3和5与通信单元被实现为RF模块的情况有关。 图3是根据本发明示例性实施例的使用基于RF通信的移动终端的第一合成拍摄方法的时序图。 图4A至图4D是示出根据本发明示例性实施例的第一合成拍摄方法中的步骤的屏幕表示。 [0063] 参见图3,第一移动终端 100 a 撰写包含合成照片的彩信,生成参与者列表,并选择第二移动终端 100 b 在步骤 S 301 . 本步骤中,第一移动终端 100 a 构成一张不完整的合成照片。 即第一移动终端 100 a 插入在合成拍摄模式期间拍摄到给定多照片帧的至少一个照片部分的照片。 图4B示出了合成合成照片的屏幕。 第一个移动终端 100 a 选择如图4A所示的多相框,拍摄用户或其他人的面部照片,并将照片插入到第一照片部分 10 如图4B所示。 [0064] 那么,第一移动终端 100 a 生成合成拍摄参与者携带的移动终端列表。 参与者可以是第一移动终端用户的家庭成员 100 a . 为了为不同地点的家庭成员制作家庭照片,第一移动终端的用户 100 a 拍摄如图4B所示的人脸照片,生成家庭成员携带的移动终端的参与者列表,并选择移动终端,例如第二移动终端 100 b ,在参与者列表中。 可以通过合成照片合成后可用的菜单或选项键来制作参与者列表。 [0065] 此后,第一移动终端 100 a 发送到 MMSC 200 ,包含合成照片的合成MMS消息,请求将包含合成照片的合成MMS消息传送到第二移动终端 100 b 在步骤 S 303 . 多媒体信息中心 200 回复第一移动终端 100 a 在步骤 S 305 . [0066] 多媒体信息中心 200 向第二移动终端发送彩信通知 100 b 在步骤 S 307 ,以及第二个移动终端 100 b 向 MMSC 发送回复 200 在步骤 S 309 . [0067] 第二个移动终端 100 b 连接到 MMSC 200 在步骤 S 311 ,并在第一移动终端上检索相应的彩信以及参与者列表和发送者终端信息 100 a 在步骤 S 313 . 这里,发送方终端信息包括第一移动终端的电话号码 100 a. [0068] 第二个移动终端 100 b 进一步对接收到的合成照片进行构图,选择第n个移动终端 100 n 作为包含步骤 S 中合成的合成照片的 MMS 消息的接收者 315 . 该步骤合成的合成照片如图4C所示。 即第二移动终端100 b 接收具有非空第一照片部分的合成照片 10 如图4B所示,并进一步通过拍摄面部照片并将照片插入第二照片部分来构成合成照片 20 如图4C所示的合成照片。 第二个移动终端 100 b 选择第n个移动终端 100 n 在参与者列表中作为合成合成照片的接收者。 [0069] 第二个移动终端 100 b 发送到 MMSC 200 ,包含合成照片的MMS消息,请求将包含合成照片的MMS消息传送到第n个移动终端 100 n 在步骤 S 317 . 多媒体信息中心 200 向第二移动终端发送回复 100 b 在步骤 S 319 . [0070] 多媒体信息中心 200 向第n个移动终端发送彩信通知 100 n 在步骤 S 321 ,以及第n个移动终端 100 n 向 MMSC 发送回复 200 在步骤 S 323 . [0071] 第n个移动终端 100 n 连接到 MMSC 200 在步骤 S 325 ,并在第一和第二移动终端上检索相应的彩信以及参与者列表和发送者终端信息 100 a 和 100 b 在步骤 S 327 . 在参与者列表中,每个列出的移动终端都可以有一个复选框。 当第二个移动终端 100 b 再如上述合成一张合成照片,可以在相关的复选框打勾,将合成的合成照片和参与者列表发送给第n个移动终端 100 n . 换言之,移动终端进一步合成一张合成照片后,移动终端在参与者列表的相关复选框中打勾,并将参与者列表和合成照片都发送给下一个移动终端。 因此,接收到合成照片和参与者列表的下一个移动终端可以很容易地识别出参与合成拍摄的移动终端,并在参与者列表中选择要发送合成照片的下一个移动终端。 [0072] 第n个移动终端 100 n 将接收到的合成照片进一步合成,生成完整的合成照片,并在步骤S中选择参与者列表中的所有移动终端 329 . 在该步骤中完成的合成照片如图4D所示。 即第n个移动终端 100 n 接收具有非空第一和第二照片部分的合成照片 10 和 20 如图4C所示,并进一步通过拍摄面部照片并将照片插入第三照片部分来构成合成照片 30 如图 4D 所示的合成照片。 第n个移动终端 100 n 选择参与者列表中的所有移动终端(第一和第二移动终端 100 a 和 100 b ) 作为完整合成照片的接收者。 [0073] 第n个移动终端 100 n 发送到 MMSC 200 ,包含完整合成照片的MMS消息,并请求将包含完整合成照片的MMS消息传送到参与者列表中的所有移动终端(第一和第二移动终端 100 a 和 100 b ) 在步骤 S 331 . 多媒体信息中心 200 向第n个移动终端发送回复 100 n 在步骤 S 333 . [0074] 多媒体信息中心 200 向第一移动终端发送彩信通知 100 a 在步骤 S 335 和第二移动终端 100 b 在步骤 S 337 . 第一个移动终端 100 a 向 MMSC 发送回复 200 在步骤 S 339 ,以及第二个移动终端 100 b 向 MMSC 发送回复200 在步骤 S 341 . [0075] 第一个移动终端 100 a 连接到 MMSC 200 在步骤 S 343 , 并在步骤 S 中检索相应的 MMS 消息 347 . 第二个移动终端 100 b 连接到 MMSC 200 在步骤 S 345 , 并在步骤 S 中检索相应的 MMS 消息 349 . [0076] 在以上描述中,三个移动终端参与合成拍摄。 然而,本发明不限于此,参与的移动终端的数量可以根据给定的多照片帧中的照片片段的数量或参与列表中的条目的数量而变化。 此外,合成照片的产生不限于选择与多照片取景相关的特定功能。 [0077] 接下来,对使用多个移动终端的第一合成拍摄方法给出另一种描述。 图5是根据本发明示例性实施例的基于RF通信的使用移动终端的第一合成拍摄方法的流程图。 [0078] 参照图5,控制单元 113 第一个移动终端 100 a 确定是否在步骤 S 中发出了对合成拍摄模式的请求 361 . 在合成拍摄模式下,相机单元 101 如图4A所示,激活并显示多相框。 [0079] 当发出合成拍摄模式的请求时,控制单元 113 编写包含合成照片的 MMS 消息,并在步骤 S 中生成参与者列表 363 . 本步骤,如图4B所示,第一移动终端 100 a 通过将图片插入第一个照片部分来组成不完整的合成照片 10 给定的多相框。 参与者列表是参与合成拍摄的移动终端的列表。 [0080] 控制单元 113 判断步骤S中是否选择了参与者列表中的移动终端 365 . 假设用户选择了第二移动终端 100 b 作为合成照片的收件人。 如果没有选择移动终端,则控制单元 113 返回步骤 S 363 . [0081] 当第二个移动终端 100 b 被选中时,控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 请求将包含合成照片的MMS消息传送到第二移动终端 100 b 在步骤 S 367 . 控制单元 113 向MMSC发送参与者列表和发送者终端信息 200 在步骤 S 369 . [0082] 在步骤 S 未发出合成拍摄模式请求时 361 , 控制单元 113 判断步骤S中是否接收到包含合成照片的彩信 371 . 可以与合成照片一起接收参与者列表和发送者终端信息。 [0083] 当接收到包含合成照片的彩信时,控制单元 113 在步骤 S 中确定合成照片是否完成 373 . 如结合图3所述,接收到的合成照片可能是来自例如第二移动终端的不完整照片 100 b ,或者可以是完整的,例*自第n个移动终端 100 n . 控制单元 113 可以通过检测合成照片中是否存在空白照片部分(即多相框)来确定合成照片的完整性。 如果接收到的合成照片如在图 4D 的情况下是完整的,则控制单元 113 根据用户输入执行操作。 例如,控制单元 113 将接收到的合成照片存储在存储单元中 111 . [0084] 如果接收到的合成照片不完整,控制单元 113 进一步合成步骤S中的合成照片 375. 也就是说,如果接收到的合成照片不完整,如图 4B 的情况,或者 4 C、控制单元 113 激活相机单元 101 拍照,将图片插入合成照片的空白照片部分,并存储合成照片。 [0085] 控制单元 113 确定在步骤S中是否发出传输合成合成照片的请求 377 . 如果发出传输请求,控制单元 113 在步骤S中确定合成的合成照片是否完整 379 . 如结合图3所述,在步骤S合成的合成照片 375 例如,可能是来自第二移动终端的不完整的 100 b ,或者是完整的,例*自第n个移动终端 100 n . 即步骤S合成的合成照片 375 可以像图4C的情况那样不完整,或者像图4D的情况那样完整。 控制单元 113 当合成照片中不存在空白照片部分时,将合成照片视为完整照片。 [0086] 如果合成的合成照片不完整,控制单元 113 在参与者列表中选择一个移动终端,例如第n个移动终端 100 n , 在步骤 S 381 . 控制单元 113 当合成照片中存在空白照片部分时,认为合成照片不完整。 控制单元 113 在参与者列表中选择一个尚未参与合成拍摄的移动终端。 [0087] 控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 请求将包含合成照片的MMS消息传送到第n个移动终端 100 n 在步骤 S 383 , 并进入步骤 S 369 . [0088] 如果在步骤 S 合成的合成照片不完整 379 , 控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 在步骤S中请求向参与者列表中的所有移动终端发送包含合成照片的MMS消息 385 . 这里,假设参与者列表移动和发送者终端信息标识相同的移动终端。 当参与者列表移动和发送终端信息不标识相同的移动终端时,将完整的合成照片发送到发送终端信息标识的实际参与合成拍摄的移动终端。 参与者列表中的移动终端可能不参与合成拍摄。 [0089] 此后,控制单元 113 进入步骤 S 369 . [0090] 接下来,对使用多个移动终端的第一合成拍摄方法给出另一种描述。 图6是根据本发明示例性实施例的基于短距离通信的使用移动终端的第一合成拍摄方法的时序图。 在图6中,移动终端使用蓝牙通信作为短距离通信进行合成拍摄。 [0091] 参见图6,第一移动终端 100 a 合成一张不完整的合成照片,生成参与者列表,并在步骤S中激活蓝牙模块选择移动终端作为合成照片的接收者 401 . [0092] 第一个移动终端 100 a 列出获取的移动终端的远程名称,例如选择第二个移动终端 100 b 根据在步骤 S 中获得的远程名称在参与者列表中 403 . 第一个移动终端 100 a 启动蓝牙模块,发现启用蓝牙的移动终端,向发现的移动终端发出远程名称请求,从响应的移动终端获取远程名称,并显示获取的远程名称。 第一个移动终端 100 a 使用获取的远程名称,例如选择第二移动终端 100 b 在参与者列表中。 [0093] 第一个移动终端 100 a 与第二移动终端进行配对 100 b , 并在步骤 S 中建立蓝牙连接 405 . 第一个移动终端 100 a 在第一移动终端上发送合成照片、参与者列表和发送者终端信息 100 a 到第二个移动终端 100 b 在步骤 S 407 . [0094] 第二个移动终端 100 b 进一步对接收到的合成照片进行合成,并在步骤S中激活蓝牙模块传输合成的合成照片 409 . [0095] 第二个移动终端 100 b 列出获取的移动终端的远程名称,例如选择第n个移动终端 100 n 根据在步骤 S 中获得的远程名称在参与者列表中 411 . [0096] 第二个移动终端 100 b 与第n个移动终端进行配对 100 n , 并在步骤 S 中建立蓝牙连接 413 . 第二个移动终端 100 b 在第一和第二移动终端上发送合成照片、参与者列表和发送者终端信息 100 a 和 100 b 到第n个移动终端 100 n 在步骤 S 415 . [0097] 第n个移动终端 100 n 进一步对接收到的合成照片进行合成,并在步骤S中激活蓝牙模块传输合成的合成照片 417 . [0098] 第n个移动终端 100 n 列出获取的移动终端的远程名称,并根据步骤S中获取的远程名称选择参与者列表中的所有移动终端 419 . 这里,参与列表中的移动终端是参与过合成拍摄的移动终端(例如,第一移动终端和第二移动终端) 100 a 和 100 b )。 [0099] 第n个移动终端 100 n 与第二移动终端进行配对 100 b 并在步骤S中与其建立蓝牙连接 421 ,并将合成照片发送至第二移动终端 100 b 在步骤 S 425 . 第n个移动终端 100 n 与第一移动终端进行配对 100 a 并在步骤S中与其建立蓝牙连接 423 ,并将合成照片发送至第一移动终端 100 a 在步骤 S 427 . [0100] 接下来,描述使用多个移动终端的第二合成拍摄方法。 省略与第一合成拍摄方法的要素基本相同或对应的要素的描述。 [0101] 在第二种合成拍摄方法中,主移动终端向参与者列表中的一个或多个从移动终端发送合成照片,每个从移动终端进一步合成合成照片并将未完成的合成照片发送给主移动终端, 主移动终端将不完整的合成照片组合在一起成为最终的合成照片。 [0102] 返回参考图1,移动终端之一 100 a 至 100 n 可以通过摄像单元拍照形成初始合成照片,并将包含合成照片的彩信发送给另一方。 即第一移动终端 100 a 作为主机发送MMSC 200 包含合成照片的MMS消息,请求将包含合成照片的MMS消息传送到第二至第n个移动终端 100 b 至 100 n 充当奴隶。 这里,合成照片可以是第一形式,其具有填充有由第一移动终端拍摄的照片的照片部分 100 a (如图8B所示),或者在没有照片部分的第二种形式中,该照片部分填充了由第一移动终端拍摄的照片 100 a (如图 8A 所示)。 在发送合成照片的同时,还向第二至第n移动终端发送照片片段信息 100 b 至 100 n. [0103] 收到 MMS 消息后,MMSC 200 回复第一移动终端 100 a ,向第二至第n个移动终端发送彩信通知 100 b 至 100 n . 第二至第n移动终端中的每一个 100 b 至 100 n 向 MMSC 发送回复 200 , 连接到 MMSC 200 ,并检索对应的包含合成照片的彩信以及第一移动终端的发送方终端信息 100 a 和照片部分信息。 照片部分信息由第一移动终端给出 100 a ,并且表示接收移动终端(第二到第n移动终端)进入的合成照片(或多相框)的照片部分 100 b 至 100 n ) 是插入图片。 [0104] 第二至第n移动终端中的每一个 100 b 至 100 n 进一步对接收到的合成照片进行拍照,并将图片插入到照片片段信息所指示的合成照片的照片片段中。 第2至第n移动终端 100 b 至 100 n 将他们合成的合成照片发送到第一台移动终端 100 a ,然后将接收到的合成照片组合成一张完整的合成照片。 此后,第一移动终端 100 a 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n 参加过复合摄影。 [0105] 参考图2,通信单元 107 可以实现为RF模块和短距离无线模块中的至少一种。 图7和图10涉及在通信单元的情况下的第二合成拍摄方法 107 以RF模块实现,图11为通信单元情况下的第二种合成拍摄方法 107 被实现为像蓝牙模块一样的短距离无线模块。 [0106] 对于第一个移动终端 100 a 作为主机,控制单元 113 合成一张不完整的合成照片,生成参与者列表,并设置照片部分信息。 这里,不完整合成照片的合成表示在合成拍摄模式期间将拍摄的照片插入给定多照片帧的至少一个照片部分。 照片片段信息指定将图片插入到多相框的每个照片片段中的移动终端。 控制单元 113 将合成照片和照片片段信息发送至参与者列表中的至少一个从移动终端。 在从第二至第n移动终端接收合成照片时 100 b 至 100 n , 控制单元 113 将接收到的合成照片组合成一张完整的合成照片。 此后,控制单元 113 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n. [0107] 对于第二至第n个移动终端之一 100 b 至 100 n 作为从机,响应于接收到合成照片、参与者列表、照片部分信息和发送者终端信息,控制单元 113进一步对接收到的合成照片进行拍照,并将图片插入到照片片段信息所指示的合成照片的照片片段中。 控制单元 113 然后将合成的合成照片发送到第一移动终端 100 a ,即发件人。 [0108] 合成照片或多相框可以采用多种形式。 例如,第一种合成照片可以包括如图8B至8D所示的取景图像和拍摄的照片,第二种合成照片可以仅包括如图9A所示的拍摄的照片,而第三种合成照片可以 如图9B所示,在取景图像中包括拍摄的照片和相关的照片部分(未示出)。 [0109] 即,第一种合成照片作为多照片帧被传送,其照片部分包括如图8B至8D所示的拍摄照片。 如图9A所示,第二类型的合成照片作为包括在给定位置拍摄的照片而没有取景图像的多照片帧传送。 第二类合成照片作为具有相关照片部分信息的拍摄照片传输。 [0110] 在与图 8A 至 8D 以及图 9A 和 9B 相关的情况下,第一移动终端 100 a 将仅包括取景图像的合成照片发送到第二至第n移动终端 100 b 至 100 n . 即,在给定的多照片帧中,分配给第一移动终端的照片片段 100 a 是空的。 第二至第n移动终端中的每一个 100 b 至 100 n 将拍摄的照片插入接收到的多相框的指定照片部分。 当第一个移动终端 100 a 将在指定照片分区拍摄的多照片帧作为合成照片发送,第一移动终端拍摄的面部照片 100 a 应该出现在,例如,第一个照片部分 10 在图 8C 或 8 D. [0111] 接下来,描述使用多个移动终端的第二合成拍摄方法。 图7和10与通信单元被实现为RF模块的情况有关。 [0112] 图7是根据本发明示例性实施例的使用基于RF通信的移动终端的第二合成拍摄方法的时序图。 图8A至图8D是示出根据本发明示例性实施例的第二合成拍摄方法中的步骤的屏幕表示。 图9A和9B示出了根据本发明示例性实施例的可在移动终端之间传送的合成照片的形式。 [0113] 参见图7,第一移动终端 100 a 编写包含合成照片的彩信,生成参与者列表,并在步骤S中为参与者列表中的每个移动终端设置照片片段信息 501 . 本步骤中,第一移动终端 100 a 构成一张不完整的合成照片。 即第一移动终端 100 a 在合成拍摄模式期间,将拍摄的照片插入给定多照片帧的至少一个照片部分。 图8B示出了合成合成照片的屏幕。 第一个移动终端 100 a 选择如图8A所示的多照片帧,拍摄用户或其他人的面部照片,并将照片插入到第一照片部分 10 如图8B所示。 [0114] 那么,第一移动终端 100 a 生成合成拍摄参与者携带的移动终端列表。 可以通过合成照片合成后可用的菜单或选项键来制作参与者列表。 此外,第一款移动终端 100 a 通过在参与者列表中将单个照片部分分配给移动终端来设置照片部分信息。 例如,第一移动终端 100 a 可以选择如图 8A 所示的多相框,并分配第二个照片部分 20 和第三个照片部分 30 分别到第一移动终端 100 a 第n个移动终端 100 n . 可以通过可用于合成拍摄的菜单或选项键来分配照片部分。 [0115] 此后,第一移动终端 100 a 发送到 MMSC 200 ,包含合成照片的合成MMS消息,请求将包含合成照片的MMS消息传送到第二至第n个移动终端 100 b 至 100 n 在步骤 S 503 . [0116] 这里,如前所述,合成照片可以包括在分配给第一移动终端的照片部分的拍摄照片 100 a 如图8B所示,或者可以不包括如图8A所示的拍摄图片。 在下面的描述中,第一移动终端 100 a 将如图8A所示的仅包括取景图像的合成照片发送到第二至第n移动终端 100 b 至 100 n. [0117] 多媒体信息中心 200 回复第一移动终端 100 a 在步骤 S 505 . 多媒体信息中心 200 向第二至第n个移动终端发送彩信通知 100 b 至 100 n 在步骤 S 507 和 S 509 ,以及第二至第n个移动终端 100 b 至 100 n 向 MMSC 发送回复 200 在步骤 S 511 和 S 513 . [0118] 第2至第n移动终端 100 b 至 100 n 连接到 MMSC 200 在步骤 S 515 和 S 517 ,并在第一移动终端上检索相应的彩信以及照片片段信息和发送者终端信息 100 a 在步骤 S 519 和 S 521 . [0119] 第二至第n移动终端中的每一个 100 b 至 100 n 进一步对接收到的合成照片进行构图,选择第一移动终端 100 a 作为步骤 S 中的收件人 523 和 S 525 . 第二和第n个移动终端合成的不完整照片 100 b 和 100 n 在图8C和8D中示出。 即第二移动终端 100 b 通过将拍摄的照片插入第二个照片部分,进一步合成接收到的合成照片 20 如图8C所示,第n个移动终端 100 n 通过将拍摄的照片插入第三个照片部分,进一步合成接收到的合成照片 30 如图 8D 所示。 此后,第二至第n移动终端中的每一个 100 b 至 100 n 选择第一个移动终端 100 a 作为合成合成照片的接收者。 [0120] 第二至第n移动终端中的每一个 100 b 至 100 n 发送到 MMSC 200 ,包含合成照片的MMS消息,请求将包含合成照片的MMS消息传送到第一移动终端 100 a 在步骤 S 527 和 S 529 . 多媒体信息中心 200 向第二至第n个移动终端中的每一个发送回复 100 b 至 100 n 在步骤 S 531 和 S 533 . [0121] 多媒体信息中心 200 向第一移动终端发送彩信通知 100 a 在步骤 S 535 ,以及第一台移动终端 100 a 向 MMSC 发送回复 200 在步骤 S 537 . [0122] 第一个移动终端 100 a 连接到 MMSC 200 在步骤 S 539 , 并在步骤 S 中检索相应的 MMS 消息 541. 如前所述,在该步骤接收到的合成照片可以采用各种形式。 例如,第一种合成照片可以包括如图8B至8D所示的取景图像和拍摄的照片,第二种合成照片可以仅包括如图9A所示的拍摄的照片,而第三种合成照片可以 如图9B所示,在取景图像中包括拍摄的照片和相关的照片部分(未示出)。 [0123] 第一个移动终端 100 a 在步骤S中将接收到的合成照片组合成一张完整的合成照片 543 . 后来,第一个移动终端 100 a 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n 参加过复合摄影。 [0124] 在与步骤 S 相关的描述中 535 到 S 541 ,在 MMSC 之间进行一次彩信通知、回复、连接和彩信检索 200 和第一个移动终端 100 a . 每当 MMS 消息到达 MMSC 时,这些操作可能会执行一次 200 从第二个到第n个移动终端 100 b 至 100 n. [0125] 在以上描述中,三个移动终端参与合成拍摄。 然而,本发明不限于此,参与的移动终端的数量可以变化。 此外,合成照片的产生不限于选择与多照片取景相关的特定功能。 [0126] 接下来,给出使用多个移动终端的第二合成拍摄方法的另一描述。 图10是根据本发明示例性实施例的基于RF通信的使用移动终端的第二合成拍摄方法的流程图。 [0127] 参照图10,控制单元 113 第一个移动终端 100 a 确定是否在步骤 S 中发出了对合成拍摄模式的请求 561 . 在合成拍摄模式下,相机单元 101 如图8A所示,激活并显示多相框。 [0128] 当发出合成拍摄模式的请求时,控制单元 113 编写包含合成照片的彩信,生成参与者列表,并在步骤S中将合成照片的照片片段分配给参与者列表中的移动终端 563 . 在该步骤,如图8B所示,控制单元 113 通过将图片插入第一个照片部分来组成不完整的合成照片 10 . 参与者列表为参与合成拍摄的移动终端列表(第2至第n移动终端 100 b 至 100 n )。 控制单元 113 将合成照片的照片片段分配给第二至第n个移动终端 100 b 至 100 n . 例如,第二个照片部分 20 和第三个照片部分 20 分别分配给第二移动终端 100 b 和 n -th 移动终端 100 n. [0129] 控制单元 113 判断步骤S中是否发出转移请求 565 . 当发出传输请求时,控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 在步骤S中请求将包含合成照片的MMS消息传送到参与者列表中的移动终端 567 . 控制单元 113 将照片部分信息和发送者终端信息发送到MMSC 200 在步骤 S 569 . [0130] 在步骤 S 中未发出合成拍摄模式请求时 561 , 控制单元 113 判断步骤S中是否接收到包含合成照片的彩信 571 . 可以与合成照片一起接收照片片段信息和发送者终端信息。 [0131]当接收到合成照片时,控制单元 113 判断接收到的合成照片是否与步骤S中发送的合成照片匹配 573 . 如结合图7所述,第一移动终端 100 a 可将合成照片发送至第二至第n个移动终端 100 b 至 100 n ,然后从第二到第n个移动终端中的每一个接收进一步合成的合成照片 100 b 至 100 n. [0132] 如果接收到的合成照片与已发送的合成照片不匹配,则控制单元 113 进一步对步骤S中接收到的合成照片进行合成 575 . 如结合图7针对第二至第n移动终端所描述的 100 b 至 100 n ,第二至第n个移动终端中的每一个 100 b 至 100 n 可以接收如图8A所示的合成照片,并进一步合成接收到的合成照片。 即第二移动终端 100 b 将拍摄的照片插入第二个照片部分 20 如图8C所示,第n个移动终端 100 n 将拍摄的照片插入第三个照片部分 30 如图 8D 所示。 [0133] 控制单元 113 确定在步骤S中是否发出传输合成合成照片的请求 577 . 如果发出传输请求,控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 在步骤S中请求将包含合成的合成照片的MMS消息传送到发送方移动终端 579 . 多媒体信息中心 200 在步骤S中将MMS消息传递给发送方移动终端 581 . 合成的合成照片是不完整的,如图 8B 或 8 C,并且可以采用如图 8B 所示的第一种类型中的一种或 8 C、第二类如图9A所示,第三类如图9B所示。 [0134] 如果接收到的合成照片与在步骤S中发送的合成照片匹配 573 , 控制单元 113 在步骤S中将多张接收到的合成照片组合成一张完整的合成照片 583 . 如上所述,接收到的合成照片可以采取各种形式。 此后,控制单元 113 判断步骤S中是否发出完整合成照片的传输请求 585 . 如果发出传输请求,控制单元 113 向 MMSC 发送包含完整合成照片的 MMS 消息 200 请求将包含完整合成照片的MMS消息传递给在步骤S中参与合成拍摄的移动终端 587 . [0135] 接下来,给出使用多个移动终端的第二合成拍摄方法的另一描述。 在图11中,移动终端使用蓝牙通信进行合成拍摄。 图11是根据本发明示例性实施例的使用基于短距离通信的移动终端的第二合成拍摄方法的时序图。 在图11中,蓝牙通信将用作短距离通信的示例。 [0136] 参见图11,第一移动终端 100 a 合成一张不完整的合成照片,生成参与者列表,设置照片部分信息,并在步骤S中激活蓝牙模块选择移动终端作为合成照片的接收者 601 . 第一个移动终端 100 a 通过将合成照片的照片部分分配给参与者列表中的移动终端来设置照片部分信息。 可以通过可用于合成拍摄的菜单或选项键来分配照片部分。 第一个移动终端 100 a 激活蓝牙模块以选择移动终端作为合成照片的接收者。 [0137]第一个移动终端 100 a 列出获取的移动终端的远程名称,例如选择第2到第n个移动终端 100 b 至 100 n 根据在步骤 S 中获得的远程名称在参与者列表中 603 . 第一个移动终端 100 a 启动蓝牙模块,发现启用蓝牙的移动终端,向发现的移动终端发出远程名称请求,从响应的移动终端获取远程名称,并显示获取的远程名称。 第一个移动终端 100 a 使用获取的远程名称选择第二至第n个移动终端 100 b 至 100 n 在参与者列表中。 [0138] 第一个移动终端 100 a 与第二至第n个移动终端进行配对 100 b 至 100 n ,并在步骤 S 中与它们中的每一个建立蓝牙连接 605 和 S 607 . 第一个移动终端 100 a 在第一移动终端上发送合成照片、照片片段信息和发送者终端信息 100 a 到第2到第n个移动终端 100 b 至 100 n 在步骤 S 609 和 S 611 . [0139] 第二至第n移动终端中的每一个 100 b 至 100 n 进一步对接收到的合成照片进行合成,并在步骤S中激活蓝牙模块传输合成的合成照片 613 和 S 615 . 例如,第二个移动终端 100 b 通过将拍摄的照片插入第二个照片部分,进一步合成接收到的合成照片 20 如图8C所示,第n个移动终端 100 n 通过将拍摄的照片插入第三个照片部分,进一步合成接收到的合成照片 30 如图 8D 所示。 [0140] 第二至第n移动终端中的每一个 100 b 至 100 n 列出获取的移动终端远程名称,并选择发送方移动终端 100 a 在步骤 S 617 和 S 619 . 第二至第n移动终端中的每一个 100 b 至 100 n 与第一移动终端进行配对 100 a 并在步骤 S 中与其建立蓝牙连接 621 和 S 623 . 第二至第n移动终端中的每一个 100 b 至 100 n 将合成照片发送至第一移动终端 100 a 在步骤 S 625 和 S 627 . [0141] 第一个移动终端 100 a 在步骤S中将接收到的合成照片组合成一张完整的合成照片 629 . 后来,第一个移动终端 100 a 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n 参加过复合摄影。 [0142] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如在 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101065339B1(String), KR1020100003847A(String), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.712 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.712 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.713 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101065339B1(String), KR1020100003847A(String), US20100004020A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.713 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.721 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101065339B1(String), KR1020100003847A(String), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270645(Integer), KR101065339B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.731 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.731 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.731 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270645(Integer), KR1020100003847A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270645(Integer), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100004020A1(String), US20100004020A1(String), 1262793600(Integer), 270645(Integer), 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184962(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184962(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974672(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184962(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75902(Integer), 2(Integer), 184962(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 放弃(String), 2(Integer), 184962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160156760A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal alarm method and device, and mobile terminal(String), 移动终端报警方法、装置、移动终端(String), US20160156760A1(String), Disclosed is an alarm method for a mobile terminal. After a pre-alarm function of the mobile terminal is enabled, pre-alarm information is generated and output when an input operation performed on the mobile terminal is detected. Moreover, an alarm device for a mobile terminal, and the mobile terminal provided with the alarm device are disclosed. By the technical solution of the disclosure, automatic pre-alarm can be implemented for a smart mobile terminal; when the mobile terminal is operated accidentally, a notification can be given to a user at once, thus the security of the mobile terminal is ensured, and the user experience is improved; moreover, the structure of the mobile terminal does not need to be changed, and the production cost can be saved.(String), 本发明公开了一种移动终端的报警方法。 开启移动终端的预警功能后,当检测到对移动终端的输入操作时,生成并输出预警信息。 此外,还公开了一种移动终端的告警装置及具有该告警装置的移动终端。 通过本发明的技术方案,可以实现智能移动终端的自动预警; 当移动终端被误操作时,可以第一时间通知用户,保证了移动终端的安全,提高了用户体验。 并且不需要改变移动终端的结构,可以节省生产成本。(String), US14/771609(String), 1377446400(Integer), US20160156760A1(String), 1464796800(Integer), 美国(String), 2(Integer), CN(String), 6(Integer), 1(Integer), US20090298469A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184963(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ef48547905ff4818b278a511bbd8512f.png(String), 184963(Integer), ef48547905ff4818b278a511bbd8512f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal alarm method and device, and mobile terminal(String), 移动终端报警方法、装置、移动终端(String), US20160156760A1(String), Disclosed is an alarm method for a mobile terminal. After a pre-alarm function of the mobile terminal is enabled, pre-alarm information is generated and output when an input operation performed on the mobile terminal is detected. Moreover, an alarm device for a mobile terminal, and the mobile terminal provided with the alarm device are disclosed. By the technical solution of the disclosure, automatic pre-alarm can be implemented for a smart mobile terminal; when the mobile terminal is operated accidentally, a notification can be given to a user at once, thus the security of the mobile terminal is ensured, and the user experience is improved; moreover, the structure of the mobile terminal does not need to be changed, and the production cost can be saved.(String), 本发明公开了一种移动终端的报警方法。 开启移动终端的预警功能后,当检测到对移动终端的输入操作时,生成并输出预警信息。 此外,还公开了一种移动终端的告警装置及具有该告警装置的移动终端。 通过本发明的技术方案,可以实现智能移动终端的自动预警; 当移动终端被误操作时,可以第一时间通知用户,保证了移动终端的安全,提高了用户体验。 并且不需要改变移动终端的结构,可以节省生产成本。(String), US14/771609(String), 1377446400(Integer), US20160156760A1(String), 1464796800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 6(Integer), 1(Integer), US20090298469A1(String), \20230420\ef48547905ff4818b278a511bbd8512f.png(String), 20(Integer), 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 1. An alarm method for a mobile terminal, after a pre-alarm function of the mobile terminal is enabled, the method comprising:generating and outputting pre-alarm information when detecting that an input operation is performed on the mobile terminal.(String), 1.移动终端,带有报警装置包含:处理模块,用于开启移动终端的预警功能,当检测到移动终端有输入操作时,生成预警信息;和输出模块,用于输出预警信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 2. The alarm method for a mobile terminal according to claim 1, before the pre-alarm function of the mobile terminal is enabled, the method further comprising:setting the pre-alarm function for the mobile terminal.(String), 12.根据权利要求2所述的移动终端的报警方法,其中为移动终端设置预警功能包括:创建预警功能菜单,在预警功能菜单中设置预警功能开关,并设置预警输出方式;其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 3. The alarm method for a mobile terminal according to claim 1, wherein setting the pre-alarm function for the mobile terminal comprises:creating a pre-alarm function menu, setting a pre-alarm function switch in the pre-alarm function menu and setting a pre-alarm output way;wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 13.根据权利要求12所述的移动终端的报警方法,其中检测到移动终端有输入操作时,生成并输出预警信息,包括:当检测到移动终端的触摸屏或功能键被按下或检测到移动终端的应用程序输入了启用指令时,生成预警信息,并根据设置输出预警信息预报警输出方式。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 4. The alarm method for a mobile terminal according to claim 3, wherein generating and outputting pre-alarm information when detecting that the input operation is performed on the mobile terminal comprises:when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal, generating the pre-alarm information, and outputting the pre-alarm information according to the set pre-alarm output way.(String), 14.根据权利要求7所述的移动终端报警装置,其中设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 5. The alarm method for a mobile terminal according to claim 1, further comprising:setting a pre-alarm area on a touch screen of the mobile terminal; andwhen the pre-alarm function is not enabled, enabling the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, disabling the pre-alarm function when detecting that the pre-alarm area is clicked; or, counting clicking times of continuously clicking the pre-alarm area, and enabling or disabling the pre-alarm function by counting the clicking times.(String), 15.根据权利要求14所述的移动终端报警装置,其中处理模块用于在检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用的启用指令时,生成预警信息。相应的,输出模块用于根据设置的预警输出方式输出预警信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 6. An alarm device for a mobile terminal, comprising a processing module and an output module, whereinthe processing module is configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; andthe output module is configured to output the pre-alarm information.(String), 16.根据权利要求11所述的移动终端,其中报警装置还包括设置模块,用于设置移动终端的预警功能。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 7. The alarm device for a mobile terminal according to claim 6, further comprising a setting module which is configured to set the pre-alarm function for the mobile terminal.(String), 17.根据权利要求11所述的移动终端,其中设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 8. The alarm device for a mobile terminal according to claim 6, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 18.根据权利要求16所述的移动终端,其中设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 9. The alarm device for a mobile terminal according to claim 8, wherein the processing module is configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal;and correspondingly, the output module is configured to output the pre-alarm information according to the set pre-alarm output way.(String), 19.根据权利要求17所述的移动终端,其中处理模块用于在检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用的启用指令时,生成预警信息。相应的,输出模块用于根据设置的预警输出方式输出预警信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 10. The alarm device for a mobile terminal according to claim 6, wherein the setting module is further configured to set a pre-alarm area on a touch screen of the mobile terminal; andcorrespondingly, when the pre-alarm function is not enabled, the processing module enables the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, the processing module disables the pre-alarm function when detecting that the pre-alarm area is clicked; or, the processing module counts clicking times of continuously clicking the pre-alarm area, and enables or disables the pre-alarm function by counting the clicking times.(String), 20.根据权利要求11所述的移动终端,其中设置模块还用于在移动终端的触摸屏上设置预警区域;和相应地,当预警功能未开启时,处理模块在检测到预警区域被点击时开启预警功能。当开启预警功能时,处理模块检测到预警区域被点击时,关闭预警功能。或者,处理模块统计连续点击预警区域的点击次数,通过统计点击次数来开启或关闭预警功能。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 11. A mobile terminal, provided with the alarm device which comprises:a processing module configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; andan output module configured to output the pre-alarm information.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 12. The alarm method for a mobile terminal according to claim 2, wherein setting the pre-alarm function for the mobile terminal comprises:creating a pre-alarm function menu, setting a pre-alarm function switch in the pre-alarm function menu and setting a pre-alarm output way;wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 13. The alarm method for a mobile terminal according to claim 12, wherein generating and outputting pre-alarm information when detecting that the input operation is performed on the mobile terminal comprises:when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal, generating the pre-alarm information, and outputting the pre-alarm information according to the set pre-alarm output way.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 14. The alarm device for a mobile terminal according to claim 7, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 15. The alarm device for a mobile terminal according to claim 14, wherein the processing module is configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal;and correspondingly, the output module is configured to output the pre-alarm information according to the set pre-alarm output way.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 16. The mobile terminal according to claim 11, wherein the alarm device further comprises a setting module which is configured to set the pre-alarm function for the mobile terminal.(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 17. The mobile terminal according to claim 11, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 18. The mobile terminal according to claim 16, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 19. The mobile terminal according to claim 17, wherein the processing module is configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal;and correspondingly, the output module is configured to output the pre-alarm information according to the set pre-alarm output way.(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:38.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184963(Integer), 20. The mobile terminal according to claim 11, wherein the setting module is further configured to set a pre-alarm area on a touch screen of the mobile terminal; andcorrespondingly, when the pre-alarm function is not enabled, the processing module enables the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, the processing module disables the pre-alarm function when detecting that the pre-alarm area is clicked; or, the processing module counts clicking times of continuously clicking the pre-alarm area, and enables or disables the pre-alarm function by counting the clicking times.(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184963(Integer), TECHNICAL FIELD [0001]The present disclosure relates to alarm technology, and more particularly to an alarm method and an alarm device for a mobile terminal, and the mobile terminal. BACKGROUND [0002]With the rapid development of the communication technology, user equipment becomes more and more popular. Particularly, a smart terminal, such as a smart phone, is more popular with users due to its fastness and convenience. Generally, the private information of a user, such as a bank card number and an ID number of a family member, is collected in the smart phone, which may bring convenience to the user but may also cause a security problem. When the smart phone is stolen or the private information is snooped, a loss may be caused to the user. [0003]At present, the following methods are adopted to ensure the security of information in the smart phone: a fingerprint identifier is built-in in the smart phone and the smart phone is started via the fingerprint of the user; or, the communication content, such as conversation and a short message, is encrypted and decrypted. Although the security of the information in the smart phone can be protected, the production cost of the smart phone may be increased undoubtedly by methods of arranging a fingerprint identifier in the smart phone which try to change the structure of the smart phone to achieve the aim of protecting the security of information. In terms of the method for ensuring the security by encrypting and decrypting the conversation content, interference information is usually added in a short message and cannot be found until the short message is decrypted successfully, thus, the waste of software and hardware processing resources of the smart phone is caused inevitably. SUMMARY [0004]In view of this, the main objective of the embodiments of the present disclosure is to provide an alarm method and device for a mobile terminal, and the mobile terminal, so as to implement automatic pre-alarm for a smart mobile terminal without changing the structure of the smart mobile terminal, improve the user experience, and save the production cost and the processing resources. [0005]To this end, the technical solution of the embodiments of the present disclosure is implemented as follows: [0006]An embodiment of the present disclosure provides an alarm method for a mobile terminal, after a pre-alarm function of the mobile terminal is enabled, the method includes: [0007]when it is detected that an input operation is performed on the mobile terminal, pre-alarm information is generated and output. [0008]In the solution, before the pre-alarm function of the mobile terminal is enabled, the method may further include that the pre-alarm function is set for the mobile terminal. [0009]In the solution, the step that the pre-alarm function is set for the mobile terminal may include: [0010]a pre-alarm function menu is created, a pre-alarm function switch is set in the pre-alarm function menu, and a pre-alarm output way is set, wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal. [0011]In the solution, the step that when it is detected that input operation is performed on the mobile terminal, pre-alarm information is generated and output may include: [0012]when it is detected that a touch screen or a function key of the mobile terminal is pressed or it is detected that an enabling instruction is input for an application of the mobile terminal, pre-alarm information is generated, and the pre-alarm information is output according to the set pre-alarm output way. [0013]In the solution, the method may further include: [0014]a pre-alarm area is set on the touch screen of the mobile terminal; [0015]when the pre-alarm function is not enabled, the pre-alarm function is enabled when it is detected that the pre-alarm area is clicked; when the pre-alarm function is enabled, the pre-alarm function is disabled when it is detected that the pre-alarm area is clicked; or, clicking times of continuously clicking the pre-alarm area is counted, and the pre-alarm function is enabled or disabled by counting the clicking times. [0016]An embodiment of the present disclosure further provides an alarm device for a mobile terminal, and the device includes a processing module and an output module, wherein [0017]the processing module is configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; and [0018]the output module is configured to output the pre-alarm information. [0019]In the solution, the device may further include a setting module which is configured to set the pre-alarm function for the mobile terminal. [0020]In the solution, the setting module may be further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way, wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal. [0021]In the solution, the processing module may be configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal; [0022]and correspondingly, the output module may be configured to output the pre-alarm information according to the set pre-alarm output way. [0023]In the solution, the setting module may be further configured to set a pre-alarm area on the touch screen of the mobile terminal; and [0024]correspondingly, when the pre-alarm function is not enabled, the processing module enables the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, the processing module disables the pre-alarm function when detecting that the pre-alarm area is clicked; or, the processing module counts clicking times of continuously clicking the pre-alarm area, and enables or disables the pre-alarm function by counting the clicking times. [0025]An embodiment of the present disclosure further provides a mobile terminal, which is provided with the alarm device in the above solutions. [0026]According to the alarm method and the alarm device for a mobile terminal, and the mobile terminal in which the alarm device is arranged provided by the embodiments of the present disclosure, the pre-alarm function is set to be enabled; when it is detected that the touch screen or the function key of the mobile terminal is pressed or it is detected that an enabling instruction is input for an application of the mobile terminal, the pre-alarm information is generated; and the pre-alarm information is output according to the set pre-alarm output way. Through the technical solution of the embodiments of the present disclosure, automatic pre-alarm can be implemented for a smart mobile terminal; when the mobile terminal is operated accidentally, a notification can be given to a user at once, so that the security of the mobile terminal is ensured, and the user experience is improved; moreover, the structure of the mobile terminal does not need to be changed, and the production cost can be saved. BRIEF DESCRIPTION OF THE DRAWINGS [0027]FIG. 1 is a schematic diagram showing the flow of an alarm method for a mobile terminal according to an embodiment of the present disclosure; and [0028]FIG. 2 is a schematic diagram showing the composition structure of an alarm device for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0029]An embodiment of the present disclosure provides an alarm method for a mobile terminal, as shown in FIG. 1, the method includes: [0030]Step 11: A pre-alarm function of the mobile terminal is enabled. [0031]Here, the pre-alarm function is set for the mobile terminal in advance. The step that the pre-alarm function is set for the mobile terminal may include: a pre-alarm function menu is created, a pre-alarm function is set to be enabled in the pre-alarm function menu, and a pre-alarm output way is set, wherein the pre-alarm output way includes an audio way, a video way or a combined way of audio and video. The mobile terminal includes a smart phone and a feature phone. [0032]A pre-alarm area is set on a touch screen of the mobile terminal; when the pre-alarm function is not enabled, the pre-alarm function is enabled when it is detected that the pre-alarm area is clicked; when the pre-alarm function is enabled, the pre-alarm function is disabled when it is detected that the pre-alarm area is clicked; or, clicking times of continuously clicking the pre-alarm area is counted, and the pre-alarm function is enabled or disabled by counting the click times, for example, the pre-alarm function is enabled if the counted times is an odd number and the pre-alarm function is disabled if the counted times is an even number. [0033]Step 12: When it is detected that an input operation is performed on the mobile terminal, alarm information is generated and output. [0034]In the embodiment, the pre-alarm information includes at least one of the following ways: ringtone, vibration and touch panel glittering. The pre-alarm information is different from a call or short message reminder message of the mobile terminal. [0035]A pre-alarm identifier 1 represents that the pre-alarm function of the smart phone is enabled, and a pre-alarm identifier 0 represents that the pre-alarm function is disenabled. [0036]When the pre-alarm function is enabled, namely, the pre-alarm identifier is 1, pre-alarm information, such as ringtone, is generated and output when it is detected that the touch screen or the function key of the mobile terminal is pressed. [0037]Or, when the pre-alarm function is enabled, namely, the pre-alarm identifier is 1, pre-alarm information, such as ringtone, may be generated and output when it is detected that an enabling instruction is input for an application of the mobile terminal, such as a message box and a phone book. For example, when a message box button or a phone book button is clicked, pre-alarm information such as ringtone is generated and output. [0038]After the pre-alarm function is enabled, the screen of the mobile terminal is locked if it is detected that no input operation is performed on the mobile terminal within a preset time, wherein the preset time can be adjusted according to the frequency of utilization of the mobile terminal. [0039]Based on the alarm method for a mobile terminal, an embodiment of the present disclosure further provides an alarm device for a mobile terminal. FIG. 2 is a schematic diagram showing the composition structure of an alarm device for a mobile terminal, as shown in FIG. 2, the device includes a processing module 22 and an output module 23, wherein [0040]the processing module 22 is configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; and [0041]the output module 23 is configured to output the pre-alarm information. [0042]Preferably, the device further includes a setting module 21, wherein the setting module 21 is configured to set a pre-alarm function for the mobile terminal and is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu and set a pre-alarm output way; the pre-alarm information is different from a call or a short message reminder message of the mobile terminal. [0043]The processing module 22 is configured to enable the pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or an enabling instruction is input for an application of the mobile terminal, such as clicking a message box button or a phone book button; [0044]and correspondingly, the output module 23 is configured to output the pre-alarm information according to the set pre-alarm output way. [0045]The pre-alarm output way includes: an audio way, a video way or a combined way of audio and video; and correspondingly, the pre-alarm information includes at least one of the following ways: ringtone, vibration and touch panel glittering. [0046]The setting module 21 is further configured to set a pre-alarm area in the pre-alarm function menu; correspondingly, when the pre-alarm function is not enabled, the pre-alarm function is enabled when the processing module 22 detects that the pre-alarm area is clicked; when the pre-alarm function is enabled, the pre-alarm function is disabled when the processing module 22 detects that the pre-alarm area is clicked; or, the processing module 22 counts clicking times of continuously clicking the pre-alarm area and enables or disables the pre-alarm function by counting the clicking times. For example, the pre-alarm function is enabled when the clicking times is an odd number and is disabled when the clicking times is an even number. [0047]After the pre-alarm function is enabled, the screen of the mobile terminal is locked if the processing module 22 detects that no input operation is performed on the mobile terminal within a preset time, wherein the preset time is preset in the processing module 22 and can be adjusted according to the frequency of utilization of the mobile terminal. [0048]In the actual application, the setting module 21, the processing module 22 and the output module 23 can be implemented by the Central Processing Unit (CPU), the Digital Signal Processor (DSP) or the Field Programmable Gate Array (FPGA) and the like; and the CPU, DSP and FPGA can be arranged in the mobile terminal. [0049]Those skilled in the art shall understand that the implementing functions of each processing module in the alarm device for a mobile terminal in FIG. 2 can be understood in reference to the related description of the alarm method for a mobile terminal. Those skilled in the art shall understand that the function of each processing unit of the alarm device for a mobile terminal in FIG. 2 can be implemented either by a program running on a processor or by a specific logic circuit. [0050]The present disclosure further records a mobile terminal, including the alarm device in FIG. 2. [0051]According to the alarm method and the alarm device for a mobile terminal, and the mobile terminal provided by the embodiments of the present disclosure, a pre-alarm function is set to be enabled at first, and after the pre-alarm function of the mobile terminal is enabled, when it is detected that the touch screen or the function key of the mobile terminal is pressed or it is detected that an enabling instruction is input for an application of the mobile terminal, pre-alarm information is generated, and the pre-alarm information is output according to a set pre-alarm output way to remind a user that the mobile terminal is being turned on. Through the technical solution of the embodiments of the present disclosure, automatic pre-alarm can be implemented on the smart mobile terminal without changing the structure of the smart mobile terminal, thereby saving the production cost and the processing resources, and improving the user experience. [0052]Provided with the alarm device, the mobile terminal in the embodiment of the present disclosure also has the technical effects. [0053]The above are only the preferred embodiments of the present disclosure, and are not intended to limit the scope of protection of the claims of the present disclosure.(String), 技术领域 [0001] 本发明涉及报警技术,尤其涉及一种移动终端的报警方法、报警装置及移动终端。 背景 [0002] 随着通信技术的飞速发展,用户设备越来越普及。 尤其是智能终端,如智能手机,以其快捷、方便等特点更受用户欢迎。 通常,智能手机中收集了用户的隐私信息,如银行卡号、家庭成员的身份证号等,这在给用户带来方便的同时也可能带来安全问题。 当智能手机被盗或隐私信息被窥探时,可能会给用户造成损失。 [0003] 目前,为保证智能手机信息安全,主要有以下几种方式: 智能手机内置指纹识别器,通过用户指纹启动智能手机; 或者,对通话、短信等通信内容进行加密解密。 虽然可以保护智能手机中信息的安全,但通过在智能手机中设置指纹识别器,试图改变智能手机的结构来达到目的,无疑会增加智能手机的生产成本。 保护信息安全。 对于通过对通话内容进行加解密来保证安全的方法,通常在短信中加入干扰信息,只有在短信解密成功后才能发现干扰信息,浪费了终端的软硬件处理资源。 智能手机是不可避免的。 概括 [0004] 有鉴于此,本发明实施例的主要目的在于提供一种移动终端的报警方法、装置及移动终端,以在不改变结构的情况下实现智能移动终端的自动预警。 智能移动终端,提升用户体验,节约生产成本和加工资源。 [0005] 为此,本发明实施例的技术方案是这样实现的: [0006] 本发明实施例提供了一种移动终端的报警方法,在开启移动终端的预警功能后,该方法包括: [0007] 当检测到移动终端有输入操作时,生成并输出预警信息。 [0008] 上述方案中,在开启移动终端的预警功能之前,该方法还可以包括:为移动终端设置预警功能。 [0009] 上述方案中,为移动终端设置预警功能的步骤可以包括: [0010] 创建预警功能菜单,在预警功能菜单中设置预警功能开关,并设置预警输出方式,其中预警信息不同于来电或短信提醒 移动终端的消息。 [0011] 上述方案中,所述在检测到移动终端有输入操作时,生成并输出预警信息的步骤可以包括: [0012] 当检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用程序的启用指令时,生成预警信息,该预警信息为 按设置的预警输出方式输出。 [0013] 上述方案中,所述方法还可以包括: [0014] 在移动终端的触摸屏上设置预警区域; [0015] 当未开启预警功能时,检测到点击预警区域时开启预警功能; 当开启预警功能时,检测到点击预警区域时关闭预警功能; 或者,对连续点击预警区域的点击次数进行统计,通过对点击次数的统计来开启或关闭预警功能。 [0016] 本发明实施例还提供了一种移动终端的报警装置,该装置包括处理模块和输出模块,其中 [0017] 处理模块,用于开启移动终端的预警功能,当检测到移动终端有输入操作时,生成预警信息; 和 [0018] 输出模块,用于输出预警信息。 [0019] 上述方案中,所述装置还包括设置模块,用于为所述移动终端设置预警功能。 [0020] 上述方案中,设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息 不同于移动终端的来电或短信提醒消息。 [0021] 上述方案中,所述处理模块,具体用于在检测到所述移动终端的触摸屏或功能键被按下时,或者检测到输入了对所述移动终端的应用的启用指令时,生成所述预警信息; [0022] 相应的,输出模块可以用于根据设置的预警输出方式输出预警信息。 [0023] 上述方案中,所述设置模块还用于在所述移动终端的触摸屏上设置预警区域; 和 [0024] 相应地,当预警功能未开启时,处理模块在检测到预警区域被点击时开启预警功能。 当开启预警功能时,处理模块检测到预警区域被点击时,关闭预警功能。 或者,处理模块统计连续点击预警区域的点击次数,通过统计点击次数来开启或关闭预警功能。 [0025] 本发明实施例还提供了一种移动终端,包括上述方案中的报警装置。 [0026] 本发明实施例提供的移动终端的报警方法、报警装置及设置有报警装置的移动终端,设置为开启预警功能; 当检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用程序的启用指令时,生成预警信息。 并按照设置的预警输出方式输出预警信息。 通过本发明实施例的技术方案,可以实现智能移动终端的自动预警; 当移动终端被误操作时,可以第一时间通知用户,保证了移动终端的安全,提高了用户体验。 并且不需要改变移动终端的结构,可以节省生产成本。 附图的简要说明 [0027] 图1为本发明实施例提供的移动终端告警方法的流程示意图; 和 [0028] 图2为本发明实施例的移动终端报警装置的组成结构示意图。 详细说明 [0029] 本发明实施例提供了一种移动终端的告警方法,如图1所示,该方法包括: [0030] 步 11 :开启移动终端预警功能。 [0031]这里,预先为移动终端设置了预警功能。 为移动终端设置预警功能的步骤可以包括:创建预警功能菜单,在预警功能菜单中设置开启预警功能,并输出预警信号。 设置方式,其中,预警输出方式包括音频方式、视频方式或音视频结合方式。 移动终端包括智能手机和功能手机。 [0032] 在移动终端的触摸屏上设置预警区域; 当未开启预警功能时,检测到点击预警区域时开启预警功能; 当开启预警功能时,检测到点击预警区域时关闭预警功能; 或者,对连续点击预警区域的点击次数进行计数,通过对点击次数的计数来开启或关闭预警功能,例如,如果计数次数为奇数,则开启预警功能; 如果计数次数为偶数,则禁用预警功能。 [0033] 步 12 :当检测到移动终端有输入操作时,产生并输出告警信息。 [0034] 在本实施例中,预警信息包括以下方式中的至少一种:铃声、振动、触摸屏闪烁。 预警信息不同于移动终端的来电或短信提醒消息。 [0035] 预警标识符 1 表示开启智能手机的预警功能,预警标识0表示关闭预警功能。 [0036] 当开启预警功能,即预警标识为1时,检测到触摸屏或移动终端的功能键被按下时,产生并输出铃声等预警信息 . [0037] 或者,当开启预警功能时,即预警标识为1时,可以在检测到为应用程序输入开启指令时,生成并输出铃声等预警信息。 移动端,如消息框、电话簿。 例如,当点击消息框按钮或电话簿按钮时,生成并输出铃声等预警信息。 [0038] 开启预警功能后,如果检测到在预设时间内没有对移动终端进行任何输入操作,则锁定移动终端的屏幕,其中,预设时间可以根据用户的使用频率进行调整。 移动终端。 [0039] 基于上述移动终端的报警方法,本发明实施例还提供了一种移动终端的报警装置。 图2为一种移动终端报警装置的组成结构示意图,如图2所示,该装置包括处理模块 22 和一个输出模块 23 , 其中 [0040] 处理模块 22 用于开启移动终端的预警功能,当检测到移动终端有输入操作时,生成预警信息; 和 [0041] 输出模块 23 用于输出预警信息。 [0042] 优选地,所述装置还包括设置模块 21 , 其中设置模块 21 用于为移动终端设置预警功能,进一步用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式。 预警信息不同于移动终端的来电或短信提醒消息。 [0043] 处理模块 22 用于开启移动终端的预警功能,当检测到移动终端的触摸屏或功能键被按下,或者为移动终端的应用输入开启指令时,生成预警信息, 例如点击消息框按钮或电话簿按钮; [0044]相应地,输出模块 23 用于按照设置的预警输出方式输出预警信息。 [0045] 预警输出方式包括:音频方式、视频方式或音视频结合方式; 相应的,所述预警信息包括以下至少一种方式:铃声、振动、触摸屏闪烁。 [0046] 设置模块 21 还用于在预警功能菜单中设置预警区域; 相应地,当预报警功能未开启时,处理模块开启预报警功能 22 检测到预警区域被点击; 预报警功能开启时,处理模块预报警功能关闭 22 检测到预警区域被点击; 或者,处理模块 22 统计连续点击预警区域的点击次数,通过统计点击次数来开启或关闭预警功能。 例如,当点击次数为奇数时开启预警功能,当点击次数为偶数时关闭预警功能。 [0047] 启用预警功能后,如果处理模块锁定移动终端屏幕 22 检测到移动终端在预设时间内没有输入操作,该预设时间预先设置在处理模块中 22 并且可以根据移动终端的使用频率进行调整。 [0048] 在实际应用中,设置模块 21 , 处理模块 22 和输出模块 23 可由中央处理器(CPU)、数字信号处理器(DSP)或现场可编程门阵列(FPGA)等实现; CPU、DSP和FPGA可以设置在移动终端中。 [0049] 本领域技术人员应当理解,图2中的移动终端报警装置中各处理模块的实现功能可以参照移动终端报警方法的相关描述来理解。 本领域的技术人员应该理解,图2中的移动终端报警装置的各处理单元的功能可以通过运行在处理器上的程序实现,也可以通过具体的逻辑电路实现。 [0050] 本发明还记载了一种移动终端,包括图2中的报警装置。 [0051] 本发明实施例提供的移动终端的报警方法、报警装置及移动终端,首先设置开启预警功能,开启手机的预警功能后 终端开启时,当检测到移动终端的触摸屏或功能键被按下或检测到移动终端的应用输入了开启指令时,产生预警信息,并预报警 -按照设定的预报警输出方式输出报警信息,提醒用户移动终端正在开机。 通过本发明实施例的技术方案,可以在不改变智能移动终端结构的情况下,在智能移动终端上实现自动预警,节省了生产成本和处理资源,提高了用户体验。 [0052] 设置有报警装置,本发明实施例的移动终端还具有技术效果。 [0053] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104023118A(String), EP2963903A2(String), EP2963903A4(String), EP2963903B1(String), JP2016513435A(String), KR1020150123880A(String), US20160156760A1(String), WO2013189439A2(String), WO2013189439A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104023118A(String), EP2963903A2(String), EP2963903A4(String), EP2963903B1(String), JP2016513435A(String), KR1020150123880A(String), US20160156760A1(String), WO2013189439A2(String), WO2013189439A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20160156760A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104023118A(String), EP2963903A2(String), EP2963903A4(String), EP2963903B1(String), JP2016513435A(String), KR1020150123880A(String), US20160156760A1(String), WO2013189439A2(String), WO2013189439A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), CN104023118A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), EP2963903A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.080 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.080 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), EP2963903A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.092 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), EP2963903B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), JP2016513435A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), KR1020150123880A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), US20160156760A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), WO2013189439A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.140 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.140 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.140 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270646(Integer), WO2013189439A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20160156760A1(String), US20160156760A1(String), 1464796800(Integer), 270646(Integer), 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184963(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184963(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184963(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184963(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.190 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.190 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.191 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.191 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.206 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130111351A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for remotely controlling mobile terminal and mobile terminal(String), 远程控制移动终端的方法及移动终端(String), US20130111351A1(String), The present invention discloses a method for remotely controlling a mobile terminal and a mobile terminal, wherein the method comprises: receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; and sending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled. By way of the present invention, the effect of remotely controlling mobile terminals is achieved, and the application of assisting others to solve problems or sharing a mobile terminal with others via videophones is achieved, which greatly enriches the contents of videophones and provides wider application space for the business application of videophones.(String), 本发明公开了一种移动终端的远程控制方法及移动终端,该方法包括: 第一移动终端接收对待控界面的触屏操作, 发送待控界面 第二移动终端在视频通话过程中,获取该操作的第一触屏坐标; 第一移动终端将第一触屏坐标转换为待控制界面的界面坐标; 第一移动终端向第二移动终端发送界面坐标,以控制待控制界面。 通过本发明,实现了远程控制移动终端的效果,实现了通过可视电话协助他人解决问题或与他人共享移动终端的应用,极大的丰富了可视电话的内容,提供了更广阔的应用空间 用于可视电话的商业应用。(String), US13/259707(String), 1289491200(Integer), US20130111351A1(String), 1367424000(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 9(Integer), US20060015598A1 | US20080148316A1 | US20080256472A1 | US20090104943A1 | US20090298469A1 | US20100321379A1 | US20110231796A1 | US6325756B1 | US7120433B2(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184964(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\4dc9c8e2a6bb4930bc853e0ccb131664.png(String), 184964(Integer), 4dc9c8e2a6bb4930bc853e0ccb131664.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for remotely controlling mobile terminal and mobile terminal(String), 远程控制移动终端的方法及移动终端(String), US20130111351A1(String), The present invention discloses a method for remotely controlling a mobile terminal and a mobile terminal, wherein the method comprises: receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; and sending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled. By way of the present invention, the effect of remotely controlling mobile terminals is achieved, and the application of assisting others to solve problems or sharing a mobile terminal with others via videophones is achieved, which greatly enriches the contents of videophones and provides wider application space for the business application of videophones.(String), 本发明公开了一种移动终端的远程控制方法及移动终端,该方法包括: 第一移动终端接收对待控界面的触屏操作, 发送待控界面 第二移动终端在视频通话过程中,获取该操作的第一触屏坐标; 第一移动终端将第一触屏坐标转换为待控制界面的界面坐标; 第一移动终端向第二移动终端发送界面坐标,以控制待控制界面。 通过本发明,实现了远程控制移动终端的效果,实现了通过可视电话协助他人解决问题或与他人共享移动终端的应用,极大的丰富了可视电话的内容,提供了更广阔的应用空间 用于可视电话的商业应用。(String), US13/259707(String), 1289491200(Integer), US20130111351A1(String), 1367424000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 9(Integer), US20060015598A1 | US20080148316A1 | US20080256472A1 | US20090104943A1 | US20090298469A1 | US20100321379A1 | US20110231796A1 | US6325756B1 | US7120433B2(String), \20230420\4dc9c8e2a6bb4930bc853e0ccb131664.png(String), 16(Integer), 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.264 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.264 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 1. A method for remotely controlling a mobile terminal, comprising:receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation;converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; andsending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled.(String), 1.根据权利要求2所述的方法,其中第一移动终端将第一触屏坐标转换为待控制界面的界面坐标的步骤包括:第一移动终端根据第一触屏坐标、第一移动终端的触屏分辨率和视频分辨率,将第一触屏坐标转换为待控制界面的界面坐标。第一个移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 2. The method according to claim 1, wherein the method further comprises:receiving, by the second mobile terminal, the interface coordinate;converting the interface coordinate into a second touch-screen coordinate of the second mobile terminal; andperforming operation control to the interface to be controlled according to the second touch-screen coordinate.(String), 12.根据权利要求2所述的方法,其中第一移动终端向第二移动终端发送界面坐标的步骤包括:第一移动终端将接口坐标封装成H.245协议的坐标消息,坐标消息用于传输接口坐标的信息;和向第二移动终端发送坐标消息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 3. The method according to claim 1, wherein the step of converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled comprises:converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the first mobile terminal, and a video resolution of the first mobile terminal.(String), 13.根据权利要求2所述的方法,其中在第一移动终端接收视频通话中第二移动终端发送的对待控制界面的触屏操作之前,还包括:第一移动终端和第二移动终端通过H.245协议进行触屏信息传递能力交互,触屏信息传递能力用于支持第一移动终端和第二移动终端传递触屏信息界面坐标信息;和确认第一移动终端和第二移动终端均支持触屏信息传递能力。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 4. The method according to claim 1, wherein the step of sending, by the first mobile terminal, the interface coordinate to the second mobile terminal comprises:encapsulating, by the first mobile terminal, the interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transmitting the information of the interface coordinate; andsending the coordinate message to the second mobile terminal.(String), 14.根据权利要求7所述的移动终端,其中第一转换模块,用于根据第一触摸屏坐标、移动终端触摸屏的分辨率和移动终端的视频分辨率,将第一触摸屏坐标转换为待控制界面的第一界面坐标。移动终端。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 5. The method according to claim 1, wherein before the step of receiving, by the first mobile terminal, the touch-screen operation to the interface to be controlled sent by a second mobile terminal during a video call, the method further comprises:performing, by the first mobile terminal and the second mobile terminal, touch-screen information transfer capability exchange using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the first mobile terminal and the second mobile terminal to transfer the interface coordinate information; andconfirming that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 15.根据权利要求7所述的移动终端,其中第一控制模块包括:封装模块,用于将第一接口坐标封装成H.245协议的坐标消息,坐标消息用于传递接口坐标的信息;和发送模块,用于向所述另一移动终端发送所述坐标消息,以控制所述另一移动终端的待控制界面。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 6. A mobile terminal, comprising:an acquiring module, configured to receive a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by the other mobile terminal during a video call, and acquire a first touch-screen coordinate of the operation;a first converting module, configured to convert the first touch-screen coordinate into a first interface coordinate of the interface to be controlled; anda first control module, configured to send the first interface coordinate to the other mobile terminal to control the interface to be controlled.(String), 16.根据权利要求7所述的移动终端,其中移动终端还包括:交换模块,用于通过H.245协议与其他移动终端进行触屏信息传递能力交换,所述触屏信息传递能力用于支持移动终端与其他移动终端传递界面坐标信息;和确认模块,用于确认第一移动终端和第二移动终端均支持触屏信息传递能力。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 7. The mobile terminal according to claim 6, wherein the mobile terminal further comprises:a receiving module, configured to receive a second interface coordinate sent by the other mobile terminal;a second converting module, configured to convert the second interface coordinate into a second touch-screen coordinate; anda second control module, configured to perform operation control to the interface to be controlled of the mobile terminal according to the second touch-screen coordinate.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 8. The mobile terminal according to claim 6, wherein the first converting module is configured to convert the first touch-screen coordinate into the first interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the mobile terminal and a video resolution of the mobile terminal.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 9. The mobile terminal according to claim 6, wherein the first control module comprises:an encapsulating module, configured to encapsulate the first interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transferring the information of the interface coordinate; anda sending module, configured to send the coordinate message to the other mobile terminal to control the interface to be controlled of the other mobile terminal.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 10. The mobile terminal according to claim 6, wherein the mobile terminal further comprises:an exchanging module, configured to perform touch-screen information transfer capability exchange with the other mobile terminal using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the mobile terminal and the other mobile terminal to transfer interface coordinate information; anda confirmation module, configured to confirm that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 11. The method according to claim 2, wherein the step of converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled comprises:converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the first mobile terminal, and a video resolution of the first mobile terminal.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 12. The method according to claim 2, wherein the step of sending, by the first mobile terminal, the interface coordinate to the second mobile terminal comprises:encapsulating, by the first mobile terminal, the interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transmitting the information of the interface coordinate; andsending the coordinate message to the second mobile terminal.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 13. The method according to claim 2, wherein before the step of receiving, by the first mobile terminal, the touch-screen operation to the interface to be controlled sent by a second mobile terminal during a video call, the method further comprises:performing, by the first mobile terminal and the second mobile terminal, touch-screen information transfer capability exchange using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the first mobile terminal and the second mobile terminal to transfer the interface coordinate information; andconfirming that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 1(Integer), 12(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 14. The mobile terminal according to claim 7, wherein the first converting module is configured to convert the first touch-screen coordinate into the first interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the mobile terminal and a video resolution of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 15. The mobile terminal according to claim 7, wherein the first control module comprises:an encapsulating module, configured to encapsulate the first interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transferring the information of the interface coordinate; anda sending module, configured to send the coordinate message to the other mobile terminal to control the interface to be controlled of the other mobile terminal.(String), 1(Integer), 14(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184964(Integer), 16. The mobile terminal according to claim 7, wherein the mobile terminal further comprises:an exchanging module, configured to perform touch-screen information transfer capability exchange with the other mobile terminal using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the mobile terminal and the other mobile terminal to transfer interface coordinate information; anda confirmation module, configured to confirm that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 1(Integer), 15(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184964(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, and in particular to a method for remotely controlling a mobile terminal and a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the rapid development of mobile multimedia services and the gradual business application of 3G domestically, the videophone service, which has been developed and applied in the personal communication field rapidly, becomes the landmark service of 3G. The Videophone service is a point-to-point video communication service, which can make use of the telephone network to transmit the images and voice signals of the call parties bi-directionally and in real time. The video terminals can achieve an effect of face-to-face communication and realize the dream of “hear the voice and also see the people” when calling. [0003]However, when this new function of videophone is used, the following situations such as: the users do not know how to use one certain function of the mobile terminal and need the assistance of others; or the terminal cannot be used normally and needs the assistance of others to analyze the reason; or it is desired to share the contents in this terminal with other users during calling, may also often appear in practical application. [0004]As to the above situations, a video terminal and a method for achieving the share of interface contents thereof are provided in the related art. According to the method, a switch unit and an interface content processing unit are set in the video terminal, wherein the switch unit is used for receiving the switch instructions from the outside and selecting to acquire video data by a viewfinder or acquire cache data by an LCD data display cache area to collect sending data; and the interface content processing unit is used for processing the data from the LCD data display cache area and converting the same to the data which complies with the encoding input format requirements and outputting the same. During the video call, the real-time share of the terminal interface contents during video call is achieved in manner of the data transmission of video call through the switch requirements of the user and the interface content processing unit. Herein, the terminal which initiates the share is defined as a second terminal, and the other party is a first terminal In this method, although the first terminal can share the current interface contents of the second terminal, the first terminal can only accept the current interface of the second terminal passively but cannot operate the current interface actively, such as switch the interface actively and so on. Therefore, the remote coordination control demands of the users still cannot be satisfied. SUMMARY OF THE INVENTION [0005]According to the present invention, a method for remotely controlling a mobile terminal and a mobile terminal are provided to solve the above problem that the remote coordination control demands of the users cannot be satisfied by the video mobile terminal. [0006]According to one aspect of the present invention, a method for remotely controlling a mobile terminal is provided, wherein the method comprises: receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; and sending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled. [0007]Furthermore, this method for remotely controlling a mobile terminal further comprises: receiving, by the second mobile terminal, the interface coordinate; converting the interface coordinate into a second touch-screen coordinate of the second mobile terminal; and performing operation control to the interface to be controlled according to the second touch-screen coordinate. [0008]Furthermore, the step of converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled comprises: converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the first mobile terminal, and a video resolution of the first mobile terminal. [0009]Furthermore, the step of sending, by the first mobile terminal, the interface coordinate to the second mobile terminal comprises: encapsulating, by the first mobile terminal, the interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transmitting the information of the interface coordinate; and sending the coordinate message to the second mobile terminal. [0010]Furthermore, before the step of receiving, by the first mobile terminal, a touch-screen operation to the interface to be controlled sent by a second mobile terminal during a video call, the method further comprises: performing, by the first mobile terminal and the second mobile terminal, touch-screen information transfer capability exchange using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the first mobile terminal and the second mobile terminal to transfer the interface coordinate information; and confirming that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability. [0011]According to another aspect of the present invention, a mobile terminal is provided, wherein the mobile terminal comprises: an acquiring module, configured to receive a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by the other mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; a first converting module, configured to convert the first touch-screen coordinate into a first interface coordinate of the interface to be controlled; and a first control module, configured to send the first interface coordinate to the other mobile terminal to control the interface to be controlled. [0012]Furthermore, this mobile terminal further comprises: a receiving module, configured to receive a second interface coordinate sent by the other mobile terminal; a second converting module, configured to convert the second interface coordinate into a second touch-screen coordinate; and a second control module, configured to perform operation control to the interface to be controlled of the mobile terminal according to the second touch-screen coordinate. [0013]Furthermore, the first converting module is configured to convert the first touch-screen coordinate into the first interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the mobile terminal and a video resolution of the mobile terminal. [0014]Furthermore, the first control module comprises: an encapsulating module, configured to encapsulate the first interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transferring the information of the interface coordinate; and a sending module, configured to send the coordinate message to the other mobile terminal to control the interface to be controlled of the other mobile terminal. [0015]Furthermore, this mobile terminal further comprises: an exchange module, configured to perform touch-screen information transfer capability exchange with another mobile terminal using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the mobile terminal and the other mobile terminal to transfer interface coordinate information; and a confirmation module, configured to confirm that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability. [0016]By way of the present invention, the problem in the related art that the video mobile terminal cannot meet the remote coordination control demand of the users is solved by using a first mobile terminal to perform operation control to the application interface of a second mobile terminal via a videophone and a touch screen, the effect of remotely controlling mobile terminals is achieved, and the application of assisting others to solve problems or sharing a mobile terminal with others via videophones is achieved, which greatly enriches the contents of videophones and provides wider application space for the business application of videophones. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The drawings illustrated here provide a further understanding of the present invention and form a part of the present application. The exemplary embodiments and the description thereof are used to explain the present invention without unduly limiting the present invention, wherein: [0018]FIG. 1 is a schematic diagram of the data structure of a capability set according to an embodiment of the present invention; [0019]FIG. 2 is a schematic diagram of a capability format according to an embodiment of the present invention; [0020]FIG. 3 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment I of the present invention; [0021]FIG. 4 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment II of the present invention; [0022]FIG. 5 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment III of the present invention; [0023]FIG. 6 is a schematic diagram of a coordinate transfer and conversion process according to an embodiment of the present invention; [0024]FIG. 7 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment IV of the present invention; [0025]FIG. 8 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment V of the present invention; [0026]FIG. 9 is a structural block diagram of a mobile terminal according to Embodiment VI of the present invention; [0027]FIG. 10 is a structural block diagram of mobile terminals according to Embodiment VII of the present invention; and [0028]FIG. 11 is a flow chart of the steps of applying the mobile terminals shown in FIG. 10 to perform remote control. DETAILED DESCRIPTION OF THE EMBODIMENTS [0029]The embodiments of the present invention will be described hereinafter in detail in conjunction with the drawings thereof. It needs to be noted that the embodiments of the present application and the features in the embodiments can be combined with each other if no conflict exists. [0030]All the mobile terminals related in the embodiments of the present invention support videophone and are touch-screen mobile terminals. [0031]In the mobile videophone field, the most common communication protocol is the H.324 protocol set, which includes the H.223 multiplexing protocol, the H.245 system control protocol, the H.263 video encoding protocol, the G.723.1 audio encoding protocol and so on. The method of a video mobile terminal performing remote control and the video mobile terminal according to the embodiments of the present invention are based on the H.324 video communication protocol and make certain supplement to the H.245 control protocol to achieve remote control. [0032]The H.245 protocol is a control signaling protocol and mainly used for the end-to-end H.245 information exchange between terminals which are communicating. In the H.245 protocol, the capability exchange process is a process which needs to be firstly carried out after the establishment of H.245 call, the objective of which is to ensure that the sent multimedia signals can be received and encoded by a terminal. The terminal enables the other side to know the capability combination which the terminal can receive by sending its “capability set”. The other side does not have to understand all these capabilities, and the other side only needs to store the capability portion which can be understood and may be used so as to facilitate the other side to establish a logic channel. [0033]The terminal capability set contains a capability table in a message, wherein the table lists all the operation modes allowed by the terminal and each mode is assigned with a corresponding sequence number (capability number). Several capability numbers consist of a “selectable capability set” structure, which describes a media channel capability of the terminal and indicates that the terminal can work based on any mode therein. Several “selectable capability set” consist of a “simultaneous capability” structure, which indicates that this terminal can use a set of capabilities to work simultaneously. At last, several “simultaneous capability” can further consist of a “capability description set” structure, which contains a set of capability descriptions, with each description consisted of a simultaneous capability and a capability description sequence number. This data structure gives the total capability of the terminal, the particular data structure of which is as shown in FIG. 1. [0034]In the present invention, the characteristics of the above H.245 protocol are used and new capabilities are defined in the H.245 capability set: touch-screen information transfer capability, which supports the call parties to transfer coordinate information; and new message types are defined in the H.245 protocol, i.e. coordinate message, so as to enable the terminals which have touch-screen information transfer capability to send, receive, and feed back the coordinate information. [0035]In particular, the new touch-screen information transfer capability defined in the H.245 is as follows: [0036]H.245 uses ASN.1 (Abstract Syntax Notation 1) standard to define its own message structure, the message data of which uses binary encoding based on PER (Packed Encoding Rule) rule. The above capability definition format in the embodiments of the present invention is as shown in FIG. 2. [0037]According to the above capability format, the new coordinate message defined in the H.245 protocol of the embodiments of the present invention is as follows: [0038]the representation mode of coordinate message format and that of ordinary messages are consistent, and the difference only lies in the type field in the message (the corresponding type is “coordinate information”) which is used for differentiating from other message types. In addition, the coordinate location information is converted into data which complies with the encoding input format requirements and outputted and delivered in the videophone. [0039]The mobile terminal initiates an operation (such as click to select and pull) using the touch screen via the touch point coordinate information, and transfers the coordinate information during the video call using the new touch-screen information transfer capability and the coordinate message defined in H.245 to remotely control another mobile terminal, thus greatly facilitating the use of users, meeting the demand of users to perform remote cooperation control, and also accelerating the popularization of video terminals. [0040]All the mobile terminals in the following embodiments of the present invention can use the above improved H.245 protocol. [0041]Referring to FIG. 3, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment I of the present invention, and the method comprises the following steps. [0042]Step S102: a first mobile terminal receives a touch-screen operation of an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and the first mobile terminal acquires a first touch-screen coordinate of this operation. [0043]In this step, when the first mobile terminal receives the application interface to be controlled of the second mobile terminal sent by the second mobile terminal during the video call, the user of the first mobile terminal performs operation to this application interface using a touch screen, such as click or pull, etc., so as to achieve the remote control of a corresponding application interface on the second mobile terminal. At this moment, the first mobile terminal acquires the coordinate when the user performs operation to the touch screen, i.e. the first touch-screen coordinate. If this operation is the click operation, then the touch-screen coordinate of the click point can be only acquired, and if this operation is the pull operation, then the touch-screen coordinates of the starting touch point and the ending touch point can be acquired, or the touch-screen coordinates of the middle touch points during the pull can be further included. [0044]Step S104: the first mobile terminal converts the first touch-screen coordinate into an interface coordinate of the interface to be controlled. [0045]In this step, since the coordinate origin and the coordinate range of the touch screen may be different from those of the interface to be controlled, it needs to convert the touch-screen coordinate into the interface coordinate of the interface to be controlled. [0046]Step S106: the first mobile terminal sends the interface coordinate to the second mobile terminal to control the interface to be controlled. [0047]In this step, the first mobile terminal can send the interface coordinate to the second mobile terminal to perform remote control to the interface to be controlled by the touch-screen information transfer capability and coordinate message newly defined by the H.245 protocol. Of course, this embodiment is not limited to the H.245 protocol, and any protocol or message which can send the interface coordinate to the second mobile terminal can achieve the solution of this embodiment, which is not limited by the present invention. [0048]In the related art, the first mobile terminal can only accept the current interface contents of the second mobile terminal passively, and cannot perform operation to it actively, which cannot meet the remote cooperation control demand of the users. By way of this embodiment, the first mobile terminal uses the touch screen to operate the interface to be controlled of the second mobile terminal and converts the coordinate operated by the touch screen into the interface coordinate of the interface to be controlled and sends it to the second mobile terminal, and the second mobile terminal performs corresponding operations according to the received coordinate, thus achieving the remote control of the second mobile terminal by the first mobile terminal and meeting the remote cooperation control demand of the users. [0049]Referring to FIG. 4, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment II of the present invention, wherein the method comprises the following steps [0050]Step S202: a second mobile terminal initiates a video call and starts the H.245 call control process with a first mobile terminal [0051]Step S204: the second mobile terminal performs capability exchange with the first mobile terminal and confirms that both parties support the touch-screen information transfer capability. [0052]The above capability exchange process can be initiated by the first mobile terminal during the video call. The capability exchange with the second mobile terminal is performed, and that both parties support the touch-screen information transfer capability is confirmed. [0053]Step S206: the second mobile terminal sends an interface to be controlled to the first mobile terminal. [0054]In this embodiment, taking the desktop interface of the second mobile terminal as an interface to be controlled for example, the second mobile terminal sends its desktop interface to the first mobile terminal. [0055]Step S208: the first mobile terminal displays the interface to be controlled and receives an operation of clicking one certain location of the touch screen by a user. [0056]In this embodiment, taking clicking the short message folder location on the desktop interface for example, the user of the first mobile terminal clicks the corresponding location of the short message folder on the desktop interface sent by the second mobile terminal via the touch screen. [0057]Step S210: the first mobile terminal detects this click and generates a touch-screen coordinate of the touch point. [0058]In this step, the first mobile terminal detects the location of the short message folder on the desktop interface clicked by the user and generates the touch-screen coordinate of this location. [0059]Step S212: the first mobile terminal judges whether the touch-screen coordinate of this touch point is in the interface to be controlled. If yes, then perform step S214; otherwise, then judge that this click is an operation to this mobile terminal, and respond to a corresponding operation of this click touch point. [0060]This step is an optional step, especially when the range of the interface to be controlled and that of the touch screen interface are the same. [0061]Step S214: the first mobile terminal converts the touch-screen coordinate of this touch point into an interface coordinate of the interface to be controlled. [0062]In this step, the first mobile terminal converts this touch-screen coordinate into the coordinate of the short message folder in the desktop interface according to this touch-screen coordinate, the video resolution of the first mobile terminal, and the touch-screen resolution of the first mobile terminal. The particular conversion process can be performed by reference to the coordinate transfer and conversion shown in FIG. 6, which will not be described here redundantly. [0063]Step S216: the first mobile terminal sends the interface coordinate to the second mobile terminal. [0064]In this step, the first mobile terminal sends the interface coordinate to the second mobile terminal via a coordinate message of H.245. [0065]Step S218: the second mobile terminal receives the interface coordinate and converts it to be the touch-screen coordinate of the second mobile terminal. [0066]In this step, the second mobile terminal converts the interface coordinate into the touch-screen coordinate of the second mobile terminal according to the interface coordinate, the video resolution of the second mobile terminal, and the touch-screen resolution of the second mobile terminal. [0067]Step S220: the second mobile terminal responds to this touch-screen coordinate and performs operations to its interface to be controlled. [0068]In this step, the second mobile terminal performs corresponding click operation to the short message folder corresponding to this touch-screen coordinate on the desktop interface in response to this touch-screen coordinate according to the touch-screen coordinate converted from the interface coordinate. [0069]In this embodiment, the second mobile terminal achieves effective control to its interface to be controlled by receiving the interface coordinate sent by the first mobile terminal and then converting the interface coordinate into its own touch-screen coordinate. [0070]Referring to FIG. 5, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment III of the present invention, and the method comprises the following steps. [0071]Step S302: a second mobile terminal initiates a video call and starts the H.245 call control process with a first mobile terminal. [0072]Step S304: the first mobile terminal initiates control switch during the video call to perform capability exchange with the second mobile terminal and confirm that both parties support the touch-screen information transfer capability. [0073]Step S306: the second mobile terminal sends an interface to be controlled to the first mobile terminal. [0074]In this embodiment, taking the e-book interface of the second mobile terminal as an interface to be controlled for example, the second mobile terminal sends its e-book interface to the first mobile terminal. [0075]Step S308: the first mobile terminal displays the interface to be controlled and receives a pull operation of a user on the touch screen. [0076]In this embodiment, taking pulling the scrollbar of the e-book interface for example, the user of the first mobile terminal pulls the corresponding location of the vertical or horizontal scrollbar in the e-book interface sent by the second mobile terminal from top to down via the touch screen. [0077]Step S310: the first mobile terminal detects this operation and generates a touch-screen coordinates of the pulled starting touch point and the ending touch point. [0078]In this step, the first mobile terminal detects the touch-screen operation of the user, judges that this operation type is a pull touch-screen operation according to the press time, and generates the touch-screen coordinates of the pulled starting touch point and the ending touch point. The generated touch-screen coordinates can further include one to more touch point coordinates of the middle touch point during the pull so as to improve the accuracy of the pull operation. [0079]Step S312: the first mobile terminal converts the touch-screen coordinates of the starting touch point and the ending touch point into the interface coordinates of the interface to be controlled. [0080]In this step, the first mobile terminal converts the touch-screen coordinates of the starting touch point and the ending touch point into coordinates of the starting touch point and the ending touch point in the e-book interface according to the touch-screen coordinates of the starting touch point and the ending touch point, the video resolution of the first mobile terminal, and the touch-screen resolution of the first mobile terminal. The particular conversion process can be performed by reference to the coordinate transfer and conversion shown in FIG. 6, which will not be described here redundantly. [0081]Step S314: the first mobile terminal sends the interface coordinate to the second mobile terminal. [0082]In this step, the first mobile terminal sends the interface coordinate to the second mobile terminal via a coordinate message of H.245. [0083]Step S316: the second mobile terminal receives the interface coordinate and converts it into the touch-screen coordinate of the second mobile terminal. [0084]In this step, the second mobile terminal converts the interface coordinate into the touch-screen coordinates of the starting touch point and the ending touch point corresponding to the second mobile terminal according to the interface coordinate, the video resolution of the second mobile terminal, and the touch-screen resolution of the second mobile terminal. [0085]Step S318: the second mobile terminal responds to the touch-screen coordinates of the starting touch point and the ending touch point and performs operations to its interface to be controlled. [0086]In this step, the second mobile terminal performs pull operation to the e-book interface corresponding to this touch-screen coordinate according to the touch-screen coordinates of the starting touch point and the ending touch point converted from the interface coordinate so as to perform downward page turning view and the like to this e-book. [0087]Referring to FIG. 6, it shows a schematic diagram of a coordinate transfer and conversion process according to the embodiments of the present invention. [0088]The mobile terminal and videophone relates to a plurality of resolutions mainly including: video resolution, such as SQCIF, CIF, and QCIF, which are all common standardized image formats, and in which, SQCIF=128×965 pixels, CIF=352×288 pixels, QCIF=176×144 pixels; and LCD resolution which is generally 4*3 ratio, such as 320*240; and touch-screen resolution which can be defined by the terminal itself, such as 900*900. [0089]The final conversion results of the same coordinate under different resolutions are different. As shown FIG. 6, the coordinate transfer and conversion process is as follows: [0090]Step S402: after the user of the first mobile terminal clicks the touch screen, the coordinate of the touch point is touch-screen coordinate, and the coordinate of the touch point needs to be converted into interface coordinate according to the touch-screen resolution and video resolution; [0091]Step S404: since what is displayed in the first mobile terminal is the current application interface of the LCD of the second mobile terminal, this interface coordinate is converted into the LCD coordinate of the second mobile terminal; and [0092]Step S406: the LCD coordinate of the second mobile terminal is converted into the touch-screen coordinate of the second mobile terminal. [0093]The LCD display screen and the touch screen both have their own resolution indexes, which is equivalent to their coordinate systems, assuming that their coordinate systems are (x, y) and (X, Y) respectively. Taking the resolution of the LCD display screen to be 1024*600 for example, its coordinate origin (0, 0) is at the top left corner, the coordinate of the bottom right corner is (1024, 600), while the touch screen also has its own coordinate origin O (this coordinate origin is physical and fixed at one certain location in the screen, and it is very possible that this origin has already been cut away during assembly but it has no effect to coordination determination) [0094]During practical application, two two-dimensional linear coordinate systems are corresponding to each other in manner of sampling, i.e. (X, Y)→(x, y), the particular practice is: (1) the coordinates of the four corners of the LCD screen are used as sampling values (since in the situation that there is no other tools, the definite coordinates of these four points (x1, y1), (x2, y2), (x3, y3), and (x4, y4) are only known); (2) set an input device detection program before running, respectively click the four corners of the LCD, and read out the corresponding touch-screen coordinate values of these points (X1, Y1), (X2, Y2), (X3, Y3), and (X4, Y4) in the program; (3) substitute these four sampling values into the following equations: x=aX+bY+c and y=eX+fY+g; solve 7 coefficients (a, b, c, d, e, f, s) in these equations, and then the correlation of two coordinate systems can be obtained. [0095]The above situation can be used widely and is comprehensive and of high accuracy. However, there are too many unknown numbers to be solved and there are also too many sampling values; and in fact, the current assembly process can totally ensure the phase difference between the two coordinate systems to be an integral multiple of 90 degree, that is, the above correspondence equation can be simplified as the following: {x=aX+b, y=cY+d} or {x=aY+b, y=cX+d} [0096]Thus, it only needs 2 groups of sampling values to determine the corresponding coefficients. [0097]For example, the LCD resolution is 320*240, and the coordinate origin is at the top left corner; and the touch-screen resolution is 900*900, and the coordinate origin is at the top left corner, then the conversion formula is as follows: xLCD=[320*(x−x2)/(x1−x2)], yLCD=[240*(y−y2)/(y1−y2)] [0098]If the coordinate origins are inconsistent, for example, the LCD coordinate origin is at the bottom right corner and the touch screen origin is at the top left corner, then it can further perform the following conversion: xLCD=320−[320*(x−x2)/(x1−x2)] yLCD=240−[240*(y−y2)/(y1−y2)] [0099]Then, the correlation of two coordinate systems is definite, and all touch-screen coordinates are converted into corresponding coordinates in the LCD coordinate system according to this correspondence formula. [0100]Coordination conversion between touch screen and LCD can be achieved according to the above method. [0101]Referring to FIG. 7, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment IV of the present invention. This embodiment can describe the present invention from the perspective of videophone message transmission protocol procedure, which comprises the following steps. [0102]Step S502: a calling subscriber initiates a video (String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的远程控制方法及移动终端。 发明背景 [0002] 随着移动多媒体业务的快速发展和国内3G业务的逐步应用,可视电话业务在个人通信领域得到了迅速的发展和应用,成为3G的标志性业务。 可视电话业务是一种点对点的视频通信业务,它可以利用电话网络,双向、实时地传输呼叫方的图像和语音信号。 视频终端可以达到面对面交流的效果,实现通话时“闻声见人”的梦想。 [0003] 但是,在使用可视电话这一新功能时,会出现以下情况:用户不知道如何使用移动终端的某项功能,需要他人的帮助; 或终端无法正常使用,需要他人协助分析原因; 或者在通话过程中希望与其他用户共享本终端中的内容,在实际应用中也可能经常出现。 [0004] 针对上述情况,相关技术中提供了一种视频终端及其实现界面内容共享的方法。 该方法在视频终端中设置有切换单元和界面内容处理单元,切换单元用于接收来自外部的切换指令,选择取景器获取视频数据或缓存器获取缓存数据。 LCD数据显示缓存区收集发送数据; 接口内容处理单元,用于对来自LCD数据显示缓存区的数据进行处理,转换为符合编码输入格式要求的数据输出。 在视频通话过程中,通过用户的切换需求和界面内容处理单元,以视频通话数据传输的方式实现视频通话中终端界面内容的实时共享。 这里,定义发起分享的终端为第二终端,对方为第一终端。在该方法中,虽然第一终端可以分享第二终端当前的界面内容,但第一终端只能接受当前的界面内容。 第二终端被动界面,但不能主动操作当前界面,如主动切换界面等。 因此,仍然无法满足用户远程协同控制的需求。 发明内容 [0005] 本发明提供了一种远程控制移动终端的方法及移动终端,以解决上述视频移动终端无法满足用户远程协同控制需求的问题。 [0006] 根据本发明的一个方面,提供了一种远程控制移动终端的方法,该方法包括:第一移动终端接收对待控制界面的触屏操作,其中,所述待控制界面 controlled由第二移动终端在视频通话时发送,获取操作的第一触屏坐标; 第一移动终端将第一触屏坐标转换为待控制界面的界面坐标; 第一移动终端将界面坐标发送给第二移动终端以控制待控制界面。 [0007] 进一步地,该移动终端远程控制方法还包括:第二移动终端接收界面坐标; 将界面坐标转换为第二移动终端的第二触屏坐标; 根据第二触屏坐标对待控制界面进行操作控制。 [0008]进一步地,所述第一移动终端将所述第一触屏坐标转换为所述待控制界面的界面坐标包括:所述第一移动终端将所述第一触屏坐标转换为待控制界面的界面坐标。 根据第一触屏坐标、第一移动终端的触屏分辨率和第一移动终端的视频分辨率控制界面。 [0009] 进一步地,第一移动终端向第二移动终端发送接口坐标包括:第一移动终端将接口坐标封装成H.245协议的坐标消息,其中,坐标消息为 用于传递界面坐标信息; 向第二移动终端发送坐标信息。 [0010] 进一步地,在所述第一移动终端接收视频通话中第二移动终端发送的对所述待控界面的触屏操作之前,所述方法还包括:所述第一移动终端和所述第一移动终端执行: 第二移动终端,采用H.245协议的触屏信息传递能力交互,触屏信息传递能力用于支持第一移动终端和第二移动终端传递界面坐标信息; 确认第一移动终端和第二移动终端均支持触屏信息传递能力。 [0011] 根据本发明的另一方面,提供了一种移动终端,其中,所述移动终端包括: 获取模块,用于接收对待控界面的触屏操作,所述待控界面由所述待控界面发送。 视频通话中的其他移动终端,获取操作的第一触屏坐标; 第一转换模块,用于将所述第一触摸屏坐标转换为所述待控界面的第一界面坐标; 第一控制模块,用于将所述第一界面坐标发送给所述另一移动终端,以控制所述待控制界面。 [0012] 进一步地,该移动终端还包括: 接收模块,用于接收另一移动终端发送的第二界面坐标; 第二转换模块,用于将第二界面坐标转换为第二触摸屏坐标; 第二控制模块,用于根据第二触屏坐标对移动终端的待控界面进行操作控制。 [0013] 进一步地,第一转换模块,用于根据第一触摸屏坐标、移动终端触摸屏的分辨率和视频分辨率,将第一触摸屏坐标转换为待控制界面的第一界面坐标。 的移动终端。 [0014] 进一步地,所述第一控制模块包括: 封装模块,用于将所述第一接口坐标封装为H.245协议的坐标消息,所述坐标消息用于传递所述接口坐标的信息。 发送模块,用于向所述另一移动终端发送所述坐标消息,以控制所述另一移动终端的待控制界面。 [0015] 进一步地,该移动终端还包括:交换模块,用于通过H.245协议与另一移动终端进行触屏信息传递能力交换,触屏信息传递能力用于支持移动终端和 其他移动终端传递界面坐标信息; 确认模块,用于确认第一移动终端和第二移动终端均支持触屏信息传递能力。 [0016]本发明通过第一移动终端通过以下方式对第二移动终端的应用界面进行操作控制,解决了相关技术中视频移动终端无法满足用户远程协同控制需求的问题。 可视电话和触摸屏,实现远程控制移动终端的效果,实现通过可视电话协助他人解决问题或与他人共享移动终端等应用,极大地丰富了可视电话的内容,提供了更广阔的应用空间 用于可视电话的商业应用。 附图的简要说明 [0017] 此处所示的附图提供对本发明的进一步理解并且构成本申请的一部分。 示例性实施例及其描述用于解释本发明而不不当限制本发明,其中: [0018] 图1是本发明一个实施例的能力集的数据结构示意图; [0019] 图2为本发明实施例的能力格式示意图; [0020] 图3为本发明实施例一提供的远程控制移动终端的方法的步骤流程图; [0021] 图4为本发明实施例二提供的远程控制移动终端的方法的步骤流程图; [0022] 图5为本发明实施例三的远程控制移动终端的方法的步骤流程图; [0023] 图6是根据本发明实施例的坐标传递和转换过程的示意图; [0024] 图7为本发明实施例四提供的远程控制移动终端的方法的步骤流程图; [0025] 图8为本发明实施例五远程控制移动终端的方法的步骤流程图; [0026] 图9为本发明实施例六的移动终端的结构框图; [0027] 图10为本发明实施例七的移动终端的结构框图; 和 [0028] 图11是应用图10所示的移动终端进行远程控制的步骤流程图。 具体实施方式 [0029] 下面结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。 [0030] 本发明实施例涉及的移动终端均支持可视电话,且为触摸屏移动终端。 [0031] 在移动可视电话领域,最常见的通信协议是H.324协议集,其中包括H.223复用协议、H.245系统控制协议、H.263视频编码协议、G.723.1音频编码协议 协议等。 本发明实施例提供的视频移动终端进行远程控制的方法及视频移动终端基于H.324视频通信协议,对H.245控制协议进行一定的补充,实现远程控制。 [0032]H.245协议是一种控制信令协议,主要用于通信终端之间端到端的H.245信息交换。 在H.245协议中,能力交换过程是H.245呼叫建立后首先需要进行的过程,其目的是保证发送的多媒体信号能够被终端接收和编码 . 终端通过发送自己的“能力集”,让对方知道自己可以接收到的能力组合。 对方不必了解所有这些能力,对方只需要存储可以理解并可以使用的能力部分,以方便对方建立逻辑通道。 [0033] 终端能力集在消息中包含一个能力表,该表列出了终端允许的所有操作模式,并为每个模式分配了相应的序号(能力号)。 若干个能力号组成一个“可选能力集”结构,描述了终端的媒体通道能力,表示终端可以基于其中的任何模式工作。 多个“可选能力集”组成一个“同时能力”结构,表示该终端可以使用一组能力同时工作。 最后,多个“同时能力”可以进一步组成一个“能力描述集”结构,该结构包含一组能力描述,每一个描述由一个同时能力和一个能力描述序号组成。 该数据结构给出了终端的总体能力,具体数据结构如图1所示。 [0034] 本发明利用了上述H.245协议的特点,在H.245能力集中定义了新的能力: 触摸屏信息传递能力,支持呼叫方传递坐标信息; H.245协议定义了新的消息类型,即坐标消息,使具有触摸屏信息传输能力的终端能够发送、接收和反馈坐标信息。 [0035] 特别地,H.245中定义的新的触摸屏信息传递能力如下: [0036] H.245使用ASN.1(Abstract Syntax Notation 1)标准定义自己的消息结构,其消息数据使用基于PER(Packed Encoding Rule)规则的二进制编码。 上述本发明实施例中的能力定义格式如图2所示。 [0037] 根据上述能力格式,本发明实施例的H.245协议中定义的新坐标消息如下: [0038] 坐标报文格式的表示方式与普通报文一致,区别仅在于报文中的类型字段(对应的类型为“坐标信息”),用于与其他报文类型区分开来。 另外,将坐标位置信息转换成符合编码输入格式要求的数据在可视电话中输出下发。 [0039] 移动终端通过触摸点坐标信息发起触摸屏操作(如点击选择和拉动),并在视频通话中使用新的触摸屏信息传递能力和定义的坐标消息传递坐标信息 H.245远程控制另一个移动终端,极大地方便了用户的使用,满足了用户远程协作控制的需求,也加速了视频终端的普及。 [0040] 本发明以下实施例中的移动终端均可以使用上述改进的H.245协议。 [0041] 参见图3,其示出了根据本发明实施例一的远程控制移动终端的方法的步骤流程图,该方法包括以下步骤。 [0042] 脚步 102:第一移动终端接收待控界面的触屏操作,其中,所述待控界面是视频通话中第二移动终端发送的,第一移动终端获取该待控界面的第一触屏坐标 手术。 [0043] 本步骤中,当第一移动终端在视频通话中接收到第二移动终端发送的第二移动终端的待控制应用界面时,第一移动终端的用户通过触摸屏对该应用界面进行操作, 例如点击或拉动等,以实现对第二移动终端上相应应用界面的远程控制。 此时,第一移动终端获取用户对触摸屏进行操作时的坐标,即第一触摸屏坐标。 如果本次操作是点击操作,则只能获取点击点的触屏坐标,如果本次操作是拉动操作,则可以获取起始触摸点和结束触摸点的触摸屏坐标 获取,或者可以进一步包括拉动过程中中间触摸点的触摸屏坐标。 [0044] 脚步 104 :第一移动终端将第一触屏坐标转换为待控制界面的界面坐标。 [0045] 在该步骤中,由于触摸屏的坐标原点和坐标范围可能与待控界面的坐标原点和坐标范围不同,因此需要将触摸屏坐标转换为待控界面的界面坐标。 [0046] 脚步 106 :第一移动终端将界面坐标发送给第二移动终端控制待控制界面。 [0047] 本步骤中,第一移动终端可以将界面坐标发送给第二移动终端,以实现对H.245协议新定义的触摸屏信息传递能力和坐标消息控制的界面进行远程控制。 当然,本实施例不限于H.245协议,任何能够将接口坐标发送给第二移动终端的协议或消息均可实现本实施例的方案,本发明对此不做限制。 [0048] 相关技术中,第一移动终端只能被动地接受第二移动终端当前的界面内容,不能主动对其进行操作,无法满足用户的远程协作控制需求。 通过本实施例,第一移动终端通过触摸屏操作第二移动终端的待控界面,并将触摸屏操作的坐标转换为待控界面的界面坐标,发送给第二移动终端。 第二移动终端,第二移动终端根据接收到的坐标进行相应的操作,从而实现第一移动终端对第二移动终端的远程控制,满足用户的远程协作控制需求。 [0049] 参见图4,其示出了根据本发明实施例二的一种远程控制移动终端的方法的步骤流程图,该方法包括以下步骤 [0050] 脚步 202 :第二个移动终端发起视频通话,开始与第一个移动终端的H.245呼叫控制流程 [0051] 脚步 204 :第二移动终端与第一移动终端进行能力交互,确认双方均支持触屏信息传递能力。 [0052] 上述能力交换过程可以由第一移动终端在视频通话过程中发起。 与第二移动终端进行能力交互,确认双方均支持触屏信息传递能力。 [0053] 脚步 206 :第二移动终端向第一移动终端发送待控制界面。 [0054]在本实施例中,以第二移动终端的桌面界面作为待控制界面为例,第二移动终端将其桌面界面发送给第一移动终端。 [0055] 脚步 208 :第一移动终端显示待控制界面,并接收用户点击触摸屏某个位置的操作。 [0056] 在本实施例中,以点击桌面界面的短信文件夹位置为例,第一移动终端的用户通过触摸屏点击第二移动终端发送的桌面界面的短信文件夹的对应位置。 [0057] 脚步 210 :第一移动终端检测到该点击,生成触摸点的触屏坐标。 [0058] 本步骤中,第一移动终端检测用户点击的桌面界面上短信文件夹的位置,并生成该位置的触屏坐标。 [0059] 脚步 212 :第一移动终端判断该触摸点的触屏坐标是否在待控制界面中。 如果是,则执行步骤S 214 ; 否则,则判断本次点击是对本移动终端的操作,并响应本次点击触点的相应操作。 [0060] 该步骤为可选步骤,尤其是在需要控制的界面范围与触摸屏界面范围相同的情况下。 [0061] 脚步 214 :第一移动终端将该触摸点的触屏坐标转换为待控制界面的界面坐标。 [0062] 在该步骤中,第一移动终端根据该触摸屏坐标、第一移动终端的视频分辨率和第一移动终端的触摸屏分辨率,将该触摸屏坐标转换为桌面界面中短信文件夹的坐标。 第一个移动终端。 具体的转换过程可以参考图6所示的坐标传递和转换,在此不再赘述。 [0063] 脚步 216 :第一移动终端将接口坐标发送给第二移动终端。 [0064] 本步骤中,第一移动终端将接口坐标通过H.245的坐标消息发送给第二移动终端。 [0065] 脚步 218 :第二移动终端接收界面坐标,转换为第二移动终端的触屏坐标。 [0066] 本步骤中,第二移动终端根据界面坐标、第二移动终端的视频分辨率和第二移动终端的触屏分辨率,将界面坐标转换为第二移动终端的触屏坐标。 [0067] 脚步 220 :第二移动终端响应该触屏坐标,对其待控制界面进行操作。 [0068] 本步骤中,第二移动终端根据界面坐标转换后的触屏坐标,响应该触屏坐标,对桌面界面上该触屏坐标对应的短信文件夹进行相应的点击操作。 [0069] 在本实施例中,第二移动终端通过接收第一移动终端发送的界面坐标,然后将界面坐标转换为自身的触屏坐标,实现对其待控界面的有效控制。 [0070] 参见图5,其示出了根据本发明实施例三的远程控制移动终端的方法的步骤流程图,该方法包括以下步骤。 [0071] 脚步 302 :第二个移动终端发起视频呼叫,并启动与第一个移动终端的H.245呼叫控制过程。 [0072] 脚步 304:第一移动终端在视频通话过程中发起控制切换,与第二移动终端进行能力交换,确认双方均支持触屏信息传递能力。 [0073] 脚步 306 :第二移动终端向第一移动终端发送待控制界面。 [0074] 在本实施例中,以第二移动终端的电子书界面作为待控制界面为例,第二移动终端将其电子书界面发送给第一移动终端。 [0075] 脚步 308 :第一移动终端显示待控制界面,并接收用户在触摸屏上的拉动操作。 [0076] 本实施例中,以拉动电子书界面的滚动条为例,第一移动终端的用户从上到下拉动第二移动终端发送的电子书界面中垂直或水平滚动条的对应位置。 通过触摸屏。 [0077] 脚步 310 :第一移动终端检测到该操作,生成拉动的起始触摸点和结束触摸点的触屏坐标。 [0078] 本步骤中,第一移动终端检测用户的触屏操作,根据按下时间判断该操作类型为拉动触屏操作,并生成拉动起始触摸点的触屏坐标和 结束接触点。 生成的触摸屏坐标还可以包括拉动过程中中间触摸点的一个或多个触摸点坐标,以提高拉动操作的准确性。 [0079] 脚步 312 :第一移动终端将起始触摸点和结束触摸点的触摸屏坐标转换为待控制界面的界面坐标。 [0080] 本步骤中,第一移动终端根据触摸屏坐标将起始触摸点和结束触摸点的触摸屏坐标转换为电子书界面中起始触摸点和结束触摸点的坐标。 起始触摸点和结束触摸点、第一移动终端的视频分辨率和第一移动终端的触摸屏分辨率。 具体的转换过程可以参考图6所示的坐标传递和转换,在此不再赘述。 [0081] 脚步 314 :第一移动终端将接口坐标发送给第二移动终端。 [0082] 本步骤中,第一移动终端将接口坐标通过H.245的坐标消息发送给第二移动终端。 [0083] 脚步 316 :第二移动终端接收界面坐标,转换为第二移动终端的触屏坐标。 [0084] 本步骤中,第二移动终端根据界面坐标、第二移动终端的视频分辨率,将界面坐标转换为第二移动终端对应的起始触摸点和结束触摸点的触屏坐标。 第二移动终端的触摸屏分辨率。 [0085] 脚步 318 :第二移动终端响应起始触摸点和结束触摸点的触屏坐标,对其待控制界面进行操作。 [0086] 本步骤中,第二移动终端根据界面坐标转换的起始触摸点和结束触摸点的触摸屏坐标,对该触摸屏坐标对应的电子书界面进行拉动操作,以执行 对该电子书进行向下翻页查看等操作。 [0087] 参见图6,其示出了根据本发明实施例的坐标传递和转换过程的示意图。 [0088]移动终端和可视电话涉及多种分辨率,主要包括:视频分辨率,如SQCIF、CIF、QCIF等,都是常见的标准化图像格式,其中,SQCIF=128×965像素,CIF=352×288 像素,QCIF=176×144像素; LCD分辨率一般为4*3比例,如320*240; 触摸屏分辨率可由终端自行定义,如900*900。 [0089] 同一坐标在不同分辨率下最终的转换结果是不同的。 如图6所示,坐标传递和转换过程如下: [0090] 脚步 402 :第一移动终端用户点击触摸屏后,触摸点坐标为触摸屏坐标,需要根据触摸屏分辨率和视频分辨率将触摸点坐标转换为界面坐标 ; [0091] 脚步 404 :由于第一移动终端显示的是第二移动终端LCD的当前应用界面,所以将该界面坐标转换为第二移动终端的LCD坐标; 和 [0092] 脚步 406 :将第二移动终端的LCD坐标转换为第二移动终端的触摸屏坐标。 [0093] LCD显示屏和触摸屏都有自己的分辨率指标,相当于它们的坐标系,假设它们的坐标系分别为(x,y)和(X,Y)。 以液晶显示屏的分辨率为1024*600为例,其坐标原点(0, 0)在左上角,右下角的坐标为(1024, 600),而触摸屏也 有自己的坐标原点O(这个坐标原点是物理的,固定在屏幕的某个位置,很可能这个原点在组装时已经被切掉了,但对坐标确定没有影响) [0094] 在实际应用中,两个二维线性坐标系以采样方式相互对应,即(X,Y)→(x,y),具体做法是:(1) 以液晶屏作为采样值(由于在没有其他工具的情况下,确定这四个点的坐标(x1,y1),(x2,y2),(x3,y3),(x4,y4) 只知道); (2)运行前设置一个输入设备检测程序,分别点击LCD的四个角,读出这几个点(X1,Y1),(X2,Y2),(X3,Y3)对应的触摸屏坐标值 ), 和 (X4, Y4) 在程序中; (3)将这四个采样值代入如下方程:x=aX+bY+c和y=eX+fY+g; 求解这些方程中的7个系数(a、b、c、d、e、f、s),即可得到两个坐标系的相关性。 [0095] 上述情况适用范围广,内容全面,准确性高。 但是,需要求解的未知数太多,采样值也太多; 事实上,目前的装配工艺完全可以保证两个坐标系的相位差为 90 度,即上述对应方程可以简化为: {x=aX+b, y=cY+d} 或者 { x=aY+b, y=cX+d} [0096] 这样,它只需要 2 组的采样值来确定相应的系数。 [0097] 例如LCD分辨率为320*240,坐标原点在左上角; 触摸屏分辨率为900*900,坐标原点在左上角,则换算公式如下: x 液晶屏=[320*( x−x 2)/( x 1− x 2)], y 液晶屏=[240*( y−y 2)/( y 1− y 2)] [0098] 如果坐标原点不一致,比如LCD坐标原点在右下角,触摸屏坐标原点在左上角,那么还可以进一步进行如下转换: x LCD=320−[320*( x−x 2)/( x 1− x 2)] y LCD=240−[240*( y−y 2)/( y 1− y 2)] [0099] 然后确定两个坐标系的相关性,根据这个对应关系式将所有触摸屏坐标转换成LCD坐标系中对应的坐标。 [0100] 触摸屏与LCD的配合转换可按上述方法实现。 [0101] 参见图7,其示出了根据本发明实施例四的远程控制移动终端的方法的步骤流程图。 本实施例从可视电话消息传输协议流程的角度来描述本发明,包括以下步骤。 [0102] 脚步 502 :主叫用户向被叫用户发起视频通话。 [0103] 脚步 504 :主叫用户与被叫用户建立无线链路成功。 [0104] 脚步 506 :主叫用户和被叫用户进行移动电平分层,双方协商相同的移动电平。 [0105] 在这种情况下,移动层主要描述了双方能够支持的音视频编码格式,以保证通信双方的终端能够正常通信。 [0106] 脚步 508 :分层成功后,双方发起H.245呼叫控制流程,建立控制通道,进行能力交换。 [0107] 在该步骤中,双方交换H.245中新定义的触摸屏信息传递能力,以确认双方都支持双方在可视电话中传递坐标信息的能力。 [0108] 脚步 510 :被叫方发起切换指令,以其当前触摸屏的显示界面作为被控界面,将图片数据或图像信息传送给主叫方。 [0109] 脚步 512 :主叫方在被控界面任意位置点击,转换触摸点的坐标信息,然后将该坐标信息以H.245呼叫控制协议的方式发送给被叫用户。 同时启动重传定时器机制。 如果超时仍未收到对方的响应消息,则启动H.245协议中的循环延时判断过程,判断被叫是否可达。 如果不可达,则放弃此呼叫; 如果可达,则继续通话,将坐标信息再次发送给被叫方。 [0110] 脚步 514 :被叫接收到坐标信息后,反馈给主叫确认接收。 [0111] 脚步 516 :主叫方点击可视电话通话窗口界面,重复步骤S 510 到小号 514 使被叫用户能够及时响应相应的操作。 [0112] 脚步 518 :主叫停止对被叫发起控制操作,被叫收到停止发送信号后恢复界面显示。 [0113] 脚步 520 :主叫用户挂断电话,移除协议栈和无线链路,通话结束。 [0114] 参见图8,其示出了根据本发明实施例五的远程控制移动终端的方法的步骤流程图。 在本实施例中,将相互通信的双方定义为移动终端A和B。当是普通视频通话时,每个移动终端将显示两个视频,其中一个是对端的视频或界面,参考 一个是主视频,另一个是移动端当前的相机界面,称为辅助视频。 [0115] 脚步 602 :A和B视频通话过程中,A发起控制请求,B接受请求并确认。 [0116] 在该步骤中,也可以由B发起控制切换请求。 [0117]脚步 604 :双方通话界面切换。 [0118] 此时A的主视频显示的是B当前屏幕显示的应用界面,B的主视频显示的是A的摄像头视频,此时B需要设置主视频在某个时间点显示 尺寸较小的角或设置为不显示,以方便终端A对其进行远程操作控制。 [0119] 脚步 606 :A通过主视频中的触摸屏进行操作,并将该操作的坐标信息通过可视电话发送给B。 [0120] 脚步 608 : B接收到A发送的坐标信息并响应相应的操作,B进行应用界面刷新。 [0121] 脚步 610 :A的主视频界面显示B刷新后的应用界面,重复步骤S的操作 606 到小号 608 . [0122] 脚步 612 :A端或B端任意一方发起结束请求,结束遥控,恢复到普通视频通话界面。 [0123] 参见图9,其示出了根据本发明实施例六的移动终端的结构框图,包括以下模块: [0124] 获取模块 702 ,用于接收对待控制界面的触屏操作,所述待控界面为视频通话中另一移动终端发送的,并获取该操作的第一触屏坐标; 第一转换模块 704 , 用于将第一触屏坐标转换为待控制界面的第一界面坐标; 和第一控制模块 706 ,用于将第一界面坐标发送给其他移动终端控制待控制界面。 [0125] 优选地,本实施例的移动终端还包括:接收模块 708 ,用于接收其他移动终端发送的第二接口坐标; 第二个转换模块 710 , 用于将第二界面坐标转换为第二触屏坐标; 和第二个控制模块 712 ,用于根据第二触屏坐标对移动终端的待控制界面进行操作控制。 [0126] 优选地,第一转换模块 704 用于根据第一触屏坐标、移动终端的触屏分辨率和移动终端的视频分辨率,将第一触屏坐标转换为待控制界面的第一界面坐标。 [0127] 优选地,第一控制模块 706 包括:封装模块 7062 将第一接口坐标封装成H.245协议的坐标消息,坐标消息用于传递接口坐标的信息; 和发送模块 7064 用于向另一移动终端发送坐标消息以控制另一移动终端的待控制界面。 [0128] 优选地,本实施例的移动终端还包括:交换模块 714 ,用于通过H.245协议与另一移动终端进行触屏信息传递能力交互,所述触屏信息传递能力用于支持所述移动终端与所述另一移动终端传递界面坐标信息; 和一个确认模块 716 , 用于确认移动终端与另一移动终端均支持触屏信息传递能力。 [0129]参见图10,其示出了根据本发明实施例七的移动终端的结构示意图。 为了描述方便,本实施例将界面坐标的生成部分和发送部分设置在第一移动终端上,将界面坐标的接收部分和操作部分设置在第二移动终端上。 但是,本领域的技术人员应该理解,上述第一移动终端和第二移动终端可以是同一个移动终端,以达到对另一个移动终端进行远程控制并能够接收到另一个移动终端的远程控制的目的。 终端。 [0130] 其中,第一移动终端包括:可视电话通话接口,用于接收第二移动终端发送的待控界面,并通过本移动终端的触摸屏对该待控界面进行操作。 触摸屏检测装置(相当于获取模块),用于检测用户的触摸屏操作,并生成所操作的触摸点的触摸屏坐标; 触摸屏控制器,用于响应本终端用户的触摸屏操作,将触摸屏坐标发送给辅助处理模块,判断触摸点是否在待控制界面范围内; 类似; 辅助处理模块(相当于第一转换模块),用于将触摸屏坐标转换为界面坐标; 可视电话控制模块(相当于第一控制模块、交换模块和确认模块),用于通过H.245协议与第二移动终端进行能力交换,传递接口坐标等。 [0131] 其中,第二移动终端包括:可视电话控制模块(相当于接收模块),用于通过H.245协议与第二移动终端进行能力交互,接收接口坐标等。 辅助处理模块(相当于第二转换模块),用于将界面坐标转换为本终端的触屏坐标; 触摸屏控制器(相当于第二控制模块),用于根据界面坐标转换的触摸屏坐标响应第一移动终端的遥控操作等; 终端CPU,用于对触摸屏和系统进行控制等。 [0132] 参见图11,其示出了应用图10所示的移动终端进行远程控制的步骤流程图,包括以下步骤。 [0133] 脚步 902 :第一移动终端用户显示第二移动终端用户通过可视电话界面发送的待控制界面; 第一移动终端的用户点击触摸屏的某个位置; 触摸屏检测装置检测到该点击,并生成该点击的触摸点的坐标信息。 [0134] 脚步 904 :触摸屏检测装置将该坐标信息传递给触摸屏控制器,触摸屏控制器判断该触摸点是否在待控制界面内。 若是,则判断对第二移动终端进行遥控操作,继续步骤S 906 ,触摸屏控制器不执行任何操作; 若否,则判断对本终端进行操作,触摸屏控制器响应对本终端的相应操作。 [0135] 脚步 906 :触摸屏控制器为辅助处理模块提供坐标信息,辅助处理模块根据该坐标信息计算出该触摸点的坐标在待控界面中的界面坐标,视频分辨率,触摸 -屏幕分辨率。 [0136] 脚步 908:第一移动终端辅助处理模块向可视电话控制模块提供接口坐标。 [0137] 脚步 910 :第一移动终端的可视电话模块通过H.245协议将接口坐标传递给可视电话控制模块。 [0138] 脚步 912 :第二移动终端的可视电话控制模块将接口坐标传递给第二移动终端的辅助处理模块,辅助处理模块根据该接口坐标将该接口坐标转换为第二移动终端的触摸屏坐标 、LCD 分辨率和触摸屏分辨率。 [0139] 脚步 914 :第二移动终端的辅助处理模块将转换后的触摸屏坐标传递给第二移动终端的触摸屏控制器。 [0140] 脚步 916 :第二移动终端的触摸屏控制器响应界面坐标转换后的触摸屏坐标进行相应的操作。 [0141] 显然,本领域的技术人员应该理解,本发明的上述模块和步骤可以使用通用计算设备来实现,可以集成在一个计算设备中,也可以分布在由多个计算设备组成的网络上。 可选地,本发明的模块和步骤可以通过使用计算装置的可执行程序代码来实现,从而存储在存储装置中并由计算装置执行,在某些情况下,可以执行 此处所示或所述步骤以外的顺序,或分别制成集成电路模块,或多个模块或其步骤制成一个集成电路模块。 这样,本发明不限于任何特定的硬件和软件组合。 [0142] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.420 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.420 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.420 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101893964A(String), EP2472997A1(String), EP2472997A4(String), US20130111351A1(String), WO2012009904A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101893964A(String), EP2472997A1(String), EP2472997A4(String), US20130111351A1(String), WO2012009904A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20130111351A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101893964A(String), EP2472997A1(String), EP2472997A4(String), US20130111351A1(String), WO2012009904A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270647(Integer), CN101893964A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270647(Integer), EP2472997A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.453 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.454 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.454 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270647(Integer), EP2472997A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270647(Integer), US20130111351A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270647(Integer), WO2012009904A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20130111351A1(String), US20130111351A1(String), 1367424000(Integer), 270647(Integer), 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), HUANG, LIANFANG(String), LIU, YANG(String), FANG, WEN(String), 中兴通讯股份有限公司(String), HUANG LIANFANG(String), LIU YANG(String), FANG WEN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184964(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184964(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HUANG, LIANFANG(String), HUANG LIANFANG(String), 0(Integer), 1681975539(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIU, YANG(String), LIU YANG(String), 0(Integer), 1681975539(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: FANG, WEN(String), FANG WEN(String), 0(Integer), 1681975539(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184964(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75915(Integer), 2(Integer), 184964(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75916(Integer), 2(Integer), 184964(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75917(Integer), 2(Integer), 184964(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75915(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7941123B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and system for downloading data to mobile terminals and for implementing data sharing between mobile terminals(String), 一种向移动终端下载数据并实现移动终端间数据共享的方法及系统(String), US7941123B2(String), The invention discloses a method and system for downloading data to mobile terminals, a mobile terminal that utilizes the method, and a method and a system for implementing data sharing between mobile terminals. The method for data downloading includes: dividing data to be downloaded into multiple data task segments by a master mobile terminal, and allocating the data task segments to one or more mobile terminals; downloading the data by the mobile terminals in accordance with the allocated data task segments; judging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure. The system for data downloading includes: a server, at least a master mobile terminal, and at least a slave mobile terminal.(String), 本发明公开了一种向移动终端下载数据的方法和系统、利用该方法的移动终端、以及实现移动终端之间数据共享的方法和系统。 所述数据下载方法包括:由移动主终端将待下载数据划分为多个数据任务段,并将所述数据任务段分配给一个或多个移动终端。 移动终端按照分配的数据任务段下载数据; 主控移动终端判断是否有数据任务段未下载; 如果是,将数据任务段分配给至少一个已完成下载数据任务段的移动终端。 如果否,则终止下载程序。 该数据下载系统包括:服务器、至少一个主移动终端和至少一个从移动终端。(String), US11/502845(String), 1155225600(Integer), US7941123B2(String), 1304956800(Integer), 1304956800(Integer), 美国(String), 4(Integer), CN | CN | CN(String), 5(Integer), 13(Integer), CN1425990A | CN1578222A | KR1020050048719A | KR1020050053389A | US20020059400A1 | US20030013444A1 | US20040058652A1 | US20050059379A1 | WO2004003008A2 | WO2004043008A1 | WO2004066160A1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184965(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b7028b2261ed4a11878c505ca90b68a0.png(String), 184965(Integer), b7028b2261ed4a11878c505ca90b68a0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.640 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.640 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.640 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and system for downloading data to mobile terminals and for implementing data sharing between mobile terminals(String), 一种向移动终端下载数据并实现移动终端间数据共享的方法及系统(String), US7941123B2(String), The invention discloses a method and system for downloading data to mobile terminals, a mobile terminal that utilizes the method, and a method and a system for implementing data sharing between mobile terminals. The method for data downloading includes: dividing data to be downloaded into multiple data task segments by a master mobile terminal, and allocating the data task segments to one or more mobile terminals; downloading the data by the mobile terminals in accordance with the allocated data task segments; judging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure. The system for data downloading includes: a server, at least a master mobile terminal, and at least a slave mobile terminal.(String), 本发明公开了一种向移动终端下载数据的方法和系统、利用该方法的移动终端、以及实现移动终端之间数据共享的方法和系统。 所述数据下载方法包括:由移动主终端将待下载数据划分为多个数据任务段,并将所述数据任务段分配给一个或多个移动终端。 移动终端按照分配的数据任务段下载数据; 主控移动终端判断是否有数据任务段未下载; 如果是,将数据任务段分配给至少一个已完成下载数据任务段的移动终端。 如果否,则终止下载程序。 该数据下载系统包括:服务器、至少一个主移动终端和至少一个从移动终端。(String), US11/502845(String), 1155225600(Integer), US7941123B2(String), 1304956800(Integer), 1304956800(Integer), 美国(String), 3(Integer), 4(Integer), CN | CN | CN(String), 5(Integer), 13(Integer), CN1425990A | CN1578222A | KR1020050048719A | KR1020050053389A | US20020059400A1 | US20030013444A1 | US20040058652A1 | US20050059379A1 | WO2004003008A2 | WO2004043008A1 | WO2004066160A1(String), \20230420\b7028b2261ed4a11878c505ca90b68a0.png(String), 14(Integer), 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 1. A method for downloading data to mobile terminals, wherein a master mobile terminal is adapted to control one or more mobile terminal, the method comprising:obtaining information about size of data to be downloaded from a server by the master mobile terminal;calculating, by the master mobile terminal, task segments to be downloaded by the mobile terminals;dividing the data to be downloaded into multiple data task segments by the master mobile terminal, and allocating the data task segments to one or more mobile terminals;downloading the data by the mobile terminals in accordance with the allocated data task segments; andjudging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure.(String), 1.根据权利要求10所述的方法,还包括:下载完成后,将下载组中从移动终端的下载数据发送给主移动终端;主移动终端将一个或多个其他移动终端下载的数据发送给下载组中的从移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 2. The method according to claim 1, further comprising the step of sending a request to at least one mobile terminal from the master mobile terminal through a local network before the master mobile terminal allocates the data task segments to the one or more mobile terminals.(String), 12.根据权利要求10所述的方法,其中所述步骤,发送数据下载请求的移动终端加入下载组,包括以下步骤:下载组中的主移动终端邀请发送数据下载请求的移动终端加入下载组;发送数据下载请求的移动终端对主移动终端进行鉴权,鉴权成功则加入下载组。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 3. The method according to claim 1, further comprising the step of obtaining information about the size of the data to be downloaded and determining the size of a data task segment by the master mobile terminal according to the size of the data before dividing the data into multiple data task segments.(String), 13.根据权利要求10所述的方法,还包括:根据下载请求中携带的信息,包括下载数据的ID、类型、大小和定位步骤中获取的位置信息,判断是否满足移动终端的数据下载要求。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 4. The method according to claim 1, wherein in the case that a mobile terminal does not download a data task segment within a predefined duration, the master mobile terminal allocates this data task segment to one or more other mobile terminals.(String), 14.根据权利要求10所述的方法,还包括:通过CELLID或AGPS获取下载组中处于下载状态的主移动终端的位置信息;和/或通过CELLID或AGPS定位发送数据下载请求的移动终端。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 5. The method according to claim 1, wherein a mobile terminal, that has finished downloading of an allocated data task segment, obtains IDs of one or more other mobile terminals from the master mobile terminal, and sends the data of the downloaded task segment to the one or more other mobile terminals in accordance with the obtained IDs.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 6. The method according to claim 1, further comprising the steps of:reporting a message from a mobile terminal, that has finished downloading of an allocated data task segment, to the master mobile terminal indicating the allocated task segment has been downloaded;notifying one or more other mobile terminals of the message by the master mobile terminal;obtaining the downloaded data task segment by the one or more other mobile terminals from that mobile terminal that has finished downloading of the allocated data task segment.(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 7. The method according to claim 1, further comprising the steps of:when the master mobile terminal has downloaded a data task segment, sending the downloaded data task segment to one or more other mobile terminals;when a slave mobile terminal of the one or more mobile terminals has downloaded a data task segment allocated by the master mobile terminal, sending the downloaded data task segment to the master mobile terminal;storing the data task segment by the master mobile terminal and sending this data task segment to one or more other mobile terminals.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 8. A system for data downloading, comprising a server, at least one master mobile terminal, and at least one slave mobile terminal; wherein:the master mobile terminal is configured to control the at least one slave mobile terminal;the master mobile terminal obtains information about size of data to be downloaded from the server;the master mobile terminal calculates task segments to be downloaded by one or more of the master mobile terminal and the at least one slave mobile terminal;the master mobile terminal is designed to divide the data to be downloaded into multiple data task segments, allocate the data task segments to one or more of the master mobile terminal and the at least one slave mobile terminal, and send the data segments downloaded by the one or more of the master mobile terminal and the at least one slave mobile terminal to one or more other mobile terminals;the at least one slave mobile terminal is designed to download a data segment allocated by the master mobile terminal and send the downloaded data segment to the master mobile terminal;the master mobile terminal is connected to the at least one of slave mobile terminal through a network;the server is designed to store data to be downloaded; andeach of the mobile terminal is connected to the server via a communication network so as to download data.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 9. The system according to claim 8, wherein the network is a Bluetooth local network, an infrared local network and/or an Ultra Wide Band local network.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 10. The method according to claim 1, further comprising the following steps of:obtaining location information of the master mobile terminal in a download group as well as characteristic information of data being downloaded;locating a mobile terminal that sent a data download request and verifying whether the data download request is met and the master mobile terminal is located in the download group within local connections;the mobile terminal that sent the data download request joining the download group as a slave mobile terminal in order to download data.(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 11. The method according to claim 10, further comprising:sending downloaded data from a slave mobile terminal in the download group to the master mobile terminal after the download is completed;sending the data, which is downloaded by one or more other mobile terminals, by the master mobile terminal to the slave mobile terminal in the download group.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 12. The method according to claim 10, wherein the step, that the mobile terminal that sent the data download request joining the download group, comprising the steps of :inviting the mobile terminal that sent the data download request to join the download group by the master mobile terminal in the download group;the mobile terminal, that sent the data download request, authenticating the master mobile terminal, and, if the authentication is successful, joining the download group.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 13. The method according to claim 10, further comprising:determining whether the data download requirement of the mobile terminal is met in accordance with the information, including ID, type, and size of data to be downloaded, carried in the download request and the location information obtained in the locating step.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184965(Integer), 14. The method according to claim 10, further comprising:obtaining location information of the master mobile terminal in the download group, which is in a downloading state, with CELL ID or AGPS; and/orlocating the mobile terminal that sent the data download request with CELL ID or AGPS.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184965(Integer), FIELD OF THE PRESENT INVENTION [0001]The present invention relates to information communication technology field, and more particularly, to a method and a system for downloading data to mobile terminals and for implementing data sharing between mobile terminals. BACKGROUND OF THE PRESENT INVENTION [0002]With the development of mobile communication technology, mobile terminals can also be used for entertainment, such as viewing a movie and downloading large-size software, besides the basic communication function. Our entertainment space can be widened if a mobile terminal may be used for entertainment, for example, during a journey or in remote areas where mobile service coverage is available, due to the portability of the mobile terminal. The mobile terminal can be utilized not only to browse news and information through Internet, but also to view movies. [0003]In the prior art, a mobile terminal can access the internet through GPRS (General Packet Radio Service) or by dialing up, and download movies in form of media streams so as to view the movies. However, with such a download technique, each mobile terminal can only download data separately. If a same movie is to be viewed with multiple mobile terminals, each of the mobile terminals has to download that movie respectively, resulting in repeated download and the waste of bandwidth. In addition, with the above download technique, the download speed is usually lower than the playback speed, resulting in poor movie viewing experience. Furthermore, since each mobile terminal has to download the movie, a large part of bandwidth will be occupied, and the occupation time of bandwidth resource will be increased, thereby the cost will be increased accordingly. [0004]Streaming media is a new network transmission technique, which, in brief, refers to the transmission of multimedia files over network with streaming technique. The streaming technique is a network transmission technique, which, by compressing and loading continuous video and audio data onto the servers at the website, enables the users to view and listen while downloading, instead of waiting the entire compressed file to be downloaded to the mobile terminal. [0005]With the development of the radio technology, the bandwidth of wireless data access is continuously increased, and the processing capacity of a mobile terminal is improved, and a wide variety of high-quality streaming media services become matured. Though the streaming media platform, a mobile terminal can play news, movies, or music in audio/video streams at a low code rate and low speed, and play streaming media in live broadcast services; the mobile terminal can download services and media files. In addition, media files may be copyright-protected with the DRM (Digital Right Management) technique. [0006]In the prior art, the method for playing with a mobile terminal is that, the mobile terminal establishes a connection to the network first; then, the mobile terminal downloads the data streams of streaming media from network side while playing the data streams in real time. This method is mainly characterized by its real-time and heavy occupation of network bandwidth. [0007]In practical applications, there is often the case that two users wish to view a same streaming media at the same time. With the method described above, each of the two users has to establish a connection to the network respectively, as shown in FIG. 1. Then, each of the two users has to establish an over-the-air channel and download the streaming media via the air interface of the over-the-air channel, and play the streaming media locally respectively. [0008]In the above described method for playing streaming media with a mobile terminal: [0009]Overload of the device at the network side may occur, if there are many users downloading and viewing streaming media at the same time. [0010]Too many resources may be occupied. The waste of the resources will occur when two users download the same content, if the two users are not distant from each other and are in the same cell of a base station. Furthermore, two many data connections should not be established in one cell. [0011]This method suppresses the users' enthusiasm to view streaming media to a certain degree, because the users have to not only buy the copyright but also pay the download expense. SUMMARY OF THE PRESENT INVENTION [0012]The present invention is to provide a method for downloading data to mobile terminals, a system for downloading data, and a mobile terminal that utilizes that method. The present invention also provides a method and a system for implementing data sharing between mobile terminals, which implements data sharing and transmission between mobile terminals. [0013]The present invention provides a method for downloading data to mobile terminals, so that the mobile terminal can join a shared download within the local connections. [0014]In one aspect of the present invention, the method for downloading data to mobile terminals may include: [0015]dividing data to be downloaded into multiple data task segments by a master mobile terminal, and allocating the data task segments to one or more mobile terminals; [0016]downloading the data by the mobile terminals in accordance with the allocated data task segments; [0017]judging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure. [0018]Preferably, the method may further comprise the step of sending a request to at least one mobile terminal from the master mobile terminal through a local network before the master mobile terminal allocates the data task segments to the individual mobile terminals. [0019]Preferably, the method may further comprise the step of obtaining the size of the data to be downloaded and determining the size of a data task segment by the master mobile terminal according to the size of the data before dividing the data into multiple data task segments. [0020]Alternatively, in the case that a mobile terminal does not download a data task segment within a predefined duration, the master mobile terminal will allocate this data task segment to one or more other mobile terminals. [0021]Wherein, a mobile terminals, that has finished downloading of an allocated data task segment, obtains IDs of one or more other mobile terminals from the master mobile terminal, and sends the data of the downloaded task segment to the one or more other mobile terminals in accordance with the obtained IDs. [0022]Preferably, the method may further include the steps of: [0023]reporting a message from a mobile terminal, that has finished downloading of an allocated data task segment, to the master mobile terminal indicating the allocated task segment has been downloaded; [0024]notifying one or more other mobile terminals of the message by the master mobile terminal; [0025]obtaining the downloaded data task segment by the one or more other mobile terminals from that mobile terminal that has finished downloading of the allocated data task segment. [0026]Preferably, the method may further include the steps of: [0027]when the master mobile terminal has downloaded a data task segment, sending the downloaded data task segment to one or more other mobile terminals; [0028]when a slave mobile terminal has downloaded a data task segment allocated by the master mobile terminal, sending the downloaded data task segment to the master mobile terminal; storing the data task segment by the master mobile terminal and sending this data task segment to one or more other mobile terminals. [0029]The present invention also provides a system for data downloading, the system include a server, at least one master mobile terminal, and at least one slave mobile terminal; wherein: [0030]the master mobile terminal is designed to control the slave mobile terminals to download data segments and send the data segments downloaded by the master mobile terminal and/or the at least one slave mobile terminal to one or more other mobile terminals; [0031]the at least one slave mobile terminal is designed to download a data segment allocated by the master mobile terminal and send the downloaded data segment to the master mobile terminal; [0032]the master mobile terminal is connected to the at least one of slave mobile terminal through a network; [0033]the server is designed to store data to be downloaded; each of the mobile terminals is connected to the server via a communication network so as to download data. [0034]Wherein the network may be a Blue Teeth local network, an infrared local network and/or an Ultra Wide Band local network. [0035]The present invention also provides a mobile terminal, which is connected to one or more other mobile terminals through a network, including: [0036]a control unit, designed to control the mobile terminals connected therewith to download data and implement sharing of the downloaded data; [0037]a download unit, designed to obtain the size of data to be downloaded and execute download task in accordance with the task segments to be downloaded. [0038]Preferably, the control unit may include: [0039]a calculating unit, designed to calculate the task segments of data to be downloaded with the size of data to be downloaded; [0040]an allocating unit, designed to allocate the calculated task segments to the mobile terminals according to a predefined rule and distribute a data segment downloaded by a mobile terminal to one or more other mobile terminals. [0041]In another aspect of the present invention, the method for downloading data to mobile terminals may include the following steps of: [0042]obtaining location information of a master mobile terminal in a download group as well as characteristic information of data being downloaded; [0043]locating a mobile terminal that sent a data download request and verifying whether the data download request is met and the master mobile terminal is located in a download group within local connections; po the mobile terminal that sent the data download request joining the download group as a slave mobile terminal in order to download data. [0044]Preferably, the method may further include: [0045]sending downloaded data from a slave mobile terminal in the download group to the master mobile terminal after the download is completed; sending the data, which is downloaded by one or more other mobile terminals, by the master mobile terminal to the slave mobile terminal in the download group. [0046]Wherein the step, that the mobile terminal that sent the data download request joining the download group, may include the steps of: [0047]inviting the mobile terminal that sent the data download request to join the download group by the master mobile terminal in the download group; [0048]the mobile terminal, that sent the data download request, authenticating the master mobile terminal, and, if the authentication is successful, joining the download group. [0049]Preferably, the method may further includes: [0050]determining whether the data download requirement of the mobile terminal is met in accordance with the information, including ID, type, and size of data to be downloaded, carried in the download request and the location information obtained in the locating step. [0051]Preferably, the method may further include: [0052]obtaining location information of the master mobile terminal in the download group, which is in a downloading state, with CELL ID or AGPS; and/or [0053]locating the mobile terminal that sent the data download request with CELL ID or AGPS. [0054]The present invention also provides a mobile terminal, which may include: [0055]a network data flow control module, designed to establish a connection with network side and download data from the network side, and send the downloaded data to a network data storage and control module; [0056]a network data storage and control module, designed to buffer the data from the network data flow control module and send the buffered data to a local data flow control module according to a request message; [0057]a local data flow control module, designed to send a request message to the network data storage and control module and send the data stored in the network data storage and control module to one or more other mobile terminals according to a predefined QoS. [0058]The mobile terminal may further include: [0059]a data sharing and communication management module, designed to receive a data connection request message from one or more other mobile terminals, perform authentication and encryption operations for one or more other mobile terminals, and send the authenticated result to the local data flow control module. [0060]Optionally, the terminal may further include: [0061]a local application data application module, designed to send a request to the network data storage and control module and receive data from the network data storage and control module. [0062]The present invention also provides another mobile terminal, which includes: [0063]a network data storage and control module, designed to receive and buffer data from a master mobile terminal and send the buffered data to a local application data application module and a local data flow control module according to a request message; [0064]a local application data application module, designed to send a request message to the network data storage and control module and receive data from the network data storage and control module; [0065]a local data flow control module, designed to send a request message to the network data storage and control module and send the data from the network data storage and control module to other slave mobile terminals according to a predefined QoS. [0066]The mobile terminal may further include: [0067]a data sharing and communication management module, designed to receive a data connection request message from other slave mobile terminals, perform authentication and encryption control operations for other slave mobile terminals, and send the authenticated result to the local data flow control module. [0068]In another aspect of the present invention, the system for implementing data sharing between mobile terminals provided in the present invention may include: [0069]a master mobile terminal, designed to establish a connection with network side and download data from the network side, establish a local data sharing network with slave mobile terminals in a wired or wireless manner, and send the downloaded data to the slave mobile terminals through the local data sharing network; [0070]one or more slave mobile terminals, designed to establish a local data sharing network with the master mobile terminal in a wired or wireless manner, receive data from the master mobile terminal, and send the received data to other slave mobile terminals. [0071]The network formed by the master mobile terminal and all the other mobile terminals are of a star shaped structure, a chain shaped structure, or a tree structure. [0072]The present invention also provides another system for implementing data sharing between mobile terminals, which may include: [0073]a master mobile terminal, designed to establish a connection with network side and download data from the network side, establish a local data sharing network with one or more slave master mobile terminals in a wired or wireless manner, and send the downloaded data to the one or more slave master mobile terminals through the local data sharing network; [0074]one or more slave master mobile terminals, designed to receive streaming media data from the master mobile terminal and process the data accordingly, receive a data connection request from one or more other mobile terminals, perform access admission control operations, such as authentication, encryption, etc., for one or more other mobile terminals, and transmit the streaming media to one or more other mobile terminals according to a predefined QoS; in the case that an abnormity occurs in the master mobile terminal, the slave master mobile terminals receive shared data from one or more other mobile terminals and substitutes the master mobile terminal to implement the download function; [0075]at least one mobile terminal device, designed to establish a local data sharing network with the master mobile terminal in a wired or wireless manner, receive data from the master mobile terminal through the local data sharing network, and send the received data to the slave master mobile terminals. [0076]In the present invention, multiple mobile terminals are enabled to download data segments of a data respectively and share the downloaded data segments among them, thus the download time may be reduced and the download speed may be increased, for example, if there are N mobile terminals downloading data, the download time may be reduced to 1/N of the time required by a single mobile terminal, and the download speed may be increased u N times, which is adaptive to the playback speed of a movie, thereby improving the experience of the users. [0077]By locating the mobile terminal that sent the data download request, and by verifying if the data download requirement of the mobile terminal is met and the master mobile terminal is located in the shared download group within local connections in accordance with the location information of the master mobile terminal in the shared download group and characteristic information of the data being downloaded, the mobile terminal that sent the data download request is enabled to join the shared download group as a slave mobile terminal and perform the shared data download. In the present invention, a mobile terminal can join an appropriate shared download group in the local network at any time, without the need of negotiating with other mobile terminals. Therefore, the difficulties in implementation of shared data download may be mitigated, and the applicability of shared data download may be improved. [0078]It can be seen that, with the above technical scheme, network resources can be saved, the load over the equipment at network side may be reduced, and multiple mobile terminals may be enabled to play back the streaming media while a mobile terminal downloads the streaming media, thereby reducing the cost in downloading data by mobile terminals. BRIEF DESCRIPTION OF THE DRAWINGS [0079]FIG. 1 is a schematic diagram illustrating two users connect to the network respectively in the prior art; [0080]FIG. 2 is a flow diagram of a download method according to an embodiment of the present invention; [0081]FIG. 3 is a flow diagram of a download system according to an embodiment of the present invention; [0082]FIG. 4 is a schematic diagram of a mobile terminal according to an embodiment of the present invention; [0083]FIG. 5 is a flow diagram of the method for downloading data to mobile terminals according to another embodiment of the present invention; [0084]FIG. 6 shows the principle of a method for data sharing between mobile terminals according to an embodiment of the present invention; [0085]FIG. 7 is a processing flow chart of a method for data sharing between mobile terminals according to an embodiment of the present invention; [0086]FIG. 8 is a schematic diagram of a serial structure formed by a master mobile terminal and slave mobile terminals; [0087]FIG. 9 is a schematic diagram of a star shaped structure formed by a master mobile terminal and slave mobile terminals; [0088]FIG. 10 is a structural diagram of a master mobile terminal according to an embodiment of the present invention; [0089]FIG. 11 is a structural diagram of a slave mobile terminal according to an embodiment of the present invention; [0090]FIG. 12 is a structural diagram of a system according to an embodiment of the present invention; [0091]FIG. 13 is a structural diagram of a system according to another embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0092]The method for downloading data to mobile terminals and the supporting system thereof provided in an embodiment of the present invention utilize multiple mobile terminals to download the individual data segments of a data respectively, in which one mobile terminal (also referred to as the master mobile terminal) controls the download progress and sending the data downloaded by each mobile terminal to the other mobile terminals. Thereby, the download may be speeded up. The core idea of the method and the system for data sharing between mobile terminals according to an embodiment of the present invention is that, a mobile terminal establishes a connection to the network side to download streaming media, while other mobile terminals receive and play the streaming media through the local data sharing network. [0093]Hereunder the embodiments of the present invention will be described with reference to the attached drawings. [0094]Here we suppose that mobile terminals A, B, C, . . . , and N wish to obtain data “DATA” from the server. The mobile terminals A, B, C, . . . , and N download data through a communication network (e.g., a 3 G network, a GPRS network, etc.). The mobile terminals A, B, C, . . . , and N are connected through a high speed local network, which can be a local network constructed with Blue Tooth, infrared, or UWB technique. The transmission rate of the local network is required to be much higher than that of the communication network for over-the-air download. More generally, the transmission rate of the local network is at least higher than the product of the number of mobile terminals and the over-the-air download rate. [0095]Due to the fact that a local network usually has a small radius of coverage (e.g., a radius of 10 m) but a high transmission rate (e.g., much higher than the transmission rate of a communication network), the mobile terminals described in the present invention should be within the coverage. In contrast, the system network has a lower transmission rate but a wider coverage. [0096]In order to implement the embodiment of the present invention, one of the mobile terminals A, B, C, . . . , and N is designated as the master mobile terminal. This master mobile terminal only downloads data, but also allocates task segments for data downloading and distributes the download tasks to the other mobile terminals. The other mobile terminals are designated as slave mobile terminals, which are mainly responsible for data downloading. [0097]To simplify the description, here we suppose that the mobile terminal A is the master mobile terminal and the mobile terminals B, C, . . . , and N are slave mobile terminals, as shown in FIG. 2. Hereunder the process that the mobile terminals A, B, C, . . . , and N cooperate for data downloading will be described. [0098]Step S01, The master mobile terminal A originates an invitation to the mobile terminals B, C, . . . , and N through the local network for data downloading. [0099]Step S02, A part or all of slave mobile terminals B, C, . . . , and N accept the invitation from the master mobile terminal A. The master mobile terminal A records the IDs of the slave mobile terminals that have accepted the invitation. To simplify the description, hereunder we suppose all the slave mobile terminals accept the invitation from the master mobile terminal A. [0100]Step S03, The master mobile terminal A obtains from the server the information about the size of DATA file to be downloaded. [0101]Step S04, The master mobile terminal A calculates the task segments to be downloaded by the mobile terminals A, B, C, . . . , and N with a predefined algorithm. [0102]The algorithm can be an average allocation algorithm, that is, the task for downloading DATA is divided into several (e.g., M, here it is supposed that N<1)), it is considered that this mobile terminal has failed. In that case, the master mobile terminal can reallocate the data task segment, which has been allocated to this mobile terminal, to another mobile terminal. [0106]Step S07, After a mobile terminal has finished the download of the allocated task segments, the other mobile terminals is enabled to obtain the downloaded task segment data. In the embodiments of the present invention, there are three ways for the other mobile terminals to be enabled to obtain the downloaded task segment data. The first way, the mobile terminal sends the downloaded task segment data to the other slave mobile terminals. At this time, the mobile terminal has to obtain from the master mobile terminal A the IDs of all slave mobile terminals involved in download, and then send the task segment data depending on the mobile terminal IDs. The second way, the mobile terminal reports a task segment download completion message to the master mobile terminal, which in turn notifies the other slave mobile terminals of the message, so that the other slave mobile terminals can obtain the downloaded data from that mobile terminal. The third way, when the slave mobile terminals B, C, . . . , and N finish the task segments allocated by the master mobile terminal A, the downloaded task segment data will be sent to the master mobile terminal A. The master mobile terminal A stores the task segment data sent from the slave mobile terminals B, C, . . . , or N, and sends the data to the other slave mobile terminals. When its own task segments is completed, the master mobile terminal A stores the task segment data and sends the data to the slave mobile terminals B, C, . . . , and N. [0107]Step S08, The master mobile terminal A judges whether the download of “DATA” is finished. If the download is finished, the master mobile terminal A terminates the download procedure. Otherwise, the master mobile terminal A executes step S05, i.e., the master mobile terminal A allocates task segments that have not been finished to the mobile terminals that have finished their task segments, and S05-S08 is repeated, till the download is completed. [0108]FIG. 3 shows a data download system provided in an embodiment if the present invention. The system includes a server that stores and manages the data to be downloaded and at least two mobile terminals. [0109]At least one of the mobile terminals is the master mobile terminal, which is adapted to control other mobile terminal(s) to download a data segment, and send the downloaded data to mobile terminal(s). The slave mobile terminal(s) is (are) adapted to download data segments allocated by the master mobile terminal and send the downloaded data segments to the master mobile terminal. The mobile terminals are connected with each other through a local network and are connected to the server through a communication network (e.g., a 3 G network, a GPRS network, etc.), so as to download data from the server. The local network is a high-speed local wireless network, such as a local network constructed with Blue Teeth, infrared, or UWB (Ultra Wide Band) technique, with a transmission rate much higher than that of the over-the-air download communication network. In general, the transmission rate of the local network is at least higher than the product of the number of mobile terminals and the over-the-air download rate. Due to the fact that a local network usually has a small coverage radius (e.g., a radius of 10m) but a high transmission rate (e.g., much higher than the transmission rate of a communication network), the mobile terminals described in this embodiment of the present invention should be within the coverage. However, the system network has a lower transmission rate but a wider coverage. [0110]As shown in FIG. 4, a mobile terminal, i.e., as the master mobile terminal, provided in the embodiment of the present invention may include: [0111]a control unit, adapted to control the data download of the individual mobile terminals and implement the sharing of the downloaded data; a download unit, adapted to obtain the size of data to be downloaded and execute a download task in accordance with the download task segments. [0112]The control unit may include: a calculating unit, adapted to calculate the individual task segments for downloading data depending upon the size of the data to be downloaded; a allocating unit, adapted to allocate the individual calculated task segments to the mobile terminals with a predefined algorithm, so that the mobile terminals can execute the download task depending upon the allocated task segments. The allocating unit is also adapted to send the data segments downloaded by a slave mobile terminal to the other slave mobile terminals. [0113]The server is designed to store the data to be downloaded. [0114]It is to be noted that the master mobile terminal must be a mobile terminal according to the embodiments of the present invention, and the slave mobile terminal can be mobile terminals according to the embodiments of the present invention or existing mobile terminals. [0115]In the embodiments of the present invention, multiple mobile terminals are enabled to download data segments of a data respectively and share the downloaded data segments among them, thus the download time may be reduced and the download speed may be increased, for example, if there are N mobile terminals downloading data, the download time may be reduced to 1/N of the time required by a single mobile terminal, and the download speed may be increased u N times, which is adaptive to the playback speed of a movie, thereby meeting the requirement of the users. In addition, the method according to the embodiment of the present invention, compared with the method of downloading entire DATA by each mobile terminal respectively, can save the bandwidth occupied by downloading, since each of the N mobile terminals needs to download only a specific data segment. [0116]A mobile terminal according to the embodiments of the present invention can join a shared download group that meets its data download requirement and has a master mobile terminal within its local connections, by obtaining the location informat(String), 发明领域 [0001] 本发明涉及信息通信技术领域,尤其涉及一种向移动终端下载数据并实现移动终端间数据共享的方法及系统。 背景技术 [0002] 随着移动通信技术的发展,移动终端除了具备基本的通信功能外,还可以用于娱乐,如看电影、下载大型软件等。 由于移动终端的便携性,如果可以使用移动终端进行娱乐,例如在旅途中或在移动服务覆盖的偏远地区,可以拓宽我们的娱乐空间。 移动终端不仅可以用来通过互联网浏览新闻和信息,还可以用来观看电影。 [0003] 现有技术中,移动终端可以通过GPRS(General Packet Radio Service,通用分组无线业务)或拨号上网,并以媒体流的形式下载电影,以供观看电影。 然而,采用这种下载技术,每个移动终端只能单独下载数据。 如果要用多个移动终端观看同一部电影,则每个移动终端都必须分别下载该电影,造成重复下载和带宽的浪费。 另外,采用上述下载技术,下载速度通常低于播放速度,导致观影体验不佳。 此外,由于每个移动终端都要下载电影,因此会占用很大一部分带宽,增加带宽资源的占用时间,从而增加成本。 [0004] 流媒体是一种新兴的网络传输技术,简单来说就是利用流媒体技术在网络上传输多媒体文件。 流媒体技术是一种网络传输技术,通过将连续的视频、音频数据压缩加载到网站的服务器上,使用户边下载边看边听​​,而不是等待整个压缩文件下载到手机上 终端。 [0005] 随着无线技术的发展,无线数据接入的带宽不断增加,移动终端的处理能力不断提高,各种高质量的流媒体服务也日趋成熟。 通过流媒体平台,移动终端可以在音视频流中进行低码率低速播放新闻、电影或音乐,以及在直播业务中播放流媒体; 移动终端可以下载服务和媒体文件。 此外,媒体文件可能受到 DRM(数字版权管理)技术的版权保护。 [0006] 现有技术中,移动终端的玩法是,移动终端先与网络建立连接; 然后,移动终端在实时播放数据流的同时,从网络侧下载流媒体数据流。 该方法的主要特点是实时性强,占用网络带宽大。 [0007] 在实际应用中,经常会出现两个用户希望同时观看同一个流媒体的情况。 采用上述方法,两个用户分别需要建立网络连接,如图1所示。然后,两个用户分别建立无线信道,通过网络下载流媒体。 无线频道的空中接口,分别在本地播放流媒体。 [0008] 在上述移动终端播放流媒体的方法中: [0009] 如果有很多用户同时下载和观看流媒体,可能会导致网络侧设备过载。 [0010] 可能占用太多资源。 当两个用户下载相同的内容时,如果两个用户相距不远,并且在一个基站的同一个小区内,就会造成资源浪费。 此外,不应在一个小区中建立两个多数据连接。 [0011]这种方式在一定程度上抑制了用户观看流媒体的积极性,因为用户不仅要购买版权,还要支付下载费用。 发明内容 [0012] 本发明的目的在于提供一种移动终端数据下载方法、数据下载系统及应用该方法的移动终端。 本发明还提供了一种实现移动终端间数据共享的方法及系统,实现了移动终端间的数据共享和传输。 [0013] 本发明提供了一种向移动终端下载数据的方法,使得移动终端可以在本地连接内加入共享下载。 [0014] 在本发明的一个方面,所述向移动终端下载数据的方法可以包括: [0015] 主移动终端将待下载数据划分为多个数据任务段,将数据任务段分配给一个或多个移动终端; [0016] 移动终端根据分配的数据任务段下载数据; [0017] 主移动终端判断是否有未下载的数据任务段; 若是,则将数据任务段分配给至少一个数据任务段下载完成的移动终端。 如果否,则终止下载过程。 [0018] 优选地,该方法还包括在主移动终端为各个移动终端分配数据任务段之前,通过本地网络从主移动终端向至少一个移动终端发送请求的步骤。 [0019] 优选地,该方法还包括在将数据划分为多个数据任务段之前,主移动终端根据数据大小确定待下载数据的大小并确定数据任务段的大小的步骤。 [0020] 或者,在移动终端在预定时间内没有下载数据任务段的情况下,主移动终端将该数据任务段分配给一个或多个其他移动终端。 [0021] 其中,完成分配的数据任务段下载的移动终端从主移动终端获取一个或多个其他移动终端的ID,并将下载的任务段的数据发送给主移动终端中的一个或多个其他移动终端。 根据获得的ID。 [0022] 优选地,该方法还可以包括以下步骤: [0023] 分配数据任务段下载完成的移动终端向主移动终端上报分配任务段下载完毕的消息; [0024] 主移动终端将该消息通知一个或多个其他移动终端; [0025] 一个或多个其他移动终端从已完成下载分配的数据任务段的移动终端获取下载的数据任务段。 [0026] 优选地,该方法还可以包括以下步骤: [0027] 当主移动终端下载数据任务段时,将下载的数据任务段发送给一个或多个其他移动终端; [0028] 当从移动终端下载了主移动终端分配的数据任务段后,将下载的数据任务段发送给主移动终端; 主移动终端存储数据任务段,并将该数据任务段发送给一个或多个其他移动终端。 [0029] 本发明还提供了一种数据下载系统,该系统包括服务器、至少一个主移动终端和至少一个从移动终端; 其中: [0030] 主移动终端用于控制从移动终端下载数据段,并将主移动终端和/或至少一个从移动终端下载的数据段发送给一个或多个其他移动终端。 [0031]至少一个从移动终端,用于下载主移动终端分配的数据段,并将下载的数据段发送给主移动终端; [0032] 主移动终端通过网络连接到从移动终端中的至少一个; [0033] 服务器用于存储要下载的数据; 每个移动终端通过通信网络连接到服务器以下载数据。 [0034] 其中,网络可以是蓝牙局域网、红外局域网和/或超宽带局域网。 [0035] 本发明还提供了一种移动终端,通过网络连接一个或多个其他移动终端,包括: [0036] 控制单元,用于控制与其连接的移动终端下载数据,并实现下载数据的共享; [0037] 下载单元,用于获取待下载数据的大小,并根据待下载的任务段执行下载任务。 [0038] 优选地,所述控制单元可以包括: [0039] 计算单元,用于计算待下载数据的任务段和待下载数据的大小; [0040] 分配单元,用于将计算出的任务段按照预定规则分配给移动终端,并将移动终端下载的数据段分配给其他一个或多个移动终端。 [0041] 在本发明的另一个方面,所述的移动终端下载数据的方法可以包括以下步骤: [0042] 获取下载组中主移动终端的位置信息以及正在下载的数据的特征信息; [0043] 定位发送数据下载请求的移动终端,并验证是否满足数据下载请求以及主移动终端位于本地连接内的下载组; p 发送数据下载请求的移动终端作为从移动终端加入下载组以便下载数据。 [0044] 优选地,该方法还可以包括: [0045] 下载完成后,将下载组中从移动终端的下载数据发送给主移动终端; 主移动终端将一个或多个其他移动终端下载的数据发送给下载组中的从移动终端。 [0046] 其中,发送数据下载请求的移动终端加入下载组的步骤可以包括: [0047] 下载组中的主移动终端邀请发送数据下载请求的移动终端加入下载组; [0048] 发送数据下载请求的移动终端对主移动终端进行鉴权,鉴权成功则加入下载组。 [0049] 优选地,该方法还可以包括: [0050] 根据下载请求中携带的信息,包括下载数据的ID、类型、大小和定位步骤中获取的位置信息,判断是否满足移动终端的数据下载要求。 [0051] 优选地,该方法还可以包括: [0052] 通过CELL ID或AGPS获取下载组中处于下载状态的主移动终端的位置信息; 和/或 [0053] 通过CELL ID或AGPS定位发送数据下载请求的移动终端。 [0054] 本发明还提供了一种移动终端,包括: [0055] 网络数据流控制模块,用于与网络侧建立连接并从网络侧下载数据,并将下载的数据发送给网络数据存储和控制模块; [0056]网络数据存储及控制模块,用于缓存来自网络数据流控模块的数据,并根据请求报文将缓存的数据发送给本地数据流控模块; [0057] 本地数据流控制模块,用于向网络数据存储与控制模块发送请求消息,并将网络数据存储与控制模块中存储的数据按照预定义的QoS发送给一个或多个其他移动终端。 [0058] 移动终端还可以包括: [0059] 数据共享与通信管理模块,用于接收来自一个或多个其他移动终端的数据连接请求消息,对一个或多个其他移动终端进行鉴权和加密操作,并将鉴权结果发送给本地数据流控制模块。 [0060] 可选的,该终端还可以包括: [0061] 本地应用数据应用模块,用于向网络数据存储与控制模块发送请求,并接收来自网络数据存储与控制模块的数据。 [0062] 本发明还提供了另一种移动终端,包括: [0063] 网络数据存储及控制模块,用于接收和缓存来自主移动终端的数据,并根据请求消息将缓存的数据发送给本地应用数据应用模块和本地数据流控制模块; [0064] 本地应用数据应用模块,用于向网络数据存储与控制模块发送请求消息,并接收来自网络数据存储与控制模块的数据; [0065] 本地数据流控制模块,用于向网络数据存储与控制模块发送请求消息,并将来自网络数据存储与控制模块的数据按照预定义的QoS发送给其他从属移动终端。 [0066] 移动终端还可以包括: [0067] 数据共享与通信管理模块,用于接收其他从属移动终端的数据连接请求消息,对其他从属移动终端进行鉴权和加密控制操作,并将鉴权结果发送给本地数据流控模块。 [0068] 在本发明的另一方面,本发明提供的实现移动终端间数据共享的系统,包括: [0069] 主移动终端,旨在与网络侧建立连接并从网络侧下载数据,以有线或无线方式与从移动终端建立本地数据共享网络,并将下载的数据通过 本地数据共享网络; [0070] 一个或多个从移动终端,用于通过有线或无线方式与主移动终端建立本地数据共享网络,接收来自主移动终端的数据,并将接收到的数据发送给其他从移动终端。 [0071] 主移动终端与所有其他移动终端组成的网络可以是星形结构、链形结构或树形结构。 [0072] 本发明还提供了另一种实现移动终端间数据共享的系统,包括: [0073] 主移动终端,设计用于与网络侧建立连接并从网络侧下载数据,以有线或无线方式与一个或多个从主移动终端建立本地数据共享网络,并将下载的数据发送到从主移动终端 一个或多个从主移动终端通过本地数据共享网络; [0074]一个或多个从主移动终端,用于接收来自主移动终端的流媒体数据并进行相应的数据处理,接收来自一个或多个其他移动终端的数据连接请求,执行接入准入控制操作,例如认证、加密、 等,针对一个或多个其他移动终端,按照预先定义的QoS向一个或多个其他移动终端传输流媒体; 当主移动终端出现异常时,从属主移动终端接收来自一个或多个其他移动终端的共享数据,并替代主移动终端实现下载功能。 [0075] 至少一个移动终端设备,用于与主移动终端以有线或无线方式建立本地数据共享网络,通过本地数据共享网络接收来自主移动终端的数据,并将接收到的数据发送给从主移动终端 移动终端。 [0076] 本发明能够使多个移动终端分别下载一个数据的数据段,并在它们之间共享下载的数据段,从而可以减少下载时间,提高下载速度,例如,如果有N个移动终端 终端下载数据,下载时间可以减少到单个移动终端所需时间的1/N,下载速度可以提高uN倍,自适应电影播放速度,提升体验 的用户。 [0077] 通过定位发送数据下载请求的移动终端,根据主移动终端的位置信息验证是否满足移动终端的数据下载要求,以及主移动终端是否位于本地连接内的共享下载组中 共享下载组中的移动终端和正在下载的数据的特征信息,使得发送数据下载请求的移动终端作为从移动终端加入共享下载组并进行共享数据下载。 在本发明中,移动终端可以随时加入本地网络中合适的共享下载组,而不需要与其他移动终端协商。 因此,可以降低共享数据下载的实现难度,提高共享数据下载的适用性。 [0078] 可见,采用上述技术方案,可以节省网络资源,降低网络侧设备的负载,实现一个移动终端下载流媒体的同时,实现多个移动终端播放流媒体。 媒体,从而降低移动终端下载数据的成本。 附图的简要说明 [0079] 图1为现有技术中两个用户分别接入网络的示意图; [0080] 图2是本发明一个实施例的下载方法的流程图; [0081] 图3是根据本发明一个实施例的下载系统的流程图; [0082] 图4是本发明一个实施例的移动终端的示意图; [0083] 图5为本发明另一实施例的移动终端数据下载方法的流程图。 [0084] 图6示出了根据本发明实施例的移动终端之间的数据共享方法的原理。 [0085] 图7为本发明实施例的移动终端间数据共享方法的处理流程图; [0086] 图8是主移动终端和从移动终端组成的串联结构示意图; [0087] 图9是主移动终端和从移动终端组成的星形结构示意图; [0088] 图10是本发明一个实施例的主移动终端的结构图; [0089] 图11为本发明实施例的从移动终端的结构图; [0090] 图12为本发明实施例的系统结构图; [0091] 图13为本发明另一实施例的系统结构图。 具体实施方式 [0092] 本发明实施例提供的移动终端数据下载方法及其配套系统利用多个移动终端分别下载数据的各个数据段,其中一个移动终端(也称为主移动终端) ) 控制下载进度并将每个移动终端下载的数据发送给其他移动终端。 从而,可以加速下载。 本发明实施例的移动终端数据共享方法及系统的核心思想是,移动终端与网络侧建立连接下载流媒体,其他移动终端接收并播放流媒体。 媒体通过本地数据共享网络。 [0093] 下面将参考附图描述本发明的实施例。 [0094] 这里我们假设移动终端 A, B, C, . . . , 和 N 希望从服务器获取数据“DATA”。 移动终端A、B、C、……。 . . ,N通过通信网络(如3G网络、GPRS网络等)下载数据。 移动终端A、B、C、……。 . . , 和 N 通过高速本地网络连接,可以是蓝牙、红外或 UWB 技术构建的本地网络。 无线下载要求本地网络的传输速率远高于通信网络的传输速率。 更一般地,本地网络的传输速率至少高于移动终端数量与空中下载速率的乘积。 [0095] 由于本地网络通常具有较小的覆盖半径(例如半径为10 m)但传输速率较高(例如远高于通信网络的传输速率),因此在本文中描述的移动终端 本发明应在保护范围之内。 相比之下,系统网络的传输速率较低,但覆盖范围较广。 [0096] 为了实施本发明实施例,移动终端A、B、C、...中的一个。 . . , N 被指定为主移动终端。 该主移动终端只进行数据下载,还分配数据下载任务段,将下载任务分发给其他移动终端。 其他移动终端被指定为从移动终端,主要负责数据下载。 [0097] 为简化描述,这里假设移动终端A为主移动终端,移动终端B、C、...。 . . ,和N为从属移动终端,如图2所示。以下是移动终端A,B,C,...的过程。 . . , 和 N 协作进行数据下载将被描述。 [0098] 脚步 01 ,主移动终端A向移动终端B,C,...发出邀请。 . . , N 通过本地网络进行数据下载。 [0099] 脚步 02 ,部分或全部从属移动终端B,C,。 . . , N接受主移动终端A的邀请。主移动终端A记录接受邀请的从移动终端的ID。 为了简化描述,下面假设所有从移动终端都接受了主移动终端A的邀请。 [0100] 脚步 03 ,主移动终端A从服务器获取待下载DATA文件的大小信息。 [0101] 脚步 04 ,主移动终端A计算移动终端A,B,C,...需要下载的任务段。 . . , 和 N 具有预定义的算法。 [0102]该算法可以是平均分配算法,即将下载DATA的任务分成若干个(例如M,这里假设N<1)确定)时,则认为该移动终端发生故障。 在这种情况下,主移动终端可以将已经分配给该移动终端的数据任务段重新分配给另一个移动终端。 [0106] 脚步 07 ,当一个移动终端完成分配的任务段的下载后,使其他移动终端能够获取下载的任务段数据。 在本发明实施例中,可以通过三种方式使其他移动终端获取下载的任务段数据。 第一种方式,移动终端将下载的任务段数据发送给其他从属移动终端。 此时,移动终端需要从主移动终端A获取参与下载的所有从移动终端的ID,然后根据移动终端ID发送任务段数据。 第二种方式,移动终端向主移动终端上报任务段下载完成消息,主移动终端再将该消息通知给其他从移动终端,以便其他从移动终端可以从该移动终端获取下载的数据。 第三种方式,当从属移动终端B,C,...。 . . , N完成主移动终端A分配的任务段,下载的任务段数据将发送给主移动终端A。主移动终端A存储从移动终端B、C、 . . . , 或 N, 将数据发送给其他从属移动终端。 当自己的任务段完成后,主移动终端A存储任务段数据,并将数据发送给从移动终端B、C、...。 . . , 和 N. [0107] 脚步 08,主移动终端A判断“DATA”下载是否完成。 如果下载完成,则主移动终端A终止下载过程。 否则,主移动终端A执行步骤S 05 ,即主移动终端A将未完成的任务段分配给完成任务段的移动终端,S 05 -S 08 如此反复,直到下载完成。 [0108] 图3示出了本发明实施例提供的数据下载系统。 该系统包括存储和管理待下载数据的服务器和至少两个移动终端。 [0109] 其中至少一个移动终端为主移动终端,用于控制其他移动终端下载数据段,并将下载的数据发送给移动终端。 从移动终端,用于下载主移动终端分配的数据段,并将下载的数据段发送给主移动终端。 移动终端之间通过局域网连接,并通过通信网络(例如3G网络、GPRS网络等)连接到服务器,从服务器下载数据。 本地网络是一种高速本地无线网络,例如使用Blue Teeth、红外线或UWB(Ultra Wide Band)技术构建的本地网络,其传输速率远高于空中下载通信。 网络。 一般来说,本地网络的传输速率至少要高于移动终端数量与无线下载速率的乘积。 由于本地网络通常覆盖半径小(如10m半径),但传输速率高(如远高于通信网络的传输速率),本实施例描述的移动终端 本发明应在保护范围之内。 但系统网络传输速率较低,但覆盖范围较广。 [0110] 如图4所示,本发明实施例提供的移动终端,即作为主移动终端,可以包括: [0111] 控制单元,用于控制各个移动终端的数据下载,并实现下载数据的共享; 下载单元,用于获取待下载数据的大小,并根据下载任务段执行下载任务。 [0112] 控制单元可以包括: 计算单元,用于根据待下载数据的大小计算下载数据的各个任务段; 分配单元,用于将计算出的各个任务段按照预定算法分配给移动终端,使得移动终端可以根据分配的任务段执行下载任务。 分配单元还用于将从移动终端下载的数据段发送给其他从移动终端。 [0113] 服务器用于存储要下载的数据。 [0114] 需要说明的是,主移动终端必须是本发明实施例提供的移动终端,从移动终端可以是本发明实施例提供的移动终端,也可以是现有的移动终端。 [0115] 本发明实施例能够使多个移动终端分别下载一个数据的数据段,并在它们之间共享下载的数据段,从而可以减少下载时间,提高下载速度,例如,如果有 当N个移动终端下载数据时,下载时间可以减少到单个移动终端所需时间的1/N,下载速度可以提高uN倍,自适应电影的播放速度,从而 满足用户的需求。 另外,根据本发明实施例的方法,与每个移动终端分别下载整个DATA的方法相比,可以节省下载所占用的带宽,因为N个移动终端中的每一个只需要下载一个特定的数据。 部分。 [0116]本发明实施例的移动终端通过获取主移动终端在共享下载组中的位置信息,可以加入满足自身数据下载需求且本地连接内有主移动终端的共享下载组。 正在下载的数据的特征信息。 [0117] 下面,将参照附图描述根据本发明实施例的另一种用于将数据下载到移动终端的方法。 [0118] 共享下载组中的移动终端通过通信网络(例如3G网络、GPRS网络等)从服务器下载数据。 共享下载组中有主控移动端。 主移动终端不仅进行数据下载,还分配下载任务,将下载任务分发给其他移动终端。 其他移动终端作为从移动终端,主要负责自己的下载任务。 共享下载组中的移动终端通过本地网络相互连接,本地网络是采用蓝牙、红外或UWB(超宽带)技术构建的高速本地网络,传输速率远高于普通网络。 的通信网络。 [0119] 图5为本发明实施例提供的另一种移动终端数据下载方法的流程图; 其中数据下载流程如下: [0120] 脚步 10 、服务器获取并存储处于共享下载状态的共享下载组中的主移动终端的位置信息以及正在下载的数据的特征信息。 特征信息包括正在下载的数据的文件名、类型和大小。 [0121] 本发明实施例中,服务器可以利用CELL ID或AGPS(Assisted Global Positioning System)获取主移动终端的位置信息,下面分别进行说明: [0122] 通过CELL ID获取主移动终端位置信息的原理是:服务器根据当前服务基站的位置和小区覆盖范围定位主移动终端; 若小区为全向小区,则主移动终端位于以服务基站为圆心、小区覆盖半径为半径的圆内。 如果小区是定向小区,则可以进一步确定主移动终端所在的扇区。 [0123] 利用AGPS获取主移动终端位置信息的原理是:主移动终端利用AGPS信息捕获卫星信号并接收测量信息,然后将测量信息发送给定位服务中心 ,它计算出移动终端的当前位置并将信息发送到服务器。 [0124] 脚步 11 , 服务器接收到移动终端X的数据下载请求后,通过CELL ID或AGPS定位移动终端X。 [0125] 脚步 12 , 根据信息(即文件名、类型、 和下载数据的大小)以及通过定位获得的位置信息。 这里假设,在确定的共享下载组Y中,移动终端A为主移动终端,移动终端B、C、...。 . . , 和 N 是从属移动终端。 [0126] 脚步 13 ,服务器向共享下载组Y中的主移动终端A发送通知,通知移动终端X要加入共享下载组。 [0127] 脚步 14 ,主移动终端A邀请移动终端X加入共享下载组Y [0128] 脚步 15,移动终端X接受邀请并对主移动终端A进行鉴权,鉴权成功则移动终端X加入共享下载组Y并执行步骤S 16 ; 若鉴权失败,则移动终端X无法加入分享下载组,流程结束。 [0129] 移动终端X可以通过多种认证方式对主移动终端A进行认证。 例如,在步骤S 11 ,移动终端X在向服务器发送数据下载请求时,生成一个随机数并将该随机数发送给服务器。 在步骤S 13 ,服务器将通知连同随机数发送给主移动终端A。主移动终端A在邀请移动终端X加入分享下载组时将该随机数发送给移动终端X。 移动终端X收到随机数后,与本地存储的随机数进行比较; 如果两个随机数相同,则移动终端X认为主移动终端认证成功。 否则认为认证失败。 [0130] 小号 16 ,主移动终端A向组内的从移动终端发送查询消息,查询各从移动终端当前的下载进度,然后根据各从移动终端的下载情况确定剩余待下载数据的大小 从移动终端。 [0131] 脚步 17 ,主移动终端A根据步骤S确定的剩余数据大小,重新分配下载任务给共享下载组中的所有移动终端,包括移动终端X 16 ; [0132] 主移动终端A可以采用平均分配算法对下载任务进行重新分配,即将下载任务分成若干(例如M,这里假设N< Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AT467191T(String), DE602006014067D1(String), DE602006014067T2(String), EP1752886A1(String), EP1752886B1(String), US20070037563A1(String), US7941123B2(String), WO2007019770A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AT467191T(String), DE602006014067D1(String), DE602006014067T2(String), EP1752886A1(String), EP1752886B1(String), US20070037563A1(String), US7941123B2(String), WO2007019770A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7941123B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AT467191T(String), DE602006014067D1(String), DE602006014067T2(String), EP1752886A1(String), EP1752886B1(String), US20070037563A1(String), US7941123B2(String), WO2007019770A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), AT467191T(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), DE602006014067D1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), DE602006014067T2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), EP1752886A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), EP1752886B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), US20070037563A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), US7941123B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270648(Integer), WO2007019770A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7941123B2(String), US7941123B2(String), 1304956800(Integer), 270648(Integer), 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184965(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184965(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184965(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184965(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9906723B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for selection between front-facing camera and rear-facing camera of mobile terminal and mobile terminal(String), 移动终端前置摄像头和后置摄像头选择方法及移动终端(String), US9906723B2(String), A method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which are used to implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal is presented. The method in the embodiments of the present disclosure includes receiving, by a mobile terminal, a photographing request initiated by a user; determining, by the mobile terminal, a distance between the mobile terminal and the user; and if the distance is greater than or equal to a preset numeric value, turning on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turning on a rear-facing camera of the mobile terminal. The embodiments of the present disclosure can implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal.(String), 提出了一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,用于实现移动终端前置摄像头和后置摄像头的自动选择。 . 本发明实施例的方法包括:移动终端接收用户发起的拍照请求; 移动终端确定移动终端与用户的距离; 若距离大于或等于预设数值,则开启移动终端的前置摄像头。 或者如果距离小于预设数值,则开启移动终端的后置摄像头。 本发明实施例可以实现移动终端前置摄像头和后置摄像头的自动选择。(String), US15/220564(String), 1469548800(Integer), US9906723B2(String), 1519660800(Integer), 1519660800(Integer), 美国(String), 4(Integer), CN(String), 8(Integer), 35(Integer), CN101299847A | CN101299847B | CN101521696A | CN102629979A | CN102685306A | CN103037083A | CN103227869A | CN103391366A | CN103516900A | CN103795864A | EP2661068A2 | JP2003298884A | JP2005217768A | JP2007032117A | JP2007312039A | JP2009132664A | JP2012522415A | JP2013526099A | JP2013536240A | KR1020090007166A | KR1020110056094A | US20070019000A1 | US20090017867A1 | US20100245287A1 | US20110216209A1 | US20120081592A1 | US20130002722A1 | US20140118600A1 | US20140139667A1 | US20160373646A1 | US6864912B1 | US8451312B2(String), 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184966(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b94956f3f2254c54a4ee2098b1c2e154.png(String), 184966(Integer), b94956f3f2254c54a4ee2098b1c2e154.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for selection between front-facing camera and rear-facing camera of mobile terminal and mobile terminal(String), 移动终端前置摄像头和后置摄像头选择方法及移动终端(String), US9906723B2(String), A method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which are used to implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal is presented. The method in the embodiments of the present disclosure includes receiving, by a mobile terminal, a photographing request initiated by a user; determining, by the mobile terminal, a distance between the mobile terminal and the user; and if the distance is greater than or equal to a preset numeric value, turning on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turning on a rear-facing camera of the mobile terminal. The embodiments of the present disclosure can implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal.(String), 提出了一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,用于实现移动终端前置摄像头和后置摄像头的自动选择。 . 本发明实施例的方法包括:移动终端接收用户发起的拍照请求; 移动终端确定移动终端与用户的距离; 若距离大于或等于预设数值,则开启移动终端的前置摄像头。 或者如果距离小于预设数值,则开启移动终端的后置摄像头。 本发明实施例可以实现移动终端前置摄像头和后置摄像头的自动选择。(String), US15/220564(String), 1469548800(Integer), US9906723B2(String), 1519660800(Integer), 1519660800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 8(Integer), 35(Integer), CN101299847A | CN101299847B | CN101521696A | CN102629979A | CN102685306A | CN103037083A | CN103227869A | CN103391366A | CN103516900A | CN103795864A | EP2661068A2 | JP2003298884A | JP2005217768A | JP2007032117A | JP2007312039A | JP2009132664A | JP2012522415A | JP2013526099A | JP2013536240A | KR1020090007166A | KR1020110056094A | US20070019000A1 | US20090017867A1 | US20100245287A1 | US20110216209A1 | US20120081592A1 | US20130002722A1 | US20140118600A1 | US20140139667A1 | US20160373646A1 | US6864912B1 | US8451312B2(String), \20230420\b94956f3f2254c54a4ee2098b1c2e154.png(String), 22(Integer), 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 1. A method for selection between a front-facing camera and a rear-facing camera of a mobile terminal, comprising:receiving, by the mobile terminal, a photographing request initiated by a user;determining, by the mobile terminal, a distance between the mobile terminal and the user; andturning on the front-facing camera of the mobile terminal when the distance is greater than or equal to a preset numeric value; andturning on the rear-facing camera of the mobile terminal when the distance is less than the preset numeric value.(String), 1.根据权利要求1所述的方法,其中在开启移动终端的前置摄像头之前或开启移动终端的后置摄像头之前,该方法还包括:向用户发送查询请求,查询请求用于询问用户是否同意开启前置摄像头或后置摄像头;获取用户的回复;当回复为同意开启前置摄像头或后置摄像头或在一段时间内没有收到回复时,触发开启移动终端的前置摄像头或移动终端的后置摄像头预设时间段;和当回复拒绝开启前置摄像头或后置摄像头时,触发移动终端的默认动作。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 2. The method according to claim 1, wherein the determining, by the mobile terminal, a distance between the mobile terminal and the user comprises determining, by the mobile terminal, a distance between the mobile terminal and a face of the user.(String), 12.移动终端,包括:一个前置摄像头和一个后置摄像头;接收器,用于接收用户发起的拍照请求;和处理器配置为:确定移动终端与用户之间的距离;当距离大于或等于预设数值时,开启移动终端的前置摄像头;和当距离小于预设数值时,开启移动终端的后置摄像头。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 3. The method according to claim 2, wherein determining, by the mobile terminal, the distance between the mobile terminal and the face of the user comprises:determining, by the mobile terminal, a distance between the mobile terminal and a preset position on the face of the user; ordetermining, by the mobile terminal, an overall distance between the mobile terminal and at least two preset positions on the face of the user.(String), 13.根据权利要求12所述的移动终端,其中处理器还用于确定移动终端与用户面部之间的距离。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 4. The method according to claim 1, wherein the preset numeric value is set by the mobile terminal by default.(String), 14.根据权利要求13所述的移动终端,其中处理器还被配置为:确定移动终端与用户面部预设位置之间的距离;和确定移动终端与用户面部至少两个预设位置之间的总体距离。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 5. The method according to claim 4, wherein the photographing request comprises at least a first application request and a second application request; wherein the preset numeric value is a first preset numeric value when the photographing request is the first application request; wherein the preset numeric value is a second preset numeric value when the photographing request is the second application request, and wherein the first preset numeric value is different from the second preset numeric value.(String), 15.根据权利要求12所述的移动终端,其中该预设数值由移动终端默认设置。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 6. The method according to claim 5, further comprising:acquiring a first probability and a second probability, wherein the first probability is a probability of using the front-facing camera in a first application state, and wherein the second probability is a probability of using the front-facing camera in a second application state; andseparately adjusting the first preset numeric value and the second preset numeric value according to the first probability and the second probability, such that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value.(String), 16.根据权利要求15所述的移动终端,其中拍摄请求至少包括第一应用请求和第二应用请求,其中,当拍摄请求为第一应用请求时,预设数值为第一预设数值,当拍摄请求为第一应用请求时,预设数值为第二预设数值。拍照请求为第二应用请求,其中第一预设数值与第二预设数值不同。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 7. The method according to claim 4, further comprising:acquiring, by the mobile terminal, usage information about the user's usage of the front-facing camera and the rear-facing camera; andadjusting the preset numeric value according to the usage information.(String), 17.根据权利要求16所述的移动终端,其中处理器还被配置为:获取第一概率和第二概率,其中第一概率为用户在第一应用状态下使用前置摄像头的概率,第二概率为用户使用前置摄像头的概率处于第二应用状态;和根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。(String), 1(Integer), 6(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 8. The method according to claim 4, further comprising:acquiring, by the mobile terminal, personal information of the user; andadjusting the preset numeric value according to the personal information.(String), 18.根据权利要求15所述的移动终端,其中处理器还被配置为:获取用户使用前置摄像头和后置摄像头的使用信息;和根据使用信息调整预设数值。(String), 1(Integer), 7(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 9. The method according to claim 4, further comprising:acquiring, by the mobile terminal, a factor of an environment in which the mobile terminal is currently located; andadjusting the preset numeric value according to the factor of the environment in which the user is currently located.(String), 19.根据权利要求15所述的移动终端,其中处理器还被配置为:获取用户的个人信息;和根据个人信息调整预设数值。(String), 1(Integer), 8(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 10. The method according to claim 1, further comprising acquiring the preset numeric value from the user prior to determining the distance between the mobile terminal and the user.(String), 20.根据权利要求15所述的移动终端,其中处理器还被配置为:获取用户当前所处环境的因素;和根据用户当前所处环境因素调整预设数值。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 11. The method according to claim 1, wherein before the turning on the front-facing camera of the mobile terminal or before the turning on the rear-facing camera of the mobile terminal, the method further comprises:sending an inquiry request to the user, wherein the inquiry request is used to ask the user whether to agree to turn on the front-facing camera or the rear-facing camera;acquiring a reply from the user;triggering the turning on of the front-facing camera of the mobile terminal or the rear-facing camera of the mobile terminal when the reply is agreeing to turn on the front-facing camera or the rear-facing camera or no reply is received within a preset time period; andtriggering a default action of the mobile terminal when the reply is refusing to turn on the front-facing camera or the rear-facing camera.(String), 21.根据权利要求12所述的移动终端,其中处理器还用于在确定移动终端与用户之间的距离之前,获取用户的预设数值。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 12. A mobile terminal, comprising:a front-facing camera and a rear-facing camera;a receiver configured to receive a photographing request initiated by a user; anda processor configured to:determine a distance between the mobile terminal and the user;turn on the front-facing camera of the mobile terminal when the distance is greater than or equal to a preset numeric value; andturn on the rear-facing camera of the mobile terminal when the distance is less than the preset numeric value.(String), 22.根据权利要求12所述的移动终端,其中处理器还被配置为:向用户发送查询请求,查询请求用于询问用户是否同意开启前置摄像头或后置摄像头;获取用户的回复;当回复为同意开启前置摄像头或后置摄像头时,触发开启移动终端前置摄像头或开启移动终端后置摄像头;和当回复拒绝开启前置摄像头或后置摄像头时,触发移动终端的默认动作。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 13. The mobile terminal according to claim 12, wherein the processor is further configured to determine a distance between the mobile terminal and a face of the user.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 14. The mobile terminal according to claim 13, wherein the processor is further configured to:determine a distance between the mobile terminal and a preset position on the face of the user; anddetermine an overall distance between the mobile terminal and at least two preset positions on the face of the user.(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 15. The mobile terminal according to claim 12, wherein the preset numeric value is set by the mobile terminal by default.(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 16. The mobile terminal according to claim 15, wherein the photographing request comprises at least a first application request and a second application request, wherein the preset numeric value is a first preset numeric value when the photographing request is the first application request, wherein the preset numeric value is a second preset numeric value when the photographing request is the second application request, and wherein the first preset numeric value is different from the second preset numeric value.(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 17. The mobile terminal according to claim 16, wherein the processor is further configured to:acquire a first probability and a second probability, wherein the first probability is a probability of using the front-facing camera by the user in a first application state, and wherein the second probability is a probability of using the front-facing camera by the user in a second application state; andseparately adjust the first preset numeric value and the second preset numeric value according to the first probability and the second probability, such that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value.(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 18. The mobile terminal according to claim 15, wherein the processor is further configured to:acquire usage information about the user's usage of the front-facing camera and the rear-facing camera; andadjust the preset numeric value according to the usage information.(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 19. The mobile terminal according to claim 15, wherein the processor is further configured to:acquire personal information of the user; andadjust the preset numeric value according to the personal information.(String), 1(Integer), 18(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 20. The mobile terminal according to claim 15, wherein the processor is further configured to:acquire a factor of an environment in which the user is currently located; andadjust the preset numeric value according to the factor of the environment in which the user is currently located.(String), 1(Integer), 19(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 21. The mobile terminal according to claim 12, wherein the processor is further configured to acquire the preset numeric value from the user prior to determining the distance between the mobile terminal and the user.(String), 1(Integer), 20(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:39.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184966(Integer), 22. The mobile terminal according to claim 12, wherein the processor is further configured to:send an inquiry request to the user, wherein the inquiry request is used to ask the user whether to agree to turn on the front-facing camera or the rear-facing camera;acquire a reply from the user;trigger turning on the front-facing camera of the mobile terminal or turning on the rear-facing camera of the mobile terminal when the reply is agreeing to turn on the front-facing camera or the rear-facing camera; andtrigger a default action of the mobile terminal when the reply is refusing to turn on the front-facing camera or the rear-facing camera.(String), 1(Integer), 21(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.172 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184966(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a continuation of International Application No. PCT/CN2014/081100, filed on Jun. 30, 2014, which claims priority to Chinese Patent Application No. 201410043609.7, filed on Jan. 29, 2014, both of which are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of mobile communications, and in particular, to a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal. BACKGROUND [0003]Front-facing and rear-facing cameras are generally configured on existing mobile terminals (especially, mobile phones), where the rear-facing camera has many functions and is used mostly for photographing scenery and other people, while the front-facing camera is usually used only for self-photographing and video calling. [0004]When a user turns on a camera, an existing terminal generally turns on the rear-facing camera by default. When the user needs to switch to the front-facing camera, the user usually taps an independent button on a screen to implement a switch between the front-facing camera and the rear-facing camera. [0005]However, this manner requires the user to perform manual switching, and is rather complex. SUMMARY [0006]Embodiments of the present disclosure provide a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which can implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal. [0007]A first aspect of the embodiments of the present disclosure provides a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal, including receiving, by a mobile terminal, a photographing request initiated by a user; determining, by the mobile terminal, a distance between the mobile terminal and the user; and if the distance is greater than or equal to a preset numeric value, turning on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turning on a rear-facing camera of the mobile terminal. [0008]With reference to the first aspect of the embodiments of the present disclosure, in a first implementation manner of the first aspect of the embodiments of the present disclosure, the determining, by the mobile terminal, a distance between the mobile terminal and the user includes determining, by the mobile terminal, a distance between the mobile terminal and a face of the user. [0009]With reference to the first implementation manner of the first aspect of the embodiments of the present disclosure, in a second implementation manner of the first aspect of the embodiments of the present disclosure, the determining, by the mobile terminal, a distance between the mobile terminal and a face of the user includes determining, by the mobile terminal, a distance between the mobile terminal and a preset position on the face of the user; or determining, by the mobile terminal, an overall distance between the mobile terminal and at least two preset positions on the face of the user. [0010]With reference to the first aspect of the embodiments of the present disclosure, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a third implementation manner of the first aspect of the embodiments of the present disclosure, the preset numeric value is set by the mobile terminal by default. [0011]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in a fourth implementation manner of the first aspect of the embodiments of the present disclosure, the photographing request includes at least a first application request and a second application request; when the photographing request is the first application request, the preset numeric value is a first preset numeric value; when the photographing request is the second application request, the preset numeric value is a second preset numeric value; and the first preset numeric value is different from the second preset numeric value. [0012]With reference to the fourth implementation manner of the first aspect of the embodiments of the present disclosure, in a fifth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring a first probability and a second probability, where the first probability is a probability of using the front-facing camera in a first application state, and the second probability is a probability of using the front-facing camera in a second application state; and separately adjusting the first preset numeric value and the second preset numeric value according to the first probability and the second probability, so that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value. [0013]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in a sixth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring, by the mobile terminal, information about the user's usage of the front-facing camera and the rear-facing camera, and adjusting the preset numeric value according to the usage information. [0014]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in a seventh implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring, by the mobile terminal, personal information of the user, and adjusting the preset numeric value according to the personal information. [0015]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in an eighth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring, by the mobile terminal, a factor of an environment in which the user is currently located, and adjusting the preset numeric value according to the factor of the environment in which the user is currently located. [0016]With reference to the first aspect of the embodiments of the present disclosure, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a ninth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring the preset numeric value entered by the user. [0017]With reference to the first aspect of the embodiments of the present disclosure, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a tenth implementation manner of the first aspect of the embodiments of the present disclosure, before the turning on a front-facing camera of the mobile terminal or before the turning on a rear-facing camera of the mobile terminal, the method further includes sending an inquiry request to the user, where the inquiry request is used to ask the user whether to agree to turn on the camera; acquiring a reply from the user; and when the reply is agreeing to turn on the camera or no reply is received within a preset time period, triggering the turning on of the front-facing camera of the mobile terminal or the rear-facing camera of the mobile terminal; or when the reply is refusing to turn on the camera, triggering a default action of the mobile terminal. [0018]A second aspect of the embodiments of the present disclosure provides a mobile terminal, including a front-facing camera and a rear-facing camera; a receiving module configured to receive a photographing request initiated by a user; a determining module configured to determine a distance between the mobile terminal and the user; and a control module configured to, when the distance is greater than or equal to a preset numeric value, turn on the front-facing camera of the mobile terminal; or when the distance is less than the preset numeric value, turn on the rear-facing camera of the mobile terminal. [0019]With reference to the second aspect of the embodiments of the present disclosure, in a first implementation manner of the second aspect of the embodiments of the present disclosure, the determining module is configured to determine a distance between the mobile terminal and a face of the user. [0020]With reference to the first implementation manner of the second aspect of the embodiments of the present disclosure, in a second implementation manner of the second aspect of the embodiments of the present disclosure, the determining module is configured to determine a distance between the mobile terminal and a preset position on the face of the user; or the determining module is configured to determine an overall distance between the mobile terminal and at least two preset positions on the face of the user. [0021]With reference to the second aspect, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in a third implementation manner of the second aspect of the embodiments of the present disclosure, the preset numeric value is set by the mobile terminal by default. [0022]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in a fourth implementation manner of the second aspect of the embodiments of the present disclosure, the photographing request includes at least a first application request and a second application request; when the photographing request is the first application request, the preset numeric value is a first preset numeric value; when the photographing request is the second application request, the preset numeric value is a second preset numeric value; and the first preset numeric value is different from the second preset numeric value. [0023]With reference to the fourth implementation manner of the second aspect of the embodiments of the present disclosure, in a fifth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a first acquiring module configured to acquire a first probability and a second probability, where the first probability is a probability of using the front-facing camera by the user in a first application state, and the second probability is a probability of using the front-facing camera by the user in a second application state; and a first adjusting module configured to separately adjust the first preset numeric value and the second preset numeric value according to the first probability and the second probability, so that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value. [0024]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in a sixth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a second acquiring module configured to acquire information about the user's usage of the front-facing camera and the rear-facing camera; and a second adjusting module configured to adjust the preset numeric value according to the usage information. [0025]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in a seventh implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a third acquiring module configured to acquire personal information of the user, and adjust the preset numeric value according to the personal information; and a third adjusting module configured to adjust the preset numeric value according to the personal information. [0026]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in an eighth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a fourth acquiring module configured to acquire a factor of an environment in which the user is currently located; and a fourth adjusting module configured to adjust the preset numeric value according to the factor of the environment in which the user is currently located. [0027]With reference to the second aspect of the embodiments of the present disclosure, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in a ninth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a fifth acquiring module configured to acquire the preset numeric value entered by the user. [0028]With reference to the second aspect of the embodiments of the present disclosure, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in a tenth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes an inquiry module configured to send an inquiry request to the user, where the inquiry request is used to ask the user whether to agree to turn on the camera; a sixth acquiring module configured to acquire a reply from the user; a first triggering unit configured to, when the reply is agreeing to turn on the camera, trigger the control module to turn on the front-facing camera of the mobile terminal or turn on the rear-facing camera of the mobile terminal; and a second triggering unit configured to, when the reply is refusing to turn on the camera, trigger a default action of the mobile terminal. [0029]It can be seen from the foregoing technical solutions that the embodiments of the present disclosure have the following advantages. [0030]In the embodiments of the present disclosure, it is determined whether a distance between a mobile terminal and a user is greater than a preset numeric value, so as to automatically determine whether to turn on a front-facing camera of the mobile terminal or turn on a rear-facing camera of the mobile terminal, thereby implementing automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal, avoiding a case in which the user needs to perform manual selection, and improving user experience for the mobile terminal. BRIEF DESCRIPTION OF DRAWINGS [0031]FIG. 1 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure; [0032]FIG. 2 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0033]FIG. 3 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0034]FIG. 4 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0035]FIG. 5 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0036]FIG. 6 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0037]FIG. 7 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0038]FIG. 8 is a schematic diagram of a mobile terminal according to an embodiment of the present disclosure; [0039]FIG. 9 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0040]FIG. 10 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0041]FIG. 11 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0042]FIG. 12 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0043]FIG. 13 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0044]FIG. 14 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0045]FIG. 15 is a schematic diagram of a mobile phone according to an embodiment of the present disclosure; and [0046]FIG. 16 is a structural diagram of an inner part of a mobile phone according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0047]Embodiments of the present disclosure provide a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which are used to implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal. [0048]To make persons skilled in the art understand the technical solutions in the present disclosure better, the following clearly and completely describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Thespe described embodiments are merely a part rather than all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]In the specification, claims, and accompanying drawings of the present disclosure, the terms “first”, “second”, “third”, “fourth”, and so on (if existent) are intended to distinguish between similar objects but do not necessarily indicate a specific order or sequence. It should be understood that the data termed in such a way are interchangeable in proper circumstances so that the embodiments of the present disclosure described herein can be implemented in other orders than the order illustrated or described herein. Moreover, the terms “include”, “contain” and any other variants mean to cover the non-exclusive inclusion, for example, a process, method, system, product, or device that includes a list of steps or units is not necessarily limited to those units, but may include other units not expressly listed or inherent to such a process, method, system, product, or device. [0050]Referring to FIG. 1, an embodiment of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure includes the following steps. [0051]Step 101. A mobile terminal receives a photographing request initiated by a user. [0052]The mobile terminal may be a mobile phone, a tablet computer, or another mobile terminal having a camera, where a front-facing camera and a rear-facing camera are disposed on the mobile terminal, the front-facing camera refers to a camera that is located at a same side as a display screen of the mobile terminal, and the rear-facing camera refers to a camera that is located at the other side of the mobile terminal opposite to the display screen of the mobile terminal. When a user needs to take a picture, the user may trigger a photographing function of the mobile terminal. The mobile terminal receives a photographing request initiated by the user, and prepares to turn on a camera to enter a photographing state. [0053]Step 102. The mobile terminal determines a distance between the mobile terminal and the user. [0054]A distance measurement module that can measure a distance between the mobile terminal and the user is disposed in the mobile terminal, where the distance measurement module may be an independently disposed distance sensor or proximity sensor, or may be a distance sensor that is configured in the camera of the mobile terminal to implement an automatic focus function. Certainly, in an actual application, the distance measurement module may be another sensor or module that can implement the same function. [0055]It should be noted that, there are two cases herein. In a first case, the camera of the mobile terminal is off when the user initiates the photographing request to the mobile terminal. The mobile terminal determines a distance between the mobile terminal and the user when the user initiates the photographing request to the mobile terminal, so as to determine, according to the distance, whether to turn on the front-facing camera or turn on the rear-facing camera. The mobile terminal may first turn on a default camera after receiving the photographing request initiated by the user, and then determine, according to the distance, whether to switch to or additionally turn on the front-facing camera or the rear-facing camera, or directly determine, according to the distance, whether to turn on the front-facing camera or the rear-facing camera, which is not limited herein. [0056]In the first case, the distance measurement module may detect the distance between the mobile terminal and the user all the time, and when receiving the photographing request initiated by the user, the mobile terminal determines a current distance according to the distance measurement module thereof; or the distance measurement module detects the distance between the mobile terminal and the user only when the screen is on, and when receiving the photographing request initiated by the user, the mobile terminal determines a current distance according to the distance measurement module thereof; or the distance measurement module may detect a current distance between the mobile terminal and the user only when the mobile terminal receives the photographing request initiated by the user, and the mobile terminal determines, according to the distance measurement module thereof, the distance measured by the distance measurement module. [0057]In a second case, when receiving the photographing request initiated by the user, the mobile terminal is currently in a photographing state. In the whole photographing process of the mobile terminal, the distance measurement module detects the distance between the mobile terminal and the user in real time; the mobile terminal determines a current distance according to the distance measurement module thereof, and determines, according to the distance, whether to switch from a currently used camera to the other camera or whether the other camera needs to be simultaneously turned on. [0058]It should be noted that, in the foregoing description, the distance, between the mobile terminal and the user, measured by the distance measurement module may be an instantaneous value that is currently measured between the mobile terminal and the user, or may be an average value or a sample value of distances between the mobile terminal and the user within preset duration. Certainly, the foregoing description is merely an example, and is not limited herein. [0059]Step 103. If the distance is greater than or equal to a preset numeric value, turn on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turn on a rear-facing camera of the mobile terminal. [0060]After determining the distance between the mobile terminal and the user, the mobile terminal determines whether the distance is greater than or less than the preset numeric value. If the distance is greater than or equal to the preset numeric value, the front-facing camera is turned on; or the distance is less than the preset numeric value, the rear-facing camera is turned on. In the foregoing first case, after receiving the photographing request initiated by the user, the mobile terminal may directly select, according to the distance, to turn on a corresponding camera; or the mobile terminal may first turn on a default camera, and if a camera corresponding to the distance is different from the default camera, switch from the default camera to the camera corresponding to the distance, or additionally turn on the camera corresponding to the distance, that is, simultaneously turn on the front-facing camera and the rear-facing camera. [0061]In the foregoing second case, if the camera corresponding to the distance is different from a currently used camera, the mobile terminal switches from the currently used camera to the camera corresponding to the distance, or the mobile terminal additionally turns on the camera corresponding to the distance, that is, simultaneously turns on the front-facing camera and the rear-facing camera. [0062]In this embodiment, it is determined whether a distance between a mobile terminal and a user is greater than a preset numeric value, so as to automatically determine whether to turn on a front-facing camera of the mobile terminal or turn on a rear-facing camera of the mobile terminal, thereby implementing automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal, avoiding a case in which the user needs to perform manual selection, and improving user experience for the mobile terminal. [0063]In the foregoing embodiment, a distance between a mobile terminal and a user is determined, so as to determine whether to turn on a front-facing camera or a rear-facing camera. In an actual application, the distance may be a distance between the mobile terminal and a face of the user, and the following describes a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure. Referring to FIG. 2, another embodiment of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure includes the following steps. [0064]Step 201. A mobile terminal receives a photographing request initiated by a user. [0065]The mobile terminal may be a mobile phone, a tablet computer, or another mobile terminal having a camera, where a front-facing camera and a rear-facing camera are disposed on the mobile terminal, the front-facing camera refers to a camera that is located at a same side as a display screen of the mobile terminal, and the rear-facing camera refers to a camera that is located at the other side of the mobile terminal opposite to the display screen of the mobile terminal. When a user needs to take a picture, the user may trigger a photographing function of the mobile terminal. The mobile terminal receives a photographing request initiated by the user, and prepares to turn on a camera to enter a photographing state. [0066]Step 202. The mobile terminal determines a distance between the mobile terminal and a face of the user. [0067]When the distance measurement module in the mobile terminal measures the distance between the mobile terminal and the user, the distance measurement module may measure the distance between the mobile terminal and the face of the user. During measurement of the distance, the distance may be a distance between the mobile terminal and a specific preset position on the face of the user, for example, the distance is a distance between the mobile terminal and a central point between the two eyes of the user, or a distance between the mobile terminal and the nose of the user; or the distance may be an overall distance between the mobile terminal and at least two preset positions on the face of the user, for example, the distance is equal to an average value of distances between the mobile terminal and the two eyes of the user, or an average value of distances between the mobile terminal and the five sense organs of the user. Certainly, the foregoing description is merely an example, and is not limited herein. [0068]Certainly, in an actual application, the mobile terminal may not determine the distance between the mobile terminal and the face of the user, but determine a distance between the mobile terminal and another portion of the user, which is not limited herein. Preferably, the mobile terminal may receive a setting by the user for a specific definition of the distance. [0069]In an actual application, the determining a distance between the mobile terminal and a face of the user may be determining a distance between a camera of the mobile terminal and the face of the user, or determining a distance between another position on the mobile terminal and the face of the user, or determining an overall distance between at least two positions on the mobile terminal and the face of the user, which is not limited herein. [0070]Step 203. If the distance is greater than or equal to a preset numeric value, turn on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turn on a rear-facing camera of the mobile terminal. [0071]After determining the distance between the mobile terminal and the user, the mobile terminal determines whether the distance is greater than or less than the preset numeric value. If the distance is greater than or equal to the preset numeric value, the front-facing camera is turned on; or the distance is less than the preset numeric value, the rear-facing camera is turned on. In the foregoing first case, after receiving the photographing request initiated by the user, the mobile terminal may directly select, according to the distance, to turn on a corresponding camera; or the mobile terminal may first turn on a default camera, and if a camera corresponding to the distance is different from the default camera, switch from the default camera to the camera corresponding to the distance, or additionally turn on the camera corresponding to the distance, that is, simultaneously turn on the front-facing camera and the rear-facing camera. [0072]In the foregoing second case, if the camera corresponding to the distance is different from a currently used camera, the mobile terminal switches from the currently used camera to the camera corresponding to the distance, or the mobile terminal additionally turns on the camera corresponding to the distance, that is, simultaneously turns on the front-facing camera and the rear-facing camera. [0073]In this embodiment, the determining of the distance between the mobile terminal and the face of the user conforms better to a self-photographing behavior often performed by the user using the mobile terminal in an actual application, so that the mobile terminal more accurately determines, according to the distance, whether to turn on the front-facing camera or the rear-facing camera, so as to better meet an actual requirement of the user. [0074]In the foregoing embodiment, if the determined distance is greater than or equal to the preset numeric value, the front-facing camera is turned on; otherwise, the rear-facing camera is turned on. In an actual application, the preset numeric value may be set by the mobile terminal by default, and the following describes a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure. Referring to FIG. 3, another embodiment of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure includes the following steps. [0075]Step 301. A mobile terminal receives a photographing request initiated by a user. [0076]The mobile terminal may be a mobile phone, a tablet computer, or another mobile terminal having a camera, where a front-facing camera and a rear-facing camera are disposed on the mobile terminal, the front-facing camera refers to a camera that is located at a same side as a display screen of the mobile terminal, and the rear-facing camera refers to a camera that is located at the other side of the mobile terminal opposite to the display screen of the mobile terminal. When a user needs to take a picture, the user may trigger a photographing function of the mobile terminal. The mobile terminal receives a photographing request initiated by the user, and pre(String), 相关申请的交叉引用 [0001] 本申请是2014年6月30日提交的国际申请PCT/CN2014/081100的继续申请,该申请要求2014年1月29日提交的中国专利申请201410043609.7的优先权,在此将其并入 全文参考。 技术领域 [0002] 本发明涉及移动通信领域,尤其涉及一种移动终端前置摄像头和后置摄像头的选择方法及移动终端。 背景 [0003] 前置和后置摄像头一般配置在现有的移动终端(尤其是手机)上,后置摄像头功能很多,主要用于拍摄风景和其他人,而前置摄像头通常用于 仅用于自拍和视频通话。 [0004] 当用户开启摄像头时,现有终端一般默认开启后置摄像头。 当用户需要切换前置摄像头时,用户通常通过点击屏幕上的独立按钮来实现前置摄像头和后置摄像头的切换。 [0005] 但是这种方式需要用户手动切换,比较复杂。 概括 [0006] 本发明实施例提供一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,能够实现移动终端前置摄像头和后置摄像头的自动选择。 移动终端。 [0007] 本发明实施例的第一方面提供了一种移动终端前置摄像头和后置摄像头的选择方法,包括:移动终端接收用户发起的拍照请求; 移动终端确定移动终端与用户的距离; 若距离大于或等于预设数值,则开启移动终端的前置摄像头。 或者如果距离小于预设数值,则开启移动终端的后置摄像头。 [0008] 结合本发明实施例第一方面,在本发明实施例第一方面的第一种实施方式中,所述移动终端确定所述移动终端与所述用户的距离包括: ,通过移动终端,移动终端与用户的面部之间的距离。 [0009] 结合本发明实施例第一方面的第一种实施方式,在本发明实施例第一方面的第二种实施方式中,所述移动终端确定所述移动终端之间的距离 所述用户面部包括:所述移动终端确定所述移动终端与所述用户面部预设位置的距离; 或者,移动终端确定移动终端与用户面部的至少两个预设位置的总距离。 [0010] 结合本发明实施例的第一方面,或第一方面的第一实施方式,或第一方面的第二实施方式,在本发明实施例第一方面的第三实施方式中 ,预设数值由移动端默认设置。 [0011] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第四种实施方式中,所述拍照请求至少包括第一应用请求和第二应用 要求; 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值。 第一预设数值与第二预设数值不同。 [0012]结合本发明实施例第一方面的第四种实施方式,在本发明实施例第一方面的第五种实施方式中,所述方法还包括获取第一概率和第二概率,其中 第一概率为在第一应用状态下使用前置摄像头的概率,第二概率为在第二应用状态下使用前置摄像头的概率。 根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。 [0013] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第六种实施方式中,所述方法还包括:所述移动终端获取所述移动终端的信息。 用户对前置摄像头和后置摄像头的使用情况,并根据使用信息调整预设数值。 [0014] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第七种实施方式中,所述方法还包括:所述移动终端获取用户的个人信息。 用户,并根据个人信息调整预设数值。 [0015] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第八种实施方式中,所述方法还包括:所述移动终端获取因子: 用户当前所处环境,根据用户当前所处环境因素调整预设数值。 [0016] 结合本发明实施例的第一方面,或第一方面的第一实施方式,或第一方面的第二实施方式,在本发明实施例第一方面的第九种实施方式中 ,该方法还包括获取用户输入的预设数值。 [0017] 结合本发明实施例的第一方面,或者第一方面的第一实施方式,或者第一方面的第二实施方式,在本发明实施例第一方面的第十实施方式中 ,在开启移动终端前置摄像头之前或开启移动终端后置摄像头之前,该方法还包括向用户发送查询请求,该查询请求用于向用户询问 用户是否同意开启摄像头; 获取用户的回复; 当回复为同意开启摄像头或在预设时间内未收到回复时,触发开启移动终端前置摄像头或移动终端后置摄像头。 或者当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0018] 本发明实施例的第二方面提供了一种移动终端,包括前置摄像头和后置摄像头。 接收模块,用于接收用户发起的拍摄请求; 确定模块,用于确定移动终端与用户之间的距离; 控制模块,用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0019]结合本发明实施例的第二方面,在本发明实施例的第二方面的第一种实施方式中,所述确定模块,用于确定所述移动终端与所述用户的面部的距离。 . [0020] 结合本发明实施例第二方面的第一种实施方式,在本发明实施例第二方面的第二种实施方式中,所述确定模块,用于确定所述移动终端与所述移动终端之间的距离。 用户脸上的预设位置; 或者,所述确定模块,用于确定所述移动终端与所述用户面部的至少两个预设位置之间的总距离。 [0021] 结合第二方面,或第二方面的第一种实施方式,或第二方面的第二种实施方式,在本发明实施例的第二方面的第三种实施方式中,设置预设数值 手机端默认。 [0022] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第四种实施方式中,所述拍照请求至少包括第一应用请求和第二应用 要求; 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值。 第一预设数值与第二预设数值不同。 [0023] 结合本发明实施例第二方面的第四种实施方式,在本发明实施例第二方面的第五种实施方式中,所述移动终端还包括第一获取模块,用于获取第一 概率和第二概率,其中第一概率是用户在第一应用状态下使用前置摄像头的概率,第二概率是用户在第二应用状态下使用前置摄像头的概率 状态; 第一调整模块,用于根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应于第一预设数值,第二概率对应于第二 预设数值。 [0024] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第六种实施方式中,所述移动终端还包括第二获取模块,用于获取有关信息。 用户对前置摄像头和后置摄像头的使用情况; 第二调整模块,用于根据使用信息调整预设数值。 [0025] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第七种实施方式中,所述移动终端还包括第三获取模块,用于获取个人信息 用户,并根据个人信息调整预设数值; 第三调整模块,用于根据个人信息调整预设数值。 [0026] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第八种实施方式中,所述移动终端还包括第四获取模块,用于获取因子 用户当前所处的环境; 第四调整模块,用于根据用户当前所处环境的因素调整预设数值。 [0027]结合本发明实施例的第二方面,或第二方面的第一种实施方式,或第二方面的第二种实施方式,在本发明实施例第二方面的第九种实施方式中 进一步地,所述移动终端还包括第五获取模块,用于获取用户输入的预设数值。 [0028] 结合本发明实施例的第二方面,或第二方面的第一种实施方式,或第二方面的第二实施方式,在本发明实施例第二方面的第十种实施方式中 进一步地,所述移动终端还包括询问模块,用于向所述用户发送询问请求,所述询问请求用于询问所述用户是否同意开启摄像头。 第六获取模块,用于获取用户的回复; 第一触发单元,用于当回复为同意开启摄像头时,触发控制模块开启移动终端前置摄像头或开启移动终端后置摄像头; 第二触发单元,用于当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0029] 从上述技术方案可以看出,本发明实施例具有以下优点。 [0030] 本发明实施例通过判断移动终端与用户的距离是否大于预设数值,从而自动判断是否开启移动终端前置摄像头或开启 移动终端的后置摄像头,从而实现了移动终端前置摄像头和后置摄像头之间的自动选择,避免了用户需要手动选择的情况,提高了用户的使用体验。 移动终端。 附图说明 [0031] 图1为本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0032] 图2是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0033] 图3是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0034] 图4是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0035] 图5是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0036] 图6是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0037] 图7是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0038] 图8为本发明实施例提供的移动终端示意图; [0039] 图9为本发明另一实施例的移动终端的示意图; [0040] 图10是根据本发明另一实施例的移动终端的示意图; [0041] 图11是根据本发明另一实施例的移动终端的示意图; [0042] 图12为本发明另一实施例的移动终端的示意图; [0043] 图13是根据本发明另一实施例的移动终端的示意图; [0044]图14是根据本发明另一实施例的移动终端的示意图; [0045] 图15为本发明实施例提供的手机示意图; 和 [0046] 图16为本发明实施例提供的手机内部结构示意图。 具体实施方式 [0047] 本发明实施例提供一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,用于实现前置摄像头和后置摄像头的自动选择。 的移动终端。 [0048] 为使本领域技术人员更好地理解本发明的技术方案,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 以上所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 在本公开的说明书、权利要求书和附图中,术语“第一”、“第二”、“第三”、“第四”等(如果存在)旨在区分相似的对象,但不一定 表示特定的顺序或顺序。 应当理解,以这种方式命名的数据在适当的情况下是可以互换的,使得在此描述的本公开的实施例可以以除了在此图示或描述的顺序之外的其他顺序来实施。 此外,术语“包括”、“包含”和任何其他变体意味着涵盖非排他性包含,例如,包括步骤或单元列表的过程、方法、系统、产品或设备不一定受到限制 这些单元,但可能包括未明确列出的其他单元或此类过程、方法、系统、产品或设备所固有的单元。 [0050] 参见图1,根据本发明实施例的移动终端前置摄像头和后置摄像头的选择方法实施例包括以下步骤。 [0051] 步 101 . 移动终端接收用户发起的拍照请求。 [0052] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 [0053] 步 102 . 移动终端确定移动终端与用户之间的距离。 [0054] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0055]需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0056] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0057] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离; 移动终端根据其测距模块确定当前距离,并根据距离确定是从当前使用的摄像头切换到其他摄像头还是需要同时开启其他摄像头。 [0058] 需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0059] 步 103 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0060] 在确定移动终端与用户之间的距离后,移动终端判断该距离是否大于或小于预设数值。 如果距离大于等于预设数值,则开启前置摄像头; 或距离小于预设数值,开启后置摄像头。 在上述第一种情况下,移动终端在接收到用户发起的拍照请求后,可以直接根据距离选择开启对应的摄像头。 或者,移动终端可以先开启默认摄像头,如果距离对应的摄像头与默认摄像头不同,则从默认摄像头切换到距离对应的摄像头,或者额外开启距离对应的摄像头 ,即同时开启前置摄像头和后置摄像头。 [0061]上述第二种情况,如果距离对应的摄像头与当前使用的摄像头不同,则移动终端从当前使用的摄像头切换到距离对应的摄像头,或者移动终端额外开启距离对应的摄像头。 距离,即同时开启前置摄像头和后置摄像头。 [0062] 本实施例通过判断移动终端与用户的距离是否大于预设数值,从而自动判断是开启移动终端前置摄像头还是开启后置摄像头 移动终端的摄像头,从而实现了移动终端前置摄像头和后置摄像头的自动选择,避免了用户需要手动选择的情况,提高了移动终端的用户体验。 [0063] 在上述实施例中,通过确定移动终端与用户之间的距离,来确定是开启前置摄像头还是开启后置摄像头。 在实际应用中,该距离可以是移动终端与用户面部之间的距离,下面描述根据实施例的移动终端前置摄像头和后置摄像头的选择方法 本公开的内容。 参见图2,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0064] 步 201 . 移动终端接收用户发起的拍照请求。 [0065] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 [0066] 步 202 . 移动终端确定移动终端与用户面部之间的距离。 [0067] 当移动终端中的距离测量模块测量移动终端与用户之间的距离时,距离测量模块可以测量移动终端与用户面部之间的距离。 在测量距离时,该距离可以是移动终端到用户面部特定预设位置的距离,例如,距离是移动终端到用户两只眼睛中心点的距离。 用户,或者移动终端到用户鼻子的距离; 或者,该距离可以是移动终端到用户面部至少两个预设位置的总距离,例如,该距离等于移动终端到用户两只眼睛的距离的平均值, 或者移动终端与用户五种感觉器官的距离平均值。 当然,以上所述仅为举例,在此不做限定。 [0068] 当然,在实际应用中,移动终端可以不确定移动终端与用户面部的距离,而是确定移动终端与用户其他部分的距离,此处不做限定。 优选地,移动终端可以接收用户对距离的特定定义的设置。 [0069]在实际应用中,确定移动终端与用户面部的距离可以是确定移动终端的摄像头与用户面部的距离,也可以是确定移动终端上其他位置与用户面部的距离。 用户的面部,或者确定移动终端上至少两个位置与用户面部的总距离,在此不做限定。 [0070] 步 203 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0071] 在确定移动终端与用户之间的距离后,移动终端判断该距离是否大于或小于预设数值。 如果距离大于等于预设数值,则开启前置摄像头; 或距离小于预设数值,开启后置摄像头。 在上述第一种情况下,移动终端在接收到用户发起的拍照请求后,可以直接根据距离选择开启对应的摄像头。 或者,移动终端可以先开启默认摄像头,如果距离对应的摄像头与默认摄像头不同,则从默认摄像头切换到距离对应的摄像头,或者额外开启距离对应的摄像头 ,即同时开启前置摄像头和后置摄像头。 [0072] 上述第二种情况,如果距离对应的摄像头与当前使用的摄像头不同,则移动终端从当前使用的摄像头切换到距离对应的摄像头,或者移动终端额外开启距离对应的摄像头。 距离,即同时开启前置摄像头和后置摄像头。 [0073] 在本实施例中,移动终端与用户面部距离的确定更符合用户在实际应用中使用移动终端经常进行的自拍行为,从而使移动终端更准确地确定, 根据距离,开启前置摄像头或后置摄像头,以更好地满足用户的实际需求。 [0074] 在上述实施例中,如果确定的距离大于或等于预设数值,则开启前置摄像头; 否则,后置摄像头已打开。 在实际应用中,该预设数值可以由移动终端默认设置,下面对根据本发明实施例的移动终端前置摄像头和后置摄像头的选择方法进行说明 披露。 参见图3,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0075] 步 301 . 移动终端接收用户发起的拍照请求。 [0076]所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0077] 步 302 . 移动终端确定移动终端与用户之间的距离。 [0078] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0079] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0080] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0081] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0082]需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0083] 步 303 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0084] 本实施例中,预设数值由移动终端默认设置。 具体举例来说,移动终端可以默认设置该预设数值为移动终端销售区域内成年人平均臂长的0.7倍至1倍。 [0085] 当用户发起不同的拍照请求时,用户分别使用前置摄像头和后置摄像头的情况可能会有所不同。 因此,优选地,在本实施例中,在根据距离是否小于预设数值来判断是开启前置摄像头还是开启后置摄像头时,针对不同的拍摄请求,预设数值 移动端默认设置不同。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0086] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0087] 当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0088] 在本实施例中,移动终端针对不同的拍照请求默认设置不同的预设数值,使得移动终端可以根据实际情况更灵活地自动开启前置摄像头或后置摄像头,提高用户使用体验。 经验。 [0089] 在上述实施例中,针对不同的拍摄请求,移动终端默认设置的预设数值是不同的。 在实际应用中,对于不同的拍照请求,移动终端还可以根据其他方法调整不同拍照请求对应的预设数值。 下面对根据本发明实施例的移动终端前置摄像头和后置摄像头的选择方法进行说明。 参见图4,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0090] 步 401 . 移动终端接收用户发起的拍照请求。 [0091] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0092] 步 402 . 移动终端确定移动终端与用户之间的距离。 [0093] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0094] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0095] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者测距模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍照请求时,根据自身测距模块或距离确定当前距离 只有当移动终端接收到用户发起的拍照请求时,测量模块才可以检测到移动终端与用户之间的当前距离,移动终端根据其测距模块确定测距模块测得的距离 . [0096] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0097]需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0098] 步 403 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0099] 本实施例中,预设数值由移动终端默认设置。 不同的拍摄请求对应不同的预设数值。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0100] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0101] 步 404 . 获取第一概率和第二概率,第一概率为在第一应用状态下使用前置摄像头的概率,第二概率为在第二应用状态下使用前置摄像头的概率。 [0102] 移动终端统计摄像头分别应用于第一应用和第二应用的次数以及前置摄像头和后置摄像头分别在两个不同应用中的使用次数,然后计算出a 在移动终端的摄像头的第一应用状态和第二应用状态下分别使用前置摄像头的第一概率和第二概率。 举一个具体的例子,移动终端统计摄像头的应用次数,得到摄像头应用到第一应用的次数为589次,摄像头应用到第二个应用的次数为589次。 应用为628,其中摄像头处于第一应用状态时使用前置摄像头的次数为342,摄像头处于第二应用状态时使用前置摄像头的次数为 381. 因此,通过计算可以得到在第一个应用状态下使用前置摄像头的第一概率为342/589,第二个应用状态下使用前置摄像头的第二个概率为381/628 . [0103] 当然,在实际应用中,也可以获取前置摄像头在其他应用状态下的使用概率,或者只获取前置摄像头在最常用的两种应用状态下的使用概率,或者只获取前置摄像头在其他应用状态下的使用概率。 统计用户选择的两种应用状态的前置摄像头,此处不做限定。 [0104]在计算出第一概率和第二概率后,移动终端可以按照预设的时间间隔更新这两个概率,也可以在每次使用相机后更新数据,在此不做限定。 [0105] 步 405 . 根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。 [0106] 获取第一概率和第二概率后,若第一概率大于第二概率,则调整第一预设数值和/或第二预设数值,使得第一预设数值小于第二 预设数值。 举个具体的例子,第一个概率是摄像头在视频通话状态时使用前置摄像头的概率,第二个概率是摄像头处于拍照状态时使用前置摄像头的概率, 并且第一个概率大于第二个概率。 因此,移动终端根据第一概率大于第二概率调整第一预设数值和/或第二预设数值,使得第一预设数值小于第二预设数值。 [0107] 当调整第一预设数值和/或第二预设数值使得第一预设数值小于第二预设数值时,可以使第一预设数值与第二预设数值的比例成比例 第二概率与第一概率的比值; 或者,可以使第一预设数值与第二预设数值的差与第二概率与第一概率的差成正比。 当然,在实际应用中,还可以采用其他方式,使得第一概率对应于第一预设数值,第二概率对应于第二预设数值,在此不做限定。 [0108] 在实际应用中,移动终端可以以预设的时间间隔调整第一预设数值和第二预设数值,例如,移动终端在第一概率和第二概率之后调整第一预设数值和第二预设数值。 概率更新,或者可以在每次使用相机后调整第一预设数值和第二预设数值。 [0109] 本实施例中,移动终端根据摄像头在不同应用状态下使用前置摄像头的概率不同,设置不同应用状态对应的预设数值,以实现移动终端自动开启前置摄像头。 根据实际情况更灵活地选择前置摄像头或后置摄像头,提高用户体验。 [0110] 在上述实施例中,移动终端默认设置的预设数值分别根据第一概率和第二概率进行调整。 在实际应用中,移动终端还可以通过其他方法调整预设数值,下面对本发明实施例提供的移动终端前置摄像头和后置摄像头的选择方法进行说明。 . 参见图5,根据本发明实施例的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0111] 步 501 . 移动终端接收用户发起的拍照请求。 [0112]所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0113] 步 502 . 移动终端确定移动终端与用户之间的距离。 [0114] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0115] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0116] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,移动终端根据其测距模块确定当前距离或 测距模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍照请求时,根据其测距模块或测距确定当前距离 只有当移动终端接收到用户发起的拍照请求时,模块才可以检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定测距模块测得的距离。 [0117] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0118]需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0119] 步 503 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0120] 本实施例中,预设数值由移动终端默认设置。 不同的拍摄请求对应不同的预设数值。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0121] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0122] 步 504 . 移动终端获取用户对前置摄像头和后置摄像头的使用信息,并根据使用信息调整预设数值。 [0123] 移动终端获取用户使用前置摄像头和后置摄像头的信息,该使用信息包括用户使用前置摄像头和后置摄像头的所有记录,例如频率 前置摄像头和后置摄像头分开使用的频率,用户从一个摄像头切换到另一个摄像头的频率,以及用户使用前置摄像头和后置摄像头时移动终端与用户之间的距离 - 单独面对相机。 移动终端在获取到用户对前置摄像头和后置摄像头的使用信息后,根据使用信息进行计算分析,并根据分析结果调整预设数值。 [0124]例如,移动终端确定使用记录中移动终端与用户之间的所有距离的值或确定一些样本值,并计算用户使用前置摄像头的概率和使用后置摄像头的概率。 每个确定的距离值对应的面向相机,然后找出与使用前置相机的概率与使用后置相机的概率之差小于或等于的情况对应的所有目标距离 等于0,并将预设数值调整为所有目标距离之一。 举一个具体的例子,移动终端确定该使用记录中移动终端与用户之间的所有距离的取值范围为0厘米(cm)至60厘米。 当距离值为30cm时,使用后置摄像头的概率为95%,使用前置摄像头的概率为5%; 当距离为40cm时,使用后置摄像头的概率为40%,使用前置摄像头的概率为60%; 距离为50cm时,使用后置摄像头的概率为30%,使用前置摄像头的概率为70%。 因此,可以将预设数值调整为40厘米。 或者,在所有距离值中,使用前置摄像头的概率均低于5%,说明用户很少使用前置摄像头,因此可以将预设数值设置为较大的值, 例如,可能等于手臂长度的 0.95 倍。 [0125] 又如,移动终端在确定开启前置摄像头后,根据移动终端与用户的距离,确定开启前置摄像头还是后置摄像头时 或者后置摄像头,在打开前置摄像头或者后置摄像头之前,移动终端还向用户发送询问请求,询问请求用于询问用户是否同意开启 在相机上; 若用户同意开启摄像头或在预设时间内未收到回复,则移动终端继续开启摄像头; 或者如果用户拒绝开启摄像头,则在第一种情况下,移动终端继续开启默认摄像头,在第二种情况下,移动终端继续使用原有摄像头。 此外,移动终端对用户的反馈进行统计分析。 如果移动终端询问用户是否开启前置摄像头时一致概率超过50%,而移动终端询问用户是否开启后置摄像头时一致概率低于50%,则 移动终端将预设数值增加预定值。 [0126] 需要说明的是,以上描述仅为举例,在此不做限定。 [0127] 当然,在实际应用中,移动终端在对前置摄像头和后置摄像头的使用信息进行分析计算之前,还可以进一步对两个摄像头的使用信息进行分类,其中使用信息, 将前置摄像头和后置摄像头对应的每种拍照请求分类为同一类型,然后对每种使用信息进行分析计算,分别调整对应的预设数值 不同的拍摄要求。 [0128] 移动终端可以按照预设的时间间隔更新前置摄像头和后置摄像头的使用信息,也可以在每次使用摄像头后更新使用信息,在此不做限定。 同理,移动终端可以按照预设的时间间隔调整预设数值,也可以在每次使用相机后调整预设数值,在此不做限定。 [0129]在本实施例中,移动终端获取用户对前置摄像头和后置摄像头的使用信息,并根据使用信息调整预设数值,使移动终端能够自动开启前置摄像头和后置摄像头。 根据实际情况更准确地选择前置摄像头或后置摄像头,从而提高用户体验。 [0130] 在上述实施例中,移动终端默认设置的预设数值是根据用户对前置摄像头和后置摄像头的使用信息进行调整的。 在实际应用中,移动终端可以根据用户的个人信息调整预设的数值,下面对本实施例提供的移动终端前置摄像头和后置摄像头的选择方法进行说明。 本公开的内容。 参见图6,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0131] 步 601 . 移动终端接收用户发起的拍照请求。 [0132] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0133] 步 602 . 移动终端确定移动终端与用户之间的距离。 [0134] 移动终端中设置有可以测量移动终端与用户之间距离的测距模块,测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0135] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0136]在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0137] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0138] 需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0139] 步 603 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0140] 本实施例中,预设数值由移动终端默认设置。 具体举例来说,移动终端可以将预设数值默认设置为移动终端销售区域内成年人平均臂长的0.7倍至1倍。 [0141] 当用户发起不同的拍照请求时,用户分别使用前置摄像头和后置摄像头的情况可能会有所不同。 因此,优选地,在本实施例中,在根据距离是否小于预设数值来判断是开启前置摄像头还是开启后置摄像头时,针对不同的拍摄请求,预设数值 移动端默认设置不同。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0142] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0143]当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0144] 步 604 . 移动终端获取用户的个人信息,并根据个人信息调整预设数值。 [0145] 移动终端可以从移动终端内部存储的应用程序中获取用户的个人信息,也可以从运营商处获取用户的个人信息,也可以由用户输入个人信息。 当然,在实际应用中,移动终端可以从其他来源获取用户的个人信息。 示例仅在本文中描述,并且不受限制。 移动终端获取的用户个人信息可以包括用户的年龄、身高、臂长、性别等信息。 移动终端获取到用户的个人信息后,根据个人信息调整预设数值。 例如,如果用户是女性,由于女性自拍的概率较高,移动终端可以将预设数值减少预定值; 或者如果用户年龄在50岁以上,则用户自拍的概率较低,因此,移动终端可以将预设数值增加预定值。 或者,如果用户的臂长为56cm,则可以将用户臂长的倍数(例如0.7倍)作为预设数值。 当然,以上所述仅为举例,在此不做限定。 [0146] 在本实施例中,移动终端获取用户的个人信息,并根据个人信息调整预设数值,以使移动终端能够更准确地自动开启前置摄像头或后置摄像头。 用户的个人实际情况,从而提高用户体验。 [0147] 在上述实施例中,移动终端默认设置的预设数值是根据用户的个人信息进行调整的。 在实际应用中,移动终端可以根据用户当前所处的环境因素来调整预设数值,下面介绍前置摄像头和后置摄像头的选择方法。 根据本发明实施例的移动终端。 参见图7,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0148] 步 701 . 移动终端接收用户发起的拍照请求。 [0149] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0150] 步 702 . 移动终端确定移动终端与用户之间的距离。 [0151]移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0152] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0153] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0154] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0155] 需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0156] 步 703 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0157] 本实施例中,预设数值由移动终端默认设置。 具体举例来说,移动终端可以将预设数值默认设置为移动终端销售区域内成年人平均臂长的0.7倍至1倍。 [0158]当用户发起不同的拍照请求时,用户分别使用前置摄像头和后置摄像头的情况可能会有所不同。 因此,优选地,在本实施例中,在根据距离是否小于预设数值来判断是开启前置摄像头还是开启后置摄像头时,针对不同的拍摄请求,预设数值 移动端默认设置不同。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0159] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0160] 当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0161] 步 704 . 移动终端获取用户当前所处环境的因子,并根据用户当前所处的环境因子调整预设数值。 [0162] 移动终端可以通过设置在其中的检测器或者其他传感模块获取用户当前所处的环境因素,其中,用户当前所处的环境因素可以包括光线等环境因素。 用户当前所处环境的强度或温度,或用户是在房间内还是在房间外,或用户所处环境的运动状态,并根据 不同的环境因素。 举一个具体的例子,移动终端设置的预设数值的初始值对应于预设的光强参考值。 当移动终端接收到用户发起的拍照请求时,移动终端检测用户当前所处环境的光照强度,并根据预设表格将预设数值调整为预定值。 预设表中设置了不同光强与预设数值的不同具体数值一一对应,光强越小对应预设数值越小。 [0163] 在本实施例中,移动终端获取用户当前所处环境的因子,并根据用户当前所处的环境因子调整预设数值,使移动终端能够自动转向 更准确地根据用户的个人实际情况设置在前置摄像头或后置摄像头上,从而提高用户体验。 [0164]当然,在实际应用中,预设数值也可以不由移动终端默认设置,而可以由用户手动输入。 这样,用户可以根据自己的实际情况设置预设数值,从而使移动终端可以根据个人实际情况更准确地自动开启前置摄像头或后置摄像头。 用户,从而提升用户体验。 [0165] 在上述所有实施例中,当移动终端根据移动终端与用户的距离确定开启前置摄像头还是后置摄像头时,在确定开启前置摄像头后, 前置摄像头或后置摄像头在开启前置摄像头或后置摄像头之前,移动终端进一步向用户发送询问请求,询问请求用于询问用户是否同意 打开相机; 若用户同意开启摄像头或在预设时间内未收到回复,则移动终端触发摄像头开启; 或者如果用户拒绝开启摄像头,则移动终端触发移动终端的默认动作。 第一种情况,默认动作是继续开启移动终端的默认摄像头,第二种情况,默认动作是继续使用原有摄像头。 移动终端在向用户发送查询请求时,可以通过在屏幕上出现的弹窗显示文字来询问用户; 或者,移动终端可以通过语音询问用户是否同意开启摄像头。 用户可以通过点击移动终端屏幕上的预设区域,或者通过语音命令,或者通过摇动终端,或者通过按下移动终端上的物理按键或者虚拟按键来响应来自移动终端的询问。 . 当然,以上所述仅为举例,在此不做限定。 [0166] 或者,移动终端也可以不询问用户,而是直接通知用户前置摄像头或后置摄像头开启。 例如,移动终端可以通过在屏幕上显示文本或图像或其他标志来通知用户,或者通过发出声音或振动来通知用户。 当然,以上所述仅为举例,在此不做限定。 [0167] 为便于理解,下面结合实际应用场景对本实施例的移动终端前置摄像头和后置摄像头的选择方法进行说明。 [0168] 手机默认设置预设数值的初始值为35cm。 手机的摄像头目前处于关闭状态。 手机接收用户发起的拍照请求,手机中的测距模块检测当前手机摄像头与用户鼻子之间的距离。 手机根据测距模块确定测距模块检测到的距离为40cm。 [0169] 手机判断距离大于手机默认设置的预设数值,并通过语音询问用户是否同意开启手机前置摄像头。 手机获取用户的语音指令后,对语音指令进行分析,识别出用户同意开启前置摄像头,然后开启手机前置摄像头。 [0170]此外,手机还会更新手机中存储的用户使用前置摄像头和后置摄像头的信息,更新后的数据如下: 手机与用户鼻子35厘米,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%; 距离为40cm时,使用后置摄像头的概率为52%,使用前置摄像头的概率为48%; 当距离为45cm时,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%。 因此,手机将预设数值的具体数值调整为40厘米。 [0171] 以上对本发明实施例的移动终端前置摄像头和后置摄像头的选择方法进行了描述,下面对本发明实施例的移动终端进行说明。 参见图8,本发明实施例的移动终端实施例包括前置摄像头和后置摄像头。 接收模块 801 用于接收用户发起的拍照请求; 确定模块 802 用于确定移动终端与用户之间的距离; 和一个控制模块 803 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0172] 本实施例中,移动终端通过控制模块判断移动终端与用户的距离是否大于预设数值,从而自动判断是否开启移动终端的前置摄像头。 或者打开移动终端的后置摄像头,从而实现了移动终端前置摄像头和后置摄像头之间的自动选择,避免了用户需要手动选择的情况,提高了用户 移动端体验。 [0173] 在上述实施例中,移动终端与用户之间的距离可以是移动终端与用户面部之间的距离。 该距离可以是移动终端到用户面部特定预设位置的距离,例如,该距离是移动终端到用户两只眼睛的中心点的距离,或者是两眼之间的距离。 移动终端和用户的鼻子; 或者,该距离可以是移动终端到用户面部至少两个预设位置的总距离,例如,该距离等于移动终端到用户两只眼睛的距离的平均值, 或者移动终端与用户五种感觉器官的距离平均值。 当然,以上所述仅为举例,在此不做限定。 [0174] 当然,在实际应用中,该距离可以不是确定的移动终端与用户面部之间的距离,而可以是移动终端与用户其他部分的距离,在此不做限定。 优选地,移动终端可以接收用户对距离的特定定义的设置。 [0175] 在实际应用中,确定移动终端与用户面部的距离可以是确定移动终端的摄像头与用户面部的距离,也可以是确定移动终端上其他位置与用户面部的距离。 用户的面部,或者确定移动终端上至少两个位置与用户面部的总距离,在此不做限定。 [0176]上述实施例中,控制模块用于当确定的距离大于或等于预设数值时,开启前置摄像头; 或者当距离小于预设数值时,开启后置摄像头。 在实际应用中,预设数值可以由移动终端默认设置。 优选地,接收模块接收到的拍摄请求至少包括第一应用请求和第二应用请求。 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值,第一预设数值与第二预设数值不同。 这样,移动终端可以针对不同的拍照请求默认设置不同的预设数值,使得移动终端可以根据实际情况更灵活地自动开启前置摄像头或后置摄像头,从而提高 用户体验。 当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0177] 在实际应用中,当移动终端分别调整第一预设数值和第二预设数值,使得这两个预设数值不同时,可以根据分别使用前置摄像头的概率进行调整。 相机的第一应用状态和第二应用状态。 下面对本发明实施例的移动终端进行说明。 参见图9,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 901 用于接收用户发起的拍照请求; 确定模块 902 用于确定移动终端与用户之间的距离; 和一个控制模块 903 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0178] 在本实施例中,移动终端还包括第一获取模块 904 用于获取第一概率和第二概率,第一概率为用户在第一应用状态下使用前置摄像头的概率,第二概率为用户使用前置摄像头的概率。 处于第二应用状态的用户; 以及第一调整模块 905 用于根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。 [0179] 本实施例中,移动终端根据摄像头在不同应用状态下使用前置摄像头的概率不同,设置不同应用状态对应的预设数值,以实现移动终端自动开启前置摄像头。 根据实际情况更灵活地选择前置摄像头或后置摄像头,提高用户体验。 [0180] 在上述实施例中,移动终端默认设置的预设数值分别根据第一概率和第二概率进行调整。 在实际应用中,移动终端可以通过其他方法调整预设数值,下面对本发明实施例提供的移动终端进行说明。 参见图10,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1001 用于接收用户发起的拍照请求; 确定模块1002 用于确定移动终端与用户之间的距离; 和一个控制模块 1003 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0181] 在本实施例中,移动终端还包括第二获取模块 1004 用于获取用户使用前置摄像头和后置摄像头的信息; 第二调整模块 1005 用于根据使用信息调整预设数值。 [0182] 在本实施例中,移动终端获取用户对前置摄像头和后置摄像头的使用信息,并根据使用信息调整预设数值,使得移动终端可以自动开启前置摄像头和后置摄像头。 根据实际情况更准确地选择前置摄像头或后置摄像头,从而提高用户体验。 [0183] 上述实施例中,移动终端根据用户使用前置摄像头和后置摄像头的信息,调整移动终端默认设置的预设数值。 在实际应用中,移动终端还可以利用用户的个人信息对预设数值进行调整,下面对本发明实施例提供的移动终端进行说明。 参见图11,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1101 用于接收用户发起的拍照请求; 确定模块 1102 用于确定移动终端与用户之间的距离; 和一个控制模块 1103 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0184] 在本实施例中,移动终端还包括第三获取模块 1104 用于获取用户的个人信息,并根据个人信息调整预设数值; 第三调整模块 1105 用于根据个人信息调整预设数值。 [0185] 在本实施例中,移动终端获取用户的个人信息,并根据个人信息调整预设数值,使得移动终端能够更准确地根据个人信息自动开启前置摄像头或后置摄像头。 用户的个人实际情况,从而提高用户体验。 [0186] 上述实施例中,移动终端根据用户的个人信息,对移动终端默认设置的预设数值进行调整。 在实际应用中,移动终端还可以根据用户当前所处的环境对预设数值进行调整,下面对本发明实施例的移动终端进行说明。 参见图12,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1201 用于接收用户发起的拍照请求; 确定模块 1202 用于确定移动终端与用户之间的距离; 和一个控制模块 1203 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0187] 在本实施例中,移动终端还包括第四获取模块 1204 用于获取用户当前所处环境的因子; 第四调整模块 1205用于根据用户当前所处环境的因素调整预设数值。 [0188] 在本实施例中,移动终端获取用户当前所处环境的因子,并根据用户当前所处的环境因子调整预设数值,使移动终端能够自动转向 更准确地根据用户的个人实际情况设置在前置摄像头或后置摄像头上,从而提高用户体验。 [0189] 在上述实施例中,预设数值是由移动终端默认设置的。 在实际应用中,预设数值可以由用户手动输入,下面对本发明实施例提供的移动终端进行说明。 参见图13,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1301 用于接收用户发起的拍照请求; 确定模块 1302 用于确定移动终端与用户之间的距离; 和一个控制模块 1303 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0190] 在本实施例中,移动终端还包括第五获取模块 1304 用于获取用户输入的预设数值。 [0191] 在本实施例中,移动终端可以使用户根据用户的实际情况设置预设数值,从而使移动终端能够更准确地自动开启前置摄像头或后置摄像头。 用户的个人实际情况,从而提高用户体验。 [0192] 在上述实施例中,移动终端根据移动终端与用户的距离来确定开启前置摄像头还是后置摄像头。 在实际应用中,在开启前置摄像头或后置摄像头之前,还可以向用户发送查询请求,下面对本发明实施例的移动终端进行说明。 参见图14,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头; 接收模块 1401 用于接收用户发起的拍照请求; 确定模块 1402 用于确定移动终端与用户之间的距离; 和一个控制模块 1403 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0193] 在本实施例中,移动终端还包括查询模块 1404 用于向用户发送查询请求,该查询请求用于询问用户是否同意开启摄像头; 第六获取模块 1405 配置为获取用户的回复; 第一触发单元 1406 用于当回复为同意开启摄像头或在预设时间内未收到回复时,触发开启移动终端前置摄像头或移动终端后置摄像头; 和第二个触发单元 1407 用于当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0194] 在本实施例中,移动终端可以通过询问用户来确定是自动开启前置摄像头还是后置摄像头,以便开启的摄像头更好地满足用户的需求,从而 改善用户体验。 [0195]为便于理解,下面以实际应用场景对本实施例的移动终端进行说明。 [0196] 手机默认设置预设数值的初始值为35cm。 手机的摄像头目前处于关闭状态。 手机的接收模块接收用户发起的拍照请求,手机中的测距模块检测当前手机摄像头与用户鼻子之间的距离。 手机的判断模块根据测距模块确定测距模块检测到的距离为40cm。 [0197] 手机判断距离大于手机默认设置的预设数值,通过查询模块向用户发出语音,询问用户是否同意开启手机前置摄像头。 手机。 第六获取模块获取用户的语音命令。 当第六获取模块通过分析语音指令识别出用户同意开启摄像头时,第一触发单元触发控制模块开启手机前置摄像头。 [0198] 此外,第二获取模块获取用户对前置摄像头和后置摄像头的使用信息,更新使用信息并存储更新后的使用信息,更新后的数据如下: 手机的摄像头与用户鼻子的距离为35厘米,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%; 距离为40cm时,使用后置摄像头的概率为52%,使用前置摄像头的概率为48%; 当距离为45cm时,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%。 因此,手机的第二调整模块将预设数值的具体数值调整为40cm。 [0199] 参见图15,本实施例以手机为例对本发明进行说明。 [0200] 需要注意的是,手机 100 图中所示仅为移动终端的示例,手机 100 可以包括比图中所示的组件更多或更少的组件,或者可以组合两个或更多组件,或者可以使用不同的组件部署。 图中所示的组件可以以硬件、软件或包括一个或多个信号处理和/或专用集成电路的硬件和软件的组合来实现。 [0201] 这里以手机为例进行具体说明。 如图15所示,手机上设置有前置摄像头和后置摄像头,手机还包括内存 11 , 一个中央处理器 13 (CPU),外围接口 14 , 射频 (RF) 电路 15 , 音频电路 16 , 一个扬声器 17 ,电源管理集成芯片 18 , 输入/输出 (I/O) 子系统 19 , 另一个输入/控制设备 110 , 和一个外部端口 111 ,其中这些组件使用一条或多条通信总线或信号线相互通信 112 . [0202] 需要说明的是,本实施例提供的手机仅仅是移动终端的一个示例。 本发明实施例所涉及的服务器可以包括比图15所示的组件更多或更少的组件,或者可以组合两个或多个组件,或者可以使用不同的组件部署或设置。 并且这些组件可以以硬件、软件或包括一个或多个信号处理和/或专用集成电路的硬件和软件的组合来实现。 [0203] 下面对本发明实施例提供的信息推送手机进行详细说明。 [0204] 记忆 11 CPU可以访问 13 和外围接口 14, 记忆 11 存储器可以包括高速随机存取存储器,也可以包括非易失性存储器,例如,一个或多个磁存储设备、闪存或其他非易失性固态存储器。 [0205] 外围接口可以将设备的输入和输出外围设备连接到 CPU 13 和记忆 11 . [0206] I/O 子系统 19 可以连接设备上的输入和输出外围设备,例如触摸屏 113 (相当于前述实施例中的显示器)和另一个输入/控制设备 110 , 到外围接口 14 . I/O 子系统 19 可能包括显示控制器 191 和一个或多个输入控制器 192 用于控制另一个输入/控制设备 110 . 一个或多个输入控制器 192 从另一个输入/控制设备接收电信号 110 或将电信号发送到另一个输入/控制设备 110 ,其中另一个输入/控制设备 110 可以包括物理按钮(按下按钮、摇杆按钮等)、拨盘、滑动开关、操纵杆、点击滚轮。 需要注意的是,输入控制器 192 可与以下任一组件连接:键盘、红外端口、通用串行总线(USB)接口、鼠标等定点设备。 [0207] 触摸屏 113 作为移动终端与用户之间的输入接口和输出接口,向用户显示可视输出,可视输出可以包括图片、文字、图标、视频等。 [0208] 显示控制器 191 在 I/O 子系统中 19 从触摸屏接收电信号 113 或向触摸屏发送电信号 113 . 触摸屏 113 检测触摸屏上的触摸; 显示控制器 191 将检测到的触摸转换为与触摸屏上显示的用户界面对象的交互 113 ,即人机交互,其中用户界面对象显示在触摸屏上 113 可以是游戏运行图标、链接到相应网络的图标等。 需要说明的是,该装置还可以包括光学鼠标,该光学鼠标是不显示可见输出的触敏面,或者是由触摸屏形成的触敏面的延伸。 [0209] 射频电路 15 主要用于建立手机与无线网络(即网络侧)之间的通信,实现手机与无线网络之间的数据收发,如短信业务消息的收发 和电子邮件(E-mail)。 射频电路 15 接收和发送射频信号,该射频信号也称为电磁信号; 射频电路 15 将电信号转换为电磁信号或将电磁信号转换为电信号,并使用该电磁信号与通信网络和其他设备进行通信。 射频电路 15 可以包括用于执行这些功能的已知电路,包括但不限于天线系统、RF收发器、一个或多个放大器、调谐器、一个或多个振荡器、数字信号处理器、CODEC芯片组、用户 身份模块 (SIM) 等。 [0210] 音频电路 16 主要配置为从外设接口接收音频数据 14 ,将音频数据转换为电信号,并将电信号发送到扬声器 17 . [0211] 扬声器 17 用于通过射频电路恢复手机从无线网络接收到的语音信号 15 发声,并向用户播放声音。 [0212] 电源管理集成芯片 18 配置为为连接到 CPU 的硬件供电 13 、I/O 子系统和外围接口,并执行电源管理。 [0213]图16是手机内部结构图。 在本发明实施例中,软件部分存储在存储器中 11 可能包括操作系统 21 , 通信模块 22 , 触控/移动模块 23 , 一个图形模块 24 , 和一个功能模块 26 . [0214] 操作系统 21 (例如,Darwin、RTXC、LINUX、UNIX、OS X、WINDOWS 或 VxWorks® 等嵌入式操作系统)包括用于控制和管理常见系统任务(例如,内存管理、控制 通过存储设备、电源管理等),并促进硬件部分和软件部分之间的通信。 [0215] 通讯模块 22 配置为使用一个或多个外部端口与另一设备通信 111 ,并且还包括用于处理RF电路接收到的数据的各种软件部分 15 和/或外部端口 111 . [0216] 触控/移动模块 23 可能会检测到触摸屏上的触摸 113 (结合显示控制器 191 ) 和另一个触敏设备(例如,触摸板或物理点击滚轮)。 触控/移动模块 23 包括用于执行和检测各种与触摸相关的操作的各种软件部分,其中操作例如判断是否发生触摸、判断触摸是否移动以及在触摸屏上跟踪移动 113 ,并判断触摸是否已经中断(即触摸是否已经停止)。 确定触摸点的移动可以包括确定触摸的速率(幅度值)、速度(幅度值和方向)和/或加速度(幅度值和/或方向的变化) 观点。 这些操作可以应用于单个触摸(例如,用一根手指触摸)或应用于多个同时触摸(例如,“多点触摸”/用多个手指触摸)。 在一些实施例中,触摸/移动模块 23 和显示控制器 191 进一步检测触摸板上的触摸。 [0217] 图形模块 24 包括用于在触摸屏上显示图像的各种已知软件部件 113 ,包括用于改变显示图像亮度的部分,例如,用于接收来自中央处理器的指令的图形用户界面 13 并在触摸屏上显示各类软件 113 . [0218] 功能模块 26 可能包括以下模块一个接收模块 261 用于接收用户发起的拍照请求; 确定模块 262 用于确定移动终端与用户之间的距离; 和一个控制模块 263 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,开启移动终端的后置摄像头。 [0219] 射频电路 15 接收网络侧或其他设备发送的信息,该消息可以是上述实施例中的第一用户的终端号码和推荐率计算参数。 可以理解的是,接收到的消息可以是其他类型的信息,本发明实施例对此不做限定。 本领域技术人员可以知道,接收到的信息可以携带多种数据类型的数据。 可能只有一种数据类型的数据,也可能有两种或多种数据类型的数据。 [0220] 中央处理器 13 识别射频电路接收到的信息中数据的数据类型 15 ; 根据对应关系列表将数据存储到与数据的数据类型对应的功能模块中,对应关系列表为数据类型与功能模块对应关系的列表,其中功能模块 26 可能是一个控制模块 263 和确定模块 262. 可以理解的是,在本发明实施例中,中央处理器的一种方式 13 识别各种格式的数据可以是上述实施例的方式,在此不再赘述。 [0221] 判断模块 262 被配置为确定移动终端与用户面部之间的距离。 [0222] 判断模块 262 用于确定移动终端与用户面部预设位置的距离; 或确定模块 262 用于确定移动终端与用户面部的至少两个预设位置之间的总距离。 [0223] 预设数值由移动终端默认设置。 [0224] 拍摄请求至少包括第一应用请求和第二应用请求。 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值,第一预设数值与第二预设数值不同。 [0225] 所述功能模块还包括第一获取模块,用于获取第一概率和第二概率,所述第一概率为用户在第一应用状态下使用前置摄像头的概率,所述第二概率为概率 用户在第二应用状态下使用前置摄像头; 第一调整模块,用于根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应于第一预设数值,第二概率对应于第二 预设数值。 [0226] 所述功能模块还包括第二获取模块,用于获取用户使用前置摄像头和后置摄像头的信息。 第二调整模块,用于根据使用信息调整预设数值。 [0227] 所述功能模块还包括第三获取模块,用于获取用户的个人信息,并根据个人信息调整预设数值。 第三调整模块,用于根据个人信息调整预设数值。 [0228] 所述功能模块还包括第四获取模块,用于获取用户当前所处的环境; 第四调整模块,用于根据预设对应表,将预设数值的具体数值调整为与用户当前所处环境对应的数值,预设对应表存储映射关系 预设数值的不同环境和不同具体数值之间。 [0229] 所述功能模块还包括第五获取模块,用于获取用户输入的预设数值。 [0230] 所述功能模块还包括询问模块,用于向所述用户发送询问请求,所述询问请求用于询问所述用户是否同意开启摄像头。 第六获取模块,用于获取用户的回复; 第一触发单元,用于当回复为同意开启摄像头或在预设时间内未收到回复时,触发控制模块开启移动终端的前置摄像头或后置摄像头 移动终端; 第二触发单元,用于当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0231]在本发明实施例中,计算模块根据推荐评分计算参数计算第一用户的每个终端号码的推荐评分,发送模块将每个推荐评分发送给第二用户,以便第二用户 选择呼叫推荐等级最高的终端号码,从而准确高效地选择被呼叫号码,避免呼叫失败操作。 [0232] 在本发明的上述实施例中,服务器包括但不限于手机、PDA、平板电脑等移动通信设备的服务器。 [0233] 需要说明的是,本领域普通技术人员可以理解,实施例中方法的全部或部分过程可以通过计算机程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 当程序运行时,执行实施例中方法的流程。 上述存储介质可以包括磁盘、光盘、只读存储器(ROM)或随机存取存储器(RAM)。 [0234] 本领域技术人员可以清楚地了解到,为描述的方便和简洁,上述系统、装置和单元的具体工作过程可以参见上述方法实施例中的对应过程。 ,此处不再赘述。 [0235] 在本申请提供的几个实施例中,应当理解,所公开的系统、装置和方法可以通过其他方式实现。 例如,所描述的装置实施例仅仅是示例性的。 例如,单元划分仅仅是逻辑上的功能划分,实际实现中还可以是其他的划分。 例如,可以将多个单元或组件组合或集成到另一个系统中,或者可以忽略或不执行某些特征。 此外,显示或讨论的相互耦合或直接耦合或通信连接可以通过一些接口来实现。 装置或单元之间的间接耦合或通信连接可以以电子、机械或其他形式实现。 [0236] 被描述为独立部分的单元可以是物理上独立的,也可以不是物理上的,作为单元显示的部分可以是物理单元,也可以不是物理单元,可以位于一个位置,或者可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部单元来实现本实施例方案的目的。 [0237] 另外,本发明实施例中的功能单元可以集成在一个处理单元中,也可以是各个单元在物理上单独存在,或者两个或多个单元集成在一个单元中。 集成单元可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。 [0238] 当集成单元以软件功能单元的形式实现并作为独立产品销售或使用时,集成单元可以存储在计算机可读存储介质中。 基于这样的理解,本发明的技术方案本质上,或者对现有技术有贡献的部分,或者全部或者部分技术方案,可以以软件产品的形式来实现。 该软件产品存储在存储介质中,包括若干指令,用于指示计算机设备(可以是个人计算机、服务器或网络设备)执行本发明实施例中描述的方法的全部或部分步骤。 本公开。 上述存储介质包括U盘、移动硬盘、ROM、RAM、磁盘、光盘等任何可以存储程序代码的介质。 [0239]上述实施例仅用于说明本发明的技术方案,并不用于限制本发明。 尽管结合前述实施例对本发明进行了详细描述,但本领域普通技术人员应当理解,对于前述实施例中描述的技术方案,仍然可以进行修改或者对部分技术特征进行等效替换,而不 脱离本发明实施例技术方案的精神和范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103795864A(String), CN103795864B(String), EP3089434A1(String), EP3089434A4(String), EP3089434B1(String), EP3386174A1(String), EP3386174B1(String), ES2663245T3(String), JP2017511626A(String), JP6293295B2(String), KR101843810B1(String), KR1020160108507A(String), US20160337588A1(String), US9906723B2(String), WO2015113372A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103795864A(String), CN103795864B(String), EP3089434A1(String), EP3089434A4(String), EP3089434B1(String), EP3386174A1(String), EP3386174B1(String), ES2663245T3(String), JP2017511626A(String), JP6293295B2(String), KR101843810B1(String), KR1020160108507A(String), US20160337588A1(String), US9906723B2(String), WO2015113372A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9906723B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.217 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103795864A(String), CN103795864B(String), EP3089434A1(String), EP3089434A4(String), EP3089434B1(String), EP3386174A1(String), EP3386174B1(String), ES2663245T3(String), JP2017511626A(String), JP6293295B2(String), KR101843810B1(String), KR1020160108507A(String), US20160337588A1(String), US9906723B2(String), WO2015113372A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), CN103795864A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), CN103795864B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), EP3089434A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), EP3089434A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), EP3089434B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), EP3386174A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), EP3386174B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), ES2663245T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), JP2017511626A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), JP6293295B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), KR101843810B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), KR1020160108507A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), US20160337588A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), US9906723B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270649(Integer), WO2015113372A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9906723B2(String), US9906723B2(String), 1519660800(Integer), 270649(Integer), 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184966(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184966(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184966(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184966(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9781547B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for establishing WLAN by mobile terminal, and mobile terminal(String), 移动终端建立WLAN的方法及移动终端(String), US9781547B2(String), Provided are a method for establishing a WLAN by a mobile terminal and a mobile terminal. The method comprises: when the mobile terminal needs to establish a WLAN with other terminals, the mobile terminal starts Bluetooth, and modifies a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; and starts Bluetooth search to acquire Bluetooth MAC addresses of other terminals with the identifiers contained in the name of the Bluetooth device; and a Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN.(String), 提供了一种移动终端建立WLAN的方法及移动终端。 该方法包括:当移动终端需要与其他终端建立WLAN时,移动终端启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 启动蓝牙搜索,以蓝牙设备名称中包含的标识获取其他终端的蓝牙MAC地址; 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。(String), US14/913467(String), 1384358400(Integer), US9781547B2(String), 1506960000(Integer), 1506960000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 5(Integer), CN103037533A | CN103179635A | US20090207445A1 | US20140206346A1 | WO2007057758A2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184967(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8ae8f48a8e0d4d87827e32e5f448598c.png(String), 184967(Integer), 8ae8f48a8e0d4d87827e32e5f448598c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for establishing WLAN by mobile terminal, and mobile terminal(String), 移动终端建立WLAN的方法及移动终端(String), US9781547B2(String), Provided are a method for establishing a WLAN by a mobile terminal and a mobile terminal. The method comprises: when the mobile terminal needs to establish a WLAN with other terminals, the mobile terminal starts Bluetooth, and modifies a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; and starts Bluetooth search to acquire Bluetooth MAC addresses of other terminals with the identifiers contained in the name of the Bluetooth device; and a Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN.(String), 提供了一种移动终端建立WLAN的方法及移动终端。 该方法包括:当移动终端需要与其他终端建立WLAN时,移动终端启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 启动蓝牙搜索,以蓝牙设备名称中包含的标识获取其他终端的蓝牙MAC地址; 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。(String), US14/913467(String), 1384358400(Integer), US9781547B2(String), 1506960000(Integer), 1506960000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 5(Integer), CN103037533A | CN103179635A | US20090207445A1 | US20140206346A1 | WO2007057758A2(String), \20230420\8ae8f48a8e0d4d87827e32e5f448598c.png(String), 12(Integer), 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 1. A method for establishing a Wireless Local Area Network (WLAN) by a mobile terminal, comprising:when the mobile terminal needs to establish the WLAN with other terminals, starting a Bluetooth device in the mobile terminal, and modifying a name of the Bluetooth device in the mobile terminal to a character string that contains an identifier;starting Bluetooth search, to acquire Bluetooth Media Access Control (MAC) addresses of the other terminals with the identifier contained in a name of a Bluetooth device in each of the other terminals; andcomparing a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN.(String), 1.一种移动终端建立无线局域网的方法,包括:当移动终端需要与其他终端建立WLAN时,启动移动终端中的蓝牙设备,将移动终端中的蓝牙设备的名称修改为包含标识的字符串。启动蓝牙搜索,获取其他终端的蓝牙媒体访问控制(MAC)地址,以及其他终端中蓝牙设备名称中包含的标识;和分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 2. The method according to claim 1, wherein comparing the Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets the pre-set condition, setting the mobile terminal as the wireless access point of the WLAN comprises:performing character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when a character string of the Bluetooth MAC address of the mobile terminal is a maximum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from the other terminals with the identifier contained in the name of the Bluetooth device; orperforming character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when the character string of the Bluetooth MAC address of the mobile terminal is a minimum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start the wireless access function, receive and agree with the wireless access request of the other terminals with the identifier contained in the name of the Bluetooth device.(String), 2.根据权利要求1所述的方法,其中将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点包括:分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为移动终端的蓝牙MAC地址和获取蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求;或者对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为移动终端的蓝牙MAC地址和获取的蓝牙MAC地址中的最小值时蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 3. The method according to claim 2, wherein setting, when the Bluetooth MAC address of the mobile terminal meets the pre-set condition, the mobile terminal as the wireless access point of the WLAN further comprises:verifying the wireless access request sent by the other terminals with the identifier contained in the name of the Bluetooth device.(String), 3.根据权利要求2所述的方法,其中设置,当移动终端的蓝牙MAC地址满足预设条件时,移动终端作为WLAN的无线接入点还包括:通过蓝牙设备名称中包含的标识验证其他终端发送的无线接入请求。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 4. The method according to claim 1, wherein after the Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, the method further comprises:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, searching for the wireless access point and sending the wireless access request.(String), 4.根据权利要求1所述的方法,其中将移动终端的蓝牙MAC地址分别与获取的蓝牙MAC地址进行比较后,该方法还包括:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 5. The method according to claim 1, wherein starting the Bluetooth search to acquire the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device comprises:starting the Bluetooth search, setting a search condition as containing the identifier in the name of the Bluetooth device, and acquiring the Bluetooth MAC addresses of the other terminals with the identifier contained in the name of the Bluetooth device.(String), 5.根据权利要求1所述的方法,其中启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址,包括:启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,并获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。6、一种建立无线局域网的移动终端,包括:启动及修改模块,用于当移动终端需要与其他终端建立WLAN时,启动移动终端中的蓝牙设备,并将移动终端的蓝牙设备名称修改为包含标识的字符串;搜索获取模块,用于启动蓝牙搜索,获取其他终端的蓝牙媒体访问控制(MAC)地址,以及其他终端中蓝牙设备名称中包含的标识;和比较执行模块,用于分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为无线接入点无线局域网。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 6. A mobile terminal for establishing a Wireless Local Area Network, comprising:a start and modification component configured to, when the mobile terminal needs to establish the WLAN with other terminals, start a Bluetooth device in the mobile terminal, and modify a name of the Bluetooth device of the mobile terminal to a character string that contains an identifier;a search and acquisition component configured to start Bluetooth search, to acquire Bluetooth media access control (MAC) addresses of the other terminals with the identifier contained in a name of a Bluetooth device in each of the other terminals; anda comparison and execution component configured to compare a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, set the mobile terminal as a wireless access point of the WLAN.(String), 7.根据权利要求6所述的移动终端,其中比较和执行组件配置为:分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串是移动终端的蓝牙MAC地址和获取蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求;或者分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为移动终端的蓝牙MAC地址和获取蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他终端的无线接入请求,该终端带有蓝牙设备名称中的标识。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 7. The mobile terminal according to claim 6, wherein the comparison and execution component is configured to:perform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when a character string of the Bluetooth MAC address of the mobile terminal is a maximum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from the other terminals with the identifier contained in a name of a Bluetooth device; orperform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when a character string of the Bluetooth MAC address of the mobile terminal is a minimum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start the wireless access function, receive and agree with the wireless access request from the other terminals with the identifier contained in the name of the Bluetooth device.(String), 8.根据权利要求7所述的移动终端,其中比较执行组件进一步配置为:通过蓝牙设备名称中包含的标识符验证其他终端发送的无线接入请求。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 8. The mobile terminal according to claim 7, wherein the comparison and execution component is further configured to:verify the wireless access request sent by the other terminals with the identifier contained in the name of the Bluetooth device.(String), 9.根据权利要求6所述的移动终端,其中比较执行组件进一步配置为:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 9. The mobile terminal according to claim 6, wherein the comparison and execution component is further configured to:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, search for the wireless access point and send the wireless access request.(String), 10.根据权利要求6所述的移动终端,其中搜索和获取组件进一步配置为:启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 10. The mobile terminal according to claim 6, wherein the search and acquisition component is further configured to:start the Bluetooth search, set a search condition as containing the identifier in the name of the Bluetooth device, and acquire the Bluetooth MAC addresses of the other terminals with the identifier contained in the name of the Bluetooth device.(String), 11.根据权利要求2所述的方法,其中将移动终端的蓝牙MAC地址分别与获取的蓝牙MAC地址进行比较后,该方法还包括:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 11. The method according to claim 2, wherein after the Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, the method further comprises:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, searching for the wireless access point and sending the wireless access request.(String), 12.根据权利要求7所述的移动终端,其中比较执行组件进一步配置为:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184967(Integer), 12. The mobile terminal according to claim 7, wherein the comparison and execution component is further configured to:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, search for the wireless access point and send the wireless access request.(String), 1(Integer), 11(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184967(Integer), TECHNICAL FIELD [0001]The present disclosure relates to the technical field of mobile communications, and in particular to a method for establishing a Wireless Local Area Network (WLAN) by a mobile terminal, and the mobile terminal. BACKGROUND [0002]With the popularization of mobile intelligent devices, the need for establishing a WLAN between mobile terminals in a short distance to share files is increasing. In establishing the WLAN between mobile terminals in a short distance, one of the mobile terminals is required to serve as a wireless access point (Access Point, referred to as AP for short), and other mobile terminals join the AP, so that the WLAN is established for communication. [0003]However, in the related art, the establishment of the WLAN among mobile terminals requires a user to have a certain network technologies base, which brings difficulty to the operation of common users; in addition, users of different mobile terminals are required to coordinate and determine, in the process of establishing the WLAN, which side serves as a wireless access point and which side serves as a common request access end, and the operation is quite complex, thereby reducing the interest of a user in establishing a WLAN for files sharing, and being not beneficial to the promotion of applications related to a WLAN of a mobile terminal. SUMMARY [0004]The embodiments of the present disclosure provide a method for establishing a WLAN by a mobile terminal, and a mobile terminal, so as to more conveniently and quickly establish a WLAN. [0005]The embodiments of the present disclosure provide a method for establishing a WLAN by a mobile terminal, comprising: [0006]when the mobile terminal needs to establish a WLAN with other terminals, starting Bluetooth, and modifying a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; [0007]starting Bluetooth search to acquire Bluetooth media access control (Media Access Control, referred to as MAC for short) addresses of other terminals with the identifier contained in the name of the Bluetooth device; and [0008]comparing a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN. [0009]Preferably, comparing the Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN comprises: [0010]performing character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in a name in a Bluetooth device; or [0011]performing character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in the name of the Bluetooth device. [0012]Preferably, setting the mobile terminal as the wireless access point of the WLAN when the Bluetooth MAC address of the mobile terminal meets the pre-set condition further comprises: [0013]verifying the wireless access request sent by other terminals with the identifier contained in the name of the Bluetooth device. [0014]Preferably, after comparing the Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, the method further comprises: [0015]when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, searching for the wireless access point and sending the wireless access request. [0016]Preferably, starting Bluetooth search to acquire the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device comprises: [0017]starting the Bluetooth search, setting a search condition as containing the identifier in the name of the Bluetooth device, and acquiring the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device. [0018]The embodiments of the present disclosure further provide a mobile terminal for establishing a WLAN, wherein the device comprises: [0019]a start and modification component configured to start Bluetooth when the mobile terminal needs to establish a WLAN with other terminals, and modify a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; [0020]a search and acquisition component configured to start Bluetooth search to acquire Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device; and [0021]a comparison and execution component configured to compare a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, set the mobile terminal as a wireless access point of the WLAN. [0022]Preferably, the comparison and execution component is configured to: [0023]perform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in the name of the Bluetooth device; or [0024]perform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in the name of the Bluetooth device. [0025]Preferably, the comparison and execution component is further configured to: [0026]verify the wireless access request sent by other terminals with the identifier contained in the name of the Bluetooth device. [0027]Preferably, the comparison and execution component is further configured to: [0028]when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, search for the wireless access point and send the wireless access request. [0029]Preferably, the search and acquisition component is further configured to: [0030]start the Bluetooth search, set a search condition as containing the identifier in the name of the Bluetooth device, and acquire the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device. [0031]The method for establishing a WLAN by a mobile terminal, and the mobile terminal are provided by the embodiments of the present disclosure, in which Bluetooth MAC addresses of other terminals intending to establish the WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when a character string of a Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as a wireless access point to start a wireless access function to receive a wireless access request of other terminals so as to establish the WLAN; and since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. BRIEF DESCRIPTION OF THE DRAWINGS [0032]FIG. 1 shows a schematic flowchart of a method for establishing a WLAN by a mobile terminal according to a preferred embodiment of the present disclosure; and [0033]FIG. 2 shows a structural schematic diagram of a mobile terminal for establishing a WLAN in a preferred embodiment of the present disclosure. [0034]To make the technical solutions of the present disclosure more clear, the present disclosure is further described in detail hereinafter in conjunction with the drawings. DETAILED DESCRIPTION OF THE EMBODIMENTS [0035]The solution of the embodiments of the present disclosure is mainly: Bluetooth MAC addresses of other terminals intending to establish a WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when a character string of a Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as a wireless access point to start a wireless access function to receive a wireless access request from other terminals so as to establish the WLAN. Since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved. [0036]As shown in FIG. 1, the preferred embodiment of the present disclosure provides a method for establishing a WLAN by a mobile terminal. [0037]In the step S101, when a mobile terminal needs to establish a WLAN with other terminals, Bluetooth is started, and a name of a Bluetooth device of the mobile terminal is modified to a character string that contains an identifier. [0038]In the present embodiment, the mobile terminal has a Bluetooth function, and when the mobile terminal needs to establish the WLAN with other terminals, Bluetooth is started, and the name of the Bluetooth device thereof is modified to the character string that contains the identifier, wherein the identifier may be a feature field for setting an identification for several terminals that need to establish the WLAN for identification, so that the interference of other unrelated terminals is avoided. [0039]In step S102, Bluetooth search is started to acquire Bluetooth MAC addresses, of other terminals with the identifier above contained in a name of a Bluetooth device. [0040]After modifying the name of the Bluetooth device thereof to the character string that contains the identifier, the mobile terminal uses Bluetooth for search, and sets a search condition as containing the identifier above in the name of the Bluetooth device, so as to ensure that the identified terminals are other terminals needing to establish the WLAN, thereby avoiding wasting time searching other unrelated terminals, and saving the time for search. [0041]After other terminals with the identifier above contained in the name of the Bluetooth device are searched, the Bluetooth MAC addresses of the Bluetooth devices containing the identifier above in the name of the Bluetooth device are acquired and recorded. An MAC address is also called physical address for representing an identifier of each site on the Internet, with a hexadecimal number being adopted, six bytes in total (48-bit). A Bluetooth MAC address of each terminal is unique, and is not the same as that of other terminals, and therefore the acquired and recorded Bluetooth MAC addresses of the Bluetooth devices containing the identifier above in the name of the Bluetooth device and the several terminals needing to establish the WLAN are in one-to-one correspondence. [0042]In Step S103, a Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, the mobile terminal is set as a wireless access point of the WLAN. [0043]Comparison of a character string size is performed on a Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when the comparison is performed, the comparison is begun from a first character in the leftmost of the character string, and if a character size is compared, the comparison is stopped, and the character string with a large character is great; and if the character is the same, the next character continues to be compared in sequence from left to right until the character size is compared, and a character string with a large character is determined to be great. [0044]When the character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the acquired Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request from other terminals with the identifier above contained in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point; and in one optional implementation of the present embodiment, when the character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the acquired Bluetooth MAC addresses, the mobile terminal may further be set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request of other terminals containing the identifier above in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point. [0045]When the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, that is to say, the character string of the Bluetooth MAC address of the mobile terminal is neither the maximum one in all the acquired Bluetooth MAC addresses nor is it the minimum one in all the acquired Bluetooth MAC addresses, it indicates that the maximum or minimum character string is one of the acquired Bluetooth MAC addresses, a terminal corresponding thereto serving as the wireless access point starts a wireless access function, and then the mobile terminal only needs to search for the wireless access point and sends a wireless access request to the searched wireless access point, i.e. being able to join the established WLAN, which is also quite convenient. [0046]Thereby, only via the Bluetooth on the mobile terminal, a user may determine which side serves as the wireless access point and which side serves as a common request access end in several terminals that need to establish the WLAN, so as to establish the WLAN, which is very convenient and quick. [0047]In one optional implementation of the present embodiment, if the mobile terminal serving as the wireless access point starts its own wireless access function, after receiving the wireless access requests from other terminals with the identifier above contained in the name of the Bluetooth device, the mobile terminal also further verifies the wireless access request above, and after the verification performed by the mobile terminal succeeds, a terminal corresponding to the successfully-verified wireless access request is joined in the established WLAN, such that the mobile terminal serving as the wireless access point needing to establish the WLAN can screen other terminals that request to join the WLAN, which is more flexible, ensures that other terminals joining the WLAN are reliable and verified and agreed by the wireless access point, and improves the security of the WLAN. [0048]Through the above-mentioned solution of the present embodiment, Bluetooth MAC addresses of other terminals intending to establish the WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when the character string of the Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start a wireless access function to receive a wireless access request from other terminals so as to establish the WLAN; and since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. [0049]As shown in FIG. 2, a preferred embodiment of the present disclosure provides a mobile terminal for establishing a WLAN. The device comprises: a start and modification component 201, a search and acquisition component 202 and a comparison and execution component 203. [0050]The start and modification component 201 is configured to start Bluetooth when the mobile terminal needs to establish a WLAN with other terminals, and modify a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier. [0051]In the present embodiment, the mobile terminal has a Bluetooth function, and when the mobile terminal needs to establish a WLAN with other terminals, Bluetooth is started, and the name of a Bluetooth device thereof is modified to a character string that contains an identifier, wherein the identifier may be a feature field for setting an identification for identifying several terminals that need to establish the WLAN, so that the interference of other unrelated terminals is avoided. [0052]The search and acquisition component 202 is configured to start Bluetooth search to acquire Bluetooth MAC addresses from other terminals with the identifier contained in the name of the Bluetooth device. [0053]After modifying the name of the Bluetooth device thereof to the character string that contains the identifier, the mobile terminal uses Bluetooth for search, and sets a search condition as containing the identifier above in the name of the Bluetooth device, so as to ensure that the identified terminals are other terminals needing to establish the WLAN, thereby avoiding wasting time searching other unrelated terminals, and saving the time for search. [0054]After other terminals with the identifier above contained in the name of the Bluetooth device are found, the Bluetooth MAC addresses of the Bluetooth devices containing the identifier above in the name of the Bluetooth device are acquired and recorded. An MAC address is also called physical address for representing an identifier of each site on the Internet, with a hexadecimal number being adopted, six bytes in total (48-bit). A Bluetooth MAC address of each terminal is unique, and is not the same as that of other terminals, and therefore the acquired and recorded Bluetooth MAC addresses of the Bluetooth device containing the identifier above in the name of the Bluetooth device and the several terminals needing to establish the WLAN are in one-to-one correspondence. [0055]The comparison and execution component 203 is configured to compare a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, set the mobile terminal as a wireless access point of the WLAN. [0056]Comparison of a character string size is performed on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when the comparison is performed, the comparison is begun from a first character in the leftmost of the character string, and if the character size is compared, the comparison is stopped, and the character string with a large character is great; and if the character is the same, the next character continues to be compared in sequence from left to right until the character size is compared, and a character string with a large character is determined to be great. [0057]When the character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the acquired Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request from other terminals with the identifier above contained in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point; and in one optional implementation of the present embodiment, when the character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the acquired Bluetooth MAC addresses, the mobile terminal may further be set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request from other terminals with the identifier above contained in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point. [0058]When the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, that is, the character string of the Bluetooth MAC address of the mobile terminal is neither the maximum one in all the acquired Bluetooth MAC addresses nor is it the minimum one in all the acquired Bluetooth MAC addresses, it indicates that the maximum or minimum character string is one of the acquired Bluetooth MAC addresses, a terminal corresponding thereto serving as the wireless access point starts a wireless access function, and then the mobile terminal only needs to search for the wireless access point and sends a wireless access request to the found wireless access point, i.e. being able to join the established WLAN, which is also quite convenient. [0059]Thereby, only via the Bluetooth on the mobile terminal, a user may determine which side serves as the wireless access point and which side serves as a common request access end in several terminals that need to establish the WLAN, so as to establish the WLAN, which is very convenient and quick. [0060]In one optional implementation of the present embodiment, if the mobile terminal serving as the wireless access point starts its own wireless access function, after receiving the wireless access request from other terminals with the identifier contained in the name of the Bluetooth device, the mobile terminal also further verifies the wireless access request above, and after the verification performed by the mobile terminal succeeds, a terminal corresponding to the successfully-verified wireless access request is joined in the established WLAN, such that the mobile terminal serving as the wireless access point needing to establish the WLAN can screen other terminals that request to join the WLAN, which is more flexible, ensures that other terminals joining the WLAN are reliable and verified and agreed by the wireless access point, and improves the security of the WLAN. [0061]Through the above-mentioned solution of the present embodiment, since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. [0062]The method for establishing a WLAN by a mobile terminal, and the mobile terminal are provided by the present disclosure, in which Bluetooth MAC addresses of other terminals intending to establish the WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when the character string of the Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start a wireless access function to receive a wireless access request of other terminals so as to establish the WLAN; and since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. [0063]It can be clearly understood by persons skilled in the art that, for the purpose of convenient and brief description, only the foregoing division of the functional units and components is taken as an example for illustration, in actual applications, the foregoing functions can be allocated for being completed by different functional units or components according to the needs, i.e. dividing the internal structure of an apparatus into different functional units or components to complete all or some of the foregoing functions. Various functional units and components in the embodiments may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit, and the foregoing integrated unit may be implemented in a form of hardware, or may also be implemented in a form of a software function unit. In addition, the specific names of all functional units and components are only intended to distinguish between each other, but are not used to limit the protection scope of the present application. For the specific working process of the units and components in the foregoing apparatus, reference may be made to the corresponding process in the foregoing method embodiments, and details are not described herein again. [0064]The foregoing descriptions are only preferable embodiments of the present disclosure, and the patent scope of the present disclosure is not limited thereto. Any equivalent structure or process variation made by using the content of the description and drawings of the present disclosure, or any direct or indirect application of them in other relevant technical fields, shall all fall within the patent protection scope of the present disclosure INDUSTRIAL APPLICABILITY [0065]The above-mentioned technical solution provided by the present disclosure may be applied to the process of establishing a WLAN, in which the technical solution that Bluetooth MAC addresses of other terminals intending to establish the WLAN is acquired by using a character string containing an identifier through Bluetooth search of a mobile terminal, and when a character string of a Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as a wireless access point to start a wireless access function is adopted to receive a wireless access request from other terminals so as to establish the WLAN, thereby improving the quickness and simplicity of establishing a WLAN by a user via a mobile terminal, and greatly facilitating a user to share files by establishing a WLAN.(String), 技术领域 [0001] 本发明涉及移动通信技术领域,尤其涉及一种移动终端建立无线局域网的方法及移动终端。 背景 [0002] 随着移动智能设备的普及,移动终端之间近距离建立无线局域网共享文件的需求越来越大。 在近距离移动终端之间建立WLAN时,需要其中一个移动终端作为无线接入点(Access Point,简称AP),其他移动终端加入该AP,从而实现WLAN 建立通信。 [0003] 然而,在相关技术中,移动终端之间建立WLAN需要用户具有一定的网络技术基础,这给普通用户的操作带来了困难; 另外,不同移动终端的用户在建立WLAN的过程中需要协调确定哪一侧作为无线接入点,哪一侧作为共同请求接入端,操作较为复杂,从而 降低了用户建立WLAN进行文件共享的兴趣,不利于移动终端WLAN相关应用的推广。 概括 [0004] 本发明实施例提供一种移动终端建立WLAN的方法及移动终端,能够更加方便快捷地建立WLAN。 [0005] 本发明实施例提供一种移动终端建立WLAN的方法,包括: [0006] 当移动终端需要与其他终端建立WLAN时,启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串; [0007] 启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙媒体访问控制(Media Access Control,简称MAC)地址; 和 [0008] 分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。 [0009] 优选地,分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点,包括: [0010] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最大的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意蓝牙设备名称中包含标识的其他终端的无线接入请求; 要么 [0011] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最小的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求。 [0012] 优选地,当移动终端的蓝牙MAC地址满足预设条件时,设置移动终端为WLAN的无线接入点还包括: [0013] 通过蓝牙设备名称中包含的标识验证其他终端发送的无线接入请求。 [0014] 优选地,将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较后,该方法还包括: [0015]当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。 [0016] 优选地,启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址,包括: [0017] 启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,并获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。 [0018] 本发明实施例还提供了一种建立WLAN的移动终端,其特征在于,所述装置包括: [0019] 启动及修改模块,用于在移动终端需要与其他终端建立WLAN时启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串; [0020] 搜索获取模块,用于启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址; 和 [0021] 比较执行模块,用于分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为无线接入点 无线局域网。 [0022] 优选地,所述比较执行模块被配置为: [0023] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最大的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求; 要么 [0024] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最小的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求。 [0025] 优选地,所述比较执行模块还用于: [0026] 通过蓝牙设备名称中包含的标识符验证其他终端发送的无线接入请求。 [0027] 优选地,所述比较执行模块还用于: [0028] 当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。 [0029] 优选地,所述搜索获取模块还用于: [0030] 启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。 [0031]本发明实施例提供了一种移动终端建立WLAN的方法及移动终端,通过移动终端的蓝牙搜索,获取其他有意建立WLAN的终端的蓝牙MAC地址。 包含标识的字符串,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最大或最小的一个时,将移动终端设置为无线接入点,启动无线接入功能以 接收其他终端的无线接入请求,建立WLAN; 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性,用户通过建立WLAN共享文件 大大方便了。 附图的简要说明 [0032] 图1示出了根据本发明一个优选实施例的移动终端建立WLAN的方法的流程示意图; 和 [0033] 图2示出了本发明优选实施例中用于建立WLAN的移动终端的结构示意图。 [0034] 为使本发明的技术方案更加清楚明白,下面结合附图对本发明作进一步详细说明。 具体实施方式 [0035] 本发明实施例的方案主要是:根据包含标识的字符串通过移动终端的蓝牙搜索获取其他有意建立WLAN的终端的蓝牙MAC地址,当蓝牙MAC的字符串为 移动终端的地址为所有蓝牙MAC地址中最大或最小的一个,则将移动终端设置为无线接入点,启动无线接入功能,接收其他终端的无线接入请求,建立WLAN。 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性。 [0036] 如图1所示,本发明优选实施例提供了一种移动终端建立WLAN的方法。 [0037] 在步骤S 101 ,当移动终端需要与其他终端建立WLAN时,启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 [0038] 本实施例中,移动终端具有蓝牙功能,当移动终端需要与其他终端建立WLAN时,启动蓝牙,并将其蓝牙设备名称修改为包含标识的字符串, 其中,标识可以是特征字段,用于为需要建立WLAN进行识别的多个终端设置标识,避免其他无关终端的干扰。 [0039] 在步骤S 102 ,开始搜索蓝牙,获取蓝牙设备名称中包含上述标识的其他终端的蓝牙MAC地址。 [0040] 移动终端将自身的蓝牙设备名称修改为包含该标识的字符串后,使用蓝牙进行搜索,将搜索条件设置为蓝牙设备名称中包含上述标识,从而保证 识别出的终端是其他需要建立WLAN的终端,避免了浪费时间搜索其他不相关的终端,节省了搜索的时间。 [0041]在搜索到蓝牙设备名称中包含上述标识的其他终端后,获取并记录蓝牙设备名称中包含上述标识的蓝牙设备的蓝牙MAC地址。 MAC地址也称为物理地址,表示Internet上各个站点的标识,采用十六进制数,共6字节(48位)。 每个终端的蓝牙MAC地址是唯一的,不与其他终端相同,因此获取和记录的蓝牙设备名称中包含上述标识的蓝牙设备的蓝牙MAC地址和需要的多个终端 建立WLAN是一一对应的。 [0042] 在步骤S 103 ,将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。 [0043] 分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串大小的比较,比较时,从字符串最左边的第一个字符开始比较,如果 比较字符大小,停止比较,字符大的字符串为大; 如果字符相同,则继续从左到右依次比较下一个字符,直到比较字符大小,确定字符大的字符串为大。 [0044] 当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最大的一个时,移动终端设置为无线接入点,启动自身的无线接入功能,接收并同意无线接入 其他终端请求蓝牙设备名称中包含上述标识,建立以移动终端为无线接入点的WLAN; 并且在本实施例的一种可选实施方式中,当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最小的一个时,还可以将移动终端设置为无线接入点,启动其无线接入点。 自身的无线接入功能,接收并同意蓝牙设备名称中包含上述标识的其他终端的无线接入请求,从而建立以移动终端为无线接入点的WLAN。 [0045] 当移动终端的蓝牙MAC地址不满足预设条件时,即移动终端的蓝牙MAC地址字符串既不是获取的所有蓝牙MAC地址中最大的,也不是 获取的所有蓝牙MAC地址中最小的一个,表示最大或最小的字符串为获取的蓝牙MAC地址之一,其对应的作为无线接入点的终端启动无线接入功能,则移动终端 只需要搜索无线接入点,向搜索到的无线接入点发送无线接入请求,即可加入已建立的WLAN,也相当方便。 [0046] 从而,用户仅通过移动终端上的蓝牙,就可以在多个需要建立WLAN的终端中确定哪一侧作为无线接入点,哪一侧作为共同请求接入端,从而建立WLAN, 非常方便快捷。 [0047]在本实施例的一种可选实施方式中,如果作为无线接入点的移动终端启动了自身的无线接入功能,则在接收到蓝牙设备名称中包含上述标识的其他终端的无线接入请求后,该移动终端 终端还对上述无线接入请求进行验证,在移动终端验证成功后,将验证成功的无线接入请求对应的终端加入到已建立的WLAN中,使得移动终端作为无线接入点 需要建立WLAN的可以屏蔽其他请求加入WLAN的终端,更加灵活,保证其他加入WLAN的终端是可靠的,并且是经过无线接入点验证同意的,提高了WLAN的安全性。 [0048] 通过本实施例的上述方案,根据包含标识的字符串通过移动终端的蓝牙搜索获取其他有意建立WLAN的终端的蓝牙MAC地址,当该蓝牙MAC地址的字符串 移动终端的MAC地址为所有蓝牙MAC地址中最大或最小的一个,则将移动终端设置为无线接入点,启动无线接入功能,接收其他终端的无线接入请求,建立WLAN。 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性,用户通过建立WLAN共享文件 大大方便了。 [0049] 如图2所示,本发明一个优选实施例提供了一种建立WLAN的移动终端。 该装置包括:启动和修改组件 201 ,一个搜索和获取组件 202 以及比较和执行组件 203 . [0050] 启动和修改组件 201 用于在移动终端需要与其他终端建立WLAN时启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 [0051] 本实施例中,移动终端具有蓝牙功能,当移动终端需要与其他终端建立WLAN时,启动蓝牙,并将其蓝牙设备名称修改为包含标识的字符串, 其中,标识可以是特征字段,用于设置标识,用于标识需要建立WLAN的若干个终端,从而避免其他无关终端的干扰。 [0052] 搜索和获取组件 202 用于启动蓝牙搜索,从其他终端获取蓝牙设备名称中包含的标识的蓝牙MAC地址。 [0053] 移动终端将自身的蓝牙设备名称修改为包含该标识的字符串后,使用蓝牙进行搜索,将搜索条件设置为蓝牙设备名称中包含上述标识,从而保证 识别出的终端是其他需要建立WLAN的终端,避免了浪费时间搜索其他不相关的终端,节省了搜索的时间。 [0054] 在搜索到蓝牙设备名称中包含上述标识的其他终端后,获取并记录蓝牙设备名称中包含上述标识的蓝牙设备的蓝牙MAC地址。 MAC地址也称为物理地址,表示Internet上各个站点的标识,采用十六进制数,共6字节(48位)。 每个终端的蓝牙MAC地址是唯一的,不与其他终端相同,因此获取和记录的蓝牙设备的蓝牙MAC地址包含蓝牙设备名称中的上述标识以及需要的多个终端 建立WLAN是一一对应的。 [0055]比较和执行组件 203 用于分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。 [0056] 分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串大小比较,比较时从字符串最左边的第一个字符开始比较,如果 比较字符大小,停止比较,字符大的字符串为大; 如果字符相同,则继续从左到右依次比较下一个字符,直到比较字符大小,确定字符大的字符串为大。 [0057] 当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最大的一个时,移动终端设置为无线接入点,启动自身的无线接入功能,接收并同意无线接入 其他终端请求蓝牙设备名称中包含上述标识,建立以移动终端为无线接入点的WLAN; 并且在本实施例的一种可选实施方式中,当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最小的一个时,还可以将移动终端设置为无线接入点,启动其无线接入点。 自身的无线接入功能,接收并同意蓝牙设备名称中包含上述标识的其他终端的无线接入请求,从而建立以移动终端为无线接入点的WLAN。 [0058] 当移动终端的蓝牙MAC地址不满足预设条件时,即移动终端的蓝牙MAC地址字符串既不是获取的所有蓝牙MAC地址中最大的,也不是最小的 获取的所有蓝牙MAC地址中的一个,表示最大或最小字符串为获取的蓝牙MAC地址之一,其对应的作为无线接入点的终端启动无线接入功能,则移动终端只需要 搜索无线接入点,向搜索到的无线接入点发送无线接入请求,即可以加入已建立的WLAN,也很方便。 [0059] 从而,用户仅通过移动终端上的蓝牙,就可以在多个需要建立WLAN的终端中确定哪一侧作为无线接入点,哪一侧作为共同请求接入端,从而建立WLAN, 非常方便快捷。 [0060] 在本实施例的一种可选实施方式中,如果作为无线接入点的移动终端开启了自身的无线接入功能,则移动终端在接收到来自其他终端的无线接入请求后,该无线接入请求带有蓝牙设备名称中包含的标识, 还进一步对上述无线接入请求进行验证,在移动终端验证成功后,将验证成功的无线接入请求对应的终端加入到已建立的WLAN中,使得作为无线接入点的移动终端需要 建立WLAN可以屏蔽其他请求加入WLAN的终端,更加灵活,保证其他加入WLAN的终端是可靠的,并且是经过无线接入点验证同意的,提高了WLAN的安全性。 [0061] 通过本实施例的上述方案,由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性, 大大方便了用户通过建立WLAN来共享文件。 [0062]本发明提供一种移动终端建立WLAN的方法及移动终端,通过移动终端的蓝牙搜索,根据包含以下内容的字符串获取其他有意建立WLAN的终端的蓝牙MAC地址。 标识,当移动终端的蓝牙MAC地址字符串为所有蓝牙MAC地址中最大或最小的一个时,将移动终端设置为无线接入点,启动无线接入功能,接收无线信号 其他终端接入请求建立WLAN; 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性,用户通过建立WLAN共享文件 大大方便了。 [0063] 本领域的技术人员可以清楚地了解到,为描述的方便和简洁起见,仅以上述功能单元和组件的划分为例进行说明,在实际应用中,可以将上述功能进行分配 根据需要由不同的功能单元或部件来完成,即将装置的内部结构划分为不同的功能单元或部件来完成上述全部或部分功能。 实施例中的各个功能单元和部件可以集成为一个处理单元,或者各个单元物理上单独存在,或者两个或多个单元集成为一个单元,上述集成的单元可以采用硬件的形式实现 ,或者也可以以软件功能单元的形式实现。 另外,各功能单元和部件的具体名称只是为了相互区分,并不用于限定本申请的保护范围。 上述装置中各单元和部件的具体工作过程可以参见上述方法实施例中的对应过程,在此不再赘述。 [0064] 以上所述仅为本发明的优选实施例而已,并不限于本发明的专利范围。 利用本发明的说明书和附图的内容而作出的等效结构或工艺变化,或者将其直接或间接应用于其他相关技术领域,均属于本发明的专利保护范围 工业实用性 [0065] 本发明提供的上述技术方案可以应用于建立WLAN的过程中,其中通过包含标识符的字符串获取其他有意建立WLAN的终端的蓝牙MAC地址的技术方案 搜索移动终端的蓝牙,当移动终端的蓝牙MAC地址字符串为所有蓝牙MAC地址中最大或最小的一个时,将移动终端设置为无线接入点,启动无线接入功能 本发明通过接收其他终端的无线接入请求建立WLAN,提高了用户通过移动终端建立WLAN的快捷性和简便性,大大方便了用户通过建立WLAN共享文件。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104427579A(String), KR1020160045772A(String), US20160212572A1(String), US9781547B2(String), WO2014169633A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104427579A(String), KR1020160045772A(String), US20160212572A1(String), US9781547B2(String), WO2014169633A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9781547B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104427579A(String), KR1020160045772A(String), US20160212572A1(String), US9781547B2(String), WO2014169633A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270650(Integer), CN104427579A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270650(Integer), KR1020160045772A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270650(Integer), US20160212572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270650(Integer), US9781547B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270650(Integer), WO2014169633A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9781547B2(String), US9781547B2(String), 1506960000(Integer), 270650(Integer), 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184967(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184967(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184967(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184967(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.690 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.690 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权 | 权利转移(String), 3(Integer), 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.716 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8825010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.720 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.720 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Cell locking method for mobile terminal and mobile terminal capable of locking cell(String), 移动终端的小区锁定方法及能够锁定小区的移动终端(String), US8825010B2(String), A cell locking method for a mobile terminal and a mobile terminal capable of locking a cell are disclosed in the present invention. The method includes: the mobile terminal acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell; judging whether the SID, NID, BASE ID and PN are already stored in a database of the mobile terminal, if yes, then setting the mobile terminal to a normal status; judging whether the SID, the NID, and the PN are already stored in the database of the mobile terminal and the database is not full, or whether the BASE ID and PN are already stored in the database of the mobile terminal, if yes, then transferring to D; and D. writing the SID, NID, BASE ID and PN into the database of the mobile terminal.(String), 本发明公开了一种移动终端的小区锁定方法及能够锁定小区的移动终端。 该方法包括:移动终端获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN)。 判断SID、NID、BASE ID和PN是否已经存储在移动终端的数据库中,如果是,则将移动终端设置为正常状态。 判断SID、NID、PN是否已经存入移动终端数据库且数据库未满,或者BASE ID和PN是否已经存入移动终端数据库,如果是,则 转移到 D; D.将SID、NID、BASE ID和PN写入移动终端的数据库。(String), US13/501299(String), 1282665600(Integer), US8825010B2(String), 1409587200(Integer), 1409587200(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 12(Integer), CN100428820C | CN101072439A | CN101668285A | US20040048597A1 | US20060217130A1 | US20080287140A1 | US20090098873A1 | US20090129327A1 | US20090135731A1 | US20100002611A1 | US20100279705A1 | US8054803B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.730 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184968(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.735 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\3eca34d62eff42c59bc55b197c0daca4.png(String), 184968(Integer), 3eca34d62eff42c59bc55b197c0daca4.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.746 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.746 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Cell locking method for mobile terminal and mobile terminal capable of locking cell(String), 移动终端的小区锁定方法及能够锁定小区的移动终端(String), US8825010B2(String), A cell locking method for a mobile terminal and a mobile terminal capable of locking a cell are disclosed in the present invention. The method includes: the mobile terminal acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell; judging whether the SID, NID, BASE ID and PN are already stored in a database of the mobile terminal, if yes, then setting the mobile terminal to a normal status; judging whether the SID, the NID, and the PN are already stored in the database of the mobile terminal and the database is not full, or whether the BASE ID and PN are already stored in the database of the mobile terminal, if yes, then transferring to D; and D. writing the SID, NID, BASE ID and PN into the database of the mobile terminal.(String), 本发明公开了一种移动终端的小区锁定方法及能够锁定小区的移动终端。 该方法包括:移动终端获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN)。 判断SID、NID、BASE ID和PN是否已经存储在移动终端的数据库中,如果是,则将移动终端设置为正常状态。 判断SID、NID、PN是否已经存入移动终端数据库且数据库未满,或者BASE ID和PN是否已经存入移动终端数据库,如果是,则 转移到 D; D.将SID、NID、BASE ID和PN写入移动终端的数据库。(String), US13/501299(String), 1282665600(Integer), US8825010B2(String), 1409587200(Integer), 1409587200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 12(Integer), CN100428820C | CN101072439A | CN101668285A | US20040048597A1 | US20060217130A1 | US20080287140A1 | US20090098873A1 | US20090129327A1 | US20090135731A1 | US20100002611A1 | US20100279705A1 | US8054803B2(String), \20230420\3eca34d62eff42c59bc55b197c0daca4.png(String), 14(Integer), 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.758 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 1. A cell locking method for a mobile terminal, wherein said method comprises:searching, by the mobile terminal, a current cell at a current location to acquire a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of said cell;judging, by the mobile terminal, whether said SID, said NID, said BASE ID and said PN of the current cell are already stored in a database of said mobile terminal;when said SID, said NID, said BASE ID and said PN of the current cell are all already stored in the database of said mobile terminal, setting said mobile terminal to a normal status for normal operation;when said SID, said NID and said PN are already stored in the database of said mobile terminal, but said BASE ID is not stored in the database and said database is not full, writing said BASE ID, with said SID, said NID and said PN, into the database, and setting said mobile terminal into the normal status for normal operation;when said BASE ID and said PN are already stored in the database of said mobile terminal, but said SID and said NID are not stored in the database, writing said SID and said NID, with said BASE ID and said PN, into the database, and setting said mobile terminal into the normal status for normal operation;for any other judgment results, setting said mobile terminal to a lock status for not normal operation.(String), 1.根据权利要求10所述的移动终端的小区锁定方法,其中在将移动终端设置为锁定状态时,该方法还包括:若该移动终端响应或发起业务连接,则禁止该移动终端访问或响应系统,并向系统返回指定的错误码。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 2. The cell locking method for a mobile terminal according to claim 1, wherein before the step of searching, by the mobile terminal, a current cell at a current location, the method further comprises an initialization procedure, and said initialization procedure comprises:setting a number N of limited dials;limiting a maximum number of BASE IDs simultaneously supported by the mobile terminal of a user;after the user acquiring the mobile terminal dials a (N+1)th non-emergent number, acquiring and storing, by the mobile terminal, said SID, said NID, said BASE ID and said PN in a system parameter message and a PN sequence set stored in said mobile terminal according to a current network signaling.(String), 12.根据权利要求1所述的移动终端的小区锁定方法,其中在将移动终端设置为锁定状态时,该方法还包括:若该移动终端响应或发起业务连接,则禁止该移动终端访问或响应系统,并向系统返回指定的错误码。13、一种可锁定小区的移动终端,其中所述移动终端包括当前小区参数获取单元、数据存储单元、参数比较单元、数据库写入单元和状态设置单元,其中当前小区参数获取单元,用于获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASEID)和伪随机数(PN);数据存储单元,用于存储移动终端的数据库,数据库包括SID、NID、BASEID和PN参数。参数比较单元,用于将当前小区参数获取单元获取的SID、NID、BASEID和PN与存储在所述数据存储单元中的参数通过以下方式进行比较:当当前小区的所述SID、所述NID、所述BASEID和所述PN均已存储在所述移动终端的数据库中时,向状态设置单元发送第一比较结果,当所述SID、所述NID和所述PN已经存储在所述移动终端的数据库中,但是所述BASEID未存储在数据库中且所述数据库未满时,向数据库写入单元发送第二比较结果,以及状态设置单元,当所述BASEID和所述PN已存储在所述移动终端的数据库中,但所述SID和所述NID未存储在数据库中时,向数据库写入单元和状态设置单元发送第三比较结果,以及当比较结果不满足上述任一比较结果时,向状态设置单元发送第四比较结果;数据库写入单元,用于在接收到第二比对结果时,将所述BASEID、所述SID、所述NID和所述PN写入所述数据库。当接收到第三比对结果时,将所述SID和所述NID与所述BASEID和所述PN一起写入数据库;状态设置单元,用于在接收到第一比较结果、第二比较结果或第三比较结果时,将所述移动终端设置为正常状态,进行正常工作。当接收到第四比较结果时,将所述移动终端设置为非正常操作的锁定状态。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 3. The cell locking method for a mobile terminal according to claim 2, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 14.根据权利要求13所述的移动终端,其中所述移动终端还包括解锁单元,所述解锁单元与所述数据存储单元连接,用于根据接收到的解锁指令或解锁短信清空所述数据库中的SID、NID、BASEID和PN,并重置锁定的小区配置。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 4. The cell locking method for a mobile terminal according to claim 2, wherein said PN sequence set comprises an active set, a candidate set and a neighbor set.(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 5. The cell locking method for a mobile terminal according to claim 4, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 6. The cell locking method for a mobile terminal according to claim 1, wherein after the mobile terminal is set to the lock status, the method further comprises an unlock procedure, and said unlock procedure comprises:determining, by an operator, whether identity and requirement of said user is legal according to a cell unlock request of the user;when the identity and requirement of said user is legal, sending, by the operator, an unlock instruction or unlock short message to the user terminal;after receiving said unlock instruction or said unlock short message, emptying, by the mobile terminal, the SID, NID, BASE ID and PN stored in said database and resetting locked cell configuration.(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 7. The cell locking method for a mobile terminal according to claim 6, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 8. The cell locking method for a mobile terminal according to claim 6, wherein when the cell unlock request of said user is sent to the operator by dialing a specified service number, the operator sends said unlock short message to the user terminal.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 9. The cell locking method for a mobile terminal according to claim 8, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 10. The cell locking method for a mobile terminal according to claim 6, wherein when the cell unlock request of said user is sent to the operator by sending said user terminal to the operator, the operator sends said unlock instruction to the user terminal by using a tool.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 11. The cell locking method for a mobile terminal according to claim 10, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 12. The cell locking method for a mobile terminal according to claim 1, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 13. A mobile terminal capable of locking a cell, wherein said mobile terminal comprises a current cell parameter acquisition unit, a data storage unit, a parameter comparison unit, a database writing-in unit and a status setting unit, whereinthe current cell parameter acquisition unit is used for acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell;the data storage unit is used for storing a database of the mobile terminal, wherein, the database includes SID, NID, BASE ID and PN parameters;the parameter comparison unit is used for comparing the SID, NID, BASE ID and PN acquired by the current cell parameter acquisition unit with the parameters stored in said data storage unit by the following ways:when said SID, said NID, said BASE ID and said PN of the current cell are all already stored in the database of said mobile terminal, sending a first comparison result to the status setting unit,when said SID, said NID and said PN are already stored in the database of said mobile terminal, but said BASE ID is not stored in the database and said database is not full, sending a second comparison result to the database writing-in unit and the status setting unit,when said BASE ID and said PN are already stored in the database of said mobile terminal, but said SID and said NID are not stored in the database, sending a third comparison result to the database writing-in unit and the status setting unit, andwhen the comparison result does not meet any one of the above comparison results, sending a fourth comparison result to the status setting unit;the database writing-in unit is used for: when receiving the second comparison result, writing said BASE ID, with said SID, said NID and said PN, into said database; when receiving the third comparison result, writing said SID and said NID, with said BASE ID and said PN, into the database;the status setting unit is used for: when receiving the first comparison result, the second comparison result, or the third comparison result, setting said mobile terminal to a normal status for normal operation; when receiving the fourth comparison result, setting said mobile terminal to a lock status for not normal operation.(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184968(Integer), 14. The mobile terminal according to claim 13, wherein said mobile terminal further comprises an unlock unit which is connected to said data storage unit and is used for emptying the SID, NID, BASE ID and PN in said database according to a received unlock instruction or unlock short message and resetting the locked cell configuration.(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.879 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.879 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.880 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.880 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.880 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184968(Integer), TECHNICAL FIELD [0001]The present invention relates to the technical field of wireless communication, and in particularly, to a cell locking method for a mobile terminal and a mobile terminal capable of locking a cell. BACKGROUND OF THE RELATED ART [0002]With the rapid development of the mobile communication technology, the mobile terminal also exhibits diversified development, and the requirement on limiting the mobility of the mobile terminal also appears, i.e. limit the mobile terminal to only work in a specified cell. Currently, there are two common cell locking methods for the mobile terminal. [0003]The first method is to lock the base station ID and system ID. In this method, the number of base stations which can be locked by the mobile terminal is firstly determined, each time the mobile terminal searches out a new base station, then the mobile terminal adds the base station to a base station list, and if the number of the base stations in the base station list reaches a specified number, then the mobile station stops updating the base station list; after having been registered into the base station, the terminal firstly compares to determine whether ID of this base station is already in the base station list, if it is contained in the base station list, then the terminal provides normal service, otherwise the terminal provides limited service. [0004]The second method is to establish duplex channels between the system side and the mobile terminal, in which the system side issues a control command to the mobile terminal so as to configure the subscription list of the terminal, and the mobile terminal continuously monitors the system, reports information according to the requirements, and determines whether or not to provide normal service. [0005]However, during implementation of the present invention, the inventors have found out that the above currently available cell locking methods for a mobile terminal has the following defects: first, the base station has respiratory effect, which means that, in the Code Division Multiple Access (CDMA) system, when the interference signal in a cell is very strong, the actual effective coverage area of the base station will be reduced; and when the interference signal in a cell is very weak, the actual effective coverage area of the base station will be increased. In a word, the respiratory effect exhibits that the coverage radius constricts as the number of users increases. The main reason leading to the respiratory effect is that the CDMA system is a self-interference system, where the increasing of user leads to the increasing of interference and affects the coverage. Due to the existence of respiratory effect, after the signal coverage of the base station becomes larger, the terminal located at the coverage boundary of the base station will be in the subscribed cell, but when the signal coverage of the base station becomes smaller, the terminal will be out of the coverage of the subscribed cell, then the terminal will be in a lock status, thus the service provided by the terminal is limited, and such phenomenon is called ping-pong effect. Secondly, in the abovementioned methods in the related art, although a plurality of base stations can be locked, there is no association among the locked base stations, and it is only judged whether the base station currently providing the service is in the subscribed base station list, if the current base station is not in the subscribed base station list and the number (preset in the terminal in advance) of the subscribed base stations does not reach the specified upper limit, then the base station currently providing the service is added into the subscription list and provides normal service, or the base station currently providing the service is in the subscribed base station list, then normal service will be provided; and if the current base station is not in the subscription list and the subscription list is full, then the terminal only provides limited service. Because there is no restriction relationship among the locked base stations, it leads to that these base stations may form individual islands, which conflicts with the object of locking a cell. SUMMARY OF THE INVENTION [0006]The problem to be solved by the present invention is to provide a cell locking method for a mobile terminal and a mobile terminal capable of locking a cell so as to overcome the defects of the ping-pong effect and island effect in related art. [0007]In order to reach the abovementioned object, the technical solution of the present invention provides a cell locking method for a mobile terminal, and said method includes the steps of: step A. the mobile terminal searching a cell at a current location to acquire a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of the cell; step B. judging whether said SID, said NID, said BASE ID and said PN are already stored in a database of said mobile terminal, if yes, then setting the mobile terminal to a normal status and transferring to step E, otherwise transferring to step C; step C. judging whether said SID, said NID, and said PN are already stored in the database station of said mobile terminal and said database is not full, or said BASE ID and said PN are already stored in the database of said mobile terminal, if yes, then transferring to step D, otherwise setting said mobile terminal to a lock status and transferring to step E; step D. writing said SID, said NID, said BASE ID and said PN into the database of said mobile terminal and setting said mobile terminal into a normal status and transferring to step E; and step E. finishing the lock procedure. [0008]Furthermore, before step A, the method further includes an initialization procedure, and said initialization procedure includes: setting the number N of limited dials; limiting the maximum number of BASE ID simultaneously supported by a user terminal; said user terminal, after a user acquiring the user terminal dials a (N+1)th non-emergent number, acquiring and storing said SID, said NID, said BASE ID and said PN in a system parameter message and a PN sequence set stored in said user terminal according to a current network signaling. [0009]Furthermore, said PN sequence set includes an active set, a candidate set and a neighbor set. [0010]Furthermore, after the mobile terminal is set into the lock status, the method further includes an unlock procedure F, and said F includes: step F1. an operator determining whether identity and requirement of said user is legal according to a cell unlock request of the user, if yes, then transferring to step F2, otherwise ending; step F2. the operator sending an unlock instruction or unlock short message to the user terminal; step F3. after receiving said unlock instruction or said unlock short message, the user terminal emptying the SID, NID, BASE ID and PN stored in said database and resetting locked cell configuration. [0011]Furthermore, when the cell unlock request of said user is sent to the operator by dialing a specified service number, the operator sends said unlock short message to the user terminal. [0012]Furthermore, when the cell unlock request of said user is sent to the operator by sending said user terminal to the operator, the operator sends said unlock instruction to the user terminal by using a tool. [0013]Furthermore, when setting the mobile terminal to the lock status, the method further comprises: if said user terminal responds or initiates a service connection, then forbidding said user terminal to access or to respond to the system and sending back a specified error code to the system. [0014]The technical solution of the present invention also provides a mobile terminal capable of locking a cell, and said mobile terminal includes a current cell parameter acquisition unit, a data storage unit, a parameter comparison unit, a database writing-in unit and a status setting unit; wherein [0015]the current cell parameter acquisition unit is used for acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell; the parameter comparison unit is used for comparing the parameter acquired by the parameter acquiring unit of said current cell with a parameter stored in said data storage unit; the database writing-in unit is used for writing data into said database according to the comparison result of said parameter comparison unit; and the status setting unit is used for setting the status of said mobile terminal according to the comparison result of said parameter comparison unit. [0016]Furthermore, said database writing unit is further used for writing said SID, said NID, said BASE ID and said PN into the database of said mobile terminal when said comparison result is that said SID, said NID and said PN acquired by the current cell parameter acquisition unit are the same as the SID, NID and PN stored in said database and said database is not full, or when said BASE ID and said PN acquired by the current cell parameter acquisition unit are the same as the BASE ID and PN stored in said database. [0017]Furthermore, said status setting unit is further used for setting said mobile terminal into the normal status when said comparison result is that said SID, said NID, said BASE ID and said PN acquired by the current cell parameter acquisition unit are the same as the SID, NID, BASE ID and PN stored in said database, or when said SID, said NID and said PN acquired by the current cell parameter acquisition unit are the same as the SID, NID and PN stored in said database and said database is not full, or when said BASE ID and said PN acquired by the current cell parameter acquisition unit are the same as the BASE ID and PN stored in said database, otherwise setting said mobile terminal into the lock status. [0018]Furthermore, said mobile terminal further includes an unlock unit which is connected to said data storage unit and is used for emptying the SID, NID, BASE ID and PN in said database according to a received unlock instruction or unlock short message and reset locked cell configuration The beneficial effects of the present invention compared with related art are as follows: [0019]by the present invention, the operating costs is reduced without adding or modifying the configuration of the network side; in addition, by the present invention, a certain cell can be strictly locked, which solves the ping-pong effect generated by spasmodically locking a certain cell at some special locations by the terminal due to the network respiratory effect, and also will not lead to island effect. BRIEF DESCRIPTION OF DRAWINGS [0020]FIG. 1 is a flowchart of a cell locking method for a mobile terminal in an example of the present invention. [0021]FIG. 2 is a flowchart of an initialization procedure in an example of the present invention. [0022]FIG. 3 is a flowchart of unlock of an example of the present invention. [0023]FIG. 4 is a flowchart of a mobile terminal responding to a system after locking a cell using the present invention. [0024]FIG. 5 is a flowchart of a mobile terminal accessing a system after locking a cell using the present invention. [0025]FIG. 6 is a schematic diagram of a mobile terminal capable of locking a cell in an example of the present invention. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0026]Hereinafter, the particular embodiments of the present invention will be further described in detail in conjunction with the accompanying drawings and examples. The following examples are used for describing the present invention, but not for limiting the scope of the present invention. [0027]In the examples of the present invention, the cells in a CDMA network are defined as a set P of several {SID, NID, BASE ID, PN}, and it can be known from the network characteristics that all the SIDs and NIDs are the same in the same cell, a set B of the BASE ID is the base station registered by the current terminal and the neighbor base station, and the BASE ID of the current base station can be acquired from a system parameter message sent by the base station; and the PN set of the cell where the terminal is located is S. Such a cell structure is for adapting to the respiratory effect of the CDMA network, and avoiding the ping-pong effect caused by the respiratory effect, and at the same time it also can avoid the island effect caused by only locking the BASE ID in the conventional cell locking solution. In this case, said SID is the abbreviation of system identification which indicates the System ID; said NID is the abbreviation of network identification which indicates the network ID; said BASE ID indicates the base station ID; and said PN is the abbreviation of pseudo-random number which indicates pseudo-random code. Example 1 [0028]A cell locking method for a mobile terminal in the example of the present invention is as shown in FIG. 1 and includes the steps as follows. [0029]Step s101. The mobile terminal searches a cell at a current location, and the mobile terminal, when receiving a system parameter message, reads Pj={SIDj, NIDj, BASE IDj, PNj} from the system parameter message. [0030]Step s102. It is judged whether Pj belongs to P; if yes, then transfer to step s107, otherwise transfer to step s103. [0031]Step s103. It is judged whether SIDj=SID, NIDj=NID, PNjεS, BASE IDj!εB, and the number of elements in B is less than the maximum number M of the BASE ID simultaneously supported by the user terminal, if yes, then transfer to step s104, otherwise transfer to step s105. [0032]Step s104. Pj is added to the set P, i.e. P+={Pj}; BASE IDj is added to set B, i.e. B+={BASE IDj}; B and P are stored, and transfer to step s107. [0033]Step s105. It is judged whether BASE IDjεB, PNjεS, and Pj!εP, if yes, then transfer to step s106, otherwise transfer to step s108. [0034]Step s106. Pj is added to set P, i.e. P+={Pj}, then P is stored and transfer to step s107. [0035]Step s107. The mobile terminal is set to a normal status and transfer to step s109. [0036]Step s108. The mobile terminal is set to a lock status and transfer to step s109. [0037]Step s109. The lock procedure is ended. Example 2 [0038]Before example 1, the present invention further includes an initialization procedure, and the flow of the initialization procedure in the example of the present invention is as shown in FIG. 2 and includes the following steps. [0039]Step s201, the number of limited dials N which is 5 in this example is set. [0040]Step s202, the user, after having acquired the user terminal, dials the telephone. [0041]Step s203, it is judged whether the number of times of non-emergent number dialed by the user is greater than N; if yes, then transfer to step s204, otherwise transfer to step s202. [0042]Step s204, the user terminal acquires Pi={SID, NID, BASE ID, PN} in the system parameter message sent by the current base station and the PN set S maintained by the terminal, wherein the PN sequence set S includes an active set, a candidate set and a neighbor set. [0043]Step s205, the user terminal initializes the set P={Pi}, B={BASE ID}, and automatically stores S, P, B, SID and NID. Example 3 [0044]When the mobile terminal is in the lock status, the user can alter the subscribed cell by way of an unlock procedure, and an unlock procedure in the example of the present invention is as shown in FIG. 3, which includes the steps as follows. [0045]Step s301, the user requests a cell unlock. [0046]Herein, the user can request cell unlock toward the operator by two manners, among which one manner is to send the request to the operator by dialing a specified service number, another manner is to send the user terminal to the operator. [0047]Step s302, the operator determines whether the identity and the requirement of the user is legal according to the cell unlock request of the user, if yes, then transfer to step s303, otherwise end. [0048]Step s303, when the cell unlock request of the user is sent to the operator by dialing a specified service number, the operator sends an unlock short message to the user terminal; and when the cell unlock request of the user is sent to the operator by sending the user terminal thereto, the operator sends an unlock instruction to the user terminal by using a tool. [0049]Step s304, after having received the unlock instruction or unlock short message, the user terminal empties the SID, NID, BASE ID and PN in the database and resets the locked cell configuration. [0050]After having reset the locked cell configuration, the user terminal restarts the cell locking procedure. [0051]Herein, after the mobile terminal locks a cell using the present invention, its procedure of responding to the system is as shown in FIG. 4, and its procedure of accessing the system is as shown in FIG. 5. When the mobile terminal responds or initiates a service connection, the status of the current mobile terminal will be first checked. If the mobile terminal is in the normal status, then the terminal normally accesses or responds to the system. If the mobile terminal is in the lock status, then it is checked whether the user alters the subscribed cell by way of unlock procedures such as an Over The Air Parameter Administration (OTAPA), an unlock short message or dialing a specified number, etc., if yes, then unlock is performed and the normally access or responding to the system is performed, otherwise, a specified error code is sent back to the system and the access or respond to the system is forbidden. [0052]The schematic diagram of a mobile terminal capable of locking a cell in the example of the present invention is as shown in FIG. 6, in which the mobile terminal includes a current cell parameter acquisition unit 61, a parameter comparison unit 62, a status setting unit 63, a database writing-in unit 64, a data storage unit 65 and an unlock unit 66. Among them, the parameter comparison unit 62 is respectively connected to the current parameter acquisition unit 61, status setting unit 63, database writing-in unit 64 and data storage unit 65; and the data storage unit 65 is respectively connected to the database writing-in unit 64 and unlock unit 66. [0053]The current cell parameter acquisition unit 61 is used for acquiring the SID, NID, BASE ID and PN of the current cell. [0054]The data storage unit 65 is used for storing the database of the mobile terminal, wherein, the database includes the SID, NID, BASE ID and PN parameters in the database. [0055]The parameter comparison unit 62 is used for comparing the parameter acquired by parameter acquiring unit 61 of the current cell with the parameter stored in data storage unit 65. [0056]The database station writing-in unit 64 is used for writing data into the database according to the comparison result of the parameter comparison unit 62; writing the SID, NID, BASE ID and PN into the database of the mobile terminal when the comparison result is that the SID, NID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID and PN stored in the database and the database is not full, or when the BASE ID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, the BASE ID and PN stored in the database. [0057]The status setting unit 63 is used for setting the status of the mobile terminal according to the comparison result of parameter comparison unit 62; setting the mobile terminal into a normal status when the comparison result is that the SID, NID, BASE ID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID, BASE ID and PN stored in the database, or when the SID, NID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID and PN stored in the database and the database is not full, or when the BASE ID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID and PN stored in PN database, otherwise, setting the mobile terminal to a lock status. [0058]The unlock unit 66 is used for emptying the SID, NID, BASE ID and PN in the database and resetting the locked cell configuration according to the received unlock instruction or unlock short message. [0059]When using the present invention, the operating costs can be reduced without adding or modifying the configuration of the network side; and the present invention can strictly lock a certain cell, which solves the ping-pong effect generated by spasmodically locking a certain cell at some special location by the terminal due to the network respiratory effect, and also will not lead to island effect. [0060]What is described above is merely preferred embodiments of the present invention, and it should be pointed out that several improvements and modifications can also be made without departing from the technical principle of the present invention for those skilled in the art, and these improvements and modifications should also be regarded as the scope of protection of the present invention.(String), 技术领域 [0001] 本发明涉及无线通信技术领域,尤其涉及一种移动终端的小区锁定方法和能够锁定小区的移动终端。 背景技术 [0002] 随着移动通信技术的飞速发展,移动终端也呈现多元化发展,也出现了限制移动终端移动性的要求,即限制移动终端只能工作在特定小区。 目前,移动终端常用的小区锁定方式有两种。 [0003] 第一种方法是锁定基站ID和系统ID。 该方法首先确定移动终端可以锁定的基站数量,每次移动终端搜索到新的基站,移动终端将该基站添加到基站列表中,如果 基站列表中的基站数量达到指定数量,则移动台停止更新基站列表。 终端注册到基站后,首先比较判断该基站的ID是否已经在基站列表中,如果在基站列表中,则终端提供正常服务,否则终端提供 有限的服务。 [0004] 第二种方法是在系统侧和移动终端之间建立双工信道,系统侧向移动终端下发控制命令,配置终端的订阅列表,移动终端持续监控系统, 根据要求上报信息,确定是否提供正常服务。 [0005] 但是,发明人在实施本发明的过程中发现,上述现有的移动终端小区锁定方法存在以下缺陷:首先,基站具有呼吸效应,也就是说,在码分多址中, (CDMA)系统,当小区内的干扰信号很强时,基站的实际有效覆盖范围会缩小; 当小区内的干扰信号很弱时,会增加基站的实际有效覆盖范围。 总之,呼吸效应表现为覆盖半径随着用户数量的增加而缩小。 导致呼吸效应的主要原因是CDMA系统是一个自干扰系统,用户的增加导致干扰的增加,影响覆盖。 由于呼吸效应的存在,当基站的信号覆盖范围变大后,位于基站覆盖边界的终端会在签约小区内,但当基站的信号覆盖范围变小时, 终端将超出订阅小区的覆盖范围,终端将处于锁定状态,从而终端提供的服务受到限制,这种现象称为乒乓效应。 其次,在上述相关技术的方法中,虽然可以锁定多个基站,但是锁定的基站之间没有关联,仅判断当前提供服务的基站是否在签约基站中。 列表,如果当前基站不在订阅基站列表中,且订阅基站数量(终端预先设置)未达到指定上限,则将当前提供服务的基站加入 订阅列表并提供正常服务,或当前提供服务的基站在订阅基站列表中,则提供正常服务; 如果当前基站不在订阅列表中且订阅列表已满,则终端仅提供有限服务。 由于锁定的基站之间没有限制关系,导致这些基站可能形成单独的孤岛,这与锁定小区的目的相冲突。 发明内容 [0006]本发明要解决的问题是提供一种移动终端的小区锁定方法及能够锁定小区的移动终端,以克服相关技术中存在的乒乓效应和孤岛效应的缺陷。 [0007] 为了达到上述目的,本发明的技术方案提供了一种移动终端的小区锁定方法,该方法包括以下步骤: 步骤A、移动终端搜索当前位置的小区以获取系统 小区标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN); 步骤B、判断所述SID、所述NID、所述BASE ID和所述PN是否已经存储在所述移动终端的数据库中,如果是,则将移动终端设置为正常状态并转至步骤E,否则转至步骤 C; 步骤C.判断所述SID、所述NID和所述PN是否已经存储在所述移动终端的数据库站中并且所述数据库未满,或者所述BASE ID和所述PN已经存储在所述移动终端的数据库中, 如果是,则转入步骤D,否则将所述移动终端设置为锁定状态,转入步骤E。 步骤D、将所述SID、所述NID、所述BASE ID和所述PN写入所述移动终端的数据库中,并将所述移动终端设置为正常状态,转入步骤E。 步骤E,完成锁定程序。 [0008] 进一步地,在步骤A之前,该方法还包括初始化过程,所述初始化过程包括: 设置受限拨号数N; 限制用户终端同时支持的BASE ID的最大数量; 所述用户终端,在用户获取用户终端拨打第(N+1)个非紧急号码后,获取并存储所述SID、所述NID、所述BASE ID和所述PN在系统参数消息和存储的PN序列集合中 在所述用户终端中根据当前网络信令。 [0009] 进一步地,所述PN序列集包括激活集、候选集和邻居集。 [0010] 进一步地,在移动终端进入锁定状态后,该方法还包括解锁流程F,所述F包括: 步骤F 1 . 运营商根据用户的小区解锁请求判断所述用户的身份和要求是否合法,如果是,则转入步骤F 2 , 否则结束; 步骤 F 2 . 运营商向用户终端发送解锁指令或解锁短信; 步骤 F 3 . 用户终端接收到所述解锁指令或所述解锁短信后,清空所述数据库中存储的SID、NID、BASE ID和PN,并重置锁定小区配置。 [0011] 进一步地,当所述用户的小区解锁请求通过拨打指定的业务号码发送给运营商时,运营商向用户终端发送所述解锁短信。 [0012] 进一步地,当通过向运营商发送所述用户终端向运营商发送所述用户的小区解锁请求时,运营商通过工具向用户终端发送所述解锁指令。 [0013] 进一步地,在将移动终端设置为锁定状态时,该方法还包括:若所述用户终端响应或发起业务连接,则禁止所述用户终端访问或响应系统,并返回指定的错误码给所述用户终端。 系统。 [0014] 本发明的技术方案还提供了一种能够锁定小区的移动终端,所述移动终端包括当前小区参数获取单元、数据存储单元、参数比较单元、数据库写入单元和状态设置。 单元; 其中 [0015]当前小区参数获取单元,用于获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN)。 参数比较单元,用于将所述当前小区的参数获取单元获取的参数与所述数据存储单元中存储的参数进行比较。 数据库写入单元,用于根据所述参数比较单元的比较结果将数据写入所述数据库; 状态设置单元,用于根据所述参数比较单元的比较结果设置所述移动终端的状态。 [0016] 进一步地,所述数据库写入单元还用于当所述比对结果为当前小区参数获取的所述SID、所述NID和所述PN时,将所述SID、所述NID、所述BASE ID和所述PN写入所述移动终端的数据库中。 获取单元与所述数据库中存储的SID、NID和PN相同且所述数据库未满,或者当当前小区参数获取单元获取的所述BASE ID和所述PN与存储在其中的BASE ID和PN相同时 说数据库。 [0017] 进一步地,所述状态设置单元还用于当所述比较结果为所述当前小区参数获取单元获取的所述SID、所述NID、所述BASE ID和所述PN与SID相同时,将所述移动终端设置为正常状态。 ,所述数据库中存储的NID、BASE ID和PN,或者当所述SID时,当前小区参数获取单元获取的所述NID和所述PN与所述数据库中存储的SID、NID和PN相同且所述数据库未满 ,或者当当前小区参数获取单元获取的所述BASE ID和所述PN与所述数据库中存储的BASE ID和PN相同时,否则将所述移动终端设置为锁定状态。 [0018] 进一步地,所述移动终端还包括解锁单元,与所述数据存储单元连接,用于根据接收到的解锁指令或解锁短信清空所述数据库中的SID、NID、BASE ID和PN,并重置锁定小区配置。 本发明与现有技术相比的有益效果如下: [0019] 通过本发明,在不增加或修改网络侧配置的情况下,降低了运营成本。 另外,通过本发明,可以对某个小区进行严格锁定,解决了终端由于网络呼吸效应在某些特殊位置痉挛锁定某个小区产生的乒乓效应,也不会导致 孤岛效应。 附图说明 [0020] 图1为本发明实施例中移动终端的小区锁定方法的流程图。 [0021] 图2是本发明示例中的初始化过程的流程图。 [0022] 图3为本发明实施例解锁流程图。 [0023] 图4是使用本发明的移动终端在锁定小区后响应系统的流程图。 [0024] 图5为本发明移动终端锁定小区后接入系统的流程图。 [0025] 图6为本发明实施例移动终端可锁定小区的示意图。 本发明的优选实施方案 [0026] 下面结合附图和实施例对本发明的具体实施方式作进一步的详细说明。 以下实施例用于描述本发明,但不用于限制本发明的范围。 [0027]在本发明实施例中,将CDMA网络中的小区定义为若干个{SID, NID, BASE ID, PN}的集合P,从网络特性可知,所有的SID和NID都是 同一个小区,BASE ID的集合B为当前终端和邻居基站注册的基站,当前基站的BASE ID可以从基站发送的系统参数消息中获取 ; 终端所在小区的PN集合为S。这样的小区结构是为了适应CDMA网络的呼吸效应,避免呼吸效应引起的乒乓效应,同时 也可以避免传统小区锁定方案中只锁定BASE ID所带来的孤岛效应。 在这种情况下,SID是系统标识的缩写,表示系统ID; 所述NID是网络标识的缩写,表示网络ID; 所述BASE ID表示基站ID; 所述PN为pseudo-random number的缩写,表示伪随机码。 示例 1 [0028] 本发明实施例的移动终端的小区锁定方法如图1所示,包括以下步骤。 [0029] 脚步 101 . 移动终端搜索当前位置的小区,移动终端在接收到系统参数消息时,从系统参数消息中读取Pj={SIDj,NIDj,BASE IDj,PNj}。 [0030] 脚步 102 . 判断Pj是否属于P; 如果是,则转移到步骤s 107 , 否则转到步骤 s 103 . [0031] 脚步 103 . 判断是否SIDj=SID,NIDj=NID,PNjεS,BASE IDj!εB,且B中的元素个数小于用户终端同时支持的BASE ID的最大个数M,如果是,则转入 脚步 104 , 否则转到步骤 s 105 . [0032] 脚步 104 . Pj被添加到集合P中,即P+={Pj}; BASE IDj 添加到集合 B,即 B+={BASE IDj}; B和P被存储,并转移到步骤s 107 . [0033] 脚步 105 . 判断是否有BASE IDjεB、PNjεS、Pj!εP,如果是,则转步骤s 106 , 否则转到步骤 s 108 . [0034] 脚步 106 . 将 Pj 添加到集合 P,即 P+={Pj},然后将 P 存储并转移到步骤 s 107 . [0035] 脚步 107 . 移动终端设置为正常状态,转步骤s 109 . [0036] 脚步 108 . 移动终端设置为锁定状态,转步骤s 109 . [0037] 脚步 109 . 锁定过程结束。 示例 2 [0038] 在实施例一之前,本发明还包括初始化流程,本发明实施例中的初始化流程流程如图2所示,包括以下步骤。 [0039] 脚步 201 ,在本例中设定为5的限定拨号数N。 [0040] 脚步 202 ,用户在获得用户终端后拨打电话。 [0041] 脚步 203 ,判断用户拨打非紧急号码的次数是否大于N; 如果是,则转移到步骤s 204 , 否则转到步骤 s 202 . [0042] 脚步 204 ,用户终端获取当前基站发送的系统参数消息中的Pi={SID, NID, BASE ID, PN}和终端维护的PN集合S,其中PN序列集合S包括激活集,a 候选集和邻居集。 [0043] 脚步 205 ,用户终端初始化集合P={Pi},B={BASE ID},并自动存储S、P、B、SID和NID。 示例 3 [0044] 当移动终端处于锁定状态时,用户可以通过解锁流程改变订阅小区,本发明实施例的解锁流程如图3所示,包括如下步骤。 [0045] 脚步 301 ,用户请求小区解锁。 [0046]这里,用户可以通过两种方式向运营商请求小区解锁,其中一种方式是通过拨打指定的服务号码向运营商发送请求,另一种方式是将用户终端发送给运营商。 [0047] 脚步 302 ,运营商根据用户的小区解锁请求判断用户的身份和要求是否合法,如果是,则转步骤s 303 ,否则结束。 [0048] 脚步 303 ,当用户通过拨打指定业务号码向运营商发送小区解锁请求时,运营商向用户终端发送解锁短信; 当通过用户终端向运营商发送用户的小区解锁请求给运营商时,运营商通过工具向用户终端发送解锁指令。 [0049] 脚步 304 ,用户终端收到解锁指令或解锁短信后,清空数据库中的SID、NID、BASE ID和PN,并重新设置锁定小区配置。 [0050] 在重置锁定小区配置后,用户终端重新启动小区锁定过程。 [0051] 这里,移动终端使用本发明锁定小区后,其响应系统的流程如图4所示,其接入系统的流程如图5所示。当移动终端响应或发起一个 服务连接,首先检查当前移动终端的状态。 如果移动终端处于正常状态,则终端正常访问或响应系统。 如果移动终端处于锁定状态,则检查用户是否通过空中参数管理(OTAPA)、解锁短消息或拨打指定号码等解锁程序改变订阅小区。 ,如果是,则解锁,正常访问或响应系统,否则返回指定的错误码,禁止访问或响应系统。 [0052] 本发明实施例的可锁定小区的移动终端示意图如图6所示,该移动终端包括当前小区参数获取单元 61 , 参数比较单元 62 ,一个状态设置单元 63 , 数据库写入单元 64 , 一个数据存储单元 65 和一个解锁单元 66 . 其中,参数比较单元 62 分别连接到当前参数采集单元 61 , 状态设置单元 63 , 数据库写入单元 64 和数据存储单元 65 ; 和数据存储单元 65 分别连接到数据库写入单元 64 并解锁单元 66 . [0053] 当前小区参数获取单元 61 用于获取当前小区的SID、NID、BASE ID和PN。 [0054] 数据存储单元 65 用于存储移动终端的数据库,其中,数据库包括数据库中的SID、NID、BASE ID和PN参数。 [0055] 参数比较单元 62 用于比较参数获取单元获取的参数 61 当前单元格的参数与存储在数据存储单元中的参数 65 . [0056] 数据库站写入单元 64 用于根据参数比较单元的比较结果将数据写入数据库 62 ; 当比对结果为参数获取单元获取的SID、NID和PN时,将SID、NID、BASE ID和PN写入移动终端的数据库 61 当前小区的SID、NID、PN与数据库中存储的SID、NID、PN相同且数据库未满,或参数获取单元获取的BASE ID、PN时 61 当前单元格的名称与存储在数据库中的 SID、BASE ID 和 PN 相同。 [0057] 状态设定单元 63 用于根据参数比较单元的比较结果设置移动终端的状态 62; 当比对结果为参数获取单元获取的SID、NID、BASE ID和PN时,将移动终端设置为正常状态 61 当前小区的SID、NID、BASE ID、PN与数据库中存储的SID、NID、BASE ID、PN相同,或者参数获取单元获取的SID、NID、PN时 61 当前小区的SID、NID、PN与数据库中存储的SID、NID、PN相同且数据库未满,或参数获取单元获取的BASE ID、PN时 61 与存储在PN数据库中的SID、NID和PN相同,否则将移动终端设置为锁定状态。 [0058] 解锁单元 66 用于根据接收到的解锁指令或解锁短信清空数据库中的SID、NID、BASE ID和PN,并重置锁定小区配置。 [0059] 使用本发明,无需增加或修改网络侧的配置,即可降低运营成本; 本发明可以严格锁定某个小区,解决了由于网络呼吸效应,终端在某个特殊位置痉挛性锁定某个小区产生的乒乓效应,也不会导致孤岛效应。 [0060] 以上所述仅为本发明的较佳实施例而已,需要指出的是,对于本领域的技术人员来说,在不脱离本发明的技术原理的情况下,还可以进行若干改进和变型,这些改进和变型 也应视为本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: BR112012009106A2(String), CN101668285A(String), CN101668285B(String), EP2472924A1(String), EP2472924A4(String), EP2472924B1(String), ES2505246T3(String), US20120202463A1(String), US8825010B2(String), WO2011047577A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: BR112012009106A2(String), CN101668285A(String), CN101668285B(String), EP2472924A1(String), EP2472924A4(String), EP2472924B1(String), ES2505246T3(String), US20120202463A1(String), US8825010B2(String), WO2011047577A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8825010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), BR112012009106A2(String), CN101668285A(String), CN101668285B(String), EP2472924A1(String), EP2472924A4(String), EP2472924B1(String), ES2505246T3(String), US20120202463A1(String), US8825010B2(String), WO2011047577A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), BR112012009106A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), CN101668285A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), CN101668285B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), EP2472924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), EP2472924A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), EP2472924B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:40.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), ES2505246T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), US20120202463A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), US8825010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.019 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.020 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.020 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270651(Integer), WO2011047577A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8825010B2(String), US8825010B2(String), 1409587200(Integer), 270651(Integer), 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184968(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184968(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184968(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184968(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.066 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.066 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.066 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20110258451A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for updating mobile terminal software and mobile terminal(String), 移动终端软件更新方法及移动终端(String), US20110258451A1(String), Disclosed are a method for updating mobile terminal software and a mobile terminal. The method comprises the following steps: the mobile terminal software and/or the tool software used for updating the mobile terminal software perform hand-shaking according to encrypted hand-shaking data sent by the other party; wherein in the case that said hand-shaking is successful, the mobile terminal software or the tool software carries out verification of new mobile terminal software according to the pre-encrypted feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software, and determines whether the update is allowable according to the verification result. By introducing the two authentications of both the handshaking data and of the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by a software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the prior art in preventing such unlocking and language modification, ensures to the largest extend the terminal security, and effectively protects the interests of providers.(String), 本发明公开了一种移动终端软件更新方法及移动终端。 该方法包括以下步骤:移动终端软件和/或用于更新移动终端软件的工具软件根据对方发送的加密握手数据进行握手。 其中,在所述握手成功的情况下,移动终端软件或工具软件根据预先加密的移动终端软件的特征标识和新移动终端的特征标识,对新的移动终端软件进行验证。 软件,并根据验证结果判断是否允许更新。 本发明通过引入握手数据和特征标识的两种认证,极大地消除了终端被软件修改的可能性,避免了相关技术中终端解锁和语言修改,克服了现有技术的不足。 防止此类解锁和语言修改,最大限度地保证终端安全,有效保护提供商的利益。(String), US13/141202(String), 1250006400(Integer), US20110258451A1(String), 1319040000(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 10(Integer), US20030172090A1 | US20080233947A1 | US5418837A | US5887254A | US6029065A | US6091765A | US6223290B1 | US6449476B1 | US6859650B1 | US7031665B1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184969(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0d2c5e8804344f92a62e9827131bbb30.png(String), 184969(Integer), 0d2c5e8804344f92a62e9827131bbb30.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for updating mobile terminal software and mobile terminal(String), 移动终端软件更新方法及移动终端(String), US20110258451A1(String), Disclosed are a method for updating mobile terminal software and a mobile terminal. The method comprises the following steps: the mobile terminal software and/or the tool software used for updating the mobile terminal software perform hand-shaking according to encrypted hand-shaking data sent by the other party; wherein in the case that said hand-shaking is successful, the mobile terminal software or the tool software carries out verification of new mobile terminal software according to the pre-encrypted feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software, and determines whether the update is allowable according to the verification result. By introducing the two authentications of both the handshaking data and of the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by a software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the prior art in preventing such unlocking and language modification, ensures to the largest extend the terminal security, and effectively protects the interests of providers.(String), 本发明公开了一种移动终端软件更新方法及移动终端。 该方法包括以下步骤:移动终端软件和/或用于更新移动终端软件的工具软件根据对方发送的加密握手数据进行握手。 其中,在所述握手成功的情况下,移动终端软件或工具软件根据预先加密的移动终端软件的特征标识和新移动终端的特征标识,对新的移动终端软件进行验证。 软件,并根据验证结果判断是否允许更新。 本发明通过引入握手数据和特征标识的两种认证,极大地消除了终端被软件修改的可能性,避免了相关技术中终端解锁和语言修改,克服了现有技术的不足。 防止此类解锁和语言修改,最大限度地保证终端安全,有效保护提供商的利益。(String), US13/141202(String), 1250006400(Integer), US20110258451A1(String), 1319040000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 10(Integer), US20030172090A1 | US20080233947A1 | US5418837A | US5887254A | US6029065A | US6091765A | US6223290B1 | US6449476B1 | US6859650B1 | US7031665B1(String), \20230420\0d2c5e8804344f92a62e9827131bbb30.png(String), 16(Integer), 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 1. A method for updating mobile terminal software, comprising:mobile terminal software and/or tool software used for updating the mobile terminal software performing hand-shaking according to encrypted hand-shaking data sent by the other party; andif the hand-shaking is successful, the mobile terminal software or the tool software carrying out verification of new mobile terminal software according to a pre-encrypted feature identifier of the mobile terminal software and a feature identifier of the new mobile terminal software, and determining whether the update is allowable according to the verification result.(String), 1.根据权利要求2所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 2. The method for updating mobile terminal software according to claim 1, wherein the hand-shaking comprises:one party of the mobile terminal software and/or the tool software decrypting the encrypted hand-shaking data from the other party, and determining whether the decrypted hand-shaking data is identical to preset hand-shaking data; andif the determining result is yes, the mobile terminal software determining that the hand-shaking is successful, otherwise, the mobile terminal software determining that the hand-shaking is failed.(String), 12.根据权利要求3所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 3. The method for updating mobile terminal software according to claim 2, wherein in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises:the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the encrypted hand-shaking data from the tool software; andthe mobile terminal software decrypting the encrypted hand-shaking data from the tool software, and comparing the decrypted hand-shaking data with the preset hand-shaking data.(String), 13.根据权利要求4所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 4. The method for updating mobile terminal software according to claim 2, wherein in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises:the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the specific parameters served as the hand-shaking data encrypted and sent by the tool software; andthe mobile terminal software decrypting the encrypted hand-shaking data from the tool software to obtain the specific parameters, performing the calculation on the specific parameters according to the preset algorithm, and comparing the calculated result of the specific parameters with the preset hand-shaking data.(String), 14.根据权利要求5所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 5. The method for updating mobile terminal software according to claim 1, wherein the processing for verifying the new mobile terminal software by the mobile terminal software or the tool software comprises:the mobile terminal software or the tool software decrypting the pre-encrypted feature identifier of the mobile terminal software;the mobile terminal software or the tool software comparing the decrypted feature identifier of the mobile terminal software with the feature identifier of the new mobile terminal software;if the feature identifier of the mobile terminal software is identical to the feature identifier of the new mobile terminal software, determining that the new mobile terminal software passes the verification; andif the feature identifier of the mobile terminal software is different from the feature identifier of the new mobile terminal software, determining that the new mobile terminal software does not pass the verification.(String), 15.根据权利要求6所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 6. The method for updating mobile terminal software according to claim 5, wherein the processing for determining whether the update is allowable according to the verification result comprises:if the new mobile terminal software passes the verification, the tool software updating the mobile terminal software by using the new mobile terminal software; andif the new mobile terminal software does not pass the verification, stopping the update processing.(String), 16.根据权利要求9所述的移动终端,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 7. The method for updating mobile terminal software according to claim 1, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 8. A mobile terminal, comprising:a hand-shaking data module, configured to generate hand-shaking data, determine whether the hand-shaking between mobile terminal software and tool software is successful according to hand-shaking data from the tool software and the generated hand-shaking data, and return the determination result to the tool software;a feature identifier module, configured to store the encrypted preset feature identifier which is used for the mobile terminal software or the tool software to carry out the verification of the new mobile terminal software for updating the mobile terminal software;an encryption module, configured to encrypt the hand-shaking data generated by the hand-shaking data module and the unencrypted feature identifier; anda communication command module, configured to send the hand-shaking data encrypted by the encryption module to the tool software, and receive the encrypted hand-shaking data from the tool software.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 9. The mobile terminal according to claim 8, wherein the hand-shaking data module is configured to compare the hand-shaking data from the tool software with the generated hand-shaking data, determine the hand-shaking is successful if the hand-shaking data from the tool software is identical to the generated hand-shaking data, and determine the hand-shaking is failed if the hand-shaking data from the tool software is different from the generated hand-shaking data.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 10. The mobile terminal according to claim 8, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 11. The method for updating mobile terminal software according to claim 2, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 12. The method for updating mobile terminal software according to claim 3, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 13. The method for updating mobile terminal software according to claim 4, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 12(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 14. The method for updating mobile terminal software according to claim 5, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 13(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 15. The method for updating mobile terminal software according to claim 6, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 14(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184969(Integer), 16. The mobile terminal according to claim 9, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184969(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, and more particularly, to a method for updating mobile terminal software and a mobile terminal. BACKGROUND OF THE INVENTION [0002]At present, along with the rapid development of global mobile communication market, the competitions among various operators are also intense. Especially in the terminal product market, operators release various series of promotion policies one after another to attract users, and sell terminals to users with great preferential benefit; and some operators even give terminals to users for free. [0003]However, considering of theirs own benefits, operators generally adopt a series of restrictive measures. The common restrictive manner is to restrict a terminal, so that the terminal can only be used in the network of the operator giving the user with preferential benefit, or it is required to insert a specified card to enable the terminal into the usable state. Such restrictive manner is usually called as network-locking or card-locking. [0004]Though operators can restrict the usage of their terminals, it is still possible that the terminals of network-locking or card-locking may be modified by some lawbreakers via some methods, so that the modified terminals lose the function of network-locking or card-locking, which releases the restriction of operators and makes the terminals capable of being used by other operators or other networks; or makes the terminals used by inserting cards apart from the specified card, and it is even possible to change the interface of the terminal to other languages and further causes the changed terminal to be used in the network of the operators with other languages, which obviously damages the benefits of operators seriously. [0005]Therefore, an important issue is how to prevent network-locking and card-locking terminal from being changed to an unlocked terminal by software (i.e. avoiding the unlocking), and to prevent language A of terminals from being changed to language B by software (i.e. avoid modification of language), so as to protect the benefits of operators. [0006]At present, there are a few methods provided in the mobile terminal field, for preventing the software of the mobile terminal device from being modified illegally, wherein one method is to record the value stored in PAF-ROM and necessary data such as international mobile equipment identity (IMEI) simultaneously in a memory area that can only be programmed once, and with such values as the basic data, a comparison is made to determine whether it is abnormal changed software, when being changed by the software, so as to determine whether the software is illegally changed. The problem of the above method is that a portion of the terminal must be divided as a memory that can only be programmed once, or a programmable read only memory (PROM) chip must be added independently, so that the cost of implementation is high; moreover, the determination of the above method is focused on the changed result, and it is necessary to prevent the changed terminal from being used continuously after determining that the software of terminal is illegally changed, which has lag and is unable to prevent the terminal from being changed by software in fact. [0007]There is no effective solution provided in the related art to solve the problem that it is impossible for preventing the terminal from being changed by software. SUMMARY OF THE INVENTION [0008]The present invention is provided to solve the problem that it is impossible for preventing the terminal from being changed by software in the related art; and the major objective of the present invention is to provide a method for updating mobile terminal software and mobile terminal to solve the above problem. [0009]To achieve the above objectives, according to one aspect of the present invention, a method for updating mobile terminal software is provided. [0010]The method for updating mobile terminal software comprises the following steps: mobile terminal software and/or tool software used for updating the mobile terminal software performing hand-shaking according to encrypted hand-shaking data sent by the other party; if the hand-shaking is successful, the mobile terminal software or the tool software carrying out verification of new mobile terminal software according to a pre-encrypted feature identifier of the mobile terminal software and a feature identifier of the new mobile terminal software, and determining whether the update is allowable according to the verification result. [0011]The above hand-shaking comprises the following steps: one party of the mobile terminal software and/or the tool software decrypting the encrypted hand-shaking data from the other party, and determining whether the decrypted hand-shaking data is identical to preset hand-shaking data; if the determining result is yes, the mobile terminal software determining that the hand-shaking is successful, otherwise, the mobile terminal software determining that the hand-shaking is failed. [0012]On the one hand, in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises: the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the encrypted hand-shaking data from the tool software; and the mobile terminal software decrypting the encrypted hand-shaking data from the tool software, and comparing the decrypted hand-shaking data with the preset hand-shaking data. [0013]On the other hand, in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises: the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the specific parameters served as the hand-shaking data encrypted and sent by the tool software; and the mobile terminal software decrypting the encrypted hand-shaking data from the tool software to obtain the specific parameters, performing the calculation on the specific parameters according to the preset algorithm, and comparing the calculated result of the specific parameters with the preset hand-shaking data. [0014]In addition, the processing for verifying the new mobile terminal software by the mobile terminal software or the tool software comprises: the mobile terminal software or the tool software decrypting the pre-encrypted feature identifier of the mobile terminal software; the mobile terminal software or the tool software comparing the decrypted feature identifier of the mobile terminal software with the feature identifier of the new mobile terminal software; if the feature identifier of the mobile terminal software is identical to the feature identifier of the new mobile terminal software, determining that the new mobile terminal software passes the verification; and if the feature identifier of the mobile terminal software is different from the feature identifier of the new mobile terminal software, determining that the new mobile terminal software does not pass the verification. [0015]The processing for determining whether the update is allowable according to the verification result comprises: if the new mobile terminal software passes the verification, the tool software updating the mobile terminal software by using the new mobile terminal software; and if the new mobile terminal software does not pass the verification, stopping the update processing. [0016]Preferably, the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier. [0017]To achieve the above objectives, according to another aspect of the present invention, a mobile terminal device is provided. [0018]The mobile terminal comprises: a hand-shaking data module, configured to generate hand-shaking data, determine whether the hand-shaking between mobile terminal software and tool software is successful according to hand-shaking data from the tool software and the generated hand-shaking data, and return the determination result to the tool software; a feature identifier module, configured to store the encrypted preset feature identifier which is used for the mobile terminal software or the tool software to carry out the verification of the new mobile terminal software for updating the mobile terminal software; an encryption module, configured to encrypt the hand-shaking data generated by the hand-shaking data module and the unencrypted feature identifier; and a communication command module, configured to send the hand-shaking data encrypted by the encryption module to the tool software, and receive the encrypted hand-shaking data from the tool software. [0019]The hand-shaking data module is configured to compare the hand-shaking data from the tool software with the generated hand-shaking data, determine the hand-shaking is successful if the hand-shaking data from the tool software is identical to the generated hand-shaking data, and determine the hand-shaking is failed if the hand-shaking data from the tool software is different from the generated hand-shaking data. [0020]Preferably, the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier. [0021]By means of the above technical solution of the present invention, by introducing the two authentications of both the handshaking data and the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by a software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the technology of preventing such unlocking and language modification in the prior art, ensures maximum terminal security, and effectively protects the interests of providers. BRIEF DESCRIPTION OF THE DRAWINGS [0022]The accompanying drawings described herein are used for further illustrating the present invention and constitute a part of the application. The illustrative embodiments of the present invention and the description thereof are used for further explaining the present invention and are not used for limiting unduly the protection scope thereof, in which: [0023]FIG. 1 is a flowchart illustrating the method for updating mobile terminal software according to method embodiment of the present invention; [0024]FIG. 2 is a flowchart illustrating a processing example of the method for updating mobile terminal software according to method embodiment of the present invention; and [0025]FIG. 3 is a block diagram illustrating the mobile terminal according to device embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Function Summary [0026]To solve the problem that the terminal can easily be changed by software in the related art, the present invention implements the unidirectional/bidirectional hand-shaking of the tool software (software for performing the update) and the mobile terminal software (the software to be updated) and the verification of the new software of the mobile terminal (the software that will replace the mobile terminal software) performed by the mobile terminal software by taking into account the feature that the changing of software needs pass through a data line, a built-in data interface of mobile terminal and the data line connected to the interface, so as to eliminate the possibility of illegally updating the mobile terminal software during the illegal changing process rather than based on the illegally-changed result, thereby protecting to the largest extend the mobile terminal in the nondestructive manner. Method Embodiment [0027]In accordance with the embodiment of the present invention, a method for updating mobile terminal software is provided for preventing the mobile terminal software of the mobile terminal from being illegally updated. [0028]FIG. 1 is a flowchart illustrating the method for updating mobile terminal software according to method embodiment of the present invention. As shown in FIG. 1, the method comprises the following steps S102-S104. [0029]Step S102, mobile terminal software and/or tool software used for updating the mobile terminal software perform hand-shaking according to encrypted hand-shaking data sent by the other part, that is to say, one party of the mobile terminal software and the tool software used for updating the mobile terminal software performs an unidirectional hand-shaking of both parties according to the encrypted hand-shaking data sent by the other party, or the mobile terminal software and the tool software used for updating the mobile terminal software perform the bidirectional hand-shaking of both parties according to the encrypted hand-shaking data that both parties send to each other. [0030]Step S104, if said hand-shaking is successful, the mobile terminal software or the tool software carries out verification of new mobile terminal software according to a pre-encrypted feature identifier of the mobile terminal software (the feature identifier may be a identification group, of which the composition may be combined and adjusted freely according to the practical requirement, for example, it may include one or the combination of an operator identifier, a network-locking card-locking identifier and a language identifier, and further include information such as a version number) and a feature identifier of the new mobile terminal software required for updating the mobile terminal software, and determines whether the update is allowable according to the verification result, i.e. determines whether it is allowable that the new mobile terminal software is used to update the mobile terminal software. [0031]In step S102, The processing for performing the unidirectional or bidirectional hand-shaking specifically comprises the following steps: no matter it is unidirectional hand-shaking or bidirectional hand-shaking, one party of the mobile terminal software and the tool software needs to decrypt the encrypted hand-shaking data from the other party, and determines whether the decrypted hand-shaking data are identical to the preset hand-shaking data, wherein if said determining result is yes, the hand-shaking is determined to be successful; otherwise, the hand-shaking is determined to be failed. [0032]Moreover, in step S102, the hand-shaking data may be generated randomly by the mobile terminal software according to some information; the mobile terminal software and the legal tool software both know the content of hand-shaking data. By introducing the hand-shaking data, it is guaranteed that the illegal tool software can not implement successfully the hand-shaking communication; at the same time, by encrypting the hand-shaking data, it is guaranteed that the correct hand-shaking data can not be monitored from the transmission packet. The method for encrypting the hand-shaking data may adopt a same set of encryption algorithm negotiated and shared by the mobile terminal software and the tool software. [0033]Additionally, if the unidirectional hand-shaking is performed, the encrypted hand-shaking data may be transmitted as a command by the tool software served as the master control side to the mobile terminal software. After receiving and decrypting the hand-shaking data, the mobile terminal software served as the receiving side compares the hand-shaking data with its hand-shaking data firmly stored (in read only memory). The encrypted hand-shaking data may also be transmitted to the tool software by the mobile terminal software served as the master control side via a command response packet. After receiving and decrypting the hand-shaking data, the tool software served as the receiving side compares the hand-shaking data with its hand-shaking data firmly stored (in read only memory). Preferably, no matter the hand-shaking data is in the mobile terminal software or in the tool software, the hand-shaking data is set as read only attribute, so that the hand-shaking data can not be changed through any external manner. [0034]In the above processing, the hand-shaking data may be calculated according to the preset parameters (for example, the terminal serial number that can be acquired by the mobile terminal software and the tool software); and the parameters can also be directly served as the hand-shaking data for encrypted transmission. In general, such preset parameters may be stored in the tool software and/or the mobile terminal software. The initiating side of hand-shaking may be any one of the terminal software and the tool software. [0035]However, preferably, the final result determination may be performed at the mobile terminal software side to prevent some pirated tools from skipping the step for determining whether the hand-shaking is successful, which further guarantees the security of update. [0036]The manner for performing the hand-shaking success determination at the terminal side may be one of the following manners. [0037](Manner 1) the mobile terminal software performs calculation on preset parameters by using preset algorithm(s) to obtain preset hand-shaking data, and receives the encrypted hand-shaking data from the tool software; and the mobile terminal software decrypts the encrypted hand-shaking data from the tool software, and compares the decrypted hand-shaking data with preset hand-shaking data. [0038](Manner 2) the mobile terminal software performs calculation on preset parameters by using preset algorithm(s) to obtain preset hand-shaking data, and receives the specific parameters served as the hand-shaking data encrypted and sent by the tool software; the mobile terminal software decrypts the encrypted hand-shaking data from the tool software to obtain the specific parameters, performs calculation on the specific parameters according to the preset algorithm(s), and compares the calculation result of the specific parameters with the preset hand-shaking data. [0039]It should be noted that, in the above Manner 2, the specific parameters are severed as the hand-shaking data, and the processing for the calculation of the specific parameters is performed at the terminal side. [0040]In addition, in step 104, the processing of verifying new mobile terminal software performed by the mobile terminal software or tool software comprises following steps: the mobile terminal software or the tool software decrypts the pre-encrypted feature identifier of the mobile terminal software; and the mobile terminal software or the tool software compares the decrypted feature identifier of the mobile terminal software with the feature identifier of the new mobile terminal software wherein if the feature identifier of the mobile terminal software is identical to the feature identifier of the new mobile terminal software, it is determined that the new mobile terminal software passes the verification and the update is allowed; and if the feature identifier of the mobile terminal software is different from the feature identifier of the new mobile terminal software, it is determined that the new mobile terminal software does not pass the verification and the update processing is stopped. [0041]In the case of verifying the new mobile terminal software by the tool software, the tool software needs to send a command for acquiring the feature identifier of mobile terminal software to the mobile terminal software; moreover, in the process of the mobile terminal software sending its feature identifier to the tool software, the feature identifier may be encrypted and then be transmitted, which enhances the security of the update process. [0042]On the other hand, in the case of verifying the new mobile terminal software by the mobile terminal software, it is necessary for receiving the feature identifier of the new mobile terminal software from the tool software; and the feature identifier of the new mobile terminal software may be encrypted and then be transmitted, which enhances the security of the update process. [0043]The verification of the new mobile terminal software performed by the tool software is described as example. [0044]FIG. 2 is a flowchart illustrating an example of the method for updating mobile terminal software according to the method embodiment of the present invention. As shown in FIG. 2, in practical application, in the case of verifying the new mobile terminal software by the tool software, the method for updating mobile terminal software according to the present embodiment may comprise the following steps 201-206. [0045]Step 201, a personal computer (PC) capable of executing tool software is connected to a terminal via a data line, and starts to communicate with the terminal. [0046]Step 202, the software of the terminal itself and the tool software transmit encrypted hand-shaking data. [0047]Step 203, it is determined whether the hand-shaking is successful, wherein in the case of the unidirectional hand-shaking, if the tool software served as the master control side sends the encrypted hand-shaking data in step 202, the mobile terminal software determines whether the hand-shaking data are correct, encrypts the determination result and returns it to the tool software via a command response packet, and if the mobile terminal software served as the master control side sends the encrypted hand-shaking data in step 202, the tool software determines whether the hand-shaking data are correct, and returns the encrypted determination result; and in the case of the bidirectional hand-shaking, each of the two sides needs to determine whether the hand-shaking data of the other side is correct, and returns the encrypted determination result to the other side (steps 202 and 203 correspond to the above step S102). [0048]Step 204, it can be determined whether the hand-shaking is successful according to the determination result of step 203, wherein if the hand-shaking is failed, the tool software terminates the procedure; and if the hand-shaking is successful, the tool software sends a specific command to the mobile terminal software to acquire the encrypted feature identifier of mobile terminal software, wherein the specific command is negotiated between the tool software and the mobile terminal software in a special manner, the algorithm for encrypting the feature identifier may be negotiated by the mobile terminal software and the tool software together, and the algorithm for encrypting the feature identifier may be the same as the algorithm for encrypting the hand-shaking data; and the encryption transmission of the feature identifier guarantees that the real data can not be monitored during transmission, which enhances the protection of terminal security. [0049]Step 205, it is determined whether the acquired decrypted feature identifier is identical to the feature identifier of the mobile terminal software to be updated (i.e. the above new mobile terminal software) (steps 204 and 205 correspond to the above step S104). [0050]Step 206, if the comparing result of step 205 is “being identical”, it is started to update the mobile terminal software (which can have the update procedure in which the tool software replaces the mobile terminal software with the new mobile terminal software), otherwise, the procedure is terminated. Device Embodiment [0051]In the present embodiment, a mobile terminal is provided for implementing the above method for updating mobile terminal software and the mobile terminal can avoid the illegal update of its terminal software. [0052]FIG. 3 is a block diagram illustrating the mobile terminal according to the device embodiment of the present invention. As shown in FIG. 3, the mobile terminal according to the present embodiment comprises: a hand-shaking data module 10, a feature identifier module 20, an encryption module 30, a communication command module 40, of which the above structure is described hereinafter. [0053]The hand-shaking data module 10 is used for generating the hand-shaking data, reading the hand-shaking data from the tool software, determining whether the hand-shaking of the mobile terminal software and the tool software is successful according to the hand-shaking data from the tool software and the generated hand-shaking data, and returning the determination result to the tool software. [0054]The feature identifier module 20 is used for storing the encrypted preset feature identifier, so that the mobile terminal software or the tool software carries out the verification of the new mobile terminal software for replacing the mobile terminal software, by using the stored feature identifier; [0055]The encryption module (may also be referred to as encryption algorithm module) 30 is used for encrypting the hand-shaking data generated by the hand-shaking data module 10 and the unencrypted feature identifier, so as to avoid that the transmitted hand-shaking data and the feature identifier of the mobile terminal software are monitored in the process of communication. [0056]The communication command module 40 is used for sending the hand-shaking data encrypted by the encryption module 30 to the tool software, receiving the encrypted hand-shaking data from the tool software, and encoding, packing and transmitting the feature identifier of the mobile terminal software. Preferably, during the implementation of the present invention, the command transmitted by the communication command module can be separated from other general commands, so as to further guarantee the security of terminal. [0057]The hand-shaking data module 10 may compare the hand-shaking data from the tool software with the generated hand-shaking data, determine the hand-shaking is successful if the hand-shaking data from the tool software are the same as the generated hand-shaking data, otherwise, determine the hand-shaking is failed. Herein, the generated hand-shaking data may be the hand-shaking data which calculated according preset parameters (for example the serial number of terminal), or may be the extracted preset parameters; moreover, during the hand-shaking, the processing described in the above Manner 1 and Manner 2 can be referred to for the detailed processing. [0058]The method of the encryption module 30 for encrypting the hand-shaking data generated by the hand-shaking data module 10 may be the same as or different from the method for encrypting the unencrypted feature identifier. [0059]Preferably, the feature identifier is at least one of the following: an operator identifier, a network-locking card-locking identifier, a language identifier. The feature identifier herein may be an identification group, of which the composition may be adjusted and changed according to the practical requirements, which is not listed herein one by one any more. [0060]It can be seen from the above that, in the technical solution of the present invention, the software of the terminal itself and the tool software both have a set of negotiated encryption algorithm. When the mobile terminal software is changed through the data line, it is only possible to replace the mobile terminal software with the network-locking card-locking software of the local operator and the mobile terminal software of the local operator language, which effectively avoids the illegal software update of terminal and guarantees the security of terminal. [0061]To sum up, by introducing the two authentications of both the handshaking data and the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the prior art in preventing such unlocking and language modification, ensures to the largest extent the terminal security, and effectively protects the interests of operators; in addition, the security may be ensured only by adding a little processing, which is implemented simply and reliably. [0062]The foregoing is only preferred embodiments of the present invention and is not for use in limiting the protection scope thereof, and for those skilled in the art, there may be various modifications and changes to the present invention. Any modification, equivalent replacement and improvement made under the spirit and principle of the present invention should be included in the protection scope thereof.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端软件更新方法及移动终端。 发明背景 [0002] 目前,随着全球移动通信市场的快速发展,各运营商之间的竞争也十分激烈。 特别是在终端产品市场,运营商纷纷出台各种系列的促销政策吸引用户,并以极大的优惠力度向用户销售终端; 有些运营商甚至免费向用户提供终端。 [0003] 但是,考虑到自身的利益,运营商一般会采取一系列的限制措施。 常见的限制方式是对终端进行限制,使终端只能在给用户优惠的运营商的网络中使用,或者需要插入指定的卡才能使终端进入可用状态。 这种限制方式通常称为锁网或锁卡。 [0004] 虽然运营商可以对其终端的使用进行限制,但锁网或锁卡终端仍有可能被一些不法分子通过某种方法进行改造,使改造后的终端失去锁网或卡锁功能。 锁定,解除对运营商的限制,使终端可以被其他运营商或其他网络使用; 或将插卡使用的终端与指定的卡分开,甚至可以将终端的界面更改为其他语言,进而导致更改后的终端在其他语言的运营商网络中使用,显然 严重损害了经营者的利益。 [0005] 因此,一个重要的问题是如何防止锁网卡锁终端被软件更改为未解锁的终端(即避免解锁),以及如何防止终端的语言A被软件更改为语言B(即无法解锁)。 避免修改语言),以保护运营商的利益。 [0006] 目前,移动终端领域提供了几种防止移动终端设备的软件被非法修改的方法,其中一种方法是记录PAF-ROM中存储的值和必要的数据,如国际移动设备 同时在一个只能被编程一次的内存区域中,与基本数据等值进行比较,判断是否是异常修改的软件,当被软件修改时,判断是否 软件被非法更改。 上述方法的问题在于必须将终端的一部分划分为只能一次编程的存储器,或者必须单独添加可编程只读存储器(PROM)芯片,实现成本高; 而且,上述方法的判定主要针对变更后的结果,在判定终端软件被非法变更后,需要防止变更后的终端继续使用,存在滞后性,无法阻止终端被盗用。 实际上是由软件改变的。 [0007] 相关技术中没有提供有效的方案来解决无法通过软件改变终端的问题。 发明内容 [0008] 为解决相关技术中无法防止终端被软件更改的问题而提出本发明; 本发明的主要目的在于提供一种移动终端软件更新方法及移动终端,以解决上述问题。 [0009] 为实现上述目的,根据本发明的一个方面,提供了一种移动终端软件的更新方法。 [0010]该移动终端软件更新方法包括以下步骤:移动终端软件和/或用于更新移动终端软件的工具软件根据对方发送的加密握手数据进行握手; 若握手成功,则移动终端软件或工具软件根据预加密的移动终端软件特征标识和新移动终端软件特征标识对新移动终端软件进行校验,确定 根据验证结果是否允许更新。 [0011] 上述握手包括以下步骤:移动终端软件和/或工具软件的一方对另一方加密后的握手数据进行解密,并判断解密后的握手数据是否与预设的握手数据相同。 抖动数据; 若判断结果为是,移动终端软件判断握手成功,否则移动终端软件判断握手失败。 [0012] 一方面,在移动终端软件判断握手是否成功的情况下,进行握手的处理包括:移动终端软件使用预设的参数对预设参数进行计算。 算法获取预设的握手数据,并从工具软件接收加密后的握手数据; 移动终端软件对来自工具软件的加密后的握手数据进行解密,并将解密后的握手数据与预设的握手数据进行比对。 [0013] 另一方面,在移动终端软件判断握手是否成功的情况下,进行握手的处理包括:移动终端软件使用预设的参数对预设参数进行计算。 算法获取预设的握手数据,接收工具软件加密发送的握手数据的具体参数; 移动终端软件从工具软件中解密加密后的握手数据,得到特定参数,根据预设算法对特定参数进行计算,并将特定参数的计算结果与预设握手进行比较 数据。 [0014] 进一步地,所述移动终端软件或工具软件对新的移动终端软件进行验证的处理包括: 移动终端软件或工具软件对移动终端软件的预加密特征标识进行解密; 移动终端软件或工具软件将解密后的移动终端软件特征标识与新移动终端软件的特征标识进行比较; 如果移动终端软件的特征标识与新的移动终端软件的特征标识相同,则确定新的移动终端软件通过验证; 如果移动终端软件的特征标识与新的移动终端软件的特征标识不同,则确定新的移动终端软件未通过验证。 [0015] 所述根据验证结果判断是否允许更新的处理包括:如果新的移动终端软件验证通过,则工具软件使用新的移动终端软件更新移动终端软件。 如果新的移动终端软件没有通过验证,则停止更新处理。 [0016] 优选地,所述移动终端软件的特征标识和所述新的移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。 [0017] 为实现上述目的,根据本发明的另一方面,提供了一种移动终端设备。 [0018]移动终端包括:握手数据模块,用于生成握手数据,根据来自工具软件的握手数据和生成的握手信息,判断移动终端软件与工具软件握手是否成功。 摇动数据,并将判断结果返回给工具软件; 特征标识模块,用于存储加密后的预设特征标识,用于移动终端软件或工具软件对新的移动终端软件进行验证,以更新移动终端软件; 加密模块,用于对握手数据模块生成的握手数据和未加密的特征标识进行加密; 通信命令模块,用于将加密模块加密后的握手数据发送给工具软件,并从工具软件接收加密后的握手数据。 [0019] 握手数据模块,用于将工具软件的握手数据与生成的握手数据进行比对,如果工具软件的握手数据与生成的握手数据相同,则握手成功。 -握手数据,如果来自工具软件的握手数据与生成的握手数据不一致,则判定握手失败。 [0020] 优选地,所述移动终端软件的特征标识和所述新的移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。 [0021] 通过本发明的上述技术方案,通过引入握手数据和特征标识的两次认证,大大消除了终端被软件修改的可能性,避免了终端解锁和语言修改。 在相关技术中,克服了现有技术中防止此类解锁和语言修改技术的不足,最大限度地保证了终端安全,有效保护了提供商的利益。 附图的简要说明 [0022] 此处所描述的附图用于进一步说明本发明,构成本申请的一部分。 本发明的示例性实施例及其说明用于进一步解释本发明,并不用于不当限制本发明的保护范围,其中: [0023] 图1为本发明方法实施例的移动终端软件更新方法的流程图; [0024] 图2为本发明方法实施例的移动终端软件更新方法的处理示例流程图。 和 [0025] 图3是示出根据本发明的设备实施例的移动终端的框图。 优选实施例的详细说明 功能概要 [0026] 为了解决相关技术中终端容易被软件更改的问题,本发明实现了工具软件(进行更新的软件)和移动终端软件(待更新的软件)的单向/双向握手。 更新)和移动终端软件对移动终端新软件(将替代移动终端软件的软件)的验证,考虑到软件更改需要通过数据线的特点,内置了一个 -in移动终端的数据接口及连接该接口的数据线,杜绝在非法更改过程中对移动终端软件进行非法更新的可能性,而不是基于非法更改的结果,从而最大程度地保护 以无损方式访问移动终端。 方法实施例 [0027] 根据本发明实施例,提供了一种移动终端软件的更新方法,以防止移动终端的移动终端软件被非法更新。 [0028] 图1为本发明方法实施例的移动终端软件更新方法的流程图。 如图1所示,该方法包括以下步骤S 102 -S 104 . [0029] 脚步 102 、移动终端软件和/或用于更新移动终端软件的工具软件根据另一方发送的加密握手数据进行握手,即移动终端软件的一方和所使用的工具软件 更新移动终端软件根据对方发送的加密握手数据对双方进行单向握手,或者移动终端软件和更新移动终端软件的工具软件进行双向握手。 双方根据双方发送给对方的加密握手数据进行握手。 [0030] 脚步 104 ,如果所述握手成功,则移动终端软件或工具软件根据预先加密的移动终端软件的特征标识(特征标识可以是标识组,其中 组成可以根据实际需要自由组合调整,例如可以包括运营商标识、锁网锁卡标识和语言标识中的一种或组合,还可以包括版本等信息 number)和更新移动终端软件所需的新移动终端软件的特征标识,根据验证结果判断是否允许更新,即判断是否允许使用新移动终端软件更新移动终端软件。 移动端软件。 [0031] 在步骤S 102 ,进行单向或双向握手的处理具体包括以下步骤:无论是单向握手还是双向握手,移动终端软件和工具软件的一方需要对加密后的握手信息进行解密。 来自对方的握手数据,判断解密后的握手数据与预设的握手数据是否相同,若判断结果为是,则确定握手成功。 否则,确定握手失败。 [0032] 此外,在步骤S 102 ,握手数据可以是移动终端软件根据一些信息随机生成的; 移动终端软件和合法工具软件都知道握手数据的内容。 通过引入握手数据,保证非法工具软件无法成功实现握手通信; 同时,通过对握手数据进行加密,保证无法从传输包中监听到正确的握手数据。 对握手数据进行加密的方法可以采用移动终端软件和工具软件协商共享的同一套加密算法。 [0033] 另外,如果是单向握手,则可以由作为主控端的工具软件将加密后的握手数据作为命令发送给移动终端软件。 作为接收方的移动终端软件在接收并解密握手数据后,将握手数据与其牢固存储的握手数据(在只读存储器中)进行比较。 也可以由作为主控端的移动终端软件通过命令响应包将加密后的握手数据发送给工具软件。 作为接收方的工具软件在接收并解密握手数据后,将握手数据与其牢固存储的握手数据(在只读存储器中)进行比较。 优选地,无论握手数据是在移动终端软件中还是在工具软件中,都将握手数据设置为只读属性,使得握手数据无法通过任何外部方式进行更改。 [0034]在上述处理中,可以根据预先设置的参数(例如,移动终端软件和工具软件可以获取的终端序列号)计算握手数据; 参数也可以直接作为握手数据进行加密传输。 通常,这些预设参数可以存储在工具软件和/或移动终端软件中。 握手的发起方可以是终端软件和工具软件中的任意一种。 [0035] 但优选地,最终结果判断可以在移动终端软件侧进行,避免部分盗版工具跳过判断握手是否成功的步骤,进一步保证更新的安全性。 [0036] 终端侧进行握手成功判断的方式可以为以下方式之一。 [0037] (方式一)移动终端软件通过预设算法对预设参数进行计算,得到预设的握手数据,并从工具软件接收加密后的握手数据; 移动终端软件对来自工具软件的加密后的握手数据进行解密,并将解密后的握手数据与预设的握手数据进行比对。 [0038] (方式二)移动终端软件通过预设算法对预设参数进行计算得到预设握手数据,并接收工具软件加密发送的握手数据具体参数; 移动终端软件对来自工具软件的加密握手数据进行解密,得到特定参数,根据预设算法对特定参数进行计算,并将特定参数的计算结果与预设握手数据进行比较。 震动数据。 [0039] 需要说明的是,在上述方式二中,将特定参数分割为握手数据,在终端侧进行特定参数的计算处理。 [0040] 此外,在步 104 、 移动终端软件或工具软件对新的移动终端软件进行验证的处理包括以下步骤: 移动终端软件或工具软件对预加密的移动终端软件特征标识进行解密; 移动终端软件或工具软件将解密后的移动终端软件的特征标识与新的移动终端软件的特征标识进行比较,如果移动终端软件的特征标识与新的移动终端的特征标识相同 软件,确定新的移动终端软件通过验证,允许更新; 如果移动终端软件的特征标识与新的移动终端软件的特征标识不同,则确定新的移动终端软件未通过验证,停止更新处理。 [0041] 在工具软件对新的移动终端软件进行验证时,工具软件需要向移动终端软件发送获取移动终端软件特征标识的命令; 并且,移动终端软件在向工具软件发送其特征标识的过程中,可以对特征标识进行加密后传输,增强了更新过程的安全性。 [0042] 另一方面,在移动终端软件对新的移动终端软件进行验证时,需要从工具软件中接收新的移动终端软件的特征标识; 并且可以对新的移动终端软件的特征标识进行加密后传输,增强了更新过程的安全性。 [0043] 以工具软件对新的移动终端软件的验证为例进行说明。 [0044]图2是示出根据本发明方法实施例的更新移动终端软件的方法的示例的流程图。 如图2所示,在实际应用中,在通过工具软件验证新的移动终端软件的情况下,本实施例的移动终端软件更新方法可以包括以下步骤 201 - 206 . [0045] 步 201 ,可执行工具软件的个人计算机(PC)通过数据线连接到终端,并开始与终端通信。 [0046] 步 202 ,终端自身的软件和工具软件传输加密的握手数据。 [0047] 步 203 ,判断握手是否成功,其中在单向握手的情况下,如果作为主控端的工具软件在步骤中发送加密的握手数据 202 ,移动终端软件判断握手数据是否正确,将判断结果加密后通过命令响应包返回给工具软件,如果作为主控端的移动终端软件发送加密后的握手数据 数据同步 202 ,工具软件判断握手数据是否正确,并返回加密后的判断结果; 而在双向握手的情况下,双方都需要判断对方的握手数据是否正确,并将加密后的判断结果返回给对方(步骤 202 和 203 对应上面的步骤S 102 ). [0048] 步 204 ,可以根据step的判断结果判断握手是否成功 203 ,其中如果握手失败,则工具软件终止流程; 如果握手成功,则工具软件向移动终端软件发送特定命令以获取移动终端软件的加密特征标识,其中该特定命令是工具软件与移动终端软件以特殊方式协商的。 方式中,特征标识的加密算法可以由移动终端软件和工具软件共同协商,特征标识的加密算法可以与握手数据的加密算法相同。 特征标识的加密传输保证了真实数据在传输过程中无法被监听,增强了对终端安全的保护。 [0049] 步 205 ,判断获取的解密后的特征标识与待更新的移动终端软件(即上述新的移动终端软件)的特征标识是否相同(步骤 204 和 205 对应上面的步骤S 104 ). [0050] 步 206 , 如果步骤的比较结果 205 为“相同”,则开始更新移动终端软件(可以有工具软件用新的移动终端软件替换移动终端软件的更新流程),否则流程结束。 装置实施例 [0051] 本实施例提供了一种移动终端,用于实现上述移动终端软件的更新方法,移动终端可以避免其终端软件被非法更新。 [0052] 图3是示出根据本发明装置实施例的移动终端的框图。 如图3所示,本实施例的移动终端包括: 握手数据模块 10 ,特征标识符模块 20 , 一个加密模块 30 , 通信命令模块 40 ,其上述结构在下文中描述。 [0053] 握手数据模块 10用于生成握手数据,从工具软件中读取握手数据,根据来自工具软件的握手数据判断移动终端软件与工具软件握手是否成功,以及 生成的握手数据,将判断结果返回给工具软件。 [0054] 特征标识符模块 20 用于存储加密后的预设特征标识,以便移动终端软件或工具软件使用存储的特征标识对新的移动终端软件进行验证,以替换移动终端软件。 [0055] 加密模块(也可称为加密算法模块) 30 用于对握手数据模块生成的握手数据进行加密 10 以及未加密的特征标识,避免通信过程中传输的握手数据和移动终端软件的特征标识被监听。 [0056] 通信命令模块 40 用于发送加密模块加密后的握手数据 30 发送给工具软件,接收来自工具软件的加密后的握手数据,对移动终端软件的特征标识进行编码、打包和传输。 优选地,在实施本发明的过程中,可以将通信命令模块发送的命令与其他通用命令分开,进一步保证终端的安全性。 [0057] 握手数据模块 10 可以将来自工具软件的握手数据与生成的握手数据进行比较,如果来自工具软件的握手数据与生成的握手数据相同,则判断握手成功,否则,判断 握手失败。 其中,生成的握手数据可以是根据预设参数(例如终端序列号)计算得到的握手数据,也可以是提取的预设参数。 并且,在握手过程中,具体处理可以参考上述方式一和方式二中描述的处理。 [0058] 加密模块的方法 30 用于对握手数据模块生成的握手数据进行加密 10 与未加密特征标识的加密方法可以相同也可以不同。 [0059] 优选地,所述特征标识为以下至少之一:运营商标识、锁网锁卡标识、语言标识。 这里的特征标识可以是一个标识组,其组成可以根据实际需要进行调整和变化,在此不再一一列举。 [0060] 由上可见,在本发明的技术方案中,终端自身的软件和工具软件均具有一套协商的加密算法。 通过数据线更换手机端软件时,只能更换手机端软件为当地运营商的锁网锁卡软件和当地运营商语言的手机端软件,有效避免了 终端的非法软件更新,保证终端的安全。 [0061] 综上所述,本发明通过引入握手数据和特征标识两种认证方式,极大地杜绝了终端被软件修改的可能性,避免了相关技术中的终端解锁和语言修改,克服了现有技术的不足。 防止此类解锁和语言修改的现有技术,最大限度地保证了终端安全,有效保护了运营商的利益。 另外,只需增加少量处理即可保证安全性,实现简单可靠。 [0062]以上所述仅为本发明的优选实施例而已,并不用于限制本发明的保护范围,对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101437224A(String), EP2381711A1(String), EP2381711A4(String), US20110258451A1(String), WO2010072073A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101437224A(String), EP2381711A1(String), EP2381711A4(String), US20110258451A1(String), WO2010072073A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20110258451A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101437224A(String), EP2381711A1(String), EP2381711A4(String), US20110258451A1(String), WO2010072073A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270652(Integer), CN101437224A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270652(Integer), EP2381711A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270652(Integer), EP2381711A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270652(Integer), US20110258451A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270652(Integer), WO2010072073A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20110258451A1(String), US20110258451A1(String), 1319040000(Integer), 270652(Integer), 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.374 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), YANG, CUIHONG(String), SUN, DENGYUN(String), 中兴通讯股份有限公司(String), YANG CUIHONG(String), SUN DENGYUN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184969(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184969(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: YANG, CUIHONG(String), YANG CUIHONG(String), 0(Integer), 1681975541(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SUN, DENGYUN(String), SUN DENGYUN(String), 0(Integer), 1681975541(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184969(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75918(Integer), 2(Integer), 184969(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75919(Integer), 2(Integer), 184969(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.432 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75918(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10063685B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Automatic execution method and device for operation of mobile terminal, and mobile terminal(String), 移动终端操作自动执行方法、装置及移动终端(String), US10063685B2(String), Embodiments of the present disclosure provide a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal. The method for automatically executing an operation of a mobile terminal includes: acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal, herein the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current; determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; and executing a preset operation according to the current state.(String), 本发明实施例提供一种自动执行移动终端操作的方法、装置及移动终端。 自动执行移动终端操作的方法包括:获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度,其中移动终端的当前移动/静止情况信息包括指示: 移动终端当前静止或移动终端当前移动; 根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态; 根据当前状态执行预设操作。(String), US15/329252(String), 1414944000(Integer), US10063685B2(String), 1535385600(Integer), 1535385600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 10(Integer), CN102884841A | CN103780748A | CN103943106A | CN202907027U | US20060116175A1 | US20110273378A1 | US20110304648A1 | US20120094714A1 | US20140028445A1 | US7676340B2(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184970(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0f66e0163c844609823b4c5a3a98359e.png(String), 184970(Integer), 0f66e0163c844609823b4c5a3a98359e.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Automatic execution method and device for operation of mobile terminal, and mobile terminal(String), 移动终端操作自动执行方法、装置及移动终端(String), US10063685B2(String), Embodiments of the present disclosure provide a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal. The method for automatically executing an operation of a mobile terminal includes: acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal, herein the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current; determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; and executing a preset operation according to the current state.(String), 本发明实施例提供一种自动执行移动终端操作的方法、装置及移动终端。 自动执行移动终端操作的方法包括:获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度,其中移动终端的当前移动/静止情况信息包括指示: 移动终端当前静止或移动终端当前移动; 根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态; 根据当前状态执行预设操作。(String), US15/329252(String), 1414944000(Integer), US10063685B2(String), 1535385600(Integer), 1535385600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 10(Integer), CN102884841A | CN103780748A | CN103943106A | CN202907027U | US20060116175A1 | US20110273378A1 | US20110304648A1 | US20120094714A1 | US20140028445A1 | US7676340B2(String), \20230420\0f66e0163c844609823b4c5a3a98359e.png(String), 17(Integer), 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 1. A method for automatically executing an operation of a mobile terminal, comprising:acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of a mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current;determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; andexecuting a preset operation according to the current state,wherein said determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature comprises:when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state; andwhen the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state, and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state.(String), 1.一种自动执行移动终端操作的方法,包括:获取移动终端当前动/静情况信息、内部温度和当前环境温度,其中,移动终端当前动/静情况信息包括表示移动终端当前静止或移动中的信息目前;根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态;和根据当前状态执行预设操作,其中,所述根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态包括:当移动终端当前处于移动状态时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则确定移动终端当前处于暴露环境中,并移动状态;若内部温度与当前环境温度的差值大于或等于预设第一温度阈值且小于或等于预设第二温度阈值,则确定移动终端当前状态为移动终端处于在浅隐蔽环境和移动状态下;若内部温度与当前环境温度的差值大于预设的第二温度阈值,则确定移动终端当前处于深隐环境和移动状态。和当前移动终端静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则确定移动终端当前处于暴露环境中,并静止状态,若内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端当前状态为处于隐藏环境和静止状态.2.根据权利要求1所述的方法,其中所述获取移动终端当前动/静情况信息包括:通过加速度传感器获取移动终端的运动加速度;和根据移动加速度获取移动终端当前的移动/静止情况信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 2. The method according to claim 1, wherein said acquiring current moving/stationary situation information of a mobile terminal comprises:acquiring a movement acceleration of the mobile terminal through an acceleration sensor; andacquiring the current moving/stationary situation information of the mobile terminal according to the movement acceleration.(String), 3.根据权利要求1所述的方法,其中所述获取移动终端的内部温度和当前环境温度包括:通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度;和通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前环境温度。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 3. The method according to claim 1, wherein said acquiring an internal temperature and a current environment temperature of a mobile terminal comprises:acquiring the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal; andacquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal.(String), 4.根据权利要求3所述的方法,其中第二温度传感器为多个第二温度传感器。所述通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前环境温度包括:通过多个第二温度传感器获取多个环境温度;和获取多个环境温度的期望值作为当前环境温度。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 4. The method according to claim 3, wherein the second temperature sensor is a plurality of second temperature sensors; and said acquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal comprises:acquiring a plurality of environment temperatures through the plurality of second temperature sensors; andacquiring an expected value of the plurality of environment temperatures as the current environment temperature.(String), 5.根据权利要求1所述的方法,其中,在根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端当前状态之前,该方法还包括:根据移动终端当前的CPU使用率和待机电流大小分别确定第一温度阈值、第二温度阈值和第三温度阈值。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 5. The method according to claim 1, wherein, before determining the current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature, the method further comprises:determining the first temperature threshold, the second temperature threshold and the third temperature threshold respectively according to a current CPU use rate and a standby current magnitude of the mobile terminal.(String), 6.非暂时性计算机程序,包括一种程序指令,其特征在于,所述程序指令在移动终端执行时,所述移动终端能够执行权利要求1所述的方法。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 6. A non-transitory computer program, comprising program instructions, wherein, when the program instructions are executed by a mobile terminal, the mobile terminal can execute the method according to claim 1.(String), 7.一种承载根据权利要求6的计算机程序的载体。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 7. A carrier carrying the computer program according to claim 6.(String), 8.一种自动执行移动终端操作的装置,包括:获取模块,用于获取移动终端的当前动/静状态信息、内部温度和当前环境温度,其中,移动终端当前动/静状态信息包括表示移动终端在当前或静止状态的信息。移动终端当前正在移动;第一确定模块,用于根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态;和执行模块,用于根据当前状态执行预设操作,其中,第一判断模块包括:第一判断子模块,用于当移动终端当前处于移动状态时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则将移动终端当前状态判断为:移动终端处于暴露环境和移动状态;若内部温度与当前环境温度之差大于或等于预设第一温度阈值且小于或等于预设第二温度阈值,则确定移动终端当前状态为移动终端处于浅隐环境和移动状态;如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则确定移动终端的当前状态为深隐蔽环境和移动状态。和第二判断子模块,用于当前移动终端静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则判断移动终端当前状态为:移动终端处于暴露环境和静止状态;如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端的当前状态为处于隐藏环境和静止状态。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 8. A device for automatically executing an operation of a mobile terminal, comprising:an acquisition module arranged to acquire current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current;a first determination module arranged to determine a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; andan execution module arranged to execute a preset operation according to the current state,wherein the first determination module comprises:a first determination sub-module arranged to, when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, determine that the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state; anda second determination sub-module arranged to, when the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state; and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state.(String), 9.根据权利要求8所述的装置,其中采集模块包括:第一获取子模块,用于通过加速度传感器获取移动终端的运动加速度;和第二获取子模块,用于根据移动加速度获取移动终端当前的移动/静止情况信息。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 9. The device according to claim 8, wherein the acquisition module comprises:a first acquisition sub-module arranged to acquire a movement acceleration of the mobile terminal through an acceleration sensor; anda second acquisition sub-module arranged to acquire the current moving/stationary situation information of the mobile terminal according to the movement acceleration.(String), 10.一个移动终端,包括:10.根据权利要求9所述的内部温度传感器、外部温度传感器、加速度传感器以及自动执行移动终端操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 10. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 9, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 11.根据权利要求8所述的装置,其中采集模块包括:第三获取子模块,用于通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度;和第四获取子模块,用于通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前的环境温度。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 11. The device according to claim 8, wherein the acquisition module comprises:a third acquisition sub-module arranged to acquire the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal; anda fourth acquisition sub-module arranged to acquire the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal.(String), 12.根据权利要求11所述的装置,其中第二温度传感器为多个第二温度传感器。第四采集子模块包括:第一获取单元,用于通过多个第二温度传感器获取多个环境温度;和第二获取单元,用于获取所述多个环境温度中的期望值作为当前环境温度。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 12. The device according to claim 11, wherein the second temperature sensor is a plurality of second temperature sensors; and the fourth acquisition sub-module comprises:a first acquisition unit arranged to acquire a plurality of environment temperatures through the plurality of second temperature sensors; anda second acquisition unit arranged to acquire an expected value of the plurality of environment temperatures as the current environment temperature.(String), 13.移动终端,包括:13.根据权利要求12所述的移动终端内部温度传感器、外部温度传感器、加速度传感器及自动执行操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 13. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 12, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 14.移动终端,包括:12.根据权利要求11所述的移动终端内部温度传感器、外部温度传感器、加速度传感器及自动执行操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 14. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 11, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 15.根据权利要求8所述的装置,还包括:第二确定模块,用于根据移动终端当前的CPU使用率和待机电流大小,分别确定第一温度阈值、第二温度阈值和第三温度阈值。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 15. The device according to claim 8, further comprising:a second determination module arranged to respectively determine the first temperature threshold, the second temperature threshold and the third temperature threshold according to a current CPU use rate and a standby current magnitude of the mobile terminal.(String), 16.移动终端,包括:16.根据权利要求15所述的内部温度传感器、外部温度传感器、加速度传感器以及自动执行移动终端操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 14(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 16. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 15, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 17.移动终端,包括:9.根据权利要求8所述的内部温度传感器、外部温度传感器、加速度传感器以及自动执行移动终端操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184970(Integer), 17. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 8, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 1(Integer), 16(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184970(Integer), TECHNICAL FIELD [0001]The present disclosure relates to a terminal application technology, and in particular to an operation of a mobile terminal. BACKGROUND [0002]When people use mobile phones in daily life, different magnitudes of vibration or volume will be set according to different scenarios. On traditional functional mobile phones, such mode is referred as a scenario mode. However, that function is gradually faded on smart phones, but demands of users are not changed thereby. For example, when a user is in an office, volume needs to be turned down; and when a mobile phone is put in a pocket or a bag, to avoid misses of calls and short messages, the volume of the mobile phone needs to be turned up; and when the user sleeps, the volume and the vibration need to be turned off or a flight mode is turned on. In daily life, since the users forgot to adjust volume, vibration and the like, great inconvenience is brought to mobile phone users. SUMMARY [0003]Embodiments of the present disclosure provide a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal, which can determine a current state of a mobile terminal according to an internal temperature, a current environment temperature and current moving/stationary situation information of the mobile terminal, to automatically execute a corresponding preset operation, such that the mobile terminal can automatically adjust related settings according to different scenarios. [0004]According to one aspect of the present disclosure, an embodiment of the present disclosure provides a method for automatically executing an operation of a mobile terminal. The method includes: acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of a mobile terminal, herein the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current; determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; and executing a preset operation according to the current state. [0005]In an exemplary embodiment, acquiring current moving/stationary situation information of the mobile terminal includes: acquiring a movement acceleration of the mobile terminal through an acceleration sensor; and acquiring the current moving/stationary situation information of the mobile terminal according to the movement acceleration. [0006]In an exemplary embodiment, acquiring an internal temperature and a current environment temperature of a mobile terminal includes: acquiring the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal; and acquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0007]In an exemplary embodiment, the second temperature sensor is a plurality of second temperature sensors; and acquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal includes: acquiring a plurality of environment temperatures through the plurality of second temperature sensors; and acquiring an expected value of the plurality of environment temperatures as the current environment temperature. [0008]In an exemplary embodiment, determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature includes the following operations. [0009]When the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state. [0010]When the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state; and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state. [0011]In an exemplary embodiment, before determining the current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature, the method further includes: respectively determining the first temperature threshold, the second temperature threshold and the third temperature threshold according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0012]According to another aspect of the present disclosure, an embodiment of the present disclosure further provides a device for automatically executing an operation of a mobile terminal. The device includes an acquisition module, a first determination module and an execution module. The acquisition module is arranged to acquire current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. The first determination module is arranged to determine a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature. The execution module is arranged to execute a preset operation according to the current state. [0013]In an exemplary embodiment, the acquisition module includes a first acquisition sub-module and a second acquisition sub-module. The first acquisition sub-module is arranged to acquire a movement acceleration of the mobile terminal through an acceleration sensor. The second acquisition sub-module is arranged to acquire the current moving/stationary situation information of the mobile terminal according to the movement acceleration. [0014]In an exemplary embodiment, the acquisition module includes a third acquisition sub-module and a fourth acquisition sub-module. The third acquisition sub-module is arranged to acquire the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal. The fourth acquisition sub-module is arranged to acquire the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0015]In an exemplary embodiment, the second temperature sensor is a plurality of second temperature sensors. The fourth acquisition sub-module includes a first acquisition unit and a second acquisition unit. The first acquisition unit is arranged to acquire a plurality of environment temperatures through the plurality of second temperature sensors. The second acquisition unit is arranged to acquire an expected value of the plurality of environment temperatures as the current environment temperature. [0016]In an exemplary embodiment, the first determination module includes a first determination sub-module and a second determination sub-module. [0017]The first determination sub-module is arranged to, when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, determine that the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state. [0018]The second determination sub-module arranged to, when the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state; and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state. [0019]In an exemplary embodiment, the device further includes: a second determination module arranged to respectively determine the first temperature threshold, the second temperature threshold and the third temperature threshold according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0020]According to another aspect of the present disclosure, an embodiment of the present disclosure further provides a mobile terminal, including: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the automobile execution device for the operation of the mobile terminal. Herein, the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal. The external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal. The acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. [0021]According to another aspect of the present disclosure, an embodiment of the present disclosure further provides a computer program and a carrier thereof. The computer program includes program instructions, and when the program instructions are executed by a mobile terminal, the mobile terminal can execute the method for automatically executing an operation of a mobile terminal. [0022]The above-mentioned technical solution of the embodiments of the present disclosure has the following beneficial effects: [0023]The method and device for automatically executing an operation of a mobile terminal, and the mobile terminal provided by the embodiments of the present disclosure can determine a current state of a mobile terminal according to an internal temperature, a current environment temperature and current moving/stationary situation information of the mobile terminal, to automatically execute a corresponding preset operation, such that the mobile terminal can automatically adjust related settings according to different scenarios. BRIEF DESCRIPTION OF DRAWINGS [0024]FIG. 1 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 1 of the present disclosure. [0025]FIG. 2 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 2 of the present disclosure. DETAILED DESCRIPTION [0026]The embodiments of the present disclosure will be described below in detail with reference to the drawings. It needs to be stated that the embodiments in the present disclosure and the features in the embodiments may be mutually and freely combined under the situation of no conflict. Although a logic sequence is illustrated in flowcharts, the illustrated or described steps may be executed according to a sequence different from a sequence here under certain circumstances. [0027]Aiming at the situation that calls are missed since terminal users often forget to adjust settings of mobile terminals according to different scenarios in the related art, an embodiment of the present disclosure provides a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal, which can determine a current state of a mobile terminal according to an internal temperature, a current environment temperature and current moving/stationary situation information of the mobile terminal, to automatically execute a corresponding preset operation, such that the mobile terminal can automatically adjust related settings according to different scenarios. [0028]FIG. 1 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 1 of the present disclosure. As illustrated in FIG. 1, the method includes the following steps S100-S104. [0029]In step S100, current moving/stationary situation information, an internal temperature and a current environment temperature of a mobile terminal are acquired. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. [0030]In step S102, a current state of the mobile terminal is determined according to the current moving/stationary situation information, the internal temperature and the current environment temperature. [0031]In step S104, a preset operation is executed according to the current state. [0032]In the method for automatically executing an operation of a mobile terminal, by acquiring the moving/stationary situation that the mobile terminal is stationary or moving at current and the internal temperature and the current environment temperature of the mobile terminal, the current state of the mobile terminal is determined and thus a preset operation corresponding to the current state is executed. [0033]According to the method for automatically executing an operation of a mobile terminal provided by the embodiment of the present disclosure, since the current state of the mobile terminal can be determined according to the current moving/stationary situation, the internal temperature and the current ambient temperature of the mobile terminal and the corresponding preset operation is executed, the mobile terminal can automatically adjust related settings according to different scenarios. [0034]In one specific embodiment of the present disclosure, the step S100 may specifically include the following operations. A movement acceleration of the mobile terminal is acquired through an acceleration sensor. The current moving/stationary situation information of the mobile terminal is acquired according to the movement acceleration. [0035]The mobile terminal may acquire the movement acceleration of the mobile terminal through the acceleration sensor and determine that the mobile terminal is stationary or moving according to the movement acceleration. For example, if the times of movement of the mobile terminal and a time interval of movement at each time detected by the acceleration sensor within a period of time t are smaller than preset thresholds, it may be determined that the mobile terminal is stationary. The purpose of doing that is to avoid the situation that certain vibration of the mobile terminal is mistakenly considered as the movement of the mobile terminal. For example, when the mobile terminal is put on a table and the mobile terminal is stationary, if the table is touched and shakes, the acceleration sensor will detect movement acceleration within short time. If it is determined that the mobile terminal is moving according to the movement acceleration, misjudgment will be caused. To avoid similar situations, a threshold may be set. [0036]In one specific embodiment of the present disclosure, the step S100 may specifically include the following operations. The internal temperature of the mobile terminal is acquired through a first temperature sensor arranged inside the mobile terminal. The current environment temperature of the mobile terminal is acquired through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0037]The mobile terminal may acquire the internal temperature and the current environment temperature of the mobile terminal through temperature sensors. Specifically, the internal temperature of the mobile terminal is acquired through a temperature sensor arranged inside the mobile terminal. The temperature sensor may be a temperature sensor self-contained by a chip used by the mobile terminal, and may also be a temperature sensor which is separately arranged. The current environment temperature is acquired through a temperature sensor arranged on the surface of the housing of the mobile terminal. [0038]In one specific embodiment of the present disclosure, the second temperature sensor is a plurality of second temperature sensors. The operation of acquiring the current environment temperature of the mobile terminal through the second temperature sensors includes the following operations. A plurality of environment temperatures are acquired through the plurality of second temperature sensors. An expected value of the plurality of environment temperatures is acquired as the current environment temperature. [0039]To enable the acquired current environment temperature to be more accurate, the current environment temperature may be obtained through temperatures acquired by a plurality of temperature sensors arranged on the surface of the housing of the mobile terminal. Specifically, the distribution of the temperature values measured by the plurality of temperature sensors may be analyzed and an expected value of the plurality of temperature values is acquired as the current environment temperature. [0040]In a specific embodiment of the present disclosure, the step S102 may specifically include the following operations. When the mobile terminal is stationary at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in an exposed environment and a stationary state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in a hidden environment and a stationary state. When the mobile terminal is moving at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset second temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in an exposed environment and moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset second temperature threshold and is smaller than or equal to a preset third temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in a shallow hidden environment and moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset third temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in a deep hidden environment and moving state. [0041]When the mobile terminal is stationary, environments in which the mobile terminal is located may be divided into two types. Herein, a first type is exposed environment, i.e., the mobile terminal is placed in an open space, e.g., on a tabletop; and a second type is hidden environment, i.e., the mobile terminal is placed in a closed space, e.g., in a drawer, a bag or a pocket of clothes which are not put on by a user. When the mobile terminal is in a hidden environment, since heat is not easy to dissipate in the closed space, the internal temperature and the current environment temperature of the mobile terminal have a great difference. Therefore, the environment in which the mobile terminal is located can be determined according to the difference between the internal temperature and the current environment temperature of the mobile terminal. [0042]When the mobile terminal is moving, environments in which the mobile terminal is located may be divided into three types. Herein, a first type is an exposed environment, i.e., the mobile terminal is placed in an open space, e.g., on a tabletop; a second type is a deep hidden environment, i.e., the mobile terminal is placed in a pocket of clothes which are put on by a user; and a third type is a shallow hidden environment, i.e., the mobile terminal is placed in other closed spaces, e.g., a bag. When the mobile terminal is placed in the pocket of the clothes which are put on by the user, since the mobile terminal is carried with the user, the automatic operation executed by the mobile terminal may be distinguished from the automatic operation executed when the mobile terminal is in other closed spaces. When the mobile terminal is in a deep hidden environment, i.e., the pocket of the clothes which are put on by the user, since the mobile terminal is carried with the user, the current environment temperature of the mobile terminal will be influenced by body temperature of the user; and simultaneously, since the internal space of the pocket is small, at this moment the difference between the internal temperature and the current environment temperature of the mobile terminal is greater than the difference therebetween when the mobile terminal is in a shallow hidden environment. Therefore, the environment in which the mobile terminal is located can be determined according to the difference between the internal temperature and the current environment temperature of the mobile terminal. [0043]In the method for automatically executing an operation of a mobile terminal provided by the embodiment of the present disclosure, the current state of the mobile terminal is determined by comparing the difference between the internal temperature and the current environment temperature of the mobile terminal with the preset first temperature threshold, second temperature threshold or third temperature threshold. However, actually the difference between the internal temperature and the current environment temperature of the mobile terminal will be influenced by factors a current CPU use rate and a standby current magnitude of the mobile terminal. Therefore, if the adopted preset first temperature threshold, second temperature threshold or third temperature threshold is a fixed value, a judgment result will be caused to be inaccurate. [0044]Therefore, in an exemplary embodiment, in the method for automatically executing an operation of a mobile terminal, before the current state of the mobile terminal is determined according to the current moving/stationary situation information, the internal temperature and the current environment temperature, the method further includes the following step. The first temperature threshold, the second temperature threshold and the third temperature threshold are respectively determined according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0045]By respectively determining the first temperature threshold, the second temperature threshold and the third temperature threshold according to the current CPU use rate and the standby current magnitude of the mobile terminal, the influence caused by the current CPU use rate and the standby current magnitude of the mobile terminal is avoided and the current state of the mobile terminal can be more accurately determined. [0046]FIG. 2 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 2 of the present disclosure. As illustrated in FIG. 2, the method includes the following steps S200-S228. [0047]In step S200, movement information of a mobile terminal is acquired through an acceleration sensor, and an internal temperature and a current environment temperature of the mobile terminal are acquired through temperature sensors. [0048]In step S202, whether the mobile terminal is moving is judged. If yes, step S204 is executed, and if no, step S220 is executed. Specifically, if the movement information detected by the acceleration sensor within a period of time indicates that the mobile terminal is stationary, or the movement information of the mobile terminal detected by the acceleration sensor within such period of time indicates that the mobile terminal is moved but a time interval of movement is smaller than a preset threshold, it is considered that the mobile terminal is stationary. If the movement information detected by the acceleration sensor within a period of time indicates that the mobile terminal is moving, or the movement information of the mobile terminal detected by the acceleration sensor within such period of time indicates that the mobile terminal is moved and the time interval of movement is greater than the preset threshold, it is considered as that the mobile terminal is moving. [0049]In step S204, whether a difference between the internal temperature and the current environment temperature is smaller than a preset first threshold F1 is judged. If yes, step S206 is executed, and if no, step S210 is executed. Herein, the first threshold F1 is a variable which is determined according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0050]In step S206, the mobile terminal is in an exposed environment and is moving, e.g., a user holds the mobile terminal in a hand. [0051]In step S208, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a mute mode. [0052]In step S210, whether the difference between the internal temperature and the current environment temperature is greater than or equal to a preset second threshold F2 is judged. If yes, step S212 is executed, and if no, step S216 is executed. Herein, the second threshold F2 is a variable which is determined according to the current CPU use rate and the standby current magnitude of the mobile terminal. [0053]In step S212, the mobile terminal is in a shallow hidden environment and is moving, e.g., the user places the mobile terminal in a bag backpacked by the user during walking. [0054]In step S214, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a ringing mode and a ring volume magnitude is set. [0055]In step S216, the mobile terminal is in a deep hidden environment and is moving, e.g., the user places the mobile terminal in a pocket of clothes which are put on during walking. [0056]In step S218, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a vibration mode. [0057]In step S220, whether the difference between the internal temperature and the current environment temperature is smaller than a preset third threshold F3 is judged. If yes, step S222 is executed, and if no, step S226 is executed. Herein, the third threshold F3 is a variable which is determined according to the current CPU use rate and the standby current magnitude of the mobile terminal. [0058]In step S222, the mobile terminal is in an exposed environment and is stationary, e.g., the mobile terminal is placed on a table. [0059]In step S224, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a mute mode. [0060]In step S226, the mobile terminal is in a hidden environment and is stationary, e.g., the mobile terminal is placed in a bag or a drawer. [0061]In step S228, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a ringing mode and a ring volume is set. [0062]An embodiment of the present disclosure further provides a device for automatically executing an operation of a mobile terminal, including an acquisition module, a first determination module and an execution module. The acquisition module is arranged to acquire current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. The first determination module is arranged to determine a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature. The execution module is arranged to execute a preset operation according to the current state. [0063]In the device for automatically executing an operation of a mobile terminal, the acquisition module includes a first acquisition sub-module and a second acquisition sub-module. The first acquisition sub-module is arranged to acquire a movement acceleration of the mobile terminal through an acceleration sensor. The second acquisition sub-module is arranged to acquire the current moving/stationary situation information of the mobile terminal according to the movement acceleration. [0064]In the device for automatically executing an operation of a mobile terminal, the acquisition module includes a third acquisition sub-module and a fourth acquisition sub-module. The third acquisition sub-module is arranged to acquire the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal. The fourth acquisition sub-module is arranged to acquire the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0065]In the device for automatically executing an operation of a mobile terminal, the second temperature sensor is a plurality of second temperature sensors; and the fourth acquisition sub-module includes a first acquisition unit and a second acquisition unit. The first acquisition unit is arranged to acquire a plurality of environment temperatures through the plurality of second temperature sensors. The second acquisition unit is arranged to acquire an expected value of the plurality of environment temperatures as the current environment temperature. [0066]In the device for automatically executing an operation of a mobile terminal, the first determination module includes a first determination sub-module and a second determination sub-module. [0067]The first determination sub-module is arranged to, when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the(String), 技术领域 [0001] 本发明涉及一种终端应用技术,尤其涉及一种移动终端的操作。 背景 [0002] 人们在日常生活中使用手机时,会根据不同的场景设置不同幅度的震动或音量。 在传统的功能手机上,这种模式被称为场景模式。 不过,该功能在智能手机上逐渐淡出,但用户的需求并没有因此而改变。 例如,当用户在办公室时,需要调低音量; 手机放在口袋或包里时,为了避免漏接电话和短信,需要调高手机音量。 并且当用户睡觉时,需要关闭音量和振动或者开启飞行模式。 在日常生活中,由于用户忘记调节音量、振动等,给手机用户带来了极大的不便。 概括 [0003] 本发明实施例提供一种自动执行移动终端操作的方法、装置及移动终端,能够根据内部温度、当前环境温度和当前移动/静止确定移动终端的当前状态。 移动终端的情境信息,自动执行相应的预设操作,使移动终端能够根据不同的场景自动调整相关设置。 [0004] 根据本公开的一个方面,本公开的实施例提供了一种自动执行移动终端的操作的方法。 该方法包括:获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度,其中,移动终端的当前移动/静止情况信息包括移动终端当前处于静止状态或当前处于静止状态的信息。 移动终端在当前移动; 根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态; 根据当前状态执行预设操作。 [0005] 优选地,获取移动终端当前的移动/静止情况信息包括: 通过加速度传感器获取移动终端的移动加速度; 根据移动加速度获取移动终端当前的移动/静止情况信息。 [0006] 在一个示例性实施例中,获取移动终端的内部温度和当前环境温度包括: 通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度; 通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前的环境温度。 [0007] 在一个示例性实施例中,第二温度传感器是多个第二温度传感器; 通过设置在移动终端机壳表面的第二温度传感器获取移动终端当前的环境温度包括: 通过多个第二温度传感器获取多个环境温度; 获取多个环境温度的期望值作为当前环境温度。 [0008] 在示例性实施例中,根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态包括以下操作。 [0009]当移动终端当前移动时,如果内部温度与当前环境温度的差值小于预设的第一温度阈值,则确定移动终端当前状态为暴露环境 和移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值且小于或等于预设的第二温度阈值,则确定移动终端的当前状态为 终端处于浅层隐藏环境和移动状态; 如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则确定移动终端当前的状态为移动终端处于深度隐藏环境和移动状态。 [0010] 当移动终端当前静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则判断移动终端当前状态为暴露环境 和静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端的当前状态为移动终端处于隐藏环境和静止状态。 [0011] 在一个示例性实施例中,在根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态之前,该方法还包括:分别确定第一温度阈值、第二温度阈值和 第三温度阈值根据移动终端当前的CPU使用率和待机电流大小。 [0012] 根据本发明的另一方面,本发明实施例还提供一种自动执行移动终端操作的装置。 该装置包括获取模块、第一判断模块和执行模块。 获取模块用于获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 第一确定模块用于根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态。 执行模块用于根据当前状态执行预设操作。 [0013] 在一个示例性实施例中,获取模块包括第一获取子模块和第二获取子模块。 第一获取子模块用于通过加速度传感器获取移动终端的运动加速度。 第二获取子模块用于根据移动加速度获取移动终端当前的移动/静止情况信息。 [0014] 在一个示例性实施例中,获取模块包括第三获取子模块和第四获取子模块。 第三获取子模块用于通过移动终端内部的第一温度传感器获取移动终端的内部温度。 第四获取子模块用于通过设置在移动终端机壳表面的第二温度传感器获取移动终端当前的环境温度。 [0015]在示例性实施例中,第二温度传感器是多个第二温度传感器。 第四获取子模块包括第一获取单元和第二获取单元。 第一获取单元用于通过多个第二温度传感器获取多个环境温度。 第二获取单元用于获取多个环境温度的期望值作为当前环境温度。 [0016] 在一个示例性实施例中,第一确定模块包括第一确定子模块和第二确定子模块。 [0017] 第一判断子模块,用于在移动终端当前移动时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则判断移动终端当前的状态为: 移动终端处于暴露环境和移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值且小于或等于预设的第二温度阈值,则确定移动终端的当前状态为移动终端 处于浅隐环境和运动状态; 如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则判断移动终端当前的状态为移动终端处于深度隐藏环境和移动状态。 [0018] 第二确定子模块,用于当移动终端当前静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则确定移动终端当前状态为 移动终端处于暴露环境和静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端当前的状态为移动终端处于隐藏环境和静止状态。 [0019] 优选地,该装置还包括: 第二确定模块,用于根据移动终端当前的CPU使用率和待机电流大小分别确定第一温度阈值、第二温度阈值和第三温度阈值。 [0020] 根据本发明的另一方面,本发明实施例还提供了一种移动终端,包括:内部温度传感器、外部温度传感器、加速度传感器和用于移动终端操作的汽车执行装置。 这里,内部温度传感器用于获取移动终端的内部温度。 外部温度传感器用于获取移动终端的当前环境温度。 加速度传感器用于获取移动终端当前的移动/静止情况信息。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 [0021] 根据本发明的另一方面,本发明实施例还提供了一种计算机程序及其载体。 计算机程序包括程序指令,当程序指令被移动终端执行时,移动终端可以执行自动执行移动终端操作的方法。 [0022] 本发明实施例的上述技术方案具有以下有益效果: [0023]本发明实施例提供的移动终端自动执行操作的方法和装置,以及移动终端可以根据内部温度、当前环境温度和当前移动/静止确定移动终端的当前状态 移动终端的情境信息,自动执行相应的预设操作,使移动终端能够根据不同的场景自动调整相关设置。 附图说明 [0024] 图1为本发明实施例一提供的一种自动执行移动终端操作的方法的流程图。 [0025] 图2为本发明实施例二提供的一种自动执行移动终端操作的方法流程图。 详细说明 [0026] 下面结合附图对本发明实施例进行详细说明。 需要说明的是,本发明实施例和实施例中的特征可以在不冲突的情况下相互自由组合。 尽管在流程图中示出了逻辑顺序,但是在某些情况下,可以根据与此处的顺序不同的顺序来执行示出或描述的步骤。 [0027] 针对相关技术中终端用户根据不同的场景,经常忘记调整移动终端的设置而导致漏接电话的情况,本发明实施例提供了一种自动执行移动终端操作的方法及装置, 移动终端,可根据移动终端的内部温度、当前环境温度和当前移动/静止情况信息确定移动终端的当前状态,自动执行相应的预设操作,使移动终端能够 根据不同场景自动调整相关设置。 [0028] 图1为本发明实施例一提供的一种自动执行移动终端操作的方法的流程图。 如图1所示,该方法包括以下步骤S 100 -S 104 . [0029] 在步骤 S 100 ,获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 [0030] 在步骤 S 102 ,根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态。 [0031] 在步骤 S 104 ,根据当前状态执行预设操作。 [0032] 一种自动执行移动终端操作的方法,通过获取移动终端当前静止或移动的移动/静止情况以及移动终端的内部温度和当前环境温度,获取移动终端的当前状态。 终端被确定,从而执行与当前状态对应的预设操作。 [0033] 根据本发明实施例提供的自动执行移动终端操作的方法,由于可以根据当前移动/静止情况、内部温度和当前环境温度确定移动终端的当前状态。 并执行相应的预设操作,移动终端可以根据不同的场景自动调整相关设置。 [0034] 在本发明的一个具体实施例中,步骤S 100具体可以包括以下操作。 通过加速度传感器获取移动终端的运动加速度。 根据移动加速度获取移动终端当前的移动/静止情况信息。 [0035] 移动终端可以通过加速度传感器获取移动终端的移动加速度,并根据移动加速度判断移动终端是静止的还是移动的。 例如,如果移动终端的移动次数和加速度传感器在一段时间t内检测到的每次移动的时间间隔小于预设阈值,则可以确定移动终端是静止的。 这样做的目的是为了避免将移动终端的某些振动误认为是移动终端的移动。 例如,当移动终端放在桌子上且移动终端静止时,如果桌子被触摸和晃动,加速度传感器将在短时间内检测到运动加速度。 如果根据移动加速度判断移动终端正在移动,则会造成误判。 为了避免类似情况,可以设置阈值。 [0036] 在本发明的一个具体实施例中,步骤S 100 具体可以包括以下操作。 通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度。 移动终端当前的环境温度是通过设置在移动终端外壳表面的第二温度传感器获取的。 [0037] 移动终端可以通过温度传感器获取移动终端的内部温度和当前环境温度。 具体地,通过设置在移动终端内部的温度传感器获取移动终端的内部温度。 温度传感器可以是移动终端使用的芯片自带的温度传感器,也可以是单独设置的温度传感器。 当前环境温度是通过设置在移动终端外壳表面的温度传感器获取的。 [0038] 在本发明的一个具体实施例中,所述第二温度传感器为多个第二温度传感器。 通过第二温度传感器获取移动终端当前环境温度的操作包括以下操作。 通过多个第二温度传感器获取多个环境温度。 获取多个环境温度的期望值作为当前环境温度。 [0039] 为了使获取的当前环境温度更加准确,可以通过设置在移动终端外壳表面的多个温度传感器获取的温度来获取当前环境温度。 具体地,可以分析多个温度传感器测量的温度值的分布,获取多个温度值的期望值作为当前环境温度。 [0040] 在本发明的一个具体实施例中,步骤S 102具体可以包括以下操作。 当移动终端当前静止时,如果内部温度与当前环境温度的差值小于预设的第一温度阈值,则确定移动终端的当前状态为处于暴露环境中,并且 静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值,则确定移动终端的当前状态为移动终端处于隐藏环境和静止状态。 当移动终端在当前移动时,如果内部温度与当前环境温度的差值小于预设的第二温度阈值,则确定移动终端的当前状态为移动终端处于暴露环境中, 移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第二温度阈值且小于或等于预设的第三温度阈值,则确定移动终端的当前状态为移动终端 处于浅隐环境和运动状态; 若内部温度与当前环境温度的差值大于预设的第三温度阈值,则确定移动终端当前状态为深隐环境移动状态。 [0041] 当移动终端静止时,移动终端所处的环境可以分为两种。 这里,第一类是暴露环境,即移动终端放置在开放空间,例如桌面上; 第二种是隐蔽环境,即将移动终端放置在封闭的空间内,如抽屉、包或用户不穿的衣服口袋中。 当移动终端处于隐蔽环境时,由于在封闭空间内热量不易散发,因此移动终端内部温度与当前环境温度存在较大差异。 因此,可以根据移动终端内部温度与当前环境温度的差值来确定移动终端所处的环境。 [0042] 当移动终端在移动时,移动终端所处的环境可以分为三种。 这里,第一类是暴露环境,即移动终端放置在空旷的空间,例如桌面上; 第二种是深度隐蔽环境,即移动终端放置在用户穿上的衣服口袋中。 第三种是浅隐蔽环境,即移动终端放置在其他封闭空间,例如包中。 当移动终端放置在用户所穿衣服的口袋中时,由于移动终端是随身携带的,因此移动终端执行的自动操作可以与移动终端执行的自动操作区分开来。 在其他封闭空间。 当移动终端处于较深的隐蔽环境,即用户穿上的衣服口袋时,由于移动终端是随身携带的,因此移动终端当前的环境温度会受到体温的影响 用户的; 同时,由于口袋内部空间较小,此时移动终端内部温度与当前环境温度的差值大于移动终端处于浅隐藏环境时的差值。 因此,可以根据移动终端内部温度与当前环境温度的差值来确定移动终端所处的环境。 [0043]本发明实施例提供的一种自动执行移动终端操作的方法,通过将移动终端内部温度与当前环境温度的差值与预设值进行比较,确定移动终端的当前状态。 第一温度阈值、第二温度阈值或第三温度阈值。 然而,实际上移动终端内部温度与当前环境温度的差异会受到移动终端当前CPU使用率和待机电流大小等因素的影响。 因此,如果采用预设的第一温度阈值、第二温度阈值或第三温度阈值为固定值,将导致判断结果不准确。 [0044] 因此,在示例性实施例中,在自动执行移动终端操作的方法中,在根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态之前, 该方法还包括以下步骤。 第一温度阈值、第二温度阈值和第三温度阈值分别根据移动终端的当前CPU使用率和待机电流大小确定。 [0045] 通过根据移动终端当前CPU使用率和待机电流大小分别确定第一温度阈值、第二温度阈值和第三温度阈值,当前CPU使用率和待机电流大小对移动终端的影响 避免了移动终端,可以更准确的判断移动终端的当前状态。 [0046] 图2为本发明实施例二提供的一种自动执行移动终端操作的方法流程图。 如图2所示,该方法包括以下步骤S 200 -S 228 . [0047] 在步骤 S 200 ,通过加速度传感器获取移动终端的运动信息,通过温度传感器获取移动终端的内部温度和当前环境温度。 [0048] 在步骤 S 202 ,判断移动终端是否在移动。 如果是,步骤 S 204 被执行,如果没有,步骤S 220 被执行。 具体地,如果加速度传感器在一段时间内检测到的移动信息表明移动终端是静止的,或者加速度传感器在这段时间内检测到移动终端的移动信息表明移动终端是移动的,但是 移动的时间间隔小于预设阈值,则认为移动终端静止。 如果加速度传感器在一段时间内检测到的移动信息表明移动终端正在移动,或者加速度传感器在该时间段内检测到移动终端的移动信息表明移动终端移动了,则该时间 移动间隔大于预设阈值,则认为移动终端正在移动。 [0049] 在步骤 S 204 ,内部温度与当前环境温度的差值是否小于预设的第一阈值F 1 被判断。 如果是,步骤 S 206 被执行,如果没有,步骤S 210 被执行。 其中,第一阈值 F 1 是根据移动终端当前CPU使用率和待机电流大小确定的变量。 [0050] 在步骤 S 206 ,移动终端处于暴露环境中并且正在移动,例如,用户将移动终端握在手中。 [0051] 在步骤 S 208 ,移动终端执行相应的预设操作,例如将移动终端调整为静音模式。 [0052] 在步骤 S 210 ,内部温度与当前环境温度的差值是否大于或等于预设的第二阈值F 2被判断。 如果是,步骤 S 212 被执行,如果没有,步骤S 216 被执行。 这里,第二阈值 F 2 是根据当前CPU使用率和移动终端的待机电流大小确定的变量。 [0053] 在步骤 S 212 ,移动终端处于浅层隐蔽环境中,正在移动,例如,用户在行走时将移动终端放在用户背包的包中。 [0054] 在步骤 S 214 ,移动终端执行相应的预设操作,例如将移动终端调整为响铃模式,设置响铃音量大小。 [0055] 在步骤 S 216 ,移动终端处于深隐环境中,并且正在移动,例如,用户将移动终端放置在行走时穿上的衣服口袋中。 [0056] 在步骤 S 218 ,移动终端执行相应的预设操作,例如将移动终端调整为振动模式。 [0057] 在步骤 S 220 ,内部温度与当前环境温度的差值是否小于预设的第三阈值F 3 被判断。 如果是,步骤 S 222 被执行,如果没有,步骤S 226 被执行。 这里,第三阈值 F 3 是根据当前CPU使用率和移动终端的待机电流大小确定的变量。 [0058] 在步骤 S 222 ,移动终端处于暴露环境中并且是静止的,例如,移动终端被放置在桌子上。 [0059] 在步骤 S 224 ,移动终端执行相应的预设操作,例如将移动终端调整为静音模式。 [0060] 在步骤 S 226 ,移动终端处于隐蔽环境中,是静止的,例如,移动终端被放置在包或抽屉中。 [0061] 在步骤 S 228 ,移动终端执行相应的预设操作,例如,将移动终端调整为响铃模式并设置响铃音量。 [0062] 本发明实施例还提供一种自动执行移动终端操作的装置,包括获取模块、第一判断模块和执行模块。 获取模块用于获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 第一确定模块用于根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态。 执行模块用于根据当前状态执行预设操作。 [0063] 在自动执行移动终端操作的装置中,获取模块包括第一获取子模块和第二获取子模块。 第一获取子模块用于通过加速度传感器获取移动终端的运动加速度。 第二获取子模块用于根据移动加速度获取移动终端当前的移动/静止情况信息。 [0064] 在自动执行移动终端操作的装置中,获取模块包括第三获取子模块和第四获取子模块。 第三获取子模块用于通过移动终端内部的第一温度传感器获取移动终端的内部温度。 第四获取子模块用于通过设置在移动终端机壳表面的第二温度传感器获取移动终端当前的环境温度。 [0065]在移动终端自动执行操作的装置中,第二温度传感器为多个第二温度传感器。 第四获取子模块包括第一获取单元和第二获取单元。 第一获取单元用于通过多个第二温度传感器获取多个环境温度。 第二获取单元用于获取多个环境温度的期望值作为当前环境温度。 [0066] 在自动执行移动终端操作的装置中,第一判断模块包括第一判断子模块和第二判断子模块。 [0067] 第一判断子模块,用于在移动终端当前移动时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则判断移动终端当前的状态为: 移动终端处于暴露环境和移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值且小于或等于预设的第二温度阈值,则确定移动终端的当前状态为移动终端 处于浅隐环境和运动状态; 如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则判断移动终端当前的状态为移动终端处于深度隐藏环境和移动状态。 [0068] 第二判断子模块,用于当移动终端当前静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则判断移动终端当前的状态为 移动终端处于暴露环境和静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端当前的状态为移动终端处于隐藏环境和静止状态。 [0069] 在自动执行移动终端操作的装置中,该装置还包括第二确定模块,用于根据当前CPU使用率和待机电流分别确定第一温度阈值、第二温度阈值和第三温度阈值。 移动终端的规模。 [0070] 本发明实施例还提供一种移动终端,包括内置温度传感器、外置温度传感器、加速度传感器和用于移动终端运行的汽车执行装置。 内部温度传感器用于获取移动终端的内部温度。 外部温度传感器用于获取移动终端的当前环境温度。 加速度传感器用于获取移动终端当前的移动/静止情况信息。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 [0071] 本领域普通技术人员可以理解,上述方法中的全部或部分步骤可以通过程序指令相关硬件来完成,该程序可以存储在只读存储器等计算机可读存储介质中。 等等。 或者,上述实施例中的全部或部分步骤也可以采用一个或多个集成电路来实现。 相应地,上述实施例中的各个模块/单元可以通过硬件实现,也可以通过软件功能模块实现。 本公开不限于任何特定形式的硬件和软件的组合。 [0072]当然,本发明还可以有其他各种环境。 本领域的技术人员可以在不脱离本发明的原则和实质的情况下,根据本发明进行各种相应的修改和变化。 但是,这种相应的修改和变化仍应包含在本发明权利要求的保护范围之内。 工业适用性 [0073] 根据本发明实施例提供的移动终端自动执行操作的方法、装置及移动终端,通过获取当前移动/静止情况信息、内部温度,确定移动终端的当前状态。 移动终端当前的环境温度; 根据当前状态执行预设操作,使移动终端可以根据不同场景自动调整相关设置。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105338167A(String), CN105338167B(String), EP3179704A1(String), EP3179704A4(String), EP3179704B1(String), US10063685B2(String), US20170272567A1(String), WO2015154446A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105338167A(String), CN105338167B(String), EP3179704A1(String), EP3179704A4(String), EP3179704B1(String), US10063685B2(String), US20170272567A1(String), WO2015154446A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10063685B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105338167A(String), CN105338167B(String), EP3179704A1(String), EP3179704A4(String), EP3179704B1(String), US10063685B2(String), US20170272567A1(String), WO2015154446A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), CN105338167A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), CN105338167B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.678 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.678 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), EP3179704A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.689 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), EP3179704A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), EP3179704B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), US10063685B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), US20170272567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270653(Integer), WO2015154446A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10063685B2(String), US10063685B2(String), 1535385600(Integer), 270653(Integer), 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.755 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184970(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184970(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184970(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184970(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130104163A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Encryption method for television service of mobile terminal, mobile terminal and server(String), 移动终端电视业务加密方法、移动终端及服务器(String), US20130104163A1(String), The disclosure provides an encryption method for a television service of a mobile terminal, a mobile terminal and a server. The method comprises: a mobile terminal ordering and obtaining a program that has not been subscribed; the mobile terminal encrypting the program to shield a part of data of the program; and the mobile terminal playing the program that is encrypted. The encryption method for the television service of the mobile terminal, the mobile terminal and the server provided in the disclosure can encrypt the program, which is ordered but has not been subscribed by the user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program, thus certain experience can be enjoyed by the user, and the content of the program is protected.(String), 本发明提供一种移动终端的电视业务加密方法、移动终端及服务器。 该方法包括:移动终端订购并获取未订阅的节目; 移动终端对程序进行加密,以屏蔽程序的部分数据; 移动终端播放加密后的节目。 本发明提供的移动终端电视业务加密方法、移动终端和服务器可以在移动终端侧或服务器侧对用户已点播但尚未订阅的节目进行加密,从而 将节目的部分数据屏蔽后播放节目,用户可以享受到一定的体验,节目内容受到保护。(String), US13/700954(String), 1288800000(Integer), US20130104163A1(String), 1366819200(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 11(Integer), EP2079228A1 | US20040019787A1 | US20050070248A1 | US20070092082A1 | US20070201695A1 | US20080134232A1 | US20100333130A1 | US20110019816A1 | US4225884A | WO2006134517A2 | WO2008053576A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184971(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b63634b6f9ad489d9fdd3f17696adacc.png(String), 184971(Integer), b63634b6f9ad489d9fdd3f17696adacc.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Encryption method for television service of mobile terminal, mobile terminal and server(String), 移动终端电视业务加密方法、移动终端及服务器(String), US20130104163A1(String), The disclosure provides an encryption method for a television service of a mobile terminal, a mobile terminal and a server. The method comprises: a mobile terminal ordering and obtaining a program that has not been subscribed; the mobile terminal encrypting the program to shield a part of data of the program; and the mobile terminal playing the program that is encrypted. The encryption method for the television service of the mobile terminal, the mobile terminal and the server provided in the disclosure can encrypt the program, which is ordered but has not been subscribed by the user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program, thus certain experience can be enjoyed by the user, and the content of the program is protected.(String), 本发明提供一种移动终端的电视业务加密方法、移动终端及服务器。 该方法包括:移动终端订购并获取未订阅的节目; 移动终端对程序进行加密,以屏蔽程序的部分数据; 移动终端播放加密后的节目。 本发明提供的移动终端电视业务加密方法、移动终端和服务器可以在移动终端侧或服务器侧对用户已点播但尚未订阅的节目进行加密,从而 将节目的部分数据屏蔽后播放节目,用户可以享受到一定的体验,节目内容受到保护。(String), US13/700954(String), 1288800000(Integer), US20130104163A1(String), 1366819200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 11(Integer), EP2079228A1 | US20040019787A1 | US20050070248A1 | US20070092082A1 | US20070201695A1 | US20080134232A1 | US20100333130A1 | US20110019816A1 | US4225884A | WO2006134517A2 | WO2008053576A1(String), \20230420\b63634b6f9ad489d9fdd3f17696adacc.png(String), 16(Integer), 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.845 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.846 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.846 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 1. An encryption method for a television service of a mobile terminal, comprising:a mobile terminal ordering and obtaining a program that has not been subscribed;the mobile terminal encrypting the program to shield a part of data of the program; andthe mobile terminal playing the program that is encrypted.(String), 1、一种移动终端电视业务的加密方法,包括:移动终端点播获取未订阅节目;移动终端对节目进行加密,屏蔽节目的部分数据;和移动终端播放加密后的节目。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 2. The encryption method for the television service of the mobile terminal according to claim 1, wherein the step of the mobile terminal ordering and obtaining the program that has not been subscribed comprises:when ordering the program that has not been subscribed, the mobile terminal sending an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; anddownloading and obtaining the program with the decryption key.(String), 2.根据权利要求1所述的移动终端电视业务的加密方法,其中移动终端点播并获取未订阅节目的步骤包括:在点播未订阅的节目时,移动终端发送移动终端的识别码和移动终端用户识别卡的卡号,获取节目的解密密钥。和下载并获取带有解密密钥的程序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 3. The encryption method for the television service of the mobile terminal according to claim 1, wherein the identification code of the mobile terminal is a model number of the mobile terminal.(String), 3.根据权利要求1所述的移动终端电视业务的加密方法,其中移动终端的识别码为移动终端的型号。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 4. The encryption method for the television service of the mobile terminal according to claim 1, wherein the step of encrypting the program to shield a part of data of the program comprises:creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/orperforming audio mixing on a part of audio data of the program.(String), 4.根据权利要求1所述的移动终端电视业务的加密方法,其中对程序进行加密以屏蔽程序的部分数据的步骤包括:建立至少一色彩干扰区,并将该至少一色彩干扰区覆盖于节目的部分视频数据上;和/或对节目的部分音频数据进行混音。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 5. (canceled)6. (canceled)7. (canceled)8. (canceled)9. An encryption method for a television service of a mobile terminal, comprising:when a mobile terminal orders a program that has not been subscribed, a server encrypting the program to shield a part of data of the program, and creating a new channel for the program that is encrypted; andthe server sending information about the new channel and a decryption key to the mobile terminal.(String), 5.(已取消)6.(已取消)7.(已取消)8.(已取消)9、一种移动终端电视业务的加密方法,包括:当移动终端点播未订阅的节目时,服务器对节目进行加密,屏蔽节目的部分数据,并为加密后的节目创建新的频道。和服务器向移动终端发送新频道信息和解密密钥。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 10. The encryption method for the television service of the mobile terminal according to claim 9, wherein the step of encrypting the program to shield a part of data of the program comprises:creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/orperforming audio mixing on a part of audio data of the program.(String), 10.根据权利要求9所述的移动终端电视业务的加密方法,其中对程序进行加密以屏蔽程序的部分数据的步骤包括:建立至少一色彩干扰区,并将该至少一色彩干扰区覆盖于节目的部分视频数据上;和/或对节目的部分音频数据进行混音。11、一种服务器,用于移动终端的电视业务,其中服务器包括:加密模块,用于当移动终端点播未订阅的节目时,对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道;和发送模块,用于向移动终端发送新频道信息和解密密钥。(String), 1(Integer), 5(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 11. A server, used for a television service of a mobile terminal, wherein the server comprises:an encryption module, configured to, when a mobile terminal orders a program that has not been subscribed, encrypt the program to shield a part of data of the program, and create a new channel for the program that is encrypted; anda sending module, configured to send information about the new channel and a decryption key to the mobile terminal.(String), 12.根据权利要求11所述的服务器,其中加密模块还包括:视频干扰单元,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上;和/或音频干扰单元,用于对节目的部分音频数据进行混音。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 12. The server according to claim 11, wherein the encryption module further comprises:a video interference unit, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/oran audio interference unit, configured to perform audio mixing on a part of audio data of the program.(String), 13.根据权利要求2所述的移动终端电视业务的加密方法,其中移动终端的识别码为移动终端的型号。(String), 1(Integer), 7(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 13. The encryption method for the television service of the mobile terminal according to claim 2, wherein the identification code of the mobile terminal is a model number of the mobile terminal.(String), 14.根据权利要求2所述的移动终端电视业务的加密方法,其中对程序进行加密以屏蔽程序的部分数据的步骤包括:建立至少一色彩干扰区,并将该至少一色彩干扰区覆盖于节目的部分视频数据上;和/或对节目的部分音频数据进行混音。(String), 1(Integer), 8(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 14. The encryption method for the television service of the mobile terminal according to claim 2, wherein the step of encrypting the program to shield a part of data of the program comprises:creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/orperforming audio mixing on a part of audio data of the program.(String), 15.(已取消)16.(已取消)(String), 1(Integer), 9(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184971(Integer), 15. (canceled)16. (canceled)(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184971(Integer), FIELD OF THE INVENTION [0001]The disclosure relates to the technical field of communications, in particular to an encryption method for a television service of a mobile terminal, a mobile terminal and a server. BACKGROUND OF THE INVENTION [0002]A television service of a mobile terminal such as a mobile phone is actually realized in such a way that: a streaming media technology is utilized to launch a mobile terminal television as a data service, and what users see is downloaded video data. In a current encryption method for a television service of a mobile terminal, all television programs provided by a service provider are encrypted, a user is authorized by the service provider only when the user has subscribed a mobile terminal television program, then the user can order the subscribed program. Such encryption method for the television service of the mobile terminal has one defect: usually, users want to watch a part of data of a program before subscribing the program to decide whether to subscribe the program depending on the experience, however, according to the current encryption method for the television service of the mobile terminal, for users who have not subscribed the program, data is completely shielded and cannot be watched, the users cannot have experience of the program, therefore, the popularization of the television service of the mobile phone is limited. SUMMARY OF THE INVENTION [0003]The disclosure provides an encryption method for a television service of a mobile terminal, a mobile terminal and a server, so that the service provider can popularize the television service of the mobile terminal such as a mobile phone better. [0004]The disclosure proposes an encryption method for a television service of a mobile terminal, comprising: a mobile terminal ordering and obtaining a program that has not been subscribed; the mobile terminal encrypting the program to shield a part of data of the program; and the mobile terminal playing the program that is encrypted. [0005]Preferably, the step of the mobile terminal ordering and obtaining the program that has not been subscribed comprises: when ordering the program that has not been subscribed, the mobile terminal sending an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; and downloading and obtaining the program with the decryption key. [0006]Preferably, the identification code of the mobile terminal is a model number of the mobile terminal. [0007]Preferably, the step of encrypting the program to shield a part of data of the program comprises: creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/or, performing audio mixing on a part of audio data of the program. [0008]The disclosure proposes a mobile terminal, comprising: an obtaining module, configured to order and obtain a program that has not been subscribed; an encryption module, configured to encrypt the program to shield a part of data of the program; and a playing module, configured to play the program that is encrypted. [0009]Preferably, the obtaining module comprises: an authentication module, configured to, when ordering the program that has not been subscribed, send an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; and a downloading module, configured to download and obtain the program with the decryption key. [0010]Preferably, the identification code of the mobile terminal is a model number of the mobile terminal. [0011]Preferably, the encryption module comprises: a video interference unit, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit, configured to perform audio mixing on a part of audio data of the program. [0012]The disclosure proposes an encryption method for a television service of a mobile terminal, comprising: when a mobile terminal orders a program that has not been subscribed, a server encrypting the program to shield a part of data of the program, and creating a new channel for the program that is encrypted; and the server sending information about the new channel and a decryption key to the mobile terminal. [0013]Preferably, the step of encrypting the program to shield a part of data of the program comprises: creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/or, performing audio mixing on a part of audio data of the program. [0014]The disclosure proposes a server, used for a television service of a mobile terminal, wherein the server comprises: an encryption module, configured to, when a mobile terminal orders a program that has not been subscribed, encrypt the program to shield a part of data of the program, and create a new channel for the program that is encrypted; and a sending module, configured to send information about the new channel and a decryption key to the mobile terminal. [0015]Preferably, the encryption module further comprises: a video interference unit, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit, configured to perform audio mixing on a part of audio data of the program. [0016]The encryption method for the television service of the mobile terminal, the mobile terminal and the server provided in the disclosure can encrypt the program, which is ordered but has not been subscribed by the user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program, thus certain experience can be enjoyed by the user, and the content of the program is protected, therefore the television service of the mobile terminal such as a mobile phone can be popularized greatly. BRIEF DESCRIPTION OF THE DRAWINGS [0017]FIG. 1 is a flow chart of an embodiment of an encryption method for a television service of a mobile terminal in the disclosure; [0018]FIG. 2 is a structure diagram of an embodiment of a mobile terminal in the disclosure; [0019]FIG. 3 is a structure diagram of an encryption module in an embodiment of the mobile terminal in the disclosure; [0020]FIG. 4 is a flow chart of an embodiment of another encryption method for a television service of a mobile terminal in the disclosure; [0021]FIG. 5 is a structure diagram of an embodiment of a server in the disclosure; and [0022]FIG. 6 is a structure diagram of an encryption module in an embodiment of the server in the disclosure. [0023]The implementation, functions, characteristics and advantages of the disclosure will be further described below with reference to drawings in combination with embodiments. DETAILED DESCRIPTION OF THE EMBODIMENTS [0024]An encryption method for a television service of a mobile terminal, a mobile terminal and a server provided in the embodiments of the disclosure can encrypt a program, which is ordered but has not been subscribed by a user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program. [0025]With reference to FIG. 1, a flow chart of an embodiment of an encryption method for a television service of a mobile terminal in the disclosure is shown, and the method comprises the steps as follows. [0026]Step 101: a mobile terminal orders and obtains a program that has not been subscribed. [0027]Preferably, if a program sending end encrypts the program, when ordering the program that has not been subscribed, the mobile terminal can send an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal to the program sending end to obtain a decryption key of the program; and then, the mobile terminal can download the program with the decryption key. [0028]Step 102: the mobile terminal encrypts the program to shield a part of data of the program. [0029]Step 103: the mobile terminal plays the program that is encrypted. [0030]Step 102 is specifically as follows: [0031]at least one color interference region is created, and the at least one color interference region is covered on a part of video data of the program; and/or, perform audio mixing on a part of audio data of the program. [0032]By taking a case that the mobile terminal sends the identification code of the mobile terminal and the card number of the user identification card to the program sending end as an example, the working principle of the encryption method for the television service of the mobile terminal in the preferable embodiment of the disclosure will be described in details below. [0033]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, and sends the identification code of the mobile terminal and the card number of the user identification card of the mobile terminal after establishing a data link with the server; the server locally inquires a user subscription list of the user according to the card number of the user identification card of the mobile terminal, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the server further checks the identification code of the mobile terminal, which is generally the model number of the mobile terminal, and the server will send a decryption key of the program that is ordered by the mobile terminal to the mobile terminal if only the mobile terminal has a specific model number, that is, the mobile terminal has a multimedia information encryption function. [0034]After obtaining the decryption key, the mobile terminal downloads the program that is ordered (program on demand) with the decryption key. [0035]It should be noted that, the mobile terminal may not send the identification code of the mobile terminal and the card number of the user identification card to the program sending end, instead, it directly obtains the program and then judges whether the program is a program that has not been subscribed, if so, the mobile terminal encrypts the program. [0036]After downloading the program that is ordered, the mobile terminal encrypts data of the program to shield a part of data of the program, so that the mobile terminal user can have experience on the program, but cannot watch the complete program. The encryption process is described as follows. [0037]The program downloaded by the mobile terminal comprises video data and audio data. The video data exist in a format of bitmap in the mobile terminal after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the mobile terminal can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0038]wherein ‘MEMSET’ is an encryption function for encrypting the program, and ‘pDATA’ is a temporary variable for indicating the location of the color interference region. [0039]The color interference region is covered at the very center of the video data of the downloaded program, so that, when playing the program, the mobile terminal can play the program normally, but the user can not watch the complete program. [0040]The mobile terminal also can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the audio data downloaded and decoded by the mobile terminal for purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)); }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0041]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0042]The encryption for the video data and the audio data of the download program can be performed alternatively or simultaneously. [0043]Attention should be paid that the encryption for contents of the program by the mobile terminal is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0044]In the method, the program is encrypted at the mobile terminal side, so that the mobile terminal can protect the contents of the television program that has not been subscribed while providing certain experience on the television program for the user, therefore, the television service of the mobile phone is popularized greatly. [0045]With reference to FIG. 2 and FIG. 3, a structure diagram of an embodiment of a mobile terminal in the disclosure is shown, and the mobile terminal comprises: [0046]an obtaining module 01, configured to order and obtain a program that has not been subscribed; [0047]an encryption module 30, configured to encrypt the program to shield a part of data of the program; and [0048]a playing module 40, configured to play the program that is encrypted. [0049]The obtaining module 01 comprises: [0050]an authentication module 10, configured to, when ordering the program that has not been subscribed, send an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; and [0051]a downloading module 20, configured to download and obtain the program with the decryption key. [0052]The encryption module 30 further comprises: [0053]a video interference unit 32, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit 33, configured to perform audio mixing on a part of audio data of the program. [0054]The working principle of the mobile terminal in the embodiment will be described in details below. [0055]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, after establishing a data link with the server, the authentication module 10 sends the identification code of the mobile terminal and the card number of the user identification card of the mobile terminal; the server locally inquires a user subscription list of the card number, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the server further checks the identification code of the mobile terminal, which is generally the model number of the mobile terminal, and the server will send a decryption key of the program that is ordered by the mobile terminal to the mobile terminal if only the mobile terminal has a specific model number, that is, the mobile terminal has a multimedia information encryption function. [0056]After the mobile terminal obtains the decryption key, the downloading module 20 downloads the program that is ordered with the decryption key. [0057]After the mobile terminal downloads the program that is ordered, the encryption module 30 encrypts the program to shield a part of data of the program, so that the mobile terminal user can have experience on the program, but cannot watch the complete program. The encryption process is described as follows. [0058]The program downloaded by the mobile terminal comprises video data and audio data. The video data exist in a format of bitmap in the mobile terminal after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the video interference unit 32 can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0059]The video interference unit 32 covers the color interference region at the very center of the video data of the downloaded program so as to complete the encryption. The playing module 40 can play the program, but can not play the complete program, what the user watch is only the program which is coated with the color region in the center. [0060]The audio interference unit 33 of the mobile terminal can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the audio data downloaded and decoded by the mobile terminal for purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0061]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0062]The video interference unit 32 and the audio interference unit 33 can exist separately or simultaneously. [0063]Attention should be paid that the encryption for contents of the program by the mobile terminal is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0064]The program is encrypted by the mobile terminal, so that the mobile terminal can protect the contents of the television program that has not been subscribed while providing certain experience on the television program for the user, therefore, the television service of the mobile phone is popularized greatly. [0065]With reference to FIG. 4, a flow chart of an embodiment of another encryption method for a television service of a mobile terminal in the disclosure is shown, and the method comprises: [0066]Step 201: when a mobile terminal orders a program that has not been subscribed, a server encrypts the program to shield a part of data of the program, and creates a new channel for the program that is encrypted; [0067]Step 202: the server sends information about the channel and a decryption key to the mobile terminal. [0068]Step 201 is specifically as follows: [0069]at least one color interference region is created, and the at least one color interference region is covered on a part of video data of the program; and/or, [0070]perform audio mixing on a part of audio data of the program. [0071]The working principle of the method in the embodiment will be described in details below. [0072]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, and sends a card number of a user identification card to the server after establishing a data link with the server; the server locally inquires a user subscription list of the user according to the card number of the user identification card of the mobile terminal, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the server encrypts the program to shield a part of data of the program, and creates a new channel for the program that is encrypted. The encryption process is described as follows. [0073]Video data of the program provided by the server exists in a format of bitmap after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the server can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0074]The color interference region is covered at the very center of the video data of the program, so as to complete the encryption for the video data of the program. [0075]The server also can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the original audio data for the purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0076]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0077]The encryption for the video data and the audio data can be performed alternatively or simultaneously. [0078]The server creates a new channel for the program that is encrypted and sends information about the new channel and the decryption key of the new channel to the mobile terminal. After receiving the information about the new channel, the mobile terminal automatically switches to the channel and plays the program with the decryption key, wherein the program played by the mobile terminal is a program, a part of data of which are shielded, not a complete program. [0079]Attention should be paid to that the encryption for contents of the program by the server is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0080]In the method, the program is encrypted at the server side serving as a data source, so that the mobile terminal users can have certain experience on a television program that has not been subscribed, and the content of the program is protected, therefore, the television service of the mobile phone is popularized greatly. [0081]With reference to FIG. 5 and FIG. 6, a structure diagram of an embodiment of a server in the disclosure is shown, the server is used for a television service of a mobile terminal, and the server comprises: [0082]an encryption module 50, configured to, when a mobile terminal orders a program that has not been subscribed, encrypt the program to shield a part of data of the program, and create a new channel for the program that is encrypted; and [0083]a sending module 60, configured to send information about the new channel and a decryption key to the mobile terminal. [0084]The encryption module 50 comprises: [0085]a video interference unit 52, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit 53, configured to perform audio mixing on a part of audio data of the program. [0086]The working principle of the server in the embodiment will be described in details below. [0087]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, and sends a card number of a user identification card to the server after establishing a data link with the server; the server locally inquires a user subscription list of the user according to the card number of the user identification card of the mobile terminal, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the encryption module 50 encrypts the program to shield a part of data of the program, and creates a new channel for the program that is encrypted. The encryption process is described as follows. [0088]Video data of the program provided by the server exists in a format of bitmap after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the video interference unit 52 can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0089]The video interference unit 52 covers the color interference region at the very center of the video data of the program so as to complete the partial encryption for the data of the program. [0090]The audio interference unit 53 of the server can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the original audio data for the purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0091]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0092]The video interference unit 52 and the audio interference unit 53 can exist separately or simultaneously. [0093]The encryption module 50 creates a new channel for the program that is encrypted, the sending module 60 sends information about the new channel and the decryption key of the new channel to the mobile terminal. After receiving the information about the new channel, the mobile terminal automatically switches to the channel and plays the program with the decryption key, wherein the program played by the mobile terminal is a program, a part of data of which are shielded, not a complete program. [0094]Attention should be paid to that the encryption for contents of the program by the server is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0095]In the embodiment, the server encrypts the program, so that the mobile terminal can have certain experience on a television program that has not been subscribed, and the content of the program is protected, therefore, the television service of the mobile phone is popularized greatly. [0096]The above contents just describe preferable embodiments of the disclosure and are not intended to limit the patent scope of the disclosure. Any equivalent structure or equivalent flow transform made by utilizing contents of the specification and drawings in the disclosure, or any direct or indirect application in other relevant technical fields, should be comprised within the patent protection scope of the disclosure.(String), 发明领域 [0001] 本发明涉及通信技术领域,尤其涉及一种移动终端电视业务的加密方法、移动终端及服务器。 发明背景 [0002] 手机等移动终端的电视业务实际上是这样实现的:利用流媒体技术推出移动终端电视作为数据业务,用户看到的是下载的视频数据。 现有的移动终端电视业务加密方法中,服务提供商提供的所有电视节目都是加密的,用户只有在订阅了移动终端电视节目后,才能得到服务提供商的授权,用户才能点播。 订阅的节目。 这种移动终端电视服务的加密方式有一个缺陷:用户通常希望在订阅节目之前先观看节目的一部分数据,以根据体验决定是否订阅该节目,但根据目前的 手机电视服务的加密方法,对于没有订阅节目的用户,数据完全屏蔽,无法收看,用户无法体验节目,因此,手机电视服务的普及 是有限的。 发明内容 [0003] 本发明提供了一种移动终端电视业务的加密方法、移动终端及服务器,以便于服务提供商更好地推广手机等移动终端电视业务。 [0004] 本发明提出了一种移动终端电视业务的加密方法,包括:移动终端订购并获取未订阅的节目; 移动终端对节目进行加密,屏蔽节目的部分数据; 移动终端播放加密后的节目。 [0005] 优选地,移动终端点播并获取未订阅节目的步骤包括:移动终端在点播未订阅节目时,发送移动终端的识别码和用户识别卡的卡号。 移动终端,获取程序的解密密钥; 下载并获取带有解密密钥的程序。 [0006] 优选地,移动终端的识别码为移动终端的型号。 [0007] 优选地,对节目进行加密以屏蔽节目的部分数据的步骤包括:创建至少一个颜色干扰区域,并将至少一个颜色干扰区域覆盖在节目的部分视频数据上。 和/或,对节目的部分音频数据进行混音。 [0008] 本发明提出了一种移动终端,包括: 获取模块,用于点播并获取未订阅的节目; 加密模块,用于对程序进行加密,屏蔽程序的部分数据; 播放模块,用于播放加密后的节目。 [0009] 优选地,所述获取模块包括: 鉴权模块,用于在点播未订阅的节目时,发送移动终端的识别码和移动终端用户识别卡的卡号,以获取解密码 程序的关键; 下载模块,用于下载并获取带有解密密钥的程序。 [0010] 优选地,移动终端的识别码为移动终端的型号。 [0011] 优选地,所述加密模块包括: 视频干扰单元,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上。 和/或,音频干扰单元,用于对节目的部分音频数据进行混音。 [0012]本发明提出了一种移动终端电视业务的加密方法,包括:当移动终端点播未订阅的节目时,服务器对该节目进行加密,屏蔽该节目的部分数据,并创建新的频道。 对于加密的程序; 服务器向移动终端发送新频道信息和解密密钥。 [0013] 优选地,对节目进行加密以屏蔽节目的部分数据的步骤包括:创建至少一个颜色干扰区域,并将至少一个颜色干扰区域覆盖在节目的部分视频数据上。 和/或,对节目的部分音频数据进行混音。 [0014] 本发明提出了一种服务器,用于移动终端的电视业务,该服务器包括: 加密模块,用于当移动终端点播未订阅的节目时,对该节目进行加密,以屏蔽部分数据。 程序,并为加密的程序创建一个新的频道; 发送模块,用于向移动终端发送新频道信息和解密密钥。 [0015] 优选地,所述加密模块还包括: 视频干扰单元,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上。 和/或,音频干扰单元,用于对节目的部分音频数据进行混音。 [0016] 本发明提供的移动终端电视业务的加密方法、移动终端及服务器,可以在移动终端侧或服务器侧对用户点播但未订阅的节目进行加密,以便 将节目的部分数据屏蔽后再播放,可以给用户带来一定的体验,节目的内容也得到了保护,可以极大地普及手机等移动终端的电视业务。 . 附图的简要说明 [0017] 图1为本发明移动终端电视业务加密方法的一个实施例的流程图; [0018] 图2为本发明移动终端一个实施例的结构图; [0019] 图3为本发明移动终端实施例中加密模块的结构图; [0020] 图4为本发明另一种移动终端电视业务加密方法的实施例流程图。 [0021] 图5为本发明服务器一个实施例的结构图; 和 [0022] 图6为本发明服务器实施例中加密模块的结构图。 [0023] 下面参照附图并结合实施例对本发明的实施方式、功能、特点和优点作进一步说明。 具体实施方式 [0024] 本发明实施例提供的一种移动终端电视业务的加密方法、移动终端及服务器,能够在移动终端侧或服务器对用户点播未订阅的节目进行加密。 屏蔽部分节目数据后播放节目。 [0025] 参见图1,示出了本发明移动终端电视业务加密方法的一个实施例的流程图,该方法包括以下步骤。 [0026] 步 101 :移动终端点播并获取未订阅的节目。 [0027] 优选地,如果节目发送端对节目进行加密,则移动终端在点播未订阅的节目时,可以向节目发送端发送移动终端的识别码和移动终端用户识别卡的卡号。 结束获取程序的解密密钥; 然后,移动终端可以使用解密密钥下载程序。 [0028] 步 102:移动端对节目进行加密,屏蔽节目的部分数据。 [0029] 步 103 :移动终端播放加密后的节目。 [0030] 步 102 具体如下: [0031] 产生至少一色彩干扰区,且至少一色彩干扰区覆盖于节目的部分视频数据上。 和/或,对节目的部分音频数据进行混音。 [0032] 以移动终端向节目发送端发送移动终端识别码和用户识别卡卡号为例,说明移动终端电视业务加密方法的工作原理。 下面对本发明的优选实施例进行详细说明。 [0033] 手机等移动终端向提供移动终端电视服务的服务器发起某个节目的点播请求,发送移动终端的识别码和移动终端用户识别卡的卡号 与服务器建立数据链接后; 服务器根据移动终端用户识别卡的卡号在本地查询用户的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息, 如果发现该卡号没有订阅节目且该节目不是免费节目,则服务器进一步核对移动终端的识别码,一般为移动终端的型号,服务器会发送解密 如果移动终端具有特定型号,即移动终端具有多媒体信息加密功能,则移动终端向移动终端订购的节目的密钥。 [0034] 移动终端获得解密密钥后,下载使用解密密钥点播的节目(节目点播)。 [0035] 需要说明的是,移动终端可以不向节目发送端发送移动终端的识别码和用户识别卡的卡号,而是直接获取节目,再判断节目是否为节目。 如果没有订阅,则移动终端对节目进行加密。 [0036] 移动终端下载订购的节目后,对节目数据进行加密,屏蔽部分节目数据,使移动终端用户可以体验节目,但不能观看完整的节目。 加密过程描述如下。 [0037] 移动终端下载的节目包括视频数据和音频数据。 视频数据解码后以位图的形式存在于移动终端中,位图的数据数组为线性数组。 例如,视频数据的大小为320*240,则移动终端可以创建一个彩色干扰区域,例如一个黑色矩形干扰区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0038] 其中‘MEMSET’是一个加密函数,用于对程序进行加密,‘pDATA’是一个临时变量,用于指示颜色干扰区域的位置。 [0039] 颜色干扰区域覆盖在下载节目的视频数据的最中心,使得在播放节目时,移动终端可以正常播放节目,但用户无法观看到完整的节目。 [0040] 移动终端还可以对音频数据进行加密,屏蔽节目的部分音频数据。 在移动终端下载解码的音频数据中选择性地加入其他音频数据进行混音,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)); }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0041] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0042]下载程序的视频数据和音频数据的加密可以交替进行,也可以同时进行。 [0043] 需要注意的是,移动终端对节目内容的加密并不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0044] 该方法在移动终端侧对节目进行加密,使得移动终端在为用户提供一定的电视节目体验的同时,可以保护未订阅的电视节目的内容,从而实现电视服务。 手机大为普及。 [0045] 参考图2和图3,示出了本发明移动终端一个实施例的结构图,该移动终端包括: [0046] 获取模块 01 , 用于订购并获取未订购的节目; [0047] 加密模块 30 ,用于对程序进行加密,屏蔽程序的部分数据; 和 [0048] 播放模块 40 ,配置为播放加密的节目。 [0049] 获取模块 01 包含: [0050] 认证模块 10 ,用于在点播未订阅的节目时,发送移动终端的识别码和移动终端用户识别卡的卡号,获取节目的解密密钥; 和 [0051] 一个下载模块 20 ,配置为下载并获取带有解密密钥的程序。 [0052] 加密模块 30 还包括: [0053] 视频干扰单元 32 ,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上; 和/或,音频干扰单元 33 ,用于对节目的部分音频数据进行混音。 [0054] 下面对本实施例的移动终端的工作原理进行详细说明。 [0055] 手机等移动终端向提供该移动终端电视服务的服务器发起某个节目的点播请求,与该服务器建立数据链路后,鉴权模块 10 发送移动终端识别码和移动终端用户识别卡卡号; 服务器在本地查询该卡号的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息,若发现该卡号未订阅该节目,则 程序不是免费程序,服务器进一步核对移动终端的识别码,一般为移动终端的型号,服务器将移动终端订购的程序的解密密钥发送给 移动终端如果只有移动终端具有特定型号,即移动终端具有多媒体信息加密功能。 [0056] 移动终端获得解密密钥后,下载模块 20 下载使用解密密钥订购的程序。 [0057] 移动端下载订购的程序后,加密模块 30 对节目进行加密,屏蔽节目的部分数据,使移动端用户可以体验节目,但不能观看完整的节目。 加密过程描述如下。 [0058] 移动终端下载的节目包括视频数据和音频数据。 视频数据解码后以位图的形式存在于移动终端中,位图的数据数组为线性数组。 比如视频数据的大小是320*240,那么视频干扰单元 32 可以创建一个颜色的干涉区域,例如一个黑色的矩形干涉区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0059] 视频干扰单元 32 覆盖下载节目视频数据最中心的颜色干扰区域,完成加密。 播放模块 40 可以播放节目,但不能播放完整的节目,用户看到的只是中间涂有彩色区域的节目。 [0060] 音频干扰单元 33 移动端可以对音频数据进行加密,屏蔽节目的部分音频数据。 在移动终端下载解码的音频数据中选择性地加入其他音频数据进行混音,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0061] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0062] 视频干扰单元 32 和音频干扰单元 33 可以单独存在,也可以同时存在。 [0063] 需要注意的是,移动终端对节目内容的加密并不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0064] 节目通过移动终端加密,使得移动终端在为用户提供一定的电视节目体验的同时,可以保护未订阅的电视节目内容,从而普及手机电视业务 大大。 [0065] 参见图4,示出了本发明另一种移动终端电视业务加密方法的实施例流程图,该方法包括: [0066] 步 201 :当移动终端点播未订阅的节目时,服务器对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道; [0067] 步 202 :服务器向移动终端发送信道信息和解密密钥。 [0068] 步 201 具体如下: [0069] 产生至少一色彩干扰区,且至少一色彩干扰区覆盖于节目的部分视频数据上。 和/或, [0070] 对节目的部分音频数据进行混音。 [0071] 下面对本实施例方法的工作原理进行详细说明。 [0072] 手机等移动终端向提供该移动终端电视服务的服务器发起某个节目的点播请求,与该服务器建立数据链路后,向该服务器发送用户识别卡的卡号; 服务器根据移动终端用户识别卡的卡号在本地查询用户的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息, 如果发现该卡号未订阅该节目且该节目不是免费节目,则服务器对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道。 加密过程描述如下。 [0073] 服务器提供的节目的视频数据解码后以位图的形式存在,位图的数据数组为线性数组。 例如视频数据的大小为320*240,则服务器可以创建一个颜色的干扰区域,例如一个黑色的矩形干扰区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0074] 颜色干扰区域覆盖在节目视频数据的最中心,从而完成对节目视频数据的加密。 [0075] 服务器还可以对音频数据进行加密,屏蔽节目的部分音频数据。 在原始音频数据中有选择地加入其他音频数据,以达到混音的目的,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0076] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0077] 视频数据和音频数据的加密可以交替进行,也可以同时进行。 [0078] 服务器为加密后的节目创建新的频道,并将新频道的信息和新频道的解密密钥发送给移动终端。 移动终端接收到新频道信息后,自动切换到该频道并播放带有解密密钥的节目,其中移动终端播放的节目为部分数据被屏蔽的节目,并非完整节目 程序。 [0079] 需要注意的是,服务器对节目内容的加密不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0080] 该方法在作为数据源的服务器端对节目进行加密,使移动终端用户对未订阅的电视节目有一定的体验,节目内容受到保护,因此, 手机电视业务大为普及。 [0081] 参考图5和图6,示出了本发明服务器一个实施例的结构图,该服务器用于移动终端的电视业务,该服务器包括: [0082] 加密模块 50 ,用于当移动终端点播未订阅的节目时,对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道; 和 [0083] 发送模块 60 ,用于向移动终端发送新频道信息和解密密钥。 [0084] 加密模块 50 包含: [0085] 视频干扰单元 52 ,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上; 和/或,音频干扰单元 53 ,用于对节目的部分音频数据进行混音。 [0086] 下面详细说明本实施例中服务器的工作原理。 [0087] 手机等移动终端向提供该移动终端电视服务的服务器发起某个节目的点播请求,与该服务器建立数据链路后,向该服务器发送用户识别卡的卡号; 服务器根据移动终端用户识别卡的卡号在本地查询用户的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息, 如果发现卡号没有订阅节目且节目不是免费节目,则加密模块 50 对节目进行加密,屏蔽节目的部分数据,为加密后的节目创建新的频道。 加密过程描述如下。 [0088] 服务器提供的节目的视频数据解码后以位图的形式存在,位图的数据数组为线性数组。 比如视频数据的大小是320*240,那么视频干扰单元 52 可以创建一个颜色的干涉区域,例如一个黑色的矩形干涉区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0089] 视频干扰单元 52 覆盖节目视频数据最中心的颜色干扰区域,完成对节目数据的部分加密。 [0090] 音频干扰单元 53 服务器端可以对音频数据进行加密,屏蔽节目的部分音频数据。 在原始音频数据中有选择地加入其他音频数据,以达到混音的目的,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0091] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0092] 视频干扰单元 52 和音频干扰单元 53 可以单独存在,也可以同时存在。 [0093] 加密模块 50 为加密的程序创建一个新的通道,发送模块 60 向移动终端发送新频道信息和新频道的解密密钥。 移动终端接收到新频道信息后,自动切换到该频道并播放带有解密密钥的节目,其中移动终端播放的节目为部分数据被屏蔽的节目,并非完整节目 程序。 [0094] 需要注意的是,服务器对节目内容的加密不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0095] 本实施例通过服务器对节目进行加密,使得移动终端对未订阅的电视节目有一定的体验,节目内容受到保护,极大地普及了手机电视业务。 . [0096] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的专利范围。 凡利用本发明说明书和附图的内容所作出的等效结构或等效流程变换,或者在其他相关技术领域的直接或间接应用,均应包含在本发明的专利保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101883241A(String), EP2579589A1(String), EP2579589A4(String), US20130104163A1(String), WO2011150627A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101883241A(String), EP2579589A1(String), EP2579589A4(String), US20130104163A1(String), WO2011150627A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20130104163A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101883241A(String), EP2579589A1(String), EP2579589A4(String), US20130104163A1(String), WO2011150627A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270654(Integer), CN101883241A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270654(Integer), EP2579589A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270654(Integer), EP2579589A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:41.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270654(Integer), US20130104163A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270654(Integer), WO2011150627A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20130104163A1(String), US20130104163A1(String), 1366819200(Integer), 270654(Integer), 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), HE, LIPENG(String), ZHANG, SHUYAN(String), 中兴通讯股份有限公司(String), HE LIPENG(String), ZHANG SHUYAN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184971(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184971(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HE, LIPENG(String), HE LIPENG(String), 0(Integer), 1681975542(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHANG, SHUYAN(String), ZHANG SHUYAN(String), 0(Integer), 1681975542(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184971(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75920(Integer), 2(Integer), 184971(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75921(Integer), 2(Integer), 184971(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.085 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75920(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.113 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20220353819A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Reducing Power Consumption of Mobile Terminal and Mobile Terminal(String), 降低移动终端功耗的方法及移动终端(String), US20220353819A1(String), A method for reducing power consumption of a mobile terminal and a mobile terminal are provided. The method includes: A mobile terminal establishes a Wi-Fi connection to an electronic device by using a Wi-Fi module; the mobile terminal interacts with a server by using the Wi-Fi connection; if the mobile terminal doesn't send or receive a packet within a first time period, the mobile terminal controls the Wi-Fi module to enter a sleep state; and after the Wi-Fi module enters the sleep state, if the mobile terminal needs to send a heartbeat packet, the mobile terminal may establish a Bluetooth connection to the electronic device by using a Bluetooth module, and send the heartbeat packet by using the Bluetooth connection.(String), 提供了一种降低移动终端功耗的方法和移动终端。 该方法包括:移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接; 移动终端通过Wi-Fi连接与服务器交互; 如果移动终端在第一时间段内没有发送或接收数据包,则移动终端控制Wi-Fi模块进入休眠状态。 Wi-Fi模块进入休眠状态后,如果移动终端需要发送心跳包,移动终端可以通过蓝牙模块与电子设备建立蓝牙连接,通过蓝牙发送心跳包 联系。(String), US17/812755(String), 1657814400(Integer), US20220353819A1(String), 1667404800(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 0(Integer), 18(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184972(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\50119a36dc4c4c428c3cac792ec9a881.png(String), 184972(Integer), 50119a36dc4c4c428c3cac792ec9a881.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Reducing Power Consumption of Mobile Terminal and Mobile Terminal(String), 降低移动终端功耗的方法及移动终端(String), US20220353819A1(String), A method for reducing power consumption of a mobile terminal and a mobile terminal are provided. The method includes: A mobile terminal establishes a Wi-Fi connection to an electronic device by using a Wi-Fi module; the mobile terminal interacts with a server by using the Wi-Fi connection; if the mobile terminal doesn't send or receive a packet within a first time period, the mobile terminal controls the Wi-Fi module to enter a sleep state; and after the Wi-Fi module enters the sleep state, if the mobile terminal needs to send a heartbeat packet, the mobile terminal may establish a Bluetooth connection to the electronic device by using a Bluetooth module, and send the heartbeat packet by using the Bluetooth connection.(String), 提供了一种降低移动终端功耗的方法和移动终端。 该方法包括:移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接; 移动终端通过Wi-Fi连接与服务器交互; 如果移动终端在第一时间段内没有发送或接收数据包,则移动终端控制Wi-Fi模块进入休眠状态。 Wi-Fi模块进入休眠状态后,如果移动终端需要发送心跳包,移动终端可以通过蓝牙模块与电子设备建立蓝牙连接,通过蓝牙发送心跳包 联系。(String), US17/812755(String), 1657814400(Integer), US20220353819A1(String), 1667404800(Integer), 美国(String), 1(Integer), 2(Integer), CN(String), 5(Integer), 0(Integer), \20230420\50119a36dc4c4c428c3cac792ec9a881.png(String), 18(Integer), 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 1. A method, comprising:establishing, by a mobile terminal, a Wi-Fi connection to an electronic device by using a Wi-Fi module of the mobile terminal, and interacting, by the mobile terminal, with a server by using the Wi-Fi connection;controlling, by the mobile terminal, the Wi-Fi module to enter a sleep state; andwhile the Wi-Fi module is in the sleep state, when the mobile terminal has a to-be-sent first packet, sending, by the mobile terminal, the to-be-sent first packet to the electronic device using a Bluetooth connection established by a Bluetooth module of the mobile terminal, wherein the first packet is a heartbeat packet or a packet used to establish a transport layer link.(String), 1.一种方法,包括:移动终端通过移动终端的Wi-Fi模块与电子设备建立Wi-Fi连接,并通过该Wi-Fi连接与服务器交互;移动终端控制Wi-Fi模块进入休眠状态;和在Wi-Fi模块处于休眠状态时,当移动终端有待发送的第一包时,移动终端通过已建立的蓝牙连接向电子设备发送待发送的第一包通过移动终端的蓝牙模块,其中,第一报文为心跳报文或用于建立传输层链路的报文。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 2. The method according to claim 1, further comprising:while the Wi-Fi module is in the sleep state, when the mobile terminal has the to-be-sent first packet, waking up, by the mobile terminal, the Bluetooth module, and establishing the Bluetooth connection to the electronic device using the Bluetooth module.(String), 2.根据权利要求1所述的方法,还包括:在Wi-Fi模块处于休眠状态时,当移动终端有待发送的第一个数据包时,移动终端唤醒蓝牙模块,并通过蓝牙与电子设备建立蓝牙连接模块。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 3. The method according to claim 1, further comprising:after the mobile terminal sends the to-be-sent first packet, when the mobile terminal does not send or receive another packet within a second time period after sending the to-be-sent first packet, controlling the Bluetooth module to enter a sleep state.(String), 3.根据权利要求1所述的方法,还包括:移动终端发送待发送的第一个数据包后,当移动终端在发送该待发送的第一个数据包后的第二时间段内没有发送或接收到另一个数据包时,控制蓝牙模块进入休眠状态.4.根据权利要求1所述的方法,其特征在于,所述蓝牙连接为标准蓝牙连接或蓝牙低功耗连接。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 4. The method according to claim 1, wherein the Bluetooth connection is a standard Bluetooth connection or a Bluetooth low energy connection.(String), 5.根据权利要求1所述的方法,其特征在于,所述电子设备为无线路由器、Wi-Fi设备或具有热点能力的移动终端中的任一种。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 5. The method according to claim 1, wherein the electronic device is any one of a wireless router, a Wi-Fi device, or a mobile terminal with a hotspot capability.(String), 6.根据权利要求1所述的方法,还包括:Wi-Fi模块进入休眠状态后,当移动终端有待发送的第二包或待接收的第二包时,移动终端唤醒Wi-Fi模块,重新建立移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接,并通过Wi-Fi连接传输第二封包,其中移动终端保持或断开移动终端与电子设备之间的蓝牙连接移动终端唤醒后。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 6. The method according to claim 1, further comprising:after the Wi-Fi module enters the sleep state, when the mobile terminal has a to-be-sent second packet or a to-be-received second packet, waking up, by the mobile terminal, the Wi-Fi module, reestablishing a Wi-Fi connection between the mobile terminal and the electronic device by using the Wi-Fi module, and transmitting the second packet using the Wi-Fi connection, wherein the mobile terminal retains or disconnects the Bluetooth connection between the mobile terminal and the electronic device after the mobile terminal wakes up.(String), 7.根据权利要求1所述的方法,还包括:Wi-Fi模块进入休眠状态后,当移动终端有待发送首包时,在移动终端通过自身建立的蓝牙连接发送待发送首包之前蓝牙模块发送至电子设备,移动终端接收用户开启第一功能的指示,或者移动终端在判断满足第一条件时开启第一功能,其中第一功能是移动终端降低功耗的功能,第一条件包括:移动终端的电池电量小于预设值,移动终端启用的应用数量大于预设数量,移动终端终端启用任何一个或多个预设应用程序。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 7. The method according to claim 1, further comprising:after the Wi-Fi module enters the sleep state, when the mobile terminal has the to-be-sent first packet, and before sending, by the mobile terminal, the to-be-sent first packet by using the Bluetooth connection established by the Bluetooth module to the electronic device, receiving, by the mobile terminal, an indication for enabling a first function from a user, or enabling, by the mobile terminal, the first function when determining that a first condition is met, wherein the first function is a function of reducing power consumption of the mobile terminal, and the first condition comprises: a battery level of the mobile terminal is less than a preset value, a quantity of applications enabled by the mobile terminal is greater than a preset quantity, and the mobile terminal enables any one or more of preset applications.(String), 8.根据权利要求1所述的方法,其特征在于,所述心跳包在所述移动终端与所述服务器之间进行交换。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 8. The method according to claim 1, wherein the heartbeat packet is exchanged between the mobile terminal and the server.(String), 9.一种计算机可读存储介质,包括计算机指令,其中当所述计算机指令在移动终端上运行时,所述移动终端执行根据权利要求1所述的方法。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 9. A computer readable storage medium, comprising computer instructions, wherein when the computer instructions are run on a mobile terminal, the mobile terminal performs the method according to claim 1.(String), 10.一种方法,包括:电子设备通过电子设备的Wi-Fi模块分别与N个移动终端建立Wi-Fi连接,N个移动终端通过Wi-Fi连接与服务器交互,电子设备建立一个与服务器的通信连接;和当N个移动终端的所有Wi-Fi模块进入休眠状态时,电子设备控制电子设备的Wi-Fi模块进入休眠状态;和当N个移动终端中的M个移动终端的Wi-Fi模块进入休眠状态时,电子设备分别通过电子设备的蓝牙模块与M个移动终端建立蓝牙连接,发送待发送或M个移动终端的待接收的第一包,其中每个第一包为心跳包或用于建立传输层链路的包,M和N为正整数,M小于或等于N。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 10. A method, comprising:respectively establishing, by an electronic device, Wi-Fi connections to N mobile terminals using a Wi-Fi module of the electronic device, wherein the N mobile terminals interact with a server by using the Wi-Fi connections, and the electronic device establishes a communication connection to the server; andwhen all Wi-Fi modules of the N mobile terminals enter a sleep state, controlling, by the electronic device, a Wi-Fi module of the electronic device to enter the sleep state; andwhen Wi-Fi modules of M mobile terminals in the N mobile terminals enter a sleep state, respectively establishing, by the electronic device, Bluetooth connections to the M mobile terminals using a Bluetooth module of the electronic device, to transmit to-be-sent or to-be-received first packets of the M mobile terminals, wherein each first packet is a heartbeat packet or a packet used to establish a transport layer link, M and N are positive integers, and M is less than or equal to N.(String), 11.根据权利要求10所述的方法,其中,所述蓝牙连接是标准蓝牙连接或蓝牙低功耗连接。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 11. The method according to claim 10, wherein the Bluetooth connection is a standard Bluetooth connection or a Bluetooth low energy connection.(String), 12.根据权利要求10所述的方法,其特征在于,所述电子设备为无线路由器、随行的Wi-Fi设备或具有热点能力的移动终端中的任一种。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 12. The method according to claim 10, wherein the electronic device is any one of a wireless router, an accompanying Wi-Fi device, or a mobile terminal with a hotspot capability.(String), 13.一种电子设备,包括处理器、存储器、Wi-Fi模块和蓝牙模块,其中存储器、Wi-Fi模块和蓝牙模块耦合到处理器;存储器被配置为存储计算机程序代码;计算机程序代码包括计算机指令;当处理器从存储器读取计算机指令时,电子设备执行根据权利要求10所述的方法。(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 13. An electronic device, comprising a processor, a memory, a Wi-Fi module, and a Bluetooth module, wherein the memory, the Wi-Fi module, and the Bluetooth module are coupled to the processor; the memory is configured to store computer program code; the computer program code comprises computer instructions; and when the processor reads the computer instructions from the memory, the electronic device performs the method according to claim 10.(String), 14.根据权利要求10所述的方法,其特征在于,所述心跳包在所述移动终端与所述服务器之间进行交换。(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 14. The method according to claim 10, wherein the heartbeat packet is exchanged between the mobile terminal and the server.(String), 15.一种计算机可读存储介质,包括计算机指令,其中当所述计算机指令在电子设备上运行时,所述电子设备执行根据权利要求10所述的方法。(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 15. A computer readable storage medium, comprising computer instructions, wherein when the computer instructions are run on an electronic device, the electronic device performs the method according to claim 10.(String), 16.一种芯片系统,包括一个或多个处理器,其中当所述一个或多个处理器执行指令时,使所述电子设备执行根据权利要求10所述的方法。(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 16. A chip system, comprising one or more processors, wherein when the one or more processors execute instructions, the electronic device is caused to perform the method according to claim 10.(String), 17.一种电子设备系统,包括一个或多个移动终端和根据权利要求10所述的电子设备。(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 17. An electronic device system, comprising one or more mobile terminals and the electronic device according to claim 10.(String), 18.一种移动终端,包括:处理器;一段记忆;触摸屏;一个Wi-Fi模块;和蓝牙模块,其中存储器、触摸屏、Wi-Fi模块和蓝牙模块耦合到处理器;其中,所述存储器用于存储计算机程序代码,所述计算机程序代码包括可由所述处理器执行的计算机指令,当所述计算机指令被执行时,使所述移动终端:通过Wi-Fi模块与电子设备建立Wi-Fi连接,移动终端通过Wi-Fi连接与服务器交互;控制Wi-Fi模块进入休眠状态;和在Wi-Fi模块处于休眠状态时,当移动终端有待发送的第一包时,通过蓝牙模块建立的蓝牙连接将待发送的第一包发送给电子设备,其中第一个数据包是心跳数据包或用于建立传输层链路的数据包。(String), 1(Integer), 16(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184972(Integer), 18. A mobile terminal, comprising:a processor;a memory;a touchscreen;a Wi-Fi module; anda Bluetooth module, wherein the memory, the touchscreen, the Wi-Fi module, and the Bluetooth module are coupled to the processor;wherein the memory is configured to store computer program code, the computer program code comprises computer instructions executable by the processor, and when the computer instructions are executed, the mobile terminal is caused to:establish a Wi-Fi connection to an electronic device by using the Wi-Fi module, and interacting, by the mobile terminal, with a server by using the Wi-Fi connection;control the Wi-Fi module to enter a sleep state; andwhile the Wi-Fi module is in the sleep state, when the mobile terminal has a to-be-sent first packet, send the to-be-sent first packet to the electronic device using a Bluetooth connection established by the Bluetooth module, wherein the first packet is a heartbeat packet or a packet used to establish a transport layer link.(String), 0(Integer), 17(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184972(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2020/127544, filed on Nov. 9, 2020, which claims priority to Chinese Patent Application No. 202010043528.2, filed on Jan. 15, 2020. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]This application relates to the field of mobile terminal technologies, and in particular, to a method for reducing power consumption of a mobile terminal and a mobile terminal. BACKGROUND [0003]With the development of electronic technologies, mobile terminals provide increasingly more functions, enriching people's lives. When using an application on a mobile terminal, a user usually needs to access a network, to be specific, establish, by using one or more networks, a communication connection to a server corresponding to the application. [0004]Wi-Fi has a lower tariff and a higher network speed. Therefore, Wi-Fi is preferred for users to access the network. The mobile terminal may establish, by using a configured Wi-Fi module, a communication connection to the server in a connection manner of a wireless local area network (for example, a Wi-Fi network) by using the internet or a mobile communications network. Alternatively, the mobile terminal establishes, by using a Wi-Fi module, a communication connection to an accompanying Wi-Fi device (or referred to as a mobile Wi-Fi device) in a connection manner of a wireless local area network (for example, a Wi-Fi network), and accesses a mobile communications network by using the accompanying Wi-Fi device, to interact with the server. [0005]As a network access time of the user increases, a working time of the Wi-Fi module also extends, and power consumption of the Wi-Fi module is very high. It can be learned that power consumption of the Wi-Fi module is one of important indicators that affect a battery life of the mobile terminal. Therefore, how to reduce the power consumption of the Wi-Fi module in the mobile terminal is always a hot topic researched by manufacturers. SUMMARY [0006]This application provides a method for reducing power consumption of a mobile terminal and a mobile terminal, to reduce power consumption of a Wi-Fi module in the mobile terminal, thereby helping prolong a standby time of the mobile terminal. [0007]To achieve the foregoing objective, embodiments of this application provide the following technical solutions. [0008]According to a first aspect, a method for reducing power consumption of a mobile terminal is provided. The mobile terminal has a Wi-Fi module and a Bluetooth module. The method includes: The mobile terminal establishes a Wi-Fi connection to an electronic device by using the Wi-Fi module, and the mobile terminal interacts with a server by using the Wi-Fi connection. If the mobile terminal does not send or receive a packet within a first time period, the mobile terminal controls the Wi-Fi module to enter a sleep state, where the packet includes a first packet and a second packet, or the packet includes a second packet. The first packet is a heartbeat packet or a packet used to establish a transport layer link, and the second packet is a packet other than the first packet. After the Wi-Fi module enters the sleep state, if the mobile terminal has a to-be-sent first packet, the mobile terminal sends the to-be-sent first packet by using a Bluetooth connection established by the Bluetooth module to the electronic device. [0009]It can be learned that, when the Wi-Fi module of the mobile terminal is in the sleep state, if the mobile terminal only needs to send the first packet, the mobile terminal does not wake up the Wi-Fi module, but wakes up the Bluetooth module having lower power consumption than the Wi-Fi module, and sends the first packet in a Bluetooth mode, to reduce power consumption of the Wi-Fi module. In this way, overall power consumption of the mobile terminal is reduced, and a battery life of the mobile terminal is prolonged. [0010]In a possible implementation, the method further includes: After the Wi-Fi module enters the sleep state, if the mobile terminal has the to-be-sent first packet, the mobile terminal wakes up the Bluetooth module, and establishes the Bluetooth connection to the electronic device by using the Bluetooth module. [0011]In some examples, after the Wi-Fi module enters the sleep state, the mobile terminal starts to establish the Bluetooth connection to the electronic device. Alternatively, after the Wi-Fi module enters the sleep state, the mobile terminal establishes the Bluetooth connection to the electronic device only when determining that a first packet needs to be sent. In some other examples, the mobile terminal may alternatively establish the Bluetooth connection to the electronic device before the Wi-Fi module enters the sleep state. Therefore, a plurality of occasions for establishing the Bluetooth connection between the mobile terminal and the electronic device are provided. [0012]In a possible implementation, the method further includes: After the mobile terminal sends the to-be-sent first packet, if the mobile terminal does not send or receive another packet within a second time period, the mobile terminal controls the Bluetooth module to enter a sleep state. This helps further reduce power consumption of the Bluetooth module. [0013]In a possible implementation, the Bluetooth connection is a classic Bluetooth connection or a Bluetooth low energy connection. [0014]In a possible implementation, the electronic device is any one of a wireless router, an accompanying Wi-Fi device, or a mobile terminal with a hotspot capability. [0015]In a possible implementation, after the Wi-Fi module enters the sleep state, the method further includes: If the mobile terminal has a to-be-sent second packet or a to-be-received second packet, the mobile terminal wakes up the Wi-Fi module, reestablishes a Wi-Fi connection between the mobile terminal and the electronic device by using the Wi-Fi module, and transmits the second packet by using the Wi-Fi connection, and the mobile terminal retains or disconnects the Bluetooth connection between the mobile terminal and the electronic device. [0016]In a possible implementation, after the Wi-Fi module enters the sleep state, if the mobile terminal has a to-be-sent first packet, before the mobile terminal sends the to-be-sent first packet by using the Bluetooth connection established by the Bluetooth module to the electronic device, the method further includes: The mobile terminal receives an indication for enabling a first function from a user, or the mobile terminal enables the first function when determining that a first condition is met, where the first function is a function of reducing power consumption of the mobile terminal, and the first condition includes: a battery level of the mobile terminal is less than a preset value, a quantity of applications enabled by the mobile terminal is greater than a preset quantity, and the mobile terminal enables any one or more of preset applications. [0017]In a possible implementation, the heartbeat packet is a heartbeat packet exchanged between the mobile terminal and the server. [0018]According to a second aspect, a method for reducing power consumption of a mobile terminal is provided. An electronic device has a Wi-Fi module and a Bluetooth module, and the electronic device establishes a communication connection to a server. The method includes: The electronic device respectively establishes Wi-Fi connections to N mobile terminals by using the Wi-Fi module, so that the N mobile terminals interact with the server by using the Wi-Fi connections. If Wi-Fi modules of M mobile terminals in the N mobile terminals enter a sleep state, the electronic device respectively establishes Bluetooth connections to the M mobile terminals by using the Bluetooth module, to transmit to-be-sent or to-be-received first packets of the M mobile terminals. The first packet is a heartbeat packet or a packet used to establish a transport layer link, M and N are positive integers, and M is less than or equal to N. Therefore, power consumption of the M mobile terminals is reduced. [0019]In a possible implementation, after the Wi-Fi modules of the M mobile terminals in the N mobile terminals enter the sleep state, where M is less than N, the method further includes: The electronic device transmits, by using a Wi-Fi connection, packets to be sent or to be received by mobile terminals other than the M mobile terminals and whose Wi-Fi modules do not enter the sleep state. [0020]In a possible implementation, the method further includes: If all Wi-Fi modules of the N mobile terminals enter the sleep state, that is, if M is equal to N, the electronic device controls the Wi-Fi module of the electronic device to enter the sleep state. [0021]In a possible implementation, the Bluetooth connection is a classic Bluetooth connection or a Bluetooth low energy connection. [0022]In a possible implementation, the electronic device is any one of a wireless router, an accompanying Wi-Fi device, or a mobile terminal with a hotspot capability. [0023]In a possible implementation, the heartbeat packet is a heartbeat packet exchanged between the mobile terminal and the server. [0024]According to a third aspect, a mobile terminal is provided, including a processor, a memory, a touchscreen, a Wi-Fi module, and a Bluetooth module. The memory, the touchscreen, the Wi-Fi module, and the Bluetooth module are coupled to the processor, and the memory is configured to store computer program code. The computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the mobile terminal performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0025]According to a fourth aspect, an electronic device is provided, including a processor, a memory, a Wi-Fi module, and a Bluetooth module. The memory, the Wi-Fi module, and the Bluetooth module are coupled to the processor, and the memory is configured to store computer program code. The computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the electronic device performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0026]According to a fifth aspect, an apparatus is provided. The apparatus is included in a mobile terminal, and the apparatus has a function of implementing behavior of the mobile terminal in any method in the foregoing aspects and the possible implementations of the foregoing aspects. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or the software includes at least one module or unit corresponding to the foregoing function, for example, a communication module or unit, or a control module or unit. [0027]According to a sixth aspect, an apparatus is provided. The apparatus is included in an electronic device, and the apparatus has a function of implementing behavior of the electronic device in any method in the foregoing aspects and the possible implementations of the foregoing aspects. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or the software includes at least one module or unit corresponding to the foregoing function, for example, a communication module or unit, or a control module or unit. [0028]According to a seventh aspect, a computer readable storage medium is provided, including computer instructions. When the computer instructions are run on a mobile terminal, the mobile terminal performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0029]According to an eighth aspect, a computer readable storage medium is provided, including computer instructions. When the computer instructions are run on an electronic device, the electronic device performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0030]According to a ninth aspect, a computer program product is provided. When the computer program product runs on a computer, the computer performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0031]According to a tenth aspect, a chip system is provided, including a processor. When the processor executes instructions, the processor performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. BRIEF DESCRIPTION OF THE DRAWINGS [0032]FIG. 1 is a schematic structural diagram of a communications system according to an embodiment of this application; [0033]FIG. 2A is a schematic structural diagram 1 of a mobile terminal according to an embodiment of this application; [0034]FIG. 2B is a schematic structural diagram 2 of a mobile terminal according to an embodiment of this application; [0035]FIG. 3 is a schematic diagram of some user interfaces of a mobile terminal according to an embodiment of this application; [0036]FIG. 4 is a schematic flowchart of a method for reducing power consumption of a mobile terminal according to an embodiment of this application; [0037]FIG. 5A is a schematic flowchart of another method for reducing power consumption of a mobile terminal according to an embodiment of this application; [0038]FIG. 5B is a schematic flowchart of another method for reducing power consumption of a mobile terminal according to an embodiment of this application; and [0039]FIG. 6 is a schematic structural diagram of a chip system according to an embodiment of this application. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0040]In the embodiments of this application, words such as “example” or “for example” are used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as “example” or “for example” in the embodiments of this application should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the words such as “example” or “for example” is intended to present a relative concept in a specific manner. [0041]The following terms “first” and “second” are merely intended for a purpose of description, and shall not be understood as an indication or implication of relative importance or implicit indication of a quantity of indicated technical features. Therefore, a feature limited by “first” or “second” may explicitly or implicitly include one or more features. In the descriptions of the embodiments of this application, unless otherwise stated, “a plurality of” means two or more than two. [0042]Applications installed on a mobile terminal generally provide rich functions for a user. When using the application on the mobile terminal, the user usually needs to access a network, to be specific, establish, by using one or more networks, a communication connection to a server corresponding to the application. Currently, the mobile terminal may establish, by using a configured modem, a communication connection to the server in a wireless communication connection manner such as 2G/3G/4G/5G by using a mobile communications network. Alternatively, the mobile terminal may establish, by using a configured Wi-Fi module, a communication connection to the server in a connection manner of a wireless local area network (for example, a Wi-Fi network) by using the internet or a mobile communications network. In an example, the mobile terminal establishes a communication connection to a wireless router by using a Wi-Fi wireless connection technology, and accesses the internet by using the wireless router, to interact with the server. Alternatively, the mobile terminal establishes a communication connection to an accompanying Wi-Fi device (or referred to as a mobile Wi-Fi device) by using a Wi-Fi wireless connection technology, and accesses a mobile communications network by using the accompanying Wi-Fi device, to interact with the server. [0043]Wi-Fi has a lower tariff and a higher network speed. Therefore, Wi-Fi is preferred for network access. It can be learned that power consumption of the Wi-Fi module is one of important indicators that affect a battery life of the mobile terminal. Currently, some solutions have been used to reduce the power consumption of the Wi-Fi module. For example, when the mobile terminal has no data transmission, the Wi-Fi module may be controlled to enter a sleep state. Subsequently, when the mobile terminal has data transmission, the Wi-Fi module is woken up to continue to work. [0044]It may be noted that after the Wi-Fi module enters the sleep state, because a large quantity of applications are installed on the mobile terminal, the Wi-Fi module is frequently woken up when these applications send heartbeat packets. In the embodiments of this application, when an application sends a heartbeat packet, the mobile terminal does not wake up the Wi-Fi module, but wakes up a Bluetooth module having lower power consumption than the Wi-Fi module, and sends a heartbeat packet of each application in a Bluetooth mode, to reduce the power consumption of the Wi-Fi module. In this way, overall power consumption of the mobile terminal is reduced, and the battery life of the mobile terminal is prolonged. [0045]FIG. 1 is a schematic structural diagram of a communications system according to an embodiment of this application. The communications system includes a mobile terminal 100 and an electronic device 200. Various applications may be installed and run on the mobile terminal 100, to provide rich functions for a user. Generally, the mobile terminal 100 may access the internet or a mobile communications network through the electronic device 200, to communicate with a server corresponding to each application. [0046]For example, the mobile terminal 100 in this application may be a mobile phone, a tablet computer, a personal computer (PC), a personal digital assistant (PDA), a smartwatch, a netbook, a wearable electronic device, an augmented reality (AR) device, a virtual reality (VR) device, a vehicle-mounted device, a smart car, a smart stereo, a robot, and the like. A specific form of the mobile terminal is not specifically limited in this application. [0047]FIG. 2A is a schematic structural diagram of the mobile terminal 100. The mobile terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identification module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, an optical proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like. [0048]It may be understood that the structure shown in this embodiment of the present invention constitutes no specific limitation on the mobile terminal 100. In some other embodiments of this application, the mobile terminal 100 may include more or fewer components than those shown in the figure, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. [0049]The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural network processing unit (NPU). Different processing units may be independent components, or may be integrated into one or more processors. [0050]The controller may generate an operation control signal based on instruction operation code and a time sequence signal, to control instruction fetching and instruction execution. [0051]A memory may be further disposed in the processor 110, and is configured to store instructions and data. In some embodiments, the memory in the processor 110 is a cache. The memory may store instructions or data that is used or cyclically used by the processor 110. If the processor 110 needs to use the instructions or the data again, the instructions or the data may be invoked directly from the memory. This avoids repeated access and reduces a waiting time of the processor 110, thereby improving efficiency of the system. [0052]In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (SIM) interface, a universal serial bus (USB) interface, and/or the like. [0053]The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include a plurality of I2C buses. The processor 110 may be separately coupled to the touch sensor, a charger, a flash, the camera 193, and the like by using different I2C bus interfaces. For example, the processor no may be coupled to the touch sensor by using an I2C interface, so that the processor no communicates with the touch sensor by using the I2C bus interface, to implement a touch function of the mobile terminal 100. [0054]The I2S interface may be used for audio communication. In some embodiments, the processor no may include a plurality of I2S buses. The processor no may be coupled to the audio module 170 by using an I2S bus, to implement communication between the processor no and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 by using the I2S interface, to implement a function of answering a call by using a Bluetooth headset. [0055]The PCM interface may also be used for audio communication to sample, quantize, and encode an analog signal. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by using a PCM bus interface. In some embodiments, the audio module 170 may alternatively transmit an audio signal to the wireless communication module 160 by using the PCM interface, to implement a function of answering a call by using a Bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication. [0056]The UART interface is a universal serial data bus used for asynchronous communication. The bus may be a bidirectional communications bus. The bus implements conversion between serial communication and parallel communication for data to be transmitted. In some embodiments, the UART interface is generally configured to connect the processor no to the wireless communication module 160. For example, the processor no communicates with a Bluetooth module in the wireless communication module 160 by using the UART interface, to implement a Bluetooth function. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 by using the UART interface, to implement a function of playing music by using a Bluetooth headset. [0057]The MIPI interface may be configured to connect the processor 110 to peripheral devices such as the display 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), and the like. In some embodiments, the processor 110 communicates with the camera 193 by using the CSI interface, to implement a photographing function of the mobile terminal 100. The processor 110 communicates with the display 194 by using the DSI interface, to implement a display function of the mobile terminal 100. [0058]The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal, or may be configured as a data signal. In some embodiments, the GPIO interface may be configured to connect the processor 110 to the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may alternatively be configured as an I2C interface, an I2S interface, a UART interface, an MIPI interface, or the like. [0059]The USB interface 130 is an interface that complies with a USB standard specification, and may be specifically a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be configured to connect to the charger to charge the mobile terminal 100, or may be configured to transmit data between the mobile terminal 100 and a peripheral device. The USB interface 130 may alternatively be configured to connect to a headset, to play audio by using the headset. The interface may alternatively be configured to connect to another mobile terminal, for example, an AR device. [0060]It may be understood that the interface connection relationship between modules shown in this embodiment of the present invention is merely an example for description, and does not constitute a structural limitation on the mobile terminal 100. In some other embodiments of this application, the mobile terminal 100 may alternatively use an interface connection manner different from that in the foregoing embodiment, or a combination of a plurality of interface connection manners. [0061]The charging management module 140 is configured to receive charging input from the charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger by using the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input by using a wireless charging coil of the mobile terminal 100. When charging the battery 142, the charging management module 140 may further supply power to the mobile terminal by using the power management module 141. [0062]The power management module 141 is configured to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may be further configured to monitor parameters such as a battery capacity, a quantity of battery cycles, and a battery health status (leakage and impedance). In some other embodiments, the power management module 141 may alternatively be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 may alternatively be disposed in a same device. [0063]A wireless communication function of the mobile terminal 100 may be implemented by using the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like. [0064]The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the mobile terminal 100 may be configured to cover a single or more communication bands. Different antennas may be further multiplexed to improve antenna utilization. For example, the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In some other embodiments, the antenna may be used in combination with a tuning switch. [0065]The mobile communication module 150 may provide a wireless communication solution that is applied to the mobile terminal 100 and that includes 2G/3G/4G/5G or the like. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 may receive an electromagnetic wave by using the antenna 1, perform processing such as filtering and amplification on the received electromagnetic wave, and transmit the received electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may further amplify a signal modulated by the modem processor, and convert the signal into an electromagnetic wave by using the antenna 1 for radiation. In some embodiments, at least some function modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some function modules of the mobile communication module 150 and at least some modules of the processor 110 may be disposed in a same device. [0066]The modem processor may include a modulator and a demodulator. The modulator is configured to modulate a low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low frequency baseband signal. Then, the demodulator transmits the low frequency baseband signal obtained through demodulation to the baseband processor for processing. After being processed by the baseband processor, the low frequency baseband signal is transmitted to the application processor. The application processor outputs an audio signal by using an audio device (not limited to the speaker 170A, the receiver 170B, or the like), or display an image or a video by using the display 194. In some embodiments, the modem processor may be an independent device. In some other embodiments, the modem processor may be independent of the processor 110, and disposed in a same device with the mobile communication module 150 or another function module. [0067]The wireless communication module 160 may provide a wireless communication solution that is applied to the mobile terminal 100 and that includes a wireless local area network (WLAN) (for example, a Wireless Fidelity (Wi-Fi) network), Bluetooth (BT), a global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), or the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives an electromagnetic wave by using the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signal, and sends a processed signal to the processor 110. The wireless communication module 160 may further receive a to-be-sent signal from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into an electromagnetic wave by using the antenna 2 for radiation. [0068]In some embodiments of this application, when determining that all applications have no data transmission, the processor 110 may indicate a WLAN module (for example, a Wi-Fi module) in the wireless communication module to enter a sleep state. When the WLAN module is in the sleep state, if an application needs to send a heartbeat packet, the processor 110 indicates a BT module in the wireless communication module to establish a communication connection between the mobile terminal 100 and the electronic device 200, and send a heartbeat packet of each application by using the communication connection. When determining that one or more applications need to send data (non-heartbeat packets), the processor 110 wakes up the WLAN module, establishes a WLAN connection between the mobile terminal 100 and the electronic device, and transmits the dat(String), 相关申请的交叉引用 [0001] 本申请是2020年11月9日提交的国际申请PCT/CN2020/127544的继续申请,该申请要求2020年1月15日提交的中国专利申请202010043528.2的优先权。上述申请的公开内容是 特此通过引用将其全部内容并入本文。 技术领域 [0002] 本申请涉及移动终端技术领域,尤其涉及一种降低移动终端功耗的方法及移动终端。 背景 [0003] 随着电子技术的发展,移动终端提供了越来越多的功能,丰富了人们的生活。 用户在移动终端上使用应用程序时,通常需要访问网络,具体而言,通过一个或多个网络与该应用程序对应的服务器建立通信连接。 [0004] Wi-Fi资费更低,网速更高。 因此,Wi-Fi 是用户接入网络的首选方式。 移动终端可以通过配置的Wi-Fi模块通过互联网或移动通信网络以无线局域网(例如Wi-Fi网络)的连接方式与服务器建立通信连接 . 或者,移动终端通过Wi-Fi模块,以无线局域网的连接方式(例如 ,Wi-Fi 网络),并通过随附的 Wi-Fi 设备访问移动通信网络,与服务器交互。 [0005] 随着用户上网时间的增加,Wi-Fi模块的工作时间也随之延长,Wi-Fi模块的功耗非常高。 可以看出,Wi-Fi模块的功耗是影响移动终端续航的重要指标之一。 因此,如何降低移动终端中Wi-Fi模块的功耗一直是厂商研究的热点。 概括 [0006] 本申请提供一种降低移动终端功耗的方法及移动终端,以降低移动终端中Wi-Fi模块的功耗,从而有助于延长移动终端的待机时间。 [0007] 为实现上述目的,本申请实施例提供以下技术方案。 [0008] 根据第一方面,提供了一种用于降低移动终端的功耗的方法。 移动终端具有Wi-Fi模块和蓝牙模块。 该方法包括:移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接,移动终端通过Wi-Fi连接与服务器交互。 如果移动终端在第一时间段内没有发送或接收数据包,则移动终端控制Wi-Fi模块进入休眠状态,该数据包包括第一数据包和第二数据包,或者该数据包包括第二数据包。 包。 第一报文为心跳报文或用于建立传输层链路的报文,第二报文为第一报文以外的报文。 Wi-Fi模块进入休眠状态后,如果移动终端有待发送的第一包,移动终端通过蓝牙模块建立的蓝牙连接将待发送的第一包发送给电子设备。 设备。 [0009] 可以了解到,当移动终端的Wi-Fi模块处于休眠状态时,如果移动终端只需要发送第一个数据包,移动终端不会唤醒Wi-Fi模块,而是唤醒 蓝牙模块的功耗低于Wi-Fi模块,并以蓝牙模式发送第一包,以降低Wi-Fi模块的功耗。 这样,降低了移动终端的整体功耗,延长了移动终端的电池寿命。 [0010]在一种可能的实现方式中,该方法还包括: Wi-Fi模块进入休眠状态后,若移动终端有待发送的第一包,则移动终端唤醒蓝牙模块,建立蓝牙连接 使用蓝牙模块的电子设备。 [0011] 在一些示例中,在Wi-Fi模块进入休眠状态后,移动终端开始与电子设备建立蓝牙连接。 或者,在Wi-Fi模块进入休眠状态后,移动终端仅在确定需要发送第一包时才与电子设备建立蓝牙连接。 在一些其他示例中,移动终端也可以在Wi-Fi模块进入休眠状态之前与电子设备建立蓝牙连接。 因此,提供了移动终端与电子设备之间建立蓝牙连接的多种场合。 [0012] 在一种可能的实现方式中,该方法还包括: 移动终端发送待发送的第一包后,如果移动终端在第二时间段内没有发送或接收到其他包,则移动终端控制蓝牙模块进入 一种睡眠状态。 这有助于进一步降低蓝牙模块的功耗。 [0013] 在一种可能的实现方式中,蓝牙连接为经典蓝牙连接或蓝牙低功耗连接。 [0014] 在一种可能的实现方式中,电子设备为无线路由器、随行的Wi-Fi设备或具有热点能力的移动终端中的任一种。 [0015] 在一种可能的实现方式中,在Wi-Fi模块进入休眠状态后,该方法还包括: 若移动终端有待发送的第二包或待接收的第二包,则移动终端唤醒 Wi-Fi模块,通过Wi-Fi模块重新建立移动终端与电子设备的Wi-Fi连接,并通过Wi-Fi连接发送第二数据包,移动终端保持或断开蓝牙连接 在移动终端和电子设备之间。 [0016] 在一种可能的实现方式中,在Wi-Fi模块进入休眠状态后,如果移动终端有待发送的第一包,则在移动终端通过蓝牙连接发送该待发送的第一包之前 所述蓝牙模块发送至所述电子设备,所述方法还包括: 所述移动终端接收用户开启第一功能的指示,或者所述移动终端在确定满足第一条件时开启所述第一功能,所述第一功能为 移动终端降低功耗的功能,第一条件包括:移动终端的电池电量小于预设值,移动终端启用的应用数量大于预设数量,移动终端 终端启用任何一个或多个预设应用程序。 [0017] 在一种可能的实现方式中,所述心跳包为移动终端与服务器之间交互的心跳包。 [0018] 根据第二方面,提供了一种降低移动终端功耗的方法。 电子装置具有Wi-Fi模块及蓝牙模块,电子装置与服务器建立通讯连接。 该方法包括:电子设备通过Wi-Fi模块分别与N个移动终端建立Wi-Fi连接,以使N个移动终端通过Wi-Fi连接与服务器进行交互。 如果N个移动终端中的M个移动终端的Wi-Fi模块进入休眠状态,则电子设备通过蓝牙模块分别与M个移动终端建立蓝牙连接,发送待发送或待接收 M个移动终端的第一个数据包。 第一报文为心跳报文或用于建立传输层链路的报文,M和N为正整数,M小于或等于N,从而降低了M个移动终端的功耗。 [0019]在一种可能的实现方式中,N个移动终端中的M个移动终端的Wi-Fi模块进入休眠状态后,M小于N,该方法还包括: 电子设备通过Wi-Fi连接进行传输 ,除M个移动终端外,其Wi-Fi模块未进入睡眠状态的移动终端要发送或要接收的数据包。 [0020] 在一种可能的实现方式中,该方法还包括: 若N个移动终端的Wi-Fi模块全部进入休眠状态,即M等于N,则电子设备控制电子设备的Wi-Fi模块 进入睡眠状态。 [0021] 在一种可能的实现方式中,蓝牙连接为经典蓝牙连接或蓝牙低功耗连接。 [0022] 在一种可能的实现方式中,电子设备为无线路由器、随行的Wi-Fi设备或具有热点能力的移动终端中的任一种。 [0023] 在一种可能的实现方式中,所述心跳包为移动终端与服务器之间交互的心跳包。 [0024] 第三方面,提供一种移动终端,包括处理器、存储器、触摸屏、Wi-Fi模块和蓝牙模块。 存储器、触摸屏、Wi-Fi模块和蓝牙模块耦合到处理器,并且存储器被配置为存储计算机程序代码。 所述计算机程序代码包括计算机指令,当所述处理器从所述存储器中读取所述计算机指令时,所述移动终端执行上述任一方面的方法以及上述方面的可能实现方式。 [0025] 第四方面,提供一种电子装置,包括处理器、存储器、Wi-Fi模块以及蓝牙模块。 存储器、Wi-Fi模块和蓝牙模块耦合到处理器,并且存储器被配置为存储计算机程序代码。 所述计算机程序代码包括计算机指令,当所述处理器从所述存储器中读取所述计算机指令时,所述电子设备执行上述任一方面的方法以及上述方面的可能实施方式。 [0026] 根据第五方面,提供了一种装置。 该装置包括在移动终端中,具有实现上述方面的任一方法和上述方面的可能实现方式中的移动终端的行为的功能。 该功能可以通过硬件来实现,也可以通过硬件执行相应的软件来实现。 硬件或软件包括与上述功能对应的至少一个模块或单元,例如通信模块或单元,或者控制模块或单元。 [0027] 根据第六方面,提供了一种装置。 该装置包括在电子设备中,具有实现电子设备在上述方面和上述方面的可能实现方式中的任一种方法中的行为的功能。 该功能可以通过硬件来实现,也可以通过硬件执行相应的软件来实现。 硬件或软件包括与上述功能对应的至少一个模块或单元,例如通信模块或单元,或者控制模块或单元。 [0028] 根据第七方面,提供了一种计算机可读存储介质,包括计算机指令。 当计算机指令在移动终端上运行时,移动终端执行上述任一方面的方法及上述方面的可能实现方式。 [0029] 根据第八方面,提供了一种计算机可读存储介质,包括计算机指令。 当计算机指令在电子设备上运行时,电子设备执行上述任一方面的方法以及上述方面的可能实现方式。 [0030]根据第九方面,提供了一种计算机程序产品。 当计算机程序产品在计算机上运行时,计算机执行上述任一方面的方法以及上述方面的可能实现方式。 [0031] 第十方面,提供一种芯片系统,包括处理器。 当处理器执行指令时,处理器执行上述任一方面的方法以及上述方面的可能实现方式。 附图的简要说明 [0032] 图1为本申请实施例提供的一种通信系统的结构示意图; [0033] 图2A是结构示意图 1 根据本申请的一个实施例的移动终端的; [0034] 图2B为结构示意图 2 根据本申请的一个实施例的移动终端的; [0035] 图3为本申请实施例提供的移动终端部分用户界面示意图; [0036] 图4为本申请实施例提供的一种降低移动终端功耗的方法的流程示意图; [0037] 图5A为本申请实施例提供的另一种降低移动终端功耗的方法的流程示意图; [0038] 图5B为本申请实施例提供的另一种降低移动终端功耗的方法的流程示意图; 和 [0039] 图6为本申请实施例提供的一种芯片系统的结构示意图。 说明性实施例的详细说明 [0040] 在本申请实施例中,“示例”或“例如”等词语用于表示举例、说明或描述。 在本申请的实施例中描述为“示例”或“例如”的任何实施例或设计方案不应被解释为比另一个实施例或设计方案更优选或具有更多优点。 确切地说,使用“example”或“for example”等词语是为了以特定的方式呈现一个相对的概念。 [0041] 以下术语“第一”和“第二”仅用于描述目的,不应被理解为相对重要性的指示或暗示或所指示的技术特征的数量的隐含指示。 因此,受“第一”或“第二”限制的特征可以明确或隐含地包括一个或多个特征。 在本申请实施例的描述中,除非另有说明,“多个”是指两个或两个以上。 [0042] 安装在移动终端上的应用程序通常为用户提供丰富的功能。 用户在移动终端上使用应用程序时,通常需要接入网络,具体而言,通过一个或多个网络与该应用程序对应的服务器建立通信连接。 目前,移动终端可以通过配置的调制解调器,通过移动通信网络以2G/3G/4G/5G等无线通信连接方式与服务器建立通信连接。 或者,移动终端可以通过配置的Wi-Fi模块,通过互联网或移动设备以无线局域网(例如Wi-Fi网络)的连接方式与服务器建立通信连接。 通讯网络。 在一个示例中,移动终端通过Wi-Fi无线连接技术与无线路由器建立通信连接,并通过无线路由器访问互联网,与服务器交互。 或者,移动终端通过Wi-Fi无线连接技术与随行Wi-Fi设备(或称为移动Wi-Fi设备)建立通信连接,并通过随行Wi-Fi接入移动通信网络。 Fi 设备,用于与服务器交互。 [0043]Wi-Fi资费更低,网速更高。 因此,Wi-Fi 是首选的网络访问方式。 可以看出,Wi-Fi模块的功耗是影响移动终端续航的重要指标之一。 目前,已经采用了一些方案来降低Wi-Fi模块的功耗。 例如,当移动终端没有数据传输时,可以控制Wi-Fi模块进入休眠状态。 随后,当移动终端有数据传输时,唤醒Wi-Fi模块继续工作。 [0044] 需要注意的是,Wi-Fi模块进入休眠状态后,由于移动终端安装了大量的应用程序,这些应用程序在发送心跳包时会频繁地唤醒Wi-Fi模块。 在本申请实施例中,当应用发送心跳包时,移动终端不会唤醒Wi-Fi模块,而是唤醒功耗比Wi-Fi模块低的蓝牙模块,并发送心跳包 蓝牙模式下的每个应用程序,以降低Wi-Fi模块的功耗。 这样,降低了移动终端的整体功耗,延长了移动终端的电池寿命。 [0045] 图1为本申请实施例提供的一种通信系统的结构示意图。 该通信系统包括移动终端 100 和一个电子设备 200 . 可以在移动终端上安装和运行各种应用程序 100 , 为用户提供丰富的功能。 一般来说,移动端 100 可以通过电子设备访问互联网或移动通信网络 200 ,与每个应用程序对应的服务器进行通信。 [0046] 例如,移动终端 100 在此应用中可以是手机、平板电脑、个人电脑 (PC)、个人数字助理 (PDA)、智能手表、上网本、可穿戴电子设备、增强现实 (AR) 设备、虚拟现实 (VR)设备、车载设备、智能汽车、智能音响、机器人等。 本申请对移动终端的具体形式不作具体限定。 [0047] 图2A是移动终端的结构示意图 100 . 移动终端 100 可能包括处理器 110 ,一个外部存储器接口 120 , 内部存储器 121 , 一个通用串行总线 (USB) 接口 130 , 充电管理模块 140 , 电源管理模块 141 , 一个电池 142 , 天线 1 , 天线 2 , 移动通信模块 150 , 无线通讯模块 160 , 一个音频模块 170 , 扬声器 170 A、接收器 170 B、麦克风 170 C、耳机插孔 170 D、传感器模块 180 , 关键 190 , 一个马达 191 , 一个指标 192 , 相机 193 , 一个显示器 194 ,一个用户识别模块(SIM)卡接口 195 ,等等。 传感器模块 180 可包括压力传感器、陀螺仪传感器、气压传感器、磁传感器、加速度传感器、距离传感器、光学接近传感器、指纹传感器、温度传感器、触摸传感器、环境光传感器、 骨传导传感器等。 [0048] 可以理解的是,本发明实施例所示的结构不构成对移动终端的具体限制 100 . 在本申请的其他一些实施例中,移动终端 100 可以包括比图中所示更多或更少的组件,或者组合一些组件,或者拆分一些组件,或者具有不同的组件布置。 所示组件可以以硬件、软件或软件和硬件的组合来实现。 [0049] 处理器 110 可以包括一个或多个处理单元。 例如,处理器 110可包括应用处理器 (AP)、调制解调器处理器、图形处理单元 (GPU)、图像信号处理器 (ISP)、控制器、视频编解码器、数字信号处理器 (DSP)、基带处理器和/ 或神经网络处理单元(NPU)。 不同的处理单元可以是独立的组件,也可以集成到一个或多个处理器中。 [0050] 控制器可以基于指令操作码和时序信号产生操作控制信号,以控制指令获取和指令执行。 [0051] 处理器中还可以设置存储器 110 ,并且被配置为存储指令和数据。 在一些实施例中,处理器中的存储器 110 是一个缓存。 存储器可以存储处理器使用或循环使用的指令或数据 110 . 如果处理器 110 需要再次使用指令或数据时,可以直接从内存中调用指令或数据。 这避免了重复访问并减少了处理器的等待时间 110 ,从而提高系统的效率。 [0052] 在一些实施例中,处理器 110 可以包括一个或多个接口。 该接口可以包括内部集成电路(I2C)接口、内部集成电路声音(I2S)接口、脉冲编码调制(PCM)接口、通用异步接收器/发送器(UART)接口、移动工业处理器接口 (MIPI)、通用输入/输出(GPIO)接口、订户身份模块(SIM)接口、通用串行总线(USB)接口等。 [0053] I2C 接口是双向同步串行总线,包括串行数据线 (SDA) 和串行时钟线 (SCL)。 在一些实施例中,处理器 110 可以包括多个I2C总线。 处理器 110 可以单独耦合到触摸传感器、充电器、闪光灯、相机 193 等通过使用不同的 I2C 总线接口。 例如,处理器no可以通过I2C接口与触摸传感器耦合,使得处理器no通过I2C总线接口与触摸传感器通信,实现移动终端的触摸功能。 100 . [0054] I2S 接口可用于音频通信。 在一些实施例中,处理器可以包括多个I2S总线。 处理器no可以耦合到音频模块 170 使用I2S总线,实现处理器No与音频模块的通信 170 . 在一些实施例中,音频模块 170 可以向无线通信模块发送音频信号 160 通过I2S接口,实现蓝牙耳机接听电话的功能。 [0055] PCM 接口也可用于音频通信以对模拟信号进行采样、量化和编码。 在一些实施例中,音频模块 170 以及无线通讯模块 160 可以通过使用PCM总线接口来耦合。 在一些实施例中,音频模块 170 可替代地向无线通信模块发送音频信号 160 通过PCM接口,实现蓝牙耳机接听电话的功能。 I2S 接口和 PCM 接口都可以用于音频通信。 [0056] UART 接口是用于异步通信的通用串行数据总线。 总线可以是双向通信总线。 总线对要传输的数据实现串行通信和并行通信的转换。 在一些实施例中,UART接口通常被配置为将处理器no连接到无线通信模块 160 . 例如,处理器不与无线通信模块中的蓝牙模块通信 160 通过使用UART接口,实现蓝牙功能。 在一些实施例中,音频模块 170 可以向无线通信模块发送音频信号 160 通过UART接口,实现蓝牙耳机播放音乐的功能。 [0057] MIPI接口可配置为连接处理器 110到显示器等外围设备 194 和相机 193 . MIPI接口包括相机串行接口(CSI)、显示器串行接口(DSI)等。 在一些实施例中,处理器 110 与相机通信 193 通过CSI接口,实现移动终端的拍照功能 100 . 处理器 110 与显示器通信 194 通过DSI接口,实现移动终端的显示功能 100 . [0058] GPIO 接口可以通过软件进行配置。 GPIO接口可以配置为控制信号,也可以配置为数据信号。 在一些实施例中,GPIO接口可以被配置为连接处理器 110 到相机 193 , 显示器 194 , 无线通讯模块 160 , 音频模块 170 , 传感器模块 180 ,等等。 GPIO接口也可以配置为I2C接口、I2S接口、UART接口、MIPI接口等。 [0059] USB接口 130 是符合USB标准规范的接口,具体可以是Mini USB接口、Micro USB接口、USB Type C接口等。 USB接口 130 可配置为连接充电器为移动终端充电 100 ,或者可以配置为在移动终端之间传输数据 100 和外围设备。 USB接口 130 或者,可以配置为连接到耳机,通过使用耳机播放音频。 该接口可以替代地被配置为连接到另一个移动终端,例如,AR设备。 [0060] 可以理解的是,本发明实施例所示的各模块之间的接口连接关系仅为举例说明,并不构成对移动终端的结构限制 100 . 在本申请的其他一些实施例中,移动终端 100 也可以采用与上述实施例不同的接口连接方式,或者多种接口连接方式的组合。 [0061] 充电管理模块 140 配置为接收来自充电器的充电输入。 充电器可以是无线充电器或有线充电器。 在一些有线充电实施例中,充电管理模块 140 可通过USB接口接收来自有线充电器的充电输入 130 . 在一些无线充电实施例中,充电管理模块 140 可以通过移动终端的无线充电线圈接收无线充电输入 100 . 给电池充电时 142 ,充电管理模块 140 还可以通过电源管理模块为移动终端供电 141 . [0062] 电源管理模块 141 配置为连接电池 142 ,充电管理模块 140 , 和处理器 110 . 电源管理模块 141 从电池接收输入 142 和/或充电管理模块 140 , 并为处理器供电 110 , 内部存储器 121 , 显示器 194 , 相机 193 , 无线通讯模块 160 ,等等。 电源管理模块 141 还可以用于监测电池容量、电池循环次数、电池健康状态(漏电和阻抗)等参数。 在一些其他实施例中,电源管理模块 141 或者可以设置在处理器中 110 . 在一些其他实施例中,电源管理模块 141 和充电管理模块 140 或者可以将其设置在同一设备中。 [0063] 一种移动终端的无线通信功能 100 可以通过使用天线来实现 1 , 天线 2 , 移动通信模块 150 , 无线通讯模块 160 、调制解调器处理器、基带处理器等。 [0064] 天线 1 和天线 2 被配置为发送和接收电磁波信号。 移动终端中的每个天线 100 可以被配置为覆盖单个或多个通信频带。 可以进一步复用不同的天线以提高天线利用率。 例如,天线 1 可以复用为无线局域网的分集天线。 在一些其他实施例中,天线可以与调谐开关结合使用。 [0065] 移动通信模块 150 可提供应用于移动终端的无线通信解决方案 100 其中包括2G/3G/4G/5G等。 移动通信模块 150 可以包括至少一个滤波器、开关、功率放大器、低噪声放大器(LNA)等。 移动通信模块 150 可以通过天线接收电磁波 1 ,对接收到的电磁波进行滤波、放大等处理,并将接收到的电磁波传送到调制解调器处理器进行解调。 移动通信模块 150 可以进一步放大调制解调处理器调制的信号,并通过天线将信号转换为电磁波 1 为辐射。 在一些实施例中,移动通信模块的至少一些功能模块 150 可以设置在处理器中 110 . 在一些实施例中,移动通信模块的至少一些功能模块 150 以及处理器的至少一些模块 110 可以设置在同一设备中。 [0066] 调制解调器处理器可以包括调制器和解调器。 调制器用于将要发送的低频基带信号调制成中高频信号。 解调器被配置为将接收到的电磁波信号解调为低频基带信号。 然后,解调器将解调得到的低频基带信号传送给基带处理器进行处理。 低频基带信号经过基带处理器处理后,传送到应用处理器。 应用处理器通过音频设备(不限于扬声器)输出音频信号 170 A、接收器 170 B等),或使用显示器显示图像或视频 194 . 在一些实施例中,调制解调器处理器可以是独立设备。 在一些其他实施例中,调制解调器处理器可以独立于处理器 110 ,并与移动通讯模块设置于同一装置中 150 或其他功能模块。 [0067] 无线通讯模块 160 可提供应用于移动终端的无线通信解决方案 100 其中包括无线局域网 (WLAN)(例如,无线保真 (Wi-Fi) 网络)、蓝牙 (BT)、全球导航卫星系统 (GNSS)、调频 (FM)、近场通信 ( NFC)、红外线(IR)等。 无线通讯模块 160 可以是集成了至少一个通信处理模块的一个或多个设备。 无线通讯模块 160 使用天线接收电磁波 2 ,对电磁波信号进行调频和滤波处理,将处理后的信号发送给处理器 110 . 无线通讯模块 160 还可以从处理器接收待发送信号 110 ,对信号进行调频放大,利用天线将信号转换成电磁波 2 为辐射。 [0068] 在本申请的一些实施例中,当确定所有应用都没有数据传输时,处理器 110 可以指示无线通信模块中的WLAN模块(例如,Wi-Fi模块)进入休眠状态。 当 WLAN 模块处于休眠状态时,如果应用程序需要发送心跳包,处理器 110 表示无线通信模块中的BT模块建立移动终端之间的通信连接100 和电子设备 200 ,并通过通信连接发送每个应用程序的心跳包。 当确定一个或多个应用程序需要发送数据(非心跳包)时,处理器 110 唤醒WLAN模块,建立移动终端之间的WLAN连接 100 以及电子装置,并通过WLAN连接传输一个或多个应用程序的数据。 也就是说,当移动终端上的应用程序 100 只需要发送心跳包,移动端 100 不唤醒WLAN模块,而是使用功耗比WLAN模块低的BT模块建立通信连接。 这样就降低了WLAN模块的功耗,降低了移动终端的整体功耗。 100 降低了。 [0069] 在一些实施例中,天线 1 移动终端的 100 耦接移动通讯模块 150 , 和天线 2 耦接无线通讯模块 160 ,让移动端 100 可以通过使用无线通信技术与网络和其他设备进行通信。 无线通信技术可以包括诸如全球移动通信系统(GSM)、通用分组无线电服务(GPRS)、码分多址(CDMA)、宽带码分多址(WCDMA)、时分码等技术。 分多址 (TD-SCDMA)、长期演进 (LTE)、BT、GNSS、WLAN、NFC、FM 和/或 IR。 GNSS可以包括全球定位系统(GPS)、全球导航卫星系统(GLONASS)、北斗导航卫星系统(BDS)、准天顶卫星系统(QZSS)和/或基于卫星的增强系统( SBAS)。 [0070] 移动终端 100 使用GPU实现显示功能,显示 194 、应用处理器等。 GPU是用于图像处理的微处理器,与显示器相连 194 和应用处理器。 GPU 被配置为执行图形渲染的数学和几何计算。 处理器 110 可以包括一个或多个GPU,它们执行程序指令以生成或改变显示信息。 [0071] 显示器 194 被配置为显示图像、视频等。 显示器 194 包括显示面板。 显示面板可以是液晶显示器(LCD)、有机发光二极管(OLED)、有源矩阵有机发光二极管(AMOLED)、柔性发光二极管(FLED)、mini-LED 、微型LED、微型OLED、量子点发光二极管(QLED)等。 在一些实施例中,移动终端 100 可能包括一个或 N 个显示器 194 ,其中 N 是大于 1 的正整数。 [0072] 移动终端 100 可以通过ISP实现拍照功能,摄像头 193 、视频编解码器、GPU、显示器 194 、应用处理器等。 [0073] ISP配置为处理摄像头反馈的数据 193 . 例如,在拍摄过程中,快门打开,光线通过镜头传输到相机的感光元件,将光信号转换为电信号。 相机的感光元件将电信号传送给ISP进行处理,使ISP将电信号转换成肉眼可见的图像。 ISP可以进一步对图像的噪声、亮度和肤色进行算法优化。 ISP可以进一步优化拍摄场景的参数,例如曝光和色温。 在一些实施例中,ISP可以设置在相机中 193 . [0074] 相机 193被配置为捕获静态图像或视频。 镜头为物体产生光学影像,并将光学影像投射到感光元件上。 光敏元件可以是电荷耦合器件(CCD)或互补金属氧化物半导体(CMOS)光电晶体管。 感光元件将光信号转换为电信号,然后将电信号传输到ISP,转换为数字图像信号。 ISP将数字图像信号输出到DSP进行处理。 DSP将数字图像信号转换为RGB或YUV等标准格式的图像信号。 在一些实施例中,移动终端 100 可能包括一个或 N 个摄像头 193 ,其中 N 是大于 1 的正整数。 [0075] 数字信号处理器被配置为处理数字信号,并且可以处理除了数字图像信号之外的另一个数字信号。 例如,当移动终端 100 选择频率,数字信号处理器用于对该频率的能量进行傅里叶变换。 [0076] 视频编解码器被配置为压缩或解压缩数字视频。 移动终端 100 可能支持一种或多种视频编解码器。 这样,移动终端 100 可以播放或录制多种编码格式的视频,例如,运动图像专家组(MPEG)-1、MPEG-2、MPEG-3和MPEG-4。 [0077] NPU 是一种神经网络 (NN) 计算处理器。 NPU通过借鉴生物神经网络结构的经验,例如借鉴人脑神经元之间传输方式的经验,对输入信息进行快速处理,进而不断进行自学习。 NPU可用于实现移动终端智能认知等应用 100 例如,图像识别、面部识别、语音识别和文本理解。 [0078] 外部存储器接口 120 可用于连接micro SD卡等外置存储卡,扩展移动终端的存储能力 100 . 外部存储卡通过外部存储接口与处理器通讯 120 ,实现数据存储功能。 例如,音乐或视频等文件存储在外部存储卡中。 [0079] 内部存储器 121 可以被配置为存储计算机可执行程序代码,并且可执行程序代码包括指令。 内部存储器 121 可以包括程序存储区和数据存储区。 程序存储区可以存储操作系统、至少一种功能(例如,声音播放功能或图像播放功能)所需的应用程序等。 数据存储区域可以存储在使用移动终端的过程中创建的数据(例如,音频数据或地址簿) 100 ,等等。 此外,内部存储器 121 可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储设备、闪存设备或通用闪存(universal flash storage,UFS)。 处理器 110 执行移动终端的各种功能应用和数据处理 100 通过运行存储在内部存储器中的指令 121 和/或存储在处理器中的存储器中的指令。 [0080] 移动终端 100 可以通过音频模块实现音乐播放或录音等音频功能 170 , 演讲者 170 A、接收器 170 B、麦克风 170 C、耳机插孔 170 D、应用处理器等。 [0081] 音频模块 170 用于将数字音频信息转换为模拟音频信号输出,还用于将模拟音频输入转换为数字音频信号。 音频模块 170 还可被配置为对音频信号进行编码和解码。 在一些实施例中,音频模块 170 可以设置在处理器中 110 ,或者音频模块的一些功能模块170 可以设置在处理器中 110 . [0082] 演讲者 170 A,也称为“喇叭”,被配置为将音频电信号转换为声音信号。 移动终端 100 可用于听音乐或使用扬声器听免提通话 170 一个。 [0083] 收件人 170 B,也称为“听筒”,用于将音频电信号转换为声音信号。 当移动端 100 用于接听电话或收听语音信息,放置听筒即可收听语音 170 B 接近人耳。 [0084] 麦克风 170 C,也称为“麦克风”或“麦克风”,用于将声音信号转换为电信号。 在拨打电话或发送语音信息时,用户可以将麦克风放在 170 C 靠近人嘴发声,向麦克风输入声音信号 170 C. 至少一个麦克风 170 C可以设置在移动终端中 100 . 在一些其他实施例中,两个麦克风 170 C可以设置在移动终端中 100 . 除了采集声音信号外,麦克风还可以实现降噪功能。 在一些其他实施例中,三个、四个或更多麦克风 170 C可以设置在移动终端中 100 ,用于采集声音信号、降噪、识别声源、实现定向录音等功能。 [0085] 耳机插孔 170 D 配置为连接到有线耳机。 耳机插孔 170 D可能是USB接口 130 ,或者可以是 3.5 毫米开放移动终端平台 (OMTP) 标准接口或美国蜂窝电信工业协会 (CTIA) 标准接口。 [0086] 钥匙 190 包括电源键、音量键等。 钥匙 190 可以是机械键,也可以是触摸键。 移动终端 100 可以接收按键输入,并生成与移动终端的用户设置和功能控制相关的按键信号输入 100 . [0087] 电机 191 可能会产生振动警报。 电机 191 可用于产生来电振动提示,或产生触摸操作振动反馈。 例如,在不同的应用程序(例如拍照和音频播放)上进行的触摸操作可以对应不同的振动反馈效果。 电机 191 可以进一步实现对显示器不同区域的触摸操作 194 以对应不同的振动反馈效果。 不同的应用场景(如时间提醒、信息接收、闹钟、游戏等)也可能对应不同的震动反馈效果。 也可以定制触摸操作的振动反馈效果。 [0088] 指标 192 可以是指示灯,可以用于指示充电状态和电量变化,也可以用于指示消息、未接电话、通知等。 [0089] SIM卡接口 195 配置为连接到 SIM 卡。 SIM卡可以插入SIM卡接口 195 或从 SIM 卡接口中移除 195 , 实现与移动终端的联系或分离 100 . 移动终端 100 可以支持一个或N个SIM卡接口,其中N为大于1的正整数。 SIM卡接口 195 可以支持nano-SIM卡、micro-SIM卡、SIM卡等。 同一个SIM卡接口可以插入多张卡 195 同时。 多个卡可以是相同类型或不同类型。 SIM卡接口 195 可能与不同类型的 SIM 卡兼容。 SIM卡接口 195 也可能与外部存储卡兼容。 移动终端 100 通过SIM卡与网络进行交互,实现通话、数据通信等功能。 在一些实施例中,移动终端 100使用eSIM,即嵌入式SIM卡。 eSIM卡可嵌入移动终端 100 , 和移动端分不开 100 . [0090] 一种移动终端的软件系统 100 可以使用分层架构、事件驱动架构、微内核架构、微服务架构或云架构。 本发明实施例以分层架构的Android系统为例,对移动终端的软件结构进行说明。 100 . [0091] 图2B是移动终端的软件结构框图 100 根据本发明的这个实施例。 [0092] 在分层架构中,软件被划分为多个层次,每一层都有明确的作用和职责。 层通过使用软件接口相互通信。 在一些实施例中,Android系统自上而下分为四层,分别为应用层、应用框架层、Android运行时(Android runtime)和系统库、内核层。 [0093] 如图2B所示,应用层可以包括一系列应用包,包括移动终端出厂前预配置的应用,或者用户安装后在应用市场等方式安装的应用。 移动终端出厂。 这些应用包括但不限于相机、图库、日历、电话、地图、导航、WLAN、蓝牙、音乐、视频、短信、浏览器、微信、淘宝、支付宝等应用(图中只展示了一部分) )。 这些应用大多需要网络访问,例如导航、浏览器、微信、淘宝和支付宝。 [0094] 应用程序框架层为应用程序层的应用程序提供应用程序编程接口(API)和编程框架。 应用程序框架层包括一些预定义的功能。 [0095] 如图2B所示,应用框架层可以包括窗口管理器、内容提供器、视图系统、电话管理器、资源管理器、通知管理器等。 窗口管理器用于管理窗口程序。 窗口管理器可以获取显示大小、判断是否有状态栏、锁屏、截屏等。 内容提供者被配置为存储和获取数据并使应用程序可以访问数据。 数据可以包括视频、图像、音频、拨打和接听的电话、浏览历史和书签、地址簿等。 视图系统包括视觉控件,例如,用于显示文本的控件和用于显示图片的控件。 视图系统可以被配置为构建应用程序。 显示界面可以包括一个或多个视图。 例如,包括SMS通知图标的显示界面可以包括用于显示文本的视图和用于显示图片的视图。 手机管家,用于提供移动终端的通讯功能 100 例如,通话状态管理(包括通话连接和断开等)。 资源管理器为应用程序提供各种资源,例如本地化字符串、图标、图片、布局文件和视频文件。 通知管理器使应用程序能够在状态栏中显示通知信息,该信息可用于传达通知类型的消息,该消息可以在短暂停留后自动消失而无需用户交互。 例如,通知管理器用于指示下载完成、提供消息提醒等。 通知管理器还可以提供以图表或滚动条文本的形式出现在系统顶部状态栏的通知,例如后台运行的应用程序的通知,还可以提供 以对话窗口的形式出现在屏幕上的通知。 例如状态栏显示文字信息、播放提示音、移动终端振动、指示灯闪烁等。 [0096]在本申请的一些实施例中,应用框架层还可以包括第一模块,用于收集各应用在应用层向服务器发送的数据包,并根据数据包的类型确定是否要 唤醒 Wi-Fi 模块或唤醒蓝牙模块。 例如,当确定应用层的应用程序在特定时间段内没有任何应用程序发送数据包时,第一模块可以通过内核层的Wi-Fi驱动程序指示Wi-Fi模块休眠。 又例如,当应用层的应用程序确定需要发送心跳包时,第一模块可以通过内核层的蓝牙驱动程序唤醒蓝牙模块,并通过建立的链路发送心跳包。 蓝牙模块。 如果蓝牙模块不处于休眠状态,则可以通过蓝牙模块建立的链路直接发送心跳包。 又例如,当应用层的应用程序确定需要发送数据包(非心跳数据包)时,第一模块可以通过内核层的Wi-Fi驱动程序唤醒Wi-Fi模块,并发送 应用程序的数据包通过Wi-Fi模块建立的链接。 [0097] 在本申请的另一个实施例中,第一模块还可以用于在应用层采集应用的心跳包,并在一段时间内集中发送应用的心跳包。 另外,在集中发送应用程序的心跳包时,通过内核层的蓝牙驱动程序唤醒蓝牙模块,通过蓝牙链路发送心跳包。 [0098] 在本申请的一些其他实施例中,所述第一模块还可以用于识别报文(如设备ID、设备IP地址、端口号和所使用的协议信息、TCP链路建立报文等) 在移动终端之间建立传输层链路 100 和电子设备 200 ,唤醒蓝牙模块,并通过蓝牙链路传输用于建立传输层链路的数据包。 需要说明的是,这种情况下,蓝牙链路只建立了物理层链路,没有建立传输层链路。 例如,控制报文(如用于广播移动终端地址的报文) 100 ) 移动端之间 100 和电子设备 200 可以携带传输层链路的报文。 换言之,可以预先建立传输层链路。 随后,当移动终端需要建立蓝牙链路或Wi-Fi链路时,在建立相应的物理层链路后,移动终端可以直接使用预先建立的传输层链路。 现有技术中,物理层Wi-Fi链路或物理层蓝牙链路建立后,还需要进一步建立传输层链路来传输报文。 在本申请实施例的方法中,与传统技术相比,由于提前建立了传输层链路,在移动终端唤醒Wi-Fi模块或蓝牙模块后,可以快速启动报文传输,从而 提高Wi-Fi模块或蓝牙模块的工作效率,有助于降低Wi-Fi模块或蓝牙模块的功耗。 因此,降低了移动终端的整体功耗。 [0099] Android 运行时包括一个内核库和一个虚拟机。 Android 运行时调度和管理 Android 系统。 [0100] 内核库包括两部分:一是Java语言需要调用的函数,二是Android的内核库。 [0101]应用层和应用框架层运行在虚拟机中。 虚拟机将应用层和应用框架层的Java文件作为二进制文件执行。 虚拟机被配置为执行对象生命周期管理、堆栈管理、线程管理、安全和异常管理以及垃圾收集等功能。 [0102] 系统库可以包括多个功能模块,例如表面管理器、媒体库、三维图形处理库(例如OpenGL ES)、二维图形引擎(例如SGL)。 [0103] 表面管理器被配置为管理显示子系统并为多个应用提供2D和3D层的融合。 [0104] 媒体库支持各种常见音视频格式、静态图片文件等的播放和录制。 媒体库可支持MPEG-4、H.264、MP3、AAC、AMR、JPG、PNG等多种音视频编码格式。 [0105] 三维图形处理库用于实现三维图形绘制、图像渲染、合成、图层处理等。 [0106] 2D图形引擎是用于2D绘图的绘图引擎。 [0107] 内核层是介于硬件和软件之间的一层。 内核层至少包括显示驱动程序、摄像头驱动程序、音频驱动程序和传感器驱动程序。 [0108] 电子设备 200 在这个应用程序中是一个可以为移动终端提供无线网络访问功能的设备 100 例如,无线路由器、便携式 Wi-Fi 设备(也称为随附的 Wi-Fi 设备或移动 Wi-Fi 设备)或客户端设备 (CPE),或者可能是提供 移动端热点 100 例如,可以是手机或平板电脑。 在这个应用程序中,电子设备 200 具有蓝牙模块,该蓝牙模块可以提供经典蓝牙(或称为传统蓝牙)功能和/或蓝牙低功耗功能。 [0109] 需要说明的是,对于电子设备的结构 200 ,参考移动端的结构 100 在图 2A 中。 电子设备 200 可以具有比图2A所示结构更多或更少的组件,或者组合一些组件,或者拆分一些组件,或者具有不同的组件布置。 所示组件可以以硬件、软件或软件和硬件的组合来实现。 [0110] 例如,当电子设备 200 是路由器,电子设备 200 可以包括处理器、存储器、无线通信模块、天线、电源模块、被配置为连接到互联网的网络接入模块等。 无线通信模块包括Wi-Fi模块和蓝牙模块。 Wi-Fi模块可用于与移动终端建立Wi-Fi连接 100 . 这样,移动终端 100 可以通过电子设备的网络访问模块访问互联网 200 . 蓝牙模块可用于与移动终端建立蓝牙连接(经典蓝牙连接或BLE连接) 100 ,让移动端 100 可以通过电子设备的网络访问模块访问互联网 200 . [0111] 其他内容参见移动终端相关结构说明 100 在图 2A 中。 细节不在此描述。 [0112] 又例如,当电子设备 200 是随附的 Wi-Fi 设备,电子设备 200 可以包括处理器、存储器、无线通信模块、天线、电源模块、移动通信模块等。 移动通信模块可以被配置为提供应用于电子设备的无线通信解决方案 100 其中包括2G/3G/4G/5G等。 [0113]无线通信模块包括Wi-Fi模块和蓝牙模块。 Wi-Fi模块可用于与移动终端建立Wi-Fi连接 100 . 这样,移动终端 100 可通过电子设备的移动通信模块接入移动通信网络 200 . 蓝牙模块可用于与移动终端建立蓝牙连接(经典蓝牙连接或BLE连接) 100 ,让移动端 100 可通过电子设备的移动通信模块接入移动通信网络 200 . [0114] 其他内容参见移动终端相关结构说明 100 在图 2A 中。 细节不在此描述。 [0115] 以下实施例中的所有技术方案均可以在移动终端中实现 100 具有上述硬件架构和软件架构。 [0116] 下面结合附图对本申请实施例提供的技术方案进行详细说明。 [0117] 例如,默认情况下,移动终端可以一直使用本申请实施例提供的方法,以降低移动终端的功耗。 或者,默认情况下,在特定场景下,移动终端可以采用本申请实施例提供的方法来降低移动终端的功耗。 例如,默认情况下,当电量低于预设值时(例如电量低于20%),移动终端可以自动开始使用本申请实施例提供的方法,以减少 移动终端的功耗。 又例如,默认情况下,当启用的应用程序的数量大于预设数量(例如5个)时,移动终端可以自动开始使用本申请实施例提供的方法,以降低应用程序的功耗。 移动终端。 又例如,当确定移动终端启用特定应用程序时(例如,特定应用程序是需要频繁发送心跳包的应用程序,例如即时通讯应用程序),移动终端自动开始使用 本申请实施例提供的方法,以降低移动终端的功耗。 [0118] 在其他一些示例中,也可以在移动终端中设置开关,用户可以通过该开关手动开启或关闭本申请实施例提供的降低移动终端功耗的功能。 例如,如图 ( 1 ) 在图 3 中,一个开关控制 301 可以设置在“设置”应用中的“WLAN”设置页面,供用户手动开启或关闭移动终端的省电功能。 再举一个例子,如( 2 ) 在图 3 中,一个开关控制 302 可以设置在“设置”应用程序中,供用户手动开启或关闭移动终端的省电功能。 [0119] 图4为本申请实施例提供的一种降低移动终端功耗的方法流程示意图。 详情如下: [0120] 小号 401 :移动终端与电子设备建立Wi-Fi通信连接和蓝牙通信连接,并通过电子设备与服务器交互。 [0121] 在一些实施例中,移动终端自动开启省电功能或用户手动开启省电功能后,移动终端可以自动开启或提示用户开启手机的Wi-Fi功能和蓝牙功能。 终端,分别与电子设备建立Wi-Fi连接和蓝牙连接。 蓝牙连接可以是经典的蓝牙连接,也可以是低功耗蓝牙(Bluetooth low energy,BLE)连接。 [0122]如果移动终端首次与电子设备建立Wi-Fi连接,用户需要选择电子设备对应的Wi-Fi名称、输入密码等,或者使用扫描等其他方式 快速响应码,用于建立移动终端与电子设备之间的Wi-Fi连接。 如果移动终端不是第一次与电子设备建立Wi-Fi连接,移动终端会存储电子设备对应的Wi-Fi名称和密码等信息,移动终端可以自动建立Wi-Fi连接。 - 与电子设备的 Fi 连接。 [0123] 与建立Wi-Fi连接类似,如果移动终端首次与电子设备建立蓝牙连接,用户需要进行选择电子设备对应的蓝牙名称等操作,然后移动终端 终端建立与电子设备的蓝牙连接。 如果移动终端之前已经与电子设备建立了蓝牙连接,则移动终端存储该电子设备对应的蓝牙名称等信息,随后移动终端可以自动与电子设备建立蓝牙连接。 [0124] 在其他一些实施例中,移动终端在开启Wi-Fi功能时,还可以询问用户是否开启功耗降低功能。 如果用户选择开启省电功能,移动终端可以自动开启或提示用户开启移动终端的蓝牙功能。 移动终端与电子设备建立Wi-Fi连接和蓝牙连接的过程与上述实施例相同,在此不再赘述。 [0125] 在其他一些实施例中,移动终端在开启Wi-Fi功能并与电子设备建立Wi-Fi连接后,还可以判断该电子设备是否为预设设备。 预设设备是能够支持本申请实施例提供的方法,能够与移动终端建立Wi-Fi连接和蓝牙连接的设备。 如果移动终端确定电子设备为预设设备,则移动终端自动开启省电功能,自动开启蓝牙功能,并与电子设备建立蓝牙连接。 [0126] 在其他一些实施例中,在同时开启Wi-Fi功能和蓝牙功能后,移动终端还可以自动开启功耗降低功能,或者询问用户是否开启功耗降低功能。 移动终端与电子设备建立Wi-Fi连接和蓝牙连接的过程参见上述实施例。 细节不在此描述。 [0127]需要说明的是,在一些示例中,移动终端与电子设备建立Wi-Fi连接和蓝牙连接后,移动终端首先通过Wi-Fi连接向电子设备发送数据包,然后 电子设备将接收到的数据包发送给服务器。 或者,电子设备从服务器接收到要发送给移动终端的数据包,然后电子设备通过Wi-Fi连接将数据包发送给移动终端。 换言之,移动终端通过电子设备与服务器进行通信。 移动终端通过Wi-Fi连接与电子设备进行通信。 在这个过程中,由于一段时间内没有数据包传输,蓝牙连接可能会自动断开。 移动终端的蓝牙模块也可以处于休眠状态。 在一些其他示例中,当移动终端通过使用Wi-Fi连接发送数据包时,移动终端可以替代地保持与电子设备的蓝牙连接。 在其他一些示例中,移动终端与电子设备建立Wi-Fi连接后,移动终端和电子设备均开启蓝牙功能,但此时不建立蓝牙连接。 然而,应当注意,移动终端和电子设备之间已经预先建立了连接。 也就是说,在这种情况下,移动终端和电子设备都存储了彼此的蓝牙地址等信息,以便移动终端和电子设备能够快速建立连接并随后发送数据包。 [0128] 小号 402 :移动终端在确定第一时间段内没有数据包发送时,控制Wi-Fi模块进入休眠状态。 [0129] Wi-Fi模块进入休眠状态也可以理解为Wi-Fi模块处于低功耗工作模式。 在低功耗工作模式下,暂停Wi-Fi模块的大部分功能,以降低整个Wi-Fi模块的功耗。 例如,Wi-Fi模块进入睡眠状态包括Wi-Fi模块处于睡眠模式或深度睡眠模式。 在休眠模式下,移动终端的系统运行时钟保持不变,Wi-Fi模块可以通过串口或网络数据包唤醒,GPIO(通用输入输出)端口保持输出。 深度睡眠模式下,移动终端系统运行时钟减半,Wi-Fi模块可通过串口或网络数据包唤醒,GPIO口保持输出,唤醒响应时间 略长于睡眠模式。 [0130] 当移动终端在第一时间段内既没有向电子设备发送数据包也没有接收到电子设备的数据包时,移动终端可以控制移动终端的Wi-Fi模块进入休眠状态,以降低电量 Wi-Fi 模块的消耗。 在一个示例中,当移动终端在第一时间段内不需要发送或接收任何数据包时,即当移动终端不需要发送或接收随后的第二个数据包时(例如,与 移动终端上的各个应用的服务)和后面的第一个报文(例如,应用的心跳报文或用于建立传输层链路的报文),移动终端可以控制移动终端的Wi-Fi模块 进入睡眠状态。 又如,当移动终端在第一时间段内不需要发送或接收后续的第二报文(例如,与移动终端上各个应用的业务相关的报文)时,移动终端可以控制Wi -移动终端的Fi模块进入休眠状态。 也就是说,当移动终端在第一时间内只需要发送第一包时,移动终端也可以控制移动终端的Wi-Fi模块进入休眠状态,唤醒蓝牙模块,发送 第一个数据包通过使用蓝牙模块。 [0131]例如,当移动终端处于亮屏状态时,移动终端上的应用程序不会通过电子设备向服务器请求数据包,服务器也不会通过电子设备向移动终端发送数据包。 . 在这种情况下,在第一时间段之后,移动终端可以断开与电子设备的Wi-Fi连接,并控制移动终端的Wi-Fi模块进入休眠状态。 [0132] 又例如,当移动终端在特定时间段内没有接收到用户的操作,并且移动终端没有运行视频应用等应用时,移动终端关闭屏幕并进入屏幕关闭 状态。 当移动终端处于熄屏状态且移动终端未运行音频相关应用时,经过第一时间段后,移动终端可以断开与电子设备的Wi-Fi连接,并控制Wi-Fi 移动终端的Fi模块进入休眠状态。 [0133] 小号 403 :当Wi-Fi模块处于休眠状态时,如果移动终端确定需要发送第一包,则移动终端唤醒蓝牙模块并以蓝牙连接的方式向电子设备发送第一包, 然后电子装置将第一封包传送至伺服器。 第一报文是移动终端上的应用程序的心跳报文,或者是用于建立传输层链路的报文。 心跳包是移动终端上的应用程序与该应用程序对应的服务器之间交互的心跳包,可以包括移动终端向服务器发送的心跳请求,以及服务器向移动终端返回的心跳响应。 . [0134] 如上所述,在步骤 S 403 ,移动终端与电子设备之间已建立蓝牙连接(例如BLE连接)。 移动终端和电子设备分别存储彼此的蓝牙地址等信息。 在确定需要发送第一包后,移动终端可以唤醒蓝牙模块,与电子设备建立蓝牙连接。 接着,通过蓝牙连接将第一封包发送至电子装置,以使电子装置进一步将第一封包发送至服务器。 或者,移动终端与电子设备始终保持蓝牙连接,此时可以直接通过蓝牙连接传输第一数据包。 [0135] 需要注意的是,移动终端维护与电子设备的Wi-Fi连接和蓝牙连接的信息。 具体的,移动终端可以保证在发送第一数据包时,移动终端可以自动连接到电子设备对应的蓝牙连接,将第一数据包发送给电子设备,避免连接到其他电子设备发送数据包。 将第一封包传送至另一电子装置,确保封包传输安全。 [0136] 在本申请的一些实施例中,第一报文为需要在移动终端与电子设备之间传输的心跳报文。 当移动终端处于休眠状态时,移动终端上运行的各个应用程序仍需要周期性地向该应用程序对应的服务器发送心跳包,以通知服务器该应用程序在线。 现有技术中,当移动终端上运行的应用程序需要向服务器发送心跳包时,移动终端唤醒Wi-Fi模块,与电子设备建立Wi-Fi连接,发送心跳包 通过使用 Wi-Fi 连接。 当移动终端上运行的应用较多时,发送心跳包的场合也较多。 因此,唤醒Wi-Fi模块的场合也更多。 也就是说,Wi-Fi模块处于工作状态的时间较长,功耗较高。 [0137]但是,在本申请实施例中,当确定移动终端的应用需要发送心跳包时,移动终端可以不唤醒Wi-Fi模块,而是唤醒功耗更低的蓝牙模块(相比 Wi-Fi 模块),并通过蓝牙连接发送心跳包。 因此,可以降低移动终端的整体功耗。 [0138] 在本申请的其他一些实施例中,移动终端也可以选择收集各个应用程序需要发送的心跳包,并在特定的时间段内集中发送心跳包。 当心跳包以集中方式发送时,蓝牙模块被唤醒,心跳包通过蓝牙连接发送至电子设备。 然后,电子装置将心跳封包发送至应用程序对应的服务器。 [0139] 在本申请的一些其他实施例中,第一报文也可以是用于建立传输的报文(如设备ID、设备IP地址、端口号和所使用协议的信息、TCP链路建立报文等)。 层链接由移动终端。 在某些场景下,移动终端可以通过蓝牙链路传输用于建立传输层链路的报文。 需要说明的是,这种情况下,蓝牙链路只建立了物理层链路,没有建立传输层链路。 例如,移动终端与电子设备之间的控制报文(如用于广播移动终端地址的报文)可以携带传输层链路的报文。 换言之,可以预先建立传输层链路。 例如,可以周期性地建立传输层链路。 随后,当移动终端需要建立蓝牙链路或Wi-Fi链路时,在建立相应的物理层链路后,移动终端可以直接使用预先建立的传输层链路。 由于预先建立了传输层链路,移动终端唤醒Wi-Fi模块或蓝牙模块后,可以快速启动数据包传输,从而提高Wi-Fi模块或蓝牙模块的工作效率,帮助 降低Wi-Fi模块或蓝牙模块的功耗。 因此,降低了移动终端的整体功耗。 [0140] 需要说明的是,在一些示例中,移动终端唤醒蓝牙模块发送第一包后,如果一段时间内没有发送第一包,则移动终端控制蓝牙模块断开蓝牙连接, 电子设备进入休眠状态,以降低功耗。 或者,在一些场景中,在一段时间内以集中的方式周期性地发送第一包。 例如,多个应用的​​心跳包在一段时间内以集中的方式周期性发送。 在这种情况下,移动终端在确定一个周期内的第一个数据包都发送完毕后,可以直接控制蓝牙模块断开与电子设备的蓝牙连接,进入休眠状态,等待下一个周期。 换言之,移动终端在发送一个周期的第一个数据包后,不需要等待一段时间来断开与电子设备的蓝牙连接。 这有助于进一步降低蓝牙模块的功耗。 在其他一些示例中,在移动终端唤醒蓝牙模块发送第一数据包后,移动终端可以不断开连接。 换言之,移动终端与电子设备长期保持蓝牙连接。 [0141] 小号 404:如果移动终端确定需要发送第二个数据包,则移动终端唤醒Wi-Fi模块,以Wi-Fi连接的方式将第二个数据包发送给电子设备,然后电子设备再发送第二个数据包。 数据包到服务器。 或者,当确定服务器向电子设备下发要发送给移动终端的第二数据包时,电子设备恢复与移动终端的Wi-Fi连接。 该场景下,移动终端唤醒Wi-Fi模块,并以Wi-Fi连接方式接收电子设备发送的第二报文。 [0142] 第二报文是与第一报文不同的另一个需要移动终端发送的报文,可以包括与移动终端上的各个应用的业务相关的报文(例如业务数据)。 [0143] 在本申请的一些实施例中,当移动终端确定需要发送第二个数据包时,如果移动终端仍然保持与电子设备的蓝牙连接,则移动终端可以主动断开蓝牙连接,建立Wi-Fi连接 ,并以Wi-Fi连接方式发送第二个数据包。 在一些示例中,如果此时移动终端仍需要向电子设备发送第一数据包,则移动终端也可以通过Wi-Fi连接的方式发送第一数据包,然后再发送第二数据包。 在其他一些示例中,如果移动终端确定第一报文是具有低延迟要求的报文或者是不重要的报文(例如,用于建立物理层链路的报文),则移动终端可以首先发送 Wi-Fi连接方式的第二个数据包,然后发送第一个数据包或直接丢弃第一个数据包。 [0144] 在本申请的一些其他实施例中,当移动终端与电子设备保持Wi-Fi连接时,如果移动终端检测到移动终端需要发送第一包,则移动终端可以直接通过Wi-Fi进行传输。 -Fi 连接。 [0145] 下面结合具体场景举例说明本申请实施例提供的方法。 [0146] 场景一:移动终端(如手机、平板电脑、智能音箱)与无线路由器建立Wi-Fi连接,通过无线路由器接入网络。 开启移动终端和无线路由器的蓝牙功能,移动终端和无线路由器之间已经建立了蓝牙连接。 [0147] 举例来说,如果移动终端在第一时间段内没有发送任何数据包(包括心跳包),则移动终端断开与无线路由器的Wi-Fi连接,并控制手机中配置的Wi-Fi模块。 终端进入休眠状态。 又例如,如果移动终端在第一时间段内不需要发送除心跳包以外的包(即第二包),则移动终端断开与无线路由器的Wi-Fi连接,并控制无线路由器的Wi-Fi连接。 移动终端中配置的Wi-Fi模块进入休眠状态。 当移动终端在第一时间段只需要发送心跳包时,移动终端也可以唤醒蓝牙模块,以蓝牙连接的方式发送心跳包。 [0148]当移动终端配置的Wi-Fi模块处于休眠状态时,如果移动终端检测到移动终端上运行的应用需要发送心跳包(无其他包),移动终端唤醒蓝牙模块 在移动终端中配置,与电子设备建立蓝牙连接(例如BLE),并通过蓝牙连接发送心跳包。 移动终端唤醒蓝牙模块后与电子设备建立蓝牙连接的过程可参见本领域相关技术,在此不再赘述。 在一些示例中,在发送心跳包后,如果移动终端在第二时间段内没有发送包,则移动终端断开与无线路由器的蓝牙连接,并控制移动终端中配置的蓝牙模块进入 睡眠状态。 [0149] 如果移动终端上的应用需要发送一个包(非心跳包,例如应用的业务相关包),移动终端唤醒移动终端的Wi-Fi模块,建立一个Wi - 与电子设备的 Fi 连接,并使用 Wi-Fi 连接发送数据包。 移动终端在唤醒Wi-Fi模块后与电子设备建立Wi-Fi连接的过程可参见本领域相关技术,在此不再赘述。 [0150] 如果无线路由器需要向移动终端发送来自服务器的数据包(非心跳数据包),则无线路由器与移动终端建立Wi-Fi连接,并通过 无线网络连接。 无线路由器与电子设备建立Wi-Fi连接的过程可参见本领域相关技术,在此不再赘述。 [0151] 场景二:移动终端(如手机、平板电脑、智能音箱等)与随行Wi-Fi设备建立Wi-Fi连接,通过随行Wi-Fi设备接入网络。 移动终端与随附的Wi-Fi设备的蓝牙功能开启,且移动终端与随附的Wi-Fi设备之间已预先建立了蓝牙连接。 [0152] 与场景一不同的是,随行Wi-Fi设备也是移动终端,配置有Wi-Fi模块,Wi-Fi模块的功耗是随行Wi-Fi设备的一种主要功耗。 随行Wi-Fi设备还配置有移动通信模块,该移动通信模块可用于提供应用于随行Wi-Fi设备的无线通信方案,包括2G/3G/4G/5G等。 也就是说,移动终端通过Wi-Fi连接与随身Wi-Fi设备进行交互,通过随身Wi-Fi设备的移动通信模块接入移动通信网络,实现网络接入功能。 [0153] 如果移动终端与随行Wi-Fi设备连接,则在确定与移动终端没有数据包传输时,随行Wi-Fi设备也可以控制随行Wi-Fi设备的Wi-Fi模块进入 睡眠状态。 随后,当随行Wi-Fi设备接收到网络侧下发的数据包,需要将该数据包发送给移动终端时,随行Wi-Fi设备唤醒Wi-Fi模块,并建立Wi-Fi连接到移动终端。 移动终端,传输网络侧下发的报文。 [0154] 以附带的Wi-Fi设备连接一个移动终端为例进行说明。 图5A和图5B为本申请实施例提供的另一种降低移动终端功耗的方法的流程示意图。 详情如下: [0155] 首先参见图5A,从随附的Wi-Fi设备一侧,降低移动终端功耗的方法包括步骤S 500 到步骤 S 505 , 如下: [0156] 小号 500. 打开随附的 Wi-Fi 设备。 [0157] 小号 501 . 随附的 Wi-Fi 设备确定是否存在与其他移动终端的 Wi-Fi 连接。 如果随行Wi-Fi设备判断一段时间内没有Wi-Fi连接,则随行Wi-Fi设备执行步骤S 502 . 如果随行Wi-Fi设备确定有Wi-Fi连接,则随行Wi-Fi设备执行步骤S 503 . [0158] 小号 502 . 随附的 Wi-Fi 设备控制 Wi-Fi 模块进入睡眠状态。 [0159] Wi-Fi 模块进入休眠状态,有助于降低随附 Wi-Fi 设备的功耗。 然后,随行的Wi-Fi设备继续监测是否有Wi-Fi连接,即执行步骤S 501 . [0160] 小号 503 . 附带的Wi-Fi设备判断是否需要在第一时间段传输数据(非心跳包)。 如果需要传输数据,则随附的 Wi-Fi 设备执行步骤 S 504 . 如果不需要传输数据,则随附的 Wi-Fi 设备执行步骤 S 505 . [0161] 例如,随行Wi-Fi设备具体判断随行Wi-Fi设备是否在第一时间段内从网络侧设备接收到需要发送给移动终端的数据,或者随行Wi-Fi设备是否 从移动终端接收需要发送到网络侧的数据。 [0162] 小号 504 . 随附的 Wi-Fi 设备通过使用 Wi-Fi 连接将数据传输到移动终端。 [0163] 然后,伴随的Wi-Fi设备继续监测是否需要传输数据,即执行步骤S 503 . [0164] 小号 505 . 随附的Wi-Fi设备控制Wi-Fi模块进入休眠状态,通过蓝牙连接向移动终端发送心跳包。 [0165] 当确定需要发送心跳包时,随行的Wi-Fi设备唤醒蓝牙模块(如果蓝牙模块不处于休眠状态则不需要唤醒),并通过蓝牙连接发送心跳包( 例如,一个 BLE 连接)在随附的 Wi-Fi 设备和移动终端之间。 然后,伴随的Wi-Fi设备继续监测是否需要传输数据,即执行步骤S 503 . 需要注意的是,在步骤 S 之后 503 ,如果随附的Wi-Fi设备确定需要传输数据,则在步骤S之前 504 ,如果Wi-Fi模块处于休眠状态,则伴随的Wi-Fi设备首先唤醒Wi-Fi模块,然后通过Wi-Fi模块传输数据。 [0166] 参见图5B,从移动终端一侧,降低移动终端功耗的方法包括步骤S 506 到步骤 S 511 , 如下: [0167] 小号 506 . 移动终端处于屏幕关闭状态。 [0168] 如果移动终端不处于熄屏状态,则移动终端处于数据传输场景或者不处于低功耗场景的概率较大。 因此,此处以移动终端处于屏幕关闭状态为例进行说明。 [0169] 小号 507 . 移动终端在第一时间段内判断是否需要传输数据(非心跳包)。 如果需要传输数据,移动终端执行步骤S 508 . 如果不需要传输数据,移动终端执行步骤S 509 . [0170] 例如,移动终端判断移动终端是否有数据需要发送给随附的Wi-Fi设备。 [0171] 小号 508 . 移动终端通过Wi-Fi模块提供的Wi-Fi连接将数据传输到随附的Wi-Fi设备。 [0172] 然后,移动终端继续监听是否需要传输数据,即执行步骤S 507 . [0173] 小号 509. 移动终端控制Wi-Fi模块进入休眠状态。 [0174] 小号 510 . 移动终端判断是否需要发送心跳包。 如果需要发送心跳包,移动终端执行步骤S 511 . 如果不需要发送心跳包,移动终端执行步骤S 507 . [0175] 小号 511 . 移动终端通过蓝牙连接向随附的Wi-Fi设备发送心跳包。 [0176] 移动终端可以唤醒蓝牙模块(如果蓝牙模块不处于休眠状态则不需要唤醒),并通过蓝牙连接(例如BLE连接)将心跳包传输到随附的Wi-Fi 设备。 然后,移动终端执行步骤S 507 . 需要注意的是,在步骤 S 之后 507 ,如果移动终端确定需要传输数据,则在步骤S之前 508 ,如果Wi-Fi模块处于休眠状态,移动终端首先唤醒Wi-Fi模块,然后通过Wi-Fi模块传输数据。 [0177] 在本申请实施例中,当随行Wi-Fi设备与移动终端之间只需要传输心跳包时,随行Wi-Fi设备与移动终端通过蓝牙连接传输心跳包。 功耗更低的蓝牙模块(与 Wi-Fi 模块相比)。 整体降低了随行Wi-Fi设备和移动终端分别唤醒各自Wi-Fi模块的概率,降低了任一Wi-Fi模块的工作时间,降低了随行Wi-Fi设备的功耗 降低了移动终端的功耗。 [0178] 也就是说,在这种场景下,除了移动终端的功耗之外,还可以降低随行Wi-Fi设备的功耗,延长随行Wi-Fi设备的待机时间。 [0179] 如果N个移动终端连接到随行Wi-Fi设备,当确定与所有N个移动终端都连接到随行Wi-Fi设备没有数据包传输时,随行Wi-Fi设备控制的Wi-Fi模块 伴随的 Wi-Fi 设备进入睡眠状态。 随后,当确定N个移动终端中的任意一个或多个移动终端只需要发送一个心跳包时,随行的Wi-Fi设备分别与一个或多个移动终端建立蓝牙连接,以发送每个移动终端之间交换的心跳包。 终端和网络侧。 当确定N个移动终端中的任意一个或多个需要传输数据(非心跳包)时,随行的Wi-Fi设备唤醒Wi-Fi模块,分别与其中一个或多个建立Wi-Fi连接。 更多的移动终端来传输数据。 [0180] 如果N个移动终端中的M个移动终端(M大于等于1且小于N)的Wi-Fi模块进入休眠状态,则伴随的Wi-Fi设备单独建立蓝牙连接(即M个蓝牙连接) 发送给M个移动终端,并通过M个蓝牙连接分别传输各个移动终端与网络侧交换的心跳包。 需要说明的是,随附的Wi-Fi设备仍然使用Wi-Fi连接来传输其他(N-M)个移动终端与网络侧之间交换的数据包。 [0181] 本场景的其他内容请参见场景一的描述及前述相关内容。 细节不在此描述。 [0182] 场景三:移动终端(如手机、平板电脑、智能音箱)通过其他移动终端(如手机、平板电脑、智能音箱)提供的热点接入网络 扬声器)。 开启两个移动终端的蓝牙功能,并且两个移动终端之间已经建立了蓝牙连接。 [0183] 该场景的详细介绍请参考其他场景中相关内容的描述。 [0184]本申请实施例还提供了一种芯片系统。 如图6所示,该芯片系统包括至少一个处理器 1101 和至少一个接口电路 1102 . 处理器 1101 和接口电路 1102 可以通过一条线相互连接。 比如接口电路 1102 可以被配置为从另一个设备(例如,移动终端的存储器)接收信号 100 )。 再比如接口电路 1102 可以配置为将信号发送到另一个设备(例如,处理器 1101 )。 比如接口电路 1102 可以读取存储在内存中的指令,并将指令发送到处理器 1101 . 当处理器执行指令时 1101 ,移动终端可以执行移动终端执行的步骤 100 (例如,移动电话)在前述实施例中。 当然,芯片系统还可以包括其他分立器件。 本申请实施例对此不作具体限定。 [0185] 本申请实施例还提供了一种装置。 该装置包括在移动终端或电子设备中,具有实现上述实施例中任一方法的移动终端或电子设备的行为的功能。 该功能可以通过硬件来实现,也可以通过硬件执行相应的软件来实现。 硬件或软件包括与上述功能对应的至少一个模块或单元,例如检测模块或单元,或者确定模块或单元。 [0186] 本申请实施例还提供了一种计算机可读存储介质,包括计算机指令。 当计算机指令在移动终端或电子设备上运行时,移动终端或电子设备执行上述实施例中的任一方法。 [0187] 本申请实施例还提供了一种计算机程序产品。 当计算机程序产品在计算机上运行时,计算机执行上述实施例中的任何方法。 [0188] 可以理解,为了实现上述功能,终端包括相应的硬件结构和/或软件模块,用于执行各个功能。 本领域普通技术人员应该容易意识到,结合本说明书中所公开的实施例中描述的示例的单元和算法步骤,本申请实施例可以通过硬件或者硬件与计算机的结合来实现。 软件。 功能是由硬件执行还是由计算机软件驱动的硬件取决于具体的应用和技术方案的设计约束。 本领域技术人员可以针对每个特定的应用使用不同的方法来实现所描述的功能,但不应认为其实现超出了本发明实施例的范围。 [0189] 在本申请实施例中,可以基于上述方法示例对终端等进行功能模块划分。 例如,可以根据对应的功能划分得到每个功能模块,或者可以将两个或多个功能集成到一个处理模块中。 集成模块可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。 需要说明的是,在本发明实施例中,模块划分只是一个例子,只是逻辑上的功能划分。 在实际实现中,还可以采用另一种划分方式。 [0190]上述实施方式的描述使本领域技术人员可以清楚地了解到,为了描述的方便和简洁,以对上述功能模块的划分为例进行说明。 在实际应用中,上述功能可以根据需要分配到不同的模块中实现。 换言之,将装置的内部结构划分为不同的功能模块来实现上述全部或部分功能。 上述系统、装置和单元的详细工作过程参见上述方法实施例中的对应过程,在此不再赘述。 [0191] 本申请实施例中的功能单元可以集成在一个处理单元中,也可以每个单元在物理上单独存在,或者两个或多个单元集成在一个单元中。 集成单元可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。 [0192] 当集成单元以软件功能单元的形式实现并作为独立产品销售或使用时,集成单元可以存储在计算机可读存储介质中。 基于这样的理解,本申请实施例的技术方案本质上,或者对现有技术有贡献的部分,或者全部或者部分技术方案,可以以软件产品的形式来实现。 计算机软件产品存储在存储介质中,包括若干指令,用于指示计算机设备(可以是个人计算机、服务器或网络设备)执行实施例中描述的方法的全部或部分步骤 这个应用程序的。 上述存储介质包括:闪存、移动硬盘、只读存储器、随机存取存储器、磁盘、光盘等任何可以存储程序代码的介质。 [0193] 以上所述仅为本申请的具体实施方式,并非用于限定本申请的保护范围。 在本申请所公开的技术范围内的任何变更或替换,均应包含在本申请的保护范围之内。 因此,本申请的保护范围应以权利要求的保护范围为准。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN113133095A(String), CN113133095B(String), EP3923617A1(String), EP3923617A4(String), JP2023510259A(String), US20220353819A1(String), WO2021143314A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN113133095A(String), CN113133095B(String), EP3923617A1(String), EP3923617A4(String), JP2023510259A(String), US20220353819A1(String), WO2021143314A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20220353819A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN113133095A(String), CN113133095B(String), EP3923617A1(String), EP3923617A4(String), JP2023510259A(String), US20220353819A1(String), WO2021143314A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), CN113133095A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), CN113133095B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), EP3923617A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), EP3923617A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), JP2023510259A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), US20220353819A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.420 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270655(Integer), WO2021143314A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20220353819A1(String), US20220353819A1(String), 1667404800(Integer), 270655(Integer), 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184972(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184972(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184972(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184972(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 实质审查(String), 1(Integer), 184972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10419919B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 移动终端的网络注册方法、存储介质及移动终端(String), US10419919B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端和存储介质。 移动终端的网络注册方法实现如下。 元素T i 响应于确定在移动终端注册第一网络时发生预定异常事件而读取时间数组中的。 i为1至N之间的正整数,N为正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时,得到第一计时时间。 判断第一次计数时间是否达到T i . 如果第一个计数时间达到T,则获得第一个身份 i . 第一标识为第一网络注册时注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/072025(String), 1497283200(Integer), US10419919B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184973(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b596be0e438d48d9b2ce105effb1bf2f.png(String), 184973(Integer), b596be0e438d48d9b2ce105effb1bf2f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 移动终端的网络注册方法、存储介质及移动终端(String), US10419919B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端和存储介质。 移动终端的网络注册方法实现如下。 元素T i 响应于确定在移动终端注册第一网络时发生预定异常事件而读取时间数组中的。 i为1至N之间的正整数,N为正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时,得到第一计时时间。 判断第一次计数时间是否达到T i . 如果第一个计数时间达到T,则获得第一个身份 i . 第一标识为第一网络注册时注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/072025(String), 1497283200(Integer), US10419919B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), \20230420\b596be0e438d48d9b2ce105effb1bf2f.png(String), 20(Integer), 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 1. A network registration method of a mobile terminal, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity.(String), 1.根据权利要求9所述的移动终端,其中处理器还被配置为:当第一次计时时间未达到T时,继续控制移动终端注册第二网络i.12.根据权利要求9所述的移动终端,其中预定异常事件包括跟踪区域更新(TAU)被拒绝。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 2. The method according to claim 1, wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity.(String), 13.根据权利要求9所述的移动终端,其中处理器还被配置为:获取TAU被拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 3. The method according to claim 2, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 14.根据权利要求9所述的移动终端,其中处理器还被配置为:设置元素T的值i根据用户命令在时间数组中。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 4. The method according to claim 2, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 15.一种非暂时性计算机可读存储介质,有其中存储有当移动终端的处理器执行时使移动终端执行网络注册方法的指令,包括:读取时间数组{T1,T2,...,Ti,Ti+1,...,Tn}响应于确定移动终端注册第一网络时发生预定异常事件,其中i介于1和N之间,N为正整数;禁止移动终端注册第一网络,控制移动终端注册第二网络;启动定时器进行计时,得到第一计时时间;判断第一次计时时间是否达到Ti;在第一计数时间达到Ti时获取第一标识,其中,第一标识为移动终端在注册第一网络时注册的小区的相邻小区的跟踪区标识;和控制移动终端根据第一标识重新注册第一网络。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 5. The method according to claim 1, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 16.根据权利要求15所述的非暂时性计算机可读存储介质,其中在根据第一标识控制移动终端重新注册第一网络之后,该方法还包括:判断移动终端重新注册第一网络时是否发生预定异常事件;当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间;判断第二次计时是否达到Ti+1;第二次计时时间达到T时获得第二身份i+1,其中,第二标识为移动终端在重新注册第一网络时注册的小区的相邻小区的跟踪区标识;和控制移动终端根据第二标识重新注册第一网络。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 6. The method according to claim 1, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 17.根据权利要求15所述的非暂时性计算机可读存储介质,其中在判断第一次计数时间是否达到T后i,该方法还包括:当第一次计时时间未达到T时,继续控制移动终端注册第二网络i.18.根据权利要求15所述的非暂时性计算机可读存储介质,其中预定异常事件包括跟踪区域更新(TAU)被拒绝。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 7. The method according to claim 1, further comprising:obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 19.根据权利要求15所述的非暂时性计算机可读存储介质,还包括:获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 8. The method according to claim 1, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 20.根据权利要求15所述的非暂时性计算机可读存储介质,还包括:设置元素T的值i根据用户命令在时间数组中。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 9. A mobile terminal, comprising:a housing;a processor;a memory; anda circuit board and a power supply circuit,wherein, the circuit board is disposed inside a space enclosed by the housing; the processor and the memory are disposed on the circuit board; the power supply circuit is configured to supply power for respective circuits or components of the mobile terminal; the memory is configured to store executable program codes; and the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform:reading an element Ti, in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 10. The mobile terminal according to claim 9, wherein the processor is further configured to:determine whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, control the mobile terminal to re-register the second network, and reset the timer for timing again to obtain a second counted time;determine whether the second counted time reaches Ti+1;obtain a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when re-registering the first network; andcontrol the mobile terminal to re-register the first network according to the second identity.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 11. The mobile terminal according to claim 9, wherein the processor is further configured to:continue to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 12. The mobile terminal according to claim 9, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 13. The mobile terminal according to claim 9, wherein the processor is further configured to:obtain information about TAU being rejected, and send the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 14. The mobile terminal according to claim 9, wherein the processor is further configured to:set a value of the element Ti in the time array according to a user command.(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 15. A non-transitory computer-readable storage medium, having stored therein instructions that, when executed by a processor of a mobile terminal, cause the mobile terminal to execute a network registration method, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is between 1 and N, and N is a positive integer;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity.(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 16. The non-transitory computer-readable storage medium according to claim 15, wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity.(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 17. The non-transitory computer-readable storage medium according to claim 15, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 18. The non-transitory computer-readable storage medium according to claim 15, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 19. The non-transitory computer-readable storage medium according to claim 15, further comprising:obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 1(Integer), 18(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184973(Integer), 20. The non-transitory computer-readable storage medium according to claim 15, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 19(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184973(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a National phase application of International Application No. PCT/CN2017/088117 filed on Jun. 13, 2017, which claims priority to Chinese Patent Application No. 201610460475.8 filed on Jun. 21, 2016 and titled with “NETWORK REGISTRATION METHOD AND APPARATUS FOR MOBILE TERMINAL, AND MOBILE TERMINAL”, the entire contents of which are incorporated herein by reference. FIELD [0002]The present disclosure relates to the communication technology field, and more particularly, to a network registration method of a mobile terminal, a storage medium and a mobile terminal. BACKGROUND [0003]With continuous development of communication technologies, most areas of the country have been covered by 4G network, and users can quickly access to Internet by connecting the mobile terminals to the 4G network. In the related art, when the mobile terminal receives a response indicating that TAU (Tracking Area Update) is rejected, the mobile terminal stops registering the 4G network and does not search for networks of cells with different TAI (Tracking Area Identity). [0004]In this way, when the current TAU is rejected by the network, a success rate of registering the network by the mobile terminal is low. SUMMARY [0005]The present disclosure aims to solve at least one of the problems existing in the related art to some extent at least. [0006]Embodiments of the present disclosure provide a network registration method of a mobile terminal. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. [0007]Embodiments of the present disclosure provide a mobile terminal. The mobile terminal includes a housing, a processor, a memory, a circuit board and a power supply circuit. The circuit board is disposed inside a space enclosed by the housing. The processor and the memory are disposed on the circuit board. The power supply circuit is configured to supply power for respective circuits or components of the mobile terminal. The memory is configured to store executable program codes. The processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform: reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. [0008]Embodiments of the present disclosure provide a non-transitory storage medium. When instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform a network registration method. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. [0009]It is to be understood that, both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to explain technical solutions of the present disclosure more clearly, drawings required to be used in the description of embodiments will now be illustrated briefly. Obviously, drawings in the following description are some embodiments of the present disclosure, and further drawings can be obtained by those skilled in the art based on these drawings, without creative labor. [0011]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0013]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0014]FIG. 4 is a block diagram of a network registration apparatus of a mobile terminal according to an embodiment of the present disclosure. [0015]FIG. 5 is a block diagram of a network registration apparatus of a mobile terminal according to another embodiment of the present disclosure. DETAILED DESCRIPTION [0016]Technical solutions in embodiments of the present disclosure will be described clearly and completely in the following with reference to drawings in embodiments of the present disclosure. Obviously, the embodiments described are merely illustrative, and are not exhaustive. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without creative labor belong to the protection scope of the present disclosure. [0017]Terms such as “first”, “second”, “third” and “four” in the description, claims and drawings of the present disclosure are used to distinguish different objects, and are not used to describe specific order. In addition, terms such as “including” and “having” and their variants intend to cover non-exclusive inclusion. For example, procedures, methods, systems, products or apparatus including a series of steps or units are not limited to listed steps or units, but alternatively further include steps or units which are not listed, or alternatively further include other steps or units inherent to these procedures, methods, products and apparatus. [0018]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in a network registration apparatus of a mobile terminal for illustration. Embodiments of the present disclosure may be applied in a procedure when the user uses the mobile terminal to register 4G network, or may be applied in a procedure of registering 3G network or 2G network, which are not limited. The mobile terminal may be hardware devices with various operating systems, such as a smart phone, a tablet PC, a PDA, and an E-book. [0019]The network registration method of the mobile terminal can include following actions in blocks illustrated in FIG. 1. The method can begin at block S11. [0020]At block S11, an element Ti in a time array is read in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, in which the time array is {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, i is a positive integer between 1 and N, and N is a positive integer. [0021]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0022]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0023]Alternatively, the predetermined abnormal event includes TAU being rejected. [0024]The first network is 4G network. [0025]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0026]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the network with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0027]A value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0028]At S12, the mobile terminal is prohibited from registering the first network, and is controlled to register a second network. [0029]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0030]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti, thus effectively ensuring that the mobile terminal can normally access to Internet. [0031]At S13, the timer is started to time, to obtain a first counted time. [0032]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0033]At S14, it is determined whether the first counted time reaches Ti. [0034]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0035]In some embodiments, as illustrated in FIG. 2, following action may be performed after S14. [0036]At S21, when the first counted time does not reach T1, the mobile terminal is continuously controlled to register the second network. [0037]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0038]At S15, when the first counted time reaches Ti, a first identity is obtained, in which the first identity is the TAI of an adjacent cell of a cell where the mobile terminal is when registering the first network. [0039]In embodiments of the present disclosure, when the first counted time reached Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0040]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0041]At S16, the mobile terminal is controlled to re-register the first network according to the first identity. [0042]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the times reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0043]In this embodiment, by controlling the mobile terminal to register the second network when the predetermined abnormal event occurs during the mobile terminal registers the first network, it can ensure that the user registers the network successfully, and by obtaining the first identity (the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network) when the first counted time reaches Ti, and controlling the mobile terminal to re-register the first network according to the first identity, the mobile terminal can register the network of the cell with different TAI when the current TAU is rejected by the network, thus effectively enhancing the success rate of registering the network. [0044]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in the network registration apparatus of the mobile terminal for illustration. [0045]The network registration method of the mobile terminal includes following actions in blocks illustrated in FIG. 3. The method can begin at block S301. [0046]At S301, the value of the element Ti in the time array is set according to a user command. [0047]In this embodiment, the value of the element Ti in the time array may be preset by the user based on this own demand. [0048]For example, the mobile terminal may receive the command input by the user on the screen, and sets the value of the element Ti in the time array according to the user command. The values of the elements Ti in the time array may be sequentially input by the user on the screen, or may be selectively input by the user, which is not limited. [0049]In this action, the time Ti of the time array is set by the user, and thus personalized setting of the time array may be realized, the generality of the network registration method of the mobile terminal may be improved, and the success rate of the network registration of the mobile terminal may be enhanced. [0050]At S302, it is determined whether the predetermined abnormal event occurs when the mobile terminal registers the first network, and if yes, S303 is executed, and if no, S315 is executed. [0051]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0052]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0053]Alternatively, the predetermined abnormal event includes TAU being rejected. [0054]The first network is 4G network. [0055]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. This embodiment is applied in the procedure in which the mobile terminal registers the network, and is applied after the TAU is rejected. [0056]Alternatively, it is possible to determine whether the event of the TAU being rejected by the network occurs during the mobile terminal registers the 4G network, to trigger subsequent actions. [0057]At S303, the element Ti in the time array is read, in which the time array is {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, i is a positive integer between 1 and N, and N is a positive integer. [0058]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the networks with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0059]The value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0060]At S304, the mobile terminal is prohibited from registering the first network, and is controlled to register the second network. [0061]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0062]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti, thus effectively ensuring that the mobile terminal can normally access to Internet. [0063]At S305, the timer is started to time, to obtain the first counted time. [0064]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0065]At S306, it is determined whether the first counted time reaches Ti, and if yes, S308 is executed, and if no, S307 is executed. [0066]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0067]At S307, the mobile terminal is continuously controlled to register the second network. [0068]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0069]At S308, the first identity is obtained, in which the first identity is the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network. [0070]In embodiments of the present disclosure, when the first counted time reaches Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0071]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0072]At S309, the mobile terminal is controlled to re-register the first network according to the first identity. [0073]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the timer reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0074]At S310, it is determined whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network, and if yes, S311 is executed, and if no, S315 is executed. [0075]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0076]Alternatively, it is determined whether the TAU is rejected by the network when the mobile terminal re-registers the first network, to trigger subsequent actions. [0077]At S311, the mobile terminal is controlled to re-register the second network, and the timer is reset to time again to obtain the second counted time. [0078]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T2. Alternatively, when the mobile terminal alternately reads the element Ti+1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti+1, thus effectively ensuring that the mobile terminal can normally access to Internet. [0079]While the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the second counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti+1 according to the second counted time, which is not limited. [0080]At S312, it is determined whether the second counted time reaches Ti+1. [0081]In embodiments of the present disclosure, it is possible to determine whether the second counted time reaches Ti+1, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0082]At S313, when the second counted time reaches Ti+1, the second identity is obtained, in which the second identity is the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network. [0083]In embodiments of the present disclosure, when the second counted time reaches Ti+1, the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0084]The TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0085]At S314, the mobile terminal is controlled to re-register the first network according to the second identity. [0086]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network due to the TAU being rejected, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T2, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T2. Then, when the counted time of the timer reaches T2, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T3 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T3. When the re-counted time reaches T3, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0087]At S315, information about the TAU being rejected is obtained and sent to the server, such that the server backs up the predetermined abnormal event according to the information. [0088]Alternatively, the mobile terminal obtains the information about the TAU being rejected by the network, and sends the information to the server, such that the server backs up the predetermined abnormal event according to the information. [0089]In this embodiment, the time Ti of the time array is set by the user, and thus personalized setting of the time array can be realized, and generality of the network registration method of the mobile terminal can be improved. By controlling the mobile terminal to register the second network when the predetermined abnormal event occurs during the mobile terminal registers the first network, it can ensure that the user registers the network successfully, and by obtaining the first identity (the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network) when the first counted time reaches Ti, obtaining the second identity (the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network) when the second counted time reaches Ti+1, and controlling the mobile terminal to re-register the first network according to the first identity or the second identity, the mobile terminal can register the network of the cell with different TAI when the current TAU is rejected by the network, thus effectively enhancing the success rate of registering the network. [0090]In order to illustrate the actions of the above embodiments more clearly, an example is given as follows. [0091]As an example, when the time array is {1 min, 6 min, 12 min}, it indicates that the mobile terminal reads the element 1 min in the time array {1 min, 6 min, 12 min} when the mobile terminal fails to register the 4G network the first time due to the TAU being rejected. In the time interval of 1 min, the mobile terminal is prohibited from registering the first network, and switches to register the 2G or 3G network. The mobile terminal accesses to the 2G or 3G network in the time interval of 1 min. then, when the counted time of the timer reaches 1 min, the mobile terminal is controlled to re-register the 4G network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the 4G network. If the registration fails, the mobile terminal reads the element 6 min in the time array {1 min, 6 min, 12 min}, and re-starts the timer for timing. In the time interval of 6 min, the mobile terminal switches to register the 2G or 3G network again. When the re-counted time reaches 6 min, the mobile terminal is controlled to register the 4G network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the 4G network the second time. If the registration successes, the mobile terminal accesses to the 4G network. If the registration fails, the mobile terminal reads the last element 12 min in the time array {1 min, 6 min, 12 min} and re-starts the timer for timing. In the time interval of 12 min, the mobile terminal switches to register the 2G or 3G network again. When the re-counted time reaches 12 min, the mobile terminal is controlled to register the 4G network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the 4G network the third time. By that analogy, the mobile terminal then re-searches for the 4G network every 12 min. In this way, it can ensure that the user can register the network with other rate when the TAU is rejected by the network, avoiding the connectionless network service state. [0092]FIG. 4 is a block diagram of a network registration apparatus of a mobile terminal according to an embodiment of the present disclosure. The network registration apparatus 40 of the mobile terminal may be (String), 相关申请的交叉引用 [0001] 本申请为于2017年6月13日提交的国际申请号PCT/CN2017/088117的国家阶段申请,要求于2016年6月21日提交的申请号为201610460475.8的“网络注册方法及方法”的中国专利申请的优先权。 APPARATUS FOR MOBILE TERMINAL, AND MOBILE TERMINAL”,其全部内容通过引用并入本文。 场地 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端的网络注册方法、存储介质和移动终端。 背景 [0003] 随着通信技术的不断发展,全国大部分地区已被4G网络覆盖,用户可以通过移动终端接入4G网络快速上网。 相关技术中,当移动终端接收到拒绝TAU(Tracking Area Update)响应时,移动终端停止注册4G网络,不再搜索不同TAI(Tracking Area Identity)小区的网络。 [0004] 这样,当当前TAU被网络拒绝时,移动终端注册网络的成功率较低。 概括 [0005] 本发明旨在至少在一定程度上解决相关技术中存在的问题中的至少一个。 [0006] 本发明实施例提供了一种移动终端的网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中,i为1至N之间的正整数,N为正整数; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 [0007] 本发明实施例提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器,用于通过读取内存中存储的可执行程序代码,运行与可执行程序代码对应的程序,以执行:读取元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中,i为1至N之间的正整数,N为正整数; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 [0008]本公开的实施例提供了一种非暂时性存储介质。 当移动终端的处理器执行存储在存储介质中的指令时,使移动终端执行网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中,i为1至N之间的正整数,N为正整数; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 [0009] 应当理解,前述的一般描述和以下的详细描述都只是示例性和解释性的,而不是对本公开的限制。 附图的简要说明 [0010] 为了更加清楚地说明本发明的技术方案,现对实施例描述中需要用到的附图进行简要说明。 显然,以下描述中的附图仅为本发明的一些实施例,本领域技术人员基于这些附图在没有做出创造性劳动的情况下所获得的进一步的附图。 [0011] 图1是根据本发明实施例的移动终端的网络注册方法的流程图。 [0012] 图2是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0013] 图3是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0014] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 [0015] 图5是根据本发明另一实施例的移动终端的网络注册装置的框图。 详细说明 [0016] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 显然,所描述的实施例仅仅是示例性的,而不是穷举性的。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0017] 本发明的说明书、权利要求书和附图中的“第一”、“第二”、“第三”、“四”等术语用于区分不同的对象,不用于描述具体顺序。 此外,诸如“包括”和“具有”及其变体等术语旨在涵盖非排他性包含。 例如,包括一系列步骤或单元的程序、方法、系统、产品或装置不限于列出的步骤或单元,而是还包括未列出的步骤或单元,或者还包括其他固有的步骤或单元 这些程序、方法、产品和设备。 [0018]图1是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 本发明实施例可以应用在用户使用移动终端注册4G网络的过程中,也可以应用在注册3G网络或2G网络的过程中,不做限定。 移动终端可以是智能手机、平板电脑、PDA、电子书等各种操作系统的硬件设备。 [0019] 移动终端的网络注册方法可以包括图1所示的块中的以下动作。该方法可以从块S开始 11 . [0020] 在S座 11 , 元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0021] 本发明实施例以移动终端注册4G网络为例进行说明。 [0022] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0023] 或者,预定异常事件包括TAU被拒绝。 [0024] 第一个网络是4G网络。 [0025] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0026] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0027] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0028] 在小号 12 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0029] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0030] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0031] 在小号 13 ,定时器开始计时,得到第一个计时时间。 [0032] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0033] 在小号 14 , 判断第一个计数时间是否达到T i . [0034] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0035] 在一些实施例中,如图2所示,可以在S之后执行以下动作 14 . [0036] 在小号 21 , 当第一次计数时间没有达到 T 1 ,继续控制移动终端注册第二网络。 [0037] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0038] 在小号 15 , 当第一个计数时间到达 T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0039] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0040] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0041] 在小号 16 ,控制移动终端根据第一标识重新注册第一网络。 [0042] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0043]本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0044] 图3是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 [0045] 移动终端的网络注册方法包括图3所示方框内的以下动作。该方法可以从方框S开始 301 . [0046] 在小号 301 , 元素 T 的值 i 根据用户命令设置时间数组中的。 [0047] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0048] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0049] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0050] 在小号 302 , 判断移动终端注册第一网络时是否发生预定异常事件, 如果是, S 303 被执行,如果没有,S 315 被执行。 [0051] 本发明实施例以移动终端注册4G网络为例进行说明。 [0052] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0053] 或者,预定异常事件包括TAU被拒绝。 [0054] 第一个网络是4G网络。 [0055] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0056] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0057] 在小号 303 , 元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0058] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0059] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0060] 在小号 304 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0061] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0062] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0063] 在小号 305 ,定时器开始计时,得到第一个计时的时间。 [0064] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0065] 在小号 306 , 判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0066] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0067] 在小号 307 ,继续控制移动终端注册第二网络。 [0068] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0069] 在小号 308 ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的邻区TAI。 [0070] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0071] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0072] 在小号 309,控制移动终端根据第一标识重新注册第一网络。 [0073] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0074] 在小号 310 ,判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0075] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0076] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0077] 在小号 311 ,控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0078] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0079] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0080] 在小号 312 ,判断第二次计数时间是否达到T i+1 . [0081] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0082] 在小号 313 , 当第二次计数时间到达 T i+1,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0083] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0084] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0085] 在小号 314 ,控制移动终端根据第二标识重新注册第一网络。 [0086] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0087] 在小号 315 ,获取TAU被拒绝的信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0088] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0089] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 网络注册成功率。 [0090] 为了更清楚地说明上述实施例的作用,举例如下。 [0091]例如,当时间数组为{1分钟,6分钟,12分钟}时,表示移动终端在发生故障时读取时间数组{1分钟,6分钟,12分钟}中的元素1分钟 由于TAU被拒绝,第一次注册4G网络。 在1分钟的时间间隔内,禁止移动终端注册第一网络,切换注册2G或3G网络。 移动终端以1分钟的时间间隔接入2G或3G网络。 然后,当定时器计时到1分钟时,根据邻区TAI控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}中的元素6分钟,重新启动定时器进行计时。 在6分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到6分钟时,根据移动终端第二次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}的最后一个元素12分钟,重新启动定时器进行计时。 在12分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到12分钟时,根据移动终端第三次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 以此类推,移动终端每12分钟重新搜索一次4G网络。 这样可以保证用户在TAU被网络拒绝的情况下可以注册到其他速率的网络,避免无连接的网络服务状态。 [0092] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 网络注册设备 40 移动终端的功能可以通过软件、硬件或其组合来实现。 网络注册设备 40 移动终端的可以包括阅读模块 401 , 第一控制模块 402 , 一个起始模块 403 , 第一判断模块 404 , 处理模块 405 和第二个控制模块 406 . [0093] 阅读模块 401 被配置为读取元素 T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1至N之间的正整数,N为正整数。 [0094] 或者,预定异常事件包括TAU被拒绝。 [0095] 第一控制模块 402 用于禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0096] 启动模块 403 用于启动定时器进行计时,得到第一计时时间。 [0097] 第一判断模块 404 配置为判断第一个计数时间是否达到T i . [0098] 处理模块 405 被配置为当第一次计数时间达到T时获得第一身份 i 其中,第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识。 [0099] 第二控制模块 406 用于控制移动终端根据第一标识重新注册第一网络。 [0100] 或者,在一些实施例中,如图5所示,网络注册装置 40 移动终端还可以包括第二判断模块 407 , 第三个控制模块 408 , 第三判断模块 409 , 第一获取模块410 , 第四控制模块 411 , 第二个获取模块 412 , 和一个设置模块 413 . [0101] 第二判断模块 407 用于判断移动终端重新注册第一网络时是否发生预定异常事件。 [0102] 第三控制模块 408 用于当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间。 [0103] 第三判断模块 409 用于判断第二次计数时间是否达到T i+1 . [0104] 第一个获取模块 410 用于在秒计数时间达到T时获取第二身份 i+1 其中,第二标识为移动终端在重新注册第一网络时所在小区的相邻小区的跟踪区标识。 [0105] 第四个控制模块 411 用于控制移动终端根据第二标识重新注册第一网络。 [0106] 或者,处理模块 405 还用于当第一计时时间未达到T时,继续控制移动终端注册第二网络 i . [0107] 第二个获取模块 412 用于获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0108] 设置模块 413 被配置为设置元素T的值 i 根据用户命令在时间数组中。 [0109] 需要说明的是,结合图1-图3对移动终端的网络注册方法实施例的说明同样适用于移动终端的网络注册装置,其原理类似,在此不再赘述。 [0110] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i 以及根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率。 网络。 [0111] 本发明实施例还提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器用于通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0112] 在小号 11 ′, 一个元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0113] 本发明实施例以移动终端注册4G网络为例进行说明。 [0114] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0115] 或者,预定异常事件包括TAU被拒绝。 [0116]第一个网络是4G网络。 [0117] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0118] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0119] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0120] 在小号 12 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0121] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0122] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0123] 在小号 13 ',启动定时器计时,得到第一计时时间。 [0124] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0125] 在小号 14 ′,判断第一个计数时间是否达到T i . [0126] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0127] 在另一实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0128] 在小号 21 ′,当第一次计数时间未达到 T 1 ,继续控制移动终端注册第二网络。 [0129]本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0130] 在小号 15 ′,当第一个计数时间到达T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0131] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0132] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0133] 在小号 16 ',控制移动终端根据第一标识重新注册第一网络。 [0134] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0135] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0136] 在另一个实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0137] 在小号 301 ′,元素T的值 i 根据用户命令设置时间数组中的。 [0138] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0139] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0140] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0141] 在小号 302 ',判断移动终端注册第一网络时是否发生预定异常事件,如果是,S 303 被执行,如果没有,S 315 被执行。 [0142] 本发明实施例以移动终端注册4G网络为例进行说明。 [0143] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0144] 或者,预定异常事件包括TAU被拒绝。 [0145] 第一个网络是4G网络。 [0146] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0147] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0148] 在小号 303 ′,元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} i是1到N之间的正整数,N是正整数。 [0149] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0150] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0151] 在小号 304 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0152] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0153] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1. 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0154] 在小号 305 ',启动定时器计时,得到第一个计时时间。 [0155] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0156] 在小号 306 ′,判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0157] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0158] 在小号 307 ',继续控制移动终端注册第二网络。 [0159] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0160] 在小号 308 ',获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0161] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0162] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0163] 在小号 309 ',控制移动终端根据第一标识重新注册第一网络。 [0164] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 z ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0165] 在小号 310 ',判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0166] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0167] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0168] 在小号 311 ',控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0169] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0170] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0171] 在小号 312 ′,判断第二次计时是否达到T i+1 . [0172] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0173] 在小号 313 ′,当第二次计数时间到达T i+1 ,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0174] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0175] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0176] 在小号 314 ',控制移动终端根据第二标识重新注册第一网络。 [0177] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,在第二次注册第一网络时,根据移动终端注册所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0178] 在小号 315 ',获取TAU被拒绝的信息并发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0179] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0180] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 网络注册成功率。 [0181] 上述装置实施例仅仅是示例性的,其中作为单独的部件示出的单元在物理上可以是分离的,也可以不是物理分离的,作为单元示出的部件可以是物理单元也可以不是物理单元,即可以位于一个空间内,或者可以是物理单元。 分布到多个网络单元。 可以根据实际需要选择其中的部分或全部模块来实现本发明的目的。 本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0182] 本发明方法实施例中的动作可以根据实际需要进行调整、合并或者删除。 [0183] 本发明装置实施例中的模块或单元可以根据实际需要进行合并、划分和删除。 [0184] 本发明实施例中的模块或单元可以采用通用集成电路(如CPU)实现,也可以采用专用集成电路(ASIC)实现。 [0185]通过以上对实施例的描述,本领域的技术人员可以清楚地了解到,各个实施例可以通过软件结合必要的通用硬件平台来实现,也可以通过硬件来实现。 基于这种理解,上述技术方案的本质或者对相关技术有贡献的部分可以以软件产品的形式体现。 计算机软件产品可以存储在计算机可读存储介质中,例如ROM/RAM、磁盘、CD等,可以包括若干指令,用于使计算机设备(可以是个人计算机、服务器或 网络设备)执行各个实施例或实施例的部分描述的方法。 [0186] 上述实施方式并不构成对本发明保护范围的限制。 凡在本发明的精神和范围内所作的任何修改、等同或者改进,均包含在本技术方案的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.716 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.717 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.717 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10419919B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.730 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.731 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), CN105933884A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), CN105933884B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), US10419919B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), US10419920B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), US20190045350A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), US20190141514A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270656(Integer), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10419919B2(String), US10419919B2(String), 1568649600(Integer), 270656(Integer), 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 0(Integer), 1681975542(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184973(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 1(Integer), 184973(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD.(String), OPPO广东移动通信有限公司(String), 0(Integer), 1681975542(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.847 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.848 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184973(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75923(Integer), 2(Integer), 184973(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75923(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.876 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.876 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10419920B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 一种移动终端的网络注册方法、存储介质和移动终端(String), US10419920B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端及存储介质。 移动终端的网络注册方法实现如下。 一个元素 T i 响应于确定移动终端注册第一网络时发生预定异常事件,读取时间数组中的时间数组。 i是1到N之间的正整数,N是正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时以获得第一计数时间。 判断第一个计数时间是否达到T i . 如果第一个计数时间达到 T,则获取第一个身份 i . 第一标识为注册第一网络时所注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/201705(String), 1543248000(Integer), US10419920B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184974(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\6554149e309b4c0cb8eae99e62551a0a.png(String), 184974(Integer), 6554149e309b4c0cb8eae99e62551a0a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 一种移动终端的网络注册方法、存储介质和移动终端(String), US10419920B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端及存储介质。 移动终端的网络注册方法实现如下。 一个元素 T i 响应于确定移动终端注册第一网络时发生预定异常事件,读取时间数组中的时间数组。 i是1到N之间的正整数,N是正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时以获得第一计数时间。 判断第一个计数时间是否达到T i . 如果第一个计数时间达到 T,则获取第一个身份 i . 第一标识为注册第一网络时所注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/201705(String), 1543248000(Integer), US10419920B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), \20230420\6554149e309b4c0cb8eae99e62551a0a.png(String), 12(Integer), 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 1. A network registration method of a mobile terminal, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity;wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity;obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 1.根据权利要求10所述的非暂时性计算机可读存储介质,还包括:设置元素T的值i根据用户命令在时间数组中。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 2. The method according to claim 1, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 12.根据权利要求9所述的非暂时性计算机可读存储介质,还包括:设置元素T的值i根据用户命令在时间数组中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 3. The method according to claim 2, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 4. The method according to claim 1, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 5. A mobile terminal, comprising:a housing;a processor;a memory; anda circuit board and a power supply circuit,wherein, the circuit board is disposed inside a space enclosed by the housing; the processor and the memory are disposed on the circuit board; the power supply circuit is configured to supply power for respective circuits or components of the mobile terminal; the memory is configured to store executable program codes; and the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform:reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity;wherein the processor is further configured to:determine whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, control the mobile terminal to re-register the second network, and reset the timer for timing again to obtain a second counted time;alternately read an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determine whether the second counted time reaches Ti+1;obtain a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when re-registering the first network; andcontrol the mobile terminal to re-register the first network according to the second identity;obtain information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 6. The mobile terminal according to claim 5, wherein the processor is further configured to:continue to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 7. The mobile terminal according to claim 6, wherein the processor is further configured to:set a value of the element Ti in the time array according to a user command.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 8. The mobile terminal according to claim 5, wherein the processor is further configured to:set a value of the element Ti in the time array according to a user command.(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 9. A non-transitory computer-readable storage medium, having stored therein instructions that, when executed by a processor of a mobile terminal, cause the mobile terminal to execute a network registration method, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity;wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity;obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 10. The non-transitory computer-readable storage medium according to claim 9, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 11. The non-transitory computer-readable storage medium according to claim 10, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:42.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184974(Integer), 12. The non-transitory computer-readable storage medium according to claim 9, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.021 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184974(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a Continuation Application of U.S. application Ser. No. 16/072,025, filed Jul. 23, 2018, which is a National Stage Entry of International Application No. PCT/CN2017/088117, filed Jun. 13, 2017 which claims priority to Chinese Patent Application No. 201610460475.8 filed by on Jun. 21, 2016 and titled with “NETWORK REGISTRATION METHOD AND APPARATUS FOR MOBILE TERMINAL, AND MOBILE TERMINAL”, the entire contents of which are incorporated herein by reference. FIELD [0002]The present disclosure relates to the communication technology field, and more particularly, to a network registration method of a mobile terminal, a storage medium and a mobile terminal. BACKGROUND [0003]With continuous development of communication technologies, most areas of the country have been covered by 4G network, and users can quickly access to Internet by connecting the mobile terminals to the 4G network. In the related art, when the mobile terminal receives a response indicating that TAU (Tracking Area Update) is rejected, the mobile terminal stops registering the 4G network and does not search for networks of cells with different TAI (Tracking Area Identity). [0004]In this way, when the current TAU is rejected by the network, a success rate of registering the network by the mobile terminal is low. SUMMARY [0005]The present disclosure aims to solve at least one of the problems existing in the related art to some extent at least. [0006]Embodiments of the present disclosure provide a network registration method of a mobile terminal. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. After controlling the mobile terminal to re-register the first network according to the first identity, the method further includes: determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network; when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time; alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1; obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; and controlling the mobile terminal to re-register the first network according to the second identity; obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information. [0007]Embodiments of the present disclosure provide a mobile terminal. The mobile terminal includes a housing, a processor, a memory, a circuit board and a power supply circuit. The circuit board is disposed inside a space enclosed by the housing. The processor and the memory are disposed on the circuit board. The power supply circuit is configured to supply power for respective circuits or components of the mobile terminal. The memory is configured to store executable program codes. The processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform: reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. The processor is further configured to: determine whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network; when the predetermined abnormal event occurs, control the mobile terminal to re-register the second network, and reset the timer for timing again to obtain a second counted time; alternately read an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determine whether the second counted time reaches Ti+1; obtain a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when re-registering the first network; and control the mobile terminal to re-register the first network according to the second identity; obtain information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information. [0008]Embodiments of the present disclosure provide a non-transitory storage medium. When instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform a network registration method. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. After controlling the mobile terminal to re-register the first network according to the first identity, the method further includes: determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network; when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time; alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1; obtaining a second identity when the second counted time reaches wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; and controlling the mobile terminal to re-register the first network according to the second identity; obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information. [0009]It is to be understood that, both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to explain technical solutions of the present disclosure more clearly, drawings required to be used in the description of embodiments will now be illustrated briefly. Obviously, drawings in the following description are some embodiments of the present disclosure, and further drawings can be obtained by those skilled in the art based on these drawings, without creative labor. [0011]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0013]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0014]FIG. 4 is a block diagram of a network registration apparatus of a mobile terminal according to an embodiment of the present disclosure. [0015]FIG. 5 is a block diagram of a network registration apparatus of a mobile terminal according to another embodiment of the present disclosure. DETAILED DESCRIPTION [0016]Technical solutions in embodiments of the present disclosure will be described clearly and completely in the following with reference to drawings in embodiments of the present disclosure. Obviously, the embodiments described are merely illustrative, and are not exhaustive. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without creative labor belong to the protection scope of the present disclosure. [0017]Terms such as “first”, “second”, “third” and “four” in the description, claims and drawings of the present disclosure are used to distinguish different objects, and are not used to describe specific order. In addition, terms such as “including” and “having” and their variants intend to cover non-exclusive inclusion. For example, procedures, methods, systems, products or apparatus including a series of steps or units are not limited to listed steps or units, but alternatively further include steps or units which are not listed, or alternatively further include other steps or units inherent to these procedures, methods, products and apparatus. [0018]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in a network registration apparatus of a mobile terminal for illustration. Embodiments of the present disclosure may be applied in a procedure when the user uses the mobile terminal to register 4G network, or may be applied in a procedure of registering 3G network or 2G network, which are not limited. The mobile terminal may be hardware devices with various operating systems, such as a smart phone, a tablet PC, a PDA, and an E-book. [0019]The network registration method of the mobile terminal can include following actions in blocks illustrated in FIG. 1. The method can begin at block S11. [0020]At block S11, an element Ti in a time array is read in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, in which the time array is {T1, . . . , T2, Ti, Ti+1, . . . , Tn}, is a positive integer between 1 and N, and N is a positive integer. [0021]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0022]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0023]Alternatively, the predetermined abnormal event includes TAU being rejected. [0024]The first network is 4G network. [0025]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0026]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the network with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0027]A value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0028]At S12, the mobile terminal is prohibited from registering the first network, and is controlled to register a second network. [0029]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0030]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of thus effectively ensuring that the mobile terminal can normally access to Internet. [0031]At S13, the timer is started to time, to obtain a first counted time. [0032]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0033]At S14, it is determined whether the first counted time reaches Ti. [0034]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0035]In some embodiments, as illustrated in FIG. 2, following action may be performed after S14. [0036]At S21, when the first counted time does not reach T1, the mobile terminal is continuously controlled to register the second network. [0037]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0038]At S15, when the first counted time reaches Ti, a first identity is obtained, in which the first identity is the TAI of an adjacent cell of a cell where the mobile terminal is when registering the first network. [0039]In embodiments of the present disclosure, when the first counted time reached Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0040]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0041]At S16, the mobile terminal is controlled to re-register the first network according to the first identity. [0042]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the times reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0043]In this embodiment, by controlling the mobile terminal to register the second network when the predetermined abnormal event occurs during the mobile terminal registers the first network, it can ensure that the user registers the network successfully, and by obtaining the first identity (the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network) when the first counted time reaches Ti, and controlling the mobile terminal to re-register the first network according to the first identity, the mobile terminal can register the network of the cell with different TAI when the current TAU is rejected by the network, thus effectively enhancing the success rate of registering the network. [0044]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in the network registration apparatus of the mobile terminal for illustration. [0045]The network registration method of the mobile terminal includes following actions in blocks illustrated in FIG. 3. The method can begin at block S301. [0046]At S301, the value of the element Ti in the time array is set according to a user command. [0047]In this embodiment, the value of the element Ti in the time array may be preset by the user based on this own demand. [0048]For example, the mobile terminal may receive the command input by the user on the screen, and sets the value of the element Ti in the time array according to the user command. The values of the elements Ti in the time array may be sequentially input by the user on the screen, or may be selectively input by the user, which is not limited. [0049]In this action, the time Ti of the time array is set by the user, and thus personalized setting of the time array may be realized, the generality of the network registration method of the mobile terminal may be improved, and the success rate of the network registration of the mobile terminal may be enhanced. [0050]At S302, it is determined whether the predetermined abnormal event occurs when the mobile terminal registers the first network, and if yes, S303 is executed, and if no, S315 is executed. [0051]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0052]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0053]Alternatively, the predetermined abnormal event includes TAU being rejected. [0054]The first network is 4G network. [0055]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. This embodiment is applied in the procedure in which the mobile terminal registers the network, and is applied after the TAU is rejected. [0056]Alternatively, it is possible to determine whether the event of the TAU being rejected by the network occurs during the mobile terminal registers the 4G network, to trigger subsequent actions. [0057]At S303, the element Ti in the time array is read, in which the time array is {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, i is a positive integer between 1 and N, and N is a positive integer. [0058]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the networks with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0059]The value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0060]At S304, the mobile terminal is prohibited from registering the first network, and is controlled to register the second network. [0061]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0062]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti, thus effectively ensuring that the mobile terminal can normally access to Internet. [0063]At S305, the timer is started to time, to obtain the first counted time. [0064]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0065]At S306, it is determined whether the first counted time reaches Ti, and if yes, S308 is executed, and if no, S307 is executed. [0066]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0067]At S307, the mobile terminal is continuously controlled to register the second network. [0068]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0069]At S308, the first identity is obtained, in which the first identity is the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network. [0070]In embodiments of the present disclosure, when the first counted time reaches Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0071]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0072]At S309, the mobile terminal is controlled to re-register the first network according to the first identity. [0073]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the timer reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0074]At S310, it is determined whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network, and if yes, S311 is executed, and if no, S315 is executed. [0075]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0076]Alternatively, it is determined whether the TAU is rejected by the network when the mobile terminal re-registers the first network, to trigger subsequent actions. [0077]At S311, the mobile terminal is controlled to re-register the second network, and the timer is reset to time again to obtain the second counted time. [0078]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T2. Alternatively, when the mobile terminal alternately reads the element Ti+1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti+1, thus effectively ensuring that the mobile terminal can normally access to Internet. [0079]While the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the second counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti+1 according to the second counted time, which is not limited. [0080]At S312, it is determined whether the second counted time reaches Ti+1. [0081]In embodiments of the present disclosure, it is possible to determine whether the second counted time reaches Ti+1, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0082]At S313, when the second counted time reaches Ti+1, the second identity is obtained, in which the second identity is the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network. [0083]In embodiments of the present disclosure, when the second counted time reaches Ti+1, the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0084]The TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0085]At S314, the mobile terminal is controlled to re-register the first network according to the second identity. [0086]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network due to the TAU being rejected, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T2, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T2. Then, when the counted time of the timer reaches T2, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T3 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T3. When the re-counted time reaches T3, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0087]At S315, information about the TAU being rejected is obtained and se(String), 相关申请的交叉引用 [0001] 该申请是美国申请序列号的延续申请。 2018年7月23日提交的第16/072,025号国际申请进入国家阶段,2017年6月13日提交的PCT/CN2017/088117号要求2017年6月13日提交的中国专利申请201610460475.8的优先权 . 21, 2016,标题为“用于移动终端的网络注册方法和装置,以及移动终端”,其全部内容通过引用并入本文。 场地 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端的网络注册方法、存储介质及移动终端。 背景 [0003] 随着通信技术的不断发展,全国大部分地区已被4G网络覆盖,用户可以通过移动终端接入4G网络快速上网。 相关技术中,当移动终端接收到拒绝TAU(Tracking Area Update)响应时,移动终端停止注册4G网络,不再搜索不同TAI(Tracking Area Identity)小区的网络。 [0004] 这样,当当前TAU被网络拒绝时,移动终端注册网络的成功率较低。 概括 [0005] 本发明旨在至少在一定程度上解决相关技术中存在的问题中的至少一个。 [0006] 本发明实施例提供了一种移动终端的网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1和N之间的正整数,N为正整数,预定异常事件包括跟踪区域更新(TAU)为 拒绝,元素 T 的值 i 时间数组中的是用户在屏幕上依次输入或者是用户选择性输入; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 在根据第一标识控制移动终端重新注册第一网络之后,该方法还包括: 判断移动终端重新注册第一网络时是否发生预定异常事件; 当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间; 交替读取元素 T i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n},判断第二次计时是否达到T i+1 ; 第二次计时时间达到T时获得第二身份 i+1 ,其中,所述第二标识为所述移动终端在重新注册第一网络时注册的小区的相邻小区的跟踪区标识; 控制移动终端根据第二身份重新注册第一网络; 获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0007]本发明实施例提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器,用于通过读取内存中存储的可执行程序代码,运行与可执行程序代码对应的程序,以执行:读取元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1和N之间的正整数,N为正整数,预定异常事件包括跟踪区域更新(TAU)为 拒绝,元素 T 的值 i 时间数组中的是用户在屏幕上依次输入或者是用户选择性输入; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 处理器还用于判断移动终端重新注册第一网络时是否发生预定异常事件; 当预定异常事件发生时,控制移动终端重新注册第二网络,并重新设置定时器重新计时,得到第二计时时间。 交替读取一个元素 T i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n},判断第二次计数时间是否达到T i+1 ; 当第二次计数时间达到T时获得第二个身份 i+1 ,其中,所述第二标识为所述移动终端在重新注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第二身份重新注册第一网络; 获取TAU被拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0008] 本公开的实施例提供了一种非暂时性存储介质。 当移动终端的处理器执行存储在存储介质中的指令时,使移动终端执行网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1和N之间的正整数,N为正整数,预定异常事件包括跟踪区域更新(TAU)为 拒绝,元素 T 的值 i 时间数组中的是用户在屏幕上依次输入或者是用户选择性输入; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i, 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 在根据第一标识控制移动终端重新注册第一网络之后,该方法还包括: 判断移动终端重新注册第一网络时是否发生预定异常事件; 当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间; 交替读取元素 T i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n},判断第二次计时是否达到T i+1 ; 在第二计数时间到达时获取第二标识,其中,第二标识为移动终端在重新注册第一网络时注册的小区的相邻小区的跟踪区标识; 控制移动终端根据第二身份重新注册第一网络; 获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0009] 应当理解,前述的一般描述和以下的详细描述都只是示例性和解释性的,而不是对本公开的限制。 附图的简要说明 [0010] 为了更加清楚地说明本发明的技术方案,现对实施例描述中需要用到的附图进行简要说明。 显然,以下描述中的附图仅为本发明的一些实施例,本领域技术人员基于这些附图在没有做出创造性劳动的情况下所获得的进一步的附图。 [0011] 图1是根据本发明实施例的移动终端的网络注册方法的流程图。 [0012] 图2是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0013] 图3是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0014] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 [0015] 图5是根据本发明另一实施例的移动终端的网络注册装置的框图。 详细说明 [0016] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 显然,所描述的实施例仅仅是示例性的,而不是穷举性的。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0017] 本发明的说明书、权利要求书和附图中的“第一”、“第二”、“第三”、“四”等术语用于区分不同的对象,不用于描述具体顺序。 此外,诸如“包括”和“具有”及其变体等术语旨在涵盖非排他性包含。 例如,包括一系列步骤或单元的程序、方法、系统、产品或装置不限于列出的步骤或单元,而是还包括未列出的步骤或单元,或者还包括其他固有的步骤或单元 这些程序、方法、产品和设备。 [0018]图1是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 本发明实施例可以应用在用户使用移动终端注册4G网络的过程中,也可以应用在注册3G网络或2G网络的过程中,不做限定。 移动终端可以是智能手机、平板电脑、PDA、电子书等各种操作系统的硬件设备。 [0019] 移动终端的网络注册方法可以包括图1所示的块中的以下动作。该方法可以从块S开始 11 . [0020] 在S座 11 , 元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 ,. . . , 吨 2 , 吨 i , 吨 i+1 ,. . . , 吨 n},是1到N之间的正整数,N是正整数。 [0021] 本发明实施例以移动终端注册4G网络为例进行说明。 [0022] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0023] 或者,预定异常事件包括TAU被拒绝。 [0024] 第一个网络是4G网络。 [0025] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0026] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0027] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0028] 在小号 12 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0029] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0030] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在时间间隔内切换注册不同速率的网络,从而有效保证移动终端可以正常上网。 [0031] 在小号 13 ,定时器开始计时,得到第一个计时时间。 [0032] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0033] 在小号 14 , 判断第一个计数时间是否达到T i . [0034] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0035] 在一些实施例中,如图2所示,可以在S之后执行以下动作 14 . [0036] 在小号 21 , 当第一次计数时间没有达到 T 1 ,继续控制移动终端注册第二网络。 [0037] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0038] 在小号 15 , 当第一个计数时间到达 T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0039] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0040] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0041] 在小号 16 ,控制移动终端根据第一标识重新注册第一网络。 [0042] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0043]本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0044] 图3是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 [0045] 移动终端的网络注册方法包括图3所示方框内的以下动作。该方法可以从方框S开始 301 . [0046] 在小号 301 , 元素 T 的值 i 根据用户命令设置时间数组中的。 [0047] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0048] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0049] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0050] 在小号 302 , 判断移动终端注册第一网络时是否发生预定异常事件, 如果是, S 303 被执行,如果没有,S 315 被执行。 [0051] 本发明实施例以移动终端注册4G网络为例进行说明。 [0052] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0053] 或者,预定异常事件包括TAU被拒绝。 [0054] 第一个网络是4G网络。 [0055] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0056] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0057] 在小号 303 , 元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0058] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0059] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0060] 在小号 304 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0061] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0062] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0063] 在小号 305 ,定时器开始计时,得到第一个计时的时间。 [0064] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0065] 在小号 306 , 判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0066] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0067] 在小号 307 ,继续控制移动终端注册第二网络。 [0068] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0069] 在小号 308 ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的邻区TAI。 [0070] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0071] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0072] 在小号 309,控制移动终端根据第一标识重新注册第一网络。 [0073] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0074] 在小号 310 ,判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0075] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0076] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0077] 在小号 311 ,控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0078] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0079] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0080] 在小号 312 ,判断第二次计数时间是否达到T i+1 . [0081] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0082] 在小号 313 , 当第二次计数时间到达 T i+1,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0083] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0084] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0085] 在小号 314 ,控制移动终端根据第二标识重新注册第一网络。 [0086] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0087] 在小号 315 ,获取TAU被拒绝的信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0088] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0089] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 注册网络的成功率。 [0090] 为了更清楚地说明上述实施例的作用,举例如下。 [0091]例如,当时间数组为{1分钟,6分钟,12分钟}时,表示移动终端在发生故障时读取时间数组{1分钟,6分钟,12分钟}中的元素1分钟 由于TAU被拒绝,第一次注册4G网络。 在1分钟的时间间隔内,禁止移动终端注册第一网络,切换注册2G或3G网络。 移动终端以1分钟的时间间隔接入2G或3G网络。 然后,当定时器计时到1分钟时,根据邻区TAI控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}中的元素6分钟,重新启动定时器进行计时。 在6分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到6分钟时,根据移动终端第二次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}的最后一个元素12分钟,重新启动定时器进行计时。 在12分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到12分钟时,根据移动终端第三次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 以此类推,移动终端每12分钟重新搜索一次4G网络。 这样可以保证用户在TAU被网络拒绝的情况下可以注册到其他速率的网络,避免无连接的网络服务状态。 [0092] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 网络注册设备 40 移动终端的功能可以通过软件、硬件或其组合来实现。 网络注册设备 40 移动终端的可以包括阅读模块 401 , 第一控制模块 402 , 一个起始模块 403 , 第一判断模块 404 , 处理模块 405 和第二个控制模块 406 . [0093] 阅读模块 401 被配置为读取元素 T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1至N之间的正整数,N为正整数。 [0094] 或者,预定异常事件包括TAU被拒绝。 [0095] 第一控制模块 402 用于禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0096] 启动模块 403 用于启动定时器进行计时,得到第一计时时间。 [0097] 第一判断模块 404 配置为判断第一个计数时间是否达到T i . [0098] 处理模块 405 被配置为当第一次计数时间达到T时获得第一身份 i 其中,第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识。 [0099] 第二控制模块 406 用于控制移动终端根据第一标识重新注册第一网络。 [0100] 或者,在一些实施例中,如图5所示,网络注册装置 40 移动终端还可以包括第二判断模块 407 , 第三个控制模块 408 , 第三判断模块 409 , 第一获取模块410 , 第四控制模块 411 , 第二个获取模块 412 , 和一个设置模块 413 . [0101] 第二判断模块 407 用于判断移动终端重新注册第一网络时是否发生预定异常事件。 [0102] 第三控制模块 408 用于当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间。 [0103] 第三判断模块 409 用于判断第二次计数时间是否达到T i+1 . [0104] 第一个获取模块 410 用于在秒计数时间达到T时获取第二身份 i+1 其中,第二标识为移动终端在重新注册第一网络时所在小区的相邻小区的跟踪区标识。 [0105] 第四个控制模块 411 用于控制移动终端根据第二标识重新注册第一网络。 [0106] 或者,处理模块 405 还用于当第一计时时间未达到T时,继续控制移动终端注册第二网络 i . [0107] 第二个获取模块 412 用于获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0108] 设置模块 413 被配置为设置元素T的值 i 根据用户命令在时间数组中。 [0109] 需要说明的是,结合图1-图3对移动终端的网络注册方法实施例的说明同样适用于移动终端的网络注册装置,其原理类似,在此不再赘述。 [0110] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i 以及根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率。 网络。 [0111] 本发明实施例还提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器用于通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0112] 在小号 11 ′, 一个元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0113] 本发明实施例以移动终端注册4G网络为例进行说明。 [0114] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0115] 或者,预定异常事件包括TAU被拒绝。 [0116]第一个网络是4G网络。 [0117] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0118] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0119] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0120] 在小号 12 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0121] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0122] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . ,T},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0123] 在小号 13 ',启动定时器计时,得到第一计时时间。 [0124] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0125] 在小号 14 ′,判断第一个计数时间是否达到T i . [0126] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0127] 在另一个实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0128] 在小号 21 ′,当第一次计数时间未达到 T 1 ,继续控制移动终端注册第二网络。 [0129] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0130] 在小号 15 ′,当第一个计数时间到达T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0131] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0132] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0133] 在小号 16 ',控制移动终端根据第一标识重新注册第一网络。 [0134] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . ,T}并重新设置定时器重新计时,在T的时间间隔内切换到重新注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0135] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0136] 在另一个实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0137] 在小号 301 ′,元素T的值 i 根据用户命令设置时间数组中的。 [0138] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0139] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0140] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0141] 在小号 302 ',判断移动终端注册第一网络时是否发生预定异常事件,如果是,S 303 被执行,如果没有,S 315 被执行。 [0142] 本发明实施例以移动终端注册4G网络为例进行说明。 [0143] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0144] 或者,预定异常事件包括TAU被拒绝。 [0145] 第一个网络是4G网络。 [0146] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0147] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0148] 在小号 303 ′,元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0149] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0150] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0151] 在小号 304 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0152] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0153] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0154] 在小号 305 ',启动定时器计时,得到第一个计时时间。 [0155] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0156] 在小号 306 ′,判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0157] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0158] 在小号 307 ',继续控制移动终端注册第二网络。 [0159] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0160] 在小号 308 ',获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0161] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0162] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0163] 在小号 309 ',控制移动终端根据第一标识重新注册第一网络。 [0164] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0165] 在小号 310',判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0166] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0167] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0168] 在小号 311 ',控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0169] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0170] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0171] 在小号 312 ′,判断第二次计时是否达到T i+1 . [0172] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0173] 在小号 313 ′,当第二次计数时间到达T i+1 ,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0174] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0175] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0176] 在小号 314 ',控制移动终端根据第二标识重新注册第一网络。 [0177] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,在第二次注册第一网络时,根据移动终端注册所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0178] 在小号 315 ',获取TAU被拒绝的信息并发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0179] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0180] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 网络注册成功率。 [0181] 上述装置实施例仅仅是示例性的,其中作为单独的部件示出的单元在物理上可以是分离的,也可以不是物理分离的,作为单元示出的部件可以是物理单元也可以不是物理单元,即可以位于一个空间内,或者可以是物理单元。 分布到多个网络单元。 可以根据实际需要选择其中的部分或全部模块来实现本发明的目的。 本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0182] 本发明方法实施例中的动作可以根据实际需要进行调整、合并或者删除。 [0183] 本发明装置实施例中的模块或单元可以根据实际需要进行合并、划分和删除。 [0184] 本发明实施例中的模块或单元可以采用通用集成电路(如CPU)实现,也可以采用专用集成电路(ASIC)实现。 [0185] 通过以上对实施例的描述,本领域的技术人员可以清楚地了解到,各个实施例可以通过软件结合必要的通用硬件平台来实现,也可以通过硬件来实现。 基于这种理解,上述技术方案的本质或者对相关技术有贡献的部分可以以软件产品的形式体现。 计算机软件产品可以存储在计算机可读存储介质中,例如ROM/RAM、磁盘、CD等,可以包括若干指令,用于使计算机设备(可以是个人计算机、服务器或 网络设备)执行各个实施例或实施例的部分描述的方法。 [0186] 上述实施方式并不构成对本发明保护范围的限制。 凡在本发明的精神和范围内所作的任何修改、等同或者改进,均包含在本技术方案的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), CN105933884A(String), 1047114(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.052 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.052 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.052 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), CN105933884B(String), 1047115(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), US10419919B2(String), 1047116(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), US10419920B2(String), 1047117(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), US20190045350A1(String), 1047118(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), US20190141514A1(String), 1047119(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270656(Integer), WO2017219897A1(String), 1047120(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10419919B2(String), US10419919B2(String), 1568649600(Integer), 270656(Integer), 184973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184974(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.066 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 1(Integer), 184974(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.076 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.077 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.077 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184974(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 2(Integer), 184974(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.100 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.100 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.100 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10469652B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, method for mobile terminal to set font display state, and storage medium(String), 移动终端、移动终端设置字体显示状态的方法及存储介质(String), US10469652B2(String), Disclosed are a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. The method may comprise: acquiring, by a mobile terminal, a current shake level; searching, by the mobile terminal, a corresponding relationship between a shake level and a font display state according to the current shake level, to acquire a font display state corresponding to the current shake level of the mobile terminal; and setting, by the mobile terminal, a default font display state as the font display state corresponding to the current shake level of the mobile terminal.(String), 本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 该方法可以包括: 移动终端获取当前抖动程度; 移动终端根据当前抖动级别查找抖动级别与字体显示状态的对应关系,获取移动终端当前抖动级别对应的字体显示状态; 移动终端设置默认字体显示状态为移动终端当前抖动级别对应的字体显示状态。(String), US15/511022(String), 1418572800(Integer), US10469652B2(String), 1572883200(Integer), 1572883200(Integer), 美国(String), 4(Integer), CN(String), 3(Integer), 27(Integer), CN102239471A | CN102541254A | CN103176623A | CN103176694A | CN103200323A | CN103246441A | CN103248749A | CN103309582A | JP2003169125A | JP2005006161A | JP2005012297A | JP2006201006A | US20080254837A1 | US20090186659A1 | US20100103197A1 | US20110208472A1 | US20120081281A1 | US20130235058A1 | US20130254657A1 | US20130293589A1 | US20150177826A1 | US20150192424A1 | US20150212611A1 | US20150248378A1 | US20150296034A1 | US20160259420A1 | US9430450B1(String), 9(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184975(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\98e25a3724b94de0a10d1dde9aff99bd.png(String), 184975(Integer), 98e25a3724b94de0a10d1dde9aff99bd.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, method for mobile terminal to set font display state, and storage medium(String), 移动终端、移动终端设置字体显示状态的方法及存储介质(String), US10469652B2(String), Disclosed are a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. The method may comprise: acquiring, by a mobile terminal, a current shake level; searching, by the mobile terminal, a corresponding relationship between a shake level and a font display state according to the current shake level, to acquire a font display state corresponding to the current shake level of the mobile terminal; and setting, by the mobile terminal, a default font display state as the font display state corresponding to the current shake level of the mobile terminal.(String), 本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 该方法可以包括: 移动终端获取当前抖动程度; 移动终端根据当前抖动级别查找抖动级别与字体显示状态的对应关系,获取移动终端当前抖动级别对应的字体显示状态; 移动终端设置默认字体显示状态为移动终端当前抖动级别对应的字体显示状态。(String), US15/511022(String), 1418572800(Integer), US10469652B2(String), 1572883200(Integer), 1572883200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 3(Integer), 27(Integer), CN102239471A | CN102541254A | CN103176623A | CN103176694A | CN103200323A | CN103246441A | CN103248749A | CN103309582A | JP2003169125A | JP2005006161A | JP2005012297A | JP2006201006A | US20080254837A1 | US20090186659A1 | US20100103197A1 | US20110208472A1 | US20120081281A1 | US20130235058A1 | US20130254657A1 | US20130293589A1 | US20150177826A1 | US20150192424A1 | US20150212611A1 | US20150248378A1 | US20150296034A1 | US20160259420A1 | US9430450B1(String), \20230420\98e25a3724b94de0a10d1dde9aff99bd.png(String), 9(Integer), 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.140 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.142 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 1. A method for a mobile terminal to set a font display state comprising:acquiring, by the mobile terminal, a current jitter level;searching, by the mobile terminal, a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; andsetting, by the mobile terminal, a default font display state as the font display state corresponding to the current jitter level of the mobile terminal;wherein acquiring, by the mobile terminal, the current jitter level comprises:acquiring, by the mobile terminal, a first acceleration range absolute value within a first preset time period, and comparing the first acceleration range absolute value with a preset acceleration range absolute value threshold;acquiring, by the mobile terminal, at least two second acceleration range absolute values within a second preset time period when the first acceleration range absolute value is larger than the preset acceleration range absolute value threshold;acquiring, by the mobile terminal, a third acceleration range absolute value, which is larger than the preset acceleration range absolute value threshold, from each of the at least two second acceleration range absolute values; andacquiring, by the mobile terminal, an average value of the third acceleration range absolute values when a number of the third acceleration range absolute values is not smaller than a first preset number; andwherein searching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the current jitter level, to acquire the font display state corresponding to the current jitter level of the mobile terminal, comprises:searching, by the mobile terminal, a correspondence relationship between an acceleration range absolute value and the font display state according to the average value, to acquire a font display state corresponding to the average value.(String), 1、一种移动终端设置字体显示状态的方法包括:移动终端获取当前的抖动水平;移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态;和移动终端将默认的字体显示状态设置为移动终端当前抖动等级对应的字体显示状态;其中,移动终端获取当前抖动水平包括:移动终端获取第一预设时间段内的第一加速度范围绝对值,将第一加速度范围绝对值与预设加速度范围绝对值阈值进行比较;当第一加速度范围绝对值大于预设加速度范围绝对值阈值时,移动终端在第二预设时间段内获取至少两个第二加速度范围绝对值;移动终端分别从至少两个第二加速度范围绝对值中获取大于预设加速度范围绝对值阈值的第三加速度范围绝对值;和当第三加速度范围绝对值的个数不小于第一预设数量时,移动终端获取第三加速度范围绝对值的平均值;和其中,移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态,包括:移动终端根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取平均值对应的字体显示状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 2. The method according to claim 1, wherein acquiring, by the mobile terminal, the first acceleration range absolute value within the first preset time period comprises:acquiring, by the mobile terminal, a first original acceleration and a second original acceleration within the first preset time period;processing, by the mobile terminal, the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively;processing, by the mobile terminal, the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively; andperforming, by the mobile terminal, an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value.(String), 2.根据权利要求1所述的方法,其中移动终端获取第一预设时间段内的第一加速度范围绝对值包括:移动终端获取第一预设时间内的第一原始加速度和第二原始加速度;移动终端通过低通滤波器处理第一原始加速度和第二原始加速度,分别获取第一加速度中值和第二加速度中值;移动终端通过高通滤波器处理第一加速度中值和第二加速度中值,分别获取第一加速度和第二加速度;和移动终端对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 3. The method according to claim 1, wherein when a current font display state of the mobile terminal is not the default font display state, the method further comprises:acquiring, by the mobile terminal, at least two fourth acceleration range absolute values within a third time period;acquiring, by the mobile terminal, an updated jitter level when a number of those larger than the preset acceleration range absolute value threshold among the at least two fourth acceleration range absolute values is not smaller than a second preset number;searching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; andsetting, by the mobile terminal, the current font display state as the font display state corresponding to the updated jitter level of the mobile terminal.(String), 3.根据权利要求1所述的方法,其中当移动终端当前的字体显示状态不是默认字体显示状态时,该方法还包括:移动终端在第三时间段内获取至少两个第四加速度范围绝对值;当所述至少两个第四加速度范围绝对值中大于预设加速度范围绝对值阈值的个数不小于第二预设个数时,移动终端获取更新后的抖动水平;移动终端根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态;和移动终端将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 4. A mobile terminal comprising a processor and a memory for storing instructions executable by the processor, wherein the processor is arranged to:acquire a current jitter level;search a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; andset a default font display state as the font display state corresponding to the current jitter level of the mobile terminal;wherein the processor is further arranged to:acquire a first acceleration range absolute value within a first preset time period, and compare the first acceleration range absolute value with a preset acceleration range absolute value threshold;acquire at least two second acceleration range absolute values within a second preset time period when the first acceleration range absolute value is larger than the preset acceleration range absolute value threshold;acquire a third acceleration range absolute value, which is larger than the preset acceleration range absolute value threshold, from each of the at least two second acceleration range absolute values;acquire an average value of the third acceleration range absolute values when a number of the third acceleration range absolute values is not smaller than a first preset number; andsearch a correspondence relationship between an acceleration range absolute value and the font display state according to the average value, to acquire a font display state corresponding to the average value.(String), 4.移动端包括处理器和用于存储可由处理器执行的指令的存储器,其中处理器被布置成:获取当前抖动水平;根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态;和设置默认字体显示状态为移动终端当前抖动等级对应的字体显示状态;其中,处理器还被布置成:在第一预设时间段内获取第一加速度范围绝对值,并将第一加速度范围绝对值与预设加速度范围绝对值阈值进行比较;当第一加速度范围绝对值大于预设加速度范围绝对值阈值时,在第二预设时间段内获取至少两个第二加速度范围绝对值;从至少两个第二加速度范围绝对值中的每一个获取大于预设加速度范围绝对值阈值的第三加速度范围绝对值;当第三加速度范围绝对值的个数不小于第一预设数量时,获取第三加速度范围绝对值的平均值;和根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取该平均值对应的字体显示状态。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 5. The mobile terminal according to claim 4, wherein the processor is further arranged to:acquire a first original acceleration and a second original acceleration within the first preset time period;process the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively;process the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively; andperform an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value.(String), 5.根据权利要求4所述的移动终端,其中处理器还被布置成:在第一预设时间段内获取第一原始加速度和第二原始加速度;通过低通滤波器处理第一原始加速度和第二原始加速度,分别获得第一加速度中值和第二加速度中值;通过高通滤波器对第一加速度中值和第二加速度中值进行处理,分别得到第一加速度和第二加速度。和对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 6. The mobile terminal according to claim 4, wherein when a current font display state of the mobile terminal is not the default font display state, the processor is further arranged to:acquire at least two fourth acceleration range absolute values within a third time period;acquire an updated jitter level when a number of those larger than the preset acceleration range absolute value threshold among the at least two fourth acceleration range absolute values is not smaller than a second preset number;search the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; andset the current font display state as the font display state corresponding to the updated jitter level of the mobile terminal.(String), 6.根据权利要求4所述的移动终端,其中当移动终端当前的字体显示状态不是默认字体显示状态时,处理器还用于:在第三时间段内获取至少两个第四加速度范围绝对值;当至少两个第四加速度范围绝对值中大于预设加速度范围绝对值阈值的个数不小于第二预设个数时,获取更新的抖动水平;根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态;和将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 7. A non-transitory computer storage medium storing a computer program for performing a method for a mobile terminal to set a font display state, the method comprising:acquiring, by the mobile terminal, a current jitter level;searching, by the mobile terminal, a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; andsetting, by the mobile terminal, a default font display state as the font display state corresponding to the current jitter level of the mobile terminal;wherein acquiring, by the mobile terminal, the current jitter level comprises:acquiring, by the mobile terminal, a first acceleration range absolute value within a first preset time period, and comparing the first acceleration range absolute value with a preset acceleration range absolute value threshold;acquiring, by the mobile terminal, at least two second acceleration range absolute values within a second preset time period when the first acceleration range absolute value is larger than the preset acceleration range absolute value threshold;acquiring, by the mobile terminal, a third acceleration range absolute value, which is larger than the preset acceleration range absolute value threshold, from each of the at least two second acceleration range absolute values; andacquiring, by the mobile terminal, an average value of the third acceleration range absolute values when a number of the third acceleration range absolute values is not smaller than a first preset number; andwherein searching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the current jitter level, to acquire the font display state corresponding to the current litter level of the mobile terminal, comprises:searching, by the mobile terminal, a correspondence relationship between an acceleration range absolute value and the font display state according to the average value, to acquire a font display state corresponding to the average value.(String), 7.一种非暂时性计算机存储介质,存储用于执行移动终端设置字体显示状态的方法的计算机程序,该方法包括:移动终端获取当前的抖动水平;移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态;和移动终端将默认的字体显示状态设置为移动终端当前抖动等级对应的字体显示状态;其中,移动终端获取当前抖动水平包括:移动终端获取第一预设时间段内的第一加速度范围绝对值,将第一加速度范围绝对值与预设加速度范围绝对值阈值进行比较;当第一加速度范围绝对值大于预设加速度范围绝对值阈值时,移动终端在第二预设时间段内获取至少两个第二加速度范围绝对值;移动终端分别从至少两个第二加速度范围绝对值中获取大于预设加速度范围绝对值阈值的第三加速度范围绝对值;和当第三加速度范围绝对值的个数不小于第一预设数量时,移动终端获取第三加速度范围绝对值的平均值;和其中,移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前乱码等级对应的字体显示状态,包括:移动终端根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取平均值对应的字体显示状态。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 8. The non-transitory computer storage medium according to claim 7, wherein acquiring, by the mobile terminal, the first acceleration range absolute value within the first preset time period comprises:acquiring, by the mobile terminal, a first original acceleration and a second original acceleration within the first preset time period;processing, by the mobile terminal, the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively;processing, by the mobile terminal, the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively; andperforming, by the mobile terminal, an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value.(String), 8.根据权利要求7所述的非暂时性计算机存储介质,其中移动终端获取第一预设时间段内的第一加速度范围绝对值包括:移动终端获取第一预设时间内的第一原始加速度和第二原始加速度;移动终端通过低通滤波器处理第一原始加速度和第二原始加速度,分别获取第一加速度中值和第二加速度中值;移动终端通过高通滤波器处理第一加速度中值和第二加速度中值,分别获取第一加速度和第二加速度;和移动终端对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184975(Integer), 9. The non-transitory computer storage medium according to claim 7, wherein when a current font display state of the mobile terminal is not the default font display state, the method further comprises:acquiring, by the mobile terminal, at least two fourth acceleration range absolute values within a third time period;acquiring, by the mobile terminal, an updated jitter level when a number of those larger than the preset acceleration range absolute value threshold among the at least two fourth acceleration range absolute values is not smaller than a second preset number; andsearching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; andsetting, by the mobile terminal, the current font display state as the font display state corresponding to the updated jitter level of the mobile terminal.(String), 9.根据权利要求7所述的非暂时性计算机存储介质,其中当移动终端当前的字体显示状态不是默认字体显示状态时,该方法还包括:移动终端在第三时间段内获取至少两个第四加速度范围绝对值;当所述至少两个第四加速度范围绝对值中大于预设加速度范围绝对值阈值的个数不小于第二预设个数时,移动终端获取更新后的抖动水平;和移动终端根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态;和移动终端将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184975(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of mobile terminals, and in particular to a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. BACKGROUND [0002]Currently, a mobile terminal is widely used in daily life of users. During the use of the mobile terminal, for example when a user is on a public transportation, the user cannot see clearly the content on a screen of the terminal because of an external jitter, thereby causing user asthenopia. SUMMARY [0003]In order to solve the technical problem described above, the disclosure discloses a mobile terminal, a method for the mobile terminal to set a font display state and a storage medium. [0004]The technical solution of the disclosure is implemented as follows. [0005]According to a first aspect, the disclosure discloses a method for a mobile terminal to set a font display state including: a mobile terminal acquires a current jitter level; the mobile terminal searches a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; and the mobile terminal sets a default font display state as the font display state corresponding to the current jitter level of the mobile terminal. [0006]According to a second aspect, the disclosure discloses a mobile terminal including an acquiring unit, a searching unit and a setting unit. The acquiring unit is arranged to acquire a current jitter level. The searching unit is arranged to search a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal. The setting unit is arranged to set a default font display state as the font display state corresponding to the current jitter level of the mobile terminal. [0007]According to a third aspect, the disclosure discloses a computer storage medium storing a computer program for performing the method for a mobile terminal to set a font display state as described above. [0008]The disclosure discloses a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. A jitter degree of a mobile terminal is acquired and a font state displayed on the screen of the mobile terminal is set according to the jitter degree. Thus a user can see the content on the screen of the mobile terminal clearly when external jitter exists, and the user asthenopia can be avoided. BRIEF DESCRIPTION OF THE DRAWINGS [0009]FIG. 1 is a flowchart of a method for a mobile terminal to set a font display state; [0010]FIG. 2 is a flowchart of a method for a mobile terminal to acquire a current jitter level; [0011]FIG. 3 is a structural diagram of a mobile terminal according to an embodiment of the disclosure; [0012]FIG. 4 is a block diagram of a mobile terminal according to an embodiment of the disclosure; [0013]FIG. 5 is a block diagram of font sizes according to an embodiment of the disclosure; [0014]FIG. 6 is a table showing acceleration with respect to time periods according to an embodiment of the disclosure. DETAILED DESCRIPTION [0015]The technical solution in embodiments of the disclosure will be described clearly and completely below with reference to the drawings in the embodiments of the disclosure. [0016]In the embodiments of the disclosure, a jitter degree of a mobile terminal is acquired at first, and then a font state displayed on the mobile terminal screen is correspondingly set according to the jitter degree. The font state may include, but not limited to a font size, a font type and a font color etc. The embodiments of the disclosure are described with the font size (in FIG. 5) being as an example. It will be understood that other font states may be set according to the technical solution in embodiments of the disclosure. [0017]Refer to FIG. 1 which shows a method for a mobile terminal to set a font display state according to an embodiment of the disclosure. The method may be used in a mobile terminal. For example, rather than limit, the mobile terminal may include, but not limited to a portable terminal device such as a phone, a tablet computer or a notebook computer etc. The method may include the following steps. [0018]At step S101, a mobile terminal acquires a current jitter level. It is important to note that the current jitter level is a basis for setting a font display state. Only if the jitter level is acquired accurately, the font state as which the font display state should be set can be determined. [0019]For example, as shown in FIG. 2, the mobile terminal acquiring the current jitter level may include steps S201-S204. [0020]At step S201, the mobile terminal acquires a first acceleration range absolute value within a preset first time period (in FIG. 6), and compares the first acceleration range absolute value with a preset acceleration range absolute value threshold. It is important to note that the step S201 is used for judging whether the jitter is caused by an external shake, which is a necessary condition for acquiring the current jitter level. Thus, the acceleration range absolute value threshold may be set to judge whether the jitter is caused by the external shake. [0021]Alternatively, the mobile terminal acquiring the first acceleration range absolute value within the preset first time period may include the following steps. Firstly, the mobile terminal detects and acquires two accelerations, i.e. a first original acceleration and a second original acceleration, within the preset first time period through a built-in acceleration sensor. Then, the first original acceleration and the second original acceleration are processed through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively. Then, the first acceleration median and the second acceleration median are processed through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively. At last, an absolute value computation is implemented on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value. [0022]It is important to note that the preset first time period T1 is a time interval between the two acceleration detections of the acceleration sensor, which may be set in default by a system, or set by a user. The first original acceleration and the second original acceleration detected and acquired by the acceleration sensor may be represented by a vector synthesis of acceleration components on three orthogonal coordinate axis. [0023]Generally, the first original acceleration and the second original acceleration may be interfered by gravity. Thus, preferably, in the embodiment, the first original acceleration and the second original acceleration are processed by the mobile terminal through the low-pass filter, then the first acceleration median and the second acceleration median are processed through the high-pass filter, to acquire the first acceleration and the second acceleration respectively. In such a way, the interference of the gravity may be eliminated. It will be understood that the first acceleration and the second acceleration may also be represented by the vector synthesis of acceleration components on three orthogonal coordinate axis. In the embodiment, the module value of the first acceleration can be represented as follows: a1=√{square root over (x12+y12+z12)} where, a1 is the module value of the first acceleration in a unit of m/s2, x1 is a component value of the first acceleration in x-axis direction, y1 is a component value of the first acceleration in y-axis direction, z1 is a component value of the first acceleration in z-axis direction, and units of x1, y1 and z1 are m/s2. [0024]Correspondingly, the module value of the second acceleration can be represented as follows: a2=√{square root over (x22+y22+z22)} where, a2 is the module value of the second acceleration in a unit of m/s2; x2 is a component value of the second acceleration in x-axis direction, y2 is a component value of the second acceleration in y-axis direction, z2 is a component value of the second acceleration in z-axis direction, and units of x2, y2 and z2 are m/s2. [0025]Preferably, the first acceleration range absolute value can be obtained through the following formula: a=|a2−a1| where, a is the first acceleration range absolute value, a1 is the module value of the first acceleration, a2 is the module value of the second acceleration, and units of a, a1 and a2 are m/s2. [0026]At step S202, when the first acceleration range absolute value is larger than the acceleration range absolute value threshold, the mobile terminal acquires at least two second acceleration range absolute values within a preset second time period (in FIG. 6). It is important to note that when the first acceleration range absolute value is larger than the acceleration range absolute value threshold, it may be determined that the jitter is caused by the external environment. Subsequently, it is needed to detect the duration time of the jitter. For example, in the embodiment, the mobile terminal acquires N second acceleration range absolute values within the second time period T2, where N≥2. It will be understood that the second acceleration range absolute values is acquired in the same way as the first acceleration range absolute value is acquired in S201, and will not be repeated here again. [0027]At step S203, the mobile terminal acquires a third acceleration range absolute value, which is larger than the acceleration range absolute value threshold, from the second acceleration range absolute values. In the embodiment, among N second acceleration range absolute values, the mobile terminals may count a number of the second acceleration range absolute values larger than the acceleration range absolute value threshold, to acquire M third acceleration range absolute values, where M≥1. [0028]At step S204, when the number of the third acceleration range absolute values is not smaller than a preset first number, the mobile terminal acquires an average value of the third acceleration range absolute values. It is important to note that in the embodiment, the mobile terminal compares M with the preset first number, and when M is smaller than the preset first number, it means that the jitter occurs occasionally or the jitter degree is not violent. At this point, there is no need for the mobile terminal to adjust the font display state. When M is not smaller than the preset first number, it means that the jitter is not occasional, but lasts for a certain time and has affected the reading of the user. At this point, the jitter degree is evaluated through the average value of the third acceleration range absolute values, which is a worst estimation of the jitter level. [0029]Alternatively, for those skilled in the art, it is possible to evaluate the jitter degree through the last acquired third acceleration range absolute value, which is not repeated here again. [0030]At step S102, the mobile terminal searches a correspondence relationship between the jitter level and the font display state according to the current jitter level, to acquire the font display state corresponding to the current jitter level of the mobile terminal. Preferably, the correspondence relationship between the jitter level and the font display state can be represented by a mapping table shown in table 1, or can be represented by other methods capable of expressing the correspondence relationship, which are not limited in the embodiment: [0031]TABLE 1Jitter levelFont display stateFirst jitter levelFirst font display stateSecond jitter levelSecond font display stateThird jitter levelThird font display state [0032]In the embodiment, it can be seen from S201-S204 that the jitter level is represented by the average value of the third acceleration range absolute values. Thus, preferably, the average value of the third acceleration range absolute values can be correspondingly divided into four sections, which are corresponding to the font display sizes one by one. Thus a correspondence relationship represented in Table 2 is obtained: [0033]TABLE 2Acceleration range absolute value(unit: m/s2)Font display size0-3Normal font4-6Middle-small font7-9Middle-large font10-12Large font [0034]At step S103, the mobile terminal sets a default font display state as the font display state corresponding to the current jitter level of the mobile terminal. [0035]It is important to note that after the end of the above process, the font display state is changed from the default font display state to a font display state corresponding to the current jitter level. However, in general, the jitter changes over time, and one jitter level will not last for a long time. In order to adapt to the changes, the font display state needs to be adjusted on time according to changes of the jitter level. [0036]Preferably, when the current font display state of the mobile terminal is not the default font display state, the method further includes: the mobile terminal acquiring at least two fourth acceleration range absolute values within a third time period; when the number of the fourth acceleration range absolute value(s) among at least two fourth acceleration range absolute values larger than the acceleration range absolute value threshold is not smaller than a second preset number, the mobile terminal acquiring an updated jitter level; the mobile terminal searching the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; and the mobile terminal setting the current font display state to the font display state corresponding to the updated jitter level of the mobile terminal. [0037]It will be understood that a level difference between the font display state corresponding to the updated jitter level of the mobile terminal and the current font display state can be level-skipped. For example, currently displayed normal font size can be set as a middle-large font or a large font, and it will not be repeated here again in the embodiment of the disclosure. [0038]The disclosure discloses a method for a mobile terminal to set a font display state. A jitter degree of the mobile terminal may be acquired and the font state displayed on the mobile terminal screen may be set according to the jitter degree. Thus a user can see the content on the mobile terminal screen clearly when external shake exists, and the user asthenopia can be avoided. [0039]Based on a technical concept which is the same as the above embodiment, as shown in FIG. 3, a structure of a mobile terminal 30 is provided in the embodiment of the disclosure. For example, rather than limit, the mobile terminal may include, but not limited to, a portable terminal device such as a phone, a tablet computer or a notebook computer etc. The mobile terminal 30 may include an acquiring unit 301, a searching unit 302 and a setting unit 303. The acquiring unit 301 is arranged to acquire a current jitter level. The searching unit 302 is arranged to search a correspondence relationship between a jitter level and a font display state according to the current jitter level acquired by the acquiring unit 301, to acquire a font display state corresponding to the current jitter level. The setting unit 303 is arranged to set a default font display state as the font display state corresponding to the current jitter level obtained by the searching unit 302. [0040]In an example, the acquiring unit 301 is arranged to: acquire a first acceleration range absolute value within a preset first time period, and compare the first acceleration range absolute value with a preset acceleration range absolute value threshold; when the first acceleration range absolute value is larger than the acceleration range absolute value threshold, acquire at least two second acceleration range absolute values within a preset second time period; and acquire a third acceleration range absolute value, which is larger than the acceleration range absolute value threshold, from the second acceleration range absolute values; and when the number of the third acceleration range absolute values is not smaller than a preset first number, acquire an average value of the third acceleration range absolute values. [0041]Correspondingly, the searching unit 302 is arranged to search a correspondence relationship between the acceleration range absolute value and the font display state according to the average value, to acquire the font display state corresponding to the average value. [0042]Preferably, the acquiring unit 301 is arranged to: acquire a first original acceleration and a second original acceleration within the first time period; process the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median respectively; process the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration respectively; and perform an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value. [0043]In an example, when the current font display state of the mobile terminal 30 is not the default font display state, the acquiring unit 301 is further arranged to: acquire at least two fourth acceleration range absolute values within a third time period; when the number of the forth acceleration range absolute value(s), which is larger than the acceleration range absolute value threshold, among the at least two fourth acceleration range absolute values is not smaller than a second preset number, acquire an updated jitter level. The searching unit 302 is further arranged to search the correspondence relationship between the jitter level and the font display state according to the updated jitter level acquired by the acquiring unit 301, to acquire the font display state corresponding to the updated jitter level of the mobile terminal. The setting unit 303 is further arranged to set the current font display state as the font display state corresponding to the updated jitter level acquired by the searching unit 302. [0044]The disclosure discloses a mobile terminal. A jitter degree of the mobile terminal is acquired and the font state displayed on the mobile terminal screen is set according to the jitter degree. Thus a user can see the content on the mobile terminal screen clearly when external shake exists, and the user asthenopia can be avoided. [0045]Those skilled in the art should understand that the embodiments of the disclosure can be provided as a method, a system or a computer program product. Thus, forms of hardware embodiments, software embodiments or embodiments integrating software and hardware can be adopted in the disclosure. Moreover, a form of the computer program product implemented on one or more computer available storage media (including, but not limited to, a disk memory, an optical memory and the like) containing computer available program codes can be adopted in the disclosure. [0046]The disclosure is described with reference to flowcharts and/or block diagrams of the method, the equipment (system) and the computer program product according to the embodiments of the disclosure. It should be understood that each flow and/or block in the flowcharts and/or the block diagrams and a combination of the flows and/or the blocks in the flowcharts and/or the block diagrams can be realized by computer program instructions. These computer program instructions can be provided for a general computer, a dedicated computer, an embedded processor or processors of other programmable data processing devices to generate a machine, so that an apparatus (in FIG. 4) for realizing functions assigned in one or more flows of the flowcharts and/or one or more blocks of the block diagrams is generated via instructions executed by the computers or the processors of the other programmable data processing devices. [0047]These computer program instructions can also be stored in a computer readable memory capable of guiding the computers or the other programmable data processing devices to work in a specific mode, so that a manufactured product including an instruction apparatus is generated via the instructions stored in the computer readable memory, and the instruction apparatus realizes the functions assigned in one or more flows of the flowcharts and/or one or more blocks of the block diagrams. [0048]These computer program instructions can also be loaded to the computers or the other programmable data processing devices, so that processing realized by the computers is generated by executing a series of operation steps on the computers or the other programmable devices, and therefore the instructions executed on the computers or the other programmable devices provide a step of realizing the functions assigned in one or more flows of the flowcharts and/or one or more blocks of the block diagrams. [0049]Correspondingly, the disclosure further discloses a computer storage medium, wherein a computer program is stored in it and the computer program is used for performing the method for the mobile terminal to set the font display state in embodiment of the disclosure. [0050]The above description is only the preferred embodiments of the disclosure, not intended to limit the scope of protection of the disclosure. INDUSTRIAL APPLICABILITY [0051]Based on each embodiment of the disclosure, by acquiring a jitter degree of a mobile terminal and setting a font state displayed on the mobile terminal screen according to the jitter degree, a user can see the content on the mobile terminal screen clearly when external shake exists, and the user asthenopia can be avoided.(String), 技术领域 [0001] 本发明涉及移动终端领域,尤其涉及一种移动终端、移动终端设置字体显示状态的方法及存储介质。 背景 [0002] 目前,移动终端广泛应用于用户的日常生活中。 在移动终端的使用过程中,例如用户在乘坐公共交通工具时,由于外界抖动,导致用户无法看清终端屏幕上的内容,从而导致用户视疲劳。 概括 [0003] 为解决上述技术问题,本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 [0004] 本发明的技术方案是这样实现的。 [0005] 第一方面,本发明公开了一种移动终端设置字体显示状态的方法,包括:移动终端获取当前抖动等级; 移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态; 移动终端设置默认的字体显示状态作为移动终端当前抖动等级对应的字体显示状态。 [0006] 第二方面,本发明公开了一种移动终端,包括获取单元、搜索单元和设置单元。 获取单元用于获取当前的抖动水平。 查找单元,用于根据当前抖动级别查找抖动级别与字体显示状态的对应关系,获取移动终端当前抖动级别对应的字体显示状态。 设置单元用于设置默认的字体显示状态作为移动终端当前抖动程度对应的字体显示状态。 [0007] 第三方面,本发明公开了一种计算机存储介质,存储有计算机程序,该计算机程序用于执行上述移动终端设置字体显示状态的方法。 [0008] 本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 获取移动终端的抖动程度,根据抖动程度设置移动终端屏幕显示的字体状态。 从而在存在外部抖动的情况下,用户可以清晰地看到移动终端屏幕上的内容,避免用户视疲劳。 附图的简要说明 [0009] 图1为移动终端设置字体显示状态的方法流程图; [0010] 图2为移动终端获取当前抖动水平的方法流程图; [0011] 图3是根据本发明实施例的移动终端的结构图; [0012] 图4是根据本发明一个实施例的移动终端的框图; [0013] 图5为根据本发明一实施例的字体大小的方块图。 [0014] 图6是显示根据本公开的实施例的相对于时间段的加速度的表格。 详细说明 [0015] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 [0016] 本发明实施例首先获取移动终端的抖动程度,然后根据抖动程度相应设置移动终端屏幕显示的字体状态。 字体状态可以包括但不限于字体大小、字体类型和字体颜色等。本发明实施例以字体大小(图5)为例进行说明。 可以理解,根据本发明实施例的技术方案还可以设置其他字体状态。 [0017]参见图1,其示出了根据本发明实施例的移动终端设置字体显示状态的方法。 该方法可以用于移动终端。 例如,但不限于,移动终端可以包括但不限于手机、平板电脑或笔记本电脑等便携式终端设备。该方法可以包括以下步骤。 [0018] 在步骤S 101 ,移动终端获取当前的抖动水平。 需要注意的是,当前抖动级别是设置字体显示状态的基础。 只有准确获取抖动水平,才能确定字体显示状态应设置为何种字体状态。 [0019] 例如,如图2所示,移动终端获取当前抖动水平可以包括步骤S 201 -S 204 . [0020] 在步骤S 201 、移动终端在预设的第一时间段内(图6)获取第一加速度范围绝对值,并将第一加速度范围绝对值与预设的加速度范围绝对值阈值进行比较。 重要的是要注意步骤S 201 用于判断抖动是否由外部抖动引起,是获取当前抖动水平的必要条件。 因此,可以通过设置加速度范围绝对值阈值来判断抖动是否由外部抖动引起。 [0021] 或者,移动终端在预设的第一时间段内获取第一加速度范围绝对值可以包括以下步骤。 首先,移动终端通过内置的加速度传感器在预设的第一时间段内检测并获取两个加速度,即第一原始加速度和第二原始加速度。 然后,第一原始加速度和第二原始加速度通过低通滤波器处理,分别获得第一加速度中值和第二加速度中值。 然后,第一加速度中值和第二加速度中值经过高通滤波器处理,分别得到第一加速度和第二加速度。 最后,对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。 [0022] 需要注意的是,预设的第一时间段T 1 为加速度传感器两次检测加速度之间的时间间隔,可以由系统默认设置,也可以由用户设置。 加速度传感器检测获取的第一原始加速度和第二原始加速度可以用三个正交坐标轴上的加速度分量的矢量合成来表示。 [0023] 通常,第一原始加速度和第二原始加速度可能受到重力的干扰。 因此,优选地,在本实施例中,第一原始加速度和第二原始加速度由移动终端通过低通滤波器处理,然后第一加速度中值和第二加速度中值通过高通滤波器处理,以 分别获取第一加速度和第二加速度。 这样,可以消除重力的干扰。 可以理解,第一加速度和第二加速度也可以用三个正交坐标轴上的加速度分量的矢量合成来表示。 在本实施例中,第一加速度的模值可以表示为: a 1 =√{对( x 1 2 +y 1 2 +z 1 2 )} 哪里,一个 1 是第一个加速度的模值,单位为m/s 2 , X 1 是x轴方向第一加速度的分量值,y 1 是y轴方向第一加速度的分量值,z 1 为z轴方向第一加速度的分量值,单位为x 1 , 是 1 和 1 是米/秒 2 . [0024]相应地,二次加速度的模值可以表示为: a 2 =√{对( x 2 2 +y 2 2 +z 2 2 )} 哪里,一个 2 是第二个加速度的模值,单位为m/s 2 ; X 2 是x轴方向第二个加速度的分量值,y 2 为y轴方向二次加速度分量值,z 2 为z轴方向二次加速度的分量值,单位为x 2 , 是 2 和 2 是米/秒 2 . [0025] 优选地,所述第一加速度范围绝对值可以通过以下公式得到: 一=|一个 2 −a 1 | 其中,a为第一加速度范围绝对值,a 1 是第一加速度的模值,a 2 为二次加速度的模值,单位为a,a 1 和一个 2 是米/秒 2 . [0026] 在步骤S 202 ,当第一加速度范围绝对值大于加速度范围绝对值阈值时,移动终端在预设的第二时间段内获取至少两个第二加速度范围绝对值(图6)。 需要说明的是,当第一加速度范围绝对值大于加速度范围绝对值阈值时,可以确定抖动是由外部环境引起的。 随后,需要检测抖动的持续时间。 例如,本实施例中,移动终端在第二时间段T内获取N个第二加速度范围绝对值。 2 ,其中 N≥2。 可以理解,第二加速度范围绝对值的获取方式与S中获取第一加速度范围绝对值的方式相同。 201 ,这里不再赘述。 [0027] 在步骤S 203 ,移动终端从第二加速度范围绝对值中获取大于加速度范围绝对值阈值的第三加速度范围绝对值。 本实施例中,移动终端可以统计N个第二加速度范围绝对值中大于加速度范围绝对值阈值的第二加速度范围绝对值的个数,得到M个第三加速度范围绝对值,M≥1。 [0028] 在步骤S 204 ,当第三加速度范围绝对值的个数不小于预设的第一数量时,移动终端获取第三加速度范围绝对值的平均值。 需要说明的是,在本实施例中,移动终端将M与预设的第一数进行比较,当M小于预设的第一数时,表示抖动是偶发的或者抖动程度不剧烈。 此时,移动端无需调整字体显示状态。 当M不小于预设的第一个数时,说明抖动不是偶然的,而是持续了一定时间,已经影响了用户的阅读。 此时,通过第三加速度范围绝对值的平均值来评估抖动程度,这是对抖动水平的最差估计。 [0029] 或者,对于本领域的技术人员,也可以通过上次获取的第三加速度范围绝对值来评价抖动程度,在此不再赘述。 [0030] 在步骤S 102 ,移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态。 优选地,抖动级别与字体显示状态的对应关系可以用表1所示的映射表来表示,也可以用其他能够表达该对应关系的方法来表示,本实施例对此不作限定: [0031] 表格1 抖动水平 字体显示状态 第一抖动水平 第一个字体显示状态 第二抖动水平 第二字体显示状态 第三抖动等级 第三种字体显示状态 [0032] 在实施例中,从S可以看出201 -S 204 抖动水平由第三加速度范围绝对值的平均值表示。 因此,优选地,第三加速度范围绝对值的平均值可以对应地分为四个部分,与字体显示大小一一对应。 从而得到如表2所示的对应关系: [0033] 表 2 加速度范围绝对值 (单位:米/秒 2 ) 字体显示大小 0-3 普通字体 4-6 中小字体 7-9 中大字体 10-12 大字体 [0034] 在步骤S 103 ,移动终端设置默认的字体显示状态作为移动终端当前抖动等级对应的字体显示状态。 [0035] 需要说明的是,在上述过程结束后,字体显示状态由默认的字体显示状态变为当前抖动级别对应的字体显示状态。 但是,一般情况下,抖动会随着时间的推移而变化,一个抖动级别不会持续很长时间。 为了适应变化,需要根据抖动程度的变化及时调整字体显示状态。 [0036] 优选地,当移动终端当前的字体显示状态不是默认字体显示状态时,该方法还包括: 移动终端在第三时间段内获取至少两个第四加速度范围绝对值; 当至少两个第四加速度范围绝对值中大于加速度范围绝对值阈值的第四加速度范围绝对值的个数不小于第二预设个数时,移动终端获取更新的抖动水平; 移动终端根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态; 移动终端将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。 [0037] 可以理解,移动终端更新后的抖动等级对应的字体显示状态与当前字体显示状态之间的等级差可以跳级。 例如,当前显示的正常字体大小可以设置为中大号字体或大号字体,本发明实施例在此不再赘述。 [0038] 本发明公开了一种移动终端设置字体显示状态的方法。 可以获取移动终端的抖动程度,根据抖动程度设置移动终端屏幕显示的字体状态。 从而在有外界晃动的情况下,用户可以清晰的看到移动终端屏幕上的内容,避免用户视疲劳。 [0039] 基于与上述实施例相同的技术构思,如图3所示,移动终端的结构 30 在本发明实施例中提供。 例如,但不限于,移动终端可以包括但不限于手机、平板电脑或笔记本电脑等便携式终端设备。移动终端 30 可能包括收购单位 301 , 一个搜索单元 302 和一个设置单元 303 . 收单单位 301 被布置为获取当前抖动水平。 搜寻单位 302 用于根据获取单元获取的当前抖动等级查找抖动等级与字体显示状态的对应关系 301 , 获取当前抖动等级对应的字体显示状态。 设定单位 303 设置为设置默认字体显示状态为搜索单元获取的当前抖动级别对应的字体显示状态 302 . [0040] 在一个例子中,获取单元 301用于在预设的第一时间段内获取第一加速度范围绝对值,并将第一加速度范围绝对值与预设的加速度范围绝对值阈值进行比较; 当第一加速度范围绝对值大于加速度范围绝对值阈值时,在预设的第二时间段内获取至少两个第二加速度范围绝对值; 从第二加速度范围绝对值中获取大于加速度范围绝对值阈值的第三加速度范围绝对值。 当第三加速度范围绝对值的数量不小于预设的第一数量时,获取第三加速度范围绝对值的平均值。 [0041] 相应地,搜索单元 302 用于根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取该平均值对应的字体显示状态。 [0042] 优选地,获取单元 301 用于在第一时间段内获取第一原始加速度和第二原始加速度; 通过低通滤波器处理第一原始加速度和第二原始加速度,分别获得第一加速度中值和第二加速度中值; 通过高通滤波器对第一加速度中值和第二加速度中值进行处理,分别得到第一加速度和第二加速度。 对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。 [0043] 示例中,当移动终端当前字体显示状态 30 不是默认字体显示状态,获取单元 301 还用于在第三时间段内获取至少两个第四加速度范围绝对值; 当至少两个第四加速度范围绝对值中大于加速度范围绝对值阈值的第四加速度范围绝对值的个数不小于第二预设个数时,获取更新后的抖动水平。 搜寻单位 302 还用于根据获取单元获取的更新后的抖动等级,查找抖动等级与字体显示状态的对应关系 301 , 获取更新后的移动终端抖动等级对应的字体显示状态。 设定单位 303 还用于将当前字体显示状态设置为搜索单元获取的更新后的抖动等级对应的字体显示状态 302 . [0044] 本发明公开了一种移动终端。 获取移动终端的抖动程度,根据抖动程度设置移动终端屏幕显示的字体状态。 从而在有外界晃动的情况下,用户可以清晰的看到移动终端屏幕上的内容,避免用户视疲劳。 [0045] 本领域的技术人员应该理解,本公开的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本发明可以采用硬件实施例、软件实施例或软硬件结合的实施例的形式。 此外,本发明可采用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光存储器等)上实现计算机可用程序代码的计算机程序产品的形式。 [0046]本发明是参照根据本发明实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述的。 应当理解,流程图和/或框图中的每个流程和/或框以及流程图和/或框图中的流程和/或框的组合可以由计算机程序指令实现。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或其他可编程数据处理设备的处理器生成机器,从而实现一个或多个流程分配的功能的装置(图4) 流程图的一部分和/或框图的一个或多个块经由由计算机或其他可编程数据处理设备的处理器执行的指令生成。 [0047] 这些计算机程序指令也可以存储在能够引导计算机或其他可编程数据处理设备以特定模式工作的计算机可读存储器中,从而通过存储在计算机中的指令生成包括指令装置的制造产品 可读存储器,指令装置实现流程图的一个或多个流程和/或方框图的一个或多个块中指定的功能。 [0048] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备中,使得计算机实现的处理是通过在计算机或其他可编程设备上执行一系列操作步骤而产生的,因此在计算机或其他可编程数据处理设备上执行的指令 计算机或其他可编程设备提供实现在流程图的一个或多个流程和/或框图的一个或多个块中分配的功能的步骤。 [0049] 相应地,本发明还公开了一种计算机存储介质,其中存储有计算机程序,该计算机程序用于执行本发明实施例中移动终端设置字体显示状态的方法。 [0050] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。 工业实用性 [0051] 基于本发明各实施例,通过获取移动终端的抖动程度,并根据抖动程度设置移动终端屏幕显示的字体状态,使得用户在存在外部抖动时,能够清晰的看到移动终端屏幕上的内容。 ,可以避免用户疲劳。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104320534A(String), CN104320534B(String), US10469652B2(String), US20190158651A1(String), WO2015131604A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104320534A(String), CN104320534B(String), US10469652B2(String), US20190158651A1(String), WO2015131604A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10469652B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104320534A(String), CN104320534B(String), US10469652B2(String), US20190158651A1(String), WO2015131604A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270657(Integer), CN104320534A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270657(Integer), CN104320534B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270657(Integer), US10469652B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270657(Integer), US20190158651A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270657(Integer), WO2015131604A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10469652B2(String), US10469652B2(String), 1572883200(Integer), 270657(Integer), 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184975(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184975(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184975(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184975(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9455952B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for setting functional module name of mobile terminal, and mobile terminal(String), 一种设置移动终端功能模块名称的方法及移动终端(String), US9455952B2(String), The embodiment of the present document discloses a method for setting functional module names of a mobile terminal, which includes: setting the name of a mobile terminal; according to the set name of the mobile terminal, generating functional module names corresponding to functional modules in the mobile terminal. The embodiment of the present document further discloses a mobile terminal. The solution disclosed in the embodiment of the present document can be used to automatically modify the names of various functional modules in a mobile terminal by setting the name of the mobile terminal, thus reducing the user's operation steps and also improving the user experience.(String), 本发明实施例公开了一种移动终端功能模块名称设置方法,包括:设置移动终端名称; 根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称。 本发明实施例还公开了一种移动终端。 采用本发明实施例公开的方案,可以通过设置移动终端的名称,自动修改移动终端中各个功能模块的名称,从而减少了用户的操作步骤,也提高了用户体验。(String), US14/761949(String), 1372262400(Integer), US9455952B2(String), 1474905600(Integer), 1474905600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 16(Integer), CN102281350A | CN102469453A | EP1838047A2 | US20060276133A1 | US20090181653A1 | US20110019599A1 | US20110117849A1 | US20120164947A1 | US20120315839A1 | US20140120906A1 | US20140129652A1 | US20150373179A1 | US7801485B2 | US8126399B1 | US8626233B2 | WO2007027660A2(String), 8(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184976(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.392 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\4e19e3129e7a436e9145634e6bc8e97d.png(String), 184976(Integer), 4e19e3129e7a436e9145634e6bc8e97d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for setting functional module name of mobile terminal, and mobile terminal(String), 一种设置移动终端功能模块名称的方法及移动终端(String), US9455952B2(String), The embodiment of the present document discloses a method for setting functional module names of a mobile terminal, which includes: setting the name of a mobile terminal; according to the set name of the mobile terminal, generating functional module names corresponding to functional modules in the mobile terminal. The embodiment of the present document further discloses a mobile terminal. The solution disclosed in the embodiment of the present document can be used to automatically modify the names of various functional modules in a mobile terminal by setting the name of the mobile terminal, thus reducing the user's operation steps and also improving the user experience.(String), 本发明实施例公开了一种移动终端功能模块名称设置方法,包括:设置移动终端名称; 根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称。 本发明实施例还公开了一种移动终端。 采用本发明实施例公开的方案,可以通过设置移动终端的名称,自动修改移动终端中各个功能模块的名称,从而减少了用户的操作步骤,也提高了用户体验。(String), US14/761949(String), 1372262400(Integer), US9455952B2(String), 1474905600(Integer), 1474905600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 16(Integer), CN102281350A | CN102469453A | EP1838047A2 | US20060276133A1 | US20090181653A1 | US20110019599A1 | US20110117849A1 | US20120164947A1 | US20120315839A1 | US20140120906A1 | US20140129652A1 | US20150373179A1 | US7801485B2 | US8126399B1 | US8626233B2 | WO2007027660A2(String), \20230420\4e19e3129e7a436e9145634e6bc8e97d.png(String), 8(Integer), 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 1. A method for setting functional module names of a mobile terminal, the method comprising:setting a name of the mobile terminal;according to the name of the mobile terminal, generating functional module names corresponding to various functional modules in the mobile terminal;displaying the functional module names;prompting a user to confirm the functional module names; andaccording to a current state of each functional module, saving the corresponding functional module name of each functional module, wherein the current state comprises a non-startup state, a turned-off state and a turned-on state.(String), 1.一种设置移动终端功能模块名称的方法,该方法包括:设置移动终端名称;根据移动终端的名称,生成移动终端中各个功能模块对应的功能模块名称;显示功能模块名称;提示用户确认功能模块名称;和根据每个功能模块的当前状态,保存每个功能模块对应的功能模块名称,其中,当前状态包括未启动状态、关闭状态和开启状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 2. The method of claim 1, wherein said according to a current state of each functional module, saving the corresponding functional module name of each functional module comprises:when the current state of the functional module is the non-startup state, saving the functional module name corresponding to the functional module into a database;when the current state of the functional module is the turned-off state, saving the functional module name corresponding to the functional module into a configuration file of the functional module;when the current state of the functional module is the turned-on state, replacing and saving the functional module name corresponding to the functional module into the configuration file of the functional module.(String), 2.如权利要求1所述的方法,其中所述根据各功能模块的当前状态,保存各功能模块对应的功能模块名称包括:当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中;当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中;当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换保存到功能模块的配置文件中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 3. The method of claim 1, wherein before executing said generating functional module names corresponding to various functional modules in the mobile terminal according to the set name of the mobile terminal, the method further comprises:judging a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 3.如权利要求1所述的方法,其中在执行所述根据设置的移动终端名称生成移动终端中各个功能模块对应的功能模块名称之前,该方法还包括:判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 4. The method of claim 2, wherein before executing said generating functional module names corresponding to various functional modules in the mobile terminal according to the set name of the mobile terminal, the method further comprises:judging a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 4.如权利要求2所述的方法,其中在执行所述根据设置的移动终端名称生成移动终端中各个功能模块对应的功能模块名称之前,该方法还包括:判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 5. A mobile terminal, comprising a processor and a storage device, wherein the storage device stores processor-executable programs with following modules:a setting module, configured to: set a name of a mobile terminal; anda name generating module, configured to: according to the name of the mobile terminal, generate functional module names corresponding to various functional modules in the mobile terminal;a displaying module, configured to: display the functional module names;a prompting module, configured to: prompt a user to confirm the functional module names; anda saving module, configured to: according to a current state of each functional module, save the corresponding functional module name of each functional module, wherein the current state comprises a non-startup state, a turned-off state and a turned-on state.(String), 5.移动终端,包括处理器和存储设备,其中存储设备存储具有以下模块的处理器可执行程序:设置模块,用于设置移动终端的名称;和名称生成模块,用于根据移动终端的名称,生成移动终端中各个功能模块对应的功能模块名称;显示模块,用于显示功能模块名称;提示模块,用于提示用户确认功能模块名称;和保存模块,用于根据各功能模块的当前状态,保存各功能模块对应的功能模块名称,其中,当前状态包括非开机状态、关机状态和开机状态.6.如权利要求5所述的移动终端,其中保存模块配置为:当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中;当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中;当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换并保存到功能模块的配置文件中。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 6. The mobile terminal of claim 5, wherein the saving module is configured to:when the current state of the functional module is the non-startup state, save the functional module name corresponding to the functional module into a database;when the current state of the functional module is the turned-off state, save the functional module name corresponding to the functional module into a configuration file of the functional module;when the current state of the functional module is the turned-on state, replace and save the functional module name corresponding to the functional module into the configuration file of the functional module.(String), 7.如权利要求5所述的移动终端,还包括:判断模块,用于判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 7. The mobile terminal of claim 5, further comprising:a judging module, configured to: judge a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 8.如权利要求6所述的移动终端,还包括:判断模块,用于判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184976(Integer), 8. The mobile terminal of claim 6, further comprising:a judging module, configured to: judge a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184976(Integer), TECHNICAL FIELD [0001]The present document relates to the field of mobile communication technologies, and more particularly, to a method for setting functional module names of a mobile terminal and the mobile terminal. BACKGROUND OF THE RELATED ART [0002]Currently, technologies such as Bluetooth, portable wireless fidelity (WIFI) hot spots, WIFI Direct have been more widely used in high-end mobile terminals, and the Bluetooth and the portable WIFI hotspot have already been common features. Through the Bluetooth, users can easily exchange and share information with various types of equipment; through the portable WIFI hotspot, users can share the mobile network of the mobile terminal with other equipment, and through the WIFI Direct, the users can conveniently achieve directly connecting, transferring data, or sharing applications with other equipment. [0003]However, because currently the mobile terminals usually identify Bluetooth devices with default device names, and use a default value or a random value to identify WIFI hot spots and WIFI Direct devices, and no matter whether to uniformly use an identification or randomly generate an identification, it causes disorder for the user to distinguish, because when a user uses the abovementioned function, usually the user is just for one person, and then connects to his device, but rarely knows what the device name of the other party is. In order to identify the user's device, the current practice is that, in modules such as Bluetooth, portable WIFI hotspot, WIFI Direct, the user can individually modify the name of each module. However, the operation of this method has some complexity and limitations. SUMMARY OF THE INVENTION [0004]The embodiment of the present document provides a method for setting functional module names of a mobile terminal and the mobile terminal, and it is designed to automatically modify the names of various functional modules in a mobile terminal to reduce the user's operation steps and enhance the user experience. [0005]The present document provides a method for setting functional module names of a mobile terminal, comprising: [0006]setting the name of a mobile terminal; [0007]according to the set name of the mobile terminal, generating functional module names corresponding to functional modules in the mobile terminal. [0008]Preferably, after executing said generating the functional module names corresponding to the functional modules in the mobile terminal, it further comprises: [0009]displaying the functional module names. [0010]Preferably, after executing said displaying the functional module names, it further comprises: [0011]prompting a user to confirm the functional module names. [0012]Preferably, after executing said prompting the user to confirm the functional module names, it further comprises: [0013]according to the current states of the functional modules, saving the functional module names; the current states of the functional modules comprise non-startup state, turned-off state and turned-on state. [0014]Preferably, said saving the functional module names according to the current states of the functional modules comprises: [0015]when the current state of the functional module is the non-startup state, saving the functional module name corresponding to the functional module into a database; [0016]when the current state of the functional module is the turned-off state, saving the functional module name corresponding to the functional module into a configuration file of the functional module; [0017]when the current state of the functional module is the turned-on state, replacing and saving the functional module name corresponding to the functional module into the configuration file of the functional module. [0018]Preferably, before executing said generating functional module names corresponding to various functional modules in the mobile terminal in accordance with the set name of the mobile terminal, it further comprises: [0019]judging the condition of the mobile terminal supporting the functional modules; the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0020]The embodiment of the present document further provides a mobile terminal, comprising: [0021]a setting module, configured to: set the name of a mobile terminal; [0022]a name generating module, configured to: according to the set name of the mobile terminal, generate functional module names corresponding to functional modules in the mobile terminal. [0023]Preferably, the mobile terminal further comprises: [0024]a displaying module, which is configured to: display the functional module names. [0025]Preferably, the mobile terminal further comprises: [0026]a prompting module, configured to: prompt a user to confirm the functional module names. [0027]Preferably, the mobile terminal further comprises: [0028]a saving module, which is configured to: according to the current states of the functional modules, save the functional module names; the current states of the functional modules comprise a non-startup state, a turned-off state and a turned-on state. [0029]Preferably, the saving module is configured to: [0030]when the current state of the functional module is the non-startup state, save the functional module name corresponding to the functional module into a database; [0031]when the current state of the functional module is the turned-off state, save the functional module name corresponding to the functional module into a configuration file of the functional module; [0032]when the current state of the functional module is the turned-on state, replace and save the functional module name corresponding to the functional module into the configuration file of the functional module. [0033]Preferably, the mobile terminal further comprises: [0034]a judging module, configured to: judge the condition of the mobile terminal supporting the functional modules; the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0035]In the embodiment of the present document, it sets the name of a mobile terminal and then generates functional module names corresponding to functional modules in the mobile terminal according to the set name of the mobile terminal. By setting the name of the mobile terminal, the names of various functional modules in the mobile terminal can be automatically modified, thus reducing the user's operation steps and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a flow chart of a first embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0037]FIG. 2 is a flow chart of a second embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0038]FIG. 3 is a flow chart of a third embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0039]FIG. 4 is a flow chart of a fourth embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0040]FIG. 5 is a flow chart of saving the functional module names in the method for setting functional module names of a mobile terminal in accordance with the present document; [0041]FIG. 6 is a flow chart of a fifth embodiment of the method for setting the functional module names of a mobile terminal in accordance with the present document; [0042]FIG. 7 is a schematic diagram of the structure of a first embodiment of a mobile terminal in accordance with the present document; [0043]FIG. 8 is a schematic diagram of the structure of a second embodiment of the mobile terminal in accordance with the present document; [0044]FIG. 9 is a schematic diagram of the structure of a third embodiment of the mobile terminal in accordance with the present document; [0045]FIG. 10 is a schematic diagram of the structure of a fourth embodiment of the mobile terminal in accordance with the present document; [0046]FIG. 11 is a schematic diagram of the structure of a fifth embodiment of the mobile terminal in accordance with the present document. [0047]Object implementations, functions and features and advantages of the present document will be further described in conjunction with the embodiments and with reference to the accompanying drawings. PREFERRED EMBODIMENTS OF THE INVENTION [0048]It should be understood that the specific embodiments described herein are only for explaining the present document and are not intended to limit the present document. In the case of no conflict, embodiments and features in the embodiments of the present application can be combined with each other. [0049]The embodiment of the present document provides a method for setting functional module names of a mobile terminal, which automatically generates corresponding functional module names for various functional modules supported by the mobile terminal by setting the name of the mobile terminal, and displays the functional module names to the user for the user to confirm whether to save the names or not, and the user can also modify the functional module names by himself/herself. [0050]Referring to FIG. 1FIG. 1 is a flow chart of a first embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0051]The method for setting functional module names of a mobile terminal provided in the present embodiment comprises: [0052]in step S10, it is to set the name of a mobile terminal; [0053]In the present embodiment, an entry can be added in the setting module of the mobile terminal for a user to enter the name of the mobile terminal, and the user can set the name of the mobile terminal through the entry. Before setting the functional module names corresponding to various functional modules in the mobile terminal, the name of the mobile terminal is first set. The name of the mobile terminal can be set by the user by himself/herself, which can play a role of identifying the user's mobile terminal device, and in the present embodiment, in order to ensure that it has a different name from the ones that other surrounding mobile terminals have, preferably the user's full name is used as the name of mobile terminal. [0054]In step S20, according to the set name of the mobile terminal, it is to generate a functional module name corresponding to the functional module in the mobile terminal; [0055]after the name of the mobile terminal is set, functional module names corresponding to various functional modules are automatically generated according to the functional modules supported by the mobile terminal as well as the name of the mobile terminal. In the present embodiment, a functional module name can be the set name of the mobile terminal plus the function name of the functional module. [0056]In the embodiment of the present document, it sets the name of a mobile terminal and then generates functional module names corresponding to functional modules in the mobile terminal according to the set name of the mobile terminal. By setting the name of the mobile terminal, the names of various functional modules in the mobile terminal can be automatically modified, thus reducing the user's operation steps and improving the user experience. [0057]Refer to FIG. 2, and FIG. 2 is a flow chart of a second embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0058]Based on the abovementioned embodiment, after executing the step S20, the method further comprises: [0059]in step S30, it is to display the functional module names. [0060]After functional module names corresponding to various functional modules are automatically generated according to the name of the mobile terminal, the generated functional module names are displayed to the user through an interface, and in the present embodiment, the respective functional modules and the corresponding functional module names can be listed in the interface of the mobile terminal. [0061]After functional module names corresponding to various functional modules are automatically generated according to the set name of the mobile terminal, the generated functional module names are displayed to the user, so as to provide a foundation for the user to confirm the functional module names. [0062]Refer to FIG. 3, and FIG. 3 is a flow chart of a third embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0063]Based on the abovementioned embodiment, after performing the step S30, the method further comprises: [0064]in step S40, it is to prompt the user to confirm the functional module names. [0065]The generated functional module names are displayed in the interface of the mobile terminal, meanwhile, a confirmation button is set for the user to confirm the functional module names corresponding to various functional modules, prompting the user to perform confirming. In this case, if the user accepts the automatically generated functional module names, then the user clicks the confirmation; and if the user does not accept them, then the user can make modifications by himself/herself and click the confirmation after modifications, thus completing the setting of names of functional modules of the mobile terminal. [0066]The generated functional module names are displayed, and the user is prompted to confirm the functional module names displayed in the interface, thus ensuring that the names of various functional modules of the mobile terminal can be automatically modified by setting the name of the mobile terminal. [0067]Refer to FIG. 4, and FIG. 4 is a flow chart of a fourth embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0068]Based on the abovementioned embodiment, after performing the step S40, the method further comprises: [0069]in step S50, it is to save the functional module names according to the current states of the functional modules; the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state. [0070]After the user accepts the displayed and automatically generated functional module names and clicks the confirmation, or after the user modifies the functional module names by himself/herself and clicks the confirmation, at this time, it is to judge the current states of the functional modules, and according to the difference of the current states, perform different savings on the functional module names. In this embodiment, the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state, wherein the non-startup state refers to that the functional module of the mobile terminal has never been started up in these circumstances that it was out of the factory, or restored with the factory settings, or upgraded; the turned-off state refers to that the functional module was started up but it is currently in the turned-off state; and the turned-on state refers to that the functional module is currently in the turned-on state. [0071]After the user confirms the automatically generated functional module names or the user modifies the functional module names by himself/herself, according to the current states of the functional modules, the functional module names are saved, to facilitate finding and using the functional module names when starting up the functional modules next time, which provides a premise guarantee for reducing the user's operation steps. [0072]Refer to FIG. 5, and FIG. 5 is a flow chart of saving the functional module names in the method for setting functional module names of a mobile terminal in accordance with the present document. [0073]Based on the abovementioned embodiment, in step S50, when the current state of a functional module is the non-startup state, proceed to step S51; when the current state of a functional module is the turned-off state, proceed to step S52; when the current state of a functional module is the turned-on state, proceed to step S53. [0074]In step S51, it is to save the functional module name corresponding to the functional module into the database; [0075]when determining that the current state of a functional module is the non-startup state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has not been generated, then the functional module name is stored in the database of the mobile terminal. In this embodiment, a record is generated according to the functional module name, and the record takes the functional module as the key and the functional module name as the value, and the record is saved in the database. After the functional module is started up, the database is searched to judge whether there is a record which takes the functional module as the key and the functional module name as the value therein, and if yes, the functional module name in the record is displayed and written into the configuration file of the functional module, then the value is cleared, and when the functional module is turned on next time, the value in the database will not be used again, but the configuration file is directly searched and the value therein is used. [0076]In step S52, it is to save the functional module name corresponding to a functional module into the configuration file of the functional module; [0077]when determining that the current state of a functional module is the turned-off state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has been generated, and at this time, it is to directly save the functional module name into the configuration file. [0078]In step S53, it is to replace and save the functional module name corresponding to the functional module into the configuration file of the functional module. [0079]When determining that the current state of a functional module is the turned-on state, because various functional modules in the mobile terminal have corresponding processing procedures of changing names, when the current state of a functional module is the turned-on state, it is to first trigger the processing procedure of changing names of the functional module, and replace the name previously stored in the configuration file with the currently generated functional module name and save the currently generated functional module name in the configuration file. [0080]When the current state of a functional module is the non-startup state, the turned-off state or the turned-on state, it is to respectively save the functional module name corresponding to the functional module into the database, or into the configuration file, or replace and save it into the configuration file, which ensures to reduce the user's operation steps and enhance the user experience. [0081]Refer to FIG. 6, and FIG. 6 is a flow chart of a fifth embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0082]Based on the first embodiment of the method for setting the functional module name of a mobile terminal in the present document, before performing the step S20, it further comprises: [0083]in step S60, it is to judge the condition of the mobile terminal supporting the functional modules; and the functional modules comprise at least a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0084]Before generating functional module names corresponding to the functional modules according to the set name of the mobile terminal, it is to first judge the functional modules supported by the mobile terminal, that is, judge which functional modules are supported by the mobile terminal. In this embodiment, the functional modules comprise a Bluetooth module, a WIFI hotspot module, a WIFI Direct module and other modules, and when the mobile terminal communicates with other mobile terminals through these modules, it needs to provide a name which can be identified by the other party. [0085]After setting the name of mobile terminal, it needs to, before generating functional module names corresponding to various functional modules of the mobile terminal according to the name, first judge which functional modules are supported by the mobile terminal, so as to generate functional module names of these functional modules, thus providing the foundation for automatically modifying the names of various functional modules of the mobile terminal according to the name of the mobile terminal. [0086]Refer to FIG. 7, and FIG. 7 is a schematic diagram of the structure of a first embodiment of the mobile terminal in accordance with the present document. [0087]The mobile terminal provided in the present embodiment comprises: [0088]a setting module 10, which is configured to: set the name of the mobile terminal; [0089]a name generating module 20, configured to: according to the set name of the mobile terminal, generate functional module names corresponding to the functional modules in the mobile terminal; [0090]In the present embodiment, an entry can be added in the setting module of the mobile terminal for the user to enter the name of the mobile terminal, and the user can set the name of the mobile terminal through the entry. Before setting functional module names corresponding to various functional modules in the mobile terminal, the name of the mobile terminal is firstly set through the setting module 10. The name of the mobile terminal is set by the user by himself/herself, which can play a role of identifying the user's mobile terminal device, and in this embodiment, in order to ensure that the name is different from the ones that other surrounding mobile terminals have, preferably the user's full name is used as the name of the mobile terminal. [0091]After setting the name of the mobile terminal, the name generating module 20 automatically generates functional module names corresponding to various functional modules according to the functional modules supported by the mobile terminal as well as the name of the mobile terminal. In the present embodiment, a functional module name can be set as the name of the mobile terminal plus the function name of the functional module. [0092]In the embodiment of the present document, it sets the name of a mobile terminal and then generates functional module names corresponding to functional modules in the mobile terminal according to the set name of the mobile terminal. By setting the name of the mobile terminal, the names of various functional modules in the mobile terminal can be automatically modified, thus reducing the user's operation steps and improving the user experience. [0093]Refer to FIG. 8, and FIG. 8 is a schematic diagram of the structure of a second embodiment of the mobile terminal in accordance with the present document. [0094]Based on the abovementioned embodiment, the mobile terminal further comprises: [0095]a displaying module 30, configured to: display the functional module names. [0096]After functional module names corresponding to various functional modules according to the name of the mobile terminal are automatically generated, the displaying module 30 displays the generated functional module names to the user through the interface, and in this embodiment, various functional modules and the corresponding functional module names may be listed in the interface of the mobile terminal. [0097]After the functional module names corresponding to various functional modules according to the set name of the mobile terminal are automatically generated, the generated functional module names are displayed to the user, so as to provide the foundation for the user to confirm the functional module names. [0098]Refer to FIG. 9, and FIG. 9 is a schematic diagram of the structure of a third embodiment of the mobile terminal in accordance with the present document. [0099]Based on the abovementioned embodiment, the mobile terminal further comprises: [0100]a prompting module 40, configured to: prompt the user to confirm the functional module names. [0101]the generated functional module names are displayed in the interface of the mobile terminal, meanwhile the prompting module 40 is provided with a confirmation button for the user to confirm the functional module names corresponding to various functional modules, prompting the user to perform confirming. In this case, if the user accepts the automatically generated functional module names, then the user clicks the confirmation; and if the user does not accept the names, the user can make modifications by himself/herself and then click the confirmation after the modification, so as to complete the setting of names of the functional modules of the mobile terminal. [0102]Displaying the generated functional module names and prompting the user to confirm the functional module names displayed in the interface can further ensure that the names of various functional modules of the mobile terminal can be automatically modified by setting the name of the mobile terminal. [0103]Refer to FIG. 10, and FIG. 10 is a schematic diagram of the structure of a fourth embodiment of the mobile terminal in accordance with the present document. [0104]Based on the abovementioned embodiment, the mobile terminal further comprises: [0105]a saving module 50, which is configured to: according to the current states of the functional modules, save the functional module names; the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state. [0106]After the user accepts the displayed and automatically generated functional module names and clicks the confirmation, or after the user modifies the functional module names by himself/herself and clicks the confirmation, at this time, the saving module 50 judges the current states of the functional modules, and perform different savings on the functional module names according to the difference of the current states. In this embodiment, the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state, wherein the non-startup state refers to that the functional module of the mobile terminal has never been started up in these circumstances that it was out of the factory, or restored with the factory settings, or upgraded; the turned-off state refers to that the functional module was started up but it is currently in the turned-off state; and the turned-on state refers to that the functional module is currently in the turned-on state. [0107]After the user confirms the automatically generated functional module names, or the user modifies the functional module names by himself/herself, the functional module names are saved according to the current states of the functional modules, so as to facilitate finding and using the functional module names when starting up the functional modules next time, which provides a premise guarantee for reducing the user's operation steps. [0108]In the abovementioned embodiment, the saving module 50 is configured to: [0109]when the current state of a functional module is the non-startup state, save the functional module name corresponding to the functional module into a database; [0110]when the current state of a functional module is the turned-off state, save the functional module name corresponding to the functional module into a configuration file of the functional module; [0111]when the current state of a functional module is the turned-on state, replace and save the functional module name corresponding to the functional module into the configuration file of the functional module. [0112]when determining that the current state of a functional module is the non-startup state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has not been generated, at this time, the functional module name is stored in the database of the mobile terminal. In this embodiment, a record is generated according to the functional module name, and the record takes the functional module as the key and the functional module name as the value, and the record is saved in the database. When the functional module is started up, it is to search in the database to judge whether there is a record which takes the functional module as the key and the functional module name as the value therein, and if yes, display the functional module name in the record and write it into the configuration file of the functional module, and then clear the value, and when the functional module is started up next time, the value in the database will not be used again, and the configuration file is directly searched and the value therein is used. [0113]When determining that the current state of a functional module is the turned-off state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has been generated, at this time, it is to directly save the functional module name in the configuration file. [0114]When determining that the current state of a functional module is the turned-on state, because various functional module in the mobile terminal has corresponding processing procedures of changing names, when the current state of the functional module is the turned-on state, it is to first trigger the processing procedures of changing names of the functional module, and replace the name previously stored in the configuration file with the currently generated functional module name and save the currently generated functional module name in the configuration file. [0115]When the current state of the functional module is the non-startup state, the turned-off state or the turned-on state, it is to respectively save the functional module name corresponding to the functional module into the database, or into the configuration file, or replace and save it in the configuration file, which ensures to reduce the user's operation steps and enhance the user experience. [0116]Refer to FIG. 11, and FIG. 11 is a schematic diagram of the structure of a fifth embodiment of the mobile terminal in accordance with the present document. [0117]Based on the abovementioned embodiment, the mobile terminal further comprises: [0118]a judging module 60, configured to: judge the condition of the mobile terminal supporting the mobile modules; the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0119]Before generating a functional module name corresponding to a functional module according to the set name of the mobile terminal, the functional modules supported by the mobile terminal are firstly judged through the judging module 40, that is, it judges which functional modules are supported by the mobile terminal. In this embodiment, the functional modules comprise a Bluetooth module, a WIFI hotspot module, a WIFI Direct module and other modules, and when the mobile terminal communicates with other mobile terminals through these modules, it needs to provide a name which can be identified by the other party. [0120]After setting the name of mobile terminal, it needs to, before generating functional module names corresponding to various functional modules of the mobile terminal according to the name, first judge which functional modules are supported by the mobile terminal, so as to generate functional module names of these functional modules, thus providing the foundation for automatically modifying the names of various functional modules of the mobile terminal according to the name of the mobile terminal. [0121]In another embodiment, it further provides a kind of software which is used to perform the technical solution described in the abovementioned embodiments and the preferred embodiments. [0122]In another embodiment, it further provides a storage medium, and the storage medium stores the above software, and the storage medium includes, but is not limited to: compact disc, floppy disk, hard disk, flash memory or the like. [0123]Obviously, a person skilled in the art should understand that the respective modules or steps in the embodiments of the present document can be implemented with general-purpose computing devices, and they can be concentrat(String), 技术领域 [0001] 本发明涉及移动通信技术领域,尤其涉及一种移动终端功能模块名称的设置方法及移动终端。 相关技术背景 [0002] 目前,蓝牙、便携式WIFI热点、WIFI Direct等技术在高端移动终端中的应用越来越广泛,蓝牙和便携式WIFI热点已经成为普遍特征。 通过蓝牙,用户可以方便地与各类设备进行信息交换和共享; 通过随身WIFI热点,用户可以与其他设备共享移动终端的移动网络,通过WIFI Direct,用户可以方便地实现与其他设备的直接连接、传输数据或共享应用。 [0003] 但是,由于目前移动终端通常使用默认设备名称来识别蓝牙设备,使用默认值或随机值来识别WIFI热点和WIFI直连设备,无论是统一使用标识还是随机生成标识, 造成用户辨别混乱,因为当用户使用上述功能时,通常用户只是针对一个人,然后连接到他的设备,而很少知道对方的设备名称是什么。 为了识别用户的设备,目前的做法是,在蓝牙、便携式WIFI热点、WIFI Direct等模块中,用户可以单独修改每个模块的名称。 然而,这种方法的操作具有一定的复杂性和局限性。 发明内容 [0004] 本发明实施例提供一种移动终端功能模块名称的设置方法及移动终端,旨在自动修改移动终端中各功能模块的名称,以减少用户的操作步骤,提高用户使用体验。 经验。 [0005] 本发明提供了一种移动终端功能模块名称的设置方法,包括: [0006] 设置移动终端名称; [0007] 根据设置的移动终端名称,生成移动终端中功能模块对应的功能模块名称。 [0008] 优选地,在执行所述生成移动终端中的功能模块对应的功能模块名称之后,还包括: [0009] 显示功能模块名称。 [0010] 优选地,在执行所述显示功能模块名称之后,还包括: [0011] 提示用户确认功能模块名称。 [0012] 优选地,在执行所述提示用户确认功能模块名称之后,还包括: [0013] 根据功能模块的当前状态,保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0014] 优选地,所述根据功能模块的当前状态保存功能模块名称包括: [0015] 当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中; [0016] 当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0017] 当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换保存到功能模块的配置文件中。 [0018] 优选地,在执行所述根据设置的移动终端名称生成移动终端中各功能模块对应的功能模块名称之前,还包括: [0019]判断移动终端支持功能模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0020] 本发明实施例还提供一种移动终端,包括: [0021] 设置模块,用于设置移动终端的名称; [0022] 名称生成模块,用于根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称。 [0023] 优选地,所述移动终端还包括: [0024] 显示模块,用于显示功能模块名称。 [0025] 优选地,所述移动终端还包括: [0026] 提示模块,用于提示用户确认功能模块名称。 [0027] 优选地,所述移动终端还包括: [0028] 保存模块,用于根据功能模块的当前状态,保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0029] 优选地,所述保存模块用于: [0030] 当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中; [0031] 当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0032] 当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换并保存到功能模块的配置文件中。 [0033] 优选地,所述移动终端还包括: [0034] 判断模块,用于判断移动终端支持该功能模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0035] 在本发明实施例中,设置移动终端的名称,然后根据设置的移动终端名称生成移动终端中的功能模块对应的功能模块名称。 通过设置移动终端的名称,可以自动修改移动终端中各个功能模块的名称,减少了用户的操作步骤,提高了用户体验。 附图的简要说明 [0036] 图1为本发明移动终端功能模块名称设置方法第一实施例的流程图; [0037] 图2为本发明移动终端功能模块名称设置方法第二实施例的流程图; [0038] 图3为本发明移动终端功能模块名称设置方法第三实施例的流程图; [0039] 图4为本发明移动终端功能模块名称设置方法第四实施例的流程图。 [0040] 图5为本发明移动终端功能模块名称设置方法中保存功能模块名称的流程图; [0041] 图6为本发明移动终端功能模块名称设置方法第五实施例的流程图; [0042] 图7为本发明移动终端第一实施例的结构示意图; [0043] 图8为本发明移动终端第二实施例的结构示意图; [0044] 图9为本发明移动终端第三实施例的结构示意图; [0045]图10为本发明移动终端第四实施例的结构示意图; [0046] 图11为本发明移动终端第五实施例的结构示意图。 [0047] 本发明目的的实现、功能特点和优点将结合实施例并参照附图进行进一步说明。 本发明的优选实施例 [0048] 应当理解,此处所描述的具体实施例仅仅用于解释本发明,并不用于限制本发明。 在不冲突的情况下,本申请实施例中的实施例及特征可以相互组合。 [0049] 本发明实施例提供了一种设置移动终端功能模块名称的方法,通过设置移动终端的名称,自动为移动终端支持的各种功能模块生成对应的功能模块名称,并显示功能模块名称。 供用户确认是否保存名称,用户也可以自行修改功能模块名称。 [0050] 参见图1图1为本发明移动终端功能模块名称设置方法第一实施例的流程图。 [0051] 本实施例提供的设置移动终端功能模块名称的方法包括: [0052] 在步骤S 10 , 设置移动终端名称; [0053] 本实施例中,可以在移动终端的设置模块中增加一个入口,供用户输入移动终端的名称,用户可以通过该入口设置移动终端的名称。 在设置移动终端中各个功能模块对应的功能模块名称之前,首先设置移动终端的名称。 移动终端的名称可以由用户自己设置,可以起到识别用户移动终端设备的作用,本实施例中,为了保证其与实际使用的名称不同 其他周边移动终端有,优选使用用户的全名作为移动终端的名称。 [0054] 在步骤S 20 、根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称; [0055] 设置移动终端的名称后,根据移动终端支持的功能模块以及移动终端的名称,自动生成各个功能模块对应的功能模块名称。 在本实施例中,功能模块名称可以为移动终端的设置名称加上功能模块的功能名称。 [0056] 在本发明实施例中,设置移动终端的名称,然后根据设置的移动终端名称生成移动终端中的功能模块对应的功能模块名称。 通过设置移动终端的名称,可以自动修改移动终端中各个功能模块的名称,减少了用户的操作步骤,提高了用户体验。 [0057] 参见图2,图2为本发明移动终端功能模块名称设置方法第二实施例的流程图。 [0058] 基于上述实施例,执行步骤S后 20 ,该方法还包括: [0059] 在步骤S 30 , 显示功能模块名称。 [0060]根据移动终端的名称自动生成各个功能模块对应的功能模块名称后,将生成的功能模块名称通过界面显示给用户,本实施例中,各个功能模块和对应的功能模块 名称可以列在移动终端的界面中。 [0061] 根据设置的移动终端名称自动生成各个功能模块对应的功能模块名称后,将生成的功能模块名称显示给用户,为用户确认功能模块名称提供依据。 [0062] 参见图3,图3为本发明移动终端功能模块名称设置方法第三实施例的流程图。 [0063] 基于上述实施例,在执行完步骤S后 30 ,该方法还包括: [0064] 在步骤S 40 , 提示用户确认功能模块名称。 [0065] 将生成的功能模块名称显示在移动终端的界面中,同时设置确认按钮供用户确认各个功能模块对应的功能模块名称,提示用户进行确认。 在这种情况下,如果用户接受自动生成的功能模块名称,则用户点击确认; 如果用户不接受,则用户可以自行修改,修改后点击确认,从而完成移动终端功能模块名称的设置。 [0066] 显示生成的功能模块名称,并提示用户确认界面显示的功能模块名称,从而保证移动终端的各个功能模块的名称可以通过设置移动终端的名称自动修改。 [0067] 参见图4,图4为本发明移动终端功能模块名称设置方法第四实施例的流程图。 [0068] 基于上述实施例,在执行完步骤S后 40 ,该方法还包括: [0069] 在步骤S 50 ,根据功能模块的当前状态保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0070] 用户接受显示的自动生成的功能模块名称并点击确认后,或者用户自行修改功能模块名称并点击确认后,此时判断功能模块的当前状态 ,并根据当前状态的不同,对功能模块名称进行不同的保存。 在本实施例中,功能模块的当前状态包括非启动状态、关机状态和开机状态,其中,非启动状态是指移动终端的功能模块从未启动过 在这些情况下,它是出厂的,或者恢复出厂设置,或者升级; 关闭状态是指功能模块已经启动,但当前处于关闭状态。 开启状态是指功能模块当前处于开启状态。 [0071] 用户确认自动生成的功能模块名称或用户自行修改功能模块名称后,根据功能模块的当前状态,保存功能模块名称,方便用户在使用时查找和使用功能模块名称。 下次启动功能模块,为减少用户的操作步骤提供了前提保证。 [0072] 参见图5,图5为本发明移动终端功能模块名称设置方法中保存功能模块名称的流程图。 [0073]基于上述实施例,在步骤S中 50 , 当功能模块当前状态为非启动状态时,转步骤S 51 ; 当功能模块当前状态为关闭状态时,转步骤S 52 ; 当功能模块当前状态为开启状态时,转步骤S 53 . [0074] 在步骤S 51 ,就是将功能模块对应的功能模块名称存入数据库; [0075] 当判断功能模块的当前状态为非启动状态时,说明还没有生成该功能模块的用于存储功能模块名称的配置文件,则存储功能模块名称 在移动终端的数据库中。 在本实施例中,根据功能模块名称生成一条记录,该记录以功能模块为键,功能模块名称为值,保存在数据库中。 功能模块启动后,查找数据库,判断其中是否存在以功能模块为key,功能模块名称为value的记录,如果有,则显示记录中的功能模块名称 并写入功能模块的配置文件,然后清空该值,下次开启该功能模块时,不再使用数据库中的值,而是直接查找配置文件,将其中的值 用来。 [0076] 在步骤S 52 ,将一个功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0077] 当判断功能模块的当前状态为关闭状态时,表示该功能模块的用于存储功能模块名称的配置文件已经生成,此时, 直接将功能模块名称保存到配置文件中。 [0078] 在步骤S 53 ,就是将功能模块对应的功能模块名替换保存到功能模块的配置文件中。 [0079] 当确定功能模块的当前状态为开机状态时,由于移动终端中的各个功能模块都有相应的更名处理过程,当功能模块的当前状态为开机状态时, 首先触发更改功能模块名称的处理流程,将配置文件中先前保存的名称替换为当前生成的功能模块名称,并将当前生成的功能模块名称保存在配置文件中。 [0080] 当功能模块当前状态为非启动状态、关机状态或开机状态时,分别将该功能模块对应的功能模块名称保存到数据库中,或者保存到配置文件中 ,或者替换保存到配置文件中,保证减少用户的操作步骤,提升用户体验。 [0081] 参见图6,图6为本发明移动终端功能模块名称设置方法第五实施例的流程图。 [0082] 基于本发明移动终端功能模块名称设置方法实施例一,在执行步骤S之前 20 ,它还包括: [0083] 在步骤S 60 ,判断移动终端支持该功能模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0084]在根据设置的移动终端名称生成功能模块对应的功能模块名称之前,首先判断移动终端支持的功能模块,即判断移动终端支持哪些功能模块。 本实施例中,功能模块包括蓝牙模块、WIFI热点模块、WIFI直连模块等模块,移动终端在通过这些模块与其他移动终端进行通信时,需要提供一个名称,该名称可以通过 对方。 [0085] 设置好移动终端的名称后,需要在根据名称生成移动终端的各个功能模块对应的功能模块名称之前,先判断移动终端支持哪些功能模块,从而生成功能模块名称 这些功能模块的名称,从而为根据移动终端的名称自动修改移动终端的各个功能模块的名称提供了基础。 [0086] 请参阅图7,图7为本发明移动终端第一实施例的结构示意图。 [0087] 本实施例提供的移动终端包括: [0088] 设置模块 10 ,用于设置移动终端的名称; [0089] 名称生成模块 20 ,用于根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称; [0090] 本实施例中,可以在移动终端的设置模块中增加一个入口,供用户输入移动终端的名称,用户可以通过该入口设置移动终端的名称。 在设置移动终端中各个功能模块对应的功能模块名称之前,首先通过设置模块设置移动终端的名称 10 . 移动终端的名称由用户自己设置,可以起到识别用户移动终端设备的作用,本实施例中为了保证该名称与周围其他移动设备的名称不同 终端具有,优选地使用用户的全名作为移动终端的名称。 [0091] 设置好手机端名字后,名字生成模块 20 根据移动终端支持的功能模块以及移动终端的名称,自动生成各个功能模块对应的功能模块名称。 在本实施例中,功能模块名称可以设置为移动终端的名称加上功能模块的功能名称。 [0092] 在本发明实施例中,设置移动终端的名称,然后根据设置的移动终端名称生成移动终端中的功能模块对应的功能模块名称。 通过设置移动终端的名称,可以自动修改移动终端中各个功能模块的名称,减少了用户的操作步骤,提高了用户体验。 [0093] 请参阅图8,图8为本发明移动终端第二实施例的结构示意图。 [0094] 在上述实施例的基础上,所述移动终端还包括: [0095] 显示模块 30 ,配置为:显示功能模块名称。 [0096] 根据移动终端名称自动生成各个功能模块对应的功能模块名称后,显示模块 30 将生成的功能模块名称通过界面显示给用户,本实施例中可以在移动终端的界面中列出各种功能模块以及对应的功能模块名称。 [0097]根据设置的移动终端名称自动生成各个功能模块对应的功能模块名称后,将生成的功能模块名称显示给用户,为用户确认功能模块名称提供依据。 [0098] 请参阅图9,图9为本发明移动终端第三实施例的结构示意图。 [0099] 在上述实施例的基础上,所述移动终端还包括: [0100] 提示模块 40 ,配置为:提示用户确认功能模块名称。 [0101] 生成的功能模块名称显示在移动端界面,同时提示模块 40 设有确认按钮供用户确认各个功能模块对应的功能模块名称,提示用户进行确认。 在这种情况下,如果用户接受自动生成的功能模块名称,则用户点击确认; 如果用户不接受名称,用户可以自行修改,修改完成后点击确认,即可完成移动终端功能模块名称的设置。 [0102] 显示生成的功能模块名称并提示用户确认界面显示的功能模块名称,可以进一步保证移动终端的各个功能模块的名称可以通过设置移动终端的名称自动修改。 [0103] 请参阅图10,图10为本发明移动终端第四实施例的结构示意图。 [0104] 在上述实施例的基础上,所述移动终端还包括: [0105] 一个保存模块 50 ,用于根据功能模块的当前状态,保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0106] 用户接受显示的自动生成的功能模块名称并点击确认后,或用户自行修改功能模块名称并点击确认后,此时保存模块 50 判断功能模块的当前状态,根据当前状态的不同,对功能模块名称进行不同的保存。 在本实施例中,功能模块的当前状态包括非启动状态、关机状态和开机状态,其中,非启动状态是指移动终端的功能模块从未启动过 在这些情况下,它是出厂的,或者恢复出厂设置,或者升级; 关闭状态是指功能模块已经启动,但当前处于关闭状态。 开启状态是指功能模块当前处于开启状态。 [0107] 用户确认自动生成的功能模块名称,或用户自行修改功能模块名称后,根据功能模块当前状态保存功能模块名称,方便查找和使用功能模块 下次启动功能模块时命名,为减少用户的操作步骤提供了前提保证。 [0108] 在上述实施例中,保存模块 50 配置为: [0109] 当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中; [0110] 当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0111]当功能模块的当前状态为开启状态时,将该功能模块对应的功能模块名称替换并保存到该功能模块的配置文件中。 [0112] 当判断功能模块的当前状态为非启动状态时,说明该功能模块的用于存储功能模块名称的配置文件还没有生成,此时,该功能模块 名称存储在移动终端的数据库中。 在本实施例中,根据功能模块名称生成一条记录,该记录以功能模块为键,功能模块名称为值,保存在数据库中。 功能模块启动时,在数据库中查找,判断其中是否有以功能模块为键,功能模块名称为值的记录,如果有,则在中显示功能模块名称 记录写入功能模块的配置文件,然后清空该值,下次启动功能模块时,数据库中的值不再使用,直接查找配置文件, 使用其中的值。 [0113] 当判断一个功能模块的当前状态为关闭状态时,说明该功能模块的用于存储功能模块名称的配置文件已经生成,此时直接 在配置文件中保存功能模块名称。 [0114] 当确定功能模块的当前状态为开机状态时,由于移动终端中的各个功能模块都有相应的更名处理过程,当功能模块的当前状态为开机状态时, 首先触发更改功能模块名称的处理流程,将配置文件中先前保存的名称替换为当前生成的功能模块名称,并将当前生成的功能模块名称保存在配置文件中。 [0115] 当功能模块当前状态为非启动状态、关机状态或开机状态时,分别将该功能模块对应的功能模块名称保存到数据库中,或者保存到配置文件中 ,或者替换保存在配置文件中,保证减少用户的操作步骤,提升用户体验。 [0116] 请参阅图11,图11为本发明移动终端第五实施例的结构示意图。 [0117] 在上述实施例的基础上,所述移动终端还包括: [0118] 判断模块 60 ,用于判断移动终端支持移动模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0119] 在根据设置的移动终端名称生成功能模块对应的功能模块名称之前,首先通过判断模块判断移动终端支持的功能模块 40 ,即判断移动终端支持哪些功能模块。 本实施例中,功能模块包括蓝牙模块、WIFI热点模块、WIFI直连模块等模块,移动终端在通过这些模块与其他移动终端进行通信时,需要提供一个名称,该名称可以通过 对方。 [0120] 设置好移动终端的名称后,需要在根据名称生成移动终端的各个功能模块对应的功能模块名称之前,先判断移动终端支持哪些功能模块,从而生成功能模块名称 这些功能模块的名称,从而为根据移动终端的名称自动修改移动终端的各个功能模块的名称提供了基础。 [0121]在另一个实施例中,还提供了一种软件,用于执行上述实施例及优选实施例中描述的技术方案。 [0122] 在另一个实施例中,还提供了一种存储介质,该存储介质存储有上述软件,该存储介质包括但不限于:光盘、软盘、硬盘、闪存等。 [0123] 显然,本领域的技术人员应该理解,本发明实施例中的各个模块或步骤可以用通用的计算设备来实现,它们可以集中在单个计算设备上,也可以分布在由以下设备组成的网络中。 多个计算设备,备选地,它们可以由计算装置可执行的程序代码来执行,以便它们可以存储在存储装置中并由计算装置执行,并且在某些情况下,以不同于 也可以单独制作成单独的集成电路模块,或者将其中的部分模块或步骤制作成单个集成电路模块来实现。 因此,本文档不限于任何特定的硬件和软件组合。 [0124] 以上所述仅为本发明的较佳实施例而已,并不用于限制本发明的专利范围,任何利用本发明的说明书及附图所作的等同结构或等同过程变换,均属于本发明的范围。 直接或者间接应用于其他相关技术的,应当纳入本文件的专利保护范围。 工业实用性 [0125] 本发明实施例通过设置移动终端的名称,自动修改移动终端各功能模块的名称,减少了用户的操作步骤,提高了用户体验。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103856622A(String), EP2930915A1(String), EP2930915A4(String), EP2930915B1(String), US20150372974A1(String), US9455952B2(String), WO2013182100A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103856622A(String), EP2930915A1(String), EP2930915A4(String), EP2930915B1(String), US20150372974A1(String), US9455952B2(String), WO2013182100A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9455952B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103856622A(String), EP2930915A1(String), EP2930915A4(String), EP2930915B1(String), US20150372974A1(String), US9455952B2(String), WO2013182100A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), CN103856622A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), EP2930915A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), EP2930915A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), EP2930915B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), US20150372974A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), US9455952B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270658(Integer), WO2013182100A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9455952B2(String), US9455952B2(String), 1474905600(Integer), 270658(Integer), 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184976(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184976(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184976(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184976(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20150249630A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and System for Controlling Message of Mobile Terminal and Mobile Terminal(String), 移动终端消息控制方法及系统及移动终端(String), US20150249630A1(String), A method and system for controlling a message of a mobile terminal and the mobile terminal including an application platform for receiving a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal. The application platform displays information to be processed in the message to be processed. With the method and system for controlling a message of a mobile terminal, flexibility in control over the message of the mobile terminal is improved, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved.(String), 一种移动终端消息控制方法及系统,该移动终端包括:应用平台,用于接收该移动终端的待处理消息,该待处理消息由管理平台转发,其中,该待处理消息被发送至移动终端。 移动端管理平台。 应用平台在待处理消息中显示待处理信息。 通过本发明的移动终端消息控制方法及系统,提高了移动终端消息控制的灵活性,提高了移动终端消息控制的易用性,提高了用户对信息的感知能力。 待处理得到改进。(String), US14/426696(String), 1375200000(Integer), US20150249630A1(String), 1441209600(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 7(Integer), US20040082348A1 | US20040158609A1 | US20050091670A1 | US20070239830A1 | US20090141879A1 | US20100093379A1 | US20100240401A1(String), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184977(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\1add644023604de0aef5099ad86932e2.png(String), 184977(Integer), 1add644023604de0aef5099ad86932e2.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and System for Controlling Message of Mobile Terminal and Mobile Terminal(String), 移动终端消息控制方法及系统及移动终端(String), US20150249630A1(String), A method and system for controlling a message of a mobile terminal and the mobile terminal including an application platform for receiving a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal. The application platform displays information to be processed in the message to be processed. With the method and system for controlling a message of a mobile terminal, flexibility in control over the message of the mobile terminal is improved, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved.(String), 一种移动终端消息控制方法及系统,该移动终端包括:应用平台,用于接收该移动终端的待处理消息,该待处理消息由管理平台转发,其中,该待处理消息被发送至移动终端。 移动端管理平台。 应用平台在待处理消息中显示待处理信息。 通过本发明的移动终端消息控制方法及系统,提高了移动终端消息控制的灵活性,提高了移动终端消息控制的易用性,提高了用户对信息的感知能力。 待处理得到改进。(String), US14/426696(String), 1375200000(Integer), US20150249630A1(String), 1441209600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 7(Integer), US20040082348A1 | US20040158609A1 | US20050091670A1 | US20070239830A1 | US20090141879A1 | US20100093379A1 | US20100240401A1(String), \20230420\1add644023604de0aef5099ad86932e2.png(String), 10(Integer), 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 1. A method for controlling a message of a mobile terminal, comprising:receiving, by an application platform, a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal; anddisplaying, by the application platform, information to be processed in the message to be processed.(String), 1、一种移动终端的消息控制方法,包括:应用平台接收管理平台转发的移动终端的待处理消息,该待处理消息由移动终端发送给管理平台;和应用平台在待处理消息中显示待处理信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 2. The method according to claim 1, wherein before receiving, by the application platform, the message to be processed of the mobile terminal, which is forwarded by the management platform, the method further comprises:transmitting, by the mobile terminal, the message to be processed to the management platform according to a transmission rule, wherein the transmission rule comprises at least one of: information for indicating a type of the information to be processed, which is to be transmitted, and information for indicating a filtering condition for transmission of the information to be processed, which is to be transmitted.(String), 2.根据权利要求1所述的方法,其中应用平台接收管理平台转发的移动终端待处理消息之前,该方法还包括:移动终端根据传输规则向管理平台传输待处理消息,其中传输规则包括以下至少之一:用于指示待传输的待处理信息的类型的信息,用于指示传输待处理信息的过滤条件的信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 3. The method according to claim 2, wherein the transmission rule is directly set on the mobile terminal; and/or, the application platform transmits the set transmission rule to the mobile terminal.(String), 3.根据权利要求2所述的方法,其中传输规则直接在移动终端设置;和/或,应用平台将设置的传输规则发送给移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 4. The method according to claim 23, wherein the application platform transmitting the set transmission rule to the mobile terminal comprises:transmitting, by the application platform, an authentication message and the transmission rule to the management platform, wherein an identifier of the mobile terminal is carried in the authentication message; andperforming, by the management platform, subscribing relationship authentication on the mobile terminal, and under a condition that the mobile terminal passes the subscribing relationship authentication, transmitting the transmission rule to the mobile terminal according to the identifier of the mobile terminal.(String), 4.根据权利要求23所述的方法,其中应用平台向移动终端发送设置的传输规则,包括:应用平台向管理平台发送鉴权消息和传输规则,鉴权消息中携带移动终端的标识;和管理平台对移动终端进行订阅关系认证,在移动终端通过订阅关系认证的情况下,根据移动终端的标识向移动终端发送传输规则。(String), 1(Integer), 3(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 5. The method according to claim 1, wherein before receiving, by the application platform, the message to be processed of the mobile terminal, which is forwarded by the management platform, the method further comprises:performing, by the management platform, format check on the message to be processed, and performing the subscribing relationship authentication on the mobile terminal; andunder a condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, forwarding, by the management platform, the message to be processed to the application platform according to a subscribing relationship of the mobile terminal.(String), 5.根据权利要求1所述的方法,其中应用平台接收管理平台转发的移动终端待处理消息之前,该方法还包括:管理平台对待处理的消息进行格式校验,并对移动终端进行订阅关系认证;和在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,管理平台根据移动终端的订阅关系将待处理消息转发给应用平台。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 6. The method according to claim 1, wherein displaying, by the application platform, the information to be processed comprises:performing, by the application platform, permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; andunder a condition that the message to be processed passes the permission authentication, displaying, by the application platform, the information to be processed.(String), 6.根据权利要求1所述的方法,其中应用平台显示待处理信息包括:应用平台对待处理消息进行权限认证,权限用于表示是否允许在应用平台上展示待处理消息中的待处理信息。和在待处理消息通过权限认证的情况下,应用平台展示待处理信息。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 7. The method according to claim 1, wherein after displaying, by the application platform, the information to be processed, the method further comprises:transmitting, by the application platform, a reply message for the information to be processed to the management platform, wherein the reply message comprises: reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed; andperforming, by the management platform, authentication on the reply message, and under a condition that the reply message passes the authentication, transmitting the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forwarding the reply message to the mobile terminal for the mobile terminal to transmit the reply message to the source equipment of the information to be processed.(String), 7.根据权利要求1所述的方法,其中在应用平台显示待处理信息后,该方法还包括:应用平台向管理平台发送待处理信息的回复消息,该回复消息包括:待处理信息的回复信息、移动终端的标识和信息来源标识被处理;和管理平台对回复消息进行鉴权,在回复消息鉴权通过的情况下,根据回复消息中携带的转发标识将回复消息发送给待处理信息的源设备,或者将回复消息转发给移动终端,以便移动终端将回复消息发送给待处理信息的源设备。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 8. The method according to claim 1, wherein the information to be processed comprises at least one of: a short message to be processed, a missed call, QQ information to be processed and Microsoft Network (MSN) information to be processed.(String), 8.根据权利要求1所述的方法,其中所述待处理信息包括以下至少之一:待处理短信、未接来电、待处理QQ信息、待处理微软网络(MSN)信息。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 9. A mobile terminal, comprising:an acquiring component, configured to acquire information to be processed of the mobile terminal and generate a message to be processed, wherein the message to be processed comprises the information to be processed; anda first transmitting component, configured to transmit the message to be processed to a management platform and forward the message to be processed to an application platform through the management platform, wherein the application platform displays the information to be processed.(String), 9.移动终端,包括:获取模块,用于获取移动终端的待处理信息,并生成待处理消息,所述待处理消息包括所述待处理信息;和第一发送模块,用于将待处理消息发送给管理平台,并通过管理平台将待处理消息转发给应用平台,应用平台显示待处理信息。10、一种移动终端消息控制系统,其中该系统包括:如权利要求9所述的移动终端;管理平台,用于将移动终端发送的待处理消息转发给应用平台;应用平台,用于接收待处理消息,并显示待处理消息中的待处理信息。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184977(Integer), 10. A system for controlling a message of a mobile terminal, wherein the system comprises: the mobile terminal according to claim 9; a management platform, configured to forward the message to be processed, which is transmitted by the mobile terminal, to the application platform; and the application platform, configured to receive the message to be processed and display information to be processed in the message to be processed.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184977(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of communication, including, e.g., a method and system for controlling a message of a mobile terminal, and a mobile terminal. BACKGROUND [0002]In the related art, most of mobile phone services are controlled by an operator side. For example, the operator side may forward an incoming call of a user by a call forwarding service, and may prompt the user of a missed call by services such as a call reminding service and SmartCall. It can be seen that most of the mobile phone services need to be implemented by subscribing to specific services of an operator. [0003]For at least one problem in a related art, there is yet no effective solution. SUMMARY [0004]The embodiments of the disclosure provides a method and system for controlling a message of a mobile terminal and the mobile terminal, so as to at least solve the problem that a user needs to subscribe to a specific service of an operator to remind of information to be processed in a related art. [0005]According to an embodiment of the disclosure, a method for controlling a message of a mobile terminal is provided, including that: an application platform receives a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal; and the application platform displays information to be processed in the message to be processed. [0006]According to an embodiment of the disclosure, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the mobile terminal transmits the message to be processed to the management platform according to a transmission rule, wherein the transmission rule includes at least one of: information for indicating a type of the information to be processed, which is to be transmitted, and information for indicating a filtering condition for transmission of the information to be processed, which is to be transmitted. [0007]According to an embodiment of the disclosure, the transmission rule is directly set on the mobile terminal; and/or, the application platform transmits the set transmission rule to the mobile terminal. [0008]According to an embodiment of the disclosure, the application platform transmits the set transmission rule to the mobile terminal includes that: the application platform transmits an authentication message and the transmission rule to the management platform, wherein an identifier of the mobile terminal is carried in the authentication message; and the management platform performs subscribing relationship authentication on the mobile terminal, and under a condition that the mobile terminal passes the subscribing relationship authentication, transmits the transmission rule to the mobile terminal according to the identifier of the mobile terminal. [0009]According to an embodiment of the disclosure, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the management platform performs format check on the message to be processed, and performs the subscribing relationship authentication on the mobile terminal; and under a condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, the management platform forwards the message to be processed to the application platform according to a subscribing relationship of the mobile terminal. [0010]According to an embodiment of the disclosure, the application platform displays the information to be processed includes that: the application platform performs permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; and under a condition that the message to be processed passes the permission authentication, the application platform displays the information to be processed. [0011]According to an embodiment of the disclosure, after the application platform displays the information to be processed, the method for controlling the message of the mobile terminal further includes that: the application platform transmits a reply message for the information to be processed to the management platform, wherein the reply message includes: reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed; and the management platform performs authentication on the reply message, and under a condition that the reply message passes the authentication, transmits the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forwards the reply message to the mobile terminal, and the mobile terminal transmits the reply message to the source equipment of the information to be processed. [0012]According to an embodiment of the disclosure, the information to be processed includes at least one of: a short message to be processed, a missed call, QQ information to be processed and Microsoft Network (MSN) information to be processed. [0013]According to another aspect of the disclosure, a mobile terminal is provided, including: an acquiring component, configured to acquire information to be processed of the mobile terminal and generate a message to be processed, wherein the message to be processed includes the information to be processed; and a first transmitting component, configured to transmit the message to be processed to a management platform and forward the message to be processed to an application platform through the management platform, wherein the application platform displays the information to be processed. [0014]According to a third aspect of the disclosure, a system for controlling a message of a mobile terminal is provided, where the system comprises: any above-mentioned mobile terminal; a management platform, configured to forward the message to be processed, which is transmitted by the mobile terminal, to an application platform; and the application platform, configured to receive the message to be processed and display information to be processed in the message to be processed. [0015]According to the disclosure, the mobile terminal generates the message to be processed by using the information to be processed on the mobile terminal, transmits the message to be processed to the management platform, and forwards the message to be processed to the application platform through the management platform, and the application platform displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. BRIEF DESCRIPTION OF THE DRAWINGS [0016]The drawings are described here to provide further understanding of the disclosure, and form a part of the disclosure. The schematic embodiments and description of the disclosure are adopted to explain the disclosure, and do not form improper limits to the disclosure. In the drawings: [0017]FIG. 1 is a flowchart of a method for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0018]FIG. 2 is a structure diagram of a mobile terminal according to an embodiment of the disclosure; [0019]FIG. 3 is a structure diagram of another mobile terminal according to an embodiment of the disclosure; [0020]FIG. 4 is a structure diagram of a system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0021]FIG. 5 is a structure diagram of another system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0022]FIG. 6 is a structure diagram of a third system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0023]FIG. 7 is a structure diagram of a fourth system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0024]FIG. 8 is a flowchart of controlling a short message and a missed call of a user by utilizing a method for controlling a message of a mobile terminal according to an embodiment of the disclosure; and [0025]FIG. 9 is a flowchart of controlling a QQ/MSN message of a mobile phone of a user by utilizing a method for controlling a message of a mobile terminal according to an embodiment of the disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS [0026]The disclosure is described below with reference to the drawings and the embodiments in detail. It is important to note that the embodiments of the disclosure and the characteristics in the embodiments can be combined under the condition of no conflicts. [0027]A method for controlling a message of a mobile terminal is provided in the embodiment of the disclosure, and as shown in FIG. 1, the method for controlling the message of the mobile terminal includes S102 to S104. [0028]S102: an application platform receives a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal. [0029]S104: the application platform displays information to be processed in the message to be processed. [0030]By the steps, the mobile terminal generates the message to be processed by using the information to be processed on the mobile terminal, transmits the message to be processed to the management platform, and forwards the message to be processed to the application platform through the management platform, and the application platform displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. [0031]According to an embodiment of the disclosure, in order to facilitate the authentication over the mobile terminal and improve the security of the information, the message to be processed can further include: an identifier of the mobile terminal and a source identifier of the information to be processed, besides the information to be processed. [0032]In order to flexibly transmit the information to be processed on the mobile terminal to meet requirements of different application scenarios, in the preferred embodiment, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the mobile terminal transmits the message to be processed to the management platform according to a transmission rule, wherein the transmission rule includes at least one of: information for indicating a type of the information to be processed, which is to be transmitted, and information for indicating a filtering condition for transmission of the information to be processed, which is to be transmitted. That is, the transmission rule can be set according to a habit or requirement of the user; the information indicating the type of the information to be processed, which is to be transmitted, for example, which information to be processed is to be transmitted and which information to be processed is not to be transmitted can be set according to the requirement. For example, according to the requirement, information to be processed such as short message information and a missed call can be set to be transmitted, QQ information to be processed can be set not to be transmitted, and the information of all types can also be set to be transmitted; and the filtering condition of the information to be processed, which is to be transmitted, can also be set, for example, if the short message information to be processed is set to be transmitted, a time frame in which the short message information to be processed is to be transmitted can further be set in order to the user to conveniently perceive the information to be processed. [0033]In order to meet the requirements of different application scenarios and improve the setting flexibility of the transmission rule, in the preferred embodiment, the transmission rule is directly set on the mobile terminal; and/or, the application platform transmits the set transmission rule to the mobile terminal, that is, different manners for setting the transmission rule can be selected according to different application scenarios, the transmission rule can be directly set on the mobile terminal, and can also be set through the application platform. Setting operation is conducted on an application display interface of the application platform, then the application platform transmits the set transmission rule to the mobile terminal through the management platform, and the mobile terminal performs setting according to the received transmission rule. [0034]In order to improve the security of the information, in the preferred embodiment, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the management platform performs format check on the message to be processed, and performs subscribing relationship authentication on the mobile terminal; and under the condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, the management platform forwards the message to be processed to the application platform according to a subscribing relationship of the mobile terminal. That is, after the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, the message to be processed is transmitted to the application platform, so that the security of the information is improved. [0035]In order to correctly display the information to be processed, in the preferred embodiment, that the application platform displays the information to be processed includes that: the application platform performs permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; and under the condition that the message to be processed passes the permission authentication, the application platform displays the information to be processed. That is, after that the information to be processed can be displayed is determined, the information to be processed is displayed. [0036]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, after the application platform displays the information to be processed, the method for controlling the message of the mobile terminal further includes that: the application platform transmits a reply message for the information to be processed to the management platform, wherein the reply message includes: reply information for the information to be processed, the identifier of the mobile terminal and a source identifier of the information to be processed; and the management platform performs authentication on the reply message, and under the condition that the reply message passes the authentication, transmits the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forwards the reply message to the mobile terminal, and the reply message is transmitted by the mobile to the source equipment of the information to be processed. That is, the user can process the information to be processed through the management platform, and directly transmits the processed rely message to the source equipment of the information to be processed through the management platform; and the information to be processed can also be processed through the management platform, the management platform forwards the processed reply message to the mobile terminal, and the mobile terminal automatically transmits the received reply message to the source equipment of the information to be processed. [0037]In order to meet application requirements of different users and improve the practicability, in the preferred embodiment, the information to be processed can include at least one of: a short message to be processed, a missed call, QQ information to be processed, MSN information to be processed and the like. [0038]In the preferred embodiment, a preferred mobile terminal is provided, and as shown in FIG. 2, the mobile terminal includes: an acquiring component 202, which is configured to acquire the information to be processed of the mobile terminal and generate a message to be processed, wherein the message to be processed includes the information to be processed; and a first transmitting component 204, connected to the acquiring component 202, which is configured to transmit the message to be processed to a management platform and forward the message to be processed to an application platform through the management platform, wherein the application platform displays the information to be processed. [0039]In the preferred embodiment, the acquiring component 202 generates the message to be processed by using the information to be processed on the mobile terminal, the first transmitting component 204 transmits the message to be processed to the management platform, and forwards the message to be processed to the application platform through the management platform, and the application platform displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. [0040]In order to meet the requirements of different application scenarios and improve the setting flexibility of a transmission rule, in the preferred embodiment, as shown in FIG. 3, the mobile terminal further includes: a first setting component 206, which is configured to set the transmission rule. [0041]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, as shown in FIG. 3, the mobile terminal further includes: a receiving component 208, which is configured to receive a reply message for the information to be processed, which is forwarded by the management platform, wherein the reply message is transmitted by the application platform, and the reply message includes reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed; and a first forwarding component 210, connected to the receiving component 208, which is configured to forward the reply message to source equipment of the information to be processed. [0042]In the preferred embodiment, a preferred system for controlling a message of a mobile terminal is provided, and as shown in FIG. 4, the system for controlling the message of the mobile terminal includes: the mobile terminal 402; a management platform 404, connected to the mobile terminal 402, which is configured to forward a message to be processed, which is transmitted by the mobile terminal, to an application platform; and the application platform 406, connected to the management platform 404, which is configured to receive the message to be processed and display information to be processed in the message to be processed. [0043]In the preferred embodiment, the mobile terminal 402 generates the message to be processed by using the information to be processed on the mobile terminal 402, transmits the message to be processed to the management platform 404, and forwards the message to be processed to the application platform 406 through the management platform 404, and the application platform 406 displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. [0044]In order to meet the requirements of different application scenarios and improve the setting flexibility of a transmission rule, in the preferred embodiment, as shown in FIG. 5, the application platform includes: a second setting rule 4062, which is configured to set the transmission rule and transmit the set transmission rule to the mobile terminal. [0045]In order to correctly display the information to be processed, in the preferred embodiment, as shown in FIG. 5, the application platform 406 further includes: a first authentication component 4064, which is configured to perform permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; and a display component 4066, connected to the first authentication component 4064, which is configured to, under the condition that the message to be processed passes the permission authentication, display the information to be processed. [0046]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, as shown in FIG. 5, the application platform 406 further includes: a second transmission component 4068, which is configured to transmit a reply message for the information to be processed to the management platform, wherein the reply message includes: reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed. [0047]In order to improve the security of the information, in the preferred embodiment, as shown in FIG. 6, the management platform 404 includes: a second authentication component 4042, which is configured to perform format check on the message to be processed and perform subscribing relationship authentication on the mobile terminal; and a second forwarding component 4044, connected to the second authentication component 4042, which is configured to, under the condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, forward the message to be processed to the application platform according to a subscribing relationship of the mobile terminal. [0048]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, the second forwarding component 4044 is further configured to perform authentication on the reply message for the information to be processed, and under the condition that the reply message passes the authentication, transmit the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forward the reply message to the mobile terminal for the mobile terminal to transmit the reply message to the source equipment of the information to be processed. [0049]Each preferred embodiment is described below with reference to the drawings in detail. [0050]In the preferred embodiment, the mobile terminal takes a smart mobile phone as an example, FIG. 7 is a structure diagram of a fourth system for controlling a message of a mobile terminal, and as shown in FIG. 7, the system for controlling the message of the mobile terminal includes: the mobile terminal 702, wherein the mobile terminal 702 includes a missed information detection unit, which is configured to receive and process missed information of a user, such as missed call information, a missed short message, missed QQ information and missed MSN information. A function of the missed information detection unit can be realized through software, for example, by certain software, message contents such as the missed short message, the missed call information, the missed QQ information and the missed MSN information, and message sources such as a mobile phone number, a QQ number and an MSN number can be extracted from the mobile phone. The message can be transparently transmitted to a specific management platform in a certain format according to a set mode (equivalent to the above transmission rule); the management platform 704, which is configured to perform application and terminal access, terminal and application management and data transparent-transmission between the terminal and an application; and an application platform 706, wherein the application platform 706 can include: an authentication component 7062 (equivalent to the first authentication component 4064), which is configured to perform authentication on a message between the terminal and the application according to a set filtering condition, a background processing component 7064, which is configured to receive the missed information of the user from the management platform and process and transmit the information to a missed information display component, and the missed information display component 7066 (equivalent to the display component 4066), which is configured to display the information processed by the background processing component 7064. [0051]By the system for controlling the message of the mobile terminal, the user can control certain information of the mobile phone without subscribing to a certain service of an operator, and can receive a short message, know a missed call and communicate with a user of a chatting tool such as QQ, MSN and the like on the mobile phone even under the condition of not carrying the mobile phone. However, in order to flexibly transmit the information to be processed, the transmission rule for the message to be processed such as the short message, the missed call, a QQ message and an MSN message can be set on the mobile phone at first, wherein the transmission rule indicates which message needs to be forwarded, a filtering condition for forwarding and the like; there are two manners for setting the transmission rule, one is to set the transmission rule on the software of the mobile phone by the user, and the other is to set the transmission rule through a display interface (such as a web page) of the application platform by the user. The setting of the transmission rule through the display interface of the application platform can be implemented by the following steps that: [0052]S1: the user operates the application display interface, sets a forwarding rule, and submits the set forwarding rule. [0053]S2: the application platform performs message authentication to determine whether the user is permitted to use a function of transmitting the information to be processed to the application platform or not. [0054]S3: an application background processes, packs and converts an authentication message into a message format consistent with the management platform. [0055]S4: the management platform receives the authentication message from the application platform, performs subscribing relationship authentication and the like, extracts the identification information, such as to which user the message is to be transmitted, of the mobile terminal from the authentication message, and transparently transmits the message if the condition is met, and turns to S5. [0056]S5: the mobile phone terminal receives an automatic forwarding message from the management platform, parses the automatic forwarding message, and performs automatic forwarding setting according to an instruction. [0057]FIG. 8 is a flowchart of controlling a short message and a missed call of a user by utilizing a method for controlling a message of a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 8, the flow can include the following steps that: [0058]S802: a mobile phone terminal receives a short message (including a Fetion message) and a missed call, the short message (including the Fetion message) and the missed call are processed and packed into a message to be processed by the software in the mobile phone terminal, the message to be processed including: a mobile phone terminal number, a source mobile phone number and contents (short message contents or the missed call), and the mobile phone terminal transparently transmits the data of the message to be processed to a management platform. [0059]S804: the management platform performs message format check and subscribing relationship authentication on the message to be processed, and transparently transmits the data to a corresponding application platform according to a subscribing relationship. [0060]S806: an application background of the application platform parses the message to be processed, which is transmitted by the management platform, converts a message format of the message to be processed, and transmits the message to be processed to an authentication component (equivalent to the first authentication component 4064) of the application platform. [0061]S808: the authentication component performs internal subscribing relationship authentication, permission authentication and the like on the received message, and transmits the contents of the message passing the authentication to a user display component (equivalent to the display component 4066). [0062]S810: a user (user A) can directly reply the short message on a display interface of the application platform, and can select to directly forward a reply message through the management platform if the management platform can transmit the short message or to reply the short message through the mobile phone if the management platform cannot transmit the short message; for example, for reply contents, the message is forwarded to the management platform through the authentication component and a message processing component; the management platform forwards the reply message to a source mobile phone of the short message or the mobile phone terminal according to a forwarding identifier of the short message, and if being(String), 技术领域 [0001] 本发明涉及通信领域,例如包括一种移动终端的消息控制方法、系统及移动终端。 背景 [0002] 相关技术中,大部分手机业务由运营商侧控制。 例如,运营商侧可以通过呼叫转移业务来转移用户的来电,也可以通过来电提醒业务、SmartCall等业务提示用户有未接来电。 可以看出,大部分的手机业务都需要通过订阅运营商的特定业务来实现。 [0003] 对于相关技术中的至少一个问题,目前还没有有效的解决方案。 概括 [0004] 本发明实施例提供了一种控制移动终端消息的方法、系统及移动终端,以至少解决用户需要订阅运营商的特定业务来提醒信息的问题。 在相关技术中处理。 [0005] 根据本发明的一个实施例,提供了一种移动终端的消息控制方法,包括:应用平台接收管理平台转发的移动终端的待处理消息,其中,所述消息发送至 待处理通过移动终端传输至管理平台; 应用平台在待处理消息中显示待处理信息。 [0006] 根据本发明的一个实施例,在应用平台接收到管理平台转发的移动终端待处理消息之前,控制移动终端消息的方法还包括:移动终端发送 根据传输规则向管理平台发送待处理消息,其中,所述传输规则包括以下至少之一:用于指示待传输的待处理信息的类型的信息,以及用于指示过滤条件的信息 传输要处理的信息,即要传输的信息。 [0007] 根据本发明的一个实施例,传输规则直接设置在移动终端上; 和/或,应用平台将设置的传输规则发送给移动终端。 [0008] 根据本发明的一个实施例,应用平台向移动终端发送设置的传输规则包括:应用平台向管理平台发送鉴权消息和传输规则,其中,移动终端的标识携带在 认证信息; 管理平台对移动终端进行订阅关系认证,在移动终端通过订阅关系认证的情况下,根据移动终端的标识向移动终端发送传输规则。 [0009] 根据本发明的一个实施例,在应用平台接收到管理平台转发的移动终端待处理消息之前,控制移动终端消息的方法还包括:管理平台进行格式化 检查待处理的消息,并在移动终端上进行订阅关系认证; 在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,管理平台根据移动终端的订阅关系将待处理消息转发给应用平台。 [0010]根据本发明的一个实施例,应用平台展示待处理信息包括: 应用平台对待处理消息进行权限认证,权限用于指示消息中的待处理信息是否可以访问。 待处理是否允许在应用平台上展示; 在待处理消息通过权限认证的情况下,应用平台展示待处理信息。 [0011] 根据本发明的一个实施例,在应用平台显示待处理信息后,控制移动终端消息的方法还包括:应用平台向管理平台发送针对待处理信息的回复消息。 ,其中,回复消息包括:待处理信息的回复信息、移动终端的标识和待处理信息的来源标识; 管理平台对回复消息进行鉴权,在回复消息鉴权通过的情况下,根据回复消息中携带的转发标识将回复消息发送给待处理信息的源设备,或者转发 回复消息给移动终端,移动终端将回复消息发送给待处理信息的源设备。 [0012] 根据本发明的一个实施例,所述待处理信息包括以下至少之一:待处理短信、未接来电、待处理QQ信息、待处理微软网络(MSN)信息。 [0013] 根据本发明的另一方面,提供了一种移动终端,包括: 获取模块,用于获取移动终端的待处理信息并生成待处理消息,所述待处理消息包括待处理信息。 处理; 第一发送模块,用于将待处理消息发送给管理平台,并通过管理平台将待处理消息转发给应用平台,应用平台显示待处理信息。 [0014] 根据本发明的第三方面,提供了一种移动终端的消息控制系统,该系统包括: 上述任一种移动终端; 管理平台,用于将移动终端发送的待处理消息转发给应用平台; 应用平台,用于接收待处理消息,并显示待处理消息中的待处理信息。 [0015] 根据本发明,移动终端利用移动终端上的待处理信息生成待处理消息,将待处理消息发送给管理平台,并通过管理平台转发待处理消息给应用平台。 管理平台,应用平台将待处理信息显示在待处理消息中,用户无需订阅运营商的特定服务即可提醒待处理信息,消息控制灵活 改进了移动端; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 附图的简要说明 [0016] 此处描述的附图是为了提供对本公开的进一步理解,并且构成本公开的一部分。 本发明中的示意性实施例和说明用于解释本发明,并不对本发明构成不当限制。 在图纸中: [0017]图1是根据本发明实施例的移动终端的消息控制方法的流程图; [0018] 图2是根据本发明实施例的移动终端的结构图; [0019] 图3为本发明实施例提供的另一种移动终端的结构图; [0020] 图4是根据本发明实施例的移动终端的消息控制系统的结构图。 [0021] 图5为本发明实施例提供的另一种移动终端消息控制系统的结构图; [0022] 图6是根据本发明实施例的第三种移动终端消息控制系统的结构图; [0023] 图7是根据本发明实施例的第四种移动终端消息控制系统的结构图; [0024] 图8是根据本发明实施例的利用移动终端的消息控制方法控制用户的短信和未接来电的流程图; 和 [0025] 图9为根据本发明实施例的利用控制移动终端消息的方法控制用户手机QQ/MSN消息的流程图。 具体实施方式 [0026] 下面结合附图和实施例对本发明进行详细说明。 需要说明的是,在不冲突的情况下,本发明中的实施例及实施例中的特征可以相互组合。 [0027] 本发明实施例提供了一种移动终端的消息控制方法,如图1所示,该移动终端的消息控制方法包括: 102 到小号 104 . [0028] 小号 102 :应用平台接收管理平台转发的移动终端的待处理消息,该待处理消息由移动终端发送给管理平台。 [0029] 小号 104 :应用平台在待处理消息中显示待处理信息。 [0030] 通过上述步骤,移动终端利用移动终端上的待处理信息生成待处理消息,将待处理消息发送给管理平台,通过管理将待处理消息转发给应用平台。 平台,应用平台将待处理信息显示在待处理消息中,用户无需订阅运营商的特定服务即可提醒待处理信息,灵活控制消息 改进了移动端; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0031] 根据本发明的一个实施例,为了便于对移动终端进行鉴权,提高信息的安全性,待处理消息还可以包括:移动终端的标识和待处理信息的来源标识。 processed,除了要处理的信息。 [0032]为了灵活地在移动终端上传输待处理信息以满足不同应用场景的需求,在优选实施例中,应用平台在接收到管理平台转发的移动终端待处理消息之前, 所述移动终端的消息控制方法还包括: 移动终端根据传输规则向管理平台发送待处理消息, 其中, 传输规则包括以下至少之一: 指示消息类型的信息 待传输的待处理信息和用于指示传输待传输的待处理信息的过滤条件的信息。 即可以根据用户的习惯或需求设置传输规则; 表示待处理信息的类型的信息,例如,哪些待处理信息需要传输,哪些待处理信息不需要传输,可以根据需要进行设置。 例如,根据需要,可以设置发送短信信息、未接来电等需要处理的信息,可以设置不发送需要处理的QQ信息,还可以设置所有类型的信息。 设置为传输; 并且还可以设置待发送的待处理信息的过滤条件,例如,如果待处理的短消息信息设置为发送,则发送该短消息信息的时间范围 为了方便用户感知待处理的信息,还可以进一步设置待处理的待传输信息。 [0033] 为了满足不同应用场景的需求,提高传输规则设置的灵活性,在优选实施例中,传输规则直接设置在移动终端上; 和/或,应用平台将设置的传输规则发送给移动终端,即可以根据不同的应用场景选择不同的传输规则设置方式,传输规则可以直接在移动终端上设置,可以 也可以通过应用平台进行设置。 在应用平台的应用显示界面进行设置操作,然后应用平台通过管理平台将设置的传输规则发送给移动终端,移动终端根据接收到的传输规则进行设置。 [0034] 为了提高信息的安全性,在优选实施例中,在应用平台接收到管理平台转发的移动终端待处理消息之前,控制移动终端消息的方法还包括: 即:管理平台对待处理的消息进行格式校验,并对移动终端进行订阅关系认证; 在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,管理平台根据移动终端的订阅关系将待处理消息转发给应用平台。 即待处理消息通过格式校验,移动终端通过订阅关系认证后,将待处理消息传输至应用平台,提高了信息的安全性。 [0035]为了正确显示待处理信息,在优选实施例中,应用平台显示待处理信息包括: 应用平台对待处理消息进行权限认证,其中,权限用于指示是否允许。 待处理消息中的待处理信息是否允许在应用平台上展示; 在待处理消息通过权限认证的情况下,应用平台展示待处理信息。 即在确定可以显示待处理信息后,显示待处理信息。 [0036] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,在应用平台显示待处理信息后,控制移动终端消息的方法还包括:应用 平台向管理平台发送待处理信息的回复消息,该回复消息包括:待处理信息的回复信息、移动终端的标识和待处理信息的来源标识; 管理平台对回复消息进行鉴权,在回复消息鉴权通过的情况下,根据回复消息中携带的转发标识将回复消息发送给待处理信息的源设备,或者转发 回复消息给移动终端,回复消息由移动终端发送给待处理信息的源设备。 即用户可以通过管理平台对待处理信息进行处理,并通过管理平台将处理后的依赖报文直接发送给待处理信息的源设备; 还可以通过管理平台对待处理信息进行处理,管理平台将处理后的回复消息转发给移动终端,移动终端自动将接收到的回复消息发送给待处理信息的源设备。 [0037] 为了满足不同用户的应用需求,提高实用性,在优选实施例中,待处理信息可以包括以下至少之一:待处理短信、未接来电、待处理QQ信息、MSN信息 待处理之类的。 [0038] 在本优选实施例中,提供了一种优选的移动终端,如图2所示,该移动终端包括: 获取模块 202 ,用于获取移动终端的待处理信息,并生成待处理消息,所述待处理消息包括所述待处理信息; 和第一传输组件 204 , 连接到获取组件 202 ,用于将所述待处理消息传输至管理平台,并通过所述管理平台将所述待处理消息转发至应用平台,所述应用平台展示所述待处理信息。 [0039] 在优选实施例中,获取组件 202 移动终端上的待处理信息生成待处理消息,第一发送部件 204将待处理的消息传输给管理平台,通过管理平台将待处理的消息转发给应用平台,应用平台将待处理的信息显示在待处理的消息中,以便用户可以 无需订阅运营商的特定服务即可提醒需要处理的信息,提高了移动终端消息控制的灵活性; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0040] 为了满足不同应用场景的需求,提高传输规则设置的灵活性,在优选实施例中,如图3所示,移动终端还包括: 第一设置模块 206 , 用于设置传输规则。 [0041] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,如图3所示,移动终端还包括: 接收模块 208 ,用于接收管理平台转发的对待处理信息的回复消息,其中,回复消息由应用平台发送,回复消息包括对待处理信息的回复信息, 移动终端的标识和待处理信息的来源标识; 和第一个转发组件 210 , 连接到接收组件 208 ,用于将回复消息转发给待处理信息的源设备。 [0042] 在本优选实施例中,还提供了一种优选的移动终端消息控制系统,如图4所示,所述移动终端消息控制系统包括: 移动终端 402 ; 管理平台 404 , 连接到移动端 402 ,用于将移动终端发送的待处理消息转发给应用平台; 和应用平台 406 , 连接到管理平台 404 ,用于接收待处理消息,并显示待处理消息中的待处理信息。 [0043] 在优选实施例中,移动终端 402 利用移动端的待处理信息生成待处理消息 402 , 将待处理的消息传送给管理平台 404 ,并将待处理的消息转发给应用平台 406 通过管理平台 404 , 以及应用平台 406 在待处理消息中显示待处理信息,使用户无需订阅运营商的特定服务即可提醒待处理信息,提高了对移动终端消息的控制灵活性。 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0044] 为了满足不同应用场景的需求,提高传输规则设置的灵活性,在优选实施例中,如图5所示,应用平台包括: 第二设置规则 4062 ,用于设置传输规则,并将设置的传输规则发送给移动终端。 [0045]为了正确显示待处理信息,在优选实施例中,如图5所示,应用平台 406 还包括:第一认证组件 4064 ,用于对所述待处理消息进行权限认证,其中,权限用于指示所述待处理消息中的所述待处理信息是否允许在所述应用平台上展示。 和一个显示组件 4066 , 连接到第一个认证组件 4064 ,用于在待处理消息通过权限认证的情况下,显示待处理信息。 [0046] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,如图5所示,应用平台 406 还包括:第二传输组件 4068 ,用于向所述管理平台发送所述待处理信息的回复消息,所述回复消息包括:所述待处理信息的回复信息、所述移动终端的标识和所述待处理信息的来源标识 处理。 [0047] 为了提高信息的安全性,在优选实施例中,如图6所示,管理平台 404 包括:第二个身份验证组件 4042 ,用于对待处理的消息进行格式检查,并对移动终端进行订阅关系认证; 和第二个转发组件 4044 , 连接到第二个身份验证组件 4042 ,用于在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,根据移动终端的订阅关系将待处理消息转发给应用平台。 [0048] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,第二转发组件 4044 还用于对所述待处理信息的回复消息进行鉴权,在所述回复消息鉴权通过的情况下,根据所述待处理信息中携带的转发标识将所述回复消息发送给所述待处理信息的源设备 回复消息,或者将回复消息转发给移动终端,以便移动终端将回复消息发送给待处理信息的源设备。 [0049] 下面结合附图详细描述每个优选实施例。 [0050] 在本优选实施例中,移动终端以智能手机为例,图7为第四种移动终端消息控制系统的结构图,如图7所示,该消息控制系统为: 移动终端包括:移动终端 702 , 其中移动终端 702 包括漏接信息检测单元,用于接收并处理用户的漏接信息,例如漏接电话信息、漏接短信、漏接QQ信息、漏接MSN信息等。 漏接信息检测单元的功能可以通过软件实现,例如通过某种软件实现漏接短信、漏接电话信息、漏接QQ信息、漏接MSN信息等消息内容,以及漏接消息来源等。 可以从手机中提取手机号、QQ号和MSN号。 消息可以按照设定的模式以一定的格式透传到特定的管理平台(相当于上面的传输规则); 管理平台 704 ,用于进行应用与终端的接入、终端与应用的管理以及终端与应用之间的数据透传; 和应用平台 706 , 其中应用平台 706 可以包括:身份验证组件 7062 (相当于第一个认证组件 4064),用于根据设定的过滤条件对终端与应用之间的消息进行鉴权,后台处理组件 7064 ,用于从管理平台接收用户的遗漏信息,处理并传递给遗漏信息展示组件,所述遗漏信息展示组件 7066 (相当于显示组件 4066 ), 用于显示后台处理组件处理后的信息 7064 . [0051] 通过本发明的移动终端消息控制系统,用户无需开通运营商的某项服务,即可控制手机的某些信息,并可接收短信、知晓未接来电、与某运营商的用户进行通话。 即使在不携带手机的情况下,也可以在手机上使用QQ、MSN等聊天工具。 但是,为了灵活传输待处理信息,可以先在手机上设置短消息、未接来电、QQ消息、MSN消息等待处理消息的传输规则,其中 传输规则表示需要转发哪些消息、转发的过滤条件等; 设置传输规则有两种方式,一种是用户在手机软件上设置传输规则,另一种是通过手机的显示界面(如网页)设置传输规则。 用户的应用平台。 通过应用平台的显示界面设置传输规则可以通过以下步骤实现: [0052] 小号 1 :用户操作应用展示界面,设置转发规则,提交设置的转发规则。 [0053] 小号 2 :应用平台进行消息鉴权,判断用户是否允许使用将待处理信息传送给应用平台的功能。 [0054] 小号 3 :应用后台对认证消息进行处理、打包、转换为与管理平台一致的消息格式。 [0055] 小号 4 :管理平台接收应用平台的鉴权消息,进行订阅关系鉴权等,从鉴权消息中提取移动终端的标识信息,如向哪个用户发送消息,透传 如果满足条件则消息,并转向 S 5 . [0056] 小号 5 :手机终端接收来自管理平台的自动转发消息,解析自动转发消息,根据指令进行自动转发设置。 [0057] 图8是根据本发明实施例的利用移动终端的消息控制方法控制用户的短信和未接来电的流程图,如图8所示,该流程可以包括: 步骤: [0058] 小号 802 :手机终端收到短信(包括飞信短信)和未接来电,将短信(包括飞信短信)和未接来电处理打包成短信,由手机中的软件进行处理 终端,待处理消息包括:手机终端号码,源手机号码和内容(短信内容或未接来电),手机端透传待处理消息数据给管理端 平台。 [0059] 小号 804 :管理平台对待处理的消息进行消息格式校验和订阅关系认证,并根据订阅关系将数据透传给相应的应用平台。 [0060] 小号 806:应用平台的应用后台解析管理平台传来的待处理消息,转换待处理消息的消息格式,将待处理消息传给鉴权组件(相当于第一个) 认证组件 4064 ) 的应用平台。 [0061] 小号 808 :认证组件对接收到的消息进行内部订阅关系认证、权限认证等,并将认证通过的消息内容发送给用户显示组件(相当于显示组件 4066 ). [0062] 小号 810 :用户(用户A)可以在应用平台的显示界面上直接回复短信,如果管理平台可以转发短信或者回复短信,可以选择直接通过管理平台转发回复消息 管理平台无法发送短信时通过手机; 例如,对于回复内容,通过鉴权组件和消息处理组件将消息转发给管理平台。 管理平台根据短信的转发标识将回复消息转发给短信的源手机或手机终端,如果是管理平台转发的,则直接发送回复消息(the transmitted message 包括手机终端号码)通过管理平台认证; 否则,回复消息经管理平台鉴权后转发至手机终端,由手机终端软件进行消息处理,自动发送。 [0063] 在本优选实施例中,该应用场景只是举例说明而不做限定,该应用场景为用户手机登录QQ、MSN等聊天工具,但不能或未随身携带, 且用户所在网络不支持聊天工具的登录, 图9为利用根据本发明的控制移动终端消息的方法控制用户手机QQ/MSN消息的流程图 对于本发明的一个实施例,如图9所示,该流程可以包括以下步骤: [0064] 小号 902 :手机终端接收QQ或MSN消息内容,对QQ或MSN消息内容进行处理,由手机终端中的软件按照时序打包生成待处理消息,其中待处理消息为 处理包括:手机终端号码、源QQ或MSN号码及内容,将待处理消息的数据透传给管理平台。 [0065] 小号 904 :管理平台对待处理的消息进行消息格式校验和订阅关系认证,并根据订阅关系将数据透传给相应的应用平台。 [0066] 小号 906 :应用平台的应用后台解析管理平台传来的待处理消息,转换待处理消息的消息格式,将待处理消息传给鉴权组件(相当于第一个) 认证组件 4064 ) 的应用平台。 [0067] 小号 908 :认证组件对接收到的消息进行内部订阅关系认证、权限认证等,并将认证通过的消息内容发送给用户显示组件(相当于显示组件 4066 ). [0068] 小号 910 :用户回复消息,回复消息经过鉴权模块和消息处理模块处理后,传给管理平台。 [0069] 小号 912:管理平台进行回复消息格式认证、订阅关系认证等,并将数据透传至手机端。 [0070] 小号 914 :手机端提取并格式化回复信息,按时间顺序自动回复QQ/MSN消息。 [0071] 在上述优选实施例中,不需要用户直接在用户手机的界面上处理漏话,用户手机未携带的漏话(待处理信息) 用户可以快速获取用户,用户可以通过应用界面回复消息,提高了用户体验。 [0072] 综上所述,本优选实施例实现了以下技术效果: 移动终端利用移动终端上的待处理信息生成待处理消息,将待处理消息发送给管理平台,转发消息 待处理信息通过管理平台发送至应用平台,应用平台将待处理信息显示在待处理消息中,使用户无需订阅特定服务即可提醒待处理信息 运营商,提高了对移动终端消息控制的灵活性; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0073] 显然,本领域的技术人员应该知道,本发明的各个组成部分或步骤可以由一个通用的计算设备来实现,这些组成部分或步骤可以集中在单个计算设备上,也可以分布在多个计算设备组成的网络上。 设备,并且可以可选地由计算设备可执行的可编程代码来实现,使得组件或步骤可以存储在存储设备中以与计算设备一起执行,或者可以形成每个集成电路组件,或者其中的多个组件或步骤 可以组成一个单一的集成电路元件来实现。 因此,本公开不限于任何特定的硬件和软件组合。 [0074] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明,本领域的技术人员可以对本发明做出各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2884464A1(String), CN103685688A(String), CN103685688B(String), EP2894937A2(String), EP2894937A4(String), US20150249630A1(String), WO2013174353A2(String), WO2013174353A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2884464A1(String), CN103685688A(String), CN103685688B(String), EP2894937A2(String), EP2894937A4(String), US20150249630A1(String), WO2013174353A2(String), WO2013174353A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20150249630A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2884464A1(String), CN103685688A(String), CN103685688B(String), EP2894937A2(String), EP2894937A4(String), US20150249630A1(String), WO2013174353A2(String), WO2013174353A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), CA2884464A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), CN103685688A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.829 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.829 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.830 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), CN103685688B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), EP2894937A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), EP2894937A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), US20150249630A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.872 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), WO2013174353A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270659(Integer), WO2013174353A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20150249630A1(String), US20150249630A1(String), 1441209600(Integer), 270659(Integer), 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184977(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184977(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184977(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184977(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for inputting function of mobile terminal using user's grip posture while holding mobile terminal(String), 使用用户握持移动终端的握持姿势输入移动终端功能的方法和装置(String), US8055305B2(String), An apparatus for and a method of inputting a function of a mobile terminal such as a mobile phone, in which a grip posture of a user who holds the mobile terminal is recognized and a function corresponding to the recognized grip posture is detected. The method includes: recognizing a grip posture of a user who uses the mobile terminal; detecting a function corresponding to the recognized grip posture; and performing the detected function. Accordingly, by considering user's grip postures formed when performing the functions of a mobile terminal such as a mobile phone, specific functions are respectively matched to a plurality of grip postures, a grip posture of a user who is holding the mobile terminal is recognized, and a function corresponding to the recognized grip posture is automatically performed without any operation such as an additional key input operation. Therefore, a complex input unit or input method is not required even when diverse functions are provided by the mobile terminal, and the user can easily and conveniently use the mobile terminal.(String), 一种用于输入诸如移动电话的移动终端的功能的设备和方法,其中识别持有移动终端的用户的握持姿势并且检测与识别的握持姿势相对应的功能。 该方法包括:识别使用移动终端的用户的握持姿势; 检测与识别出的握持姿势对应的功能; 并执行检测到的功能。 因此,通过考虑用户在执行手机等移动终端的功能时形成的握持姿势,将特定功能分别与多个握持姿势相匹配,识别出手持移动终端的用户的握持姿势,并 自动执行与识别的握持姿势对应的功能,无需任何操作,例如额外的键输入操作。 因此,即使移动终端提供多种功能,也不需要复杂的输入单元或输入方法,用户可以轻松方便地使用移动终端。(String), US11/476631(String), 1151510400(Integer), US8055305B2(String), 1320681600(Integer), 1320681600(Integer), 美国(String), 4(Integer), KR(String), 2(Integer), 19(Integer), KR1020060028295A | US20010014616A1 | US20010044318A1 | US20020115469A1 | US20020198006A1 | US20040157647A1 | US20040204016A1 | US20050035955A1 | US20050143124A1 | US20050250553A1 | US20060084482A1 | US20060238513A1 | US20060248478A1 | US20080214250A1 | US6298230B1 | US7098894B2 | US7440003B2 | USRE40116E1(String), 31(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184978(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\9e723102a68743ee94420df36f3e0230.png(String), 184978(Integer), 9e723102a68743ee94420df36f3e0230.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for inputting function of mobile terminal using user's grip posture while holding mobile terminal(String), 使用用户握持移动终端的握持姿势输入移动终端功能的方法和装置(String), US8055305B2(String), An apparatus for and a method of inputting a function of a mobile terminal such as a mobile phone, in which a grip posture of a user who holds the mobile terminal is recognized and a function corresponding to the recognized grip posture is detected. The method includes: recognizing a grip posture of a user who uses the mobile terminal; detecting a function corresponding to the recognized grip posture; and performing the detected function. Accordingly, by considering user's grip postures formed when performing the functions of a mobile terminal such as a mobile phone, specific functions are respectively matched to a plurality of grip postures, a grip posture of a user who is holding the mobile terminal is recognized, and a function corresponding to the recognized grip posture is automatically performed without any operation such as an additional key input operation. Therefore, a complex input unit or input method is not required even when diverse functions are provided by the mobile terminal, and the user can easily and conveniently use the mobile terminal.(String), 一种用于输入诸如移动电话的移动终端的功能的设备和方法,其中识别持有移动终端的用户的握持姿势并且检测与识别的握持姿势相对应的功能。 该方法包括:识别使用移动终端的用户的握持姿势; 检测与识别出的握持姿势对应的功能; 并执行检测到的功能。 因此,通过考虑用户在执行手机等移动终端的功能时形成的握持姿势,将特定功能分别与多个握持姿势相匹配,识别出手持移动终端的用户的握持姿势,并 自动执行与识别的握持姿势对应的功能,无需任何操作,例如额外的键输入操作。 因此,即使移动终端提供多种功能,也不需要复杂的输入单元或输入方法,用户可以轻松方便地使用移动终端。(String), US11/476631(String), 1151510400(Integer), US8055305B2(String), 1320681600(Integer), 1320681600(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 19(Integer), KR1020060028295A | US20010014616A1 | US20010044318A1 | US20020115469A1 | US20020198006A1 | US20040157647A1 | US20040204016A1 | US20050035955A1 | US20050143124A1 | US20050250553A1 | US20060084482A1 | US20060238513A1 | US20060248478A1 | US20080214250A1 | US6298230B1 | US7098894B2 | US7440003B2 | USRE40116E1(String), \20230420\9e723102a68743ee94420df36f3e0230.png(String), 31(Integer), 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 1. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing a grip posture comprises:receiving output signals from a plurality of touch sensors on the mobile terminal; andrecognizing the grip posture using the output signals from the touch sensors, wherein the recognizing the grip posture using the output signals comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, and a distance between adjacent contact points in each portion of the mobile terminal using the sensor output signals; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, and the distance between adjacent contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 1.一种移动终端功能的输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:接收来自移动终端上的多个触摸传感器的输出信号;和利用触摸传感器的输出信号识别握持姿势,其中,利用输出信号识别握持姿势包括:将移动终端的表面分成多个部分;使用传感器输出信号检测移动终端的每个部分中的接触点的数量、每个检测到的接触点的接触宽度以及相邻接触点之间的距离;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度以及移动终端的每个部分中相邻接触点之间的距离来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 2. The method of claim 1, wherein the plurality of touch sensors are arranged on a surface of the mobile terminal at regular intervals.(String), 2.如权利要求1所述的方法,其中多个触摸传感器以规则的间隔排列在移动终端的表面上。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 3. The method of claim 1, wherein the plurality of touch sensors are arranged in each of the portions at different intervals according to how frequently the user touches each portion when the user grips the mobile terminal.(String), 3.如权利要求1所述的方法,其中多个触摸传感器根据用户在握持移动终端时触摸每个部分的频率,以不同的间隔布置在每个部分中。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 4. The method of claim 3, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 4.如权利要求3所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 5. The method of claim 1, wherein, in the recognizing the grip posture using the output signals, the user's grip posture is recognized from the output signals by using one of an artificial neuron network, a template matching, a hidden Markov model, and a support vector machine (SVM).(String), 5.如权利要求1所述的方法,其中,在使用输出信号识别握持姿势中,通过使用人工神经元网络、模板匹配、隐马尔可夫模型和支持向量机(SVM)中的一种从输出信号识别用户的握持姿势。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 6. The method of claim 5, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 6.如权利要求5所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 7. The method of claim 1, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 7.如权利要求1所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 8. The method of claim 1, wherein the grip posture includes at least one of a right hand/vertical grip, a right hand/horizontal grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/horizontal grip, and a left hand/vertical grip.(String), 8.如权利要求1所述的方法,其中握持姿势包括右手/竖握、右手/横握、双手/横握、双手/竖握、左手/横握、左手/竖握中的至少一种.9.如权利要求8所述的方法,其中当识别的握持姿势为右手/竖握时,识别的握持姿势对应的功能为通话功能。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 9. The method of claim 8, wherein the function corresponding to the recognized grip posture is a phone call function when the recognized grip posture is a right hand/vertical grip.(String), 10.如权利要求8所述的方法,其中当识别的握持姿势为双手/竖握时,识别的握持姿势对应的功能为文本输入功能。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 10. The method of claim 8, wherein the function corresponding to the recognized grip posture is a text input function when the recognized grip posture is a both hands/vertical grip.(String), 11.如权利要求8所述的方法,其中当识别的握持姿势为右手/横握时,识别的握持姿势对应的功能为拍照功能。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 11. The method of claim 8, wherein the function corresponding to the recognized grip posture is a photography function when the recognized grip posture is a right hand/horizontal grip.(String), 12.如权利要求8所述的方法,其中当识别的握持姿势为双手/横握时,识别的握持姿势对应的功能为游戏功能。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 12. The method of claim 8, wherein the function corresponding to the recognized grip posture is a game function when the recognized grip posture is a both hands/horizontal grip.(String), 13.如权利要求1所述的方法,其中检测功能包括基于键输入和移动终端的当前功能中的至少一个来检测与识别的握持姿势相对应的多个功能之一。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 13. The method of claim 1, wherein the detecting a function comprises detecting one of plural functions corresponding to the recognized grip posture based on at least one of a key input and a current function of the mobile terminal.(String), 14.如权利要求1所述的方法,还包括,当至少两个函数对应于识别的握持姿势时:显示功能;和在显示的功能中接收用户想要执行的功能。(String), 1(Integer), 12(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 14. The method of claim 1, further comprising, when at least two functions correspond to the recognized grip posture:displaying the functions; andreceiving a function that the user wants to perform among the displayed functions.(String), 15.一种存储用于执行权利要求1的方法的程序的非暂时性计算机可读记录介质。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 15. A non-transitory computer readable recording medium storing a program for executing the method of claim 1.(String), 16.一种移动终端功能的输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:将移动终端的表面分成多个部分;检测移动终端各部分的接触点个数、每个检测到的接触点的接触宽度和相邻接触点之间的距离;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度以及移动终端的每个部分中相邻接触点之间的距离来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 14(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 16. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing the grip posture comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, and a distance between adjacent contact points in each portion of the mobile terminal; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, and the distance between adjacent contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 17.如权利要求16所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 17. The method of claim 16, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 18.一种包含在移动终端中的功能输入装置,该装置包括:握持姿势识别单元,用于识别用户握持移动终端的握持姿势,其中识别出的握持姿势是多种握持姿势中的一种;和功能检测单元,用于检测对应于识别的握持姿势的功能,其中,所述握持姿势识别单元包括:多个触摸传感器;接触检测单元,用于基于来自单独部分中的触摸传感器的输出信号来检测用户是否接触移动终端的表面被划分成的单独部分;和握持姿势确定单元,使用每个部分的检测结果来确定用户的握持姿势,其中,接触检测单元检测接触点的数量、每个检测到的接触点的接触宽度以及每个部分中的相邻接触点之间的距离,并且抓握姿势确定单元使用检测到的接触点的数量来确定用户的抓握姿势,每个检测到的接触点的接触宽度,以及每个部分相邻接触点之间的距离,以及其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 18. A function input apparatus included in a mobile terminal, the apparatus comprising:a grip posture recognition unit to recognize a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture,wherein the grip posture recognition unit comprises:a plurality of touch sensors;a contact detection unit to detect whether the user contacts individual portions into which the surface of the mobile terminal is divided based on output signals from touch sensors in the individual portions; anda grip posture determining unit to determine the user's grip posture using the detection result for each portion,wherein the contact detection unit detects a number of contact points, a contact width of each detected contact point, and a distance between adjacent contact points in each portion, and the grip posture determining unit determines the user's grip posture using the detected number of contact points, the contact width of each detected contact point, and the distance between adjacent contact points at each portion, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 19.如权利要求18所述的功能输入装置,其中多个触摸传感器以一定间隔排列在移动终端表面。(String), 0(Integer), 17(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 19. The function input apparatus of claim 18, wherein the plurality of touch sensors are arranged on the surface of the mobile terminal at regular intervals.(String), 20.如权利要求18所述的功能输入装置,其中多个触摸传感器根据用户在握持移动终端时触摸每个部分的频率,以不同的间隔布置在每个部分上。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:43.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 20. The function input apparatus of claim 18, wherein the plurality of touch sensors are arranged on each of the portions at different intervals according to how frequently the user touches each portion when the user grips the mobile terminal.(String), 21.如权利要求20所述的功能输入装置,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 21. The function input apparatus of claim 20, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 22.如权利要求18所述的功能输入装置,其中抓握姿势识别单元使用人工神经元网络、模板匹配、隐马尔可夫模型和支持向量机(SVM)中的一种来识别用户的抓握姿势。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 22. The function input apparatus of claim 18, wherein the grip posture recognition unit recognizes the user's grip posture using one of an artificial neuron network, a template matching, a hidden Markov model, and a support vector machine (SVM).(String), 23.如权利要求18所述的功能输入装置,其中握持姿势包括右手/横握、右手/竖握、双手/横握、双手/竖握、左手/横握、左手/竖握中的至少一种.24.如权利要求18所述的功能输入装置,其中功能检测单元接收来自用户的键输入,确定移动终端的当前功能,并基于键输入和移动终端的当前功能中的至少一个来检测与识别的握持姿势相对应的多个功能之一.25.如权利要求18所述的功能输入装置,还包括:显示单元向用户显示信息;和用户输入单元接收来自用户的输入,其中,当两个或更多功能对应于识别的握持姿势时,显示单元显示对应于识别的握持姿势的功能,并且用户输入单元接收显示的功能中用户想要执行的功能。(String), 1(Integer), 21(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 23. The function input apparatus of claim 18, wherein the grip posture includes at least one of a right hand/horizontal grip, a right hand/vertical grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/horizontal grip, and a left hand/vertical grip.(String), 26.功能输入装置、装置包括:传感器单元具有多个单独检测用户与移动终端的接触的触摸传感器,检测到的接触定义检测到的握持姿势;抓握姿势识别单元基于从传感器单元检测到的抓握姿势来识别抓握姿势,其中识别出的抓握姿势是多个抓握姿势之一;和功能检测单元,用于检测对应于识别的握持姿势的功能,其中,所述握持姿势识别单元包括:特征提取单元,用于提取检测到的握持姿势的特征数据;和存储器检索部,检索存储器,输出与检测出的握持姿势的特征数据对应的存储在存储器中的特征数据中定义的握持姿势,作为识别出的握持姿势,其中,特征数据包括各部分接触点的个数、检测到的各接触点的接触宽度、各部分相邻接触点之间的距离,用于判断用户的握持姿势,以及其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 22(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 24. The function input apparatus of claim 18, wherein the function detection unit receives a key input from a user, determines a current function of the mobile terminal, and detects one of plural functions corresponding to the recognized grip posture based on at least one of the key input and the current function of the mobile terminal.(String), 27.如权利要求26所述的装置,还包括功能执行单元执行检测到的功能。(String), 1(Integer), 23(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 25. The function input apparatus of claim 18, further comprising:a display unit displaying information to a user; anda user input unit receiving an input from a user,wherein, when two or more functions corresponds to the recognized grip posture, the display unit displays the functions corresponding to the recognized grip posture and the user input unit receives a function that the user wants to perform among the displayed functions.(String), 28.一种移动终端的功能输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:接收来自移动终端上的多个触摸传感器的输出信号;和利用触摸传感器的输出信号识别握持姿势,其中,利用输出信号识别握持姿势包括:将移动终端的表面分成多个部分;使用传感器输出信号检测移动终端的每个部分中的接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及检测到的接触点的总宽度;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及移动终端的每个部分中检测到的接触点的总宽度来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。29、一种移动终端功能的输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:将移动终端的表面分成多个部分;检测接触点的个数,每个检测到的接触点的接触宽度,相邻接触点之间的距离,以及移动终端各部分检测到的接触点的总宽度;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及移动终端的每个部分中检测到的接触点的总宽度来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 24(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 26. A function input apparatus, the apparatus comprising:a sensor unit having a plurality of touch sensors individually detecting a user's contact with the mobile terminal, the detected contact defining a detected grip posture;a grip posture recognition unit to recognize a grip posture based on the detected grip posture from the sensor unit, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture,wherein the grip posture recognition unit comprises:a characteristic extraction unit to extract characteristic data of a detected grip posture; anda memory search unit to search a memory and to output as the recognized grip posture a grip posture which is defined in characteristic data stored in the memory that corresponds to the characteristic data of detected grip posture,wherein the characteristic data comprises a number of contact points in each portion, a contact width of each detected contact point, and a distance between adjacent contact points in each portion, which are used to determine the user's grip posture, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 30.一种包含在移动终端中的功能输入装置,该装置包括:握持姿势识别单元,用于识别用户握持移动终端的握持姿势,其中识别出的握持姿势是多种握持姿势中的一种;和功能检测单元,用于检测对应于识别的握持姿势的功能,其中,所述握持姿势识别单元包括:多个触摸传感器;接触检测单元,用于基于来自单独部分中的触摸传感器的输出信号来检测用户是否接触移动终端的表面被划分成的单独部分;和握持姿势确定单元,使用每个部分的检测结果来确定用户的握持姿势,其中,接触检测单元检测接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及每个部分中检测到的接触点的总宽度,并且抓握姿势确定单元确定用户的抓握使用检测到的接触点数量的姿势、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及每个部分检测到的接触点的总宽度,以及其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 0(Integer), 25(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 27. The apparatus of claim 26, further comprising a function performing unit performing the detected function.(String), 31.一种功能输入装置、装置包括:传感器单元具有多个单独检测用户与移动终端的接触的触摸传感器,检测到的接触定义检测到的握持姿势;抓握姿势识别单元基于从传感器单元检测到的抓握姿势来识别抓握姿势,其中识别出的抓握姿势是多个抓握姿势之一;和功能检测单元,用于检测识别出的握持姿势对应的功能,其中,所述握持姿势识别单元包括:特征提取单元,用于提取检测到的握持姿势的特征数据;和存储器检索部,检索存储器,输出与检测出的握持姿势的特征数据对应的存储在存储器中的特征数据中定义的握持姿势,作为识别出的握持姿势,其中,特征数据包括每个部分的接触点个数、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及每个部分检测到的接触点的总宽度,用于判断用户的握持情况。姿势,和其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 26(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 28. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing a grip posture comprises:receiving output signals from a plurality of touch sensors on the mobile terminal; andrecognizing the grip posture using the output signals from the touch sensors, wherein the recognizing the grip posture using the output signals comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal using the sensor output signals; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, the distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 27(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 29. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing the grip posture comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, the distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 28(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 30. A function input apparatus included in a mobile terminal, the apparatus comprising:a grip posture recognition unit to recognize a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture,wherein the grip posture recognition unit comprises:a plurality of touch sensors;a contact detection unit to detect whether the user contacts individual portions into which the surface of the mobile terminal is divided based on output signals from touch sensors in the individual portions; anda grip posture determining unit to determine the user's grip posture using the detection result for each portion,wherein the contact detection unit detects a number of contact points, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion, and the grip posture determining unit determines the user's grip posture using the detected number of contact points, the contact width of each detected contact point, the distance between adjacent contact points, and a total width of detected contact points at each portion, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 29(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184978(Integer), 31. A function input apparatus, the apparatus comprising:a sensor unit having a plurality of touch sensors individually detecting a user's contact with the mobile terminal, the detected contact defining a detected grip posture;a grip posture recognition unit to recognize a grip posture based on the detected grip posture from the sensor unit, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture, wherein the grip posture recognition unit comprises:a characteristic extraction unit to extract characteristic data of a detected grip posture; anda memory search unit to search a memory and to output as the recognized grip posture a grip posture which is defined in characteristic data stored in the memory that corresponds to the characteristic data of detected grip posture,wherein the characteristic data comprises a number of contact points in each portion, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion, which are used to determine the user's grip posture, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 30(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184978(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application claims the priority of Korean Patent Application No. 10-2005-0056933, filed on Jun. 29, 2005, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method and apparatus for receiving a desired function from a user in a mobile terminal such as a mobile phone, and more particularly, to a method and apparatus for inputting a function of a mobile terminal, in which a grip posture of a user who holds the mobile terminal is recognized and a function corresponding to the recognized grip posture is executed. [0004]2. Description of Related Art [0005]Typically, when using a mobile terminal, a user selects a function such as making a phone call, or sending or receiving a text message, and inputs Korean characters, English characters and numbers using a plurality of buttons included in the mobile terminal. [0006]Recent mobile terminals such as mobile phones have developed to combine the typical main functions of the mobile terminals, which include a phone call and a text message function, with another electronic machine functions. For instance, mobile phones now have various functions such as an MP3 file playing function of an MP3 player, an image recording and viewing function of a digital camera, a digital dictionary function, and a digital TV function. [0007]An increase in functions of mobile terminals usually results in an increase in price, size and complexity, which is not desirable to users. Therefore, it is important to keep the device size as small as possible while maximizing the number of device functions. [0008]Even when it is not difficult to add various functions to mobile terminals or miniaturize the devices for the mobile terminals with the development of technology, technical problems to be solved for providing a user interface that allows users to promptly and easily input complicated functions and control the terminal are increased. For example, a user interface that reduces key input steps necessary for performing a specific function, or easily managing, searching and playing a number of digital contents such as pictures, browsing images, music contents, e-mails, and the like is required. [0009]For instance, to download the latest music ringtones by accessing the Internet wireless using a mobile phone, a user presses a wireless Internet access button, selects, for example, a My Phone Bell menu after accessing the wireless Internet, then selects a Ringtones menu which is a sub menu of the My Phone Bell menu, and finally selects the Latest Ringtones menu which is a sub menu of the Ringtones menu. In this case, the user needs to press buttons a total of four times. [0010]In the case of a mobile terminal, an increase in the number of buttons for inputting a plurality of functions as described above may be impossible due to the limited size of the terminal, and can make a user input operation complicated. Moreover, when the number of buttons for key input is not increased, the number of key pressing times for selecting a specific function is increased. BRIEF SUMMARY [0011]An aspect of the present invention provides a method and apparatus for inputting a function of the mobile terminal in which general grip postures of a user holding the mobile terminal are recognized and a function corresponding to each grip posture is automatically performed without any additional operation such as a key input operation. [0012]According to an aspect of the present invention, there is provided a method of inputting a function of a mobile terminal, the method including: recognizing a grip posture of a user gripping the mobile terminal; detecting a function corresponding to the recognized grip posture; and performing the detected function. [0013]The recognizing of the grip posture may include: receiving output signals from a plurality of touch sensors formed on the mobile terminal; and recognizing the grip posture of the user using the output signals from the touch sensors. [0014]The plurality of touch sensors may be arranged on a surface of the mobile terminal at regular intervals, or the surface of the mobile terminal may be divided into a plurality of portions, and then the plurality of touch sensors may be arranged in each portion of the mobile terminal at different intervals according to how frequently the user touches each portion of the mobile terminal when the user holds the mobile terminal. [0015]The plurality of portions of the mobile terminal may include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side of the mobile terminal. The recognizing of the grip posture using the sensor output signals may comprise: dividing the surface of the mobile terminal into a plurality of portions; detecting at least one of the number of contact points, the contact width, and a distance between adjacent contact points in each portion of the mobile terminal using the sensor output signals; and determining the user's grip posture using at least one of the detected number of contact points, the contact width, and a distance between adjacent contact points in each portion of the mobile terminal. [0016]In the recognizing of the grip posture using the sensor output signals, the user's grip posture may be recognized from the sensor output signals by using one of an artificial neuron network, a template matching, a hidden Markov model, and an SVM (support vector machine). [0017]The recognizing of the grip posture may include: dividing the surface of the mobile terminal into a plurality of portions; detecting at least one of the number of contact points, a contact width, and a distance between adjacent contact points in each portion of the mobile terminal; and determining the user's grip posture using at least one of the detected number of contact points, a contact width, and a distance between adjacent contact points in each portion of the mobile terminal. [0018]The plurality of portions of the mobile terminal may include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side of the mobile terminal. The grip posture may include at least one of a right hand/horizontal grip, a right hand/vertical grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/vertical grip, and a left hand/vertical grip. [0019]A function corresponding to the recognized grip posture may be a phone call function when the recognized grip posture is a right hand/vertical grip, a text input function when the recognized grip posture is a both hands/vertical grip, a photography function when the recognized grip posture is a right hand/horizontal grip, or a game function when the recognized grip posture is a both hands/horizontal grip. [0020]The detecting of the function may include detecting one of the functions corresponding to the recognized grip based on at least one of the key input and the current function of the mobile terminal. [0021]If two or more functions correspond to the recognized grip posture, the method may further include: displaying the functions; and receiving a function that the user wants to perform among the displayed two or more functions. [0022]According to another aspect of the present invention, there is provided a function input apparatus included in a mobile terminal, the apparatus including: a grip posture recognition unit recognizing a grip posture of a user gripping the mobile terminal; a function detection unit detecting a function corresponding to the recognized grip posture; and a function performing unit performing the detected function. [0023]The grip posture recognition unit may include a plurality of touch sensors, and recognize the user's grip posture using output signals of the touch sensors. [0024]The plurality of touch sensors may be arranged on the surface of the mobile terminal at regular intervals, or the surface of the mobile terminal may divided into a plurality of portions, and then the plurality of touch sensors may be arranged on each portion of the mobile terminal at different intervals according to how frequently the user touches each portion of the mobile terminal when the user holds the mobile terminal. [0025]The plurality of portions of the mobile terminal may include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side of the mobile terminal. [0026]The grip posture recognition unit may include: a contact detection unit detecting at least one of the number of contact points, a contact width, and a distance between adjacent contact points in each portion; and a grip posture determining unit determining the user's grip posture using at least one of the detected number of contact points, the contact width, and the distance between adjacent contact points at each portion. [0027]The grip posture recognition unit may recognize the user's grip posture from the sensor output signals using one of an artificial neuron network, a template matching, a hidden Markov model, and an SVM. [0028]The grip posture may include at least one of a right hand/horizontal grip, a right hand/vertical grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/horizontal grip, and a left hand/vertical grip. [0029]A function corresponding to the recognized grip posture may be a phone call function when the recognized grip posture is a right hand/vertical grip, a text input function when the recognized grip posture is a both hands/vertical grip, a photography function when the recognized grip posture is a right hand/horizontal grip, or a game function when the recognized grip posture is a both hands/horizontal grip. [0030]The function detection unit may receive a key input from a user for determine a current function of the mobile terminal when more than one functions are selected by the user's hand grip pattern. Then, the function is determined by combining the key input and the current recognized hand grip pattern. [0031]The function input apparatus may further include: a display unit displaying information to a user; and a user input unit receiving an input from a user, wherein, when two or more functions corresponds to the recognized grip posture, the display unit displays the functions corresponding to the recognized grip posture and the user input unit receives a function that the user wants to perform among the displayed two or more functions from the user. [0032]According to another aspect of the present invention, there is provided a function input apparatus, the apparatus including: a sensor unit having a plurality of touch sensors individually detecting a user's contact with the mobile terminal, the detected contact defining a detected grip posture; a grip posture recognition unit recognizing a grip posture based on the detected grip posture from the sensor unit; and a function detection unit detecting a function corresponding to the recognized grip posture. [0033]The apparatus may further include a function performing unit performing the detected function. [0034]The grip posture recognition unit may include: a characteristic extraction unit extracting characteristic data of a detected grip posture; and a memory search unit searching a memory and outputting as the recognized grip posture a grip posture which is defined in characteristic data stored in the memory that corresponds to the characteristic data of detected grip posture. [0035]Other aspects of the present invention provide computer-readable recording media storing programs for executing the aforementioned methods of the present invention. [0036]Additional and/or other aspects and advantages of the present invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention BRIEF DESCRIPTION OF THE DRAWINGS [0037]The above and/or other aspects and advantages of the present invention will become apparent and more readily appreciated from the following detailed description, taken in conjunction with the accompanying drawings of which: [0038]FIG. 1 is a flowchart illustrating a method of inputting a function into a mobile terminal according to an embodiment of the present invention; [0039]FIGS. 2A and 2B are diagrams for explaining arrangements of touch sensors included in a mobile terminal; [0040]FIG. 3 is a view for explaining a method of dividing user's hands into a plurality of portions for defining a user's grip posture; [0041]FIGS. 4A, 4B, 4C and 4D are views illustrating user's grip postures when holding the mobile terminal; [0042]FIG. 5 is a diagram for explaining a method of defining contact points of the mobile terminal according to the user's grip posture; [0043]FIG. 6 is a flowchart illustrating a function detecting operation of FIG. 1; [0044]FIG. 7 is a block diagram of a function input apparatus of a mobile terminal according to an embodiment of the present invention; and [0045]FIG. 8 is a block diagram of a grip posture recognition unit of the function input apparatus shown in FIG. 7. DETAILED DESCRIPTION OF EMBODIMENTS [0046]Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below to explain the present invention by referring to the figures. [0047]FIG. 1 is a flowchart illustrating a method of inputting a function into a mobile terminal according to an embodiment of the present invention. The method illustrated in FIG. 1 will be, for ease of explanation only, described in connection with FIG. 7, which is a block diagram of a function input apparatus included in a mobile terminal according to an embodiment of the present invention. [0048]Referring to FIGS. 1 and 7, when a user holds the mobile terminal for use, a plurality of touch sensors included in a sensor unit 700 individually detect whether the user touches the mobile terminal and output signals corresponding to the detection results (operation 100). The plurality of touch sensors may be arranged on a surface of the mobile terminal at regular intervals. Alternatively, the surface of the mobile terminal can be divided into several portions, and the touch sensors may be arranged in each portion at different intervals according to the user touch frequency in each portion. Since the average width of an adult's finger is 15 mm, a unit used for each touch sensor sensing whether the user touches the mobile terminal can be, by way of a limiting example, less than about 15 mm. [0049]FIG. 2A is a diagram for explaining an approach of dividing the surface of the mobile terminal for the arrangement of the touch sensors. The surface of the mobile terminal is divided into several portions, that is, a front side 200, a rear side 210, an upper portion 220, a bottom portion 230, a left side 250, and a right side 240. The intervals at which the touch sensors are arranged on the plurality of portions divided as described above are set as follows. [0050]The touch frequency on each portion when the user holds the mobile terminal is detected, and the touch sensors are arranged on the frequently touched portions at relatively small intervals and the touch sensors are arranged on the less frequently touched portions at relatively large intervals. For example, the upper portion 220 and the bottom portion 230 are less touched when the user holds the mobile terminal, and thus, the touch sensors are arranged at relatively larger intervals on the upper portion 220 or the bottom portion 230. Meanwhile, since the left and right sides 240 and 250 are frequently touched, the touch sensors may be arranged at relatively smaller intervals in these regions. [0051]The touch frequency on each divided portion may be determined when a user experimentally holds the mobile terminal to perform all functions available in the mobile terminal several times. [0052]FIG. 2B is a diagram for explaining another approach of dividing the surface of the mobile terminal into a plurality of portions for the arrangement of the touch sensors. The surface of the mobile terminal is divided into a liquid crystal display (LCD) 260, a front side 270, a first rear side portion 280, a second rear side portion 290, a third rear side portion 295, an upper portion 220, a bottom portion 270, a left side 250, and a right side 260. As shown in FIG. 2B, when the surface of the mobile terminal is divided into more portions and the intervals between the touch sensors arranged on each portion are adjusted according to the touch frequency, the touch sensors can be more efficiently used. [0053]A grip posture recognition unit 710 receives output signals from the touch sensors of the sensor unit 700, and recognizes a grip posture of a user who holds the mobile terminal (operation 110). FIG. 8 is a block diagram of the grip posture recognition unit 710. The grip posture recognition unit 710 includes a characteristic extraction unit 800, a memory search unit 810, and a memory 820. [0054]The characteristic extraction unit 800 extracts characteristic data of the grip posture of the user who holds the mobile terminal using the sensor output signals received from the sensor unit 700. The memory 820 stores characteristic data defining the grip postures. The memory search unit 810 searches the memory 820, and outputs as the user's grip posture a grip posture which is defined in the characteristic data stored in the memory 820 and identical to the characteristic data of the user's grip posture that is extracted by the characteristic extraction unit 800. A method of defining the characteristic data of each of the grip postures will be described below. [0055]FIG. 3 illustrates views for explaining an approach of dividing both hands of a user into a plurality of portions for defining grip postures. Each hand is divided into six portions (L1-L6 for the left hand and R1-R6 for the right hand). A grip posture may be defined according to which portions of each hand shown in FIG. 3 touch which portions of the mobile terminal shown in FIG. 2A or 2B. [0056]FIG. 4A illustrates a right hand of the user who is vertically holding the mobile terminal. Table 1 shows which portions of the right hand touch which portions of the mobile terminal. [0057]TABLE 1UpperBottomLeftRightRearportionportionsidesidesideR11R2R31R41R51R6 [0058]In Table 1, the portions of the hands and the mobile terminal marked with ‘1’ are the portions which are in contact with each other. Referring to Table 1, a right hand/vertical grip posture is defined as a pattern where the thumb (R1) of the right hand of the user contacts the right side of the mobile terminal and a middle finger R3, a third finger R4, and a pinky finger R5 of the right hand contact the left side. [0059]The grip posture may be further defined by portions of the hand and the mobile terminal which can contact each other depending on circumstances as shown in Table 2. In table 2, the portions of the right hand that can touch the portions of the mobile terminal depending on circumstances are further marked by ‘*’, which can be added to define the right hand/vertical grip posture of Table 1. [0060]TABLE 2UpperBottomLeftRightRearportionportionsidesidesideR11R2*R31R41R51R6* [0061]Referring to Table 2, the right hand/vertical grip posture may be further defined as a pattern where a forefinger R2 of the right hand can contact the left side of the mobile terminal and a palm R6 of the right hand can contact the right side, in addition to the contacting portions defined in Table 1. [0062]The grip posture defined by combination of the contacting portions of the hand contacting portions of the mobile terminal may be defined by the number of contact points in each portion of the mobile terminal, the width of each contact point, a distance between adjacent contact points, and the width of the contact points. By doing this, the characteristic data of the defined grip posture can be easily extracted from the output signals of the touch sensors. As shown in FIG. 5, it is assumed that, when there are two contact points 500 and 510, the respective widths of contact points 500 and 510 are K1 and K2, the distance between the adjacent contact points 500 and 510 is d12, and the total width of the contact points 500 and 510 is L. [0063]The right hand/vertical grip posture defined in Table 2 may be defined as shown in Table 3. [0064]TABLE 3UpperBottomLeftRightRearportionportionsidesidesideNumber of contact3 or 41 or 2pointsWidth of contact0.5 cm < k1 cm ⁢(X,Y)=X-Y=∑i=1n⁢(xi-yi)2(4) [0089]According to Equations 3 and 4, the input X is classified into a grip posture to which data Y* belongs. [0090]In yet another example of the present embodiment, a grip posture may be recognized using a hidden Markov model. The hidden Markov model is a set of states connected via transitions and output functions associated with each state. A model is composed of two kinds of probabilities: a transition probability needed for transition and an output probability indicating a conditional probability of observing an output symbol included in a finite alphabet at each state. Since similarity between an input pattern and a reference pattern is estimated, the hidden Markov model may provide a plurality of candidates. In addition, since temporal-spatial change is represented with probabilities in a state and a transition, it is not necessary to additionally consider the temporal-spatial change in the reference pattern during a matching process. [0091]Besides the above-described pattern recognition methods, other diverse pattern recognition methods may be used to recognize the user's grip posture using the sensor output signals. [0092]The function detection unit 720 receives the user's grip posture from the grip posture recognition unit 710, and detects a function corresponding to the grip posture (operation 120). A memory (not shown) may store functions corresponding to individual grip patterns recognizable by the grip posture recognition unit 710. The function detection unit 720 may search the memory to detect the function corresponding to the input user's grip posture. [0093]When using a phone call function, a user generally holds the mobile terminal vertically with a right hand as illustrated in FIG. 4B, and thus the right hand/vertical grip posture may correspond to the phone call function. [0094]When using a character input function to send a text message, the user generally holds the mobile terminal vertically with both hands as illustrated in FIG. 4C, and therefore the both hand/vertical grip posture may correspond to the character input function. [0095]When a user plays a game using the mobile terminal, the user typically holds the mobile terminal horizontally with both hands, and hence the both hands/horizontal grip posture may correspond to a game function. [0096]If two or more functions corresponding to the same grip posture are present, the functions may be stored in the memory. [0097]FIG. 6 is a flowchart illustrating an example of the function detecting operation (operation 120). Referring to FIG. 6, the function detection unit 720 searches for a function corresponding to the recognized grip type (operation 600). The function detection unit 720 checks if two or more functions has been found (operation 610). If there are two or more functions found, the function detection unit 720 displays names of the functions on an LCD (not shown) (operation 620). The function detection unit 720 receives a desired function selected from the displayed functions by a user using an input unit such as a keypad formed on the mobile terminal (operation 630). [0098]When the function detection unit 720 finds and outputs the function corresponding to the user's current grip type, the function performing unit 730 performs the detected function (operation 130). In the case of a phone call function, the function performing unit 730 may display a screen for inputting a phone number or searching stored phone numbers on an LCD formed on the mobile terminal. [0099]Embodiments of the present invention include computer-readable code on a computer-readable recording medium. The computer-readable recording medium is any data storage device that can store data which can be thereafter read by a computer system. Examples of the computer-readable recording medium include read-only memory (ROM), and random-access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, optical data storage devices. The computer-readable recording medium can also be distributed over network coupled computer systems so that the computer-readable code is stored and executed in (String), 相关申请的交叉引用 [0001] 本申请要求于2005年6月29日向韩国知识产权局提交的韩国专利申请No.10-2005-0056933的优先权,其公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明涉及一种在移动终端(例如手机)中从用户接收期望功能的方法和装置,更具体地,涉及一种用于输入移动终端的功能的方法和装置,其中握持姿势 识别持有移动终端的用户的姿势,并执行与识别的握持姿势对应的功能。 [0004] 2.相关技术说明 [0005] 通常,当使用移动终端时,用户选择诸如拨打电话或发送或接收文本消息的功能,并使用移动终端中包括的多个按钮输入韩文字符、英文字符和数字。 [0006] 最近的移动终端,例如手机,已经发展为将移动终端的典型主要功能,包括电话和短信功能,与另一种电子机器功能相结合。 例如,现在的手机具有多种功能,例如MP3播放器的MP3文件播放功能、数码相机的图像记录和查看功能、数字词典功能和数字电视功能。 [0007] 移动终端功能的增加通常会导致价格、尺寸和复杂性的增加,这是用户所不希望的。 因此,重要的是保持设备尺寸尽可能小,同时最大限度地增加设备功能的数量。 [0008] 即使随着技术的发展向移动终端添加各种功能或使移动终端的设备小型化并不困难,但提供用户界面以使用户能够快速轻松地输入复杂功能并控制移动终端的技术问题仍需解决。 终端增加。 例如,需要减少执行特定功能或容易地管理、搜索和播放诸如图片、浏览图像、音乐内容、电子邮件等的许多数字内容所需的键输入步骤的用户界面。 [0009] 例如,要通过手机无线上网下载最新的音乐铃声,用户按下无线上网按钮,在接入无线互联网后选择例如我的电话铃菜单,然后选择铃声菜单, 是我的电话铃菜单的子菜单,最后选择最新铃声菜单,它是铃声菜单的子菜单。 在这种情况下,用户总共需要按下按钮四次。 [0010] 在移动终端的情况下,由于终端的尺寸有限,如上所述增加用于输入多个功能的按钮的数量是不可能的,并且会使用户输入操作变得复杂。 此外,当用于键输入的按钮数量不增加时,用于选择特定功能的按键次数增加。 简要概述 [0011] 本发明的一方面提供了一种用于输入移动终端的功能的方法和设备,其中识别持有移动终端的用户的一般握持姿势,并且自动执行与每个握持姿势对应的功能,而无需任何附加操作,例如 一键输入操作。 [0012] 根据本发明的一个方面,提供了一种输入移动终端的功能的方法,该方法包括:识别用户握持移动终端的握持姿势; 检测与识别出的握持姿势对应的功能; 并执行检测到的功能。 [0013] 握持姿势的识别可以包括:接收来自移动终端上形成的多个触摸传感器的输出信号; 使用触控传感器的输出信号识别用户的握持姿势。 [0014]多个触摸传感器可以等间隔排列在移动终端的表面,也可以将移动终端的表面分割成多个部分,然后将多个触摸传感器分别排列在移动终端的每个部分。 当用户手持移动终端时,根据用户触摸移动终端各个部分的频率,移动终端的间隔不同。 [0015] 移动终端的多个部分可以包括移动终端的前侧、后侧、上部、底部、左侧和右侧。 使用传感器输出信号识别握持姿势可以包括: 将移动终端的表面划分为多个部分; 使用传感器输出信号检测移动终端的每个部分中的接触点的数量、接触宽度和相邻接触点之间的距离中的至少一项; 使用检测到的接触点的数量、接触宽度和移动终端的每个部分中相邻接触点之间的距离中的至少一种来确定用户的握持姿势。 [0016] 在使用传感器输出信号识别握持姿势时,可以通过使用人工神经元网络、模板匹配、隐马尔可夫模型和SVM(支持向量机)中的一种从传感器输出信号中识别用户的握持姿势。 )。 [0017] 握持姿势的识别可以包括:将移动终端的表面划分为多个部分; 检测移动终端各部分中接触点的数量、接触宽度和相邻接触点之间的距离中的至少一种; 使用检测到的接触点的数量、接触宽度和移动终端的每个部分中相邻接触点之间的距离中的至少一种来确定用户的握持姿势。 [0018] 移动终端的多个部分可以包括移动终端的前侧、后侧、上部、底部、左侧和右侧。 握持姿势可以包括右手/水平握持、右手/垂直握持、双手/水平握持、双手/垂直握持、左手/垂直握持和左手/垂直握持中的至少一种。 紧握。 [0019] 识别出的握持姿势对应的功能可以是识别出的握持姿势为右手/竖握时的电话功能,识别的握持姿势为双手/竖握时的文字输入功能,识别出的握持姿势时的拍照功能。 握持姿势是右手/水平握持,或者当识别的握持姿势是双手/水平握持时的游戏功能。 [0020] 功能的检测可以包括基于键输入和移动终端的当前功能中的至少一个来检测与识别的握持相对应的功能之一。 [0021] 如果识别出的握持姿势对应两个或多个功能,该方法还可以包括:显示功能; 接收所显示的两个或多个功能中用户想要执行的功能。 [0022] 根据本发明的另一方面,提供了一种包括在移动终端中的功能输入装置,该装置包括: 握持姿势识别单元,识别握持移动终端的用户的握持姿势; 功能检测单元检测与识别出的握持姿势对应的功能; 功能执行单元执行检测到的功能。 [0023] 握持姿势识别单元可以包括多个触摸传感器,并且使用触摸传感器的输出信号来识别用户的握持姿势。 [0024] 多个触摸传感器可以等间隔地设置在移动终端的表面,也可以将移动终端的表面分成多个部分,然后将多个触摸传感器设置在移动终端的各个部分上。 在用户手持移动终端时,根据用户触摸移动终端各个部分的频率,以不同的间隔设置终端。 [0025]移动终端的多个部分可以包括移动终端的前侧、后侧、上部、底部、左侧和右侧。 [0026] 握持姿势识别单元可以包括:接触检测单元,检测每个部分中的接触点的数量、接触宽度和相邻接触点之间的距离中的至少一个; 握持姿势确定单元使用检测到的接触点的数量、接触宽度和每个部分的相邻接触点之间的距离中的至少一个来确定用户的握持姿势。 [0027] 握持姿势识别单元可以使用人工神经元网络、模板匹配、隐马尔可夫模型和SVM中的一种从传感器输出信号中识别用户的握持姿势。 [0028] 握持姿势可以包括右手/水平握持、右手/垂直握持、双手/水平握持、双手/垂直握持、左手/水平握持和左手/垂直握持中的至少一种。 紧握。 [0029] 识别出的握持姿势对应的功能可以是识别出的握持姿势为右手/竖握时的电话功能,识别的握持姿势为双手/竖握时的文字输入功能,识别出的握持姿势时的拍照功能。 握持姿势是右手/水平握持,或者当识别的握持姿势是双手/水平握持时的游戏功能。 [0030] 当用户的手握模式选择了多个功能时,功能检测单元可以接收来自用户的键输入以确定移动终端的当前功能。 然后,通过组合键输入和当前识别的手握模式来确定功能。 [0031] 功能输入装置还可以包括:显示单元,向用户显示信息; 用户输入单元,接收来自用户的输入,其中,当识别出的握持姿势对应两个或更多功能时,显示单元显示与识别出的握持姿势对应的功能,并且用户输入单元接收用户想要的功能 在显示的用户的两个或多个功能中执行。 [0032] 根据本发明的另一方面,提供了一种功能输入装置,该装置包括: 传感器单元,具有多个触摸传感器,分别检测用户与移动终端的接触,检测到的接触定义检测到的握持姿势; 握持姿势识别单元基于从传感器单元检测到的握持姿势识别握持姿势; 功能检测部检测与识别出的把持姿势对应的功能。 [0033] 该设备还可以包括执行检测到的功能的功能执行单元。 [0034] 握持姿势识别单元可以包括:特征提取单元,提取检测到的握持姿势的特征数据; 存储器检索部检索存储器,将与检测出的握持姿势的特征数据对应的存储器中存储的特征数据中定义的握持姿势作为识别握持姿势输出。 [0035] 本发明的其他方面提供了存储用于执行本发明的上述方法的程序的计算机可读记录介质。 [0036] 本发明的附加和/或其他方面和优点将部分地在下面的描述中阐述,并且部分地从描述中显而易见,或者可以通过本发明的实践来了解 附图的简要说明 [0037] 本发明的上述和/或其他方面和优点将从以下结合附图的详细描述中变得明显和更容易理解,其中: [0038] 图1是示出根据本发明实施例的向移动终端输入功能的方法的流程图; [0039] 图2A和图2B是用于说明移动终端所具备的触摸传感器的配置的图。 [0040]图3是用于说明将用户的手分割成多个部分来定义用户的握持姿势的方法的图。 [0041] 图4A, 4 乙, 4 C 和 4 D是说明用户握持移动终端时的握持姿势的图; [0042] 图5是说明根据用户的握持姿势定义移动终端的接触点的方法的图。 [0043] 图6是说明图1的功能检测动作的流程图。 [0044] 图7是根据本发明实施例的移动终端的功能输入装置的框图。 和 [0045] 图8是图7所示的功能输入装置的握持姿势识别部的框图。 具体实施方式 [0046] 现在将详细参考本发明的实施例,其示例在附图中示出,其中相同的附图标记始终指代相同的元件。 下面通过参考附图描述实施例以解释本发明。 [0047] 图1是图示根据本发明实施例的将功能输入到移动终端的方法的流程图。 为了便于说明,将结合图7描述图1所示的方法,图7是根据本发明实施例的移动终端中包括的功能输入装置的框图。 [0048] 参照图1和图7,当用户手持移动终端使用时,传感器单元中包括的多个触摸传感器 700 单独检测用户是否触摸移动终端并输出与检测结果对应的信号(操作 100 )。 多个触摸传感器可以以规则的间隔布置在移动终端的表面上。 或者,也可以将移动终端的表面分成若干部分,根据用户在每一部分的触摸频率,将触摸传感器以不同的间隔排列在每一部分中。 由于成人手指的平均宽度为15mm,作为限制性示例,用于感测用户是否触摸移动终端的每个触摸传感器的单位可以小于约15mm。 [0049] 图2A是用于说明为了配置触摸传感器而划分移动终端的表面的方法的图。 移动终端的表面分为几个部分,即正面 200 , 背面 210 , 上部 220 , 底部 230 , 左侧 250 , 和右侧 240 . 将触摸传感器布置在如上所述划分的多个部分上的间隔设置如下。 [0050] 检测用户手持移动终端时各部位的触摸频率,将触摸传感器以较小的间距布置在频繁触摸的部分上,将触摸传感器以较大的间距布置在触摸频率较低的部分上。 例如,上半部分 220 和底部 230 用户手持移动终端时触摸较少,因此触摸传感器在上部的间距相对较大 220 或底部 230 . 同时,由于左右两侧 240 和 250 对于被频繁触摸的区域,触摸传感器可以以相对较小的间隔布置在这些区域中。 [0051] 每个划分部分的触摸频率可以在用户实验性地握持移动终端执行移动终端中的所有可用功能数次时确定。 [0052] 图2B是用于说明将移动终端的表面划分为多个部分以用于触摸传感器的布置的另一种方法的图。 移动终端的表面分为液晶显示器(LCD) 260 , 正面 270 ,第一后侧部分 280 ,第二后侧部分 290 ,第三后侧部分 295 , 上部220 , 底部 270 , 左侧 250 , 和右侧 260 . 如图2B所示,当移动终端的表面被划分为更多部分,并根据触摸频率调整设置在每个部分上的触摸传感器之间的间隔时,可以更有效地使用触摸传感器。 [0053] 握持姿势识别单元 710 接收来自传感器单元的触摸传感器的输出信号 700 ,并识别持有移动终端的用户的握持姿势(操作 110 )。 图8是握持姿势识别单元的框图 710 . 握持姿势识别单元 710 包括一个特征提取单元 800 , 一个内存搜索单元 810 , 和记忆 820 . [0054] 特征提取单元 800 使用从传感器单元接收的传感器输出信号,提取持有移动终端的用户的握持姿势的特征数据 700 . 记忆 820 存储定义握持姿势的特征数据。 内存搜索单元 810 搜索记忆 820 ,并且将在存储在存储器中的特征数据中定义的握持姿势作为用户的握持姿势输出 820 与特征提取单元提取的用户握持姿势的特征数据相同 800 . 下面将描述定义每个握持姿势的特征数据的方法。 [0055] 图3示出了用于解释将用户的双手分成多个部分以定义握持姿势的方法的视图。 每只手分为六个部分(L 1 -L 6 对于左手和 R 1 -R 6 右手)。 可以根据图3中所示的每只手的哪些部分触摸图2A中所示的移动终端的哪些部分或 2 B. [0056] 图4A图示了垂直握住移动终端的用户的右手。 表1显示了右手的哪些部分触摸了移动终端的哪些部分。 [0057] 表格1 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 1 R2 R3 1 R4 1 R5 1 R6 [0058] 在表1中,手和移动终端标有“1”的部分是相互接触的部分。 参考表 1,右手/垂直握持姿势定义为拇指(R 1 ) 用户右手接触移动终端右侧和中指R 3 , 第三个手指 R 4 , 和一个小指 R 5 右手接触左侧。 [0059] 握持姿势可以进一步由手和移动终端的可以根据情况相互接触的部分定义,如表2所示。在表2中,右手可以接触移动终端的部分的部分取决于 在情况下进一步用'*'标记,可以添加它来定义表1的右手/垂直握持姿势。 [0060] 表 2 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 1 R2 * R3 1 R4 1 R5 1 R6 * [0061] 参见表2,右手/竖握姿势可以进一步定义为食指R 2 右手可以接触到移动终端的左侧和手掌R 6 除了表 1 中定义的接触部分外,右手的手可以接触右侧。 [0062] 由移动终端的手接触部分的接触部分的组合定义的握持姿势可以由移动终端的每个部分中的接触点的数量、每个接触点的宽度、相邻接触点之间的距离、 和接触点的宽度。 通过这样做,可以容易地从触摸传感器的输出信号中提取定义的握持姿势的特征数据。 如图 5 所示,假设当有两个接触点时 500 和 510 , 各自的接触点宽度 500 和 510 是 K 1 和 K 2 , 相邻接触点之间的距离 500 和 510 是 d 12,以及接触点的总宽度 500 和 510 是 L。 [0063] 表 2 中定义的右手/垂直握持姿势可定义如表 3 所示。 [0064] 表3 上 底部 剩下 正确的 后部 部分 部分 边 边 边 联系人数量 3 or 4 1 or 2 积分 接触宽度 0.5 厘米 < k 1 厘米 < (k) 点 k < 10 厘米 总宽度 2 厘米 < 2 厘米 < 接触点 (L) 长 < 9.5 厘米 长 < 11 厘米 之间的距离 d < 3 厘米 d < 3 厘米 联络点(d) [0065] 图4B示出了水平握住移动终端的用户的右手。 在表 4 和表 5 中,定义了右手/水平握持姿势。 [0066] 表 4 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 * R2 1 R3 1 R4 * R5 R6 1 [0067] 表 5 上 底部 剩下 正确的 后部 部分 部分 边 边 边 数量 1 0 or 1 1 1 or 2 联络点 宽度 1 厘米 < 1 厘米 < 1 厘米 < 1 厘米 < 接触点 k < 4 k < 2.5 k < 3.5 k < 8 (k) 厘米 厘米 厘米 厘米 总宽度 1 厘米 < 1 厘米 < 1 厘米 < 1 厘米 < 联络点 L < 4 L < 2.5 L < 3.5 L < 10 (L) 厘米 厘米 厘米 厘米 距离 d < 2 之间 厘米 接触 (d) 点 [0068] 图4C示出了垂直握住移动终端的用户的双手。 在表6和表7中,定义了图4C所示的双手/垂直握持姿势。 [0069] 表 6 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 R2 * 1 R3 * 1 R4 * R5 R6 1 L1 L2 * 1 L3 * 1 L4 * L5 L6 1 [0070] 表 7 上 底部 剩下 正确的 后部 部分 部分 边 边 边 数量 1, 2 or 3 1, 2, or 4, 5, or 联络点 3 6 宽度 1 厘米 < 1 厘米 < 0.5 厘米 < 接触点 k < 10 厘米 k < 10 厘米 k < 10 厘米 (k) 总宽度 1 厘米 < 1 厘米 < 长 < 10 厘米 联络点 长 < 10 厘米 长 < 10 厘米 (L) 距离 0.5 厘米 < 0.5 厘米 < 0.5 厘米 < 之间 d < 8 厘米 d < 8 厘米 d < 7 厘米 接触 (d) 点 [0071] 图4D示出了水平握住移动终端的用户的双手。 在表8和表9中,定义了图4D所示的双手/水平握持姿势。 [0072] 表 8 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 R2 * R3 1 R4 1 R5 R6 * L1 L2 * L3 1 L4 * L5 L6 * [0073] 表 9 上 底部 剩下 正确的 后部 部分 部分 边 边 边 数量 0 or 1 0 or 1 3-6 联络点 宽度 1 厘米 < 1 厘米 < 0.5 厘米 < 接触点 k < 4 厘米 k < 4 厘米 k < 7 厘米 (k) 总宽度 1 厘米 < 1 厘米 < 长 < 11 厘米 联系方式 长 < 4 厘米 长 < 4 厘米 点数 (L) 距离 0.5 厘米 < 之间 d < 9 厘米 联络点 (d) [0074] 如上所述定义的每个握持姿势的特征数据存储在存储器中 820 ,以及特征提取单元 800 提取用户当前握持姿势的特征数据,该特征数据与内存中存储的特征数据一致 820 ,来自接收到的传感器输出信号。 [0075] 特征提取单元 800 可以使用接收到的传感器输出信号提取每个部分中的接触点的数量、每个接触点的宽度、相邻接触点之间的距离以及接触点的总宽度。 [0076] 握持姿势识别单元 710 可以使用模式识别方法从接收到的传感器输出信号中识别用户的握持姿势。 [0077] 模式识别方法可以包括以下过程。 [0078] 首先,从用户那里收集大量关于 {input X, class C} 的数据。 然后,将收集到的数据分为学习数据和测试数据。 接下来,将学习数据提供给模式识别系统,并执行学习操作。 模式识别系统的模型参数根据学习数据而改变。 然后,只有输入 X 被提供给模式识别系统,因此系统输出 C 类。 [0079] 根据本实施例的示例,模式识别方法可以使用人工神经元网络。 人工神经元网络是通过简化生物的神经传递过程并对其进行数学分析而获得的模型。 在人工神经网络中,通过根据连接类型调整神经元之间连接的权重的学习过程来分析操作。 这个过程类似于人们学习和记忆的过程。 通过这个过程,可以进行推理、分类、预测等。 在人工神经网络中,一个神经元对应一个节点,神经元之间的连接强度对应于节点间弧上的权重。 人工神经网络可以是包括多个单层感知器的多层感知器神经网络并且可以使用反向传播学习来学习。 [0080] 反向传播学习是通过将 Widrow-Hoff 学习规则推广到多层网络和非线性可微传递函数来实现的,通常用于字符识别和非线性预测。 神经网络中的每个节点使用多个不同的可微传递函数之一来生成输出。 公式 1 中所示的对数 sigmoid 传递函数 (logsig) 使用最广泛。 [0081] f ⁡ ( x ) = 1 1 + ⅇ - x ( 1 ) [0082] 该函数根据从负无穷到正无穷的输入值输出一个从 0 到 1 的值。 在使用反向传播算法减小期望输出值和实际输出值之间的偏差的同时学习期望函数。 [0083]当从传感器输出的信号输入到人工神经网络输入层上的节点时,信号在每个节点中发生变化,然后传输到中间层。 以同样的方式,信号被传输到最后一层,输出一个运动模式。 节点之间的连接强度(以下称为“节点连接强度”)被调整为使得从人工神经网络输出的激活值与在学习期间为各个模式定义的激活值之间的差异减小。 另外,根据delta学习规则,下层根据上层的反向传播结果来调整节点连接强度,以使误差最小化。 根据增量学习规则,调整节点连接强度,使得输入/输出函数最小化目标输出与从包括非线性神经元在内的网络中的所有单个输入模式获得的输出之间的误差平方和。 [0084] 在通过上述学习过程学习所有预定握持姿势后,人工神经网络接收来自传感器单元的运动信号 700 (图7)并将该信号识别为预定握持姿势之一。 [0085] 必要时,可以根据用户的选择操作人工神经网络以重新学习握持姿势。 例如,当用户选择要重新学习的握持姿势并多次做出与选择的握持姿势对应的动作时,人工神经网络可以重新学习反映用户做出的动作的握持姿势。 [0086] 在本实施例的另一示例中,可以使用SVM(支持向量机)来识别用户的握持姿势。 这里,N维向量空间由运动信号的N维特征形成。 在根据学习数据找到合适的超平面后,可以使用超平面对模式进行分类。 每个模式都可以由公式 2 定义。 类=1 如果 W T X+b≥ 0 类=0 如果 W T X+b< 0  (2) 其中 W 是权重矩阵,X 是输入向量,b 是偏移量。 [0087] 在本实施例的又一示例中,可以使用模板匹配来识别握持姿势。 在这种情况下,在从学习数据中选择用于分类握持姿势的模板数据之后,找到与当前输入最接近的模板数据项,并将当前输入分类为与该模板数据项对应的握持姿势。 换句话说,关于输入数据 X=P(x 1 , . . . X n ) 和第 i 个数据项 Y i =P(y 1 , . . . 是的 n ) 在学习数据中,Y* 可以定义为 Y *=分钟 i 距离( X,Y i )  (3) 其中距离 (X, Y) 可以使用 [0088] Distance ⁢ ⁢ ( X , Y ) = X - Y = ∑ i = 1 n ⁢ ( x i - y i ) 2 ( 4 ) [0089] 根据等式3和4,输入X被分类为数据Y*所属的握持姿势。 [0090] 在本实施例的又一示例中,可以使用隐马尔可夫模型来识别握持姿势。 隐马尔可夫模型是一组通过与每个状态相关的转换和输出函数连接的状态。 模型由两种概率组成:转移所需的转移概率和指示在每个状态下观察包含在有限字母表中的输出符号的条件概率的输出概率。 由于估计输入模式和参考模式之间的相似性,隐马尔可夫模型可以提供多个候选。 另外,由于时间-空间变化是用状态和转移的概率来表示的,所以在匹配过程中不需要额外考虑参考模式的时间-空间变化。 [0091] 除了上述模式识别方法之外,其他多种模式识别方法可以用于使用传感器输出信号来识别用户的握持姿势。 [0092] 功能检测单元 720 从握持姿势识别单元接收用户的握持姿势 710,并检测与握持姿势对应的功能(操作 120 )。 存储器(未示出)可以存储与握持姿势识别单元可识别的各个握持模式相对应的功能 710 . 功能检测单元 720 可以搜索内存以检测与输入的用户的握持姿势对应的功能。 [0093] 在使用电话功能时,用户一般如图4B所示用右手垂直握持移动终端,因此右手/垂直握持姿势可以对应电话功能。 [0094] 在使用字符输入功能发送短信时,用户一般如图4C所示,双手垂直握持移动终端,因此双手/垂直握持姿势可以对应字符输入功能。 [0095] 当用户使用移动终端玩游戏时,用户通常双手水平握持移动终端,因此双手/水平握持姿势可以对应游戏功能。 [0096] 如果存在对应于相同握持姿势的两个或更多个功能,则可以将这些功能存储在存储器中。 [0097] 图6是表示功能检测动作的一个例子的流程图(动作 120 )。 参见图6,功能检测单元 720 搜索与识别的握持类型对应的功能(操作 600 )。 功能检测单元 720 检查是否找到了两个或多个函数(操作 610 )。 如果发现两个或更多功能,功能检测单元 720 在 LCD 上显示功能名称(未显示)(操作 620 )。 功能检测单元 720 接收用户使用移动终端上形成的键盘等输入单元从显示的功能中选择的所需功能(操作 630 )。 [0098] 当功能检测单元 720 查找并输出用户当前握持类型对应的功能,功能执行单元 730 执行检测到的功能(操作 130 )。 在电话功能的情况下,功能执行单元 730 可以在移动终端上形成的LCD上显示用于输入电话号码或搜索存储的电话号码的屏幕。 [0099] 本发明的实施例包括计算机可读记录介质上的计算机可读代码。 计算机可读记录介质是可以存储数据的任何数据存储设备,该数据随后可以被计算机系统读取。 计算机可读记录介质的示例包括只读存储器(ROM)和随机存取存储器(RAM)、CD-ROM、磁带、软盘、光学数据存储设备。 计算机可读记录介质还可以分布在网络耦合的计算机系统上,使得计算机可读代码以分布式方式存储和执行。 [0100] 根据本发明的上述实施例,在使用用户的握持姿势在移动终端中输入功能的装置和方法中,考虑了在执行诸如移动电话的移动终端的功能时形成的用户握持姿势 ,具体功能分别与多种握持姿势相匹配。 当用户手持移动终端时,识别用户的握持姿势,并自动执行与识别的握持姿势对应的功能,而无需任何额外的操作,例如按键输入操作。 因此,即使当移动终端提供多种功能时,也不需要复杂的输入单元或输入方法,并且用户可以容易且方便地使用移动终端。 [0101] 尽管已经示出和描述了本发明的几个实施例,但是本发明不限于所描述的实施例。 相反,本领域技术人员应当理解,可以对这些实施例进行改变而不背离本发明的原理和精神,本发明的范围由权利要求及其等同物限定。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100668341B1(String), KR1020070001440A(String), US20070002016A1(String), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100668341B1(String), KR1020070001440A(String), US20070002016A1(String), US8055305B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100668341B1(String), KR1020070001440A(String), US20070002016A1(String), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270660(Integer), KR100668341B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270660(Integer), KR1020070001440A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270660(Integer), US20070002016A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270660(Integer), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8055305B2(String), US8055305B2(String), 1320681600(Integer), 270660(Integer), 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184978(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184978(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184978(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184978(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.371 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.371 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.371 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.372 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.373 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.373 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.374 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.374 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.374 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7561063B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminals including location management systems and location management methods for mobile terminals(String), 移动终端,包括位置管理系统和移动终端的位置管理方法(String), US7561063B2(String), Methods of managing a location of a mobile terminal include obtaining a position of the mobile terminal, estimating a distance from the mobile terminal to a destination point, generating an estimated time for the mobile terminal to reach the destination point, and generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. Related mobile terminals are also disclosed.(String), 管理移动终端位置的方法包括获取移动终端的位置、估计从移动终端到目的地点的距离、生成移动终端到达目的地点的估计时间、以及如果发生移动终端则生成警报。 移动终端到达目的地点的估计时间达到阈值时间。 还公开了相关的移动终端。(String), US11/714053(String), 1173024000(Integer), US7561063B2(String), 1247500800(Integer), 1247500800(Integer), 美国(String), 4(Integer), 11(Integer), 8(Integer), US20030060979A1 | US20050165543A1 | US5790974A | US6360101B1 | US6958692B1 | WO2001029512A1 | WO2002015148A1 | WO2002071365A1(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184979(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\280a25202da04cc197474f9dda8f6dac.png(String), 184979(Integer), 280a25202da04cc197474f9dda8f6dac.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.420 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.421 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.422 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminals including location management systems and location management methods for mobile terminals(String), 移动终端,包括位置管理系统和移动终端的位置管理方法(String), US7561063B2(String), Methods of managing a location of a mobile terminal include obtaining a position of the mobile terminal, estimating a distance from the mobile terminal to a destination point, generating an estimated time for the mobile terminal to reach the destination point, and generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. Related mobile terminals are also disclosed.(String), 管理移动终端位置的方法包括获取移动终端的位置、估计从移动终端到目的地点的距离、生成移动终端到达目的地点的估计时间、以及如果发生移动终端则生成警报。 移动终端到达目的地点的估计时间达到阈值时间。 还公开了相关的移动终端。(String), US11/714053(String), 1173024000(Integer), US7561063B2(String), 1247500800(Integer), 1247500800(Integer), 美国(String), 3(Integer), 4(Integer), 11(Integer), 8(Integer), US20030060979A1 | US20050165543A1 | US5790974A | US6360101B1 | US6958692B1 | WO2001029512A1 | WO2002015148A1 | WO2002071365A1(String), \20230420\280a25202da04cc197474f9dda8f6dac.png(String), 17(Integer), 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 1. A method of managing a location of a mobile terminal, comprising:obtaining a position of the mobile terminal measuring a current speed of the mobile terminal;estimating a distance from the mobile terminal to a destination point wherein estimating the distance from the mobile terminal to a destination point comprises generating a route between the position of the mobile terminal and the destination point based on a movement constraint of the mobile terminal;generating an estimated time for the mobile terminal to reach the destination point wherein generating the estimated time for the mobile terminal to reach the destination point comprises generating the estimated time in response to the current speed of the mobile terminal and the generated route; andgenerating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time.(String), 1.一种移动终端位置管理方法,包括:获取移动终端的位置,测量移动终端的当前速度;估计移动终端到目的地点的距离其中,估计移动终端到目的地点的距离包括基于移动终端的移动约束生成移动终端的位置和目的地点之间的路线;生成移动终端到达目的地点的预估时间,其中生成移动终端到达目的地点的预估时间包括响应于移动终端的当前速度和生成的路线生成预估时间;和如果移动终端到达目的地点的估计时间达到阈值时间,则生成警报。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 2. The method of claim 1, wherein generating the route is performed in response to an operational mode of the mobile terminal.(String), 2.如权利要求1所述的方法,其中生成路线是响应于移动终端的操作模式而执行的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 3. The method of claim 2, wherein the operational mode comprises a pedestrian operational mode, and wherein the movement constraint comprises at least one of a building, a bridge, a gate, or a fence.(String), 3.如权利要求2所述的方法,其中操作模式包括行人操作模式,并且其中运动限制包括建筑物、桥梁、大门或栅栏中的至少一个。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 4. The method of claim 2, wherein the operational mode comprises a vehicular operational mode, and wherein the movement constraint comprises a road.(String), 4.如权利要求2所述的方法,其中操作模式包括车辆操作模式,并且其中移动约束包括道路。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 5. The method of claim 1, wherein generating the estimated time for the mobile terminal to reach the destination point comprises generating the estimated time assuming the mobile terminal travels the route at an average speed and/or at a maximum speed.(String), 5.如权利要求1所述的方法,其中生成移动终端到达目的地点的估计时间包括假设移动终端以平均速度和/或最大速度行进路线来生成估计时间。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 6. The method of claim 1, further comprising:obtaining traffic information indicative of traffic in an area between the mobile terminal and the destination point;wherein generating the estimated time for the mobile terminal to reach the destination point comprises generating the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point.(String), 6.如权利要求1所述的方法,还包括:获取指示移动终端和目的地点之间的区域中的交通的交通信息;其中生成移动终端到达目的地点的估计时间包括响应于移动终端的位置和目的地点之间的区域中的交通生成估计时间。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 7. The method of claim 6, wherein generating the route comprises generating a quickest route between the position of the mobile terminal and the destination point in response to the traffic in the area between the mobile terminal and the destination point.(String), 7.如权利要求6所述的方法,其中生成路线包括响应于移动终端和目的地点之间的区域中的交通生成移动终端的位置和目的地点之间的最快路线。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 8. The method of claim 1, wherein generating the alert comprises generating the alert if the estimated time for the mobile terminal to reach the destination point exceeds the threshold time.(String), 8.如权利要求1所述的方法,其中生成警报包括如果移动终端到达目的地点的估计时间超过阈值时间则生成警报。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 9. The method of claim 1, wherein generating the alert comprises generating the alert if the estimated time for the mobile terminal to reach the destination point is less than the threshold time.(String), 9.如权利要求1所述的方法,其中生成警报包括如果移动终端到达目的地点的估计时间小于阈值时间则生成警报。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 10. The method of claim 1, further comprising displaying an information box associated with the mobile terminal, the information box comprising an estimated time for the mobile terminal to reach the destination point.(String), 10.如权利要求1所述的方法,还包括显示与移动终端相关联的信息框,该信息框包括移动终端到达目的地点的估计时间。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 11. The method of claim 1, further comprising dynamically updating the geo-temporal boundary in response to a passage of time.(String), 11.如权利要求1所述的方法,还包括动态更新地理时间边界以响应时间的流逝。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 12. A method of managing locations of a plurality of mobile terminals, comprising:obtaining positions of the plurality of mobile terminals measuring a current speed of the mobile terminal;estimating distances from the plurality of mobile terminals to a destination point wherein estimating the distances from the plurality of mobile terminals to a destination point comprises generating routes between the positions of the mobile terminals and the destination point based on movement constraints of the mobile terminals;generating estimated times for the mobile terminals to reach the destination point wherein generating the estimated times for the mobile terminals to reach the destination point comprises generating the estimated times in response to the current speeds of the mobile terminals and the generated routes; andgenerating an alert if the estimated time for at least one of the mobile terminals to reach the destination point reaches a threshold time.(String), 12.一种管理多个移动终端位置的方法,包括:测量移动终端的当前速度,获取多个移动终端的位置;估计多个移动终端到目的地点的距离其中,估计多个移动终端到目的地点的距离包括基于移动终端的移动约束生成移动终端的位置和目的地点之间的路线;生成移动终端到达目的地点的估计时间,其中生成移动终端到达目的地点的估计时间包括响应于移动终端的当前速度和生成的路线生成估计时间;和如果至少一个移动终端到达目的地点的估计时间达到阈值时间,则生成警报。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 13. A mobile terminal, comprisinga location management unit configured to obtain a position of a mobile terminal; anda controller configured to estimate a distance from the position of the mobile terminal to a destination point by generating a route between the position of the mobile terminal and the destination point based on a movement constraint of the mobile terminal, configured to measure a current speed of the mobile terminal, configured to generate an estimated time for the mobile terminal to reach the destination point in response to the current speed of the mobile terminal and the generated route, and configured to generate an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time.(String), 13.移动终端,包括位置管理单元,用于获取移动终端的位置;和控制器被配置为通过基于移动终端的移动约束生成移动终端的位置与目的地点之间的路线来估计从移动终端的位置到目的地点的距离,被配置为测量当前速度移动终端,用于响应于移动终端当前的速度和生成的路线,生成移动终端到达目的地点的预计时间,如果移动终端预计到达时间,则生成提醒目的点到达阈值时间。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 14. The mobile terminal of claim 13, further comprising:a traffic information unit configured to obtain traffic information indicative of traffic in an area between the position of the mobile terminal and the destination point;wherein the controller is further configured to generate the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point.(String), 14.如权利要求13所述的移动终端,还包括:交通信息单元,被配置为获取指示移动终端的位置和目的地点之间的区域中的交通的交通信息;其中,控制器还被配置为响应于移动终端的位置和目的地点之间的区域中的交通来生成估计时间。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 15. The mobile terminal of claim 13, wherein the controller is further configured to calculate a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and a rate of motion of the mobile terminal.(String), 15.如权利要求13所述的移动终端,其中控制器还被配置为响应于移动终端的位置、目的地点的位置和移动终端的运动速率来计算目的地点周围的时空边界。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 16. The mobile terminal of claim 13, further comprising a map database, wherein the controller is further configured to generate a route between the position of the mobile terminal and the destination point in response to map information stored in the map database.(String), 16.如权利要求13所述的移动终端,还包括地图数据库,其中,控制器还被配置为响应于存储在地图数据库中的地图信息生成移动终端的位置和目的地点之间的路线。(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184979(Integer), 17. A method of managing a location of a mobile terminal, comprising:obtaining a position of the mobile terminal;measuring a current speed of the mobile terminal;estimating a distance from the mobile terminal to a destination point;generating an estimated time for the mobile terminal to reach the destination point;generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time;calculating a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and the current speed of motion of the mobile terminal, wherein the geo-temporal boundary indicates a farthest distance that the mobile terminal can be from the destination point while still being less than the threshold time away from reaching the destination point; anddisplaying the geo-temporal boundary on a display screen of the mobile terminal.(String), 17.一种管理移动终端位置的方法,包括:获取移动终端的位置;测量移动终端的当前速度;估计从移动终端到目的地点的距离;生成移动终端到达目的地点的预计时间;如果移动终端到达目的地点的估计时间达到阈值时间,则产生警报;响应于移动终端的位置、目的地点的位置和移动终端的当前运动速度计算目的地点周围的时空边界,其中,时空边界表示距离移动终端最远的距离。移动终端可以在距离到达目的地点的距离小于阈值时间的情况下离开目的地点;和在移动终端的显示屏上显示时空边界。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184979(Integer), FIELD OF THE INVENTION [0001]The present invention relates to wireless communication terminals, and more particularly, to wireless communication terminals including functionality for determining the location of the terminal. BACKGROUND [0002]Wireless communication terminals are typically purchased by a user for the purpose of obtaining access to wireless telephone services through a cellular telephone network. However, as the capabilities of communication mobile terminals increase, an additional level of user functionality is being included in the hardware and/or software of such mobile terminals. For example, a communication terminal may be provided with a still and/or video camera, allowing pictures and/or videos to be taken by a user and transmitted from the mobile terminal to others. Likewise, many communication terminals include personal digital assistant (PDA) type applications suitable for tracking scheduling, tasks and the like. Many communication terminals also include messaging capability, such as electronic mail (e-mail), short message service (SMS) and multimedia message service (MMS) capabilities. Communication terminals may also be capable of connecting to the internet by using internet protocol (IP) over wireless and/or wired networks. [0003]Communication terminals are also increasingly being provided with the capability of determining the physical location of the terminal. For example, many communication terminals include global positioning system (GPS) receivers that permit the terminals to determine their location with a high degree of precision. Other systems for determining the location of a communication terminal have been implemented, including systems that obtain location information from a cellular communications network, and systems that obtain location information through inertial guidance techniques. SUMMARY [0004]Some embodiments of the invention provide methods of managing a location of a mobile terminal. The methods include obtaining a position of the mobile terminal, estimating a distance from the mobile terminal to a destination point, generating an estimated time for the mobile terminal to reach the destination point, and generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. [0005]Estimating a distance from the mobile terminal to a destination point may include generating a route between the position of the mobile terminal and the destination point based on a movement constraint of the mobile terminal. Generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time based on the generated route. [0006]Generating the route may be performed in response to an operational mode of the mobile terminal. The operational mode may include a pedestrian operational mode, and the movement constraint may include at least one of a building, a bridge, a gate, or a fence. In some embodiments, the operational mode may include a vehicular operational mode, and the movement constraint may include a road. [0007]The methods may further include measuring a current speed of the mobile terminal, and generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time in response to the current speed. In some embodiments, generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time assuming the mobile terminal travels the route at an average speed and/or a maximum speed. [0008]The methods may further include obtaining traffic information indicative of traffic in an area between the mobile terminal and the destination point. Generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point. [0009]Generating the route may include generating a quickest route between the position of the mobile terminal and the destination point in response to the traffic in the area between the mobile terminal and the destination point. [0010]Generating the alert may include generating the alert if the estimated time for the mobile terminal to reach the destination point exceeds the threshold time. In some embodiments, generating the alert may include generating the alert if the estimated time for the mobile terminal to reach the destination point is less than the threshold time. [0011]The methods may further include calculating a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and a rate of motion of the mobile terminal. The methods may further include displaying the geo-temporal boundary on a display screen of the mobile terminal. [0012]The methods may further include receiving a user input designating the destination point, and generating a route between the position of the mobile terminal and the destination point. [0013]The methods may further include displaying an information box associated with the mobile terminal, the information box including an estimated time for the mobile terminal to reach the destination point. The methods may further include dynamically updating the geo-temporal boundary in response to a passage of time. [0014]Methods of managing locations of a plurality of mobile terminals according to some embodiments of the invention include obtaining positions of the plurality of mobile terminals, estimating distances from the plurality of mobile terminals to a destination point, generating estimated times for the mobile terminals to reach the destination point, and generating an alert if the estimated time for at least one of the mobile terminals to reach the destination point reaches a threshold time. [0015]A mobile terminal according to some embodiments of the invention includes a location management unit configured to obtain a position of a mobile terminal, and a controller. The controller is configured to estimate a distance from the position of the mobile terminal to a destination point, configured to generate an estimated time for the mobile terminal to reach the destination point, and configured to generate an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. [0016]The mobile terminal may further include a traffic information unit configured to obtain traffic information indicative of traffic in an area between the position of the mobile terminal and the destination point. The controller may be further configured to generate the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point. [0017]The controller may be further configured to calculate a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and a rate of motion of the mobile terminal. [0018]The mobile terminal may further include a map database, and the controller may be further configured to generate a route between the position of the mobile terminal and the destination point in response to map information stored in the map database. BRIEF DESCRIPTION OF THE DRAWINGS [0019]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate certain embodiment(s) of the invention. In the drawings: [0020]FIG. 1 is a schematic block diagram illustrating wireless communication terminals and a cellular communication system in accordance with some embodiments of the present invention. [0021]FIG. 2 is a schematic block diagram illustrating some aspects of a wireless communication terminal in accordance with some embodiments of the present invention. [0022]FIG. 3 is a schematic block diagram illustrating some aspects of a wireless communication terminal in accordance with some embodiments of the present invention. [0023]FIGS. 4-8 are exemplary illustrations of display screens configured according to some embodiments of the invention. [0024]FIGS. 9-11 are flow diagrams illustrating operations of communication terminals according to some embodiments of the invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION [0025]The present invention now will be described more fully with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein the term “comprising” or “comprises” is open-ended, and includes one or more stated elements, steps and/or functions without precluding one or more unstated elements, steps and/or functions. As used herein the term “and/or” includes any and all combinations of one or more of the associated listed items. [0026]Embodiments according to the present invention are described with reference to block diagrams and/or operational illustrations of methods and communication terminals. It is to be understood that each block of the block diagrams and/or operational illustrations, and combinations of blocks in the block diagrams and/or operational illustrations, can be implemented by radio frequency, analog and/or digital hardware, and/or program instructions. These program instructions may be provided to a controller, which may include one or more general purpose processors, special purpose processors, ASICs, and/or other programmable data processing apparatus, such that the instructions, which execute via the controller and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or operational block or blocks. In some implementations, the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. [0027]As used herein, a “communication terminal” (or simply a “terminal”) includes, but is not limited to, a device that is configured to receive/transmit communication signals via a wireline connection, such as via a public-switched telephone network (PSTN), digital subscriber line (DSL), digital cable, a direct cable connection, and/or another data connection/network, and/or via a wireless interface with, for example, a cellular network, a wireless local area network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM/FM broadcast transmitter, and/or another communication terminal. A communication terminal that is configured to communicate over a wireless interface may be referred to as a “wireless communication terminal,” a “wireless terminal” and/or a “mobile terminal.” Examples of mobile terminals include, but are not limited to, a satellite or cellular radiotelephone; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and a conventional laptop and/or palmtop receiver or other appliance that includes a radiotelephone transceiver. [0028]Wireless communication between electronic devices may be accomplished using a wide variety of communication media, communication systems and communication standards. For example, portable electronic devices such as mobile telephones are typically configured to communicate via analog and/or digital wireless radio frequency (RF) telephone systems. Such devices may additionally be configured to communicate using wired and/or wireless local area networks (LANs), short range communication channels, such as Bluetooth RF communication channels and/or infrared communication channels, and/or long range communication systems, such as satellite communication systems. [0029]FIG. 1 is a schematic block diagram of a wireless communication system 100 that includes two communication terminals 102, 104 that are configured to communicate data with one another over a direct wireless communication interface 106, over another wireless communication interface 108 through one or more cellular base stations 110a-b, and/or over another wireless communication interface 112 through a wireless local area network (WLAN) access point 114. The direct wireless communication interface 106 may include an RF wireless communication interface such as a Bluetooth interface or an infrared communication interface, such as, for example, the infrared communication interface defined by the Infrared Data Association (IRDA) protocols. The IRDA defines a number of standards for infrared wireless data communication, including standards for infrared wireless communication at data rates up to 16 Mb/s. It will be appreciated that one or more of the communication terminals 102, 104 may be handheld wireless communication terminals, such as mobile telephones, PDAs, and the like. [0030]As further illustrated in FIG. 1, the terminals 102, 104 may include a user interface 122, a controller 126, a communication module 128, and a memory 125. [0031]The communication module 128 is configured to communicate data over one or more of the wireless interfaces 106, 108, and/or 112 to another remote terminal or other communication device. The memory 125 is configured to store programs and or data for use by the controller 126. The memory 125 may include a nonvolatile memory that is capable of storing digital information even when power to the terminal 102, 104 is switched off. [0032]The communication module 128 can include, for example, a cellular communication module, a Bluetooth module, an infrared communication module, and/or a WLAN module. With a cellular communication module, the terminals 102, 104 can communicate via the base stations 110a-b using one or more cellular communication protocols such as, for example, Advanced Mobile Phone Service (AMPS), ANSI-136, Global Standard for Mobile (GSM) communication, General Packet Radio Service (GPRS), enhanced data rates for GSM evolution (EDGE), code division multiple access (CDMA), wideband-CDMA, CDMA2000, and Universal Mobile Telecommunications System (UMTS). The cellular base stations 110a-b may be connected to a Mobile Telephone Switching Office (MTSO) 116, which, in turn, may be connected to one or more other networks 118 (e.g. the Internet, a public switched telephone network, and/or another network). With a Bluetooth or infrared module, the terminal 102, 104 can communicate via an ad-hoc network using the direct interface 106. With a WLAN module, the terminal 102, 104 can communicate through the WLAN router 114 using a communication protocol that may include, but is not limited to, 802.11a, 802.11b, 802.11e, 802.11g, and/or 802.11i. One or more of the terminals 102, 104 may also be configured to communicate directly over the networks 118 as shown in FIG. 1. [0033]The terminals 102, 104 may be configured to transmit and/or receive a digital data signal between one another and/or with another communication terminal that may be communicatively coupled thereto through, for example the MTSO 116, and/or another network 118, such as a public switched telephone network (PSTN). However, it will be appreciated that data communication between terminals 102, 104 may be accomplished without using the MTSO 116 or the other networks 118. [0034]The terminals 102, 104 my additionally include an AM/FM radio tuner, a UHF/VHF tuner, a satellite radio tuner, a DVB-H receiver, and/or another receiver configured to receive a broadcast audio/video signal. [0035]Some further aspects of a terminal 102 according to some embodiments of the invention are illustrated in FIG. 2. As shown therein, a terminal 102 may further include a position/velocity determination unit 146 and a traffic information unit 148. The position/velocity determination unit 146 and the traffic information unit 148 may communicate with the communication module 128 through the controller 126 as shown in FIG. 2. Alternatively or additionally, the position/velocity determination unit 146 and/or the traffic information unit 148 may communicate directly with the communication module 128, for example through a system bus. [0036]According to some embodiments, the position/velocity determination unit 146 may be configured to determine a current position and/or velocity of the terminal 102. For example, the position/velocity determination unit 146 may include a global positioning system (GPS) receiver that permits the position/velocity determination unit 146 to determine the location of the terminal 102 with a high degree of precision. The position/velocity determination unit 146 may include other systems and/or functionality for determining the location of the terminal 102. For example, the position/velocity determination unit 146 may be configured to obtain location information for the terminal 102 from a cellular communications network with which the terminal 102 may communicate. The position/velocity determination unit 146 may further include an inertial guidance system that permits the position/velocity determination unit 146 to determine a position/velocity of the terminal 102 through inertial movement from a known position. [0037]The traffic information unit 148 is configured to obtain information about current automobile and/or pedestrian traffic in or near a location at which the terminal 102 is located and/or near a destination point, or along a route from a current location of the terminal 102 to a destination point. For example, traffic information may be broadcast in one or more data subchannels of a public and/or private communication network that may be received by the terminal 102. For example, Traffic Message Channel (TMC) data is available in a number of cities throughout North America and Europe. TMC data is broadcast continuously on FM radio channels, and may provide notification of accidents, road construction, police, or emergency action, etc. [0038]Traffic information obtained by the traffic information unit 148 may be used by the controller 126 to determine estimated travel times and/or route information for a user of the terminal 102, as will be described in greater detail below. [0039]The terminal 102 may further include a map database 150 that contains map information concerning a geographic location in which the terminal 102 is located, or in which a destination point is located. For example, the map database 150 may contain street/road information and/or may contain map information for other areas, such as pedestrian walking areas. The map information may further include information regarding features, such as buildings, fences, rivers, etc., that may constrain the motion of a user of the terminal 102. [0040]Although the map database 150 is shown as a component of the terminal 102, it will be appreciated that the map database 150, and/or a portion of the map database 150, may be located remotely from the terminal 102. For example, the map database 150 may be stored remotely and accessed through the communication module 128. A portion of the map database 150 may be retrieved and stored locally at the terminal 102. [0041]Referring to FIG. 3, the user interface 122 can include an input device 134, such as a keypad, keyboard, touchpad, jog dial and/or other user input device. The user interface 122 may further include a display screen 132, such as an LCD display that is capable of displaying video signals in a video format, such as Quarter VGA (QVGA, 320×240 pixels), Common Intermediate Format (CIF, 360×288 pixels) and/or Quarter Common Intermediate Format (QCIF, 180×144 pixels). The terminal 102 may include appropriate CODECs to permit the terminal 102 to decode and display video signals in various formats. The user interface 122 can also include an audio interface unit 136 including a microphone coupled to an audio processor that is configured to generate an audio data stream responsive to sound incident on the microphone, and a speaker that generates sound responsive to an input audio signal. [0042]Accordingly, a navigational aid, such as a map, may be displayed on the display screen 132. Furthermore, alerts and or navigational information may be communicated to a user or the terminal 102 through the audio interface 136. [0043]According to some embodiments, a position of a terminal 102 is determined by the position/velocity determination unit 146. The controller 126 may then estimate the distance of the terminal 102 from a destination point, and may determine an estimated time for the terminal 102 to reach the destination point, assuming a given course and velocity. The controller 126 may generate an alert if the estimated time for the communication terminal to reach the destination point reaches a threshold time. [0044]In particular, the controller 126 may determine a route between a current position of the terminal 102 and the destination point. The route may be determined based on an operational mode of the controller 126. For example, in a first mode (i.e. an unconstrained mode), the route may be determined without movement constraints on the user. Thus, the route may be a straight line from the current position of the terminal 102 to the destination point. [0045]In some embodiments, the controller 126 may operate in a second mode (“constrained mode”), in which the route may be determined based on movement constraints. For example, the movement of the terminal 102 may be limited to movement over streets/roads. [0046]In a third mode (“partially constrained mode”), the route may be determined based on partial movement constraints, such as the presence of buildings, fences, gates, and/or other features that may partially restrict the movement of the user and/or vehicle in which the terminal 102 is located. The partially constrained mode of operation may be suitable for locations in which the terminal 102 is carried by a user, but in which the user's movement is at least partially limited. For example, the partially constrained mode may be suitable in urban locations, where the movement of the user in certain directions may be blocked by buildings, rivers, walls and/or other geographic features, or in locations, such as theme parks, where the movement of a user of the terminal 102 is generally unconstrained but may be limited, for example, by fences, gates, etc. [0047]The terminal102 may also operate in a vehicular mode or a pedestrian mode of operation. In a vehicular mode of operation, the terminal 102 may be limited to movement along streets/roads (i.e. constrained mode) for purposes of route/distance/time calculation, but may be assumed to be able to move at prevailing traffic speeds. In a pedestrian mode, the terminal 102 may be assumed to be in an unconstrained mode or a partially constrained mode, but may be assumed to have a maximum speed that corresponds to an average, predicted or maximum walking speed for purposes of route/distance/time calculation. [0048]The current speed of the terminal 102 may be determined, and the estimated time for the terminal 102 to reach the destination point may be determined based on the current speed of the user and/or the operational mode of the terminal 102. In some embodiments, an average speed may be used to determine the estimated time for the terminal 102 to reach the destination point. In other embodiments, a maximum historic speed may be used to determine the estimated time for the communication terminal to reach the destination point. In some embodiments, the velocity (speed and direction) of the terminal 102 may be determined, and the estimated time for the terminal 102 to reach the destination point may be determined based on the current velocity of the user. [0049]In some embodiments, an alert may be generated if the estimated time for the terminal 102 to reach the destination point (assuming movement along a designated route) exceeds the threshold time. This might be the case, for example, if the terminal 102 moves too far away from a designated destination point. Thus, for example, in some embodiments, a user may wish to be notified if they move too far away from a destination point to be able to return to the destination point within a given amount of time. As an example, a user may have an appointment at a destination point at a given time. The user may wish to temporarily walk away from the destination point, but may not want to be more than, for example, 15 minutes away from the destination point. Accordingly, an alert may be generated, and the user may be notified, if it is determined that the estimated time for the user of the terminal 102 to return to the destination point is greater than 15 minutes. [0050]In some embodiments, the alert may be generated if the estimated time for the user of the terminal 102 to reach the destination point is less than the threshold time. For example, a user may wish to be notified when they are less than 15 minutes away from a destination point that the user is traveling toward. [0051]Some embodiments of the invention are illustrated in FIG. 4, which shows a map displayed on a display screen 132 of the terminal 102. The map displayed on the display screen 132 includes icons showing a destination point 138 (indicated by a star) and a first location 140a of a user of the terminal 102. The destination point 138 may be entered by a user of the terminal 102 and displayed by the communication terminal on the display screen 132. The user may also enter a temporal limit indicating an amount of time from the destination point 138 based on speed and/or directional constraints of the user. In the embodiments shown in FIG. 4, the terminal 102 is operating in an unconstrained mode, such that it is assumed that the user of the communication terminal may move in any direction. [0052]In some embodiments, the terminal 102 may generate a geo-temporal boundary 142, which indicates the farthest location that the user can be from the destination point while still being less than the temporal limit away from reaching the destination point. That is, assuming the temporal limit entered by the user is 15 minutes, when the communication terminal is located just on the geo-temporal boundary 142, it is estimated that it would take the user approximately 15 minutes to reach the destination point along a chosen path. In some embodiments, the communication terminal may determine a shortest path from the current location of the terminal 102 and the geo-temporal boundary 142 may be determined based on the shortest path to the destination point. [0053]In some embodiments, the geo-temporal boundary 142 may be explicitly calculated or estimated by the terminal 102 and displayed on the display screen 132, for example, as a shaded and/or highlighted area around a destination point 138. However, in some embodiments, the geo-temporal boundary may not be explicitly determined. Rather, the terminal 102 may periodically update an expected travel time from a current location 140 to a destination point 138, and an alert may be generated when the expected travel time equals the temporal limit established by the user. [0054]In the embodiments shown in FIG. 4, as the movement of the user is assumed to be unconstrained, the geo-temporal boundary 142 has the shape of a circle with the destination point at the center of the circle. [0055]The time that it is estimated to take the user to move from the current location of the terminal 102 to the destination point may be estimated with reference to an assumed movement rate (speed) of the user. The assumed speed of the user may be equal to a current speed of the user, an average speed of the user, and/or an arbitrarily chosen speed. [0056]Accordingly, assuming unconstrained movement, the radius R of the geo-temporal boundary 142 may be given by the following equation: R=S*T  (1) where S is the assumed speed of the user and T is the temporal limit entered by the user. [0057]In some embodiments, the location of the geo-temporal boundary may be updated at regular and/or irregular time intervals. For example, the user may specify a certain time that he or she needs to be at a destination point. In that case, the radius of the geo-temporal boundary 142 may be given by the equation: R′=S*(T−t)  (2) where S and T are as given above, and t represents the elapsed time since the temporal limit was established. Thus, as shown in FIG. 4, after an amount of time t has elapsed, the geo-temporal boundary 142 will shrink to a new boundary 142′ in proportion to the amount of time elapsed. [0058]As an example, a visitor to a theme park may have a reservation to ride a particular ride located at a destination point 138 in the park. The user may enter the destination point into the terminal 102 and may designate a temporal limit that is less than or equal to the time remaining before the reservation time. The communication terminal may then determine a geo-temporal boundary 142 around the destination point based on the temporal limit. A map showing the geo-temporal boundary 142, the location of the destination point 138 and the current location 140 of the terminal 102 may be displayed on the display screen 132. The geo-temporal boundary 142 may be continually updated according to changes in elapsed time. Provided the user stays within the geo-temporal boundary 142, the user can have confidence that he or she will be able to reach the ride by the appointed time. [0059]The geo-temporal boundary 142 may also be updated based on changes in the average speed of movement of the user and/or on traffic and/or congestion information obtained by the traffic information unit 148. [0060]FIG. 4 also illustrates a user located at a location 140b outside the geo-temporal boundary 142. In some embodiments, a user may wish to be notified when he or she comes within a certain travel time of a destination point so that a predetermined action can be performed. For example, a user may wish to be notified when he or she is within ten minutes of a destination, so that the user can contact someone at the destination. [0061]FIG. 5 illustrates a map on a display 132 of a communication terminal where the motion of the user is partially constrained. In particular, the user and the destination point 138 may be in an urban environment including streets 146 and buildings 144 that restrict movement to generally orthogonal directions (e.g. north/south and east/west). Accordingly, the geo-temporal boundary 142 may have a shape that is non-circular. In particular, since the motion of the user in the area shown in FIG. 5 is generally limited to north/south and east/west movement, the geo-temporal boundary 142 may have a generally diamond shaped periphery. [0062]In the embodiments shown in FIG. 5, the location of the user terminal 102 is indicated by a symbol 140 that indicates position and direction of the user. [0063]In some embodiments, traffic information may be provided to the terminal 102 by a public and/or private traffic information system, as described above. In some embodiments, one or more traffic cameras 143 or other sensors may be positioned in an area and may be used to provide an indication of vehicular and/or pedestrian traffic. The amount of traffic present in a location may be used to determine an expected and/or maximum speed of the user, which in turn may be used to determine the estimated travel time of the user to the destination point 138 and/or the location of the geo-temporal boundary 142. For example, more traffic congestion may result in slower expected speeds, which may reduce the footprint of the geo-temporal boundary 142. Traffic information and/or information concerning average or expected rates of speed may also be obtained from other location-enabled mobile terminals 102, and may be communicated to the terminal 102, for example, through a communication link 106, 108, 112 as shown in FIG. 1. [0064]Anot(String), 发明领域 [0001] 本发明涉及无线通信终端,更具体地,涉及包括用于确定终端位置的功能的无线通信终端。 背景 [0002] 无线通信终端通常由用户购买,目的是通过蜂窝电话网络获得对无线电话服务的访问。 然而,随着通信移动终端的能力增加,附加级别的用户功能被包括在这样的移动终端的硬件和/或软件中。 例如,通信终端可以配备静态和/或摄像机,允许用户拍摄照片和/或视频并从移动终端传输给其他人。 同样,许多通信终端包括适用于跟踪日程安排、任务等的个人数字助理(PDA)类型的应用程序。 许多通信终端还包括消息传递能力,例如电子邮件(e-mail)、短消息服务(SMS)和多媒体消息服务(MMS)能力。 通信终端也能够通过使用互联网协议(IP)在无线和/或有线网络上连接到互联网。 [0003] 通信终端也越来越多地具有确定终端物理位置的能力。 例如,许多通信终端包括允许终端以高精度确定它们的位置的全球定位系统(GPS)接收器。 已经实现了用于确定通信终端位置的其他系统,包括从蜂窝通信网络获取位置信息的系统,以及通过惯性引导技术获取位置信息的系统。 概括 [0004] 本发明的一些实施例提供了管理移动终端的位置的方法。 该方法包括获取移动终端的位置,估计移动终端到目的地点的距离,生成移动终端到达目的地点的估计时间,以及如果移动终端到达目的地的估计时间则生成警报。 到达目的地点达到阈值时间。 [0005] 估计从移动终端到目的地点的距离可以包括基于移动终端的移动约束生成移动终端的位置和目的地点之间的路线。 生成移动终端到达目的地点的估计时间可以包括基于生成的路线生成估计时间。 [0006] 可以响应于移动终端的操作模式来执行生成路线。 操作模式可包括行人操作模式,并且移动约束可包括建筑物、桥梁、大门或栅栏中的至少一者。 在一些实施例中,操作模式可以包括车辆操作模式,并且移动约束可以包括道路。 [0007] 该方法还可以包括测量移动终端的当前速度,并且生成移动终端到达目的地点的估计时间可以包括响应于当前速度生成估计时间。 在一些实施例中,生成移动终端到达目的地点的估计时间可以包括假设移动终端以平均速度和/或最大速度行进路线来生成估计时间。 [0008] 该方法还可以包括获得指示移动终端和目的地点之间的区域中的交通的交通信息。 生成移动终端到达目的地点的估计时间可以包括响应于移动终端的位置和目的地点之间的区域中的交通生成估计时间。 [0009] 生成路线可以包括响应于移动终端和目的地点之间的区域中的交通生成移动终端的位置和目的地点之间的最快路线。 [0010]生成警报可以包括如果移动终端到达目的地点的估计时间超过阈值时间则生成警报。 在一些实施例中,生成警报可以包括如果移动终端到达目的地点的估计时间小于阈值时间则生成警报。 [0011] 该方法还可以包括响应于移动终端的位置、目的地点的位置和移动终端的运动速率来计算目的地点周围的地理-时间边界。 该方法还可以包括在移动终端的显示屏上显示地理时间边界。 [0012] 该方法还可以包括接收指定目的地点的用户输入,以及生成移动终端的位置和目的地点之间的路线。 [0013] 该方法还可以包括显示与移动终端相关联的信息框,该信息框包括移动终端到达目的地点的估计时间。 该方法还可以包括响应于时间的流逝动态地更新地理时间边界。 [0014] 根据本发明的一些实施例的管理多个移动终端的位置的方法包括获取多个移动终端的位置、估计多个移动终端到目的地点的距离、生成移动终端到达目的地的估计时间。 目的地点,并且如果移动终端中的至少一个移动终端到达目的地点的估计时间达到阈值时间则生成警报。 [0015] 根据本发明一些实施例的移动终端包括被配置为获得移动终端的位置的位置管理单元和控制器。 控制器被配置为估计从移动终端的位置到目的地点的距离,被配置为生成移动终端到达目的地点的估计时间,并且被配置为如果移动终端的估计时间生成警报 到达目的地点达到阈值时间。 [0016] 移动终端还可以包括交通信息单元,配置为获得指示移动终端的位置和目的地点之间的区域中的交通的交通信息。 控制器还可以被配置为响应于移动终端的位置和目的地点之间的区域中的交通产生估计时间。 [0017] 控制器还可以被配置为响应于移动终端的位置、目的地点的位置和移动终端的运动速率来计算目的地点周围的地理-时间边界。 [0018] 移动终端还可以包括地图数据库,并且控制器还可以被配置为响应于存储在地图数据库中的地图信息生成移动终端的位置和目的地点之间的路线。 附图的简要说明 [0019] 包括的附图是为了提供对本发明的进一步理解并且并入本申请并构成本申请的一部分,图示了本发明的某些实施例。 在图纸中: [0020] 图1是说明根据本发明一些实施例的无线通信终端和蜂窝通信系统的示意框图。 [0021] 图2是说明根据本发明一些实施例的无线通信终端的一些方面的示意框图。 [0022] 图3是说明根据本发明一些实施例的无线通信终端的一些方面的示意框图。 [0023] 图4-8是根据本发明的一些实施例配置的显示屏的示例性图示。 [0024] 图9-11是图示根据本发明的一些实施例的通信终端的操作的流程图。 具体实施方式的详细说明 [0025] 现在将参考附图更全面地描述本发明,在附图中示出了本发明的实施例。 然而,本发明不应被解释为限于在此阐述的实施例。 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明的范围充分地传达给本领域的技术人员。 相同的数字始终指代相同的元素。 如本文所用,术语“包括”或“包括”是开放式的,并且包括一个或多个规定的要素、步骤和/或功能而不排除一个或多个未规定的要素、步骤和/或功能。 如本文所用,术语“和/或”包括一个或多个关联列出的项目的任何和所有组合。 [0026] 参照方框图和/或方法和通信终端的操作说明来描述根据本发明的实施例。 应当理解,方框图和/或操作说明的每个方框,以及方框图和/或操作说明中方框的组合,可以通过射频、模拟和/或数字硬件、和/或程序来实现 指示。 这些程序指令可以提供给控制器,该控制器可以包括一个或多个通用处理器、专用处理器、ASIC和/或其他可编程数据处理装置,使得经由控制器和/或其他可编程数据处理装置执行的指令 数据处理设备,创建用于实现框图和/或操作块中指定的功能/动作的装置。 在一些实施方式中,块中标注的功能/动作可能不按操作说明中标注的顺序发生。 例如,连续显示的两个块实际上可以基本上同时执行,或者这些块有时可以以相反的顺序执行,这取决于所涉及的功能/动作。 [0027] 如本文所用,“通信终端”(或简称为“终端”)包括但不限于配置为通过有线连接(例如通过公共交换电话网络)接收/发送通信信号的设备 (PSTN)、数字用户线 (DSL)、数字电缆、直接电缆连接和/或另一个数据连接/网络,和/或通过无线接口与例如蜂窝网络、无线局域网( WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM/FM广播发射机和/或另一个通信终端。 被配置为通过无线接口进行通信的通信终端可以称为“无线通信终端”、“无线终端”和/或“移动终端”。 移动终端的示例包括但不限于卫星或蜂窝无线电话; 个人通信系统 (PCS) 终端,可将蜂窝无线电话与数据处理、传真和数据通信功能相结合; 可包括无线电话、寻呼机、互联网/内联网访问、Web 浏览器、管理器、日历和/或全球定位系统 (GPS) 接收器的 PDA; 以及包括无线电话收发器的常规膝上型和/或掌上型接收器或其他器具。 [0028] 电子设备之间的无线通信可以使用各种各样的通信媒体、通信系统和通信标准来实现。 例如,诸如移动电话的便携式电子设备通常被配置为通过模拟和/或数字无线射频(RF)电话系统进行通信。 此类设备还可配置为使用有线和/或无线局域网 (LAN)、短程通信信道(例如蓝牙 RF 通信信道和/或红外通信信道)和/或远程通信系统(例如卫星)进行通信 通信系统。 [0029] 图1是无线通信系统的示意框图 100 其中包括两个通信终端 102 , 104 配置为通过直接无线通信接口相互通信数据 106, 通过另一个无线通信接口 108 通过一个或多个蜂窝基站 110 a - b ,和/或通过另一个无线通信接口 112 通过无线局域网 (WLAN) 接入点 114 . 直接无线通讯接口 106 可以包括RF无线通信接口,例如蓝牙接口或红外通信接口,例如由红外数据协会(IRDA)协议定义的红外通信接口。 IRDA 定义了许多红外无线数据通信标准,包括数据速率高达 16 Mb/s 的红外无线通信标准。 应当理解,一个或多个通信终端 102 , 104 可以是手持无线通信终端,例如手机、PDA等。 [0030] 如图 1 中进一步所示,终端 102 , 104 可能包括用户界面 122 , 一个控制器 126 , 通信模块 128 , 和记忆 125 . [0031] 通信模块 128 被配置为通过一个或多个无线接口传送数据 106 , 108 , 和/或 112 到另一个远程终端或其他通信设备。 记忆 125 被配置为存储供控制器使用的程序和/或数据 126 . 记忆 125 可能包括一个非易失性存储器,即使在为终端供电时也能够存储数字信息 102 , 104 已关闭。 [0032] 通信模块 128 可以包括例如蜂窝通信模块、蓝牙模块、红外通信模块和/或WLAN模块。 使用蜂窝通信模块,终端 102 , 104 可以通过基站进行通信 110 a - b 使用一种或多种蜂窝通信协议,例如高级移动电话服务 (AMPS)、ANSI-136、全球移动标准 (GSM) 通信、通用分组无线服务 (GPRS)、增强数据速率的 GSM 演进 (EDGE) )、码分多址 (CDMA)、宽带 CDMA、CDMA2000 和通用移动电信系统 (UMTS)。 蜂窝基站 110 a - b 可以连接到移动电话交换局 (MTSO) 116 ,这反过来又可以连接到一个或多个其他网络 118 (例如互联网、公共交换电话网络和/或其他网络)。 带有蓝牙或红外模块,终端 102 , 104 可以使用直接接口通过临时网络进行通信 106 . 带有WLAN模块,终端 102 , 104 可以通过WLAN路由器进行通信 114 使用的通信协议可能包括但不限于 802.11a、802.11b、802.11e、802.11g 和/或 802.11i。 一个或多个终端 102 , 104 也可以配置为直接通过网络通信 118 如图1所示。 [0033] 终端机 102 , 104 可以被配置为在彼此之间和/或与可以通过例如MTSO与其通信耦合的另一通信终端之间传送和/或接收数字数据信号 116 , 和/或另一个网络 118 ,例如公共交换电话网 (PSTN)。 然而,应当理解,终端之间的数据通信 102 , 104 可以在不使用 MTSO 的情况下完成 116 或其他网络 118 . [0034] 终端机 102 , 104 我还包括 AM/FM 无线电调谐器、UHF/VHF 调谐器、卫星无线电调谐器、DVB-H 接收器和/或配置为接收广播音频/视频信号的另一个接收器。 [0035] 终端的一些其他方面 102 根据本发明的一些实施例在图2中示出。如图中所示,终端 102 可以进一步包括位置/速度确定单元 146 和一个交通信息单元 148 . 位置/速度确定单元146 和交通信息单元 148 可与通讯模块通讯 128 通过控制器 126 如图 2 所示。可替代地或附加地,位置/速度确定单元 146 和/或交通信息单元 148 可直接与通讯模块通讯 128 ,例如通过系统总线。 [0036] 根据一些实施例,位置/速度确定单元 146 可以被配置为确定终端的当前位置和/或速度 102 . 例如,位置/速度确定单元 146 可能包括允许位置/速度确定单元的全球定位系统 (GPS) 接收器 146 确定终端的位置 102 具有高精度。 位置/速度确定单元 146 可能包括用于确定终端位置的其他系统和/或功能 102 . 例如,位置/速度确定单元 146 可以配置为获取终端的位置信息 102 从与终端的蜂窝通信网络 102 可以交流。 位置/速度确定单元 146 可以进一步包括惯性制导系统,允许位置/速度确定单元 146 确定终端的位置/速度 102 通过已知位置的惯性运动。 [0037] 交通信息单元 148 被配置为获取有关当前汽车和/或行人在终端所在位置或附近的信息 102 位于和/或靠近目的地点,或沿着终端当前位置的路线 102 到一个目的地点。 例如,可以在终端可以接收的公共和/或专用通信网络的一个或多个数据子信道中广播交通信息 102 . 例如,交通信息频道 (TMC) 数据在北美和欧洲的许多城市都可用。 TMC 数据在 FM 无线电频道上连续广播,并可能提供事故、道路施工、警察或紧急行动等通知。 [0038] 交通信息单元获取的交通信息 148 可以被控制器使用 126 为终端用户确定估计的旅行时间和/或路线信息 102 , 下文将更详细地描述。 [0039] 终点站 102 可能还包括地图数据库 150 包含有关终端所在地理位置的地图信息 102 位于,或目标点位于其中。 比如地图数据库 150 可能包含街道/道路信息和/或可能包含其他区域的地图信息,例如步行区。 地图信息还可以包括关于可能限制终端用户的运动的特征的信息,例如建筑物、栅栏、河流等 102 . [0040] 虽然地图数据库 150 显示为终端的一个组件 102 , 将会理解地图数据库 150 和/或地图数据库的一部分 150 , 可能远离终端 102 . 比如地图数据库 150 可远程存储并通过通信模块访问 128 . 地图数据库的一部分 150 可以在终端本地检索和存储 102 . [0041] 参考图3,用户界面 122 可以包括一个输入设备 134 ,例如小键盘、键盘、触摸板、滚轮和/或其他用户输入设备。 用户界面 122 还可以包括显示屏 132 ,例如能够以视频格式显示视频信号的 LCD 显示器,例如四分之一 VGA(QVGA,320×240 像素)、通用中间格式(CIF,360×288 像素)和/或四分之一通用中间格式( QCIF,180×144 像素)。 终点站 102 可能包括适当的编解码器以允许终端 102解码和显示各种格式的视频信号。 用户界面 122 还可以包括一个音频接口单元 136 包括耦合到音频处理器的麦克风,音频处理器被配置为响应于入射到麦克风上的声音而生成音频数据流,以及扬声器,其响应于输入音频信号而生成声音。 [0042] 因此,可以在显示屏上显示诸如地图之类的导航帮助 132 . 此外,可以将警报和/或导航信息传送给用户或终端 102 通过音频接口 136 . [0043] 根据一些实施例,终端的位置 102 由位置/速度确定单元确定 146 . 控制器 126 然后可以估计终端的距离 102 从目的地点,并且可以确定终端的估计时间 102 假设给定的路线和速度到达目的地点。 控制器 126 如果通信终端到达目的地点的估计时间达到阈值时间,则可以生成警报。 [0044] 特别地,控制器 126 可以确定终端的当前位置之间的路线 102 和目的地点。 路线可基于控制器的操作模式来确定 126 . 例如,在第一模式(即无约束模式)中,可以在没有对用户的移动约束的情况下确定路线。 因此,该路线可以是从终端的当前位置开始的直线 102 到目的地点。 [0045] 在一些实施例中,控制器 126 可以在第二模式(“受限模式”)下操作,其中可以基于移动约束来确定路线。 例如终端的移动 102 可能仅限于在街道/道路上移动。 [0046] 在第三种模式(“部分受限模式”)中,可以基于部分移动限制来确定路线,例如建筑物、栅栏、大门和/或其他可能部分限制用户移动的特征和/ 或终端所在的车辆 102 位于。 部分约束的操作模式可能适用于终端所在的位置 102 由用户携带,但用户的移动至少部分受到限制。 例如,部分约束模式可能适用于城市位置,其中用户在某些方向上的移动可能被建筑物、河流、墙壁和/或其他地理特征阻挡,或者适用于诸如主题公园之类的位置,其中 终端用户的移动 102 通常不受约束,但也可能受到限制,例如,受到栅栏、大门等的限制。 [0047] 终点站 102 也可以以车辆模式或行人模式运行。 在车辆操作模式下,终端 102 出于路线/距离/时间计算的目的,可能仅限于沿街道/道路移动(即约束模式),但可以假定能够以现行交通速度移动。 在行人模式下,航站楼 102 可以假定处于无约束模式或部分约束模式,但可以假定最大速度对应于用于路线/距离/时间计算的平均、预测或最大步行速度。 [0048] 终端当前速度 102 可以确定,和终端的估计时间 102 到达目的地点可以基于用户当前的速度和/或终端的操作模式来确定 102 . 在一些实施例中,可以使用平均速度来确定终端的估计时间 102 到达目的地。 在其他实施例中,可以使用最大历史速度来确定通信终端到达目的地点的估计时间。 在一些实施例中,终端的速度(速度和方向) 102 可以确定,和终端的估计时间 102 可以基于用户的当前速度来确定到达目的地点的时间。 [0049]在一些实施例中,如果终端的估计时间 102 到达目的地点(假设沿指定路线移动)超过阈值时间。 这可能是这种情况,例如,如果终端 102 距离指定的目的地点太远。 因此,例如,在一些实施例中,如果用户移动距离目的地点太远而不能在给定的时间内返回目的地点,则用户可能希望得到通知。 作为示例,用户可能在给定时间在目的地点有约会。 用户可能希望暂时离开目的地点,但可能不想离开目的地点超过例如15分钟。 因此,如果确定终端的用户的估计时间,则可以生成警报,并且可以通知用户 102 返回目的地点的时间大于 15 分钟。 [0050] 在一些实施例中,如果终端用户的估计时间 102 到达目的地点的时间小于阈值时间。 例如,用户可能希望在距离用户行进的目的地点不到 15 分钟时收到通知。 [0051] 本发明的一些实施例在图4中示出,其示出显示在显示屏上的地图 132 终端的 102 . 显示屏上显示的地图 132 包括显示目的地点的图标 138 (用星号表示)和第一个位置 140 a 终端用户的 102 . 目的地点 138 可以由终端用户输入 102 并由通讯终端显示在显示屏上 132 . 用户还可以输入时间限制,指示距离目的地点的时间量 138 基于用户的速度和/或方向限制。 在图4所示的实施例中,终端 102 正在以不受约束的模式操作,从而假设通信终端的用户可以在任何方向上移动。 [0052] 在一些实施例中,终端 102 可能会产生地理时间边界 142 ,它表示用户可以到达目的地点的最远位置,同时仍然小于距离到达目的地点的时间限制。 即,假设用户输入的时限为15分钟,当通信终端刚好位于时空边界上时 142 ,估计用户需要大约 15 分钟才能沿着所选路径到达目的地点。 在一些实施例中,通信终端可以确定距终端当前位置的最短路径 102 和地理时间边界 142 可以基于到目的地点的最短路径来确定。 [0053] 在一些实施例中,地理时间边界 142 可以由终端显式计算或估计 102 并显示在显示屏上 132 ,例如,作为目的地点周围的阴影和/或突出显示区域 138 . 然而,在一些实施例中,地理时间边界可能未被明确确定。 而是终端 102 可能会定期更新从当前位置出发的预期旅行时间 140 到目的地 138 ,并且当预期旅行时间等于用户建立的时间限制时可以生成警报。 [0054] 在图 4 所示的实施例中,由于假设用户的移动不受约束,因此地理时间边界 142 具有圆的形状,目标点位于圆的中心。 [0055] 估计用户从终端当前位置移动所需的时间 102 可以参考假定的用户移动速率(速度)来估计到目的地点的距离。 假定的用户速度可以等于用户的当前速度、用户的平均速度和/或任意选择的速度。 [0056]因此,假设不受约束的运动,地理时间边界的半径 R 142 可由以下等式给出: R=S*T (1) 其中 S 是用户的假定速度,T 是用户输入的时间限制。 [0057] 在一些实施例中,地理时间边界的位置可以以规律和/或不规律的时间间隔更新。 例如,用户可以指定他或她需要到达目的地点的特定时间。 在那种情况下,地理时间边界的半径 142 可以由以下等式给出: R′=S* ( T−t ) (2) 其中 S 和 T 如上所述,t 表示自时间限制建立以来经过的时间。 因此,如图 4 所示,经过一定时间量 t 后,地理-时间边界 142 将缩小到一个新的边界 142 ' 与经过的时间成正比。 [0058] 例如,主题公园的游客可能预订了位于目的地的特定游乐设施 138 在公园里。 用户可以将目的地点输入终端 102 并且可以指定一个时间限制,该时间限制小于或等于保留时间之前的剩余时间。 然后通信终端可以确定地理时间边界 142 基于时间限制在目的地点周围。 显示时空边界的地图 142 , 目标点的位置 138 和当前位置 140 终端的 102 可能会显示在显示屏上 132 . 时空边界 142 可以根据经过的时间的变化不断更新。 如果用户停留在地理时间边界内 142 ,用户可以确信他或她将能够在指定时间到达乘车点。 [0059] 时空边界 142 也可以基于用户移动的平均速度的变化和/或交通信息单元获得的交通和/或拥塞信息来更新 148 . [0060] 图 4 还说明了位于某个位置的用户 140 b 在地理时间边界之外 142 . 在一些实施例中,用户可能希望在他或她在目的地点的特定旅行时间内到达时得到通知,以便可以执行预定动作。 例如,用户可能希望在他或她距离目的地不到十分钟时收到通知,以便用户可以联系目的地的某人。 [0061] 图5图示了显示器上的地图 132 用户的运动被部分约束的通信终端的例子。 特别是,用户和目的地点 138 可能在城市环境中,包括街道 146 和建筑物 144 将运动限制在大致正交的方向(例如北/南和东/西)。 因此,地理时间边界 142 可能具有非圆形的形状。 具体而言,由于用户在图 5 所示区域中的运动通常限于北/南和东/西运动,因此地理时间边界 142 可以具有大致菱形的外围。 [0062] 在图5所示的实施例中,用户终端的位置 102 由符号表示 140 指示用户的位置和方向。 [0063] 在一些实施例中,可以向终端提供交通信息 102 通过公共和/或私人交通信息系统,如上所述。 在一些实施例中,一个或多个交通摄像头 143 或其他传感器可以放置在一个区域中,并可以用来提供车辆和/或行人交通的指示。 位置中存在的交通量可用于确定用户的预期和/或最大速度,这又可用于确定用户到目的地点的估计行进时间 138 和/或地理时间边界的位置 142 . 例如,更多的交通拥堵可能会导致预期速度变慢,这可能会减少地理时间边界的足迹 142. 还可以从其他支持定位的移动终端获得交通信息和/或关于平均或预期速度的信息 102 , 并且可以传达给终端 102 ,例如,通过通信链路 106 , 108 , 112 如图1所示。 [0064] 图 6 中显示了部分受限运动的另一个示例。在图 6 中所示的实施例中,用户(其位置由图标指示 140 ) 和目的地点 138 位于包括围栏的城市或准城市环境中 148 包括一个门 147 . 时空边界 142 包括一部分 142 a 在围栏的同一侧 148 作为目的地 138 和一部分 142 b 在篱笆的另一边 148 从目的地点 138 . 如图 6 所示,围栏的存在 148 和大门 147 导致时空边界的形状 142 被扭曲。 例如,假设时间限制 T L 已由用户建立,一部分 142 a 时空边界 142 在围栏的同一侧 148 作为目的地 138 大致呈圆形,半径为 R a 等于 S*T L ,其中 S 是用户的估计移动速度。 假设用户需要花费 T 的时间 1 分钟到达目的地 138 从门口 147 ,然后是部分 142 b 时空边界 142 在栅栏的另一边是一个半圆,其半径 Rb 等于 S*(T L −(T 1 +T G )), 其中 T G 代表,例如,在门口的等待时间 147 . [0065] 时空边界的扭曲 142 可以以与上述类似的方式来确定基于其他运动约束的。 目标点周围区域中的建筑物、围栏、大门、桥梁等移动约束越多,时空边界扭曲的越多 142 可能会变成。 时空边界 142 也可能基于用户在不同位置的预期移动速度的变化而失真。 [0066] 约束模式的示例如图 7 所示,其中显示 132 显示包含道路的路线图 156 . 目的地点 138 由星号表示,用户位置由图标表示 140 指示终端的位置和移动方向 102 . 用户位置 140 在路上 156 . 地理时间边界 142 显示为包括部分 156 的道路 156 在用户建立的时间限制内。 在一些实施例中,如图7所示,部分 156 的道路 156 在地理时间边界内 142 可以突出显示、加阴影和/或以其他方式标记以指示地理时间区域内的道路范围 142 . [0067] 终端时可以使用图7所示的显示格式 102 被放置在车辆操作模式下,其中终端的运动 102 仅限于街道/道路 156 . 终端的时间距离 102 从目的地 138 可以通过建立终端当前位置之间的路线来确定 102 和目的地点 138 . 使用地图信息计算路线是本领域已知的,并且不需要进一步描述。 [0068] 图8说明本发明的进一步实施例,其中多于一个终端的位置 102 a - c 可能会显示在显示屏上 132 . 一个或多个终端的当前位置/速度 102 b , 102 c 可以传送到终端 102 a ,例如,通过通信链路 106 , 108 , 112 如图 1. 终端所示 102 a 可能会在显示屏上显示图标 132 终端的 102 a 指示通信终端的位置和/或移动方向 102 b , 102 c ,以及它自己的位置/方向。 此外,如图 8 所示,信息框 141 a - 141 c 可以显示在相应用户图标附近 140 a - 140 c 例如,可以指示从所选目的地点和/或终端的当前操作模式的估计行程时间 102 a - 102 c 与用户图标关联 140 a - 1 . 40 c. [0069] 在图 8 所示的示例中,假设目的地点 138 a 是指定的目的地点,终点站位于location 140 a 以车辆模式运行,预计到达指定目的地点的时间为 12 分 31 秒。 航站楼位于 location 140 b 也以车辆模式运行,预计到达指定目的地点的时间为 18 分 45 秒。 航站楼位于 location 140 c 以行人模式运行,预计到达指定目的地点的时间为 5 分 23 秒。 [0070] 如图 8 中进一步所示,多个目的地点 138 a , 138 b 可能会显示在显示屏上 132 . 选择特定目的地点后 138 a , 138 b , 终点站 102 a 可以显示地理时间边界 142 与所选目的地点相关联和/或信息框可以更新以显示信息,例如相对于所选目的地点的估计旅行时间 138 a , 138 b. [0071] 图8中所示的实施例对于希望提供期望水平的服务和/或对特定位置的响应的服务提供商可能特别有用。 例如,服务级别协议可能指定服务提供商有义务向给定的客户位置提供少于 15 分钟的响应时间。 因此,一些实施例可用于显示服务提供商是否在距客户位置的指定旅行时间内。 [0072] 应当理解,正在跟踪和显示终端位置的终端 102 a - 102 c 和目的地点 138 a , 138 b 不一定是移动或无线通信终端,但可以是例如与终端通信的工作站 102 a - 102 c 通过一个或多个通信链接 106 , 108 , 112 如图1所示。 [0073] 根据本发明的一些实施例的操作在图9至11中示出,其是可以由终端执行的操作的流程图 102 如上所述配置。 参考图9,用户可以设置目的地点 138 在终端 102 (堵塞 205 ). 用户还可以在目的地点周围设置时间限制(块 210 ). [0074] 用户可以设置终端的操作模式 102 用于确定距目的地点的距离和/或时间(块 215 ). 例如,用户可以将操作模式设置为行人模式或车辆模式。 在行人模式下,航站楼 102 可以设置为在无约束模式或部分约束模式下操作,如上所述。 [0075] 终点站 102 可以选择生成和/或显示地理时间边界 142 响应目的地点、时间限制和操作模式(块 220 ). 如上所述,地理时间边界 142 可以参考终端的预期、估计、平均和/或最大速度来确定 102 . [0076] 参见图10,在操作中,终端 102 可以确定终端的位置(块 225 ) 使用位置确定单元 146 (图 2)。 终点站 102 可以进一步获取目的地点周围地理区域的交通/拥堵信息 138 ,例如,使用交通信息单元 148 (堵塞 230 ). 接下来是终端 102 可以计算终端当前位置之间的路线 102 和目的地点 138 使用地图信息、终端位置、目的地点位置和/或交通信息(块 235 ). 在一些实施例中,终端 102 可以确定终端位置和目的地点之间的最快路线。 [0077] 参考图11,终端 102 可以使用位置/速度确定单元确定其位置 146 (堵塞 305 ). 终点站 102 然后可以检查终端的用户是否 102 已经跨越了地理时间边界(块 310 ). 在一些实施例中,终端 102 可确定到达目的地点的预期行程时间 138 已达到指定的时间限制。 [0078] 如果确定终端 102 没有跨越地理时间边界 142 (或者到目的地的预计行程时间 138 没有达到指定的时间限制)(块 310 ),操作可能会循环返回以再次确定终端的位置(块 305 ). [0079] 但是,如果终端 102 确定它已经跨越了地理时间边界 142 (堵塞 310 ), 并且可能会生成警报并且可能会通知用户越界 (bock 315 ). [0080] 已经参考图9-11部分地描述了本发明,图9-11是说明根据本发明的方面的示例性操作的流程图图示。 应当理解,图 9-11 的流程图的方框以及流程图中方框的组合可以使用包括在终端中的电子电路来实现,例如终端 102 . 还应理解,图 9-11 的流程图的块以及流程图中的块的组合可以使用不同于图 1 中所示的组件来实现, 2 和 2 A,一般来说,图 9-11 的流程图的方框和流程图中方框的组合,可以在专用硬件中实现,例如分立的模拟和/或数字电路,例如集成的组合 电路或一个或多个专用集成电路 (ASIC),以及通过可以加载到计算机或其他可编程数据处理设备上以产生机器的计算机程序指令,使得在计算机上执行的指令或其他可编程数据 处理装置创建用于实现流程图块或块中指定的功能的装置。 计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,以导致在计算机或其他可编程设备上执行一系列操作步骤,以产生计算机实现的过程,使得在计算机或其他可编程数据处理设备上执行的指令 其他可编程装置提供用于实现流程图块或块中指定的功能的步骤。 [0081] 因此,图9-11的流程图图示的块支持用于执行指定功能/动作的电子电路和其他装置,以及用于执行指定功能/动作的步骤的组合。 应当理解,图 9-11 的流程图的每个块所支持的电路和其他装置以及其中的块的组合可以通过在专用或通用数据处理器上运行的专用硬件、软件或固件来实现, 或其组合。 [0082]在附图和说明书中,已经公开了本发明的实施例,尽管使用了特定的术语,但它们仅用于一般和描述性的意义,而不是为了限制的目的,本发明的范围如下所述 索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AT483316T(String), BRPI0721418A2(String), CN101627610A(String), CN101627610B(String), DE602007009573D1(String), DE602007009573T2(String), EP2116013A2(String), EP2116013B1(String), IN4590CHENP2009A(String), JP2010522867A(String), MX2009008667A(String), MX293111B(String), RU2009136561A(String), RU2460042C2(String), US20080218405A1(String), US7561063B2(String), WO2008108827A2(String), WO2008108827A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AT483316T(String), BRPI0721418A2(String), CN101627610A(String), CN101627610B(String), DE602007009573D1(String), DE602007009573T2(String), EP2116013A2(String), EP2116013B1(String), IN4590CHENP2009A(String), JP2010522867A(String), MX2009008667A(String), MX293111B(String), RU2009136561A(String), RU2460042C2(String), US20080218405A1(String), US7561063B2(String), WO2008108827A2(String), WO2008108827A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7561063B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AT483316T(String), BRPI0721418A2(String), CN101627610A(String), CN101627610B(String), DE602007009573D1(String), DE602007009573T2(String), EP2116013A2(String), EP2116013B1(String), IN4590CHENP2009A(String), JP2010522867A(String), MX2009008667A(String), MX293111B(String), RU2009136561A(String), RU2460042C2(String), US20080218405A1(String), US7561063B2(String), WO2008108827A2(String), WO2008108827A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), AT483316T(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), BRPI0721418A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), CN101627610A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), CN101627610B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), DE602007009573D1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), DE602007009573T2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), EP2116013A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), EP2116013B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), IN4590CHENP2009A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), JP2010522867A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), MX2009008667A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), MX293111B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), RU2009136561A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.755 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.755 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.755 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), RU2460042C2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), US20080218405A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), US7561063B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), WO2008108827A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270661(Integer), WO2008108827A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7561063B2(String), US7561063B2(String), 1247500800(Integer), 270661(Integer), 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184979(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 184979(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 0(Integer), 1681975544(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184979(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75924(Integer), 2(Integer), 184979(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.867 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.867 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权 | 权利转移(String), 3(Integer), 184979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US11209555B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Positioning method and apparatus for mobile terminal, and mobile terminal(String), 移动终端的定位方法、装置及移动终端(String), US11209555B2(String), A positioning method and apparatus for a mobile terminal, and a mobile terminal. After a first time period elapses, a main processor obtains M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal, and obtains K pieces of buffered position change data of the mobile terminal. The main processor combines the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. The N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period. The K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period.(String), 一种移动终端的定位方法、装置及移动终端。 在经过第一时间段后,主处理器从缓存的N条移动终端导航数据中获取M条可靠的导航数据,并获取缓存的K条移动终端位置变化数据。 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 N个导航数据是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 K个位置变化数据是利用移动终端的传感器在第一时间段内监测得到的数据计算得到的。(String), US15/764263(String), 1447084800(Integer), US11209555B2(String), 1640620800(Integer), 1640620800(Integer), 美国(String), 4(Integer), WO(String), 5(Integer), 37(Integer), CN101035386A | CN101769747A | CN102243315A | CN102645667A | CN102901975A | CN103312902A | CN103454659A | CN104598253A | CN104749592A | CN104793223A | CN105223595A | JP2011209057A | JP2012083323A | JP2014190827A | US10514468B2 | US20050049787A1 | US20070010936A1 | US20080266174A1 | US20090278738A1 | US20110106450A1 | US20110175772A1 | US20110237275A1 | US20110291886A1 | US20120062414A1 | US20120176270A1 | US20150304985A1 | US7171303B1 | US7460064B1 | US8054220B1 | US8362949B2 | US8391888B2 | US8560218B1 | US8655578B2 | US8692709B2 | US9291704B2 | US9451580B2 | US9880286B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184980(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8f44ebe602784ec7b55b2c1d7a798a62.png(String), 184980(Integer), 8f44ebe602784ec7b55b2c1d7a798a62.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Positioning method and apparatus for mobile terminal, and mobile terminal(String), 移动终端的定位方法、装置及移动终端(String), US11209555B2(String), A positioning method and apparatus for a mobile terminal, and a mobile terminal. After a first time period elapses, a main processor obtains M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal, and obtains K pieces of buffered position change data of the mobile terminal. The main processor combines the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. The N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period. The K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period.(String), 一种移动终端的定位方法、装置及移动终端。 在经过第一时间段后,主处理器从缓存的N条移动终端导航数据中获取M条可靠的导航数据,并获取缓存的K条移动终端位置变化数据。 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 N个导航数据是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 K个位置变化数据是利用移动终端的传感器在第一时间段内监测得到的数据计算得到的。(String), US15/764263(String), 1447084800(Integer), US11209555B2(String), 1640620800(Integer), 1640620800(Integer), 美国(String), 3(Integer), 4(Integer), WO(String), 5(Integer), 37(Integer), CN101035386A | CN101769747A | CN102243315A | CN102645667A | CN102901975A | CN103312902A | CN103454659A | CN104598253A | CN104749592A | CN104793223A | CN105223595A | JP2011209057A | JP2012083323A | JP2014190827A | US10514468B2 | US20050049787A1 | US20070010936A1 | US20080266174A1 | US20090278738A1 | US20110106450A1 | US20110175772A1 | US20110237275A1 | US20110291886A1 | US20120062414A1 | US20120176270A1 | US20150304985A1 | US7171303B1 | US7460064B1 | US8054220B1 | US8362949B2 | US8391888B2 | US8560218B1 | US8655578B2 | US8692709B2 | US9291704B2 | US9451580B2 | US9880286B2(String), \20230420\8f44ebe602784ec7b55b2c1d7a798a62.png(String), 20(Integer), 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 1. A positioning method for a mobile terminal, wherein the mobile terminal comprises at least one processor, a sensor, and a global navigation satellite system (GNSS) receiver, and the method comprises:receiving, by the GNSS receiver and from one or more GNSS navigation satellites, a satellite navigation signal during a first time period;storing N pieces of navigation data of the mobile terminal in a first buffer, wherein N is an integer, and wherein the N pieces of navigation data are obtained through calculation by using the satellite navigation signal received during the first time period;monitoring, by the sensor, movement data of the mobile terminal during the first time period;storing K pieces of position change data of the mobile terminal in a second buffer, wherein K≥1, K is an integer, and the K pieces of position change data are obtained through calculation by using the movement data of the mobile terminal during the first time period;obtaining, by the at least one processor after the first time period elapses, M pieces of navigation data from the N pieces of navigation data of the mobile terminal in the first buffer, wherein N≥M, M≥1, and M;obtaining, by the at least one processor after the first time period elapses, the K pieces of position change data of the mobile terminal in the second buffer; andcombining, by the at least one processor, the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period.(String), 1.根据权利要求10所述的方法,其中至少一处理器从N个导航数据中取得M个导航数据包含:其中,N个导航数据分别对应一个时刻和一个信号强度,N个导航数据对应时刻t1,吨2,...,和TN分别按照时刻的先后顺序;至少一处理器根据时刻的先后顺序遍历N条导航数据的信号强度;至少一处理器判断第一导航数据的状态为高,其中第一导航数据为N个导航数据中信号强度大于或等于a的第一导航数据。第一预设阈值;至少一个处理器通过以下方式确定另一导航数据的状态,其中,另一导航数据为N个导航数据中的第一导航数据之后的导航数据,其中:如果导航数据在时刻t的状态i高,当时刻t的导航数据信号强度i+1小于第二预设阈值,确定t时刻导航数据的状态i+1低;或者如果导航数据在时刻t的状态i低,当时刻t的导航数据信号强度i+1大于或等于第三预设阈值,确定t时刻导航数据的状态i+1为高,其中1≥i≥n,i为整数,第二预设阈值大于第三预设阈值;和至少一处理器将所有状态为高的导航数据确定为M条导航数据。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 2. The method according to claim 1, wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and wherein the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data of the mobile terminal comprises:traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;determining, by the at least one processor, a status of first navigation data to be high, wherein the first navigation data is the first piece of navigation data of the N pieces of navigation data, with a signal strength greater than or equal to a first preset threshold;determining, by the at least one processor, a status of another piece of navigation data in the following manner, wherein the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data, wherein:if a status of navigation data at a moment ti is high, when a signal strength of navigation data at a moment ti+1 is less than a second preset threshold, determining a status of the navigation data at the moment ti+1 to be low; orif a status of navigation data at a moment ti is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti+1 to be high, wherein 1≤i≤n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is as high as the M pieces of navigation data.(String), 12.根据权利要求10所述的方法,其中至少一处理器从N个导航数据中取得M个导航数据包含:其中,N个导航数据分别对应一个时刻和一个信号强度,N个导航数据对应时刻t1,吨2,...,和TN分别按照时刻的先后顺序;至少一处理器根据时刻的先后顺序遍历N条导航数据的信号强度;至少一处理器取得N个导航数据中第一个导航数据之前的先前导航数据的状态,其中先前导航数据对应的时刻t0先于时刻t1对应第一条导航数据,时刻to与时刻t相邻1;至少一个处理器通过以下方式确定N条导航数据的状态:如果导航数据在时刻t的状态i−1高,当时刻t的导航数据信号强度i小于第二预设阈值,确定t时刻导航数据的状态i低;或者若某时刻导航数据状态低,当某时刻导航数据信号强度ti大于或等于第三预设阈值,确定t时刻导航数据的状态i为高,其中1≤i≤n,i为整数,第二预设阈值大于第三预设阈值;和至少一处理器将所有状态为高的导航数据确定为M条导航数据。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 3. The method according to claim 1, wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data of the mobile terminal comprises:wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and wherein the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;obtaining, by the at least one processor, a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, wherein a moment to corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment t0 is adjacent to the moment t1;determining, by the at least one processor, statuses of the N pieces of navigation data in the following manner:if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment ti is less than a second preset threshold, determining a status of the navigation data at the moment ti to be low; orif a status of navigation data at a moment ti−1 is low, when a signal strength of navigation data at a moment ti is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti to be high, wherein 1≤i≤n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is high as the M pieces of navigation data.(String), 13.根据权利要求10所述的方法,其中每个导航数据对应一个时刻,每个位置变化数据对应一个时刻,其中当m个时刻th一条导航数据与n的时刻相同th一段位置变化数据,mth一条导航数据被设置为匹配nth位置变化数据;和其中,所述至少一个处理器对M条导航数据和K条位置变化数据进行融合处理,得到移动终端在第一时间段内的位置信息,包括:至少一处理器从M个导航数据和K个位置变化数据中获取相互匹配的导航数据和位置变化数据;和所述至少一个处理器将匹配的导航数据和位置变化数据进行合并,并结合未合并的位置变化数据,获取移动终端在第一时间段内的位置信息。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 4. The method according to claim 1, wherein each of the navigation data corresponds to one moment, and each of the position change data corresponds to one moment;and when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; andwherein the combining, by the at least one processor, the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor, navigation data and position change data that match each other from the M pieces of navigation data and the K pieces of position change data; andcombining, by the at least one processor, the navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtaining the position information of the mobile terminal in the first time period.(String), 14.根据权利要求10所述的方法,其中导航数据为利用卫星导航信号计算得到的待计算位置坐标的数据,其中,所述至少一个处理器对所述M个导航数据和所述K个导航数据进行融合处理位置变化数据,获取移动终端在第一时间段内的位置信息,包括:至少一处理器根据M个导航数据计算得到M个位置坐标;和至少一个处理器将M个位置坐标与K个位置变化数据结合,得到移动终端在第一时间段内的位置信息。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 5. The method according to claim 1, wherein the navigation data is data obtained through calculation by using the satellite navigation signal and from which position coordinates are to be calculated, and the combining, by the at least one processor, the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor through calculation, M position coordinates according to the M pieces of navigation data; andcombining, by the at least one processor, the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period.(String), 15.根据权利要求10所述的方法,其中导航数据是位置坐标。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 6. The method according to claim 1, wherein the navigation data is position coordinates.(String), 16.根据权利要求10所述的方法,其中至少一个处理器在第一时间段内保持睡眠状态;和至少一个处理器在第一时间段过去后被唤醒。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 7. The method according to claim 1, whereinthe at least one processor remains in a sleep state during the first time period; andthe at least one processor is woken up after the first time period elapses.(String), 17.根据权利要求10所述的方法,其中该方法还包括:至少一个处理器在第一时间段内获取到移动终端的位置信息后进入休眠状态。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 8. The method according to claim 1, wherein the method further comprises:entering, by the at least one processor, a sleep state after obtaining the position information of the mobile terminal in the first time period.(String), 18.根据权利要求10所述的方法,其中移动终端在第一时间段的位置信息包括至少两个位置坐标,其中每个位置坐标对应于第一时间段的一个时刻。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 9. The method according to claim 1, wherein the position information of the mobile terminal in the first time period comprises at least two position coordinates, and wherein each of the position coordinates corresponds to one moment of the first time period.(String), 19.移动终端,包括至少一个处理器、一个全球导航卫星系统(GNSS)接收器和一个传感器,其中GNSS接收器配置为:在第一时间段期间从一个或多个GNSS导航卫星接收卫星导航信号;将移动终端的N条导航数据存储在第一缓存中,N为整数,N条导航数据是利用第一时间段接收到的卫星导航信号计算得到的;和从卫星导航信号计算导航数据,其中导航数据是要计算位置坐标的数据或者导航数据是位置坐标;传感器配置为:监测第一时间段移动终端的运动数据;将移动终端的K个位置变化数据存储在第二缓冲区中,其中K≤l,K为整数,K个位置变化数据是利用第一阶段移动终端的运动数据计算得到的时间段;和至少一个处理器被配置为:在经过第一时间段后,从第一缓存中的移动终端的N条导航数据中获取M条导航数据,其中N≤M,M≤1,M为整数;在经过第一时间段后,获取第二缓冲区中移动终端的K条位置变化数据;和结合M条导航数据和K条位置变化数据,得到移动终端在第一时间段内的位置信息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 10. A positioning method for a mobile terminal, wherein the mobile terminal comprises at least one processor and a global navigation satellite system (GNSS) receiver, and the method comprises:receiving, by the GNSS receiver and from one or more GNSS navigation satellites, a satellite navigation signal during a first time period;obtaining through calculation N pieces of navigation data according to the satellite navigation signal, and buffering the N pieces of navigation data in a first buffer, wherein N≥1, and N is an integer;monitoring, during the first time period, movement data of the mobile terminal by using a sensor of the mobile terminal;obtaining through calculation K pieces of position change data of the mobile terminal according to the data obtained by the sensor through monitoring, and buffering the K pieces of position change data in a second buffer, wherein K≥1, and K is an integer;obtaining, by the at least one processor after the first time period elapses, M pieces of navigation data from the N pieces of navigation data in the first buffer, wherein N≥M, M≥1, and M is an integer; andperforming, by the at least one processor, fusion processing on the M pieces of navigation data and the K pieces of position change data in the second buffer, to obtain position information of the mobile terminal in the first time period.(String), 20.根据权利要求19所述的移动终端,其中第一时间段包括第二时间段,GNSS接收器在第二时间段处于休眠状态;和传感器在第一时间段处于工作状态。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 11. The method according to claim 10, wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data comprises:wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;determining, by the at least one processor, a status of first navigation data to be high, wherein the first navigation data is the first piece of navigation data, of the N pieces of navigation data, with a signal strength greater than or equal to a first preset threshold;determining, by the at least one processor, a status of another piece of navigation data in the following manner, wherein the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data, wherein:if a status of navigation data at a moment ti is high, when a signal strength of navigation data at a moment ti+1 is less than a second preset threshold, determining a status of the navigation data at the moment ti+1 to be low; orif a status of navigation data at a moment ti is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti+1 to be high, wherein 1≥i≥n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is high as the M pieces of navigation data.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 12. The method according to claim 10, wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data comprises:wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;obtaining, by the at least one processor, a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, wherein a moment to corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment to is adjacent to the moment t1;determining, by the at least one processor, statuses of the N pieces of navigation data in the following manner:if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment ti is less than a second preset threshold, determining a status of the navigation data at the moment ti to be low; orif a status of navigation data at a moment is low, when a signal strength of navigation data at a moment ti is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti to be high, wherein 1≤i≤n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is high as the M pieces of navigation data.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 13. The method according to claim 10, wherein each of the navigation data corresponds to one moment, and each of the position change data corresponds to one moment, and wherein when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; andwherein the performing, by the at least one processor, fusion processing on the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor, navigation data and position change data that match each other from the M pieces of navigation data and the K pieces of position change data; andcombining, by the at least one processor, the navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtaining the position information of the mobile terminal in the first time period.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 14. The method according to claim 10, wherein the navigation data is data obtained through calculation by using the satellite navigation signal and from which position coordinates are to be calculated, and wherein the performing, by the at least one processor, fusion processing on the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor through calculation, M position coordinates according to the M pieces of navigation data; andcombining, by the at least one processor, the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 15. The method according to claim 10, wherein the navigation data is position coordinates.(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 16. The method according to claim 10, whereinthe at least one processor remains in a sleep state during the first time period; andthe at least one processor is woken up after the first time period elapses.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 17. The method according to claim 10, wherein the method further comprises:entering, by the at least one processor, a sleep state after obtaining the position information of the mobile terminal in the first time period.(String), 1(Integer), 16(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 18. The method according to claim 10, wherein the position information of the mobile terminal in the first time period comprises at least two position coordinates, and wherein each of the position coordinates corresponds to one moment of the first time period.(String), 1(Integer), 17(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 19. A mobile terminal, comprising at least one processor, a global navigation satellite system (GNSS) receiver, and a sensor, whereinthe GNSS receiver is configured to:receive, from one or more GNSS navigation satellites, a satellite navigation signal during a first time period;store N pieces of navigation data of the mobile terminal in a first buffer, wherein N is an integer, and wherein the N pieces of navigation data are obtained through calculation by using the satellite navigation signal received during the first time period; andcalculate navigation data from the satellite navigation signal, wherein the navigation data is data from which position coordinates are to be calculated or the navigation data is position coordinates;the sensor is configured to:monitor movement data of the mobile terminal during the first time period;store K pieces of position change data of the mobile terminal in a second buffer, wherein K≤l, K is an integer, and the K pieces of position change data are obtained through calculation by using the movement data of the mobile terminal during the first time period; andthe at least one processor is configured to:obtain, after the first time period elapses, M pieces of navigation data from the N pieces of navigation data of the mobile terminal in the first buffer, wherein N≤M, M≤1, and M is an integer;obtain, after the first time period elapses, the K pieces of position change data of the mobile terminal in the second buffer; andcombine the M pieces of navigation data and the K pieces of position change data to obtain position information of the mobile terminal in the first time period.(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:44.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184980(Integer), 20. The mobile terminal according to claim 19, whereinthe first time period comprises a second time period,the GNSS receiver is in a sleep state during the second time period; andthe sensor is in a working state during the first time period.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184980(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a national stage of International Application No. PCT/CN2015/094224, filed on Nov. 10, 2015, which claims priority to International Application No. PCT/CN2015/091138, filed on Sep. 29, 2015. Both of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present invention relate to communications technologies, and in particular, to a positioning method and apparatus for a mobile terminal, and a mobile terminal. BACKGROUND [0003]A global navigation satellite system (Global Navigation Satellite System, GNSS) is a generic term for a type of system that uses a navigation satellite to implement positioning. The GNSS can obtain user coordinates over the globe, and is a widely used positioning technology. However, in urban areas, due to reflection and blockage of a navigation signal, drifting usually exists in a positioning result or even positioning cannot be implemented. Dead reckoning (Dead Reckoning, DR) is a technology that uses a sensor module (such as an accelerometer, a gyroscope, and a magnetic field sensor) of a mobile terminal to calculate a relative position of a moving user. The dead reckoning does not rely on an external wireless signal, and can implement positioning when a navigation signal is blocked. However, accuracy of the DR deteriorates because errors are accumulated over time. [0004]In the prior art, two sets of positioning systems: the GNSS and the DR may be operated simultaneously to separately output positioning results, and a central processing unit (CPU) performs real-time fusion processing on the positioning results of the two sets of positioning systems to implement accurate positioning. However, real-time fusion processing performed by the CPU causes relatively high power consumption of a terminal. SUMMARY [0005]Embodiments of the present invention provide a positioning method and apparatus for a mobile terminal, and a mobile terminal, to resolve a prior-art problem of high power consumption of positioning services. [0006]According to a first aspect, an embodiment of the present invention provides a positioning method for a mobile terminal, where the mobile terminal includes a main processor, and the method includes: [0007]obtaining, by the main processor after a first time period elapses, M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal, where N≥M, M≥1, M and N are integers, and the N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period; [0008]obtaining, by the main processor after the first time period elapses, K pieces of buffered position change data of the mobile terminal, where K≥1, K is an integer, and the K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period; and [0009]combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. [0010]Optionally, the obtaining, by the main processor, M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal includes: [0011]where each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; [0012]traversing, by the main processor according to the order of the moments, signal strengths of the N pieces of navigation data; [0013]determining, by the main processor, a status of first navigation data to be high, where the first navigation data is the first piece of navigation data, of the N pieces of navigation data, with a signal strength greater than or equal to a first threshold; [0014]determining, by the main processor, a status of another piece of navigation data in the following manner, where the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data: if a status of navigation data at a moment t1 is high, when a signal strength of navigation data at a moment ti+1 is less than a second threshold, determining a status of the navigation data at the moment ti+1 to be low; or if a status of navigation data at a moment t1 is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third threshold, determining a status of the navigation data at the moment ti+1 to be high, where 1≤i≤n, i is an integer, and the second threshold is greater than the third threshold; and [0015]determining, by the main processor, all navigation data whose status is high as the M pieces of reliable navigation data. [0016]Optionally, the obtaining, by the main processor, M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal includes: [0017]where each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; [0018]traversing, by the main processor according to the order of the moments, signal strengths of the N pieces of navigation data; [0019]obtaining, by the main processor, a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, where a moment t0 corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment t0 is adjacent to the moment t1; [0020]determining, by the main processor, statuses of the N pieces of navigation data in the following manner: if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment ti is less than a second threshold, determining a status of the navigation data at the moment ti to be low; or if a status of navigation data at a moment ti−1 is low, when a signal strength of navigation data at a moment ti is greater than or equal to a third threshold, determining a status of the navigation data at the moment ti to be high, where 1≤i≤n, i is an integer, and the second threshold is greater than the third threshold; and determining, by the processor, all navigation data whose status is high as the M pieces of reliable navigation data. [0021]Optionally, each of the navigation data is corresponding to one moment, and each of the position change data is corresponding to one moment; and when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; and [0022]the combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period includes: [0023]obtaining, by the main processor, reliable navigation data and position change data that match each other from the M pieces of reliable navigation data and the K pieces of position change data; and [0024]combining, by the main processor, the reliable navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtaining the position information of the mobile terminal in the first time period. [0025]Optionally, the navigation data is data that is obtained through calculation by using the satellite navigation signal of the mobile terminal and from which position coordinates are to be calculated, and the combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period includes: [0026]obtaining, by the main processor through calculation, M position coordinates according to the M pieces of reliable navigation data; and [0027]combining, by the main processor, the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period. [0028]Optionally, the navigation data is position coordinates. [0029]Optionally, the method further includes: [0030]remaining, by the main processor, in a sleep state during the first time period; and [0031]being woken up, by the main processor, after the first time period elapses. [0032]Optionally, the method further includes: [0033]entering, by the main processor, a sleep state after obtaining the position information of the mobile terminal in the first time period. [0034]Optionally, the position information of the mobile terminal in the first time period includes at least two position coordinates, and each of the position coordinates is corresponding to one moment of the first time period. [0035]According to a second aspect, an embodiment of the present invention further provides a positioning method for a mobile terminal, where the mobile terminal includes a main processor, and the method includes: [0036]receiving a satellite navigation signal of the mobile terminal during a first time period; [0037]obtaining through calculation N pieces of navigation data according to the satellite navigation signal, and buffering the N pieces of navigation data, where N≥1, and N is an integer; [0038]monitoring, during the first time period, movement data of the mobile terminal by using a sensor of the mobile terminal; [0039]obtaining through calculation K pieces of position change data of the mobile terminal according to the movement data that is obtained by the sensor through monitoring, and buffering the K pieces of position change data, where K≥1, and K is an integer; [0040]obtaining, by the main processor after the first time period elapses, M pieces of reliable navigation data from the N pieces of navigation data, where N≥M, M≥1, and M is an integer; and [0041]combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. [0042]Optionally, the method according to the second aspect may further include all the optional solutions in the first aspect. [0043]According to a third aspect, an embodiment of the present invention provides a positioning apparatus for a mobile terminal, including: [0044]an obtaining module, configured to obtain M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal after a first time period elapses, where N≥M, M≥1, M and N are integers, and the N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period; where [0045]the obtaining module is further configured to obtain K pieces of buffered position change data of the mobile terminal after the first time period elapses, where K≥1, K is an integer, and the K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period; and [0046]a data processing module, configured to combine the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. [0047]Optionally, each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; and [0048]the obtaining module is specifically configured to: [0049]traverse signal strengths of the N pieces of navigation data according to the order of the moments; [0050]determine a status of first navigation data to be high, where the first navigation data is the first piece of navigation data, of the N pieces of navigation data, with a signal strength greater than or equal to a first threshold; [0051]determine a status of another piece of navigation data in the following manner, where the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data: if a status of navigation data at a moment ti is high, when a signal strength of navigation data at a moment ti+1 is less than a second threshold, determine a status of the navigation data at the moment ti+1 to be low; or if a status of navigation data at a moment ti is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third threshold, determine a status of the navigation data at the moment ti+1 to be high, where 1≤i≤n, i is an integer, and the second threshold is greater than the third threshold; and determine all navigation data whose status is high as the M pieces of reliable navigation data. [0052]Optionally, each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; and [0053]the obtaining module is specifically configured to: [0054]traverse signal strengths of the N pieces of navigation data according to the order of the moments; and obtain a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, where a moment t0 corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment t0 is adjacent to the moment t1; [0055]determine statuses of the N pieces of navigation data in the following manner: if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment t1 is less than a second threshold, determine a status of the navigation data at the moment ti to be low; or if a status of navigation data at a moment ti−1 is low, when a signal strength of navigation data at a moment t1 is greater than or equal to a third threshold, determine a status of the navigation data at the moment ti to be high, where 1≤i≤n, and the second threshold is greater than the third threshold; and [0056]determine all navigation data whose status is high as the M pieces of reliable navigation data. [0057]Optionally, each of the navigation data is corresponding to one moment, and each of the position change data is corresponding to one moment; and when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; and [0058]the data processing module is specifically configured to: [0059]obtain reliable navigation data and position change data that match each other from the M pieces of reliable navigation data and the K pieces of position change data; and [0060]combine the reliable navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtain the position information of the mobile terminal in the first time period. [0061]Optionally, the navigation data is data that is obtained through calculation by using the satellite navigation signal of the mobile terminal and from which position coordinates are to be calculated; and the data processing module is specifically configured to: [0062]obtain through calculation M position coordinates according to the M pieces of reliable navigation data; and [0063]combine the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period. [0064]Optionally, the apparatus further includes: [0065]a wake-up module, configured to wake up the positioning apparatus after the first time period elapses; where [0066]the positioning apparatus is in a sleep state during the first time period. [0067]Optionally, the apparatus further includes: [0068]a sleep module, configured to enable the positioning apparatus to enter a sleep state after the position information of the mobile terminal in the first time period is obtained. [0069]According to a fourth aspect, an embodiment of the present invention provides a mobile terminal, including a main processor, a global navigation satellite system GNSS receiver, a sensor, and a coprocessor, where [0070]the main processor is configured to execute any one of the foregoing methods; [0071]the GNSS receiver is configured to: receive a satellite navigation signal of the mobile terminal during a first time period, and calculate navigation data from the satellite navigation signal, where the navigation data is data from which position coordinates are to be calculated or the navigation data is position coordinates; [0072]the sensor is configured to monitor movement data of the mobile terminal during the first time period; and [0073]the coprocessor is configured to obtain through calculation K pieces of position change data according to the movement data that is obtained by the sensor through monitoring; or the coprocessor is configured to: obtain through calculation K pieces of position change data according to the movement data that is obtained by the sensor through monitoring, and calculate the position coordinates from the navigation data. [0074]Optionally, the first time period includes a second time period, and the global navigation satellite system GNSS receiver is in a sleep state during the second time period; and the sensor is in a working state during the first time period. [0075]In the embodiments of the present invention, N pieces of navigation data and K pieces of position change data that are obtained during a first time period are separately buffered. A main processor may obtain the K pieces of position change data after the first time period elapses, obtain M pieces of reliable navigation data from the N pieces of buffered navigation data, and combine the reliable navigation data and the position change data, to obtain position information of a mobile terminal. During a process of obtaining the N pieces of navigation data and the K pieces of position change data, the main processor does not need to be turned on in real time, thereby reducing positioning power consumption of a system. BRIEF DESCRIPTION OF DRAWINGS [0076]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0077]FIG. 1 is a schematic diagram of a frame structure of a mobile terminal according to an embodiment of the present invention; [0078]FIG. 2 is a schematic diagram of a frame structure of another mobile terminal according to an embodiment of the present invention; [0079]FIG. 3 is a schematic flowchart of a positioning method for a mobile terminal according to an embodiment of the present invention; [0080]FIG. 4 is a schematic diagram of an operating manner of a GNSS receiver and a DR module according to an embodiment of the present invention; [0081]FIG. 5 is a schematic flowchart of a method for obtaining reliable navigation data according to an embodiment of the present invention; [0082]FIG. 6 is a schematic flowchart of a specific implementation manner of the method for obtaining reliable navigation data in FIG. 5; [0083]FIG. 7 is a schematic flowchart of another method for obtaining reliable navigation data according to an embodiment of the present invention; and [0084]FIG. 8 is a schematic structural diagram of a positioning apparatus for a mobile terminal according to an embodiment of the present invention. DESCRIPTION OF EMBODIMENTS [0085]To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0086]In the embodiments of the present invention, a GNSS positioning technology and a DR positioning technology are combined to improve positioning performance, and a main processor combines a GNSS positioning result and a DR positioning result in a non-real-time manner to reduce positioning power consumption. [0087]Specifically, GNSS is a generic term for a type of system that uses a navigation satellite to implement positioning, and may include America's Global Positioning System (Global Positioning System, GPS), Russia's GLONASS (GLONASS), Europe's Galileo (Galileo), China's BeiDou System, Japan's Quasi-Zenith Satellite System (Quasi-Zenith Satellite System, QZSS), and so on. The GNSS can be used to obtain user coordinates over the globe, and is a widely used positioning technology. However, in urban areas, a navigation signal is likely to be reflected or blocked by buildings, drifting exists in a positioning result or even positioning cannot be implemented by using the GNSS positioning technology. [0088]The DR positioning technology uses a sensor module (such as an accelerometer, a gyroscope, and a magnetic field sensor) of a mobile terminal to calculate a relative position of a moving user. The DR positioning technology does not rely on an external wireless signal, and can implement positioning when a navigation signal is blocked. However, accuracy of DR positioning deteriorates as errors are accumulated over time. [0089]FIG. 1 is a schematic diagram of a frame structure of a mobile terminal according to an embodiment of the present invention. Referring to FIG. 1, the mobile terminal includes components such as a GNSS receiver 10, a sensor 20, a main processor 30, a coprocessor 40, a first storage unit 50, and a second storage unit 43. The components communicate with each other by using one or more buses. It can be understood by a person skilled in the art that the structure of the mobile terminal shown in the figure does not constitute any limitation on the present invention. The structure may be either a bus structure or a star structure, and may include more or less components than those shown in the figure, or may combine some parts, or may have a component layout different from that in the figure. The mobile terminal may be any mobile or portable electronic device, and includes but is not limited to a mobile phone, a mobile computer, a tablet computer, a personal digital assistant (Personal Digital Assistant, PDA), a navigation apparatus, a mobile internet device (Mobile Internet Device, MID), or a wearable device (Wearable Device). [0090]The GNSS receiver 10 is configured to: receive a navigation signal transmitted by a GNSS navigation satellite, and calculate data such as a pseudorange, a navigation message, and a signal strength from the navigation signal. The GNSS receiver 10 may be a GNSS receiver, a GNSS positioning chip, and the like. A satellite of one of the GPS, the GLONASS, the Galileo, the BeiDou System, the QZSS, or another system may be used for navigation (a single-mode receiver), or more than one system may be simultaneously used to implement positioning (a multi-mode receiver). The main processor 30 obtains through calculation position coordinates of a user according to the data such as the pseudorange, the navigation message, and the signal strength. The GNSS receiver may include an integrated circuit, such as a GNSS chip. The GNSS receiver includes a first buffer 11, configured to buffer data such as a measurement and a navigation message. The first buffer 11 is a storage area integrated in the GNSS receiver and may include an integrated circuit. [0091]The sensor 20 may include an accelerometer, a gyroscope, a magnetic field sensor, and the like. The sensor 20 is connected to the coprocessor 40 by using a transmission circuit, such as an I2C bus, and transmits physical data obtained through measurement by the sensor 20 to the coprocessor 40 for processing. [0092]The main processor 30 and the coprocessor 40 are control centers of the mobile terminal; are connected to various parts of the entire electronic device by using various interfaces and lines; and run or execute a software program and/or a module stored in the storage unit and invoke data stored in the storage unit, to implement various functions of the electronic device and/or process data. The main processor 30 and the coprocessor 40 may include an integrated circuit (Integrated Circuit, IC for short), for example, may include a single packaged IC, or may include multiple packaged ICs with a same function or different functions. For example, the main processor 30 and coprocessor 40 may include only a central processing unit (Central Processing Unit, CPU), or may include a combination of a graphics processing unit (Graphics Processing Unit, GPU), a digital signal processor (Digital Signal Processor, DSP for short), and a control chip (for example, a baseband chip) of a communications unit. In this embodiment of the present invention, the CPU may be a single-core processor or a multi-core processor. [0093]The main processor 30 has higher power consumption due to its greater processing capability and more complex circuit structure. The coprocessor has lower power consumption due to its weaker processing capability and simpler circuit structure. For example, the coprocessor may include a microcontroller unit (Microcontroller Unit, MCU), or may be implemented by using a sensor hub (Sensor Hub) technology. The first storage unit 50 is configured to provide the main processor 30 with a storage capacity required for code storage and processing. [0094]The coprocessor 40 includes a second buffer 41, configured to buffer user position change information that is obtained by processing the physical data output by the sensor module. The second storage unit 43 is configured to provide the coprocessor 40 with a storage capacity required in a code storage and processing process. The first storage unit 50 and the second storage unit 43 may be configured to store a software program and a module. The main processor 30 and the coprocessor 40 run the software program and the module stored in the first storage unit 50 and the second storage unit 43, to implement various functions and applications of the mobile terminal and implement data processing. The first storage unit 50 and the second storage unit 43 include a program storage area and a data storage area. The program storage area may store an operating system, and an application program required for at least one function, such as an audio playback program and an image playback program. The data storage area may store data created during the use of the mobile terminal (such as audio data and a phone book), and so on. In this embodiment of the present invention, the first storage unit 50 and the second storage unit 43 may include a volatile memory, such as a nonvolatile dynamic random access memory (Nonvolatile Random Access Memory, NVRAM), a phase-change random access memory (Phase Change RAM, PRAM), and a magnetoresistive random access memory (Magetoresistive RAM, MRAM); and may include a nonvolatile memory, such as at least one disk storage device, an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), and a flash memory device, such as a NOR flash memory (NOR flash memory) or a NAND flash memory (NAND flash memory). The nonvolatile memory stores the operating system and the application program executed by the main processor 30 and the coprocessor 40. The main processor 30 and the coprocessor 40 load a running program and data from the nonvolatile memory into a memory and store digital content in a large-capacity storage apparatus. The operating system includes various components and/or drivers that are used to control and manage a conventional system task, such as memory management, storage device control, and power management, and that facilitate communication between various hardware and software. In this embodiment of the present invention, the operating system may be the Android system of Google, the iOS system developed by Apple, the Windows operating system developed by the Microsoft Corporation, or the like, or an embedded operating system such as Vxworks. [0095]A buffer is a type of storage unit, can be quickly read and written, and is generally implemented by using a register circuit. The first buffer 11 is configured to buffer data that the GNSS receiver 10 needs to transmit to the main processor 30. The second buffer 41 is configured to buffer data that the coprocessor 40 needs to transmit to the main processor 40. [0096]FIG. 2 is a schematic diagram of a frame structure of another mobile terminal according to an embodiment of the present invention. Referring to FIG. 2, on the basis of the mobile terminal provided in the embodiment shown in FIG. 1, a GNSS receiver 10 is not connected to a main processor 30 by using a bus, but is directly connected to a coprocessor 40 by using a transmission circuit. For example, the transmission circuit may be a universal asynchronous receiver/transmitter (Universal Asynchronous Receiver/Transmitter, UART). [0097]The mobile terminal shown in FIG. 1 receives, by using a GNSS receiver 10, a navigation signal sent by a GNSS navigation satellite, calculates data such as a pseudorange, a navigation message, and a signal strength according to the navigation signal, and buffers the data into a first buffer 11 of the GNSS receiver 10. During processing, a main processor 30 reads the data such as the pseudorange, the navigation message, and the signal strength from the first buffer 11 and calculates corresponding position coordinates of a user. [0098]Compared with the mobile terminal shown in FIG. 1, no first buffer is provided in the GNSS receiver 10 of the mobile terminal shown in FIG. 2. After receiving a navigation signal transmitted from a GNSS navigation satellite and calculating data such as a pseudorange, a navigation message, and a signal strength according to the navigation signal, the GNSS receiver 10 does not buffer the data, but directly transmits the data to a coprocessor 40 by using a transmission circuit. The coprocessor 40 calculates position coordinates of a user in real time according to the data such as the pseudorange, the navigation message, and the signal strength, and buffers the position coordinates of the user into a second buffer 41 of the coprocessor 40. [0099]The embodiments of the present invention may be applied to a non-real-time positioning scenario. For example, when a user is running, a mobile phone may be used to record a running track. During a process of recording, the mobile phone may be in a screen-off (screen-turnoff) state, that is, a main processor is in a sleep state. In this case, the phone does not calculate a current position in real time but buffers GNSS and DR data, and after the main processor is woken up, calculates coordinates of a running track of the user according to the buffered data. [0100]The technical solutions of the present invention are described in detail with reference to specific embodiments below. The following specific embodiments may be combined with each other, and a same or similar concept or process may not be repeated in some embodiments. [0101]FIG. 3 is a schematic flowchart of a positioning method for a mobile terminal according to an embodiment of the present invention. The positioning method shown in FIG. 3 can be implemented by the mobile terminal shown in FIG. 1 or FIG. 2. Referring (String), 交叉引用相关申请 [0001] 本申请为 2015 年 11 月 10 日提交的国际申请号 PCT/CN2015/094224 的国家阶段,其要求于 2015 年 9 月 29 日提交的国际申请号 PCT/CN2015/091138 的优先权。 上述申请通过引用整体并入本文。 技术领域 [0002] 本发明实施例涉及通信技术,尤其涉及一种移动终端的定位方法、装置及移动终端。 背景 [0003] 全球导航卫星系统(Global Navigation Satellite System,GNSS)是利用导航卫星实现定位的一类系统的总称。 GNSS可以获取全球用户坐标,是一种应用广泛的定位技术。 但是在市区,由于导航信号的反射和遮挡,定位结果通常会出现漂移,甚至无法定位。 航位推算(Dead Reckoning,DR)是一种利用移动终端的传感器模块(如加速度计、陀螺仪、磁场传感器等)计算移动用户的相对位置的技术。 航位推算不依赖外部无线信号,可以在导航信号受阻时进行定位。 然而,由于误差随着时间的推移而累积,DR 的准确性会下降。 [0004] 现有技术中,GNSS和DR两套定位系统可以同时运行,分别输出定位结果,中央处理器(CPU)对两组定位的定位结果进行实时融合处理 系统实现精准定位。 但是,CPU进行实时融合处理会导致终端的功耗较高。 概括 [0005] 本发明实施例提供一种移动终端的定位方法、装置及移动终端,以解决现有技术中定位业务的高功耗问题。 [0006] 根据第一方面,本发明实施例提供一种移动终端的定位方法,所述移动终端包括主处理器,所述方法包括: [0007] 主处理器经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠的导航数据,其中N≥M,M≥1,M和N为整数,N条 导航数据的个数是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的; [0008] 主处理器在经过第一时间段后得到移动终端缓存的K条位置变化数据,其中K≥1,K为整数,K条位置变化数据是利用数据计算得到的 由移动终端的传感器在第一时间段内监测得到; 和 [0009] 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0010] 可选的,主处理器从移动终端缓存的N个导航数据中获取M个可靠导航数据包括: [0011] 其中N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; [0012] 主处理器按照矩的顺序遍历N个导航数据的信号强度; [0013] 主处理器确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据 ; [0014]主处理器通过如下方式确定另一条导航数据的状态,其中该另一条导航数据是N条导航数据中在第一条导航数据之后的导航数据: 如果是导航状态 t时刻的数据 1 为高,当导航数据的信号强度在时刻 t i+1 小于第二阈值,确定时刻t的导航数据状态 i+1 低; 或者如果在时刻 t 的导航数据状态 1 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,确定导航数据在时刻t的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 和 [0015] 主处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0016] 可选的,主处理器从移动终端缓存的N个导航数据中获取M个可靠导航数据包括: [0017] 其中N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; [0018] 主处理器按照矩的顺序遍历N个导航数据的信号强度; [0019] 主处理器获取N个导航数据中第一个导航数据之前的前一个导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 ; [0020] 主处理器通过以下方式确定N条导航数据的状态:如果导航数据在时刻t的状态 i−1 为高,当导航数据的信号强度在时刻 t i 小于第二阈值,确定时刻t的导航数据状态 i 低; 或者如果在时刻 t 的导航数据状态 i−1 低,当导航数据的信号强度在时刻 t i 大于或等于第三阈值,确定导航数据在时刻t的状态 i 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0021] 可选的,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻; 当 m 的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一条位置变化数据; 和 [0022] 主处理器将M个可靠导航数据和K个位置变化数据组合,得到第一时间段内移动终端的位置信息包括: [0023] 主处理器从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据; 和 [0024] 主处理器结合可靠的导航数据和匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0025]可选地,所述导航数据为利用所述移动终端的卫星导航信号计算得到的待计算位置坐标的数据,主处理器将所述M个可靠导航数据与所述M个可靠导航数据相结合。 K条位置变化数据,获取移动终端在第一时间段的位置信息包括: [0026] 主处理器根据M个可靠导航数据计算得到M个位置坐标; 和 [0027] 主处理器结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0028] 可选地,导航数据是位置坐标。 [0029] 可选的,该方法还包括: [0030] 在第一时间段内由主处理器保持在睡眠状态; 和 [0031] 在第一个时间段过去后,被主处理器唤醒。 [0032] 可选的,该方法还包括: [0033] 主处理器在第一时间段内获得移动终端的位置信息后进入休眠状态。 [0034] 可选的,第一时间段内移动终端的位置信息包括至少两个位置坐标,每个位置坐标对应第一时间段的一个时刻。 [0035] 根据第二方面,本发明实施例还提供一种移动终端的定位方法,所述移动终端包括主处理器,所述方法包括: [0036] 在第一时间段接收移动终端的卫星导航信号; [0037] 根据卫星导航信号计算得到N个导航数据,并缓存N个导航数据,其中N≥1,N为整数。 [0038] 通过移动终端的传感器在第一时间段内监测移动终端的运动数据; [0039] 根据传感器监测得到的运动数据,计算得到移动终端的K条位置变化数据,并缓存K条位置变化数据,其中K≥1,K为整数。 [0040] 在经过第一时间段后,主处理器从N个导航数据中获取M个可靠导航数据,其中N≥M,M≥1,M为整数; 和 [0041] 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0042] 可选的,第二方面的方法还可以包括第一方面的所有可选方案。 [0043] 第三方面,本发明实施例提供一种移动终端的定位装置,包括: [0044] 获取模块,用于在经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠导航数据,其中N≥M,M≥1,M和N为整数,N条 导航数据的个数是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的; 在哪里 [0045] 获取模块,还用于在经过第一时间段后,获取移动终端缓存的K条位置变化数据,其中K≥1,K为整数,K条位置变化数据通过计算得到 移动终端的传感器在第一时间段内监测得到的数据; 和 [0046] 数据处理模块,用于将M个可靠导航数据和K个位置变化数据结合起来,得到第一时间段内移动终端的位置信息。 [0047]可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; 和 [0048] 获取模块具体用于: [0049] 按照矩的顺序遍历N个导航数据的信号强度; [0050] 确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据; [0051] 判断另一条导航数据状态的方式如下,其中该另一条导航数据是N条导航数据中在第一个导航数据之后的导航数据: 如果某时刻t的导航数据的状态 i 为高,当导航数据的信号强度在时刻 t i+1 小于第二个阈值,判断t时刻导航数据的状态 i+1 低; 或者如果在时刻 t 的导航数据状态 i 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,判断t时刻导航数据的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 将所有状态为高的导航数据确定为M个可靠导航数据。 [0052] 可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; 和 [0053] 获取模块具体用于: [0054] 按照矩的顺序遍历N个导航数据的信号强度; 获取N个导航数据中第一个导航数据之前的前一个导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 ; [0055] N个导航数据的状态判断方法如下:如果某时刻t的导航数据的状态 i−1 为高,当导航数据的信号强度在时刻 t 1 小于第二个阈值,判断t时刻导航数据的状态 i 低; 或者如果在时刻 t 的导航数据状态 i−1 低,当导航数据的信号强度在时刻 t 1 大于或等于第三阈值,判断t时刻导航数据的状态 i 为高,其中1≤i≤n,第二阈值大于第三阈值; 和 [0056] 将所有状态为高的导航数据确定为M个可靠导航数据。 [0057] 可选的,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻; 当 m 的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一条位置变化数据; 和 [0058] 数据处理模块具体用于: [0059] 从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据; 和 [0060] 结合可靠的导航数据和相互匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0061]可选地,所述导航数据为利用所述移动终端的卫星导航信号计算得到的、用于计算位置坐标的数据; 数据处理模块具体用于: [0062] 根据M个可靠导航数据计算得到M个位置坐标; 和 [0063] 结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0064] 可选的,该装置还包括: [0065] 唤醒模块,用于在经过第一时间段后唤醒定位装置; 在哪里 [0066] 定位装置在第一时间段内处于休眠状态。 [0067] 可选的,该装置还包括: [0068] 休眠模块,用于在获取到移动终端在第一时间段内的位置信息后,使定位装置进入休眠状态。 [0069] 根据第四方面,本发明实施例提供一种移动终端,包括主处理器、全球导航卫星系统GNSS接收器、传感器和协处理器,其中 [0070] 主处理器,用于执行上述任一方法; [0071] GNSS接收器,用于在第一时间段内接收移动终端的卫星导航信号,并根据卫星导航信号计算导航数据,导航数据为计算位置坐标的数据或导航数据。 是位置坐标; [0072] 传感器用于监测第一时间段内移动终端的运动数据; 和 [0073] 协处理器,用于根据传感器监测得到的运动数据,计算得到K个位置变化数据。 或者,协处理器,用于根据传感器监测得到的运动数据,计算得到K个位置变化数据,并根据导航数据计算出位置坐标。 [0074] 可选地,所述第一时间段包括第二时间段,所述全球导航卫星系统GNSS接收机在第二时间段内处于休眠状态; 第一时间段内传感器处于工作状态。 [0075] 在本发明实施例中,分别缓存第一时间段获取的N个导航数据和K个位置变化数据。 主处理器可以在经过第一时间段后获取K个位置变化数据,从缓存的N个导航数据中获取M个可靠导航数据,将可靠导航数据和位置变化数据结合,得到位置 移动终端的信息。 在获取N个导航数据和K个位置变化数据的过程中,不需要实时开启主处理器,从而降低了系统的定位功耗。 附图说明 [0076] 为了更清楚地描述本发明实施例中的技术方案,下面对描述实施例所需的附图进行简要说明。 显然,以下描述中的附图示出了本发明的一些实施例,本领域普通技术人员在没有做出创造性劳动的情况下仍可以从这些附图中导出其他附图。 [0077] 图1是根据本发明实施例的移动终端的帧结构示意图; [0078] 图2为本发明实施例提供的另一种移动终端的帧结构示意图; [0079] 图3为本发明实施例提供的移动终端定位方法的流程示意图; [0080]图4是根据本发明实施例的GNSS接收器和DR模块的工作方式示意图; [0081] 图5为本发明实施例提供的可靠导航数据获取方法的流程示意图。 [0082] 图6是图5中获取可靠导航数据的方法的具体实施方式的流程示意图; [0083] 图7为本发明实施例提供的另一种可靠导航数据获取方法的流程示意图; 和 [0084] 图8为本发明实施例提供的移动终端定位装置的结构示意图。 具体实施方式 [0085] 为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。 显然,所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0086] 本发明实施例将GNSS定位技术和DR定位技术结合起来提高定位性能,主处理器将GNSS定位结果和DR定位结果以非实时方式结合起来,降低定位功率 消耗。 [0087] 具体来说,GNSS是利用导航卫星实现定位的一类系统的总称,可能包括美国的全球定位系统(Global Positioning System,GPS)、俄罗斯的格洛纳斯(GLONASS)、欧洲的伽利略(Galileo)、中国的北斗 系统,日本的准天顶卫星系统(Quasi-Zenith Satellite System,QZSS)等。 GNSS 可用于获取全球用户坐标,是一种应用广泛的定位技术。 然而,在市区,导航信号容易被建筑物反射或遮挡,定位结果存在漂移,甚至无法利用GNSS定位技术进行定位。 [0088] DR定位技术利用移动终端的传感器模块(如加速度计、陀螺仪、磁场传感器等)计算移动用户的相对位置。 DR定位技术不依赖外部无线信号,可以在导航信号受阻时进行定位。 然而,DR 定位的准确性会随着时间的推移累积误差而恶化。 [0089] 图1为本发明实施例提供的移动终端的帧结构示意图。 参考图1,移动终端包括诸如GNSS接收器等组件 10 , 一个传感器 20 , 主处理器 30 , 协处理器 40 ,第一存储单元 50 ,以及第二个存储单元 43 . 组件通过使用一条或多条总线相互通信。 本领域技术人员可以理解,图中所示的移动终端的结构并不构成对本发明的任何限制。 该结构可以是总线结构,也可以是星形结构,可以包括比图中所示更多或更少的元件,也可以组合一些部件,也可以有与图中不同的元件布局。 移动终端可以是任何移动或便携式电子设备,包括但不限于手机、移动电脑、平板电脑、个人数字助理(Personal Digital Assistant,PDA)、导航仪、移动互联网 设备(Mobile Internet Device,MID)或可穿戴设备(Wearable Device)。 [0090] GNSS 接收机 10 用于接收GNSS导航卫星发射的导航信号,并根据导航信号计算伪距、导航电文、信号强度等数据。 GNSS 接收机10 可以是GNSS接收器、GNSS定位芯片等。 GPS、GLONASS、Galileo、北斗系统、QZSS或其他系统之一的卫星可用于导航(单模接收机),也可同时使用多个系统实现定位( 多模式接收器)。 主处理器 30 根据伪距、导航电文、信号强度等数据计算出用户的位置坐标。 GNSS接收器可以包括集成电路,例如GNSS芯片。 GNSS接收器包括第一缓冲器 11 ,配置为缓冲数据,例如测量和导航消息。 第一个缓冲区 11 是集成在GNSS接收器中的存储区域并且可以包括集成电路。 [0091] 传感器 20 可以包括加速度计、陀螺仪、磁场传感器等。 传感器 20 连接到协处理器 40 使用I2C总线等传输电路,传输传感器测量得到的物理数据 20 到协处理器 40 用于处理。 [0092] 主处理器 30 和协处理器 40 是移动终端的控制中心; 通过各种接口和线路连接到整个电子设备的各个部分; 运行或执行存储单元中存储的软件程序和/或模块,并调用存储单元中存储的数据,以实现电子设备的各种功能和/或处理数据。 主处理器 30 和协处理器 40 可以包括集成电路(Integrated Circuit,简称IC),例如可以包括单个封装好的IC,也可以包括多个功能相同或不同的封装好的IC。 例如,主处理器 30 和协处理器 40 可以只包括中央处理单元(Central Processing Unit,CPU),也可以包括图形处理单元(Graphics Processing Unit,GPU)、数字信号处理器(Digital Signal Processor,简称DSP)和控制器的组合 通信单元的芯片(例如基带芯片)。 在本发明实施例中,CPU可以是单核处理器,也可以是多核处理器。 [0093] 主处理器 30 由于处理能力更强,电路结构更复杂,功耗也更高。 协处理器由于处理能力较弱,电路结构较简单,功耗较低。 例如,协处理器可以包括微控制器单元(Microcontroller Unit,MCU),也可以通过传感器集线器(Sensor Hub)技术实现。 第一存储单元 50 配置为提供主处理器 30 具有代码存储和处理所需的存储容量。 [0094] 协处理器 40 包括第二个缓冲区 41 ,用于缓存对传感器模块输出的物理数据进行处理得到的用户位置变化信息。 第二存储单元 43 配置为提供协处理器 40 具有代码存储和处理过程所需的存储容量。 第一存储单元 50 第二存储单元 43 可以被配置为存储软件程序和模块。 主处理器 30 和协处理器 40 运行存储在第一存储单元中的软件程序和模块 50 第二存储单元 43 ,实现移动终端的各种功能和应用,实现数据处理。 第一存储单元 50 第二存储单元 43 包括程序存储区和数据存储区。 程序存储区可以存储操作系统,以及至少一种功能所需的应用程序,例如音频播放程序和图像播放程序。 数据存储区可以存储移动终端使用过程中产生的数据(如音频数据和电话簿)等。 在本发明实施例中,第一存储单元 50 第二存储单元 43可以包括易失性存储器,例如非易失性动态随机存取存储器(Nonvolatile Random Access Memory,NVRAM)、相变随机存取存储器(Phase Change RAM,PRAM)和磁阻随机存取存储器(Magetoresistive RAM,MRAM) ; 并且可以包括非易失性存储器,例如至少一个磁盘存储设备、电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory,EEPROM)和闪存设备,例如NOR闪存(NOR 闪存)或 NAND 闪存(NAND 闪存)。 非易失性存储器存储操作系统和主处理器执行的应用程序 30 和协处理器 40 . 主处理器 30 和协处理器 40 将非易失性存储器中的运行程序和数据加载到存储器中,并将数字内容存储在大容量存储装置中。 操作系统包括各种组件和/或驱动程序,用于控制和管理常规系统任务,例如内存管理、存储设备控制和电源管理,并促进各种硬件和软件之间的通信。 在本发明实施例中,操作系统可以是谷歌的Android系统、苹果公司开发的iOS系统、微软公司开发的Windows操作系统等,也可以是Vxworks等嵌入式操作系统。 [0095] 缓冲器是一种存储单元,可以快速读写,一般采用寄存器电路实现。 第一个缓冲区 11 配置为缓冲 GNSS 接收器的数据 10 需要传输到主处理器 30 . 第二个缓冲区 41 配置为缓冲协处理器的数据 40 需要传输到主处理器 40 . [0096] 图2为本发明实施例提供的另一种移动终端的帧结构示意图。 参见图2,基于图1所示实施例提供的移动终端,一种GNSS接收机 10 未连接到主处理器 30 通过使用总线,但直接连接到协处理器 40 通过使用传输电路。 例如,传输电路可以是通用异步接收器/发送器(Universal Asynchronous Receiver/Transmitter,UART)。 [0097] 图1所示的移动终端通过使用GNSS接收器接收 10 ,GNSS导航卫星发送的导航信号,根据导航信号计算伪距、导航电文、信号强度等数据,并将数据缓存到第一缓冲区 11 GNSS 接收机 10 . 在处理过程中,主处理器 30 从第一个缓冲区中读取伪距、导航信息、信号强度等数据 11 计算用户对应的位置坐标。 [0098] 与图1所示的移动终端相比,在GNSS接收器中没有设置第一缓冲器 10 GNSS接收机接收到GNSS导航卫星发射的导航信号,根据导航信号计算伪距、导航电文、信号强度等数据后, 10 不缓存数据,而是直接将数据传输到协处理器 40 通过使用传输电路。 协处理器 40 根据伪距、导航电文、信号强度等数据实时计算出用户的位置坐标,并将用户的位置坐标缓存到第二缓冲区 41 协处理器 40 . [0099]本发明实施例可以应用于非实时定位场景。 例如,当用户在跑步时,可以使用手机记录跑步轨迹。 在录制过程中,手机可能处于熄屏(screen-turnoff)状态,即主处理器处于休眠状态。 在这种情况下,手机不会实时计算当前位置,而是缓存GNSS和DR数据,在主处理器唤醒后,根据缓存的数据计算用户的跑步轨迹坐标。 [0100] 下面结合具体实施例对本发明的技术方案进行详细说明。 以下具体实施例可以相互结合,相同或相似的概念或过程在某些实施例中不再赘述。 [0101] 图3为本发明实施例提供的移动终端定位方法的流程示意图。 图3所示的定位方法可以由图1或图2所示的移动终端实现。 参见图3,在本发明实施例中,移动终端包括主处理器,该方法包括以下步骤 . [0102] 小号 301 . 主处理器在经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠的导航数据,其中N≥M,M≥1,M和N为整数,N条导航数据 是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 [0103] 具体地,导航数据可以是根据卫星信号计算得到的中间数据,例如伪距、导航电文、信号强度等数据。 中间数据用于计算最终位置坐标。 或者,导航数据可以是根据卫星信号计算得到的位置坐标。 位置坐标可以是经纬度坐标,也可以是其他可以表示移动终端位置的坐标形式。 [0104] 当导航数据为伪距、导航消息、信号强度等中间数据时,图3所示的定位方法可以通过图1所示的移动终端来实现。 具体地,GNSS接收机 10 在第一时间段接收移动终端的卫星导航信号,根据卫星导航信号计算伪距、导航电文、信号强度等数据,并缓存伪距、导航电文等数据, 和信号强度进入第一个缓冲区 11 . 主处理器 30 可以根据伪距、导航信息、信号强度等数据计算出移动终端对应的位置坐标。 [0105] 当导航数据为位置坐标时,图3所示的定位方法可以由图2所示的移动终端来实现。 具体地,GNSS接收机 10 在第一时间段内接收移动终端的卫星导航信号,并根据卫星导航信号计算出伪距、导航电文、信号强度等中间数据。 协处理器 40 根据伪距、导航信息、信号强度等数据计算移动终端对应的位置坐标,并将位置坐标缓存到第二缓存中 41 . [0106] 具体来说,在第一个时间段内,GNSS 接收机 10 可以间歇性地计算伪距、导航电文、信号强度等数据,例如每隔1s或5s计算一次。 因此,在第一时间段内对应得到多个时间点的导航数据。 当获取导航数据对应的时刻时,可以根据卫星导航信号获取该时刻的信息,也可以通过时钟信号(例如协处理器的时钟)来标记导航数据对应的时刻 40),即系统的时间戳。 [0107] 缓存第一时间段的N条导航数据。 在经过第一时间段之后的第一时刻后,主处理器可以从缓存的N个导航数据中获取M个可靠导航数据。 第一时刻可以是第一时间段的最后时刻。 也就是说,在第一个时间段过去后,主处理器 30 可以读取缓冲的导航数据。 GNSS 接收机接收到的卫星信号的信号强度 10 可能不稳定。 当卫星信号的信号强度比较强时,根据卫星信号计算得到的导航数据是准确的,即可靠的。 当卫星信号的信号强度较弱时,根据卫星信号计算得到的导航数据可能不准确,即不可靠。 因此,主处理器 30 在读取缓存的导航数据时,获取M个可靠的导航数据。 [0108] 在缓存导航数据的过程中,主处理器 30 可能处于休眠状态以降低功耗。 然后是主处理器 30 唤醒后可以处理缓存的导航数据。 具体来说,主处理器可能有多种状态 30 . 例如,主处理器 30 第一时刻前处于休眠状态,主处理器 30 在第一时间被唤醒。 被唤醒后,主处理器 30 获取缓冲的导航数据。 如果第一时刻是第一时间段的最后时刻,主处理器 30 第一时间段处于休眠状态,主处理器 30 在第一个时间段过去后被唤醒。 被唤醒后,主处理器 30 获取缓冲的导航数据。 [0109] 具体来说,主处理器 30 可以定期唤醒,也可以通过设置的触发条件唤醒。 例如,当移动终端的屏幕打开时,主处理器被唤醒,或者在定位过程结束后,主处理器被唤醒。 [0110] 小号 302 . 主处理器在经过第一时间段后,获取移动终端缓存的K条位置变化数据,其中K≥1,K为整数,利用得到的数据计算得到K条位置变化数据 通过移动终端的传感器在第一时间段内进行监测。 [0111] 具体来说,在第一时间段内,传感器 20 监控移动设备的运动数据(例如,加速度计、陀螺仪或磁场传感器的观测数据),并将监控得到的运动数据传送给协处理器 40 . DR 模块在协处理单元中运行。 DR模块根据传感器监测得到的数据,计算出移动终端的K条位置变化数据(包括移动方向变化和相邻时刻之间的距离),即进行航位推算DR; 并将K条位置变化数据缓存到第二个缓冲区中 41 . 航位推算DR也可以间歇进行,例如每隔1s或5s一次,从而可以得到移动终端在相邻两个计算时刻之间的位置变化数据。 协处理器可以通过时钟电路记录每个计算时刻,并在保存K条位置变化数据时记录对应的计算时刻,即时间戳。 时间戳和K条位置变化数据一起缓存到第二个缓存中 41 . [0112] 在缓存K个位置变化数据的过程中,主处理器 30 可能处于休眠状态以降低功耗。 被唤醒时,主处理器 30 可以对缓存的K个位置变化数据进行处理。 [0113]可选地,在航位推算DR过程中,可以以固定的时间间隔计算位置变化数据,也可以在满足设定条件时计算。 例如,当检测到移动终端的移动距离超过设定的阈值时,计算移动终端的位置变化数据。 或者,可以根据时间间隔和空间移动距离确定是否需要计算移动终端的位置变化数据。 例如,设置时间间隔阈值和空间移动距离阈值,当满足任一阈值条件时,可以计算位置变化数据。 [0114] 可选地,GNSS接收器的时钟电路可以与协处理器的时钟电路异步。 N条导航数据和对应的时间戳保存在第一个缓冲区中 11 GNSS 接收机 10 . K个位置变化数据和对应的时间戳存储在第二个缓冲区中 41 协处理器 40 . [0115] 可选地,GNSS 接收器之间的时钟同步 10 和协处理器 40 可以使用同步时钟电路来实现。 在这种情况下,不需要保存N个导航数据对应的时间戳和K个位置变化数据对应的时间戳。 [0116] 需要说明的是,在本发明实施例中,步骤S的执行顺序 301 和步骤 S 302 不受限制。 脚步 301 可以先执行,或者步骤 S 302 可以先执行,也可以两步同时执行。 此外,在第一时间段内,GNSS接收器获取卫星导航信号和传感器监测移动终端移动数据的执行顺序不设限制。 [0117] 小号 303 . 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0118] 为了在保证移动终端能够正常定位的同时提高移动终端的定位精度,主处理器将M个可靠导航数据和K个位置变化数据进行合并。 [0119] 具体地,主处理器从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据。 主处理器结合可靠的导航数据和相互匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0120] 可靠导航数据的数​​量可以等于或小于位置变化数据的数量。 当可靠导航数据的数​​量与位置变化数据的数量相等且每个导航数据与一个位置变化数据匹配时,未合并的位置变化数据的数量为零。 即对所有位置变化数据和匹配的导航数据进行融合处理。 当可靠导航数据的数​​量小于位置变化数据的数量时,只对匹配的可靠导航数据和位置变化数据进行融合处理。 [0121] 具体地,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻。 当m的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一块位置变化数据。 那一刻的m th 一条导航数据与n的时刻相同 th 一条位置变化数据表示两个时刻的时间差在允许的误差范围内(即两个时刻的差小于或等于预设阈值)。 如果至少两个GNSS导航数据对应的坐标点与一个位置变化数据对应的同一个DR坐标点匹配,则只保留一个GNSS导航数据对应的坐标点。 为了降低功耗,GNSS导航数据的计算时间间隔可以长于位置变化数据的计算时间间隔,或者GNSS导航数据的计算时间间隔可以是位置变化数据的计算时间间隔的倍数 . [0122] 在主处理器将M个可靠导航数据与K个位置变化数据进行匹配的过程中,可选地,当GNSS接收机的时钟电路与协处理器的时钟电路异步时,主处理器进行匹配 根据第一缓存中M个可靠导航数据对应的时间戳和第二缓存中K个位置变化数据对应的时间戳,将时间戳相等或相同的导航数据和位置变化数据合并 最接近。 [0123] 可选地,当GNSS接收机的时钟电路与协处理器的时钟电路同步时,主处理器可以直接将同一时刻的导航数据和位置变化数据进行合并,而不需要通过时间戳进行匹配。 具体地,当导航数据为根据移动终端的卫星导航信号计算得到的位置坐标时,主处理器将相互匹配的可靠导航数据和位置变化数据进行组合,可以但不限于: 以下实施方式。 [0124] 主处理器得到匹配的导航数据和位置变化数据后,根据位置变化数据对应的时间点建立卡尔曼滤波过程。 根据卡尔曼滤波对匹配的可靠导航数据和位置变化数据进行融合处理的具体过程如下。 [0125] 在DR过程中可以得到用户在两个时刻的位置坐标的变化,据此可以得到卡尔曼滤波的状态方程: X k+1 =F k ·X k [0126] 其中,X为卡尔曼滤波中的待估计向量,具体可以包括用户坐标、用户运动方向等。 k表示待估计向量对应的矩; 和 F k 反映了向量 X 在两个相邻时刻的变化关系(即 k th 时刻和 (k+1) th 时刻,其中 k th 时刻在 (k+1) 之前 th 时刻),和 F k 是矩阵,可以根据DR模块的输出结果得到。 [0127] 此外,如果在 k th 时刻,有可靠的导航数据与位置变化数据相匹配,可靠的导航数据在 k th 时刻被标记为观察向量 Z k , 可以建立一个观测方程: Z k =H k ·X k [0128] 其中 H k 表示观测方程在 k 处的系数矩阵 th 片刻。 [0129] 本发明实施例中,可靠导航数据与位置变化数据相互匹配的卡尔曼滤波过程可以建立如下: [0130] (1)初始化卡尔曼滤波参数:X 0 和 P 0 . X 0 表示待估计向量的初始值,P 0 表示 X 的均方误差矩阵 0 初始化时。 [0131] (2) 进行一步预测:X k+1/k =F x ·X k , 其中 X k+1/k 表示一个预测向量,在 (k+1) th 时刻,根据k处的待估计向量得到 th 片刻。 [0132] (3) 对一个均方误差矩阵进行一步预测:P k+1/k =F k ·P k ·F k T +Q k , 其中 P k 表示 X 的均方误差矩阵 k 在 k th 片刻; 磷 k+1/k 表示预测的均方误差矩阵,在 (k+1) th 时刻,根据 k 处的均方误差矩阵得到 th 片刻; F k T 表示 F 的转置矩阵 k ; 和问 k 表示卡尔曼滤波系统的噪声协方差矩阵,用于表示状态方程的可靠程度。 [0133] (4) 计算一个滤波器增益:K k+1 =P k+1/k ·H k+1 T ·(H k+1 ·P k+1/k ·H k+1 T +R k+1 ) −1 [0134] 其中K k+1 表示卡尔曼滤波系统在 (k+1) 处的滤波增益 th 片刻; H k+1 T 表示 H 的转置矩阵 k+1 ; 和 R k+1 表示在 (k+1) 处观察到的噪声协方差 th 矩,用来表示观测方程的可靠程度。 [0135] (5) 计算可靠的导航数据和相互匹配的位置变化数据合并后的结果: X k+1 =X k+1/k +K k+1 ·(Z k+1 -H k+1 ·X k+1/k )。 [0136] (6) 更新均方误差矩阵:P k+1 =(I−K k+1 ·H k+1 )·P k+1/k ,其中 I 是单位矩阵。 [0137] 如果在 (k+1) th 此时,不存在与位置变化数据相匹配的可靠导航数据,本发明实施例根据卡尔曼滤波状态方程对未合并的位置变化数据建立卡尔曼滤波过程如下 : [0138] (1) 进行一步预测:X k+1/k =F k ·X k , 其中 X k+1/k 表示一个预测向量,在 (k+1) th 时刻,根据k处的待估计向量得到 th 片刻。 [0139] (2) 对一个均方误差矩阵进行一步预测:P k+1/k =F k ·P k ·F k T +Q k 其中P k 表示 X 的均方误差矩阵 k 在 k th 片刻; 磷 k+1/k 表示预测的均方误差矩阵,在 (k+1) th 时刻,根据 k 处的均方误差矩阵得到 th 片刻; F k T 表示 F 的转置矩阵 k ; 和问 k 表示卡尔曼滤波系统的噪声协方差矩阵,用于表示状态方程的可靠程度。 [0140] (3)更新待估计向量的结果:X k+1 =X k+1/k . [0141] (4) 更新均方误差矩阵:P k+1 =P k+1/k . [0142] GNSS接收机和DR模块在将可靠的导航数据和相互匹配的位置变化数据进行组合的过程中,可以具有但不限于以下几种操作方式。 [0143] GNSS接收机的一种工作方式是:GNSS接收机和DR模块全程开启,计算相应的导航数据和位置变化数据。 [0144]GNSS接收机的另一种工作方式是:DR模块全程开启,GNSS接收机间歇性开启(如图4所示)。 图4为本发明实施例提供的GNSS接收机和DR模块的工作方式示意图。 参见图4,在主处理器结合可靠导航数据和位置变化数据相互匹配的过程中,DR模块在整个过程中处于开启状态,而GNSS接收器则进入休眠状态或低电平状态。 开机一段时间后的耗电状态。 此外,还增加了在每个时间段开始时打开 GNSS 接收器的步骤。 当DR模块持续开启时,GNSS接收器的工作状态相对灵活,GNSS接收器可以根据预设规则交替处于工作状态和休眠状态。 例如,当DR模块和GNSS接收器在一段时间内都开启时,主处理器可以将相互匹配的导航数据和位置变化数据进行组合。 当DR模块开启而GNSS接收机休眠一段时间后,主处理器仅通过位置变化数据获取移动终端的位置信息。 [0145] 还有一种工作方式是:GNSS接收机和DR模块交替开启,即交替计算导航数据和位置变化数据。 在这种情况下,无需将导航数据与位置变化数据进行匹配或进行卡尔曼滤波。 只有导航数据时,根据导航数据获取位置坐标点。 当只有位置变化数据时,根据上一时刻的位置坐标点,递归得到位置坐标点。 [0146] 具体来说,在步骤 303 ,当导航数据是利用移动终端的卫星导航信号计算得到的数据,需要计算位置坐标时,主处理器将M个可靠导航数据与K 获取移动终端在第一时间段内的位置信息的位置变化数据包括: [0147] 主处理器根据M个可靠导航数据计算得到M个位置坐标; 和 [0148] 主处理器结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0149] 当导航数据为利用移动终端的卫星导航信号计算得到的用于计算位置坐标的中间数据(如伪码、导航电文、信号强度等)时, 主处理器不能直接结合中间数据和位置变化数据。 主处理器在进行融合处理前,首先从可靠的导航数据中计算出对应的位置坐标,然后通过卡尔曼滤波将M个位置坐标和K个位置变化数据结合起来,首先得到移动终端的位置信息。 时间段。 具体融合过程与上述方法相同,此处不再赘述。 [0150] 具体地,第一时间段内移动终端的位置信息包括至少两个位置坐标,每个位置坐标对应第一时间段的一个时刻。 [0151] 步骤 S 之后 303 ,本实施例还可以包括以下步骤。 [0152] 小号 304 . 主处理器在第一时间段内获得移动终端的位置信息后进入休眠状态。 [0153] 在获得移动终端的位置信息后,如果不需要处理其他任务,则主处理器可以进入休眠状态以降低功耗。 [0154]在本发明实施例中,分别缓存第一时间段内获取的N个导航数据和K个位置变化数据。 主处理器可以在经过第一时间段后获取K个位置变化数据,从缓存的N个导航数据中获取M个可靠导航数据,将可靠导航数据和位置变化数据结合,得到位置 移动终端的信息。 在获取N个导航数据和K个位置变化数据的过程中,不需要实时开启主处理器,从而降低了系统的定位功耗。 [0155] 具体地,步骤S中主处理器从移动终端缓存的N条导航数据中获取M条可靠的导航数据 101 可以通过但不限于以下两种可能的实现方式来实现。 [0156] 图5为本发明实施例提供的可靠导航数据获取方法的流程示意图。 图6是图5中获取可靠导航数据的方法的具体实施方式的流程示意图。 参见图5和图6,在一种可能的实施方式中,第一时间段之前的导航数据的状态不是 在第一个时间段之前确定或没有缓冲的导航数据。 如图5和图6所述,主处理器从移动终端缓存的N个导航数据中获取M个可靠的导航数据包括以下步骤。 [0157] 小号 501 . 主处理器按照矩的顺序遍历N个导航数据的信号强度。 [0158] N个导航数据中的每一个都对应一个时刻和一个信号强度。 N条导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照时刻的顺序。 [0159] 具体地,时刻的顺序是指按照时刻的时间顺序,在先的时刻为前时刻,后的时刻为后时刻。 [0160] 小号 502 . 主处理器确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据。 [0161] 第一时间段之前的导航数据的状态未确定或者第一时间段之前没有缓存的导航数据。 主处理器 30 根据第一阈值确定第一导航数据,以根据第一导航数据确定导航数据跟随第一导航数据的状态。 第一阈值可以预先设置。 具体来说,主处理器 30 根据时刻的顺序确定N条导航数据的信号强度(如图6所示)。 在判断过程中,判断信号强度大于或等于第一阈值的第一导航数据的导航数据的状态为高,并将导航数据判断为第一导航数据。 [0162] 具体来说,在 GNSS 导航期间,GNSS 接收机 10 接收来自多颗卫星的信号,每个卫星信号对应一个信号强度,信号强度一般用信噪比或载噪比来表示。 当某一时刻接收到的导航数据的信号强度(例如,时刻 T a ) 计算,卫星信号强度在时刻 T 分辨率的平均值 a 可以计算; 或在时刻 T 分辨率的卫星信号强度的最小值 a 可以计算; 或者可以计算A卫星信号强度的平均值,也可以计算A卫星信号强度最小值。 A卫星是所有可见卫星中按信号强度降序排列的第一个A卫星,A不大于B,B是T时刻所有可见卫星的数量 a . 可见卫星是 GNSS 接收器所在的卫星 10 可以接收导航信号。 [0163] 小号 503 . 处理器通过如下方式确定另一条导航数据的状态,其中,另一条导航数据是N条导航数据中在第一条导航数据之后的导航数据: 如果是当前导航数据的状态 吨 i 为高,当导航数据的信号强度在时刻 t i+1 小于第二阈值,确定导航数据在时刻t的状态 i+1 低; 或者如果在时刻 t 的导航数据状态 i 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,确定导航数据在时刻t的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值。 [0164] 具体地,处理器在确定第一导航数据之后的导航数据的状态时,可以根据第一导航数据的状态、第二阈值和第三阈值确定下一时刻导航数据的状态。 可以根据当前时刻的导航数据的状态确定每个导航数据在下一时刻的状态。 例如,假设某时刻导航数据的状态为 t 2 判断为高,导航数据在时刻t的信号强度是否 3 确定小于第二阈值。 如果此时导航数据的信号强度为 t 3 小于第二阈值,导航数据在t时刻的状态 3 确定为低。 如果此时导航数据的信号强度为 t 3 不小于第二阈值,t时刻导航数据的状态 3 确定为高。 假设某一时刻导航数据的状态为 t 2 判断为低,导航数据是否在t时刻的信号强度 3 大于第三阈值被确定。 如果此时导航数据的信号强度为 t 3 大于第三阈值,导航数据在t时刻的状态 3 确定为高。 如果此时导航数据的信号强度为 t 3 不大于第三阈值,t时刻导航数据的状态 3 确定为低。 [0165] 具体地,当移动终端进入建筑物时,导航信号容易被遮挡。 因此,需要设置较高的第二阈值,以便尽快丢弃导航信号强度不够强的GNSS导航数据,使用DR得到的移动终端位置变化数据。 这样就保证了移动终端可以正常定位。 同理,当移动终端离开建筑物时,由于使用DR得到的移动终端位置变化数据的累积误差较大,因此需要设置较低的第三阈值。 即需要将第三阈值设置为小于第二阈值,以便尽快合并GNSS导航数据,保证移动终端的定位精度。 可选的,第二阈值可以与第一阈值相同,也可以与第一阈值不同。 [0166] 小号 504 . 处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0167]图7为本发明实施例提供的另一种可靠导航数据获取方法的流程示意图。 在另一种可能的实施方式中,第一时间段内的第一导航数据之前存在导航数据,并确定第一时间段内第一导航数据之前的导航数据的状态。 主处理器从移动终端缓存的N条导航数据中获取M条可靠的导航数据包括以下步骤。 [0168] 小号 701 . 主处理器按照矩的顺序遍历N个导航数据的信号强度。 [0169] N个导航数据中的每一个都对应一个时刻和一个信号强度。 N条导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照时刻的顺序。 [0170] 小号 702 . 主处理器获取N个导航数据中的第一个导航数据之前的先前导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 . [0171] 小号 703 . 主处理器通过以下方式确定N条导航数据的状态:如果在时刻t的导航数据的状态 i−1 为高,当导航数据的信号强度在时刻 t i 小于第二阈值,确定导航数据在时刻t的状态 i 低; 或者如果某一时刻导航数据的状态为低,当某一时刻导航数据的信号强度为 t i 大于或等于第三阈值,确定导航数据在时刻t的状态 i 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值。 [0172] 确定第一时间段内第一条导航数据之前的先前导航数据的状态。 因此,主处理器可以根据之前的导航数据的状态确定第一时间段内的第一导航数据的状态,并根据第一时间段的状态确定下一时刻的导航数据的状态。 第一时间段内的导航数据,以此类推。 具体地,在另一种实施方式中,主处理器根据前一导航数据的状态判断第一导航数据的状态,以及根据前一导航数据的状态判断下一时刻导航数据状态的方式。 第一条导航数据与S中描述的方法相同 503 ,此处不再赘述。 [0173] 小号 704 . 处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0174] 本发明实施例还提供一种移动终端的定位装置。 图8为本发明实施例提供的移动终端定位装置的结构示意图。 参见图8,定位装置至少包括获取模块 810 和数据处理模块 820 . [0175] 具体来说,获取模块 810 用于在经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠的导航数据,其中N≥M,M≥1,M和N为整数,N条导航数据 是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 [0176] 获取模块 810还用于在经过第一时间段后,获取缓存的移动终端的K条位置变化数据,其中,K≥1,K为整数,K条位置变化数据由以下数据计算得到: 通过移动终端的传感器在第一时间段内监测得到。 [0177] 数据处理模块 820 用于将M个可靠导航数据和K个位置变化数据结合起来,得到移动终端在第一时间段内的位置信息。 [0178] 可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序。 [0179] 获取模块 810 专门配置为: [0180] 按照矩的顺序遍历N个导航数据的信号强度; [0181] 确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据; [0182] 判断另一条导航数据状态的方式如下,其中该另一条导航数据是N条导航数据中在第一个导航数据之后的导航数据: 如果某时刻t的导航数据的状态 i 为高,当导航数据的信号强度在时刻 t i+1 小于第二个阈值,判断t时刻导航数据的状态 i+1 低; 或者如果在时刻 t 的导航数据状态 1 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,判断t时刻导航数据的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 和 [0183] 将所有状态为高的导航数据确定为M个可靠导航数据。 [0184] 可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序。 [0185] 获取模块 810 专门配置为: [0186] 按照矩的顺序遍历N个导航数据的信号强度; 获取N个导航数据中第一个导航数据之前的前一个导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 ; [0187] N个导航数据的状态判断方法如下:如果某时刻t的导航数据的状态 i−1 为高,当导航数据的信号强度在时刻 t i 小于第二个阈值,判断t时刻导航数据的状态 i 低; 或者如果在时刻 t 的导航数据状态 i−1 低,当导航数据的信号强度在时刻 t i 大于或等于第三阈值,判断t时刻导航数据的状态 i 为高,其中1≤i≤n,第二阈值大于第三阈值; 和 [0188] 将所有状态为高的导航数据确定为M个可靠导航数据。 [0189] 可选的,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻; 当 m 的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一块位置变化数据。 [0190]数据处理模块 820 专门配置为: [0191] 从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据; 和 [0192] 结合可靠的导航数据和相互匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0193] 可选地,所述导航数据为利用所述移动终端的卫星导航信号计算得到的、用于计算位置坐标的数据。 数据处理模块 820 专门配置为: [0194] 根据M个可靠导航数据计算得到M个位置坐标; 和 [0195] 结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0196] 可选的,该装置还包括: [0197] 唤醒模块 830 ,用于在经过第一时间段后唤醒定位装置; 其中,定位装置在第一时间段内处于休眠状态。 [0198] 可选的,该装置还包括: [0199] 睡眠模块 840 ,用于在获取到移动终端在第一时间段内的位置信息后,使定位装置进入休眠状态。 [0200] 本发明实施例提供的移动终端定位装置,具体用于执行方法实施例提供的技术方案。 其实现原理和效果与方法实施例类似,在此不再赘述。 [0201] 本发明实施例还提供一种移动终端。 参考图1和图2,移动终端至少包括主处理器 30 , 全球导航卫星系统 GNSS 接收机 10 , 一个传感器 20 , 和协处理器 40 . [0202] 主处理器 30 用于执行方法实施例中描述的方法。 [0203] GNSS 接收机 10 用于在第一时间段接收移动终端的卫星导航信号,并根据卫星导航信号计算导航数据,导航数据为计算位置坐标的数据或导航数据为位置坐标 . [0204] 传感器 20 用于监测第一时间段内移动终端的运动数据。 [0205] 协处理器 40 用于根据传感器获取的运动数据计算得到K个位置变化数据 20 通过监控。 或者,协处理器 40 用于根据传感器监测得到的运动数据计算得到K个位置变化数据,并根据导航数据计算出位置坐标。 [0206] 可选地,第一时间段包括第二时间段,GNSS接收机 10 在第二时间段内处于休眠状态。 传感器 20 在第一时间段处于工作状态。 [0207] 本发明实施例提供的移动终端可以执行方法实施例提供的技术方案。 其实现原理和效果与方法实施例类似,在此不再赘述。 [0208]本领域普通技术人员可以理解,上述方法实施例的全部或者部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机、手机或其他便携设备可以读取的存储介质中。 当程序运行时,执行方法实施例的步骤。 上述存储介质包括:ROM、RAM、磁盘、光盘等任何可以存储程序代码的介质。 [0209] 最后需要说明的是,上述实施例仅仅用以说明本发明的技术方案,并不用于限制本发明。 尽管结合上述实施例对本发明进行了详细描述,但本领域普通技术人员应当理解,他们仍然可以对上述实施例中描述的技术方案进行修改或者对部分或全部技术特征进行等同替换 在不脱离本发明实施例技术方案的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.103 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN108029092A(String), CN108029092B(String), IN201827013200A(String), JP2019502895A(String), JP6646741B2(String), US11209555B2(String), US20180239027A1(String), WO2017054298A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN108029092A(String), CN108029092B(String), IN201827013200A(String), JP2019502895A(String), JP6646741B2(String), US11209555B2(String), US20180239027A1(String), WO2017054298A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US11209555B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN108029092A(String), CN108029092B(String), IN201827013200A(String), JP2019502895A(String), JP6646741B2(String), US11209555B2(String), US20180239027A1(String), WO2017054298A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), CN108029092A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), CN108029092B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), IN201827013200A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), JP2019502895A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), JP6646741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), US11209555B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.177 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.177 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), US20180239027A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270662(Integer), WO2017054298A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US11209555B2(String), US11209555B2(String), 1640620800(Integer), 270662(Integer), 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.210 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.213 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.215 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.217 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.217 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184980(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184980(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184980(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184980(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.263 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.263 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.263 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9899854B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, master data communication device and mobile terminal charging system and method(String), 移动终端、主数据通信设备和移动终端计费系统和方法(String), US9899854B2(String), A mobile terminal, a master data communication device and a mobile terminal charging system and method are provided. The method includes that: a mobile terminal determines whether or not a power supply device is a master data communication device and, if so, determines an appropriate charging mode for charging the mobile terminal. The disclosure not only enables a mobile terminal to select a plurality of adjustable charging modes to charge the mobile terminal but also enables the terminal to select a most appropriate charging mode to charging the mobile terminal, thus improving the charging efficiency.(String), 提供了一种移动终端、主数据通信设备以及移动终端计费系统和方法。 该方法包括:移动终端判断供电设备是否为主数据通信设备,如果是,则确定为移动终端充电的合适充电模式。 本发明不仅使移动终端能够选择多种可调节的充电模式对移动终端进行充电,而且使终端能够选择最合适的充电模式对移动终端进行充电,从而提高充电效率。(String), US14/428826(String), 1375286400(Integer), US9899854B2(String), 1519056000(Integer), 1519056000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 31(Integer), CN101162403A | CN101383627A | CN101853966A | CN102301305A | CN102377221A | CN102868820A | CN1617620A | CN1797894A | CN2569461Y | JP2011041394A | JP2012176786A | US20040189251A1 | US20070024239A1 | US20080084189A1 | US20080238358A1 | US20080278119A1 | US20100007310A1 | US20100026236A1 | US20110018503A1 | US20110103004A1 | US20110144823A1 | US20120181983A1 | US20130076299A1 | US20130110340A1 | US20130254580A1 | US20140035530A1 | US20140139176A1 | US20140347003A1 | US20150278038A1 | US7884571B2 | WO2005013456A1(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.300 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.301 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.301 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184981(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\193ffba619be47699ab4d337ea4a087c.png(String), 184981(Integer), 193ffba619be47699ab4d337ea4a087c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, master data communication device and mobile terminal charging system and method(String), 移动终端、主数据通信设备和移动终端计费系统和方法(String), US9899854B2(String), A mobile terminal, a master data communication device and a mobile terminal charging system and method are provided. The method includes that: a mobile terminal determines whether or not a power supply device is a master data communication device and, if so, determines an appropriate charging mode for charging the mobile terminal. The disclosure not only enables a mobile terminal to select a plurality of adjustable charging modes to charge the mobile terminal but also enables the terminal to select a most appropriate charging mode to charging the mobile terminal, thus improving the charging efficiency.(String), 提供了一种移动终端、主数据通信设备以及移动终端计费系统和方法。 该方法包括:移动终端判断供电设备是否为主数据通信设备,如果是,则确定为移动终端充电的合适充电模式。 本发明不仅使移动终端能够选择多种可调节的充电模式对移动终端进行充电,而且使终端能够选择最合适的充电模式对移动终端进行充电,从而提高充电效率。(String), US14/428826(String), 1375286400(Integer), US9899854B2(String), 1519056000(Integer), 1519056000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 31(Integer), CN101162403A | CN101383627A | CN101853966A | CN102301305A | CN102377221A | CN102868820A | CN1617620A | CN1797894A | CN2569461Y | JP2011041394A | JP2012176786A | US20040189251A1 | US20070024239A1 | US20080084189A1 | US20080238358A1 | US20080278119A1 | US20100007310A1 | US20100026236A1 | US20110018503A1 | US20110103004A1 | US20110144823A1 | US20120181983A1 | US20130076299A1 | US20130110340A1 | US20130254580A1 | US20140035530A1 | US20140139176A1 | US20140347003A1 | US20150278038A1 | US7884571B2 | WO2005013456A1(String), \20230420\193ffba619be47699ab4d337ea4a087c.png(String), 11(Integer), 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.325 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 1. A master data communication device comprising an interface unit and a command generation unit, whereinthe interface unit is configured to be connected with a mobile terminal to transfer interaction information between the master data communication device and the mobile terminal; andthe command generation unit is configured to generate a charging command and send the generated charging command to the mobile terminal via the interface unit,wherein the device further comprises a mode selection unit configured to select an adjustable charging mode needed by the mobile terminal, and accordingly, the command generation unit is configured to generate a corresponding charging command according to the adjustable charging mode selected by the mode selection unit; or the command generation unit is configured to generate a corresponding charging command based on a charging command request received from the mobile terminal;wherein the adjustable charging mode is one of a standard charging mode, a first charging mode and a second charging mode, and a working current in the standard charging mode is a first working current commonly used by the master data communication device, a working current in the first charging mode is a second working current higher than the first working current, a working current in the second charging mode is a third working current higher than the second working current, and the third working current is the maximum working current that the master data communication can supply.(String), 1.主控数据通讯设备包括接口单元和命令生成单元,其中接口单元,用于与移动终端连接,传递数据通信主设备与移动终端之间的交互信息;和命令生成单元,用于生成充电命令,并将生成的充电命令通过接口单元发送给移动终端,其中,所述装置还包括模式选择单元,用于选择移动终端需要的可调充电模式,相应地,命令生成单元用于根据模式选择单元选择的可调充电模式生成相应的充电命令。或者,命令生成单元,用于根据从移动终端接收到的充电命令请求,生成相应的充电命令;其中,可调充电模式为标准充电模式、第一充电模式和第二充电模式中的一种,标准充电模式下的工作电流为数据通信主设备常用的第一工作电流,工作电流为第一充电模式为高于第一工作电流的第二工作电流,第二充电模式下的工作电流为高于第二工作电流的第三工作电流,第三工作电流为主数据的最大工作电流。通讯可以供应。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 2. The master data communication device according to claim 1, further comprising an identification unit configured to identify whether or not the mobile terminal supports adjustable charging modes.(String), 2.根据权利要求1所述的主数据通信装置,还包括识别单元,用于识别移动终端是否支持可调充电模式。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 3. The master data communication device according to claim 1, wherein the command generation unit is configured to automatically generate a charging command corresponding to a maximum working current available in adjustable charging modes supported by the mobile terminal.(String), 3.根据权利要求1所述的主数据通信装置,其中命令生成单元,用于自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令。4、移动终端充电系统包括一种数据通信主设备和移动终端,其中主数据通信设备与移动终端连接;数据通信主设备,用于向移动终端发送充电命令;和移动终端,用于接收来自数据通信主设备的充电指令,选择与充电指令对应的可调充电模式进行充电,其中,主数据通信设备根据移动终端选择的可调充电模式对应的充电命令请求发送相应的充电命令,或者根据主数据通信设备选择的可调充电模式为移动终端发送相应的充电命令。移动终端,或者自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令,并发送生成的充电命令;其中,可调充电模式为标准充电模式、第一充电模式和第二充电模式中的一种,标准充电模式下的工作电流为数据通信主设备常用的第一工作电流,工作电流为第一充电模式为高于第一工作电流的第二工作电流,第二充电模式下的工作电流为高于第二工作电流的第三工作电流,第三工作电流为主数据的最大工作电流。通讯可以供应。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 4. A mobile terminal charging system comprising a master data communication device and a mobile terminal, whereinthe master data communication device is connected with the mobile terminal;the master data communication device is configured to send a charging command to the mobile terminal; andthe mobile terminal is configured to receive the charging command from the master data communication device and select an adjustable charging mode corresponding to the charging command so as to be charged,wherein the master data communication device sends a corresponding charging command according to a charging command request corresponding to the adjustable charging mode selected by the mobile terminal, or sends a corresponding charging command according to the adjustable charging mode selected by the master data communication device for the mobile terminal, or automatically generates a charging command corresponding to a maximum working current available in adjustable charging modes supported by the mobile terminal and sends the generated charging command;wherein the adjustable charging mode is one of a standard charging mode, a first charging mode and a second charging mode, and a working current in the standard charging mode is a first working current commonly used by the master data communication device, a working current in the first charging mode is a second working current higher than the first working current, a working current in the second charging mode is a third working current higher than the second working current, and the third working current is the maximum working current that the master data communication can supply.(String), 5.根据权利要求4所述的移动终端充电系统,其中数据通信主设备还用于判断移动终端是否支持可调充电模式。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 5. The mobile terminal charging system according to claim 4, wherein the master data communication device is further configured to determine whether or not the mobile terminal supports adjustable charging modes.(String), 6.根据权利要求4所述的移动终端充电系统,其中主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一个,其中标准充电模式、第一充电模式和第二充电模式对应于标准充电命令,分别为第一充电指令与第二充电指令。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 6. The mobile terminal charging system according to claim 4, wherein the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command wherein the standard charging mode, the first charging mode and the second charging mode are corresponding to the standard charging command, the first charging command and the second charging command, respectively.(String), 7.根据权利要求6所述的移动终端充电系统,其中标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。8、一种移动端充电方法,包括:移动终端与主数据通信设备连接;数据通信主设备向移动终端发送相应的充电指令;和移动终端根据相应的充电指令选择相应的充电模式为移动终端充电,其中,在主数据通信设备向移动终端发送相应的充电命令之前,该方法还包括:主数据通信设备判断移动终端是否支持可调充电模式;数据通信主设备在确定移动终端支持可调充电模式后,向移动终端发送相应的充电命令,其中,数据通信主设备向移动终端发送相应的充电命令包括:移动终端选择需要的可调充电模式,并向数据通信主设备发送与选择的可调充电模式对应的充电命令请求;数据通信主设备根据充电命令请求向移动终端发送相应的充电命令;或者数据通信主设备为移动终端选择可调充电模式,数据通信主设备根据选择的可调充电模式生成相应的充电命令,数据通信主设备发送向移动终端生成充电命令;或者数据通信主设备自动生成移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令,并将生成的充电命令发送给移动终端;其中,可调充电模式为标准充电模式、第一充电模式和第二充电模式中的一种,标准充电模式下的工作电流为数据通信主设备常用的第一工作电流,工作电流为第一充电模式为高于第一工作电流的第二工作电流,第二充电模式下的工作电流为高于第二工作电流的第三工作电流,第三工作电流为主数据的最大工作电流。通讯可以供应。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 7. The mobile terminal charging system according to claim 6, wherein a working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA.(String), 9.根据权利要求8所述的移动终端充电方法,其中主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一个,其中标准充电模式、第一充电模式和第二充电模式对应于标准充电命令,第一充电命令和第二充电命令,分别。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 8. A mobile terminal charging method, comprising:connecting a mobile terminal with a master data communication device;sending, by the master data communication device, a corresponding charging command to the mobile terminal; andselecting, by the mobile terminal, a corresponding charging mode according to the corresponding charging command to charge the mobile terminal,wherein before the master data communication device sends the corresponding charging command to the mobile terminal, the method further comprising: determining, by the master data communication device, whether or not the mobile terminal supports adjustable charging modes; and sending, by the master data communication device, the corresponding charging command to the mobile terminal after the master data communication device determines that the mobile terminal supports adjustable charging modes,wherein the sending, by the master data communication device, a corresponding charging command to the mobile terminal comprises:selecting, by the mobile terminal, an adjustable charging mode needed and sending, by the mobile terminal, a charging command request corresponding to the selected adjustable charging mode to the master data communication device; and sending, by the master data communication device, the corresponding charging command to the mobile terminal according to the charging command request; orselecting, by the master data communication device, an adjustable charging mode for the mobile terminal, generating, by the master data communication device, the corresponding charging command according to the selected adjustable charging mode, and sending, by the master data communication device, the generated charging command to the mobile terminal; orautomatically generating, by the master data communication device, a charging command corresponding to a maximum working current available in adjustable charging modes supported by the mobile terminal and sending, by the master data communication device, the generated charging command to the mobile terminal;wherein the adjustable charging mode is one of a standard charging mode, a first charging mode and a second charging mode, and a working current in the standard charging mode is a first working current commonly used by the master data communication device, a working current in the first charging mode is a second working current higher than the first working current, a working current in the second charging mode is a third working current higher than the second working current, and the third working current is the maximum working current that the master data communication can supply.(String), 10.根据权利要求9所述的移动终端充电方法,其中标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 9. The mobile terminal charging method according to claim 8, wherein the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command, wherein the standard charging mode, the first charging mode and the second charging mode are corresponding to the standard charging command, the first charging command and the second charging command, respectively.(String), 11.根据权利要求1所述的主数据通信装置,其中指令产生单元所产生的充电指令为标准充电指令、第一充电指令及第二充电指令其中之一,其中标准充电模式、第一充电模式及第二充电模式对应于标准充电指令,分别为第一充电指令与第二充电指令。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 10. The mobile terminal charging method according to claim 9, wherein a working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184981(Integer), 11. The master data communication device according to claim 1, wherein the charging command generated by the command generation unit is one of a standard charging command, a first charging command and a second charging command, wherein the standard charging mode, the first charging mode and the second charging mode are corresponding to the standard charging command, the first charging command and the second charging command, respectively.(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184981(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of electronic communications, and in particular to a mobile terminal, a master data communication device and a mobile terminal charging system and method. BACKGROUND [0002]At present, it is very convenient to use mobile terminal devices because of the employment of a USB interface as a power interface by chargers for most of mobile terminal devices such as mobile phones, cameras and PAD and due to the easiness of getting a standard USB master device which is capable of charging these mobile terminal devices. However, as the current provided by a standard USB master device is small, for example, the current provided by a standard USB master device with a USB2.0 interface is 500 mA, and that provided by a standard USB master device with a USB1.1 interface is 250 mA, it takes a long time to charge a mobile terminal using a standard USB master device, resulting in poor user experience. Some existing portable power sources with a USB interface are capable of supplying a larger charging current, for example, a current of 800 mA, 1 A or even 1.5 A, than a standard USB master device. For existing USB master devices having a large-current charging capacity, as a USB slave device, that is, a mobile terminal, is incapable of automatically changing the magnitude of a charging current according to the power supply capacity of such a USB master device, the charging efficiency is low. For customers, it is desirable that a mobile terminal is capable of selecting a charging current as needed while providing a data communication service and that a plurality of charging modes are selectable for the convenient and rapid charging of a mobile terminal. SUMMARY [0003]The main technical problem the disclosure is intended to solve is to provide a mobile terminal, a master data communication device and a mobile terminal charging system and method to avoid a low charging efficiency caused because of the incapability of a mobile terminal to select in real time a charging mode matching with a master device to charge itself. [0004]To address the technical problem above, the technical solution of the disclosure is as follows: [0005]a mobile terminal includes a first interface unit, a first identification unit, a command receiving unit and a charging management unit, wherein [0006]the first interface unit is configured to be connected with a power supply device to transfer interaction information between the mobile terminal and the power supply device; [0007]the first identification unit is configured to identify whether or not the power supply device is a master data communication device; [0008]the command receiving unit is configured to receive a charging command sent by the power supply device when an identification result is that the power supply device is a master data communication device; and [0009]the charging management unit is configured to select an adjustable charging mode for charging according to the charging command. [0010]In an embodiment, the charging command received by the control unit may be one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the charging management unit may be one of: a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the standard charging command, the first charging command and the second charging command, respectively. A working current of the standard charging mode may be 500 mA, a working current in the first charging mode may be 800 mA, and a working current in the second charging mode may be 1000 mA or 1500 mA. [0011]In an embodiment, the mobile terminal further may include a first mode selection unit configured to select a corresponding adjustable charging mode needed by the mobile terminal and send a corresponding charging command request to the power supply device. [0012]In an embodiment, the first interface unit may be a USB interface unit. [0013]A master data communication device is also provided in an embodiment of the disclosure, which includes a second interface unit and a command generation unit, wherein [0014]the second interface unit is configured to be connected with a mobile terminal to transfer interaction information between the master data communication device and the mobile terminal; and [0015]the command generation unit is configured to generate a charging command and send the generated charging command to the mobile terminal via the second interface unit. [0016]In an embodiment, the master data communication device further may include a second identification unit configured to identify whether or not the mobile terminal supports adjustable charging modes. [0017]In an embodiment, the command generation unit may be configured to automatically generate a charging command corresponding to a maximum working current available in the adjustable charging modes supported by the mobile terminal. [0018]In an embodiment, the master data communication device further may include a second mode selection unit configured to select an adjustable charging mode needed by the mobile terminal, and correspondingly, the command generation unit is configured to generate a corresponding charging command according to the adjustable charging mode selected by the second mode selection unit; or the command generation unit generates a corresponding charging command based on a charging command request received from the mobile terminal. [0019]A mobile terminal charging system is also provided in an embodiment of the disclosure, which includes a master data communication device and a mobile terminal, wherein [0020]the master data communication device is connected with the mobile terminal; [0021]the master data communication device is configured to send a charging command to the mobile terminal; and [0022]the mobile terminal is configured to receive the charging command sent by the master data communication device and select an adjustable charging mode corresponding to the charging command so as to be charged. [0023]In an embodiment, the master data communication device may be also configured to determine whether or not the mobile terminal supports adjustable charging modes. [0024]In an embodiment, the charging command sent by the master data communication device may be one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal may be one of a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the standard charging command, the first charging command and the second charging command, respectively. A working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA. [0025]In an embodiment, the master data communication device may send a corresponding charging command according to a charging command request corresponding to the adjustable charging mode selected by the mobile terminal, or may send a corresponding charging command according to an adjustable charging mode selected by the master data communication device for the mobile terminal, or may automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and sends the generated charging command. [0026]A mobile terminal charging method is also provided in an embodiment of the disclosure, which includes that: [0027]a mobile terminal is connected with a master data communication device; [0028]the master data communication device sends a corresponding charging command to the mobile terminal; and [0029]the mobile terminal selects a corresponding charging mode according to the charging command so as to be charged. [0030]In an embodiment, before the master data communication device sends a corresponding charging command to the mobile terminal, the method further may include that: [0031]the master data communication device determines whether or not the mobile terminal supports adjustable charging modes and, after determining that the mobile terminal supports adjustable charging modes, sends the corresponding charging command to the mobile terminal. [0032]In an embodiment, the process that the master data communication device sends a corresponding charging command to the mobile terminal may include that: [0033]the mobile terminal selects a needed adjustable charging mode and sends a charging command request corresponding to the selected adjustable charging mode to the master data communication device; and [0034]the master data communication device sends a corresponding charging command to the mobile terminal according to the charging command request. [0035]In an embodiment, the process that the master data communication device sends a corresponding charging command to the mobile terminal may include that: the master data communication device selects an adjustable charging mode for the mobile terminal, generates a corresponding charging command according to the adjustable charging mode selected and sends the corresponding charging command generated to the mobile terminal; or the master data communication device automatically generates a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and sends the generated charging command. [0036]In an embodiment, the charging command sent by the master data communication device may be one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal may be one of a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the standard charging command, the first charging command and the second charging command, respectively. A working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA. [0037]Embodiments of the disclosure achieve the following beneficial effect: by means of the mobile terminal, the master data communication device and the mobile terminal charging system and method provided herein, a mobile data terminal can determine whether or not a power supply device is a master data communication device and if so, determine an appropriate charging mode for charging itself. In this way, the mobile terminal can not only select a corresponding charging mode for charging itself from a plurality of adjustable charging modes but also select the most appropriate charging mode for charging itself, thus improving the charging efficiency BRIEF DESCRIPTION OF THE DRAWINGS [0038]FIG. 1 is a schematic diagram illustrating the structure of a mobile terminal according to an embodiment of the disclosure; [0039]FIG. 2 is a schematic diagram illustrating the structure of a master data communication device according to an embodiment of the disclosure; [0040]FIG. 3 is a schematic diagram illustrating the structure of a mobile terminal charging system according to an embodiment of the disclosure; and [0041]FIG. 4 is a flowchart illustrating of a mobile terminal charging method according to an embodiment of the disclosure. DETAILED DESCRIPTION [0042]In embodiments of the disclosure, a mobile terminal can make a selection from a plurality of charging modes supported by a master device to achieve a user-desired or optimal charging mode, and a user-desired or optimal charging efficiency. Technical solution and the advantages of the disclosure will become clearer from the detailed description of the disclosure when taken in conjunction with accompanying drawings. [0043]A mobile terminal is provided in an embodiment of the disclosure, which, as shown in FIG. 1, includes: a first interface unit 101, a first identification unit 102, a command receiving unit 104 and a charging management unit 105, wherein [0044]the first interface unit 101 is connected with a power supply device to transfer the interaction information between the mobile terminal and the power supply device; [0045]the mobile terminal, which may be connected with the power supply device via a plurality of interfaces, is preferably connected with the power supply device via a USB interface. [0046]The first identification unit 102 is configured to identify whether or not the power supply device is a master data communication device; [0047]Although there are a variety of kinds of power supply devices, such as AC/DC adaptors, standard master devices, portable power sources and master data communication devices, the power supply device here is preferably a master data communication device as the master data communication device is capable of providing a plurality of charging modes for a mobile terminal while performing data communication with the mobile terminal, and also capable of providing both a standard current charging mode and a large current (e.g. 1000 mA) charging mode for the mobile terminal. [0048]The command receiving unit 104 is configured to start a master device charging mode when the identification result is that the power supply device is a master data communication device and to receive a charging command sent by the power supply device; [0049]when the first identification unit 102 identifies that the power supply device is a master data communication device, the command receiving unit 104 controls the mobile terminal to enter a charging mode and receives charging commands sent by a plurality of power supply devices. [0050]The charging management unit 105 is configured to select a corresponding adjustable charging mode for charging according to the charging command received by the command receiving unit 104. [0051]In the embodiment, a variety of kinds of charging commands may be sent by the power supply device, including one of a standard charging command, a first charging command and a second charging command; and there are also a plurality of adjustable charging modes corresponding to the mobile terminal, including a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. Specifically, the standard charging command is corresponding to the standard charging mode, the first charging command is corresponding to the first charging mode, and the second charging command is corresponding to the second charging mode. In an embodiment, the working current in the standard charging mode, which is the working current commonly used by the power supply device, is preferably 500 mA; the working current in the first charging mode, which is a relatively large working current that the power supply device can supply, is usually 800 mA; the working current in the second charging mode, which is the maximum working current that the power supply device can supply, is preferably 1000 mA or 1500 mA; and the working currents mentioned herein cover any working current that can be provided by the power supply device and supported by the mobile terminal, but not limited to a specific working current limited in the disclosure. [0052]In the embodiment, the mobile terminal further includes a first mode selection unit which is mainly configured to select an adjustable charging mode needed by the mobile terminal and send a corresponding charging command request to the power supply device; after the first identification unit 102 identifies that the power supply device is a master data communication device, the user may select a needed adjustable charging mode through the first mode selection unit, generates a corresponding charging command request and sends the generated charging command to the power supply device, the power supply device generates, according to the charging command request, a charging command corresponding to the charging mode and sends the generated charging command to the command receiving unit 104, and the charging management unit 105 starts a corresponding charging mode. [0053]In the embodiment, as the first interface unit 101 is a USB interface unit, the identification of the power supply device as a master data communication device by the first identification unit 104 mainly includes the following identification steps of: [0054]determining whether or not the power supply device is an AC/DC adaptor with a USB interface or a USB master device by detecting whether or not the D+ signal pin and the D− signal pin of the USB are short-circuited; if the D+ signal pin and the D− signal pin of the USB are short-circuited, determining that the power supply device is an AC/DC adaptor with a USB interface, otherwise, determining that the power supply device is a USB master device; and [0055]sequentially determining whether or not the power supply device is a portable power source with a USB interface or a master data communication device by detecting whether or not there are signals at the D+ signal pin and the D− signal pin of the USB, determining that the power supply device is a master data communication device if there are signals at the D+ signal pin and the D− signal pin of the USB, otherwise, determining that the power supply device is a portable power source with a USB interface. [0056]A master data communication device is also provided in an embodiment of the disclosure, which, as shown in FIG. 2, includes: a second interface unit 201, a second identification unit 202 and a command generation unit 204, wherein [0057]the second interface unit 201 is connected with a mobile terminal to transfer the interaction information between the master data communication device and the mobile terminal; [0058]the second identification unit 202 is configured to identify whether or not the mobile terminal supports adjustable charging modes; after being connected with the mobile terminal, the second identification unit needs to identify the mobile terminal so as to determine whether or not the mobile terminal supports adjustable charging modes; [0059]the specific determination process is as follows: the second identification unit sends a test command and analyzes the result information fed back to determine whether or not the mobile terminal supports adjustable charging modes; or the second identification unit 202 directly sends a charging command generation request to the command generation unit 204, and the command generation unit 204 sends a first or second charging command to the mobile terminal; if the result information fed back is an acknowledgement, which indicates that the mobile terminal supports adjustable charging modes, then the mobile terminal starts a charging mode corresponding to the charging command so as to be charged; and if the result information fed back is a fault, which indicates that the mobile terminal supports no adjustable charging mode, then the command generation unit 204 sends a standard charging command to the mobile terminal; and [0060]the command generation unit 204 is configured to generate a charging command and send the generated charging command to the mobile terminal via the second interface unit 201; [0061]the command generation unit 204 is mainly configured to generate a corresponding charging command and send the generated charging command to the mobile terminal to start a corresponding charging mode to charge the mobile terminal. [0062]In the embodiment, the master data communication device further may include a second mode selection unit 203 configured to select an adjustable charging mode needed by the mobile terminal; in consideration of the situation that a mobile terminal is out of power and cannot be launched, which happens sometimes, and the situation that a user is used to performing a charging operation at the side of the master data communication device, the user may select an adjustable charging mode supported by the terminal on the interface of the master data communication device through the second mode selection unit 203, and the command generation unit 204 generates a corresponding charging command according to the adjustable charging mode selected by the second mode selection unit 203. In the embodiment, the command generation unit 204 may further generate a corresponding charging command based on a charging command request sent by the mobile terminal. If no adjustable charging mode is selected by the user from the mobile terminal or from the master data communication device, then the command generation unit 204 may automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and send the generated charging command to the mobile terminal. [0063]A mobile terminal charging system is also provided in an embodiment of the disclosure, which, as shown in FIG. 3, includes a master data communication device and a mobile terminal, wherein [0064]the master data communication device is connected with the mobile terminal and configured to determine whether or not the mobile terminal supports adjustable charging modes and send a charging command to the mobile terminal; and the mobile terminal is configured to receive the charging command sent by the master data communication device and select an adjustable charging mode corresponding to the charging command so as to be charged. [0065]In the embodiment, the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal includes a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. Specifically, the standard charging command is corresponding to the standard charging mode, the first charging command is corresponding to the first charging mode, and the second charging command is corresponding to the second charging mode. In an embodiment, the working current in the standard charging mode, which is the working current commonly used by the power supply device, is preferably 500 mA; the working current in the first charging mode, which is a relatively large working current the power supply device can supply, is usually 800 mA; the working current in the second charging mode, which is the maximum working current the power supply device can supply, is preferably 1000 mA or 1500 mA; and the working currents mentioned herein cover any working current that can be provided by the power supply device and supported by the mobile terminal, but not limited to a specific working current limited in the disclosure. [0066]In the embodiment, the master data communication device may send a charging command according to a charging command request corresponding to the adjustable charging mode selected by the mobile terminal, or send a corresponding charging command according to an adjustable charging mode selected by the master data communication device for the mobile terminal, or automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and send the generated charging command. [0067]A mobile terminal charging method is also provided in an embodiment of the disclosure, which specifically includes the following steps that: [0068]a mobile terminal is connected with a master data communication device; [0069]the master data communication device sends a corresponding charging command to the mobile terminal; and [0070]the mobile terminal selects a corresponding charging mode according to the charging command so as to be charged. [0071]In the embodiment, the process that the master data communication device sends a corresponding charging command to the mobile terminal specifically includes that: [0072]the mobile terminal selects a needed adjustable charging mode and sends a charging command request corresponding to the selected adjustable charging mode to the master data communication device; and [0073]the master data communication device sends a corresponding charging command to the mobile terminal according to the charging command request. [0074]In the embodiment, the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal includes a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. [0075]In the embodiment, the master data communication device may directly generate a first or second charging command and send the generated first or second charging command to the mobile terminal; if the result information fed back is acknowledgement, which indicates that the mobile terminal supports adjustable charging modes, then the mobile terminal starts a charging mode corresponding to the charging command so as to be charged; and if the result information fed back is fault, which indicates that the mobile terminal supports no adjustable charging mode, then the master data communication device sends a standard charging command to the mobile terminal. [0076]Alternatively, in the embodiment, before the master data communication device sends a corresponding charging command to the mobile terminal, the method further may include that: the master data communication device determines whether or not the mobile terminal supports adjustable charging modes. As in the embodiment, besides by directly sending a charging command to the mobile terminal, the master data communication device may also determine whether or not the mobile terminal supports adjustable charging modes by sending a test command to the mobile terminal and analyzing the result information fed back. [0077]Alternatively, in the embodiment, the process that the master data communication device sends a charging command to the mobile terminal may be as follows: the master data communication device selects an adjustable charging mode for the mobile terminal, generates a corresponding charging command according to the adjustable charging mode selected and sends the charging command generated to the mobile terminal; or the master data communication device automatically generates a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and sends the generated charging command. [0078]Refer to FIG. 4, the mobile terminal charging method disclosed herein is described in detail below based on a specific embodiment: [0079]Step 402: a mobile terminal is connected with a master data communication device, and then Step 404 is executed; [0080]Step 404: the master data communication device determines whether or not the mobile terminal supports adjustable charging modes, if so, Step 410 is executed, otherwise, Step 406 is executed; [0081]in this step, the master data communication device sends a test command to determine whether or not the mobile terminal supports adjustable charging modes; [0082]Step 406: the master data communication device sends a standard charging command, and then Step 408 is executed; [0083]Step 408: the mobile terminal starts a standard charging mode for charging itself; [0084]Step 410: the mobile terminal selects an adjustable charging mode and then Step 412 is executed; [0085]in this step, in consideration of the situation that a mobile terminal may go out of power and cannot be launched, which happens sometimes, and the situation that a user is used to performing a charging operation at the side of the master data communication device, the user may select an adjustable charging mode supported by the terminal on the interface of the master data communication device through the second mode selection unit of the master data communication device, and the command generation unit of the master data communication device generates a corresponding charging command according to the adjustable charging mode selected by the second mode selection unit. In the embodiment, the command generation unit may further generate a corresponding charging command based on a charging command request received from the mobile terminal. If no adjustable charging mode is selected by the user from the mobile terminal or from the master data communication device, then the command generation unit may automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and send the generated charging command to the mobile terminal; [0086]Step 412: a corresponding charging command request is generated according to the selected adjustable charging mode and sent to the master data communication device, and then Step 414 is executed; [0087]Step 414: the master data communication device generates a corresponding charging command according to the charging command request and sends the generated charging command to the mobile terminal, and then Step 416 is executed; and [0088]Step 416: the mobile terminal selects and starts a corresponding adjustable charging mode according to the received charging command so as to be charged. [0089]In Step 414 and Step 416, the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal includes a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. In an embodiment, the working current in the standard charging mode, which is the working current commonly used by the power supply device, is preferably 500 mA; the working current in the first charging mode, which is a relatively large working current the power supply device can supply, is usually 800 mA; the working current in the second charging mode, which is the maximum working current the power supply device can supply, is preferably 1000 mA or 1500 mA; and the working currents mentioned herein cover any working current that can be provided by the power supply device and supported by the mobile terminal, but not limited to a specific working current limited in the disclosure. [0090]The mentioned above is merely detailed description of specific implementation mode of the disclosure but is not to be construed as limiting the specific implementation of the disclosure. It should be appreciated by those ordinary skills in the art that a variety of simple derivations and substitutes can be devised without departing from the spirit and scope of the disclosure, and all the derivations and substitutes should fall within the scope of the disclosure.(String), 技术领域 [0001] 本发明涉及电子通信领域,尤其涉及一种移动终端、数据通信主设备及移动终端计费系统及方法。 背景 [0002] 目前,手机、相机、PAD等移动终端设备大多采用USB接口作为充电器的电源接口,而且标准USB接口随手可得,使用起来非常方便。 能够为这些移动终端设备充电的主控设备。 但由于标准USB主控设备提供的电流较小,例如USB2.0接口的标准USB主控设备提供的电流为500mA,USB1.0接口的标准USB主控设备提供的电流为500mA。 1接口为250毫安,使用标准USB主控设备给移动终端充电时间较长,导致用户体验不佳。 现有的一些带有USB接口的便携式电源能够提供比标准USB主设备更大的充电电流,例如800mA、1A甚至1.5A的电流。 对于现有的具有大电流充电能力的USB主控设备,作为USB从属设备,即移动终端,无法根据此类USB主控设备的供电能力自动改变充电电流的大小, 充电效率低。 对于消费者而言,希望移动终端在提供数据通信服务的同时,能够根据需要选择充电电流,并且能够选择多种充电模式,以方便、快速地为移动终端充电。 概括 [0003] 本发明所要解决的主要技术问题是提供一种移动终端、数据通信主设备及移动终端充电系统及方法,避免因移动终端无法实时选择而导致的充电效率低下 与主控设备匹配的充电方式,为自身充电。 [0004] 为解决上述技术问题,本发明的技术方案如下: [0005] 一种移动终端,包括第一接口单元、第一识别单元、命令接收单元和充电管理单元,其中 [0006] 第一接口单元,用于与供电设备连接,以传递移动终端与供电设备之间的交互信息; [0007] 第一识别单元用于识别供电设备是否为主数据通信设备; [0008] 命令接收单元,用于当识别结果为供电设备为主数据通信设备时,接收供电设备发送的充电命令; 和 [0009] 充电管理单元用于根据充电命令选择可调的充电模式进行充电。 [0010] 在一个实施例中,控制单元接收到的充电命令可以是标准充电命令、第一充电命令和第二充电命令中的一种; 充电管理单元选择的可调充电模式可以为以下之一:标准充电模式、第一充电模式和第二充电模式,分别对应于标准充电命令、第一充电命令和第二充电命令, 分别。 标准充电模式的工作电流可以为500mA,第一充电模式的工作电流可以为800mA,第二充电模式的工作电流可以为1000mA或1500mA。 [0011] 在一个实施例中,移动终端还可以包括第一模式选择单元,用于选择移动终端需要的对应的可调充电模式,并向供电设备发送对应的充电命令请求。 [0012] 在一个实施例中,第一接口单元可以是USB接口单元。 [0013] 本发明实施例还提供一种主控数据通信装置,包括第二接口单元和命令生成单元,其中, [0014]第二接口单元,用于与移动终端连接,传递数据通信主设备与移动终端之间的交互信息; 和 [0015] 命令生成单元,用于生成充电命令,并将生成的充电命令通过第二接口单元发送给移动终端。 [0016] 在一个实施例中,数据通信主设备还可以包括第二识别单元,用于识别移动终端是否支持可调充电模式。 [0017] 在一个实施例中,命令生成单元可以用于自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令。 [0018] 在一个实施例中,数据通信主设备还可以包括:第二模式选择单元,用于选择移动终端需要的可调充电模式;相应的,命令生成单元,用于根据可调充电模式生成相应的充电命令。 第二模式选择单元选择的模式; 或者,命令生成单元根据从移动终端接收到的充电命令请求生成相应的充电命令。 [0019] 本发明实施例还提供了一种移动终端计费系统,包括数据通信主设备和移动终端,其中, [0020] 主数据通信设备与移动终端连接; [0021] 数据通信主设备,用于向移动终端发送充电命令; 和 [0022] 移动终端,用于接收数据通信主设备发送的充电命令,选择与充电命令对应的可调充电模式进行充电。 [0023] 在一个实施例中,主数据通信设备还可以用于判断移动终端是否支持可调充电模式。 [0024] 在一个实施例中,主数据通信设备发送的充电命令可以是标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式可以为标准充电模式、第一充电模式和第二充电模式中的一种,分别对应于标准充电命令、第一充电命令和第二充电命令。 标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。 [0025] 在一个实施例中,主数据通信设备可以根据移动终端选择的可调充电模式对应的充电命令请求发送相应的充电命令,也可以根据主数据通信设备选择的可调充电模式发送相应的充电命令。 用于移动终端的数据通信装置,或者可以在移动终端支持的可调充电模式中自动生成与可用的最大工作电流对应的充电命令并发送生成的充电命令。 [0026] 本发明实施例还提供了一种移动终端的充电方法,包括: [0027] 移动终端连接主数​​据通信设备; [0028] 数据通信主设备向移动终端发送相应的充电命令; 和 [0029] 移动终端根据充电指令选择相应的充电模式进行充电。 [0030] 在一个实施例中,在主数据通信设备向移动终端发送相应的充电命令之前,该方法还可以包括: [0031]数据通信主设备判断移动终端是否支持可调充电模式,在判断移动终端支持可调充电模式后,向移动终端发送相应的充电命令。 [0032] 在一个实施例中,主数据通信设备向移动终端发送相应的充电命令的过程可以包括: [0033] 移动终端选择需要的可调充电模式,并向数据通信主设备发送与选择的可调充电模式对应的充电命令请求; 和 [0034] 数据通信主设备根据充电命令请求向移动终端发送相应的充电命令。 [0035] 在一个实施例中,数据通信主设备向移动终端发送相应的充电命令的过程可以包括:数据通信主设备为移动终端选择可调充电模式,根据可调充电生成相应的充电命令。 选择模式并将生成的相应充电命令发送给移动终端; 或者,主数据通信设备在移动终端支持的可调充电模式下自动生成最大可用工作电流对应的充电指令,并发送生成的充电指令。 [0036] 在一个实施例中,主数据通信设备发送的充电命令可以是标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式可以为标准充电模式、第一充电模式和第二充电模式中的一种,分别对应于标准充电命令、第一充电命令和第二充电命令。 标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。 [0037] 本发明实施例的有益效果是:通过本发明提供的移动终端、数据通信主设备及移动终端充电系统及方法,移动数据终端可以判断供电设备是否为数据主设备。 通信设备,如果是,则确定适当的充电模式来为自身充电。 这样,移动终端不仅可以从多种可调节的充电模式中选择相应的充电模式为自己充电,还可以选择最合适的充电模式为自己充电,提高了充电效率。 附图的简要说明 [0038] 图1是根据本发明一个实施例的移动终端的结构示意图; [0039] 图2为根据本发明一实施例的主数据通信装置的结构示意图。 [0040] 图3是根据本发明实施例的移动终端计费系统的结构示意图。 和 [0041] 图4为根据本发明一实施例的移动终端充电方法的流程图。 详细说明 [0042] 在本发明实施例中,移动终端可以从主设备支持的多种充电模式中进行选择,以实现用户期望或最优的充电模式,以及用户期望或最优的充电效率。 通过结合附图对本发明的详细描述,本发明的技术方案和优点将会更加清楚。 [0043] 本发明实施例提供一种移动终端,如图1所示,包括: 第一接口单元 101 , 第一识别单元 102 , 一个指令接收单元 104 和充电管理单元 105 , 其中 [0044] 第一接口单元 101与供电设备连接,传递移动终端与供电设备的交互信息; [0045] 移动终端与供电设备可以通过多种接口连接,优选地通过USB接口与供电设备连接。 [0046] 第一标识单元 102 用于识别供电设备是否为主数据通信设备; [0047] 虽然供电装置种类繁多,例如AC/DC适配器、标准主控装置、可携式电源及主控数据通讯装置,但此处的供电装置较佳为主控数据通讯装置,作为主控数据通讯装置 能够在与移动终端进行数据通信的同时为移动终端提供多种充电模式,也能够为移动终端提供标准电流充电模式和大电流(如1000mA)充电模式。 [0048] 指令接收单元 104 用于当识别结果为供电设备为主数据通信设备时,启动主设备充电模式,并接收供电设备发送的充电命令; [0049] 当第一个标识单元 102 识别供电设备为主数据通信设备,命令接收单元 104 控制移动终端进入充电模式,并接收多个供电设备发送的充电指令。 [0050] 充电管理单元 105 用于根据命令接收单元接收到的充电命令选择相应的可调充电模式进行充电 104 . [0051] 在本实施例中,供电设备可以发送多种充电指令,包括标准充电指令、第一充电指令和第二充电指令中的一种; 移动终端对应的充电模式也有多种可调,包括标准充电模式、第一充电模式和第二充电模式,分别对应上述充电指令。 具体地,标准充电指令对应标准充电模式,第一充电指令对应第一充电模式,第二充电指令对应第二充电模式。 在一个实施例中,标准充电模式下的工作电流,即供电设备常用的工作电流,优选为500mA; 第一充电模式下的工作电流,是供电设备能够提供的较大的工作电流,通常为800mA。 第二充电模式下的工作电流,即供电装置所能提供的最大工作电流,优选为1000mA或1500mA。 此处所说的工作电流涵盖了供电装置能够提供的、移动终端支持的任何工作电流,而不限于本发明所限定的具体工作电流。 [0052] 在本实施例中,移动终端还包括第一模式选择单元,主要用于选择移动终端需要的可调充电模式,并向供电设备发送相应的充电命令请求。 在第一个识别单元之后 102 识别供电设备为主数据通信设备,用户可以通过第一模式选择单元选择需要的可调充电模式,生成相应的充电命令请求,并将生成的充电命令发送给供电设备,供电设备 设备根据充电命令请求生成与充电模式对应的充电命令,并将生成的充电命令发送给命令接收单元 104 , 以及充电管理单元 105 启动相应的充电模式。 [0053] 本实施例中,作为第一接口单元 101为USB接口单元,第一识别单元识别供电设备为主数据通信设备 104 主要包括以下识别步骤: [0054] 通过检测USB的D+信号脚和D-信号脚是否短路来判断供电设备是否为USB接口的AC/DC适配器或USB主控设备; 若USB的D+信号脚与D-信号脚短路,则判断供电设备为USB接口的AC/DC适配器,否则判断供电设备为USB主控设备; 和 [0055] 通过检测USB的D+信号管脚和D-信号管脚是否有信号,依次判断供电设备是否为USB接口的便携式电源或数据通信主设备,确定 若USB的D+信号脚和D-信号脚均有信号,则供电设备为主数据通信设备,否则,确定供电设备为USB接口的便携式电源。 [0056] 本发明实施例还提供一种主数据通信装置,如图2所示,包括: 第二接口单元 201 , 第二识别单元 202 和一个命令生成单元 204 , 其中 [0057] 第二接口单元 201 与移动终端连接,传递数据通信主设备与移动终端之间的交互信息; [0058] 第二识别单元 202 用于识别移动终端是否支持可调充电模式; 第二识别单元在与移动终端连接后,需要对移动终端进行识别,以判断移动终端是否支持可调充电模式。 [0059] 具体判断过程为:第二识别单元发送测试命令,分析反馈的结果信息,判断移动终端是否支持可调充电模式。 或第二识别单元 202 直接向命令生成单元发送充电命令生成请求 204 , 和命令生成单元 204 向移动终端发送第一或第二充电命令; 若反馈的结果信息为确认,表明移动终端支持可调充电模式,则移动终端启动与充电命令对应的充电模式进行充电。 如果反馈的结果信息为错误,表明移动终端不支持可调充电模式,则命令生成单元 204 向移动终端发送标准充电命令; 和 [0060] 命令生成单元 204 用于生成充电命令,并将生成的充电命令通过第二接口单元发送给移动终端 201 ; [0061] 命令生成单元 204 主要用于生成相应的充电命令,并将生成的充电命令发送给移动终端,以启动相应的充电模式对移动终端进行充电。 [0062] 在本实施例中,主数据通信装置还可以包括:第二模式选择单元 203 用于选择移动终端需要的可调充电模式; 考虑到移动终端有时会出现没电无法启动的情况,以及用户习惯在主数据通信设备侧进行充电操作的情况,用户可以选择 终端通过第二模式选择单元在主数据通信设备接口上支持的充电模式可调 203 , 和命令生成单元 204 根据第二模式选择单元选择的可调充电模式产生相应的充电命令 203 . 本实施例中,命令生成单元 204还可以根据移动终端发送的充电命令请求生成相应的充电命令。 如果用户没有从移动终端或主数据通信设备选择可调充电模式,则命令生成单元 204 可以在移动终端支持的可调充电模式中自动生成最大可用工作电流对应的充电指令,并将生成的充电指令发送给移动终端。 [0063] 本发明实施例还提供了一种移动终端计费系统,如图3所示,包括数据通信主设备和移动终端,其中, [0064] 数据通信主设备与移动终端连接,用于判断移动终端是否支持可调充电模式,并向移动终端发送充电命令; 移动终端用于接收数据通信主设备发送的充电指令,选择与充电指令对应的可调充电模式进行充电。 [0065] 在本实施例中,主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式包括标准充电模式、第一充电模式和第二充电模式,分别对应于上述充电指令。 具体地,标准充电指令对应标准充电模式,第一充电指令对应第一充电模式,第二充电指令对应第二充电模式。 在一个实施例中,标准充电模式下的工作电流,即供电设备常用的工作电流,优选为500mA; 第一充电模式下的工作电流,是供电设备能够提供的较大工作电流,通常为800mA。 第二充电模式下的工作电流,即供电设备能够提供的最大工作电流,优选为1000mA或1500mA。 此处所说的工作电流涵盖了供电装置能够提供的、移动终端支持的任何工作电流,而不限于本发明所限定的具体工作电流。 [0066] 本实施例中,主数据通信设备可以根据移动终端选择的可调充电模式对应的充电命令请求发送充电命令,或者根据主数据通信选择的可调充电模式发送相应的充电命令。 设备为移动终端,或者在移动终端支持的可调充电模式中自动生成对应于最大可用工作电流的充电命令并发送生成的充电命令。 [0067] 本发明实施例还提供了一种移动终端的充电方法,具体包括以下步骤: [0068] 移动终端连接主数​​据通信设备; [0069] 数据通信主设备向移动终端发送相应的充电命令; 和 [0070] 移动终端根据充电指令选择相应的充电模式进行充电。 [0071] 在本实施例中,主数据通信设备向移动终端发送相应的充电命令的过程具体包括: [0072] 移动终端选择需要的可调充电模式,并向数据通信主设备发送与选择的可调充电模式对应的充电命令请求; 和 [0073] 数据通信主设备根据充电命令请求向移动终端发送相应的充电命令。 [0074]在本实施例中,主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式包括标准充电模式、第一充电模式和第二充电模式,分别对应于上述充电指令。 [0075] 本实施例中,主数据通信设备可以直接生成第一或第二充电命令,并将生成的第一或第二充电命令发送给移动终端。 若反馈的结果信息为确认,表明移动终端支持可调充电模式,则移动终端启动与充电命令对应的充电模式进行充电。 如果反馈的结果信息为fault,表明移动终端不支持可调充电模式,则数据通信主设备向移动终端发送标准充电命令。 [0076] 可选地,在本实施例中,在主数据通信设备向移动终端发送相应的充电命令之前,该方法还可以包括: 主数据通信设备判断移动终端是否支持可调充电模式。 如本实施例,数据通信主设备除了直接向移动终端发送充电指令外,还可以通过向移动终端发送测试指令,分析反馈的结果信息,判断移动终端是否支持可调充电模式。 背部。 [0077] 可选地,在本实施例中,主数据通信设备向移动终端发送充电命令的过程可以为: 主数据通信设备为移动终端选择可调节的充电模式,根据充电模式生成相应的充电命令。 选择可调充电模式并将生成的充电命令发送给移动终端; 或者,主数据通信设备在移动终端支持的可调充电模式下自动生成最大可用工作电流对应的充电指令,并发送生成的充电指令。 [0078] 参见图4,下面结合一个具体实施例对本发明公开的移动终端充电方法进行详细说明: [0079] 步 402 :移动终端与主数据通信设备连接,然后步骤 404 被执行; [0080] 步 404 :主数据通信设备判断移动终端是否支持可调充电模式,若支持,步骤 410 被执行,否则,Step 406 被执行; [0081] 本步骤中,数据通信主设备发送测试命令,判断移动终端是否支持可调充电模式。 [0082] 步 406 :主数据通信设备发送标准充电命令,然后Step 408 被执行; [0083] 步 408 :移动终端启动标准充电模式为自身充电; [0084] 步 410 :移动端选择一种可调节的充电方式,然后Step 412 被执行; [0085]本步骤中,考虑到移动终端有时会出现没电无法启动的情况,以及用户习惯在主数据通信设备侧进行充电操作的情况, 用户可以通过主数据通信设备的第二模式选择单元在主数据通信设备的界面上选择终端支持的可调充电模式,主数据通信设备的命令生成单元生成相应的充电命令 根据第二模式选择单元选择的可调充电模式。 在本实施例中,命令生成单元还可以根据从移动终端接收到的充电命令请求生成相应的充电命令。 如果用户未从移动终端或数据通信主设备选择可调充电模式,则命令生成单元可自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令 将生成的充电命令发送给移动终端; [0086] 步 412 :根据选择的可调充电模式生成相应的充电命令请求发送给主数据通信设备,然后步骤 414 被执行; [0087] 步 414 :主数据通信设备根据计费命令请求生成相应的计费命令,并将生成的计费命令发送给移动终端,然后步骤 416 被执行; 和 [0088] 步 416 :移动终端根据接收到的充电指令选择并启动相应的可调充电模式进行充电。 [0089] 在步骤 414 和步骤 416 ,主数据通信装置发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一个; 移动终端选择的可调充电模式包括标准充电模式、第一充电模式和第二充电模式,分别对应于上述充电命令。 在一个实施例中,标准充电模式下的工作电流,即供电设备常用的工作电流,优选为500mA; 第一充电模式下的工作电流,是供电设备能够提供的较大工作电流,通常为800mA。 第二充电模式下的工作电流,即供电设备能够提供的最大工作电流,优选为1000mA或1500mA。 此处所说的工作电流涵盖了供电装置能够提供的、移动终端支持的任何工作电流,而不限于本发明所限定的具体工作电流。 [0090] 以上所述仅为本发明的具体实施方式的详细说明,并不构成对本发明具体实施方式的限定。 本领域的普通技术人员应当理解,在不脱离本公开的精神和范围的情况下,可以设计出各种简单的推导和替代,并且所有的推导和替代都应落入本公开的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.432 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.432 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102868820A(String), EP2892214A2(String), EP2892214A4(String), EP2892214B1(String), US20150256018A1(String), US9899854B2(String), WO2013178191A2(String), WO2013178191A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102868820A(String), EP2892214A2(String), EP2892214A4(String), EP2892214B1(String), US20150256018A1(String), US9899854B2(String), WO2013178191A2(String), WO2013178191A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9899854B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102868820A(String), EP2892214A2(String), EP2892214A4(String), EP2892214B1(String), US20150256018A1(String), US9899854B2(String), WO2013178191A2(String), WO2013178191A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), CN102868820A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), EP2892214A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), EP2892214A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), EP2892214B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), US20150256018A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), US9899854B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), WO2013178191A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270663(Integer), WO2013178191A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9899854B2(String), US9899854B2(String), 1519056000(Integer), 270663(Integer), 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184981(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184981(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184981(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184981(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7668136B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: System, network, mobile terminal, computer program product and method for cross-paging a mobile terminal via a data burst message(String), 用于通过数据突发消息对移动终端进行跨页寻呼的系统、网络、移动终端、计算机程序产品和方法(String), US7668136B2(String), Systems and methods are provided to permit a network, such as a data only network, with which a mobile terminal is not currently communicating to notify the mobile terminal that the network desires to establish communication with the mobile terminal, even in instances in which the mobile terminal is actively communicating via another network, such as a voice and data network and has stopped monitoring for paging messages. The mobile terminal can then end communications with the network with which it has been previously communicating and commence communications with the other network that has transmitted the paging message. For example, a mobile terminal may terminate voice communications via a voice and data network in order to receive a Multimedia Message Service message via a data only network upon receiving notification that the data only network desires to establish a communications session with the mobile terminal.(String), 提供系统和方法以允许移动终端当前未与之通信的网络(例如纯数据网络)通知移动终端该网络希望与移动终端建立通信,即使在移动终端未与之通信的情况下也是如此。 终端正在通过另一个网络(例如语音和数据网络)进行主动通信,并且已停止监听寻呼消息。 移动终端然后可以结束与其先前已经与之通信的网络的通信并且开始与已经发送寻呼消息的其他网络的通信。 例如,移动终端可以终止经由语音和数据网络的语音通信以便在接收到仅数据网络期望与移动终端建立通信会话的通知时经由仅数据网络接收多媒体消息服务消息。(String), US11/353542(String), 1139846400(Integer), US7668136B2(String), 1266854400(Integer), 1266854400(Integer), 美国(String), 4(Integer), US(String), 15(Integer), 12(Integer), US20020082029A1 | US20020154627A1 | US20020187804A1 | US20040037222A1 | US20040120283A1 | US20040185879A1 | US20040218575A1 | US20050276273A1 | US20060176870A1 | US6047071A | WO2004005236A1 | WO2004045236A1(String), 31(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184982(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\95981a3e176a48a1982b9b5c11fcfff8.png(String), 184982(Integer), 95981a3e176a48a1982b9b5c11fcfff8.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System, network, mobile terminal, computer program product and method for cross-paging a mobile terminal via a data burst message(String), 用于通过数据突发消息对移动终端进行跨页寻呼的系统、网络、移动终端、计算机程序产品和方法(String), US7668136B2(String), Systems and methods are provided to permit a network, such as a data only network, with which a mobile terminal is not currently communicating to notify the mobile terminal that the network desires to establish communication with the mobile terminal, even in instances in which the mobile terminal is actively communicating via another network, such as a voice and data network and has stopped monitoring for paging messages. The mobile terminal can then end communications with the network with which it has been previously communicating and commence communications with the other network that has transmitted the paging message. For example, a mobile terminal may terminate voice communications via a voice and data network in order to receive a Multimedia Message Service message via a data only network upon receiving notification that the data only network desires to establish a communications session with the mobile terminal.(String), 提供系统和方法以允许移动终端当前未与之通信的网络(例如纯数据网络)通知移动终端该网络希望与移动终端建立通信,即使在移动终端未与之通信的情况下也是如此。 终端正在通过另一个网络(例如语音和数据网络)进行主动通信,并且已停止监听寻呼消息。 移动终端然后可以结束与其先前已经与之通信的网络的通信并且开始与已经发送寻呼消息的其他网络的通信。 例如,移动终端可以终止经由语音和数据网络的语音通信以便在接收到仅数据网络期望与移动终端建立通信会话的通知时经由仅数据网络接收多媒体消息服务消息。(String), US11/353542(String), 1139846400(Integer), US7668136B2(String), 1266854400(Integer), 1266854400(Integer), 美国(String), 2(Integer), 4(Integer), US(String), 15(Integer), 12(Integer), US20020082029A1 | US20020154627A1 | US20020187804A1 | US20040037222A1 | US20040120283A1 | US20040185879A1 | US20040218575A1 | US20050276273A1 | US20060176870A1 | US6047071A | WO2004005236A1 | WO2004045236A1(String), \20230420\95981a3e176a48a1982b9b5c11fcfff8.png(String), 31(Integer), 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 1. A network comprising an agent configured to enable communication with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot, the agent including a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the agent to perform at least:receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal, andissuing a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the series of messages including:a first message for directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 1.一个网络包括一种代理,被配置为能够与插槽中的至少一个混合移动终端和至少一个非混合移动终端进行通信,该代理包括处理器和包含计算机程序代码的存储器,该存储器和计算机程序代码被配置为,处理器,使代理至少执行:从目标网络接收寻呼指示,寻呼指示指示目标网络期望与选定的混合移动终端通信,以及向至少一个混合移动终端和至少一个非混合移动终端发布一系列消息,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示至少一个非混合移动终端停止监视时隙;和第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 2. A network according to claim 1, wherein the series of messages further comprises a third message for directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 2.根据权利要求1的网络,其中该系列消息还包括第三消息,用于指示剩余的混合移动终端停止监视时隙。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 3. A network according to claim 1, wherein the data burst message includes a predefined code indicative of the page indication.(String), 3.根据权利要求1的网络,其中数据突发消息包括指示寻呼指示的预定义代码。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 4. A network according to claim 1, wherein the selected hybrid mobile terminal is configured to switch from the network to the target network in response to the data burst message.(String), 4.根据权利要求1的网络,其中所选择的混合移动终端被配置为响应于数据突发消息从网络切换到目标网络。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 5. A network according to claim 1, wherein the processor, memory and the computer program code further cause the agent to perform receiving network and service availability information from the target network.(String), 5.根据权利要求1的网络,其中处理器、存储器和计算机程序代码进一步使代理执行从目标网络接收网络和服务可用性信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 6. A network according to claim 1, wherein the at least one hybrid mobile terminal ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 6.根据权利要求1所述的网络,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则至少一个混合移动终端停止监视时隙。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 7. An apparatus comprising a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus to perform at least:receiving a series of messages from an anchor network in communication with the apparatus while the apparatus is monitoring a slot, the apparatus being enabled to communicate with a target network, the series of messages including:a first message for directing any non-hybrid mobile terminal in communication with the anchor network to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of a page indication to the apparatus, the page indication indicating that the target network desires to communicate with the apparatus.(String), 7.仪器包括处理器和存储器,包括计算机程序代码,存储器和计算机程序代码被配置为与处理器一起使装置至少执行:当该装置正在监视时隙时,从与该装置通信的锚网络接收一系列消息,该装置能够与目标网络通信,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示与锚定网络通信的任何非混合移动终端停止监视时隙;和第二消息包括指示对装置的寻呼指示的数据突发消息,寻呼指示指示目标网络期望与装置通信。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 8. An apparatus according to claim 7, wherein the data burst message includes a predefined code indicative of the page indication.(String), 8.根据权利要求7所述的装置,其中数据突发消息包括指示寻呼指示的预定义代码。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 9. An apparatus according to claim 7, wherein the apparatus is configured to switch from the anchor network to the target network in response to the data burst message.(String), 9.根据权利要求7所述的装置,其中该装置被配置为响应于数据突发消息从锚定网络切换到目标网络。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 10. An apparatus according to claim 7, wherein the apparatus ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 10.根据权利要求7所述的装置,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则装置停止监视时隙。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 11. A method comprising:receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal in a communication network enabled to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal monitoring a slot;sending a first message of a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the first message directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; andsending a second message of the series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 11.一种方法包括:从目标网络接收寻呼指示,该寻呼指示指示目标网络希望与通信网络中的选定混合移动终端通信,该通信网络能够与至少一个混合移动终端和至少一个非混合移动终端监控进行通信插槽;向至少一个混合移动终端和至少一个非混合移动终端发送一系列消息中的第一消息,第一消息指示至少一个非混合移动终端停止监视时隙,如果预定义字段第一消息的设置为预定值;和向至少一个混合移动终端和至少一个非混合移动终端发送一系列消息中的第二消息,第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 12. A method according to claim 11, further comprising sending a third message of the series of messages, the third message directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 12.根据权利要求11所述的方法,还包括发送一系列消息中的第三条消息,第三条消息指示剩余的混合移动终端停止监视时隙。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 13. A method according to claim 11, further comprising receiving network and service availability information from the target network.(String), 13.根据权利要求11所述的方法,还包括从目标网络接收网络和服务可用性信息。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 14. A method according to claim 11, wherein sending the first message further comprises directing the at least one hybrid mobile terminal to cease to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 14.根据权利要求11所述的方法,其中发送第一消息还包括如果消息系列的第一消息的预定义字段被设置为不同于预定值的值,则指示至少一个混合移动终端停止监视时隙。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 15. A computer program product comprising at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:a first executable portion for receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal in a communication network enabled to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal monitoring a slot;a second executable portion for sending a first message of a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the first message directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda third executable portion for sending a second message of the series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 15.计算机程序产品包括至少一个计算机可读存储介质,其中存储有计算机可读程序代码部分,计算机可读程序代码部分包括:第一可执行部分,用于从目标网络接收寻呼指示,该寻呼指示指示目标网络希望与通信网络中的选定混合移动终端通信,该通信网络能够与至少一个混合移动终端和至少一个非-混合移动终端监控槽;第二可执行部分,用于向至少一个混合移动终端和至少一个非混合移动终端发送一系列消息中的第一消息,第一消息指示至少一个非混合移动终端停止监视如果第一消息的预定义字段被设置为预定值,则时隙;和第三可执行部分,用于向至少一个混合移动终端和至少一个非混合移动终端发送消息系列中的第二消息,第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息移动终端。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 16. A computer program product according to claim 15, further comprising a fourth executable portion for sending a third message of the series of messages, the third message directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 16.根据权利要求15所述的计算机程序产品,还包括第四可执行部分,用于发送消息系列中的第三消息,第三消息指示混合移动终端中的其余混合移动终端停止监视时隙。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 17. A computer program product according to claim 15, further comprising a fourth executable portion for receiving network and service availability information from the target network.(String), 17.根据权利要求15所述的计算机程序产品,还包括第四可执行部分,用于从目标网络接收网络和服务可用性信息。(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 18. A computer program product according to claim 15, wherein the second executable portion includes further instructions for directing the at least one hybrid mobile terminal to cease to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 18.根据权利要求15所述的计算机程序产品,其中第二可执行部分包括进一步的指令,用于在消息系列的第一消息的预定义字段被设置为不同于预定值的值的情况下指示至少一个混合移动终端停止监视时隙。(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 19. A system comprising:an anchor network configured to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot; anda target network configured to issue a page indication to the anchor network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal,wherein the anchor network issues a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the series of messages including:a first message for directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 19.一个系统包括:锚定网络,用于在时隙中与至少一个混合移动终端和至少一个非混合移动终端进行通信;和目标网络被配置为向锚网络发出寻呼指示,该寻呼指示指示目标网络希望与选定的混合移动终端通信,其中,锚定网络向至少一个混合移动终端和至少一个非混合移动终端下发一系列消息,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示至少一个非混合移动终端停止监视时隙;和第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 20. A system according to claim 19, wherein the series of messages further comprises a third message for directing remaining ones of the at least one hybrid mobile terminals to cease monitoring the slot.(String), 20.根据权利要求19所述的系统,其中该系列消息还包括第三消息,用于指示至少一个混合移动终端中的其余混合移动终端停止监视时隙。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 21. A system according to claim 19, wherein the at least one hybrid mobile terminal ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 21.根据权利要求19所述的系统,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则至少一个混合移动终端停止监视时隙。(String), 1(Integer), 20(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 22. A network comprising:means for receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal, the network being enabled to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot; andmeans for issuing a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the series of messages including:a first message for directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 22.一个网络包括:用于从目标网络接收寻呼指示的装置,该寻呼指示指示目标网络希望与选定的混合移动终端通信,该网络能够与至少一个混合移动终端和至少一个非混合移动终端通信插槽中的端子;和用于向至少一个混合移动终端和至少一个非混合移动终端发布一系列消息的装置,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示至少一个非混合移动终端停止监视时隙;和第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 21(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 23. A network according to claim 22, further comprising a means for issuing a third message for directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 23.根据权利要求22所述的网络,还包括用于发出第三消息以指示混合移动终端中的其余移动终端停止监视时隙的装置。(String), 1(Integer), 22(Integer), 21(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 24. A network according to claim 22, wherein the data burst message includes a predefined code indicative of the page indication.(String), 24.根据权利要求22所述的网络,其中数据突发消息包括指示寻呼指示的预定义代码。(String), 1(Integer), 23(Integer), 21(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 25. A network according to claim 22, wherein the at least one hybrid mobile terminal ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 25.根据权利要求22所述的网络,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则至少一个混合移动终端停止监视时隙。(String), 1(Integer), 24(Integer), 21(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 26. A network comprising an agent configured to enable communication with at least one hybrid mobile terminal in a slot, the agent including a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the agent to perform at least:receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal, andissuing a data burst message having a predefined code indicative of the page indication to the selected hybrid mobile terminal, wherein the data burst message is issued in sequence following a general page message, and wherein the selected hybrid mobile terminal ceases to monitor the slot if the predefined field of the general page message is set to a value other than the predetermined value.(String), 26.一个网络包括代理被配置为能够与插槽中的至少一个混合移动终端进行通信,代理包括处理器和存储器,存储器包括计算机程序代码,存储器和计算机程序代码被配置为与处理器一起使代理执行至少:从目标网络接收寻呼指示,寻呼指示指示目标网络期望与选定的混合移动终端通信,以及向所选混合移动终端发布具有指示寻呼指示的预定义代码的数据突发消息,其中数据突发消息在通用寻呼消息之后按顺序发布,并且其中所选混合移动终端停止监视时隙,如果通用寻呼消息的预定义字段被设置为不同于预定值的值。(String), 0(Integer), 25(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 27. A network according to claim 26, wherein the data burst message is issued in sequence prior to a general page message.(String), 27.根据权利要求26所述的网络,其中数据突发消息在一般寻呼消息之前按顺序发出。(String), 1(Integer), 26(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 28. A network according to claim 26, wherein in response to a predefined field of the general page message having a predetermined value, the selected hybrid mobile terminal is directed to monitor the slot for subsequent transmission of the data burst message.(String), 28.根据权利要求26所述的网络,其中响应于具有预定值的通用寻呼消息的预定义字段,选择的混合移动终端被指示监视用于数据突发消息的后续传输的时隙。(String), 1(Integer), 27(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 29. An apparatus comprising a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus to perform at least:receiving a data burst message from an anchor network, the data burst message having a predefined code indicative of a page indication to the apparatus monitoring a slot while in communication with an anchor network and configured to communicate with a target network,wherein the page indication is received by the anchor network from the target network, the page indication indicating that the target network desires to communicate with the apparatus,wherein the data burst message is issued in sequence following a general page message, andwherein the apparatus ceases to monitor the slot if the predefined field of the general page message is set to a value other than the predetermined value.(String), 29.仪器包括处理器和存储器,包括计算机程序代码,存储器和计算机程序代码被配置为与处理器一起使装置至少执行:从锚定网络接收数据突发消息,该数据突发消息具有指示寻呼指示的预定义代码,该寻呼指示在与锚定网络通信时监控时隙并被配置为与目标网络通信,其中寻呼指示由锚网络从目标网络接收,寻呼指示指示目标网络期望与装置通信,其中,数据突发消息是在一般寻呼消息之后按顺序发出的,并且其中,如果通用寻呼消息的预定义字段被设置为不同于预定值的值,则该装置停止监视时隙。(String), 0(Integer), 28(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 30. An apparatus according to claim 29, wherein the data burst message is issued in sequence prior to a general page message.(String), 30.根据权利要求29所述的装置,其中数据突发消息在一般寻呼消息之前按顺序发出。(String), 1(Integer), 29(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184982(Integer), 31. An apparatus according to claim 29, wherein in response to a predefined field of the general page message having a predetermined value, the apparatus is directed to monitor the slot for subsequent transmission of the data burst message.(String), 31.根据权利要求29所述的装置,其中响应于具有预定值的通用寻呼消息的预定义字段,该装置被指示监视用于数据突发消息的后续传输的时隙。(String), 1(Integer), 30(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184982(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application claims the benefit of U.S. Provisional Application No. 60/652,674, filed Feb. 14, 2005, the contents of which are incorporated herein in their entirety. FIELD OF THE INVENTION [0002]The present invention generally relates to systems and methods of cross-paging a mobile terminal from one network while the mobile terminal operates in another network and, more particularly, relates to systems and methods of cross-paging a mobile terminal from a network via a data burst message (DBM) in another network within which the mobile terminal is operating. BACKGROUND OF THE INVENTION [0003]A communication network operates to communicate data between two, or more, communication stations. A communication network is formed, at a minimum, of a first communication station, forming a sending station, and a second communication station, forming a receiving station. The communication stations are interconnected by way of a communication channel. And data that is to be communicated by the first communication station to the second communication station is sent to the second communication station by way of the communication channel. The data that is to be communicated is converted by the first communication station into a form to permit its communication upon the communication channel. And the second communication station operates to detect the data communicated thereto and to recover the informational content thereof. [0004]Many different types of communication networks have been developed and implemented to effectuate the communication of the data between the communication stations. And with continued advancements in communication technologies, new types of communication networks, as well as improvements to existing communication networks, have been, and continue to be, made. [0005]A radio communication network is an exemplary type of communication network. A radio communication network utilizes radio communication channels upon which to transmit the data that is to be communicated between the communication stations operable therein. Radio communication channels are defined upon radio links forming part of the electromagnetic spectrum. As a radio link is utilized upon which to define the communication channels, the need otherwise to utilize wireline connections upon which to define communication channels is obviated. Implementation of a radio communication network is generally less costly than the corresponding costs that would be required to construct a conventional, wireline communication network. And a radio communication network can be implemented to form a mobile communication network. [0006]A cellular communication network, exemplary of a radio communication network, has been widely implemented and has achieved wide levels of usage. A cellular communication network provides for radio communications with mobile terminals. The mobile terminals permit telephonic communication to be effectuated therethrough. A cellular communication network includes a network part that is installed throughout a geographical area and with which the mobile terminals communicate by way of radio channels. Base transceiver stations, forming portions of the network part of the communication network, are installed at spaced apart locations throughout the geographical area that is to be covered by the communication network. Each of the base transceiver stations defines a cell encompassing a portion of the geographical area. When a mobile terminal is within the cell defined by a base transceiver station, communications are generally effectuable with the base transceiver station that defines the cell. [0007]As a mobile terminal travels between cells defined by different ones of the base transceiver stations, communication handoffs are effectuated to permit continued communications by, and with, the mobile terminal. Through appropriate positioning of the base transceiver stations, only relatively low-powered signals need to be generated to effectuate communications between a mobile terminal and a base transceiver station. Hand-offs of communications between successive base transceiver stations, as the mobile terminal moves between cells permit the continued communications without necessitating increases in the power levels at which the communication signals are transmitted. And, because only relatively low-powered signals need to be generated to effectuate communications, the same radio channels can be reused at different locations of the same cellular communication network. Efficient utilization of the frequency-spectrum allocation to the cellular communication network is thereby possible. [0008]Various operating specifications have been promulgated that define operational parameters by which cellular, as well as other, communication networks are to be operable. Successive generations of cellular communication networks, incorporating technological advancements, as such advancements become available, have been defined by successive generations, or updates to, operational specifications. First-generation (1G) and second-generation (2G) networks have been widely implemented and have achieved significant levels of usage. In this regard, the goal of second generation (2G) networks (e.g., IS-95) was to enable pre-defined mobile telephony services that were spectrum efficient and economically viable. The result was a network that provided mobile low rate circuit switched voice communications and low rate data communications. The success of 2G is evidenced by its consumer acceptance and popularity that exceeded expectations. As more consumers used mobile terminal services, certain increasing numbers of them manifested a desire for more capacity in both voice and data. The cellular industry responded with third-generation (3G) (e.g., cdma2000) networks, the next generation that introduced packet switched data networks. [0009]Code Division Multiple Access (CDMA) was introduced into cellular based, mobile communication systems in the early 1990s with the introduction of the IS-95 standard. Since then, CDMA technology has been well accepted in the wireless industry and has been widely disseminated reaching literally hundreds of millions of subscribers throughout the world. More recently, 3G backward-compatible evolutions of the IS-95 standard, such as the cdma2000 1X standard, have been developed to further improve the voice service capacity of CDMA while providing higher data rates for data services. As part of this evolution, the cdma2000 1X-EVDO network was developed to optimize wireless, high speed packet data services, such as may be facilitated by the Internet Protocol (IP). However, as networks such as cdma2000 1X-EVDO only support packet data services, mobile terminals, sometimes referred to as hybrid terminals, have been developed that are capable of accessing networks, such as cdma2000 1X, that provide both voice and data services, as well as networks such as cdma2000 1X-EVDO that provide higher-speed packet data services. Thus, a hybrid terminal could utilize a cdma2000-1X network for voice communications and for short message service (SMS), and a cdma2000-1X-EVDO network for multimedia message service (MMS) and for other data communications. [0010]In a network such as cdma2000 1X or 1X-EVDO, when a message (i.e., a “call”) is to be terminated at a mobile terminal, the network infrastructure broadcasts a paging message to alert the mobile terminal of the message. Monitoring channels of the respective network, the mobile terminal detects the paging message and, in response, performs various operations to receive the terminating message. With respect to the detection of a paging message, slotted mode operation was introduced in cdma2000 1X systems to conserve the life of a mobile terminal's battery. In this regard, the channel via which paging messages are transmitted, e.g., the forward common signaling logical channel (f-csch), is divided into 2048 slots. A mobile terminal operating in slotted mode is therefore assigned one of the slots and only needs to monitor its assigned slot and subsequent slot. See, for example, FIG. 1. Other than its assigned slot and the subsequent slot, the mobile terminal can opt to turn off its receiver/transmitter and to defer other non-vital processing. Each paging slot in a cdma2000 1X system is 80 ms in length and the slot assigned to a mobile terminal is determined through a hash algorithm defined in the cdma2000 1X standard. By way of example, the hash algorithm takes the phone number (MIN) of the mobile terminal and determines which slot of the 2048 possible slots (denoted slots 0˜2047) is the slot assigned to the mobile terminal. Since the cdma200 1X network also uses the same hash algorithm, the network is also aware which is the slot assigned to the mobile terminal. [0011]Also defined in a cdma2000 1X system is the concept of a slot cycle. In this regard, once a mobile terminal determines its assigned slot, the mobile terminal will wake up every slot cycle to check if there is page indication or other message addressed to it in its assigned slot or in the subsequent slot. As shown in FIG. 1, the mobile terminals may have different slot cycles with the cycle of MN 0 being 1.28 seconds and the cycle of MN 7 being 2.56 seconds, for example. Moreover, by permitting messages to be transmitted to the mobile terminal both in its assigned slot and in the subsequent slot, the network has improved flexibility in regards to the scheduling of the messages to the mobile terminal which is particularly useful in instances in which the paging channel is crowded. [0012]Since there are only 2048 possible slot positions, different mobile terminals can be assigned the same slot. See FIG. 1 in which MN 0, MN 3 and MN 4 are all assigned to one slot, and MN 1 and MN 7 are all assigned to another slot. Before monitoring its assigned slot, a mobile terminal does not know whether there will be pages/messages for the mobile terminal in its next assigned slot. If the network does not need to page or transmit any other message to any of the mobile terminals in that assigned slot, the network advantageously advises the mobile terminals assigned to the slot as soon as possible within the slot so that mobile terminals can go to sleep as early as possible, thereby further conserving battery power. As shown in FIG. 2, the mechanism in a cdma2000 1X network is to set the CLASS—0_DONE field to ‘1’ in the General Page Message (GPM) to indicate that there are no pages/messages for the mobile terminals of the respective slot. Upon receiving this GPM in the assigned slot, the mobile terminals can go to sleep immediately, i.e., prior to the end of the slot as shown in FIG. 2. In the common instance in which many mobile terminals utilize the same slot, the network cannot transmit the GPM with the CLASS—0_DONE field set to 1 until any messages have been transmitted to the mobile terminals assigned to the slot. For those mobile terminals that are not receiving a message, the mobile terminals must stay awake, during the transmission of messages to other mobile terminals, thereby unnecessarily consuming battery power. [0013]As will be appreciated by those skilled in the art, however, in various instances of operating in a network such as cdma2000 1X, a mobile terminal may not otherwise monitor for paging messages from a cdma2000 1X-EVDO network, thereby conserving battery power. For example, a mobile terminal may initially be operating in a cdma2000 1X-EVDO network in conjunction with a data application, e.g., the download of an ftp file. At some point in time, the data application may go dormant, such as upon completion of the ftp file download, and the mobile terminal may be placed in an idle state by the cdma2000 1X-EVDO network. The mobile terminal may thereafter switch to a cdma2000 1X network. The mobile terminal may switch to the cdma2000 1X network for many reasons including the loss of network services by the cdma2000 1X-EVDO network coupled with the discovery of network services by the cdma2000 1X network or the placing of a voice call by the mobile terminal. Since the mobile terminal is now monitoring a different frequency for signals from the cdma2000 1X network than from the cdma2000 1X-EVDO network, the mobile terminal will no longer be monitoring for paging messages from the cdma2000 1X-EVDO network. In addition to frequency differences, differences in the over-the-air technology between two networks would also prevent the mobile terminal active in one network from monitoring for paging messages in another network. In such instances, although the cdma2000 1X-EVDO network may have a message to be terminated at the mobile terminal operating in the cdma2000 1X network, such as an advertisement or the download of a new movie, the cdma2000 1X-EVDO network may be unable to reach the mobile terminal via a paging message. SUMMARY OF THE INVENTION [0014]In light of the foregoing background, embodiments of the present invention provide a system, a network, a mobile terminal and a method for cross-paging a mobile terminal even in instances in which the mobile terminal has stopped monitoring for paging messages. In this regard, a target network, such as a data only network (e.g., cdma2000 1X-EVDO), with which the mobile terminal is not currently communicating may notify the mobile terminal that the target network desires to establish communication with the mobile terminal, even in instances in which the mobile terminal is actively communicating via an anchor network, such as a voice and data network (e.g., cdma2000 1X) and has stopped monitoring for paging messages from other networks. As such, the mobile terminal can end communications with the anchor network and can then commence communications with the target network. For example, a user of a mobile terminal may terminate voice communications via a voice and data network in order to receive a MMS message or download a movie via a data only network upon receiving notification that the data only network desires to establish a communications session with the mobile terminal. [0015]The target network may notify the mobile terminal of its desire to communicate with the mobile terminal by means of a message, such as a page message, transmitted to the anchor network. The anchor network of this embodiment can then issue a Data Burst Message (DBM) including a predefined code to the mobile terminal notifying the mobile terminal of the inquiry from the target network. In response to the DBM, the mobile terminal may determine if a switch should be made from the anchor network to the target network and, if so, may end the anchor traffic channel assignment and issue a connection request to the target network to initiate target network traffic and service setup. Along with a page notification, the target network can provide the anchor network with network and service availability information. This network and service availability information can assist the user in determining whether to switch to the target network and, if so, can assist in rapidly and efficiently performing the target network traffic and service setup. [0016]According to one embodiment, the signaling sequence is altered for those mobile terminals that are in an idle state. In the slot to which the mobile terminals are assigned, a general page message (GPM) may be transmitted with a predefined field set to a predetermined value which notifies all non-hybrid mobile terminals, i.e., those mobile terminals that would be incapable of communicating with the target network, assigned to the slot to cease monitoring the slot and to go back to sleep. The hybrid mobile terminals continue monitoring the slot so as to receive the DBM which is directed to one or more hybrid mobile terminals. A conventional GPM can then be issued to direct the remaining hybrid mobile terminals, i.e., those hybrid mobile terminals that have not switched to a target network, to cease monitoring the slot and to go back to sleep. By employing the signaling sequence of this embodiment of the present invention, the battery life of the non-hybrid mobile terminals is therefore further conserved. [0017]According to exemplary embodiments, a method and computer program product is provided for cross-paging a selected hybrid mobile terminal which includes receiving a page indication from a target network. The page indication indicates that the target network desires to communicate with the selected hybrid mobile terminal. A first message of a series of messages is then sent to the selected hybrid mobile terminal which is one of a group of hybrid mobile terminals and non-hybrid mobile terminals. The first message directs the at least one non-hybrid mobile terminal to cease monitoring a slot if a predefined field of the first message is set to a predetermined value. A second message of the series of messages is then sent. The second message includes a data burst message indicative of the page indication to the selected hybrid mobile terminal. A third message of the general page message may then be sent. The third message directs any remaining hybrid mobile terminals to cease monitoring the slot. [0018]According to another exemplary embodiment, a system and networks for cross-paging a selected hybrid mobile terminal are provided. The system includes an anchor network and a target network. The anchor network is capable of communication with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot. The target network is capable of issuing a page indication to the anchor network. The page indication indicates that the target network desires to communicate with the selected hybrid mobile terminal, which is one of the hybrid mobile terminals. The anchor network issues a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal. The series of messages includes a first message and a second message. The first message directs the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value. The second message includes a data burst message indicative of the page indication to the selected hybrid mobile terminal. [0019]According to another exemplary embodiment, a mobile terminal capable of being cross-paged is provided. The mobile terminal monitors a slot while in communication with an anchor network and is capable of communication with a target network. The mobile terminal includes a controller capable of receiving a series of messages from the anchor network. The series of messages includes a first message and a second message. The first message directs any non-hybrid mobile terminal in communication with the anchor network to cease monitoring the slot if a predefined field of the first message is set to a predetermined value. The second message includes a data burst message indicative of a page indication to the mobile terminal, with the page indication indicating that the target network desires to communicate with the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0020]Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein: [0021]FIG. 1 is a schematic representation of the slotted mode operation provided by a conventional cdma2000 system; [0022]FIG. 2 is a schematic representation of the use of GPM in a conventional manner to halt the monitoring of a slot as soon as practical; [0023]FIG. 3 is a block diagram of one type of mobile node and system that would benefit from embodiments of the present invention; [0024]FIG. 4 is a schematic block diagram of an entity capable of operating as a mobile node, home agent, foreign agent and/or correspondent node, in accordance with embodiments of the present invention; [0025]FIG. 5 is a schematic block diagram of a mobile node, in accordance with one embodiment of the present invention; [0026]FIG. 6 is a control flow diagram illustrating communication between various entities performing a method of cross-paging a mobile terminal, in accordance with one embodiment of the present invention; [0027]FIG. 7 is a schematic representation of a DBM transmitted in a slot in accordance with one embodiment of the present invention; [0028]FIG. 8 is a schematic representation of a modified GPM and a DBM transmitted in a slot in accordance with another embodiment of the present invention; and [0029]FIG. 9 is a block diagram of an exemplary method for cross-paging a mobile terminal via a data burst message in accordance with an exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION [0030]The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. [0031]Referring to FIG. 3, an illustration of one type of system that would benefit from the present invention is provided. The system, method and computer program product of embodiments of the present invention will be primarily described in conjunction with mobile communications applications. It should be understood, however, that the system, method and computer program product of embodiments of the present invention can be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries. For example, the system, method and computer program product of embodiments of the present invention can be utilized in conjunction with wireline and/or wireless network (e.g., Internet) applications. [0032]As shown, the system can include a mobile terminal, hereinafter a mobile node (MN), 10 capable of transmitting signals to and for receiving signals from base sites or base stations (BS) 14, two of which are shown in FIG. 3 (shown and described below as including an anchor BS 14a and a target BS 14b). The base station is a part of one or more cellular or mobile networks that include elements required to operate the network, such as a mobile switching center (MSC) (not shown). As well known to those skilled in the art, the mobile network may also be referred to as a Base Station/MSC/Interworking function (BMI). In operation, the MSC is capable of routing calls to and from the terminal when the terminal is making and receiving calls. The MSC can also provide a connection to landline trunks when the terminal is involved in a call. In addition, the MSC can be capable of controlling the forwarding of messages to and from the terminal, and can also control the forwarding of messages for the terminal to and from a messaging center. [0033]The MN 10 can also be coupled to a data network. For example, the BS 14 can be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN). In one typical embodiment, the BS is coupled to a gateway, which is coupled to the data network, such as an Internet Protocol (IP) network 16. The gateway can comprise any of a number of different entities capable of providing network connectivity between the MN and other nodes directly or indirectly coupled to the data network. As will be appreciated, the gateway can be described in any of a number of different manners, such as a home agent (HA) 18, foreign agent (FA) 20 (shown and described below as including an anchor FA 20a and a target FA 20b), packet data serving node (PDSN), access router or the like. In this regard, a HA can comprise a router within a home network 22 of the MN. The HA is capable of tunneling data for delivery to the MN when the MN is away from home, and can maintain current location information for the MN. A FA, on the other hand, can comprise router within a visited network 24 of the MN (shown and described below as including an anchor visited network 24a and a target visited network 24b). The FA provides routing services to the MN while the MN is registered with the visited network. In operation, the FA detunnels data from the HA, and delivers the data to the MN. Then, for data sent from a MN registered with the visited network, the FA can serve as a default router. [0034]The other nodes coupled to the MN 10 via the IP network 16 can comprise any of a number of different devices, systems or the like capable of communicating with the MN in accordance with embodiments of the present invention. As described herein, a node capable of communicating with the MN via the IP network is referred to as a correspondent node (CN) 26, one of which is shown in FIG. 3. The other CNs can comprise, for example, personal computers, server computers or the like. Additionally or alternatively, for example, one or more CNs can comprise, other MNs, such as mobile telephones, portable digital assistants (PDAs), pagers, laptop computers, or the like. [0035]Although not every element of every possible network is shown and described herein, it should be appreciated that the MN 10 can be coupled to one or more of any of a number of different networks. As shown and described herein, the anchor visited network 24a is capable of supporting communication in accordance with third-generation (3G) mobile communication protocol cdma2000 1X (TIA/EIA/IS-2000), while the target visited network 24b is capable of supporting communication in accordance with 3G mobile communication protocol cdma2000 1XEV-DO (TIA/EIA/IS-856). It should be appreciated, however, that the mobile network(s) may be equally capable of operating in accordance with embodiments of the present invention while supporting communication in accordance with any one or more of a number of other first-generation (1G), second-generation (2G), 2.5G, 3G or other mobile communication protocols. For example, one or more networks capable of supporting communication in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, IS-95 (CDMA) or the like; 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE) or the like; and/or 3G wireless communication protocols Universal Mobile Telephone System (UMTS) network employing Wideband Code Division Multiple Access (WCDMA) radio access technology, cdma2000 1XEV-DV or the like. [0036]Referring now to FIG. 4, a block diagram of an entity capable of operating as a MN 10, HA 18, FA 20 and/or CN 26 is shown in accordance with one embodiment of the present invention. Although shown as separate entities, in some embodiments, one or more entities may support one or more of a MN, HA, FA and/or CN, logically separated but co-located within the entit(ies). For example, a single entity may support a logically separate, but co-located, HA and CN. Also, for example, a single entity may support a logically separate, but co-located FA and CN. [0037]As shown, the entity capable of operating as a MN 10, HA 18, FA 20 and/or CN 26 can generally include a processor 30 connected to a memory 32. The memory can comprise volatile and/or non-volatile memory, and typically stores content, data or the like. For example, the memory typically stores content transmitted from, and/or received by, the entity. Also for example, the memory typically stores software applications, instructions or the like for the processor to perform steps associated with operation of the entity in accordance with embodiments of the present invention. [0038]In addition to the memory 32, the processor 30 can also be connected to at least one interface or other means for displaying, transmitting and/or receiving data, content or the like. In this regard, the interface(s) can include at least one communication interface 34 or other means for transmitting and/or receiving data, content or the like, as well as at least one user interface that can include a display 36 and/or a user input interface 38. The user input interface, in turn, can comprise any of a number of devices allowing the entity to receive data from a user, such as a keypad, a touch display, a joystick or other input device. [0039]Reference is now made to FIG. 5, which illustrates one type of MN 10 that would benefit from embodiments of the present invention. It should be understood, however, that the MN illustrated and hereinafter described is merely illustrative of one type of MN that would benefit from the present invention and, therefore, should not be taken to limit the scope of the present invention. While several embodiments of the MN are illustrated and will be hereinafter described for purposes of example, other types of MNs, such as portable digital assistants (PDAs), pagers, laptop computers and other types of electronic systems, can readily employ the present invention. [0040]As shown, in addition to an antenna 40, the MN 10 includes a transmitter 42, a receiver 44, and a controller 46 that provides signals to and receives signals from the transmitter and receiver, respectively. These signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data. In this regard, the MN can be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. As explained herein, the MN is capable of operating in accordance with the cdma2000 1X and cdma2000 1XEV-DO communication protocols. It should be understood, however, that the MN may more generally be capable of operating in accordance with any of a number of 1G, 2G, 2.5G, 3G or other communication protocols. [0041]It is understood that the controller 46 includes the circuitry required for implementing the audio and logic functions of the MN 10. For example, the controller may be comprised of a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits. The control and signal processing functions of the MN are allocated between these devices according to their respective capabilities. The controller can additionally include an internal voice coder (VC) 46A, and may include an internal data modem (DM) 46B. Further, the controller may include the functionality to operate one or more software programs, which may be stored in memory (described below). For example, the controller may be capable of operating a connectivity program, such as a conventional Web browser. The connectivity program may then allow the MN to transmit and receive Web content, such as according to HTTP and/or the Wireless Application Protocol (WAP), for example. [0042]The MN 10 also comprises a user interface including a conventional earphone or speaker 48, a ringer 50, a microphone 52, a display 54, and a user input interface, all of which are coupled to the controller 46. The user input interface, which allows the MN to receive data, can comprise any of a number of devices allowing the MN to receive data, such as a keypad 56, a touch display (not shown) or other input device. In embodiments including a keypad, the keypad includes the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the MN. Although not shown, the MN can include a battery, such as a vibrating battery pack, for powering the various circuits that are required to operate the MN, as well as optionally providing mechanical vibration as a detectable output. [0043]The MN 10 can also include memory, such as a subscriber identity module (SIM) 58, a removable user identity module (R-UIM) or the like, which typically stores information elements related to a mobile subscriber. In addition to the SIM, the MN can include other removable and/or fixed memory. In this regard, the MN can include volatile memory 60, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The MN can also include other non-volatile memory 62, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively comprise an EEPROM, flash memory or the like. The memories can store any of a number of pieces of information,(String), 相关申请的交叉引用 [0001] 本申请要求 2005 年 2 月 14 日提交的美国临时申请第 60/652,674 号的权益,其内容全部并入本文。 发明领域 [0002] [0001] 本发明一般涉及当移动终端在另一网络中操作时从一个网络交叉寻呼移动终端的系统和方法,更具体地,涉及通过数据从网络交叉寻呼移动终端的系统和方法。 移动终端在其中运行的另一个网络中的突发消息 (DBM)。 发明背景 [0003] 通信网络用于在两个或多个通信站之间传送数据。 通信网络至少由构成发送站的第一通信站和构成接收站的第二通信站构成。 通信站通过通信信道相互连接。 并且要由第一通信站传送到第二通信站的数据通过通信信道被发送到第二通信站。 要传送的数据由第一通信站转换成允许其在通信信道上传送的形式。 并且第二通信站操作以检测向其传送的数据并恢复其信息内容。 [0004] 已经开发和实施了许多不同类型的通信网络以实现通信站之间的数据通信。 随着通信技术的不断进步,新型通信网络以及对现有通信网络的改进已经并将继续进行。 [0005] 无线电通信网络是通信网络的示例类型。 无线电通信网络利用无线电通信信道来传输要在其中运行的通信站之间通信的数据。 无线通信信道是根据构成电磁频谱一部分的无线链路定义的。 由于使用无线电链路来定义通信信道,因此避免了使用有线连接来定义通信信道的需要。 无线通信网络的实现通常比构建传统的有线通信网络所需的相应成本要低。 并且可以实现无线电通信网络以形成移动通信网络。 [0006] 作为无线电通信网络的示例的蜂窝通信网络已经被广泛实施并且已经达到了广泛的使用水平。 蜂窝通信网络提供与移动终端的无线电通信。 移动终端允许通过其实现电话通信。 蜂窝通信网络包括遍及地理区域安装的网络部分并且移动终端通过无线电信道与其通信。 构成通信网络的网络部分的部分的基站收发信机安装在整个地理区域中的间隔开的位置,该地理区域将被通信网络覆盖。 每个基站收发器定义了一个包含一部分地理区域的小区。 当移动终端位于基站收发信台定义的小区内时,通常可以与定义该小区的基站收发信台进行通信。 [0007]当移动终端在由不同的基站收发信台定义的小区之间移动时,实现通信切换以允许移动终端继续进行通信并与移动终端进行通信。 通过基站收发器的适当定位,仅需要生成相对低功率的信号来实现移动终端和基站收发器之间的通信。 当移动终端在小区之间移动时,连续基站收发信台之间的通信切换允许继续通信,而无需增加通信信号传输的功率电平。 并且,因为只需要产生相对低功率的信号来实现通信,所以可以在同一蜂窝通信网络的不同位置重复使用相同的无线电信道。 从而可以有效地利用分配给蜂窝通信网络的频谱。 [0008] 已经颁布了各种操作规范,这些规范定义了蜂窝以及其他通信网络可操作的操作参数。 结合技术进步的连续几代蜂窝通信网络,随着此类进步变得可用,已由连续几代或更新操作规范定义。 第一代 (1G) 和第二代 (2G) 网络已得到广泛实施,并取得了显着的使用水平。 在这方面,第二代 (2G) 网络(例如 IS-95)的目标是实现频谱高效且经济可行的预定义移动电话服务。 结果是一个提供移动低速率电路交换语音通信和低速率数据通信的网络。 2G 的成功体现在其消费者接受度和受欢迎程度超出预期。 随着越来越多的消费者使用移动终端服务,越来越多的消费者表现出对更多语音和数据容量的需求。 蜂窝行业以第三代 (3G)(例如 cdma2000)网络作为回应,下一代网络引入了分组交换数据网络。 [0009] 随着 IS-95 标准的推出,码分多址 (CDMA) 在 1990 年代初被引入基于蜂窝的移动通信系统。 从那时起,CDMA 技术在无线行业得到了广泛接受,并得到了广泛传播,几乎覆盖了全世界数亿用户。 最近,已经开发了 IS-95 标准的 3G 向后兼容演进,例如 cdma2000 1X 标准,以进一步提高 CDMA 的语音服务容量,同时为数据服务提供更高的数据速率。 作为这一演进的一部分,开发了 cdma2000 1X-EVDO 网络以优化无线、高速分组数据服务,例如因特网协议 (IP) 可能促进的服务。 然而,由于cdma2000 1X-EVDO等网络仅支持分组数据业务,因此开发了移动终端,有时也称为混合终端,能够接入提供语音和数据业务的网络,如cdma2000 1X,如 以及提供更高速分组数据服务的网络,例如 cdma2000 1X-EVDO。 因此,混合终端可以利用 cdma2000-1X 网络进行语音通信和短消息服务 (SMS),并利用 cdma2000-1X-EVDO 网络进行多媒体消息服务 (MMS) 和其他数据通信。 [0010]在 cdma2000 1X 或 1X-EVDO 等网络中,当消息(即“呼叫”)要在移动终端终止时,网络基础设施会广播寻呼消息以提醒移动终端该消息。 监视相应网络的信道,移动终端检测寻呼消息并作为响应执行各种操作以接收终止消息。 关于寻呼消息的检测,在 cdma2000 1X 系统中引入时隙模式操作以节省移动终端电池的寿命。 在这点上,传送寻呼消息的信道,例如前向公共信令逻辑信道(f-csch),被分成2048个时隙。 因此,以时隙模式运行的移动终端被分配了一个时隙,并且只需要监视其分配的时隙和后续时隙。 参见例如图1。除了分配给它的时隙和随后的时隙之外,移动终端可以选择关闭它的接收器/发射器并推迟其他非重要的处理。 cdma2000 1X 系统中的每个寻呼时隙长度为 80 ms,分配给移动终端的时隙是通过 cdma2000 1X 标准中定义的散列算法确定的。 举例来说,散列算法采用移动终端的电话号码(MIN)并确定2048个可能的时隙(表示为时隙0~2047)中的哪个时隙是分配给移动终端的时隙。 由于 cdma200 1X 网络也使用相同的散列算法,网络也知道分配给移动终端的时隙。 [0011] 在 cdma2000 1X 系统中还定义了时隙周期的概念。 就此而言,一旦移动终端确定了其分配的时隙,移动终端将在每个时隙周期唤​​醒以检查在其分配的时隙或后续时隙中是否存在寻呼指示或寻址到它的其他消息。 如图1所示,移动终端的时隙周期可以与MN的周期不同 0 为 1.28 秒和 MN 的周期 7 例如,为 2.56 秒。 此外,通过允许在分配给移动终端的时隙和随后的时隙中向移动终端发送消息,网络在向移动终端调度消息方面提高了灵活性,这在寻呼的情况下特别有用 通道拥挤。 [0012] 由于只有 2048 个可能的时隙位置,不同的移动终端可以分配相同的时隙。 见图1,其中MN 0 , 明尼苏达州 3 和锰 4 都分配到一个时隙,MN 1 和锰 7 都分配给另一个插槽。 在监视其分配的时隙之前,移动终端不知道在其下一个分配的时隙中是否有针对该移动终端的寻呼/消息。 如果网络不需要寻呼或发送任何其他消息到指定时隙中的任何移动终端,则网络有利地在该时隙内尽快通知指定给该时隙的移动终端,以便移动终端可以进入休眠状态 尽早,从而进一步节省电池电量。 如图 2 所示,cdma2000 1X 网络中的机制是设置 CLASS — 通用寻呼消息 (GPM) 中的 0_DONE 字段为“1”,指示相应时隙的移动终端没有寻呼/消息。 在分配的时隙中收到此 GPM 后,移动终端可以立即进入休眠状态,即在时隙结束之前,如图 2 所示。在许多移动终端使用同一时隙的常见情况下,网络无法 用 CLASS 传输 GPM — 0_DONE 字段设置为 1,直到任何消息都已传输到分配给该时隙的移动终端。 对于那些没有接收到消息的移动终端,在向其他移动终端发送消息期间,移动终端必须保持清醒,从而不必要地消耗电池电量。 [0013]然而,如本领域技术人员将理解的那样,在诸如cdma2000 1X的网络中操作的各种实例中,移动终端可能不以其他方式监视来自cdma2000 1X-EVDO网络的寻呼消息,从而节省电池电量。 例如,移动终端最初可能在 cdma2000 1X-EVDO 网络中结合数据应用程序运行,例如,下载 ftp 文件。 在某个时间点,数据应用程序可能会进入休眠状态,例如在完成 ftp 文件下载时,并且移动终端可能会被 cdma2000 1X-EVDO 网络置于空闲状态。 此后移动终端可以切换到cdma2000 1X网络。 移动终端切换到cdma2000 1X网络的原因有很多,包括cdma2000 1X-EVDO网络的网络服务丢失以及cdma2000 1X网络发现网络服务或者移动终端发起语音呼叫。 由于移动终端现在正在监视来自 cdma2000 1X 网络和来自 cdma2000 1X-EVDO 网络的不同频率的信号,因此移动终端将不再监视来自 cdma2000 1X-EVDO 网络的寻呼消息。 除了频率差异之外,两个网络之间无线技术的差异也会阻止在一个网络中活动的移动终端监听另一个网络中的寻呼消息。 在这种情况下,尽管 cdma2000 1X-EVDO 网络可能有一条消息要在 cdma2000 1X 网络中运行的移动终端终止,例如广告或下载新电影,但 cdma2000 1X-EVDO 网络可能无法 通过寻呼消息到达移动终端。 发明内容 [0014] 鉴于上述背景,本发明实施例提供了一种即使在移动终端停止监听寻呼消息的情况下,也能对移动终端进行交叉寻呼的系统、网络、移动终端及方法。 就此而言,移动终端当前未与之通信的诸如纯数据网络(例如,cdma2000 1X-EVDO)的目标网络可以通知移动终端目标网络期望与移动终端建立通信, 即使在移动终端通过诸如语音和数据网络(例如,cdma2000 1X)之类的锚定网络主动通信并且已经停止监视来自其他网络的寻呼消息的情况下。 这样,移动终端可以结束与锚定网络的通信,然后可以开始与目标网络的通信。 例如,移动终端的用户可以在接收到仅数据网络希望与 移动终端。 [0015] 目标网络可以通过发送给锚定网络的消息,例如寻呼消息,通知移动终端其希望与移动终端进行通信。 然后,该实施例的锚定网络可以向移动终端发出包括预定义代码的数据突发消息(DBM),通知移动终端来自目标网络的查询。 响应于DBM,移动终端可以确定是否应该从锚定网络切换到目标网络,并且如果是,则可以结束锚定业务信道分配并且向目标网络发出连接请求以启动目标网络 流量和服务设置。 连同页面通知,目标网络可以向锚定网络提供网络和服务可用性信息。 该网络和服务可用性信息可以帮助用户确定是否切换到目标网络,如果是,则可以帮助快速有效地执行目标网络流量和服务设置。 [0016]根据一个实施例,对于处于空闲状态的那些移动终端改变信令序列。 在分配给移动终端的时隙中,可以发送通用寻呼消息(GPM),其中预定义字段设置为预定值,通知所有非混合移动终端,即那些不能通信的移动终端 与目标网络,分配给插槽以停止监视插槽并返回睡眠状态。 混合移动终端继续监视时隙以便接收指向一个或多个混合移动终端的DBM。 然后可以发布传统的 GPM 以指示剩余的混合移动终端,即,那些还没有切换到目标网络的混合移动终端,停止监视时隙并返回睡眠。 通过采用本发明该实施例的信令序列,因此进一步节省了非混合移动终端的电池寿命。 [0017] 根据示例性实施例,提供了一种用于交叉寻呼所选择的混合移动终端的方法和计算机程序产品,其包括从目标网络接收寻呼指示。 寻呼指示表明目标网络希望与选定的混合移动终端进行通信。 然后将一系列消息中的第一条消息发送到所选择的混合移动终端,该混合移动终端是一组混合移动终端和非混合移动终端中的一个。 如果第一消息的预定义字段被设置为预定值,则第一消息指示至少一个非混合移动终端停止监视时隙。 然后发送该系列消息中的第二条消息。 第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。 然后可以发送通用寻呼消息的第三消息。 第三条消息指示任何剩余的混合移动终端停止监视时隙。 [0018] 根据另一个示例性实施例,提供了一种用于交叉寻呼所选择的混合移动终端的系统和网络。 该系统包括锚网络和目标网络。 锚定网络能够在时隙中与至少一个混合移动终端和至少一个非混合移动终端进行通信。 目标网络能够向锚网络发出寻呼指示。 寻呼指示指示目标网络期望与选择的混合移动终端通信,该混合移动终端是混合移动终端之一。 锚定网络向至少一个混合移动终端和至少一个非混合移动终端发布一系列消息。 该系列消息包括第一消息和第二消息。 如果第一消息的预定义字段被设置为预定值,则第一消息指示至少一个非混合移动终端停止监视时隙。 第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。 [0019] 根据另一示例性实施例,提供了一种能够跨页的移动终端。 移动终端在与锚定网络通信的同时监听时隙,能够与目标网络进行通信。 移动终端包括能够从锚定网络接收一系列消息的控制器。 该系列消息包括第一消息和第二消息。 如果第一消息的预定义字段被设置为预定值,则第一消息指示与锚定网络通信的任何非混合移动终端停止监视时隙。 第二消息包括指示对移动终端的寻呼指示的数据突发消息,寻呼指示指示目标网络期望与移动终端通信。 附图的简要说明 [0020] [0032] 已经以一般术语描述了本发明,现在将参考附图,这些附图不一定按比例绘制,并且其中: [0021] 图1是传统cdma2000系统提供的时隙模式操作的示意图; [0022]图2是以常规方式使用GPM来尽快停止对时隙的监视的示意图; [0023] 图3是受益于本发明实施例的一种类型的移动节点和系统的框图; [0024] 图4是根据本发明实施例的能够作为移动节点、归属代理、外地代理和/或通信节点操作的实体的示意框图; [0025] 图5是根据本发明的一个实施例的移动节点的示意框图; [0026] 图6是说明根据本发明的一个实施例的执行跨寻呼移动终端的方法的各种实体之间的通信的控制流程图; [0027] 图7是根据本发明的一个实施例在时隙中传输的DBM的示意图; [0028] 图8是根据本发明的另一个实施例的在时隙中传输的修改的GPM和DBM的示意图; 和 [0029] 图9是根据本发明示例性实施例的用于经由数据突发消息交叉寻呼移动终端的示例性方法的框图。 发明详述 [0030] 现在将在下文中参考附图更全面地描述本发明,其中示出了本发明的优选实施例。 然而,本发明可以以许多不同的形式来体现,并且不应被解释为限于在此阐述的实施例; 相反,提供这些实施例是为了使本公开透彻和完整,并将本发明的范围充分地传达给本领域的技术人员。 相同的数字始终指代相同的元素。 [0031] 参考图3,提供了将受益于本发明的一种类型的系统的图示。 将主要结合移动通信应用来描述本发明实施例的系统、方法和计算机程序产品。 然而,应当理解,本发明的实施例的系统、方法和计算机程序产品可以结合移动通信行业中和移动通信行业之外的各种其他应用来使用。 例如,本发明实施例的系统、方法和计算机程序产品可以结合有线和/或无线网络(例如因特网)应用程序使用。 [0032] 如图所示,该系统可以包括移动终端,以下称为移动节点(MN), 10 能够向基站或基站 (BS) 发送信号并从中接收信号 14 ,其中两个显示在图 3 中(在下面显示和描述为包括锚点 BS 14 a 和一个目标 BS 14 b ). 基站是一个或多个蜂窝或移动网络的一部分,包括操作网络所需的元件,例如移动交换中心(MSC)(未示出)。 如本领域技术人员所熟知的,移动网络也可以称为基站/MSC/互通功能(BMI)。 在操作中,当终端正在拨打和接收呼叫时,MSC 能够将呼叫路由到终端和从终端路由呼叫。 当终端参与通话时,MSC 还可以提供与陆线干线的连接。 另外,MSC可以控制与终端的消息转发,也可以控制终端与消息中心的消息转发。 [0033] 明尼苏达州 10 也可以耦合到数据网络。 例如,英国学士学位 14 可以耦合到数据网络,例如局域网(LAN)、城域网(MAN)和/或广域网(WAN)。 在一个典型的实施例中,BS耦合到网关,网关耦合到数据网络,例如互联网协议(IP)网络 16. 网关可以包括能够提供MN与直接或间接耦合到数据网络的其他节点之间的网络连接的多个不同实体中的任何一个。 应当理解,网关可以用多种不同方式中的任何一种来描述,例如归属代理(HA) 18 , 外国代理人 (FA) 20 (在下面显示和描述为包括锚点 FA 20 a 和一个目标 FA 20 b )、分组数据服务节点(PDSN)、接入路由器等。 在这方面,HA 可以包括家庭网络中的路由器 22 明尼苏达州的。 HA能够在MN不在家时通过隧道传输数据以传递给MN,并且可以维护MN的当前位置信息。 另一方面,FA 可以包含访问网络中的路由器 24 MN 的(如下所示和描述为包括锚访问网络 24 a 和目标访问网络 24 b ). FA在MN注册到拜访网络的同时向MN提供路由服务。 在操作中,FA 从 HA 解除数据隧道,并将数据传递给 MN。 然后,对于从注册到访问网络的MN发送的数据,FA可以作为默认路由器。 [0034] 其他节点耦合到 MN 10 通过IP网络 16 根据本发明的实施例,MN可以包括能够与MN通信的多个不同设备、系统等中的任何一个。 如本文所述,能够经由IP网络与MN通信的节点被称为对应节点(CN) 26 ,其中一个在图3中示出。其他CN可以包括例如个人计算机、服务器计算机等。 此外或备选地,例如,一个或多个CN可以包括其他MN,例如移动电话、便携式数字助理(PDA)、寻呼机、膝上型计算机等。 [0035] 虽然这里没有显示和描述每个可能网络的每个元素,但是应该理解,MN 10 可以耦合到许多不同网络中的任何一个或多个。 如本文所示和所述,锚访问网络 24 a 能够支持符合第三代 (3G) 移动通信协议 cdma2000 1X (TIA/EIA/IS-2000) 的通信,而目标访问网络 24 b 能够支持符合 3G 移动通信协议 cdma2000 1XEV-DO (TIA/EIA/IS-856) 的通信。 然而,应当理解,移动网络可以同样能够根据本发明的实施例操作,同时支持根据多个其他第一代(1G)中的任何一个或多个的通信, 第二代 (2G)、2.5G、3G 或其他移动通信协议。 例如,能够支持根据2G无线通信协议IS-136(TDMA)、GSM、IS-95(CDMA)等通信的一个或多个网络; 2.5G无线通信协议GPRS、增强型数据GSM环境(EDGE)等; 和/或 3G 无线通信协议 采用宽带码分多址 (WCDMA) 无线电接入技术的通用移动电话系统 (UMTS) 网络、cdma2000 1XEV-DV 等。 [0036] 现在参考图4,能够作为MN操作的实体的框图 10 , 哈 18 , F A 20 和/或中国 26 根据本发明的一个实施例示出。 尽管被示为单独的实体,但在一些实施例中,一个或多个实体可支持逻辑上分离但共同位于实体内的MN、HA、FA和/或CN中的一者或一者以上。 例如,单个实体可能支持逻辑上分离但位于同一位置的 HA 和 CN。 此外,例如,单个实体可以支持逻辑上分离但位于同一位置的 FA 和 CN。 [0037] 如图所示,能够作为 MN 运行的实体 10 , 哈 18 , F A 20 和/或中国 26 通常可以包括一个处理器 30 连接到内存 32. 存储器可以包括易失性和/或非易失性存储器,并且通常存储内容、数据等。 例如,存储器通常存储从实体发送和/或由实体接收的内容。 又例如,根据本发明的实施例,存储器通常存储软件应用程序、指令等以供处理器执行与实体的操作相关联的步骤。 [0038] 除了记忆 32 , 处理器 30 还可以连接到至少一个接口或其他装置,用于显示、传输和/或接收数据、内容等。 在这方面,接口可以包括至少一个通信接口 34 或用于传输和/或接收数据、内容等的其他装置,以及至少一个可以包括显示器的用户界面 36 和/或用户输入界面 38 . 用户输入接口又可以包括允许实体从用户接收数据的许多设备中的任何设备,例如小键盘、触摸显示器、操纵杆或其他输入设备。 [0039] 现在参考图5,其图示了一种类型的MN 10 这将受益于本发明的实施例。 然而,应当理解,所示出和下文描述的MN仅是将受益于本发明的一种类型的MN的说明,因此不应被视为限制本发明的范围。 虽然出于示例的目的示出并在下文中描述了MN的几个实施例,但是其他类型的MN,例如便携式数字助理(PDA)、寻呼机、膝上型计算机和其他类型的电子系统,可以容易地采用本发明。 [0040] 如图所示,除了一根天线 40 , 锰 10 包括一个发射器 42 , 一个接收器 44 , 和一个控制器 46 分别向发射器和接收器提供信号和从发射器和接收器接收信号。 这些信号包括符合适用蜂窝系统的空中接口标准的信令信息,以及用户语音和/或用户生成的数据。 就这一点而言,MN能够以一种或多种空中接口标准、通信协议、调制类型和接入类型进行操作。 如本文所解释的,MN能够根据cdma2000 1X和cdma2000 1XEV-DO通信协议进行操作。 然而,应当理解,MN可以更一般地能够根据多个1G、2G、2.5G、3G或其他通信协议中的任何一个来操作。 [0041] 据了解,控制器 46 包括实现 MN 的音频和逻辑功能所需的电路 10 . 例如,控制器可以包括数字信号处理器装置、微处理器装置以及各种模数转换器、数模转换器和其他支持电路。 MN的控制和信号处理功能根据各自的能力在这些设备之间进行分配。 控制器还可以包括一个内部语音编码器 (VC) 46 A,并且可能包括一个内部数据调制解调器(DM) 46 B.此外,控制器可以包括操作一个或多个软件程序的功能,这些软件程序可以存储在存储器中(如下所述)。 例如,控制器可能能够运行连接程序,例如传统的网络浏览器。 连接性程序然后可以允许 MN 发送和接收 Web 内容,例如根据 HTTP 和/或无线应用协议(WAP)。 [0042] 明尼苏达州 10 还包括一个用户界面,包括一个传统的耳机或扬声器 48 , 铃声 50 , 麦克风 52 , 一个显示器 54 和用户输入接口,所有这些都耦合到控制器 46 . 允许 MN 接收数据的用户输入接口可以包括任何允许 MN 接收数据的设备,例如键盘 56、触摸显示器(未显示)或其他输入设备。 在包括小键盘的实施例中,小键盘包括常规数字(0-9)和相关键(#、*),以及用于操作MN的其他键。 虽然未示出,但 MN 可以包括电池,例如振动电池组,用于为操作 MN 所需的各种电路供电,以及可选地提供机械振动作为可检测输出。 [0043] 明尼苏达州 10 还可以包括存储器,例如用户识别模块 (SIM) 58 、可移除用户身份模块(R-UIM)等,其通常存储与移动订户相关的信息元素。 除了 SIM 之外,MN 还可以包括其他可移动和/或固定存储器。 在这方面,MN 可以包括易失性存储器 60 ,例如易失性随机存取存储器(RAM),包括用于临时存储数据的高速缓存区域。 MN 还可以包括其他非易失性存储器 62 ,可以嵌入和/或可以移动。 非易失性存储器可以附加地或替代地包括EEPROM、闪存等。 存储器可以存储由 MN 用来实现 MN 功能的多条信息和数据中的任何一条。 例如,存储器可以存储标识符,例如国际移动设备识别码(IMEI)码、国际移动用户识别码(IMSI)码、移动台综合业务数字网络(MSISDN)码(移动电话号码)、会话发起协议(Session Initiation Protocol) (SIP)地址等,能够唯一识别移动站,例如移动网络 22 , 24 . [0044] 如背景部分中所解释的,网络,例如纯数据网络(例如,cdma2000 1X-EVDO),可能希望与 MN 建立通信 10 在另一个网络中运行,例如语音和数据网络(例如,cdma2000 1X)。 例如,cdma2000 1X-EVDO网络可能希望通过cdma2000 1X网络向当前支持语音通信的MN发送MMS消息或下载文件,例如电影或广告。 然而,在一个网络中运行的 MN 可能已停止监视其他网络的寻呼消息,这是 MN 当前未与之通信的网络通知 MN 它希望建立的传统技术 与 MN 的通信。 就这一点而言,如上所述,MN可能已经停止监视符合管理标准的寻呼消息以减少电池消耗。 [0045] 如下面更详细地解释的,本发明的实施例因此能够允许网络,诸如纯数据网络(例如,cdma2000 1X-EVDO),MN通过该网络 10 当前未通信以通知 MN 网络希望与 MN 建立通信,即使在 MN 正在通过另一个网络(例如语音和数据网络(例如,cdma2000 1X))主动通信并已停止监视的情况下 用于来自其他网络的寻呼消息。 因此,MN 可以结束与其先前一直与之通信的网络的通信,通常是在从 MN 或 MN 的用户接收到授权后,然后可以开始与已通知 MN 其期望的其他网络通信 与 MN 通信。 例如,MN 的用户可以在接收到仅数据网络希望与 锰。 [0046] 现在参考图6,其图示了交叉寻呼MN的方法的控制流程图 10 在当前的锚点 FA 中运行 20 a 在第一网络中,例如在 MN 和 CN 之间的通信会话期间 26 , MN 被新的目标 FA 通知 20 b 在目标 FA 希望与 MN 通信的不同网络中。 如本文所解释的,MN正在与锚点FA通信。 然而,应当理解,MN可以与锚点HA同等地通信 18, 在不脱离本发明的精神和范围的情况下。 此外,如下文所解释的,图6的方法适用于当MN在cdma2000 1X网络中操作时通过cdma2000 1X-EVDO网络交叉寻呼MN,或者将来可能通过信令的适当扩展反之亦然 由 cdma2000 1X-EVDO 网络提供。 就此而言,图6的方法将结合在cdma2000 1X-EVDO网络中从目标PDSN(即,目标FA)交叉寻呼MN来解释,同时MN处于与锚定PDSN的通信会话中( 即,在 cdma2000 1X 网络中锚定 FA)。 然而,应当理解,图6的方法可以同样适用于在MN在相同或不同类型的网络中操作时从多个其他网络中的任何网络交叉寻呼MN,而不背离 本发明的精神和范围。 [0047] 如图6所示,一种MN交叉寻呼的方法 10 根据本发明的一个实施例,包括一个 MN 10 最初与锚定网络中的锚定 PDSN 通信 20 a ,即 cdma 2000 1X 网络。 例如,MN 和锚点 PDSN 可能参与语音通信或 SMS 消息的交换。 在这个与锚定 PDSN 的通信会话期间,MN 可以停止监视来自其他网络的寻呼消息,否则这些寻呼消息会提醒 MN 另一个网络希望与 MN 通信。 MN 对寻呼消息的监视的停止通常由适用的标准管理并且可以出于各种原因来完成,包括例如为了节省电池消耗。 [0048] 在图6的方法中,目标网络 20 b ,例如 cdma2000 1X-EVDO 网络,可能希望与 MN 建立通信 10 , 但可以确定 MN 当前在锚网络中处于活动状态 20 a . 在这种情况下,目标网络向锚定网络发送目标页面。 该目标页面不仅包括页面通知,还有利地包括与目标网络相关的网络信息和服务可用性信息。 在其他信息中,网络信息例如可以包括目标网络的频率信息、开销信息和/或目标网络的业务信道分配。 锚定网络然后构造数据突发消息(DBM)以传送到MN以警告MN目标网络期望与MN通信。 尽管 MN 可能没有监视来自目标网络的寻呼消息,但是 MN 将接收并响应 DBM,从而即使在 MN 已经停止监视寻呼消息之后也允许 MN 被警告来自目标网络的寻呼通知。 [0049] DBM通常在预定字段中包括预定义代码以告知MN该DBM和其中包括的信息有效地构成来自另一个网络的页面通知。 尽管可以在不同领域使用各种代码,但是一个实施例的 DBM 的结构使得锚网络 20 a 将突发类型字段设置为 000111 以提醒 MN 10 另一个网络已发出寻呼通知。 除了在突发类型字段中包含预定义代码外,目标网络提供的其他信息 20 b ,例如网络信息和服务可用性信息也可以被封装并包含在DBM中。 当MN处于空闲状态或业务状态时,锚网络可以将DBM发送给MN。 如果处于空闲状态,则锚定网络通常在分配给 MN 的时隙中或在分配的时隙之后的时隙中传输 DBM。 或者,如果处于业务状态,则锚定网络仅以传统方式将DBM传输到MN。 [0050] 在接收到在预定字段中具有预定义代码的 DBM 后,例如突发类型字段设置为 000111,MN 10 可以确定是否希望从锚网络切换 20 a 到目标网络 20 b. 就此而言,如果MN处于空闲状态,则MN可以自动切换到目标网络,通常是在尽可能快的机会。 或者,如果MN处于业务状态,则MN可以被配置为在最早的实际机会自动从锚定网络切换到目标网络。 然而,典型地,处于业务状态的MN被配置为首先征求用户授权,例如经由呈现在MN的显示器上的图标建议用户另一网络期望与MN通信。 由于目标网络连同寻呼通知一起提供了各种服务和其他网络信息,因此 MN 可以但不一定向用户呈现至少一些这种附加信息,或者至少允许用户访问这种附加信息中的一些 根据请求提供信息,从而允许用户做出关于用户是否希望从锚定网络切换到目标网络的更明智的决定。 例如,用户可以在接收到另一网络期望与MN通信的通知时与朋友进行语音呼叫。 在查看与通知关联的附加信息时,在附加信息指示用户希望观看的新电影现在可供下载的情况下,用户可以选择终止语音呼叫并切换到另一个网络。 或者,在附加信息指示其他网络仅希望将广告下载到MN的情况下,用户可以选择继续语音呼叫并延迟到其他网络的任何切换。 [0051] 如果用户不希望切换到目标网络或者如果 MN 10 否则无法切换到目标网络,MN 向锚定网络发送预定义信号,例如移动站拒绝命令 20 a 反过来,它建议目标网络 20 b . 然而,如果 MN 要切换到目标网络,无论是由于 MN 处于空闲状态还是由于从处于业务状态的 MN 的用户接收到授权而自动切换,MN 发出 到目标网络的连接请求。 在 MN 已处于与锚定网络的业务状态的情况下,MN 必须首先结束当前业务信道分配,通常是在第一个实际机会时,然后发出连接请求。 为了进一步加速到目标网络的转换,MN可以放弃典型响应,例如通常为响应​​寻呼而发出的寻呼响应或通常为响应​​而发出的移动站确认命令(MS Ack) 到 DBM。 对于本领域的技术人员来说显而易见的是,目标网络先前提供的网络信息和服务可用性信息有助于MN构造连接请求。 例如,网络信息可以包括关于目标网络的频率信息,其帮助MN确定MN可以期望来自目标网络的服务的频率,从而避免MN必须基于基于目标网络来搜索来自目标网络的服务。 运营商提供的频率列表。 作为另一示例,网络信息还可以包括关于目标网络的开销信息。 由于MN在发送连接请求之前需要从目标网络获取最新的开销信息,因此MN不需要等待目标网络周期性发送开销信息,而是可以在获取到目标网络后立即发起连接请求,因为 MN已经收到DBM中的开销信息。 最后,网络信息可以包括目标网络中的业务分配,其允许MN直接切换到目标网络中的特定业务信道,甚至无需发送连接请求。 [0052] 收到连接请求后,目标网络 20 b 和锰 10 可以执行常规的流量和服务设置程序。 此后,MN经由目标网络与目标PDSN通信,例如交换MMS消息或其他纯数据服务。 [0053] 作为采用本发明实施例的交叉寻呼技术的结果,目标网络 20 b 可以向MN提供寻呼通知 10 为了从锚定网络发起切换 20 a 即使 MN 已停止监视来自其他网络的寻呼消息,也可以发送到目标网络。 此外,通过连同寻呼通知一起提供网络信息和/或业务信道分配,MN可以更快速和有效地连接到目标网络。 此外,通过连同寻呼通知一起提供服务可用性信息,处于与锚定网络的流量状态的MN的用户可以就用户是否期望切换到目标网络做出更有根据的决定。 本发明实施例的交叉寻呼技术还提供了无论MN处于空闲状态还是业务状态,目标网络和锚定网络都以相同的方式将来自目标网络的寻呼通知告知MN,从而简化了 网络侧的信令过程。 [0054] 如背景部分所述,cdma2000 1X 网络使用时隙操作模式,而 MN 10 处于空闲状态以节省 MN 电池的寿命。 也如上所述,cdma2000 1X 网络采用具有 CLASS 的 GPM — 0_DONE 字段设置为“1”以指示没有分配给相应时隙的 MN 的页面/消息,以便 MN 可以立即进入休眠状态,即,在时隙结束之前,并进一步节省电池电量。 为了确保 MN 收到指示目标网络的 DBM 20 b 希望与 MN 通信,DBM 必须在 GPM 与 CLASS 之前传输 — 0_DONE字段设置为1。如图7所示,MN 0 , 明尼苏达州 3 , 明尼苏达州 4 和锰 8 都分配到同一个插槽。 在发送 GPM 之前,如上所述传输 DBM,这表明目标网络希望与 MN 通信 4 . 收到 DBM 后,MN 4 切换到目标网络,而 MN 0 , 明尼苏达州 3 和锰 8 继续监控插槽。 GPM 与 CLASS — 然后发送设置为 1 的 0_DONE 字段,使得 MN 0 , 明尼苏达州 3 和锰 8 可以去睡觉了。 显而易见,所有 MN 都需要监视时隙,直到收到具有 CLASS 的 GPM — 0_DONE 字段设置为 1 会不利地消耗 DBM 未指向的 MN 的电池电量。 事实上,一些 MN 可能是非混合 MN,它们只能在语音和数据网络中进行通信,而不能在纯数据网络中进行通信。 尽管如此,所有 MN,包括不能在纯数据网络中通信的非混合 MN,都保持通电以接收 DBM,即使在这种情况下 DBM 与非混合 MN 无关。 [0055] 因此,本发明的一个实施例利用 GPM 中的预定义字段(例如 RESERVED 字段)来更改 MN 重新进入睡眠状态的过程,以便进一步节省电池电量,尤其是对于非混合 MN . 如图8所示,例如,其中MN 0 , 明尼苏达州 3 , 明尼苏达州 4 和锰 8 再次被分配到同一个时隙,考虑 MN 的情况 0 和锰 8 是非混合 MN 和 MN 3 和锰 4 是混合 MN。 一流的 GPM — 设置为 1 的 0_DONE 字段可能最初由锚网络传输 20 a. 与传统的 GPM 相比,预定义字段(例如 RESERVED 字段)被设置为预定值,例如 1。在任何情况下都无法访问目标网络的非混合 MN 不会检查 RESERVED 字段,并且 ,而是停止监视寻呼信道并返回休眠状态。 混合 MN 查看预定义字段以获取进一步说明。 在预定义字段被设置为预定值的情况下,例如,RESERVED字段被设置为1,混合MN继续监视DBM的寻呼信道。 或者,如果预定义字段未设置为预定值,例如,RESERVED字段设置为0,则混合MN也可以停止监视寻呼信道并返回休眠。 [0056] 在预定义字段设置为预定值的情况下,锚网络 20 a 接下来可以如上所述发送DBM。 如图8所示,DBM表示目标网络 20 b 希望与 MN 沟通 4 . 在 DBM 之后,MN 4 可以如上所述切换到目标网络,而MN 3 继续监视寻呼信道。 具有 CLASS 的传统 GPM — 可以发送设置为 1 的 0_DONE 字段和设置为不同于预定值的值的预定义字段,例如设置为 0 的 RESERVED 字段。 该 GPM 由尚未切换到另一个网络的所有混合 MN 接收,使得这些其他混合 MN(MN 3 在此示例中),也可以停止监视寻呼信道并返回休眠状态。 通过允许所有非混合 MN 返回休眠而不等待 DBM,根据该实施例进一步节省了非混合 MN 的电池电量,同时仍然允许一个或多个混合 MN 在另一个网络出现时得到通知 希望建立通信。 [0057] 根据本发明的一个方面,本发明的系统的全部或部分,例如MN的全部或部分 10 , 锚FA 20 a 目标 FA 20 b ,通常在计算机程序产品的控制下运行。 用于执行本发明实施例的方法的计算机程序产品包括计算机可读存储介质,例如非易失性存储介质,以及计算机可读程序代码部分,例如一系列计算机指令,体现在 计算机可读存储介质。 [0058] 在这方面,图9是根据本发明的方法、系统和计算机程序产品的框图。 应当理解,控制流程图的每个块或步骤以及控制流程图中的块的组合可以由计算机程序指令来实现。 这些计算机程序指令可以加载到计算机或其他可编程设备上以产生机器,使得在计算机或其他可编程设备上执行的指令创建用于实现控制流程图块或步骤中指定的功能的手段 (s). 这些计算机程序指令也可以存储在计算机可读存储器中,该存储器可以指示计算机或其他可编程装置以特定方式运行,使得存储在计算机可读存储器中的指令产生包括指令装置的制品 实现控制流程图块或步骤中指定的功能。 计算机程序指令也可以加载到计算机或其他可编程设备上,以导致在计算机或其他可编程设备上执行一系列操作步骤,以产生计算机实现的过程,使得在计算机或其他可编程设备上执行的指令 装置提供用于实现控制流程图块或步骤中指定的功能的步骤。 [0059]因此,框图的块或步骤支持用于执行指定功能的装置的组合、用于执行指定功能的步骤的组合以及用于执行指定功能的程序指令装置。 还应当理解,控制流程图的每个块或步骤,以及控制流程图中的块或步骤的组合,可以由执行指定功能或步骤的专用基于硬件的计算机系统来实现,或者 专用硬件和计算机指令。 [0060] 就此而言,在能够与至少一个混合移动终端和至少一个监视时隙的非混合移动终端通信的通信网络中,一种用于交叉寻呼至少一个混合移动终端中的所选一个的方法包括接收 操作中来自目标网络的寻呼指示 100 . 寻呼指示指示目标网络希望与至少一个混合移动终端中选择的一个进行通信。 运行中 110 ,将一系列消息中的第一消息发送到至少一个混合移动终端和至少一个非混合移动终端。 如果第一消息的预定义字段被设置为预定值,则第一消息指示至少一个非混合移动终端停止监视时隙。 运行中 120 ,可以将一系列消息中的第二消息发送到至少一个混合移动终端和至少一个非混合移动终端。 第二消息包括指示对至少一个混合移动终端中选择的一个的寻呼指示的数据突发消息。 运行中 130 ,可以发送该系列消息中的第三条消息。 第三消息指示至少一个混合移动终端中的任何其余混合移动终端停止监视时隙。 [0061] 本发明所属领域的技术人员受益于前述描述和相关附图中呈现的教导,将想到本发明的许多修改和其他实施例。 因此,应当理解,本发明不限于所公开的具体实施例,修改和其他实施例旨在包括在所附权利要求的范围内。 尽管本文使用了特定术语,但它们仅在一般和描述性意义上使用,并非出于限制目的。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: BRPI0608532A2(String), CN101164362A(String), EP1849328A1(String), IN6352DELNP2007A(String), JP2008532352A(String), KR1020080002760A(String), MX2007009823A(String), MYPI2006000588A0(String), SG134706A1(String), SG134706B(String), TW200642334A(String), US20060182069A1(String), US60652674P0(String), US7668136B2(String), VN16596A(String), WO2006085218A1(String), ZA200707790B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: BRPI0608532A2(String), CN101164362A(String), EP1849328A1(String), IN6352DELNP2007A(String), JP2008532352A(String), KR1020080002760A(String), MX2007009823A(String), MYPI2006000588A0(String), SG134706A1(String), SG134706B(String), TW200642334A(String), US20060182069A1(String), US60652674P0(String), US7668136B2(String), VN16596A(String), WO2006085218A1(String), ZA200707790B(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7668136B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), BRPI0608532A2(String), CN101164362A(String), EP1849328A1(String), IN6352DELNP2007A(String), JP2008532352A(String), KR1020080002760A(String), MX2007009823A(String), MYPI2006000588A0(String), SG134706A1(String), SG134706B(String), TW200642334A(String), US20060182069A1(String), US60652674P0(String), US7668136B2(String), VN16596A(String), WO2006085218A1(String), ZA200707790B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), BRPI0608532A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), CN101164362A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), EP1849328A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), IN6352DELNP2007A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), JP2008532352A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), KR1020080002760A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), MX2007009823A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), MYPI2006000588A0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:45.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), SG134706A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), SG134706B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), TW200642334A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.020 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.020 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.020 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), US20060182069A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), US60652674P0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), US7668136B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), VN16596A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), WO2006085218A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270664(Integer), ZA200707790B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.074 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.074 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.074 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7668136B2(String), US7668136B2(String), 1266854400(Integer), 270664(Integer), 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: NOKIA CORPORATION(String), NOKIA CORPORATION(String), 诺基亚公司(String), 诺基亚公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: NOKIA CORPORATION(String), 诺基亚公司(String), 0(Integer), 1681975546(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184982(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75925(Integer), 1(Integer), 184982(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: NOKIA CORPORATION(String), 诺基亚公司(String), 0(Integer), 1681975546(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184982(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75926(Integer), 2(Integer), 184982(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.142 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.142 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.142 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 184982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120072902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Self-Starting Method and Apparatus for Mobile Terminal, and Mobile Terminal(String), 一种移动终端的自启动方法、装置及移动终端(String), US20120072902A1(String), The present invention discloses a self-starting method and apparatus for a mobile terminal and a mobile terminal, which method comprises: when the mobile terminal is installed in a computer, installing the mobile terminal as a virtual compact disc (CD) of the computer; automatically running an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; and driving the mobile terminal using the driver. The present invention can achieve the self-starting of the mobile terminal, thus achieving the technical effect of facilitating use of user.(String), 本发明公开了一种移动终端自启动方法、装置及移动终端,方法包括:当移动终端安装在电脑中时,将移动终端安装为电脑的虚拟光盘; 自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 使用驱动程序驱动移动终端。 本发明能够实现移动终端的自启动,从而达到方便用户使用的技术效果。(String), US13/259777(String), 1274716800(Integer), US20120072902A1(String), 1332345600(Integer), 美国(String), 2(Integer), CN(String), 6(Integer), 10(Integer), US20030046447A1 | US20030099147A1 | US20040210897A1 | US20050015540A1 | US20090119445A1 | US20090193152A1 | US20100082843A1 | US20110060877A1 | US20130127749A1 | US8296757B2(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184983(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\4abbd99d35444ee8bd73449a6c7156fd.png(String), 184983(Integer), 4abbd99d35444ee8bd73449a6c7156fd.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Self-Starting Method and Apparatus for Mobile Terminal, and Mobile Terminal(String), 一种移动终端的自启动方法、装置及移动终端(String), US20120072902A1(String), The present invention discloses a self-starting method and apparatus for a mobile terminal and a mobile terminal, which method comprises: when the mobile terminal is installed in a computer, installing the mobile terminal as a virtual compact disc (CD) of the computer; automatically running an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; and driving the mobile terminal using the driver. The present invention can achieve the self-starting of the mobile terminal, thus achieving the technical effect of facilitating use of user.(String), 本发明公开了一种移动终端自启动方法、装置及移动终端,方法包括:当移动终端安装在电脑中时,将移动终端安装为电脑的虚拟光盘; 自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 使用驱动程序驱动移动终端。 本发明能够实现移动终端的自启动,从而达到方便用户使用的技术效果。(String), US13/259777(String), 1274716800(Integer), US20120072902A1(String), 1332345600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 6(Integer), 10(Integer), US20030046447A1 | US20030099147A1 | US20040210897A1 | US20050015540A1 | US20090119445A1 | US20090193152A1 | US20100082843A1 | US20110060877A1 | US20130127749A1 | US8296757B2(String), \20230420\4abbd99d35444ee8bd73449a6c7156fd.png(String), 11(Integer), 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 1. A self-starting method for a mobile terminal, comprising:installing the mobile terminal as a virtual CD of a computer when the mobile terminal is installed in the computer;automatically running an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; anddriving the mobile terminal using the driver.(String), 1.根据权利要求9所述的移动终端,其中开关模块为通用串行总线单刀双掷开关。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 2. The self-starting method according to claim 1, wherein installing the mobile terminal as a virtual CD of the computer comprises:the mobile terminal reporting itself as the virtual CD to the computer; andthe computer identifying and installing the mobile terminal as the virtual CD.(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 3. The self-starting method according to claim 1, wherein after the installation of the driver and before driving the mobile terminal using the driver, the method further comprises:sending a switch command to the mobile terminal; andthe mobile terminal switching a data path connected to the computer from a first path to a second path in response to the switch command and triggering the computer to re-enumerate a device,wherein, the first path is a default path and is connected to a driver installation module of the mobile terminal, and the second path is connected to a main module of the mobile terminal.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 4. A self-starting apparatus for a mobile terminal, comprising:a driver installation module, configured to, when the mobile terminal is installed in a computer, install the mobile terminal as a virtual CD of the computer and automatically run an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; anda driving module, configured to drive the mobile terminal using the driver.(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 5. The self-starting apparatus according to claim 4, wherein the apparatus further comprises:a switch command sending module, configured to send a switch command to a switching module according to the driver installation result of the driver installation module; andthe switching module, configured to switch a data path connecting the mobile terminal to the computer from a first path to a second path in response to the switch command and trigger the computer to re-enumerate a device,wherein, the first path is a default path and is connected to an automatic installation program of the mobile terminal, and the second path is connected to a main module of the mobile terminal.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 6. The self-starting apparatus according to claim 5, wherein the driver installation module and the switching module are located in the mobile terminal, and the switch command sending module and the driving module are installed in the computer while installing the driver.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 7. The self-starting apparatus according to claim 5, wherein the switching module is a universal serial bus single-pole double-throw switch.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 8. A mobile terminal comprises a self-starting apparatus, wherein the self-starting apparatus comprises:a driver installation module, configured to install the mobile terminal as a virtual CD of a computer when the mobile terminal is installed in the computer, and automatically run an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; anda driving module, configured to drive the mobile terminal using the driver.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 9. The mobile terminal according to claim 8, wherein the self-starting apparatus further comprises:a switch command sending module, configured to send a switch command to a switching module according to the driver installation result of the driver installation module; andthe switching module, configured to switch a data path connecting the mobile terminal to the computer from a first path to a second path in response to the switch command and trigger the computer to re-enumerate a device,wherein the first path is a default path and is connected to an automatic installation program of the mobile terminal, and the second path is connected to a main module of the mobile terminal.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 10. The mobile terminal according to claim 9, wherein the driver installation module and the switching module are located in the mobile terminal, and the switch command sending module and the driving module are installed in the computer while installing the driver.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184983(Integer), 11. The mobile terminal according to claim 9, wherein the switching module is a universal serial bus single-pole double-throw switch.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184983(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, and in particular to a self-starting method and apparatus for a mobile terminal as well as a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the popularization of mobile terminal devices, there is an increasing demand for interconnecting a mobile terminal to a computer. Especially those mobile communication card type devices with various standards must cooperate with the computers to finish various functions. [0003]Currently, the self-starting method generally used when a mobile terminal is connected to a computer is: a user installs the driver software of a mobile terminal adapted to the type of the mobile terminal in a computer, and the object of starting the mobile terminal by using the driver software to drive the mobile terminal is achieved when the mobile terminal of this type is connected to the computer. [0004]During the implementation of the present invention, the inventors find that, when a mobile terminal is connected to a computer in relevant art, the self-starting method requires a user to manually install the driver software of the mobile terminal of its type in the computer, which causes the operation to be inconvenient. SUMMARY OF THE INVENTION [0005]An aspect of the present invention is to provide a self-starting method and apparatus for a mobile terminal as well as a mobile terminal, which is capable of solving the technical problem in relevant art that it needs a user to manually install the driver of a mobile terminal in a computer and thus causes the operation to be inconvenient. [0006]A self-starting method for a mobile terminal is provided according to one aspect of the present invention, which method comprises: when a mobile terminal is installed in a computer, installing the mobile terminal as a virtual compact disc (CD) of the computer; automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and driving the mobile terminal using the driver. [0007]A self-starting apparatus for a mobile terminal is further provided according to another aspect of the present invention, which apparatus comprises: a driver installation module for, when a mobile terminal is installed in a computer, installing the mobile terminal as a virtual CD of the computer and automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and a driving module for driving the mobile terminal using the driver. [0008]A mobile terminal comprising a self-starting apparatus is further provided according to still another aspect of the present invention, which self-starting apparatus comprises: a driver installation module for, when a mobile terminal is installed in a computer, installing the mobile terminal as a virtual CD of the computer and automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and a driving module for driving the mobile terminal using the driver. [0009]By virtue of at least one of the above technical solutions of the present invention, the object of self-starting of the mobile terminal is achieved by installing the mobile terminal as the virtual CD of the computer when the mobile terminal is connected to the computer so as to automatically running an automatic installation program in the mobile terminal, thus achieving the technical effect of facilitating the user. BRIEF DESCRIPTION OF THE DRAWINGS [0010]The drawings, provided for further understanding of the present invention and forming a part of the specification, are used to explain the present invention together with embodiments of the present invention rather than to limit the present invention, wherein [0011]FIG. 1 is a flow chart of a self-starting method for a mobile terminal according to a first embodiment of the present invention; [0012]FIG. 2 is a block diagram of a self-starting apparatus for a mobile terminal according to a second embodiment of the present invention; [0013]FIG. 3 is a schematic diagram of the connection of a switching module of a self-starting apparatus for a mobile terminal according to the second embodiment of the present invention; [0014]FIG. 4 is a block diagram of a mobile terminal according to a third embodiment of the present invention; [0015]FIG. 5 is a flowchart of a self-starting method for a mobile terminal according to a fourth embodiment of the present invention; and [0016]FIG. 6 is a block diagram of a self-starting apparatus for a mobile terminal according to the second embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS [0017]A detailed description of the preferred embodiments of the present invention is provided hereinafter with reference to attached drawings. It should be understood that the preferred embodiments described herein are used for illustrating and explaining the present invention only and shall not be used for limiting the protection scope of the present invention. [0018]For the purpose of illustration, certain details are described in the description below, in order to offer a better understanding of the present invention. However, it is apparent, that the present invention can be achieved even without these certain details, and moreover, the following embodiments and the technical features of these embodiments can be combined if there is no conflict, i.e. without departing from the spirit and scope interpreted by the appended claims. First Embodiment [0019]FIG. 1 is a flow chart of a self-starting method for a mobile terminal according to a first embodiment of the present invention. As shown in FIG. 1, when a mobile terminal is connected to a computer, the self-starting method for the mobile terminal according to the first embodiment of the present invention comprises the following steps: [0020]Step S102: installing a mobile terminal as a virtual CD of a computer when the mobile terminal is installed in (also referred to as “connected to”) the computer; [0021]Step S104: automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and [0022]Step S106: driving the mobile terminal using the driver. [0023]The self-starting method for a mobile terminal according to the first embodiment of the present invention achieves the self-starting object of the mobile terminal by installing the mobile terminal as the virtual CD of the computer when the mobile terminal is connected to the computer so as to automatically run an automatic installation program in the mobile terminal, thus avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. [0024]Preferably, installing the mobile terminal as a virtual CD of the computer comprises: the mobile terminal reporting itself as the virtual CD to the computer; and the computer identifying and installing the mobile terminal as the virtual CD. Thus, it can make the operation of the user more convenient. Optionally, the user can manually set the mobile terminal as the virtual CD to enable the computer to identify and install the mobile terminal as the virtual CD. [0025]Preferably, after the installation of the driver and before driving the mobile terminal using the driver, it further comprises: sending a switch command to the mobile terminal; and the mobile terminal switching a data path connected to the computer from a first path to a second path in response to the switch command and triggering the computer to re-enumerate a device, wherein the first path is a default path and is connected to a driver installation module of the mobile terminal, and the second path is connected to a main module of the mobile terminal. [0026]While installing the driver, a switch command sending module is also installed in the computer so as to send to the mobile terminal a switch command of switching between the first path and the second path after the installation of the driver has been finished; and after the installation of the driver has been finished, the computer re-enumerates the mobile terminal as a mobile terminal instead of a virtual CD by the switch between the first path and the second path, thus achieving normal data communication. [0027]The self-starting method for a mobile terminal according to this embodiment enables the mobile terminal to automatically switch to the main module after the installation of the driver has been finished by switching from the first path to the second path after the installation of the driver has been finished, thus achieving the self-starting of the mobile terminal. Since the self-starting method for a mobile terminal according to the embodiments of the present invention achieves the self-starting of a mobile terminal by switching from a first path which is connected to the driver installation module to a second path which is connected to the main module of the mobile terminal after the installation of the driver has been finished, the achievement of the self-starting function of the self-starting method for a mobile terminal according to the embodiments of the present invention is irrelevant to whether the main module of the mobile terminal supports the function of reporting it as a virtual CD, and therefore it solves the technical problem in relevant art that the self-starting function of a mobile terminal depends on the support of the main module for self-starting function, thus reducing the dependence of the self-starting function upon the main module of the mobile terminal. [0028]Additionally, if it is not the first time that the mobile terminal is connected to the computer, i.e. the driver of this mobile terminal or a mobile terminal of this type is already installed in the computer, and since the first path is a default path, the command sending module directly sends to the mobile terminal a switch command of switching between the first path and the second path so as to enable the computer to re-enumerate the mobile terminal as a mobile terminal instead of a virtual CD, thus achieving normal data communication. [0029]Preferably, sending a switch command to the mobile terminal comprises: enabling a command-sending flag; and sending a switch command according to the command-sending flag. After the command sending module has been installed, it actively detects the command-sending flag which marks whether the installation of the driver is finished or not, if the command-sending flag is in the enabled state, then it indicates that the installation of the driver is finished and the command sending module sends a switch command to the mobile terminal, and if the command-sending flag is not enabled, then it indicates that the installation of the driver is not yet finished and the command sending module continues the detection. Thus, the self-starting function of the mobile terminal is achieved. [0030]The self-starting method for a mobile terminal according to the first embodiment of the present invention achieves the self-starting object of a mobile terminal by installing the mobile terminal as a virtual CD of a computer when the mobile terminal is connected to the computer so as to automatically run an automatic installation program in the mobile terminal and to install the driver of the mobile terminal in the computer, thereby avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. Second Embodiment [0031]FIG. 2 is a block diagram of a self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention. As shown in FIG. 2, the self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention comprises: a driver installation module 202, configured to install the mobile terminal as a virtual CD of a computer when installing the mobile terminal in the computer, and automatically run an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and a driving module 204, configured to drive the mobile terminal using the driver. [0032]The self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention achieves the self-starting object of the mobile terminal by using a driver installation module 202 to install the mobile terminal as the virtual CD of a computer when the mobile terminal is connected to the computer and automatically running the automatic installation program in the mobile terminal, thereby avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. [0033]In this embodiment, the driver installation module can be a mass storage device with self-starting function, or can be other devices with self-starting function. [0034]Preferably, as shown in FIG. 6, the self-starting apparatus 200 further comprises: a switch command sending module 206, configured to send a switch command according to the driver installation result of the driver installation module 202; and a switching module 208, configured to switch a data path connected to the computer from a first path to a second path in response to the switch command and trigger the computer to re-enumerate a device, wherein the first path is a default path and is connected to the driver installation module of the mobile terminal, while the second path is connected to a main module of the mobile terminal. [0035]The self-starting apparatus 200 for a mobile terminal according to this embodiment enables the mobile terminal to automatically switch to the main module by using the switching module 208 to switch from the first path to the second path after the installation of the driver has been finished, thus achieving the self-starting of the mobile terminal. Since the self-starting apparatus 200 of this embodiment reports the mobile terminal as a virtual CD and automatically runs the driver installation program by the driver installation module 202 to which the first path is connected and then switches the data path to the second path which is connected to the main module of the mobile terminal only after the installation of the driver has been finished, the achievement of the self-starting function of the self-starting apparatus 200 of this embodiment is irrelevant to whether the main module of the mobile terminal supports the function of reporting it as a virtual CD, and therefore it solves the technical problem in relevant art that the self-starting function of a mobile terminal depends on the support of the main module for self-starting function, thus reducing the dependence of the self-starting function upon the main module of the mobile terminal. [0036]While installing the driver, a switch command sending module 206 is also installed in the computer to send a switch command of switching between the first path and the second path to the mobile terminal after the installation of the driver has been finished; and the computer re-enumerates the mobile terminal as a mobile terminal instead of a virtual CD after the installation of the driver has been finished by switching between the first path and the second path, thus achieving normal data communication. [0037]Additionally, if it is not the first time that the mobile terminal is connected to the computer, i.e. the driver of the mobile terminal or a mobile terminal of this type is already installed in the computer, since the first path is a default path, the switch command sending module 206 directly sends a switch command of switching between the first path and the second path to the mobile terminal so as to enable the computer to re-enumerate the mobile terminal as a mobile terminal instead of a virtual CD, thus achieving normal data communication. [0038]Preferably, the switch command sending module 206 includes: a command-sending flag enabling unit, configured to enable a command-sending flag; and a command sending unit, configured to send a switch command to the switching module 208 according to the command-sending flag. The command sending flag enabling unit enables the command-sending flag after the installation of the driver has been finished, and after the installation of the switch command sending module 206 has been finished, the command sending module actively detects the command-sending flag, if the command-sending flag is enabled, then it indicates that the installation of the driver is finished and the command sending module sends a switch command to the mobile terminal, and if the command sending flag is not enabled, then it indicates that the installation of the driver is not yet finished and the command sending module continues the detection. Thus, the self-starting function of the mobile terminal is achieved. [0039]Preferably, the driver installation module 202 and the switching module 208 are located in the mobile terminal, while the switch command sending module 206 and the driving module 204 are installed in the computer while installing the driver. They cooperate with each other to finish the self-starting of the mobile terminal. [0040]Preferably, the switching module 208 is a USB single-pole double-throw switch, as shown in FIG. 3. The single-pole double-throw switch can decide whether to switch the data path to the first path which is connected to the driver installation module 202 or to the second path which is connected to the main module of the mobile terminal by judging the level of its selected pin. Thus, the switch between data paths can be achieved, thus achieving normal data communication. [0041]The self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention uses the driver installation module 202 to install a mobile terminal as a virtual CD of a computer when the mobile terminal is connected to the computer and automatically runs an automatic installation program in the mobile terminal so as to install the driver in the computer and then achieves the self-starting of the mobile terminal by switching the data path from the driver installation module 202 to the main module, thus avoiding the inconvenience caused requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. Third Embodiment [0042]FIG. 4 is a block diagram of a mobile terminal according to a third embodiment of the present invention. As shown in FIG. 4, a mobile terminal 400 according to the third embodiment of the present invention comprises a self-starting apparatus 200 for a mobile terminal and a main module 404 shown in FIG. 2 or FIG. 6. [0043]Preferably, the mobile terminal is a WiMax terminal. As to the WiMax terminal, since its built-in WiMax main chip does not support to report it as a virtual CD, the self-starting function of the terminal is finished with the assistance of arranging a self-starting apparatus according to the embodiments of the present invention in this mobile terminal. [0044]The mobile terminal according to this embodiment enables the mobile terminal to automatically switch to the main module 404 after the installation of the driver has been finished by using the switching module 208 to switch from the first path to the second path after the installation of the driver has been finished, thus achieving the self-starting of the mobile terminal. Since the mobile terminal according to the embodiment of the present invention reports a mobile terminal as a virtual CD by the driver installation module 202 connected to the first path, automatically runs the driver installation program, and switches the data path to the second path which is connected to the main module 404 of the mobile terminal after the installation of the driver has been finished, the achievement of the self-starting function of the mobile terminal according to the embodiment of the present invention is irrelevant to whether the main module 404 of the mobile terminal supports the function of reporting it as a virtual CD, and therefore it solves the technical problem in relevant art that the self-starting function of a mobile terminal depends on the support of the main module 404 for self-starting function, thus reducing the dependence of the self-starting function upon the main module 404 of the mobile terminal. [0045]The mobile terminal according to the third embodiment of the present invention performs self-starting using a self-starting apparatus, thus avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. Fourth Embodiment [0046]FIG. 5 is a flowchart of a self-starting method for a mobile terminal according to a fourth embodiment of the present invention. As shown in FIG. 5, the self-starting method for a mobile terminal when it is connected to a computer according to the fourth embodiment of the present invention comprises the following steps, [0047]Step S502: when a mobile terminal is installed in a computer, it is judged whether it is the first time that the mobile terminal is connected to the computer, if it is, then step S504 is performed, otherwise step S508 is performed. [0048]Step S504: the driver installation module reports the mobile terminal as a CDROM (Compact Disk Read Only Memory), and the system automatically performs the installation of an installation package according to autorun.inf and enables a command-sending flag by using a command-sending flag enabling unit installed simultaneously during the installation of the driver. [0049]Step S506: a command sending module which has already been installed at the computer side detects the enabling flag, if it is enabled, then proceed to step S508, and if it is not enabled, then continue the detection. [0050]Step S508: the command sending module sends a switch command. [0051]Step S510: after having received the switch command, the driver installation module at the mobile terminal side resolves the command and sends a switch signal to a USB-switch according to the resolution result. [0052]Step S512: after having received the switch signal, the USB-switch performs the switch of USB data paths and switches the data path from the driver installation module to the main module of the mobile terminal. [0053]Step S514: the computer removes the command sending module installed therein, and re-enumerates device information to obtain the report of the main module of the mobile terminal so as to identify it as a mobile terminal. [0054]The self-starting method for a mobile terminal according to the fourth embodiment of the present invention uses a driver installation module to install a mobile terminal as a virtual CD of a computer and automatically runs the automatic installation program in the mobile terminal so as to install the mobile terminal in the computer and then achieves the self-starting of the mobile terminal by switching the data path from the driver installation module to the main module, thus avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. [0055]As described above, the technical solutions of the present invention can achieve the self-starting of a mobile terminal by using a driver installation module to install the mobile terminal in a computer when it is the first time that the mobile terminal is connected to the computer, thus achieving the technical effect of facilitating the user. [0056]Above description is only to illustrate the preferred embodiments but not to limit the present invention. Any amendments, equivalent substitutions, improvements and etc. within the spirit and principle of the present invention are all included in the scope of the present invention.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的自启动方法、装置及移动终端。 发明背景 [0002] 随着移动终端设备的普及,移动终端与计算机互联的需求越来越大。 尤其是各种制式的移动通讯卡类设备,必须配合电脑才能完成各种功能。 [0003] 目前,移动终端与电脑连接时一般采用的自启动方法是:用户在电脑中安装适配移动终端类型的移动终端驱动软件,启动移动终端的对象 该类移动终端与电脑连接时,通过驱动软件驱动移动终端即可实现。 [0004] 发明人在实施本发明的过程中发现,相关技术中移动终端与计算机连接时,自启动方法需要用户在计算机中手动安装该类型移动终端的驱动软件。 ,导致操作不便。 发明内容 [0005] 本发明的一方面在于提供一种移动终端的自启动方法、装置及移动终端,能够解决相关技术中需要用户手动安装驱动程序的技术问题。 移动终端在电脑上,造成操作不便。 [0006] 根据本发明的一个方面,提供了一种移动终端的自启动方法,该方法包括: 当移动终端安装在计算机中时,将移动终端安装为计算机的虚拟光盘(CD); 自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 使用驱动程序驱动移动终端。 [0007] 根据本发明的另一方面,还提供了一种移动终端的自启动装置,该装置包括: 驱动安装模块,用于在计算机安装移动终端时,将移动终端安装为计算机的虚拟光盘。 电脑自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 以及驱动模块,用于使用驱动程序驱动移动终端。 [0008] 根据本发明的再一方面,还提供了一种包括自启动装置的移动终端,该自启动装置包括: 驱动安装模块,用于在计算机中安装移动终端时,将移动终端安装为 计算机的虚拟光盘,自动运行虚拟光盘中的自动安装程序,在计算机中安装移动终端的驱动程序; 以及驱动模块,用于使用驱动程序驱动移动终端。 [0009] 通过本发明的上述至少一种技术方案,实现了移动终端在连接电脑时将移动终端安装为电脑的虚拟光盘,从而实现了移动终端自启动的目的。 在移动终端中自动运行自动安装程序,达到方便用户的技术效果。 附图的简要说明 [0010] 附图为使本发明进一步理解而构成说明书的一部分,与本发明的实施例一起用于解释本发明,并不用于限制本发明,其中 [0011] 图1为本发明第一实施例的移动终端自启动方法的流程图; [0012] 图2为本发明第二实施例的移动终端自启动装置框图; [0013]图3为本发明实施例二的移动终端自启动装置的切换模块的连接示意图; [0014] 图4是本发明第三实施例的移动终端的框图; [0015] 图5为本发明第四实施例的移动终端自启动方法的流程图; 和 [0016] 图6为本发明第二实施例的移动终端自启动装置的框图。 具体实施方式 [0017] 下面结合附图对本发明的优选实施例进行详细说明。 应当理解,此处所描述的优选实施例仅用于说明和解释本发明,并不用于限定本发明的保护范围。 [0018] 为了说明的目的,在下面的描述中描述了一些细节,以便提供对本发明更好的理解。 然而,显而易见的是,即使没有这些特定细节也可以实现本发明,而且,在不冲突的情况下,即在不脱离所解释的精神和范围的情况下,可以组合以下实施例和这些实施例的技术特征 通过所附权利要求。 第一实施例 [0019] 图1为本发明第一实施例的移动终端自启动方法的流程图。 如图1所示,当移动终端与计算机连接时,本发明第一实施例的移动终端自启动方法包括以下步骤: [0020] 脚步 102 :当移动终端安装在(也称为“连接到”)计算机中时,将移动终端安装为计算机的虚拟CD; [0021] 脚步 104 :自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 和 [0022] 脚步 106 :使用驱动驱动移动端。 [0023] 本发明第一实施例的移动终端自启动方法,通过在移动终端与计算机连接时,将移动终端安装为计算机的虚拟光盘,实现了移动终端自启动的目的,因此 在移动终端中自动运行自动安装程序,避免了移动终端与电脑连接时需要用户手动安装驱动带来的不便,达到了方便用户的技术效果。 [0024] 优选地,将移动终端安装为计算机的虚拟光盘包括: 移动终端向计算机报告自身为虚拟光盘; 计算机将移动终端识别为虚拟光盘安装。 从而可以使用户的操作更加方便。 可选的,用户可以手动将移动终端设置为虚拟光盘,使计算机能够识别并安装移动终端为虚拟光盘。 [0025] 优选地,在安装驱动之后,在使用驱动驱动移动终端之前,还包括: 向移动终端发送切换命令; 移动终端响应于切换命令将与计算机连接的数据路径从第一路径切换到第二路径,并触发计算机重新枚举设备,其中,第一路径为默认路径,连接到 移动终端驱动安装模块,第二路径连接移动终端主模块。 [0026]在安装驱动的同时,计算机中还安装有切换命令发送模块,用于在驱动安装完成后向移动终端发送切换第一路径和第二路径的切换命令; 驱动安装完成后,计算机通过第一路径和第二路径的切换,将移动终端重新枚举为移动终端,而不是虚拟光盘,从而实现正常的数据通信。 [0027] 本实施例的移动终端自启动方法通过在驱动安装完成后从第一路径切换到第二路径,使得移动终端在驱动安装完成后自动切换到主模块。 完成,从而实现移动终端的自启动。 由于本发明实施例的移动终端自启动方法是通过从连接驱动安装模块的第一路径切换到连接驱动安装模块的第二路径实现移动终端自启动的。 驱动安装完成后的移动终端主模块,本发明实施例的移动终端自启动方法的自启动功能的实现与主模块是否安装无关。 移动终端支持虚拟光盘上报功能,解决了相关技术中移动终端的自启动功能依赖于主模块对自启动功能的支持的技术问题,减少了 自启动功能对移动终端主模块的依赖。 [0028] 另外,如果移动终端不是第一次连接电脑,即电脑中已经安装了该移动终端或该类型移动终端的驱动,由于第一路径为默认路径, 命令发送模块直接向移动终端发送切换第一路径和第二路径的切换命令,使得计算机将移动终端重新枚举为移动终端而不是虚拟CD,从而实现正常数据 沟通。 [0029] 优选地,向移动终端发送切换命令包括:​​ 使能命令发送标志; 根据命令发送标志发送切换命令。 命令发送模块安装完成后,会主动检测标记驱动安装是否完成的命令发送标志,如果命令发送标志为使能状态,则表示驱动安装完成。 驱动完成,指令发送模块向移动终端发送切换指令,若指令发送标志位未开启,则表示驱动尚未安装完成,指令发送模块继续检测。 从而实现了移动终端的自启动功能。 [0030] 本发明第一实施例的移动终端自启动方法通过在移动终端与计算机连接时将移动终端安装为计算机的虚拟光盘来实现移动终端自启动的目的,因此 在移动终端中自动运行自动安装程序,在电脑中安装移动终端的驱动程序,避免了移动终端与电脑连接时需要用户手动安装驱动程序带来的不便, 达到方便用户的技术效果。 第二实施例 [0031] 图2是自启动装置的框图 200 用于根据本发明第二实施例的移动终端。 如图2所示,自启动装置 200 本发明实施例二提供的一种移动终端,包括:驱动安装模块 202、用于在电脑中安装移动终端时将移动终端作为电脑的虚拟光盘安装,并自动运行虚拟光盘中的自动安装程序,以在电脑中安装移动终端的驱动程序; 和一个驱动模块 204 ,配置为使用驱动程序驱动移动终端。 [0032] 自启动装置 200 本发明实施例二的移动终端通过驱动安装模块实现移动终端自启动的目的 202 当移动终端与电脑连接时,将移动终端作为电脑的虚拟光盘进行安装,自动运行移动终端中的自动安装程序,避免了移动终端需要用户手动安装驱动带来的不便。 终端与电脑连接,达到方便用户使用的技术效果。 [0033] 在本实施例中,驱动安装模块可以是具有自启动功能的大容量存储设备,也可以是其他具有自启动功能的设备。 [0034] 优选地,如图6所示,自启动装置 200 还包括:开关命令发送模块 206 ,配置为根据驱动安装模块的驱动安装结果发送切换命令 202 ; 和一个开关模块 208 ,用于响应于切换命令将连接计算机的数据路径从第一路径切换到第二路径,并触发计算机重新枚举设备,其中,第一路径为默认路径,连接驱动程序 移动终端的安装模块,而第二路径连接移动终端的主模块。 [0035] 自启动装置 200 本实施例的移动终端通过切换模块实现移动终端自动切换到主模块 208 驱动安装完成后从第一路径切换到第二路径,从而实现移动终端的自启动。 自启动装置 200 本实施例将移动终端上报为虚拟光盘,驱动安装模块自动运行驱动安装程序 202 连接第一条路径,然后在驱动安装完成后,将数据路径切换到连接移动终端主模块的第二条路径,实现自身的自启动功能 -启动装置 200 本实施例与移动终端主模块是否支持虚拟光盘上报功能无关,解决了相关技术中移动终端自启动功能依赖于上报虚拟光盘功能的技术问题。 自启动功能的主模块,减少了自启动功能对移动终端主模块的依赖。 [0036] 安装驱动时,开关命令发送模块 206 还安装在电脑中,用于在驱动安装完成后向移动终端发送切换第一路径和第二路径的切换命令; 计算机通过在第一路径和第二路径之间切换,驱动安装完成后,将移动终端重新枚举为移动终端,而不是虚拟光盘,从而实现正常的数据通信。 [0037] 另外,如果移动终端不是第一次连接电脑,即电脑中已经安装了移动终端的驱动程序或此类移动终端,由于第一条路径为默认路径,则 开关命令发送模块 206 直接向移动终端发送切换第一路径和第二路径的切换命令,使得计算机将移动终端重新枚举为移动终端,而不是虚拟CD,从而实现正常的数据通信。 [0038] 优选地,所述开关命令发送模块 206包括: 命令发送标志使能单元,用于使能命令发送标志; 命令发送单元,用于向切换模块发送切换命令 208 根据命令发送标志。 命令发送标志使能单元在驱动安装完成后,开关命令发送模块安装完成后,使能命令发送标志。 206 完成后,命令发送模块主动检测命令发送标志位,若命令发送标志位开启,则表示驱动安装完成,命令发送模块向移动终端发送切换命令, 如果命令发送标志位没有开启,则说明驱动尚未安装完成,命令发送模块继续检测。 从而实现了移动终端的自启动功能。 [0039] 优选的,驱动安装模块 202 和开关模块 208 位于移动端,而开关命令发送模块 206 和驱动模块 204 在安装驱动程序的同时安装在计算机中。 它们相互配合完成移动终端的自启动。 [0040] 优选地,切换模块 208 是一个USB单刀双掷开关,如图3所示。单刀双掷开关可以决定是否将数据路径切换到连接驱动安装模块的第一条路径 202 或者通过判断其选择引脚的电平,连接到移动终端主模块的第二条路径。 从而实现数据路径之间的切换,从而实现正常的数据通信。 [0041] 自启动装置 200 本发明第二实施例的移动终端使用驱动安装模块 202 将移动终端作为电脑的虚拟光盘进行安装,当移动终端与电脑连接时,自动运行移动终端中的自动安装程序,安装电脑中的驱动程序,实现自启动。 移动端通过驱动安装模块切换数据路径 202 避免了移动终端与电脑连接时需要用户手动安装驱动带来的不便,达到了方便用户的技术效果。 第三实施例 [0042] 图4是根据本发明第三实施例的移动终端的框图。 如图4所示,移动终端 400 根据本发明的第三实施例包括自启动装置 200 用于移动终端和主模块 404 如图2或图6所示。 [0043] 优选地,移动终端为WiMax终端。 对于WiMax终端,由于其内置的WiMax主芯片不支持上报为虚拟光盘,根据本发明实施例设置自启动装置辅助完成终端的自启动功能。 本发明在该移动终端中。 [0044] 本实施例的移动终端能够使移动终端自动切换到主模块 404 使用交换模块完成驱动安装后 208 驱动安装完成后从第一路径切换到第二路径,从而实现移动终端的自启动。 由于本发明实施例的移动终端通过驱动安装模块将移动终端上报为虚拟光盘 202 连接到第一条路径,自动运行驱动安装程序,并将数据路径切换到连接到主模块的第二条路径 404 移动终端在驱动安装完成后,本发明实施例的移动终端自启动功能的实现与主模块是否完成无关。 404移动终端支持虚拟光盘上报功能,解决了相关技术中移动终端自启动功能依赖于主模块支持的技术问题 404 用于自启动功能,从而减少自启动功能对主模块的依赖 404 的移动终端。 [0045] 本发明实施例三的移动终端通过自启动装置进行自启动,避免了移动终端连接电脑时需要用户手动安装驱动带来的不便,实现了 方便用户的技术效果。 第四实施例 [0046] 图5为本发明第四实施例的移动终端自启动方法的流程图。 如图5所示,本发明第四实施例的移动终端连接电脑自启动的方法包括以下步骤, [0047] 脚步 502 :当移动终端安装在电脑上时,判断移动终端是否是第一次连接电脑,如果是,则步骤S 504 执行,否则执行步骤S 508 被执行。 [0048] 脚步 504 :驱动安装模块将移动端上报为CDROM(Compact Disk Read Only Memory),系统根据autorun.inf自动进行安装包的安装,并通过命令发送标志启用命令发送标志 在安装驱动程序的过程中同时安装启用单元。 [0049] 脚步 506 :计算机端已经安装的命令发送模块检测启用标志,如果启用,则进行步骤S 508 ,如果没有启用,则继续检测。 [0050] 脚步 508 :命令发送模块发送切换命令。 [0051] 脚步 510 :移动终端侧的驱动安装模块接收到开关命令后,对该命令进行解析,并根据解析结果向USB-switch发送开关信号。 [0052] 脚步 512 :USB-switch接收到切换信号后,进行USB数据路径的切换,将数据路径从驱动安装模块切换到移动终端主模块。 [0053] 脚步 514 :计算机移除安装在其中的命令发送模块,重新枚举设备信息得到移动终端主模块的上报,从而识别为移动终端。 [0054] 本发明第四实施例的移动终端自启动方法采用驱动安装模块安装移动终端作为计算机的虚拟光盘,自动运行移动终端中的自动安装程序进行安装 移动终端在电脑中,然后通过将数据路径从驱动安装模块切换到主模块,实现移动终端的自启动,避免了移动终端需要用户手动安装驱动带来的不便。 与电脑连接,达到方便使用者的技术效果。 [0055] 综上所述,本发明技术方案在移动终端首次连接电脑时,通过驱动安装模块将移动终端安装到电脑中,实现了移动终端的自启动。 ,从而达到方便用户的技术效果。 [0056] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明保护的范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101576863A(String), CN101576863B(String), DE202010017805U1(String), DK201200117U1(String), DK201200117U4(String), DK201200117W(String), EP2439649A1(String), EP2439649A4(String), US20120072902A1(String), WO2010139246A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101576863A(String), CN101576863B(String), DE202010017805U1(String), DK201200117U1(String), DK201200117U4(String), DK201200117W(String), EP2439649A1(String), EP2439649A4(String), US20120072902A1(String), WO2010139246A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120072902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101576863A(String), CN101576863B(String), DE202010017805U1(String), DK201200117U1(String), DK201200117U4(String), DK201200117W(String), EP2439649A1(String), EP2439649A4(String), US20120072902A1(String), WO2010139246A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), CN101576863A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), CN101576863B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), DE202010017805U1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), DK201200117U1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), DK201200117U4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), DK201200117W(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), EP2439649A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), EP2439649A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), US20120072902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270665(Integer), WO2010139246A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120072902A1(String), US20120072902A1(String), 1332345600(Integer), 270665(Integer), 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184983(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184983(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.475 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.475 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.475 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184983(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184983(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130246051A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for reducing call consumption of mobile terminal(String), 减少移动终端通话消耗的方法及移动终端(String), US20130246051A1(String), A method for reducing call power consumption of a mobile terminal and mobile terminal are disclosed in the present invention, wherein, the method includes: in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of the user; if not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal. With the present invention, voice call power consumption of the mobile terminal is reduced, battery usage time of the mobile terminal is extended, and user experience is enhanced.(String), 本发明公开了一种降低移动终端通话功耗的方法及移动终端,其中,该方法包括:在语音通话过程中,移动终端对移动终端自身采集的音频信号进行声纹建模, 获取声纹模型,判断获取的声纹模型与存储的用户声纹模型是否匹配; 如果不匹配,则放弃对采集的音频信号进行无线传输或放弃对采集的音频信号进行基带和射频处理和无线传输,如果匹配,则对音频信号进行基带和射频处理和无线传输 . 通过本发明,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。(String), US13/641808(String), 1307980800(Integer), US20130246051A1(String), 1379520000(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 15(Integer), US20030061036A1 | US20040138890A1 | US20050102134A1 | US20060074658A1 | US20080211641A1 | US20080255842A1 | US20080312924A1 | US20090094029A1 | US20090119106A1 | US6453285B1 | US7016834B1 | US7231019B2 | US7260724B1 | US7567827B2 | US7664636B1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184984(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f6f8a9090d9e4b479c4f055536809e69.png(String), 184984(Integer), f6f8a9090d9e4b479c4f055536809e69.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for reducing call consumption of mobile terminal(String), 减少移动终端通话消耗的方法及移动终端(String), US20130246051A1(String), A method for reducing call power consumption of a mobile terminal and mobile terminal are disclosed in the present invention, wherein, the method includes: in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of the user; if not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal. With the present invention, voice call power consumption of the mobile terminal is reduced, battery usage time of the mobile terminal is extended, and user experience is enhanced.(String), 本发明公开了一种降低移动终端通话功耗的方法及移动终端,其中,该方法包括:在语音通话过程中,移动终端对移动终端自身采集的音频信号进行声纹建模, 获取声纹模型,判断获取的声纹模型与存储的用户声纹模型是否匹配; 如果不匹配,则放弃对采集的音频信号进行无线传输或放弃对采集的音频信号进行基带和射频处理和无线传输,如果匹配,则对音频信号进行基带和射频处理和无线传输 . 通过本发明,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。(String), US13/641808(String), 1307980800(Integer), US20130246051A1(String), 1379520000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 15(Integer), US20030061036A1 | US20040138890A1 | US20050102134A1 | US20060074658A1 | US20080211641A1 | US20080255842A1 | US20080312924A1 | US20090094029A1 | US20090119106A1 | US6453285B1 | US7016834B1 | US7231019B2 | US7260724B1 | US7567827B2 | US7664636B1(String), \20230420\f6f8a9090d9e4b479c4f055536809e69.png(String), 14(Integer), 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 1. A method for reducing call power consumption of a mobile terminal, comprising:in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user; andif not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 1.根据权利要求2所述的方法,其中:当存储有多个用户声纹模型时,如果移动终端判断移动终端采集到的音频信号与多个用户声纹模型中的任何一个都不匹配,则移动终端放弃对采集到的语音信号进行无线传输音频信号或者放弃对采集到的音频信号进行基带和射频处理以及无线传输,如果移动终端判断移动终端采集到的音频信号与用户的多种声纹模型中的至少一种相匹配,则移动终端对音频信号进行基带和射频处理及无线传输。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 2. The method according to claim 1, wherein:an establishment way of the stored voiceprint model of the user is any one or two of the following ways:before the voice call starts, recording a voice segment of a user, and establishing and storing the voiceprint model of the user according to the voice segment;when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, establishing and storing the voiceprint model of the user.(String), 12.根据权利要求2所述的方法,其中:存储的用户声纹模型包括:普通用户声纹模型和临时用户声纹模型;该方法还包括:将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中;或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 3. The method according to claim 1, wherein:when there are multiple stored voiceprint models of users, if the mobile terminal judges that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, the mobile terminal gives up performing the wireless transmission on the collected audio signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, and if the mobile terminal judges that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of users, the mobile terminal performs the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 13.根据权利要求7所述的移动终端,其中:声纹处理子模块,还用于当存储的用户声纹模型有多个时,当判断移动终端采集的音频信号与多个用户声纹模型中的任意一个不匹配时,确定获取的声纹模型与用户预存的声纹模型不匹配,当判断移动终端采集的音频信号与用户的多个声纹模型中的至少一个匹配时,确定获取的声纹模型与预存的声纹模型匹配-存储用户的声纹模型。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 4. The method according to claim 1, wherein:the stored voiceprint model of the user comprises: a voiceprint model of a common user and a voiceprint model of a temporary user;the method further comprises: storing the voiceprint model of the common user and the voiceprint model of the temporary user in a non-volatile memory of the mobile terminal; or, storing the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and storing the voiceprint model of the temporary user in a volatile memory of the mobile terminal.(String), 14.根据权利要求7所述的移动终端,其中:存储的用户声纹模型具体包括普通用户声纹模型和临时用户声纹模型,移动终端的存储器包括非易失性存储器和易失性存储器。声纹处理子模块还用于将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中。或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 5. The method according to claim 1, wherein:the step of the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user comprises: when the voice call starts, after receiving a voiceprint model establishment indication sent by the user, the mobile terminal firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process, and judging whether the obtained voiceprint model matches with any of all the stored voiceprint models of users;in the step of giving up performing the wireless transmission on the collected audio signal or giving up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, performing the wireless transmission on the audio signal collected in the subsequent voice call process is given up or performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process is given up.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 6. A mobile terminal for reducing call power consumption, comprising: a memory module and an antenna module, and further comprising: a baseband and radio frequency processing module, wherein, the baseband and radio frequency processing module comprises a voiceprint processing submodule and an audio signal control processing submodule;the memory module is configured to: store a voiceprint model of a user;the voiceprint processing submodule is configured to: in a voice call process, perform voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, judge whether the obtained voiceprint model matches with a stored voiceprint model of the user, and send a judgment result to the audio signal control processing submodule; andthe audio signal control processing submodule is configured to: when the judgment result is not matching, give up performing wireless transmission on the collected audio signal or give up performing baseband and radio frequency processing and wireless transmission on the collected audio signal; and when the judgment result is matching, perform the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 7. The mobile terminal according to claim 6, wherein:the voiceprint processing submodule is further configured to establish the stored voiceprint model of the user in any one or two of the following ways:before a voice call of the mobile terminal starts, according to a voice segment of a user recorded by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal;after the voice call of the mobile terminal starts, and when a voiceprint model establishment indication sent by the user is received, according to the audio signal collected by the mobile terminal, establishing the voiceprint model of the user and storing in the memory of the mobile terminal.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 8. The mobile terminal according to claim 6, wherein:the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 9. The mobile terminal according to claim 6, wherein:the stored voiceprint model of the user specifically comprises a voiceprint model of a common user and a voiceprint model of a temporary user, and the memory of the mobile terminal comprises a non-volatile memory and a volatile memory;the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 10. The mobile terminal according to claim 6, wherein:the voiceprint processing submodule is configured to perform the voiceprint modeling on the audio signal collected by the mobile terminal to obtain the voiceprint model during the voice call process in the following way: when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process to obtain the voiceprint model;the audio signal control processing submodule is configured to give up performing the wireless transmission on the collected audio signal or give up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal in the following way: giving up performing the wireless transmission on the audio signal collected in the subsequent voice call process or giving up performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 11. The method according to claim 2, wherein:when there are multiple stored voiceprint models of users, if the mobile terminal judges that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, the mobile terminal gives up performing the wireless transmission on the collected audio signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, and if the mobile terminal judges that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of users, the mobile terminal performs the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 12. The method according to claim 2, wherein:the stored voiceprint model of the user comprises: a voiceprint model of a common user and a voiceprint model of a temporary user;the method further comprises: storing the voiceprint model of the common user and the voiceprint model of the temporary user in a non-volatile memory of the mobile terminal; or, storing the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and storing the voiceprint model of the temporary user in a volatile memory of the mobile terminal.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 13. The mobile terminal according to claim 7, wherein:the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user.(String), 1(Integer), 12(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184984(Integer), 14. The mobile terminal according to claim 7, wherein:the stored voiceprint model of the user specifically comprises a voiceprint model of a common user and a voiceprint model of a temporary user, and the memory of the mobile terminal comprises a non-volatile memory and a volatile memory;the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184984(Integer), TECHNICAL FIELD [0001]The present invention relates to the field of mobile communication technology, and specifically, the invention relates to a method for reducing call power consumption of a mobile terminal and a mobile terminal. BACKGROUND OF THE RELATED ART [0002]With the rapid development of the communication and microelectronic technology, functions of a mobile phone become richer. Besides a traditional voice call function, various functions such as video call, photograph, camera shooting, recording, music play, video play, mobile TV, net play and JAVA games and so on are integrated, and the power consumption is comparatively high when these functions are used. Currently, lithium ion battery is used to power most mobile phones. Capacity of the lithium ion battery is usually small, but mobile phone users often expect that the battery can be used for a long time after one time of charging, so a contradiction between fast electricity consumption of mobile phone and limited battery capacity is caused. How to reduce the power consumption of the mobile phone to extend the usage time of the battery after one-time charging becomes an important task. In the study of reducing the power consumption of the mobile phone, the voice call service becomes the most important aspect in the task of reducing the power consumption of the mobile phone as the voice call service is used frequently and has high power consumption. [0003]As shown in FIG. 1, the existing uplink data transmission flow of mobile phone voice calls is: an audio signal collected through an MIC of a mobile terminal going through the analog amplification processing (such as three-level analog amplification processing), then being converted through an Analog-to-Digital Converter, which is also called as an AD converter, into a Pulse-code modulation (PCM) numerical code stream, being processed through an audio frequency algorithm, then being filtered through an equalizer, then audio frequency Adaptive Multi-Rat (AMR) coding being performed after a digital gain, and finally being transmitted out through a radio frequency after going through processing such as channel coding and modulation and so on. SUMMARY OF THE INVENTION [0004]In a normal condition, making a call is an interaction process between the two parties, wherein one party always speaks in a certain time and listens to the other party in a certain time, therefore, voices required to be transmitted through mobile phones and networks are discontinuous. However, the environment of voice calls is relatively complicated, as besides the voice of a caller himself, voices of other people and other environmental noises around always exist. Although the existing audio algorithm has echo suppression and noise suppression, it can only perform the noise suppression processing on the voices when the caller is speaking. When the caller is not speaking, other voices in the ambient environment are still taken as valid data to be processed and transmitted, so no matter whether the caller is speaking or not, the voices processed and transmitted by the audio frequency algorithm are always continuous. It causes that a great quantity of unwanted voice data are collected, processed and transmitted by the mobile phones and the system needs to process a great quantity of additional data, which brings large power consumption of the baseband and radio frequency. [0005]The object of the present invention is to provide a method and mobile terminal for reducing call power consumption of the mobile terminal, to solve the problem of how to reduce the power consumption of voice calls, save the battery electricity consumption of the mobile terminal, and reduce the transmission of invalid data. [0006]In order to solve the above technical problem, the present invention provides a method for reducing call power consumption of a mobile terminal, which comprises: [0007]in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user; and [0008]if not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal. [0009]In the method of the present invention, an establishment way of the stored voiceprint model of the user is any one or two of the following ways: [0010]before the voice call starts, recording a voice segment of a user, and establishing and storing the voiceprint model of the user according to the voice segment; [0011]when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, establishing and storing the voiceprint model of the user. [0012]In the method of the present invention, when there are multiple stored voiceprint models of users, if the mobile terminal judges that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, the mobile terminal gives up performing the wireless transmission on the collected audio signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, and if the mobile terminal judges that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of users, the mobile terminal performs the baseband and radio frequency processing and wireless transmission on the audio signal. [0013]In the method of the present invention, the stored voiceprint model of the user comprises: a voiceprint model of a common user and a voiceprint model of a temporary user; [0014]the method further comprises: storing the voiceprint model of the common user and the voiceprint model of the temporary user in a non-volatile memory of the mobile terminal; or, [0015]storing the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and storing the voiceprint model of the temporary user in a volatile memory of the mobile terminal. [0016]In the method of the present invention, the step of the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user comprises: when the voice call starts, after receiving a voiceprint model establishment indication sent by the user, the mobile terminal firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process, and judging whether the obtained voiceprint model matches with any of all the stored voiceprint models of users; [0017]in the step of giving up performing the wireless transmission on the collected audio signal or giving up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, performing the wireless transmission on the audio signal collected in the subsequent voice call process is given up or performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process is given up. [0018]In order to solve the above technical problem, the present invention further provides a mobile terminal for reducing call power consumption, which comprises: a memory module and an antenna module, and further comprises: a baseband and radio frequency processing module, wherein, the baseband and radio frequency processing module comprises a voiceprint processing submodule and an audio signal control processing submodule; [0019]the memory module is configured to: store a voiceprint model of a user; [0020]the voiceprint processing submodule is configured to: in a voice call process, perform voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, judge whether the obtained voiceprint model matches with a stored voiceprint model of the user, and send a judgment result to the audio signal control processing submodule; and [0021]the audio signal control processing submodule is configured to: when the judgment result is not matching, give up performing wireless transmission on the collected audio signal or give up performing baseband and radio frequency processing and wireless transmission on the collected audio signal; and when the judgment result is matching, perform the baseband and radio frequency processing and wireless transmission on the audio signal. [0022]In the mobile terminal of the present invention, the voiceprint processing submodule is further configured to establish the stored voiceprint model of the user in any one or two of the following ways: [0023]before a voice call of the mobile terminal starts, according to a voice segment of a user recorded by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal; [0024]after the voice call of the mobile terminal starts, and when a voiceprint model establishment indication sent by the user is received, according to the audio signal collected by the mobile terminal, establishing the voiceprint model of the user and storing in the memory of the mobile terminal. [0025]In the mobile terminal of the present invention, the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user. [0026]In the mobile terminal of the present invention, the stored voiceprint model of the user specifically comprises a voiceprint model of a common user and a voiceprint model of a temporary user, and the memory of the mobile terminal comprises a non-volatile memory and a volatile memory; [0027]the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal. [0028]In the mobile terminal of the present invention, the voiceprint processing submodule is configured to perform the voiceprint modeling on the audio signal collected by the mobile terminal to obtain the voiceprint model during the voice call process in the following way: when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process to obtain the voiceprint model; [0029]the audio signal control processing submodule is configured to give up performing the wireless transmission on the collected audio signal or give up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal in the following way: giving up performing the wireless transmission on the audio signal collected in the subsequent voice call process or giving up performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process. [0030]Compared with the related art, with the technical scheme of the present invention, voice call power consumption of the mobile terminal is reduced, battery usage time of the mobile terminal is extended, and user experience is enhanced. Moreover, since transmission of invalid data is reduced, system load is alleviated, effective utilization rate of system resources is improved, and power consumption of the baseband and radio frequency is reduced. BRIEF DESCRIPTION OF DRAWINGS [0031]FIG. 1 is a traditional flow diagram of uplink voice processing of a mobile terminal voice call. [0032]FIG. 2 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in the example of the present invention. [0033]FIG. 3 is a structure diagram of a mobile terminal for reducing call power consumption in the example of the present invention. [0034]FIG. 4 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in one application example. [0035]FIG. 5 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in another application example. [0036]FIG. 6 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in another application example. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0037]In order to make the object, technical scheme and advantages of the present invention more clear, the examples of the present invention will be described in detail in combination with the accompanying drawings below. It should be noted that the examples in the present invention and the characteristics in the examples can be optionally combined with each other in the condition of no conflict. [0038]As shown in FIG. 2, the example of the present invention provides a method for reducing call power consumption of a mobile terminal, a mobile phone is taken as an example, and the method includes following steps. [0039]In S201, when a caller is on the phone, in a voice call process, the mobile phone performs voiceprint modeling on an audio signal collected by the mobile phone itself. [0040]Wherein, the audio signal collected by the mobile phone itself refers to an audio signal collected by the mobile phone through an internal MIC, but not an audio signal received from an opposite terminal through the radio communication. The mobile phone uses the in-built MIC to collect audio signals, and no additional hardware device is required to be added, therefore, the system complexity is not increased, which is simple and practical. [0041]Wherein, in the call process, the operation of performing voiceprint modeling is generally real-time, which is performed in a certain time interval, the time interval can be manually set by a user according to the use demand, and also can be defaulted in the mobile terminal. [0042]The process of performing voiceprint modeling on the voice signal includes: after performing analog amplification, AD conversion and denoising operation on the collected audio signal, extracting voiceprint feature data from the denoised audio data, and then establishing the voiceprint model according to the extracted voiceprint feature data. Extracting the voiceprint feature data refers to extracting acoustic feature data or language feature data such as a cepstrum and so on with strong divisibility and high stability from the denoised audio data. [0043]At the point, the established voiceprint model may be the voiceprint model of the caller, and also may be voiceprint models formed from voices of other speakers in the environment. [0044]In S202, whether the obtained voiceprint model matches with a stored voiceprint model of the user is judged. [0045]The speaker of the current voices can be confirmed through the model matching, and it can be determined whether the extracted voices are the voices of the caller, that is, whether the caller is speaking, and whether the voice data are valid data of the call. [0046]Wherein, an establishment way of the stored voiceprint model of the user is any one or two of the following ways: [0047]before a voice call starts, recording a voice segment of the user, and according to the voice segment, establishing and storing the voiceprint model of the user; [0048]when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, establishing and storing the voiceprint model of the user according to the collected audio signal. [0049]The stored voiceprint model of the user comprises: a voiceprint model of the common user and a voiceprint model of the temporary user, the voiceprint model of the common user and voiceprint model of the temporary user are stored in a non-volatile memory of the mobile terminal; or, the voiceprint model of the common user is stored in the non-volatile memory of the mobile terminal, and the voiceprint model of the temporary user is stored in a one-time memory of the mobile terminal. Generally speaking, the voiceprint model stored in the non-volatile memory of the mobile phone will be saved permanently, and the voiceprint model stored in the one-time memory of the mobile phone or in one data structure will be automatically deleted by the mobile phone after a time and will not be saved permanently. In the above storage modes, the first storage mode is beneficial to guaranteeing the data security, and the second mode is beneficial to saving the storage space of the mobile phone and processing capacity. [0050]In a general application situation, the user using the mobile phone only includes the owner of the mobile phone. When the mobile phone is in a non-call state, the owner of the mobile phone can record the voice segment of the user through the mobile phone, and the voiceprint model of the user can be established and stored according to the voice segment. [0051]In other application situations, the user using the mobile phone not only includes the owner of the mobile phone, but also includes other users. A common user can be the owner of the mobile phone, and a temporary user can be a temporary borrower of the mobile phone. If what the caller is using is not his own mobile phone, or if a situation that the mobile phone needs to be transferred to another person who will talk to the other party of the conversation in the call process occurs, the voiceprint model establishment indication can be sent to the mobile phone in the way of key selection through a menu on the mobile phone during the conversation, and its own voiceprint model is established within a period of time when the conversation just starts and stored in the mobile phone, and is taken as a reference voiceprint model for the subsequent model matching. For example, a certain keypad used to establish and store the voiceprint model of the current caller is set, and then after the current caller presses the keypad, the mobile phone receives the voiceprint model establishment indication sent by the user. The user sends a segment of voice used for modeling after pressing the keypad, and the mobile phone automatically intercepts the voice from the beginning of receiving the voiceprint model establishment indication to a later preset time length (e.g. 10 seconds) so as to establish and store the voiceprint model of the user, or, the user also can control the end time of the voice. For example, after the user sends the segment of voice, the mobile phone is indicated by keypad selection though the menu on the mobile phone during the conversation that the voice for modeling ends, and then the mobile phone establishes and stores the voiceprint model of the user according to the voice from the time of receiving the voiceprint model establishment indication to the time of receiving a voiceprint model establishment end indication. [0052]Certainly, in the specific implementation, other methods also can be used to confirm the common user. For example, a public terminal can determine one or multiple common users and one or multiple temporary users voluntarily. [0053]In the example, the model matching refers to performing similarity matching on the voiceprint model established according to the extracted voiceprint feature data and the voiceprint model stored in the mobile phone. A common method includes: a probability statistics method, a dynamic time warping method and a neural network method and so on. In the specific implementation, whether a matching degree between the voiceprint model established according to the extracted voiceprint feature data and the reference voiceprint model stored in the mobile phone reaches a certain preset threshold can be judged through a distance measurement algorithm. If the matching degree between the voiceprint model established according to the extracted voiceprint feature data and the reference voiceprint model stored in the mobile phone reaches the certain preset threshold, it is matching, and if the matching degree between the voiceprint model established according to the extracted voiceprint feature data and the reference voiceprint model stored in the mobile phone does not reach the certain preset threshold, it is not matching. Generally, the threshold can be adjusted according to the practical situation. [0054]In S203, if not matching, performing wireless transmission on the collected voice signal is given up or performing baseband and radio frequency processing and wireless transmission on the collected voice signal is given up, and if matching, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. [0055]Specifically, in the example, if the matching is determined, it is considered that the extracted voices are the voices of the existing valid user, and the voice data thereof are valid data of the call and required to be processed and transmitted. If the matching is not determined, it is considered that the extracted voices are not the voices of the existing valid user, such as environmental sounds (including mute, or the voices of other people in the environment), and the voice data thereof are not valid data of the call and not required to be processed and transmitted. At the point, the CPU load of a baseband chip of the mobile phone is decreased, a radio frequency is also in a state of no data transmission, and the system power consumption can be reduced. [0056]In practical applications, the mobile phone also may have stored voiceprint models of multiple users. If the mobile terminal judges that the voice signal collected by the mobile terminal itself does not match with any one of the multiple voiceprint models of the users, the mobile terminal gives up performing the wireless transmission on the collected voice signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected voice signal, and if the mobile terminal judges that the voice signal collected by the mobile terminal itself matches with at least one of the multiple voiceprint model of the users, performs the baseband and radio frequency processing and wireless transmission on the voice signal. [0057]In the above example, performing the baseband and radio frequency processing on the voice signal refers to performing processing such as audio algorithm processing, digital equalization processing, digital gain processing, AMR coding processing, channel coding processing, modulation processing and radio frequency processing, etc. on the audio signal. [0058]Correspondingly, as shown in FIG. 3, the example also provides a mobile terminal for reducing call power consumption, and the mobile terminal includes: a memory module, a baseband and radio frequency processing module and an antenna module, wherein, [0059]the memory module includes a volatile memory and a non-volatile memory, and is configured to: store a voiceprint model of the user, wherein, the stored voiceprint model of the user specifically includes a voiceprint model of the common user and a voiceprint model of the temporary user; [0060]the baseband and radio frequency processing module includes a voiceprint processing submodule and an audio signal control processing submodule, wherein, [0061]the voiceprint processing submodule is configured to: in a voice call process, perform voiceprint modeling on an audio signal collected by the mobile terminal, judge whether the obtained voiceprint model matches with the stored voiceprint model of the user, and send a judgment result to the audio signal control processing submodule; [0062]the voiceprint processing submodule is further configured to establish the stored voiceprint model of the user in any one or two of the following ways: before a voice call of the mobile terminal starts, according to a voice segment of a user recorded by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal; after the voice call of the mobile terminal starts, and when a voiceprint model establishment indication sent by the user is received, according to the audio signal collected by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal; [0063]the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user; and [0064]the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal. [0065]The audio signal control processing submodule is configured to: when the judgment result is not matching, give up performing wireless transmission on the collected audio signal or give up performing baseband and radio frequency processing and wireless transmission on the collected audio signal; and when the judgment result is matching, perform the baseband and radio frequency processing and wireless transmission on the audio signal. [0066]The audio signal control processing submodule performing the baseband and radio frequency processing on the audio signal refers to: performing audio algorithm processing, digital equalization processing, digital gain processing, AMR coding processing, channel coding processing, modulation processing and radio frequency processing on the audio signal. [0067]The antenna module is configured to: perform wireless transmission on the voice signal which has gone through the baseband and radio frequency processing. Specific Example 1 [0068]In the specific example 1, an execution mode of establishing and storing a voiceprint model of the user before a call starts is mainly described. As shown in FIG. 4, the specific example includes following steps. [0069]In S301, before the voice call starts, a mobile terminal records a voice segment of a common user A, and according to the voice segment, establishes and stores a voiceprint model of the user A. [0070]In S302, during the voice call, the mobile terminal performs voiceprint modeling on an audio signal collected by the mobile terminal itself. [0071]In S303, whether the obtained voiceprint model matches with the stored voiceprint model of the user A is judged. [0072]In S304, if not matching, step S305 is executed, and if matching, S306 is executed. [0073]In S305, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process is given up, and the flow ends. [0074]In S306, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. Specific Example 2 [0075]In the specific example 2, an execution mode of establishing and storing a voiceprint model of the user after a call starts is mainly described. As shown in FIG. 5, the specific example includes following steps. [0076]In S401, after the voice call starts, a mobile terminal receives a voiceprint model establishment indication sent by a user A, and according to the collected voice signal (i.e. a voice sent after the user presses the voiceprint model establishment indication), establishes and stores a voiceprint model of the user A. [0077]In S402, during the subsequent voice call, the mobile terminal performs voiceprint modeling on a voice signal collected in subsequence. [0078]In S403, whether the obtained voiceprint model matches with the stored voiceprint model of the user is judged. [0079]In S404, if not matching, step S405 is executed, and if matching, S406 is executed. [0080]In S405, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process is given up, and the flow ends. [0081]In S406, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. Specific Example 3 [0082]In the specific example 3, an execution mode that a voiceprint model of the user is required to be established and stored before and after a call starts is mainly described. As shown in FIG. 6, the specific example includes following steps. [0083]In S501, before the voice call starts, a mobile terminal records a voice segment of a common user A, and according to the voice segment, establishes and stores a voiceprint model of the user A. [0084]In S502, during the process of the user A using the mobile phone to make the voice call, the mobile terminal performs voiceprint modeling on an audio signal collected by the mobile terminal itself. [0085]In S503, whether the obtained voiceprint model matches with the stored voiceprint model of the user A is judged. [0086]In S504, if not matching, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process is given up, and if matching, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. [0087]In S505, a temporary user B replaces the user A to make the call with the opposite end in the call process, and sends a voiceprint model establishment indication to the mobile phone by performing key selection through a menu on the mobile phone while talking, the mobile phone establishes and stores a voiceprint model of the user B according to the voice signal collected in subsequence (i.e. a voice sent after the user B presses the voiceprint model establishment indication). Within the time range of the mobile phone establishing the voiceprint model for the user B, the baseband and radio frequency processing and wireless transmission are performed on all the collected audio signals. [0088]In S506, after establishing and storing the voiceprint model of the user B, the mobile phone continues to perform voiceprint modeling on voice signals collected in subsequence. [0089]In S507, whether the obtained voiceprint model matches with the stored voiceprint models of the user A and user B is judged. [0090]In S508, if no one of the stored voiceprint models of the user A and user B is matched, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process(String), 技术领域 [0001] 本发明涉及移动通信技术领域,具体涉及一种降低移动终端通话功耗的方法及移动终端。 相关技术背景 [0002] 随着通信技术和微电子技术的飞速发展,手机的功能越来越丰富。 除了传统的语音通话功能外,还集成了视频通话、拍照、拍照、录音、音乐播放、视频播放、手机电视、网络播放、JAVA游戏等多种功能,这些功能耗电较高 使用函数。 目前,锂离子电池用于为大多数手机供电。 锂离子电池的容量通常较小,而手机用户往往希望电池充一次电就可以使用很长时间,这就造成了手机用电快和电池容量有限的矛盾。 如何降低手机的功耗,延长电池一次充电后的使用时间成为一项重要课题。 在降低手机功耗的研究中,由于语音通话业务使用频率高、功耗大,因此语音通话业务成为降低手机功耗任务中最重要的方面。 [0003] 如图1所示,现有的手机语音通话的上行数据传输流程是:通过移动终端MIC采集的音频信号,经过模拟放大处理(如三级模拟放大处理),然后进行转换 通过Analog-to-Digital Converter,也叫AD转换器,转换成Pulse-code modulation(PCM)数字码流,经过音频算法处理,再经过均衡器滤波,然后音频自适应 Multi-Rat(AMR)编码是经过数字增益后进行的,经过信道编码、调制等处理后,最终通过射频发射出去。 发明内容 [0004] 在正常情况下,通话是双方的一个交互过程,一方总是在一定的时间内说话,而另一方总是在一定的时间内听对方说话,因此,需要通过手机和网络传输的语音是 不连续的。 然而,语音通话的环境比较复杂,除了通话者自己的声音外,周围的其他人的声音和其他环境噪声也始终存在。 现有的音频算法虽然具有回声抑制和噪声抑制功能,但只能对来电者说话时的声音进行噪声抑制处理。 当来电者不说话时,周围环境中的其他声音仍然作为有效数据进行处理和传输,所以无论来电者是否在说话,经过音频算法处理和传输的语音始终是连续的。 这导致手机采集、处理和传输大量不需要的语音数据,系统需要处理大量的附加数据,带来基带和射频的大量功耗。 [0005] 本发明的目的在于提供一种降低移动终端通话功耗的方法及移动终端,解决如何降低语音通话功耗,节省移动终端电池电量,以及 减少无效数据的传输。 [0006] 为了解决上述技术问题,本发明提供了一种降低移动终端通话功耗的方法,包括: [0007] 在语音通话过程中,移动终端对自身采集的音频信号进行声纹建模,得到声纹模型,判断得到的声纹模型与存储的用户声纹模型是否匹配。 和 [0008]不匹配则放弃对采集到的音频信号进行无线传输或放弃对采集到的音频信号进行基带和射频处理无线传输,匹配则对音频信号进行基带和射频处理无线传输 . [0009] 在本发明的方法中,所述用户存储声纹模型的建立方式为以下方式中的任意一种或两种: [0010] 在语音通话开始前,记录用户的语音片段,并根据语音片段建立并存储用户的声纹模型; [0011] 当语音通话开始时,接收到用户发送的声纹模型建立指示后,建立并存储用户的声纹模型。 [0012] 在本发明的方法中,当存储有多个用户声纹模型时,如果移动终端判断出移动终端采集的音频信号与多个用户声纹模型中的任何一个都不匹配,则移动终端给出 停止对采集到的音频信号进行无线传输或者放弃对采集到的音频信号进行基带和射频处理以及无线传输,如果移动终端判断出移动终端采集到的音频信号与以下至少一种匹配 用户的多种声纹模型,移动终端对音频信号进行基带和射频处理及无线传输。 [0013] 在本发明的方法中,所述存储的用户声纹模型包括:普通用户声纹模型和临时用户声纹模型; [0014] 该方法还包括:将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中; 或者, [0015] 将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。 [0016] 在本发明的方法中,所述移动终端对其采集的音频信号进行声纹建模得到声纹模型,并判断得到的声纹模型与存储的用户声纹模型是否匹配包括: 当语音通话开始时,移动终端接收到用户发送的声纹模型建立指示后,首先根据采集到的音频信号建立并存储用户的声纹模型,然后对采集到的音频信号进行声纹建模。 后续的语音通话流程,判断获取的声纹模型是否与所有存储的用户声纹模型匹配; [0017] 所述放弃对采集到的音频信号进行无线传输或者放弃对采集到的音频信号进行基带和射频处理无线传输的步骤中,对后续语音通话过程中采集到的音频信号进行无线传输为 放弃或放弃对后续语音通话过程中采集到的音频信号进行基带和射频处理和无线传输。 [0018] 为了解决上述技术问题,本发明还提供了一种降低通话功耗的移动终端,包括:存储模块和天线模块,还包括:基带和射频处理模块,其中,基带 射频处理模块包括声纹处理子模块和音频信号控制处理子模块; [0019] 存储模块用于存储用户的声纹模型; [0020]声纹处理子模块用于在语音通话过程中,对移动终端采集的音频信号进行声纹建模,得到声纹模型,判断得到的声纹模型与存储的用户声纹模型是否匹配,发送 判断结果给音频信号控制处理子模块; 和 [0021] 音频信号控制处理子模块,用于当判断结果不匹配时,放弃对采集到的音频信号进行无线传输或放弃对采集到的音频信号进行基带和射频处理及无线传输。 当判断结果匹配时,对音频信号进行基带和射频处理及无线传输。 [0022] 在本发明的移动终端中,所述声纹处理子模块还用于通过以下任意一种或两种方式建立所述用户的存储声纹模型: [0023] 在移动终端语音通话开始前,根据移动终端记录的用户的语音片段,建立用户的声纹模型并存储在移动终端的内存中; [0024] 移动终端语音通话开始后,当接收到用户发送的声纹模型建立指示时,根据移动终端采集的音频信号,建立用户的声纹模型并存储在手机内存中 终端。 [0025] 在本发明的移动终端中,所述声纹处理子模块还用于:当存储的用户声纹模型有多个时,当判断移动终端采集的音频信号与所述多个声纹模型中的任意一个不匹配时 的用户,确定获取的声纹模型与预先存储的用户的声纹模型不匹配,当判断移动终端采集的音频信号与用户的多个声纹模型中的至少一个匹配时,确定 获取的声纹模型与预先存储的用户声纹模型匹配。 [0026] 在本发明的移动终端中,存储的用户声纹模型具体包括普通用户声纹模型和临时用户声纹模型,移动终端的存储器包括非易失性存储器和易失性存储器。 记忆; [0027] 声纹处理子模块还用于将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中。 或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。 [0028] 在本发明的移动终端中,声纹处理子模块用于在语音通话过程中对移动终端采集的音频信号进行声纹建模,得到声纹模型:当语音通话开始时, 接收到用户发送的声纹模型建立指示后,首先根据采集到的音频信号建立并存储用户的声纹模型,再对后续语音通话过程中采集到的音频信号进行声纹建模得到 声纹模型; [0029] 音频信号控制处理子模块,用于放弃对采集到的音频信号进行无线传输或者放弃对采集到的音频信号进行基带和射频处理无线传输,具体方式为:放弃对采集到的音频信号进行无线传输。 后续语音通话过程中采集的音频信号或者放弃对后续语音通话过程中采集的音频信号进行基带和射频处理以及无线传输。 [0030]与相关技术相比,采用本发明的技术方案,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。 并且,由于减少了无效数据的传输,减轻了系统负载,提高了系统资源的有效利用率,降低了基带和射频的功耗。 附图说明 [0031] 图1是传统的移动终端语音通话的上行语音处理流程图。 [0032] 图2为本发明实施例中用于降低通话功耗的手机语音通话的上行语音处理流程图。 [0033] 图3为本发明实施例中降低通话功耗的移动终端的结构示意图。 [0034] 图4为一种应用示例中为降低通话功耗而对手机语音通话进行上行语音处理的流程图。 [0035] 图5为另一应用示例中降低通话功耗的手机语音通话的上行语音处理流程图。 [0036] 图6为另一应用示例中降低通话功耗的手机语音通话的上行语音处理流程图。 本发明的优选实施例 [0037] 为使本发明的目的、技术方案及优点更加清楚明白,以下结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本发明中的实施例及实施例中的特征可以相互任意组合。 [0038] 如图2所示,本发明实施例提供了一种降低移动终端通话功耗的方法,以手机为例,该方法包括以下步骤。 [0039] 在 S 201 ,当来电者在通话时,在语音通话过程中,手机对手机自身采集的音频信号进行声纹建模。 [0040] 其中,手机自身采集的音频信号是指手机通过内置MIC采集的音频信号,而不是通过无线通信从对端接收到的音频信号。 该手机采用内置MIC采集音频信号,无需增加额外的硬件设备,不增加系统复杂度,简单实用。 [0041] 其中,在通话过程中,进行声纹建模的操作一般是实时的,以一定的时间间隔进行,该时间间隔可以由用户根据使用需求手动设置,也可以默认为 移动终端。 [0042] 对语音信号进行声纹建模的过程包括:对采集到的音频信号进行模拟放大、AD转换和去噪操作后,从去噪后的音频数据中提取声纹特征数据,然后根据提取的声纹特征建立声纹模型 数据。 提取声纹特征数据是指从降噪后的音频数据中提取可分性强、稳定性高的声学特征数据或语言特征数据,如倒谱等。 [0043] 此时,建立的声纹模型可以是通话方的声纹模型,也可以是环境中其他说话人的声音形成的声纹模型。 [0044] 在 S 202 ,判断获取的声纹模型与存储的用户声纹模型是否匹配。 [0045] 通过模型匹配可以确定当前语音的说话人,判断提取的语音是否为来电方的语音,即来电方是否在说话,语音数据是否为通话的有效数据 . [0046] 其中,用户存储的声纹模型的建立方式为以下方式中的任意一种或两种: [0047] 在语音通话开始前,记录用户的语音片段,并根据语音片段建立并存储用户的声纹模型; [0048] 当语音通话开始时,接收到用户发送的声纹模型建立指示后,根据采集到的音频信号建立并存储用户的声纹模型。 [0049] 存储的用户声纹模型包括:普通用户声纹模型和临时用户声纹模型,普通用户声纹模型和临时用户声纹模型存储在手机的非易失性存储器中 终端; 或者,普通用户的声纹模型存储在移动终端的非易失性存储器中,临时用户的声纹模型存储在移动终端的一次性存储器中。 一般来说,保存在手机非易失性存储器中的声纹模型会永久保存,而保存在手机一次性内存或某种数据结构中的声纹模型会被手机自动删除 一段时间后,将不会永久保存。 在上述存储方式中,第一种存储方式有利于保证数据安全,第二种存储方式有利于节省手机的存储空间和处理能力。 [0050] 在一般的应用情况下,使用手机的用户只包括手机的所有者。 当手机处于非通话状态时,手机主人可以通过手机记录用户的语音片段,根据语音片段建立并存储用户的声纹模型。 [0051] 在其他应用场合,使用手机的用户不仅包括手机的所有者,还包括其他用户。 普通用户可以是手机的主人,临时用户可以是手机的临时借用者。 如果主叫方使用的不是自己的手机,或者在通话过程中出现需要将手机转移给其他人与通话对方通话的情况,声纹模型建立指示可以 在通话过程中通过手机上的菜单以按键选择的方式发送至手机,并在通话刚开始的一段时间内建立自己的声纹模型并存储在手机中,并被提取 作为后续模型匹配的参考声纹模型。 例如,设置用于建立和存储当前主叫方声纹模型的某个键盘,则当前主叫方按下该键盘后,手机接收到用户发送的声纹模型建立指示。 用户按下键盘后发送一段用于建模的语音,手机从收到声纹模型建立指示开始到后面的预设时长(如10秒)自动截取语音,建立并存储 用户的声纹型号,或者,用户还可以控制语音的结束时间。 例如,用户发送一段语音后,在通话过程中通过手机菜单通过键盘选择提示手机建模语音结束,然后手机建立并存储该语音段的声纹模型。 用户根据语音从接收到声纹模型建立指示到接收到声纹模型建立结束指示为止。 [0052] 当然,在具体实现中,也可以采用其他方式对普通用户进行确认。 例如,公共终端可以自行确定一个或多个普通用户和一个或多个临时用户。 [0053]在本实施例中,模型匹配是指将根据提取的声纹特征数据建立的声纹模型与手机中存储的声纹模型进行相似度匹配。 常用的方法有:概率统计法、动态时间规整法和神经网络法等。 具体实施中,可以通过测距算法判断根据提取的声纹特征数据建立的声纹模型与手机中存储的参考声纹模型的匹配度是否达到某个预设阈值。 如果根据提取的声纹特征数据建立的声纹模型与手机中存储的参考声纹模型的匹配度达到一定的预设阈值,则匹配,如果根据提取的声纹特征数据建立的声纹模型之间的匹配度 声纹特征数据与手机中存储的参考声纹模型没有达到一定的预设阈值,不匹配。 一般来说,阈值可以根据实际情况进行调整。 [0054] 在 S 203 ,如果不匹配,则放弃对采集到的语音信号进行无线传输或者放弃对采集到的语音信号进行基带和射频处理,无线传输,如果匹配,则进行基带和射频处理,无线传输 在语音信号上。 [0055] 具体地,在该示例中,如果确定匹配,则认为提取的语音是现有有效用户的语音,其语音数据是呼叫的有效数据,需要处理和传输。 如果不匹配,则认为提取的语音不是现有有效用户的语音,如环境音(包括静音,或环境中其他人的语音),其语音数据不是 呼叫的有效数据,不需要处理和传输。 此时手机基带芯片的CPU负荷降低,射频也处于无数据传输状态,可以降低系统功耗。 [0056] 在实际应用中,手机中还可能存储有多个用户的声纹模型。 若移动终端判断自身采集的语音信号与用户的多个声纹模型中的任一个都不匹配,则移动终端放弃对采集到的语音信号进行无线传输或者放弃进行基带传输。 对采集到的语音信号进行射频处理和无线传输,如果移动终端判断自身采集到的语音信号与用户的多种声纹模型中的至少一种匹配,则进行基带和射频处理 以及语音信号的无线传输。 [0057] 在上面的例子中,对语音信号进行基带和射频处理是指进行音频算法处理、数字均衡处理、数字增益处理、AMR编码处理、信道编码处理、调制处理和射频处理等处理。 .关于音频信号。 [0058] 相应地,如图3所示,本实施例还提供了一种降低通话功耗的移动终端,该移动终端包括:存储模块、基带及射频处理模块和天线模块,其中, [0059] 存储模块包括易失性存储器和非易失性存储器,用于存储用户的声纹模型,其中,存储的用户声纹模型具体包括普通用户的声纹模型和普通用户的声纹模型。 临时用户; [0060] 基带及射频处理模块包括声纹处理子模块和音频信号控制处理子模块,其中, [0061]声纹处理子模块用于在语音通话过程中,对移动终端采集的音频信号进行声纹建模,判断获取的声纹模型与存储的用户声纹模型是否匹配,并将判断结果发送给 音频信号控制处理子模块; [0062] 声纹处理子模块还用于通过以下任意一种或两种方式建立存储的用户声纹模型: 在移动终端语音通话开始前,根据移动终端记录的用户语音片段, 建立用户的声纹模型并存储在移动终端的内存中; 移动终端语音通话开始后,当接收到用户发送的声纹模型建立指示时,根据移动终端采集到的音频信号,建立用户的声纹模型并存储在手机的内存中 终端; [0063] 声纹处理子模块,还用于当存储的用户声纹模型有多个时,当判断移动终端采集的音频信号与多个用户声纹模型中的任意一个不匹配时,确定获取的声纹模型 与用户预存的声纹模型不匹配,当判断移动终端采集的音频信号与用户的多个声纹模型中的至少一个匹配时,确定获取的声纹模型与预存的声纹模型匹配 -存储的用户声纹模型; 和 [0064] 声纹处理子模块还用于将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中。 或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。 [0065] 音频信号控制处理子模块,用于当判断结果不匹配时,放弃对采集到的音频信号进行无线传输或放弃对采集到的音频信号进行基带和射频处理及无线传输。 当判断结果匹配时,对音频信号进行基带和射频处理及无线传输。 [0066] 音频信号控制处理子模块对音频信号进行基带和射频处理是指:对音频进行音频算法处理、数字均衡处理、数字增益处理、AMR编码处理、信道编码处理、调制处理和射频处理。 信号。 [0067] 天线模块用于对经过基带和射频处理后的语音信号进行无线传输。 具体实例一 [0068] 在具体实施例一中,主要描述在通话开始前建立并存储用户的声纹模型的执行方式。 如图4所示,具体示例包括以下步骤。 [0069] 在 S 301 ,在语音通话开始前,移动终端记录普通用户A的语音片段,并根据语音片段建立并存储用户A的声纹模型。 [0070] 在 S 302 ,在语音通话过程中,移动终端对移动终端自身采集的音频信号进行声纹建模。 [0071] 在 S 303 ,判断获取的声纹模型与存储的用户A的声纹模型是否匹配。 [0072] 在 S 304 , 如果不匹配, 步骤S 305 被执行,如果匹配,S 306 被执行。 [0073] 在 S 305 、放弃对后续语音通话过程中采集的语音信号进行无线传输,或者放弃对后续语音通话过程中采集的语音信号进行基带和射频处理,无线传输,流程结束。 [0074] 在 S 306,对语音信号进行基带和射频处理及无线传输。 具体例子2 [0075] 在具体实施例二中,主要描述通话开始后建立并存储用户的声纹模型的执行方式。 如图5所示,具体示例包括以下步骤。 [0076] 在 S 401 ,语音通话开始后,移动终端接收用户A发送的声纹模型建立指示,根据采集到的语音信号(即用户按下声纹模型建立指示后发出的语音),建立并存储声纹 用户A的模型 [0077] 在 S 402 ,在后续的语音通话中,移动终端对后续采集的语音信号进行声纹建模。 [0078] 在 S 403 ,判断获取的声纹模型与存储的用户声纹模型是否匹配。 [0079] 在 S 404 , 如果不匹配, 步骤S 405 被执行,如果匹配,S 406 被执行。 [0080] 在 S 405 、放弃对后续语音通话过程中采集的语音信号进行无线传输,或者放弃对后续语音通话过程中采集的语音信号进行基带和射频处理,无线传输,流程结束。 [0081] 在 S 406 ,对语音信号进行基带和射频处理及无线传输。 具体实例3 [0082] 在具体实施例三中,主要描述了通话开始前后需要建立并存储用户的声纹模型的执行方式。 如图6所示,具体示例包括以下步骤。 [0083] 在 S 501 ,在语音通话开始前,移动终端记录普通用户A的语音片段,并根据语音片段建立并存储用户A的声纹模型。 [0084] 在 S 502 ,在用户A使用手机进行语音通话的过程中,移动终端对自身采集的音频信号进行声纹建模。 [0085] 在 S 503 ,判断获取的声纹模型与存储的用户A的声纹模型是否匹配。 [0086] 在 S 504 ,如果不匹配,则放弃对后续语音通话过程中采集的语音信号进行无线传输或者放弃对后续语音通话过程中采集的语音信号进行基带和射频处理,无线传输,如果匹配 ,对语音信号进行基带和射频处理及无线传输。 [0087] 在 S 505 ,临时用户B在通话过程中代替用户A与对端通话,并在通话过程中通过手机上的菜单进行按键选择,向手机发送声纹模型建立指示,手机 根据后续采集到的语音信号(即用户B按下声纹模型建立指示后发出的语音),建立并存储用户B的声纹模型。 在手机为用户B建立声纹模型的时间范围内,对采集到的所有音频信号进行基带和射频处理及无线传输。 [0088] 在 S 506 ,手机B建立并存储用户B的声纹模型后,继续对后续采集的语音信号进行声纹建模。 [0089] 在 S 507 ,判断获取的声纹模型与存储的用户A和用户B的声纹模型是否匹配。 [0090] 在 S 508,如果存储的用户A和用户B的声纹模型均不匹配,则放弃对后续语音通话过程中采集的语音信号进行无线传输或对语音信号进行基带和射频处理无线传输 放弃在后续语音通话过程中收集到的,如果其中至少有一个匹配,则对语音信号进行基带和射频处理和无线传输。 [0091] 从以上示例可以看出,本发明提供的降低移动终端通话功耗的方法及移动终端,通过在现有语音通话上行流程中增加一个基带处理模块,对声纹建模进行声纹建模。 移动终端采集的语音信号,非主叫方的语音数据通过模型匹配被丢弃,后续的基带和射频处理和/或无线传输不再进行,减少了处理和传输 对于无效数据,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,提升了用户体验。 同时,如果通话对方手机的上行也采用声纹处理,则相应地带来当前方接收数据量的减少,下行流量处理的任务量也减少 从而减轻系统负载,提高系统资源的有效利用率,降低基带和射频的功耗。 [0092] 本发明不需要在手机的硬件系统中增加额外的部件,也不需要对硬件布局进行改动。 只需要在软件上已有的语音通话上行流程中增加一个基带处理模块,利用手机内置的音频系统即可实现。 [0093] 本领域普通技术人员可以理解,上述方法中的全部或部分步骤可以通过程序指令相关硬件来完成,该程序可以存储在计算机可读取存储介质中,例如只读存储器 、磁盘或光盘等。 或者,上述实施例的全部或部分步骤也可以采用一个或多个集成电路来实现。 相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。 本发明不限于任何特定形式的硬件和软件的组合。 [0094] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。 根据本发明的内容,还可以有其他各种实施例,本领域的技术人员可以在不脱离本发明的精神和实质的情况下,根据本发明作出各种相应的变化和变换,所有 所作的修改、等同替换、改进等,均属于本发明的保护范围。 工业实用性 [0095] 采用本发明的技术方案,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。 并且,由于减少了无效数据的传输,减轻了系统负载,提高了系统资源的有效利用率,降低了基带和射频的功耗。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102781075A(String), CN102781075B(String), DK2551847T3(String), EP2551847A1(String), EP2551847A4(String), EP2551847B1(String), US20130246051A1(String), WO2012151771A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102781075A(String), CN102781075B(String), DK2551847T3(String), EP2551847A1(String), EP2551847A4(String), EP2551847B1(String), US20130246051A1(String), WO2012151771A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20130246051A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102781075A(String), CN102781075B(String), DK2551847T3(String), EP2551847A1(String), EP2551847A4(String), EP2551847B1(String), US20130246051A1(String), WO2012151771A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), CN102781075A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), CN102781075B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), DK2551847T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), EP2551847A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.735 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.736 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.736 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), EP2551847A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), EP2551847B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), US20130246051A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270666(Integer), WO2012151771A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20130246051A1(String), US20130246051A1(String), 1379520000(Integer), 270666(Integer), 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), CAI, XIAOGUANG(String), ZHAN, MING(String), 中兴通讯股份有限公司(String), CAI XIAOGUANG(String), ZHAN MING(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184984(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184984(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: CAI, XIAOGUANG(String), CAI XIAOGUANG(String), 0(Integer), 1681975546(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHAN, MING(String), ZHAN MING(String), 0(Integer), 1681975546(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184984(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75927(Integer), 2(Integer), 184984(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75928(Integer), 2(Integer), 184984(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.842 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.843 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.843 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.843 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8811949B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Anti-theft mobile terminal and anti-theft method for mobile terminal(String), 移动终端防盗及移动终端防盗方法(String), US8811949B2(String), An anti-theft mobile terminal is disclosed, including: a setting module (10); an encryption module (11), configured to set a screen-lock password and an information return verification password of the mobile terminal; a password verification module (12), configured to verify a screen-unlock password input by a user; a detection module (18), configured to trigger a power management module (13) when detecting that an SIM card or battery has been pulled out, or the battery has run down longer than a preset duration; the power management module (13), configured to stop power supply from the battery of the mobile terminal and start a standby power supply to supply power to an information return module (14), an information deleting module (15), a positioning module (16), and an IMSI; the information return module (14), configured to verify a received information return verification password and return information saved in a set storage area after successful verification; the information deleting module (15), configured to delete the returned information; the positioning module (16), configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. An anti-theft method for mobile terminals is also disclosed.(String), 公开了一种防盗移动终端,包括:设置模块( 10 ); 加密模块( 11 ),用于设置移动终端的锁屏密码和信息返回验证密码; 密码验证模块( 12 ),用于验证用户输入的屏幕解锁密码; 检测模块( 18 ),配置为触发电源管理模块( 13 ) 当检测到 SIM 卡或电池已被拔出,或电池电量耗尽超过预设持续时间时; 电源管理模块( 13 ),用于停止移动终端电池供电,启动备用电源为信息回传模块( 14 ),信息删除模块( 15 )、定位模块( 16 ) 和 IMSI; 信息返回模块( 14 ),用于验证接收到的信息返回验证密码,验证成功后返回保存在设定存储区的信息; 信息删除模块( 15 ),配置删除返回的信息; 定位模块( 16 ),用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 还公开了一种移动终端的防盗方法。(String), US13/258287(String), 1276185600(Integer), US8811949B2(String), 1408377600(Integer), 1408377600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 12(Integer), CN100473194C | CN101026422A | CN101039479A | CN101459721A | CN101568119A | CN101610500A | CN1859670A | US20090093235A1 | US20090270126A1 | US20100009697A1 | US7137003B2 | US8265695B2(String), 8(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.877 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184985(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.878 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\79821a254bc94eb696de7a26ac227d9d.png(String), 184985(Integer), 79821a254bc94eb696de7a26ac227d9d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Anti-theft mobile terminal and anti-theft method for mobile terminal(String), 移动终端防盗及移动终端防盗方法(String), US8811949B2(String), An anti-theft mobile terminal is disclosed, including: a setting module (10); an encryption module (11), configured to set a screen-lock password and an information return verification password of the mobile terminal; a password verification module (12), configured to verify a screen-unlock password input by a user; a detection module (18), configured to trigger a power management module (13) when detecting that an SIM card or battery has been pulled out, or the battery has run down longer than a preset duration; the power management module (13), configured to stop power supply from the battery of the mobile terminal and start a standby power supply to supply power to an information return module (14), an information deleting module (15), a positioning module (16), and an IMSI; the information return module (14), configured to verify a received information return verification password and return information saved in a set storage area after successful verification; the information deleting module (15), configured to delete the returned information; the positioning module (16), configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. An anti-theft method for mobile terminals is also disclosed.(String), 公开了一种防盗移动终端,包括:设置模块( 10 ); 加密模块( 11 ),用于设置移动终端的锁屏密码和信息返回验证密码; 密码验证模块( 12 ),用于验证用户输入的屏幕解锁密码; 检测模块( 18 ),配置为触发电源管理模块( 13 ) 当检测到 SIM 卡或电池已被拔出,或电池电量耗尽超过预设持续时间时; 电源管理模块( 13 ),用于停止移动终端电池供电,启动备用电源为信息回传模块( 14 ),信息删除模块( 15 )、定位模块( 16 ) 和 IMSI; 信息返回模块( 14 ),用于验证接收到的信息返回验证密码,验证成功后返回保存在设定存储区的信息; 信息删除模块( 15 ),配置删除返回的信息; 定位模块( 16 ),用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 还公开了一种移动终端的防盗方法。(String), US13/258287(String), 1276185600(Integer), US8811949B2(String), 1408377600(Integer), 1408377600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 12(Integer), CN100473194C | CN101026422A | CN101039479A | CN101459721A | CN101568119A | CN101610500A | CN1859670A | US20090093235A1 | US20090270126A1 | US20100009697A1 | US7137003B2 | US8265695B2(String), \20230420\79821a254bc94eb696de7a26ac227d9d.png(String), 8(Integer), 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 1. An anti-theft mobile terminal, comprising: a battery, a setting unit, an encryption module, a password verification module, a detection module, a power management module, an information return module, an information deleting module and a positioning module; whereinthe setting unit is configured to set an International Mobile Subscriber Identity (IMSI) for the mobile terminal;the encryption module is configured to set a screen-lock password and an information return verification password of the mobile terminal;the password verification module is configured to verify a screen-unlock password input by a user, and unlock a screen after successful verification;the detection module is configured to detect a battery or a Subscriber Identity Module (SIM) card of the mobile terminal, and trigger the power management module to manage a power supply when detecting that the SIM card has been pulled out, the battery has been pulled out, or the battery has run down longer than a preset duration;the power management module is configured to stop a power supply function of the battery of the mobile terminal and start a standby power supply to supply power to the information return module, the information deleting module, the positioning module, and the IMSI;the information return module is configured to receive an information return verification password from another mobile terminal, verify the information return verification password, and return information saved in a set storage area in the mobile terminal to the another terminal after successful verification;the information deleting module is configured to delete information having been returned by the information return module from the set storage area; andthe positioning module is configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal;wherein the password verification module is configured to trigger the power management module to manage the power supply when the number of verification attempts exceeds a preset threshold, and is started after the mobile terminal is restarted or powered on again.(String), 1.防盗移动终端,包括:电池、设置单元、加密模块、密码验证模块、检测模块、电源管理模块、信息返回模块、信息删除模块和定位模块;其中设置单元,用于为移动终端设置IMSI;加密模块,用于设置移动终端的锁屏密码和信息返回验证密码;密码验证模块,用于验证用户输入的解锁密码,验证成功后解锁屏幕;检测模块,用于检测移动终端的电池或SIM卡,当检测到SIM卡已拔出、电池已拔出时,触发电源管理模块进行电源管理out,或者电池耗尽的时间超过预设时间;电源管理模块,用于停止移动终端电池的供电功能,启动备用电源为信息返回模块、信息删除模块、定位模块和IMSI供电。信息返回模块,用于接收来自其他移动终端的信息返回验证密码,对信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给其他终端。信息删除模块,用于从设置的存储区中删除信息返回模块返回的信息;和定位模块,用于对移动终端进行定位,并周期性向网络侧或指定的移动终端发送定位信息;其中,密码验证模块用于在验证尝试次数超过预设阈值时触发电源管理模块管理电源,并在移动终端重启或再次上电后启动。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 2. The mobile terminal according to claim 1, further comprising:an SIM card binding module, configured to bind a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refuse to provide a network access service to the non-set SIM card.(String), 2.根据权利要求1所述的移动终端,还包括:SIM卡绑定模块,用于为移动终端绑定设置的SIM卡,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 3. The mobile terminal according to claim 2, wherein the SIM card binding module is further configured to bind the IMSI of the mobile terminal to the set SIM card.(String), 3.根据权利要求2所述的移动终端,其中SIM卡绑定模块还用于将移动终端的IMSI与设置的SIM卡进行绑定。四、一种移动终端防盗方法包括:设置移动终端的锁屏密码和信息返回验证密码;为移动终端设置国际移动用户识别码(IMSI);还包括:接收并验证用户输入的解锁密码,验证成功后解锁移动终端的屏幕;当检测到移动终端SIM卡被拔出、移动终端电池被拔出或电池电量耗尽超过预设时间时,停止移动终端电池供电,启动备用电源,使移动终端进入自动运行状态,以移动终端的IMSI作为通信标识;其中,所述自动运行状态包括:接收来自另一移动终端的信息返回验证密码,并对所述信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给另一终端,并从中删除返回的信息。设定的存储区域;启动移动终端的自动定位功能,周期性地向网络侧或指定的移动终端发送移动终端的当前定位信息;和当移动终端输入验证密码错误且尝试验证次数超过预设阈值时,停止移动终端电池供电,启动备用电源,使移动终端进入自动运行状态;并在移动终端重启或再次上电时自动锁定移动终端的屏幕。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 4. An anti-theft method for a mobile terminal comprising: setting a screen-lock password and an information return verification password of the mobile terminal; and setting an International Mobile Subscriber Identity (IMSI) for the mobile terminal; and further comprising:receiving and verifying a screen-unlock password input by a user, and unlocking a screen of the mobile terminal after successful verification; when detecting that an SIM card of the mobile terminal has been pulled out, a battery of the mobile terminal has been pulled out, or the battery has run down longer than a preset duration, stopping supply of power from the battery of the mobile terminal, starting a standby power supply, enabling the mobile terminal to enter an automatic running state, and using the IMSI of the mobile terminal as a communication identity; wherein the automatic running state comprises: receiving an information return verification password from another mobile terminal and verifying the information return verification password, returning information saved in a set storage area in the mobile terminal to the another terminal after successful verification, and deleting returned information from the set storage area; and starting an automatic positioning function of the mobile terminal and periodically transmitting current positioning information of the mobile terminal to a network side or a specified mobile terminal; andwhen an input verification password is incorrect to the mobile terminal and the number of verification attempts exceeds a preset threshold, stopping supply of power from the battery of the mobile terminal, starting the standby power supply, and enabling the mobile terminal to enter the automatic running state; and automatically locking the screen of the mobile terminal when the mobile terminal is restarted or powered on again.(String), 5.根据权利要求4所述的方法,还包括:将设置的SIM卡与移动终端绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 5. The method according to claim 4, further comprising:binding a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card.(String), 6.根据权利要求4所述的方法,还包括:将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 6. The method according to claim 4, further comprising:binding the IMSI of the mobile terminal to a set SIM card, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card.(String), 7.根据权利要求4所述的方法,还包括:当移动终端中的SIM卡或电池拔出时间超过预设时间时,由移动终端启动备用电源,使移动终端自身进入自动运行状态。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 7. The method according to claim 4, further comprising:starting the standby power supply by the mobile terminal and enabling the mobile terminal itself to enter the automatic running state when the SIM card or the battery in the mobile terminal has been pulled out longer than the preset duration.(String), 8.根据权利要求5所述的方法,还包括:将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 1(Integer), 6(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184985(Integer), 8. The method according to claim 5, further comprising:binding the IMSI of the mobile terminal to the set SIM card, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card.(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184985(Integer), TECHNICAL FIELD [0001]The present disclosure relates to anti-theft technologies for mobile terminals, and in particular to an anti-theft mobile terminal and an anti-theft method for a mobile terminal. BACKGROUND [0002]Due to system complexity and application diversity, mobile terminals become like personal computers (PCs) when they are used. Users have become accustomed to storing their important personal information and files in mobile terminals because of portability. This is especially the case for business mobile terminals, which store large amounts of important user information. However, such portability also produces a high risk of losing mobile terminals. A large number of mobile terminal users have experienced such loss. Once a mobile terminal is lost, a user may suffer great economic loss. Therefore, if a mobile terminal is lost, a user would always want to ensure that personal information stored in the mobile terminal is well protected when recovering the lost mobile terminal. However, current mobile terminals obviously do not have this function. [0003]At present, anti-theft methods commonly used for mobile terminals are as follows: [0004]1. using a physical a case is for a mobile terminal: specifically, using a case for a mobile terminal, attaching a chain-like link on the case, and tying the mobile terminal to the user's clothes through the chain-like link to prevent anti-theft; this method can reduce the probability of loss of a terminal, however, once a mobile terminal is lost, a user cannot prevent loss of the user's personal information; [0005]2. arranging a mechanical locking apparatus inside a mobile terminal: a mechanical locking apparatus is placed inside a mobile terminal, wherein, generally, the locking apparatus includes a lock latch, a lock body, a spring, an electromagnetic coil, an iron core, and a locking tongue panel connected to a cell panel; in this method, the locking apparatus is complex in structure and is difficult to implement within the small space of a mobile terminal, meanwhile, the mechanical lock can be easily unlocked by persons skilled in lock-picking, thereby being an ineffective anti-theft mechanism; [0006]3. setting a startup password for a mobile terminal, generally, setting a four-digit PIN code for encryption: such anti-theft method is simple but passwords can be easily cracked, system can be easily reset by using professional cracking software or by refreshing the mobile terminal, therefore, great security risks still exist; and [0007]4. returning related information stored in a mobile terminal through a short message after the mobile terminal is stolen, specifically, returning important information of a user stored in a set storage area, such as an address book, to a new mobile terminal of the user: this method is very effective in returning personal contact information, but has certain limitations, for example, a user cannot implement information return if the mobile terminal is powered off or if a Subscriber Identity Module (SIM) card is replaced. SUMMARY [0008]In view of the above mentioned, the main objective of the present disclosure is to provide an anti-theft mobile terminal and an anti-theft method for a mobile terminal, so that related information in a mobile terminal can be retrieved when the mobile terminal is stolen and the mobile terminal can be accurately positioned. [0009]In order to the above objective, the technical solution of the present disclosure is implemented as follows. [0010]An anti-theft mobile terminal includes a setting unit, an encryption module, a password verification module, a detection module, a power management module, an information return module, an information deleting module, and a positioning module; wherein [0011]the setting unit is configured to set an International Mobile Subscriber Identity (IMSI) for the mobile terminal; [0012]the encryption module is configured to set a screen-lock password and an information return verification password of the mobile terminal; [0013]the password verification module is configured to verify a screen-unlock password input by a user, and unlock a screen after successful verification; [0014]the detection module is configured to detect a battery or an SIM card of the mobile terminal, and trigger the power management module to manage a power supply when detecting that the SIM card has been pulled out, the battery has been pulled out, or the battery has run down longer than a preset duration; [0015]the power management module is configured to stop a power supply function of the battery of the mobile terminal and start a standby power supply to supply power to the information return module, the information deleting module, the positioning module, and the IMSI; [0016]the information return module is configured to receive an information return verification password from another mobile terminal, verify the information return verification password, and return information saved in a set storage area in the mobile terminal to the another terminal after successful verification; [0017]the information deleting module is configured to delete information having been returned by the information return module from the set storage area; and [0018]the positioning module is configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. [0019]Preferably, the mobile terminal may further include: [0020]an SIM card binding module, configured to bind a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refuse to provide a network access service to the non-set SIM card. [0021]Preferably, the SIM card binding module may be further configured to bind the IMSI of the mobile terminal to the set SIM card. [0022]Preferably, the password verification module may be configured to trigger the power management module to manage the power supply when the number of verification attempts exceeds a preset threshold, and is started after the mobile terminal is restarted or powered on again. [0023]Preferably, the power management module may not supply power to the information return module, the information deleting module, the positioning module, and the IMSI when the mobile terminal is powered by the battery normally. [0024]An anti-theft method for a mobile terminal includes: setting a screen-lock password and an information return verification password of a mobile terminal; and setting an IMSI for the mobile terminal; the method further includes:[0025]receiving and verifying a screen-unlock password input by a user, and unlocking a screen of the mobile terminal alter successful verification; when detecting that an SIM card of the mobile terminal has been pulled out, or a battery of the mobile terminal has been pulled out, or the battery has run down longer than a preset duration, stopping supply of power from the battery of the mobile terminal, starting a standby power supply, enabling the mobile terminal to enter an automatic running state, and using the IMSI of the mobile terminal as a communication identity; [0026]wherein the automatic running state comprises: receiving an information return verification password from another mobile terminal and verifying the information return verification password, returning information saved in a set storage area in the mobile terminal to the another terminal after successful verification, and deleting returned information from the set storage area; and starting an automatic positioning function of the mobile terminal and periodically transmitting current positioning information of the mobile terminal to a network side or a specified mobile terminal. [0027]Preferably, the method may further include: [0028]binding a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card. [0029]Preferably, the method may further include: [0030]binding the IMSI of the mobile terminal to the set SIM card, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card. [0031]Preferably, the method may further include: [0032]when an input verification password is incorrect to the mobile terminal and the number of verification attempts exceeds a preset threshold, stopping supply of power from the battery of the mobile terminal, and starting the standby power supply, and enabling the mobile terminal to enter the automatic running state; and automatically locking the screen of the mobile terminal when the mobile terminal is restarted or powered on again. [0033]Preferably, the method may further include: [0034]starting the standby power supply by the mobile terminal and enabling the mobile terminal itself to enter the automatic running state when the SIM card or the battery in the mobile terminal has been pulled out longer than the preset duration. [0035]In the present disclosure, by means of additional arrangement of the IMSI, the password encryption module, the positioning module and the standby power supply in a mobile terminal, when the mobile terminal is stolen or a screen-lock password has been input for many times, the mobile terminal stops its battery from supplying power, starts the standby power supply, and enters the automatic running state, i.e., an anti-theft state. In this case, the standby power supply only supplies power to a module related to the anti-theft state. In this way, the mobile terminal verifies a password requested to be input upon receiving a request for information return from a user who sends this request through another mobile terminal, and sends related information stored in a set storage area to the another mobile terminal after successful verification. Meanwhile, the positioning module of the stolen mobile terminal is started, automatically positions the mobile terminal, and sends positioning information to a network side or a specified mobile terminal. In this way, when a mobile terminal is lost, the lost mobile terminal can be accurately positioned, and can send related information stored in its set storage area to another terminal through which a request for information return is sent, after a user sends a password for information return through the another mobile terminal to the lost mobile terminal. The loss due to loss of a mobile terminal can be greatly reduced by means of the technical solution disclosed in the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure; [0037]FIG. 2 is another structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure; and [0038]FIG. 3 is a flowchart of an anti-theft method for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0039]The basic idea of the present disclosure is that: an IMSI, a password setting module, a positioning module, a standby power supply and the like are arranged in a mobile terminal, so that when the mobile terminal is stolen or a screen-lock password has been input for many times, the mobile terminal stops a mobile terminal battery from supplying power, starts the standby power supply, and enters an automatic running state, i.e., an anti-theft state, in this case, the standby power supply only supplies power to a module related to the anti-theft state. The mobile terminal verifies a password requested to be input after receiving a request for information return which is sent by the user through another mobile terminal, and sends related information stored in a set storage area after successful verification to the mobile terminal which sent the request. Meanwhile, the positioning module of the stolen mobile terminal is started, automatically positions the mobile terminal, and sends positioning information to a network side or a specified mobile terminal. [0040]FIG. 1 is a structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 1, the anti-theft mobile terminal in this embodiment includes: a setting unit 10, an encryption module 11, a password verification module 12, a detection module 18, a power management module 13, an information return module 14, an information deleting module 15, and a positioning module 16. [0041]The setting unit 10 is configured to set an IMSI for the mobile terminal. After the mobile terminal is lost and enters an anti-theft state, the IMSI is started to act as the identity of the lost mobile terminal so as to implement relevant communication with the lost mobile terminal. [0042]The encryption module 11 is configured to set a screen-lock password and an information return verification password of the mobile terminal, wherein the screen-lock password and the information return verification password can be a password whose number of digits is not limited, which may be numeral or character combination, and is set by a user after the mobile terminal is started. The screen-lock password is a password which is required to be input to unlock the screen of the mobile terminal when the user wants to use the mobile terminal. The information return verification password is a password for verifying whether a requester is an authorized user upon a request for information return is received. When the verification password is input correctly, the request for information return is considered valid. [0043]The password verification module 12 is configured to verify a screen-unlock password input by a user, unlock the screen after successful verification, and trigger the power management module to manage a power supply when the number of verification attempts exceeds a preset threshold. Here, the threshold of the number of verification attempts for a screen-unlock password may be set to 6, that is, when a user inputs incorrect screen-unlock password six times consecutively, the mobile terminal enters an automatic running state, i.e., an anti-theft state. When detecting that a battery or an SIM card of the mobile terminal has been pulled out longer than a preset duration, the mobile terminal enters the automatic running state. The preset duration can be one hour, two hours, 24 hours, or a week, and is set by a mobile terminal user. [0044]In the present disclosure, the password verification module 12 is started after the mobile terminal is restarted or powered on again, i.e., after the mobile terminal is restarted or powered on again, the password verification module 12 considers it a normal start and prompts a user to input the screen-unlock password. [0045]The detection module 18 is configured to detect the battery or the SIM card of the mobile terminal, and trigger the power management module 13 to manage the power supply when detecting that the SIM card has been pulled out, the battery has been pulled out, or the battery has run down longer than a preset duration. The detection module 18 is configured to prevent the user from being unable to communicate with and find the lost mobile terminal in the case where a thief pulls out the SIM card or battery, or powers off the stolen mobile terminal. To overcome this defect of existing mobile terminals, the detection module 18 is arranged for the mobile terminal in the present disclosure to start a standby power supply automatically to enable the mobile terminal enter the anti-theft state when detecting that the battery of the mobile terminal has run down longer than the preset duration or the SIM card has been pulled out longer than the preset duration. The preset duration can be set as 30 minutes, 20 minutes, or one day. [0046]The power management module 13 is configured to stop power supply from the battery and start a standby power supply to supply power to the information return module 14, the information deleting module 15, the positioning module 16, and the IMSI; that is to say, when determining that the number of verification attempts for a screen-unlock password input by a user exceeds the preset threshold, the battery of the mobile terminal is automatically cut off and no power is supplied to corresponding processing units, then, the mobile terminal enters a power-off state like existing mobile terminals does. In the present disclosure, the standby power supply is connected to the battery of the mobile terminal, charged by the battery of the mobile terminal when the mobile terminal is working normally, and supplies power to relevant modules in the anti-theft state in the mobile terminal once the battery of the mobile terminal stops working, so that the anti-theft function of the mobile terminal can be implemented. Detailed description is given below on how the mobile terminal implements the anti-theft function according to the present disclosure. [0047]The power management module 13 does not supply power to the information return module 14, information deleting module 15, positioning module 16 and the IMSI when the mobile terminal is powered by the battery normally. [0048]The information return module 14 is configured to receive and verify the information return verification password, and return information saved in a set storage area in the mobile terminal to another terminal when verification succeeds. When a user confirms that his/her mobile terminal is lost, the user can send a request for information return to the lost mobile terminal using any other mobile terminal; specifically, the request is sent to the lost mobile terminal through a short message, the content of which is the information return verification password set by the user before the mobile terminal is lost. After the lost mobile terminal starts an automatic running mode, the lost mobile terminal, once upon receiving the short message, takes the message as the information return verification password by default, extracts the content from the short message and compares the content with the information return verification password stored in the lost mobile terminal; if they are consistent, the lost mobile terminal automatically sends related information stored in the set storage area in the lost mobile terminal to the terminal who sent the request. Specifically, the above set storage area may be an address book storage area, a short message storage area, or a user personal information storage area, etc. [0049]Since the lost mobile terminal has entered the anti-theft state, the SIM card in the mobile terminal does not work any longer. Therefore, in order to enable the request for information return to be responded by the lost mobile terminal, an IMSI set for the lost mobile terminal is required to be used as an identity, that is, the mobile terminal is located in a network environment supporting the IMSI and can receive a short message and the like from any other mobile terminal. [0050]The information deleting module 15 is configured to delete information having been returned by the information return module 14 from the set storage area. When the information return module 14 returns related information stored in the set storage area to another mobile terminal, the information deleting module 15 deletes the information. In this way, even though the screen-lock password set for the lost mobile terminal is cracked, the information cannot be obtained, which effectively protects privacy of the mobile terminal user. [0051]The positioning module 16 is configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. In the present disclosure, the positioning module 16 can be implemented by a Global Positioning System (GPS) or an equivalent processor. The GPS positioning function can be simply implemented on a mobile terminal. In the present disclosure, the positioning module 16 can be also a Geographic Information System (GIS) positioning instrument, and specifically, determines location information of the mobile terminal according to base station location information reported by the mobile terminal to a network side, an angle at which a signal is transmitted from the mobile terminal to the base station and power of the signal. In the present disclosure, when the positioning module 16 is started, it automatically positions the mobile terminal and reports positioning information to a network side or a specified mobile terminal. In this way, once the mobile terminal is lost, current positioning information of the lost mobile terminal can be provided to a relevant person, thus giving the person a clue to finding of the lost mobile terminal. [0052]FIG. 2 is another structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 2, based on the terminal illustrated in FIG. 1, the anti-theft mobile terminal further includes: [0053]an SIM card binding module 17, configured to bind a set SIM card to the mobile terminal, and refuse to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card; wherein the function of the SIM card binding module 17 can be set by a user, for example, when the user selects the function of binding the current mobile terminal to the current inserted SIM card, the mobile terminal enables the binding function. With this function enabled, the mobile terminal does not support any other SIM card except its bound SIM card unless a binding relationship is set between the mobile terminal and other SIM card. [0054]Or the SIM card binding module is further configured to bind the IMSI to the set SIM card, and refuse to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card. The principle of binding the IMSI to the SIM card is the same as that of binding the SIM card to the mobile terminal. [0055]FIG. 3 is a flowchart of an anti-theft method for a mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 3, the method includes the following steps: [0056]step 301: a screen-lock password and an information return verification password of the mobile terminal are set; and an IMSI is set for the mobile terminal; [0057]in this step, after the mobile terminal enters a normal running state, the screen-lock password and the information return verification password are set through corresponding setting functions, wherein these passwords are set by a user, and can be numeral or/and character combination. Setting the IMSI is equivalent to setting another network access mode for the mobile terminal; this mode is not started when the mobile terminal is working normally but started when the mobile terminal enters the anti-theft state. That is to say, the mobile terminal according to the present disclosure supports a multi-mode function, however, during actual working, only a single mode, either a network function supported by the IMSI (in the anti-theft state) or a network function supported by the SIM card (in normal working), can be enabled; [0058]step 302: after the screen of the mobile terminal is locked, a screen-unlock password input by the user is received and verified, and the screen is unlocked when the password verification is successful; if the input password is incorrect and the number of verification attempts exceeds a preset threshold, a battery of the mobile terminal stops supplying power, a standby power supply is started and the mobile terminal enters an automatic running state, further, the IMSI of the mobile terminal is used as a communication identity; here, the mobile terminal enters the automatic running state, i.e. it enters the anti-theft state; [0059]when the number of times of inputting an incorrect screen-lock password exceeds the preset threshold, the mobile terminal automatically enters the anti-theft state, at this moment, the mobile terminal appears to be powered off, disables the network function supported by the SIM card but enables the network function supported by the IMSI set in the mobile terminal. In fact, at this moment, the mobile terminal, with the help of the standby power supply, still supports a network communication function, which is, however, not controlled by a user. [0060]It should be noted that when the SIM card or battery of the mobile terminal has been pulled out or the battery has been unable to supply power because of shutdown or battery faults or other reasons longer than a preset duration, the mobile terminal also enters the automatic running state, i.e., the anti-theft state. The preset duration can be set as 30 minutes, 20 minutes, or one day. [0061]The automatic running state here includes: receiving an information return verification password from another mobile terminal and verifying the password, returning information saved in a set storage area in the mobile terminal to the another terminal after successful verification, and deleting information, which has been returned by the information return module, from the set storage area; and starting an automatic positioning function of the mobile terminal and periodically transmitting current positioning information of the mobile terminal to a network side or a specified mobile terminal. [0062]In the present disclosure, besides the above-mentioned step 301 and step 302, the anti-theft method further includes: binding the SIM card to the mobile terminal, and refusing to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card. The above function can be set by a user, for example, when the user selects the function of binding the current mobile terminal to the current inserted SIM card, the mobile terminal enables the binding function, thus, the mobile terminal does not support any other SIM card any longer except this SIM card inserted in the mobile terminal unless a binding relationship is additionally set between the mobile terminal and other SIM card. [0063]Or the anti-theft method further includes: binding the IMSI of the mobile terminal to the set SIM card, and refusing to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card. Binding of the IMSI to the set SIM card and binding of the mobile terminal to the set SIM card are the same, which is not detailed here again. [0064]To prevent the mobile terminal from entering the anti-theft state in stead of the normal state due to an operation mistake or a failure in memorizing a password, the mobile terminal according to the present disclosure automatically locks its screen after being restarted and powered-on again, i.e., it automatically enters a screen-lock state after being started or powered on again, and can enter a normal working state after the user inputs a correct screen-unlock password. [0065]The above are only preferred embodiments of the present disclosure, and not intended to limit the protection scope of the present disclosure.(String), 技术领域 [0001] 本发明涉及移动终端防盗技术,尤其涉及一种移动终端防盗及移动终端防盗方法。 背景 [0002] 由于系统的复杂性和应用的多样性,移动终端在使用时变得像个人电脑(Personal Computer,PC)。 由于便携性的原因,用户已经习惯于将重要的个人信息和文件存储在移动终端中。 尤其是商务移动终端,存储了大量重要的用户信息。 然而,这种便携性也产生了丢失移动终端的高风险。 大量的移动终端用户都曾经历过这样的流失。 一旦移动终端丢失,用户可能会遭受很大的经济损失。 因此,如果移动终端丢失,用户在找回丢失的移动终端时,总是希望能够保证移动终端中存储的个人信息得到很好的保护。 但是,目前的移动终端显然没有这个功能。 [0003] 目前,移动终端常用的防盗方法有以下几种: [0004] 1、移动终端使用实体外壳:具体为移动终端使用外壳,在外壳上附上链条,通过链条将移动终端系在用户的衣服上,以防 防小偷; 这种方法可以降低终端丢失的概率,但是一旦移动终端丢失,用户就无法避免用户个人信息的丢失。 [0005] 2、在移动终端内部设置机械锁紧装置:在移动终端内部设置机械锁紧装置,通常,锁紧装置包括锁舌、锁体、弹簧、电磁线圈、铁芯, 与电池板连接的锁舌板; 该方法中,锁定装置结构复杂,难以在移动终端的狭小空间内实现,同时机械锁很容易被开锁技术人员解锁,防盗效果不佳。 ; [0006] 3、为移动终端设置开机密码,一般设置一个四位PIN码进行加密:这种防盗方法简单,但密码容易被破解,使用专业破解软件或刷新即可轻松重置系统 因此,移动终端仍然存在很大的安全隐患; 和 [0007] 4、移动终端被盗后通过短信返回移动终端中存储的相关信息,具体为将存储在设定存储区域中的用户重要信息,如通讯录返回给用户的新移动终端。 :这种方法在返回个人联系信息方面非常有效,但是有一定的局限性,例如,如果移动终端关机或更换SIM卡,用户将无法实现信息返回。 概括 [0008] 鉴于以上所述,本发明的主要目的在于提供一种移动终端防盗及移动终端防盗方法,使得移动终端在被盗时能够检索到移动终端中的相关信息。 被盗,移动终端可以准确定位。 [0009] 为实现上述目的,本发明的技术方案是通过以下方式实现的。 [0010] 一种移动防盗终端,包括设置单元、加密模块、密码验证模块、检测模块、电源管理模块、信息返回模块、信息删除模块和定位模块; 其中 [0011] 设置单元,用于为移动终端设置IMSI; [0012] 加密模块,用于设置移动终端的锁屏密码和信息返回验证密码; [0013] 密码验证模块,用于验证用户输入的解锁密码,验证成功后解锁屏幕; [0014]检测模块用于检测移动终端的电池或SIM卡,当检测到SIM卡已拔出、电池已拔出或电池已拔出时,触发电源管理模块进行电源管理。 耗尽时间超过预设持续时间; [0015] 电源管理模块,用于停止移动终端电池的供电功能,启动备用电源为信息返回模块、信息删除模块、定位模块和IMSI供电。 [0016] 信息返回模块,用于接收来自其他移动终端的信息返回验证密码,对信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给其他终端。 [0017] 信息删除模块,用于从设置的存储区中删除信息返回模块返回的信息; 和 [0018] 定位模块,用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 [0019] 优选地,所述移动终端还可以包括: [0020] SIM卡绑定模块,用于为移动终端绑定设置的SIM卡,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 [0021] 优选地,SIM卡绑定模块还用于将移动终端的IMSI与设置的SIM卡进行绑定。 [0022] 优选地,密码验证模块可以用于在验证尝试次数超过预设阈值时触发电源管理模块管理电源,并在移动终端重启或重新上电后启动。 [0023] 优选地,当移动终端由电池正常供电时,电源管理模块可以不向信息返回模块、信息删除模块、定位模块和IMSI供电。 [0024] 一种移动终端防盗方法,包括:设置移动终端的锁屏密码和信息返回验证密码; 为移动终端设置IMSI; 该方法还包括: [0025]接收并验证用户输入的锁屏密码,验证成功后解锁移动终端屏幕; 当检测到移动终端SIM卡被拔出,或移动终端电池被拔出,或电池电量耗尽超过预设时间时,停止移动终端电池供电 、启动备用电源,使移动终端进入自动运行状态,以移动终端的IMSI作为通信标识; [0026] 其中,所述自动运行状态包括:接收来自另一移动终端的信息返回验证密码,并对所述信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给另一终端,并从中删除返回的信息。 设定的存储区域; 启动移动终端的自动定位功能,周期性地向网络侧或指定移动终端发送移动终端当前的定位信息。 [0027] 优选地,该方法还可以包括: [0028] 将设置的SIM卡与移动终端绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 [0029] 优选地,该方法还可以包括: [0030] 将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 [0031] 优选地,该方法还可以包括: [0032] 当移动终端输入验证密码错误且尝试验证次数超过预设阈值时,停止移动终端电池供电,启动备用电源,使移动终端进入自动模式 运行状态; 并在移动终端重启或再次上电时自动锁定移动终端的屏幕。 [0033] 优选地,该方法还可以包括: [0034]当移动终端中的SIM卡或电池拔出时间超过预设时间时,由移动终端启动备用电源,使移动终端自身进入自动运行状态。 [0035] 本发明通过在移动终端中增设IMSI、密码加密模块、定位模块和备用电源,当移动终端被盗或多次输入锁屏密码时 ,移动终端停止电池供电,启动备用电源,进入自动运行状态,即防盗状态。 此时,备用电源只为与防盗状态相关的模块供电。 这样,移动终端在接收到用户通过其他移动终端发送信息返回请求后,对要求输入的密码进行验证,成功后将存储在设置的存储区中的相关信息发送给其他移动终端。 确认。 同时启动被盗移动终端的定位模块,自动对移动终端进行定位,并向网络侧或指定移动终端发送定位信息。 这样,当移动终端丢失时,可以准确定位丢失的移动终端,并在用户发送密码后,将其设置的存储区域中存储的相关信息发送给另一个终端,通过该终端发送信息返回请求。 用于通过另一移动终端向丢失的移动终端返回信息。 通过本发明公开的技术方案,可以大大减少因移动终端丢失而造成的损失。 附图的简要说明 [0036] 图1为本发明实施例提供的一种移动防盗终端的结构示意图; [0037] 图2为本发明实施例提供的一种移动防盗终端的另一种结构示意图; 和 [0038] 图3为本发明实施例提供的一种移动终端防盗方法的流程图。 详细说明 [0039] 本发明的基本思想是:在移动终端中设置IMSI、密码设置模块、定位模块、备用电源等,以便在移动终端被盗或锁屏密码时 多次输入后,移动终端停止移动终端电池供电,启动备用电源,进入自动运行状态,即防盗状态,此时备用电源只供电 给与防盗状态相关的模块供电。 移动终端在接收到用户通过其他移动终端发送的信息返回请求后,对请求输入的密码进行验证,将验证成功后存储在设置的存储区中的相关信息发送给发送请求的移动终端。 同时启动被盗移动终端的定位模块,自动对移动终端进行定位,并向网络侧或指定移动终端发送定位信息。 [0040] 图1为本发明实施例提供的一种移动防盗终端的结构示意图。 如图1所示,本实施例的移动防盗终端,包括: 设置单元 10 , 一个加密模块 11 , 密码验证模块 12 , 检测模块 18 , 电源管理模块 13 , 信息返回模块 14 ,信息删除模块 15 , 和一个定位模块 16 . [0041] 设定单位 10 用于为移动终端设置IMSI。 当移动终端丢失进入防盗状态后,启动IMSI作为丢失移动终端的标识,与丢失移动终端进行相关通信。 [0042] 加密模块 11用于设置移动终端的锁屏密码和信息返回验证密码,其中,屏幕锁定密码和信息返回验证密码可以是不限位数的密码,可以是数字或字符。 组合,由用户在移动终端启动后设置。 锁屏密码是用户在使用移动终端时解锁移动终端屏幕所需要输入的密码。 信息返回验证密码是在接收到信息返回请求时验证请求者是否为授权用户的密码。 当验证密码输入正确时,信息返回请求被视为有效。 [0043] 密码验证模块 12 用于验证用户输入的屏幕解锁密码,验证成功后解锁屏幕,当验证次数超过预设阈值时,触发电源管理模块对电源进行管理。 这里,可以将锁屏密码的验证尝试次数阈值设置为6,即当用户连续6次输入错误的锁屏密码时,移动终端进入自动运行状态,即 防盗状态。 当检测到移动终端的电池或SIM卡被拔出时间超过预设时间时,移动终端进入自动运行状态。 预设时长可以为1小时、2小时、24小时或一周,由移动终端用户设置。 [0044] 在本发明中,密码验证模块 12 密码验证模块在移动终端重启或重新上电后启动,即移动终端重新启动或重新上电后,密码验证模块 12 认为是正常启动,提示用户输入锁屏密码。 [0045] 检测模块 18 用于检测移动终端的电池或SIM卡,并触发电源管理模块 13 当检测到SIM卡被拔出、电池被拔出或电池电量耗尽超过预设时间时,进行电源管理。 检测模块 18 用于防止在小偷拔出SIM卡或电池,或将被盗移动终端关机等情况下,用户无法与丢失的移动终端通信,无法找到丢失的移动终端。 为了克服现有移动终端的这一缺陷,检测模块 18 本发明的移动终端设置为当检测到移动终端电池电量耗尽超过预设时长或SIM卡失灵时,自动启动待机电源使移动终端进入防盗状态。 被拔出的时间超过预设时间。 预设持续时间可以设置为 30 分钟、20 分钟或一天。 [0046] 电源管理模块 13 设置为停止电池供电,启动备用电源给信息返回模块供电 14 ,信息删除模块 15 , 定位模块 16 , 和 IMSI; 也就是说,当判断用户输入的锁屏密码验证次数超过预设阈值时,移动终端的电池自动断电,不给相应的处理单元供电,则, 移动终端与现有移动终端一样进入关机状态。 本发明中,备用电源连接移动终端的电池,在移动终端正常工作时由移动终端的电池充电,并在防盗状态下为手机中的相关模块供电。 一旦移动终端的电池停止工作,终端可以实现移动终端的防盗功能。 下面详细说明移动终端如何实现本发明的防盗功能。 [0047] 电源管理模块 13 不给信息返回模块供电 14一、信息删除模块 15 , 定位模块 16 以及移动终端正常由电池供电时的IMSI。 [0048] 信息反馈模块 14 用于接收并验证信息返回验证密码,验证成功时,将移动终端中设置的存储区域中保存的信息返回给其他终端。 当用户确认自己的移动终端丢失后,用户可以使用其他任何移动终端向丢失的移动终端发送信息找回请求; 具体地,通过短信向丢失的移动终端发送请求,短信内容为用户在移动终端丢失前设置的信息返还验证密码。 丢失的移动终端启动自动运行模式后,丢失的移动终端一旦收到短信,默认将该短信作为信息返回验证密码,提取短信内容,与信息返回进行比对 遗失移动终端中保存的验证密码; 如果一致,则丢失的移动终端自动将丢失移动终端中设置的存储区域中存储的相关信息发送给发送请求的终端。 具体的,上述设置的存储区可以为通讯录存储区、短信存储区或用户个人信息存储区等。 [0049] 由于丢失的移动终端已经进入防盗状态,移动终端中的SIM卡不再工作。 因此,为了使丢失的移动终端响应信息返回请求,需要使用为丢失的移动终端设置的IMSI作为标识,即移动终端所处的网络环境支持 IMSI,可以接收来自任何其他移动终端的短消息等。 [0050] 信息删除模块 15 用于删除信息返回模块返回的信息 14 从设定的存储区。 当信息返回模块 14 将设置的存储区中存储的相关信息返回给另一移动终端,信息删除模块 15 删除信息。 这样即使为丢失的移动终端设置的锁屏密码被破解,也无法获取信息,有效保护了移动终端用户的隐私。 [0051] 定位模块 16 用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 在本发明中,定位模块 16 可以通过全球定位系统 (GPS) 或等效处理器来实现。 GPS定位功能可以简单地在移动终端上实现。 在本发明中,定位模块 16 也可以是地理信息系统(GIS)定位仪,具体地,根据移动终端向网络侧上报的基站位置信息、移动终端发射信号的角度等,确定移动终端的位置信息 终端到基站和信号功率。 在本发明中,当定位模块 16 启动后,自动对移动终端进行定位,并将定位信息上报给网络侧或指定的移动终端。 这样,一旦移动终端丢失,就可以将丢失的移动终端当前的定位信息提供给相关人员,从而为相关人员寻找丢失的移动终端提供线索。 [0052] 图2为本发明实施例提供的一种移动防盗终端的另一种结构示意图。 如图2所示,该移动防盗终端在图1所示终端的基础上,还包括: [0053] SIM卡绑定模块 17 ,用于将设置的SIM卡绑定到移动终端,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供网络接入服务; 其中SIM卡绑定模块的功能 17可以由用户设置,例如,当用户选择绑定当前移动终端和当前插入的SIM卡的功能时,移动终端开启绑定功能。 启用该功能后,除非移动终端与其他SIM卡建立绑定关系,否则移动终端不支持除自身绑定的SIM卡外的其他任何SIM卡。 [0054] 或者,SIM卡绑定模块,还用于将IMSI绑定到设置的SIM卡上,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供网络接入服务。 IMSI与SIM卡的绑定原理与SIM卡与移动终端的绑定原理相同。 [0055] 图3为本发明实施例提供的一种移动终端防盗方法的流程图。 如图3所示,该方法包括以下步骤: [0056] 步 301 :设置移动终端的锁屏密码和信息返回验证密码; 为移动终端设置IMSI; [0057] 本步骤中,移动终端进入正常运行状态后,通过相应的设置功能设置锁屏密码和信息返回验证密码,这些密码由用户设置,可以是数字或/和字符的组合 . 设置IMSI相当于为移动终端设置了另一种网络接入方式; 该模式在移动终端正常工作时不启动,在移动终端进入防盗状态时启动。 也就是说,本发明的移动终端支持多模功能,但在实际工作中,只有一种模式,要么是IMSI支持的网络功能(防盗状态下),要么是网络 SIM卡支持的功能(正常工作时),可以启用; [0058] 步 302 :移动终端锁屏后,接收并验证用户输入的解锁密码,验证成功后解锁屏幕; 如果输入的密码错误,且尝试验证的次数超过预设阈值,则移动终端的电池停止供电,启动备用电源,移动终端进入自动运行状态,进一步,移动终端的IMSI 终端作为通信标识; 此时,移动终端进入自动运行状态,即进入防盗状态; [0059] 当锁屏密码输入错误次数超过预设阈值时,移动终端自动进入防盗状态,此时移动终端呈现关机状态,禁用SIM支持的网络功能 卡,但启用移动终端设置的IMSI支持的网络功能。 实际上,此时移动终端借助于备用电源,仍然支持网络通信功能,但不受用户控制。 [0060] 需要注意的是,当移动终端的SIM卡或电池被拔出或电池因关机或电池故障等原因超过预设时间无法供电时,移动终端也会进入自动关机状态。 运行状态,即防盗状态。 预设持续时间可以设置为 30 分钟、20 分钟或一天。 [0061] 这里的自动运行状态包括:接收到另一移动终端的信息返回验证密码并验证密码,验证成功后将保存在移动终端中设置的存储区域中的信息返回给另一终端,并删除已返回的信息 由信息返回模块,从设定的存储区中获取; 启动移动终端的自动定位功能,周期性地向网络侧或指定移动终端发送移动终端当前的定位信息。 [0062] 在本发明中,除了上述步骤外 301 和步骤 302,该防盗方法还包括:将SIM卡与移动终端绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 上述功能可以由用户设置,例如当用户选择绑定当前移动终端与当前插入的SIM卡的功能时,移动终端开启绑定功能,则移动终端不支持任何其他功能 除非移动终端与其他SIM卡另外设置绑定关系,否则移动终端中不再插入此SIM卡以外的SIM卡。 [0063] 或者,该防盗方法还包括:将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 IMSI与设置的SIM卡的绑定与移动终端与设置的SIM卡的绑定相同,此处不再赘述。 [0064] 为防止移动终端因操作失误或密码记忆失败而进入防盗状态而不是正常状态,本发明的移动终端在重启开机后自动锁屏。 再次,即开机或再次上电后自动进入锁屏状态,用户输入正确的锁屏密码后即可进入正常工作状态。 [0065] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101772018A(String), CN101772018B(String), EP2503806A1(String), EP2503806A4(String), EP2503806B1(String), US20120244839A1(String), US8811949B2(String), WO2011088652A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101772018A(String), CN101772018B(String), EP2503806A1(String), EP2503806A4(String), EP2503806B1(String), US20120244839A1(String), US8811949B2(String), WO2011088652A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:46.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8811949B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101772018A(String), CN101772018B(String), EP2503806A1(String), EP2503806A4(String), EP2503806B1(String), US20120244839A1(String), US8811949B2(String), WO2011088652A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), CN101772018A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), CN101772018B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), EP2503806A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), EP2503806A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.052 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), EP2503806B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), US20120244839A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.074 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.074 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), US8811949B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270667(Integer), WO2011088652A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8811949B2(String), US8811949B2(String), 1408377600(Integer), 270667(Integer), 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.104 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184985(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184985(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184985(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184985(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.136 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9621802B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US9621802B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US14/735625(String), 1433865600(Integer), US9621802B2(String), 1491840000(Integer), 1491840000(Integer), 美国(String), 4(Integer), 8(Integer), 36(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130229529A1 | US20140168356A1 | US20140210940A1 | US20140375760A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.179 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184986(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\958a1be051274159bc3d984e10f27462.png(String), 184986(Integer), 958a1be051274159bc3d984e10f27462.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.214 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.214 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.215 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US9621802B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US14/735625(String), 1433865600(Integer), US9621802B2(String), 1491840000(Integer), 1491840000(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 36(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130229529A1 | US20140168356A1 | US20140210940A1 | US20140375760A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2(String), \20230420\958a1be051274159bc3d984e10f27462.png(String), 20(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 1. A method for presenting a panoramic photo in a mobile terminal, comprising:detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, wherein the immersive browsing mode is a browsing mode in which the panoramic photo moves as the mobile terminal rotates;detecting and determining a rotation angle of the mobile terminal when the trigger instruction is detected;calculating a minimum displacement of the panoramic photo according to a preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; andmoving and presenting, according to the rotation angle and the minimum displacement, the panoramic photo that is displayed in a normal mode in the mobile terminal, andwherein the panoramic photo is moved for the minimum displacement along a direction opposite to a rotation direction of the mobile terminal.(String), 1.移动终端,包括:输入设备;传感器;处理器耦合到输入装置和传感器;和显示屏耦合到处理器,其中,输入设备用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,其中,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,其中,传感器用于检测移动终端的旋转角度,其中,处理器用于根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、全景照片沿旋转方向的照片宽度,确定全景照片的最小位移。移动端拍摄全景照片时,其中,处理器用于在检测到输入设备输入触发指令时,根据旋转角度和最小位移移动移动终端中以正常模式呈现的全景照片,其中,处理器用于将全景照片沿与移动终端的旋转方向相反的方向移动最小位移,以及其中,显示屏用于呈现全景照片。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 2. The method according to claim 1, wherein determining the rotation angle of the mobile terminal comprises:determining a placement direction in which the mobile terminal is located in a rotation process; anddetermining the rotation angle of the mobile terminal according to the placement direction.(String), 12.根据权利要求11所述的移动终端,其中传感器配置为:确定移动终端在旋转过程中所处的放置方向;和根据放置方向确定移动终端的旋转角度。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 3. The method according to claim 2, wherein determining the placement direction in which the mobile terminal is located in the rotation process comprises:detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, wherein the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and wherein a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located; anddetermining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process.(String), 13.根据权利要求12所述的移动终端,其中传感器用于通过以下方式确定移动终端在旋转过程中所处的放置方向:检测移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,其中参考三维坐标系的X-Y平面平行于屏幕所在的平面移动终端的屏幕所在平面,其中参考三维坐标系的Z轴垂直于移动终端屏幕所在的平面。和根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端在旋转过程中所处的放置方向。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 4. The method according to claim 3, wherein determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process comprises:determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees; anddetermining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees.(String), 14.根据权利要求12所述的移动终端,其中传感器,用于根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角,确定如下方式,其中,所述放置方向为:移动端位于轮换过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角为时,确定移动终端在旋转过程中所处的放置方向为竖直放置方向不大于45度;和当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角为时,确定移动终端在旋转过程中所处的放置方向为水平放置方向大于45度。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 5. The method according to claim 3, wherein determining the rotation angle of the mobile terminal according to the placement direction comprises:using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 15.根据权利要求13所述的移动终端,其中传感器用于根据放置方向,通过以下方式确定移动终端的旋转角度:当确定移动终端在旋转过程中所处的放置方向为a时,将参考三维坐标系中Z轴的方向作为移动终端在旋转过程中对应的轴向水平放置方向;和将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 6. The method according to claim 3, wherein determining the rotation angle of the mobile terminal according to the placement direction comprises:using one of a direction of an X-axis and a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 16.根据权利要求13所述的移动终端,其中传感器用于根据放置方向,通过以下方式确定移动终端的旋转角度:当确定放置方向为旋转过程时,将参考三维坐标系中的X轴方向和Y轴方向之一作为移动终端对应的轴向方向。移动端在旋转过程中定位为竖直放置方向;和将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。(String), 1(Integer), 5(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 7. The method according to claim 1, wherein before moving, according to the rotation angle, the panoramic photo that is displayed in the normal mode in the mobile terminal, further comprises determining that the rotation angle of the mobile terminal reaches the preset rotation angle threshold.(String), 17.根据权利要求11所述的移动终端,其中处理器,还用于确定移动终端的旋转角度达到预设的旋转角度阈值后,根据旋转角度移动终端中正常模式下呈现的全景照片。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 8. The method according to claim 1, wherein before detecting and determining the rotation angle of the mobile terminal, the method further comprises providing prompt information that is used to instruct to rotate the mobile terminal.(String), 18.根据权利要求11所述的移动终端,其中处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 9. The method according to claim 8, wherein before providing the prompt information that is used to instruct to rotate the mobile terminal, the method further comprises acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and wherein providing the prompt information that is used to instruct to rotate the mobile terminal comprises providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction.(String), 19.根据权利要求18所述的移动终端,其中处理器还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,其中,处理器具体用于提供,以下方式,根据获取的旋转方向,提供用于指示旋转移动终端的提示信息,用于指示旋转移动终端的提示信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 10. The method according to claim 1, wherein the minimum displacement is calculated according to an equation:s=d⁢φ1φ2,wherein s is the minimum displacement, d is the width of the panoramic photo, φ1 is the preset rotation angle threshold, and wherein φ2 is the rotation angle of the mobile terminal when the panoramic photo is photographed.(String), 20.根据权利要求11所述的移动终端,其中最小位移根据以下公式计算:s=d⁢φ1φ2,其中s为最小位移,d为全景照片的宽度,φ1为预设旋转角度阈值,其中φ2为拍摄全景照片时移动端的旋转角度。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 11. A mobile terminal, comprising:an input device;a sensor;a processor coupled to the input device and the sensor; anda display screen coupled to the processor,wherein the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode,wherein the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates,wherein the sensor is configured to detect a rotation angle of the mobile terminal,wherein the processor is configured to determine a minimum displacement of the panoramic photo according to a preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed,wherein the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle and the minimum displacement, the panoramic photo that is presented in a normal mode in the mobile terminal,wherein the processor is configured to move the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal, andwherein the display screen is configured to present the panoramic photo.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 12. The mobile terminal according to claim 11, wherein the sensor is configured to:determine a placement direction in which the mobile terminal is located in a rotation process; anddetermine the rotation angle of the mobile terminal according to the placement direction.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 13. The mobile terminal according to claim 12, wherein the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process:detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, wherein the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and wherein a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located; anddetermining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 14. The mobile terminal according to claim 12, wherein the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, and wherein the placement direction in which the mobile terminal is located in the rotation process:determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees; anddetermining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees.(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 15. The mobile terminal according to claim 13, wherein the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction:using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 16. The mobile terminal according to claim 13, wherein the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction:using one of a direction of an X-axis and a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 17. The mobile terminal according to claim 11, wherein the processor is further configured to determine that the rotation angle of the mobile terminal reaches the preset rotation angle threshold before moving, according to the rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal.(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 18. The mobile terminal according to claim 11, wherein the processor is further configured to provide prompt information that is used to instruct to rotate the mobile terminal when it is detected that the trigger instruction is input by the input device.(String), 1(Integer), 17(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 19. The mobile terminal according to claim 18, wherein the processor is further configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed before providing the prompt information that is used to instruct to rotate the mobile terminal, and wherein the processor is specifically configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal by providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction.(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184986(Integer), 20. The mobile terminal according to claim 11, wherein the minimum displacement is calculated according to an equation:s=d⁢φ1φ2,wherein s is the minimum displacement, d is the width of the panoramic photo, φ1 is the preset rotation angle threshold, and wherein φ2 is the rotation angle of the mobile terminal when the panoramic photo is photographed.(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184986(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a continuation of International Application No. PCT/CN2014/079950, filed on Jun. 16, 2014, which is incorporated herein by reference in its entirety. TECHNICAL FIELD [0002]The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present invention provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is specifically configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is specifically configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is specifically configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is specifically configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is specifically configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is specifically configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is specifically configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is specifically configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is specifically configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is specifically configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is specifically configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present invention, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present invention. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present invention. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present invention. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present invention. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present invention. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present invention. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present invention. [0046]FIG. 10A to FIG. 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. The described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present invention, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present invention, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. The method may be performed by a mobile terminal, or specifically by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps: [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present invention, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present invention, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present invention, there may be multiple implementation manners for specifically implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present invention in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. The method may be performed by a mobile terminal, or specifically by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps: [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present invention, a user may input, by using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present invention, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present invention, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present invention, in order to implement immersive mode browsing, the user needs to rotate the mobile terminal, so that the panoramic photo can move as the mobile terminal rotates. Generally, for better browsing of the panoramic photo, the prompt information t(String), 相关申请的交叉引用 [0001] 本申请是 2014 年 6 月 16 日提交的国际申请号 PCT/CN2014/079950 的延续,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及通信技术领域,尤其涉及一种全景照片在移动终端中的呈现方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,移动终端的使用范围和环境也越来越多样化。 例如,目前很多移动终端,如手机、个人数字助理、个人电脑等都具有全景拍摄的功能。 [0004] 当移动终端进行全景拍摄时,用户旋转移动终端拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 然后可以将多张拍摄的照片按照上述的拼接原理拼接成一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,会在全景照片上浏览到比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端中呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作较为复杂。 概括 [0006] 本发明实施例提供一种全景照片在移动终端中的呈现方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 第一方面,提供了一种全景照片在移动终端中的呈现方法,包括:检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为浏览模式。 其中全景照片随着移动终端的旋转而移动,若检测到触发指令,则检测并确定移动终端的旋转角度,根据确定的旋转角度移动呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实现方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009] 结合第一方面的第一种实现方式,在第二种实现方式中,所述确定移动终端在旋转过程中所处的放置方向包括检测移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考的Z轴 三维坐标系垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于参考三维X-Y平面方向的夹角确定- 维度坐标系,移动终端在旋转过程中所处的放置方向。 [0010]结合第一方面的第二种实现方式,在第三种实现方式中,所述根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为竖直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0011] 结合第一方面的第二种实现方式或第一方面的第三种实现方式,在第四种实现方式中,所述根据放置方向确定移动终端的旋转角度包括: 其中,旋转过程中移动终端所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为旋转过程中移动终端对应的轴向。 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者判断旋转过程中移动终端所处的放置方向为竖直放置方向 ,将参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 分别以轴向为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实现方式,在第五种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013] 结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括确定: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动终端中以正常模式呈现的全景照片移动包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实现方式中,所述检测确定移动终端的旋转角度之前,还包括提供用于指示旋转移动终端的提示信息。 [0015] 结合第一方面的第七种实现方式,在第八种实现方式中,所述提供用于指示旋转移动终端的提示信息之前,所述方法还包括: 获取旋转时保存的移动终端的旋转方向。 拍摄全景照片,提供用于指示旋转移动终端的提示信息包括:根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0016]第二方面,提供了一种全景照片在移动终端中的呈现装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,所述触发指令用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元,所述沉浸式浏览模式为全景照片随着移动终端移动的浏览模式。 旋转,所述判断单元,用于接收检测单元发送的检测结果,若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送给呈现单元,呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0017] 结合第二方面,在第一种实现方式中,所述确定单元具体用于通过以下方式确定所述移动终端的旋转角度,确定所述移动终端在旋转过程中所处的放置方向,以及 根据放置方向确定移动终端的旋转角度。 [0018] 结合第二方面的第一种实现方式,在第二种实现方式中,所述确定单元具体用于通过以下方式确定所述移动终端在检测角度的旋转过程中所处的放置方向 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 位于,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端所在的放置方向 d 在旋转过程中。 [0019] 结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元具体用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,通过如下方式确定: 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向相对于参考的X-Y平面方向的夹角 三维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面方向大于45度,确定 其中,旋转过程中移动终端所处的放置方向为水平放置方向。 [0020]结合第二方面的第二种实现方式或第二方面的第三种实现方式,在第四种实现方式中,所述确定单元具体用于通过如下方式确定所述移动终端的旋转角度: 放置方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴向 旋转过程中的移动终端,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向 旋转过程为垂直放置方向,使用X轴方向或Y轴方向 参考三​​维坐标系中的s作为移动终端在旋转过程中对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实现方式,在第五种实现方式中,所述装置还包括判断单元,所述判断单元根据所述确定的旋转角度,在所述呈现单元移动前,确定所述全景图 在移动终端中以正常模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元还用于在所述呈现单元根据确定的旋转角度移动之前,以正常模式呈现的全景照片处于 移动终端,根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 呈现单元,具体用于如下移动移动终端中正常模式呈现的全景照片,使全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0023] 结合第二方面,在第七种实现方式中,所述装置还包括提示单元,所述提示单元用于接收所述检测单元发送的检测结果; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示旋转移动终端的提示信息。 [0024] 结合第二方面的第七种实现方式,在第八种实现方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄所述全景照片时保存的所述移动终端的旋转方向 , 向提示单元发送获取的拍摄照片时保存的移动终端的旋转方向, 提示单元具体用于通过以下方式提供提示信息, 用于指示 旋转移动终端,根据获取单元获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0025]第三方面,提供了一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于在检测到输入设备输入触发指令时,根据检测确定的旋转角度移动移动终端中以正常模式呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实现方式,在第二种实现方式中,所述传感器具体用于通过以下方式,在检测角度的旋转过程中,确定所述移动终端所处的放置方向 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 定位,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端在ro中的放置方向 化过程。 [0028] 结合第三方面的第二种实现方式,在第三种实现方式中,所述传感器具体用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,采用如下方式确定: 参考三​​维坐标系的X-Y平面,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角时,移动终端在旋转过程中所处的放置方向- 维度坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于方向的夹角为 参考三​​维坐标系的X-Y平面大于45度,确定t 移动终端在旋转过程中所处的放置方向为水平放置方向。 [0029]结合第三方面的第二种实现方式或第三方面的第三种实现方式,在第四种实现方式中,所述传感器具体用于通过以下方式,根据所述移动终端的旋转角度确定所述移动终端的旋转角度。 放置方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴向 旋转过程中的移动终端,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向 旋转过程为垂直放置方向,在旋转过程中使用X轴方向或Y轴方向 在旋转过程中参考三维坐标系作为移动终端对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,移动所述移动设备中以正常模式呈现的全景照片。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于,在移动终端中以正常模式呈现的全景照片根据确定的旋转角度移动之前,确定 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 所述处理器,具体用于移动终端中正常模式下呈现的全景照片的移动方式, 使全景照片沿与移动终端的旋转方向相反的方向移动最小位移 . [0032] 结合第三方面,在第七种实现方式中,处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示所述移动终端旋转的提示信息之前,获取所述移动终端的旋转方向,即 拍摄全景照片时保存, 处理器具体用于按照以下方式提供用于指示旋转移动终端的提示信息, 提供用于指示旋转移动终端的提示信息 到获得的旋转方向。 [0034] 本发明实施例提供的一种移动终端全景照片呈现方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测到,检测并确定移动终端的旋转角度; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 通过本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,简单方便。 操作。 附图说明 [0035]为了更加清楚地描述本发明实施例中的技术方案,下面对实施例描述中所需要的附图进行简单介绍。 [0036] 图1为本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一种实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端的旋转角度的过程的示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所处放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实现示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实现示意图。 [0043] 图8为本发明实施例的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例的全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例的全景照片浏览过程的实现示意图。 [0046] 图10A至图10D为本发明实施例的移动终端中全景照片呈现装置的结构示意图。 [0047] 图11为本发明实施例的移动终端的结构示意图。 具体实施方式 [0048] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 本发明实施例提供的移动终端中全景照片的呈现方法,全景照片随着移动终端的旋转而移动。 本发明实施例中为了描述方便,将全景照片随着移动终端的旋转而移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为 以下简称正常模式,当然不限于此; 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览以普通模式显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 该方法可以由移动终端执行,或者具体可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤: [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 本发明实施例中,若检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :根据S中确定的旋转角度移动并呈现 102 ,移动终端正常显示的全景照片。 [0055] 本发明实施例提供的移动终端中全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 通过本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,简单方便。 操作。 [0056] 在本发明实施例中,具体实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在用户触发移动终端进入沉浸式浏览模式后立即以预定方式旋转移动终端,该预定方式可以例如通过用户手册预先学习得到。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示旋转移动终端的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供用于指示旋转移动终端的提示信息的实现方式为例,对全景照片在移动终端中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的全景照片在移动终端中的呈现方法的另一种实现流程图。 该方法可以由移动终端执行,或者具体可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤: [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,本发明实施例可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 启用控件的启用状态用于确定是否启用沉浸式浏览模式,当检测到启用控件被启用时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面设置沉浸式浏览按钮。 When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选地,本发明实施例还可以在检测到用户正在浏览全景照片时,提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片随着移动终端的旋转而移动。 通常,为了更好的浏览全景照片,可以提供用于指示旋转移动终端的提示信息,以告知用户移动终端需要按照预设方向进行旋转,该预设方向可以为 例如,从左向右旋转,当然,也可以从右向左旋转。 [0064] 在本发明实施例中,所提供的提示信息可以是在显示界面上显示的文本信息,当然,也可以是通过语音输出的方式通知的语音信息,本发明实施例对此不作具体限定。 . [0065] 可选地,本发明实施例还可以获取拍摄全景照片时保存的移动终端的旋转方向,并以提示信息的形式通知获取的旋转方向。 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,提示用户根据获取的拍摄全景照片时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,从而及时控制全景照片移动。 [0068] 用户在拍摄全景照片时,一般会将移动终端定位在确定的放置方向上。 但是,用户在浏览全景照片时,很可能会使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了更准确地浏览全景照片,可以根据移动终端在旋转过程中所处的放置方向来确定移动终端的旋转角度。 [0069] S中移动终端旋转角度的确定过程 203 本发明实施例可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 在本发明实施例中,可以利用设置在移动终端中的重力传感器指示的移动终端的重力方向来确定移动终端所在的放置方向,移动终端的旋转角度为 通过使用布置在移动终端中的陀螺仪传感器的角度来确定。 可选地,在本发明实施例中,用于确定移动终端的放置方向的重力传感器和用于确定移动终端的旋转角度的陀螺仪传感器可以在用于指示移动终端的触发指令时被启用。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选地,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤: [0074] 小号 2031 a :以移动终端屏幕所在平面为基准,建立参考三维坐标系。 [0075]本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面平行于该平面 移动终端屏幕所在平面,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也根据移动终端的不同放置方向进行旋转。 例如,参考三维坐标系的示意图分别对应图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的夹角 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过在S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选地,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于基准三的X-Y平面方向的夹角时- 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为竖直放置方向。 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所处的放置方向 旋转过程中为水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为竖直放置方向,或者为水平放置方向,本发明实施例具体可以设置为竖直放置方向。 [0081] 本发明实施例中,如果通过移动终端的重力方向相对于参考三的X-Y平面方向的夹角确定旋转过程中移动终端所处的放置方向 S中的维坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 : [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 本发明实施例在确定移动终端在旋转过程中所处的放置方向为水平放置方向时,采用参考三维坐标系中Z轴的方向 作为移动终端在旋转过程中对应的轴向; 或者,当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 用作移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,本发明实施例中,上述移动终端在旋转过程中对应的轴向仅仅是为了简化确定移动终端旋转角度的过程,具体的确定方式不作限定。 至此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺仪传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于对应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度移动移动终端正常显示的全景照片。 [0088] 本发明实施例中,在浏览全景照片时,一般先以普通浏览方式显示全景照片; 例如,可以是分辨率较低的全景照片,或者只有全景照片的最左部分或全景照片的最右部分等部分全景照片显示在手机的显示屏中 终端。 本发明实施例在确定移动终端的旋转角度后,可以移动终端中正常模式显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实现方式来移动移动终端中正常模式下显示的全景照片。 例如,移动终端在正常模式下显示的全景照片可以沿与移动终端的旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,本发明实施例中,为了实现全景照片的平滑移动,可以预先设置一个旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现了全景照片的平滑移动。 如果没有达到预设的旋转角度阈值,全景照片可能不会被移动。 [0091] 本发明实施例中,根据确定的移动终端的旋转角度,移动终端中正常模式下显示的全景照片在S中沿与移动终端旋转方向相反的方向移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端的旋转方向相同的方向移动时,也可以采用类似的方式): [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,则执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常模式显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,在本发明实施例中,为了进一步增强平滑移动的效果,还可以确定最小位移,当控制全景图像沿与移动终端的旋转方向相反的方向移动时, 照片每次移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,可以根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度以及全景照片沿a的照片宽度,确定全景照片的最小位移量。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录并保存,可以是 直接从本发明实施例拍摄全景照片时保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选地,在本发明实施例中,确定全景照片的最小位移可以采用以下方式。 全景照片的最小位移根据公式确定 [0097] s = d ⁢ φ 1 φ 2 , 其中s是全景照片的最小位移; d为全景照片的照片宽度; φ 1 为预设旋转角度阈值; φ2为拍摄全景照片时移动终端的旋转角度。 [0098] 本发明实施例中,对于浏览的全景照片,在确定为全景照片时,全景照片的照片宽度d和拍摄全景照片时移动终端的旋转角度φ2为固定值(如果 在拍摄全景照片的过程中记录了旋转角度φ2,使用记录的值;如果在拍摄过程中没有记录旋转角度φ2,则可以参考一些参考值,例如180度或360度作为旋转角度。 角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,适当的旋转角度阈值φ 1 可能是预设的。 若预设旋转角度阈值φ 1 固定后,确定全景照片在旋转过程中移动的最小位移量。 在浏览全景照片的过程中,实时检测并判断移动终端的旋转角度,如果判断移动终端的旋转角度达到预设的旋转角度阈值φ 1 ,全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0099] 本发明实施例中,移动终端的旋转角度可以为移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,可以认为上一次移动全景照片时移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为持续执行并重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值φ 1,可以将移动终端的初始旋转角度设置为0,检测并确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值来移动全景照片。 例如,移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 −1度,全景照片不动; 当移动端旋转到φ 1 度,全景照片移动最小位移,重新设置旋转角度,继续检测移动端的旋转角度; 当移动端旋转到φ 1 度,全景照片再次移动最小位移,如此循环直到移动终端停止转动。 [0100] 进一步地,本发明实施例中移动全景照片的过程可以为立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,则移动全景照片 ; 例如,预设的旋转角度阈值φ 1 为5度,当旋转角度达到5度时,全景照片移动到最小位移。 移动全景照片的过程也可以是延时执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后,在一段时间内将全景照片移动最小位移量 临界点。 [0101] 移动终端的旋转角度还可以为移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以为a 随着用户移动移动终端不断积累价值。 此时,可以设置全景照片移动的位移与旋转角度成正比关系。 即,移动终端旋转角度越大,全景照片移动的位移越大,移动终端旋转角度越小,全景照片移动的位移越小。 [0102] 上述移动全景照片的方式和最小位移的确定方式还可以有其他实施方式,本发明不对其具体实施方式进行限定。 [0103] 小号 205 :以沉浸式浏览方式呈现全景照片。 [0104] 本发明实施例在沉浸式浏览方式下实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种全景照片的呈现方式可以采用现有的实施方案,例如,在呈现全景照片时,在将全景照片适配显示屏尺寸的过程中可以采用现有的实施方式。 [0105]本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移并呈现。 通过本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,而不需要手动在移动终端的屏幕上滑动浏览全景照片,简单易行。 操作方便。 [0106] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,当然本发明不限于此。 [0107] 本发明实施例提供的控制全景照片在移动终端中呈现的方法的实现基于拍摄全景照片时保存的照片参数,该照片参数例如为: 拍摄全景照片时移动终端旋转,移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的移动终端中全景照片的呈现方法,在拍摄全景照片时,该方法也可以区别于现有的全景照片拍摄。 本发明以下实施例将结合实际案例举例说明全景照片的拍摄过程和浏览过程。 [0108] 图9A示出了根据本发明实施例的拍摄全景照片的过程的实现示意图。 如图9A所示,实现过程包括以下步骤: [0109] 小号 301 :启用全景拍摄模式。 [0110] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0111] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0112] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0113] 本发明实施例中,可以通过陀螺仪传感器在S中启动的角度来确定移动终端的旋转角度。 302 旋转。 [0114] 小号 305 :保存拍摄的全景照片的属性信息。 [0115] 本发明实施例中,保存的全景照片的属性信息至少包括照片类型、拍摄角度和照片尺寸,其中,照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0116] 可选地,本发明实施例中,保存的全景照片的属性信息还可以包括拍摄全景照片时移动终端的旋转方向,该旋转方向例如可以为从右向左, 当然,也可能是从左到右。 [0117] 图9B示出了根据本发明实施例的全景照片浏览过程的实现示意图。 如图9B所示,实现过程包括以下步骤: [0118] 小号 401 :检测用户浏览的照片类型。 [0119] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行S 403 ; 否则,以正常的照片浏览方式浏览照片。 [0120] 小号 403 :当检测到用户触发了用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0121] 小号 404 :用户通过旋转移动端浏览全景照片。 [0122] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 具体的确定过程可以参见前述实施例的相关描述。 [0123] 小号 406 :根据S中确定的放置方向,确定移动终端在相应轴向的旋转角度 405 以及陀螺仪传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端在Z方向上旋转的角度 -轴,当移动终端的放置方向为竖直放置方向时,确定移动终端在X轴或Y轴方向上旋转的角度。 [0124] 小号 407 :判断旋转角度是否在S中确定 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0125] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移量。 [0126] 小号 409 :检测移动终端的放置方向和旋转角度; 当移动端的放置方向改变时,执行S 405 ,当旋转角度发生变化时,执行S 407 . [0127] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,从而及时调整全景照片的移动。 [0128] 本发明实施例提供的移动终端中全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 通过本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动滑动。 在移动终端屏幕上浏览全景照片。 [0129] 基于上述实施例提供的移动终端中全景照片的呈现方法,本发明实施例还提供一种装置 900 用于在移动终端呈现全景照片。 如图 10A 所示,该装置 900 包括一个检测单元 901 , 决定单位 902 , 和一个呈现单元 903 . [0130] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元 902 ,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动的浏览模式。 [0131] 决定单位 902用于接收检测单元发送的检测结果 901 ; 若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的移动终端的旋转角度发送给呈现单元 903 . [0132] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0133] 在第一种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端的旋转角度,确定移动终端在旋转过程中所处的放置方向,并根据放置方向确定移动终端的旋转角度。 [0134] 在第二种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端在旋转过程中所处的放置方向: 检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角 -维坐标系,其中参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于 移动终端屏幕所在的平面; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0135] 在第三种实施方式中,确定单元 902 具体用于,通过如下方式,根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端的放置方向 定位旋转过程:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 端子位于旋转过程中是垂直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0136] 在第四种实施方式中,所述确定单元 902 具体用于通过以下方式根据放置方向确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向 维坐标系作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 l以相对于轴向为移动终端的旋转角度旋转。 [0137] 在第五种实施方式中,所述装置还包括判断单元 904, 如图 10B 所示, 在呈现单元之前 903 判断单元根据确定的旋转角度移动移动终端中正常模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0138] 在第六种实施方式中,所述确定单元 902 还配置在呈现单元之前 903 移动,根据确定的旋转角度移动终端中正常模式下呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,全景时移动终端的旋转角度 拍摄全景照片时,全景照片沿移动终端旋转方向的照片宽度,以及呈现单元 903 具体用于如下所述移动移动终端中正常模式下呈现的全景照片,将全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量。 [0139] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供用于指示旋转移动终端的提示信息。 [0140] 在第八种实施方式中,所述装置还包括获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,并发送给提示单元 905 ,获取拍照时保存的移动终端的旋转方向,以及提示单元 905 具体用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取单元获取的旋转方向提供用于指示旋转移动终端的提示信息 906 . [0141] 需要说明的是,对于本发明实施例图10A至图10D提供的全景照片在移动终端中的呈现装置,如果具体实现全景照片在移动终端中的呈现过程不是 描述的不够详细,可以参见方法实施例的相关描述,在此不再赘述。 [0142] 本发明实施例提供的移动终端中全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 通过本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动滑动。 在移动终端屏幕上浏览全景照片。 [0143] 基于上述实施例提供的全景照片在移动终端中的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动端 1000 包括一个输入设备 1001 , 一个传感器 1002 , 处理器 1003 , 和一个显示屏 1004 ,其中输入设备 1001 用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,所述传感器 1002 用于检测移动终端的旋转角度,处理器1003 用于当检测到输入设备输入触发指令时 1001 ,根据检测确定的旋转角度移动移动终端中正常模式呈现的全景照片,显示屏幕 1004 用于呈现全景照片。 [0144] 本发明实施例中,输入设备可以是一个或多个 1001 ,例如,输入设备 1001 可能是显示屏或按钮,可能与处理器集成在一起 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可能连接到处理器 1003 使用有线连接(例如电缆/端口)或无线连接(例如蓝牙)。 [0145] 处理器 1003 可以在单芯片、多芯片或多个电子元件上实现,可以采用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0146] 可能有一个或多个传感器 1002 ,其中传感器 1002 可能有也可能没有运算处理功能。 例如,传感器 1002 本发明实施例中可以为重力传感器和陀螺仪传感器中的至少一种。 [0147] 在本发明的这个实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0148] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0149] 第二种实现方式,传感器 1002 具体用于通过以下方式确定移动终端在旋转过程中所处的放置方向: 检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角 -维坐标系,其中参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于 移动终端屏幕所在的平面; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0150] 第三种实现方式,传感器 1002 具体用于,通过如下方式,根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端的放置方向 定位旋转过程:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 终端在旋转过程中所处位置为竖直放置方向,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,确定: 移动终端在旋转过程中所处的放置方向为水平放置方向 节。 [0151] 在第四种实现方式中,传感器 1002 具体用于通过以下方式根据放置方向确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向 维坐标系作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 l以相对于轴向为移动终端的旋转角度旋转。 [0152] 在第五种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,将在移动终端中以正常模式呈现的全景照片确定移动终端的旋转角度达到预设的旋转角度阈值。 [0153] 在第六种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移, 拍摄全景照片时的移动终端,以及拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度,以及处理器 1003 具体用于移动终端中正常模式下呈现的全景照片的移动方式: 将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0154] 在第七种实现方式中,处理器 1003 还用于当检测到输入设备输入触发指令时 1001 ,提供用于指示旋转移动终端的提示信息。 [0155] 在第八种实现方式中,处理器 1003 还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,处理器 1003 用于指示旋转移动终端的提示信息,具体用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0156] 需要说明的是,对于本发明实施例图11提供的移动终端,具体实现控制全景照片在移动终端中显示的过程如果描述的不够详细,可以参考 方法实施例的相关描述,此处不再赘述。 [0157] 本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片随着移动终端的旋转而移动。 通过本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动滑动。 在移动终端屏幕上浏览全景照片。 [0158]本领域的技术人员应该理解,本发明的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本发明可以采用纯硬件实施例、纯软件实施例或结合软件和硬件的实施例的形式。 此外,本发明可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0159] 参考根据本发明实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图描述了本发明。 应当理解,可以使用计算机程序指令来实现流程图和/或框图中的每个过程和/或每个框以及流程图和/或框图中的过程和/或框的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器生成机器,使得任何计算机或处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0160] 这些计算机程序指令也可以存储在计算机可读存储器中,该计算机可读存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,使得存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程中和/或在框图中的一个或多个块中实现特定功能。 [0161] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程数据处理设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供了用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0162] 以上虽然描述了本发明的一些优选实施例,但是本领域的技术人员在了解了基本的发明构思后,可以对这些实施例进行更改和变型。 因此,所附权利要求旨在被解释为涵盖优选实施例以及落入本发明范围内的所有改变和修改。 [0163] 显然,本领域的技术人员可以对本发明实施例进行各种更改和变型而不脱离本发明实施例的范围。 本发明旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9621802B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), CA2966400A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), CA2966400C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), CN104471519A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.475 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), CN104471519B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), CN110650241A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), CN110650241B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US10222877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US10649546B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US11126275B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US20150363915A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US20170212609A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US20190171300A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US20200241657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), US9621802B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270668(Integer), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9621802B2(String), US9621802B2(String), 1491840000(Integer), 270668(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184986(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184986(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184986(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184986(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.636 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.636 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10222877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10222877B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US15/483724(String), 1491753600(Integer), US10222877B2(String), 1551715200(Integer), 1551715200(Integer), 美国(String), 4(Integer), 8(Integer), 47(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20070263995A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9729788B2 | US9894272B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184987(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\17c4852a1bf3465b9412b79dfe602382.png(String), 184987(Integer), 17c4852a1bf3465b9412b79dfe602382.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10222877B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US15/483724(String), 1491753600(Integer), US10222877B2(String), 1551715200(Integer), 1551715200(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 47(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20070263995A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9729788B2 | US9894272B2(String), \20230420\17c4852a1bf3465b9412b79dfe602382.png(String), 20(Integer), 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.700 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 1. A method of presenting a panoramic photo in a mobile terminal, comprising:photographing a panoramic photo with the mobile terminal moving along one direction;receiving an instruction of entering an immersive browsing mode; andunder the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating along an axis of a plane with a first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating along the axis of the plane with the first direction, the plane being a plane of a screen of the mobile terminal;detecting the mobile terminal rotating along the axis with a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating along the axis with the second direction, the first direction being the same as the direction of the mobile terminal when the panoramic photo is photographed, the second direction being opposite to the first direction, the second part of the panoramic photo being different from the first part of the panoramic photo, and the third part of the panoramic photo being different from the first part of the panoramic photo.(String), 1.如权利要求10所述的移动终端,其中移动终端从左向右移动,或从右向左移动拍摄全景照片。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 2. The method of claim 1, wherein the panoramic photo is photographed with the mobile terminal moving from left to right, or moving from right to left.(String), 12.如权利要求11所述的移动终端,其中全景照片的第一部分是全景照片的最左侧部分或全景照片的最右侧部分。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 3. The method of claim 2, wherein the first part of the panoramic photo is the leftmost part of the panoramic photo or the rightmost part of the panoramic photo.(String), 13.如权利要求10所述的移动终端,其中在移动终端从左向右移动拍摄全景照片的情况下,第二部分在第一部分的右侧,第三部分在第一部分的左侧。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 4. The method of claim 1, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from left to right, the second part is to the right of the first part, and the third part is to the left of the first part.(String), 14.如权利要求10所述的移动终端,其中在移动终端从右向左移动拍摄全景照片的情况下,第二部分在第一部分的左侧,第三部分在第一部分的右侧。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 5. The method of claim 4, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from right to left, the second part is to the left of the first part, and the third part is to the right of the first part.(String), 15.如权利要求10所述的移动终端,其中指令使移动终端进一步执行:以正常模式显示全景照片;在正常模式下显示图标;检测图标上的输入;和响应于检测到图标上的输入而进入沉浸式浏览模式。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 6. The method of claim 1, further comprising:displaying the panoramic photo in a normal mode;displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 16.如权利要求10所述的移动终端,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 7. The method of claim 1, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 17.如权利要求10所述的移动终端,其中移动终端沿轴的旋转由移动终端的陀螺仪传感器检测。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 8. The method of claim 1, wherein rotation of the mobile terminal along the axis is detected by a gyro sensor of the mobile terminal.(String), 18.如权利要求10所述的移动终端,其中该轴线平行于移动终端屏幕的一侧,并横跨移动终端的中心。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 9. The method of claim 1, wherein the axis is parallel to a side of the screen of the mobile terminal and is across a center of the mobile terminal.(String), 19.一种非暂时性计算机可读存储介质包括当由移动终端执行时,使移动终端执行以下步骤的指令:移动终端沿一个方向移动拍摄全景照片;接收进入沉浸式浏览模式的指令;和沉浸式浏览模式下:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向的平面轴旋转;响应于检测到移动终端沿第一方向的平面的轴旋转显示全景照片的第二部分,该平面为移动终端的屏幕平面;检测移动终端沿第二方向的轴旋转;和响应于检测到移动终端以第二方向沿轴旋转显示全景照片的第三部分,第一方向与拍摄全景照片时移动终端的方向相同,第二方向与第一方向,第二部分全景照片不同于第一部分全景照片,第三部分全景照片不同于第一部分全景照片。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 10. A mobile terminal, comprising:one or more processors;a screen coupled to the one or more processors;a camera coupled to the one or more processors;a sensor coupled to the one or more processors; anda memory coupled to the one or more processors and comprising instructions that when executed by the one or more processors, cause the mobile terminal to perform:photographing a panoramic photo with the mobile terminal moving along one direction;receiving an instruction of entering an immersive browsing mode; andunder the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating along an axis of a plane with a first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating along the axis of the plane with the first direction, the plane being a plane of a screen of the mobile terminal;detecting the mobile terminal rotating along the axis with a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating along the axis with the second direction, the first direction being the same as the direction of the mobile terminal when the panoramic photo is photographed, the second direction being opposite to the first direction, the second part of the panoramic photo being different from the first part of the panoramic photo, and the third part of the panoramic photo being different from the first part of the panoramic photo.(String), 20.如权利要求19所述的非暂时性计算机可读存储介质,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 11. The mobile terminal of claim 10, wherein the panoramic photo is photographed with the mobile terminal moving from left to right, or moving from right to left.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 12. The mobile terminal of claim 11, wherein the first part of the panoramic photo is the leftmost part of the panoramic photo or the rightmost part of the panoramic photo.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 13. The mobile terminal of claim 10, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from left to right, the second part is to the right of the first part, and the third part is to the left of the first part.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 14. The mobile terminal of claim 10, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from right to left, the second part is to the left of the first part, and the third part is to the right of the first part.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 15. The mobile terminal of claim 10, wherein the instructions cause the mobile terminal to further perform:displaying the panoramic photo in a normal mode;displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 16. The mobile terminal of claim 10, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 17. The mobile terminal of claim 10, wherein rotation of the mobile terminal along the axis is detected by a gyro sensor of the mobile terminal.(String), 1(Integer), 16(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 18. The mobile terminal of claim 10, wherein the axis is parallel to a side of the screen of the mobile terminal and is across a center of the mobile terminal.(String), 1(Integer), 17(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 19. A non-transitory computer-readable storage medium comprising instructions which, when executed by a mobile terminal, cause the mobile terminal to carry out the following steps:photographing a panoramic photo with the mobile terminal moving along one direction;receiving an instruction of entering an immersive browsing mode; andunder the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating along an axis of a plane with a first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating along the axis of the plane with the first direction, the plane being a plane of a screen of the mobile terminal;detecting the mobile terminal rotating along the axis with a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating along the axis with the second direction, the first direction being the same as the direction of the mobile terminal when the panoramic photo is photographed, the second direction being opposite to the first direction, the second part of the panoramic photo being different from the first part of the panoramic photo, and the third part of the panoramic photo being different from the first part of the panoramic photo.(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184987(Integer), 20. The non-transitory computer-readable storage medium of claim 19, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184987(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 14/735,625 filed Jun. 10, 2015, now U.S. Pat. No. 9,621,802, which is a continuation of International Patent Application No. PCT/CN2014/079950, filed on Jun. 16, 2014. All of the afore-mentioned patent applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present disclosure. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present disclosure. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present disclosure. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present disclosure. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present disclosure. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present disclosure. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present disclosure. [0046]FIGS. 10A, 10B, 10C, and 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present disclosure, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present disclosure, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps. [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present disclosure, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present disclosure, there may be multiple implementation manners for implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present disclosure in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps. [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present disclosure, a user may input, using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present disclosure, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present disclosure, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present disclosure, in order to implement immersive mode browsing, the user needs to rotate the mobile terminal, so that the panoramic photo can move as the mobile terminal rotates. Generally, for better browsing of the panoramic phot(String), 相关申请的交叉引用 [0001] 本申请是美国专利申请系列的延续。 2015 年 6 月 10 日提交的第 14/735,625 号,现为美国专利。 美国专利第 9,621,802 号是 2014 年 6 月 16 日提交的国际专利申请第 PCT/CN2014/079950 号的延续。所有上述专利申请均以引用方式全文并入本文。 技术领域 [0002] 本发明涉及通信技术领域,尤其涉及一种在移动终端中呈现全景照片的方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,使用移动终端的范围和环境也越来越多样化。 例如,目前手机、个人数字助理、个人电脑等很多移动终端都具备全景拍照功能。 [0004] 当移动终端进行全景拍摄时,用户转动移动终端来拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 再根据上述拼接原理,可以将多张拍摄的照片拼接为一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,可以浏览全景照片上比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作相对复杂。 概括 [0006] 本发明实施例提供一种在移动终端中呈现全景照片的方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 根据第一方面,提供了一种在移动终端中呈现全景照片的方法,包括检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为 全景照片随着移动终端旋转移动,若检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实施方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009] 结合第一方面的第一种实现方式,在第二种实现方式中,确定移动终端在旋转过程中所处的放置方向包括:检测移动终端的重力方向相对于移动终端的角度。 参考三​​维坐标系的X-Y平面方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考坐标系的Z轴 三维坐标系垂直于移动终端屏幕所在的平面,根据移动终端重力方向相对于参考三坐标X-Y平面方向的夹角确定 三维坐标系,移动终端在旋转过程中所处的放置方向。 [0010] 结合第一方面的第二种实现方式,在第三种实现方式中,根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为垂直放置方向; 当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,确定移动终端所在的放置方向为旋转 工艺是水平放置方向。 [0011] 结合第一方面的第二种实施方式或第一方面的第三种实施方式,在第四种实施方式中,根据放置方向确定移动终端的旋转角度包括:如果确定放置方向 其中移动终端在旋转过程中所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向; 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端在旋转过程中所处的放置方向为垂直放置方向 ,以参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并以移动终端旋转的角度为 相对于轴向作为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实施方式,在第五种实施方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013] 结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动在移动终端中以正常模式呈现的全景照片,包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实施方式中,在检测确定移动终端的旋转角度之前,还包括:提供用于指示移动终端旋转的提示信息。 [0015] 结合第一方面的第七种实施方式,在第八种实施方式中,在提供用于指示移动终端旋转的提示信息之前,该方法还包括:获取移动终端的旋转方向。 拍摄全景照片, 提供用于指示移动终端旋转的提示信息包括: 提供用于指示根据获取的旋转方向旋转移动终端的提示信息。 [0016] 第二方面,提供了一种在移动终端中呈现全景照片的装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送至确定单元,沉浸式浏览模式为全景照片随着移动终端移动的浏览模式 旋转时,确定单元,用于接收检测单元发送的检测结果,如果检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送到呈现单元, 呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度,移动并呈现移动终端中正常呈现的全景照片。 [0017] 结合第二方面,在第一种实施方式中,确定单元用于确定移动终端的旋转角度如下:确定移动终端在旋转过程中所处的放置方向,确定 移动终端根据放置方向的旋转角度。 [0018] 结合第二方面的第一种实施方式,在第二种实施方式中,所述确定单元,用于通过以下方式确定所述移动终端在检测角度的旋转过程中所处的放置方向。 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,其中,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面。 参考三​​维坐标系的Z轴垂直于移动终端屏幕所在的平面,根据移动终端的重力方向相对于该移动终端的角度确定 参考三​​维坐标系的X-Y平面方向,移动终端在轮播中所处的放置方向 化过程。 [0019] 结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元,用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,采用如下方式确定。 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向与参考三坐标的X-Y平面方向的夹角时 -维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为垂直放置方向,当移动终端的重力方向相对于该方向的夹角时 参考三​​维坐标系的 X-Y 平面的夹角大于 45 度,确定 th 移动终端在旋转过程中所处的放置方向为水平放置方向。 [0020]结合第二方面的第二种实施方式或第二方面的第三种实施方式,在第四种实施方式中,所述确定单元,用于根据以下方式确定所述移动终端的旋转角度: 放置方向如果确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所在的放置方向在 旋转过程是垂直放置方向,使用参考中的X轴方向或Y轴方向 以三维坐标系作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实施方式,在第五种实施方式中,所述装置还包括判断单元,所述判断单元在所述呈现单元移动之前,根据所述确定的旋转角度,确定所述全景图。 在移动终端中以普通模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元,还用于在所述呈现单元移动之前,根据所述确定的旋转角度,将正常模式下呈现的全景照片在 移动终端,根据预设的旋转角度阈值、全景照片拍摄时移动终端的旋转角度、全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 所述呈现单元,用于将所述移动终端以正常模式呈现的所述全景照片沿与所述移动终端的旋转方向相反的方向移动所述全景照片最小位移。 [0023] 结合第二方面,在第七种实施方式中,所述装置还包括提示单元,所述提示单元,用于接收所述检测单元发送的检测结果。 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0024] 结合第二方面的第七种实施方式,在第八种实施方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄全景照片时保存的所述移动终端的旋转方向。 ,并将获取的拍摄照片时保存的移动终端的旋转方向发送给提示单元, 提示单元用于以如下方式提供用于指示旋转的提示信息 移动终端提供提示信息,用于指示移动终端根据获取单元获取的旋转方向进行旋转。 [0025]第三方面,提供一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,所述沉浸式浏览模式为全景照片随着移动终端旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于当检测到输入设备输入触发指令时,根据检测确定的旋转角度,移动移动终端中正常呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实施方式,在第二种实施方式中,所述传感器用于通过如下方式确定所述移动终端在检测重力角的旋转过程中所处的放置方向 移动终端的方向相对于参考三维坐标系的X-Y平面的方向,其中,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 ,参考三维坐标系的Z轴与移动终端屏幕所在的平面垂直,根据移动终端的重力方向相对于该方向的夹角确定 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向 s。 [0028] 结合第三方面的第二种实施方式,在第三种实施方式中,所述传感器,用于根据所述移动终端的重力方向相对于X-Y方向的夹角,如下确定: 参考三​​维坐标系平面,移动终端在旋转过程中所处的放置方向,移动终端的重力方向相对于参考三维坐标系X-Y平面方向的夹角 坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为垂直放置方向,当移动终端的重力方向相对于移动终端的方向的夹角时 参考三​​维坐标系的X-Y平面大于45度,确定放置 移动终端在旋转过程中所处的方向为水平放置方向。 [0029]结合第三方面的第二种实施方式或第三方面的第三种实施方式,在第四种实施方式中,所述传感器用于根据所述摆放位置通过如下方式确定所述移动终端的旋转角度 方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所在的放置方向在 旋转过程是垂直放置方向,在参考三中使用一个X轴的方向或者一个Y轴的方向 -维坐标系作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,将正常模式下呈现的全景照片在手机中移动。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,确定在移动终端中以正常模式呈现的全景照片 全景照片根据预设旋转角度阈值的最小位移、全景照片拍摄时移动终端的旋转角度、全景照片拍摄时全景照片沿移动终端旋转方向的照片宽度 所述处理器用于将所述移动终端以正常模式呈现的全景照片沿与所述移动终端的旋转方向相反的方向移动所述全景照片最小位移。 [0032] 结合第三方面,在第七种实施方式中,所述处理器还用于在检测到所述输入设备输入触发指令时,提供用于指示移动终端旋转的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示旋转所述移动终端的提示信息之前,获取所述移动终端的旋转方向为: 在拍摄全景照片时保存, 处理器用于按照如下方式提供用于指示移动终端旋转的提示信息,提供用于指示移动终端旋转的提示信息 获取的旋转方向。 [0034] 根据本发明实施例提供的一种在移动终端中呈现全景照片的方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测,检测确定移动终端的旋转角度; 根据确定的旋转角度,移动并呈现移动终端中正常显示的全景照片。 通过本发明,可以实现全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便 . 附图说明 [0035]为了更清楚地描述本发明实施例中的技术方案,下面简要介绍描述实施例所需的附图。 [0036] 图1是根据本发明实施例的在移动终端中呈现全景照片的方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端旋转角度的过程示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所在放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实施示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实施示意图。 [0043] 图8为本发明实施例提供的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例提供的全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例提供的全景照片浏览过程的实现示意图。 [0046] 图10A、图10B、图10C和图10D是根据本发明实施例的移动终端中全景照片的呈现装置的结构示意图。 [0047] 图11为本发明实施例提供的一种移动终端的结构示意图。 具体实施方式 [0048] 下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚的说明。 以上所述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 根据本发明实施例提供的一种移动终端中全景照片的呈现方法,全景照片随着移动终端的转动而移动。 本发明实施例为了描述方便,将全景照片随移动终端旋转移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为 以下称为正常模式,当然不限于此。 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览正常模式下显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的在移动终端中呈现全景照片的方法的实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤。 [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 在本发明实施例中,如果检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :根据 S 中确定的旋转角度移动并呈现 102 ,在移动端以普通模式显示的全景照片。 [0055] 根据本发明实施例提供的移动终端全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 根据确定的旋转角度,移动并呈现移动终端中正常显示的全景照片。 通过本发明,可以实现全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便 . [0056] 在本发明实施例中,实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在触发移动终端进入沉浸式浏览模式后,立即以预定义的方式旋转移动终端,该预定义的方式例如可以通过预先学习用户手册获得。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示移动终端旋转的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供提示信息用于指示移动终端旋转的实现方式为例,对全景照片在手机中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的在移动终端中呈现全景照片的方法的另一个实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤。 [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 在本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,在本发明实施例中,可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 使能控件的使能状态用于确定是否使能沉浸式浏览模式,当检测到使能控件被使能时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面上设置沉浸式浏览按钮。 在选择进入沉浸式浏览模式浏览全景照片时,用户可以触发按钮,指示移动终端进入沉浸式浏览模式; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选的,在本发明实施例中,还可以在检测到用户正在浏览全景照片时,进一步提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片可以随着移动终端的旋转而移动。 通常,为了更好地浏览全景照片,可以提供用于指示移动终端旋转的提示信息,通知用户移动终端需要按照预设方向进行旋转,其中预设方向可以是 ,例如从左到右旋转,当然,也可能是从右到左旋转。 [0064] 在本发明实施例中,提供的提示信息可以是显示界面上显示的文字信息,当然也可以是通过语音输出通知的语音信息,本发明实施例对此不做限定。 [0065] 可选的,本发明实施例还可以进一步获取拍摄全景照片时保存的移动终端的旋转方向,并将获取的旋转方向以提示信息的形式通知; 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,以提示用户根据获取的全景照片拍摄时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,及时控制全景照片移动。 [0068] 在拍摄全景照片时,用户一般将移动终端定位在确定的放置方向。 然而,在浏览全景照片时,用户很可能使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了比较精确地浏览全景照片,可以根据移动终端在旋转过程中所处的放置方向来确定移动终端的旋转角度。 [0069] S中确定移动终端旋转角度的过程 203 在本发明实施例中,可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 在本发明实施例中,可以通过设置在移动终端中的重力传感器所指示的移动终端的重力方向来确定移动终端所处的放置方向,并确定移动终端的旋转角度。 使用设置在移动终端中的陀螺传感器的角度。 可选地,在本发明实施例中,用于确定移动终端放置方向的重力传感器和用于确定移动终端旋转角度的陀螺传感器可以在用于指示移动终端的触发指令时开启。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选的,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤。 [0074] 小号 2031 a :基于移动终端屏幕所在的平面,建立参考三维坐标系。 [0075]在本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面与该平面平行 移动终端屏幕所在的位置,参考三维坐标系的Z轴垂直于移动终端屏幕所在的平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也会根据移动终端的不同放置方向旋转。 例如,参考三维坐标系的示意图分别对应于图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的角度 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选的,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角时, 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为垂直放置方向; 当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所在的放置方向 在旋转过程中是水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为垂直放置方向,或者为水平放置方向,本发明实施例可以设置为垂直放置方向。 [0081] 在本发明实施例中,如果移动终端在旋转过程中所处的放置方向是通过移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角来确定的, S中的维度坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 . [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 在本发明实施例中,当确定移动终端在旋转过程中所处的放置方向为水平放置方向时,使用参考三维坐标系中的Z轴方向 作为移动终端在旋转过程中对应的轴向; 或者当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 作为移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,在本发明实施例中,上述移动终端在旋转过程中对应的轴向只是为了简化确定移动终端旋转角度的过程,并不限定具体的确定方式 对此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 在本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于相应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度,移动移动终端中正常显示的全景照片。 [0088] 在本发明实施例中,在浏览全景照片时,一般先以普通浏览模式显示全景照片; 例如,可以是分辨率比较低的全景照片,或者只有全景照片的最左边或最右边的部分全景照片显示在手机的显示屏上。 终端。 本发明实施例中,在确定移动终端的旋转角度后,可以移动移动终端中正常模式下显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实现方式来移动移动终端中正常模式下显示的全景照片。 例如,移动终端中以正常模式显示的全景照片可以沿与移动终端旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,在本发明实施例中,为了实现全景照片的平滑移动,可以预先设置旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动终端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现全景照片的平滑移动。 如果未达到预设的旋转角度阈值,则全景照片可能无法移动。 [0091] 在本发明实施例中,根据确定的移动终端的旋转角度,将移动终端中正常模式显示的全景照片沿与移动终端在S中的旋转方向相反的方向移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端旋转方向相同的方向移动时,也可以采用类似方式)。 [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,在本发明实施例中,为了进一步增强平滑移动的效果,还可以进一步确定最小位移,当被控制沿与移动终端旋转方向相反的方向移动时,全景 每次将照片移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,全景照片的最小位移可以根据预设的旋转角度阈值、全景照片拍摄时移动终端的旋转角度、全景照片沿一方向的照片宽度确定。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时沿移动终端旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录保存,可以是 本发明实施例在拍摄全景照片时直接从保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选的,在本发明实施例中,确定全景照片的最小位移可以采用以下方式。 全景照片的最小位移根据公式s=dφ确定 1 /φ 2 ,其中 s 是全景照片的最小位移; d 为全景照片的照片宽度; φ 1 是预设的旋转角度阈值; 和 2 是拍摄全景照片时移动终端的旋转角度。 [0097] 本发明实施例中,对于浏览的全景照片,在确定全景照片时,全景照片的照片宽度d和旋转角度φ 2 全景照片拍摄时移动端的固定值(如果旋转角度φ 2 在拍摄全景照片的过程中记录,使用记录值; 如果旋转角 φ 2 拍摄时不记录,可以使用一些参考值,如180度或360度作为旋转角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,需要设置一个合适的旋转角度阈值φ 1 可以预设。 如果预设的旋转角度阈值 φ 1 固定,则确定全景照片在旋转过程中移动的最小位移。 在浏览全景照片的过程中,实时检测确定移动终端的旋转角度,如果确定移动终端的旋转角度达到预设的旋转角度阈值φ 1 ,全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0098] 在本发明实施例中,移动终端的旋转角度可以是移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,则可以认为上一次移动全景照片时,移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为一个不断执行和重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值 φ 1,可以将移动终端的初始旋转角度设置为0,检测确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值移动全景照片。 例如,将移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 -1度,全景照片不动; 当移动终端旋转到 φ 1 度,全景照片移动到最小位移,重置旋转角度,继续检测移动终端的旋转角度; 当移动终端旋转到 φ 1 度,全景照片再次移动最小位移,如此重复直到移动终端停止旋转。 [0099] 进一步地,在本发明实施例中,移动全景照片的过程可以是立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,就移动全景照片。 ; 例如,预设的旋转角度阈值 φ 1 为 5 度,一旦旋转角度达到 5 度,全景照片将移动最小位移。 移动全景照片的过程也可以是延迟执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后的一段时间内,将全景照片移动最小位移。 临界点。 [0100] 移动终端的旋转角度还可以是移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以是 随着用户移动移动终端而不断累积的值。 在这种情况下,可以在全景照片移动的位移和旋转角度之间设置成正比关系。 即,移动终端的旋转角度越大,表示全景照片移动的位移越大,移动终端的旋转角度越小,表示全景照片移动的位移越小。 [0101] 上述全景照片的移动方式和最小位移的确定方式还可以有其他实施例,本发明对其具体实施方式不作限定。 [0102] 小号 205 :以沉浸式浏览模式呈现全景照片。 [0103] 本发明实施例在以沉浸式浏览方式实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种呈现全景照片的方式可以使用现有的实施方案,例如在呈现全景照片时,在使全景照片适应显示屏尺寸的过程中可以使用现有的实施方式。 [0104]根据本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端旋转方向相反的方向移动最小位移并呈现。 使用本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,无需在移动终端的屏幕上手动滑动来浏览全景照片,方便快捷。 在操作上很方便。 [0105] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,本发明当然不限于此。 [0106] 本发明实施例提供的全景照片在移动终端呈现的控制方法的实现,是基于拍摄全景照片时保存的照片参数,例如,照片参数为拍摄的角度。 移动终端旋转和拍摄全景照片时移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的在移动终端中呈现全景照片的方法,该方法在全景照片拍摄时也可以与现有的全景照片拍摄不同。 本发明以下实施例结合实际案例,以举例的方式描述全景照片的拍摄过程和浏览过程。 [0107] 图9A示出了根据本发明实施例的全景照片拍摄过程的实现示意图。 如图9A所示,实施过程包括以下步骤。 [0108] 小号 301 :启用全景拍摄模式。 [0109] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0110] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0111] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0112] 在本发明实施例中,移动终端的旋转角度可以通过陀螺传感器在S开始的角度来确定。 302 旋转。 [0113] 小号 305 :保存拍摄的全景照片的属性信息。 [0114] 在本发明实施例中,保存的全景照片属性信息至少包括照片类型、拍摄角度和照片尺寸,其中照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0115] 可选的,在本发明实施例中,保存的全景照片的属性信息还可以包括移动终端在拍摄全景照片时的旋转方向,该旋转方向例如可以是从右到左, 当然,也可能是从左到右。 [0116] 图9B示出了根据本发明实施例的浏览全景照片的过程的实现示意图。 如图9B所示,实现过程包括以下步骤: [0117] 小号 401 :检测用户浏览的照片类型。 [0118] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行 S 403 ; 否则,以普通照片浏览模式浏览照片。 [0119] 小号 403 :当检测到用户触发用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0120] 小号 404 :用户通过旋转移动终端浏览全景照片。 [0121] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 确定的具体过程可以参见上述实施例的相关描述。 [0122] 小号 406 :根据S中确定的放置方向确定移动终端在相应轴向上的旋转角度 405 陀螺传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端沿Z方向旋转的角度 轴,当移动终端的放置方向为垂直放置方向时,确定移动终端沿X轴或Y轴方向旋转的角度。 [0123] 小号 407 :判断是否在S中确定的旋转角度 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0124] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移。 [0125] 小号 409 :检测移动端的放置方向和旋转角度; 当移动终端的放置方向发生变化时,执行S 405 ,当旋转角度发生变化时,执行 S 407 . [0126] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,及时调整全景照片的移动。 [0127] 本发明实施例提供的移动终端全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动滑动。 移动终端屏幕浏览全景照片。 [0128] 在上述实施例提供的移动终端中全景照片的呈现方法的基础上,本发明实施例还提供了一种装置 900 用于在移动终端中呈现全景照片。 如图 10A 所示,该装置 900 包括检测单元 901 , 确定单元 902 , 和一个呈现单元 903 . [0129] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给确定单元 902 其中,沉浸式浏览模式是全景照片随着移动终端旋转而移动的浏览模式。 [0130] 确定单元 902用于接收检测单元发送的检测结果 901 ; 如果检测结果为检测到触发指令,则检测确定移动终端的旋转角度,并将确定的移动终端旋转角度发送给呈现单元 903 . [0131] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度,移动并呈现移动终端中正常呈现的全景照片。 [0132] 在第一种实施方式中,确定单元 902 用于确定移动终端的旋转角度如下,确定移动终端在旋转过程中所处的放置方向,根据放置方向确定移动终端的旋转角度。 [0133] 在第二种实施方式中,确定单元 902 用于通过如下方式确定移动终端在旋转过程中所处的放置方向:检测移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角。 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端的屏幕所在的位置; 根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角,确定移动终端在旋转过程中所处的放置方向。 [0134] 在第三种实施方式中,确定单元 902 用于通过如下方式,根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定移动终端所在的放置方向 旋转过程中:当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端所处的放置方向 位于旋转过程中的是垂直放置方向; 当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,确定移动终端所在的放置方向为旋转 工艺是水平放置方向。 [0135] 在第四种实施方式中,确定单元 902 用于根据放置方向通过如下方式确定移动终端的旋转角度: 如果确定旋转过程中移动终端所处的放置方向为水平放置方向,则使用 以参考三维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向的旋转角度作为移动终端的旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为垂直放置方向,则使用参考三轴中的X轴方向或Y轴方向 将一维坐标系作为移动终端在旋转过程中对应的轴向,使用移动终端旋转的角度 h相对于轴向方向作为移动终端的旋转角度。 [0136] 在第五种实施方式中,所述装置还包括判断单元 904 ,如图10B所示,其中在呈现单元之前 903判断单元根据确定的旋转角度移动在移动终端中以普通模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0137] 在第六种实施方式中,所述确定单元 902 还用于呈现单元之前 903 根据确定的旋转角度移动在移动终端中以普通模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,移动终端在全景拍摄时的旋转角度 拍摄照片, 以及全景照片拍摄时沿移动终端旋转方向的照片宽度, 呈现单元 903 用于将在移动终端中以正常模式呈现的全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量的移动终端以如下方式移动。 [0138] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供提示信息,用于指示移动终端旋转。 [0139] 在第八种实施方式中,所述装置还包括:获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,发送给提示单元 905 、获取的拍摄照片时保存的移动终端的旋转方向,以及提示单元 905 用于通过以下方式提供用于指示移动终端旋转的提示信息: 根据获取单元获取的旋转方向,提供用于指示移动终端旋转的提示信息 906 . [0140] 需要说明的是,对于本发明实施例中图10A至图10D提供的移动终端中全景照片的呈现装置,如果不对移动终端中全景照片的呈现过程进行描述, 足够详细的可以参见方法实施例的相关描述,在此不再赘述。 [0141] 根据本发明实施例提供的移动终端全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动滑动。 移动终端屏幕浏览全景照片。 [0142] 基于上述实施例提供的移动终端中全景照片的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动终端 1000 包括输入设备 1001 , 一个传感器 1002 , 一个处理器 1003 , 和显示屏 1004 , 其中输入设备 1001 用于输入触发指令,用于指示移动终端进入沉浸式浏览模式,所述沉浸式浏览模式为全景照片随着移动终端旋转而移动的浏览模式,所述传感器 1002 所述处理器,用于检测所述移动终端的旋转角度, 1003 用于当检测到输入设备输入触发指令时1001 ,根据检测确定的旋转角度,移动在移动终端中以正常模式呈现的全景照片,以及显示屏幕 1004 配置为呈现全景照片。 [0143] 在本发明实施例中,输入设备可以是一个或多个 1001 ,例如输入设备 1001 可以是显示屏或按钮,可以与处理器集成 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可以连接到处理器 1003 使用有线连接(例如,电缆/端口)或无线连接(例如,蓝牙)。 [0144] 处理器 1003 可以在单个芯片、多个芯片或多个电子元件上实现,并且可以使用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0145] 可能有一个或多个传感器 1002 , 其中传感器 1002 可能有也可能没有操作处理功能。 例如,传感器 1002 在本发明实施例中,可以是重力传感器和陀螺仪传感器中的至少一种。 [0146] 在本发明实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0147] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0148] 在第二种实施方式中,传感器 1002 用于通过如下方式确定移动终端在旋转过程中所处的放置方向:检测移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角。 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端的屏幕所在的位置; 根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角,确定移动终端在旋转过程中所处的放置方向。 [0149] 在第三种实施方式中,传感器 1002 用于通过如下方式,根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定移动终端所在的放置方向 旋转过程中:当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端所处的放置方向 位于旋转过程中为垂直放置方向,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,判断为 移动终端在旋转过程中所处的放置方向为水平放置方向。 [0150] 在第四种实施方式中,传感器 1002用于根据放置方向通过如下方式确定移动终端的旋转角度: 如果确定旋转过程中移动终端所处的放置方向为水平放置方向,则使用 以参考三维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向的旋转角度作为移动终端的旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为垂直放置方向,则使用参考三轴中的X轴方向或Y轴方向 将一维坐标系作为移动终端在旋转过程中对应的轴向,使用移动终端旋转的角度 h相对于轴向方向作为移动终端的旋转角度。 [0151] 在第五种实施方式中,处理器 1003 还用于根据确定的旋转角度,在移动终端中以正常模式呈现的全景照片在移动之前,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0152] 在第六种实施方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,在移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值,确定全景照片的最小位移,所述全景照片的旋转角度。 拍摄全景照片时的移动终端,以及拍摄全景照片时沿移动终端旋转方向的全景照片的照片宽度,以及处理器 1003 用于以如下方式移动移动终端中正常模式呈现的全景照片:将全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0153] 在第七种实施方式中,处理器 1003 还用于当检测到所述触发指令由所述输入设备输入时 1001 ,提供提示信息,用于指示移动终端旋转。 [0154] 在第八种实施方式中,处理器 1003 还用于在提供用于指示移动终端旋转的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向, 处理器 1003 用于通过以下方式提供用于指示移动终端旋转的提示信息: 提供用于指示根据获取的旋转方向旋转移动终端的提示信息。 [0155] 需要说明的是,对于本发明实施例中图11提供的移动终端,其实现控制全景照片在移动终端中显示的过程如描述不充分,可参见相关 以上为方法实施例的描述,在此不再赘述。 [0156] 根据本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片会随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动滑动 移动终端屏幕浏览全景照片。 [0157]本领域技术人员应当理解,本发明实施例可以作为方法、系统或者计算机程序产品来提供。 因此,本发明可以采用纯硬件实施例、纯软件实施例或软件和硬件结合的实施例的形式。 此外,本公开可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0158] 参考根据本公开实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述本公开。 应当理解,计算机程序指令可以用于实现流程图和/或框图中的每个过程和/或每个块以及流程图和/或框图中的过程和/或块的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器以生成机器,以便由计算机或任何处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0159] 这些计算机程序指令还可以存储在计算机可读存储器中,该存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,以便存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能。 [0160] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0161] 尽管已经描述了本公开的一些优选实施例,但是本领域技术人员一旦了解了基本的发明概念,就可以对这些实施例进行改变和修改。 因此,以下权利要求旨在解释为覆盖优选实施例以及落入本公开范围内的所有变化和修改。 [0162] 显然,本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的范围。 本公开旨在覆盖这些修改和变化,只要它们落入由以下权利要求及其等效技术限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CA2966400A1(String), 1047222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CA2966400C(String), 1047223(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN104471519A(String), 1047224(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN104471519B(String), 1047225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN110650241A(String), 1047226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN110650241B(String), 1047227(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US10222877B2(String), 1047228(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US10649546B2(String), 1047229(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US11126275B2(String), 1047230(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20150363915A1(String), 1047231(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20170212609A1(String), 1047232(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20190171300A1(String), 1047233(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20200241657A1(String), 1047234(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US9621802B2(String), 1047235(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), WO2016004554A1(String), 1047236(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9621802B2(String), US9621802B2(String), 1491840000(Integer), 270668(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184987(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184987(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184987(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184987(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10649546B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10649546B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US16/266498(String), 1549209600(Integer), US10649546B2(String), 1589212800(Integer), 1589212800(Integer), 美国(String), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | JP2006129329A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184988(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c068aaff5aa7445aa374a70501349226.png(String), 184988(Integer), c068aaff5aa7445aa374a70501349226.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:47.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10649546B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US16/266498(String), 1549209600(Integer), US10649546B2(String), 1589212800(Integer), 1589212800(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | JP2006129329A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), \20230420\c068aaff5aa7445aa374a70501349226.png(String), 20(Integer), 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 1. A method for presenting a panoramic photo using a mobile terminal, the method comprising:photographing the panoramic photo while the mobile terminal is moving in a first direction;receiving an instruction for entering an immersive browsing mode; andperforming the following operations in the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 1.一种使用移动终端呈现全景照片的方法,该方法包括:移动终端在第一方向移动时拍摄全景照片;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下进行以下操作:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 2. The method of claim 1, wherein the first direction is either from left to right or from right to left.(String), 2.如权利要求1所述的方法,其中第一个方向是从左到右或从右到左。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 3. The method of claim 2, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 3.如权利要求2所述的方法,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 4. The method of claim 1, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 4.如权利要求1所述的方法,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 5. The method of claim 1, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 5.如权利要求1所述的方法,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 6. The method of claim 1, further comprising:displaying the panoramic photo in a normal mode that is different than the immersive browsing mode;displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 6.如权利要求1所述的方法,还包括:以不同于沉浸式浏览模式的正常模式显示全景照片;在正常模式下显示图标;检测图标上的输入;和响应于检测到图标上的输入而进入沉浸式浏览模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 7. The method of claim 1, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 7.如权利要求1所述的方法,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 8. The method of claim 1, wherein rotation of the mobile terminal in either the first direction or the second direction is detected by a gyro sensor of the mobile terminal.(String), 8.如权利要求1所述的方法,其中移动终端沿第一方向或第二方向的旋转由移动终端的陀螺仪传感器检测。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 9. A mobile terminal, comprising:one or more processors; anda memory coupled to the one or more processors and comprising instructions that, when executed by the one or more processors, cause the mobile terminal to:photograph a panoramic photo while the mobile terminal is moving in a first direction;receive an instruction for entering an immersive browsing mode; andperform the following operations in the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 9.移动终端,包括:一个或多个处理器;和存储器耦合到一个或多个处理器并包括指令,当由一个或多个处理器执行时,使移动终端:移动终端在第一方向移动时拍摄全景照片;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下进行以下操作:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 10. The mobile terminal of claim 9, wherein the first direction is either from left to right or from right to left.(String), 10.如权利要求9所述的移动终端,其中第一个方向是从左到右或从右到左。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 11. The mobile terminal of claim 10, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 11.如权利要求10所述的移动终端,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 12. The mobile terminal of claim 9, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 12.如权利要求9所述的移动终端,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 13. The mobile terminal of claim 9, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 13.如权利要求9所述的移动终端,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 14. The mobile terminal of claim 9, wherein the instructions further cause the mobile terminal to:display the panoramic photo in a normal mode that is different than the immersive browsing mode;display an icon in the normal mode;detect an input on the icon; andenter the immersive browsing mode in response to detecting the input on the icon.(String), 14.如权利要求9所述的移动终端,其中该指令进一步使移动终端:以不同于沉浸式浏览模式的正常模式显示全景照片;在正常模式下显示一个图标;检测图标上的输入;和响应于检测到图标上的输入进入沉浸式浏览模式。(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 15. The mobile terminal of claim 9, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 15.如权利要求9所述的移动终端,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 16. The mobile terminal of claim 9, further comprising a gyro sensor coupled to the one or more processors and configured to detect rotation of the mobile terminal in either the first direction or the second direction.(String), 16.如权利要求9所述的移动终端,还包括陀螺仪传感器耦合到一个或多个处理器并被配置为检测移动终端在第一方向或第二方向上的旋转。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 17. A non-transitory computer-readable storage medium comprising instructions that, when executed by a mobile terminal, cause the mobile terminal to:photograph a panoramic photo while the mobile terminal is moving in a first direction;receive an instruction for entering an immersive browsing mode; andperform the following operations in the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 17.一种非暂时性计算机可读存储介质包括指令,当由移动终端执行时,使移动终端:移动终端在第一方向移动时拍摄全景照片;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下进行以下操作:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 18. The non-transitory computer-readable storage medium of claim 17, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 18.如权利要求17所述的非暂时性计算机可读存储介质,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 19. The non-transitory computer-readable storage medium of claim 17, wherein the first direction is either from left to right or from right to left.(String), 19.如权利要求17所述的非暂时性计算机可读存储介质,其中第一个方向是从左到右或从右到左。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184988(Integer), 20. The non-transitory computer-readable storage medium of claim 19, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 20.如权利要求19所述的非暂时性计算机可读存储介质,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.183 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184988(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 15/483,724 filed on Apr. 10, 2017, the U.S. patent application Ser. No. 15/483,724 is a continuation of U.S. patent application Ser. No. 14/735,625 filed on Jun. 10, 2015, now U.S. Pat. No. 9,621,802, which is a continuation of International Patent Application No. PCT/CN2014/079950 filed on Jun. 16, 2014. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present disclosure. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present disclosure. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present disclosure. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present disclosure. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present disclosure. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present disclosure. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present disclosure. [0046]FIGS. 10A, 10B, 10C, and 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present disclosure, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present disclosure, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps. [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present disclosure, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present disclosure, there may be multiple implementation manners for implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present disclosure in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps. [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present disclosure, a user may input, using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present disclosure, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present disclosure, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present disclosure, in order to implement immersive mode browsing, the user needs to rotate the mobile (String), 相关申请的交叉引用 [0001] 该申请是美国专利申请序列号的延续。 2017 年 4 月 10 日提交的第 15/483,724 号美国专利申请序列号。 第 15/483,724 号是美国专利申请序列号的延续。 2015 年 6 月 10 日提交的第 14/735,625 号,现为美国专利。 美国专利第 9,621,802 号,是 2014 年 6 月 16 日提交的国际专利申请号 PCT/CN2014/079950 的继续申请。所有上述申请的全部内容通过引用并入本文。 技术领域 [0002] 本 发明涉及通信技术领域,尤其涉及一种移动终端中全景照片的呈现方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,移动终端的使用范围和环境也越来越多样化。 例如,目前很多移动终端,如手机、个人数字助理、个人电脑等都具有全景拍摄的功能。 [0004] 当移动终端进行全景拍摄时,用户旋转移动终端拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 然后可以将多张拍摄的照片按照上述的拼接原理拼接成一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,会在全景照片上浏览到比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端中呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作较为复杂。 概括 [0006] 本发明实施例提供一种全景照片在移动终端中的呈现方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 第一方面,提供了一种全景照片在移动终端中的呈现方法,包括:检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为浏览模式。 其中全景照片随着移动终端的旋转而移动,若检测到触发指令,则检测并确定移动终端的旋转角度,根据确定的旋转角度移动呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实现方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009]结合第一方面的第一种实现方式,在第二种实现方式中,所述确定移动终端在旋转过程中所处的放置方向包括检测移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考的Z轴 三维坐标系垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于参考三维X-Y平面方向的夹角确定- 维度坐标系,移动终端在旋转过程中所处的放置方向。 [0010] 结合第一方面的第二种实现方式,在第三种实现方式中,所述根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为竖直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0011] 结合第一方面的第二种实现方式或第一方面的第三种实现方式,在第四种实现方式中,所述根据放置方向确定移动终端的旋转角度包括: 其中,旋转过程中移动终端所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为旋转过程中移动终端对应的轴向。 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者判断旋转过程中移动终端所处的放置方向为竖直放置方向 ,将参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 分别以轴向为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实现方式,在第五种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013]结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括确定: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动终端中以正常模式呈现的全景照片移动包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实现方式中,所述检测确定移动终端的旋转角度之前,还包括提供用于指示旋转移动终端的提示信息。 [0015] 结合第一方面的第七种实现方式,在第八种实现方式中,所述提供用于指示旋转移动终端的提示信息之前,所述方法还包括: 获取旋转时保存的移动终端的旋转方向。 拍摄全景照片,提供用于指示旋转移动终端的提示信息包括:根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0016] 第二方面,提供了一种全景照片在移动终端中的呈现装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,所述触发指令用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元,所述沉浸式浏览模式为全景照片随着移动终端移动的浏览模式。 旋转,所述判断单元,用于接收检测单元发送的检测结果,若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送给呈现单元,呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0017] 结合第二方面,在第一种实现方式中,所述确定单元用于通过以下方式确定所述移动终端的旋转角度,确定所述移动终端在旋转过程中所处的放置方向,并确定 移动终端根据放置方向的旋转角度。 [0018] 结合第二方面的第一种实现方式,在第二种实现方式中,所述确定单元具体用于通过如下方式确定移动终端在旋转过程中检测角度的放置方向。 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 定位,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端在rota中的放置方向 化过程。 [0019]结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元,用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,通过如下方式确定: 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向相对于参考三维的X-Y平面方向的夹角 -维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于该方向的夹角 参考三​​维坐标系的X-Y平面的夹角大于45度,确定th e 旋转过程中移动终端所处的放置方向为水平放置方向。 [0020] 结合第二方面的第二种实现方式或第二方面的第三种实现方式,在第四种实现方式中,所述确定单元,用于通过以下方式,根据所述移动终端的旋转角度确定所述移动终端的旋转角度。 放置方向若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 rotation process为垂直放置方向,参考中使用X轴方向或Y轴方向 以三维坐标系作为移动终端在旋转过程中对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实现方式,在第五种实现方式中,所述装置还包括判断单元,所述判断单元根据所述确定的旋转角度,在所述呈现单元移动前,确定所述全景图 在移动终端中以正常模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元还用于在所述呈现单元根据确定的旋转角度移动之前,以正常模式呈现的全景照片处于 移动终端,根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 呈现单元,用于将移动终端中正常模式呈现的全景照片按如下方式移动,使全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0023] 结合第二方面,在第七种实现方式中,所述装置还包括提示单元,所述提示单元用于接收所述检测单元发送的检测结果; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示旋转移动终端的提示信息。 [0024]结合第二方面的第七种实现方式,在第八种实现方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄所述全景照片时保存的所述移动终端的旋转方向 , 向提示单元发送获取的拍摄照片时保存的移动终端的旋转方向, 提示单元用于通过以下方式提供用于指示旋转的提示信息 移动终端根据获取单元获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0025] 第三方面,提供了一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于在检测到输入设备输入触发指令时,根据检测确定的旋转角度移动移动终端中以正常模式呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实现方式,在第二种实现方式中,所述传感器用于在检测重力角度的旋转过程中,通过如下方式确定所述移动终端所处的放置方向 移动终端的方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 ,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端的重力方向与相对方向的夹角确定 参考三​​维坐标系的X-Y平面,旋转过程中移动终端所处的放置方向 秒。 [0028] 结合第三方面的第二种实现方式,在第三种实现方式中,所述传感器用于根据所述移动终端的重力方向相对于X-Y方向的夹角,通过如下方式进行判断 参考三​​维坐标系的平面,移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角时移动终端在旋转过程中所处的放置方向 坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面大于45度,确定放置 旋转过程中移动终端所处的方向为水平放置方向。 [0029]结合第三方面的第二种实现方式或第三方面的第三种实现方式,在第四种实现方式中,所述传感器,用于通过如下方式确定所述移动终端根据放置的旋转角度 方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向作为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 旋转过程为垂直放置方向,参考三中X轴方向或Y轴方向 移动终端在旋转过程中对应的轴向为维坐标系,移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,移动所述移动设备中以正常模式呈现的全景照片。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于,在移动终端中以正常模式呈现的全景照片根据确定的旋转角度移动之前,确定 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 拍摄后,处理器用于移动终端中正常模式下呈现的全景照片,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0032] 结合第三方面,在第七种实现方式中,处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示所述移动终端旋转的提示信息之前,获取所述移动终端的旋转方向,即 拍摄全景照片时保存, 处理器用于按照以下方式提供用于指示旋转移动终端的提示信息, 提供用于指示旋转移动终端的提示信息 获取的旋转方向。 [0034] 本发明实施例提供的一种移动终端全景照片呈现方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测到,检测并确定移动终端的旋转角度; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . 附图说明 [0035]为更加清楚地描述本发明实施例的技术方案,下面对实施例描述所需的附图进行简单介绍。 [0036] 图1为本发明实施例提供的全景照片在移动终端中的呈现方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一种实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端的旋转角度的过程的示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所处放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实现示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实现示意图。 [0043] 图8是根据本发明实施例的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例的全景照片浏览过程的实现示意图。 [0046] 图10A、10B、10C和10D是根据本发明实施例的移动终端中全景照片呈现装置的结构示意图。 [0047] 图11为本发明实施例提供的移动终端的结构示意图。 具体实施方式 [0048] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 本发明实施例提供的移动终端中全景照片的呈现方法,全景照片随着移动终端的旋转而移动。 本发明实施例中为了描述方便,将全景照片随着移动终端旋转而移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为“沉浸式浏览模式”。 以下简称正常模式,当然不限于此; 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览以普通模式显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤。 [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 本发明实施例中,若检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :移动呈现,根据S中确定的旋转角度 102 ,移动终端正常显示的全景照片。 [0055] 本发明实施例提供的移动终端中全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . [0056] 在本发明实施例中,实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在用户触发移动终端进入沉浸式浏览模式后立即以预定方式旋转移动终端,该预定方式可以例如通过用户手册预先学习得到。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示旋转移动终端的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供用于指示旋转移动终端的提示信息的实现方式为例,对全景照片在移动终端中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的全景照片在移动终端中的呈现方法的另一种实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤。 [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 在本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,本发明实施例可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 启用控件的启用状态用于确定是否启用沉浸式浏览模式,当检测到启用控件被启用时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面设置沉浸式浏览按钮。 When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选地,本发明实施例还可以在检测到用户正在浏览全景照片时,提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片随着移动终端的旋转而移动。 通常,为了更好的浏览全景照片,可以提供用于指示旋转移动终端的提示信息,以告知用户移动终端需要按照预设方向进行旋转,该预设方向可以为 例如,从左向右旋转,当然,也可以从右向左旋转。 [0064] 在本发明实施例中,提供的提示信息可以是在显示界面上显示的文字信息,当然,也可以是通过语音输出的方式通知的语音信息,本发明实施例对此不做限定。 [0065] 可选的,本发明实施例还可以获取拍摄全景照片时保存的移动终端的旋转方向,并以提示信息的形式通知获取的旋转方向。 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,提示用户根据获取的拍摄全景照片时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,从而及时控制全景照片移动。 [0068] 用户在拍摄全景照片时,一般会将移动终端定位在确定的放置方向上。 但是,用户在浏览全景照片时,很可能会使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了更加准确地浏览全景照片,在旋转过程中,可以根据移动终端所处的放置方向来确定移动终端的旋转角度。 [0069] S中移动终端旋转角度的确定过程 203 本发明实施例可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 本发明实施例中,可以利用设置在移动终端中的重力传感器指示的移动终端的重力方向,确定移动终端所在的放置方向,确定移动终端的旋转角度。 使用设置在移动终端中的陀螺仪传感器的角度。 可选地,在本发明实施例中,用于确定移动终端的放置方向的重力传感器和用于确定移动终端的旋转角度的陀螺仪传感器可以在用于指示移动终端的触发指令时被启用。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选地,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤。 [0074] 小号 2031 a :以移动终端屏幕所在平面为基准,建立参考三维坐标系。 [0075]本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面平行于该平面 移动终端屏幕所在平面,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也根据移动终端的不同放置方向进行旋转。 例如,参考三维坐标系的示意图分别对应图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的夹角 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过在S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选地,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于基准三的X-Y平面方向的夹角- 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为竖直放置方向。 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所处的放置方向 旋转过程中为水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为竖直放置方向,或者为水平放置方向,本发明实施例可以设置为竖直放置方向。 [0081] 本发明实施例中,如果利用移动终端的重力方向相对于基准三的X-Y平面方向的夹角来确定移动终端在旋转过程中所处的放置方向—— S 中的维度坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 . [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 本发明实施例在确定移动终端在旋转过程中所处的放置方向为水平放置方向时,采用参考三维坐标系中Z轴的方向 作为移动终端在旋转过程中对应的轴向; 或者,当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 用作移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,本发明实施例中,上述移动终端在旋转过程中对应的轴向只是为了简化确定移动终端旋转角度的过程,具体的确定方式不作限定。 至此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺仪传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于对应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度移动移动终端正常显示的全景照片。 [0088] 在本发明实施例中,在浏览全景照片时,一般先以普通浏览方式显示全景照片; 例如,可以是分辨率较低的全景照片,或者只有全景照片的最左部分或全景照片的最右部分等部分全景照片显示在手机的显示屏中 终端。 本发明实施例在确定移动终端的旋转角度后,可以移动终端中正常模式显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实施方式对移动终端中正常模式显示的全景照片进行移动。 例如,移动终端在正常模式下显示的全景照片可以沿与移动终端的旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,本发明实施例中,为了实现全景照片的平滑移动,可以预先设置旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现了全景照片的平滑移动。 如果没有达到预设的旋转角度阈值,全景照片可能不会被移动。 [0091] 本发明实施例中,根据确定的移动终端的旋转角度,将移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向在S中移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端的旋转方向相同的方向移动时,也可以采用类似的方式)。 [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,则执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常模式显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,本发明实施例中,为了进一步增强平滑移动的效果,还可以确定最小位移,当控制全景图像沿与移动终端的旋转方向相反的方向移动时, 照片每次移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,可以根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度以及全景照片沿a的照片宽度,确定全景照片的最小位移量。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录并保存,可以是 直接从本发明实施例拍摄全景照片时保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选地,在本发明实施例中,确定全景照片的最小位移可以采用如下方式。 全景照片的最小位移根据公式确定 [0097] s = d ⁢ ⁢ φ 1 φ 2 , 其中s是全景照片的最小位移; d为全景照片的照片宽度; φ 1 为预设旋转角度阈值; φ2为拍摄全景照片时移动终端的旋转角度。 [0098] 本发明实施例中,对于浏览的全景照片,在确定全景照片时,全景照片的照片宽度d和拍摄全景照片时移动终端的旋转角度φ2为固定值(如果 在拍摄全景照片的过程中记录了旋转角度φ2,使用记录的值;如果在拍摄过程中没有记录旋转角度φ2,则可以参考一些参考值,例如180度或360度作为旋转角度。 角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,适当的旋转角度阈值φ 1 可能是预设的。 若预设旋转角度阈值φ 1 固定后,确定全景照片在旋转过程中移动的最小位移量。 在浏览全景照片的过程中,实时检测并判断移动终端的旋转角度,如果判断移动终端的旋转角度达到预设的旋转角度阈值φ 1 ,全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0099] 本发明实施例中,移动终端的旋转角度可以为移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,可以认为上一次移动全景照片时移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为一个持续执行并重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值φ 1,可以将移动终端的初始旋转角度设置为0,检测并确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值来移动全景照片。 例如,移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 −1度,全景照片不动; 当移动端旋转到φ 1 度,全景照片移动最小位移,重新设置旋转角度,继续检测移动端的旋转角度; 当移动端旋转到φ 1 度,全景照片再次移动最小位移,如此循环直到移动终端停止转动。 [0100] 进一步地,在本发明实施例中,移动全景照片的过程可以是立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,则移动全景照片。 ; 例如,预设的旋转角度阈值φ 1 为5度,当旋转角度达到5度时,全景照片移动到最小位移。 移动全景照片的过程也可以是延时执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后,在一段时间内将全景照片移动最小位移量 临界点。 [0101] 移动终端的旋转角度还可以为移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以为a 随着用户移动移动终端不断积累价值。 此时,可以设置全景照片移动的位移与旋转角度成正比关系。 即,移动终端旋转角度越大,全景照片移动的位移越大,移动终端旋转角度越小,全景照片移动的位移越小。 [0102] 上述移动全景照片的方式和最小位移的确定方式还可以有其他实施方式,本发明不对其具体实施方式进行限定。 [0103] 小号 205 :以沉浸式浏览方式呈现全景照片。 [0104] 本发明实施例在沉浸式浏览模式下实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种全景照片的呈现方式可以采用现有的实施方案,例如,在呈现全景照片时,在将全景照片适配显示屏尺寸的过程中可以采用现有的实施方式。 [0105]本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移并呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,而不需要手动在移动终端的屏幕上滑动来浏览全景照片,简单易行。 在操作方面方便。 [0106] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,当然不限于此。 [0107] 本发明实施例提供的控制全景照片在移动终端中呈现的方法的实现基于拍摄全景照片时保存的照片参数,该照片参数例如为: 拍摄全景照片时移动终端旋转,移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的移动终端中全景照片的呈现方法,在拍摄全景照片时,该方法也可以区别于现有的全景照片拍摄。 本发明以下实施例结合实际案例,举例说明全景照片的拍摄过程和浏览过程。 [0108] 图9A示出了根据本发明实施例的全景照片拍摄过程的实现示意图。 如图9A所示,实施过程包括以下步骤。 [0109] 小号 301 :启用全景拍摄模式。 [0110] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0111] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0112] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0113] 本发明实施例中,可以通过陀螺仪传感器在S中启动的角度来确定移动终端的旋转角度。 302 旋转。 [0114] 小号 305 :保存拍摄的全景照片的属性信息。 [0115] 本发明实施例中,保存的全景照片的属性信息至少包括照片类型、拍摄角度和照片尺寸,其中,照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0116] 可选地,本发明实施例中,保存的全景照片的属性信息还可以包括拍摄全景照片时移动终端的旋转方向,该旋转方向例如可以为从右向左, 当然,也可能是从左到右。 [0117] 图9B示出了根据本发明实施例的全景照片浏览过程的实现示意图。 如图9B所示,实施过程包括以下步骤。 [0118] 小号 401 :检测用户浏览的照片类型。 [0119] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行S 403 ; 否则,以正常的照片浏览方式浏览照片。 [0120] 小号 403 :当检测到用户触发了用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0121] 小号 404 :用户通过旋转移动端浏览全景照片。 [0122] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 具体的确定过程可以参见前述实施例的相关描述。 [0123] 小号 406 :根据S中确定的放置方向,确定移动终端在相应轴向的旋转角度 405 以及陀螺仪传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端在Z方向上旋转的角度 -轴,当移动终端的放置方向为竖直放置方向时,确定移动终端在X轴或Y轴方向上旋转的角度。 [0124] 小号 407 :判断旋转角度是否在S中确定 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0125] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移量。 [0126] 小号 409 :检测移动终端的放置方向和旋转角度; 当移动端的放置方向改变时,执行S 405 ,当旋转角度发生变化时,执行S 407 . [0127] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,从而及时调整全景照片的移动。 [0128] 本发明实施例提供的移动终端中全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0129] 基于上述实施例提供的移动终端中全景照片的呈现方法,本发明实施例还提供了一种装置 900 用于在移动终端呈现全景照片。 如图 10A 所示,该装置 900 包括一个检测单元 901 , 决定单位 902 , 和一个呈现单元 903 . [0130] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元 902 ,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动的浏览模式。 [0131] 决定单位 902用于接收检测单元发送的检测结果 901 ; 若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的移动终端的旋转角度发送给呈现单元 903 . [0132] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0133] 在第一种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端的旋转角度,确定移动终端在旋转过程中所处的放置方向,根据放置方向确定移动终端的旋转角度。 [0134] 在第二种实施方式中,所述确定单元 902 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0135] 在第三种实施方式中,确定单元 902 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 位于旋转过程中的是垂直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 工艺是水平放置方向。 [0136] 在第四种实施方式中,所述确定单元 902 用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0137] 在第五种实施方式中,所述装置还包括判断单元 904 , 如图 10B 所示, 在呈现单元之前 903判断单元根据确定的旋转角度移动移动终端中正常模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0138] 在第六种实施方式中,所述确定单元 902 还配置在呈现单元之前 903 移动,根据确定的旋转角度移动终端中正常模式下呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,全景时移动终端的旋转角度 拍摄全景照片时,全景照片沿移动终端旋转方向的照片宽度,以及呈现单元 903 用于将移动终端中正常模式下呈现的全景照片按照如下方式移动,将全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量。 [0139] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供用于指示旋转移动终端的提示信息。 [0140] 在第八种实施方式中,所述装置还包括获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,并发送给提示单元 905 ,获取拍照时保存的移动终端的旋转方向,以及提示单元 905 用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取单元获取的旋转方向提供用于指示旋转移动终端的提示信息 906 . [0141] 需要说明的是,对于本发明实施例图10A至图10D提供的全景照片在移动终端中的呈现装置,如果不描述在移动终端中实现全景照片的呈现过程 不够详细,可以参见方法实施例的相关描述,在此不再赘述。 [0142] 本发明实施例提供的移动终端中全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0143] 基于上述实施例提供的全景照片在移动终端中的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动端 1000 包括一个输入设备 1001 , 一个传感器 1002 , 处理器 1003 , 和一个显示屏 1004 ,其中输入设备 1001 用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,所述传感器 1002 用于检测移动终端的旋转角度,处理器 1003 用于当检测到输入设备输入触发指令时1001 ,根据检测确定的旋转角度移动移动终端中正常模式呈现的全景照片,显示屏幕 1004 用于呈现全景照片。 [0144] 本发明实施例中,输入设备可以是一个或多个 1001 ,例如,输入设备 1001 可能是显示屏或按钮,可能与处理器集成在一起 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可能连接到处理器 1003 使用有线连接(例如电缆/端口)或无线连接(例如蓝牙)。 [0145] 处理器 1003 可以在单芯片、多芯片或多个电子元件上实现,可以采用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0146] 可能有一个或多个传感器 1002 ,其中传感器 1002 可能有也可能没有运算处理功能。 例如,传感器 1002 在本发明实施例中,可以为重力传感器和陀螺仪传感器中的至少一种。 [0147] 在本公开的该实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0148] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0149] 第二种实现方式,传感器 1002 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0150] 第三种实现方式,传感器 1002 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 旋转过程中位于垂直放置方向,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定 旋转过程中移动终端所处的放置方向为水平放置方向。 [0151] 在第四种实现方式中,传感器 1002用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0152] 在第五种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,将在移动终端中以正常模式呈现的全景照片确定移动终端的旋转角度达到预设的旋转角度阈值。 [0153] 在第六种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移, 拍摄全景照片时的移动终端,以及拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度,以及处理器 1003 用于移动终端中正常模式下呈现的全景照片的移动方式: 将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0154] 在第七种实现方式中,处理器 1003 还用于当检测到输入设备输入触发指令时 1001 ,提供用于指示旋转移动终端的提示信息。 [0155] 在第八种实现方式中,处理器 1003 还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,处理器 1003 用于提供指示旋转移动终端的提示信息的方式如下: 根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0156] 需要说明的是,对于本发明实施例图11提供的移动终端,在移动终端中实现控制全景照片显示的过程如描述不够详细,可以参考相关文献 方法实施例的描述,此处不再赘述。 [0157] 本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0158]本领域的技术人员应该理解,本公开的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本公开可以采用纯硬件实施例、纯软件实施例或结合软件和硬件的实施例的形式。 此外,本公开可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0159] 参考根据本公开的实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述本公开。 应当理解,可以使用计算机程序指令来实现流程图和/或框图中的每个过程和/或每个框以及流程图和/或框图中的过程和/或框的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器生成机器,使得任何计算机或处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0160] 这些计算机程序指令也可以存储在计算机可读存储器中,该计算机可读存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,使得存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程中和/或在框图中的一个或多个块中实现特定功能。 [0161] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程数据处理设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供了用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0162] 尽管已经描述了本公开的一些优选实施例,但是本领域的技术人员在了解基本发明构思后可以对这些实施例进行更改和修改。 因此,所附权利要求旨在被解释为涵盖优选实施例以及落入本公开范围内的所有变化和修改。 [0163] 显然,本领域的技术人员可以对本发明实施例进行各种更改和变型而不脱离本发明实施例的范围。 本公开旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.220 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.220 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.220 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CA2966400A1(String), 1047222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CA2966400C(String), 1047223(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN104471519A(String), 1047224(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN104471519B(String), 1047225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN110650241A(String), 1047226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN110650241B(String), 1047227(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US10222877B2(String), 1047228(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US10649546B2(String), 1047229(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US11126275B2(String), 1047230(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20150363915A1(String), 1047231(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20170212609A1(String), 1047232(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20190171300A1(String), 1047233(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20200241657A1(String), 1047234(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US9621802B2(String), 1047235(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), WO2016004554A1(String), 1047236(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9621802B2(String), US9621802B2(String), 1491840000(Integer), 270668(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184988(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184988(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184988(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184988(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.290 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10182389B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for restricting usage region of mobile terminal, and mobile terminal(String), 移动终端使用区域限制方法、装置及移动终端(String), US10182389B2(String), A method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal are provided. Cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information, otherwise, the mobile terminal skips accessing a wireless communications network. Hence, the cell identification information of the cell network at the current location is compared with the locked identification information to control cell network access of the mobile terminal.(String), 提供了一种限制移动终端使用区域的方法、装置和移动终端。 可以获得覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络,否则,移动终端跳过接入无线通信网络。 因此,将当前位置的小区网络的小区标识信息与锁定的标识信息进行比较,以控制移动终端的小区网络接入。(String), US15/551131(String), 1423929600(Integer), US10182389B2(String), 1547481600(Integer), 1547481600(Integer), 美国(String), 4(Integer), 5(Integer), 11(Integer), CN101137173A | CN101137214A | CN102984778A | GB2369004A | JP1992373330A | JP1995107550A | JP2012526407A | US20070275717A1 | US20140045505A1 | US20150057003A1 | US5966668A(String), 13(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184989(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ee9712cd61ae4f58a0aa6c9dcb5446ef.png(String), 184989(Integer), ee9712cd61ae4f58a0aa6c9dcb5446ef.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for restricting usage region of mobile terminal, and mobile terminal(String), 移动终端使用区域限制方法、装置及移动终端(String), US10182389B2(String), A method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal are provided. Cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information, otherwise, the mobile terminal skips accessing a wireless communications network. Hence, the cell identification information of the cell network at the current location is compared with the locked identification information to control cell network access of the mobile terminal.(String), 提供了一种限制移动终端使用区域的方法、装置和移动终端。 可以获得覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络,否则,移动终端跳过接入无线通信网络。 因此,将当前位置的小区网络的小区标识信息与锁定的标识信息进行比较,以控制移动终端的小区网络接入。(String), US15/551131(String), 1423929600(Integer), US10182389B2(String), 1547481600(Integer), 1547481600(Integer), 美国(String), 3(Integer), 4(Integer), 5(Integer), 11(Integer), CN101137173A | CN101137214A | CN102984778A | GB2369004A | JP1992373330A | JP1995107550A | JP2012526407A | US20070275717A1 | US20140045505A1 | US20150057003A1 | US5966668A(String), \20230420\ee9712cd61ae4f58a0aa6c9dcb5446ef.png(String), 13(Integer), 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 1. A method for restricting a usage region of a mobile terminal, applied to a mobile terminal, comprising:obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, the at least one cell network corresponding to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information comprising at least one of frequency channel number information, and the frequency channel number information and auxiliary cell identification information;determining a cell network having maximum signal strength in the at least one cell network covering the current location of the mobile terminal;sending cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile terminal;determining, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, the region lock instruction comprising the cell identification information corresponding to the cell network having maximum signal strength;determining the cell identification information corresponding to the cell network having maximum signal strength as locked identification information;determining whether the cell identification information comprises cell identification information matching the locked identification information, a parameter of the locked identification information being in a one-to-one correspondence with a parameter of the cell identification information;accessing, by the mobile terminal, a cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information; andskipping access, by the mobile terminal, of a wireless communication network when the cell identification information does not comprise the cell identification information matching the locked identification information.(String), 1.根据权利要求9所述的非暂时性计算机可读存储介质,其中接入锁定的标识信息对应的小区网络包括当小区标识信息中包含与锁定的标识信息匹配的小区标识信息时,移动终端接入锁定的标识信息对应的小区网络,当小区的信号强度为与锁定的标识信息匹配的标识信息不小于预设强度阈值。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 2. The method according to claim 1, wherein when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information comprises the frequency channel number information and the locked identification information comprises a locked frequency channel number, and wherein when the network standard supported by the mobile terminal is not GSM, the cell identification information comprises the frequency channel number information and the auxiliary cell identification information, and the locked identification information comprises the locked frequency channel number and locked auxiliary identification information.(String), 12.根据权利要求9所述的非暂时性计算机可读存储介质,其中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息包括:移动终端进行频率扫描;和从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 3. The method according to claim 1, wherein accessing the cell network corresponding to the locked identification information comprises accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information, and when signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold.(String), 13.根据权利要求9所述的非暂时性计算机可读存储介质,其中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息包括:移动终端接收小区广播消息;和从小区广播消息中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 4. The method according to claim 1, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:performing, by the mobile terminal, frequency scanning; andobtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 5. The method according to claim 1, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:receiving, by the mobile terminal, a cell broadcast message; andobtaining, from the cell broadcast message, the cell identification information of the at least one cell network covering the current location of the mobile terminal.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 6. A mobile terminal, comprising:a processor;a memory;a communications interface; anda bus,wherein the processor, the memory, and the communications interface are coupled and communicate with each other using the bus,wherein the memory is configured to store an executable program code, andwherein when executed, the executable program code causes the processor to be configured to:obtain cell identification information of at least one cell network that covers a current location of the mobile terminal, the at least one cell network corresponding to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information comprising at least one of frequency channel number information and the frequency channel number information and auxiliary cell identification information;determine a cell network having maximum signal strength in the at least one cell network covering the current location of the mobile terminal;send the cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile terminal;determine, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, the region lock instruction comprising the cell identification information corresponding to the cell network having maximum signal strength;determine the cell identification information corresponding to the cell network having maximum signal strength as locked identification information;determine whether the cell identification information comprises cell identification information matching the locked identification information, a parameter of the locked identification information being in a one-to-one correspondence with a parameter of the cell identification information;access a cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information; andskipping access of a wireless communication network when the cell identification information does not comprise the cell identification information matching the locked identification information.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 7. The mobile terminal according to claim 6, wherein when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information comprises the frequency channel number information and the locked identification information comprises a locked frequency channel number, and wherein when the network standard supported by the mobile terminal is not the GSM, the cell identification information comprises the frequency channel number information and the auxiliary cell identification information, and the locked identification information comprises the locked frequency channel number and locked auxiliary identification information.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 8. The mobile terminal according to claim 6, wherein the executable program code further causes the processor to be configured to access the cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 9. A non-transitory computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to carry out a method comprising:obtaining cell identification information of at least one cell network that covers a current location of a mobile terminal, the at least one cell network corresponding to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information comprising frequency channel number information, or the frequency channel number information and auxiliary cell identification information;determining a cell network having maximum signal strength in the at least one cell network covering the current location of the mobile terminal;sending cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile terminal;determining, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, the region lock instruction comprising the cell identification information corresponding to the cell network having maximum signal strength;determining the cell identification information corresponding to the cell network having maximum signal strength as locked identification information;determining whether the cell identification information comprises cell identification information matching the locked identification information, a parameter of the locked identification information being in a one-to-one correspondence with a parameter of the cell identification information;accessing, by the mobile terminal, a cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information; andskip access, by the mobile terminal, of a wireless communication network when the cell identification information does not comprise the cell identification information matching the locked identification information.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 10. The non-transitory computer-readable storage medium according to claim 9, wherein when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information comprises the frequency channel number information and the locked identification information comprises a locked frequency channel number, and wherein when the network standard supported by the mobile terminal is not GSM, the cell identification information comprises the frequency channel number information and the auxiliary cell identification information, and the locked identification information comprises the locked frequency channel number and locked auxiliary identification information.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 11. The non-transitory computer-readable storage medium according to claim 9, wherein accessing the cell network corresponding to the locked identification information comprises accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information, and when signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 12. The non-transitory computer-readable storage medium according to claim 9, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:performing, by the mobile terminal, frequency scanning; andobtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184989(Integer), 13. The non-transitory computer-readable storage medium according to claim 9, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:receiving, by the mobile terminal, a cell broadcast message; andobtaining, from the cell broadcast message, the cell identification information of the at least one cell network covering the current location of the mobile terminal.(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184989(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a U.S. National Stage of International Patent Application No. PCT/CN2015/073113 filed on Feb. 15, 2015, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present disclosure relates to the field of mobile communications, and in particular, to a method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal. BACKGROUND [0003]For a particular purpose, usage ranges of some mobile terminals (for example, mobile phones, point of sale (POS) machines, and a portable wireless broadband apparatus (MIFI)) often need to be restricted. Within only a specified usage range, these mobile terminals can normally use a wireless communication service such as a voice communication service, a short message service, or a data communication service provided by a communications operator. For example, MIFI can be used only in a specified region. When MIFI is in the specified region, MIFI can work normally to provide a wireless network for another device. When MIFI is outside the specified region, MIFI cannot work normally and cannot provide a wireless network for another device. [0004]In other approaches, a usage range of a mobile terminal is restricted by locking a location area code. When a mobile terminal is in a region identified by a locked location area code, the mobile terminal can normally use a wireless communication service. Otherwise, the mobile terminal cannot normally use a wireless communication service. [0005]However, a region identified by a location area code is excessively large, and even a district or a county is in a region identified by a location area code. Therefore, in the other approaches, a usage range of a mobile terminal cannot be restricted precisely. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal to restrict a usage range of a mobile terminal more precisely. Solutions are as follows. [0007]According to a first aspect, a method for restricting a usage region of a mobile terminal is provided. The method is applied to a mobile terminal, and the method includes obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skipping accessing, by the mobile terminal, a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0008]With reference to the first aspect, in a first possible implementation manner, when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information is frequency channel number information and the locked identification information includes a locked frequency channel number, and when the network standard supported by the mobile terminal is not GSM, the cell identification information includes frequency channel number information and auxiliary cell identification information, and the locked identification information includes a locked frequency channel number and locked auxiliary identification information. [0009]With reference to the first aspect, in a second possible implementation manner, before determining whether the cell identification information includes cell identification information matching locked identification information, the method further includes determining a cell network having maximum signal strength in the at least one cell network that covers the current location of the mobile terminal, and sending cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile device, determining, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, where the region lock instruction includes the cell identification information corresponding to the cell network having maximum signal strength, and determining the cell identification information corresponding to the cell network having maximum signal strength as the locked identification information. [0010]With reference to the first aspect, in a third possible implementation manner, accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information includes accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the obtained cell identification information includes the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold. [0011]With reference to the first to the third possible implementation manners of the first aspect, in a fourth possible implementation manner, obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal includes performing, by the mobile terminal, frequency scanning, and obtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result, or receiving, by the mobile terminal, a cell broadcast message, and obtaining, from the broadcast message, the cell identification information of the at least one cell network that covers the current location of the mobile terminal. [0012]According to a second aspect, an apparatus for restricting a usage region of a mobile terminal is provided. The apparatus is applied to a mobile terminal, and the apparatus includes a cell identification information obtaining unit, a match determining unit, a network access unit, and a network discarding unit, where the cell identification information obtaining unit is configured to obtain cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information. The match determining unit is configured to determine whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information. The network access unit is configured to access a cell network corresponding to the locked identification information, when the cell identification information obtained by the cell identification information obtaining unit includes the cell identification information matching the locked identification information, and the network discarding unit is configured to skip accessing a wireless communication network when the cell identification information obtained by the cell identification information obtaining unit does not include the cell identification information matching the locked identification information. [0013]With reference to the second aspect, in a first possible implementation manner, when the network standard supported by the mobile terminal is GSM, the cell identification information is frequency channel number information and the locked identification information includes a locked frequency channel number, and when the network standard supported by the mobile terminal is not GSM, the cell identification information includes frequency channel number information and auxiliary cell identification information, and the locked identification information includes a locked frequency channel number and locked auxiliary identification information. [0014]With reference to the second aspect, in a second possible implementation manner, the apparatus further includes a strongest network determining unit, an identification information determining unit, and an identification information locking unit, where before determining, by the match determining unit, whether the cell identification information includes the cell identification information matching the locked identification information, the strongest network determining unit is configured to determine a cell network having maximum signal strength in the at least one cell network that covers the current location of the mobile terminal, and send cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile device. The identification information determining unit is configured to determine, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, where the region lock instruction includes the cell identification information corresponding to the cell network having maximum signal strength, and the identification information locking unit is configured to determine the cell identification information corresponding to the cell network having maximum signal strength as the locked identification information. [0015]With reference to the second aspect, in a third possible implementation manner, the network access unit is further configured to access, by the mobile terminal, the cell network corresponding to the locked identification information when the obtained cell identification information includes the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold. [0016]With reference to the first to the third possible implementation manners of the second aspect, in a fourth possible implementation manner, the cell identification information obtaining unit includes a frequency scanning subunit and/or a broadcast receiving subunit, where the frequency scanning subunit is configured to perform frequency scanning, and obtain the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result, and the broadcast receiving subunit is configured to receive a cell broadcast message, and obtain, from the broadcast message, the cell identification information of the at least one cell network that covers the current location of the mobile terminal. [0017]According to a third aspect, a storage medium is provided. The storage medium is configured to store an application program. When the application program runs, the method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is executed. The method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is applied to a mobile terminal, and the method may include obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skip accessing, by the mobile terminal, a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0018]According to a fourth aspect, an application program is provided. When the application program runs, the method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is executed. The method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is applied to a mobile terminal, and the method may include obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skip accessing, by the mobile terminal, a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0019]According to a fifth aspect, a mobile terminal is provided, including a processor, a memory, a communications interface, and a bus, where the processor, the memory, and the communications interface are connected and communicate with each other using the bus. The memory stores executable program code. The processor reads the executable program code stored in the memory to run a program corresponding to the executable program code to perform the following steps of obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skip accessing a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0020]As can be known from the foregoing technical solutions, according to the method and the apparatus for restricting a usage region of a mobile terminal, and the mobile terminal in the embodiments of the present disclosure, cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information. Otherwise, the mobile terminal skips accessing a wireless communications network. In the present disclosure, the cell identification information of the cell network at the current location is compared with the locked identification information, to control cell network access of the mobile terminal. In the present disclosure, because a region corresponding to a cell is smaller than that corresponding to a location area code, a usage range of the mobile terminal can be more precisely restricted. BRIEF DESCRIPTION OF DRAWINGS [0021]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required in the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0022]FIG. 1 is a flowchart of a method for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; [0023]FIG. 2 is a schematic diagram of coverage of a wireless communications network according to an embodiment of the present disclosure; [0024]FIG. 3 is a flowchart of another method for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; [0025]FIG. 4 is a schematic diagram of communication between a control device and a mobile terminal according to an embodiment of the present disclosure; [0026]FIG. 5 is a schematic structural diagram of an apparatus for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; [0027]FIG. 6 is a schematic structural diagram of another apparatus for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; and [0028]FIG. 7 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0029]To make the objectives, technical solutions, and advantages of the present disclosure clearer and more comprehensible, the following further describes the present disclosure in detail with reference to the accompanying drawings and embodiments. The described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0030]As shown in FIG. 1, an embodiment of the present disclosure provides a method for restricting a usage region of a mobile terminal. The method is applied to a mobile terminal, and the method may include the following steps. [0031]Step S100: Obtain cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information. [0032]The mobile terminal may be a mobile phone, a POS machine, an MIFI, or the like. [0033]A cell (also referred to as a cellular cell) is a minimum unit on a wireless communications network, and multiple cells may form a region corresponding to a location area code. A cell is smaller than a region corresponding to a location area code. [0034]The frequency channel number information is a number of a fixed frequency. To avoid interference caused by same frequency channel number information, frequency channel number information of cells in a region is different from each other. Frequency channel number information of cells is different from each other in a wide area of a communications apparatus that uses a standard of GSM. Therefore, frequency channel number information, obtained by the mobile terminal, of cells of the wireless communications network that covers the current location is different from each other. [0035]A frequency multiplexing technology is used in a network standard such as Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), or Long Term Evolution (LTE). Therefore, frequency channel number information, obtained by the mobile terminal, of the cell network that covers the current location may be the same. Therefore, to reduce misoperations, auxiliary cell identification information of a cell may also be obtained to identify the cell. In WCDMA, auxiliary cell identification information is a primary scrambling code. In TD-SCDMA, auxiliary cell identification information is a scrambling code. In LTE, auxiliary cell identification information is a physical layer cell number. Cells can be more precisely distinguished using frequency channel number information of the cells and auxiliary cell identification information of the cells, to reduce misoperations. The cell identification information may consist of the frequency channel number information and the auxiliary cell identification information. [0036]It may be understood that, different frequency bands are used in different network standards. For example, frequency channel numbers of a frequency band 900 megahertz (MHz) and a frequency band 1800 MHz are used in the GSM standard. When the mobile terminal supports only the GSM standard, frequency channel number information of the frequency band 900 MHz and the frequency band 1800 MHz may be obtained. [0037]Further, alternatively, only cell identification information of at least one cell network of a first communications operator that covers the current location of the mobile terminal may be obtained. The first communications operator is a communications operator that provides a subscriber identity module card/universal subscriber identity module card of the mobile terminal. [0038]For example, for the frequency band 900 MHz in the GSM standard, a downlink frequency band of CHINA MOBILE is 935-954 MHz, and a downlink frequency band of CHINA UNICOM is 954-960 MHz. When the subscriber identity module card/universal subscriber identity module card of the mobile terminal is provided by CHINA MOBILE, only frequency channel number information of 935-954 MHz may be obtained. [0039]A wireless communication signal of a cell network is provided by a base station, and one base station may provide a wireless communication signal for one or more cell networks. When multiple cell networks cover the current location of the mobile terminal, the mobile terminal may obtain wireless communication signals of the multiple cell networks provided by a base station. As shown in FIG. 2, it is assumed that a base station 201 provides a wireless communication signal for a cell network A, a base station 202 provides a wireless communication signal for a cell network B, and a base station 203 provides a wireless communication signal for a cell network C, and the wireless communication signals of the three cell networks A, B, and C cover a current location of the mobile terminal 200. In this case, the mobile terminal 200 may obtain cell identification information of the three cell networks A, B, and C at the current location. [0040]The mobile terminal 200 may obtain the cell identification information by performing frequency scanning or receiving a cell broadcast message. Further, step S100 may include performing, by the mobile terminal, frequency scanning, and obtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result, or receiving, by the mobile terminal, a cell broadcast message, and obtaining, from the broadcast message, the cell identification information of the at least one cell network that covers the current location of the mobile terminal. [0041]Step S200: Determine whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information. [0042]When the network standard supported by the mobile terminal is GSM, the cell identification information is frequency channel number information and the locked identification information includes a locked frequency channel number, and when the network standard supported by the mobile terminal is not GSM, the cell identification information includes frequency channel number information and auxiliary cell identification information, and the locked identification information includes a locked frequency channel number and locked auxiliary identification information. [0043]Step S300: The mobile terminal accesses a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information. [0044]Step S400: The mobile terminal skips accessing a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0045]Further, a network access function of the mobile terminal may be locked in a particular period to not access a wireless communications network in order to discard the network. For example, cell handover and cell reselection functions of the mobile terminal are locked. After a period during which the network access function of the mobile terminal is locked is beyond the particular period, go back to step S100. [0046]The locked identification information may be cell identification information of a cell covered in a restricted region. The restricted region is a usage region, such as a factory, to which the mobile terminal needs to be restricted. There may be one or at least two pieces of locked identification information. [0047]Optionally, when the obtained cell identification information includes only the cell identification information matching the locked identification information, the cell network corresponding to the locked identification information may be accessed. When the obtained cell identification information includes at least two pieces of cell identification information matching the locked identification information, a cell network corresponding to one piece of the locked identification information may be accessed. Preferably, a cell network that corresponds to the locked identification information and has maximum signal strength may be accessed. [0048]Optionally, step S300 may include accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the obtained cell identification information includes the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold. [0049]In some cases, although the mobile terminal can access the cell network corresponding to the locked identification information, the cell network has relatively poor signal strength and cannot provide a desirable communication service for a user. Therefore, to ensure that a desirable communication service is provided for a user, the cell network corresponding to the locked identification information may be accessed when signal strength is relatively high. [0050]According to the method for restricting a usage region of a mobile terminal provided in this embodiment of the present disclosure, cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information. Otherwise, the mobile terminal skips accessing a wireless communications network. In the present disclosure, the cell identification information of the cell network at the current location is compared with the locked identification information to control cell network access of the mobile terminal. In the present disclosure, because a region corresponding to a cell is smaller than that corresponding to a location area code, a usage range of the mobile terminal can be more precisely restricted. [0051]Based on the embodiment shown in FIG. 1, as shown in FIG. 3, an embodiment of the present disclosure provides another method for restricting a usage region of a mobile terminal. Before step S200, the method may further include the following steps. [0052]Step S101: Determine a cell network having maximum signal strength in the at least one cell network that covers the current location of the mobile terminal, and send cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile device. [0053]In another embodiment of the present disclosure, alternatively, cell identification information corresponding to another cell network that covers the current location of the mobile terminal may also be sent to a control device. When multiple pieces of cell identification information are sent to the control device, signal strength information may be simultaneously sent to the control device. [0054]Step S102: Determine, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, where the region lock instruction includes the cell identification information corresponding to the cell network having maximum signal strength. [0055]The region lock instruction may be delivered by the control device after a user performs a region locking operation on the control device, or may be automatically delivered by the control device. [0056]Step S103: Determine the cell identification information corresponding to the cell network having maximum signal strength as the locked identification information. [0057]It may be understood that, when the mobile terminal is located in the restricted region, steps S101 to S103 may be performed. The cell network having maximum signal strength is one of cell networks that provide wireless communication services for the mobile terminal at the current location of the restricted region. The cell network has maximum signal strength and therefore provides highest wireless communication service quality. When the cell identification information corresponding to the cell network having maximum signal strength is set as the locked identification information, the mobile terminal can access the cell network having better service quality. (String), 相关申请的交叉引用 [0001] 本申请为2015年2月15日提交的美国国家阶段国际专利申请PCT/CN2015/073113,其全部内容通过引用并入本文。 技术领域 [0002] 本 发明涉及移动通信领域,尤其涉及一种限制移动终端使用区域的方法、装置及移动终端。 背景 [0003] 为了特定的目的,一些移动终端(例如手机、POS机、MIFI)的使用范围往往需要进行限制。 只有在特定的使用范围内,这些移动终端才能正常使用通信运营商提供的语音通信服务、短信服务或数据通信服务等无线通信服务。 例如,MIFI 只能在指定区域使用。 当 MIFI 在指定区域时,MIFI 可以正常工作,为其他设备提供无线网络。 当MIFI在指定区域之外时,MIFI无法正常工作,无法为其他设备提供无线网络。 [0004] 在其他方式中,通过锁定位置区码来限制移动终端的使用范围。 当移动终端处于锁定位置区码标识的区域时,移动终端可以正常使用无线通信服务。 否则,移动终端将无法正常使用无线通信服务。 [0005] 但是,位置区码标识的区域太大,甚至区县都在位置区码标识的区域内。 因此,其他方式无法精确限制移动终端的使用范围。 概括 [0006] 本发明实施例提供一种限制移动终端使用区域的方法、装置及移动终端,以更加精确地限制移动终端的使用范围。 解决方法如下。 [0007] 第一方面,提供了一种限制移动终端使用区域的方法。 该方法应用于移动终端,该方法包括获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,该小区网络对应于无线通信网络所支持的网络制式。 移动终端,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断小区标识信息是否包括与锁定标识信息匹配的小区标识信息,参数为 锁定标识信息与小区标识信息的参数一一对应,当获取到小区标识信息时,移动终端接入锁定标识信息对应的小区网络 包括与锁定的标识信息匹配的小区标识信息,或者当获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,移动终端跳过接入无线通信网络。 [0008] 结合第一方面,在第一种可能的实现方式中,当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定的标识信息包括锁定的 频道号,当移动终端支持的网络制式不是GSM时,小区标识信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0009]结合第一方面,在第二种可能的实现方式中,在判断所述小区标识信息是否包括与锁定标识信息匹配的小区标识信息之前,所述方法还包括:确定所述至少一个小区网络中信号强度最大的小区网络。 覆盖移动终端的当前位置,向与移动设备连接的控制设备发送信号强度最大的小区网络对应的小区标识信息,根据控制设备下发的区域锁定指令确定小区标识 信号强度最大的小区网络对应的信息, 区域锁定指令包括信号强度最大的小区网络对应的小区标识信息, 确定si最大的小区网络对应的小区标识信息 gnal强度作为锁定的标识信息。 [0010] 结合第一方面,在第三种可能的实现方式中,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,移动终端接入锁定的标识信息对应的小区网络包括接入, 移动终端在获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息,且与锁定标识信息匹配的小区标识信息的信号强度不小于预设值时,获取锁定标识信息对应的小区网络 强度阈值。 [0011] 结合第一方面的第一种至第三种可能的实现方式,在第四种可能的实现方式中,获取覆盖所述移动终端当前位置的至少一个小区网络的小区标识信息,包括: 所述移动终端执行: 频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,或者移动终端接收小区广播消息,从广播中获取 消息,覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0012] 第二方面,提供了一种限制移动终端使用区域的装置。 该装置应用于移动终端,该装置包括小区标识信息获取单元、匹配判断单元、网络接入单元和网络丢弃单元,小区标识信息获取单元用于获取小区标识信息 覆盖移动终端当前位置的至少一个小区网络的标识,该小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者, 小区标识信息包括频道号信息和辅助小区标识信息。 匹配判断单元,用于判断小区标识信息中是否包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应。 网络接入单元,用于当小区标识信息获取单元获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,接入锁定标识信息对应的小区网络; 网络丢弃单元,用于 当小区标识信息获取单元获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0013]结合第二方面,在第一种可能的实现方式中,当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定标识信息包括锁定频道号,当 移动终端支持的网络制式不是GSM,小区标识信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0014] 结合第二方面,在第二种可能的实现方式中,所述装置还包括最强网络确定单元、标识信息确定单元和标识信息锁定单元,其中,所述匹配确定单元在确定所述小区是否为所述小区之前 标识信息包括与锁定的标识信息匹配的小区标识信息, 最强网络确定单元用于确定覆盖移动终端当前位置的至少一个小区网络中信号强度最大的小区网络,并发送小区标识 将与具有最大信号强度的小区网络对应的信息发送给连接到移动设备的控制设备。 标识信息确定单元,用于根据控制设备下发的区域锁定指令,确定信号强度最大的小区网络对应的小区标识信息,该区域锁定指令包括该小区对应的小区标识信息 所述信号强度最大的小区网络,所述标识信息锁定单元用于将所述信号强度最大的小区网络对应的小区标识信息确定为锁定的标识信息。 [0015] 结合第二方面,在第三种可能的实现方式中,所述网络接入单元,还用于当获取的小区标识信息中包括匹配的小区标识信息时,移动终端接入锁定的标识信息对应的小区网络。 锁定标识信息,与锁定标识信息匹配的小区标识信息的信号强度不小于预设强度门限。 [0016] 结合第二方面的第一种至第三种可能的实现方式,在第四种可能的实现方式中,所述小区标识信息获取单元包括频率扫描子单元和/或广播接收子单元,所述频率扫描子单元用于 进行频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,广播接收子单元用于接收小区广播消息,从中获取 广播消息、覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0017]第三方面,提供了一种存储介质。 存储介质用于存储应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0018] 第四方面,提供了一种应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0019]第五方面,提供了一种移动终端,包括处理器、存储器、通信接口和总线,处理器、存储器和通信接口通过总线连接并通信。 存储器存储可执行程序代码。 处理器读取存储在存储器中的可执行程序代码,以运行与可执行程序代码对应的程序,以执行以下步骤:获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,其中小区 网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断小区标识是否为 信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,接入锁定标识对应的小区网络 当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,则跳过无线通信网络的接入;或者当获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0020] 由上述技术方案可知,根据本发明实施例的移动终端使用区域限制方法、装置及移动终端,覆盖当前小区网络的小区标识信息 可以获得移动终端的位置。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 否则,移动终端跳过接入无线通信网络。 本发明通过将当前位置的小区网络的小区标识信息与锁定的标识信息进行比对,来控制移动终端的小区网络接入。 在本发明中,由于小区对应的区域小于位置区码对应的区域,因此可以更精确地限制移动终端的使用范围。 附图说明 [0021] 为更加清楚地描述本发明实施例中的技术方案,下面对实施例中所需要的附图进行简要说明。 下面描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0022] 图1为本发明实施例限制移动终端使用区域的方法流程图; [0023] 图2是根据本发明实施例的无线通信网络的覆盖示意图; [0024] 图3为本发明实施例提供的另一种限制移动终端使用区域的方法流程图; [0025] 图4为本发明实施例控制设备与移动终端通信的示意图; [0026] 图5为本发明实施例限制移动终端使用区域的装置的结构示意图; [0027] 图6为本发明实施例提供的另一种限制移动终端使用区域的装置的结构示意图; 和 [0028] 图7为本发明实施例提供的移动终端的结构示意图。 具体实施方式 [0029] 为使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本发明进行进一步详细说明。 所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0030] 如图1所示,本发明实施例提供了一种限制移动终端使用区域的方法。 该方法应用于移动终端,该方法可以包括以下步骤。 [0031] 脚步 100 :获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,该小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道 号信息,或者小区标识信息包括频道号信息和辅助小区标识信息。 [0032] 移动终端可以是手机、POS机、MIFI等。 [0033] 小区(cell,也称为蜂窝小区)是无线通信网络上的最小单位,多个小区可以组成一个位置区码对应的区域。 小区小于位置区域码对应的区域。 [0034] 频道号信息为固定频率的编号。 为了避免相同频道号信息造成的干扰,一个区域内的小区的频道号信息是不同的。 在使用GSM标准的通信设备的广泛区域中,小区的频道号信息彼此不同。 因此,移动终端获取到的覆盖当前位置的无线通信网络的小区的频道号信息是不同的。 [0035] 频率复用技术用于诸如宽带码分多址(WCDMA)、时分同步码分多址(TD-SCDMA)或长期演进(LTE)的网络标准中。 因此,移动终端获取的覆盖当前位置的小区网络的频道号信息可能是相同的。 因此,为了减少误操作,还可以获取小区的辅助小区标识信息来识别小区。 在WCDMA中,辅助小区标识信息是主要的扰码。 在TD-SCDMA中,辅助小区标识信息是扰码。 在LTE中,辅助小区标识信息是物理层小区号。 利用小区的频道号信息和小区的辅助小区标识信息,可以更准确的区分小区,减少误操作。 小区标识信息可以由频道号信息和辅助小区标识信息组成。 [0036] 可以理解的是,不同的网络标准使用不同的频段。 例如,GSM标准中使用900兆赫兹(MHz)频段和1800MHz频段的频道号。 当移动终端仅支持GSM制式时,可以获取900MHz频段和1800MHz频段的频道号信息。 [0037] 进一步地,可选地,可以仅获取覆盖移动终端当前位置的第一通信运营商的至少一个小区网络的小区标识信息。 第一通信运营商为提供移动终端的用户识别卡/通用用户识别卡的通信运营商。 [0038]例如,对于GSM标准中的900MHz频段,中国移动的下行频段为935-954MHz,中国联通的下行频段为954-960MHz。 当移动终端的用户识别卡/通用用户识别卡为中国移动提供时,只能获取935-954MHz的频道号信息。 [0039] 小区网络的无线通信信号由基站提供,一个基站可以为一个或多个小区网络提供无线通信信号。 当多个小区网络覆盖移动终端的当前位置时,移动终端可以获得基站提供的多个小区网络的无线通信信号。 如图2所示,假设基站 201 为小区网络A提供无线通信信号,基站 202 为小区网络B提供无线通信信号,基站 203 为小区网络C提供无线通信信号,三个小区网络A、B、C的无线通信信号覆盖移动终端的当前位置 200 . 在这种情况下,移动端 200 可以获得当前位置的三个小区网络A、B、C的小区标识信息。 [0040] 移动端 200 可以通过频率扫描或者接收小区广播消息来获取小区标识信息。 进一步地,步骤S 100 可以包括移动终端进行频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,或者移动终端接收小区 广播消息,从广播消息中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0041] 脚步 200 :判断小区标识信息是否包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应。 [0042] 当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定标识信息包括锁定频道号,当移动终端支持的网络制式为非GSM时,小区标识信息为锁定频道号。 信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0043] 脚步 300 :当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 [0044] 脚步 400 :移动终端在获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0045] 进一步地,移动终端的网络接入功能可以在特定时间段内被锁定以不接入无线通信网络以丢弃网络。 例如,移动终端的小区切换和小区重选功能被锁定。 移动终端的网络接入功能被锁定的时间超过特定时间后,返回步骤S 100 . [0046] 锁定的标识信息可以是受限区域覆盖的小区的小区标识信息。 受限区域为移动终端需要限制的使用区域,例如工厂。 锁定的标识信息可以是一条或至少两条。 [0047]可选的,当获取的小区标识信息仅包括与锁定的标识信息匹配的小区标识信息时,可以接入锁定的标识信息对应的小区网络。 当获取的小区标识信息包括至少两条与锁定标识信息匹配的小区标识信息时,可以接入其中一条锁定标识信息对应的小区网络。 优选地,可以接入锁定的标识信息对应的信号强度最大的小区网络。 [0048] 可选地,步骤S 300 可以包括:当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息,且与锁定标识信息匹配的小区标识信息的信号强度不存在时,移动终端接入锁定标识信息对应的小区网络。 低于预设的强度阈值。 [0049] 在某些情况下,移动终端虽然可以接入锁定的标识信息对应的小区网络,但是该小区网络信号强度较差,无法为用户提供满意的通信服务。 因此,为了保证为用户提供满意的通信服务,可以在信号强度较大时接入锁定的标识信息对应的小区网络。 [0050] 本发明实施例提供的限制移动终端使用区域的方法,可以获取覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 否则,移动终端跳过接入无线通信网络。 本发明通过将当前位置的小区网络的小区标识信息与锁定的标识信息进行比对来控制移动终端的小区网络接入。 在本发明中,由于小区对应的区域小于位置区码对应的区域,因此可以更精确地限制移动终端的使用范围。 [0051] 基于图1所示实施例,如图3所示,本发明实施例提供了另一种限制移动终端使用区域的方法。 在步骤 S 之前 200 ,该方法还可以包括以下步骤。 [0052] 脚步 101 :确定覆盖移动终端当前位置的至少一个小区网络中信号强度最大的小区网络,将信号强度最大的小区网络对应的小区标识信息发送给与移动设备连接的控制设备。 [0053] 在本发明的另一个实施例中,可选地,也可以向控制设备发送覆盖移动终端当前所在位置的其他小区网络对应的小区标识信息。 当向控制设备发送多个小区标识信息时,可以同时向控制设备发送信号强度信息。 [0054] 脚步 102 :根据控制设备下发的区域锁定指令确定信号强度最大的小区网络对应的小区标识信息,区域锁定指令包括信号强度最大的小区网络对应的小区标识信息。 [0055] 区域锁定指令可以是用户对控制设备进行区域锁定操作后控制设备下发的,也可以是控制设备自动下发的。 [0056] 脚步 103 :确定信号强度最大的小区网络对应的小区标识信息作为锁定标识信息。 [0057]可以理解的是,当移动终端位于限制区域时,步骤S 101 到小号 103 可能被执行。 信号强度最大的小区网络是为受限区域当前位置的移动终端提供无线通信服务的小区网络之一。 小区网络具有最大信号强度,因此提供最高的无线通信服务质量。 当将信号强度最大的小区网络对应的小区标识信息设置为锁定标识信息时,移动终端可以接入服务质量较好的小区网络。 [0058] 步骤 101 到小号 103 是设置锁定标识信息的过程。 可以理解的是,不需要每次都在步骤S之前进行设置过程 200 被执行。 或者,步骤 S 101 到小号 103 可以在步骤S之前执行 100 , 以及一系列执行步骤 S 101 到小号 103 和步骤S 100 不限于本公开。 [0059] 控制设备可以是与移动终端通信连接的服务器、个人电脑、移动设备等。 在本发明中,移动终端可以通过WI-FI、通用串行总线(USB)路径等方式与控制设备进行通信连接。 步骤 S 之后 103 进行,步骤S 200 可以开始执行图1所示的步骤。 执行步骤 S 后 300 或步骤S 400 之后,移动终端还可以向控制设备返回小区网络接入结果,例如是否接入小区网络,或者接入小区网络的信息。 [0060] 当控制设备通过USB路径与移动终端通信连接时,参见图4,移动终端的流程 502 与控制设备通信 501 设置锁定标识信息并尝试访问小区可以包括以下内容。 [0061] 第1步:通过控制装置传送 501 通过USB路径,向移动终端获取小区标识信息的第一控制指令 502 ; [0062] 第二步:移动端后 502 通过USB口接收第一控制指令,通过USB口将第一控制指令转发给非接入层; [0063] 步骤3、非接入层解析第一控制指令,并将解析后的消息发送给接入层; [0064] 步骤4:接入层进行频率扫描,或者接收广播消息,获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息 502 ,确定覆盖移动终端当前位置的至少一个小区网络中信号强度最大的小区网络 502 ,向非接入层发送信号强度最大的小区网络对应的小区标识信息; [0065] 第五步:非接入层发送给控制设备 501 使用USB路径,接入层发送的小区标识信息; [0066] 第六步:发送,由控制设备 501 , 向移动端的区域锁定指令 502 采用USB路径,区域锁定指令包括信号强度最大的小区网络对应的小区标识信息; [0067] 第七步:转发,通过移动端USB口转发 502 , 非接入层的区域锁定指令; [0068] 步骤8、非接入层解析区域锁定指令,并将解析后的消息发送给接入层,解析后的消息中包含信号强度最大的小区网络对应的小区标识信息; [0069]步骤9:接入层将信号强度最大的小区网络对应的小区标识信息设置为锁定标识信息,在步骤4得到的小区标识信息中查找与锁定标识信息匹配的小区标识信息,如果是 查找到与锁定标识信息匹配的小区标识信息,接入锁定标识信息对应的小区网络,否则跳过接入无线通信网络,进行网络丢弃处理; 和 [0070] 第十步:返回,通过移动端 502 , 将步骤9的处理结果发送给控制设备 501 使用 USB 路径。 [0071] 接入层和非接入层是移动终端通信技术的另一种方式,本领域技术人员可以理解接入层和非接入层的上述工作过程。 [0072] 与上述方法实施例对应,本发明还提供了一种限制移动终端使用区域的装置。 [0073] 如图5所示,本发明实施例提供了一种限制移动终端使用区域的装置。 该装置应用于移动终端,该装置可以包括小区标识信息获取单元 100 , 匹配判定单元 200 , 一个网络访问单元 300 , 和一个网络丢弃单元 400 . [0074] 小区标识信息获取单元 100 用于获取覆盖所述移动终端当前位置的至少一个小区网络的小区标识信息,所述小区网络对应于所述移动终端支持的网络制式对应的无线通信网络,所述小区标识信息为 频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息。 [0075] 移动终端可以是手机、POS机、MIFI等。 [0076] 小区标识信息获取单元 100 可以包括频率扫描子单元(未示出)和/或广播接收子单元(未示出)。 [0077] 频率扫描子单元,用于进行频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0078] 广播接收子单元,用于接收小区广播消息,从广播消息中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0079] 匹配判定单元 200 用于判断小区标识信息是否包括与锁定标识信息匹配的小区标识信息,其中锁定标识信息的参数与小区标识信息的参数一一对应。 [0080] 当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定标识信息包括锁定频道号,当移动终端支持的网络制式为非GSM时,小区标识信息为锁定频道号。 信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0081] 网络接入单元 300 用于当小区标识信息获取单元获取到小区标识信息时,接入锁定的标识信息对应的小区网络 100 包括与锁定标识信息匹配的小区标识信息。 [0082] 网络丢弃单元 400用于当小区标识信息获取单元获取到小区标识信息时,跳过接入无线通信网络 100 不包括与锁定标识信息匹配的小区标识信息。 [0083] 进一步地,移动终端的网络接入功能可以在特定时间段内被锁定以不接入无线通信网络以丢弃网络。 例如,移动终端的小区切换和小区重选功能被锁定。 在移动终端的网络接入功能被锁定的时间超过特定时间后,小区标识信息获取单元 100 可能会再次触发。 [0084] 网络接入单元 300 可以用于当获取的小区标识信息包括与锁定标识信息匹配的小区标识信息以及与锁定标识信息匹配的小区标识信息的信号强度时,移动终端接入锁定标识信息对应的小区网络 不低于预设的强度阈值。 [0085] 在某些情况下,移动终端虽然可以接入锁定的标识信息对应的小区网络,但是该小区网络信号强度较差,无法为用户提供满意的通信服务。 因此,为了保证为用户提供满意的通信服务,可以在信号强度较大时接入锁定的标识信息对应的小区网络。 [0086] 本发明实施例提供的限制移动终端使用区域的装置,可以获取覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 否则,移动终端跳过接入无线通信网络。 本发明通过将当前位置的小区网络的小区标识信息与锁定的标识信息进行比对来控制移动终端的小区网络接入。 在本发明中,由于小区对应的区域小于位置区码对应的区域,因此可以更精确地限制移动终端的使用范围。 [0087] 基于图5所示实施例,如图6所示,本发明实施例提供了另一种限制移动终端使用区域的装置。 该装置还可以包括最强网络确定单元 101 , 识别信息确定单元 102 , 以及识别信息锁定单元 103 . [0088] 最强网络决定单位 101 用于确定覆盖移动终端当前所在位置的至少一个小区网络中信号强度最大的小区网络,将信号强度最大的小区网络对应的小区标识信息发送给与移动终端连接的控制设备 确定前的设备,由匹配确定单元 200 ,小区标识信息中是否包括与锁定的标识信息相匹配的小区标识信息。 [0089] 身份信息确定单元 102 用于根据控制设备下发的区域锁定指令确定信号强度最大的小区网络对应的小区标识信息, 区域锁定指令包括信号强度最大的小区网络对应的小区标识信息 . [0090] 区域锁定指令可以是用户对控制设备进行区域锁定操作后控制设备下发的,也可以是控制设备自动下发的。 [0091]识别信息锁定单元 103 用于将信号强度最大的小区网络对应的小区标识信息确定为锁定标识信息。 [0092] 信号强度最大的小区网络是为受限区域当前位置的移动终端提供无线通信服务的小区网络之一。 小区网络具有最大信号强度,因此提供最高的无线通信服务质量。 当将信号强度最大的小区网络对应的小区标识信息设置为锁定标识信息时,移动终端可以接入服务质量较好的小区网络。 [0093] 控制设备可以是与移动终端通信连接的服务器、个人电脑、移动设备等。 在本发明中,移动终端可以通过WI-FI、USB路径等方式与控制设备通信连接。 [0094] 相应地,本发明实施例还提供了一种存储介质。 存储介质用于存储应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0095]本发明实施例还提供了一种应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0096] 本发明还提供了一种与上述方法实施例对应的移动终端。 [0097] 本发明实施例提供的移动终端可以包括处理器、存储器、通信接口和总线。 [0098] 处理器、存储器和通信接口使用总线相互连接和通信。 [0099] 存储器存储可执行程序代码。 [0100] 处理器读取存储在存储器中的可执行程序代码,以运行与可执行程序代码对应的程序,以执行以下步骤获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,其中小区 网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断小区标识是否为 信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,接入锁定标识对应的小区网络 当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,则跳过无线通信网络的接入;或者当获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0101] 本发明实施例提供的移动终端中的处理器可以为基带芯片。 存储器可以是多芯片封装。 通信接口可以包括USB端口、射频器件和WI-FI芯片。 此外,本发明实施例提供的移动终端还可以包括用户识别模块卡。 [0102] 进一步的,如图7所示,本发明实施例提供的移动终端可以包括:基带芯片 701 , 一个射频分量 702 , 多芯片封装 703 , 订户识别模块卡(SIM卡) 704 , WI-FI芯片 705 , 和一个 USB 端口 706 . 射频成分 702 , 多芯片封装 703 , 用户识别模块卡 704, WI-FI芯片 705 , 和 USB 端口 706 都与基带芯片电连接 701 . [0103] 基带芯片 701 用于进行数据处理、完成与网络侧的信令交互、处理控制设备的控制命令和数据请求、使用SIM卡进行鉴权等操作 704 ,以及读/写多芯片封装 703 . [0104] 射频成分 702 被配置为提供移动WI-FI的第三代(3G)上行链路路径。 [0105] 多芯片封装 703 集成了闪存和双倍数据率同步动态随机存取存储器(DRAM)。 闪存用于存储处理器的图像和数据。 DRAM 被配置为存储运行的程序。 [0106] WI-FI芯片 705 用于承载移动终端的无线局域网连接。 [0107] USB端口 706 作为移动终端与控制设备的物理连接路径,承载控制设备与移动终端之间的数据交互。 [0108] 本发明实施例提供了另一种移动终端。 移动终端还可以包括电源管理单元。 电源管理单元为基带芯片、射频器件、多芯片封装、SIM卡、WI-FI芯片和USB接口供电。 [0109] 以上所述仅为本发明的实施例而已,并不用于限制本发明。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN107113765A(String), CN107113765B(String), EP3249983A1(String), EP3249983A4(String), EP3249983B1(String), JP2018505627A(String), JP6514350B2(String), US10182389B2(String), US20180035355A1(String), WO2016127432A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN107113765A(String), CN107113765B(String), EP3249983A1(String), EP3249983A4(String), EP3249983B1(String), JP2018505627A(String), JP6514350B2(String), US10182389B2(String), US20180035355A1(String), WO2016127432A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10182389B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN107113765A(String), CN107113765B(String), EP3249983A1(String), EP3249983A4(String), EP3249983B1(String), JP2018505627A(String), JP6514350B2(String), US10182389B2(String), US20180035355A1(String), WO2016127432A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), CN107113765A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.486 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), CN107113765B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), EP3249983A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), EP3249983A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), EP3249983B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), JP2018505627A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), JP6514350B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), US10182389B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), US20180035355A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270669(Integer), WO2016127432A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10182389B2(String), US10182389B2(String), 1547481600(Integer), 270669(Integer), 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184989(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 184989(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184989(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 184989(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20140245234A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 用于根据与移动终端的操作相关的输入来控制多个对象的显示的方法及其移动终端(String), US20140245234A1(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US14/105735(String), 1386864000(Integer), US20140245234A1(String), 1409155200(Integer), 美国(String), 2(Integer), KR(String), 17(Integer), 22(Integer), US20080250312A1 | US20080282202A1 | US20090197635A1 | US20100070926A1 | US20100125816A1 | US20100217685A1 | US20100248788A1 | US20110041101A1 | US20110281633A1 | US20120030569A1 | US20120162261A1 | US20120166997A1 | US20120192121A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130278484A1 | US20140059472A1 | US20140139637A1 | US20140143737A1 | US20140181751A1 | US20150077333A1(String), 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184990(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b850f04037a24014b34673e50a44c481.png(String), 184990(Integer), b850f04037a24014b34673e50a44c481.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 用于根据与移动终端的操作相关的输入来控制多个对象的显示的方法及其移动终端(String), US20140245234A1(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US14/105735(String), 1386864000(Integer), US20140245234A1(String), 1409155200(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 17(Integer), 22(Integer), US20080250312A1 | US20080282202A1 | US20090197635A1 | US20100070926A1 | US20100125816A1 | US20100217685A1 | US20100248788A1 | US20110041101A1 | US20110281633A1 | US20120030569A1 | US20120162261A1 | US20120166997A1 | US20120192121A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130278484A1 | US20140059472A1 | US20140139637A1 | US20140143737A1 | US20140181751A1 | US20150077333A1(String), \20230420\b850f04037a24014b34673e50a44c481.png(String), 25(Integer), 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.678 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 1. A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal, the method comprising:displaying a layout including a plurality of areas in which a plurality of objects are respectively displayed;receiving the input related to the operation of the mobile terminal;changing one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal; anddisplaying a layout including the changed areas.(String), 1.一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法,该方法包括:显示包括分别显示多个对象的多个区域的布局;接收与移动终端操作相关的输入;改变与移动终端的操作相关的输入对应的多个区域中的一个或多个区域;和显示包含更改区域的布局。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 2. The method of claim 1, wherein the input related to the operation of the mobile terminal is at least one of a motion of the mobile terminal, a user's breath, and a gesture.(String), 2.如权利要求1所述的方法,其中与移动终端的操作相关的输入为移动终端的动作、用户的呼吸、手势中的至少一种。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 3. The method of claim 2, further comprising:detecting a reciprocating motion direction corresponding to at least one of an up-down direction, a left-right direction, and a diagonal direction of the mobile terminal if the input related to the operation of the mobile terminal is a motion of the mobile terminal4. The method of claim 3, wherein the changing of the areas corresponding to the input related to the operation of the mobile terminal comprises changing one or more areas of the plurality of areas corresponding to the reciprocating motion direction.(String), 3.如权利要求2所述的方法,还包括:如果与移动终端的操作相关的输入是移动终端的运动,则检测对应于移动终端的上下方向、左右方向和对角线方向中的至少一个的往复运动方向4.如权利要求3所述的方法,其中改变与移动终端的操作相关的输入对应的区域包括改变多个区域中对应往复运动方向的一个或多个区域。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 5. The method of claim 1, further comprising:determining whether one of the plurality of areas is touched;determining whether the input related to the operation of the mobile terminal is received while the touch is maintained; andrearranging the remaining areas except for the touched area if the input related to the operation of the mobile terminal is received while the touch is maintained.(String), 5.如权利要求1所述的方法,还包括:确定多个区域之一是否被触摸;判断在保持触摸的情况下是否接收到与移动终端操作相关的输入;和如果在保持触摸的同时接收到与移动终端的操作相关的输入,则重新排列除触摸区域之外的其余区域。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 6. The method of claim 5, further comprising:searching for one or more objects associated with an object belonging to the touched area based on a property of the object if the input related to the operation of the mobile terminal is received while the touch is maintained; anddisplaying a layout in which the found objects are respectively displayed in the remaining areas.(String), 6.如权利要求5所述的方法,还包括:如果在保持触摸的同时接收到与移动终端的操作相关的输入,则基于对象的属性搜索与属于触摸区域的对象关联的一个或多个对象;和显示在剩余区域中分别显示找到的对象的布局。(String), 1(Integer), 4(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 7. The method of claim 6, further comprising:if the object belonging to the touch area is a portrait, searching for pictures associated with a person appearing on the portrait are, and respectively displaying the found pictures in the remaining areas.(String), 7.如权利要求6所述的方法,还包括:如果属于触摸区域的对象为人像,则在人像区域中查找与人像区域相关联的图片,并在其余区域分别显示查找到的图片。(String), 1(Integer), 5(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 8. The method of claim 1, wherein the displaying of the layout including the changed areas comprises arranging the plurality of objects on the changed areas in consideration of the properties of the objects, the properties regarding the horizontal and vertical formats of the objects.(String), 8.如权利要求1所述的方法,其中包括改变区域的布局的显示包括考虑到对象的属性,关于对象的水平和垂直格式的属性,将多个对象布置在改变区域上。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 9. The method of claim 1, wherein the displaying of the layout including the changed areas comprises moving an object displayed on a largest area among the plurality of objects to a smallest area and moving an object displayed on the smallest area to the largest area.(String), 9.如权利要求1所述的方法,其中包括改变区域的布局的显示包括将多个对象中显示在最大区域上的对象移动到最小区域,并将显示在最小区域上的对象移动到最大区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 10. The method of claim 3, further comprising:determining whether a number of one or more reciprocating motions of the mobile terminal is equal to or greater than a predetermined number if the direction of the reciprocating motions of the mobile terminal is determined; andadding a predetermined number of areas to areas constituting a layout of a current page if the number of the reciprocating motions is equal to or greater than the predetermined number.(String), 10.如权利要求3所述的方法,还包括:如果确定了移动终端的往复运动的方向,则判断移动终端的一次或多次往复运动的次数是否等于或大于预定次数;和如果往复运动的次数等于或大于预定数目,则将预定数目的区域添加到构成当前页面的布局的区域。(String), 1(Integer), 8(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 11. The method of claim 10, wherein the predetermined number of areas is a predetermined number of areas constituting a layout of a next page.(String), 11.如权利要求10所述的方法,其中预定数量的区域是构成下一页布局的预定数量的区域。(String), 1(Integer), 9(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 12. The method of claim 1, further comprising:displaying an icon for adjusting a number of the plurality of areas if a request for adjusting the number of the areas is received; andadding/removing one or more areas to/from the plurality of areas if an input related to operation of the mobile terminal is received while the icon for adjusting the number of the areas is touched.(String), 12.如权利要求1所述的方法,还包括:如果接收到调整区域数量的请求,则显示用于调整多个区域数量的图标;和如果在触摸用于调整区域数量的图标的同时接收到与移动终端的操作相关的输入,则向/从多个区域添加/删除一个或多个区域。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 13. A mobile terminal for controlling a display of a plurality of objects according to an input related to operation of the mobile terminal, the mobile terminal comprising:a display unit configured to display a layout including a plurality of areas in which the plurality of objects are respectively displayed;a sensor module configured to detect the input related to the operation of the mobile terminal; anda controller configured to change one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and to control the display unit to display a layout including the changed areas.(String), 13.一种用于根据与移动终端的操作相关的输入来控制多个对象的显示的移动终端,该移动终端包括:显示单元被配置为显示包括分别显示多个对象的多个区域的布局;传感器模块,用于检测与移动终端的操作相关的输入;和控制器被配置为对应于与移动终端的操作相关的输入来改变多个区域中的一个或多个区域,并且控制显示单元显示包括改变的区域的布局。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 14. The mobile terminal of claim 13, wherein the input related to the operation of the mobile terminal is at least one of a motion of the mobile terminal, a user's breath, and a gesture.(String), 14.如权利要求13所述的移动终端,其中与移动终端的操作相关的输入为移动终端的动作、用户的呼吸、手势中的至少一种。(String), 1(Integer), 12(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 15. The mobile terminal of claim 14, wherein the sensor module comprises at least one of a motion sensor for detecting the motion of the mobile terminal, a breath detection sensor for detecting the user's breath, and a camera sensor for sensing the gesture.(String), 15.如权利要求14所述的移动终端,其中传感器模块包括用于检测移动终端运动的运动传感器、用于检测用户呼吸的呼吸检测传感器和用于感应手势的摄像头传感器中的至少一种。(String), 1(Integer), 13(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 16. The mobile terminal of claim 14, wherein the sensor module detects a reciprocating motion direction corresponding to at least one of an up-down direction, a left-right direction, and a diagonal direction of the mobile terminal.(String), 16.如权利要求14所述的移动终端,其中传感器模块检测对应于移动终端的上下方向、左右方向和对角线方向中的至少一个的往复运动方向。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 17. The mobile terminal of claim 16, wherein the controller changes one or more areas of the plurality of areas corresponding to a reciprocating motion direction detected through the sensor module.(String), 17.如权利要求16所述的移动终端,其中控制器对应于通过传感器模块检测到的往复运动方向改变多个区域中的一个或多个区域。(String), 1(Integer), 15(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 18. The mobile terminal of claim 13, wherein the controller determines whether any one of the plurality of areas is selected, and rearranges the remaining areas except for the selected area if an input related to the mobile terminal is detected through the sensor module while the selection is maintained.(String), 18.如权利要求13所述的移动终端,其中控制器确定是否选择了多个区域中的任何一个,并且如果在保持选择的同时通过传感器模块检测到与移动终端相关的输入,则重新排列除了所选区域之外的剩余区域。(String), 1(Integer), 16(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 19. The mobile terminal of claim 18, wherein if the input related to the operation of the mobile terminal is detected through the sensor module while the selection is maintained, the controller searches for objects associated with an object belonging to the selected area based on a property of the selected area, and controls the display unit to display a layout in which the found objects are respectively displayed in the remaining areas.(String), 19.如权利要求18所述的移动终端,其中如果在保持选择的同时通过传感器模块检测到与移动终端的操作相关的输入,则控制器基于所选区域的属性搜索与属于所选区域的对象相关联的对象,并控制显示显示布局的单元,其中找到的对象分别显示在其余区域中。(String), 1(Integer), 17(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 20. The mobile terminal of claim 19, wherein if the object belonging to the selected area is a portrait, the controller searches for pictures associated with a person appearing on the portrait, and then controls the display unit to display the found pictures in the remaining areas, respectively.(String), 20.如权利要求19所述的移动终端,其中如果属于所选区域的对象是肖像,则控制器搜索与出现在肖像上的人相关联的图片,然后控制显示单元分别在其余区域中显示找到的图片。(String), 1(Integer), 18(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 21. The mobile terminal of claim 13, wherein the controller arranges the plurality of objects on the changed areas in consideration of the properties of the objects, the properties regarding the horizontal and vertical formats of the objects.(String), 21.如权利要求13所述的移动终端,其中控制器考虑到对象的属性,关于对象的水平和垂直格式的属性,将多个对象布置在改变的区域上。(String), 1(Integer), 19(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 22. The mobile terminal of claim 13, wherein the controller moves an object displayed on a largest area among the plurality of objects to a smallest area and moves an object displayed on the smallest area to the largest area.(String), 22.如权利要求13所述的移动终端,其中控制器将多个对象中显示在最大区域上的对象移动到最小区域,并将显示在最小区域上的对象移动到最大区域。(String), 1(Integer), 20(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 23. The mobile terminal of claim 14, wherein the controller determines whether the number of one or more reciprocating motions of the mobile terminal detected through the sensor module is equal to or greater than a predetermined number, and adds a predetermined number of areas to areas constituting a layout of a current page if the number of the reciprocating motions is equal to or greater than the predetermined number.(String), 23.如权利要求14所述的移动终端,其中控制器判断通过传感器模块检测到的移动终端的一个或多个往复运动的次数是否等于或大于预定数目,如果数目为,则将预定数目的区域添加到构成当前页面布局的区域往复运动的次数等于或大于预定次数。(String), 1(Integer), 21(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 24. The mobile terminal of claim 23, wherein the predetermined number of areas is a predetermined number of areas constituting a layout of a next page.(String), 24.如权利要求23所述的移动终端,其中预定数量的区域是构成下一页布局的预定数量的区域。(String), 1(Integer), 22(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184990(Integer), 25. The mobile terminal of claim 13, wherein the controller displays an icon for adjusting the number of the plurality of areas if a request for adjusting the number of the areas is received, and adds/removes one or more areas to/from the plurality of areas if an input related to operation of the mobile terminal is detected while the icon for adjusting the number of the areas is selected.(String), 25.如权利要求13所述的移动终端,其中如果接收到调整区域数量的请求,则控制器显示用于调整多个区域的数量的图标,并且如果与操作相关的输入,控制器向/从多个区域添加/删除一个或多个区域mobileterminalisdetectedwhiletheiconforadjustingthenumberoftheareasisselected.(String), 1(Integer), 23(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184990(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Feb. 22, 2013 in the Korean Intellectual Property Office and assigned Serial No. 10-2013-0019508, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an apparatus and method for managing a plurality of objects that are displayed on a touch screen. More particularly, the present invention relates to an apparatus and method for allowing a user of a mobile terminal to easily change a display of a plurality of objects on a touch screen according to a motion of the mobile terminal [0004]2. Description of the Related Art [0005]A touch screen with a touch panel mounted on a display device displays images and allows a user to easily input commands without using a keyboard or a mouse. The touch screen has been widely used in various electronic devices, such as a mobile terminal, a navigation system, a TV, Automated Teller Machines (ATMs), a Point-Of-Sale (POS) system, and the like. [0006]For example, with the variety of services and additional functions that can be provided by mobile terminals, many recent mobile terminals provide a Graphic User Interface (GUI) based on a touch screen. [0007]In order to raise the effective value of such mobile terminals and meet users' needs, various applications executable in mobile terminals are being developed. [0008]A mobile terminal can store basic applications developed by the mobile terminal's manufacturing company, as well as additional applications downloaded from application sales web sites through the Internet, and execute the applications. [0009]Accordingly, a mobile terminal, such as the latest smart phone, tablet PC, and the like, stores at least hundreds of applications, and shortcut keys for executing the applications individually are displayed in the form of icons on the touch screen of the mobile terminal. A user can touch one of the icons displayed on the touch screen of a mobile terminal to thus execute a desired application on the mobile terminal. Various visual objects, such as widgets, pictures, document, etc., other than the shortcut keys, may also be displayed on the touch screen of the mobile terminal. [0010]However, as the number of such various visual objects increases, another issue arises. The number of objects that can be displayed on the small screen of a mobile terminal is limited although the mobile terminal stores many visual objects. [0011]Accordingly, due to the spatial limitation of a display screen, there is a need for classifying and arranging visual objects that can be displayed on the screen. However, arranging the components of a layout at regular intervals is insufficient, and it is necessary for a user to be able to conveniently manage visual objects displayed on the screen of a mobile terminal, such as editing, moving, or deleting the visual objects. According to the related art, when a user wants to change a display of objects, the user should convert the screen of his/her mobile terminal into an Edit environment, and input commands for deleting or correcting objects, which causes onerousness and inconvenience and requires a long time for editing. [0012]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. [0013]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY OF THE INVENTION [0014]Aspects of the present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide an apparatus and method for allowing a user to conveniently change the components of a layout in which a plurality of objects are arranged according to his/her desired pattern. [0015]Another aspect of the present invention is to provide an apparatus and method for easily controlling an arrangement of a plurality of objects and a display of a layout in which the objects are arranged according to a motion of a mobile terminal. [0016]In accordance with an aspect of the present invention, a method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes displaying a layout including a plurality of areas in which a plurality of objects are respectively displayed, receiving the input related to the operation of the mobile terminal, changing one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. [0017]In accordance with another aspect of the present invention, a mobile terminal for controlling a display of a plurality of objects according to an input related to operation of the mobile terminal is provided. The mobile terminal includes a display unit configured to display a layout including a plurality of areas in which the plurality of objects are respectively displayed, a sensor module configured to detect the input related to the operation of the mobile terminal, and a controller configured to change one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and to control the display unit to display a layout including the changed areas. [0018]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0019]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0020]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention; [0021]FIG. 2 is a front perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0022]FIG. 3 is a rear perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0023]FIG. 4 is a flowchart of a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0024]FIGS. 5A through 8B show examples for explaining a process in which areas constituting a layout change according to directions of reciprocating motions of a mobile terminal according to an exemplary embodiment of the present invention; [0025]FIGS. 9A to 9D show examples for explaining a process in which areas constituting a layout change according to a breath according to an exemplary embodiment of the present invention; [0026]FIGS. 10A to 11D are views for explaining an arrangement rule of a layout according to an exemplary embodiment of the present invention; [0027]FIG. 12 is a flowchart for explaining a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0028]FIGS. 13A and 13B show examples for explaining a process in which different objects are respectively displayed on areas constituting a layout according to the property of a touched object according to an exemplary embodiment of the present invention; [0029]FIGS. 14A and 14B are flowcharts for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0030]FIGS. 15A to 15I show examples for explaining a process of adjusting a number of areas constituting a layout in the mobile terminal, according to an exemplary embodiment of the present invention; [0031]FIG. 16 is a flowchart for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; and [0032]FIGS. 17A to 17C show examples for explaining a process of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention. [0033]Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0034]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. [0035]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0036]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0037]It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. [0038]The exemplary embodiments that will be described below relate to a hand-held terminal, however, an apparatus and method for managing a plurality of objects displayed on a touch screen, according to exemplary embodiments of the present invention, may be applied to various electronic devices with touch screens, such as a navigation system, a television (TV), an Automated Teller Machine (ATM), a Point-Of-Sale (POS) system, and the like, as well as a mobile terminal, such as a mobile phone, a smart phone, a tablet PC, and the like. [0039]Also, in the following description, a mobile terminal may be a flexible device or a flexible display device. As a representative mobile terminal, a mobile phone is assumed, and some components of such a mobile terminal may be omitted or changed as necessary. [0040]Exemplary embodiments of the present invention provide a method of controlling a display of a plurality of objects according to an input related to a motion of a mobile terminal Exemplary embodiments of the present invention includes an operation of changing, if an input related to a motion of the mobile terminal is received when a layout including areas in which the plurality of objects are displayed is displayed, one or more areas corresponding to the input related to the motion of the mobile terminal among the areas constituting the layout; and an operation of displaying a layout comprised of the changed areas. The input related to the motion of the mobile terminal may correspond to a motion of the mobile terminal, a user's breath, a gesture, and the like. According to exemplary embodiments of the present invention, if an input related to a motion of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged. In this case, objects that are respectively displayed in the remaining areas may be objects searched in correspondence to the property of an object displayed on the touched area. Thereby, a user can easily change components corresponding to the areas of a layout, as well as changing the areas of the layout. [0041]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention. [0042]Referring to FIG. 1, the mobile terminal 100 may be connected to an external electronic device (not shown) using at least one of a communication module 120, a connector 165, and an earphone connecting jack 167. The external electronic device may include an earphone, an external speaker, a Universal Serial Bus (USB) memory, a battery charger, a Cradle/Dock, a Digital Multimedia Broadcasting (DMB) antenna, a mobile payment system, healthcare equipment (a blood glucose meter, etc.), a game, a vehicle navigation system, and the like, which can be removably connected to the mobile terminal 100 through a line. The external electronic device may include a Bluetooth communication apparatus, a Near Field Communication (NFC) apparatus, a WiFi Direct communication apparatus, a Wireless Access Point (WAP), and the like, which can be connected to the mobile terminal 100 in a wireless fashion. The mobile terminal 100 may be connected to one of other mobile terminals or electronic devices (for example, a mobile phone, a smart phone, a tablet PC, a desktop PC, and a server) in a wired/wireless fashion. [0043]The mobile terminal 100 includes a touch screen 190 and at least one touch screen controller 195. The mobile terminal 100 may further include a controller 110, the communication module 120, a multimedia module 140, a camera module 150, an input/output module 160, a sensor module 170, a storage unit 175, and a power supply unit 180. [0044]The communication module 120 includes a mobile communication module 121, a sub communication module 130, and a broadcasting communication module 141. [0045]The sub communication module 130 includes at least one of a Wireless LAN (WLAN) module 131 and a short-range communication module 132. The multimedia module 140 includes at least one of an audio play module 142 and a video play module 143. The camera module 150 may include at least one of a first camera 151 and a second camera 152. The camera module 150 may also include at least one of a body tube 155 for zooming in/out the first and/or second camera 151 or 152, a motor unit 154 for controlling the movement of the body tube 155, and a flash 153 for providing a light source for photographing, according to the main purpose of the mobile terminal 100. The input/output module 160 may includes at least one of a button 161, a microphone 162, a speaker 163, a vibration device 164, the connector 165, and a keypad 166. [0046]The controller 110 may include a CPU 111, a Read Only Memory (ROM) 112 that stores control programs for controlling the mobile terminal 100, and a Random Access Memory (RAM) 113 that stores signals or data received from the outside or is used as a memory area for tasks being performed by the mobile terminal 100. The CPU 111 may include one or more cores, such as a single core, a dual core, a triple core, or a quad core. The CPU 111, ROM 112, and RAM 113 may be connected to each other through internal buses. [0047]Also, the controller 110 may control the communication module 120, the multimedia module 140, the camera module 150, the input/output module 160, the sensor module 170, the storage unit 175, the power supply unit 180, the touch screen 190, and the touch screen controller 195. [0048]When a user input device, such as an input unit 168 or a user's finger, touches, approaches, or is located in proximity to at least one of a plurality of objects or items displayed on the touch screen 190, the controller 110 senses a user input, and identifies an object corresponding to a location at which the user input has been sensed on the touch screen 190. The user input through the touch screen 190 may be one of a direct touch input of directly touching an object, and a hovering input which is an indirect touch input of approaching an object within a predetermined identification distance without directly touching the object. For example, when a user brings the input unit 168 close to the touch screen 190, an object located straightly below the input unit 168 may be selected. The user input may be a gesture input through the camera module 150, a switch/button input through the button 161 or the keypad 166, or a voice input through the microphone 16, other than a user input through the touch screen 190. [0049]The object or item (such as a function item) may be at least one of an application, a menu, document, a widget, a picture, video, E-mail, a Short Message Service (SMS) message, a Multimedia Message Service (MMS) message, and the like, which have been or can be displayed on the touch screen 190 of the mobile terminal 100. The object or item can be selected, executed, deleted, canceled, stored, or changed by the user input device. The item may be a button, an icon (such as a shortcut icon), a thumbnail image, or a folder that stores at least one object in a mobile terminal. The item may be displayed in the form of an image, text, and the like. [0050]A shortcut item is an image that is displayed on the touch screen 190 to quickly execute a call, a contact list, a menu, etc., which are provided by each application or by the mobile terminal 100. If a command or selection for executing a shortcut item is received, the corresponding application is executed. [0051]When the input unit 168 approaches the touch screen 190 or is placed in proximity to the touch screen 190, the controller 110 may sense a user input event such as a hovering event. If a user input event is generated with respect to a predetermined item or according to a predetermined method, the controller 110 performs predetermined program operation corresponding to the user input event. [0052]The controller 110 may output a control signal to the input unit 168 or the vibration device 164. The control signal may include information regarding a vibration pattern, and the input unit 168 or the vibration device 164 may generate vibration according to the vibration pattern. The information regarding the vibration pattern may represent a vibration pattern, an identifier of a vibration pattern, or the like. Alternatively, the control signal may include only a request for generation of vibration. [0053]The mobile terminal 100 may include at least one of the mobile communication module 121, the WLAN module 131, and the short-range communication module 132, according to the function of the mobile terminal 100. [0054]The mobile communication module 121 may connect the mobile terminal 100 to an external electronic device through mobile communication using one or more antennas (not shown) under the control of the controller 110. The mobile communication module 121 may transmit/receive radio signals for a voice call, a video call, a SMS message, or a MMS message to/from a mobile phone (not shown), a smart phone (not shown), a tablet PC (not shown), or another electronic device (not shown) when the corresponding phone number is input to the mobile terminal 100. [0055]The sub communication module 130 may include at least one of the WLAN module 131 and the short-range communication module 132 as described above. For example, the sub communication module 130 may include one of the WLAN module 131 and the short-range communication module 132, or both the WLAN module 131 and the short-range communication module 132. [0056]The WLAN module 131 may be connected to the Internet at a place in which a WAP has been installed, under the control of the controller 110. The WLAN module 131 supports the IEEE802.11x standard. The short-range communication module 132 performs short-range communication between the mobile terminal 100 and an external electronic device in a wireless fashion under the control of the controller 110. The short-range communication may include Bluetooth, Infrared Data Association (IrDA), WiFi-Direct communication, NFC, and the like. [0057]The controller 110 may transmit a control signal according to a haptic pattern to the input unit 168 through the sub communication module 130. [0058]The broadcasting communication module 141 may receive broadcasting signals (for example, TV broadcasting signals, radio broadcasting signals, or data broadcasting signals) and broadcasting additional information (for example, an Electric Program Guide (EPS) or an Electric Service Guide (ESG)) transmitted from a broadcast station through a broadcasting communication antenna (not shown), under the control of the controller 110. [0059]The multimedia module 140 may include the audio play module 142 and the video play module 143 as described above. The audio play module 142 may reproduce a digital audio file (for example, a file with the extension “.mp3”, “.wma”, “.ogg” or “.wav”) that is stored in the storage unit 175 or received from an external device, under the control of the controller 110. The video play module 143 may reproduce a digital video file (for example, a file with the extension “.mpeg”, “.mpg”, “.mp4”, “.avi”, “.mov”, or “.mkv”) that is stored or received, under the control of the controller 110. The multimedia module 140 may be integrated with the controller 110. [0060]The camera module 150 may include at least one of the first and second cameras 151 and 152 for photographing still images or moving images under the control of the controller 110. The camera module 150 may also include at least one among the body tube 155 for zooming in/out to photograph a subject, the motor unit 154, and the flash 153 for providing a secondary light source required for photographing the subject. The first camera 151 may be disposed in the front side of the mobile terminal 100, and the second camera 152 may be disposed in the rear side of the mobile terminal 100. [0061]Each of the first and second cameras 151 and 152 may include a lens system, an image sensor, and the like. Each of the first and second cameras 151 and 152 converts an optical signal received (or photographed) through the lens system into an electrical image signal, and outputs the electrical image signal to the controller 110. Accordingly, a user can photograph a moving image or a still image through the first and second cameras 151 and 152. [0062]The input/output module 160 may include at least one among at least one button 161, at least one microphone 162, at least one speaker 163, at least one vibration device 164, the connector 165, the keypad 166, the earphone connecting jack 167, and the input unit 168. However, the input/output module 160 is not limited to the above-mentioned devices, and a cursor control, such as a mouse, a trackball, a joystick, or cursor direction keys, may also be provided to control the movement of a cursor on the touch screen 190. [0063]The button 161 may be formed on the front, side, or rear surface of the housing (or case) of the mobile terminal 100, and may include at least one among a power/lock button, a volume button, a menu button, a home button, a back button, and a search button. [0064]The microphone 162 may receive a voice or sound under the control of the controller 110 to generate an electrical signal. [0065]The speaker 163 may output sound corresponding to various signals or data (for example, radio data, broadcasting data, digital audio data, digital video data, etc.) out of the mobile terminal 100 under the control of the controller 110. The speaker 163 may output sound (for example, button manipulation sound corresponding to a call, currency connection sound, the other party's voice, etc.) corresponding to a function that is performed by the mobile terminal 100. One or more speakers 163 may be provided at one or more appropriate locations on the housing of the mobile terminal 100. [0066]The vibration device 164 may convert an electrical signal into mechanical vibration under the control of the controller 110. For example, if a voice or video call is made by another device (not shown) when the mobile terminal 100 is in a vibration mode, the vibration device 164 operates. One or more vibration devices 164 may be provided in the housing of the mobile terminal 100. The vibration device 164 may operate in correspondence to a user input through the touch screen 190. [0067]The connector 165 may be used as an interface for connecting the mobile terminal 100 to an external electronic device or a power source (not shown). The controller 110 may transmit data stored in the storage unit 175 to an external electronic device or receive data from the external electronic device through a wired cable connected to the connector 165. The mobile terminal 100 may receive power from a power source or charge a battery using the power source through the wired cable connected to the connector 165. [0068]The keypad 166 may receive a key input from a user to control the mobile terminal 100. The keypad 166 includes a physical keypad (not shown) formed on the mobile terminal 100 or a virtual keypad (not shown) displayed on the touch screen 190. The physical keypad formed on the mobile terminal 100 may be excluded according to the performance or structure of the mobile terminal 100. [0069]The earphone (not shown) may be inserted into the earphone connecting jack 167 to connect to the mobile terminal 100. [0070]The input unit 168 may be inserted into and held in the mobile terminal 100, and when in use, the input unit 168 may be drawn or separated from the mobile terminal 100. A detachment/attachment recognition switch 169 that operates in correspondence to attachment and detachment of the input unit 168 may be provided in an area of the mobile terminal 100 into which the input unit 168 is inserted. The detachment/attachment recognition switch 169 may output a signal corresponding to attachment/separation of the input unit 168 to the controller 110. The detachment/attachment recognition switch 169 may be configured to directly or indirectly contact the input unit 168 when the input unit 169 is attached in the mobile terminal 100. Accordingly, the detachment/attachment recognition switch 169 generates a signal (i.e., a signal for notifying attachment or separation of the input unit 168) corresponding to attachment or separation of the input unit 168 based on whether the detachment/attachment recognition switch 169 contacts the input unit 168, and outputs the signal to the controller 110. [0071]The sensor module 170 may include at least one sensor for detecting the state of the mobile terminal 100. For example, the sensor module may include at least one sensor among a proximity sensor (not shown) for detecting an approach to the mobile terminal 100, an ambient light sensor (not shown) for detecting the ambient light intensity around the mobile terminal 100, a motion sensor (not shown) for detecting a motion (for example, rotation, acceleration, vibration) of the mobile terminal 100, a geo-magnetic sensor (not shown) for detecting a point of the compass of the mobile terminal 100 using the earth's magnetic field, a gravity sensor (not shown) for detecting a direction in which gravity is applied, an altimeter (not shown) for measuring atmospheric pressure to detect an altitude, and a GPS module 157. A camera sensor for sensing a user's gesture may also be included in the sensor module 170. [0072]The motion sensor among the above-mentioned sensors senses the location, movement, and the like of the mobile terminal 100 using an acceleration sensor, a gyro sensor, a tilt sensor, or their combinations. However, the sensors are not limited to the above-mentioned sensors, and may include other types of a sensor capable of sensing the reciprocating motions, movement directions, and the like of the mobile terminal 100. [0073]Sensing data (that is, motion information) output through the motion sensors may have a direction and a magnitude. For example, an acceleration sensor for sensing the acceleration of the mobile terminal 100 can sense acceleration with respect to at least one reference-axis direction of x, y, and z axes, and output the acceleration information. The reference-axis may be an axis (for example, the up-down (z-axis), left-right (x-axis), and front-rear (y-axis) directions of the mobile terminal 100) according to the direction of the mobile terminal 100, or may be an axis according to the direction of gravity (the direction (z-axis) of gravity and directions (z and y axes) perpendicular to the direction of gravity). [0074]The sensor module 170 may further include a calculator (not shown) for integrating sensed angular velocity, velocity, etc. over time to calculate a rotation angle, a direction, velocity, a travel distance, a location, a trajectory, and the like according to a motion of the mobile terminal 100, and output the calculated information. The calculator may be included in the controller 110. The calculator may also include a frequency filter for blocking or passing a specific band of a signal such as sensed acceleration in order to calculate a trajectory, etc. or effectively analyze the direction of a motion. [0075]When the sensor module 170 includes the calculator, the calculator may calculate a direction or angle in or at which the mobile terminal 100 moves, and transfer the result of the calculation to the controller 100. However, the direction or angle in or at which the mobile terminal 100 moves may be calculated by the controller 110. The direction in which the mobile terminal 100 moves may be basically an up-down direction or a left-right direction. The direction in which the mobile terminal 100 moves may be a front direction in which the mobile terminal 100 is pulled horizontally toward a user or a back direction in which the mobile terminal 100 is pushed horizontally against the user. A tilting direction in which the mobile terminal 100 is tilted with respect to a reference axis is included in the direction of a motion. When the angle at which the mobile terminal 100 moves is calculated in a direction which the mobile terminal 100 is tilted under an assumption that the current position of the mobile terminal 100 is at 0 degree, a direction diagonal to the direction in which the mobile terminal 100 moves also may be included in the direction of a motion. [0076]According to an exemplary embodiment of the present invention, the sensor module 170 may also include a breath detection sensor for using a user's breath as a control command to change the configuration of a layout according to the user's breath. The breath detection sensor is attached on the outer surface of the mobile terminal 100, and detects a user's breath or wind brown through an inlet. The breath detection sensor may be a wind velocity sensor that outputs an electrical signal according to a user's breath. The wind velocity sensor transfers an output value that increases at a constant rate according to a user's breath intensity to the controller 110. Alternatively, the breath detection sensor may be a temperature sensor or a humidity sensor capable of sensing a user's breath, in which case the temperature sensor or the humidity sensor can transfer various levels of output values to the controller 110 according to a user's breath intensity. [0077]The GPS module 157 can receive radio waves from a plurality of GPS satellites (not shown) on the orbit around the earth, and calculate the location of the mobile terminal 100 based on a time of arrival of the radio waves from the GPS satellites to the mobile terminal 100. [0078]The storage unit 175 may store signals or data that is input/output according (String), 优先 [0001] 此申请根据 35 U.S.C. 2013 年 2 月 22 日向韩国知识产权局提交的韩国专利申请的第 119(a) 条,并转让了序列号 10-2013-0019508,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及一种用于管理在触摸屏上显示的多个对象的设备和方法。 更具体地,本发明涉及一种用于允许移动终端的用户根据移动终端的动作容易地改变触摸屏上的多个对象的显示的设备和方法 [0004] 2.相关技术的描述 [0005] 具有安装在显示设备上的触摸面板的触摸屏显示图像并允许用户在不使用键盘或鼠标的情况下轻松输入命令。 触摸屏已广泛应用于各种电子设备,例如移动终端、导航系统、电视、自动柜员机(ATM)、销售点(POS)系统等。 [0006] 例如,随着移动终端可以提供的各种服务和附加功能,最近的许多移动终端都提供了基于触摸屏的图形用户界面(GUI)。 [0007] 为了提高此类移动终端的有效价值并满足用户的需求,正在开发可在移动终端中执行的各种应用程序。 [0008] 移动终端可以存储移动终端制造公司开发的基本应用程序,以及通过互联网从应用程序销售网站下载的附加应用程序,并执行这些应用程序。 [0009] 相应地,移动终端,例如最新的智能手机、平板电脑等,存储了至少数百个应用程序,并且用于单独执行应用程序的快捷键以图标的形式显示在移动终端的触摸屏上 . 用户可以触摸显示在移动终端的触摸屏上的图标之一,从而在移动终端上执行期望的应用。 移动终端的触摸屏上还可以显示除快捷键之外的各种可视对象,如小部件、图片、文档等。 [0010] 然而,随着这种各种视觉对象的数量增加,出现了另一个问题。 移动终端虽然存储了很多可视对象,但在移动终端的小屏幕上可以显示的对象的数量是有限的。 [0011] 因此,由于显示屏幕的空间限制,需要对可显示在屏幕上的视觉对象进行分类和排列。 然而,将布局的组成部分等间隔排列是不够的,需要用户能够方便地管理移动终端屏幕上显示的可视对象,例如对可视对象进行编辑、移动或删除等。 现有技术中,当用户想要改变对象的显示时,需要将自己的移动终端屏幕转换为Edit环境,并输入删除或更正对象的命令,造成繁重不便,需要 很长一段时间的编辑。 [0012] 上述信息仅作为背景信息提供以帮助理解本公开。 没有做出任何决定,也没有做出断言,关于上述任何内容是否可以用作关于本发明的现有技术。 [0013] 上述信息仅作为背景信息提供以帮助理解本公开。 没有做出任何决定,也没有做出断言,关于上述任何内容是否可以用作关于本发明的现有技术。 发明内容 [0014]本发明的方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面是提供一种允许用户方便地改变布局的组件的设备和方法,其中多个对象根据他/她的期望图案排列。 [0015] 本发明的另一方面在于提供一种用于容易地控制多个对象的布置以及其中根据移动终端的运动布置对象的布局的显示的设备和方法。 [0016] 根据本发明的一方面,提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括显示包括多个区域的布局,其中分别显示多个对象,接收与移动终端的操作相关的输入,改变与与移动终端相关的输入对应的多个区域中的一个或多个区域。 移动终端的操作,以及显示包括改变区域的布局。 [0017] 根据本发明的另一方面,提供了一种用于根据与移动终端的操作相关的输入来控制多个对象的显示的移动终端。 移动终端包括:显示单元,被配置为显示包括多个区域的布局,在该多个区域中分别显示多个对象;传感器模块,被配置为检测与移动终端的操作相关的输入;以及控制器,被配置为改变 对应于与移动终端的操作相关的输入的多个区域中的一个或多个,并控制显示单元显示包括改变的区域的布局。 [0018] 通过以下详细描述,本发明的其他方面、优点和显着特征对于本领域技术人员将变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0019] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0020] 如图。 附图说明图1是示出根据本发明示例性实施例的移动终端的框图; [0021] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图; [0022] 如图。 图3是根据本发明示例性实施例的移动终端的后透视图; [0023] 如图。 图4是根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图; [0024] 图 图5A至图8B示出了用于解释根据本发明示例性实施例的构成布局的区域根据移动终端的往复运动方向改变的处理的示例; [0025] 图 图9A至9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的处理的示例; [0026] 图 图10A~图11D是用于说明本发明的实施方式的布局的排列规则的图。 [0027] 如图。 图12是用于说明根据本发明示例性实施例的移动终端中改变构成布局的区域的方法的流程图; [0028] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的特性将不同对象分别显示在构成布局的区域上的处理的示例; [0029]图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; [0030] 图 图15A至图15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例; [0031] 如图。 图16是用于说明根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; 和 [0032] 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0033] 在整个附图中,相同的附图标记将被理解为指代相同的部件、组件和结构。 示例性实施例的详细描述 [0034] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,可以省略对众所周知的功能和结构的描述。 [0035] 以下描述和权利要求中使用的术语和词语不限于书目含义,而仅由发明人使用以使对本发明的理解清晰一致。 因此,本领域技术人员应当清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0036] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0037] 应当理解,尽管在本文中可以使用术语第一、第二等来描述各种元素,但是这些元素不应受到这些术语的限制。 这些术语仅用于区分一个元素与另一个元素。 例如,可以将第一元件称为第二元件,并且类似地,可以将第二元件称为第一元件,而不脱离本发明的范围。 如本文所用,单数形式“a”、“an”和“the”旨在也包括复数形式,除非上下文另有明确指示。 [0038] 下面将描述的示例性实施例涉及手持终端,然而,根据本发明示例性实施例的用于管理显示在触摸屏上的多个对象的设备和方法可以应用于各种电子设备 具有触摸屏,例如导航系统、电视(TV)、自动柜员机(ATM)、销售点(POS)系统等,以及移动终端,例如移动 手机、智能手机、平板电脑等。 [0039] 此外,在以下描述中,移动终端可以是柔性设备或柔性显示设备。 作为代表性的移动终端,假设是移动电话,并且可以根据需要省略或改变这种移动终端的一些组件。 [0040]本发明的示例性实施例提供了一种根据与移动终端的运动相关的输入来控制多个对象的显示的方法。 当显示包括显示多个对象的区域的布局时,接收移动终端,构成布局的区域中与移动终端的运动相关的输入对应的一个或多个区域; 以及显示由改变的区域组成的布局的操作。 与移动终端的动作相关的输入可以对应于移动终端的动作、用户的呼吸、手势等。 根据本发明的示例性实施例,如果在构成布局的区域之一被触摸时检测到与移动终端的运动相关的输入,则重新排列除了被触摸区域之外的其余区域。 在这种情况下,分别显示在剩余区域中的对象可以是与显示在触摸区域上的对象的属性相对应的搜索对象。 因此,用户可以容易地改变与布局的区域相对应的组件,以及改变布局的区域。 [0041] 如图。 图1是示出根据本发明示例性实施例的移动终端的框图。 [0042] 参考图。 1、移动端 100 可以使用通信模块中的至少一个连接到外部电子设备(未示出) 120 , 一个连接器 165 和耳机连接插孔 167 . 外部电子设备可以包括耳机、外部扬声器、通用串行总线(USB)存储器、电池充电器、底座/底座、数字多媒体广播(DMB)天线、移动支付系统、医疗保健设备(血液 血糖仪等)、游戏、车载导航系统等,可拆卸地连接到移动终端 100 通过一条线。 外部电子设备可以包括蓝牙通信装置、近场通信(NFC)装置、WiFi Direct通信装置、无线接入点(WAP)等,它们可以连接到移动终端 100 以无线方式。 移动终端 100 可以有线/无线方式连接到其他移动终端或电子设备(例如,手机、智能手机、平板电脑、台式电脑和服务器)之一。 [0043] 移动终端 100 包括一个触摸屏 190 和至少一个触摸屏控制器 195 . 移动终端 100 还可以包括控制器 110 , 通讯模块 120 , 多媒体模块 140 , 一个摄像头模块 150 , 输入/输出模块 160 , 一个传感器模块 170 , 一个存储单元 175 , 和一个电源单元 180 . [0044] 通讯模块 120 包括一个移动通信模块 121 , 一个子通信模块 130 ,以及广播通信模块 141 . [0045] 子通讯模块 130 包括至少一个无线 LAN (WLAN) 模块 131 和一个短距离通信模块 132 . 多媒体模块 140 包括至少一个音频播放模块 142 和一个视频播放模块 143 . 摄像头模组 150 可以包括第一相机中的至少一个 151 和第二台相机 152 . 摄像头模组 150 还可以包括至少一个体管 155 用于放大/缩小第一台和/或第二台摄像机 151 或者 152 , 一个电机单元 154 用于控制体管的运动 155 , 和一个闪光灯 153 根据移动终端的主要用途,为拍照提供光源 100 . 输入/输出模块 160 可以包括至少一个按钮 161 , 麦克风 162 , 扬声器 163 , 振动装置 164 , 连接器 165 , 和一个键盘 166 . [0046] 控制器110 可能包括一个 CPU 111 , 只读存储器 (ROM) 112 存储用于控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 存储从外部接收的信号或数据或用作移动终端正在执行的任务的存储区域 100 . 中央处理器 111 可以包括一个或多个核,例如单核、双核、三核或四核。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线相互连接。 [0047] 此外,控制器 110 可以控制通讯模块 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 存储单元 175 , 电源单元 180 , 触摸屏 190 , 和触摸屏控制器 195 . [0048] 当用户输入设备,例如输入单元 168 或用户的手指、触摸、接近或位于触摸屏上显示的多个对象或项目中的至少一个的附近 190 , 控制器 110 感测用户输入,并识别与在触摸屏上感测到用户输入的位置相对应的对象 190 . 用户通过触摸屏输入 190 可以是直接触摸对象的直接触摸输入和不直接触摸对象而接近预定识别距离内的对象的间接触摸输入的悬停输入之一。 例如,当用户将输入单元 168 靠近触摸屏 190 , 位于输入单元正下方的对象 168 可以选择。 用户输入可以是通过相机模块的手势输入 150 , 一个开关/按钮通过按钮输入 161 或键盘 166 ,或通过麦克风输入的语音 16 , 除了通过触摸屏的用户输入 190 . [0049] 对象或项(例如功能项)可以是应用程序、菜单、文档、小部件、图片、视频、电子邮件、短消息服务(SMS)消息、多媒体消息服务中的至少一个 (MMS)消息等,已经或可以在触摸屏上显示 190 移动终端的 100 . 对象或项目可以由用户输入设备选择、执行、删除、取消、存储或改变。 该项目可以是按钮、图标(例如快捷方式图标)、缩略图或移动终端中存储至少一个对象的文件夹。 该项目可以以图像、文本等的形式显示。 [0050] 快捷项目是显示在触摸屏上的图像 190 快速执行各个应用或移动终端提供的通话、联系人列表、菜单等 100 . 如果接收到用于执行快捷方式项的命令或选择,则执行相应的应用程序。 [0051] 当输入单元 168 接近触摸屏 190 或放置在触摸屏附近 190 , 控制器 110 可以感测用户输入事件,例如悬停事件。 如果针对预定项目或根据预定方法生成用户输入事件,则控制器 110 执行对应于用户输入事件的预定程序操作。 [0052] 控制器 110 可以向输入单元输出控制信号 168 或振动装置 164 . 控制信号可以包括关于振动模式的信息,以及输入单元 168 或振动装置 164 可以根据振动模式产生振动。 关于振动模式的信息可以表示振动模式、振动模式的标识符等。 或者,控制信号可以仅包括产生振动的请求。 [0053] 移动终端 100 可以包括至少一个移动通信模块 121 , WLAN 模块 131 , 和短距离通信模块 132,根据手机端的功能 100 . [0054] 移动通信模块 121 可以连接移动终端 100 在控制器的控制下,使用一根或多根天线(未显示)通过移动通信连接到外部电子设备 110 . 移动通信模块 121 可以向/从移动电话(未示出)、智能手机(未示出)、平板电脑(未示出)发送/接收用于语音呼叫、视频呼叫、SMS消息或MMS消息的无线电信号, 当对应的电话号码输入到移动终端时,或另一个电子设备(未示出) 100 . [0055] 子通讯模块 130 可以包括至少一个 WLAN 模块 131 和短距离通信模块 132 如上所述。 例如子通信模块 130 可能包括 WLAN 模块之一 131 和短距离通信模块 132 , 或两者 WLAN 模块 131 和短距离通信模块 132 . [0056] 无线局域网模块 131 在控制器的控制下,可以在安装了 WAP 的地方连接到 Internet 110 . 无线局域网模块 131 支持 IEEE802.11x 标准。 短距离通信模块 132 在移动终端之间进行短距离通信 100 以及在控制器控制下以无线方式的外部电子设备 110 . 短距离通信可以包括蓝牙、红外数据协会(IrDA)、WiFi-Direct通信、NFC等。 [0057] 控制器 110 可以根据触觉模式向输入单元发送控制信号 168 通过子通讯模块 130 . [0058] 广播通信模块 141 可以接收广播信号(例如,电视广播信号、无线电广播信号或数据广播信号)和广播从广播站发送的附加信息(例如,电子节目指南(EPS)或电子服务指南(ESG)) 通过广播通信天线(未显示),在控制器的控制下 110 . [0059] 多媒体模块 140 可能包括音频播放模块 142 和视频播放模块 143 如上所述。 音频播放模块 142 可以再现存储在存储单元中的数字音频文件(例如,扩展名为“.mp3”、“.wma”、“.ogg”或“.wav”的文件) 175 或从外部设备接收,在控制器的控制下 110 . 视频播放模块 143 可以复制存储或 收到,在控制器的控制下 110 . 多媒体模块 140 可与控制器集成 110 . [0060] 摄像头模组 150 可以包括第一和第二相机中的至少一个 151 和 152 在控制器的控制下拍摄静止图像或运动图像 110 . 摄像头模组 150 还可以包括至少一种管体 155 用于放大/缩小拍摄对象,电机单元 154 , 和闪光灯 153 用于提供拍摄对象所需的辅助光源。 第一台相机 151 可以设置在移动终端的正面 100 , 和第二台相机 152 可以设置在移动终端的背面 100 . [0061] 第一和第二相机中的每一个 151 和 152 可以包括透镜系统、图像传感器等。 第一和第二相机中的每一个 151 和 152 将通过镜头系统接收(或拍摄)的光信号转换为电图像信号,并将电图像信号输出到控制器 110 . 因此,用户可以通过第一和第二相机拍摄运动图像或静止图像 151 和 152 . [0062] 输入/输出模块 160 可以包括至少一个按钮中的至少一个 161 , 至少一个麦克风 162 , 至少一位发言者 163 , 至少一个振动装置 164 , 连接器 165 , 键盘 166 , 耳机连接插孔 167 , 和输入单元 168 . 然而,输入/输出模块 160 不限于上述设备,还可以提供鼠标、轨迹球、操纵杆或光标方向键等光标控件来控制光标在触摸屏上的移动 190 . [0063] 按钮 161 可以形成在移动终端的外壳(或外壳)的正面、侧面或背面 100 ,并且可以包括电源/锁定按钮、音量按钮、菜单按钮、主页按钮、返回按钮和搜索按钮中的至少一个。 [0064] 麦克风 162 可以在控制器的控制下接收语音或声音 110 产生电信号。 [0065] 演讲者 163 可以将与各种信号或数据(例如,无线电数据、广播数据、数字音频数据、数字视频数据等)对应的声音输出到移动终端之外 100 在控制器的控制下 110 . 演讲者 163 可以输出与移动终端执行的功能对应的声音(例如,与呼叫对应的按钮操作声音、货币连接声音、对方的语音等) 100 . 一位或多位演讲者 163 可以在移动终端的外壳上的一个或多个适当位置提供 100 . [0066] 振动装置 164 可在控制器的控制下将电信号转换为机械振动 110 . 例如,如果在移动终端时由另一个设备(未示出)进行语音或视频通话 100 处于振动模式时,振动装置 164 运作。 一个或多个振动装置 164 可以设置在移动终端的外壳中 100 . 振动装置 164 可以对应于通过触摸屏的用户输入进行操作 190 . [0067] 连接器 165 可作为连接移动终端的接口 100 连接到外部电子设备或电源(未显示)。 控制器 110 可以传输存储在存储单元中的数据 175 到外部电子设备或通过连接到连接器的有线电缆从外部电子设备接收数据 165 . 移动终端 100 可以通过连接到连接器的有线电缆从电源接收电力或使用电源为电池充电 165 . [0068] 键盘 166 可以接收来自用户的按键输入以控制移动终端 100 . 键盘 166 包括在移动终端上形成的物理键盘(未显示) 100 或触摸屏上显示的虚拟键盘(未显示) 190 . 在移动终端上形成的物理键盘 100 可根据移动终端的性能或结构排除 100 . [0069] 耳机(未显示)可以插入耳机连接插孔 167 连接到移动终端 100 . [0070] 输入单元 168 可插入并保持在移动终端中 100 ,而在使用时,输入单元 168 可从移动终端抽出或分离 100 . 脱离/附着识别开关 169 对应于输入单元的安装和拆卸进行操作 168 可以设置在移动终端的区域内 100 输入单元 168 被插入。 分离/附着识别开关 169 可以输出与输入单元的连接/分离相对应的信号 168 到控制器 110 . 分离/附着识别开关 169 可配置为直接或间接接触输入单元 168 当输入单元169 附在手机端 100 . 因此,分离/附着识别开关 169 产生一个信号(即,用于通知输入单元的连接或分离的信号 168 ) 对应于输入单元的连接或分离 168 基于是否分离/附着识别开关 169 接触输入单元 168 , 并将信号输出到控制器 110 . [0071] 传感器模块 170 可以包括至少一个传感器,用于检测移动终端的状态 100 . 例如,传感器模块可以包括用于检测接近移动终端的接近传感器(未示出)中的至少一个传感器 100 ,环境光传感器(未示出),用于检测移动终端周围的环境光强度 100 ,用于检测移动终端的运动(例如,旋转、加速度、振动)的运动传感器(未示出) 100 ,地磁传感器(未示出),用于检测移动终端的罗盘点 100 使用地球磁场,用于检测施加重力的方向的重力传感器(未示出),用于测量大气压力以检测高度的高度计(未示出),以及GPS模块 157 . 用于感测用户手势的相机传感器也可以包括在传感器模块中 170 . [0072] 上述传感器中的运动传感器感知移动终端的位置、运动等 100 使用加速度传感器、陀螺仪传感器、倾斜传感器或它们的组合。 然而,传感器不限于上述传感器,还可以包括能够感测移动终端的往复运动、移动方向等的其他类型的传感器。 100 . [0073] 通过运动传感器输出的感测数据(即运动信息)可以具有方向和幅度。 例如,用于感应移动终端加速度的加速度传感器 100 可以感应相对于x、y和z轴中至少一个参考轴方向的加速度,并输出加速度信息。 参考轴可以是移动终端的轴(例如,上下(z轴)、左右(x轴)和前后(y轴)方向) 100 ) 根据移动端的方向 100 ,或者可以是根据重力方向的轴(重力方向(z轴)和垂直于重力方向的方向(z和y轴))。 [0074] 传感器模块 170 还可以包括计算器(未示出),用于将感测到的角速度、速度等随时间积分以根据物体的运动计算旋转角度、方向、速度、行进距离、位置、轨迹等。 移动终端 100 ,并输出计算得到的信息。 计算器可能包含在控制器中 110 . 计算器还可以包括频率滤波器,用于阻止或通过特定频带的信号,例如检测到的加速度,以便计算轨迹等或有效地分析运动的方向。 [0075] 当传感器模块 170 包括计算器,计算器可以计算移动终端所处的方向或角度 100 移动,并将计算结果传送给控制器 100 . 但是,移动终端所处的方向或角度 100 移动可由控制器计算 110 . 移动终端的方向 100 移动基本上可以是上下方向或左右方向。 移动终端的方向 100 移动可以是移动终端所处的正面方向 100 被水平拉向用户或移动终端所在的后退方向 100 被水平推向用户。 移动终端的倾斜方向 100 相对于参考轴倾斜 包含在运动方向中。 当移动终端的角度 100 移动是在移动终端的方向上计算的 100在假设移动终端的当前位置是倾斜的 100 为0度,与移动终端所在方向的对角线方向 100 运动也可以包含在运动的方向中。 [0076] 根据本发明的示例性实施例,传感器模块 170 还可以包括呼吸检测传感器,用于使用用户的呼吸作为控制命令来根据用户的呼吸改变布局的配置。 呼吸检测传感器贴附在移动终端的外表面上 100 ,并通过入口检测用户的呼吸或风棕色。 呼吸检测传感器可以是根据用户的呼吸输出电信号的风速传感器。 风速传感器将根据用户的呼吸强度以恒定速率增加的输出值传输到控制器 110 . 或者,呼吸检测传感器可以是能够感测用户呼吸的温度传感器或湿度传感器,在这种情况下,温度传感器或湿度传感器可以将各种级别的输出值传递给控制器 110 根据用户的呼吸强度。 [0077] GPS模块 157 可以接收来自环绕地球轨道上的多个GPS卫星(未图示)的无线电波,并计算移动终端的位置 100 基于从 GPS 卫星到移动终端的无线电波的到达时间 100 . [0078] 存储单元 175 可以存储根据通信模块的操作输入/输出的信号或数据 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 或触摸屏 190 , 在控制器的控制下 110 . 存储单元 175 可以存储用于控制移动终端的应用程序和控制程序 100 或控制器 110 . [0079] 术语“存储单元”表示任意数据存储设备,例如存储单元 175 , 只读存储器 112 和内存 113 在控制器中 110 ,安装在移动终端中的存储卡(例如,SD卡或记忆棒) 100 ,等等。 存储单元 175 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)和固态驱动器(SSD)。 [0080] 存储单元 175 可以存储具有各种功能的应用程序,例如导航、视频通话、游戏、基于时间的警报应用程序等、用于为用户提供与应用程序相关联的图形用户界面 (GUI) 的图像、用户信息、文档、数据库 或与处理触摸输入的方法、背景图像(菜单屏幕、锁定屏幕等)或驱动移动终端所需的操作程序有关的数据 100 , 摄像头模块拍摄的图像 150 等存储单元 175 还可以存储与合成图像提供方法相关的数据。 [0081] 存储单元 175 是机器(例如,计算机)可读介质,术语“机器可读介质”可以定义为向机器提供数据以使机器能够执行特定功能的介质。 存储单元 175 可能包括非易失性介质和易失性介质。 这样的介质需要是有形的,以便传送到介质的命令可以被使用机器读取命令的物理工具检测到。 [0082] 机器可读介质包括软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、穿孔卡、纸带中的至少一种。 、RAM、可编程只读存储器(PROM)、可擦除PROM(EPROM)和FLASH-EPROM,然而,机器可读介质不限于上述设备。 [0083] 电源单元 180 可以为安装在移动终端外壳中的一个或多个电池供电 100 在控制器的控制下 110 . 一节或多节电池为移动终端供电 100. 电源单元 180 可以将从外部电源接收的电力提供给移动终端 100 通过连接到连接器的有线电缆 165 . 电源单元 180 可以将从外部电源无线接收的电力提供给移动终端 100 通过无线充电技术。 [0084] 移动终端 100 可能包括至少一个触摸屏 190 为用户提供与各种服务(例如,通话、数据传输、拍照)相对应的GUI。 [0085] 触摸屏 190 可以将与输入到用户图形界面的至少一个用户输入相对应的模拟信号输出到触摸屏控制器 195 . 触摸屏 190 可以通过用户的身体部位(例如,包括拇指的手指)或输入单元接收至少一个用户输入 168 (例如,手写笔或电子笔)。 触摸屏 190 可以接收触摸的连续移动(例如,拖动输入)。 触摸屏 190 可以将与触摸的连续移动对应的模拟信号输出到触摸屏控制器 195 . [0086] 在本说明书中,术语“触摸”不限于手指或输入单元的接触 168 到触摸屏 190 ,并且可以包括非接触式识别(例如,当用户输入设备位于识别距离(例如,1 cm)内时,用户输入设备可以在不直接接触触摸屏的情况下被检测到) 190 )。 触摸屏的识别距离 190 能否识别用户输入设备可能取决于移动终端的性能或结构 100 . 为了触摸屏 190 为了区分与用户输入设备直接接触产生的直接触摸事件和间接触摸事件(即悬停事件),触摸屏 190 可以被配置为根据直接触摸事件和悬停事件输出不同的值(例如,包括电压值和电流值的模拟值)。 [0087] 触摸屏 190 可以是电阻式触摸屏、电容式触摸屏、红外触摸屏、声波触摸屏或它们的组合。 [0088] 触摸屏 190 还可以包括至少两个触摸面板,分别用于感应手指和输入单元的触摸或接近 168 分别接收手指和输入单元的输入 168 . 至少两个触摸面板针对手指和输入单元的输入提供不同的输出值 168 到触摸屏控制器 195 , 和触摸屏控制器 195 识别从至少两个触摸面板接收到的不同输出值,以确定触摸屏是否有输入 190 是手指输入还是输入单元输入 168 . [0089] 触摸屏控制器 195 转换从触摸屏接收到的模拟信号 190 转换成数字信号,并将数字信号传输给控制器 110 . 控制器 110 可以控制触摸屏 190 使用从触摸屏控制器接收到的数字信号 195 . 例如,控制器 110 可以选择或执行显示在触摸屏上的快捷方式图标或对象 190 响应直接触摸事件或悬停事件。 触摸屏控制器 195 可以集成到控制器中 110 . [0090] 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值) 190 确定悬停间隔或距离以及用户的输入位置,将确定的距离值转换为数字信号(例如z坐标),然后将数字信号提供给控制器 110 . 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值) 190估计用户输入设备按压触摸屏的压力 190 ,将估计的压力值转换为数字信号,然后将数字信号提供给控制器 110 . [0091] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图,以及图2是根据本发明示例性实施例的移动终端的前透视图。 图3是根据本发明示例性实施例的移动终端的后透视图。 [0092] 参考图。 1-3、触摸屏 190 放置在正面的中央 101 移动终端的触摸屏 190 可以形成占据正面主要部分的大面积 101 移动终端的图。 图2示出了在触摸屏上显示主主屏幕的示例 190 . 主主屏幕是最初出现在触摸屏上的屏幕 190 当移动端 100 通电。 如果移动端 100 具有多个页面的不同主屏幕,主主屏幕可以是主屏幕中的第一个主屏幕。 主屏幕可能会显示快捷方式图标 191 - 1 , 191 - 2 , 和 191 - 3 用于执行常用应用程序,主菜单转换键 191 - 4 、当前时间、天气信息等。如果用户选择主菜单转换键 191 - 4 , 触摸屏上显示菜单画面 190 . 状态栏 192 代表移动终端的状态 100 可在触摸屏上方显示电池充电状态、接收信号强度、当前时间等 190 . [0093] 一个主页按钮 161 a, 一个菜单按钮 161 b, 和一个后退按钮 161 c 可能会显示在触摸屏的下部 190 . 主页按钮 161 a 用于在触摸屏上显示主主屏幕 190 . 例如,如果主页按钮 161 a 当触摸屏上显示除主主屏幕或菜单屏幕之外的另一个主屏幕时选择 190 , 主屏幕可能会显示在触摸屏上 190 . 如果主页按钮 161 a 在触摸屏上执行应用程序时选择 190 ,主屏幕如图所示。 2 可在触摸屏上显示 190 . 主页按钮 161 a 可用于在触摸屏上显示最近使用的应用程序 190 或在触摸屏上显示任务管理器 190 . [0094] 菜单按钮 161 b 提供可在触摸屏上显示的链接菜单 190 . 链接菜单可以包括小部件添加菜单、锁屏改变菜单、搜索菜单、编辑菜单、设置菜单等。 [0095] 后退按钮 161 c 可用于显示恰好在当前正在执行的屏幕之前执行的屏幕或终止最近使用的应用程序。 [0096] 第一台相机 151 , 环境光传感器 170 a, 和接近传感器 170 b 可以设置在移动终端正面的一个边缘部分 100 . 第二台相机 152 , 闪光 153 , 和扬声器 163 可以设置在背面 103 移动终端的 100 . [0097] 在移动终端的侧面 102 ,例如,电源/锁定按钮 161 d, 音量按钮 161 e 包括一个音量增大按钮 161 f 和一个音量减小按钮 161 g, 地面DMB天线 141 a 用于接收广播,一个或多个麦克风 162 等。 DMB 天线 141 a 可以固定或可拆卸地附在移动终端上 100 . [0098] 连接器 165 形成在移动终端下端的侧面 10 . 连接器 165包括多个电极,并且可以通过线路连接到外部设备。 耳机连接插孔 167 可以形成在移动终端上端的侧面 100 . 耳机可插入耳机连接插孔 167 . [0099] 输入单元 168 可安装在移动终端下端的侧面 100 . 输入单元 168 可插入移动终端内部 100 并存储在移动终端中 100 ,而在使用时,输入单元 168 与移动端分离 100 . [0100] 随着用户在移动终端上以各种形式显示多个视觉对象的愿望的增加 100 通过上述结构,例如,在相册应用的情况下,用户可以通过轻弹或拖拽手势在将图片排列在布局的预定区域上的屏幕上翻页的同时查看许多图片。 触摸屏 190 . [0101] 然而,为了让用户改变图片的排列和显示图片的区域,用户必须在编辑屏幕上编辑层,这可能需要很长时间。 此外,用户倾向于将关联图片收集到特定文件夹中,以便轻松快速地找到想要的图片或关联图片。 [0102] 因此,根据本发明的示例性实施例,提供了一种用于在触摸屏上容易且快速地改变由显示视觉对象的区域组成的布局的方法和设备 190 ,根据移动终端的动作 100 当用户选择特定对象时,提供一种布局,在该布局中,考虑到所选对象的属性,显示与所选对象相关联的对象。 [0103] 如图。 图4是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 [0104] 参考图。 参照图4,将参照图1和图4所示的示例来描述改变构成布局的区域的方法。 然而,在图5A至8B中,该方法不限于图5A至图8B中所示的示例。 5A到8B。 此外,根据本发明的示例性实施例,例如,当执行故事专辑应用程序时,将作为示例描述显示划分为预定数量的区域的布局并改变布局的组件的方法。 然而,对于本领域普通技术人员来说显而易见的是,根据移动终端的运动改变布局的组件的方法可以应用于各种显示屏幕。 [0105] 在步骤 400 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 . 在本说明书中,配置布局的“区域”也可以称为“网格”、“部分”等。 [0106] 图 图5A到8B示出了根据本发明示例性实施例的用于解释构成布局的区域根据移动终端的往复运动的方向改变的处理的示例。 [0107] 参考图。 参见图 5A-8B, 图5A示出了在触摸屏上显示对象的显示屏的示例 190 布局由区域 A、B、C 和 D 组成。可在各个区域上显示的对象可能包括图片、插图、字母(字体、类型)、字符等组件,还包括各种 视觉对象,例如各种内容(例如,文本)、用于执行应用程序的快捷图标、小部件、表示具有各种文件格式的文档的图标、文件夹等。对象还可以包括从视觉对象中选择的一些视觉对象。 [0108] 当显示画面如图所示。 如图5A所示,用户可以通过摇动移动终端来改变布局区域的排列 100 与移动终端 100 在用户手中。 在步骤 405 , 控制器110 判断移动终端是否往复运动 100 通过传感器模块检测到 170 . 如果移动终端的往复运动 100 检测到,然后在步骤中确定检测到的往复运动的方向 410 . 控制器 110 判断移动终端往复运动的方向是否 100 基于通过传感器模块收集的传感器信号对应于上下方向、左右方向和对角方向中的哪个方向 170 . 在步骤 415 , 控制器 110 根据确定的往复运动方向改变构成布局的区域,并在步 420 , 控制器 110 显示使用更改区域重新配置的布局。 [0109] 如图。 图5B示出了当用户摇动移动终端时的示例 100 在左右方向 500 , 左右方向对齐的区域排列 500 根据本发明的示例性实施例改变。 [0110] 参考图。 5B,如果用户摇动移动终端 100 在左右方向上预定次数(例如一次或两次) 500 与移动终端 100 在用户手中时,屏幕如图所示。 显示图5A,在左右方向上对齐的区域排列 500 在布局更改的区域之间。 在图。 在图5A中,区域A、B、C和D中的区域B和C对应于可以根据左右方向上的往复运动而改变的区域 500 ,因此,在左右方向的往复运动之后 500 执行后,区域B和C的布置改变如图6所示。 5B。 显示在图1的区域B中的对象。 图5A移动到并显示在图5的区域B中。 图5B的区域C中显示的对象。 图5A移动到并显示在图5的区域C中。 5B。 [0111] 图 图6A到6B示出了当用户摇动移动终端时的示例 100 在上下方向 600 ,根据本发明的示例性实施例,沿上下方向排列的区域的排列发生变化。 [0112] 参考图。 如图 6A 和 6B 所示,如果在上下方向上往复运动 600 当显示配置有区域 A、B、C 和 D 的布局屏幕时,执行如图 10 所示。 图6A,上下方向排列的区域排列 600 如图所示的变化。 6B。 如果上下方向往复运动 600 执行,图的区域B和C。 图6A移动到图6的上部区域。 在图6B中,区域D对应于图6的下部区域。 图6A移动到图6的中心区域。 图6B的区域A,图6B的区域A。 图6A移动到图6的下部区域。 6B(即,到图6B的区域A)。 下面参照图1至图3描述区域的排列规则。 10 和 11。 [0113] 图 图7A和7B示出了当用户摇动移动终端时的示例 100 在对角线方向 700 ,根据本发明的示例性实施例,沿对角线方向排列的区域的排列发生变化。 [0114] 参考图。 如图 7A 和 7B 所示,如果沿对角线方向往复运动 700 当屏幕如图 3 所示时执行。 显示图7A的区域A,显示图7A的区域A。 图7A移动到图7的区域A。 图7B的区域D和图7B的区域D。 图7A移动到图7的区域D。 7B。 [0115] 图 图8A和8B示出了当用户摇动移动终端时的示例 100 ,除触摸区域外的其余区域的排列发生变化。 如图。 图8A示出了用于说明用户摇动移动终端的情况的画面示例 100 在对角线方向 805 在保持在区域A上的触摸的同时。在这种情况下,除了图1的区域A之外的其余区域B、C和D的布置可以保持在区域A上。 保持触摸的图8A的变化如图8A所示。 8B。 [0116] 如果用户晃动移动终端 100 同时保持对用户所需区域的触摸 800,只有触摸的区域是固定的。 类似地,如果用户在两个或多个区域上保持触摸,则对应的区域也是固定的。 例如,如果用户手持移动终端 100 用双手晃动移动终端可能会让用户感到困难或不舒服 100 在一个特定的方向。 在这种情况下,可以使用用户拉/推移动终端的动作来改变布局的配置 100 朝向/反对用户、倾斜运动等。 [0117] 上述示例性实施例如图1和2所示。 图5A到7B涉及布局的配置根据用户摇动移动终端的往复运动而改变的情况 100 左右方向、上下方向、对角线方向。 然而,也可以根据其他各种动作来改变布局的配置,例如拉/推移动终端的动作 100 水平,倾斜运动,旋转运动等。 图5A到8B涉及根据预定动作改变布局配置的方法。 然而,改变布局的配置的方法不限于以上参照图1至图3描述的方法。 5A到8B。 例如,可以使用呼吸来改变布局的配置。 [0118] 图 图9A至9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的过程的示例。 [0119] 参考图。 9A-9D,如果用户在一个方向吹他/她的呼吸 900 朝向显示由区域A、B、C和D组成的布局的屏幕,如图1所示。 在图9A中,如图9A所示,显示区域A、B、C和D响应用户的呼吸而吹散的屏幕,好像这些区域是从屏幕上吹出的纸一样。 9B。 依次如图所示。 如图9C所示,显示区域A、B、C和D的布置响应于用户的呼吸而改变的屏幕,并且如图9C所示。 参照图9D,显示具有改变了区域A、B、C和D的布置的布局的屏幕。 如上所述,图。 图9A至9D涉及考虑“吹纸”的应用示例,“吹纸”是各种呼吸行为中的一种简单、直接的行为。 图9A到9D示出了显示交互图像的情况,其中响应于用户的呼吸,区域被吹散,就好像纸吹掉了一样。因此,用户可以具有控制屏幕区域的体验,就好像用户实际上是在吹掉纸一样。 . 根据本发明的示例性实施例,屏幕的内容可以根据用户呼吸的强度而变化。 [0120] 根据本发明的另一示例性实施例,构成布局的区域可以通过检测预定手势(例如,好像翻页的手势)来改变。 这种姿势可以由相机传感器、环境光传感器等检测。 图 1 和 3 中所示的示例。 如上所述,图5A到9D涉及使用动作或呼吸重新配置布局的情况,然而,当相机传感器、环境光传感器等接收到与各种行为有关的输入时,也可以重新配置布局。 [0121] 如上所述,当用户摇动移动终端时 100 或者对着移动终端的屏幕呼吸 100 ,屏幕上显示的图像会根据移动终端的动作而变化 100 或用户的呼吸,使用户无需操作按钮即可轻松快速地排列对象,感受图像的生动变化。 [0122] 可以使用如下所述的排列规则重新排列布局的组件。 [0123] 图 图10A至图10D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0124]参考图。 参照图10A-10D,根据区域大小的排列规则是将显示在较大区域上的对象移动到较小区域并且将显示在较小区域上的对象移动到较大区域的方法。 如图。 图10A示出了其中区域A具有最大尺寸并且区域B和C具有小于区域A的尺寸的屏幕。如果移动终端的往复运动 100 例如,当画面如图1所示时,检测到上下方向的往复运动。 在显示图10A时,显示在具有大尺寸的区域A中的对象移动到具有小尺寸的区域A,如图10所示。 10B 步中 1000 ,并且显示在具有小尺寸的区域C中的对象移动到具有大尺寸的区域C,如图5所示。 10B 步中 1005 . 根据排列规则,每当移动终端有动作 100 当检测到如图 3 所示的屏幕时。 在显示图10A的情况下,布局的配置按照图10的顺序改变。 参照图10B至图10。 10D。 [0125] 图 图11A至11D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0126] 参考图。 如图11A-11D所示,在水平拍摄图像和垂直拍摄图像的情况下,优选水平拍摄图像位于水平区域,而垂直拍摄图像位于垂直区域。 如图。 图11A示出了区域A是水平区域并且区域B和C是垂直区域的示例。 在这种情况下,最好是水平物体 1100 分配到区域 A 并显示在区域 A 中,垂直对象 1102 和 1105 被分配到区域B和C并显示在区域B和C中。根据本发明的示例性实施例,关于对象具有水平格式或垂直格式的每个对象的属性是对象的唯一属性并且可以被识别 提前。 因此,控制器 110 考虑到对象的属性,将每个对象定位在与对象对应的区域。 当执行智能相册应用程序时,控制器 110 可以确定必须显示的对象的数量,从页面具有不同区域排列的多个布局中选择与对象的数量和对象的属性相对应的布局,并提供选择的布局。 [0127] 如果检测到运动时出现如图所示的画面。 在显示图11A的情况下,可以显示具有改变的区域布置的布局,如图11所示。 11B。 如果一个对象显示在图 C 的区域中。 11A是垂直物体 1105 , 垂直物体 1105 可以显示虽然垂直对象 1105 移动到图1的区域C。 11B。 垂直物体 1105 可以显示在图3的区域C中。 11B虽然零件 1110 垂直物体的 1105 被截断且未显示。 [0128] 随后,如果再次检测到运动,则如图3所示的布局。 图11B改变为具有如图11所示布置的布局。 11C。 即,由于显示在图2的区域B中的对象。 11B对应垂直物体 1105 显示在图 2 的区域 B 中。 如图11A所示,对象可以移动到图11的区域B并显示在区域B上。 11C。 然而,由于对象显示在图1的区域A中。 11B对应于水平物体 1100 显示在图 1 的区域 A 中。 如图11A所示,对象不能移动到图11的区域A并显示在区域A上。 11D。 当水平物体 1100 位于图A的区域A中。 11D,零件 1115 水平物体的 1100 被切断,同时在区域A中出现空白。这种具有比预定允许的比例失配程度更大的比例失配程度的区域优选在搬迁对象时排除。 因此,图1中所示的布局。 11D 不包括在可选择以更改布局的布局中。 因此,通过考虑每个对象的属性来改变布局,可以在屏幕的区域上适当地布置诸如肖像、风景等的组件,同时保持每个组件的比例。 [0129]如图。 图12是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 在下文中,将参考图10描述根据触摸对象的属性改变在构成布局的区域中显示的对象的方法。 然而,如图12所示,该方法不限于图12所示的示例。 12. [0130] 参考图。 1和12,在步骤 1200 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 移动终端的 100 . 在步骤 1205 , 控制器 110 确定至少一个区域是否已被输入设备触摸。 如果至少触摸了一个区域,则在步骤 1210 控制器 110 判断移动终端是否往复运动 100 被检测到。 如果移动终端的往复运动 100 被检测到,然后在步骤 1215 控制器 110 搜索与属于触摸区域的对象的属性相对应的对象。 如果在步骤中确定 1205 没有接触过任何区域,或者是否在步骤中确定 1210 没有检测到往复运动,则过程返回步骤 1200 并保持布局。 [0131] 在步骤 1220 , 控制器 110 将找到的对象排列在除显示触摸对象的区域之外的其余区域中,并在步骤 1225 , 控制器 110 显示重新配置的布局,其中包含排列找到的对象的区域。 如果没有检测到往复运动,则过程返回操作 1200 ,并且布局保持不变。 [0132] 在上述本发明的示例性实施例中,步骤 1215 搜索关联对象的步骤在步骤之后执行 1210 在保持触摸的同时检测往复运动; 然而,当至少一个区域被触摸时,也可能搜索与属于该区域的对象相关联的对象。 [0133] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的属性将不同对象分别显示在构成布局的区域上的处理的示例。 [0134] 参考图。 参照图13A和13B,除了基于位置布置对象的方法之外,还可以采用根据对象的属性布置关联对象的各种方法。 这样的方法包括基于人来布置对象的方法、基于社交网络来布置对象的方法等。 [0135] 在基于人的布置对象的方法的情况下,如果用户摇动移动终端 100 同时保持对移动终端屏幕上显示的图片上特定人的触摸 100 ,则与被触摸的人相关联的图片可以被重新排列以配置当前页面的布局。 显示多人图片时,允许用户在人群中只选择一个人,如果用户摇晃移动终端 100 在保持触摸特定人的同时,可以搜索与特定人相关联的图片并在各个重新排列的区域上显示。 在基于社交网络的排列对象的方法的情况下,例如,如果选择了facebook feed功能,则可以重新排列相应的Facebook feed以适合相应页面的布局区域。 [0136] 如图。 图13A示出了由地图区域和区域A、B和C组成的布局。如果用户触摸地图区域并摇动移动终端 100 同时保持对地图区域的触摸 1300 ,可以根据对象的属性搜索与属于地图区域的对象相关联的对象,并且可以将找到的对象排列并显示在各个区域上,如图3所示。 13B。 例如,如果用户摇动移动终端 100在地图区域按住“纽约时代广场”的同时,与“纽约时代广场”相关联的对象,例如在该地点拍摄的照片、该地点的相关新闻、该地点推荐的应用项目, 等可以布置在各个区域上,如图1所示。 13B。 [0137] 图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图。 图 图15A到15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例 [0138] 参考图。 参见图14A和14B以及图14A和14B。 参照图15A-15I,图15的过程。 图14B跟随图14的过程。 14A。 为了便于理解,将参照图1至图3描述调整区域数量的方法。 图15A至15I; 然而,该方法不限于图1和图2所示的示例。 15A至15I。 [0139] 在步骤 1400 , 控制器 110 显示由触摸屏上显示对象的区域组成的布局 190 . 在步骤 1405 , 控制器 110 判断是否接收到改变区域数量的请求。 用户可以通过按下诸如音量键之类的特定键或通过位于屏幕上部的操作栏上显示的选项功能来发送改变区域数量的请求。 如果收到更改区域数量的请求,则在步骤 1410 , 控制器 110 显示用于调整区域数量的图标。 如果没有收到更改区域数量的请求,则返回步骤 1400 . 在步骤 1415 , 控制器 110 确定是否触摸了任何一个图标。 [0140] 如果在操作中确定 1415 如果没有检测到触摸输入,则过程返回操作 1410 . 如果选择了用于添加区域的图标,则在步骤 1420 图。 14B、控制器 110 确定在触摸用于添加区域的图标时是否检测到往复运动。 如果检测到往复运动,则在运行中 1425 , 控制器 110 将构成下一页布局的区域添加到构成当前页面布局的区域中,并且在步骤 1440 , 控制器 110 显示重新配置的布局以包括添加的区域。 如果在触摸区域添加图标时重复检测到往复运动,控制器 110 每当检测到往复运动时,逐步添加区域。 [0141] 图 图15A至图15I示出了用于说明根据移动终端的动作调整构成布局的区域的数量以及改变区域的布置的过程的示例 100 ,根据本发明的示例性实施例。 如果接收到调整区域数量的请求,则在如图 10 所示的屏幕。 显示图15A,区域添加图标 1510 和一个区域移除图标 1510 如图所示显示。 15B。 如果用户晃动移动终端 100 同时保持触摸区域添加图标 1510 ,添加区域D,如图3所示。 在图15C中,A、B和C区域被重新排列。 如果用户晃动移动终端 100 再次,添加区域E,如图4所示。 15D,其余区域重新排列。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 保持15D。 因此,如果构成在页面上显示的布局的区域的数量增加,则将减少总页面数量,因为要显示的对象的数量已经设置。 [0142] 如果在步骤中未触摸区域添加图标 1430 , 控制器 110 确定在区域移除图标被触摸时是否检测到往复运动。 如果在触摸区域移除图标时检测到往复运动,则在操作中 1435 控制器 110从构成当前页面布局的区域中删除一个区域,并在操作中 1440 , 控制器 110 显示用剩余区域重新配置的布局。 如果在区域移除图标时反复检测到往复运动 1500 被触摸时,每当检测到往复运动时,区域就会逐步移除。 [0143] 如果用户晃动移动终端 100 同时保持触摸区域移除图标 1500 如图所示。 在图15F中,去除了D区域,如图15F所示。 15G,A、B、C区域重新排列。 当用户摇动移动终端时 100 同时保持触摸区域移除图标 1500 ,由于已经设置了最小区域数,因此区域数可能不会改变,如图3所示。 15H。 在这种情况下,区域的排列会发生变化。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 15I 保持不变。 因此,如果减少在页面上显示的构成布局的区域的数量,则页面的总数将增加以显示预定数量的对象。 [0144] 运行中 1430 ,如果在没有触摸区域添加/删除图标时检测到往复运动,则在操作中 1445 控制器 110 根据往复运动方向的方向改变构成布局的区域,如图1和2所示。 5至7,并在运行 1450 , 控制器 110 显示使用更改区域重新配置的布局。 [0145] 上述示例是使用图标增加或减少页面上显示的区域数量的情况; 然而,也可以采用其他方法,例如使用音量增大/减小键添加或删除区域的方法。 例如,一个区域可能是如果用户摇动移动终端 100 如果用户摇动移动终端,同时按住音量增大键并移除区域 100 按住音量减小键的同时。 [0146] 如图。 图16是用于说明在移动终端中调整构成布局的区域数的方法的流程图 100 ,根据本发明的示例性实施例。 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0147] 参考图。 16 和 17 一个- 17 C、自步骤 1600 和 1605 步骤相同 400 和 405 图。 在图4中,将省略其详细描述。 运行中 1610 ,确定往复运动的次数是否等于或大于预定次数。 如果往复运动的次数等于或大于预定次数,则在步骤 1615 包括在下一页的布局中的预定数量的区域被添加到构成当前页面的布局的区域中。 运行中 1620 , 控制器 110 显示重新配置的布局以包括添加的区域。 可以根据往复运动的次数确定添加的区域的数量。 [0148] 如图。 图17A示出了当前页面的布局由区域A、B、C和D构成的情况,而图17A示出了当前页面的布局配置有区域A、B、C和D的情况。 图17B示出了下一页面的布局由区域E、F、G、H和I配置的情况。当前页面是显示在触摸屏上的页面 190 , 下一页是轻弹或拖动触摸屏手势时将显示的页面 190从用户接收。 因此,如果在当前页面如图1所示时检测到一个或多个往复运动。 如图17A所示,下一页的区域E和F如图17所示。 如图17B所示,根据往复运动的次数将图17B的区域添加到当前页面的区域。 如图17C所示,同时,区域A、B和C根据往复运动的方向重新排列。 这些区域可以一个一个地添加,也可以以预定数量为单位添加。 当区域被添加到当前页面时,在下一页的区域E和F上显示的对象如图4所示。 如图17B所示,图17B移动到区域E和F并显示在区域E和F上。 17C。 [0149] 如上所述,根据本发明的示例性实施例,用户可以使用移动终端的动作以他/她的期望模式直观地布置布局的组件(即,区域/对象) 100 . 因此,根据本发明的示例性实施例,用户可以根据移动终端的动作容易且快速地将显示在移动终端的屏幕上的多个对象的排列改变为用户期望的图案。 此外,由于可以通过移动终端的简单动作的输入来改变布置对象的布局的配置,所以可以最大化用户的便利性。 [0150] 此外,由于可以通过考虑对象的属性来配置布局来提供由期望的对象组成的布局,因此可以提供具有统一顺序的个性化布局。 [0151] 本发明的示例性实施例可以以硬件、软件或硬件和软件的组合的形式来实现。 软件可以存储在易失性或非易失性存储设备中,例如 ROM,不管它是可擦除的还是可重写的,存储在诸如 RAM、存储芯片、 和集成电路 (IC),或在光/磁可记录和机器可读的存储介质中,例如压缩盘 (CD)、数字多功能盘 (DVD)、磁盘和磁带 . 可以包括在移动终端中的存储器是适用于存储一个或多个程序的非暂时性机器可读存储介质的示例,包括实现本发明示例性实施例的指令。 因此,本发明的示例性实施例包括包括用于实现如说明书的所附权利要求中所述的设备和方法的代码的程序,以及存储这些程序的机器可读存储介质。 [0152] 此外,移动终端可以从以有线/无线方式连接的程序提供装置接收和存储程序。 程序提供装置可以包括:存储器,用于存储程序,该程序包括用于执行根据移动终端的动作控制多个对象的显示的方法的指令;通信单元,用于与移动终端进行有线/无线通信; 控制器,用于根据移动终端的请求或自动向移动终端发送程序。 [0153] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20140245234A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), AU2014219558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), AU2014219558B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), BR112015020243A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), BR112015020243B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), CN104007892A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), CN104007892B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), CN110333758A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), EP2770424A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), EP2770424A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:48.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), EP2770424B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), EP3696653A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), EP3696653B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), IN2703MUMNP2015A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), IN407024B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), JP2016511471A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), JP2019083048A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), JP6816858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), KR1020140105344A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), KR102146244B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), MX2015010598A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.107 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), MX353242B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), RU2015140072A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.127 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), RU2667496C2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), US10775896B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.148 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), US20140245234A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), US20190121443A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), VN10030622B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.172 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), VN44787A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), WO2014129862A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), ZA201505799A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270670(Integer), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.220 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.220 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20140245234A1(String), US20140245234A1(String), 1409155200(Integer), 270670(Integer), 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184990(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184990(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184990(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184990(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8898492B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.295 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.295 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.295 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: System, method and mobile terminal for sharing battery between mobile terminals(String), 移动终端间共享电池的系统、方法及移动终端(String), US8898492B2(String), A system, a method, and a mobile terminal for sharing a battery between mobile terminals are disclosed, which can solve a problem that the battery can not be shared between mobile terminals in the prior art. In accordance with the present invention, a mobile terminal having power supplying ability is able to supply power to a mobile terminal lacking power by an external power supply line, power control circuits of the power supply end and the power utilization end are controlled, the power utilization end is able to detect an electricity quantity of the power supply end, and the sharing of a battery between two mobile terminals can be achieved, thereby greatly increasing utilization modes of the battery without external charging power supply so as to facilitate the using of a user.(String), 本发明公开了一种移动终端间共享电池的系统、方法及移动终端,能够解决现有技术中移动终端间无法共享电池的问题。 根据本发明,具有供电能力的移动终端能够通过外接电源线向缺电的移动终端供电,控制供电端和用电端的电源控制电路,电源 利用端能够检测供电端的电量,可以实现两个移动终端共享电池,大大增加了电池在无需外接充电电源的情况下的使用方式,方便使用 用户。(String), US13/517866(String), 1339603200(Integer), US8898492B2(String), 1416844800(Integer), 1416844800(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 12(Integer), US20030030412A1 | US20050174710A1 | US20060017839A1 | US20080054855A1 | US20080074077A1 | US20080116854A1 | US20090167245A1 | US20090200989A1 | US20090267571A1 | US20100045243A1 | US20100109602A1 | US7508162B2(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184991(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c6fa5ca2e2fe429ba61ab19984135d01.png(String), 184991(Integer), c6fa5ca2e2fe429ba61ab19984135d01.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System, method and mobile terminal for sharing battery between mobile terminals(String), 移动终端间共享电池的系统、方法及移动终端(String), US8898492B2(String), A system, a method, and a mobile terminal for sharing a battery between mobile terminals are disclosed, which can solve a problem that the battery can not be shared between mobile terminals in the prior art. In accordance with the present invention, a mobile terminal having power supplying ability is able to supply power to a mobile terminal lacking power by an external power supply line, power control circuits of the power supply end and the power utilization end are controlled, the power utilization end is able to detect an electricity quantity of the power supply end, and the sharing of a battery between two mobile terminals can be achieved, thereby greatly increasing utilization modes of the battery without external charging power supply so as to facilitate the using of a user.(String), 本发明公开了一种移动终端间共享电池的系统、方法及移动终端,能够解决现有技术中移动终端间无法共享电池的问题。 根据本发明,具有供电能力的移动终端能够通过外接电源线向缺电的移动终端供电,控制供电端和用电端的电源控制电路,电源 利用端能够检测供电端的电量,可以实现两个移动终端共享电池,大大增加了电池在无需外接充电电源的情况下的使用方式,方便使用 用户。(String), US13/517866(String), 1339603200(Integer), US8898492B2(String), 1416844800(Integer), 1416844800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 12(Integer), US20030030412A1 | US20050174710A1 | US20060017839A1 | US20080054855A1 | US20080074077A1 | US20080116854A1 | US20090167245A1 | US20090200989A1 | US20090267571A1 | US20100045243A1 | US20100109602A1 | US7508162B2(String), \20230420\c6fa5ca2e2fe429ba61ab19984135d01.png(String), 6(Integer), 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184991(Integer), 1. A system for sharing a battery between mobile terminals, comprising a mobile terminal of a power supply end and a mobile terminal of a power utilization end, wherein,the mobile terminal of the power supply end comprises a battery of the power supply end, a circuit interface of the power supply end and a power supply control unit of the power supply end, wherein the power supply control unit of the power supply end is coupled with the battery of the power supply end and the circuit interface of the power supply end respectively;the mobile terminal of the power utilization end comprises a battery of the power utilization end, a circuit interface of the power utilization end, a power supply control unit of the power utilization end and a power management unit, wherein the power management unit is coupled with the battery of the power utilization end and comprises a power supply switch subunit;wherein the circuit interface of the power utilization end is coupled with the circuit interface of the power supply end; the power supply control unit of the power supply end is configured to control the battery of the power supply end to supply power to the mobile terminal of the power utilization end through the circuit interface of the power supply end;the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; and the power supply control unit of the power utilization end is configured to supply power to the mobile terminal of the power utilization end;wherein the power management unit further comprises: a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series, and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal of the power utilization end further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein,the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end;the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the mobile terminal of the power supply end charges the battery of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; andthe electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of the battery of the power supply end.(String), 1、一种移动终端共享电池的系统,包括一种供电端移动终端和用电端移动终端,其中,供电端移动终端包括供电端电池、供电端电路接口和供电端供电控制单元,供电端供电控制单元耦接分别带有供电端的电池和供电端的电路接口;用电端移动终端包括用电端电池、用电端电路接口、用电端供电控制单元和电源管理单元,其中,电源管理单元耦接于电源利用端的电池,包括电源切换子单元;其中,用电端的电路接口与供电端的电路接口耦合;供电端供电控制单元用于控制供电端电池通过供电端电路接口为用电端移动终端供电。电源开关子单元,分别与用电端电路接口、用电端电池和用电端电源控制单元耦合,用于控制用电端电路接口或用电端电池与用电端电源控制单元耦合;用电端供电控制单元,用于为用电端移动终端供电;其中,电源管理单元还包括:依次串联耦合在用电端的电路接口与供电开关子单元之间的充电供电模式控制子单元和电量检测开关子单元,以及耦合的电量检测子单元。带电量检测开关子单元;用电端移动终端还包括与用电端电池耦合的用电端充电控制单元。其中,用电端充电控制单元,用于对用电端电池进行充电控制;充电供电模式控制子单元,与用电端充电控制单元耦合,用于控制供电端移动终端在供电端移动终端充电时是否对用电端电池进行充电。端为用电端的移动终端供电;和电量检测开关子单元,用于控制电量检测子单元检测用电端电池电量或供电端电池电量。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184991(Integer), 2. The system for sharing a battery between mobile terminals according to claim 1, wherein the mobile terminal of the power supply end further comprises:a charging control unit of the power supply end, coupled with the battery of the power supply end, configured to perform charging control to the battery of the power supply end; anda power supply interface control unit, coupled between the circuit interface of the power supply end and the power supply control unit of the power supply end in series and coupled with the charging control unit of the power supply end, configured to control the circuit interface of the power supply end to couple with the charging control unit of the power supply end or the power supply control unit of the power supply end.(String), 2.根据权利要求1所述的移动终端电池共享系统,其中供电端移动终端还包括:供电端充电控制单元,与供电端电池耦合,用于对供电端电池进行充电控制;和供电接口控制单元,串联耦合在供电端的电路接口与供电端的供电控制单元之间,并与供电端的充电控制单元耦合,用于控制供电端的电路接口供电端耦接供电端的充电控制单元或供电端的供电控制单元。3、一种移动终端共享电池的方法,包括步骤:供电端移动终端通过用电端电路接口向用电端移动终端供电;和用电端移动终端在用电端移动终端中开启用电端电池的供电电路,同时关闭用电端电路接口的供电电路,从而实现供电端移动终端向用电端移动终端供电;其中,用电端充电控制单元对用电端电池进行充电控制;充电及供电方式控制子单元,控制供电端移动终端向用电端移动终端供电时,供电端移动终端是否对用电端电池进行充电;和电量检测开关子单元控制电量检测子单元检测供电端电池的电量。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184991(Integer), 3. A method for sharing a battery between mobile terminals, comprising the steps of:a mobile terminal of a power supply end supplying power to a mobile terminal of a power utilization end through a circuit interface of the power utilization end; andthe mobile terminal of the power utilization end opening a power supply circuit of the battery of the power utilization end in the mobile terminal of the power utilization end and closing a power supply circuit of the circuit interface of the power utilization end at the same time, thus enabling the mobile terminal of the power supply end to supply power to the mobile terminal of the power utilization end;wherein a charging control unit of the power utilization end performing charging control to the battery of the power utilization end;a charging and power supply mode control subunit controlling whether the mobile terminal of the power supply end charges the battery of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; andan electricity quantity detection switch subunit controlling an electricity quantity detection subunit to detect an electricity quantity of the battery of the power supply end.(String), 4.根据权利要求3所述的移动终端电池共享方法,其中在供电端移动终端向用电端移动终端供电之前,该方法还包括以下步骤:用电端移动终端判断是否对用电端移动终端中的用电端电池进行充电,如果是,将用电端电路接口与充电电路耦合;如果否,断开用电端电路接口与充电电路的耦合。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184991(Integer), 4. The method for sharing a battery between mobile terminals according to claim 3, wherein before the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of:the mobile terminal of the power utilization end determining whether to charge the battery of the power utilization end in the mobile terminal of the power utilization end, if yes, coupling the circuit interface of the power utilization end with a charging circuit; if no, breaking a coupling between the circuit interface of the power utilization end and the charging circuit.(String), 5.根据权利要求3所述的移动终端共享电池的方法,其中在供电端移动终端向用电端移动终端供电过程中,该方法还包括以下步骤:用电端移动终端检测并显示供电端移动终端的供电端电池电量。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184991(Integer), 5. The method for sharing a battery between mobile terminals according to claim 3, wherein during the procedure that the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of:the mobile terminal of the power utilization end detecting and displaying an electricity quantity of the battery of the power supply end of the mobile terminal of the power supply end.(String), 6.移动终端,包括用电端电池、与用电端电池耦合的电源管理单元,其中电源管理单元包括电源开关子单元,移动终端还包括用电端电路接口和用电端供电控制单元;其中,电源利用端的电路接口,用于连接外部供电设备;电源开关子单元,分别与用电端电路接口、用电端电池和用电端电源控制单元耦合,用于控制用电端电路接口或用电端电池与用电端电源控制单元耦合;和用电端供电控制单元,用于为移动终端供电;其中,所述电源管理单元还包括依次串联耦合在用电端电路接口与供电开关子单元之间的充电供电模式控制子单元和电量检测开关子单元,以及与所述电源耦合的电量检测子单元。电量检测开关子单元;移动终端还包括与用电端电池耦合的用电端充电控制单元。其中,用电端充电控制单元,用于对用电端电池进行充电控制;充电供电方式控制子单元,与用电端充电控制单元耦合,用于在外部供电设备为移动设备供电时,控制外部供电设备是否对用电端电池进行充电。用电端终端;和电量检测开关子单元,用于控制电量检测子单元检测用电端电池电量或外部供电设备电池电量。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184991(Integer), 6. A mobile terminal, comprising a battery of a power utilization end, a power management unit coupled with the battery of the power utilization end, wherein the power management unit comprises a power supply switch subunit, and the mobile terminal further comprises a circuit interface of the power utilization end and a power supply control unit of the power utilization end; wherein,the circuit interface of the power utilization end is configured to couple with an external power supply device;the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; andthe power supply control unit of the power utilization end is configured to supply power to the mobile terminal;wherein the power management unit further comprises a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein,the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end;the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the external power supply device charges the battery of the power utilization end when the external power supply device supplies power to the mobile terminal of the power utilization end; andthe electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of a battery of the external power supply device.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184991(Integer), [0001]This is a continuation of International Application PCT/CN2010/073703, with an International Filing Date of Jun. 9, 2010, which claims priority to Chinese Application No. 200910260372.7, filed Dec. 17, 2009, each of which is incorporated by reference. FIELD OF THE INVENTION [0002]The present invention relates to the technical field of mobile terminal devices, and in particular to a system, a method and a mobile terminal for sharing a battery between mobile terminals. BACKGROUND OF THE INVENTION [0003]As a portable device, a mobile terminal is more frequently used than other portable devices and has become the most frequently used portable device of a user and a main carrier for the communication, information management and entertainment of the user. Due to the characteristics of a portable device, the mobile terminal, whose power supply is realized by means of a built-in battery, usually does not use an external power supply to supply power after being charged. Therefore, the continuous using time of the mobile terminal is completely determined by the electricity quantity of the battery in the device. With respect to a portable device, the using time of the battery is an important technical reference index. [0004]Currently, the power supply of the mobile terminal is basically based on the built-in rechargeable battery in the mobile terminal. Even for mobile terminals of the same type, their batteries are used independently. When one mobile terminal runs out of power, it is only possible to take out the battery of another mobile terminal and then replace the battery of the mobile terminal, which runs out of power, with the battery of the another mobile terminal, however, the another mobile terminal can not be used at the same time, causing inconvenience to the users. Therefore, in a working environment without charging fittings and with special requirements, the user desires to use the mobile terminals simultaneously when a mobile terminal runs out of power. SUMMARY OF THE INVENTION [0005]The present invention provides a system, a method and a mobile terminal for sharing a battery between mobile terminals, so as to address the problem that the battery can not be shared between mobile terminals in the prior art. [0006]To solve the technical problem above, in one aspect, a system for sharing a battery between mobile terminals is provided, which comprises a mobile terminal of a power supply end and a mobile terminal of a power utilization end; wherein, [0007]the mobile terminal of the power supply end comprises a battery of the power supply end, a circuit interface of the power supply end and a power supply control unit of the power supply end, wherein the power supply control unit of the power supply end is coupled with the battery of the power supply end and the circuit interface of the power supply end respectively; [0008]the mobile terminal of the power utilization end comprises a battery of the power utilization end, a circuit interface of the power utilization end, a power supply control unit of the power utilization end and a power management unit of the power utilization end, wherein the power management unit is coupled with the battery of the power utilization end and comprises a power supply switch subunit; [0009]wherein the circuit interface of the power utilization end is coupled with the circuit interface of the power supply end; the power supply control unit of the power supply end is configured to control the battery of the power supply end to supply power to the mobile terminal of the power utilization end through the circuit interface of the power supply end; [0010]the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; and the power supply control unit of the power utilization end is configured to supply power to the mobile terminal of the power utilization end. [0011]Preferably, the mobile terminal of the power supply end further comprises: [0012]a charging control unit of the power supply end, coupled with the battery of the power supply end, configured to perform charging control to the battery of the power supply end; and [0013]a power supply interface control unit, coupled between the circuit interface of the power supply end and the power supply control unit of the power supply end in series and coupled with the charging control unit of the power supply end, configured to control the circuit interface of the power supply end to couple with the charging control unit of the power supply end or the power supply control unit of the power supply end. [0014]Preferably, the power management unit further comprises: a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series, and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal of the power utilization end further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein, [0015]the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end; [0016]the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the mobile terminal of the power supply end charges the battery of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; and [0017]the electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of the battery of the power supply end. [0018]In another aspect, a method for sharing a battery between mobile terminals is provided, comprising: [0019]a mobile terminal of a power supply end supplying power to a mobile terminal of a power utilization end through a circuit interface of the power utilization end; and [0020]the mobile terminal of the power utilization end opening a power supply circuit of the battery of the power utilization end and closing a power supply circuit of the circuit interface of the power utilization end at the same time, thus enabling the mobile terminal of the power supply end to supply power to the mobile terminal of the power utilization end. [0021]Preferably, before the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of: [0022]the mobile terminal of the power utilization end determining whether to charge the battery of the power utilization end in the mobile terminal of the power utilization end, if yes, coupling the circuit interface of the power utilization end with a charging circuit; if no, breaking a coupling between the circuit interface of the power utilization end and the charging circuit. [0023]Preferably, during the procedure that the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of: [0024]the mobile terminal of the power utilization end detecting and displaying an electricity quantity of the battery of the power supply end of the mobile terminal of the power supply end. [0025]In another aspect, a mobile terminal is provided, the mobile terminal comprises a battery of a power supply end, and the mobile terminal further comprises: [0026]a circuit interface of the power supply end; and [0027]a power supply control unit of the power supply end, coupled with the battery of the power supply end and the circuit interface of the power supply end respectively, configured to control the battery of the power supply end to supply power externally through the circuit interface of the power supply end. [0028]Preferably, the mobile terminal further comprises: [0029]a charging control unit of the power supply end, coupled with the battery of the power supply end, configured to perform charging control to the battery of the power supply end; and [0030]a power supply interface control unit, coupled between the circuit interface of the power supply end and the power supply control unit of the power supply end in series, and coupled with the charging control unit of the power supply end, configured to control the circuit interface of the power supply end to couple with the charging control unit of the power supply end or the power supply control unit of the power supply end. [0031]In another aspect, a mobile terminal is provided, comprising a battery of a power utilization end and a power management unit which is coupled with the battery of the power utilization end and comprises a power supply switch subunit, the mobile terminal further comprises a circuit interface of the power utilization end and a power supply control unit of the power utilization end; wherein, [0032]the circuit interface of the power utilization end is configured to couple with an external power supply device; [0033]the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; and [0034]the power supply control unit of the power utilization end is configured to supply power to the mobile terminal. [0035]Preferably, the power management unit further comprises a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series, and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein, [0036]the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end; [0037]the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the external power supply device charges the battery of the power utilization end when the external power supply device supplies power to the mobile terminal of the power utilization end; and [0038]the electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of a battery of the external power supply device. [0039]In accordance with the present invention, a mobile terminal having power supplying ability is able to supply power to a mobile terminal lacking power by an external power supply line, power control circuits of the power supply end and the power utilization end are controlled, the power utilization end is able to detect an electricity quantity of the power supply end, and the sharing of a battery between two mobile terminals can be achieved, thereby greatly increasing utilization modes of the battery without external charging power supply so as to facilitate the utilization of a user. BRIEF DESCRIPTION OF THE DRAWINGS [0040]FIG. 1 is a schematic diagram of the structure of a mobile terminal of a power supply end in accordance with an embodiment of the present invention; [0041]FIG. 2 is a schematic diagram of the structure of a mobile terminal of a power utilization end in accordance with an embodiment of the present invention; [0042]FIG. 3 is a schematic diagram of the structure of another mobile terminal of a power supply end in accordance with an embodiment of the present invention; [0043]FIG. 4 is a schematic diagram of the structure of another mobile terminal of power utilization end in accordance with an embodiment of the present invention; [0044]FIG. 5 is a flowchart of a method for sharing a battery between mobile terminals in accordance with an embodiment of the present invention; [0045]FIG. 6 is a flowchart when a mobile terminal of a power supply end supplies power externally in accordance with an embodiment of the present invention; and [0046]FIG. 7 is a flowchart when a mobile terminal of a power utilization end receives power from external in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0047]To solve the problem that the battery can not be shared between mobile terminals in the prior art, a system, a method and a mobile terminal for sharing a battery between mobile terminals are provided in the present invention, which will be detailed hereinafter in conjunction with the accompanying figures and the embodiments. It shall be understood that the embodiments described herein are only to illustrate the present invention, rather than limit it. [0048]As shown in FIGS. 1 and 2, Embodiment 1 of the present invention relates to a system for sharing a battery between mobile terminals, comprising a mobile terminal of a power supply end and a mobile terminal of a power utilization end. The structure of the mobile terminal of the power supply end is as shown in FIG. 1, comprising a battery 103 of the power supply end, a circuit interface 101 of the power supply end and a power supply control unit 102 of the power supply end, wherein the power supply control unit 102 of the power supply end is coupled with the battery 103 of the power supply end and the circuit interface 101 of the power supply end respectively. The structure of the mobile terminal of the power utilization end is as shown in FIG. 2, comprising a battery 204 of the power utilization end, a circuit interface 201 of the power utilization end, a power supply control unit 203 of the power utilization end and a power management unit 202, wherein the power management unit 202 is coupled with the battery 204 of the power utilization end and comprises a power supply switch subunit 2021. [0049]The circuit interface 201 of the power utilization end is coupled with the circuit interface 101 of the power supply end; the power supply control unit 102 of the power supply end is configured to control the battery 103 of the power supply end to supply power to the mobile terminal of the power utilization end through the circuit interface 101 of the power supply end; [0050]the power supply switch subunit 2021, coupled with the circuit interface 201 of the power utilization end, the battery 204 of the power utilization end and the power supply control unit 203 of the power utilization end respectively, is configured to control the circuit interface 201 of the power utilization end or the battery 204 of the power utilization end to couple with the power supply control unit 203 of the power utilization end; and the power supply control unit 203 of the power utilization end is configured to supply power to the mobile terminal of the power utilization end. [0051]When the mobile terminal of the power supply end supplies power locally, namely when the mobile terminal of the power supply end does not enable its battery sharing function thereby not supplying power to the mobile terminal of the power utilization end, the battery 103 of the power supply end in the mobile terminal of the power supply end is coupled with the power supply control unit 102 of the power supply end, and supplies power locally through the power supply control unit 102 of the power supply end. When the mobile terminal of the power supply end enables its battery sharing function thereby supplying power to the mobile terminal of the power utilization end, the battery 103 of the power supply end, the power supply control unit 102 of the power supply end and the circuit interface 101 of the power supply end are coupled serially in sequence, at this time, the power supply control unit 102 of the power supply end realizes, on the premise of ensuring the local power supply to the mobile terminal of the power supply end, the function of supplying power to the mobile terminal of the power utilization end through the circuit interface 101 of the power supply end connected with the mobile terminal of the power utilization end. [0052]When the mobile terminal of the power utilization end supplies power through the battery 204 of the power utilization end, the power supply switch subunit 2021 of the power management unit 202 is coupled with the battery 204 of the power utilization end, thus enabling the power of the battery 204 of the power utilization end to supply power to the mobile terminal of the power utilization end locally through the power supply switch subunit 2021 and the power supply control unit 203 of the power utilization end coupled with the power supply switch subunit 2021. When the battery 204 of the power utilization end runs low or down, the circuit interface 101 of the power supply end is coupled with the circuit interface 201 of the power utilization end through a power supply line, so that the battery 103 of the power supply end in the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end. A power supply voltage no higher than a local voltage of the mobile terminal of the power supply end can be provided by controlling the output voltage of the circuit interface 101 of the power supply end through the power supply control unit 102 of the power supply end, thus supplying power to the mobile terminal of the power utilization end with a power supply voltage no higher than the above local voltage. At this time, the power supply switch subunit 2021 breaks its coupling with the battery 204 of the power utilization end and couples with the circuit interface 201 of the power utilization end, thus the power provided by the battery 103 of the power supply end is supplied to the power supply control unit 203 of the power utilization end through the circuit interface 101 of the power supply end, the circuit interface 201 of the power utilization end and the power supply switch subunit 2021. The power supply control unit 203 of the power utilization end adjusts the voltage and the electricity quantity according to parameters (such as voltage, current and electricity quantity) used by the mobile terminal of the power utilization end and finally supplies power to the mobile terminal of the power utilization end. The sharing of the battery 103 of the power supply end between the mobile terminals of the power supply end and the power utilization end is realized, and the purpose of using the two mobile terminals of the power supply end and the power utilization end simultaneously is reached. [0053]In addition, since most of the mobile terminals use rechargeable battery or require data transfer, a mobile terminal is usually provided with a charging interface or a data interface. Due to the requirements for the portability of a mobile terminal, they are limited in size and interface quantity. Moreover, considering that the charging interface or some data interfaces can be used as power supply interface, the additional use of the charging interface or data interfaces on the mobile terminal of the power supply end as the circuit interface 101 of the power supply end is designed in the embodiment. [0054]As shown in FIG. 3, on the basis of the embodiment above, the mobile terminal of the power supply end further comprises: a charging control unit 105 of the power supply end and a power supply interface control unit 104, wherein the charging control unit 105 of the power supply end is coupled with the battery 103 of the power supply end; the power supply interface control unit 104 is coupled serially between the circuit interface 101 of the power supply end and the power supply control unit 102 of the power supply end and is coupled with the charging control unit 105 of the power supply end. The charging control unit 105 of the power supply end is configured to perform charging control to the battery 103 of the power supply end; and the power supply interface control unit 104 is configured to control the circuit interface 101 of the power supply end to couple with the charging control unit 105 of the power supply end or the power supply control unit 102 of the power supply end. Namely, when the circuit interface 101 of the power supply end is used as a charging interface, the power supply interface control unit 104 controls the circuit interface 101 of the power supply end to couple with the charging control unit 105 of the power supply end, and breaks the coupling between the circuit interface 101 of the power supply end and the power supply control unit 102 of the power supply end. In this way, the battery 103 of the power supply end can be charged and can supply power locally through the power supply control unit 102 of the power supply end. [0055]When the circuit interface 101 of the power supply end is coupled with the power supply line, the user configures to enable the battery sharing function of the mobile terminal of the power supply end to supply power to the mobile terminal of the power utilization end. Namely, when the circuit interface 101 of the power supply end is used as the power supply interface, the power supply interface control unit 104 breaks the coupling between the circuit interface 101 of the power supply end and the charging control unit 105 of the power supply end, couples the circuit interface 101 of the power supply end with the power supply control unit 102 of the power supply end, reads configuration parameters such as voltage, and configures the power supply control unit 102 of the power supply end. Thus the battery 103 of the power supply end can supply power externally through the circuit interface 101 of the power supply end when simultaneously supplying power locally through the power supply control unit 102 of the power supply end. [0056]Moreover, when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, there may exist a case that the mobile terminal of the power utilization end cannot be coupled with the mobile terminal of the power supply end through the power supply line for a long period of time, so the user has the requirement of charging the mobile terminal of the power utilization end by the mobile terminal of the power supply end. In addition, when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the residual electricity quantity of the battery 103 of the power supply end is critical to the mobile terminal of the power supply end and the mobile terminal of the power utilization end, so it is necessary to detect the residual electricity quantity of the battery 103 of the power supply end, so as to remind the user to conduct corresponding operation. In view of the above, the mobile terminal of the power utilization end is further designed in the embodiment of the present invention. [0057]As shown in FIG. 4, on the basis of the embodiment above, the mobile terminal of the power utilization end also comprises a charging control unit 205 of the power utilization end coupled with the battery 204 of the power utilization end; the power management unit 202 also comprises a charging and power supply mode control subunit 2022, an electricity quantity detection switch subunit 2023 and an electricity quantity detection subunit 2024, wherein the charging and power supply mode control subunit 2022 and the electricity quantity detection switch subunit 2023 are coupled serially between the circuit interface 201 of the power utilization end and the power supply switch subunit 2021 in sequence, and the electricity quantity detection subunit 2024 is coupled with the electricity quantity detection switch subunit 2023. The charging control unit 205 of the power utilization end is configured to perform charging control to the battery 204 of the power utilization end; the charging and power supply mode control subunit 2022 is coupled with the charging control unit 204 of the power utilization end and is configured to control whether the mobile terminal of the power supply end charges the battery 204 of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; and the electricity quantity detection switch subunit 2023 is configured to control the electricity quantity detection subunit 2024 to detect the electricity quantity of the battery 103 of the power supply end or the electricity quantity of the battery 204 of the power utilization end. [0058]After the circuit interface 201 of the power utilization end in the mobile terminal of the power utilization end is coupled with the power supply line, firstly, the mobile terminal of the power utilization end determines whether to charge the battery 204 of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, if the answer is yes, the charging and power supply mode control subunit 2022 controls the circuit interface 201 of the power utilization end to couple with the charging control unit 205 of the power utilization end so as to charge the battery 204 of the power utilization end through the charging control unit 205 of the power utilization end, and simultaneously keeps the coupling between the circuit interface 201 of the power utilization end and the power supply switch subunit 2021 so as to supply power to the mobile terminal of the power utilization end; if the answer is no, the charging and power supply mode control subunit 2022 breaks the coupling between the circuit interface 201 of the power utilization end and the charging control unit 205 of the power utilization end, and only keeps the coupling between the circuit interface 201 of the power utilization end and the power supply switch subunit 2021 so as to supply power to the mobile terminal of the power utilization end. [0059]When the mobile terminal of the power utilization end is supplied with power through the battery 204 of the power utilization end, the electricity quantity detection switch subunit 2023 controls the electricity quantity detection subunit 2024 to detect an end voltage of the battery 204 of the power utilization end and a voltage attenuation, estimate a capacity of the battery 103 of the power supply end, write the estimated capacity in a PMU status register for the access of an UI (User Interface), and display the current electricity quantity. During the procedure that the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the electricity quantity detection switch subunit 2023 controls the electricity quantity detection subunit 2024 to detect the end voltage of the battery 103 of the power supply end and the voltage attenuation, estimate the capacity of the battery 103 of the power supply end, write the estimated capacity in the PMU status register for the access of the UI, and display the current electricity quantity. [0060]It can be seen from the embodiment above that, through supplying power to the mobile terminal of the power utilization end by the mobile terminal of the power supply end, the embodiment of the present invention achieves sharing the battery of the power supply end between the mobile terminals of the power supply end and the power utilization end, reduces the hardware added by the additional use of the interfaces, simplifies the structure and realizes the function of charging to the battery of the power utilization end, thus facilitating using of a user. [0061]As shown in FIG. 5, Embodiment 2 of the present invention relates to a method for sharing a battery between mobile terminals, comprising the steps as follows. [0062]S301, a mobile terminal of a power supply end supplies power to a mobile terminal of a power utilization end through a circuit interface of the power utilization end. [0063]As shown in FIG. 6, if a charging interface of the mobile terminal of the power supply end is additionally used as the circuit interface of the power supply end in the mobile terminal of the power supply end, the step above comprises the steps as follows. [0064]S3011, after the mobile terminal of the power supply end is coupled with the mobile terminal of the power utilization end through a power supply line, a power supply mode is enabled. [0065]S3012, since the circuit interface of the power supply end is used as a charging interface when the mobile terminal of the power supply end does not supply power externally, the circuit interface of the power supply end is coupled with a charging circuit, namely the circuit interface of the power supply end is coupled with the charging control unit of the power supply end so as to charge the battery of the power supply end through the charging control unit of the power supply end. When the mobile terminal of the power supply end supplies power externally, the circuit interface of the power supply end is not used as a charging interface any more, thus it is required to break the coupling between the circuit interface of the power supply end and the charging circuit. [0066]S3013, since a rated operational voltage in normal operation may vary with different mobile terminals, it is required to determine whether to configure a voltage reduction parameter before supplying power to the mobile terminal of the power utilization end, if the answer is yes, turn to S3014, otherwise, turn to S3015. [0067]S3014, the voltage reduction parameter is configured according to parameters such as rated operational voltage and rated operational current of the mobile terminal of the power utilization end, and then turn to S3016. [0068]S3015, the current voltage parameter of the battery of the power supply end is used, and turn to S3016. [0069]S3016, the circuit interface of the power supply end is coupled with a discharge circuit of the battery of the power supply end, namely the circuit interface of the power supply end is coupled with the battery of the power supply end through the power supply control unit of the power supply end. [0070]S3017, the power supply control unit of the power supply end supplies power, through the circuit interface of the power supply end, to the mobile terminal of the power utilization end connected with it when locally supplying power to the mobile terminal of the power supply end at the same time. [0071]S302, the mobile terminal of the power utilization end opens a power supply circuit of the battery of the power utilization end and closes a power supply circuit of the circuit interface of the power utilization end. [0072]As shown in FIG. 7, in the case that the mobile terminal of the power supply end is also required to charge the battery of the power utilization end when supplying power to the mobile terminal of the power utilization end, S302 specifically comprises the steps as follows. [0073]S3021, power supply of the mobile terminal of the power supply end enters to supply power to the mobile terminal of the power utilization end. [0074]S3022, firstly, it is determined whether it is required to charge the battery of the power utilization end in the mobile terminal of power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, if it is required to do so, keep the coupling between the circuit interface of the power utilization end and the charging circuit, namely keep the coupling between the circuit interface of the power utilization end and the charging control unit of the power utilization end, then turn to S3024; if it is not required to do so, turn to (String), [0001] 这是国际申请 PCT/CN2010/073703 的延续,国际申请日为 2010 年 6 月 9 日,该申请要求于 2009 年 12 月 17 日提交的中国申请号 200910260372.7 的优先权,该申请均通过引用并入本文。 发明领域 [0002] 本发明涉及移动终端设备技术领域,尤其涉及一种移动终端间共享电池的系统、方法及移动终端。 背景技术 [0003] 移动终端作为便携设备,使用频率高于其他便携设备,已成为用户最频繁使用的便携设备,也是用户进行通信、信息管理和娱乐的主要载体。 由于便携设备的特性,通过内置电池实现供电的移动终端在充电后通常不使用外接电源供电。 因此,移动终端的持续使用时间完全取决于设备中电池的电量。 对于便携设备而言,电池的使用时间是一项重要的技术参考指标。 [0004] 目前,移动终端的供电基本都是基于移动终端内置的可充电电池。 即使是同类型的移动终端,其电池也是独立使用的。 当一个移动终端没电时,只能取出另一个移动终端的电池,然后用另一个移动终端的电池更换没电的移动终端的电池。 不能同时使用其他移动终端,给用户带来不便。 因此,在没有充电配件且有特殊要求的工作环境中,用户希望在移动终端没电的情况下同时使用移动终端。 发明内容 [0005] 本发明提供一种移动终端间共享电池的系统、方法及移动终端,以解决现有技术中移动终端间无法共享电池的问题。 [0006] 为解决上述技术问题,一方面,提供了一种移动终端间共享电池的系统,包括供电端移动终端和用电端移动终端。 其中, [0007] 供电端的移动终端包括供电端的电池、供电端的电路接口和供电端的供电控制单元,其中供电端的供电控制单元耦接 分别与供电端的电池和供电端的电路接口; [0008] 用电端的移动终端包括用电端的电池、用电端的电路接口、用电端的供电控制单元和用电端的电源管理单元,其中电源 管理单元与用电端的电池耦合,包括电源开关子单元; [0009] 其中,用电端的电路接口与供电端的电路接口耦接。 供电端的供电控制单元,用于控制供电端的电池通过供电端的电路接口向用电端的移动终端供电。 [0010] 电源开关子单元,分别与用电端的电路接口、用电端的电池和用电端的电源控制单元耦合,用于控制用电端的电路接口或 用电端的电池与用电端的供电控制单元耦合; 所述用电端的供电控制单元,用于为所述用电端的移动终端供电。 [0011]优选地,所述供电端的移动终端还包括: [0012] 所述供电端的充电控制单元,与所述供电端的电池相连,用于对所述供电端的电池进行充电控制; 和 [0013] 电源接口控制单元,串联在电源端的电路接口和电源端的电源控制单元之间,并与电源端的充电控制单元耦合,用于控制电源端的电路接口。 供电端耦接供电端的充电控制单元或供电端的供电控制单元。 [0014] 优选地,所述电源管理单元还包括:充电供电模式控制子单元和电量检测开关子单元,依次串联在所述用电端的电路接口和所述电源开关子单元之间,以及电量检测子单元。 与电量检测开关子单元连接; 所述用电端的移动终端还包括:所述用电端的充电控制单元,与所述用电端的电池相连。 其中, [0015] 用电端的充电控制单元,用于对用电端的电池进行充电控制。 [0016] 充电和供电模式控制子单元,与用电端的充电控制单元耦合,用于控制供电端的移动终端在供电端的移动终端是否对用电端的电池进行充电。 端向用电端的移动终端供电; 和 [0017] 电量检测开关子单元,用于控制电量检测子单元检测用电端电池电量或供电端电池电量。 [0018] 另一方面,提供了一种移动终端之间共享电池的方法,包括: [0019] 供电端的移动终端通过用电端的电路接口向用电端的移动终端供电; 和 [0020] 用电端的移动终端打开用电端电池的供电电路,同时关闭用电端电路接口的供电电路,从而使供电的移动终端 端向用电端的移动终端供电。 [0021] 优选地,在供电端的移动终端向用电端的移动终端供电之前,该方法还包括以下步骤: [0022] 用电端的移动终端在用电端的移动终端中判断是否对用电端的电池进行充电,如果是,则将用电端的电路接口与充电电路耦合。 如果否,则断开用电端的电路接口与充电电路之间的耦合。 [0023] 优选地,在供电端的移动终端向用电端的移动终端供电的过程中,该方法还包括以下步骤: [0024] 用电端的移动终端检测并显示供电端的移动终端的供电端的电池电量。 [0025] 另一方面,提供了一种移动终端,所述移动终端包括供电端的电池,所述移动终端还包括: [0026] 电源端电路接口; 和 [0027]供电端的供电控制单元,分别与供电端的电池和供电端的电路接口耦接,用于通过电路接口控制供电端的电池对外供电。 电源端。 [0028] 优选地,所述移动终端还包括: [0029] 所述供电端的充电控制单元,与所述供电端的电池相连,用于对所述供电端的电池进行充电控制; 和 [0030] 电源接口控制单元,串联在电源端的电路接口和电源端的电源控制单元之间,并与电源端的充电控制单元耦合,用于控制电路接口 供电端与供电端的充电控制单元或供电端的供电控制单元耦接。 [0031] 另一方面,提供了一种移动终端,包括用电端的电池和与用电端的电池耦合的电源管理单元,所述电源管理单元包括电源开关子单元,所述移动终端还包括电路接口。 用电端的结构和用电端的供电控制单元; 其中, [0032] 用电端的电路接口,用于与外部供电装置耦合; [0033] 电源开关子单元,分别与用电端的电路接口、用电端的电池和用电端的电源控制单元耦合,用于控制用电端的电路接口或 用电端的电池与用电端的供电控制单元耦合; 和 [0034] 用电端的供电控制单元,用于为移动终端供电。 [0035] 优选地,电源管理单元还包括依次串联在用电端的电路接口和供电开关子单元之间的充电供电模式控制子单元和电量检测开关子单元,以及电量检测子单元。 带有电量检测开关子单元; 所述移动终端还包括所述用电端的充电控制单元,与所述用电端的电池相连。 其中, [0036] 用电端的充电控制单元,用于对用电端的电池进行充电控制。 [0037] 充电和供电模式控制子单元,与用电端的充电控制单元耦合,用于控制外部供电设备在给移动设备供电时,是否对用电端的电池进行充电。 用电端终端; 和 [0038] 电量检测开关子单元,用于控制电量检测子单元检测用电端的电池电量或外部供电设备的电池电量。 [0039] 根据本发明,具有供电能力的移动终端能够通过外接电源线向缺电的移动终端供电,控制供电端和用电端的电源控制电路,电源 利用端能够检测供电端的电量,可以实现两个移动终端共享一个电池,大大增加了电池在无需外接充电电源的情况下的利用方式,方便用户利用 用户。 附图的简要说明 [0040] 图1是根据本发明实施例的供电端移动终端的结构示意图; [0041]图2是根据本发明实施例的用电端的移动终端的结构示意图; [0042] 图3为本发明实施例提供的另一种供电端移动终端的结构示意图。 [0043] 图4为本发明实施例提供的另一种用电端移动终端的结构示意图。 [0044] 图5为本发明实施例提供的移动终端间共享电池的方法流程图。 [0045] 图6为本发明实施例供电端移动终端对外供电时的流程图。 和 [0046] 图7是根据本发明实施例的用电端的移动终端从外部接收电力时的流程图。 具体实施方式 [0047] 为解决现有技术中无法在移动终端间共享电池的问题,本发明提供了一种移动终端间共享电池的系统、方法及移动终端,下面将结合以下内容进行详细说明。 附图和实施例。 应当理解,此处所描述的实施例仅用于说明本发明,并不用于限制本发明。 [0048] 如图1和图2所示,本发明实施例一涉及一种移动终端间共享电池的系统,包括供电端移动终端和用电端移动终端。 供电端移动终端结构如图1所示,包括电池 103 电源端,电路接口 101 供电端和供电控制单元 102 所述的供电端,其中所述供电控制单元 102 电源端与电池耦合 103 电源端与电路接口 101 电源端分别。 用电端的移动终端结构如图2所示,包括电池 204 用电端,电路接口 201 用电端,电源控制单元 203 用电端和电源管理单元 202 ,其中电源管理单元 202 与电池耦合 204 用电端,包括电源开关子单元 2021 . [0049] 电路接口 201 用电端与电路接口耦合 101 电源端; 电源控制单元 102 电源端用于控制电池 103 供电端通过电路接口向用电端的移动终端供电 101 电源端; [0050] 电源开关子单元 2021 ,加上电路接口 201 用电端,电池 204 用电端和供电控制单元 203 用电端分别用于控制电路接口 201 用电端或电池 204 用电端与电源控制单元耦合 203 用电端; 和电源控制单元 203 用电端的移动终端,用于向用电端的移动终端供电。 [0051] 当供电端的移动终端在本地供电时,即供电端的移动终端没有开启电池共享功能从而不给用电端的移动终端供电时,电池 103 供电端在移动终端中的供电端与供电控制单元耦合 102供电端,通过供电控制单元就地供电 102 的电源端。 当供电端的移动终端开启电池共享功能从而为用电端的移动终端供电时,电池 103 电源端,电源控制单元 102 电源端与电路接口 101 电源端依次串联耦合,此时电源控制单元 102 供电端在保证供电端移动终端本地供电的前提下,通过电路接口实现向用电端移动终端供电的功能 101 供电端与用电端的移动终端相连。 [0052] 当用电端的移动终端通过电池供电时 204 用电端,供电开关子单元 2021 电源管理单元 202 与电池耦合 204 用电端,从而使电池的电源 204 用电端通过供电开关子单元对用电端的移动终端本地供电 2021 和电源控制单元 203 与电源开关子单元耦合的用电端的 2021 . 当电池 204 用电端低电平或停机,电路接口 101 电源端与电路接口耦合 201 用电端通过供电线,使电池 103 供电端移动终端中的供电端向用电端移动终端供电。 通过控制电路接口的输出电压,可以提供不高于供电端移动终端本地电压的供电电压 101 电源端通过电源控制单元 102 ,从而以不高于上述本地电压的电源电压向用电端的移动终端供电。 此时,电源开关子单元 2021 断开与电池的耦合 204 用电端与电路接口耦合 201 用电端,即电池提供的电量 103 供电端向供电控制单元供电 203 用电端通过电路接口 101 电源端,电路接口 201 用电端和供电开关子单元 2021 . 电源控制单元 203 用电端的移动终端根据用电端移动终端使用的电压、电流、电量等参数调整电压和电量,最终向用电端移动终端供电。 电池共享 103 实现了供电端和用电端的移动终端之间的供电端的连接,达到同时使用供电端和用电端两个移动终端的目的。 [0053] 另外,由于大多数移动终端使用充电电池或需要数据传输,因此移动终端通常设置有充电接口或数据接口。 由于移动终端便携性的要求,它们在尺寸和接口数量上受到限制。 另外,考虑到充电接口或者部分数据接口可以作为供电接口,额外使用供电端移动终端上的充电接口或者数据接口作为电路接口 101 本实施例中设计了电源端。 [0054] 如图3所示,在上述实施例的基础上,供电端的移动终端还包括:充电控制单元 105供电端和供电接口控制单元 104 ,其中充电控制单元 105 电源端与电池耦合 103 电源端; 电源接口控制单元 104 在电路接口之间串联耦合 101 电源端和电源控制单元的 102 电源端,与充电控制单元耦合 105 的电源端。 充电控制单元 105 供电端,用于对电池进行充电控制 103 电源端; 和电源接口控制单元 104 被配置为控制电路接口 101 电源端与充电控制单元耦合 105 供电端或供电控制单元 102 的电源端。 即当电路接口 101 供电端作为充电接口,供电接口控制单元 104 控制电路接口 101 电源端与充电控制单元耦合 105 电源端,并断开电路接口之间的耦合 101 电源端和电源控制单元的 102 的电源端。 这样,电池 103 供电端可充电,可通过供电控制单元就地供电 102 的电源端。 [0055] 当电路接口 101 供电端与供电线耦合,用户配置开启供电端移动终端的电池共享功能,为用电端移动终端供电。 即当电路接口 101 供电端作为供电接口,供电接口控制单元 104 打破了电路接口之间的耦合 101 供电端与充电控制单元 105 电源端,耦合电路接口 101 带电源控制单元的电源端 102 电源端,读取电压等配置参数,配置电源控制单元 102 的电源端。 因此电池 103 电源端可通过电路接口对外供电 101 通过供电控制单元本地同时供电时供电端的 102 的电源端。 [0056] 并且,供电端的移动终端在向用电端的移动终端供电时,可能存在用电端的移动终端无法通过以下方式与供电端的移动终端耦合的情况。 供电线路较长时间,因此用户有通过供电端的移动终端给用电端的移动终端充电的需求。 另外,供电端的移动终端向用电端的移动终端供电时,电池的剩余电量 103 供电端的移动端对供电端的移动终端和用电端的移动终端来说都是至关重要的,所以需要检测电池的剩余电量 103 以提醒用户进行相应的操作。 综上所述,本发明实施例进一步设计了用电端的移动终端。 [0057] 如图4所示,在上述实施例的基础上,用电端的移动终端还包括充电控制单元 205 用电端与电池耦合 204 用电端; 电源管理单元 202 还包括充电和供电模式控制子单元 2022 、电量检测开关子单元 2023 电量检测子单元 2024,其中充电和供电模式控制子单元 2022 电量检测开关子单元 2023 在电路接口之间串联耦合 201 用电端和供电开关子单元 2021 依次,电量检测子单元 2024 与电量检测开关子单元耦合 2023 . 充电控制单元 205 用电端,用于对电池进行充电控制 204 用电端; 充电和供电方式控制子单元 2022 与充电控制单元耦合 204 供电端的移动终端,用于控制供电端的移动终端是否对电池进行充电 204 供电端的移动终端向用电端的移动终端供电时,用电端的供电; 电量检测开关子单元 2023 用于控制电量检测子单元 2024 检测电池电量 103 电源端或电池电量 204 用电端。 [0058] 后电路接口 201 用电端的移动终端中的用电端与供电线耦合,首先,用电端的移动终端判断是否给电池充电 204 供电端的移动终端向用电端的移动终端供电时,供电端的移动终端向供电端的移动终端供电时,若为是,则充电及供电模式控制子单元 2022 控制电路接口 201 用电端与充电控制单元耦合 205 用电端对电池充电 204 用电端通过充电控制单元 205 用电端,同时保持电路接口之间的耦合 201 用电端和供电开关子单元 2021 为用电端的移动终端供电; 否,充电和供电模式控制子单元 2022 打破了电路接口之间的耦合 201 用电端和充电控制单元 205 用电端,只保持电路接口之间的耦合 201 用电端和供电开关子单元 2021 为用电端的移动终端供电。 [0059] 当用电端的移动终端通过电池供电时 204 用电端,电量检测开关子单元 2023 控制电量检测子单元 2024 检测电池的端电压 204 用电端和电压衰减,估算电池容量 103 供电端,将预估容量写入PMU状态寄存器,供UI(User Interface)访问,并显示当前电量。 在供电端移动终端向用电端移动终端供电过程中,电量检测切换子单元 2023 控制电量检测子单元 2024 检测电池的端电压 103 电源端和电压衰减,估算电池容量 103 供电端,将预估容量写入PMU状态寄存器供UI访问,显示当前电量。 [0060]由上述实施例可知,本发明实施例通过供电端的移动终端向用电端的移动终端供电,实现了移动端之间共享供电端的电池。 供电端和用电端的端子,减少了额外使用接口所增加的硬件,简化了结构,实现了对用电端电池充电的功能,方便用户使用。 [0061] 如图5所示,本发明实施例二涉及一种移动终端间共享电池的方法,包括以下步骤。 [0062] 小号 301 供电端的移动终端通过用电端的电路接口向用电端的移动终端供电。 [0063] 如图6所示,如果供电端移动终端的充电接口额外作为供电端移动终端中的供电端电路接口,则上述步骤包括如下步骤。 [0064] 小号 3011 ,供电端的移动终端通过供电线与用电端的移动终端耦合后,开启供电模式。 [0065] 小号 3012 ,由于供电端的电路接口在供电端的移动终端不对外供电时作为充电接口,所以供电端的电路接口与充电电路耦合,即电路接口 供电端的充电控制单元耦接供电端的充电控制单元,以通过供电端的充电控制单元对供电端的电池进行充电。 供电端的移动终端对外供电时,供电端的电路接口不再作为充电接口,因此需要断开供电端的电路接口与充电端之间的耦合。 充电电路。 [0066] 小号 3013 ,由于正常工作时的额定工作电压可能因不同的移动终端而异,需要在给用电端的移动终端供电前确定是否配置降压参数,如果是,则转S 3014 , 否则转 S 3015 . [0067] 小号 3014 ,根据用电端移动终端的额定工作电压、额定工作电流等参数配置降压参数,然后转S 3016 . [0068] 小号 3015 ,使用供电端电池的当前电压参数,转S 3016 . [0069] 小号 3016 ,电源端的电路接口与电源端电池的放电电路耦合,即电源端的电路接口通过电源控制单元与电源端的电池耦合。 电源端。 [0070] 小号 3017 ,供电端的供电控制单元在本地向供电端的移动终端供电时,通过供电端的电路接口向与其连接的用电端的移动终端供电。 同时。 [0071] 小号 302 ,用电端的移动终端打开用电端电池的供电电路,关闭用电端电路接口的供电电路。 [0072] 如图7所示,在供电端的移动终端在给用电端的移动终端供电时,还需要给用电端的电池充电的情况下,S 302 具体包括如下步骤。 [0073] 小号 3021 ,供电端的移动终端的电源进入为用电端的移动终端供电。 [0074] 小号 3022,首先判断供电端的移动终端向用电端的移动终端供电时,是否需要在用电端的移动终端对用电端的电池进行充电,如果是 需要这样做,保持用电端的电路接口和充电电路的耦合,即保持用电端的电路接口和用电端的充电控制单元的耦合,然后转向 小号 3024 ; 如果不需要,请转到 S 3023 . [0075] 小号 3023 ,用电端的电路接口与用电端的电池的耦合断开,即用电端的电路接口与用电端的充电控制单元的耦合断开,然后 转向S 3024 . [0076] 小号 3024 ,判断用电端的移动终端是否开启电池共享功能,即判断用电端的移动终端是否有外接电源输入,如果用电端的移动终端有外接电源 电源输入,表示开启电池共享功能,转S 3025 ; 如果用电端的移动终端没有外接电源输入,则表示电池共享功能关闭,转S 3026 . [0077] 小号 3025 ,用电端移动终端在供电端移动终端检测供电端电池端电压及电压衰减,估计供电端电池容量,写入估计 在 PMU 状态寄存器的容量为 U 的访问 1 ,最后显示当前电量。 [0078] 小号 3026 ,用电端电池的供电电路断开(即用电端电池与PMU供电开关子单元的耦合断开),同时, 用电端的电路接口闭合(即将用电端的电路接口与供电开关子单元耦合)。 [0079] 小号 3027 ,结束,即完成供电端的移动终端向用电端的移动终端供电的电路。 [0080] 小号 303 ,供电端的移动终端向用电端的移动终端供电。 [0081] 以USB(Universal Serial Bus)作为供电端和用电端的电路接口为例,详细说明本实施例的方案。 [0082] 目前,移动终端一般都带有USB接口,用于数据传输和充电。 标准USB接口提供5V电压和0.5A输出电流,具有4根数据线和2根电源线的有效引线,其中电源线分别耦合到PMU管脚上,用于充电和供电。 供电端移动终端的USB接口作为供电电路接口。 该移动终端之间共享电池的方法包括以下步骤。 [0083] 1、USB接口附加作为供电端移动终端的供电电路接口。 [0084]增加USB接口控制开关,控制与USB接口耦合的供电端电池的充电电路(电源管理单元,PMU)和放电电路。 用户可以配置控制开关来控制USB接口与充电电路或放电电路耦合。 如果移动终端的电池提供4.2V的输出电压,USB接口在与放电电路耦合的情况下,可以提供4.2V的输出电压。 如果电源IC串联耦合,通过控制电源IC可以控制接口提供不高于4.2V的输出电压。 或者可以串联一个二极管以提供降低到固定值的电压输出。 [0085] 2、用电端移动终端的USB接口与用电端移动终端的PMU耦合。 PMU可以通过编程控制用电端电池的充电电路和供电电路的闭合或断开,切换供电和充电模式。 PMU还可以控制输入电压的范围,将输入电压降低到用电端移动终端的允许电压范围内,从而为用电端移动终端提供一致的电流供电。 例如,如果用电端的移动终端的供电电压为3.9V,则供电电路将通过降压提供3.9V的电压输出。 充电电路是指对用电端电池充电所涉及的电路; 供电端是指为用电端的移动终端供电所涉及的电路。 [0086] 3、通过将用电端的移动终端配置为电池共享模式,PMU将电量检测切换到进入的供电线路,以检测供电端电池的电压衰减情况,估算出供电端的容量。 电源端的电池,并将估计容量写入PMU的状态寄存器,用于UI的访问和当前电量的显示。 [0087] 由以上描述可知,通过该方法,可以在增加少量硬件的情况下,额外使用现有接口,降低成本,实现电池共享,特别是在没有可用充电配件的情况下,可以丰富使用 移动终端之间的电池模式。 并且,通过对用电端移动终端的控制,可以灵活配置供电电压,保证用电端移动终端的安全使用。 用电端移动终端可以通过检测输入电压来模拟供电端移动终端的电池容量,以方便用户使用。 用电端移动终端可以通过配置在供电模式和充电/供电模式之间切换,可以有效利用供电端移动终端的电池容量,方便用户使用。 [0088] 尽管出于示例性目的公开了本发明的优选实施例,但是本领域技术人员应当意识到各种改进、添加和替换是可能的。 因此,本发明的范围不应限于上述实施例。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101728859A(String), CN101728859B(String), EP2515416A1(String), EP2515416A4(String), EP2515416B1(String), US20120266001A1(String), US8898492B2(String), WO2010148950A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101728859A(String), CN101728859B(String), EP2515416A1(String), EP2515416A4(String), EP2515416B1(String), US20120266001A1(String), US8898492B2(String), WO2010148950A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8898492B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101728859A(String), CN101728859B(String), EP2515416A1(String), EP2515416A4(String), EP2515416B1(String), US20120266001A1(String), US8898492B2(String), WO2010148950A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), CN101728859A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), CN101728859B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.431 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), EP2515416A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), EP2515416A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), EP2515416B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), US20120266001A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), US8898492B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270671(Integer), WO2010148950A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.485 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.485 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.485 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8898492B2(String), US8898492B2(String), 1416844800(Integer), 270671(Integer), 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), SHA, JINCHUAN(String), ZHONG, SHENG(String), 中兴通讯股份有限公司(String), SHA JINCHUAN(String), ZHONG SHENG(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184991(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184991(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHA, JINCHUAN(String), SHA JINCHUAN(String), 0(Integer), 1681975549(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHONG, SHENG(String), ZHONG SHENG(String), 0(Integer), 1681975549(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184991(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75929(Integer), 2(Integer), 184991(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75930(Integer), 2(Integer), 184991(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8099108B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminals including display screens capable of displaying maps and map display methods for mobile terminals(String), 包括能够显示地图的显示屏的移动终端和用于移动终端的地图显示方法(String), US8099108B2(String), A mobile terminal includes a communication module, a display screen, and control circuitry. The circuitry is configured to estimate a current geographic position of the mobile terminal, and to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. The circuitry is further configured to retrieve additional geographic map information including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information.(String), 一种移动终端,包括通信模块、显示屏和控制电路。 该电路被配置为估计移动终端的当前地理位置,并确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内。 该电路还被配置为如果移动终端的当前位置不在所存储的地理地图信息的边界内,则使用通信模块检索包括移动终端的当前位置的附加地理地图信息。(String), US11/776805(String), 1184169600(Integer), US8099108B2(String), 1326729600(Integer), 1326729600(Integer), 美国(String), 4(Integer), 6(Integer), 17(Integer), DE19537255A1 | JP1996145699A | JP1996286602A | JP1998013961A | JP1998105053A | JP2001117554A | JP2002213990A | JP2002312801A | US20020087263A1 | US20020116121A1 | US20030201912A1 | US20040193371A1 | US20050195221A1 | US20060122768A1 | US20070124065A1 | US20080243375A1 | US20080288166A1(String), 19(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184992(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\1d29f9f5feaa4d9eb1b82edc128507a8.png(String), 184992(Integer), 1d29f9f5feaa4d9eb1b82edc128507a8.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminals including display screens capable of displaying maps and map display methods for mobile terminals(String), 包括能够显示地图的显示屏的移动终端和用于移动终端的地图显示方法(String), US8099108B2(String), A mobile terminal includes a communication module, a display screen, and control circuitry. The circuitry is configured to estimate a current geographic position of the mobile terminal, and to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. The circuitry is further configured to retrieve additional geographic map information including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information.(String), 一种移动终端,包括通信模块、显示屏和控制电路。 该电路被配置为估计移动终端的当前地理位置,并确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内。 该电路还被配置为如果移动终端的当前位置不在所存储的地理地图信息的边界内,则使用通信模块检索包括移动终端的当前位置的附加地理地图信息。(String), US11/776805(String), 1184169600(Integer), US8099108B2(String), 1326729600(Integer), 1326729600(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 17(Integer), DE19537255A1 | JP1996145699A | JP1996286602A | JP1998013961A | JP1998105053A | JP2001117554A | JP2002213990A | JP2002312801A | US20020087263A1 | US20020116121A1 | US20030201912A1 | US20040193371A1 | US20050195221A1 | US20060122768A1 | US20070124065A1 | US20080243375A1 | US20080288166A1(String), \20230420\1d29f9f5feaa4d9eb1b82edc128507a8.png(String), 19(Integer), 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 1. A method comprising:estimating a current geographic position of a mobile terminal including a communication module and a display screen;determining if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, the geographic map information defining geographic features within a first geographic area;in response to determining that the estimated current position of the mobile terminal is within the boundary of the stored geographic map information, displaying the map including the current position of the mobile terminal on the display;in response to determining that the estimated current position of the mobile terminal is not within the boundary of the stored geographic map information, providing additional geographic map information to the mobile terminal using the communication module, the additional geographic map information defining geographic features within a second geographic area that includes the estimated current position of the mobile terminal; anddetermining a current scale for the display screen to display a map by estimating a current speed of the mobile terminal and automatically selecting a display scale in response to the current speed of the mobile terminal, wherein selecting the display scale comprises selecting a relatively larger scale if the speed of the mobile terminal is higher and selecting a smaller scale if the speed of the mobile terminal is smaller.(String), 1.一种方法包括:估计包括通信模块和显示屏的移动终端的当前地理位置;确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内,该地理地图信息定义第一地理区域内的地理特征;响应于确定移动终端的估计当前位置在存储的地理地图信息的边界内,将包括移动终端当前位置的地图显示在显示器上;响应于确定移动终端的估计当前位置不在所存储的地理地图信息的边界内,使用通信模块向移动终端提供额外的地理地图信息,该额外的地理地图信息定义第二内的地理特征包括移动终端的估计当前位置的地理区域;和通过估计移动终端的当前速度确定显示屏显示地图的当前比例尺,并根据移动终端的当前速度自动选择显示比例尺,其中,选择显示比例尺包括选择相对较大的比例尺,如果移动端的速度越小,移动端的速度越高,选择越小的尺度。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 2. The method of claim 1, further comprising:determining a current scale for the map;determining if the stored map information contains enough map information to fill the display screen at the current scale;in response to determining that the stored map information does not contain enough map information to fill the display screen at the current scale, reducing the scale of the display screen until the stored map information is sufficient to fill the display screen at the reduced scale.(String), 2.如权利要求1所述的方法,还包括:确定地图的当前比例;确定存储的地图信息是否包含足够的地图信息以填满当前比例尺的显示屏幕;响应于确定存储的地图信息不包含足够的地图信息来以当前比例填充显示屏幕,减小显示屏幕的比例直到存储的地图信息足以以缩小的比例填充显示屏幕。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 3. The method of claim 2, further comprising retrieving additional map information using the communication module sufficient to fill the display screen at the current scale, and after the additional map information has been retrieved, increasing the scale to the current scale.(String), 3.如权利要求2所述的方法,还包括使用足以以当前比例填满显示屏幕的通信模块检索额外的地图信息,并且在已经检索到额外的地图信息之后,将比例增加到当前比例。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 4. The method of claim 1, further comprising estimating a current speed and direction of travel of the mobile terminal and estimating, in response to the current speed and direction of travel of the mobile terminal, when the mobile terminal will leave an area described by the stored map information.(String), 4.如权利要求1所述的方法,还包括估计移动终端当前的行进速度和方向,并根据移动终端当前的行进速度和方向,估计移动终端将离开存储的地图信息描述的区域的时间。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 5. The method of claim 4, further comprising:estimating an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and downloading the additional map information before the mobile terminal leaves the area described by the stored map information.(String), 5.如权利要求4所述的方法,还包括:估计为移动终端正前往的地理区域下载附加地图信息所需的时间量,并且在移动终端离开存储的地图信息所描述的区域之前下载附加地图信息。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 6. The method of claim 1, wherein estimating the current position of the mobile terminal is performed by a remote server in response to network-generated location information.(String), 6.如权利要求1所述的方法,其中估计移动终端的当前位置由远程服务器响应于网络生成的位置信息来执行。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 7. The method of claim 6, further comprising transmitting additional map information to the mobile terminal from the remote server if the current position of the mobile terminal is not within the boundary of the stored geographic map information.(String), 7.如权利要求6所述的方法,还包括如果移动终端的当前位置不在存储的地理地图信息的边界内,则从远程服务器向移动终端发送附加地图信息。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 8. The method of claim 1, wherein displaying the map including the current position of the mobile terminal on the display comprises displaying the map including the current position of the mobile terminal on the display after a predetermined period of nonuse of the mobile terminal.(String), 8.如权利要求1所述的方法,其中在显示器上显示包括移动终端的当前位置的地图包括在移动终端未使用预定时间段之后在显示器上显示包括移动终端的当前位置的地图。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 9. The method of claim 8, wherein the mobile terminal further comprises a secondary display screen on a flip portion that is movable between an open position and a closed position so that the secondary display screen is visible when the flip portion is in the closed position, the method comprising displaying the map including the current position of the mobile terminal on the secondary display when the flip portion is in the closed position.(String), 9.如权利要求8所述的方法,其中移动终端还包括在翻盖部分上的副显示屏,该副显示屏可在打开位置和闭合位置之间移动,使得副显示屏在翻盖部分处于闭合位置时可见,该方法包括显示地图,该地图包括当翻盖部分处于关闭位置时移动终端在辅助显示器上的当前位置。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 10. The method of claim 1, further comprising:determining that the mobile terminal has entered an idle mode; andreducing a brightness of the display and/or turning the display off;wherein estimating the current geographic position of the mobile terminal and determining if the estimated current position of the mobile terminal is within the boundary of geographic map information stored in the mobile terminal are performed while the mobile terminal is in the idle mode.(String), 10.如权利要求1所述的方法,还包括:确定移动终端进入空闲模式;和降低显示器的亮度和/或关闭显示器;其中,估计移动终端的当前地理位置以及判断估计的移动终端的当前位置是否在移动终端存储的地理地图信息的边界内是在移动终端处于空闲模式时执行的。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 11. The method of claim 10, wherein providing additional geographic map information to the mobile terminal using the communication module is performed while the mobile terminal is in the idle mode.(String), 11.如权利要求10所述的方法,其中当移动终端处于空闲模式时执行使用通信模块向移动终端提供附加地理地图信息。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 12. A mobile terminal, comprising:a communication module;a display screen; andcircuitry configured to estimate a current geographic position of the mobile terminal; to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, the geographic map information defining geographic features within a first geographic area; to display the map including the current position of the mobile terminal on the display in response to determining that the estimated current position of the mobile terminal is within the boundary of the stored geographic map information; and to retrieve additional geographic map information using the communication module in response to determining that the estimated current position of the mobile terminal is not within the boundary of the stored geographic map information, the additional geographic map information defining geographic features within a second geographic area that includes the estimated current position of the mobile terminal;wherein the circuitry is further configured to determine a current scale for the map on the display screen by estimating a current speed of the mobile terminal and to automatically select a display scale in response to the current speed of the mobile terminal.(String), 12.移动终端,包括:通信模块;显示屏;和被配置为估计移动终端的当前地理位置的电路​​;确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内,该地理地图信息定义第一地理区域内的地理特征;响应于确定移动终端的估计当前位置在存储的地理地图信息的边界内,在显示器上显示包括移动终端当前位置的地图;响应于确定移动终端的估计当前位置不在存储的地理地图信息的边界内,使用通信模块检索附加地理地图信息,附加地理地图信息定义第二地理区域内的地理特征包括移动终端的估计当前位置;其中,该电路还被配置为通过估计移动终端的当前速度来确定显示屏上地图的当前比例尺,并响应于移动终端的当前速度自动选择显示比例尺。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 13. The mobile terminal of claim 12, wherein the circuitry is further configured to determine a current scale for the map; to determine if the stored map information contains enough map information to fill the display screen at the current scale; and to reduce the scale of the display screen until the stored map information is sufficient to fill the display screen at the reduced scale in response to determining that the stored map information does not contain enough map information to fill the display screen at the current scale.(String), 13.如权利要求12所述的移动终端,其中该电路还被配置为确定地图的当前比例;判断存储的地图信息是否包含足够的地图信息以填满当前比例尺的显示屏幕;响应于确定存储的地图信息不包含足够的地图信息来以当前比例填满显示屏幕,减小显示屏幕的比例直到存储的地图信息足以以缩小的比例填满显示屏幕。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 14. The mobile terminal of claim 13, wherein the circuitry is further configured to retrieve additional map information using the communication module, and to increase the scale to an increased scale that is larger than the reduced scale after the additional map information has been retrieved.(String), 14.如权利要求13所述的移动终端,其中该电路还被配置为使用通信模块检索附加地图信息,并且在检索到附加地图信息之后将比例尺增加到大于缩小比例尺的增加比例尺。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 15. The mobile terminal of claim 12, wherein the circuitry is further configured to estimate a current speed and direction of travel of the mobile terminal, and, in response to the current speed and direction of travel of the mobile terminal, to estimate when the mobile terminal will leave an area described by the stored map information.(String), 15.如权利要求12所述的移动终端,其中该电路还被配置为估计移动终端的当前行进速度和方向,并且响应于移动终端的当前行进速度和方向,估计移动终端何时将离开存储的描述的区域地图信息。(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 16. The mobile terminal of claim 15, wherein the circuitry is further configured toestimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to download the additional map information before the mobile terminal leaves the area described by the stored map information.(String), 16.如权利要求15所述的移动终端,其中该电路还被配置为估计为移动终端正前往的地理区域下载附加地图信息以及在移动终端离开由存储的地图信息描述的区域之前下载附加地图信息所需的时间量。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 17. A map server, comprising:a communication module configured to communicate with a remotely located mobile terminal;a position/velocity determination unit configured to estimate position/velocity information for the mobile terminal;a database storing map information; andcircuitry configured to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, the geographic map information defining geographic features within a first geographic area; and to send additional geographic map information from the database using the communication module in response to determining that the estimated current position of the mobile terminal is not within the boundary of the stored geographic map information, the additional geographic map information defining geographic features within a second geographic area that includes the estimated current position of the mobile terminal;wherein the circuitry is further configured to determine a current scale for a map on a display screen of the mobile terminal by estimating a current speed of the mobile terminal and to automatically select a display scale for the map in response to the current speed of the mobile terminal.(String), 17.地图服务器,包括:通信模块,用于与远程移动终端进行通信;位置/速度确定单元,用于估计移动终端的位置/速度信息;储存地图信息的数据库;和被配置为确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内的电路,该地理地图信息定义第一地理区域内的地理特征;响应于确定移动终端的估计的当前位置不在存储的地理地图信息的边界内,使用通信模块从数据库发送附加的地理地图信息,附加的地理地图信息定义了第二个内的地理特征包括移动终端的估计当前位置的地理区域;其中,该电路还被配置为通过估计移动终端的当前速度来确定移动终端显示屏上地图的当前比例尺,并响应于移动终端的当前速度自动选择地图的显示比例尺终端。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 18. The map server of claim 17, wherein the position/velocity determination unit is configured to estimate the current position of the mobile terminal using location information provided by a communication network in which the mobile terminal is registered.(String), 18.如权利要求17所述的地图服务器,其中位置/速度确定单元被配置为使用由移动终端在其中注册的通信网络提供的位置信息来估计移动终端的当前位置。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184992(Integer), 19. The map server of claim 17, wherein the circuitry is further configured to estimate when the mobile terminal will leave an area described by the map information stored at the mobile terminal using the position/velocity of the mobile terminal, to estimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to transmit the additional map information to the mobile terminal before the mobile terminal leaves the area described by the map information stored at the mobile terminal.(String), 19.如权利要求17所述的地图服务器,其中电路还被配置为使用移动终端的位置/速度来估计移动终端何时将离开存储在移动终端处的地图信息所描述的区域,以估计下载地理的附加地图信息所需的时间量移动终端正前往的区域,并且在移动终端离开存储在移动终端处的地图信息所描述的区域之前将附加地图信息发送到移动终端。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184992(Integer), FIELD OF THE INVENTION [0001]The present invention relates to wireless communication terminals, and more particularly, to wireless communication terminals including display screens capable of displaying map information. BACKGROUND [0002]Wireless communication terminals are primarily used for obtaining access to wireless telephone services through a cellular telephone network. However, as the capabilities of wireless communication terminals increase, an additional level of user functionality is being included in the hardware and/or software of such terminals. For example, a communication terminal may be provided with a still and/or video camera, allowing pictures and/or videos to be taken by a user and transmitted from the mobile terminal to others. Likewise, many communication terminals include personal digital assistant (PDA) type applications suitable for tracking and managing schedules, tasks and the like. Many communication terminals also include messaging capability, such as electronic mail (e-mail), short message service (SMS) and multimedia message service (MMS) capabilities. Communication terminals may also be capable of connecting to the internet by using internet protocol (IP) over wireless and/or wired networks. [0003]Communication terminals are also increasingly being provided with the capability of determining the physical location of the terminal. For example, many communication terminals include global positioning system (GPS) receivers that permit the terminals to determine their location with a high degree of precision. Other systems for determining the location of a communication terminal have been implemented, including systems that obtain location information from a cellular communications network, and systems that obtain location information through inertial guidance techniques. [0004]In addition, some wireless networks have the ability to determine an approximate location of a terminal that is registered to the system. Such location information can be used, for example, to provide location information to emergency operators when a terminal is used to call for emergency help. SUMMARY [0005]Methods according to some embodiments of the invention include estimating a current geographic position of a mobile terminal including a communication module and a display screen, and determining if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. If the current position of the mobile terminal is within the boundary of the stored geographic map information, the map including the current position of the mobile terminal is displayed on the display. If the current position of the mobile terminal is not within the boundary of the stored geographic map information, additional geographic map information including the current position of the mobile terminal is provided to the mobile terminal using the communication module. [0006]The methods may further include determining a current scale for the map, and determining if the stored map information contains enough map information to fill the display screen at the current scale. If the stored map information does not contain enough map information to fill the display screen at the current scale, the scale of the display screen can be reduced until the stored map information is sufficient to fill the display screen at the reduced scale. [0007]The methods may further include retrieving additional map information using the communication module sufficient to fill the display screen at the current scale, and after the additional map information has been retrieved, increasing the scale to the current scale. [0008]The methods may further include determining a current scale for the display screen by estimating a current speed of the mobile terminal and selecting a display scale in response to the current speed of the mobile terminal. Determining the current scale may include selecting a relatively larger scale if the speed of the mobile terminal is higher and selecting a smaller scale if the speed of the mobile terminal is smaller. [0009]The methods may further include estimating a current speed and direction of travel of the mobile terminal and estimating, in response to the current speed and direction of travel of the mobile terminal, when the mobile terminal will leave an area described by the stored map information. [0010]The methods may further include estimating an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and downloading the additional map information before the mobile terminal leaves the area described by the stored map information. [0011]Estimating the current position of the mobile terminal may be performed by a remote server in response to network-generated location information. The methods may further include transmitting additional map information to the mobile terminal from the remote server if the current position of the mobile terminal is not within the boundary of the stored geographic map information. [0012]Displaying the map including the current position of the mobile terminal on the display may include displaying the map on the display after a predetermined period of nonuse of the mobile terminal. [0013]The mobile terminal may further include a secondary display screen on a flip portion of the device that is movable between an open position and a closed position so that the secondary display screen is visible when the flip portion is in the closed position. The methods may include displaying the map including the current position of the mobile terminal on the secondary display when the flip portion is in the closed position. [0014]The methods may further include determining that the mobile terminal has entered an idle mode, and reducing a brightness of the display and/or turning the display off. Estimating the current geographic position of the mobile terminal and determining if the estimated current position of the mobile terminal is within the boundary of geographic map information stored in the mobile terminal may be performed while the mobile terminal is in the idle mode. Furthermore, providing additional geographic map information to the mobile terminal using the communication module may be performed while the mobile terminal is in the idle mode. [0015]A mobile terminal according to some embodiments of the invention includes a communication module, a display screen, and control circuitry. The circuitry is configured to estimate a current geographic position of the mobile terminal, and to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. The circuitry is further configured to display the map including the current position of the mobile terminal on the display if the current position of the mobile terminal is within the boundary of the stored geographic map information, and to retrieve additional geographic map information including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information. [0016]The circuitry may be further configured to determine a current scale for the map, to determine if the stored map information contains enough map information to fill the display screen at the current scale, and to reduce the scale of the display screen until the stored map information is sufficient to fill the display screen at the reduced scale if the stored map information does not contain enough map information to fill the display screen at the current scale. [0017]The circuitry may be further configured to retrieve additional map information using the communication module, and to increase the scale to an increased scale that is larger than the reduced scale after the additional map information has been retrieved. [0018]The circuitry may be further configured to determine a current scale for the display screen by estimating a current speed of the mobile terminal and to select a display scale in response to the current speed of the mobile terminal. [0019]The circuitry may be further configured to estimate a current speed and direction of travel of the mobile terminal, and, in response to the current speed and direction of travel of the mobile terminal, to estimate when the mobile terminal will leave an area described by the stored map information. The circuitry may be further configured to estimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to download the additional map information before the mobile terminal leaves the area described by the stored map information. [0020]A map server according to some embodiments of the invention includes a communication module configured to communicate with a remotely located mobile terminal, a position/velocity determination unit configured to estimate position/velocity information for the mobile terminal, a database storing map information, and a circuitry configured to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, and to send additional geographic map information from the database including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information. [0021]The position/velocity determination unit may be configured to estimate the current position of the mobile terminal using location information provided by a communication network in which the mobile terminal is registered. [0022]The circuitry may be further configured to estimate when the mobile terminal will leave an area described by the map information stored at the mobile terminal using the position/velocity of the mobile terminal, to estimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to transmit the additional map information to the mobile terminal before the mobile terminal leaves the area described by the map information stored at the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0023]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate certain embodiment(s) of the invention. In the drawings: [0024]FIG. 1 illustrates an electronic device according to some embodiments of the invention. [0025]FIGS. 2A-2B illustrate a flip-type mobile telephone according to some embodiments of the invention. [0026]FIG. 3 is a schematic block diagram illustrating an electronic device and a cellular communication system in accordance with some embodiments of the present invention. [0027]FIGS. 4A and 4B are a schematic block diagrams illustrating some aspects of an electronic device in accordance with some embodiments of the present invention. [0028]FIG. 5 is a schematic block diagram illustrating a map server in accordance with some embodiments of the present invention. [0029]FIGS. 6A, 6B, 7A, 7B and 7C are exemplary illustrations of display screens configured according to some embodiments of the invention. [0030]FIGS. 8-11 are flow diagrams illustrating operations of electronic devices according to some embodiments of the invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION [0031]The present invention now will be described more fully with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein the term “comprising” or “comprises” is open-ended, and includes one or more stated elements, steps and/or functions without precluding one or more unstated elements, steps and/or functions. As used herein the term “and/or” includes any and all combinations of one or more of the associated listed items. [0032]Embodiments according to the present invention are described with reference to block diagrams and/or operational illustrations of methods and communication terminals. It is to be understood that each block of the block diagrams and/or operational illustrations, and combinations of blocks in the block diagrams and/or operational illustrations, can be implemented by radio frequency, analog and/or digital hardware, and/or program instructions. These program instructions may be provided to a controller, which may include one or more general purpose processors, special purpose processors, ASICs, and/or other programmable data processing apparatus, such that the instructions, which execute via the controller and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or operational block or blocks. In some implementations, the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. [0033]As used herein, a “communication terminal” (or simply a “terminal”) includes, but is not limited to, a device that is configured to receive/transmit communication signals via a wireline connection, such as via a public-switched telephone network (PSTN), digital subscriber line (DSL), digital cable, a direct cable connection, and/or another data connection/network, and/or via a wireless interface with, for example, a cellular network, a wireless local area network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM/FM broadcast transmitter, and/or another communication terminal. A communication terminal that is configured to communicate over a wireless interface may be referred to as a “wireless communication terminal,” a “wireless terminal” and/or a “mobile terminal.” Examples of mobile terminals include, but are not limited to, a satellite or cellular radiotelephone; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and a conventional laptop and/or palmtop receiver or other appliance that includes a radiotelephone transceiver. [0034]Wireless communication between electronic devices may be accomplished using a wide variety of communication media, communication systems and communication standards. For example, mobile terminals such as wireless mobile telephones are typically configured to communicate via analog and/or digital wireless radio frequency (RF) telephone systems. Such devices may additionally be configured to communicate using wired and/or wireless local area networks (LANs), short range communication channels, such as Bluetooth RF communication channels and/or infrared communication channels, and/or long range communication systems, such as satellite communication systems. [0035]Mobile terminals, such as wireless mobile telephones, according to embodiments of the invention can have a variety of shapes, sizes and housing types. Examples of several types of mobile telephone housings are shown in FIGS. 1 to 2B. For example, a mobile terminal 100A according to some embodiments is illustrated in FIG. 1. The mobile terminal 100A includes a housing 15 that houses and protects the electronics of the mobile terminal 100A. The mobile terminal 100A includes an LCD display 18 and a keypad 16. The mobile terminal 100A further includes a multifunction control/input button 22 that can be used to select menu items and/or to input commands to the mobile terminal 100A. [0036]The mobile terminal 100A includes a microphone port 14 and an earphone/speaker 20. The housing 15 may be designed to form an acoustic seal to the user's ear when the earphone/speaker 20 is placed against the user's head. The mobile terminal 100A may be configured to play video files and or audio files, such as song files, which may be stereophonic signals. [0037]A flip-style mobile terminal 100B is illustrated in FIGS. 2A and 2B. The flip-style mobile terminal 100B is shown in the open position in FIG. 2A and the closed position in FIG. 2B. The mobile terminal 100B includes a housing 15 that includes a lower housing 15A and an upper housing, or “flip” portion 15B that are rotatably connected by means of a hinge 24. The mobile terminal 100B includes a primary LCD display 18 on the inside of the flip 15B and a keypad 16 on the inside of the lower housing 15A. The mobile terminal 100B further includes a multifunction control/input button 22. [0038]The mobile terminal 100A includes a microphone port 14 on the lower housing 15A and an earphone/speaker 20 on the inside of the flip 15B. As shown in FIG. 2B, a secondary display 28 and a camera lens 30 may be located on the outside of the flip 15B. [0039]FIG. 3 is a schematic block diagram of a wireless communication system 10 that includes a mobile terminal 100 that is configured to communicate with a map server 200A, 200B. For example, the mobile terminal 100 can communicate with the map server 200A over a direct wireless communication interface 106, over another wireless communication interface 108 through one or more cellular base stations 110a-b, and/or over another wireless communication interface 112 through a wireless local area network (WLAN) access point 114. The direct wireless communication interface 106 may include an RF wireless communication interface such as a Bluetooth interface or an infrared communication interface, such as, for example, the infrared communication interface defined by the Infrared Data Association (IRDA) protocols. The IRDA defines a number of standards for infrared wireless data communication, including standards for infrared wireless communication at data rates up to 16 Mb/s. It will be appreciated that the mobile terminal 100 may be a handheld wireless communication terminal, such as a mobile telephone, PDA, or the like. [0040]As further illustrated in FIG. 3, the mobile terminal 100 can include a user interface 122, a controller 126, a communication module 128, and a memory 125. [0041]The communication module 128 is configured to communicate data over one or more of the wireless interfaces 106, 108, and/or 112 to another remote terminal or other communication device, such as the map server 200A, 200B. The memory 125 is configured to store programs and or data for use by the controller 126. The memory 125 may include a nonvolatile memory that is capable of storing digital information even when power to the mobile terminal 100 is switched off. [0042]The communication module 128 can include, for example, a cellular communication module, a Bluetooth module, an infrared communication module, and/or a WLAN module. With a cellular communication module, the mobile terminal 100 can communicate via the base stations 110a-b using one or more cellular communication protocols such as, for example, Advanced Mobile Phone Service (AMPS), ANSI-136, Global Standard for Mobile (GSM) communication, General Packet Radio Service (GPRS), enhanced data rates for GSM evolution (EDGE), code division multiple access (CDMA), wideband-CDMA, CDMA2000, and Universal Mobile Telecommunications System (UMTS). The cellular base stations 110a-b may be connected to a Mobile Telephone Switching Office (MTSO) 116, which, in turn, may be connected to one or more other networks 118 (e.g. the Internet, a public switched telephone network, and/or another network). With a Bluetooth or infrared module, the mobile terminal 100 can communicate via an ad-hoc network using the direct interface 106. With a WLAN module, the mobile terminal 100 can communicate through the WLAN router 114 using a communication protocol that may include, but is not limited to, 802.11a, 802.11b, 802.11e, 802.11g, and/or 802.11i. A mobile telephone may also be configured to communicate directly over the networks 118. [0043]The mobile terminal 100 may be configured to transmit and/or receive a digital data signal to/from another communication terminal that may be communicatively coupled thereto through, for example the MTSO 116, and/or another network 118, such as a public switched telephone network (PSTN). However, it will be appreciated from the foregoing description that data communication between the mobile terminal 100 and another terminal may be accomplished without using the MTSO 116 or the other networks 118. [0044]The mobile terminal 100 my additionally include an AM/FM radio tuner, a UHF/VHF tuner, a satellite radio tuner, a DVB-H receiver, and/or another receiver configured to receive a broadcast audio/video signal and/or data signal. [0045]The map server 200A can be a standalone server that is configured to communicate with the mobile terminal 100 over wireless communication links, such as the WLAN communication link 112, a direct wireless communication link 106, and/or another wireless communication interface 108 through one or more cellular base stations 110a-b. For example, the map server 200A could be configured to broadcast a data signal including map information over the wireless communication link 106 to mobile terminals, such as mobile terminal 100, within a geographic service area. That is, the map server 200A could broadcast maps of a particular geographic area to mobile terminals, such as mobile terminal 100, within the geographic area. In some embodiments, the wireless communication link 106 could be a one-way communication link, and maps could be broadcast over the one-way wireless communication link 106 blindly, i.e. without knowledge of any mobile terminals 100 within the geographic area. In other embodiments, the wireless communication link 106 could be a one-way communication link, and map information could be broadcast or otherwise transmitted on demand to a requesting mobile terminal 100 in response to a request received over a separate communication link, such as the WLAN communication link 112 and/or a cellular communication link 108. [0046]The map server 200B can be located within or otherwise controlled by a mobile telephone switching office (MTSO) 116, in which case the map server 200B may communicate with the wireless telephone 100 primarily using the wireless communication interface 108. [0047]Some further aspects of a mobile terminal 100 according to some embodiments of the invention are illustrated in FIGS. 4A and 4B. As shown therein, a mobile terminal 100 may further include a position/velocity determination unit 146 and a traffic information unit 148. The position/velocity determination unit 146 and the traffic information unit 148 may communicate with the communication module 128 through the controller 126 as shown in FIG. 3. Alternatively or additionally, the position/velocity determination unit 146 and/or the traffic information unit 148 may communicate directly with the communication module 128, for example through a system bus. [0048]According to some embodiments, the position/velocity determination unit 146 may be configured to determine a current position and/or velocity of the mobile terminal 100. For example, the position/velocity determination unit 146 may include a global positioning system (GPS) receiver that permits the position/velocity determination unit 146 to determine the location of the mobile terminal 100 with a high degree of precision. The position/velocity determination unit 146 may include other systems and/or functionality for determining the location of the mobile terminal 100. For example, the position/velocity determination unit 146 may be configured to obtain location information for the mobile terminal 100 from a cellular communications network with which the mobile terminal 100 communicates. The position/velocity determination unit 146 may additionally or alternatively include an inertial guidance system that permits the position/velocity determination unit 146 to determine a position/velocity of the mobile terminal 100 through inertial movement from a known position. [0049]The traffic information unit 148 is configured to obtain information about current automobile and/or pedestrian traffic in or near a location at which the mobile terminal 100 is located and/or near a destination point, or along a route from a current location of the mobile terminal 100 to a destination point. For example, traffic information may be broadcast in one or more data subchannels of a public and/or private communication network that may be received by the mobile terminal 100. For example, Traffic Message Channel (TMC) data is available in a number of cities throughout North America and Europe. TMC data is broadcast continuously on FM radio channels, and may provide notification of accidents, road construction, police, or emergency action, etc. [0050]Traffic information obtained by the traffic information unit 148 may be used by the controller 126 to determine estimated travel times and/or route information for a user of the mobile terminal 100. [0051]The mobile terminal 100 may further include a map database 150 that contains map information concerning a geographic area in which the mobile terminal 100 is located, and/or in which a destination point is located. For example, the map database 150 may contain street/road information and/or may contain map information for other areas, such as pedestrian walking areas. The map information may further include information regarding features, such as buildings, fences, rivers, etc., that may constrain the motion of a user of the mobile terminal 100. [0052]Although the map database 150 is shown as a component of the terminal 102, it will be appreciated that the map database 150, and/or a portion of the map database 150, may be located remotely from the mobile terminal 100. For example, the map database 150 may be stored remotely and accessed through the communication module 128. A portion of the map database 150 may be retrieved and stored locally at the mobile terminal 100. Remote storage of the map database 150 may be desirable, since memory storage space in the mobile terminal 100 may be limited, and a map database may consume a significant amount of memory. In some embodiments, the map database 150 may be stored at a map server 200A, 200B. [0053]Referring to FIG. 4B, the user interface 122 can include an input device 134, such as a keypad 16, multifunction key 22, keyboard, touchpad, jog dial and/or other user input device. The user interface 122 may further include a primary display screen 18, such as an LCD display that is capable of displaying video signals in a video format, such as Quarter VGA (QVGA, 320×240 pixels), Common Intermediate Format (CIF, 360×288 pixels) and/or Quarter Common Intermediate Format (QCIF, 180×144 pixels). The mobile terminal 100 may include appropriate CODECs to permit the mobile terminal 100 to decode and display video signals in various formats. A secondary display screen 28 may also be provided. [0054]The user interface 122 can also include an audio interface unit including a microphone 14 coupled to an audio processor that is configured to generate an audio signal responsive to sound incident on the microphone, and a speaker 20 that generates sound responsive to an output audio signal. [0055]According to some embodiments, a navigational aid, such as a map, may be displayed on the primary display screen 18 and/or the secondary display screen 28. Furthermore, alerts and or navigational information may be communicated to a user of the mobile terminal 100 through the audio interface. [0056]Some aspects of a map server 200A according to some embodiments of the invention are illustrated in FIG. 5. As shown therein, a map server 200A may include a position/velocity determination unit 246 and a traffic information unit 248. The position/velocity determination unit 246 and the traffic information unit 248 may communicate with the communication module 228 through the controller 226 as shown in FIG. 5. Alternatively or additionally, the position/velocity determination unit 246 and/or the traffic information unit 248 may communicate directly with the communication module 228, for example through a system bus. [0057]According to some embodiments, the position/velocity determination unit 246 may be configured to determine a current position and/or velocity of a remotely located mobile terminal 100. For example, the position/velocity determination unit 246 may receive global positioning system (GPS) information from the mobile terminal 100 that permits the position/velocity determination unit 246 to determine the location of the mobile terminal 100 with a high degree of precision. The position/velocity determination unit 246 may include other systems and/or functionality for determining the location of the mobile terminal 100. For example, the position/velocity determination unit 246 may be configured to obtain location information for the mobile terminal 100 from a cellular communications network on which the mobile terminal 100 is registered. [0058]The traffic information unit 248 is configured to obtain information about current automobile and/or pedestrian traffic in or near a location at which the mobile terminal 100 is located and/or near a destination point, or along a route from a current location of the mobile terminal 100 to a destination point. [0059]Traffic information obtained by the traffic information unit 248 may be used by the controller 226 to determine estimated travel times and/or route information for a user of the mobile terminal 100. [0060]The map server 200 may further include a map database 250 that contains map information concerning a wide geographic area in which the mobile terminal 100 may be located. For example, the map database 250 may contain street/road information and/or may contain map information for other areas, such as pedestrian walking areas. The map information may further include information regarding features, such as buildings, fences, rivers, etc., that may constrain the motion of a user of the mobile terminal 100. [0061]According to some embodiments, a position of a mobile terminal 100 is determined. In some embodiments, the position of the mobile telephone may be determined by the position/velocity determination unit 146. In other embodiments, the position of the mobile terminal 100 may be determined by an element in the network 10 (FIG. 3). For example, the position of the mobile telephone may be determined by map server 200A or 200B. [0062]The mobile terminal 100 and/or the map server 200A, 200B may then determine if the estimated current position of the mobile terminal 100 is within a boundary of geographic map information stored in the mobile terminal 100, e.g. within a boundary of a map stored in short term memory, such as within the memory 125 (e.g. a RAM cache) and/or stored in the map database 150. If the current position of the mobile terminal 100 is within the boundary of the stored geographic map information, the mobile terminal 100 may display a map including the current position of the mobile terminal 100 on its primary display 18 and/or secondary display 28. [0063]If the current position of the mobile terminal 100 is not within the boundary of the geographic map information stored in the mobile terminal 100, geographic map information including the current position of the mobile terminal 100 may be retrieved by the mobile terminal 100 and/or pushed to the mobile terminal 100 from the map server 200A, 200B using the communication module 128. Thus, in some embodiments, it may not be necessary for the mobile terminal 100 to store large amounts of map information locally in the map database 150. Instead, the mobile terminal 100 may be able to download only the map information needed to be displayed at a given time. Old and/or unused map information may be stored locally, e.g. wit(String), 发明领域 [0001] 无线 通信终端技术领域本发明涉及无线通信终端,更具体地,涉及包括能够显示地图信息的显示屏的无线通信终端。 背景 [0002] 无线通信终端主要用于通过蜂窝电话网络获得对无线电话服务的访问。 然而,随着无线通信终端的能力增加,附加级别的用户功能被包括在这样的终端的硬件和/或软件中。 例如,通信终端可以配备静态和/或摄像机,允许用户拍摄照片和/或视频并从移动终端传输给其他人。 同样,许多通信终端包括适用于跟踪和管理日程、任务等的个人数字助理(PDA)类型的应用程序。 许多通信终端还包括消息传递能力,例如电子邮件(e-mail)、短消息服务(SMS)和多媒体消息服务(MMS)能力。 通信终端也能够通过使用互联网协议(IP)在无线和/或有线网络上连接到互联网。 [0003] 通信终端也越来越多地具有确定终端物理位置的能力。 例如,许多通信终端包括允许终端以高精度确定它们的位置的全球定位系统(GPS)接收器。 已经实现了用于确定通信终端位置的其他系统,包括从蜂窝通信网络获取位置信息的系统,以及通过惯性引导技术获取位置信息的系统。 [0004] 此外,一些无线网络能够确定注册到系统的终端的大致位置。 这样的位置信息可以用于例如在使用终端呼叫紧急帮助时向紧急操作员提供位置信息。 概括 [0005] 根据本发明的一些实施例的方法包括估计包括通信模块和显示屏的移动终端的当前地理位置,以及确定估计的移动终端的当前位置是否在移动终端中存储的地理地图信息的边界内。 终端。 如果移动终端的当前位置在存储的地理地图信息的边界内,则在显示器上显示包括移动终端的当前位置的地图。 如果移动终端的当前位置不在存储的地理地图信息的边界内,则使用通信模块向移动终端提供包括移动终端的当前位置的附加地理地图信息。 [0006] 该方法还可以包括确定地图的当前比例,以及确定存储的地图信息是否包含足够的地图信息来以当前比例填充显示屏。 如果存储的地图信息没有包含足够的地图信息来以当前比例填充显示屏幕,则可以缩小显示屏幕的比例直到存储的地图信息足以以缩小的比例填充显示屏幕。 [0007] 该方法还可以包括使用足以以当前比例填满显示屏幕的通信模块来检索附加地图信息,并且在已经检索到附加地图信息之后,将比例增加到当前比例。 [0008] 该方法还可以包括通过估计移动终端的当前速度并响应于移动终端的当前速度选择显示比例来确定显示屏幕的当前比例。 确定当前比例可以包括如果移动终端的速度较高则选择相对较大的比例并且如果移动终端的速度较小则选择较小的比例。 [0009]该方法还可以包括估计移动终端的当前行进速度和方向,并且响应于移动终端的当前行进速度和方向来估计移动终端将何时离开存储的地图信息所描述的区域。 [0010] 该方法还可以包括估计为移动终端正前往的地理区域下载附加地图信息所需的时间量,以及在移动终端离开存储的地图信息所描述的区域之前下载附加地图信息。 [0011] 估计移动终端的当前位置可以由远程服务器响应于网络生成的位置信息来执行。 该方法还可以包括如果移动终端的当前位置不在存储的地理地图信息的边界内则从远程服务器向移动终端发送附加地图信息。 [0012] 在显示器上显示包括移动终端的当前位置的地图可以包括在移动终端未使用预定时间段之后在显示器上显示地图。 [0013] 移动终端还可以包括在设备的翻盖部分上的副显示屏,该副显示屏可在打开位置和闭合位置之间移动,使得副显示屏在翻盖部分处于闭合位置时可见。 该方法可以包括当翻盖部分处于关闭位置时在辅助显示器上显示包括移动终端的当前位置的地图。 [0014] 该方法还可以包括确定移动终端已经进入空闲模式,并且降低显示器的亮度和/或关闭显示器。 估计移动终端的当前地理位置并判断估计的移动终端的当前位置是否在移动终端存储的地理地图信息的边界内可以在移动终端处于空闲模式时执行。 此外,可以在移动终端处于空闲模式时执行使用通信模块向移动终端提供附加地理地图信息。 [0015] 根据本发明一些实施例的移动终端包括通信模块、显示屏和控制电路。 该电路被配置为估计移动终端的当前地理位置,并确定估计的移动终端的当前位置是否在存储在移动终端中的地理地图信息的边界内。 该电路还被配置为如果移动终端的当前位置在所存储的地理地图信息的边界内则在显示器上显示包括移动终端的当前位置的地图,并且检索包括当前位置的附加地理地图信息 如果移动终端的当前位置不在存储的地理地图信息的边界内,则移动终端使用通信模块。 [0016] 该电路还可以被配置为确定地图的当前比例,以确定存储的地图信息是否包含足够的地图信息以在当前比例下填充显示屏,以及减小显示屏的比例直到存储的地图信息 如果存储的地图信息不包含足够的地图信息来以当前比例填充显示屏幕,则足以以缩小的比例填充显示屏幕。 [0017] 该电路还可以被配置为使用通信模块检索附加地图信息,并且在已经检索到附加地图信息之后将比例尺增加到大于缩小比例尺的增加比例尺。 [0018] 该电路还可以被配置为通过估计移动终端的当前速度来确定显示屏幕的当前比例,并且响应于移动终端的当前速度来选择显示比例。 [0019]该电路还可以被配置为估计移动终端的当前行进速度和方向,并且响应于移动终端的当前行进速度和方向,估计移动终端何时将离开由 存储的地图信息。 该电路还可以被配置为估计下载移动终端正前往的地理区域的附加地图信息以及在移动终端离开所存储的地图信息所描述的区域之前下载附加地图信息所需的时间量 . [0020] 根据本发明一些实施例的地图服务器包括被配置为与位于远程的移动终端通信的通信模块、被配置为为移动终端估计位置/速度信息的位置/速度确定单元、存储地图信息的数据库、以及 电路被配置为确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内,并且如果是则使用通信模块从数据库发送包括移动终端的当前位置的附加地理地图信息 移动终端当前位置不在存储的地图信息范围内。 [0021] 位置/速度确定单元可以被配置为使用由移动终端在其中注册的通信网络提供的位置信息来估计移动终端的当前位置。 [0022] 该电路还可以被配置为使用移动终端的位置/速度来估计移动终端何时将离开存储在移动终端处的地图信息所描述的区域,以估计下载附加地图信息所需的时间量 移动终端正前往的地理区域,并且在移动终端离开存储在移动终端处的地图信息所描述的区域之前将附加地图信息发送到移动终端。 附图的简要说明 [0023] 包括的附图是为了提供对本发明的进一步理解并且并入本申请并构成本申请的一部分,图示了本发明的某些实施例。 在图纸中: [0024] 图1图示了根据本发明一些实施例的电子设备。 [0025] 图2A-2B示出了根据本发明一些实施例的翻盖式移动电话。 [0026] 图3是图示根据本发明的一些实施例的电子设备和蜂窝通信系统的示意性框图。 [0027] 图4A和4B是图示根据本发明一些实施例的电子设备的一些方面的示意性框图。 [0028] 图5是示出根据本发明一些实施例的地图服务器的示意性框图。 [0029] 图6A, 6 乙, 7 一种, 7 乐队 7 C是根据本发明的一些实施例配置的显示屏的示例性图示。 [0030] 图8-11是说明根据本发明一些实施例的电子设备的操作的流程图。 具体实施方式的详细说明 [0031] 现在将参考附图更全面地描述本发明,在附图中示出了本发明的实施例。 然而,本发明不应被解释为限于在此阐述的实施例。 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明的范围充分地传达给本领域的技术人员。 相同的数字始终指代相同的元素。 如本文所用,术语“包括”或“包括”是开放式的,并且包括一个或多个规定的要素、步骤和/或功能而不排除一个或多个未规定的要素、步骤和/或功能。 如本文所用,术语“和/或”包括一个或多个关联列出的项目的任何和所有组合。 [0032] 参照方框图和/或方法和通信终端的操作说明来描述根据本发明的实施例。 应当理解,方框图和/或操作说明的每个方框,以及方框图和/或操作说明中方框的组合,可以通过射频、模拟和/或数字硬件、和/或程序来实现 指示。 这些程序指令可以提供给控制器,该控制器可以包括一个或多个通用处理器、专用处理器、ASIC和/或其他可编程数据处理装置,使得经由控制器和/或其他可编程数据处理装置执行的指令 数据处理设备,创建用于实现框图和/或操作块中指定的功能/动作的装置。 在一些实施方式中,块中标注的功能/动作可能不按操作说明中标注的顺序发生。 例如,连续显示的两个块实际上可以基本上同时执行,或者这些块有时可以以相反的顺序执行,这取决于所涉及的功能/动作。 [0033] 如本文所用,“通信终端”(或简称为“终端”)包括但不限于配置为通过有线连接(例如通过公共交换电话网络)接收/发送通信信号的设备 (PSTN)、数字用户线 (DSL)、数字电缆、直接电缆连接和/或另一个数据连接/网络,和/或通过无线接口与例如蜂窝网络、无线局域网( WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM/FM广播发射机和/或另一个通信终端。 被配置为通过无线接口进行通信的通信终端可以称为“无线通信终端”、“无线终端”和/或“移动终端”。 移动终端的示例包括但不限于卫星或蜂窝无线电话; 个人通信系统 (PCS) 终端,可将蜂窝无线电话与数据处理、传真和数据通信功能相结合; 可包括无线电话、寻呼机、互联网/内联网访问、Web 浏览器、管理器、日历和/或全球定位系统 (GPS) 接收器的 PDA; 以及包括无线电话收发器的常规膝上型和/或掌上型接收器或其他器具。 [0034] 电子设备之间的无线通信可以使用各种各样的通信媒体、通信系统和通信标准来实现。 例如,诸如无线移动电话的移动终端通常被配置为通过模拟和/或数字无线射频(RF)电话系统进行通信。 此类设备还可配置为使用有线和/或无线局域网 (LAN)、短程通信信道(例如蓝牙 RF 通信信道和/或红外通信信道)和/或远程通信系统(例如卫星)进行通信 通信系统。 [0035] 根据本发明实施例的诸如无线移动电话的移动终端可以具有多种形状、尺寸和外壳类型。 几种类型的移动电话外壳的示例在图1至2B中示出。 比如移动端 100 图 1 中图示了根据一些实施例的移动终端 100 A包括外壳 15 容纳和保护移动终端的电子设备 100 A.移动端 100 A包括一个LCD显示器 18 和一个键盘 16 . 移动端 100 A还包括一个多功能控制/输入按钮 22 可用于选择菜单项和/或向移动终端输入命令 100 一种。 [0036] 移动端 100 A包括一个麦克风端口 14 和耳机/扬声器 20 . 住房 15 可以设计成当耳机/扬声器与用户的耳朵形成声学密封 20 被放置在用户的头部。 移动端 100A可以被配置为播放视频文件和/或音频文件,例如歌曲文件,它们可以是立体声信号。 [0037] 翻盖式移动终端 100 B如图2A和2B所示。 翻盖式移动终端 100 B在图2A中显示为打开位置,在图2B中显示为关闭位置。 移动端 100 B包括外壳 15 包括一个较低的住房 15 A 和上部外壳,或“翻盖”部分 15 B 通过铰链可旋转地连接 24 . 移动端 100 B 包括一个主 LCD 显示屏 18 在翻盖内侧 15 B 和键盘 16 在下部外壳的内侧 15 A.移动端 100 B还包括一个多功能控制/输入按钮 22 . [0038] 移动端 100 A包括一个麦克风端口 14 在较低的外壳上 15 A和耳机/扬声器 20 在翻盖内侧 15 B. 如图 2B 所示,辅助显示 28 和一个相机镜头 30 可能位于翻盖的外侧 15 B. [0039] 图3是无线通信系统的示意框图 10 其中包括一个移动终端 100 配置为与地图服务器通信 200 一种, 200 B. 例如移动端 100 可以与地图服务器通信 200 A 通过直接无线通信接口 106 , 通过另一个无线通信接口 108 通过一个或多个蜂窝基站 110 a - b ,和/或通过另一个无线通信接口 112 通过无线局域网 (WLAN) 接入点 114 . 直接无线通讯接口 106 可以包括RF无线通信接口,例如蓝牙接口或红外通信接口,例如由红外数据协会(IRDA)协议定义的红外通信接口。 IRDA 定义了许多红外无线数据通信标准,包括数据速率高达 16 Mb/s 的红外无线通信标准。 可以理解,移动终端 100 可以是手持无线通信终端,例如手机、PDA等。 [0040] 如图 3 进一步所示,移动终端 100 可以包括用户界面 122 , 一个控制器 126 , 通信模块 128 , 和记忆 125 . [0041] 通信模块 128 被配置为通过一个或多个无线接口传送数据 106 , 108 , 和/或 112 到另一个远程终端或其他通信设备,例如地图服务器 200 一种, 200 B、记忆 125 被配置为存储供控制器使用的程序和/或数据 126 . 记忆 125 可能包括一个非易失性存储器,即使在移动终端通电时也能存储数字信息 100 已关闭。 [0042] 通信模块 128 可以包括例如蜂窝通信模块、蓝牙模块、红外通信模块和/或WLAN模块。 带有蜂窝通信模块的移动终端 100 可以通过基站进行通信 110 a - b 使用一种或多种蜂窝通信协议,例如高级移动电话服务 (AMPS)、ANSI-136、全球移动标准 (GSM) 通信、通用分组无线服务 (GPRS)、增强数据速率的 GSM 演进 (EDGE) )、码分多址 (CDMA)、宽带 CDMA、CDMA2000 和通用移动电信系统 (UMTS)。 蜂窝基站 110 a - b 可以连接到移动电话交换局 (MTSO) 116 ,这反过来又可以连接到一个或多个其他网络 118 (例如互联网、公共交换电话网络和/或其他网络)。 带有蓝牙或红外模块,移动终端 100可以使用直接接口通过临时网络进行通信 106 . 带有WLAN模块,移动终端 100 可以通过WLAN路由器进行通信 114 使用的通信协议可能包括但不限于 802.11a、802.11b、802.11e、802.11g 和/或 802.11i。 移动电话也可以配置为直接通过网络通信 118 . [0043] 移动端 100 可以被配置为向/从另一个通信终端发送和/或接收数字数据信号,该另一个通信终端可以通过例如MTSO与其通信耦合 116 , 和/或另一个网络 118 ,例如公共交换电话网 (PSTN)。 然而,从前面的描述中可以理解,移动终端之间的数据通信 100 无需使用 MTSO 即可完成另一个终端 116 或其他网络 118 . [0044] 移动端 100 我还包括 AM/FM 无线电调谐器、UHF/VHF 调谐器、卫星无线电调谐器、DVB-H 接收器和/或配置为接收广播音频/视频信号和/或数据信号的另一个接收器。 [0045] 地图服务器 200 A可以是独立的服务器,配置为与移动终端通信 100 通过无线通信链路,例如 WLAN 通信链路 112 ,一个直接的无线通信链路 106 ,和/或另一个无线通信接口 108 通过一个或多个蜂窝基站 110 a - b . 例如,地图服务器 200 A 可以配置为通过无线通信链路广播包括地图信息的数据信号 106 到移动终端,比如移动终端 100 , 在一个地理服务区内。 即地图服务器 200 A可以向移动终端广播特定地理区域的地图,例如移动终端 100 , 在地理区域内。 在一些实施例中,无线通信链路 106 可以是单向通信链路,地图可以通过单向无线通信链路广播 106 盲目地,即不了解任何移动终端 100 地理区域内。 在其他实施例中,无线通信链路 106 可以是单向通信链路,地图信息可以按需广播或以其他方式传输到请求移动终端 100 响应通过单独的通信链路(例如 WLAN 通信链路)收到的请求 112 和/或蜂窝通信链路 108 . [0046] 地图服务器 200 B 可以位于移动电话交换局 (MTSO) 内或由其控制 116 ,在这种情况下,地图服务器 200 B可与无线电话通话 100 主要使用无线通信接口 108 . [0047] 移动终端的一些进一步方面 100 根据本发明的一些实施例,在图4A和4B中示出。 如图所示,移动终端 100 可以进一步包括位置/速度确定单元 146 和一个交通信息单元 148 . 位置/速度确定单元 146 和交通信息单元 148 可与通讯模块通讯 128 通过控制器 126 如图 3 所示。可替代地或附加地,位置/速度确定单元 146 和/或交通信息单元 148 可直接与通讯模块通讯 128 ,例如通过系统总线。 [0048] 根据一些实施例,位置/速度确定单元 146 可以被配置为确定移动终端的当前位置和/或速度 100 . 例如,位置/速度确定单元 146 可能包括允许位置/速度确定单元的全球定位系统 (GPS) 接收器 146 确定移动终端的位置 100 具有高精度。 位置/速度确定单元146 可以包括用于确定移动终端位置的其他系统和/或功能 100 . 例如,位置/速度确定单元 146 可以配置为获取移动终端的位置信息 100 来自移动终端所使用的蜂窝通信网络 100 沟通。 位置/速度确定单元 146 可以额外地或替代地包括允许位置/速度确定单元的惯性制导系统 146 确定移动终端的位置/速度 100 通过已知位置的惯性运动。 [0049] 交通信息单元 148 被配置为获取关于移动终端所在位置或其附近的当前汽车和/或行人交通的信息 100 位于和/或靠近目的地点,或沿着移动终端当前位置的路线 100 到一个目的地点。 例如,可以在移动终端可以接收的公共和/或专用通信网络的一个或多个数据子信道中广播交通信息 100 . 例如,交通信息频道 (TMC) 数据在北美和欧洲的许多城市都可用。 TMC 数据在 FM 无线电频道上连续广播,并可能提供事故、道路施工、警察或紧急行动等通知。 [0050] 交通信息单元获取的交通信息 148 可以被控制器使用 126 为移动终端的用户确定估计的旅行时间和/或路线信息 100 . [0051] 移动端 100 可能还包括地图数据库 150 包含有关移动终端所在地理区域的地图信息 100 位于,和/或目标点位于其中。 比如地图数据库 150 可能包含街道/道路信息和/或可能包含其他区域的地图信息,例如步行区。 地图信息还可以包括关于可能限制移动终端的用户的运动的特征的信息,例如建筑物、栅栏、河流等 100 . [0052] 虽然地图数据库 150 显示为终端的一个组件 102 , 将会理解地图数据库 150 和/或地图数据库的一部分 150 , 可能位于远离移动终端的地方 100 . 比如地图数据库 150 可远程存储并通过通信模块访问 128 . 地图数据库的一部分 150 可以在移动终端本地检索和存储 100 . 地图数据库远程存储 150 可能是可取的,因为移动终端中的内存存储空间 100 可能是有限的,并且地图数据库可能会消耗大量内存。 在一些实施例中,地图数据库 150 可以存储在地图服务器上 200 一种, 200 B. [0053] 参考图 4B,用户界面 122 可以包括一个输入设备 134 , 比如键盘 16 , 多功能键 22 、键盘、触摸板、滚轮和/或其他用户输入设备。 用户界面 122 还可以包括主显示屏 18 ,例如能够以视频格式显示视频信号的 LCD 显示器,例如四分之一 VGA(QVGA,320×240 像素)、通用中间格式(CIF,360×288 像素)和/或四分之一通用中间格式( QCIF,180×144 像素)。 移动端 100 可能包括适当的编解码器以允许移动终端 100 解码和显示各种格式的视频信号。 副显示屏 28 也可以提供。 [0054] 用户界面 122 还可以包括一个音频接口单元,包括一个麦克风 14 耦合到音频处理器和扬声器,音频处理器被配置为响应于入射在麦克风上的声音而生成音频信号 20 产生响应于输出音频信号的声音。 [0055]根据一些实施例,可以在主显示屏上显示诸如地图的导航帮助 18 和/或辅助显示屏 28 . 此外,可以将警报和/或导航信息传送给移动终端的用户 100 通过音频接口。 [0056] 地图服务器的某些方面 200 图 5 中说明了根据本发明的一些实施例。如其中所示,地图服务器 200 A可以包括位置/速度确定单元 246 和一个交通信息单元 248 . 位置/速度确定单元 246 和交通信息单元 248 可与通讯模块通讯 228 通过控制器 226 如图5所示。可替代地或附加地,位置/速度确定单元 246 和/或交通信息单元 248 可直接与通讯模块通讯 228 ,例如通过系统总线。 [0057] 根据一些实施例,位置/速度确定单元 246 可以被配置为确定远程移动终端的当前位置和/或速度 100 . 例如,位置/速度确定单元 246 可以从移动终端接收全球定位系统(GPS)信息 100 允许位置/速度确定单元 246 确定移动终端的位置 100 具有高精度。 位置/速度确定单元 246 可以包括用于确定移动终端位置的其他系统和/或功能 100 . 例如,位置/速度确定单元 246 可以配置为获取移动终端的位置信息 100 来自移动终端所在的蜂窝通信网络 100 已登记。 [0058] 交通信息单元 248 被配置为获取关于移动终端所在位置或其附近的当前汽车和/或行人交通的信息 100 位于和/或靠近目的地点,或沿着移动终端当前位置的路线 100 到一个目的地点。 [0059] 交通信息单元获取的交通信息 248 可以被控制器使用 226 为移动终端的用户确定估计的旅行时间和/或路线信息 100 . [0060] 地图服务器 200 可能还包括地图数据库 250 包含有关移动终端所在广阔地理区域的地图信息 100 可能位于。 比如地图数据库 250 可能包含街道/道路信息和/或可能包含其他区域的地图信息,例如步行区。 地图信息还可以包括关于可能限制移动终端的用户的运动的特征的信息,例如建筑物、栅栏、河流等 100 . [0061] 根据一些实施例,移动终端的位置 100 决心,决意,决定。 在一些实施例中,移动电话的位置可以由位置/速度确定单元确定 146 . 在其他实施例中,移动终端的位置 100 可能由网络中的元素决定 10 (图 3)。 例如,移动电话的位置可以由地图服务器确定 200 一个或 200 B. [0062] 移动端 100 和/或地图服务器 200 一种, 200 B然后可以确定移动终端的估计的当前位置是否 100 在移动终端存储的地理地图信息的边界内 100 ,例如 在存储在短期记忆中的地图的边界内,例如在内存中 125 (例如 RAM 缓存)和/或存储在地图数据库中 150 . 如果移动端当前位置 100 在存储的地理地图信息的边界内,移动终端 100 可以显示包含移动终端当前位置的地图 100在其主显示屏上 18 和/或辅助显示器 28 . [0063] 如果移动端当前位置 100 不在移动终端存储的地理地图信息范围内 100 ,包括移动终端当前位置的地理地图信息 100 可通过移动端检索 100 和/或推送到移动端 100 从地图服务器 200 一种, 200 B 使用通信模块 128 . 因此,在一些实施例中,移动终端可能不需要 100 在本地地图数据库中存储大量地图信息 150 . 取而代之的是移动端 100 可以只下载给定时间需要显示的地图信息。 旧的和/或未使用的地图信息可以存储在本地,例如 在记忆中 125 和/或地图数据库 150 , 但可能会根据需要删除,以便为更新的地图信息提供空间。 [0064] 此外,移动终端当前位置的地图 100 可以在主显示器上连续显示,例如作为屏幕保护程序或背景 18 或辅助显示 28 ,这样用户就可以很容易地获得地图信息,而不必选择菜单项、按键或以其他方式发出显示当前地图的命令。 [0065] 移动端 100 当移动终端没有连接到外部电源时,可以配置为在一段时间不活动之后进入空闲模式或电池节省模式以保存电池电量。 进入闲置或省电模式后,主显示屏 18 和/或辅助显示器 28 可以调暗和/或可以关闭背光,但移动终端 100 可能会继续跟踪和更新其位置/速度。 在一些实施例中,主显示器 18 和/或辅助显示器 28 可以关闭,但是移动端的位置/速度 100 仍然可以计算,并且可以根据需要下载新的地图信息。 当移动终端“醒来”时(例如,当用户按下按钮时),新位置可以在显示屏上轻松快速地更新,而无需用户等待位置更新和/或新地图信息的下载。 [0066] 根据本发明的实施例的样本显示图像如图 6A-6B 所示, 7 一种- 7 B.例如,图6A图示了地图图像 120 可能会显示在主显示器上 18 和/或辅助显示器 28 移动终端的 100 . 移动终端的位置 100 由图标指示 140 可以指示移动终端的位置和行进方向 100 . 在图 6A 所示的显示中,图标 140 位于显示屏中央,其中还包括一个图标 142 指示北方方向,以及比例指示器 144 显示每单位显示屏的距离。 在所示示例中,比例尺为每单位 1 公里。 可以使用其他比例指示器。 例如,可以在显示器上叠加一个网格图案,每个网格分区代表一个特定的距离(例如 1 公里、100 米等)。 [0067] 显示地图图像 120 , 地图数据库 150 移动端 100 包括地图图像中显示的整个区域的地图信息 120 . 另外,地图数据库 150 可能包含其他区域的地图信息,例如地图图像中显示的区域周围的区域 120 . 地图数据库中存储的附加地图信息 150 移动端 100 但当前未显示在图 6A 中显示为区域 132 以虚线显示。 作为移动端 100 移动,地图图像 120 也可以移动保持图标 140 对应移动端 100 以地图图像为中心 120 . [0068] 当移动端 100靠近地图数据库中存储的地图信息的边缘或边界 150 , 移动端 100 可以从地图服务器下载额外的地图信息 200 一种, 200 B、例如,如图6B所示,移动终端 100 100 , 如图标所示 140 , 已经移动到显示图像的边缘 120 已到达地图信息的边缘 132 存储在地图数据库中 150 移动端 100 . 参考图 7A,附加地图信息 134 可以从地图服务器下载 200 一种, 200 B 为移动终端进入的区域 100 正在移动。 [0069] 在一些实施例中,附加的地图信息可以被下载到移动终端 100 在移动端之前 100 移动到如此靠近地图信息的边缘或边界 132 存储在地图数据库中 150 即移动端 100 将用完地图信息以显示在显示屏上 18 , 28 在目前的规模。 但是,如果由于某些原因,例如网络拥塞和/或地图服务器不可用 200 一种, 200 B、移动端 100 无法检索到足够的地图信息 132 以当前比例显示全屏,移动端 100 可以更改地图的显示比例,以便存储的地图信息继续显示在屏幕上。 例如,如图7B所示,作为移动终端 100 移动到存储的地图信息的边缘 132 , 尺度缩小为每单位 500 m。 或者,如果移动终端 100 无法检索到足够的附加地图信息 134 以当前比例显示全屏,移动端 100 可以保持当前比例并移动图标 140 代表移动端 100 偏离显示图像的中心 120 如图7C所示直到附加地图信息 134 已下载。 [0070] 因此,本发明的一些实施例可以包括确定地图的当前比例,以及确定存储的地图信息是否包含足够的地图信息来以当前比例填充显示屏。 如果存储的地图信息没有包含足够的地图信息以填充当前比例尺的显示屏幕,则可以缩小显示屏幕的比例尺直到存储的地图信息足以以缩小的比例尺填充显示屏幕,并且地图 可能会显示在显示屏上 18 , 28 缩小比例,或图标 140 代表移动端 100 可能会远离显示器的中心 120 . [0071] 从地图服务器下载附加地图信息后 200 一种, 200 B,比例可能会增加(例如,显示的比例可能会增加到以前的比例)和/或图标 140 可以移回显示的中心。 [0072] 一些实施例可以估计移动终端的当前行进速度和方向 100 并估计,响应于移动终端当前的行进速度和方向 100 , 当移动端 100 将离开存储的地图信息描述的区域 132 . 移动终端所在的位置 100 将离开存储的地图信息所描述的区域 132 可根据道路位置、移动终端当前速度和方向进行预测 100 、拥堵/交通状况和/或其他因素。 为移动终端下载某个地理区域的附加地图信息所需的时间量 100 可以预估正在前往的方向,可以在移动终端之前下载附加地图信息 100 离开存储的地图信息所描述的区域。 这样,移动终端所在区域的地图 100 位置可以在移动端无缝显示 100 移动到以前没有地图信息的区域。 [0073] 在一些实施例中,可以响应于移动终端的速度来设置显示的比例 100 . 例如,在低速时,可以使用较低的刻度,而在高速时,可以使用较高的刻度。 例如,在高速下,可以使用诸如每单位1公里或更高的比例,而在较低速度下,可以使用小于每单位1公里的比例。 [0074] 估计移动终端的当前位置 100 可由移动终端执行 100 和/或可以由远程服务器执行,例如地图服务器 200 一种, 200 B、响应网络生成的位置信息。 [0075] 在一些实施例中,地图包括移动终端的当前位置 100 可能会显示在主显示屏上 18 和/或辅助显示器 28 在预定的不使用移动终端的时间之后 100 ,例如 作为屏幕保护程序或默认图像。 [0076] 在一些实施例中,移动终端 100 可能包括一个辅助显示屏 28 在可在打开位置和关闭位置之间移动的翻盖部分上,以便副显示屏 28 当翻盖部分处于关闭位置时,如图 2A 和 2B 所示,可见。 在那种情况下,地图包括移动终端的当前位置 100 当翻盖部分处于关闭位置时,可以在副显示器上显示。 [0077] 图8-10是说明根据本发明一些实施例的电子设备的操作的流程图。 例如,如图8的流程图所示,根据一些实施例,诸如移动终端的设备的位置 100 ,估计(块 205 ). 如上所述,设备的位置 100 可以由设备本身使用 GPS 定位、惯性导航或任何其他合适的技术来估计。 设备的位置 100 也可以由例如远程服务器确定,例如地图服务器 200 一种, 200 B 使用基于网络的定位技术和/或使用移动终端提供的信息 100 . [0078] 在座 210 ,确定移动终端是否 100 位于移动终端本地存储的地图信息所描述的区域内 100 , 比如在地图数据库中 150 移动端 100 . [0079] 如果设备 100 位于移动终端本地存储的地图信息所描述的区域 100 ,地图显示在移动终端的屏幕上 100 , 如主显示器 18 和/或辅助显示器 28 (堵塞 220 ). [0080] 但是,如果设备不在本地存储的地图信息所描述的区域(即设备 100 没有其当前位置的地图),则可以获得额外的地图信息(块 215 ). 附加地图信息可以从远程服务器下载,例如地图服务器 200 一种, 200 B、和/或附加地图信息可以从远程服务器推送,例如地图服务器 200 一种, 200 B、到移动端 100 , 没有先接收到来自移动端的请求 100 . 一旦移动终端接收到附加地图数据 100 ,地图可以显示在移动终端的屏幕上 100 , 如主屏幕 18 和/或辅助屏幕 28 . [0081] 图 9 的流程图中说明了本发明的进一步实施例。如其中所示,在方框 305 移动终端屏幕显示地图信息的默认比例尺 100 决心,决意,决定。 接下来检查移动终端本地存储的地图信息是否 100 , 比如在地图数据库中 150 移动端 100 , 足以以默认比例显示全屏信息(块 310 ). 如果是,则地图显示在屏幕上(块 320 ). [0082]但是,如果本地存储的地图信息不足以显示全屏,则可能会缩小显示比例和/或图标 140 代表移动端 100 可以从显示图像的中心移开 120 (堵塞 315 ) 直到本地存储了足够数量的地图信息以允许全屏显示(块 310 ). 然后地图可以修改后的(缩小的)比例尺(方块)显示在显示屏上 320 ). [0083] 在 Block 进行支票 325 查看比例是否缩小或图标是否 140 被转移到街区 315 . 如果是这样,可以将额外的地图数据下载到移动终端 100 (根据要求或推送到移动端 100 ) (堵塞 330 ). 然后可以增加显示的比例,例如增加到默认比例,和/或图标 140 可以移回显示图像的中心 120 (堵塞 335 ). [0084] 本发明的进一步实施例在图10的流程图中示出。如图所示,在一些实施例中,移动终端 100 可以显示一个地图,显示移动终端的位置 100 在当前规模(块 405 ). 移动终端何时产生估计 100 将留下移动终端本地存储的地图信息覆盖的区域 100 ,例如在地图数据库中 150 (堵塞 415 ). 该估计可以基于诸如移动终端的速度和方向等因素 100 、道路、桥梁、路口等位置,可影响移动终端用户当前路线的出行时间、交通/拥堵 100 , ETC。 [0085] 还可以估计用于下载额外地图数据的时间量(块 420 ). 可将附加地图数据传输至移动终端 100 就在移动终端之前 100 离开存储的地图数据的区域(块 425 ). 因此,可以延迟附加地图数据的下载,直到实际需要该数据为止。 这可以潜在地避免下载不需要的地图信息。 [0086] 图 11 中说明了本发明的其他实施例。如其中所示,在方框 510 , 移动终端的位置 100 使用例如图8所示的操作更新并显示在显示屏上。检查移动终端是否 100 已进入空闲或节电模式(块 520 ). 如果没有,移动端 100 继续更新并显示其所描述的位置。 [0087] 如果移动端 100 已进入空闲或省电模式,移动终端的显示屏幕 100 可以调暗(例如,通过降低背光亮度或完全关闭背光)或完全关闭(阻止 530 ). 但是,移动端 100 可能会继续估计其位置(块 540 ) 并确定其位置是否在存储的地图信息覆盖的区域内(块 550 ). 如果没有,则移动终端可以获得额外的地图信息(Block 560 ) 覆盖移动终端所在的地理区域 100 位于。 [0088] 移动端 100 然后确定它是否已经退出空闲或电池节能模式(块 570 ), 如果是,则显示包含移动终端当前位置的地图 100 在显示屏上(块 580 ). 否则,操作返回阻塞 540 ,并且移动终端继续估计它的位置。 [0089] 已经参考图8-11部分地描述了本发明,图8-11是说明根据本发明的方面的示例性操作的流程图图示。 将理解,图8-11的流程图的块以及流程图中块的组合可以使用包括在诸如移动终端的终端中的电子电路来实现 100. 还应当理解,图 8-11 的流程图的块以及流程图中的块的组合可以使用不同于图 1 到 5 中所示的组件来实现,并且通常, 图8-11的流程图图示和流程图图示中的块的组合,可以在诸如分立模拟和/或数字电路的专用硬件中实现,诸如集成电路的组合或一个或多个专用集成电路(ASIC) ), 以及通过可以加载到计算机或其他可编程数据处理设备上的计算机程序指令来生产机器, 使得在计算机或其他可编程数据处理设备上执行的指令创建用于实现在 流程图块或块。 计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,以导致在计算机或其他可编程设备上执行一系列操作步骤,以产生计算机实现的过程,使得在计算机或其他可编程数据处理设备上执行的指令 其他可编程装置提供用于实现流程图块或块中指定的功能的步骤。 [0090] 因此,图8-11的流程图图示的块支持用于执行指定功能/动作的电子电路和其他装置,以及用于执行指定功能/动作的步骤的组合。 应当理解,图 8-11 的流程图的每个块所支持的电路和其他装置,以及其中的块的组合,可以通过在专用或通用数据处理器上运行的专用硬件、软件或固件来实现, 或其组合。 [0091] 在附图和说明书中,已经公开了本发明的实施例,尽管使用了特定的术语,但它们仅用于一般和描述性的意义,而不是为了限制的目的,本发明的范围如下所述 索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101688786A(String), CN101688786B(String), EP2167919A1(String), EP2167919B1(String), JP2010534858A(String), JP4951707B2(String), KR101491195B1(String), KR1020100041814A(String), US20090017840A1(String), US8099108B2(String), WO2009008909A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101688786A(String), CN101688786B(String), EP2167919A1(String), EP2167919B1(String), JP2010534858A(String), JP4951707B2(String), KR101491195B1(String), KR1020100041814A(String), US20090017840A1(String), US8099108B2(String), WO2009008909A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8099108B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101688786A(String), CN101688786B(String), EP2167919A1(String), EP2167919B1(String), JP2010534858A(String), JP4951707B2(String), KR101491195B1(String), KR1020100041814A(String), US20090017840A1(String), US8099108B2(String), WO2009008909A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), CN101688786A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), CN101688786B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), EP2167919A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), EP2167919B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), JP2010534858A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), JP4951707B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), KR101491195B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.872 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), KR1020100041814A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), US20090017840A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), US8099108B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270672(Integer), WO2009008909A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8099108B2(String), US8099108B2(String), 1326729600(Integer), 270672(Integer), 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184992(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 184992(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1681975544(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184992(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75924(Integer), 2(Integer), 184992(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权 | 权利转移(String), 3(Integer), 184992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130346212A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US20130346212A1(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in a macrocell of the macro base station set in a downlink broadcast channel of the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station among the at least one femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations of the mobile terminal and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list of the neighboring femto base stations and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别设置在宏小区的下行链路广播信道中的宏基站的宏小区中的毫微微小区。 当移动终端在广播信道部分中的至少一个毫微微基站中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成移动终端的相邻毫微微基站列表和相邻毫微微基站信息,并发送相邻毫微微基站列表和相邻毫微微基站信息。 移动终端的相邻毫微微基站。(String), US14/014938(String), 1377792000(Integer), US20130346212A1(String), 1387987200(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 2(Integer), US20090307091A1 | US7489768B1(String), 4(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184993(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\a2d9377b96fa453f977a931ad42eeb81.png(String), 184993(Integer), a2d9377b96fa453f977a931ad42eeb81.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:49.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US20130346212A1(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in a macrocell of the macro base station set in a downlink broadcast channel of the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station among the at least one femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations of the mobile terminal and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list of the neighboring femto base stations and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别设置在宏小区的下行链路广播信道中的宏基站的宏小区中的毫微微小区。 当移动终端在广播信道部分中的至少一个毫微微基站中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成移动终端的相邻毫微微基站列表和相邻毫微微基站信息,并发送相邻毫微微基站列表和相邻毫微微基站信息。 移动终端的相邻毫微微基站。(String), US14/014938(String), 1377792000(Integer), US20130346212A1(String), 1387987200(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 2(Integer), US20090307091A1 | US7489768B1(String), \20230420\a2d9377b96fa453f977a931ad42eeb81.png(String), 4(Integer), 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184993(Integer), 1. A method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising:identifying a voice call transmitting signal transmitted from the mobile terminal;postponing transmission of the voice call transmitting signal, in response to the identification of the voice call transmitting signal; andoffering a unique voice advertisement service of the femto base station, in response to the identification of the voice call transmitting signal.(String), 1.一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括:识别移动终端发送的语音呼叫发送信号;延迟发送语音呼叫发送信号,以响应语音呼叫发送信号的识别;和响应语音呼叫发射信号的识别,提供毫微微基站的独特语音广告服务。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184993(Integer), 2. The method of claim 1, further comprising:identifying a ringback tone signal transmitted from a receiving side; andstopping the unique voice advertisement service of the femto base station in response to the identification of the ringback tone signal.(String), 2.如权利要求1所述的方法,还包括:识别接收端发送的回铃音信号;和响应回铃音信号的识别,停止毫微微基站的唯一语音广告服务。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184993(Integer), 3. A method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising:identifying a data communication connection signal transmitted from the mobile terminal;postponing transmission of the data communication connection signal, in response to the identification of the data communication connection signal; andoffering a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal.(String), 3.一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括:识别移动终端发送的数据通信连接信号;响应于数据通信连接信号的识别,推迟数据通信连接信号的传输;和响应于数据通信连接信号的识别,向移动终端提供毫微微基站的唯一广告服务。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184993(Integer), 4. The method of claim 3, further comprising:identifying a data reception signal about a uniform resource locator (URL) address that the mobile terminal desires to access; andstopping the unique advertisement service of the femto base station, in response to the identification of the data reception signal.(String), 4.如权利要求3所述的方法,还包括:识别关于移动终端希望访问的统一资源定位符(URL)地址的数据接收信号;和响应于数据接收信号的识别,停止毫微微基站的唯一广告服务。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184993(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a division of Application No. 13/013,617, filed on Jan. 25, 2011, which claims the benefit of Korean Patent Application No. 10-2010-0055844, filed on Jun. 14, 2010, in the Korean Intellectual Property Office, the entire disclosures of which are incorporated herein by reference for all purposes. BACKGROUND [0002]1. Field [0003]The following description relates to a method of advertising to a mobile terminal connected to a femto base station, and a communication method of a mobile terminal, a femto base station, and a macro base station. [0004]2. Description of Related Art [0005]Femtocells may be classified into various types of femtocells, for example, a personal femtocell that may be used to provide an ultrahigh speed transmission service within a predetermined area, a commercial femtocell to provide an advertisement service for sales promotion of a shop, and an authorized femtocell to provide a location service. Most femtocell applications focus on a user's convenience but do not sufficiently consider benefits to various installers and administrators. [0006]In a personal femtocell, a femtocell installer and an administrator may be substantially the same as a service beneficiary, and therefore, various administrative rights need not be distinguished. However, in the commercial femtocell, there is a need to further distinguish the rights of a femtocell installer with that of a femtocell administrator in order to protect commercial rights. SUMMARY [0007]In one general aspect, there is provided a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in a macrocell set in a downlink broadcast channel of the macrocell, receiving position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal from the mobile terminal, when the mobile terminal identifies an accessible femto base station from among the at least one femto base station in the broadcast channel section, generating a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal. [0008]The method may further comprise transmitting connection information to enable the mobile terminal to access a femto base station selected by the mobile terminal from among the femto base stations in the list to the mobile terminal. [0009]The broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0010]The information about the neighbor femto base stations of the mobile terminal may comprise information about a shop in which each of the femto base stations is located or information about a discount policy of a connection service offered by each of the femto base stations. [0011]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a voice call transmitting signal transmitted from the mobile terminal, postponing transmission of the voice call transmitting signal, in response to the identification of the voice call transmitting signal, and offering a unique voice advertisement service of the femto base station, in response to the identification of the voice call transmitting signal. [0012]The method may further comprise identifying a ringback tone signal transmitted from a receiving side, and stopping the unique voice advertisement service of the femto base station in response to the identification of the ringback tone signal. [0013]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a data communication connection signal transmitted from the mobile terminal, postponing transmission of the data communication connection signal, in response to the identification of the data communication connection signal, and offering a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal. [0014]The method may further comprise identifying a data reception signal about a uniform resource locator (URL) address that the mobile terminal desires to access, and stopping the unique advertisement service of the femto base station, in response to the identification of the data reception signal. [0015]In another aspect, there is provided a communication method of a mobile terminal, the method comprising detecting a broadcast channel section used to identify a femtocell in a macrocell set in a downlink broadcast channel of the macrocell, identifying a femto base station which is accessible to the mobile terminal from among at least one femto base station in the macrocell based on a measurement of an intensity of a signal of the broadcast channel section, transmitting, to a macro base station, position information of the mobile terminal and a request for information about the accessible femto base station, receiving a list of neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal from the macro base station, and selecting a femto base station from among the neighbor femto base stations of the mobile terminal based on the list of the neighbor femto base stations and the information about the neighbor femto base stations. [0016]The detecting of the broadcast channel section to identify the femtocell in the macrocell may detect a broadcast channel section based on whether a femtocell exploration mode of the mobile terminal in the macrocell is set. [0017]The indentifying of the accessible femto base station may identify a femto base station which is accessible to the mobile terminal from among the at least one femto base station in the macrocell by comparing a preset threshold value with the measured intensity of the signal of the broadcast channel section. [0018]The selected femto base station may be selected based on preferences of a user of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal. [0019]The method may further comprise receiving connection information to enable access to the selected femto base station from among the femto base stations in the list from the macro base station. [0020]The broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0021]The information about the neighbor femto base stations of the mobile terminal may comprise information about a shop in which the femto base stations are located, respectively, or comprises information about a discount policy of a connection service offered by each respective femto base station. [0022]In another aspect, there is provided a communication method of a femto base station, the method comprising receiving, from a macro base station, a report about a broadcast channel section used to identify a femtocell in a macrocell of the macro base station set in a downlink broadcast channel in the macrocell, and setting a signal in the broadcast channel section to report that the existence of a femtocell of the femto base station is within the macrocell of the macro base station. [0023]In another aspect, there is provided a computer-readable storage medium having stored therein program instructions to cause a processor to execute a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in a macrocell set in a downlink broadcast channel of the macrocell, receiving position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal from the mobile terminal, when the mobile terminal identifies an accessible femto base station from among the at least one femto base station in the broadcast channel section, generating a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal. [0024]Other features and aspects may apparent from the following description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0025]FIG. 1 is a diagram illustrating an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0026]FIG. 2 is a diagram illustrating an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0027]FIG. 3 is a flowchart illustrating an example of a communication method of a macro base station. [0028]FIG. 4 is a flowchart illustrating an example of a communication method of a mobile terminal. [0029]FIG. 5 is a flowchart illustrating an example of a method of offering an advertisement to a mobile terminal connected to a femto base station. [0030]Throughout the drawings and the description, unless otherwise described, the same drawing reference numerals should be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience. DESCRIPTION [0031]The following description is provided to assist the reader in gaining a comprehensive understanding of the methods, apparatuses, and/or systems described herein. Accordingly, various changes, modifications, and equivalents of the methods, apparatuses, and/or systems described herein may be suggested to those of ordinary skill in the art. Also, description of well-known functions and constructions may be omitted for increased clarity and conciseness. [0032]As described herein, a macrocell refers to a coverage area of a macro base station, and a femtocell refers to a coverage area of a femto base station. [0033]FIG. 1 illustrates an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0034]Referring to FIG. 1, the network in which the mobile terminal identifies and connects to the neighbor femtocell includes a macro base station 101, two femto base stations 103, and a mobile terminal 105. It should be appreciated that the number of macro base stations, femto base stations, and mobile terminals are not limited to the example shown in FIG. 1. For example, the network may include one or more macro base stations, one or more femto base stations, and one or more mobile terminals. [0035]The macro base station coverage area includes a macrocell. The macro base station 101 sets up a broadcast channel section 109 to identify a femtocell within a downlink broadcast channel 107 of the macrocell of the macro base station 105. The macro base station 101 reports the broadcast channel section 109 to at least one femto base station 103 in the macrocell of the macro base station 105. [0036]For example, the macro base station 101 may be linked with the femto base station 103 positioned in the macrocell of the macro base station 105, and maintain and renew a database including connection information. The connection information may include, for example, information about linked femto base stations 103, information about shops in which the linked femto base stations 103 are located, information about the linked femto base stations 103 with the macro base station 101, and the like. [0037]For example, the macro base station 101 may renew the database at a time when a femto base station 103 is added to the macrocell of the macro base station 105, at a preset time, or at any other desired time. [0038]The femto base stations 103 may offer various services, for example, real-time advertisements and event announcements of shops to the mobile terminal 105 as the user of the mobile terminal is within the coverage area of the femto base stations or passing by the shops in which the femto base stations 103 are located. [0039]For example, the femto base stations 103 may be linked with the macro base station 101 to attract customers passing by the shops in which the femto base stations 103 are located. The femto base stations 103 may be synchronized with the macro base station 101 to be linked with the macro base station 101. [0040]The mobile terminal 105 may set a femtocell exploration mode of the mobile terminal 105 to automatically identify a femtocell. For example, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 in order to identify a femtocell in the macrocell and identify whether there is a neighbor femtocell. During femtocell exploration mode, the mobile terminal 105 may detect one or more femtocells corresponding to one or more femto base stations 103, which are within the macrocell of the macro base station 101 and which are available for the mobile terminal 105 to connect with. [0041]The mobile terminal 105 may select a femto base station 103 from among the one or more detected femto base stations 103 based on a user preference of the mobile terminal 105 and/or information about neighbor femto base stations 103 of the mobile terminal 105 received from the macro base station 101. Accordingly, the mobile terminal 105 may be provided with a unique advertisement service of the femto base station 103 while located within a femtocell of the femto base station 103. [0042]For example, the unique advertisement service of the femto base station 103 may include products sold by a shop in which the femto base station 103 is located, an advertisement for the shop, an advertisement service for an event held by the shop, and the like. [0043]As an example, when the shop in which the femto base station 103 is located is an ice cream shop, an advertisement service for the shop may include an advertisement for a new flavor of ice cream that may be purchased in the shop, discount information about products “on sale”, discount coupons, and the like. [0044]As described herein, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 to identify a femtocell of a femto base station 103 that is located within the macrocell of the macro base station 101, and be provided with the a unique advertisement service of the femto base station 103 from the femto base station 103. The mobile terminal 105 may be positioned in the same macrocell as the macro base station 101 and the femto base station 103. The downlink broadcast channel 107 of the macrocell may be used to identify a femtocell in the macrocell. [0045]The broadcast channel section 109 used to identify the femtocell in the macrocell set in the downlink broadcast channel 107 of the macrocell may be set at a preset cycle, for example, a cycle of a hundred milliseconds, two hundred milliseconds, five hundred milliseconds, or other desired amount of time. [0046]Hereinafter, a method including the macro base station 101, the femto base station 103, and the mobile terminal 105 in which the mobile terminal 105 identifies a neighbor femto base station 103 of the mobile terminal 105 and connect to the femto base station 103, is described. [0047]The macro base station 101 reports information about the broadcast channel section 109 to the femtocell corresponding to at least one femto cell 103 in the macrocell set in the downlink broadcast channel 107 of the macrocell, in 110. For example, the macro base station may report to one or more femto base stations 103 during 110. [0048]The femto base station 103 receiving a report about the broadcast channel section 109 from the macro base station 101 may set a signal in the broadcast channel section 109 in order to report the existence of the femtocell corresponding to the femto base station 103, in 120. [0049]For example, the broadcast channel section 109 of the downlink broadcast channel 107 may be set to a single bit or multiple bits. [0050]In 120, the femto base station 103 may set various types of signals in the broadcast channel section 109 to report the existence of the femtocell of the femto base station 103, for example, the femto base station 103 may set a particular bit of the broadcast channel section 109 to ‘1’ or set the broadcast channel section 109 to a dummy signal. [0051]When the femtocell exploration mode of the mobile terminal 105 is set to ON in 130, the mobile terminal 105 may detect the broadcast channel section 109 to that identify the femtocell corresponding to the a femto base station 103 is within the macrocell corresponding to the macro base station 101. [0052]The mobile terminal 105 may identify a femto base station 103 that is accessible to the mobile terminal 105 from among the at least one femto base station 103 that is within the macrocell of the macro base station, based on a measurement result of an intensity of the signal of the broadcast channel section 109, in 140. [0053]For example, when the measurement result of the intensity of the signal in the broadcast channel section 109 is higher than a preset threshold value, the mobile terminal 105 may identify that there is at least one femto base station 103 neighboring the mobile terminal 105 and which is accessible to the mobile terminal 105. As another example, based on the intensity of the signal the mobile terminal 105 may determine that a plurality of femto base stations are neighboring and available, for example, two femto base stations, three femto base stations, four femto base stations, or more femto base stations. [0054]For example, the femto base station 103 may set a signal in the broadcast channel section 109 in order to report the existence of the femtocell that corresponds to the femto base station 103 when receiving the report about the broadcast channel section 109 to identify the femtocell in the macrocell from the macro base station 101. [0055]The mobile terminal 105 may measure an intensity of the signal in the broadcast channel section 109 received from each neighbor femto base station 103 of the mobile terminal 105. The mobile terminal 105 may identify a femto base station 103 that is accessible to the mobile terminal 105 from among the at least one femto base station 103 in the macrocell based on the measured intensity. [0056]The mobile terminal 105 may transmit position information of the mobile terminal 105 to the macro base station 101, and may transmit a request for information about the femto base station 103 which is accessible to the mobile terminal 105 to the macro base station 101, in 150. [0057]For example, the macro base station 101 may generate a list of neighbor femto base stations 103 and information about the neighbor femto base stations 103 based on the position information of the mobile terminal 105 received from the mobile terminal 105, and may transmit the generated information to the mobile terminal 105, in 160. [0058]As an example, the information about the neighbor femto base stations 103 of the mobile terminal 105 may include information about a shop in which each of the respective femto base stations 103 is located or information about a discount policy of a connection service offered by each of the femto base stations 103. [0059]The mobile terminal 105 may select one femto base station 103 from among the neighbor femto base stations 103 of the mobile terminal 105 based on the list of the neighbor femto base stations 103 and the information about the neighbor femto base stations 103 received from the macro base station 101, in 170. [0060]In 170, the mobile terminal 105 may select the femto base station 103 in the list of the neighbor femto base stations 103 based on a user preference of the mobile terminal 105 and/or the information about the neighbor femto base stations 103 of the mobile terminal 105. [0061]An example of the list of the neighbor femto base stations 103 of the mobile terminal 105 received by the mobile terminal 105 from the macro base station 101 may include the following contents as shown in Table 1. TABLE 1Locationof BaseFemto baseBusinessTransmissionstationstation IDcategoryPolicy for usespeedaACosmeticsfreeLowaBClothing10 cents/minHighaCEntertainmentfreeMediumaDFast food5 cent/minHigh(free whenreceivingadvertisements) [0062]In this example, the mobile terminal 105 receives information about four femto base stations A, B, C, and D 103 neighboring the mobile terminal 105 from the macro base station 101. Accordingly, if a user of the mobile terminal 105 prefers a femto base station that provides a high transmittance speed and a free communication channel, the user of the mobile terminal 105 may select femto base station D to receive communication from. [0063]That is, the mobile terminal 105 may automatically select or a user of the mobile terminal 105 may select the femto base station D which satisfies all user preferences from among the femto base stations B and D that provide a high transmittance speed and a free communication channel from among the femto base stations A, B, C, and D in the list. [0064]For example, the mobile terminal 105 may use the communication channel provided by the selected femto base station D. Further, the mobile terminal 105 may be provided with information about a shop in which the femto base station D is located or information about a discount policy of a connection service offered by the femto base station D from the femto base station D. [0065]In this example, the femto base station D corresponds to a femto base station of a fast food restaurant. Accordingly, the mobile terminal 105 may be provided with information about a fast food restaurant in which the femto base station D is located, information about a sales event offered by the fast food restaurant, coupons for discounts offered by the fast food restaurant, and an advertisement for the sales event. [0066]As another example, the mobile terminal 105 may select a femto base station 103 based on the information about the neighbor femto base stations 103 of the mobile terminal 105. [0067]For example, the mobile terminal 105 may select a femto base station 103 corresponding to information in which a user of the mobile terminal 105 is interested in from among information about shops in which the respective femto base stations 103 in the list of the neighbor the femto base stations 103 of the mobile terminal 105 are located. [0068]As an example, the mobile terminal 105 may select a femto base station 103 located in a shop in the list of the neighbor femto base stations 103 of the mobile terminal 105, the shop offering a sales event, a shop providing a coupon of a product for a discount when receiving an advertisement service, and the like. [0069]As described above, the mobile terminal 105 may automatically select a femto base station 103 from the list of the neighbor femto base stations 103 of the mobile terminal 105 by various methods. Depending on the femto base station 103 selected, the user of the mobile terminal 105 may be provided with an advertisement service from the femto base station 103. [0070]Further, the mobile terminal 105 itself may provide the list of the neighbor femto base stations 103 of the mobile terminal 105 and information about events thereof to a user of the mobile terminal 105 when selecting a femto base station 103, thereby allowing the users to select a femto base station 103 themselves. [0071]As another example, a femto base station 103 may be automatically selected by the macro base station 101. In yet other embodiments, the femto base station 103 may be automatically selected by the mobile terminal 105 based on predetermined settings or dynamically adjusted settings that may be dynamically set by a user. As yet another example, the femto base station 103 may be selected by a user of the mobile terminal 105. [0072]As another example, the macro base station 101 may store a user preference of the mobile terminal 105 and the information about the neighbor femto base stations 103 of the mobile terminal 105 in advance, and selectively provide a femto base station 103 that satisfies the user preference based on stored information. [0073]For example, the macro base station 101 may include a database of information about the user preference of the mobile terminal 105 shown in the following Table 2. TABLE 2MobileterminalAgePolicy forTransmissionInterestedIDgroupsusespeedbusiness categoryOthersA20sFreeMediumCommunicationSelecting free ofterminals, gamescharge whenreceivingadvertisementsB30sFree/chargedHighRestaurantsHigh transmissionspeedC40sFreeMediumSports, bookReceiving sports-storesrelatedadvertisements [0074]The macro base station 101 may select a femto base station 103 which corresponds to the user preferences of the mobile terminal 105 shown in Table 2 from among the information about the neighbor femto base stations 103 of the mobile terminal 105 and provide the femto base station 103 to the mobile terminal 105. [0075]The macro base station 101 may transmit connection information to the mobile terminal 105 to enable an access to the selected femto base station 103 in the list of the femto base stations 103, in 180. [0076]The mobile terminal 105 may connect to the selected femto base station 103 using the connection information received from the macro base station 101, in 190. [0077]Accordingly, the mobile terminal 105 connected to the femto base station 103 may be provided with various communication services and advertisement services offered by the femto base station 103. [0078]For example, the advertisement services may include a unique voice advertisement service of the femto base station 103 and a unique display advertisement service of the femto base station 103. For example, the unique voice advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 inputs a telephone number and waits for a call to connect. [0079]As described herein, the unique advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 waits for data reception about a uniform resource locator (URL) address which the mobile terminal 105 desires to access. [0080]FIG. 2 illustrates an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0081]Referring to FIG. 2, the network for providing the advertisement to the mobile terminal includes a counterpart exchange station 201, a femto base station 203, a mobile terminal 205, and a receiving side mobile terminal 207. [0082]For example, a user in control of the mobile terminal 205 passing by a shop in which the femto base station 203 is located may attempt to call a friend by entering the phone number of a friend that corresponds to the receiving side mobile terminal 207, to try a call, in 210. [0083]In response to the call being placed by the user of the mobile terminal 205, the femto base station 203 identifies a voice call transmitting signal transmitted from the mobile terminal 205 based on the call being placed. Accordingly, the femto base station 203 may provide an advertisement to the mobile terminal 205 connected to the femto base station 203, and postpone transmission of the voice call transmitting signal in response to the identification of the voice call transmitting signal, in 220. [0084]For example, the femto base station 203 may include a voice call transmitting signal identification module that may identify the voice call transmitting signal transmitted from the mobile terminal 205. The femto base station 203 may offer a unique voice advertisement service of the femto base station 203 to the mobile terminal 205 in response to the identification of the voice call transmitting signal, in 230. [0085]The femto base station 203 forwards the postponed voice call transmitting signal to the counterpart exchange station 201, in 240. For example, the femto base station 203 may forward the postponed voice call transmitting signal after a predetermined amount of time elapses. [0086]For example, the femto base station 203 may identify a ringback tone signal transmitted from the receiving side mobile terminal 207, and accordingly, the femto base station 203 stops the unique voice advertisement service of the femto base station 203 in response to the identification of the ringback tone signal, in 250. [0087]After stopping the unique voice advertisement service of the femto base station 203, the femto base station 203 may forward the ringback tone signal to the mobile terminal 205 to connect a voice call, in 260. [0088]FIG. 3 illustrates an example of a communication method of a macro base station. [0089]Referring to FIG. 3, the macro base station reports information about a broadcast channel section to at least one femto base station to identify a femtocell corresponding to a femto base station in the macrocell corresponding to the macro base station set in a downlink broadcast channel of the macrocell, in 310. For example, the broadcast channel may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0090]The macro base station receives position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, in 320. For example, the position information and the request for information may be transmitted from the mobile terminal. For example, when the mobile terminal identifies an accessible femto base station from among the at least one femto base station in the broadcast channel section, the mobile terminal may transmit the information to the macro base station. [0091]For example, the information about the neighbor femto base stations of the mobile terminal may include information about a shop in which each of the femto base stations is located. As another example, the information may include information about a discount policy of a connection service offered by each of the femto base stations. [0092]The macro base station generates a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, in 330. [0093]The macro base station transmits the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal, in 340. [0094]In 350, the macro base station may transmit connection information to enable the mobile terminal access to a femto base station. [0095]The connection information to enable the mobile terminal access to the femto base station may be information about a femto base station selected by the mobile terminal from among the neighbor femto base stations of the mobile terminal in the list. [0096]FIG. 4 illustrates an example of a communication method of a mobile terminal. [0097]Referring to FIG. 4, the mobile terminal may determine whether a femtocell exploration mode of the mobile terminal in a macrocell is set to ‘ON’, in 410. [0098]When the femtocell exploration mode is set to ‘ON,’ the mobile terminal detects a broadcast channel section to identify a femtocell that the macrocell set in a downlink broadcast channel of the macrocell, in 420. For example, the broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0099]As a result of the determination in 410, if the femtocell exploration mode is not set to ‘ON,’ or the mobile terminal does not have a femtocell exploration function, the mobile terminal may finish the process without performing subsequent operations to 410. [0100]The mobile terminal identifies a f(String), 相关申请的交叉引用 [0001] 本申请是 2011 年 1 月 25 日提交的申请号 13/013,617 的分案,该申请要求韩国知识产权局于 2010 年 6 月 14 日提交的韩国专利申请号 10-2010-0055844 的权益 Office,其全部公开内容出于所有目的通过引用并入本文。 背景 [0002] 1. 领域 [0003] 以下描述涉及向连接到毫微微基站的移动终端进行广告的方法,以及移动终端、毫微微基站和宏基站的通信方法。 [0004] 2.相关技术说明 [0005] Femtocell可以分为各种类型的femtocell,例如,可以用于在预定区域内提供超高速传输服务的个人femtocell,用于为商店的促销提供广告服务的商业femtocell,以及授权的femtocell。 femtocell 提供定位服务。 大多数毫微微蜂窝应用关注用户的便利性,但没有充分考虑对各种安装人员和管理员的好处。 [0006] 在个人femtocell中,femtocell安装者和管理员可以作为服务受益人基本相同,因此不需要区分各种管理权限。 然而,在商用毫微微基站中,需要进一步区分毫微微基站安装者和毫微微基站管理员的权利,以保护商业权利。 概括 [0007] 在一个一般方面,提供了一种宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告关于用于识别毫微微小区中的毫微微小区的广播信道部分的信息。 宏小区设置在宏小区的下行广播信道中,当移动终端识别出可接入的毫微微基站时,从移动终端接收移动终端的位置信息和对移动终端的相邻毫微微基站的信息的请求 广播信道部分中的至少一个毫微微基站,基于移动终端的位置信息生成移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息,并发送 移动终端的相邻femto基站列表和有关相邻femt的信息 o 移动终端的基站到移动终端。 [0008] 该方法还可以包括向移动终端发送连接信息以使移动终端能够接入由移动终端从列表中的毫微微基站中选择的毫微微基站。 [0009] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0010] 关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于每个毫微微基站提供的连接服务的折扣政策的信息。 [0011] 在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的语音呼叫发送信号,作为响应推迟语音呼叫发送信号的发送 对语音呼叫发送信号的识别,并响应语音呼叫发送信号的识别,提供毫微微基站的独特语音广告服务。 [0012] 该方法还可以包括识别从接收侧发送的回铃音信号,并且响应于回铃音信号的识别停止毫微微基站的唯一语音广告服务。 [0013]在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的数据通信连接信号,作为响应推迟数据通信连接信号的发送 对数据通信连接信号的识别进行响应,并响应于数据通信连接信号的识别,向移动终端提供毫微微基站的唯一广告服务。 [0014] 该方法还可以包括识别关于移动终端期望访问的统一资源定位符(URL)地址的数据接收信号,并且响应于数据接收信号的识别停止毫微微基站的唯一广告服务。 [0015] 在另一方面,提供了一种移动终端的通信方法,该方法包括:检测用于在宏小区的下行链路广播信道中设置的宏小区中识别毫微微小区的广播信道部分,识别可接入的毫微微基站。 来自宏小区中的至少一个毫微微基站中的移动终端基于对广播信道部分的信号强度的测量,向宏基站发送移动终端的位置信息和对有关信息的请求 可接入的毫微微基站,从宏基站接收移动终端的相邻毫微微基站列表和关于移动终端的相邻毫微微基站的信息,并从相邻毫微微基站中选择毫微微基站 移动终端基于相邻毫微微基站列表和有关相邻毫微微基站的信息 车站。 [0016] 检测广播信道区间以识别宏小区中的毫微微小区可以基于是否设置了移动终端在宏小区中的毫微微小区探索模式来检测广播信道区间。 [0017] 可接入毫微微基站的识别可以通过将预设阈值与所测量的广播信道的信号强度进行比较,从宏小区中的至少一个毫微微基站中识别出移动终端可接入的毫微微基站。 部分。 [0018] 可以基于移动终端的用户的偏好和关于移动终端的相邻毫微微基站的信息来选择所选择的毫微微基站。 [0019] 该方法还可以包括从宏基站接收连接信息以使得能够从列表中的毫微微基站中接入所选择的毫微微基站。 [0020] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0021] 移动终端的相邻毫微微基站的信息可以包括毫微微基站所在店铺的信息,或者包括各个毫微微基站提供的连接服务的折扣政策的信息。 [0022] 在另一方面,提供了一种毫微微基站的通信方法,该方法包括从宏基站接收关于用于识别设置在宏基站的宏小区中的毫微微小区的广播信道部分的报告。 宏小区中的下行广播信道,并在广播信道部分设置信号以报告在宏基站的宏小区内存在毫微微基站的毫微微小区。 [0023]在另一方面,提供了一种其中存储有程序指令的计算机可读存储介质,以使处理器执行宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告。 宏基站,关于用于识别宏小区下行广播信道中设置的宏小区中的毫微微小区的广播信道部分的信息,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求。 移动终端,当移动终端从广播信道部分的至少一个毫微微基站中识别出可接入的毫微微基站时,生成移动终端的相邻毫微微基站的列表和关于相邻毫微微基站的信息 移动终端根据移动终端的位置信息,发送l 移动终端的相邻毫微微基站的列表以及移动终端的相邻毫微微基站的信息给移动终端。 [0024] 从以下描述、附图和权利要求中,其他特征和方面可能是显而易见的。 附图的简要说明 [0025] 图1是图示允许移动终端识别并连接到相邻毫微微小区的网络的示例的图。 [0026] 图2是图示允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例的图。 [0027] 图3是图示宏基站的通信方法的示例的流程图。 [0028] 图4是图示移动终端的通信方法的示例的流程图。 [0029] 图5是图示向连接到毫微微基站的移动终端提供广告的方法的示例的流程图。 [0030] 在整个附图和描述中,除非另有说明,相同的附图标记应被理解为指代相同的元件、特征和结构。 为了清楚、说明和方便起见,这些元素的相对大小和描述可能会被夸大。 描述 [0031] 提供以下描述以帮助读者获得对本文描述的方法、装置和/或系统的全面理解。 因此,可以向本领域普通技术人员建议本文描述的方法、装置和/或系统的各种改变、修改和等效物。 此外,为了更清楚和简明,可以省略对众所周知的功能和结构的描述。 [0032] 如本文所述,宏小区是指宏基站的覆盖区域,毫微微小区是指毫微微基站的覆盖区域。 [0033] 图1图示了允许移动终端识别并连接到相邻毫微微小区的网络的示例。 [0034] 参考图1,移动终端识别并连接到相邻毫微微小区的网络包括宏基站 101 , 两个毫微微基站 103 , 和一个移动终端 105 . 应当理解,宏基站、毫微微基站和移动终端的数量不限于图1所示的示例。例如,网络可以包括一个或多个宏基站、一个或多个毫微微基站 ,以及一个或多个移动终端。 [0035] 宏基站覆盖区域包括宏小区。 宏基站 101 设置广播频道部分 109 识别下行广播信道内的毫微微小区 107 宏基站的宏小区 105 . 宏基站 101 报告广播频道部分 109 到至少一个毫微微基站 103 在宏基站的宏小区中 105 . [0036] 例如宏基站 101 可与毫微微基站链接 103 位于宏基站的宏小区 105,并维护和更新包括连接信息的数据库。 连接信息可以包括例如关于链接的毫微微基站的信息 103 ,有关链接的毫微微基站的商店的信息 103 定位,有关链接的毫微微基站的信息 103 与宏基站 101 ,等等。 [0037] 例如宏基站 101 可以在毫微微基站更新数据库时 103 加入宏基站的宏小区 105 ,在预设时间,或在任何其他所需时间。 [0038] 毫微微基站 103 可以向移动终端提供各种服务,例如商店的实时广告和活动公告 105 当移动终端的用户在毫微微基站的覆盖范围内或经过毫微微基站所在的商店时 103 位于。 [0039] 例如,毫微微基站 103 可与宏基站联动 101 吸引经过femto基站所在商店的顾客 103 位于。 毫微微基站 103 可与宏基站同步 101 与宏基站联动 101 . [0040] 移动终端 105 可以设置移动终端的femtocell探索模式 105 自动识别毫微微蜂窝基站。 例如,当移动终端的femtocell探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 以识别宏小区中的毫微微小区,并识别是否有相邻毫微微小区。 在femtocell探索模式下,移动终端 105 可以检测对应于一个或多个毫微微基站的一个或多个毫微微小区 103 ,在宏基站的宏小区内 101 哪些可用于移动端 105 连接。 [0041] 移动终端 105 可以选择一个毫微微基站 103 从一个或多个检测到的毫微微基站中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 移动终端的 105 从宏基站接收 101 . 因此,移动终端 105 可以提供femto基站的独特广告服务 103 当位于毫微微基站的毫微微小区内时 103 . [0042] 例如,femto 基站的独特广告服务 103 可能包括由 Femto 基站所在的商店销售的产品 103 定位,商店的广告,商店举办的活动的广告服务等。 [0043] 例如,当 femto 基站所在的商店 103 如果位于冰淇淋店,则该店的广告服务可以包括可在该店购买的新口味冰淇淋的广告、“特价”产品的折扣信息、折扣券等。 [0044] 如本文所述,当移动终端的毫微微小区探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 识别毫微微基站的毫微微小区 103 位于宏基站的宏小区内 101 ,并获得femto基站独有的广告服务 103 从毫微微基站 103 . 移动终端 105 可以与宏基站位于同一宏小区中 101 和毫微微基站 103 . 下行广播信道 107 宏小区的名称可以用于识别宏小区中的毫微微小区。 [0045] 广播频道部分 109 用于识别下行广播信道中宏小区集合中的毫微微小区 107宏小区的时间周期可以设置为预设的周期,例如一百毫秒、两百毫秒、五百毫秒的周期,或者其他期望的时间量。 [0046] 在下文中,一种包括宏基站的方法 101 , 毫微微基站 103 , 和移动终端 105 其中移动端 105 识别相邻的毫微微基站 103 移动终端的 105 并连接到 femto 基站 103 , 被描述。 [0047] 宏基站 101 报告有关广播频道部分的信息 109 到对应于至少一个毫微微小区的毫微微小区 103 在下行广播信道中设置的宏小区中 107 宏蜂窝,在 110 . 例如,宏基站可以向一个或多个毫微微基站报告 103 期间 110 . [0048] 毫微微基站 103 接收有关广播频道部分的报告 109 从宏基站 101 可以在广播频道部分设置信号 109 为了上报femto基站对应的femtocell的存在 103 , 在 120 . [0049] 例如,广播频道部分 109 下行广播信道 107 可以设置为单个位或多个位。 [0050] 在 120 , 毫微微基站 103 可以在广播频道部分设置各种类型的信号 109 报告femto基站的femtocell存在 103 ,例如,毫微微基站 103 可以设置广播频道部分的特定位 109 为“1”或设置广播频道部分 109 到一个虚拟信号。 [0051] 当移动终端的femtocell探索模式 105 在设置为 ON 130 , 移动端 105 可以检测广播频道部分 109 以识别对应于一个毫微微基站的毫微微小区 103 在宏基站对应的宏小区内 101 . [0052] 移动终端 105 可以识别毫微微基站 103 移动终端可以访问的 105 从至少一个毫微微基站中 103 在宏基站的宏小区内,基于广播信道部分的信号强度的测量结果 109 , 在 140 . [0053] 例如,当广播频道部分的信号强度测量结果 109 高于预设阈值,移动终端 105 可以识别存在至少一个毫微微基站 103 靠近移动终端 105 移动终端可以访问的 105 . 作为另一个示例,基于信号的强度,移动终端 105 可以确定多个毫微微基站相邻且可用,例如,两个毫微微基站、三个毫微微基站、四个毫微微基站或更多毫微微基站。 [0054] 例如,毫微微基站 103 可以在广播频道部分设置信号 109 为了上报femto基站对应的femtocell的存在 103 收到有关广播频道部分的报告时 109 从宏基站识别宏小区中的毫微微小区 101 . [0055] 移动终端 105 可以测量广播频道部分的信号强度 109 从每个相邻毫微微基站接收 103 移动终端的 105 . 移动终端 105 可以识别毫微微基站 103 移动终端可以访问的 105 从至少一个毫微微基站中 103 在基于测量强度的宏单元中。 [0056] 移动终端 105 可以发送移动终端的位置信息 105 到宏基站101 ,并且可以发送对关于毫微微基站的信息的请求 103 移动终端可以访问的 105 到宏基站 101 , 在 150 . [0057] 例如宏基站 101 可以生成相邻毫微微基站的列表 103 以及有关相邻毫微微基站的信息 103 基于移动终端的位置信息 105 从移动终端接收 105 ,并且可以将生成的信息发送到移动终端 105 , 在 160 . [0058] 例如,有关相邻毫微微基站的信息 103 移动终端的 105 可以包括关于商店的信息,其中每个相应的毫微微基站 103 位置或有关每个毫微微基站提供的连接服务的折扣政策的信息 103 . [0059] 移动终端 105 可选择一个毫微微基站 103 从相邻的毫微微基站中 103 移动终端的 105 基于相邻毫微微基站列表 103 以及有关相邻毫微微基站的信息 103 从宏基站接收 101 , 在 170 . [0060] 在 170 , 移动端 105 可选择femto基站 103 在相邻毫微微基站列表中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 移动终端的 105 . [0061] 相邻毫微微基站列表的示例 103 移动终端的 105 由移动终端接收 105 从宏基站 101 可包括以下内容,如表 1 所示。 表格1 地点 基地 毫微微基站 商业 传播 车站 站号 类别 使用政策 速度 a A 化妆品 自由的 低的 a B 衣服 10 美分/分钟 高的 a C 娱乐 自由的 中等的 a D 快餐 5 分/分钟 高的 (免费时 接收 广告) [0062] 在这个例子中,移动终端 105 接收有关四个毫微微基站 A、B、C 和 D 的信息 103 靠近移动终端 105 从宏基站 101 . 因此,如果移动终端的用户 105 移动终端的用户更喜欢提供高传输速度和免费通信信道的毫微微基站 105 可以选择毫微微基站D来接收通信。 [0063] 也就是移动终端 105 可自动选择或移动终端的用户 105 可以从列表中的毫微微基站A、B、C和D中提供高传输速度和空闲通信信道的毫微微基站B和D中选择满足所有用户偏好的毫微微基站D。 [0064] 例如,移动终端 105 可以使用由选择的毫微微基站D提供的通信信道。此外,移动终端 105 可以提供关于毫微微基站D所在的商店的信息或者关于毫微微基站D从毫微微基站D提供的连接服务的折扣政策的信息。 [0065] 在该示例中,毫微微基站D对应于快餐店的毫微微基站。 因此,移动终端 105 可以提供关于毫微微基站D所在的快餐店的信息、关于快餐店提供的销售活动的信息、快餐店提供的折扣券以及销售活动的广告。 [0066] 再举一个例子,移动终端 105 可以选择一个毫微微基站 103 基于有关相邻毫微微基站的信息 103 移动终端的 105 . [0067] 例如,移动终端 105 可以选择一个毫微微基站 103 对应于移动终端用户的信息 105 从有关各个femto基站所在商店的信息中感兴趣 103在邻居列表中的毫微微基站 103 移动终端的 105 位于。 [0068] 以移动终端为例 105 可以选择一个毫微微基站 103 位于相邻毫微微基站列表中的商店中 103 移动终端的 105 、提供销售活动的商店、在接收广告服务时提供产品优惠券以获得折扣的商店等。 [0069] 如上所述,移动终端 105 可以自动选择一个毫微微基站 103 从相邻毫微微基站列表中 103 移动终端的 105 通过各种方法。 取决于毫微微基站 103 选中,移动端的用户 105 可以从毫微微基站提供广告服务 103 . [0070] 此外,移动终端 105 本身可以提供相邻毫微微基站的列表 103 移动终端的 105 以及关于其事件的信息给移动终端的用户 105 选择毫微微基站时 103 ,从而允许用户选择一个毫微微基站 103 他们自己。 [0071] 作为另一个示例,毫微微基站 103 可由宏基站自动选择 101 . 在又一些实施例中,毫微微基站 103 可由移动端自动选择 105 基于可以由用户动态设置的预定设置或动态调整的设置。 作为又一示例,毫微微基站 103 可由移动终端的用户选择 105 . [0072] 再举一个例子,宏基站 101 可以存储移动终端的用户偏好 105 以及有关相邻毫微微基站的信息 103 移动终端的 105 提前,并有选择地提供一个毫微微基站 103 根据存储的信息满足用户偏好。 [0073] 例如宏基站 101 可以包括关于移动终端的用户偏好的信息数据库 105 如下表2所示。 表 2 移动的 终端 年龄 政策 传播 感兴趣的 ID 团体 利用 速度 业务类别 其他 A 20s 自由的 中等的 沟通 选择免费的 终端、游戏 什么时候收费 接收 广告 B 30s 免费/收费 高的 餐厅 高传输 速度 C 40s 自由的 中等的 运动、书籍 接受运动—— 商店 有关的 广告 [0074] 宏基站 101 可以选择一个毫微微基站 103 对应移动终端的用户偏好 105 从有关相邻毫微微基站的信息中显示在表2中 103 移动终端的 105 并提供femto基站 103 到移动终端 105 . [0075] 宏基站 101 可以向移动终端发送连接信息 105 启用对所选毫微微基站的访问 103 在 femto 基站列表中 103 , 在 180 . [0076] 移动终端 105 可以连接到选定的毫微微基站 103 使用从宏基站接收到的连接信息 101 , 在 190 . [0077] 因此,移动终端 105 连接到毫微微基站 103 可以提供由毫微微基站提供的各种通信服务和广告服务 103 . [0078] 例如,广告服务可以包括毫微微基站的独特语音广告服务 103 以及femto基站独有的展示广告服务 103 . 例如,femto基站独有的语音广告服务 103 可提供给移动终端 105 而移动端 105 输入电话号码并等待呼叫接通。 [0079] 如本文所述,毫微微基站的独特广告服务 103 可提供给移动终端 105 而移动端 105 等待关于移动终端的统一资源定位符(URL)地址的数据接收 105 渴望访问。 [0080] 图2图示了允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例。 [0081] 参考图2,用于向移动终端提供广告的网络包括对方交换站 201 , 一个毫微微基站 203 , 移动终端 205 ,以及接收方移动终端 207 . [0082] 例如,控制移动终端的用户 205 路过一家有femto基站的商店 203 定位到可以尝试通过输入与接收方移动终端对应的朋友的电话号码来呼叫朋友 207 , 尝试通话,在 210 . [0083] 响应移动终端用户的呼叫 205 , 毫微微基站 203 识别移动终端发送的语音呼叫发送信号 205 根据正在拨打的电话。 因此,毫微微基站 203 可以向移动终端提供广告 205 连接到毫微微基站 203 ,并且响应于语音呼叫发射信号的识别延迟语音呼叫发射信号的传输,在 220 . [0084] 例如,毫微微基站 203 可以包括语音呼叫发送信号识别模块,其可以识别从移动终端发送的语音呼叫发送信号 205 . 毫微微基站 203 可以提供femto基站独特的语音广告服务 203 到移动终端 205 响应语音呼叫发射信号的识别,在 230 . [0085] 毫微微基站 203 将延迟的语音呼叫发射信号转发给对方交换台 201 , 在 240 . 例如,毫微微基站 203 可以在经过预定时间量之后转发延迟的语音呼叫发送信号。 [0086] 例如,毫微微基站 203 可以识别从接收侧移动终端发送的回铃音信号 207 ,因此,毫微微基站 203 停止femto基站独有的语音广告服务 203 响应回铃音信号的识别,在 250 . [0087] 停止femto基站的独特语音广告服务后 203 , 毫微微基站 203 可以将回铃音信号转发给移动终端 205 连接语音通话,在 260 . [0088] 图3图示了宏基站的通信方法的示例。 [0089] 参考图3,宏基站向至少一个毫微微基站报告关于广播信道部分的信息,以识别与在该宏基站的下行链路广播信道中设置的宏基站对应的宏小区中的毫微微基站对应的毫微微小区。 宏单元,在 310 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道。 [0090] 宏基站接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,在 320 . 例如,可以从移动终端发送位置信息和信息请求。 例如,当移动终端从广播信道部分中的至少一个毫微微基站中识别出可访问的毫微微基站时,移动终端可以将该信息发送到宏基站。 [0091] 例如,关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息。 作为另一示例,该信息可以包括关于由每个毫微微基站提供的连接服务的折扣策略的信息。 [0092]宏基站根据移动终端的位置信息生成移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息,在 330 . [0093] 宏基站将移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息发送给移动终端,在 340 . [0094] 在 350 ,宏基站可以发送连接信息以使移动终端能够接入毫微微基站。 [0095] 使移动终端能够接入毫微微基站的连接信息可以是关于移动终端从列表中的移动终端的相邻毫微微基站中选择的毫微微基站的信息。 [0096] 图4图示了移动终端的通信方法的示例。 [0097] 参考图4,移动终端可以确定移动终端在宏小区中的毫微微小区探索模式是否设置为“ON”,在 410 . [0098] 当毫微微小区探索模式设置为“开启”时,移动终端检测广播信道部分以识别宏小区在宏小区的下行链路广播信道中设置的毫微微小区,在 420 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道段。 [0099] 作为确定的结果 410 ,如果femtocell探索模式未设置为“ON”,或者移动终端不具备femtocell探索功能,则移动终端可以不执行后续操作就完成该过程 410 . [0100] 移动终端基于广播信道部分的信号强度的测量从宏小区中的至少一个毫微微基站中识别移动终端可接入的毫微微基站,以便识别宏小区中的毫微微小区 . [0101] 也就是说,移动终端可以测量广播信道部分的信号强度以识别毫微微小区,并将测量结果与预设阈值进行比较,在 440 . [0102] 当测量的广播频道部分的信号强度 440 高于预设阈值时,移动终端可以从宏小区中的至少一个毫微微基站中识别出该毫微微基站是移动终端可接入的,在 450 . [0103] 移动终端向宏基站发送移动终端的位置信息和对关于可接入毫微微基站的信息的请求,在 460 . 移动终端接收来自宏基站的请求信息,在 470 . [0104] 例如,从宏基站接收的信息可以包括移动终端的相邻毫微微基站的列表和关于移动终端的相邻毫微微基站的信息。 例如,可以基于移动终端的位置信息来生成列表和信息。 [0105] 作为示例,关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于由每个毫微微基站提供的连接服务的折扣政策的信息。 车站。 [0106] 移动终端可以基于相邻毫微微基站的列表和关于相邻毫微微基站的信息,从移动终端的相邻毫微微基站中选择毫微微基站,在 480 . [0107] 例如,移动终端可以使用移动终端的用户的偏好和关于移动终端的相邻毫微微基站的信息来选择毫微微基站。 [0108] 图5图示了向连接到毫微微基站的移动终端提供广告的方法的示例。 [0109]参考图5,当移动终端输入诸如移动终端希望访问的URL地址的数据通信连接信号时,毫微微基站识别从移动终端发送的数据通信连接信号,在 510 . [0110] 毫微微基站响应于数据通信连接信号的识别延迟数据通信连接信号的传输,在 520 . [0111] 毫微微基站响应数据通信连接信号的识别,向移动终端提供独特的毫微微基站广告服务,在 530 . 例如,在经过预定量的时间之后,毫微微基站可以将延迟的数据通信连接信号转发到运行中的互联网服务器。 [0112] 在 540 ,毫微微基站识别关于移动终端希望访问的URL地址的数据接收信号。 例如,毫微微基站可以包括识别数据接收信号的功能模块,例如移动终端期望的主页或URL地址,以便识别数据接收信号。 [0113] 毫微微基站可以响应关于移动终端希望访问的URL地址的数据接收信号的识别,停止毫微微基站的唯一广告服务,在 550 . 毫微微基站可以将关于移动终端期望访问的URL地址的数据接收信号转发给移动终端以连接语音呼叫。 [0114] 如本文所述,移动终端可以包括各种模式,例如毫微微小区探索模式。 然而,应该理解,移动终端可能只有一种模式,其中移动终端不断地搜索可用的毫微微小区。 [0115] 仅作为非穷举说明,此处描述的终端设备可以指移动设备,例如蜂窝电话、个人数字助理(PDA)、数码相机、便携式游戏机、MP3播放器、便携式/个人多媒体 播放器 (PMP)、手持电子书、便携式实验室个人计算机 (PC)、全球定位系统 (GPS) 导航,以及台式 PC、高清电视 (HDTV)、光盘等设备 播放器、设置盒等,能够进行与本文所公开的一致的无线通信或网络通信。 [0116] 计算系统或计算机可以包括与总线、用户接口和存储器控制器电连接的微处理器。 它还可以包括闪存设备。 闪存设备可以通过存储控制器存储N位数据。 N位数据由微处理器处理或将由微处理器处理,N可以为1或大于1的整数。当计算系统或计算机为移动设备时,可额外提供电池以提供计算的工作电压 系统或计算机。 [0117] 对于本领域的普通技术人员来说,计算系统或计算机还可以包括应用芯片组、相机图像处理器(CIS)、移动动态随机存取存储器(DRAM)等应该是显而易见的。 存储器控制器和闪存设备可以构成使用非易失性存储器来存储数据的固态驱动器/磁盘(SSD)。 [0118]上述过程、功能、方法和/或软件可以被记录、存储或固定在一个或多个计算机可读存储介质中,该存储介质包括要由计算机实现以使处理器执行或执行程序的程序指令 指示。 媒体还可以单独或与程序指令、数据文件、数据结构等组合地包括。 计算机可读存储介质的示例包括诸如硬盘、软盘和磁带之类的磁介质; 光媒体,如 CD ROM 盘和 DVD; 磁光介质,例如光盘; 以及专门用于存储和执行程序指令的硬件设备,例如只读存储器(ROM)、随机存取存储器(RAM)、闪存等。 程序指令的示例包括机器代码(例如由编译器生成)和包含可由计算机使用解释器执行的更高级别代码的文件。 所描述的硬件设备可以被配置为充当一个或多个软件模块以执行上述操作和方法,反之亦然。 此外,计算机可读存储介质可以分布在通过网络连接的计算机系统之间,并且可以以分散方式存储和执行非暂时性计算机可读代码或程序指令。 [0119] 上面已经描述了许多示例。 然而,应该理解可以进行各种修改。 例如,如果以不同的顺序执行所描述的技术和/或如果所描述的系统、架构、设备或电路中的组件以不同的方式组合和/或由其他组件替换或补充或 他们的等价物。 因此,其他实施方式在所附权利要求的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.066 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20130346212A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.077 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.077 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270673(Integer), KR101622169B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270673(Integer), KR1020110136068A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270673(Integer), US20110306324A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270673(Integer), US20130346212A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270673(Integer), US8548504B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270673(Integer), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20130346212A1(String), US20130346212A1(String), 1387987200(Integer), 270673(Integer), 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.148 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), JANG, KYUNG HUN(String), KWON, TAE SOO(String), CHOI, HYUN HO(String), LIM, JONG BU(String), SHIN, WON JAE(String), 三星电子株式会社(String), JANG KYUNG HUN(String), KWON TAE SOO(String), CHOI HYUN HO(String), LIM JONG BU(String), SHIN WON JAE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184993(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184993(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: JANG, KYUNG HUN(String), JANG KYUNG HUN(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: KWON, TAE SOO(String), KWON TAE SOO(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: CHOI, HYUN HO(String), CHOI HYUN HO(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIM, JONG BU(String), LIM JONG BU(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHIN, WON JAE(String), SHIN WON JAE(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.210 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.211 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.211 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184993(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75931(Integer), 2(Integer), 184993(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75932(Integer), 2(Integer), 184993(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75933(Integer), 2(Integer), 184993(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75934(Integer), 2(Integer), 184993(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75935(Integer), 2(Integer), 184993(Integer), 4(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.283 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.293 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10775896B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 根据与移动终端操作相关的输入来控制多个对象显示的方法及其移动终端(String), US10775896B2(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US16/227823(String), 1545235200(Integer), US10775896B2(String), 1600099200(Integer), 1600099200(Integer), 美国(String), 4(Integer), KR(String), 17(Integer), 113(Integer), CN102736849A | JP1456713S | JP1976007453A | JP2003345492A | JP2004240757A | JP2004254281A | JP2006055398A | JP2006513487A | JP2007094378A | JP2007511851A | JP2007538203A | JP2008247873A | JP2008268689A | JP2009122093A | JP2011007701A | JP2011028677A | JP2012038292A | JP2012118652A | JP2012138892A | JP2012150205A | JP2012217677A | JP2012230572A | JP2012243091A | JP2012509544A | JP2012521595A | JP2012533751A | JP2013174279A | JP2013245447A | JP2014003854A | JP2014069285A | JP2014082404A | JP2014215737A | JP2015061605A | JP5107453B1 | JPWO2005112336A1 | JPWO2011125790A1 | KR1020050086960A | KR1020050086963A | KR1020110016194A | KR1020120071468A | KR1020120129697A | RU2011110239A | RU2455679C2 | US20050108655A1 | US20060053385A1 | US20060101352A1 | US20080250312A1 | US20080282202A1 | US20090046075A1 | US20090051648A1 | US20090106694A1 | US20090197635A1 | US20090327272A1 | US20100060599A1 | US20100070926A1 | US20100125811A1 | US20100125816A1 | US20100134312A1 | US20100164992A1 | US20100217685A1 | US20100248788A1 | US20100281374A1 | US20110016423A1 | US20110041101A1 | US20110175930A1 | US20110281633A1 | US20110312349A1 | US20120030569A1 | US20120032901A1 | US20120154294A1 | US20120162261A1 | US20120166997A1 | US20120190407A1 | US20120192121A1 | US20120200513A1 | US20120246586A1 | US20120264512A1 | US20120274541A1 | US20120299847A1 | US20130120295A1 | US20130120447A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130191784A1 | US20130219277A1 | US20130278484A1 | US20140035946A1 | US20140059472A1 | US20140101610A1 | US20140115493A1 | US20140139637A1 | US20140143737A1 | US20140149903A1 | US20140152597A1 | US20140181751A1 | US20140189601A1 | US20140215310A1 | US20150077333A1 | US8191011B2 | WO2008117827A1 | WO2010117827A2 | WO2012061917A1 | WO2012066591A1 | WO2012083277A2 | WO2012108620A2 | WO2012159268A1 | WO2012169190A1(String), 21(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184994(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\852de00609a14646b06a62f4e61d9db9.png(String), 184994(Integer), 852de00609a14646b06a62f4e61d9db9.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 根据与移动终端操作相关的输入来控制多个对象显示的方法及其移动终端(String), US10775896B2(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US16/227823(String), 1545235200(Integer), US10775896B2(String), 1600099200(Integer), 1600099200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 17(Integer), 113(Integer), CN102736849A | JP1456713S | JP1976007453A | JP2003345492A | JP2004240757A | JP2004254281A | JP2006055398A | JP2006513487A | JP2007094378A | JP2007511851A | JP2007538203A | JP2008247873A | JP2008268689A | JP2009122093A | JP2011007701A | JP2011028677A | JP2012038292A | JP2012118652A | JP2012138892A | JP2012150205A | JP2012217677A | JP2012230572A | JP2012243091A | JP2012509544A | JP2012521595A | JP2012533751A | JP2013174279A | JP2013245447A | JP2014003854A | JP2014069285A | JP2014082404A | JP2014215737A | JP2015061605A | JP5107453B1 | JPWO2005112336A1 | JPWO2011125790A1 | KR1020050086960A | KR1020050086963A | KR1020110016194A | KR1020120071468A | KR1020120129697A | RU2011110239A | RU2455679C2 | US20050108655A1 | US20060053385A1 | US20060101352A1 | US20080250312A1 | US20080282202A1 | US20090046075A1 | US20090051648A1 | US20090106694A1 | US20090197635A1 | US20090327272A1 | US20100060599A1 | US20100070926A1 | US20100125811A1 | US20100125816A1 | US20100134312A1 | US20100164992A1 | US20100217685A1 | US20100248788A1 | US20100281374A1 | US20110016423A1 | US20110041101A1 | US20110175930A1 | US20110281633A1 | US20110312349A1 | US20120030569A1 | US20120032901A1 | US20120154294A1 | US20120162261A1 | US20120166997A1 | US20120190407A1 | US20120192121A1 | US20120200513A1 | US20120246586A1 | US20120264512A1 | US20120274541A1 | US20120299847A1 | US20130120295A1 | US20130120447A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130191784A1 | US20130219277A1 | US20130278484A1 | US20140035946A1 | US20140059472A1 | US20140101610A1 | US20140115493A1 | US20140139637A1 | US20140143737A1 | US20140149903A1 | US20140152597A1 | US20140181751A1 | US20140189601A1 | US20140215310A1 | US20150077333A1 | US8191011B2 | WO2008117827A1 | WO2010117827A2 | WO2012061917A1 | WO2012066591A1 | WO2012083277A2 | WO2012108620A2 | WO2012159268A1 | WO2012169190A1(String), \20230420\852de00609a14646b06a62f4e61d9db9.png(String), 21(Integer), 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 1. A method of controlling a display of a plurality of areas according to a motion of a mobile terminal, the method comprising:dividing a display screen into the plurality of areas according to a predefined layout;identifying a shaking motion of the mobile terminal while the plurality of areas are displayed, wherein the shaking motion comprises a first movement associated with a first direction and a second movement associated with a second direction opposite to the first direction;determining whether the first and second direction of the shaking motion corresponds to a reconfiguration direction in which the layout changes; andin response to the shaking motion being performed a predetermined number of times:identifying at least one area of the plurality of areas to be moved according to the reconfiguration direction,maintaining remaining areas of the plurality of areas that are not to be moved in same area in which the remaining areas are displayed before the shaking motion, wherein the at least one area to be moved and the remaining areas to be maintained in the same area are identified according to a preset arrangement rule,moving all of the identified at least one area of the plurality of areas to at least one different location within the layout in which the identified at least one area of the plurality of areas was not displayed before the shaking motion, such that the plurality of areas are arranged according to the preset arrangement rule and remain being displayed on the display screen after the shaking motion; anddisplaying at least one icon for adjusting a number of the plurality of areas in the layout andrearranging the plurality of areas when adding or removing one or more areas in response to the shaking motion of the mobile terminal being performed number of times while a touch on the at least one icon for adjusting is maintained.(String), 1.一种根据移动终端的运动控制多个区域显示的方法,该方法包括:根据预定布局将显示屏幕划分为多个区域;识别显示多个区域时移动终端的摇动动作,其中摇动动作包括与第一方向相关联的第一运动和与第一方向相反的第二方向相关联的第二运动;判断摇动的第一方向和第二方向是否对应于布局变化的重构方向;和响应于执行预定次数的摇动动作:根据重构方向识别要移动的多个区域中的至少一个区域,将多个待移动区域中的剩余区域保持在同一区域中,所述剩余区域在摇动动作之前显示在同一区域中,其中,所述至少一个待移动区域与所述剩余待移动区域保持在同一区域中根据预设排列规则识别,将多个区域中的所有已识别的至少一个区域移动到布局内的至少一个不同位置,其中在摇动动作之前未显示多个区域中的已识别的至少一个区域,使得多个区域按照预设排列规则排列,并在摇动后保持显示在显示屏上;和显示至少一个图标,用于调整布局中多个区域的数量,以及当响应于移动终端被执行多次摇动动作而增加或移除一个或多个区域时,重新排列多个区域,同时保持对至少一个用于调整的图标的触摸。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 2. The method of claim 1, further comprising:determining whether one of the plurality of areas is applied to the preset arrangement rule in response to the shaking motion of the mobile terminal.(String), 2.如权利要求1所述的方法,还包括:响应于移动终端的摇动动作,确定多个区域之一是否适用于预设排列规则。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 3. The method of claim 1, wherein the preset arrangement rule is in consideration of the properties of the plurality of areas, the properties regarding the horizontal and vertical formats of the plurality of areas.(String), 3.如权利要求1所述的方法,其中预设排列规则是考虑了多个区域的属性,即多个区域的横向和纵向格式的属性。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 4. The method of claim 1, wherein the plurality of areas include shortcut icons for executing applications.(String), 4.如权利要求1所述的方法,其中多个区域包括用于执行应用程序的快捷方式图标。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 5. The method of claim 4, further comprising:detecting a direction of the shaking motion corresponding to at least one of an up-down direction, a left-right direction, or a diagonal direction of the mobile terminal.(String), 5.如权利要求4所述的方法,还包括:检测与移动终端的上下方向、左右方向或对角方向中的至少一个方向对应的摇动运动的方向。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 6. The method of claim 1, further comprising:determining whether a number of shaking motions of the mobile terminal is equal to or greater than a predetermined number in response to the shaking motion of the mobile terminal; andadding a predetermined number of areas to a current page in response to the number of the shaking motions being equal to or greater than the predetermined number.(String), 6.如权利要求1所述的方法,还包括:响应于移动终端的摇动动作,判断移动终端的摇动动作次数是否等于或大于预定次数;和响应于摇动动作的数量等于或大于预定数量,将预定数量的区域添加到当前页面。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 7. The method of claim 6, wherein the added areas include areas of a next page.(String), 7.如权利要求6所述的方法,其中添加的区域包括下一页的区域。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 8. The method of claim 1, further comprising:determining whether one of the plurality of areas is touched; determining whether the shaking motion of the mobile terminal is received while the touch is maintained; andin response to identifying the shaking motion of the mobile terminal while the touch is maintained, rearranging remaining areas except for the touched areas in response to the shaking motion of the mobile terminal.(String), 8.如权利要求1所述的方法,还包括:确定多个区域之一是否被触摸;判断在保持触摸的同时是否接收到移动终端的摇动动作;和响应于在保持触摸的同时识别移动终端的摇动动作,响应于移动终端的摇动动作重新排列除了被触摸区域之外的剩余区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 9. The method of claim 8, further comprising:searching for areas associated with an area belonging to the touched area corresponding to a property of the area in response to the shaking motion of the mobile terminal;adding the searched areas to position where the area is not displayed; anddisplaying the searched areas.(String), 9.如权利要求8所述的方法,还包括:响应于移动终端的摇动运动,搜索与区域的属性对应的属于触摸区域的区域相关联的区域;将搜索到的区域添加到未显示区域的位置;和显示搜索到的区域。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 10. The method of claim 9, further comprising: searching for pictures associated with a person appearing on a portrait in response to the area belonging to the touch area being the portrait; andrespectively displaying the searched pictures.(String), 10.如权利要求9所述的方法,还包括:响应于属于触摸区域的区域是人像,搜索与出现在人像上的人物相关联的图片;和分别显示搜索到的图片。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 11. A mobile terminal for controlling a display of a plurality of areas according to a shaking motion of the mobile terminal, the mobile terminal comprising:a display screen divided into the plurality of areas according to a predefined layout;a sensor device configured to detect the shaking motion of the mobile terminal; andat least one processor configured to:identify, by using the sensor device, the shaking motion of the mobile terminal while the plurality of areas are displayed, wherein the shaking motion comprises a first movement associated with a first direction and a second movement associated with a second direction opposite to the first direction,determine whether the first and second direction of the shaking motion corresponds to a reconfiguration direction in which the layout changes; andin response to the shaking motion being performed a predetermined number of times:identify at least one area of the plurality of areas to be moved according to the reconfiguration direction, maintain all remaining areas of the plurality of areas that are not to be moved in same area in which the remaining areas are displayed before the shaking motion, wherein the at least one area to be moved and the remaining areas to be maintained in the same area are identified according to a preset arrangement rule,move all of the identified at least one area of the plurality of areas to at least one different location within the layout in which the identified at least one area of the plurality of areas was not displayed before the shaking motion, such that the plurality of areas are arranged according to the preset arrangement rule and remain being displayed on the display screen after the shaking motion, anddisplay at least one icon for adjusting a number of the plurality of areas in the layout and rearranging the plurality of areas when adding or removing one or more areas in response to the shaking motion of the mobile terminal being performed number of times while a touch on the at least one icon for adjusting is maintained.(String), 11.一种根据移动终端的摇动动作控制多个区域显示的移动终端,该移动终端包括:显示屏按照预定布局划分为多个区域;传感器装置,用于检测移动终端的晃动动作;和至少一个处理器配置为:通过传感器装置识别显示多个区域时移动终端的摇动动作,其中摇动动作包括与第一方向相关联的第一运动和与第一方向相反的第二方向相关联的第二运动,判断摇动的第一方向和第二方向是否对应于布局变化的重构方向;和响应于执行预定次数的摇动动作:根据重构方向识别多个待移动区域中的至少一个区域,将多个待移动区域中的所有剩余区域保持在摇动动作之前显示剩余区域的同一区域中,其中根据预设排列规则识别出至少一个待移动区域和同一区域中的其余待维护区域,将多个区域中的所有已识别的至少一个区域移动到布局内的至少一个不同位置,其中在摇动动作之前未显示多个区域中的已识别的至少一个区域,使得多个区域按照预设排列规则排列,并在摇动后保持显示在显示屏上;显示至少一个图标,用于在添加或删除一个或多个区域时响应于在触摸保留至少一个调整图标。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 12. The mobile terminal of claim 11, wherein the at least one processor is further configured to determine whether one of the plurality of areas is applied to the preset arrangement rule in response to the shaking motion of the mobile terminal.(String), 12.如权利要求11所述的移动终端,其中至少一个处理器还用于响应于移动终端的摇动动作,判断多个区域之一是否适用于预设排列规则。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 13. The mobile terminal of claim 11, wherein the preset arrangement rule is in consideration of the properties of the plurality of areas, the properties regarding the horizontal and vertical formats of the plurality of areas.(String), 13.如权利要求11所述的移动终端,其中预设排列规则是考虑了多个区域的属性,即多个区域的横向和纵向格式的属性。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 14. The mobile terminal of claim 11, wherein the at least one processor is further configured to:determine whether a number of shaking motions of the mobile terminal detected through the sensor device is equal to or greater than a predetermined number, andadd a predetermined number of areas to position of a current page in response to the number of the shaking motions being equal to or greater than the predetermined number.(String), 14.如权利要求11所述的移动终端,其中至少一个处理器还被配置为:确定通过传感器装置检测到的移动终端的摇动动作的次数是否等于或大于预定次数,以及响应于大于或等于预定数量的摇动动作,在当前页面的位置添加预定数量的区域。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 15. The mobile terminal of claim 14, wherein the added areas include areas of a next page.(String), 15.如权利要求14所述的移动终端,其中添加的区域包括下一页的区域。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 16. The mobile terminal of claim 11, wherein the at leas t one processor is further configured to:determine whether any one of the plurality of areas is selected, andin response to identifying the shaking motion of the mobile terminal while the selection is maintained, switch positions of remaining areas except for the selected area in response to detecting the shaking motion of the mobile terminal through the sensor device while the selection is maintained.(String), 16.如权利要求11所述的移动终端,其中至少一个处理器还被配置为:确定是否选择了多个区域中的任何一个,并且响应于在保持选择的同时识别移动终端的摇动动作,响应于在保持选择的同时通过传感器装置检测到移动终端的摇动动作,切换除所选区域之外的其余区域的位置。(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 17. The mobile terminal of claim 16, wherein, in response to detecting the shaking motion of the mobile terminal through the sensor device while the selection is maintained, the at least one processor is further configured to:search for areas associated with an area belonging to the selected area based on a property of the selected area,add the searched areas to position where the area is not displayed, and control the display to display the searched areas.(String), 17.如权利要求16所述的移动终端,其中,响应于在保持选择的同时通过传感器设备检测到移动终端的摇动动作,至少一个处理器还被配置为:基于所选区域的属性搜索与属于所选区域的区域关联的区域,将搜索到的区域添加到不显示该区域的位置,控制显示器显示搜索到的区域。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 18. The mobile terminal of claim 17, wherein, in response to the selected area being a portrait, the at least one processor is further configured to:search for pictures associated with a person appearing on the portrait, and control the display to display the searched pictures.(String), 18.如权利要求17所述的移动终端,其中,响应于所选区域为人像,所述至少一个处理器还用于:查找人像中出现的人物相关联的图片,并控制显示器显示查找到的图片。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 19. The mobile terminal of claim 11, wherein the plurality of areas include shortcut icons for executing applications.(String), 19.如权利要求11所述的移动终端,其中多个区域包括用于执行应用程序的快捷方式图标。(String), 1(Integer), 18(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 20. The mobile terminal of claim 19, wherein the sensor device comprises a motion sensor for detecting the shaking motion of the mobile terminal.(String), 20.如权利要求19所述的移动终端,其中传感器装置包括用于检测移动终端的晃动运动的运动传感器。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.350 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184994(Integer), 21. The mobile terminal of claim 19, wherein the sensor device is further configured to detect a direction of the shaking motion corresponding to at least one of an up-down direction, a left-right direction, or a diagonal direction of the mobile terminal.(String), 21.如权利要求19所述的移动终端,其中传感器装置还被配置为检测对应于移动终端的上下方向、左右方向或对角线方向中的至少一个的摇动运动的方向。(String), 1(Integer), 20(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184994(Integer), PRIORITY [0001]This application is a continuation application of prior application Ser. No. 14/105,735, filed on Dec. 13, 2013, which was based on and claimed priority under 35 U.S.C § 119(a) of a Korean patent application number 10-2013-0019508, filed on Feb. 22, 2013, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein in its entirety. BACKGROUND OF THE INVENTION 1. Field of the Invention [0002]The present invention relates generally to an apparatus and method for managing a plurality of objects that are displayed on a touch screen. More particularly, the present invention relates to an apparatus and method for allowing a user of a mobile terminal to easily change a display of a plurality of objects on a touch screen according to a motion of the mobile terminal. 2. Description of the Related Art [0003]A touch screen with a touch panel mounted on a display device displays images and allows a user to easily input commands without using a keyboard or a mouse. The touch screen has been widely used in various electronic devices, such as a mobile terminal, a navigation system, a TV, Automated Teller Machines (ATMs), a Point-Of-Sale (POS) system, and the like. [0004]For example, with the variety of services and additional functions that can be provided by mobile terminals, many recent mobile terminals provide a Graphic User Interface (GUI) based on a touch screen. [0005]In order to raise the effective value of such mobile terminals and meet users' needs, various applications executable in mobile terminals are being developed. [0006]A mobile terminal can store basic applications developed by the mobile terminal's manufacturing company, as well as additional applications downloaded from application sales web sites through the Internet, and execute the applications. [0007]Accordingly, a mobile terminal, such as the latest smart phone, tablet PC, and the like, stores at least hundreds of applications, and shortcut keys for executing the applications individually are displayed in the form of icons on the touch screen of the mobile terminal. A user can touch one of the icons displayed on the touch screen of a mobile terminal to thus execute a desired application on the mobile terminal. Various visual objects, such as widgets, pictures, document, etc., other than the shortcut keys, may also be displayed on the touch screen of the mobile terminal. [0008]However, as the number of such various visual objects increases, another issue arises. The number of objects that can be displayed on the small screen of a mobile terminal is limited although the mobile terminal stores many visual objects. [0009]Accordingly, due to the spatial limitation of a display screen, there is a need for classifying and arranging visual objects that can be displayed on the screen. However, arranging the components of a layout at regular intervals is insufficient, and it is necessary for a user to be able to conveniently manage visual objects displayed on the screen of a mobile terminal, such as editing, moving, or deleting the visual objects. According to the related art, when a user wants to change a display of objects, the user should convert the screen of his/her mobile terminal into an Edit environment, and input commands for deleting or correcting objects, which causes onerousness and inconvenience and requires a long time for editing. [0010]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. [0011]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY OF THE INVENTION [0012]Aspects of the present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide an apparatus and method for allowing a user to conveniently change the components of a layout in which a plurality of objects are arranged according to his/her desired pattern. [0013]Another aspect of the present invention is to provide an apparatus and method for easily controlling an arrangement of a plurality of objects and a display of a layout in which the objects are arranged according to a motion of a mobile terminal. [0014]In accordance with an aspect of the present invention, a method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes displaying a layout including a plurality of areas in which a plurality of objects are respectively displayed, receiving the input related to the operation of the mobile terminal, changing one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. [0015]In accordance with another aspect of the present invention, a mobile terminal for controlling a display of a plurality of objects according to an input related to operation of the mobile terminal is provided. The mobile terminal includes a display unit configured to display a layout including a plurality of areas in which the plurality of objects are respectively displayed, a sensor module configured to detect the input related to the operation of the mobile terminal, and a controller configured to change one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and to control the display unit to display a layout including the changed areas. [0016]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention; [0019]FIG. 2 is a front perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0020]FIG. 3 is a rear perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0021]FIG. 4 is a flowchart of a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0022]FIGS. 5A through 8B show examples for explaining a process in which areas constituting a layout change according to directions of reciprocating motions of a mobile terminal according to an exemplary embodiment of the present invention; [0023]FIGS. 9A to 9D show examples for explaining a process in which areas constituting a layout change according to a breath according to an exemplary embodiment of the present invention; [0024]FIGS. 10A to 11D are views for explaining an arrangement rule of a layout according to an exemplary embodiment of the present invention; [0025]FIG. 12 is a flowchart for explaining a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0026]FIGS. 13A and 13B show examples for explaining a process in which different objects are respectively displayed on areas constituting a layout according to the property of a touched object according to an exemplary embodiment of the present invention; [0027]FIGS. 14A and 14B are flowcharts for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0028]FIGS. 15A to 15I show examples for explaining a process of adjusting a number of areas constituting a layout in the mobile terminal, according to an exemplary embodiment of the present invention; [0029]FIG. 16 is a flowchart for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; and [0030]FIGS. 17A to 17C show examples for explaining a process of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention. [0031]Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0032]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. [0033]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0034]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0035]It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. [0036]The exemplary embodiments that will be described below relate to a hand-held terminal, however, an apparatus and method for managing a plurality of objects displayed on a touch screen, according to exemplary embodiments of the present invention, may be applied to various electronic devices with touch screens, such as a navigation system, a television (TV), an Automated Teller Machine (ATM), a Point-Of-Sale (POS) system, and the like, as well as a mobile terminal, such as a mobile phone, a smart phone, a tablet PC, and the like. [0037]Also, in the following description, a mobile terminal may be a flexible device or a flexible display device. As a representative mobile terminal, a mobile phone is assumed, and some components of such a mobile terminal may be omitted or changed as necessary. [0038]Exemplary embodiments of the present invention provide a method of controlling a display of a plurality of objects according to an input related to a motion of a mobile terminal. Exemplary embodiments of the present invention includes an operation of changing, if an input related to a motion of the mobile terminal is received when a layout including areas in which the plurality of objects are displayed is displayed, one or more areas corresponding to the input related to the motion of the mobile terminal among the areas constituting the layout; and an operation of displaying a layout comprised of the changed areas. The input related to the motion of the mobile terminal may correspond to a motion of the mobile terminal, a user's breath, a gesture, and the like. According to exemplary embodiments of the present invention, if an input related to a motion of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged. In this case, objects that are respectively displayed in the remaining areas may be objects searched in correspondence to the property of an object displayed on the touched area. Thereby, a user can easily change components corresponding to the areas of a layout, as well as changing the areas of the layout. [0039]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention. [0040]Referring to FIG. 1, the mobile terminal 100 may be connected to an external electronic device (not shown) using at least one of a communication module 120, a connector 165, and an earphone connecting jack 167. The external electronic device may include an earphone, an external speaker, a Universal Serial Bus (USB) memory, a battery charger, a Cradle/Dock, a Digital Multimedia Broadcasting (DMB) antenna, a mobile payment system, healthcare equipment (a blood glucose meter, etc.), a game, a vehicle navigation system, and the like, which can be removably connected to the mobile terminal 100 through a line. The external electronic device may include a Bluetooth communication apparatus, a Near Field Communication (NFC) apparatus, a WiFi Direct communication apparatus, a Wireless Access Point (WAP), and the like, which can be connected to the mobile terminal 100 in a wireless fashion. The mobile terminal 100 may be connected to one of other mobile terminals or electronic devices (for example, a mobile phone, a smart phone, a tablet PC, a desktop PC, and a server) in a wired/wireless fashion. [0041]The mobile terminal 100 includes a touch screen 190 and at least one touch screen controller 195. The mobile terminal 100 may further include a controller 110, the communication module 120, a multimedia module 140, a camera module 150, an input/output module 160, a sensor module 170, a storage unit 175, and a power supply unit 180. [0042]The communication module 120 includes a mobile communication module 121, a sub communication module 130, and a broadcasting communication module 141. [0043]The sub communication module 130 includes at least one of a Wireless LAN (WLAN) module 131 and a short-range communication module 132. The multimedia module 140 includes at least one of an audio play module 142 and a video play module 143. The camera module 150 may include at least one of a first camera 151 and a second camera 152. The camera module 150 may also include at least one of a body tube 155 for zooming in/out the first and/or second camera 151 or 152, a motor unit 154 for controlling the movement of the body tube 155, and a flash 153 for providing a light source for photographing, according to the main purpose of the mobile terminal 100. The input/output module 160 may includes at least one of a button 161, a microphone 162, a speaker 163, a vibration device 164, the connector 165, and a keypad 166. [0044]The controller 110 may include a CPU 111, a Read Only Memory (ROM) 112 that stores control programs for controlling the mobile terminal 100, and a Random Access Memory (RAM) 113 that stores signals or data received from the outside or is used as a memory area for tasks being performed by the mobile terminal 100. The CPU 111 may include one or more cores, such as a single core, a dual core, a triple core, or a quad core. The CPU 111, ROM 112, and RAM 113 may be connected to each other through internal buses. [0045]Also, the controller 110 may control the communication module 120, the multimedia module 140, the camera module 150, the input/output module 160, the sensor module 170, the storage unit 175, the power supply unit 180, the touch screen 190, and the touch screen controller 195. [0046]When a user input device, such as an input unit 168 or a user's finger, touches, approaches, or is located in proximity to at least one of a plurality of objects or items displayed on the touch screen 190, the controller 110 senses a user input, and identifies an object corresponding to a location at which the user input has been sensed on the touch screen 190. The user input through the touch screen 190 may be one of a direct touch input of directly touching an object, and a hovering input which is an indirect touch input of approaching an object within a predetermined identification distance without directly touching the object. For example, when a user brings the input unit 168 close to the touch screen 190, an object located straightly below the input unit 168 may be selected. The user input may be a gesture input through the camera module 150, a switch/button input through the button 161 or the keypad 166, or a voice input through the microphone 16, other than a user input through the touch screen 190. [0047]The object or item (such as a function item) may be at least one of an application, a menu, document, a widget, a picture, video, E-mail, a Short Message Service (SMS) message, a Multimedia Message Service (MMS) message, and the like, which have been or can be displayed on the touch screen 190 of the mobile terminal 100. The object or item can be selected, executed, deleted, canceled, stored, or changed by the user input device. The item may be a button, an icon (such as a shortcut icon), a thumbnail image, or a folder that stores at least one object in a mobile terminal. The item may be displayed in the form of an image, text, and the like. [0048]A shortcut item is an image that is displayed on the touch screen 190 to quickly execute a call, a contact list, a menu, etc., which are provided by each application or by the mobile terminal 100. If a command or selection for executing a shortcut item is received, the corresponding application is executed. [0049]When the input unit 168 approaches the touch screen 190 or is placed in proximity to the touch screen 190, the controller 110 may sense a user input event such as a hovering event. If a user input event is generated with respect to a predetermined item or according to a predetermined method, the controller 110 performs predetermined program operation corresponding to the user input event. [0050]The controller 110 may output a control signal to the input unit 168 or the vibration device 164. The control signal may include information regarding a vibration pattern, and the input unit 168 or the vibration device 164 may generate vibration according to the vibration pattern. The information regarding the vibration pattern may represent a vibration pattern, an identifier of a vibration pattern, or the like. Alternatively, the control signal may include only a request for generation of vibration. [0051]The mobile terminal 100 may include at least one of the mobile communication module 121, the WLAN module 131, and the short-range communication module 132, according to the function of the mobile terminal 100. [0052]The mobile communication module 121 may connect the mobile terminal 100 to an external electronic device through mobile communication using one or more antennas (not shown) under the control of the controller 110. The mobile communication module 121 may transmit/receive radio signals for a voice call, a video call, a SMS message, or a MMS message to/from a mobile phone (not shown), a smart phone (not shown), a tablet PC (not shown), or another electronic device (not shown) when the corresponding phone number is input to the mobile terminal 100. [0053]The sub communication module 130 may include at least one of the WLAN module 131 and the short-range communication module 132 as described above. For example, the sub communication module 130 may include one of the WLAN module 131 and the short-range communication module 132, or both the WLAN module 131 and the short-range communication module 132. [0054]The WLAN module 131 may be connected to the Internet at a place in which a WAP has been installed, under the control of the controller 110. The WLAN module 131 supports the IEEE802.11x standard. The short-range communication module 132 performs short-range communication between the mobile terminal 100 and an external electronic device in a wireless fashion under the control of the controller 110. The short-range communication may include Bluetooth, Infrared Data Association (IrDA), WiFi-Direct communication, NFC, and the like. [0055]The controller 110 may transmit a control signal according to a haptic pattern to the input unit 168 through the sub communication module 130. [0056]The broadcasting communication module 141 may receive broadcasting signals (for example, TV broadcasting signals, radio broadcasting signals, or data broadcasting signals) and broadcasting additional information (for example, an Electric Program Guide (EPS) or an Electric Service Guide (ESG)) transmitted from a broadcast station through a broadcasting communication antenna (not shown), under the control of the controller 110. [0057]The multimedia module 140 may include the audio play module 142 and the video play module 143 as described above. The audio play module 142 may reproduce a digital audio file (for example, a file with the extension “.mp3”, “. wma”, “.ogg” or “.wav”) that is stored in the storage unit 175 or received from an external device, under the control of the controller 110. The video play module 143 may reproduce a digital video file (for example, a file with the extension “.mpeg”, “. mpg”, “.mp4”, “.avi”, “.mov”, or “.mkv”) that is stored or received, under the control of the controller 110. The multimedia module 140 may be integrated with the controller 110. [0058]The camera module 150 may include at least one of the first and second cameras 151 and 152 for photographing still images or moving images under the control of the controller 110. The camera module 150 may also include at least one among the body tube 155 for zooming in/out to photograph a subject, the motor unit 154, and the flash 153 for providing a secondary light source required for photographing the subject. The first camera 151 may be disposed in the front side of the mobile terminal 100, and the second camera 152 may be disposed in the rear side of the mobile terminal 100. [0059]Each of the first and second cameras 151 and 152 may include a lens system, an image sensor, and the like. Each of the first and second cameras 151 and 152 converts an optical signal received (or photographed) through the lens system into an electrical image signal, and outputs the electrical image signal to the controller 110. Accordingly, a user can photograph a moving image or a still image through the first and second cameras 151 and 152. [0060]The input/output module 160 may include at least one among at least one button 161, at least one microphone 162, at least one speaker 163, at least one vibration device 164, the connector 165, the keypad 166, the earphone connecting jack 167, and the input unit 168. However, the input/output module 160 is not limited to the above-mentioned devices, and a cursor control, such as a mouse, a trackball, a joystick, or cursor direction keys, may also be provided to control the movement of a cursor on the touch screen 190. [0061]The button 161 may be formed on the front, side, or rear surface of the housing (or case) of the mobile terminal 100, and may include at least one among a power/lock button, a volume button, a menu button, a home button, a back button, and a search button. [0062]The microphone 162 may receive a voice or sound under the control of the controller 110 to generate an electrical signal. [0063]The speaker 163 may output sound corresponding to various signals or data (for example, radio data, broadcasting data, digital audio data, digital video data, etc.) out of the mobile terminal 100 under the control of the controller 110. The speaker 163 may output sound (for example, button manipulation sound corresponding to a call, currency connection sound, the other party's voice, etc.) corresponding to a function that is performed by the mobile terminal 100. One or more speakers 163 may be provided at one or more appropriate locations on the housing of the mobile terminal 100. [0064]The vibration device 164 may convert an electrical signal into mechanical vibration under the control of the controller 110. For example, if a voice or video call is made by another device (not shown) when the mobile terminal 100 is in a vibration mode, the vibration device 164 operates. One or more vibration devices 164 may be provided in the housing of the mobile terminal 100. The vibration device 164 may operate in correspondence to a user input through the touch screen 190. [0065]The connector 165 may be used as an interface for connecting the mobile terminal 100 to an external electronic device or a power source (not shown). The controller 110 may transmit data stored in the storage unit 175 to an external electronic device or receive data from the external electronic device through a wired cable connected to the connector 165. The mobile terminal 100 may receive power from a power source or charge a battery using the power source through the wired cable connected to the connector 165. [0066]The keypad 166 may receive a key input from a user to control the mobile terminal 100. The keypad 166 includes a physical keypad (not shown) formed on the mobile terminal 100 or a virtual keypad (not shown) displayed on the touch screen 190. The physical keypad formed on the mobile terminal 100 may be excluded according to the performance or structure of the mobile terminal 100. [0067]The earphone (not shown) may be inserted into the earphone connecting jack 167 to connect to the mobile terminal 100. [0068]The input unit 168 may be inserted into and held in the mobile terminal 100, and when in use, the input unit 168 may be drawn or separated from the mobile terminal 100. A detachment/attachment recognition switch 169 that operates in correspondence to attachment and detachment of the input unit 168 may be provided in an area of the mobile terminal 100 into which the input unit 168 is inserted. The detachment/attachment recognition switch 169 may output a signal corresponding to attachment/separation of the input unit 168 to the controller 110. The detachment/attachment recognition switch 169 may be configured to directly or indirectly contact the input unit 168 when the input unit 169 is attached in the mobile terminal 100. Accordingly, the detachment/attachment recognition switch 169 generates a signal (i.e., a signal for notifying attachment or separation of the input unit 168) corresponding to attachment or separation of the input unit 168 based on whether the detachment/attachment recognition switch 169 contacts the input unit 168, and outputs the signal to the controller 110. [0069]The sensor module 170 may include at least one sensor for detecting the state of the mobile terminal 100. For example, the sensor module may include at least one sensor among a proximity sensor (not shown) for detecting an approach to the mobile terminal 100, an ambient light sensor (not shown) for detecting the ambient light intensity around the mobile terminal 100, a motion sensor (not shown) for detecting a motion (for example, rotation, acceleration, vibration) of the mobile terminal 100, a geo-magnetic sensor (not shown) for detecting a point of the compass of the mobile terminal 100 using the earth's magnetic field, a gravity sensor (not shown) for detecting a direction in which gravity is applied, an altimeter (not shown) for measuring atmospheric pressure to detect an altitude, and a GPS module 157. A camera sensor for sensing a user's gesture may also be included in the sensor module 170. [0070]The motion sensor among the above-mentioned sensors senses the location, movement, and the like of the mobile terminal 100 using an acceleration sensor, a gyro sensor, a tilt sensor, or their combinations. However, the sensors are not limited to the above-mentioned sensors, and may include other types of a sensor capable of sensing the reciprocating motions, movement directions, and the like of the mobile terminal 100. [0071]Sensing data (that is, motion information) output through the motion sensors may have a direction and a magnitude. For example, an acceleration sensor for sensing the acceleration of the mobile terminal 100 can sense acceleration with respect to at least one reference-axis direction of x, y, and z axes, and output the acceleration information. The reference-axis may be an axis (for example, the up-down (z-axis), left-right (x-axis), and front-rear (y-axis) directions of the mobile terminal 100) according to the direction of the mobile terminal 100, or may be an axis according to the direction of gravity (the direction (z-axis) of gravity and directions (z and y axes) perpendicular to the direction of gravity). [0072]The sensor module 170 may further include a calculator (not shown) for integrating sensed angular velocity, velocity, etc. over time to calculate a rotation angle, a direction, velocity, a travel distance, a location, a trajectory, and the like according to a motion of the mobile terminal 100, and output the calculated information. The calculator may be included in the controller 110. The calculator may also include a frequency filter for blocking or passing a specific band of a signal such as sensed acceleration in order to calculate a trajectory, etc. or effectively analyze the direction of a motion. [0073]When the sensor module 170 includes the calculator, the calculator may calculate a direction or angle in or at which the mobile terminal 100 moves, and transfer the result of the calculation to the controller 100. However, the direction or angle in or at which the mobile terminal 100 moves may be calculated by the controller 110. The direction in which the mobile terminal 100 moves may be basically an up-down direction or a left-right direction. The direction in which the mobile terminal 100 moves may be a front direction in which the mobile terminal 100 is pulled horizontally toward a user or a back direction in which the mobile terminal 100 is pushed horizontally against the user. A tilting direction in which the mobile terminal 100 is tilted with respect to a reference axis is included in the direction of a motion. When the angle at which the mobile terminal 100 moves is calculated in a direction which the mobile terminal 100 is tilted under an assumption that the current position of the mobile terminal 100 is at 0 degree, a direction diagonal to the direction in which the mobile terminal 100 moves also may be included in the direction of a motion. [0074]According to an exemplary embodiment of the present invention, the sensor module 170 may also include a breath detection sensor for using a user's breath as a control command to change the configuration of a layout according to the user's breath. The breath detection sensor is attached on the outer surface of the mobile terminal 100, and detects a user's breath or wind brown through an inlet. The breath detection sensor may be a wind velocity sensor that outputs an electrical signal according to a user's breath. The wind velocity sensor transfers an output value that increases at a constant rate according to a user's breath intensity to the controller 110. Alternatively, the breath detection sensor may be a temperature sensor or a humidity sensor capable of sensing a user's breath, in which case the temperature sensor or the humidity sensor can transfer various levels of output values to the controller 110 according to a user's breath intensity. [0075]The GPS module 157 can receive radio waves from a plurality of GPS satellites (not shown) on the orbit around the earth, and calculate the location of the mobile terminal 100 based on a time of arrival of the radio waves from the GPS satellites to the mob(String), 优先 [0001] 本申请是在先申请系列的延续申请。 2013 年 12 月 13 日提交的第 14/105,735 号,该专利基于 2013 年 2 月 22 日提交的韩国专利申请号 10-2013-0019508 并根据 35 U.S.C § 119(a) 要求优先权 韩国知识产权局,其公开的全部内容通过引用并入本文。 背景技术 1. 发明领域 [0002] 本发明总体上涉及一种用于管理在触摸屏上显示的多个对象的设备和方法。 更具体地,本发明涉及一种用于允许移动终端的用户根据移动终端的动作容易地改变触摸屏上的多个对象的显示的设备和方法。 2.相关技术的描述 [0003] 具有安装在显示设备上的触摸面板的触摸屏显示图像并允许用户在不使用键盘或鼠标的情况下轻松输入命令。 触摸屏已广泛应用于各种电子设备,例如移动终端、导航系统、电视、自动柜员机(ATM)、销售点(POS)系统等。 [0004] 例如,随着移动终端可以提供的各种服务和附加功能,最近的许多移动终端都提供了基于触摸屏的图形用户界面(GUI)。 [0005] 为了提高这种移动终端的有效价值并满足用户的需求,正在开发可在移动终端中执行的各种应用程序。 [0006] 移动终端可以存储移动终端制造公司开发的基本应用程序,以及通过互联网从应用程序销售网站下载的附加应用程序,并执行这些应用程序。 [0007] 相应地,移动终端,例如最新的智能手机、平板电脑等,存储了至少数百个应用程序,并且用于单独执行应用程序的快捷键以图标的形式显示在移动终端的触摸屏上 . 用户可以触摸显示在移动终端的触摸屏上的图标之一,从而在移动终端上执行期望的应用。 移动终端的触摸屏上还可以显示除快捷键之外的各种可视对象,如小部件、图片、文档等。 [0008] 然而,随着这种各种视觉对象的数量增加,另一个问题出现了。 移动终端虽然存储了很多视觉对象,但是在移动终端的小屏幕上可以显示的对象的数量是有限的。 [0009] 因此,由于显示屏幕的空间限制,需要对可显示在屏幕上的视觉对象进行分类和排列。 然而,将布局的组成部分等间隔排列是不够的,需要用户能够方便地管理移动终端屏幕上显示的可视对象,例如对可视对象进行编辑、移动或删除等。 现有技术中,当用户想要改变对象的显示时,需要将自己的移动终端屏幕转换为Edit环境,并输入删除或更正对象的命令,造成繁重不便,需要 很长一段时间的编辑。 [0010] 上述信息仅作为背景信息提供以帮助理解本公开。 没有作出任何决定,也没有作出任何断言,关于上述任何内容是否可以用作关于本发明的现有技术。 [0011] 上述信息仅作为背景信息提供以帮助理解本公开。 没有作出任何决定,也没有作出任何断言,关于上述任何内容是否可以用作关于本发明的现有技术。 发明内容 [0012]本发明的方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面是提供一种允许用户方便地改变布局的组件的设备和方法,其中多个对象根据他/她的期望图案排列。 [0013] 本发明的另一方面在于提供一种用于容易地控制多个对象的布置以及其中根据移动终端的运动布置对象的布局的显示的设备和方法。 [0014] 根据本发明的一方面,提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括显示包括多个区域的布局,其中分别显示多个对象,接收与移动终端的操作相关的输入,改变与与移动终端相关的输入对应的多个区域中的一个或多个区域。 移动终端的操作,以及显示包括改变区域的布局。 [0015] 根据本发明的另一方面,提供了一种用于根据与移动终端的操作相关的输入来控制多个对象的显示的移动终端。 移动终端包括:显示单元,被配置为显示包括多个区域的布局,在该多个区域中分别显示多个对象;传感器模块,被配置为检测与移动终端的操作相关的输入;以及控制器,被配置为改变 对应于与移动终端的操作相关的输入的多个区域中的一个或多个,并控制显示单元显示包括改变的区域的布局。 [0016] 通过以下详细描述,本发明的其他方面、优点和显着特征对于本领域技术人员将变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0017] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0018] 如图。 附图说明图1是示出根据本发明示例性实施例的移动终端的框图; [0019] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图; [0020] 如图。 图3是根据本发明示例性实施例的移动终端的后透视图; [0021] 如图。 图4是根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图; [0022] 图 图5A至图8B示出了用于解释根据本发明示例性实施例的构成布局的区域根据移动终端的往复运动方向改变的处理的示例; [0023] 图 图9A至9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的处理的示例; [0024] 图 图10A~图11D是用于说明本发明的实施方式的布局的排列规则的图。 [0025] 如图。 图12是用于说明根据本发明示例性实施例的移动终端中改变构成布局的区域的方法的流程图; [0026] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的特性将不同对象分别显示在构成布局的区域上的处理的示例; [0027]图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; [0028] 图 图15A至图15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例; [0029] 如图。 图16是用于说明根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; 和 [0030] 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0031] 在整个附图中,相似的附图标记将被理解为指代相似的部件、组件和结构。 示例性实施例的详细描述 [0032] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,可以省略对众所周知的功能和结构的描述。 [0033] 以下描述和权利要求中使用的术语和词语不限于书目含义,而仅由发明人使用以使对本发明的理解清晰一致。 因此,本领域技术人员应当清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物限定的本发明。 [0034] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0035] 应当理解,尽管在本文中可以使用术语第一、第二等来描述各种元素,但是这些元素不应受到这些术语的限制。 这些术语仅用于区分一个元素与另一个元素。 例如,可以将第一元件称为第二元件,并且类似地,可以将第二元件称为第一元件,而不脱离本发明的范围。 如本文所用,单数形式“a”、“an”和“the”旨在也包括复数形式,除非上下文另有明确指示。 [0036] 下面将描述的示例性实施例涉及手持终端,然而,根据本发明示例性实施例的用于管理显示在触摸屏上的多个对象的设备和方法可以应用于各种电子设备 具有触摸屏,例如导航系统、电视(TV)、自动柜员机(ATM)、销售点(POS)系统等,以及移动终端,例如移动 手机、智能手机、平板电脑等。 [0037] 此外,在以下描述中,移动终端可以是柔性设备或柔性显示设备。 作为代表性的移动终端,假设是移动电话,并且可以根据需要省略或改变这种移动终端的一些组件。 [0038]本发明的示例性实施例提供了一种根据与移动终端的运动相关的输入来控制多个对象的显示的方法。 本发明的示例性实施例包括如下操作:如果在显示包括显示多个对象的区域的布局时接收到与移动终端的运动相关的输入,则改变与该输入相关的一个或多个区域的操作。 移动终端在构成布局的区域之间的运动; 以及显示由改变的区域组成的布局的操作。 与移动终端的动作相关的输入可以对应于移动终端的动作、用户的呼吸、手势等。 根据本发明的示例性实施例,如果在构成布局的区域之一被触摸时检测到与移动终端的运动相关的输入,则重新排列除了被触摸区域之外的其余区域。 在这种情况下,分别显示在剩余区域中的对象可以是与显示在触摸区域上的对象的属性相对应的搜索对象。 因此,用户可以容易地改变与布局的区域相对应的组件,以及改变布局的区域。 [0039] 如图。 图1是示出根据本发明示例性实施例的移动终端的框图。 [0040] 参考图。 1、移动端 100 可以使用通信模块中的至少一个连接到外部电子设备(未示出) 120 , 一个连接器 165 和耳机连接插孔 167 . 外部电子设备可以包括耳机、外部扬声器、通用串行总线(USB)存储器、电池充电器、底座/底座、数字多媒体广播(DMB)天线、移动支付系统、医疗保健设备(血液 血糖仪等)、游戏、车载导航系统等,可拆卸地连接到移动终端 100 通过一条线。 外部电子设备可以包括蓝牙通信装置、近场通信(NFC)装置、WiFi Direct通信装置、无线接入点(WAP)等,它们可以连接到移动终端 100 以无线方式。 移动终端 100 可以有线/无线方式连接到其他移动终端或电子设备(例如,手机、智能手机、平板电脑、台式电脑和服务器)之一。 [0041] 移动终端 100 包括一个触摸屏 190 和至少一个触摸屏控制器 195 . 移动终端 100 还可以包括控制器 110 , 通讯模块 120 , 多媒体模块 140 , 一个摄像头模块 150 , 输入/输出模块 160 , 一个传感器模块 170 , 一个存储单元 175 , 和一个电源单元 180 . [0042] 通讯模块 120 包括一个移动通信模块 121 , 一个子通信模块 130 ,以及广播通信模块 141 . [0043] 子通讯模块 130 包括至少一个无线 LAN (WLAN) 模块 131 和一个短距离通信模块 132 . 多媒体模块 140 包括至少一个音频播放模块 142 和一个视频播放模块 143 . 摄像头模组 150 可以包括第一相机中的至少一个 151 和第二台相机 152 . 摄像头模组 150 还可以包括至少一个体管 155 用于放大/缩小第一台和/或第二台摄像机 151 或者 152 , 一个电机单元 154 用于控制体管的运动 155 , 和一个闪光灯 153 根据移动终端的主要用途,为拍照提供光源 100 . 输入/输出模块 160 可以包括至少一个按钮 161 , 麦克风 162 , 扬声器 163 , 振动装置 164 , 连接器 165 , 和一个键盘 166 . [0044]控制器 110 可能包括一个 CPU 111 , 只读存储器 (ROM) 112 存储用于控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 存储从外部接收的信号或数据或用作移动终端正在执行的任务的存储区域 100 . 中央处理器 111 可以包括一个或多个核,例如单核、双核、三核或四核。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线相互连接。 [0045] 此外,控制器 110 可以控制通讯模块 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 存储单元 175 , 电源单元 180 , 触摸屏 190 , 和触摸屏控制器 195 . [0046] 当用户输入设备,例如输入单元 168 或用户的手指、触摸、接近或位于触摸屏上显示的多个对象或项目中的至少一个的附近 190 , 控制器 110 感测用户输入,并识别与在触摸屏上感测到用户输入的位置相对应的对象 190 . 用户通过触摸屏输入 190 可以是直接触摸对象的直接触摸输入和不直接触摸对象而接近预定识别距离内的对象的间接触摸输入的悬停输入之一。 例如,当用户将输入单元 168 靠近触摸屏 190 , 位于输入单元正下方的对象 168 可以选择。 用户输入可以是通过相机模块的手势输入 150 , 一个开关/按钮通过按钮输入 161 或键盘 166 ,或通过麦克风输入的语音 16 , 除了通过触摸屏的用户输入 190 . [0047] 对象或项(例如功能项)可以是应用程序、菜单、文档、小部件、图片、视频、电子邮件、短消息服务(SMS)消息、多媒体消息服务中的至少一个 (MMS)消息等,已经或可以在触摸屏上显示 190 移动终端的 100 . 对象或项目可以由用户输入设备选择、执行、删除、取消、存储或改变。 该项目可以是按钮、图标(例如快捷方式图标)、缩略图或移动终端中存储至少一个对象的文件夹。 该项目可以以图像、文本等的形式显示。 [0048] 快捷项目是显示在触摸屏上的图像 190 快速执行各个应用或移动终端提供的通话、联系人列表、菜单等 100 . 如果接收到用于执行快捷方式项的命令或选择,则执行相应的应用程序。 [0049] 当输入单元 168 接近触摸屏 190 或放置在触摸屏附近 190 , 控制器 110 可以感测用户输入事件,例如悬停事件。 如果针对预定项目或根据预定方法生成用户输入事件,则控制器 110 执行对应于用户输入事件的预定程序操作。 [0050] 控制器 110 可以向输入单元输出控制信号 168 或振动装置 164 . 控制信号可以包括关于振动模式的信息,以及输入单元 168 或振动装置 164 可以根据振动模式产生振动。 关于振动模式的信息可以表示振动模式、振动模式的标识符等。 或者,控制信号可以仅包括产生振动的请求。 [0051] 移动终端 100 可以包括至少一个移动通信模块 121 , WLAN 模块 131 , 和短距离通信模块132 ,根据手机端的功能 100 . [0052] 移动通信模块 121 可以连接移动终端 100 在控制器的控制下,使用一根或多根天线(未显示)通过移动通信连接到外部电子设备 110 . 移动通信模块 121 可以向/从移动电话(未示出)、智能手机(未示出)、平板电脑(未示出)发送/接收用于语音呼叫、视频呼叫、SMS消息或MMS消息的无线电信号, 当对应的电话号码被输入到移动终端时,或另一个电子设备(未示出) 100 . [0053] 子通讯模块 130 可以包括至少一个 WLAN 模块 131 和短距离通信模块 132 如上所述。 例如子通信模块 130 可能包括 WLAN 模块之一 131 和短距离通信模块 132 , 或两者 WLAN 模块 131 和短距离通信模块 132 . [0054] 无线局域网模块 131 在控制器的控制下,可以在安装了 WAP 的地方连接到 Internet 110 . 无线局域网模块 131 支持 IEEE802.11x 标准。 短距离通信模块 132 在移动终端之间进行短距离通信 100 以及在控制器控制下以无线方式的外部电子设备 110 . 短距离通信可以包括蓝牙、红外数据协会(IrDA)、WiFi-Direct通信、NFC等。 [0055] 控制器 110 可以根据触觉模式向输入单元发送控制信号 168 通过子通讯模块 130 . [0056] 广播通信模块 141 可以接收广播信号(例如,电视广播信号、无线电广播信号或数据广播信号)和广播从广播站发送的附加信息(例如,电子节目指南(EPS)或电子服务指南(ESG)) 通过广播通信天线(未显示),在控制器的控制下 110 . [0057] 多媒体模块 140 可能包括音频播放模块 142 和视频播放模块 143 如上所述。 音频播放模块 142 可以再现存储在存储单元中的数字音频文件(例如,扩展名为“.mp3”、“.wma”、“.ogg”或“.wav”的文件) 175 或从外部设备接收,在控制器的控制下 110 . 视频播放模块 143 可以复制存储或 收到,在控制器的控制下 110 . 多媒体模块 140 可与控制器集成 110 . [0058] 摄像头模组 150 可以包括第一和第二相机中的至少一个 151 和 152 在控制器的控制下拍摄静止图像或运动图像 110 . 摄像头模组 150 还可以包括至少一种管体 155 为了放大/缩小拍摄对象,电机单元 154 , 和闪光灯 153 用于提供拍摄对象所需的辅助光源。 第一台相机 151 可以设置在移动终端的正面 100 , 和第二个摄像头 152 可以设置在移动终端的背面 100 . [0059] 第一和第二相机中的每一个 151 和 152 可以包括镜头系统、图像传感器等。 第一和第二相机中的每一个 151 和 152 将通过镜头系统接收(或拍摄)的光信号转换为电图像信号,并将电图像信号输出到控制器 110 . 因此,用户可以通过第一和第二相机拍摄运动图像或静止图像 151 和152 . [0060] 输入/输出模块 160 可以包括至少一个按钮中的至少一个 161 , 至少一个麦克风 162 , 至少一位发言者 163 , 至少一个振动装置 164 , 连接器 165 , 键盘 166 , 耳机连接插孔 167 , 和输入单元 168 . 然而,输入/输出模块 160 不限于上述设备,还可以提供鼠标、轨迹球、操纵杆或光标方向键等光标控件来控制光标在触摸屏上的移动 190 . [0061] 按钮 161 可以形成在移动终端的外壳(或外壳)的正面、侧面或背面 100 ,并且可以包括电源/锁定按钮、音量按钮、菜单按钮、主页按钮、返回按钮和搜索按钮中的至少一个。 [0062] 麦克风 162 可以在控制器的控制下接收语音或声音 110 产生电信号。 [0063] 演讲者 163 可以将与各种信号或数据(例如,无线电数据、广播数据、数字音频数据、数字视频数据等)对应的声音输出到移动终端之外 100 在控制器的控制下 110 . 演讲者 163 可以输出与移动终端执行的功能对应的声音(例如,与呼叫对应的按钮操作声音、货币连接声音、对方的语音等) 100 . 一位或多位演讲者 163 可以在移动终端的外壳上的一个或多个适当位置提供 100 . [0064] 振动装置 164 可在控制器的控制下将电信号转换为机械振动 110 . 例如,如果在移动终端时由另一个设备(未示出)进行语音或视频通话 100 处于振动模式时,振动装置 164 运作。 一个或多个振动装置 164 可以设置在移动终端的外壳中 100 . 振动装置 164 可以对应于通过触摸屏的用户输入进行操作 190 . [0065] 连接器 165 可作为连接移动终端的接口 100 连接到外部电子设备或电源(未显示)。 控制器 110 可以传输存储在存储单元中的数据 175 到外部电子设备或通过连接到连接器的有线电缆从外部电子设备接收数据 165 . 移动终端 100 可以通过连接到连接器的有线电缆从电源接收电力或使用电源为电池充电 165 . [0066] 键盘 166 可以接收来自用户的按键输入以控制移动终端 100 . 键盘 166 包括在移动终端上形成的物理键盘(未显示) 100 或触摸屏上显示的虚拟键盘(未显示) 190 . 在移动终端上形成的物理键盘 100 可根据移动终端的性能或结构排除 100 . [0067] 耳机(未显示)可以插入耳机连接插孔 167 连接到移动终端 100 . [0068] 输入单元 168 可插入并保持在移动终端中 100 ,而在使用时,输入单元 168 可从移动终端抽出或分离 100 . 脱离/附着识别开关 169 对应于输入单元的安装和拆卸进行操作 168 可以设置在移动终端的区域内 100 输入单元 168 被插入。 分离/附着识别开关 169 可以输出与输入单元的连接/分离相对应的信号 168 到控制器 110 . 分离/附着识别开关 169 可配置为直接或间接接触输入单元 168当输入单元 169 附在手机端 100 . 因此,分离/附着识别开关 169 产生一个信号(即,用于通知输入单元的连接或分离的信号 168 ) 对应于输入单元的连接或分离 168 基于是否分离/附着识别开关 169 接触输入单元 168 , 并将信号输出到控制器 110 . [0069] 传感器模块 170 可以包括至少一个传感器,用于检测移动终端的状态 100 . 例如,传感器模块可以包括用于检测接近移动终端的接近传感器(未示出)中的至少一个传感器 100 ,环境光传感器(未示出),用于检测移动终端周围的环境光强度 100 ,用于检测移动终端的运动(例如,旋转、加速度、振动)的运动传感器(未示出) 100 ,地磁传感器(未示出),用于检测移动终端的罗盘点 100 使用地球磁场,用于检测施加重力的方向的重力传感器(未示出),用于测量大气压力以检测高度的高度计(未示出),以及GPS模块 157 . 用于感测用户手势的相机传感器也可以包括在传感器模块中 170 . [0070] 上述传感器中的运动传感器感知移动终端的位置、运动等 100 使用加速度传感器、陀螺仪传感器、倾斜传感器或它们的组合。 然而,传感器不限于上述传感器,还可以包括能够感测移动终端的往复运动、移动方向等的其他类型的传感器。 100 . [0071] 通过运动传感器输出的感测数据(即运动信息)可以具有方向和幅度。 例如,用于感应移动终端加速度的加速度传感器 100 可以感应相对于x、y和z轴中至少一个参考轴方向的加速度,并输出加速度信息。 参考轴可以是移动终端的轴(例如,上下(z轴)、左右(x轴)和前后(y轴)方向) 100 ) 根据移动端的方向 100 ,或者可以是根据重力方向的轴(重力方向(z轴)和垂直于重力方向的方向(z和y轴))。 [0072] 传感器模块 170 还可以包括计算器(未示出),用于将感测到的角速度、速度等随时间积分以根据物体的运动计算旋转角度、方向、速度、行进距离、位置、轨迹等。 移动终端 100 ,并输出计算得到的信息。 计算器可能包含在控制器中 110 . 计算器还可以包括频率滤波器,用于阻止或通过特定频带的信号,例如检测到的加速度,以便计算轨迹等或有效地分析运动的方向。 [0073] 当传感器模块 170 包括计算器,计算器可以计算移动终端所处的方向或角度 100 移动,并将计算结果传送给控制器 100 . 但是,移动终端所处的方向或角度 100 移动可由控制器计算 110 . 移动终端的方向 100 移动基本上可以是上下方向或左右方向。 移动终端的方向 100 移动可以是移动终端所处的正面方向 100 被水平拉向用户或移动终端所在的后退方向 100 被水平推向用户。 移动终端的倾斜方向 100 相对于参考轴倾斜 包含在运动方向中。 当移动终端的角度 100移动是在移动终端的方向上计算的 100 在假设移动终端的当前位置是倾斜的 100 为0度,与移动终端所在方向的对角线方向 100 运动也可以包含在运动的方向中。 [0074] 根据本发明的示例性实施例,传感器模块 170 还可以包括呼吸检测传感器,用于使用用户的呼吸作为控制命令来根据用户的呼吸改变布局的配置。 呼吸检测传感器贴附在移动终端的外表面上 100 ,并通过入口检测用户的呼吸或风棕色。 呼吸检测传感器可以是根据用户的呼吸输出电信号的风速传感器。 风速传感器将根据用户的呼吸强度以恒定速率增加的输出值传输到控制器 110 . 或者,呼吸检测传感器可以是能够感测用户呼吸的温度传感器或湿度传感器,在这种情况下,温度传感器或湿度传感器可以将各种级别的输出值传递给控制器 110 根据用户的呼吸强度。 [0075] GPS模块 157 可以接收来自环绕地球轨道上的多个GPS卫星(未示出)的无线电波,并计算移动终端的位置 100 基于从 GPS 卫星到移动终端的无线电波的到达时间 100 . [0076] 存储单元 175 可以存储根据通信模块的操作输入/输出的信号或数据 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 或触摸屏 190 , 在控制器的控制下 110 . 存储单元 175 可以存储用于控制移动终端的应用程序和控制程序 100 或控制器 110 . [0077] 术语“存储单元”表示任意数据存储设备,例如存储单元 175 , 只读存储器 112 和内存 113 在控制器中 110 ,安装在移动终端中的存储卡(例如,SD卡或记忆棒) 100 ,等等。 存储单元 175 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)和固态驱动器(SSD)。 [0078] 存储单元 175 可以存储具有各种功能的应用程序,例如导航、视频通话、游戏、基于时间的警报应用程序等、用于为用户提供与应用程序相关联的图形用户界面 (GUI) 的图像、用户信息、文档、数据库 或与处理触摸输入的方法、背景图像(菜单屏幕、锁定屏幕等)或驱动移动终端所需的操作程序有关的数据 100 , 摄像头模块拍摄的图像 150 等存储单元 175 还可以存储与合成图像提供方法相关的数据。 [0079] 存储单元 175 是机器(例如,计算机)可读介质,术语“机器可读介质”可以定义为向机器提供数据以使机器能够执行特定功能的介质。 存储单元 175 可能包括非易失性介质和易失性介质。 这样的介质需要是有形的,以便传送到介质的命令可以被使用机器读取命令的物理工具检测到。 [0080] 机器可读介质包括软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、穿孔卡、纸带中的至少一种。 、RAM、可编程只读存储器(PROM)、可擦除PROM(EPROM)和FLASH-EPROM,然而,机器可读介质不限于上述设备。 [0081] 电源单元 180 可以为安装在移动终端外壳中的一个或多个电池供电 100 在控制器的控制下 110. 一节或多节电池为移动终端供电 100 . 电源单元 180 可以将从外部电源接收的电力提供给移动终端 100 通过连接到连接器的有线电缆 165 . 电源单元 180 可以将从外部电源无线接收的电力提供给移动终端 100 通过无线充电技术。 [0082] 移动终端 100 可能包括至少一个触摸屏 190 为用户提供与各种服务(例如,通话、数据传输、拍照)相对应的GUI。 [0083] 触摸屏 190 可以将与输入到用户图形界面的至少一个用户输入相对应的模拟信号输出到触摸屏控制器 195 . 触摸屏 190 可以通过用户的身体部位(例如,包括拇指的手指)或输入单元接收至少一个用户输入 168 (例如,手写笔或电子笔)。 触摸屏 190 可以接收触摸的连续移动(例如,拖动输入)。 触摸屏 190 可以将与触摸的连续移动对应的模拟信号输出到触摸屏控制器 195 . [0084] 在本说明书中,术语“触摸”不限于手指或输入单元的接触 168 到触摸屏 190 ,并且可以包括非接触式识别(例如,当用户输入设备位于识别距离(例如,1 cm)内时,用户输入设备可以在不直接接触触摸屏的情况下被检测到) 190 )。 触摸屏的识别距离 190 能否识别用户输入设备可能取决于移动终端的性能或结构 100 . 为了触摸屏 190 为了区分与用户输入设备直接接触产生的直接触摸事件和间接触摸事件(即悬停事件),触摸屏 190 可以被配置为根据直接触摸事件和悬停事件输出不同的值(例如,包括电压值和电流值的模拟值)。 [0085] 触摸屏 190 可以是电阻式触摸屏、电容式触摸屏、红外触摸屏、声波触摸屏或它们的组合。 [0086] 触摸屏 190 还可以包括至少两个触摸面板,分别用于感应手指和输入单元的触摸或接近 168 分别接收手指和输入单元的输入 168 . 至少两个触摸面板针对手指和输入单元的输入提供不同的输出值 168 到触摸屏控制器 195 , 和触摸屏控制器 195 识别从至少两个触摸面板接收到的不同输出值,以确定触摸屏是否有输入 190 是手指输入还是输入单元输入 168 . [0087] 触摸屏控制器 195 转换从触摸屏接收到的模拟信号 190 转换成数字信号,并将数字信号传输给控制器 110 . 控制器 110 可以控制触摸屏 190 使用从触摸屏控制器接收到的数字信号 195 . 例如,控制器 110 可以选择或执行显示在触摸屏上的快捷方式图标或对象 190 响应直接触摸事件或悬停事件。 触摸屏控制器 195 可以集成到控制器中 110 . [0088] 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值) 190 确定悬停间隔或距离以及用户的输入位置,将确定的距离值转换为数字信号(例如z坐标),然后将数字信号提供给控制器 110 . 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值)190 估计用户输入设备按压触摸屏的压力 190 ,将估计的压力值转换成数字信号,然后将数字信号提供给控制器 110 . [0089] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图,以及图2是根据本发明示例性实施例的移动终端的前透视图。 图3是根据本发明示例性实施例的移动终端的后透视图。 [0090] 参考图。 1-3、触摸屏 190 放置在正面的中央 101 的移动终端。 触摸屏 190 可以形成占据正面主要部分的大面积 101 的移动终端。 如图。 图2示出了在触摸屏上显示主主屏幕的示例 190 . 主主屏幕是最初出现在触摸屏上的屏幕 190 当移动端 100 通电。 如果移动端 100 具有多个页面的不同主屏幕,主主屏幕可以是主屏幕中的第一个主屏幕。 主屏幕可能会显示快捷方式图标 191 - 1 , 191 - 2 , 和 191 - 3 用于执行常用应用程序,主菜单转换键 191 - 4 、当前时间、天气信息等。如果用户选择主菜单转换键 191 - 4 , 触摸屏上显示菜单画面 190 . 状态栏 192 代表移动终端的状态 100 可在触摸屏上方显示电池充电状态、接收信号强度、当前时间等 190 . [0091] 一个主页按钮 161 a , 一个菜单按钮 161 b , 和一个后退按钮 161 c 可能会显示在触摸屏的下部 190 . 主页按钮 161 a 用于在触摸屏上显示主主屏幕 190 . 例如,如果主页按钮 161 a 当触摸屏上显示除主主屏幕或菜单屏幕之外的另一个主屏幕时选择 190 , 主屏幕可能会显示在触摸屏上 190 . 如果主页按钮 161 a 在触摸屏上执行应用程序时选择 190 ,主屏幕如图所示。 2 可在触摸屏上显示 190 . 主页按钮 161 a 可用于在触摸屏上显示最近使用的应用程序 190 或在触摸屏上显示任务管理器 190 . [0092] 菜单按钮 161 b 提供可在触摸屏上显示的链接菜单 190 . 链接菜单可以包括小部件添加菜单、锁屏改变菜单、搜索菜单、编辑菜单、设置菜单等。 [0093] 后退按钮 161 c 可用于显示恰好在当前正在执行的屏幕之前执行的屏幕或终止最近使用的应用程序。 [0094] 第一台相机 151 , 环境光传感器 170 a , 和一个接近传感器 170 b 可以设置在移动终端正面的一个边缘部分 100 . 第二台相机 152 , 闪光 153 , 和扬声器 163 可以设置在背面 103 移动终端的 100 . [0095] 在移动终端的侧面 102 ,例如,电源/锁定按钮 161 d , 音量按钮 161 e 包括一个音量增大按钮 161 f 和一个音量减小按钮 161 g ,地面DMB天线 141 a 用于接收广播,一个或多个麦克风 162 等。 DMB 天线 141 a 可以固定或可拆卸地附在移动终端上 100 . [0096] 连接器 165 形成在移动终端下端的侧面 10 . 连接器 165包括多个电极,并且可以通过线路连接到外部设备。 耳机连接插孔 167 可以形成在移动终端上端的侧面 100 . 耳机可插入耳机连接插孔 167 . [0097] 输入单元 168 可安装在移动终端下端的侧面 100 . 输入单元 168 可插入移动终端内部 100 并存储在移动终端中 100 ,而在使用时,输入单元 168 与移动端分离 100 . [0098] 随着用户在移动终端上以各种形式显示多个视觉对象的愿望的增加 100 通过上述结构,例如,在相册应用的情况下,用户可以通过轻弹或拖拽手势在将图片排列在布局的预定区域的屏幕上翻页的同时查看许多图片。 触摸屏 190 . [0099] 然而,为了让用户改变图片的排列和显示图片的区域,用户必须在编辑屏幕上编辑层,这可能需要很长时间。 此外,用户倾向于将关联图片收集到特定文件夹中,以便轻松快速地找到想要的图片或关联图片。 [0100] 因此,根据本发明的示例性实施例,提供了一种用于在触摸屏上容易且快速地改变由显示视觉对象的区域组成的布局的方法和设备 190 ,根据移动终端的动作 100 当用户选择特定对象时,提供一种布局,在该布局中,考虑到所选对象的属性,显示与所选对象相关联的对象。 [0101] 如图。 图4是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 [0102] 参考图。 参照图4,将参照图1和图4所示的示例来描述改变构成布局的区域的方法。 然而,在图5A至8B中,该方法不限于图5A至图8B中所示的示例。 5A到8B。 此外,根据本发明的示例性实施例,例如,当执行故事专辑应用程序时,将作为示例描述显示被划分为预定数量的区域的布局并改变布局的组件的方法。 然而,对于本领域普通技术人员来说显而易见的是,可以将根据移动终端的运动改变布局的组件的方法应用于各种显示屏幕。 [0103] 在步骤 400 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 . 在本说明书中,配置布局的“区域”也可以称为“网格”、“部分”等。 [0104] 图 图5A到8B示出了根据本发明示例性实施例的用于解释构成布局的区域根据移动终端的往复运动的方向改变的处理的示例。 [0105] 参考图。 参见图 5A-8B, 图5A示出了在触摸屏上显示对象的显示屏的示例 190 布局由区域 A、B、C 和 D 组成。可在各个区域上显示的对象可能包括图片、插图、字母(字体、类型)、字符等组件,还包括各种 视觉对象,例如各种内容(例如,文本)、用于执行应用程序的快捷图标、小部件、表示具有各种文件格式的文档的图标、文件夹等。对象还可以包括从视觉对象中选择的一些视觉对象。 [0106] 当显示画面如图所示。 如图5A所示,用户可以通过摇动移动终端来改变布局区域的排列 100 与移动终端 100 在用户手中。 在步骤 405 , 控制器110 判断移动终端是否往复运动 100 通过传感器模块检测到 170 . 如果移动终端的往复运动 100 检测到,然后在步骤中确定检测到的往复运动的方向 410 . 控制器 110 判断移动终端往复运动的方向是否 100 基于通过传感器模块收集的传感器信号对应于上下方向、左右方向和对角方向中的哪个方向 170 . 在步骤 415 , 控制器 110 根据确定的往复运动方向改变构成布局的区域,并在步 420 , 控制器 110 显示使用更改区域重新配置的布局。 [0107] 如图。 图5B示出了当用户摇动移动终端时的示例 100 在左右方向 500 , 左右方向对齐的区域排列 500 根据本发明的示例性实施例改变。 [0108] 参考图。 5B,如果用户摇动移动终端 100 在左右方向上预定次数(例如一次或两次) 500 与移动终端 100 在用户手中时,屏幕如图所示。 显示图5A,在左右方向上对齐的区域排列 500 在布局更改的区域之间。 在图。 在图5A中,区域A、B、C和D中的区域B和C对应于可以根据左右方向上的往复运动而改变的区域 500 ,因此,在左右方向的往复运动之后 500 执行后,区域B和C的布置改变如图6所示。 5B。 显示在图1的区域B中的对象。 图5A移动到并显示在图5的区域B中。 图5B的区域C中显示的对象。 图5A移动到并显示在图5的区域C中。 5B。 [0109] 图 图6A到6B示出了当用户摇动移动终端时的示例 100 在上下方向 600 ,根据本发明的示例性实施例,沿上下方向排列的区域的排列发生变化。 [0110] 参考图。 如图 6A 和 6B 所示,如果在上下方向上往复运动 600 当显示配置有区域 A、B、C 和 D 的布局屏幕时,执行如图 10 所示。 图6A,上下方向排列的区域排列 600 如图所示的变化。 6B。 如果上下方向往复运动 600 执行,图的区域B和C。 图6A移动到图6的上部区域。 在图6B中,区域D对应于图6的下部区域。 图6A移动到图6的中心区域。 图6B的区域A,图6B的区域A。 图6A移动到图6的下部区域。 6B(即,到图6B的区域A)。 下面参照图1至图3描述区域的排列规则。 10 和 11。 [0111] 图 图7A和7B示出了当用户摇动移动终端时的示例 100 在对角线方向 700 ,根据本发明的示例性实施例,沿对角线方向排列的区域的排列发生变化。 [0112] 参考图。 如图 7A 和 7B 所示,如果沿对角线方向往复运动 700 当屏幕如图 3 所示时执行。 显示图7A的区域A,显示图7A的区域A。 图7A移动到图7的区域A。 图7B的区域D和图7B的区域D。 图7A移动到图7的区域D。 7B。 [0113] 图 图8A和8B示出了当用户摇动移动终端时的示例 100 ,除触摸区域外的其余区域的排列发生变化。 如图。 图8A示出了用于说明用户摇动移动终端的情况的画面示例 100 在对角线方向 805 在保持对区域A的触摸的同时。在这种情况下,除了图1中的区域A之外的其余区域B、C和D的布置可以保持在区域A上。 保持触摸的图8A的变化如图8A所示。 8B。 [0114] 如果用户晃动移动终端 100 同时保持对用户所需区域的触摸 800,只有触摸的区域是固定的。 类似地,如果用户在两个或多个区域上保持触摸,则对应的区域也是固定的。 例如,如果用户手持移动终端 100 用双手晃动移动终端可能会让用户感到困难或不舒服 100 在一个特定的方向。 在这种情况下,可以使用用户拉/推移动终端的动作来改变布局的配置 100 朝向/反对用户、倾斜运动等。 [0115] 上述示例性实施例如图1和2所示。 图5A到7B涉及布局的配置根据用户摇动移动终端的往复运动而改变的情况 100 左右方向、上下方向、对角线方向。 然而,也可以根据其他各种动作来改变布局的配置,例如拉/推移动终端的动作 100 水平,倾斜运动,旋转运动等。 图5A到8B涉及根据预定动作改变布局配置的方法。 然而,改变布局的配置的方法不限于以上参照图1至图3描述的方法。 5A到8B。 例如,可以使用呼吸来改变布局的配置。 [0116] 图 图9A到9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的处理的示例。 [0117] 参考图。 9A-9D,如果用户在一个方向吹他/她的呼吸 900 朝向显示由区域A、B、C和D组成的布局的屏幕,如图1所示。 在图9A中,如图9A所示,显示区域A、B、C和D响应用户的呼吸而吹散的屏幕,好像这些区域是从屏幕上吹出的纸一样。 9B。 依次如图所示。 如图9C所示,显示区域A、B、C和D的布置响应于用户的呼吸而改变的屏幕,并且如图9C所示。 参照图9D,显示具有改变了区域A、B、C和D的布置的布局的屏幕。 如上所述,图。 图9A至9D涉及考虑“吹纸”的应用示例,“吹纸”是各种呼吸行为中的一种简单、直接的行为。 图9A至9D示出了显示交互图像的情况,其中区域响应于用户的呼吸而吹散,就好像纸张吹散一样。 因此,用户可以具有控制屏幕区域的体验,就好像用户实际上是在吹纸一样。 根据本发明的示例性实施例,屏幕的内容可以根据用户呼吸的强度而变化。 [0118] 根据本发明的另一示例性实施例,构成布局的区域可以通过检测预定手势(例如,好像翻页的手势)来改变。 这种姿势可以由相机传感器、环境光传感器等检测。 图 1 和 3 中所示的示例。 如上所述,图5A到9D涉及使用动作或呼吸重新配置布局的情况,然而,当相机传感器、环境光传感器等接收到与各种行为有关的输入时,也可以重新配置布局。 [0119] 如上所述,当用户摇动移动终端时 100 或者对着移动终端的屏幕呼吸 100 ,屏幕上显示的图像会根据移动终端的动作而变化 100 或用户的呼吸,使用户无需操作按钮即可轻松快速地排列对象,感受图像的生动变化。 [0120] 可以使用如下所述的排列规则重新排列布局的组件。 [0121] 图 图10A至图10D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0122]参考图。 参照图10A-10D,根据区域大小的排列规则是将显示在较大区域上的对象移动到较小区域并且将显示在较小区域上的对象移动到较大区域的方法。 如图。 图10A示出了其中区域A具有最大尺寸并且区域B和C具有小于区域A的尺寸的屏幕。如果移动终端的往复运动 100 例如,当屏幕如图1所示时,检测到上下方向的往复运动。 在显示图10A时,显示在具有大尺寸的区域A中的对象移动到具有小尺寸的区域A,如图10A所示。 10B 步中 1000 ,并且显示在具有小尺寸的区域C中的对象移动到具有大尺寸的区域C,如图5所示。 10B 步中 1005 . 根据排列规则,每当移动终端有动作 100 当检测到如图 3 所示的屏幕时。 在显示图10A的情况下,布局的配置按照图10的顺序改变。 参照图10B至图10。 10D。 [0123] 图 图11A至11D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0124] 参考图。 如图11A-11D所示,在水平拍摄图像和垂直拍摄图像的情况下,优选水平拍摄图像位于水平区域,而垂直拍摄图像位于垂直区域。 如图。 图11A示出了区域A是水平区域并且区域B和C是垂直区域的示例。 在这种情况下,最好是水平物体 1100 分配到区域 A 并显示在区域 A 中,垂直对象 1102 和 1105 被分配到区域B和C并显示在区域B和C中。根据本发明的示例性实施例,关于对象具有水平格式或垂直格式的每个对象的属性是对象的唯一属性并且可以被识别 提前。 因此,控制器 110 考虑到对象的属性,将每个对象定位在与对象对应的区域。 当执行智能相册应用程序时,控制器 110 可以确定必须显示的对象的数量,从页面具有不同区域排列的多个布局中选择与对象的数量和对象的属性相对应的布局,并提供选择的布局。 [0125] 如果检测到运动时出现如图所示的画面。 在显示图11A的情况下,可以显示具有改变的区域布置的布局,如图11A所示。 11B。 如果一个对象显示在图 C 的区域中。 11A是垂直物体 1105 , 垂直物体 1105 可以显示虽然垂直对象 1105 移动到图1的区域C。 11B。 垂直物体 1105 可以显示在图3的区域C中。 11B 虽然零件 1110 垂直物体的 1105 被截断且未显示。 [0126] 随后,如果再次检测到运动,则如图3所示的布局。 图11B改变为具有如图11所示布置的布局。 11C。 即,由于显示在图2的区域B中的对象。 11B对应垂直物体 1105 显示在图 2 的区域 B 中。 如图11A所示,对象可以移动到图11的区域B并显示在区域B上。 11C。 然而,由于对象显示在图1的区域A中。 11B对应于水平物体 1100 显示在图 1 的区域 A 中。 如图11A所示,对象不能移动到图11的区域A并显示在区域A上。 11D。 当水平物体 1100 位于图A的区域A中。 11D,零件 1115 水平物体的 1100 被切断,同时在区域A中出现空白。这种具有比预定允许的比例失配程度更大的比例失配程度的区域优选在搬迁对象时排除。 因此,图1中所示的布局。 11D 不包括在可选择以更改布局的布局中。 因此,通过考虑每个对象的属性来改变布局,可以在屏幕的区域上适当地布置诸如肖像、风景等的组件,同时保持每个组件的比例。 [0127]如图。 图12是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 在下文中,将参考图10描述根据触摸对象的属性改变在构成布局的区域中显示的对象的方法。 然而,如图12所示,该方法不限于图12所示的示例。 12. [0128] 参考图。 1和12,在步骤 1200 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 移动终端的 100 . 在步骤 1205 , 控制器 110 确定至少一个区域是否已被输入设备触摸。 如果至少触摸了一个区域,则在步骤 1210 控制器 110 判断移动终端是否往复运动 100 被检测到。 如果移动终端的往复运动 100 被检测到,然后在步骤 1215 控制器 110 搜索与属于触摸区域的对象的属性相对应的对象。 如果在步骤中确定 1205 没有接触过任何区域,或者是否在步骤中确定 1210 没有检测到往复运动,则过程返回步骤 1200 并保持布局。 [0129] 在步骤 1220 , 控制器 110 将找到的对象排列在除显示触摸对象的区域之外的其余区域中,并在步骤 1225 , 控制器 110 显示重新配置的布局,其中包含排列找到的对象的区域。 如果没有检测到往复运动,则过程返回操作 1200 ,并且布局保持不变。 [0130] 在上述本发明的示例性实施例中,步骤 1215 搜索关联对象的步骤在步骤之后执行 1210 在保持触摸的同时检测往复运动; 然而,当至少一个区域被触摸时,也可能搜索与属于该区域的对象相关联的对象。 [0131] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的属性将不同对象分别显示在构成布局的区域上的处理的示例。 [0132] 参考图。 参照图13A和13B,除了基于位置布置对象的方法之外,还可以采用根据对象的属性布置关联对象的各种方法。 这样的方法包括基于人来布置对象的方法、基于社交网络来布置对象的方法等。 [0133] 在基于人的布置对象的方法的情况下,如果用户摇动移动终端 100 同时保持对移动终端屏幕上显示的图片上特定人的触摸 100 ,则与被触摸的人相关联的图片可以被重新排列以配置当前页面的布局。 显示多人图片时,允许用户在人群中只选择一个人,如果用户摇晃移动终端 100 在保持触摸特定人的同时,可以搜索与特定人相关联的图片并在各个重新排列的区域上显示。 在基于社交网络的排列对象的方法的情况下,例如,如果选择了facebook feed功能,则可以重新排列相应的Facebook feed以适合相应页面的布局区域。 [0134] 如图。 图13A示出了由地图区域和区域A、B和C组成的布局。如果用户触摸地图区域并摇动移动终端 100 同时保持对地图区域的触摸 1300 ,可以根据对象的属性搜索与属于地图区域的对象相关联的对象,并且可以将找到的对象排列并显示在各个区域上,如图3所示。 13B。 例如,如果用户摇动移动终端 100在地图区域按住“纽约时代广场”的同时,与“纽约时代广场”相关联的对象,例如在该地点拍摄的照片、该地点的相关新闻、该地点推荐的应用项目, 等可以布置在各个区域上,如图1所示。 13B。 [0135] 图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图。 图 图15A到15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例 [0136] 参考图。 参见图14A和14B以及图14A和14B。 参照图15A-15I,图15的过程。 图14B跟随图14的过程。 14A。 为了便于理解,将参考图1至图3描述调整区域数量的方法。 图15A至15I; 然而,该方法不限于图1和图2所示的示例。 15A至15I。 [0137] 在步骤 1400 , 控制器 110 显示由触摸屏上显示对象的区域组成的布局 190 . 在步骤 1405 , 控制器 110 判断是否接收到改变区域数量的请求。 用户可以通过按下诸如音量键之类的特定键或通过位于屏幕上部的操作栏上显示的选项功能来发送改变区域数量的请求。 如果收到更改区域数量的请求,则在步骤 1410 , 控制器 110 显示用于调整区域数量的图标。 如果没有收到更改区域数量的请求,则返回步骤 1400 . 在步骤 1415 , 控制器 110 确定是否触摸了任何一个图标。 [0138] 如果在操作中确定 1415 如果没有检测到触摸输入,则过程返回操作 1410 . 如果选择了用于添加区域的图标,则在步骤 1420 图。 14B、控制器 110 确定在触摸用于添加区域的图标时是否检测到往复运动。 如果检测到往复运动,则在运行中 1425 , 控制器 110 将构成下一页布局的区域添加到构成当前页面布局的区域中,并且在步骤 1440 , 控制器 110 显示重新配置的布局以包括添加的区域。 如果在触摸区域添加图标时重复检测到往复运动,则控制器 110 每当检测到往复运动时,逐步添加区域。 [0139] 图 图15A至图15I示出了用于说明根据移动终端的动作调整构成布局的区域的数量以及改变区域的布置的过程的示例 100 ,根据本发明的示例性实施例。 如果接收到调整区域数量的请求,则在如图 10 所示的屏幕。 显示图15A,区域添加图标 1510 和一个区域移除图标 1510 如图所示显示。 15B。 如果用户晃动移动终端 100 同时保持触摸区域添加图标 1510 ,添加区域D,如图3所示。 在图15C中,A、B和C区域被重新排列。 如果用户晃动移动终端 100 再次,添加区域E,如图4所示。 15D,其余区域重新排列。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 保持15D。 因此,如果构成在页面上显示的布局的区域的数量增加,则将减少总页面数量,因为要显示的对象的数量已经设置。 [0140] 如果在步骤中未触摸区域添加图标 1430 , 控制器 110 确定在区域移除图标被触摸时是否检测到往复运动。 如果在触摸区域移除图标时检测到往复运动,则在操作中 1435 控制器 110从构成当前页面布局的区域中删除一个区域,并在操作中 1440 , 控制器 110 显示用剩余区域重新配置的布局。 如果在区域移除图标时反复检测到往复运动 1500 被触摸时,每当检测到往复运动时,区域就会逐步移除。 [0141] 如果用户晃动移动终端 100 同时保持触摸区域移除图标 1500 如图所示。 在图15F中,去除了D区域,如图15F所示。 15G,A、B、C区域重新排列。 当用户摇动移动终端时 100 同时保持触摸区域移除图标 1500 ,由于已经设置了最小区域数,因此区域数可能不会改变,如图3所示。 15H。 在这种情况下,区域的排列会发生变化。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 15I 保持不变。 因此,如果减少在页面上显示的构成布局的区域的数量,则页面的总数将增加以显示预定数量的对象。 [0142] 运行中 1430 ,如果在没有触摸区域添加/删除图标时检测到往复运动,则在操作中 1445 控制器 110 根据往复运动方向的方向改变构成布局的区域,如图1和2所示。 5至7,并在运行 1450 , 控制器 110 显示使用更改区域重新配置的布局。 [0143] 上述示例是使用图标增加或减少页面上显示的区域数量的情况; 然而,也可以采用其他方法,例如使用音量增大/减小键添加或删除区域的方法。 例如,一个区域可能是如果用户摇动移动终端 100 如果用户摇动移动终端,同时按住音量增大键并移除区域 100 按住音量减小键的同时。 [0144] 如图。 图16是用于说明在移动终端中调整构成布局的区域数的方法的流程图 100 ,根据本发明的示例性实施例。 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0145] 参考图。 参见图 16 和 17A-17C,因为步骤 1600 和 1605 步骤相同 400 和 405 图。 在图4中,将省略其详细描述。 运行中 1610 ,确定往复运动的次数是否等于或大于预定次数。 如果往复运动的次数等于或大于预定次数,则在步骤 1615 包括在下一页的布局中的预定数量的区域被添加到构成当前页面的布局的区域中。 运行中 1620 , 控制器 110 显示重新配置的布局以包括添加的区域。 可以根据往复运动的次数确定添加的区域的数量。 [0146] 如图。 图17A示出了当前页面的布局由区域A、B、C和D构成的情况,而图17A示出了当前页面的布局配置有区域A、B、C和D的情况。 图17B示出了下一页面的布局由区域E、F、G、H和I配置的情况。当前页面是显示在触摸屏上的页面 190 , 下一页是轻弹或拖动触摸屏手势时将显示的页面 190从用户接收。 因此,如果在当前页面如图1所示时检测到一个或多个往复运动。 如图17A所示,下一页的区域E和F如图17所示。 如图17B所示,根据往复运动的次数将图17B的区域添加到当前页面的区域。 如图17C所示,同时,区域A、B和C根据往复运动的方向重新排列。 这些区域可以一个一个地添加,也可以以预定数量为单位添加。 当区域被添加到当前页面时,在下一页的区域E和F上显示的对象如图4所示。 如图17B所示,图17B移动到区域E和F并显示在区域E和F上。 17C。 [0147] 如上所述,根据本发明的示例性实施例,用户可以使用移动终端的动作以他/她的期望模式直观地布置布局的组件(即,区域/对象) 100 . 因此,根据本发明的示例性实施例,用户可以根据移动终端的动作容易且快速地将显示在移动终端的屏幕上的多个对象的排列改变为用户期望的图案。 此外,由于可以通过移动终端的简单动作的输入来改变布置对象的布局的配置,所以可以最大化用户的便利性。 [0148] 此外,由于可以通过考虑对象的属性来配置布局来提供由期望的对象组成的布局,因此可以提供具有统一顺序的个性化布局。 [0149] 本发明的示例性实施例可以以硬件、软件或硬件和软件的组合的形式来实现。 软件可以存储在易失性或非易失性存储设备中,例如 ROM,不管它是可擦除的还是可重写的,存储在诸如 RAM、存储芯片、 和集成电路 (IC),或在光/磁可记录和机器可读的存储介质中,例如压缩盘 (CD)、数字多功能盘 (DVD)、磁盘和磁带 . 可以包括在移动终端中的存储器是适用于存储一个或多个程序的非暂时性机器可读存储介质的示例,包括实现本发明示例性实施例的指令。 因此,本发明的示例性实施例包括包括用于实现如说明书的所附权利要求中所述的设备和方法的代码的程序,以及存储这些程序的机器可读存储介质。 [0150] 此外,移动终端可以从以有线/无线方式连接的程序提供装置接收和存储程序。 程序提供设备可以包括:存储器,用于存储程序,该程序包括用于执行根据移动终端的动作控制多个对象的显示的方法的指令;通信单元,用于与移动终端进行有线/无线通信; 控制器,用于根据移动终端的请求或自动向移动终端发送程序。 [0151] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 31 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), AU2014219558A1(String), 1047247(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), AU2014219558B2(String), 1047248(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), BR112015020243A2(String), 1047249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), BR112015020243B1(String), 1047250(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), CN104007892A(String), 1047251(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), CN104007892B(String), 1047252(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), CN110333758A(String), 1047253(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), EP2770424A2(String), 1047254(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), EP2770424A3(String), 1047255(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), EP2770424B1(String), 1047256(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), EP3696653A1(String), 1047257(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), EP3696653B1(String), 1047258(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), IN2703MUMNP2015A(String), 1047259(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), IN407024B(String), 1047260(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), JP2016511471A(String), 1047261(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), JP2019083048A(String), 1047262(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), JP6816858B2(String), 1047263(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), KR1020140105344A(String), 1047264(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), KR102146244B1(String), 1047265(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), MX2015010598A(String), 1047266(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), MX353242B(String), 1047267(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), RU2015140072A(String), 1047268(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), RU2667496C2(String), 1047269(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), US10775896B2(String), 1047270(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), US20140245234A1(String), 1047271(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), US20190121443A1(String), 1047272(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), VN10030622B(String), 1047273(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), VN44787A(String), 1047274(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), WO2014129862A1(String), 1047275(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), ZA201505799A(String), 1047276(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270670(Integer), ZA201505799B(String), 1047277(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20140245234A1(String), US20140245234A1(String), 1409155200(Integer), 270670(Integer), 184990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184994(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184994(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184994(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184994(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.626 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9565293B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and device for operating mobile terminal based on sensor, and mobile terminal(String), 基于传感器的移动终端操作方法、装置及移动终端(String), US9565293B2(String), A method for operating a mobile terminal based on a sensor is disclosed. The method includes: a sensor is triggered according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, ab operation type, which is corresponding to the digital signal, of the mobile terminal is determined; and a corresponding operation process is performed on the mobile terminal according to the operation type. The disclosure also provides a corresponding device and a mobile terminal including the device. The method for operating the mobile terminal based on the sensor provided in the disclosure completes power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler.(String), 公开了一种基于传感器操作移动终端的方法。 该方法包括:根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; 接收到传感器输出的与触发规则对应的数字信号后,确定该数字信号对应的移动终端的操作类型ab; 根据操作类型对移动终端进行相应的操作过程。 本发明还提供了相应的装置和包括该装置的移动终端。 本发明提供的基于传感器的移动终端操作方法通过传感器完成对移动终端的开机/关机、唤醒、休眠等操作,从而在制作结构的同时给用户带来更好的使用体验。 移动端的更简单。(String), US14/399993(String), 1342368000(Integer), US9565293B2(String), 1486396800(Integer), 1486396800(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 18(Integer), CN101002175A | CN101101523A | CN101847055A | CN101937316A | CN102265253A | US20020173299A1 | US20060005156A1 | US20070161400A1 | US20090143103A1 | US20100123664A1 | US20100245282A1 | US20110183601A1 | US20110238191A1 | US20110244844A1 | US20120019390A1 | US20120306770A1 | US20130063611A1 | WO2012054005A1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184995(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\1622a6ed66cb4b5fa815c60ff24c6249.png(String), 184995(Integer), 1622a6ed66cb4b5fa815c60ff24c6249.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and device for operating mobile terminal based on sensor, and mobile terminal(String), 基于传感器的移动终端操作方法、装置及移动终端(String), US9565293B2(String), A method for operating a mobile terminal based on a sensor is disclosed. The method includes: a sensor is triggered according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, ab operation type, which is corresponding to the digital signal, of the mobile terminal is determined; and a corresponding operation process is performed on the mobile terminal according to the operation type. The disclosure also provides a corresponding device and a mobile terminal including the device. The method for operating the mobile terminal based on the sensor provided in the disclosure completes power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler.(String), 公开了一种基于传感器操作移动终端的方法。 该方法包括:根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; 接收到传感器输出的与触发规则对应的数字信号后,确定该数字信号对应的移动终端的操作类型ab; 根据操作类型对移动终端进行相应的操作过程。 本发明还提供了相应的装置和包括该装置的移动终端。 本发明提供的基于传感器的移动终端操作方法通过传感器完成对移动终端的开机/关机、唤醒、休眠等操作,从而在制作结构的同时给用户带来更好的使用体验。 移动端的更简单。(String), US14/399993(String), 1342368000(Integer), US9565293B2(String), 1486396800(Integer), 1486396800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 18(Integer), CN101002175A | CN101101523A | CN101847055A | CN101937316A | CN102265253A | US20020173299A1 | US20060005156A1 | US20070161400A1 | US20090143103A1 | US20100123664A1 | US20100245282A1 | US20110183601A1 | US20110238191A1 | US20110244844A1 | US20120019390A1 | US20120306770A1 | US20130063611A1 | WO2012054005A1(String), \20230420\1622a6ed66cb4b5fa815c60ff24c6249.png(String), 12(Integer), 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 1. A method for operating a mobile terminal based on a sensor, comprising:presetting a plurality of trigger rules for triggering the sensor according to a plurality of operation types of the mobile terminal;triggering the sensor according to one of the plurality of trigger rules to make the sensor output a digital signal corresponding to the trigger rule;determining an operation type, which is corresponding to the digital signal, of the mobile terminal, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor; andperforming a corresponding operation process on the mobile terminal according to the operation type,wherein after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal comprises:determining that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;determining that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anddetermining that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1.移动终端,包括8.根据权利要求7所述的基于传感器操作移动终端的装置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 2. The method according to claim 1, wherein the plurality of operation types of the mobile terminal comprises at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system.(String), 12.移动终端,包括9.根据权利要求8所述的基于传感器操作移动终端的装置。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 3. The method according to claim 2, wherein the plurality of trigger rules comprises a long press, a click and a double-click; wherein,an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off;an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; andan operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep.(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 4. The method according to claim 3, wherein after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal comprises:determining that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;determining that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anddetermining that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 5. The method according to claim 2, wherein after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal comprises:determining that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;determining that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anddetermining that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 6. A device for operating a mobile terminal based on a sensor, comprising:a presetting component to preset a plurality of trigger rules for triggering the sensor according to a plurality of operation types of the mobile terminal;a triggering component to trigger a sensor according a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule;a determining component to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine an operation type, which is corresponding to the digital signal, of the mobile terminal; andan operating component to perform a corresponding operation process on the mobile terminal according to the operation type,wherein the determining component comprises:a first determining unit to-determine that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;a second determining unit to determine that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anda third determining unit determine that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 7. The device according to claim 6, wherein the operation types of the mobile terminal comprise at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 8. The device according to claim 7, wherein the plurality of trigger rules comprises: a long press, a click and a double-click; wherein,an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off;an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; andan operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 9. The device according to claim 7, wherein the determining component comprises:a first determining unit to-determine that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;a second determining unit to determine that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anda third determining unit to determine that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 10. A mobile terminal, comprising the device for operating the mobile terminal based on the sensor according to claim 6.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 11. A mobile terminal, comprising the device for operating the mobile terminal based on the sensor according to claim 7.(String), 1(Integer), 10(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184995(Integer), 12. A mobile terminal, comprising the device for operating the mobile terminal based on the sensor according to claim 8.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184995(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of communications, and more particularly to a method and device for operating a mobile terminal based on a sensor, and a mobile terminal. BACKGROUND [0002]With higher and higher requirement of people on function and appearance of a mobile terminal, the appearance and production of a mobile terminal become more and more exquisite. At present, the most obvious change of a mobile terminal is that the past keypad is gradually replaced by a touch screen. However, despite this, the increasing aesthetic demand of a user is not satisfied; therefore, the current manufactured mobile terminal is equipped with as few keys as possible or not equipped with key at all. [0003]Currently, most mobile terminals with touch screen mainly include a home key, a power-on key, several function keys at side of the mobile terminals, and so on. However, these mobile terminals usually start a system through an entity power button; the specific method is that: an entity power button is connected with a Power Management Unit (PMU); the PMU will be triggered after long press of the entity power button, and a Main Control Unit (MCU) is powered through the PMU, so as to maintain normal running of the MCU, thus, to complete start-up of a terminal system; when powering off, it is implemented by long press of the entity power button. But, using an entity power button to power on or off a mobile terminal makes the structure of the mobile terminal not simple enough, and can not bring better use experience to a user. SUMMARY [0004]The disclosure provides a method and device for operating a mobile terminal based on a sensor, and a mobile terminal, so as to complete power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor, and bring better use experience to a user while making the structure of the mobile terminal simpler. [0005]The disclosure provides a method for operating a mobile terminal based on a sensor, and the method includes: [0006]the sensor is triggered according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0007]after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, an operation type, which is corresponding to the digital signal, of the mobile terminal is determined; and [0008]a corresponding operation process is performed on the mobile terminal according to the operation type. [0009]Before triggering the sensor according to the preset trigger rule, the method may further include that: [0010]according to a plurality of operation types of the mobile terminal, a plurality of trigger rules for triggering a sensor are preset. [0011]The plurality of operation types of the mobile terminal may include at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system. [0012]The trigger rule may include long press, click or double-click, wherein, an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off; [0013]an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; and [0014]an operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep. [0015]After receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal may include: [0016]after receiving the digital signal, it is determined that the operation type of the mobile terminal is power-on or power-off if the trigger rule corresponding to the digital signal is long press; [0017]if the trigger rule corresponding to the digital signal is click, it is determined that the operation type of the mobile terminal is going to the main menu of system; and [0018]if the trigger rule corresponding to the digital signal is double-click, it is determined that the operation type of the mobile terminal is wakeup or sleep. [0019]The disclosure also provides a device for operating a mobile terminal based on a sensor, and the device includes: [0020]a triggering component configured to trigger the sensor according a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0021]a determining component configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine the operation type, which is corresponding to the digital signal, of the mobile terminal; and [0022]an operating component configured to perform a corresponding operation process on the mobile terminal according to the operation type. [0023]The device for operating the mobile terminal based on the sensor may further include: [0024]a presetting component configured to preset, according to a plurality of operation types of the mobile terminal, a plurality of trigger rules for triggering a sensor. [0025]The operation types of the mobile terminal may include at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system. [0026]The plurality of trigger rules may include long press, click and double-click; wherein, [0027]an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off; [0028]an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; and [0029]an operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep. [0030]The determining component may include: [0031]a first determining unit configured to, after receiving the digital signal, determine that the operation type of the mobile terminal is power-on or power-off if the trigger rule corresponding to the digital signal is long press; [0032]a second determining unit configured to, if the trigger rule corresponding to the digital signal is click, determine that the operation type of the mobile terminal is going to the main menu of system; and [0033]a third determining unit configured to, if the trigger rule corresponding to the digital signal is double-click, determine that the operation type of a mobile terminal is wakeup or sleep. [0034]The disclosure further provides a mobile terminal, including the device for operating the mobile terminal based on the sensor; the device includes: [0035]a triggering component configured to trigger the sensor according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0036]a determining component configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine the operation type, which is corresponding to the digital signal, of the mobile terminal; and [0037]an operating component configured to perform a corresponding operation process on the mobile terminal according to the operation type. [0038]The disclosure adopts the sensor to replace a power-on/off button of a mobile terminal or a button for wakeup or sleep of the mobile terminal. Firstly, the sensor is triggered according to the preset trigger rule, and the sensor outputs the digital signal corresponding to the trigger rule; after the digital signal is received, the digital signal is detected to obtain the operation type of the mobile terminal corresponding to the determined digital signal, and a corresponding operation process is performed on a mobile terminal according to the obtained operation type. By adopting such solution, power-on/off, wakeup, sleep and other operations on the mobile terminal are completed through a sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler. BRIEF DESCRIPTION OF THE DRAWINGS [0039]FIG. 1 is a flowchart of a method for operating a mobile terminal based on a sensor in an embodiment of the disclosure; [0040]FIG. 2 is a flowchart of determining an operation type of a mobile terminal in a method for operating the mobile terminal based on a sensor according to an embodiment of the disclosure; [0041]FIG. 3 is a flowchart of a method for operating a mobile terminal based on a sensor according to another embodiment of the disclosure; [0042]FIG. 4 is a structure diagram of a device for operating a mobile terminal based on a sensor according to an embodiment of the disclosure; [0043]FIG. 5 is a structure diagram of a determining component of a device for operating a mobile terminal based on a sensor according to an embodiment of the disclosure; and [0044]FIG. 6 is a structure diagram of a device for operating a mobile terminal based on a sensor according to another embodiment of the disclosure. [0045]The implementation of the aim, the function features and the advantages of the disclosure will be further illustrated in combination with the accompanying drawings and embodiments. DETAILED DESCRIPTION OF THE EMBODIMENTS [0046]It should be understood that specific embodiments described here are only used for illustrating the disclosure and not intended to limit the disclosure. [0047]A method for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 1, the method includes the following steps. [0048]S10: the sensor is triggered according to a preset trigger rule, in order to make the sensor output a digital signal corresponding to the trigger rule. [0049]The method for operating the mobile terminal based on the sensor provided by the embodiment of the disclosure adopts a sensor to replace a power-on/off button in a mobile terminal or a button for wakeup or sleep of the mobile terminal, so as to implement a function of performing corresponding operation on a mobile terminal without any button. In this way, a system of mobile terminal, to which the method for operating the mobile terminal based on a sensor provided by the disclosure may be applied, may include a sensor, a battery, a Power Management Unit (PMU) and a Main Control Unit (MCU), wherein the battery is used for power supply of the PMU and the sensor; the sensor may be provided at any position on the screen of the mobile terminal; the sensor is connected to a pin of the PMU; after the PMU is triggered, it can supply power for the MCU, so as to maintain normal running of the MCU. At the same time, in the present embodiment, it is also needed to integrate in the system of mobile terminal a software processing module which is used for processing digital information output to the MCU by the sensor. [0050]In the present embodiment, when the mobile terminal is operated according to the actual requirement of a user, firstly, the sensor is triggered according to the trigger rule preset in the system of mobile terminal. The trigger rule includes long press, click or double-click, and different trigger rules correspond to different operation types of the mobile terminal. After the sensor is triggered according to different trigger rules, a processing chip in the sensor converts analogue data corresponding to an trigger action into a digital signal corresponding to the trigger rule, and then outputs the digital signal. In the present embodiment, a pressure sensor may be adopted as the provided sensor. Because the sensor is connected to a pin of the PMU, the PMU may be triggered after the sensor is triggered, thus making a battery work for the PMU; at this point, the PMU powers the MCU on to maintain normal running of the MCU. [0051]S20: after the digital signal, which is corresponding to the trigger rule and is output from the sensor is received, an operation type, which is corresponding to the digital signal, of the mobile terminal is determined. [0052]After the digital signal, which is output from the sensor and obtained from conversion performed by a processing chip of the sensor according to the current trigger rule for triggering the sensor, is received, the digital signal is determined, so as to determine the operation type, which is corresponding to the digital signal, of the mobile terminal, and then to get which operation is needed to perform by a user on the mobile terminal now. In the present embodiment, the operation types of the mobile terminal may include: power-on, power-off, wakeup, sleep, going to the main menu of system, and so on; besides, the preset trigger rules for triggering the sensor corresponds to these operation types; that is, an operation type of the mobile terminal corresponding to the long press is power-on or power-off; an operation type of the mobile terminal corresponding to the click is going to the main menu of system; and an operation type of the mobile terminal corresponding to the double-click is wakeup and/or sleep. [0053]S30: a corresponding operation process is performed on a mobile terminal according to the operation type. [0054]After the operation type of the mobile terminal is determined according to the digital signal output from the sensor, it is needed to perform the corresponding operation process which is corresponding to the current operation type. That is, the mobile terminal is powered on or off; and after powering on, wakeup, sleep, going to the main menu and other operations are performed. [0055]The method for operating the mobile terminal based on the sensor provided by the present embodiment adopts a sensor to replace a power-on/off button in a mobile terminal or a button for wakeup or sleep of the mobile terminal. Firstly, the sensor is triggered according to the preset trigger rule, and the sensor outputs the digital signal corresponding to the trigger rule; after the digital signal is received, the digital signal is detected to obtain the operation type, which is corresponding to the digital signal, of the mobile terminal, and the corresponding operation process is performed on the mobile terminal according to the operation type of the mobile terminal corresponding to the digital signal. By adopting this method, power-on/off, wakeup, sleep and other operations on the mobile terminal are completed through a sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler. [0056]A method for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 2, the step S20 includes the following steps: [0057]S21: after a digital signal is received, a trigger rule corresponding to the digital signal is determined according to the digital signal; if the trigger rule corresponding to the digital signal is long press, turn to the step S22; if the trigger rule corresponding to the digital signal is click, turn to the step S23; if the trigger rule corresponding to the digital signal is double-click, turn to the step S24; [0058]S22: the operation type of the mobile terminal is determined to be power-on or power-off; [0059]S23: the operation type of the mobile terminal is determined to be going to the main menu of system; and [0060]S24: the operation type of the mobile terminal is determined to be wakeup or sleep. [0061]In the above embodiment, after the digital signal, which is corresponding to the trigger rule and is output from the sensor, is received, firstly, the trigger rule corresponding to the digital signal is determined according to the digital signal, and then the operation type of the mobile terminal is determined according to the trigger rule. If the trigger rule corresponding to the digital signal is long press, the operation type of the mobile terminal may be determined to be power-on or power-off. In this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically power-on or power-off; if it is power-on, a software processing module which is integrated in the system and used for processing digital information is loaded, so as to enter a normal power-on process to start the mobile terminal; if it is power-off, the software processing module is released, so as to enter a normal power-off process to power the mobile terminal off. [0062]After entering a power-on process by triggering the sensor and starting the mobile terminal, that is, the mobile terminal is in the power on state, a process for making the mobile terminal sleep or wakeup may also be performed on the mobile terminal. Therefore, if a digital signal is received at this point and the trigger rule corresponding to the digital signal is double-click, it may be determined that the operation type of the mobile terminal corresponding to the digital signal at this point is wakeup or sleep. Likewise, in this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically wakeup or sleep; if it is wakeup, a wakeup process is performed to wake the mobile terminal up. [0063]After the mobile terminal is woken up, if the sensor is triggered again, and a digital signal corresponding to a trigger signal is received, a software processing module used for processing the digital signal is needed to process the digital signal, that is, the operation type of the mobile terminal corresponding to the digital signal at this point is determined. If the trigger rule is click, the operation type of the mobile terminal corresponding to the digital signal at this point is going to the main menu, and the software processing module responses the operation type to return the main menu; if the trigger rule is double-click, the software processing module responses the operation type to make the mobile terminal enter a sleep state. [0064]Of course, after the mobile terminal is woken up, the sensor may also be pressed long to make the mobile terminal power off. That is, at this point, the sensor may also output a digital signal corresponding to long press. Then, if the operation type of the mobile terminal corresponding to the digital signal is determined to be power-off through a software processing module, a normal power-off process is performed directly to power the mobile terminal off. [0065]After the digital signal output from the sensor is received, the operation type corresponding to the digital signal is determined. The operation type of the mobile terminal corresponding to the trigger rule is determined according to different trigger rules for triggering the sensor, and a corresponding operation is performed on the mobile terminal according to the determined operation type. In this way, the process of completing power-on/off, wakeup, sleep and other operations on a mobile terminal through a sensor is further perfected, and better use experience is further brought to a user while further ensuring to make the structure of the mobile terminal simpler. [0066]As shown in FIG. 3, a method for operating a mobile terminal based on a sensor is provided according to another embodiment of the disclosure. [0067]Before performing the step S10, the method further includes the following steps. [0068]Step S40: trigger rules for triggering the sensor are preset according to operation types of the mobile terminal. [0069]Because there are many different operation types of the mobile terminal, it is required the sensor to detect different operation types of the mobile terminal when the sensor is adopted to replace a button of the mobile terminal. In this way, before triggering the sensor, it is needed to preset in the system of mobile terminal the trigger rules, which are corresponding to the operation types, for triggering the sensor according to different operation types, wherein the trigger rules includes long press, click and double-click. After the sensor is triggered by using corresponding trigger rule according to the actual requirement of a user, the system of mobile terminal may identify the trigger rule, so as to determine the operation type corresponding to the trigger rule and complete the corresponding operation process. [0070]The trigger rules for triggering the sensor are preset according to several different operation types of the mobile terminal, so that the trigger rule may be identified after triggering the sensor by using the corresponding trigger rule, and the corresponding operation type may be determined. In this way, a more powerful guarantee is provided for using the sensor to implement power-on/off, wakeup, sleep and other operations on the mobile terminal. [0071]As shown in FIG. 4, a device for operating a mobile terminal based on a sensor is provided according to an embodiment of the disclosure and the device includes: [0072]a triggering component 10 configured to trigger the sensor according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0073]a determining component 20 configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine an operation type, which is corresponding to the digital signal, for the mobile terminal; and [0074]an operating component 30 configured to perform a corresponding operation process on the mobile terminal according to the operation type. [0075]The device for operating the mobile terminal based on the sensor provided by the present embodiment adopts the sensor to replace a power-on/off button of the mobile terminal or a button for wakeup or sleep of the mobile terminal, so as to implement a function of performing corresponding operation on the mobile terminal without any button. In this way, a system of mobile terminal to which the method for operating the mobile terminal based on the sensor provided by the disclosure can be applied may include a sensor, a battery, a PMU and an MCU. The battery is used for power supply of the PMU and the sensor. The sensor may be provided at any position on the screen of the mobile terminal. The sensor is connected to a pin of the PMU. After the PMU is triggered, the PMU may supply power for the MCU, so as to maintain normal running of the MCU. At the same time, in the present embodiment, it is also needed to integrate in the system of mobile terminal a software processing module which is used for processing digital information output to the MCU by the sensor. [0076]In the present embodiment, when the mobile terminal is operated according to the actual requirement of the user, firstly, the sensor is triggered by the triggering component 10 according to the trigger rules preset in the system of mobile terminal. The trigger rules include long press, click and double-click; different trigger rules correspond to different operation types of the mobile terminal. After the sensor is triggered according to different trigger rules, a processing chip in the sensor converts corresponding analogue data of a trigger action into a digital signal corresponding to the trigger rule, and then outputs the digital signal. In the present embodiment, a pressure sensor may be adopted as the provided sensor. Because the sensor is connected to a pin of the PMU, the PMU may be triggered after the sensor is triggered, so as to make a battery supply power to the PMU. At this point, the PMU supply power to the MCU to maintain normal running of the MCU. [0077]After the digital signal which is output from the sensor and obtained from conversion performed by a processing chip of the sensor according to the current trigger rule for triggering the sensor, the digital signal is detected by the determining component 20, so as to determine the operation type of the mobile terminal corresponding to the digital signal, and then to get which operation is needed to perform by the user on the mobile terminal now. In the present embodiment, the operation types of the mobile terminal may include: power-on, power-off, wakeup, sleep, going to the main menu of system, and so on; besides, the preset trigger rules for triggering the sensor corresponds to these operation types; that is, the operation type of the mobile terminal corresponding to the long press is power-on or power-off; the operation type of the mobile terminal corresponding to the click is going to the main menu of system; and the operation type of the mobile terminal corresponding to the double-click is wakeup and/or sleep. [0078]After the operation type of the mobile terminal is determined according to the digital signal output from the sensor, the operating component 30 needs to perform a corresponding operation process according to the current operation type. That is, the mobile terminal is powered on or off; and after powering on, wakeup, sleep, going to the main menu and other operations may be performed. [0079]The device for operating the mobile terminal based on the sensor provided by the present embodiment adopts the sensor to replace a power-on/off button of a mobile terminal or a button for wakeup or sleep of the mobile terminal. Firstly, the sensor is triggered according to the preset trigger rule, and the sensor outputs the digital signal corresponding to the trigger rule; after the digital signal is received, the digital signal is detected to obtain the operation type of the mobile terminal corresponding to the determined digital signal, and a corresponding operation process is performed on a mobile terminal according to the obtained the operation type. By adopting this method, power-on/off, wakeup, sleep and other operations on the mobile terminal are completed through the sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler. [0080]A device for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 5, the determining component 20 specifically includes: [0081]a first determining unit 21 configured to, if the trigger rule corresponding to the digital signal is long press, determine that the operation type of the mobile terminal is power-on or power-off; [0082]a second determining unit 22 configured to, if the trigger rule corresponding to the digital signal is click, determine that the operation type of the mobile terminal is going to the main menu of system; and [0083]a third determining unit 23 configured to, if the trigger rule corresponding to the digital signal is double-click, determine that the operation type of the mobile terminal is wakeup or sleep. [0084]In the above embodiment, after the digital signal which is corresponding to the trigger rule and is output from the sensor is received, firstly, the trigger rule corresponding to the digital signal is determined according to the digital signal, and then the operation type of the mobile terminal is determined according to the trigger rule. If the trigger rule corresponding to the digital signal is long press, the first determining unit 21 may determine that the operation type of the mobile terminal is power-on or power-off. In this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically power-on or power-off; if it is power-on, a software processing module which is integrated in the system and used for processing digital information is loaded, so as to enter a normal power-on process to power on the mobile terminal; if it is power-off, the software processing module is released, so as to enter a normal power-off process to power the mobile terminal off. [0085]After the mobile terminal enters a power-on process when the sensor is trigged and the mobile terminal is powered on, a process for making the mobile terminal sleep or wakeup may also be performed in a case that the mobile terminal is in a power-on state. Therefore, if the digital signal is received at this point and the trigger rule corresponding to the digital signal is double-click, the third determining unit 23 may determine that the operation type of the mobile terminal corresponding to the digital signal at this point is wakeup or sleep. Likewise, in this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically wakeup or sleep; if it is wakeup, a wakeup process is performed to wake the mobile terminal up. [0086]After the mobile terminal is woken up, if the sensor is triggered again, and a digital signal corresponding to a trigger signal is received, a software processing module used for processing the digital signal is needed to process the digital signal, that is, the operation type of the mobile terminal corresponding to the digital signal at this point is determined. If the trigger rule is click, the second determining unit 22 may determine that the operation type of the mobile terminal corresponding to the digital signal at this point is going to the main menu, and the software processing module responds by returning the main the menu; if the trigger rule is double-click, the software processing module responds by making the mobile terminal enter a sleep state. [0087]Of course, after the mobile terminal is woken up, the sensor may also be pressed long to power the mobile terminal off. That is, at this point, the sensor may also output a digital signal corresponding to long press. Then, if an operation type of the mobile terminal corresponding to the digital signal is determined to be power-off through the software processing module, a normal power-off process to power the mobile terminal off is performed directly. [0088]After the digital signal output from the sensor is received, the operation type corresponding to the digital signal is determined. The operation type of the mobile terminal corresponding to the trigger rule is determined according to different trigger rules for triggering the sensor, and a corresponding operation is performed on the mobile terminal according to the determined operation type. In this way, the process of completing power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor is further perfected, and better use experience is further brought to a user while further ensuring to make the structure of the mobile terminal simpler. [0089]A device for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 6, the device further includes: [0090]a presetting component 40 configured to preset, according to a plurality of operation types of the mobile terminal, trigger rules for triggering the sensor. [0091]When the sensor is adopted to replace a button of the mobile terminal, because the mobile terminal includes several different operation types, it is required to adopt a sensor to detect different operation types of the mobile terminal. In this way, before triggering the sensor, the presetting component 40 needs to preset in the system of mobile terminal the trigger rules for triggering the sensor corresponding to the plurality of operation types according to different operation types, wherein the trigger rules includes long press, click and double-click. After the sensor is triggered by using corresponding trigger rule according to the actual requirement of a user, the system of mobile terminal may identify the trigger rule, so as to determine the operation type corresponding to the trigger rule and complete corresponding operation process. [0092]The trigger rules for triggering the sensor is preset according to several different operation types of the mobile terminal, so that a trigger rule may be identified after the sensor is trigged by using corresponding trigger rule, and the corresponding operation type may be determined. In this way, a more powerful guarantee is provided for using the sensor to implement power-on/off, wakeup, sleep and other operations on the mobile terminal. [0093]The embodiment of the disclosure further provides a mobile terminal, including a device for operating a mobile terminal based on a sensor; and the device includes: [0094]a triggering component 10 configured to trigger a sensor according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0095]a determining component 20 configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine an operation type, which is corresponding to the digital signal, of the mobile terminal; and [0096]an operating component 30 configured to per(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种基于传感器的移动终端操作方法、装置及移动终端。 背景 [0002] 随着人们对移动终端的功能和外观的要求越来越高,移动终端的外观和制作也越来越讲究。 目前,移动终端最明显的变化就是过去的键盘逐渐被触摸屏所取代。 然而,尽管如此,仍不能满足用户日益增长的审美需求; 因此,目前制造的移动终端都尽可能少配备按键或根本不配备按键。 [0003] 目前,大多数触摸屏移动终端主要包括主页键、开机键、移动终端侧边的几个功能键等。 然而,这些移动终端通常通过实体电源按钮来启动系统; 具体方法是:实体电源按钮连接电源管理单元(PMU)。 长按实体电源键触发PMU,通过PMU给主控单元(Main Control Unit,MCU)供电,维持MCU正常运行,从而完成终端系统的启动。 关机时,通过长按实体电源键实现。 但是,使用实体电源键来开启或关闭移动终端使得移动终端的结构不够简单,不能给用户带来更好的使用体验。 概括 [0004] 本发明提供了一种基于传感器操作移动终端的方法、装置及移动终端,以通过传感器完成对移动终端的开关机、唤醒、休眠等操作,带来更好的使用体验。 在使移动终端的结构更简单的同时,给用户带来更好的体验。 [0005] 本发明提供了一种基于传感器的移动终端操作方法,该方法包括: [0006] 根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0007] 在接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型。 和 [0008] 根据操作类型对移动终端进行相应的操作处理。 [0009] 在根据预设触发规则触发传感器之前,该方法还可以包括: [0010] 根据移动终端的多种操作类型,预先设置多种触发传感器的触发规则。 [0011] 移动终端的多种操作类型可以包括以下至少一种:开机、关机、唤醒、休眠和进入系统主菜单。 [0012] 触发规则可以包括长按、点击或双击,其中,长按对应的移动终端的操作类型为开机或关机; [0013] 移动终端点击对应的操作类型为进入系统主菜单; 和 [0014] 移动终端双击对应的操作类型为唤醒和/或休眠。 [0015] 在接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型可以包括: [0016] 接收到数字信号后,若数字信号对应的触发规则为长按,则判断移动终端的操作类型为开机或关机。 [0017] 若数字信号对应的触发规则为点击,则判断移动终端的操作类型为进入系统主菜单。 和 [0018] 若数字信号对应的触发规则为双击,则确定移动终端的操作类型为唤醒或睡眠。 [0019] 本发明还提供了一种基于传感器操作移动终端的装置,该装置包括: [0020] 触发组件,用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0021] 判断模块,用于在接收到传感器输出的与触发规则对应的数字信号后,判断移动终端与该数字信号对应的操作类型; 和 [0022] 操作模块,用于根据操作类型对移动终端执行相应的操作过程。 [0023] 基于传感器操作移动终端的装置还可以包括: [0024] 预设模块,用于根据移动终端的多种操作类型,预设多种触发传感器的触发规则。 [0025] 移动终端的操作类型可以包括以下至少一种:开机、关机、唤醒、休眠和进入系统主菜单。 [0026] 多个触发规则可以包括长按、点击和双击; 其中, [0027] 移动终端长按对应的操作类型为开机或关机; [0028] 移动终端点击对应的操作类型为进入系统主菜单; 和 [0029] 移动终端双击对应的操作类型为唤醒和/或休眠。 [0030] 决定性成分可能包括: [0031] 第一判断单元,用于在接收到数字信号后,若数字信号对应的触发规则为长按,则判断移动终端的操作类型为开机或关机; [0032] 第二判断单元,用于若数字信号对应的触发规则为点击,则判断移动终端的操作类型为进入系统主菜单; 和 [0033] 第三判断单元,用于若数字信号对应的触发规则为双击,则判断移动终端的操作类型为唤醒或睡眠。 [0034] 本发明还提供了一种移动终端,包括上述基于传感器的移动终端操作装置; 该设备包括: [0035] 触发组件,用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0036] 判断模块,用于在接收到传感器输出的与触发规则对应的数字信号后,判断移动终端与该数字信号对应的操作类型; 和 [0037] 操作模块,用于根据操作类型对移动终端执行相应的操作过程。 [0038] 本发明采用传感器替代移动终端的开机/关机按钮或移动终端的唤醒或睡眠按钮。 首先,传感器根据预设的触发规则进行触发,传感器输出与触发规则对应的数字信号; 接收到数字信号后,对数字信号进行检测,获取确定的数字信号对应的移动终端的操作类型,并根据获取的操作类型对移动终端进行相应的操作处理。 采用该方案,通过传感器完成对移动终端的开关机、唤醒、睡眠等操作,在简化移动终端结构的同时,给用户带来更好的使用体验。 附图的简要说明 [0039] 图1为本发明实施例中基于传感器的移动终端操作方法的流程图; [0040]图2是根据本发明实施例的基于传感器的移动终端操作方法中确定移动终端操作类型的流程图。 [0041] 图3是根据本发明另一实施例的基于传感器的移动终端操作方法的流程图。 [0042] 图4是根据本发明实施例的基于传感器操作移动终端的装置的结构图; [0043] 图5是根据本发明实施例的基于传感器操作移动终端的装置的判断模块的结构图。 和 [0044] 图6是根据本发明另一实施例的基于传感器操作移动终端的装置的结构图。 [0045] 本发明目的的实现、功能特点及优点将结合附图及实施例作进一步说明。 具体实施方式 [0046] 应当理解,此处所描述的具体实施例仅仅用于说明本发明,并不用于限制本发明。 [0047] 本发明实施例提供了一种基于传感器的移动终端操作方法。 如图1所示,该方法包括以下步骤。 [0048] 小号 10 :传感器按照预设的触发规则触发,使传感器输出符合触发规则的数字信号。 [0049] 本发明实施例提供的基于传感器的移动终端操作方法,采用传感器代替移动终端中的开机/关机按键或移动终端的唤醒或休眠按键,以实现 无需按键即可在移动终端上进行相应操作的功能。 这样,应用本发明提供的基于传感器的移动终端操作方法的移动终端系统可以包括传感器、电池、电源管理单元(PMU)和主控。 单元(MCU),其中电池用于PMU和传感器的供电; 传感器可以设置在移动终端屏幕的任意位置。 传感器连接到PMU的引脚; PMU被触发后,可以为MCU供电,维持MCU的正常运行。 同时,本实施例还需要在移动终端的系统中集成一个软件处理模块,用于处理传感器输出给MCU的数字信息。 [0050] 在本实施例中,当根据用户的实际需求对移动终端进行操作时,首先根据移动终端系统中预设的触发规则触发传感器。 触发规则包括长按、点击或双击,不同的触发规则对应移动终端的不同操作类型。 传感器根据不同的触发规则被触发后,传感器中的处理芯片将触发动作对应的模拟数据转换为触发规则对应的数字信号,然后输出数字信号。 在本实施例中,可以采用压力传感器作为所提供的传感器。 由于传感器连接到PMU的一个管脚上,所以PMU可以在传感器被触发后被触发,从而使电池为PMU工作; 此时PMU给MCU上电,维持MCU正常运行。 [0051] 小号 20 :接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型。 [0052]接收到传感器输出的数字信号,该数字信号由传感器的处理芯片根据当前触发传感器的触发规则进行转换得到,判断该数字信号,从而确定操作类型 ,对应移动终端的数字信号,则可以得到用户现在需要在移动终端上进行哪些操作。 在本实施例中,移动终端的操作类型可以包括:开机、关机、唤醒、睡眠、进入系统主菜单等; 另外,预先设置的触发传感器的触发规则对应这些操作类型; 即长按对应的移动终端的操作类型为开机或关机。 点击对应的移动终端操作类型为进入系统主菜单; 双击对应的移动终端的操作类型为唤醒和/或睡眠。 [0053] 小号 30 :根据操作类型在移动终端上进行相应的操作处理。 [0054] 根据传感器输出的数字信号确定移动终端的操作类型后,需要执行与当前操作类型对应的相应操作处理。 即移动终端处于开机或关机状态; 开机后进行唤醒、休眠、进入主菜单等操作。 [0055] 本实施例提供的基于传感器的移动终端的操作方法,采用传感器代替移动终端中的开机/关机按钮或移动终端的唤醒或休眠按钮。 首先,传感器根据预设的触发规则进行触发,传感器输出与触发规则对应的数字信号; 接收到数字信号后,检测数字信号得到数字信号对应的移动终端的操作类型,并根据移动终端的操作类型对移动终端进行相应的操作处理 终端对应的数字信号。 采用该方法,通过传感器完成对移动终端的开关机、唤醒、睡眠等操作,在简化移动终端结构的同时,给用户带来更好的使用体验。 [0056] 本发明实施例提供了一种基于传感器的移动终端操作方法。 如图2所示,步骤S 20 包括以下步骤: [0057] 小号 21 :接收到数字信号后,根据数字信号确定数字信号对应的触发规则; 若数字信号对应的触发规则为长按,转步骤S 22 ; 若数字信号对应的触发规则为点击,转步骤S 23 ; 若数字信号对应的触发规则为双击,转步骤S 24 ; [0058] 小号 22 :确定移动终端的操作类型为开机或关机; [0059] 小号 23 :确定移动终端的操作类型为进入系统主菜单; 和 [0060] 小号 24 :确定移动终端的操作类型是唤醒还是睡眠。 [0061]在上述实施例中,在接收到传感器输出的与触发规则对应的数字信号后,首先根据数字信号确定与数字信号对应的触发规则,然后确定操作类型。 根据触发规则确定移动终端的号码。 若数字信号对应的触发规则为长按,则可判断移动终端的操作类型为开机或关机。 这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是开机还是关机; 若开机,则加载系统中集成的用于处理数字信息的软件处理模块,进入正常开机流程,启动移动终端。 若为关机,则释放软件处理模块,进入正常关机流程,将移动终端关机。 [0062] 在通过触发传感器启动移动终端进入开机过程后,即移动终端处于开机状态后,还可以在移动终端上进行使移动终端休眠或唤醒的过程。 因此,若此时接收到数字信号,且该数字信号对应的触发规则为双击,则可以确定此时该数字信号对应的移动终端的操作类型为唤醒或睡眠。 同样,这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是唤醒还是睡眠; 如果是唤醒,则执行唤醒过程,将移动终端唤醒。 [0063] 移动终端被唤醒后,如果再次触发传感器,接收到触发信号对应的数字信号,则需要用于处理数字信号的软件处理模块对数字信号进行处理,即操作 确定此时数字信号对应的移动终端的类型。 若触发规则为点击,则此时数字信号对应的移动终端操作类型为进入主菜单,软件处理模块响应该操作类型返回主菜单; 若触发规则为双击,则软件处理模块响应操作类型,使移动终端进入休眠状态。 [0064] 当然,在移动终端被唤醒后,也可以长按感应器使移动终端关机。 也就是说,此时,传感器还可以输出长按对应的数字信号。 然后,如果通过软件处理模块判断出数字信号对应的移动终端的操作类型为关机,则直接执行正常的关机流程,将移动终端关机。 [0065] 在接收到传感器输出的数字信号后,判断该数字信号对应的操作类型。 根据触发传感器的不同触发规则,确定触发规则对应的移动终端的操作类型,并根据确定的操作类型对移动终端进行相应的操作。 这样,进一步完善了通过传感器完成移动终端的开关机、唤醒、休眠等操作的过程,进一步为用户带来更好的使用体验,同时进一步保证了移动终端的架构。 移动端更简单。 [0066] 如图3所示,根据本发明的另一个实施例,提供了一种基于传感器的移动终端的操作方法。 [0067] 在执行步骤S之前 10 ,该方法还包括以下步骤。 [0068] 脚步 40 :根据移动终端的操作类型预先设置触发传感器的触发规则。 [0069]由于移动终端的操作类型多种多样,因此在采用传感器代替移动终端的按键时,需要传感器检测移动终端的不同操作类型。 这样,在触发传感器之前,需要在移动终端的系统中预先设置与操作类型对应的触发规则,用于根据不同的操作类型触发传感器,其中,触发规则包括长按、 单击并双击。 在根据用户的实际需求使用相应的触发规则触发传感器后,移动终端的系统可以识别触发规则,从而确定触发规则对应的操作类型,并完成相应的操作过程。 [0070] 触发传感器的触发规则是根据移动终端的几种不同的操作类型预先设置的,从而可以在使用相应的触发规则触发传感器后识别触发规则,从而确定相应的操作类型。 这样,为利用传感器实现移动终端的开关机、唤醒、睡眠等操作提供了更有力的保障。 [0071] 如图4所示,本发明实施例提供了一种基于传感器操作移动终端的装置,该装置包括: [0072] 触发组件 10 用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0073] 决定因素 20 用于在接收到传感器输出的触发规则对应的数字信号后,为移动终端确定该数字信号对应的操作类型; 和 [0074] 一个操作组件 30 用于根据操作类型对移动终端进行相应的操作处理。 [0075] 本实施例提供的基于传感器的移动终端操作装置,采用传感器替代移动终端的开机/关机按键或移动终端的唤醒或睡眠按键,实现功能 无需任何按钮即可在移动终端上进行相应的操作。 这样,本发明提供的基于传感器的移动终端操作方法可应用的移动终端系统可以包括传感器、电池、PMU和MCU。 电池用于PMU和传感器的供电。 传感器可以设置在移动终端屏幕的任意位置。 传感器连接到 PMU 的一个引脚。 PMU被触发后,PMU可以为MCU供电,以维持MCU的正常运行。 同时,本实施例还需要在移动终端的系统中集成一个软件处理模块,用于处理传感器输出给MCU的数字信息。 [0076] 在本实施例中,当根据用户的实际需求对移动终端进行操作时,首先,传感器被触发组件触发。 10 根据移动端系统预设的触发规则。 触发规则包括长按、单击、双击; 不同的触发规则对应移动终端的不同操作类型。 传感器根据不同的触发规则被触发后,传感器中的处理芯片将触发动作对应的模拟数据转换成与触发规则对应的数字信号,然后输出数字信号。 在本实施例中,可以采用压力传感器作为所提供的传感器。 由于传感器连接到PMU的一个管脚,因此可以在传感器被触发后触发PMU,从而使电池为PMU供电。 此时PMU为MCU供电,维持MCU正常运行。 [0077]传感器输出的数字信号由传感器的处理芯片根据当前触发传感器的触发规则转换得到后,由判断部件检测数字信号。 20 ,从而确定该数字信号对应的移动终端的操作类型,进而得到用户现在需要在移动终端上进行哪些操作。 在本实施例中,移动终端的操作类型可以包括:开机、关机、唤醒、睡眠、进入系统主菜单等; 另外,预先设置的触发传感器的触发规则对应这些操作类型; 即长按对应的移动终端的操作类型为开机或关机。 点击对应的移动端操作类型为进入系统主菜单; 双击对应的移动终端的操作类型为唤醒和/或睡眠。 [0078] 根据传感器输出的数字信号确定移动终端的操作类型后,操作组件 30 需要根据当前的操作类型进行相应的操作流程。 即移动终端处于开机或关机状态; 开机后可以进行唤醒、休眠、进入主菜单等操作。 [0079] 本实施例提供的基于传感器的移动终端操作装置,采用传感器代替移动终端的开机/关机按钮或移动终端的唤醒或休眠按钮。 首先,传感器根据预设的触发规则进行触发,传感器输出与触发规则对应的数字信号; 接收到数字信号后,检测数字信号,获取确定的数字信号对应的移动终端的操作类型,并根据获取的操作类型对移动终端进行相应的操作处理。 采用该方法,通过传感器完成对移动终端的开关机、唤醒、睡眠等操作,在简化移动终端结构的同时,给用户带来更好的使用体验。 [0080] 本发明实施例提供了一种基于传感器的移动终端操作装置。 如图5所示,判断组件 20 具体包括: [0081] 第一确定单位 21 用于若数字信号对应的触发规则为长按,则判断移动终端的操作类型为开机或关机; [0082] 第二决定单位 22 用于若数字信号对应的触发规则为点击,则判断移动终端的操作类型为进入系统主菜单; 和 [0083] 第三决定单位 23 配置为若数字信号对应的触发规则为双击,则判断移动终端的操作类型为唤醒或休眠。 [0084] 在上述实施例中,接收到传感器输出的与触发规则对应的数字信号后,首先根据该数字信号确定与该数字信号对应的触发规则,然后确定该数字信号对应的触发规则的操作类型。 移动终端根据触发规则确定。 若数字信号对应的触发规则为长按,则第一判断单元 21 可以判断移动终端的操作类型是开机还是关机。 这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是开机还是关机; 若开机,则加载系统中集成的用于处理数字信息的软件处理模块,进入正常开机流程,为移动终端开机。 若为关机,则释放软件处理模块,进入正常关机流程,将移动终端关机。 [0085]当传感器被触发移动终端进入开机流程后,移动终端开机,在移动终端处于开机状态的情况下,还可以进行使移动终端休眠或唤醒的流程 状态。 因此,若此时接收到数字信号,且该数字信号对应的触发规则为双击,则第三判断单元 23 可以判断此时数字信号对应的移动终端的操作类型是唤醒还是睡眠。 同样,这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是唤醒还是睡眠; 如果是唤醒,则执行唤醒过程,将移动终端唤醒。 [0086] 移动终端被唤醒后,如果再次触发传感器,接收到触发信号对应的数字信号,则需要用于处理数字信号的软件处理模块对数字信号进行处理,即操作 确定此时数字信号对应的移动终端的类型。 若触发规则为点击,则第二判断单元 22 可以判断此时数字信号对应的移动终端的操作类型为进入主菜单,软件处理模块响应返回主菜单。 若触发规则为双击,则软件处理模块响应使移动终端进入休眠状态。 [0087] 当然,在移动终端被唤醒后,也可以通过长按感应器来关闭移动终端。 也就是说,此时,传感器还可以输出长按对应的数字信号。 然后,如果通过软件处理模块判断出数字信号对应的移动终端的操作类型为关机,则直接执行正常关机流程,将移动终端关机。 [0088] 在接收到传感器输出的数字信号后,判断该数字信号对应的操作类型。 根据触发传感器的不同触发规则,确定触发规则对应的移动终端的操作类型,并根据确定的操作类型对移动终端进行相应的操作。 这样,进一步完善了通过传感器完成移动终端的开关机、唤醒、休眠等操作的流程,进一步为用户带来更好的使用体验,同时进一步保证了移动终端的架构。 移动端更简单。 [0089] 本发明实施例提供了一种基于传感器的移动终端操作装置。 如图6所示,该装置还包括: [0090] 预设组件 40 用于根据移动终端的多种操作类型预设触发传感器的触发规则。 [0091] 当采用传感器代替移动终端的按键时,由于移动终端包括多种不同的操作类型,因此需要采用传感器来检测移动终端的不同操作类型。 这样,在触发传感器之前,预置元件 40 需要根据不同的操作类型,在移动终端的系统中预设触发多个操作类型对应的传感器的触发规则,其中,触发规则包括长按、点击和双击。 在根据用户的实际需求使用相应的触发规则触发传感器后,移动终端的系统可以识别触发规则,从而确定触发规则对应的操作类型,完成相应的操作过程。 [0092]触发传感器的触发规则是根据移动终端的几种不同的操作类型预先设置的,从而可以在传感器被触发后使用相应的触发规则来识别触发规则,并确定相应的操作类型。 这样,为利用传感器实现移动终端的开关机、唤醒、睡眠等操作提供了更有力的保障。 [0093] 本发明实施例还提供了一种移动终端,包括基于传感器的移动终端操作装置; 该设备包括: [0094] 触发组件 10 用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0095] 决定因素 20 用于在接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型; 和 [0096] 一个操作组件 30 用于根据操作类型对移动终端进行相应的操作处理。 [0097] 该移动终端实施例包括图4至图6所示的基于传感器的移动终端操作装置实施例的全部技术方案; 实现的技术效果是一样的,这里不再赘述。 [0098] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的保护范围; 任何基于本发明的说明书和附图的内容所进行的结构或流程的等同替换,或者等同替换在其他相关技术领域的直接或间接应用,均属于本发明权利要求的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102681784A(String), EP2849415A1(String), EP2849415A4(String), US20150215441A1(String), US9565293B2(String), WO2013166778A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102681784A(String), EP2849415A1(String), EP2849415A4(String), US20150215441A1(String), US9565293B2(String), WO2013166778A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9565293B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102681784A(String), EP2849415A1(String), EP2849415A4(String), US20150215441A1(String), US9565293B2(String), WO2013166778A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270674(Integer), CN102681784A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270674(Integer), EP2849415A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270674(Integer), EP2849415A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270674(Integer), US20150215441A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.842 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.842 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270674(Integer), US9565293B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270674(Integer), WO2013166778A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9565293B2(String), US9565293B2(String), 1486396800(Integer), 270674(Integer), 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), SHEN, CHUANGYE(String), LIU, LITIAN(String), SUN, XIAOMIN(String), 中兴通讯股份有限公司(String), SHEN CHUANGYE(String), LIU LITIAN(String), SUN XIAOMIN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184995(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.876 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.876 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.876 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184995(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.885 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHEN, CHUANGYE(String), SHEN CHUANGYE(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIU, LITIAN(String), LIU LITIAN(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SUN, XIAOMIN(String), SUN XIAOMIN(String), 0(Integer), 1681975550(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184995(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75936(Integer), 2(Integer), 184995(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75937(Integer), 2(Integer), 184995(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75938(Integer), 2(Integer), 184995(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7245911B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal for automatically managing country code and method for storing/finding phone number using the same(String), 自动管理国家代码的移动终端及使用该移动终端存储/查找电话号码的方法(String), US7245911B2(String), A mobile terminal for providing a mobile service and a method for storing and finding a phone number using the mobile terminal. The mobile terminal stores and manages country code information, a mobile service subscriber's registration information, and mobile service usage history information; automatically generates a country code of a country where the mobile terminal is located using the mobile service subscriber's registration information and mobile service usage history information; and executes a phone number storage command or a phone number search command using the country code. Where an international roaming service is executed by a user's moving from one country to another country, the mobile terminal can automatically generate a country code or store an arbitrary phone number. Thus, there is no need for mobile service users to manually enter a country code in their mobile terminal when roaming service is executed.(String), 一种用于提供移动服务的移动终端以及使用该移动终端存储和查找电话号码的方法。 移动终端存储和管理国家代码信息、移动业务用户注册信息、移动业务使用历史信息; 利用移动业务用户的注册信息和移动业务使用历史信息,自动生成移动终端所在国家的国家代码; 使用国家代码执行电话号码存储命令或电话号码搜索命令。 在用户从一个国家移动到另一个国家执行国际漫游业务的情况下,移动终端可以自动生成国家代码或存储任意电话号码。 因此,移动服务用户在执行漫游服务时无需手动在其移动终端中输入国家代码。(String), US10/760907(String), 1074528000(Integer), US7245911B2(String), 1184601600(Integer), 1184601600(Integer), 美国(String), 4(Integer), KR(String), 5(Integer), 6(Integer), DE19711096A1 | EP0526832A2 | US20040204117A1 | US20050101323A1 | US5305372A | WO2000041422A1(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184996(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:50.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\05bc6f0eb3ee44ee826448a616e3db08.png(String), 184996(Integer), 05bc6f0eb3ee44ee826448a616e3db08.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal for automatically managing country code and method for storing/finding phone number using the same(String), 自动管理国家代码的移动终端及使用该移动终端存储/查找电话号码的方法(String), US7245911B2(String), A mobile terminal for providing a mobile service and a method for storing and finding a phone number using the mobile terminal. The mobile terminal stores and manages country code information, a mobile service subscriber's registration information, and mobile service usage history information; automatically generates a country code of a country where the mobile terminal is located using the mobile service subscriber's registration information and mobile service usage history information; and executes a phone number storage command or a phone number search command using the country code. Where an international roaming service is executed by a user's moving from one country to another country, the mobile terminal can automatically generate a country code or store an arbitrary phone number. Thus, there is no need for mobile service users to manually enter a country code in their mobile terminal when roaming service is executed.(String), 一种用于提供移动服务的移动终端以及使用该移动终端存储和查找电话号码的方法。 移动终端存储和管理国家代码信息、移动业务用户注册信息、移动业务使用历史信息; 利用移动业务用户的注册信息和移动业务使用历史信息,自动生成移动终端所在国家的国家代码; 使用国家代码执行电话号码存储命令或电话号码搜索命令。 在用户从一个国家移动到另一个国家执行国际漫游业务的情况下,移动终端可以自动生成国家代码或存储任意电话号码。 因此,移动服务用户在执行漫游服务时无需手动在其移动终端中输入国家代码。(String), US10/760907(String), 1074528000(Integer), US7245911B2(String), 1184601600(Integer), 1184601600(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 5(Integer), 6(Integer), DE19711096A1 | EP0526832A2 | US20040204117A1 | US20050101323A1 | US5305372A | WO2000041422A1(String), \20230420\05bc6f0eb3ee44ee826448a616e3db08.png(String), 6(Integer), 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184996(Integer), 1. A mobile terminal for providing mobile service subscribers with a mobile service, comprising:a country code storage unit for coupling each mobile communication network ID received from each of a plurality of mobile communication network MSCs (Mobile Switching Centers) providing a mobile communication network service for every service area with a country code of a prescribed country in which the mobile communication network is located, and for storing and managing the coupling result of the mobile communication network ID and the country code;a subscriber information storage unit for storing and managing mobile service registration information and mobile service usage history information of the mobile service subscriber;a phone number storage unit for storing and managing phone number information; anda controller for detecting a mobile communication network ID of a current PLMN (Public Land Mobile Network) service, retrieving mobile service usage history information from the subscriber information storage unit upon receiving either a phone number storage command or a phone number search command, determining whether a roaming operation of the mobile terminal is executed on the basis of the mobile communication network ID of the current PLMN service and the mobile service usage history information, and executing a phone number storage command or a phone number search command using both a received entry phone number and a detected country code.(String), 1.为移动服务用户提供移动服务的移动终端,包括:国家代码存储单元,用于耦合从多个移动通信网络MSC(移动交换中心)中的每一个接收的每个移动通信网络ID,为每个服务区域提供移动通信网络服务与移动设备所在的规定国家的国家代码通信网络定位,用于存储和管理移动通信网络ID与国家代码的耦合结果;用户信息存储单元,用于存储和管理移动业务用户的移动业务注册信息和移动业务使用历史信息;电话号码存储单元,用于存储和管理电话号码信息;和控制器,用于检测当前PLMN(公共陆地移动网络)服务的移动通信网络ID,在接收到电话号码存储命令或电话号码搜索命令时,从用户信息存储单元中检索移动服务使用历史信息,确定是否移动终端根据当前PLMN业务的移动通信网络ID和移动业务使用历史信息执行漫游操作,并使用接收到的登录电话执行电话号码存储命令或电话号码搜索命令号码和检测到的国家代码。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184996(Integer), 2. The mobile terminal as set forth in claim 1, wherein the phone number storage unit includes a phone number storage field, a phone number storage field excluding country code, and a reception information storage field of the phone number excluding country code.(String), 2.如权利要求1所述的移动终端,其中电话号码存储单元包括电话号码存储字段、不包括国家代码的电话号码存储字段和不包括国家代码的电话号码的接收信息存储字段。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184996(Integer), 3. The mobile terminal as set forth in claim 1, wherein the controller analyzes an entry phone number received for a phone number storage service, determines whether the entry phone number has a country code, retrieves a country code of a country where the mobile terminal is located from the country code storage unit in the case where the entry phone number has no country code, and stores the country code and the entry phone number in the phone number storage unit.(String), 3.如权利要求1所述的移动终端,其中控制器分析接收到的用于电话号码存储服务的入口电话号码,判断入口电话号码是否具有国家代码,如果是,则从国家代码存储单元中检索移动终端所在国家的国家代码。入口电话号码没有国家代码,将国家代码和入口电话号码存储在电话号码存储单元中。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184996(Integer), 4. The mobile terminal as set forth in claim 1, wherein the controller reads a requested phone number from the phone number storage unit, detects a country code of a country where the mobile terminal is located according to the phone number search command, compares the detected country code with an other country code associated with a phone number read from the phone number storage unit, and then displays a phone number having the other country code inserted into the phone number on a display in a predetermined display format when the detected country code is different from the other country code.(String), 4.如权利要求1所述的移动终端,其中控制器从电话号码存储单元中读取请求的电话号码,根据电话号码搜索命令检测移动终端所在国家的国家代码,将检测到的国家代码与与电话号码关联的其他国家代码进行比较从电话号码存储单元中读取,然后当检测到的国家代码不同于其他国家代码时,以预定显示格式在显示器上显示具有插入电话号码中的其他国家代码的电话号码。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184996(Integer), 5. The mobile terminal as set forth in claim 4, wherein the controller, if the detected country code is identical to the other country code read from the phone number storage unit, displays on the display a phone number created by removing the country code from the phone number read from the phone number storage unit in a predetermined display format.(String), 5.如权利要求4所述的移动终端,其中控制器,如果检测到的国家代码与从电话号码存储单元读取的其他国家代码相同,则在显示器上显示通过以预定的时间从从电话号码存储单元读取的电话号码中去除国家代码而创建的电话号码显示格式。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184996(Integer), 6. A method for finding a phone number in a mobile terminal adapted to store and manage country code information of various countries to allow a mutual roaming process among countries, mobile service registration information and mobile service usage history information of the mobile service subscriber comprising the steps of:a) reading a search-requested phone number from a memory contained in the mobile terminal upon receiving a phone number search command;b) detecting a country code of a current country wherein the mobile terminal is located;c) comparing a country code contained in the phone number read at step (a) with the country code detected at step (b); andd) displaying the phone number read at step (a) in the form of a prescribed display format on the basis of the result of step (c),wherein if it is determined at step (c) that the country code detected at step (b) is different from the country code contained in the phone number read at step (a), displaying in step (d) a phone number having the country code contained in the phone number read at step (a), and if it is determined at step (c) that the country code detected at step (b) is the same as the country code contained in the phone number read at step (a), displaying in step (d) a phone number created by removing the country code from the read phone number of step (a).(String), 6.一种在移动终端中查找电话号码的方法,适用于存储和管理各个国家的国家代码信息以允许在国家之间进行相互漫游的过程,移动服务注册信息和移动服务订户的移动服务使用历史信息包括步骤:a)在接收到电话号码搜索命令时,从移动终端包含的存储器中读取搜索请求的电话号码;b)检测移动终端当前所在国家的国家代码;c)将步骤(a)读取的电话号码中包含的国家代码与步骤(b)检测到的国家代码进行比较;和d)在步骤(c)的结果的基础上,以规定的显示格式显示步骤(a)读取的电话号码,其中,如果在步骤(c)确定在步骤(b)检测到的国家代码与在步骤(a)读取的电话号码中包含的国家代码不同,则在步骤(d)显示具有该国家的电话号码在步骤(a)中读取的电话号码中包含的代码,并且如果在步骤(c)中确定在步骤(b)中检测到的国家代码与在步骤(a)中读取的电话号码中包含的国家代码相同),在步骤(d)中显示通过从步骤(a)中读取的电话号码中删除国家代码而创建的电话号码。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184996(Integer), PRIORITY [0001]This application claims priority to an application entitled “WIRELESS TERMINAL FOR AUTO-MANAGING NATIONAL CODE AND METHOD FOR STORING AND SEARCHING PHONE NUMBER USING THE WIRELESS-TERMINAL” filed in the Korean Intellectual Property Office on Jan. 22, 2003 and assigned Serial No. 2003-04307, the contents of which are hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal, also called a wireless terminal, and more particularly to a mobile terminal for automatically managing a country code during roaming, and a method for storing and finding a phone number using the mobile terminal [0004]2. Description of the Related Art [0005]Typically, a GSM (Global System for Mobile communication) is a digital mobile phone system widely used in Europe and other countries in recent times. The GSM is a variant of TDMA (Time Division Multiple Access), and is one of the three most widely used wireless telephony systems: the TDMA system, the CDMA (Code Division Multiple Access) system, and the GSM system. A GSM enables a user who travels abroad to continuously use his or her mobile phone anywhere he or she wishes because many international GSM network enterprisers have entered into roaming agreements with each other. [0006]Conventionally, in the case where a user of a GSM-based mobile service moves from one country to another country and thus a roaming process between such countries is performed, in order to select a phone number previously registered in a mobile terminal and to use the selected phone number to make a phone call to a receiving party, the user must append a corresponding country code to the registered phone number prior to roaming. Also, the user who is roaming from one country to another country must append a country code of an original country to the phone number registered on a PLMN (Public Land Mobile Network) of the original country, in order for the user's phone number as registered on the PLMN to be stored in his or her mobile terminal. [0007]FIG. 1 is an exemplary view illustrating a conceptual diagram wherein an international roaming process occurs on a PLMN service network. Referring to FIG. 1, in the case where a mobile terminal 10 of a subscriber registered in a MSC (Mobile Switching Center) 30 of a PLMN B service having a country code of ‘0033’ roams within a MSC's 20 area of a PLMN A service having a country code of ‘0044’, a user of the mobile terminal 10 must append a country code of ‘0033′’ to a prestored phone number to make a phone call to the prestored phone number. Unless the user appends the country code of ‘0033’ to the prestored phone number, there may-occur an erroneous phone call to another party registered to the PLMN A service having the country code of ‘0044’. For example, in the case where the mobile terminal 10 previously stores a phone number of ‘123-4567’ therein, and a user of the mobile terminal 10 selects only the phone number of 123-4567 without appending an appropriate country code to the phone number of ‘123-4567’, the PLMN A service MSC 20 makes a phone, call to a wrong phone number of ‘0044-123-4567’ instead of a correct phone number of ‘0033-123-4567’. [0008]Conversely, in the case where the PLMN B service subscriber attempts to store in the mobile terminal 10 a phone number of a user registered to the PLMN A service in an area of the PLMN A service MSC 20, the subscriber must append a country code of ‘0044’ corresponding to the PLMN A service to the user's phone number. Otherwise, the mobile terminal 10 recognizes the user's phone number as a phone number of a subscriber registered to the PLMN B service. [0009]In this manner, conventionally, in the case where a user of such a PLMN service moves from one country to another country and thus there occurs a roaming process between countries, he or she must append an additional country code to his or her phone number in order to make a phone call to a called: party or store any phone number in the mobile terminal, resulting in a user's inconvenience. SUMMARY OF THE INVENTION [0010]Therefore, the present invention has been made in view of the above problems, and it is an object of the present invention to provide a mobile terminal for storing any phone number in the mobile terminal, and for automatically generating a country code, when a user is roaming internationally by moving from one country to another country, to make a phone call to a called party without appending a country code to the mobile terminal. [0011]It is another object of the present invention to provide a method for storing a phone number which automatically generates a country code upon receiving a phone number storage command. [0012]It is yet another object of the present invention to provide a method for finding a phone number which automatically generates a country code upon receiving a phone number search command. [0013]In accordance with one aspect of the present invention, the above and other objects can be accomplished by the provision of a mobile terminal for providing mobile service subscribers with a mobile service, comprising: a country code storage unit for coupling each mobile communication network ID with a country code of a prescribed country having the mobile communication network, and storing and managing the coupling result of the mobile communication network ID and the country code, wherein the mobile communication network ID is received from each of a plurality of mobile communication network MSCs (Mobile Switching Centers) providing a mobile communication network service for every service area; a subscriber information storage unit for storing and managing mobile service subscriber's registration information and mobile service usage history information; a phone number storage unit for storing and managing phone number information; and a controller for detecting a mobile communication network ID of a current PLMN service and retrieving mobile service usage history information from the subscriber information storage unit upon receiving a phone number storage command or a phone number search command, for determining whether a roaming operation of the mobile terminal is executed on the basis of the mobile communication network ID of the current PLMN service and the mobile service usage history information, and for executing either one of the phone number storage command or the phone number search command using an entry phone number and the detected country code. [0014]In accordance with another aspect of the present invention, there is provided a method for storing a phone number in a mobile terminal adapted to store and manage country code information of various countries, mobile service subscriber's registration information, and mobile service usage history information, comprising the steps of: a) reading an external entry phone number according to a phone number storage command; b) analyzing the phone number read at step (a) to determine whether the phone number has a country code; c) if the phone number has no country code at step (b), retrieving a country code of a country where the mobile terminal is located using a mobile communication network ID of a current PLMN service; and d) storing the phone number read at step (a) and the country code retrieved at step (c) in the mobile terminal. [0015]In accordance with yet another aspect of the present invention, there is provided a method for finding a phone number in a mobile terminal adapted to store and manage country code information of many countries, mobile service subscriber's registration information, and mobile service usage history information, comprising the steps of: a) reading a search-requested phone number from a memory contained in the mobile terminal upon receiving a phone number search command; b) detecting a country code of a country where the mobile terminal is located; c) comparing a country code contained in the phone number read at step (a) with the country code detected at step (b); and d) displaying the phone number read at step (a) in the form of a prescribed display format on the basis of the result of step (c). BRIEF DESCRIPTION OF THE DRAWINGS [0016]The above and other objects, features and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which: [0017]FIG. 1 is an exemplary view illustrating a conceptual diagram wherein the roaming between countries occurs on a PLMN service network; [0018]FIG. 2 is a view illustrating a schematic diagram of a mobile terminal in accordance with a preferred embodiment of the present invention; [0019]FIG. 3 is a view illustrating an exemplary configuration for storing a country code therein using a country code table in accordance with a preferred embodiment of the present invention; [0020]FIG. 4 is a view illustrating an exemplary configuration for storing/managing a phone number in a phone number storage unit in accordance with a preferred embodiment of the present invention; [0021]FIG. 5 is a flow chart illustrating a procedure for storing a phone number in accordance with a preferred embodiment of the present invention; [0022]FIG. 6 is a flow chart illustrating a procedure for automatically generating a country code in accordance with a preferred embodiment of the present invention; and [0023]FIG. 7 is a flow chart illustrating a procedure for finding a phone number in accordance with a preferred embodiment of the present invention DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0024]Preferred embodiments of the present invention will be described in detail with reference to the attached drawings. In the drawings, the same or similar elements are denoted by the same reference numerals even though they are depicted in different drawings. In the following description, a detailed description of known functions and configurations incorporated herein will be omitted when they might make the subject matter of the present invention unclear. [0025]FIG. 2 is a view illustrating a schematic diagram of a mobile terminal in accordance with a preferred embodiment of the present invention. Referring to FIG. 2, the mobile terminal according to the present invention includes an input unit 110, a controller 120, a subscriber information storage unit 130, a country code table 140, a phone number storage unit 150, and a display 160. [0026]The input unit 110 is adapted to execute an interface between a user and his or her mobile terminal. For example, a representative example of such an input unit 110 is a keypad. The display 160 displays operation status and an external entry item thereon. The input unit 110 and the display 160 are adapted to execute an interface between the mobile terminal and the user, and are typically contained in a general mobile terminal along with a speaker and a microphone (not shown), so their detailed description will hereinafter be omitted. [0027]The country code table 140 stores and manages country code information of various countries for allowing a mutual international roaming process. An exemplary structure for storing a country code in the country code table 140 is depicted in FIG. 3. Referring to FIG. 3, the country code table 140 couples each mobile communication network ID with a country code of a prescribed country where the mobile communication network is located, and individually stores and manages a plurality of couples of the network IDs and the country code, in which the mobile communication network IDs are received from a plurality of MSCs for providing a mobile communication network service for every service area. [0028]The mobile communication network ID is specific information transmitted to a mobile terminal from a MSC providing a mobile communication network service for every service area. Such a mobile communication network ID includes an MCC (Mobile Country Code), an MNC (Mobile Network Code), an LAI (Location Area Identity), and a PLMN enterpriser ID. [0029]The subscriber information storage unit 130 stores and manages a mobile service subscriber's registration information and mobile service usage history information. The mobile service subscriber's registration information is information stored in a mobile terminal when the mobile service subscriber joins a prescribed mobile communication service as a member. A representative example of such mobile communication service subscriber's registration information is a MCC (hereinafter referred to as an H_MCC) of a PLMN (i.e., Home PLMN). The mobile service usage history information is a subscriber's usage record information, stored from the time of a subscriber's mobile service registration up to the time of the subscriber's most recent usage, and is typically stored in a mobile terminal. A representative example of mobile service usage history information is a MCC (hereinafter referred to as an R_MCC) of a PLMN (i.e., registered PLMN) indicating the most recent usage record of a mobile terminal. [0030]The phone number storage unit 150 stores and manages phone number information entered by a user. An exemplary structure for storing/managing phone numbers in the phone number storage unit 150 is shown in FIG. 4. Referring to FIG. 4, the phone number storage unit 150 includes a reception information storage field (e.g., a receiver name), a country code storage field, and a phone number storage field. The phone number storage unit 150 divides a phone number into a country code and a common phone number excluding country code, and stores the phone number divided into the country code and the common phone number, as shown in FIG. 4. [0031]The controller 120 controls an operation of the mobile terminal according to an external control command. Particularly, the controller 120 automatically generates a country code of a country in which the mobile terminal is located using the mobile service subscriber's registration information and the mobile service usage history information stored in the subscriber information storage unit 130. The controller 120 adapts the country code to execute a new phone number storage command or a prestored phone number search command. [0032]A method for automatically generating a country code, a method for storing a phone number using the country code, and a method for finding a phone number using the country code are shown in FIGS. 5–7, respectively. [0033]FIG. 5 is a flow chart illustrating a procedure for storing a phone number in accordance with a preferred embodiment of the present invention. Referring to FIGS. 2 and 5, if a user selects a command for storing a phone number on the input unit 110 and enters a desired phone number at step S110, the controller 120 reads the entry phone number and determines at step S120 whether the entry phone number has a country code. The controller 120 determines whether a specific code or specific number arrangement is contained in the entry phone number at step S120. For example, the controller determines whether specific information of ‘00’ or ‘+’ is contained in the phone number entered by the input unit 110, because a general country code begins with the specific information of ‘00’ or ‘+’ as shown in ‘0044’ or ‘+44’. [0034]The controller 120 determines at step S130 whether a country code of a country in which the mobile terminal is located is automatically generated on the basis of the result of step S120. If it is determined at step S120 that the entry phone number has no country code, the controller 120 automatically generates a country code using a mobile communication network ID of a current PLMN service at step S150, and stores the automatically generated country code and the entry phone number in the phone number storage unit 150 at step S160. If it is determined at step S120 that the entry phone number has a country code, the controller 120 stores the entry phone number in the phone number storage unit 150 at step S140. The controller 120 separately stores in the phone number storage unit 150 the country code received from the input unit 110 or automatically generated at step S150, and a phone number excluding the country code. The controller 120 stores the country code in a country code field of the phone number storage unit 150, and the phone number excluding the country code in a phone number field of the phone number storage unit 150. [0035]Herein, please note that FIG. 6 illustrates the procedure of step S150 of FIG. 5 in detail. FIG. 6 is a flow chart illustrating a procedure for automatically generating a country code in accordance with a preferred embodiment of the present invention. Referring to FIGS. 2 and 6, if the controller 120 decides to automatically generate a country code, it checks a mobile communication network ID (i.e., MCC) of a current PLMN service at step S151, and checks another ID (i.e., R_MCC) of the most recent use of the mobile communication network by the mobile terminal, using a mobile service usage history information previously stored in the subscriber information storage unit 130 at step S153, to determine whether a roaming service is executed. The controller 120 determines at step S155 whether the mobile communication network ID (MCC) of step S151 is identical to the other ID (R_MCC) of step S153. Based on the determination result, the controller 120 retrieves a country code corresponding to either the MCC or the R_MCC from the prestored country code table, and generates a correct country code at step S157 or S159. If it is determined at step S155 that the mobile communication network ID (MCC) is identical to the other ID (R_MCC), the controller 120 determines that a roaming service is not executed and retrieves a country code corresponding to the ID (R_MCC) confirmed at step S153 from the country code table 140. If it is determined at step S155 that mobile communication network ID (MCC) is not identical to the other, ID (R_MCC), the controller 120 determines that a roaming service is executed and retrieves a country code corresponding to the ID (MCC) confirmed at step S151 from the country code table 140. The controller 120 then automatically allocates the retrieved country code as a country code of a country in which the mobile terminal is located. [0036]For instance, in the case where any mobile service subscriber enters a phone number shown in the following Table 1 in an area using a country code of ‘0044’, and attempts to store the entry phone number in a mobile terminal carried with the subscriber, the result of storing the entry phone number in the mobile terminal on the basis of the methods shown in FIGS. 5–6 is shown in the following Table 2: [0037]TABLE 1NamePhone NumberFather0208775331Mother0208786998Boss07787816714 American_uncle001-778835991 [0038]TABLE 2NameCountry CodePhone NumberFather00440208775331Mother00440208786998Boss004407787816714American_uncle 0010778835991 [0039]With reference to the above Tables 1˜2, in the case of ‘American_uncle’, wherein a user manually enters a country code, the mobile terminal stores a country code and phone number entered by the user. In the cases of ‘Father’, ‘Mother’, and ‘Boss’, wherein a user does not enter a country code, it can be seen that a country code of ‘0044’ of a country (or area) where the user is located is automatically appended on the front of each phone number. [0040]FIG. 7 is a flow chart illustrating a procedure for finding a phone number in accordance with a preferred embodiment of the present invention. Referring to FIGS. 2 and 7, if a user selects a command for finding a phone number on the input unit 110 and enters desired search information at step S210, the controller 120 searches through the phone number storage unit 150, and retrieves a corresponding phone number from the phone number storage unit 150 at step S220. The controller 120 determines a country code of a country where a mobile terminal is located at step S230, being a country where the user of the mobile terminal is located. The controller 120 determines at step S240 whether the country code determined at step S230 is identical to the other country code contained in the phone number found at step S220. Based on the result of comparing the two country codes at step S240, the controller 120 controls the display 150 to display a found phone number in a prescribed display format at steps S250–270. If it is determined at step S240 that the country code determined at step S230 is identical to the other country code contained in the phone number found at step S220, the controller 120 removes the country code from the found phone number at step S250, and controls the display 160 to display a phone number excluding country code at step S260. On the other hand, if it is determined at step S240 that the country code determined at step S230 is not identical to the other country code contained in the phone number found at step S220, the controller 120 controls the display 160 to display the found phone number at step S270. In this case, the result may be displayed in a display format preset by the user. For example, in the case where the found phone number is composed of a country code, a regional number, and a common phone number excluding both the country code and the regional number, the country code, the regional number, and the common phone number excluding both the country code and the regional number are distinguishably displayed according to a user-defined display format. For example, a specific sign such as ‘-’ may be inserted between the country code, the regional number, and the common phone number according to the user-defined display format, or may be added only to the rear of the country code. Such a display format may be applicable in various ways according to the type of user-defined information. [0041]For example, in the case where a phone number is stored in the phone number storage unit 150 in the form of the above Table 2 and a user enters a command for finding a phone number of ‘Father’ in a certain area having a country code of ‘0044’, the result of finding the phone number of ‘Father’ in the phone number storage unit 150 on the basis of the methods shown in FIGS. 5–7 is displayed in a format (i.e., 0208775331) excluding the country code of ‘0044’. Such a display format may be applicable in various ways according to the type of user-defined information. [0042]In another example, in the case where a phone number is stored in the phone number storage unit 150 in the form of the above Table 2 and a user enters a command for finding a phone number of ‘Father’ in a place other than the area having the country code of ‘0044’, the result of finding the phone number of ‘Father’ in the phone number storage unit 150 on the basis of the method shown in FIG. 7 is displayed in the a format (i.e., 0044-0208775331) including the country code of ‘0044’. Such a display format may be applicable in various ways according to the type of user-defined information. [0043]As apparent from the above description, in the case where an international roaming service is executed by a user's moving from one country to another country, a mobile terminal automatically generates a country code without appending a country code to the mobile terminal to make a phone call to a called party, or stores an arbitrary phone number in the mobile terminal. Thus, the present invention automatically processes a country code in a mobile terminal when executing an international roaming service between countries, such that there is no need for mobile service users to manually enter a country code in their mobile terminal when they move from one country to another country, thereby increasing users' convenience. [0044]Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims. The present invention has been disclosed on a GSM system, however, it can also be applicable, for example, to a wideband CDMA system which uses a chipset for supporting GSM and CDMA schemes as well as a protocol for supporting the same.(String), 优先 [0001] 本申请要求于 2003 年 1 月 22 日向韩国知识产权局提交并转让序列号为 2003 的题为“用于自动管理国家代码的无线终端和使用无线终端存储和搜索电话号码的方法”的申请的优先权 -04307,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明涉及一种移动终端,也称为无线终端,尤其涉及一种在漫游时自动管理国家代码的移动终端,以及使用该移动终端存储和查找电话号码的方法 [0004] 2.相关技术的描述 [0005] 通常,GSM(全球移动通信系统)是近年来在欧洲和其他国家广泛使用的数字移动电话系统。 GSM 是 TDMA(时分多址)的变体,是三种最广泛使用的无线电话系统之一:TDMA 系统、CDMA(码分多址)系统和 GSM 系统。 GSM 使出国旅行的用户能够在任何他或她希望的地方持续使用他或她的移动电话,因为许多国际 GSM 网络企业已经相互签订了漫游协议。 [0006] 传统上,在基于GSM的移动服务的用户从一个国家移动到另一个国家并因此执行这些国家之间的漫游过程的情况下,为了选择预先在移动终端中注册的电话号码并使用 选择电话号码向接收方拨打电话,用户必须在漫游前将相应的国家代码附加到注册的电话号码。 另外,从一个国家漫游到另一个国家的用户,必须在原国家PLMN(公共陆地移动网络)上注册的电话号码上附加原国家的国家代码,才能使用户的电话号码注册 在PLMN上存储在他或她的移动终端中。 [0007] 如图。 附图说明图1是图示其中国际漫游过程发生在PLMN服务网络上的概念图的示例性视图。 参考图。 1、在有移动终端的情况下 10 在 MSC(移动交换中心)注册的用户 30 国家代码为“0033”的 PLMN B 服务在 MSC 内漫游 20 PLMN 区域 国家代码为“0044”的服务,移动终端的用户 10 必须将国家代码“0033”附加到预存的电话号码才能拨打预存的电话号码。 除非用户将国家代码“0033”附加到预存的电话号码,否则可能会出现错误的电话呼叫注册到国家代码为“0044”的PLMN A服务的另一方。 例如,在移动终端 10 之前存储了一个电话号码“123-4567”,移动终端的用户 10 仅选择电话号码 123-4567 而不将适当的国家代码附加到电话号码“123-4567”,PLMN A 服务 MSC 20 拨打电话,拨打错误的电话号码“0044-123-4567”而不是正确的电话号码“0033-123-4567”。 [0008] 相反,在PLMN B服务用户尝试在移动终端中存储的情况下 10 PLMN A业务MSC区域内注册PLMN A业务的用户电话号码 20 ,用户必须在用户电话号码后附加一个与PLMN A业务对应的国家代码‘0044’。 否则,移动端 10 将用户的电话号码识别为注册到 PLMN B 服务的用户的电话号码。 [0009] 以这种方式,传统上,在这种PLMN服务的用户从一个国家移动到另一个国家并因此在国家之间发生漫游过程的情况下,他或她必须在他或她的电话号码中附加一个额外的国家代码。 为了给被叫打电话:一方或在移动终端中存储任何电话号码,给用户带来不便。 发明内容 [0010]因此,鉴于上述问题做出了本发明,并且本发明的目的是提供一种移动终端,用于在移动终端中存储任何电话号码,并在用户使用时自动生成国家代码。 正在通过从一个国家移动到另一个国家来进行国际漫游,以便在移动终端上不附加国家代码的情况下向被叫方拨打电话。 [0011] 本发明的另一个目的是提供一种存储电话号码的方法,该方法在接收到电话号码存储命令时自动生成国家代码。 [0012] 本发明的又一个目的是提供一种查找电话号码的方法,该方法在接收到电话号码搜索命令时自动生成国家代码。 [0013] 根据本发明的一个方面,上述和其他目的可以通过提供一种用于向移动服务订户提供移动服务的移动终端来实现,包括:国家代码存储单元,用于将每个移动通信网络ID与 具有移动通信网络的规定国家的国家代码,并存储和管理移动通信网络ID和国家代码的耦合结果,其中移动通信网络ID是从多个移动通信网络MSC中的每一个接收的( 移动交换中心)为每个服务区提供移动通信网络服务; 用户信息存储单元,用于存储和管理移动服务用户的注册信息和移动服务使用历史信息; 电话号码存储单元,用于存储和管理电话号码信息; 控制器,用于检测当前PLMN服务的移动通信网络ID,并在接收到电话号码存储命令或电话号码搜索命令时,从用户信息存储单元中检索移动服务使用历史信息,用于确定是否有漫游操作。 移动终端基于当前PLMN服务的移动通信网络ID和移动服务使用历史信息执行,用于使用条目电话号码执行电话号码存储命令或电话号码搜索命令之一,并且 检测到的国家代码。 [0014] 根据本发明的另一方面,提供了一种在移动终端中存储电话号码的方法,用于存储和管理各个国家的国家代码信息、移动服务用户的注册信息和移动服务使用历史信息,包括 步骤:a)根据电话号码存储命令读取外部入口电话号码; b)分析在步骤(a)中读取的电话号码以确定该电话号码是否具有国家代码; c)如果步骤(b)的电话号码没有国家代码,则使用当前PLMN业务的移动通信网络ID,获取移动终端所在国家的国家代码; d)将在步骤(a)中读取的电话号码和在步骤(c)中检索到的国家代码存储在移动终端中。 [0015] 根据本发明的又一方面,提供了一种在移动终端中查找电话号码的方法,该方法适用于存储和管理多个国家的国家代码信息、移动服务用户的注册信息和移动服务使用历史信息, 包括以下步骤: a)在接收到电话号码搜索命令时,从包含在移动终端中的存储器中读取请求搜索的电话号码; b) 检测移动终端所在国家的国家代码; c) 将在步骤 (a) 读取的电话号码中包含的国家代码与在步骤 (b) 检测到的国家代码进行比较; d)根据步骤(c)的结果,以规定的显示格式显示在步骤(a)中读取的电话号码。 附图的简要说明 [0016] 本发明的上述和其他目的、特征和其他优点将从以下结合附图的详细描述中得到更清楚的理解,其中: [0017]如图。 附图说明图1是表示国家间漫游发生在PLMN服务网络上的概念图的示例图。 [0018] 如图。 图2为本发明较佳实施例的移动终端示意图。 [0019] 如图。 图3是示出根据本发明的优选实施例的使用国家代码表在其中存储国家代码的示例性配置的视图; [0020] 如图。 图4是表示本发明的优选实施方式的电话号码存储部中的电话号码的存储/管理的结构例的图。 [0021] 如图。 图5是说明根据本发明优选实施例的用于存储电话号码的过程的流程图; [0022] 如图。 图6是说明根据本发明优选实施例的自动生成国家代码的过程的流程图; 和 [0023] 如图。 图7是说明根据本发明优选实施例的查找电话号码的过程的流程图 优选实施例的详细说明 [0024] 将参照附图详细描述本发明的优选实施例。 在附图中,相同或相似的元件由相同的附图标记表示,即使它们在不同的附图中被描绘。 在以下描述中,当包含在本文中的已知功能和配置可能使本发明的主题不清楚时,将省略它们的详细描述。 [0025] 如图。 图2是示出了根据本发明优选实施例的移动终端的示意图。 参考图。 2、根据本发明的移动终端包括输入单元 110 , 一个控制器 120 ,订户信息存储单元 130 , 国家代码表 140 ,电话号码存储单元 150 , 和一个显示器 160 . [0026] 输入单元 110 用于执行用户与其移动终端之间的接口。 例如,这种输入单元的一个代表例子 110 是键盘。 显示器 160 显示运行状态和外部输入项。 输入单元 110 和显示器 160 用于执行移动终端和用户之间的接口,通常与扬声器和麦克风(未示出)一起包含在普通移动终端中,因此在下文中将省略对其的详细描述。 [0027] 国家代码表 140 存储和管理各个国家的国家代码信息,以实现相互国际漫游。 用于在国家代码表中存储国家代码的示例性结构 140 在图 1 中描绘。 3.参考图。 3、国家代码表 140 将每个移动通信网络ID与该移动通信网络所在的规定国家的国家代码进行耦合,并单独存储和管理多个网络ID和国家代码对,其中接收移动通信网络ID 多个MSC,用于为每个服务区域提供移动通信网络服务。 [0028] 移动通信网络ID是从为每个服务区域提供移动通信网络服务的MSC发送到移动终端的特定信息。 这种移动通信网络ID包括MCC(移动国家代码)、MNC(移动网络代码)、LAI(位置区域标识)和PLMN企业ID。 [0029] 订户信息存储单元 130存储和管理移动服务用户的注册信息和移动服务使用历史信息。 移动服务用户注册信息是当移动服务用户作为会员加入规定的移动通信服务时存储在移动终端中的信息。 这种移动通信服务订户的注册信息的代表性示例是PLMN(即,归属PLMN)的MCC(以下称为H_MCC)。 移动服务使用历史信息是订户的使用记录信息,从订户的移动服务注册时间到订户最近一次使用的时间存储,并且通常存储在移动终端中。 移动服务使用历史信息的代表性示例是指示移动终端的最近使用记录的PLMN(即,注册的PLMN)的MCC(以下称为R_MCC)。 [0030] 电话号码存储单元 150 存储和管理用户输入的电话号码信息。 用于在电话号码存储单元中存储/管理电话号码的示例性结构 150 如图所示。 4.参考图。 4、电话号码存储单元 150 包括接收信息存储字段(例如,接收者姓名)、国家代码存储字段和电话号码存储字段。 电话号码存储单元 150 将电话号码分为国家码和不包括国家码的普通电话号码,并存储分为国家码和普通电话号码的电话号码,如图2所示。 4. [0031] 控制器 120 根据外部控制命令控制移动终端的操作。 特别是控制器 120 使用移动服务用户的注册信息和存储在用户信息存储单元中的移动服务使用历史信息自动生成移动终端所在国家的国家代码 130 . 控制器 120 调整国家代码以执行新的电话号码存储命令或预先存储的电话号码搜索命令。 [0032] 一种自动生成国家代码的方法、一种使用国家代码存储电话号码的方法、以及一种使用国家代码查找电话号码的方法如图1和图2所示。 5-7,分别。 [0033] 如图。 图5是说明根据本发明优选实施例的用于存储电话号码的过程的流程图。 参考图。 参照图2和图5,如果用户在输入单元上选择用于存储电话号码的命令 110 并在步骤 S 输入所需的电话号码 110 , 控制器 120 读取入口电话号码并在步骤 S 确定 120 入口电话号码是否有国家代码。 控制器 120 在步骤 S 确定输入电话号码中是否包含特定代码或特定号码排列 120 . 例如,控制器确定输入单元输入的电话号码中是否包含“00”或“+”的特定信息 110 ,因为一般国家代码以“00”或“+”的特定信息开头,如“0044”或“+44”所示。 [0034] 控制器 120 在步骤 S 确定 130 是否根据步骤S的结果自动生成移动终端所在国家的国家代码 120 . 如果在步骤 S 确定 120 输入电话号码没有国家代码,控制器 120 在步骤 S,使用当前 PLMN 服务的移动通信网络 ID 自动生成国家代码 150 ,并将自动生成的国家代码和输入的电话号码存储在电话号码存储单元中 150 在步骤 S 160 . 如果在步骤 S 确定 120 输入电话号码有国家代码,控制器 120 将输入电话号码存储在电话号码存储单元中 150 在步骤 S 140 . 控制器 120 分别存储在电话号码存储单元中 150 从输入单元接收到的国家代码 110 或在步骤 S 自动生成 150,以及不包括国家/地区代码的电话号码。 控制器 120 将国家代码存储在电话号码存储单元的国家代码字段中 150 ,以及电话号码存储单元的电话号码字段中不包括国家代码的电话号码 150 . [0035] 在此,请注意图。 图6说明步骤S的过程 150 图。 5 详细。 如图。 图6是说明根据本发明优选实施例的用于自动生成国家代码的过程的流程图。 参考图。 2和6,如果控制器 120 决定自动生成国家代码,它在步骤 S 检查当前 PLMN 服务的移动通信网络 ID(即 MCC) 151 ,并使用先前存储在订户信息存储单元中的移动服务使用历史信息,检查移动终端最近使用移动通信网络的另一个ID(即,R_MCC) 130 在步骤 S 153 ,判断是否执行漫游服务。 控制器 120 在步骤 S 确定 155 步骤S的移动通信网络ID(MCC)是否 151 与步骤 S 的另一个 ID (R_MCC) 相同 153 . 根据判断结果,控制器 120 从预存的国家代码表中检索对应于MCC或R_MCC的国家代码,并在步骤S生成正确的国家代码 157 或小号 159 . 如果在步骤 S 确定 155 如果移动通信网络 ID (MCC) 与另一个 ID (R_MCC) 相同,则控制器 120 确定未执行漫游服务并检索与在步骤S确认的ID(R_MCC)对应的国家代码 153 从国家代码表 140 . 如果在步骤 S 确定 155 即移动通信网络 ID (MCC) 与其他 ID (R_MCC) 不同,控制器 120 确定执行漫游服务并检索与在步骤 S 确认的 ID (MCC) 对应的国家代码 151 从国家代码表 140 . 控制器 120 然后将检索到的国家代码自动分配为移动终端所在国家的国家代码。 [0036] 例如,如果任何移动服务用户在使用国家代码“0044”的地区输入下表1中所示的电话号码,并试图将输入的电话号码存储在用户所携带的移动终端中, 基于图1和2所示方法在移动终端中存储入口电话号码的结果。 5-6如下表2所示: [0037] 表格1 姓名 电话号码 父亲 0208775331 母亲 0208786998 老板 07787816714  American_uncle 001-778835991 [0038] 表 2 姓名 国家代码 电话号码 父亲 0044 0208775331 母亲 0044 0208786998 老板 0044 07787816714 American_uncle  001 0778835991 [0039] 参照上述表1~表2,在用户手动输入国家代码的“American_uncle”的情况下,移动终端存储用户输入的国家代码和电话号码。 在“父亲”、“母亲”和“老板”的情况下,用户没有输入国家代码,可以看出用户所在国家(或地区)的国家代码“0044” 位于每个电话号码的前面会自动附加。 [0040] 如图。 图7是说明根据本发明优选实施例的查找电话号码的过程的流程图。 参考图。 参照图2和图7,如果用户在输入单元上选择用于查找电话号码的命令 110 并在步骤 S 输入所需的搜索信息 210 , 控制器 120 搜索电话号码存储单元 150 ,并从电话号码存储单元中检索对应的电话号码 150 在步骤 S 220 . 控制器 120 在步骤S确定移动终端所在国家的国家代码 230 ,为移动终端用户所在的国家。 控制器 120 在步骤 S 确定 240 是否在步骤 S 确定的国家代码 230 与步骤 S 中找到的电话号码中包含的其他国家/地区代码相同 220 . 基于在步骤 S 比较两个国家代码的结果 240 , 控制器 120控制显示 150 在步骤 S 以规定的显示格式显示找到的电话号码 250 – 270 . 如果在步骤 S 确定 240 在步骤 S 确定的国家代码 230 与步骤 S 中找到的电话号码中包含的其他国家/地区代码相同 220 , 控制器 120 在步骤 S 从找到的电话号码中删除国家代码 250 , 并控制显示 160 在步骤 S 显示不包括国家代码的电话号码 260 . 另一方面,如果在步骤 S 确定 240 在步骤 S 确定的国家代码 230 与步骤 S 中找到的电话号码中包含的其他国家/地区代码不同 220 , 控制器 120 控制显示 160 在步骤 S 显示找到的电话号码 270 . 在这种情况下,可以以用户预设的显示格式来显示结果。 例如,在查找到的电话号码由国家代码、地区号码和不包括国家代码和地区号码的公共电话号码组成的情况下,国家代码、地区号码和公共电话号码 除国家代码和地区号码外,按照用户自定义的显示格式进行区分显示。 例如,可以根据用户自定义的显示格式,在国家代码、地区号码和常用电话号码之间插入“-”等特定符号,也可以只在国家代码后面添加“-”。 这种显示格式可以根据用户定义信息的类型以各种方式应用。 [0041] 例如,在电话号码存储单元中存储电话号码的情况下 150 如上表2的形式,用户在国家代码为“0044”的某个地区输入查找“父亲”电话号码的命令,在手机中查找“父亲”电话号码的结果 号码存储单元 150 基于图1和2所示的方法。 5-7 以不包括国家代码“0044”的格式(即 0208775331)显示。 这种显示格式可以根据用户定义信息的类型以各种方式应用。 [0042] 在另一示例中,在电话号码存储在电话号码存储单元中的情况下 150 如上表2的形式,用户在国家代码为“0044”的地区以外的地方输入查找“父亲”电话号码的命令,得到“父亲”电话号码的结果 在电话号码存储单元中 150 基于图1所示的方法。 7以a格式(即0044-0208775331)显示,包括国家代码“0044”。 这种显示格式可以根据用户定义信息的类型以各种方式应用。 [0043] 从上面的描述可以看出,在用户从一个国家移动到另一个国家来执行国际漫游业务的情况下,移动终端自动生成国家代码,而不需要在移动终端上附加国家代码来拨打电话。 发送给被叫方,或在移动终端中存储任意电话号码。 因此,本发明在执行国家间国际漫游业务时,自动处理移动终端中的国家代码,使得移动服务用户在从一个国家移动到另一个国家时,无需在其移动终端中手动输入国家代码。 另一个国家,从而增加了用户的便利性。 [0044] 尽管为了说明的目的已经公开了本发明的优选实施例,但是本领域技术人员将理解,在不背离所附权利要求中公开的本发明的范围和精神的情况下,各种修改、添加和替换是可能的。 本发明已经在GSM系统上公开,然而,它也可以应用于例如使用支持GSM和CDMA方案的芯片组以及支持它们的协议的宽带CDMA系统。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN100527870C(String), CN1518387A(String), EP1441557A2(String), EP1441557A3(String), EP1441557B1(String), KR100929090B1(String), KR1020040067277A(String), US20040147260A1(String), US20070178896A1(String), US7245911B2(String), US7418262B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN100527870C(String), CN1518387A(String), EP1441557A2(String), EP1441557A3(String), EP1441557B1(String), KR100929090B1(String), KR1020040067277A(String), US20040147260A1(String), US20070178896A1(String), US7245911B2(String), US7418262B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.085 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7245911B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.094 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN100527870C(String), CN1518387A(String), EP1441557A2(String), EP1441557A3(String), EP1441557B1(String), KR100929090B1(String), KR1020040067277A(String), US20040147260A1(String), US20070178896A1(String), US7245911B2(String), US7418262B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), CN100527870C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.107 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), CN1518387A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), EP1441557A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), EP1441557A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), EP1441557B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.147 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), KR100929090B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), KR1020040067277A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), US20040147260A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), US20070178896A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), US7245911B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270675(Integer), US7418262B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.212 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7245911B2(String), US7245911B2(String), 1184601600(Integer), 270675(Integer), 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184996(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184996(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184996(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 184996(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.295 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20110319037A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Implementing method for matching frequency bands of mobile terminals, and mobile terminal and mainboard thereof(String), 移动终端频段匹配的实现方法、移动终端和主板(String), US20110319037A1(String), An implementing method for matching the frequency bands of the mobile terminals, a mobile terminal, and a mainboard thereof are disclosed. The mobile terminal involves a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module. The mobile terminal further involves a first connection selection module and a second connection selection module. The implementing method for matching the frequency bands of the mobile terminals comprises the following steps. The multi frequency bands bonding pad compatibility is achieved respectively on the circuit board by the radio-frequency transmitting module, the radio-frequency receiving module and the radio-frequency front-end module. When the mobile terminal has to work within a certain frequency band, one end of the first connection selection module is connected with the transmitting pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency transmitting module. One end of the second connection selection module is connected with the receiving pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency receiving module. The radio-frequency front-end module is connected with the radio-frequency transmitting module and the radio-frequency receiving module.(String), 本发明公开了一种移动终端频段匹配的实现方法、移动终端及其主板。 移动终端包括具有至少两个频段的信号发射/接收模块、射频发射模块、射频接收模块和射频前端模块。 移动终端还包括第一连接选择模块和第二连接选择模块。 该移动终端频段匹配的实现方法包括以下步骤。 射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容。 当移动终端必须工作在某个频段时,第一连接选择模块的一端与信号收发模块中该频段的发射管脚相连,另一端与射频相连。 发射模块。 第二连接选择模块的一端与信号发射/接收模块中频段的接收引脚相连,另一端与射频接收模块相连。 射频前端模块与射频发射模块和射频接收模块连接。(String), US13/225687(String), 1315238400(Integer), US20110319037A1(String), 1325088000(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 3(Integer), US20080100374A1 | US5915212A | US6845126B2(String), 21(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184997(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\39afbe5f71bd4b8588befadb1c57084c.png(String), 184997(Integer), 39afbe5f71bd4b8588befadb1c57084c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Implementing method for matching frequency bands of mobile terminals, and mobile terminal and mainboard thereof(String), 移动终端频段匹配的实现方法、移动终端和主板(String), US20110319037A1(String), An implementing method for matching the frequency bands of the mobile terminals, a mobile terminal, and a mainboard thereof are disclosed. The mobile terminal involves a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module. The mobile terminal further involves a first connection selection module and a second connection selection module. The implementing method for matching the frequency bands of the mobile terminals comprises the following steps. The multi frequency bands bonding pad compatibility is achieved respectively on the circuit board by the radio-frequency transmitting module, the radio-frequency receiving module and the radio-frequency front-end module. When the mobile terminal has to work within a certain frequency band, one end of the first connection selection module is connected with the transmitting pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency transmitting module. One end of the second connection selection module is connected with the receiving pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency receiving module. The radio-frequency front-end module is connected with the radio-frequency transmitting module and the radio-frequency receiving module.(String), 本发明公开了一种移动终端频段匹配的实现方法、移动终端及其主板。 移动终端包括具有至少两个频段的信号发射/接收模块、射频发射模块、射频接收模块和射频前端模块。 移动终端还包括第一连接选择模块和第二连接选择模块。 该移动终端频段匹配的实现方法包括以下步骤。 射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容。 当移动终端必须工作在某个频段时,第一连接选择模块的一端与信号收发模块中该频段的发射管脚相连,另一端与射频相连。 发射模块。 第二连接选择模块的一端与信号发射/接收模块中频段的接收引脚相连,另一端与射频接收模块相连。 射频前端模块与射频发射模块和射频接收模块连接。(String), US13/225687(String), 1315238400(Integer), US20110319037A1(String), 1325088000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 3(Integer), US20080100374A1 | US5915212A | US6845126B2(String), \20230420\39afbe5f71bd4b8588befadb1c57084c.png(String), 21(Integer), 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 1. An implementing method for matching frequency bands of a mobile terminal, which comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module, wherein said mobile terminal further comprises a first connection selection module and a second connection selection module, the method comprising:achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module; andwhen said mobile terminal needs to work within a certain frequency band, connecting one end of said first connection selection module to a transmitting pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency transmitting module; connecting one end of said second connection selection module to a receiving pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency receiving module; and connecting said radio-frequency front-end module to said radio-frequency transmitting module and said radio-frequency receiving module.(String), 1.如权利要求8所述的移动终端,其中所述射频发射模块包括射频功率放大器、耦合器和匹配网络。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 2. The implementing method as claimed in claim 1, wherein said first connection selection module or said second connection selection module comprises at least two of resistors, capacitor(s) or inductor(s).(String), 12.如权利要求8所述的移动终端,其中所述射频接收模块包括匹配网络。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 3. The implementing method as claimed in claim 1, wherein achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module includes that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module.(String), 13.如权利要求8所述的移动终端,其中所述射频前端模块包括双工器和匹配网络。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 4. The implementing method as claimed in claim 1, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 14.如权利要求8所述的移动终端,其中所述移动终端为手机或网卡。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 5. The implementing method as claimed in claim 1, wherein said radio-frequency receiving module comprises a matching network.(String), 15.一种移动终端主板,主板包括信号发射/接收模块接口、射频发射模块接口、射频接收模块接口和射频前端模块接口,其中所述主板还包括第一连接选择模块接口和第二连接选择模块接口。模块接口,其中,所述第一连接选择模块接口的一端用于选择性地连接所述信号发射/接收模块接口中的管脚,其另一端用于连接所述射频发射模块接口。所述第二连接选择模块的一端用于选择性地连接所述信号发射/接收模块接口中的管脚,其另一端用于连接所述射频接收模块接口。所述射频前端模块接口连接所述射频发射模块接口和所述射频接收模块接口。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 6. The implementing method as claimed in claim 1, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 16.如权利要求3所述的实施方法,其中所述射频发射模块包括射频功率放大器、耦合器和匹配网络。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 7. The implementing method as claimed in claim 1, wherein said mobile terminal is a cell phone or a network card.(String), 17.如权利要求3所述的实施方法,其中所述射频接收模块包括匹配网络。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 8. A mobile terminal, which comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module, a radio-frequency front-end module and an antenna module, wherein said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieve the multi frequency bands bonding pad compatibility respectively on a circuit board; andsaid mobile terminal further comprises a first connection selection module and a second connection selection module, wherein one end of said first connection selection module is connected to a transmitting pin of a certain frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency transmitting module; one end of said second connection selection module is connected to a receiving pin of the frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency receiving module; and said radio-frequency front-end module is connected to said radio-frequency transmitting module and said radio-frequency receiving module.(String), 18.如权利要求3所述的实施方法,其中所述射频前端模块包括双工器和匹配网络。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 9. The mobile terminal as claimed in claim 8, wherein said first connection selection module or said second connection selection module comprises at least two of resistors, capacitor(s) or inductor(s).(String), 19.如权利要求10所述的移动终端,其中所述射频发射模块包括射频功率放大器、耦合器和匹配网络。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 10. The mobile terminal as claimed in claim 8, wherein said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieving the multi frequency bands bonding pad compatibility respectively on a circuit board specifically refers to that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module.(String), 20.如权利要求10所述的移动终端,其中所述射频接收模块包括匹配网络。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 11. The mobile terminal as claimed in claim 8, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 21.如权利要求10所述的移动终端,其中所述射频前端模块包括双工器和匹配网络。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 12. The mobile terminal as claimed in claim 8, wherein said radio-frequency receiving module comprises a matching network.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 13. The mobile terminal as claimed in claim 8, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 1(Integer), 12(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 14. The mobile terminal as claimed in claim 8, wherein said mobile terminal is a cell phone or a network card.(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 15. A mainboard for a mobile terminal, the mainboard comprising a signal transmitting/receiving module interface, a radio-frequency transmitting module interface, a radio-frequency receiving module interface and a radio-frequency front-end module interface, wherein said mainboard further comprises a first connection selection module interface and a second connection selection module interface, wherein one end of said first connection selection module interface is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency transmitting module interface; one end of said second connection selection module is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency receiving module interface; and said radio-frequency front-end module interface connects said radio-frequency transmitting module interface and said radio-frequency receiving module interface.(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 16. The implementing method as claimed in claim 3, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 1(Integer), 15(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 17. The implementing method as claimed in claim 3, wherein said radio-frequency receiving module comprises a matching network.(String), 1(Integer), 16(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 18. The implementing method as claimed in claim 3, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 1(Integer), 17(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 19. The mobile terminal as claimed in claim 10, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 1(Integer), 18(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 20. The mobile terminal as claimed in claim 10, wherein said radio-frequency receiving module comprises a matching network.(String), 1(Integer), 19(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184997(Integer), 21. The mobile terminal as claimed in claim 10, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 1(Integer), 20(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184997(Integer), [0001]This is a continuation of International Application PCT/CN2009/075636, with an International Filing Date of Dec. 16, 2009, which claims priority to Chinese Application No. 200910108393.7, filed Jun. 24, 2009, each of which is incorporated by reference. TECHNICAL FIELD [0002]The present invention relates to the field of communication technology and, particularly, to an implementing method for matching the frequency bands of the mobile terminals, and a mobile terminal and a mainboard thereof. BACKGROUND ART [0003]The development of the modern communication technology is extremely rapid. Not only there are a variety of systems, such as Global System for Mobile Communication (GSM for short), Code Division Multiple Access (CDMA for short), Wideband Code Division Multiple Access (WCDMA for short), etc., but also there are a variety of frequency bands which a same system needs to support, for example, CDMA needs to support 800M, 1.9 G, 450M, etc. In order to support multi frequency bands, radio-frequency transmitting/receiving circuit(s) corresponding to each of the frequency bands has to be added into the mobile terminal of a certain system when the circuit thereof is designed. However, for a specific market and a specific operator, normally only a specific frequency band is used. Taking CDMA as an example, CDMA 800M is used in China, while CDMA 1.9 G is used in Indonesia. [0004]FIG. 1 is a schematic diagram of a module in which a mobile terminal with double frequency bands is supported by two radio-frequency transmitting/receiving circuits according to the related art. As shown in FIG. 1, it illustrates the existing method in which two radio-frequency transmitting/receiving circuits are used to support a mobile terminal with double frequency bands. The function of a band 1 is achieved by means of one radio-frequency transmitting/receiving circuit supporting the band 1, and the function of a band 2 is achieved by means of the other radio-frequency transmitting/receiving circuit supporting the band 2. Such method of employing a plurality of radio-frequency transmitting/receiving circuits to make multi frequency bands compatible cannot be realized in many mobile terminals since it occupies a relatively larger area of the circuit board. At present, this is addressed by a method of designing a plurality of circuit boards. Taking CDMA as an example, in a common method, as for the CDMA 800M market, one circuit board is design on which only the radio-frequency transmitting/receiving devices related to CDMA 800M are bonded and the radio-frequency transmitting/receiving devices related to CDMA 1.9 G are not bonded; while as for the CDMA 1.9 G market, one circuit board is designed on which only the radio-frequency transmitting/receiving devices related to CDMA 1.9 G are bonded and the radio-frequency transmitting/receiving devices related to CDMA 800M are not bonded. The circuit devices of the corresponding frequency band are bonded according to the specific market demand. Such solution causes that the number of the circuit boards to be designed in the mobile terminal is increased, and thus the cost is improved, the design period is prolonged, and more developers are needed. SUMMARY OF THE INVENTION [0005]The technical problem to be addressed by the present invention is to provide an implementing method for matching the frequency bands of the mobile terminals, a mobile terminal, and a mainboard thereof, so as to overcome the defects that the number of the designed circuit boards in the mobile terminal is increased, the cost is improved, the design period is prolonged, and more developers are needed. [0006]In order to solve the abovementioned technical problem, the present invention provides an implementing method for matching frequency bands of a mobile terminal, the mobile terminal comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module, said mobile terminal further comprises a first connection selection module and a second connection selection module, and the implementing method for matching the frequency bands of the mobile terminal comprises:[0007]achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module;[0008]when said mobile terminal needs to work within a certain frequency band, connecting one end of said first connection selection module to the transmitting pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency transmitting module; connecting one end of said second connection selection module to a receiving pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency receiving module; and connecting said radio-frequency front-end module to said radio-frequency transmitting module and said radio-frequency receiving module. [0009]Further, in the abovementioned method, said first selection module or said second selection module comprises at least two of resistors, capacitor(s) or inductor(s). [0010]Further, in the abovementioned method, achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module specifically refers to that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module. [0011]Further, in the abovementioned method, said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network. [0012]Further, in the abovementioned method, said radio-frequency receiving module comprises a matching network. [0013]Further, in the abovementioned method, said radio-frequency front-end module comprises a duplexer and a matching network. [0014]In order to solve the abovementioned technical problem, the present invention also provides a mobile terminal, and the mobile terminal comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module, a radio-frequency front-end module and an antenna module, in which said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieve the multi frequency bands bonding pad compatibility respectively on a circuit board; and[0015]said mobile terminal further comprises a first connection selection module and a second connection selection module, in which one end of said first connection selection module is connected to a transmitting pin of a certain frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency transmitting module; one end of said second connection selection module is connected to a receiving pin of the frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency receiving module; and said radio-frequency front-end module is connected to said radio-frequency transmitting module and said radio-frequency receiving module. [0016]Further, said first selection module or said second selection module comprises at least two of resistors, capacitor(s) or inductor(s). [0017]Further, said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieving the multi frequency bands bonding pad compatibility respectively on a circuit board specifically refers to that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module. [0018]Further, said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network. [0019]Further, said radio-frequency receiving module comprises a matching network. [0020]Further, said radio-frequency front-end module comprises a duplexer and a matching network. [0021]In order to solve the abovementioned technical problem, the present invention also provides a mainboard for a mobile terminal, the mainboard comprises a signal transmitting/receiving module interface, a radio-frequency transmitting module interface, a radio-frequency receiving module interface and a radio-frequency front-end module interface, and said mainboard further comprises a first connection selection module interface and a second connection selection module interface, in which one end of said first connection selection module interface is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency transmitting module interface; one end of said second connection selection module is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency receiving module interface; and said radio-frequency front-end module interface connects said radio-frequency transmitting module interface and said radio-frequency receiving module interface. [0022]In this case, in the abovementioned method or mobile terminal, said mobile terminal may be a cell phone or a network card, etc. [0023]Since the technical solution disclosed by the present invention achieves the compatibility of multi frequency bands by using a single radio-frequency transmitting/receiving circuit, it can realize that one circuit board implements multi frequency bands in the miniaturization design of mobile terminals, which replaces the current multi circuit boards, so as to reduce the research and development costs and decrease the period of research and development and research personnel. BRIEF DESCRIPTION OF THE DRAWINGS [0024]FIG. 1 is a module schematic diagram in which a mobile terminal with double frequency bands is supported by two radio-frequency transmitting/receiving circuits according to the related art; [0025]FIG. 2 is a module schematic diagram of a mobile terminal with double frequency bands in an embodiment of the present invention; [0026]FIG. 3 is a module schematic diagram of a mobile terminal of CDMA 800M and CDMA 1900M in an embodiment of the present invention; [0027]FIG. 4 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N frequency bands in an embodiment of the present invention; [0028]FIG. 5 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N-M frequency bands in an embodiment of the present invention; and [0029]FIG. 6 is a module schematic diagram of a mobile terminal in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0030]In order to further describe the technical means adopted by the present invention to achieve the predetermined target and the effects thereof, the implementing method for matching the frequency bands of mobile terminals, the mobile terminal, and the mainboard thereof will be described in detail hereinbelow in conjunction with the accompanying drawings and the embodiments. [0031]FIG. 2 is a module schematic diagram of a mobile terminal with double frequency bands in an embodiment of the present invention, and as shown in FIG. 2, a double frequency bands signal transmitting/receiving module 101 fulfills the transmission and reception of the radio-frequency signals of the frequency band 1 and the frequency band 2, and a first connection selection module 102 and a second connection selection module 103 select the frequency band 1 or the frequency band 2 to be connected to a single radio-frequency transmitting/receiving circuit according to the requirement, and at the same time disconnect the signal with unnecessary frequency band from the single radio-frequency transmitting/receiving circuit. A radio-frequency transmitting module 104, a radio-frequency receiving module 105 and a radio-frequency front-end module 106 are compatible with the frequency band 1 and the frequency band 2 on the circuit board, therefore the modules with the corresponding frequency band can be bonded according to the practical requirement, and an antenna module 107 is selected to support the modules with the corresponding frequency band, so as to achieve that the single radio-frequency transmitting/receiving circuit supports the double frequency bands. In this embodiment, the single radio-frequency transmitting/receiving circuit specifically refers to the circuit composed of the radio-frequency transmitting module 104, the radio-frequency receiving module 105, the radio-frequency front-end module 106 and the antenna module 107. [0032]Specifically speaking, if the mobile terminal supporting the frequency band 1 is needed, the first connection selection module 102 connects the transmitting signal of the frequency band 1 in the double frequency bands signal transmitting/receiving module 101 to the single radio-frequency transmitting/receiving circuit, and disconnects the transmitting signal of the frequency band 2 in the double frequency bands signal transmitting/receiving module 101 from the single radio-frequency transmitting/receiving circuit; and the second connection selection module 103 connects the receiving signal of the frequency band 1 in the double frequency bands signal transmitting/receiving module 101 to the single radio-frequency transmitting/receiving circuit, and disconnects the receiving signal of the frequency band 2 in the double frequency bands signal transmitting/receiving module 101 from the single radio-frequency transmitting/receiving circuit. The radio-frequency transmitting module 104, the radio-frequency receiving module 105 and the radio-frequency front-end module 106 are all bonded with the modules corresponding to the frequency band 1, and are connected to the antenna module 107 supporting the frequency band 1, so as to fulfill the radio-frequency support for the frequency band 1. [0033]FIG. 3 is a module schematic diagram of a mobile terminal of CDMA 800M and CDMA 1900M in an embodiment of the present invention, and as shown in FIG. 3, the master chip 201 can fulfill the transmission and reception of the radio-frequency signals of CDMA 800M and CDMA 1900M. [0034]The first connection selection module 202 is composed of two capacitors, wherein one end of a capacitor A is connected to the transmitting pin of CDMA 800M of the master chip 201, one end of a capacitor B is connected to the transmitting pin of CDMA 1900M of the master chip 201, and the other ends of the capacitors A and B are connected with each other to join a radio-frequency transmitting path. [0035]The second connection selection module 203 is composed of four capacitors, and in this embodiment, since the receiving signals of CDMA 800M and CDMA 1900M are both differential signals, there are two signal lines for each receiving signal, wherein capacitors M and N respectively have one end which is respectively connected to one of the two differential receiving pins of CDMA 800M of the master chip 201, capacitors X and Y respectively have one end which is respectively connected to one of the two differential receiving pins of CDMA 1900M of the master chip 201, the other ends of the capacitors M and X are connected with each other to join the radio-frequency receiving path, and the other ends of the capacitors N and Y are connected with each other to join the radio-frequency receiving path. [0036]The radio-frequency transmitting module 204 comprises a radio-frequency power amplifier, a coupler and a matching network, etc., and appropriate devices are selected to make the bonding pad compatibility of the radio-frequency power amplifiers, the couplers and the matching networks of CDMA 800M and CDMA 1900M on the circuit board. [0037]The radio-frequency receiving module 205 comprises a matching network, etc., and appropriate devices are selected to make the bonding pad compatibility of the matching networks of CDMA 800M and CDMA 1900M on the circuit board;[0038]the radio-frequency front-end module 206 comprises a duplexer and a matching network, etc., and appropriate devices are selected to make the bonding pad compatibility of the duplexers and the matching networks of CDMA 800M and CDMA 1900M on the circuit board; and[0039]the antenna module 207 achieves the compatibility of the feed point on the circuit board. [0040]In this embodiment, if CDMA 800M needs to be supported, then the capacitor A is bonded in the first connection selection module 202, and the capacitor B is not bonded; the capacitors M and N are bonded in the second connection selection module 203, and the capacitors X and Y are not bonded; a radio-frequency power amplifier, coupler and matching network corresponding to CDMA 800M are bonded in the radio-frequency transmitting module 204; a matching network corresponding to CDMA 800M is bonded in the radio-frequency receiving module 205; a duplexer and matching network corresponding to CDMA 800M are bonded in the radio-frequency front-end module, and the antenna module 207 supporting CDMA 800M is further installed, so as to fulfill the support for CDMA 800M. The matching network refers to a circuit composed of capacitor(s), inductor(s) or resistor(s). [0041]If CDMA 1900M needs to be supported, then the capacitor B is bonded in the first connection selection module 202, and the capacitor A is not bonded; the capacitors X and Y are bonded in the second connection selection module 203, and the capacitors M and N are not bonded; a radio-frequency power amplifier, coupler and matching network corresponding to CDMA 1900M are bonded in the radio-frequency transmitting module 204; a matching network corresponding to CDMA 1900M is bonded in the radio-frequency receiving module 205; a duplexer and matching network corresponding to CDMA 1900M are bonded in the radio-frequency front-end module, and the antenna module 207 supporting CDMA 1900M is further installed, so as to fulfill the support for CDMA 1900M. [0042]FIG. 2 and FIG. 3 are mainly directed to the mobile terminal with double frequency bands. If it is a mobile terminal with multi frequency bands, there are many ways to use this method. FIG. 4 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N frequency bands in an embodiment of the present invention. In FIG. 4, a single radio-frequency transmitting/receiving circuit is used to be compatible with the N frequency bands. [0043]FIG. 5 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N-M frequency bands in an embodiment of the present invention. As shown in FIG. 5, among N frequency bands, there are the N-M frequency bands which a single radio-frequency transmitting/receiving circuit is compatible with, and each of the rest M frequency bands is supported by using one radio-frequency transmitting/receiving circuit. [0044]FIG. 6 is a module schematic diagram of a mobile terminal in an embodiment of the present invention. As shown in FIG. 6, the mobile terminal comprises a signal transmitting/receiving module 501, a first connection selection module 502, a second connection selection module 503, a radio-frequency transmitting module 504, a radio-frequency receiving module 505, a radio-frequency front-end module 506, and an antenna module 507 which are connected in sequence. [0045]In the embodiment of the present invention, the radio-frequency transmitting module 504, the radio-frequency receiving module 505 and the radio-frequency front-end module 506 respectively achieve the multi frequency bands bonding pad compatibility on the circuit board. Herein, the multi frequency bands bonding pad compatibility specifically refers to that the radio-frequency transmitting module 504, the radio-frequency receiving module 505 and the radio-frequency front-end module 506 can be compatible with the various frequency bands in the signal transmitting/receiving module 501 on the circuit board. One end of the first connection selection module 502 is connected to the transmitting pin of a certain frequency band in said signal transmitting/receiving module, and the other end thereof is connected to the radio-frequency transmitting module 504; one end of the second connection selection module 503 is connected to the receiving pin of the frequency band in said signal transmitting/receiving module, and the other end thereof is connected to the radio-frequency receiving module 505; and the radio-frequency front-end module 506 is connected to the radio-frequency transmitting module 504 and the radio-frequency receiving module 505. [0046]What are mentioned above are merely the preferred exemplary embodiments of the present invention, which are not intended to limit the present invention; and any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be covered in the protective scope of the present invention.(String), [0001] 本申请是国际申请 PCT/CN2009/075636 的延续,国际申请日期为 2009 年 12 月 16 日,该申请要求 2009 年 6 月 24 日提交的中国申请号 200910108393.7 的优先权,每份申请均通过引用并入。 技术领域 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端频段匹配的实现方法、移动终端及其主板。 背景技术 [0003] 现代通信技术的发展非常迅速。 不仅有全球移动通信系统(简称GSM)、码分多址(简称CDMA)、宽带码分多址(简称WCDMA)等多种制式,而且还有 同一个系统需要支持的多种频段,例如CDMA需要支持800M、1.9G、450M等,为了支持多频段,射频发射/接收电路需要对应每个频段 某些系统的移动终端在设计其电路时,必须增加频段的数量。 但是,对于特定的市场和特定的运营商,通常只使用特定的频段。 以CDMA为例,中国使用CDMA 800M,而印度尼西亚使用CDMA 1.9G。 [0004] 图1为现有技术中两个射频发射/接收电路支持双频段移动终端的模块示意图。 如图1所示,说明了现有的利用两个射频发射/接收电路来支持双频段移动终端的方法。 乐队的作用 1 通过一个支持频段的射频发射/接收电路实现 1 , 和乐队的功能 2 是通过其他支持该频段的射频发射/接收电路实现的 2 . 这种采用多个射频发射/接收电路实现多频段兼容的方法由于占用的电路板面积较大,在很多移动终端中无法实现。 目前,这是通过设计多个电路板的方法来解决的。 以CDMA为例,通常的做法是,针对CDMA 800M市场,设计一块电路板,上面只绑定CDMA 800M相关的射频发射/接收器件,相关的射频发射/接收器件 CDMA 1.9 G 未绑定; 而对于CDMA 1.9G市场,设计了一块电路板,只绑定了CDMA 1.9G相关的射频发射/接收器件,没有绑定CDMA 800M相关的射频发射/接收器件。 相应频段的电路器件根据具体的市场需求进行绑定。 这种方案导致移动终端中需要设计的电路板数量增加,从而提高了成本,延长了设计周期,需要更多的开发人员。 发明内容 [0005] 本发明所要解决的技术问题是提供一种移动终端频段匹配的实现方法、移动终端及其主板,以克服设计电路板数量多的不足。 移动端增加,成本提高,设计周期延长,需要更多的开发人员。 [0006] 为了解决上述技术问题,本发明提供了一种移动终端频段匹配的实现方法,该移动终端包括至少两个频段的信号发射/接收模块、射频发射模块、 射频接收模块和射频前端模块,所述移动终端还包括第一连接选择模块和第二连接选择模块,匹配移动终端频段的实现方法包括: [0007]射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容;[0008] 当所述移动终端需要工作在某个频段时,将所述第一连接选择模块的一端连接到所述信号发射/接收模块中该频段的发射引脚,将其另一端连接到所述射频发射 模块; 所述第二连接选择模块的一端与所述信号发射/接收模块中的频段接收引脚相连,另一端与所述射频接收模块相连; 将所述射频前端模块连接至所述射频发射模块和所述射频接收模块。 [0009]进一步地,在上述方法中,所述第一选择模块或所述第二选择模块包括电阻、电容或电感中的至少两者。 [0010] 进一步地,上述方法中,所述射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容,具体是指所述射频- 频率发射模块、射频接收模块和射频前端模块可以在电路板上兼容信号发射/接收模块中的各个频段。 [0011] 进一步地,在上述方法中,所述射频发射模块包括射频功率放大器、耦合器和匹配网络。 [0012] 进一步地,在上述方法中,所述射频接收模块包括匹配网络。 [0013] 进一步地,在上述方法中,所述射频前端模块包括双工器和匹配网络。 [0014] 为了解决上述技术问题,本发明还提供了一种移动终端,该移动终端包括具有至少两个频段的信号发射/接收模块、射频发射模块、射频接收模块, 射频前端模块和天线模块,其中所述射频发射模块、所述射频接收模块和所述射频前端模块分别在电路板上实现多频段焊盘兼容 ; 和 [0015] 所述移动终端还包括第一连接选择模块和第二连接选择模块,所述第一连接选择模块的一端连接所述信号发射/接收模块中某一频段的发射引脚,另一端 其连接至所述射频发射模块; 所述第二连接选择模块的一端连接所述信号发射/接收模块中频段的接收引脚,另一端连接所述射频接收模块。 射频前端模块连接射频发射模块和射频接收模块。 [0016] 进一步地,所述第一选择模块或所述第二选择模块包括电阻、电容或电感中的至少两者。 [0017] 进一步地,所述射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容,具体是指所述射频发射模块、所述无线电 -频率接收模块和所述射频前端模块可以在电路板上兼容所述信号发射/接收模块中的各个频段。 [0018] 进一步地,所述射频发射模块包括射频功率放大器、耦合器和匹配网络。 [0019] 进一步地,所述射频接收模块包括匹配网络。 [0020] 进一步地,所述射频前端模块包括双工器和匹配网络。 [0021] 为了解决上述技术问题,本发明还提供了一种移动终端主板,该主板包括信号发射/接收模块接口、射频发射模块接口、射频接收模块接口和无线电 -频率前端模块接口,所述主板还包括第一连接选择模块接口和第二连接选择模块接口,所述第一连接选择模块接口的一端用于选择性地连接所述信号传输中的管脚/ 接收模块接口,其另一端连接所述射频发射模块接口; 所述第二连接选择模块的一端用于选择性地连接所述信号发射/接收模块接口中的管脚,其另一端用于连接所述射频接收模块接口。 所述射频前端模块接口连接所述射频发射模块接口和所述射频接收模块接口。 [0022] 此时,上述方法或移动终端中,所述移动终端可以为手机或网卡等。 [0023]由于本发明所公开的技术方案通过单一的射频发射/接收电路实现了多频段的兼容,在移动终端的小型化设计中可以实现一块电路板实现多频段,取代 电流多电路板,从而降低研发成本,减少研发和研究人员的周期。 附图的简要说明 [0024] 图1为现有技术中两个射频发射/接收电路支持双频段移动终端的模块示意图; [0025] 图2为本发明实施例中双频段移动终端的模块示意图; [0026] 图3为本发明实施例中CDMA 800M和CDMA 1900M移动终端的模块示意图; [0027] 图4为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N个频段的模块示意图; [0028] 图5为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N-M频段的模块示意图; 和 [0029] 图6为本发明实施例移动终端的模块示意图。 具体实施方式 [0030] 为了进一步说明本发明为达到预定目标所采用的技术手段及其效果,下面对移动终端频段匹配的实现方法、移动终端及其主板进行详细说明。 结合附图和实施例。 [0031] 图2为本发明实施例中双频段移动终端的模块示意图,如图2所示,双频段信号发射/接收模块 101 完成该频段射频信号的发射和接收 1 和频段 2 ,以及第一连接选择模块 102 和第二连接选择模块 103 选择频段 1 或频段 2 根据需要连接到单个射频发射/接收电路,同时断开不需要频段的信号与单个射频发射/接收电路的连接。 一种射频发射模块 104 ,射频接收模块 105 和射频前端模块 106 兼容频段 1 和频段 2 在电路板上,因此可以根据实际需要粘合相应频段的模块,以及天线模块 107 选择支持相应频段的模块,从而实现单个射频发射/接收电路支持双频段。 在本实施例中,单个射频发射/接收电路具体是指由射频发射模块组成的电路。 104 ,射频接收模块 105 , 射频前端模块 106 和天线模块 107 . [0032] 具体来说,如果移动终端支持该频段 1 需要,第一个连接选择模块 102 连接频段的发射信号 1 双频段信号发射/接收模块 101 到单射频发射/接收电路,断开该频段的发射信号 2 双频段信号发射/接收模块 101来自单个射频发射/接收电路; 和第二个连接选择模块 103 连接频段的接收信号 1 双频段信号发射/接收模块 101 到单射频发射/接收电路,断开该频段的接收信号 2 双频段信号发射/接收模块 101 来自单个射频发射/接收电路。 射频发射模块 104 ,射频接收模块 105 和射频前端模块 106 均与频段对应的模块绑定 1 ,并连接到天线模块 107 支持频段 1 ,从而实现对频段的射频支持 1 . [0033] 图3为本发明实施例中CDMA 800M和CDMA 1900M移动终端的模块示意图,如图3所示 3 , 主控芯片 201 可以完成CDMA 800M和CDMA 1900M射频信号的发射和接收。 [0034] 第一连接选择模块 202 由两个电容组成,电容A的一端接主控芯片CDMA 800M的发射脚 201 ,电容B的一端接主控芯片CDMA 1900M的发射脚 201 ,电容A、B的另一端相互连接,加入射频发射通路。 [0035] 第二连接选择模块 203 由四个电容组成,在本实施例中,由于CDMA 800M和CDMA 1900M的接收信号都是差分信号,所以每个接收信号有两条信号线,其中电容M和N的一端分别连接到 主控芯片CDMA 800M的两个差分接收引脚之一 201 ,电容X和Y各有一端分别接主控芯片CDMA 1900M的两个差分接收管脚之一 201 ,电容M和X的另一端相互连接加入射频接收通路,电容N和Y的另一端相互连接加入射频接收通路。 [0036] 射频发射模块 204 包括射频功率放大器、耦合器和匹配网络等,选择合适的器件使CDMA 800M和CDMA 1900M射频功率放大器、耦合器和匹配网络的焊盘兼容 电路板。 [0037] 射频接收模块 205 包括匹配网络等,选择合适的器件使电路板上CDMA 800M和CDMA 1900M匹配网络的焊盘兼容; [0038]射频前端模块 206 包括双工器和匹配网络等,选择合适的器件使电路板上双工器和CDMA 800M、CDMA 1900M匹配网络的焊盘兼容。 和[0039]天线模块 207 实现电路板上馈电点的兼容性。 [0040] 本实施例中,如果需要支持CDMA 800M,则在第一连接选择模块中绑定电容A 202 ,且电容器 B 未绑定; 电容器M和N在第二连接选择模块中被绑定 203 ,并且电容器 X 和 Y 未绑定; 射频发射模块中绑定了CDMA 800M对应的射频功率放大器、耦合器和匹配网络 204 ; 射频接收模块绑定了CDMA 800M对应的匹配网络 205 ; 射频前端模块中绑定了CDMA 800M对应的双工器和匹配网络,天线模块 207 进一步安装支持CDMA 800M,完成对CDMA 800M的支持。 匹配网络是指由电容器、电感器或电阻器组成的电路。 [0041] 如果需要支持CDMA 1900M,则在第一连接选择模块中键合电容B 202 , 且电容器 A 未绑定; 电容器X和Y在第二个连接选择模块中被绑定 203, 电容 M 和 N 未绑定; 射频发射模块中绑定了CDMA 1900M对应的射频功率放大器、耦合器和匹配网络 204 ; 射频接收模块绑定了CDMA 1900M对应的匹配网络 205 ; 射频前端模块中绑定了CDMA 1900M对应的双工器和匹配网络,天线模块 207 进一步安装支持CDMA 1900M,完成对CDMA 1900M的支持。 [0042] 图2和图3主要针对双频段移动终端。 如果是多频段的移动终端,使用这种方法的方式有很多种。 图4为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N个频段的模块示意图。 在图4中,采用单个射频发射/接收电路来兼容N个频段。 [0043] 图5为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N-M频段的模块示意图。 如图5所示,在N个频段中,有N-M个频段是单个射频发射/接收电路兼容的,其余M个频段各由一个射频发射/接收电路支持 电路。 [0044] 图6为本发明实施例移动终端的模块示意图。 如图6所示,移动终端包括信号发射/接收模块 501 , 第一连接选择模块 502 , 第二连接选择模块 503 , 射频发射模块 504 ,射频接收模块 505 , 射频前端模块 506 , 和一个天线模块 507 它们是按顺序连接的。 [0045] 在本发明实施例中,射频发射模块 504 ,射频接收模块 505 和射频前端模块 506 分别实现电路板上的多频段焊盘兼容。 在此,多频段焊盘兼容性具体是指射频发射模块 504 ,射频接收模块 505 和射频前端模块 506 可兼容信号发射/接收模块中的各种频段 501 在电路板上。 第一连接选择模块一端 502 与所述信号发射/接收模块中某一频段的发射引脚相连,另一端与射频发射模块相连 504 ; 第二连接选择模块的一端 503 连接到所述信号发射/接收模块中的频段的接收引脚,其另一端连接到射频接收模块 505 ; 和射频前端模块 506 连接射频发射模块 504 射频接收模块 505 . [0046] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明; 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101604980A(String), CN101604980B(String), EP2448128A1(String), EP2448128A4(String), IN1865MUMNP2011A(String), US20110319037A1(String), WO2010148615A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101604980A(String), CN101604980B(String), EP2448128A1(String), EP2448128A4(String), IN1865MUMNP2011A(String), US20110319037A1(String), WO2010148615A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20110319037A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101604980A(String), CN101604980B(String), EP2448128A1(String), EP2448128A4(String), IN1865MUMNP2011A(String), US20110319037A1(String), WO2010148615A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), CN101604980A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), CN101604980B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), EP2448128A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), EP2448128A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), IN1865MUMNP2011A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), US20110319037A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270676(Integer), WO2010148615A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20110319037A1(String), US20110319037A1(String), 1325088000(Integer), 270676(Integer), 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), SHAO, YONGPING(String), WU, YAN(String), LIANG, PANFENG(String), GUO, SHUAI(String), WEI, HONGPO(String), LUO, YIBAO(String), 中兴通讯股份有限公司(String), SHAO YONGPING(String), WU YAN(String), LIANG PANFENG(String), GUO SHUAI(String), WEI HONGPO(String), LUO YIBAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184997(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184997(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHAO, YONGPING(String), SHAO YONGPING(String), 0(Integer), 1681975551(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: WU, YAN(String), WU YAN(String), 0(Integer), 1681975551(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIANG, PANFENG(String), LIANG PANFENG(String), 0(Integer), 1681975551(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUO, SHUAI(String), GUO SHUAI(String), 0(Integer), 1681975551(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: WEI, HONGPO(String), WEI HONGPO(String), 0(Integer), 1681975551(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LUO, YIBAO(String), LUO YIBAO(String), 0(Integer), 1681975551(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184997(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.678 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75939(Integer), 2(Integer), 184997(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75940(Integer), 2(Integer), 184997(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75941(Integer), 2(Integer), 184997(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75942(Integer), 2(Integer), 184997(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75943(Integer), 2(Integer), 184997(Integer), 4(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75944(Integer), 2(Integer), 184997(Integer), 5(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.741 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.742 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.742 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.744 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.744 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal for information security and information security method of mobile terminal(String), 用于信息安全的移动终端及移动终端的信息安全方法(String), US20100299757A1(String), A mobile terminal to secure information stored therein is provided. The mobile terminal may perform an algorithm to perform information security without remote control. The mobile terminal may detect a characteristic behavior pattern of a user of the mobile terminal, compare the characteristic behavior pattern with a behavior pattern of a current user, and thereby may determine whether a current user is an authorized user. Also, the mobile terminal may perform processing to protect data stored in the mobile terminal based on a result of the determination.(String), 提供了一种用于保护其中存储的信息的移动终端。 移动终端可以在没有远程控制的情况下执行算法来执行信息安全。 移动终端可以检测移动终端用户的特征行为模式,将特征行为模式与当前用户的行为模式进行比较,从而可以确定当前用户是否为授权用户。 此外,移动终端可以基于确定的结果来执行处理以保护存储在移动终端中的数据。(String), US12/706023(String), 1266249600(Integer), US20100299757A1(String), 1290614400(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030129964A1 | US20030185361A1 | US20040085909A1 | US20050262563A1 | US20060094401A1 | US20070236330A1 | US20080172715A1 | US20080189776A1 | US20090247122A1 | US20110016534A1 | US20110107421A1 | US7924989B1 | US8145561B1 | US8351408B2 | US8423785B2(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184998(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\39fb32db2f5f48c9b92e6f8a26097559.png(String), 184998(Integer), 39fb32db2f5f48c9b92e6f8a26097559.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal for information security and information security method of mobile terminal(String), 用于信息安全的移动终端及移动终端的信息安全方法(String), US20100299757A1(String), A mobile terminal to secure information stored therein is provided. The mobile terminal may perform an algorithm to perform information security without remote control. The mobile terminal may detect a characteristic behavior pattern of a user of the mobile terminal, compare the characteristic behavior pattern with a behavior pattern of a current user, and thereby may determine whether a current user is an authorized user. Also, the mobile terminal may perform processing to protect data stored in the mobile terminal based on a result of the determination.(String), 提供了一种用于保护其中存储的信息的移动终端。 移动终端可以在没有远程控制的情况下执行算法来执行信息安全。 移动终端可以检测移动终端用户的特征行为模式,将特征行为模式与当前用户的行为模式进行比较,从而可以确定当前用户是否为授权用户。 此外,移动终端可以基于确定的结果来执行处理以保护存储在移动终端中的数据。(String), US12/706023(String), 1266249600(Integer), US20100299757A1(String), 1290614400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030129964A1 | US20030185361A1 | US20040085909A1 | US20050262563A1 | US20060094401A1 | US20070236330A1 | US20080172715A1 | US20080189776A1 | US20090247122A1 | US20110016534A1 | US20110107421A1 | US7924989B1 | US8145561B1 | US8351408B2 | US8423785B2(String), \20230420\39fb32db2f5f48c9b92e6f8a26097559.png(String), 15(Integer), 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 1. An information security method in a mobile terminal, the information security method comprising:collecting data associated with a characteristic behavior pattern of a user of the mobile terminal;comparing the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period; andperforming processing to protect data stored in the mobile terminal based on a result of the comparison.(String), 1.一种移动终端中的信息安全方法,信息安全方法包括:收集与移动终端用户的特征行为模式相关联的数据;将特征行为模式与用户针对移动终端的行为模式进行比较,该行为模式是在特定时间段内被监控的;和基于比较的结果执行保护存储在移动终端中的数据的处理。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 2. The information security method of claim 1, wherein the performing comprises:hiding or deleting the data stored in the mobile terminal.(String), 2.如权利要求1所述的信息安全方法,其中表演包括:隐藏或删除移动终端中存储的数据。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 3. The information security method of claim 1, wherein the performing comprises:transmitting a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal.(String), 3.如权利要求1所述的信息安全方法,其中表演包括:向移动终端外部发送与移动终端的当前状态或当前位置相关联的通知消息。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 4. The information security method of claim 1, wherein the collecting collects the data associated with the characteristic behavior pattern of the user to update the characteristic behavior pattern.(String), 4.如权利要求1所述的信息安全方法,其中收集收集与用户的特征行为模式相关联的数据,以更新特征行为模式。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 5. The information security method of claim 1, further comprising:detecting the characteristic behavior pattern of the user based on the collected data.(String), 5.如权利要求1所述的信息安全方法,还包括:根据收集到的数据检测用户的特征行为模式。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 6. The information security method of claim 1, further comprising:monitoring the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period.(String), 6.如权利要求1所述的信息安全方法,还包括:实时监控移动终端,检测用户在特定时间段内针对移动终端的行为模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 7. The information security method of claim 1, wherein the comparing compares a value corresponding to the characteristic behavior pattern of the user with a value corresponding to the behavior pattern of the user to compare the characteristic behavior pattern with the behavior pattern of the user.(String), 7.如权利要求1所述的信息安全方法,其中比较是将用户的特征行为模式对应的值与用户的行为模式对应的值进行比较,以将特征行为模式与用户的行为模式进行比较。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 8. The information security method of claim 1, wherein the performing performs processing to protect data, which is requested to be protected in advance, from among the data stored in the mobile terminal.(String), 8.如权利要求1所述的信息安全方法,其中执行部执行处理以保护移动终端中存储的数据中预先请求保护的数据。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 9. The information security method of claim 1, wherein the characteristic behavior pattern of the user includes a characteristic usage pattern of the user with respect to the mobile terminal or a characteristic change pattern of an environment of the mobile terminal.(String), 9.如权利要求1所述的信息安全方法,其中用户的特征行为模式包括用户对移动终端的特征使用模式或移动终端环境的特征变化模式。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 10. The information security method of claim 1, wherein the characteristic behavior pattern of the user includes a characteristic usage pattern of the user with respect to the mobile terminal, and the characteristic usage pattern is detected based on at least one of details of calls of the user, a history of access to the Internet, a history of sending and/or receiving a text message, keystroke information, and a history of application uses.(String), 10.如权利要求1所述的信息安全方法,其中用户特征行为模式包括用户对移动终端的特征使用模式,特征使用模式是基于用户通话详情、上网历史中的至少一项检测的,发送和/或接收文本消息的历史记录、击键信息以及应用程序使用的历史记录。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 11. The information security method of claim 1, wherein the characteristic behavior pattern of the user includes a characteristic change pattern of an environment of the mobile terminal, and the characteristic change pattern is detected based on at least one of a moving route of the mobile terminal, information about the environment of the mobile terminal, and biological information of the user.(String), 11.如权利要求1所述的信息安全方法,其中用户的特征行为模式包括移动终端环境的特征变化模式,该特征变化模式是基于移动终端的移动路线、移动终端的环境信息中的至少一种检测的,和用户的生物信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 12. A computer-readable storage medium to store a program to implement an information security method in a mobile terminal, comprising instructions causing a computer to:collect data associated with a characteristic behavior pattern of a user of the mobile terminal;compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period; andperform processing to protect data stored in the mobile terminal based on a result of the comparison.(String), 12.一种计算机可读存储介质,用于存储在移动终端中实现信息安全方法的程序,包括导致计算机执行以下操作的指令:收集与移动终端用户的特征行为模式相关联的数据;将特征行为模式与用户针对移动终端的行为模式进行比较,该行为模式是在特定时间段内被监控的;和基于比较的结果执行保护存储在移动终端中的数据的处理。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 13. A mobile terminal to secure information stored therein, the mobile terminal comprising:a database to collect data associated with a characteristic behavior pattern of a user of the mobile terminal;a monitoring unit to detect the characteristic behavior pattern of the user using the database;a pattern comparison/reasoning unit to compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period; anda post-processing unit to perform processing to protect data stored in the mobile terminal based on a result of the comparison.(String), 13.一种用于保护存储在其中的信息的移动终端,该移动终端包括:数据库,用于收集与移动终端用户的特征行为模式相关联的数据;监测单元使用数据库检测用户的特征行为模式;模式比较/推理单元,将特征行为模式与用户针对移动终端的行为模式进行比较,该行为模式在特定时间段内被监控;和后处理单元基于比较的结果执行处理以保护存储在移动终端中的数据。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 14. The mobile terminal of claim 13, wherein the post-processing unit comprises at least one of a data management unit to hide or delete the data stored in the mobile terminal, and an urgent communication unit to transmit a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal.(String), 14.如权利要求13所述的移动终端,其中后处理单元包括隐藏或删除存储在移动终端中的数据的数据管理单元和发送与移动终端的当前状态或当前位置相关联的通知消息的紧急通信单元中的至少一个,到移动终端的外部。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184998(Integer), 15. The mobile terminal of claim 13, wherein the monitoring unit monitors the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period.(String), 15.如权利要求13所述的移动终端,其中监控单元实时监控移动终端,检测用户在特定时间段内针对移动终端的行为模式。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184998(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean Patent Application No. 10-2009-0044372, filed on May 21, 2009, in the Korean Intellectual Property Office, the entire disclosure of which is incorporated herein by reference for all purposes. BACKGROUND [0002]1. Field [0003]The following description relates to a technology to protect information stored in a terminal, and more particularly, to a technology to protect information stored in a mobile terminal in the event of an emergency such as loss or theft of the mobile terminal. [0004]2. Description of the Related Art [0005]Currently, various mobile terminals such as a cellular phone, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), and the like are widely used. A user may store various types of data or information in a mobile terminal. For example, a user may store photos, music files, data of a telephone book, text messages, etc., in a cellular phone. [0006]When a user loses the mobile terminal or has it stolen, the user's privacy may be compromised if confidential information was stored thereon. Furthermore, where information stored in a mobile terminal is used by a company or a government employee, a significant amount of damage may be caused if the otherwise secure information is available to an unauthorized user. [0007]In response to this issue, a variety of methods to protect information stored in a mobile terminal have been attempted. For example, security technologies include functions to activate a mobile terminal only when a password is input, technologies to remotely control a lost or stolen mobile terminal to protect information stored in the mobile terminal, etc. However, a mobile terminal having the above technologies may be operated manually and by an unauthorized user if the unauthorized user has access to the true mobile terminal owner's password. Accordingly, such technologies may not effectively protect information stored in a mobile terminal where a user does not know that the mobile terminal has been lost or stolen. SUMMARY [0008]In one general aspect, there is provided an information security method in a mobile terminal, the information security method includes collecting data associated with a characteristic behavior pattern of a user of the mobile terminal, comparing the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period, and performing processing to protect data stored in the mobile terminal based on a result of the comparison. [0009]The performing may include hiding or deleting the data stored in the mobile terminal, or transmitting a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal. [0010]The collecting may collect the data associated with the characteristic behavior pattern of the user to update the characteristic behavior pattern. [0011]The information security method may further include detecting the characteristic behavior pattern of the user based on the collected data. [0012]The information security method may further include monitoring the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period. [0013]The comparing may compare a value corresponding to the characteristic behavior pattern of the user with a value corresponding to the behavior pattern of the user to compare the characteristic behavior pattern with the behavior pattern of the user. [0014]The performing may perform processing to protect data, which is requested to be protected in advance, from among the data stored in the mobile terminal. [0015]The characteristic behavior pattern of the user may include a characteristic usage pattern of the user with respect to the mobile terminal or a characteristic environmental change pattern around the mobile terminal. [0016]The characteristic behavior pattern of the user may include a characteristic usage pattern of the user with respect to the mobile terminal, and the characteristic usage pattern may be detected based on details of calls of the user, a history of access to the Internet, a history of sending/receiving a text message, keystroke information, and a history of application uses. [0017]The characteristic behavior pattern of the user includes a characteristic environmental pattern of the user with respect to the mobile terminal, and the characteristic environmental change pattern may be detected based on at least one of a moving route of the mobile terminal, information about the environment of the mobile terminal, and biological information of the user. [0018]In another general aspect, there is provided a computer-readable storage medium to store a program to implement an information security method in a mobile terminal, comprising instructions causing a computer to collect data associated with a characteristic behavior pattern of a user of the mobile terminal, compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period, and perform processing to protect data stored in the mobile terminal based on a result of the comparison. [0019]In another general aspect, there is provided a mobile terminal to secure information stored therein, the mobile terminal includes a database to collect data associated with a characteristic behavior pattern of a user of the mobile terminal, a monitoring unit to detect the characteristic behavior pattern of the user using the database, a pattern comparison/reasoning unit to compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period, and a post-processing unit to perform processing to protect data stored in the mobile terminal based on a result of the comparison. [0020]The post-processing unit may include at least one of a data management unit to hide or delete the data stored in the mobile terminal, and an urgent communication unit to transmit a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal. [0021]The monitoring unit may monitor the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period. [0022]Other features and aspects will be apparent from the following detailed description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0023]FIG. 1 is a diagram illustrating examples of a mobile terminal and various types of data stored in the mobile terminal. [0024]FIG. 2 is a diagram illustrating an example of a mobile terminal to detect a characteristic behavior pattern of a user and to check whether a current user is an authorized user using the detected characteristic behavior pattern in real time. [0025]FIG. 3 is a flowchart illustrating an example of an information security method. [0026]FIG. 4 is a diagram illustrating an example of data used during detection of a characteristic behavior pattern. [0027]FIG. 5 is a block diagram illustrating a configuration of an example of a mobile terminal. [0028]Throughout the drawings and the detailed description, unless otherwise described, the same drawing reference numerals will be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience. DETAILED DESCRIPTION [0029]The following detailed description is provided to assist the reader in gaining a comprehensive understanding of the media, apparatuses, methods and/or systems described herein. Accordingly, various changes, modifications, and equivalents of the systems, methods, apparatuses and/or media described herein will be suggested to those of ordinary skill in the art. Also, descriptions of well-known functions and constructions may be omitted for increased clarity and conciseness. [0030]FIG. 1 illustrates examples of a mobile terminal and various types of data stored in the mobile terminal. [0031]Referring to FIG. 1, various types of data may be stored in the mobile terminal, which may include various types of devices such as a cellular phone, a notebook computer (i.e. laptop), and the like. For example, as illustrated in FIG. 1, private information such as text messages, photo and video files, phone book, and the like, may be stored in the cellular phone. Also, emails, various documents, photos, and the like may be stored in the notebook computer. [0032]If the information stored in the mobile terminal is easily revealed and unsecure, a user's private information may be compromised thereby resulting in potentially substantial financial damage. In particular, if the user's mobile terminal is stolen, the user loses control the mobile terminal and all of the information stored thereupon. Furthermore, conventional methods of password-protecting mobile terminals may be difficult, inconvenient, and cumbersome. [0033]A user's mobile terminal usage behavior such as calling, sending and/or receiving text messages, movement, and application uses, may have a particular pattern. For example, the user of the mobile terminal generally moves along a particular moving route, talks on the mobile terminal with a particular caller and a particular receiver, and uses particular applications from among a plurality of applications installed in the mobile terminal. A characteristic behavior pattern of the user may be detected from the above-described behavior patterns of the user. [0034]Accordingly, the mobile terminal may actively ascertain a loss or theft of the mobile terminal using the detected user's characteristic behavior pattern, without remote control. For example, where a behavior of a current user is significantly different from the characteristic behavior pattern of the user, the mobile terminal may determine that the current user is an unauthorized user, and recognize that the mobile terminal is lost or stolen. An operation of actively and intelligently recognizing the loss or theft is described in detail below. [0035]FIG. 2 illustrates an example of a mobile terminal 210 to detect a characteristic behavior pattern of a user 220 and to check whether a current user is an authorized user using the detected characteristic behavior pattern in real time. [0036]Referring to FIG. 2, the mobile terminal 210 may recognize the characteristic behavior pattern of the user 220 from among various behaviors of the user 220. Accordingly, the characteristic behavior pattern of the user 220 may be classified into a characteristic usage pattern of the user 220 and a characteristic change pattern of an environment of the mobile terminal 210. [0037]The characteristic behavior pattern of the user 220 may be detected based on details regarding calls the user 220 has made and/or received, a history of access to the Internet, a history of sending and/or receiving text messages, keystroke information, and a history of application uses. The details of the calls of the user 220 may include information about a caller, information about a receiver, a time of making the calls, a time of receiving the calls, and a call duration. The history of sending and/or receiving the text messages may include information about a caller, information about a receiver, a size of the text message, a time of sending, a time of receiving, and the like. Also, the keystroke information of the user 220 may include information about a strength and/or speed of the manner in which keys were input. The history of application uses may include information about a type and/or time of use of a particular application which is installed in the mobile terminal 210. [0038]Also, the characteristic change pattern of the environment of the mobile terminal 210 may be influenced by external factors. That is, the characteristic change pattern of the environment of the mobile terminal 210 may be detected based on at least one of a moving route of the mobile terminal 210, information about the environment of the mobile terminal 210, and biological information of the user 220. More specifically, the information about the environment may include a brightness of a location of the mobile terminal 210, a humidity level of the location of the mobile terminal 210, a noise level of the location of the mobile terminal 210, etc., and the biological information may include a body temperature of the user, etc. [0039]The mobile terminal 210 may check whether the current user is the authorized user 220 in real time, after detecting the characteristic behavior pattern of the user 220 from the behaviors of the user 220. That is, the mobile terminal 210 may determine whether a behavior pattern, detected from the behavior of the current user, is similar to the characteristic behavior pattern of the user 220, and thereby may check whether the current user is the authorized user 220. As a similarity between the detected behavior pattern of the current user and the characteristic behavior pattern of the user 220 decreases, a probability that the current user may be an unauthorized user increases. [0040]Where the current user is an unauthorized user, the mobile terminal 210 may actively hide or delete data in order to protect the mobile terminal 210's true owner (i.e., the user 220 as illustrated in FIG. 2). In this instance, the data actively hidden or deleted may be set by the user 220 in advance. [0041]Also, the mobile terminal 210 may report the loss or theft of the mobile terminal 210 and transmit a notification message to a location outside of the mobile terminal 210, such as a serving base station. The notification message may include a current location of the mobile terminal 210. [0042]FIG. 3 illustrates an example of an information security method. [0043]The information security method may be actively and intelligently performed. [0044]Referring to FIG. 3, at 310, the information security method may identify data, which is requested to be protected by a user, from among data stored in a mobile terminal. In this instance, the user may request data associated with privacy, valuable data, and the like, to be protected in advance. [0045]At 320, the information security method may set an operation mode corresponding to a loss or theft of the mobile terminal according to a user setting. For example, if the mobile terminal is lost or stolen, the user may desire a mode of hiding or deleting the data to be protected, and select a mode of transmitting a notification message. [0046]At 330, the information security method may collect data associated with a characteristic behavior pattern of the user of the mobile terminal. In this instance, the mobile terminal may continuously collect details of calls of the user, a history of access to the Internet, a history of sending and/or receiving text messages, keystroke information, and a history of application uses. Accordingly, the application may be installed in the mobile terminal. Also, the mobile terminal may collect at least one of information about a moving route of the mobile terminal, information about an environment of the mobile terminal, and biological information of the user. The information about the environment may include a brightness of a location of the mobile terminal, a humidity level of the location of the mobile terminal, a noise level of the location of the mobile terminal, and, and the biological information may include a body temperature of the user, etc. [0047]At 340, the information security method may detect the characteristic behavior pattern of the user based on the collected data. In this instance, a variety of well-known data analysis schemes may be applied, and the characteristic behavior pattern may be expressed numerically or in a table or a graph. [0048]At 350, the information security method may collect data to detect a current behavior pattern of a user of the mobile terminal in real time. [0049]At 360, the information security method may compare the characteristic behavior pattern, detected at 340, with the behavior pattern, detected at 350. [0050]At 370, the information security method may determine whether the current user is an authorized user or whether the mobile terminal is lost or stolen, based on a result of the comparison at 360. [0051]That is, where the behavior pattern, detected at 350, is significantly different from the characteristic behavior pattern, detected at 340, the information security method may determine that the current user is an unauthorized user. Conversely, where the behavior pattern, detected at 350, is significantly similar to the characteristic behavior pattern, detected at 340, the information security method may determine that the current user is an authorized user. [0052]Where the current user is in fact the authorized user, the information security method may return to 330. However, where the current user is the unauthorized user, the information security method may perform at least one of transmitting data (at 382) and deleting or hiding data (at 381). [0053]At 381, the information security method may hide or delete the data to be protected. At 382, the information security method may transmit the notification message to an outside location of the mobile terminal. [0054]FIG. 4 illustrates an example of data used during detection of a characteristic behavior pattern. [0055]The examples of data to be protected and an operation mode are illustrated in FIG. 4. That is, a user may determine an image file, received from a girlfriend (for example), as the data to be protected. Also, the data to be protected may be set by the user, and the user may set a mode of hiding the data to be protected and a mode of transmitting a notification message in an event of loss or theft of the mobile terminal, as the operation mode. [0056]The user may behave according to the characteristic behavior pattern as illustrated in FIG. 4. That is, the user may send and/or receive an image file from and/or to the girlfriend between 12:00 and 13:00, and perform a video call with the girlfriend between 23:00 and 01:00. Also, the user usually moves along a route of home—school—home on weekdays, and along a route of home—training center—girlfriend's house—home on weekends. The above-described behaviors may be automatically monitored by the mobile terminal, and the mobile terminal may detect the characteristic behavior pattern using data associated with the collected behaviors of the user. Accordingly, the characteristic behavior pattern may be expressed in various ways such as a table, a numerical value, a graph, and the like. [0057]For example, it may be assumed that the user lost the mobile terminal in a bus while going to school on Wednesday morning, and the user does not realize it. Accordingly, the mobile terminal lost on the bus may continuously monitor a behavior pattern of a user of the mobile terminal. [0058]Hence, the mobile terminal moves along a route of the bus, and the user does not send and/or receive an image file between 12:00 and 13:00, and a monitored noise around the mobile terminal may be higher than usual. [0059]In this instance, the mobile terminal may determine that the current situation around the mobile terminal is different from typical patterns by means of the characteristic behavior pattern based on the collected data. In particular, the mobile terminal may compare a value corresponding to the characteristic behavior pattern with a value corresponding to the current situation around the mobile terminal, and apply a result of the comparison to a particular rule, and thereby may determine that the current situation around the mobile terminal is different from the characteristic behavior pattern. [0060]As a result, the mobile terminal may hide the image file received from the girlfriend, which is the data to be protected, and transmit the notification message. Accordingly, although the user may not recognize the loss or theft of the mobile terminal, the data will be protected. Also, the data may be efficiently protected even when a communication of the mobile terminal is unavailable, since remote control is not required. [0061]FIG. 5 illustrates a configuration of an example of a mobile terminal. [0062]Referring to FIG. 5, the mobile terminal includes a user setting management unit 510, a database 520, a pattern comparison/reasoning unit 530, a monitoring unit 540, an internal sensor 550, an external sensor 560, and a post-processing unit 570. [0063]The user setting management unit 510 may manage a user setting with respect to data to be protected, and an operation mode if the mobile terminal is lost or stolen. The data to be protected may be requested by a user. [0064]The database 520 may store the characteristic behavior pattern of the user based on the collected data associated with a characteristic behavior pattern of a user of the mobile terminal. This behavior pattern is provided from the monitoring unit 540. In this instance, the database 520 may update the characteristic behavior pattern. [0065]Also, the pattern comparison/reasoning unit 530 may compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal. The behavior pattern may be monitored in a particular time period. Also, the pattern comparison/reasoning unit 530 may apply a result of the comparison to a particular rule, and thereby may identify a current state of the mobile terminal. [0066]Also, the monitoring unit 540 may monitor data, provided from the internal sensor 550 and the external sensor 560, in real time and detect the behavior pattern of the user with respect to the mobile terminal based on the data. Also, the monitoring unit 540 may provide the detected behavior pattern to the database 520 and the pattern comparison/reasoning unit 530. Accordingly, the internal sensor 550 may provide, to the monitoring unit 540, details of calls of the user, a history of access to the Internet, a history of sending/receiving text messages, keystroke information, and a history of application uses in real time. Also, the external sensor 560 may provide, to the monitoring unit 540, a moving route of the mobile terminal, information about an environment of the mobile terminal, and biological information of the user. [0067]The post-processing unit 570 includes a data management unit 571 and an urgent communication unit 572. In this instance, the data management unit 571 may hide or delete the data stored in the mobile terminal based on the user setting, and the urgent communication unit 572 may transmit a notification message, associated with a current state or a current location of the mobile terminal, to a location outside of the mobile terminal. [0068]Since the descriptions described with reference to FIGS. 1 through 4 may be applied to the above-described units illustrated in FIG. 5, further detailed descriptions will be omitted herein. [0069]The processes, functions, methods and/or software described above may be recorded, stored, or fixed in one or more computer-readable storage media that includes program instructions to be implemented by a computer to cause a processor to execute or perform the program instructions. The media may also include, alone or in combination with the program instructions, data files, data structures, and the like. The media and program instructions may be those specially designed and constructed, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable media include magnetic media, such as hard disks, floppy disks, and magnetic tape; optical media such as CD ROM disks and DVDs; magneto-optical media, such as optical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory (ROM), random access memory (RAM), flash memory, and the like. Examples of program instructions include machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter. The described hardware devices may be configured to act as one or more software modules in order to perform the operations and methods described above, or vice versa. In addition, a computer-readable storage medium may be distributed among computer systems connected through a network and computer-readable codes or program instructions may be stored and executed in a decentralized manner. [0070]As described above with reference to the figures, a mobile terminal may actively or intelligently determine whether the mobile terminal is lost or stolen, or whether a current user is an authorized user, and thereby may efficiently protect information, stored in the mobile terminal, even when the user does not recognize the loss or theft. [0071]Also as described above with reference to the figures, a mobile terminal may compare a characteristic behavior pattern of a user with a current behavior pattern, and thereby may accurately determine whether the mobile terminal is lost or stolen or whether a current user is an authorized user. [0072]Further as described above with reference to the figures, a mobile terminal may actively or intelligently determine whether the mobile terminal is lost or stolen, or whether a current user is an authorized user, and thereby may economically protect information, stored in the mobile terminal, without a separate hardware for remote control. [0073]A number of examples have been described above. Nevertheless, it will be understood that various modifications may be made. For example, suitable results may be achieved if the described techniques are performed in a different order and/or if components in a described system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components or their equivalents. Accordingly, other implementations are within the scope of the following claims.(String), 相关申请的交叉引用 [0001] 此申请根据 35 U.S.C. 2009 年 5 月 21 日向韩国知识产权局提交的第 10-2009-0044372 号韩国专利申请的§119(a),其全部公开内容通过引用并入本文用于所有目的。 背景 [0002] 1. 领域 [0003] 以下描述涉及保护存储在终端中的信息的技术,更具体地,涉及在紧急情况例如移动终端丢失或被盗的情况下保护存储在移动终端中的信息的技术。 [0004] 2.相关技术的描述 [0005] 目前,各种移动终端如蜂窝电话、个人数字助理(PDA)、便携式多媒体播放器(PMP)等被广泛使用。 用户可以在移动终端中存储各种类型的数据或信息。 例如,用户可以将照片、音乐文件、电话簿数据、文本消息等存储在蜂窝电话中。 [0006] 当用户丢失或被盗移动终端时,如果在其上存储机密信息,用户的隐私可能会受到损害。 此外,在存储在移动终端中的信息被公司或政府雇员使用的情况下,如果未经授权的用户可以使用原本安全的信息,则可能造成大量损害。 [0007] 针对这个问题,已经尝试了多种方法来保护存储在移动终端中的信息。 例如,安全技术包括仅在输入密码时激活移动终端的功能,远程控制丢失或被盗的移动终端以保护移动终端中存储的信息的技术等。但是,具有上述技术的移动终端可以 如果未经授权的用户可以访问真正的移动终端所有者的密码,则由未经授权的用户手动操作。 因此,在用户不知道移动终端丢失或被盗的情况下,这样的技术可能无法有效地保护存储在移动终端中的信息。 概括 [0008] 在一个一般方面,提供了一种移动终端中的信息安全方法,该信息安全方法包括收集与移动终端的用户的特征行为模式相关联的数据,将特征行为模式与用户的行为模式进行比较 对于移动终端,在特定时间段内监测行为模式,并根据比较结果进行处理以保护移动终端中存储的数据。 [0009] 该执行可以包括隐藏或删除存储在移动终端中的数据,或者将与移动终端的当前状态或当前位置相关联的通知消息发送到移动终端的外部。 [0010] 收集可以收集与用户的特征行为模式相关联的数据以更新特征行为模式。 [0011] 信息安全方法还可以包括基于收集的数据检测用户的特征行为模式。 [0012] 所述信息安全方法还可以包括对所述移动终端进行实时监控,以检测用户对所述移动终端的行为模式,所述用户的行为模式在特定时间段内被监测。 [0013] 比较可以将与用户的特征行为模式对应的值与与用户的行为模式对应的值进行比较,以将特征行为模式与用户的行为模式进行比较。 [0014] 执行可以执行处理以保护存储在移动终端中的数据之中的被预先请求保护的数据。 [0015] 用户的特征行为模式可以包括用户对移动终端的特征使用模式或移动终端周围的特征环境变化模式。 [0016]用户的特征行为模式可以包括用户对移动终端的特征使用模式,该特征使用模式可以基于用户的通话细节、上网历史、上网历史等来检测。 发送/接收文本消息、击键信息和应用程序使用历史。 [0017] 用户的特征行为模式包括用户相对于移动终端的特征环境模式,可以基于移动终端的移动路线、环境信息中的至少一种来检测特征环境变化模式。 移动终端,以及用户的生物信息。 [0018] 在另一个一般方面,提供了一种计算机可读存储介质,用于存储在移动终端中实现信息安全方法的程序,包括使计算机收集与移动终端用户的特征行为模式相关联的数据的指令 ,将特征行为模式与用户对移动终端的行为模式进行比较,该行为模式在特定时间段内被监控,并根据比较结果进行处理以保护移动终端中存储的数据。 [0019] 在另一个一般方面,提供了一种用于保护其中存储的信息的移动终端,该移动终端包括用于收集与该移动终端的用户的特征行为模式相关联的数据的数据库、用于检测用户的特征行为模式的监控单元。 用户使用数据库,模式比较/推理单元将特征行为模式与用户相对于移动终端的行为模式进行比较,在特定时间段内被监控的行为模式,以及后处理单元,用于 根据比较结果,进行处理以保护移动终端中存储的数据。 [0020] 后处理单元可以包括至少一个数据管理单元,用于隐藏或删除存储在移动终端中的数据,以及紧急通信单元,用于发送与移动设备的当前状态或当前位置相关联的通知消息。 终端,到移动终端的外部。 [0021] 监控单元可以对移动终端进行实时监控,以检测用户对移动终端的行为模式,该用户的行为模式在特定时间段内被监控。 [0022] 从以下详细描述、附图和权利要求中,其他特征和方面将是显而易见的。 附图的简要说明 [0023] 如图。 附图说明图1是图示移动终端和存储在移动终端中的各种类型的数据的示例的图。 [0024] 如图。 图2是示出移动终端检测用户的特征行为模式并使用检测到的特征行为模式实时检查当前用户是否是授权用户的示例的图。 [0025] 如图。 图3是表示信息安全方法的一个例子的流程图。 [0026] 如图。 图4是表示特征行为模式的检测时使用的数据的一例的图。 [0027] 如图。 图5是图示移动终端的示例的配置的框图。 [0028] 在整个附图和详细描述中,除非另有说明,否则相同的附图标记将被理解为指代相同的元件、特征和结构。 为了清楚、说明和方便起见,这些元素的相对大小和描述可能会被夸大。 详细说明 [0029]提供以下详细描述以帮助读者获得对本文描述的媒体、装置、方法和/或系统的全面理解。 因此,本文所述的系统、方法、装置和/或媒体的各种改变、修改和等效物将被建议给本领域普通技术人员。 此外,为了更清楚和简明,可以省略对众所周知的功能和结构的描述。 [0030] 如图。 图1图示了移动终端和存储在移动终端中的各种类型的数据的示例。 [0031] 参考图。 参照图1,移动终端中可以存储各种类型的数据,移动终端可以包括各种类型的设备,例如蜂窝电话、笔记本电脑(即膝上型电脑)等。 例如,如图所示。 如图1所示,诸如文本消息、照片和视频文件、电话簿等的私人信息可以存储在蜂窝电话中。 此外,电子邮件、各种文档、照片等可以存储在笔记本计算机中。 [0032] 如果存储在移动终端中的信息容易泄露且不安全,则用户的私人信息可能会受到损害,从而导致潜在的重大经济损失。 特别是,如果用户的移动终端被盗,用户将失去对移动终端的控制以及其上存储的所有信息。 此外,传统的密码保护移动终端的方法可能是困难的、不方便的和麻烦的。 [0033] 用户的移动终端使用行为,例如呼叫、发送和/或接收文本消息、移动和应用程序使用,可能具有特定的模式。 例如,移动终端的用户通常沿着特定的移动路线移动,在移动终端上与特定的呼叫者和特定的接收者通话,并使用安装在移动终端中的多个应用程序中的特定应用程序。 可以从上述用户的行为模式中检测出用户的特征行为模式。 [0034] 因此,移动终端可以使用检测到的用户的特征行为模式来主动确定移动终端的丢失或被盗,而无需远程控制。 例如,在当前用户的行为与用户的特征行为模式显着不同的情况下,移动终端可以确定当前用户是未经授权的用户,并识别出移动终端丢失或被盗。 下面详细介绍主动智能识别丢失或被盗的操作。 [0035] 如图。 图2图示了移动终端的示例 210 检测用户的特征行为模式 220 使用检测到的特征行为模式实时检查当前用户是否为授权用户。 [0036] 参考图。 2、移动端 210 可以识别用户的特征行为模式 220 从用户的各种行为中 220 . 相应地,用户的特征行为模式 220 可以分类为用户的特征使用模式 220 以及移动终端环境的特征变化模式 210 . [0037] 用户的特征行为模式 220 可以根据有关用户呼叫的详细信息进行检测 220 已制作和/或接收到互联网访问历史、发送和/或接收文本消息的历史、击键信息和应用程序使用历史。 用户通话详情 220 可以包括关于呼叫者的信息、关于接收者的信息、进行呼叫的时间、接收呼叫的时间和呼叫时长。 发送和/或接收文本消息的历史可以包括关于呼叫者的信息、关于接收者的信息、文本消息的大小、发送时间、接收时间等。 还有用户的按键信息 220“输入键”可以包括关于输入键的方式的强度和/或速度的信息。 应用程序使用历史可以包括关于安装在移动终端中的特定应用程序的类型和/或使用时间的信息 210 . [0038] 此外,移动终端环境的特征变化模式 210 可能会受到外部因素的影响。 即移动终端环境的特征变化模式 210 可以基于移动终端的移动路线中的至少一个来检测 210 , 移动终端的环境信息 210 ,以及用户的生物信息 220 . 更具体地,关于环境的信息可以包括移动终端的位置的亮度 210 , 移动终端所在位置的湿度等级 210 , 移动终端位置的噪声级 210 等,并且生物信息可以包括用户的体温等。 [0039] 移动终端 210 可以检查当前用户是否是授权用户 220 实时检测用户的特征行为模式后 220 从用户的行为 220 . 也就是移动终端 210 可以确定从当前用户的行为中检测到的行为模式是否与用户的特征行为模式相似 220 ,从而可以检查当前用户是否是授权用户 220 . 作为检测到的当前用户的行为模式与用户的特征行为模式之间的相似度 220 减少,当前用户可能是未授权用户的概率增加。 [0040] 当前用户为非法用户时,移动终端 210 可能会主动隐藏或删除数据以保护移动终端 210 的真正所有者(即用户 220 如图所示。 2)。 在这种情况下,主动隐藏或删除的数据可能由用户设置 220 提前。 [0041] 此外,移动终端 210 可报移动终端丢失或被盗 210 向移动终端外的位置发送通知消息 210 ,例如服务基站。 通知消息可以包括移动终端的当前位置 210 . [0042] 如图。 图3图示了信息安全方法的示例。 [0043] 可以主动智能地执行信息安全方法。 [0044] 参考图。 3、在 310 所述信息安全方法可以从存储在移动终端中的数据中识别出用户请求保护的数据。 在这种情况下,用户可以请求提前保护与隐私、有价值的数据等相关的数据。 [0045] 在 320 ,该信息安全方法可以根据用户设置设置与移动终端丢失或被盗对应的操作模式。 例如,如果移动终端丢失或被盗,用户可能希望隐藏或删除要保护的数据的模式,并选择发送通知消息的模式。 [0046] 在 330,该信息安全方法可以收集与移动终端用户的特征行为模式相关联的数据。 在这种情况下,移动终端可以不断地收集用户的通话细节、访问互联网的历史、发送和/或接收文本消息的历史、击键信息和应用程序使用的历史。 因此,应用程序可以安装在移动终端中。 此外,移动终端可以收集关于移动终端的移动路线的信息、关于移动终端的环境的信息和用户的生物信息中的至少一种。 关于环境的信息可以包括移动终端所在位置的亮度、移动终端所在位置的湿度水平、移动终端所在位置的噪声水平,并且,生物信息可以包括体温 用户等 [0047] 在 340 ,信息安全方法可以基于收集的数据检测用户的特征行为模式。 在这种情况下,可以应用各种众所周知的数据分析方案,并且可以用数字或表格或图形来表示特征行为模式。 [0048] 在 350 ,该信息安全方法可以收集数据以实时检测移动终端用户的当前行为模式。 [0049] 在 360 ,信息安全方法可以比较特征行为模式,在 340 ,与行为模式,检测到 350 . [0050] 在 370 ,信息安全方法可以根据在 360 . [0051] 也就是说,在哪里检测到行为模式 350 ,与特征行为模式显着不同,在 340 ,信息安全方法可以确定当前用户为非授权用户。 相反,在行为模式中,检测到 350 ,与特征行为模式显着相似,在 340 ,信息安全方法可以确定当前用户为授权用户。 [0052] 在当前用户实际上是授权用户的情况下,信息安全方法可能会返回到 330 . 然而,在当前用户是未授权用户的情况下,信息安全方法可以执行至少一种传输数据(在 382 )和删除或隐藏数据(在 381 )。 [0053] 在 381 ,信息安全方法可能会隐藏或删除要保护的数据。 在 382 ,信息安全方法可以将通知消息发送到移动终端的外部位置。 [0054] 如图。 图4图示了在检测特征行为模式期间使用的数据的示例。 [0055] 要保护的数据的示例和操作模式在图1中示出。 4、即用户可以将例如从女朋友处接收到的图像文件确定为要保护的数据。 另外,需要保护的数据可以由用户设置,用户可以设置隐藏需要保护的数据的方式和移动终端丢失或被盗时发送通知消息的方式,作为 操作模式。 [0056] 用户可以根据如图1所示的特征行为模式来行动。 4、即用户可以在12:00到13:00之间向女朋友发送和/或接收图像文件,并在23:00到01:00之间与女朋友进行视频通话。 此外,用户通常在工作日沿着家-学校-家的路线移动,而在周末沿着家-培训中心-女朋友家-家的路线移动。 上述行为可以由移动终端自动监测,并且移动终端可以使用与收集的用户行为相关联的数据来检测特征行为模式。 因此,可以以诸如表格、数值、图表等的各种方式来表达特征行为模式。 [0057]例如,可以假设用户在周三早上去上学时在公交车上丢失了移动终端,而用户没有意识到这一点。 因此,在公共汽车上丢失的移动终端可以持续监控移动终端用户的行为模式。 [0058] 因此,移动终端沿着公交车的路线移动,并且用户在12:00和13:00之间没有发送和/或接收图像文件,并且移动终端周围的监测到的噪声可能比平时高。 [0059] 在这种情况下,移动终端可以通过基于收集到的数据的特征行为模式来确定移动终端周围的当前情况不同于典型模式。 具体地,移动终端可以将对应于特征行为模式的值与对应于移动终端周围的当前情况的值进行比较,并将比较的结果应用于特定规则,从而可以确定周围的当前情况 移动终端不同于特征行为模式。 [0060] 结果,移动终端可以隐藏从女朋友接收到的图像文件,这是要保护的数据,并发送通知消息。 因此,虽然用户可能无法识别移动终端的丢失或被盗,但数据将受到保护。 此外,即使在移动终端的通信不可用时,也可以有效地保护数据,因为不需要远程控制。 [0061] 如图。 图5图示了移动终端的示例的配置。 [0062] 参考图。 5、移动终端包括用户设置管理单元 510 , 一个数据库 520 , 一个模式比较/推理单元 530 , 一个监控单元 540 , 一个内部传感器 550 , 一个外部传感器 560 , 和一个后处理单元 570 . [0063] 用户设置管理单元 510 可以管理关于要保护的数据的用户设置,以及移动终端丢失或被盗时的操作模式。 要保护的数据可以由用户请求。 [0064] 数据库 520 可以基于收集到的与移动终端的用户的特征行为模式相关联的数据来存储用户的特征行为模式。 此行为模式由监控单元提供 540 . 在这种情况下,数据库 520 可以更新特征行为模式。 [0065] 此外,模式比较/推理单元 530 可以将特征行为模式与用户对移动终端的行为模式进行比较。 可以在特定时间段内监控行为模式。 此外,模式比较/推理单元 530 可以将比较的结果应用到特定规则,从而可以识别移动终端的当前状态。 [0066] 此外,监控单元 540 可以监控从内部传感器提供的数据 550 和外部传感器 560 ,基于数据实时检测用户对移动终端的行为模式。 此外,监控单元 540 可以将检测到的行为模式提供给数据库 520 和模式比较/推理单元 530 . 因此,内部传感器 550 可以提供给监控单元 540 、用户通话详情、上网历史、收发短信历史、按键信息、应用程序使用历史实时。 此外,外部传感器 560 可以提供给监控单元 540 、移动终端的移动路线、移动终端的环境信息、用户的生物信息。 [0067] 后处理单元 570 包括一个数据管理单元 571 和一个紧急通信单元 572 . 在这种情况下,数据管理单元 571 可根据用户设置隐藏或删除移动终端中存储的数据,紧急通信单元 572可以将与移动终端的当前状态或当前位置相关联的通知消息发送到移动终端之外的位置。 [0068] 由于参照图1至图5描述的描述。 图1至图4的实施例可以应用于图1所示的上述单元。 参照图5,这里将省略进一步的详细描述。 [0069] 上述过程、功能、方法和/或软件可以被记录、存储或固定在一个或多个计算机可读存储介质中,该存储介质包括将由计算机实现以使处理器执行或执行程序指令的程序指令 . 媒体还可以单独或与程序指令、数据文件、数据结构等组合地包括。 媒体和程序指令可以是那些专门设计和构造的,或者它们可以是计算机软件领域的技术人员熟知和可用的那种。 计算机可读介质的示例包括磁介质,例如硬盘、软盘和磁带; 光媒体,如 CD ROM 盘和 DVD; 磁光介质,例如光盘; 以及专门用于存储和执行程序指令的硬件设备,例如只读存储器(ROM)、随机存取存储器(RAM)、闪存等。 程序指令的示例包括诸如由编译器产生的机器代码,以及包含可由计算机使用解释器执行的更高级别代码的文件。 所描述的硬件设备可以被配置为充当一个或多个软件模块以执行上述操作和方法,反之亦然。 此外,计算机可读存储介质可以分布在通过网络连接的计算机系统之间,并且计算机可读代码或程序指令可以以分散方式存储和执行。 [0070] 如上文结合附图所描述的,移动终端可以主动或智能地确定移动终端是否丢失或被盗,或者当前用户是否为授权用户,从而可以有效地保护存储在移动终端中的信息,甚至 当用户不承认丢失或被盗时。 [0071] 同样如上面参考附图所描述的,移动终端可以将用户的特征行为模式与当前行为模式进行比较,从而可以准确地确定移动终端是否丢失或被盗或者当前用户是否是授权用户 . [0072] 进一步如以上参考附图所述,移动终端可以主动或智能地确定移动终端是否丢失或被盗,或者当前用户是否为授权用户,从而可以经济地保护存储在移动终端中的信息, 无需单独的硬件进行远程控制。 [0073] 上面已经描述了许多示例。 然而,应当理解,可以进行各种修改。 例如,如果以不同的顺序执行所描述的技术和/或如果所描述的系统、架构、设备或电路中的组件以不同的方式组合和/或由其他组件替换或补充或 他们的等价物。 因此,其他实施方式在所附权利要求的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101541305B1(String), KR1020100125588A(String), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101541305B1(String), KR1020100125588A(String), US20100299757A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101541305B1(String), KR1020100125588A(String), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270677(Integer), KR101541305B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270677(Integer), KR1020100125588A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270677(Integer), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:51.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100299757A1(String), US20100299757A1(String), 1290614400(Integer), 270677(Integer), 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), LEE, HO SUB(String), 三星电子株式会社(String), LEE HO SUB(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184998(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 184998(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LEE, HO SUB(String), LEE HO SUB(String), 0(Integer), 1681975552(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184998(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75945(Integer), 2(Integer), 184998(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.062 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120231798A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and cell reselection method of mobile terminal(String), 移动终端及移动终端的小区重选方法(String), US20120231798A1(String), The present invention provides a cell reselection method of a mobile terminal. The method comprises the following steps: setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. The present invention further provides a mobile terminal. The present invention solves the problem that the mobile terminal, which is in the WCDMA/GSM dual mode and resides in the GSM cell, cannot reside in the WCDMA cell while the WCDMA network can be used actually, improves the capability and success rate of the reselection toward the WCDMA network of the mobile terminal, and enables the user to have more opportunities to enjoy rich and colourful 3G services.(String), 本发明提供一种移动终端的小区重选方法。 该方法包括以下步骤:设置移动终端从GSM小区到WCDMA小区的重选参数; 根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 本发明还提供一种移动终端。 本发明解决了WCDMA/GSM双模驻留在GSM小区中的移动终端不能驻留在WCDMA小区而WCDMA网络可以实际使用的问题,提高了移动终端的能力和成功率。 重新选择移动终端的WCDMA网络,让用户有更多机会享受丰富多彩的3G服务。(String), US13/510346(String), 1282579200(Integer), US20120231798A1(String), 1347465600(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 3(Integer), US20040082328A1 | US20080102847A1 | US20100056178A1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184999(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\6e1f728b410c498da6dd951cd1b05bf8.png(String), 184999(Integer), 6e1f728b410c498da6dd951cd1b05bf8.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.100 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.102 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and cell reselection method of mobile terminal(String), 移动终端及移动终端的小区重选方法(String), US20120231798A1(String), The present invention provides a cell reselection method of a mobile terminal. The method comprises the following steps: setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. The present invention further provides a mobile terminal. The present invention solves the problem that the mobile terminal, which is in the WCDMA/GSM dual mode and resides in the GSM cell, cannot reside in the WCDMA cell while the WCDMA network can be used actually, improves the capability and success rate of the reselection toward the WCDMA network of the mobile terminal, and enables the user to have more opportunities to enjoy rich and colourful 3G services.(String), 本发明提供一种移动终端的小区重选方法。 该方法包括以下步骤:设置移动终端从GSM小区到WCDMA小区的重选参数; 根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 本发明还提供一种移动终端。 本发明解决了WCDMA/GSM双模驻留在GSM小区中的移动终端不能驻留在WCDMA小区而WCDMA网络可以实际使用的问题,提高了移动终端的能力和成功率。 重新选择移动终端的WCDMA网络,让用户有更多机会享受丰富多彩的3G服务。(String), US13/510346(String), 1282579200(Integer), US20120231798A1(String), 1347465600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 3(Integer), US20040082328A1 | US20080102847A1 | US20100056178A1(String), \20230420\6e1f728b410c498da6dd951cd1b05bf8.png(String), 14(Integer), 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 1. A mobile terminal, comprising a setting module and a detecting module, whereinthe setting module is configured to set a reselection parameter of a mobile terminal from a Global System for Mobile Communications (GSM) cell to a Wideband Code Division Multiple Access (WCDMA) cell; andthe detecting module is configured to judge whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter.(String), 1.移动终端,包括设置模块和检测模块,其中设置模块,用于设置移动终端从GSM小区到WCDMA小区的重选参数;和检测模块,用于根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 2. The mobile terminal according to claim 1, wherein, the step that the setting module sets a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: the setting module sets a first threshold of Received Energy per Chip Divided by the Noise Spectral Density (Ec/No) of the mobile terminal on each code channel of a transmitter after spreading spectrum, and sets a second threshold of Received Signal Code Power (RSCP).(String), 2.根据权利要求1所述的移动终端,其中,设置模块设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:设置模块设置第一门限值为每个码片的接收能量除以移动终端的噪声频谱密度(Ec/No)终端在扩频后的发射机的每个码道上,并设置接收信号码功率(RSCP)的第二门限。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 3. The mobile terminal according to claim 2, wherein, the step that the detecting module judges whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter comprises:the detecting module measures the value of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum of the WCDMA cell, and the value of the RSCP of the mobile terminal, and initiates a reselection toward the WCDMA cell when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP is greater than or equal to the second threshold which situation lasts for a second preset time.(String), 3.根据权利要求2所述的移动终端,其中,检测模块根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选包括:检测模块测量WCDMA小区扩频后发射机各码道上移动终端的Ec/No值和移动终端的RSCP值,当满足时向WCDMA小区发起重选发射机扩频后各码道上的Ec/No测量值大于或等于第一门限,这种情况持续第一预设时间,RSCP测量值大于或等于第二阈值,该情况持续第二预设时间。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 4. The mobile terminal according to claim 2, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module sets the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and sets the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 4.根据权利要求2所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和RSCP的第二门限包括:设置模块设置第一门限大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,并将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 5. The mobile terminal according to claim 2, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module presets the first threshold and the second threshold during factory manufacture of the mobile terminal, and sets the first threshold and the second threshold as being modifiable.(String), 5.根据权利要求2所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和设置RSCP的第二门限包括:设置模块预先设置第一门限和第二门限在移动终端出厂时,将第一阈值和第二阈值设置为可修改。6、一种移动终端的小区重选方法,包括:设置移动终端从GSM小区到WCDMA小区的重选参数;和根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 6. A cell reselection method of a mobile terminal, comprising:setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; andjudging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter.(String), 7.根据权利要求6所述的移动终端的小区重选方法,其中,设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:设置移动终端在WCDMA小区扩频后的发射机各码道上的第一门限Ec/No,设置RSCP的第二个阈值。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 7. The cell reselection method of a mobile terminal according to claim 6, wherein,the step of setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: setting a first threshold of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum of the WCDMA cell, and setting a second threshold of RSCP.(String), 8.根据权利要求7所述的移动终端的小区重选方法,其中,基于WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选包括:移动终端测量WCDMA小区扩频后的发射机信道大于或等于第一门限,该情况持续第一预设时间,并且WCDMA小区的RSCP测量值大于或者等于第二阈值,该情况持续第二预设时间。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 8. The cell reselection method of a mobile terminal according to claim 7, wherein, the step of judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter comprises: initiating a reselection toward the WCDMA cell when the measured value of Ec/No on each code channel of the transmitter after spreading spectrum of the WCDMA cell, measured by the mobile terminal, is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP of the WCDMA cell is greater than or equal to the second threshold which situation lasts for a second preset time.(String), 9.根据权利要求7所述的移动终端的小区重选方法,其中,设置第一阈值和第二阈值的步骤包括:将第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 9. The cell reselection method of a mobile terminal according to claim 7, wherein, the step of setting the first threshold and the second threshold comprises: setting the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and setting the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 10.根据权利要求7所述的移动终端的小区重选方法,其中,第一阈值和第二阈值在移动终端出厂时预先设置,可以修改。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 10. The cell reselection method of a mobile terminal according to claim 7, wherein, the first threshold and the second threshold are preset during factory manufacture of the mobile terminal, and are modifiable.(String), 11.根据权利要求3所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和RSCP的第二门限包括:设置模块设置第一门限大于或等于−18dB且小于FDD_Qmin−FDD_Qmin13Offset,将第二阈值设置为大于等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 11. The mobile terminal according to claim 3, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module sets the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin13Offset, and sets the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 12.根据权利要求3所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和设置RSCP的第二门限包括:设置模块预先设置第一门限和第二门限在移动终端出厂时,将第一阈值和第二阈值设置为可修改。(String), 1(Integer), 10(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 12. The mobile terminal according to claim 3, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module presets the first threshold and the second threshold during factory manufacture of the mobile terminal, and sets the first threshold and the second threshold as being modifiable.(String), 13.根据权利要求8所述的移动终端的小区重选方法,其中,设置第一阈值和第二阈值的步骤包括:将第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 13. The cell reselection method of a mobile terminal according to claim 8, wherein, the step of setting the first threshold and the second threshold comprises: setting the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and setting the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 14.根据权利要求8所述的移动终端的小区重选方法,其中,第一阈值和第二阈值在移动终端出厂时预先设置,可以修改。(String), 1(Integer), 12(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184999(Integer), 14. The cell reselection method of a mobile terminal according to claim 8, wherein, the first threshold and the second threshold are preset during factory manufacture of the mobile terminal, and are modifiable.(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 184999(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the technical field of mobile communication, and in particular to a mobile terminal and a cell reselection method of a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the development of mobile communication technology, at present, a same one operator usually operates a Wideband Code Division Multiple Access (WCDMA) network and a Global System for Mobile Communication (GSM) network at the same time, mainly for the reason: as the WCDMA in the mainstream standards of 3G is evolved from the GSM, in order to protect the investment on the GSM network at the earlier stage, the operator generally modifies and utilize the original GSM network; the operator needs to retain the old users of GSM network; and the WCDMA network construction cannot achieve complete coverage in short time. When the WCDMA network and the GSM network coexist, all the operators hope the users to switch from the GSM network to the WCDMA network, thus the users may use the rich 3G services, thereby increasing income of operators. [0003]In 3GPP protocol, there are requirements for reselection from the GSM cell to the WCDMA cell, relating to many parameters and algorithms, mainly comprising the following two adopted. [0004]First, control parameters of reselection from the GSM cell to the WCDMA cell are sent to the mobile terminal in the system information SYSTEM_INFORMATION—2QUATER; the mobile terminal stores these parameters after receiving them. The key parameters are as follows: [0005]3G Measurement Parameters Description[0006]Qsearch_I=7 (0×7)[0007]Qsearch_C_Initial=0 (0×0)[0008]fdd_qoffset_present=1 (0×1)[0009]FDD_Qoffset=0 (0×0)[0010]FDD_REP_QUANT=1 (0×1)[0011]FDD_MULTIRAT_REPORTING=0 (0×0)[0012]FDD_Qmin=7 (0×7)[0013]tdd_qoffset_present=0 (0×0) [0014]The description of value thereof can be obtained by referring to the 3GPP protocol 45.008, wherein the value of Qsearch_I is usually 7, which means to select the WCDMA cell unconditionally as long as the measurement of the WCDMA cell meets requirements, and the operator makes such configuration usually for the purpose of facilitating users to switch to the WCDMA network as much as possible; [0015]Second, after residing in the GSM cell, the mobile terminal constantly measures the surrounding WCDMA cells, calculates and judges the measured value according to the requirement of 6.6.5 in the 3GPP 45.008. Since the Qsearch_I is usually set as 7 (which means it is unconditional), finally it is judged whether the measured values of Received Energy per Chip Divided by the Noise Spectral Density (Ec/No) on each code channel of a transmitter after spreading spectrum and Received Signal Code Power (RSCP) meet the judging condition with the meeting lasts for more than 5 seconds, and if yes, a selection toward the WCDMA cell is initiated. The judging condition is that: whether the measured value of the Ec/No is greater than or equal to FDD_Qmin−FDD_Qmin_Offset; whether the measured value of the RSCP is greater than or equal to FDD_RSCP_threshold. [0016]The system information SYSTEM_INFORMATION—2QUATER sent by the network side decides the values of FDD_Qmin, FDD_Qmin_Offset and FDD_RSCP_threshold. The specific calculating and value setting methods can be know by referring to the 3GPP 45.008. [0017]In practical field test, it is often found that the mobile terminal can register to the WCDMA network when being set only in the WCDMA mode, but under the situation that the mobile terminal is set in WCDMA/GSM dual mode, if the mobile terminal firstly resides in the GSM cell, the measured values of the Ec/No and RSCP always do not meet the requirements, which causes the reselection toward the WCDMA cell cannot be initiated. Thus, the mobile terminal cannot reside in the WCDMA cell while the WCDMA network can be used actually. SUMMARY OF THE INVENTION [0018]The technical problem to be solved by the present invention is to provide a mobile terminal and a cell selection method thereof, which can improve the reselection capability of the mobile terminal from the GSM cell to the WCDMA cell. [0019]For solving the above technical problem, the present invention provides a cell selection method of a mobile terminal, which comprises the following steps: [0020]setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; and [0021]judging whether to initiate a reselection toward the WCDMA cell based on the s comparison between a signal measurement value of the WCDMA cell and the parameter. [0022]The step of setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: setting a first threshold of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum of the WCDMA cell, and setting a second threshold of RSCP. [0023]The step of judging based on comparison comprises: when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum of the WCDMA cell measured by the mobile terminal is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP of the WCDMA cell is greater than or equal to the second threshold which situation lasts for a second preset time, initiating a reselection toward the WCDMA cell. [0024]The first threshold is set as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, the second threshold is set as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0025]The first threshold and the second threshold can be preset during factory manufacture of the mobile terminal, and are modifiable. [0026]A mobile terminal, which comprises a setting module and a detecting module; the setting module is configured to set a reselection parameter of the mobile terminal from a GSM cell to a WCDMA cell, and the detecting module is configured to judge whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. [0027]The step of setting a reselection parameter of the mobile terminal from a GSM cell to a WCDMA cell comprises: the setting module sets a first threshold of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum, and sets a second threshold of RSCP. [0028]The detecting module is further configured to measure the value of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum of the WCDMA cell and the value of the RSCP of the mobile terminal, and initiate a reselection toward the WCDMA cell when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP is greater than or equal to the second threshold which situation lasts for a second preset time. [0029]The setting module is further configured to set the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and set the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0030]The setting module is further configured to preset the first threshold and the second threshold during factory manufacture of the mobile terminal, and set the first threshold and the second threshold as being modifiable. [0031]The beneficial effects of the present invention are as follows: [0032](1) in the present invention, setting a reselection parameter of a mobile terminal is from a GSM cell to a WCDMA cell, and judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter solve the problem that the mobile terminal, which is set in WCDMA/GSM dual mode, cannot reside in the WCDMA cell while the WCDMA network can be actually used, if the mobile terminal firstly resides in the GSM cell, and improve the capability and success rate of the reselection toward the WCDMA network of the mobile terminal, such that the user can have more opportunities to enjoy rich and colourful 3G services; [0033](2) in the present invention, when the measured value of Ec/No on each code channel of a transmitter after spreading spectrum of a WCDMA cell measured by the mobile terminal is greater than or equal to a first threshold which situation lasts for a first preset time, and the measured value of RSCP of the WCDMA cell is greater than or equal to a second threshold which situation lasts for a second preset time, a reselection toward the WCDMA cell is initiated, which is simple and easy to perform; [0034](3) in the present invention, the first threshold and the second threshold can be determined according to empirical values, which ensures that the mobile terminal can initiate a reselection from a GSM cell to a WCDMA cell when the condition is met; and [0035](4) in the present invention, the first threshold and the second threshold can be preset during factory manufacture of the mobile terminal and are modifiable, which enable the operator and user to set and modify based on actual need. Compared with the traditional art in which only the parameters sent by the network side are accepted, the first threshold and the second threshold can be adjusted according to actual situation, so it is more flexible and convenient to use. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a schematic diagram of a structure of a specific embodiment of a mobile terminal of the present invention; [0037]FIG. 2 is a flowchart of a cell reselection method of the present invention; and [0038]FIG. 3 is a flowchart of a specific embodiment of a cell reselection method of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0039]The present invention is described in detail hereinafter with reference to the accompanying drawings and in conjunction with embodiments. [0040]FIG. 1 is a schematic diagram of a structural of a specific embodiment of a mobile terminal of the present invention. As shown in FIG. 1, in an embodiment of the mobile terminal of the present invention, the mobile terminal comprises a setting module and a detecting module, wherein [0041]the setting module is configured to set a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; [0042]the detecting module is configured to judge whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter. [0043]The step that the setting module sets a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: the setting module sets a first threshold Ec/No min of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum of the WCDMA cell and sets a second threshold RSCP_min of RSCP. [0044]The step that the detecting module judges whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter comprises: the detecting module measures the value of the Ec/No on each code channel of the transmitter after spreading spectrum of the WCDMA cell and the value of the RSCP of the mobile terminal, and initiates a reselection toward the WCDMA cell when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum is greater than or equal to the first threshold Ec/No_min which situation lasts for a first preset time, and the measured value of the RSCP is greater than or equal to the second threshold RSCP_min, lasting for a second preset time. [0045]The first preset time can be set according to specific need, and in this specific embodiment, it can be set as 5 seconds or other suitable time. The second preset time can also be set according to specific need, and in this specific embodiment, it can be set as 5 seconds or other suitable time. [0046]Preferably, the first threshold Ec/No_min can be set as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and the second threshold RSCP_min can be set as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0047]The setting module is further configured to set the first threshold Ec/No_min and the second threshold RSCP_min according to empirical value. [0048]The setting module can preset the first threshold Ec/No_min and the second threshold RSCP_min during factory manufacture of the mobile terminal, and set them as being modifiable. [0049]FIG. 2 is a flowchart of a cell reselection method of the present invention. As shown in FIG. 2, the cell reselection method of the present invention comprises the following steps: [0050]Step 201: setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; [0051]Step 202: judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. [0052]In this case, the parameter compared with the signal measurement value of the WCDMA cell is the reselection parameter from the GSM cell to the WCDMA cell in Step 201. [0053]The cell reselection method of a mobile terminal of the present invention is described hereinafter in detail. FIG. 3 is a flowchart of a specific embodiment of a cell reselection method of the present invention. As shown in FIG. 3, the method comprises the following steps: [0054]Step 301: setting the threshold Ec/No_min of the Ec/No and the threshold RSCP_min of the RSCP. [0055]In this specific embodiment, the threshold of the Ec/No is the first threshold, and specifically the first threshold Ec/No_min can be set as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset. The threshold of the RSCP is the second threshold, and specifically the second threshold RSCP_min can be set as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0056]The first threshold Ec/No_min and the second threshold RSCP min can be set according to empirical value. [0057]In practical application, the first threshold Ec/No_min and the second threshold RSCP_min can be preset during factory manufacture of the mobile terminal, and are set as being modifiable, thus they can be adjusted flexibly for different networks; [0058]Step 302: the mobile terminal detects a WCDMA cell. [0059]The mobile terminal measures the surrounding WCDMA cells and measures the signals thereof. In this specific embodiment, it is needed to measure the Ec/No and its lasting period, the RSCP and its lasting period and so on. [0060]Step 303: it is judged whether the measured value of the Ec/No is greater than or equal to the Ec/No_min which situation lasts for a first preset time, and whether the measured value of the RSCP is greater than or equal to the RSCP_min which situation lasts for a second preset time, and if yes, turning to Step 304, otherwise, turning to Step 302. [0061]The mobile terminal judges whether the measured value of the Ec/No is greater than or equal to the Ec/No_min which situation lasts for the first preset time, wherein the first preset time can be set according to specific requirement, and in this specific embodiment, it can be set as 5 seconds or other suitable time; the mobile terminal judges whether the measured value of the RSCP is greater than or equal to the RSCP_min which situation lasts for the second preset time, wherein the second preset time can also be set according to specific requirement, and in this specific embodiment, it can be set as 5 seconds or other suitable time. If simultaneously meeting the conditions that the measured value of the Ec/No is greater than or equal to the Ec/No_min which situation lasts for the first preset time, and the measured value of the RSCP is greater than or equal to the RSCP_min which situation lasts for the second preset time, it turns to Step 304, otherwise, it turns to Step 302. [0062]Step 304: initiating a reselection toward the WCDMA cell. [0063]In this case, the mobile terminal initiates the reselection toward the WCDMA cell. [0064]In the present invention, except setting the first threshold Ec/No_min and its first preset time, and the second threshold RSCP_min and its preset time, other parameters can be set according to the requirements of 6.6.5 in the 3GPP 45.008. [0065]The above content is further detailed descriptions of the present invention in conjunction with the specific embodiments, and the specific embodiments of the present invention should not limit only to these descriptions. Those skilled in the art can perform some simple deductions or equivalent substitutions without departing from the spirit of the present invention, and these deductions or substitutions are within the scope of the claims of the present invention.(String), 发明领域 [0001] 本发明涉及移动通信技术领域,尤其涉及一种移动终端及移动终端的小区重选方法。 发明背景 [0002] 随着移动通信技术的发展,目前同一个运营商通常同时运营一个宽带码分多址(WCDMA)网络和一个全球移动通信系统(GSM)网络,主要是因为:作为 3G主流标准中的WCDMA是从GSM演进而来的,为了保护前期对GSM网络的投资,运营商一般会对原有的GSM网络进行改造利用; 运营商需要留住GSM网络的老用户; 而WCDMA网络建设无法在短时间内实现全覆盖。 当WCDMA网络和GSM网络并存时,所有运营商都希望用户从GSM网络切换到WCDMA网络,这样用户就可以享受到丰富的3G业务,从而增加运营商的收入。 [0003] 在3GPP协议中,对从GSM小区重选到WCDMA小区有要求,涉及到很多参数和算法,主要采用的有以下两种。 [0004] 首先在系统信息SYSTEM_INFORMATION中向移动终端发送GSM小区重选到WCDMA小区的控制参数 — 2季度; 移动终端接收到这些参数后进行存储。 关键参数如下: [0005] 3G测量参数说明 [0006]Qsearch_I=7 (0×7)[0007] Qsearch_C_Initial=0 (0×0)[0008] fdd_qoffset_present=1 (0×1)[0009] FDD_Qoffset=0 (0×0)[0010] FDD_REP_QUANT=1 (0×1)[0011] FDD_MULTIRAT_REPORTING=0 (0×0)[0012] FDD_Qmin=7 (0×7)[0013] tdd_qoffset_present=0 (0×0) [0014] 其取值的描述可参考3GPP协议45.008,其中Qsearch_I的取值通常为7,表示只要WCDMA小区的测量满足要求,就无条件选择WCDMA小区,运营商做出这样的选择 配置通常是为了方便用户尽可能切换到WCDMA网络; [0015] 第二,移动终端驻留在GSM小区后,不断测量周围的WCDMA小区,根据3GPP 45.008中6.6.5的要求计算判断测量值。 由于Qsearch_I通常设置为7(表示无条件),最后判断扩频后发射机各码道上的每码片接收能量除以噪声谱密度(Ec/No)的测量值是否 和接收信号码功率(RSCP)满足判断条件且满足持续5秒以上,如果满足,则发起对WCDMA小区的选择。 判断条件为:Ec/No的测量值是否大于等于FDD_Qmin-FDD_Qmin_Offset; RSCP的测量值是否大于等于FDD_RSCP_threshold。 [0016] 系统信息SYSTEM_INFORMATION — 网络侧发送的2QUATER决定了FDD_Qmin、FDD_Qmin_Offset和FDD_RSCP_threshold的值。 具体的计算和取值方法可以参考3GPP 45.008。 [0017] 在实际外场测试中,经常发现移动终端只设置为WCDMA模式时可以注册到WCDMA网络,但是在移动终端设置为WCDMA/GSM双模式的情况下,如果移动终端先 驻留在GSM小区,Ec/No和RSCP的测量值总是不符合要求,导致无法发起向WCDMA小区的重选。 这样,移动终端不能驻留在WCDMA小区中,而WCDMA网络可以实际使用。 发明内容 [0018] 本发明所要解决的技术问题是提供一种移动终端及其小区选择方法,能够提高移动终端从GSM小区到WCDMA小区的重选能力。 [0019] 为解决上述技术问题,本发明提供了一种移动终端的小区选择方法,包括以下步骤: [0020] 设置移动终端从GSM小区到WCDMA小区的重选参数; 和 [0021]根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 [0022] 设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:在WCDMA小区扩频后,在发射机的每个码道上设置移动终端的第一门限Ec/No,设置 RSCP 的第二个阈值。 [0023] 所述基于比较判断的步骤包括:当移动终端测量的WCDMA小区扩频后的发射机各码道上的Ec/No测量值大于或等于第一门限时,该情况持续为 第一预设时间,WCDMA小区的RSCP测量值大于或等于第二阈值,该情况持续第二预设时间,发起向WCDMA小区的重选。 [0024] 第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。 [0025] 第一阈值和第二阈值可以在移动终端出厂时预先设置,可以修改。 [0026] 一种移动终端,包括设置模块和检测模块; 设置模块用于设置移动终端从GSM小区到WCDMA小区的重选参数,检测模块用于根据信号测量值与WCDMA小区的比较判断是否发起向WCDMA小区的重选 WCDMA 小区和参数。 [0027] 设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:设置模块在发射机扩频后的每个码道上设置移动终端的第一门限Ec/No,并设置 RSCP 的第二个阈值。 [0028] 检测模块,还用于测量WCDMA小区扩频后发射机各码道上移动终端的Ec/No值和移动终端的RSCP值,并发起重选。 WCDMA小区,当发射机扩频后各码道上的Ec/No测量值大于或等于第一门限,且该情况持续第一预设时间,且RSCP测量值大于或等于 等于第二阈值,该情况持续第二预设时间。 [0029] 设置模块还用于将第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。 [0030] 设置模块还用于在移动终端出厂时预先设置第一阈值和第二阈值,并设置第一阈值和第二阈值可修改。 [0031] 本发明的有益效果如下: [0032] (1)本发明中,设置移动终端的重选参数为从GSM小区到WCDMA小区,根据WCDMA小区信号测量值的比较判断是否发起向WCDMA小区的重选 该参数解决了设置为WCDMA/GSM双模式的移动终端无法驻留在WCDMA小区的问题,而如果移动终端先驻留在GSM小区,则可以实际使用WCDMA网络,提高了 移动终端重选WCDMA网络的能力和成功率,使用户有更多机会享受丰富多彩的3G业务; [0033](2)本发明中,当移动终端测量的WCDMA小区扩频后发射机各码道上的Ec/No测量值大于或等于第一门限时,该情况持续第一时间 预设时间,且WCDMA小区的RSCP测量值大于或等于第二阈值,且该情况持续第二预设时间,则发起向WCDMA小区的重选,简单易行。 [0034] (3)本发明中,第一门限和第二门限可以根据经验值确定,保证了移动终端在满足条件时能够发起从GSM小区到WCDMA小区的重选; 和 [0035] (4)在本发明中,第一阈值和第二阈值可以在移动终端出厂时预先设置,并且可以修改,使得运营商和用户可以根据实际需要进行设置和修改。 与传统技术只接受网络侧发送的参数相比,第一门限和第二门限可以根据实际情况进行调整,使用起来更加灵活方便。 附图的简要说明 [0036] 图1为本发明移动终端一个具体实施例的结构示意图; [0037] 图2是本发明小区重选方法的流程图; 和 [0038] 图3为本发明小区重选方法的一个具体实施例的流程图。 具体实施方式 [0039] 下面将参照附图并结合实施例对本发明进行详细说明。 [0040] 图1为本发明移动终端一个具体实施例的结构示意图。 如图1所示,在本发明移动终端的一个实施例中,移动终端包括设置模块和检测模块,其中 [0041] 设置模块,用于设置移动终端从GSM小区到WCDMA小区的重选参数; [0042] 检测模块,用于根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选。 [0043] 设置模块设置移动终端从GSM小区到WCDMA小区的重选参数包括:设置模块在发射机的每个码道上设置移动终端的Ec/No的第一阈值Ec/No min 在WCDMA小区扩频之后,设置RSCP的第二阈值RSCP_min。 [0044] 检测模块根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选包括: 检测模块测量各码道上的Ec/No值 WCDMA小区扩频后发射机的RSCP值与移动终端RSCP的值,当发射机扩频后各码道上的Ec/No测量值较大时,向WCDMA小区发起重选 大于等于第一阈值Ec/No_min,持续第一预设时间,RSCP的测量值大于等于第二阈值RSCP_min,持续第二预设时间。 [0045] 第一预设时间可以根据具体需要进行设置,在本具体实施例中,可以设置为5秒或者其他合适的时间。 第二预设时间也可以根据具体需要进行设置,在本具体实施例中,可以设置为5秒或者其他合适的时间。 [0046] 优选地,第一门限Ec/No_min可设置为大于等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,第二门限RSCP_min可设置为大于等于-105dB且小于FDD_RSCP_threshold . [0047]设置模块还用于根据经验值设置第一阈值Ec/No_min和第二阈值RSCP_min。 [0048] 设置模块可以在移动终端出厂时预先设置第一阈值Ec/No_min和第二阈值RSCP_min,并设置为可修改。 [0049] 图2是本发明小区重选方法的流程图。 如图2所示,本发明的小区重选方法包括以下步骤: [0050] 步 201 :设置移动终端从GSM小区到WCDMA小区的重选参数; [0051] 步 202 :根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 [0052] 此时,与WCDMA小区的信号测量值比较的参数为步骤中GSM小区到WCDMA小区的重选参数 201 . [0053] 下面对本发明的移动终端的小区重选方法进行详细说明。 图3为本发明小区重选方法的一个具体实施例的流程图。 如图3所示,该方法包括以下步骤: [0054] 步 301 :设置Ec/No的阈值Ec/No_min和RSCP的阈值RSCP_min。 [0055] 本具体实施例中,Ec/No的门限为第一门限,具体可以将第一门限Ec/No_min设置为大于等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset。 RSCP的阈值为第二阈值,具体可以将第二阈值RSCP_min设置为大于等于-105dB且小于FDD_RSCP_threshold。 [0056] 第一阈值Ec/No_min和第二阈值RSCP min可根据经验值设定。 [0057] 在实际应用中,第一门限Ec/No_min和第二门限RSCP_min可以在移动终端出厂时预先设置,设置为可修改的,从而可以针对不同的网络灵活调整。 [0058] 步 302 :移动终端检测到WCDMA小区。 [0059] 移动终端测量周围的WCDMA小区并测量其信号。 在本具体实施例中,需要测量Ec/No及其持续时间、RSCP及其持续时间等。 [0060] 步 303 :判断Ec/No的测量值是否大于或等于Ec/No_min哪种情况持续第一预设时间,以及RSCP的测量值是否大于或等于RSCP_min哪种情况 持续第二个预设时间,如果是,则转到步骤 304 , 否则转向 Step 302 . [0061] 移动终端判断Ec/No的测量值是否大于或等于Ec/No_min哪种情况持续第一预设时间,其中第一预设时间可以根据具体需要设置,在本具体实施例中 ,可设置为5秒或其他合适的时间; 移动终端判断RSCP的测量值是否大于或等于RSCP_min,这种情况持续第二预设时间,其中,第二预设时间也可以根据具体需要进行设置,在本具体实施例中,可以 设置为 5 秒或其他合适的时间。 如果同时满足Ec/No测量值大于或等于Ec/No_min这种情况持续第一个预设时间,并且RSCP测量值大于或等于RSCP_min这种情况 持续第二个预设时间,转为Step 304 , 否则转为 Step 302 . [0062] 步 304 :向WCDMA小区发起重选。 [0063] 在这种情况下,移动终端发起向WCDMA小区的重选。 [0064]本发明中,除了设置第一阈值Ec/No_min及其第一预设时间、第二阈值RSCP_min及其预设时间外,其他参数可按照3GPP 45.008中6.6.5的要求进行设置。 [0065] 以上内容是结合具体实施例对本发明所做的进一步详细说明,本发明的具体实施不应只局限于这些说明。 本领域的技术人员可以在不脱离本发明的精神的情况下进行一些简单的推演或等同替换,这些推演或替换都在本发明的权利要求的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101707791A(String), EP2503821A1(String), EP2503821A4(String), US20120231798A1(String), WO2011060657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101707791A(String), EP2503821A1(String), EP2503821A4(String), US20120231798A1(String), WO2011060657A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120231798A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101707791A(String), EP2503821A1(String), EP2503821A4(String), US20120231798A1(String), WO2011060657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270678(Integer), CN101707791A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270678(Integer), EP2503821A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270678(Integer), EP2503821A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270678(Integer), US20120231798A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270678(Integer), WO2011060657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120231798A1(String), US20120231798A1(String), 1347465600(Integer), 270678(Integer), 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184999(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 184999(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184999(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 184999(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20170131793A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Controlling Mobile Terminal Screen Display and Mobile Terminal(String), 一种控制移动终端屏幕显示的方法及移动终端(String), US20170131793A1(String), A method for controlling mobile terminal screen display, and a mobile terminal is presented. The method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 提出了一种控制移动终端屏幕显示的方法及移动终端。 该方法包括获取移动终端的当前倾斜角度; 当确定当前倾斜角度在第二或第三预设角度范围内时,根据该倾斜角度调整移动终端屏幕的界面内容布局。 或者,在确定移动终端的当前倾斜角度在第一预设角度范围内时,保持移动终端屏幕现有的界面内容布局,其中第二、第一和第三预设角度范围依次形成连续的角度范围。(String), US15/414869(String), 1485273600(Integer), US20170131793A1(String), 1494432000(Integer), 美国(String), 2(Integer), 5(Integer), 0(Integer), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185000(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\9d454f2654cb4a7796fa5023b1ac0f59.png(String), 185000(Integer), 9d454f2654cb4a7796fa5023b1ac0f59.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Controlling Mobile Terminal Screen Display and Mobile Terminal(String), 一种控制移动终端屏幕显示的方法及移动终端(String), US20170131793A1(String), A method for controlling mobile terminal screen display, and a mobile terminal is presented. The method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 提出了一种控制移动终端屏幕显示的方法及移动终端。 该方法包括获取移动终端的当前倾斜角度; 当确定当前倾斜角度在第二或第三预设角度范围内时,根据该倾斜角度调整移动终端屏幕的界面内容布局。 或者,在确定移动终端的当前倾斜角度在第一预设角度范围内时,保持移动终端屏幕现有的界面内容布局,其中第二、第一和第三预设角度范围依次形成连续的角度范围。(String), US15/414869(String), 1485273600(Integer), US20170131793A1(String), 1494432000(Integer), 美国(String), 2(Integer), 2(Integer), 5(Integer), 0(Integer), \20230420\9d454f2654cb4a7796fa5023b1ac0f59.png(String), 20(Integer), 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 1. A mobile terminal, comprising:a sensor configured to acquire a current tilt angle of the mobile terminal;a screen configured to display interface content on the mobile terminal; anda processor configured to:adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a second or third preset angle range; andkeep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 1.移动终端,包括:传感器,用于获取移动终端的当前倾斜角度;屏幕,用于在移动终端上显示界面内容;和处理器配置为:在确定当前倾斜角度处于第二或第三预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 2. The mobile terminal according to claim 1, wherein the processor being configured to adjust the interface content layout of the mobile terminal screen according to the tilt angle comprises the processor being configured to:determine an adjustment magnitude according to the tilt angle; andadjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude.(String), 2.根据权利要求1所述的移动终端,其中处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,包括:根据倾斜角度确定调整幅度;和根据调整幅度调整移动终端屏幕的全部或部分界面内容。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 3. The mobile terminal according to claim 2, wherein the processor being configured to determine the adjustment magnitude according to the tilt angle, and adjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude comprises the processor being configured to implement one of the following:determine an adjustment distance according to the tilt angle, and pan or float all or a part of the interface content of the mobile terminal screen, wherein a distance of the panning or floating is the adjustment distance; anddetermine an adjustment angle according to the tilt angle, and rotate all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, wherein an angle of the rotating is the adjustment angle.(String), 3.根据权利要求2所述的移动终端,其中处理器,用于根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容,包括:处理器,用于实现以下之一:根据倾斜角度确定调整距离,对移动终端屏幕的全部或部分界面内容进行平移或浮动,平移或浮动的距离即为调整距离。和根据倾斜角度确定调整角度,以移动终端屏幕为中心旋转移动终端屏幕的全部或部分界面内容,旋转的角度即为调整角度。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 4. The mobile terminal according to claim 3, wherein the processor being configured to adjust the interface content layout of the mobile terminal screen according to the tilt angle further comprises the processor being configured to:determine an adjustment direction according to the tilt angle; andadjust the interface content layout of the mobile terminal screen in the determined adjustment direction.(String), 4.根据权利要求3所述的移动终端,其中处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,还包括:处理器,用于:根据倾斜角度确定调整方向;和沿确定的调整方向调整移动终端屏幕的界面内容布局。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 5. The mobile terminal according to claim 4, wherein the processor being configured to determine the adjustment direction according to the tilt angle comprises the processor being configured to:determine that the adjustment direction is a first direction when the current tilt angle is in the second preset angle range; anddetermine that the adjustment direction is a second direction when the current tilt angle is in the third preset angle range.(String), 5.根据权利要求4所述的移动终端,其中处理器,用于根据倾斜角度确定调整方向,包括:处理器,用于:当前倾斜角度在第二预设角度范围内时,确定调整方向为第一方向;和当前倾斜角度在第三预设角度范围内时,确定调整方向为第二方向。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 6. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 6.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向上,当移动终端当前的倾斜角度小于第一阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮;和确定调整方向为向下,当移动终端当前倾斜角度大于第二阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 7. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 7.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向下,当移动终端当前倾斜角度小于第一阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容;和确定调整方向为向上,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或浮动。(String), 1(Integer), 6(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 8. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 8.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向右,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动;和确定调整方向为向左,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。(String), 1(Integer), 7(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 9. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 9.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向左,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动;和确定调整方向为向右,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。(String), 1(Integer), 8(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 10. The mobile terminal according to claim 2, wherein the sensor is further configured to acquire ambient light intensity information of the mobile terminal, and wherein the processor being configured to determine an adjustment magnitude according to the tilt angle comprises the processor being configured to determine, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle.(String), 10.根据权利要求2所述的移动终端,其中所述传感器,还用于获取所述移动终端的环境光强度信息,其中,所述处理器用于根据所述倾斜角度确定调整幅度,包括所述处理器用于根据所述环境光强度信息确定调整量对应于倾斜角的大小。(String), 1(Integer), 9(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 11. The mobile terminal according to claim 1, wherein the processor is further configured to:receive angle range adjustment information; andadjust at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information.(String), 11.根据权利要求1所述的移动终端,其中处理器还被配置为:接收角度范围调整信息;和根据角度范围调整信息调整第一、第二或第三预设角度范围中的至少一个预设角度范围。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 12. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 12.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向上,当移动终端当前的倾斜角度小于第一阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮;和确定调整方向为向下,当移动终端当前倾斜角度大于第二阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容。(String), 1(Integer), 11(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 13. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 13.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向下,当移动终端当前倾斜角度小于第一阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容;和确定调整方向为向上,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或浮动。(String), 1(Integer), 12(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 14. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 14.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向右,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动;和确定调整方向为向左,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。(String), 1(Integer), 13(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 15. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 15.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向左,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动;和确定调整方向为向右,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。16、一种控制移动终端屏幕显示的方法,包括:获取移动终端的当前倾斜角度;当确定当前倾斜角度在第二或第三预设角度范围内时,根据倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。(String), 1(Integer), 14(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 16. A method for controlling mobile terminal screen display, comprising:acquiring a current tilt angle of a mobile terminal;adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; andkeeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 17.根据权利要求16所述的方法,其中根据倾斜角度调整移动终端屏幕的界面内容布局包括:根据倾斜角度确定调整幅度;和根据调整幅度调整移动终端屏幕的全部或部分界面内容。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 17. The method according to claim 16, wherein adjusting the interface content layout of the mobile terminal screen according to the tilt angle comprises:determining an adjustment magnitude according to the tilt angle; andadjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude.(String), 18.根据权利要求17所述的方法,其中根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容,包括以下之一:根据倾斜角度确定调整距离,对移动终端屏幕的全部或部分界面内容进行平移或浮动,平移或浮动的距离即为调整距离。和根据倾斜角度确定调整角度,以移动终端屏幕为中心旋转移动终端屏幕的全部或部分界面内容,旋转的角度即为调整角度。19、一种控制移动终端屏幕显示的方法,包括:获取移动终端的当前倾斜角度;在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 18. The method according to claim 17, wherein determining the adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude comprises one of the following:determining an adjustment distance according to the tilt angle, and panning or floating all or a part of the interface content of the mobile terminal screen, wherein a distance of the panning or floating is the adjustment distance; anddetermining an adjustment angle according to the tilt angle, and rotating all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, wherein an angle of the rotating is the adjustment angle.(String), 20.移动终端,包括:传感器,用于获取移动终端的当前倾斜角度;屏幕,用于在移动终端上显示界面内容;和处理器配置为:在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 19. A method for controlling mobile terminal screen display, comprising:acquiring a current tilt angle of a mobile terminal;adjusting an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; andkeeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.443 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185000(Integer), 20. A mobile terminal, comprising:a sensor configured to acquire a current tilt angle of the mobile terminal;a screen configured to display interface content on the mobile terminal; anda processor configured to:adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; andkeep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 0(Integer), 19(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185000(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Patent Application No. PCT/CN2014/083097 filed on Jul. 26, 2014, the disclosure of which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present disclosure relates to the technical field of mobile terminals, and in particular, to a method for controlling mobile terminal screen display and a mobile terminal. BACKGROUND [0003]Currently, functions of mobile terminals such as a mobile phone and a tablet keep increasing. Nowadays, most smart mobile terminals can switch between a landscape orientation and a portrait orientation of an interface (which is equivalent to rotating the interface by 90 degrees) on a mobile terminal screen so long as a tilt angle of the mobile terminal is greater than a specific angle, which, however, tends to cause unwanted switching. That is, although the mobile terminal tilts at a specific angle, a user does not expect switching of interface display. Consequently, control of screen display does not exactly meet a use requirement of the user, thereby lowering user experience. SUMMARY [0004]Embodiments of the present disclosure provide a method for controlling mobile terminal screen display and a mobile terminal to better meet a use requirement of a user and improve user experience. [0005]According to a first aspect, an embodiment of the present disclosure provides a method for controlling mobile terminal screen display, where the method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0006]With reference to the first aspect, in a first possible implementation manner of the first aspect, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle includes determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude. [0007]With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude includes determining an adjustment distance according to the tilt angle, and panning or floating all or a part of the interface content of the mobile terminal screen, where a distance of the panning or floating is the adjustment distance; or determining an adjustment angle according to the tilt angle, and rotating all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, where an angle of the rotating is the adjustment angle. [0008]With reference to the first or second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle further includes determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction. [0009]With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the determining an adjustment direction according to the tilt angle includes, when the current tilt angle is in the second preset angle range, determining that the adjustment direction is a first direction; or when the current tilt angle is in the third preset angle range, determining that the adjustment direction is a second direction. [0010]With reference to the third or fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen. [0011]With reference to the third or fourth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen. [0012]With reference to the third or fourth possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen. [0013]With reference to the third or fourth possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen. [0014]With reference to any one of the first possible implementation manner of the first aspect to the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner of the first aspect, the method further includes acquiring ambient light intensity information of the mobile terminal; and the determining an adjustment magnitude according to the tilt angle includes determining, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle. [0015]With reference to the first aspect or any one of the first possible implementation manner of the first aspect to the ninth possible implementation manner of the first aspect, in a tenth possible implementation manner of the first aspect, the method further includes receiving angle range adjustment information; and adjusting at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information. [0016]According to a second aspect, an embodiment of the present disclosure provides a method for controlling mobile terminal screen display, where the method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0017]According to a third aspect, an embodiment of the present disclosure provides a mobile terminal, where the mobile terminal includes a sensor configured to acquire a current tilt angle of the mobile terminal; a screen configured to display interface content on the mobile terminal; and a processor configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a second or third preset angle range; or keep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0018]With reference to the third aspect, in a first possible implementation manner of the third aspect, the processor being configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle includes the processor being configured to determine an adjustment magnitude according to the tilt angle, and adjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude. [0019]With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the processor being configured to determine an adjustment magnitude according to the tilt angle, and adjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude includes the processor being configured to determine an adjustment distance according to the tilt angle, and pan or float all or a part of the interface content of the mobile terminal screen, where a distance of the panning or floating is the adjustment distance; or the processor being configured to determine an adjustment angle according to the tilt angle, and rotate all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, where an angle of the rotating is the adjustment angle. [0020]With reference to the first or second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the processor being configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle further includes the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction. [0021]With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the processor being configured to determine an adjustment direction according to the tilt angle is the processor being configured to, when the current tilt angle is in the second preset angle range, determine that the adjustment direction is a first direction; or when the current tilt angle is in the third preset angle range, determine that the adjustment direction is a second direction. [0022]With reference to the third or fourth possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen. [0023]With reference to the third or fourth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen. [0024]With reference to the third or fourth possible implementation manner of the third aspect, in a seventh possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen. [0025]With reference to the third or fourth possible implementation manner of the third aspect, in an eighth possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen. [0026]With reference to any one of the first possible implementation manner of the third aspect to the eighth possible implementation manner of the third aspect, in a ninth possible implementation manner of the third aspect, the sensor is further configured to acquire ambient light intensity information of the mobile terminal; and the processor being configured to determine an adjustment magnitude according to the tilt angle includes the processor being configured to determine, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle. [0027]With reference to the third aspect or any one of the first possible implementation manner of the third aspect to the ninth possible implementation manner of the third aspect, in a tenth possible implementation manner of the third aspect, the processor is further configured to receive angle range adjustment information; and adjust at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information. [0028]According to a fourth aspect, an embodiment of the present disclosure provides a mobile terminal, where the mobile terminal includes a sensor configured to acquire a current tilt angle of the mobile terminal; a screen configured to display interface content on the mobile terminal; and a processor configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; or keep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0029]According to the method and the mobile terminal that are provided in the embodiments of the present disclosure, a current tilt angle of the mobile terminal may be detected; and an interface content layout of a mobile terminal screen is adjusted according to the tilt angle only in a case in which the current tilt angle of the mobile terminal meets a specific range condition, for example, when the current tilt angle of the mobile terminal is in a second or third preset angle range; or an existing interface content layout of a mobile terminal screen is kept when the current tilt angle of the mobile terminal is in a first preset angle range. In this way, screen display adjustment is avoided in a case in which a user does not expect the screen display adjustment although the mobile terminal tilts at a specific angle, so that the method for controlling mobile terminal screen display better meets a use requirement of the user and improves user experience. BRIEF DESCRIPTION OF DRAWINGS [0030]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0031]FIG. 1 is a flowchart of a method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0032]FIG. 2 is a flowchart of another method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0033]FIG. 3A, FIG. 3B, FIG. 4A, FIG. 4B, FIG. 5A, and FIG. 5B, are schematic diagrams of a tilt angle of a mobile terminal according to an embodiment of the present disclosure; [0034]FIG. 6, FIG. 7, FIG. 8, FIG. 9, and FIG. 10 are schematic effect diagrams of a method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0035]FIG. 11, FIG. 12, and FIG. 13 are schematic effect diagrams of another method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0036]FIG. 14 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure; [0037]FIG. 15 is a schematic diagram of a tilt angle of a mobile terminal according to an embodiment of the present disclosure; and [0038]FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 16E, FIG. 16F, and FIG. 16G are schematic effect diagrams of another method for controlling mobile terminal screen display according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0039]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0040]The term “and/or” in this specification describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, the character “/” in this specification generally indicates an “or” relationship between associated objects. Embodiment 1 [0041]As shown in FIG. 1, in an embodiment of a method for controlling mobile terminal screen display according to the present disclosure, the method may include the following steps. [0042]Step 101. Acquire a current tilt angle of a mobile terminal. [0043]The current tilt angle of the mobile terminal may be detected and acquired using a sensor such as a gravity sensor or a gyro sensor. [0044]The mobile terminal in the present disclosure may be a mobile terminal device with a screen, such as a mobile phone, a tablet, or a personal digital assistant (PDA), where the screen may be a touchscreen. [0045]Step 102. Adjust an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range. [0046]Step 103. Keep an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, that is, skip adjusting the interface content layout currently displayed on the mobile terminal screen. [0047]The second, first, and third preset angle ranges sequentially form a continuous angle range. [0048]Further, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle includes determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude. [0049]Further, the determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude includes determining an adjustment distance according to the tilt angle, and panning or floating all or a part of the interface content of the mobile terminal screen, where a distance of the panning or floating is the adjustment distance; or determining an adjustment angle according to the tilt angle, and rotating all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, where an angle of the rotating is the adjustment angle. [0050]Further, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle further includes determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction. [0051]Further, the determining an adjustment direction according to the tilt angle includes, when the current tilt angle is in the second preset angle range, determining that the adjustment direction is a first direction; or when the current tilt angle is in the third preset angle range, determining that the adjustment direction is a second direction. [0052]The first direction may be the same as or different from the second direction, which may be determined according to a specific condition. [0053]Further, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold. [0054]The current tilt angle of the mobile terminal may be an acute angle or a right angle, the first threshold is greater than 0 degrees, and the second threshold is less than or equal to 90 degrees. [0055]For example, the first threshold may be 30 degrees, and the second threshold may be 60 degrees. [0056]In a specific embodiment, the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane. [0057]In an implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen. [0058]Alternatively, in another implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen. [0059]In another specific embodiment, the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane. [0060]In an implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen. [0061]Alternatively, in another implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen. [0062]Further, the method may further include acquiring ambient light intensity information of the mobile terminal, where the ambient light intensity information of the mobile terminal may be acquired using a light sensor. [0063]The determining an adjustment magnitude according to the tilt angle includes determining, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle. [0064]Further, the method may further include receiving angle range adjustment information; and adjusting at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information. [0065]Information about adjustment of an angle range may be received from a user. In this way, for a different user, a proper angle range may be configured for the different user according to an actual use habit or requirement of the different user, and the interface content layout of the mobile terminal screen may be adjusted according to the proper angle range. Such an adjustment can better meet the actual use habit or requirement of the user, and reduce an unnecessary adjustment of the interface content layout of the mobile terminal screen. [0066]Further, optionally, the method may further include recei(String), 相关申请的交叉引用 [0001] 本申请是2014年7月26日提交的国际专利申请号PCT/CN2014/083097的继续申请,其公开内容通过引用全部并入本文。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端屏幕显示的控制方法及移动终端。 背景 [0003] 目前,手机、平板等移动终端的功能不断丰富。 现在大部分智能移动终端只要移动终端的倾斜角度大于 特定的角度,然而,这往往会导致不必要的切换。 也就是说,虽然移动终端倾斜了特定的角度,但用户并不期望界面显示的切换。 因此,对屏幕显示的控制并不能完全满足用户的使用需求,从而降低了用户体验。 概括 [0004] 本发明实施例提供一种移动终端屏幕显示的控制方法及移动终端,以更好地满足用户的使用需求,提高用户体验。 [0005] 第一方面,本发明实施例提供了一种控制移动终端屏幕显示的方法,该方法包括获取移动终端当前的倾斜角度; 当确定当前倾斜角度处于第二或第三预设角度范围内时,根据倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。 [0006] 结合第一方面,在第一方面的第一种可能的实现方式中,所述根据倾斜角度调整移动终端屏幕的界面内容布局,包括根据倾斜角度确定调整幅度,调整全部或部分内容。 移动端屏幕部分界面内容根据调整幅度。 [0007] 结合第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,所述根据倾斜角度确定调整幅度,根据所述调整移动终端屏幕的全部或部分界面内容。 调整幅度包括根据倾斜角度确定调整距离,平移或浮动移动终端屏幕的全部或部分界面内容,平移或浮动的距离为调整距离。 或者,根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容以移动终端屏幕为中心旋转,旋转的角度即为调整角度。 [0008] 结合第一方面的第一种或第二种可能的实现方式,在第一方面的第三种可能的实现方式中,所述根据倾斜角度调整移动终端屏幕的界面内容布局,还包括根据倾斜角度确定调整方向。 倾斜角度,按照确定的调整方向调整移动终端屏幕的界面内容布局。 [0009] 结合第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中,所述根据倾斜角度确定调整方向包括:当当前倾斜角度在第二预设角度范围内时,确定 调整方向为第一方向; 或者,当当前倾斜角度处于第三预设角度范围内时,确定调整方向为第二方向。 [0010]结合第一方面的第三种或第四种可能的实现方式,在第一方面的第五种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或悬浮; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0011] 结合第一方面的第三种或第四种可能的实现方式,在第一方面的第六种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向为向下,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或悬浮。 [0012] 结合第一方面的第三种或第四种可能的实现方式,在第一方面的第七种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0013]结合第一方面的第三种或第四种可能的实现方式,在第一方面的第八种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动; 或者,如果移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0014] 结合第一方面的第一种可能的实现方式至第一方面的第八种可能的实现方式中的任一种,在第一方面的第九种可能的实现方式中,所述方法还包括获取移动终端的环境光强度信息。 ; 其中,根据倾斜角度确定调整幅度包括:根据环境光强度信息确定倾斜角度对应的调整幅度。 [0015] 结合第一方面或第一方面的第一种可能的实现方式至第一方面的第九种可能的实现方式中的任一种,在第一方面的第十种可能的实现方式中,所述方法还包括:接收角度范围调整信息 ; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0016] 第二方面,本发明实施例提供了一种控制移动终端屏幕显示的方法,该方法包括获取移动终端当前的倾斜角度; 当确定当前倾斜角度在第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围 . [0017] 第三方面,本发明实施例提供了一种移动终端,该移动终端包括传感器,用于获取移动终端当前的倾斜角度; 屏幕,用于在移动终端上显示界面内容; 处理器,用于在确定当前倾斜角度处于第二或第三预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。 [0018] 结合第三方面,在第三方面的第一种可能的实现方式中,所述处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,包括: 所述处理器,用于根据以下参数确定调整幅度: 倾斜角度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0019]结合第三方面的第一种可能的实现方式,在第三方面的第二种可能的实现方式中,所述处理器,用于根据倾斜角度确定调整幅度,调整所述界面的全部或部分内容。 根据调整幅度移动终端屏幕包括处理器,用于根据倾斜角度确定调整距离,平移或浮动移动终端屏幕的全部或部分界面内容,其中,平移或浮动的距离 为调整距离; 或者,处理器,用于根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容围绕移动终端屏幕的中心旋转,旋转的角度为调整角度 . [0020] 结合第三方面的第一种或第二种可能的实现方式,在第三方面的第三种可能的实现方式中,所述处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,还包括: 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0021] 结合第三方面的第三种可能的实现方式,在第三方面的第四种可能的实现方式中,所述处理器,用于根据所述倾斜角度确定调整方向,所述处理器用于,当当前倾斜角度为 处于第二预设角度范围内,确定调整方向为第一方向; 或者,当前倾斜角度在第三预设角度范围内时,确定调整方向为第二方向。 [0022] 结合第三方面的第三种或第四种可能的实现方式,在第三方面的第五种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0023]结合第三方面的第三种或第四种可能的实现方式,在第三方面的第六种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮。 [0024] 结合第三方面的第三种或第四种可能的实现方式,在第三方面的第七种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0025] 结合第三方面的第三种或第四种可能的实现方式,在第三方面的第八种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0026] 结合第三方面的第一种可能的实现方式至第三方面的第八种可能的实现方式中的任一种,在第三方面的第九种可能的实现方式中,所述传感器,还用于获取所述传感器的环境光强度信息。 移动终端; 处理器,用于根据倾斜角度确定调整幅度,包括处理器,用于根据环境光强度信息,确定倾斜角度对应的调整幅度。 [0027]结合第三方面或第三方面的第一种可能的实现方式至第三方面的第九种可能的实现方式中的任一种,在第三方面的第十种可能的实现方式中,所述处理器还用于接收角度范围 调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0028] 第四方面,本发明实施例提供了一种移动终端,该移动终端包括传感器,用于获取移动终端当前的倾斜角度; 屏幕,用于在移动终端上显示界面内容; 处理器,用于在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。 [0029] 本发明实施例提供的方法及移动终端,可以检测移动终端当前的倾斜角度; 仅在移动终端当前倾斜角度满足特定范围条件的情况下,例如当移动终端当前倾斜角度为 在第二或第三预设角度范围内; 或者,当移动终端的当前倾斜角度在第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局。 这样,避免了在移动终端倾斜特定角度但用户不希望进行屏幕显示调整的情况下进行屏幕显示调整,使得本控制移动终端屏幕显示的方法更好地满足了用户的使用需求。 用户并改善用户体验。 附图说明 [0030] 为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简要说明。 下面描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0031] 图1为本发明实施例的移动终端屏幕显示控制方法的流程图; [0032] 图2为本发明实施例提供的另一种移动终端屏幕显示控制方法的流程图; [0033] 图3A、图3B、图4A、图4B、图5A、图5B为本发明实施例的移动终端的倾斜角度示意图。 [0034] 图6、图7、图8、图9和图10为本发明实施例的移动终端屏幕显示控制方法的效果示意图; [0035] 图11、图12和图13为本发明实施例提供的另一种控制移动终端屏幕显示的方法的效果示意图; [0036] 图14为本发明实施例提供的移动终端的结构示意图; [0037] 图15为本发明实施例的移动终端的倾斜角度示意图; 和 [0038] 图16A、图16B、图16C、图16D、图16E、图16F和图16G为本发明实施例提供的另一种移动终端屏幕显示控制方法的效果示意图。 具体实施方式 [0039]下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0040] 本说明书中的术语“和/或”仅描述了描述关联对象的关联关系,表示可以存在三种关系。 例如,A和/或B可以表示以下三种情况:只有A存在,A和B都存在,只有B存在。 另外,本说明书中字符“/”一般表示关联对象之间的“或”关系。 实施例一 [0041] 如图1所示,在本发明移动终端屏幕显示控制方法的一个实施例中,该方法可以包括以下步骤。 [0042] 步 101 . 获取移动终端当前的倾斜角度。 [0043] 移动终端当前的倾斜角度可以通过重力传感器、陀螺仪等传感器检测获取。 [0044] 本发明中的移动终端可以是手机、平板电脑、个人数字助理(Personal Digital Assistant,PDA)等带有屏幕的移动终端设备,其中屏幕可以是触摸屏。 [0045] 步 102 . 当确定当前倾斜角度处于第二或第三预设角度范围内时,根据倾斜角度调整移动终端屏幕的界面内容布局。 [0046] 步 103 . 当确定移动终端当前的倾斜角度在第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局,即跳过调整移动终端屏幕当前显示的界面内容布局。 [0047] 第二、第一和第三预设角度范围依次形成连续的角度范围。 [0048] 进一步地,所述根据倾斜角度调整移动终端屏幕的界面内容布局包括根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0049] 进一步地,所述根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容包括:根据倾斜角度确定调整距离,平移或浮动全部或部分界面内容。 移动端屏幕的部分界面内容,其中平移或悬浮的距离为调整距离; 或者,根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容以移动终端屏幕为中心旋转,旋转的角度即为调整角度。 [0050] 进一步的,根据倾斜角度调整移动终端屏幕的界面内容布局还包括根据倾斜角度确定调整方向,在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0051] 进一步地,所述根据倾斜角度确定调整方向包括:当当前倾斜角度在第二预设角度范围内时,确定调整方向为第一方向; 或者,当当前倾斜角度处于第三预设角度范围内时,确定调整方向为第二方向。 [0052] 第一方向可以与第二方向相同,也可以不同,具体可以根据具体情况确定。 [0053] 进一步地,第一预设角度范围为大于等于第一阈值且小于等于第二阈值的角度范围,第一阈值小于第二阈值。 [0054]移动终端当前的倾斜角度可以为锐角或直角,第一阈值大于0度,第二阈值小于或等于90度。 [0055] 例如,第一阈值可以是30度,第二阈值可以是60度。 [0056] 在一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角。 [0057] 在一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值, 确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0058] 可选地,在另一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端的当前倾斜角度小于第一倾斜角度 阈值,确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或悬浮。 [0059] 在另一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角。 [0060] 在一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值, 确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0061] 可选地,在另一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端的当前倾斜角度小于第一倾斜角度 阈值,确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动; 或者,如果移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0062] 进一步地,该方法还可以包括获取移动终端的环境光强度信息,该移动终端的环境光强度信息可以通过光传感器获取。 [0063] 其中,根据倾斜角度确定调整幅度包括:根据环境光强度信息确定倾斜角度对应的调整幅度。 [0064]进一步地,该方法还可以包括:接收角度范围调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0065] 可以从用户接收关于角度范围调整的信息。 这样,对于不同的用户,可以根据不同用户的实际使用习惯或需求,为不同的用户配置合适的角度范围,并根据合适的角度调整移动终端屏幕的界面内容布局。 角度范围。 这样的调整可以更好地满足用户的实际使用习惯或需求,减少对移动终端屏幕界面内容布局的不必要的调整。 [0066] 进一步可选的,该方法还可以包括接收用户的反馈信息; 其中,根据倾斜角度确定调整幅度可以包括:根据反馈信息确定倾斜角度对应的调整幅度。 [0067] 例如,在调整移动终端屏幕的界面内容布局后,可以接收用户对本次调整的反馈。 例如,用户可以反馈调整大小是否过大或过小,以便根据用户的反馈信息配置调整大小。 [0068] 在本发明中,第一阈值和/或第二阈值可以是移动终端预先设置的,或者是用户设置的,或者是根据用户使用移动终端的情况统计得到的。 对于不同的用户,可以根据不同用户的使用习惯来确定第一阈值和/或第二阈值。 通常,当用户正常手持手机等移动终端时,手机不一定是完全水平或垂直的,而是倾斜一定的角度,手机与水平面和/或 一个垂直平面。 现有技术中,在重力传感器检测到手机不是水平或垂直的所有情况下,确定手机处于倾斜状态,以及当前显示在手机屏幕上的界面内容布局 被调整。 因此,虽然有时手机会倾斜特定角度,但用户是在正常使用手机,调整手机屏幕当前显示的界面内容会影响用户正常使用手机。 本发明通过重力传感器或陀螺仪检测手机当前的倾斜角度。 当手机当前倾斜角度处于用户手持手机的正常角度范围(本实施例中为第一预设角度范围)时,不调整手机屏幕当前显示的界面内容布局,即 更好的满足了用户使用手机的习惯,避免了对手机屏幕当前显示的界面内容布局进行不必要的调整,降低了手机的功耗,提升了手机的用户体验。 当手机当前的倾斜角度超出用户手持手机的正常角度范围(本实施例中为第二或第三预设角度范围)时,根据手机屏幕的界面内容布局进行调整 倾斜角度。 由于第一阈值和第二阈值与用户使用手机的习惯相关,本实施例能够为用户提供更加智能的调整手机屏幕界面内容布局的方法,提供更好的体验。 本公开基于用户使用手机的习惯。 [0069]在本实施例中,以手机为例,手机当前的倾斜角度在用户手持手机的正常角度范围之外,可以是手机当前的倾斜角度小于第一倾斜角度。 阈值或大于第二阈值。 即,手机当前的倾斜角度在用户手持手机的正常角度范围内可以是手机当前的倾斜角度大于或等于第一阈值且小于或等于 到第二个门槛。 [0070] 调整移动终端屏幕的界面内容布局可以包括:将移动终端屏幕的部分或全部界面内容在确定的方向上进行平移或浮动或旋转; 或者将特定区域的界面内容部分从隐藏状态变为显示状态,从显示状态变为隐藏状态等。 浮动可以是指将移动终端屏幕的界面内容中的一个或多个元素从界面上的原位置移动到新的位置,以方便用户操作。 进一步可选的,在用户操作完成后,或者在用户将手机的倾斜角度改变一定程度后,可以将一个或多个元素重新定位回原来的位置。 例如,浮动是指将移动终端屏幕的界面内容中的图标从原来的位置移动到界面上的新位置,以方便用户操作。 可选的,在用户操作完成后,可以将图标重新定位回原来的位置。 在用户看来,该图标似乎漂浮在界面上。 [0071] 本发明实施例将第一预设角度范围作为重力感应的基本水平面(相当于正常使用手机的场合),根据倾斜角度调整手机屏幕的界面内容布局 当手机当前的倾斜角度(例如图3A中手机与水平面的夹角γ)在第一预设角度范围之外时。 如图3A、图4A和图5A所示,图中灰色区域为第一预设角度范围。 [0072] α为第一预设角度范围内的最小角度,即用户正常使用手机时的最小角度,本实施例中的a为第一阈值。 在一个实施例中,a大于0度。 [0073] β为第一预设角度范围内的最大角度,即用户正常使用手机时的最大角度,本实施例中的β为第二阈值。 [0074] γ为手机右视图中手机与水平面的夹角(也可以理解为手机屏幕长度方向与水平面的夹角),本实施例中为 手机当前的倾斜角度。 本发明实施例仅以γ为锐角(或直角)为例进行说明。 也就是说,在本发明实施例中,γ值可以在大于0度且小于等于90度的范围内。 实际上,γ可以是钝角。 当γ为钝角时,参照γ为锐角(或直角)的情况,可作相同或相似的理解。 本发明实施例中,第一预设角度范围可以设置为大于0度且小于等于90度的范围(例如图3A中灰色区域所示的范围为第一预设角度 范围)。 [0075] μ是用户在使用手机的过程中手机可以承受的最小倾斜角度,μ可以大于等于0度,即如果手机倾斜角度小于这个 倾斜角度,用户无法正常查看手机屏幕的界面内容。 [0076] μ2为用户在使用手机的过程中手机最大可承受的倾斜角度,μ2可以小于或等于90度,即如果手机倾斜角度大于此 倾斜角度,用户无法正常查看手机屏幕的界面内容。 [0077] μ和μ2是可选的,以下与μ和μ2相关的内容也是可选的。 μ< a<β<μ 2. [0078] 在本发明实施例中,当手机当前倾斜角度γ在α和β之间时(如图3A所示)或者当手机当前倾斜角度等于α或β时,可以是 本发明实施例考虑到手机的倾斜角度在用户正常使用手机的范围内,手机屏幕的界面内容布局没有发生变化。 当手机的倾斜角度处于用户正常使用手机的范围内时,本发明实施例可以对手机的倾斜角度进行角度转换。 角度转换后(例如,当手机当前倾斜角度γ在α和β之间时,可以将当前倾斜角度γ转换为0度),则可以认为手机的重力感应状态为 平行于水平面(例如本发明实施例中手机倾斜角度在正常范围内时,进行角度转换后的重力感应状态,如图3B所示),而不会产生 重力感应组件,因此不调整手机屏幕的界面内容布局。 [0079] 当手机当前的倾斜角度γ小于α时(如图4A所示),本发明实施例可以认为手机的倾斜角度超出正常使用手机的范围 由用户使用,可能会影响用户正常使用手机。 这种情况下,需要调整手机屏幕的界面内容布局。 调整幅度可以通过以下方式获得。 可以根据手机当前的倾斜角度对倾斜角度进行角度转换处理,得到角度α-γ,并确定角度α-γ对应的调整幅度。 例如,调整幅度可以等于预设的调整系数×(α-γ)。 如图4B所示,虽然手机当前的倾斜角度实际为γ,但是本发明实施例中可以对当前的倾斜角度进行角度转换处理,根据角度α确定调整幅度。 -γ是经过角度转换处理后得到的,避免出现以下情况:当手机倾斜角度γ为α时不进行调整,而当γ略小于α时进行较大幅度的调整。 [0080] 当手机当前的倾斜角度γ大于β且小于μ2时(如图5A所示),本发明实施例可以认为手机的倾斜角度超出正常范围。 用户使用手机但在用户使用手机过程中不超过手机最大可承受倾斜角度。 在这种情况下,由于手机倾斜角度过大,可能会影响用户观看手机屏幕的视线,影响用户正常使用手机,影响用户使用体验。 手机受影响。 需要调整手机屏幕的界面内容布局。 调整幅度可以通过以下方式获得。 可以根据手机当前的倾斜角度对倾斜角度进行角度转换处理,得到角度γ-β,并确定角度γ-β对应的调整幅度。 如图5B所示,虽然手机当前的倾斜角度实际为γ,但是本发明实施例中可以对当前的倾斜角度进行角度转换处理,根据角度γ确定调整幅度。 -β是经过角度转换处理后得到的,以避免出现以下情况:当手机倾斜角度γ为β时不进行调整,而当γ略大于β时进行较大幅度的调整。 [0081]本发明各实施例均以仅以一个预设角度范围(本实施例中为第一预设角度范围)作为重力感应的基本水平面(相当于正常使用手机的场合)为例进行说明。 ,灰色区域为预设角度范围。 在多个预设角度范围作为重力感应的基本水平面的情况下(相当于正常使用手机的场合),如图15所示(显示两个预设角度范围:α1至β1,α2 至β2),可以参照以一个预设角度范围作为重力感应的基本水平面的情况的相关或相似内容来理解。 此时,可以理解为包括本发明实施例中的第一、第二、第三预设角度范围,第二、第一、第三预设角度范围依次形成一个连续的角度范围(例如, 一个连续的角度范围 0 到 α2); 角度范围α2至β2所指示的灰色区域可以理解为本发明实施例在本发明实施例的基础上进一步新增的第四预设角度范围。 [0082] 移动终端屏幕的界面内容部分可以是界面上的至少一个图标、按钮和/或图片等。 [0083] 根据反重力感应原理确定的方向与根据重力感应原理确定的调整方向相反。 反重力感应显示是将移动终端屏幕的全部或部分界面内容向与重力感应相反的方向平移或浮动(例如,根据重力感应原理,当手机向左倾斜时,界面内容 向左平移或悬浮;但根据反重力感应原理,当手机向左倾斜时,界面内容会向右平移或悬浮)。 [0084] 本发明实施例以第一预设角度范围作为重力感应的基本水平面。 当手机当前倾斜角度在第一预设角度范围内时,不启动重力/反重力感应显示,不调整手机屏幕的界面内容布局; 当手机当前倾斜角度大于第一预设角度范围的第二阈值时,若启动重力感应显示,则将手机屏幕的界面内容布局调整为向下/向右。 当手机当前的倾斜角度小于第一预设角度范围的第一阈值时,将手机屏幕的界面内容布局调整为向上/向左方向。 [0085] 如果开启反重力感应显示,则将手机屏幕的界面内容布局调整到与重力感应相反的方向。 [0086] 下面举例说明根据重力感应或反重力感应原理向上或向下平移手机屏幕的整个界面内容的情况。 图6至图10为同一界面内容在手机屏幕上的不同布局。 手机屏幕的界面内容布局可以参考以下方法进行调整。 [0087] (1)首先,利用重力传感器或陀螺仪检测手机在空间中的位置和角度,其中手机与水平面的夹角记为γ。 当然,也可以测量并记录手机与垂直面的夹角(大小可以为90-γ)。 [0088] (2)当γ在预设角度α和β之间时,手机屏幕界面内容布局显示不变,如图6所示。若手机与垂直面夹角90-γ为 测量并记录,可以理解当90-γ在预设角度90-β和90-α之间时,手机屏幕界面内容布局的显示没有变化,下面的描述也可以自适应理解 . [0089](3)当γ在α和β之间的范围之外时,可以启动反重力感应显示或重力感应显示。 即根据基本水平面,将移动终端屏幕的全部或部分界面内容的布局显示调整到与反重力感应或重力感应相同的方向。 [0090] (4)反重力感应显示规则至少包括以下步骤之一。 [0091] (a) 当γ小于a且大于μ时,反重力感应方向向下,手机屏幕界面内容在屏幕上向下偏移。 如图7所示,在屏幕上将手机屏幕的整个界面内容向下移动的过程中,将区域A中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户进行操作。 用户操作A区原本不方便触摸的界面内容。 [0092] (b)可选的,当γ小于或等于μ时,将手机屏幕的界面内容在屏幕上向下移动,直到到达极限位置。 如图8所示,区域A中的界面内容被完全移动到可触摸区域,使得用户更方便地操作区域A中原本不方便触摸的界面内容。当γ小于 或等于μ时,手机屏幕界面内容在屏幕上向下移动,直到到达极限位置,可以避免手机屏幕界面内容因连续减小而无限制移动而影响用户体验 的倾斜角度,进一步提高手机的智能性和易用性。 [0093] (c) 当γ小于μ2且大于β时,反重力感应方向向上,手机屏幕界面内容在屏幕上向上偏移。 如图9所示,将区域C中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户对区域C中原本不方便触摸的界面内容进行操作。 [0094] (d)可选的,当γ大于或等于μ2时,将手机屏幕的界面内容在屏幕上向上移动,直到到达极限位置。 如图10所示,区域C中的界面内容被完全移动到可触摸区域,使得用户更方便地操作区域C中原本不方便触摸的界面内容。当γ大于 或等于μ2时,手机屏幕界面内容在屏幕上向上移动,直到到达极限位置,可以避免手机屏幕界面内容连续增加导致的无限移动影响用户体验 的倾斜角度,进一步提高手机的智能性和易用性。 [0095] (五)重力感应展示规则至少包括以下一项: [0096] (a) 当γ小于a且大于μ时,重力感应方向向上,手机屏幕界面内容在屏幕上向上平移(或平移或浮动)。 如图9所示,将区域C中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户对区域C中原本不方便触摸的界面内容进行操作。 [0097] (b)可选的,当γ小于或等于μ时,将手机屏幕的界面内容在屏幕上向上移动,直到到达极限位置。 如图10所示,将C区的界面内容完全移至可触摸区,使得用户对C区原本不方便触摸的界面内容进行操作更加方便。 [0098](c) 当γ小于μ2且大于β时,重力感应方向向下,手机屏幕界面内容在屏幕上向下偏移。 如图7所示,在屏幕上将手机屏幕的整个界面内容向下移动的过程中,将区域A中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户的操作。 用户操作A区原本不方便触摸的界面内容。 [0099] (d)可选的,当γ大于或等于μ2时,将手机屏幕的界面内容在屏幕上向下移动,直到到达极限位置。 如图8所示,将A区的界面内容完全移至可触摸区,使得用户对A区原本不方便触摸的界面内容进行操作更加方便。 [0100] 用户在实际使用手机时,可以利用上述规则,根据需要操作的对象所在的区域倾斜手机,从而相应地调整手机屏幕的界面内容,满足操作需求。 用户的。 特别是当用户单手使用手机时,有些区域的物体有时单手难以触摸,可以利用上述规则将手机倾斜,从而相应地调整手机的界面内容 屏幕。 这样,将原本不能单手触摸的物体调整到可以触摸的位置,使得用户可以方便地单手操作该物体,更好地满足了用户的操作需求。 [0101] 上述规则同样适用于手机向左或向右倾斜时对手机屏幕的界面内容进行的调整处理。 手机向上或向下倾斜时所涉及的角度可以是手机屏幕的长度方向与水平面(或竖直面)之间的夹角,手机向左或向右倾斜时所涉及的角度可以是 手机屏幕的宽度方向与水平面(或垂直面)的夹角。 [0102] 在实施例一的基础上,可以根据倾斜角度确定调整角度,可以使移动终端屏幕的界面内容全部或部分以移动终端屏幕为中心旋转,旋转的角度为 调整角度。 进一步的,旋转方向可以根据倾斜角度确定,可以是顺时针方向,也可以是逆时针方向。 [0103]图11为手机屏幕正常显示的界面内容。 当用户在使用手机的过程中将手机倾斜到特定的角度,且手机当前的倾斜角度在预设的角度范围内时,不调整手机屏幕的界面内容布局, 如图12所示,当手机当前倾斜角度超出预设角度范围时,根据重力感应检测到的当前倾斜角度旋转手机屏幕的全部或部分界面内容。 手机(如图13旋转效果示意图)。 旋转的程度或角度与倾斜角度有关。 例如,可以通过预设的算法或公式得到倾斜角度对应的调整幅度(此处为旋转的角度)。 在本发明实施例中,根据手机的倾斜角度,对手机屏幕的界面内容进行全部或部分的旋转。 旋转的角度与倾斜角度相关,并不是每次都以固定的角度在横向和纵向之间切换屏幕(可以理解为固定旋转90度)。 因此,可以更好地满足用户的不同需求。 例如,用户可以更方便地以不同的视角观看手机屏幕的界面内容。 另外,还可以对旋转后的界面内容进行进一步调整,例如将旋转后的界面内容放大或缩小,使人眼看到的界面内容区域为矩形,提供更好的观看效果。 [0104] 下面举例说明如何根据倾斜角度旋转移动终端屏幕的全部或部分界面内容。 [0105] 当手机正常使用时(例如手机当前的倾斜角度在预设范围内时),手机屏幕的界面内容如图16A所示,为横向显示。 当手机当前的倾斜角度如图5A所示时,手机屏幕的界面内容可以逆时针旋转(如图16B和图16C所示,箭头表示旋转方向)。 随着倾斜角度的不断增大,当倾斜角度达到最大倾斜角度(例如μ2)时,手机屏幕的界面内容在旋转后变为垂直显示(如图16D所示)。 当手机当前的倾斜角度如图4A所示时,手机屏幕的界面内容可以顺时针旋转(如图16E和图16F所示)。 随着倾斜角度的不断减小,当倾斜角度达到最小倾斜角度(例如μ)时,手机屏幕的界面内容在旋转后变成倒置显示(如图16G所示)。 实施例二 [0106] 如图2所示,在本发明移动终端屏幕显示控制方法的另一实施例中,该方法包括以下步骤。 [0107] 步 101 . 获取移动终端当前的倾斜角度。 [0108] 步 202 . 在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局。 [0109] 步 203 . 在确定移动终端当前倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕已有的界面内容布局。 第二、第一和第三预设角度范围依次形成连续的角度范围。 [0110] 进一步地,所述根据倾斜角度调整移动终端屏幕的界面内容布局包括根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0111]进一步地,所述根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容包括:根据倾斜角度确定调整距离,平移或浮动全部或部分界面内容。 移动端屏幕的部分界面内容,其中平移或悬浮的距离为调整距离; 或者,根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容以移动终端屏幕为中心旋转,旋转的角度即为调整角度。 [0112] 进一步的,根据倾斜角度调整移动终端屏幕的界面内容布局还包括根据倾斜角度确定调整方向,在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0113] 进一步地,第一预设角度范围为大于等于第一阈值且小于等于第二阈值的角度范围,第一阈值小于第二阈值。 [0114] 移动终端当前的倾斜角度可以为锐角或直角,第一阈值大于0度,第二阈值小于或等于90度。 [0115] 例如,第一阈值可以是30度,第二阈值可以是60度。 [0116] 在本实施例中,手机当前的倾斜角度在用户手持手机的正常角度范围之外可以是手机当前的倾斜角度在第一阈值和第二阈值之间。 即,手机当前倾斜角度处于用户手持手机的正常角度范围内,可以是手机当前倾斜角度小于第一阈值或大于第二阈值。 [0117] 进一步地,该方法还可以包括获取移动终端的环境光强度信息,该移动终端的环境光强度信息可以通过光传感器获取。 [0118] 其中,根据倾斜角度确定调整幅度包括:根据环境光强度信息确定倾斜角度对应的调整幅度。 [0119] 进一步地,该方法还可以包括:接收角度范围调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0120] 可以从用户接收关于角度范围调整的信息。 这样,对于不同的用户,可以根据不同用户的实际使用习惯或需求,为不同的用户配置合适的角度范围,并根据合适的角度调整移动终端屏幕的界面内容布局。 角度范围。 这样的调整可以更好地满足用户的实际使用习惯或需求,减少对移动终端屏幕界面内容布局的不必要的调整。 [0121] 进一步可选的,该方法还可以包括接收用户的反馈信息; 其中,根据倾斜角度确定调整幅度可以包括:根据反馈信息确定倾斜角度对应的调整幅度。 [0122] 例如,在调整移动终端屏幕的界面内容布局后,可以接收用户对本次调整的反馈。 例如,用户可以反馈调整大小是否过大或过小,以便根据用户的反馈信息配置调整大小。 [0123]在本发明中,第一阈值和/或第二阈值可以是移动终端预先设置的,或者是用户设置的,或者是根据用户使用移动终端的情况统计得到的。 对于不同的用户,可以根据不同用户的使用习惯来确定第一阈值和/或第二阈值。 通常,当用户正常手持手机等移动终端时,手机不一定是完全水平或垂直的,而是倾斜一定的角度,手机与水平面和/或 一个垂直平面。 现有技术中,在重力传感器检测到手机不是水平或垂直的所有情况下,确定手机处于倾斜状态,以及当前显示在手机屏幕上的界面内容布局 被调整。 因此,虽然有时手机会倾斜特定角度,但用户是在正常使用手机,调整手机屏幕当前显示的界面内容会影响用户正常使用手机。 本发明通过重力传感器或陀螺仪检测手机当前的倾斜角度。 当手机当前倾斜角度处于用户手持手机的正常角度范围(本实施例中为第二或第三预设角度范围)时,不调整手机屏幕当前显示的界面内容布局 ,更符合用户使用手机的习惯,避免了对手机屏幕当前显示的界面内容布局进行不必要的调整,降低了手机的功耗,提升了手机的用户体验。 当手机当前的倾斜角度超出用户手持手机的正常角度范围(本实施例中为第一预设角度范围)时,根据倾斜度调整手机屏幕的界面内容布局 角度。 由于第一阈值和第二阈值与用户使用手机的习惯相关,本实施例能够为用户提供更加智能的调整手机屏幕界面内容布局的方法,提供更好的体验。 本公开基于用户使用手机的习惯。 [0124] 本发明实施例中的第一、第二或第三预设角度范围可以与实施例一中的第一、第二或第三预设角度范围相同或不同。 [0125] 本发明实施例中的部分内容可以参见实施例一中的相关部分,这些内容可以有相同或相近的理解,在此不再赘述。 实施例3 [0126] 本发明实施例还提供了一种移动终端。 图14示出了本发明提供的移动终端的一个实施例。 本实施例中,移动终端包括传感器 1401 用于获取移动终端当前的倾斜角度,其中传感器 1401 可以是一个或多个具有相同功能或不同功能的传感器,可以包括重力传感器或陀螺仪传感器,进一步可选地,可以包括光传感器等; 屏幕 1402 用于在移动终端上显示界面内容; 和一个处理器 1403 用于在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。 [0127] 或者,在另一个实施例-实施例4中,处理器 1403用于在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。 [0128] 可能有一个或多个处理器 1403 例如,可以包括图像处理器。 [0129] 进一步地,移动终端还可以包括存储器 1407 用于存储各种数据或指令,还可以包括接收器 1405 和一个发射器 1406 分别用于接收和发送信号。 [0130] 基于实施例三或四,进一步地,处理器 1403 用于根据倾斜角度调整移动终端屏幕的界面内容布局,包括处理器 1403 具体用于根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0131] 基于实施例三或四,进一步地,处理器 1403 用于根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容,包括处理器 1403 用于根据倾斜角度确定调整距离,平移或浮动移动终端屏幕的全部或部分界面内容,平移或浮动的距离为调整距离。 或处理器 1403 用于根据倾斜角度确定调整角度,将移动终端屏幕的界面内容全部或部分以移动终端屏幕为中心旋转,旋转的角度为调整角度。 [0132] 基于实施例三或四,进一步地,处理器 1403 用于根据倾斜角度调整移动终端屏幕的界面内容布局还包括处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0133] 基于实施例三或四,进一步的,所述第一预设角度范围为大于等于第一阈值且小于等于第二阈值的角度范围,所述第一阈值小于第二阈值。 [0134] 移动终端当前的倾斜角度可以为锐角或直角,第一阈值大于0度,第二阈值小于或等于90度。 [0135] 例如,第一阈值可以是30度,第二阈值可以是60度。 [0136] 在实施例三的基础上,进一步地,处理器 1403 处理器用于根据倾斜角度确定调整方向,当当前倾斜角度处于第二预设角度范围内时,确定调整方向为第一方向。 或者,当前倾斜角度在第三预设角度范围内时,确定调整方向为第二方向。 [0137] 基于实施例三,在一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角。 [0138] 在一种实现方式中,处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403用于若移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上平移或向上浮动。 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0139] 或者, 在另一种实现方式中, 处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403 用于如果移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮。 [0140] 基于实施例三,在另一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角。 [0141] 在一种实现方式中,处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403 用于如果移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0142] 或者, 在另一种实现方式中, 处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403 用于若移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0143] 在实施例3或4的基础上,进一步地,传感器 1401 还用于获取移动终端的环境光强度信息; 和处理器 1401 被配置为根据倾斜角度确定调整幅度包括处理器 1401 用于根据环境光强度信息确定倾斜角度对应的调整幅度。 [0144] 基于实施例三或四,进一步地,处理器 1403 还用于接收角度范围调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0145] 需要说明的是,各个装置实施例可以参见对应的方法实施例中的内容,在此不再赘述,方法实施例之间相同或相似的内容互相参见即可 此处不再详述。 [0146]需要说明的是,在本说明书中,第一、第二等关系术语仅用于区分一个实体或操作与另一个实体或操作,并不一定要求或暗示这些实体或操作之间存在任何实际关系或顺序 . 此外,术语“包括”、“包含”或它们的任何其他变体旨在涵盖非排他性的包含,因此包括元素列表的过程、方法、物品或装置不仅包括 这些元素,但也包括未明确列出的其他元素,或进一步包括此类过程、方法、物品或设备固有的元素。 前面带有“的元素包括一个 . . . ” 在没有更多限制的情况下,不排除在包含该元素的过程、方法、物品或设备中存在其他相同元素。 [0147] 本领域普通技术人员可以理解,上述任一实施例所规定的方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在移动终端的闪存或电可擦除可编程只读存储器(EEPROM)等可读取存储介质中。 当程序运行时,程序执行上述全部或部分步骤。 [0148] 在上述具体实施方式中,进一步详细说明了本发明的目的、技术方案和有益效果。 应当理解,可以组合不同的实施例。 以上所述仅为本发明的具体实施方式,并非用于限定本发明的保护范围。 凡在不脱离本发明的精神和原则的情况下,所作的任何组合、修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.626 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104756059A(String), EP3166289A1(String), EP3166289A4(String), KR1020170023198A(String), US20170131793A1(String), WO2016015183A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104756059A(String), EP3166289A1(String), EP3166289A4(String), KR1020170023198A(String), US20170131793A1(String), WO2016015183A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20170131793A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.636 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104756059A(String), EP3166289A1(String), EP3166289A4(String), KR1020170023198A(String), US20170131793A1(String), WO2016015183A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.640 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270679(Integer), CN104756059A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270679(Integer), EP3166289A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270679(Integer), EP3166289A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270679(Integer), KR1020170023198A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270679(Integer), US20170131793A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270679(Integer), WO2016015183A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20170131793A1(String), US20170131793A1(String), 1494432000(Integer), 270679(Integer), 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.730 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.731 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.731 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185000(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185000(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.746 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.750 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185000(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185000(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.774 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.787 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160192162A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Transferring Call on Mobile Terminal, and Mobile Terminal(String), 移动终端呼叫转移的方法及移动终端(String), US20160192162A1(String), A method for transferring a call in a mobile terminal and a mobile terminal thereof, wherein the method includes: a mobile terminal controlling its two communication cards to respectively establish a first call connection and a second call connection; when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection; the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink call connection of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 一种移动终端中呼叫转移的方法及移动终端,该方法包括:移动终端控制其两张通信卡分别建立第一呼叫连接和第二呼叫连接; 移动终端在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行呼叫连接,并屏蔽音频 移动终端中的数据输入/输出单元。(String), US14/910685(String), 1396540800(Integer), US20160192162A1(String), 1467216000(Integer), 美国(String), 2(Integer), CN(String), 3(Integer), 2(Integer), US6606305B1 | US9002364B2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185001(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e4ba55c446ea4d78bc4f64f51defc42d.png(String), 185001(Integer), e4ba55c446ea4d78bc4f64f51defc42d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Transferring Call on Mobile Terminal, and Mobile Terminal(String), 移动终端呼叫转移的方法及移动终端(String), US20160192162A1(String), A method for transferring a call in a mobile terminal and a mobile terminal thereof, wherein the method includes: a mobile terminal controlling its two communication cards to respectively establish a first call connection and a second call connection; when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection; the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink call connection of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 一种移动终端中呼叫转移的方法及移动终端,该方法包括:移动终端控制其两张通信卡分别建立第一呼叫连接和第二呼叫连接; 移动终端在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行呼叫连接,并屏蔽音频 移动终端中的数据输入/输出单元。(String), US14/910685(String), 1396540800(Integer), US20160192162A1(String), 1467216000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 3(Integer), 2(Integer), US6606305B1 | US9002364B2(String), \20230420\e4ba55c446ea4d78bc4f64f51defc42d.png(String), 12(Integer), 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.830 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 1. A method for transferring a call in a mobile terminal, comprising:a mobile terminal controlling two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection;when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection;the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 1.如权利要求2所述的方法,其中,在移动终端控制移动终端的两个通信卡分别建立第一呼叫连接和第二呼叫连接之后,该方法还包括:移动终端接收到用户通过本终端发送的终止通话指令后,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接;或者当第一呼叫连接终止时,移动终端控制第二呼叫连接断开,或者当第二呼叫连接终止时,移动终端控制第一呼叫连接断开。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 2. The method of claim 1, wherein, before obtaining the downlink channel data of the first call connection and the second call connection, a call state corresponding to the first call connection is a call hold state, a call state corresponding to the second call connection is a call activated state.(String), 12.如权利要求5所述的方法,其中,在控制移动终端的第二通信卡建立第二呼叫连接之后,该方法还包括:移动终端接收到用户通过本终端发送的终止通话指令后,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接;或者移动终端在第一呼叫连接终止时控制断开第二呼叫连接,或者在第二呼叫连接断开时控制第一呼叫连接断开。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 3. The method of claim 1 or 2, wherein, after the mobile terminal controls two communication cards of the mobile terminal to respectively establish the first call connection and the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orwhen the first call connection is terminated, the mobile terminal controlling the second call connection to be disconnected, or when the second call connection is terminated, the mobile terminal controlling the first call connection to be disconnected.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 4. A method for transferring a call in a mobile terminal, comprising:a mobile terminal controlling a first communication card of the mobile terminal to establish a first call connection;when receiving a call transferring instruction, the mobile terminal controlling a second communication card of the mobile terminal to establish a second call connection and obtaining downlink channel data of the first call connection and the second call connection;the mobile terminal taking the obtained downlink channel data of the first call connection as uplink data channel of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 5. The method of claim 4, wherein, before obtaining the downlink channel data of the first call connection and the second call connection, a call state corresponding to the first call connection and a call state corresponding to the second call connection are call activated states.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 6. The method of claim 4, wherein, after controlling the second communication card of the mobile terminal to establish the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orthe mobile terminal controlling the second call connection to be disconnected when the first call connection is terminated, or controlling the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 7. A mobile terminal for transferring a call in the mobile terminal, comprising:a controlling module, configured to: control two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection;an obtaining module, configured to: upon receiving a call transferring instruction, obtain downlink channel data of the first call connection and the second call connection;a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield an audio data input/output unit in the mobile terminal.(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 8. The mobile terminal of claim 7, wherein, the controlling module is further configured to:upon receiving a call termination instruction sent by a user through a present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orcontrol the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 9. A mobile terminal for transferring a call in the mobile terminal, comprising:a controlling module, configured to: control a first communication card of the mobile terminal to establish a first call connection; and further configured to: control a second communication card of the mobile terminal to establish a second call connection upon receiving a call transferring instruction;an obtaining module, configured to: obtain downlink channel data of the first call connection and the second call connection;a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield an audio data input/output unit in the mobile terminal.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 10. The mobile terminal of claim 9, wherein, the controlling module is further configured to:upon receiving a call termination instruction sent by a user through a present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orcontrol the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 11. The method of claim 2, wherein, after the mobile terminal controls two communication cards of the mobile terminal to respectively establish the first call connection and the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orwhen the first call connection is terminated, the mobile terminal controlling the second call connection to be disconnected, or when the second call connection is terminated, the mobile terminal controlling the first call connection to be disconnected.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185001(Integer), 12. The method of claim 5, wherein, after controlling the second communication card of the mobile terminal to establish the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orthe mobile terminal controlling the second call connection to be disconnected when the first call connection is terminated, or controlling the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 11(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185001(Integer), TECHNICAL FIELD [0001]The present document relates to the field of communication technologies, and more particularly, to a method for transferring a call on a mobile terminal and a mobile terminal thereof. BACKGROUND OF THE RELATED ART [0002]Although a related dual-card dual-standby dual-pass mobile terminal can achieve a three-party call under two communication cards, when two parties want to talk directly during the call, they must hang up and then call each other directly to talk with each other directly. For example, Xiao Wang establishes a call connection with Xiao Hong via a first communication card, and also establishes a call connection with Xiao Ming via a second communication card, and if Xiao Hong and Xiao Ming want to chat with each other, they can only do so by respectively hanging up the call connections with Xiao Wang and redial each other's phone number to chat, and when the Xiao Hong and Xiao Ming don't hang up the call connections with Xiao Wang respectively, the call of the Xiao Hong and Xiao Ming cannot be directly transferred by Xiao Wang to implement the direct call between the Xiao Hong and Xiao Ming. Also, if Xiao Hong is looking for Xiao Ming through the first card, the terminal may directly dial Xiao Ming's phone number through the second card and directly transfer the call to Xiao Hong without disclosing the Xiao Ming's phone number or hanging up the call. With the increasing number of dual-card dual-standby dual-pass terminals, this call transferring function will become the urgent needs of the users. SUMMARY OF THE INVENTION [0003]The embodiment of the present document is to provide a method for transferring a call on a mobile terminal and the mobile terminal thereof to address the defects that the call transferring function cannot be achieved in an existing mobile terminal. [0004]The embodiment of the present document provides a method for transferring a call in a mobile terminal, comprising: a mobile terminal controlling its two communication cards to respectively establish a first call connection and a second call connection; when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection; [0005]the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal. [0006]Preferably, before obtaining the downlink channel data of the first call connection and the second call connection, a call state corresponding to the first call connection is a call hold state, a call state corresponding to the second call connection is a call activated state. [0007]Preferably, after the mobile terminal controls its two communication cards to respectively establish the first call connection and the second call connection, the method further comprises: upon receiving a call termination instruction sent by a user through the present terminal, the mobile terminal controlling its two communication cards to disconnect the established first call connection and second call connection; or when the first call connection is terminated, the mobile terminal controlling the second call connection to be disconnected, or when the second call connection is terminated, the mobile terminal controlling the first call connection to be disconnected. [0008]A method for transferring a call in a mobile terminal, comprising: a mobile terminal controlling its first communication card to establish a first call connection; when receiving a call transferring instruction, the mobile terminal controlling its second communication card to establish a second call connection and obtaining downlink channel data of the first call connection and the second call connection; the mobile terminal taking the obtained downlink channel data of the first call connection as uplink data channel of the second call connection, and taking the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal. [0009]Preferably, before obtaining the downlink channel data of the first call connection and the second call connection, the call state corresponding to the first call connection and the call state corresponding to the second call connection are the call activated state. [0010]Preferably, after controlling its second communication card to establish the second call connection, the method further comprises: upon receiving a call termination instruction sent by the user through the present terminal, the mobile terminal controlling its two communication cards to disconnect the established first call connection and second call connection; or the mobile terminal controlling the second call connection to be disconnected when the first call connection is terminated, or controlling the first call connection to be disconnected when the second call connection is terminated. [0011]The embodiment of the present document further provides a mobile terminal for transferring a call in the mobile terminal, comprising: [0012]a controlling module, configured to: control two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection; an obtaining module, configured to: upon receiving a call transferring instruction, obtain downlink channel data of the first call connection and the second call connection; a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield an audio data input/output unit in the mobile terminal. [0013]Preferably, the controlling module is further configured to: upon receiving a call termination instruction sent by the user through the present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; or control the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated. [0014]A mobile terminal for transferring a call in the mobile terminal, comprising: a controlling module, configured to: control first communication card of the mobile terminal to establish a first call connection, and further configured to: control second communication card of the mobile terminal to establish a second call connection upon receiving a call transferring instruction; an obtaining module, configured to: obtain downlink channel data of the first call connection and the second call connection; a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield the audio data input/output unit in the mobile terminal. [0015]Preferably, the controlling module is further configured to: upon receiving a call termination instruction sent by a user through the present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; or [0016]control the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated. [0017]The embodiment of the present document can directly perform a call connection on the opposite-end calls through a call transferring method without hanging up the current call connections when two communication cards respectively establish call connections according to user demands, so as to easily, simply and quickly implement the call transferring function in a mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0018]FIG. 1 is a flow chart of an embodiment of a method for transferring a call in a mobile terminal in accordance with an embodiment of the present document; [0019]FIG. 2 is a flow chart of another embodiment of the method for transferring a call in a mobile terminal in accordance with an embodiment of the present document; [0020]FIG. 3 is a functional block diagram of an embodiment of a mobile terminal for transferring a call in a mobile terminal in accordance with an embodiment of the present document; [0021]FIG. 4 is a functional block diagram of another embodiment of the mobile terminal for transferring a call in a mobile terminal in accordance with an embodiment of the present document. PREFERRED EMBODIMENTS OF THE INVENTION [0022]Hereinafter, in conjunction with the accompanying drawings and embodiments, the technical solution of the present document will be further described. It should be understood that the specific embodiments described herein are only intended to explain rather than limit the present document. [0023]FIG. 1 shows a flow chart of an embodiment of the method for transferring a call in a mobile terminal in accordance with an embodiment of the present document. [0024]It should be emphasized that: the flow chart shown in FIG. 1 is only a preferred embodiment, and those skilled in the art should know that any embodiments constructed within the thoughts of the present document should not be departed from the scope covered in the following technical solution: [0025]the method for transferring a call in a mobile terminal provided in the present embodiment comprises: [0026]in step S10, the mobile terminal controls its two communication cards to respectively establish a first call connection and a second call connection; [0027]In the present embodiment, the two communication cards may belong to the same network standard, which can be any one of GSM (Global System Of Mobile Communication), WCDMA (Wideband Code Division Multiple Access), CDMA (Code division Multiple Access), TD-SCDMA (Time division-synchronous Code division Multiple Access) and LTE (long Term Evolution), or may respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the mobile terminal establishes a first call connection through the GSM network standard of the first communication card and establishes a second call connection through the CDMA network standard of the second communication card, or the mobile terminal establishes a first call connection through the GSM network standard of the first communication card, and establishes a second call connection through the GSM network standard of the second communication card. [0028]In step S20, upon receiving a call transferring instruction, the mobile terminal obtains downlink channel data of the first call connection and the second call connection; [0029]upon receiving the call transferring instruction, the mobile terminal has already established two call connections through the two communication cards. The call state corresponding to the first call connection is the call hold state, that is, call waiting state, the call state corresponding to the second call connection is the call activated state, that is, normal call state. According to the user needs, it may also switch between these two states. For example, when the user wants to switch from the call of the second call connection to the first call connection, it transmits a Retrieve instruction to the network side of the first communication card and transmits a Hold instruction to the network side of the second communication card, to retrieve the first call connection of the first communication card; of course, the user can also switch the call of the first call connection to the second call connection, the processing procedure is the same and is not repeated here. [0030]After receiving the call transferring instruction, it sends a Retrieve instruction to the corresponding first communication card or second communication card to enable the first communication card or the second communication card to stay in the call activated state, that is, the normal call state. The mobile terminal obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card. [0031]In step S30, the mobile terminal takes the obtained downlink channel data of the first call connection as the uplink channel data of the second call connection, and takes the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shields the audio data input/output unit in the mobile terminal. [0032]In the GSM and CDMA network standards, for example, the mobile terminal controls its two communication cards to establish the first call connection and the second call connection respectively through the GSM and CDMA networks, upon receiving a call transferring instruction, the mobile terminal takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0033]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0034]Preferably, in the call transferring process, when the mobile terminal receives a call termination instruction sent by the user through the present terminal, the mobile terminal controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the mobile terminal controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the mobile terminal controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0035]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0036]The present embodiment can directly perform a call connection on the opposite-end calls through a call transferring method without hanging up the current call connections when two communication cards respectively establish call connections according to user demands, so as to easily, simply and quickly implement the call transferring function in a mobile terminal. [0037]FIG. 2 shows a flow chart of another embodiment of the method for transferring a call in a mobile terminal in accordance with an embodiment of the present document. [0038]It should be emphasized that: the flow chart shown in FIG. 2 is only a preferred embodiment, and those skilled in the art should know that any embodiments constructed within the thoughts of the present document should not be departed from the scope covered in the following technical solution: [0039]The method for transferring a call in a mobile terminal provided in the present embodiment comprises: [0040]in step S110, the mobile terminal controls its first communication card to establish a first call connection; [0041]in step S120, the mobile terminal controls its second communication card to establish a second call connection when receiving a call transferring instruction, and obtains the downlink channel data of the first call connection and the second call connection; [0042]in the present embodiment, the first communication card and the second communication card may belong to the same network standard, which can be any one of GSM (Global System Of Mobile Communication), WCDMA (Wideband Code Division Multiple Access), CDMA (Code division Multiple Access), TD-SCDMA (Time division-synchronous Code division Multiple Access) and LTE (long Term Evolution), or respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the mobile terminal establishes a first call connection through the GSM network standard of the first communication card and the mobile terminal establishes a second call connection through the CDMA network standard of the second communication card when receiving a call transferring instruction, or the mobile terminal establishes a first call connection through the GSM network standard of the first communication card, and the mobile terminal establishes a second call connection through the GSM network standard of the second communication card when receiving a call transferring instruction. [0043]The mobile terminal controls its first communication card to establish a first call connection; upon receiving the call transferring instruction, the mobile terminal controls its second communication card to establish a second call connection. In this case the mobile terminal has already established two call connections through the first communication card and the second communication card respectively. The call state corresponding to the first call connection and the call state corresponding to the second call connection are the call activated state, that is, the normal call state. [0044]When the mobile terminal controls its second communication card to establish the second call connection, the mobile terminal obtains the downlink channel data of the first call connection established through the first communication card as well as the downlink channel data of the second call connection established through the second communication card. [0045]In step S130, the mobile terminal takes the obtained downlink channel data of the first call connection as the uplink channel data of the second call connection and the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shields the audio data input/output unit in the mobile terminal. [0046]In the GSM and CDMA network standards, for example, the mobile terminal controls its first communication card to establish the first call connection through the GSM network, and controls its second communication card to establish the second call connection through the CDMA network when receiving a call transferring instruction, and it obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card; the mobile terminal takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0047]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0048]Furthermore, in the call transferring process, when the mobile terminal receives a call termination instruction sent by the user through the present terminal, the mobile terminal controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the mobile terminal controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the mobile terminal controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0049]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0050]FIG. 3 shows a functional block diagram of an embodiment of the mobile terminal for transferring a call in a mobile terminal in accordance with the present document. The mobile terminal 1 provided in the present embodiment comprises: [0051]a controlling module 10, used to control two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection; [0052]In the present embodiment, the two communication cards may belong to the same network standard, which can be any one of GSM, WCDMA, CDMA, TD-SCDMA and LTE, or respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the controlling module 10 establishes a first call connection through the GSM network standard of the first communication card and establishes a second call connection through the CDMA network standard of the second communication card, or the controlling module 10 establishes the first call connection through the GSM network standard of the first communication card, and establishes the second call connection through the GSM network standard of the second communication card. [0053]An obtaining module 20 is configured to, upon receiving a call transferring instruction, obtain downlink channel data of the first call connection and the second call connection; [0054]upon receiving the call transferring instruction, the controlling module 10 has already established two call connections through the two communication cards. The call state corresponding to the first call connection is the call hold state, that is, the call waiting state, and the call state corresponding to the second call connection is the call activated state, that is, the normal call state. According to the user needs, it can also switch between these two states. For example, when the user wants to switch from the call of the second call connection to the first call connection, it transmits a Retrieve instruction to the network side of the first communication card and transmits a Hold instruction to the network side of the second communication card to retrieve the first call connection of the first communication card; of course, the user can also switch the call of the first call connection to the second call connection, the processing procedure is same and is not repeated here. [0055]After receiving the call transferring instruction, it is to send a Retrieve instruction to the corresponding first communication card or second communication card to enable the first communication card or second communication card to stay in the call activated state, that is the normal call state. The obtaining module 20 obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card. [0056]A processing module 30 is configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection and the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shield the audio data input/output unit in the mobile terminal. [0057]In the GSM and CDMA network standards, for example, the controlling module 10 controls two communication cards of the mobile terminal to respectively establish the first call connection and the second call connection through the GSM and CDMA networks, and upon receiving a call transferring instruction, the processing module 30 takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0058]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0059]Preferably, in the call transferring process, when the controlling module 10 receives a call termination instruction sent by the user through the present terminal, the controlling module 10 controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the controlling module 10 controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the controlling module 10 controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0060]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0061]The embodiment of the present document can directly perform a call connection on the opposite-end calls through a call transferring method without hanging up the current call connections when two communication cards respectively establish call connections according to user demands, so as to easily, simply and quickly implement the call transferring function in a mobile terminal. [0062]FIG. 4 shows a functional block diagram of another embodiment of the mobile terminal for transferring a call in a mobile terminal in accordance with an embodiment of the present document. The mobile terminal 2 provided in the present embodiment comprises: [0063]a controlling module 110, configured to: control a first communication card of the mobile terminal to establish a first call connection; and also used to control a second communication card of the mobile terminal to establish a second call connection when receiving a call transferring instruction, [0064]an obtaining module 120, configured to: obtain downlink channel data of the first call connection and the second call connection;[0065]in the present embodiment, the first communication card and the second communication card may belong to the same network standard, which can be any one of GSM, WCDMA, CDMA, TD-SCDMA and LTE, or respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the controlling module 110 establishes a first call connection through the GSM network standard of the first communication card, and the controlling module 110 establishes a second call connection through the CDMA network standard of the second communication card when receiving a call transferring instruction, or the controlling module 110 establishes the first call connection through the GSM network standard of the first communication card, and the controlling module 110 establishes the second call connection through the GSM network standard of the second communication card when receiving a call transferring instruction. [0066]The controlling module 110 controls the first communication card of the mobile terminal to establish a first call connection; upon receiving a call transferring instruction, the controlling module 110 controls the second communication card of the mobile terminal to establish a second call connection. In this case the controlling module 110 has already established two call connections through the first communication card and the second communication card respectively. The call state corresponding to the first call connection and the call state corresponding to the second call connection are the call activated state, that is, the normal call state. [0067]When the controlling module 110 controls the second communication card of the mobile terminal to establish the second call connection, the obtaining module 120 obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card. [0068]A processing module 130 is configured to: take the obtained downlink channel data of the first call connection as the uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shield the audio data input/output unit in the mobile terminal. [0069]In the GSM and CDMA network standards, for example, the controlling module 110 controls its first communication card to establish the first call connection through the GSM network, and the controlling module 110 controls its second communication card to establish the second call connection through the CDMA network, and the obtaining module 120 obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card; the processing module 130 takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0070]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0071]Preferably, in the call transferring process, when the controlling module 110 receives a call termination instruction sent by the user through the present terminal, the controlling module 110 controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the controlling module 10 controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the controlling module 10 controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0072]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0073]The above description is preferred embodiments of the present document and is not intended to limit the patent scope of the embodiments of the present document, any equivalent structure transformations made by using the contents of the specification and the accompanying drawings of the present document, or directly or indirectly used in other related technical fields, should similarly be included in the patent protection scope of the embodiments of the present document. INDUSTRIAL APPLICABILITY [0074]The embodiment of the present document can directly perform(String), 技术领域 [0001] 本 发明涉及通信技术领域,尤其涉及一种移动终端呼叫转移的方法及移动终端。 相关技术背景 [0002] 虽然相关的双卡双待双通移动终端可以实现两张通讯卡下的三方通话,但是当通话中双方想直接通话时,必须先挂机再直接呼叫对方通话。 直接互相 例如,小王通过第一通讯卡与小红建立通话连接,也通过第二通讯卡与小明建立通话连接,如果小红和小明要聊天,只能 分别挂断与小王的通话连接并重拨对方的电话号码进行聊天,当小红和小明分别没有挂断与小王的通话连接时,小红和小明的通话 小王不能直接调用小明实现小红和小明之间的直接通话。 另外,如果小红通过第一张卡寻找小明,则终端可以通过第二张卡直接拨打小明的电话号码,直接将电话转给小红,而不会泄露小明的电话号码,也不会挂断电话。 随着双卡双待双通终端越来越多,这种呼叫转移功能将成为用户的迫切需求。 发明内容 [0003] 本发明实施例旨在提供一种移动终端来电转接的方法及其移动终端,以解决现有移动终端无法实现来电转接功能的缺陷。 [0004] 本发明实施例提供了一种移动终端中呼叫转移的方法,包括: 移动终端控制其两块通信卡分别建立第一呼叫连接和第二呼叫连接; 当接收到呼叫转移指令时,移动终端获取第一呼叫连接和第二呼叫连接的下行信道数据; [0005] 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,并将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,并屏蔽音频 移动终端中的数据输入/输出单元。 [0006] 优选地,在获取第一呼叫连接和第二呼叫连接的下行信道数据之前,第一呼叫连接对应的呼叫状态为呼叫保持状态,第二呼叫连接对应的呼叫状态为呼叫激活状态。 [0007] 优选地,所述移动终端控制其两块通信卡分别建立第一呼叫连接和第二呼叫连接之后,所述方法还包括: 移动终端接收到用户通过本终端发送的终止呼叫指令后,控制其两块通信卡。 通信卡断开已建立的第一呼叫连接和第二呼叫连接; 或者,当第一呼叫连接终止时,移动终端控制断开第二呼叫连接,或者当第二呼叫连接终止时,移动终端控制第一呼叫连接断开。 [0008]一种移动终端呼叫转移的方法,包括: 移动终端控制其第一通信卡建立第一呼叫连接; 当移动终端接收到呼叫转移指令时,移动终端控制其第二通信卡建立第二呼叫连接,并获取第一呼叫连接和第二呼叫连接的下行信道数据; 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行数据信道,并将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,屏蔽 移动终端中的音频数据输入/输出单元。 [0009] 优选地,在获取第一呼叫连接和第二呼叫连接的下行信道数据之前,第一呼叫连接对应的呼叫状态和第二呼叫连接对应的呼叫状态为呼叫激活状态。 [0010] 优选地,在控制自身的第二通信卡建立第二呼叫连接之后,所述方法还包括: 移动终端接收到用户通过本终端发送的终止呼叫指令后,控制自身的两个通信卡断开建立的第一呼叫连接。 和第二呼叫连接; 或者,移动终端在第一呼叫连接终止时控制断开第二呼叫连接,或者在第二呼叫连接断开时控制第一呼叫连接断开。 [0011] 本发明实施例还提供了一种移动终端,用于移动终端中的呼叫转移,包括: [0012] 控制模块,用于控制移动终端的两个通信卡分别建立第一呼叫连接和第二呼叫连接; 获取模块,用于在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; 处理模块,用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行数据信道, 屏蔽移动终端中的音频数据输入/输出单元。 [0013] 优选地,所述控制模块,还用于在接收到用户通过本终端发送的终止通话指令时,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接。 或者在第一呼叫连接终止时控制第二呼叫连接断开,或者在第二呼叫连接终止时控制第一呼叫连接断开。 [0014] 一种移动终端,用于在移动终端中转移呼叫,包括: 控制模块,用于控制移动终端的第一通信卡建立第一呼叫连接,还用于控制移动终端的第二通信卡建立第一呼叫连接。 接收到呼叫转移指令后建立第二呼叫连接; 获取模块,用于获取第一呼叫连接和第二呼叫连接的下行信道数据; 处理模块,用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行数据信道, 屏蔽移动终端中的音频数据输入/输出单元。 [0015] 优选地,所述控制模块,还用于在接收到用户通过本终端发送的通话结束指令时,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接。 或者 [0016] 在第一呼叫连接终止时控制第二呼叫连接断开,或者在第二呼叫连接终止时控制第一呼叫连接断开。 [0017] 本发明实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接与对端呼叫进行呼叫连接,而无需挂断当前的呼叫连接,实现了简单、方便、快捷的目的。 快速实现移动终端的呼叫转移功能。 附图的简要说明 [0018] 图1为本发明实施例提供的移动终端来电转移方法实施例的流程图; [0019] 图2为本发明实施例提供的移动终端来电转移方法另一实施例的流程图。 [0020] 图3是本发明实施例的移动终端中呼叫转移的实施例的功能框图; [0021] 图4是根据本发明实施例的移动终端中用于转移呼叫的移动终端的另一个实施例的功能框图。 本发明的优选实施例 [0022] 下面结合附图及实施例,对本发明的技术方案作进一步说明。 应当理解,此处所描述的具体实施例仅仅用于解释,并不用于限制本发明。 [0023] 图1示出了根据本发明实施例的移动终端中呼叫转移方法的一个实施例的流程图。 [0024] 需要强调的是:图1所示的流程图仅为一个优选实施例,本领域的技术人员应当知晓,任何在本文档思想构思内所构筑的实施例都不应该脱离以下技术所涵盖的范围 解决方案: [0025] 本实施例提供的移动终端中的呼叫转移方法包括: [0026] 在步骤S 10 ,移动终端控制其两块通信卡分别建立第一通话连接和第二通话连接; [0027] 在本实施例中,两块通信卡可以属于同一网络制式,可以是GSM(全球移动通信系统)、WCDMA(宽带码分多址)、CDMA(码分多址)、TD中的任意一种。 -SCDMA(时分同步码分多址)和LTE(长期演进),或者可以分别属于GSM、CDMA、WCDMA、TD-SCDMA和LTE中的任意两个。 例如,移动终端通过第一通信卡的GSM网络制式建立第一呼叫连接,通过第二通信卡的CDMA网络制式建立第二呼叫连接,或者移动终端通过GSM建立第一呼叫连接 第一通信卡的网络制式,通过第二通信卡的GSM网络制式建立第二通话连接。 [0028] 在步骤S 20 、移动终端接收到呼叫转移指令后,获取第一呼叫连接和第二呼叫连接的下行信道数据; [0029]移动终端在接收到呼叫转移指令后,已经通过两张通信卡建立了两条呼叫连接。 第一呼叫连接对应的呼叫状态为呼叫保持状态,即呼叫等待状态,第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 根据用户需要,还可以在这两种状态之间切换。 例如,当用户想从第二呼叫连接的呼叫切换到第一呼叫连接时,向第一通信卡的网络侧发送Retrieve指令,向第二通信的网络侧发送Hold指令 card,获取第一通信卡的第一通话连接; 当然,用户也可以将第一呼叫连接的呼叫切换到第二呼叫连接,处理过程相同,此处不再赘述。 [0030] 接收到呼叫转移指令后,向对应的第一通信卡或第二通信卡发送Retrieve指令,使第一通信卡或第二通信卡保持呼叫激活状态,即正常呼叫状态。 移动终端获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据。 [0031] 在步骤S 30 ,移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,以及 屏蔽移动终端中的音频数据输入/输出单元。 [0032] 例如,在GSM和CDMA网络制式中,移动终端通过GSM和CDMA网络控制自己的两块通信卡分别建立第一呼叫连接和第二呼叫连接,当移动终端收到呼叫转移指令时,移动终端接 将从GSM网络侧接收的下行信道数据作为CDMA网络侧的上行信道数据进行传输,将从CDMA网络侧接收的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0033] 音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0034] 优选地,在呼叫转移过程中,当移动终端接收到用户通过本终端发送的终止呼叫指令时,移动终端控制第一通信卡和第二通信卡断开已建立的第一呼叫连接和第二呼叫连接。 ; 或者移动终端在第一通信卡的第一呼叫连接终止时控制第二通信卡的第二呼叫连接断开,或者移动终端在第二通信卡的第一呼叫连接断开时控制第一通信卡的第一呼叫连接断开。 呼叫连接终止。 [0035] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0036] 本实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接对对端呼叫进行呼叫连接,而无需挂断当前呼叫连接,从而方便、简单、快速地实现。 移动终端中的呼叫转移功能。 [0037]图2示出了根据本发明实施例的移动终端中呼叫转移方法的另一个实施例的流程图。 [0038] 需要强调的是:图2所示的流程图仅为一个较佳实施例,本领域的技术人员应该知晓,任何在本文档思想构思下所构筑的实施例都不应脱离以下技术所涵盖的范围 解决方案: [0039] 本实施例提供的移动终端中的呼叫转移方法包括: [0040] 在步骤S 110 ,移动终端控制其第一通信卡建立第一呼叫连接; [0041] 在步骤S 120 、移动终端在接收到呼叫转移指令时控制其第二通信卡建立第二呼叫连接,并获取第一呼叫连接和第二呼叫连接的下行信道数据; [0042] 在本实施例中,第一通信卡和第二通信卡可以属于同一网络制式,可以是GSM(全球移动通信系统)、WCDMA(宽带码分多址)、CDMA(码分 Multiple Access)、TD-SCDMA(Time Division-Synchronous Code Division Multiple Access)和LTE(Long Term Evolution),或者分别属于GSM、CDMA、WCDMA、TD-SCDMA和LTE中的任意两个。 例如,移动终端在接收到呼叫转移指令时,通过第一通信卡的GSM网络制式建立第一呼叫连接,移动终端通过第二通信卡的CDMA网络制式建立第二呼叫连接,或者移动终端 终端通过第一通信卡的GSM网络制式建立第一呼叫连接,移动终端在接收到呼叫转移指令时通过第二通信卡的GSM网络制式建立第二呼叫连接。 [0043] 移动终端控制其第一通信卡建立第一呼叫连接; 移动终端接收到呼叫转移指令后,控制其第二通信卡建立第二呼叫连接。 此时移动终端已经分别通过第一通信卡和第二通信卡建立了两个通话连接。 第一呼叫连接对应的呼叫状态和第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 [0044] 当移动终端控制其第二通信卡建立第二呼叫连接时,移动终端获取通过第一通信卡建立的第一呼叫连接的下行信道数据以及通过第二通信卡建立的第二呼叫连接的下行信道数据。 第二张通讯卡。 [0045] 在步骤S 130 ,移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,屏蔽 移动终端中的音频数据输入/输出单元。 [0046] 例如,在GSM和CDMA网络制式中,移动终端在接到电话时控制自己的第一通信卡通过GSM网络建立第一呼叫连接,控制第二通信卡通过CDMA网络建立第二呼叫连接 传递指令,获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据; 移动终端将从GSM网络侧接收到的下行信道数据作为CDMA网络侧的上行信道数据进行传输,并将从CDMA网络侧接收到的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0047]音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0048] 进一步地,在呼叫转移过程中,当移动终端接收到用户通过本终端发送的终止呼叫指令时,移动终端控制第一通信卡和第二通信卡断开已建立的第一呼叫连接和第二呼叫连接。 ; 或者移动终端在第一通信卡的第一呼叫连接终止时控制第二通信卡的第二呼叫连接断开,或者移动终端在第二通信卡的第一呼叫连接断开时控制第一通信卡的第一呼叫连接断开。 呼叫连接终止。 [0049] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0050] 图3示出了根据本文档的用于在移动终端中转移呼叫的移动终端的实施例的功能框图。 移动端 1 本实施例提供的包括: [0051] 一个控制模块 10 ,用于控制移动终端的两个通信卡分别建立第一呼叫连接和第二呼叫连接; [0052] 在本实施例中,两块通信卡可以属于同一网络制式,可以是GSM、WCDMA、CDMA、TD-SCDMA和LTE中的任意一种,也可以分别属于GSM、CDMA、WCDMA中的任意两种。 、TD-SCDMA 和 LTE。 例如,控制模块 10 通过第一通信卡的GSM网络制式建立第一呼叫连接,通过第二通信卡的CDMA网络制式建立第二呼叫连接,或控制模块 10 通过第一通信卡的GSM网络制式建立第一呼叫连接,通过第二通信卡的GSM网络制式建立第二呼叫连接。 [0053] 获取模块 20 用于在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; [0054] 控制模块收到呼叫转移指令后, 10 已经通过两张通讯卡建立了两条通话连接。 第一呼叫连接对应的呼叫状态为呼叫保持状态,即呼叫等待状态,第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 根据用户需要,还可以在这两种状态之间切换。 例如,当用户想从第二呼叫连接的呼叫切换到第一呼叫连接时,向第一通信卡的网络侧发送Retrieve指令,向第二通信的网络侧发送Hold指令 卡取回第一通信卡的第一通话连接; 当然,用户也可以将第一呼叫连接的呼叫切换到第二呼叫连接,处理过程相同,此处不再赘述。 [0055] 接收到呼叫转移指令后,向对应的第一通信卡或第二通信卡发送Retrieve指令,使第一通信卡或第二通信卡保持呼叫激活状态,即正常呼叫状态。 获取模块 20获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据。 [0056] 一个处理模块 30 用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,并对音频数据进行屏蔽 移动终端中的输入/输出单元。 [0057] 在GSM和CDMA网络标准中,例如,控制模块 10 控制移动终端的两个通信卡分别通过GSM和CDMA网络建立第一呼叫连接和第二呼叫连接,处理模块接收到呼叫转移指令后, 30 将从GSM网络侧接收到的下行信道数据作为CDMA网络侧的上行信道数据进行传输,将从CDMA网络侧接收到的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0058] 音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0059] 优选地,在呼叫转移过程中,当控制模块 10 控制模块接收用户通过本终端发送的通话结束指令, 10 控制第一通信卡和第二通信卡断开已建立的第一通话连接和第二通话连接; 或控制模块 10 当第一通信卡的第一呼叫连接终止时,控制第二通信卡的第二呼叫连接断开,或者控制模块 10 当第二通话连接终止时,控制第一通信卡的第一通话连接断开。 [0060] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0061] 本发明实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接与对端呼叫进行呼叫连接,而无需挂断当前的呼叫连接,实现了简单、方便、快捷的目的。 快速实现移动终端的呼叫转移功能。 [0062] 图4示出了根据本发明实施例的移动终端中用于转移呼叫的移动终端的另一个实施例的功能框图。 移动端 2 本实施例提供的包括: [0063] 一个控制模块 110 , 用于控制移动终端的第一通信卡建立第一呼叫连接; 还用于在接收到呼叫转移指令时,控制移动终端的第二通信卡建立第二呼叫连接, [0064] 获取模块 120 ,用于获取第一呼叫连接和第二呼叫连接的下行信道数据; [0065]本实施例中,第一通信卡和第二通信卡可以属于同一网络制式,可以是GSM、WCDMA、CDMA、TD-SCDMA和LTE中的任意一种,也可以分别属于GSM中的任意两种, CDMA、WCDMA、TD-SCDMA和LTE。 例如,控制模块 110 通过第一通信卡的GSM网络制式建立第一通话连接,控制模块 110 接收到呼叫转移指令时,通过第二通信卡的CDMA网络制式建立第二呼叫连接,或者控制模块 110 通过第一通信卡的GSM网络标准建立第一通话连接,控制模块 110 接收到呼叫转移指令时,通过第二通信卡的GSM网络制式建立第二呼叫连接。 [0066] 控制模块 110 控制移动终端的第一通信卡建立第一呼叫连接; 控制模块收到呼叫转移指令后, 110 控制移动终端的第二通信卡建立第二呼叫连接。 在这种情况下,控制模块 110已经分别通过第一通讯卡和第二通讯卡建立了两个通话连接。 第一呼叫连接对应的呼叫状态和第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 [0067] 当控制模块 110 控制移动终端的第二通信卡建立第二呼叫连接,获取模块 120 获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据。 [0068] 一个处理模块 130 用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据, 屏蔽移动终端中的音频数据输入/输出单元。 [0069] 在GSM和CDMA网络标准中,例如,控制模块 110 控制其第一通信卡通过GSM网络建立第一通话连接,控制模块 110 控制其第二通信卡通过CDMA网络建立第二呼叫连接,获取模块 120 获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据; 处理模块 130 将从GSM网络侧接收到的下行信道数据作为CDMA网络侧的上行信道数据进行传输,将从CDMA网络侧接收到的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0070] 音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0071] 优选地,在呼叫转移过程中,当控制模块 110 控制模块接收用户通过本终端发送的通话结束指令, 110 控制第一通信卡和第二通信卡断开已建立的第一通话连接和第二通话连接; 或控制模块 10 当第一通信卡的第一呼叫连接终止时,控制第二通信卡的第二呼叫连接断开,或者控制模块 10 当第二通话连接终止时,控制第一通信卡的第一通话连接断开。 [0072] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0073] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明实施例的专利范围,任何利用本发明说明书内容及附图所作的等同结构变换,或者直接 或者间接用于其他相关技术领域,同样应当包含在本发明实施例的专利保护范围内。 工业实用性 [0074]本发明实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接与对端呼叫进行呼叫连接,而无需挂断当前的呼叫连接,实现了简单、方便、快捷的目的。 快速实现移动终端的呼叫转移功能。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104378748A(String), US20160192162A1(String), WO2014169764A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104378748A(String), US20160192162A1(String), WO2014169764A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20160192162A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104378748A(String), US20160192162A1(String), WO2014169764A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270680(Integer), CN104378748A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270680(Integer), US20160192162A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270680(Integer), WO2014169764A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:52.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20160192162A1(String), US20160192162A1(String), 1467216000(Integer), 270680(Integer), 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185001(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185001(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185001(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185001(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10827055B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for obtaining event information on mobile terminal and mobile terminal(String), 移动终端获取事件信息的方法及移动终端(String), US10827055B2(String), This application provides a mobile terminal and a method for obtaining event information on a mobile terminal, so as to automatically add a plurality of pieces of classifiable information in an event notification message to an application, thereby improving addition efficiency. The method includes: receiving, by a mobile terminal, an event notification message of a first application; obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template; determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule; and adding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to the m class attributes in the second application.(String), 本申请提供一种移动终端及获取移动终端事件信息的方法,以自动将事件通知消息中的多条可分类信息添加到应用程序中,提高添加效率。 该方法包括:移动终端接收第一应用的事件通知消息; 移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息; 移动终端根据预设规则,根据n个类属性确定第二应用程序; 移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m个类属性中。(String), US16/456951(String), 1561651200(Integer), US10827055B2(String), 1604332800(Integer), 1604332800(Integer), 美国(String), 4(Integer), CN(String), 3(Integer), 20(Integer), CN103221948A | CN103325031A | CN104750357A | CN104980549A | CN105227572A | CN105657158A | CN105898721A | CN106686240A | EP1965594A1 | JP2007317190A | JP2009137193A | US20040196866A1 | US20070271293A1 | US20090068990A1 | US20120226753A1 | US20120289206A1 | US20130145024A1 | US20150304425A1 | US20170126609A1 | WO2009030769A2(String), 5(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185002(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.085 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\864fc47c8ddd4aa7a2c60d76830e66c5.png(String), 185002(Integer), 864fc47c8ddd4aa7a2c60d76830e66c5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.094 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.097 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for obtaining event information on mobile terminal and mobile terminal(String), 移动终端获取事件信息的方法及移动终端(String), US10827055B2(String), This application provides a mobile terminal and a method for obtaining event information on a mobile terminal, so as to automatically add a plurality of pieces of classifiable information in an event notification message to an application, thereby improving addition efficiency. The method includes: receiving, by a mobile terminal, an event notification message of a first application; obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template; determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule; and adding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to the m class attributes in the second application.(String), 本申请提供一种移动终端及获取移动终端事件信息的方法,以自动将事件通知消息中的多条可分类信息添加到应用程序中,提高添加效率。 该方法包括:移动终端接收第一应用的事件通知消息; 移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息; 移动终端根据预设规则,根据n个类属性确定第二应用程序; 移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m个类属性中。(String), US16/456951(String), 1561651200(Integer), US10827055B2(String), 1604332800(Integer), 1604332800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 3(Integer), 20(Integer), CN103221948A | CN103325031A | CN104750357A | CN104980549A | CN105227572A | CN105657158A | CN105898721A | CN106686240A | EP1965594A1 | JP2007317190A | JP2009137193A | US20040196866A1 | US20070271293A1 | US20090068990A1 | US20120226753A1 | US20120289206A1 | US20130145024A1 | US20150304425A1 | US20170126609A1 | WO2009030769A2(String), \20230420\864fc47c8ddd4aa7a2c60d76830e66c5.png(String), 5(Integer), 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.113 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185002(Integer), 1. A method, comprising:receiving, by a mobile terminal, an event notification message of a first application;obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template, wherein the n pieces of classifiable information correspond to n class attributes, the predefined class template comprises a classification relationship between classifiable information and a particular class attribute, and n is an integer greater than 2;determining a plurality of target applications of the mobile terminal based on then class attributes, wherein each target application of the plurality of target applications comprises at least one class attribute in then class attributes;determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule, wherein the second application comprises m class attributes, a set that comprises them class attributes is a subset of a set that comprises then class attributes, and m is an integer greater than or equal to 2 and less than n; andadding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to them class attributes in the second application, wherein them pieces of classifiable information correspond to them class attributes in the second applicationwherein the determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule comprises:determining, by the mobile terminal from the plurality of target applications, a particular application that comprises the greatest number of attributes in then class attributes, to serve as the second application.(String), 1.一种方法,包括:移动终端接收第一应用的事件通知消息;移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息,其中,n条可分类信息对应n个类属性,预定义的类模板包括可分类信息与类属性之间的分类关系。特定类属性,n为大于2的整数;基于类别属性确定移动终端的多个目标应用,其中,多个目标应用中的每个目标应用包括类别属性中的至少一个类别属性;移动终端根据预设规则从多个目标应用中确定第二应用,其中,第二应用包括m个类别属性,包括m个类别属性的集合是包括m个类别属性的集合的子集,m为大于或等于2且小于n的整数;和移动终端将事件通知消息中的m条可分类信息添加到第二应用中的类属性中,其中,所述可分类信息对应于第二应用中的类属性其中,移动终端根据预设规则从多个目标应用中确定第二应用包括:移动终端从多个目标应用中确定在该类属性中包含最多属性的特定应用作为第二应用。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185002(Integer), 2. The method according to claim 1, wherein before the adding, by the mobile terminal, m pieces of classifiable information in the event notification message to the m class attributes in the second application, the method further comprises:searching, by the mobile terminal, existing content in the second application for similar content that includes the m pieces of classifiable information; andperforming, by the mobile terminal, first processing on the similar content based on an operation performed by the user on the similar content, wherein the first processing comprises deletion processing.(String), 2.根据权利要求1所述的方法,其中在移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m类属性之前,还包括:移动终端在第二应用中已有的内容中查找包含m条可分类信息的相似内容;和移动终端根据用户对相似内容的操作,对相似内容进行第一处理,其中,第一处理包括删除处理。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185002(Integer), 3. A mobile terminal, comprising a transceiver, a processor, and a memory, wherein the memory is configured to store at least one instruction, and the processor is configured to invoke the at least one instruction to perform the following processing:receiving, from the transceiver, an event notification message of a first application;obtaining n pieces of classifiable information in the event notification message based on a predefined class template, wherein the n pieces of classifiable information correspond to n class attributes, the predefined class template comprises a classification relationship between classifiable information and a class attribute, and n is an integer greater than 2;determining a plurality of target applications of the mobile terminal based on then class attributes, wherein each target application of the plurality of target applications comprises at least one class attribute in then class attributes;determining a second application from the plurality of target applications according to a preset rule, wherein the second application comprises m class attributes, a set that comprises them class attributes is a subset of a set that comprises then class attributes, and m is an integer greater than or equal to 2 and less than n; andadding m pieces of classifiable information that are in the event notification message to them class attributes in the second application, wherein them pieces of classifiable information correspond to them class attributes in the second applicationwherein the determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule comprises:determining, by the mobile terminal from the plurality of target applications, a particular application that comprises the greatest number of attributes in then class attributes, to serve as the second application.(String), 3.移动终端,包括收发器、处理器和存储器,其中,所述存储器用于存储至少一条指令,所述处理器用于调用所述至少一条指令进行以下处理:从收发器接收第一应用程序的事件通知消息;基于预定义的类模板获取事件通知消息中的n条可分类信息,其中,n条可分类信息对应n个类属性,预定义类模板包括可分类信息与类属性之间的分类关系,n为大于2的整数;基于类别属性确定移动终端的多个目标应用,其中,多个目标应用中的每个目标应用包括类别属性中的至少一个类别属性;根据预设规则从多个目标应用中确定第二应用,其中,第二应用包括m个类别属性,包括其类别属性的集合为包括该类别属性的集合的子集,m为大于的整数小于或等于2且小于n;和将事件通知消息中的m条可分类信息添加到第二应用中的类属性中,其中每条可分类信息对应第二应用中的类属性其中,移动终端根据预设规则从多个目标应用中确定第二应用包括:移动终端从多个目标应用中确定在该类属性中包含最多属性的特定应用作为第二应用。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.115 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185002(Integer), 4. The mobile terminal according to claim 3, wherein the processor is further configured to search existing content in the second application for similar content that includes the m pieces of classifiable information; andperform first processing on the similar content based on an operation performed by the user on the similar content, wherein the first processing comprises deletion processing.(String), 4.根据权利要求3所述的移动终端,其中处理器还用于在第二应用程序中的现有内容中查找包含m条可分类信息的相似内容。和基于用户对相似内容的操作对相似内容进行第一处理,其中,第一处理包括删除处理。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185002(Integer), 5. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to carry out the following operations:receiving, by a mobile terminal, an event notification message of a first application;obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template, wherein the n pieces of classifiable information correspond to n class attributes, the predefined class template comprises a classification relationship between classifiable information and a particular class attribute, and n is an integer greater than 2;determining a plurality of target applications of the mobile terminal based on then class attributes, wherein each target application of the plurality of target applications comprises at least one class attribute in then class attributes;determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule, wherein the second application comprises m class attributes, a set that comprises them class attributes is a subset of a set that comprises then class attributes, and m is an integer greater than or equal to 2 and less than n; andadding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to them class attributes in the second application, wherein them pieces of classifiable information correspond to them class attributes in the second applicationwherein the determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule comprises:determining, by the mobile terminal from the plurality of target applications, a particular application that comprises the greatest number of attributes in then class attributes, to serve as the second application.(String), 5.一种非暂时性计算机可读存储介质包括当被处理器执行时,使处理器执行以下操作的指令:移动终端接收第一应用的事件通知消息;移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息,其中,n条可分类信息对应n个类属性,预定义的类模板包括可分类信息与类属性之间的分类关系。特定类属性,n为大于2的整数;基于类别属性确定移动终端的多个目标应用,其中,多个目标应用中的每个目标应用包括类别属性中的至少一个类别属性;移动终端根据预设规则从多个目标应用中确定第二应用,其中,第二应用包括m个类别属性,包括m个类别属性的集合是包括m个类别属性的集合的子集,m为大于或等于2且小于n的整数;和移动终端将事件通知消息中的m条可分类信息添加到第二应用中的类属性中,其中,所述可分类信息对应于第二应用中的类属性其中,移动终端根据预设规则从多个目标应用中确定第二应用包括:移动终端从多个目标应用中确定在该类属性中包含最多属性的特定应用作为第二应用。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185002(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2017/099424, filed on Aug. 29, 2017, which claims priority to Chinese Patent Application No. 201611260769.2, filed on Dec. 30, 2016. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of this application relate to the field of information processing on a mobile terminal, and more specifically, to a method for obtaining event information on a mobile terminal and a mobile terminal. BACKGROUND [0003]Content recognition by a mobile terminal mainly includes automatic matching and feature capturing performed by the mobile terminal on information such as a character, a picture, and a geographic location. Character recognition may be applied to a plurality of fields such as reading, translation, document retrieval, letter and parcel sorting, manuscript editing and proofreading, summarization and analysis of massive statistical statements and cards, bank check processing, commodity invoice summarization, commodity code recognition, commodity warehouse management, automatic processing of massive credit cards in services of charging fees for water, electricity, gas, house rent, and personal insurance, and partial work automation for office typists. Character information recognition in a mobile terminal system can support the mobile terminal system in performing a further intelligent scenario function after obtaining and recognizing character information. For example, after obtaining and recognizing address content, the mobile terminal system may invoke a related map application in the system based on a shortcut operation performed by a user on the address content, to recommend content related to the address text content to the user, so that the user can check and select the content recommended by the mobile terminal and the like. [0004]In the prior art, an event notification message received by a mobile terminal may include a plurality of pieces of information, and if a user needs to add the plurality of pieces of information to an application, the user needs to respectively perform operations such as manual addition or system recognition addition. For example, after an SMS application module receives a notification message that includes content such as a position, a contact, an email address, and a phone number, when the user needs to add the contact, the email address, and the phone number to an address book, the user first performs a shortcut operation on the phone number to add the phone number to the address book, and then successively manually enters or copies the contact and the email address in the SMS message to a contact and email address column in the address book. It can be learned that such a method for adding a plurality of pieces of classifiable information in one event notification message to an application one by one causes relatively low efficiency. SUMMARY [0005]This application provides a method for obtaining event information on a mobile terminal and a mobile terminal, so as to automatically add a plurality of pieces of classifiable information in an event notification message to an application, thereby improving addition efficiency. [0006]According to a first aspect, a method for obtaining event information on a mobile terminal is provided, and includes: receiving, by a mobile terminal, an event notification message of a first application; [0007]obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template, where the n pieces of classifiable information are respectively corresponding to n class attributes, the class template includes a classification relationship between classifiable information and a class attribute, and n is an integer greater than or equal to 2; [0008]determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule, where the second application includes m class attributes, a set that includes the m class attributes is a subset of a set that includes the n class attributes, and m is an integer greater than or equal to 2 and not greater than n; and [0009]adding, by the mobile terminal, m pieces of classifiable information that are in the event notification message and that are respectively corresponding to the m class attributes to the m class attributes in the second application. [0010]According to the method for obtaining event information on a mobile terminal in this application, the mobile terminal may obtain the plurality of pieces of classifiable information included in the event notification message by using the predefined class template. In addition, the mobile terminal may obtain, according to the preset rule, an application (namely, the second application) that includes class attributes corresponding to at least two pieces of classifiable information in the plurality of pieces of classifiable information. Further, the mobile terminal may automatically add the at least two pieces of classifiable information in the plurality of pieces of classifiable information to the corresponding class attributes in the second application. Therefore, operation complexity of adding all pieces of classifiable information by a user one by one can be reduced, information addition efficiency can be improved, and user experience can be improved. [0011]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0012]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0013]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application that includes most attributes in the n class attributes, to serve as the second application. [0014]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0015]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0016]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application that has highest relevance to the first application, to serve as the second application. [0017]In the foregoing manner, the mobile terminal may automatically add the classifiable information in the event notification message to the application having highest relevance to the first application. [0018]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0019]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0020]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application used by a user at a time that is proximate to a time at which the first application is used, to serve as the second application. [0021]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0022]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0023]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application that is most frequently used by a user, to serve as the second application. [0024]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0025]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0026]if there are a plurality of target applications, determining, by the mobile terminal, an application that is randomly selected from the target applications, to serve as the second application. [0027]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0028]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0029]if there is one target application, determining, by the mobile terminal, the target application as the second application. [0030]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0031]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0032]if there are a plurality of target applications, determining, by the mobile terminal, any one of the target applications as the second application. [0033]Optionally, the mobile terminal may determine some or all of the target applications as second applications. [0034]If there are a plurality of second applications, the mobile terminal may sequentially present application names of the determined second applications to the user based on a quantity of included class attributes in the n class attributes. In addition, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on relevance to the first application. Moreover, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on an interval between a use time of the user and a current time, or a use frequency of the user in a recent period of time. Certainly, the mobile terminal may randomly sort the second applications to present application names of the second applications to the user. [0035]The user may select any one of the foregoing second applications, and add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in the selected application. The user may select no application from the presented second applications, but add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in each second application together. [0036]It should be understood that for the foregoing plurality of manners of determining the second application by the mobile terminal, the mobile terminal may select one thereof or perform combination, and a specific manner that is to be used may be defined or selected by the user, so as to meet different user requirements. [0037]In a possible implementation, before the adding, by the mobile terminal, m pieces of classifiable information in the event notification message to the m class attributes in the second application, the method further includes: [0038]searching, by the mobile terminal, existing content corresponding to the m class attributes in the second application for content that is the same as the m pieces of classifiable information; and [0039]performing, by the mobile terminal, first processing on the same content based on an operation performed by the user on the same information content, where the first processing includes deletion processing. [0040]The deletion processing is performed on the content, in the second application, that is the same as the m pieces of classifiable information, so as to avoid repeated information storage, and release storage space of the mobile terminal. In addition, it is convenient for the user to read and search for related content, so as to improve user experience. [0041]According to a second aspect, a mobile terminal is provided, and is configured to perform the method in the first aspect or any possible implementation of the first aspect. Specifically, the mobile terminal includes units configured to perform the method in the first aspect or any possible implementation of the first aspect. [0042]According to a third aspect, a mobile terminal is provided, and includes a processor, a memory, and a transceiver, where the processor, the memory, and the transceiver are connected by using a bus system. The memory is configured to store an instruction, and the processor is configured to invoke the instruction stored in the memory, so that the terminal device performs the method in the first aspect or any possible implementation of the first aspect. [0043]According to a fourth aspect, a computer readable medium is provided, and is configured to store a computer program, where the computer program includes an instruction used to perform the method in the first aspect or any possible implementation of the first aspect. BRIEF DESCRIPTION OF DRAWINGS [0044]FIG. 1 is a schematic diagram of an application scenario according to this application; [0045]FIG. 2 is a schematic flowchart of a method for obtaining event information on a mobile terminal according to an embodiment of this application; [0046]FIG. 3 is a schematic diagram of a method for obtaining event information on a mobile terminal according to a specific embodiment of this application; [0047]FIG. 4 is a schematic diagram of a method for obtaining event information on a mobile terminal according to a specific embodiment of this application; [0048]FIG. 5 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0049]FIG. 6 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0050]FIG. 7 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0051]FIG. 8 is a schematic diagram of a method for obtaining event information on a mobile terminal according to still another specific embodiment of this application; [0052]FIG. 9 is a schematic diagram of a method for obtaining event information on a mobile terminal according to still another specific embodiment of this application; [0053]FIG. 10 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0054]FIG. 11 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0055]FIG. 12 is a schematic block diagram of a mobile terminal according to an embodiment of this application; and [0056]FIG. 13 is a schematic block diagram of a mobile terminal according to another embodiment of this application. DESCRIPTION OF EMBODIMENTS [0057]The following describes the embodiments of this application with reference to accompanying drawings. [0058]In this application, the term such as “for example” is used to indicate an example, instance, or illustration. Any embodiment or design scheme described by using the term “for example” in the embodiments of this application should not be construed as having more advantages than another embodiment or design scheme. Exactly, using the term such as “for example” is intended to present a related concept in a specific manner. [0059]A terminal device in this application includes an electronic product that can perform human-computer interaction with a user by using a keyboard, a touchpad, or a sound control device. For example, the terminal device may be a computer, a smartphone, a wearable device, a tablet computer (Portable Android Device (PAD)), or the like. An operating system running on the terminal device may be a Linux kernel-based operating system such as Android in a mobile version, Ubuntu in a mobile version, or Tizen, and a desktop operating system such as Windows, Mac OS, or Linux. This is not limited in this application. [0060]In the embodiments of this application, an application may be referred to as an application program (e.g., Application or APP), and an application may be an application built into the operating system of the terminal device, or may be a third-party application installed in the operating system of the terminal device. This is not limited in this application. [0061]FIG. 1 shows an application scenario according to embodiments of this application. As shown in FIG. 1, when an application of the terminal device, such as an SMS message or the WeChat® APP, receives an event notification message, and the event notification message includes two or more pieces of classifiable information such as a conference theme, a time, a position, staff, and a phone number, the terminal device may process the classifiable information by identifying an operation performed by a user on the classifiable information, for example, may enable an application related to the classifiable information. [0062]In an existing related technology, a mobile system end usually performs tappable single recognition on key text content through tapping or touching and holding. The tapping triggers a most frequently-used operation action, and the touching and holding adds more operations on the text information. For example, when a current prompt is that digits may be tapped, the tapping is triggering a user to perform a call operation, and the touching and holding is triggering more operation options that include making a call, sending an SMS message, adding to an address book, copying, and the like. When the user needs to add the conference theme, the time, the position, the staff, and the phone number shown in FIG. 1 to an application such as a calendar, the user needs to perform operations on the conference theme, the time, the position, the staff, and the phone number one by one, to respectively add the conference theme, the time, the position, the staff, and the phone number to corresponding class attributes of the calendar. Such a method for adding a plurality of pieces of classifiable information to corresponding class attributes of an application one by one causes relatively low efficiency and relatively complex operations. [0063]Based on the foregoing prior-art problems, this application provides a method for obtaining event information on a mobile terminal. When an event notification message includes a plurality of pieces of classifiable information, at least two pieces of classifiable information in the plurality of pieces of classifiable information can be automatically added to a corresponding application, and do not need to be manually added by a user, so as to improve addition efficiency, reduce addition operation complexity, and improve user experience. [0064]FIG. 2 is a schematic flowchart of a method for obtaining event information on a mobile terminal according to an embodiment of this application. [0065]S210. A mobile terminal receives an event notification message. [0066]The event notification message is a message of a first application. For example, the first application may be an SMS message APP, WeChat® APP, or QQ® APP, and correspondingly, the event notification message may be an SMS message, a WeChat message, or a QQ message. For example, the event notification message may be a conference notification message, and the conference notification message may include a time, a position, staff, and a phone number (a contact may be included). For another example, the event notification message may be a flight notification message, and the flight notification message may include information such as a time (including a departure time and a landing time), a flight number, a position (including a departure position and a destination). [0067]S220. The mobile terminal obtains n pieces of classifiable information in the event notification message based on a predefined class template according to a preset rule. [0068]For example, a user usually needs to add a plurality of pieces of information such as a contact or a phone number to an address book, and the mobile terminal may define a class template based on class attributes such as a contact, a phone number, an address, and an email address presented in the address book. For example, the mobile terminal may define that the class template includes three class attributes: the contact, the address, and the email address. For another example, the mobile terminal may define that the class template includes four class attributes: the contact, the address, the phone number, and the email address. Then, the mobile terminal obtains the n pieces of classifiable information in the event notification message based on the predefined class template according to the preset rule. The n pieces of classifiable information are respectively corresponding to n class attributes, and n is an integer greater than or equal to 2. For example, when the event notification message is the conference notification message described in S210, then class attributes included in the event notification message include a time, a position, staff, and a phone number. When the class template includes the four class attributes, the mobile terminal may obtain information about the time, the position, the staff, and the phone number information in the event notification message. [0069]It should be understood that in this embodiment of this application, a system may define a class template based on one or more applications. For example, the system may define the class template based on only one application such as an address book or a calendar, or define the class template with reference to a plurality of applications such as an address book and a calendar. This is not limited in this embodiment of this application. [0070]In this embodiment of this application, after obtaining the n pieces of classifiable information in the event notification message, the mobile terminal may present a first operation page to the user, and the first operation page includes at least two of the n pieces of classifiable information. Based on information presented on the first operation page, the user can learn of the classifiable information obtained by the terminal device in S220. In addition, to improve intelligibility, the first operation page may further present identification information used to identify each piece of classifiable information. The identification information may be predefined by the system based on a class template. For example, the identification information may be a text or an image for identifying a class attribute defined in the class template. For example, time information may be identified by using a text “time” or an image with an icon of an alarm clock, and position information may be identified by using a text “position” or an image with an icon of a map. A specific form of the identification information is not limited in this application. [0071]S230. The mobile terminal determines a second application based on the n class attributes according to the preset rule. [0072]The second application includes m class attributes, a set that includes the m class attributes is a subset of a set that includes the n class attributes, and m is an integer greater than or equal to 2 and not greater than n. For example, when the n class attributes include the time, the position, the staff, and the phone number, the m class attributes may include the time, the position, and the staff, or may include the position, the staff, and the phone number. [0073]When determining the second application based on the n class attributes according to the preset rule, the mobile terminal may first determine a target application based on the n class attributes, and the target application includes at least one class attribute in the n class attributes. In other words, the mobile terminal may determine an application as the target application, provided that the application includes one of the n class attributes. If there is only one target application, the mobile terminal determines the target application as the second application. If there are a plurality of target applications, the mobile terminal may determine the second application in the following manners. [0074]Manner 1 [0075]The mobile terminal determines, from the target applications, an application that has most attributes in the n class attributes, to serve as the second application. [0076]Specifically, after the mobile terminal determines the target applications, the mobile terminal selects, from the target applications, the application that has most attributes in the n class attributes, and determines the application as the second application. For example, the n class attributes include the time, the position, the staff, and the phone number; the address book includes two class attributes: the staff and the phone number; a note includes four class attributes: the time, the position, the staff, and the phone number; and the calendar includes one attribute: the time. Therefore, the target applications determined by the mobile terminal include the address book, the note, and the calendar. The note includes most class attributes in the target applications, and therefore the mobile terminal may determine the note that includes the foregoing four class attributes, to serve as the second application. [0077]Manner 2 [0078]The mobile terminal determines, from the target applications, an application that has highest relevance to the first application, to serve as the second application. [0079]For example, the first application may be an SMS application, and applications related to the first application may be the WeChat® APP, the QQ® APP, an address book, and the like. The mobile terminal may predefine the applications related to the first application, and define relevance of each application to the first application. When defining an application related to the first application, the mobile terminal may define an application that is frequently used by the user recently or an application that is invoked together with the first application by using a shortcut, to serve as the application related to the first application. This is not specifically limited in this embodiment of this application. In this embodiment of this application, the mobile terminal may first obtain the target applications that include the at least one class attribute in the n class attributes, and then find, based on relevance of these applications to the first application, the application that has highest relevance to the first application, to serve as the second application. [0080]Manner 3 [0081]The mobile terminal determines, from the target applications, an application used by a user at a time that is proximate to a time at which the first application is used, to serve as the second application. [0082]Specifically, in this embodiment, the mobile terminal first determines a target application that includes at least one class attribute in the n class attributes. If there are a plurality of target applications, the mobile terminal may determine, based on times at which a user uses these applications, an application used at a most recent time that is proximate to a current time, and determine the application as the second application. [0083]For example, the target applications determined by the mobile terminal include the address book, the calendar, and the note, and if most recent times at which the user uses the three applications are respectively one day ago, two days ago, and five days ago, the mobile terminal determines the address book as the second application. [0084]Manner 4 [0085]The mobile terminal determines, from the target applications, an application that is most frequently used by a user, to serve as the second application. [0086]After determining the target applications, the mobile terminal obtains, based on a frequency of recently using each of the target applications by the user, the application that is most frequently used by the user, and determines the application as the second application. [0087]For example, the target applications determined by the mobile terminal include the address book, the calendar, and the note, and if frequencies of recently using the three applications by the user, for example, in the last six months or the last three months are respectively 200, 20, and 10, respectively, the mobile terminal determines the address book as the second application. [0088]Manner 5 [0089]The mobile terminal determines an application that is randomly selected from the target applications, to serve as the second application. [0090]Herein, the mobile terminal may determine the second application by using a random algorithm. An algorithm or a method used by the mobile terminal for random selection is not limited in this embodiment of this application. [0091]Manner 6 [0092]The mobile terminal determines any one of the target applications as the second application. [0093]In other words, the mobile terminal may determine one or more applications that include the at least one class attribute in the n class attributes, to serve as the second application. [0094]If determining a plurality of applications in the target applications as second applications, the mobile terminal may sequentially present application names of the determined second applications to the user based on a quantity of included class attributes in the n class attributes. For example, from top to bottom of a display screen, the mobile terminal may present, in the first row, a name of an application that includes the most class attributes in the n class attributes, present, in the second row, a name of an application that includes the second most class attributes in the n class attributes, and by analogy, present, in the last row, a name of an application that includes the fewest class attributes in the n class attributes. In addition, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on relevance to the first application. For example, from top to bottom of a display screen, the mobile terminal may present, in the first row, a name of an application that has the highest relevance to the first application, present, in the second row, a name of an application that has the second highest relevance to the first application, and by analogy, present, in the last row, a name of an application that has the lowest relevance to the first application. Moreover, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on an interval between a use time of the user and a current time, or a use frequency of the user in a recent period of time. Certainly, the mobile terminal may randomly sort the second applications to present application names of the second applications to the user. [0095]The user may select any one of the foregoing second applications, and add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in the selected application. The user may select no application from the presented second applications, but add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in each second application together. [0096]It should be understood that for the foregoing plurality of manners of determining the second application by the mobile terminal, the mobile terminal may select one thereof or perform combination, and a specific manner that is to be used may be defined or selected by the user, so as to meet different user requirements. [0097]It should be understood that the mobile terminal determines the second application based on selection from a plurality of applications. For ease of description, the plurality of applications are referred to as third applic(String), 相关申请的交叉引用 [0001] 本申请是2017年8月29日提交的国际申请号PCT/CN2017/099424的继续申请,该国际申请要求2016年12月30日提交的中国专利申请号201611260769.2的优先权。上述申请的公开内容是 特此通过引用整体并入。 技术领域 [0002] 本申请实施例涉及移动终端信息处理领域,更具体地,涉及一种移动终端事件信息的获取方法及移动终端。 背景 [0003] 移动终端的内容识别主要包括移动终端对字符、图片、地理位置等信息进行的自动匹配和特征捕获。 字符识别可应用于阅读、翻译、文献检索、信件包裹分拣、稿件编辑校对、海量统计报表、卡片汇总分析、银行支票处理、商品发票汇总、商品代码识别等多个领域 、商品仓库管理、水、电、气、房租、人身保险等收费服务的海量信用卡自动处理,办公打字员部分工作自动化。 移动终端系统中的字符信息识别,可以支持移动终端系统在获取并识别字符信息后,进一步执行智能化的场景功能。 例如,移动终端系统获取并识别地址内容后,可以根据用户对地址内容的快捷操作,调用系统中相关的地图应用,向用户推荐与地址文本内容相关的内容, 方便用户查看和选择移动端推荐的内容等。 [0004] 现有技术中,移动终端接收到的事件通知消息中可能包含多条信息,如果用户需要将多条信息添加到应用程序中,则需要用户分别进行手动操作等操作。 添加或系统识别添加。 例如,短信应用模块收到包含位置、联系人、邮箱、电话号码等内容的通知消息后,当用户需要将联系人、邮箱、电话添加到 通讯录,用户首先对电话号码进行快捷操作,将电话号码添加到通讯录中,然后依次手动输入或复制短信中的联系人和邮箱到通讯录中的联系人和邮箱栏中 地址簿。 可以看出,这种将一条事件通知消息中的多条可分类信息逐一添加到应用程序中的方法效率较低。 概括 [0005] 本申请提供了一种获取移动终端事件信息的方法及移动终端,能够自动为应用程序添加事件通知消息中的多条可分类信息,提高添加效率。 [0006] 第一方面,提供了一种获取移动终端事件信息的方法,包括: 移动终端接收第一应用的事件通知消息; [0007] 移动终端根据预先定义的类模板获取事件通知消息中的n条可分类信息,该n条可分类信息分别对应n个类属性,类模板包括可分类信息与类模板之间的分类关系 类属性,n为大于等于2的整数; [0008] 移动终端根据预设规则根据n类属性确定第二应用,其中,第二应用包括m类属性,包括m类属性的集合是包括n类的集合的子集 属性,m为大于等于2且不大于n的整数; 和 [0009] 移动终端将事件通知消息中的m类属性分别对应的m条可分类信息添加到第二应用中的m类属性中。 [0010] 根据本申请的移动终端事件信息的获取方法,移动终端可以通过预先定义的类模板获取事件通知消息中包含的多个可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包括至少两个分类信息对应的类别属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个分类信息中的至少两个分类信息添加到第二应用中对应的类属性中。 从而可以降低用户将所有可分类信息逐条添加的操作复杂度,提高信息添加效率,提高用户体验。 [0011] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0012] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0013] 若目标应用为多个,则移动终端从目标应用中确定n类属性中属性最多的应用作为第二应用。 [0014] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0015] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0016] 若目标应用为多个,则移动终端从目标应用中确定与第一应用相关性最高的应用作为第二应用。 [0017] 通过上述方式,移动终端可以自动将事件通知消息中的可分类信息添加到与第一应用相关度最高的应用中。 [0018] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0019] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0020] 若目标应用为多个,则移动终端从目标应用中确定用户在与第一应用的使用时间相近的时间使用的应用作为第二应用。 [0021] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0022] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0023] 若目标应用为多个,则移动终端从目标应用中确定用户使用频率最高的应用作为第二应用。 [0024] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0025] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0026]若目标应用为多个,则移动终端从目标应用中随机选择一个应用作为第二应用。 [0027] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0028] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0029] 若目标应用为一个,则移动终端将该目标应用确定为第二应用。 [0030] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0031] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0032] 若目标应用为多个,则移动终端将目标应用中的任一个确定为第二应用。 [0033] 可选的,移动终端可以将部分或全部目标应用确定为第二应用。 [0034] 如果存在多个第二应用,则移动终端可以根据n个类别属性中包含的类别属性的数量,依次将确定的第二应用的应用名称呈现给用户。 另外,移动终端还可以根据与第一应用的相关性,将确定的第二应用的应用名称依次呈现给用户。 并且,移动终端还可以根据用户使用时间与当前时间的间隔,或者用户最近一段时间的使用频率,依次将确定的第二应用的应用名称依次呈现给用户。 当然,移动终端可以对第二应用程序进行随机排序,以将第二应用程序的应用程序名称呈现给用户。 [0035] 用户可以选择上述任一第二应用,将n条可分类信息中的一条或多条可分类信息添加到所选应用中对应的类属性中。 用户可以在所呈现的第二应用中不选择任何应用,而是将n条可分类信息中的一条或多条可分类信息一起添加到每个第二应用中对应的类别属性中。 [0036] 可以理解的是,对于上述多种移动终端确定第二应用的方式,移动终端可以选择其中的一种或者进行组合,具体采用何种方式可以由用户自行定义或选择, 以满足不同的用户需求。 [0037] 在一种可能的实现方式中,移动终端在将事件通知消息中的m条可分类信息添加到第二应用中的m类属性之前,还包括: [0038] 移动终端在第二应用中的m类属性对应的已有内容中查找与m条可分类信息相同的内容; 和 [0039] 移动终端根据用户对同一信息内容的操作,对同一内容进行第一处理,第一处理包括删除处理。 [0040] 对第二应用中与m条可分类信息相同的内容进行删除处理,避免重复信息存储,释放移动终端的存储空间。 另外,方便用户阅读和搜索相关内容,提高用户体验。 [0041]第二方面,提供了一种移动终端,用于执行第一方面或第一方面的任何可能实现方式中的方法。 具体地,该移动终端包括用于执行第一方面的方法或第一方面的任何可能实现方式的单元。 [0042] 第三方面,提供了一种移动终端,包括处理器、存储器和收发器,所述处理器、存储器和收发器通过总线系统连接。 存储器,用于存储指令,处理器,用于调用存储在存储器中的指令,使得终端设备执行第一方面的方法或第一方面的任何可能实现方式。 [0043] 第四方面,提供一种计算机可读介质,用于存储计算机程序,所述计算机程序包括用于执行第一方面的方法或第一方面的任何可能实现方式的指令。 附图说明 [0044] 图1为本申请的应用场景示意图; [0045] 图2为本申请实施例提供的一种获取移动终端事件信息的方法流程示意图; [0046] 图3为本申请具体实施例提供的移动终端事件信息的获取方法示意图; [0047] 图4为本申请具体实施例提供的移动终端事件信息的获取方法示意图; [0048] 图5为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0049] 图6为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0050] 图7为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0051] 图8为本申请又一具体实施例提供的移动终端事件信息的获取方法示意图; [0052] 图9为本申请再一具体实施例提供的移动终端事件信息的获取方法示意图; [0053] 图10为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0054] 图11为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0055] 图12是本申请一个实施例的移动终端的示意性框图; 和 [0056] 图13是根据本申请另一实施例的移动终端的示意性框图。 具体实施方式 [0057] 下面将结合附图对本申请的实施例进行描述。 [0058] 在本申请中,诸如“例如”之类的术语用于表示示例、实例或说明。 凡在本申请实施例中以“举例”一词描述的实施例或设计方案,不应理解为比其他实施例或设计方案具有更多的优点。 确切地说,使用诸如“例如”之类的术语是为了以特定方式呈现相关概念。 [0059]本申请中的终端设备包括能够通过键盘、触摸板或声控设备与用户进行人机交互的电子产品。 例如,终端设备可以是计算机、智能手机、可穿戴设备、平板电脑(Portable Android Device(PAD))等。 终端设备上运行的操作系统可以是基于Linux内核的操作系统,例如移动版的Android、移动版的Ubuntu、Tizen,以及桌面操作系统,例如Windows、Mac OS、Linux。 本申请不限于此。 [0060] 在本申请实施例中,应用程序可以称为应用程序(例如Application或APP),应用程序可以是终端设备操作系统内置的应用程序,也可以是第三方应用程序 安装在终端设备的操作系统中。 本申请不限于此。 [0061] 图1示出了根据本申请实施例的应用场景。 如图1所示,当终端设备的应用程序如短信或微信®APP接收到事件通知消息时,事件通知消息中包含两条或多条可分类信息,如会议主题, 终端设备可以通过识别用户对分类信息的操作来对分类信息进行处理,例如,可以开启与分类信息相关的应用。 [0062] 在现有的相关技术中,移动系统端通常通过点击或长按的方式对关键文本内容进行可点击的单一识别。 点击触发最常用的操作动作,长按增加对文本信息的更多操作。 例如,当当前提示为可以点击数字时,点击触发用户进行通话操作,长按触发更多的操作选项,包括拨打电话、发送短信、添加 地址簿、复印等。 当用户需要将图1所示的会议主题、时间、地点、人员、电话号码添加到日历等应用中时,用户需要对会议主题、时间、地点等进行操作。 职位、人员、电话一一对应,将会议主题、时间、职位、人员、电话一一添加到日历对应的类属性中。 这种将多条可分类信息逐条添加到应用程序对应的类属性中的方法效率较低,操作也比较复杂。 [0063] 基于上述现有技术问题,本申请提供了一种获取移动终端事件信息的方法。 当事件通知消息包括多个分类信息时,可以将多个分类信息中的至少两个分类信息自动添加到对应的应用中,不需要用户手动添加, 从而提高加法效率,降低加法操作复杂度,提升用户体验。 [0064] 图2为本申请实施例提供的一种获取移动终端事件信息的方法流程示意图。 [0065] 小号 210 . 移动终端接收事件通知消息。 [0066]事件通知消息为第一应用程序的消息。 例如,第一应用可以是短信APP、微信APP或QQAPP,相应的,事件通知消息可以是短信、微信或QQ消息。 例如,事件通知消息可以是会议通知消息,会议通知消息可以包括时间、地点、工作人员、电话号码(可以包括联系人)。 又例如,事件通知消息可以是航班通知消息,航班通知消息可以包括时间(包括起飞时间和降落时间)、航班号、位置(包括起飞位置和降落时间)等信息。 目的地)。 [0067] 小号 220 . 移动终端根据预设规则,基于预定义的类模板获取事件通知消息中的n条可分类信息。 [0068] 例如,用户通常需要在通讯录中添加联系人或电话号码等多条信息,移动终端可以根据联系人、电话号码等类属性定义类模板, 地址簿中显示的地址和电子邮件地址。 例如,移动终端可以定义类模板包括三个类属性:联系人、地址和电子邮件地址。 又例如,移动终端可以定义类模板包括四个类属性:联系人、地址、电话号码和电子邮件地址。 然后,移动终端根据预设规则基于预定义的类模板获取事件通知消息中的n条可分类信息。 n条可分类信息分别对应n个类别属性,n为大于等于2的整数。例如,当事件通知消息为S中描述的会议通知消息时 210 ,则事件通知消息中包含的类属性包括时间、职位、人员、电话号码。 当类模板包括四种类属性时,移动终端可以获取事件通知消息中的时间、位置、人员、电话号码信息。 [0069] 应理解,在本申请实施例中,系统可以基于一个或多个应用定义类模板。 例如,系统可以仅基于通讯录或日历等一个应用程序来定义类模板,也可以参考通讯录和日历等多个应用程序来定义类模板。 本申请实施例对此不作限定。 [0070] 本申请实施例中,移动终端在获取事件通知消息中的n条可分类信息后,可以向用户呈现第一操作页面,第一操作页面包括n条可分类信息中的至少两条。 . 用户可以根据第一个操作页面呈现的信息,了解到终端设备在S中获取的分类信息 220 . 另外,为了提高易懂性,第一操作页面还可以呈现用于标识每条可分类信息的标识信息。 标识信息可以是系统基于类模板预先定义的。 例如,标识信息可以是用于标识类模板中定义的类属性的文本或图像。 例如,时间信息可以通过文本“时间”或带有闹钟图标的图像来标识,位置信息可以通过文本“位置”或带有地图图标的图像来标识。 本申请不对标识信息的具体形式进行限定。 [0071] 小号 230 . 移动终端根据预设规则,基于n个类属性确定第二应用。 [0072]第二应用包括m类属性,包括m类属性的集合是包括n类属性的集合的子集,m为大于等于2且不大于n的整数。 例如,当n类属性包括时间、职位、人员、电话号码时,m类属性可以包括时间、职位、人员,也可以包括职位、人员、电话号码。 电话号码。 [0073] 在根据预设规则基于n个类属性确定第二应用时,移动终端可以首先根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性。 也就是说,移动终端可以确定一个应用程序为目标应用程序,前提是该应用程序包括n个类属性之一。 如果目标应用只有一个,则移动终端将目标应用确定为第二应用。 如果目标应用有多个,则移动终端可以通过以下方式确定第二应用。 [0074] 方式一 [0075] 移动终端从目标应用中确定n类属性中属性最多的应用作为第二应用。 [0076] 具体地,移动终端确定目标应用后,移动终端从目标应用中选择n类属性中属性最多的应用,确定该应用为第二应用。 例如,n个类属性包括时间、职位、人员、电话号码; 通讯录包括两个类属性:工作人员和电话号码; 一张便条包括四个类属性:时间、职位、人员、电话号码; 日历包含一个属性:时间。 因此,移动终端确定的目标应用包括通讯录、便签和日历。 笔记包含了目标应用中的大部分类属性,因此移动终端可以确定包含上述四种类属性的笔记作为第二应用。 [0077] 方式二 [0078] 移动终端从目标应用中确定与第一应用相关性最高的应用作为第二应用。 [0079] 例如,第一应用可以是短信应用,与第一应用相关的应用可以是微信APP、QQAPP、通讯录等。 移动终端可以预先定义与第一应用相关的应用,并定义每个应用与第一应用的相关性。 移动终端在定义与第一应用相关的应用时,可以定义用户最近使用频率较高的应用或者通过快捷方式与第一应用一起调用的应用,作为与第一应用相关的应用 应用。 本申请实施例对此不作具体限定。 在本申请实施例中,移动终端可以先获取n个类属性中包含至少一个类属性的目标应用,然后根据这些应用与第一应用的相关性,查找具有最高的应用。 与第一个应用程序相关,作为第二个应用程序。 [0080] 方式三 [0081] 移动终端从目标应用中确定用户在与第一应用的使用时间最接近的时间使用的应用作为第二应用。 [0082] 具体地,在本实施例中,移动终端首先确定n个类别属性中包括至少一个类别属性的目标应用。 如果目标应用有多个,则移动终端可以根据用户使用这些应用的时间,确定与当前时间最近一次使用的应用,确定该应用为第二应用 . [0083]例如,移动终端确定的目标应用包括通讯录、日历和便签,如果用户最近使用这三个应用的时间分别为一天前、两天前和五天前 ,移动终端确定通讯录为第二应用。 [0084] 方式四 [0085] 移动终端从目标应用中确定用户使用频率最高的应用作为第二应用。 [0086] 在确定目标应用程序后,移动终端根据用户最近使用各个目标应用程序的频率,获取用户使用频率最高的应用程序,确定该应用程序为第二应用程序。 [0087] 例如,移动终端确定的目标应用包括通讯录、日历和便签,如果用户最近使用这三个应用的频率,例如最近六个月或最近三个月, 分别为200、20、10,移动终端确定通讯录为第二应用。 [0088] 方式五 [0089] 移动终端从目标应用中随机选择一个应用作为第二应用。 [0090] 这里,移动终端可以通过随机算法确定第二应用。 本申请实施例不对移动终端随机选择的算法或方法进行限定。 [0091] 方式6 [0092] 移动终端将目标应用中的任意一个确定为第二应用。 [0093] 也就是说,移动终端可以确定n个类别属性中包括至少一个类别属性的一个或多个应用作为第二应用。 [0094] 如果将目标应用中的多个应用确定为第二应用,则移动终端可以根据n个类别属性中包含的类别属性的数量,依次向用户呈现确定的第二应用的应用名称。 例如,移动终端从显示屏的上到下,可以在第一行呈现n个类别属性中类别属性最多的应用程序的名称,在第二行呈现以下应用程序的名称: n个类属性中包含第二多类属性的应用程序,以此类推,在最后一行给出n个类属性中包含最少类属性的应用程序的名称。 另外,移动终端还可以根据与第一应用的相关性,将确定的第二应用的应用名称依次呈现给用户。 例如,移动终端从显示屏幕的顶部到底部,可以在第一行呈现与第一应用相关度最高的应用的名称,在第二行呈现应用的名称 与第一应用的相关性第二高的应用名称,以此类推,在最后一行给出与第一应用的相关性最低的应用名称。 并且,移动终端还可以根据用户使用时间与当前时间的间隔,或者用户最近一段时间的使用频率,依次将确定的第二应用的应用名称依次呈现给用户。 当然,移动终端可以对第二应用程序进行随机排序,以将第二应用程序的应用程序名称呈现给用户。 [0095] 用户可以选择上述任一第二应用,将n条可分类信息中的一条或多条可分类信息添加到所选应用中对应的类属性中。 用户可以在所呈现的第二应用中不选择任何应用,而是将n条可分类信息中的一条或多条可分类信息一起添加到每个第二应用中对应的类别属性中。 [0096]可以理解的是,对于上述多种移动终端确定第二应用的方式,移动终端可以选择其中的一种或者进行组合,具体采用何种方式可以由用户自行定义或选择, 以满足不同的用户需求。 [0097] 应理解,移动终端基于从多个应用中的选择来确定第二应用。 为了便于描述,以下将多个应用称为第三应用。 具体的,移动终端根据n个类别属性从第三应用程序中确定n个类别属性中的至少一个类别属性的应用程序作为第二应用程序。 第三应用可由用户自行定义。 例如,用户可以定义移动终端系统内置的部分或全部应用程序为第三应用程序。 又例如,用户可以定义移动终端上安装的部分或全部第三方应用程序为第三方应用程序。 再例如,用户可以定义移动终端系统中内置的所有应用程序和移动终端上安装的所有第三方应用程序都是第三方应用程序。 本申请不限制第三应用的数量和第三应用的来源。 第三应用程序可以由系统定义。 换句话说,用户不能改变第三应用程序的定义。 [0098] 还应理解,上述类模板也可以是基于第三应用定义的。 当第三应用由用户定义时,类模板也可能随着用户改变第三应用而改变。 当系统定义第三个应用时,类模板对用户来说是固定的,只随系统变化。 需要说明的是,移动终端通常是在接收到事件通知消息后,对事件通知消息进行识别。 当识别成功时,移动终端通过对内容进行特殊标记,例如下划线等,提示用户对事件通知消息中的某些内容进行快捷操作。 但是,在本申请实施例中,S中获取的分类信息 220 基于预定义的类模板可以只包括上述特别标注的内容,也可以只包括不特别标注的内容,还可以包括前述特别标注的内容和不特别标注的内容。 [0099] 小号 240 . 移动终端将事件通知消息中的m个类别属性分别对应的m条可分类信息添加到第二应用中的m个类别属性中。 具体地,移动终端在获取事件通知消息和第二应用中的n条可分类信息后,可以自动将n条可分类信息中的m条可分类信息添加到第二应用中的m类属性中。 例如,用户可以通过对第一操作页面进行操作,例如长按第一操作页面,将m条可分类信息添加到第二应用中的m类属性中。 [0100]因此,本申请的获取移动终端事件信息的方法,移动终端可以通过预定义的类模板获取事件通知消息中包含的多个可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包括至少两个分类信息对应的类别属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个分类信息中的至少两个分类信息添加到第二应用中对应的类属性中。 从而可以降低用户将所有可分类信息逐一添加的操作复杂度,提高信息添加效率,提高用户体验。 [0101] 下面以类模板包括四个类属性:联系人、电话号码、时间和位置为例,对本申请实施例的获取移动终端事件信息的方法进行说明。 会议通知消息如图1所示。 [0102] 移动终端接收到图1所示的会议通知消息后,通过类模板和会议通知消息,移动终端可以获取到会议通知消息中的四项信息:联系人:叶敏,电话号码: 13800000000,事件:明早10点,位置:A路18号。此时,移动终端呈现给用户的第一操作页面如图3所示。 或者,移动终端可以在S中通过任意方式确定第二应用。 230 同时将第一个操作页面呈现给用户。 例如,移动终端可以通过方式三确定通讯录为第二应用。则在用户操作图3所示的第一操作页面后,例如,用户长按图3所示的第一操作页面。 3、移动终端可以将第一操作页面上的联系人:叶敏和电话号码分别添加到通讯录的联系人栏和电话号码栏中。 添加完成后,通讯录生成的快捷操作页面如图4所示,用户可以在该页面上进行快捷操作,例如拨打电话、发送短信等。 [0103] 可选的,移动终端接收到事件通知消息后,可以向用户呈现第二操作页面。 第二操作页面包括事件通知消息和用于提示用户操作事件通知消息的第二页面元素。 移动终端可以根据预先定义的类模板和用户对第二页面元素的操作,获取事件通知消息中的n条可分类信息。 [0104] 具体地,以移动终端接收到主题为部门年中活动主题策划讨论的通知消息为例,移动终端接收到该通知消息后,呈现如图5所示的第二操作页面。当用户需要时 为了获取通知消息中的n条可分类信息,用户可以通过操作第二页面元素,例如点击第二页面元素,获取图3或图6所示的第一操作页面。 用户在获取到第一操作页面后,对移动终端呈现的第一操作页面进行操作,使得移动终端可以将n条分类信息中的至少两条分类信息添加到第二应用中。 [0105]第一操作页面还可以包括第一页面元素。 移动终端可以根据用户对第一页面元素的操作,将n条分类信息中的至少两条分类信息添加到第二应用中。 第一页元素可以是图形标记。 例如,第一页面元素可以是图6所示的图形标记,用户可以通过点击图形标记将n条分类信息中的至少两条分类信息添加到第二应用中。 第一页面元素可以是用于提示用户对第一操作页面进行添加操作的文本等标识。 本申请不对第一页面元素的具体形式进行限定。 [0106] 进一步地,若移动终端确定的第二应用为多个,则当移动终端根据用户对第二应用的操作,将n条可分类信息中的至少两条可分类信息添加到第二应用中。 第一操作页面,移动终端可以首先根据用户在第一操作页面上的操作呈现第一操作提示项。 第一操作提示项可以表示添加了n条可分类信息中的至少两条可分类信息的目标应用。 也就是说,第一操作提示项用于向用户提示可以添加n条分类信息中的至少两条分类信息的应用。 如果用户需要将第一操作页面呈现的分类信息添加到所有呈现的应用中,则用户可以长按第一操作页面,为这些应用中对应的类属性添加对应的分类信息。 另外,用户可以对呈现的应用进行选择,移动终端可以根据用户的选择,将n条分类信息中的至少两条分类信息添加到选择的第二应用中对应的类属性中。 第一个用户。 [0107] 例如,在用户对第一操作页面进行操作后,例如,用户在图6所示的第一操作页面上点击第一页面元素后,移动终端可以对第一操作页面呈现的可分类信息进行添加处理 当第一操作页面呈现的分类信息可以添加到多个应用时,可以呈现图7所示的第一操作提示项。 如图7所示,第一操作提示项包括提示项“添加事件到待办事项”和提示项“添加事件到通讯录”。 在用户触发第一操作提示项后,移动终端可以将第一操作页面呈现的分类信息添加到相应应用中的相应类属性中。 例如,在用户触发提示项“添加事件到通讯录”后,移动终端可以将图6所示的联系人和电话号码添加到通讯录中。 或者,在用户触发提示项“添加事件到待办事项”后,移动终端可以将图6所示的四种信息添加到待办事项中。 [0108] 在本申请的另一个实施例中,在移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m类属性之前,该方法还可以包括: [0109] 移动终端在第二应用中的m类属性对应的已有内容中查找与m条可分类信息相同的内容; 和 [0110] 移动终端根据用户对同一信息内容的操作,对同一内容进行第一处理,第一处理包括删除处理。 [0111]对第二应用中与m条可分类信息相同的内容进行删除处理,避免重复信息存储,释放移动终端的存储空间。 另外,方便用户阅读和搜索相关内容,提高用户体验。 [0112] 具体的,第二应用可以包括与n条可分类信息相关的内容,移动终端可以在第二应用中对应m类属性的m条内容中查找与n条可分类信息相同的内容。 . 例如,当第二应用包括待办事项应用和通讯录时,移动终端可以分别将n条可分类信息与时间、地址、姓名、地址等关键词的信息内容进行匹配。 待办事项应用中用户记录的个人姓名,以及通讯录中的联系人、电话号码、邮箱地址等关键词的信息内容。 通过上述匹配操作,可以得到第二应用中与n条可分类信息相关的内容。 例如,事件通知消息为短信,当短信中包含两个或两个以上与待办事项或通讯录中的内容相同的文本字符时,匹配成功。 移动终端得到的匹配结果为待办事项或通讯录中的内容包括两个或两个以上与每条可分类信息相同的文本字符。 移动终端在获取到与n条可分类信息相同的内容后,可以在第一操作页面上以第二操作提示项的形式向用户提示第二应用包括的内容为: 与n条可分类信息相同。 用户通过操作第二操作提示项,可以对第二应用中与n条可分类信息相关的内容进行相应的处理,例如删除处理。 [0113] 另外,在上述匹配过程中,移动终端还可以触发相应的互联网资源和服务,以及系统的其他传感器模块,如加速度模块、湿度模块、脉搏模块等进行匹配。 例如,当事件通知消息中包含地址时,移动终端可以触发相应的互联网资源和服务选项,如地图打开、路线规划、现状状态识别等。 例如,通过获取传感器速度,如果检测到用户当前处于驾驶模式,则默认推送路线导航驾驶模式,或者如果检测到用户当前处于禁止状态,则打车应用 服务被推送。 [0114] 因此,根据本申请中获取移动终端事件信息的方法,移动终端在获取并识别分类信息时,在第二应用中查找与分类信息相同的内容,使得 用户在向第二应用添加事件通知消息中的可分类信息之前,可以对第二应用中与可分类信息相同的内容进行删除处理,从而提高第二应用中内容的可理解性, 并改善用户体验。 [0115] 本申请实施例中,当移动终端查找到与n条可分类信息相同的内容时,移动终端可以呈现提示项“检查已有内容”(即第二操作提示项的示例) ) 在第一个操作页面上。 [0116]例如,参考图1,移动终端接收到关于部门年中活动主题策划讨论主题的通知消息后,根据预定义的类模板获取n条可分类信息,例如,关于部门年中活动主题策划讨论的内容。 如图3或图6所示的第一操作页面,移动终端在确定第二应用后,在待办事项或通讯录等第二应用中查找与至少一条可分类信息相同的内容 在 n 条可分类信息中。 当移动终端查找到与至少一条可分类信息相同的内容时,移动终端向用户呈现如图8所示的第一操作页面。 [0117] 在移动终端呈现包括第二操作提示项的第一操作页面后,用户可以对第二操作提示项进行操作,例如可以通过点击第二操作提示项查看m条内容中的内容 ,即与n条分类信息中的至少一条分类信息相同。 若第二应用包括与n条分类信息中的至少一条分类信息相同的内容,则在用户触发第二操作提示项后,移动系统呈现第二子操作提示项。 第二子操作提示项表示与n条分类信息中的至少一条分类信息相同的内容所在的第二应用。 通过操作第二子操作提示项,用户可以在期望的应用中查看n条分类信息中与至少一条分类信息相同的内容。 [0118] 例如,结合图8所示的第一操作页面,在用户触发提示项“查看已有内容”后,移动终端呈现图9所示的第二子操作提示项。第二子操作提示项包括: 提示项“在通讯录中查看匹配的内容”和提示项“在待办事项列表中查看匹配的内容”。 在用户触发第二子操作提示项后,例如,在用户触发“查看通讯录中匹配的内容”提示项后,移动系统开启通讯录应用,用户可以在通讯录中进行查看 ,与n条分类信息中的至少一条分类信息相同的内容。 [0119] 可选的,在用户操作第一操作页面后,移动终端可以根据用户在第一操作页面上的操作,呈现第三操作提示项。 第三操作提示项提示用户对第二应用中与n条分类信息中的至少一条分类信息相同的内容进行第一处理。 用户操作第三操作提示项,使得移动终端可以对第二应用中与n条分类信息中的至少一条分类信息相同的内容进行第一处理。 [0120] 可选的,第一处理操作包括取消事件提醒操作和删除操作,或者取消事件提醒操作或删除操作。 [0121] 例如,如图10所示,用户在第一操作页面对第一页面元素进行操作后,移动终端可以向用户呈现如图11所示的第三操作提示项。 如图11所示,第三操作提示项包括提示项“是否取消同一待办事项提醒”和提示项“删除原待办事项记录”。 在用户触发图11所示的提示项后,移动终端进行与用户触发的提示项对应的处理。 例如,在用户触发提示项“是否取消同一待办事件提醒”后,移动终端系统取消明天上午10点A路18号相关事件的提醒,或者 叶敏。 [0122]对第二应用中与m条可分类信息相同的内容进行删除处理,避免重复信息存储,释放移动终端的存储空间。 另外,方便用户阅读和搜索相关内容,提高用户体验。 [0123] 以上结合图2至图11详细描述了根据本申请实施例的候选项呈现方法,下面结合图12详细描述根据本申请实施例的移动终端。 [0124] 图12是移动终端的示意框图 20 根据本申请的一个实施例。 如图12所示,移动终端 20 包括一个接收单元 21 , 一个获取单元 22 , 决定单位 23 , 和一个加法单元 24 . [0125] 接收单位 21 用于接收第一应用的事件通知消息。 [0126] 获取单位 22 用于根据预定义的类模板获取事件通知消息中的n条可分类信息。 n条可分类信息分别对应n个类属性,类模板包括可分类信息与类属性的分类关系,n为大于等于2的整数。 [0127] 决定单位 23 用于根据预设规则根据n类属性确定第二应用。 第二应用包括m类属性,包括m类属性的集合是包括n类属性的集合的子集,m为大于等于2且不大于n的整数。 [0128] 添加单元 24 用于将事件通知消息中的m类属性分别对应的m条可分类信息添加到第二应用中的m类属性中。 [0129] 在本申请实施例中,移动终端可以通过预先定义的类模板获取事件通知消息中包含的多条可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包括至少两个分类信息对应的类别属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个分类信息中的至少两个分类信息添加到第二应用中对应的类属性中。 从而可以降低用户将所有可分类信息逐条添加的操作复杂度,提高信息添加效率,提高用户体验。 [0130] 应该理解为移动端 20 可以用于执行图2所示方法中的流程和/或步骤,为避免重复,此处不再赘述。 [0131] 还应当理解,移动终端 20 这里以功能模块的形式实现。 此处的术语“单元”可以是专用集成电路(ASIC)、电子电路、被配置为执行一个或多个软件或固件的处理器(例如,共享处理器、专用处理器或分组处理器) 程序、存储器、组合逻辑电路和/或用于支持所描述的功能的另一个合适的组件。 [0132] 如图13所示,本申请实施例还提供了一种移动终端 40 . 如图13所示,移动终端 40 可能具体包括射频 (RF) 电路等组件 41 , 一段记忆 42 , 一个输入单元 43 , 显示单元 44 , 一个音频单元 45 , 处理器 46 , 电源 47 , 和一个接口 48. 本领域技术人员可以理解,图13所示移动终端的结构并不构成对移动终端的限制。 移动终端具体可以包括比图13所示更多或更少的组件,或者组合一些组件,或者具有不同的组件排列。 [0133] 射频电路 41 用于接收第一应用的事件通知消息。 处理器 46 用于根据预先定义的类模板获取事件通知消息中的n条可分类信息,所述n条可分类信息分别对应n个类属性,所述类模板包括可分类信息与类的分类关系 属性,n为大于等于2的整数; 根据预设规则,根据n类属性确定第二应用,第二应用包括m类属性,包括m类属性的集合是包括n类属性的集合的子集,m为 大于或等于2且不大于n的整数; 将事件通知消息中的m个类别属性分别对应的m条可分类信息添加到第二应用中的m个类别属性中。 [0134] 因此,在本申请中,移动终端可以通过预定义的类模板获取事件通知消息中包含的多个可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包含一个或多个分类信息对应的类属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个可分类信息中的一个或多个信息添加到第二应用中对应的类别属性中。 从而可以降低用户将所有可分类信息逐条添加的操作复杂度,提高信息添加效率,提高用户体验。 [0135] 应当理解,在本申请实施例中,射频电路 41 可以用于在信息收发过程或通话过程中接收和发送信号。 特别地,在接收到下行链路信号后,RF电路 41 发送下行信号给处理器 46 进行处理,并发送上行信号。 射频电路通常包括但不限于天线、至少一个放大器、收发器、耦合器、低噪声放大器(LNA)、双工器等。 此外,射频电路 41 还可以通过无线通信与网络和另一设备进行通信。 无线通信可以使用任何通信标准或协议,包括但不限于全球移动通信系统(GSM)、通用分组无线电服务(GPRS)、码分多址(CDMA)、宽带码分多址( WCDMA)、长期演进(LTE)、电子邮件、短消息服务(SMS)等。 [0136] 记忆 42 可以被配置为存储软件程序和模块。 处理器 46 通过运行存储在内存中的软件程序和模块进行移动终端的各种功能应用和信号处理 42 . 记忆 42 可以主要包括程序存储区和数据存储区。 程序存储区可以存储智能手机的操作系统、至少一种功能所需的应用程序(例如信息输入功能所需的应用程序,即输入法应用程序、声音播放功能或图像播放功能) 功能)等。 数据存储区可以存储在使用智能手机时创建的数据(例如,当用户使用输入法时创建的词典、音频数据、图像数据或电话簿)等。 此外,内存 42可以包括高速随机存取存储器,或者可以包括非易失性存储器,例如至少一个磁盘存储设备、闪存或另一易失性固态存储设备。 [0137] 输入单元 43 可以用于:接收输入的数字或字符信息,产生与移动终端的用户设置和功能控制相关的按键信号输入。 具体来说,输入单元 43 可能包括触摸屏 431 和另一个输入设备 432 . 触摸屏 431 也称为触摸屏,可以采集触摸操作(例如用户在触摸屏上或触摸屏附近的操作 431 通过使用任何适当的物体或配件,如手指或手写笔)由用户在触摸屏上或触摸屏附近执行 431 ,并通过预设程序驱动相应的连接设备。 可选地,触摸屏 431 可以包括两部分:触摸检测装置和触摸控制器。 触摸检测装置检测用户的触摸位置,检测触摸操作带来的信号,并将该信号传送给触摸控制器。 触摸控制器接收来自触摸检测装置的触摸信息,将触摸信息转换为接触坐标,将接触坐标发送给处理器 46 ,并接收并执行处理器发送的命令 46 . 此外,触摸屏 431 可以采用电阻式、电容式、红外线式、表面声波式等多种方式实现。 另一个输入设备 432 可以包括但不限于物理键盘、功能键(如音量控制键或电源键)、轨迹球、鼠标、摇杆等中的一种或多种。 [0138] 显示器 44 可以用于显示移动终端的各种菜单,以及用户输入的信息或为用户提供的信息。 显示单元 44 可能包括一个显示面板 441 . 可选地,显示面板 441 可以以诸如液晶显示器(LCD)或有机发光二极管(OLED)的形式来配置。 此外,触摸屏 431 可能会覆盖显示面板 441 . 检测到触摸屏上或触摸屏附近的触摸操作后 431 , 触摸屏 431 将触摸操作传送给处理器 46 以确定触摸事件的类型。 然后,处理器 46 在显示面板上提供相应的视觉输出 441 基于触摸事件的类型。 虽然触摸屏 431 和显示面板 441 图13中的智能手机作为两个独立的组件实现输入输出功能,在一些实施例中,触摸屏 431 和显示面板 441 可以集成实现移动终端的输入输出功能。 [0139] 音频单元 45 包括一个音频电路 451 , 一个扬声器 452 , 和一个麦克风 453 . 音频单元 45 可以在用户和移动终端之间提供音频接口。 音频电路 451 可以将接收到的音频数据转换成电信号并将电信号传输到扬声器 452 , 和扬声器 452 将电信号转换为声音信号并输出​​声音信号。 此外,麦克风 453 将采集到的声音信号转换成电信号,音频电路 451 接收电信号,将电信号转换成音频数据,输出音频数据给射频电路 41 将音频数据发送到例如另一个移动终端,或者将音频数据输出到存储器 42 进行进一步处理。 [0140] 处理器 46 是移动终端的控制中心,通过各种接口和线路连接到整个移动终端的各个部分,通过运行或执行存储在内存中的软件程序和模块实现移动终端的各种功能和数据处理 42并通过调用存储在内存中的数据 42 ,实现移动终端的相应功能。 可选地,处理器 46 可能包括一个或多个处理单元。 可选地,应用处理器和调制解调器处理器可以集成到处理器中 46 其中,应用处理器主要处理操作系统、用户界面、应用程序等,调制解调器处理器主要处理无线通信。 可以理解,上述调制解调器处理器可以不集成到处理器中 46 . [0141] 移动终端还包括电源 47 (如电池)为组件供电。 优选地,电源可以逻辑地连接到处理器 46 通过电源管理系统实现充放电管理、用电管理等功能。 [0142] 界面 48 可以用于:连接其他设备,在移动终端与其他设备之间传输数据。 [0143] 可选的,移动终端还可以包括图13中未示出的无线保真(Wi-Fi)模块、蓝牙模块等,本申请实施例不再赘述。 [0144] 应该理解为移动端 40 本申请实施例中可以对应移动终端 20 在本申请实施例中,可以与本申请方法实施例中的移动终端相对应。 为简洁起见,在此不再赘述。 [0145] 应当理解,整个说明书中所提及的“一个实施例”或“一个实施例”是指与该实施例相关的特定特征、结构或特性包含在本申请的至少一个实施例中。 因此,贯穿说明书出现的“在一个实施例中”或“在一个实施例中”并不指代相同的实施例。 此外,这些特定的特征、结构或特性可以通过任何适当的方式组合在一个或多个实施例中。 [0146] 本说明书中的术语“和/或”仅描述了描述关联对象的关联关系,表示可以存在三种关系。 例如,A和/或B可能代表以下三种情况:只有A存在,A和B都存在,只有B存在。 另外,本说明书中的字符“/”一般表示关联对象之间是一种“或”的关系。 [0147] 应当理解,上述过程的序号并不代表本申请各实施例中的执行顺序。 进程的执行顺序应当根据进程的功能和内部逻辑来确定,不应理解为对本申请实施例的实现过程的限制。 [0148] 本领域普通技术人员可以知悉,结合本说明书所公开的实施例中所描述的示例,方法步骤和单元可以通过电子硬件、计算机软件或其组合来实现。 为了清楚地描述硬件和软件之间的互换性,以上根据功能概括地描述了各个实施例的步骤和组成。 这些功能是通过硬件还是软件来实现,取决于技术方案的特定应用和设计约束条件。 对于每个特定的应用,本领域的普通技术人员可以采用不同的方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。 [0149]本说明书所公开的实施例所描述的方法或步骤可以通过硬件、处理器执行的软件程序或其组合来实现。 软件程序可以设置在随机存取存储器(RAM)、存储器、只读存储器(ROM)、电可编程只读存储器(EPROM)、电可擦除可编程只读存储器(EEPROM)、 寄存器、硬盘、可移动磁盘、光盘只读存储器(CD-ROM)或本领域已知的任何其他形式的存储介质。 [0150] 在本申请提供的几个实施例中,应当理解,所公开的系统、装置和方法可以有其他的实现方式。 例如,所描述的装置实施例仅仅是一个示例。 例如,单元划分仅仅是逻辑功能划分,在实际实现中可以是其他划分。 例如,可以将多个单元或组件组合或集成到另一个系统中,或者可以忽略或不执行某些特征。 [0151] 描述为独立组件的单元可以是物理上独立的也可以不是物理上独立的,作为单元显示的组件可以是物理单元也可以不是物理单元,可以位于一个位置,也可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。 [0152] 另外,本申请实施例中的各功能单元可以集成为一个处理单元,也可以各单元在物理上单独存在,或者两个或多个单元集成为一个单元。 [0153] 参照附图并结合优选实施例对本申请进行了详细说明,但并不限于此。 在不脱离本申请的精神和实质的情况下,本领域的普通技术人员可以对本申请中的实施例进行各种等同修改或替换,这些修改或替换均属于本申请保护的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106686240A(String), CN106686240B(String), US10827055B2(String), US20190327356A1(String), WO2018120882A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106686240A(String), CN106686240B(String), US10827055B2(String), US20190327356A1(String), WO2018120882A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10827055B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106686240A(String), CN106686240B(String), US10827055B2(String), US20190327356A1(String), WO2018120882A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.188 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270681(Integer), CN106686240A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270681(Integer), CN106686240B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270681(Integer), US10827055B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270681(Integer), US20190327356A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270681(Integer), WO2018120882A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10827055B2(String), US10827055B2(String), 1604332800(Integer), 270681(Integer), 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185002(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185002(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.290 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.290 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185002(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185002(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.301 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.342 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9814022B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US9814022B2(String), The present invention discloses a network accessing method for a mobile terminal, and a mobile terminal. In some implementations of the present invention, a mobile terminal reads a help request for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 本发明公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一移动终端接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US14/801612(String), 1436976000(Integer), US9814022B2(String), 1509984000(Integer), 1509984000(Integer), 美国(String), 4(Integer), 6(Integer), 17(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185003(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c0fc477214a24e82b572b66eb619c832.png(String), 185003(Integer), c0fc477214a24e82b572b66eb619c832.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US9814022B2(String), The present invention discloses a network accessing method for a mobile terminal, and a mobile terminal. In some implementations of the present invention, a mobile terminal reads a help request for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 本发明公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一移动终端接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US14/801612(String), 1436976000(Integer), US9814022B2(String), 1509984000(Integer), 1509984000(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 17(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2(String), \20230420\c0fc477214a24e82b572b66eb619c832.png(String), 12(Integer), 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 1. A network accessing method for a mobile terminal, comprising:reading a help request for accessing a network by the mobile terminal;establishing a radio resource control (RRC) connection to a base station of the network;applying to the base station to become a base-station mobile terminal;receiving a beacon channel resource, a broadcast channel resource, and an access resource that are allocated by the base station;sending a beacon channel on the beacon channel resource allocated by the base station;sending a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises the access resource; andreceiving an access request of the mobile terminal on the access resource.(String), 1.根据权利要求9所述的非暂时性计算机存储介质,其中接收网络基站分配的信标信道资源、广播信道资源和接入资源的步骤还包括:接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 2. The network accessing method for a mobile terminal according to claim 1, further comprising:connecting the mobile terminal to the network.(String), 12.根据权利要求9所述的非暂时性计算机存储介质,还包括:成为基站移动终端;和向网络发送分配请求。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 3. The network accessing method for a mobile terminal according to claim 1, wherein the steps of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 4. The network accessing method for a mobile terminal according to claim 1, further comprising:becoming a base-station mobile terminal; andsending an allocation request to the network.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 5. A mobile terminal, comprising an input apparatus, an output apparatus, a memory, and a processor, wherein the processor performs the following steps:reading a help request for accessing a network by another mobile terminal;establishing a radio resource control (RRC) connection to a base station of the network;sending a request for becoming a base-station mobile terminal to the network;receiving a beacon channel resource, a broadcast channel resource, and an access resource that are allocated by the base station of the network;sending a beacon channel on the beacon channel resource allocated by the base station of the network;sending a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises the access resource; andreceiving an access request of the another mobile terminal on the access resource after the another mobile terminal synchronizes with the mobile terminal according to the beacon channel, and, after synchronizing with the mobile terminal, reads the broadcast signal to obtain the access resource.(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 6. The mobile terminal according to claim 5, further comprising:connecting the another mobile terminal to the network.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 7. The mobile terminal according to claim 5, wherein the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 8. The mobile terminal according to claim 5, further comprising:becoming a base-station mobile terminal; andsending an allocation request to the network.(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 9. A non-transitory computer storage medium, wherein the computer storage medium stores a program, and the program is configured to perform a network accessing method for a mobile terminal, wherein the method comprises:reading a help request for accessing a network by the mobile terminal;establishing a radio resource control (RRC) connection to a base station of the network;applying to the base station of the network to become a base-station mobile terminal;receiving a beacon channel resource, a broadcast channel resource, and an access resource that are allocated by the base station of the network;sending a beacon channel on the beacon channel resource allocated by the base station;sending a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises the access resource; andreceiving an access request of the mobile terminal on the access resource.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 10. The non-transitory computer storage medium according to claim 9, further comprising:connecting the mobile terminal to the network.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 11. The non-transitory computer storage medium according to claim 9, wherein the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185003(Integer), 12. The non-transitory computer storage medium according to claim 9, further comprising:becoming a base-station mobile terminal; andsending an allocation request to the network.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185003(Integer), [0001]This application is a continuation of International Application No. PCT/CN2013/070522, filed on Jan. 16, 2013, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present invention relates to the field of communications technologies, and specifically, to a network accessing method for a mobile terminal, and a mobile terminal. BACKGROUND [0003]In a current cellular system, a base station includes a macro base station and a micro base station. Because distances from different mobile terminals to the base station are different, interference to different mobile terminals is different, which causes channel quality of different mobile terminals to be different. In addition, in some cases, some mobile terminals may not be covered by a base station, for example, a mobile terminal falls in a coverage hole area, or a base station is damaged for some special reasons, such as an earthquake. Such a mobile terminal that is not covered needs another mobile terminal to help access a network. A mobile terminal that is not covered or weakly covered is defined as an access mobile terminal, and a mobile terminal that can connect to a base station to access a network and can help the access mobile terminal access the network is defined as a base-station mobile terminal. [0004]Because the access mobile terminal needs the base-station mobile terminal to help access a network, the access mobile terminal needs to discover the base-station mobile terminal and also needs to establish a connection to the base-station mobile terminal, and in this way, a final aim of accessing the network by the access mobile terminal can be implemented. Currently, an existing discovering manner for mobile terminals is mainly a manner in which mobile terminals autonomously discover each other. Each mobile terminal sends a beacon channel on a specific resource, so as to discover each other by checking beacon channels of each other. [0005]Because a beacon channel resource is limited, it is necessary to check, before a mobile terminal sends a beacon channel, whether there is a beacon channel resource, and if there is a beacon channel resource, the mobile terminal sends the beacon channel. In this way, a disadvantage of a distributed manner for autonomously using a beacon channel by a mobile terminal is that a mobile terminal may use a beacon channel but does not establish a connection to another mobile terminal, thereby wasting the beacon channel. SUMMARY [0006]Embodiments of the present invention provide a network accessing method for a mobile terminal, and a mobile terminal, which can more effectively use a beacon channel resource. [0007]According to a first aspect, the present invention provides a network accessing method for a mobile terminal, including reading a help request used for accessing a network by the mobile terminal; sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network. [0008]In a first possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0009]In a second possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0010]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes receiving the access request of the mobile terminal on the access resource, and assisting the mobile terminal in completing access to the network. [0011]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0012]In a fifth possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0013]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes receiving the access request of the mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the mobile terminal in completing access to the network. [0014]According to a second aspect, the present invention provides a mobile terminal, including a reading module, configured to read a help request used for accessing a network by another mobile terminal; a broadcasting module, configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and a receiving module, configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0015]In a first possible implementation manner, the broadcasting module includes: a network connecting submodule, configured to establish a RRC connection to the base station of the network, send a request for becoming a base-station mobile terminal to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0016]In a second possible implementation manner, the mobile terminal further includes a base-station module, configured to make the mobile terminal become a base-station mobile terminal; and the broadcasting module includes: a network connecting submodule, configured to send an allocation request to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0017]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the network connecting submodule receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0018]In a fourth possible implementation manner, the broadcasting module includes a network connecting submodule, configured to camp on the base station of the network, acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and a broadcasting submodule, configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0019]With reference to the fourth possible implementation manner, in a fifth possible implementation manner, the network connecting submodule is further configured to, after the receiving module receives the access request, access the base station and request to become a base-station mobile terminal, so as to assist the another mobile terminal in accessing the network. [0020]According to a third aspect, the present invention provides a computer storage medium, where the computer storage medium may store a program, and the program is used to perform the steps according to the first aspect of the present invention or any one of the first to the sixth possible implementation manners of the first aspect. [0021]According to a fourth aspect, the present invention provides a mobile terminal, including an input apparatus, an output apparatus, a memory, and a processor, where the processor performs the following steps: reading a help request used for accessing a network by another mobile terminal; sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network. [0022]In a first possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes establishing a RRC connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0023]In a second possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0024]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes: receiving the access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in completing access to the network. [0025]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step, which is performed by the processor, of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes: receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0026]In a fifth possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0027]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes receiving the access request of the another mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the another mobile terminal in completing access to the network. [0028]According to the network accessing method for a mobile terminal, and the mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that another mobile terminal connects to the mobile terminal on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. BRIEF DESCRIPTION OF DRAWINGS [0029]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0030]FIG. 1 is a schematic diagram of an application environment according to an embodiment of the present invention; [0031]FIG. 2 to FIG. 4 are schematic flowcharts of a network accessing method for a mobile terminal according to embodiments of the present invention; and [0032]FIG. 5 to FIG. 8 are schematic diagrams of a mobile terminal according to embodiments of the present invention. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0033]The following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0034]Referring to FIG. 1, FIG. 1 is a schematic diagram of an application environment of a network accessing method for a mobile terminal according to an embodiment of the present invention. In an implementation manner of the present invention, the network accessing method for a mobile terminal is used in a mobile communications system, for example, a Long Term Evolution (LTE) network, and a network under the 3rd Generation Partnership Project (3GPP). In some implementation manners of the present invention, the network accessing method for a mobile terminal may also be used in a wireless system. A network shown in FIG. 1 is a mobile communications system network, including a base station 30, where the base station 30 includes a macro base station (only one macro base station is used as an example in FIG. 1) and a micro base station (only one micro base station is used as an example in FIG. 1). A mobile terminal 10 is in coverage of the base station 30 and can access a network; and a mobile terminal 20 is not in the coverage of the base station 30, and cannot access the network, and therefore, the mobile terminal 10 is needed to assist the mobile terminal 20 in accessing the network. The mobile terminal 20 that is not covered or weakly covered is defined as an access mobile terminal, and the mobile terminal 10 that can connect to the base station 30 to access the network and can help the access mobile terminal 20 access the network is defined as a base-station mobile terminal. [0035]It should be noted that, in specific implementation, a function of a beacon channel is to make a terminal be discovered by another terminal. Therefore, in specific implementation, a resource allocated by the base station in the present invention is not merely limited to a beacon channel, and code that can be used to discover a terminal can be allocated by the base station in the present invention. That is, in this embodiment of the present invention, a beacon channel is merely used to indicate code used to discover a terminal, but is not used to limit use of other code having a terminal discovering function in this embodiment of the present invention. [0036]It may be understood that, because a base-station mobile terminal and an access mobile terminal move, the base-station mobile terminal may also become an access mobile terminal, and the access mobile terminal may also become a base-station mobile terminal. [0037]With reference to FIG. 1 and referring to FIG. 2, a network accessing method for a mobile terminal according to a first embodiment of the present invention includes: [0038]S201. Read a help request used for accessing a network by the mobile terminal 20. [0039]In this embodiment, the mobile terminal 20 is an access mobile terminal 20 that cannot access a network, and therefore, sends, on an agreed resource, the help request used for accessing a network, where the agreed resource may be, for example, a first timeslot of a frequency. By means of scanning, the mobile terminal 10 reads, on the agreed resource, the help request used for accessing a network by the mobile terminal 20. [0040]S202. Send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. [0041]In some implementation manners of the present invention, the mobile terminal 10 sends the beacon channel on the beacon channel resource allocated by the base station of the network. For example, there are resources of eight subframes from 0 to 7, and a second subframe is idle. In this case, the base station may allocate the second subframe to the mobile terminal 10, and the mobile terminal 10 may send a beacon channel in the second subframe and send a broadcast signal on a broadcast channel resource corresponding to the second subframe, for example, a third subframe, where the broadcast signal includes an access resource, for example, a fifth subframe. [0042]S203. Receive an access request of the mobile terminal 20 on the access resource, and assist the mobile terminal 20 in accessing the network. [0043]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0044]With reference to FIG. 1 and referring to FIG. 3, a network accessing method for a mobile terminal according to a second embodiment of the present invention includes: [0045]S301. The access mobile terminal 20 sends a request for requesting the mobile terminal 10 to help access a network. [0046]S302. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0047]S303. The mobile terminal 10 establishes a radio resource control (RRC) protocol connection to the base station 30 of the network, and sends a request for becoming a base-station mobile terminal to the base station 30. [0048]In this embodiment of the present invention, if the mobile terminal 10 intends to become a base-station mobile terminal after reading the help request of the access mobile terminal 20, the mobile terminal 10 sends the request for becoming a base-station mobile terminal to the base station 30. [0049]In some embodiments of the present invention, the mobile terminal 10 may also have become a base-station mobile terminal; in this case, the mobile terminal 10 sends only an allocation request to the base station 30. [0050]S304. The base station 30 allocates a beacon channel resource, a broadcast channel resource, and an access resource to the mobile terminal 10. [0051]In this embodiment of the present invention, the base station 30 allocates the beacon channel resource, the broadcast channel resource, and the access resource to the mobile terminal 10 by using radio resource control protocol signaling. [0052]In some implementation manners of the present invention, the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station 30 include a timeslot resource, a frequency resource, a code channel resource, and the like. [0053]In this case, the mobile terminal 10 becomes a base-station mobile terminal. [0054]S305. The mobile terminal 10 sends a beacon channel on the beacon channel resource allocated by the base station 30, and sends a broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0055]Step S303 to S305 are specific implementation steps of step S202 in FIG. 2. [0056]S306. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0057]S307. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0058]After receiving the access request of the access mobile terminal 20, the base-station mobile terminal 10 may help the access mobile terminal 20 complete access to the network, that is, the base station 30. [0059]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station 30, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0060]With reference to FIG. 1 and referring to FIG. 4, a network accessing method for a mobile terminal according to a third embodiment of the present invention includes: [0061]S401. The access mobile terminal 20 sends a request for requesting the base-station mobile terminal 10 to help access a network. [0062]S402. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0063]S403. The mobile terminal 10 camps on the base station 30, and acquires a beacon channel resource set and an access resource set by means of broadcast of the base station 30. [0064]S404. The mobile terminal 10 sends a beacon channel on an idle beacon channel resource in the beacon channel resource set, and sends a broadcast signal on a broadcast channel resource, where the broadcast signal includes an access resource. [0065]The mobile terminal 10 checks whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, and if there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the mobile terminal 10 sends the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sends the broadcast signal on a corresponding broadcast channel resource, where the broadcast signal includes the access resource. [0066]Step S403 to step S404 are specific implementation manners of step S202 in FIG. 2. [0067]S405. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0068]S406. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0069]S407. The mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, so as to assist the access mobile terminal in completing access to the network. [0070]According to the network accessing method for a mobile terminal, it is checked whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the beacon channel is sent on the idle beacon channel resource in the beacon channel resource set, and the broadcast signal is sent on a broadcast channel resource corresponding to the idle beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses a network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. In addition, only after receiving the access request of the access mobile terminal 20, the mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, thereby avoiding a waste of a resource. [0071]To better implement the foregoing solutions in the embodiments of the present invention, a related apparatus configured to cooperate to implement the foregoing solutions is provided in the following. [0072]Referring to FIG. 5, a mobile terminal 50 according to an embodiment of the present invention includes a reading module 500, a broadcasting module 510, and a receiving module 520. The reading module 500 is configured to read a help request used for accessing a network by another mobile terminal. The another mobile terminal is not covered by a network or weakly covered by a network, and therefore the another mobile terminal requests the mobile terminal 50 to help access the network. [0073]The broadcasting module 510 is configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The receiving module 520 is configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0074]Referring to FIG. 6, the broadcasting module 510 includes a network connecting submodule 511 and a broadcasting submodule 512. [0075]In some implementation manners of the present invention, the network connecting submodule 511 is configured to send a request for becoming a base-station mobile terminal to the network and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network. The broadcasting submodule 512 is configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0076]In some implementation manners of the present invention, the network connecting submodule 511 receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0077]In some implementation manners of the present invention, the network connecting submodule 511 is configured to camp on the base station of the network, and acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes the idle beacon channel resource, and the access resource set includes the access resource. The broadcasting submodule 512 is configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes the access resource. [0078]In some implementation manners of the present invention, the network connecting submodule 511 is further configured to, after the receiving module receives the access request, access the base station and request to become a base-station mobile terminal, so as to assist the another mobile terminal in accessing the network. [0079]It may be understood that the mobile terminal 50 in this embodiment may be, for example, a computer, a mobile phone, or a tablet computer. [0080]It may be understood that, functions of all function modules of the mobile terminal 50 in this embodiment may be specifically implemented according to the methods in the foregoing first(String), [0001] 本申请是 2013 年 1 月 16 日提交的国际申请号 PCT/CN2013/070522 的延续,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及通信技术领域,具体涉及一种移动终端的网络接入方法及移动终端。 背景 [0003] 在目前的蜂窝系统中,基站包括宏基站和微基站。 由于不同移动终端到基站的距离不同,对不同移动终端的干扰不同,从而导致不同移动终端的信道质量不同。 另外,在某些情况下,一些移动终端可能不在基站的覆盖范围内,例如移动终端落入覆盖盲区,或者由于地震等特殊原因导致基站损坏等。 这种未被覆盖的移动终端需要另外的移动终端帮助接入网络。 将未覆盖或弱覆盖的移动终端定义为接入移动终端,能够连接基站接入网络并帮助接入移动终端接入网络的移动终端定义为基站 移动终端。 [0004] 由于接入移动终端需要基站移动终端帮助接入网络,因此接入移动终端需要发现基站移动终端,同时也需要与基站移动终端建立连接,这种方式 ,可以实现接入移动终端接入网络的最终目的。 目前,现有的移动终端发现方式主要是移动终端自主发现对方的方式。 每个移动终端在特定资源上发送信标信道,以便通过检查彼此的信标信道来相互发现。 [0005] 由于信标信道资源有限,移动终端在发送信标信道之前,需要检查是否有信标信道资源,如果有信标信道资源,则移动终端发送信标信道。 这样,移动终端自主使用信标信道的分布式方式的缺点是移动终端可以使用信标信道但不与其他移动终端建立连接,从而浪费信标信道。 概括 [0006] 本发明实施例提供一种移动终端的网络接入方法及移动终端,能够更有效地利用信标信道资源。 [0007] 第一方面,本发明提供一种移动终端的网络接入方法,包括读取移动终端接入网络的帮助请求; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收移动终端对接入资源的接入请求,协助移动终端接入网络。 [0008] 在第一种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源还包括与网络基站建立无线资源控制(Radio Resource Control,无线资源控制)连接,向网络发送成为基站移动终端的请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0009]在第二种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源进一步包括成为基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0010] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,接收所述移动终端对所述接入资源的接入请求,并协助所述移动终端接入网络的步骤还包括接收所述接入请求 接入资源上的移动终端,辅助移动终端完成接入网络。 [0011] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述接收网络基站分配的信标信道资源、广播信道资源和接入资源的步骤还包括接收 网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0012] 在第五种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源进一步包括驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲的信标信道资源,所述 访问资源集包括访问资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0013] 结合第五种可能的实现方式,在第六种可能的实现方式中,所述接收移动终端对接入资源的接入请求,并协助移动终端接入网络的步骤还包括接收移动终端的接入请求。 访问资源上的终端; 接入基站并请求成为基站移动终端,以辅助移动终端完成入网。 [0014] 第二方面,本发明提供了一种移动终端,包括:读取模块,用于读取其他移动终端接入网络的帮助请求; 广播模块,用于在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源; 接收模块,用于接收所述另一移动终端对所述接入资源的接入请求,协助所述另一移动终端接入网络。 [0015]在第一种可能的实现方式中,所述广播模块包括: 网络连接子模块,用于与网络基站建立RRC连接,向网络发送成为基站移动终端的请求,并接收beacon 网络基站分配的信道资源、广播信道资源和接入资源; 广播子模块,用于在网络基站分配的信标信道资源上发送信标信道,并在广播信道资源上发送广播信号,广播信号包括接入资源。 [0016] 在第二种可能的实现方式中,所述移动终端还包括基站模块,用于使所述移动终端成为基站移动终端; 广播模块包括:网络连接子模块,用于向网络发送分配请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块,用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号中包括接入资源。 [0017] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,网络连接子模块接收网络基站通过使用 无线电资源控制协议信令。 [0018] 在第四种可能的实现方式中,广播模块包括网络连接子模块,用于驻留在网络的基站上,通过基站的广播获取信标信道资源集和接入资源集,其中,所述beacon 信道资源集包括空闲信标信道资源,接入资源集包括接入资源; 广播子模块,用于在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号包括接入资源 . [0019] 结合第四种可能的实现方式,在第五种可能的实现方式中,网络连接子模块还用于接收模块接收到接入请求后,接入基站,请求成为基站移动终端,因此 以协助其他移动终端接入网络。 [0020] 第三方面,本发明提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行本发明第一方面或第一至至任意一项所述的步骤。 第一方面的第六种可能的实现方式。 [0021] 第四方面,本发明提供一种移动终端,包括输入装置、输出装置、存储器和处理器,所述处理器执行以下步骤: 读取另一移动设备接入网络的帮助请求 终端; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0022]在第一种可能的实现方式中,所述处理器执行在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号的步骤 信道资源,其中广播信号包括接入资源还包括与网络基站建立RRC连接,向网络发送成为基站移动终端的请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0023] 在第二种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括成为基站的移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0024] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述处理器接收所述另一移动终端对所述接入资源的接入请求,并协助所述另一移动终端执行的步骤 接入网络还包括:接收另一移动终端对接入资源的接入请求,协助另一移动终端完成接入网络。 [0025] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述处理器接收所述处理器分配的信标信道资源、广播信道资源和接入资源的步骤。 网络基站还包括:接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0026] 在第五种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括 空闲信标信道资源,接入资源集合包括接入资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0027] 结合第五种可能的实现方式,在第六种可能的实现方式中,所述处理器接收所述其他移动终端对所述访问资源的访问请求,协助所述其他移动终端访问所述访问资源。 网络还包括接收另一移动终端对接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0028]一种移动终端入网方法及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在信标对应的广播信道资源上发送 channel resource,指示接入资源,以便其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入资源。 附图说明 [0029] 为更加清楚地描述本发明实施例中的技术方案,下面对实施例描述中所需要的附图进行简单介绍。 显然,以下描述中的附图仅仅是本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0030] 图1为本发明实施例的应用环境示意图; [0031] 图2至图4是根据本发明实施例的移动终端的网络接入方法的流程示意图; 和 [0032] 图5至图8是根据本发明实施例的移动终端的示意图。 说明性实施例的详细说明 [0033] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 显然,所描述的实施例仅仅是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0034] 请参阅图1,图1为本发明实施例提供的移动终端的网络接入方法的应用环境示意图。 在本发明的一个实施方式中,所述移动终端的入网方法用于移动通信系统,例如长期演进(LTE)网络、第三代合作伙伴计划(3GPP)下的网络。 在本发明的一些实施方式中,该移动终端的网络接入方法还可以用于无线系统中。 图1所示网络为移动通信系统网络,包括基站 30 ,其中基站 30 包括宏基站(图1中仅以一个宏基站为例)和微基站(图1中仅以一个微基站为例)。 移动终端 10 在基站覆盖范围内 30 并且可以访问网络; 和移动终端 20 不在基站覆盖范围内 30 , 无法上网, 因此, 移动终端 10 需要移动端辅助 20 在访问网络时。 手机端 20 未覆盖或弱覆盖定义为接入移动终端,移动终端 10 可以连接到基站 30 接入网络,可以帮助接入移动终端 20 接入网络的移动终端被定义为基站。 [0035] 需要说明的是,在具体实现中,信标信道的作用是使一个终端被另一个终端发现。 因此,在具体实施中,本发明基站分配的资源并不仅限于信标信道,本发明基站可以分配可用于发现终端的代码。 即本发明实施例中,信标信道仅用于指示用于发现终端的代码,并不用于限制本发明实施例中使用其他具有终端发现功能的代码。 [0036]可以理解的是,由于基站移动终端和接入移动终端移动,因此基站移动终端也可能成为接入移动终端,接入移动终端也可能成为基站移动终端。 [0037] 结合图1并参考图2,本发明实施例一提供的一种移动终端的网络接入方法包括: [0038] 小号 201 . 读取移动终端接入网络的帮助请求 20 . [0039] 本实施例中,移动终端 20 是接入移动终端 20 无法接入网络,因此在约定的资源上发送用于接入网络的帮助请求,该约定的资源例如可以是频率的第一时隙。 手机端扫一扫 10 在约定的资源上读取移动终端接入网络的帮助请求 20 . [0040] 小号 202 . 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0041] 在本发明的一些实施方式中,移动终端 10 在网络基站分配的信标信道资源上发送信标信道。 例如,0到7有8个子帧的资源,第二个子帧空闲。 在这种情况下,基站可以将第二子帧分配给移动终端 10 , 和移动端 10 可以在第二子帧发送信标信道,在第二子帧对应的广播信道资源,例如第三子帧上发送广播信号,该广播信号包括接入资源,例如第五子帧。 [0042] 小号 203 . 接收移动终端的访问请求 20 在接入资源上,协助移动终端 20 在访问网络时。 [0043] 该移动终端的入网方法,在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,以指示 访问资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0044] 结合图1并参考图3,本发明实施例二提供的一种移动终端的网络接入方法包括: [0045] 小号 301 . 接入移动终端 20 发送请求移动端的请求 10 帮助访问网络。 [0046] 小号 302 . 移动端 10 读取接入移动端的帮助请求 20 . [0047] 小号 303 . 移动端 10 建立到基站的无线资源控制 (RRC) 协议连接 30 向基站发送成为基站移动终端的请求 30 . [0048] 本发明实施例中,如果移动终端 10 读取接入移动终端的帮助请求后,打算成为基站移动终端 20 , 移动端 10 向基站发送成为基站移动终端的请求 30 . [0049] 在本发明的一些实施例中,移动终端 10 也可能成为基站移动终端; 在这种情况下,移动端 10 只向基站发送分配请求 30 . [0050] 小号 304 . 基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源10 . [0051] 本发明实施例中,基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源 10 通过使用无线电资源控制协议信令。 [0052] 在本发明的一些实施方式中,基站分配的信标信道资源、广播信道资源和接入资源 30 包括时隙资源、频率资源、码道资源等。 [0053] 在这种情况下,移动端 10 成为基站移动终端。 [0054] 小号 305 . 手机端 10 在基站分配的信标信道资源上发送信标信道 30 ,在广播信道资源上发送广播信号,广播信号中包含接入资源。 [0055] 脚步 303 到小号 305 是步骤S的具体实现步骤 202 在图 2 中。 [0056] 小号 306 . 接入移动终端 20 搜索信标信道,与移动终端同步 10 ,从而读取广播信号,并从广播信号中读取接入资源。 [0057] 小号 307 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0058] 收到接入移动终端的接入请求后 20 , 基站移动终端 10 可以帮助接入移动终端 20 完全接入网络,即基站 30 . [0059] 一种移动终端入网方法,所述信标信道在基站分配的信标信道资源上发送 30 ,在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0060] 结合图1并参考图4,本发明实施例三提供的一种移动终端的网络接入方法包括: [0061] 小号 401 . 接入移动终端 20 发送请求基站移动终端的请求 10 帮助访问网络。 [0062] 小号 402 . 手机端 10 读取接入移动端的帮助请求 20 . [0063] 小号 403 . 手机端 10 基站上的营地 30 , 通过基站的广播获取信标信道资源集和接入资源集 30 . [0064] 小号 404 . 手机端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,在广播信道资源上发送广播信号,该广播信号包括接入资源。 [0065] 手机端 10 检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30 , 如果基站广播的信标信道资源集合中有空闲的信标信道资源 30 , 移动端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在相应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0066] 脚步 403 到步骤 S 404 是步骤S的具体实现方式 202 在图 2 中。 [0067] 小号 405 . 接入移动终端 20 搜索信标信道,与移动终端同步 10,从而读取广播信号,并从广播信号中读取接入资源。 [0068] 小号 406 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0069] 小号 407 . 手机端 10 接入基站 30 请求成为基站移动终端,以协助接入移动终端完成入网。 [0070] 一种移动终端入网方法,检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30 ,信标信道在信标信道资源集合中的空闲信标信道资源上发送,广播信号在空闲信标信道资源对应的广播信道资源上发送,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 另外,只有在接收到接入移动终端的接入请求后 20 , 移动端 10 接入基站 30 请求成为基站移动终端,避免资源浪费。 [0071] 为了更好的实施本发明实施例的上述方案,下面提供一种用于配合实施上述方案的相关装置。 [0072] 参见图5,移动终端 50 根据本发明的实施例包括读取模块 500 , 广播模块 510 , 和一个接收模块 520 . 阅读模块 500 用于读取其他移动终端接入网络的帮助请求。 另一移动终端未被网络覆盖或弱网络覆盖,因此另一移动终端请求该移动终端 50 以帮助访问网络。 [0073] 广播模块 510 用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 接收模块 520 用于接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0074] 参见图6,广播模块 510 包括一个网络连接子模块 511 和一个广播子模块 512 . [0075] 在本发明的一些实施方式中,网络连接子模块 511 用于向网络发送成为基站移动终端的请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0076] 在本发明的一些实施方式中,网络连接子模块 511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0077] 在本发明的一些实施方式中,网络连接子模块 511 用于驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲信标信道资源和接入资源 set 包括访问资源。 广播子模块 512用于在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0078] 在本发明的一些实施方式中,网络连接子模块 511 还用于接收模块接收到接入请求后,接入基站并请求成为基站移动终端,以辅助其他移动终端接入网络。 [0079] 可以理解为移动端 50 本实施例中例如可以为电脑、手机或平板电脑。 [0080] 可以理解为,移动终端的所有功能模块的功能 50 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0081] 上述移动终端 50 在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 50 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0082] 参考图7,移动终端之间的区别 70 根据本发明实施例的移动终端 50 图5所示为基站模块 700 除了阅读模块外,还包括 500 , 广播模块 510 , 和一个接收模块 520 , 其中阅读模块 500 ,广播模块 510 , 接收模块 520 与图5所示的相应模块基本相同,在此不再赘述。 基站模块 700 配置为使移动端 70 成为基站移动终端。 [0083] 广播模块 510 还包括网络连接子模块 511 和广播子模块 512 如图6所示,其中网络连接子模块 511 用于向网络端发送分配请求,接收网络端基站分配的信标信道资源、广播信道资源和接入资源; 和广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0084] 在本发明的一些实施方式中,网络连接子模块 511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0085] 可以理解为移动端 70 本实施例中例如可以为电脑、手机或平板电脑。 [0086] 可以理解为,移动终端的所有功能模块的功能 70 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0087] 上述移动终端 70在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 70 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0088] 本发明实施例还提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行上述方法中描述的移动终端上网方法的部分或全部步骤。 实施例。 [0089] 参见图8,本发明实施例还提供了一种移动终端 80 ,包括一个处理器 810 , 一段记忆 800 , 输入设备 820 , 和一个输出设备 830 (可能有一个或多个处理器 810 在移动端 80 ,图8中以一个处理器为例)。 在本发明的一些实施例中,输入装置 820 , 输出设备 830 , 记忆 800 , 和处理器 810 可以通过使用总线或以其他方式相互连接。 图8中以它们通过总线连接为例。 [0090] 处理器 810 执行以下步骤: 读取另一移动终端用于接入网络的帮助请求; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0091] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:发送 请求成为网络的基站移动终端; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0092] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:成为一个 基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0093] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络还包括:接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络。 完成对网络的访问。 [0094] 在本发明的一些实施方式中,所述步骤由处理器执行 810接收网络基站分配的信标信道资源、广播信道资源和接入资源还包括:接收网络基站分配的信标信道资源、广播信道资源和接入资源。 网络的基站通过使用无线资源控制协议信令。 [0095] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,还包括:驻留在 网络的基站,通过基站广播获取信标信道资源集和接入资源集,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源 ; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0096] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收所述另一移动终端对所述接入资源的接入请求,协助所述另一移动终端接入网络还包括:接收所述另一移动终端对所述接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0097] 可以理解为,移动终端的所有功能模块的功能 80 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0098] 需要说明的是,为便于描述,上述方法实施例均以一系列动作进行描述。 然而,本领域的技术人员应该理解,本发明不限于所描述的动作顺序,因为根据本发明,一些步骤可以以不同的顺序或同时执行。 其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本发明所必须的。 [0099] 在上述实施例中,对各个实施例的描述都各有侧重。 一个实施例中没有详述的部分,可以参见其他实施例的相关描述。 [0100] 综上所述,根据移动终端的入网方法,以及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在相应的广播信道资源上发送 到信标信道资源,指示接入资源,使得其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入 资源。 [0101] 本领域普通技术人员可以理解,上述实施例中方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 存储介质可以包括:只读存储器、随机存取存储器、磁盘或光盘。 [0102]以上对本发明实施例提供的移动终端的网络接入方法及移动终端进行了详细描述。 本说明书中采用具体的例子来说明本发明的原理和实施方式。 上述实施例只是为了帮助理解本发明的方法和核心思想。 此外,对于实施方式和适用范围,本领域的普通技术人员可以根据本发明的思想进行修改。 总之,说明书不应理解为对本发明的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9814022B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), CN104303526A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), CN104303526B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), EP2947901A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), EP2947901A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), EP2947901B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), EP3624471A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), EP3624471B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), US10200973B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), US20150327216A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), US20180054802A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), US9814022B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270682(Integer), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9814022B2(String), US9814022B2(String), 1509984000(Integer), 270682(Integer), 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), 华为技术有限公司(String), 0(Integer), 1681975553(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.656 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185003(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75946(Integer), 1(Integer), 185003(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185003(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185003(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.696 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10200973B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.712 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.712 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.712 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US10200973B2(String), Embodiments disclose a network accessing method for a mobile terminal, and a mobile terminal. In some implementation manners of the present invention, a mobile terminal reads a help request used for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 实施例公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一个移动终端用于接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US15/796502(String), 1509033600(Integer), US10200973B2(String), 1549296000(Integer), 1549296000(Integer), 美国(String), 4(Integer), 6(Integer), 19(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | CN102844993A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2 | US9814022B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185004(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.725 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.725 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\1f15957c6ace411db44db03477630094.png(String), 185004(Integer), 1f15957c6ace411db44db03477630094.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.732 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US10200973B2(String), Embodiments disclose a network accessing method for a mobile terminal, and a mobile terminal. In some implementation manners of the present invention, a mobile terminal reads a help request used for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 实施例公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一个移动终端用于接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US15/796502(String), 1509033600(Integer), US10200973B2(String), 1549296000(Integer), 1549296000(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 19(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | CN102844993A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2 | US9814022B2(String), \20230420\1f15957c6ace411db44db03477630094.png(String), 20(Integer), 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.744 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 1. A method, comprising:reading, by a first mobile terminal, a help request for accessing a network, wherein the help request is sent by a second mobile terminal;in response to reading the help request, and in response to a determination that the first mobile terminal will allow the second mobile terminal to communicate with the network using a network connection of the first mobile terminal, sending, by the first mobile terminal, a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises an access resource; andreceiving, by the first mobile terminal, an access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 1.一种方法,包括:第一移动终端读取第二移动终端发送的入网帮助请求;响应于读取帮助请求,并且响应于确定第一移动终端将允许第二移动终端使用第一移动终端的网络连接与网络通信,由第一移动终端发送信标在网络基站分配的信标信道资源上信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源;和第一移动终端接收第二移动终端对接入资源的接入请求,允许第二移动终端利用第一移动终端的网络连接与网络进行通信。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 2. The method according to claim 1, wherein sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises:establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, wherein the broadcast signal comprises the access resource.(String), 2.根据权利要求1所述的方法,其中在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,包括:与网络基站建立无线资源控制(RRC)连接,向网络发送成为基站移动终端的请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,以及在广播信道资源上发送广播信号,其中广播信号包括接入资源。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 3. The method according to claim 2, wherein receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises:receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 3.根据权利要求2所述的方法,其中接收第二移动终端对接入资源的接入请求,允许第二移动终端利用第一移动终端的网络连接与网络进行通信,包括:接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 4. The method according to claim 2, wherein receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network using radio resource control protocol signaling.(String), 4.根据权利要求2所述的方法,其中接收网络基站分配的信标信道资源、广播信道资源和接入资源包括:接收网络基站使用无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.747 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 5. The method according to claim 1, wherein sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises:becoming a base-station mobile terminal;sending an allocation request to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, wherein the broadcast signal comprises the access resource.(String), 5.根据权利要求1所述的方法,其中在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,包括:成为基站移动终端;向网络发送分配请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,以及在广播信道资源上发送广播信号,其中广播信号包括接入资源。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 6. The method according to claim 1, wherein sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, further comprises:camping on the base station the network, and acquiring a beacon channel resource set and an access resource set from a broadcast of the base station, wherein the beacon channel resource set comprises an idle beacon channel resource, and the access resource set comprises the access resource; andsending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, wherein the broadcast signal comprises the access resource.(String), 6.根据权利要求1所述的方法,其中在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,还包括:基站驻留网络,从基站的广播中获取信标信道资源集和接入资源集,其中,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源;和在信标信道资源集合中的空闲信标信道资源上发送信标信道,以及在空闲信标信道资源对应的广播信道资源上发送广播信号,其中广播信号包括接入资源。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 7. The network accessing method for a mobile terminal according to claim 6, wherein receiving the access request of the mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises:receiving the access request of the mobile terminal on the access resource; andaccessing the base station and requesting to become a base-station mobile terminal, to allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 7.根据权利要求6所述的移动终端的网络接入方法,其中接收移动终端对接入资源的接入请求,允许第二移动终端利用第一移动终端的网络连接与网络进行通信,包括:接收移动终端对接入资源的接入请求;和接入基站并请求成为基站移动终端,以允许第二移动终端使用第一移动终端的网络连接与网络进行通信。8、一种移动终端,用于作为第一移动终端,该移动终端包括:输入装置;输出装置;非暂时性记忆;和一个处理器,配置为:读取入网帮助请求,该帮助请求由第二移动终端发送;响应于读取帮助请求,并且响应于第一移动终端将允许第二移动终端使用第一移动终端的网络连接与网络通信的确定,在分配的信标信道资源上发送信标信道通过网络的基站,在与信标信道资源对应的广播信道资源上发送广播信号,其中广播信号包括接入资源;和接收第二移动终端对接入资源的接入请求,并允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 8. A mobile terminal, configured to act as a first mobile terminal, the mobile terminal comprising:an input apparatus;an output apparatus;a non-transitory memory; anda processor, configured to:read a help request for accessing a network, wherein the help request is sent by a second mobile terminal;in response to reading the help request, and is response to a determination that the first mobile terminal will allow the second mobile terminal to communicate with the network using a network connection of the first mobile terminal, send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises an access resource; andreceive an access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 9.根据权利要求8所述的移动终端,其中所述处理器,用于在所述网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,包括所述处理器,用于:与网络基站建立无线资源控制(RRC)连接,向网络发送成为基站移动终端的请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 9. The mobile terminal according to claim 8, wherein the processor being configured to send a beacon channel on the beacon channel resource allocated by the base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, comprises the processor being configured to:establish a radio resource control (RRC) connection to the base station of the network, and send a request for becoming a base-station mobile terminal to the network;receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsend the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource.(String), 10.根据权利要求9所述的移动终端,其中处理器,用于接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信,包括处理器,用于:接收第二移动终端对接入资源的接入请求,并允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 10. The mobile terminal according to claim 9, wherein the processor being configured to receive an access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises the processor being configured to:receive the access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 11.根据权利要求9所述的移动终端,其中处理器,用于接收网络基站分配的信标信道资源、广播信道资源和接入资源,包括处理器,用于:接收网络基站使用无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 11. The mobile terminal according to claim 9, wherein the processor being configured to receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network, comprises the processor being configured to:receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network using radio resource control protocol signaling.(String), 12.根据权利要求8所述的移动终端,其中处理器,用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,包括处理器,用于:成为基站移动终端;向网络发送分配请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 12. The mobile terminal according to claim 8, wherein the processor being configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the processor being configured to:become a base-station mobile terminal;send an allocation request to the network;receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsend the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource.(String), 13.根据权利要求8所述的移动终端,其中处理器,用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,包括处理器,用于:驻留在网络的基站,从基站的广播中获取信标信道资源集和接入资源集,其中,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源;和在信标信道资源集合中的空闲信标信道资源上发送信标信道,在空闲信标信道资源对应的广播信道资源上发送广播信号。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.748 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 13. The mobile terminal according to claim 8, wherein the processor being configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the processor being configured to:camp on the base station of the network, and acquire a beacon channel resource set and an access resource set from a broadcast of the base station, wherein the beacon channel resource set comprises an idle beacon channel resource, and the access resource set comprises the access resource; andsend the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource.(String), 14.根据权利要求13所述的移动终端,其中处理器,用于接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信,包括处理器,用于:接收第二移动终端对接入资源的接入请求;和接入基站并请求成为基站移动终端,以允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 12(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 14. The mobile terminal according to claim 13, wherein the processor being configured to receive an access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises the processor being configured to:receive the access request of the second mobile terminal on the access resource; andaccess the base station and request to become a base-station mobile terminal, to allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 15.非暂时性计算机存储介质,其中非暂时性计算机存储介质存储程序,该程序包括用于:读取第二移动终端发送的入网帮助请求;响应于读取帮助请求,并且响应于确定第一移动终端将允许第二移动终端使用第一移动终端的网络连接与网络通信,在分配的信标信道资源上发送信标信道通过网络的基站,在与信标信道资源对应的广播信道资源上发送广播信号,其中广播信号包括接入资源;和接收第二移动终端对接入资源的接入请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 15. A non-transitory computer storage medium, wherein the non-transitory computer storage medium stores a program, and the program comprises instructions for:reading a help request for accessing a network, wherein the help request is sent-by a second mobile terminal;in response to reading the help request, and in response to a determination that a first mobile terminal will allow the second mobile terminal to communicate with the network using a network connection of the first mobile terminal, sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises an access resource; andreceiving an access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 16.根据权利要求15所述的非暂时性计算机存储介质,其中包括用于在网络的基站分配的信标信道资源上发送信标信道以及在与信标信道资源对应的广播信道资源上发送广播信号的指令的程序包括用于以下指令的程序:与网络基站建立无线资源控制(RRC)连接,向网络发送成为基站移动终端的请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 16. The non-transitory computer storage medium according to claim 15, wherein the program including instructions for sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the program including instructions for:establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource.(String), 17.根据权利要求16所述的非暂时性计算机存储介质,其中包括用于接收第二移动终端对访问资源的访问请求并允许第二移动终端使用第一移动终端的网络连接与网络通信的指令的程序包括用于:接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 17. The non-transitory computer storage medium according to claim 16, wherein the program including instructions for receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises the program including instructions for:receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 18.根据权利要求16所述的非暂时性计算机存储介质,其中包括用于接收由网络的基站分配的信标信道资源、广播信道资源和接入资源的指令的程序包括用于以下指令的程序:接收网络基站使用无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 18. The non-transitory computer storage medium according to claim 16, wherein the program including instructions for receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network, comprises the program including instructions for:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network using radio resource control protocol signaling.(String), 19.根据权利要求15所述的非暂时性计算机存储介质,其中包括用于在网络的基站分配的信标信道资源上发送信标信道以及在与信标信道资源对应的广播信道资源上发送广播信号的指令的程序包括用于以下指令的程序:成为基站移动终端;向网络发送分配请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 19. The non-transitory computer storage medium according to claim 15, wherein the program including instructions for sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the program including instructions for:becoming a base-station mobile terminal;sending an allocation request to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource.(String), 20.根据权利要求15所述的非暂时性计算机存储介质,其中包括用于在网络的基站分配的信标信道资源上发送信标信道以及在与信标信道资源对应的广播信道资源上发送广播信号的指令的程序包括用于以下指令的程序:基站驻留网络,通过基站的广播获取信标信道资源集和接入资源集,其中,所述信标信道资源集包括空闲信标信道资源,所述接入资源集包括接入资源;和在信标信道资源集合中的空闲信标信道资源上发送信标信道,在空闲信标信道资源对应的广播信道资源上发送广播信号。(String), 1(Integer), 18(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.749 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185004(Integer), 20. The non-transitory computer storage medium according to claim 15, wherein the program including instructions for sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the program including instructions for:camping on the base station the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, wherein the beacon channel resource set comprises an idle beacon channel resource, and the access resource set comprises the access resource; andsending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource.(String), 1(Integer), 19(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185004(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 14/801,612, filed on Jul. 16, 2015, now U.S. Pat. No. 9,814,022, which is a continuation of International Application No. PCT/CN2013/070522, filed on Jan. 16, 2013. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present invention relates to the field of communications technologies, and specifically, to a network accessing method for a mobile terminal, and a mobile terminal. BACKGROUND [0003]In a current cellular system, a base station includes a macro base station and a micro base station. Because distances from different mobile terminals to the base station are different, interference to different mobile terminals is different, which causes that channel quality of different mobile terminals is different. In addition, in some cases, some mobile terminals may not be covered by a base station, for example, a mobile terminal falls in a coverage hole area, or a base station is damaged for some special reasons, such as an earthquake. Such a mobile terminal that is not covered needs another mobile terminal to help access a network. A mobile terminal that is not covered or weakly covered is defined as an access mobile terminal, and a mobile terminal that can connect to a base station to access a network and can help the access mobile terminal access the network is defined as a base-station mobile terminal. [0004]Because the access mobile terminal needs the base-station mobile terminal to help access a network, the access mobile terminal needs to discover the base-station mobile terminal and also needs to establish a connection to the base-station mobile terminal, and in this way, a final aim of accessing the network by the access mobile terminal can be implemented. Currently, an existing discovering manner for mobile terminals is mainly a manner in which mobile terminals autonomously discover each other. Each mobile terminal sends a beacon channel on a specific resource, so as to discover each other by checking beacon channels of each other. [0005]Because a beacon channel resource is limited, it is necessary to check, before a mobile terminal sends a beacon channel, whether there is a beacon channel resource, and if there is a beacon channel resource, the mobile terminal sends the beacon channel. In this way, a disadvantage of a distributed manner for autonomously using a beacon channel by a mobile terminal is that a mobile terminal may use a beacon channel but does not establish a connection to another mobile terminal, thereby wasting the beacon channel. SUMMARY [0006]Embodiments of the present invention provide a network accessing method for a mobile terminal, and a mobile terminal, which can more effectively use a beacon channel resource. [0007]According to a first aspect, embodiments of the present invention provide a network accessing method for a mobile terminal. The method includes reading a help request used for accessing a network by the mobile terminal. The method also includes sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The method also includes receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network. [0008]In a first possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0009]In a second possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0010]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes: receiving the access request of the mobile terminal on the access resource, and assisting the mobile terminal in completing access to the network. [0011]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes: receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0012]In a fifth possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0013]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes: receiving the access request of the mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the mobile terminal in completing access to the network. [0014]According to a second aspect, embodiments of the present invention provide a mobile terminal. The mobile terminal includes a reading module, configured to read a help request used for accessing a network by another mobile terminal. The mobile terminal also includes a broadcasting module, configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The mobile terminal also includes a receiving module, configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0015]In a first possible implementation manner, the broadcasting module includes: a network connecting submodule, configured to establish a RRC connection to the base station of the network, send a request for becoming a base-station mobile terminal to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0016]In a second possible implementation manner, the mobile terminal further includes a base-station module, configured to make the mobile terminal become a base-station mobile terminal; and the broadcasting module includes: a network connecting submodule, configured to send an allocation request to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0017]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the network connecting submodule receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0018]In a fourth possible implementation manner, the broadcasting module includes: a network connecting submodule, configured to camp on the base station of the network, acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and a broadcasting submodule, configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0019]With reference to the fourth possible implementation manner, in a fifth possible implementation manner, the network connecting submodule is further configured to, after the receiving module receives the access request, access the base station and request to become a base-station mobile terminal, so as to assist the another mobile terminal in accessing the network. [0020]According to a third aspect, embodiments of the present invention provide a computer storage medium, where the computer storage medium may store a program, and the program is used to perform the steps according to the first aspect of the present invention or any one of the first to the sixth possible implementation manners of the first aspect. [0021]According to a fourth aspect, embodiments of the present invention provide a mobile terminal, including an input apparatus, an output apparatus, a memory, and a processor, where the processor performs the following steps: reading a help request used for accessing a network by another mobile terminal; sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network. [0022]In a first possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: establishing a RRC connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0023]In a second possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0024]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes: receiving the access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in completing access to the network. [0025]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step, which is performed by the processor, of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes: receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0026]In a fifth possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0027]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes: receiving the access request of the another mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the another mobile terminal in completing access to the network. [0028]According to the network accessing method for a mobile terminal, and the mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that another mobile terminal connects to the mobile terminal on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. BRIEF DESCRIPTION OF THE DRAWINGS [0029]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0030]FIG. 1 is a schematic diagram of an application environment according to an embodiment of the present invention; [0031]FIG. 2 to FIG. 4 are schematic flowcharts of a network accessing method for a mobile terminal according to embodiments of the present invention; and [0032]FIG. 5 to FIG. 8 are schematic diagrams of a mobile terminal according to embodiments of the present invention. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0033]The following describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0034]Referring to FIG. 1, FIG. 1 is a schematic diagram of an application environment of a network accessing method for a mobile terminal according to an embodiment of the present invention. In an implementation manner of the present invention, the network accessing method for a mobile terminal is used in a mobile communications system, for example, a Long Term Evolution (LTE for short) network, and a network under the 3rd Generation Partnership Project (3GPP for short). In some implementation manners of the present invention, the network accessing method for a mobile terminal may also be used in a wireless system. A network shown in FIG. 1 is a mobile communications system network, including a base station 30, where the base station 30 includes a macro base station (only one macro base station is used as an example in FIG. 1) and a micro base station (only one micro base station is used as an example in FIG. 1). A mobile terminal 10 is in coverage of the base station 30 and can access a network; and a mobile terminal 20 is not in the coverage of the base station 30, and cannot access the network, and therefore, the mobile terminal 10 is needed to assist the mobile terminal 20 in accessing the network. The mobile terminal 20 that is not covered or weakly covered is defined as an access mobile terminal, and the mobile terminal 10 that can connect to the base station 30 to access the network and can help the access mobile terminal 20 access the network is defined as a base-station mobile terminal. [0035]It should be noted that, in specific implementation, a function of a beacon channel is to make a terminal be discovered by another terminal. Therefore, in specific implementation, a resource allocated by the base station in the present invention is not merely limited to a beacon channel, and code that can be used to discover a terminal can be allocated by the base station in the present invention. That is, in this embodiment of the present invention, a beacon channel is merely used to indicate code used to discover a terminal, but is not used to limit use of other code having a terminal discovering function in this embodiment of the present invention. [0036]It may be understood that, because a base-station mobile terminal and an access mobile terminal move, the base-station mobile terminal may also become an access mobile terminal, and the access mobile terminal may also become a base-station mobile terminal. [0037]With reference to FIG. 1 and referring to FIG. 2, a network accessing method for a mobile terminal according to a first embodiment of the present invention includes the following steps. [0038]S201. Read a help request used for accessing a network by the mobile terminal 20. [0039]In this embodiment, the mobile terminal 20 is an access mobile terminal 20 that cannot access a network, and therefore, sends, on an agreed resource, the help request used for accessing a network, where the agreed resource may be, for example, a first timeslot of a frequency. By means of scanning, the mobile terminal 10 reads, on the agreed resource, the help request used for accessing a network by the mobile terminal 20. [0040]S202. Send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. [0041]In some implementation manners of the present invention, the mobile terminal 10 sends the beacon channel on the beacon channel resource allocated by the base station of the network. For example, there are resources of eight subframes from 0 to 7, and a second subframe is idle. In this case, the base station may allocate the second subframe to the mobile terminal 10, and the mobile terminal 10 may send a beacon channel in the second subframe and send a broadcast signal on a broadcast channel resource corresponding to the second subframe, for example, a third subframe, where the broadcast signal includes an access resource, for example, a fifth subframe. [0042]S203. Receive an access request of the mobile terminal 20 on the access resource, and assist the mobile terminal 20 in accessing the network. [0043]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0044]With reference to FIG. 1 and referring to FIG. 3, a network accessing method for a mobile terminal according to a second embodiment of the present invention includes: [0045]S301. The access mobile terminal 20 sends a request for requesting the mobile terminal 10 to help access a network. [0046]S302. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0047]S303. The mobile terminal 10 establishes a radio resource control (RRC) protocol connection to the base station 30 of the network, and sends a request for becoming a base-station mobile terminal to the base station 30. [0048]In this embodiment of the present invention, if the mobile terminal 10 intends to become a base-station mobile terminal after reading the help request of the access mobile terminal 20, the mobile terminal 10 sends the request for becoming a base-station mobile terminal to the base station 30. [0049]In some embodiments of the present invention, the mobile terminal 10 may also have become a base-station mobile terminal; in this case, the mobile terminal 10 sends only an allocation request to the base station 30. [0050]S304. The base station 30 allocates a beacon channel resource, a broadcast channel resource, and an access resource to the mobile terminal 10. [0051]In this embodiment of the present invention, the base station 30 allocates the beacon channel resource, the broadcast channel resource, and the access resource to the mobile terminal 10 by using radio resource control protocol signaling. [0052]In some implementation manners of the present invention, the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station 30 include a timeslot resource, a frequency resource, a code channel resource, and the like. [0053]In this case, the mobile terminal 10 becomes a base-station mobile terminal. [0054]S305. The mobile terminal 10 sends a beacon channel on the beacon channel resource allocated by the base station 30, and sends a broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0055]Step S303 to S305 are specific implementation steps of step S202 in FIG. 2. [0056]S306. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0057]S307. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0058]After receiving the access request of the access mobile terminal 20, the base-station mobile terminal 10 may help the access mobile terminal 20 complete access to the network, that is, the base station 30. [0059]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station 30, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0060]With reference to FIG. 1 and referring to FIG. 4, a network accessing method for a mobile terminal according to a third embodiment of the present invention includes the following steps. [0061]S401. The access mobile terminal 20 sends a request for requesting the base-station mobile terminal 10 to help access a network. [0062]S402. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0063]S403. The mobile terminal 10 camps on the base station 30, and acquires a beacon channel resource set and an access resource set by means of broadcast of the base station 30. [0064]S404. The mobile terminal 10 sends a beacon channel on an idle beacon channel resource in the beacon channel resource set, and sends a broadcast signal on a broadcast channel resource, where the broadcast signal includes an access resource. [0065]The mobile terminal 10 checks whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, and if there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the mobile terminal 10 sends the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sends the broadcast signal on a corresponding broadcast channel resource, where the broadcast signal includes the access resource. [0066]Step S403 to step S404 are specific implementation manners of step S202 in FIG. 2. [0067]S405. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0068]S406. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0069]S407. The mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, so as to assist the access mobile terminal in completing access to the network. [0070]According to the network accessing method for a mobile terminal, it is checked whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the beacon channel is sent on the idle beacon channel resource in the beacon channel resource set, and the broadcast signal is sent on a broadcast channel resource corresponding to the idle beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses a network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. In addition, only after receiving the access request of the access mobile terminal 20, the mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, thereby avoiding a waste of a resource. [0071]To better implement the foregoing solutions in the embodiments of the present invention, a related apparatus configured to cooperate to implement the foregoing solutions is provided in the following. [0072]Referring to FIG. 5, a mobile terminal 50 according to an embodiment of the present invention includes a reading module 500, a broadcasting module 510, and a receiving module 520. The reading module 500 is configured to read a help request used for accessing a network by another mobile terminal. The another mobile terminal is not covered by a network or weakly covered by a network, and therefore the another mobile terminal requests the mobile terminal 50 to help access the network. [0073]The broadcasting module 510 is configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The receiving module 520 is configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0074]Referring to FIG. 6, the broadcasting module 510 includes a network connecting submodule 511 and a broadcasting submodule 512. [0075]In some implementation manners of the present invention, the network connecting submodule 511 is configured to send a request for becoming a base-station mobile terminal to the network and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network. The broadcasting submodule 512 is configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0076]In some implementation manners of the present invention, the network connecting submodule 511 receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0077]In some implementation manners of the present invention, the network connecting submodule 511 is configured to camp on the base station of the network, and acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes the idle beacon channel resource, and the access resource set includes the access resource. The broadcasting submodule 512 is configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes the access resource. [0078]In some implementation manners of the present invention, the network connecting submodule 511 is further configured to, after the receiving module receives the access request, access the base st(String), 相关申请的交叉引用 [0001] 该申请是美国专利申请序列号的延续。 第 14/801,612 号,2015 年 7 月 16 日提交,现为美国专利。 美国第 9,814,022 号是 2013 年 1 月 16 日提交的国际申请第 PCT/CN2013/070522 号的继续申请。所有上述申请均通过引用整体并入本文。 技术领域 [0002] 本发明涉及通信技术领域,具体涉及一种移动终端的网络接入方法及移动终端。 背景 [0003] 在目前的蜂窝系统中,基站包括宏基站和微基站。 由于不同移动终端到基站的距离不同,对不同移动终端的干扰不同,导致不同移动终端的信道质量不同。 另外,在某些情况下,一些移动终端可能不在基站的覆盖范围内,例如移动终端落入覆盖盲区,或者由于地震等特殊原因导致基站损坏等。 这种未被覆盖的移动终端需要另外的移动终端帮助接入网络。 将未覆盖或弱覆盖的移动终端定义为接入移动终端,能够连接基站接入网络并帮助接入移动终端接入网络的移动终端定义为基站 移动终端。 [0004] 由于接入移动终端需要基站移动终端帮助接入网络,因此接入移动终端需要发现基站移动终端,同时也需要与基站移动终端建立连接,这种方式 ,可以实现接入移动终端接入网络的最终目的。 目前,现有的移动终端发现方式主要是移动终端自主发现对方的方式。 每个移动终端在特定资源上发送信标信道,以便通过检查彼此的信标信道来相互发现。 [0005] 由于信标信道资源有限,移动终端在发送信标信道之前,需要检查是否有信标信道资源,如果有信标信道资源,则移动终端发送信标信道。 这样,移动终端自主使用信标信道的分布式方式的缺点是移动终端可以使用信标信道但不与其他移动终端建立连接,从而浪费信标信道。 概括 [0006] 本发明实施例提供一种移动终端的网络接入方法及移动终端,能够更有效地利用信标信道资源。 [0007] 第一方面,本发明实施例提供了一种移动终端的网络接入方法。 该方法包括读取移动终端用于接入网络的帮助请求。 该方法还包括在由网络的基站分配的信标信道资源上发送信标信道,以及在对应于该信标信道资源的广播信道资源上发送广播信号,其中该广播信号包括接入资源。 该方法还包括接收移动终端对接入资源的接入请求,协助移动终端接入网络。 [0008]在第一种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源还包括:与网络基站建立无线资源控制(Radio Resource Control,无线资源控制)连接,向网络发送成为基站移动终端的请求。 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0009] 在第二种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源还包括:成为基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0010] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,接收所述移动终端对所述接入资源的接入请求,并协助所述移动终端接入网络的步骤还包括:接收所述接入 移动终端对接入资源的请求,协助移动终端完成对网络的接入。 [0011] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述接收网络基站分配的信标信道资源、广播信道资源和接入资源的步骤还包括: 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0012] 在第五种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 一种接入资源,进一步包括:驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲的信标信道资源,以及 访问资源集合包括访问资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0013] 结合第五种可能的实现方式,在第六种可能的实现方式中,接收所述移动终端对所述接入资源的接入请求,并协助所述移动终端接入网络的步骤还包括:接收所述移动终端的接入请求。 接入资源上的移动终端; 接入基站并请求成为基站移动终端,以辅助移动终端完成入网。 [0014]第二方面,本发明实施例提供了一种移动终端。 该移动终端包括读取模块,用于读取其他移动终端接入网络的帮助请求。 移动终端还包括广播模块,用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,其中,广播信号 包括访问资源。 移动终端还包括接收模块,用于接收其他移动终端对访问资源的访问请求,协助其他移动终端访问网络。 [0015] 在第一种可能的实现方式中,所述广播模块包括: 网络连接子模块,用于与网络基站建立RRC连接,向网络发送成为基站移动终端的请求,并接收beacon 网络基站分配的信道资源、广播信道资源和接入资源; 广播子模块,用于在网络基站分配的信标信道资源上发送信标信道,并在广播信道资源上发送广播信号,广播信号包括接入资源。 [0016] 在第二种可能的实现方式中,所述移动终端还包括基站模块,用于使所述移动终端成为基站移动终端; 广播模块包括:网络连接子模块,用于向网络发送分配请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块,用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号中包括接入资源。 [0017] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,网络连接子模块接收网络基站通过使用 无线电资源控制协议信令。 [0018] 在第四种可能的实现方式中,广播模块包括:网络连接子模块,用于驻留在网络的基站上,通过基站的广播获取信标信道资源集和接入资源集,其中, 信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源; 广播子模块,用于在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号包括接入资源 . [0019] 结合第四种可能的实现方式,在第五种可能的实现方式中,网络连接子模块还用于接收模块接收到接入请求后,接入基站,请求成为基站移动终端,因此 以协助其他移动终端接入网络。 [0020] 第三方面,本发明实施例提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行本发明第一方面或以下任一项所述的步骤 第一方面的第一种至第六种可能的实现方式。 [0021]第四方面,本发明实施例提供一种移动终端,包括输入装置、输出装置、存储器和处理器,所述处理器执行以下步骤:读取用于访问网络的帮助请求。 另一个移动终端; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0022] 在第一种可能的实现方式中,所述处理器执行在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号的步骤 信道资源,其中广播信号包括接入资源还包括:与网络基站建立RRC连接,向网络发送成为基站移动终端的请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0023] 在第二种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括:成为基站的移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0024] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述处理器接收所述另一移动终端对所述接入资源的接入请求,并协助所述另一移动终端执行的步骤 接入网络还包括:接收另一移动终端对接入资源的接入请求,协助另一移动终端完成接入网络。 [0025] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述处理器接收所述处理器分配的信标信道资源、广播信道资源和接入资源的步骤。 网络基站还包括:接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0026] 在第五种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括:驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,其中,所述信标信道资源集 包括空闲信标信道资源,接入资源集合包括接入资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0027] 结合第五种可能的实现方式,在第六种可能的实现方式中,所述处理器接收所述其他移动终端对所述访问资源的访问请求,协助所述其他移动终端访问所述访问资源。 网络还包括:接收另一移动终端对接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0028] 一种移动终端入网方法及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在信标对应的广播信道资源上发送 channel resource,指示接入资源,以便其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入资源。 附图的简要说明 [0029] 为了更加清楚地描述本发明实施例中的技术方案,下面对实施例描述中所需要的附图进行简单介绍。 显然,以下描述中的附图仅仅是本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0030] 图1为本发明实施例的应用环境示意图; [0031] 图2至图4是根据本发明实施例的移动终端的网络接入方法的流程示意图; 和 [0032] 图5至图8是根据本发明实施例的移动终端的示意图。 说明性实施例的详细说明 [0033] 下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行说明。 显然,所描述的实施例仅仅是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0034] 请参阅图1,图1为本发明实施例提供的移动终端的网络接入方法的应用环境示意图。 在本发明的一个实施方式中,所述移动终端的入网方法用于移动通信系统,例如长期演进(Long Term Evolution,简称LTE)网络、第三代合作伙伴计划(3GPP)下的网络。 简称)。 在本发明的一些实施方式中,该移动终端的网络接入方法还可以用于无线系统中。 图1所示网络为移动通信系统网络,包括基站 30 ,其中基站 30 包括宏基站(图1中仅以一个宏基站为例)和微基站(图1中仅以一个微基站为例)。 移动终端 10 在基站覆盖范围内 30 并且可以访问网络; 和移动终端 20 不在基站覆盖范围内 30 , 无法上网, 因此, 移动终端 10 需要移动端辅助 20 在访问网络时。 移动端 20 未覆盖或弱覆盖定义为接入移动终端,移动终端 10 可以连接到基站 30 接入网络,可以帮助接入移动终端 20 接入网络的移动终端被定义为基站。 [0035]需要说明的是,在具体实现中,信标信道的作用是使一个终端被另一个终端发现。 因此,在具体实施中,本发明基站分配的资源并不仅限于信标信道,本发明基站可以分配可用于发现终端的代码。 即本发明实施例中,信标信道仅用于指示用于发现终端的代码,并不用于限制本发明实施例中使用其他具有终端发现功能的代码。 [0036] 可以理解的是,由于基站移动终端和接入移动终端移动,因此基站移动终端也可能成为接入移动终端,接入移动终端也可能成为基站移动终端。 [0037] 参考图1并参考图2,根据本发明第一实施例的移动终端的网络接入方法包括以下步骤。 [0038] 小号 201 . 读取移动终端接入网络的帮助请求 20 . [0039] 本实施例中,移动终端 20 是接入移动终端 20 无法接入网络,因此在约定的资源上发送用于接入网络的帮助请求,该约定的资源例如可以是频率的第一时隙。 手机端扫一扫 10 在约定的资源上读取移动终端接入网络的帮助请求 20 . [0040] 小号 202 . 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0041] 在本发明的一些实施方式中,移动终端 10 在网络基站分配的信标信道资源上发送信标信道。 例如,0到7有8个子帧的资源,第二个子帧空闲。 在这种情况下,基站可以将第二子帧分配给移动终端 10 , 和移动端 10 可以在第二子帧发送信标信道,在第二子帧对应的广播信道资源,例如第三子帧上发送广播信号,该广播信号包括接入资源,例如第五子帧。 [0042] 小号 203 . 接收移动终端的访问请求 20 在接入资源上,协助移动终端 20 在访问网络时。 [0043] 一种移动终端的入网方法,所述信标信道在网络基站分配的信标信道资源上发送,广播信号在所述信标信道资源对应的广播信道资源上发送,以指示 访问资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理地利用了信标信道和接入资源。 [0044] 结合图1并参考图3,本发明实施例二提供的一种移动终端的网络接入方法包括: [0045] 小号 301 . 接入移动终端 20 发送请求移动端的请求 10 帮助访问网络。 [0046] 小号 302 . 移动端 10 读取接入移动端的帮助请求 20 . [0047] 小号 303 . 移动端 10 建立到基站的无线资源控制 (RRC) 协议连接 30 向基站发送成为基站移动终端的请求 30 . [0048] 本发明实施例中,若移动终端 10读取接入移动终端的帮助请求后,打算成为基站移动终端 20 , 移动端 10 向基站发送成为基站移动终端的请求 30 . [0049] 在本发明的一些实施例中,移动终端 10 也可能成为基站移动终端; 在这种情况下,移动端 10 仅向基站发送分配请求 30 . [0050] 小号 304 . 基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源 10 . [0051] 本发明实施例中,基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源 10 通过使用无线电资源控制协议信令。 [0052] 在本发明的一些实施方式中,基站分配的信标信道资源、广播信道资源和接入资源 30 包括时隙资源、频率资源、码道资源等。 [0053] 在这种情况下,移动端 10 成为基站移动终端。 [0054] 小号 305 . 移动端 10 在基站分配的信标信道资源上发送信标信道 30 ,在广播信道资源上发送广播信号,广播信号中包含接入资源。 [0055] 脚步 303 到小号 305 是步骤S的具体实现步骤 202 在图 2 中。 [0056] 小号 306 . 接入移动终端 20 搜索信标信道,与移动终端同步 10 ,从而读取广播信号,并从广播信号中读取接入资源。 [0057] 小号 307 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0058] 收到接入移动终端的接入请求后 20 , 基站移动终端 10 可以帮助接入移动终端 20 完全接入网络,即基站 30 . [0059] 一种移动终端入网方法,所述信标信道在基站分配的信标信道资源上发送 30 ,在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0060] 参考图1并参考图4,根据本发明实施例三的移动终端的网络接入方法包括以下步骤。 [0061] 小号 401 . 接入移动终端 20 发送请求基站移动终端的请求 10 帮助访问网络。 [0062] 小号 402 . 移动端 10 读取接入移动端的帮助请求 20 . [0063] 小号 403 . 移动端 10 基站上的营地 30 , 通过基站的广播获取信标信道资源集和接入资源集 30 . [0064] 小号 404 . 移动端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,在广播信道资源上发送广播信号,该广播信号包括接入资源。 [0065] 移动端 10 检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30, 如果基站广播的信标信道资源集合中有空闲的信标信道资源 30 , 移动端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在相应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0066] 脚步 403 到步骤 S 404 是步骤S的具体实现方式 202 在图 2 中。 [0067] 小号 405 . 接入移动终端 20 搜索信标信道,与移动终端同步 10 ,从而读取广播信号,并从广播信号中读取接入资源。 [0068] 小号 406 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0069] 小号 407 . 移动端 10 接入基站 30 请求成为基站移动终端,以协助接入移动终端完成入网。 [0070] 一种移动终端入网方法,检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30 ,信标信道在信标信道资源集合中的空闲信标信道资源上发送,广播信号在空闲信标信道资源对应的广播信道资源上发送,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 另外,只有在接收到接入移动终端的接入请求后 20 , 移动端 10 接入基站 30 请求成为基站移动终端,避免资源浪费。 [0071] 为了更好的实施本发明实施例的上述方案,下面提供一种用于配合实施上述方案的相关装置。 [0072] 参见图5,移动终端 50 根据本发明的实施例包括读取模块 500 , 广播模块 510 , 和一个接收模块 520 . 阅读模块 500 用于读取其他移动终端接入网络的帮助请求。 另一移动终端未被网络覆盖或弱网络覆盖,因此另一移动终端请求该移动终端 50 以帮助访问网络。 [0073] 广播模块 510 用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 接收模块 520 用于接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0074] 参见图6,广播模块 510 包括一个网络连接子模块 511 和一个广播子模块 512 . [0075] 在本发明的一些实施方式中,网络连接子模块 511 用于向网络发送成为基站移动终端的请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0076] 在本发明的一些实施方式中,网络连接子模块511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0077] 在本发明的一些实施方式中,网络连接子模块 511 用于驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲信标信道资源和接入资源 set 包括访问资源。 广播子模块 512 用于在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0078] 在本发明的一些实施方式中,网络连接子模块 511 还用于接收模块接收到接入请求后,接入基站并请求成为基站移动终端,以辅助其他移动终端接入网络。 [0079] 可以理解为移动端 50 本实施例中例如可以为电脑、手机或平板电脑。 [0080] 可以理解为,移动终端的所有功能模块的功能 50 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0081] 上述移动终端 50 在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 50 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0082] 参考图7,移动终端之间的区别 70 根据本发明实施例的移动终端 50 图5所示为基站模块 700 除了阅读模块外,还包括 500 , 广播模块 510 , 和一个接收模块 520 , 其中阅读模块 500 ,广播模块 510 , 接收模块 520 与图5所示的相应模块基本相同,在此不再赘述。 基站模块 700 配置为使移动端 70 成为基站移动终端。 [0083] 广播模块 510 还包括网络连接子模块 511 和广播子模块 512 如图6所示,其中网络连接子模块 511 用于向网络端发送分配请求,接收网络端基站分配的信标信道资源、广播信道资源和接入资源; 和广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0084] 在本发明的一些实施方式中,网络连接子模块 511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0085] 可以理解为移动端 70 本实施例中例如可以为电脑、手机或平板电脑。 [0086]可以理解为,移动终端的所有功能模块的功能 70 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0087] 上述移动终端 70 在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 70 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0088] 本发明实施例还提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行上述方法中描述的移动终端上网方法的部分或全部步骤。 实施例。 [0089] 参见图8,本发明实施例还提供了一种移动终端 80 ,包括一个处理器 810 , 一段记忆 800 , 输入设备 820 , 和一个输出设备 830 (可能有一个或多个处理器 810 在移动端 80 ,图8中以一个处理器为例)。 在本发明的一些实施例中,输入装置 820 , 输出设备 830 , 记忆 800 , 和处理器 810 可以通过使用总线或以其他方式相互连接。 图8中以它们通过总线连接为例。 [0090] 处理器 810 执行以下步骤: 读取另一移动终端用于接入网络的帮助请求; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0091] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:发送 请求成为网络的基站移动终端; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0092] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:成为一个 基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0093] 在本发明的一些实施方式中,所述步骤由处理器执行 810接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络还包括:接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络。 完成对网络的访问。 [0094] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收网络基站分配的信标信道资源、广播信道资源和接入资源还包括:接收网络基站分配的信标信道资源、广播信道资源和接入资源。 网络的基站通过使用无线资源控制协议信令。 [0095] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,还包括:驻留在 网络的基站,通过基站广播获取信标信道资源集和接入资源集,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源 ; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0096] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收所述另一移动终端对所述接入资源的接入请求,协助所述另一移动终端接入网络还包括:接收所述另一移动终端对所述接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0097] 可以理解为,移动终端的所有功能模块的功能 80 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0098] 需要说明的是,为便于描述,上述方法实施例均以一系列动作进行描述。 然而,本领域的技术人员应该理解,本发明不限于所描述的动作顺序,因为根据本发明,一些步骤可以以不同的顺序或同时执行。 其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本发明所必须的。 [0099] 在上述实施例中,对各个实施例的描述都各有侧重。 一个实施例中没有详述的部分,可以参见其他实施例的相关描述。 [0100] 综上所述,根据移动终端的入网方法,以及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在相应的广播信道资源上发送 到信标信道资源,指示接入资源,使得其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入 资源。 [0101]本领域普通技术人员可以理解,上述实施例中方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 存储介质可以包括:只读存储器、随机存取存储器、磁盘或光盘。 [0102] 以上对本发明实施例提供的移动终端的网络接入方法及移动终端进行了详细描述。 本说明书中采用具体的例子来说明本发明的原理和实施方式。 上述实施例只是为了帮助理解本发明的方法和核心思想。 此外,对于实施方式和适用范围,本领域的普通技术人员可以根据本发明的思想进行修改。 总之,说明书不应理解为对本发明的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), CN104303526A(String), 1047349(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), CN104303526B(String), 1047350(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), EP2947901A1(String), 1047351(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), EP2947901A4(String), 1047352(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), EP2947901B1(String), 1047353(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), EP3624471A1(String), 1047354(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), EP3624471B1(String), 1047355(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.945 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), US10200973B2(String), 1047356(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), US20150327216A1(String), 1047357(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), US20180054802A1(String), 1047358(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), US9814022B2(String), 1047359(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270682(Integer), WO2014110726A1(String), 1047360(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9814022B2(String), US9814022B2(String), 1509984000(Integer), 270682(Integer), 185003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975553(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185004(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75946(Integer), 1(Integer), 185004(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185004(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185004(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:53.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10310566B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Foldable mechanism of mobile terminal and mobile terminal(String), 移动终端折叠机构及移动终端(String), US10310566B2(String), The present disclosure provides a foldable mechanism of a mobile terminal and the mobile terminal. The foldable mechanism includes a soft support structure and a hard support structure embedded in the soft support structure. The foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting a first housing and a second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward. Therefore, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved.(String), 本发明提供一种移动终端的折叠机构及移动终端。 折叠机构包括软支撑结构和嵌入软支撑结构的硬支撑结构。 由软支撑结构和嵌入软支撑结构中的硬支撑结构形成的可折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软支撑结构和硬支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 当移动终端折叠时,软支撑结构远离硬支撑结构的一侧向内收缩。 因此,避免了移动终端具有突兀的外观结构,提高了移动终端的外观效果。(String), US16/119102(String), 1535644800(Integer), US10310566B2(String), 1559577600(Integer), 1559577600(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 34(Integer), CN102710823A | CN104900149A | CN105096756A | CN105549690A | CN204069046U | CN205446377U | KR101467857B1 | US20020067339A1 | US20070117600A1 | US20100164837A1 | US20120147542A1 | US20120307423A1 | US20120307472A1 | US20130216740A1 | US20140196254A1 | US20140217875A1 | US20150055287A1 | US20150077917A1 | US20150176317A1 | US20150257290A1 | US20150330614A1 | US20160062412A1 | US20160139634A1 | US20160187935A1 | US20160224072A1 | US20180077810A1 | US6421235B2 | US6577496B1 | US9506279B2 | US9811119B2 | US9818961B2 | US9898051B2 | US9927841B2 | WO2012167204A2(String), 18(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185005(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f7dc4590436c41f188f8e9747ac43e47.png(String), 185005(Integer), f7dc4590436c41f188f8e9747ac43e47.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.037 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Foldable mechanism of mobile terminal and mobile terminal(String), 移动终端折叠机构及移动终端(String), US10310566B2(String), The present disclosure provides a foldable mechanism of a mobile terminal and the mobile terminal. The foldable mechanism includes a soft support structure and a hard support structure embedded in the soft support structure. The foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting a first housing and a second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward. Therefore, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved.(String), 本发明提供一种移动终端的折叠机构及移动终端。 折叠机构包括软支撑结构和嵌入软支撑结构的硬支撑结构。 由软支撑结构和嵌入软支撑结构中的硬支撑结构形成的可折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软支撑结构和硬支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 当移动终端折叠时,软支撑结构远离硬支撑结构的一侧向内收缩。 因此,避免了移动终端具有突兀的外观结构,提高了移动终端的外观效果。(String), US16/119102(String), 1535644800(Integer), US10310566B2(String), 1559577600(Integer), 1559577600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 34(Integer), CN102710823A | CN104900149A | CN105096756A | CN105549690A | CN204069046U | CN205446377U | KR101467857B1 | US20020067339A1 | US20070117600A1 | US20100164837A1 | US20120147542A1 | US20120307423A1 | US20120307472A1 | US20130216740A1 | US20140196254A1 | US20140217875A1 | US20150055287A1 | US20150077917A1 | US20150176317A1 | US20150257290A1 | US20150330614A1 | US20160062412A1 | US20160139634A1 | US20160187935A1 | US20160224072A1 | US20180077810A1 | US6421235B2 | US6577496B1 | US9506279B2 | US9811119B2 | US9818961B2 | US9898051B2 | US9927841B2 | WO2012167204A2(String), \20230420\f7dc4590436c41f188f8e9747ac43e47.png(String), 18(Integer), 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.051 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 1. A foldable mechanism of a mobile terminal, comprising:a soft support structure to connect a first housing and a second housing of the mobile terminal, the soft support structure comprising a plurality of V-shaped supports arranged in a single row, open ends of adjacent V-shaped supports are connected, and an opening of each V-shaped support faces a flexible display screen of the mobile terminal; anda hard support structure included in each V-shaped support and configured to support the flexible display screen, wherein each hard support structure blocks two ends of a V-shaped support corresponding to the hard support structure; and further comprising a blocking layer included between bending tip portions of any two adjacent V-shaped supports;when the foldable mechanism of the mobile terminal is bent, bending tip portions of the plurality of V-shaped supports converge, and each blocking layer is compressed into a gap between two V-shaped supports connected by the blocking layer; andwhen the foldable mechanism of the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports move away from each other, and each blocking layer is unfolded to block the gap between the two V-shaped supports connected by the blocking layer.(String), 1.根据权利要求10所述的移动终端,其中多个阻挡层为一体结构的折弯板,折弯板上包括多个折痕,多个V形支架的折弯尖端部分等间距固定连接于折弯板上的折痕,并且相邻的V形支撑之间存在奇数个折痕。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 2. The foldable mechanism of the mobile terminal according to claim 1, wherein a plurality of blocking layers are a bending plate of an integrated structure, a plurality of creases are included on the bending plate, the bending tip portions of the plurality of V-shaped supports are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports.(String), 12.根据权利要求10所述的移动终端,其中多个阻挡层中的至少一个阻挡层为弯折件,弯折件上存在奇数条折痕,弯折件的两端分别与两侧的V型支架的弯折尖端部连接。一对一的基础上的阻挡层。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 3. The foldable mechanism of the mobile terminal according to claim 1, wherein at least one blocking layer in a plurality of blocking layers is a bending piece, an odd number of creases exist on the bending piece, and two ends of the bending piece are respectively connected to bending tip portions of V-shaped supports on two sides of the blocking layer on a one-to-one basis.(String), 13.根据权利要求12所述的移动终端,其中每个弯曲件上都有一个折痕。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 4. The foldable mechanism of the mobile terminal according to claim 3, wherein one crease exists on each bending piece.(String), 14.根据权利要求10所述的移动终端,其中多个阻挡层中的至少一个阻挡层包括夹在相邻V形支撑件之间的弹性材料层。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 5. The foldable mechanism of the mobile terminal according to claim 1, wherein at least one blocking layer in the plurality of blocking layers comprises an elastic material layer included between adjacent V-shaped supports.(String), 15.根据权利要求14所述的移动终端,其中各弹性材料层和与弹性材料层相邻的V型支架为一体结构。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 6. The foldable mechanism of the mobile terminal according to claim 5, wherein each elastic material layer and a V-shaped support adjacent to the elastic material layer are an integrated structure.(String), 16.根据权利要求10所述的移动终端,其中每个硬质支撑结构包括挡住硬质支撑结构对应的V型支架的开口的第一支撑层,第一支撑层的两端具有挡住V型支架一端的折叠机构。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 7. The foldable mechanism of the mobile terminal according to claim 1, wherein each hard support structure comprises a first support layer blocking an opening of a V-shaped support corresponding to the hard support structure, and a foldable mechanism blocking one end of the V-shaped support exists at either end of the first support layer.(String), 17.根据权利要求16所述的移动终端,还包括外层包括在可折叠机构的外侧壁上。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 8. The foldable mechanism of the mobile terminal according to claim 7, further comprising an exterior layer included on an external sidewall of the foldable mechanism.(String), 18.根据权利要求16所述的移动终端,其中硬质支撑结构还包括包裹第一支撑层的第二支撑层,第二支撑层的强度高于第一支撑层的强度。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 9. The foldable mechanism of the mobile terminal according to claim 7, wherein the hard support structure further comprises a second support layer wrapping the first support layer, and strength of the second support layer is higher than strength of the first support layer.(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 10. A mobile terminal, comprising,a housing; anda flexible display screen included in the housing, the housing comprising:a first housing,a second housing, anda foldable mechanism to fold the first housing and the second housing, the foldable mechanism comprising:a soft support structure to connect the first housing and the second housing of the mobile terminal, the soft support structure comprising a plurality of V-shaped supports arranged in a single row, open ends of adjacent V-shaped supports are connected, and an opening of each V-shaped support faces a flexible display screen of the mobile terminal; anda hard support structure included in each V-shaped support and configured to support the flexible display screen, wherein each hard support structure blocks two ends of a V-shaped support corresponding to the hard support structure; and further comprising a blocking layer included between bending tip portions of any two adjacent V-shaped supports;when the foldable mechanism of the mobile terminal is bent, bending tip portions of the plurality of V-shaped supports converge, and each blocking layer is compressed into a gap between two V-shaped supports connected by the blocking layer; andwhen the foldable mechanism of the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports move away from each other, and each blocking layer is unfolded to block the gap between the two V-shaped supports connected by the blocking layer.(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 11. The mobile terminal according to claim 10, wherein a plurality of blocking layers are a bending plate of an integrated structure, a plurality of creases are included on the bending plate, the bending tip portions of the plurality of V-shaped supports are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 12. The mobile terminal according to claim 10, wherein at least one blocking layer in a plurality of blocking layers is a bending piece, an odd number of creases exist on the bending piece, and two ends of the bending piece are respectively connected to bending tip portions of V-shaped supports on two sides of the blocking layer on a one-to-one basis.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 13. The mobile terminal according to claim 12, wherein one crease exists on each bending piece.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 14. The mobile terminal according to claim 10, wherein at least one blocking layer in the plurality of blocking layers comprises an elastic material layer included between adjacent V-shaped supports.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 15. The mobile terminal according to claim 14, wherein each elastic material layer and a V-shaped support adjacent to the elastic material layer are an integrated structure.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 16. The mobile terminal according to claim 10, wherein each hard support structure comprises a first support layer blocking an opening of a V-shaped support corresponding to the hard support structure, and a foldable mechanism blocking one end of the V-shaped support exists at either end of the first support layer.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 17. The mobile terminal according to claim 16, further comprising an exterior layer included on an external sidewall of the foldable mechanism.(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185005(Integer), 18. The mobile terminal according to claim 16, wherein the hard support structure further comprises a second support layer wrapping the first support layer, and strength of the second support layer is higher than strength of the first support layer.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185005(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2017/102310, filed on Sep. 19, 2017, which claims priority to Chinese Patent Application No. 201610836223.0, filed on Sep. 20, 2016. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of mobile terminal technologies, and in particular, to a foldable mechanism of a mobile terminal and the mobile terminal. BACKGROUND [0003]As flexible foldable screen technologies are increasingly mature, foldable terminal products will also be a main trend in the future. A foldable terminal product (for example, an electronic device such as a foldable mobile phone, a foldable tablet, or a foldable computer) needs to have a relatively good ID exterior, so that the product can be accepted by consumers. Using a foldable mobile phone as an example, different from a conventional flip phone, a flexible foldable mobile phone has a screen that can be continuously folded. To ensure that the foldable screen is not pulled or squeezed, a middle hinge folding part of an entire exterior of the product is largely deformed, but a general structure cannot implement such large deformation. Therefore, all foldable mechanisms in the prior art are foldable mechanisms implemented by using a mechanical linkage mechanism, and complexity is relatively high. In addition, when a component of the mechanical linkage mechanism moves, an exterior effect of a mobile terminal is impaired unavoidably. SUMMARY [0004]Embodiments of the present invention provide a foldable mechanism of a mobile terminal and the mobile terminal to improve an effect of the mobile terminal when the mobile terminal is bent. [0005]Embodiments of the present invention provide a foldable mechanism of a mobile terminal. The foldable mechanism includes a soft support structure that connects a first housing and a second housing of the mobile terminal, where the soft support structure includes a plurality of V-shaped supports arranged in a single row, open ends of adjacent V-shaped supports are connected, and an opening of each V-shaped support faces a flexible display screen of the mobile terminal; the foldable mechanism further includes a hard support structure that is disposed in each V-shaped support and configured to support the flexible display screen, where each hard support structure blocks two ends of a V-shaped support corresponding to the hard support structure; and the foldable mechanism further includes a blocking layer disposed between bending tip portions of any two adjacent V-shaped supports; [0006]when the foldable mechanism of the mobile terminal is bent, bending tip portions of the plurality of V-shaped supports converge, and each blocking layer is compressed into a gap between two V-shaped supports connected by the blocking layer; and [0007]when the foldable mechanism of the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports move away from each other, and each blocking layer is unfolded to block the gap between the two V-shaped supports connected by the blocking layer. [0008]In the foregoing technical solution, the foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting the first housing and the second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward, and one side of the soft support structure located on the hard support structure is also extended and bent, so that the entire foldable mechanism forms a C-shaped structure to implement bending of the first housing and the second housing. In the foregoing bending process, the flexible screen is supported by the hard support structure, and the shape of the foldable mechanism is changed according to a change of the soft support structure. Therefore, continuity of connections between the foldable mechanism and the first housing and the second housing is improved, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved. [0009]In a specific implementation solution, a plurality of blocking layers are a bending plate of an integrated structure, a plurality of creases are disposed on the bending plate, the bending tip portions of the plurality of V-shaped supports are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports. That is, the blocking layers use the bending plate to block a gap formed by tip ends of the plurality of V-shaped supports. This improves the exterior effect of the entire mobile terminal. In addition, when being bent, the bending plate occupies less space. Therefore, the exterior effect after the entire structure is bent can be ensured. [0010]In another implementation solution, at least one blocking layer in a plurality of blocking layers is a bending piece, an odd number of creases exist on the bending piece, and two ends of the bending piece are respectively connected to bending tip portions of V-shaped supports on two sides of the blocking layer on a one-to-one basis. That is, the blocking layer may use a structure of a bending piece. There is no great structural difference between the bending piece and the foregoing bending plate. The only difference is that the bending piece in this solution is located between two V-shaped supports. In addition, in this solution, when all blocking layers use bending pieces as described above, after the bending pieces are connected, there is no great structural difference from the bending plate. However, the blocking layer in this solution not only uses the structure of the bending piece, but also may use another foldable mechanism. Therefore, the V-shaped support may be blocked by using different structures. In a specific solution, one crease exists on each bending piece. That is, when being bent, the bending piece needs to be bent only once to fit into the gap between the V-shaped supports. This improves convenience during deformation, reduces a thickness of the bending piece after the bending piece is folded, and improves an effect after the bending piece is bent. [0011]In addition, in a third implementation solution, at least one blocking layer in the plurality of blocking layers includes an elastic material layer disposed between adjacent V-shaped supports. That is, the gap between the V-shaped supports is filled with the elastic material layer. After the foldable mechanism is bent, the elastic material layer is compressed and deformed, so that the foldable mechanism can be bent. When being unfolded, the elastic material recovers to an initial state, and can effectively block the gap between the V-shaped supports. In a specific implementation, each blocking layer may use an elastic material layer. Alternatively, only some blocking layers use elastic material layers. [0012]In a fourth implementation solution, some blocking layers may use bending pieces, and other blocking layers may use elastic material layers, that is, the elastic material layers and the bending pieces are mixed to form the blocking layers, thereby achieving an effect of blocking the gap between the V-shaped supports in the soft support structure. In addition, when being bent, the blocking layers can implement good deformation, and do not affect bending of the foldable mechanism. [0013]In the foregoing solution, when an elastic material layer is used as a blocking layer, each elastic material layer and a V-shaped support adjacent to the elastic material layer are an integrated structure. That is, the elastic material layer and a soft support layer are disposed by using a same material. In this case, the soft support structure may be considered as a sheet-like elastic layer in which a plurality of V-shaped slots are provided and a hard support structure is embedded in each V-shaped slot. [0014]In specific disposition, hard support structure may use different structures. In a manner, each hard support structure includes a first support layer blocking an opening of a V-shaped support corresponding to the hard support frame, and a foldable mechanism blocking one end of the V-shaped support exists at either end of the first support layer. That is, the flexible display screen is supported by the first support layer, and openings at two ends of the V-shaped support are blocked by using foldable mechanisms. Therefore, the mobile terminal is prevented from having an exterior gap or hole. This improves the exterior effect of the mobile terminal. [0015]In a solution, the hard support structure further includes an exterior layer disposed on an external sidewall of the foldable mechanism. The exterior layer is disposed to block the gap when the first support layer is connected to the V-shaped support. This further improves the exterior effect of the mobile terminal. [0016]In addition, to enhance support strength of the hard support structure, connection strength between the hard support structure and the soft support structure is improved. In an improved solution, the hard support structure further includes a second support layer wrapping the first support layer, and strength of the second support layer is higher than strength of the first support layer. That is, the first support layer of the hard support structure is made of a material that has a relatively good adhesive effect with the soft support structure and relatively small hardness, but the second support layer may be made of a material that has relatively high support strength. This improves an effect of supporting the flexible display screen by the hard support structure. [0017]Embodiments of the present invention further provide a mobile terminal. The mobile terminal includes a housing and a flexible display screen disposed in the housing, where the housing includes a first housing, a second housing, and the foldable mechanism for implementing folding of the first housing and the second housing according to any one of the foregoing. [0018]In the foregoing technical solution, the foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting the first housing and the second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward, and one side of the soft support structure located on the hard support structure is also extended and bent, so that the entire foldable mechanism forms a C-shaped structure to implement bending of the first housing and the second housing. In the foregoing bending process, the flexible screen is supported by the hard support structure, and the shape of the foldable mechanism is changed according to a change of the soft support structure. Therefore, continuity of connections between the foldable mechanism and the first housing and the second housing is improved, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved. BRIEF DESCRIPTION OF DRAWINGS [0019]FIG. 1 is a schematic view of a mobile terminal in a folded state according to an embodiment of the present invention; [0020]FIG. 2 is a schematic exploded view of a mobile terminal in a folded state according to an embodiment of the present invention; [0021]FIG. 3 is a schematic view of a mobile terminal in an unfolded state according to an embodiment of the present invention; [0022]FIG. 4 is a schematic exploded view of a mobile terminal in an unfolded state according to an embodiment of the present invention; [0023]FIG. 5 is a schematic view of a foldable mechanism in a bent state according to an embodiment of the present invention; [0024]FIG. 6 is a schematic exploded view of a foldable mechanism in a bent state according to an embodiment of the present invention; [0025]FIG. 7 is a schematic view of a foldable mechanism in an unfolded state according to an embodiment of the present invention; [0026]FIG. 8 is a schematic status diagram of a foldable mechanism in a bending process according to an embodiment of the present invention; [0027]FIG. 9 is a schematic exploded view of another foldable mechanism according to an embodiment of the present invention; [0028]FIG. 10 is a schematic view of a third foldable mechanism according to an embodiment of the present invention; [0029]FIG. 11 is a sectional view of a hard support structure according to an embodiment of the present invention; and [0030]FIG. 12 is a schematic exploded view of a foldable mechanism when the hard support structure shown in FIG. 11 is used according to an embodiment of the present invention. REFERENCE SIGNS IN THE DRAWINGS [0031]10: flexible display screen; 20: first housing; 30: second housing[0032]40: foldable mechanism; 41: soft support structure; 411: V-shaped support[0033]42: hard support structure; 421: first support layer; 422: foldable mechanism[0034]423: exterior layer; 43: blocking layer; 431: bending piece; 4311: first bending piece[0035]4312: second bending piece; 432: elastic material layer DESCRIPTION OF EMBODIMENTS [0036]To make the objectives, technical solutions, and advantages of the present invention clearer, the following further describes the present invention in detail with reference to the accompanying drawings. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0037]As shown in FIG. 1 and FIG. 3, FIG. 1 and FIG. 3 are schematic views of a mobile terminal in different states according to an embodiment of the present invention. [0038]An embodiment of the present invention provides a foldable mechanism of a mobile terminal. The foldable mechanism is applied to the mobile terminal. The mobile terminal includes a housing and a flexible display screen 10 disposed in the housing. The housing includes a first housing 20, a second housing 30, and the foldable mechanism 40 for implementing folding of the first housing 20 and the second housing 30 according to any one of the foregoing. The first housing 20 and the second housing 30 are connected by the foldable mechanism 40 to form an entirety. The flexible display screen 10 is installed in the housing formed by the first housing 20 and the second housing 30. [0039]As shown in FIG. 5, FIG. 6, and FIG. 7, FIG. 5 and FIG. 7 are schematic views of the foldable mechanism 40 in different states, and FIG. 6 is a schematic exploded view of the foldable mechanism 40. The foldable mechanism 40 provided by this embodiment has a bending function. The foldable mechanism 40 may be used to implement bending and unfolding of the first housing 20 and the second housing 30, that is, implement folding and unfolding of the mobile terminal. Specifically, the foldable mechanism 40 includes a soft support structure 41 that connects the first housing 20 and the second housing 30. The soft support structure 41 includes a plurality of V-shaped supports 411 arranged in a single row, and open ends of adjacent V-shaped supports 411 are connected. Specifically, as shown in FIG. 5 and FIG. 6, top positions of sidewalls between two adjacent V-shaped supports 411 are connected, and the plurality of V-shaped supports 411 are connected in sequence, so that the plurality of V-shaped supports 411 are connected to form an entirety. In addition, in specific disposition, a length direction of each V-shaped support 411 is parallel to a direction of rotation of the first housing 20 relative to the second housing 30, that is, in the V-shaped supports 411 arranged in the single row, V-shaped supports 411 located at two ends are connected to the first housing 20 and the second housing 30 respectively. Therefore, when the first housing 20 and the second housing 30 rotate relatively, the V-shaped supports 411 can be deformed, and tip portions of the V-shaped supports 411 move in a direction of convergence. Therefore, the soft support frame forms a structure, with its interior (one side away from the flexible display screen 10) converging and its exterior (facing the flexible display screen 10) being extended. [0040]In addition, in disposition, an opening of each V-shaped support 411 faces the flexible display screen 10, and a hard support structure 42 configured to support the flexible display screen 10 is disposed in each V-shaped support 411. The hard support structure 42 is fixed in a groove part in the V-shaped support 411, and faces the flexible display screen 10. The hard support structure 42, the first housing 20, and the second housing 30 together form a support structure for the flexible display screen 10. In the foregoing description, it should be understood that, “soft” and “hard” in the soft support structure 41 and the hard support structure 42 provided by this embodiment are relative concepts, and are relative features of materials in two parts of structures in the foldable mechanism 40. [0041]In specific disposition, the hard support structure 42 is located in a dented area of the V-shaped support 411, and each hard support structure 42 blocks two ends of a V-shaped support 411 corresponding to the hard support structure 42. The hard support structure 42 is disposed to block openings at the two ends of the V-shaped support 411. Therefore, adverse impact caused by a gap or the like on an exterior surface of the foldable mechanism 40 to an exterior structure of the mobile terminal is avoided, and exterior consistency of the mobile terminal is improved. [0042]In specific disposition, the hard support structure 42 may use different structures. As shown in FIG. 5 and FIG. 6, each hard support structure 42 includes a first support layer 421 blocking an opening of a V-shaped support 411 corresponding to the hard support frame, and a foldable mechanism 422 blocking one end of the V-shaped support 411 exists at either end of the first support layer 421. Specifically, each hard support structure 42 includes one first support layer 421 and one foldable mechanism 422 located at either end of the first support layer 421. The first support layer 421 blocks a top opening position of the V-shaped support 411, and the foldable mechanisms 422 located at the two ends of the first support layer 421 block V-shaped openings at the two ends of the V-shaped support 411 respectively. The first support layer 421 is disposed to support the flexible display screen 10, and the foldable mechanisms 422 are disposed to block the openings at the two ends of the V-shaped support 411, thereby ensuring exterior consistency of the foldable mechanisms 422. An assembled structure is shown in FIG. 5. [0043]In addition, to improve structure strength and an exterior effect of the hard support structure 42, preferably, the hard support structure 42 further includes an exterior layer 423 disposed on an external sidewall of the foldable mechanism 422. As shown in FIG. 11 and FIG. 12, the foldable mechanism 422 at either end of the first support layer 421 of each hard support structure 42 is fixedly sleeved with an exterior layer 423. The exterior layer 423 is configured to block a gap at a joint of the foldable mechanism 422 and the V-shaped support 411, thereby improving an exterior effect of the entire foldable mechanism 422. In addition, support strength of the exterior layer 423 is higher than strength of the first support layer 421. This further enhances support strength of the entire foldable mechanism 422. That is, the exterior layer 423 is disposed to block the gap when the first support layer 421 is connected to the V-shaped support 411. This further improves an exterior effect of the mobile terminal. [0044]As a variation of the hard support structure 42 shown in FIG. 11 and FIG. 12, the hard support structure 42 may not only use the foregoing exterior layer 423, but also use a second support layer disposed on the first support layer 421 to improve a support effect and the exterior effect. Specifically, the hard support structure 42 further includes a second support layer wrapping the first support layer 421, and strength of the second support layer is higher than strength of the first support layer 421. Structurally, a structure of the second support layer is the same as a structure of the first support layer 421, that is, both include a support layer and a foldable mechanism 422 disposed at either end of the support layer. In addition, in specific disposition, the second support layer is located on one side of the first support layer 421 away from the V-shaped support 411, and the first support layer 421 and the first support layer 421 are disposed in an overlapping manner, so that the second support layer wraps the first support layer 421, that is, it may be considered that the first support layer 421 and the second support layer are disposed in a sleeving manner. In addition, in specific disposition, strength of the first support layer 421 is lower than strength of the second support layer, that is, the first support layer 421 is made of a low-strength material that cooperates more easily with the V-shaped support 411 made of a soft material, but the second support layer is made of a material of relatively high strength. Use of the foregoing materials and structures ensures a combination of the soft support structure 41 and the hard support structure 42, and also enhances a support effect of the hard support structure 42 for the flexible display screen 10. [0045]Referring to FIG. 8, FIG. 9, and FIG. 10, FIG. 8 is a status diagram in a bending process, and is a simplified schematic diagram. The mobile terminal further includes a blocking layer 431 disposed between bending tip portions of any two adjacent V-shaped supports 411. The blocking layer 431 is configured to block a gap between tip portions of the plurality of V-shaped supports 411. As shown in FIG. 1 and FIG. 2, when the mobile terminal is folded, bending tip portions of the plurality of V-shaped supports 411 converge, and each blocking layer 431 is compressed into a gap between two V-shaped supports 411 connected by the blocking layer 431, so that the foldable mechanism 40 forms a C-shaped structure, and that the first housing 20 overlaps the second housing 30 to implement folding of the mobile terminal. As shown in FIG. 3 and FIG. 4, when the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports 411 move away from each other, and each blocking layer 431 is unfolded to block the gap between the two V-shaped supports 411 connected by the blocking layer 431. In this case, the blocking layer 431 is unfolded to block the gap between the tip portions of the V-shaped supports. [0046]In specific disposition, the blocking layer 431 may use different structures to block the gap between the tip portions of the V-shaped supports 411. As shown in FIG. 8, the blocking layer 431 uses a bending piece 431. As shown in FIG. 9, the blocking layer 431 uses an elastic material layer 432. Alternatively, as shown in FIG. 10, some blocking layers 431 use bending pieces 431, and other blocking layers 431 use different structures such as elastic material layers 432 to block the tip portions of the V-shaped supports 411. For ease of understanding, the following describes the structures by using examples separately. [0047]As shown in FIG. 8, in a plurality of blocking layers 431, at least one blocking layer 431 is a bending piece 431. In the structure shown in FIG. 8, a structure in which all blocking layers 431 are bending pieces 431 is shown. However, it should be understood that, the blocking layer 431 may also use a structure different from the bending piece 431. For the bending piece 431, an odd number of creases exist on the bending piece 431, and two ends of the bending piece 431 are respectively connected to bending tip portions of V-shaped supports 411 on two sides of the blocking layer 431 on a one-to-one basis. In addition, the bending piece 431 is disposed in a gap between tip portions of adjacent V-shaped supports 411. Still referring to FIG. 8, FIG. 8 shows a bending status of the bending piece 431 in a bending process. As can be seen from FIG. 8, the crease of the bending piece 431 causes the bending piece 431 to be bent into a gap between tip portions of the adjacent V-shaped supports 411, so that the folded bending piece 431 can shrink in the gap. Therefore, when being bent, the bending piece 431 is prevented from protruding, which otherwise affects an exterior of the foldable mechanism 40. In specific disposition, the number of creases on the bending piece 431 is an odd number, for example, 1, 3, or 5. In use of the odd number of creases, it is ensured that when the bending piece 431 is bent, an outermost end of the bending piece 431 can be flush to the tip portions of the V-shaped supports 411 or shrink in the gap between the V-shaped supports 411, and further, it is ensured that the bending piece 431 does not interfere with the foldable mechanism 40 when the foldable mechanism 40 is bent. In addition, when the mobile terminal is unfolded, the bending piece 431 can be flush to the tip portions of the V-shaped supports 411 as far as possible. This ensures exterior consistency of the mobile terminal, and improves the exterior effect of the mobile terminal. In a specific implementation solution, as shown in FIG. 8, one crease exists on each bending piece 431, that is, the bending piece 431 includes a first bending piece 4311 and a second bending piece 4312. That is, when being bent, the bending piece 431 needs to be bent only once to fit into the gap between the V-shaped supports 411. This improves convenience during deformation, reduces a thickness of the bending piece 431 after the bending piece 431 is folded, and improves an effect after the bending piece 431 is bent. [0048]As a variation of the foldable mechanism 40 shown in FIG. 8, in another solution, a plurality of blocking layers 431 are a bending plate of an integrated structure, a plurality of creases are disposed on the bending plate, the bending tip portions of the plurality of V-shaped supports 411 are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports 411. In the foregoing structure, it may be considered that when each blocking layer 431 uses a bending piece 431, a plurality of bending piece 431 are connected in sequence to form an integrated structure. When the blocking layers 431 use the bending plate to block the gap formed by tip ends of the plurality of V-shaped supports, a tip portion of a V-shaped support 411 corresponds to a crease on the bending plate, and a bending plate part located on two sides of the tip portion of the V-shaped support 411, when being bent, is attached to a sidewall of the V-shaped support 411. When being bent, a bending plate part located between two V-shaped supports 411 is located in the gap between the V-shaped supports 411. A specific operating principle thereof is similar to that of the bending piece 431 shown in FIG. 8. Details are not further described herein. [0049]In another structure of the blocking layer 431, at least one blocking layer 431 in the plurality of blocking layers 431 includes an elastic material layer 432 disposed between adjacent V-shaped supports 411. As shown in FIG. 9, FIG. 9 is a schematic view of a structure that uses the elastic material layer 432 as the blocking layer 431. In this embodiment, the gap between the adjacent V-shaped supports 411 is filled with the elastic material layer 432. In specific disposition, the elastic material layer 432 may be made of different materials, for example, a material such as rubber or plastic, provided that the material can have good elasticity. After the foldable mechanism 40 is bent, the elastic material layer 432 is compressed and deformed, so that the foldable mechanism 40 can be bent. When being unfolded, the elastic material recovers to an initial state, and can effectively block the gap between the V-shaped supports 411. In a specific implementation, each blocking layer 431 may use an elastic material layer 432. Alternatively, only some blocking layers use elastic material layers 432. Specific disposition may be determined according to an actual situation. In a specific solution, each elastic material layer 432 and a V-shaped support 411 adjacent to the elastic material layer 432 are an integrated structure. That is, the elastic material layer 432 and a soft support layer are disposed by using a same material, and form an integrated structure. In this case, the soft support structure 41 may be considered as a sheet-like elastic material layer in which a plurality of V-shaped slots are provided and a hard support structure 42 is embedded in each V-shaped slot. When the foregoing structure is used, it can be seen that, when the entire soft support structure 41 is disposed, a lateral side is blocked by the elastic material layer 432, and the elastic material layer 432 and the V-shaped support 411 are disposed in an integrated structure, so that when the mobile terminal is unfolded, a lateral side away from the hard support structure 42 may be a smooth side. This further improves the exterior effect of the entire mobile terminal. [0050]In the foregoing description, the blocking layer 431 may use different structures. As shown in FIG. 10, FIG. 10 shows a form of the blocking layer 431 that uses a combination of a bending piece 431 and an elastic material. As can be seen from FIG. 10, some blocking layers 431 use bending pieces 431, and other blocking layers 431 use elastic material layers 432. That is, the elastic material layers 432 and the bending pieces 431 are mixed to form the blocking layers 431, thereby achieving an effect of blocking the gap between the V-shaped supports 411 in the soft support structure. In addition, when being bent, the blocking layers 431 can implement good deformation, and do not affect bending of the foldable mechanism 40. [0051]When the foregoing formed foldable mechanism 40 is used, the foldable mechanism 40 formed by the soft support structure 41 and the hard support structure 42 embedded in the soft support structure 41 is used as a component for connecting the first housing 20 and the second housing 30. As shown in FIG. 3 and FIG. 4, when the mobile terminal is unfolded, the foldable mechanism 40 formed by the soft support structure 41 and the hard support structure 42 is unfolded and turns into a flat structure connected to the first housing 20 and the second housing 30. As shown in FIG. 1 and FIG. 2, when the mobile terminal is folded, one side of the soft support structure 41 away from the hard support structure 42 shrinks inward, and one side of the soft support structure 41 located on the hard support structure 42 is also extended and bent, so that the entire foldable mechanism 40 forms a C-shaped structure to implement bending of the first housing 20 and the second housing 30. In the foregoing bending process, the flexible screen is supported by the hard support structure, and the shape of the foldable mechanism 40 is changed according to a change of the soft support structure 41. Therefore, continuity of connections between the foldable mechanism 40 and the first housing 20 and the second housing 30 is improved, the mobile terminal is prevented from having an abrupt exterior structure, and the exterior effect of the mobile terminal is improved. [0052]Obviously, a person skilled in the art can make various modifications and variations to the present invention without departing from the spi(String), 相关申请的交叉引用 [0001] 本申请是2017年9月19日提交的国际申请PCT/CN2017/102310的继续申请,该国际申请要求2016年9月20日提交的中国专利申请201610836223.0的优先权。上述申请的公开内容是 特此通过引用整体并入。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端的折叠机构及移动终端。 背景 [0003] 随着柔性折叠屏技术的日益成熟,可折叠终端产品也将是未来的主流趋势。 可折叠终端产品(例如可折叠手机、可折叠平板电脑、可折叠电脑等电子设备)需要有一个比较好的ID外观,这样产品才能被消费者接受。 以可折叠手机为例,与传统的翻盖手机不同,柔性可折叠手机的屏幕可以连续折叠。 为了保证折叠屏不被拉扯和挤压,产品整个外观的中间铰链折叠部分变形较大,而一般的结构无法实现如此大的变形。 因此,现有技术中的折叠机构都是采用机械联动机构实现的折叠机构,复杂度较高。 另外,当机械联动机构的部件移动时,不可避免地会影响移动终端的外观效果。 概括 [0004] 本发明实施例提供一种移动终端的折叠机构及移动终端,以提高移动终端弯曲时的效果。 [0005] 本发明实施例提供了一种移动终端的折叠机构。 折叠机构包括连接移动终端的第一壳体和第二壳体的软质支撑结构,软质支撑结构包括多个排成一排的V型支架,相邻V型支架的开口端为 连接,每个V型支架的开口面向移动终端的柔性显示屏; 折叠机构还包括硬质支撑结构,硬质支撑结构设置于各V型支架内,用于支撑柔性显示屏,各硬质支撑结构挡住与硬质支撑结构对应的V型支架的两端。 折叠机构还包括阻挡层,设置在任意两个相邻的V型支撑件的弯曲尖端部之间。 [0006] 当移动终端的折叠机构弯曲时,多个V型支撑件的弯曲尖端部分会合,每个阻挡层被压入阻挡层连接的两个V型支撑件之间的间隙中。 和 [0007] 当移动终端的折叠机构展开时,多个V型支撑件的弯曲尖端部分相互远离,各阻挡层展开以阻挡阻挡件连接的两个V型支撑件之间的缝隙。 层。 [0008]上述技术方案中,采用软质支撑结构和嵌入软质支撑结构中的硬质支撑结构形成的折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软质支撑结构和硬质支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 折叠移动终端时,软支撑结构远离硬支撑结构的一侧向内收缩,软支撑结构位于硬支撑结构上的一侧也伸展弯曲,从而形成整个折叠机构。 C型结构,实现第一壳体和第二壳体的弯折。 在上述弯折过程中,柔性屏由硬质支撑结构支撑,折叠机构的形状随着软质支撑结构的变化而变化。 从而提高了折叠机构与第一壳体和第二壳体连接的连续性,避免了移动终端的外观结构突兀,提高了移动终端的外观效果。 [0009] 在一种具体实施方案中,所述多个阻挡层为一体结构的折弯板,所述折弯板上设置有多个折痕,所述多个V型支架的折弯尖端部固定连接在折痕上。 折弯板等间距排列,相邻V型支撑之间存在奇数条折痕。 即,挡层利用弯板挡住多个V型支架的末端形成的间隙。 提高了整个移动终端的外观效果。 此外,弯曲板在弯曲时占用的空间更小。 因此,可以保证整个结构弯曲后的外观效果。 [0010] 在另一种实施方案中,多个阻挡层中的至少一个阻挡层为弯折件,弯折件上存在奇数条折痕,弯折件的两端分别连接V形的弯折尖端部。 一对一支撑在阻挡层的两侧。 即,阻挡层可以采用弯折件的结构。 该折弯件与上述折弯板在结构上没有太大区别。 唯一不同的是,该方案中的弯曲件位于两个V型支架之间。 另外,在该方案中,当所有阻挡层都采用如上所述的折弯件时,折弯件连接后,与折弯板在结构上没有太大的区别。 但是,该方案中的阻挡层不仅采用弯折件的结构,还可以采用另一种折叠机构。 因此,可以采用不同的结构来阻挡V型支架。 具体方案中,每个折弯件上存在一条折痕。 也就是说,在弯曲时,弯曲件只需弯曲一次即可嵌入到V型支架之间的缝隙中。 提高了变形时的便利性,减小了弯折件折叠后的厚度,提高了弯折件弯折后的效果。 [0011] 另外,在第三种实施方案中,所述多个阻挡层中的至少一个阻挡层包括设置在相邻V型支撑件之间的弹性材料层。 即,V型支撑件之间的间隙被弹性材料层填充。 折叠机构弯折后,弹性材料层受压变形,使得折叠机构可弯折。 弹性材料在展开时恢复到初始状态,可以有效地堵住V型支架之间的缝隙。 在具体实施中,各阻挡层可以采用弹性材料层。 或者,只有部分阻挡层使用弹性材料层。 [0012]在第四种实施方案中,部分阻挡层可以使用弯折件,其他阻挡层可以使用弹性材料层,即弹性材料层和弯折件混合形成阻挡层,从而达到阻挡的效果。 软支撑结构中 V 形支撑之间的间隙。 另外,在弯曲时,阻挡层可以实现良好的形变,不影响折叠机构的弯曲。 [0013] 上述方案中,当采用弹性材料层作为阻挡层时,各弹性材料层和与弹性材料层相邻的V型支架为一体结构。 即,弹性材料层和软质支撑层采用相同的材​​料设置。 在这种情况下,软支撑结构可以被认为是片状弹性层,其中设置有多个V形槽,并且在每个V形槽中嵌入硬支撑结构。 [0014] 在具体配置中,硬支撑结构可以采用不同的结构。 在一种方式中,每个硬质支撑结构包括第一支撑层,第一支撑层挡住与硬质支撑架对应的V型支架的开口,第一支架的两端分别设有挡住V型支架一端的折叠机构。 层。 即,柔性显示屏由第一支撑层支撑,V型支撑体两端开口采用折叠机构封闭。 因此,防止移动终端具有外部间隙或孔。 这提高了移动终端的外观效果。 [0015] 在一个方案中,硬质支撑结构还包括设置在可折叠机构的外侧壁上的外层。 当第一支撑层连接至V型支撑件时,设置外层以阻挡间隙。 这进一步提高了移动终端的外观效果。 [0016] 此外,为了增强硬质支撑结构的支撑强度,硬质支撑结构与软质支撑结构之间的连接强度得到提高。 在一种改进方案中,所述硬质支撑结构还包括包裹所述第一支撑层的第二支撑层,所述第二支撑层的强度高于所述第一支撑层的强度。 即,硬质支撑结构的第一支撑层采用与软质支撑结构的粘合效果较好且硬度较小的材料,而第二支撑层可以采用与软质支撑结构具有较高支撑力的材料制成 力量。 提高了硬质支撑结构对柔性显示屏的支撑效果。 [0017] 本发明实施例还提供了一种移动终端。 该移动终端包括壳体和设置在壳体内的柔性显示屏,壳体包括第一壳体、第二壳体以及根据前述任一项所述的用于实现第一壳体和第二壳体折叠的折叠机构。 . [0018]上述技术方案中,采用软质支撑结构和嵌入软质支撑结构中的硬质支撑结构形成的折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软质支撑结构和硬质支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 折叠移动终端时,软支撑结构远离硬支撑结构的一侧向内收缩,软支撑结构位于硬支撑结构上的一侧也伸展弯曲,从而形成整个折叠机构。 C型结构,实现第一壳体和第二壳体的弯折。 在上述弯折过程中,柔性屏由硬质支撑结构支撑,折叠机构的形状随着软质支撑结构的变化而变化。 从而提高了折叠机构与第一壳体和第二壳体连接的连续性,避免了移动终端的外观结构突兀,提高了移动终端的外观效果。 附图说明 [0019] 图1是本发明一个实施例的移动终端处于折叠状态的示意图; [0020] 图2是本发明一个实施例的移动终端处于折叠状态的分解示意图; [0021] 图3是本发明一个实施例的移动终端处于展开状态的示意图; [0022] 图4是本发明一个实施例的移动终端处于展开状态的分解示意图; [0023] 图5为本发明一实施例的折叠机构处于弯曲状态的示意图。 [0024] 图6为本发明一实施例的折叠机构处于弯曲状态的分解示意图。 [0025] 图7为本发明一实施例的折叠机构处于展开状态的示意图。 [0026] 图8为本发明实施例的折叠机构在折弯过程中的状态示意图; [0027] 图9为本实用新型一实施例的另一种折叠机构的分解示意图。 [0028] 图10为本发明实施例的第三种折叠机构的示意图。 [0029] 图11为本发明一实施例的硬质支撑结构的剖面图。 和 [0030] 图12为本发明一实施例的使用图11所示的硬质支撑结构时的折叠机构的分解示意图。 附图中的参考标记 [0031]10 :柔性显示屏; 20 : 第一住房; 30 : 第二套住房[0032]40 :可折叠机制; 41 :软支撑结构; 411 :V型支撑[0033]42 :硬支撑结构; 421 :第一支撑层; 422 :折叠机制[0034]423 : 外层; 43 : 阻挡层; 431 : 弯曲件; 4311 :第一个弯曲件[0035]4312 : 第二弯曲件; 432 : 弹性材料层 具体实施方式 [0036] 为使本发明的目的、技术方案和优点更加清楚,下面将结合附图对本发明作进一步地详细描述。 显然,所描述的实施例仅仅是本发明的一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0037] 如图1和图3所示,图1和图3是根据本发明实施例的移动终端在不同状态下的示意图。 [0038] 本发明实施例提供了一种移动终端的折叠机构。 折叠机构应用于移动终端。 移动终端包括外壳和柔性显示屏 10 布置在外壳中。 外壳包括第一外壳 20 , 第二个住房 30 , 和可折叠机制 40 用于实现第一外壳的折叠 20 和第二个住房30 根据上述任何一项。 第一住房 20 和第二个住房 30 由可折叠机构连接 40 形成一个整体。 柔性显示屏 10 安装在由第一壳体形成的壳体中 20 和第二个住房 30 . [0039] 如图5、图6、图7所示,图5、图7为折叠机构示意图 40 不同状态下,图6为折叠机构的分解示意图 40 . 可折叠机构 40 本实施例提供的弯折功能。 可折叠机构 40 可用于实现第一外壳的弯曲和展开 20 和第二个住房 30 ,即实现移动终端的折叠和展开。 具体来说,折叠机构 40 包括软支撑结构 41 连接第一个外壳 20 和第二个住房 30 . 软支撑结构 41 包括多个V形支架 411 单排排列,相邻V型支架两端开口 411 连接。 具体地,如图5和图6所示,两个相邻V型支架之间的侧壁顶部位置 411 连接起来,并且多个V形支撑 411 依次连接,使得多个V形支架 411 连接起来形成一个整体。 另外,在具体配置中,每个V型支架的长度方向 411 平行于第一壳体的旋转方向 20 相对于第二个住房 30 ,也就是说,在 V 形支撑 411 单排排列,V型支撑 411 位于两端连接第一壳体 20 和第二个住房 30 分别。 因此,当第一个住房 20 和第二个住房 30 相对旋转,V形支撑 411 可以变形,并且 V 形支撑的尖端部分 411 向趋同的方向发展。 因此,软支撑架形成一个结构,其内部(远离柔性显示屏的一侧 10 ) 会聚及其外部(面向柔性显示屏 10 ) 被扩展。 [0040] 此外,在配置中,每个V形支架的开口 411 面向柔性显示屏 10 和硬支撑结构 42 配置为支持柔性显示屏 10 设置在每个V型支架中 411 . 硬支撑结构 42 固定在V型支架的凹槽部分 411 ,面向柔性显示屏 10 . 硬支撑结构 42 , 第一个住房 20 , 和第二个住房 30 共同构成柔性显示屏的支撑结构 10 . 在上述描述中,应当理解,软支撑结构中的“软”和“硬” 41 和硬支撑结构 42 本实施例提供的是相对概念,是折叠机构中两部分结构的材料的相对特征。 40 . [0041] 具体配置中,硬支撑结构 42 位于 V 形支架的凹陷区域 411 , 和每个硬支撑结构 42 挡住V型支架的两端 411 对应硬支撑结构 42 . 硬支撑结构 42 设置成堵住V型支架两端的开口 411 . 因此,可折叠机构的外表面上的间隙等造成的不利影响 40 避免了移动终端的外观结构,提高了移动终端的外观一致性。 [0042] 具体配置中,硬支撑结构 42 可以使用不同的结构。 如图5和图6所示,各硬支撑结构 42 包括第一支撑层 421 堵住V型支架的开口 411对应硬质支撑架,折叠机构 422 挡住V型支架的一端 411 存在于第一支撑层的两端 421 . 具体来说,每个硬支撑结构 42 包括一个第一支撑层 421 和一个可折叠机构 422 位于第一支撑层的两端 421 . 第一支撑层 421 挡住V型支架的顶部开口位置 411 , 以及可折叠机制 422 位于第一支撑层的两端 421 V型支架两端挡V型开口 411 分别。 第一支撑层 421 用以支撑柔性显示屏 10 , 以及可折叠机制 422 设置成堵住V型支架两端的开口 411 ,从而确保可折叠机制的外部一致性 422 . 组装后的结构如图5所示。 [0043] 此外,提高硬支撑结构的结构强度和外部效果 42 , 最好是硬支撑结构 42 还包括外层 423 设置在折叠机构的外侧壁上 422 . 如图11和图12所示,折叠机构 422 在第一支撑层的两端 421 每个硬支撑结构 42 固定套有外层 423 . 外层 423 用于堵住折叠机构的连接处的缝隙 422 和V形支撑 411 ,从而提升整个折叠机构的外观效果 422 . 此外,外层的支撑强度 423 高于第一支撑层的强度 421 . 这进一步增强了整个折叠机构的支撑强度 422 . 即外层 423 被布置成在第一支撑层时阻挡间隙 421 连接到V型支架 411 . 这进一步改善了移动终端的外观效果。 [0044] 作为硬支撑结构的变体 42 如图11和图12所示,硬支撑结构 42 可能不仅使用前述外层 423 , 但也使用设置在第一支撑层上的第二支撑层 421 提高支撑效果和外在效果。 具体来说,硬支撑结构 42 还包括包裹第一支撑层的第二支撑层 421 ,且第二支撑层的强度高于第一支撑层的强度 421 . 在结构上,第二支撑层的结构与第一支撑层的结构相同 421 ,也就是说,两者都包括支撑层和可折叠机构 422 设置在支撑层的两端。 另外,在具体设置中,第二支撑层位于第一支撑层的一侧 421 远离V型支撑 411 , 和第一支撑层 421 和第一支撑层 421 以重叠方式设置,使得第二支撑层包裹第一支撑层 421 ,也就是说,可以认为第一支撑层 421 第二支撑层套设设置。 另外,在具体配置中,第一支撑层的强度 421 低于第二支撑层即第一支撑层的强度 421 由低强度材料制成,更容易与V型支架配合 411 由柔软的材料制成,而第二支撑层由强度较高的材料制成。 上述材料和结构的使用确保了软支撑结构的组合 41 和硬支撑结构 42 ,也增强了硬支撑结构的支撑作用 42 用于柔性显示屏 10 . [0045]请参阅图8、图9、图10,图8为折弯过程中的状态图,为简化示意图。 移动终端还包括阻挡层 431 设置在任意两个相邻V型支架的弯曲尖端部分之间 411 . 阻挡层 431 被配置为阻塞多个V形支撑件的尖端部分之间的间隙 411 . 如图1和图2所示,当移动终端折叠时,多个V型支架的尖端部分弯曲 411 收敛,每个阻塞层 431 被压缩到两个 V 形支撑之间的间隙中 411 由阻塞层连接 431 ,这样折叠机构 40 形成一个C形结构,并且第一个外壳 20 与第二个外壳重叠 30 实现移动终端的折叠。 如图3和图4所示,当移动终端展开时,多个V形支架的弯曲尖端部分 411 彼此远离,每个阻挡层 431 展开挡住两个V型支架之间的缝隙 411 由阻塞层连接 431 . 在这种情况下,阻挡层 431 展开以堵住V形支架尖端部分之间的间隙。 [0046] 具体配置中,阻挡层 431 可以使用不同的结构来堵住V形支架尖端部分之间的间隙 411 . 如图8所示,阻挡层 431 使用弯曲件 431 . 如图9所示,阻挡层 431 使用弹性材料层 432 . 或者,如图10所示,一些阻挡层 431 使用弯曲件 431 和其他阻挡层 431 使用不同的结构,例如弹性材料层 432 挡住 V 形支架的尖端部分 411 . 为了便于理解,下面分别举例说明结构。 [0047] 如图8所示,在多个阻挡层中 431 , 至少一层阻挡层 431 是弯曲件 431 . 在图8所示的结构中,所有阻挡层的结构 431 是弯曲件 431 显示。 但是,应该理解的是,阻挡层 431 也可采用与弯管件不同的结构 431 . 对于弯曲件 431 , 折弯件上存在奇数条折痕 431 , 弯曲件的两端 431 分别连接到V形支架的弯曲尖端部分 411 在阻挡层的两侧 431 在一对一的基础上。 另外,弯曲件 431 设置在相邻V型支架的尖端部分之间的间隙中 411 . 仍然参见图8,图8显示了弯曲件的弯曲状态 431 在弯曲过程中。 从图8可以看出,折弯件的折痕 431 导致弯曲件 431 弯入相邻V型支架尖端部分之间的缝隙 411 , 使折叠的弯曲件 431 可以缩小在差距。 因此,弯曲时,弯曲件 431 防止突出,否则会影响可折叠机构的外部 40 . 具体配置中,折弯件的折痕数量 431 为奇数,例如1、3、5。在使用奇数折痕时,保证折弯件时 431 弯曲,弯曲件的最外端 431 可以齐平到 V 形支架的尖端部分 411 或缩小V形支架之间的间隙 411 , 进一步保证弯曲件 431 不干扰折叠机制 40 当折叠机制 40 是弯曲的。 另外,当移动终端展开时,弯折件 431 可以齐平到 V 形支架的尖端部分 411越远越好。 保证了移动终端外观的一致性,提高了移动终端的外观效果。 在一种具体实施方案中,如图8所示,每个折弯件上存在一条折痕 431 , 即弯曲件 431 包括第一弯曲件 4311 和第二个弯曲件 4312 . 即弯曲时,弯曲件 431 只需弯曲一次即可装入 V 形支架之间的间隙 411 . 这提高了变形过程中的便利性,减少了弯曲件的厚度 431 弯曲件后 431 折叠,提高了折弯件后的效果 431 是弯曲的。 [0048] 作为可折叠机制的变体 40 如图8所示,在另一种方案中,多个阻挡层 431 为一体结构的折弯板,折弯板上设置有多个折痕,多个V形支架的折弯尖端部分 411 等间距固定连接在弯板上的折痕上,相邻V型支撑之间存在奇数个折痕 411 . 在上述结构中,可以认为当每个阻挡层 431 使用弯曲件 431 , 多个折弯件 431 依次连接形成一个整体结构。 当阻挡层 431 利用弯板堵住多个V型支架的尖端形成的缝隙,V型支架的尖端部分 411 对应折弯板上的折痕,折弯板部分位于V型支架尖端部分的两侧 411 , 弯曲时, 附在 V 形支架的侧壁上 411 . 弯曲时,位于两个V型支架之间的弯曲板部分 411 位于V型支架之间的空隙中 411 . 其具体工作原理与弯管件类似 431 如图8所示,在此不再赘述。 [0049] 在阻挡层的另一种结构中 431 , 至少一层阻挡层 431 在多个阻挡层中 431 包括弹性材料层 432 布置在相邻的V形支架之间 411 . 如图9所示,图9为采用弹性材料层的结构示意图 432 作为阻挡层 431 . 在本实施例中,相邻V型支架之间的间隙 411 填充有弹性材料层 432 . 具体配置中,弹性材料层 432 可以由不同的材料制成,例如橡胶或塑料等材料,只要该材料能够具有良好的弹性。 后折叠机构 40 被弯曲时,弹性材料层 432 被压缩变形,使折叠机构 40 可以弯曲。 展开时,弹性材料恢复初始状态,可有效堵住V型支架之间的缝隙 411 . 在具体实现中,每个阻塞层 431 可以使用弹性材料层 432 . 或者,只有一些阻挡层使用弹性材料层 432 . 具体配置可根据实际情况确定。 在具体方案中,各弹性材料层 432 和一个V形支架 411 紧邻弹性材料层 432 是一个集成的结构。 即弹性材料层 432 软质支撑层采用同种材料设置,形成一体结构。 在这种情况下,软支撑结构 41 可以认为是片状弹性材料层,其中设置有多个V形槽和硬质支撑结构 42 嵌在每个 V 形槽中。 当采用上述结构时,可以看出,当整个软支撑结构 41 设置时,侧面被弹性材料层挡住 432 , 和弹性材料层 432 和V形支撑 411一体式结构设置,使得移动终端展开时,远离硬质支撑结构的侧面 42 可能是光滑的一面。 这进一步提高了整个移动终端的外观效果。 [0050] 在前面的描述中,阻挡层 431 可以使用不同的结构。 如图10所示,图10为阻挡层的一种形式 431 使用弯曲件的组合 431 和弹性材料。 从图10可以看出,一些阻挡层 431 使用弯曲件 431 和其他阻挡层 431 使用弹性材料层 432 . 即弹性材料层 432 和弯曲件 431 混合形成阻挡层 431 ,从而达到堵住V型支架之间缝隙的效果 411 在软支撑结构中。 此外,当被弯曲时,阻挡层 431 可以实现良好的变形,不影响折叠机构的弯曲 40 . [0051] 当上述形成折叠机构时 40 使用,可折叠机制 40 由软支撑结构形成 41 和硬支撑结构 42 嵌入软支撑结构 41 用作连接第一壳体的组件 20 和第二个住房 30 . 如图3和图4所示,当移动终端展开时,折叠机构 40 由软支撑结构形成 41 和硬支撑结构 42 展开后变成平面结构连接到第一壳体 20 和第二个住房 30 . 如图1和图2所示,当移动终端折叠时,软支撑结构的一侧 41 远离硬支撑结构 42 向内收缩,软支撑结构的一侧 41 位于硬支撑结构上 42 也延伸和弯曲,使整个折叠机构 40 形成C型结构实现第一壳体的弯折 20 和第二个住房 30 . 在上述弯曲过程中,柔性屏由硬质支撑结构支撑,折叠机构的形状 40 根据软支撑结构的变化而变化 41 . 因此,可折叠机构之间连接的连续性 40 和第一个住房 20 和第二个住房 30 通过改进,避免了移动终端的外观结构突兀,提高了移动终端的外观效果。 [0052] 显然,本领域的技术人员可以对本发明进行各种更改和变型而不脱离本发明的精神和范围。 本发明旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN107846484A(String), CN107846484B(String), EP3352044A1(String), EP3352044A4(String), EP3352044B1(String), EP3690598A1(String), KR1020180064472A(String), KR102063283B1(String), US10310566B2(String), US20180373297A1(String), WO2018054291A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN107846484A(String), CN107846484B(String), EP3352044A1(String), EP3352044A4(String), EP3352044B1(String), EP3690598A1(String), KR1020180064472A(String), KR102063283B1(String), US10310566B2(String), US20180373297A1(String), WO2018054291A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10310566B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.244 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN107846484A(String), CN107846484B(String), EP3352044A1(String), EP3352044A4(String), EP3352044B1(String), EP3690598A1(String), KR1020180064472A(String), KR102063283B1(String), US10310566B2(String), US20180373297A1(String), WO2018054291A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.246 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), CN107846484A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), CN107846484B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), EP3352044A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), EP3352044A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), EP3352044B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), EP3690598A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), KR1020180064472A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), KR102063283B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), US10310566B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.342 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), US20180373297A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), WO2018054291A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10310566B2(String), US10310566B2(String), 1559577600(Integer), 270683(Integer), 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185005(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185005(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185005(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185005(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.407 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.430 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.430 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.432 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.433 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.435 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9292680B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal detection method and mobile terminal(String), 移动终端检测方法及移动终端(String), US9292680B2(String), A mobile terminal detection method and a mobile terminal. The method includes: reading a first international mobile equipment identity (IMEI) stored in a flash; comparing the first IMEI with a backup IMEI stored in a one-time programmable data (OTP) region which is prohibited from being modified; and disabling the mobile terminal when the first IMEI and the backup IMEI are inconsistent. In the present invention, the IMEI plaintext is directly backed up to the OTP region of the mobile terminal, and the value of the IMEI stored in the flash and the value of the backup IMEI are dynamically compared, so as to conveniently detect the legitimacy of the IMEI of the mobile terminal, effectively protect the IMEI number of the mobile terminal from being arbitrarily modified, and ensure the legitimate interests of users and operators.(String), 一种移动终端检测方法及移动终端。 该方法包括:读取闪存中存储的第一国际移动设备标识(IMEI); 将第一IMEI与存储在禁止修改的一次性可编程数据(OTP)区域中的备份IMEI进行比较; 当第一IMEI和备份IMEI不一致时,禁用移动终端。 本发明直接将IMEI明文备份到移动终端的OTP区域,并动态比较存储在flash中的IMEI值与备份IMEI值,方便检测合法性。 移动终端IMEI,有效保护移动终端IMEI号不被任意修改,保障用户和运营商的合法权益。(String), US14/396174(String), 1372176000(Integer), US9292680B2(String), 1458576000(Integer), 1458576000(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 26(Integer), CN100401822C | CN101719959A | CN102083055A | CN102625281A | CN102831079A | CN1722878A | KR1020090059346A | US20020120873A1 | US20020147918A1 | US20040204021A1 | US20050079868A1 | US20060236111A1 | US20070050622A1 | US20070077912A1 | US20070259683A1 | US20110003581A1 | US20110070866A1 | US20110117881A1 | US20120021805A1 | US20120157055A1 | US20130157715A1 | US20130279689A1 | US6223290B1 | US6707915B1 | US8660529B2(String), 5(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185006(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\3d8c677ee6e94a47b3ef4b0e1c638634.png(String), 185006(Integer), 3d8c677ee6e94a47b3ef4b0e1c638634.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal detection method and mobile terminal(String), 移动终端检测方法及移动终端(String), US9292680B2(String), A mobile terminal detection method and a mobile terminal. The method includes: reading a first international mobile equipment identity (IMEI) stored in a flash; comparing the first IMEI with a backup IMEI stored in a one-time programmable data (OTP) region which is prohibited from being modified; and disabling the mobile terminal when the first IMEI and the backup IMEI are inconsistent. In the present invention, the IMEI plaintext is directly backed up to the OTP region of the mobile terminal, and the value of the IMEI stored in the flash and the value of the backup IMEI are dynamically compared, so as to conveniently detect the legitimacy of the IMEI of the mobile terminal, effectively protect the IMEI number of the mobile terminal from being arbitrarily modified, and ensure the legitimate interests of users and operators.(String), 一种移动终端检测方法及移动终端。 该方法包括:读取闪存中存储的第一国际移动设备标识(IMEI); 将第一IMEI与存储在禁止修改的一次性可编程数据(OTP)区域中的备份IMEI进行比较; 当第一IMEI和备份IMEI不一致时,禁用移动终端。 本发明直接将IMEI明文备份到移动终端的OTP区域,并动态比较存储在flash中的IMEI值与备份IMEI值,方便检测合法性。 移动终端IMEI,有效保护移动终端IMEI号不被任意修改,保障用户和运营商的合法权益。(String), US14/396174(String), 1372176000(Integer), US9292680B2(String), 1458576000(Integer), 1458576000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 26(Integer), CN100401822C | CN101719959A | CN102083055A | CN102625281A | CN102831079A | CN1722878A | KR1020090059346A | US20020120873A1 | US20020147918A1 | US20040204021A1 | US20050079868A1 | US20060236111A1 | US20070050622A1 | US20070077912A1 | US20070259683A1 | US20110003581A1 | US20110070866A1 | US20110117881A1 | US20120021805A1 | US20120157055A1 | US20130157715A1 | US20130279689A1 | US6223290B1 | US6707915B1 | US8660529B2(String), \20230420\3d8c677ee6e94a47b3ef4b0e1c638634.png(String), 5(Integer), 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185006(Integer), 1. A mobile terminal detection method, comprising:powering up said mobile terminal, and reading a flag file stored in a flash;when said flag file exists, if detecting that there is an initial international mobile terminal equipment identity (IMEI) in said flag file, writing said initial IMEI into a one-time programmable data region of said mobile terminal as a backup IMEI, and deleting said flag file;when said flag file exists, if the initial IMEI is not detected in said flag file, determining that said mobile terminal is in a production phase, and normally starting up the mobile terminal;when said flag file does not exist, determining that said initial IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, giving a prompt, and performing IMEI validation by:reading a first IMEI stored in said flash;comparing said first IMEI with said backup IMEI stored in said one-time programmable data region which is prohibited from being modified, to determine whether said initial IMEI is modified;wherein if said first IMEI and said backup IMEI are inconsistent as a result of said comparing, disabling said mobile terminal, andif said first IMEI and said backup IMEI are consistent as a result of said comparing, allowing said mobile terminal to access a network.(String), 1、一种移动端检测方法,包括:为所述移动终端上电,读取存储在flash中的flag文件;当所述标志文件存在时,若检测到所述标志文件中存在初始国际移动终端设备标识(IMEI),则将所述初始IMEI写入所述移动终端的一次性可编程数据区作为备份IMEI,并删除所述初始IMEI标志文件;当所述flag文件存在时,若未在所述flag文件中检测到初始IMEI,则确定所述移动终端处于生产阶段,正常开机。当所述标志文件不存在时,确定所述初始IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并进行提示,并通过以下方式进行IMEI验证:读取存储在所述闪存中的第一IMEI;将所述第一IMEI与存储在所述不可修改的一次性可编程数据区中的所述备份IMEI进行比较,判断所述初始IMEI是否被修改;其中,如果作为所述比较的结果,所述第一IMEI和所述备份IMEI不一致,则禁用所述移动终端,以及如果所述第一IMEI和所述备份IMEI比较结果一致,则允许所述移动终端接入网络。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.483 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185006(Integer), 2. The method of claim 1,further comprises:when said flag file does not exist, determining that said IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, giving a prompt.(String), 2.如权利要求1所述的方法,还包括:当所述标志文件不存在时,确定所述IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并给出提示。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185006(Integer), 3. The method of claim 1, wherein,after said mobile terminal accesses to said network, further comprising:when said first IMEI is modified, automatically comparing said first IMEI with said backup IMEI, if they are inconsistent, disabling said mobile terminal.(String), 3.如权利要求1所述的方法,其中,所述移动终端接入所述网络后,还包括:当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185006(Integer), 4. A mobile terminal, comprising:circuitry including memory with program instructions stored therein;a writing unit stored in the memory and configured to, when powering up the mobile terminal, read a flag file stored in a flash; when said flag file exists, if an initial international mobile terminal equipment identity (IMEI) is detected in said flag file, write said initial IMEI into a one-time programmable data region of said mobile terminal as a backup IMEI, and delete said flag file; when said flag file exists, if no initial IMEI is detected in said flag file, determine that said mobile terminal is in a production phase and normally starting of the mobile terminal;a prompting module stored in the memory and configured to, when said flag file does not exist, determine that said initial IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, giving a prompt; and the mobile terminal performs IMEI validation when said flag file does not exist by:reading, by a reading unit stored in the memory, a first IMEI stored in said flash;comparing, by a checking unit stored in the memory, said first IMEI with said backup IMEI stored in said one-time programmable data region which is prevented from being modified to determine whether said initial IMEI is modified; anddisabling said mobile terminal, by a disabling unit stored in the memory, if said first IMEI and said backup IMEI are inconsistent as a result of said comparing; andallowing said mobile terminal to access a network, by an enabling unit stored in the memory, if said first IMEI and said backup IMEI are consistent as a result of said comparing.(String), 4.移动终端,包括:包括存储有程序指令的存储器的电路;写入单元,存储在存储器中,用于在移动终端上电时,读取闪存中存储的标志文件;当所述标志文件存在时,如果在所述标志文件中检测到初始国际移动终端设备标识(IMEI),则将所述初始IMEI写入所述移动终端的一次性可编程数据区作为备份IMEI,并删除所述标志文件;当存在所述flag文件时,若未在所述flag文件中检测到初始IMEI,则确定所述移动终端处于生产阶段,正常开机;提示模块,存储在存储器中,用于当所述标志文件不存在时,确定所述初始IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并进行提示。当所述标志文件不存在时,移动终端通过以下方式进行IMEI验证:存储在存储器中的读取单元读取存储在所述闪存中的第一IMEI;通过存储在存储器中的校验单元将所述第一IMEI与存储在所述一次性可编程数据区中的防止修改的所述备份IMEI进行比较,以确定所述初始IMEI是否被修改;和如果所述第一IMEI与所述备份IMEI不一致,则通过存储在内存中的禁用单元禁用所述移动终端;和如果所述第一IMEI与所述备份IMEI的比较结果一致,则通过存储在存储器中的使能单元允许所述移动终端接入网络。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185006(Integer), 5. The mobile terminal of claim 4, further comprising a flash detecting unit stored in the memory, wherein:said flash detecting unit is configured to, when said first IMEI is modified, automatically compare said first IMEI with said backup IMEI, and if they are inconsistent, disable said mobile terminal.(String), 5.如权利要求4所述的移动终端,还包括存储在存储器中的闪光检测单元,其中:所述flash检测单元用于当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185006(Integer), CROSS-REFERENCE TO RELATED APPLICATION(S) [0001]This application is the US National Phase application of PCT application number PCT/CN2013/077970 having a PCT filing date of Jun. 26, 2013, which claims priority of Chinese patent application 201210295759.8 filed on Aug. 20, 2012, the disclosures of which are hereby incorporated by reference. TECHNICAL FIELD [0002]The present document relates to the mobile terminal technology, and more particularly, to a mobile terminal detection method and a mobile terminal. BACKGROUND [0003]International Mobile Equipment Identity (IMEI) consists of 15 digits, and is commonly known as serial number and stored in an EEPROM. Each mobile terminal corresponds to a unique IMEI, and will be written with a unique IMEI when assembled and delivered from the factory. From production to delivery, the IMEI will be recorded by manufacturing vendors, and it is also the archive number and ID number of said mobile terminal at the manufacturer side. [0004]IMEI consists of TAO+FAC+SNR+SP. [0005]1, the first six digits (TAO) are the type approval number, generally representing the model, [0006]2, the following two digits (FAC) are the final assembling number, usually representing the origin, [0007]3, the following 6 digits (SNR) is a string number, generally representing the production serial number, [0008]4, the last digit (SP) is usually 0, representing the check code. [0009]In the standby screen, inputting *#06# can check the IMEI. Only a mobile terminal having an IMEI can be used in the GSM/UMTS/LTE network, and the operators can identify the device type according to the IMEI, and then provide related services, users can also make use of the IMEI to determine whether the purchased mobile terminal is an original production or not. [0010]Since the IMEI of said mobile terminal is written in a Flash that can be repeatedly read and written, it will be relatively easy to be modified by computer programs to deceive the network to obtain illegal status or function, thus the IMEI protection would be included within the requirements of the operator. [0011]The related design idea proposed aiming to the IMEI protection is to use the IMEI and the device parameters to generate the checked value with the relevant algorithm and store it in an one-time programmable (OTP) region, at each time of starting up the host, said checked value will be compared, and the usage is limited if they are different; or use an external device, and said external device encrypts the IMEI with a certain encryption algorithm to form into the ciphertext which is stored together with the decryption key in said OTP region, and accesses to the plaintext data after decrypting the ciphertext with the decryption key, and then connects with the communication terminal to verify. [0012]The abovementioned technique has the following problem: the way of protecting the IMEI is too complicated, increasing the difficulty of implementation, or it needs to use an external device to protect the IMEI, so that the mobile terminal is not convenient to use. SUMMARY [0013]To solve the technical problem, the embodiment of the present document provides a mobile terminal detection method and a mobile terminal, used to solve the shortcoming that the method for protecting the IMEI is too complex in the related art. [0014]To solve the abovementioned technical problem, the embodiment of the present document provides a mobile terminal detection method, and said method comprising: [0015]reading a first international mobile terminal equipment identity (IMEI) stored in a flash; [0016]comparing said first IMEI with a backup IMEI stored in a one-time programmable data region which is prevented from being modified; [0017]if said first IMEI and said backup IMEI are inconsistent, disabling said mobile terminal. [0018]Preferably, before reading said first IMEI stored in said flash, the method further comprises: [0019]powering up, and reading a flag file stored in said flash; [0020]when said flag file exists, if detecting there is an initial IMEI in said flag file, writing said initial IMEI into said one-time programmable data region as a backup IMEI, and deleting said flag file. [0021]Preferably, when said flag file exists, if the initial IMEI is not detected in said flag file, it is determined that said mobile terminal is in the production phase. [0022]Preferably, after reading said flag file stored in said flash, the following is further comprised: [0023]when said flag file does not exist, determining that said IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, and giving a prompt. [0024]Preferably, after comparing said first IMEI with said backup IMEI stored in said one time programmable data region, the following is further comprised: [0025]if said first IMEI and said backup IMEI are consistent, allowing said mobile terminal to access to a network. [0026]Preferably, after said mobile terminal accesses to said network, the following is further comprised: [0027]when said first IMEI is modified, automatically comparing said first IMEI with said backup IMEI, if they are inconsistent, disabling said mobile terminal. [0028]To solve the abovementioned technical problem, the embodiment of the present document further provides a mobile terminal, comprising: [0029]a reading unit, which is set to read a first international mobile terminal equipment identity (IMEI) stored in a flash; [0030]a checking unit, which is set to compare said first IMEI with a backup IMEI stored in an one-time programmable data region, and said one-time programmable data region is prevented from being modified; and [0031]a disabling unit, which is set to, if said first IMEI and said backup IMEI are inconsistent, disable said mobile terminal. [0032]Preferably, said mobile terminal further comprises a writing unit, wherein: [0033]said writing unit is set to, when powering up, read a flag file stored in said flash; when said flag file exists, if an initial IMEI is detected in said flag file, write said initial IMEI into said one-time programmable data region as said backup IMEI, and delete said flag file. [0034]Preferably, said writing unit is further set to, when said flag file exists, if no initial IMEI is detected in said flag file, determine that said mobile terminal is in the production phase. [0035]Preferably, said mobile terminal further comprises a prompting module, wherein: [0036]said prompting module is set to, when said flag file does not exist, determine that said IMEI has been written into said mobile terminal, and give a prompt. [0037]Preferably, said mobile terminal further comprises an enabling unit, wherein: [0038]the checking unit comprises: [0039]a one-time programmable data region reading module for reading said backup IMEI in said one-time programmable data region; [0040]a comparing module for comparing said first IMEI with said backup IMEI; [0041]said enabling unit is set to: if said first IMEI and said backup IMEI are consistent, allow said mobile terminal to access to the network. [0042]Preferably, the abovementioned mobile terminal further comprises a flash detecting unit, wherein: [0043]said flash detecting unit is set to, when said first IMEI is modified, automatically compare said first IMEI with said backup IMEI, if they are inconsistent, disable said mobile terminal. [0044]The beneficial effects of the abovementioned technical scheme of the present document are as follows: the OTP region is prohibited from modifying the data within it, and then the backup IMEI therein may not be modified, effectively protecting the IMEI of said mobile from being modified arbitrarily, and ensuring the legitimate interests of the users and operators. BRIEF DESCRIPTION OF THE DRAWINGS [0045]FIG. 1 is a schematic diagram of a mobile terminal detection method in accordance with an embodiment of the present document; [0046]FIG. 2 a structural diagram of a mobile terminal in accordance with an embodiment of the present document. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0047]Hereinafter with reference to the accompanying drawings, the embodiments of the present document will be described in detail. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments of the present application may be arbitrarily combined with each other. [0048]The embodiments of the present document directly back up the IMEI plaintext into a one-time programmable data (OTP) region of a mobile terminal, and dynamically compare the value of the IMEI standardly stored in the flash with the value of said backup IMEI. [0049]A mobile terminal detection method according to an embodiment of the present document, as shown in FIG. 1, comprises the following steps. [0050]In step 101, read the first international mobile equipment identity (IMEI) stored in the flash; [0051]In step 102, compare said first IMEI with the backup IMEI stored in the one-time programmable (OTP) data region, and said one-time programmable data region is prohibited from being modified; [0052]In step 103, if said first IMEI and said backup IMEI are inconsistent, disable said mobile terminal. [0053]Applying the provided technical scheme, the OTP region is prohibited to modify the data within it, and then it is impossible to modify the backup IMEI therein, effectively protecting the IMEI of said mobile terminal from being arbitrarily modified, and ensuring the legitimate interests of the users and operators. [0054]Only after said mobile terminal accesses to the network can it enjoy the network services provided by the operators. [0055]In a preferred embodiment, before reading the first IMEI stored in the flash, the following is further comprised: [0056]powering up, and reading the flag file stored in the flash; [0057]when said flag file exists, reading the initial IMEI in said flag file, if detecting the initial IMEI, writing said initial IMEI into said one-time programmable data region as said backup IMEI, and deleting said flag file. [0058]If the original IMEI is not detected in said flag file, it is determined that said mobile terminal is in the production phase. [0059]In one application scenario, before reading the first IMEI stored in the flash, it further comprises the process of initializing the OTP region, comprising: [0060]step 1, power up, and read the flag file in the flash; [0061]step 2, if there is a flag file, read the IMEI in said flag file, if no IMEI is detected, consider the device in the production phase, and normally start up the mobile terminal; If the IMEI is detected, write it into the OTP region, and delete said flag file; [0062]step 3, if said flag file does not exist, enter into the normal IMEI validation phase of said mobile terminal. [0063]In said step one, said flag file exist in the Flash before writing said IMEI into said mobile terminal. [0064]In said step 2, the normal startup state is exclusively used in the research & development and production testing phases. [0065]In a preferred embodiment, reading the flag file stored in the flash further comprises: [0066]when said flag file does not exist, determining that said IMEI has been written into said mobile terminal, and giving a prompt. [0067]Whether said flag file exist or not is the unique condition to judge whether said mobile terminal is in the production phase or not, if said flag file does not exist, it represents that said IMEI has been written into said mobile terminal and backed up, thus completing the production process, and being in the user using phase. [0068]In a preferred embodiment, comparing said first IMEI with the backup IMEI stored in the one time programmable data region comprises: [0069]reading said backup IMEI in said one-time programmable data region; [0070]comparing said first IMEI with said backup IMEI. [0071]In a preferred embodiment, if said first IMEI and said backup IMEI are consistent, allow said mobile terminal to access to the network. [0072]In a preferred embodiment, after said mobile terminal accesses to the network, [0073]when said first IMEI is modified, automatically compare said first IMEI with the backup IMEI, if they are inconsistent, disable said mobile terminal. [0074]The embodiment of the present invention provides a mobile terminal, as shown in FIG. 2, comprising: [0075]reading unit 201, which is set to read the first international mobile equipment identity (IMEI) stored in the flash; [0076]detecting unit 202, which is set to compare said first IMEI with the backup IMEI stored in the one-time programmable data region, and said one-time programmable data area is prohibited from being modified; and [0077]disabling unit 203, which is set to, if said first IMEI and said backup IMEI are inconsistent, disable said mobile terminal. [0078]After using the abovementioned technical solution, directly back up said IMEI plaintext to the OTP region, protect the IMEI by dynamically comparing the value of the IMEI standardly stored in the flash with the value of the backup IMEI, so that the IMEI will not be arbitrarily rewritten, meanwhile, this function is integrated into the terminal, to achieve the dynamic self-protection of the terminal. [0079]In a preferred embodiment, said mobile terminal further comprises a writing unit, wherein: [0080]said writing unit is configured to, when powering up, read the flag file stored in the flash; if the initial IMEI is detected in said flag file, write said initial IMEI into said one-time programmable data region as said backup IMEI, delete said flag file; if the initial IMEI is not detected, determine that said mobile terminal is in the production phase. [0081]In a preferred embodiment, said mobile terminal further comprises a prompting module, wherein: [0082]said prompting module is set to, when the flag file does not exist, determine that said IMEI has been written to said mobile terminal, and give a prompt. [0083]In a preferred embodiment, said detecting unit 202 comprises: [0084]a one-time programmable read data region module, which is set to read the backup IMEI in said one-time programmable data region; and [0085]a comparing module, which is set to compare said first IMEI with said backup IMEI. [0086]In a preferred embodiment, said mobile terminal further comprises an enabling unit, wherein: [0087]said enabling unit is set to, if said first IMEI and said backup IMEI are consistent, allow said mobile terminal to access to the network. [0088]In a preferred embodiment, said mobile terminal further comprises a flash detecting unit, wherein: [0089]said flash detecting unit is set to, when said first IMEI is modified, automatically compare said first IMEI with said backup IMEI, if they are inconsistent, disable said mobile terminal. [0090]After using this scheme, the advantages are: backing up the IMEI to the OTP region, when modifying said IMEI or powering up said mobile terminal, automatically detecting whether the first IMEI currently stored in the flash and the backup IMEI are consistent or not, if they are consistent, booting the host normally, if they are inconsistent, disabling the host, so as to dynamically detect the legitimacy of the IMEI of said mobile terminal; integrating this function into the terminal can effectively protect the IMEI number of said mobile terminal from being arbitrarily modified, so as to ensure the legitimate interests of the users and operators. [0091]The above description is the preferred embodiments of the present document, and it should be noted that for a person of ordinary skill in the art, any method for protecting the IMEI backed up in the non-erasable region can also make a number of improvements and modifications without departing from the principles of the present document, and these improvements and modifications should be considered within the protection scope of the present document. [0092]Those ordinarily skilled in the art can understand that all or some of steps of the abovementioned method may be completed by the programs instructing the relevant hardware, and said programs may be stored in a computer-readable storage medium, such as read only memory, magnetic or optical disk. Alternatively, all or some of the steps of the abovementioned embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/unit in the abovementioned embodiments can be realized in the form of hardware or software function module. The present document is not limited to any specific form of hardware and software combinations. [0093]The above description is only preferred embodiments of the present document, and is not intended to limit the protection scope of the present document. According to the inventive content of the present document, there may be also a variety of other embodiments, and without departing from the spirit and essence of the document, those skilled in the field can make all kinds of corresponding changes and modifications in accordance with the present document, while within the spirit and principles of the present document, all changes, equivalent replacements and improvements should be included within the protection scope of the present document. INDUSTRIAL APPLICABILITY [0094]Compared with the relevant technology, the embodiment of the present document directly backs up the IMEI plaintext to the OTP region of the mobile terminal, and dynamically compares the value of the IMEI stored in the flash with the value of the backup IMEI, so as to conveniently detect the legitimacy of the IMEI of the mobile terminal, effectively protect the IMEI number of the mobile terminal from being modified arbitrarily, and ensure the legitimate interests of the users and operators.(String), 相关申请的交叉引用 [0001] 本申请为PCT申请号PCT/CN2013/077970的美国国家阶段申请,PCT申请日为2013年6月26日,要求2012年8月20日提交的中国专利申请201210295759.8的优先权,其公开内容为 特此通过引用并入。 技术领域 [0002] 本发明涉及移动终端技术,尤其涉及一种移动终端检测方法及移动终端。 背景 [0003] 国际移动设备识别码 (IMEI) 由 15 位数字组成,通常称为序列号,存储在 EEPROM 中。 每个移动终端对应一个唯一的 IMEI,在出厂组装和交付时都会写入一个唯一的 IMEI。 从生产到发货,IMEI都会被制造商记录下来,也是该移动终端在制造商端的存档号和ID号。 [0004] IMEI由TAO+FAC+SNR+SP组成。 [0005] 1、前六位数字(TAO)为型式批准号,一般代表型号, [0006] 2、后面的两位数(FAC)是最终的组装编号,通常代表产地, [0007] 3、后面6位数字(SNR)是一个字符串数字,一般代表生产序列号, [0008] 4、最后一位(SP)通常为0,代表校验码。 [0009] 在待机界面输入*#06#可以查看IMEI。 在GSM/UMTS/LTE网络中只能使用具有IMEI的移动终端,运营商可以根据IMEI识别设备类型,然后提供相关服务,用户也可以利用IMEI判断是否 购买的移动终端是否为原装产品。 [0010] 由于所述移动终端的IMEI是写在可反复读写的Flash中的,因此比较容易被计算机程序修改以欺骗网络获得非法状态或功能,因此IMEI保护将包含在 运营商的要求。 [0011] 针对IMEI保护提出的相关设计思路是,在主机每次开机时,利用IMEI和设备参数,通过相关算法生成校验值,并存储在一次性可编程(OTP)区域中 ,该校验值将进行比较,如果不同则限制使用; 或者使用外部设备,所述外部设备通过一定的加密算法将IMEI加密形成密文,与解密密钥一起存储在所述OTP区域中,通过解密密钥对密文进行解密后访问明文数据 ,然后连接通讯终端进行验证。 [0012] 上述技术存在以下问题:保护IMEI的方式过于复杂,增加了实施难度,或者需要使用外部设备保护IMEI,导致移动终端使用不方便。 概括 [0013] 为解决上述技术问题,本发明实施例提供了一种移动终端检测方法及移动终端,用以解决现有技术中保护IMEI的方法过于复杂的缺点。 [0014] 为解决上述技术问题,本发明实施例提供了一种移动终端检测方法,该方法包括: [0015] 读取存储在闪存中的第一国际移动终端设备标识(IMEI); [0016] 将所述第一IMEI与存储在防止被修改的一次性可编程数据区域中的备份IMEI进行比较; [0017] 如果所述第一IMEI和所述备份IMEI不一致,则禁用所述移动终端。 [0018] 优选地,在读取所述闪存中存储的所述第一IMEI之前,该方法还包括: [0019] 上电,并读取存储在所述闪存中的标志文件; [0020]当所述标志文件存在时,若检测到所述标志文件中存在初始IMEI,则将所述初始IMEI写入所述一次性可编程数据区作为备份IMEI,并删除所述标志文件。 [0021] 优选地,当所述标志文件存在时,如果在所述标志文件中未检测到初始IMEI,则确定所述移动终端处于生产阶段。 [0022] 优选地,在读取存储在所述flash中的所述标志文件之后,还包括: [0023] 当所述标志文件不存在时,确定所述IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并进行提示。 [0024] 优选地,在将所述第一IMEI与所述一次性可编程数据区域中存储的所述备份IMEI进行比较之后,还包括: [0025] 如果所述第一IMEI和所述备份IMEI一致,则允许所述移动终端接入网络。 [0026] 优选地,所述移动终端接入所述网络后,还包括: [0027] 当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0028] 为解决上述技术问题,本发明实施例还提供了一种移动终端,包括: [0029] 读取单元,用于读取闪存中存储的第一国际移动终端设备识别码(IMEI); [0030] 检查单元,用于将所述第一IMEI与存储在一次性可编程数据区域中的备份IMEI进行比较,防止所述一次性可编程数据区域被修改。 和 [0031] 禁用单元,用于当所述第一IMEI和所述备用IMEI不一致时,禁用所述移动终端。 [0032] 优选地,所述移动终端还包括写入单元,其中: [0033] 所述写入单元设置为在上电时读取存储在所述flash中的标志文件。 当所述标志文件存在时,若在所述标志文件中检测到初始IMEI,则将所述初始IMEI写入所述一次性可编程数据区作为所述备份IMEI,并删除所述标志文件。 [0034] 优选地,所述写入单元还设置为,当所述标志文件存在时,如果在所述标志文件中没有检测到初始IMEI,则确定所述移动终端处于生产阶段。 [0035] 优选地,所述移动终端还包括提示模块,其中: [0036] 所述提示模块,用于当所述标志文件不存在时,确定所述IMEI已写入所述移动终端,并进行提示。 [0037] 优选地,所述移动终端还包括使能单元,其中: [0038] 检查单元包括: [0039] 一次性可编程数据区读取模块,用于读取所述一次性可编程数据区中的备份IMEI; [0040] 比较模块,用于将所述第一IMEI与所述备用IMEI进行比较; [0041] 所述启用单元设置为:若所述第一IMEI和所述备用IMEI一致,则允许所述移动终端接入网络。 [0042] 优选地,上述移动终端还包括闪光检测单元,其中: [0043] 所述闪现检测单元设置为,当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0044] 本发明上述技术方案的有益效果是:禁止OTP区域修改其中的数据,从而不修改其中的备份IMEI,有效保护了所述手机的IMEI不被任意修改。 ,并确保用户和经营者的合法利益。 附图的简要说明 [0045] 图1为本发明实施例提供的一种移动终端检测方法示意图; [0046]图2为本发明实施例提供的一种移动终端的结构示意图。 本发明的优选实施方案 [0047] 下面结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本申请实施例中的实施例和特征可以任意组合。 [0048] 本发明实施例直接将IMEI明文备份到移动终端的一次性可编程数据(OTP)区域,并动态比较标准存储在flash中的IMEI值与备份IMEI值。 [0049] 本发明实施例提供的一种移动终端检测方法,如图1所示,包括以下步骤。 [0050] 在步骤 101 ,读取存储在闪存中的第一个国际移动设备标识(IMEI); [0051] 在步骤 102 ,将所述第一IMEI与所述一次性可编程(OTP)数据区中存储的备份IMEI进行比较,禁止修改所述一次性可编程数据区; [0052] 在步骤 103 ,如果所述第一IMEI和所述备份IMEI不一致,则禁用所述移动终端。 [0053] 应用所提供的技术方案,OTP区域内的数据被禁止修改,从而无法修改其中的备份IMEI,有效保护了移动终端的IMEI不被任意修改,保障了用户的合法权益。 用户和运营商。 [0054] 该移动终端只有接入网络后才能享受运营商提供的网络服务。 [0055] 在一个优选实施例中,在读取闪存中存储的第一IMEI之前,还包括: [0056] 上电,读取存储在flash中的flag文件; [0057] 当所述标志文件存在时,读取所述标志文件中的初始IMEI,若检测到所述初始IMEI,将所述初始IMEI写入所述一次性可编程数据区作为所述备份IMEI,并删除所述标志文件。 [0058] 如果在所述标志文件中未检测到原始IMEI,则确定所述移动终端处于生产阶段。 [0059] 在一种应用场景中,在读取存储在flash中的第一个IMEI之前,还包括初始化OTP区域的过程,包括: [0060] step 1,上电,读取flash中的flag文件; [0061] 步骤2,如果有标志文件,则读取该标志文件中的IMEI,如果没有检测到IMEI,则认为设备处于生产阶段,正常启动移动终端。 如果检测到IMEI,则将其写入OTP区域,并删除该标志文件; [0062] 步骤3,如果所述标志文件不存在,则进入所述移动终端的正常IMEI验证阶段。 [0063] 所述步骤一中,在将所述IMEI写入所述移动终端之前,所述标志文件存在于Flash中。 [0064] 所述步骤2中,正常启动状态专门用于研发和生产测试阶段。 [0065] 在一个优选实施例中,读取闪存中存储的标志文件还包括: [0066] 当所述标志文件不存在时,确定所述IMEI已写入所述移动终端,并进行提示。 [0067] 所述标志文件是否存在是判断所述移动终端是否处于生产阶段的唯一条件,如果所述标志文件不存在,则表示所述IMEI已写入所述移动终端并备份,因此 完成生产过程,进入用户使用阶段。 [0068] 在优选实施例中,将所述第一IMEI与存储在一次性可编程数据区域中的备份IMEI进行比较包括: [0069] 读取所述一次性可编程数据区域中的所述备份IMEI; [0070] 将所述第一IMEI与所述备用IMEI进行比较。 [0071]在一个优选实施例中,如果所述第一IMEI和所述备用IMEI一致,则允许所述移动终端接入网络。 [0072] 在一个优选实施例中,所述移动终端接入网络后, [0073] 当所述第一IMEI被修改时,自动将所述第一IMEI与备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0074] 本发明实施例提供一种移动终端,如图2所示,包括: [0075] 阅读单元 201 ,设置为读取存储在闪存中的第一个国际移动设备标识(IMEI); [0076] 检测单元 202 ,设置为将所述第一IMEI与存储在所述一次性可编程数据区中的备份IMEI进行比较,并禁止修改所述一次性可编程数据区; 和 [0077] 禁用单元 203 ,设置为如果所述第一IMEI和所述备用IMEI不一致,则禁用所述移动终端。 [0078] 使用上述技术方案后,直接将所述IMEI明文备份到OTP区域,通过动态比较标准存储在flash中的IMEI值与备份IMEI值来保护IMEI,使IMEI不会被任意篡改 重写,同时将该功能集成到终端中,实现终端的动态自我保护。 [0079] 在一个优选实施例中,所述移动终端还包括写入单元,其中: [0080] 所述写入单元,用于在上电时读取闪存中存储的标志文件; 如果在所述标志文件中检测到初始IMEI,将所述初始IMEI写入所述一次性可编程数据区作为所述备份IMEI,删除所述标志文件; 如果未检测到初始IMEI,则确定所述移动终端处于生产阶段。 [0081] 在一个优选实施例中,所述移动终端还包括提示模块,其中: [0082] 所述提示模块设置为当标志文件不存在时,确定所述IMEI已写入所述移动终端,并进行提示。 [0083] 在一个优选实施例中,所述检测单元 202 包含: [0084] 一次性可编程读取数据区模块,用于读取所述一次性可编程数据区中的备份IMEI; 和 [0085] 比较模块,用于将所述第一IMEI与所述备用IMEI进行比较。 [0086] 在一个优选实施例中,所述移动终端还包括使能单元,其中: [0087] 所述启动单元设置为,如果所述第一IMEI和所述备用IMEI一致,则允许所述移动终端接入网络。 [0088] 在一个优选实施例中,所述移动终端还包括闪光检测单元,其中: [0089] 所述闪现检测单元设置为,当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0090] 使用该方案后的优点是:将IMEI备份到OTP区域,在修改IMEI或给移动终端上电时,自动检测当前存储在flash中的第一个IMEI与备份的IMEI是否一致,如果 一致,正常启动主机,如果不一致,关闭主机,动态检测所述移动终端IMEI的合法性。 将该功能集成到终端中,可以有效保护该移动终端的IMEI号不被任意修改,保障用户和运营商的合法权益。 [0091] 以上所述为本文档的较佳实施例,需要说明的是,对于本领域的普通技术人员来说,任何保护不可擦除区域备份的IMEI的方法都可以做很多改进和改进。 在不脱离本文件原则的情况下进行修改,这些改进和修改应视为在本文件的保护范围之内。 [0092]本领域普通技术人员可以理解,上述方法的全部或部分步骤可以通过程序指令相关硬件来完成,所述程序可以存储在计算机可读存储介质中,例如只读存储器、磁 或光盘。 或者,上述实施例的全部或部分步骤也可以通过一个或多个集成电路来实现。 因此,上述实施例中的各个模块/单元可以采用硬件或软件功能模块的形式来实现。 本文档不限于任何特定形式的硬件和软件组合。 [0093] 以上所述,仅为本发明的较佳实施例而已,并不用于限定本发明的保护范围。 根据本发明的发明内容,还可以有多种其他的实施例,在不脱离本发明的精神和实质的前提下,本领域技术人员可以根据本发明进行各种相应的改动和变型。 本文件,在本文件的精神和原则之内,一切改动、等同替换、改进等,均应包含在本文件的保护范围之内。 工业适用性 [0094] 与相关技术相比,本文档实施例直接将IMEI明文备份到移动终端的OTP区域,并动态比较存储在flash中的IMEI值与备份IMEI值,从而 方便检测移动终端IMEI的合法性,有效保护移动终端IMEI号不被任意修改,保障用户和运营商的合法权益。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2013270195A1(String), AU2013270195B2(String), CN102831079A(String), CN102831079B(String), EP2829978A1(String), EP2829978A4(String), EP2829978B1(String), RU2014141581A(String), RU2601841C2(String), US20150067780A1(String), US9292680B2(String), WO2013178117A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2013270195A1(String), AU2013270195B2(String), CN102831079A(String), CN102831079B(String), EP2829978A1(String), EP2829978A4(String), EP2829978B1(String), RU2014141581A(String), RU2601841C2(String), US20150067780A1(String), US9292680B2(String), WO2013178117A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9292680B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2013270195A1(String), AU2013270195B2(String), CN102831079A(String), CN102831079B(String), EP2829978A1(String), EP2829978A4(String), EP2829978B1(String), RU2014141581A(String), RU2601841C2(String), US20150067780A1(String), US9292680B2(String), WO2013178117A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), AU2013270195A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.567 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.567 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), AU2013270195B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), CN102831079A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), CN102831079B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), EP2829978A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), EP2829978A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), EP2829978B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), RU2014141581A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), RU2601841C2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), US20150067780A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), US9292680B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270684(Integer), WO2013178117A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9292680B2(String), US9292680B2(String), 1458576000(Integer), 270684(Integer), 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.687 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.688 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185006(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.690 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.690 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185006(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.700 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.700 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185006(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185006(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.713 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.715 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.716 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.717 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.717 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.718 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.725 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.726 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.726 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.736 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.737 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7720717B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal device, mobile terminal method, mobile terminal program, and electronic money server(String), 移动终端装置、移动终端方法、移动终端程序以及电子货币服务器(String), US7720717B2(String), A mobile terminal device has an information processing unit that processes electronic money information and a storage unit that stores the electronic money information. A receiving unit receives from an electronic money server an electronic money identification (ID), a mobile terminal identification (ID) identifying the mobile terminal device, and a money information processing program for enabling the information processing unit to execute processing of the money information stored in the storage unit. An installation unit installs into the storage unit the money information processing program and the IDs received by the receiving unit. A sending unit sends to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information being sent to the electronic server before the receiving unit receives the money information processing and the IDs.(String), 移动终端设备具有处理电子货币信息的信息处理单元和存储电子货币信息的存储单元。 接收部从电子货币服务器接收电子货币识别码(ID)、识别移动终端装置的移动终端识别码(ID)、以及用于使信息处理部执行所存储的货币信息的处理的货币信息处理程序。 在存储单元中。 安装单元将货币信息处理程序和接收单元接收到的ID安装到存储单元中。 发送单元向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息,该必要信息在接收单元接收货币信息处理和ID之前被发送至电子服务器。(String), US10/547977(String), 1078416000(Integer), US7720717B2(String), 1274112000(Integer), 1274112000(Integer), 美国(String), 4(Integer), JP(String), 13(Integer), 27(Integer), EP0950968A1 | EP1221669A1 | JP2000112719A | JP2000259148A | JP2001291032A | JP2002004886A | JP2002042216A | JP2002073973A | JP2002135424A | JP2002329053A | JP2002352173A | JP2003016041A | JP2003022483A | JP2004102698A | US20010034725A1 | US20020049662A1 | US20020052838A1 | US20020064074A1 | US20060136548A1 | US5796832A | US6198915B1 | US6282656B1 | US6321078B1 | US6434403B1 | WO1996025828A1 | WO1997045814A1 | WO2002048869A1(String), 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185007(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\37893f4ad47e43e1a19af665a1b1cab6.png(String), 185007(Integer), 37893f4ad47e43e1a19af665a1b1cab6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal device, mobile terminal method, mobile terminal program, and electronic money server(String), 移动终端装置、移动终端方法、移动终端程序以及电子货币服务器(String), US7720717B2(String), A mobile terminal device has an information processing unit that processes electronic money information and a storage unit that stores the electronic money information. A receiving unit receives from an electronic money server an electronic money identification (ID), a mobile terminal identification (ID) identifying the mobile terminal device, and a money information processing program for enabling the information processing unit to execute processing of the money information stored in the storage unit. An installation unit installs into the storage unit the money information processing program and the IDs received by the receiving unit. A sending unit sends to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information being sent to the electronic server before the receiving unit receives the money information processing and the IDs.(String), 移动终端设备具有处理电子货币信息的信息处理单元和存储电子货币信息的存储单元。 接收部从电子货币服务器接收电子货币识别码(ID)、识别移动终端装置的移动终端识别码(ID)、以及用于使信息处理部执行所存储的货币信息的处理的货币信息处理程序。 在存储单元中。 安装单元将货币信息处理程序和接收单元接收到的ID安装到存储单元中。 发送单元向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息,该必要信息在接收单元接收货币信息处理和ID之前被发送至电子服务器。(String), US10/547977(String), 1078416000(Integer), US7720717B2(String), 1274112000(Integer), 1274112000(Integer), 美国(String), 2(Integer), 4(Integer), JP(String), 13(Integer), 27(Integer), EP0950968A1 | EP1221669A1 | JP2000112719A | JP2000259148A | JP2001291032A | JP2002004886A | JP2002042216A | JP2002073973A | JP2002135424A | JP2002329053A | JP2002352173A | JP2003016041A | JP2003022483A | JP2004102698A | US20010034725A1 | US20020049662A1 | US20020052838A1 | US20020064074A1 | US20060136548A1 | US5796832A | US6198915B1 | US6282656B1 | US6321078B1 | US6434403B1 | WO1996025828A1 | WO1997045814A1 | WO2002048869A1(String), \20230420\37893f4ad47e43e1a19af665a1b1cab6.png(String), 25(Integer), 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 1. A mobile terminal device having an Internet access function for access to the Internet to communicate the mobile terminal device with an electronic money server providing electronic money service, the mobile terminal device comprising:information processing means for processing electronic information including money information;storing means for storing the electronic information including the money information;receiving means for receiving from the electronic money server secret information and an electronic money identification (ID);means for downloading from the electronic money server a money information processing program using the received secret information and electronic money ID for enabling the information processing means to execute processing of the money information stored in the storing means;installing means for installing into the storing means the money information processing program downloaded from the electronic money server and the electronic money ID and the secret information received by the receiving means while the mobile terminal device communicates only with the electronic money server;sending means for sending to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information corresponding to the electronic money ID and being sent to the electronic server by the sending means before the money information processing program is downloaded from the electronic money server and the receiving means receives the electronic money ID and the secret information from the electronic money server; anda log data storing unit for storing a history of electronic information processed by the information processing means;wherein while the mobile terminal device communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing means to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stared by the storing means by using the secret information installed in the storing means, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing means and stored in the log data storing unit;wherein the installing means generates the log data storing unit in the storing means when the installing means installs into the storing means the money information processing program, the electronic money ID, and the secret information;wherein the information processing means and the storing means comprise at least one IC chip;wherein the necessary information sent by the sending means to the electronic money server comprises information identifying the IC chip; andwherein the receiving means receives the electronic money ID from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 1.移动终端设备有互联网访问功能,用于访问互联网以将移动终端设备与提供电子货币服务的电子货币服务器进行通信,该移动终端设备包括:用于处理包括货币信息在内的电子信息的信息处理装置;用于存储包括货币信息的电子信息的存储装置;用于从电子货币服务器接收秘密信息和电子货币标识(ID)的接收装置;用于从电子货币服务器下载货币信息处理程序的装置,该货币信息处理程序使用接收到的秘密信息和电子货币ID,使得信息处理装置能够执行存储在存储装置中的货币信息的处理;在移动终端装置仅与电子货币服务器进行通信的状态下,将从电子货币服务器下载的货币信息处理程序和接收装置接收到的电子货币ID及秘密信息安装到存储装置的安装单元。发送装置,用于向电子货币服务器发送使电子货币服务器能够提供电子货币服务所必需的信息,该必要信息对应于电子货币ID并且在货币信息处理程序被执行之前由发送装置发送至电子服务器。从电子货币服务器下载,接收装置从电子货币服务器接收电子货币ID和秘密信息;和日志数据存储单元,用于存储由信息处理装置处理的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理装置执行用于接收来自电子货币服务器或电子终端设备的信息的金额信息接收功能。通过使用安装在存储装置中的秘密信息,对应于与由存储装置启动的货币信息相对应的货币量的变化,执行货币信息处理功能,用于根据接收到的相应信息改变货币量对于金额的变化,执行历史信息记录功能,用于记录由信息处理装置处理并存储在日志数据存储单元中的电子信息的历史;其中,当安装装置将货币信息处理程序、电子货币ID和秘密信息安装到存储装置中时,安装装置在存储装置中生成日志数据存储单元;其中,信息处理装置和存储装置包括至少一个IC芯片;其中,发送装置向电子货币服务器发送的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,接收装置从电子货币服务器接收电子货币ID。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 2. A mobile terminal device according to claim 1; wherein the secret information comprises identification information that enables the mobile terminal device to be identified by the electronic terminal device or the electronic money server.(String), 2.如权利要求1所述的移动终端设备;其中秘密信息包括使移动终端设备能够被电子终端设备或电子货币服务器识别的标识信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 3. A mobile terminal device according to claim 1; further comprising display means for displaying the electronic money ID received by the receiving means and installed by the installing means.(String), 3.根据权利要求1所述的移动终端设备;还包括显示装置,用于显示由接收装置接收并由安装装置安装的电子货币ID。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 4. A mobile terminal device according to claim 2; further comprising display means for displaying the electronic money ID received by the receiving means and installed by the installing means.(String), 4.如权利要求2所述的移动终端设备;还包括显示装置,用于显示由接收装置接收并由安装装置安装的电子货币ID。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 5. A mobile terminal device according to claim 3; wherein the money information processing program enables the information processing means to send to the electronic terminal device the electronic money ID in response to receipt of the information corresponding to a change in the amount of money from the electronic terminal device when the information processing means performs the money-amount information receiving function.(String), 5.根据权利要求3所述的移动终端设备;其中货币信息处理程序使信息处理装置能够响应于在信息处理装置执行货币时从电子终端设备接收到对应于货币量的变化的信息而向电子终端设备发送电子货币ID-金额信息接收功能。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 6. A mobile terminal device according to claim 4; wherein the money information processing program enables the information processing means to send to the electronic terminal device the electronic money ID in response to receipt of the information corresponding to a change in the amount of money from the electronic terminal device when the information processing means performs the money-amount information receiving function.(String), 6.如权利要求4所述的移动终端设备;其中货币信息处理程序使信息处理装置能够响应于在信息处理装置执行货币时从电子终端设备接收到对应于货币量的变化的信息而向电子终端设备发送电子货币ID-金额信息接收功能。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 7. An electronic money server for providing electronic money service using the mobile terminal device according to claim 1, the electronic money server comprising:connecting means for enabling Internet connection of the electronic money server to the mobile terminal device via the Internet access function of the mobile terminal device; andsending means for sending the secret information, the money information processing program, and the electronic money ID to the receiving means of the mobile terminal device when the electronic money server and the mobile terminal device are connected via the Internet.(String), 7.一种电子货币服务器,使用权利要求1所述的移动终端装置提供电子货币服务,该电子货币服务器包括:用于通过移动终端设备的互联网访问功能实现电子货币服务器与移动终端设备的互联网连接的连接装置;和发送装置,当电子货币服务器和移动终端设备通过因特网连接时,将秘密信息、货币信息处理程序和电子货币ID发送到移动终端设备的接收装置。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 8. A method executed by a computer for performing communication between a mobile terminal device according to claim 1 and an electronic money server for providing electronic money service using the mobile terminal device, comprising:enabling Internet connection of the electronic money server to the mobile terminal device via the Internet access function of the mobile terminal device; andsending the secret information, the money information processing program, and the electronic money ID to the receiving means of the mobile terminal device when the electronic money server and the mobile terminal device are connected via the Internet.(String), 8.一种由计算机执行的方法,用于在根据权利要求1所述的移动终端设备和使用该移动终端设备提供电子货币服务的电子货币服务器之间进行通信,包括:通过移动终端设备的互联网接入功能,使电子货币服务器能够与移动终端设备进行互联网连接;和当电子货币服务器和移动终端设备通过因特网连接时,将秘密信息、货币信息处理程序和电子货币ID发送到移动终端设备的接收装置。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 9. A mobile terminal device according to claim 1; wherein the mobile terminal device comprises a cellular mobile telephone having mobile phone functions.(String), 9.根据权利要求1所述的移动终端设备;其中移动终端设备包括具有手机功能的蜂窝移动电话。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 10. A mobile terminal device according to claim 1; wherein the mobile terminal device comprises one of a wireless communications device, a wirelessly-equipped personal digital assistant (PDA), and a portable computer.(String), 10.根据权利要求1所述的移动终端设备;其中移动终端设备包括无线通信设备、配备无线的个人数字助理(PDA)和便携式计算机之一。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 11. A mobile terminal device according to claim 1; wherein the sending means includes means for sending to the electronic money server user identification information for identifying a user of the mobile terminal device.(String), 11.根据权利要求1所述的移动终端设备;其中发送装置包括用于向电子货币服务器发送用于识别移动终端设备的用户的用户识别信息的装置。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 12. A mobile terminal device according to claim 11; wherein the user identification information comprises the information identifying the IC chip.(String), 12.根据权利要求11所述的移动终端设备;其中用户识别信息包括识别IC芯片的信息。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 13. A mobile terminal device according to claim 11; wherein the user identification information comprises the electronic money ID.(String), 13.根据权利要求11所述的移动终端设备;其中用户识别信息包括电子货币ID。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 14. A mobile terminal device according to claim 1; wherein the installing means installs the secret information, money information processing program, and electronic money ID using the secret information.(String), 14.根据权利要求1所述的移动终端设备;其中安装装置安装秘密信息、货币信息处理程序和使用秘密信息的电子货币ID。15、一种电脑执行的移动端方法有用于处理电子信息的信息处理设备,用于存储电子信息的存储设备,以及用于访问因特网以将移动终端设备与提供电子货币服务的电子货币服务器进行通信的因特网访问功能,该移动终端方法包括:向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息;在向电子货币服务器发送必要信息后,从电子货币服务器接收保密信息和与必要信息对应的电子货币标识(ID);使用接收到的秘密信息和电子货币ID,从电子货币服务器下载货币信息处理程序,以使信息处理装置能够执行存储在存储装置中的货币信息的处理;在移动终端设备与电子货币服务器通信的同时将从电子货币服务器下载的货币信息处理程序和从电子货币服务器接收的电子货币ID和秘密信息安装到存储装置中;和在存储装置中生成日志数据存储单元,用于存储信息处理处理过的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理设备执行用于接收来自电子货币服务器或电子终端设备的信息的金额信息接收功能。通过使用存储设备中安装的秘密信息,对应于存储设备存储的与货币信息相对应的货币数量的变化,执行货币信息处理功能,用于根据接收到的相应信息改变货币数量对于金额的变化,执行历史信息记录功能,用于记录由信息处理设备处理并存储在日志数据存储单元中的电子信息的历史;其中,当货币信息处理程序、电子货币ID和秘密信息被安装到存储设备中时,在存储设备中生成日志数据存储单元;其中,信息处理装置和存储装置包括至少一个IC芯片;其中,发送给电子货币服务器的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,从电子货币服务器接收电子货币ID。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 15. A mobile terminal method executed by a computer having an information processing device for processing electronic information, a storage device for storing the electronic information, and an Internet access function for access to the Internet to communicate a mobile terminal device with an electronic money server providing electronic money service, the mobile terminal method comprising:sending to the electronic money server information necessary for enabling the electronic money server to provide electronic money service;receiving from the electronic money server, after the necessary information is sent to the electronic money server, secret information and an electronic money identification (ID) corresponding to the necessary information;downloading from the electronic money server a money information processing program using the received secret information and electronic money ID for enabling the information processing device to execute processing of money information stored in the storing device;installing into the storage device the money information processing program downloaded from the electronic money server and the electronic money ID and the secret information received from the electronic money server while the mobile terminal device communicates with the electronic money server; andgenerating a log data storing unit in the storage device for storing a history of electronic information processed by the information processing;wherein while the mobile terminal device communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing device to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stored by the storage device by using the secret information installed in the storage device, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing device and stored in the log data storing unit;wherein the log data storing unit is generated in the storage device when the money information processing program, the electronic money ID, and the secret information are installed into the storage device;wherein the information processing device and the storage device comprise at least one IC chip;wherein the necessary information sent to the electronic money server comprises information identifying the IC chip; andwherein the electronic money ID is received from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 16.计算机程序产品包含一种计算机可读介质,具有用于使用计算机执行移动终端方法的指令,所述计算机具有用于处理电子信息的信息处理装置、用于存储电子信息的存储装置和用于访问因特网以通信的因特网访问功能具有提供电子货币服务的电子货币服务器的移动终端设备,指令使计算机:向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息;在向电子货币服务器发送必要信息后,从电子货币服务器接收保密信息和与必要信息对应的电子货币标识(ID);使用接收到的秘密信息和电子货币(ID)从电子货币服务器下载货币信息处理程序,以使信息处理装置能够执行存储在存储装置中的货币信息的处理;在移动终端装置仅与电子货币服务器通信的状态下,将从电子货币服务器下载的货币信息处理程序和从电子货币服务器接收的电子货币ID和秘密信息安装到存储装置中。和在存储装置中生成日志数据存储单元,用于存储信息处理装置处理过的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理设备执行用于接收来自电子货币服务器或电子终端设备的信息的金额信息接收功能。通过使用存储设备中安装的秘密信息,对应于存储设备存储的与货币信息相对应的货币数量的变化,执行货币信息处理功能,用于根据接收到的相应信息改变货币数量对于金额的变化,执行历史信息记录功能,用于记录由信息处理设备处理并存储在日志数据存储单元中的电子信息的历史;其中,当货币信息处理程序、电子货币ID和秘密信息被安装到存储设备中时,在存储设备中生成日志数据存储单元;其中,信息处理装置和存储装置包括至少一个IC芯片;其中,发送给电子货币服务器的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,从电子货币服务器接收电子货币ID。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 16. A computer program product including a computer readable medium having instructions for causing the execution of a mobile terminal method using a computer having an information processing device for processing electronic information, a storage device for storing the electronic information, and an Internet access function for access to the Internet to communicate a mobile terminal device with an electronic money server providing electronic money service, the instructions causing the computer to:send to the electronic money server information necessary for enabling the electronic money server to provide electronic money service;receive from the electronic money server, after the necessary information is sent to the electronic money server, secret information and an electronic money identification (ID) corresponding to the necessary information;download from the electronic money server a money information processing program using the received secret information and electronic money (ID) for enabling the information processing device to execute processing of money information stored in the storing device;install into the storage device the money information processing program downloaded from the electronic money server and the electronic money ID and the secret information received from the electronic money server while the mobile terminal device communicates only with the electronic money server; andgenerate a log data storing unit in the storage device for storing a history of electronic information processed by the information processing device;wherein while the mobile terminal device communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing device to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stored by the storage device by using the secret information installed in the storage device, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing device and stored in the log data storing unit;wherein the log data storing unit is generated in the storage device when the money information processing program, the electronic money ID, and the secret information are installed into the storage device;wherein the information processing device and the storage device comprise at least one IC chip;wherein the necessary information sent to the electronic money server comprises information identifying the IC chip; andwherein the electronic money ID is received from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 17.一种通过因特网连接与提供电子货币服务的电子货币服务器进行通信的移动终端设备,该移动终端设备包括:处理电子货币信息的信息处理单元;存储电子货币信息的存储单元;接收单元从电子货币服务器接收电子货币标识(ID)和标识移动终端设备的移动终端标识(ID);下载单元使用电子货币ID和移动终端ID从电子货币服务器下载货币信息处理程序,使得信息处理单元能够执行存储在存储单元中的货币信息的处理;安装部,在便携终端装置仅与电子货币服务器进行通信的状态下,将下载部下载的货币信息处理程序和接收部接收到的电子货币ID以及便携终端ID安装到存储部。发送单元向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息,该必要信息在下载单元下载货币信息处理程序之前被发送至电子服务器并且接收单元接收电子货币ID和移动终端ID;和日志数据存储单元,用于存储由信息处理单元处理的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理单元执行用于从电子货币服务器或电子终端设备接收信息的金额信息接收功能通过使用安装在存储单元中的移动终端ID,对应于存储单元存储的货币信息对应的货币数量的变化,以执行用于根据接收到的信息改变货币数量的货币信息处理功能对应于金额的变化,执行历史信息记录功能,用于记录信息处理单元处理并存储在日志数据存储单元中的电子信息的历史;其中,当安装单元将货币信息处理程序、电子货币ID和移动终端ID安装到存储单元时,安装单元在存储单元中生成日志数据存储单元;其中,信息单元和存储单元包括至少一IC芯片。其中,发送单元向电子货币服务器发送的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,接收单元从电子货币服务器接收电子货币ID。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 17. A mobile terminal device for communication via an Internet connection to an electronic money server providing electronic money service, the mobile terminal device comprising:an information processing unit that processes electronic money information;a storage unit that stores the electronic money information;a receiving unit that receives from the electronic money server an electronic money identification (ID) and a mobile terminal identification (ID) identifying the mobile terminal device;a downloading unit that downloads from the electronic money server a money information processing program using the electronic money ID and the mobile terminal ID for enabling the information processing unit to execute processing of the money information stored in the storage unit;an installation unit that installs into the storage unit the money information processing program downloaded by the downloading unit and the electronic money ID and the mobile terminal ID received by the receiving unit while the mobile terminal device communicates only with the electronic money server;a sending unit that sends to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information being sent to the electronic server before the downloading unit downloads the money information processing program and the receiving unit receives electronic money ID and the mobile terminal ID; anda log data storing unit for storing a history of electronic information processed by the information processing unit;wherein while the mobile terminal device Communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing unit to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stored by the storage unit by using the mobile terminal ID installed in the storage unit, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing unit and stored in the log data storing unit;wherein the installation unit generates the log data storing unit in the storage unit when the installation unit installs into the storage unit the money information processing program, the electronic money ID, and the mobile terminal ID;wherein the information unit and the storage unit comprise at least one IC chip;wherein the necessary information sent by the sending unit to the electronic money server comprises information identifying the IC chip; andwherein the receiving unit receives the electronic money ID from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 18.根据权利要求17所述的移动终端设备;其中移动终端设备包括具有手机功能的蜂窝移动电话。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 18. A mobile terminal device according to claim 17; wherein the mobile terminal device comprises a cellular mobile telephone having mobile phone functions.(String), 19.根据权利要求17所述的移动终端设备;其中移动终端设备包括无线通信设备、配备无线的个人数字助理(PDA)和便携式计算机之一。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 19. A mobile terminal device according to claim 17; wherein the mobile terminal device comprises one of a wireless communications device, a wirelessly-equipped personal digital assistant (PDA), and a portable computer.(String), 20.根据权利要求17所述的移动终端设备;其中信息处理单元与储存单元包括至少一IC芯片。其中,移动终端ID包括识别IC芯片的信息。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 20. A mobile terminal device according to claim 17; wherein the information processing unit and the storage unit comprise at least one IC chip; and wherein the mobile terminal ID comprises information identifying the IC chip.(String), 21.根据权利要求20所述的移动终端设备;其中发送单元向电子货币服务器发送用于识别移动终端设备的用户的用户识别信息。(String), 1(Integer), 19(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 21. A mobile terminal device according to claim 20; wherein the sending unit sends to the electronic money server user identification information for identifying a user of the mobile terminal device.(String), 22.根据权利要求21所述的移动终端设备;其中用户识别信息包括识别IC芯片的信息。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 22. A mobile terminal device according to claim 21; wherein the user identification information comprises the information identifying the IC chip.(String), 23.根据权利要求21所述的移动终端设备;其中用户识别信息包括电子货币ID。(String), 1(Integer), 21(Integer), 20(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 23. A mobile terminal device according to claim 21; wherein the user identification information comprises the electronic money ID.(String), 24.根据权利要求17所述的移动终端设备;其中安装单元使用移动终端ID安装货币信息处理程序和电子货币ID。(String), 1(Integer), 22(Integer), 20(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 24. A mobile terminal device according to claim 17; wherein the installing unit installs the money information processing program and the electronic money ID using the mobile terminal ID.(String), 25.一种电子货币服务器,用于使用根据权利要求17所述的移动终端设备提供电子货币服务,该电子货币服务器包括:使电子货币服务器能够与移动终端设备进行因特网连接的连接装置;和发送单元,在电子货币服务器与移动终端装置经由因特网连接时,将移动终端ID、货币信息处理程序、电子货币ID发送到移动终端装置的接收部。(String), 1(Integer), 23(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:54.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185007(Integer), 25. An electronic money server for providing electronic money service using the mobile terminal device according to claim 17, the electronic money server comprising:connecting means for enabling Internet connection of the electronic money server to the mobile terminal device; andsending means for sending the mobile terminal ID, the money information processing program, and the electronic money ID to the receiving unit of the mobile terminal device when the electronic money server and the mobile terminal device are connected via the Internet.(String), 1(Integer), 24(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185007(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a U.S. national stage application of copending International Application No. PCT/JP2004/002862, filed Mar. 5, 2004, claiming a priority date of Mar. 7, 2003, and published in a non-English language. TECHNICAL FIELD [0002]The present invention relates to a mobile phone device, and more particularly, to a mobile phone using electronic-money service. BACKGROUND ART [0003]In recent years, a demonstration test of a settlement system using electronic money has been successful and the electronic money is put into practical use. [0004]Currently, a retail shop uses the electronic money for settlement. Further, in order to widespread the electronic money to general users, efforts are made to develop a technology of elements and structure a business model. [0005]In addition to the retail shop, a system using the electronic money is put into practical use to adjust the fare of a train or bus. [0006]With the electronic money, an electronic-money card stores the same exchange value, that is, so-called value, as the money, and is used as an electronic wallet. [0007]The value is written to the electronic-money card by a specific terminal device (hereinafter, referred to as an electronic-money terminal). The processing for writing the value is called charge. Upon charging the value, the money corresponding to the value is collected from a user. Thus, the actual money corresponds to the value, thereby keeping the exchange value of the value for security. [0008]The settlement using the value is executed by subtracting the amount of money corresponding to the settlement from the value stored in the electronic-money card on the electronic-money terminal. [0009]The electronic-money card comprises a non-contact IC (Integrated Circuit) card or a contact IC card. [0010]The electronic-money card comprising the non-contact IC card comprises: an IC chip having a value processing function and a value storing function; and an antenna for communication with the electronic-money terminal. The antenna has a function for wireless communication with the electronic-money terminal and further has a function for generating the power for receiving the electronic waves from the electronic-money terminal and driving the IC chip. [0011]The electronic-money terminal communicates by radio waves with the IC chip via the antenna, and accesses the IC chip in the electronic-money card, thereby performing various processing for value (writing processing, subtraction, and reference to the balance, hereinafter, referred to as value processing). Mainly, using forms of the electronic-money card are as follows. (1) Charge Value [0012]First, in a shop in which an electronic-money terminal is installed, an electronic-money card is set to the electronic-money terminal, and the writing operation of a value is requested to a person in charge. In this case, the money corresponding to the value is paid. [0013]Next, the person in charge operates the electronic-money terminal to write the value of charge to the electronic-money terminal. [0014]Then, the electronic-money terminal sends a write command for adding the money corresponding to the value to the IC chip in the electronic-money card. [0015]The IC chip receives the write command and executes the command, thereby adding the money of value stored in the IC chip. [0016]As mentioned above, the value is charged to the electronic-money card. [0017]Incidentally, in an unmanned electronic-money terminal, the electronic money card is set and the money is set to the electronic-money card, thereby automatically charging the value. (2) Settle by Value [0018]First, a product or service, serving as a target of settlement, is presented to a person in charge of an electronic-money terminal. An electronic-money card is set to the electronic-money terminal installed to a shop, and a message indicating the settlement using the value is sent to the person in charge. [0019]On the contrary, the person in charge operates the electronic-money terminal to subtract the money for settlement from the value stored in the electronic-money card. [0020]Then, the electronic-money terminal sends a subtract command for subtracting the value corresponding to the money to the IC chip in the electronic-money card. [0021]The IC chip receives the subtract command and executes the command, thereby subtracting the value corresponding to the value stored in the IC chip. [0022]As mentioned above, the settlement is performed by using the value in the electronic-money card. [0023]Incidentally, in an electronic-money terminal installed to a vending machine, a user purchases a product, and the value is automatically settled. (3) Use Electronic Money on Internet [0024]With a terminal device having an Internet access function and a reader/writer for reading/writing data to/from an electronic-money card, a value is charged to the electronic-money card or a settlement is performed by a value stored in the electronic-money card. [0025]When a value is to be charged, the electronic-money card is set to the reader/writer and is accessed to a Web site for charge on the terminal device. Then, the communication is established between a server device and the electronic-money card, and the server device writes the value to the electronic-money card. The money corresponding to the written value is withdrawn from a bank account of a user, or is processed by a credit card. [0026]In the settlement using the value, similarly, the communication is established between the server device and the electronic-money card, and the value is subtracted. [0027]As mentioned above, the electronic-money card is used as a pre-paid electronic wallet and, in particular, it is advantageous for a user in the settlement of a small amount of money because the small change does not burden the user. [0028]Recently, the mobile phone is excessively spread and it is tried that the mobile phone has the same function as that of the electronic-money card. [0029]If the mobile phone has the same function as that of the electronic-money card, a user charges the value to the mobile phone or settles the money by the value stored in the mobile phone. [0030]As mentioned above, the following technology allows the mobile phone to have the function of the electronic-money card. [0031](Patent Document 1) [0032]Japanese Unexamined Patent Application Publication-No. 2002-352173 [0033]According to the invention disclosed in Patent Document 1, a specific memory for storing the value to the mobile phone is provided, and the value is charged or the money is settled by the stored value. [0034]Upon installing the same value processing function as that of the electronic-money card to the mobile phone, the install timing is a problem. [0035]Upon installing the value processing function to the mobile phone, various information on the security must be installed. [0036]If the install processing is commissioned to an external operator, then, information on the security is transferred to the commission site, and the information is not managed in the company itself. SUMMARY OF THE INVENTION [0037]Then, it is an object of the present invention to provide a mobile terminal device in which information is easily managed upon installing the value processing function. [0038]In order to solve the object, according to a first aspect of the invention, there is provided a mobile terminal device comprising: information processing means for processing electronic information; storing means for storing the electronic information; generating means for generating money information storing means for storing money information to the storing means; secret information receiving means for being connected to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device; and installing means for installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0039]According to the invention, in the mobile terminal device the secret information is identification information for identifying the mobile terminal device by the predetermined terminal device or the predetermined server device. [0040]According to the invention the mobile terminal device further comprises: ID information receiving means for receiving registering ID information from the providing server device; and display means for displaying information, wherein the installing means installs the received registering ID information to the storing means so as to display the received registering ID information on the display means. [0041]According to the invention, in the mobile terminal device the money information processing program enables the information processing means to realize an ID sending function for sending, to the predetermined terminal, the registering ID information installed upon receiving the changing information of the amount of money from the predetermined terminal by the money-amount information receiving function. [0042]According to a second aspect of the invention, a mobile terminal method executed by a computer comprises information processing means for processing electronic information, storing means for storing the electronic information, generating means, secret information receiving means, and installing means, the mobile terminal method comprising: a generating step of generating money information storing means for storing money information to the storing means; a secret information receiving step of enabling the connection to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device by the secret information receiving means; and an installing step of installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0043]According to a third aspect of the invention, a mobile terminal program for a computer comprises information processing means for processing electronic information and storing means for storing the electronic information to execute: a generating function for generating money information storing means for storing money information to the storing means; a secret information receiving function for enabling the connection to a providing server device for providing predetermined secret information and receiving the secret information from the providing server device; and an installing function for installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0044]According to a fourth aspect of the invention, a providing server device for providing secret information to a mobile terminal device according to the first aspect comprises: connecting means for enabling the connection to the mobile terminal device; and sending means for sending the secret information to the connected mobile terminal device. [0045]According to a fifth aspect of the invention a providing server method executed by a computer comprising connecting means and sending means, for providing secret information to a mobile terminal device according to the first aspect comprises: a connecting step of enabling the connection to the mobile terminal device by the connecting means; and a sending step of sending the secret information to the connected mobile terminal device by the sending means. [0046]According to a sixth aspect of the invention, a providing server program for providing secret information to a mobile terminal device for enabling a computer to realize: a connecting function for enabling the connection to the mobile terminal device; and a sending function for sending the secret information to the connected mobile terminal device. [0047]According to another embodiment of the invention, a mobile terminal device comprises: connecting means for enabling the connection to an information processing device comprising information processing means for processing electronic information and storing means for storing the electronic information; generating means for generating money information storing means for storing money information to the storing means for the connected information processing device; secret information receiving means for enabling the connection to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device; and installing means for installing, into the storing means of the connecter information processing device, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0048]According to another embodiment of the first aspect of the invention, a mobile terminal device comprises: connecting means for enabling the connection to storing means for storing electronic information; information processing means for processing electronic information; generating means for generating money information storing means for storing money information to the connected storing means; secret information receiving means for enabling the connection to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device; and installing means for installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0049]According to the present invention, secret information to install the value processing function to the mobile terminal device is easily managed. BRIEF DESCRIPTION OF THE DRAWINGS [0050]FIG. 1 is a diagram showing one example of the structure of an electronic-money system; [0051]FIG. 2 is a diagram showing one example of the appearance of a mobile phone; [0052]FIG. 3 is a diagram for explaining a function of the mobile phone before installing the value processing function; [0053]FIG. 4 is a diagram for explaining the function of the mobile phone after installing the value processing function; [0054]FIG. 5 is a diagram for explaining one example of the hardware structure of the mobile phone; [0055]FIG. 6 is a diagram for explaining one example of the functional structure of an electronic-money server; [0056]FIG. 7 is a diagram showing one example of the logical structure of user information; [0057]FIG. 8 is a diagram showing one example of the logical structure of transaction information; [0058]FIG. 9 is a diagram showing one example of the hardware structure of the electronic-money server; [0059]FIG. 10 is a diagram showing one example of the hardware structure of an electronic-money card; [0060]FIG. 11(a) is a diagram for explaining the operation of the mobile phone upon installing the value processing function, and FIG. 11(b) is a diagram for explaining the operation of the mobile phone after installing the value processing function; [0061]FIG. 12 is a diagram showing one example of a screen displayed on the mobile phone upon installing the value processing function; [0062]FIG. 13 is a diagram for explaining the case of charging the value from an electronic-money terminal to the mobile phone; and [0063]FIG. 14 is a flowchart for explaining the installing sequence of the value processing function. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0064]Hereinbelow, a preferred embodiment of the present invention will be described. (1) Outline of Embodiments [0065]A mobile phone having an Internet access function comprises an IC chip having the same function as that used for a non-contact electronic-money card; and an auxiliary program (hereinafter, referred to as an installing program for installing the value processing function to the IC chip by a server device. At the time that the mobile phone is sold, the value processing function is not installed to the IC chip of the mobile phone. A user purchases the mobile phone, then, the mobile phone communicates with the server device for communication, and the value processing function is installed to the IC chip. [0066]At the installing time, the mobile phone sends, to an electronic-money server, information necessary for a carrier of electronic money, such as an IC chip ID (ID information uniquely assigned to the IC chip), and receives information necessary for using electronic-money service from the electronic-money server and installs the received information. The received and installed information includes secret information for security, such as key information, which will be described later. [0067]After installing the value processing function, the function operates. Then, similarly to the electronic-money card, the IC chip charges the value or performs the value processing such as the settlement using the value. [0068]The IC chip comprises an antenna for wireless communication with the electronic-money terminal, similarly to the electronic-money card. With the IC chip, the mobile phone is set to the electronic-money terminal to charge the value to the mobile phone, or the money is settled by the value stored in the mobile phone. [0069]Further, the mobile phone comprises an Internet access function. Therefore, the value on the IC chip is charged from the server device on the Internet, or the money is settled by the value stored in the IC chip. [0070]According to the embodiment, the mobile phone includes the IC chip (information processing device). Further, the IC chip may be detachable to the mobile phone, and may be attached to the mobile phone for use purpose. Alternatively, the mobile phone may include a function unit corresponding to a CPU (information processing means) of the IC chip, and a function unit corresponding to a memory (memory means) of the IC ship may be detachable. [0071]In the case of using a detachable IC chip or memory, a connector (connecting means) is arranged on the mobile phone side. (2) Details of the Embodiment [0072]FIG. 1 is a diagram showing an example of an electronic-money operating system 1 according to the embodiment. [0073]The electronic-money operating system 1 comprises: a mobile phone 7; an electronic-money server 2; an Internet 4; a base station 5; a phone line network 6; an electronic-money card 15; and electronic-money terminals 8, 8, 8 . . . . [0074]Hereinbelow, the components will be described later. [0075]The mobile phone 7 (mobile terminal device) comprises: a phone function unit 10; an electronic-money function unit 12; and a relay unit 27 which connects the phone function unit 10 to the electronic-money function unit 12. [0076]The phone function unit 10 is a function unit having a function as a digital phone having an Internet access function. The electronic-money function unit 12 is a function unit for storing the value and processing the value, similarly to the electronic-money card 15 (which will be described later). [0077]The communication is established between the phone function unit 10 and the electronic-money function unit 12 via the relay unit 27. [0078]Here the value means money information indicating the amount of money having the money price as electronic information, and has the identical exchange value to the money. The money information is operated by increase/reduction, thereby moving the value. Thus, the value is used for settlement (e.g. of a consumer transaction. [0079]The phone function unit 10 has two modes of a call mode and an application mode. A user uses communication service in the call mode. In the application mode, the user receives the service provided by the application. [0080]The phone function unit 10 communicates with the base station 5 by radio waves, and accesses the phone line network 6 or Internet 4 via the base station 5. [0081]Upon using the mobile phone 7 in the call mode, a communication line is established between the mobile phone 7 and a partner's phone via the phone line network 6. [0082]Upon using the mobile phone 7 in the application mode, the mobile phone 7 is accessed to the Internet 4, thereby using services provided by server devices. In addition, service of a game is used off-line (without being accessed to the Internet 4). [0083]FIG. 2 is a diagram showing an example of the appearance of the mobile phone 7. The mobile phone 7 comprises: a phone antenna 19; speaker 20; a display 21; a keyboard 22; and a microphone 23. [0084]The phone antenna 19 is an antenna for radio communication with the base station 5. [0085]The speaker 20 is a device for converting an electrical signal and generating sound. In the call mode, sound generated by a call partner is outputted. In the application mode, sound data-sent from the server device is reproduced. [0086]The display 21 is a display device for displaying characters and an image, such as a liquid crystal display or a plasma display. [0087]In the call mode, the display 21 displays call information on the call including a receiving state of radio waves, a phone number inputted by the user, or a phone number of the call partner. [0088]In the application mode, the display 21 displays a screen provided by the application. [0089]In the access to the Internet, a screen using screen data sent by the server device is displayed. [0090]In the off-line, various screens, such as a game screen, provided by the application are displayed. For example, the balance or history of value stored in the electronic-money function unit 12 is displayed. [0091]The keyboard 22 comprises a character key for inputting character information of numerals and characters and a function key. The function key is a key having assigned specific functions for turning on/off the mobile phone 7, switching the call mode and the application mode, or moving a cursor displayed on the exposing device 21, and clicking a button displayed on the display 21. [0092]The user presses the key of the display 21 to perform various operations, thereby inputting a URL (Uniform Resource Locators) on a desired Web site, inputting information in an input column displayed on the screen, and selecting an item displayed on the screen. [0093]With the above function, the URL of a service site (Web site for providing the service on the electronic money) of the electronic-money server 2 is inputted or the install operation of the value processing function is selected on the screen provided by the service site, thereby installing the value processing function to the mobile phone 7. [0094]The microphone 23 is a device for obtaining sound and converting the sound into an electronic signal. The user inputs the sound from the microphone 23. [0095]Next, a description is given of the value processing of the various functions provided for the mobile phone 7. [0096]The functions of the mobile phone 7 are different from the state before installing the value processing function and the state after the install operation. First, a description is given of the functional structure before installing the value processing function with reference to FIG. 3. [0097]FIG. 3 is a diagram showing the functional structure of the mobile phone 7 before installing the value processing function. [0098]Referring to FIG. 3, before installing the value processing function, the electronic-money function unit 12 shown in FIG. 1 is referred to as an IC function unit 12a. [0099]As will be described later, the phone function unit 10 and the IC function unit 12a comprise CPUs (Central Processing Units). The CPUs execute predetermined programs, thereby enabling the function units to operate like software. [0100]Referring to FIG. 3, the IC function unit 12a comprises a central processing unit 28a (information processing means) and a storing unit 29a (storing means). [0101]Although not shown, the IC function unit 12a has the identical function as that of an antenna (hereinafter, referred to as a terminal antenna) for communication between a non-contact IC card and the electronic-money terminal 8, and accesses a terminal for the non-contact IC card, such as the electronic-money terminal 8. [0102]The storing unit 29a is writable and readable and stores a plurality of pieces of programs data. [0103]At the time of sale of the mobile phone 7 to the users, a basic program for operating the IC function unit 28a is installed to the storing unit 29a. [0104]The above-mentioned basic program includes an OS (Operating System) for input/output processing of a file, and control of the IC function unit 12a, or a communication program for radio communication of the IC function unit 12a with a terminal for non-contact IC card. [0105]The central processing unit 28a is a function unit for executing a predetermined program, performing the calculation, controlling the entire IC function unit 12a, and executing information processing such as input/output of data. [0106]The central processing unit 28a reads a program or data from the storing unit 29a or the application unit 26. Further, the central processing unit 28a receives, by wireless manner, a program or data from a terminal for non-contact IC card via a terminal antenna, and reads the received program or data. [0107]An install program is read to the central processing unit 28a, and is executed, thereby installing application programs to the storing unit 29a. The install program is provided for each application program. [0108]The central processing unit 28a executes the install program and then ensures an area for installing the application program in the storing unit 29a (when the application program for install is known in advance, the area for the program is ensured in advance). [0109]After formatting the ensured area to match the data format of the application program, the application program is written to the area. [0110]After installing the application program to the storing unit 29a, the application program is read to the central processing unit 28a, and is executed. [0111]According to the embodiment, the application program (hereinafter, value processing program) is installed to the storing unit 29a, and the central processing unit 28a realizes the value processing function. [0112]The relay unit 27 is a function unit (interface) for relaying the communication between the phone function unit 10 and the IC function unit 12a. In the relay of communication between the phone function unit 10 and the IC function unit 12a, the relay unit 27 encrypts the data to be sent to the phone function unit 10, or decrypts the encrypted data to be sent to the IC function unit 12a by the phone function unit 10. [0113]This is because the data the phone function unit 10 receives and transmits to/from the electronic-money server 2 are encrypted/decrypted, thereby improving the security. [0114]The electronic-money server 2 comprises: means for combining the data received from the phone function unit 19; and means for encrypting the data sent to the mobile phone 7. [0115]When the communication format of the phone function unit 10 is different from that of the IC function unit 12a, the communication format can be converted. [0116]This is because, for example, there could be a case in which the IC function unit 12a communicates data in the same communication format of the non-contact IC card, while the phone function unit 10 uses the communication format on the Internet 4 and the communication format needs to be con converted to access the IC function unit 12a from the phone function unit 10. [0117]The application unit 26 is a function unit for providing various applications by the mobile phone 7. [0118]The application unit 26 provides an Internet access function for connecting the mobile phone 7 to the Internet 4, a using function of the IC function unit for using application programs installed in the IC function unit 12a, and a service providing function for providing various services such as a game or calendar. [0119]In the case of providing the Internet access function, the application unit 26 receives the input of URL and accesses the mobile phone 7 to a Web site specified by the URL. Further, the application unit 26 reproduces information (image information, character information, and sound information) sent by the site in the access destination and sends the information from the mobile phone 7 to a site in the access destination and thus functions as a browser. [0120]The application unit 26 has an installing unit 26a (installing means and generating means) for supporting the install operation of the value processing program (money information processing program) to the IC function unit 12a by the electronic-money server 2. [0121]The installing unit 26 communicates with the central processing unit 28a and the electronic-money server 2 and simultaneously installs (incorporates) the value processing program to the storing unit 29a. [0122]Specifically, the installing unit 26 operates cooperatively with the electronic-money server 2, and sends, to the central processing unit 28a, a program for installing the value processing program. The central processing unit 28a executes the sent program, thereby installing the value processing program to the storing-unit 29a. [0123]The program to be installed may be downloaded from the electronic-money server 2 at the install time, or may be provided for the installing unit 26a in advance. [0124]In the case of installing the value processing program, the installing unit 26a receives information necessary for executing the value processing program including key information (identification information used (String), 相关申请的交叉引用 [0001] 本申请是共同未决国际申请号 PCT/JP2004/002862 的美国国家阶段申请,于 2004 年 3 月 5 日提交,要求优先权日期为 2003 年 3 月 7 日,并以非英语公布。 技术领域 [0002] [0001] 本发明涉及一种移动电话装置,更具体地,涉及一种使用电子货币服务的移动电话。 背景技术 [0003] 近年来,电子货币结算系统的实证试验取得成功,电子货币已投入实际使用。 [0004] 目前,零售商店使用电子货币进行结算。 此外,为了向普通用户普及电子货币,努力开发元件技术和构建商业模型。 [0005] 除了零售店之外,使用电子货币的系统也被投入实际使用以调整火车或公共汽车的票价。 [0006] 对于电子货币,电子货币卡存储与货币相同的交换价值,即所谓的价值,并用作电子钱包。 [0007] 通过特定的终端设备(以下称为电子货币终端)将价值写入电子货币卡。 写入值的处理称为充电。 在收取该价值后,从用户处收取对应于该价值的钱。 这样,实际的货币就对应了价值,从而保持了交换价值的安全性。 [0008] 使用价值的结算是通过从电子货币终端上存储在电子货币卡中的价值减去与结算对应的金额来执行的。 [0009] 电子货币卡包括非接触式IC(集成电路)卡或接触式IC卡。 [0010] 包括非接触IC卡的电子货币卡包括:具有价值处理功能和价值存储功能的IC芯片; 以及用于与电子货币终端通信的天线。 天线具有与电子货币终端进行无线通信的功能,还具有产生电力以接收来自电子货币终端的电子波并驱动IC芯片的功能。 [0011] 电子货币终端通过天线与IC芯片进行电波通信,访问电子货币卡内的IC芯片,进行各种价值处理(写入处理、减法、余额参照,以下称为 作为价值处理)。 电子货币卡的使用方式主要有以下几种。 (1) 收费金额 [0012] 首先,在设置有电子货币终端的店铺中,将电子货币卡设置于电子货币终端,向负责人请求价值的写入操作。 在这种情况下,支付与价值对应的钱。 [0013] 接下来,负责人操作电子货币终端以将充值金额写入电子货币终端。 [0014] 然后,电子货币终端向电子货币卡内的IC芯片发送追加与价值对应的货币的写入命令。 [0015] IC芯片接收写入命令并执行命令,从而增加存储在IC芯片中的有价货币。 [0016] 如上所述,价值被记入电子货币卡。 [0017] 顺便提及,在无人电子货币终端中,设置电子货币卡并将货币设置到电子货币卡,从而自动充值。 (2) 按价值结算 [0018] 首先,将作为结算对象的商品或服务出示给电子货币终端的负责人。 电子货币卡被设置到安装到商店的电子货币终端,并且指示使用价值的结算的消息被发送到负责人。 [0019]相反,负责人操作电子货币终端以从存储在电子货币卡中的价值中减去用于结算的货币。 [0020] 然后,电子货币终端向电子货币卡中的IC芯片发送用于减去对应于货币的价值的减法命令。 [0021] IC芯片接收减法命令并执行该命令,从而减去与IC芯片中存储的值对应的值。 [0022] 如上所述,使用电子货币卡内的价值进行结算。 [0023] 附带地,在安装到自动售货机的电子货币终端中,用户购买商品,并且自动结算价值。 (3) 在互联网上使用电子货币 [0024] 通过具有因特网访问功能的终端装置和用于向/从电子货币卡读取/写入数据的读取器/写入器,向电子货币卡充值或使用存储在电子货币卡中的值进行结算 -钱卡。 [0025] 当要充值时,电子货币卡被设置到读取器/写入器并在终端设备上访问用于充值的网站。 然后,在服务器装置和电子货币卡之间建立通信,并且服务器装置将值写入电子货币卡。 对应于书面价值的钱从用户的银行账户中提取,或者通过信用卡处理。 [0026] 在使用价值的结算中,类似地,在服务器设备和电子货币卡之间建立通信,并且减去价值。 [0027] 如上所述,电子货币卡被用作预付电子钱包,特别是对于用户来说小额货币的结算是有利的,因为小额零钱不会给用户造成负担。 [0028] 最近,手机过度普及,尝试手机具有与电子货币卡相同的功能。 [0029] 如果手机具有与电子货币卡相同的功能,用户可以通过手机充值或使用手机中存储的金额进行结算。 [0030] 如上所述,以下技术可以让手机具备电子货币卡的功能。 [0031] (专利文献1) [0032] 日本未审查专利申请公开号 2002-352173 [0033] 根据专利文献1所公开的发明,在移动电话中设置用于存储价值的特定存储器,根据该价值进行充值或结算。 [0034] 在将与电子货币卡相同的价值处理功能安装到移动电话时,安装时机是个问题。 [0035] 在手机上安装值处理功能后,必须安装各种安全信息。 [0036] 如果将安装处理委托给外部运营商,则与安全有关的信息被传送到委托站点,并且该信息不在公司本身进行管理。 发明内容 [0037] 因此,本发明的目的在于提供一种在安装了价值处理功能时能够容易地管理信息的便携终端装置。 [0038]为了解决该目的,根据本发明的第一方面,提供了一种移动终端设备,包括: 用于处理电子信息的信息处理装置; 用于存储电子信息的存储装置; 用于生成货币信息的生成装置,用于将货币信息存储到存储装置的存储装置; 秘密信息接收装置,用于连接到提供预定秘密信息的提供服务器设备,并用于从提供服务器设备接收秘密信息; 安装装置,用于在存储装置中安装使信息处理装置能够执行货币信息处理的货币信息处理程序和接收到的秘密信息,其中货币信息处理程序使信息处理装置能够实现货币量 信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收货币数量的变化信息,以及货币信息处理功能,用于改变存储在货币信息存储中的货币信息的货币数量 是指利用接收到的金额变化信息。 [0039] 根据本发明,在移动终端设备中,秘密信息是用于由预定终端设备或预定服务器设备识别移动终端设备的识别信息。 [0040] 根据本发明,移动终端设备还包括: ID信息接收装置,用于从提供服务器设备接收注册ID信息; 以及用于显示信息的显示装置,其中,安装装置将接收到的注册ID信息安装到存储装置中,以便在显示装置上显示接收到的注册ID信息。 [0041] 根据本发明,在移动终端设备中,货币信息处理程序使信息处理装置能够实现ID发送功能,用于向预定终端发送在从 通过金额信息接收功能向规定的终端发送信息。 [0042] 根据本发明的第二方面,一种由计算机执行的移动终端方法包括用于处理电子信息的信息处理装置、用于存储电子信息的存储装置、生成装置、秘密信息接收装置和安装装置,该移动终端方法 包括:生成货币信息存储装置的生成步骤,用于将货币信息存储到存储装置; 秘密信息接收步骤,使与提供预定秘密信息的提供服务器设备的连接成为可能,并通过秘密信息接收装置从提供服务器设备接收秘密信息; 以及安装步骤,将用于使信息处理装置执行货币信息处理的货币信息处理程序和接收到的秘密信息安装到存储装置中,其中货币信息处理程序使信息处理装置能够实现货币- 金额信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收金额的变化信息,以及货币信息处理功能,用于改变存储在货币信息中的货币信息的金额 存储装置利用接收到的金额变化信息。 [0043]根据本发明的第三方面,用于计算机的移动终端程序包括用于处理电子信息的信息处理装置和用于存储电子信息以执行的存储装置:用于生成货币信息的生成功能存储装置用于将货币信息存储到 储存装置; 秘密信息接收功能,用于与提供预定的秘密信息的提供服务器装置连接,并从提供服务器装置接收秘密信息; 以及安装功能,用于将用于使信息处理装置执行货币信息处理的货币信息处理程序和接收到的秘密信息安装到存储装置中,其中货币信息处理程序使信息处理装置能够实现货币- 金额信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收金额的变化信息,以及货币信息处理功能,用于改变存储在货币信息中的货币信息的金额 存储装置利用接收到的金额变化信息。 [0044] 根据本发明的第四方面,一种用于向根据第一方面的移动终端设备提供秘密信息的提供服务器设备包括: 连接装置,用于实现与移动终端设备的连接; 发送装置,用于向连接的移动终端设备发送秘密信息。 [0045] 根据本发明的第五方面,一种由计算机执行的提供服务器方法,包括连接装置和发送装置,用于向根据第一方面的移动终端设备提供秘密信息,包括:连接步骤,启用与移动终端的连接 通过连接装置的装置; 发送步骤,通过发送装置将保密信息发送给连接的移动终端设备。 [0046] 根据本发明的第六方面,一种提供服务器程序,用于向移动终端设备提供秘密信息,以使得计算机能够实现: 连接功能,用于实现与移动终端设备的连接; 以及发送功能,用于将秘密信息发送到连接的移动终端设备。 [0047] 根据本发明的另一个实施例,移动终端设备包括:连接装置,用于实现与信息处理设备的连接,该信息处理设备包括用于处理电子信息的信息处理装置和用于存储电子信息的存储装置; 用于生成货币信息的生成装置,用于将货币信息存储到连接的信息处理设备的存储装置中的存储装置; 秘密信息接收装置,用于实现与提供预定秘密信息的提供服务器设备的连接,并用于从提供服务器设备接收秘密信息; 安装装置,用于将用于使信息处理装置执行货币信息处理的货币信息处理程序和接收到的秘密信息安装到连接器信息处理设备的存储装置中,其中货币信息处理程序使信息处理装置能够执行 实现用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收金额变化信息的金额信息接收功能和用于改变货币信息的金额的货币信息处理功能 利用接收到的金额变化信息,将货币金额存储在货币信息存储装置中。 [0048]根据本发明第一方面的另一个实施例,一种移动终端设备包括:连接装置,用于实现与用于存储电子信息的存储装置的连接; 用于处理电子信息的信息处理装置; 用于生成货币信息存储装置的生成装置,用于将货币信息存储到连接的存储装置; 秘密信息接收装置,用于实现与提供预定秘密信息的提供服务器设备的连接,并用于从提供服务器设备接收秘密信息; 安装装置,用于在存储装置中安装使信息处理装置能够执行货币信息处理的货币信息处理程序和接收到的秘密信息,其中货币信息处理程序使信息处理装置能够实现货币量 信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收货币数量的变化信息,以及货币信息处理功能,用于改变存储在货币信息存储中的货币信息的货币数量 是指利用接收到的金额变化信息。 [0049] 根据本发明,容易管理用于将价值处理功能安装到移动终端设备的秘密信息。 附图的简要说明 [0050] 图1是表示电子货币系统的构成例的图。 [0051] 图2是表示移动电话的外观例的图。 [0052] 图3是用于说明安装数值处理功能之前的移动电话的功能的图。 [0053] 图4是手机安装数值处理功能后的功能说明图。 [0054] 图5是用于说明移动电话的硬件结构的一例的图。 [0055] 图6是用于说明电子货币服务器的功能结构的一例的图。 [0056] 图7是表示用户信息的逻辑结构的一例的图。 [0057] 图8是表示交易信息的逻辑结构的一个例子的图。 [0058] 图9是表示电子货币服务器的硬件结构的一例的图。 [0059] 图10是表示电子货币卡的硬件结构的一例的图。 [0060] 图 11( a )是用于说明移动电话在安装值处理功能时的操作的图,图11( b )为手机安装数值处理功能后的操作说明图; [0061] 图12是表示安装了数值处理功能时移动电话显示的画面的一例的图。 [0062] 图13是用于说明从电子货币终端向移动电话充值的情况的图。 和 [0063] 图14是用于说明值处理功能的安装顺序的流程图。 优选实施例的详细说明 [0064] 以下,对本发明的优选实施方式进行说明。 (1)实施方式概要 [0065] 一种具有上网功能的手机,包括与非接触式电子货币卡功能相同的IC芯片; 以及辅助程序(以下称为安装程序,用于通过服务器设备将价值处理功能安装到IC芯片。在移动电话销售时,价值处理功能未安装到IC芯片 手机,用户购买手机后,手机与服务器设备进行通信,并在IC芯片上安装价值处理功能。 [0066]在安装时,移动电话向电子货币服务器发送电子货币的载体所需的信息,例如IC芯片ID(唯一分配给IC芯片的ID信息),并接收使用电子货币所需的信息 -来自电子货币服务器的货币服务并安装接收到的信息。 接收和安装的信息包括用于安全的秘密信息,例如稍后将描述的密钥信息。 [0067] 安装值处理函数后,函数运行。 然后,类似于电子货币卡,IC芯片对价值进行充值或使用该价值执行诸如结算的价值处理。 [0068] IC芯片包括用于与电子货币终端进行无线通信的天线,类似于电子货币卡。 通过IC芯片,将手机设置为电子货币终端,向手机充值,或通过手机中存储的金额进行结算。 [0069] 进一步的,所述手机具有上网功能。 因此,IC芯片上的价值是从互联网上的服务器设备收取的,或者是用IC芯片中存储的价值来结算的。 [0070] 根据该实施例,移动电话包括IC芯片(信息处理装置)。 此外,IC芯片可以是可拆卸到手机上的,并且可以附加到手机上使用。 或者,移动电话可以包括对应于IC芯片的CPU(信息处理装置)的功能单元,并且对应于IC芯片的存储器(存储装置)的功能单元可以是可拆卸的。 [0071] 在使用可拆卸的IC芯片或存储器的情况下,连接器(连接装置)布置在移动电话侧。 (2)实施方式的详细内容 [0072] 图1是表示电子货币操作系统的例子的图 1 根据实施例。 [0073] 电子货币操作系统 1 包括:一部手机 7 ; 电子货币服务器 2 ; 互联网 4 ; 基站 5 ; 电话线网络 6 ; 电子货币卡 15 ; 和电子货币终端 8 , 8 , 8 . . . . [0074] 在下文中,稍后将描述这些组件。 [0075] 手机 7 (移动终端设备)包括:电话功能单元 10 ; 电子货币功能单元 12 ; 和一个中继单元 27 连接电话功能单元 10 到电子货币功能单元 12 . [0076] 电话功能单元 10 是具有作为具有因特网访问功能的数字电话的功能的功能单元。 电子货币功能单元 12 是存储价值和处理价值的功能单元,类似于电子货币卡 15 (这将在后面描述)。 [0077] 电话功能单元之间建立通信 10 和电子货币功能单元 12 通过中继单元 27 . [0078] 在此,价值是指表示具有作为电子信息的货币价格的金额的货币信息,并且具有与货币相同的交换价值。 通过增加/减少操作货币信息,从而移动价值。 因此,该值用于结算(例如消费者交易。 [0079] 电话功能单元 10 具有调用模式和应用模式两种模式。 用户在呼叫模式下使用通信服务。 在应用模式下,用户接收应用提供的服务。 [0080] 电话功能单元 10 与基站通信 5 通过无线电波,并接入电话线网络 6 或互联网 4 通过基站 5 . [0081] 使用手机时 7 在通话模式下,手机与手机之间建立了一条通讯线路 7 和合作伙伴的电话通过电话线网络6 . [0082] 使用手机时 7 在应用程序模式下,手机 7 访问互联网 4 ,从而使用服务器设备提供的服务。 此外,游戏服务是离线使用的(无需访问互联网 4 ). [0083] 图2是移动电话的外观示例图 7 . 手机 7 包括:电话天线 19 ; 扬声器 20 ; 显示器 21 ; 键盘 22 ; 和麦克风 23 . [0084] 手机天线 19 是与基站进行无线电通信的天线 5 . [0085] 演讲者 20 是一种转换电信号并产生声音的装置。 在通话模式中,输出通话伙伴发出的声音。 在应用模式中,再现从服务器设备发送的声音数据。 [0086] 显示器 21 是用于显示字符和图像的显示设备,例如液晶显示器或等离子显示器。 [0087] 在通话模式下,显示 21 显示呼叫的呼叫信息,包括无线电波的接收状态、用户输入的电话号码或呼叫伙伴的电话号码。 [0088] 在应用模式下,显示 21 显示应用程序提供的屏幕。 [0089] 在访问因特网时,显示使用服务器设备发送的屏幕数据的屏幕。 [0090] 在离线状态下,显示应用提供的游戏画面等各种画面。 例如,存储在电子货币功能单元中的余额或历史价值 12 被陈列。 [0091] 键盘 22 包括用于输入数字和字符的字符信息的字符键和功能键。 功能键是分配了特定功能的按键,用于打开/关闭手机 7 ,切换调用模式和应用模式,或移动显示在显示设备上的光标 21 ,然后单击显示屏上显示的按钮 21 . [0092] 用户按下显示器的键 21 执行各种操作,从而在所需网站上输入 URL(统一资源定位器),在屏幕上显示的输入栏中输入信息,并选择屏幕上显示的项目。 [0093] 通过上述功能,电子货币服务器的服务站点(提供电子货币服务的网站)的 URL 2 在服务站点提供的屏幕上输入或选择值处理功能的安装操作,从而将值处理功能安装到手机上 7 . [0094] 麦克风 23 是一种获取声音并将声音转换成电子信号的装置。 用户从麦克风输入声音 23 . [0095] 下面对手机提供的各种功能的取值处理进行说明 7 . [0096] 手机的功能 7 不同于安装值处理函数之前的状态和安装操作之后的状态。 首先,参照图3说明安装值处理功能之前的功能结构。 [0097] 图3为手机功能结构示意图 7 在安装值处理功能之前。 [0098] 参考图3,在安装价值处理功能之前,电子货币功能单元 12 如图1所示称为IC功能单元 12 a. [0099] 正如后面将要描述的,电话功能单元 10 和 IC 功能单元 12 a 包括 CPU(中央处理单元)。 CPU执行预定程序,从而使功能单元能够像软件一样操作。 [0100] 参考图3,IC功能单元 12 a 包括一个中央处理单元 28 a (信息处理装置)和存储单元 29 a (存储方式)。 [0101] 虽然没有显示, IC功能单元 12 a 具有与用于非接触式IC卡和电子货币终端之间的通信的天线(以下称为终端天线)相同的功能 8 ,接入非接触式IC卡终端,如电子货币终端 8 . [0102] 收纳单元 29 a 可写入可读取,并储存多个程序数据。 [0103] 手机销售时 7 给用户,用于操作 IC 功能单元的基本程序 28 a 安装到存储单元 29 a. [0104] 上述基本程序包括用于文件的输入/输出处理的OS(操作系统)和IC功能单元的控制 12 a ,或用于IC功能单元无线电通信的通信程序 12 a 带有非接触式IC卡终端。 [0105] 中央处理器 28 a 是一个功能单元,用于执行预定的程序,进行计算,控制整个IC功能单元 12 a ,并执行信息处理,例如数据的输入/输出。 [0106] 中央处理器 28 a 从存储单元中读取程序或数据 29 a 或申请单位 26 . 此外,中央处理器 28 a 通过终端天线以无线方式接收来自非接触式IC卡终端的程序或数据,并读取接收到的程序或数据。 [0107] 安装程序被读取到中央处理器 28 a ,并被执行,从而将应用程序安装到存储单元 29 a . 为每个应用程序提供安装程序。 [0108] 中央处理器 28 a 执行安装程序,然后在存储单元中确保用于安装应用程序的区域 29 a (当预先知道要安装的应用程序时,预先确定程序的区域)。 [0109] 在对保证区域进行格式化以匹配应用程序的数据格式后,将应用程序写入该区域。 [0110] 将应用程序安装到存储单元后 29 a , 应用程序被读入中央处理器 28 a , 并被执行。 [0111] 根据该实施例,应用程序(以下称为值处理程序)被安装到存储单元 29 a , 和中央处理单元 28 a 实现值处理功能。 [0112] 中继单元 27 是一个功能单元(接口),用于中继电话功能单元之间的通信 10 和 IC 功能单元 12 a . 在电话功能单元之间的中继通信 10 和 IC 功能单元 12 a , 中继单元 27 加密要发送到电话功能单元的数据 10 , 或解密加密数据发送给IC功能单元 12 a 通过电话功能单元 10 . [0113] 这是因为电话功能单元的数据 10 从电子货币服务器接收和传输 2 加密/解密,从而提高安全性。 [0114] 电子货币服务器 2 包括:用于组合从电话功能单元接收的数据的装置 19 ; 以及对发送到手机的数据进行加密的方法 7 . [0115] 当电话功能单元的通信格式 10 不同于IC功能单元 12 a , 可以转换通讯格式。 [0116]这是因为,例如,可能存在 IC 功能单元 12 a 以与非接触式IC卡相同的通信格式进行数据通信,而电话功能单元 10 使用互联网上的通信格式 4 需要con转换通讯格式才能访问IC功能单元 12 a 从电话功能单元 10 . [0117] 申请单位 26 是手机提供各种应用的功能单元 7 . [0118] 申请单位 26 提供连接手机上网功能 7 上网 4 , IC功能单元的使用函数,用于使用安装在IC功能单元中的应用程序 12 a ,以及提供游戏或日历等各种服务的服务提供功能。 [0119] 在提供上网功能的情况下,申请单位 26 接收URL输入并访问手机 7 到 URL 指定的网站。 此外,申请单位 26 再现访问目的地站点发送的信息(图像信息、字符信息和声音信息),并从手机发送信息 7 到访问目的地的站点,从而起到浏览器的作用。 [0120] 申请单位 26 有一个安装单元 26 a (安装装置和生成装置)用于支持价值处理程序(货币信息处理程序)到IC功能单元的安装操作 12 a 通过电子货币服务器 2 . [0121] 安装单位 26 与中央处理器通信 28 a 和电子货币服务器 2 同时安装(合并)价值处理程序到存储单元 29 a. [0122] 具体安装单位 26 与电子货币服务器协同操作 2 , 并发送到中央处理单元 28 a ,用于安装值处理程序的程序。 中央处理器 28 a 执行发送的程序,从而将值处理程序安装到存储单元 29 a. [0123] 要安装的程序可以从电子货币服务器上下载 2 在安装时,或者可以为安装单元提供 26 a 提前。 [0124] 在安装值处理程序的情况下,安装单元 26 a 接收执行价值处理程序所需的信息,包括密钥信息(用于识别移动电话的识别信息 7 通过电子货币终端 8 )、后述的电子货币ID(注册ID信息)以及来自电子货币服务器的电子货币ID 2 , 并将信息存入存储单元 29 a . 此外,安装单位 26 a 发送到电子货币服务器 2 , 电子货币服务器提供电子货币服务所需的信息 2 ,例如构成IC功能单元的IC芯片的IC芯片ID 12 a. [0125] 下面结合图4对手机的功能结构进行说明 7 将值处理函数安装到IC功能单元后 12 a. [0126] 参考图4,IC功能单元 12 a 执行值处理程序,从而生成,给IC功能单元 12 a , 电子货币功能单元 12 包括值处理单元 28 和日志数据存储单元 29 (货币信息存储装置)。 [0127] 顺便提及,值处理程序可以总是被执行。 或者,在将另一个程序安装到 IC 功能单元时 12a , 相应的应用程序可能会根据需要启动。 [0128] 日志数据存储单元 29 是一个功能单元,用于存储值上的日志数据。 在执行值的写入、减法、余额的参照等值处理时,日志数据是记录处理内容的履历信息。 通过查阅日志数据,当前手机中存储的余额 7 或者可以知道价值处理的历史。 [0129] 作为日志数据记录的内容是处理的日期和时间、处理的类型、变化的值(例如,写入值时的值对应的金额或金额)等信息 减去价值时对应于减去的价值)如果对应于价值的金额通过处理改变,则电子货币终端的终端ID 8 用于访问和处理价值,以及当前价值余额。 [0130] 顺便说一句,申请单位 26 可以访问信息并可以在显示器上显示信息 21 . [0131] 值处理单元 28 与电子货币终端通信 8 或申请单位 26 (金额信息接收功能),执行存储在日志数据存储部中的价值处理(金额信息处理功能) 29 . [0132] 如后所述,电子货币终端 8 有读/写单元 8 a 具有用于与电子货币卡进行无线电通信的天线 15 . 手机 7 靠近电子货币终端 8 通过设置和值处理单元 28 从而与读写器单元通信 8 a 通过无线电波。 [0133] 通过申请单位 26 和中继单元 27 , 电子货币服务器 2 与值处理单元通信 28 以及价值处理单元 28 执行值处理。 [0134] 如上所述,值处理单元 28 与电子货币终端通信 8 , 申请单位 26 , 和电子货币服务器 2 . [0135] 值处理单元 28 接收命令的输入,并执行命令指定的信息处理。 [0136] 提供了各种类型的命令,例如,包括用于增加值的写入命令、用于减去值的减法命令以及用于参考值余额的余额参考命令。 [0137] 命令从电子货币终端输入 8 , 申请单位 26 , 和电子货币服务器 2 . [0138] 但是,仅由应用单元输入的命令 26 例如,是不改变与该值对应的金额的余额参考命令。 [0139] 在执行改变与价值相对应的金额的处理时,需要与实际货币对应。 因此,可以防止与电子货币载体无关地仅增加/减少价值。 [0140] 改变金额的命令形成金额改变信息。 [0141] 写入命令包括作为附件的关于值写入处理的信息,例如写入的金额、终端ID、处理日期和时间、以及用于指定组店的组店ID作为参数。 写入命令输入到值处理单元 28 然后是值处理单元 28 更新日志数据存储单元的日志数据 29 . 此外,值处理单元 28 执行加法,将参数指定的金额值加到当前余额上。 执行加法,从而收取价值。 [0142]减去命令具有作为附件的关于结算的信息,包括作为参数的减去值的金额、终端ID、处理日期和时间以及组店ID。 减法命令被输入到值处理单元 28 和值处理单元 28 从而更新日志数据存储单元的日志数据 29 . 此外,值处理单元 28 执行从当前余额中减去参数指定的金额值的减法。 通过执行减法,执行使用该值的结算(支付)。 [0143] 余额参考命令是获取当前余额值的命令。 平衡参考指令输入数值处理单元 28 和值处理单元 28 从而在日志数据存储单元中查找日志数据 29 ,从而返回值的当前余额。 [0144] 显示器 21 显示值处理单元返回的当前余额 28 ,从而向用户发送指示当前余额的通知。 [0145] 此外,用于操作值处理单元的各种命令 28 提供。 例如,操作值处理单元的命令 28 包括用于读取形成电子货币功能单元的IC芯片的IC芯片ID的读取命令 12 、电子货币ID的读取指令、向电子货币终端发送用于识别的密钥信息的指令 8 . [0146] 中继单元 27 中继应用程序单元之间的通信 26 和电子货币功能单元 12 . [0147] 申请单位 26 向值处理单元输入各种命令 28 通过中继单元 27 ,类似于电子货币终端 8 . 在这种情况下,继电器单元 27 具有与读写器相同的功能 8 a. [0148] 电子货币终端之间的通信 8 和电子货币功能单元 12 已加密。 [0149] 申请单位 26 访问值处理单元 28 通过中继单元 27 . 申请单位 26 向值处理单元输入各种命令 28 ,从而操作值处理单元 28 不改变价值余额(余额参考)并进一步连接到电子货币服务器 2 ,从而中介与电子货币服务器的通信 2 和值处理单元 28 连同继电器单元 27 . [0150] 上面提到了与值处理单元通信的方法 28 包括来自电子货币终端的无线电通信的情况 8 以及通过中继单元进行通信的情况 27 . [0151] 因此,写入命令或减法命令被输入到值处理单元 28 从电子货币终端 8 , 并通过充值或使用该值进行结算来进行结算。 命令输入到值处理单元 28 来自电子货币服务器 2 通过申请单位 26 . 然后,在互联网上收取价值 4 或者使用该值进行结算。 [0152] 下面以手机的硬件结构为例进行说明 7 参考图5,图5为安装值处理函数后的结构。 [0153] 电话功能单元 10 形成具有上网功能的数字手机 4 ,并且包括:电话天线 40 ; 基站通信单元 41 ; 电话控制单元 200 ; 一个存储单元 45 ; 显示单元 46 ; 一个操作单元 47 ; 数字信号处理单元 48 ; 和一个声音输入/输出单元 49 . [0154] 手机天线 40 向基站辐射电波 5 或吸收基站天线辐射的电波 5 . 于是,手机 7 通过无线电波与基站通信 5 , 并通过基站拨打电话 5 并上网 4 . [0155] 基站通信单元 41 (秘密信息接收装置和ID信息接收装置)驱动电话天线 40 ,并放大从电话天线发送的信号 40 或放大从基站接收到的信号 5 ,从而向电话控制单元提供信号 200 . [0156] 电话控制单元 200 包括:CPU 42 ; ROM(只读存储器) 43 和 RAM(随机存取存储器) 44 . [0157] 中央处理器 42 是中央处理单元,用于执行预定程序和进行各种信息处理,并表现出功能,如具有电话功能单元的互联网访问功能的移动电话 10 . [0158] 中央处理器 42 执行存储在ROM中的程序 43 , 内存 44 , 或存储单元 45 ,从而起到手机或互联网终端的作用 4 . 此外,中央处理器 42 访问电子货币功能单元 12 通过中继单元 27 . [0159] 只读存储器 43 是一个只读存储器,安排为可由 CPU 读取 42 , 存放CPU执行的程序或参数 42 . [0160] 只读存储器 43 例如,存储操作系统作为基本程序,用于 CPU 的操作 42 . [0161] 内存 44 是一个可读/可写的内存,为CPU提供一个工作区 42 在操作 CPU 时 42 . [0162] 收纳单元 45 存储 CPU 使用的程序或数据 42 . 收纳单元 45 是CPU的可读/可写内存 42 . 例如,存储单元 45 是闪存或 EEPROM(电可擦除可编程 ROM)。 [0163] 根据实施例,存储单元 45 包括:应用程序 45 a 用于启用 CPU 42 实现应用功能; 和一个安装程序 45 c 用于辅助电子货币服务器价值处理功能的安装操作 2 . [0164] 中央处理器 42 执行应用程序 45 a 和安装程序 45 c , 从而构建应用单元的软件 26 (参考图3)和安装单元 26 a. [0165] 此外,存储单元 45 存储用户注册的电话号码和电子邮件地址、假名和汉字转换程序以及其他信息(未显示)。 [0166] 显示单元 46 是在显示器上显示字符信息和图像的功能单元 21 (参考图2)。 [0167] 显示单元 46 在通话模式下选择性地显示用户注册的电话号码列表,并进一步显示通话信息,如基站发出的电波强度 5 , 用户输入的电话号码, 或呼叫伙伴电话号码的电话号码。 [0168] 在应用程序模式下,应用程序提供的应用程序屏幕 45 a 显示URL的输入栏、服务器装置发送的画面、邮件。 此外,显示价值的余额。 [0169] 经营单位 47 包括键盘 22 用于将用户的按键操作转换为电信号,并将转换后的信号输入CPU 42 . [0170] 声音输入输出单元 49 包括:麦克风 23 和演讲者 20, 转换通过麦克风接收到的声音 23 转换成模拟信号或将模拟信号转换为声音,并从扬声器输出声音 20 . [0171] 来自麦克风的用户语音转换为电信号,并将语音输入到电话功能单元 10 . 此外,从电话功能单元输出的声音信号 10 转换为声音并通过扬声器收听。 [0172] 数字信号处理单元 48 是将声音数据的模拟信号转换为数字信号或将数字信号快速转换为模拟信号的功能单元,并且包括例如DSP(数字信号处理器)。 此外,数字信号处理单元 48 压缩或解压缩声音数据。 [0173] 麦克风和扬声器使用模拟信号。 另一方面,电话功能单元的其他功能单元 10 使用数字信号。 然后,在输入声音信号后,数字信号处理单元 48 转换从麦克风输出的模拟信号,并进一步压缩转换后的信号。 在输出声音信号时,数字信号处理单元 48 解压缩电话功能单元输出的数字信号 10 并通过扬声器输出转换后的模拟信号。 [0174] 电子货币功能单元 12 包括:终端天线 35 ; 终端通信单元 31 ; IC控制单元 300 ; 和一个存储单元 36 . 元器件中,不含终端天线的元器件 35 被容纳在一个IC芯片上。 [0175] IC控制单元 300 和电话控制单元 200 通过中继单元连接 27 . [0176] 根据实施例,手机 7 包括电子货币功能单元 12 . 然而,本发明不限于此,电子货币功能单元 12 可以与手机分离 7 . [0177] 终端天线 35 与布置在读取器/写入器单元上的天线通信 8 a 电子货币终端 8 通过电波。 [0178] 终端通信单元 31 驱动终端天线 35 ,并进一步放大用于接收和传输的信号。 [0179] IC控制单元 300 包括:CPU 32 ; 只读存储器 33 ; 和一个内存 34 . [0180] 中央处理器 32 是中央处理单元,通过执行存储在ROM中的程序来执行数值处理 33 , 内存 34 , 和存储单元 36 . [0181] 只读存储器 33 是只读存储器,安排为可由 CPU 读取 32 . 只读存储器 33 存储,例如,操作系统,作为操作 CPU 的基本程序 32 . [0182] 在 IC 芯片的制造步骤中,特定的 IC 芯片 ID 被分配给 IC 芯片,并存储在 ROM 中 33 . [0183] IC 芯片 ID 在出厂后不会更改,一般情况下用户不会读取。 [0184] 内存 34 是一个可读/可写的内存,用于为CPU提供一个工作区 32 在操作 CPU 时 32 . [0185] 收纳单元 36 包括,例如,闪存或EEPROM,并且是布置成可由CPU读取/写入的存储介质 32 . 收纳单元 36 存储应用程序或其他数据。 [0186] 收纳单元 36 确保电子货币区 36 a 用于价值管理。 电子货币领域 36 a 形成这样的申请单位 26 a 将价值处理功能安装到电子货币功能单元 12 . [0187] 电子货币领域 36 a 包括一个程序区域 36 b 用于存储程序和日志数据区 36 c 用于存储日志数据。 [0188] 使能CPU的值处理程序 32 实现值处理函数安装到程序区 36 b . 中央处理器 32 执行值处理程序,从而构建值处理单元的软件 28 和日志数据存储单元 29 (参考图4)。 [0189] 节目区 36 b 存储从电子货币服务器发送的密钥信息和电子货币ID 2 , 在安装单元安装值处理函数时 26 a. [0190] 日志数据区 36 c 存储值处理的日志数据,形成日志数据存储单元 29 (参考图4)。 [0191] 存储单元中的应用程序 36 包括价值处理程序和作为通勤季票的季票程序(通过手机设置进站) 7 在检票口),并且有选择地驱动应用程序。 [0192] 如上所述,手机 7 具有值处理功能,因此用户不仅设置了手机 7 到电子货币终端 8 , 从而充值或使用该值进行结算, 还使用了电子货币服务器 2 ,从而收取价值或使用价值结算货币。 [0193] 接下来,对因特网进行说明 4 , 基站 5 , 和电话线网络 6 (参见图 1)。 [0194] 互联网 4 连接各种服务器设备和终端,并使用 TCP/IP(传输控制协议/互联网协议)或其他协议进行数据通信。 [0195] 互联网 4 一般采用分组通讯。 在分组通信中,数据以分组为单位被分割并被发送。 作为附件,包具有用于指定发送目的地的发送目的地指定信息和用于从发送目的地上的包恢复原始数据的恢复信息作为报头。 [0196] 数据接收端构造数据包并恢复原始数据。 [0197] 虽然未显示,但各种服务器设备已连接到互联网 4 . 用于提供各种服务的网站向服务器设备开放。 网站由 URL 指定。 [0198] 通过互联网接收或发送电子邮件 4 . 电子邮件帐户,作为电子邮件的发送目的地由电子邮件地址指定。 [0199] 电子邮件不仅发送和接收字符数据,还发送和接收图像数据、程序和作为附件的其他数据。 [0200] 基站 5 与手机通信 7 通过无线电波,为手机用户提供通话服务或上网服务 7 . [0201] 当用户接入基站时 5 从手机 7 在通话模式下,基站 5 将线路设置为电话线网络 6 用于呼叫操作。 当用户接入基站时 5 在应用模式中,基站 5 设置访问因特网使用Web服务器提供的服务的操作 4 . [0202] 参考图1,网上 4 和电话线网络 6 是独立安排的。 功能视图中使用独立排列,互联网 4 和电话线网络 6 包括物理上通用的传输介质。 [0203] 作为传输媒介,使用了各种电缆、光纤和经由人造卫星的线路。 [0204] 接着,对电子货币服务器进行说明 2 (参见图 1)。 [0205] 图6是表示电子货币服务器的功能结构的一例的概念图 2(提供服务器设备)。 电子货币服务器 2 上网 4 通过互联网线路,并进一步连接到电子货币终端 8 , 8 , 8 . . . . [0206] 电子货币服务器 2 包括:一个服务站点单元 56 ; 安装注册单元 57 ; 识别单元 58 ; 事务处理单元 59 ; 各种功能单元; 用户信息数据库 54 ; 交易信息数据库 55 ; 和其他各种数据库。 [0207] 根据该实施例,电子货币服务器 2 使用电子货币提供服务。 然而,本发明不限于此并且可以使用通过组合多个服务器设备获得的系统。 [0208] 例如,电子货币服务器的服务 2 可以通过将打开电子货币服务站点的Web服务器、用于识别用户的识别服务器、用于交易处理的交易处理服务器以及用于安装价值处理功能的安装服务器的服务器设备来提供。 [0209] 服务站点单位 56 是在因特网上以电子货币服务运营网站的功能单元 4 . [0210] 用户通过手机输入服务站点的URL 7 或者其他终端,从而访问服务站点,从而使用服务站点提供的各种服务。 [0211] 用户访问服务站点和电子货币服务器 2 在手机上显示主菜单屏幕时发送屏幕数据 7 . 主菜单屏幕可选择地显示由服务站点提供的服务的项目,并且用户选择期望的项目。 [0212] 提供各种服务项目,例如,不仅包括关于电子货币的使用,例如用户注册、用户注册信息的更改、价值的收取和使用价值的结算,还包括活动的新呈现、客户的接收 查询等 [0213] 用户注册后,同时安装数值处理功能。 [0214] 安装注册单元 57 是一个功能单元,进行用户注册信息的处理和值处理功能的安装操作,例如用户注册,值处理功能到手机的安装操作 7 、删除注册、注册内容的变更等。 [0215] 此外,安装注册单元 57 当用户选择用户注册信息上的项目时启动,例如主菜单屏幕上的用户注册或用户注册信息的更改。 [0216] 这里,对新用户登记的情况进行说明。 用户在主菜单屏幕上选择用户注册,然后选择安装注册单元 57 发送用于显示注册屏幕的屏幕数据到手机 7 . [0217] 注册屏幕有一栏用于输入注册信息,例如用户名、密码和发行者。 用户将信息输入到栏中,并将信息发送到电子货币服务器 2 . [0218] 安装注册单元 57 将信息存储到用户信息数据库 54 , 并转移到值处理函数的安装处理。 顺便提及,在价值处理功能的安装处理之前将使用条款呈现给用户,用户接受该条款,然后可以执行安装处理。 当不接受安装处理时,可以稍后执行。 [0219] 安装注册单元 57 与安装单元一起执行安装处理 26 a (参考图3)。 一、安装注册单元 57 从手机接收IC芯片ID 7 ,并将IC芯片ID存入用户信息数据库 54. IC芯片ID由申请单位读取 26 a 来自 IC 功能单元 12 a. [0220] 电子货币ID被使用并发送到手机 7 . 此外,电子货币ID存储在用户信息数据库中 54 . [0221] 安装注册单元 57 具有确保安全所必需的关键信息或其他秘密信息,并将秘密信息和必要的数据发送到手机 7 . [0222] 当用于安装值处理程序的程序被发送到手机时 7 来自电子货币服务器 2 ,程序发送到手机 7 . 手机的时候 7 提前有节目,节目不发。 [0223] 图7是表示存储在用户信息数据库中的用户信息的逻辑结构的例子的图。 54 . [0224] 用户信息包括电子货币ID 61 , 一个用户名 62 , 密码 63 , 发行人 64 , 一个 IC 芯片 ID 65 , 状态 66 , ETC。 [0225] 电子货币ID 61 是安装登记单位发行的电子货币ID 57 手机安装值处理功能后 7 . [0226] 尽管未显示,但电子货币服务器 2 具有用于对电子货币ID进行编号的编号表,以及电子货币ID 61 由安装注册单元从表中编号 57 . [0227] 用户名 62 是用户在注册屏幕上输入的名称。 [0228] 密码 63 是用于确认使用服务的用户是否为真实用户的信息,由用户在用户注册时设定。 [0229] 发行人 64 是用于指定在从电子货币服务器收取价值时由哪个发行者发行价值的信息 2 通过互联网 4 , 由用户在用户注册时从多个发行人中选择。 [0230] 尽管未显示,但电子货币服务器 2 有一个issuer master用于注册issuer,用户从issuer master中选择issuer。 [0231] 顺便提及,发行者表示发行价值的发行者,并且出于业务操作的原因存在多个发行者。 此外,发行的价值被任何电子货币终端使用 8 ,与发行人无关。 [0232] IC芯片ID 65 设置为电子货币服务器 2 从手机 7 安装价值处理功能后。 [0233] 根据该实施例,如上所述,IC芯片ID被注册,因此用户从移动电话被注册 7 . 未注册IC芯片ID时,用户从手机以外的其他终端注册 7 . [0234] 现状 66 为用户设置状态“未安装”和“已安装”。 [0235] 直到安装注册单元 57 接收用户注册并结束安装处理,安装注册单元 57 将状态设置为“未安装”。 安装过程结束后,安装注册单元 57 将状态更新为“已安装”。 [0236] 返回参考图6,识别单元 58 是注册用户使用服务站点时识别用户的功能单元。 [0237] 服务站点单位提供的服务 56 包括不需要识别的服务和需要识别的服务。 用户接收到标识,然后接收需要标识的服务。 [0238] 识别单位 58 发送,到手机 7,输入密码的画面数据(显示如图2所示的密码输入画面),接收用户从手机输入的密码、IC芯片ID、电子货币号码 7 . [0239] 信息核对到用户信息库中存储的信息 54 . 当信息与用户信息数据库中存储的信息相匹配时 54 ,用户被识别为普通用户。 [0240] 上述标识指定用户,从而提供针对该用户的服务。 [0241] 用户识别不需要所有的密码、IC芯片ID和电子货币ID。 密码、IC芯片ID和电子货币ID中的至少一种用于识别。 [0242] 事务处理单元 59 是将用户的交易记录记录到交易信息数据库中的功能单元 55 . [0243] 事务处理单元 59 记录,到交易信息数据库 55 、收费处理、结算等由手机进行的处理 7 或电子货币卡 15 . [0244] 图8是表示存储在交易信息数据库中的交易信息的逻辑结构的一个例子的图 55 . [0245] 交易信息包括电子货币ID 67 , 充电记录 68 , 结算记录 69 . [0246] 充电记录 68 记录进行充值操作的终端ID信息、充值日期、充值金额。 [0247] 电子货币ID 67 从手机读取 7 (或电子货币卡 15 ) 通过电子货币终端 8 . 在与电子货币服务器的通信中 2 通过互联网 4 , 电子货币 ID 67 从手机读取 7 通过电子货币服务器 2 . [0248] 例如,录音 71 记录图7中第一行的IC芯片ID,作为终端ID。 如上所述,在从电子货币服务器收取价值的情况下 2 通过互联网 4 , 手机的IC芯片ID 7 其中收费的价值被记录下来。 [0249] 记录 72 表示电子货币终端 8 由终端ID“347895”指定的终端收取相当于3,000日元的价值。 [0250] 结算记录 69 包括:结算终端; 结算日期和时间; 结算金额和价值。 例如录音 73 表示电子货币终端 8 终端 ID“2547657”指定的 2000 日元对应的金额结算。 [0251] 在使用电子货币服务器的价值结算中 2 通过互联网 4 , 手机的IC芯片ID 7 被记录为终端ID。 [0252] 交易信息中存储的交易信息 55 分析,从而将从发行者收取的现金按价值分配给结算货币的商店,以及非法电子货币卡 15 受到监控以收集用于业务的信息。 另外,同时记录用户购买的产品,从而进行市场调查等数据挖掘。 [0253] 顺便说一下,事务处理单元 59 不一定实时进行信息处理。 电子货币终端 8 存储交易信息并更新交易信息数据库 55 通过稍后接收交易信息。 因此,电子货币操作系统 1 无需访问电子货币服务器即可快速执行处理 2 在商店的收费操作或结算中。 [0254]根据该实施例,在电子货币操作系统中 1 ,用于结算的值存储在手机中 7 或电子货币卡 15 . 电子货币服务器 2 管理其交易信息。 [0255] 因此,电子货币服务器 2 在使用价值的结算中不实时访问,并在现场快速处理价值。 另外,交易信息暂时存储在电子货币终端的存储装置中 8 , 并被传送到电子货币服务器 2 在预定时间后,或者用于存储交易信息的存储介质被负责人收集。 [0256] 接着,对电子货币服务器的硬件结构的一例进行说明 2 (参见图 1)。 [0257] 如图9所示,电子货币服务器 2 包括:CPU 75 , 只读存储器 76 , 内存 77 , 通讯控制单元 78 ; 和存储单元 79 它们由总线连接 82 . [0258] 中央处理器 75 根据预定程序进行信息处理并控制整个电子货币服务器 2 . [0259] 只读存储器 76 是只读存储器,存储操作电子货币服务器的基本程序或参数 2 . [0260] 内存 77 是可读/可写内存,提供CPU的工作内存 75 或者加载并存储存储单元中存储的程序或数据 79 . [0261] 通信控制单元 78 (接收装置和发送装置)是与手机通信的功能单元 7 通过互联网 4 或基站 5 ,或与电子货币终端通信 8 通过通信线路。 [0262] 中央处理器 75 使用电子货币卡接收交易信息 15 或手机 7 从电子货币终端 8 通过通信控制单元 78 , 并与手机通信 7 并向手机充值 7 或使用手机中的金额进行结算 7 . [0263] 收纳单元 79 为硬盘或非易失性存储器,包括程序存储单元 80 用于存储各种程序和数据存储单元 81 用于存储数据。 [0264] 程序存储单元 80 存储操作系统,作为电子货币服务器运行的基本程序 2 ,用于操作服务站点的服务站点程序,用于注册用户或安装价值处理功能的注册程序,用于识别用户的识别程序,用于执行交易的交易程序等。 [0265] 中央处理器 75 执行程序,因此,服务站点单元 56 , 安装注册单元 57 , 识别单位 58 , 和事务处理单元 59 (参考图5)由软件配置。 [0266] 数据存储单元 81 存放用户信息的数据库 54 、交易信息数据库 55 、编号表、发行人主数据库和另一个数据库。 [0267] 接着,对电子货币终端进行说明 8 (参见图 1)。 [0268] 电子货币终端 8 是与电子货币功能单元通信的终端设备 12 手机的 7 通过无线电波,并操作值处理单元 28 (图 4)。 [0269] 电子货币终端 8 安装在便利店收银台,用户设置手机 7 到电子货币终端的预定部分 8 (读写器单元 8 a ), 从而对价值进行计费和结算。 [0270] 以下,对电子货币终端之间的通信进行说明 8 和手机 7 . 电子货币终端 8 执行与电子货币卡相同的处理 15 . [0271] 读写器单元 8 a 通过使用其中的天线进行近距离无线电通信,并通过无线电波从/向终端天线接收/发送数据 35 在电子货币功能单元 12 . [0272] 开始与手机通信时 7 , 电子货币终端 8 从电子货币功能单元读取关键信息 12 (向值处理单元发送读取关键信息的命令 28 并接收值处理单元发送的密钥信息 28 ). 将密钥信息与电子货币终端的密钥信息进行比对 8 然后检查电子货币功能单元是否 12 是有规律的。 [0273] 电子货币终端 8 确定电子货币功能单元 12 是有规律的,然后向值处理单元输入写入命令或减法命令 28 ,从而启用值处理单元 28 执行值处理。 [0274] 电子货币终端 8 在网络上连接到电子货币服务器 2 通过数字电话线等通信线路发送至电子货币服务器 2 , 对手机的计费结算信息 7 . [0275] 发送到电子货币服务器的信息 2 通过电子货币终端 8 是指定电子货币终端之间的处理内容的信息 8 和电子货币功能单元 12 ,例如,终端ID(用于识别电子货币终端的ID 8 )、会员店ID、电子货币编号、充值金额、结算金额、充值或结算日期时间。 [0276] 基于该信息,电子货币服务器 2 确认与存储在电子货币功能单元中的价值相对应的货币数量 12 以及哪个电子货币终端 8 以及哪个电子货币功能单元 12 收取或结算多少价值。 [0277] 电子货币终端 8 对电子货币卡进行充值和结算 15 ,这将在后面描述,类似于电子货币功能单元 12 . [0278] 根据该实施例,电子货币终端 8 安装在零售商店并执行计费和价值结算。 [0279] 此外,电子货币终端 8 安装在自动售货机、车站检票口、阶梯井、出租车、剧院入口等用户的收费处。 在这种情况下,电子货币终端 8 仅供结算即可安装。 [0280] 此外,在公共场所或公园等人多的地方,电子货币终端 8 for charge only 可以安装充电值。 [0281] 电子货币终端之间的网络连接 8 和电子货币服务器 2 一般是数字电话线。 此外,电子货币终端之间的网络连接 8 和电子货币服务器 2 由特定线路实现。 [0282] 可以在电子货币终端附近安装无线终端 8 并且可以通过电子货币终端之间的无线电线路实现连接 8 和一个无线终端。 由于一个无线终端与多个电子货币终端通信 8通过无线电波,与为个人电子货币终端安装线路相比,成本可能会降低 8 . 通过这种结构,有利的是,多个电子货币终端 8 安装在自动售货机上的设备被统一管理。 [0283] 此外,可以将存储介质布置到电子货币终端 8 , 存储电子货币终端之间通信处理内容的数据 8 和手机 7 ,负责人可以收集存储介质。 [0284] 该结构在安装电子货币终端的情况下是有利的 8 到移动成员,例如公共汽车、出租车、飞机或轮船。 [0285] 接着,对电子货币卡进行说明 15 (参见图 1)。 [0286] 电子货币卡 15 由塑料外壳中的终端天线和 IC 芯片组成。 [0287] 图10是表示电子货币卡的硬件构成例的图 15 . [0288] 电子货币卡 15 包括:IC芯片 112 ; 和一个中央处理器 132 , 只读存储器 133 , 一个内存 134 , 一个存储单元 136 , 和一个终端通信单元 131 安装在IC芯片上 112 . 电子货币卡 15 为IC芯片供电 112 ,还包括终端天线 135 用于接收和发送信号。 [0289] 电子货币卡 15 设置在电子货币终端的预定位置 8 , 类似于电子货币功能单元 12 ,从而在非接触状态下充电和稳定值。 [0290] 在这种情况下,电子货币终端发出的无线电波 8 被接收,并且终端天线 135 电子货币卡 15 产生电力,从而提供驱动IC芯片的电力 112 . 如上所述,终端天线 135 产生电力并从/向电子货币终端接收和发送数据 8 . [0291] 自电子货币功能单元 12 手机的 7 从手机的电源接收电力 7 , 电子货币功能单元的IC芯片 12 从电子货币终端获取电源 8 或手机电源 7 . [0292] 一般来说,当手机 7 开机时,电源取自手机电池 7 . 手机的时候 7 关闭时,从电子货币终端获取电源 8 . [0293] 中央处理器 132 , 只读存储器 133 , 内存 134 , 存储单元 136 , 和终端通信单元 131 安装在IC芯片上 112 具有与CPU相同的功能 32 , 只读存储器 33 , 内存 34 , 存储单元 34 , 和终端通信单元 31 安装在电子货币功能单元上 12 . [0294] 即存储单元 136 存储值处理程序和CPU 132 执行值处理程序,从而通过软件配置值处理单元。 收纳单元 136 有一个日志数据存储单元。 [0295] 值处理单元的操作设置了电子货币卡 15 到电子货币终端的读取器/写入器单元 8 ,从而收取价值并使用价值进行结算。 [0296] 接下来,说明在电子货币操作系统中安装价值处理功能的情况下的组件的操作 1 参考图11所示的参考数字具有上述结构( a ). [0297] (1) 用户购买手机后启动应用模式 7 , 从而使用应用程序单元 26. 然后,电子货币服务器的服务站点的URL 2 被输入到申请单元 26 , 和服务站点单元 56 电子货币服务器 2 从手机访问 7 . [0298] 相反,服务站点单元 56 发送,到手机 7 , 用于显示主菜单屏幕的屏幕数据。 [0299] 图 12( a )是表示显示在显示器上的主菜单画面的例子的图 21 (参考图2)的手机 7 . [0300] 参考图 12( a ), 电子货币服务器提供的服务 2 显示主菜单屏幕上的每个项目,用户通过操作键盘选择项目 22 . 在这里,“1。 注册用户”被选中。 [0301] (2) 用户选择项目“1. 注册用户”,然后安装注册单元 57 在电子货币服务器中启动 2 (图 11( a )). 一、电子货币服务器 2 将显示注册画面的画面数据发送至手机 7 . [0302] 图 12( b )是表示显示在显示器上的登记画面的例子的图 21 . [0303] 注册屏幕具有用于输入名称的栏、用于输入设置密码的栏、用于选择发行者的栏(未示出)和另一个输入栏。 通过操作键盘在注册屏幕上输入必要的项目 22 . [0304] 输入必要的项目后,用户点击显示在显示器上的发送按钮(未示出) 21 . 因此,输入项目被发送到电子货币服务器 2 从手机 7 . [0305] 关于发行者的选择,在显示器上显示发行者选择屏幕 21 , 用户任意选择显示屏上显示的发行人 21 . [0306] 在电子货币服务器中 2 , 安装注册单元 57 存储从手机接收到的注册信息 7 到用户信息数据库 54 , 并注册用户。 [0307] 注册用户后,安装注册单元 57 发送用于显示 use 子句的屏幕数据。 use子句中有install选择项供用户选择手机是否安装值处理功能 7 . 当用户同意使用条款时,即安装值处理功能。 当用户不同意使用条款时,不安装数值处理功能。 [0308] 图 12( c )是显示在显示器上显示的安装选择项目的一个例子的图 21 . [0309] 用户选择“是”和“否”中的任何一个。 选择“是”时,将注册用户,然后开始值处理功能的安装操作。 选择“NO”时,安装操作不会开始。 选择“否”时,电子货币服务器 2 稍后访问并执行安装操作。 [0310] (3) 当用户选择“YES”时,安装注册单元 57 开始安装过程。 [0311] 之后,安装注册单元 57 与安装单元通信 26 a 并同时进行安装处理。 [0312] 一、在手机中 7 , 安装单位 26 a (参考图3)确保电子货币区 36 a 在存储单元 36 (参考图5),并形成程序区 36 b 和日志数据区 36 c . 当电子货币区 36 a 事先保证,此步骤省略。 [0313] 然后,安装单元 26 a 将值处理程序安装到程序区 36 b. [0314] 此外,安装单元 26 a 读取IC芯片ID并将IC芯片ID发送至电子货币服务器 2 . [0315] 在电子货币服务器中 2 , 安装注册单元 57 从手机接收IC芯片ID 7 ,并将IC芯片ID存入用户信息数据库 54 . 此外,电子货币服务器 2 发行电子货币ID并将电子货币ID存储到用户信息数据库中 54 . [0316] 随后,安装注册单元 57 将编号的电子货币ID和密钥信息等秘密信息发送到手机 7 . [0317] 在手机里 7 , 安装单位 26 a 写,到程序区 36 b , 从电子货币服务器接收到的电子货币ID 2 以及秘密信息,例如关键信息。 [0318] 如上所述,电子货币服务器 2 和安装单元 26 a 协同安装值处理功能到IC功能单元 12 a. [0319] 安装过程中,安装单位 26 a 显示如图12所示的画面( d ) 在显示屏上 21 . [0320] 安装处理结束后,参见图12( e ), 电子货币 ID 显示在显示器上 21 . [0321] 电子货币ID用于用户服务。 此外,在充值或使用该价值进行结算的情况下,其信息和电子货币ID被记录并用于价值管理。 [0322] 图 11( b )是表示电子货币功能单元之间关系的图 12 , 电子货币终端 8 , 和电子货币服务器 2 安装值处理功能后。 [0323] 参考图 11( b ), 值处理单元 28 直接接收来自电子货币终端的访问 8 . 此外,值处理单元 28 接收来自电子货币服务器的访问 2 通过申请单位 26 和中继单元 27 . [0324] 值处理单元 28 从电子货币终端接收各种命令 8 和电子货币服务器 2 并执行命令,并处理日志数据存储单元中存储的值 29 . [0325] 说明从电子货币终端充值的操作 8 到电子货币功能单元 12 如上参照图13中的参考数字形成的。 [0326] (1) 一、手机 7 设置为读写器单元 8 a 电子货币终端 8 . 然后,电子货币功能单元之间开始通信 12 和电子货币终端 8 . [0327] 电子货币终端 8 请求将密钥信息传输到值处理单元 28 . 作为响应,值处理单元 28 从程序区读取关键信息 36 b (参考图5)并将密钥信息发送到电子货币终端 8 . [0328] 电子货币终端 8 通过使用从值处理单元接收到的密钥信息来识别 28 , 是否为电子货币功能单元 12 是有规律的。 此外,电子货币终端 8 从价值处理单元读取并记录电子货币ID 28 . [0329] (2) 电子货币终端 8 接收指定充值金额的写入信息的输入。 例如,负责人从设置到电子货币终端的输入设备输入写入信息 8 . [0330] (3) 电子货币终端 8生成对输入的货币对应的价值进行充值的写入指令,并将写入指令发送给价值处理单元 28 . [0331] (4) 值处理单元 28 从电子货币终端接收写入命令 8 并执行命令。 然后,值处理单元 28 将与输入的金额对应的金额添加到日志数据存储单元中存储的当前余额值中 29 ,并更新日志数据。 [0332] 作为上述处理的结果,价值被充入电子货币功能单元 12 从电子货币终端 8 . [0333] 类似地执行使用该值的结算。 即电子货币终端 8 从电子货币功能单元接收密钥信息 12 , 标识电子货币功能单元 12 ,生成结算对应金额的减法命令,并将该命令发送给值处理单元 28 . 值处理单元 28 执行命令并减去 value 的余额。 [0334] 写命令和减命令被输入到值处理单元 28 来自电子货币服务器 2 通过申请单位 26 和中继单元 27 ,价值被收取或结算。 在这种情况下,申请单位 26 读取密钥信息并将密钥信息发送给电子货币服务器 2 . 然后,电子货币服务器 2 识别关键信息。 [0335] 下面说明数值处理功能在手机上的安装顺序 7 参考图14所示的流程图。 [0336] 一、在手机中 7 ,电话功能单元 10 设置为应用模式,电子货币服务器的服务站点 2 被访问(在步骤 3 ). [0337] 相反,在电子货币服务器中 2 、服务现场单位 56 发送,到手机 7 ,用于显示主菜单屏幕的屏幕数据(在步骤 50 ). [0338] 手机 7 接收屏幕数据,应用单元 26 在显示屏上显示主菜单屏幕 21 通过使用屏幕数据。 [0339] 用户在主菜单屏幕上选择各种项目。 在这里,用户选择用户注册(步骤 5 ). [0340] 相反,在电子货币服务器中 2 , 安装注册单元 57 启动并发送到电子货币服务器 2 ,用于显示注册屏幕的屏幕数据(在步骤 55 ). [0341] 手机 7 接收屏幕数据,应用单元 26 在显示器上显示注册屏幕 21 通过使用屏幕数据。 [0342] 用户从注册屏幕输入注册所需的信息,例如姓名、密码和选择的发行者,并点击显示在注册屏幕上的发送按钮。 那么,申请单位 26 发送到电子货币服务器 2 ,输入的注册信息(步骤 10 ). [0343] 电子货币服务器 2 接收手机发送的注册信息 7 . 安装注册单元 57 搜索用户信息数据库 54 通过使用接收到的注册信息,并检查用户是否注册(步骤 60 ). 当用户的item存在且状态为“正在安装”时(Y;步骤中 60 ), 向手机发送用户注册信息 7 然后处理返回到步骤 50 . [0344] 当用户信息数据库 54 不包含该用户或当用户信息数据库的项目 54包括用户的item但现有状态为“未安装”(默认是在安装操作时造成的,然后再次执行安装操作)(N;在步骤 60 ), 用户注册到用户信息数据库 54 (在步骤 65 ). 然后,将用户项的状态设置为“未安装”。 [0345] 接下来,安装注册单元 57 发送使用条款数据,用于显示使用条款至手机 7 (在步骤 70 ). [0346] 手机 7 接收有关使用条款和申请单位的数据 26 在显示器上显示 use 子句 21 通过使用 use 子句上的数据。 [0347] 用户阅读使用条款,选择用户是同意使用条款并安装价值处理功能还是用户不同意使用条款不安装价值处理功能,并将选择结果发送给电子货币 服务器 2 (在步骤 15 ). [0348] 电子货币服务器 2 收到选择结果。 当用户不同意使用条款时(N;在步骤 75 ), 安装注册单元 57 不进行安装处理和电子货币服务器的状态 2 返回步骤 50 . [0349] 当用户同意使用条款时(Y;在步骤 75 ), 安装注册单元 57 开始安装过程,与安装单元通信 26 a 手机的 7 , 与安装单元一起进行值处理函数的安装处理 26 a (按步骤 80 和 20 ). [0350] 即安装注册单元 57 发行电子货币ID并将密钥信息和电子货币ID发送到手机 7 . 安装单位 26 a 读取IC芯片ID并将IC芯片ID发送至电子货币服务器 2 . [0351] 手机的时候 7 从电子货币服务器下载 2 ,值处理程序,安装注册单元 57 将价值处理程序发送到电子货币服务器 2 . [0352] 安装注册单元 57 存储从手机接收到的IC芯片ID 7 和手机的电子货币ID号 7 到用户信息数据库中用户的项目 54 . [0353] 安装单位 26 a 使用密钥信息和电子货币ID安装价值处理程序。 [0354] 手机 7 结束值处理程序,然后是应用程序单元 26 在显示屏上显示安装结束消息 21 并且用户检查消息。 用户查看消息,然后是应用单元 26 向电子货币服务器发送指示安装操作结束的通知 2 (在步骤 25 ). [0355] 电子货币服务器 2 收到结束通知,安装注册单元 57 更新用户信息数据库中用户项目的状态 54 并确定值处理函数的安装操作(在步骤 85 ). [0356] 当在安装值处理功能期间导致默认时,执行以下处理。 [0357] 在开始安装过程之前(步骤之前 20 和 80 ),不进行恢复处理,电子货币服务器 2 再次发送,到手机 7 , 用于显示主菜单屏幕的屏幕数据。 [0358] 在开始安装处理后发生默认时,执行恢复处理并且安装处理从处理中断开始。 [0359] 上述电子货币操作系统具有以下优点 1根据本发明。 [0360] (1)由于关键信息和另一个信息被发送到手机 7 直接从电子货币服务器 2 安装价值处理功能后,安全的秘密信息和其他秘密信息不会发送给外包合作伙伴,信息易于管理。 [0361] (2) 手机 7 不给IC功能单元安装价值处理功能就卖给用户 12 a (参考图3)。 因此,降低了安装操作的成本。 [0362] (3) 与电子货币卡相同 15 , 手机 7 安装价值处理功能后,对价值进行充值或使用价值进行结算。 此外,从电子货币服务器中充值并使用该价值进行结算 2 . [0363] 上面已经描述了根据本发明的实施例。 然而,本发明不限于所描述的实施例并且可以根据权利要求的范围进行修改。 [0364] 例如,具有电子货币功能单元的移动终端设备 12 不限于手机 7 并且可以是可以访问电子货币服务器的移动电子设备,例如PDA(个人数字助理)或袖珍铃 2 通过网络。 [0365] 根据该实施例,IC芯片具有与电子货币卡中的IC芯片相同的功能 15 安装在手机中 7 . 硬件结构不限于此。 例如,值处理程序安装在存储单元中 45 (参考图5)在电话功能单元 10 , 并且可以被 CPU 执行 42 . 在这种情况下,电话功能单元 10 具有电子货币功能单元的功能 12 因此无需在手机中安装IC芯片 7 .(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.040 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: BRPI0408141A(String), BRPI0408141A2(String), CA2518209A1(String), CN1759414A(String), EP1610245A1(String), EP1610245A4(String), HK1090455A(String), IN2161CHENP2005A(String), JP2004272561A(String), JP2004272561A5(String), JP2006018847A5(String), KR1020050111340A(String), RU2005131017A(String), TW200423691A(String), US20060100933A1(String), US7720717B2(String), WO2004079616A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: BRPI0408141A(String), BRPI0408141A2(String), CA2518209A1(String), CN1759414A(String), EP1610245A1(String), EP1610245A4(String), HK1090455A(String), IN2161CHENP2005A(String), JP2004272561A(String), JP2004272561A5(String), JP2006018847A5(String), KR1020050111340A(String), RU2005131017A(String), TW200423691A(String), US20060100933A1(String), US7720717B2(String), WO2004079616A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7720717B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), BRPI0408141A(String), BRPI0408141A2(String), CA2518209A1(String), CN1759414A(String), EP1610245A1(String), EP1610245A4(String), HK1090455A(String), IN2161CHENP2005A(String), JP2004272561A(String), JP2004272561A5(String), JP2006018847A5(String), KR1020050111340A(String), RU2005131017A(String), TW200423691A(String), US20060100933A1(String), US7720717B2(String), WO2004079616A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), BRPI0408141A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.066 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), BRPI0408141A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.089 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), CA2518209A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.098 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.099 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), CN1759414A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), EP1610245A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), EP1610245A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), HK1090455A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.142 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.142 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), IN2161CHENP2005A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), JP2004272561A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), JP2004272561A5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.179 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.179 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), JP2006018847A5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.188 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.188 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.188 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), KR1020050111340A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), RU2005131017A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), TW200423691A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), US20060100933A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), US7720717B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270685(Integer), WO2004079616A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7720717B2(String), US7720717B2(String), 1274112000(Integer), 270685(Integer), 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY CORPORATION(String), 索尼公司(String), 索尼公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185007(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 185007(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.301 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185007(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.306 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 2(Integer), 185007(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.315 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.337 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费 | 权利转移(String), 2(Integer), 185007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20170111495A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.392 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Control method for mobile terminal antenna, and mobile terminal(String), 一种移动终端天线的控制方法及移动终端(String), US20170111495A1(String), Embodiments provide a control method for a mobile terminal antenna, and a mobile terminal. By means of the control method for a mobile terminal antenna, and the mobile terminal, the mobile terminal can determine, according to a specific application scenario, for example, information such as a service that needs to be executed and an environment sensed, a quantity of antennas that should be enabled.(String), 实施例提供了一种移动终端天线的控制方法及移动终端。 本发明的移动终端天线的控制方法及移动终端,移动终端可以根据具体的应用场景,例如需要执行的业务、感知的环境等信息,确定数量。 应启用的天线数量。(String), US15/395022(String), 1483027200(Integer), US20170111495A1(String), 1492617600(Integer), 美国(String), 2(Integer), CN(String), 8(Integer), 0(Integer), 24(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185008(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\099b31f4549c47b89e858046c1aef8b3.png(String), 185008(Integer), 099b31f4549c47b89e858046c1aef8b3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Control method for mobile terminal antenna, and mobile terminal(String), 一种移动终端天线的控制方法及移动终端(String), US20170111495A1(String), Embodiments provide a control method for a mobile terminal antenna, and a mobile terminal. By means of the control method for a mobile terminal antenna, and the mobile terminal, the mobile terminal can determine, according to a specific application scenario, for example, information such as a service that needs to be executed and an environment sensed, a quantity of antennas that should be enabled.(String), 实施例提供了一种移动终端天线的控制方法及移动终端。 本发明的移动终端天线的控制方法及移动终端,移动终端可以根据具体的应用场景,例如需要执行的业务、感知的环境等信息,确定数量。 应启用的天线数量。(String), US15/395022(String), 1483027200(Integer), US20170111495A1(String), 1492617600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 8(Integer), 0(Integer), \20230420\099b31f4549c47b89e858046c1aef8b3.png(String), 24(Integer), 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 1. A method comprising:acquiring, by a mobile terminal, a start command of a service;determining, by the mobile terminal according to the start command, a quantity of antennas to be enabled for the service; andcontrolling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal, wherein the quantity of enabled antennas of the mobile terminal equals the quantity of antennas to be enabled for the service.(String), 1.一种方法包括:移动终端获取业务启动命令;移动终端根据启动命令确定该业务需要启用的天线数量;和移动终端控制移动终端启用的天线数量,其中,移动终端启用的天线数量等于业务要启用的天线数量。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 2. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, a service signal of the service, wherein the service signal is the start command;prompting, by the mobile terminal, a user whether to start the service; andcontrolling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the service signal has been received, in response to the mobile terminal not receiving, within a preset time, an operation instruction entered by the user, or determining that the operation instruction entered by the user and received within a preset time is not an instruction to start the service.(String), 2.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收业务的业务信号,业务信号为启动命令;移动终端提示用户是否开启服务;和响应于移动终端在预设时间内没有接收到用户输入的操作指令,移动终端控制移动终端启用的天线数量恢复到接收到业务信号之前的天线数量用户,或者确定在预设时间内接收到的用户输入的操作指令不是启动服务的指令。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 3. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, a service signal of the service;prompting, by the mobile terminal, a user whether to start the service;receiving, by the mobile terminal, an operation instruction entered by the user; andsing the operation instruction as the start command in response to the mobile terminal determining that the operation instruction is an instruction to start the service.(String), 3.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收业务的业务信号;移动终端提示用户是否开启服务;移动终端接收用户输入的操作指令;和响应于移动终端确定操作指令为启动业务的指令,将操作指令作为启动命令发出。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 4. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, an operation instruction relevant to the service, wherein the operation instruction has been entered by a user, wherein the operation instruction relevant to the service is the start command.(String), 4.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收与该业务相关的操作指令,该操作指令是用户输入的,该与该业务相关的操作指令为启动命令。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 5. The method according to claim 4, further comprising:prompting, by the mobile terminal, the user to enter a subsequent operation instruction; andcontrolling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the operation instruction relevant to the service is received, in response to the mobile terminal not receiving, within a preset time, the subsequent operation instruction entered by the user, or determining that the subsequent operation instruction received within the preset time is not an instruction to start the service.(String), 5.根据权利要求4所述的方法,还包括:移动终端提示用户输入后续操作指令;和响应于移动终端在预设时间内没有接收到后续的业务相关操作指令,移动终端控制移动终端启用的天线数量恢复到接收到业务相关操作指令之前的天线数量用户输入的操作指令,或者确定后续在预设时间内收到的操作指令不是启动服务的指令。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 6. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, an operation instruction relevant to the service, wherein the operation instruction has been entered by a user;prompting, by the mobile terminal according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction;receiving, by the mobile terminal, a subsequent operation instruction to start the service; andusing the subsequent operation instruction to start the service as the start command after receiving the subsequent operation instruction to start the service.(String), 6.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收用户输入的与业务相关的操作指令;移动终端根据与业务相关的操作指令提示用户输入后续操作指令;移动终端接收后续启动服务的操作指令;和接收到启动服务的后续操作指令后,将启动服务的后续操作指令作为启动命令。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 7. A method comprising:acquiring, by a mobile terminal, relevant information, wherein the relevant information comprises information selected from the group consisting of: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal;determining, by the mobile terminal according to the relevant information, a quantity of antennas to remain enabled; andcontrolling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal, wherein the quantity of enabled antennas corresponds to the relevant information.(String), 7.一种方法包括:移动终端获取相关信息,其中,相关信息包括选自以下信息:与移动终端相关的环境信息、移动终端的相关参数、移动终端当前的工作模式;移动终端根据相关信息确定保持开启的天线数量;和移动终端控制移动终端启用的天线数量,启用的天线数量与相关信息对应。8、如权利要求7所述的方法,所述移动终端根据相关信息确定保持开启的天线数量之前,还包括:移动终端将相关信息与预设条件进行比对;和判断相关信息是否满足预设条件;其中,所述预设条件为响应于所述相关信息为与所述移动终端相关的环境信息,且所述环境信息为所述移动终端辐射范围内的用户而预设的生物信息;其中,预设条件为响应于环境信息为移动终端所在场景而预设的限制场景;其中,预设条件大于预设辐射阈值响应于相关信息为移动终端的相关参数,相关参数为移动终端的辐射强度;其中,预设条件小于预设信号阈值响应于相关参数为移动终端的信号强度;和其中,预设条件为响应于相关参数为移动终端的当前工作模式而预设的工作模式。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 8. The method according to claim 7, before determining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled, further comprising:comparing, by the mobile terminal, the relevant information with a preset condition; anddetermining whether the relevant information meets the preset condition;wherein the preset condition is preset biological information in response to the relevant information being the environment information relevant to the mobile terminal, and the environment information being a user within radiation of the mobile terminal;wherein the preset condition is a preset limitation scenario in response to the environment information being a scenario in which the mobile terminal is located;wherein the preset condition is greater than a preset radiation threshold in response to the relevant information being the relevant parameter of the mobile terminal, and the relevant parameter being a radiant intensity of the mobile terminal;wherein the preset condition is less than a preset signal threshold in response to the relevant parameter being a signal strength of the mobile terminal; andwherein the preset condition is a preset work mode in response to the relevant parameter being the current work mode of the mobile terminal.(String), 9.根据权利要求8所述的方法,其中响应于环境信息为移动终端辐射范围内的用户,该方法还包括:移动终端将第三方设备发送的用户特征与预设的生物信息进行比对,或移动终端解析用户输入的操作指令或获取的用户信息,获取用户特征,移动终端将用户特征与预设的生物信息进行比对,其中,用户信息由用户或由第三方设备发送;判断用户特征是否符合预设生物信息;和移动终端根据相关信息确定用户特征满足预设生物信息后保持开启的天线数量。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 9. The method according to claim 8, wherein in response to the environment information being the user within the radiation of the mobile terminal, the method further comprises:comparing, by the mobile terminal, a user feature sent by a third-party device with the preset biological information, orparsing, by the mobile terminal, an operation instruction entered by the user or acquired user information, to acquire a user feature, and comparing, by the mobile terminal, the user feature with the preset biological information, wherein the user information is entered by the user or sent by a third-party device;determining whether the user feature meets the preset biological information; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the user feature meeting the preset biological information.(String), 10.根据权利要求8所述的方法,其中响应于环境信息为移动终端所在的场景,该方法还包括:移动终端将场景信息与预设的限制场景进行比较,判断场景信息是否满足预设的限制场景,其中,场景信息是通过移动终端上的传感器或摄像头获取的;和移动终端根据相关信息确定满足预设限制场景的场景信息响应的保持启用的天线数量。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 10. The method according to claim 8, wherein in response to the environment information being the scenario in which the mobile terminal is located, the method further comprises:comparing, by the mobile terminal, scenario information with the preset limitation scenario, and determining whether the scenario information meets the preset limitation scenario, wherein the scenario information is acquired using a sensor or a camera on the mobile terminal; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the scenario information meeting the preset limitation scenario.(String), 11.根据权利要求8所述的方法:其中响应于相关参数为移动终端的辐射强度,该方法还包括:移动终端将检测到的移动终端的辐射强度与预设的辐射阈值进行比较,判断移动终端的辐射强度是否大于预设的辐射阈值;和响应于移动终端的辐射强度大于预设辐射阈值,移动终端根据相关信息确定保持开启的天线数量;或者其中,响应于相关参数为移动终端的信号强度,该方法还包括:移动终端将检测到的移动终端信号强度与预设信号门限值进行比较,判断移动终端信号强度是否小于预设信号门限值;和移动终端根据相关信息确定响应于移动终端的辐射强度大于预设辐射阈值而保持开启的天线数量。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 11. The method according to claim 8:wherein in response to the relevant parameter being the radiant intensity of the mobile terminal, the method further comprises:comparing, by the mobile terminal, a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determining whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled, in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold; orwherein, in response to the relevant parameter being the signal strength of the mobile terminal, the method further comprises:comparing, by the mobile terminal, a detected signal strength of the mobile terminal with the preset signal threshold, and determining whether the signal strength of the mobile terminal is less than the preset signal threshold; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold.(String), 12.根据权利要求8所述的方法,其中响应于相关参数为移动终端当前的工作模式,该方法还包括:移动终端将移动终端当前的工作模式与预设的工作模式进行比较,判断当前的工作模式是否满足预设的工作模式,其中当前的工作模式是用户设置的,或者当前的工作模式为移动终端响应于移动终端检测到移动终端剩余电量低于预设电量阈值而设置;和移动终端根据相关信息,确定移动终端当前工作模式满足预设工作模式时,保持开启的天线数量。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 12. The method according to claim 8, wherein in response to the relevant parameter being the current work mode of the mobile terminal, and the method further comprises:comparing, by the mobile terminal, the current work mode of the mobile terminal with a preset operation mode, and determining whether the current work mode meets the preset work mode, wherein the current work mode is set by the user, or the current work mode is set by the mobile terminal in response to the mobile terminal detecting that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the current work mode of the mobile terminal meeting the preset work mode.(String), 13.移动终端,包括:处理器;和一种非暂时性计算机可读存储介质,存储由处理器执行的程序,该程序包括以下指令:获取服务的启动命令;根据启动命令确定该业务需要启用的天线数量;和控制移动终端启用的天线数量为业务确定启用的天线数量。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 13. A mobile terminal, comprising:a processor; anda non-transitory computer readable storage medium storing a program for execution by the processor, the program including instructions to:acquire a start command of a service;determine, according to the start command, a quantity of antennas to be enabled for the service; andcontrol a quantity of enabled antennas of the mobile terminal to be the quantity of antennas determined to be enabled for the service.(String), 14.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收服务的服务信号,服务信号为启动命令;提示用户是否启动服务;和响应于确定移动终端在预设时间内没有接收到用户输入的操作指令,控制移动终端使能的天线数量恢复到接收到业务信号之前的天线数量,或者移动终端在预设时间内接收到的用户输入的操作指令不是启动服务的指令。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 14. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive a service signal of the service, wherein the service signal is the start command;prompt a user whether to start the service; andcontrol the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the service signal is received, in response to determining that the mobile terminal does not receive, within a preset time, an operation instruction entered by the user, or that an operation instruction entered by the user and received by the mobile terminal within the preset time is not an instruction to start the service.(String), 15.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收服务的服务信号;提示用户是否启动服务;接收用户输入的操作指令;确定该操作指令为启动服务的指令;和在确定操作指令为启动服务的指令后,将该操作指令作为启动命令。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 15. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive a service signal of the service;prompt a user whether to start the service;receive an operation instruction entered by the user;determine that the operation instruction is an instruction to start the service; anduse the operation instruction as the start command after determining that the operation instructions is an instruction to start the service.(String), 16.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收用户输入的与业务相关的操作指令,其中,与业务相关的操作指令为启动命令。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 16. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive an operation instruction relevant to the service and entered by a user, wherein the operation instruction relevant to the service is the start command.(String), 17.根据权利要求16所述的移动终端,其中该说明还包括以下说明:提示用户输入后续操作指令;和响应于确定移动终端在预设时间内没有接收到后续输入的操作指令,控制移动终端使能的天线数量恢复到接收到与业务相关的操作指令之前的天线数量用户输入的移动终端在预设时间内接收到的后续操作指令不属于业务启动指令。(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 17. The mobile terminal according to claim 16, wherein the instructions further comprise instructions to:prompt the user to enter a subsequent operation instruction; andcontrol the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the operation instruction relevant to the service is received, in response to determining that the mobile terminal does not receive, within a preset time, a subsequent operation instruction entered by the user, or that a subsequent operation instruction entered by the user and received by the mobile terminal within the preset time is not an instruction to start the service.(String), 18.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收用户输入的与服务相关的操作指令;根据与服务相关的操作指令,提示用户输入后续操作指令;确定移动终端接收到后续启动服务的操作指令;和在确定移动终端接收到后续操作指令后,将后续操作指令启动服务作为启动命令。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 18. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive an operation instruction relevant to the service and entered by a user;prompt, according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction;determine that the mobile terminal receives a subsequent operation instruction to start the service; anduse the subsequent operation instruction to start the service as the start command after determining that the mobile terminal receives the subsequent operation instruction.(String), 19.移动终端,包括:处理器;和一种非暂时性计算机可读存储介质,存储由处理器执行的程序,该程序包括以下指令:获取相关信息,其中,所述相关信息包括从以下组中选择的信息:与移动终端相关的环境信息、移动终端的相关参数和移动终端当前的工作模式;根据相关信息确定保持启用的天线数量;和控制移动终端启用的天线数量为确定保持启用的天线数量。(String), 1(Integer), 17(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 19. A mobile terminal, comprising:a processor; anda non-transitory computer readable storage medium storing a program for execution by the processor, the program including instructions to:acquire relevant information, wherein the relevant information comprises information selecting from the group consisting of: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal;determine, according to the relevant information, a quantity of antennas to remain enabled; andcontrol a quantity of enabled antennas of the mobile terminal to be the quantity of antennas determined to remain enabled.(String), 20.根据权利要求19所述的移动终端,其中该说明还包括以下说明:将相关信息与预设条件进行比较,判断相关信息是否满足预设条件;其中,所述预设条件为响应于所述相关信息为与所述移动终端相关的环境信息,且所述环境信息为所述移动终端辐射范围内的用户而预设的生物信息;其中,预设条件为响应于环境信息为移动终端所在场景而预设的限制场景;其中,预设条件大于预设辐射阈值响应于相关信息为移动终端的相关参数,相关参数为移动终端的辐射强度;其中,预设条件小于预设信号阈值响应于相关参数为移动终端的信号强度;和其中,预设条件为响应于相关参数为移动终端的当前工作模式而预设的工作模式。(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 20. The mobile terminal according to claim 19, wherein the instructions further comprise instructions to:compare the relevant information with a preset condition, and determine whether the relevant information meets the preset condition;wherein the preset condition is preset biological information in response to the relevant information being the environment information relevant to the mobile terminal, and the environment information being a user within radiation of the mobile terminal;wherein the preset condition is a preset limitation scenario in response to the environment information being a scenario in which the mobile terminal is located;wherein the preset condition is greater than a preset radiation threshold in response to the relevant information being the relevant parameter of the mobile terminal, and the relevant parameter being a radiant intensity of the mobile terminal;wherein the preset condition is less than a preset signal threshold in response to the relevant parameter being a signal strength of the mobile terminal; andwherein the preset condition is a preset work mode in response to the relevant parameter being the current work mode of the mobile terminal.(String), 21.根据权利要求20所述的移动终端,其中响应于环境信息为移动终端辐射范围内的用户,所述指令还包括:将第三方设备发送的用户特征与预设生物信息进行比对,或解析用户输入的操作指令或获取的用户信息,获取用户特征,并将用户特征与预设的生物信息进行比对,其中,用户信息由用户输入或由第三方设备发送;判断用户特征是否符合预设生物信息;和根据相关信息,确定用户特征满足预设生物信息后保持开启的天线数量。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 21. The mobile terminal according to claim 20, wherein in response to the environment information being a user within radiation of the mobile terminal, the instructions further comprise instructions to:compare a user feature sent by a third-party device with the preset biological information, orparse an operation instruction entered by the user or acquired user information, to acquire a user feature, and compare the user feature with the preset biological information, wherein the user information is entered by the user or sent by a third-party device;determine whether the user feature meets the preset biological information; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the user feature meeting the preset biological information.(String), 22.根据权利要求20所述的移动终端,其中响应于环境信息为移动终端所在的场景,所述指令还包括:将场景信息与预设限制场景进行比较,判断场景信息是否满足预设限制场景,其中,场景信息由移动终端上的传感器或摄像头获取;和根据相关信息,确定满足预设限制场景的场景信息中保持启用的天线数量。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 22. The mobile terminal according to claim 20, wherein in response to the environment information being the scenario in which the mobile terminal is located, the instructions further comprise instructions to:compare scenario information with the preset limitation scenario, and determine whether the scenario information meets the preset limitation scenario, wherein the scenario information is acquired by a sensor or a camera on the mobile terminal; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the scenario information meeting the preset limitation scenario.(String), 23.根据权利要求20所述的移动终端:其中响应于相关参数为移动终端的辐射强度,所述指令还包括:将检测到的移动终端的辐射强度与预设辐射阈值进行比较,判断移动终端的辐射强度是否大于预设辐射阈值;和根据相关信息,确定响应于移动终端的辐射强度大于预设辐射阈值而保持开启的天线数量;和其中,响应于相关参数为移动终端的信号强度,所述指令还包括:将检测到的移动终端信号强度与预设信号门限值进行比较,判断移动终端信号强度是否小于预设信号门限值;和根据相关信息,确定响应于移动终端的辐射强度大于预设辐射阈值而保持开启的天线数量。(String), 1(Integer), 21(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 23. The mobile terminal according to claim 20:wherein in response to the relevant parameter being the radiant intensity of the mobile terminal, the instructions further comprise instructions to:compare a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determine whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold; andwherein in response to the relevant parameter being the signal strength of the mobile terminal, the instructions further comprise instructions to:compare a detected signal strength of the mobile terminal with the preset signal threshold, and determine whether the signal strength of the mobile terminal is less than the preset signal threshold; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold.(String), 24.根据权利要求20所述的移动终端,其中响应于相关参数为移动终端当前的工作模式,所述指令还包括:将移动终端当前工作模式与当前工作模式进行比较,判断当前工作模式是否满足预设工作模式,其中当前工作模式由用户设置,或者当前工作模式由移动终端设置响应于移动终端检测到移动终端的剩余电量低于预设电量阈值;和根据相关信息,确定移动终端当前工作模式满足预设工作模式时保持开启的天线数量。(String), 1(Integer), 22(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185008(Integer), 24. The mobile terminal according to claim 20, wherein in response to the relevant parameter being the current work mode of the mobile terminal, the instructions further comprise instructions to:compare the current work mode of the mobile terminal with the current work mode, and determine whether the current work mode meets the preset work mode, wherein the current work mode is set by the user, or the current work mode is set by the mobile terminal in response to the mobile terminal detecting that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the current work mode of the mobile terminal meeting the preset work mode.(String), 1(Integer), 23(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:55.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185008(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2015/073496, filed on Mar. 2, 2015, which claims priority to Chinese Patent Application No. 201410307645.X, filed on Jun. 30, 2014. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present embodiments relate to the field of communications technologies, and in particular, to a control method for a mobile terminal antenna, and a mobile terminal. BACKGROUND [0003]In second generation (2G) and third generation (3G) technologies, one antenna is configured for a mobile terminal, while in fourth generation (4G) LTE (Long Term Evolution), two antennas are configured for a mobile terminal. Further, in LTE-Advanced, as many as four antennas may be configured for a mobile terminal. With development and evolution of communications technologies, eight or even more antennas, for example, 12 antennas or 16 antennas, may be configured for a mobile terminal in the future. In an MIMO (Multiple Input Multiple Output) technology, an increase in a quantity of antennas of a mobile terminal may improve a transmission capacity and a transmission rate. However, more antennas also increase calculation complexity of communication between the terminal and a communications network element, further leading to higher power consumption. [0004]Specifically, some tasks, services, or the like that are executed on the mobile terminal do not need participation of many antennas, for example, only two antennas need to be enabled to normally execute a session service. In this case, if four antennas on the mobile terminal are enabled, it causes excessively high power consumption of the mobile terminal. Especially, in the case of the mobile terminal, which is an electronic device that relies on a battery for power supply, enabling an unnecessary antenna wastes electricity of the battery, and affects use by a user. SUMMARY [0005]Embodiments provide a control method for a mobile terminal antenna, and a mobile terminal, which are used to properly control a quantity of disabled or enabled antennas of the mobile terminal. [0006]According to a first aspect, an embodiment provides a control method for a mobile terminal antenna, including acquiring, by a mobile terminal, a start command of a service and determining, by the mobile terminal according to the start command, a quantity of antennas that need to be enabled for the service. The control method also includes controlling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0007]With reference to the first aspect, in a first implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, a service signal of the service, where the service signal is the start command. [0008]With reference to the first implementation manner of the first aspect, in a second implementation manner, the method further includes: prompting, by the mobile terminal, a user whether to start the service; and if the mobile terminal does not receive, within a preset time, an operation instruction entered by the user, or the mobile terminal determines that an operation instruction entered by the user and received within the preset time is not an instruction to start the service, controlling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0009]With reference to the first aspect, in a third implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, a service signal of the service; prompting, by the mobile terminal, a user whether to start the service; receiving, by the mobile terminal, an operation instruction entered by the user; and if the mobile terminal determines that the operation instruction is an instruction to start the service, using the operation instruction as the start command. [0010]With reference to the first aspect, in a fourth implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, an operation instruction relevant to the service and entered by the user, where the operation instruction relevant to the service is the start command. [0011]With reference to the fourth implementation manner of the first aspect, in a fifth implementation manner, the method further includes: prompting, by the mobile terminal, the user to enter a subsequent operation instruction; and if the mobile terminal does not receive, within a preset time, the subsequent operation instruction entered by the user, or the mobile terminal determines that a subsequent operation instruction received within the preset time is not an instruction to start the service, controlling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0012]With reference to the first aspect, in a sixth implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, an operation instruction relevant to the service and entered by a user; prompting, by the mobile terminal according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction; and receiving, by the mobile terminal, a subsequent operation instruction to start the service, and then using the subsequent operation instruction to start the service as the start command. [0013]With reference to any implementation manner of the first aspect to the sixth implementation manner of the first aspect, in a seventh implementation manner, the control method further includes: receiving, by the mobile terminal, information for terminating the service; and terminating, by the mobile terminal, the service, and controlling the quantity of enabled antennas of the mobile terminal to revert to a quantity before the start command is received. [0014]According to a second aspect, an embodiment provides a control method for a mobile terminal antenna, including acquiring, by a mobile terminal, relevant information, where the relevant information is at least any of the following information: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal. The control method also includes determining, by the mobile terminal according to the relevant information, a quantity of antennas that should remain enabled and controlling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal to be the quantity of antennas corresponding to the relevant information. [0015]With reference to the second aspect, in a first implementation manner, before the determining, by the mobile terminal according to the relevant information, a quantity of antennas that should remain enabled, the control method further includes: comparing, by the mobile terminal, the relevant information with a preset condition, and determining whether the relevant information meets the preset condition, where when the relevant information is the environment information relevant to the terminal, and the environment information is a user within radiation of the mobile terminal, the preset condition is preset biological information; when the environment information is a scenario in which the mobile terminal is located, the preset condition is a preset limitation scenario; when the relevant information is the relevant parameter of the terminal, and the relevant parameter is a radiant intensity of the mobile terminal, the preset condition is being greater than a preset radiation threshold; when the relevant parameter is a signal strength of the mobile terminal, the preset condition is being less than a preset signal threshold; and when the relevant parameter is the current work mode of the mobile terminal, the preset condition is a preset work mode. [0016]With reference to the first implementation manner of the second aspect, in a second implementation manner, when the environment information is the user within the radiation of the mobile terminal, the control method further includes: comparing, by the mobile terminal, a user feature sent by a third-party device with the preset biological information, and determining whether the user feature sent by the third-party device meets the preset biological information; or, parsing, by the mobile terminal, an operation instruction entered by the user or acquired user information, to acquire a user feature; and comparing, by the mobile terminal, the user feature with the preset biological information, and determining whether the user feature meets the preset biological information, where the user information is entered by the user or sent by a third-party device; and if the user feature meets the preset biological information, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. [0017]With reference to the first implementation manner of the second aspect, in a third implementation manner, when the environment information is the scenario in which the mobile terminal is located, the control method includes: comparing, by the mobile terminal, scenario information with the preset limitation scenario, and determining whether the scenario information meets the preset limitation scenario, where the scenario information is acquired by using a sensor or a camera on the mobile terminal; and if the scenario information meets the preset limitation scenario, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. [0018]With reference to the first implementation manner of the second aspect, in a fourth implementation manner, when the relevant parameter is the radiant intensity of the mobile terminal, the control method further includes: comparing, by the mobile terminal, a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determining whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled; and when the relevant parameter is the signal strength of the mobile terminal, the control method further includes: comparing, by the mobile terminal, a detected signal strength of the mobile terminal with the preset signal threshold, and determining whether the signal strength of the mobile terminal is less than the preset signal threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. With reference to the first implementation manner of the second aspect, in a fifth implementation manner, the relevant parameter is the current work mode of the mobile terminal, and the control method further includes: comparing, by the mobile terminal, the current work mode of the mobile terminal with the work mode, and determining whether the current work mode meets the preset work mode, where the current work mode is set by the user, or is set by the mobile terminal when the mobile terminal detects that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; and if the current work mode of the mobile terminal meets the preset work mode, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. [0019]According to a third aspect, an embodiment provides a mobile terminal, including: an acquiring module, configured to acquire a start command of a service; a determining module, configured to determine, according to the start command, a quantity of antennas that need to be enabled for the service; and a processing module, configured to control a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0020]With reference to the third aspect, in a first implementation manner, the acquiring module is specifically configured to receive a service signal of the service, where the service signal is the start command. [0021]With reference to the first implementation manner of the third aspect, in a second implementation manner, the mobile terminal further includes a prompting module and a judging module, where the prompting module is configured to prompting a user whether to start the service; and if the judging module determines that the acquiring module does not receive, within a preset time, an operation instruction entered by the user, or the judging module determines that an operation instruction entered by the user and received by the acquiring module within the preset time is not an instruction to start the service, the processing module controls the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0022]With reference to the third aspect, in a third implementation manner, the mobile terminal further includes a prompting module and a judging module, where the acquiring module is further configured to receive a service signal of the service; the prompting module is configured to prompting a user whether to start the service; and the acquiring module is configured to receive an operation instruction entered by the user; and the judging module is configured to determine that the operation instruction is an instruction to start the service, and then the acquiring module is specifically configured to use the operation instruction as the start command. [0023]With reference to the third aspect, in a fourth implementation manner, the acquiring module is specifically configured to receive an operation instruction relevant to the service and entered by the user, where the operation instruction relevant to the service is the start command. [0024]With reference to the fourth implementation manner of the third aspect, in a fifth implementation manner, the mobile terminal further includes a prompting module and a judging module, where the prompting module is configured to prompt the user to enter a subsequent operation instruction; and if the judging module determines that the acquiring module does not receive, within a preset time, a subsequent operation instruction entered by the user, or the judging module determines that a subsequent operation instruction entered by the user and received by the acquiring module within the preset time is not an instruction to start the service, the processing module is configured to control the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0025]With reference to the third aspect, in a sixth implementation manner, the mobile terminal further includes a prompting module and a judging module, where the acquiring module receives an operation instruction relevant to the service and entered by a user; the prompting module prompts, according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction; and the judging module determines that the acquiring module receives a subsequent operation instruction to start the service, and then the acquiring module uses the subsequent operation instruction to start the service as the start command. [0026]With reference to any implementation manner of the third aspect to the sixth implementation manner of the third aspect, in a seventh implementation manner, the acquiring module is further configured to receive information for terminating the service; and the processing module terminates the service, and controls the quantity of enabled antennas of the mobile terminal to revert to a quantity before the start command is received. [0027]According to a fourth aspect, an embodiment provides a mobile terminal, including: an acquiring module, configured to acquire relevant information, where the relevant information is at least any of the following information: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal; a determining module, configured to determine, according to the relevant information, a quantity of antennas that should remain enabled; and a processing module, configured to control a quantity of enabled antennas of the mobile terminal to be the quantity of antennas corresponding to the relevant information. [0028]With reference to the fourth aspect, in a first implementation manner, the determining module is further configured to compare the relevant information with a preset condition, and determine whether the relevant information meets the preset condition, where when the relevant information is the environment information relevant to the terminal, and the environment information is a user within radiation of the mobile terminal, the preset condition is preset biological information; when the environment information is a scenario in which the mobile terminal is located, the preset condition is a preset limitation scenario; when the relevant information is the relevant parameter of the terminal, and the relevant parameter is a radiant intensity of the mobile terminal, the preset condition is being greater than a preset radiation threshold; when the relevant parameter is a signal strength of the mobile terminal, the preset condition is being less than a preset signal threshold; and when the relevant parameter is the current work mode of the mobile terminal, the preset condition is a preset work mode. [0029]With reference to the first implementation manner of the fourth aspect, in a second implementation manner, the environment information is a user within radiation of the mobile terminal, and then the determining module is specifically configured to compare a user feature sent by a third-party device with the preset biological information, and determine whether the user feature sent by the third-party device meets the preset biological information; or, the acquiring module is further configured to parse an operation instruction entered by the user or acquired user information, to acquire a user feature; and the determining module is further configured to compare the user feature with the preset biological information, and determine whether the user feature meets the preset biological information, where the user information is entered by the user or sent by a third-party device; and if the user feature meets the preset biological information, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0030]With reference to the first implementation manner of the fourth aspect, in a third implementation manner, when the environment information is the scenario in which the mobile terminal is located, and the determining module is specifically configured to compare scenario information with the preset limitation scenario, and determine whether the scenario information meets the preset limitation scenario, where the scenario information is acquired by using a sensor or a camera on the mobile terminal; and if the scenario information meets the preset limitation scenario, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0031]With reference to the first implementation manner of the fourth aspect, in a fourth implementation manner, when the relevant parameter is the radiant intensity of the mobile terminal, the determining module is specifically configured to compare a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determine whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled; when the relevant parameter is the signal strength of the mobile terminal, the determining module is specifically configured to compare a detected signal strength of the mobile terminal with the preset signal threshold, and determine whether the signal strength of the mobile terminal is less than the preset signal threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0032]With reference to the first implementation manner of the fourth aspect, in a fifth implementation manner, when the relevant parameter is the current work mode of the mobile terminal, the determining module compares the current work mode of the mobile terminal with the work mode, and determines whether the current work mode meets the preset work mode, where the current work mode is set by the user, or is set by the mobile terminal when the mobile terminal detects that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; and if the current work mode of the mobile terminal meets the preset work mode, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0033]By means of the control method for a mobile terminal antenna and the mobile terminal that are provided in the embodiments, when a start command or relevant information of a service is received, a quantity of antennas that the mobile terminal should enable is determined, and a quantity of enabled antennas on the mobile terminal is flexibly changed, thereby preventing that the quantity of enabled antennas on the mobile terminal cannot meet a requirement for executing the service, and also preventing that the quantity of enabled antennas on the mobile terminal is excessive, which causes unnecessary energy loss; moreover, it can further prevent the quantity of enabled antennas on the mobile terminal from causing harmful impact on surroundings, or consuming electricity of the mobile terminal excessively fast and affecting performance of the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0034]FIG. 1 is a schematic diagram of an application scenario according to an embodiment; [0035]FIG. 2 is a flowchart of Embodiment 1 of a control method for a mobile terminal antenna according to the embodiments; [0036]FIG. 3 is a flowchart of Embodiment 2 of a control method for a mobile terminal antenna according to the present embodiments; [0037]FIG. 4 is a flowchart of Embodiment 3 of a control method for a mobile terminal antenna according to the present embodiments; [0038]FIG. 5 is a flowchart of Embodiment 4 of a control method for a mobile terminal antenna according to the present embodiments; [0039]FIG. 6 is a flowchart of Embodiment 5 of a control method for a mobile terminal antenna according to the present embodiments; [0040]FIG. 7 is a flowchart of Embodiment 6 of a control method for a mobile terminal antenna according to the present embodiments; [0041]FIG. 8 is a flowchart of Embodiment 7 of a control method for a mobile terminal antenna according to the present embodiments; [0042]FIG. 9 is a structural diagram of Embodiment 1 of a mobile terminal according to the present embodiments; [0043]FIG. 10 is a structural diagram of Embodiment 2 of a mobile terminal according to the present embodiments; [0044]FIG. 11 is a structural diagram of Embodiment 3 of a mobile terminal according to the present embodiments; and [0045]FIG. 12 is a structural diagram of Embodiment 4 of a mobile terminal according to the present embodiments. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0046]To make the objectives, technical solutions, and advantages of the embodiments clearer, the following clearly describes the technical solutions in the embodiments with reference to the accompanying drawings in the embodiments. Apparently, the described embodiments are some but not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments without creative efforts shall fall within the protection scope of the present embodiments. [0047]FIG. 1 is a schematic diagram of an application scenario according to an embodiment. As shown in FIG. 1, this embodiment is applied to a communications network on which technologies such as fourth generation long term evolution (4G LTE), LTE-Advanced, and multiple-input multiple-output (MIMO) are used, and a quantity of antennas that are generally disposed on a mobile terminal (such as a mobile phone or a tablet) is at least 2. Accordingly, multiple antennas are set on a network element (such as a base station) that provides a communications service for the mobile terminal. For example, N antennas are disposed on the mobile terminal, where N is a positive integer not less than 2, and M antennas are disposed on the base station, where M is a positive integer not less than 2, and in this case, the mobile terminal on the communications network can communicate, by using the N antennas, with the M antennas of the base station, to transmit a data stream. It may be understood that, when the mobile terminal executes some services, service requirements can be met by enabling only one antenna; although to use multiple antennas can improve communications performance by some degree, multiple antennas participating in communication increases complexity of the communication, causes high power consumption of the mobile terminal, and brings inconvenience to a user when the user uses the mobile terminal, or in some cases, the mobile terminal enables multiple antennas, and therefore causes excessive radiation to people or devices near the mobile terminal. Therefore, the mobile terminal needs to properly control a quantity of enabled antennas on the mobile terminal, and a specific control manner is as follows: [0048]FIG. 2 is a flowchart of Embodiment 1 of a control method for a mobile terminal antenna according to the present embodiments. As shown in FIG. 2, reference may be made to FIG. 1, and this embodiment is executed by a mobile terminal, where the mobile terminal is specifically a mobile phone, a tablet, or the like. The control method specifically includes. [0049]S101: A mobile terminal acquires a start command of a service. [0050]The start command may be a service signal of the service, for example, if a user using a mobile terminal has subscribed to a video push service, a video server periodically sends video content to the mobile terminal; and in this case, when the mobile terminal receives a video stream signal, the video stream signal is a service signal used as the start command. [0051]Alternatively, the start command may be an operation instruction entered by a user, where the operation instruction is used to instruct the mobile terminal to execute the service, for example, if the user taps a “Radio” icon on a display of the mobile terminal, the start command of the service received by the mobile terminal is an operation instruction “start a radio service”. [0052]S102: The mobile terminal determines, according to the start command, a quantity of antennas that need to be enabled for the service. [0053]The mobile terminal learns about, according to the start command, a specific service to be executed at present, and thereby can determine a quantity of antennas that are needed by the service to be started. For example, the mobile terminal enables 4 antennas at a current moment, but at this time, an incoming call paging message is received, and in this case, the mobile terminal determines that the service to be executed is a session service; the mobile terminal determines, according to settings of a network or a capability of the mobile terminal, that 1 (when the mobile terminal is on a 2G network) or 2 (when the mobile terminal is on an LTE network) antennas need to be enabled to meet a requirement of the session service; and then unnecessary enabled antennas may be disabled, that is, the following S103 is further performed. [0054]S103: The mobile terminal controls a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0055]It should be additionally noted that, when or after S103 is performed, the mobile terminal begins to execute the service, and subsequently, when the mobile terminal receives information for terminating the service, the mobile terminal terminates the service, and controls the quantity of enabled antennas of the mobile terminal to revert to a quantity before the start command is received. [0056]In this embodiment, a mobile terminal determines, according to a received start command of a service, a quantity of antennas that need to be enabled for the service, and flexibly changes a quantity of enabled antennas on the mobile terminal, thereby preventing that the quantity of enabled antennas on the mobile terminal cannot meet a requirement for executing the service, and also preventing that the quantity of enabled antennas on the mobile terminal is excessive, which causes unnecessary energy loss and affects performance of the mobile terminal. [0057]FIG. 3 is a flowchart of Embodiment 2 of a control method for a mobile terminal antenna according to the present embodiments. As shown in FIG. 3, in this embodiment, a start command of a service is a service signal of the service, and in this case, a specific process is as follows: [0058]S201: A mobile terminal receives a service signal of a service. [0059]S202: The mobile terminal determines, according to the service signal of the service, a quantity of antennas that need to be enabled for the service. [0060]Description is made by using an example in which an incoming call paging message in a session service is used as the service signal. When the mobile terminal receives the incoming call paging message, the mobile terminal learns that the session service is about to be executed, and currently the mobile terminal camps on a second generation (2G) network; in this case, the mobile terminal can meet a requirement of the session service by enabling only 1 antenna, and therefore, the mobile terminal determines, by using S202, to enable 1 antenna; and if the mobile terminal camps on an LTE network, and corresponding to the LTE network, the mobile terminal can meet the requirement of the session service by enabling only 2 antennas, and therefore, the mobile terminal determines, by using S202, to enable 2 antennas. [0061]S203: The mobile terminal controls a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0062]For example, the mobile terminal enables 4 antennas at a current moment, but determines, by using S202, that the quantity of antennas that need to be enabled is 2, and then in S203, the mobile terminal disables 2 antennas, to retain 2 enabled antennas. [0063]It may be understood that, if the service signal is a video stream signal sent by a video server to the mobile terminal according to a push service that the mobile terminal subscribes to, the mobile terminal enables, by using S201 to S203, antennas needed by a video service, and then the mobile terminal directly receives and plays a video stream, that is, directly executes the service; and the following S204 to S209 may not be performed. However, to improve user experience, the mobile terminal prompts a user whether to start the service; for example, if the service signal is an incoming call paging message, the mobile terminal displays options such as “Answer” and “Reject” on a display, to prompting the user whether to start the session service, that is, in this embodiment, the following S204 to S209 still need to be performed: [0064]S20(String), 相关申请的交叉引用 [0001] 本申请是2015年3月2日提交的国际申请No.PCT / CN2015 / 073496的延续,其要求2014年6月30日提交的中国专利申请No.201410307645.X的优先权。 这些申请在此全文引入作为参考。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种移动终端天线的控制方法及移动终端。 背景 [0003] 在第二代(2G)和第三代(3G)技术中,一个天线被配置用于移动终端,而在第四代(4G)LTE(长期演进)中,两个天线被配置用于移动终端。 此外,在高级LTE中,可以为移动终端配置多达四个天线。 随着通信技术的发展和演进,将来可以为移动终端配置八个或更多个天线,例如12个天线或16个天线。 在MIMO(多输入多输出)技术中,移动终端的天线数量的增加可以提高传输容量和传输速率。 然而,更多的天线也增加了终端与通信网络元件之间的通信的计算复杂度,进一步导致更高的功耗。 [0004] 具体地,在移动终端上执行的某些任务,服务等不需要很多天线的参与,例如,仅需要启用两个天线即可正常执行会话服务。 在这种情况下,如果在移动终端上启用了四个天线,则会导致移动终端的功耗过高。 特别地,在移动终端是依靠电池供电的电子设备的情况下,启用不必要的天线会浪费电池的电,并影响用户的使用。 概要 [0005] 实施例提供了用于移动终端天线的控制方法和移动终端,其用于适当地控制移动终端的禁用或启用的天线的数量。 [0006] 根据第一方面,实施例提供了一种用于移动终端天线的控制方法,包括:由移动终端获取服务的开始命令,以及由移动终端根据该开始命令确定天线的数量。 需要启用该服务。 该控制方法还包括由移动终端将移动终端的启用的天线的数量控制为该服务需要启用的天线的数量。 [0007] 结合第一方面,在第一种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收所述服务的服务信号,所述服务信号为启动 命令。 [0008] 结合第一方面的第一种实现方式,在第二种实现方式中,该方法还包括:移动终端提示用户是否启动服务; 如果移动终端在预设时间内没有接收到用户输入的操作指令,或者移动终端确定用户输入并在预设时间内接收到的操作指令不是启动服务的指令, 由移动终端控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0009] 结合第一方面,在第三种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收所述服务的服务信号; 所述移动终端提示用户是否启动所述服务; 所述移动终端接收用户输入的操作指令; 如果移动终端确定该操作指令为启动服务的指令,则将该操作指令作为启动指令。 [0010] 结合第一方面,在第四种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收用户输入的与所述服务相关的操作指令, 与服务相关的操作指令是启动命令。 [0011] 结合第一方面的第四种实施方式,在第五种实施方式中,所述方法还包括:移动终端提示用户输入后续的操作指令; 如果移动终端在预设时间内没有接收到用户输入的后续操作指令,或者移动终端确定在预设时间内接收到的后续操作指令不是启动服务的指令, 在移动终端中,移动终端的启用天线的数量恢复为在接收服务信号之前的数量。 [0012] 结合第一方面,在第六种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收用户输入的与所述服务相关的操作指令; 所述移动终端根据所述业务相关的操作指令提示用户输入后续的操作指令; 所述移动终端接收后续的操作指令以启动所述服务,然后使用所述后续的操作指令以启动所述服务作为所述启动命令。 [0013] 结合第一方面的第一实施方式至第一方面的第六实施方式中的任意一种,在第七实施方式中,所述控制方法还包括:所述移动终端接收用于终止服务的信息; 所述移动终端终止所述服务,并控制所述移动终端的使能天线数量恢复为接收到所述启动命令之前的数量。 [0014] 根据第二方面,实施例提供了一种用于移动终端天线的控制方法,包括:由移动终端获取相关信息,其中,所述相关信息是以下信息中的至少任何一种:与所述移动终端相关的环境信息; 移动终端的相关参数以及移动终端的当前工作模式。 该控制方法还包括:由移动终端根据相关信息确定应保持启用的天线的数量;以及由移动终端将移动终端的启用的天线的数量控制为与之对应的天线的数量。 相关信息。 [0015] 结合第二方面,在第一种实现方式中,在所述移动终端根据所述相关信息确定需要保持启用的天线数量之前,所述控制方法还包括:所述移动终端比较所述 具有预设条件的相关信息,并确定所述相关信息是否满足所述预设条件,当所述相关信息为与所述终端相关的环境信息,所述环境信息为所述移动终端辐射范围内的用户时,所述预设条件为 预设生物学信息; 当环境信息为移动终端所处的场景时,预设条件为预设限制场景; 当相关信息为终端的相关参数,且相关参数为移动终端的辐射强度时,预设条件大于预设辐射阈值; 当相关参数为移动终端的信号强度时,所述预设条件小于预设信号阈值; 当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0016] 结合第二方面的第一种实现方式,在第二种实现方式中,当所述环境信息为所述移动终端辐射范围内的用户时,所述控制方法还包括:所述移动终端比较发送的用户特征 第三方设备获取预设的生物信息,并确定第三方设备发送的用户特征是否满足预设的生物信息; 或者,移动终端解析用户输入的操作指令或获取的用户信息,获取用户特征; 所述移动终端将所述用户特征与所述预设生物信息进行比较,确定所述用户特征是否满足所述预设生物信息,所述用户信息由用户输入或由第三方设备发送; 如果用户特征满足预设的生物信息,则移动终端根据相关信息确定应保持启用的天线数量。 [0017] 结合第二方面的第一种实现方式,在第三种实现方式中,当所述环境信息为所述移动终端所在的场景时,所述控制方法包括:所述移动终端将所述场景信息与所述预设信息进行比较。 限制场景,并确定所述场景信息是否满足预设的限制场景,所述场景信息是通过移动终端上的传感器或摄像头获取的; 如果所述场景信息满足所述预设的限制场景,则所述移动终端根据所述相关信息确定应保持启用的天线数量。 [0018] 结合第二方面的第一种实现方式,在第四种实现方式中,当所述相关参数为所述移动终端的辐射强度时,所述控制方法还包括:所述移动终端比较检测到的所述移动终端的辐射强度。 具有预设的辐射阈值的移动终端,并确定所述移动终端的辐射强度是否大于预设的辐射阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则移动终端根据相关信息确定应保持启用的天线数量; 当所述相关参数为所述移动终端的信号强度时,所述控制方法还包括:所述移动终端将检测到的所述移动终端的信号强度与所述预设信号阈值进行比较,并确定所述移动终端的信号强度 终端小于预设信号阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则由移动终端根据相关信息确定应保持启用的天线数量。 结合第二方面的第一种实现方式,在第五种实现方式中,所述相关参数为所述移动终端的当前工作模式,所述控制方法还包括:所述移动终端比较所述移动终端当前的工作模式。 具有工作模式的移动终端,并确定当前工作模式是否满足预设工作模式,即当前工作模式由用户设置,还是当移动终端检测到剩余电量时由移动终端设置 所述移动终端低于预设电量阈值; 如果移动终端当前的工作模式满足预设的工作模式,则移动终端根据相关信息确定应保持启用的天线数量。 [0019] 根据第三方面,实施例提供了一种移动终端,包括:获取模块,用于获取服务的启动命令; 确定模块,用于根据启动命令,确定需要为该业务启用的天线数量; 处理模块,用于将所述移动终端的已启用天线的数量控制为所述业务需要启用的天线的数量。 [0020] 结合第三方面,在第一种实现方式中,所述获取模块,具体用于接收所述服务的服务信号,所述服务信号为所述启动命令。 [0021] 结合第三方面的第一种实现方式,在第二种实现方式中,所述移动终端还包括提示模块和判断模块,所述提示模块,用于提示用户是否启动所述服务; 判断模块确定获取模块在预设时间内没有收到用户输入的操作指令,或者判断模块确定用户输入并获取模块在预设时间内接收到的操作指令 如果不是开始服务的指令,则处理模块控制移动终端的已启用天线的数量以恢复到接收到服务信号之前的数量。 [0022] 结合第三方面,在第三种实施方式中,所述移动终端还包括提示模块和判断模块,所述获取模块,还用于接收所述服务的服务信号; 提示模块,用于提示用户是否启动服务; 获取模块,用于接收用户输入的操作指令; 所述判断模块,用于确定所述操作指令为启动服务的指令,所述获取模块,具体用于,将所述操作指令作为所述启动命令。 [0023] 结合第三方面,在第四种实现方式中,所述获取模块,用于接收用户输入的与所述服务有关的操作指令,其中,与所述服务有关的操作指令为启动命令。 [0024] 结合第三方面的第四种实施方式,在第五种实施方式中,所述移动终端还包括提示模块和判断模块,所述提示模块用于提示用户输入后续的操作指令; 判断模块确定获取模块在预设时间内没有接收到用户输入的后续操作指令,或者判断模块确定用户输入并由获取模块接收到的后续操作指令 预设时间不是开始服务的指令,处理模块被配置为控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0025] 结合第三方面,在第六种实现方式中,所述移动终端还包括提示模块和判断模块,所述获取模块接收与所述服务相关的用户输入的操作指令; 提示模块根据与服务有关的操作指令提示用户输入后续的操作指令; 判断模块确定获取模块接收到后续的操作指令以启动服务,然后获取模块使用后续的操作指令以启动服务作为启动命令。 [0026] 结合第三方面的任何实现方式至第三方面的第六种实现方式,在第七种实现方式中,所述获取模块,还用于接收用于终止服务的信息; 处理模块终止服务,控制移动终端的使能天线数量恢复到接收到启动命令之前的数量。 [0027] 根据第四方面,实施例提供了一种移动终端,包括:获取模块,用于获取相关信息,所述相关信息为以下至少信息:与所述移动终端相关的环境信息, 该移动终端,以及该移动终端的当前工作模式; 确定模块,用于根据相关信息,确定应保持启用状态的天线数量; 处理模块,用于将所述移动终端的启用天线的数量控制为与所述相关信息对应的天线的数量。 [0028] 结合第四方面,在第一实施方式中,所述确定模块,还用于将所述相关信息与预设条件进行比较,并确定所述相关信息是否满足所述预设条件; 所述环境信息为所述移动终端辐射范围内的用户,所述预设条件为预设生物信息; 当环境信息为移动终端所处的场景时,预设条件为预设限制场景; 当相关信息为终端的相关参数,且相关参数为移动终端的辐射强度时,预设条件大于预设辐射阈值; 当相关参数为移动终端的信号强度时,所述预设条件小于预设信号阈值; 当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0029] 结合第四方面的第一种实现方式,在第二种实现方式中,环境信息为移动终端辐射范围内的用户,则确定模块具体用于比较第三方发送的用户特征 具有所述预设生物信息的设备,并确定所述第三方设备发送的用户特征是否满足所述预设生物信息; 所述获取模块,还用于解析所述用户输入的操作指令或获取的用户信息,以获取用户特征; 所述确定模块,还用于将所述用户特征与所述预设生物信息进行比较,确定所述用户特征是否满足所述预设生物信息,所述用户信息由用户输入或由第三方设备发送; 如果所述用户特征满足所述预设的生物信息,则所述处理模块,用于根据所述相关信息,确定应保持启用的天线数量。 [0030] 结合第四方面的第一种实现方式,在第三种实现方式中,当所述环境信息为所述移动终端所处的场景时,所述确定模块具体用于将所述场景信息与所述预设的限制场景进行比较, 确定场景信息是否满足预设的限制场景,该场景信息是通过移动终端上的传感器或摄像头获取的; 如果所述场景信息满足所述预设的限制场景,则所述处理模块,用于根据所述相关信息,确定应保持启用的天线数量。 [0031] 结合第四方面的第一种实现方式,在第四种实现方式中,当所述相关参数为所述移动终端的辐射强度时,所述确定模块具体用于将检测到的所述移动终端的辐射强度与所述预设值进行比较 辐射阈值,并确定移动终端的辐射强度是否大于预设的辐射阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则处理模块,用于根据相关信息,确定应保持启用的天线数量; 当相关参数为移动终端的信号强度时,确定模块具体用于将检测到的移动终端的信号强度与预设的信号阈值进行比较,判断移动终端的信号强度是否小于预设的 信号阈值 如果所述移动终端的辐射强度大于所述预设的辐射阈值,则所述处理模块,用于根据所述相关信息,确定应保持启用的天线数量。 [0032] 结合第四方面的第一种实现方式,在第五种实现方式中,当所述相关参数为所述移动终端的当前工作模式时,所述确定模块将所述移动终端的当前工作模式与所述工作模式进行比较, 确定当前工作模式是否满足用户设置的当前工作模式或当前工作模式是否满足预设工作模式,或者当移动终端检测到剩余电量低于预设电量时,由移动终端设置 数量阈值 如果移动终端当前的工作模式满足预设的工作模式,则处理模块,用于根据相关信息,确定应保持启用的天线数量。 [0033] 通过实施例中提供的移动终端天线的控制方法和移动终端,当接收到启动命令或服务的相关信息时,确定移动终端应启用的天线数量, 可以灵活地改变移动终端上启用天线的数量,从而防止移动终端上启用天线的数量不能满足执行业务的需求,还可以防止移动终端上启用天线的数量过多, 造成不必要的能量损失; 此外,它还可以防止移动终端上启用的天线数量对周围环境造成有害影响,或者过快地消耗移动终端的电力并影响移动终端的性能。 附图的简要说明 [0034] 图。 图1是根据一个实施例的应用场景的示意图; [0035] 图。 图2是根据实施例的用于移动终端天线的控制方法的实施例1的流程图; [0036] 图。 图3是本实施方式的移动终端天线的控制方法的实施方式2的流程图。 [0037] 图。 图4是本实施方式的移动终端天线的控制方法的实施方式3的流程图。 [0038] 图。 图5是本实施方式的移动终端天线的控制方法的实施方式4的流程图。 [0039] 图。 图6是本实施方式的移动终端天线的控制方法的实施方式5的流程图。 [0040] 图。 图7是本实施方式的移动终端天线的控制方法的实施方式6的流程图。 [0041] 图。 图8是本实施方式的移动终端天线的控制方法的实施方式7的流程图。 [0042] 图。 图9是本实施方式的移动终端的实施方式1的结构图。 [0043] 图。 图10是本实施方式的移动终端的实施方式2的结构图。 [0044] 图。 图11是本实施方式的移动终端的实施方式3的结构图。 和 [0045] 图。 图12是根据本实施例的移动终端的实施例四的结构图。 具体实施方式 [0046] 为了使实施例的目的,技术方案和优点更加清楚,下面结合实施例中的附图,对实施例中的技术方案进行清楚地描述。 显然,所描述的实施例是一些但不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0047] 图。 图1是根据一个实施例的应用场景的示意图。 如图1所示。 参照图1,该实施例被应用于使用诸如第四代长期演进(4G LTE),LTE-Advanced和多输入多输出(MIMO)的技术以及通常使用的天线数量的通信网络。 设置在移动终端(例如,移动电话或平板电脑)上的至少2个。因此,在为移动终端提供通信服务的网络元件(例如,基站)上设置了多个天线。 例如,在移动终端上设置N个天线,其中N为不小于2的正整数,在基站上设置M个天线,其中M为不小于2的正整数,在这种情况下, 通信网络上的移动终端可以通过使用N个天线与基站的M个天线进行通信,以传输数据流。 可以理解的是,当移动终端执行某些服务时,仅启用一根天线就可以满足服务需求。 尽管使用多个天线可以在某种程度上改善通信性能,但是参与通信的多个天线增加了通信的复杂性,导致移动终端的功耗高,并且在用户使用移动终端时或在某些情况下给用户带来不便 在这种情况下,移动终端启用多个天线,因此对移动终端附近的人或设备造成过多的辐射。 因此,移动终端需要适当控制移动终端上启用的天线数量,具体控制方式如下: [0048] 图。 图2是根据本实施例的用于移动终端天线的控制方法的实施例1的流程图。 如图1所示。 参考图2,可以参考图1。 如图1所示,本实施例由移动终端执行,其中,移动终端具体为手机,平板电脑等。 该控制方法具体包括。 [0049] 小号 101 :移动终端获取服务的启动命令。 [0050] 该开始命令可以是该服务的服务信号,例如,如果使用移动终端的用户已经订阅了视频推送服务,则视频服务器周期性地向移动终端发送视频内容; 在这种情况下,当移动终端接收到视频流信号时,该视频流信号是用作开始命令的服务信号。 [0051] 替代地,开始命令可以是用户输入的操作指令,其中该操作指令用于指示移动终端执行服务,例如,如果用户点击了移动终端的显示器上的“无线电”图标。 移动终端接收到的服务的启动命令为操作指令“启动无线服务”。 [0052] 小号 102 :移动终端根据启动命令确定需要为该服务启用的天线数量。 [0053] 移动终端根据启动命令了解当前要执行的特定服务,从而可以确定要启动的服务所需的天线数量。 例如,移动终端在当前时刻启用了四个天线,但是此时,接收到呼入寻呼消息,在这种情况下,移动终端确定要执行的服务是会话服务; 移动终端根据网络的设置或移动终端的能力确定需要启用1根(当移动终端在2G网络上时)或2根(当移动终端在LTE网络上时)天线。 满足会话服务的要求; 然后可能会禁用不必要的启用天线,即以下S 103 进一步执行。 [0054] 小号 103 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0055] 还应注意,在S时或之后 103 执行该操作时,移动终端开始执行服务,随后,当移动终端接收到终止服务的信息时,移动终端终止服务,并控制移动终端的启用天线的数量恢复到之前的数量。 收到启动命令。 [0056] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0057] 图。 图3是根据本实施例的用于移动终端天线的控制方法的实施例2的流程图。 如图1所示。 如图3所示,在本实施例中,服务的启动命令是该服务的服务信号,在这种情况下,具体过程如下: [0058] 小号 201 :移动终端接收服务的服务信号。 [0059] 小号 202 :移动终端根据该服务的服务信号,确定该服务需要启用的天线数量。 [0060] 通过使用将会话服务中的呼入寻呼消息用作服务信号的示例进行描述。 当移动终端接收到呼入寻呼消息时,得知该会话服务即将被执行,当前该移动终端预占第二代(2G)网络。 在这种情况下,移动终端仅启用1个天线就可以满足会话服务的要求,因此,移动终端通过使用S来确定 202 ,启用1根天线; 如果移动终端驻留在LTE网络上并且对应于LTE网络,则移动终端仅启用2个天线就可以满足会话服务的需求,因此,移动终端通过使用S确定 202 ,以启用2根天线。 [0061] 小号 203 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0062] 例如,移动终端在当前时刻启用4个天线,但通过使用S来确定 202 ,则需要启用的天线数量为2,然后为S 203 ,移动终端禁用2根天线,以保留2根启用的天线。 [0063] 可以理解,如果服务信号是视频服务器根据移动终端订阅的推送服务发送给移动终端的视频流信号,则移动终端通过使用S 201 到S 203 视频服务所需的天线,然后移动终端直接接收并播放视频流,即直接执行该服务; 和以下的S 204 到S 209 可能无法执行。 然而,为了改善用户体验,移动终端提示用户是否启动服务。 例如,如果业务信号为呼入寻呼消息,则移动终端在显示屏上显示诸如“应答”和“拒绝”的选项,以提示用户是否开始会话服务,即,在本实施例中, 以下的S 204 到S 209 仍然需要执行: [0064] 小号 204 :移动终端提示用户是否启动该服务。 [0065] 小号 205 :移动终端确定是否在预设时间内接收到用户输入的操作指令,如果是,则执行S 206 ; 否则,执行S 209 。 [0066] 用户将手机放在手提包中,不知道有通话,或者用户不在移动终端附近,无法及时输入操作指令,但是移动终端无法一直等到用户进入 操作说明; 因此,移动终端需要确定是否在预设时间内接收到操作指令。 [0067] 小号 206 :移动终端确定接收到的操作指令是否为服务启动指令,如果是,则执行S 207 ; 否则,执行S 209 。 [0068] 在移动终端的显示器上显示诸如“回答”和“拒绝”之类的选项。 如果用户点击“答案”,则移动终端确定用户输入了操作指令以启动服务; 或者,如果用户点击“拒绝”,则移动终端确定用户输入了不用于启动该服务的操作指令,即会话服务在启动前已经结束,因此,S 209 被执行。 [0069] 小号 207 :移动终端执行服务。 [0070] 小号 208 :移动终端接收用于终止服务的信息。 [0071] 例如,移动终端接收视频流中的最后一条视频数据,则视频业务结束; 或者在终止呼叫时用户点击“举手”选项,则会话服务结束。 [0072] 小号 209 :移动终端控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0073] 在S 205 当移动终端确定在预设时间内没有收到用户输入的操作指令时,可以认为该服务在执行之前已经结束; 在S中 206 ,当移动终端确定接收到的操作指令为不用于启动服务的指令时,也可以认为该服务在执行之前结束; 和在S 208 ,移动终端接收用于终止服务的信息。 因此,当移动终端确定在预设时间内没有接收到用户输入的操作指令时,或者当移动终端确定接收到的操作指令是不用于启动服务的指令时,或者在移动终端之后。 终端开始执行服务,移动终端在S接收到用于终止服务的信息 209 因此,可以认为移动终端终止了服务,并且控制了移动终端的启用天线的数量以恢复到接收到服务信号之前的数量。 [0074] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0075] 图。 图4是根据本实施例的用于移动终端天线的控制方法的实施例3的流程图。 如图1所示。 如图4所示,在本实施例中,服务的启动命令为操作指令,在这种情况下,具体过程如下: [0076] 小号 301 :移动终端接收与服务有关并由用户输入的操作指令。 [0077] 小号 302 :移动终端根据与该服务相关的操作指令,确定该服务需要启用的天线数量。 [0078] 例如,在S中 301 ,如果用户点击“广播”图标,则移动终端接收用户输入的与收听广播业务有关的操作指令; 或者,如果用户点击“电话”应用(应用)图标和“联系人”应用图标,则移动终端接收与会话服务相关的操作指令,然后移动终端开始执行该服务。 因此,在本实施方式中,与服务相关的操作指令是开始指令。 然后在S 302 然后,移动终端根据与该服务相关的操作指令,确定要执行的服务以及该服务需要启用的天线数量。 [0079] 小号 303 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0080] 通过使用用户点击“联系人”应用程序的示例,移动终端通过使用S确定 302 ,要执行的服务是会话服务,但通过使用S确定 302 ,则需要为会话服务启用的天线数量为2,然后为S 303 ,移动终端禁用2根天线,并保留2根启用的天线。 [0081] 可以理解的是,如果与服务相关的操作指令正在点击“无线电”应用,并且移动终端通过使用S来启用 301 到S 303 ,是收听广播服务并直接执行该服务所需的天线,以下S 304 到S 309 可能无法执行。 对于某些服务,为了改善用户体验,或者避免用户输入的操作指令是用户误按的结果,在执行该服务之前,移动终端还需要接收后续的操作指令,以确定 用户决定启动服务。 例如,在用户点击“联系人”应用图标后,移动终端向用户显示多个联系人选项和“返回”选项; 移动终端直到用户进一步点击联系人之后并与该联系人的选项相对应的拨号选项之前,才确认用户决定开始会话服务; 或者,如果用户选择“返回”选项,则表明用户决定不启动会话服务。 详细信息如S所示 304 到S 309 : [0082] 小号 304 :移动终端提示用户输入后续的操作指令。 [0083] 小号 305 :移动终端确定是否在预设时间内接收到用户输入的后续操作指令,如果是,则执行S 306 ; 否则,执行S 309 。 [0084] 在用户不知不觉地误按图标的情况下,用户不能及时输入后续的操作指令,但是移动终端不能一直等到用户输入后续的操作指令。 因此,移动终端需要确定在预定时间内是否接收到后续的操作指令。 [0085] 小号 306 :移动终端确定接收到的后续操作指令是否为启动服务的指令,如果是,则执行S 307 ; 否则,执行S 309 。 [0086] 多个联系人选项和与该联系人选项相对应的拨号选项显示在移动终端的显示屏上,同时还有诸如“返回”和“放入黑名单”之类的选项。 如果用户点击“拨号”选项,则移动终端确定用户输入了后续的操作指令以启动服务。 或者,如果用户点击“返回”或“放入黑名单”之类的选项,则移动终端确定用户输入了不用于启动该服务的后续操作指令,即会话服务在启动前已结束 ,因此S 309 被执行。 [0087] 小号 307 :移动终端执行服务。 [0088] 小号 308 :移动终端接收用于终止服务的信息。 [0089] 具体而言,请参阅S 208 。 [0090] 小号 309 :移动终端控制移动终端的启用天线的数量,使其恢复到接收到操作指令之前的数量。 [0091] 在S 305 ,当移动终端确定在预设时间内没有收到用户输入的后续操作指令时,可以认为该服务在执行之前已经结束; 在S中 306 ,当移动终端确定接收到的后续操作指令为不用于启动服务的指令时,还可以认为该服务在执行之前结束; 和在S 308 ,移动终端接收用于终止服务的信息。 因此,当移动终端确定在预设时间内没有接收到用户输入的操作指令时,或者当移动终端确定接收到的操作指令是不用于启动服务的指令时,或者在移动终端之后。 终端开始执行服务,移动终端在S接收到用于终止服务的信息 309 因此,可以认为移动终端终止了服务,并且控制了移动终端的启用天线的数量以恢复到接收到服务信号之前的数量。 [0092] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 在移动终端上启用天线的数量不能满足执行服务的要求,并且还防止了在移动终端上启用天线的数量过多,这导致不必要的功耗并影响移动终端的性能。 [0093] 在前述实施例中,接收到的服务信号或与服务有关的操作指令被用作开始命令。 在某些情况下,当移动终端接收到服务信号或与该服务有关的操作指令时,该移动终端仅准备执行该服务,而没有立即执行该服务,然而,为了有效地向用户提供该服务, 移动终端仍立即将移动终端的启用天线的数量控制为为要执行服务而需要启用的天线的数量。 然而,在某些情况下,与服务有关的操作指令是用户错​​误按压的结果,或者接收到服务信号,但是用户不能立即给出指令,即,移动终端没有接收到操作。 在预设时间内发出指令,在这种情况下,需要控制移动终端将启用天线的数量恢复为接收到启动命令之前的数量。 在该过程中,在移动终端上发生不必要的启用/关闭控制。 移动终端对天线的开/关控制也需要开销,而不必要的开/关控制会浪费开销。 因此,优选地,通过使用图2所示的实施例,可以进一步执行天线的开/关控制。 5或图。 6: [0094] 图。 图5是根据本实施例的移动终端天线的控制方法的实施例四的流程图。 如图1所示。 参照图5,该实施例包括。 [0095] 小号 401 :移动终端接收服务的服务信号。 [0096] 小号 402 :移动终端提示用户是否启动该服务。 [0097] 小号 403 :移动终端确定是否在预设时间内接收到用户输入的操作指令,如果是,则执行S 404 ; 否则,结束该过程。 [0098] 通过使用呼入呼呼消息作为服务信号的示例,用户将移动电话放在手提包中并且不知道有呼叫,或者用户不在移动终端附近并且不能在其中输入操作指令。 时间,但是移动终端不能一直等到用户输入操作指令。 因此,移动终端需要确定是否在预设时间内接收到操作指令。 [0099] 小号 404 :移动终端确定接收到的操作指令是否为服务启动指令,如果是,则执行S 405 ; 否则,结束该过程。 [0100] 在移动终端的显示器上显示诸如“回答”和“拒绝”之类的选项。 如果用户点击“答案”,则移动终端确定用户输入了操作指令以启动服务; 或者,如果用户点击“拒绝”,则移动终端确定用户输入了不用于启动服务的操作指令,即会话服务在启动前已经结束,本实施例结束。 [0101] 小号 405 :移动终端将该操作指令作为启动命令,并根据该启动命令确定需要为该服务启用的天线数量。 [0102] 即,移动终端确定在预设时间内接收到的操作指令是启动服务的指令,然后将该操作指令用作启动命令。 [0103] 小号 406 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0104] 执行S时 406 ,移动终端同时执行服务。 [0105] 小号 407 :移动终端接收用于终止服务的信息。 [0106] 小号 408 :移动终端控制移动终端的启用天线的数量,使其恢复到接收到启动命令之前的数量。 [0107] 同时,移动终端终止服务。 [0108] 在该实施例中,当接收到服务信号时,启用天线的数量不会立即改变。 当接收到用户输入的用于启动服务的操作指令时,将用于启动服务的操作指令用作启动命令。 其他步骤与图1所示实施例中的相应步骤相似。 具体可以参见图3所示实施例中的相应步骤。 3.在本实施例中,将启动服务的操作指令用作启动命令,可以避免不必要的天线开/关开销。 [0109] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 在移动终端上启用天线的数量不能满足执行服务的要求,并且还防止了在移动终端上启用天线的数量过多,这导致不必要的功耗并影响移动终端的性能。 [0110] 图。 图6是根据本实施例的移动终端天线的控制方法的实施例五的流程图。 如图1所示。 参照图6,该实施例包括。 [0111] 小号 501 :移动终端接收与服务有关并由用户输入的操作指令。 [0112] 小号 502 :移动终端根据与业务有关的操作指令提示用户输入后续的操作指令。 [0113] 小号 503 :移动终端确定是否在预设时间内接收到用户输入的后续操作指令,如果是,则执行S 504 ; 否则,结束该过程。 [0114] 在用户不知不觉地误按图标的情况下,用户不能及时输入后续的操作指令,但是移动终端不能一直等到用户输入后续的操作指令。 因此,移动终端需要确定是否在预设时间内接收到后续的操作指令,如果是,则S 504 被执行; 否则,过程结束。 [0115] 小号 504 :移动终端确定接收到的后续操作指令是否为启动服务的指令,如果是,则执行S 505 ; 否则,结束该过程。 [0116] 多个联系人选项和与该联系人选项相对应的拨号选项显示在移动终端的显示屏上,同时还有诸如“返回”和“放入黑名单”之类的选项。 如果用户点击“拨号”选项,则移动终端确定用户输入了后续的操作指令以启动服务。 或者,如果用户点击“返回”或“添加至黑名单”等选项,则移动终端确定用户输入了不用于启动服务的后续操作指令,然后结束本实施例。 [0117] 小号 505 :移动终端使用后续的操作指令作为启动命令启动服务,并根据该启动命令确定需要为该服务启用的天线数量。 [0118] 移动终端接收到随后的用于启动服务的操作指令,因此,随后的用于启动服务的操作指令被用作启动命令。 [0119] 小号 506 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0120] 同时,服务被执行。 [0121] 小号 507 :移动终端接收用于终止服务的信息。 [0122] 小号 508 :移动终端控制移动终端的启用天线的数量,使其恢复到接收到启动命令之前的数量。 [0123] 同时,移动终端终止服务。 [0124] 与图1所示的实施例相比, 参照图4,在该实施例中,当接收到与服务有关的操作指令时,启用天线的数量不立即改变。 当接收到用户输入的用于启动服务的后续操作指令时,将用于启动服务的操作指令用作启动命令。 其他步骤与图1所示实施例中的相应步骤相似。 具体可以参见图4所示实施例中的相应步骤。 4.在本实施例中,将随后的启动服务的操作指令作为启动命令,可以避免不必要的天线开/关开销。 [0125] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0126] 图。 图7是根据本实施例的移动终端天线的控制方法的实施例六的流程图。 如图1所示。 参照图7,该实施例包括。 [0127] 小号 601 :移动终端获取相关信息。 [0128] 相关信息是以下信息中的至少任何一个:与移动终端相关的环境信息,移动终端的相关参数以及移动终端的当前工作模式。 [0129] 小号 602 :移动终端根据相关信息确定应保持启用状态的天线数量。 [0130] 具体地,移动终端获取的相关信息为相关参数,该相关参数表示移动终端的辐射过多,容易对用户造成有害影响。 因此,需要通过禁用某些天线来减少辐射。 例如,如果移动终端当前启用4个天线,导致移动终端过度辐射,则通过使用S来确定 602 ,应保持启用的天线数量为2,因此,使用S禁用2根天线 603 。 [0131] 小号 603 :移动终端控制移动终端的启用天线的数量为与相关信息相对应的天线的数量。 [0132] 在本实施例中,移动终端根据获取到的相关信息,确定该移动终端上应保持启用的天线数量,并灵活地改变该移动终端上的启用天线数量,从而防止移动终端上启用天线数量的增加。 移动终端对周围环境造成有害影响,或者移动终端耗电等电能消耗过快,影响移动终端性能。 [0133] 图。 图8是根据本实施例的移动终端天线的控制方法的实施例七的流程图。 如图1所示。 在图8所示的实施例的基础上,图8示出了该实施例。 参照图7,该实施例提供了进一步的详细描述,并且具体包括。 [0134] 小号 701 :移动终端获取相关信息。 [0135] 小号 702 :移动终端将相关信息与预设条件进行比较,确定相关信息是否满足预设条件,如果是,则执行S 703 ; 否则,结束该过程。 [0136] 具体地,如果相关信息具体为由相关参数反映的辐射强度,则预设条件大于预设辐射阈值。 确定后,使用S 702 ,表明辐射强度大于预设的辐射阈值S 703 否则,表明当前移动终端启用的天线数量不影响附近的用户,在这种情况下,不需要禁用天线,本实施例结束。 备选地,可以认为移动终端执行S。 703 即,当移动终端当前启用的天线数量不影响附近的用户时,根据相关信息,确定应保持启用的天线数量与相关之前保持相同。 信息被获取。 如果相关信息具体是由相关参数反映的信号强度,则预设条件小于预设信号阈值。 确定后,使用S 702 ,表明信号强度小于预设信号阈值S 703 执行该操作,使更多的天线能够确保移动终端正常地为用户提供服务,否则,表明移动终端当前启用的天线数量满足移动终端正常运行的要求, 在这种情况下,不需要执行启用天线的控制,并且该实施例结束。 备选地,可以认为移动终端执行S。 703 即,当移动终端的当前信号强度大于预设信号阈值时,通过使用S确定 703 其中,不需要增加使能的天线数量,即根据相关信息确定应保持使能的天线数量保持与获取相关信息之前的数量相同。 [0137] 如果相关信息不满足预设条件,则表明不需要改变移动终端上的启用天线数量,本实施例结束。 换句话说,S 703 和S 704 仍然执行,即通过使用S确定 703 根据不满足预设条件的相关信息,保持启用天线的数量与获取相关信息之前的数量相同。 然后在S 704 ,控制移动终端以保持启用天线的数量与S之前的数量相同 701 。 [0138] 小号 703 :移动终端根据相关信息确定应保持启用状态的天线数量。 [0139] 小号 704 :移动终端控制移动终端的启用天线的数量为与相关信息相对应的天线的数量。 [0140] 此外,相关信息是以下信息中的至少任何一个:与移动终端相关的环境信息,移动终端的相关参数以及移动终端的当前工作模式。 对应地,可能的相关信息有以下五种情况:第一种情况:当相关信息是与终端相关的环境信息,并且该环境信息是移动终端辐射范围内的用户时,预设条件为预设生物 信息; 第二种情况:当环境信息是移动终端所处的场景时,预设条件为预设限制场景; 第三种情况:当相关信息是终端的相关参数,并且相关参数是移动终端的辐射强度时,预设条件大于预设辐射阈值; 第四种:当相关参数为移动终端的信号强度时,预设条件小于预设信号阈值; 第五种:当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0141] 对于第一种情况,以下步骤用于表示S的特定执行过程 701 到S 702 , 那是。 [0142] 小号 11 a :移动终端接收第三方设备发送的用户功能。 [0143] 第三方设备是智能可穿戴设备,其中,第三方设备可以获取移动终端用户或附近人的用户特征,该人具体为成年人,老人,孕妇,儿童。 等等。 [0144] 或者,S 11 a 可以用S代替 11 b. [0145] 小号 11 b :移动终端解析用户输入的操作指令或获取的用户信息,以获取用户特征。 [0146] 例如,操作指令是“访问孕妇网页”,或打开一个名为“老人保健”的应用程序; 然后,在解析该操作指令后,获取关键字“孕妇”或“老人”,表示使用该移动终端的用户是孕妇还是老人。 然后使用S确定 12 ,这些用作用户功能的关键字是否符合预设的生物学信息。 [0147] 用户信息由用户输入或由第三方设备发送; 例如,用户通过使用照相机或移动终端的温度传感器来获得诸如使用该移动终端的用户的面部图像和体温或该移动终端附近的人的面部图像和体温之类的用户信息。 ,或智能穿戴设备之类的第三方设备收集用户信息,例如体温,用户的皮肤湿度和弹性; 然后,在解析用户信息之后,移动终端获取用户特征,即根据用户信息确定的用户特征具体为生物特征,例如老人,儿童,孕妇或成年人。 [0148] 小号 12 :移动终端将用户特征与预设的生物信息进行比较,确定用户特征是否符合预设的生物信息,如果是,则执行S 703 ; 否则,结束该过程。 [0149] 例如,预设的生物学信息具体包括老年人,儿童和孕妇。 如果使用S获得用户功能 11 是老年人,通过使用S确定 12 需要注意的是,用户功能符合预设的生物学信息,因此需要禁用某些天线以减少对老年人的辐射。 如果用户特征是成年人,则无需禁用天线,即本实施例结束,换句话说,移动终端仍然继续执行S操作。 703 到S 704 :在这种情况下,通过使用S确定 703 ,则无需为成年人更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0150] 对于第二种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0151] 小号 21 :移动终端获取场景信息。 [0152] 通过在移动终端上使用传感器或照相机来获取场景信息。 [0153] 小号 22 :移动终端将场景信息与预设的限制场景进行比较,确定场景信息是否满足预设的限制场景,如果是,则执行S 703 ; 否则,结束该过程。 [0154] 预设限制场景是诸如医院和机场之类的场景,其中需要限制来自移动终端的辐射干扰。 例如,如果在照相机拍摄的图像上出现医院的标识符,机场的标识符,儿童,孕妇,老人的标识符等,则通过移动终端的图像分析获悉: 因此,通信设备位于诸如医院或机场之类的环境中,或者周围有儿童,孕妇,老人等,并且移动终端继续执行S 703 。 可替代地,如果场景信息不是预设的限制场景所规定的任何场景,则不需要执行天线开启/关闭的控制,即该实施例结束,或者说,移动终端仍然继续 施行 703 到S 704 :在这种情况下,通过使用S确定 703 ,对于预设限制场景未规定的任何场景,无需更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0155] 对于第三种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0156] 小号 31 :移动终端自身检测辐射强度,以获取移动终端当前的辐射强度。 [0157] 小号 32 :移动终端将检测到的移动终端的辐射强度与预设的辐射阈值进行比较,确定移动终端的辐射强度是否大于预设的辐射阈值,如果是,则执行S 703 ; 否则,结束该过程。 该过程的结束也可以被解释为继续执行S。 703 到S 704 即辐射强度不大于预设的辐射阈值; 并通过使用S来确定 703 ,则无需为成年人更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0158] 对于第四种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0159] 小号 41 :移动终端自身检测信号强度,以获取移动终端的当前信号强度。 [0160] 小号 42 :移动终端将检测到的移动终端的信号强度与预设信号阈值进行比较,确定移动终端的信号强度是否小于预设信号阈值,如果是,则执行S 703 ; 否则,结束该过程。 该过程的结束也可以被解释为执行S。 703 到S 704 即,当辐射强度大于预设的辐射阈值时,通过S确定 703 ,则无需更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0161] 对于第五种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0162] 小号 51 :移动终端获取当前的工作模式。 [0163] 当前的工作模式是由用户设置的,例如,飞行模式,省电模式,正常模式或增强模式,并且在这种情况下,预设工作模式包括以下模式: 需要控制启用状态,例如飞行模式,省电模式,正常模式或增强模式。 例如,正常模式通常是移动终端的默认模式,并且保持启用了4根天线; 在飞行模式下需要禁用所有天线,在省电模式下只需要启用一根天线,在增强模式下需要启用超过4根天线; 另外,可以由移动终端设置省电模式,例如,当移动终端检测到移动终端的剩余电量低于预设的电量阈值时,可以由移动终端设置省电模式。 移动终端。 [0164] 小号 52 :移动终端将移动终端的当前工作模式与预设工作模式进行比较,确定当前工作模式是否满足预设工作模式,如果是,则执行S 703 ; 否则,结束该过程。 该过程的结束也可以被解释为执行S。 703 到S 704 即当前工作模式不是预设工作模式下的任何模式,例如,如果当前工作模式为普通模式,则通过S来确定 703 ,对于正常模式,仅需要保留默认数量的启用天线,并且不需要更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0165] 在本实施例中,移动终端根据获取到的相关信息,确定该移动终端上应保持启用的天线数量,并灵活地改变该移动终端上的启用天线数量,从而防止移动终端上启用天线数量的增加。 移动终端对周围环境造成有害影响,或者移动终端耗电等电能消耗过快,影响移动终端性能。 [0166] 图。 图9是根据本实施例的移动终端的实施例1的结构图。 如图1所示。 9,移动终端 600 包括:获取模块 61 ,配置为获取服务的启动命令; 确定模块 62 ,用于根据启动命令确定需要为该服务启用的天线数量; 和一个处理模块 63 配置为将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0167] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0168] 图。 图10是根据本实施例的移动终端的实施例二的结构图。 如图1所示。 在图10所示的实施例的基础上, 9 ,本实施例提供了进一步的详细描述,具体地,获取模块 61 具体用于接收业务的业务信号,业务信号为启动命令。 [0169] 进一步地,所述移动终端还包括提示模块 64 和一个判断模块 65 ,其中提示模块 64 配置为提示用户是否启动服务; 以及判断模块 65 确定获取模块 61 在预设时间内未收到用户或判断模块输入的操作指令 65 确定所述用户输入并由所述获取模块接收到的操作指令 61 在预设时间内未启动服务指令,处理模块 63 控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0170] 进一步的,获取模块 61 还被配置为接收该服务的服务信号; 提示模块 64 配置为提示用户是否启动服务; 获取模块 61 用于接收用户输入的操作指令; 和评审模块 65 配置为确定该操作指令为启动服务的指令,然后获取模块 61 专门配置为使用操作指令作为启动命令。 [0171] 进一步的,获取模块 61 具体用于接收用户输入的与服务有关的操作指令,其中,与服务有关的操作指令为启动命令。 [0172] (可选)提示模块 64 用于提示用户输入后续的操作指令; 以及判断模块 65 确定获取模块 61 在预设时间内没有收到用户或判断模块输入的后续操作指令 65 确定所述用户输入并由所述获取模块接收到的后续操作指令 61 在预设时间内未启动服务指令,处理模块 63 配置为控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0173] 可选地,获取模块 61 接收用户输入的与服务相关的操作指令; 提示模块 64 根据与服务有关的操作指令提示用户输入后续的操作指令; 和评审模块 65 确定获取模块 61 接收后续的操作指令启动服务,然后获取模块 61 使用后续的操作指令将服务作为启动命令来启动。 [0174] 进一步的,获取模块 61 还被配置为接收用于终止服务的信息; 和处理模块 63 终止服务,并控制移动终端的启用天线数量,使其恢复到接收到启动命令之前的数量。 [0175] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0176] 图。 图11是根据本实施例的移动终端的实施例三的结构图。 如图1所示。 11,移动终端 700 本实施例中包括:获取模块 71 ,用于获取相关信息,所述相关信息至少为以下信息中的任意一种:与所述移动终端相关的环境信息,所述移动终端的相关参数以及所述移动终端的当前工作模式; 确定模块 72 ,配置为根据相关信息确定应保持启用状态的天线数量; 和一个处理模块 73 ,被配置为控制移动终端的启用天线的数量为与相关信息相对应的天线的数量。 [0177] 进一步地,确定模块 72 还用于将所述相关信息与预设条件进行比较,并确定所述相关信息是否满足所述预设条件,其中,当所述相关信息为与所述终端相关的环境信息,所述环境信息为所述移动终端辐射范围内的用户时 终端,预设条件为预设生物信息; 当环境信息为移动终端所处的场景时,预设条件为预设限制场景; 当相关信息为终端的相关参数,且相关参数为移动终端的辐射强度时,预设条件大于预设辐射阈值; 当相关参数为移动终端的信号强度时,所述预设条件小于预设信号阈值; 当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0178] 进一步地,当环境信息是移动终端辐射范围内的用户时,确定模块 72 具体用于将第三方设备发送的用户特征与预设的生物信息进行比较,确定第三方设备发送的用户特征是否满足预设的生物信息; 或者,获取模块 71 进一步用于解析用户输入的操作指令或获取的用户信息,获取用户特征; 和确定模块 72 进一步用于将所述用户特征与所述预设生物信息进行比较,并确定所述用户特征是否满足所述预设生物信息,所述用户信息由用户输入或由第三方设备发送; 如果用户特征满足预设的生物学信息,则处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0179] 当环境信息为移动终端所在的场景时,确定模块 72 具体用于将场景信息与预设的限制场景进行比较,确定场景信息是否满足预设的限制场景,该场景信息是通过移动终端上的传感器或摄像机获取的。 如果所述场景信息满足预设的限制场景,则所述处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0180] 当相关参数为移动终端的辐射强度时,确定模块 72 具体用于将检测到的移动终端的辐射强度与预设的辐射阈值进行比较,判断移动终端的辐射强度是否大于预设的辐射阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则处理模块 73 用于根据相关信息确定应保持启用状态的天线数量; 或者,当相关参数为移动终端的信号强度时,确定模块 72 具体用于将检测到的所述移动终端的信号强度与所述预设信号阈值进行比较,判断所述移动终端的信号强度是否小于所述预设信号阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0181] 当相关参数为移动终端当前的工作模式时,确定模块 72 将移动终端的当前工作模式与工作模式进行比较,确定当前工作模式是否满足预设工作模式,其中当前工作模式由用户设置,或由移动终端在检测到工作模式时设置 移动终端的剩余电量低于预设电量阈值; 如果移动终端当前的工作模式满足预设的工作模式,则处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0182] 在本实施例中,移动终端根据获取到的相关信息,确定该移动终端上应保持启用的天线数量,并灵活地改变该移动终端上的启用天线数量,从而防止移动终端上启用天线数量的增加。 移动终端对周围环境造成有害影响,或者移动终端耗电等电能消耗过快,影响移动终端性能。 [0183] 需要另外说明的是,移动终端实施例中的模块分别执行图3所示方法实施例中的步骤。 参照图2至图3。 如图8所示,具体执行过程和有益效果可以参考方法实施例。 [0184] 图。 图12是根据本实施例的移动终端的实施例四的结构图。 如图1所示。 参照图12,该实施例中的移动终端仅是示例。 可以理解,在实际应用中,移动终端可以是智能手机,iPad等。 不同移动终端内部的模块和部件不相同; 因此,在实践中,移动终端可以具有比图2所示的更多或更少的部件。 如图12所示,可以组合两个或更多个部分,或者可以具有不同的部分构造。 图2中所示的部件包括: 可以用包括一个或多个信号处理和/或专用集成电路的硬件,软件或硬件和软件的组合来实现图12所示的处理。 [0185] 移动终端 800 至少包含2根天线 81 ,至少一个处理器 82 记忆 83 传感器 84 ,输入/输出(I / O)接口 85 ,一个通讯模块 86 ,以及至少一条通讯总线 87 。 进一步地,移动终端还包括另一功能组件,例如,用于电池管理的电池模块,用户设置管理模块或参数检测模块; 和通讯总线 87 配置为实现模块和组件之间的连接通信。 记忆 83 存储器可以包括非易失性固态存储器和/或动态非易失性存储设备,例如闪存或可旋转磁盘驱动器。 传感器 84 包括各种传感器,例如温度传感器和湿度传感器,并且被配置为测量诸如使用移动终端的用户的体温和皮肤湿度的信息; 通讯模块 86 3G技术可以用于GSM(全球移动通信系统),CDMA(码分多址),GPRS(通用分组无线业务)或EDGE(GSM演进的增强数据速率)等长距离通信。 作为WCDMA(宽带码分多址)或TD-SCDMA(时分同步码分多址),LTE(长期演进)等4G技术等; 和通讯模块 86 可以进一步用于短距离通信,并且可以与第三方执行短距离无线电通信,例如ZigBee,超宽带(UWB),Wi-Fi,蓝牙,近场通信(NFC)和红外通信 短距离内的设备(例如智能穿戴设备)以及天线 81 与通讯模块配合 86 配置为接收和发送信号。 [0186] 具体而言,I / O接口 85 包括触摸屏 851 用于显示和输入的I / O键盘 852 (可选)用于输入,麦克风 853 , 相机 854 等等。 [0187] 具体来说,内存 83 包括一个操作系统 4021 和一个应用程序 4022 ,其中的操作系统 4021 包括各种操作系统程序,用于实现基于硬件的各种操作; 和应用程序 4022 包括各种应用程序,用于实现各种应用程序功能,例如,用于启用/关闭天线的控制程序,服务识别程序,用户特征识别程序以及相关的信息识别程序,其中,服务识别程序 可以根据用户输入的操作或移动终端接收到的服务信号,标识移动终端将要执行的服务,用户特征识别程序可以分析获取到的图像,得到关键词, 用户特征等,或者可以根据用户输入的声纹信息执行分析,以获取用户特征,或者可以分析由第三方设备(例如智能可穿戴设备)发送并由第三方设备接收的用户信息。 通信模块,以获得用户功能。 [0188] 此外,内存 83 可以进一步存储预设条件,该预设条件可以是预设生物信息,预设限制场景,预设辐射阈值,预设信号阈值,预设工作模式等。 [0189] 处理器 82 使用通讯总线与模块和组件进行通讯 87 。 在控制禁用或启用移动终端上的天线期间,当通信模块 86 通过使用天线接收服务的服务信号 81 ; 基于存储器中的服务识别程序,处理器识别服务并确定需要为该服务启用的天线数量,然后基于用于启用/关闭天线的控制程序控制启用的天线数量 移动终端的数量等于需要为该服务启用的天线数量。 [0190] 可选地,当用户通过触摸屏输入操作指令时,所述处理器基于所述服务标识程序,识别所述服务并确定需要为该服务启用的天线数量,然后基于所述控制程序启用 断开/断开天线,将移动终端的已启用天线的数量控制为该服务需要启用的天线的数量。 [0191] 另外,处理器 82 可以进一步控制触摸屏 851 通过使用通讯总线 87 ,并提示用户是否启动服务,并提示用户输入操作指令。 [0192] 进一步,当处理器获得相关信息时 82 是在移动终端辐射范围内的用户,处理器 82 根据用户特征识别程序解析用户信息,获得用户特征,将用户特征与存储在存储器中的预设生物信息进行比较,然后基于控制程序使能/关闭天线,控制天线的数量。 使移动终端的天线成为与用户特征相对应的天线数量,其中,用户信息可以是用户通过使用麦克风输入的声纹信息,用户通过使用摄像头捕获的面部图像或者用户的身体 温度,皮肤湿度等由温度传感器或湿度传感器感测到,或者可以是智能可穿戴设备感测并由通信模块接收的用户信息,或者是来自用户并由触摸屏接收的操作指令 。 [0193] 或者,处理器 82 可以基于相关信息识别程序进一步分析一些相关信息,将相关信息与存储在存储器中的预设条件进行比较,然后基于用于启用/禁用天线的控制程序,控制移动台的启用天线数量 终端是与相关信息相对应的天线数量,其中相关信息可以是移动终端所在的场景,所述场景是从摄像机拍摄的图片中获取的,相关信息标识程序可以标识 场景图片中的内容,例如医院或机场等关键字; 或者,所述相关信息为参数检测模块获取的移动终端的信号强度,辐射强度等; 或相关信息为用户设置管理模块中设置的工作模式,该工作模式可以由用户通过触摸屏输入的操作指令设置 851 或键盘 852 。 用户设置管理模块还通过使用通信总线与电池模块进行通信 87 并且,当电池模块检测到剩余电量小于预设阈值时,可以指示用户设置管理模块将工作模式设置为省电模式。 [0194] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行业务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失; 另外,移动终端还可以根据获取的相关信息,确定移动终端上应保持启用的天线数量,并灵活地改变移动终端上的启用天线数量,从而避免启用天线数量 会导致移动终端上的信息对周围环境造成有害影响,或者消耗过多的能量,例如移动终端的电能,从而影响移动终端的性能。 [0195] 本领域普通技术人员可以理解,方法实施例的全部或部分步骤可以通过指令相关硬件的程序来实现。 程序可以存储在计算机可读存储介质中。 当程序运行时,执行方法实施例的步骤。 前述存储介质包括:可以存储程序代码的任何介质,例如只读存储器(ROM),随机存取存储器(RAM),磁盘或光盘。 [0196] 最后,需要说明的是,上述实施例仅用于描述本实施例的技术方案,并不用于限制本发明。 尽管参考前述实施例详细描述了本实施例,但是本领域普通技术人员应该理解,他们仍然可以对前述实施例中描述的技术方案进行修改,或者对其部分或全部技术特征进行等同替换。 在不脱离实施例技术方案范围的情况下。 (String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104219377A(String), CN104219377B(String), CN107734615A(String), EP3151525A1(String), EP3151525A4(String), EP3151525B1(String), EP4020955A1(String), IN201627044485A(String), JP2017529808A(String), US20170111495A1(String), WO2016000460A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104219377A(String), CN104219377B(String), CN107734615A(String), EP3151525A1(String), EP3151525A4(String), EP3151525B1(String), EP4020955A1(String), IN201627044485A(String), JP2017529808A(String), US20170111495A1(String), WO2016000460A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20170111495A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104219377A(String), CN104219377B(String), CN107734615A(String), EP3151525A1(String), EP3151525A4(String), EP3151525B1(String), EP4020955A1(String), IN201627044485A(String), JP2017529808A(String), US20170111495A1(String), WO2016000460A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.079 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.080 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.080 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), CN104219377A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.088 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), CN104219377B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), CN107734615A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), EP3151525A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), EP3151525A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), EP3151525B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.297 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), EP4020955A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.312 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), IN201627044485A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), JP2017529808A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), US20170111495A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270686(Integer), WO2016000460A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.381 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20170111495A1(String), US20170111495A1(String), 1492617600(Integer), 270686(Integer), 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.393 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.394 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.396 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.396 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185008(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185008(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185008(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185008(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.423 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.445 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10666789B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Control method and device for sensors of mobile terminal, storage medium and mobile terminal(String), 移动终端传感器的控制方法及装置、存储介质及移动终端(String), US10666789B2(String), A control method for sensors of a mobile terminal is provided, which includes: a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; when determining that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, when there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and when the state resetting is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported.(String), 一种移动终端传感器的控制方法,包括:根据传感器使能指令确定移动终端传感器中的待使能传感器; 当确定触发移动终端的传感器开机事件时,获取移动终端的目标传感器的开机延迟,其中目标传感器至少包括待使能传感器,当有 为一个目标传感器,目标传感器的开机延迟小于移动终端传感器的最大开机延迟; 响应确定当前时刻达到目标传感器对应的开机延迟,对目标传感器执行状态复位; 当状态复位完成后,使能待使能传感器成为使能传感器,并上报使能传感器的获取数据。(String), US16/483693(String), 1508169600(Integer), US10666789B2(String), 1590422400(Integer), 1590422400(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 14(Integer), CN104503565A | CN105843365A | CN106850985A | CN108249874A | CN108255937A | US10111175B2 | US20090184849A1 | US20090259865A1 | US20100235667A1 | US20100302028A1 | US20130039230A1 | US20150005039A1 | US9167527B2 | US9693310B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185009(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\5e77d1e4cb8047738bdc6db0b9b8aeb3.png(String), 185009(Integer), 5e77d1e4cb8047738bdc6db0b9b8aeb3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Control method and device for sensors of mobile terminal, storage medium and mobile terminal(String), 移动终端传感器的控制方法及装置、存储介质及移动终端(String), US10666789B2(String), A control method for sensors of a mobile terminal is provided, which includes: a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; when determining that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, when there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and when the state resetting is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported.(String), 一种移动终端传感器的控制方法,包括:根据传感器使能指令确定移动终端传感器中的待使能传感器; 当确定触发移动终端的传感器开机事件时,获取移动终端的目标传感器的开机延迟,其中目标传感器至少包括待使能传感器,当有 为一个目标传感器,目标传感器的开机延迟小于移动终端传感器的最大开机延迟; 响应确定当前时刻达到目标传感器对应的开机延迟,对目标传感器执行状态复位; 当状态复位完成后,使能待使能传感器成为使能传感器,并上报使能传感器的获取数据。(String), US16/483693(String), 1508169600(Integer), US10666789B2(String), 1590422400(Integer), 1590422400(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 14(Integer), CN104503565A | CN105843365A | CN106850985A | CN108249874A | CN108255937A | US10111175B2 | US20090184849A1 | US20090259865A1 | US20100235667A1 | US20100302028A1 | US20130039230A1 | US20150005039A1 | US9167527B2 | US9693310B2(String), \20230420\5e77d1e4cb8047738bdc6db0b9b8aeb3.png(String), 14(Integer), 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 1. A control method for sensors of a mobile terminal, comprising:determining a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction;a determining that a sensor power-on event of the mobile terminal is triggered and acquiring a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least comprises the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal;executing, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; anddetermining that the state resetting on the to-be-enabled sensor is completed, enabling the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and reporting acquired data of the enabled sensor.(String), 1.如权利要求9所述的移动终端,还包括:响应于确定当前时刻达到移动终端的传感器的最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 2. The method as claimed in claim 1, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a first power-on delay of the to-be-enabled sensor; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor.(String), 12.如权利要求8所述的移动终端,其中获取移动终端的目标传感器的开机延时包括:获取移动终端各传感器的开机延时;和执行,响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器进行状态重置包括:响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 3. The method as claimed in claim 2, after reporting the acquired data of the enabled sensor, further comprising:executing state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 13.如权利要求12所述的移动终端,还包括:在确定移动终端的传感器开机事件被触发的同时启动调谐器,其中执行时,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器进行状态复位包括:响应于确定定时,定时器的值达到每个传感器中对应传感器的上电延迟,执行对应传感器上的状态重置。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 4. The method as claimed in claim 2, further comprising:executing, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 14.如权利要求12所述的移动终端,其中获取移动终端各传感器的开机延时包括:按照开机延时由短到长的顺序获取移动终端各传感器的开机延时。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 5. The method as claimed in claim 1, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a power-on delay of each sensor of the mobile terminal; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that a power-on delay of a corresponding sensor in each sensor is reached at the present moment, state resetting on the corresponding sensor.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 6. The method as claimed in claim 5, further comprising:starting a timer at the same time of determining that the sensor power-on event of the mobile terminal is triggered, whereinexecuting, in response to determining that a power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor comprises:executing, in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting on the corresponding sensor.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 7. The method as claimed in claim 5, wherein acquiring the power-on delay of each sensor of the mobile terminal comprises:acquiring the power-on delay of each sensor of the mobile terminal according to a sequence from short to long power-on delays.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 8. A mobile terminal, comprising a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to implement the following operations:determining a to-be-enabled sensor in sensors of the mobile terminal according to a sensor enabling instruction;determining that a sensor power-on event of the mobile terminal is triggered, and acquiring a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least comprises the to-be-enabled sensor and, in a ease where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal;executing, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; anddetermining that the state resetting on the to-be-enabled sensor is completed, enabling the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and reporting acquired data of the enabled sensor.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 9. The mobile terminal as claimed in claim 8, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a first power-on delay of the to-be-enabled sensor; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 10. The mobile terminal as claimed in claim 9, after reporting the acquired data of the enabled sensor, further comprising:executing the state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 11. The mobile terminal as claimed in claim 9, further comprising:executing, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, the state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 12. The mobile terminal as claimed in claim 8, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a power-on delay of each sensor of the mobile terminal; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that a power-on delay of a corresponding sensor in each sensor is reached at the present moment, state resetting on the corresponding sensor.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 13. The mobile terminal as claimed in claim 12, further comprising:starting a tuner at the same time of determining that the sensor power-on event of the mobile terminal is triggered, whereinexecuting, in response to determining the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor comprises:executing, in response to determining that a timing, value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting on the corresponding sensor.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185009(Integer), 14. The mobile terminal as claimed in claim 12, wherein acquiring the power-on delay of each sensor of the mobile terminal comprises:acquiring the power-on delay of each sensor of the mobile terminal according to a sequence from short to long power-on delays.(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185009(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The present application is a national stage application of International Patent Application No. PCT/CN2017/106612, which is filed on Oct. 17, 2017 and claims benefit to Chinese Patent Application No. 201710065209.X, filed on Feb. 4, 2017 and entitled “Control Method and Device for Sensors of Mobile Terminal, and Mobile Terminal”, the contents of which are hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]Embodiments of the application relate to the technical field of data processing, and particularly to a control method and device for sensors of a mobile terminal, a storage medium and a mobile terminal. BACKGROUND [0003]A mobile terminal such as a mobile phone is integrated with various types of sensors configured to assist in realization of various functions of the mobile phone. For example, an ambient light sensor may be configured to regulate brightness of automatic backlight of a screen of the mobile phone, a proximity sensor may be configured to assist in controlling the screen to be turned on and turned off, an acceleration sensor may be configured for step counting, a gravity sensor may be applied to a gravity sensing type game, a magnetic field sensor may be applied to map navigation and a compass, and a gyroscope may be configured to control a viewing angle in a game and implement inertial navigation and the like according to a motion state of an object when there is no signal of a Global Positioning System (GPS). SUMMARY [0004]The embodiments of the application provide a control method and device for sensors of a mobile terminal, a storage medium and a mobile terminal, which may increase a reporting speed of sensor data of the mobile terminal. [0005]The embodiments of the application provide a control method for sensors of a mobile terminal, which may include that: [0006]a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; [0007]in response to detecting that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0008]in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and [0009]in response to detecting that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0010]The embodiments of the application provide a control device for sensors of a mobile terminal, which may include: [0011]a to-be-enabled sensor determination module, configured to determine a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction; [0012]a power-on delay acquisition module, configured to acquire, in response to detecting that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0013]a target sensor state resetting module, configured to execute, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; and [0014]a sensor data reporting module, configured to, in response to detecting that state resetting of the to-be-enabled sensor is completed, enable the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and report acquired data of the enabled sensor. [0015]The embodiments of the application provide a storage medium, in which multiple instructions may be stored, the instructions being suitable to be loaded by a processor to execute the control method for the sensors of the mobile terminal in the embodiments of the application. [0016]The embodiments of the application provide a mobile terminal, which may include a memory, a processor and a computer program stored in the memory and capable of running on a processor, the processor executing the computer program to implement the following operations: [0017]a to-be-enabled sensor in sensors of the mobile terminal is determined according to a sensor enabling instruction; [0018]in response to detecting that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0019]in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and [0020]in response to detecting that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0021]According to the control method and device for the sensors of the mobile terminal, storage medium and mobile terminal provided in the embodiments of the application, a reporting speed of sensor data of the mobile terminal may be increased. BRIEF DESCRIPTION OF THE DRAWINGS [0022]FIG. 1 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application; [0023]FIG. 2 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application; [0024]FIG. 3 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application; [0025]FIG. 4 is a structure diagram of a control device for sensors of a mobile terminal according to an embodiment of the application; and [0026]FIG. 5 is a structure diagram of a mobile terminal according to an embodiment of the application. DETAILED DESCRIPTION OF THE EMBODIMENTS [0027]In order to make the purpose, technical solutions and advantages of the application clearer, exemplary embodiments of the application will further be described below in combination with the drawings in detail. It can be understood that the exemplary embodiments described herein are adopted only to explain the application and not intended to limit the application. It is also to be noted that, for convenient description, not all contents but only parts related to the application are illustrated in the drawings. It is to be mentioned before more detailed discussions about exemplary embodiments that some exemplary embodiments are described as processing or methods described in the flowcharts. Although each operation (or step) is described into sequential processing in the flowcharts, many operations therein may be implemented in parallel, concurrently or simultaneously. In addition, a sequence of each operation may be rearranged. When the operations are completed, processing may be terminated, but there may also be additional operations not included in the drawings. Processing may correspond to a method, a function, a procedure, a subroutine, a subprogram and the like. [0028]When a mobile terminal is woken from a dormant state, sensors may usually be controlled through the following process: powering-on each sensor, waiting for a power-on delay for each sensor, performing state resetting for each sensor, enabling one or more sensors, and reporting data of the one or more enabled sensors. A control method for sensors of a mobile terminal in a related art has defects and therefore needs to be improved. [0029]An embodiment of the application provides a control method for sensors of a mobile terminal, which includes that: [0030]a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; [0031]it is determined that a sensor power-on event of the mobile terminal is triggered, and a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0032]in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and [0033]it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0034]In an implementation mode, the operation that the power-on delay of the target sensor of the mobile terminal is acquired includes that: [0035]a first power-on delay of the to-be-enabled sensor is acquired; and [0036]the operation that the state resetting is executed on the target sensor in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment includes that: [0037]in response to determining that the first power-on delay is reached at the present moment, the state resetting is executed on the to-be-enabled sensor. [0038]In an implementation mode, the operation that the power-on delay of the target sensor of the mobile terminal is acquired includes that: [0039]a power-on delay of each sensor of the mobile terminal is acquired; and [0040]the operation that the state resetting is executed on the target sensor in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment includes that: [0041]in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting is executed on the corresponding sensor. [0042]In an implementation mode, after the operation that the acquired data of the enabled sensor is reported, the method further includes that: [0043]the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0044]In an implementation mode, the control method for the sensors of the mobile terminal further includes that: [0045]in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0046]In an implementation mode, the control method for the sensors of the mobile terminal further includes that: [0047]a timer is started at the same time of determining that the sensor power-on event of the mobile terminal is triggered; and [0048]the operation that the state resetting is executed on the corresponding sensor in response to determining that the power-on delay of the corresponding sensor in each sensor is reached at the present moment includes that: [0049]in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting is executed on the corresponding sensor. [0050]FIG. 1 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application. The method of the embodiment may be executed by a control device for sensors of a mobile terminal. The device may be implemented by hardware and/or software. The device may be arranged in the mobile terminal as a part of the mobile terminal. [0051]As shown in FIG. 1, the control method for the sensors of the mobile terminal in the embodiment includes the following operations. [0052]In operation 101, a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction. [0053]In the embodiment, the mobile terminal includes, but is not limited to, a device such as a mobile phone, a notebook computer and a tablet computer, and the sensors of the mobile terminal include, but are not limited to, an ambient light sensor, a proximity sensor, an acceleration sensor, a gravity sensor, a magnetic field sensor, a gyroscope, a fingerprint sensor, a hall sensor, an air pressure sensor, a heartbeat sensor, an ultraviolet sensor and the like. [0054]An application of the mobile terminal, when needing to acquire data by use of a sensor, may send a sensor enabling instruction to a hardware abstract layer of the mobile terminal through an application layer of the mobile terminal. For example, when the mobile terminal changes from a screen-off state to a screen-on state, some applications (for example, a false triggering prevention application) may send enabling instructions of enabling the proximity sensor to the hardware abstract layer to acquire data of the proximity sensor, and some applications (for example, an automatic backlight regulation application) may send enabling instructions of enabling the ambient light sensor to the hardware abstract layer to acquire data of the ambient light sensor. There are many sensors in the mobile terminal, only one or more sensors may be to be enabled, and the one or more sensors of this type are called one or more to-be-enabled sensors. Then, the one or more to-be-enabled sensors in the sensors of the mobile terminal may be determined according to the sensor enabling instructions. After a sensor is enabled, data may be acquired by use of the sensor. For example, an ambient light parameter is acquired by use of the ambient light sensor, and a distance parameter between a user or another target object and the mobile terminal is acquired by use of the proximity sensor. Herein, there may be one or more to-be-enabled sensors. [0055]In operation 102, it is determined that that a sensor power-on event of the mobile terminal is triggered, and a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal. [0056]That the sensor power-on event of the mobile terminal is triggered includes that the mobile terminal is woken from a dormant state (for example, changing from the screen-off state to the screen-on state), or that the sensors are woken from the dormant state or that the sensor enabling instruction is detected. [0057]The power-on delay refers to a minimum time duration started from a power-on moment to ensure stable and normal power-on of the sensor. The power-on delay of each sensor may be different. For example, the power-on delay of the ambient light sensor is 20 ms, the power-on delay of the proximity sensor is 30 ms, while the power-on delay of the gyroscope is 150 ms. [0058]The target sensor may be the to-be-enabled sensor, and may alternatively include the to-be-enabled sensor and the other sensors. [0059]In operation 103, whether power-on delay corresponding to the target sensor is reached at a present moment or not is judged, if the power-on delay corresponding to the target sensor is reached at the present moment, operation 104 is executed, otherwise operation 103 is continued to be executed until the power-on delay is reached at the present moment. [0060]The inventor finds that many sensors in the mobile terminal share an Inter-Integrated Circuit (I2C) and a power supply and thus all of the sensors may be simultaneously powered on during power-on of the sensors. A maximum power-on delay in the power-on delays of all the sensors may be selected as the power-on delay to ensure normal power-on of each sensor. For example, the gyroscope usually requires a relatively long power-on delay as long as 150 ms, but the power-on delay of the ambient light sensor or the proximity sensor is short or even not required. Even if the ambient light sensor only needs to be enabled for an application, state resetting and enabling of the ambient light sensor can be executed only after the delay of 150 ms, which greatly delays data reporting of the ambient light sensor and reduces a reporting speed of sensor data. [0061]In a first example, if the target sensor includes the ambient light sensor and the proximity sensor, both of which are to-be-enabled sensors, state resetting is executed on the ambient light sensor 20 ms after power-on is started, and the state resetting is executed on the proximity sensor 30 ms after power-on is started. [0062]In a second example, if the target sensor includes the ambient light sensor which is a to-be-enabled sensor and another sensor, i.e., the gyroscope, the state resetting is executed on the ambient light sensor 20 ms after power-on is started, and the state resetting is executed on the gyroscope 150 ms after power-on is started. [0063]Herein, initial states of some sensors may be abnormal and thus state resetting is executed to ensure that the powered-on sensors are in normal states. [0064]In operation 104, state resetting is executed on the target sensor. [0065]In response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting is executed on the target sensor. [0066]If there are multiple target sensors, in response to determining that the power-on delay of a certain sensor is reached, the state resetting is executed on this sensor. [0067]In operation 105, it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0068]In a process of executing the resetting operation on the target sensor, if state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor. [0069]In the first example, the state resetting is executed on the ambient light sensor 20 ms after power-on is started, and in response to determining that state resetting of the ambient light sensor is completed, the ambient light sensor is enabled, and acquired data of the ambient light sensor is reported. Also in the first example, the state resetting is executed on the proximity sensor 30 ms after power-on is started, and in response to determining that state resetting of the proximity sensor is completed, the proximity sensor is enabled, and acquired data of the proximity sensor is reported. Compared with executing state resetting on the proximity sensor and the ambient light sensor and enabling the proximity sensor and the ambient light sensor 150 ms after power-on, this manner has the advantage that the reporting speed of the sensor data is greatly increased. [0070]In the second example, the state resetting is executed on the ambient light sensor 20 ms after power-on is started, and in response to determining that state resetting of the ambient light sensor is completed, the ambient light sensor is enabled, and the acquired data of the ambient light sensor is reported. Also in the second example, the state resetting is executed on the gyroscope 150 ms after power-on is started. [0071]It is to be noted that operation 105 may be executed in a process of executing operation 104 and may alternatively be executed after operation 104 is executed. FIG. 1 exemplarily illustrates an execution sequence of operations 104 and 105. Exemplarily, if the target sensor is the ambient light sensor which is a to-be-enabled sensor, after operation 104 is executed to execute the state resetting on the ambient light sensor, operation 105 is executed to determine that state resetting of the ambient light sensor is completed and enable the ambient light sensor. In the second example, after operation 104 is executed to execute the state resetting on the ambient light sensor 20 ms after power-on is started, operation 105 is executed to determine that state resetting of the ambient light sensor is completed and enable the ambient light sensor, and then operation 104 is re-executed to execute the state resetting on the gyroscope. [0072]FIG. 2 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application. As shown in FIG. 2, the method provided in the embodiment includes the following operations. [0073]In operation 201, a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction. [0074]In operation 202, it is determined that a sensor power-on event of the mobile terminal is triggered, and a first power-on delay of the to-be-enabled sensor is acquired. [0075]When there are multiple to-be-enabled sensors, there are correspondingly multiple first power-on delays. [0076]In operation 203, whether the first power-on delay is reached at a present moment or not is judged, if the first power-on delay is reached at the present moment, operation 204 is executed, otherwise operation 203 is continued to be executed until the first power-on delay is reached at the present moment. [0077]In operation 204, state resetting is executed on the to-be-enabled sensor. [0078]When there are multiple first power-on delays, in response to determining that the first power-on delay of a certain sensor is reached at the present moment, the state resetting may be executed on this sensor. [0079]In operation 205, it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0080]When there are multiple to-be-enabled sensors, in response to determining that state resetting of a certain sensor therein is completed, the sensor is immediately enabled. [0081]After the operation that the acquired data of the enabled sensor is reported, the method may further include that: the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0082]In response to determining that a maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0083]FIG. 3 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application. As shown in FIG. 3, the control method for the sensors of the mobile terminal in the embodiment includes the following operations. [0084]In operation 301, a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction. [0085]In operation 302, it is determined that a sensor power-on event of the mobile terminal is triggered, and a power-on delay of each sensor of the mobile terminal is acquired. [0086]In operation 303, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at a present moment, state resetting is executed on the corresponding sensor. [0087]The operation 303 may include that: each power-on delay corresponding to each sensor is determined according to a sequence from short to long power-on delays; each power-on delay is determined as a present power-on delay respectively; and in response to determining that the present power-on delay is reached at the present moment, the state resetting is executed on the sensor corresponding to the present power-on delay. [0088]Exemplarily, the power-on delays of each sensor of the mobile terminal are 20 ms, 30 ms, 50 ms and 150 ms respectively. Then, the state resetting is executed on the sensor with the 20 ms power-on delay 20 ms after power-on is started, the state resetting is executed on the sensor with the 30 ms power-on delay 30 ms after power-on is started, the state resetting is executed on the sensor with the 50 ms power-on delay 50 ms after power-on is started, and finally the state resetting is executed on the sensor with the 150 ms power-on delay 150 ms after power-on is started. [0089]In operation 304, it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0090]A timer is started at the same time of determining that the sensor power-on event of the mobile terminal is triggered. Correspondingly, operation 303 may include that: in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting is executed on the corresponding sensor. Herein, the operation that the state resetting is executed on the corresponding sensor in response to determining that the power-on delay of the corresponding sensor in each sensor is reached at the timing value of the timer may include that: each power-on delay corresponding to each sensor is determined; each power-on delay is determined as a present power-on delay; and in response to determining that the present power-on delay is reached at the timing value of the timer, the state resetting is executed on the sensor corresponding to the present power-on delay. [0091]An embodiment of the application provides a control device for sensors of a mobile terminal, which includes: [0092]a to-be-enabled sensor determination module, configured to determine a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction; [0093]a power-on delay acquisition module, configured to determine that a sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0094]a target sensor state resetting module, configured to execute, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; and [0095]a sensor data reporting module, configured to determine that state resetting of the to-be-enabled sensor is completed, enable the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and report acquired data of the enabled sensor. [0096]In an implementation mode, the power-on delay acquisition module is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a first power-on delay of the to-be-enabled sensor; and [0097]the target sensor state resetting module is configured to execute, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor. [0098]In an implementation mode, the power-on delay acquisition module is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of each sensor of the mobile terminal; and [0099]the target sensor state resetting module is configured to execute, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor. [0100]In an implementation mode, the device further includes: [0101]a first other sensor state resetting module, configured to, after the acquired data of the enabled sensor is reported, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0102]In an implementation mode, device further includes: [0103]a second other sensor state resetting module, configured to, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0104]In an implementation mode, the device further includes: [0105]a timer starting module, configured to start a timer at the same time of determining that the sensor power-on event of the mobile terminal is triggered; and [0106]the operation that the target sensor state resetting module executes, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor includes that: [0107]in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting is executed on the corresponding sensor. [0108]FIG. 4 is a structure block diagram of a control device for sensors of a mobile terminal according to an embodiment of the application. The device may be implemented by software and/or hardware, and is integrated into a mobile terminal. As shown in FIG. 4, the device includes a to-be-enabled sensor determination module 41, a power-on delay acquisition module 42, a target sensor state resetting module 43 and a sensor data reporting module 44. [0109]The to-be-enabled sensor determination module 41 is configured to determine a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction. [0110]The power-on delay acquisition module 42 is configured to determine that a sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal. [0111]The target sensor state resetting module 43 is configured to execute, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor. [0112]The sensor data reporting module 44 is configured to determine that state resetting of the to-be-enabled sensor is completed, enable the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and report acquired data of the enabled sensor. [0113]The power-on delay acquisition module 42 is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a first power-on delay of the to-be-enabled sensor; and [0114]the target sensor state resetting module 43 is configured to execute, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor. [0115]The power-on delay acquisition module 42 is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of each sensor of the mobile terminal; and [0116]the target sensor state resetting module 43 is configured to execute, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor. [0117]The device may further include a first other sensor state resetting module, configured to, after the acquired data of the enabled sensor is reported, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0118]The device may further include a second other sensor state resetting module, configured to, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0119]The device may further include a timer starting module, configured to start a timer at the same time of determining that the sensor power-on event of the mobile terminal is triggered; and [0120]the operation that the target sensor state resetting module 43 executes, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor includes that: [0121]in response to dete(String), 相关申请的交叉引用 [0001] 本申请是2017年10月17日提交的国际专利申请PCT/CN2017/106612的国家阶段申请,要求2017年2月4日提交的中国专利申请201710065209.X的权益, 标题为“用于移动终端的传感器的控制方法和装置以及移动终端”的专利,其内容通过引用整体并入本文。 技术领域 [0002] 本发明实施例涉及数据处理技术领域,尤其涉及一种移动终端传感器的控制方法、装置、存储介质和移动终端。 背景 [0003] 手机等移动终端中集成了各种传感器,用于辅助实现手机的各种功能。 例如,可以配置环境光传感器来调节手机屏幕自动背光的亮度,可以配置接近传感器来辅助控制屏幕的开启和关闭,可以配置加速度传感器 对于计步,重力传感器可以应用于重力感应类游戏,磁场传感器可以应用于地图导航和指南针,陀螺仪可以用于控制游戏中的视角,实现惯性导航; 当没有全球定位系统(GPS)的信号时,根据物体的运动状态等。 概括 [0004] 本发明实施例提供一种移动终端传感器的控制方法、装置、存储介质和移动终端,能够提高移动终端传感器数据的上报速度。 [0005] 本申请实施例提供了一种移动终端传感器的控制方法,包括: [0006] 根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0007] 响应于检测到移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0008] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0009] 响应于检测到待使能传感器状态复位完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0010] 本申请实施例提供了一种移动终端传感器的控制装置,包括: [0011] 待启用传感器确定模块,用于根据传感器启用指令确定移动终端的传感器中的待启用传感器; [0012] 开机延时获取模块,用于响应于检测到移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,所述目标传感器至少 包括待使能的传感器,在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时; [0013] 目标传感器状态重置模块,用于响应于判断当前时刻达到目标传感器对应的开机延时,对目标传感器执行状态重置; 和 [0014] 传感器数据上报模块,用于响应于检测到待使能传感器状态复位完成,使待使能传感器变为使能传感器, 报告已启用传感器的采集数据。 [0015]本发明实施例提供了一种存储介质,该存储介质中可以存储多条指令,该指令适合处理器加载以执行本发明实施例的移动终端的传感器的控制方法。 [0016] 本发明实施例提供了一种移动终端,包括存储器、处理器以及存储在存储器中并能够在处理器上运行的计算机程序,处理器执行计算机程序以实现以下操作: [0017] 根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0018] 响应于检测到移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0019] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0020] 响应于检测到待使能传感器状态复位完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0021] 本发明实施例提供的移动终端传感器的控制方法及装置、存储介质及移动终端,可以提高移动终端传感器数据的上报速度。 附图的简要说明 [0022] 图1是根据本发明一个实施例的移动终端的传感器的控制方法的流程图; [0023] 图2是根据本发明一个实施例的移动终端的传感器的控制方法的流程图; [0024] 图3是根据本发明一个实施例的移动终端的传感器的控制方法的流程图; [0025] 图4是根据本发明一个实施例的移动终端的传感器控制装置的结构图; 和 [0026] 图5是根据本发明实施例的移动终端的结构图。 具体实施方式 [0027] 为使本申请的目的、技术方案及优点更加清楚,下面将结合附图对本申请的优选实施例作进一步地详细描述。 可以理解,此处所描述的示例性实施例仅仅用于解释本申请,并不用于限制本申请。 还需要说明的是,为便于描述,附图中并未示出全部内容,仅示出了与本申请相关的部分。 在对示例性实施例进行更详细的讨论之前需要提及的是,一些示例性实施例被描述为流程图中描述的处理或方法。 虽然在流程图中每个操作(或步骤)被描述为顺序处理,但是其中的许多操作可以并行、并发或同时执行。 此外,可以重新安排每个操作的顺序。 当操作完成时,可以终止处理,但也可能存在未包括在附图中的额外操作。 处理可以对应于方法、函数、过程、子例程、子程序等。 [0028] 当移动终端从休眠状态唤醒时,通常可以通过以下流程控制传感器:为每个传感器上电,为每个传感器等待上电延时,为每个传感器进行状态复位,使能一个或多个传感器 ,以及报告一个或多个启用的传感器的数据。 相关技术中移动终端传感器的控制方法存在缺陷,需要改进。 [0029] 本申请实施例提供了一种移动终端传感器的控制方法,包括: [0030]根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0031] 确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0032] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0033] 确定待使能传感器的状态重置完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0034] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0035] 获取待使能传感器的首次上电延时; 和 [0036] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0037] 响应于确定当前时刻达到第一上电延时,对待使能传感器执行状态重置。 [0038] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0039] 获取移动终端各传感器的开机延时; 和 [0040] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0041] 响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。 [0042] 在一种实施方式中,在上报使能传感器的获取数据的操作之后,所述方法还包括: [0043] 对移动终端中除启用的传感器外的传感器进行状态重置。 [0044] 在一个实施方式中,所述移动终端的传感器的控制方法还包括: [0045] 响应于确定当前时刻达到移动终端的传感器的最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。 [0046] 在一个实施方式中,所述移动终端的传感器的控制方法还包括: [0047] 在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0048] 响应于确定当前时刻达到各传感器中对应传感器的上电延时,对对应传感器执行状态复位的操作包括: [0049] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0050] 图1是根据本发明一个实施例的移动终端的传感器的控制方法的流程图。 本实施例的方法可以由移动终端的传感器控制装置执行。 该设备可以通过硬件和/或软件来实现。 该设备可以作为移动终端的一部分设置在移动终端中。 [0051] 如图1所示,本实施例的移动终端的传感器的控制方法包括以下操作。 [0052] 运作中 101 、根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0053]在本实施例中,移动终端包括但不限于手机、笔记本电脑、平板电脑等设备,移动终端的传感器包括但不限于环境光传感器。 、接近传感器、加速度传感器、重力传感器、磁场传感器、陀螺仪、指纹传感器、霍尔传感器、气压传感器、心跳传感器、紫外线传感器等。 [0054] 移动终端的应用程序在需要通过传感器获取数据时,可以通过移动终端的应用层向移动终端的硬件抽象层发送传感器使能指令。 例如,当移动终端从熄屏状态变为亮屏状态时,一些应用程序(例如防误触发应用程序)可以向硬件抽象层发送开启接近传感器的开启指令,以获取数据 接近传感器的实现,一些应用程序(例如背光自动调节应用程序)可以向硬件抽象层发送使能环境光传感器的使能指令,以获取环境光传感器的数据。 移动终端中的传感器有很多,可以只启用一个或多个传感器,这种类型的一个或多个传感器称为一个或多个待启用传感器。 然后,可以根据传感器启用指令确定移动终端的传感器中的一个或多个待启用传感器。 启用传感器后,可以使用传感器获取数据。 例如,通过环境光传感器获取环境光参数,通过接近传感器获取用户或其他目标物体与移动终端之间的距离参数。 其中,待启用的传感器可以是一个或多个。 [0055] 运作中 102 ,确定触发移动终端的传感器开机事件,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待使能的传感器 并且,在目标传感器为一个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0056] 触发移动终端的传感器开机事件包括移动终端从休眠状态被唤醒(例如,从熄屏状态变为亮屏状态),或者传感器被唤醒。 休眠状态或检测到传感器使能指令。 [0057] 上电延时是指从上电时刻开始,保证传感器稳定正常上电的最短时间。 每个传感器的上电延迟可能不同。 例如,环境光传感器的上电延迟为20ms,接近传感器的上电延迟为30ms,而陀螺仪的上电延迟为150ms。 [0058] 目标传感器可以是待使能传感器,也可以包括待使能传感器和其他传感器。 [0059] 运作中 103 ,判断当前时刻是否达到目标传感器对应的开机延时,如果当前时刻达到目标传感器对应的开机延时,则运行 104 被执行,否则运行 103 继续执行,直到当前时刻达到开机延时。 [0060]发明人发现移动终端中的多个传感器共用一个I2C(Inter-Integrated Circuit,I2C)和一个电源,因此在传感器上电的过程中,所有的传感器都可以同时上电。 可以选择所有传感器的开机延时中的最大开机延时作为开机延时,以保证各传感器正常开机。 例如,陀螺仪通常需要比较长的上电延时,长达150ms,而环境光传感器或接近传感器的上电延时很短,甚至不需要。 即使应用只需要使能环境光传感器,也需要延迟150ms后才能进行环境光传感器的状态复位和使能,大大延迟了环境光传感器的数据上报,降低了上报速度 的传感器数据。 [0061] 在第一个例子中,如果目标传感器包括环境光传感器和接近传感器,两者都是待使能传感器,则在开始上电20ms后对环境光传感器执行状态重置,并且 上电30ms后对接近传感器执行状态复位。 [0062] 在第二个例子中,如果目标传感器包括作为待使能传感器的环境光传感器和另一个传感器,即陀螺仪,则在开始上电20ms后对环境光传感器执行状态重置 , 陀螺仪在上电 150 ms 后进行状态清零。 [0063] 在此,部分传感器的初始状态可能会出现异常,因此需要进行状态重置,以确保已上电的传感器处于正常状态。 [0064] 运作中 104 ,在目标传感器上执行状态重置。 [0065] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态重置。 [0066] 如果目标传感器有多个,则响应于确定达到某个传感器的上电延时,对该传感器执行状态复位。 [0067] 运作中 105 ,确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0068] 在对目标传感器执行复位操作的过程中,若待使能传感器的状态复位完成,则使能待使能传感器成为使能传感器。 [0069] 在第一个例子中,在开始上电20ms后,对环境光传感器进行状态重置,响应于确定环境光传感器状态重置完成,启用环境光传感器,并获取数据 环境光传感器的报告。 同样在实施例一中,在开始上电30ms后对接近传感器执行状态复位,响应于确定接近传感器状态复位完成,使接近传感器使能,并获取接近传感器的数据。 报告接近传感器。 与在上电150ms后对接近传感器和环境光传感器进行状态重置,并使能接近传感器和环境光传感器相比,这种方式的优点是大大提高了传感器数据的上报速度。 [0070] 实施例二中,在开始上电20ms后对环境光传感器进行状态复位,响应于确定环境光传感器状态复位完成,使能环境光传感器,并获取到 报告环境光传感器的数据。 同样在第二个例子中,在开始上电150ms后对陀螺仪执行状态重置。 [0071] 需要注意的是,操作 105 可以在执行操作的过程中执行 104 也可以在操作后执行 104 被执行。 图1示例性地说明了操作的执行顺序 104 和 105 . 示例性的,若目标传感器为环境光传感器,为待使能传感器,运行后 104被执行以对环境光传感器执行状态重置,操作 105 执行判断环境光传感器的状态重置完成并启用环境光传感器。 在第二个例子中,运行后 104 执行上电后20ms对环境光传感器执行状态复位,操作 105 执行判断环境光传感器状态复位完成并启用环境光传感器,然后操作 104 重新执行,对陀螺仪进行状态清零。 [0072] 图2是根据本发明一个实施例的移动终端的传感器的控制方法的流程图。 如图2所示,本实施例提供的方法包括以下操作。 [0073] 运作中 201 、根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0074] 运作中 202 ,确定移动终端的传感器开机事件被触发,获取待使能传感器的第一次开机延时。 [0075] 当有多个待使能的传感器时,对应有多个首次上电延时。 [0076] 运作中 203 , 判断当前时刻是否到达第一个上电延时, 如果当前时刻到达第一个上电延时, 则运行 204 被执行,否则运行 203 继续执行,直到当前时刻到达第一个上电延时。 [0077] 运作中 204 , 对待使能的传感器执行状态复位。 [0078] 当存在多个首次上电延时时,响应于判断当前时刻达到某个传感器的首次上电延时,可以对该传感器执行状态复位。 [0079] 运作中 205 ,确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0080] 当有多个待启用的传感器时,响应于确定其中某个传感器的状态重置完成,立即启用该传感器。 [0081] 在上报使能传感器的获取数据的操作之后,该方法还可以包括:对移动终端中除使能传感器之外的传感器执行状态重置。 [0082] 响应于确定当前时刻移动终端的传感器达到最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。 [0083] 图3是根据本发明一个实施例的移动终端的传感器的控制方法的流程图。 如图3所示,本实施例的移动终端的传感器的控制方法包括以下操作。 [0084] 运作中 301 、根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0085] 运作中 302 ,确定触发了移动终端的传感器开机事件,获取移动终端各传感器的开机延时。 [0086] 运作中 303 ,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。 [0087] 操作 303 可以包括:每个传感器对应的每个上电延时按照上电延时由短到长的顺序确定; 将每个开机延时分别确定为当前开机延时; 响应于判断当前时刻达到当前上电延时,对当前上电延时对应的传感器进行状态复位。 [0088]示例的,移动终端的每个传感器的开机延时分别为20ms、30ms、50ms和150ms。 然后,在开始上电20ms后,对传感器执行状态复位,延时20ms,上电30ms后,对传感器执行状态复位,延时30ms。 started, sensor 执行状态复位 50 ms power-on delay 开机后 50 ms,最后 sensor 执行状态复位 150 ms power-on delay 开机后 150 ms on 开始了。 [0089] 运作中 304 ,确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0090] 在确定移动终端的传感器开机事件被触发的同时启动定时器。 相应地,操作 303 可以包括:各传感器中响应于确定定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 其中,响应于在定时器的定时值确定各传感器中对应传感器的上电延时到达,对对应传感器执行状态复位的操作可以包括: 对应的各上电延时 对每个传感器进行确定; 每次开机延时确定为当前开机延时; 响应于在定时器的定时值判断为达到当前上电延时,对当前上电延时对应的传感器进行状态复位。 [0091] 本申请实施例提供了一种移动终端传感器的控制装置,包括: [0092] 待启用传感器确定模块,用于根据传感器启用指令确定移动终端的传感器中的待启用传感器; [0093] 开机延时获取模块,用于确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,所述目标传感器至少包括: 启用传感器,在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端传感器的最大开机延时; [0094] 目标传感器状态重置模块,用于响应于判断当前时刻达到目标传感器对应的开机延时,对目标传感器执行状态重置; 和 [0095] 传感器数据上报模块,用于确定待使能传感器状态复位完成,使能待使能传感器,使待使能传感器变为使能传感器,并上报获取的数据。 启用的传感器。 [0096] 在一种实施方式中,所述开机延时获取模块,用于确定所述移动终端的传感器开机事件被触发,获取所述待使能传感器的第一开机延时; 和 [0097] 目标传感器状态重置模块,用于响应于判断当前时刻达到第一上电延时,对待使能传感器执行状态重置。 [0098] 在一种实施方式中,所述开机延时获取模块,用于确定所述移动终端的传感器开机事件被触发,获取所述移动终端各传感器的开机延时; 和 [0099] 目标传感器状态重置模块,用于响应于确定当前时刻达到各传感器中对应传感器的上电延时,执行对应传感器的状态重置。 [0100] 在一种实施方式中,该装置还包括: [0101] 第一其他传感器状态重置模块,用于在上报启用传感器的获取数据后,对移动终端中除启用传感器之外的传感器执行状态重置。 [0102]在一种实施方式中,装置还包括: [0103] 第二其他传感器状态重置模块,用于响应于确定当前时刻移动终端的传感器达到最大开机延时,对除使能的传感器之外的传感器执行状态重置。 移动终端。 [0104] 在一种实施方式中,该装置还包括: [0105] 定时器启动模块,用于在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0106] 目标传感器状态重置模块执行的操作,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器进行状态重置包括: [0107] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0108] 图4是根据本发明一个实施例的移动终端的传感器控制装置的结构框图。 该装置可以通过软件和/或硬件实现,集成在移动终端中。 如图4所示,该装置包括待使能传感器判断模块 41 , 上电延时采集模块 42 , 目标传感器状态复位模块 43 和传感器数据报告模块 44 . [0109] 待使能传感器判断模块 41 用于根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0110] 上电延时采集模块 42 用于确定移动终端的传感器开机事件被触发,并获取移动终端的目标传感器的开机延时,其中,所述目标传感器至少包括待使能的传感器,在 在目标传感器为一个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0111] 目标传感器状态复位模块 43 用于响应于确定当前时刻达到目标传感器对应的开机延时,对目标传感器执行状态复位。 [0112] 传感器数据上报模块 44 用于判断待使能传感器状态复位完成,使能待使能传感器,使待使能传感器变为使能传感器,并上报获取使能传感器的数据。 [0113] 上电延时采集模块 42 用于确定移动终端的传感器开机事件被触发,获取待启用传感器的第一开机延时; 和 [0114] 目标传感器状态复位模块 43 用于响应于判断当前时刻达到第一上电延时,对待使能传感器执行状态复位。 [0115] 上电延时采集模块 42 用于确定移动终端的传感器开机事件被触发,获取移动终端各传感器的开机延时; 和 [0116] 目标传感器状态复位模块 43 用于响应于确定当前时刻达到各传感器中对应传感器的开机延时,执行对应传感器的状态复位。 [0117] 该装置还可以包括:第一其他传感器状态重置模块,用于在上报所述使能传感器的获取数据后,对所述移动终端中除所述使能传感器之外的传感器执行状态重置。 [0118]该装置还可以包括第二其他传感器状态重置模块,用于响应于确定当前时刻达到移动终端的传感器的最大开机延时,对除传感器之外的传感器执行状态重置。 启用传感器,在移动终端。 [0119] 该装置还可以包括:定时器启动模块,用于在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0120] 目标传感器状态复位模块的操作 43 执行时,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,所述对应传感器的状态复位包括: [0121] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0122] 本发明实施例提供了一种存储介质,该存储介质中存储有多条指令,该指令适合处理器加载以执行本发明实施例的移动终端的传感器的控制方法。 本申请实施例提供了一种移动终端,包括存储器、处理器以及存储在存储器中并能够在处理器上运行的计算机程序,处理器执行计算机程序以实现以下操作: [0123] 根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0124] 确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0125] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0126] 确定待使能传感器的状态重置完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0127] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0128] 获取待使能传感器的首次上电延时; 和 [0129] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0130] 响应于确定当前时刻达到第一上电延时,对待使能传感器执行状态重置。 [0131] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0132] 获取移动终端各传感器的开机延时; 和 [0133] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0134] 响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。 [0135] 在一种实施方式中,在上报使能传感器的采集数据的操作之后,还包括以下操作: [0136] 对移动终端中除启用的传感器外的传感器进行状态重置。 [0137] 在一种实施方式中,所述移动终端还包括: [0138]响应于确定当前时刻达到移动终端的传感器的最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。 [0139] 在一种实施方式中,所述移动终端还包括: [0140] 在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0141] 响应于确定当前时刻达到各传感器中对应传感器的上电延时,对对应传感器执行状态复位的操作包括: [0142] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0143] 图5是根据本发明实施例的移动终端的结构图。 在本申请任一实施例中,移动终端可以包括移动终端传感器的控制装置。 如图5所示,该移动终端可以包括:存储器 501 和中央处理器 (CPU) 502 (也称为处理器)。 记忆 501 被配置为存储可执行程序代码。 处理器 502 读取存储在内存中的可执行程序代码 501 运行该可执行程序代码对应的程序执行以下操作: 根据传感器开启指令确定移动终端的传感器中待开启的传感器; 确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0144] 移动终端还包括:外设接口 503 , 射频 (RF) 电路 505 , 音频电路 506 , 扬声器 511 , 电源管理芯片 508 , 输入/输出 (I/O) 子系统 509 , 触摸屏 512 , 另一个输入/控制设备 510 和一个外部端口 504 ,这些组件通过一条或多条通信总线或信号线进行通信 507 . [0145] 可以理解的是,移动端 500 图中所示仅为移动端的示例,移动端 500 可以具有比图中所示的部件更多或更少的部件,可以组合两个或更多部件或者可以制作不同的部件配置。 图中所示的每个组件可以以包括一个或多个信号处理和/或专用集成电路的硬件、软件或硬件和软件的组合来实现。 [0146] 下面详细描述本实施例提供的移动终端,用于控制移动终端的传感器。 例如,移动终端为手机。 [0147] 记忆 501 : 记忆 501 可以被CPU访问 502 , 外设接口 503 之类的,还有内存 501 可以包括高速随机存取存储器(RAM),还可以包括非易失性存储器,例如,一个或多个磁盘存储设备、闪存或其他非易失性固态存储设备。 [0148] 外设接口 503 :外设接口 503 可以将设备的 I/O 外围设备连接到 CPU 502 和记忆 501 . [0149] 输入输出子系统 509 : I/O 子系统 509可以连接设备的I/O外设,例如触摸屏 512 和另一个输入/控制设备 510 到外设接口 503 . 输入输出子系统 509 可能包括一个显示控制器 5091 以及一个或多个输入控制器 5092 配置为控制其他输入/控制设备 510 . 在此,一个或多个输入控制器 5092 从其他输入/控制设备接收电信号 510 或将电信号发送到其他输入/控制设备 510 , 和另一个输入/控制设备 510 可以包括物理按钮(按压按钮和摇臂按钮)、拨盘、滑动开关、操纵杆和点击滚轮。 值得注意的是,输入控制器 5092 可以与键盘、红外端口、通用串行总线(USB)接口、鼠标等指示设备中的任意一种连接。 [0150] 触摸屏 512 : 触摸屏 512 为用户终端与用户之间的输入接口和输出接口,向用户显示视觉输出,视觉输出可以包括图形、文字、图标、视频等。 [0151] 显示控制器 5091 在 I/O 子系统中 509 从触摸屏接收电信号 512 或向触摸屏发送电信号 512 . 触摸屏 512 检测触摸屏上的接触,显示控制器 5091 将检测到的接触转换为与触摸屏上显示的用户界面对象的交互 512 实现人机交互,将用户界面对象显示在触摸屏上 512 可以是正在运行的游戏图标、连接到相应网络的图标等。 需要说明的是,该设备还可以包括光电鼠标,该光电鼠标是不显示视觉输出的触敏面,或者是触摸屏形成的触敏面的延伸。 [0152] 射频电路 505 主要用于建立手机与无线网络(即网络侧)之间的通信,以实现手机与无线网络之间的数据收发,例如短信、电子邮件的收发 . 在某些示例性实施例中,RF电路 505 接收和发送射频信号,射频信号也称为电磁信号。 射频电路 505 将电信号转换为电磁信号或将电磁信号转换为电信号,并通过电磁信号与通信网络和其他设备进行通信。 射频电路 505 可以包括被配置为执行这些功能的已知电路,并且包括但不限于天线系统、RF收发器、一个或多个放大器、调谐器、一个或多个振荡器、数字信号处理器、编码器-解码器( CODEC)芯片组、用户识别模块(SIM)等。 [0153] 音频电路 506 主要用于接收外设接口的音频数据 503 ,将音频数据转换成电信号,并将电信号发送给扬声器 511 . [0154] 演讲者 511 用于还原手机通过射频电路从无线网络接收到的语音信号 505 变成声音并向用户播放声音。 [0155] 电源管理芯片 508 配置为对CPU进行供电和电源管理 502 , I/O 子系统和与外设接口连接的硬件 503 . [0156]需要说明的是,对于本申请实施例中的移动终端传感器的控制方法,本领域普通技术人员可以理解实现该移动终端传感器控制方法的全部或部分流程。 本申请实施例中的终端,可以通过计算机程序控制相关硬件来完成。 该计算机程序可以存储在一个计算机可读取存储介质中,例如存储在内存中,由至少一个处理器执行,执行过程可以包括上述传感器的控制方法实施例的流程。 移动终端。 这里,存储介质可以是磁盘、光盘、只读存储器(Read Only Memory,ROM)、RAM等。 [0157] 以上所述仅为本申请的较佳实施例及所应用的技术原理。 本申请不限于这里描述的示例性实施例。 在不脱离本申请保护范围的情况下,本领域的技术人员可以做出各种显而易见的变更、规定和替换。 因此,本申请虽然通过上述实施例进行了详细描述,但并不限于上述实施例,在不脱离本申请的构思的前提下,还可以包括更多其他等同的实施例,本申请的范围由其所公开的范围确定。 的索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106850985A(String), CN106850985B(String), EP3579531A1(String), EP3579531A4(String), US10666789B2(String), US20200028957A1(String), WO2018141167A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106850985A(String), CN106850985B(String), EP3579531A1(String), EP3579531A4(String), US10666789B2(String), US20200028957A1(String), WO2018141167A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:56.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10666789B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.007 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106850985A(String), CN106850985B(String), EP3579531A1(String), EP3579531A4(String), US10666789B2(String), US20200028957A1(String), WO2018141167A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), CN106850985A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), CN106850985B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.226 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), EP3579531A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), EP3579531A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), US10666789B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), US20200028957A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270687(Integer), WO2018141167A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10666789B2(String), US10666789B2(String), 1590422400(Integer), 270687(Integer), 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185009(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.466 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 1(Integer), 185009(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185009(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 2(Integer), 185009(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.556 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20180139553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Operating Mobile Terminal Based on Blowing Action and Mobile Terminal(String), 基于吹气动作的移动终端操作方法及移动终端(String), US20180139553A1(String), A method for operating a mobile terminal based on a blowing action and a mobile terminal, where the mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained, an operation type is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation instruction is generated according to the operation type, and an operation corresponding to the operation instruction is performed such that a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency.(String), 一种基于吹气动作操作移动终端的方法及移动终端,所述移动终端上设置有至少两个麦克风。 当用户对至少两个麦克风吹气时,分别获取至少两个麦克风接收的声音信号的特征参数,根据获得的至少两个麦克风接收的声音信号的特征参数确定操作类型 ,根据操作类型生成操作指令,并执行与操作指令对应的操作,从而可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率 .(String), US15/570201(String), 1430150400(Integer), US20180139553A1(String), 1526486400(Integer), 美国(String), 2(Integer), 4(Integer), 3(Integer), CN103680501A | CN103955278A | US20140119568A1(String), 44(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.567 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185010(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8c08c4fc15654ed6a7effeb4187769e0.png(String), 185010(Integer), 8c08c4fc15654ed6a7effeb4187769e0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Operating Mobile Terminal Based on Blowing Action and Mobile Terminal(String), 基于吹气动作的移动终端操作方法及移动终端(String), US20180139553A1(String), A method for operating a mobile terminal based on a blowing action and a mobile terminal, where the mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained, an operation type is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation instruction is generated according to the operation type, and an operation corresponding to the operation instruction is performed such that a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency.(String), 一种基于吹气动作操作移动终端的方法及移动终端,所述移动终端上设置有至少两个麦克风。 当用户对至少两个麦克风吹气时,分别获取至少两个麦克风接收的声音信号的特征参数,根据获得的至少两个麦克风接收的声音信号的特征参数确定操作类型 ,根据操作类型生成操作指令,并执行与操作指令对应的操作,从而可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率 .(String), US15/570201(String), 1430150400(Integer), US20180139553A1(String), 1526486400(Integer), 美国(String), 2(Integer), 2(Integer), 4(Integer), 3(Integer), CN103680501A | CN103955278A | US20140119568A1(String), \20230420\8c08c4fc15654ed6a7effeb4187769e0.png(String), 44(Integer), 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 1.-24. (canceled)25. A method for operating a mobile terminal based on a blowing action, wherein the mobile terminal comprises at least two microphones, and wherein the method comprises:separately obtaining characteristic parameters of sound signals received by the at least two microphones;determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones;generating an operation instruction according to the operation type; andperforming an operation corresponding to the operation instruction.(String), 1.-24.(取消)25、一种基于吹气动作操作移动终端的方法,其中所述移动终端包括至少两个麦克风,所述方法包括:分别获取至少两个麦克风接收到的声音信号的特征参数;根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型;根据操作类型生成操作指令;和执行与操作指令对应的操作。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 26. The method according to claim 25, wherein a characteristics parameter of a sound signal comprises at least one of a start moment, input duration, or sound loudness of the sound signal received by a microphone.(String), 26.根据权利要求25所述的方法,其中声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入时长、声音响度中的至少一项。(String), 1(Integer), 1(Integer), 24(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 27. The method according to claim 25, further comprising:determining, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow; anddetermining the operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of the blown airflow.(String), 27.根据权利要求25所述的方法,还包括:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断所述至少两个麦克风接收到的声音信号是否为吹入气流的声音信号;和当所述至少两个麦克风接收到的声音信号为吹出气流的声音信号时,根据获取的所述至少两个麦克风接收到的声音信号的特征参数确定操作类型。(String), 1(Integer), 2(Integer), 24(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 28. The method according to claim 26, further comprising:determining, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow; anddetermining the operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of the blown airflow.(String), 28.根据权利要求26所述的方法,还包括:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断所述至少两个麦克风接收到的声音信号是否为吹入气流的声音信号;和当所述至少两个麦克风接收到的声音信号为吹出气流的声音信号时,根据获取的所述至少两个麦克风接收到的声音信号的特征参数确定操作类型。(String), 1(Integer), 3(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 29. The method according to claim 26, wherein the at least two microphones comprise a first microphone and a second microphone, and wherein when the characteristics parameter of the sound signal comprises the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, determining a corresponding operation type comprises:determining that the corresponding operation type is a first operation when a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal; anddetermining that the corresponding operation type is a second operation when the start moment of the second sound signal received by the second microphone is earlier than the start moment of the first sound signal received by the first microphone, and the sound loudness of the second sound signal is greater than the sound loudness of the first sound signal.(String), 29.根据权利要求26所述的方法,其中至少两个麦克风包括第一麦克风和第二麦克风,其中当声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入持续时间和声音响度时,确定相应的操作类型包括:当第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻时,确定对应的操作类型为第一操作,且第一声音信号的声音响度为大于第二声音信号的声音响度;和当第二麦克风接收到第二声音信号的开始时刻早于第一麦克风接收到第一声音信号的开始时刻时,确定对应的操作类型为第二操作,以及第二声音信号的声音响度大于第一声音信号的声音响度。(String), 1(Integer), 4(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 30. The method according to claim 25, further comprising determining, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance corresponding to the operation type, and wherein generating the operation instruction comprises generating the operation instruction according to the operation type and the operation distance.(String), 30.根据权利要求25所述的方法,还包括根据获取的所述至少两个麦克风接收到的声音信号的特征参数,确定所述操作类型对应的操作距离;其中,生成操作指令包括根据操作类型和操作距离生成操作指令。(String), 1(Integer), 5(Integer), 24(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 31. The method according to claim 29, wherein when the first microphone is disposed on a top of the mobile terminal and the second microphone is disposed at a bottom of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from top to bottom, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from bottom to top.(String), 31.根据权利要求29所述的方法,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作包括移动终端的显示内容从上到下的移动,其中,第二操作包括移动终端的显示内容由下往上的移动。(String), 1(Integer), 6(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 32. The method according to claim 29, wherein when the first microphone is disposed on a left of the mobile terminal and the second microphone is disposed on a right of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from left to right, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from right to left.(String), 32.根据权利要求29所述的方法,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作包括移动终端的显示内容从左向右移动,其中,第二操作包括移动终端的显示内容从右到左的移动。(String), 1(Integer), 7(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 33. The method according to claim 31, wherein when the first microphone is disposed on the top of the mobile terminal and the second microphone is disposed at the bottom of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and wherein an operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top.(String), 33.根据权利要求31所述的方法,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作对应的操作距离为移动终端的显示内容从顶部移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从下往上移动的距离。(String), 1(Integer), 8(Integer), 30(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 34. The method according to claim 32, wherein when the first microphone is disposed on the left of the mobile terminal and the second microphone is disposed on the right of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and wherein operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left.(String), 34.根据权利要求32所述的方法,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作对应的操作距离为移动终端的显示内容从左侧移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从右向左移动的距离。(String), 1(Integer), 9(Integer), 31(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 35. The method according to claim 31, wherein when the first microphone is disposed on the top of the mobile terminal and the second microphone is disposed at the bottom of the mobile terminal, the first operation comprises one of a page up operation, an operation of sliding from top to bottom to unblock, and a back operation, and wherein the second operation comprises one of a page down operation, an operation of sliding from bottom to top to unblock, and a forward operation.(String), 35.根据权利要求31所述的方法,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作包括向上翻页操作、从上向下滑动解锁操作,以及返回操作,其中,第二操作包括向下翻页操作、从下向上滑动解锁操作和前进操作中的一种。(String), 1(Integer), 10(Integer), 30(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 36. A mobile terminal, comprising:at least two microphones;a processor; anda memory,wherein the at least two microphones, the processor, and the memory are coupled to each other using a bus,wherein the memory is configured to store a computer program, andwherein the computer program causes the processor to be configured to:separately obtain characteristic parameters of sound signals received by the at least two microphones;determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones;generate an operation instruction according to the operation type; andperform an operation corresponding to the operation instruction.(String), 36.移动终端,包括:至少两个麦克风;处理器;和一段回忆,其中至少两个麦克风、处理器和存储器使用总线彼此耦合,其中存储器被配置为存储计算机程序,并且其中计算机程序使处理器被配置为:分别获取至少两个麦克风接收到的声音信号的特征参数;根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型;根据操作类型生成操作指令;和执行与操作指令对应的操作。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 37. The mobile terminal according to claim 36, wherein a characteristics parameter of a sound signal comprises at least one of a start moment, input duration, or sound loudness of the sound signal received by a microphone.(String), 37.根据权利要求36所述的移动终端,其中声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入时长、声音响度中的至少一项。(String), 1(Integer), 12(Integer), 35(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 38. The mobile terminal according to claim 36, wherein the computer program further causes the processor to be configured to:determine, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow; anddetermine the operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of the blown airflow.(String), 38.根据权利要求36所述的移动终端,其中计算机程序还使处理器被配置为:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断所述至少两个麦克风接收到的声音信号是否为吹入气流的声音信号;和当至少两个麦克风接收到的声音信号为吹出气流的声音信号时,根据获取的至少两个麦克风接收到的声音信号的特征参数确定操作类型。(String), 1(Integer), 13(Integer), 35(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 39. The mobile terminal according to claim 37, wherein the at least two microphones comprise a first microphone and a second microphone, and wherein when the characteristics parameter of the sound signal comprises the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, the computer program further causes the processor to be configured to:determine that the operation type is a first operation when a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal; anddetermine that the operation type is a second operation when the start moment of the second sound signal received by the second microphone is earlier than the start moment of the first sound signal received by the first microphone, and the sound loudness of the second sound signal is greater than the sound loudness of the first sound signal.(String), 39.根据权利要求37所述的移动终端,其中至少两个麦克风包括第一麦克风和第二麦克风,其中当声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入持续时间和声音响度时,计算机程序进一步使处理器配置为:当第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻,且第一声音信号的声音响度较大时,确定操作类型为第一操作比第二声音信号的声音响度;和当第二麦克风接收到第二声音信号的开始时刻早于第一麦克风接收到第一声音信号的开始时刻时,确定操作类型为第二操作,且第二声音信号的声音响度为大于第一声音信号的声音响度。(String), 1(Integer), 14(Integer), 36(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 40. The mobile terminal according to a claim 36, wherein the computer program further causes the processor to be configured to determine, according to the obtained Characteristic parameters of the sound signals received by the at least two microphones, an operation distance corresponding to the operation type, and wherein when generating the operation instruction, the computer program further causes the processor to be configured to generate the operation instruction according to the operation type and the operation distance.(String), 40.根据权利要求36所述的移动终端,其中计算机程序还使得处理器用于根据获取的至少两个麦克风接收的声音信号的特征参数,确定与操作类型对应的操作距离,其中,计算机在生成操作指令时,程序还使得处理器用于根据操作类型和操作距离生成操作指令。(String), 1(Integer), 15(Integer), 35(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 41. The mobile terminal according to claim 39, wherein when the first microphone is disposed on a top of the mobile terminal and the second microphone is disposed at a bottom of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from top to bottom, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from bottom to top.(String), 41.根据权利要求39所述的移动终端,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作包括移动终端的显示内容从上到下的移动,其中,第二操作包括移动终端的显示内容由下往上的移动。(String), 1(Integer), 16(Integer), 38(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 42. The mobile terminal according to claim 39, wherein when the first microphone is disposed on a left of the mobile terminal and the second microphone is disposed on a right of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from left to right, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from right to left.(String), 42.根据权利要求39所述的移动终端,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作包括移动终端的显示内容从左向右移动,其中,第二操作包括移动终端的显示内容从右到左的移动。(String), 1(Integer), 17(Integer), 38(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 43. The mobile terminal according to claim 41, wherein when the first microphone is disposed on the top of the mobile terminal and the second microphone is disposed at the bottom of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and wherein an operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top.(String), 43.根据权利要求41所述的移动终端,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作对应的操作距离为移动终端的显示内容从顶部移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从下往上移动的距离。(String), 1(Integer), 18(Integer), 40(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185010(Integer), 44. The mobile terminal according to claim 41, wherein when the first microphone is disposed on the left of the mobile terminal and the second microphone is disposed on the right of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and wherein an operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left.(String), 44.根据权利要求41所述的移动终端,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作对应的操作距离为移动终端的显示内容从左侧移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从右向左移动的距离。(String), 1(Integer), 19(Integer), 40(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185010(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a U.S. National Stage of International Patent Application No. PCT/CN2015/077665 filed on Apr. 28, 2015, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]Embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method for operating a mobile terminal based on a blowing action and a mobile terminal. BACKGROUND [0003]With development of mobile terminals such as smart tablet computers and smartphones, sizes of screens of the mobile terminals become increasingly large, and some limitations are caused to a screen sliding operation performed through finger touch. Especially, during a one-handed operation, it is relatively clumsy to perform a screen sliding operation using a finger, and man-machine interaction efficiency is low. [0004]As the sizes of the screens of the mobile terminals become increasingly large, design of dual microphones and multiple microphones becomes increasingly popular in these products, and is mainly used for noise reduction processing during a voice conversation. How to use these microphones to perform a screen sliding operation, simplify an existing operation mode, and improve man-machine interaction efficiency is a problem that needs to be resolved in the present disclosure. SUMMARY [0005]Embodiments of the present disclosure provide a method for operating a mobile terminal based on a blowing action and a mobile terminal such that a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency. [0006]According to a first aspect, a method for operating a mobile terminal based on a blowing action is provided, where the mobile terminal includes at least two microphones, and the method includes separately obtaining characteristic parameters of sound signals received by the at least two microphones, determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones, generating an operation instruction according to the operation type, and performing an operation that corresponds to the operation instruction. [0007]With reference to the first aspect, in a first possible implementation manner, the characteristics parameter of the sound signal includes at least one of a start moment, input duration, or sound loudness of the sound signal received by the microphone. [0008]With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the method further includes determining, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow, and performing the operation of determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of a blown airflow. [0009]With reference to the first or the second possible implementation manner of the first aspect, in a third possible implementation manner, the at least two microphones include a first microphone and a second microphone, and if the characteristics parameter of the sound signal includes the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, determining a corresponding operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones includes determining that the operation type is a first operation if a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal, or determining that the operation type is a second operation if a start moment of a second sound signal received by the second microphone is earlier than a start moment of a first sound signal received by the first microphone, and sound loudness of the second sound signal is greater than sound loudness of the first sound signal. [0010]With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner, the method further includes determining, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance that corresponds to the operation type, and generating an operation instruction according to the operation type includes generating the operation instruction according to the operation type and the operation distance. [0011]With reference to the third or the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from top to bottom, and the second operation includes a movement of the displayed content of the mobile terminal from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from left to right, and the second operation includes a movement of the displayed content of the mobile terminal from right to left. [0012]With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left. [0013]With reference to the third or the fourth possible implementation manner of the first aspect, in a seventh possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a page up operation, an operation of sliding from top to bottom to unblock, or a back operation, and the second operation includes a page down operation, an operation of sliding from bottom to top to unblock, or a forward operation, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a page up operation, an operation of sliding from left to right to unblock, or a back operation, and the second operation includes an operation of sliding from right to left to unblock, a page down operation, or a forward operation. [0014]According to a second aspect, a mobile terminal is provided, where the mobile terminal includes at least two microphones, and the mobile terminal further includes a monitoring unit configured to separately obtain characteristic parameters of sound signals received by the at least two microphones, a determining unit configured to determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones, a generation unit configured to generate an operation instruction according to the operation type, and an execution unit configured to perform an operation that corresponds to the operation instruction. [0015]With reference to the second aspect, in a first possible implementation manner, the characteristics parameter of the sound signal includes at least one of a start moment, input duration, or sound loudness of the sound signal received by the microphone. [0016]With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the mobile terminal further includes an identification unit configured to determine, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow, and the determining unit performs the operation of determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of a blown airflow. [0017]With reference to the first or the second possible implementation manner of the second aspect, in a third possible implementation manner, the at least two microphones include a first microphone and a second microphone, and if the characteristics parameter of the sound signal includes the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, the determining unit is further configured to determine that the operation type is a first operation if a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal, or determine that the operation type is a second operation if a start moment of a second sound signal received by the second microphone is earlier than a start moment of a first sound signal received by the first microphone, and sound loudness of the second sound signal is greater than sound loudness of the first sound signal. [0018]With reference to the second aspect or any one of the foregoing possible implementation manners of the second aspect, in a fourth possible implementation manner, the determining unit is further configured to determine, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance that corresponds to the operation type, and generating an operation instruction according to the operation type includes generating the operation instruction according to the operation type and the operation distance. [0019]With reference to the third or the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from top to bottom, and the second operation includes a movement of the displayed content of the mobile terminal from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from left to right, and the second operation includes a movement of the displayed content of the mobile terminal from right to left. [0020]With reference to the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left. [0021]With reference to the third or the fourth possible implementation manner of the second aspect, in a seventh possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a page up operation, an operation of sliding from top to bottom to unblock, or a back operation, and the second operation includes a page down operation, an operation of sliding from bottom to top to unblock, or a forward operation, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a page up operation, an operation of sliding from left to right to unblock, or a back operation, and the second operation includes an operation of sliding from right to left to unblock, a page down operation, or a forward operation. [0022]According to a third aspect, a mobile terminal is provided, where the mobile terminal includes at least two microphones, and the mobile terminal further includes a processor and a memory, where the at least two microphones, the processor, and the memory are connected using a bus, the memory is configured to store a computer program, and the processor is configured to perform the computer program, where the processor performs the computer program to separately obtain characteristic parameters of sound signals received by the at least two microphones, determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones, generate an operation instruction according to the operation type, and perform an operation that corresponds to the operation instruction. [0023]With reference to the third aspect, in a first possible implementation manner, the characteristics parameter of the sound signal includes at least one of a start moment, input duration, or sound loudness of the sound signal received by the microphone. [0024]With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the processor performs the computer program to determine, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow, and perform the operation of determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of a blown airflow. [0025]With reference to the first or the second possible implementation manner of the third aspect, in a third possible implementation manner, the at least two microphones include a first microphone and a second microphone, and if the characteristics parameter of the sound signal includes the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, the processor performs the computer program to determine that the operation type is a first operation if a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal, or determine that the operation type is a second operation if a start moment of a second sound signal received by the second microphone is earlier than a start moment of a first sound signal received by the first microphone, and sound loudness of the second sound signal is greater than sound loudness of the first sound signal. [0026]With reference to the third aspect or any one of the foregoing possible implementation manners of the third aspect, in a fourth possible implementation manner, the processor performs the computer program to determine, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance that corresponds to the operation type, and generating an operation instruction according to the operation type includes generating the operation instruction according to the operation type and the operation distance. [0027]With reference to the third or the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from top to bottom, and the second operation includes a movement of the displayed content of the mobile terminal from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from left to right, and the second operation includes a movement of the displayed content of the mobile terminal from right to left. [0028]With reference to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left. [0029]With reference to the third or the fourth possible implementation manner of the third aspect, in a seventh possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a page up operation, an operation of sliding from top to bottom to unblock, or a back operation, and the second operation includes a page down operation, an operation of sliding from bottom to top to unblock, or a forward operation, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a page up operation, an operation of sliding from left to right to unblock, or a back operation, and the second operation includes an operation of sliding from right to left to unblock, a page down operation, or a forward operation. [0030]The embodiments of the present disclosure provide a method for operating a mobile terminal based on a blowing action and a mobile terminal. The mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained, where the characteristics parameter includes a start moment, input duration, or sound loudness of the sound signal. An operation type (and an operation distance) is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones. An operation instruction is generated according to the operation type (and the operation distance). An operation that corresponds to the operation instruction is performed. Therefore, a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency. BRIEF DESCRIPTION OF DRAWINGS [0031]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show some embodiments of the present disclosure, and persons of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0032]FIG. 1 is a schematic flowchart of a method for operating a mobile terminal based on a blowing action according to the present disclosure, [0033]FIG. 2 is a schematic flowchart of another method for operating a mobile terminal based on a blowing action according to the present disclosure, [0034]FIG. 3A and FIG. 3B are diagrams of sound signals that correspond to different blowing directions according to an embodiment of the present disclosure, [0035]FIG. 4 is a schematic diagram of an operation effect according to an embodiment of the present disclosure, [0036]FIG. 5 is a schematic diagram of another operation effect according to an embodiment of the present disclosure. [0037]FIG. 6 is a schematic diagram of another operation effect according to an embodiment of the present disclosure, [0038]FIG. 7 is a schematic diagram of another operation effect according to an embodiment of the present disclosure, [0039]FIG. 8 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure, [0040]FIG. 9 is a schematic structural diagram of another mobile terminal according to an embodiment of the present disclosure, and [0041]FIG. 10 is a schematic structural diagram of still another mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0042]To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the following clearly and completely describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0043]An embodiment of the present disclosure provides a method for operating a mobile terminal based on a blowing action. As shown in FIG. 1, the method includes the following steps. [0044]Step 101: Separately obtain characteristic parameters of sound signals received by at least two microphones. [0045]Step 102: Determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones. [0046]The characteristic parameters of the sound signals received by the at least two microphones are parameters that can represent physical characteristics of the sound signals received by the at least two microphones. The characteristic parameters can be used to distinguish and identify different sound signals. The characteristic parameters may be start moments, input duration, and sound loudness of the sound signals received by the at least two microphones. [0047]Step 103: Generate an operation instruction according to the operation type. [0048]Step 104: Perform an operation that corresponds to the operation instruction. [0049]This embodiment of the present disclosure provides a method for operating a mobile terminal based on a blowing action. The mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained. An operation type is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones. An operation instruction is generated according to the operation type. An operation that corresponds to the operation instruction is performed. Therefore, a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency. [0050]To make persons skilled in the art understand the technical solutions provided in the embodiments of the present disclosure more clearly, the method for operating a mobile terminal based on a blowing action provided in this embodiment of the present disclosure is described below in detail using a specific embodiment. For ease of description, that a first microphone is a microphone disposed on the top of a mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal is used as an example. As shown in FIG. 2, the method includes the following steps. [0051]Step 201: The mobile terminal identifies whether the mobile terminal is in an automatic-screen-sliding scenario. [0052]In this embodiment of the present disclosure, “screen sliding” may be construed as a movement of content displayed on a screen of the mobile terminal. The movement includes, but is not limited to touch unblock, sliding unblock, an up/down movement or a left/right movement of the displayed content, page up, and page down. The automatic-screen-sliding scenario may be construed as a scenario in which the foregoing “screen sliding” operation can be performed without needing a touch operation by a user. [0053]For example, in an implementation manner, an on-off key may be set on a drop-down (or may be another direction) notification bar of the terminal to make it convenient for the user to turn off or on the on-off key. When the user enables an automatic-screen-sliding function using the on-off key, the mobile terminal determines that the mobile terminal is currently in the automatic-screen-sliding scenario. Otherwise, the mobile terminal determines that the mobile terminal is not in the automatic-screen-sliding scenario. [0054]Alternatively, in another implementation manner, an automatic-screen-sliding function may be set in advance to be associated with some application programs. These application programs may be application programs, such as a browser, a reading application, and a video application, that the user wants to operate without any hand blocking the screen. In this way, when the user runs the foregoing application programs on the mobile terminal, the mobile terminal determines that the mobile terminal is currently in the automatic-screen-sliding scenario, and after these application programs are exited, the mobile terminal determines that the mobile terminal is not currently in the automatic-screen-sliding scenario. [0055]Alternatively, in another implementation manner, a preset enabling gesture and a preset disabling gesture may be associated with an automatic-screen-sliding function. When a user gesture received by the mobile terminal is consistent with the enabling gesture, it is determined that the mobile terminal is currently in the automatic-screen-sliding scenario, and when a user gesture received by the mobile terminal in the automatic-screen-sliding scenario is consistent with the disabling gesture, the mobile terminal determines that the mobile terminal is not currently in the automatic-screen-sliding scenario. [0056]The foregoing several manners are only examples, and the present disclosure includes, but is not limited to the foregoing several manners. In addition, another possible manner may be used to identify whether the mobile terminal is in the automatic-screen-sliding scenario, and examples are not separately provided herein. [0057]If it is identified that the mobile terminal is in the automatic-screen-sliding scenario, step 202 is performed, otherwise, step 201 continues to be performed. [0058]Step 202: The mobile terminal turns on the first microphone and the second microphone. [0059]Step 203: The mobile terminal detects whether the first microphone and the second microphone both receive sound signals, and if the first microphone and the second microphone both receive sound signals, step 204 is performed, otherwise, step 203 continues to be performed. [0060]Step 204: The mobile terminal separately obtains a characteristics parameter of a first sound signal received by the first microphone and a characteristics parameter of a second sound signal received by the second microphone. [0061]The characteristic parameters of the first sound signal and the second sound signal include at least one of start moments, input duration, and sound loudness of the first sound signal and the second sound signal. When the user blows air to the first microphone and the second microphone, an airflow signal should have a particular strength (for example, loudness of a sound signal reaches a particular decibel (dB) value) and stability (for example, the sound signal needs to exist for a period of time). In addition, the first sound signal and the second sound signal should be relevant, but a difference lies in that the first sound signal and the second sound signal have different start moments and different sound loudness when air is blown in different directions. Therefore, the following steps may be used to determine whether the first sound signal and the second sound signal are sound signals that are generated by the user by blowing air. [0062]Step 205: The mobile terminal determines, according to relevancy between the characteristic parameters of the first sound signal and the second sound signal, whether the first sound signal and the second sound signal are sound signals of a blown airflow. [0063]For example, the characteristics parameter of the sound signal may include the start moment, the input duration, and the sound loudness of the sound signal. Before it is determined, using the relevancy between the characteristic parameters of the first sound signal and the second sound signal, whether the first sound signal and the second sound signal are sound signals of a blown airflow, screening may be first performed using the input duration of the first sound signal and the input duration of the second sound signal in order to reduce processing complexity. A specific method is as follows. [0064]After the first microphone and the second microphone respectively receive the first sound signal and the second sound signal, the input duration of the first sound signal and the input duration of the second sound signal may be f(String), 相关申请的交叉引用 [0001] 本申请为2015年4月28日提交的美国国家阶段国际专利申请PCT/CN2015/077665,其全部内容通过引用并入本文。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种基于吹气动作的移动终端操作方法及移动终端。 背景 [0003] 随着智能平板电脑、智能手机等移动终端的发展,移动终端的屏幕尺寸越来越大,对通过手指触摸进行的屏幕滑动操作造成了一定的限制。 尤其是单手操作时,用手指进行屏幕滑动操作比较笨拙,人机交互效率低。 [0004] 随着移动终端的屏幕尺寸越来越大,双麦克风和多麦克风的设计在这些产品中越来越流行,主要用于语音通话时的降噪处理。 如何利用这些麦克风进行屏幕滑动操作,简化现有的操作方式,提高人机交互效率,是本发明需要解决的问题。 概括 [0005] 本发明实施例提供一种基于吹气动作的移动终端操作方法及移动终端,可以通过移动终端上的麦克风对移动终端进行操作,简化现有操作方式,提高人机交互效率。 . [0006] 根据第一方面,提供一种基于吹气动作操作移动终端的方法,所述移动终端包括至少两个麦克风,所述方法包括分别获取所述至少两个麦克风接收的声音信号的特征参数, 根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型,根据操作类型生成操作指令,执行与操作指令对应的操作。 [0007] 结合第一方面,在第一种可能的实现方式中,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一个。 [0008] 结合第一方面或第一方面的第一种可能的实现方式,在第二种可能的实现方式中,所述方法还包括:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断是否 所述至少两个麦克风接收到的声音信号为吹出气流的声音信号,当所述至少两个麦克风接收到的声音信号时,根据获得的所述至少两个麦克风接收到的声音信号的特征参数,执行确定操作类型的操作。 至少两个麦克风为吹出气流的声音信号。 [0009]结合第一方面的第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述至少两个麦克风包括第一麦克风和第二麦克风,如果所述声音信号的特征参数包括所述起始时刻 、输入时长和麦克风接收的声音信号的声音响度,根据获得的至少两个麦克风接收的声音信号的特征参数确定对应的操作类型包括确定操作类型为第一操作 如果第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度, 或者如果接收到第二声音信号的开始时刻,则确定操作类型为第二操作b y 第二麦克风早于第一麦克风接收第一声音信号的开始时刻,第二声音信号的声音响度大于第一声音信号的声音响度。 [0010] 结合第一方面或第一方面的上述任一种可能的实现方式,在第四种可能的实现方式中,所述方法还包括:根据获取的所述至少两个麦克风接收的声音信号的特征参数确定 ,对应于操作类型的操作距离,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0011] 结合第一方面的第三种或第四种可能的实现方式,在第五种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 移动终端,第一操作包括移动终端显示内容从上到下移动,第二操作包括移动终端显示内容从下到上移动,或者如果第一麦克风为麦克风 设置在移动终端左侧,第二麦克风为设置在移动终端右侧的麦克风,第一操作包括移动终端的显示内容从左向右移动,第二操作包括移动终端的移动。 移动终端的显示内容从右到左。 [0012] 结合第一方面的第五种可能的实现方式,在第六种可能的实现方式中,如果第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风 ,第一操作对应的操作距离为移动终端的显示内容从上到下移动的距离,第二操作对应的操作距离为移动终端的显示内容的移动距离 从下向上移动,或者如果第一麦克风为设置在移动终端左侧的麦克风,第二麦克风为设置在移动终端右侧的麦克风,则第一操作对应的操作距离为距离 移动终端的显示内容从左向右移动的距离,以及对应第二个的操作距离 操作是移动终端的显示内容从右向左移动的距离。 [0013]结合第一方面的第三种或第四种可能的实现方式,在第七种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 所述移动终端,所述第一操作包括上翻页操作、从上往下滑动解锁操作或返回操作,所述第二操作包括下翻页操作、从下往上滑动解锁操作, 或者前向操作,或者如果第一麦克风是设置在移动终端左侧的麦克风,第二麦克风是设置在移动终端右侧的麦克风,则第一操作包括向上翻页操作、滑动操作 从左到右解除阻塞或返回操作,第二操作包括从右向左滑动解除阻塞操作、向下翻页操作或前进操作 操作。 [0014] 第二方面,提供一种移动终端,所述移动终端包括至少两个麦克风,所述移动终端还包括监测单元,用于分别获取所述至少两个麦克风接收的声音信号的特征参数,确定 单元,用于根据获取的所述至少两个麦克风接收的声音信号的特征参数确定操作类型; 生成单元,用于根据所述操作类型生成操作指令; 执行单元,用于执行以下操作: 对应操作说明。 [0015] 结合第二方面,在第一种可能的实现方式中,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一个。 [0016] 结合第二方面或第二方面的第一种可能的实现方式,在第二种可能的实现方式中,所述移动终端还包括识别单元,用于根据所述接收到的声音信号的特征参数之间的相关性确定 至少两个麦克风, 所述至少两个麦克风接收的声音信号是否为吹出气流的声音信号, 判断单元根据获取的所述麦克风接收的声音信号的特征参数执行判断操作类型的操作。 当至少两个麦克风接收到的声音信号为吹出气流的声音信号时,至少两个麦克风。 [0017] 结合第二方面的第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述至少两个麦克风包括第一麦克风和第二麦克风,如果所述声音信号的特征参数包括起始时刻 、输入时长、麦克风接收到的声音信号的声音响度,判断单元还用于如果第一麦克风接收到的第一声音信号的开始时刻较早,则判断操作类型为第一操作。 大于第二麦克风接收的第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度,或者如果 第二麦克风接收到的第二声音信号早于第一麦克风接收到的第一声音信号的开始时刻,并且声音 第二声音信号的响度大于第一声音信号的响度。 [0018] 结合第二方面或第二方面的上述任一种可能的实现方式,在第四种可能的实现方式中,所述确定单元,还用于根据获取的所述终端接收到的声音信号的特征参数,确定 至少两个麦克风,操作距离对应操作类型,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0019] 结合第二方面的第三种或第四种可能的实现方式,在第五种可能的实现方式中,如果第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 移动终端,第一操作包括移动终端显示内容从上到下移动,第二操作包括移动终端显示内容从下到上移动,或者如果第一麦克风为麦克风 设置在移动终端左侧,第二麦克风为设置在移动终端右侧的麦克风,第一操作包括移动终端的显示内容从左向右移动,第二操作包括移动终端的移动。 移动终端显示的内容从右到左。 [0020] 结合第二方面的第五种可能的实现方式,在第六种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风 ,第一操作对应的操作距离为移动终端的显示内容从上到下移动的距离,第二操作对应的操作距离为移动终端的显示内容的移动距离 从下向上移动,或者如果第一麦克风为设置在移动终端左侧的麦克风,第二麦克风为设置在移动终端右侧的麦克风,则第一操作对应的操作距离为距离 移动终端的显示内容从左到右移动的距离,以及对应第二个的操作距离 操作是移动终端的显示内容从右向左移动的距离。 [0021] 结合第二方面的第三种或第四种可能的实现方式,在第七种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 所述移动终端,所述第一操作包括上翻页操作、从上往下滑动解锁操作或返回操作,所述第二操作包括下翻页操作、从下往上滑动解锁操作, 或者前向操作,或者如果第一麦克风是设置在移动终端左侧的麦克风,第二麦克风是设置在移动终端右侧的麦克风,则第一操作包括向上翻页操作、滑动操作 从左到右解锁或返回操作,第二操作包括从右到左滑动解锁操作、向下翻页操作或向前 手术。 [0022] 第三方面,提供了一种移动终端,所述移动终端包括至少两个麦克风,所述移动终端还包括处理器和存储器,所述至少两个麦克风、所述处理器和所述存储器通过以下方式连接。 总线,存储器用于存储计算机程序,处理器用于执行计算机程序,处理器执行计算机程序分别获取至少两个麦克风接收的声音信号的特征参数,确定操作 根据获取的至少两个麦克风接收的声音信号的特征参数进行类型,根据操作类型生成操作指令,执行与操作指令对应的操作。 [0023] 结合第三方面,在第一种可能的实现方式中,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一个。 [0024]结合第三方面或第三方面的第一种可能的实现方式,在第二种可能的实现方式中,处理器执行计算机程序,根据至少两个接收到的声音信号的特征参数之间的相关性确定 麦克风,所述至少两个麦克风接收到的声音信号是否为吹出气流的声音信号,并根据获得的所述至少两个麦克风接收到的声音信号的特征参数,在发出声音时,执行确定操作类型的操作。 至少两个麦克风接收到的信号为吹出气流的声音信号。 [0025] 结合第三方面的第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述至少两个麦克风包括第一麦克风和第二麦克风,如果所述声音信号的特征参数包括所述起始时刻 、输入持续时间以及麦克风接收到的声音信号的声音响度,处理器执行计算机程序,如果第一麦克风接收到的第一声音信号的开始时刻较早,则确定操作类型为第一操作。 大于第二麦克风接收的第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度,或者如果 第二麦克风接收到的第二声音信号早于第一麦克风接收到的第一声音信号的开始时刻,并且声音 第二声音信号的响度大于第一声音信号的响度。 [0026] 结合第三方面或第三方面的上述任一种可能的实现方式,在第四种可能的实现方式中,处理器执行计算机程序,根据获取的终端接收的声音信号的特征参数确定 至少两个麦克风,操作距离对应操作类型,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0027] 结合第三方面的第三种或第四种可能的实现方式,在第五种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 移动终端,第一操作包括移动终端显示内容从上到下移动,第二操作包括移动终端显示内容从下到上移动,或者如果第一麦克风为麦克风 设置在移动终端左侧,第二麦克风为设置在移动终端右侧的麦克风,第一操作包括移动终端的显示内容从左向右移动,第二操作包括移动终端的移动。 移动终端的显示内容从右到左。 [0028] 结合第三方面的第五种可能的实现方式,在第六种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风 ,第一操作对应的操作距离为移动终端的显示内容从上到下移动的距离,第二操作对应的操作距离为移动终端的显示内容的移动距离 从下向上移动,或者如果第一麦克风为设置在移动终端左侧的麦克风,第二麦克风为设置在移动终端右侧的麦克风,则第一操作对应的操作距离为距离 移动终端的显示内容从左向右移动的距离,以及对应第二个的操作距离 操作是移动终端的显示内容从右向左移动的距离。 [0029] 结合第三方面的第三种或第四种可能的实现方式,在第七种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 所述移动终端,所述第一操作包括上翻页操作、从上往下滑动解锁操作或返回操作,所述第二操作包括下翻页操作、从下往上滑动解锁操作, 或者前向操作,或者如果第一麦克风是设置在移动终端左侧的麦克风,第二麦克风是设置在移动终端右侧的麦克风,则第一操作包括向上翻页操作、滑动操作 从左到右解除阻塞或返回操作,第二操作包括从右向左滑动解除阻塞操作、向下翻页操作或前进操作 操作。 [0030] 本发明实施例提供一种基于吹气动作的移动终端操作方法及移动终端。 移动终端设置有至少两个麦克风。 当用户对至少两个麦克风吹气时,分别获取至少两个麦克风接收到的声音信号的特征参数,该特征参数包括声音信号的起始时刻、输入时长或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离)。 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率。 附图说明 [0031] 为了更清楚地描述本发明实施例中的技术方案,下面对描述实施例所需的附图进行简单说明。 以下描述中的附图示出了本发明的一些实施例,本领域普通技术人员在没有做出创造性劳动的情况下仍可以从这些附图中导出其他附图。 [0032] 图1为本发明基于吹气动作操作移动终端的方法流程示意图, [0033] 图2为本发明另一种基于吹气动作操作移动终端的方法流程示意图; [0034] 图3A和图3B是根据本发明实施例的不同吹气方向对应的声音信号示意图, [0035] 图4为本发明实施例的操作效果示意图, [0036] 图5为本发明实施例提供的另一种操作效果示意图。 [0037] 图6为本发明实施例提供的另一种操作效果示意图, [0038] 图7为本发明实施例提供的另一种操作效果示意图, [0039] 图8为本发明实施例提供的一种移动终端的结构示意图, [0040] 图9为本发明实施例提供的另一种移动终端的结构示意图, [0041] 图10为本发明实施例提供的又一种移动终端的结构示意图。 具体实施方式 [0042]为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。 以上所述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0043] 本发明实施例提供一种基于吹气动作的移动终端操作方法。 如图1所示,该方法包括以下步骤。 [0044] 步 101 :分别获取至少两个麦克风接收到的声音信号的特征参数。 [0045] 步 102 :根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型。 [0046] 至少两个麦克风接收到的声音信号的特征参数是能够代表至少两个麦克风接收到的声音信号的物理特性的参数。 特征参数可用于区分和识别不同的声音信号。 特征参数可以是至少两个麦克风接收到的声音信号的起始时刻、输入时长和声音响度。 [0047] 步 103 :根据操作类型生成操作指令。 [0048] 步 104 :执行与操作指令对应的操作。 [0049] 本发明实施例提供一种基于吹气动作的移动终端操作方法。 移动终端设置有至少两个麦克风。 当用户向至少两个麦克风吹气时,分别获得至少两个麦克风接收到的声音信号的特征参数。 根据获得的至少两个麦克风接收的声音信号的特征参数确定操作类型。 根据操作类型生成操作指令。 执行对应于操作指令的操作。 因此,可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率。 [0050] 为使本领域技术人员更加清楚地理解本发明实施例提供的技术方案,下面以具体的方式对本发明实施例提供的基于吹气动作的移动终端操作方法进行详细说明。 体现。 为了便于描述,以第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风为例进行说明。 如图2所示,该方法包括以下步骤。 [0051] 步 201 :移动终端识别移动终端是否处于自动滑屏场景。 [0052] 在本发明实施例中,“屏幕滑动”可以理解为移动终端屏幕上显示的内容的移动。 移动包括但不限于触摸解锁、滑动解锁、显示内容的上下移动或左右移动、上翻页和下翻页。 自动滑屏场景可以理解为无需用户进行触摸操作即可进行上述“滑屏”操作的场景。 [0053]例如,在一种实施方式中,可以在终端的下拉(或者可以是其他方向)通知栏上设置开关键,以方便用户对开关键进行关闭或打开。 . 当用户通过开关键开启自动滑屏功能时,移动终端确定移动终端当前处于自动滑屏场景。 否则,移动终端确定移动终端不处于自动滑屏场景。 [0054] 或者,在另一种实施方式中,可以预先设置自动滑屏功能与一些应用程序相关联。 这些应用程序可以是用户想要在没有任何手遮挡屏幕的情况下操作的应用程序,例如浏览器、阅读应用、视频应用等。 这样,当用户在移动终端上运行上述应用程序时,移动终端确定移动终端当前处于自动滑屏场景,退出这些应用程序后,移动终端确定 移动端目前不在自动滑屏场景。 [0055] 或者,在另一种实施方式中,可以将预设的启用手势和预设的禁用手势与自动滑屏功能相关联。 当移动终端接收到的用户手势与启用手势一致时,确定移动终端当前处于自动滑屏场景,当移动终端接收到的用户手势处于自动滑屏场景时 滑动场景与禁用手势一致,移动终端判断移动终端当前不在自动滑屏场景。 [0056] 上述几种方式仅为示例,本发明包括但不限于上述几种方式。 此外,还可以采用其他可能的方式来识别移动终端是否处于自动滑屏场景,在此不再一一举例。 [0057] 如果识别出移动终端处于自动滑屏场景,则步骤 202 执行,否则,步骤 201 继续执行。 [0058] 步 202 :移动终端开启第一麦克风和第二麦克风。 [0059] 步 203 :移动终端检测第一麦克风和第二麦克风是否都接收到声音信号,如果第一麦克风和第二麦克风都接收到声音信号,则步骤 204 执行,否则,步骤 203 继续执行。 [0060] 步 204 :移动终端分别获取第一麦克风接收的第一声音信号的特征参数和第二麦克风接收的第二声音信号的特征参数。 [0061] 第一声​​音信号和第二声音信号的特征参数包括第一声音信号和第二声音信号的起始时刻、输入时长和声音响度中的至少一个。 当用户向第一麦克风和第二麦克风吹气时,气流信号应该具有特定的强度(例如,声音信号的响度达到特定的分贝(dB)值)和稳定性(例如,声音信号需要 存在一段时间)。 另外,第一声音信号和第二声音信号应该是相关的,但区别在于第一声音信号和第二声音信号在不同方向吹气时的起始时刻不同,声音响度也不同。 因此,可以通过以下步骤来判断第一声音信号和第二声音信号是否为用户通过吹气产生的声音信号。 [0062] 步 205 :移动终端根据第一声音信号和第二声音信号的特征参数的相关性判断第一声音信号和第二声音信号是否为吹出气流的声音信号。 [0063]例如,声音信号的特征参数可以包括声音信号的开始时刻、输入时长、声音响度。 在确定第一声音信号和第二声音信号的特征参数之间的相关性,第一声音信号和第二声音信号是否为吹出气流的声音信号之前,可以先使用输入的时长进行筛选 第一声​​音信号的输入时间和第二声音信号的输入时长,以降低处理复杂度。 具体方法如下。 [0064] 在第一麦克风和第二麦克风分别接收到第一声音信号和第二声音信号后,可以先将第一声音信号的输入时长和第二声音信号的输入时长与预设时长进行比较。 [0065] 如果第一声音信号的输入持续时间和第二声音信号的输入持续时间小于预设持续时间,则确定第一声音信号和第二声音信号不是吹出气流的声音信号。 [0066] 第一声​​音信号和第二声音信号可以是吹出气流的声音信号,为了保证第一声音信号和第二声音信号的输入时长和输入时长为 第二声音信号大于或等于预设时长。 [0067] 相关性是指两个对象之间的相关程度,一般可以用百分比来表示。 因此,第一声音信号和第二声音信号之间的相关性可以被解释为第一声音信号和第二声音信号之间的相关程度。 [0068] 例如,第一声音信号和第二声音信号的特征参数还可以包括第一声音信号和第二声音信号的频率。 因此,可以得到第一声音信号的频率和第二声音信号的频率,并根据第一声音信号的频率和第二声音信号的频率计算第一声音信号和第二声音信号的相关度。 第二个声音信号。 当用户向第一麦克风和第二麦克风吹气时,只有一个声源。 因此,如果第一声音信号和第二声音信号是吹出气流的声音,则第一声音信号和第二声音信号的频率应该相同或者误差很小。 因此,获得的相关性应该等于 1 或大约为 1。 [0069] 或者,可以根据第一声音信号的声音响度在一段时间内的变化趋势和第二声音信号的声音响度在一段时间内的变化趋势计算第一声音信号与第二声音信号的相关度。 同时。 可以通过获得第一声音信号的声音响度值和 采样时间内多个采样点的第二个声音信号。 当变化趋势越接近时,相关度也越接近1。或者,可以通过比较第一声音信号在一段时间内的声音响度波形得到第一声音信号与第二声音信号的相关度。 具有第二声音信号的声音响度的波形。 波形越接近,相关度也越接近1。采样时间和时间段可以是第一声音信号和第二声音信号的输入时长,也可以是小于输入时长的一段时间。 [0070] 当然,为了更准确的识别,上述两种方法可以结合使用。 此外,上述以频率和声音响度计算相关度的方法仅为示例,还可以使用其他可用于评估两个声音信号之间的相关度的参数。 [0071]在获得第一声音信号和第二声音信号的相关度后,可以将获得的相关度与预设的相关度阈值进行比较。 [0072] 当获得的相关度大于或等于相关度阈值时,确定第一声音信号和第二声音信号为被吹出的气流产生的声音信号,否则确定第一声音信号和第二声音 信号不是由吹出的气流产生的声音信号。 这样可以排除其他原因产生的声音信号,避免误操作。 [0073] 在确定第一声音信号和第二声音信号是由吹出的气流产生的声音信号后,步骤 206 执行,否则返回步骤 203 . [0074] 步 206 :移动终端根据获取的第一声音信号和第二声音信号的特征参数确定操作类型,第一声音信号和第二声音信号的特征参数包括开始时刻、输入时长和声音响度。 第一声​​音信号和第二声音信号。 [0075] 进一步地,当空气吹向不同方向时,第一声音信号和第二声音信号具有不同的开始时刻和不同的声音响度。 例如,当移动终端从下向上吹空气时,第二麦克风首先接收到声音信号,由于用户的嘴巴距离第二麦克风较近,因此第二麦克风接收到的第二声音信号的响度较大。 第二麦克风大于第一麦克风接收的第一声音信号的响度。 反之,当移动终端从上往下吹气时,第一麦克风首先接收到声音信号,由于用户的嘴巴距离第一麦克风较近,因此第一麦克风接收到的第一声音信号的响度较大。 第一麦克风大于第二麦克风接收到的第二声音信号的响度。 [0076] 因此,可以根据获得的第一声音信号和第二声音信号的起始时刻和声音响度来确定吹气方向。 图3A和图3B为本发明实施例的不同吹气方向对应的声音信号示意图。 [0077] 首先,如图3B所示,如果第一声音信号的开始时刻早于第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度, 确定用户从移动终端的上向下吹气,从而可以确定操作类型为第一操作。 [0078] 如图3A所示,若第二声音信号的起始时刻早于第一声音信号的起始时刻,且第二声音信号的声音响度大于第一声音信号的声音响度,则为 确定用户从移动终端的底部向顶部吹气,从而可以确定操作类型为第二操作。 [0079] 需要说明的是,由于第一声音信号和第二声音信号的声音响度可能在第一声音信号和第二声音信号的整个输入时长内发生波动,因此可以采用以下方法来比较第一声音信号和第二声音信号的声音响度 声音信号和第二声音信号。 [0080] 如果第一个声音信号在时刻 t 的声音响度 1 大于第二个声音信号在t时刻的声音响度 2 ,则确定第一声音信号的声音响度大于第二声音信号的声音响度。 时刻 t 1 是第一个声音信号的输入持续时间内的任何时刻,时刻 t 之间的差 2 和时刻 t 1 为Δt,Δt为第二声音信号的起始时刻与第一声音信号的起始时刻之差。 [0081] 同样,如果第二个声音信号在时刻 t 的声音响度 2大于第一个声音信号在时刻 t 的声音响度 1 ,第二声音信号的声音响度大于第一声音信号的声音响度。 时刻 t 2 是第二声音信号输入持续时间内第二声音信号的任何时刻,时刻t之间的差 1 和时刻 t 2 为Δt,Δt为第一声音信号的起始时刻与第二声音信号的起始时刻之差。 [0082] 或者,可以从第一声音信号和第二声音的整个输入持续时间中选择第一声音信号和第二声音信号都稳定的时间段,例如图3A和图3B中的时间段T。 信号。 如果在T内任意时刻第一声音信号的声音响度大于第二声音信号的声音响度,则确定第一声音信号的声音响度大于第二声音信号的声音响度。 如果在T内任意时刻第二声音信号的声音响度大于第一声音信号的声音响度,则确定第二声音信号的声音响度大于第一声音信号的声音响度。 [0083] 例如,可以根据需要预先配置第一操作和第二操作的具体内容。 第一操作对应于从移动终端的顶部到底部的吹气,第二操作对应于从移动终端的底部到顶部的吹气。 例如,第一操作可以是移动终端的显示内容从上到下的移动,或者是翻页操作,或者是从上到下滑动解锁的操作(可以理解为移动的操作) 在锁定屏幕界面中从上到下的滑块解锁)。 例如,如图4所示,第一操作是显示内容从上到下的移动,或者第一操作可以是浏览器或类似应用程序运行过程中的后退操作(图4未示出)。 [0084] 第二操作可以是移动终端的显示内容从下往上移动,也可以是向下翻页操作,或者是从下往上滑动解锁的操作(可以理解为滑块从下往上移动的操作)。 在锁屏界面从下到上解锁)。 例如,如图5所示,第二操作是显示内容从下向上移动,或者第二操作可以是浏览器或类似应用程序运行过程中的前进操作(图5未示出)。 [0085] 该方法还可以包括以下步骤。 [0086] 步 207 :移动终端根据获取的第一声音信号和第二声音信号的特征参数,确定操作类型对应的操作距离。 操作距离可以称为操作路径。 [0087] 例如,当第一操作是移动终端的显示内容从上到下移动或者从上到下滑动解锁操作,第二操作是移动终端的显示内容从上往下移动时 从下到上或从下到上滑动解锁的操作,还需要获取操作距离。 [0088] 以第一操作为移动终端的显示内容自上而下移动为例,第一操作对应的操作距离为移动终端的显示内容自下而上移动的距离 . 同样,当第二操作为移动终端的显示内容从下向上移动时,第二操作对应的操作距离为移动终端的显示内容从下向上移动的距离。 [0089]由于显示内容移动的距离可以用像素值来衡量,因此第一操作对应的操作距离可以是移动终端的显示内容从下到上需要移动的像素值, 第二操作对应的操作距离可以是移动终端的显示内容从下向上移动所需的像素值。 [0090] 同理,当第一操作为上下滑动解锁操作时,第一操作对应的操作距离为解锁界面中的滑块需要上下移动的像素值。 当第二操作为从下向上滑动解锁操作时,第二操作对应的操作距离为解锁界面中的滑块需要从下向上移动的像素值。 [0091] 另外,可以根据第一声音信号的输入时长或第二声音信号的输入时长中的至少一个来确定第一操作或第二操作对应的操作距离。 以像素值为例,可以直接根据第一声音信号的输入时长和第二声音信号的输入时长确定需要移动的像素值的大小。 例如,可以预设不同输入时长对应的待移动像素值,也可以预设每单位时长对应的单位像素值。 在得到第一声音信号的输入时长和第二声音信号的输入时长后,可以根据输入时长得到对应的待移动像素值。 如果声音信号是用户通过吹气产生的,则第一声音信号的输入持续时间和第二声音信号的输入持续时间应该相等或有很小的误差。 因此,在计算时,需要使用第一声音信号或第二声音信号中的至少一个的输入时长。 [0092] 步 208 :移动终端根据操作类型生成操作指令。 [0093] 当然,如果存在与确定的操作类型对应的操作距离,则需要根据操作类型和操作距离生成操作指令。 [0094] 步 209 :移动终端执行与操作指令对应的操作。 [0095] 可选地,作为另一种实施方式,在本实施例中,第一麦克风可以是设置在移动终端左侧的麦克风,第二麦克风可以是设置在移动终端右侧的麦克风。 [0096] 在这种情况下,相应地,第一操作对应于移动终端从左到右的吹气,第二操作对应于移动终端的从右到左的吹气。 例如,第一操作可以是移动终端的显示内容从左向右移动,或者是向上翻页操作,或者是从左向右滑动解锁的操作(可以理解为移动的操作)。 在锁定屏幕界面中从左到右的滑块解锁)。 例如,如图6所示,第一操作是显示内容从左向右移动,或者第一操作可以是浏览器或类似应用程序运行过程中的后退操作(图6中未示出)。 [0097] 第二操作可以是移动终端的显示内容从右向左移动,也可以是向下翻页操作,或者是从右向左滑动解除阻塞的操作(可以理解为从 在锁屏界面从右到左解锁)。 例如,如图7所示,第二操作是移动终端的显示内容从右向左移动,或者第二操作可以是浏览器运行过程中的前进操作(图7中未示出),或者 类似的应用程序。 [0098]另外,当第一麦克风和第二麦克风设置在移动终端的左右两侧时,基于吹气动作操作移动终端的方法与上述第一麦克风和第二麦克风的方法相同。 第二麦克风设置在移动终端的顶部和底部。 [0099] 此外,需要注意的是,步骤 204 其中,移动终端分别获取第一麦克风接收到的第一声音信号的特征参数和第二麦克风接收到的第二声音信号的特征参数可以周期性地执行。 即每隔一段预设时间,获取第一声音信号的特征参数和第二声音信号的特征参数,剩下的步骤 205 迈出一步 209 执行。 [0100] 预设时间可以设置得很短,例如200毫秒(ms)。 也就是步 203 迈出一步 209 每 200 ms 执行一次。 这样,移动终端可以在用户吹气的同时进行操作。 在显示内容从下到上移动的例子中,移动终端的显示内容可以在用户吹气的同时从下到上移动,当用户停止吹气时,移动终端的显示内容可以从下到上移动。 移动终端也停止移动。 这更便于用户控制操作过程。 [0101] 本发明实施例提供一种基于吹气动作的移动终端操作方法。 移动终端设置有至少两个麦克风。 当用户向至少两个麦克风吹气时,分别获得至少两个麦克风接收到的声音信号的特征参数。 特征参数包括声音信号的开始时刻、输入持续时间或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离)。 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率。 [0102] 本发明实施例提供一种移动终端 01 . 移动终端 01 包括至少两个麦克风 010 . 如图8所示,移动终端 01 还包括一个监控单元 011 用于分别获取至少两个麦克风接收到的声音信号的特征参数 010 , 确定单元 012 用于根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型 010 , 一个生成单元 013 用于根据操作类型生成操作指令,以及执行单元 014 用于执行与所述操作指令对应的操作。 [0103] 可选地,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一种。 [0104] 可选的,如图9所示,移动终端 01 还包括识别单元 015 用于根据至少两个麦克风接收到的声音信号的特征参数之间的相关性确定 010 , 至少两个麦克风是否接收到声音信号 010 为吹出气流的声音信号,判断单元 012 根据获得的至少两个麦克风接收的声音信号的特征参数,执行确定操作类型的操作 010 当至少两个麦克风接收到声音信号时 010 是吹出气流的声音信号。 [0105]可选地,至少两个麦克风 010 包括第一麦克风和第二麦克风,如果声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入时长和声音响度,则在根据获得的特征确定操作类型时 至少两个麦克风接收到的声音信号的参数 010 , 确定单元 012 还用于如果所述第一麦克风接收到的第一声音信号的开始时刻早于所述第二麦克风接收到的第二声音信号的开始时刻,则确定所述操作类型为第一操作,并且所述第一麦克风的声音响度 声音信号大于第二声音信号的声音响度,或者如果第二麦克风接收到的第二声音信号的开始时刻早于第二麦克风接收到的第一声音信号的开始时刻,则确定操作类型为第二操作 第一麦克风,第二声音信号的声音响度大于第一声音信号的声音响度。 [0106] 可选的,确定单元 012 还用于根据获取的所述至少两个麦克风接收的声音信号的特征参数确定 010 , 操作类型对应的操作距离, 对应的, 生成单元 013 还用于根据操作类型和操作距离生成操作指令。 [0107] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 01 第二麦克风为设置在移动终端底部的麦克风 01 ,第一操作包括移动终端显示内容的移动 01 从上到下,第二操作包括移动终端显示内容的移动 01 从下到上,或者如果第一麦克风是设置在移动终端左侧的麦克风 01 第二麦克风为设置在移动终端右侧的麦克风 01 ,第一操作包括移动终端显示内容的移动 01 从左到右,第二操作包括移动终端显示内容的移动 01 从右到左。 [0108] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 01 第二麦克风为设置在移动终端底部的麦克风 01 ,第一操作对应的操作距离为移动终端显示内容的距离 01 从上到下移动,第二操作对应的操作距离为移动终端显示内容的距离 01 从下向上移动,或者如果第一麦克风是设置在移动终端左侧的麦克风 01 第二麦克风为设置在移动终端右侧的麦克风 01 ,第一操作对应的操作距离为移动终端显示内容的距离 01 从左向右移动,第二操作对应的操作距离为移动终端显示内容的距离 01 从右向左移动。 [0109] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 01 第二麦克风为设置在移动终端底部的麦克风 01 ,第一操作包括上翻页操作、从上往下滑动解锁或后退操作,第二操作包括下翻页操作、从下往上滑动解锁或前进 操作,或者如果第一麦克风是设置在移动终端左侧的麦克风 01 第二麦克风为设置在移动终端右侧的麦克风 01,第一操作包括向上翻页操作、从左向右滑动解除阻塞或返回操作,第二操作包括从右向左滑动解除阻塞、向下翻页操作或向前 手术。 [0110] 本实施例用于实现上述方法实施例。 本实施例中各单元的工作流程和工作原理参见上述方法实施例中的描述。 此处不再赘述。 [0111] 本发明实施例提供的移动终端 01 . 移动终端 01 配备至少两个麦克风 010 . 当用户向至少两个麦克风吹气时 010 , 至少两个麦克风接收到的声音信号的特征参数 010 分别获得。 特征参数包括声音信号的开始时刻、输入持续时间或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离) 010 . 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,移动端 01 可以使用至少两个麦克风进行操作 010 在移动端 01 ,从而简化现有的操作模式,提高人机交互效率。 [0112] 本发明实施例还提供了另一种移动终端 02 . 移动终端 02 包括至少两个麦克风 020 . 如图 10 所示,移动终端 02 还包括一个处理器 021 和一段记忆 022 . 处理器 021 , 至少两个麦克风 020 , 和内存 022 使用总线连接 023 . 记忆 022 被配置为存储计算机程序 0221 . 处理器 021 被配置为执行计算机程序 0221 . 处理器 021 执行计算机程序 0221 分别获取至少两个麦克风接收到的声音信号的特征参数 020 ,根据得到的至少两个麦克风接收到的声音信号的特征参数确定操作类型 020 ,根据操作类型生成操作指令,执行与操作指令对应的操作。 [0113] 可选地,所述声音信号的特征参数包括所述至少两个麦克风接收到的声音信号的开始时刻、输入时长或声音响度中的至少一种。 020 . [0114] 可选地,处理器 021 执行计算机程序 0221 根据至少两个麦克风接收到的声音信号的特征参数之间的相关性来确定 020 , 至少两个麦克风是否接收到声音信号 020 为吹出气流的声音信号,根据得到的至少两个麦克风接收到的声音信号的特征参数进行判断操作类型的操作 020 当至少两个麦克风接收到声音信号时 020 是吹出气流的声音信号。 [0115] 可选地,至少两个麦克风 020 包括第一麦克风和第二麦克风,如果声音信号的特征参数包括至少两个麦克风接收到的声音信号的开始时刻、输入时长和声音响度 020 , 处理器 021 执行计算机程序 0221如果第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻,则判断操作类型为第一操作,并且第一声音信号的声音响度为 大于第二声音信号的声音响度,或者如果第二麦克风接收到的第二声音信号的开始时刻早于第一麦克风接收到的第一声音信号的开始时刻,则确定操作类型为第二操作 ,且第二声音信号的声音响度大于第一声音信号的声音响度。 [0116] 可选地,处理器 021 执行计算机程序 0221 根据得到的至少两个麦克风接收到的声音信号的特征参数来确定 020 ,对应于操作类型的操作距离,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0117] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 02 第二麦克风为设置在移动终端底部的麦克风 02 ,第一操作包括移动终端显示内容的移动 02 从上到下,第二操作包括移动终端显示内容的移动 02 从下到上,或者如果第一麦克风是设置在移动终端左侧的麦克风 02 第二麦克风为设置在移动终端右侧的麦克风 02 ,第一操作包括移动终端显示内容的移动 02 从左到右,第二操作包括移动终端显示内容的移动 02 从右到左。 [0118] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 02 第二麦克风为设置在移动终端底部的麦克风 02 ,第一操作对应的操作距离为移动终端显示内容的距离 02 从上到下移动,第二操作对应的操作距离为移动终端显示内容的距离 02 从下向上移动,或者如果第一麦克风是设置在移动终端左侧的麦克风 02 第二麦克风为设置在移动终端右侧的麦克风 02 ,第一操作对应的操作距离为移动终端显示内容的距离 02 从左向右移动,第二操作对应的操作距离为移动终端显示内容的距离 02 从右向左移动。 [0119] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 02 第二麦克风为设置在移动终端底部的麦克风 02 ,第一操作包括上翻页操作,或从上到下滑动解除阻塞的操作,或返回操作,第二操作包括向下翻页操作,或从下到上滑动解除阻塞的操作,或 向前操作,或者如果第一麦克风是设置在移动终端左侧的麦克风 02 第二麦克风为设置在移动终端右侧的麦克风 02 ,第一操作包括向上翻页操作,或从左向右滑动解锁操作,或返回操作,第二操作包括从右向左滑动解锁操作,或向下翻页操作,或 前向操作。 [0120] 本实施例用于实现上述方法实施例。 本实施例中各单元的工作流程和工作原理参见上述方法实施例中的描述。 此处不再赘述。 [0121]本发明实施例提供的移动终端 02 . 移动终端 02 配备至少两个麦克风 020 . 当用户向至少两个麦克风吹气时 020 , 至少两个麦克风接收到的声音信号的特征参数 020 分别获得。 特征参数包括声音信号的开始时刻、输入持续时间或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离) 020 . 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,移动端 02 可以在移动终端上使用麦克风进行操作,简化了现有的操作方式,提高了人机交互效率。 [0122] 在本发明提供的几个实施例中,应当理解,所公开的装置和方法可以通过其他方式实现。 例如,所描述的设备实施例仅仅是示例。 例如,单元划分仅仅是逻辑上的功能划分,实际实现中还可以是其他的划分。 例如,可以将多个单元或组件组合或集成到另一个系统中,或者可以忽略或不执行某些特征。 此外,显示或讨论的相互耦合或直接耦合或通信连接可以使用一些接口来实现。 装置或单元之间的间接耦合或通信连接可以以电子、机械或其他形式实现。 [0123] 被描述为独立部分的单元可以是物理上独立的,也可以不是物理上的,作为单元显示的部分可以是物理单元,也可以不是物理单元,可以位于一个位置,或者可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部单元来实现本实施例方案的目的。 [0124] 另外,本发明实施例中的功能单元可以集成在一个处理单元中,也可以是各个单元在物理上单独存在,或者两个或多个单元集成在一个单元中。 集成单元可以以硬件的形式实现,也可以在软件功能单元的基础上以硬件的形式实现。 [0125] 当上述集成单元以软件功能单元的形式实现时,该集成单元可以存储在计算机可读存储介质中。 软件功能单元存储在存储介质中,包括若干指令,用于指示计算机设备(可以是个人计算机、服务器或网络设备)或处理器执行上述方法的部分步骤。 本发明的实施例。 上述存储介质包括任何可以存储程序代码的介质,如通用串行总线(USB)闪存盘、移动硬盘、只读存储器(ROM)、随机存取存储器(RAM)、磁盘等。 ,或光盘。 [0126] 本领域技术人员可以清楚地理解,为了描述的方便和简洁,以上述功能模块的划分为例进行说明。 在实际应用中,上述功能可以根据需要分配到不同的功能模块中实现,即将装置的内部结构划分为不同的功能模块来实现上述全部或部分功能。 上述装置的详细工作过程可以参见上述方法实施例中的对应过程,在此不再赘述。 [0127]最后需要说明的是,上述实施例仅用于说明本发明的技术方案,并不用于限制本发明。 尽管结合前述实施例对本发明进行了详细描述,但本领域普通技术人员应当理解,对于前述实施例中描述的技术方案,仍然可以进行修改或者对其部分或全部技术特征进行等同替换。 ,而不脱离本发明实施例技术方案的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN107005609A(String), CN107005609B(String), EP3282680A1(String), EP3282680A4(String), EP3282680B1(String), US20180139553A1(String), WO2016172846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN107005609A(String), CN107005609B(String), EP3282680A1(String), EP3282680A4(String), EP3282680B1(String), US20180139553A1(String), WO2016172846A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20180139553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN107005609A(String), CN107005609B(String), EP3282680A1(String), EP3282680A4(String), EP3282680B1(String), US20180139553A1(String), WO2016172846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.838 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), CN107005609A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.845 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.846 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.846 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), CN107005609B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), EP3282680A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), EP3282680A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), EP3282680B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), US20180139553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270688(Integer), WO2016172846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20180139553A1(String), US20180139553A1(String), 1526486400(Integer), 270688(Integer), 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185010(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.933 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185010(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.941 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185010(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.946 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185010(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.974 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.974 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20210075461A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Signal processing method and circuit of mobile terminal and mobile terminal(String), 移动终端的信号处理方法及电路及移动终端(String), US20210075461A1(String), A signal processing method and circuit of a mobile terminal and a mobile terminal are provided, by sending a signal detected by operating an antenna body as a sensing pad of a sensor to a microprocessor, the microprocessor determines a usage state of the mobile terminal according to the signal, generates a control signal according to the usage state of the mobile terminal, and controls a tuning circuit to switch tuning paths through the control signal so as to perform a tuning process on a signal from a mobile terminal signal source or the antenna body.(String), 一种移动终端的信号处理方法和电路及移动终端,通过将作为传感器的感应垫的天线体操作检测到的信号发送给微处理器,微处理器根据以下情况判断移动终端的使用状态。 信号,根据移动终端的使用状态产生控制信号,通过控制信号控制调谐电路切换调谐路径,从而对来自移动终端信号源或天线本体的信号进行调谐处理 .(String), US16/644804(String), 1527091200(Integer), US20210075461A1(String), 1615392000(Integer), 美国(String), 2(Integer), CN(String), 3(Integer), 0(Integer), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:57.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185011(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\15fa3c85ce54445389d84ee0283ffea3.png(String), 185011(Integer), 15fa3c85ce54445389d84ee0283ffea3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.017 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Signal processing method and circuit of mobile terminal and mobile terminal(String), 移动终端的信号处理方法及电路及移动终端(String), US20210075461A1(String), A signal processing method and circuit of a mobile terminal and a mobile terminal are provided, by sending a signal detected by operating an antenna body as a sensing pad of a sensor to a microprocessor, the microprocessor determines a usage state of the mobile terminal according to the signal, generates a control signal according to the usage state of the mobile terminal, and controls a tuning circuit to switch tuning paths through the control signal so as to perform a tuning process on a signal from a mobile terminal signal source or the antenna body.(String), 一种移动终端的信号处理方法和电路及移动终端,通过将作为传感器的感应垫的天线体操作检测到的信号发送给微处理器,微处理器根据以下情况判断移动终端的使用状态。 信号,根据移动终端的使用状态产生控制信号,通过控制信号控制调谐电路切换调谐路径,从而对来自移动终端信号源或天线本体的信号进行调谐处理 .(String), US16/644804(String), 1527091200(Integer), US20210075461A1(String), 1615392000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 3(Integer), 0(Integer), \20230420\15fa3c85ce54445389d84ee0283ffea3.png(String), 12(Integer), 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 1. A signal processing circuit of a mobile terminal, comprising: an antenna body, a sensor connected with the antenna body, a microprocessor and a tuning circuit having a plurality of tuning paths,wherein the tuning circuit is connected between a mobile terminal signal source and the antenna body, and the microprocessor is connected with the sensor and the tuning circuit, respectively,the sensor is configured to send a signal detected by operating the antenna body as a sensing pad of the sensor to the microprocessor,the microprocessor is configured to receive the signal, determine a usage state of the mobile terminal according to the signal, generate a control signal according to the usage state of the mobile terminal, and control the tuning circuit to switch the tuning paths through the control signal to perform a tuning process on a signal from the mobile terminal signal source or the antenna body.(String), 1.存储介质,其中所述存储介质包括存储的程序,所述程序在被处理器执行时使处理器执行根据权利要求8所述的信号处理方法。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 2. The signal processing circuit of claim 1, wherein the signal processing circuit further comprises an isolation device which is a lumped inductive element, the sensor is connected with the antenna body through the isolation device, andwherein the isolation device is configured to isolate interference of a communication signal on the signal detected by the sensor.(String), 12.处理器,其中所述处理器,用于运行程序,所述处理器执行所述程序时,执行如权利要求8所述的信号处理方法。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 3. The signal processing circuit of claim 1, wherein the sensor is a capacitive proximity sensor.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.033 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 4. The signal processing circuit of claim 1, wherein,the tuning circuit comprises a tuning path T1 and a tuning path T2, the tuning path T1 comprises inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected with one stationary contact of a first switch element, and one end of the capacitor C3 is connected with a signal feed point of the antenna body,the tuning path T2 comprises inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to the other one stationary contact of the first switch element, and one end of the capacitor C5 is connected with the signal feed point of the antenna body.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 5. The signal processing circuit of claim 4, wherein the signal processing circuit comprises a second switch element, the mobile terminal signal source comprises a radio frequency circuit and a baseband processing circuit, andwherein a grounding point GND1 and a grounding point GND2 of the antenna body are respectively connected with two stationary contacts of the second switch element;control ends of the first switch element and the second switch element are both connected with one end of the microprocessor, and the other end of the microprocessor is connected with the sensor;a moving contact of the first switch element is connected with one end of the radio frequency circuit, the other end of the radio frequency circuit is connected with the baseband processing circuit, and a moving contact of the second switch element is grounded.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 6. The signal processing circuit of claim 4 or 5, wherein the tuning paths have a well-type circuit structure, a T-type circuit structure, or a it-type circuit structure.(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 7. A mobile terminal comprising the signal processing circuit of claim 1.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 8. A signal processing method of a mobile terminal, comprising:detecting a signal by operating an antenna body of the mobile terminal as a sensing pad of a sensor;determining a usage state of the mobile terminal according to the signal; andperforming a tuning process on a signal from a mobile terminal signal source or the antenna body according to the usage state of the mobile terminal.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 9. The signal processing method of claim 8, wherein determining the usage state of the mobile terminal according to the signal comprises:detecting a change condition of a capacitance as a human body approaches through the sensor and the antenna body of the mobile terminal; anddetermining the usage state of the mobile terminal according to the change condition.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 10. The signal processing method according to claim 8, wherein performing the tuning process on the signal from the mobile terminal signal source or the antenna body according to the usage state of the mobile terminal comprises:performing the tuning process on the signal from the mobile terminal signal source or the antenna body by switching a tuning circuit of the mobile terminal to a corresponding tuning path,wherein the mobile terminal is provided with the tuning circuit having a plurality of tuning paths, and each tuning path corresponds to one usage state of the mobile terminal.(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 11. A storage medium, wherein the storage medium comprises a stored program which cause, when executed by a processor, the processor to perform the signal processing method according to claim 8.(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185011(Integer), 12. A processor, wherein the processor is configured to run a program, the signal processing method according to claim 8 is performed when the program is executed by the processor.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185011(Integer), TECHNICAL FIELD [0001]The present disclosure relates to the field of communication, and in particular, to a signal processing method and circuit of a mobile terminal, and a mobile terminal. BACKGROUND [0002]With continuous development of communication technology, portable mobile terminals such as mobile phones and notebooks have become essential personal belongings for almost everyone. In a process of designing a mobile terminal, various parameters required for design are obtained usually based on performance designed in a free space mode (that is, the mobile terminal is placed in the free space), and antenna performance of the mobile terminal is designed based on the parameters. Thus, after the design of the mobile terminal is completed, the antenna performance of the mobile terminal is determined. However, in a process of using the mobile terminal, a using environment of the mobile terminal is significantly different from a free space environment, for example, when the mobile terminal is used, external factors such as holding the mobile terminal by a hand of a user and approaching the mobile terminal to a head of the user may cause deterioration of the antenna performance, and finally, user experience is affected. SUMMARY [0003]The following is a summary of a subject matter described in detail herein. This summary is not intended to limit the scope of the claims. [0004]Embodiments of the present disclosure provide a signal processing method and circuit of a mobile terminal and a mobile terminal. [0005]According to an embodiment of the present disclosure, there is provided a signal processing circuit of a mobile terminal including an antenna body, a sensor connected with the antenna body, a microprocessor and a tuning circuit having a plurality of tuning paths. The tuning circuit is connected between a mobile terminal signal source and the antenna body, and the microprocessor is connected with the sensor and the tuning circuit, respectively. The sensor is configured to send a signal detected by operating the antenna body as a sensing pad of the sensor to the microprocessor. The microprocessor is configured to receive the signal, determine a usage state of the mobile terminal according to the signal, generate a control signal according to the usage state of the mobile terminal, and control the tuning circuit to switch the tuning paths through the control signal to perform a tuning process on a signal from the mobile terminal signal source or the antenna body. [0006]In an exemplary embodiment, the signal processing circuit further includes an isolation device which is a lumped inductive element, and the sensor is connected with the antenna body through the isolation device. The isolation device is configured to isolate interference of a communication signal on the signal detected by the sensor. [0007]In an exemplary embodiment, the sensor is a capacitive proximity sensor. [0008]In an exemplary embodiment, the tuning circuit includes a tuning path T1 and a tuning path T2, the tuning path T1 includes inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected with one stationary contact of a first switch element, and one end of the capacitor C3 is connected with a signal feed point of the antenna body. The tuning path T2 includes inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to one stationary contact of the first switch element, and one end of the capacitor C5 is connected with the signal feed point of the antenna body. [0009]In an exemplary embodiment, the signal processing circuit includes a second switch element, the mobile terminal signal source includes a radio frequency circuit and a baseband processing circuit. A grounding point GND1 and a grounding point GND2 of the antenna body are respectively connected with two stationary contacts of the second switch element. Control ends of the first switch element and the second switch element are both connected with one end of the microprocessor, and the other end of the microprocessor is connected with the sensor. A moving contact of the first switch element is connected with one end of the radio frequency circuit, the other end of the radio frequency circuit is connected with the baseband processing circuit, and a moving contact of the second switch element is grounded. [0010]In an exemplary embodiment, the tuning paths have a well-type circuit structure, a T-type circuit structure, or a n-type circuit structure. [0011]According to another embodiment of the present disclosure, a mobile terminal including any of above signal processing circuits is provided. [0012]According to another embodiment of the present disclosure, a signal processing method of a mobile terminal is provided. [0013]The signal processing method includes: detecting a signal by operating an antenna body of the mobile terminal as a sensing pad of a sensor; determining a usage state of the mobile terminal according to the signal; and performing a tuning process on a signal from a mobile terminal signal source or the antenna body according to the usage state of the mobile terminal. [0014]In an exemplary embodiment, determining the usage state of the mobile terminal according to the signal includes: detecting a change condition of a capacitance as a human body approaches through the sensor and the antenna body of the mobile terminal; and determining the usage state of the mobile terminal according to the change condition. [0015]In an exemplary embodiment, performing the tuning process on the signal from the mobile terminal signal source or the antenna body according to the usage state of the mobile terminal includes: performing the tuning process on the signal from the mobile terminal signal source or the antenna body by switching a tuning circuit of the mobile terminal to a corresponding tuning path, in which the mobile terminal is provided with the tuning circuit having a plurality of tuning paths, and each tuning path corresponds to one usage state of the mobile terminal. [0016]According to another embodiment of the present disclosure, a storage medium is further provided, the storage medium includes a stored program, any of above signal processing methods is performed when the program is executed. [0017]According to another embodiment of the present disclosure, a processor is further provided, the processor is configured to run a program, any of above signal processing methods is performed when the program is executed. [0018]According to the present disclosure, by sending the signal detected by operating the antenna body as a sensing pad of the sensor to the microprocessor, the microprocessor determines the usage state of the mobile terminal according to the signal, generates the control signal according to the usage state of the mobile terminal, and controls the tuning circuit to switch tuning paths according to the control signal to perform the tuning process on the signal from the mobile terminal signal source or the antenna body. A problem is solved that a current antenna signal processing circuit occupies more space due to a fact that a sensing pad connected with the sensor needs to be independently arranged in order to ensure that an antenna system is automatically switched to an optimal state to improve quality of antenna signals, an occupied internal space of the mobile terminal is reduced, interference to a communication antenna is avoided and user experience is improved. [0019]Other aspects will be apparent after reading and understanding the accompanying drawings and the detailed description. BRIEF DESCRIPTION OF THE DRAWINGS [0020]FIG. 1 is a block diagram of a hardware structure of a mobile terminal performing a signal processing method according to an embodiment of the present disclosure; [0021]FIG. 2 is a structural block diagram of a signal processing circuit according to an embodiment of the present disclosure; [0022]FIG. 3 is a structural block diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure; [0023]FIG. 4 is a schematic diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure; [0024]FIG. 5 is a flowchart of a signal processing method of a mobile terminal according to an embodiment of the present disclosure; [0025]FIG. 6 is a flowchart of a signal processing method according to an embodiment of the present disclosure; and [0026]FIG. 7 is a structural block diagram of a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0027]At present, a smart watch and an antenna signal processing circuit thereof are disclosed, the antenna signal processing circuit includes a sensor module, a microprocessor, an antenna body and an antenna tuning circuit having a plurality of tuning paths, in which a wearing state of the smart watch is determined by using a proximity sensing signal detected by the sensor module, and then the antenna tuning circuit is switched to a tuning path corresponding to the wearing state, so that an antenna system is suitable for the current wearing state, the antenna system is guaranteed to be automatically switched to an optimal state, and quality of antenna signals is improved. The sensor module is one or more of a distance sensor, a temperature sensor and an acceleration sensor, and requires additional supporting elements and supporting circuits. [0028]There is no solution provided for a problem that the antenna signal processing circuit occupies more space due to a fact that a sensing pad connected with the sensor needs to be independently arranged in order to ensure that the antenna system is automatically switched to an optimal state to improve the quality of the antenna signals. [0029]The present disclosure will be described in detail below with reference to accompanying drawings in conjunction with embodiments. [0030]The terms “first,”“second,” and the like in the description and claims of the present disclosure and in the foregoing accompanying drawings are used to distinguish between similar elements and not necessarily for describing a particular sequence or chronological order. Example 1 [0031]A method embodiment provided in example 1 of the present disclosure may be performed in a mobile terminal, a computer terminal or a similar computing device. Taking the mobile terminal as an example, FIG. 1 is a block diagram of a hardware structure of a mobile terminal performing a signal processing method according to an embodiment of the present disclosure. As shown in FIG. 1, a mobile terminal 10 may include one or two processors 102 (only one processor 102 is shown in FIG. 1) which may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, a memory 104 for storing data, and a transmission device 106 for performing communication functions. It will be understood by those skilled in the art that the structure shown in FIG. 1 is only an illustration and is not intended to limit the structure of the mobile terminal. For example, the mobile terminal 10 may include more or fewer components than those shown in FIG. 1, or have a configuration different from that shown in FIG. 1. [0032]The memory 104 may be used to store software programs and modules of an application, such as program instructions/modules corresponding to a signal processing method according to an embodiment of the present disclosure, and the processor 102 executes various functional applications and data processes by running the software programs and the modules stored in the memory 104, so as to implement the method described above. The memory 104 may include a high speed random memory, and may also include a non-volatile memory, such as one or two magnetic memory devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory located remotely from the processor 102 which may be connected to the mobile terminal 10 via a network. Examples of the network include, but are not limited to, an internet, an intranet, a local area network, a mobile communication network, and a combination thereof. [0033]The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal 10. In one example, the transmission device 106 includes a network interface controller (NIC) which can be connected to other network apparatuses through a base station so as to communicate with the internet. In one example, the transmission device 106 may be a radio frequency (RF) module which is used to communicate with the internet in a wireless manner. [0034]According to an embodiment of the present disclosure, there is provided a signal processing circuit of a mobile terminal which is applied to the mobile terminal described above. FIG. 2 is a structural block diagram of a signal processing circuit according to an embodiment of the present disclosure. As shown in FIG. 2, the signal processing circuit includes an antenna body 201, a sensor 203 connected with the antenna body 201, a microprocessor 205, a tuning circuit 204 having a plurality of tuning paths. [0035]The tuning circuit 204 is connected between a mobile terminal signal source 206 and the antenna body 201, and the microprocessor 205 is connected with the sensor 203 and the tuning circuit 204, respectively. [0036]The sensor 203 is configured to send a signal detected by operating the antenna body 201 as a sensing pad of the sensor 203 to the microprocessor 205. [0037]The microprocessor 205 is configured to receive the signal, determine a usage state of the mobile terminal according to the signal, generate a control signal according to the usage state of the mobile terminal, and control the tuning circuit 204 to switch the tuning paths through the control signal to perform a tuning process on a signal from the mobile terminal signal source 206 or the antenna body 201. [0038]FIG. 3 is a structural block diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure. As shown in FIG. 3, the circuit further includes an isolation device 202 which is a lumped inductive element. The sensor 203 is connected to the antenna body 201 through the isolation device 202, and the isolation device 202 is configured to isolate interference of a communication signal to the signal detected by the sensor 203. [0039]In an exemplary embodiment, the sensor 203 may be a capacitive proximity sensor. [0040]FIG. 4 is a schematic diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure. As shown in FIG. 4, the tuning circuit 204 includes a tuning path T1 and a tuning path T2, the tuning path T1 includes inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected to one stationary contact of a first switch element 208, and one end of the capacitor C3 is connected to a signal feed point of the antenna body 201. [0041]The tuning path T2 includes inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to the other one stationary contact of the first switch element 208, and one end of the capacitor C5 is connected to the signal feed point of the antenna body 201. [0042]In an exemplary embodiment, the circuit may include a second switch element, the mobile terminal signal source 206 includes a radio frequency circuit 209 and a baseband processing circuit 210. [0043]A grounding point GND1 and a grounding point GND2 of the antenna body 201 are respectively connected with two stationary contacts of the second switch element. [0044]Control ends of the first switch element 208 and the second switch element are both connected with one end of the microprocessor 205, and the other end of the microprocessor 205 is connected with the sensor 203. [0045]A moving contact of the first switch element 208 is connected with one end of the radio frequency circuit 209, the other end of the radio frequency circuit 209 is connected with the baseband processing circuit 210, and a moving contact of the second switch element is grounded. [0046]In an exemplary embodiment, the tuning paths may have a well-type circuit structure, a T-type circuit structure, or a IL-type circuit structure. [0047]As shown in FIG. 4, the signal processing circuit includes the antenna body 201, the isolation device 202, the sensor 203, the tuning circuit 204 having a plurality of tuning paths, the microprocessor 205, and the mobile terminal signal source 206. The antenna body 201 is connected with the sensor 203 through the isolation device 202, the tuning circuit 204 is connected between the mobile terminal signal source 206 and the antenna body 201, and the microprocessor 205 is connected with the sensor 203 and the tuning circuit 204, respectively. The sensor 203 detects an approach signal of an external human body through the antenna body 201 and sends the detected signal to the microprocessor 205, the microprocessor 205 receives the signal and generates a control signal according to the signal, and controls the tuning circuit 204 to switch the tuning paths through the control signal to perform the tuning process on the signal from the mobile terminal signal source 206 or the antenna body 201. [0048]The sensor 203 adopts a capacitive proximity sensor 203, when a human body is close to/contacts the antenna body 201, since the human body is equivalent to a grounded capacity, a capacity may be formed between the antenna body 201 and the ground, and induced capacitance usually has several pF to tens pF. A circuit of the sensor 203 outputs a pulse signal to charge and discharge the capacity formed between the antenna body 201 and the ground, and whether or not the human body approaches or touches the antenna body 201 is detected based on a change in the capacitance. [0049]The isolation device 202 adopts a lumped inductive element with an inductance value greater than 100 nH. By isolation of the lumped inductance element, the interference of the communication signal to the detected signal of the sensor 203 is isolated. [0050]In the embodiment, one tuning path of the tuning circuit 204 corresponds to one usage state of the mobile terminal. In an implement, possible usage states of the mobile terminal should be determined firstly (which may be determined statistically through experiments), and then matching impedances of the tuning paths of the tuning circuit 204 are determined, so that one tuning path of the tuning circuit 204 corresponds to one usage state of the mobile terminal. [0051]In the embodiment, by arranging the sensor 203, the usage state of the mobile terminal is determined by using the signal detected by the antenna body 201, and then the tuning circuit 204 is switched to a corresponding tuning path, so that a system of the mobile terminal is suitable for the current usage state. In the embodiment, the antenna body 201 is connected with the sensor 203 through the isolation device 202 to detect the change in the capacitance between the antenna body 201 and the ground caused when human body is close to/contacts the antenna body 201, thereby avoiding independently arranging a sensing pad to be connected with the sensor 203, thus, a space occupied by arranging the sensing pad is reduced. Meanwhile, interference of the sensing pad to communication is avoided and communication quality is improved. As shown in FIG. 4, the signal processing circuit includes the antenna body 201, the isolation device 202, the sensor 203, the tuning circuit 204 having a plurality of tuning paths, the microprocessor 205, the radio frequency circuit 209, the baseband processing circuit 210, and the first switch element 208. The first switch element 208 includes the control end, the moving contact, and the stationary contacts. [0052]Based on the above assumption of the embodiment, accordingly, the tuning circuit 204 includes two tuning paths, i.e., the tuning path T1 and the tuning path T2. Exemplarily, as shown in FIG. 4, the tuning path T1 includes inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected to one of the stationary contacts of the first switch element 208, and one end of the capacitor C3 is connected to the signal feed point of the antenna body 201; the tuning path T2 includes inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to the other one of the stationary contacts of the first switch element 208, and one end of the capacitor C5 is connected to the signal feed point of the antenna body 201. [0053]FIG. 4 only exemplarily illustrates the tuning paths with a well-type circuit structure, the circuit structure of the tuning paths is not limited in the embodiment, and the tuning paths may be designed to have a T-type circuit structure, a n-type circuit structure, or the like. The embodiment further includes a second switch element (not shown in FIG. 4) which also includes the control end, the moving contact and the stationary contacts. Correspondingly, the antenna body 201 includes one signal feed point and two grounding points which are the grounding point GND1 and the grounding point GND2, respectively. [0054]In the embodiment, one end of the tuning path T1 and one end of the tuning path T2 are connected to the signal feed point of the antenna body 201, respectively, the other end of the tuning path T1 and the other end of the tuning path T2 are connected to the two stationary contacts of the first switch element 208, respectively, and the grounding point GND1 and the grounding point GND2 of the antenna body 201 are connected to the two stationary contacts of the second switch element, respectively; the control ends of the first switch element 208 and the second switch element are both connected with one end of the microprocessor 205, and the other end of the microprocessor 205 is connected with the sensor 203; the moving contact of the first switch element 208 is connected to one end of the radio frequency circuit 209, the other end of the radio frequency circuit 209 is connected to the baseband processing circuit 210, and the moving contact of the second switch element is grounded. [0055]The microprocessor 205 of the embodiment adjusts system performance of the mobile terminal based on the control signal as follows: the sensor 203 sends a detected change signal of a system capacitance to the microprocessor 205, and the microprocessor 205 determines the current usage state of the mobile terminal according to the signal and generates a corresponding control signal according to the current usage state of the mobile terminal. [0056]As previously assumed, the usage state in the embodiment includes a state of using, a state of free space, a state of holding by a hand of a user, and a state of approaching by the head of a user, so that the microprocessor 205 can generate a high level or a low level to control the switching of the first switch element 208 and the switching of the second switch element by using the high level or the low level. In this case, the first switch element 208 and the second switch element may be single-pole double-throw switches controlled by high and low levels inputted through the control end. [0057]Exemplarily, it is assumed that the microprocessor 205 determines that the mobile terminal is currently in the state of holding by a hand of a user, accordingly, the microprocessor 205 generates the high level to control the control ends of the first switch element 208 and the second switch element, to control the moving contact of the first switch element 208 to contact with the stationary contact connecting with the tuning path T2, and to control the moving contact of the second switch element to contact with the stationary contact connecting with the grounding point GND1, so that to perform the tuning process on the signal from the antenna body 201 or a transmission signal from the baseband processing circuit 210 by using a matching impedance of the tuning path T1 and to adjust and improve radiation performance of the antenna body 201 in the state of holding by a hand of a user by using the grounding point GND2. Example 2 [0058]In an embodiment of the present disclosure, a signal processing method of a mobile terminal is provided. FIG. 5 is a flowchart of a signal processing method of a mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 5, the flowchart includes the following steps S502 to S506. [0059]In step S502, a signal is detected by operating the antenna body 201 of the mobile terminal as a sensing pad of the sensor 203. [0060]In step S504, a usage state of the mobile terminal is determined according to the signal. [0061]In step S506, a tuning process is performed on a signal from the mobile terminal signal source 206 or the antenna body 201 according to the usage state of the mobile terminal. [0062]Through the above steps, the antenna body 201 of the mobile terminal is operated as the sensing pad of the sensor 203 to detect a signal, and the usage state of the mobile terminal is determined according to the signal, and the tuning process is performed on the signal from the mobile terminal signal source 206 or the antenna body 201 according to the usage state of the mobile terminal, so that the problem is solved that a current antenna signal processing circuit occupies more space due to a fact that a sensing pad connected with the sensor 203 needs to be independently arranged in order to ensure that an antenna system is automatically switched to an optimal state to improve quality of antenna signals, an occupied internal space of the mobile terminal is reduced, interference to a communication antenna is avoided and user experience is improved. [0063]In an exemplary embodiment, determining the usage state of the mobile terminal according to the signal may include: a change condition of a capacitance as a human body approaches is detected through the sensor 203 and the antenna body 201 of the mobile terminal, and the usage state of the mobile terminal is determined according to the change condition. [0064]In an exemplary embodiment, performing the tuning process on the signal from the mobile terminal signal source 206 or the antenna body 201 according to the usage state of the mobile terminal may include: the tuning process is performed on the signal from the mobile terminal signal source 206 or the antenna body 201 by switching the tuning circuit 204 of the mobile terminal to a corresponding tuning path, the mobile terminal is provided with the tuning circuit 204 having a plurality of tuning paths, and each tuning path corresponds to one usage state of the mobile terminal. The mobile terminal is internally provided with the antenna body 201, the sensor 203 connected with the antenna body 201, the microprocessor 205 and the tuning circuit 204 having a plurality of tuning paths, and the method includes the following steps: the sensor 203 detects a signal by operating the antenna body 201 as the sensing pad and determines the usage state of the mobile terminal according to the signal; arranging the tuning circuit 204 having a plurality of tuning paths such that one tuning path corresponds to one usage state of the mobile terminal; and switching the tuning circuit 204 to a corresponding tuning path according to the usage state of the mobile terminal, and performing the tuning process on the signal from the mobile terminal signal source or the antenna body. In the method, since a communication antenna on a module is reused as the sensing pad of the sensor 203, so that the problem of more occupied space caused by independently arranging the sensing pad connected with the sensor 203 is avoided, and interference of the sensing pad on communication is also avoided. [0065]FIG. 6 is a flowchart of a signal processing method according to an embodiment of the present disclosure. As shown in FIG. 6, the method including steps S602 to S606. [0066]In step S602, the tuning circuit 204 having a plurality of tuning paths is arranged to enable one tuning path to correspond to one usage state of the mobile terminal. [0067]In step S604, a change of a capacitance as a human body approaches is detected by using the sensor 203 and the antenna body 201, and the usage state of the mobile terminal is determined according to the change. [0068]In step S606, the microprocessor 205 switches the tuning circuit 204 and the grounding point of the antenna to a corresponding path according to the usage state of the mobile terminal, and performs a tuning processing on a signal from the mobile terminal signal source 206 or the antenna body 201. [0069]In the embodiment, the change of the capacitance as a human body approaches is detected by using the sensor 203 and the antenna body 201, the usage state of the mobile terminal is determined according to the change, and then the tuning circuit 204 is switched to the tuning path corresponding to the usage state, so that the system of the mobile terminal is suitable for the current usage state, the system of the mobile terminal can be automatically switched to an optimal state, quality of signals is ensured, and user experience is improved. [0070]In order to further improve performance of the mobile terminal in different usage states, the method in FIG. 6 further includes: arranging one signal feed point and a plurality of grounding points for the antenna body 201, and when or after performing the tuning process on the signal from the mobile terminal signal source or the antenna body 201, the method further includes: the grounding points of the antenna body 201 are switched to adjust performance of the antenna body 201. [0071]In one implementation of the embodiment, the grounding points of the antenna body may be switched by arranging a switch element for the antenna body, the switch element includes a control end, a moving contact and a plurality of stationary contacts, the moving contact is grounded, one stationary contact is connected with one grounding point, each stationary contact corresponds to one usage state of the mobile terminal, and the moving contact of the switch element is switched by controlling the control end. Example 3 [0072]According to another embodiment of the present disclosure, there is also provided a mobile terminal including the antenna body 201, the sensor 203 connecting with the antenna body 201, the microprocessor 205, and the tuning circuit 204 having a plurality of tuning paths. The interference of the communication signal to the signal of the sensor 203 is isolated through the isolation device 202 between the antenna body 201 and the sensor 203. The microprocessor 205 detects the usage state of the mobile terminal and adjusts system parameters of the mobile terminal. [0073]FIG. 7 is a structural block diagram of a mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 7, the mobile terminal of the embodiment includes an antenna signal processing circuit, an internal structure of the antenna signal processing circuit is as shown in FIG. 3, the antenna body 201 in the antenna signal processing circuit is connected to the sensor 203 through the isolation device 202, and when a human body approaches the antenna body 201, a change of a capacitance between the antenna body 201 and the ground may be detected, and the microprocessor 205 in the antenna signal processing circuit senses whether a human body approaches, so as to adjust the system parameters of the mobile terminal. [0074]In a design process of the embodiment, in order to save space of the mobile terminal and save components, the microprocessor 205 in the embodiment is a central controller CPU of the mobile terminal, that is, the actions such as determining, calculating, controlling or the like performed by the microprocessor 205 in the antenna signal processing circuit are performed by the central controller CPU of the mobile terminal. [0075]Since the baseband processing circuit in the antenna signal processing circuit is also substantially one microcontroller, the baseband processing circuit in the antenna signal processing circuit may be a central processing unit CPU of the mobile terminal either. Example 4 [0076]Embodiments of the present disclosure also provide a storage medium including stored programs, any one of the methods describe(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的信号处理方法、电路及移动终端。 背景 [0002] 随着通信技术的不断发展,手机、笔记本等便携式移动终端已经成为几乎每个人必不可少的个人随身物品。 在移动终端的设计过程中,通常根据自由空间模式(即移动终端放置在自由空间中)设计的性能,获取设计所需的各种参数,设计移动终端的天线性能 基于参数。 这样,移动终端的设计完成后,移动终端的天线性能就确定了。 然而,在使用移动终端的过程中,移动终端的使用环境与自由空间环境有很大的不同,例如,在使用移动终端时,人的手拿着移动终端等外部因素。 用户将移动终端靠近用户头部可能会导致天线性能下降,最终影响用户体验。 概括 [0003] 以下是本文详细描述的主题的概要。 该概述不旨在限制权利要求的范围。 [0004] 本发明实施例提供一种移动终端的信号处理方法、电路及移动终端。 [0005] 根据本公开的实施例,提供了一种移动终端的信号处理电路,包括天线本体、与天线本体连接的传感器、微处理器和具有多个调谐路径的调谐电路。 调谐电路连接在移动终端信号源和天线本体之间,微处理器分别连接传感器和调谐电路。 传感器被配置为将通过将天线体作为传感器的感测垫操作而检测到的信号发送到微处理器。 微处理器用于接收信号,根据信号判断移动终端的使用状态,根据移动终端的使用状态产生控制信号,通过控制信号控制调谐电路切换调谐路径 对来自移动终端信号源或天线体的信号进行调谐处理。 [0006] 在一个示例性实施例中,信号处理电路还包括隔离装置,隔离装置为集总电感元件,传感器通过隔离装置与天线本体连接。 隔离装置用于隔离通信信号对传感器检测信号的干扰。 [0007] 在示例性实施例中,传感器是电容式接近传感器。 [0008] 在示例性实施例中,调谐电路包括调谐路径T 1 和调整路径 T 2 , 调整路径 T 1 包括电感器 L 1 和我 2 和电容器 C 3 和C 4 , 电感 L 的一端 2 与第一开关元件的一个固定触点连接,电容器C的一端 3 与天线本体的信号馈入点连接。 调整路径 T 2 包括电感器 L 3 和我 4 和电容器 C 5 和C 6 , 电感 L 的一端 4 连接到第一开关元件的一个固定触点,和电容器C的一端 5 与天线本体的信号馈入点相连。 [0009] 在一个示例性实施例中,信号处理电路包括第二开关元件,移动终端信号源包括射频电路和基带处理电路。 接地点GND 1 和接地点GND 2天线本体的两个固定触点分别与第二开关元件的两个固定触点连接。 第一开关元件和第二开关元件的控制端均连接微处理器的一端,微处理器的另一端连接传感器。 第一开关元件的动触点连接射频电路的一端,射频电路的另一端连接基带处理电路,第二开关元件的动触点接地。 [0010] 在示例性实施例中,调谐路径具有阱型电路结构、T型电路结构或n型电路结构。 [0011] 根据本公开的另一个实施例,提供了一种包括上述任一种信号处理电路的移动终端。 [0012] 根据本公开的另一个实施例,提供了一种移动终端的信号处理方法。 [0013] 该信号处理方法包括:通过将移动终端的天线体作为传感器的感应垫操作来检测信号; 根据信号判断移动终端的使用状态; 根据移动终端的使用状态,对来自移动终端信号源或天线本体的信号进行调谐处理。 [0014] 在一个示例性实施例中,根据所述信号确定移动终端的使用状态包括: 通过传感器和移动终端的天线体检测人体接近时电容的变化情况; 根据变化情况判断移动终端的使用状态。 [0015] 在一个优选实施例中,根据移动终端的使用状态对来自移动终端信号源或天线本体的信号进行调谐处理包括:对来自移动终端信号源或天线本体的信号进行调谐处理。 通过将移动终端的调谐电路切换到对应的调谐路径,移动终端设置有具有多条调谐路径的调谐电路,每条调谐路径对应移动终端的一种使用状态。 [0016] 根据本发明的另一个实施例,还提供了一种存储介质,该存储介质包括存储的程序,在执行该程序时执行上述任一种信号处理方法。 [0017] 根据本发明的另一个实施例,还提供了一种处理器,该处理器用于运行程序,在程序运行时执行上述任一种信号处理方法。 [0018] 本发明通过将天线体作为传感器的感应垫工作时检测到的信号发送给微处理器,微处理器根据该信号判断移动终端的使用状态,并根据使用情况产生控制信号。 移动终端的状态,根据控制信号控制调谐电路切换调谐路径,对来自移动终端信号源或天线本体的信号进行调谐处理。 解决了现有的天线信号处理电路由于需要单独设置与传感器连接的感应垫而占用较多空间的问题,以保证天线系统自动切换到最佳状态,提高信号质量。 天线信号,减少了移动终端内部空间的占用,避免了对通信天线的干扰,提高了用户体验。 [0019] 在阅读和理解附图和详细描述之后,其他方面将是显而易见的。 附图的简要说明 [0020] 图1是执行根据本发明实施例的信号处理方法的移动终端的硬件结构框图; [0021] 图2是根据本发明实施例的信号处理电路的结构框图; [0022]图3是根据本发明一个示例性实施例的信号处理电路的结构框图。 [0023] 图4是根据本公开示例性实施例的信号处理电路的示意图; [0024] 图5是本发明一个实施例的移动终端的信号处理方法的流程图。 [0025] 图6是根据本发明实施例的信号处理方法的流程图; 和 [0026] 图7是根据本发明实施例的移动终端的结构框图。 详细说明 [0027] 目前,公开了一种智能手表及其天线信号处理电路,该天线信号处理电路包括传感器模块、微处理器、天线本体和具有多个调谐路径的天线调谐电路,其中佩戴状态 智能手表利用传感器模块检测到的接近感应信号进行判断,然后将天线调谐电路切换到与佩戴状态对应的调谐路径,使天线系统适合当前佩戴状态,天线 保证系统自动切换到最佳状态,提高天线信号质量。 传感器模块为距离传感器、温度传感器和加速度传感器中的一种或多种,​​需要额外的支持元件和支持电路。 [0028] 为保证天线系统自动切换到最佳状态,需要单独设置与传感器连接的感应垫,导致天线信号处理电路占用较多空间,目前未提供解决方案。 提高天线信号的质量。 [0029] 下面结合附图并结合实施例对本发明进行详细说明。 [0030] 本公开的说明书和权利要求以及前述附图中的术语“第一”、“第二”等用于区分相似的元素,并不一定用于描述特定的顺序或时间顺序。 示例 1 [0031] 本发明实施例一提供的方法实施例可以在移动终端、计算机终端或类似的计算设备中执行。 以移动终端为例,图1是执行根据本发明实施例的信号处理方法的移动终端的硬件结构框图。 如图1所示,一个移动终端 10 可能包括一个或两个处理器 102 (只有一个处理器 102 如图1所示)可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等处理设备、存储器 104 用于存储数据,以及传输设备 106 用于执行通信功能。 本领域的技术人员可以理解,图1所示的结构只是一种示例,并不对移动终端的结构构成限制。 比如移动端 10 可以包括比图 1 中所示的组件更多或更少的组件,或者具有与图 1 中所示的不同的配置。 [0032] 记忆 104 可以用于存储应用程序的软件程序和模块,例如与根据本公开实施例的信号处理方法对应的程序指令/模块,以及处理器 102 通过运行存储在内存中的软件程序和模块来执行各种功能应用和数据处理 104 ,从而实现上述方法。 记忆 104 可以包括高速随机存储器,也可以包括非易失性存储器,例如一个或两个磁存储设备、闪存或其他非易失性固态存储器。 在某些情况下,内存 104 还可以包括远离处理器的存储器 102 可连接移动终端 10通过网络。 网络的示例包括但不限于因特网、内联网、局域网、移动通信网络及其组合。 [0033] 传动装置 106 用于通过网络接收或传输数据。 上述网络的具体示例可以包括移动终端的通信提供商提供的无线网络 10 . 在一个例子中,传输设备 106 包括网络接口控制器(NIC),其可以通过基站连接到其他网络设备以与互联网通信。 在一个例子中,传输设备 106 可以是用于以无线方式与因特网通信的射频(RF)模块。 [0034] 根据本发明实施例,提供了一种移动终端信号处理电路,应用于上述移动终端。 图2是根据本发明实施例的信号处理电路的结构框图。 如图2所示,信号处理电路包括天线本体 201 , 一个传感器 203 与天线体相连 201 , 一个微处理器 205 , 调谐电路 204 具有多个调谐路径。 [0035] 调谐电路 204 连接在移动终端信号源之间 206 和天线体 201 , 和微处理器 205 与传感器相连 203 和调谐电路 204 , 分别。 [0036] 传感器 203 被配置为发送通过操作天线体检测到的信号 201 作为传感器的感应垫 203 到微处理器 205 . [0037] 微处理器 205 用于接收信号,根据信号判断移动终端的使用状态,根据移动终端的使用状态产生控制信号,控制调谐电路 204 通过控制信号切换调谐路径,对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 . [0038] 图3是根据本公开示例性实施例的信号处理电路的结构框图。 如图3所示,该电路还包括隔离器件 202 这是一个集总电感元件。 传感器 203 连接到天线体 201 通过隔离装置 202 和隔离装置 202 被配置为隔离通信信号对传感器检测到的信号的干扰 203 . [0039] 在示例性实施例中,传感器 203 可能是电容式接近传感器。 [0040] 图4是根据本公开示例性实施例的信号处理电路的示意图。 如图4所示,调谐电路 204 包括调谐路径 T 1 和调整路径 T 2 , 调整路径 T 1 包括电感器 L 1 和我 2 和电容器 C 3 和C 4 , 电感 L 的一端 2 连接到第一开关元件的一个固定触点 208 ,电容C的一端 3 连接到天线本体的信号馈入点 201 . [0041] 调整路径 T 2 包括电感器 L 3 和我 4 和电容器 C 5 和C 6 , 电感 L 的一端 4 连接到第一开关元件的另一个固定触点 208 ,电容C的一端 5 连接到天线本体的信号馈入点 201 . [0042] 在一个示例性实施例中,该电路可以包括第二开关元件,移动终端信号源 206 包括射频电路 209 和基带处理电路 210 . [0043] 接地点GND 1 和接地点GND 2 天线本体 201分别与第二开关元件的两个固定触点相连。 [0044] 第一开关元件的控制端 208 第二开关元件均与微处理器的一端连接 205 ,微处理器的另一端 205 与传感器相连 203 . [0045] 第一开关元件的动触点 208 与射频电路的一端相连 209 ,射频电路的另一端 209 与基带处理电路相连 210 ,第二开关元件的动触点接地。 [0046] 在示例性实施例中,调谐路径可以具有阱型电路结构、T型电路结构或IL型电路结构。 [0047] 如图4所示,信号处理电路包括天线本体 201 , 隔离装置 202 , 传感器 203 , 调谐电路 204 具有多个调谐路径,微处理器 205 , 和移动端信号源 206 . 天线本体 201 与传感器相连 203 通过隔离装置 202 , 调谐电路 204 连接在移动终端信号源之间 206 和天线体 201 , 和微处理器 205 与传感器相连 203 和调谐电路 204 , 分别。 传感器 203 通过天线体检测外界人体接近信号 201 并将检测到的信号发送给微处理器 205 , 微处理器 205 接收信号并根据信号产生控制信号,控制调谐电路 204 通过控制信号切换调谐路径,对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 . [0048] 传感器 203 采用电容式接近传感器 203 ,当人体靠近/接触天线体时 201 ,由于人体相当于一个接地电容,天线本体之间可能形成电容 201 与地、感应电容一般有几pF到几十pF。 传感器电路 203 输出脉冲信号对天线体间形成的电容进行充放电 201 和地面,以及人体是否接近或接触天线体 201 基于电容的变化来检测。 [0049] 隔离装置 202 采用电感值大于100nH的集总电感元件。 通过集总电感元件的隔离,通信信号对传感器检测信号的干扰 203 是孤立的。 [0050] 在本实施例中,调谐电路的一个调谐路径 204 对应移动终端的一种使用状态。 在实现中,首先要确定移动终端可能的使用状态(可以通过实验统计确定),然后匹配调谐电路的调谐路径的阻抗。 204 被确定,使得调谐电路的一个调谐路径 204 对应移动终端的一种使用状态。 [0051] 在本实施例中,通过设置传感器 203 ,利用天线体检测到的信号判断移动终端的使用状态 201 ,然后是调谐电路 204 切换到相应的调谐路径,使得移动终端的系统适合当前的使用状态。 本实施例中,天线本体 201 与传感器相连 203 通过隔离装置 202 检测天线体之间的电容变化 201 以及人体靠近/接触天线体时产生的接地 201 ,从而避免单独设置感应垫与传感器连接 203,从而减少了设置感应垫所占用的空间。 同时,避免了感应垫对通信的干扰,提高了通信质量。 如图4所示,信号处理电路包括天线本体 201 , 隔离装置 202 , 传感器 203 , 调谐电路 204 具有多个调谐路径,微处理器 205 , 射频电路 209 ,基带处理电路 210 , 和第一个开关元件 208 . 第一个开关元件 208 包括控制端、动触点和静触点。 [0052] 基于本实施例的上述假设,相应地,调谐电路 204 包括两条调谐路径,即调谐路径 T 1 和调整路径 T 2 . 示例性地,如图4所示,调谐路径T 1 包括电感器 L 1 和我 2 和电容器 C 3 和C 4 , 电感 L 的一端 2 连接到第一开关元件的固定触点之一 208 ,电容C的一端 3 连接到天线本体的信号馈入点 201 ; 调整路径 T 2 包括电感器 L 3 和我 4 和电容器 C 5 和C 6 , 电感 L 的一端 4 连接到第一开关元件的另一个固定触点 208 ,电容C的一端 5 连接到天线本体的信号馈入点 201 . [0053] 图4只是示例性地示出了具有阱型电路结构的调谐路径,本实施例不对调谐路径的电路结构进行限定,调谐路径可以设计为T型电路结构、n型电路结构。 电路结构等。 该实施例还包括第二开关元件(图4中未示出),第二开关元件也包括控制端、动触点和静触点。 相应地,天线体 201 包括一个信号馈入点和两个接地点,接地点为GND 1 和接地点GND 2 , 分别。 [0054] 在本实施例中,调谐路径T的一端 1 和调谐路径 T 的一端 2 连接到天线本体的信号馈入点 201 , 分别为调谐路径 T 的另一端 1 和调谐路径T的另一端 2 连接到第一个开关元件的两个固定触点 208 ,分别与接地点GND 1 和接地点GND 2 天线本体 201 分别连接至第二开关元件的两个固定触点; 第一开关元件的控制端 208 第二开关元件均与微处理器的一端连接 205 ,微处理器的另一端 205 与传感器相连 203 ; 第一开关元件的动触点 208 连接到射频电路的一端 209 ,射频电路的另一端 209 接基带处理电路 210 ,第二开关元件的动触点接地。 [0055] 微处理器 205 本实施例基于控制信号调整移动终端的系统性能如下:传感器 203 向微处理器发送检测到的系统电容变化信号 205 , 和微处理器 205 根据该信号确定移动终端的当前使用状态,并根据移动终端的当前使用状态生成相应的控制信号。 [0056] 如前所述,本实施例中的使用状态包括使用状态、空闲空间状态、用户手持状态、用户头部接近状态,使得微处理器 205 可以产生高电平或低电平来控制第一开关元件的开关 208第二开关元件以高电平或低电平切换。 在这种情况下,第一个开关元件 208 第二开关元件可以为由控制端输入的高低电平控制的单刀双掷开关。 [0057] 示例性地,假设微处理器 205 确定移动终端当前处于用户手持状态,相应地,微处理器 205 产生高电平控制第一开关元件的控制端 208 以及第二开关元件,以控制第一开关元件的动触点 208 接触与调谐路径T连接的固定触点 2 ,并控制第二开关元件的动触点与接地点GND相连的静触点接触 1 , 从而对来自天线体的信号进行调谐处理 201 或来自基带处理电路的传输信号 210 通过使用调谐路径 T 的匹配阻抗 1 调整和改善天线体的辐射性能 201 使用接地点GND在用户手持状态下 2 . 示例 2 [0058] 在本发明实施例中,提供了一种移动终端的信号处理方法。 图5是根据本公开实施例的移动终端的信号处理方法的流程图。 如图5所示,该流程图包括以下步骤S 502 到小号 506 . [0059] 在步骤S 502 ,通过操作天线体来检测信号 201 移动终端作为传感器的感应板 203 . [0060] 在步骤S 504 ,根据该信号确定移动终端的使用状态。 [0061] 在步骤S 506 , 对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 根据移动终端的使用状态。 [0062] 通过以上步骤,天线体 201 移动终端的作为传感器的感应垫操作 203 检测信号,根据信号判断移动终端的使用状态,并对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 根据移动终端的使用状态,解决了现有的天线信号处理电路由于与传感器连接的感应垫占用较多空间的问题 203 需要独立设置,以保证天线系统自动切换到最佳状态,提高天线信号质量,减少移动终端内部占用空间,避免对通信天线的干扰,提高用户体验 . [0063] 在一个示例性实施例中,根据所述信号确定移动终端的使用状态可以包括:通过传感器检测电容随着人体接近的变化情况。 203 和天线体 201 移动终端的使用状态,根据变化情况确定移动终端的使用状态。 [0064] 在一个示例性实施例中,对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 根据移动终端的使用状态可以包括:对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 通过切换调谐电路 204 移动终端到相应的调谐路径,移动终端设置有调谐电路 204 具有多个调谐路径,每个调谐路径对应移动终端的一种使用状态。 移动终端内置有天线体 201 , 传感器 203 与天线体相连 201 , 微处理器 205 和调谐电路 204具有多个调谐路径,并且该方法包括以下步骤:传感器 203 通过操作天线体来检测信号 201 作为感应垫,根据信号判断移动终端的使用状态; 布置调谐电路 204 具有多个调谐路径,一个调谐路径对应移动终端的一种使用状态; 并切换调谐电路 204 根据移动终端的使用状态到相应的调谐路径,对来自移动终端信号源或天线本体的信号进行调谐处理。 在该方法中,由于模块上的通信天线被重新用作传感器的感应垫 203 , 从而解决单独设置与传感器相连的感应垫占用空间较多的问题 203 避免了感应垫对通信的干扰。 [0065] 图6是根据本公开实施例的信号处理方法的流程图。 如图6所示,该方法包括步骤S 602 到小号 606 . [0066] 在步骤S 602 , 调谐电路 204 具有多条调谐路径,用于使一条调谐路径对应移动终端的一种使用状态。 [0067] 在步骤S 604 ,当人体接近时电容的变化是通过使用传感器检测到的 203 和天线体 201 ,根据变化判断移动终端的使用状态。 [0068] 在步骤S 606 , 微处理器 205 切换调谐电路 204 以及天线的接地点根据移动终端的使用状态到相应的路径,并对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 . [0069] 在本实施例中,利用传感器检测电容随着人体靠近的变化 203 和天线体 201 ,根据变化判断移动终端的使用状态,然后调谐电路 204 切换到与使用状态对应的调谐路径,使得移动终端的系统适合当前的使用状态,能够自动将移动终端的系统切换到最佳状态,保证信号质量, 用户体验得到改善。 [0070] 为了进一步提高移动终端在不同使用状态下的性能,图6的方法还包括:天线体设置一个信号馈入点和多个接地点。 201 ,以及在对来自移动终端信号源或天线体的信号进行调谐处理时或之后 201 ,该方法还包括:天线本体的接地点 201 被切换以调整天线体的性能 201 . [0071] 在本实施例的一种实施方式中,可以通过为天线本体设置开关元件来切换天线本体的接地点,开关元件包括控制端、动触点和多个静触点,动触点接地。 一个静触点连接一个接地点,每个静触点对应移动终端的一种使用状态,通过控制端控制开关元件的动触点进行切换。 示例 3 [0072] 根据本发明的另一个实施例,还提供了一种移动终端,包括所述天线本体 201 , 传感器 203 与天线本体连接 201 , 微处理器 205 和调谐电路 204 具有多个调谐路径。 通信信号对传感器信号的干扰 203 通过隔离装置隔离 202 天线体之间 201 和传感器 203 . 微处理器 205 检测移动终端的使用状态,调整移动终端的系统参数。 [0073]图7是根据本发明实施例的移动终端的结构框图。 如图7所示,本实施例的移动终端包括天线信号处理电路,天线信号处理电路的内部结构如图3所示,天线本体 201 在天线信号处理电路中连接到传感器 203 通过隔离装置 202 ,当人体接近天线体时 201 ,天线体之间电容的变化 201 并且可以检测到地面,并且微处理器 205 天线信号处理电路中感应是否有人体靠近,从而调整移动终端的系统参数。 [0074] 在本实施例的设计过程中,为了节省移动终端的空间和元器件,微处理器 205 本实施例中为移动终端的中控CPU,即微处理器进行的判断、计算、控制等动作 205 天线信号处理电路中的处理由移动终端的中央控制器CPU完成。 [0075] 由于天线信号处理电路中的基带处理电路实质上也是一个微控制器,因此天线信号处理电路中的基带处理电路也可以是移动终端的中央处理器CPU。 例 4 [0076] 本发明实施例还提供了一种存储介质,包括存储的程序,在执行程序时执行上述任一方法。 [0077] 可选地,在本实施例中,存储介质可以用于存储用于执行以下步骤S的程序代码 11 到小号 13 . [0078] 在步骤S 11 ,通过将移动终端的天线体作为传感器的感测垫操作来检测信号。 [0079] 在步骤S 12 ,根据该信号确定移动终端的使用状态。 [0080] 在步骤S 13 ,根据移动终端的使用状态,对来自移动终端信号源或天线体的信号进行调谐处理。 [0081] 可选地,在本实施例中,存储介质可以包括但不限于U盘、只读存储器(ROM)、随机存取存储器(RAM)、可移动存储器等各种能够存储程序代码的介质。 硬盘、磁盘或光盘。 例 5 [0082] 本发明实施例还提供一种处理器,用于运行程序,该处理器在执行程序时执行上述任一种方法中的步骤。 [0083] 可选地,在本实施例中,程序用于执行以下步骤S 21 到小号 23 . [0084] 在步骤S 21 ,通过将移动终端的天线体作为传感器的感测垫操作来检测信号。 [0085] 在步骤S 22 ,根据该信号确定移动终端的使用状态。 [0086] 在步骤S 23 ,根据移动终端的使用状态,对来自移动终端信号源或天线体的信号进行调谐处理。 [0087] 可选的,本实施例中的具体示例可以参见上述实施例及可选实施方式中描述的示例,在此不再赘述。 [0088]本领域普通技术人员可以理解,上述公开的方法、装置中的功能模块/单元、系统的全部或部分步骤可以通过软件、固件、硬件或其适当组合来实现。 在硬件实现中,上述描述中的功能模块/单元的划分并不一定对应于物理部件的划分; 例如,一个物理组件可以具有多种功能,或者一个功能或一个步骤可以由多个物理组件共同完成。 一些或所有组件可以实现为由诸如数字信号处理器或微处理器的处理器执行的软件,或者实现为硬件,或者实现为诸如专用集成电路的集成电路。 这样的软件可以分布在可以包括计算机存储介质(或非暂时性介质)的计算机可读介质上。 术语“计算机存储介质”包括以任何方法或技术实现的易失性和非易失性介质、可移动和不可移动介质,用于存储诸如计算机可读指令、数据结构、程序模块或其他数据等信息,正如那些众所周知的 本领域的普通技术人员。 计算机存储介质包括但不限于 RAM、ROM、EEPROM、闪存或其他存储技术、CD-ROM、数字通用磁盘 (DVD) 或其他光盘存储、磁带、磁带、磁盘存储 或其他磁存储设备,或任何其他可用于存储所需信息并可由计算机访问的介质。 [0089] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明,对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。 工业实用性 [0090] 根据本公开,通过将天线体作为传感器的感应垫操作检测到的信号发送给微处理器,微处理器根据该信号确定移动终端的使用状态,并根据使用情况产生控制信号。 移动终端状态,根据控制信号控制调谐电路切换调谐路径,对来自移动终端信号源或天线本体的信号进行调谐处理,解决了现有天线信号处理电路存在的问题 由于与传感器连接的感应垫占用更多空间 203 需要独立设置,以保证天线系统自动切换到最佳状态,提高天线信号质量,减少移动终端内部占用空间,避免对通信天线的干扰,提高用户体验 .(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN109474290A(String), US20210075461A1(String), WO2019047562A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN109474290A(String), US20210075461A1(String), WO2019047562A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20210075461A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN109474290A(String), US20210075461A1(String), WO2019047562A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270689(Integer), CN109474290A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270689(Integer), US20210075461A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.186 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270689(Integer), WO2019047562A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20210075461A1(String), US20210075461A1(String), 1615392000(Integer), 270689(Integer), 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185011(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185011(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185011(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185011(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.263 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.264 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.281 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 放弃(String), 2(Integer), 185011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.296 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Controlling the radiation pattern of a mobile terminal according to a posture of the mobile terminal(String), 根据移动终端的姿态控制移动终端的辐射方向图(String), US9144032B2(String), A transmission method and apparatus of a mobile terminal including an antenna are provided. The transmission method includes determining a posture of the mobile terminal in an active state, updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, and transmitting a transmit signal amplified according to the updated reference power. Accordingly, the reference power is adjusted according to the posture of the mobile terminal, whereby it is possible to control the radiation pattern of antenna of the mobile terminal.(String), 提供了一种包括天线的移动终端的传输方法和装置。 传输方法包括确定移动终端处于激活状态的姿势,通过添加根据移动终端的姿势确定的功率增益来更新预设的参考功率,以及发送根据更新的参考功率放大的发射信号。 因此,根据移动终端的姿势调整参考功率,从而可以控制移动终端的天线的辐射方向图。(String), US13/397031(String), 1329235200(Integer), US9144032B2(String), 1442851200(Integer), 1442851200(Integer), 美国(String), 4(Integer), KR(String), 2(Integer), 13(Integer), US20040176125A1 | US20070216584A1 | US20070259689A1 | US20080317175A1 | US20090253459A1 | US20090305742A1 | US20100279751A1 | US20110021139A1 | US20110237306A1 | US6512917B1 | US7212164B2 | US7330705B2 | US8436784B2(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.310 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185012(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.311 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\3cfc3fae3fd343338cf6c4c1680153c0.png(String), 185012(Integer), 3cfc3fae3fd343338cf6c4c1680153c0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Controlling the radiation pattern of a mobile terminal according to a posture of the mobile terminal(String), 根据移动终端的姿态控制移动终端的辐射方向图(String), US9144032B2(String), A transmission method and apparatus of a mobile terminal including an antenna are provided. The transmission method includes determining a posture of the mobile terminal in an active state, updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, and transmitting a transmit signal amplified according to the updated reference power. Accordingly, the reference power is adjusted according to the posture of the mobile terminal, whereby it is possible to control the radiation pattern of antenna of the mobile terminal.(String), 提供了一种包括天线的移动终端的传输方法和装置。 传输方法包括确定移动终端处于激活状态的姿势,通过添加根据移动终端的姿势确定的功率增益来更新预设的参考功率,以及发送根据更新的参考功率放大的发射信号。 因此,根据移动终端的姿势调整参考功率,从而可以控制移动终端的天线的辐射方向图。(String), US13/397031(String), 1329235200(Integer), US9144032B2(String), 1442851200(Integer), 1442851200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 13(Integer), US20040176125A1 | US20070216584A1 | US20070259689A1 | US20080317175A1 | US20090253459A1 | US20090305742A1 | US20100279751A1 | US20110021139A1 | US20110237306A1 | US6512917B1 | US7212164B2 | US7330705B2 | US8436784B2(String), \20230420\3cfc3fae3fd343338cf6c4c1680153c0.png(String), 11(Integer), 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.342 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 1. A transmission method of a mobile terminal including an antenna, the method comprising:determining a posture of the mobile terminal in an active state;updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, the posture determined according to one of an angle or a position of the mobile terminal in relation to the ground; andtransmitting a transmit signal amplified according to the updated preset reference power in a radiation pattern according to the posture of the mobile terminal,wherein the mobile terminal stores a mapping of a plurality of power gains corresponding to a plurality of different postures, andwherein the radiation pattern is at least one of symmetric and asymmetric.(String), 1.如权利要求10所述的传输装置,其中根据预设参考功率与发射功率的差值确定新的功率增益。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 2. The transmission method of claim 1, wherein the determining of the posture comprises configuring the preset reference power based on analysis of a received signal.(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 3. The transmission method of claim 2, wherein the preset reference power is determined according to strength of the received signal.(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 4. The transmission method of claim 1, wherein the transmitting of the transmit signal comprises updating, when the transmit power is less than the preset reference power, the reference power by adding a new power gain.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 5. The transmission method of claim 4, wherein the new power gain is determined according to a difference value between the preset reference power and the transmit power.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 6. A transmission apparatus of the mobile terminal, the apparatus comprising:a posture detection unit configured to detect a posture of the mobile terminal in an active state, the posture determined according to one of an angle or a position of the mobile terminal in relation to the ground;a memory unit configured to store a mapping of a plurality of power gains to a plurality of different postures;a control unit configured to control the posture detection unit to update a preset reference power by adding a power gain determined according to the posture of the mobile terminal;a Radio Frequency (RF) unit configured to amplify a transmit signal according to the updated preset reference power under the control of the control unit; andan antenna configured to radiate the transmit signal in a radiation pattern according to the posture of the mobile terminal,wherein the radiation pattern is at least one of symmetric and asymmetric.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 7. The transmission apparatus of claim 6, wherein the control unit configures the preset reference power based on analysis of a received signal.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 8. The transmission apparatus of claim 7, wherein the preset reference power is determined according to strength of the received signal.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 9. The transmission apparatus of claim 6, wherein the RF unit comprises:a power amplifier configured to amplify a transmit power of the transmit signal according to the preset reference power; anda power detector configured to determine whether the transmit power is less than the preset reference power.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 10. The transmission apparatus of claim 9, wherein the control unit updates, when the transmit power is less than the preset reference power, the reference power by adding a new power gain.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185012(Integer), 11. The transmission apparatus of claim 10, wherein the new power gain is determined according to a difference value between the preset reference power and the transmit power.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185012(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Feb. 16, 2011 in the Korean Intellectual Property Office and assigned Serial No. 10-2011-0013563, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal. More particularly, the present invention relates to a transmission method and apparatus of a mobile terminal having an antenna in a wireless communication system. [0004]2. Description of the Related Art [0005]Recently, wireless communication systems have been designed to support various multimedia services based on an integrated supplementary functionality such as a Global Positioning System (GPS), Bluetooth, and the Internet. In order to facilitate providing various multimedia services, a high data rate must be secured for transmitting high volume multimedia data. An antenna is one factor that determines transmission performance. Thus research has been conducted to acquire high quality antenna features because the antenna of a mobile terminal is substantially responsible for transmitting signals carrying multimedia services. In a mobile communication terminal, it is preferred to implement the antenna to have an optimal radiation pattern. The optimal radiation pattern can be acquired through several times of tuning processes in a manufacturing state. [0006]Meanwhile, mobile communication terminals are manufactured with a slim and compact design to secure portability. Conventional antennas such as a rod antenna and a helical antenna are exposed partially out of a terminal casing, which compromises portability and causes physical damage of the antenna. In order to address these problems, recent mobile terminals have been equipped with an internal antenna, which is also referred to as an intenna. [0007]However, the conventional mobile terminals are designed to transmit signals in a fixed radiation pattern determined as being optimal, resulting in antenna utilization efficiency problems because the optimal radiation pattern of the antenna is determined without consideration of a user's assumption factor of Electro-Magnetic Interference (EMI), i.e., Specific Absorption Rate (SAR). The signal transmitted according to the radiation pattern of the antenna can be absorbed as noise by the terminal user's body. Such EMI noise can result in a bad influence to the human body, more particularly, to the brain. SUMMARY OF THE INVENTION [0008]An aspect of the present invention is to address at least the above-mentioned problems and or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a transmission method and apparatus of a mobile terminal that is capable of adjusting an antenna's radiation pattern, resulting in improvement of transmission performance. [0009]Another aspect of the present invention is to provide a transmission method and apparatus of a mobile terminal that is capable of reducing Specific Absorption Rate (SAR) by adjusting an antenna's radiation pattern. [0010]In accordance with an aspect of the present invention, a transmission method of a mobile terminal including an antenna is provided. The method includes determining a posture of the mobile terminal in an active state, updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, and transmitting a transmit signal amplified according to the updated reference power. [0011]The transmission method may include amplifying the transmit power of the transmit signal according to the reference power and updating, when the transmit power is less than the reference power, the reference power by adding a new power gain. [0012]In accordance with another aspect of the present invention, a transmission apparatus of the mobile terminal is provided. The apparatus includes a posture detection unit for detecting a posture of the mobile terminal in an active state, a control unit for controlling the posture detection unit to update a preset reference power by adding a power gain determined according to the posture of the mobile terminal, a Radio Frequency (RF) unit which amplifies a transmit signal according to the reference power under the control of the control unit, and an antenna for radiating the transmit signal. [0013]The RF unit may include a power amplifier for amplifying a transmit power of the transmit signal according to the reference power, and a power detector for determining whether the transmit power is less than the reference power. [0014]The control unit may update, when the transmit power is less than the reference power, the reference power by adding a new power gain. [0015]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0016]The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee. [0017]The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 is a schematic diagram illustrating a configuration of a wireless communication system to which a transmission method is applied according to an exemplary embodiment of the present invention; [0019]FIG. 2 is a block diagram illustrating a configuration of the mobile terminal of FIG. 1 according to an exemplary embodiment of the present invention; [0020]FIG. 3 is a circuit diagram illustrating a configuration of the Radio Frequency (RF) transmitter of the RF unit of FIG. 2 according to an exemplary embodiment of the present invention; [0021]FIG. 4 is a flowchart illustrating a transmission method of a mobile terminal according to an exemplary embodiment of the present invention; and [0022]FIG. 5 is a diagram illustrating exemplary radiation patterns of an antenna of a mobile terminal according to an exemplary embodiment of the present invention. [0023]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0024]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, description of well-known functions and constructions may be omitted for clarity and conciseness. [0025]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0026]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0027]FIG. 1 is a schematic diagram illustrating a configuration of a wireless communication system to which a transmission method is applied according to an exemplary embodiment of the present invention. [0028]Referring to FIG. 1, the wireless communication system includes a base station 100 and a mobile terminal 200. [0029]In the wireless communication system, the base station 100 and the mobile terminal 200 can perform radio communication with each other. Once the mobile terminal 200 has entered a service area of the base station 100, it can receive signals from the base station 100. Within the service area of the base station 100, the mobile terminal 200 connects to the base station 100. At this time, the mobile terminal 200 receives signals from the base station 100. The mobile terminal 200 can transmit and receive signals to and from the base station 100 in an active state. For example, the mobile terminal 200 in an active state can perform a call establishment process with the base station 100 and request or wait for an incoming call in a standby mode. [0030]FIG. 2 is a block diagram illustrating a configuration of the mobile terminal of FIG. 1 according to an exemplary embodiment of the present invention. In an exemplary implementation, descriptions are directed to a mobile phone as a representative mobile terminal. [0031]Referring to FIG. 2, the mobile terminal 200 includes a posture detection unit 210, an antenna 220, a Radio Frequency (RF) unit 230, a control unit 240, a memory unit 250, an audio processing unit 260, a display unit 270, and a key input unit 280. [0032]The posture detection unit 210 detects a posture of the mobile terminal 200. That is, the posture detection unit 210 can determine at least one of an angle and location in relation to the ground. The posture detection unit 210 can be implemented by at least one of an acceleration sensor, a gyro sensor, and a terrestrial magnetic sensor. [0033]The antenna 220 receives and transmits radio signals. That is, the antenna 220 radiates and receives radio signals. At this time, Total Radiate Power (TRP) of the transmit signal is determined based on a unique antenna gain of the antenna 220. Here, the antenna gain is determined based on the shape and electric features of the antenna 220. That is, when the transmit signal is input to the antenna with conduction power, the antenna gain is added to the conduction power such that the radiation power is determined based on the conduction power. Accordingly, the transmit signal is radiated with the radiation power at the antenna 220. For example, if the conduction power is 30 dBm and the antenna gain is −3 dBm, the antenna radiates the transmit signal at the radiation power of 27 dBm. [0034]The antenna 220 transmits the transmit signal and receives the receive signal in a preset radiation pattern. Here, the radiation pattern is formed according to the radiation power of the transmit signal to be radiated by the antenna 220. That is, the radiation pattern can vary according to the radiation power of the transmit signal. The antenna 220 can radiate the transmit signal in an asymmetrically-formed radiation pattern in all directions. The antenna 220 also can radiate the transmit signal in a symmetrically-formed radiation pattern in all directions. [0035]The RF unit 230 processes radio frequency signals. The RF unit 210 includes a RF transmitter and a RF receiver. The RF transmitter process the transmit signal to be radiated by means of the antenna 220. The RF receiver processes the radio signal received by means of the antenna 220. [0036]FIG. 3 is a circuit diagram illustrating a configuration of the RF transmitter of the RF unit of FIG. 2 according to an exemplary embodiment of the present invention. [0037]Referring to FIG. 3, the RF transmitter of the RF unit 230 includes a mixer 231, a transceiver 233, a power amplifier 235, a duplexer 237, and a power detector 239. [0038]The mixer 231 transforms the transmit signal frequency. That is, the mixer 231 up-converts the transmit signal frequency from a baseband signal to an intermediate band signal. The transceiver 233 adjusts the frequency of the transmit signal. That is, the transceiver 233 performs filtering to the transmit signal to acquire the necessary frequency bandwidth. That power amplifier 235 amplifies the transmit power according to the reference power. That is, the power amplifier 235 amplifies the transmit power of the transmit signal in correspondence with the reference power. The duplexer 237 outputs the transmit signal to the antenna 220. At this time, the duplexer 237 blocks the received signal to the RF transmitter and guides the received signal from the antenna 220 to the RF receiver. That is, the duplexer 237 separates the transmit and receive signals from each other. When the receive signal is input by means of the antenna 220, the duplexer 237 delivers the receive signal to the RF receiver. The power detector 220 detects the transmit power of the transmit signal. That is, the power detector 239 measures the transmit power of the transmit signal at the input end of the antenna 220. [0039]The control unit 240 controls entire operations of the mobile terminal 200. The control unit 240 includes a data processing unit having a transmitter for encoding and modulating the transmit signal and a receiver for demodulating and decoding the receive signal. The data processing unit can include a modem and a codec pack. Here, the codec pack includes a data codec for processing packet data and an audio codec for processing an audio signal including voice. More particularly in an exemplary implementation, the control unit 240 controls the reference power to be applied to the transmit signal in an active state. The control unit 240 controls the RF unit 230 to amplify the transmit power of the transmit signal according to the reference power. [0040]That is, the control unit 240 configures the reference power by analyzing the receive signal in an active state. Here, the control unit 240 can configure the reference power according to the received signal strength. The control unit 240 also can configure the reference power such that the radiation power becomes greater than a preset threshold value. For example, the control unit 240 can configure the reference power such that the sum of the reference power and the antenna gain is greater than the preset threshold value. The control unit 240 also can configure the reference power periodically. When signal reception is detected, the control unit can configure the reference power. Also, the control unit 240 can configure the reference power such that the radiation power is greater than the preset threshold value. [0041]The control unit 240 also determines the posture of the mobile terminal 200 in an active state. Here, the control unit 240 determines the posture of the mobile terminal 200 based on at least one of an angle or position of the mobile terminal in relation to the ground. The control unit 240 also determines a power gain based on the posture of the mobile terminal 200. The control unit 240 updates the reference power by adding the power gain to the reference power. [0042]The control unit 240 also compares the transmit power of the transmit signal with the reference power. That is, the control unit 240 determines whether the transmit power is less than the reference power. If the transmit power is less than the reference power, the control unit determines the power gain. Here, the control unit 240 can determine the power gain according to the difference between the transmit power and the reference power. The control unit 240 updates the reference power by adding the power gain to the reference power. [0043]The memory unit 250 can include a program memory and a data memory. The program memory stores the programs necessary for controlling general operations of the mobile terminal 200. The program memory can store the programs necessary for adjusting the reference power to be applied to the transmit power according to an exemplary embodiment of the present invention. The data memory stores the data generated while the programs are running. At this time, the data memory can store the power gains corresponding to the postures available for the mobile terminal 200 according to an exemplary embodiment of the present invention. The memory unit 250 also can store the power gains corresponding to the values comparable to the difference value between the transmit power and the reference power according to an exemplary embodiment of the present invention. [0044]The audio processing unit 260 processes the audio signal output by the audio codec of the data processing unit to be played out through a Speaker (SPK) and transfers the transmit audio signal collected through a Microphone (MIC) to the audio codec of the data processing unit. [0045]The display unit 270 displays user data output by the control unit 240. The display unit may be implemented with a Liquid Crystal Display (LCD) and, in this case, the display unit 270 can include an LCD controller, a video memory for storing video data, and LCD devices. In a case where a touchscreen is enabled, the display unit 270 can function as an input device. [0046]The key input unit 280 is provided with a plurality of alphanumeric keys for data input and function keys for setting various functions. [0047]FIG. 4 is a flowchart illustrating a transmission method of a mobile terminal according to an exemplary embodiment of the present invention. FIG. 5 is a diagram illustrating exemplary radiation patterns of an antenna of a mobile terminal according to an exemplary embodiment of the present invention. [0048]Referring to FIG. 4, in the transmission method, the mobile terminal 200 first operates in an active state at step 411. In the active state, the control unit 240 can receive radio signals. In the active state, the control unit configures the reference power at step 413. Here, the control unit 240 can configure the reference power by analyzing the received signal. For example, the control unit 240 can configure the reference power in accordance with the strength of the received signal. The control unit 240 can configure the reference power periodically and can configure the reference power when signal reception is detected. The control unit 240 also can configure the reference power such that the radiation power is greater than a preset threshold power. For example, the control unit 240 can configure the reference power such that the sum of the reference power and the antenna gain is greater than the preset threshold value. For example, if the threshold value is 27 dBm and the antenna gain is −3 dBm, the control unit 240 can set the reference power to 30 dBm. [0049]The control unit 240 then determines the posture of the mobile terminal 200 at step 415. At this time, the control unit 240 determines the posture of the mobile terminal 200 based on at least one of an angle and position of the mobile terminal 200 in relation to the ground. The control unit 240 then determines the power gain according to the posture of the mobile terminal 200 at step 417. At this time, the memory unit 250 can store the power gains corresponding to the angles available in relation with the group as shown in Table 1. That is, the control unit 240 can select the power gain corresponding to the current posture of the mobile terminal 200. For example, when the mobile terminal 200 makes an angle of 90° in relation to the ground, the control unit 240 can select the power gain of +1 dBm. [0050]TABLE 1PosturePower gain (dBm) 76° to 105°+1106° to 165°  0166° to 195°−1—————— [0051]The control unit 240 updates the reference power at step 419. That is, the control unit 240 adds the power gain to the reference power. For example, if the reference power is 30 dBm and the power gain is +1 dBm, the control unit updates the reference power to 31 dBm. The control unit 240 processes the transmit signal at step 421. That is the control unit 240 generates the transmit signal. Sequentially, the control unit 240 controls the RF unit 230 to transmit the transmit signal through the antenna 220. [0052]At this time, the control unit 240 controls the RF transmitter to amplify the transmit power according to the reference power. Here, the power amplifier 235 amplifies the transmit power of the transmit signal with reference to the reference power. In this manner, the radiation power of the antenna 220 is determined based on the transmit power and antenna gain, and the radiation power is determined to be greater than the threshold value. Here, the antenna 220 radiates the transmit signal in the radiation pattern corresponding to the radiation power. For example, the radiation power is 28 dBm, the antenna 220 can radiate the transmit signal in the radiation pattern formed asymmetrically at the center of the antenna 220 as illustrated in part (a) of FIG. 5. If the radiation power 27 dBm, the antenna 220 can radiate the transmit signal in the radiation pattern formed symmetrically at the center of the antenna 220 as illustrated in part (b) of FIG. 5. [0053]Finally, the control unit 240 compares the transmit power of the transmit signal with the reference power at step 423. That is, the transmit power is detected by means of the power detector 239, the control unit 240 determines whether the transmit power is less than the reference power. In this manner, the control unit 240 can determine whether there is power loss in the transmit power as compared to the reference power. If it is determined that the transmit power is equal to or greater than the reference power at step 423, the control unit 240 ends the transmit procedure. [0054]Otherwise, if it is determined that the transmit power is less than the reference power at step 423, the control unit 240 determines the power gain at step 417. That is, if the transmit power is less than the reference power, the control unit 24 determines an occurrence of power loss and thus decides the power gain. For this purpose, the memory unit 250 can store the power gains corresponding to the individual comparison values that can be compared with the difference values between the transmit power and the reference power as shown in Table 2. That is, the control unit 240 can select the power gain corresponding to the difference value between the transmit power and the reference power. For example, if the difference value between the transmit power and the reference power is 2 dBm, the control unit 240 can select the power gain of +1 dBm. Thereafter, the control unit 240 repeats steps 419 to 423. [0055]TABLE 2PosturePower gain (dBm)Greater than 1+2Less than 1 and greater than 0+1Less than 0 and greater than −1  0—————— [0056]Although the description has been directed to the exemplary embodiments where the mobile terminal transmits or receives radio signals through the antenna, the present invention is not limited thereto. For example, exemplary embodiments of the present invention can be applied to the case where the mobile terminal having a transmit antenna and a receive antenna separated from each other. In this case, the function blocks of the mobile terminal operate in a similar manner as described above. However, the duplexer is disabled in the mobile terminal. The power amplifier of the mobile terminal amplifies the transmit signal according to the reference power and transfers the amplified signal to the antenna. In this manner, the mobile terminal adjusts the reference power to be applied to the transmitted signal in an active state and amplifies the transmit power of the transmit signal according to the reference power. [0057]According to exemplary embodiments of the present invention, the mobile terminal can control the radiation pattern of the antenna. That is, the mobile terminal can adjust the reference power to control the radiation pattern of the antenna without changing the shape of the antenna. By adjusting the reference power according to the posture of the mobile terminal, it is possible for the mobile terminal to transmit a signal in a radiation pattern corresponding to the terminal's posture. Also, since the reference power is adjusted based on a comparison result with the transmit power, the mobile terminal can perform fine adjustment of the radiation power. [0058]When the mobile terminal transmits the signal in the radiation pattern formed symmetrically in all directions and centered on the antenna, the Specific Absorption Rate (SAR) can be relatively high. In this case, the reference power is adjusted according to the posture of the mobile terminal such that the mobile terminal can transmit the signal in the radiation pattern formed asymmetrically in all directions and centered on the antenna. In this manner, the mobile terminal can reduce the SAR to the user. For example, when the mobile terminal is in the middle of the communication mode, the posture of the mobile terminal is likely to have the rectangular angle in relation to the ground. In this case, the mobile terminal transmits the signal in the radiation pattern formed asymmetrically in all directions and centered on the antenna, to reduce the SAR. [0059]As described above, the transmission method and apparatus of the mobile terminal having an antenna according to an exemplary embodiment of the present invention can control the radiation pattern of the antenna of the mobile terminal. That is, it is possible to control the radiation pattern of the antenna by adjusting the reference power of the mobile terminal. At this time, the reference power is adjusted according to the posture of the mobile terminal, and thus the mobile terminal can transmit the signal in the radiation pattern corresponding to the posture of the mobile terminal. Also, since the reference power is adjusted according to the comparison result with the transmit power, it is possible to apply fine adjustment of radiation power to the mobile terminal. [0060]When transmitting a signal in the radiation pattern formed symmetrically in all directions and centered on the antenna, the SAR to the user can be relatively high. By adjusting the reference power according to the posture of the mobile terminal, the mobile terminal can transmit the signal in the radiation pattern formed asymmetrically in all direction centering the antenna. In this manner, it is possible to reduce the SAR to the mobile terminal user. For example, in the wireless communication system, the mobile terminal is likely to be postured to have the vertical angle to the ground. At this time, the mobile terminal transmits the signal in the radiation pattern formed asymmetrically in all directions and centered on the antenna, resulting in reduction of SAR of the mobile terminal to the human body. [0061]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims and their equivalents.(String), 优先 [0001] 此申请根据 35 U.S.C. 2011 年 2 月 16 日向韩国知识产权局提交并转让序列号为 10-2011-0013563 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动终端。 更具体地,本发明涉及在无线通信系统中具有天线的移动终端的传输方法和装置。 [0004] 2.相关技术的描述 [0005] 近来,无线通信系统已被设计为支持基于诸如全球定位系统(GPS)、蓝牙和互联网等综合补充功能的各种多媒体服务。 为了便于提供各种多媒体服务,必须确保高数据速率以传输大量多媒体数据。 天线是决定传输性能的一个因素。 由于移动终端的天线主要负责传输承载多媒体服务的信号,因此进行了研究以获得高质量的天线特征。 在移动通信终端中,优选将天线实现为具有最佳辐射方向图。 在制造状态下,通过多次调谐过程可以获得最佳的辐射方向图。 [0006] 同时,移动通信终端采用纤薄紧凑的设计制造,以确保便携性。 传统的天线,如杆状天线和螺旋天线,部分暴露在终端外壳之外,这会损害便携性并导致天线的物理损坏。 为了解决这些问题,最近的移动终端已经配备了内置天线,也称为天线。 [0007] 然而,传统的移动终端被设计成以被确定为最优的固定辐射方向图发送信号,导致天线利用效率问题,因为天线的最佳辐射方向图是在没有考虑用户的电磁干扰假设因素的情况下确定的( EMI),即比吸收率(SAR)。 根据天线的辐射图发射的信号可以被终端用户的身体吸收为噪声。 这种EMI噪声会对人体产生不良影响,尤其是对大脑。 发明内容 [0008] 本发明的一个方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面是提供一种移动终端的传输方法和装置,其能够调整天线的辐射方向图,从而提高传输性能。 [0009] 本发明的另一方面在于提供一种能够通过调整天线的辐射图来降低比吸收率(SAR)的移动终端的传输方法和装置。 [0010] 根据本发明的一个方面,提供了一种包括天线的移动终端的传输方法。 该方法包括确定处于活动状态的移动终端的姿势,通过添加根据移动终端的姿势确定的功率增益来更新预设的参考功率,以及发送根据更新的参考功率放大的发射信号。 [0011] 发送方法可以包括根据参考功率放大发送信号的发送功率,并且当发送功率小于参考功率时,通过增加新的功率增益来更新参考功率。 [0012]根据本发明的另一方面,提供了一种移动终端的传输装置。 该装置包括:姿态检测单元,用于检测移动终端处于活动状态的姿态;控制单元,用于控制姿态检测单元通过添加根据移动终端的姿态确定的功率增益来更新预设参考功率, 射频(RF)单元在控制单元的控制下根据参考功率放大发射信号,以及用于辐射发射信号的天线。 [0013] RF单元可包括用于根据参考功率放大发射信号的发射功率的功率放大器,以及用于确定发射功率是否小于参考功率的功率检测器。 [0014] 当发射功率小于参考功率时,控制单元可以通过增加新的功率增益来更新参考功率。 [0015] 根据以下结合附图公开本发明示例性实施例的详细描述,本领域技术人员将清楚本发明的其他方面、优点和显着特征。 附图的简要说明 [0016] 专利或申请文件包含至少一幅彩色绘图。 专利局将根据请求和支付必要的费用提供本专利或专利申请出版物的彩色附图副本。 [0017] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0018] 图1是图示应用根据本发明示例性实施例的传输方法的无线通信系统的配置的示意图; [0019] 图2是示出根据本发明示例性实施例的图1的移动终端的配置的框图; [0020] 图3是示出根据本发明示例性实施例的图2的RF单元的射频(RF)发送器的配置的电路图; [0021] 图4是示出根据本发明示例性实施例的移动终端的传输方法的流程图; 和 [0022] 图5是图示根据本发明示例性实施例的移动终端的天线的示例性辐射图案的图。 [0023] 在整个附图中,应当注意,相似的附图标记用于描绘相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0024] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物限定的本发明的示例性实施例。 它包括有助于理解的各种具体细节,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对本文描述的实施例进行各种改变和修改。 此外,为了清楚和简明起见,可以省略对公知功能和构造的描述。 [0025] 以下描述和权利要求中使用的术语和词语不限于参考文献的含义,而只是由发明人使用以使得能够清楚和一致地理解本发明。 因此,对于本领域的技术人员来说显而易见的是,本发明的示例性实施例的以下描述仅出于说明的目的而提供,而不是为了限制如所附权利要求及其等同物所定义的本发明的目的。 [0026]应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0027] 图1是示出应用根据本发明示例性实施例的传输方法的无线通信系统的配置的示意图。 [0028] 参考图1,无线通信系统包括基站 100 和一个移动终端 200 . [0029] 在无线通信系统中,基站 100 和移动终端 200 可以相互进行无线电通信。 一旦移动端 200 已进入基站服务区 100 ,它可以接收来自基站的信号 100 . 基站服务区内 100 , 移动端 200 连接到基站 100 . 这时,移动端 200 从基站接收信号 100 . 移动终端 200 可以向基站发送和接收信号 100 处于活动状态。 例如,移动终端 200 在激活状态下可以与基站进行呼叫建立过程 100 并在待机状态下请求或等待来电。 [0030] 图2是示出根据本发明示例性实施例的图1的移动终端的配置的框图。 在示例性实施方式中,描述针对作为代表性移动终端的移动电话。 [0031] 参见图2,移动终端 200 包括姿势检测单元 210 , 天线 220 , 一个射频 (RF) 单元 230 , 一个控制单元 240 , 一个记忆单元 250 , 一个音频处理单元 260 , 一个显示单元 270 , 和一个按键输入单元 280 . [0032] 姿态检测单元 210 检测移动终端的姿态 200 . 即姿态检测单元 210 可以确定相对于地面的角度和位置中的至少一个。 姿态检测单元 210 可以通过加速度传感器、陀螺仪传感器和地磁传感器中的至少一种来实现。 [0033] 天线 220 接收和发送无线电信号。 也就是天线 220 发射和接收无线电信号。 此时,发射信号的总辐射功率(TRP)是根据天线的唯一天线增益确定的 220 . 这里,天线增益是根据天线的形状和电特性确定的 220 . 即,当发射信号以传导功率输入到天线时,天线增益被添加到传导功率,使得基于传导功率确定辐射功率。 因此,发射信号在天线处以辐射功率辐射 220 . 例如,如果传导功率为 30 dBm,天线增益为 -3 dBm,则天线以 27 dBm 的辐射功率辐射发射信号。 [0034] 天线 220 以预设的辐射方向图发射发射信号并接收接收信号。 这里,辐射图是根据天线要辐射的发射信号的辐射功率形成的 220 . 也就是说,辐射图可以根据发射信号的辐射功率而变化。 天线 220 可以在所有方向以不对称形成的辐射模式辐射发射信号。 天线 220 也可以在所有方向以对称形成的辐射模式辐射发射信号。 [0035] 射频单元 230 处理射频信号。 射频单元 210 包括射频发射器和射频接收器。 RF发射器处理要通过天线辐射的发射信号 220 . RF接收器处理通过天线接收到的无线电信号 220 . [0036]图3是示出根据本发明示例性实施例的图2的RF单元的RF发射器的配置的电路图。 [0037] 参考图3,射频单元的射频发射器 230 包括一个混合器 231 , 收发器 233 , 功率放大器 235 , 双工器 237 , 和一个功率检测器 239 . [0038] 搅拌机 231 变换发射信号频率。 也就是搅拌机 231 将发射信号频率从基带信号上变频到中带信号。 收发器 233 调整发射信号的频率。 也就是收发器 233 对发射信号进行滤波以获得必要的频率带宽。 那个功放 235 根据参考功率放大发射功率。 也就是功放 235 对应于参考功率放大发射信号的发射功率。 双工器 237 将发射信号输出到天线 220 . 这时,双工器 237 阻止接收到的信号到射频发射器并引导从天线接收到的信号 220 到射频接收器。 也就是双工器 237 将发送和接收信号相互分离。 通过天线输入接收信号时 220 , 双工器 237 将接收信号传送到射频接收器。 功率检测器 220 检测发射信号的发射功率。 也就是说,功率检测器 239 测量天线输入端发射信号的发射功率 220 . [0039] 控制单元 240 控制移动终端的整个操作 200 . 控制单元 240 包括数据处理单元,其具有用于编码和调制发射信号的发射器和用于解调和解码接收信号的接收器。 数据处理单元可以包括调制解调器和编解码器包。 这里,编解码器包包括用于处理分组数据的数据编解码器和用于处理包括语音的音频信号的音频编解码器。 更具体地,在示例性实施方式中,控制单元 240 控制在激活状态下施加到发射信号的参考功率。 控制单元 240 控制射频单元 230 根据参考功率放大发射信号的发射功率。 [0040] 也就是说,控制单元 240 通过分析处于活动状态的接收信号来配置参考功率。 这里,控制单元 240 可以根据接收到的信号强度配置参考功率。 控制单元 240 还可以配置参考功率,使得辐射功率变得大于预设阈值。 例如,控制单元 240 可以配置参考功率,使得参考功率与天线增益之和大于预设阈值。 控制单元 240 也可以定期配置参考功率。 当检测到信号接收时,控制单元可以配置参考功率。 此外,控制单元 240 可以配置参考功率,使得辐射功率大于预设阈值。 [0041] 控制单元 240 也决定了移动端的姿势 200 处于活动状态。 这里,控制单元 240 确定移动终端的姿势 200 基于移动终端相对于地面的角度或位置中的至少一个。 控制单元 240 还根据移动终端的姿势确定功率增益 200 . 控制单元 240 通过将功率增益添加到参考功率来更新参考功率。 [0042] 控制单元 240 还将发射信号的发射功率与参考功率进行比较。 也就是说,控制单元 240 判断发射功率是否小于参考功率。 如果发射功率小于参考功率,则控制单元确定功率增益。 这里,控制单元 240可以根据发射功率和参考功率的差值来确定功率增益。 控制单元 240 通过将功率增益添加到参考功率来更新参考功率。 [0043] 记忆单元 250 可以包括程序存储器和数据存储器。 程序存储器存储控制移动终端的一般操作所需的程序 200 . 根据本发明的示例性实施例,程序存储器可以存储调整要应用于发射功率的参考功率所需的程序。 数据存储器存储程序运行时生成的数据。 此时,数据存储器可以存储移动终端可用姿势对应的功率增益 200 根据本发明的示例性实施例。 记忆单元 250 根据本发明的示例性实施例,还可以存储与与发射功率和参考功率之间的差值相当的值相对应的功率增益。 [0044] 音频处理单元 260 将数据处理单元的音频编解码器输出的音频信号处理后通过扬声器(SPK)进行播放,并将通过麦克风(MIC)采集的发射音频信号传送到数据处理单元的音频编解码器。 [0045] 显示单元 270 显示控制单元输出的用户数据 240 . 显示单元可以用液晶显示器 (LCD) 来实现,在这种情况下,显示单元 270 可以包括 LCD 控制器、用于存储视频数据的视频存储器和 LCD 设备。 在启用触摸屏的情况下,显示单元 270 可以作为输入设备使用。 [0046] 按键输入单元 280 具有多个用于数据输入的字母数字键和用于设置各种功能的功能键。 [0047] 图4是示出根据本发明示例性实施例的移动终端的传输方法的流程图。 图5是示出根据本发明示例性实施例的移动终端的天线的示例性辐射方向图的图。 [0048] 参见图4,在传输方法中,移动终端 200 首先在步骤中以活动状态运行 411 . 在激活状态下,控制单元 240 可以接收无线电信号。 在激活状态下,控制单元在步骤配置参考功率 413 . 这里,控制单元 240 可以通过分析接收到的信号来配置参考功率。 例如,控制单元 240 可以根据接收信号的强弱配置参考功率。 控制单元 240 可以周期性地配置参考功率,并且可以在检测到信号接收时配置参考功率。 控制单元 240 还可以配置参考功率,使得辐射功率大于预设的阈值功率。 例如,控制单元 240 可以配置参考功率,使得参考功率与天线增益之和大于预设阈值。 例如,如果阈值为 27 dBm,天线增益为 -3 dBm,则控制单元 240 可以将参考功率设置为 30 dBm。 [0049] 控制单元 240 然后确定移动终端的姿势 200 在步骤 415 . 这时,控制单元 240 确定移动终端的姿势 200 基于移动终端的角度和位置中的至少一个 200 相对于地面。 控制单元 240 然后根据移动终端的姿态确定功率增益 200 在步骤 417 . 这时,内存单元 250 可以存储与组相关的可用角度对应的功率增益,如表 1 所示。即,控制单元 240 可选择移动终端当前姿势对应的功率增益 200 . 例如,当移动终端 200 与地面成 90° 角,控制单元240 可选择+1 dBm的功率增益。 [0050] 表格1 姿势 功率增益 (dBm) 76° 至 105° +1 106° 至 165°   0 166° 至 195° −1 — — — — — — [0051] 控制单元 240 在步骤更新参考功率 419 . 也就是说,控制单元 240 将功率增益添加到参考功率。 例如,如果参考功率为 30 dBm,功率增益为 +1 dBm,则控制单元将参考功率更新为 31 dBm。 控制单元 240 在步骤处理发送信号 421 . 那是控制单元 240 产生发射信号。 依次,控制单元 240 控制射频单元 230 通过天线发射发射信号 220 . [0052] 这时,控制单元 240 控制射频发射器根据参考功率放大发射功率。 这里的功放 235 参考参考功率放大发射信号的发射功率。 这样,天线的辐射功率 220 是基于发射功率和天线增益确定的,辐射功率被确定为大于阈值。 在这里,天线 220 以对应于辐射功率的辐射方向图来辐射发射信号。 例如,辐射功率为 28 dBm,天线 220 可以在天线中心不对称形成的辐射方向图中辐射发射信号 220 如图5(a)部分所示。如果辐射功率为27 dBm,则天线 220 可以在天线中心对称形成的辐射方向图中辐射发射信号 220 如图 5 的 (b) 部分所示。 [0053] 最后,控制单元 240 将发射信号的发射功率与参考功率进行比较 423 . 即通过功率检测器检测发射功率 239 , 控制单元 240 判断发射功率是否小于参考功率。 这样,控制单元 240 可以确定发射功率与参考功率相比是否存在功率损耗。 如果在步骤确定发射功率等于或大于参考功率 423 , 控制单元 240 结束发送过程。 [0054] 否则,如果在步骤确定发射功率小于参考功率 423 , 控制单元 240 确定步长的功率增益 417 . 也就是说,如果发射功率小于参考功率,则控制单元 24 确定功率损耗的发生,从而决定功率增益。 为此,存储单元 250 可以存储对应于各个比较值的功率增益,该比较值可以与发射功率和参考功率之间的差值进行比较,如表2所示。即,控制单元 240 可以选择与发射功率和参考功率之间的差值相对应的功率增益。 例如,如果发射功率和参考功率之间的差值为 2 dBm,则控制单元 240 可选择+1 dBm的功率增益。 此后,控制单元 240 重复步骤 419 至 423 . [0055] 表 2 姿势 功率增益 (dBm) 大于 1 +2 小于 1 且大于 0 +1 小于 0 且大于 -1   0 — — — — — — [0056] 尽管描述已经针对移动终端通过天线发送或接收无线电信号的示例性实施例,但是本发明不限于此。 例如,本发明的示例性实施例可以应用于移动终端具有彼此分离的发射天线和接收天线的情况。 在这种情况下,移动终端的功能块以与上述类似的方式操作。 然而,双工器在移动终端中被禁用。 移动终端的功率放大器根据参考功率对发射信号进行放大,并将放大后的信号传输到天线。 以这种方式,移动终端在激活状态下调整要应用于发射信号的参考功率,并根据参考功率放大发射信号的发射功率。 [0057] 根据本发明的示例性实施例,移动终端可以控制天线的辐射方向图。 也就是说,移动终端可以在不改变天线形状的情况下调整参考功率来控制天线的辐射方向图。 通过根据移动终端的姿势调整参考功率,移动终端可以以与终端的姿势对应的辐射图发射信号。 此外,由于参考功率是基于与发射功率的比较结果来调整的,因此移动终端可以对辐射功率进行微调。 [0058] 当移动终端以天线为中心在各个方向对称形成的辐射图发射信号时,比吸收率(SAR)可以相对较高。 在这种情况下,参考功率根据移动终端的姿态进行调整,使得移动终端可以以天线为中心在所有方向上不对称形成的辐射图发射信号。 以这种方式,移动终端可以降低对用户的SAR。 例如,当移动终端处于通信模式的中间时,移动终端的姿态很可能与地面呈直角。 在这种情况下,移动终端以天线为中心在所有方向不对称形成的辐射方向图发送信号,以降低SAR。 [0059] 如上所述,根据本发明示例性实施例的具有天线的移动终端的传输方法和装置可以控制移动终端的天线的辐射方向图。 也就是说,可以通过调整移动终端的参考功率来控制天线的辐射方向图。 此时,根据移动终端的姿态调整参考功率,从而使移动终端能够以与移动终端的姿态对应的辐射图发射信号。 此外,由于根据与发射功率的比较结果来调整参考功率,因此可以对移动终端应用辐射功率的微调。 [0060] 当以天线为中心在所有方向上对称形成的辐射方向图传输信号时,对用户的 SAR 可能相对较高。 通过根据移动终端的姿势调整参考功率,移动终端可以在以天线为中心的所有方向上不对称形成的辐射图发射信号。 以这种方式,可以降低对移动终端用户的SAR。 例如,在无线通信系统中,移动终端很可能被摆成与地面具有垂直角的姿势。 此时,移动终端以天线为中心,向各个方向不对称形成的辐射方向图发射信号,导致移动终端对人体的SAR降低。 [0061] 尽管本发明已经参照其某些示例性实施例进行了展示和描述,但是本领域技术人员可以在不背离本发明的精神和范围的情况下对其中的形式和细节进行各种改变。 附加的权利要求及其等价物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101778528B1(String), KR1020120094213A(String), US20120208554A1(String), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101778528B1(String), KR1020120094213A(String), US20120208554A1(String), US9144032B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.470 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101778528B1(String), KR1020120094213A(String), US20120208554A1(String), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.471 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.472 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270690(Integer), KR101778528B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270690(Integer), KR1020120094213A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270690(Integer), US20120208554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270690(Integer), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9144032B2(String), US9144032B2(String), 1442851200(Integer), 270690(Integer), 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185012(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185012(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974672(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185012(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75902(Integer), 2(Integer), 185012(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75902(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.565 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US11126275B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US11126275B2(String), An apparatus for presenting a panoramic photo in a mobile terminal receives a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle.(String), 一种在移动终端中呈现全景照片的装置,接收触发指令,用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式 ; 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。(String), US16/841961(String), 1586188800(Integer), US11126275B2(String), 1632153600(Integer), 1632153600(Integer), 美国(String), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9342998B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185013(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2570d5e98ad94d78917a9bfa490af724.png(String), 185013(Integer), 2570d5e98ad94d78917a9bfa490af724.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US11126275B2(String), An apparatus for presenting a panoramic photo in a mobile terminal receives a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle.(String), 一种在移动终端中呈现全景照片的装置,接收触发指令,用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式 ; 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。(String), US16/841961(String), 1586188800(Integer), US11126275B2(String), 1632153600(Integer), 1632153600(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9342998B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), \20230420\2570d5e98ad94d78917a9bfa490af724.png(String), 20(Integer), 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 1. A method for presenting a panoramic photo using a mobile terminal, the method comprising:photographing the panoramic photo while the mobile terminal is moving in a first direction;storing attribute information of the panoramic photo, wherein the attribute information includes a photo type indicating that the panoramic photo is panoramic;displaying only a part of the panoramic photo in a normal mode;receiving a slide operation on the panoramic photo in the normal mode;displaying another part of the panoramic photo in response to the slide operation in the normal mode;receiving an instruction for entering an immersive browsing mode; andperforming the following when in the immersive browsing mode:displaying only a first part of the panoramic photo;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 1.一种使用移动终端呈现全景照片的方法,该方法包括:移动终端在第一方向移动时拍摄全景照片;存储全景照片的属性信息,其中,属性信息包括表示全景照片为全景的照片类型;在正常模式下仅显示全景照片的一部分;在正常模式下接收对全景照片的滑动操作;在正常模式下响应滑动操作显示全景照片的另一部分;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下执行以下操作:仅显示全景照片的第一部分;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 2. The method of claim 1, wherein the first direction is either from left to right or from right to left, and wherein the first direction is stored in the attribute information.(String), 2.如权利要求1所述的方法,其中第一方向是从左到右或从右到左,其中第一方向存储在属性信息中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 3. The method of claim 2, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 3.如权利要求2所述的方法,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 4. The method of claim 1, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 4.如权利要求1所述的方法,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 5. The method of claim 1, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 5.如权利要求1所述的方法,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 6. The method of claim 1, further comprising:displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 6.如权利要求1所述的方法,还包括:在正常模式下显示图标;检测图标上的输入;和响应于检测到图标上的输入而进入沉浸式浏览模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 7. The method of claim 1, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 7.如权利要求1所述的方法,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 8. The method of claim 7, further comprising:detecting a rotation angle of the mobile terminal in real time; anddisplaying the panoramic photo in the movable way when the rotation angle is greater than a preset rotation angle threshold.(String), 8.如权利要求7所述的方法,还包括:实时检测移动终端的旋转角度;和当旋转角度大于预设的旋转角度阈值时,以可移动的方式显示全景照片。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 9. The method of claim 8, further comprising determining a minimum movement value of the movable way using the following equation:s=d⁢φ1φ2,wherein s is the minimum movement value, wherein d is a width of the panoramic photo, wherein φ1 is the preset rotation angle threshold, and wherein φ2 is a rotation angle of the mobile terminal photographing the panoramic photo in the first direction.(String), 9.如权利要求8所述的方法,还包括使用以下等式确定可移动方式的最小移动值:s=d⁢φ1φ2,其中s为最小移动值,d为全景照片的宽度,其中φ1为预设旋转角度阈值,其中φ2为移动终端拍摄全景照片在第一方向的旋转角度。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 10. The method of claim 1, wherein rotation of the mobile terminal in either the first direction or the second direction is detected by a gyro sensor of the mobile terminal.(String), 10.如权利要求1所述的方法,其中移动终端沿第一方向或第二方向的旋转由移动终端的陀螺仪传感器检测。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 11. A mobile terminal, comprising:a processor; anda memory coupled to the processor and comprising instructions that, when executed by the processor, cause the mobile terminal to:photograph a panoramic photo while the mobile terminal is moving in a first direction;store attribute information of the panoramic photo, wherein the attribute information includes a photo type indicating that the panoramic photo is panoramic;display only a part of the panoramic photo in a normal mode;receive a slide operation on the panoramic photo in the normal mode;display another part of the panoramic photo in response to the slide operation in the normal mode; andreceive an instruction for entering an immersive browsing mode;perform the following when in the immersive mode:display only a first part of the panoramic photo;detect the mobile terminal rotating in the first direction;display a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detect the mobile terminal rotating in a second direction; anddisplay a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 11.移动终端,包括:处理器;和存储器耦合到处理器并且包括当由处理器执行时使移动终端:移动终端在第一方向移动时拍摄全景照片;存储全景照片的属性信息,其中,属性信息包括表示全景照片为全景的照片类型;在正常模式下只显示全景照片的一部分;在普通模式下接收对全景照片的滑动操作;在正常模式下响应滑动操作显示全景照片的另一部分;和接收进入沉浸式浏览模式的指令;在沉浸式模式下执行以下操作:仅显示全景照片的第一部分;检测第一方向旋转的移动终端;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 12. The mobile terminal of claim 11, wherein the first direction is either from left to right or from right to left, and wherein the first direction is stored in the attribute information.(String), 12.如权利要求11所述的移动终端,其中第一方向是从左到右或从右到左,其中第一方向存储在属性信息中。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 13. The mobile terminal of claim 12, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 13.如权利要求12所述的移动终端,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 14. The mobile terminal of claim 11, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 14.如权利要求11所述的移动终端,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 15. The mobile terminal of claim 11, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 15.如权利要求11所述的移动终端,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 14(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 16. The mobile terminal of claim 11, wherein the instructions further cause the mobile terminal to:display an icon in the normal mode;detect an input on the icon; andenter the immersive browsing mode in response to detecting the input on the icon.(String), 16.如权利要求11所述的移动终端,其中该指令进一步使移动终端:在正常模式下显示一个图标;检测图标上的输入;和响应于检测到图标上的输入进入沉浸式浏览模式。(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 17. The mobile terminal of claim 11, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 17.如权利要求11所述的移动终端,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 18. The mobile terminal of claim 17, wherein the instructions further cause the mobile terminal to:detect a rotation angle of the mobile terminal in real time; anddisplay the panoramic photo in the movable way when the rotation angle is greater than a preset rotation angle threshold.(String), 18.如权利要求17所述的移动终端,其中该指令进一步使移动终端:实时检测移动终端的旋转角度;和当旋转角度大于预设的旋转角度阈值时,以可移动的方式显示全景照片。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 19. The mobile terminal of claim 18, wherein the instructions further cause the mobile terminal to determine a minimum movement value of the movable way using the following equation:s=d⁢φ1φ2,wherein s is the minimum movement value, wherein d is a width of the panoramic photo, wherein φ1 is the preset rotation angle threshold, and wherein φ2 is a rotation angle of the mobile terminal photographing the panoramic photo in the first direction.(String), 19.如权利要求18所述的移动终端,其中指令还使移动终端使用以下等式确定可移动方式的最小移动值:s=d⁢φ1φ2,其中s为最小移动值,d为全景照片的宽度,其中φ1为预设旋转角度阈值,其中φ2为移动终端拍摄全景照片在第一方向的旋转角度。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185013(Integer), 20. The mobile terminal of claim 11, further comprising a gyro sensor coupled to the processor and configured to detect rotation of the mobile terminal in either the first direction or the second direction.(String), 20.如权利要求11所述的移动终端,还包括陀螺仪传感器耦合到处理器并被配置为检测移动终端在第一方向或第二方向上的旋转。(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.770 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185013(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 16/266,498 filed on Feb. 4, 2019, which is a continuation of U.S. patent application Ser. No. 15/483,724 filed on Apr. 10, 2017, now U.S. Pat. No. 10,222,877, which is a continuation of U.S. patent application Ser. No. 14/735,625 filed on Jun. 10, 2015, now U.S. Pat. No. 9,621,802, which is a continuation of International Patent Application No. PCT/CN2014/079950 filed on Jun. 16, 2014. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present disclosure. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present disclosure. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present disclosure. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present disclosure. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present disclosure. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present disclosure. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present disclosure. [0046]FIGS. 10A, 10B, 10C, and 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present disclosure, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present disclosure, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps. [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present disclosure, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present disclosure, there may be multiple implementation manners for implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present disclosure in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps. [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present disclosure, a user may input, using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present disclosure, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present disclosure, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present disclosure, i(String), 相关申请的交叉引用 [0001] 该申请是美国专利申请序列号的延续。 2019 年 2 月 4 日提交的第 16/266,498 号美国专利申请的延续。 2017 年 4 月 10 日提交的第 15/483,724 号,现为美国专利。 第 10,222,877 号,是美国专利申请序列号的延续。 2015 年 6 月 10 日提交的第 14/735,625 号,现为美国专利。 美国专利第 9,621,802 号,是 2014 年 6 月 16 日提交的国际专利申请号 PCT/CN2014/079950 的继续申请。所有上述申请的全部内容通过引用并入本文。 技术领域 [0002] 本 发明涉及通信技术领域,尤其涉及一种移动终端中全景照片的呈现方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,移动终端的使用范围和环境也越来越多样化。 例如,目前很多移动终端,如手机、个人数字助理、个人电脑等都具有全景拍摄的功能。 [0004] 当移动终端进行全景拍摄时,用户旋转移动终端拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 然后可以将多张拍摄的照片按照上述的拼接原理拼接成一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,会在全景照片上浏览到比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端中呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作较为复杂。 概括 [0006] 本发明实施例提供一种全景照片在移动终端中的呈现方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 第一方面,提供了一种全景照片在移动终端中的呈现方法,包括:检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为浏览模式。 其中全景照片随着移动终端的旋转而移动,若检测到触发指令,则检测并确定移动终端的旋转角度,根据确定的旋转角度移动呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实现方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009]结合第一方面的第一种实现方式,在第二种实现方式中,所述确定移动终端在旋转过程中所处的放置方向包括检测移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考的Z轴 三维坐标系垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于参考三维X-Y平面方向的夹角确定- 维度坐标系,移动终端在旋转过程中所处的放置方向。 [0010] 结合第一方面的第二种实现方式,在第三种实现方式中,所述根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为竖直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0011] 结合第一方面的第二种实现方式或第一方面的第三种实现方式,在第四种实现方式中,所述根据放置方向确定移动终端的旋转角度包括: 其中,旋转过程中移动终端所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为旋转过程中移动终端对应的轴向。 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者判断旋转过程中移动终端所处的放置方向为竖直放置方向 ,将参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 分别以轴向为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实现方式,在第五种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013]结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括确定: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动终端中以正常模式呈现的全景照片移动包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实现方式中,所述检测确定移动终端的旋转角度之前,还包括提供用于指示旋转移动终端的提示信息。 [0015] 结合第一方面的第七种实现方式,在第八种实现方式中,所述提供用于指示旋转移动终端的提示信息之前,所述方法还包括: 获取旋转时保存的移动终端的旋转方向。 拍摄全景照片,提供用于指示旋转移动终端的提示信息包括:根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0016] 第二方面,提供了一种全景照片在移动终端中的呈现装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,所述触发指令用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元,所述沉浸式浏览模式为全景照片随着移动终端移动的浏览模式。 旋转,所述判断单元,用于接收检测单元发送的检测结果,若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送给呈现单元,呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0017] 结合第二方面,在第一种实现方式中,所述确定单元用于通过以下方式确定所述移动终端的旋转角度,确定所述移动终端在旋转过程中所处的放置方向,并确定 移动终端根据放置方向的旋转角度。 [0018] 结合第二方面的第一种实现方式,在第二种实现方式中,所述确定单元具体用于通过如下方式确定移动终端在旋转过程中检测角度的放置方向。 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 定位,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端在rota中的放置方向 化过程。 [0019]结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元,用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,通过如下方式确定: 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向相对于参考三维的X-Y平面方向的夹角 -维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于该方向的夹角 参考三​​维坐标系的X-Y平面的夹角大于45度,确定th e 旋转过程中移动终端所处的放置方向为水平放置方向。 [0020] 结合第二方面的第二种实现方式或第二方面的第三种实现方式,在第四种实现方式中,所述确定单元,用于通过以下方式,根据所述移动终端的旋转角度确定所述移动终端的旋转角度。 放置方向若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 rotation process为垂直放置方向,在refe中使用X轴方向或Y轴方向 以三维坐标系作为移动终端在旋转过程中对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实现方式,在第五种实现方式中,所述装置还包括判断单元,所述判断单元根据所述确定的旋转角度,在所述呈现单元移动前,确定所述全景图 在移动终端中以正常模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元还用于在所述呈现单元根据确定的旋转角度移动之前,以正常模式呈现的全景照片处于 移动终端,根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 呈现单元,用于将移动终端中正常模式呈现的全景照片按如下方式移动,使全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0023] 结合第二方面,在第七种实现方式中,所述装置还包括提示单元,所述提示单元用于接收所述检测单元发送的检测结果; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示旋转移动终端的提示信息。 [0024]结合第二方面的第七种实现方式,在第八种实现方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄所述全景照片时保存的所述移动终端的旋转方向 , 向提示单元发送获取的拍摄照片时保存的移动终端的旋转方向, 提示单元用于通过以下方式提供用于指示旋转的提示信息 移动终端根据获取单元获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0025] 第三方面,提供了一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于在检测到输入设备输入触发指令时,根据检测确定的旋转角度移动移动终端中以正常模式呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实现方式,在第二种实现方式中,所述传感器用于在检测重力角度的旋转过程中,通过如下方式确定所述移动终端所处的放置方向 移动终端的方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 ,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端的重力方向与相对方向的夹角确定 参考三​​维坐标系的X-Y平面,旋转过程中移动终端所在的放置方向 秒。 [0028] 结合第三方面的第二种实现方式,在第三种实现方式中,所述传感器用于根据所述移动终端的重力方向相对于X-Y方向的夹角,通过如下方式进行判断 参考三​​维坐标系的平面,移动终端的重力方向相对于参考三维的X-Y平面方向的夹角时移动终端在旋转过程中所处的放置方向 坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面大于45度,确定放置 旋转过程中移动终端所处的方向为水平放置方向。 [0029]结合第三方面的第二种实现方式或第三方面的第三种实现方式,在第四种实现方式中,所述传感器,用于通过如下方式确定所述移动终端根据放置的旋转角度 方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向作为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 旋转过程为垂直放置方向,参考三中X轴方向或Y轴方向 移动终端在旋转过程中对应的轴向为维坐标系,移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,移动所述移动设备中以正常模式呈现的全景照片。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于,在移动终端中以正常模式呈现的全景照片根据确定的旋转角度移动之前,确定 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 拍摄后,处理器用于移动终端中正常模式下呈现的全景照片,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0032] 结合第三方面,在第七种实现方式中,处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示所述移动终端旋转的提示信息之前,获取所述移动终端的旋转方向,即 拍摄全景照片时保存, 处理器用于按照以下方式提供用于指示旋转移动终端的提示信息, 提供用于指示旋转移动终端的提示信息 获取的旋转方向。 [0034] 本发明实施例提供的一种移动终端全景照片呈现方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测到,检测并确定移动终端的旋转角度; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . 附图说明 [0035]为更加清楚地描述本发明实施例的技术方案,下面对实施例描述所需的附图进行简单介绍。 [0036] 图1为本发明实施例提供的全景照片在移动终端中的呈现方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一种实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端的旋转角度的过程的示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所处放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实现示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实现示意图。 [0043] 图8是根据本发明实施例的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例的全景照片浏览过程的实现示意图。 [0046] 图10A、10B、10C和10D是根据本发明实施例的移动终端中全景照片呈现装置的结构示意图。 [0047] 图11为本发明实施例提供的移动终端的结构示意图。 具体实施方式 [0048] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 本发明实施例提供的移动终端中全景照片的呈现方法,全景照片随着移动终端的旋转而移动。 本发明实施例中为了描述方便,将全景照片随着移动终端旋转而移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为“沉浸式浏览模式”。 以下简称正常模式,当然不限于此; 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览以普通模式显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤。 [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 本发明实施例中,若检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :移动呈现,根据S中确定的旋转角度 102 ,移动终端正常显示的全景照片。 [0055] 本发明实施例提供的移动终端中全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . [0056] 在本发明实施例中,实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在用户触发移动终端进入沉浸式浏览模式后立即以预定方式旋转移动终端,该预定方式可以例如通过用户手册预先学习得到。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示旋转移动终端的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供用于指示旋转移动终端的提示信息的实现方式为例,对全景照片在移动终端中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的全景照片在移动终端中的呈现方法的另一种实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤。 [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 在本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,本发明实施例可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 启用控件的启用状态用于确定是否启用沉浸式浏览模式,当检测到启用控件被启用时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面设置沉浸式浏览按钮。 When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选地,本发明实施例还可以在检测到用户正在浏览全景照片时,提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片随着移动终端的旋转而移动。 通常,为了更好的浏览全景照片,可以提供用于指示旋转移动终端的提示信息,以告知用户移动终端需要按照预设方向进行旋转,该预设方向可以为 例如,从左向右旋转,当然,也可以从右向左旋转。 [0064] 在本发明实施例中,提供的提示信息可以是在显示界面上显示的文字信息,当然,也可以是通过语音输出的方式通知的语音信息,本发明实施例对此不做限定。 [0065] 可选的,本发明实施例还可以获取拍摄全景照片时保存的移动终端的旋转方向,并以提示信息的形式通知获取的旋转方向。 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,提示用户根据获取的拍摄全景照片时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,从而及时控制全景照片移动。 [0068] 用户在拍摄全景照片时,一般会将移动终端定位在确定的放置方向上。 但是,用户在浏览全景照片时,很可能会使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了更加准确地浏览全景照片,在旋转过程中,可以根据移动终端所处的放置方向来确定移动终端的旋转角度。 [0069] S中移动终端旋转角度的确定过程 203 本发明实施例可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 本发明实施例中,可以利用设置在移动终端中的重力传感器指示的移动终端的重力方向,确定移动终端所在的放置方向,确定移动终端的旋转角度。 使用设置在移动终端中的陀螺仪传感器的角度。 可选地,在本发明实施例中,用于确定移动终端的放置方向的重力传感器和用于确定移动终端的旋转角度的陀螺仪传感器可以在用于指示移动终端的触发指令时被启用。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选地,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤。 [0074] 小号 2031 a :以移动终端屏幕所在平面为基准,建立参考三维坐标系。 [0075]本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面平行于该平面 移动终端屏幕所在平面,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也根据移动终端的不同放置方向进行旋转。 例如,参考三维坐标系的示意图分别对应图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的夹角 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过在S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选地,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于基准三的X-Y平面方向的夹角- 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为竖直放置方向。 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所处的放置方向 旋转过程中为水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为竖直放置方向,或者为水平放置方向,本发明实施例可以设置为竖直放置方向。 [0081] 本发明实施例中,如果利用移动终端的重力方向相对于基准三的X-Y平面方向的夹角来确定移动终端在旋转过程中所处的放置方向—— S 中的维度坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 . [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 本发明实施例在确定移动终端在旋转过程中所处的放置方向为水平放置方向时,采用参考三维坐标系中Z轴的方向 作为移动终端在旋转过程中对应的轴向; 或者,当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 用作移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,本发明实施例中,上述移动终端在旋转过程中对应的轴向只是为了简化确定移动终端旋转角度的过程,具体的确定方式不作限定。 至此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺仪传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于对应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度移动移动终端正常显示的全景照片。 [0088] 在本发明实施例中,在浏览全景照片时,一般先以普通浏览方式显示全景照片; 例如,可以是分辨率较低的全景照片,或者只有全景照片的最左部分或全景照片的最右部分等部分全景照片显示在手机的显示屏中 终端。 本发明实施例在确定移动终端的旋转角度后,可以移动终端中正常模式显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实施方式对移动终端中正常模式显示的全景照片进行移动。 例如,移动终端在正常模式下显示的全景照片可以沿与移动终端的旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,本发明实施例中,为了实现全景照片的平滑移动,可以预先设置旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现了全景照片的平滑移动。 如果没有达到预设的旋转角度阈值,全景照片可能不会被移动。 [0091] 本发明实施例中,根据确定的移动终端的旋转角度,将移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向在S中移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端的旋转方向相同的方向移动时,也可以采用类似的方式)。 [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,则执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常模式显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,本发明实施例中,为了进一步增强平滑移动的效果,还可以确定最小位移,当控制全景图像沿与移动终端的旋转方向相反的方向移动时, 照片每次移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,可以根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度以及全景照片沿a的照片宽度,确定全景照片的最小位移量。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录并保存,可以是 直接从本发明实施例拍摄全景照片时保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选地,在本发明实施例中,确定全景照片的最小位移可以采用如下方式。 全景照片的最小位移根据公式确定 [0097] s = d ⁢ φ 1 φ2 , 其中s是全景照片的最小位移; d为全景照片的照片宽度; φ 1 为预设旋转角度阈值; φ2为拍摄全景照片时移动终端的旋转角度。 [0098] 本发明实施例中,对于浏览的全景照片,在确定全景照片时,全景照片的照片宽度d和拍摄全景照片时移动终端的旋转角度φ2为固定值(如果 在拍摄全景照片的过程中记录了旋转角度φ2,使用记录的值;如果在拍摄过程中没有记录旋转角度φ2,则可以参考一些参考值,例如180度或360度作为旋转角度。 角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,适当的旋转角度阈值φ 1 可能是预设的。 若预设旋转角度阈值φ 1 固定后,确定全景照片在旋转过程中移动的最小位移量。 在浏览全景照片的过程中,实时检测并确定移动终端的旋转角度,如果确定移动终端的旋转角度达到预设的旋转角度阈值CI,则移动全景照片 为与移动终端旋转方向相反方向的最小位移。 [0099] 本发明实施例中,移动终端的旋转角度可以为移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,可以认为上一次移动全景照片时移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为持续执行并重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值φ 1,可以将移动终端的初始旋转角度设置为0,检测并确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值来移动全景照片。 例如,移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 −1度,全景照片不动; 当移动端旋转到φ 1 度,全景照片移动最小位移,重新设置旋转角度,继续检测移动端的旋转角度; 当移动端旋转到φ 1 度,全景照片再次移动最小位移,如此循环直到移动终端停止转动。 [0100] 进一步地,在本发明实施例中,移动全景照片的过程可以是立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,则移动全景照片。 ; 例如,预设的旋转角度阈值φ 1 为5度,当旋转角度达到5度时,全景照片移动到最小位移。 移动全景照片的过程也可以是延时执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后,在一段时间内将全景照片移动最小位移量 临界点。 [0101] 移动终端的旋转角度还可以为移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以为a 随着用户移动移动终端不断积累价值。 此时,可以设置全景照片移动的位移与旋转角度成正比关系。 即,移动终端旋转角度越大,全景照片移动的位移越大,移动终端旋转角度越小,全景照片移动的位移越小。 [0102] 上述移动全景照片的方式和最小位移的确定方式还可以有其他实施方式,本发明不对其具体实施方式进行限定。 [0103] 小号 205 :以沉浸式浏览方式呈现全景照片。 [0104] 本发明实施例在沉浸式浏览模式下实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种全景照片的呈现方式可以采用现有的实施方案,例如,在呈现全景照片时,在将全景照片适配显示屏尺寸的过程中可以采用现有的实施方式。 [0105]本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移并呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,而不需要手动在移动终端的屏幕上滑动来浏览全景照片,简单易行。 操作方便。 [0106] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,当然不限于此。 [0107] 本发明实施例提供的控制全景照片在移动终端中呈现的方法的实现基于拍摄全景照片时保存的照片参数,该照片参数例如为: 拍摄全景照片时移动终端旋转,移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的移动终端中全景照片的呈现方法,在拍摄全景照片时,该方法也可以区别于现有的全景照片拍摄。 本发明以下实施例结合实际案例,举例说明全景照片的拍摄过程和浏览过程。 [0108] 图9A示出了根据本发明实施例的全景照片拍摄过程的实现示意图。 如图9A所示,实施过程包括以下步骤。 [0109] 小号 301 :启用全景拍摄模式。 [0110] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0111] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0112] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0113] 本发明实施例中,可以通过陀螺仪传感器在S中启动的角度来确定移动终端的旋转角度。 302 旋转。 [0114] 小号 305 :保存拍摄的全景照片的属性信息。 [0115] 本发明实施例中,保存的全景照片的属性信息至少包括照片类型、拍摄角度和照片尺寸,其中,照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0116] 可选地,本发明实施例中,保存的全景照片的属性信息还可以包括拍摄全景照片时移动终端的旋转方向,该旋转方向例如可以为从右向左, 当然,也可能是从左到右。 [0117] 图9B示出了根据本发明实施例的全景照片浏览过程的实现示意图。 如图9B所示,实施过程包括以下步骤。 [0118] 小号 401 :检测用户浏览的照片类型。 [0119] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行S 403 ; 否则,以正常的照片浏览方式浏览照片。 [0120] 小号 403 :当检测到用户触发了用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0121] 小号 404 :用户通过旋转移动端浏览全景照片。 [0122] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 具体的确定过程可以参见前述实施例的相关描述。 [0123] 小号 406 :根据S中确定的放置方向,确定移动终端在相应轴向的旋转角度 405 以及陀螺仪传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端在Z方向上旋转的角度 -轴,当移动终端的放置方向为竖直放置方向时,确定移动终端在X轴或Y轴方向上旋转的角度。 [0124] 小号 407 :判断旋转角度是否在S中确定 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0125] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移量。 [0126] 小号 409 :检测移动终端的放置方向和旋转角度; 当移动端的放置方向改变时,执行S 405 ,当旋转角度发生变化时,执行S 407 . [0127] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,从而及时调整全景照片的移动。 [0128] 本发明实施例提供的移动终端中全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0129] 基于上述实施例提供的移动终端中全景照片的呈现方法,本发明实施例还提供了一种装置 900 用于在移动终端呈现全景照片。 如图 10A 所示,该装置 900 包括一个检测单元 901 , 决定单位 902 , 和一个呈现单元 903 . [0130] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元 902 ,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动的浏览模式。 [0131] 决定单位 902用于接收检测单元发送的检测结果 901 ; 若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的移动终端的旋转角度发送给呈现单元 903 . [0132] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0133] 在第一种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端的旋转角度,确定移动终端在旋转过程中所处的放置方向,根据放置方向确定移动终端的旋转角度。 [0134] 在第二种实施方式中,所述确定单元 902 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0135] 在第三种实施方式中,确定单元 902 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 位于旋转过程中的是垂直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0136] 在第四种实施方式中,所述确定单元 902 用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0137] 在第五种实施方式中,所述装置还包括判断单元 904 , 如图 10B 所示, 在呈现单元之前 903判断单元根据确定的旋转角度移动移动终端中正常模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0138] 在第六种实施方式中,所述确定单元 902 还配置在呈现单元之前 903 移动,根据确定的旋转角度移动终端中正常模式下呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,全景时移动终端的旋转角度 拍摄全景照片时,全景照片沿移动终端旋转方向的照片宽度,以及呈现单元 903 用于将移动终端中正常模式下呈现的全景照片按照如下方式移动,将全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量。 [0139] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供用于指示旋转移动终端的提示信息。 [0140] 在第八种实施方式中,所述装置还包括获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,并发送给提示单元 905 ,获取拍照时保存的移动终端的旋转方向,以及提示单元 905 用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取单元获取的旋转方向提供用于指示旋转移动终端的提示信息 906 . [0141] 需要说明的是,对于本发明实施例图10A至图10D提供的全景照片在移动终端中的呈现装置,如果不描述在移动终端中实现全景照片的呈现过程 不够详细,可以参见方法实施例的相关描述,在此不再赘述。 [0142] 本发明实施例提供的移动终端中全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0143] 基于上述实施例提供的全景照片在移动终端中的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动端 1000 包括一个输入设备 1001 , 一个传感器 1002 , 处理器 1003 , 和一个显示屏 1004 ,其中输入设备 1001 用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,所述传感器 1002 用于检测移动终端的旋转角度,处理器 1003 用于当检测到输入设备输入触发指令时1001 ,根据检测确定的旋转角度移动移动终端中正常模式呈现的全景照片,显示屏幕 1004 用于呈现全景照片。 [0144] 本发明实施例中,输入设备可以是一个或多个 1001 ,例如,输入设备 1001 可能是显示屏或按钮,可能与处理器集成在一起 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可能连接到处理器 1003 使用有线连接(例如电缆/端口)或无线连接(例如蓝牙)。 [0145] 处理器 1003 可以在单芯片、多芯片或多个电子元件上实现,可以采用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0146] 可能有一个或多个传感器 1002 ,其中传感器 1002 可能有也可能没有运算处理功能。 例如,传感器 1002 在本发明实施例中,可以为重力传感器和陀螺仪传感器中的至少一种。 [0147] 在本公开的该实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0148] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0149] 第二种实现方式,传感器 1002 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0150] 第三种实现方式,传感器 1002 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 旋转过程中位于垂直放置方向,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定 旋转过程中移动终端所处的放置方向为水平放置方向。 [0151] 在第四种实现方式中,传感器 1002用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0152] 在第五种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,将在移动终端中以正常模式呈现的全景照片确定移动终端的旋转角度达到预设的旋转角度阈值。 [0153] 在第六种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移, 拍摄全景照片时的移动终端,以及拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度,以及处理器 1003 用于移动终端中正常模式下呈现的全景照片的移动方式: 将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0154] 在第七种实现方式中,处理器 1003 还用于当检测到输入设备输入触发指令时 1001 ,提供用于指示旋转移动终端的提示信息。 [0155] 在第八种实现方式中,处理器 1003 还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,处理器 1003 用于提供指示旋转移动终端的提示信息的方式如下: 根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0156] 需要说明的是,对于本发明实施例图11提供的移动终端,在移动终端中实现控制全景照片显示的过程如描述不够详细,可以参考相关文献 方法实施例的描述,此处不再赘述。 [0157] 本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0158]本领域的技术人员应该理解,本公开的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本公开可以采用纯硬件实施例、纯软件实施例或结合软件和硬件的实施例的形式。 此外,本公开可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0159] 参考根据本公开的实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述本公开。 应当理解,可以使用计算机程序指令来实现流程图和/或框图中的每个过程和/或每个框以及流程图和/或框图中的过程和/或框的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器生成机器,使得任何计算机或处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0160] 这些计算机程序指令也可以存储在计算机可读存储器中,该计算机可读存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,使得存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程中和/或在框图中的一个或多个块中实现特定功能。 [0161] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程数据处理设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供了用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0162] 尽管已经描述了本公开的一些优选实施例,但是本领域的技术人员在了解基本发明构思后可以对这些实施例进行更改和修改。 因此,所附权利要求旨在被解释为涵盖优选实施例以及落入本公开范围内的所有变化和修改。 [0163] 显然,本领域的技术人员可以对本发明实施例进行各种更改和变型而不脱离本发明实施例的范围。 本公开旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CA2966400A1(String), 1047222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CA2966400C(String), 1047223(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN104471519A(String), 1047224(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN104471519B(String), 1047225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN110650241A(String), 1047226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), CN110650241B(String), 1047227(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.808 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US10222877B2(String), 1047228(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US10649546B2(String), 1047229(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US11126275B2(String), 1047230(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20150363915A1(String), 1047231(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20170212609A1(String), 1047232(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20190171300A1(String), 1047233(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US20200241657A1(String), 1047234(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), US9621802B2(String), 1047235(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.822 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270668(Integer), WO2016004554A1(String), 1047236(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9621802B2(String), US9621802B2(String), 1491840000(Integer), 270668(Integer), 184986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.829 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.830 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185013(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185013(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.842 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.843 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185013(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185013(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.857 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.858 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.858 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.868 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.872 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.872 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.879 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8705554B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.883 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.883 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for reducing power consumption of WAPI mobile terminal and WAPI mobile terminal(String), WAPI移动终端降低功耗的方法及WAPI移动终端(String), US8705554B2(String), A method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal and a WAPI mobile terminal are provided. Said method includes: caching received WAPI service data into a dynamic cache module, and in a process of caching WAPI service data, when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data. Said WAPI mobile terminal includes: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively.(String), 提供了一种降低无线局域网认证和隐私基础设施(WAPI)移动终端的功耗的方法和WAPI移动终端。 所述方法包括:将接收到的WAPI业务数据缓存到动态缓存模块中,在缓存WAPI业务数据的过程中,当缓存的WAPI业务数据的数据量累积到所述WAPI移动终端设置的数据量阈值时,处理器模块 所述WAPI移动终端处理缓存的WAPI服务数据。 所述WAPI移动终端包括:WAPI通信模块和处理器模块相互连接,存储模块与所述处理器模块连接,动态缓存模块分别与所述WAPI通信模块和处理器模块连接。(String), US13/260080(String), 1271347200(Integer), US8705554B2(String), 1398096000(Integer), 1398096000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 9(Integer), CN100407696C | CN101588602A | CN1578516A | US20040267983A1 | US20050138238A1 | US20070238437A1 | US20120106415A1 | US6219728B1 | US6292492B1(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185014(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\eac4fc1d624049fdbb6321b53fa10553.png(String), 185014(Integer), eac4fc1d624049fdbb6321b53fa10553.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.904 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for reducing power consumption of WAPI mobile terminal and WAPI mobile terminal(String), WAPI移动终端降低功耗的方法及WAPI移动终端(String), US8705554B2(String), A method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal and a WAPI mobile terminal are provided. Said method includes: caching received WAPI service data into a dynamic cache module, and in a process of caching WAPI service data, when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data. Said WAPI mobile terminal includes: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively.(String), 提供了一种降低无线局域网认证和隐私基础设施(WAPI)移动终端的功耗的方法和WAPI移动终端。 所述方法包括:将接收到的WAPI业务数据缓存到动态缓存模块中,在缓存WAPI业务数据的过程中,当缓存的WAPI业务数据的数据量累积到所述WAPI移动终端设置的数据量阈值时,处理器模块 所述WAPI移动终端处理缓存的WAPI服务数据。 所述WAPI移动终端包括:WAPI通信模块和处理器模块相互连接,存储模块与所述处理器模块连接,动态缓存模块分别与所述WAPI通信模块和处理器模块连接。(String), US13/260080(String), 1271347200(Integer), US8705554B2(String), 1398096000(Integer), 1398096000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 9(Integer), CN100407696C | CN101588602A | CN1578516A | US20040267983A1 | US20050138238A1 | US20070238437A1 | US20120106415A1 | US6219728B1 | US6292492B1(String), \20230420\eac4fc1d624049fdbb6321b53fa10553.png(String), 6(Integer), 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.917 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.918 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185014(Integer), 1. A Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal of which power consumption is reduced, comprising: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively; whereinsaid dynamic cache module is configured to: receive and cache WAPI service data sent by said WAPI communication module; and after data quantity of cached WAPI service data accumulates to a data quantity threshold set by said processor module, send a triggering message to said processor module to notify said processor module to carry out processing, and said processor module is configured to: set the data quantity threshold of cache storage; before data quantity of cached WAPI service data accumulates to the data quantity threshold, not monitor and not process the WAPI service data; after receiving the triggering message of said dynamic cache module, process the WAPI service data cached by said dynamic cache module; set the data quantity threshold of the cache storage according to a real-time requirement of the WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is.(String), 1.一种降低功耗的无线局域网认证和隐私基础设施(WAPI)移动终端,包括:相互连接的WAPI通信模块和处理器模块,以及与所述处理器模块连接的存储模块,以及分别与所述WAPI通信模块和处理器模块连接的动态缓存模块;其中所述动态缓存模块,用于接收并缓存所述WAPI通信模块发送的WAPI服务数据;在缓存的WAPI业务数据的数据量达到所述处理器模块设置的数据量阈值后,向所述处理器模块发送触发消息,通知所述处理器模块进行处理,所述处理器模块用于:设置数据缓存存储数量阈值;在缓存的WAPI业务数据的数据量达到数据量阈值之前,不对WAPI业务数据进行监控和处理;接收到所述动态缓存模块的触发消息后,对所述动态缓存模块缓存的WAPI服务数据进行处理;根据WAPI服务的实时性要求设置缓存存储的数据量阈值,WAPI服务的实时性要求越高,设置的数据量阈值越低。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185014(Integer), 2. The WAPI mobile terminal as claimed in claim 1, whereinsaid processor module is configured to: keep in a sleeping state or process a task of which a priority is higher than that of said WAPI service in a process of caching WAPI data.(String), 2.如权利要求1所述的WAPI移动终端,其中所述处理器模块用于在缓存WAPI数据的过程中保持休眠状态或处理优先级高于所述WAPI服务的任务。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185014(Integer), 3. The WAPI mobile terminal as claimed in claim 2, whereinsaid processor module is further configured to: move the cached WAPI service data to said storage module after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, and enter into the sleeping state over again or continue to process the task of which the priority is higher than that of said WAPI service.(String), 3.如权利要求2所述的WAPI移动终端,其中所述处理器模块,还用于在缓存的WAPI业务数据的数据量累积到所述数据量阈值后,将缓存的WAPI业务数据移至所述存储模块,重新进入休眠状态或继续处理任务。其优先级高于上述WAPI服务。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.919 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185014(Integer), 4. The WAPI mobile terminal as claimed in claim 1, whereinsaid dynamic cache module is a Field Programmable Gate Array.(String), 4.如权利要求1所述的WAPI移动终端,其中所述动态缓存模块为现场可编程门阵列。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185014(Integer), 5. A method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal, comprising:caching received WAPI service data into a dynamic cache module, and when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data, and in a process of caching WAPI data, before data quantity of cached WAPI service data accumulates to the data quantity threshold, said processor module not monitoring and processing the WAPI service data, and said processor module being in a sleeping state or processing a task of which a priority is higher than that of said WAPI service, wherein said data quantity threshold is set by the WAPI mobile terminal according to a real-time requirement of a WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is.(String), 5.一种降低无线局域网认证和隐私基础设施(WAPI)移动终端功耗的方法,包括:将接收到的WAPI业务数据缓存到动态缓存模块中,当缓存的WAPI业务数据的数据量累积到WAPI移动终端设置的数据量阈值时,WAPI移动终端的处理器模块处理缓存的WAPI业务数据,并在缓存WAPI数据的过程,在缓存的WAPI业务数据的数据量达到数据量阈值之前,所述处理器模块不对WAPI业务数据进行监控和处理,所述处理器模块处于休眠状态或处理任务优先级高于所述WAPI服务,其中,所述数据量阈值由WAPI移动终端根据WAPI服务的实时性要求设置,WAPI服务的实时性要求越高,则越低设置的数据量阈值是。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.920 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185014(Integer), 6. The method as claimed in claim 5, said method further comprising:after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, said processor module moving the cached WAPI service data to a storage module of said WAPI mobile terminal, and entering into the sleeping state over again or continuing to process the task of which the priority is higher than that of said WAPI service.(String), 6.如权利要求5所述的方法,所述方法还包括:当缓存的WAPI业务数据的数据量累积到所述数据量阈值后,所述处理器模块将缓存的WAPI业务数据移至所述WAPI移动终端的存储模块,重新进入休眠状态或继续处理任务其中优先级高于上述WAPI服务。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185014(Integer), TECHNICAL FIELD [0001]The present invention relates to the communication terminal field, and particularly, to a method for reducing power consumption of a mobile terminal and a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal. BACKGROUND OF THE RELATED ART [0002]After the Time Division-Synchronous Code Division Multiple Access (TD-SDCMA) technology of the 3rd Generation (3G) standards is commercialized, the China wireless network standard WAPI also emerges to the forefront along with the wireless city upsurge rising from various cities in China, and the mobile terminal supporting the WAPI function (namely the WAPI mobile terminal) becomes more and more popular. [0003]In the mobile communication system, the continuous working time length of the mobile terminal is an important index reflecting the quality and performance of products. The mobile terminal downloading data through the WAPI technique during a long time will run out of the power of the battery quickly, and for the purpose of extending the continuous working time of the mobile terminal, it is necessary to reduce the power consumption of the mobile terminal. [0004]As shown in FIG. 1, in the prior art, the WAPI mobile terminal comprises a processor module 101, a user interface module 102, a WAPI communication module 103 and a storage module 104. When the WAPI mobile terminal downloads the large flow and long time data, the processor module 101 of the mobile terminal is required to monitor the data sent by the WAPI communication module 103 all the time, and stores the data to the storage module 104 in real-time, and carries out related processing on the received data, and the above large quantity of data processing operations of the processor module 101 makes the working current of the mobile terminal keep in a higher constant value all the time, which causes the mobile terminal to severely consume the power. SUMMARY OF THE INVENTION [0005]The technical problem to be solved in the present invention is to provide a method for reducing power consumption of a WAPI mobile terminal and a WAPI mobile terminal, which saves the power consumption of the mobile terminal and extends the working time. [0006]In order to solve the above problem, the present invention provides a WAPI mobile terminal for reducing power consumption, comprising: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively; [0007]said dynamic cache module being configured to: receive and cache WAPI service data sent by said WAPI communication module; and after data quantity of cached WAPI service data accumulates to a data quantity threshold set by said processor module, send a triggering message to said processor module to notify said processor module to carry out processing. [0008]In the above WAPI mobile terminal, the following characteristics are further included: [0009]said processor module is configured to: set the data quantity threshold of cache storage; in a process of caching WAPI service data, not monitor and process the WAPI service data; and after receiving the triggering message of said dynamic cache module, process the WAPI service data cached by said dynamic cache module. [0010]In the above WAPI mobile terminal, the following characteristics are further included: [0011]said processor module is configured to: keep in a sleeping state or process a task of which a processing priority is higher than the processing priority of said WAPI service in a process of caching WAPI data. [0012]In the above WAPI mobile terminal, the following characteristics are further included: [0013]said processor module is configured to: set the data quantity threshold of the cache storage according to a real-time requirement of the WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is. [0014]In the above WAPI mobile terminal, the following characteristics are further included: [0015]said processor module is further configured to: move the cached WAPI service data to said storage module after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, and enter into the sleeping state over again or continue to process a task of which the processing priority is higher than the processing priority of said WAPI service. [0016]In the above WAPI mobile terminal, the following characteristics are further included: [0017]said dynamic cache module is a Field Programmable Gate Array. [0018]In order to solve the above problem, the present invention also provides a method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal, comprising: [0019]caching received WAPI service data into a dynamic cache module, and when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data. [0020]The above method further comprises: [0021]in a process of caching WAPI data, said processor module not monitoring and processing the WAPI service data, and said processor module being in a sleeping state or processing a task of which a processing priority is higher than the processing priority of said WAPI service. [0022]In the above method, the following characteristics are further included: [0023]said data quantity threshold is set by the WAPI mobile terminal according to a real-time requirement of a WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is. [0024]The above method further comprises: [0025]after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, said processor module moving the cached WAPI service data to a storage module of said WAPI mobile terminal, and entering into the sleeping state over again or continuing to process a task of which the processing priority is higher than the processing priority of said WAPI service. [0026]In the method of the present invention, the WAPI mobile terminal adds a dynamic cache module, and when the mobile terminal carries out WAPI data downloading operations of lower real-time requirement and large data quantity, in the time consuming process of caching the data to the dynamic cache module, the processor of the mobile terminal doesn't need to monitor and process the data in the dynamic cache module, and further uniformly processes the data until the data accumulated in the dynamic cache module reaches to the quantity set by system, and thus the whole power consumption of the mobile terminal can be effectively reduced, and the working quantity of the processor is reduced, and further the power of the mobile terminal is saved, and the continuous using time of the mobile terminal is extended. BRIEF DESCRIPTION OF DRAWINGS [0027]FIG. 1 is a function structure diagram of the WAPI mobile terminal in the prior art; [0028]FIG. 2 is a function structure diagram of the WAPI mobile terminal of which the power consumption can be reduced according to the example; [0029]FIG. 3 is a flow chart of the method for reducing the power consumption of the WAPI mobile terminal according to the example; [0030]FIG. 4 is a flow chart of the method for reducing the power consumption of the WAPI mobile terminal according to the specific example. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0031]As shown in FIG. 2, comparing with the WAPI mobile terminal shown in FIG. 1, the WAPI mobile terminal of which the power consumption is reduced adds a dynamic cache module 105 respectively connected with the processor module 101 and the WAPI communication module 103; [0032]the user interface module 102 is used for data interaction between the man-machine interacting device and the processor module 101; wherein the man-machine interacting device of the mobile terminal is a terminal screen and a keyboard; [0033]the WAPI communication module 103 is used for carrying out data interaction with a wireless access node of a WAPI network by the WAPI protocol, and sending the WAPI data received from the wireless access node to the processor module 101 or the dynamic cache module 105; [0034]the storage module 104 is used for storing WAPI data under the control of the processor module 101; [0035]the processor module 101 is used for controlling the normal operation of the whole system, receiving the input of the external control signal, and processing the WAPI transmission data; is further used for setting the data quantity threshold of the cache storage according to the real-time requirement of the WAPI service, wherein the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is; is further used for in the process of caching the WAPI service data, enter into a sleeping state or process the task of which the priority is higher than that of said WAPI service, not monitoring or processing WAPI service data; and is further used for moving cached WAPI service data to said storage module after receiving the triggering message of said dynamic cache module, namely after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, and entering into the sleeping state over again or continuing to process the task of which the priority is higher than that of said WAPI service; [0036]the dynamic cache module 105 is used for receiving and caching the WAPI service data sent by said WAPI communication module; and is further used for sending a triggering message to said processor module 101 after the data quantity of the cached WAPI service data accumulates to the data quantity threshold set by said processor module; [0037]this dynamic cache module 105 can be a Field Programmable Gate Array (FPGA) chip with low power consumption, and the Random Access Memory (RAM) inside the FPGA chip stores the cached WAPI data. [0038]According to the real-time requirement of the WAPI service, the WAPI mobile terminal sets the data quantity threshold of the cache storage (namely the dynamic cache module), and the higher the real-time requirement of the WAPI service is, the lower the data quantity threshold of the cache storage is. For example, for the WAPI service which is required to be played in streaming media, the real-time requirement of the data transmission is very high, and the user can set a very low data quantity threshold of the cache storage, or directly set to 0, namely not caching this WAPI service data, and directly caching data by the small capacity RAM inside the processor. For the WAPI service which requires downloading file packets in a large quantity and not paying attention to the downloading content, the user can set a very high data quantity threshold of the cache storage. [0039]As shown in FIG. 3, the method for reducing power consumption of the WAPI mobile terminal comprises: [0040]step 310, the mobile terminal and the wireless access node of the WAPI network establish a communication connection between them to download data; [0041]step 302, the WAPI mobile terminal caches the received WAPI service data into the dynamic cache module; in the process of caching the WAPI data, the processor module of the WAPI mobile terminal does not process the cached WAPI data; [0042]in the process of caching the WAPI data, the processor judges that except the WAPI service, there is no other task of which the priority is higher than that of the WAPI service running, and the processor enters into the sleeping or low power consumption state; the processor judges that besides wireless communication of the WAPI, there is currently another task of which the priority is higher than that of the WAPI service running, and the processor processes this task of which the priority is higher than that of the WAPI service. [0043]Step 303, when the cached WAPI data accumulates to the data quantity threshold set by the WAPI mobile terminal, the processor of the WAPI mobile terminal processes the cached WAPI service data; [0044]when the cached WAPI data accumulates to the data quantity threshold set by the WAPI mobile terminal, and when the dynamic cache module sends the triggering message to the processor, and if the processor is in the sleeping state, then the processor quits the sleeping state, and moves the WAPI data in the dynamic cache module to the storage module; if the processor is processing another task of which the priority is higher than that of the WAPI service, then after finishing this task, the processor further moves the WAPI data inside the dynamic cache module to the storage module, or after receiving the triggering message, the processor suspends processing of this task, and moves the WAPI data in the dynamic cache module to the storage module. [0045]Step 304, the processor judges whether the WAP service data are all received, and if yes, the flow ends, otherwise the step 302 is carried out to continue to receive the WAPI service data. [0046]According to the above method, if the user downloads the WAPI service with the large flow quantity data and not high real-time requirement through the WAPI, the processor doesn't need to monitor and carry out the downloading operation of the data all the time, but caches the WAPI service data in the dynamic cache module, and when the stored data in the cache area reach to a certain value, the processor further moves the data to the storage space, and in the process of caching the WAPI service data, the processor does not monitor and process cached data, and thus in the time consuming process of caching the WAPI data, the processor doesn't need to consume the processing capability on the WAPI service, thereby saving the power; especially for the case of the larger downloaded WAPI service data quantity and consuming longer downloading time, the effect is obvious. [0047]It will further describe the specific example of the present invention in detail in combination with the figures below. [0048]As shown in FIG. 4, combining with FIG. 2, the dynamic cache module 105 of the mobile terminal is a FPGA chip, and the method of the WAPI mobile terminal processing WAPI service data comprises: [0049]step 401, according to their own application requirements, the user sets the data capacity of the cache storage area in the FPGA according to the real-time requirement of the WAPI service through the Man-Machine Interacting (MMI) devices, the set value is input into the register of the processor module 101 through the user interface module 102 of the mobile terminal; [0050]for example, when the real-time requirement of the WAPI service is very high, the data capacity of the FPGA can be set to 0, and when the real-time requirement of the WAPI service is low, for the purpose of saving power of the mobile terminal to the maximum, the user can set the data capacity of the FPGA to the maximum capacity of the cache storage. [0051]Step 402, according to the set value in the register of the processor module 101, the FGPA sets the capacity of the cache storage area of the FPGA; [0052]step 403, the WAPI communication module 103 and the wireless access node of the WAPI network establish the communication connection between them, and the user downloads data by the mobile terminal; [0053]step 404, the processor module 101 judges whether there is another task of which the priority is higher than that of the WAPI service running besides the WAPI communication module 103 being carrying out the wireless data transmission, and if yes, step 406 is carried out, otherwise step 405 is carried out; [0054]step 405, the processor module 101 enters into the sleeping or low power consumption mode, and waits for the execution of the higher priority service and the wake-up of the external interruption; [0055]step 406, the WAPI communication module 103 of the mobile terminal caches the received download data into the RAM of the dynamic cache module 105; [0056]step 407, when the data capacity stored in the RAM of the FPGA reaches to the capacity threshold set by the user, an interruption is generated to be input into the processor module 101; [0057]step 408, if the processor module 101 is in the sleeping or low power consumption mode, the processor module 101 will quit the sleeping or low power consumption mode, and move the cached data in the FPGA to the storage module 104; [0058]step 409, the processor module 101 judges whether the data transmission between the WAPI communication module 103 and the wireless access node of the WAPI network ends, and if yes, step 410 is carried out, otherwise step 404 is carried out; [0059]step 410, the mobile terminal ends this data downloading service. [0060]In the above implementation way, due to the setup of the dynamic cache module between the processing module and the WAPI communication module, the processor module doesn't need to process the WAPI service data sent by the WAPI communication module in real-time. The above method also sets the data quantity threshold, and before the WAPI service data cached by the dynamic cache module reaches to the data quantity threshold, the processor module is able to not process the WAPI service data cached in the dynamic cache module, thereby saving the power of the terminal and reducing the power consumption of the terminal. But the present invention is not limited to the above one way, and in other examples, the processor doesn't need to wait for the WAPI service data cached in the dynamic cache module reaching to the data quantity threshold in order to process data, and before reaching to the data quantity threshold, the processor can also carry out one or more times, regular or irregular discontinuous processing on the cached data as long as the processor doesn't need to process cached data in real-time, and the present invention does not limit the specific implementation method. [0061]Certainly, the present invention can also have other various examples, and without departing from the spirit or essence of the present invention, the person skilled in the art can make various corresponding modifications and transformations according to the present invention. And all the modifications and transformations shall all fall into the protection scope of the appended claims of the present invention. INDUSTRIAL APPLICABILITY [0062]In the method of the present invention, the WAPI mobile terminal adds a dynamic cache module, and when the mobile terminal carries out WAPI data downloading operations of lower real-time requirement and large data quantity, and in the time consuming process of caching the data into the dynamic cache module, the processor of the mobile terminal doesn't need to monitor and process the data in the dynamic cache module, and further uniformly processes the data until the data accumulated in the dynamic cache module reaches to the quantity set by system, and thus the whole power consumption of the mobile terminal can be effectively reduced, and the working quantity of the processor is reduced, and further the power of the mobile terminal is saved, and the continuous using time of the mobile terminal is extended.(String), 技术领域 [0001] 本发明涉及通信终端领域,尤其涉及一种降低移动终端功耗的方法及WAPI移动终端。 相关技术背景 [0002] 第三代(3G)标准的时分-同步码分多址(TD-SDCMA)技术商用后,随着中国各城市掀起的无线城市热潮,中国无线网络标准WAPI也崭露头角 ,支持WAPI功能的移动终端(即WAPI移动终端)越来越普及。 [0003] 在移动通信系统中,移动终端的连续工作时长是反映产品质量和性能的重要指标。 移动终端长时间通过WAPI技术下载数据会很快耗尽电池的电量,为了延长移动终端的连续工作时间,有必要降低手机的功耗 终端。 [0004] 如图1所示,现有技术中,WAPI移动终端包括处理器模块 101 , 一个用户界面模块 102 ,一个WAPI通信模块 103 和一个存储模块 104 . 当WAPI移动终端下载大流量、长时间数据时,处理器模块 101 需要手机端监听WAPI通讯模块发送的数据 103 一直,并将数据存储到存储模块 104 实时,并对接收到的数据进行相关处理,以及处理器模块的上述大量数据处理操作 101 使得移动终端的工作电流始终保持在一个较高的恒定值,导致移动终端严重耗电。 发明内容 [0005] 本发明所要解决的技术问题是提供一种降低WAPI移动终端功耗的方法及WAPI移动终端,节省移动终端的功耗,延长工作时间。 [0006] 为了解决上述问题,本发明提供了一种降低功耗的WAPI移动终端,包括:WAPI通信模块和处理器模块,与所述处理器模块连接的存储模块,动态缓存 分别与所述WAPI通信模块和所述处理器模块连接的模块; [0007] 所述动态缓存模块,用于接收并缓存所述WAPI通信模块发送的WAPI服务数据; 当缓存的WAPI业务数据的数据量累积到所述处理器模块设置的数据量阈值后,向所述处理器模块发送触发消息,通知所述处理器模块进行处理。 [0008] 在上述WAPI移动终端中,还包括以下特点: [0009] 所述处理器模块,用于设置缓存存储的数据量阈值; 在缓存WAPI服务数据的过程中,不对WAPI服务数据进行监控和处理; 接收到所述动态缓存模块的触发消息后,对所述动态缓存模块缓存的WAPI服务数据进行处理。 [0010] 在上述WAPI移动终端中,还包括以下特点: [0011] 所述处理器模块,用于在缓存WAPI数据的过程中,保持休眠状态或处理处理优先级高于所述WAPI服务的处理优先级的任务。 [0012] 在上述WAPI移动终端中,还包括以下特点: [0013] 所述处理器模块用于根据WAPI服务的实时性要求设置缓存存储的数据量阈值,WAPI服务的实时性要求越高,设置的数据量阈值越低。 . [0014]在上述WAPI移动终端中,还包括以下特点: [0015] 所述处理器模块,还用于在缓存的WAPI业务数据的数据量累计到所述数据量阈值后,将缓存的WAPI业务数据移至所述存储模块,重新进入休眠状态或继续处理任务。 其处理优先级高于所述WAPI服务的处理优先级。 [0016] 在上述WAPI移动终端中,还包括以下特点: [0017] 所述动态缓存模块为现场可编程门阵列。 [0018] 为了解决上述问题,本发明还提供了一种降低无线局域网认证和隐私基础设施(WAPI)移动终端功耗的方法,包括: [0019] 将接收到的WAPI业务数据缓存到动态缓存模块中,当缓存的WAPI业务数据的数据量累积到WAPI移动终端设置的数据量阈值时,WAPI移动终端的处理器模块对缓存的WAPI业务数据进行处理。 [0020] 上述方法还包括: [0021] 在缓存WAPI数据的过程中,所述处理器模块不对WAPI服务数据进行监控和处理,并且所述处理器模块处于休眠状态或者正在处理优先级高于所述WAPI服务的处理优先级的任务。 [0022] 在上述方法中,还包括以下特征: [0023] 所述数据量阈值由WAPI移动终端根据WAPI业务的实时性要求设置,WAPI业务的实时性要求越高,设置的数据量阈值越低。 [0024] 上述方法还包括: [0025] 当缓存的WAPI业务数据的数据量累积到所述数据量阈值后,所述处理器模块将缓存的WAPI业务数据移至所述WAPI移动终端的存储模块,重新进入休眠状态或继续处理任务 其中处理优先级高于该WAPI服务的处理优先级。 [0026] 在本发明的方法中,WAPI移动终端增加了动态缓存模块,当移动终端进行实时性要求较低、数据量较大的WAPI数据下载操作时,在缓存数据的耗时过程中, 动态缓存模块,移动终端的处理器不需要监视和处理动态缓存模块中的数据,进一步统一处理数据,直到动态缓存模块中累积的数据达到系统设置的数量, 从而可以有效降低移动终端的整体功耗,减少处理器的工作量,进一步节省移动终端的电量,延长移动终端的连续使用时间。 附图说明 [0027] 图1为现有技术中WAPI移动终端的功能结构图; [0028] 图2为实施例的可降低功耗的WAPI移动终端的功能结构图。 [0029] 图3为本实施例的降低WAPI移动终端功耗的方法流程图; [0030] 图4是根据具体示例的降低WAPI移动终端功耗的方法的流程图。 本发明的优选实施例 [0031] 如图2所示,与图1所示的WAPI移动终端相比,本发明降低功耗的WAPI移动终端增加了动态缓存模块。 105 分别与处理器模块相连 101 和WAPI通信模块 103 ; [0032] 用户界面模块 102 用于人机交互装置与处理器模块之间的数据交互 101; 其中,所述移动终端的人机交互装置为终端屏幕和键盘; [0033] WAPI通讯模块 103 用于通过WAPI协议与WAPI网络的无线接入节点进行数据交互,将从无线接入节点接收到的WAPI数据发送给处理器模块 101 或动态缓存模块 105 ; [0034] 存储模块 104 用于在处理器模块的控制下存储WAPI数据 101 ; [0035] 处理器模块 101 用于控制整个系统的正常运行,接收外部控制信号的输入,处理WAPI传输数据; 还用于根据WAPI服务的实时性要求设置缓存存储的数据量阈值,WAPI服务的实时性要求越高,设置的数据量阈值越低。 进一步用于在缓存WAPI服务数据的过程中,进入休眠状态或处理优先级高于该WAPI服务的任务,而不是监听或处理WAPI服务数据; 进一步用于在接收到所述动态缓存模块的触发消息后,即缓存的WAPI业务数据的数据量累积到所述数据量阈值后,将缓存的WAPI业务数据移至所述存储模块,并进入休眠状态。 再次或继续处理优先级高于该WAPI服务的任务; [0036] 动态缓存模块 105 用于接收并缓存所述WAPI通信模块发送的WAPI服务数据; 进一步用于向所述处理器模块发送触发消息 101 缓存的WAPI业务数据的数据量累积到所述处理器模块设置的数据量阈值后; [0037] 这个动态缓存模块 105 可以是低功耗的现场可编程门阵列(FPGA)芯片,FPGA芯片内部的随机存取存储器(RAM)存储缓存的WAPI数据。 [0038] WAPI移动终端根据WAPI服务的实时性要求,设置缓存存储(即动态缓存模块)的数据量阈值,WAPI服务的实时性要求越高,则越低 缓存存储的数据量阈值是。 例如,对于需要在流媒体中播放的WAPI服务,数据传输的实时性要求很高,用户可以将缓存存储的数据量阈值设置的很低,或者直接设置为 0,即不缓存此WAPI服务数据,直接由处理器内部的小容量RAM缓存数据。 对于需要大量下载文件包且不关注下载内容的WAPI业务,用户可以设置很高的缓存存储数据量阈值。 [0039] 如图3所示,降低WAPI移动终端功耗的方法包括: [0040] 步 310 、移动终端与WAPI网络的无线接入节点之间建立通信连接,进行数据下载; [0041] 步 302 、WAPI移动终端将接收到的WAPI业务数据缓存到动态缓存模块中; 在缓存WAPI数据的过程中,WAPI移动终端的处理器模块不对缓存的WAPI数据进行处理。 [0042] 在缓存WAPI数据的过程中,处理器判断除WAPI服务外,没有其他任务的优先级高于正在运行的WAPI服务,处理器进入休眠或低功耗状态。 处理器判断当前除了WAPI无线通信外,还有一个优先级高于WAPI服务运行的任务,处理器处理该优先级高于WAPI服务的任务。 [0043] 步 303、当缓存的WAPI数据累积到WAPI移动终端设置的数据量阈值时,WAPI移动终端的处理器对缓存的WAPI业务数据进行处理; [0044] 当缓存的WAPI数据累积到WAPI移动终端设置的数据量阈值时,动态缓存模块向处理器发送触发消息,若处理器处于休眠状态,则处理器退出休眠状态, 将动态缓存模块中的WAPI数据移动到存储模块中; 如果处理器正在处理另一个优先级高于WAPI服务的任务,则在完成该任务后,处理器进一步将动态缓存模块内的WAPI数据移动到存储模块,或者在接收到触发消息后, 处理器暂停处理该任务,将动态缓存模块中的WAPI数据移动到存储模块中。 [0045] 步 304 ,处理器判断是否接收到所有WAP业务数据,如果是,则流程结束,否则执行该步骤 302 进行继续接收WAPI服务数据。 [0046] 根据上述方法,如果用户通过WAPI下载数据流量大、实时性要求不高的WAPI服务,则处理器不需要一直监听并执行数据的下载操作。 ,而是将WAPI服务数据缓存在动态缓存模块中,当缓存区中存储的数据达到一定值时,处理器进一步将数据移动到存储空间中,在缓存WAPI服务数据的过程中, 处理器不对缓存的数据进行监控和处理,因此在缓存WAPI数据的耗时过程中,处理器不需要消耗对WAPI服务的处理能力,从而节省了电能。 特别是对于下载的WAPI服务数据量较大,下载时间较长的情况,效果更为明显。 [0047] 下面结合附图对本发明的具体实施例作进一步详细说明。 [0048] 如图4所示,结合图2,动态缓存模块 105 移动终端的为FPGA芯片,WAPI移动终端处理WAPI业务数据的方法包括: [0049] 步 401 ,用户根据自己的应用需求,通过人机交互(MMI)设备,根据WAPI服务的实时要求,设置FPGA中缓存存储区的数据容量,将设置值输入到 处理器模块的寄存器 101 通过用户界面模块 102 移动终端; [0050] 例如,当WAPI服务的实时性要求很高时,可以将FPGA的数据容量设置为0,而当WAPI服务的实时性要求不高时,达到节省功耗的目的。 移动端设置为最大,用户可以将FPGA的数据容量设置为缓存存储的最大容量。 [0051] 步 402 , 根据处理器模块寄存器中的设定值 101 ,FGPA设置FPGA的缓存存储区的容量; [0052] 步 403 , WAPI通信模块 103 与WAPI网络的无线接入节点之间建立通信连接,用户通过移动终端下载数据; [0053] 步 404 , 处理器模块 101 判断除WAPI通信模块外是否还有优先级高于WAPI服务运行的任务 103 正在进行无线数据传输,如果是,步骤 406 执行,否则步骤 405 完成了; [0054] 步 405 , 处理器模块 101 进入休眠或低功耗模式,等待更高优先级服务的执行和外部中断的唤醒; [0055] 步 406 , WAPI通信模块 103移动终端将接收到的下载数据缓存到动态缓存模块的RAM中 105 ; [0056] 步 407 ,当FPGA的RAM中存储的数据容量达到用户设定的容量阈值时,产生一个中断输入到处理器模块 101 ; [0057] 步 408 , 如果处理器模块 101 处于睡眠或低功耗模式时,处理器模块 101 会退出休眠或低功耗模式,将FPGA中的缓存数据移动到存储模块中 104 ; [0058] 步 409 , 处理器模块 101 判断WAPI通讯模块之间是否有数据传输 103 WAPI网络的无线接入节点结束,如果是,步骤 410 执行,否则步骤 404 完成了; [0059] 步 410 ,移动终端结束本次数据下载业务。 [0060] 在上述实现方式中,由于在处理模块和WAPI通信模块之间设置了动态缓存模块,处理器模块不需要实时处理WAPI通信模块发送的WAPI服务数据。 上述方法还设置了数据量阈值,在动态缓存模块缓存的WAPI业务数据达到数据量阈值之前,处理器模块可以不对动态缓存模块缓存的WAPI业务数据进行处理,从而节省了时间。 终端的功率,降低终端的功耗。 但本发明不限于上述一种方式,在其他示例中,处理器不需要等待动态缓存模块中缓存的WAPI服务数据达到数据量阈值来处理数据,并且 在达到数据量阈值之前,只要处理器不需要对缓存数据进行实时处理,处理器还可以对缓存数据进行一次或多次、定期或不定期的不连续处理,本发明 不限定具体的实现方式。 [0061] 当然,本发明还可以有其他各种实施例,在不脱离本发明的精神或实质的情况下,本领域的技术人员可以根据本发明做出各种相应的修改和变换。 并且所有的修改和变换均落入本发明所附权利要求的保护范围之内。 工业实用性 [0062] 在本发明的方法中,WAPI移动终端增加了动态缓存模块,当移动终端进行实时性要求较低、数据量较大的WAPI数据下载操作时,在缓存数据的过程中比较耗时。 进入动态缓存模块,移动终端的处理器不需要对动态缓存模块中的数据进行监听和处理,进一步对数据进行统一处理,直到动态缓存模块中累积的数据达到系统设定的数量 ,从而可以有效降低移动终端的整体功耗,减少处理器的工作量,进一步节省移动终端的电量,延长移动终端的连续使用时间。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101588602A(String), CN101588602B(String), EP2434802A1(String), EP2434802A4(String), EP2434802B1(String), US20120106415A1(String), US8705554B2(String), WO2010133115A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101588602A(String), CN101588602B(String), EP2434802A1(String), EP2434802A4(String), EP2434802B1(String), US20120106415A1(String), US8705554B2(String), WO2010133115A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:58.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8705554B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101588602A(String), CN101588602B(String), EP2434802A1(String), EP2434802A4(String), EP2434802B1(String), US20120106415A1(String), US8705554B2(String), WO2010133115A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), CN101588602A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), CN101588602B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), EP2434802A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), EP2434802A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), EP2434802B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), US20120106415A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), US8705554B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270691(Integer), WO2010133115A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8705554B2(String), US8705554B2(String), 1398096000(Integer), 270691(Integer), 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.090 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.092 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.095 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185014(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185014(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.107 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.107 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185014(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185014(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.175 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8548504B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US8548504B2(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别宏小区中的毫微微小区。 当移动终端在广播信道部分中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息,并且将列表和关于相邻毫微微基站的信息发送给移动终端。(String), US13/013617(String), 1295884800(Integer), US8548504B2(String), 1380556800(Integer), 1380556800(Integer), 美国(String), 4(Integer), KR(String), 4(Integer), 25(Integer), KR100858282B1 | KR1020090110103A | KR1020100011271A | US20090021287A1 | US20090135758A1 | US20090168727A1 | US20090239511A1 | US20090252073A1 | US20090299788A1 | US20090310561A1 | US20100035622A1 | US20100190496A1 | US20100240397A1 | US20100260068A1 | US20100278141A1 | US20110110520A1 | US20110111754A1 | US7107055B2 | US8144725B2 | US8180368B2 | US8345633B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185015(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7c62b3e0b56e44239c2b0e825fbf2819.png(String), 185015(Integer), 7c62b3e0b56e44239c2b0e825fbf2819.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US8548504B2(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别宏小区中的毫微微小区。 当移动终端在广播信道部分中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息,并且将列表和关于相邻毫微微基站的信息发送给移动终端。(String), US13/013617(String), 1295884800(Integer), US8548504B2(String), 1380556800(Integer), 1380556800(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 4(Integer), 25(Integer), KR100858282B1 | KR1020090110103A | KR1020100011271A | US20090021287A1 | US20090135758A1 | US20090168727A1 | US20090239511A1 | US20090252073A1 | US20090299788A1 | US20090310561A1 | US20100035622A1 | US20100190496A1 | US20100240397A1 | US20100260068A1 | US20100278141A1 | US20110110520A1 | US20110111754A1 | US7107055B2 | US8144725B2 | US8180368B2 | US8345633B2(String), \20230420\7c62b3e0b56e44239c2b0e825fbf2819.png(String), 14(Integer), 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.228 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 1. A communication method of a macro base station, the method comprising:reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell;receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section;generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal; andtransmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal.(String), 1.一种宏基站的通信方法,该方法包括:向宏基站的宏小区中的至少一个毫微微基站上报宏小区中用于标识毫微微小区的广播信道段信息;当移动终端在广播信道部分识别出可访问的毫微微基站时,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求;基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息;和将相邻毫微微基站的列表和相邻毫微微基站的信息发送给移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 2. The method of claim 1, further comprising transmitting connection information to enable the mobile terminal to access a femto base station selected by the mobile terminal.(String), 2.如权利要求1所述的方法,还包括发送连接信息以使移动终端能够接入由移动终端选择的毫微微基站。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 3. The method of claim 1, wherein the broadcast channel section is set in a downlink broadcast channel of the macrocell at a preset cycle.(String), 3.如权利要求1所述的方法,其中广播信道段以预设周期设置在宏小区的下行广播信道中。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 4. The method of claim 1, wherein the information about the neighbor femto base stations comprises information about a shop in which each of the femto base stations is located or information about a discount policy of a connection service offered by each of the femto base stations.(String), 4.如权利要求1所述的方法,其中所述相邻毫微微基站的信息包括各毫微微基站所在店铺的信息或各毫微微基站提供的连接服务的优惠政策信息。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 5. A communication method of a mobile terminal, the method comprising:detecting a broadcast channel section used to identify a femtocell in a macrocell;identifying a femto base station accessible to the mobile terminal based on a measurement of an intensity of a signal of the broadcast channel section;transmitting, to a macro base station, position information of the mobile terminal and a request for information about the accessible femto base station;receiving a list of neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations from the macro base station; andselecting a femto base station based on the list and the information about the neighbor femto base stations.(String), 5.一种移动终端的通信方法、方法包括:检测宏小区中用于识别毫微微小区的广播信道段;基于对广播信道部分的信号强度的测量来识别移动终端可访问的毫微微基站;向宏基站发送移动终端的位置信息和可访问的毫微微基站的信息请求;从宏基站接收移动终端的相邻毫微微基站列表和相邻毫微微基站的信息;和基于列表和关于相邻毫微微基站的信息选择毫微微基站。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 6. The method of claim 5, wherein the detecting of the broadcast channel section is performed when a femtocell exploration mode of the mobile terminal is set to on.(String), 6.如权利要求5所述的方法,其中广播信道段的检测在移动终端的毫微微基站探索模式设置为开启时进行。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 7. The method of claim 5, wherein the identifying of the accessible femto base station is performed by comparing a preset threshold value with the measured intensity of the signal of the broadcast channel section.(String), 7.如权利要求5所述的方法,其中可接入的毫微微基站的识别是通过将预设的阈值与广播信道段的信号的测量强度进行比较来执行的。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 8. The method of claim 5, wherein the selected femto base station is selected based on preferences of a user of the mobile terminal.(String), 8.如权利要求5所述的方法,其中所选择的毫微微基站是基于移动终端的用户的偏好来选择的。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 9. The method of claim 5, further comprising receiving connection information to enable access to the selected femto base station from the macro base station.(String), 9.如权利要求5所述的方法,还包括接收连接信息以使得能够从宏基站接入所选择的毫微微基站。(String), 1(Integer), 8(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 10. The method of claim 5, wherein the broadcast channel section is set in a downlink broadcast channel of the macrocell at a preset cycle.(String), 10.如权利要求5所述的方法,其中广播信道段以预设周期设置在宏小区的下行广播信道中。(String), 1(Integer), 9(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 11. The method of claim 5, wherein the information about the neighbor femto base stations comprises information about a shop in which the femto base stations are located, respectively, or comprises information about a discount policy of a connection service offered by each respective femto base station.(String), 11.如权利要求5所述的方法,其中所述相邻毫微微基站的信息包括各毫微微基站所在店铺的信息,或者包括各毫微微基站所提供的连接服务的优惠政策信息。(String), 1(Integer), 10(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 12. A communication method of a femto base station, the method comprising: receiving, by the femto base station from a macro base station, a report about a broadcast channel section used to identify a femtocell in a macrocell of the macro base station; setting, by the femto base station, a signal in the broadcast channel section to report existence of a femtocell of the femto base station within the macrocell; and connecting, by the femto base station, to a mobile terminal that detects the broadcast channel section to identify the femtocell of the femto base station within the macrocell.(String), 12.一种毫微微基站的通信方法,该方法包括:毫微微基站从宏基站接收宏基站宏小区中用于标识毫微微小区的广播信道段的报告;毫微微基站在广播信道段设置信号,报告宏小区内存在毫微微基站的毫微微小区;毫微微基站连接到检测广播信道段的移动终端,以在宏小区内识别毫微微基站的毫微微小区。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 13. The method of claim 12, further comprising setting, by the femto base station, the signal in the broadcast channel section to report existence of the femtocell of the femto base station within the macrocell upon receipt of the report about the broadcast channel section.(String), 13.如权利要求12所述的方法,还包括毫微微基站设置广播信道段中的信号,在收到广播信道段的报告后,报告宏小区内存在毫微微基站的毫微微小区。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185015(Integer), 14. A non-transitory computer-readable storage medium having stored therein program instructions to cause a processor to execute a communication method of a macro base station, the method comprising:reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell;receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section;generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal; andtransmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal.(String), 14.一种非暂时性计算机可读存储介质有存储在其中的程序指令使处理器执行宏基站的通信方法,该方法包括:向宏基站的宏小区中的至少一个毫微微基站上报宏小区中用于标识毫微微小区的广播信道段信息;当移动终端在广播信道部分识别出可访问的毫微微基站时,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求;基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息;和将相邻毫微微基站的列表和相邻毫微微基站的信息发送给移动终端。(String), 0(Integer), 13(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185015(Integer), CROSS-REFERENCE TO RELATED APPLICATION(S) [0001]This application claims the benefit under 35 U.S.C. §119(a) of Korean Patent Application No. 10-2010-0055844, filed on Jun. 14, 2010, in the Korean Intellectual Property Office, the entire disclosure of which is incorporated herein by reference for all purposes. BACKGROUND [0002]1. Field [0003]The following description relates to a method of advertising to a mobile terminal connected to a femto base station, and a communication method of a mobile terminal, a femto base station, and a macro base station. [0004]2. Description of Related Art [0005]Femtocells may be classified into various types, for example, a personal femtocell that may be used to provide an ultrahigh speed transmission service within a predetermined area, a commercial femtocell to provide an advertisement service for sales promotion of a shop, and an authorized femtocell to provide a location service. Most femtocell applications focus on a user's convenience but do not sufficiently consider benefits to various installers and administrators. [0006]In a personal femtocell, a femtocell installer and an administrator may be substantially the same as a service beneficiary, and therefore, various administrative rights need not be distinguished. However, in a commercial femtocell, there is a need to distinguish the rights of a femtocell installer with those of a femtocell administrator in order to protect commercial rights. SUMMARY [0007]In one general aspect, there is provided a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell, receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section, generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal. [0008]The method may further comprise transmitting connection information to enable the mobile terminal to access a femto base station selected by the mobile terminal. [0009]The broadcast channel section may be set in a downlink broadcast channel of the macrocell at a preset cycle. [0010]The information about the neighbor femto base stations may comprise information about a shop in which each of the femto base stations is located or information about a discount policy of a connection service offered by each of the femto base stations. [0011]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a voice call transmitting signal transmitted from the mobile terminal, postponing transmission of the voice call transmitting signal, in response to the identification of the voice call transmitting signal, and offering a unique voice advertisement service of the femto base station, in response to the identification of the voice call transmitting signal. [0012]The method may further comprise identifying a ringback tone signal transmitted from a receiving side, and stopping the unique voice advertisement service of the femto base station in response to the identification of the ringback tone signal. [0013]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a data communication connection signal transmitted from the mobile terminal, postponing transmission of the data communication connection signal, in response to the identification of the data communication connection signal, and offering a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal. [0014]The method may further comprise identifying a data reception signal about a uniform resource locator (URL) address that the mobile terminal desires to access, and stopping the unique advertisement service of the femto base station, in response to the identification of the data reception signal. [0015]In another aspect, there is provided a communication method of a mobile terminal, the method comprising detecting a broadcast channel section used to identify a femtocell in a macrocell, identifying a femto base station accessible to the mobile terminal based on a measurement of an intensity of a signal of the broadcast channel section, transmitting, to a macro base station, position information of the mobile terminal and a request for information about the accessible femto base station, receiving a list of neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations from the macro base station, and selecting a femto base station based on the list and the information about the neighbor femto base stations. [0016]The detecting of the broadcast channel section is performed when a femtocell exploration mode of the mobile terminal is set to on. [0017]The indentifying of the accessible femto base station may perform by comparing a preset threshold value with the measured intensity of the signal of the broadcast channel section. [0018]The selected femto base station may be selected based on preferences of a user of the mobile terminal. [0019]The method may further comprise receiving connection information to enable access to the selected femto base station from the macro base station. [0020]The broadcast channel section may be set in a downlink broadcast channel of the macrocell at a preset cycle. [0021]The information about the neighbor femto base stations may comprise information about a shop in which the femto base stations are located, respectively, or comprises information about a discount policy of a connection service offered by each respective femto base station. [0022]In another aspect, there is provided a communication method of a femto base station, the method comprising receiving, from a macro base station, a report about a broadcast channel section used to identify a femtocell in a macrocell of the macro base station, and setting a signal in the broadcast channel section to report existence of a femtocell of the femto base station within the macrocell. [0023]In another aspect, there is provided a computer-readable storage medium having stored therein program instructions to cause a processor to execute a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell, receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section, generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal. [0024]Other features and aspects may apparent from the following description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0025]FIG. 1 is a diagram illustrating an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0026]FIG. 2 is a diagram illustrating an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0027]FIG. 3 is a flowchart illustrating an example of a communication method of a macro base station. [0028]FIG. 4 is a flowchart illustrating an example of a communication method of a mobile terminal. [0029]FIG. 5 is a flowchart illustrating an example of a method of offering an advertisement to a mobile terminal connected to a femto base station. [0030]Throughout the drawings and the description, unless otherwise described, the same drawing reference numerals should be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience. DESCRIPTION [0031]The following description is provided to assist the reader in gaining a comprehensive understanding of the methods, apparatuses, and/or systems described herein. Accordingly, various changes, modifications, and equivalents of the methods, apparatuses, and/or systems described herein may be suggested to those of ordinary skill in the art. Also, description of well-known functions and constructions may be omitted for increased clarity and conciseness. [0032]As described herein, a macrocell refers to a coverage area of a macro base station, and a femtocell refers to a coverage area of a femto base station. [0033]FIG. 1 illustrates an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0034]Referring to FIG. 1, the network in which the mobile terminal identifies and connects to the neighbor femtocell includes a macro base station 101, two femto base stations 103, and a mobile terminal 105. It should be appreciated that the number of macro base stations, femto base stations, and mobile terminals are not limited to the example shown in FIG. 1. For example, the network may include one or more macro base stations, one or more femto base stations, and one or more mobile terminals. [0035]The macro base station coverage area includes a macrocell. The macro base station 101 sets up a broadcast channel section 109 within a downlink broadcast channel to identify a femtocell. The macro base station 101 reports the broadcast channel section 109 to at least one femto base station 103 in the macrocell. [0036]For example, the macro base station 101 may be linked with the femto base station 103 positioned in the macrocell, and maintain and renew a database including connection information. The connection information may include, for example, information about linked femto base stations 103, information about shops in which the linked femto base stations 103 are located, and the like. [0037]For example, the macro base station 101 may renew the database at a time when a femto base station 103 is added to the macrocell, at a preset time, or at any other desired time. [0038]The femto base stations 103 may offer various services, for example, real-time advertisements and event announcements of shops to the mobile terminal 105 as the user of the mobile terminal is within the coverage area of the femto base stations or passing by the shops in which the femto base stations 103 are located. [0039]For example, the femto base stations 103 may be linked with the macro base station 101 to attract customers passing by the shops in which the femto base stations 103 are located. The femto base stations 103 may be synchronized and linked with the macro base station 101. [0040]The mobile terminal 105 may set itself in a femtocell exploration mode to automatically identify a femtocell. For example, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 in order to identify a femtocell in the macrocell and identify whether there is a neighbor femtocell. During the femtocell exploration mode, the mobile terminal 105 may detect one or more femtocells corresponding to one or more femto base stations 103, which are within the macrocell of the macro base station 101 and are available for the mobile terminal 105 to connect with. [0041]The mobile terminal 105 may select a femto base station 103 from among the one or more detected femto base stations 103 based on a user preference of the mobile terminal 105 and/or information about neighbor femto base stations 103 received from the macro base station 101. Accordingly, the mobile terminal 105 may be provided with a unique advertisement service of the femto base station 103 while located within a femtocell of the femto base station 103. [0042]For example, the unique advertisement service of the femto base station 103 may include products sold by a shop in which the femto base station 103 is located, an advertisement for the shop, an advertisement service for an event held by the shop, and the like. [0043]As an example, when the shop in which the femto base station 103 is located is an ice cream shop, an advertisement service for the shop may include an advertisement for a new flavor of ice cream that may be purchased in the shop, discount information about products “on sale”, discount coupons, and the like. [0044]As described herein, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 to identify a femtocell of a femto base station 103 located within the macrocell of the macro base station 101, and be provided with the a unique advertisement service of the femto base station 103. [0045]The broadcast channel section 109 used to identify the femtocell in the macrocell may be set at a preset cycle, for example, a cycle of a hundred milliseconds, two hundred milliseconds, five hundred milliseconds, or other desired amount of time. [0046]Hereinafter, a method including the macro base station 101, the femto base station 103, and the mobile terminal 105 in which the mobile terminal 105 identifies a neighbor femto base station 103 of the mobile terminal 105 and connect to the femto base station 103, is described. [0047]As indicated by reference numeral 110, the macro base station 101 reports information about the broadcast channel section 109 to the femtocell corresponding to at least one femto base station 103 in the macrocell. For example, the macro base station may report to one or more femto base stations 103. [0048]The femto base station 103 receiving a report about the broadcast channel section 109 from the macro base station 101 may set a signal in the broadcast channel section 109 in order to report the existence of the femtocell corresponding to the femto base station 103, as indicated by reference numeral 120. For example, the broadcast channel section 109 of the downlink broadcast channel may be set to a single bit or multiple bits. [0049]In 120, the femto base station 103 may set various types of signals in the broadcast channel section 109 to report the existence of the femtocell of the femto base station 103, for example, the femto base station 103 may set a particular bit of the broadcast channel section 109 to ‘1’ or set the broadcast channel section 109 to a dummy signal. [0050]When the femtocell exploration mode of the mobile terminal 105 is set to ON as indicated by reference numeral 130, the mobile terminal 105 may detect the broadcast channel section 109 to identify that the femtocell corresponding to the a femto base station 103 is within the macrocell corresponding to the macro base station 101. [0051]The mobile terminal 105 may identify a femto base station 103 accessible to the mobile terminal 105 from among the at least one femto base station 103 that is within the macrocell of the macro base station, based on a measurement result of an intensity of the signal of the broadcast channel section 109, in 140. [0052]For example, when the measurement result of the intensity of the signal in the broadcast channel section 109 is higher than a preset threshold value, the mobile terminal 105 may identify that there is at least one femto base station 103 neighboring the mobile terminal 105 and accessible to the mobile terminal 105. As another example, based on the intensity of the signal, the mobile terminal 105 may determine that a plurality of femto base stations are neighboring and available, for example, two femto base stations, three femto base stations, four femto base stations, or more femto base stations. The femto base station 103 may set a signal in the broadcast channel section 109 upon receiving the report about the broadcast channel section 109 from the macro base station 101. [0053]The mobile terminal 105 may transmit its position information to the macro base station 101, and may transmit a request to the macro base station 101 for information about the femto base station 103 which is accessible to the mobile terminal 105, in 150. [0054]For example, the macro base station 101 may generate a list of neighbor femto base stations 103 and information about the neighbor femto base stations 103 based on the position information of the mobile terminal 105 received from the mobile terminal 105, and may transmit the generated information to the mobile terminal 105, in 160. [0055]As an example, the information about the neighbor femto base stations 103 of the mobile terminal 105 may include information about a shop in which each of the respective femto base stations 103 is located or information about a discount policy of a connection service offered by each of the femto base stations 103. [0056]The mobile terminal 105 may select one femto base station 103 based on the list of the neighbor femto base stations 103 and the information about the neighbor femto base stations 103 received from the macro base station 101, in 170. [0057]In 170, the mobile terminal 105 may select the femto base station 103 in the list of the neighbor femto base stations 103 based on a user preference of the mobile terminal 105 and/or the information about the neighbor femto base stations 103 of the mobile terminal 105. [0058]An example of the list of the neighbor femto base stations 103 received from the macro base station 101 may include the following contents as shown in Table 1. [0059]TABLE 1Trans-Location ofFemto baseBusinessmissionBase stationstation IDcategoryPolicy for usespeedaACosmeticsfreeLowaBClothing10 cents/minHighaCEntertainmentfreeMediumaDFast food5 cent/minHigh(free whenreceivingadvertisements) [0060]In this example, the mobile terminal 105 receives information about four femto base stations A, B, C, and D neighboring the mobile terminal 105 from the macro base station 101. Accordingly, if a user of the mobile terminal 105 prefers a femto base station that provides a high transmittance speed and a free communication channel, the user of the mobile terminal 105 may select femto base station D to receive communication from. In other words, among the femto base stations B and D that provide a high transmittance speed and the femto base stations A, C, and D that provide a free communication channel, the mobile terminal 105 may automatically select or a user of the mobile terminal 105 may select the femto base station D which satisfies all user preferences. [0061]For example, the mobile terminal 105 may use the communication channel provided by the selected femto base station D. Further, the mobile terminal 105 may be provided with information about a shop in which the femto base station D is located or information about a discount policy of a connection service offered by the femto base station D from the femto base station D. [0062]In this example, the femto base station D corresponds to a femto base station of a fast food restaurant. Accordingly, the mobile terminal 105 may be provided with information about the fast food restaurant in which the femto base station D is located, information about a sales event offered by the fast food restaurant, coupons for discounts offered by the fast food restaurant, and an advertisement for the sales event. [0063]As another example, the mobile terminal 105 may select a femto base station 103 based on the interest of the user of the mobile terminal 105. For example, the mobile terminal 105 may select a femto base station 103 located in a shop of interest a shop offering a sales event, a shop providing a coupon of a product for a discount when receiving an advertisement service, and the like. [0064]As described above, the mobile terminal 105 may automatically select a femto base station 103 from the list by various methods. Depending on the femto base station 103 selected, the user of the mobile terminal 105 may be provided with an advertisement service from the femto base station 103. [0065]Further, the mobile terminal 105 itself may provide the list of the neighbor femto base stations 103 and information about their events to allow a user to select a femto base station 103. [0066]As another example, a femto base station 103 may be automatically selected by the macro base station 101. In yet other embodiments, the femto base station 103 may be automatically selected by the mobile terminal 105 based on predetermined settings or dynamically adjusted settings that may be dynamically set by a user. As yet another example, the femto base station 103 may be selected by a user of the mobile terminal 105. [0067]As another example, the macro base station 101 may store a user preference of the mobile terminal 105 and the information about the femto base stations 103 in advance, and selectively provide a femto base station 103 that satisfies the user preference based on stored information. [0068]For example, the macro base station 101 may include a database of information about the user preference of the mobile terminal 105 shown in the following Table 2. [0069]TABLE 2MobileTrans-InterestedterminalAgePolicy formissionbusinessIDgroupsusespeedcategoryOthersA20sFreeMediumCommunica-Selecting freetionof charge whenterminals,receivinggamesadvertisementsB30sFree/HighRestaurantsHigh trans-chargedmission speedC40sFreeMediumSports,Receivingbooksports-relatedstoresadvertisements [0070]The macro base station 101 may select the femto base stations that satisfy the user preferences of the mobile terminal 105 shown in Table 2 and provide them to the mobile terminal 105. [0071]After receiving the selection from the mobile terminal 105, the macro base station 101 may transmit connection information to the mobile terminal 105 to enable an access to the selected femto base station 103, in 180. [0072]The mobile terminal 105 may connect to the selected femto base station 103 using the connection information received from the macro base station 101, in 190. [0073]Accordingly, the mobile terminal 105 connected to the femto base station 103 may be provided with various communication services and advertisement services offered by the femto base station 103. [0074]For example, the advertisement services may include a unique voice advertisement service of the femto base station 103 and a unique display advertisement service of the femto base station 103. For example, the unique voice advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 inputs a telephone number and waits for a call to connect. [0075]As described herein, the unique advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 waits for data reception about a uniform resource locator (URL) address which the mobile terminal 105 desires to access. [0076]FIG. 2 illustrates an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0077]Referring to FIG. 2, the network for providing the advertisement to the mobile terminal includes a counterpart exchange station 201, a femto base station 203, a mobile terminal 205, and a receiving side mobile terminal 207. [0078]For example, a user in control of the mobile terminal 205 passing by a shop in which the femto base station 203 is located may attempt to call a friend by entering the phone number of a friend that corresponds to the receiving side mobile terminal 207, to try a call, in 210. [0079]In response to the call being placed by the user of the mobile terminal 205, the femto base station 203 identifies a voice call transmitting signal transmitted from the mobile terminal 205 based on the call being placed. Accordingly, the femto base station 203 may provide an advertisement to the mobile terminal 205 connected to the femto base station 203, and postpone transmission of the voice call transmitting signal in response to the identification of the voice call transmitting signal, in 220. [0080]For example, the femto base station 203 may include a voice call transmitting signal identification module that may identify the voice call transmitting signal transmitted from the mobile terminal 205. The femto base station 203 may offer a unique voice advertisement service of the femto base station 203 to the mobile terminal 205 in response to the identification of the voice call transmitting signal, in 230. [0081]The femto base station 203 forwards the postponed voice call transmitting signal to the counterpart exchange station 201, in 240. For example, the femto base station 203 may forward the postponed voice call transmitting signal after a predetermined amount of time elapses. [0082]For example, the femto base station 203 may identify a ringback tone signal transmitted from the receiving side mobile terminal 207, and accordingly, the femto base station 203 stops the unique voice advertisement service of the femto base station 203 in response to the identification of the ringback tone signal, in 250. [0083]After stopping the unique voice advertisement service of the femto base station 203, the femto base station 203 may forward the ringback tone signal to the mobile terminal 205 to connect a voice call, in 260. [0084]FIG. 3 illustrates an example of a communication method of a macro base station. [0085]Referring to FIG. 3, the macro base station reports information about a broadcast channel section to at least one femto base station in the macrocell, in 310. For example, the broadcast channel may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0086]The macro base station receives position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, in 320. For example, the position information and the request for information may be transmitted from the mobile terminal when the mobile terminal identifies an accessible femto base station. [0087]The information about the neighbor femto base stations of the mobile terminal may include information about a shop in which each of the femto base stations is located. As another example, the information may include a discount policy of a connection service offered by each of the femto base stations. [0088]The macro base station generates a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, in 330. [0089]The macro base station transmits the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal, in 340. [0090]In 350, the macro base station may transmit connection information to enable the mobile terminal access to a femto base station. [0091]The connection information to enable the mobile terminal access to the femto base station may be information about a femto base station selected by the mobile terminal from among the neighbor femto base stations of the mobile terminal in the list. [0092]FIG. 4 illustrates an example of a communication method of a mobile terminal [0093]Referring to FIG. 4, the mobile terminal may determine whether a femtocell exploration mode is set to ‘ON’, in 410. [0094]When the femtocell exploration mode is set to ‘ON,’ the mobile terminal detects a broadcast channel section to identify a femtocell, in 420. For example, the broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0095]As a result of the determination in 410, if the femtocell exploration mode is not set to ‘ON,’ or the mobile terminal does not have a femtocell exploration function, the mobile terminal may finish the process without performing subsequent operations. [0096]The mobile terminal identifies a femto base station accessible to the mobile terminal based on a measurement of an intensity of a signal of the broadcast channel section in order to identify the femtocell in the macrocell. For example, the mobile terminal may measure the intensity of the signal of the broadcast channel section to identify the femtocell and compare the measurement result with a preset threshold value, in 440. [0097]When the intensity of the signal of the broadcast channel section measured in 440 is higher than the preset threshold value, the mobile terminal may identify that the femto base station is accessible to the mobile terminal, in 450. [0098]The mobile terminal transmits, to a macro base station, its position information and a request for information about the accessible femto base station, in 460. The mobile terminal receives the requested information from the macro base station, in 470. For example, the information received from the macro base station may include a list of neighbor femto base stations of the mobile terminal and information about them. For example, the list and the information may be generated based on the position information of the mobile terminal. As an example, the information about the neighbor femto base stations may include information about a shop in which each of the femto base stations is located or include information about a discount policy of a connection service offered by each of the femto base stations. [0099]The mobile terminal may select a femto base station based on the list of the neighbor femto base stations and the information about them, in 480. For example, the mobile terminal may use a preference of a user of the mobile terminal and the information about the neighbor femto base stations in selecting a femto base station. [0100]FIG. 5 illustrates an example of a method of offering an advertisement to a mobile terminal connected to a femto base station. [0101]Referring to FIG. 5, when the mobile terminal inputs a data communication connection signal such as a URL address which the mobile terminal desires to access, the femto base station identifies the data communication connection signal transmitted from the mobile terminal, in 510. [0102]The femto base station postpones transmission of the data communication connection signal in response to the identification of the data communication connection signal, in 520. [0103]The femto base station offers a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal, in 530. And, after a lapse of a predetermined amount of time, For example, the femto base station may forward the postponed data communication connection signal to an internet server in operation. [0104]In 540, the femto base station identifies a data reception signal about the URL address which the mobile terminal desires to access. For example, the femto base station may include a functional module to identify a data reception signal such as a homepage or a URL address which the mobile terminal desires in order to identify the data reception signal. [0105]The femto base station may stop a unique advertisement service in response to the identification of the data reception signal about the URL address which the mobile terminal desires to access, in 550. The femto base station may forward the data reception signal about the URL address to the mobile terminal for connection. [0106]As described herein, the mobile terminal may include various modes such as a femtocell exploration mode. However, it should be appreciated that the mobile terminal may only have one mode in which the mobile terminal constantly searches for an available femtocell. [0107]As a non-exhaustive illustration only, the terminal device described herein may refer to mobile devices such as a cellular phone, a(String), 相关申请的交叉引用 [0001] 此申请根据 35 U.S.C. 2010 年 6 月 14 日向韩国知识产权局提交的韩国专利申请号 10-2010-0055844 的§119(a),其全部公开内容通过引用并入本文用于所有目的。 背景 [0002] 1. 领域 [0003] 以下描述涉及向连接到毫微微基站的移动终端进行广告的方法,以及移动终端、毫微微基站和宏基站的通信方法。 [0004] 2.相关技术说明 [0005] 毫微微蜂窝可以分为多种类型,例如,可用于在预定区域内提供超高速传输服务的个人毫微微蜂窝、用于为商店促销提供广告服务的商业毫微微蜂窝以及授权毫微微蜂窝以 提供定位服务。 大多数毫微微蜂窝应用关注用户的便利性,但没有充分考虑对各种安装人员和管理员的好处。 [0006] 在个人毫微微小区中,毫微微小区安装者和管理员可以作为服务受益人实质上相同,因此不需要区分各种管理权限。 然而,在商业毫微微小区中,需要区分毫微微小区安装者和毫微微小区管理员的权利,以保护商业权利。 概括 [0007] 在一个一般方面,提供了一种宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告关于用于识别毫微微小区中的毫微微小区的广播信道部分的信息。 宏小区,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,当移动终端在广播信道部分中识别出可接入的毫微微基站时,生成该移动终端的列表 相邻毫微微基站和相邻毫微微基站的信息基于移动终端的位置信息,将相邻毫微微基站列表和相邻毫微微基站信息发送给移动终端。 [0008] 该方法还可以包括发送连接信息以使移动终端能够接入由移动终端选择的毫微微基站。 [0009] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0010] 关于相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于每个毫微微基站提供的连接服务的折扣政策的信息。 [0011] 在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的语音呼叫发送信号,延迟语音呼叫发送信号的发送,作为响应 对语音呼叫发射信号的识别,并响应语音呼叫发射信号的识别,提供毫微微基站的独特的语音广告服务。 [0012] 该方法还可以包括识别从接收侧发送的回铃音信号,并且响应于回铃音信号的识别停止毫微微基站的唯一语音广告服务。 [0013] 在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的数据通信连接信号,作为响应推迟数据通信连接信号的发送 对数据通信连接信号的识别进行响应,并响应于数据通信连接信号的识别,向移动终端提供毫微微基站的唯一广告服务。 [0014] 该方法还可以包括识别关于移动终端期望访问的统一资源定位符(URL)地址的数据接收信号,并且响应于数据接收信号的识别停止毫微微基站的唯一广告服务。 [0015] 在另一方面,提供了一种移动终端的通信方法,该方法包括检测用于识别宏小区中的毫微微小区的广播信道部分,基于对移动终端的强度的测量来识别移动终端可接入的毫微微基站。 广播信道部分的信号,向宏基站发送移动终端的位置信息和对关于可访问的毫微微基站的信息的请求,接收移动终端的相邻毫微微基站的列表和关于移动终端的信息 从宏基站中选择相邻毫微微基站,并基于列表和关于相邻毫微微基站的信息来选择毫微微基站。 [0016] 当移动终端的毫微微小区探索模式设置为开启时,执行广播信道部分的检测。 [0017] 可接入毫微微基站的识别可以通过将预设阈值与广播信道部分的信号的测量强度进行比较来执行。 [0018] 可以基于移动终端的用户的偏好来选择所选择的毫微微基站。 [0019] 该方法还可以包括接收连接信息以使得能够从宏基站接入所选择的毫微微基站。 [0020] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0021] 关于相邻毫微微基站的信息可以包括关于毫微微基站分别位于的商店的信息,或者包括关于各个毫微微基站提供的连接服务的折扣政策的信息。 [0022] 在另一方面,提供了一种毫微微基站的通信方法,该方法包括从宏基站接收关于用于识别宏基站的宏小区中的毫微微小区的广播信道部分的报告,以及设置 广播信道部分中的信号,用于报告宏小区内的毫微微基站的毫微微小区的存在。 [0023] 在另一方面,提供了一种其中存储有程序指令的计算机可读存储介质,以使处理器执行宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告。 宏基站,关于用于识别宏小区中的毫微微小区的广播信道部分的信息,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,当移动终端识别 广播信道部分中可接入的毫微微基站,基于移动终端的位置信息生成相邻毫微微基站列表和相邻毫微微基站的信息,并发送相邻毫微微基站列表和 向移动终端发送有关相邻毫微微基站的信息。 [0024] 从以下描述、附图和权利要求中,其他特征和方面可能是显而易见的。 附图的简要说明 [0025] 如图。 附图说明图1是图示允许移动终端识别并连接到相邻毫微微小区的网络的示例的图。 [0026] 如图。 图2是图示允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例的图。 [0027] 如图。 图3是图示宏基站的通信方法的示例的流程图。 [0028] 如图。 图4是图示移动终端的通信方法的示例的流程图。 [0029]如图。 图5是示出向连接到毫微微基站的移动终端提供广告的方法的示例的流程图。 [0030] 在整个附图和描述中,除非另有说明,相同的附图标记应被理解为指代相同的元件、特征和结构。 为了清楚、说明和方便起见,这些元素的相对大小和描述可能会被夸大。 描述 [0031] 提供以下描述以帮助读者获得对本文描述的方法、装置和/或系统的全面理解。 因此,可以向本领域普通技术人员建议本文描述的方法、装置和/或系统的各种改变、修改和等效物。 此外,为了更清楚和简明,可以省略对众所周知的功能和结构的描述。 [0032] 如本文所述,宏小区是指宏基站的覆盖区域,毫微微小区是指毫微微基站的覆盖区域。 [0033] 如图。 图1图示了允许移动终端识别并连接到相邻毫微微小区的网络的示例。 [0034] 参考图。 参照图1,移动终端识别并连接到相邻毫微微小区的网络包括宏基站 101 , 两个毫微微基站 103 , 和一个移动终端 105 . 应当理解,宏基站、毫微微基站和移动终端的数量不限于图1所示的示例。 1、例如,网络可以包括一个或多个宏基站、一个或多个毫微微基站、以及一个或多个移动终端。 [0035] 宏基站覆盖区域包括宏小区。 宏基站 101 设置广播频道部分 109 在下行链路广播信道内识别毫微微小区。 宏基站 101 报告广播频道部分 109 到至少一个毫微微基站 103 在宏单元中。 [0036] 例如宏基站 101 可与毫微微基站链接 103 定位在宏单元中,并维护和更新包括连接信息的数据库。 连接信息可以包括例如关于链接的毫微微基站的信息 103 ,有关链接的毫微微基站的商店的信息 103 位于,等等。 [0037] 例如宏基站 101 可以在毫微微基站更新数据库时 103 在预设时间,或在任何其他所需时间,将其添加到宏小区。 [0038] 毫微微基站 103 可以向移动终端提供各种服务,例如商店的实时广告和活动公告 105 当移动终端的用户在毫微微基站的覆盖范围内或经过毫微微基站所在的商店时 103 位于。 [0039] 例如,毫微微基站 103 可与宏基站联动 101 吸引经过femto基站所在商店的顾客 103 位于。 毫微微基站 103 可与宏基站同步链接 101 . [0040] 移动终端 105 可以将自身设置为femtocell探索模式以自动识别femtocell。 例如,当移动终端的femtocell探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 以识别宏小区中的毫微微小区,并识别是否有相邻毫微微小区。 在femtocell探索模式下,移动终端 105 可以检测对应于一个或多个毫微微基站的一个或多个毫微微小区 103 ,在宏基站的宏小区内 101 并且可用于移动端 105 连接。 [0041] 移动终端 105 可以选择一个毫微微基站 103从一个或多个检测到的毫微微基站中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 从宏基站接收 101 . 因此,移动终端 105 可以提供femto基站的独特广告服务 103 当位于毫微微基站的毫微微小区内时 103 . [0042] 例如,femto 基站的独特广告服务 103 可能包括由 Femto 基站所在的商店销售的产品 103 定位,商店的广告,商店举办的活动的广告服务等。 [0043] 例如,当 femto 基站所在的商店 103 如果位于冰淇淋店,则该店的广告服务可以包括可在该店购买的新口味冰淇淋的广告、“特价”产品的折扣信息、折扣券等。 [0044] 如本文所述,当移动终端的毫微微小区探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 识别毫微微基站的毫微微小区 103 位于宏基站的宏小区内 101 ,并获得femto基站独有的广告服务 103 . [0045] 广播频道部分 109 用于识别宏小区中的毫微微小区可以设置为预设周期,例如一百毫秒、两百毫秒、五百毫秒或其他所需时间量的周期。 [0046] 在下文中,一种包括宏基站的方法 101 , 毫微微基站 103 , 和移动终端 105 其中移动端 105 识别相邻的毫微微基站 103 移动终端的 105 并连接到 femto 基站 103 , 被描述。 [0047] 如参考数字所示 110 , 宏基站 101 报告有关广播频道部分的信息 109 至对应于至少一毫微微基站的毫微微小区 103 在宏单元中。 例如,宏基站可以向一个或多个毫微微基站报告 103 . [0048] 毫微微基站 103 接收有关广播频道部分的报告 109 从宏基站 101 可以在广播频道部分设置信号 109 为了上报femto基站对应的femtocell的存在 103 ,如参考数字所示 120 . 例如,广播频道部分 109 下行广播信道可以设置为单个比特或多个比特。 [0049] 在 120 , 毫微微基站 103 可以在广播频道部分设置各种类型的信号 109 报告femto基站的femtocell存在 103 ,例如,毫微微基站 103 可以设置广播频道部分的特定位 109 为“1”或设置广播频道部分 109 到一个虚拟信号。 [0050] 当移动终端的femtocell探索模式 105 如附图标记所示,设置为 ON 130 , 移动端 105 可以检测广播频道部分 109 识别该毫微微基站对应的毫微微小区 103 在宏基站对应的宏小区内 101 . [0051] 移动终端 105 可以识别毫微微基站 103 移动端可访问 105 从至少一个毫微微基站中 103 在宏基站的宏小区内,基于广播信道部分的信号强度的测量结果 109 , 在 140 . [0052]例如,当广播频道部分的信号强度测量结果 109 高于预设阈值,移动终端 105 可以识别存在至少一个毫微微基站 103 靠近移动终端 105 移动端可访问 105 . 又例如,基于信号的强度,移动终端 105 可以确定多个毫微微基站相邻且可用,例如,两个毫微微基站、三个毫微微基站、四个毫微微基站或更多毫微微基站。 毫微微基站 103 可以在广播频道部分设置信号 109 在收到有关广播频道部分的报告后 109 从宏基站 101 . [0053] 移动终端 105 可以将其位置信息发送到宏基站 101 ,并且可以向宏基站发送请求 101 有关 femto 基站的信息 103 移动终端可以访问的 105 , 在 150 . [0054] 例如宏基站 101 可以生成相邻毫微微基站的列表 103 以及有关相邻毫微微基站的信息 103 基于移动终端的位置信息 105 从移动终端接收 105 ,并且可以将生成的信息发送到移动终端 105 , 在 160 . [0055] 例如,有关相邻毫微微基站的信息 103 移动终端的 105 可以包括关于商店的信息,其中每个相应的毫微微基站 103 位置或有关每个毫微微基站提供的连接服务的折扣政策的信息 103 . [0056] 移动终端 105 可选择一个毫微微基站 103 基于相邻毫微微基站列表 103 以及有关相邻毫微微基站的信息 103 从宏基站接收 101 , 在 170 . [0057] 在 170 , 移动端 105 可选择femto基站 103 在相邻毫微微基站列表中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 移动终端的 105 . [0058] 相邻毫微微基站列表的示例 103 从宏基站接收 101 可包括以下内容,如表 1 所示。 [0059] 表格1 反式 位置 毫微微基站 商业 使命 基站 站号 类别 使用政策 速度 a A 化妆品 自由的 低的 a B 衣服 10 美分/分钟 高的 a C 娱乐 自由的 中等的 a D 快餐 5 分/分钟 高的 (免费时 接收 广告) [0060] 在这个例子中,移动终端 105 接收与移动终端相邻的四个毫微微基站 A、B、C 和 D 的信息 105 从宏基站 101 . 因此,如果移动终端的用户 105 移动终端的用户更喜欢提供高传输速度和免费通信信道的毫微微基站 105 可以选择毫微微基站D来接收通信。 换言之,在提供高传输速度的毫微微基站B和D以及提供自由通信信道的毫微微基站A、C和D中,移动终端 105 可自动选择或移动终端的用户 105 可以选择满足所有用户偏好的毫微微基站D。 [0061] 例如,移动终端 105 可以使用由选择的毫微微基站D提供的通信信道。此外,移动终端 105 可以提供关于毫微微基站D所在的商店的信息或者关于毫微微基站D从毫微微基站D提供的连接服务的折扣政策的信息。 [0062] 在该示例中,毫微微基站D对应于快餐店的毫微微基站。 因此,移动终端 105可以提供关于毫微微基站D所在的快餐店的信息、关于快餐店提供的销售活动的信息、快餐店提供的折扣券以及销售活动的广告。 [0063] 再举一个例子,移动终端 105 可以选择一个毫微微基站 103 基于移动终端用户的兴趣 105 . 例如,移动终端 105 可以选择一个毫微微基站 103 位于感兴趣的商店中、提供销售活动的商店、在接收广告服务时提供产品优惠券以获得折扣的商店等。 [0064] 如上所述,移动终端 105 可以自动选择一个毫微微基站 103 通过各种方法从列表中。 取决于毫微微基站 103 选中,移动端的用户 105 可以从毫微微基站提供广告服务 103 . [0065] 此外,移动终端 105 本身可以提供相邻毫微微基站的列表 103 以及有关其事件的信息,以允许用户选择毫微微基站 103 . [0066] 作为另一个示例,毫微微基站 103 可由宏基站自动选择 101 . 在又一些实施例中,毫微微基站 103 可由移动端自动选择 105 基于可以由用户动态设置的预定设置或动态调整的设置。 作为又一示例,毫微微基站 103 可由移动终端的用户选择 105 . [0067] 再举一个例子,宏基站 101 可以存储移动终端的用户偏好 105 以及有关femto基站的信息 103 提前,并有选择地提供一个毫微微基站 103 根据存储的信息满足用户偏好。 [0068] 例如宏基站 101 可以包括关于移动终端的用户偏好的信息数据库 105 如下表2所示。 [0069] 表 2 移动的 反式 感兴趣的 终端 年龄 政策 使命 商业 ID 团体 利用 速度 类别 其他 A 20s 自由的 中等的 通讯—— 自由选择 化 收费时 终端, 接收 游戏 广告 B 30s 自由的/ 高的 餐厅 高反式 带电 任务速度 C 40s 自由的 中等的 运动的, 接收 书 运动相关 商店 广告 [0070] 宏基站 101 可选择满足移动终端用户偏好的毫微微基站 105 如表 2 所示,并提供给移动终端 105 . [0071] 收到手机端的选择后 105 , 宏基站 101 可以向移动终端发送连接信息 105 启用对所选毫微微基站的访问 103 , 在 180 . [0072] 移动终端 105 可以连接到选定的毫微微基站 103 使用从宏基站接收到的连接信息 101 , 在 190 . [0073] 因此,移动终端 105 连接到毫微微基站 103 可以提供由毫微微基站提供的各种通信服务和广告服务 103 . [0074] 例如,广告服务可以包括毫微微基站的独特语音广告服务 103 以及femto基站独有的展示广告服务 103 . 例如,femto 基站独有的语音广告服务 103 可提供给移动终端 105 而移动端 105 输入电话号码并等待呼叫接通。 [0075] 如本文所述,毫微微基站的独特广告服务 103 可提供给移动终端 105 而移动端 105 等待关于移动终端的统一资源定位符(URL)地址的数据接收 105 渴望访问。 [0076] 如图。 图2图示了允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例。 [0077] 参考图。 参照图2,用于向移动终端提供广告的网络包括对方交换站 201 , 一个毫微微基站 203 , 移动终端 205 ,以及接收方移动终端 207 . [0078] 例如,控制移动终端的用户 205 路过一家有femto基站的商店 203 定位到可以尝试通过输入与接收方移动终端对应的朋友的电话号码来呼叫朋友 207 , 尝试通话,在 210 . [0079] 响应移动终端用户的呼叫 205 , 毫微微基站 203 识别移动终端发送的语音呼叫发送信号 205 根据正在拨打的电话。 因此,毫微微基站 203 可以向移动终端提供广告 205 连接到毫微微基站 203 ,并且响应于语音呼叫发射信号的识别延迟语音呼叫发射信号的传输,在 220 . [0080] 例如,毫微微基站 203 可以包括语音呼叫发送信号识别模块,其可以识别从移动终端发送的语音呼叫发送信号 205 . 毫微微基站 203 可以提供femto基站独特的语音广告服务 203 到移动终端 205 响应语音呼叫发射信号的识别,在 230 . [0081] 毫微微基站 203 将延迟的语音呼叫发射信号转发给对方交换台 201 , 在 240 . 例如,毫微微基站 203 可以在经过预定时间量之后转发延迟的语音呼叫发送信号。 [0082] 例如,毫微微基站 203 可以识别从接收侧移动终端发送的回铃音信号 207 ,因此,毫微微基站 203 停止femto基站独有的语音广告服务 203 响应回铃音信号的识别,在 250 . [0083] 停止femto基站的独特语音广告服务后 203 , 毫微微基站 203 可以将回铃音信号转发给移动终端 205 连接语音通话,在 260 . [0084] 如图。 图3图示了宏基站的通信方法的示例。 [0085] 参考图。 参照图3,宏基站向宏小区中的至少一个毫微微基站报告关于广播信道部分的信息,在 310 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道。 [0086] 宏基站接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,在 320 . 例如,当移动终端识别出可接入的毫微微基站时,可以从移动终端发送位置信息和信息请求。 [0087] 关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息。 作为另一示例,该信息可以包括由每个毫微微基站提供的连接服务的折扣政策。 [0088] 宏基站根据移动终端的位置信息生成移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息,在 330 . [0089] 宏基站将移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息发送给移动终端,在 340 . [0090] 在 350,宏基站可以发送连接信息以使移动终端能够接入毫微微基站。 [0091] 使移动终端能够接入毫微微基站的连接信息可以是关于移动终端从列表中的移动终端的相邻毫微微基站中选择的毫微微基站的信息。 [0092] 如图。 图4图示了移动终端的通信方法的示例 [0093] 参考图。 4、移动终端可以判断毫微微小区探索模式是否设置为“开启”,在 410 . [0094] 当毫微微小区探索模式设置为“开启”时,移动终端检测广播信道部分以识别毫微微小区,在 420 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道段。 [0095] 作为确定的结果 410 ,如果femtocell探索模式未设置为“ON”,或者移动终端不具备femtocell探索功能,则移动终端可以不执行后续操作而完成该过程。 [0096] 移动终端基于广播信道部分的信号强度的测量来识别移动终端可接入的毫微微基站,以便识别宏小区中的毫微微小区。 例如,移动终端可以测量广播信道部分的信号强度以识别毫微微小区并将测量结果与预设阈值进行比较,在 440 . [0097] 当测量的广播频道部分的信号强度 440 高于预设阈值,移动终端可以识别出该毫微微基站可接入移动终端,在 450 . [0098] 移动终端向宏基站发送其位置信息和对关于可接入毫微微基站的信息的请求,在 460 . 移动终端从宏基站接收请求的信息,在 470 . 例如,从宏基站接收的信息可以包括移动终端的相邻毫微微基站的列表以及关于它们的信息。 例如,可以基于移动终端的位置信息来生成列表和信息。 作为示例,关于相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于由每个毫微微基站提供的连接服务的折扣策略的信息。 [0099] 移动终端可以基于相邻毫微微基站的列表和关于它们的信息来选择毫微微基站,在 480 . 例如,移动终端可以在选择毫微微基站时使用移动终端用户的偏好和关于相邻毫微微基站的信息。 [0100] 如图。 图5图示了向连接到毫微微基站的移动终端提供广告的方法的示例。 [0101] 参考图。 参照图5,当移动终端输入移动终端希望访问的URL地址等数据通信连接信号时,毫微微基站识别从移动终端发送的数据通信连接信号,在 510 . [0102] 毫微微基站响应于数据通信连接信号的识别延迟数据通信连接信号的传输,在 520 . [0103] 毫微微基站响应数据通信连接信号的识别,向移动终端提供独特的毫微微基站广告服务,在 530 . 并且,在预定量的时间过去之后,例如,毫微微基站可以将延迟的数据通信连接信号转发到运行中的互联网服务器。 [0104] 在 540,毫微微基站识别关于移动终端希望访问的URL地址的数据接收信号。 例如,毫微微基站可以包括功能模块,以识别移动终端期望的诸如主页或URL地址的数据接收信号以便识别数据接收信号。 [0105] 毫微微基站可以响应于识别关于移动终端期望访问的URL地址的数据接收信号来停止唯一的广告服务,在 550 . 毫微微基站可以将关于URL地址的数据接收信号转发给移动终端进行连接。 [0106] 如本文所述,移动终端可以包括各种模式,例如毫微微小区探索模式。 然而,应当理解,移动终端可能只有一种模式,其中移动终端不断地搜索可用的毫微微小区。 [0107] 仅作为非穷举说明,此处描述的终端设备可以指移动设备,例如蜂窝电话、个人数字助理(PDA)、数码相机、便携式游戏机、MP3播放器、便携式/个人多媒体 播放器 (PMP)、手持电子书、便携式实验室个人计算机 (PC)、全球定位系统 (GPS) 导航,以及台式 PC、高清电视 (HDTV)、光盘等设备 播放器、设置盒等,能够进行与本文所公开的一致的无线通信或网络通信。 [0108] 计算系统或计算机可以包括与总线电连接的微处理器、用户接口和存储器控制器。 它还可以包括闪存设备。 闪存设备可以通过存储控制器存储N位数据。 N位数据由微处理器处理或将由微处理器处理,N可以为1或大于1的整数。当计算系统或计算机为移动设备时,可额外提供电池以提供计算的工作电压 系统或计算机。 [0109] 对于本领域的普通技术人员来说,计算系统或计算机还可以包括应用芯片组、相机图像传感器(CIS)、移动动态随机存取存储器(DRAM)等应该是显而易见的。 存储器控制器和闪存设备可以构成使用非易失性存储器来存储数据的固态驱动器/磁盘(SSD)。 [0110] 上述过程、功能、方法和/或软件可以被记录、存储或固定在一个或多个计算机可读存储介质中,该存储介质包括要由计算机实现以使处理器执行或执行程序的程序指令 指示。 媒体还可以单独或与程序指令、数据文件、数据结构等组合地包括。 计算机可读存储介质的示例包括诸如硬盘、软盘和磁带之类的磁介质; 光媒体,如 CD ROM 盘和 DVD; 磁光介质,例如光盘; 以及专门用于存储和执行程序指令的硬件设备,例如只读存储器(ROM)、随机存取存储器(RAM)、闪存等。 程序指令的示例包括机器代码(例如由编译器生成)和包含可以由计算机使用解释器执行的更高级别代码的文件。 所描述的硬件设备可以被配置为充当一个或多个软件模块以执行上述操作和方法,反之亦然。 此外,计算机可读存储介质可以分布在通过网络连接的计算机系统之间,并且可以以分散方式存储和执行非暂时性计算机可读代码或程序指令。 [0111]上面已经描述了许多示例。 然而,应该理解可以进行各种修改。 例如,如果以不同的顺序执行所描述的技术和/或如果所描述的系统、架构、设备或电路中的组件以不同的方式组合和/或由其他组件替换或补充或 他们的等价物。 因此,其他实施方式在所附权利要求的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.377 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8548504B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270692(Integer), KR101622169B1(String), 1047297(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270692(Integer), KR1020110136068A(String), 1047298(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270692(Integer), US20110306324A1(String), 1047299(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270692(Integer), US20130346212A1(String), 1047300(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.429 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270692(Integer), US8548504B2(String), 1047301(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270692(Integer), WO2011159010A1(String), 1047302(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8548504B2(String), US8548504B2(String), 1380556800(Integer), 270692(Integer), 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 270673(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 270673(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185015(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185015(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185015(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185015(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.507 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Integrated content file search method for mobile terminal and mobile terminal implementing the same(String), 移动终端集成内容文件搜索方法及实现该方法的移动终端(String), US20080010261A1(String), An integrated content file search method for a mobile terminal and a mobile terminal implementing the same are provide, in which content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and selection of one of the found content files causes immediate execution of the selected content file. A search mode for a content file search is set, a search string from a user is input, the input search string is displayed on a display unit of the mobile terminal, the text entry of content files stored in the mobile terminal are accessed, the text entry is verified to determine whether the text entry contains the input search string, a textual excerpt from the text entry containing the input search string is displayed on the display unit, and a content file that contains the displayed textual excerpt is executed.(String), 提供了一种移动终端集成内容文件搜索方法及实现该方法的移动终端,以集成的方式搜索移动终端中分层或非分层结构存储的内容文件,并选择其中一个。 找到的内容文件会立即执行选定的内容文件。 设置内容文件搜索的搜索模式,输入来自用户的搜索字符串,输入的搜索字符串显示在移动终端的显示单元上,访问存储在移动终端中的内容文件的文本条目, 验证文本条目以确定该文本条目是否包含输入搜索字符串,将包含输入搜索字符串的文本条目的文本摘录显示在显示单元上,并执行包含显示的文本摘录的内容文件。(String), US11/812880(String), 1182441600(Integer), US20080010261A1(String), 1199894400(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 5(Integer), US20050037816A1 | US20060047644A1 | US20070255785A1 | US6405060B1 | US6990180B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185016(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\abdcc21f218d45048cc5af68e79510bc.png(String), 185016(Integer), abdcc21f218d45048cc5af68e79510bc.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Integrated content file search method for mobile terminal and mobile terminal implementing the same(String), 移动终端集成内容文件搜索方法及实现该方法的移动终端(String), US20080010261A1(String), An integrated content file search method for a mobile terminal and a mobile terminal implementing the same are provide, in which content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and selection of one of the found content files causes immediate execution of the selected content file. A search mode for a content file search is set, a search string from a user is input, the input search string is displayed on a display unit of the mobile terminal, the text entry of content files stored in the mobile terminal are accessed, the text entry is verified to determine whether the text entry contains the input search string, a textual excerpt from the text entry containing the input search string is displayed on the display unit, and a content file that contains the displayed textual excerpt is executed.(String), 提供了一种移动终端集成内容文件搜索方法及实现该方法的移动终端,以集成的方式搜索移动终端中分层或非分层结构存储的内容文件,并选择其中一个。 找到的内容文件会立即执行选定的内容文件。 设置内容文件搜索的搜索模式,输入来自用户的搜索字符串,输入的搜索字符串显示在移动终端的显示单元上,访问存储在移动终端中的内容文件的文本条目, 验证文本条目以确定该文本条目是否包含输入搜索字符串,将包含输入搜索字符串的文本条目的文本摘录显示在显示单元上,并执行包含显示的文本摘录的内容文件。(String), US11/812880(String), 1182441600(Integer), US20080010261A1(String), 1199894400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 5(Integer), US20050037816A1 | US20060047644A1 | US20070255785A1 | US6405060B1 | US6990180B2(String), \20230420\abdcc21f218d45048cc5af68e79510bc.png(String), 14(Integer), 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 1. An integrated content file search method for a mobile terminal, the method comprising:setting a search mode for a content file search;inputting a search string;displaying the input search string on a display unit;accessing a text entry of stored content files;verifying the text entry to determine whether the text entry contains the input search string;displaying a textual excerpt from the text entry containing the input search string on the display unit; andexecuting a content file that contains the displayed textual excerpt.(String), 1.一种移动终端综合内容文件搜索方法,该方法包括:设置内容文件搜索的搜索模式;输入搜索字符串;在显示单元上显示输入的搜索字符串;访问存储的内容文件的文本条目;验证文本条目以确定文本条目是否包含输入的搜索字符串;在显示单元上显示来自包含输入搜索字符串的文本条目的文本摘录;和执行包含显示的文本摘录的内容文件。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 2. The integrated content file search method of claim 1, wherein the text entry of the stored content files includes a list of file subjects on the content files.(String), 2.如权利要求1所述的综合内容文件搜索方法,其中存储的内容文件的文本条目包括内容文件的文件主题列表。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 3. The integrated content file search method of claim 1, wherein the text entry of the stored content files includes textual contents of the content files.(String), 3.如权利要求1所述的综合内容文件搜索方法,其中存储的内容文件的文本条目包括内容文件的文本内容。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 4. The integrated content file search method of claim 1, wherein the displaying of the textual excerpt comprising displaying a textual excerpt of the corresponding content file is displayed together with an icon indicating the content file.(String), 4.如权利要求1所述的综合内容文件搜索方法,其中文本摘录的显示包括显示相应内容文件的文本摘录,连同指示内容文件的图标一起显示。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 5. The integrated content file search method of claim 4, further comprising selecting an icon to execute the content file associated with the icon.(String), 5.如权利要求4所述的综合内容文件搜索方法,还包括选择图标以执行与该图标关联的内容文件。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 6. The integrated content file search method of claim 4, wherein the icon comprises an avatar.(String), 6.如权利要求4所述的综合内容文件搜索方法,其中该图标包括一个化身。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 7. The integrated content file search method of claim 1, wherein the content files comprises at least one of phone book files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files and game program files.(String), 7.如权利要求1所述的综合内容文件搜索方法,其中内容文件包括电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静态图片文件、运动图片文件和游戏程序文件中的至少一种。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 8. A mobile terminal comprising:a key input unit for setting a search mode for a content file search and inputting a search string;a display unit for displaying the input search string;a controller for accessing a text entry of content files, verifying the text entry to determine whether the text entry contains the input search string, displaying a textual excerpt from the text entry containing the input search string, and executing a content file that contains the textual excerpt.(String), 8.移动终端包括:键输入单元,用于设置内容文件搜索的搜索模式并输入搜索字符串;显示单元,用于显示输入的搜索字符串;控制器,用于访问内容文件的文本条目,验证文本条目以确定文本条目是否包含输入搜索字符串,显示来自包含输入搜索字符串的文本条目的文本摘录,以及执行包含文本的内容文件摘抄。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 9. The mobile terminal of claim 8, wherein the text entry of content files comprises a list of file subjects on the content files.(String), 9.如权利要求8所述的移动终端,其中内容文件的文本条目包括内容文件上的文件主题列表。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 10. The mobile terminal of claim 8, wherein the text entry of content files comprises textual contents of the content files.(String), 10.如权利要求8所述的移动终端,其中内容文件的文本条目包括内容文件的文本内容。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 11. The mobile terminal of claim 8, wherein the textual excerpt is displayed together with an icon indicating the content file.(String), 11.如权利要求8所述的移动终端,其中文本摘录与指示内容文件的图标一起显示。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 12. The mobile terminal of claim 11, wherein selection of the icon executes the content file associated with the icon.(String), 12.如权利要求11所述的移动终端,其中选择图标会执行与该图标相关联的内容文件。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 13. The mobile terminal of claim 11, wherein the icon comprises an avatar.(String), 13.如权利要求11所述的移动终端,其中该图标包括一个化身。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185016(Integer), 14. The mobile terminal of claim 8, wherein the content files comprises at least one of phone book files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files and game program files.(String), 14.如权利要求8所述的移动终端,其中内容文件包括电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静态图片文件、运动图片文件和游戏程序文件中的至少一种。(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.736 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.736 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185016(Integer), CROSS-REFERENCE TO RELATED PATENT APPLICATION [0001]This application claims the benefit under 35 U.S.C. §119(a) of Korean Patent Application filed in the Korean Intellectual Property Office on Jul. 6, 2006 and assigned Serial No. 2006-0063428, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an integrated method and mobile terminal for searching a desired content file in the mobile terminal. More particularly, the present invention relates to an integrated content file search method for a mobile terminal wherein content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and searched content files can be selected for immediate execution. [0004]2. Description of the Related Art [0005]In recent years, mass-storage devices have been installed in mobile terminals to increase storage capacity. Some mobile terminals include a hard disk drive (HDD) or a high-capacity non-volatile memory device. [0006]With increased storage capacity, various content files (for example, phonebook files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files, and game program files) are classified according to their categories and stored in a hierarchical structure in a mobile terminal. In a hierarchical structure such as a tree-like structure, a parent-child relation exists between an element (parent) and a next-lower-level element (child). Namely, a parent element can have zero, one or multiple child elements, and a child element can have only one parent element. [0007]Because a large number of content files are stored in a hierarchical structure, it is difficult to know the location of a particular content file in a mobile terminal. Further, in a conventional search approach, content file search is limited to a particular folder or category. [0008]Accordingly, there is a need for an improved method for locating a content file in a mobile terminal and a mobile terminal implementing the same. SUMMARY OF THE INVENTION [0009]An aspect of exemplary embodiments of the present invention is to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of exemplary embodiments of the present invention is to provide an integrated content file search method for a mobile terminal wherein contents files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner and selection of one of the found content files causes immediate execution of the selected content file. [0010]In order to achieve the aspects, an exemplary embodiment of the present invention provides an integrated content file search method for a mobile terminal, in which a search mode is set for content file search, a search string from a user is input; the input search string is displayed on a display unit of the mobile terminal, a text entry of content files stored in the mobile terminal is accessed, the text entry is verified to determine whether the text entry contains the input search string, a textual excerpt from the text entry containing the input search string is displayed on the display unit, and a content file that contains the displayed textual excerpt is executed. [0011]In an exemplary implementation, the text entry of content files may include a list of file subjects on the content files. Alternatively, the text entry of content files may include textual contents of the content files. [0012]In another exemplary implementation, a textual excerpt of the corresponding content file is displayed together with an icon indicating the content file. [0013]In still another exemplary implementation, selection of a displayed icon causes execution of the content file associated with the icon. [0014]In a further exemplary implementation, the icon is represented in the form of an avatar. [0015]In order to achieve the aspects, an exemplary embodiment of the present invention provides a mobile terminal which includes: a key input unit for setting a search mode for a content file search and inputting a search string; a display unit for displaying the input search string; a controller for accessing a text entry of content files, verifying the text entry to determine whether the text entry contains the input search string, displaying a textual excerpt from the text entry containing the input search string, and executing a content file that contains the textual excerpt. BRIEF DESCRIPTION OF THE DRAWINGS [0016]The above and other objects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following detailed description in conjunction with the accompanying drawings, in which: [0017]FIG. 1 illustrates a configuration of a mobile terminal according to an exemplary embodiment of the present invention; [0018]FIG. 2 is a flow chart illustrating steps of an integrated content file search method for a mobile terminal according to an exemplary embodiment of the present invention; and [0019]FIG. 3 illustrates a display screen representation resulting from execution of the search method of FIG. 2. [0020]Throughout the drawings, the same drawing reference numerals will be understood to refer to the same elements, features and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0021]The matters defined in the description such as a detailed construction and elements are provided to assist in comprehensive understanding of exemplary embodiments of the invention. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0022]FIG. 1 illustrates a configuration of a mobile terminal according to an exemplary embodiment of the present invention. [0023]Referring to FIG. 1, the mobile terminal includes a camera module 111, a video processor 112, a display unit 113, a memory unit 114, a key input unit 115, an audio processor 116, a radio frequency (RF) unit 117, a data processor 118, and a controller 119. [0024]The camera module 111 includes a camera lens for forming an image of a target object, a camera sensor for converting an optical signal corresponding to the formed image into an electrical signal, and a signal processor for converting the analog electrical signal from the camera sensor into digital data. The camera sensor may be a charge-coupled device (CCD) sensor, and the signal processor may be a digital signal processor (DSP). The camera sensor and signal processor may be implemented as a single body or as separate bodies. [0025]The video processor 112 generates screen data to display an image signal from the camera module 111. The video processor 112 processes the image signal from the camera module 111 on a frame-by-frame basis to output frame image data corresponding to display characteristics and the size of the display unit 113. The video processor 112 includes a video coder/decoder (codec) to compress frame image data to be displayed on the display unit 113 in a predetermined format and to decompress compressed frame image data into frame image data. The video codec may be a Joint Photographic Experts Group (JPEG) codec, Moving Picture Experts Group-4 (MPEG-4) codec or wavelet codec. The video processor 112 may also perform an on screen display (OSD) function, and output OSD data corresponding to the picture size under the control of the controller 119. [0026]The display unit 113 displays an image signal from the video processor 112, and data from the controller 119 on a screen. The display unit 113 may include a panel that is composed of display devices such as liquid crystal display (LCD) devices or organic light emitting diodes (OLED). In an exemplary implementation, the panel has a touch screen capability. [0027]The memory unit 114 includes a program memory section and a data memory section. The program memory section stores executable programs of the mobile terminal, and the data memory section temporarily stores data resulting from execution of the programs. In an exemplary implementation, the memory unit 114 includes a hard disk drive for a mobile terminal or a non-volatile memory device such as a flash memory. [0028]The key input unit 115 includes a plurality of keys for inputting numeric data, text data and phone numbers, and a plurality of function keys for setting functions of the mobile terminal. The key input unit 115 may further include shortcut keys such as keys labeled by ‘#’ and ‘*’. [0029]The audio processor 116 reproduces an audio signal from an audio codec of the data processor 18, and transmits an audio signal from a microphone (MIC) to the audio codec of the data processor 18. [0030]The RF unit 117 performs wireless communication operations for the mobile terminal. The RF unit 117 includes a RF transmitter for upconverting the frequency of a signal to be transmitted and amplifying the signal, and an RF receiver for low-noise amplifying a received signal and downconverting the frequency of the signal. [0031]The data processor 118 includes a transmitter for encoding and modulating a signal to be transmitted, and a receiver for demodulating and decoding a received signal. The data processor 118 may include a modem and a codec. The codec includes a data codec for processing packet data, and an audio codec for processing an audio signal such as a voice signal. [0032]The controller 119 controls the overall operation of the mobile terminal. The controller 119 may include the data processor 118. The controller 119 is connected to the video processor 112, display unit 113, memory unit 114, key input unit 115, audio processor 116 and data processor 18, and controls these components to exchange and process data, and to establish a call. [0033]FIG. 2 is a flow chart illustrating steps of an integrated content file search method for a mobile terminal according to an exemplary embodiment of the present invention; and FIG. 3 illustrates a display screen representation resulting from execution of the search method of FIG. 2. [0034]Referring to FIG. 2, the mobile terminal is initially in an idle mode after power-on (S201). [0035]The user inputs a predetermined key to set a search mode for finding a desired content file (S203). [0036]Content files include various data files such as phonebook files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files, and game program files. [0037]In setting a search mode, a search range may be reduced by limiting categories of content files to be searched. For example, a search range may be set to include phonebook files in the mobile terminal, or set to include short message files, multimedia message files and electronic mail files. [0038]If a search range is set to include file contents in addition to file subjects, a content file containing a particular search string in textual contents thereof can be found. [0039]The user inputs a search string using a keypad of the key input unit 115 or a touch screen of the display unit 113 (S205). [0040]The controller 119 displays the input search string on a screen of the display unit 113 (S207). [0041]The controller 119 accesses a text entry of content files (S209). The text entry of content files stored in the mobile terminal may include a list of file subjects on the content files. [0042]In an exemplary implementation, each content file to be stored in the mobile terminal has at least one file subject. Thereby a content file whose file subject contains an input search string can be found. [0043]The text entry of content files may also include textual contents of the content files. If the search range is set to include file contents in addition to file subjects, a content file containing the input search string in the textual contents can be found. For example, if the contents of a document file contain an input search string, the file name of the document file is output. [0044]The controller 119 checks the text entry to determine whether at least one content file containing the input search string exists (S211). [0045]If no content file containing the input search string is found, the controller 119 returns to step S205 to input a search string for a new search. [0046]If a content file that contains the input search string is found, a textual excerpt and/or a file subject containing the input search string from the text entry, and a category of the found content file is displayed on the display unit 113 (S213). [0047]FIG. 3 illustrates a search result when a search string ‘James’ is input in a search field 320 of the display unit 113. Every content file whose file subject or textual contents contains the search string ‘James’ is found. In FIG. 3, content files, such as a phone book file 330, a text message file 340, an electronic mail file 350, a still picture file 360, and a document file 370 are found, and textual excerpts and/or file subjects of the found content files are displayed in a list of search results. [0048]In addition, an icon indicating a file category is displayed in the list of search results for easy identification of the category of a corresponding content file. The icon can be represented in the form of an avatar. [0049]The user selects a displayed item in a list of search results for execution of a content file associated with the selected item (S215). The user can select a file sequence number or an icon in the list of search results using a key of the key input unit 115 or a touch screen of the display unit 113. [0050]A content file associated with the selected item is entered into an execution mode and executed (S217). [0051]The controller 119 asks the user whether to execute another content file in the list of search results (S219). [0052]If the user decides to execute another content file in the list of search results at step S219, the controller 119 returns to step S213 and repeats step S213 and subsequent steps to execute another content file. [0053]If the user decides not to execute another content file at step S219, the controller 119 asks the user whether to perform a new search (S223). [0054]If the user inputs a command key for setting a search mode, the controller 119 returns to step S205 and repeats step S205 and subsequent steps to perform a new search. [0055]As apparent from the above description, exemplary embodiments of the present invention provide an integrated content file search method for a mobile terminal. Content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and selection of one of the found content files causes immediate execution of the selected content file. Thereby a desired content file can be easily found and executed. [0056]While the present invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.(String), 相关专利申请的交叉引用 [0001] 本申请根据 35 U.S.C. §119(a) 于 2006 年 7 月 6 日在韩国知识产权局提交并分配序列号为 2006-0063428 的韩国专利申请,其全部公开内容通过引用并入本文。 发明背景 [0002] 一、发明领域 [0003] 本发明总体上涉及一种用于在移动终端中搜索所需内容文件的集成方法和移动终端。 更具体地,本发明涉及一种用于移动终端的集成内容文件搜索方法,其中以集成方式搜索以分层或非分层结构存储在移动终端中的内容文件,并且可以选择搜索到的内容文件以用于即时 执行。 [0004] 二、相关技术说明 [0005] 近年来,大容量存储设备已经安装在移动终端中以增加存储容量。 一些移动终端包括硬盘驱动器(HDD)或大容量非易失性存储设备。 [0006] 随着存储容量的增加,各种内容文件(例如,电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静态图片文件、运动图片文件和游戏程序文件)根据其类别进行分类 并以分层结构存储在移动终端中。 在树状结构等层级结构中,元素(父)与下一级元素(子)之间存在父子关系。 即,一个父元素可以有零个、一个或多个子元素,而一个子元素只能有一个父元素。 [0007] 由于大量的内容文件以分层结构存储,因此很难知道特定内容文件在移动终端中的位置。 此外,在传统的搜索方法中,内容文件搜索限于特定文件夹或类别。 [0008] 因此,需要一种用于在移动终端中定位内容文件的改进方法和实现该方法的移动终端。 发明内容 [0009] 本发明示例性实施例的一个方面是至少解决上述问题和/或缺点并且至少提供下述优点。 因此,本发明示例性实施例的一个方面是提供一种用于移动终端的综合内容文件搜索方法,其中以综合方式搜索以分层或非分层结构存储在移动终端中的内容文件,并选择一个 找到的内容文件导致立即执行所选内容文件。 [0010] 为了实现这些方面,本发明的示例性实施例提供了一种用于移动终端的集成内容文件搜索方法,其中为内容文件搜索设置搜索模式,输入来自用户的搜索字符串; 输入的搜索字符串显示在移动终端的显示单元上,访问存储在移动终端中的内容文件的文本条目,验证文本条目以确定文本条目是否包含输入的搜索字符串,文本摘自 包含输入的搜索字符串的文本条目显示在显示单元上,并且执行包含显示的文本摘录的内容文件。 [0011] 在示例性实施方式中,内容文件的文本条目可以包括关于内容文件的文件主题的列表。 或者,内容文件的文本条目可以包括内容文件的文本内容。 [0012] 在另一示例性实施方式中,相应内容文件的文本摘录与指示内容文件的图标一起显示。 [0013] 在又一示例性实施方式中,显示图标的选择引起与该图标相关联的内容文件的执行。 [0014] 在进一步的示例性实施方式中,图标以化身的形式表示。 [0015]为了实现这些方面,本发明的示例性实施例提供了一种移动终端,包括:键输入单元,用于设置内容文件搜索的搜索模式并输入搜索字符串; 显示单元,用于显示输入的搜索字符串; 控制器,用于访问内容文件的文本条目,验证文本条目以确定文本条目是否包含输入搜索字符串,显示来自包含输入搜索字符串的文本条目的文本摘录,以及执行包含文本的内容文件 摘抄。 附图的简要说明 [0016] [0010] 通过以下结合附图的详细描述,本发明的某些示例性实施例的上述和其他目的、特征和优点将更加明显,其中: [0017] 图1图示了根据本发明示例性实施例的移动终端的配置; [0018] 图2是示出根据本发明示例性实施例的用于移动终端的综合内容文件搜索方法的步骤的流程图; 和 [0019] 图3图示了由执行图2的搜索方法产生的显示屏表示。 [0020] 在整个附图中,相同的附图标记将被理解为指代相同的元件、特征和结构。 示例性实施方案的详细描述 [0021] 提供描述中定义的事项,例如详细构造和元件,以帮助全面理解本发明的示例性实施例。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对本文描述的实施例进行各种改变和修改。 此外,为了清楚和简明起见,省略了对众所周知的功能和结构的描述。 [0022] 图1图示了根据本发明示例性实施例的移动终端的配置。 [0023] 参见图1,移动终端包括摄像头模块 111 , 视频处理器 112 , 显示单元 113 , 一个记忆单元 114 , 一个按键输入单元 115 , 音频处理器 116 , 射频 (RF) 单元 117 , 数据处理器 118 , 和一个控制器 119 . [0024] 相机模组 111 包括用于形成目标物体的图像的相机镜头、用于将与形成的图像相对应的光信号转换为电信号的相机传感器以及用于将来自相机传感器的模拟电信号转换为数字数据的信号处理器。 相机传感器可以是电荷耦合器件(CCD)传感器,信号处理器可以是数字信号处理器(DSP)。 相机传感器和信号处理器可以实现为单个主体或单独的主体。 [0025] 视频处理器 112 生成屏幕数据以显示来自相机模块的图像信号 111 . 视频处理器 112 处理来自相机模块的图像信号 111 逐帧输出对应显示特性和显示单元尺寸的帧图像数据 113 . 视频处理器 112 包括一个视频编码器/解码器(编解码器)来压缩要在显示单元上显示的帧图像数据 113 以预定格式将压缩的帧图像数据解压缩为帧图像数据。 视频编解码器可以是联合图像专家组(JPEG)编解码器、运动图像专家组-4(MPEG-4)编解码器或小波编解码器。 视频处理器 112 还可以执行屏幕显示(OSD)功能,并在控制器的控制下输出与画面尺寸对应的OSD数据 119 . [0026] 显示单元 113 显示来自视频处理器的图像信号 112 , 以及来自控制器的数据 119 在屏幕上。 显示单元 113可包括由诸如液晶显示(LCD)装置或有机发光二极管(OLED)之类的显示装置构成的面板。 在示例性实施方式中,面板具有触摸屏能力。 [0027] 记忆单元 114 包括一个程序存储部分和一个数据存储部分。 程序存储部分存储移动终端的可执行程序,数据存储部分临时存储程序执行产生的数据。 在示例性实现中,存储单元 114 包括用于移动终端的硬盘驱动器或诸如闪存的非易失性存储设备。 [0028] 按键输入单元 115 包括用于输入数字数据、文本数据和电话号码的多个键,以及用于设置移动终端功能的多个功能键。 按键输入单元 115 还可以包括快捷键,例如标有“#”和“*”的键。 [0029] 音频处理器 116 从数据处理器的音频编解码器再现音频信号 18 , 并将来自麦克风 (MIC) 的音频信号传输到数据处理器的音频编解码器 18 . [0030] 射频单元 117 为移动终端执行无线通信操作。 射频单元 117 包括用于对要发送的信号进行上变频和放大信号的RF发射器,以及用于对接收到的信号进行低噪声放大和对信号的频率进行下变频的RF接收器。 [0031] 数据处理器 118 包括用于对要发送的信号进行编码和调制的发送器,以及用于对接收到的信号进行解调和解码的接收器。 数据处理器 118 可能包括调制解调器和编解码器。 编解码器包括用于处理分组数据的数据编解码器和用于处理诸如语音信号的音频信号的音频编解码器。 [0032] 控制器 119 控制移动终端的整体操作。 控制器 119 可能包括数据处理器 118 . 控制器 119 连接到视频处理器 112 , 显示单元 113 , 记忆单元 114 , 按键输入单元 115 , 音频处理器 116 和数据处理器 18 ,并控制这些组件交换和处理数据,并建立呼叫。 [0033] 图2是示出根据本发明示例性实施例的用于移动终端的综合内容文件搜索方法的步骤的流程图; 图3示出了执行图2的搜索方法所产生的显示屏幕表示。 [0034] 参考图2,移动终端在开机后最初处于空闲模式(S 201 ). [0035] 用户输入预定键以设置用于查找所需内容文件的搜索模式(S 203 ). [0036] 内容文件包括各种数据文件,例如电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静止图片文件、运动图片文件和游戏程序文件。 [0037] 在设置搜索模式时,可以通过限制要搜索的内容文件的类别来缩小搜索范围。 例如,可以将搜索范围设置为包括移动终端中的电话本文件,或者设置为包括短信文件、彩信文件和电子邮件文件。 [0038] 如果将搜索范围设置为包括文件内容以及文件主题,则可以找到在其文本内容中包含特定搜索字符串的内容文件。 [0039] 用户使用键输入单元的小键盘输入搜索字符串 115 或显示单元的触摸屏 113 (小号 205 ). [0040] 控制器 119 在显示单元的屏幕上显示输入的搜索字符串 113 (小号 207 ). [0041] 控制器 119 访问内容文件的文本条目(S 209 ). 存储在移动终端中的内容文件的文本条目可以包括内容文件上的文件主题列表。 [0042]在一个示例性实施方式中,移动终端中存储的每个内容文件具有至少一个文件主题。 从而可以找到其文件主题包含输入的搜索字符串的内容文件。 [0043] 内容文件的文本条目还可以包括内容文件的文本内容。 如果搜索范围设置为包括文件内容和文件主题,则可以找到文本内容中包含输入搜索字符串的内容文件。 例如,如果文档文件的内容包含输入搜索字符串,则输出文档文件的文件名。 [0044] 控制器 119 检查文本条目以确定是否存在至少一个包含输入搜索字符串的内容文件(S 211 ). [0045] 如果没有找到包含输入搜索字符串的内容文件,控制器 119 回到步骤S 205 为新搜索输入搜索字符串。 [0046] 如果找到包含输入搜索字符串的内容文件,则在显示单元上显示包含来自文本条目的输入搜索字符串的文本摘录和/或文件主题,以及找到的内容文件的类别 113 (小号 213 ). [0047] 图 3 说明了在搜索字段中输入搜索字符串“James”时的搜索结果 320 显示单元 113 . 找到文件主题或文本内容包含搜索字符串“James”的每个内容文件。 在图3中,内容文件,例如电话簿文件 330 , 一个短信文件 340 , 一个电子邮件文件 350 , 静态图片文件 360 , 和文档文件 370 找到,并且找到的内容文件的文本摘录和/或文件主题显示在搜索结果列表中。 [0048] 此外,在搜索结果列表中显示指示文件类别的图标,以便于识别相应内容文件的类别。 图标可以以化身的形式表示。 [0049] 用户选择搜索结果列表中显示的项目以执行与所选项目相关联的内容文件(S 215 ). 用户可以使用键输入单元的键在搜索结果列表中选择文件序号或图标 115 或显示单元的触摸屏 113 . [0050] 与所选项目关联的内容文件进入执行模式并执行(S 217 ). [0051] 控制器 119 询问用户是否执行搜索结果列表中的另一个内容文件(S 219 ). [0052] 如果用户在步骤S决定执行搜索结果列表中的另一个内容文件 219 , 控制器 119 回到步骤S 213 并重复步骤 S 213 以及执行另一个内容文件的后续步骤。 [0053] 如果用户在步骤 S 决定不执行另一个内容文件 219 , 控制器 119 询问用户是否执行新的搜索(S 223 ). [0054] 如果用户输入用于设置搜索模式的命令键,则控制器 119 回到步骤S 205 并重复步骤 S 205 以及执行新搜索的后续步骤。 [0055] 从以上描述显而易见,本发明的示例性实施例提供了一种用于移动终端的综合内容文件搜索方法。 以集成的方式搜索存储在移动终端中的分层或非分层结构的内容文件,并且选择找到的内容文件之一导致立即执行所选内容文件。 从而可以容易地找到并执行所需的内容文件。 [0056] 虽然本发明已经参照其某些示例性实施例被示出和描述,但是本领域的技术人员将理解,在不脱离所定义的本发明的精神和范围的情况下,可以在其中进行形式和细节的各种改变 通过所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100745040B1(String), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.756 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100745040B1(String), US20080010261A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.757 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100745040B1(String), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270693(Integer), KR100745040B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270693(Integer), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20080010261A1(String), US20080010261A1(String), 1199894400(Integer), 270693(Integer), 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), NAM, HAN SOEK(String), KIM, BONG KYUN(String), KIM, HWAN(String), 三星电子株式会社(String), NAM HAN SOEK(String), KIM BONG KYUN(String), KIM HWAN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185016(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185016(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: NAM, HAN SOEK(String), NAM HAN SOEK(String), 0(Integer), 1681975559(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: KIM, BONG KYUN(String), KIM BONG KYUN(String), 0(Integer), 1681975559(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: KIM, HWAN(String), KIM HWAN(String), 0(Integer), 1681975559(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185016(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75947(Integer), 2(Integer), 185016(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75948(Integer), 2(Integer), 185016(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75949(Integer), 2(Integer), 185016(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9560486B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for identifying motion status of mobile terminal, and mobile terminal(String), 一种识别移动终端运动状态的方法及移动终端(String), US9560486B2(String), A method for identifying a motion status of a mobile terminal, and a mobile terminal are provided. The method includes collecting information about multiple wireless local area network (WLAN) access points during each time of scanning, where the information includes a basic service set identifier and signal strength; calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points; and presetting a belief decision threshold and a list orthogonality decision threshold, and comparing the decision thresholds with calculated values to acquire the motion status of the mobile terminal. Therefore, the motion status of the mobile terminal may be acquired without making a change in any hardware on an existing mobile terminal. In addition, the present disclosure is applicable to an area covered by multiple wireless local area network access points.(String), 提供了一种移动终端运动状态的识别方法及移动终端。 该方法包括在每次扫描时收集多个无线局域网(WLAN)接入点的信息,该信息包括基本服务集标识和信号强度; 根据多个WLAN接入点的信息计算置信度值和列表正交度值; 预设置信度判定阈值和列表正交性判定阈值,将判定阈值与计算值进行比较,获取移动终端的运动状态。 因此,无需对现有移动终端的硬件做任何改动,即可获取移动终端的运动状态。 另外,本发明适用于多个无线局域网接入点覆盖的区域。(String), US14/923094(String), 1445788800(Integer), US9560486B2(String), 1485792000(Integer), 1485792000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 13(Integer), CN101627561A | CN101822094A | CN102111434A | CN102355530A | CN1501610A | CN201978444U | US20070018890A1 | US20070183344A1 | US20080207278A1 | US20100248668A1 | US20100255781A1 | US20120004881A1 | US20140141796A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185017(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2c85b2403ff54aa29d8a472c1ac5b099.png(String), 185017(Integer), 2c85b2403ff54aa29d8a472c1ac5b099.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for identifying motion status of mobile terminal, and mobile terminal(String), 一种识别移动终端运动状态的方法及移动终端(String), US9560486B2(String), A method for identifying a motion status of a mobile terminal, and a mobile terminal are provided. The method includes collecting information about multiple wireless local area network (WLAN) access points during each time of scanning, where the information includes a basic service set identifier and signal strength; calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points; and presetting a belief decision threshold and a list orthogonality decision threshold, and comparing the decision thresholds with calculated values to acquire the motion status of the mobile terminal. Therefore, the motion status of the mobile terminal may be acquired without making a change in any hardware on an existing mobile terminal. In addition, the present disclosure is applicable to an area covered by multiple wireless local area network access points.(String), 提供了一种移动终端运动状态的识别方法及移动终端。 该方法包括在每次扫描时收集多个无线局域网(WLAN)接入点的信息,该信息包括基本服务集标识和信号强度; 根据多个WLAN接入点的信息计算置信度值和列表正交度值; 预设置信度判定阈值和列表正交性判定阈值,将判定阈值与计算值进行比较,获取移动终端的运动状态。 因此,无需对现有移动终端的硬件做任何改动,即可获取移动终端的运动状态。 另外,本发明适用于多个无线局域网接入点覆盖的区域。(String), US14/923094(String), 1445788800(Integer), US9560486B2(String), 1485792000(Integer), 1485792000(Integer), 美国(String), 2(Integer), 4(Integer), CN(String), 4(Integer), 13(Integer), CN101627561A | CN101822094A | CN102111434A | CN102355530A | CN1501610A | CN201978444U | US20070018890A1 | US20070183344A1 | US20080207278A1 | US20100248668A1 | US20100255781A1 | US20120004881A1 | US20140141796A1(String), \20230420\2c85b2403ff54aa29d8a472c1ac5b099.png(String), 16(Integer), 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 1. A method for identifying a motion status of a mobile terminal, the method comprising:scanning for wireless local area network (WLAN) access points of the mobile terminal once every specified sampling period;collecting information about multiple WLAN access points that are acquired during each time of scanning, wherein the information comprises a basic service set identifier and signal strength;calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length, wherein the set time window length is n sampling period, wherein n is an integral multiple, wherein the belief value is an average length of WLAN access point lists within the set time window length, and wherein the list orthogonality value is a weighted average of (n−1) orthogonalities that are acquired by separately calculating orthogonality between the last list and previous (n−1) lists within the time window;comparing the calculated belief value with a preset belief decision threshold;comparing the calculated list orthogonality value with a preset list orthogonality decision threshold when the calculated belief value is greater than the preset belief decision threshold;determining that the motion status of the mobile terminal is still when the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold; anddetermining that the motion status of the mobile terminal is driving when the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold.(String), 1.一种移动终端运动状态的识别方法,该方法包括:每隔指定的采样周期扫描一次移动终端的无线局域网(WLAN)接入点;收集每次扫描获取的多个WLAN接入点的信息,该信息包括基本服务集标识和信号强度;根据在设定的时间窗长度内获取的多个WLAN接入点的信息,计算置信值和列表正交值,其中,设定的时间窗长度为n个采样周期,n为整数倍,置信度value为设定时间窗长度内WLAN接入点列表的平均长度,其中列表正交度值为(n-1)个正交度的加权平均,分别计算上一个列表与前(n-)个列表的正交度得到1)在时间窗口内列出;将计算出的置信度值与预设的置信度决策阈值进行比较;当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较;当计算出的列表正交性值小于预设列表正交性判定阈值的最小值时,确定移动终端的运动状态为静止;和当计算出的列表正交性值大于预设列表正交性判定阈值的最大值时,确定移动终端的运动状态为驾驶。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 2. The method according to claim 1, wherein calculating the belief value comprises:multiplying a quantity of multiple WLAN access points acquired during the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; andadding all the average quantities of WLAN access points to acquire the belief value, wherein the average quantities are calculated within the set time window length.(String), 2.根据权利要求1所述的方法,其中计算置信值包括:将每隔指定采样周期扫描获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子,计算出每次扫描后的平均WLAN接入点数量;和将所有WLAN接入点的平均数量相加得到置信值,其中平均数量是在设定的时间窗长度内计算得到的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 3. The method according to claim 1, wherein calculating the list orthogonality value comprises:comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning;acquiring, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value;adding degrees of contribution of all of the non-duplicate WLAN access points;multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution;adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a quantity of WLAN access points;dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, wherein a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; andadding the list orthogonality values of the first time of scanning, the second time of scanning, and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length.(String), 3.根据权利要求1所述的方法,其中计算列表正交值包括:在设置的时间窗长度内,将第一次扫描获取的多个WLAN接入点信息与第二次扫描获取的多个WLAN接入点信息进行比较,得到非重复的WLAN接入点信息在两次扫描中获得的;根据预设的贡献度函数获取每个非重复WLAN接入点的信号强度对列表正交值的贡献度;添加所有非重复WLAN接入点的贡献度;将相加得到的值乘以预设的第二时间维度权重因子,得到平均贡献度;将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到WLAN接入点数量;将平均贡献度除以WLAN接入点数量得到第一次扫描的列表正交度值,其中第二次扫描的列表正交度值是通过比较多个WLAN接入点的信息得到的。将第二次扫描获取的多个WLAN接入点的信息与第三次扫描获取的多个WLAN接入点的信息进行比较,将获取的多个WLAN接入点的信息进行比较,得到第三次扫描的列表正交值在第三次扫描时,使用第四次扫描时获取的多个WLAN接入点的信息,以及(N-1)的列表正交值th获取扫描次数,假设在设定的时间窗长度内,在指定的采样周期内共进行了N次扫描;和将第一次扫描、第二次扫描的列表正交值相加,第(N-1)次th扫描次数获取设定时间窗长度内N次扫描的列表正交值。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 4. The method according to claim 1, further comprising determining that the motion status of the mobile terminal cannot be identified when the calculated belief value is less than the preset belief decision threshold.(String), 4.根据权利要求1所述的方法,还包括当计算出的置信度值小于预设的置信度判定阈值时,确定无法识别移动终端的运动状态。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 5. The method according to claim 1, further comprising:calculating a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length; andcomparing the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold when the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the preset list orthogonality decision threshold value.(String), 5.根据权利要求1所述的方法,还包括:根据在设定时间窗长度内获取的多个WLAN接入点的信息,计算信号波动率;和当计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于预设列表正交性判定阈值的最大值时,将计算出的信号波动率与预设信号波动率判定阈值进行比较。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 6. The method according to claim 5, further comprising:determining that the motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold; anddetermining that the motion status of the mobile terminal is still when the calculated signal fluctuation rate is less than the preset signal fluctuation rate decision threshold.(String), 6.根据权利要求5所述的方法,还包括:当计算出的信号波动率大于预设的信号波动率判定阈值时,确定移动终端的运动状态为步行;和当计算出的信号波动率小于预设的信号波动率判定阈值时,确定移动终端的运动状态为静止。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 7. The method according to claim 5, further comprising:determining that the motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold; anddetermining that the motion status of the mobile terminal is still when the calculated signal fluctuation rate is equal to the preset signal fluctuation rate decision threshold.(String), 7.根据权利要求5所述的方法,还包括:当计算出的信号波动率大于预设的信号波动率判定阈值时,确定移动终端的运动状态为步行;和当计算出的信号波动率等于预设的信号波动率判定阈值时,确定移动终端的运动状态为静止。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 8. The method according to claim 1, further comprising setting a motion status, which occurs for most times in motion statuses of the mobile terminal within several successive time windows, of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows.(String), 8.根据权利要求1所述的方法,还包括将移动终端在连续几个时间窗内的移动终端的运动状态中出现次数最多的运动状态设置为移动终端在连续几个时间窗内的最终运动状态。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 9. A mobile terminal, comprising:a processor;a communication interface;a memory; anda bus,wherein the processor, the communication interface and the memory accomplish mutual communication using the bus,wherein the communication interface is configured to communicate with another device,wherein the memory is configured to store an application, andwherein the processor is configured to execute the application stored in the memory to:scan for wireless local area network (WLAN) access points of the mobile terminal once every specified sampling period, and collect information about multiple WLAN access points that are acquired during each time of scanning, wherein the information comprises a basic service set identifier and signal strength;calculate a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length, wherein the set time window length is n sampling period, wherein n is an integral multiple, wherein the belief value is an average length of WLAN access point lists within the set time window length, and wherein the list orthogonality value is a weighted average of (n−1) orthogonalities that are acquired by separately calculating orthogonality between the last list and previous (n−1) lists within the time window;compare the calculated belief value with a preset belief decision threshold;compare the calculated list orthogonality value with a preset list orthogonality decision threshold when the calculated belief value is greater than the preset belief decision threshold;determine that motion status of the mobile terminal is still when the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold; anddetermine that motion status of the mobile terminal is driving when the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold.(String), 9.移动终端,包括:处理器;通信接口;记忆;和一辆巴士,其中,处理器、通信接口和存储器通过总线实现相互通信,其中,通信接口被配置为与另一设备通信,其中存储器被配置为存储应用程序,并且其中,处理器被配置为执行存储在存储器中的应用程序以:每隔指定的采样周期扫描一次移动终端的无线局域网(WLAN)接入点,并收集每次扫描获取的多个WLAN接入点的信息,该信息包括基本服务集标识和信号强度;根据在设定的时间窗长度内获取的多个WLAN接入点的信息计算置信值和列表正交值,其中,设定的时间窗长度为n个采样周期,n为整数倍,置信度value为设定时间窗长度内WLAN接入点列表的平均长度,其中列表正交度值为(n-1)个正交度的加权平均,分别计算上一个列表与前(n-)个列表的正交度得到1)在时间窗口内列出;将计算出的置信度值与预设的置信度决策阈值进行比较;当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较;当计算出的列表正交性值小于预设列表正交性判定阈值的最小值时,确定移动终端的运动状态为静止;和当计算出的列表正交性值大于预设列表正交性判定阈值的最大值时,确定移动终端的运动状态为正在驾驶。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 10. The mobile terminal according to claim 9, wherein the processor being configured to execute the application to calculate the belief value includes being configured to execute the application to:multiply a quantity of multiple WLAN access points acquired during the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; andadd all the average quantities of WLAN access points to acquire the belief value, wherein the average quantities are calculated within the set time window length.(String), 10.根据权利要求9所述的移动终端,其中处理器被配置为执行应用程序以计算置信度值包括被配置为执行应用程序以:将每指定采样周期扫描获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子,计算出每次扫描后的平均WLAN接入点数量;和将所有WLAN接入点的平均数量相加得到置信值,其中平均数量是在设定的时间窗长度内计算得到的。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 11. The mobile terminal according to claim 9, wherein the processor being configured to execute the application to calculate the list orthogonality value includes being configured to execute the application to:compare, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning;acquire, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value;add degrees of contribution of all of the non-duplicate WLAN access points;multiply a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution;add a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a value of a quantity of WLAN access points;divide the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, wherein a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and a list orthogonality value of the (N−1)th of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; andadd the list orthogonality values of the first time of scanning, the second time of scanning, and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length.(String), 11.根据权利要求9所述的移动终端,其中处理器被配置为执行应用程序以计算列表正交性值包括被配置为执行应用程序以:在设置的时间窗长度内,将第一次扫描获取的多个WLAN接入点信息与第二次扫描获取的多个WLAN接入点信息进行比较,得到非重复的WLAN接入点信息在两次扫描中获得的;根据预设的贡献度函数获取每个非重复WLAN接入点的信号强度对列表正交值的贡献度;添加所有非重复WLAN接入点的贡献度;相加得到的值乘以预设的第二时间维度权重因子,得到平均贡献度;将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到WLAN接入点数量值;将平均贡献度除以WLAN接入点数量得到第一次扫描的列表正交度值,其中第二次扫描的列表正交度值是通过比较多个WLAN接入点的信息得到的。将第二次扫描获取的多个WLAN接入点的信息与第三次扫描获取的多个WLAN接入点的信息进行比较,将获取的多个WLAN接入点的信息进行比较,得到第三次扫描的列表正交值在第三次扫描时,使用第四次扫描时获取的多个WLAN接入点的信息,以及(N-1)的列表正交值th获取扫描次数,假设在设定的时间窗长度内,在指定的采样周期内总共进行了N次扫描;和将第一次扫描、第二次扫描的列表正交值相加,第(N−1)th扫描次数获取设定时间窗长度内N次扫描的列表正交值。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 12. The mobile terminal according to claim 9, wherein the processor is further configured to execute the application to determine that motion status of the mobile terminal cannot be identified when the calculated belief value is less than the preset belief decision threshold.(String), 12.根据权利要求9所述的移动终端,其中处理器,还用于当计算出的置信度值小于预设置信度判定阈值时,执行应用程序判断为无法识别移动终端的运动状态。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 13. The mobile terminal according to claim 9, wherein the processor is further configured to execute the application to calculate a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length, and compare the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold when the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the list orthogonality decision threshold.(String), 13.根据权利要求9所述的移动终端,其中处理器,还用于执行应用,根据设定的时间窗长度内获取的多个WLAN接入点的信息,计算信号波动率,并将计算出的信号波动率与预设的信号波动率判定阈值进行比较当计算出的列表正交性值大于预设的列表正交性判定阈值的最小值且小于列表正交性判定阈值的最大值时。(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 14. The mobile terminal according to claim 13, wherein the processor is further configured to execute the application to determine that motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, and determine that motion status of the mobile terminal is still when the calculated signal fluctuation rate is less than the preset signal fluctuation rate decision threshold.(String), 14.根据权利要求13所述的移动终端,其中处理器还用于执行应用,当计算出的信号波动率大于预设的信号波动率判定阈值时,判断移动终端的运动状态为行走,当计算出的信号波动率大于预设信号波动率阈值时,判断移动终端的运动状态为静止。计算出的信号波动率小于预设的信号波动率判定阈值。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 15. The mobile terminal according to claim 13, wherein the processor is further configured to execute the application to determine that motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, and determine that motion status of the mobile terminal is still when the calculated signal fluctuation rate is equal to the preset signal fluctuation rate decision threshold.(String), 15.根据权利要求13所述的移动终端,其中处理器还用于执行应用,当计算出的信号波动率大于预设的信号波动率判定阈值时,判断移动终端的运动状态为行走,当计算出的信号波动率大于预设信号波动率阈值时,判断移动终端的运动状态为静止。计算出的信号波动率等于预设的信号波动率判定阈值。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:25:59.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185017(Integer), 16. The mobile terminal according to claim 9, wherein the processor is further configured to execute the application to set a motion status, which occurs for most times in motion statuses of the mobile terminal within several successive time windows of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows.(String), 16.根据权利要求9所述的移动终端,其中处理器还用于执行应用程序,将移动终端的连续几个时间窗口内的移动终端的运动状态中出现次数最多的运动状态设置为移动终端在连续的几个时间窗口内的最终运动状态视窗。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.085 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.086 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.087 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185017(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2013/087024, filed on Nov. 13, 2013, which claims priority to Chinese Patent Application No. 201310157676.7, filed on Apr. 28, 2013, both of which are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the communications field, and in particular, to a method for identifying a motion status of a mobile terminal, and a mobile terminal. BACKGROUND [0003]Motion status identification is one of important content of context awareness. With popularization of mobile terminals, intelligent services with better experience may be provided for a user by inferring, using a mobile terminal, a motion status of the user, triggering, according to the motion status of the user, a change in a status or a function of the mobile terminal, and providing for the user an intelligent mobile application, such as personalized recommendation or accurate advertisement push according to an inferred higher-class user situation. In a mobile terminal application scenario, difficulties and challenges of motion status identification are how prepared identification is performed on motion of different users in a complex and changeable environment using sensors built in most mobile terminals and without the help of a function of another additional hardware. In consideration of limited computing, storage and energy resources of a terminal, an algorithm involved in motion status identification is as simple as possible, and a dependent function module cannot generate a large number of extra function overheads. [0004]A user is positioned by means of satellite positioning (for example, a global positioning system (GPS)), and a difference between longitudes and a difference between latitudes within a time interval are converted into a motion speed for indirectly inferring a motion status of the user. This manner requires a satellite positioning function be additionally enabled. Generally, power consumption of a GPS on a mobile terminal is higher; time to first fix is longer; and this manner often cannot be used in a shaded area (for example, indoors or in an underground passage). [0005]A motion status of a user is inferred by means of feature extraction, classification, and other means and according to data collected by an inertial sensor, such as an acceleration sensor or a gyroscope. Accuracy of identification using this method is more greatly affected by a placement position of a mobile phone and is more closely related to a posture and a motion habit of the user; algorithm complexity is generally higher; and a large number of training samples need to be collected in advance. [0006]Standard deviation analysis is performed on wireless signal strength data of a base station on a traditional wireless cellular network, still and motion states are distinguished according to a standard deviation, and then, feature matching is performed on a signal sequence and a waveform in a sample library to distinguish two motion types: “walking” and “driving”. When the two motion types “walking” and “driving” are distinguished, similarity analysis needs to be performed on the waveform in real time. On one hand, calculation complexity is higher, and a challenge is brought to a processing capacity of a mobile terminal. On the other hand, signal samples need to be collected and stored in advance, and when there is a large amount of data in the sample library, a burden is brought to limited storage space of the mobile terminal. SUMMARY [0007]Objectives of embodiments of the present disclosure are to provide a method for identifying a motion status of a mobile terminal, and a mobile terminal, so as to resolve a problem about how a motion status of a mobile terminal is determined. [0008]According to a first aspect, a method for identifying a motion status of a mobile terminal is provided, where the method includes scanning for wireless local area network (WLAN) access points of the mobile terminal once every specified sampling period, and collecting information about multiple WLAN access points that are acquired during each time of scanning, where the information includes a basic service set identifier and signal strength; calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length; comparing the calculated belief value with a preset belief decision threshold; when the calculated belief value is greater than the preset belief decision threshold, comparing the calculated list orthogonality value with a preset list orthogonality decision threshold; if the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold, determining that the motion status of the mobile terminal is still; and if the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold, determining that the motion status of the mobile terminal is driving. [0009]With reference to the first aspect, in a first possible implementation manner of the first aspect, the calculating a belief value includes multiplying a quantity of multiple WLAN access points acquired in the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; and adding all the average quantities of WLAN access points to acquire the belief value, where the average quantities are calculated within the set time window length. [0010]With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the calculating a list orthogonality value includes comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning; acquiring, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value; adding degrees of contribution of all of the non-duplicate WLAN access points; multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution; adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a quantity of WLAN access points; and dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, where a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is obtained by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and so on, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; and adding the list orthogonality values of the first time of scanning, the second time of scanning, . . . , and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length. [0011]With reference to the first aspect, the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the method further includes, if the calculated belief value is less than the preset belief decision threshold, determining that the motion status of the mobile terminal cannot be identified. [0012]With reference to the first aspect, the first possible implementation manner of the first aspect, the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes calculating a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length, where if the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the list orthogonality decision threshold, comparing the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold. [0013]With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes, if the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, determining that the motion status of the mobile terminal is walking; and if the calculated signal fluctuation rate is less than or equal to the preset signal fluctuation rate decision threshold, determining that the motion status of the mobile terminal is still. [0014]With reference to the first aspect or the first possible implementation manner of the first aspect, or with reference to the second possible implementation manner of the first aspect, the third possible implementation manner of the first aspect, the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the method further includes performing determining according to motion statuses of the mobile terminal within several successive time windows, and setting a determined motion status, which occurs for most times in the motion statuses of the mobile terminal, of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows. [0015]According to a second aspect, a mobile terminal is provided, where the mobile terminal provides a collecting unit configured to scan for WLAN access points of the mobile terminal once every specified sampling period, and collect information about multiple WLAN access points that are acquired during each time of scanning, where the information includes a basic service set identifier and signal strength; a calculation unit configured to calculate a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length; a first comparison unit configured to compare the calculated belief value with a preset belief decision threshold; a second comparison unit configured to, when the calculated belief value is greater than the preset belief decision threshold, compare the calculated list orthogonality value with a preset list orthogonality decision threshold; a first determining unit configured to, if the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold, determine that motion status of the mobile terminal is still; and a second determining unit configured to, if the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold, determine that motion status of the mobile terminal is driving. [0016]With reference to the second aspect, in a first possible implementation manner of the second aspect, the step of calculating the belief value by the calculation unit is multiplying a quantity of multiple WLAN access points acquired in the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; and adding all the average quantities of WLAN access points to acquire the belief value, where the average quantities are calculated within the set time window length. [0017]With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the step of calculating the list orthogonality value by the calculation unit is comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning; obtaining, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value; adding degrees of contribution of all of the non-duplicate WLAN access points; multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to obtain an average degree of contribution, adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to obtain a quantity of WLAN access points; and dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning; where a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired the third time of scanning, a list orthogonality value of the third time of scanning is obtained by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and so on, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; and adding the list orthogonality values of the first time of scanning, the second time of scanning, . . . , and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length. [0018]With reference to the second aspect, the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the mobile terminal further includes a third determining unit, where the third determining unit is configured to, if the calculated belief value is less than the preset belief decision threshold, determine that motion status of the mobile terminal cannot be identified. [0019]With reference to the second aspect, the first possible implementation manner of the second aspect, the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, the mobile terminal further includes a calculation subunit, where the calculation subunit is configured to calculate a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length; and the mobile terminal further includes a third comparison unit, where the third comparison unit is configured to, if the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the list orthogonality decision threshold, compare the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold. [0020]With reference to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner of the second aspect, the method further includes a fourth determining unit and a fifth determining unit; the fourth determining unit is configured to, if the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, determine that motion status of the mobile terminal is walking; and the fifth determining unit is configured to, if the calculated signal fluctuation rate is less than or equal to the preset signal fluctuation rate decision threshold, determine that motion status of the mobile terminal is still. [0021]With reference to the second aspect, the first possible implementation manner of the second aspect, the second possible implementation manner of the second aspect, the third possible implementation manner of the second aspect, the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner of the second aspect, the mobile terminal further includes a processing unit, where the processing unit is configured to perform determining according to motion statuses of the mobile terminal within several successive time windows, and set a determined motion status, which occurs for most times in the motion statuses of the mobile terminal, of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows. [0022]Compared with the prior art, the embodiments of the present disclosure provide a method for identifying a motion status of a mobile terminal using a WLAN signal to perform determining and the mobile terminal. A time window length is set, and multiple WLAN access points acquired within the set time window length are collected, such that an application scope of the method is wide, that is, the method is applicable to an area covered by multiple WLAN access points and is not limited by an indoor or outdoor site. According to the method, a calculation process is simple, that is, the motion status of the mobile terminal may be determined simply by calculating a belief value and a list orthogonality value of the multiple WLAN access points, comparing the calculated belief value with a preset belief value, and comparing the calculated list orthogonality value with a preset list orthogonality value. Therefore, implementability of the method is high and the method may be directly applied to a mobile terminal having a WLAN function in the market without making a change in hardware. Because the method has no special requirement on a placement location of the mobile terminal during measurement and is irrelevant to a posture or a motion habit of a user, the method is universal. Because a quantity of feature parameters required in the method is small and a determining method is simple, complexity of the method is lower. In addition, no additional power overhead is required in measurement and operation processes in the method, that is, power consumption of the method is low. BRIEF DESCRIPTION OF DRAWINGS [0023]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0024]FIG. 1 is a flowchart of a method for identifying a motion status of a mobile terminal according to Embodiment 1 of the present disclosure; [0025]FIG. 2 is a schematic diagram of a method for identifying a motion status of a mobile terminal according to Embodiment 1 of the present disclosure; [0026]FIG. 3 is a schematic diagram of a method for identifying a motion status of a mobile terminal within multiple time windows in a combined way according to Embodiment 1 of the present disclosure; [0027]FIG. 4 is a flowchart of another method for identifying a motion status of a mobile terminal according to Embodiment 2 of the present disclosure; [0028]FIG. 5 is a structural diagram of an apparatus of a mobile terminal according to Embodiment 3 of the present disclosure; and [0029]FIG. 6 is a structural diagram of an apparatus of a mobile terminal according to Embodiment 4 of the present disclosure. DESCRIPTION OF EMBODIMENTS [0030]To make the objectives, technical solutions, and advantages of the present disclosure clearer and more comprehensible, the following further describes the present disclosure in detail with reference to the accompanying drawings and embodiments. It should be understood that the embodiments described herein are merely used to explain the present disclosure but are not intended to limit the present disclosure. [0031]The foregoing descriptions are merely exemplary embodiments of the present disclosure, but are not intended to limit the present disclosure. Any modification, equivalent replacement, and improvement made without departing from the spirit and principle of the present disclosure shall fall within the protection scope of the present disclosure. Embodiment 1 [0032]FIG. 1 is a flowchart of a method for identifying a motion status of a mobile terminal according to Embodiment 1 of the present disclosure. As shown in FIG. 1, the method includes the following steps. [0033]Step 101: Scan for WLAN access points of the mobile terminal once every specified sampling period, and collect information about multiple WLAN access points that are acquired during each time of scanning, where the information includes a basic service set identifier and signal strength. [0034]In this step, on the premise that a WLAN function of the mobile terminal is enabled, access points (AP) are scanned for once every specified sampling period Δt, and basic service set identifiers (BSSID) and signal strength of multiple WLAN access points that are measured each time are recorded. To facilitate automatic processing of software, a result of each time of scanning may be recorded in the form of a list. For example, a form of one WLAN access point list is L={, , . . . }, and multiple WLAN access point lists, L1, . . . , Lk, Lk+1, . . . , are acquired during multiple times of scanning. [0035]One time window length T is selected, where the length T is an integral multiple of the sampling period Δt, that is, T=nΔt. Combined analysis is performed on n WLAN access point lists, Li0, Li0+1, . . . , and Li0+n-1, acquired in successive times of scanning within one time window, where a smaller subscript of a list is corresponding to a list older in a time dimension. For example, Li0+n-1 is a result of the latest time of scanning within the set time window length, and Li0 is a result of the earliest historical scanning within the set time window length. [0036]Step 102: Calculate a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length. [0037]In this step, analysis on a WLAN access point list is separately calculating a belief value (recorded as Belief) and a list orthogonality value (recorded as Orth) that are corresponding to a current time window. [0038](1) Belief value: The belief value indicates an average length of WLAN access point lists within a set time window length and expressed in a formula as: [0039]Belief=∑i=0n-1⁢ki⁢Li0+i,⁢s.t.⁢∑i=0n-1⁢ki=1,0<ki<1 [0040]|Li0+i| represents a length of the list Li0+i (that is, a quantity of included access points), and k1 is a weight factor. Preferably, 0⁢∑i=0n-2⁢wi=1,0<wi<1 [0045]|Li0+n-1 ∪ Li0+l| represents a quantity of all access points in Li0n-1 and Li0+l, and a unique BSSID may be used to ensure that duplicate access points are not repeatedly counted. Preferably, 0⁢∑i=0n-2⁢wi=1 [0048]|Li0+n-1 ∩ Li0+i represents a quantity of duplicate access points between Li0+n-1 and Li0+i. [0049]The calculating a list orthogonality value includes comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning; acquiring, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value; adding degrees of contribution of all of the non-duplicate WLAN access points; multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution, adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a quantity of WLAN access points; and dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, where a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and so on, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; and adding the list orthogonality values of the first time of scanning, the second time of scanning, . . . , and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length. [0050]The list orthogonality value reflects an update speed of a list of WLAN signals acquired by several adjacent times of scanning, and higher orthogonality indicates that a user may move at a higher speed. The list orthogonality value is related to a quantity of orthogonal APs in results of several successive times of scanning and related to signal strength. A larger quantity of orthogonal APs indicates a larger list orthogonality value, and higher signal strength of the orthogonal APs also indicates a larger list orthogonality value. The quantity of orthogonal APs refers to a quantity of APs that do not occur at the same time in results of two times of scanning. [0051]Optionally, the method further includes calculating a signal fluctuation rate (recorded as Ed). [0052](3) Signal fluctuation rate: The signal fluctuation rate indicates a status of a change in signal strength of related access points in two adjacent lists within a set time window length, and is measured using an average Euclidean distance: [0053]Ed=∑i=0n-2⁢αi⁢∑APm∈Li0+n-1⋂Li0+i⁢(PLi0+n-1APm-PLi0+iAPm)2Li0+n-1⋂Li0+i,⁢s.t.⁢∑i=0n-2⁢αi=1,0<αi<1 where [0054](PLi0+n-1APm-PLi0+iAPm) represents a difference between strength of related signals from a same access point. Preferably, 0<α1≦α2≦ . . . ≦αn-2<1 may be set, such that an item fresher in a time dimension indicates a larger weight. [0055]A change in signal strength of an AP is determined using a value of a signal fluctuation rate. If the signal fluctuation rate is large, it may be determined that a motion status of a mobile terminal is walking or driving, and if the signal fluctuation rate is small, it may be determined that a motion status of a mobile terminal is still. [0056]Step 103: Compare the calculated belief value with a preset belief decision threshold. [0057]In this step, the comparing the calculated belief value with a preset belief decision threshold includes, if the calculated belief value is less than the belief decision threshold, determining that the motion status of the mobile terminal cannot be identified. [0058]Step 104: When the calculated belief value is greater than the preset belief decision threshold, compare the calculated list orthogonality value with a preset list orthogonality decision threshold. [0059]Step 105: If the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold, determine that motion status of the mobile terminal is still. [0060]Step 106: If the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold, determine that the motion status of the mobile terminal is driving. [0061]Further, when the calculated belief value is grea(String), 相关申请的交叉引用 [0001] 本申请是2013年11月13日提交的国际申请No.PCT / CN2013 / 087024的延续,其要求2013年4月28日提交的中国专利申请No.201310157676.7的优先权,其全部内容通过引用合并于此。 全文参考。 技术领域 [0002] 本发明涉及通信领域,尤其涉及一种识别移动终端运动状态的方法及移动终端。 背景 [0003] 运动状态识别是情境感知的重要内容之一。 随着移动终端的普及,通过使用移动终端推断用户的运动状态,并根据用户的运动状态触发状态或动作的变化,可以为用户提供具有更好体验的智能服务。 移动终端的功能,并根据推断出的更高级别的用户情况为用户提供智能移动应用程序,例如个性化推荐或准确的广告推送。 在移动终端应用场景中,运动状态识别的困难和挑战是如何使用大多数移动终端中内置的传感器在复杂而多变的环境中对不同用户的运动进行准备好的识别,而无需借助其他硬件的功能。 考虑到终端的有限的计算,存储和能量资源,运动状态识别中涉及的算法尽可能简单,并且从属功能模块不能产生大量的额外功能开销。 [0004] 通过卫星定位(例如,全球定位系统(GPS))来对用户进行定位,并且将时间间隔内的经度之间的差和纬度之间的差转换为运动速度,以间接地推断出用户的运动状态。 用户。 这种方式需要额外启用卫星定位功能。 通常,移动终端上GPS的功耗较高; 首次修复的时间更长; 并且这种方式通常不能在阴影区域(例如,室内或地下通道)中使用。 [0005] 借助于特征提取,分类和其他手段并且根据由诸如加速度传感器或陀螺仪的惯性传感器收集的数据来推断用户的运动状态。 使用该方法进行识别的准确性受手机放置位置的影响更大,并且与用户的姿势和运动习惯密切相关。 算法复杂度通常更高; 并且需要提前收集大量的训练样本。 [0006] 对传统无线蜂窝网络中基站的无线信号强度数据进行标准差分析,根据标准差区分静止和运动状态,然后对样本中的信号序列和波形进行特征匹配。 该库可以区分两种运动类型:“行走”和“驾驶”。 当区分“行走”和“行驶”两种运动类型时,需要实时对波形执行相似性分析。 一方面,计算复杂度较高,给移动终端的处理能力带来了挑战。 另一方面,需要预先收集并存储信号样本,并且当样本库中有大量数据时,负担增加了移动终端的有限存储空间。 概要 [0007] 本公开的实施例的目的是提供一种用于识别移动终端的运动状态的方法和一种移动终端,以解决关于如何确定移动终端的运动状态的问题。 [0008] 根据第一方面,提供了一种用于识别移动终端的运动状态的方法,其中,该方法包括:每隔指定的采样时间扫描一次移动终端的无线局域网(WLAN)接入点;以及收集关于多个终端的信息。 在每次扫描期间获取的WLAN接入点,其中的信息包括基本服务集标识符和信号强度; 根据在设置的时间窗口长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交性值; 将计算出的置信度值与预设的置信度决策阈值进行比较; 当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较; 如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止; 如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0009] 结合第一方面,在第一方面的第一种可能的实现方式中,所述计算置信度值包括:将在每个指定采样周期进行的扫描中获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子, 每次扫描后计算平均WLAN接入点数量; 将所有无线局域网接入点的平均数量相加得到置信度值,在设定的时间窗口长度内计算出平均数量。 [0010] 结合第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,所述计算列表正交性值包括:在所述设置的时间窗长度内,比较在所述时间间隔内获取的多个WLAN接入点的信息。 第一次扫描使用第二次扫描期间获取的有关多个WLAN接入点的信息来获取两次扫描期间获取的有关非重复的WLAN接入点的信息; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获得第三次扫描的列表正交性值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0011] 结合第一方面,第一方面的第一种可能的实现方式,或第一方面的第二种可能的实现方式,在第一方面的第三种可能的实现方式中,所述方法还包括:如果计算出的置信度为 小于预设的信念判定阈值,确定不能识别出移动终端的运动状态。 [0012] 结合第一方面,第一方面的第一种可能的实现方式,第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中, 该方法还包括根据在设置的时间窗口长度内获取的关于多个WLAN接入点的信息来计算信号波动率,如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于 在列表正交性判定阈值的最大值之外,将计算出的信号波动率与预设信号波动率判定阈值进行比较。 [0013] 结合第一方面的第四种可能的实现方式,在第一方面的第五种可能的实现方式中,所述方法还包括:如果计算出的信号波动率大于预设信号波动率决策阈值,则确定运动 移动终端的状态为步行; 如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定移动终端的运动状态为静止。 [0014] 结合第一方面或第一方面的第一种可能的实现方式,或结合第一方面的第二种可能的实现方式,第一方面的第三种可能的实现方式,第一方面的第四种可能的实现方式 或第一方面的第五种可能的实现方式,在第一方面的第六种可能的实现方式中,所述方法还包括:根据所述移动终端在多个连续的时间窗内的运动状态进行确定,并设置确定的运动状态; 在移动终端的运动状态中大多数时间出现在移动终端的运动状态中,作为移动终端在几个连续时间窗口内的最终运动状态。 [0015] 根据第二方面,提供了一种移动终端,其中,该移动终端提供收集单元,该收集单元被配置为每隔指定的采样时间扫描一次该移动终端的WLAN接入点,并收集关于在每个接入点期间获取的多个WLAN接入点的信息。 扫描时间,其中信息包括基本服务集标识符和信号强度; 计算单元,用于根据在设定的时间窗口长度内获取的与多个WLAN接入点的信息,计算置信度值和列表正交度值; 第一比较单元,用于将计算出的置信度值与预设的置信度决策阈值进行比较; 第二比较单元,用于当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较; 第一确定单元,用于如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止; 第二确定单元,用于如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0016] 结合第二方面,在第二方面的第一种可能的实现方式中,所述计算单元计算所述置信度值的步骤是将在每个指定采样周期进行的扫描中获取的多个WLAN接入点的数量乘以预设值 第一时间维度权重因子,用于计算每次扫描后WLAN接入点的平均数量; 将所有无线局域网接入点的平均数量相加得到置信度值,在设定的时间窗口长度内计算出平均数量。 [0017] 结合第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,所述计算单元计算列表正交性值的步骤是在设定的时间窗长度内比较多个WLAN的信息。 第一次扫描时获取的接入点,以及第二次扫描时获取的多个WLAN接入点的信息,以获取两次扫描时获取的非重复的WLAN接入点的信息; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加而获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度,然后将非重复的WLAN接入点的数量与在该过程中获取的重复的WLAN接入点的数量相加。 进行两次扫描以获得一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值; 其中,通过将第二次扫描获取的多个WLAN接入点的信息与第三次扫描获取的多个WLAN接入点的信息进行比较,得到第二次扫描的列表正交值。 通过将在第三次扫描期间获取的有关多个WLAN接入点的信息与在第四次扫描期间获取的有关多个WLAN接入点的信息进行比较,等等,获得第三次扫描的正交性值,依此类推, 和(N-1)的列表正交性值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0018] 结合第二方面,第二方面的第一种可能的实现方式,或第二方面的第二种可能的实现方式,在第二方面的第三种可能的实现方式中,所述移动终端还包括第三确定单元, 第三确定单元,如果计算出的置信度值小于预设的置信度判定阈值,则确定无法识别出移动终端的运动状态。 [0019] 结合第二方面,第二方面的第一种可能的实现方式,第二方面的第二种可能的实现方式或第二方面的第三种可能的实现方式,在第二方面的第四种可能的实现方式中, 所述移动终端还包括计算子单元,计算子单元,用于根据所述设定的时间窗长度内获取的所述多个WLAN接入点的信息,计算信号波动率; 所述移动终端还包括第三比较单元,所述第三比较单元,用于如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于列表正交性判定的最大值, 阈值,将计算出的信号波动率与预设信号波动率决策阈值进行比较。 [0020] 结合第二方面的第四种可能的实现方式,在第二方面的第五种可能的实现方式中,所述方法还包括:第四确定单元和第五确定单元; 第四确定单元,用于如果计算出的信号波动率大于预设信号波动率决策阈值,则确定移动终端的运动状态为步行; 第五确定单元,用于如果计算出的信号波动率小于或等于预设信号波动率判定阈值,则确定移动终端的运动状态为静止。 [0021] 结合第二方面,第二方面的第一种可能的实现方式,第二方面的第二种可能的实现方式,第二方面的第三种可能的实现方式,第二方面的第四种可能的实现方式,或第五种 第二方面的可能的实现方式,在第二方面的第六的可能的实现方式中,所述移动终端还包括处理单元,所述处理单元,用于在多个连续的时间窗内根据所述移动终端的运动状态进行确定。 ,并将在移动终端的运动状态中最多出现的确定的运动状态设置为移动终端在几个连续时间窗口内的最终运动状态。 [0022] 相较于现有技术,本发明实施例提供了一种利用无线局域网络信号进行移动终端识别移动终端运动状态的方法。 设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此该方法的应用范围较广,即该方法适用于多个WLAN接入点覆盖的区域,并且 不受室内或室外场所的限制。 根据该方法,计算过程很简单,也就是说,可以通过将多个WLAN接入点的置信度值和列表正交性值与预设值进行比较来简单地确定移动终端的运动状态。 置信度值,并将计算出的列表正交性值与预设列表正交性值进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 附图说明 [0023] 为了更清楚地描述本发明实施例中的技术方案,以下简要介绍用于描述实施例所需的附图。 以下描述中的附图仅示出了本公开的一些实施例,并且本领域普通技术人员仍可以在不付出创造性劳动的情况下从这些附图中得出其他附图。 [0024] 图。 附图说明图1是根据本发明实施例一的识别移动终端运动状态的方法的流程图。 [0025] 图。 图2是根据本发明实施例一的识别移动终端运动状态的方法的示意图; [0026] 图。 图3是根据本发明实施例一的在多个时间窗口内以组合方式识别移动终端的运动状态的方法的示意图; [0027] 图。 图4是根据本发明实施例二的另一种识别移动终端运动状态的方法的流程图; [0028] 图。 图5是根据本发明实施例三的移动终端的装置的结构图; 和 [0029] 图。 图6是根据本发明实施例四的移动终端的装置的结构图。 具体实施方式 [0030] 为了使本发明的目的,技术方案和优点更加清楚和理解,以下结合附图和实施例,对本发明进行进一步详细描述。 应当理解,本文所述实施例仅用于解释本发明,并不用于限制本发明。 [0031] 前述描述仅是本公开的示例性实施例,而无意于限制本公开。 凡在本发明的精神和原则之内,所作的任何修改,等同替换,改进等,均应包含在本发明的保护范围之内。 实施例1 [0032] 图。 图1是根据本公开的实施例1的识别移动终端的运动状态的方法的流程图。 如图1所示。 参照图1,该方法包括以下步骤。 [0033] 步 101 :每个指定的采样周期扫描一次移动终端的WLAN接入点,并收集每次扫描期间获取的多个WLAN接入点的信息,其中包括基本服务集标识符和信号强度。 [0034] 在该步骤中,在使能移动终端的WLAN功能的前提下,每隔规定的采样周期Δt对接入点(AP)进行一次扫描,并对多个WLAN接入点的基本业务集标识(BSSID)和信号强度进行扫描。 每次记录都测量。 为了促进软件的自动处理,可以以列表的形式记录每次扫描的结果。 例如,一个WLAN接入点列表的形式为L = { , ,。 。 。 },以及多个WLAN接入点列表L 1 ,。 。 。 ,L k ,L k+1 ,。 。 。 ,是在多次扫描中获取的。 [0035] 选择一个时间窗长度T,其中长度T是采样周期Δt的整数倍,即,T =nΔt。 对n个WLAN接入点列表Li进行组合分析 0 ,李 0+1 ,。 。 。 和李 0+n-1 在一个时间窗口内连续扫描获得的,其中列表的较小下标对应于在时间维度上较旧的列表。 例如李 0+n-1 是在设定的时间范围内扫描的最新时间的结果, 0 是在设置的时间窗口长度内最早进行历史扫描的结果。 [0036] 步 102 :根据在设置的时间窗长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交性值。 [0037] 在此步骤中,对WLAN接入点列表的分析分别计算与当前时间窗口相对应的置信度值(记录为Belief)和列表正交性值(记录为Orth)。 [0038] (1)置信度:置信度值表示设置的时间范围内的WLAN接入点列表的平均长度,用以下公式表示: [0039] 信仰 = ∑ i = 0 n - 1 ⁢ k i ⁢ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 1 ⁢ k i = 1 , 0 < k i < 1 [0040] | L i 0 +i | 代表列表的长度L i 0 +i (即,所包含的接入点的数量),以及k 1 是一个重量因素。 最好是0 Orth = ∑ i = 0 n - 2 ⁢ w i ⁢ ∑ 美联社 t ∉ ( L i 0 + n - 1 ⋂ L i 0 + i ) ⁢ C ⁡ ( P 美联社 t ) L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 , 0 < w i < 1 [0045] | L i 0 +n-1 ∪ i 0 +l | 表示L中所有接入点的数量 i 0 n-1 和我 i 0 +l ,并且可以使用唯一的BSSID来确保不会重复计算重复的访问点。 最好是0 Orth = 1 - 柯尔 = 1 - ∑ i = 0 n - 2 ⁢ w i ⁢ L i 0 + n - 1 ⋂ L i 0 + i L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 [0048] | L i 0 +n-1 ∩ i 0 +i 表示L之间的重复访问点数量 i 0 +n-1 和我 i 0 +i 。 [0049] 计算列表正交性值包括在设置的时间窗口长度内,将关于在第一次扫描期间获取的多个WLAN接入点的信息与关于在第二次扫描期间获取的多个WLAN接入点的信息进行比较以获取信息。 关于两次扫描中获取的非重复的WLAN接入点; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加而获得的值乘以预设的第二时间维度权重因子以获取平均贡献度,然后将非重复的WLAN接入点的数量和在此期间获取的重复的WLAN接入点的数量相加 进行两次扫描以获取一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获取第三次扫描的列表正交值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0050] 列表正交性值反映通过几次相邻扫描而获取的WLAN信号的列表的更新速度,并且更高的正交性表示用户可以以更高的速度移动。 列表正交值与几次连续扫描的结果中的正交AP的数量有关,并且与信号强度有关。 正交AP的数量越大,列表正交性值越大,正交AP的信号强度越高,列表正交性值越大。 正交AP的数量是指两次扫描的结果中不同时出现的AP的数量。 [0051] 可选地,该方法还包括计算信号波动率(记录为Ed)。 [0052] (3)信号波动率:信号波动率表示在设定的时间窗口长度内两个相邻列表中相关接入点的信号强度变化的状态,并使用平均欧几里德距离来测量: [0053] 埃德 = ∑ i = 0 n - 2 ⁢ α i ⁢ ∑ 美联社 m ∈ L i 0 + n - 1 ⋂ L i 0 + i ⁢ ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 2 L i 0 + n - 1 ⋂ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ α i = 1 , 0 < α i < 1 哪里 [0054] ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 代表来自同一接入点的相关信号强度之间的差异。 最好是0 <α 1 ≦α 2 ≦。 。 。 ≦α n-2 可以设置<1,以便在时间维度上较新的商品表示重量更大。 [0055] 使用信号波动率的值来确定AP的信号强度的变化。 如果信号波动率大,则可以确定移动终端的运动状态为步行或驾驶,并且如果信号波动率小,则可以确定移动终端的运动状态为静止。 [0056] 步 103 :将计算出的置信度值与预设的置信度决策阈值进行比较。 [0057] 在该步骤中,将计算出的置信度值与预设置信度决策阈值进行比较包括:如果计算出的置信度值小于置信度决策阈值,则确定不能识别出移动终端的运动状态。 [0058] 步 104 :当计算出的置信度值大于预设置信度决策阈值时,将计算出的列表正交性值与预设列表正交性决策阈值进行比较。 [0059] 步 105 :如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止。 [0060] 步 106 :如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0061] 此外,当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较。 [0062] 将计算出的列表正交性值与预设列表正交性判定阈值进行比较包括:如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止。 [0063] 此外,如果计算出的列表正交性值大于列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0064] 此外,如果计算出的列表正交性值大于列表正交性判定阈值的最小值并且小于列表正交性判定阈值的最大值,则将计算出的信号波动率与预设信号波动率判定阈值进行比较。 [0065] 该方法还包括:如果计算出的信号波动率大于预设信号波动率决策阈值,则确定移动终端的运动状态为行走; 如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定移动终端的运动状态为静止。 [0066] 如图1所示。 如图2所示。 图2是根据本公开的实施例的识别移动终端的运动状态的示意图。 如图1所示。 参照图2,在信念值大于阈值的前提下,首先使用列表正交性值的第一阈值Orth_th_low和第二阈值Orth_th_high来区分运动状态中的两个极端状态(行驶和静止)。 例如,当计算出的移动终端的列表正交度值小于第一阈值时,确定移动终端的运动状态为静止; 当计算出的所述移动终端的列表正交性值大于所述第二阈值时,确定所述移动终端的运动状态为驾驶中。 对于其余情况,使用信号波动率的阈值区分两个较平缓的运动状态(静止和行走)。 [0067] 需要说明的是,在实际应用中,在上述确定当前时间窗口内的运动状态的过程中,可以同时进行三个特征参数的计算,从而避免了不必要的计算开销,提高了确定速度。 首先,计算置信度值。 假设置信度值小于阈值,则输出直接无效,无需计算列表正交性值和信号波动率两个参数。 如果置信度值大于阈值,则计算列表正交性值。 假设列表正交性值小于第一阈值或大于第二阈值,则对应的输出为“静止”或“驱动”,并且不需要计算信号波动率。 仅当置信度值大于阈值并且列表正交性值在第一阈值和第二阈值之间时才需要计算信号波动率,并且根据信号波动率和阈值之间的关系进行确定。 [0068] 优选地,根据所述移动终端在几个连续的时间窗内的运动状态进行判断,并将确定的运动状态设置为最终运动状态,所述确定的运动状态在所述移动终端的运动状态中最多出现。 在几个连续的时间窗口内移动终端的时间间隔。 [0069] 如图1所示。 如图3所示。 图3是根据本公开实施例的用于以组合方式识别多个时间窗内的移动终端的运动状态的方法的示意图。 为了减少由信号抖动引起的错误确定,可以根据几个连续的时间窗口进一步执行组合确定,以选择在大多数情况下出现的运动状态作为最终结果。 图。 图3是在三个时间窗口内进行组合确定的示意图。 如果在三个连续的时间窗口中出现的运动状态数量大于或等于两次,则认为运动状态是确定的最终结果。 从图2可以看出。 3结合多个时间窗口进行确定可以有效避免频繁跳频。 [0070] 附表1 阈 阈 参数 值 信仰 日 3 Orth 日 — 低 0.2 Orth 日 — 高 0.7 埃德 日 2 [0071] 作为实施例,请参考附表1。首先,每Δt= 16秒(s)扫描一次有关WLAN接入点的信息。 假设在前三次连续扫描中获取的WLAN接入点列表分别为: 大号 1 = { , , , } L2={ , , } L3={ , , } [0072] 然后,分析在扫描期间获取的WLAN接入点列表。 如果使用时间窗口长度T = 48s,则在一个时间窗口内包括三次扫描,即n = 3。 设置三个功能的阈值,如附表1所示。 [0073] 对应于第一时间窗口(包括三个列表,L)的三个参数的计算,即置信度值(记录为Belief),列表正交性值(记录为Orth)和信号波动率(记录为Ed)。 1 ,L 2 , 和我 3 )用作下面的示例。 [0074] (1)信念值:如果加权值k 0 =⅙,k 1 =⅓和k 2 使用= 1/2,置信度值表示为: [0075] 信仰 = ⁢ k 1 · L 1 + k 2 · L 2 + k 3 · L 3 = ⁢ 4 / 6 + 3 / 3 + 3 / 2 = ⁢ 3.2 > 信仰 日 [0076] (2)列表正交值:如果加权值w 0 =⅓和w 1 使用=⅔,贡献度函数C(P 美联社 t )定义为: [0077] C ⁡ ( P 美联社 t ) = { 1 , P ≥ - 60 0.9 , - 80 ≤ P < - 60 0.8 , P < - 80 [0078] 因为L的正交接入点集 3 和我 1 是{ , , },以及L的正交接入点集 3 和我 2 是{ , },列表正交性值为: [0079] Orth = ⁢ w 1 ⁢ ∑ 美联社 t ∉ L 1 ⋂ L 3 ⁢ C ⁡ ( P 美联社 t ) L 1 ⋃ L 3 + w 2 ⁢ ∑ 美联社 l ∉ L 2 ⋂ L 3 ⁢ C ⁡ ( P 美联社 l ) L 2 ⋃ L 3 = ⁢ 1 3 · C ⁡ ( - 55 ) + C ⁡ ( - 71 ) + C ⁡ ( - 70 ) 5 + 2 3 · C ⁡ ( - 60 ) + C ⁡ ( - 70 ) 4 = ⁢ 1 3 · 1 + 0.9 + 0.9 5 + 2 3 · 1 + 0.9 4 = ⁢ 0.33 ∈ ( Orth 低 , Orth 高 ) [0080] (3)信号波动率:加权值α 0 =⅓和α 1 使用=⅔,信号波动率是: [0081] 埃德 = ⁢ 1 3 · ( 77 - 73 ) 2 + ( 92 - 80 ) 2 2 + 2 3 · ( 80 - 77 ) 2 + ( 86 - 80 ) 2 2 = ⁢ 4.345 > 埃德 日 [0082] 根据预设的阈值和上述三个草图值,可以推断出当前时间窗内的运动状态为“行走”。 [0083] 作为另一实施例,首先每Δt= 16s扫描关于WLAN接入点的信息。 假设在前三次连续扫描中获取的WLAN接入点列表分别为: 大号 1 = { , , , } L2={ , } L3={ , , , } [0084] 以相同的方式,使用时间窗口长度T = 48s,即n = 3。 下面显示了特征计算和确定过程。 随附表1中的值仍用作阈值。 [0085] (1)信念值:如果加权值k 0 =⅙,k 1 =⅓和k 2 使用= 1/2,置信度值表示为: [0086] 信仰 = ⁢ k 1 · L 1 + k 2 · L 2 + k 3 · L 3 = ⁢ 4 / 6 + 2 / 3 + 4 / 2 = ⁢ 3.33 > 信仰 日 [0087] (2)列表正交值:如果加权值w 0 =⅓和w 1 =⅔,使用贡献度函数C(P 美联社 t )= 1,列表正交性值为: [0088] Orth = ⁢ 1 - 柯尔 = ⁢ 1 - ( w 0 ⁢ L 1 ⋂ L 3 L 1 ⋃ L 3 + w 1 ⁢ L 2 ⋂ L 3 L 2 ⋃ L 3 ) = ⁢ 1 - ( 1 3 · 1 7 + 2 3 · 1 5 ) = ⁢ 0.822 > Orth 高 [0089] 因此,当前时间窗口内的运动状态为“行驶中”。 [0090] 本公开的实施例提供一种用于使用WLAN信号来执行确定的识别移动终端的运动状态的方法。 设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此该方法的应用范围较广,即该方法适用于多个WLAN接入点覆盖的区域 并且不受室内或室外场所的限制。 根据该方法,计算过程很简单,也就是说,可以通过将多个WLAN接入点的置信度值和列表正交性值与预设值进行比较来简单地确定移动终端的运动状态。 置信度值,并将计算出的列表正交性值与预设列表正交性值进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 实施例2 [0091] 图。 图4为本发明实施例二提供的另一种识别移动终端运动状态的方法的流程图。 如图1所示。 参照图4,该方法包括以下步骤。 [0092] 步 401 :每个指定的采样周期扫描一次移动终端的WLAN接入点,并收集每次扫描期间获取的多个WLAN接入点的信息,其中包括基本服务集标识符和信号强度。 [0093] 在该步骤中,在使能移动终端的WLAN功能的前提下,每隔规定的采样周期Δt对AP进行一次扫描,并记录每次测量的多个WLAN接入点的BSSID和信号强度。 为了促进软件的自动处理,可以以列表的形式记录每次扫描的结果。 例如,一个WLAN接入点列表的形式为L = { , ,。 。 。 },以及多个WLAN接入点列表L 1 ,。 。 。 ,L k ,L k+1 ,。 。 。 ,是在多次扫描中获取的。 [0094] 选择一个时间窗长度T,其中长度T是采样周期Δt的整数倍,即,T =nΔt。 对n个WLAN接入点列表Li进行组合分析 0 ,李 0+1 ,。 。 。 和李 0+n-1 在一个时间窗口内连续扫描获得的,其中列表的较小下标对应于在时间维度上较旧的列表。 例如李 0+n-1 是在设定的时间范围内扫描的最新时间的结果, 0 是在设置的时间窗口长度内最早进行历史扫描的结果。 [0095] 步 402 :根据在预设时间窗口长度内获取的与多个WLAN接入点有关的信息,计算置信度值,列表正交性值和信号波动率。 [0096] 在这一步骤中,对WLAN接入点列表的分析分别计算出三个参数,分别为置信度值(记录为Belief),列表正交性值(记录为Orth)和信号波动率(记录为Ed)。 到当前时间窗口。 [0097] (1)置信度:置信度值表示设置的时间范围内的WLAN接入点列表的平均长度,用以下公式表示: [0098] 信仰 = ∑ i = 0 n - 1 ⁢ k i ⁢ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 1 ⁢ k i = 1 , 0 < k i < 1 [0099] | L i 0 +i |表示列表的长度L i 0 +i (即,所包含的接入点的数量),以及k i 是一个重量因素。 最好是0 Orth = ∑ i = 0 n - 2 ⁢ w i ⁢ ∑ 美联社 t ∉ ( L i 0 + n - 1 ⋂ L i 0 + i ) ⁢ C ⁡ ( P 美联社 t ) L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 , 0 < w i < 1 [0103] | L i 0 +n-1 ∪ i 0 +i | 表示L中所有接入点的数量 i 0 +n-1 , 和我 i 高清+ i ,并且可以使用唯一的BSSID来确保不会重复计算重复的访问点。 最好是0 Orth = 1 - 柯尔 = 1 - ∑ i = 0 n - 2 ⁢ w i ⁢ L i 0 + n - 1 ⋂ L i 0 + i L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 [0106] | L i 0 +n-1 ∩ i 0 +i | 表示L之间的重复访问点数量 i 0 +n-1 和我 i 0 +i 。 [0107] 计算列表正交性值包括预先设置贡献度函数,其中,所述贡献度函数是信号强度的非递减函数,并且指示具有较高信号强度的WLAN接入点的贡献度为: 列表正交性值较高; 在设置的时间窗口长度内,将有关在第一次扫描期间获取的多个WLAN接入点的信息与有关在第二次扫描期间获取的多个WLAN接入点的信息进行比较,以获取有关非重复的WLAN接入点的信息 在两次扫描中获取的; 根据贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值。 通过将关于在第二次扫描期间获取的多个WLAN接入点的信息与关于在第三次扫描期间获取的多个WLAN接入点的信息进行比较,来获取第二次扫描的列表正交值。 通过将在第三次扫描期间获取的有关多个WLAN接入点的信息与在第四次扫描期间获取的有关多个WLAN接入点的信息进行比较,来获取第三次扫描的正交性值,依此类推, 和(N-1)的列表正交性值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0108] (3)信号波动率:信号波动率表示在设定的时间窗口长度内两个相邻列表中相关接入点的信号强度变化的状态,并使用平均欧几里德距离来测量: [0109] 埃德 = ∑ i = 0 n - 2 ⁢ α i ⁢ ∑ 美联社 m ∈ L i 0 + n - 1 ⋂ L i 0 + i ⁢ ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 2 L i 0 + n - 1 ⋂ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ α i = 1 , 0 < α i < 1 哪里 [0110] ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 代表来自同一接入点的相关信号强度之间的差异。 最好是0 <α 1 ≦α 2 ≦。 。 。 ≦α n-2 可以设置<1,以便在时间维度上较新的商品表示重量更大。 [0111] 步 403 :预设置信度判定阈值,列表正交性判定阈值和信号波动率判定阈值。 [0112] 步 404 :确定置信度值是否小于置信度决策阈值。 如果置信度值小于置信度决策阈值,请继续执行步骤 405 。 如果置信度值不小于置信度判定阈值,则执行步骤 406 。 [0113] 步 405 :如果置信度值小于预设的置信度决策阈值,则认为AP太稀疏,因此输出结果无效。 [0114] 步 406 :确定列表正交性值是否小于第一列表正交性判定阈值。 如果列表正交性值小于第一列表正交性判定阈值,则继续执行步骤 407 ,如果列表正交性值不小于第一列表正交性判定阈值,则执行步骤 408 。 [0115] 步 407 :如果列表正交性值小于第一列表正交性判定阈值,则确定移动终端的当前运动状态为静止。 [0116] 步 408 :确定列表正交性值是否大于第二列表正交性判定阈值。 如果列表正交性值大于第二列表正交性判定阈值,则继续执行步骤 409 ,如果列表正交性值不大于第二列表正交性判定阈值,则执行步骤 410 。 [0117] 步 409 :如果列表正交性值大于第二列表正交性判定阈值,则确定移动终端的当前运动状态为驾驶中。 [0118] 步 410 :确定信号波动率是否大于信号波动率值阈值。 如果信号波动率大于信号波动率值阈值,请继续执行步骤 411 ,如果信号波动率不大于信号波动率阈值,执行步骤 412 。 [0119] 步 411 :如果信号波动率大于信号波动率值阈值,请确定移动终端当前的运动状态为步行。 [0120] 步 412 :如果信号波动率小于或等于信号波动率值阈值,请确定移动终端当前的运动状态为静止。 [0121] 本公开的实施例提供一种用于使用WLAN信号来执行确定的识别移动终端的运动状态的方法。 设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此该方法的应用范围较广,即该方法适用于多个WLAN接入点覆盖的区域 并且不受室内或室外场所的限制。 根据该方法,计算过程是简单的,即,可以通过计算多个WLAN接入点的置信度值,列表正交性值和信号波动率来简单地确定移动终端的运动状态。 将计算出的置信度值与预设置信度值进行比较,将计算出的列表正交度值与预设列表正交度值进行比较,并将计算出的信号波动率与预设信号波动率进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 实施例3 [0122] 图。 图5是根据本发明实施例三的移动终端的装置的结构图。 如图1所示。 参照图5,移动终端包括以下单元。 [0123] 收集单元 501 配置为每个指定的采样周期扫描一次移动终端的WLAN接入点,并收集每次扫描期间获取的多个WLAN接入点的信息,所述信息包括基本服务集标识和信号强度。 [0124] 根据该单元,在启用移动终端的WLAN功能的前提下,每隔指定的采样周期Δt扫描AP一次,并且记录每次测量的多个WLAN接入点的BSSID和信号强度。 为了促进软件的自动处理,可以以列表的形式记录每次扫描的结果。 例如,一个WLAN接入点列表的形式为L = { , ,。 。 。 },以及多个WLAN接入点列表L 1 ,。 。 。 ,L k ,L k+1 ,。 。 。 ,是在多次扫描中获取的。 [0125] 选择一个时间窗长度T,其中长度T是采样周期Δt的整数倍,即,T =nΔt。 对n个WLAN接入点列表Li进行组合分析 0 ,李 +1 ,。 。 。 和李 0+n-1 在一个时间窗口内连续扫描获得的,其中列表的较小下标对应于在时间维度上较旧的列表。 例如李 0+n-1 是在设定的时间范围内扫描的最新时间的结果, 0 是在设置的时间窗口长度内最早进行历史扫描的结果。 [0126] 计算单位 502 配置为根据在设置的时间窗长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交度值。 [0127] 根据该单元,对WLAN接入点列表的分析分别计算与当前时间窗口相对应的置信度值(记录为信度)和列表正交性值(记录为Orth)。 [0128] (1)置信度:置信度值表示设置的时间范围内的WLAN接入点列表的平均长度,用以下公式表示: [0129] 信仰 = ∑ i = 0 n - 1 ⁢ k i ⁢ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 1 ⁢ k i = 1 , 0 < k i < 1 [0130] | L i 0 +i | 代表列表的长度L i 0 +i (即,所包含的接入点的数量),以及k i 是一个重量因素。 最好是0 Orth = ∑ i = 0 n - 2 ⁢ w i ⁢ ∑ 美联社 t ∉ ( L i 0 + n - 1 ⋂ L i 0 + i ) ⁢ C ⁡ ( P 美联社 t ) L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 , 0 < w i < 1 [0134] | L i 0 +n-1 ∪ i 0 +i | 表示L中所有接入点的数量 i 0 +n-1 和我 i 0 +i ,并且可以使用唯一的BSSID来确保不会重复计算重复的访问点。 最好是0 Orth = 1 - 柯尔 = 1 - ∑ i = 0 n - 2 ⁢ w i ⁢ L i 0 + n - 1 ⋂ L i 0 + i L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 [0137] | L i 0 +n-1 ∩ i 0 +i | 表示L之间的重复访问点数量 i 0 +n-1 和我 i 0 +i 。 [0138] 计算单元计算列表正交性值的步骤包括:预先设置贡献度函数,其中,贡献度函数是信号强度的非递减函数,表示WLAN接入的贡献度 信号强度较高的点到列表正交值较高; 在设置的时间窗口长度内,将有关在第一次扫描期间获取的多个WLAN接入点的信息与有关在第二次扫描期间获取的多个WLAN接入点的信息进行比较,以获取有关非重复的WLAN接入点的信息 在两次扫描中获取的; 根据贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获取第三次扫描的列表正交值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0139] 可选地,计算单元还包括计算子单元,计算子单元用于计算信号波动率。 [0140] (3)信号波动率:信号波动率表示在设定的时间窗口长度内两个相邻列表中相关接入点的信号强度变化的情况,并使用平均欧几里德距离来测量: [0141] 埃德 = ∑ i = 0 n - 2 ⁢ α i ⁢ ∑ 美联社 m ∈ L i 0 + n - 1 ⋂ L i 0 + i ⁢ ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 2 L i 0 + n - 1 ⋂ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ α i = 1 , 0 < α i < 1 哪里 [0142] ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 代表来自同一接入点的相关信号强度之间的差异。 最好是0 <α 1 ≦α 2 ≦。 。 。 ≦α n-2 可以设置<1,以便在时间维度上较新的商品表示重量更大。 [0143] 第一比较单元 503 配置为将计算出的置信度值与预设置信度决策阈值进行比较。 [0144] 该移动终端还包括第三确定单元 507 ,其中第三确定单元 507 配置为,如果计算出的置信度值小于预设的置信度判定阈值,则确定无法识别出所述移动终端的运动状态。 [0145] 第二比较单元 504 配置为,当计算出的置信度值大于预设置信度决策阈值时,将计算出的列表正交度值与预设列表正交度决策阈值进行比较。 [0146] 第一确定单元 505 设置为,如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止。 [0147] 第二确定单元 506 配置为,如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0148] 该移动终端还包括计算子单元,该计算子单元被配置为根据在设置的时间窗口长度内获取的与多个WLAN接入点有关的信息,计算信号波动率。 [0149] 该移动终端还包括第三比较单元 508 ,其中第三个比较单元 508 配置为,如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于列表正交性判定阈值的最大值,则将计算出的信号波动率与预设信号波动率判定阈值进行比较 。 [0150] 该移动终端还包括第四确定单元 509 第五确定单元 510 。 [0151] 第四确定单元 509 设置为,如果计算出的信号波动率大于预设信号波动率决策阈值,则确定所述移动终端的运动状态为步行。 [0152] 第五确定单元 510 设置为,如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定所述移动终端的运动状态为静止。 [0153] 该移动终端还包括处理单元,该处理单元用于在多个连续的时间窗内根据移动终端的运动状态进行确定,并设置确定的运动状态,该运动状态在移动终端的运动状态中最多发生。 移动终端中的移动终端作为移动终端在几个连续时间窗口内的最终运动状态。 [0154] 本公开的实施例提供了一种移动终端。 移动终端设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此移动终端的应用范围较广,即该方法适用于多个WLAN接入所覆盖的区域 点数,不受室内或室外站点的限制。 根据该方法,计算过程很简单,也就是说,可以通过将多个WLAN接入点的置信度值和列表正交性值与预设值进行比较来简单地确定移动终端的运动状态。 置信度值,并将计算出的列表正交性值与预设列表正交性值进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 实施例4 [0155] 图。 图6是根据本发明实施例四的移动终端的装置的结构图。 参考图。 参见图6。 6是移动终端 600 根据本公开的实施例,并且不限制本公开的实施例中的移动终端的实现。 移动终端 600 包括一个处理器 601 ,一个通讯接口 602 记忆 603 和一辆公共汽车 604 。 [0156] 处理器 601 ,通讯接口 602 以及记忆 603 使用总线完成相互通信 604 。 [0157] 通讯接口 602 配置为与另一个设备通信。 [0158] 处理器 601 配置为执行应用程序。 [0159] 该应用程序可以包括程序代码,其中该程序代码包括计算机操作指令。 [0160] 处理器 601 可以是中央处理单元(CPU),专用集成电路(ASIC)或配置为实现本公开的该实施例的一个或多个集成电路。 [0161] 记忆 603 配置为存储应用程序。 记忆 603 存储器可以包括高速随机存取存储器(RAM),或者可以包括非易失性存储器,例如,至少一个磁盘存储器。 所述应用可以包括:每隔指定的采样周期扫描一次所述移动终端的WLAN接入点;收集每次扫描所获取的多个WLAN接入点的信息,所述信息包括基本服务集标识和信号强度; 根据在设置的时间窗口长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交性值; 将计算出的置信度值与预设的置信度决策阈值进行比较; 当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较; 如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止; 如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0162] 计算置信度值包括:将在每个指定采样周期内进行的扫描中获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子,以计算每次扫描后的WLAN接入点的平均数量; 然后,将所有平均数量和WLAN接入点的总和相加,以获取置信度值,其中在设置的时间窗口长度内计算平均数量。 [0163] 计算列表正交性值包括在设置的时间窗口长度内,将关于在第一次扫描期间获取的多个WLAN接入点的信息与关于在第二次扫描期间获取的多个WLAN接入点的信息进行比较以获取信息。 关于两次扫描中获取的非重复的WLAN接入点; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获取第三次扫描的列表正交值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0164] 该应用还包括:如果计算出的置信度值小于预设的置信度判定阈值,则确定不能识别出移动终端的运动状态。 [0165] 该应用程序还包括:根据在设置的时间窗口长度内获取的关于多个WLAN接入点的信息,以及如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值,则计算信号波动率。 小于列表正交性判定阈值的最大值,将计算出的信号波动率与预设信号波动率判定阈值进行比较。 [0166] 该应用程序还包括:如果计算出的信号波动率大于预设信号波动率决策阈值,则确定移动终端的运动状态为行走; 如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定移动终端的运动状态为静止。 [0167] 该应用程序还包括根据移动终端的运动状态在几个连续的时间窗口内进行确定,并将确定的运动状态设置为最终运动状态,该确定的运动状态在移动终端的运动状态中最多出现一次。 在几个连续的时间窗口内移动终端的时间间隔。 [0168] 本领域普通技术人员可以理解,实施例中方法的全部或部分处理可以通过指令相关硬件的计算机程序(例如处理器)来实现。 程序可以存储在计算机可读存储介质中。 当程序运行时,执行实施例中的方法的处理。 前述存储介质可以包括磁盘,光盘,只读存储器(ROM)或RAM。 [0169] 以上所述仅为本发明的优选实施方式,并不用于限制本发明的保护范围。 凡在本发明的精神和原则之内,所作的任何修改,等同替换,改进等,均应包含在本发明的保护范围之内。 (String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104125021A(String), CN104125021B(String), EP2993947A1(String), EP2993947A4(String), US20160044462A1(String), US9560486B2(String), WO2014176887A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.111 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104125021A(String), CN104125021B(String), EP2993947A1(String), EP2993947A4(String), US20160044462A1(String), US9560486B2(String), WO2014176887A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.112 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9560486B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.122 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104125021A(String), CN104125021B(String), EP2993947A1(String), EP2993947A4(String), US20160044462A1(String), US9560486B2(String), WO2014176887A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.123 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), CN104125021A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.134 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), CN104125021B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.143 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.143 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.143 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), EP2993947A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.153 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), EP2993947A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), US20160044462A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), US9560486B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.184 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270694(Integer), WO2014176887A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9560486B2(String), US9560486B2(String), 1485792000(Integer), 270694(Integer), 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.208 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.209 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.209 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185017(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.210 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.210 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.210 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185017(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185017(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185017(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.268 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 185017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.280 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.282 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for printing document of mobile terminal through printer, and mobile terminal therefor(String), 一种通过打印机打印移动终端文档的方法及其移动终端(String), US20110063663A1(String), A method for printing a document of a mobile terminal without a separate printer setup is provided. The method includes performing a wireless auto-connection between a mobile terminal and a printer located near the mobile terminal, and when the mobile terminal transmits a document to be printed to the printer, the printer finds a computer capable of outputting the document, transmits the document to the computer, and prints the document in response to a print instruction received from the computer. Accordingly, a user can print various documents stored in the mobile terminal wherever a printer is located, even without information of the printer.(String), 提供了一种在没有单独的打印机设置的情况下打印移动终端的文档的方法。 该方法包括在移动终端与位于移动终端附近的打印机之间进行无线自动连接,当移动终端向打印机发送待打印文档时,打印机找到能够输出该文档的计算机,发送 文档到计算机,并响应从计算机接收到的打印指令打印文档。 因此,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档,即使没有打印机的信息。(String), US12/869984(String), 1282838400(Integer), US20110063663A1(String), 1300291200(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 20(Integer), US20020051200A1 | US20020087622A1 | US20020097433A1 | US20030002072A1 | US20060105714A1 | US20060208088A1 | US20070130296A1 | US20080309961A1 | US20100201996A1 | US20130222618A1 | US6369909B1 | US6587835B1 | US6690918B2 | US6798530B1 | US7016062B2 | US7272788B2 | US7460261B2 | US7609402B2 | US7991778B2 | US8050709B2(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185018(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.294 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d586a470c13a4d27ac833da6d3779fb0.png(String), 185018(Integer), d586a470c13a4d27ac833da6d3779fb0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.303 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for printing document of mobile terminal through printer, and mobile terminal therefor(String), 一种通过打印机打印移动终端文档的方法及其移动终端(String), US20110063663A1(String), A method for printing a document of a mobile terminal without a separate printer setup is provided. The method includes performing a wireless auto-connection between a mobile terminal and a printer located near the mobile terminal, and when the mobile terminal transmits a document to be printed to the printer, the printer finds a computer capable of outputting the document, transmits the document to the computer, and prints the document in response to a print instruction received from the computer. Accordingly, a user can print various documents stored in the mobile terminal wherever a printer is located, even without information of the printer.(String), 提供了一种在没有单独的打印机设置的情况下打印移动终端的文档的方法。 该方法包括在移动终端与位于移动终端附近的打印机之间进行无线自动连接,当移动终端向打印机发送待打印文档时,打印机找到能够输出该文档的计算机,发送 文档到计算机,并响应从计算机接收到的打印指令打印文档。 因此,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档,即使没有打印机的信息。(String), US12/869984(String), 1282838400(Integer), US20110063663A1(String), 1300291200(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 20(Integer), US20020051200A1 | US20020087622A1 | US20020097433A1 | US20030002072A1 | US20060105714A1 | US20060208088A1 | US20070130296A1 | US20080309961A1 | US20100201996A1 | US20130222618A1 | US6369909B1 | US6587835B1 | US6690918B2 | US6798530B1 | US7016062B2 | US7272788B2 | US7460261B2 | US7609402B2 | US7991778B2 | US8050709B2(String), \20230420\d586a470c13a4d27ac833da6d3779fb0.png(String), 17(Integer), 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 1. A method for printing, by a printer connected to at least one computer, a document of a mobile terminal, the method comprising the steps ofacquiring document support information from at least one computer connected with the printer;performing a wireless auto-connection procedure with the mobile terminal;receiving a print request including an output target document from the connected mobile terminal;upon receiving the print request, selecting a computer to output the output target document by referring to the acquired document support information; andprinting the output target document in response to a print instruction issued by the selected computer.(String), 1.一种通过连接至少一台计算机的打印机打印移动终端文档的方法,该方法包括的步骤从至少一台与打印机连接的计算机获取文档支持信息;执行与移动终端的无线自动连接程序;从连接的移动终端接收包括输出目标文档的打印请求;接收到打印请求后,参照获取的文档支持信息,选择计算机输出输出目标文档;和响应于所选计算机发出的打印指令打印输出目标文档。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 2. The method as claimed in claim 1, further comprising, when acquiring the document support information from the at least one computer, mapping the at least one computer according to types of documents and storing a result of the mapping in a table.(String), 2.如权利要求1所述的方法,还包括,当从至少一台计算机获取文档支持信息时,根据文档类型对至少一台计算机进行映射,并将映射结果存储在表中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 3. The method as claimed in claim 2, wherein the document support information includes at least one selected from a group consisting of a document type, a network address of the computer, a version of document software installed in the computer, information indicating whether output of the document is available, and a document storage area allocated to the computer.(String), 3.如权利要求2所述的方法,其中文档支持信息包括选自文档类型、计算机的网络地址、计算机中安装的文档软件的版本、文档是否可用的信息、文档存储区中的至少一项分配给电脑。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 4. The method as claimed in claim 1, wherein performing the wireless auto-connection procedure with the mobile terminal comprises:when a request for starting an automatic wireless Local Area Network (LAN) connection procedure is issued, generating and displaying random information used in common with the mobile terminal for the wireless auto-connection; andgenerating and configuring information required for the wireless auto-connection using the random information.(String), 4.如权利要求1所述的方法,其中与移动终端执行无线自动连接过程包括:当发出启动自动无线局域网(LAN)连接过程的请求时,生成并显示与移动终端共同用于无线自动连接的随机信息;和使用随机信息生成和配置无线自动连接所需的信息。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 5. The method as claimed in claim 1, further comprising, when the printer is powered on before the document support information is acquired, multicasting a request for the document support information to the at least one computer connected on a Local Area Network (LAN), according to a discovery protocol.(String), 5.如权利要求1所述的方法,还包括,当在获取文档支持信息之前打印机开机时,根据发现协议向连接在局域网(LAN)上的至少一台计算机组播对文档支持信息的请求。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 6. The method as claimed in claim 1, further comprising, after performing the wireless auto-connection procedure:receiving a printer information request according to a discovery protocol from the mobile terminal;providing the mobile terminal with a response message, the response message including a name of the printer, an Internet Protocol (IP) address of the printer, and port information of the printer;receiving, from the mobile terminal, a request for attribute information of the printer; andtransmitting a response to the request, wherein the response includes the attribute information of the printer.(String), 6.如权利要求1所述的方法,还包括,执行无线自动连接程序后:根据发现协议从移动终端接收打印机信息请求;向移动终端提供响应消息,该响应消息包括打印机的名称、打印机的IP地址和打印机的端口信息;接收移动终端对打印机属性信息的请求;和传送对请求的响应,其中响应包括打印机的属性信息。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 7. The method as claimed in claim 6, wherein the printer attribute information corresponds to information required for constructing a print menu in the mobile terminal, and includes at least one selected from a group consisting of state information of the printer, a type of a document that can be output, and an output-related option.(String), 7.如权利要求6所述的方法,其中打印机属性信息对应移动终端中构建打印菜单所需的信息,包括打印机状态信息、可输出文档类型、输出相关信息中的至少一项。选项。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 8. A method for printing, by a mobile terminal, a document of the mobile terminal through a printer connected with at least one computer, the method comprising the steps of:performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped; andtransmitting, when the wireless auto-connection procedure is completed a print request including an output target document to the printer, in order for the printer to select a target computer by referring to the document information.(String), 8.一种移动终端通过与至少一台计算机连接的打印机打印移动终端文档的方法,该方法包括步骤:执行与打印机的无线自动连接程序,其中打印机管理文档信息,其中映射了根据每个文档类型可用于输出的计算机;和当无线自动连接程序完成时,传送包含输出目标文档的打印请求至打印机,以供打印机参考文档信息选择目标计算机。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 9. The method as claimed in claim 8, wherein performing the wireless auto-connection procedure with the printer comprises:acquiring random information used in common with the printer for the wireless auto-connection when a request for starting an automatic wireless Local Area Network (LAN) connection procedure is issued; andgenerating and configuring information required for the wireless auto-connection using the random information.(String), 9.如权利要求8所述的方法,其中执行与打印机的无线自动连接程序包括:当发出启动无线局域网(LAN)自动连接程序的请求时,获取与打印机共同使用的无线自动连接的随机信息;和使用随机信息生成和配置无线自动连接所需的信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 10. The method as claimed in claim 8 further comprising, after performing the wireless auto-connection procedure:transmitting a request for printer information to the printer according to a discovery protocol; andreceiving a response message, wherein the response message includes a name of the printer, an Internet Protocol (IP) address of the printer, and port information of the printer.(String), 10.如权利要求8所述的方法还包括,执行无线自动连接程序后:根据发现协议向打印机发送对打印机信息的请求;和接收响应消息,其中响应消息包括打印机的名称、打印机的互联网协议(IP)地址和打印机的端口信息。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 11. The method as claimed in claim 10, further comprising, after receiving the response message:requesting the printer to send attribute information of the printer; andreceiving a response to the request, wherein the response includes attribute information of the printer.(String), 11.如权利要求10所述的方法,还包括,收到响应消息后:请求打印机发送打印机的属性信息;和接收对请求的响应,其中响应包括打印机的属性信息。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 12. The method as claimed in claim 11, wherein the printer attribute information corresponds to information required for constructing a print menu in the mobile terminal, and includes at least one selected from a group consisting of state information of the printer, a type of a document that can be output, and an output-related option.(String), 12.如权利要求11所述的方法,其中打印机属性信息对应移动终端中构建打印菜单所需的信息,包括打印机状态信息、可输出文档类型、输出相关信息中的至少一项。选项。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 13. The method as claimed in claim 12, wherein the print request including the output target document includes a print option set through the print menu.(String), 13.如权利要求12所述的方法,其中包括输出目标文档的打印请求包括通过打印菜单设置的打印选项。14、一种移动终端,通过与至少一台计算机连接的打印机输出移动终端的文档,该移动终端包括:无线自动设置模块,用于执行与打印机的无线自动连接程序,其中打印机管理文档信息,其中映射了根据每个文档类型可用于输出的计算机;发现模块,用于对连接的打印机执行发现操作;图形用户界面(GUI),用于提供打印菜单,打印菜单用于选择待输出的目标文档和选择打印选项;和打印代理模块,用于当通过打印菜单指定输出目标文档和打印选项时,向打印机发送包括输出目标文档的打印请求,以使打印机参考文档信息选择目标计算机。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 14. A mobile terminal for outputting a document of the mobile terminal through a printer connected with at least one computer, the mobile terminal comprising:a wireless auto-setup module for performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped;a discovery module for performing a discovery operation with the connected printer;a Graphical User Interface (GUI) for providing a print menu, the print menu being used for selecting a target document to be output and selecting a print option; anda printing agent module for, when the output target document and print option are appointed through the print menu, transmitting a print request including the output target document to the printer for enabling the printer to select a target computer by referring to the document information.(String), 15.如权利要求14所述的移动终端,其中发现模块通过发现协议获取打印机信息,包括打印机的名称、打印机的网际协议(IP)地址和打印机的端口信息,以及其中,发现模块将获取的打印机信息发送给打印代理模块。(String), 0(Integer), 13(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 15. The mobile terminal as claimed in claim 14, wherein the discovery module acquires printer information including a name of the printer, an Internet Protocol (IP) address of the printer, and port information of the printer, by a discovery protocol, andwherein the discovery module transmits the acquired printer information to the printing agent module.(String), 16.如权利要求14所述的移动终端,其中,打印代理模块获取打印机信息后,向打印机请求发送打印机的属性信息,根据请求接收包含打印机属性信息的响应,并将该响应传递给GUI。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 16. The mobile terminal as claimed in claim 14, wherein, after acquiring the printer information, the printing agent module requests the printer to send attribute information of the printer, receives a response comprising attribute information of the printer according to the request, and transfers the response to the GUI.(String), 17.如权利要求16所述的移动终端,其中,GUI基于接收到的打印机属性信息构造打印菜单,打印菜单包括从由打印机的状态信息、可输出的文档的类型、彩色/黑白组成的组中选择的至少一个打印选项设置和水平/垂直设置。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185018(Integer), 17. The mobile terminal as claimed in claim 16, wherein, the GUI constructs the print menu based on the received printer attribute information, the print menu including at least one print option selected from a group consisting of state information of the printer, a type of a document that can be output, color/black & white setup, and horizontal/vertical setup.(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185018(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to an application filed in the Korean Industrial Property Office on Sep. 15, 2009 and assigned Serial No. 10-2009-0087112, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an apparatus and method for printing a document of a mobile terminal, and more particularly to an apparatus and method for enabling a user to print the document through a printer, via wireless communication of the mobile terminal, and without requiring a separate printer setup procedure. [0004]2. Description of the Related Art [0005]Generally, in order for a desktop personal computer (hereinafter, referred to as a computer) to print a document via a printer, a document file, application software capable of reading the document, and driver software suitable for the particular printer model and the operating system are requested. Therefore, when the user issues a document output request, a computer reads and analyzes a document file through application software and generates, through a Graphical Device Interface (GDI) a document image that has a form suitable for a printer to which the document image is to be output. After reading and analyzing the document, the computer transmits data of the document image to the printer through a printer driver, thereby printing the document. [0006]Unlike desktop personal computer environments such as described above, a mobile terminal such as a cellular phone cannot use the same application software as that used in the computer. Since mobile terminals are designed to be carried by users, the performance of mobile terminals is lower than the performance of desktop personal computers, and mobile terminal operating systems are different from desktop computer operating systems in most cases. More specifically, mobile terminals are more limited than desktop personal computers, with respect to implementing application software. Therefore, such mobile environments, dedicated viewer software capable of only viewing documents is used to check various documents. [0007]In order to output a document stored in a mobile terminal, the mobile terminal connects to a computer. To this end, indirect and direct connection schemes are used. The indirect connection scheme includes directly inserting an external storage device into the mobile terminal, copying a desired document into the external storage device, bringing the copied document of the external storage device into the computer, and then outputting the copied document. The direct connection scheme includes outputting the document using a separate data cable or a wireless local area connection scheme. However, using an external storage device or a data cable is inconvenient for a user because the user must perform a connection task, and using a wireless local area connection scheme requires the user to be aware of the way of using software for wireless connection. [0008]As described above, a conventional mobile terminal uses dedicated viewer software in order to read a computer document. However, when using dedicated viewer software, since the number of formats for documents has already been determined, a user of the mobile terminal cannot view a corresponding document if the mobile terminal does not have the same viewer software for supporting a document format of document software, as that in the computer. Document formats may frequently change due to version upgrades according to enhancement of functions of document software. Therefore, if dedicated viewer software is not rapidly updated, the dedicated viewer software may not be used with updated document formats. Although dedicated viewer software is used to address the above-described absence of mobile versions of document-related software, such dedicated viewer software cannot support all document formats used by computers. It is also necessary to install a printer driver in order to print a document. However, since mobile terminals have no fixed printer for usage, unlike computers, a mobile terminal must find and install a suitable printer driver every time a document is to be printed. Even in the above-described method of connecting a mobile terminal and a computer, a user passes through a setup procedure of inputting, step-by-step, information for a wireless communication connection in order to establish a wireless local area communication, which is inconvenient. It is inefficient for a user to input pieces of information items, one-by-one, which is very inconvenient for users who must frequently change setup due to frequent movement. [0009]Therefore, a need exists for a method for enabling a mobile terminal to simply establish a wireless connection with a printer when the mobile terminal is located near the printer, and to print a desired document, even without installing a printer driver for document printing. SUMMARY OF THE INVENTION [0010]Accordingly, the present invention has been made to solve at least the above-mentioned problems occurring in the prior art, and the present invention provides an apparatus and method for printing documents of a mobile terminal, even without application software corresponding to each document and a separate printer setup procedure, such as installing a printer driver or other similar procedures. [0011]In addition, the present invention provides an apparatus and method for enabling the user to easily connect a mobile terminal to a printer using a wireless communication function of the mobile terminal, and to print documents of the mobile terminal using the printer. [0012]In accordance with an aspect of the present invention, there is provided a method for printing, by a printer, a document of a mobile terminal, the printer being connected with at least one computer. The method includes acquiring document support information from at least one computer connected with the printer; performing a wireless auto-connection procedure with the mobile terminal; receiving a print request including an output target document from the connected mobile terminal; selecting a computer to output the output target document by referring to the acquired document support information when receiving the print request; and printing the output target document in response to a print instruction issued by the selected computer. [0013]In accordance with another aspect of the present invention, there is provided a method for printing, by a mobile terminal, a document of the mobile terminal through a printer connected with at least one computer. The method includes performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped; and transmitting a print request including an output target document to the printer in order for the printer to select a target computer by making reference to the document information when a connection with the printer is completed. [0014]In accordance with another aspect of the present invention, there is provided a mobile terminal for outputting a document of the mobile terminal through a printer connected with at least one computer. The mobile terminal includes a wireless auto-setup module for performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped; a discovery module for performing a discovery operation with the connected printer; a Graphical User Interface (GUI) for providing a print menu, the print menu being used for selecting a target document to be output and selecting a print option; and a printing agent module for, when the output target document and print option are appointed through the print menu, transmitting a print request including the output target document to the printer for enabling the printer to select a target computer by referring to the document information. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0016]FIG. 1 is a block diagram illustrating a system for network printing according to an embodiment of the present invention; [0017]FIG. 2 is a flowchart illustrating a printing procedure according to an embodiment of the present invention; [0018]FIG. 3 is an operational flowchart further illustrating a discovery and printable document registration procedure illustrated in FIG. 2, according to an embodiment of the present invention; [0019]FIGS. 4 and 5 are operational flowcharts further illustrating a wireless auto-connection procedure illustrated in FIG. 2 according to an embodiment of the present invention; and [0020]FIG. 6 is an operational flowchart further illustrating a discovery and document output procedure between a mobile terminal and a printer illustrated in FIG. 2, according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS [0021]Hereinafter, various embodiments of the present invention are described with reference to the accompanying drawings. In the following description, the same elements are designated by the same reference numerals although they are shown in different drawings. In addition, in the following description of the present invention, a detailed description of known functions and configurations incorporated herein are omitted where a detailed description thereof may make the subject matter of the present invention unclear. [0022]The present invention provides a method for printing a document of a mobile terminal, even without a separate printer setup procedure. To this end, an embodiment of the present invention includes performing a wireless auto-connection between a mobile terminal and a printer located near the mobile terminal, and when the mobile terminal transmits a document to be printed to the printer, allowing the printer to find a computer capable of outputting the document and to transmit the document to the computer. Thereafter the printer prints the document in response to a print instruction received from the computer. Accordingly, the user can print various documents stored in the mobile terminal wherever a printer is located, even without information of the printer. [0023]FIG. 1 is a block diagram illustrating a system for network printing according to an embodiment of the present invention. As illustrated in FIG. 1, a system for printing a document of a mobile terminal includes a mobile terminal 10, a printer 20 for printing documents, and at least one computer 30, 40, and 50 connected with the printer 20 by a local area network (LAN). [0024]The mobile terminal 10, which may be a cellular phone or another similar device, performs a wireless connection operation with the adjacent printer 20 using a wireless local area communication scheme, and transmits a document to be printed to the printer 20 while sending a print request when the mobile terminal 10 is connected with the printer 20. The mobile terminal 10 includes a wireless auto-setup module 102, a discovery module 104, a printing agent module 106, and a Graphical User Interface (GUI) 108. [0025]The wireless auto-setup module 102 functions configure a wireless auto-connection between the mobile terminal 10 and the printer 20. [0026]The discovery module 104 finds a printer located near the mobile terminal 10. The discovery module 104 multicasts a printer discovery request, and then obtains a name, an Internet Protocol (IP) address, port information, etc. of a printer targeted for connection from a response to the discovery request when receiving the response. In the present example, the mobile terminal 10 obtains information form the printer 20. The information of the printer 20, obtained as described above, is used to transmit a document to be printed to the printer 20. [0027]The printing agent module 106 communicates with a printing manager module 114 of the printer 20, and transmits/receives and manages various state information of the printer 20. More specifically, the printing agent module 106 manages state information of the wirelessly-connected printer 20, such as an online state, an offline state, a power on/off state, a paper feed state, etc. The printing agent module 106 also issues a document print request to the printer 20, and checks whether a document to be printed can be printed by inquiring the printer 20 for information about whether the printer 20 can print the document and receiving a response to the inquiry. The printing agent module 106 requests and acquires information on various attributes, e.g., the number of copies, a paper type, a page, color/black & white, etc., that are used in printing. The printing agent module 106 transmits acquired attribute information to the GUI 108. When print option information and a print target document is selected by the user through the GUI 108, the printing agent module 106 transmits the print option information together with the print target document to the printer 20. [0028]Based on attribute information received from the printing agent module 106, the GUI 108 provides a user with information on the state of a wirelessly-connected printer, a selected number of copies, a selected paper, whether the printer can print a document, and other configurable print options. The user can also select a print-target document through the GUI 108. [0029]The printer 20 includes a wireless auto-setup module 110, a discovery module 112, and the printing manager module 114. [0030]The wireless auto-setup module 110 configures a wireless auto-connection with the mobile terminal 10, similarly to the wireless auto-setup module 102 of the mobile terminal 10. Such a wireless auto-connection procedure will be described in detail hereinbelow. [0031]Similarly to the discovery module 104 of the mobile terminal 10, the discovery module 112 provides a response including information on its own name. IP address, port, etc. upon receiving the discovery request from the mobile terminal 10. [0032]The printing manager module 114 manages target computers 30, 40, and 50 capable of outputting documents through the current printer 20 in the form of a table by mapping the computers 30, 40, and 50 according to types of documents. Such a table may have a structure as illustrated in Table 1 below, but the present invention is not limited thereto. TABLE 1TargetOutputType ofcomputerSoftwareavailable/AllocatedNo.documentaddressversionunavailablearea (Free)1doc192.168.0.107.0Output115 GBavailable2doc192.168.0.155.0Output 50 MBunavailable3xls192.168.0.1107.0Output663 MBavailable4ppt192.168.0.107.0Output115 GBavailable5gul192.168.0.2012  Output800 MBavailable............... [0033]As shown in Table 1, contents of the table include document support information, such as a type of each document (i.e., a file extension), a network address of each computer connected with the printer 20 in a local area network, a version of each document software installed in each computer, information regarding whether document output is available, and information regarding a document storage area allocated to each computer, etc. [0034]The printing manager module 114 also receives a document requested for printing by the user, from the printing agent module 106 of the mobile terminal 10, finds a computer capable of outputting the received document by referring to a table such as Table 1, and then transmitting the received document to the found computer. [0035]As described above, a printer auto-connected with a mobile terminal prints a document to be printed through a computer corresponding to the document among computers connected with the printer by a network, so that the mobile terminal can print a desired document, without installing a printer driver and application software corresponding to each document. [0036]The first computer 30 includes a discovery module 120, a print control module 122, a document control module 124, and a storage 126. The following description of the configuration of the first computer 30 is provided as an example; the configuration and operation of the second and third computers 40 and 50 are the same as those of the first computer 30. [0037]The discovery module 120 performs a discovery operation of the first computer 30 to find the printer 20. The discovery module 120 also registers information regarding types of documents that the first computer 30 can output, a network address, an area allocated to accommodate documents, etc., which are collected by the document control module 124 of the first computer 30 that is a local computer, with the printing manager module 114 of the printer 20. [0038]The document control module 124 searches for document software installed in the first computer 30, and manages types of documents that can be output by the first computer 30. In the present example, information managed by the document control module 124 includes a type of each document (i.e., a file extension), a name of each software, a version of each software, an installation position of each software, etc. Such management information may have a table structure as illustrated in Table 2 below, but the present invention is not limited thereto. TABLE 2Type ofNo.documentNameVersionPosition of software1docMS Word7.0C:\Program Files\Word.exe2xlsMS Excel7.0C:\Program Files\Excel.exe3pptMS PowerPoint7.0C:\Program Files\Powerpoint.exe4gulHunMinJeongEum12  C:\Program Files\Hun.exe5hwpHangul20072007   C:\Program Files\Hwp.exe............... [0039]The document control module 124 also receives an output target document and an output option set by the user from the printing manager module 114 of the printer 20, and stores the received output target document and output option in the storage 126. In addition, the document control module 124 performs document security-related operations, such as deletion, copy protection, modulation protection, etc., or a document [0040]The print control module 122 applies the received output option through an output function of document software, and controls the printer 20 to print the document. [0041]FIG. 2 is a diagram schematically illustrating a printing procedure according to an embodiment of the present invention. More specifically. FIG. 2 illustrates a procedure in which, when the mobile terminal 10 wirelessly auto-connects with the printer 20 and transmits a document to be printed to the printer 20, the printer 20 finds a computer corresponding to the document and requests the found computer to print the document. [0042]Referring to FIG. 2, when the printer 20 is powered on, the printer 20 performs a discovery operation of searching for one or more computers 30 and 40 connected by a LAN using a predetermined discovery protocol, identifies documents that can be output from the searched computers 30 and 40, and registers documents that can be output from each computer 30 and 40 in steps 200 and 205. The procedure of performing a discovery operation between the printer and the computer and registering documents that can be output in steps 200 and 205 is described detail hereinbelow with reference to FIG. 3. [0043]In step 210, a wireless auto-connection procedure is performed between the mobile terminal 10 and the printer 20. According to an embodiment of the present invention, a method for easily achieving a wireless connection is provided for improving convenience for a user. Such a wireless auto-connection procedure is described hereinbelow with reference to FIGS. 4 and 5. FIGS. 4 and 5 are flow diagrams explaining a wireless auto-connection procedure in FIG. 2 according to an embodiment of the present invention. [0044]When the mobile terminal 10 and the printer 20 have been connected with each other through step 210, a discovery operation is performed in step 215. Through the discover operation, the mobile terminal 10 can obtain attribute information of the printer 20, and can report a state of the printer 20 based on the obtained attribute information. When the user of the mobile terminal 10 has selected a print option and a document to be printed, the mobile terminal 10 transmits the document to be printed to the printer 20 in step 220. In the present example, a print option selected by the user is transmitted, together with the document, and the printer 20 finds a computer capable of outputting the document by referring to a table such as Table 1. If the printer 20 has found the second computer 40 as a computer corresponding to the document (i.e., capable of outputting the document), the printer 20 transmits the document to the second computer 40 in step 225. The second computer 40 transmits an output instruction to the printer 20 in step 230, so that the printer 20 prints the document. [0045]As described above, according to an embodiment of the present invention, the printer 20 directly finds a target computer suitable for document output among computers connected with the printer 20 by a LAN, and requests the found computer to output a document. Accordingly, the mobile terminal 10 is not required to install a separate printer driver to use the printer 20, and can print various types of documents stored in the mobile terminal 10 because a print request is sent to a computer having application software corresponding to a document to be printed, among computers connected with the printer 20 by a LAN. [0046]In order to print various types of documents, as described above, the printer 20 should be aware of information regarding documents supported by each computer 30, 40, and 50. For this reason, according to an embodiment of the present invention, a procedure of performing a discovery operation between a printer and a computer and registering documents that can be output is provided, as described in steps 200 and 205. Such a procedure is described as follows with reference to FIG. 3, wherein an operation performed between the printer 20 and the first and second computers 30 and 40 is explained as an example. [0047]In step 300, the discovery module 112 of the printer 20 multicasts a request signal for requesting each computer 30 and 40 to provide information regarding documents that can be output by the first and second computers 30 or 40, to the computers 30 and 40 connected by a LAN using a discovery protocol. The printer 20 transmits such a request in order to identity document output support information for each of the first and second computers 30 and 40. The request is transmitted to the discovery modules 120 and 130 of the first and second computers 30 and 40, respectively. Each discovery module 120 and 130 inquires each document control module 124 and 134, respectively, about a list of printable documents in steps 305 and 310, so that each of document control modules 124 and 134 acquires application information in steps 315 and 320, respectively. The application information represents document information, including types of documents supported by each computer, the version of document software installed in each computer, whether output is available or unavailable, and a document allocation area that can be accommodated. Thereafter, when each document control module 124 and 134 transmits the document information to each discovery module 120 and 130 in steps 335 and 340, each discovery module 120 and 130 generates and transmits a response message including the document information to the printer 20 in steps 345 and 350. In the present example, the response message includes a network address, in addition to the document information. [0048]As described above, each computer 30 and 40 provides the printer 20 with document support information, including types and versions of documents supported by the computer, a document allocation area that can be accommodated, whether output is available or unavailable, a network address, etc., using a discovery protocol, in advance in response to a printable document information request. If a third computer 50 is powered on after the discovery operation has been completed, the discovery module of the third computer 50 may directly register information regarding documents supported by the third computer 50 with a previously registered printer 20. [0049]When the printer 20 receives response messages including each piece of document information from each of first and second computers 30 and 40 through the aforementioned steps, the printer 20 generates a table such as Table 1 based on each piece of received document information. The table is used to find a computer that can output a document received from the mobile terminal 10. [0050]According to an embodiment of the present invention, a method for enabling the user to easily connect the mobile terminal 10 and the printer 20 using a Wireless Auto Setup procedure, i.e. a wireless auto-connection setup procedure is provided. Such a wireless auto-connection procedure corresponding to step 210 in FIG. 2 is described in detail as follows with reference to FIGS. 4 and 5. [0051]FIG. 4 is a diagram illustrating a wireless auto-connection procedure using a Wireless Fidelity (WiFi) scheme among wireless local area communication schemes, wherein a Service Set IDentifier (SSID) is required for WiFi communication between the mobile terminal 10 and the printer 20, a security key is required for authentication and encryption, an IP address must be set for IP communication, and a Wired Equivalent Privacy (WEP) key value is required, since authentication and encryption are performed in a WEP scheme. According to an embodiment of the present invention, a scheme of automatically generating and setting up all the information required for wireless connection is used. Specifically, an SSID, a security key, an IP address are automatically generated using the same information input by a user between the mobile terminal 10 and the printer 20. According to alternative embodiments of the present invention, random information may be used instead of the same information. In this case, the random information may be a random number that is randomly generated in the mobile terminal 10 and the printer 20. Through this procedure, it is possible to conveniently and automatically connect the mobile terminal 10 to the printer 20 without requiring a user to input each piece of information for wireless LAN connection every time. Due to the characteristics of random information that changes for every connection attempt, it is possible to obtain a more enhanced security characteristic. [0052]Referring to FIG. 4, the mobile terminal 10 and the printer 20 execute the same wireless connection software, in which a WiFi connection setup begins in the mobile terminal 10 and the printer 20, respectively, according to a user input. When initiation of such a wireless LAN auto-connection procedure is requested, the printer 20 generates and displays random information that is used in common with the mobile terminal 10, on a display unit of the printer 20 for the wireless auto-connection, in step 400. The mobile terminal 10 displays a random number on the display unit of the printer 20, and receives user input of the random number of the printer 20 in step 405. Such a random number is used to generate and set up information required for a wireless auto-connection. Specifically, as shown in steps 410 and 415, an SSID, a WEP, etc. is automatically generated and set up with the respective random numbers using the same hash function, thereby completing a WiFi connection. [0053]FIG. 5 is a diagram illustrating a wireless auto-connection procedure using a BLUETOOTH® (BT) scheme among wireless local area communication schemes, wherein each of the mobile terminal 10 and printer 20 generates a device name and a Personal Identification Number (PIN) code with a random number, such as in FIG. 4, using the same hash function. When a Bluetooth connection setup begins in the mobile terminal 10 and the printer 20, the printer 20 generates and outputs a random number in step 500, and then the user sees and inputs the random number through the mobile terminal 10 in step 505. Then, the printer 20 performs a device name setup procedure and a PIN code auto-generation/setup procedure using the random number in steps 510 and 515, respectively, while the mobile terminal 10 performs a printer discovery operation and a PIN code auto-generation/setup procedure using the random number in steps 520 and 525, respectively. Accordingly, the user is only required to input a random number in order to automatically achieve a wireless connection between the mobile terminal 10 and the printer 20. [0054]Hereinafter, a discovery and document output procedure between the mobile terminal and the printer, which corresponds to steps 215 to 230 in FIG. 2, is described in detail as follows with reference to FIG. 6. [0055]Referring to FIG. 6, a user may begin a network printing function through a “print” menu provided by the GUI 108. When such a beginning request is input to the mobile terminal 10, the discovery module 104 of the mobile terminal 10 executes a discovery protocol in step 600, thereby requesting a printer discovery from the discovery module 112 of the printer 20. For such a request, the discovery module 104 of the mobile terminal 10 multicasts a DISCOVERY_PRINTER message. Upon receiving such a DISCOVERY_PRINTER message, the printer 20 transmits a RESPONSE_PRINTER message, which is a response message including printer information, such as its own printer name, IP address, port information, etc., to the discovery module 104 of the mobile terminal 10 in step 605. The discovery module 104 transmits the printer information, which has been acquired through such a discovery procedure, to the printing agent module 106 in step 610. [0056]The GUI 108 transmits a PRINTING_CAPABILITY_REQUEST message for requesting attribute information of the printer 20 from the printing agent module 106 in step 615. Such an attribute information request is used to prepare a “print” menu, which enables the user to check the state of a printer, and then to configure a desired option. [0057]Accordingly, the printing agent module 106 transmits the PRINTING_CAPABILITY_REQUEST message to the printing manager module 114 of the printer 20 in step 620 in order to request attribute information. The printing manager module 114 responds by transmitting a PRINTING_CAPABILITY_RESPONSE message corresponding to the attribute information request in step 625. Such a response message includes attribute information requested by the mobile terminal 10. Here, the attribute information represents various information related to printing, and includes types of printable documents, the state of the printer 20, and information on various options which can be set. [0058]Upon receiving the PRINTING_CAPABILITY_RESPONSE message, the printing agent module 106 transfers the PRINTING_CAPABILITY_RESPONSE message to the GUI 108, in step 630. The GUI 108 provides a “print” menu based on received attribute information. Such a “print” menu includes various option functions, including state information of the printer, types of printable documents, color/black & white setup options, horizontal/vertical setup options, etc. When a print target document and various print options have been appointed through the use of the “print” menu, the GUI 108 transmits the print target document to the printing agent module 106 using a SELECT_DOCUMENT message in step 635. The printing agent module 106 combines and transmits the document and the appointed print options through the use of a PRINT_REQUEST message in step 640. [0059]Through such a PRINT_REQUEST message, the print target document, which has been combined together with the appointed print options, is transmitted to the printing manager module 114 of the printer 20. The printing manager module 114 selects a computer capable of outputting the document by referring to a table such as Table 1 in step 642. More specifically, the printer 20 compares a type of a received document, a capacity of the received document, a right of use, etc. with corresponding information in a document-computer mapping table such as Table 1, and selects a computer capable of outputting the received document. When the printer 20 selects the first computer 30, the printing manager module 114 transmits a PRINT_REQUEST message to th(String), 优先 [0001] 本申请根据 35 U.S.C. §119(a) 于 2009 年 9 月 15 日在韩国工业产权局提交并指定序列号为 10-2009-0087112 的申请,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明总体上涉及一种用于打印移动终端文档的装置和方法,更具体地涉及一种使用户能够通过移动终端的无线通信通过打印机打印文档而无需请求的装置和方法。 单独的打印机设置程序。 [0004] 2.相关技术的描述 [0005] 通常,为了使台式个人计算机(以下简称计算机)通过打印机打印文档,文档文件、能够读取该文档的应用软件以及适合特定打印机型号和操作的驱动软件。 系统被要求。 因此,当用户发出文档输出请求时,计算机通过应用软件读取并分析文档文件,并通过图形设备接口(GDI)生成适合打印机格式的文档图像。 被输出。 计算机读取并分析文档后,通过打印机驱动程序将文档图像的数据传输至打印机,从而打印文档。 [0006] 与如上所述的台式个人计算机环境不同,诸如蜂窝电话的移动终端不能使用与在计算机中使用的应用软件相同的应用软件。 由于移动终端是为用户携带而设计的,因此移动终端的性能低于台式个人电脑的性能,并且移动终端操作系统在大多数情况下与台式电脑操作系统不同。 更具体地,移动终端在实现应用软件方面比台式个人计算机更受限制。 因此,在这种移动环境下,只能查看文档的专用查看器软件被用来检查各种文档。 [0007] 为了输出存储在移动终端中的文档,移动终端连接到计算机。 为此,使用了间接和直接连接方案。 间接连接方案包括直接将外部存储设备插入移动终端,将需要的文件复制到外部存储设备中,将复制的外部存储设备的文件带入计算机,然后将复制的文件输出。 直接连接方案包括使用单独的数据线或无线局域网连接方案输出文档。 然而,使用外部存储设备或数据线对于用户来说是不方便的,因为用户必须执行连接任务,并且使用无线局域网连接方案需要用户了解使用软件进行无线连接的方式。 [0008]如上所述,传统的移动终端使用专用的浏览器软件来阅读计算机文档。 但是,在使用专用的查看器软件时,由于文档的格式数量已经确定,如果移动终端没有相同的支持文档软件的文档格式的查看器软件,则移动终端的用户将无法查看对应的文档。 ,就像电脑里的一样。 随着文档软件功能的增强,文档格式可能会因版本升级而频繁变化。 因此,如果不快速更新专用查看器软件,则专用查看器软件可能无法与更新的文档格式一起使用。 尽管使用专用查看器软件来解决上述缺少移动版本的文档相关软件的问题,但是这样的专用查看器软件不能支持计算机使用的所有文档格式。 还需要安装打印机驱动程序才能打印文档。 但是,由于移动终端没有固定的打印机可供使用,与电脑不同,移动终端每次要打印文档时都必须寻找并安装合适的打印机驱动程序。 即使在上述连接移动终端和计算机的方法中,用户通过逐步输入用于无线通信连接的信息的设置过程以建立无线局域网通信,这是 不方便。 一条一条的信息输入对于用户来说效率低下,对于因频繁移动而必须频繁更改设置的用户来说非常不方便。 [0009] 因此,需要一种方法使移动终端能够在移动终端位于打印机附近时简单地与打印机建立无线连接,并打印所需的文档,甚至无需安装用于文档打印的打印机驱动程序。 发明内容 [0010] 相应地,本发明是为了至少解决现有技术中存在的上述问题而提出的,本发明提供了一种移动终端的文档打印装置和方法,即使没有与每个文档对应的应用软件和 单独的打印机设置程序,例如安装打印机驱动程序或其他类似程序。 [0011] 此外,本发明提供了一种设备和方法,用于使用户能够使用移动终端的无线通信功能轻松地将移动终端连接到打印机,并使用打印机打印移动终端的文档。 [0012] 根据本发明的一个方面,提供了一种通过打印机打印移动终端文档的方法,该打印机与至少一台计算机连接。 该方法包括从至少一台与打印机连接的计算机获取文档支持信息; 执行与移动终端的无线自动连接程序; 从连接的移动终端接收包括输出目标文档的打印请求; 在接收到打印请求时,参照获取的文档支持信息,选择计算机输出输出目标文档; 响应于被选择的计算机发出的打印指令打印输出目标文档。 [0013] 根据本发明的另一方面,提供了一种移动终端通过与至少一个计算机连接的打印机打印移动终端的文档的方法。 该方法包括与打印机执行无线自动连接程序,其中打印机管理文档信息,其中映射了根据每个文档类型可用于输出的计算机; 当与打印机的连接完成时,向打印机发送包括输出目标文档的打印请求,以便打印机通过参考文档信息来选择目标计算机。 [0014]根据本发明的另一方面,提供了一种移动终端,用于通过与至少一台计算机连接的打印机输出移动终端的文档。 移动终端包括无线自动设置模块,用于执行与打印机的无线自动连接过程,其中打印机管理文档信息,其中根据每个文档类型映射了可用于输出的计算机; 发现模块,用于对连接的打印机执行发现操作; 图形用户界面(GUI),用于提供打印菜单,打印菜单用于选择待输出的目标文档和选择打印选项; 打印代理模块,用于当通过打印菜单指定输出目标文档和打印选项时,向打印机发送包括输出目标文档的打印请求,以使打印机参考文档信息选择目标计算机。 附图的简要说明 [0015] [0015] 通过以下结合附图的详细描述,本发明的上述及其他方面、特征和优点将更加明显,其中: [0016] 图1为本发明一实施例的网络打印系统的方块图。 [0017] 图2是表示本发明的一个实施方式的打印步骤的流程图。 [0018] 图3是进一步说明根据本发明实施例的图2中说明的发现和可打印文档注册过程的操作流程图; [0019] 图4和图5是进一步说明根据本发明实施例的图2中所示的无线自动连接过程的操作流程图; 和 [0020] 图6是进一步图示根据本发明实施例的图2所示的移动终端和打印机之间的发现和文档输出过程的操作流程图。 具体实施方式 [0021] 在下文中,将参考附图描述本发明的各种实施例。 在下面的描述中,尽管相同的元件在不同的附图中示出,但它们由相同的附图标记表示。 此外,在本发明的以下描述中,省略了对并入本文的已知功能和配置的详细描述,其中对其的详细描述可能使本发明的主题不清楚。 [0022] 本发明提供了一种打印移动终端文档的方法,甚至不需要单独的打印机设置过程。 为此,本发明实施例包括在移动终端和位于移动终端附近的打印机之间进行无线自动连接,并且当移动终端将待打印的文档发送到打印机时,允许打印机发现 能够输出文档并将文档传输到计算机的计算机。 此后打印机响应从计算机接收到的打印指令打印文档。 因此,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档,即使没有打印机的信息。 [0023] 图1是示出根据本发明实施例的用于网络打印的系统的框图。 如图1所示,一种移动终端文档打印系统,包括移动终端 10 , 打印机 20 用于打印文档,以及至少一台计算机 30 , 40 , 和 50 与打印机连接 20 通过局域网 (LAN)。 [0024] 移动端 10 ,可以是手机或其他类似设备,与相邻的打印机进行无线连接操作 20 使用无线局域网通信方案,并将要打印的文档传输到打印机 20 当移动端发送打印请求时 10 与打印机相连 20. 移动端 10 包括一个无线自动设置模块 102 , 发现模块 104 , 打印代理模块 106 和图形用户界面 (GUI) 108 . [0025] 无线自动设置模块 102 功能配置移动终端之间的无线自动连接 10 和打印机 20 . [0026] 发现模块 104 找到位于移动终端附近的打印机 10 . 发现模块 104 多播打印机发现请求,然后在接收到响应时从对发现请求的响应中获取作为连接目标的打印机的名称、互联网协议(IP)地址、端口信息等。 在本示例中,移动终端 10 从打印机获取信息 20 . 打印机信息 20 ,如上所述获得,用于将要打印的文档传输到打印机 20 . [0027] 打印代理模块 106 与打印管理器模块通信 114 打印机的 20 , 发送/接收和管理打印机的各种状态信息 20 . 更具体地说,打印代理模块 106 管理无线连接打印机的状态信息 20 ,例如在线状态、离线状态、电源开关状态、进纸状态等。 打印代理模块 106 还向打印机发出文档打印请求 20 , 并通过查询打印机来检查是否可以打印要打印的文档 20 有关打印机是否 20 可以打印文档和接收查询的响应。 打印代理模块 106 请求并获取有关打印中使用的各种属性的信息,例如份数、纸张类型、页面、彩色/黑白等。 打印代理模块 106 将获取的属性信息传输到 GUI 108 . 当用户通过 GUI 选择打印选项信息和打印目标文档时 108 ,打印代理模块 106 将打印选项信息与打印目标文档一起传输到打印机 20 . [0028] 基于从打印代理模块接收到的属性信息 106 , 图形用户界面 108 为用户提供有关无线连接打印机状态、选定份数、选定纸张、打印机是否可以打印文档以及其他可配置打印选项的信息。 用户还可以通过 GUI 选择打印目标文档 108 . [0029] 打印机 20 包括一个无线自动设置模块 110 , 发现模块 112 和打印管理器模块 114 . [0030] 无线自动设置模块 110 配置与移动终端的无线自动连接 10 ,类似于无线自动设置模块 102 移动端 10 . 下面将详细描述这种无线自动连接过程。 [0031] 类似于发现模块 104 移动端 10 , 发现模块 112 提供一个响应,包括关于它自己名字的信息。 接收到移动终端发现请求后的IP地址、端口等 10 . [0032] 打印管理器模块 114 管理目标计算机 30 , 40 , 和 50 能够通过当前打印机输出文件 20 通过映射计算机以表格的形式 30 , 40 , 和 50 根据文件类型。 这样的表可以具有如下表1所示的结构,但本发明不限于此。 表格1 目标 输出 类型 计算机 软件 可用的/ 已分配 不。 文档 地址 版本 不可用 区域(免费) 1 文件 192.168.0.10 7.0 输出 115GB 可用的 2 文件 192.168.0.15 5.0 输出 50MB 不可用 3 xls 192.168.0.110 7.0 输出 663兆字节 可用的 4 ppt 192.168.0.10 7.0 输出 115GB 可用的 5 古尔 192.168.0.20 12   输出 800 兆字节 可用的 . . . . . . . . . . . . . . . [0033] 如表1所示,该表的内容包括文档支持信息,例如每个文档的类型(即文件扩展名)、与打印机连接的每台计算机的网络地址 20在局域网中,每台计算机安装的各文档软件的版本、文档输出是否可用的信息、分配给每台计算机的文档存储区域的信息等。 [0034] 打印管理器模块 114 还从打印代理模块接收用户请求打印的文档 106 移动终端的 10 ,参照表1等表格,找到能够输出接收到的文件的计算机,然后将接收到的文件传送到找到的计算机。 [0035] 如上所述,自动连接移动终端的打印机通过网络连接打印机的计算机中与文档对应的计算机打印待打印文档,使得移动终端无需安装 每个文档对应的打印机驱动程序和应用软件。 [0036] 第一台电脑 30 包括一个发现模块 120 ,打印控制模块 122 , 文档控制模块 124 , 和一个存储 126 . 下面介绍第一台电脑的配置 30 作为示例提供; 第二台和第三台电脑的配置和操作 40 和 50 与第一台计算机相同 30 . [0037] 发现模块 120 执行第一台计算机的发现操作 30 找到打印机 20 . 发现模块 120 还注册有关第一台计算机的文档类型的信息 30 可以输出,网络地址,分配容纳文档的区域等,由文档控制模块收集 124 第一台电脑的 30 那是一台本地计算机,带有打印管理器模块 114 打印机的 20 . [0038] 文档控制模块 124 搜索安装在第一台计算机上的文档软件 30 , 并管理第一台计算机可以输出的文档类型 30 . 在本示例中,由文档控制模块管理的信息 124 包括每个文档的类型(即文件扩展名)、每个软件的名称、每个软件的版本、每个软件的安装位置等。这些管理信息可以具有如下表2所示的表格结构, 但本发明不限于此。 表 2 类型 不。 文档 姓名 版本 软件位置 1 文件 微软Word 7.0 C:\Program Files\Word.exe 2 xls 微软Excel 7.0 C:\Program Files\Excel.exe 3 ppt 微软幻灯片 7.0 C:\Program Files\Powerpoint.exe 4 古尔 训民正音 12   C:\Program Files\Hun.exe 5 hwp 韩文2007 2007    C:\Program Files\Hwp.exe . . . . . . . . . . . . . . . [0039] 文档控制模块 124 还从打印管理器模块接收输出目标文档和用户设置的输出选项 114 打印机的 20 , 并将接收到的输出目标文档和输出选项存储在存储中 126 . 另外,文档控制模块 124 执行文档安全相关的操作,如删除、复制保护、调制保护等,或者文档 [0040] 打印控制模块 122 通过文档软件的输出功能应用接收到的输出选项,并控制打印机 20 打印文档。 [0041] 图2是示意性图示根据本发明实施例的打印过程的图。 进一步来说。 图 2 说明了一个过程,其中,当移动终端 10 无线自动连接打印机 20 并将要打印的文档传输到打印机 20 , 打印机 20 查找该文档对应的计算机,并请求查找到的计算机打印该文档。 [0042] 参考图 2,当打印机 20 电源打开时,打印机 20 执行搜索一台或多台计算机的发现操作 30 和 40 使用预定的发现协议通过 LAN 连接,识别可以从搜索到的计算机输出的文档 30 和 40 , 并注册可以从每台计算机输出的文档 30 和 40 逐步 200 和 205. 在打印机和计算机之间执行发现操作并注册可分步输出的文档的过程 200 和 205 下面参照图3详细描述。 [0043] 在步 210 ,移动终端之间执行无线自动连接过程 10 和打印机 20 . 根据本发明的实施例,提供了一种容易实现无线连接的方法,以提高用户的便利性。 下面参考图4和图5描述这样的无线自动连接过程。图4和图5是解释根据本发明实施例的图2中的无线自动连接过程的流程图。 [0044] 当移动端 10 和打印机 20 已通过步骤相互连接 210 , 在步骤中执行发现操作 215 . 通过discover操作,移动端 10 可以获得打印机的属性信息 20 , 并且可以报告打印机的状态 20 基于获得的属性信息。 当移动端用户 10 选择了打印选项和需要打印的文档,移动终端 10 将要打印的文档传输到打印机 20 在步骤 220 . 在本示例中,用户选择的打印选项与文档和打印机一起被传输 20 参照表 1 等表格查找能够输出文档的计算机。如果打印机 20 找到了第二台电脑 40 作为文档对应的计算机(即能够输出文档),打印机 20 将文档传输到第二台计算机 40 在步骤 225 . 第二台电脑 40 向打印机发送输出指令 20 在步骤 230 , 这样打印机 20 打印文档。 [0045] 如上所述,根据本发明的一个实施例,打印机 20 直接在连接打印机的电脑中寻找适合文档输出的目标电脑 20 通过局域网,请求搜索到的计算机输出文件。 据此,移动终端 10 无需安装单独的打印机驱动程序即可使用打印机 20 ,并可打印存储在移动端的各类文档 10 因为打印请求被发送到与打印机连接的计算机中具有与待打印文档对应的应用软件的计算机 20 通过局域网。 [0046] 如上所述,为了打印各种类型的文档,打印机 20 应了解有关每台计算机支持的文档的信息 30 , 40 , 和 50 . 为此,根据本发明的一个实施例,提供了一种在打印机和计算机之间执行发现操作并注册可以输出的文档的过程,如步骤中所述 200 和 205 . 这种过程参考图3描述如下,其中在打印机之间执行的操作 20 以及第一台和第二台计算机 30 和 40 举例说明。 [0047] 在步 300 , 发现模块 112 打印机的 20 多播请求信号以请求每台计算机 30 和 40 提供有关第一台和第二台计算机可以输出的文档的信息 30 或者 40 , 到计算机 30 和 40 使用发现协议通过 LAN 连接。 打印机 20 传输这样的请求,以便为第一台和第二台计算机中的每台计算机提供身份证明文件输出支持信息 30 和 40 . 请求被传输到发现模块 120 和 130 第一台和第二台电脑 30 和 40 , 分别。 每个发现模块 120 和 130 查询各文件控制模块 124 和 134,分别是关于步骤的可打印文档列表 305 和 310 , 这样每个文档控制模块 124 和 134 分步获取申请信息 315 和 320 , 分别。 应用信息表示文档信息,包括每台计算机支持的文档类型、每台计算机安装的文档软件的版本、是否可以输出、可容纳的文档分配区域。 此后,当每个文档控制模块 124 和 134 将文档信息传送给各个发现模块 120 和 130 逐步 335 和 340 , 每个发现模块 120 和 130 生成并向打印机发送包含文档信息的响应消息 20 逐步 345 和 350 . 在本示例中,除了文档信息之外,响应消息还包括网络地址。 [0048] 如上所述,每台计算机 30 和 40 提供打印机 20 具有文档支持信息,包括计算机支持的文档类型和版本、可容纳的文档分配区域、是否可以输出、网络地址等,使用发现协议,预先响应一个 可打印文档信息请求。 如果第三台电脑 50 发现操作完成后上电,第三台计算机的发现模块 50 可以直接注册有关第三台计算机支持的文档的信息 50 使用先前注册的打印机 20 . [0049] 当打印机 20 从第一台计算机和第二台计算机中的每台计算机接收包括每条文档信息的响应消息 30 和 40 通过上述步骤,打印机 20 根据接收到的每条文档信息生成表格如表1。 该表用于查找可以输出从移动端接收到的文档的计算机 10 . [0050] 根据本发明的实施例,一种使用户能够轻松连接移动终端的方法 10 和打印机 20 使用无线自动设置程序,即提供无线自动连接设置程序。 这样一个无线自动连接过程对应的步骤 210 下面结合图4和图5详细描述图2中的。 [0051] 图4是图示在无线局域网通信方案中使用无线保真(WiFi)方案的无线自动连接过程的图,其中移动终端之间的WiFi通信需要服务集标识符(SSID) 10 和打印机 20 ,认证和加密需要安全密钥,IP通信必须设置IP地址,并且需要有线等效保密(WEP)密钥值,因为认证和加密是在WEP方案中执行的。 根据本发明的实施例,使用自动生成和设置无线连接所需的所有信息的方案。 具体地,SSID、安全密钥、IP地址是使用用户在移动终端之间输入的相同信息自动生成的。 10 和打印机 20 . 根据本发明的备选实施例,可以使用随机信息来代替相同的信息。 在这种情况下,随机信息可以是在移动终端中随机生成的随机数 10 和打印机 20 . 通过该流程,可以方便的自动连接移动终端 10 到打印机 20 无需用户每次都输入无线局域网连接的每条信息。 由于每次连接尝试都会发生变化的随机信息的特性,可以获得更高的安全特性。 [0052] 参见图4,移动终端 10 和打印机 20执行同样的无线连接软件,在移动端开始建立WiFi连接 10 和打印机 20 ,分别根据用户输入。 当请求启动此类无线 LAN 自动连接过程时,打印机 20 生成并显示与移动端通用的随机信息 10 , 在打印机的显示单元上 20 对于无线自动连接,步骤 400 . 移动终端 10 在打印机的显示单元上显示一个随机数 20 , 并接收用户输入的打印机随机数 20 在一步 405 . 这样的随机数用于生成和设置无线自动连接所需的信息。 具体如步骤所示 410 和 415 、SSID、WEP等自动生成,并使用相同的哈希函数设置各自的随机数,从而完成WiFi连接。 [0053] 图5是图示在无线局域通信方案中使用蓝牙(BT)方案的无线自动连接过程的图,其中每个移动终端 10 和打印机 20 使用相同的散列函数生成设备名称和带有随机数的个人识别码 (PIN) 代码,如图 4 所示。 当移动终端开始建立蓝牙连接时 10 和打印机 20 , 打印机 20 步骤中生成并输出一个随机数 500 ,然后用户通过移动端看到并输入随机数 10 在一步 505 . 然后,打印机 20 使用随机数分步执行设备名称设置程序和 PIN 码自动生成/设置程序 510 和 515 ,分别是移动端 10 使用随机数逐步执行打印机发现操作和 PIN 码自动生成/设置过程 520 和 525 , 分别。 相应地,用户只需输入一个随机数,即可自动实现移动终端之间的无线连接。 10 和打印机 20 . [0054] 以下为移动终端与打印机之间的发现及文档输出流程,对应步骤 215 至 230 在图2中,结合图6详细描述如下。 [0055] 参考图6,用户可以通过GUI提供的“打印”菜单开始网络打印功能 108 . 当这样的开始请求被输入到移动终端时 10 , 发现模块 104 移动终端的 10 在步骤中执行发现协议 600 ,从而从发现模块请求打印机发现 112 打印机的 20 . 对于这样的请求,发现模块 104 移动终端的 10 多播 DISCOVERY_PRINTER 消息。 在收到这样的 DISCOVERY_PRINTER 消息后,打印机 20 向discovery模块发送RESPONSE_PRINTER消息,该消息是包含打印机信息的响应消息,例如自己的打印机名称、IP地址、端口信息等 104 移动终端的 10 在一步 605 . 发现模块 104 将通过这种发现过程获取的打印机信息传输到打印代理模块 106 在一步 610 . [0056] 图形用户界面 108 发送 PRINTING_CAPABILITY_REQUEST 消息请求打印机的属性信息 20 来自打印代理模块 106 在一步 615 . 这种属性信息请求用于准备“打印”菜单,使用户能够检查打印机的状态,然后配置所需的选项。 [0057] 据此,印刷剂模块 106 将 PRINTING_CAPABILITY_REQUEST 消息传输到打印管理器模块 114 打印机的 20 在一步 620 为了请求属性信息。 打印管理器模块 114通过发送与步骤中的属性信息请求对应的 PRINTING_CAPABILITY_RESPONSE 消息进行响应 625 . 这种响应消息包括移动终端请求的属性信息 10 . 这里的属性信息表示与打印相关的各种信息,包括可打印文档的类型、打印机的状态 20 ,以及有关可以设置的各种选项的信息。 [0058] 在收到 PRINTING_CAPABILITY_RESPONSE 消息后,打印代理模块 106 将 PRINTING_CAPABILITY_RESPONSE 消息传输到 GUI 108 , 在步骤 630 . 图形用户界面 108 根据收到的属性信息提供“打印”菜单。 这种“打印”菜单包括各种选项功能,包括打印机的状态信息、可打印文档的类型、彩色/黑白设置选项、水平/垂直设置选项等。当打印目标文档和各种打印选项已经 通过使用“打印”菜单指定,GUI 108 将打印目标文件传送给打印代理模块 106 在步骤中使用 SELECT_DOCUMENT 消息 635 . 打印代理模块 106 在步骤中通过使用 PRINT_REQUEST 消息组合并传输文档和指定的打印选项 640 . [0059] 通过这样一个PRINT_REQUEST消息,将与指定的打印选项组合在一起的打印目标文档传送给打印管理模块 114 打印机的 20 . 打印管理器模块 114 参考步骤中的表1等表格选择能够输出文档的计算机 642 . 更具体地说,打印机 20 将接收文件的类型、接收文件的容量、使用权限等与文件-计算机映射表如表1中的相应信息进行比较,选择能够输出接收文件的计算机。 当打印机 20 选择第一台计算机 30 ,打印管理器模块 114 向文档控制模块发送 PRINT_REQUEST 消息 124 第一台电脑的 30 在步骤 650 ,从而将文档和打印选项传输到文档控制模块 124 . [0060] 收到 PRINT_REQUEST 消息后,文档控制模块 124 将文档存储在存储的本地存储区域中 126 在步骤 655 ,然后通知打印控制模块 122 通过使用 PRINT_REQUEST 消息确定存储文档的位置和打印选项,步骤 660 . 打印控制模块 122 通过参考如表2的文档-应用表,将应用程序或输出API应用到打印选项,执行与文档或应用程序的输出API对应的应用程序,使得打印管理器模块 114 打印机的 20 可以打印文档。 据此,打印控制模块 122 向打印管理器模块发送包含打印图像的 PRINT 消息 114 在步骤 665 , 以便通过打印机驱动程序执行实际打印。 [0061] 根据本发明的实施例,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档。 另外,由于文档打印指令是在移动终端位于打印机附近的状态下发出的,因此用户可以在没有打印机信息的情况下打印移动终端的文档,并且可以立即获得打印的文档。 因此,用户无需在每次打印文档时都寻找文档应用程序并安装适用于相应打印机的打印机驱动程序,从而提高了用户的便利性。 另外,根据本发明实施例,还提供了一种简单实现移动终端与打印机无线连接的方法,使得用户能够方便地连接移动终端与打印机。 [0062]虽然本发明已参照其某些实施例进行了展示和描述; 本领域的技术人员将理解,在不脱离由所附权利要求限定的本发明的精神和范围的情况下,可以在其中进行形式和细节的各种改变。 因此,本发明的范围不受上述实施例的限制,而是由权利要求及其等同物限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.477 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102023829A(String), EP2302504A2(String), EP2302504A3(String), KR1020110029435A(String), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102023829A(String), EP2302504A2(String), EP2302504A3(String), KR1020110029435A(String), US20110063663A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102023829A(String), EP2302504A2(String), EP2302504A3(String), KR1020110029435A(String), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270695(Integer), CN102023829A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270695(Integer), EP2302504A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270695(Integer), EP2302504A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.520 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270695(Integer), KR1020110029435A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270695(Integer), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20110063663A1(String), US20110063663A1(String), 1300291200(Integer), 270695(Integer), 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.557 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185018(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185018(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.567 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.567 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185018(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185018(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10425523B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for controlling mobile terminal, and mobile terminal(String), 控制移动终端的方法及移动终端(String), US10425523B2(String), The present disclosure discloses a method of controlling a mobile terminal, and a mobile terminal. The method of controlling a mobile terminal includes obtaining a motion status of a user of the mobile terminal, and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status.(String), 本公开公开了一种控制移动终端的方法和移动终端。 控制移动终端的方法包括获得移动终端的用户的运动状态,以及基于获得的运动状态执行与预定事件对应的移动终端的功能。(String), US15/570543(String), 1463932800(Integer), US10425523B2(String), 1569254400(Integer), 1569254400(Integer), 美国(String), 4(Integer), CN | CN | KR(String), 5(Integer), 42(Integer), CN101150542A | CN101179533A | CN101754462A | CN102655541A | CN103179535A | CN103476985A | CN103500047A | CN103747140A | CN103763675A | CN103873342A | CN1812380A | CN1941707A | EP2608501A1 | JP2005115557A | JP2006294970A | JP2013032932A | JP2013089238A | JP2014161930A | JP2014211850A | KR101117424B1 | KR1020100021859A | KR1020100073743A | KR1020110046909A | KR1020140073232A | US20070260730A1 | US20110106530A1 | US20130104089A1 | US20130104090A1 | US20130203393A1 | US20130237204A1 | US20150112796A1 | US7039676B1 | US7512407B2 | US8213914B2 | US9032337B2 | WO2009023701A2 | WO2013029258A1(String), 13(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185019(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f6126a7598854d78901455e47701b01a.png(String), 185019(Integer), f6126a7598854d78901455e47701b01a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for controlling mobile terminal, and mobile terminal(String), 控制移动终端的方法及移动终端(String), US10425523B2(String), The present disclosure discloses a method of controlling a mobile terminal, and a mobile terminal. The method of controlling a mobile terminal includes obtaining a motion status of a user of the mobile terminal, and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status.(String), 本公开公开了一种控制移动终端的方法和移动终端。 控制移动终端的方法包括获得移动终端的用户的运动状态,以及基于获得的运动状态执行与预定事件对应的移动终端的功能。(String), US15/570543(String), 1463932800(Integer), US10425523B2(String), 1569254400(Integer), 1569254400(Integer), 美国(String), 3(Integer), 4(Integer), CN | CN | KR(String), 5(Integer), 42(Integer), CN101150542A | CN101179533A | CN101754462A | CN102655541A | CN103179535A | CN103476985A | CN103500047A | CN103747140A | CN103763675A | CN103873342A | CN1812380A | CN1941707A | EP2608501A1 | JP2005115557A | JP2006294970A | JP2013032932A | JP2013089238A | JP2014161930A | JP2014211850A | KR101117424B1 | KR1020100021859A | KR1020100073743A | KR1020110046909A | KR1020140073232A | US20070260730A1 | US20110106530A1 | US20130104089A1 | US20130104090A1 | US20130203393A1 | US20130237204A1 | US20150112796A1 | US7039676B1 | US7512407B2 | US8213914B2 | US9032337B2 | WO2009023701A2 | WO2013029258A1(String), \20230420\f6126a7598854d78901455e47701b01a.png(String), 13(Integer), 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 1. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises transmitting the information representing the motion status of the user to a counterpart device which is in communication with the mobile terminal, andwherein a GUI object representing the motion status of the user is displayed, based on the transmitted information representing the motion status, in an interface of a contact application which is executed in the counterpart device.(String), 1.一种移动终端的控制方法、方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,执行移动终端的功能包括将表示用户的运动状态的信息发送到与移动终端通信的对方设备,以及其中,基于所发送的代表动作状态的信息,在对方设备中执行的联系人应用的界面中显示代表用户的动作状态的GUI对象。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 2. The method of claim 1, wherein the obtaining of the information representing the motion status comprises:periodically receiving output data from an inertia sensor of the mobile terminal;reading a feature value from the received output data; anddetermining the motion status corresponding to the read feature value from a table of mapping relationships between motion statuses and feature values.(String), 2.如权利要求1所述的方法,其中获取表示运动状态的信息包括:周期性地接收移动终端的惯性传感器输出的数据;从接收到的输出数据中读取特征值;和从运动状态与特征值的映射关系表中确定读取的特征值对应的运动状态。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 3. The method of claim 1, wherein the obtaining of the information representing the motion status comprises:obtaining, by a global positioning system (GPS), starting location information and ending location information corresponding to a predetermined time interval;calculating a movement velocity corresponding to the predetermined time interval, based on the starting location information and the ending location information; anddetermining the motion status corresponding to the calculated movement velocity from a table of mapping relationships between motion statuses and movement velocities.(String), 3.如权利要求1所述的方法,其中获取表示运动状态的信息包括:通过全球定位系统(GPS)获取预定时间间隔对应的起始位置信息和结束位置信息;基于起始位置信息和结束位置信息计算对应于预定时间间隔的运动速度;和根据运动状态与运动速度的映射关系表,确定计算出的运动速度对应的运动状态。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 4. The method of claim 1, wherein the contact application is an instant message application,wherein the performing of the function of the mobile terminal further comprises transmitting the information representing the motion status of the user to the counterpart device in response to execution of the instant message application, andwherein a GUI object representing the motion status of the user displayed on an instant messaging interface of the instant messaging application of the counterpart device is updated, based on the transmitted information representing the motion status.(String), 4.如权利要求1所述的方法,其中联系人应用程序是即时消息应用程序,其中,移动终端的功能的执行进一步包括响应于即时消息应用的执行将表示用户的运动状态的信息发送到对方设备,以及其中,基于所发送的代表动作状态的信息,更新对方设备的即时通讯应用的即时通讯界面上显示的代表用户的动作状态的GUI对象。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 5. The method of claim 1, wherein the contact application is a call application,wherein the performing of the function of the mobile terminal further comprises transmitting the information representing the motion status of the user to the counterpart device in response to execution of the call application, andwherein a GUI object representing the motion status of the user displayed on a call interface of the call application of the counterpart device, based on the transmitted information representing the motion status.(String), 5.如权利要求1所述的方法,其中联系人应用程序是呼叫应用程序,其中,移动终端的功能的执行还包括响应于呼叫应用的执行将表示用户的运动状态的信息发送到对方设备,以及其中,基于所传输的表示用户动作状态的信息,在对端设备的通话应用的调用界面上显示表示用户动作状态的GUI对象。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 6. The method of claim 1, wherein the contact application is an address list application,wherein the performing of the function of the mobile terminal further comprises transmitting the information representing the motion status of the user to the counterpart device in response to execution of the address list application, andwherein a GUI object representing the motion status of the user displayed on an address list of the address list application of the counterpart device, based on the transmitted information representing the motion status.(String), 6.如权利要求1所述的方法,其中联系人应用程序是地址列表应用程序,其中,移动终端的功能的执行进一步包括响应于地址列表应用的执行将表示用户的运动状态的信息发送到对方设备,以及其中,基于所发送的代表动作状态的信息,代表用户的动作状态的GUI对象被显示在对方设备的地址列表应用的地址列表上。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 7. The method of claim 1, wherein the contact application is an address list, andwherein the performing of the function of the mobile terminal further comprises displaying, in real time, a motion status of a contact in the address list and a time period required by the contact from a current location to a destination on a user interface in response to execution of a real-time timing function for the contact, based on the obtained information representing the motion status.(String), 7.如权利要求1所述的方法,其中联系人应用程序是一个地址列表,并且其中,所述移动终端的功能的执行还包括:实时显示通讯录中联系人的运动状态,以及该联系人从当前位置到目的地所需的时间,以响应用户界面。基于获得的表示运动状态的信息,为接触执行实时计时功能。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 8. The method of claim 1, the method further comprising:receiving information representing a motion status of another user of the counterpart device which is in communication with the mobile terminal, andwherein the performing of the function of the mobile terminal further comprises displaying a GUI object representing the motion status of the another user, based on the received information representing the motion status of the another user, in an interface of a contact application which is executed in the mobile terminal.(String), 8.如权利要求1所述的方法,该方法还包括:接收表示与移动终端通信的对方设备的另一用户的运动状态的信息,以及其中,移动终端的功能的执行还包括基于接收到的表示另一个用户的运动状态的信息,在联系人应用的界面中显示表示另一个用户的运动状态的GUI对象,该联系人应用在以下步骤中执行:移动终端。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 9. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises automatically switching a home screen layout of the mobile terminal in response to execution of the mobile terminal, based on the obtained information representing the motion status.(String), 9.一种移动终端的控制方法,该方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,执行移动终端的功能包括基于获得的表示运动状态的信息,响应于移动终端的执行自动切换移动终端的主屏幕布局。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 10. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises automatically adjusting a ringtone or a call volume of the mobile terminal when receiving a call, based on the obtained information representing the motion status.(String), 10.一种移动终端的控制方法,该方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,移动终端功能的执行包括:基于获取的表示运动状态的信息,在来电时自动调整移动终端的铃声或通话音量。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 11. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises, when an incoming call or a received short message is not answered within a predetermined unanswered time period, sending a status reply including the obtained motion status to an opposite party of the incoming call or the received short message, based on the obtained information representing the motion status.(String), 11.一种移动终端的控制方法,该方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,所述移动终端的功能的执行包括:当来电或收到的短信在预定无人应答时间内无人应答时,向来电或对方发送包括获取的动作状态在内的状态回复。接收到的短消息,根据获取到的代表运动状态的信息。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 12. A mobile terminal comprising:a communication interface;at least one sensor configured to detect a motion of the mobile terminal;a memory storing one or more instructions; andat least one processor configured to execute the one or more instructions at least to:obtain information representing a motion status of a user of the mobile terminal; andperform a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the at least one processor executes the one or more instructions to transmit the information representing the motion status of the user to a counterpart device which is in communication with the mobile terminal, andwherein a GUI object representing the motion status of the user is displayed, based on the transmitted information representing the motion status, in an interface of a contact application which is executed in the counterpart device.(String), 12.移动终端包括:通信接口;至少一个传感器,用于检测移动终端的运动;存储一条或多条指令的存储器;和至少一个处理器被配置为执行一个或多个指令至少以:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,至少一个处理器执行一个或多个指令以将表示用户的运动状态的信息发送到与移动终端通信的对应设备,并且其中,基于所发送的代表动作状态的信息,在对方设备中执行的联系人应用的界面中显示代表用户的动作状态的GUI对象。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185019(Integer), 13. A computer program product comprising a non-transitory computer readable storage medium comprising a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, causes the computing device to perform operations of:obtaining information representing a motion status of a user of the computing device; andperforming a function of the computing device corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the computing device comprises transmitting the information representing the motion status of the user to a counterpart device which is in communication with the computing device, andwherein a GUI object representing the motion status of the user is displayed, based on the transmitted information representing the motion status, in an interface of a contact application which is executed in the counterpart device.(String), 13.计算机程序产品包括一种非暂时性计算机可读存储介质,包括存储在其中的计算机可读程序,其中计算机可读程序当在计算设备上执行时使计算设备执行以下操作:获取表示计算设备用户的运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件相对应的计算设备的功能,其中计算设备的功能的执行包括将表示用户的运动状态的信息发送到与计算设备通信的对应设备,并且其中,基于所发送的代表动作状态的信息,在对方设备中执行的联系人应用的界面中显示代表用户的动作状态的GUI对象。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.758 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.758 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.759 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.760 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185019(Integer), TECHNICAL FIELD [0001]The present disclosure relates to a method of controlling a mobile terminal, and a mobile terminal. BACKGROUND ART [0002]To more effectively utilize functions of a mobile terminal, information about a status of a user of the mobile terminal may be reflected. However, if the user directly selects and sets the information about the status of the user, an actual status of the user cannot be accurately reflected. DETAILED DESCRIPTION OF THE INVENTION Technical Problem [0003]The present disclosure provides a method of controlling a mobile terminal, and a mobile terminal, whereby functions of the mobile terminal are more effectively utilized by using information about an actual motion status of a user of the mobile terminal. Technical Solution [0004]According to a first aspect of the present invention, there is provided a method of controlling a mobile terminal, the method including obtaining a motion status of a user of the mobile terminal; and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status. [0005]The obtaining of the motion status may include periodically receiving output data from an inertia sensor of the mobile terminal; reading a feature value from the received output data; and determining a motion status corresponding to the read feature value from a table of mapping relationships between motion statuses and feature values. [0006]The obtaining of the motion status may include obtaining, by a global positioning system (GPS), starting location information and ending location information corresponding to a predetermined time interval; calculating a movement velocity corresponding to the predetermined time interval, based on the starting location information and the ending location information; and determining a motion status corresponding to the calculated movement velocity from a table of mapping relationships between motion statuses and movement velocities. [0007]The performing of the function of the mobile terminal may include updating a motion status of an instant messaging user displayed on an instant messaging interface in response to execution of an instant message application, based on the obtained motion status. [0008]The performing of the function of the mobile terminal may include updating a motion status of an opposite party displayed on a call interface in response to execution of a call application, based on the obtained motion status. [0009]The performing of the function of the mobile terminal may include updating a motion status of a contact displayed on an address list in response to execution of an address list application, based on the obtained motion status. [0010]The performing of the function of the mobile terminal may include displaying, in real time, a motion status of a contact in an address list and a time period required by the contact from a current location to a destination on a user interface in response to execution of a real-time timing function for the contact, based on the obtained motion status. [0011]The performing of the function of the mobile terminal may include automatically switching a device mode in response to execution of the mobile terminal, based on the obtained motion status. [0012]The performing of the function of the mobile terminal may include adjusting a ringtone or a call volume of the mobile terminal when receiving a call, based on the obtained motion status. [0013]The performing of the function of the mobile terminal may include, when an incoming call or a received short message is not answered for a long time, sending a status reply including the obtained motion status to an opposite party of the incoming call or the received short message, based on the obtained motion status. [0014]According to a second aspect of the present invention, there is provided a mobile terminal including a memory configured to store computer executable instructions; and at least one processor configured to obtain a motion state of a user of the mobile terminal and perform a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion state, by executing the computer executable instructions. [0015]According to a third aspect of the present invention, there is provided a method for communication of a mobile terminal, the method including selecting a setting item for resetting communication setting; detecting a motion status of the mobile terminal in real time; obtaining a current motion status of the mobile terminal; and resetting the selected setting item according to the obtained motion status. [0016]According to a fourth aspect of the present invention, there is provided a mobile terminal including a system setting module configured to select a setting item for resetting communication setting; a motion status determining module configured to detect a motion status of the mobile terminal in real time, obtain a current motion status of the mobile terminal, and send the obtained motion status to the communication resetting module; and a communication resetting module configured to reset the selected setting item according to the obtained motion status. [0017]As shown in the above technical solutions of the present disclosure, the motion status of the mobile terminal may be detected in real time, and the current motion status of the mobile terminal may be obtained. The selected setting item may be reset according to the obtained motion status. Accordingly, the communication setting may be performed automatically according to an actual motion status of the mobile terminal, thereby making the communication setting more accurate and intelligent. DESCRIPTION OF THE DRAWINGS [0018]FIG. 1 is a schematic flowchart illustrating a communication method of a mobile terminal, according to an embodiment of the present disclosure. [0019]FIG. 2 is a flowchart of a method, performed by an inertia sensor, of determining a motion status, according to an embodiment of the present disclosure. [0020]FIG. 3 is a flowchart of a method, performed by a global positioning system (GPS), of determining a motion status, according to an embodiment of the present disclosure. [0021]FIG. 4 is a flowchart of a process of outputting motion statuses S0 and S1 when they are determined by a combination of an inertia sensor and a GPS. [0022]FIG. 5 is a flowchart of a process of outputting a final motion status, based on the motion statuses S0 and S1, according to an embodiment of the present disclosure. [0023]FIG. 6 shows interfaces for updating a motion status displayed on an instant messaging interface according to an embodiment of the present disclosure. [0024]FIG. 7 is a flowchart of a method of determining a motion track, according to an embodiment of the present disclosure. [0025]FIG. 8 shows interfaces for updating a motion status displayed in a call process according to an embodiment of the present disclosure. [0026]FIG. 9 shows interfaces for updating a motion status of a contact in an address list, according to an embodiment of the present disclosure. [0027]FIG. 10 shows interfaces prompted to the user when the motion status of a contact displayed in the address list changes according to a predefined mode or when the motion status of the contact is a predefined motion status, according to an embodiment of the present disclosure. [0028]FIG. 11 shows interfaces that display the motion track and the location information of each party member in real time according to a party assistant function in instant messaging, according to an embodiment of the present disclosure. [0029]FIG. 12 shows a process of performing a real-time timing function for a contact in an address list, according to an embodiment of the present disclosure. [0030]FIG. 13 illustrates a process of automatically recommending participating in a group according to a motion status of a user, according to an embodiment of the present disclosure. [0031]FIG. 14 illustrates interfaces on which a device mode is automatically switched according to a motion status of a user, according to an embodiment of the present disclosure. [0032]FIG. 15 illustrates a process of automatically adjusting a call ringtone or a call volume according to a motion status of a user, according to an embodiment of the present disclosure. [0033]FIG. 16 illustrates a process of automatically performing status replies to an incoming call and a received short message according to a current motion status of a user, according to an embodiment of the present disclosure. [0034]FIGS. 17A-17C are block diagrams illustrating a structure of a mobile terminal, according to an embodiment of the present disclosure. [0035]FIG. 18 is a flowchart illustrating a method of controlling a mobile terminal, according to an embodiment of the present disclosure. BEST MODE [0036]A method of controlling a mobile terminal includes obtaining a motion status of a user of the mobile terminal; and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status. Mode of the Invention [0037]Exemplary embodiments of the present disclosure will now be described more fully with reference to the accompanying drawings. The various embodiments below are only to specify the inventive concept and are not to restrict or limit the right scope of the inventive concept. It is analyzed that those which could be readily inferred by one of ordinary skill in the art to which the inventive concept belongs from the detailed description and the various embodiments belong to the right scope of the inventive concept. [0038]Terms “configured” or “include” used herein should not be construed as necessary including all of several components or several steps written in the specification, but as not including some of the components or steps or as further including additional components or steps. [0039]While such terms as “first,”“second,” etc., may be used to describe various components, such components must not be limited to the above terms. The above terms are used only to distinguish one component from another. [0040]The below embodiments relate to a mobile terminal and a method of controlling a mobile terminal, and a detailed description of matters well known to one of ordinary skill in the art to which the below embodiments pertain will be omitted. [0041]The present disclosure is described in detail with reference to the attached drawings and the embodiments. [0042]FIG. 1 is a schematic flowchart illustrating a method for communication of a mobile terminal according to an embodiment of the present disclosure. The method includes the following operations. [0043]In operation 101, a setting item for resetting communication settings is selected. [0044]When the setting item for resetting communication settings is determined based on a motion status, at least one setting item may be selected. For example, at least one of fourteen items may be selected, which include an item for updating a motion status of an instant messaging user in real time, an item for updating a motion track of an instant messaging user in real time, an item for updating a motion status of a user in a call process in real time, an item for updating a motion status of a contact in an address list in real time, an item for a prompt of a motion status of a contact in an address list, an item for enabling a party assistant function in instant messaging, an item for enabling a real-time timing function for a contact in an address list, an item for automatically recommending participating in a group according to a motion status of a user, an item for automatically performing a prompt according to a motion status of a user, an item for automatically switching a device mode according to a motion status of a user, an item for automatically switching a topic mode according to a motion status of a user, an item for automatically switching a do-not-disturb mode according to a motion status of a user, an item for call control, and an item for status reply. [0045]In operation 102, the motion status of the mobile terminal is detected in real time. [0046]Multiple methods for detecting the motion status of the mobile terminal may be used. For example, a motion status of the mobile terminal may be detected by an inertia sensor, by a global positioning system (GPS), or by a combination of the inertia sensor and the GPS. [0047]In operation 103, a current motion status of the mobile terminal is obtained. [0048]A currently-detected motion status of the mobile terminal is obtained. [0049]In operation 104, the selected setting item is reset according to the obtained motion status. [0050]After obtaining the current motion status, the selected setting item may be reset. Because setting items are different, methods for resetting the setting items are different. [0051]In an example of the present disclosure, the motion status of the mobile terminal is detected in real time, the current motion status of the mobile terminal is obtained, and the selected setting item is reset according to the obtained motion status. Accordingly, the communication setting may be performed automatically according to an actual motion status of the mobile terminal, thereby making the communication setting more accurate and intelligent. [0052]Methods for detecting a motion status will now be described according to some examples. [0053]In a first example, the motion status may be detected by an inertia sensor. [0054]The mobile terminal may include an inertia sensor. For example, the inertia sensor may be an acceleration sensor or a gyroscope. [0055]A method of detecting the motion status by the inertia sensor includes: periodically receiving output data of the inertia sensor and adding the output data to a storage queue; when the length of the storage queue is larger than a predefined value, processing data in the storage queue to extract a feature value; and finding the motion status from a table of mapping relationships between motion statuses and feature values according to the extracted feature value. [0056]Further, the accuracy of motion status determination may be improved through the following methods. [0057]The process of detecting the motion status by the inertia sensor may be repeated for N0 times, and the determined motion status may be recorded every time the process of detecting the motion status by the inertia sensor is performed. [0058]The number of times each motion status is detected is counted and represented as N. [0059]If a motion status S meets a condition of N>N0*m, the motion status S is determined as a final motion status, wherein 0N 的条件 0 *m,运动状态S被确定为最终运动状态,其中0 Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104821991A(String), CN105657188A(String), CN105657188B(String), EP3300342A1(String), EP3300342A4(String), EP3300342B1(String), KR1020160137446A(String), KR102321363B1(String), US10425523B2(String), US20180176363A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.784 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104821991A(String), CN105657188A(String), CN105657188B(String), EP3300342A1(String), EP3300342A4(String), EP3300342B1(String), KR1020160137446A(String), KR102321363B1(String), US10425523B2(String), US20180176363A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.785 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10425523B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104821991A(String), CN105657188A(String), CN105657188B(String), EP3300342A1(String), EP3300342A4(String), EP3300342B1(String), KR1020160137446A(String), KR102321363B1(String), US10425523B2(String), US20180176363A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), CN104821991A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), CN105657188A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.817 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), CN105657188B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), EP3300342A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.835 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), EP3300342A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.844 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), EP3300342B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), KR1020160137446A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), KR102321363B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.869 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), US10425523B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.881 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270696(Integer), US20180176363A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10425523B2(String), US10425523B2(String), 1569254400(Integer), 270696(Integer), 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.898 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.900 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185019(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185019(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185019(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185019(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.924 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.928 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.939 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.940 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120309450A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Controlling Communication States of Mobile Terminal and Mobile Terminal(String), 控制移动终端通信状态的方法及移动终端(String), US20120309450A1(String), The invention provides a method for controlling communication states of a mobile terminal and the mobile terminal. The method comprises: the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; and the mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are inconsistent, adjusting the current communication state to the communication state corresponding to the planned time period. The invention allows the user to set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time.(String), 本发明提供了一种控制移动终端通信状态的方法及移动终端。 该方法包括:移动终端通过特定的设置界面接收并存储用户输入的计划时间段和与计划时间段对应的通信状态; 移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态 到计划时间段对应的通信状态。 本发明允许用户根据自己的工作或学习需要在移动终端中设置时间规划和相应的通信状态,从而在闲暇时保持正常通信的同时,避免来电和短信带来的不必要的打扰。(String), US13/575703(String), 1277827200(Integer), US20120309450A1(String), 1354723200(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 3(Integer), US20100042827A1 | US6317593B1 | US7302272B2(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185020(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\847925722ed049acb4155f9312789f8e.png(String), 185020(Integer), 847925722ed049acb4155f9312789f8e.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Controlling Communication States of Mobile Terminal and Mobile Terminal(String), 控制移动终端通信状态的方法及移动终端(String), US20120309450A1(String), The invention provides a method for controlling communication states of a mobile terminal and the mobile terminal. The method comprises: the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; and the mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are inconsistent, adjusting the current communication state to the communication state corresponding to the planned time period. The invention allows the user to set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time.(String), 本发明提供了一种控制移动终端通信状态的方法及移动终端。 该方法包括:移动终端通过特定的设置界面接收并存储用户输入的计划时间段和与计划时间段对应的通信状态; 移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态 到计划时间段对应的通信状态。 本发明允许用户根据自己的工作或学习需要在移动终端中设置时间规划和相应的通信状态,从而在闲暇时保持正常通信的同时,避免来电和短信带来的不必要的打扰。(String), US13/575703(String), 1277827200(Integer), US20120309450A1(String), 1354723200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 3(Integer), US20100042827A1 | US6317593B1 | US7302272B2(String), \20230420\847925722ed049acb4155f9312789f8e.png(String), 6(Integer), 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185020(Integer), 1. A method for controlling communication states of a mobile terminal comprising:the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; andthe mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are not consistent, adjusting the current communication state to the communication state corresponding to the planned time period.(String), 1.一种移动终端通信状态控制方法包括:移动终端通过特定的设置界面接收并存储用户输入的计划时间段以及与计划时间段对应的通信状态;和移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态到计划时间段对应的通信状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185020(Integer), 2. The method according to claim 1, further comprising:the mobile terminal receiving authentication information input by the user, and detecting whether the authentication information is legal, and if yes, entering the specific setup interface.(String), 2.根据权利要求1所述的方法,还包括:移动终端接收用户输入的认证信息,检测认证信息是否合法,若合法则进入具体设置界面。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185020(Integer), 3. The method according to claim 1, further comprising:if the mobile terminal detects that the current time is in the planned time period, calculating duration from the current time to the end time of the planned time period; andmaintaining the communication state corresponding to the planned time period in the duration.(String), 3.根据权利要求1所述的方法,还包括:若移动终端检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长;和在duration中保持计划时间段对应的通信状态。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185020(Integer), 4. A mobile terminal comprising:a setting module configured to receive and store a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface;a processing module configured to detect whether the current time is in the planned time period, if yes, detect whether the current communication state is consistent with the communication state corresponding to the planned time period stored in the setting module, and if they are not consistent, output a signal to a communication module; andthe communication module configured to receive the signal from the processing module, and then adjust the current communication state to the communication state corresponding to the planned time period and stored in the setting module.(String), 4.移动端包括:设置模块,用于接收并存储用户通过特定设置界面输入的计划时间段和与计划时间段对应的通信状态;处理模块,用于检测当前时间是否在计划时间段内,如果是,则检测当前通信状态与设置模块中存储的计划时间段对应的通信状态是否一致,如果不一致,输出信号给通信模块;和通讯模块,用于接收来自处理模块的信号,将当前的通讯状态调整为设置模块中存储的计划时间段对应的通讯状态。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185020(Integer), 5. The mobile terminal according to claim 4, further comprising an authentication module, whereinthe authentication module is configured to receive authentication information input by the user, and detecting whether the authentication information is legal, and if yes, output a signal to the setting module; andthe setting module is further configured to receive the signal of the authentication module and then enter the specific setup interface.(String), 5.根据权利要求4所述的移动终端,还包括认证模块,其中鉴权模块,用于接收用户输入的鉴权信息,检测鉴权信息是否合法,若合法,则向设置模块输出信号。和设置模块还用于接收鉴权模块的信号,进入特定的设置界面。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:00.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185020(Integer), 6. The mobile terminal according to claim 4, whereinthe processing module is further configured to calculate duration from the current time to the end time of the planned time period if detecting that the current time is in the planned time period, and output the calculated duration to the communication module; andthe communication module is further configured to receive the duration and maintain the communication state corresponding to the planned time period in the duration.(String), 6.根据权利要求4所述的移动终端,其中处理模块,还用于若检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长,并将计算出的时长输出给通信模块。和通信模块还用于接收时长,并在该时长内保持计划时间段对应的通信状态。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185020(Integer), TECHNICAL FIELD [0001]The present invention relates to mobile communications, and more particularly, to a method for controlling communication states of a mobile terminal and the mobile terminal. BACKGROUND OF THE RELATED ART [0002]In the current information society, roles of information and communication are more and more important. Different users have different demands on functions of mobile terminals (such as, mobile phones, Personal Handy-phone Systems (PHS)). When services are busy or some transactions are required to be processed tranquilly, incoming calls or text messages will certainly affect users' attention. In a classroom where tens of students flock together, for example, incoming and outgoing short messages and MMS (Multimedia Messaging Service) notification messages of mobile communication terminals in class time will seriously affect students' class attention and teachers' teaching process. Moreover, cross-radiation due to the mobile terminals inside the classroom will seriously affect the students' health. SUMMARY OF THE INVENTION [0003]A object of the present invention is to provide a method for controlling communication states of a mobile terminal and the mobile terminal such that a user can set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time. [0004]In order to achieve the aforementioned object, the present invention provides a method for controlling communication states of a mobile terminal comprising:[0005]the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; and[0006]the mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are not consistent, adjusting the current communication state to the communication state corresponding to the planned time period. [0007]Preferably, the method also comprises:[0008]the mobile terminal receiving authentication information input by the user, and detecting whether the authentication information is legal, and if yes, entering the specific setup interface. [0009]Preferably, the method also comprises:[0010]if the mobile terminal detects that the current time is in the planned time period, calculating duration from the current time to the end time of the planned time period; and[0011]maintaining the communication state corresponding to the planned time period in the duration. [0012]The present invention also provides a mobile terminal comprising:[0013]a setting module configured to receive and store a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface;[0014]a processing module configured to detect whether the current time is in the planned time period, if yes, detect whether the current communication state is consistent with the communication state corresponding to the planned time period stored in the setting module, and if they are not consistent, output a signal to a communication module; and[0015]the communication module configured to receive the signal from the processing module, and then adjust the current communication state to the communication state corresponding to the planned time period and stored in the setting module. [0016]Preferably, the mobile terminal also comprises an authentication module. [0017]The authentication module is configured to receive authentication information input by the user, and detecting whether the authentication information is legal, and if yes, output a signal to the setting module. [0018]The setting module is further configured to receive the signal of the authentication module and then enter the specific setup interface. [0019]Preferably, the mobile terminal also has the following features:[0020]the processing module is further configured to calculate duration from the current time to the end time of the planned time period if detecting that the current time is in the planned time period, and output the calculated duration to the communication module; and[0021]the communication module is further configured to receive the duration and maintain the communication state corresponding to the planned time period in the duration. [0022]Compared with the prior art, the present invention has the following advantages. [0023]The user can set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time. [0024]In the present invention, the communication states of the mobile terminal in different time periods are set by planning of the user's work and rest time, to reduce harm of radiation of the mobile communication terminal to the user on the basis of meeting basic communication functions. Moreover, due to reduction of network communications, standby time of the mobile communication terminal will certainly be prolonged greatly. [0025]The present invention, which is designed specifically for students, has broad market prospects and is particularly suitable to people in universities, high schools, junior middle schools, and elementary schools. BRIEF DESCRIPTION OF DRAWINGS [0026]FIG. 1 is a block diagram of a mobile terminal in accordance with an embodiment of the present invention; [0027]FIG. 2 is a flow chart of a method for controlling communication states of a mobile terminal in accordance with an embodiment of the present invention; and [0028]FIG. 3 is a flow chart of an application example of a method for controlling communication states of a mobile terminal in accordance with the present invention. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0029]Preferred embodiments of the technical scheme of the present invention will be further described below in detail in conjunction with the accompanying drawings. [0030]FIG. 1 is a block diagram of a mobile terminal in accordance with an embodiment of the present invention. As shown in FIG. 1, the mobile terminal 100 in accordance with the embodiment comprises a setting module 110, a processing module 120 and a communication module 130. [0031]The setting module 110 is configured to receive and store a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface. [0032]Specifically, the setup interface for time planning and communication states is added to the mobile terminal such that the user can set the time planning and the corresponding communication states in the setup interface. The setting module 110 receives the time planning and the corresponding communication state information input by the user, and stores the setting result into a file system. [0033]The processing module 120 is configured to detect whether the current time is in the planned time period stored by the setting module 110, if yes, detect whether the current communication state is consistent with the communication state corresponding to the planned time period stored in the setting module 110, and if they are not consistent, output a signal to the communication module 130. [0034]The communication module 130 is configured to receive the signal from the processing module 120, and then adjust the current communication state to the communication state corresponding to the planned time period and stored in the setting module 110. [0035]For example, assuming that the mobile terminal is currently in a normal communication state, that is, the communication module 130 is in an on state. If the user sets a planned time period, and sets a communication state corresponding to the planned time period to be an off state, when the processing module 120 detects that the current time is in the time period set by the user, the communication module 130 is turned off. [0036]Thus, for the mobile terminal in accordance with this embodiment, the user can set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time. [0037]Preferably, the mobile terminal in accordance with this embodiment might also comprise an authentication module 140, which is configured to receive authentication information input by the user, detect whether the authentication information is legal, and if it is legal, output a signal to the setting module 110. After receiving the signal from the authentication module 140, the setting module 110 enters the specific setup interface. That is, a user (such as, parents) who has passed the authentication (for example, by entering a user name, password, etc.) can access to the planed setup page, otherwise the user is refused to access to the planed setup interface. [0038]Preferably, the processing module 120 is further configured to calculate duration from the current time to the end time of the planned time period if detecting that the current time is in the planned time period, and then output the calculated duration to the communication module 130. After the communication module 130 receives the duration information, it maintains the communication state corresponding to the planned time period in the duration. [0039]For example, if the user sets to close communication from 9:00 am to 10:00 am and the processing module 120 detects that the current time is in the planned time period at 9 o'clock in the morning and calculates the duration of one hour from the current time to the end time of the planned time period, then the communication module 130 will maintain the closed state for one hour and return to the normal communication after one hour. [0040]FIG. 2 is a flow chart of a method for controlling communication states of a mobile terminal in accordance with an embodiment of the present invention. As shown in FIG. 2, the method in accordance with the embodiment comprises the following steps. [0041]In S11, the mobile terminal receives authentication information input by a user. [0042]For example, the user inputs a user name, password, etc. [0043]In S12, whether the authentication information is legal is detected, if it is legal, a planed setup interface is entered, and step S13 is performed, otherwise, the planed setup interface is refused to be entered. [0044]In S13, the mobile terminal receives the planned time period input by the user and planning information of a communication state corresponding to the planned time period through the planned setup interface, and then stores the planning information. [0045]Assuming that the planning information input by the user contains a planned time period such as from 9:00 am to 10:00 am, and a communication state, such as closed communication. [0046]In S14, the mobile terminal detects whether the current time is in the planned time period, and if yes, step S15 is performed; otherwise, step S17 is performed. [0047]In S15, whether the current communication state is consistent with the stored communication state corresponding to the planned time period is detected, if they are not consistent, step S16 is performed; otherwise, step S17 is performed. [0048]In S16, the current communication state is adjusted to the communication state corresponding to the planned time period. [0049]In S17, the current communication state is maintained. [0050]If the current time is 8:00 am, the normal communication state is maintained; and if the current time is 9:00 am, the communication is closed. [0051]Preferably, after the mobile terminal detects that the current time is in the planned time period, the method further comprises the following steps. [0052]In S18, the duration from the current time to the end time of the planned time period is calculated. [0053]For example, the duration is from 9:00 am to 10:00 am, i.e., one hour. [0054]In S19, the communication state corresponding to the planned time period in the duration is maintained. [0055]For example, the communication closed state is maintained for one hour, and then the normal communication state is restored after one hour. [0056]An application example of a method for controlling communication states of a mobile terminal according to the present invention will be described below. [0057]In this application example, according to features of students, students' class time and non-class time are divided by semester, daily class time and the like. For example, the following items are set through interfaces of the mobile terminal. [0058]1. The following several time periods are set. [0059]a) Semester time periods are set. [0060]The students' school time periods are set. For example, school time of a student is set as follows: NameStartEndFirst semester2009 Mar. 12009 Jul. 1Second semester2009 Sep. 12010 Jan. 20. . .. . .. . . [0061]Saturdays and Sundays are rest days and can be marked individually. [0062]b) Class time is set. [0063]For example, the class time in a school is set as follows: Class timeStartEndFirst class in the morning 8:00 8:45Second class in the morning 9:00 9:45Third class in the morning10:0010:45Fourth class in the morning11:0011:45First class in the afternoon14:0014:45Second class in the afternoon15:0015:45Third class in the afternoon16:0016:45. . .. . . [0064]c) Sleep time periods are set. [0065]The sleep time periods in the afternoon and at night are set as follows: Sleep time periodStartEndAfternoon13:0014:00Night22:0006:30 [0066]d) Special time periods are set. [0067]For example, when there is emergency at home, kids are required to be connected at any time. For example: Special time periodStartEndEmergency at home2009 Jan. 018:002009 Jan. 0120:00Grandpa is coming2009 Dec. 058:002009 Dec. 0520:00. . .. . .. . . [0068](2) Communication states, mainly communication states of the mobile communication terminal in different time periods, are set. [0069]The above time periods mainly include class time, sleep time, special time, and other time. Setting items of the communication states include normal communication and closed communication. The closed communication means that a communication module (a RF module) in the mobile terminal is turned off, and the mobile terminal can neither receive nor send messages. [0070]For example, a student's communication states are set as follows: Time periodSetting of communication statesSpecial timeNormal communicationClass timeClosed communicationSleep timeClosed communicationOther timeNormal communication [0071]FIG. 3 illustrates a flow chart of a method for controlling communication states of a mobile terminal in accordance with the application example, which comprises the following steps. [0072]In S201, the mobile terminal is turned on. [0073]In S202, it is detected that the current time is in which planned time period set above, such as, the semester time period, the daily class time period, special time period, or sleep time period. [0074]In S203, it is determined whether the current communication state is consistent with the set planned communication state, if they are inconsistent, the current communication state is adjusted to the set planned communication state; otherwise, the current communication state is maintained unchanged. [0075]For example, the communication module at the current time is turned on or off. [0076]In S204, the duration from the current time to a time point at which the recent communication state needs to be changed is calculated. [0077]In S205, the current communication state is maintained in the duration; after the duration, step S202 is performed. [0078]In S206, if the user turns the mobile terminal off, the operation ends. [0079]In this application example, the time planning function is added to the common mobile communication terminal, that is, one day of students can be divided into different time periods, such as class time periods, sleep time periods, special time periods and other time periods. In the class time periods and sleep time periods, by turning off the communication module in the mobile terminal, the students in the class will not be disturbed by ring tones of incoming calls, SMS, MMS, and the like, thus ensuring the normal teaching order in the classroom; meanwhile, due to turning off of the communication module, radiation of the mobile communication terminal is reduced to zero. In the other time periods, the communication module of the mobile terminal is turned on to meet people's communication requirements. In the special time periods, for example, when there is an emergency at home, the communication module can be set to be in an on state all the time to ensure convenient communication with outside in the special time periods. [0080]As described above, by planning the students' time, communication states of mobile communication terminals in different time periods can be set to greatly reduce radiation of the mobile communication terminals to users. Due to the reduction of network traffic, the electricity consumption will certainly be decreased such that standby time of the mobile communication terminals can be increased greatly. [0081]Because the mobile terminal in accordance with the present invention can greatly reduce the radiation to students, teachers and students in the class, teachers and students will not be disturbed in class by incoming calls, text messages, and the like, and normal communication can be maintained after class, it will certainly especially liked by the majority of students, teachers and communities. [0082]The present invention can be applied to not only students, but also all users who need to set the corresponding communication states according to different time periods. [0083]The above embodiments are only examples of illustrating a method for controlling communication states of a mobile terminal in accordance with the present invention and should not be construed as limitation of the present invention. Various equivalent variations or substitutions may be made according to description of the technical scheme of the present invention and its preferred embodiments, and all these equivalent variations and substitutions should be covered within the protection scope of the claims of the present invention. INDUSTRIAL APPLICABILITY [0084]The technical solution of the present invention can let the users set time planning and the corresponding communication states in the mobile terminal according to their work or learning needs, in order to avoid disturbance of incoming calls and the SMS when they are unavailable, while to be able to communicate properly in their leisure time, thus it is particularly applicable to student crowds.(String), 技术领域 [0001] 控制 移动终端通信状态的方法及移动终端技术领域本发明涉及移动通信领域,尤其涉及一种控制移动终端通信状态的方法及移动终端。 相关技术背景 [0002] 在当今信息社会,信息和通信的作用越来越重要。 不同的用户对移动终端(如手机、小灵通(Personal Handy-phone System,PHS))的功能需求不同。 当业务繁忙或需要安静处理一些事务时,来电或短信肯定会影响用户的注意力。 例如,在数十名学生聚集在一起的教室中,上课时间移动通信终端的短信和MMS(Multimedia Messaging Service)通知消息会严重影响学生的课堂注意力和教师的教学过程。 此外,课堂内移动终端的交叉辐射会严重影响学生的身体健康。 发明内容 [0003] 本发明的目的在于提供一种控制移动终端通信状态的方法及移动终端,使得用户可以根据自己的工作或学习需要,在移动终端中设置时间规划和相应的通信状态,以便 避免来电、短信等不必要的打扰,同时保持闲暇时间的正常沟通。 [0004] 为实现上述目的,本发明提供了一种移动终端通信状态控制方法,包括: [0005]移动终端通过特定的设置界面接收并存储用户输入的计划时间段以及与计划时间段对应的通信状态; 和[0006] 移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态 到计划时间段对应的通信状态。 [0007] 优选地,该方法还包括: [0008] 移动终端接收用户输入的认证信息,检测认证信息是否合法,若合法则进入具体设置界面。 [0009] 优选地,该方法还包括: [0010] 若移动终端检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长; 和[0011] 在duration中保持计划时间段对应的通信状态。 [0012] 本发明还提供了一种移动终端,包括: [0013] 设置模块,用于接收并存储用户通过特定设置界面输入的计划时间段和与计划时间段对应的通信状态;[0014] 处理模块,用于检测当前时间是否在计划时间段内,如果是,则检测当前通信状态与设置模块中存储的计划时间段对应的通信状态是否一致,如果不一致 ,输出信号给通信模块; 和[0015] 通讯模块,用于接收来自处理模块的信号,将当前的通讯状态调整为设置模块中存储的计划时间段对应的通讯状态。 [0016] 优选地,移动终端还包括鉴权模块。 [0017] 鉴权模块用于接收用户输入的鉴权信息,检测鉴权信息是否合法,若合法,则向设置模块输出信号。 [0018] 设置模块还用于接收鉴权模块的信号,进入特定的设置界面。 [0019] 优选地,所述移动终端还具有以下特征: [0020] 处理模块,还用于若检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长,并将计算出的时长输出给通信模块。 和[0021] 通信模块还用于接收时长,并在该时长内保持计划时间段对应的通信状态。 [0022] 与现有技术相比,本发明具有以下优点。 [0023] 用户可以根据自己的工作或学习需要,在自己的移动终端中设置时间规划和相应的通讯状态,从而在闲暇时间保持正常通讯的同时,避免来电和短信的不必要的打扰。 [0024] 本发明通过规划用户的作息时间,设置移动终端在不同时段的通信状态,在满足基本通信功能的基础上,降低移动通信终端的辐射对用户的危害。 而且,由于网络通信的减少,移动通信终端的待机时间势必会大大延长。 [0025] 本发明专为学生设计,具有广阔的市场前景,特别适合大中小学生使用。 附图说明 [0026] 图1是根据本发明一个实施例的移动终端的框图; [0027] 图2为本发明实施例的移动终端通信状态控制方法的流程图; 和 [0028] 图3为本发明移动终端通信状态控制方法的应用实例流程图。 本发明的优选实施例 [0029]下面结合附图对本发明技术方案的优选实施方式作进一步详细说明。 [0030] 图1是根据本发明实施例的移动终端的框图。 如图1所示,移动端 100 根据该实施例包括设置模块 110 , 处理模块 120 和通信模块 130 . [0031] 设置模块 110 用于通过特定的设置界面接收并存储用户输入的计划时间段以及与计划时间段对应的通信状态。 [0032] 具体地,在移动终端中增加时间计划和通信状态的设置界面,使得用户可以在设置界面中设置时间计划和相应的通信状态。 设置模块 110 接收用户输入的时间规划和相应的通信状态信息,并将设置结果存储到文件系统中。 [0033] 处理模块 120 用于检测当前时间是否在设置模块存储的计划时间段内 110 ,若是,则检测当前通信状态是否与设置模块中存储的计划时间段对应的通信状态一致 110 , 不一致则输出信号给通讯模块 130 . [0034] 通信模块 130 用于接收来自处理模块的信号 120 ,然后将当前的通信状态调整为设置模块中存储的计划时间段对应的通信状态 110 . [0035] 例如,假设移动终端当前处于正常通信状态,即通信模块 130 处于开启状态。 若用户设置了一个计划时间段,并将该计划时间段对应的通信状态设置为关闭状态,则当处理模块 120 通信模块检测到当前时间在用户设置的时间段内, 130 被关闭。 [0036] 因此,对于本实施例的移动终端,用户可以根据自己的工作或学习需要,在自己的移动终端中设置时间规划和相应的通讯状态,从而在保持正常工作的同时,避免来电和短信的不必要的打扰。 闲暇时的交流。 [0037] 优选地,本实施例的移动终端还可以包括鉴权模块 140 ,用于接收用户输入的认证信息,检测认证信息是否合法,如果合法则输出信号给设置模块 110 . 收到认证模块的信号后 140 , 设置模块 110 进入具体设置界面。 即通过认证(如输入用户名、密码等)的用户(如家长)可以访问规划设置页面,否则拒绝访问规划设置页面 界面。 [0038] 优选地,处理模块 120 还用于若检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长,将计算出的时长输出给通信模块 130 . 通信模块后 130 接收到时长信息,在时长内保持计划时间段对应的通信状态。 [0039] 例如,用户设置上午9:00-10:00关闭通讯,处理模块 120 早上9点检测到当前时间在计划时间段内,计算当前时间到计划时间段结束时间一小时的时长,然后通信模块 130 将保持关闭状态一小时,一小时后恢复正常通讯。 [0040] 图2是根据本发明实施例的控制移动终端通信状态的方法的流程图。 如图2所示,根据本实施例的方法包括以下步骤。 [0041] 在 S 11 ,移动终端接收用户输入的认证信息。 [0042] 例如,用户输入用户名、密码等。 [0043] 在 S 12 ,检测认证信息是否合法,如果合法,则进入规划的设置界面,步骤S 13 执行,否则拒绝进入规划的设置界面。 [0044] 在 S 13 移动终端通过计划设置界面接收用户输入的计划时间段和计划时间段对应的通信状态的计划信息,然后存储计划信息。 [0045] 假设用户输入的计划信息包含计划时间段,例如上午9:00至10:00,以及通信状态,例如封闭通信。 [0046] 在 S 14 ,移动终端检测当前时间是否在计划时间段内,若是,则执行步骤S 15 执行; 否则,步骤S 17 被执行。 [0047] 在 S 15 ,检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,步骤S 16 执行; 否则,步骤S 17 被执行。 [0048] 在 S 16 ,将当前通信状态调整为规划时间段对应的通信状态。 [0049] 在 S 17 , 保持当前的通信状态。 [0050] 若当前时间为上午8:00,则保持正常通信状态; 如果当前时间是上午9:00,则关闭通信。 [0051] 优选地,在移动终端检测到当前时间在计划时间段内之后,该方法还包括以下步骤。 [0052] 在 S 18 ,计算当前时间到计划时间段结束时间的时长。 [0053] 例如,持续时间为上午9:00至上午10:00,即一小时。 [0054] 在 S 19 ,维持duration中计划时间段对应的通信状态。 [0055] 例如保持通信关闭状态一小时,一小时后恢复正常通信状态。 [0056] 下面描述根据本发明的控制移动终端通信状态的方法的应用示例。 [0057] 在本应用实例中,根据学生的特点,按学期、每天的上课时间等划分学生的上课时间和非上课时间。 例如,通过移动终端的界面设置以下项目。 [0058] 1、设置以下几个时间段。 [0059] a) 设置学期时间段。 [0060] 设置学生的上课时间段。 例如,某学生的上课时间设置如下: 姓名 开始 结尾 第一学期 2009年3月1日 2009年7月1日 第二学期 2009年9月1日 2010年1月20日 . . . . . . . . . [0061] 周六和周日为休息日,可单独标注。 [0062] b) 上课时间已定。 [0063] 比如某学校的上课时间是这样设置的: 上课时间 开始 结尾 早上第一节课  8:00  8:45 上午第二节课  9:00  9:45 上午第三节课 10:00 10:45 上午第四节课 11:00 11:45 下午第一节课 14:00 14:45 下午第二节课 15:00 15:45 下午第三节课 16:00 16:45 . . . . . . [0064] c) 设置休眠时间段。 [0065] 下午和晚上的睡眠时间段设置如下: 休眠时间段 开始 结尾 下午 13:00 14:00 夜晚 22:00 06:30 [0066] d) 设置特殊时间段。 [0067] 比如家里有急事,要求孩子随时接通。 例如: 特殊时期 开始 结尾 家里有急事 2009年1月1日 8:00 2009年1月1日 20:00 爷爷来了 2009年12月05日 8:00 2009年12月05日 20:00 . . . . . . . . . [0068] (2)设置通信状态,主要是设置移动通信终端在不同时间段的通信状态。 [0069]以上时间段主要包括上课时间、睡眠时间、特殊时间、其他时间。 通信状态的设置项包括正常通信和封闭通信。 关闭通信是指移动终端中的通信模块(射频模块)被关闭,移动终端既不能接收也不能发送消息。 [0070] 例如,学生的通信状态设置如下: 时间段 通讯状态设定 特殊时期 正常沟通 上课时间 封闭式沟通 睡觉时间 封闭式沟通 其他时间 正常沟通 [0071] 图3示出了根据本应用示例的控制移动终端通信状态的方法的流程图,包括以下步骤。 [0072] 在 S 201 ,移动终端开启。 [0073] 在 S 202 ,检测到当前时间处于上述设定的哪个计划时间段,例如学期时间段、每日上课时间段、特殊时间段或睡眠时间段。 [0074] 在 S 203 、判断当前通信状态与设定的计划通信状态是否一致,若不一致,则将当前通信状态调整为设定的计划通信状态; 否则,保持当前通信状态不变。 [0075] 例如,当前时间的通信模块处于打开或关闭状态。 [0076] 在 S 204 ,计算从当前时间到需要改变最近通信状态的时间点的时长。 [0077] 在 S 205 , 持续时间内保持当前通信状态; 持续时间后,步骤 S 202 被执行。 [0078] 在 S 206 ,如果用户关闭移动终端,则操作结束。 [0079] 本应用实例为普通移动通信终端增加了时间规划功能,即可以将学生的一天划分为不同的时间段,如上课时间段、睡眠时间段、特殊时间段等。 . 在上课时间段和睡眠时间段,通过关闭移动终端中的通讯模块,上课的学生不会受到来电、短信、彩信等铃声的打扰,保证了正常的教学 课堂秩序; 同时,由于通信模块的关闭,移动通信终端的辐射降为零。 在其他时间段,移动终端的通讯模块处于开启状态,以满足人们的通讯需求。 在特殊时间段,例如家中有紧急情况时,可以将通讯模块设置为一直处于开启状态,以保证特殊时间段与外界的方便通讯。 [0080] 如上所述,通过规划学生的时间,可以设置移动通信终端在不同时间段的通信状态,可以大大降低移动通信终端对用户的辐射。 由于网络流量的减少,必然会降低用电量,从而大大增加移动通信终端的待机时间。 [0081] 由于根据本发明的移动终端可以大大降低对学生、老师和学生在课堂上的辐射,老师和学生在课堂上不会受到来电、短信等的干扰,可以正常交流。 课后维护,一定会特别受到广大学生、老师和社区的喜爱。 [0082] 本发明不仅适用于学生,也适用于所有需要根据不同时间段设置相应通信状态的用户。 [0083]以上实施例仅是举例说明根据本发明的控制移动终端的通信状态的方法,不应理解为对本发明的限制。 根据本发明的技术方案及其优选实施例的说明,可以做出各种等同变化或替换,这些等同变化和替换均应包含在本发明的权利要求的保护范围之内。 工业实用性 [0084] 本发明的技术方案可以让用户根据自己的工作或学习需要在移动终端中设置时间计划和相应的通讯状态,从而避免在无法接听电话和短信时受到打扰,同时 能够在闲暇时间进行适当的交流,因此特别适用于学生人群。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101778171A(String), EP2519072A1(String), EP2519072A4(String), US20120309450A1(String), WO2011094996A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101778171A(String), EP2519072A1(String), EP2519072A4(String), US20120309450A1(String), WO2011094996A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120309450A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101778171A(String), EP2519072A1(String), EP2519072A4(String), US20120309450A1(String), WO2011094996A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270697(Integer), CN101778171A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270697(Integer), EP2519072A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270697(Integer), EP2519072A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270697(Integer), US20120309450A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270697(Integer), WO2011094996A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.117 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120309450A1(String), US20120309450A1(String), 1354723200(Integer), 270697(Integer), 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.126 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.128 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185020(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185020(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.137 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.139 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.141 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.143 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.143 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185020(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.145 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185020(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.156 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10114522B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method of controlling display of display device by mobile terminal and mobile terminal for the same(String), 移动终端控制显示设备显示的方法及移动终端(String), US10114522B2(String), Disclosed is a method of controlling a screen display of an external display device by a mobile terminal, including when a connection between the mobile terminal and the external display device is performed, transmitting image data to the external display device and displaying an image displayed in the mobile terminal in the external display device, and when a selection command for one of objects included in the image data is input in the mobile terminal, moving a position of the image displayed in the external display device and then controlling such that the image is displayed together with an image of the object for the selection command.(String), 公开了一种通过移动终端控制外部显示设备的屏幕显示的方法,包括在移动终端与外部显示设备之间进行连接时,将图像数据发送到外部显示设备,并显示在外部显示设备中显示的图像。 移动终端在外部显示设备中,并且当在移动终端中输入图像数据中包括的对象之一的选择命令时,移动外部显示设备中显示的图像的位置,然后进行控制以显示图像 连同用于选择命令的对象的图像。(String), US13/872783(String), 1367164800(Integer), US10114522B2(String), 1540828800(Integer), 1540828800(Integer), 美国(String), 4(Integer), KR(String), 5(Integer), 30(Integer), CN101917673A | CN102238280A | CN102301738A | CN102447969A | EP2385689A1 | KR1020120015931A | US20030069923A1 | US20070211734A1 | US20090092185A1 | US20100299436A1 | US20100313143A1 | US20110075031A1 | US20110099512A1 | US20110216064A1 | US20110268218A1 | US20110283334A1 | US20120017236A1 | US20120019674A1 | US20120038541A1 | US20120042102A1 | US20120088447A1 | US20120088548A1 | US20120131458A1 | US20130040623A1 | US20130094423A1 | US20130103446A1 | US20130125018A1 | WO2010143843A2 | WO2012026750A2(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.213 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.213 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.213 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185021(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.215 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.216 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\a43dd71e79fd451893711bd8e3e0a802.png(String), 185021(Integer), a43dd71e79fd451893711bd8e3e0a802.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of controlling display of display device by mobile terminal and mobile terminal for the same(String), 移动终端控制显示设备显示的方法及移动终端(String), US10114522B2(String), Disclosed is a method of controlling a screen display of an external display device by a mobile terminal, including when a connection between the mobile terminal and the external display device is performed, transmitting image data to the external display device and displaying an image displayed in the mobile terminal in the external display device, and when a selection command for one of objects included in the image data is input in the mobile terminal, moving a position of the image displayed in the external display device and then controlling such that the image is displayed together with an image of the object for the selection command.(String), 公开了一种通过移动终端控制外部显示设备的屏幕显示的方法,包括在移动终端与外部显示设备之间进行连接时,将图像数据发送到外部显示设备,并显示在外部显示设备中显示的图像。 移动终端在外部显示设备中,并且当在移动终端中输入图像数据中包括的对象之一的选择命令时,移动外部显示设备中显示的图像的位置,然后进行控制以显示图像 连同用于选择命令的对象的图像。(String), US13/872783(String), 1367164800(Integer), US10114522B2(String), 1540828800(Integer), 1540828800(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 5(Integer), 30(Integer), CN101917673A | CN102238280A | CN102301738A | CN102447969A | EP2385689A1 | KR1020120015931A | US20030069923A1 | US20070211734A1 | US20090092185A1 | US20100299436A1 | US20100313143A1 | US20110075031A1 | US20110099512A1 | US20110216064A1 | US20110268218A1 | US20110283334A1 | US20120017236A1 | US20120019674A1 | US20120038541A1 | US20120042102A1 | US20120088447A1 | US20120088548A1 | US20120131458A1 | US20130040623A1 | US20130094423A1 | US20130103446A1 | US20130125018A1 | WO2010143843A2 | WO2012026750A2(String), \20230420\a43dd71e79fd451893711bd8e3e0a802.png(String), 16(Integer), 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 1. A method of controlling a display of an external display device by a mobile terminal, the method comprising:transmitting, by the mobile terminal, when a connection with the external display device is performed, second content that is identical to first content displayed on the mobile terminal to the external display device, wherein the second content is displayed on the external display device, and wherein the second content occupies a portion of the external display such that the second content is mirrored based on a screen direction of the mobile terminal;receiving, by the mobile terminal, a touch input, through a touch screen of the mobile terminal, for selecting one object of a plurality of objects included in the first content displayed on the mobile terminal; anddetermining, by the mobile terminal, a screen direction of the mobile terminal;transmitting, by the mobile terminal, based on the determined screen direction being a vertical direction, information on third content corresponding to the selected object to be displayed in an empty space in order to fill the empty screen space not occupied by the second content on the external display device, to the external display device; andcontrolling, by the mobile terminal, the external display device to display the second content on a first area of the external display device and the third content corresponding to the selected object on a second area of the external display device.(String), 1.一种移动终端控制外接显示设备显示的方法,该方法包括:移动终端在与外部显示设备进行连接时,向外部显示设备发送与移动终端上显示的第一内容相同的第二内容,其中,第二内容显示在外部显示设备上,以及其中,第二内容占据外部显示器的一部分,使得第二内容基于移动终端的屏幕方向被镜像;移动终端通过移动终端的触摸屏接收触摸输入,用于选择移动终端显示的第一内容包括的多个对象中的一个对象;和移动终端确定移动终端的屏幕方向;移动终端基于确定的屏幕方向为竖直方向,发送选择的对象对应的第三内容的信息,在空白处显示,以填充第二内容未占用的空白屏幕空间外接显示设备,到外接显示设备;和移动终端控制外接显示设备在外接显示设备的第一区域显示第二内容,在外接显示设备的第二区域显示与选择的对象对应的第三内容。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 2. The method of claim 1, wherein receiving, by the mobile terminal, the selection of the one object comprises receiving an input for designating a display position of the third content on the external display device.(String), 2.如权利要求1所述的方法,其中由移动终端接收对一个对象的选择包括接收用于指定第三内容在外部显示设备上的显示位置的输入。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 3. The method of claim 2, wherein the input for designating the display position of the third content indicates a direction in which drag and drop according to a touch input is generated.(String), 3.如权利要求2所述的方法,其中用于指定第三内容的显示位置的输入指示产生根据触摸输入的拖放的方向。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 4. The method of claim 3, further comprising, when the input for designating the display position of the third content is made, transmitting a command for designating the display position of the third content to the external display device and displaying the third content together with the second content by moving a display position of the second content in the external display device.(String), 4.如权利要求3所述的方法,还包括,当进行了用于指定第三内容的显示位置的输入时,将用于指定第三内容的显示位置的命令发送到外部显示设备并且通过移动第二内容的显示位置来与第二内容一起显示第三内容外部显示设备中的内容。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 5. The method of claim 4, wherein the second content is moved to and displayed in a part of a screen in an opposite direction of the direction in which the drag and drop is generated, and the third content is displayed in a part of the screen in the direction in which the drag and drop is generated.(String), 5.如权利要求4所述的方法,其中将第二内容移动到与产生拖放方向相反的部分屏幕显示,将第三内容显示在产生拖放方向的部分屏幕。滴产生。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 6. The method of claim 1, wherein the information on the third content includes at least one of a content type of the third content and an address to receive the third content.(String), 6.如权利要求1所述的方法,其中第三内容的信息包括第三内容的内容类型和接收第三内容的地址中的至少一种。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.258 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 7. The method of claim 6, wherein the content type indicates one of web content, media content, and advertisement content according to a type of the third content.(String), 7.如权利要求6所述的方法,其中内容类型根据第三内容的类型指示网页内容、媒体内容和广告内容中的一种。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 8. The method of claim 1, further comprising performing a connection with the external display device based on a Wi-Fi Direct technique.(String), 8.如权利要求1所述的方法,还包括基于Wi-FiDirect技术与外部显示设备进行连接。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 9. The method of claim 1, wherein the second content is transmitted based on a Real Time Streaming Protocol (RTSP).(String), 9.如权利要求1所述的方法,其中第二内容基于实时流协议(RTSP)传输。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 10. The method of claim 1, wherein transmitting, by the mobile terminal, the information on the third content to the external display device comprises:configuring, when the one object is selected, a combined screen to display the second content and the third content together on the external display device; andtransmitting information on the combined screen to the external display device.(String), 10.如权利要求1所述的方法,其中移动终端向外接显示设备发送第三内容信息包括:在选择一个对象时,配置一个组合的屏幕以在外部显示设备上显示第二个内容和第三个内容;和将组合屏幕上的信息传输到外部显示设备。11、一种控制外接显示设备显示的移动终端包括:通信电路;触摸屏;和处理器配置为:在触摸屏上显示第一内容;通过通讯电路传送与第一内容相同的第二内容至外部显示装置,其中第二内容显示在外部显示装置上,且其中第二内容占据外部显示器的一部分,使得第二内容基于镜像在移动终端的屏幕方向上;通过触摸屏接收用于选择移动终端上显示的第一内容中包括的多个对象中的一个对象的触摸输入确定移动终端的屏幕方向;基于确定的屏幕方向为垂直方向,使用通信电路发送关于与选择的对象对应的第三内容的信息,以在空白空间中显示以填充未被第二内容占据的空白屏幕空间外部显示设备,到外部显示设备,以及控制外部设备在外部显示设备的第一区域上显示第二内容并且在外部显示设备的第二区域上显示与选择的对象对应的第三内容。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 11. A mobile terminal for controlling a display of an external display device comprising:a communication circuit;a touch screen; anda processor configured to:display first content on the touch screen;transmit second content identical to the first content to the external display device through the communication circuit, wherein the second content is displayed on the external display device, and wherein the second content occupies a portion of the external display such that the second content is mirrored based on a screen direction of the mobile terminal;receive, through the touch screen, a touch input for selecting one object of a plurality of objects included in the first content displayed on the mobile terminaldetermine a screen direction of the mobile terminal;transmit, using the communication circuit, based on the determined screen direction being a vertical direction, information on a third content corresponding to the selected object to be displayed in an empty space in order to fill the empty screen space not occupied by the second content on the external display device, to the external display device, andcontrol the external device to display the second content on a first area of the external display device and third content corresponding to the selected object on a second area of the external display device.(String), 12.如权利要求11所述的移动终端,其中通信电路提供显示网页的网页内容,并且提供媒体内容的数字生活网络联盟(DLNA)模块。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 12. The mobile terminal of claim 11,wherein the communication circuit provides web content showing a web page, anda Digital Living Network Alliance (DLNA) module which provides media content.(String), 13.如权利要求11所述的移动终端,其中处理器还被配置为当通过触摸屏在外部显示设备上存在用于指定第三内容的显示位置的输入时,将用于指定第三内容的显示位置的命令发送到外部显示设备。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 13. The mobile terminal of claim 11, wherein the processor is further configured such that a command for designating a display position of the third content is transmitted to the external display device when there is an input for designating the display position of the third content on the external display device through the touch screen.(String), 14.如权利要求13所述的移动终端,其中用于指定第三内容的显示位置的输入指示通过触摸屏产生根据触摸输入的拖放的方向。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 14. The mobile terminal of claim 13, wherein the input for designating the display position of the third content indicates a direction in which a drag and drop according to a touch input is generated through the touch screen.(String), 15.如权利要求13所述的移动终端,其中将第二内容移动到与产生拖放方向相反的部分屏幕显示,将第三内容显示在产生拖放方向的部分屏幕。滴产生。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 15. The mobile terminal of claim 13, wherein the second content is moved to and displayed in a part of a screen in an opposite direction of the direction in which the drag and drop is generated, and the third content is displayed in a part of the screen in the direction in which the drag and drop is generated.(String), 16.如权利要求11所述的移动终端,其中第三内容的信息包括第三内容的内容类型和接收第三内容的地址中的至少一种。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185021(Integer), 16. The mobile terminal of claim 11, wherein the information on the third content includes at least one of a content type of the third content and an address to receive the third content.(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.383 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.384 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185021(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to Korean Application Serial No. 10-2012-0079367, which was filed in the Korean Intellectual Property Office on Jul. 20, 2012, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an apparatus and a method for controlling a display in a mobile terminal, and more particularly, to an apparatus and a method for controlling a display in an external display device in a mobile terminal having a function of outputting an image to the external display device. [0004]2. Description of the Related Art [0005]Interest in a digital broadcasting service for allowing a user to watch a digital broadcast while moving has increased as digital broadcasting and mobile communication technologies have evolved. Concurrently, a paradigm of the broadcasting service has been changed from the broadcasting service having a passive concept in which the user only passively watches the broadcast to the broadcasting service having an active concept in which the user identifies information on a cost of a product shown in the broadcast and purchases the product while directly watching the broadcast. [0006]Interest in a Digital Multimedia Broadcasting (DMB) service using a mobile terminal has also increased. The DMB service overcomes spatial and temporal limitations in watching the broadcast, but is not suitable for the broadcast simultaneously watched by several people due to screen size limitations. Accordingly, there have been increased releases of mobile terminals having a function of outputting a signal to a large sized display device, such as a TV. [0007]A current mobile terminal having a Television (TV) out function can output a video such as a broadcast displayed through a screen of the mobile terminal to an external display device. Accordingly, the user can watch the broadcast through a larger sized screen by outputting image data downloaded from a web server or photographed by a camera to the external display device. Examples of advanced mobile terminals having the TV out function include a Wi-Fi Display (WFD) and an airplay mirroring. [0008]For example, WFD refers to a technology in which a small sized screen of a mobile terminal 100 interworks with an external display device such as a TV 110 and then the same screen as that of the mobile terminal 100 is wirelessly displayed in the TV as illustrated in FIG. 1. When a user input is performed through the mobile terminal screen 100, a current screen is switched to a screen corresponding to the user input. The screen of the TV 110 is switched to the same screen as that of the mobile terminal 100. [0009]However, the same image as the image on the mobile terminal screen is located in the center of the TV screen. Accordingly, while the same image as the image on the mobile terminal screen is displayed on an entire TV screen when a screen direction of the mobile terminal is horizontal, the remaining parts except for the center of the TV screen remain as empty spaces, as illustrated in FIG. 1, when the screen direction is vertical. That is, due to a difference between a screen size of the mobile terminal and a screen size of the TV, the empty spaces are generated on the TV screen as illustrated in FIG. 1. [0010]Accordingly, there is a need in the art for the user to be able to control a screen display of the external display device in displaying an image on the mobile terminal screen on the external display device, to enable the user to receive a more vivid and efficient image in comparison with using the mobile terminal. SUMMARY OF THE INVENTION [0011]Accordingly, the present invention provides an apparatus and a method for controlling the screen display of the external display device by the mobile terminal. [0012]The present invention also provides an apparatus and a method for providing an efficient screen display of the external display device. [0013]In accordance with an aspect of the present invention, a method of controlling a display of a display device by a mobile terminal includes, when a connection with the display device is performed, transmitting second content equal to first content displayed on the mobile terminal to the display device, receiving a selection of one object of objects included in the first content displayed on the mobile terminal, and transmitting information on third content corresponding to a selected object to the display device so that the second content and the third content corresponding to the selected object are displayed together in the display device. [0014]In accordance with another aspect of the present invention, a mobile terminal for controlling a display of a display device includes a connector for performing a connection with the display device, a touch screen for displaying a first content and outputting a selection signal according to a selection of one object from objects included in the first content, and a controller for controlling such that second content equal to the first content is transmitted to the display device through the connector, and controlling such that when the selection signal according to the selection of the one object is transferred from the touch screen, information on a third content corresponding to the selected object is transmitted to the display device so that the second content and third content corresponding to the selected object are displayed together on the display device. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0016]FIG. 1 illustrates a TV screen when a screen of a conventional mobile terminal is mirrored; [0017]FIG. 2 illustrates an internal block diagram of a first device and a second device according to an embodiment of the present invention; [0018]FIG. 3 illustrates an operation between the first device and the second device to control a screen display of the second device according to a first embodiment of the present invention; [0019]FIG. 4 illustrates an example for describing a method of the operation of FIG. 3; [0020]FIG. 5 illustrates an operation between the first device and the second device to control the screen display of the second device according to a second embodiment of the present invention; [0021]FIG. 6 illustrates the operation between the first device and the second device to control the screen display of the second device according to a third embodiment of the present invention; [0022]FIG. 7 illustrates an example for describing a method of the operation of FIG. 6; [0023]FIG. 8 illustrates an operation between the first device and the second device to control the screen display of the second device according to a fourth embodiment of the present invention; and [0024]FIG. 9 illustrates an example for describing a method of the operation of FIG. 8. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0025]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, the same elements will be designated by the same reference numerals although they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted for the sake of clarity and conciseness. [0026]The present invention provides a method of controlling a screen display of an external display device in a mobile terminal. To this end, the present invention includes a process of controlling such that a mobile terminal is connected with a neighboring external display device, image data is transmitted to the external display device to display an image displayed on a screen of the mobile terminal on the external display device, and a position of the image displayed on the external display device is moved and the image is displayed with an object image for the selection command when a selection command for one of objects included in the image data is input on the mobile terminal. Accordingly, it is possible to efficiently control an output screen of the external display device. [0027]FIG. 2 illustrates an internal block diagram of a first device and a second device according to an embodiment of the present invention. In FIG. 2, a first device 200 is the mobile terminal supporting an image viewing function such as a smart phone, a mobile phone, or a tablet PC, and a second device 230 is the external display device, such as a TV, having a larger sized screen than a screen of the first device 200. [0028]The first device 200 includes a display unit 205, a web browser module 210, a Digital Living Network Alliance (DLNA) module 215, a Wi-Fi Display (WFD) connector 220, and a controller 225. [0029]The display unit 205 may be implemented by a Liquid Crystal Display (LCD) panel, and operates as an input means when the LCD panel is implemented in a touch screen type. The display unit 205 serves to display information input by or provided to the user, as well as various types of menus of the mobile terminal. When the display unit 205 is implemented in the touch screen type, an input signal is output to the controller 225 if there is a touch input from the user. The controller 225 identifies an input type by means of the signal input through the touch screen, and determines, for example, a hold, a drag, and a drop. [0030]When an Internet browser is operated according to a request of the user, the web browser module 210 accesses Uniform Resource Locator (URL) information input to an Internet address window through a web server to generate a web page according to a received packet. The web browser module 210 provides web content showing the web page to the controller 225. [0031]The DLNA module 215 provides media content to the controller 225 in order to transmit the media content, such as a video, to the second device 230 in a streaming type. The DLNA module 215 shares the media content with the second device 230, to allow the user to continuously watch the media content stored in the first device 200 in the second device 230. [0032]The WFD connector 220 searches for the neighboring second device 230 which is available for a Wi-Fi Direct service. When the second device 230 is found, the WFD connector 220 serves to connect the first device 200 with the second device 230 through a process of exchanging a device capability with the second device 230. [0033]The controller 225 controls a general operation within the first device 200. Specifically, the controller 225 controls such that contents such as web content from the web browser module 210 or media content from the DLNA module 215 are transmitted to the second device 230 through the WFD connector 220 based on a Real Time Streaming Protocol (hereinafter RTSP). [0034]The controller 225 determines an input signal form from the user through the display unit 205 to control the first device 200 in accordance with the determination. For example, when the user inputs a selection command for an object included in an image displayed on the display unit 205, the controller 225 controls the web browser module 210 or the DLNA module 215 so that detailed data on the selected object is displayed. In addition, the controller 225 transmits currently displayed content to the second device 230, and a transmission type of the content follows a streaming type, so that a detailed description thereof will be omitted. Actual content may be transmitted according to the streaming type, or alternatively, only a content address to receive the content may be transmitted and then the second device 230 may access the content address to display the same content. [0035]After the same content as the currently displayed content is transmitted to be displayed on the second device 230 in the streaming type, if a selection command for one of the objects included in the content is input, detailed data on the selected object is transmitted to the second device 230. The detailed data on the selected object is inserted into a parameter based on an RTSP and then transmitted. For example, the detailed data on the selected object includes actual content data, an address to receive the content data, a display position, and a content type. [0036]When the user touches a particular content or a web page among lists found through the web browser with his/her finger and then performs a drag and drop leftwards, the first device 200 transmits to the second device 230 a signal for instructing to prepare such that the particular content or the web page is displayed in a left side of the screen of the second device 230. In response to the signal, content displayed in a center of the screen moves in order to display the particular content or the web page in the left side of the screen of the second device 230. [0037]The operation performed in the second device 230 will be described below in detail. [0038]The second device 230 includes a display unit 235, a WFD connector 240, a content type processor 245, a content position processor 250, and a controller 255. [0039]The controller 255 receives the same content as the content displayed on the first device 200 in the streaming type and controls such that the content is displayed on the display unit 235. When a command for designating a display position of the selected object based on the RTSP, that is, the selected content is received through the WFD connector 240, the controller 255 moves the content on a current screen to secure a screen space where the selected content is rendered, in response to the command. When the screen space is secured, the controller 255 controls such that selected content is displayed on the display unit 235 with the previous content. [0040]Specifically, the controller 255 divides the screen into two spaces to simultaneously display the current content and the newly selected content, and controls such that the current content and the newly selected content are disposed in the divided screen spaces, respectively. The current content which had been displayed in the center is disposed in the screen space corresponding to an opposite side of the display position of the selected content among the divided screen spaces. [0041]A size of each of the divided screen spaces can be variously set. For example, the screen may be divided to maintain a display magnification of the current content which had displayed in the center of the screen, and in this case, the newly selected content is displayed in the remaining screen space other than the screen space displaying the current content. In order to display the current content and the newly selected content with the same size, the screen may be divided into screen spaces having the same size. A method of dividing the screen for displaying the content is not limited thereto. [0042]Accordingly, the display unit 235 may display an image changed according to an object selection in the first device 200 as well as display the same image as the image displayed through the display unit 205 of the first device 200. [0043]The content type processor 245 determines a type of the content received from the first device 200 and provides the content to the controller 255. The content type refers to a type of contents such as web content and media content, and for example, the web content may be set to “web”, the media content may be set to a “video”, and an advertisement may be set to an “ads video”. [0044]When a content address is included in the detailed data on the selected object, the content position processor 250 accesses the web server corresponding to the content address, receives content corresponding to the selected object, and provides the content to the controller 255. [0045]An operation between the first device and the second device to control a screen display of the second device according to a first embodiment of the present invention will now be described with reference to FIG. 3. In FIG. 3, the first device 200 is the mobile terminal, and the second device 230 is a TV. [0046]Referring to FIG. 3, the mobile terminal 200 performs a device discovery to find a neighboring external display device supporting Wi-Fi Direct in step 300. When the TV 230 is found as an example of the external display device, the mobile terminal 200 sets a connection with the TV 230 in step 305, and exchanges a capability and performs a negotiation in step 310. The mobile terminal 200 sets an RTSP connection to transmit a command in step 315, and then directly transmits content displayed on a screen of the mobile terminal 200 to the TV 230 through an RTSP play command in step 320. [0047]When a response is received from the TV 230 in step 325, the mobile terminal 200 starts an Audio/Video (AV) streaming for a mirroring in step 330. Accordingly, the content is transmitted to the TV 230 through the streaming type. Since processes of connecting the mobile terminal 200 and the TV 230 in steps 300 to 330 are performed based on a general Wi-Fi Direct technique, a detailed description of connection processes according to the Wi-Fi Direct technique will not be made in the present invention. [0048]When the web browser is started in the mobile terminal 200 as shown in step 335, the user selects one from a search list in step 340. When the web browser is started, web content 440 is displayed in the mobile terminal 200 and the same web content 405 is displayed in the TV 230 as the web content 400 is provided to the TV 230 through the streaming type as illustrated in FIG. 4. [0049]When a command for designating a display position on the TV 230 is input when one object included in the content 400 is selected by the user, the mobile terminal 200 transmits to the TV 230 the command for designating the display position on the TV 230. For example, when the user performs a drag and drop in a right direction 410 when the user touches one object included in the content 400 with his/her finger, the mobile terminal 200 determines an input signal according to the drag and drop. Accordingly, the mobile terminal 200 transmits an RTSP setting parameter including direction information indicating the direction in which the drag and drop is performed to the TV 230 in step 345. [0050]When the RTSP setting parameter is received, the TV 230 moves a mirrored screen displayed in a center in step 350, and then transmits a response in step 355. To this end, the TV 230 analyzes direction information included in the RTSP setting parameter, and then moves the mirrored screen leftwards to display the content for the selected object in a right side when the drag and drop direction is a right direction. [0051]The mobile terminal 200 determines that the screen space is secured in the TV 230 when receiving the response, and thus transmits content information corresponding to the selected object to the TV 230 by using the RTSP setting parameter in step 360. [0052]For example, in FIG. 4, the TV 230 receives a content type set as the “web” and content information including a content address to receive the selected content such as http://xyz.com/news/20111022/headline.html. In response to the reception, the TV 230 operates the browser in step 365, and then accesses a web server 260 by using the content address to receive the content for the selected object in step 370. Accordingly, the TV 230 moves the mirrored screen 405, which had been displayed in the center, in the left direction opposite to the direction of the drag and drop of the user, and then displays the mirrored screen 405 in a left part 420 and the content for the selected object in a right part 415. Alternatively, an actual content instead of the content address may be transmitted as the content information in the streaming type. [0053]FIG. 5 illustrates an example in which the mobile terminal 200 combines screens and transmits the combined screen according to a second embodiment of the present invention. Since steps 500 to 540 of FIG. 5 are the same as steps 300 to 340 of FIG. 3, a detailed description thereof will be omitted. However, when the content for the selected object is operated in step 545, the mobile terminal 200 directly receives the content for the selected object from the web server 260 in step 550, configures the screen generated by combining the provided content and previous content in step 555, and directly transmits information on the combined screen to the TV 230 in step 560 in the second embodiment of the present invention. [0054]FIG. 6 illustrates an example of an operation between the first device and the second device to control a screen display of the second device according to a third embodiment of the present invention. Since operations performed in steps 600 to 630 of FIG. 6 are the same as the operations performed in steps 300 to 330 of FIG. 3, a detailed description thereof will be omitted. However, in FIG. 6, when a content application is executed in step 635, the mobile terminal 200 displays a content list screen 700 as illustrated in FIG. 7. When a drag and drop 710 is performed by the user when one content is selected, a content list 705 displayed on the TV 230 moves to a right part 720, and the selected content is displayed in a left part 715. [0055]An RTSP setting parameter transmitted in step 660 contains content information that includes a content type set as a “video” indicating that the content is media content and, for example, a content address set as “rtp://192.168.1.32/dlna_contents/thumnail.avi” When the RTST setting parameter is received, the TV 230 operates a player to execute the selected content in step 665, and accesses the web server 260 by using the content address to receive the content from the web server 260 in step 670. Accordingly, the content list is displayed in the right screen part 720 of the TV 230, and simultaneously, the content reproduced through the player is output in the left screen part 715. [0056]FIG. 8 illustrates an operation between the first device and the second device to control a screen display of the second device according to a fourth embodiment of the present invention. Since operations of steps 800 to 830 of FIG. 8 are the same as the operations of steps 300 to 330 of FIG. 3, a detailed description thereof will be omitted. However, in FIG. 8, the mobile terminal 200 determines a display direction of a current screen in step 835. When the screen direction is a horizontal direction, there is no empty space on the screen of the TV 230. When the screen direction is a vertical direction, there is an empty space in both sides of a center on the screen. When the current screen direction is determined as the vertical direction, the mobile terminal 200 transmits the RTSP setting parameter containing information on the content to be displayed in the empty space in order to fill the empty space in step 840. Then, the TV 230 operates the player in step 845, and receives an advertisement to be displayed in the empty space from the mobile terminal 200 in step 850. Accordingly, the TV 230 can reproduce the advertisement through the player, so that the advertisement such as a video can be output. [0057]Referring to FIG. 9, a mirrored screen of the TV 230 identical to a screen 900 of the mobile terminal 200 is located in a center part 905 of the TV 230. In this case, empty spaces are generated in left and right parts of the remaining screen except for the center part 905 of the TV 230. FIG. 9 illustrates an example where advertisement screens 910 and 915 are displayed together in both sides of the center of the mirrored screen 905. In this case, the content information contained in the RTSP setting parameter contains a content type as an “ads video” indicating that the content is an advertisement. When the mobile terminal 200 does not directly provide the advertisement, the content information may contain a content address to receive the advertisement. [0058]As described above, according to the present invention, the user can view an image on the mobile terminal screen 200 through an enlarged screen by mirroring the image on the mobile terminal screen 200 to the TV 230, and can also view an image for object selection on the mobile terminal screen 200 together with a previous image through the TV 230. [0059]According to the present invention, there is an advantage in that the user receives a more vivid and efficient image in comparison with using the mobile terminal since the user can control a screen display of an external display device. There is an advantage in that a dual screen is used according to characteristics of the device receiving a mirrored image, for example, a ratio of width to height and a web screen preview and a content preview are possible through a large sized screen of the external display device while maintaining the mobile terminal screen. [0060]Moreover, there is an advantage of using the external display device as a new business model by showing an advertisement in an empty space of the device screen. For example, it is possible to ask an advertiser for advertisement profits by counting the number of times of advertisement reproductions and maximize an advertisement effect by using the advertisement as the purpose of advertising the mobile terminal product. [0061]While the present invention has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details is made therein without departing from the spirit and scope of the present invention as defined by the appended claims. Therefore, several modifications are possible without departing from the gist of the present invention as defined by the appended claims. It should be understood that the modifications remain within the technical ideas and overviews of the invention.(String), 优先 [0001] 本申请根据 35 U.S.C. 2012 年 7 月 20 日向韩国知识产权局提交的韩国申请序列号 10-2012-0079367 的第 119(a) 条,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及用于控制移动终端中的显示的设备和方法,更具体地,涉及用于控制具有输出图像功能的移动终端中的外部显示设备中的显示的设备和方法 到外部显示设备。 [0004] 2.相关技术的描述 [0005] 随着数字广播和移动通信技术的发展,对允许用户在移动时观看数字广播的数字广播服务的兴趣增加了。 同时,广播服务的范式已经从具有被动概念的广播服务(其中用户仅被动地观看广播)改变为具有主动概念的广播服务,其中用户识别关于图1所示的产品的成本信息。 在直接观看广播的同时购买产品。 [0006] 对使用移动终端的数字多媒体广播(DMB)服务的兴趣也增加了。 DMB业务克服了收看节目的空间和时间限制,但由于屏幕尺寸的限制,不适合多人同时收看的节目。 因此,具有向TV等大型显示装置输出信号的功能的移动终端的发布增加。 [0007] 当前具有电视(TV)输出功能的移动终端可以将通过移动终端的屏幕显示的诸如广播的视频输出到外部显示设备。 因此,用户可以通过将从网络服务器下载的或由照相机拍摄的图像数据输出到外部显示设备来通过更大尺寸的屏幕观看广播。 具有电视输出功能的高级移动终端的示例包括 Wi-Fi 显示器 (WFD) 和播放镜像。 [0008] 例如,WFD 是指将移动终端的小尺寸屏幕 100 与电视等外部显示设备互通 110 然后和手机端同屏 100 如图 1 所示,在电视中无线显示。当通过移动终端屏幕进行用户输入时 100 ,将当前画面切换到与用户输入对应的画面。 电视机的屏幕 110 切换到与移动端同屏 100 . [0009] 但是,与移动终端屏幕上的图像相同的图像位于电视屏幕的中央。 因此,当移动终端的屏幕方向为水平时,虽然与移动终端屏幕上的图像相同的图像显示在整个电视屏幕上,但除了电视屏幕的中心之外的其余部分保持为空白区域,如图所示 在图1中,屏幕方向为垂直时。 也就是说,由于移动终端的屏幕尺寸和电视的屏幕尺寸不同,在电视屏幕上会产生如图1所示的空白区域。 [0010] 因此,本领域需要用户在外接显示设备上显示移动终端屏幕上的图像时能够控制外接显示设备的屏幕显示,以使用户接收到更生动、更生动的画面。 与使用移动终端相比,图像更高效。 发明内容 [0011] 因此,本发明提供了一种用于通过移动终端控制外部显示设备的屏幕显示的装置和方法。 [0012] 本发明还提供一种用于提供外部显示设备的有效屏幕显示的设备和方法。 [0013]根据本发明的一个方面,一种由移动终端控制显示装置的显示的方法包括:当执行与显示装置的连接时,将与显示在移动终端上的第一内容相同的第二内容发送到移动终端。 显示装置, 接收对移动终端上显示的第一内容中包含的对象中的一个对象的选择, 将与选择的对象对应的第三内容的信息发送到显示装置, 使得第二内容和与选择的对象对应的第三内容 对象一起显示在显示设备中。 [0014] 根据本发明的另一方面,一种用于控制显示装置的显示的移动终端包括用于执行与显示装置的连接的连接器、用于显示第一内容并根据选择输出选择信号的触摸屏 of one object from objects included in the first content, and a controller for controlling such that second content equal to the first content is transmitted to the display device through the connector, and controlling such that when the selection signal according to the selection of the one 从触摸屏传送对象,将与选择的对象对应的第三内容的信息传输到显示设备,从而将第二内容和与选择的对象对应的第三内容一起显示在显示设备上。 附图的简要说明 [0015] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0016] 图1为现有移动终端镜像时的电视画面。 [0017] 图2为本发明实施例的第一设备和第二设备的内部框图。 [0018] 图3是说明根据本发明第一实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作的示意图。 [0019] 图4是说明图3的动作方法的例子。 [0020] 图5是根据本发明第二实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作示意图。 [0021] 图6是根据本发明第三实施例的第一设备与第二设备之间控制第二设备的屏幕显示的操作示意图。 [0022] 图7是说明图6的动作方法的例子。 [0023] 图8是根据本发明第四实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作示意图。 和 [0024] 图9示出了用于描述图8的操作方法的示例。 本发明实施方案的详细说明 [0025] 在下文中,将参照附图描述本发明的实施例。 在以下描述中,相同的元件将由相同的附图标记表示,尽管它们在不同的附图中示出。 在本发明的以下描述中,为了清楚和简洁起见,将省略对包含在本文中的已知功能和配置的详细描述。 [0026]本发明提供一种在移动终端中控制外部显示设备的屏幕显示的方法。 为此,本发明包括控制使得移动终端与相邻的外部显示设备连接,图像数据被发送到外部显示设备以在外部显示在移动终端的屏幕上显示的图像的过程。 当在移动终端上输入针对图像数据中包括的对象之一的选择命令时,移动显示在外部显示设备上的图像的位置,并且将图像与用于选择命令的对象图像一起显示。 因此,可以有效地控制外部显示装置的输出画面。 [0027] 图2示出了根据本发明实施例的第一设备和第二设备的内部框图。 在图 2 中,第一个设备 200 是智能手机、手机、平板电脑等支持图像查看功能的移动终端,以及第二设备 230 是具有比第一设备的屏幕更大的屏幕的外部显示设备,例如电视 200 . [0028] 第一台设备 200 包括一个显示单元 205 , 一个网页浏览器模块 210 , 数字生活网络联盟 (DLNA) 模块 215 , 一个 Wi-Fi 显示 (WFD) 连接器 220 , 和一个控制器 225 . [0029] 显示单元 205 可以由液晶显示器(LCD)面板实现,并且当LCD面板以触摸屏类型实现时用作输入装置。 显示单元 205 用于显示用户输入或提供给用户的信息,以及移动终端的各类菜单。 当显示单元 205 在触摸屏类型中实现,输入信号输出到控制器 225 如果有来自用户的触摸输入。 控制器 225 通过触摸屏输入的信号来识别输入类型,并确定例如保持、拖动和放下。 [0030] 当根据用户的请求操作互联网浏览器时,网络浏览器模块 210 通过网络服务器访问输入到互联网地址窗口的统一资源定位符(URL)信息,以根据接收到的数据包生成网页。 网络浏览器模块 210 向控制器提供显示网页的网页内容 225 . [0031] DLNA 模块 215 向控制器提供媒体内容 225 为了将媒体内容(例如视频)传输到第二设备 230 在流式传输。 DLNA 模块 215 与第二个设备共享媒体内容 230 , 让用户可以持续观看存储在第一设备中的媒体内容 200 在第二个设备中 230 . [0032] WFD 连接器 220 搜索相邻的第二个设备 230 可用于 Wi-Fi Direct 服务。 当第二台设备 230 找到,WFD连接器 220 用于连接第一个设备 200 使用第二个设备 230 通过与第二设备交换设备能力的过程 230 . [0033] 控制器 225 控制第一设备内的一般操作 200 . 具体来说,控制器 225 控件使得来自 Web 浏览器模块的内容(例如 Web 内容) 210 或来自 DLNA 模块的媒体内容 215 被传送到第二个设备 230 通过 WFD 连接器 220 基于实时流协议(以下简称 RTSP)。 [0034] 控制器 225 通过显示单元确定来自用户的输入信号形式 205 控制第一个设备 200 按照决定。 例如,当用户输入对包括在显示单元上显示的图像中的对象的选择命令时 205 , 控制器 225 控制网络浏览器模块 210 或 DLNA 模块 215以便显示所选对象的详细数据。 此外,控制器 225 将当前显示的内容传输到第二个设备 230 ,并且内容的传输类型遵循流式传输类型,因此将省略其详细描述。 可以根据流类型传输实际内容,或者也可以只传输接收内容的内容地址,然后第二设备 230 可以访问内容地址以显示相同的内容。 [0035] 在传输与当前显示内容相同的内容后显示在第二设备上 230 在流式传输类型中,如果输入内容中包括的对象之一的选择命令,则将有关所选对象的详细数据发送到第二设备 230 . 将所选对象的详细数据插入到基于 RTSP 的参数中,然后传输。 例如,所选对象的详细数据包括实际内容数据、接收内容数据的地址、显示位置和内容类型。 [0036] 当用户用他/她的手指触摸通过网络浏览器找到的列表中的特定内容或网页然后执行向左拖放时,第一设备 200 传输到第二个设备 230 用于指示准备使得特定内容或网页显示在第二设备的屏幕左侧的信号 230 . 响应于该信号,显示在屏幕中央的内容移动以便在第二设备的屏幕左侧显示特定内容或网页 230 . [0037] 在第二个设备中执行的操作 230 下面将详细介绍。 [0038] 第二台设备 230 包括一个显示单元 235 , WFD 连接器 240 , 内容类型处理器 245 , 内容位置处理器 250 , 和一个控制器 255 . [0039] 控制器 255 接收与第一台设备上显示的内容相同的内容 200 在流类型和控制中,使得内容显示在显示单元上 235 . 当通过 WFD 连接器接收到基于 RTSP 指定所选对象的显示位置的命令时,即所选内容 240 , 控制器 255 响应命令,移动当前屏幕上的内容以确保呈现所选内容的屏幕空间。 当屏幕空间得到保证时,控制器 255 控件使得所选内容显示在显示单元上 235 与之前的内容。 [0040] 具体来说,控制器 255 将屏幕划分为两个空间同时显示当前内容和新选择的内容,并控制使得当前内容和新选择的内容分别布置在划分的屏幕空间中。 已经在中心显示的当前内容被布置在划分的屏幕空间中与选择的内容的显示位置相对的一侧对应的屏幕空间中。 [0041] 可以不同地设置每个划分的屏幕空间的大小。 例如,可以划分屏幕以保持当前显示在屏幕中央的内容的显示放大率,在这种情况下,新选择的内容显示在显示该屏幕空间之外的剩余屏幕空间中。 当前内容。 为了以相同大小显示当前内容和新选择的内容,可以将屏幕划分为具有相同大小的屏幕空间。 划分用于显示内容的屏幕的方法不限于此。 [0042] 因此,显示单元 235 可以显示根据第一设备中的对象选择而改变的图像 200 以及显示与通过显示单元显示的图像相同的图像 205 第一台设备 200 . [0043] 内容类型处理器 245 确定从第一设备接收的内容的类型 200并将内容提供给控制器 255 . 内容类型是指网页内容、媒体内容等内容的类型,例如,网页内容可以设置为“web”,媒体内容可以设置为“视频”,还可以设置广告 到“广告视频”。 [0044] 当内容地址包含在所选对象的详细数据中时,内容位置处理器 250 访问内容地址对应的web服务器,接收选择的对象对应的内容,并将内容提供给控制器 255 . [0045] 现在将参照图3描述根据本发明第一实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作。在图3中,第一设备 200 是移动终端,第二个设备 230 是电视。 [0046] 参见图3,移动终端 200 执行设备发现以查找支持 Wi-Fi Direct 的相邻外部显示设备 300 . 当电视 230 发现作为外部显示设备的示例,移动终端 200 设置与电视的连接 230 在一步 305 , 并交换能力并逐步执行协商 310 . 移动终端 200 设置 RTSP 连接以在步骤中传输命令 315 ,然后直接传输显示在移动终端屏幕上的内容 200 到电视 230 通过 RTSP 播放命令在步骤 320 . [0047] 当收到来自电视的响应时 230 在一步 325 , 移动端 200 启动音频/视频 (AV) 流以进行镜像 330 . 因此,内容被传送到电视 230 通过流式传输。 由于连接移动终端的过程 200 和电视 230 逐步 300 至 330 由于基于一般Wi-Fi Direct技术进行的连接过程,本发明将不详细描述根据Wi-Fi Direct技术的连接过程。 [0048] 在移动终端中启动网络浏览器时 200 如步骤所示 335 ,用户在步骤中从搜索列表中选择一个 340 . 当网络浏览器启动时,网页内容 440 显示在移动端 200 和相同的网页内容 405 显示在电视上 230 作为网页内容 400 提供给电视 230 通过流式传输,如图 4 所示。 [0049] 指定电视显示位置的命令时 230 当内容中包含一个对象时输入 400 由用户选择,移动端 200 传送到电视 230 指定电视显示位置的命令 230 . 例如,当用户在正确的方向上执行拖放操作时 410 当用户触摸内容中包含的一个对象时 400 用他/她的手指,移动终端 200 根据拖放确定输入信号。 因此,移动终端 200 将包括指示执行拖放方向的方向信息的RTSP设置参数发送到TV 230 在一步 345 . [0050] 当接收到 RTSP 设置参数时,电视 230 以步进方式移动显示在中心的镜像屏幕 350 ,然后在步骤中发送响应 355 . 为此,电视 230 分析RTSP设置参数中包含的方向信息,然后在拖放方向为右方向时将镜像屏幕向左移动以在右侧显示所选对象的内容。 [0051] 移动终端 200 确定电视中的屏幕空间是安全的 230 当接收到响应时,将与所选对象对应的内容信息发送到电视 230 通过使用步骤中的 RTSP 设置参数 360 . [0052] 例如,在图 4 中,电视230 接收设置为“web”的内容类型和包括接收所选内容的内容地址的内容信息,例如http://xyz.com/news/20111022/headline.html。 响应接收,电视 230 一步一步操作浏览器 365 ,然后访问 Web 服务器 260 通过使用内容地址接收步骤中所选对象的内容 370 . 因此,电视 230 移动镜像屏幕 405 ,一直显示在中间,向左方向与用户拖拽的方向相反,然后显示镜像屏幕 405 在左侧 420 以及右侧部分中所选对象的内容 415 . 备选地,可以将实际内容而不是内容地址作为流式传输类型的内容信息来发送。 [0053] 图 5 说明了一个示例,其中移动终端 200 根据本发明的第二实施例,组合屏幕并传输组合屏幕。 由于步骤 500 至 540 图5的步骤相同 300 至 340 在图3中,将省略其详细描述。 但是,当在步骤中操作所选对象的内容时 545 , 移动端 200 直接从 Web 服务器接收所选对象的内容 260 在一步 550 , 配置通过在步骤中结合提供的内容和以前的内容生成的屏幕 555 ,并直接将组合屏幕上的信息传输到电视上 230 在一步 560 在本发明的第二实施例中。 [0054] 图6示出了根据本发明第三实施例的在第一设备和第二设备之间控制第二设备的屏幕显示的操作的示例。 由于操作是分步执行的 600 至 630 图 6 的操作与步骤中执行的操作相同 300 至 330 在图3中,将省略其详细描述。 然而,在图 6 中,当在步骤 635 , 移动端 200 显示内容列表屏幕 700 如图 7 所示。当拖放 710 由用户在选择一个内容时执行,内容列表 705 显示在电视上 230 向右移动 720 , 选中的内容显示在左侧 715 . [0055] 分步传送的 RTSP 设置参数 660 包含内容信息,该内容信息包括设置为“视频”的内容类型,指示该内容是媒体内容,例如,设置为“rtp://192.168.1.32/dlna_contents/thumnail.avi”的内容地址当RTST设置时 接收到参数,电视 230 操作播放器执行步骤中选择的内容 665 , 并访问网络服务器 260 通过使用内容地址从 Web 服务器接收内容 260 在一步 670 . 因此,内容列表显示在右侧屏幕部分 720 电视的 230 ,同时通过播放器再现的内容在左画面部分输出 715 . [0056] 图8示出了根据本发明第四实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作。 由于步骤的操作 800 至 830 图8的操作与步骤的操作相同 300 至 330 在图3中,将省略其详细描述。 然而,在图 8 中,移动终端 200 在步骤中确定当前画面的显示方向 835 . 当屏幕方向为水平方向时,电视屏幕上没有空白区域 230 . 当屏幕方向为垂直方向时,屏幕中心的两侧有空白区域。 当当前屏幕方向确定为垂直方向时,移动终端 200 传送包含有关要在空白处显示的内容的信息的 RTSP 设置参数,以便在步骤中填充空白处 840. 那么,电视 230 同步操作播放器 845 ,并从移动终端接收要在空白处展示的广告 200 在一步 850 . 因此,电视 230 可以通过播放器再现广告,从而可以输出视频等广告。 [0057] 参考图9,电视的镜像屏幕 230 等同于屏幕 900 移动终端的 200 位于中心部分 905 电视的 230 . 在这种情况下,除了中心部分之外,其余屏幕的左右部分会产生空白空间 905 电视的 230 . 图 9 说明了一个示例,其中广告屏幕 910 和 915 一起显示在镜像屏幕中心的两侧 905 . 在这种情况下,包含在RTSP设置参数中的内容信息包含作为“广告视频”的内容类型,指示该内容是广告。 当移动端 200 不直接提供广告,内容信息可能包含接收广告的内容地址。 [0058] 如上所述,根据本发明,用户可以在移动终端屏幕上查看图像 200 通过将图像镜像到移动终端屏幕上的放大屏幕 200 到电视 230 ,也可以在移动端屏幕上查看图片进行对象选择 200 连同之前通过电视的图像 230 . [0059] 根据本发明,由于用户可以控制外部显示设备的屏幕显示,因此与使用移动终端相比,具有用户接收到更生动和更有效的图像的优点。 优点是根据接收镜像的设备的特点,使用双屏,例如宽高比,通过外接大屏可以进行网页预览和内容预览。 显示设备,同时保持移动终端屏幕。 [0060] 此外,通过在设备屏幕的空白空间中显示广告,具有使用外部显示设备作为新商业模式的优点。 例如,可以通过统计广告的复制次数来向广告商索取广告收益,并以广告为目的对移动终端产品进行广告宣传,从而使广告效果最大化。 [0061] 尽管本发明已经参照其某些实施例进行了展示和描述,但本领域技术人员将理解,在不背离由以下定义的本发明的精神和范围的情况下,在形式和细节上进行了各种改变。 所附权利要求。 因此,在不背离由所附权利要求限定的本发明的主旨的情况下,可以进行若干修改。 应当理解,这些修改仍然在本发明的技术思想和概述之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104471954A(String), CN104471954B(String), EP2875645A1(String), EP2875645A4(String), EP2875645B1(String), KR1020140011857A(String), US10114522B2(String), US20140026068A1(String), WO2014014185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104471954A(String), CN104471954B(String), EP2875645A1(String), EP2875645A4(String), EP2875645B1(String), KR1020140011857A(String), US10114522B2(String), US20140026068A1(String), WO2014014185A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.403 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10114522B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104471954A(String), CN104471954B(String), EP2875645A1(String), EP2875645A4(String), EP2875645B1(String), KR1020140011857A(String), US10114522B2(String), US20140026068A1(String), WO2014014185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), CN104471954A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), CN104471954B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), EP2875645A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), EP2875645A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), EP2875645B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.457 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), KR1020140011857A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), US10114522B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), US20140026068A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270698(Integer), WO2014014185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10114522B2(String), US10114522B2(String), 1540828800(Integer), 270698(Integer), 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.508 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185021(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185021(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185021(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185021(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.558 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.559 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10499298B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10499298B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/180651(String), 1541347200(Integer), US10499298B2(String), 1575302400(Integer), 1575302400(Integer), 美国(String), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185022(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2eea8ede00a24c3dbd3417b19cc650f7.png(String), 185022(Integer), 2eea8ede00a24c3dbd3417b19cc650f7.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10499298B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/180651(String), 1541347200(Integer), US10499298B2(String), 1575302400(Integer), 1575302400(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), \20230420\2eea8ede00a24c3dbd3417b19cc650f7.png(String), 16(Integer), 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 1. A method, comprising:obtaining, by a mobile terminal, a measurement result of a target cell by measuring the target cell according to measurement configuration information, wherein the measurement configuration information is obtained by the mobile terminal, by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; anddetermining, by the mobile terminal according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and in response, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell; ordetermining, by the mobile terminal, that the mobile terminal generates a measurement report according to the measurement result and that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, and in response, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell; ordetermining, by the mobile terminal, according to the measurement result and indication information that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and that the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, and in response, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell.(String), 1.一种方法,包括:移动终端根据测量配置信息对目标小区进行测量获得目标小区的测量结果,其中,所述测量配置信息是移动终端通过与所述目标小区之间建立的无线资源控制(RRC)连接获得的。移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元;和移动终端根据测量结果和指示信息确定测量结果满足该指示信息对应的测量上报事件的进入条件,作为响应,移动终端发起接入连接建立目标小区对应的网元,其中,指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立;或者移动终端确定移动终端根据测量结果生成测量报告,该测量报告为指示信息对应的测量报告事件的测量报告,作为响应,移动终端发起,与目标小区对应的接入网元建立连接,其中,指示信息用于指示移动终端发起与目标小区对应的接入网元的连接建立;或者移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件,移动终端生成对应的测量上报事件的测量报告指示信息,作为响应,移动终端向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立目标细胞。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 2. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:skipping, by the mobile terminal, sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiating connection establishment to the access network element corresponding to the target cell.(String), 2.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 3. The method according to claim 1, wherein:when it is determined that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal determines that a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orwhen it is determined that the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal determines that a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 3.根据权利要求1所述的方法,其中:当确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端确定测量结果满足指示信息对应的测量上报事件进入条件的时长达到预定时长时,移动终端发起到目标小区对应的接入网网元的连接建立;或者当确定移动终端生成指示信息对应的测量上报事件的测量报告时,移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端确定生成指示信息对应的测量报告事件的测量报告后的时长达到预定时长时,移动终端发起到目标小区对应的接入网网元的连接建立。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 4. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:when the mobile terminal is in a discontinuous reception (DRX) state, initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell.(String), 4.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端处于非连续接收(DRX)状态时,移动终端向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 5. The method according to claim 4, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 5.根据权利要求4所述的方法,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 6. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:when a mobility state estimation of the mobile terminal is greater than or equal to a speed threshold, initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell.(String), 6.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端的移动状态估计值大于或等于速度门限时,移动终端向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 7. The method according to claim 1, further comprising:sending, by the mobile terminal, a mobility state estimation of the mobile terminal to the access network element corresponding to the serving cell; andreceiving, by the mobile terminal, the indication information after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold specified by the access network element corresponding to the serving cell.(String), 7.根据权利要求1所述的方法,还包括:移动终端向服务小区对应的接入网元发送移动终端的移动状态估计;和移动终端在服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限后,接收指示信息。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 8. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:initiating, by the mobile terminal to the target cell, at least one of: a random access process, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 8.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:移动终端向目标小区发起以下至少之一:随机接入过程、RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 9. An apparatus, comprising:a storage medium comprising processor-executable instructions; anda processor coupled to the storage medium, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:obtain a measurement result of a target cell by measuring the target cell according to measurement configuration information, wherein the measurement configuration information is obtained by a mobile terminal, by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell, anddetermine, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and in response, initiate connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell, ordetermine that a measurement report is generated according to the measurement result and that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, and in response, initiate connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell, ordetermine according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and that a measurement report of the measurement reporting event corresponding to the indication information is generated, and in response, initiate connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell.(String), 9.一个仪器,包括:包括处理器可执行指令的存储介质;和耦合到存储介质的处理器,其中处理器可执行指令在由处理器执行时使装置:根据测量配置信息测量目标小区获得目标小区的测量结果,其中测量配置信息是移动终端通过移动终端与接入网之间建立的无线资源控制(RRC)连接获得的服务小区对应的网元,来自服务小区对应的接入网网元,根据测量结果和指示信息,确定测量结果满足指示信息对应的测量上报事件的进入条件,作为响应,向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示向目标小区对应的接入网元发起连接建立,或者确定根据测量结果生成测量报告,该测量报告为指示信息对应的测量报告事件的测量报告,作为响应,向目标小区对应的接入网元发起连接建立,其中指示信息用于指示向目标小区对应的接入网元发起连接建立,或者根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件,生成指示信息对应的测量上报事件的测量报告,响应、向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示向目标小区对应的接入网元发起连接建立。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 10. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:skip sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiate connection establishment to the access network element corresponding to the target cell.(String), 10.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 11. The apparatus according to claim 9, wherein:when it is determined that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:initiate connection establishment to the access network element corresponding to the target cell when a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orwhen it is determined that the measurement report is generated according to the measurement result and the measurement report is a measurement report of a measurement reporting event, the processor-executable instructions, when executed by the processor, further cause the apparatus to:initiate connection establishment to the access network element corresponding to the target cell when a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 11.根据权利要求9所述的装置,其中:当确定测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立,处理器可执行指令在处理器执行时,进一步使设备:当测量结果满足指示信息对应的测量上报事件进入条件的时长达到预定时长时,发起到目标小区对应的接入网元的连接建立;或者当确定测量报告是根据测量结果生成的并且测量报告是测量报告事件的测量报告时,处理器可执行指令在被处理器执行时还使装置:当生成指示信息对应的测量报告事件的测量报告后的时长达到预定时长时,发起到目标小区对应的接入网元的连接建立。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 12. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when the apparatus is in a discontinuous reception (DRX) state, initiate connection establishment to the access network element corresponding to the target cell.(String), 12.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当装置处于非连续接收(DRX)状态时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 13. The apparatus according to claim 12, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 13.根据权利要求12所述的装置,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 14. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when a mobility state estimation of the apparatus is greater than or equal to a speed threshold, initiate connection establishment to the access network element corresponding to the target cell.(String), 14.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当该装置的移动性状态估计大于或等于速度门限时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 15. The apparatus according to claim 9, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:send a mobility state estimation of the apparatus to the access network element corresponding to the serving cell; andreceive the indication information after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold.(String), 15.根据权利要求9所述的装置,其中处理器可执行指令在由处理器执行时使装置:向服务小区对应的接入网元发送该装置的移动性状态估计;和在服务小区对应的接入网元确定移动状态估计大于或等于速度门限后,接收指示信息。(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185022(Integer), 16. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, cause the apparatus to:initiate to the target cell, at least one of: a random access process, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 16.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时使装置:向目标小区发起以下至少之一:随机接入过程、RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185022(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. application Ser. No. 15/473,407, filed on Mar. 29, 2017, which is a continuation of International Application No. PCT/CN2014/088061, filed on Sep. 30, 2014. All of the afore-mentioned patent applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present invention relate to the field of communications technologies, and in particular, to a mobile terminal control method and a mobile terminal. BACKGROUND [0003]Currently, a mobile terminal and life of a user are closely related to each other. Usually, the user performs a communication service such as chat by using the mobile terminal while being on a vehicle such as a bus or a subway. In this case, the mobile terminal also moves at high speed as the vehicle moves. Because the mobile terminal moves at relatively high speed, in terms of a physical location, after the mobile terminal enters from a coverage area of a previous serving cell to a coverage area of a new cell, quality of a communication service provided by the serving cell is deteriorated. In addition, because the mobile terminal cannot establish a connection to the new cell in a timely manner either, mobility of the mobile terminal is affected. For example, because the quality of the communication service provided by the serving cell is deteriorated, and the mobile terminal cannot establish a connection to the new cell in a timely manner either, a communication service currently performed by the mobile terminal is interrupted. [0004]Specifically, before establishing a connection to an access network element corresponding to the new cell, the mobile terminal needs to send a measurement report about the new cell to an access network element corresponding to the serving cell. The mobile terminal may establish a connection to a new cell only when the mobile terminal receives an indication that connection establishment is allowed and that is sent by the access network element corresponding to the serving cell. It may be understood that, by using the prior art, the mobile terminal needs to wait for a relatively long time period from discovering the new cell to establishing a connection to the new cell, and cannot establish a connection to the new cell in a timely manner to obtain a communication service provided by the new cell. Particularly, when the mobile terminal is in a discontinuous reception (DRX) state, an interval at which the mobile terminal measures the serving cell and an interval at which the mobile terminal measures the new cell become longer. For example, when a DRX cycle is 320 ms, and the mobile terminal needs to spend 5 times the DRX cycle performing radio resource management (RRM) measurement on a neighboring cell, the mobile terminal needs to spend a longer time period from discovering a new cell to establishing a connection to the new cell, and mobility of the mobile terminal cannot meet a basic requirement of the user. Therefore, how the mobile terminal establishes a connection to a new cell in a timely manner is an important aspect of improving performance of the mobile terminal. SUMMARY [0005]Embodiments of the present invention provide a mobile terminal control method and a mobile terminal, so as to improve mobility of the mobile terminal. [0006]According to a first aspect, an embodiment of the present invention provides a processing method for establishing a connection to an access network element by a mobile terminal, and the method includes:[0007]measuring, by a mobile terminal, a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and[0008]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or[0009]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information; or[0010]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and when the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information, where[0011]the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. [0012]According to a second aspect, an embodiment of the present invention provides a method for controlling a DRX state of a mobile terminal, and the method includes:[0013]performing, by a mobile terminal, radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and[0014]when the mobile terminal determines, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold,[0015]starting, by the mobile terminal, a timer, and before the timer expires, transitioning the mobile terminal from a DRX state to a non-DRX state, or transitioning the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shortening a cycle of the DRX state. [0016]According to a third aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes:[0017]a measurement module, configured to measure a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and[0018]a processing module, configured to: initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or[0019]initiate connection establishment to an access network element corresponding to the target cell when generating a measurement report according to the measurement result, and determining that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the processing module generates the measurement report of the measurement reporting event corresponding to the indication information; or[0020]initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the processing module generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the processing module generates the measurement report of the measurement reporting event corresponding to the indication information, where[0021]the indication information is obtained by the processing module in advance from the access network element corresponding to the serving cell. [0022]According to a fourth aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes:[0023]an obtaining module, configured to perform radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and[0024]a processing module, configured to: when determining, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold,[0025]start a timer, and before the timer expires, transition the mobile terminal from a DRX state to a non-DRX state, or transition the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shorten a cycle of the DRX state. [0026]According to the mobile terminal control method and the mobile terminal that are provided in the embodiments of the present invention, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. BRIEF DESCRIPTION OF THE DRAWINGS [0027]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0028]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0029]FIG. 3 is a schematic diagram of an RRC connection establishment process according to Embodiment 2 of the present invention; [0030]FIG. 4 is a schematic diagram of an RRC connection re-establishment process according to Embodiment 2 of the present invention; [0031]FIG. 5 is a schematic diagram of a cell update process according to Embodiment 2 of the present invention; [0032]FIG. 6 is a schematic diagram of a contention-based random access process according to Embodiment 2 of the present invention; [0033]FIG. 7 is a schematic diagram of a non-contention-based random access channel process according to Embodiment 2 of the present invention; [0034]FIG. 8 is a schematic flowchart of Embodiment 3 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0035]FIG. 9A and FIG. 9B are a schematic flowchart of Embodiment 4 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0036]FIG. 10A and FIG. 10B are a schematic flowchart of Embodiment 5 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0037]FIG. 11A and FIG. 11B are a schematic flowchart of Embodiment 6 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0038]FIG. 12A to FIG. 12C are a schematic flowchart of Embodiment 7 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0039]FIG. 13A to FIG. 13C are a schematic flowchart of Embodiment 8 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0040]FIG. 14A to FIG. 14C are a schematic flowchart of Embodiment 9 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0041]FIG. 15A to FIG. 15C are a schematic flowchart of Embodiment 10 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0042]FIG. 16 is a schematic flowchart of Embodiment 1 of a method for controlling a DRX state of a mobile terminal according to the present invention; [0043]FIG. 17 is a schematic structural diagram of Embodiment 1 of a mobile terminal according to the present invention; [0044]FIG. 18 is a schematic structural diagram of Embodiment 2 of a mobile terminal according to the present invention; [0045]FIG. 19 is a schematic structural diagram of Embodiment 3 of a mobile terminal according to the present invention; [0046]FIG. 20 is a schematic structural diagram of Embodiment 4 of a mobile terminal according to the present invention; [0047]FIG. 21 is a schematic structural diagram of Embodiment 5 of a mobile terminal according to the present invention; and [0048]FIG. 22 is a schematic structural diagram of Embodiment 6 of a mobile terminal according to the present invention. DETAILED DESCRIPTION [0049]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 1, this embodiment is executed by a mobile terminal, and specifically includes the following steps. [0050]S101. The mobile terminal measures a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell. [0051]The mobile terminal establishes an RRC (radio resource control) connection to a serving cell, and the measurement configuration information is obtained by the mobile terminal, by using the RRC connection, from an access network element (which may be specifically a base station that manages the serving cell) corresponding to the serving cell. Specifically, the measurement configuration information includes a configuration about a measurement reporting event and the measurement reporting event may be specifically an event A3, an event A4, an event A5, or the like. [0052]Specifically, the mobile terminal performs RRM measurement on the target cell according to the measurement configuration information, so as to obtain an RRM measurement result. The target cell may be a neighboring cell of the serving cell, or may be a corresponding cell. When the target cell is a corresponding cell, the mobile terminal needs to obtain an identity of the corresponding cell from the serving cell before the mobile terminal performs measurement. [0053]S102. When the mobile terminal determines, according to the measurement result of the target cell and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0054]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0055]By performing S102, the mobile terminal skips generating a measurement report of the measurement reporting event corresponding to the indication information, skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0056]Alternatively, after performing S101, the mobile terminal chooses to perform S103 instead of S102. [0057]S103. When the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0058]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to indication information. [0059]By performing S103, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0060]Alternatively, after performing S101, the mobile terminal chooses to perform S104 instead of S102 and S103. [0061]S104. When the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0062]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information. [0063]By performing S104, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0064]In any one step of the foregoing S102, S103, or S104, the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. Optionally, the mobile terminal receives, by using the RRC connection, the indication information sent by the access network element corresponding to the serving cell. Specifically, the access network element corresponding to the serving cell may deliver the indication information while delivering the measurement configuration information to the mobile terminal, or may deliver the indication information to the mobile terminal before this embodiment is executed. In this embodiment, an example in which the measurement reporting event is the event A3 or the event A4 is used. When the measurement reporting event is specifically the event A3, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”. When the measurement reporting event is specifically the event A4, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Thresh”. Mn is the measurement result of the target cell, Ofn is a frequency specific offset of the target cell, and Ocn is a cell individual offset of the target cell. If the target cell is not configured with the cell individual offset, when the formulas are applied, a value of Ocn may be 0. Ms is a measurement result of the serving cell, Ofs is a frequency specific offset of the serving cell, Ocs is a cell individual offset of the serving cell, Hys is an event hysteresis parameter, Off is an event offset parameter, and Thresh is an event threshold parameter. Parameters such as Ofn, Ocn, Hys, Ofs, Ocs, and Off are obtained by the mobile terminal in advance. [0065]Specifically, in communication transmission, the indication information is specifically at least one piece of data. The at least one piece of data includes an identifier of the measurement reporting event. For example, if the at least one piece of data includes an identifier “A3”, it indicates that the measurement reporting event corresponding to the indication information is the event A3. Alternatively, the at least one piece of data is specifically a specific identifier. The specific identifier may be located in measurement configuration information, and is associated with the configuration about the measurement reporting event in the measurement configuration information. For example, if partial content of the measurement configuration information is a configuration about the event A3, and the specified identifier is associated with the configuration about the event A3 in the measurement configuration information, it may indicate that the measurement reporting event corresponding to the indication information is the event A3. [0066]Possibly, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0067]Optionally, the indication information may be specifically a direct re-establishment indication, a cell update indication, or a forward handover indication. [0068]In this embodiment, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0069]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 2, on the basis of the embodiment shown in FIG. 1, this embodiment is described in a implementation manner, and specifically includes the following steps. [0070]S201. A mobile terminal receives measurement configuration information and indication information that are sent by an access network element corresponding to a serving cell. [0071]The measurement configuration information and the indication information may be sent, to the mobile terminal by using same signaling, by the access network element corresponding to the serving cell, or may be sent, to the mobile terminal by using different signaling, by the access network element corresponding to the serving cell. [0072]S202. The mobile terminal measures a target cell, so as to obtain a measurement result of the target cell. [0073]The step is specifically described in S101. However, it should be noted that, in addition to being a newly discovered neighboring cell, the target cell may be a specified cell described in the S101, and may be specifically specified by the indication information. That is, if the indication information further carries a cell identity, a cell corresponding to the cell identity carried in the indication information is the target cell. [0074]S203. The mobile terminal determines whether the measurement result of the target cell meets an entering condition of a measurement reporting event corresponding to the indication information, and if yes, the mobile terminal performs S204, or if no, this embodiment ends. [0075]Optionally, in this embodiment, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0076]For example, if the mobile terminal receives two pieces of indication information in S201, one of the two pieces of indication information is corresponding to an event A3, and the other is corresponding to an event A4. When the measurement result obtained in S202 meets an entering condition of either measurement reporting event of the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S204. [0077]Alternatively, if one piece of indication information is obtained in S201, and the indication information is corresponding to an event A3 and an event A4, when the measurement result obtained in S202 meets an entering condition of either the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S204. [0078]Alternatively, if the indication information obtained in S201 is corresponding to an event A3, when the measurement result obtained in S202 meets an entering condition of the event A3, the mobile terminal performs the following S204. That is, when Mn meets “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, the mobile terminal performs S204. However, when Mn meets “Mn+Ofn+Ocn−Hys>Thresh” but does not meet “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, this embodiment ends, that is, an entering condition that is of a measurement reporting event and is met by the measurement result is not the entering condition of the measurement reporting event corresponding to the indication information. [0079]It should be additionally noted that, if the indication information is used to instruct the mobile terminal to initiate connection establishment to an access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal may directly perform S205 after determining, by performing S203, that the measurement result of the target cell meets the entering condition of the measurement reporting event corresponding to the indication information. However, to ensure that a control effect, on the mobile terminal, of a network-side device in a communications network is not affected and to give consideration to mobility of the mobile terminal as well, in this embodiment, preferably, the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. The mobile terminal performs S204 and S205 in sequence after determining, by performing S203, that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0080]S204. The mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. [0081]S205. The mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0082]The connection establishment in S205 specifically includes:[0083]initiating, by the mobile terminal, a random access process to the target cell, and/or any one of the following processing:[0084]initiating, by the mobile ter(String), 相关申请的交叉引用 [0001] 该申请是美国申请 Ser. 2017 年 3 月 29 日提交的第 15/473,407 号国际申请是 2014 年 9 月 30 日提交的国际申请第 PCT/CN2014/088061 号的继续申请。所有上述专利申请均通过引用并入本文 完整地。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种移动终端控制方法及移动终端。 背景 [0003] 目前,移动终端与用户的生活息息相关。 通常,用户在诸如公共汽车或地铁的交通工具上通过使用移动终端进行诸如聊天的通信服务。 在这种情况下,移动终端也随着车辆的移动而高速移动。 由于移动终端移动速度较高,从物理位置上来说,移动终端从上一个服务小区的覆盖范围进入到新的小区覆盖范围后,服务小区提供的通信服务质量 恶化。 另外,由于移动终端也无法及时与新小区建立连接,影响了移动终端的移动性。 例如,由于服务小区提供的通信服务质量下降,移动终端也无法及时建立到新小区的连接,导致移动终端当前进行的通信服务中断。 [0004] 具体地,移动终端在与新小区对应的接入网元建立连接之前,需要向服务小区对应的接入网元发送关于新小区的测量报告。 只有当移动终端接收到服务小区对应的接入网元发送的允许建立连接的指示时,移动终端才可以建立到新小区的连接。 可以理解的是,采用现有技术,移动终端从发现新小区到与新小区建立连接需要等待较长的时间,不能及时与新小区建立连接。 获得新小区提供的通信服务的方式。 特别地,当移动终端处于非连续接收(DRX)状态时,移动终端测量服务小区的间隔和移动终端测量新小区的间隔变长。 例如,当DRX周期为320ms时,移动终端需要花费5倍的DRX周期对邻区进行无线资源管理(Radio Resource Management,无线资源管理)测量,则移动终端需要花费更长的时间才能发现新的小区。 小区与新小区建立连接,移动终端的移动性不能满足用户的基本需求。 因此,移动终端如何及时建立与新小区的连接是提高移动终端性能的重要方面。 概括 [0005] 本发明实施例提供一种移动终端控制方法及移动终端,以提高移动终端的移动性。 [0006] 第一方面,本发明实施例提供了一种移动终端与接入网元建立连接的处理方法,该方法包括: [0007]移动终端根据测量配置信息对目标小区进行测量,以获取目标小区的测量结果,其中,移动终端获取测量配置信息,使用之间建立的无线资源控制RRC连接 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和[0008] 当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立; 或者[0009] 当移动终端根据测量结果生成测量报告时,移动终端发起到目标小区对应的接入网元的连接建立,移动终端确定该测量报告为测量报告的测量报告 指示信息对应的事件,该指示信息用于在移动终端生成该指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立; 或者[0010] 当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,当移动终端生成该指示信息对应的测量报告事件的测量报告时,该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,如果 测量结果满足指示信息对应的测量上报事件的进入条件,移动终端生成指示信息对应的测量上报事件的测量报告,其中[0011] 指示信息是移动终端预先从服务小区对应的接入网元获取的。 [0012] 第二方面,本发明实施例提供了一种移动终端的DRX状态控制方法,该方法包括: [0013] 移动终端根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,以获取服务小区的下行无线链路质量; 和[0014] 当移动终端通过估计下行无线链路质量,确定下行无线链路连续出现失步指示的次数达到预设门限时,[0015] 移动终端启动定时器,在定时器超时之前,将移动终端从DRX状态转变为非DRX状态,或者将移动终端从长周期DRX状态转变为短周期DRX状态 ,或者缩短DRX状态的周期。 [0016] 第三方面,本发明实施例提供了一种移动终端,该移动终端包括: [0017] 测量模块,用于根据测量配置信息对目标小区进行测量,以获取所述目标小区的测量结果,所述测量配置信息为所述移动终端通过与所述目标小区之间建立的无线资源控制RRC连接获得的 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和[0018]处理模块,用于在根据所述测量结果和指示信息确定所述测量结果满足所述指示信息对应的测量上报事件的进入条件时,发起到所述目标小区对应的接入网元的连接建立 , 该指示信息用于指示处理模块如果测量结果满足该指示信息对应的测量上报事件的进入条件,则向目标小区对应的接入网元发起连接建立; 或者[0019] 根据测量结果生成测量报告时,向目标小区对应的接入网元发起连接建立,确定该测量报告为指示信息对应的测量报告事件的测量报告,其中使用该指示信息 若处理模块生成指示信息对应的测量上报事件的测量报告,则指示处理模块向目标小区对应的接入网元发起连接建立; 或者[0020] 当根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,发起到目标小区对应的接入网元的连接建立,处理模块生成 指示信息对应的测量上报事件的测量报告,指示信息用于在测量结果满足测量上报进入条件时,指示处理模块向目标小区对应的接入网元发起连接建立 指示信息对应的事件,处理模块生成指示信息对应的测量报告事件的测量报告,其中[0021] 指示信息由处理模块预先从服务小区对应的接入网元获取。 [0022] 第四方面,本发明实施例提供一种移动终端,该移动终端包括: [0023] 获取模块,用于根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,获取服务小区的下行无线链路质量; 和[0024] 处理模块,用于通过对所述下行无线链路质量的估计,确定所述下行无线链路连续出现失步指示的次数达到预设门限时,[0025] 启动定时器,在定时器超时前,将移动终端从DRX状态转移到非DRX状态,或者将移动终端从长周期DRX状态转移到短周期DRX状态,或者缩短周期 DRX 状态。 [0026]本发明实施例提供的移动终端控制方法及移动终端,通过指示信息指示移动终端在测量结果满足时,向目标小区对应的接入网元发起连接建立。 指示信息对应的测量上报事件的进入条件; 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 附图的简要说明 [0027] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图; [0028] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图; [0029] 图3为本发明实施例二的RRC连接建立过程示意图; [0030] 图4为本发明实施例二的RRC连接重建过程示意图; [0031] 图5为本发明实施例二的小区更新过程示意图; [0032] 图6为本发明实施例二的基于竞争的随机接入过程的示意图; [0033] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图; [0034] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图; [0035] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图; [0036] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图; [0037] 图11A和图11B为本发明移动终端与小区建立连接的处理方法实施例六的流程示意图; [0038] 图12A至图12C为本发明移动终端与小区建立连接的处理方法实施例七的流程示意图; [0039] 图13A至图13C为本发明移动终端与小区建立连接的处理方法实施例八的流程示意图; [0040] 图14A至图14C为本发明移动终端与小区建立连接的处理方法实施例九的流程示意图; [0041]图15A至图15C为本发明移动终端与接入网元建立连接的处理方法实施例十的流程示意图; [0042] 图16为本发明移动终端的DRX状态控制方法实施例一的流程示意图; [0043] 图17为本发明移动终端实施例一的结构示意图; [0044] 图18为本发明移动终端实施例二的结构示意图; [0045] 图19为本发明移动终端实施例三的结构示意图; [0046] 图20为本发明移动终端实施例四的结构示意图; [0047] 图21为本发明移动终端实施例五的结构示意图; 和 [0048] 图22为本发明移动终端实施例六的结构示意图。 详细说明 [0049] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图。 如图1所示,本实施例的执行主体为移动终端,具体包括以下步骤。 [0050] 小号 101 . 移动终端根据测量配置信息对目标小区进行测量,以获得目标小区的测量结果。 [0051] 移动终端与服务小区建立RRC(无线资源控制)连接,移动终端通过RRC连接从接入网元(具体可以是管理基站的基站)获取测量配置信息 服务小区)对应于服务小区。 具体的,测量配置信息包括测量上报事件的配置,测量上报事件具体可以是事件A 3 , 一个事件 A 4 , 一个事件 A 5 , 等等。 [0052] 具体的,移动终端根据测量配置信息对目标小区进行RRM测量,得到RRM测量结果。 目标小区可以是服务小区的邻区,也可以是对应小区。 当目标小区为对应小区时,移动终端在进行测量前需要从服务小区获取对应小区的标识。 [0053] 小号 102 . 当移动终端根据目标小区的测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立 到目标单元格。 [0054] 该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0055] 通过执行 S 102 , 移动终端跳过生成指示信息对应的测量报告事件的测量报告, 跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告, 发起 与目标小区对应的接入网元建立连接,使得移动终端能够及时发起与目标小区对应的接入网元的连接建立,提高了移动终端的移动性。 [0056] 或者,在执行 S 之后 101 , 移动端选择执行S 103 而不是S 102 . [0057] 小号 103. 当移动终端根据测量结果生成测量报告,且移动终端确定该测量报告为指示信息对应的测量报告事件的测量报告时,移动终端向指示信息对应的接入网元发起连接建立 目标细胞。 [0058] 该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 [0059] 通过执行 S 103 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0060] 或者,在执行 S 之后 101 , 移动端选择执行S 104 而不是S 102 和小号 103 . [0061] 小号 104 . 当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端生成对应的测量上报事件的测量报告。 指示信息,移动终端向目标小区对应的接入网元发起连接建立。 [0062] 该指示信息用于指示移动终端在测量结果满足指示信息对应的测量报告事件的进入条件并生成测量报告时,向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0063] 通过执行 S 104 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0064] 在上述S的任何一个步骤中 102 , 小号 103 , 或小号 104 ,该指示信息是移动终端预先从服务小区对应的接入网元获取的。 可选的,移动终端通过RRC连接接收服务小区对应的接入网元发送的指示信息。 具体地,服务小区对应的接入网元可以在向移动终端下发测量配置信息的同时下发指示信息,也可以在本实施例执行前向移动终端下发指示信息。 本实施例以测量上报事件为事件A为例 3 或事件 A 4 用来。 当测量报告事件具体为事件A时 3 ,测量上报事件的进入条件为:“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”。 当测量报告事件具体为事件A时 4,测量上报事件的进入条件为:“Mn+Ofn+Ocn−Hys>Thresh”。 Mn是目标小区的测量结果,Ofn是目标小区的频率特定偏移,Ocn是目标小区的小区个体偏移。 如果目标小区没有配置小区个体偏移,当应用公式时,Ocn的值可以为0。Ms是服务小区的测量结果,Ofs是服务小区的频率特定偏移,Ocs是 服务小区的小区个体偏移,Hys为事件迟滞参数,Off为事件偏移参数,Thresh为事件阈值参数。 Ofn、Ocn、Hys、Ofs、Ocs、Off等参数由移动终端预先获取。 [0065] 具体地,在通信传输中,指示信息具体为至少一个数据。 至少一个数据包括测量报告事件的标识。 例如,如果至少一个数据包括标识符“A 3 ”,表示该指示信息对应的测量上报事件为事件A 3 . 或者,所述至少一个数据具体为特定标识。 特定标识可以位于测量配置信息中,与测量配置信息中关于测量上报事件的配置相关联。 例如,如果测量配置信息的部分内容是关于事件A的配置 3 , 指定的标识符与事件A的配置相关联 3 在测量配置信息中,可以指示该指示信息对应的测量上报事件为事件A 3 . [0066] 可能的,该指示信息至少有一条,该指示信息对应的测量上报事件至少有一个。 [0067] 可选的,该指示信息具体可以为直接重建指示、小区更新指示或前向切换指示。 [0068] 本实施例中,指示信息用于当测量结果满足指示信息对应的测量上报事件的进入条件时,指示移动终端向目标小区对应的接入网元发起连接建立。 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 [0069] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图。 如图2所示,在图1所示实施例的基础上,对本实施例的实施方式进行说明,具体包括以下步骤。 [0070] 小号 201 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0071] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0072] 小号 202 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0073] 该步骤在 S 中具体描述 101 . 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0074] 小号 203 . 移动终端判断目标小区的测量结果是否满足该指示信息对应的测量上报事件的进入条件,如果满足,移动终端执行S 204 ,否则,本实施例结束。 [0075] 可选的,在本实施例中,指示信息至少有一条,与指示信息对应的测量上报事件至少有一个。 [0076] 例如,如果移动终端在S中接收到两条指示信息 201 , 两条指示信息之一对应事件A 3 , 另一个对应事件A 4 . 当在 S 中获得的测量结果 202 满足事件A任一测量上报事件的进入条件 3 或事件 A 4 ,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行如下S 204 . [0077] 或者,若在S中获取到一条指示信息 201 ,指示信息对应事件A 3 和一个事件 A 4 , 当在 S 中获得的测量结果 202 满足事件A的进入条件 3 或事件 A 4 ,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行如下S 204 . [0078] 或者,若S中获取的指示信息 201 对应一个事件A 3 , 当在 S 中获得的测量结果 202 满足事件A的进入条件 3 ,移动终端执行以下S 204 . 即当Mn满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,移动终端执行S 204 . 而当Mn满足“Mn+Ofn+Ocn-Hys>Thresh”但不满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,本实施例结束,即进入条件为 测量上报事件的条件,测量结果满足的不是该指示信息对应的测量上报事件的进入条件。 [0079] 还需要说明的是,如果该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,则测量结果满足该指示信息对应的测量上报事件的进入条件 ,移动终端可以直接执行S 205 确定后,通过执行 S 203,则目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 但是,为保证通信网络中网络侧设备对移动终端的控制效果不受影响,同时兼顾移动终端的移动性,本实施例中,优选的,所述指示信息为 用于如果测量结果满足指示信息对应的测量上报事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成测量上报的测量报告 指示信息对应的事件。 移动终端执行S 204 和小号 205 确定后依次执行S 203 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0080] 小号 204 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0081] 小号 205 . 移动终端向目标小区对应的接入网元发起连接建立。 [0082] S中的连接建立 205 具体包括: [0083] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理:[0084] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 [0085] 图3为本发明实施例二的RRC连接建立过程示意图。 如图3所示,具体过程包括以下步骤: [0086] C 11 . 移动终端向目标小区对应的接入网元发送RRC连接建立请求。 [0087] C 12 . 移动终端接收目标小区对应的接入网元发送的RRC连接建立消息。 [0088] C 13 . 移动终端向目标小区对应的接入网元发送RRC连接建立完成消息。 [0089] 图4为本发明实施例二的RRC连接重建过程示意图。 如图4所示,具体过程包括以下步骤: [0090] C 21 . 移动终端向目标小区对应的接入网元发送RRC连接重建请求。 [0091] C 22 . 移动终端接收目标小区对应的接入网元发送的RRC连接重建消息。 [0092] C 23 . 移动终端向目标小区对应的接入网元发送RRC连接重建完成消息。 [0093] 图5为本发明实施例二的小区更新过程示意图。 如图5所示,具体过程包括以下步骤: [0094] C 31 . 移动终端向目标小区对应的接入网元发送小区更新请求。 [0095] C 32 . 移动终端接收目标小区对应的接入网元发送的小区更新消息。 [0096] C 33 . 移动终端向目标小区对应的接入网元发送小区更新完成消息。 [0097] C 33 为可选步骤,可以根据实际网络情况执行也可以不执行。 [0098] 图6为本发明实施例二的基于竞争的随机接入信道过程示意图。 如图6所示,具体过程包括以下步骤: [0099] C 41 . 移动端发送消息 1 到目标小区对应的接入网元。 讯息 1 特别是“随机访问前导码”。 [0100] C 42 . 移动端收到消息 2 由目标小区对应的接入网元发送。 讯息 2特别是“随机访问响应”。 [0101] C 43 . 移动端发送消息 3 到目标小区对应的接入网元。 讯息 3 特别是“预定传输”。 [0102] C 44 . 移动端收到消息 4 由目标小区对应的接入网元发送。 讯息 4 具体是“争用解决”。 [0103] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图。 如图7所示,具体过程包括以下步骤: [0104] C 51 . 移动端收到消息 0 由目标小区对应的接入网元发送。 讯息 0 具体是“RA Preamble assignment”。 [0105] C 52 . 移动端发送消息 1 到目标小区对应的接入网元。 讯息 1 特别是“随机访问前导码”。 [0106] C 53 . 移动端收到消息 2 由目标小区对应的接入网元发送。 讯息 2 特别是“随机访问响应”。 [0107] 还应该注意的是,当确定时,通过执行 S 203 , 本实施例结束, 表示移动终端不再继续执行S 204 和小号 205 ,但继续按照现有技术进行其他操作。 例如,若指示信息对应的测量上报事件为事件A 3 , 但移动端在 S 中判断 203 目标小区的测量结果不满足事件A的进入条件 3 但满足事件A的进入条件 4 , 移动终端生成事件A的测量报告 4 根据满足事件A进入条件的测量结果 4 ; 发送事件A的测量报告 4 服务小区对应的接入网元; 等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到服务小区对应的接入网元下发给移动终端的允许建立连接的指示时,移动终端才建立到目标小区的连接。 [0108] 即,现有技术中,当目标小区的测量结果满足测量上报事件的进入条件时,移动终端首先需要生成测量报告,并将测量报告上报给目标小区对应的接入网元。 服务小区,然后需要等待服务小区对应的接入网元下发允许建立连接的指示。 在这个过程中,移动终端需要花费较长的时间周期,不利于提高移动终端与目标小区对应的接入网元建立连接的效率。 但是,在本说明书中,只要目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件,移动终端生成该指示信息对应的测量上报事件的测量报告,则 移动终端能够在移动终端与目标小区之间建立连接,提高了移动终端与目标小区对应的接入网元建立连接的效率,提高了移动终端的移动性。 [0109]本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立,并且移动终端生成 指示信息对应的测量上报事件的测量报告。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,以及 直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0110] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图。 如图8所示,在图1所示实施例的基础上,对本实施例的一个优选实施方式进行说明,具体包括以下步骤。 [0111] 小号 301 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0112] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0113] 小号 302 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0114] 该步骤在 S 中具体描述 101 . 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0115] 小号 303 . 移动终端根据测量结果生成测量报告。 [0116] 小号 304 . 移动终端判断该测量报告是否为该指示信息对应的测量报告事件的测量报告,如果是,则移动终端执行S 305 ,否则,本实施例结束。 [0117] 在本实施例中,该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 前提是在 S 中获得的测量结果 302 满足测量报告事件的进入条件,在S中生成测量报告 303 . 可以理解,当S中的测量结果满足测量上报事件的进入条件时 302 不是指示信息对应的测量报告事件的进入条件,S中生成的测量报告 303 也不是该指示信息对应的测量上报事件的测量报告。 [0118] 然而,如果移动终端确定,通过执行S 304 , S 中的测量报告 303为指示信息对应的测量报告事件的测量报告,即当移动终端根据指示信息确定移动终端生成指示信息对应的测量报告事件的测量报告时,移动终端 终端可以不向服务小区对应的接入网元发送该指示信息对应的测量报告事件的测量报告,直接执行S 305 . [0119] 可选的,在本实施例中,指示信息至少有一条,与指示信息对应的测量上报事件至少有一个。 [0120] 例如,如果移动终端在S中接收到两条指示信息 301 , 两条指示信息之一对应事件A 3 , 另一个对应事件A 4 , 当在 S 中获得的测量结果 302 满足事件A任一测量上报事件的进入条件 3 或事件 A 4 , S中生成的测量报告 303 必然是指示信息对应的测量上报事件的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0121] 或者,若在S中获取到一条指示信息 301 ,指示信息对应事件A 3 和一个事件 A 4 , 当在 S 中获得的测量结果 302 满足事件A的进入条件 3 或事件 A 4 , S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0122] 或者,若S中获取的指示信息 301 对应一个事件A 3 , 当在 S 中获得的测量结果 302 满足事件A的进入条件 3 , S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . 但是,有可能,如果在S中得到的指示信息 301 对应事件A 3 , 但在 S 中获得的测量结果 302 满足事件A的进入条件 4 , S中生成的测量报告 303 不是指示信息对应的测量报告而是事件A的测量报告 4 . 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 即当Mn满足“Mn+Ofn+Ocn−Hys>Thresh”但不满足“Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”时,S中生成的测量报告 303 不是指示信息对应的测量报告。 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 [0123] 小号 305 . 移动终端向目标小区对应的接入网元发起连接建立。 [0124] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理: [0125] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 具体可以参考图3至图7所示的信令流程。 [0126]本实施例中,指示信息用于指示移动终端跳过,如果移动终端生成该指示信息对应的测量报告事件的测量报告,则向服务小区对应的接入网元发送该测量 上报指示信息对应的测量上报事件。 因此,移动终端可以直接向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0127] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图。 如图9A和图9B所示,本实施例在图1所示实施例的基础上进行进一步说明,具体包括以下步骤。 [0128] 小号 401 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0129] 移动状态估计(Mobility State Estimation,MSE)是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0130] 小号 402 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0131] 小号 403 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0132] 该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0133] 小号 404 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0134] 当服务小区对应的接入网元学习时,通过执行S 402 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 403 向移动终端下发指示信息。 [0135] 测量配置信息和指示信息可以同时下发,即S 403 和小号 404 通过使用相同的信令来实现。 可选地,S 404 可以在 S 之前执行 403 ,或者可以在 S 之前或同时执行 402 ,或者可以在 S 之前或同时执行 401 . 例如,首先,移动终端接收到测量配置信息,然后,当确定移动终端在高速移动时,服务小区对应的接入网元下发指示信息。 此外,任选地,S 401 和小号 402 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0136] 小号 405 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0137]在移动终端接收到指示信息之前,移动终端根据S-Measure发现目标小区。 即移动终端只有在获知服务小区的服务质量低于预设值时才对邻区进行RRM测量,以发现测量结果满足测量上报事件的目标小区。 但在本实施例中,移动终端接收到指示信息后,可以忽略S-Measure,即移动终端可以随时对邻区进行RRM测量,无需等到服务 服务小区的质量低于预设值,从而及时判断目标小区的测量结果是否满足测量上报事件的进入条件,从而进一步提高移动终端的移动性 改善。 [0138] 小号 406 . 移动终端确定该测量结果满足该指示信息对应的测量上报事件的进入条件。 [0139] 可以理解的是,如果移动终端与目标小区建立连接,则移动终端在任意时刻确定目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 ,弱化了网络侧设备(如基站或基站控制器)对移动终端的控制。 但是,移动终端处于短周期DRX状态或长周期DRX状态时,对移动性的影响较大。 因此,可选地,当本实施例的移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示建立到目标小区的连接,即 移动端还需要执行以下S 407 执行 S 后 406 . [0140] 小号 407 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 409 或 408 ,或者如果否,则执行 S 410 . [0141] DRX状态为短周期DRX状态或长周期DRX状态。 [0142] 现有技术中,移动终端处于休眠状态的时长也会影响移动终端的移动性。 另外,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端处于休眠状态的时间较长,对移动终端的移动性影响更为严重。 . 而本实施例中,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示及时建立到目标小区的连接,以及 移动终端的移动性不受移动终端的短周期DRX状态或长周期DRX状态的影响。 [0143] 小号 408 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 409 ,或者如果是,则执行 S 410 . [0144] 当移动终端位于服务小区和目标小区的临界区域时,如果移动终端的移动速度较低,则移动终端更容易发生目标小区和服务小区之间的“乒乓切换”。 为了避免发生乒乓切换的情况,优选地,S 408 需要执行。 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 409 . [0145]另外,移动终端指定的速度门限和服务小区对应的接入网元指定的速度门限可以相同,也可以不同。 另外,移动终端指定的速度门限可以由服务小区对应的接入网元为移动终端配置,或者在通信协议中指定,例如,移动终端的速度门限为 高机动状态的速度。 [0146] 此外,S 407 和小号 408 为可选步骤,即在实际应用中实施本实施例时,移动终端可以选择执行S 407 和/或 408 执行 S 后 406 , 以及执行 S 的序列 407 和小号 408 不受限制。 在这个实施例中,一个例子中 S 408 在 S 之后执行 407 使用确定移动终端处于DRX状态。 [0147] 小号 409 . 移动终端向目标小区对应的接入网元发起连接建立。 [0148] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 因此,当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立。 目标细胞。 即,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的进入条件后,可以不生成该指示信息对应的测量上报事件的测量报告,不发送 , 向服务小区对应的接入网元, 指示信息对应的测量报告事件的测量报告, 向目标小区对应的接入网元发起连接建立, 使得移动终端可以发起, 在 及时与目标小区对应的接入网元建立连接,提高移动终端的移动性。 [0149] 小号 410 . 移动终端生成指示信息对应的测量报告事件的测量报告,并向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 [0150] 在本实施例中,即使移动终端接收到指示信息,并且目标小区的测量结果满足该指示信息对应的测量报告事件的进入条件,移动终端也可以根据S中的判断结果进行选择。 407 和/或 408 ,应用指示信息(即,执行S 409 ). 或者,移动终端根据S中的判断结果进行选择 407 和/或 408 , 不应用指示信息; 仍然按照现有技术与目标小区对应的接入网元建立连接,即执行S 410 ; 然后,等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0151]本实施例中,移动终端根据目标小区的测量结果确定该测量结果满足指示信息对应的测量上报事件的进入条件后,根据该指示信息的指示,移动终端可以跳过生成 指示信息对应的测量上报事件的测量报告, 并跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告, 使得移动终端可以直接 向目标小区对应的接入网元发起连接建立,提高移动终端的移动性。 [0152] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图。 如图10A和图10B所示,在图1或图2所示实施例的基础上,在一个优选实施方式中,本实施例具体包括以下步骤。 [0153] 小号 501 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0154] 移动状态估计是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0155] 小号 502 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0156] 小号 503 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0157] 该指示信息用于当测量结果满足该指示信息对应的测量报告事件的进入条件并生成测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0158] 小号 504 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0159] 当服务小区对应的接入网元学习时,通过执行S 502 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 503 向移动终端下发指示信息。 [0160] 测量配置信息和指示信息可以同时下发,即S 503 和小号 504 通过使用相同的信令来实现。 可选地,S 504 可以在 S 之前执行 503 ,或者可以在 S 之前或同时执行 502 ,或者可以在 S 之前或同时执行 501 . 例如,首先,移动终端接收到测量配置信息,然后,接入网元在确定移动终端高速移动时,下发指示信息。 此外,任选地,S 501 和小号 502 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0161] 小号 505 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0162] 小号 506 . 移动终端判断测量结果是否满足指示信息对应的测量上报事件的进入条件,如果满足,则执行S 507 ,或者如果否,则执行 S 511 . [0163] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件且移动终端向目标小区对应的接入网元发起连接建立时。 生成指示信息对应的测量报告事件的测量报告。 因此,本实施例中的移动终端通过执行S来确定 506 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0164] 可能的,如果测量结果既不满足指示信息对应的测量上报事件的进入条件,也不满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件,本实施例 结束,即移动终端不再进行后续步骤。 [0165] 但是,若测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件, 在该实施例中,根据现有技术,S 511 执行和小号 512 随后执行。 图9以测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件为例 指示信息。 [0166] 小号 507 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0167] 小号 508 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 510 或 509 ,或者如果否,则执行 S 512 . [0168] DRX状态为短周期DRX状态或长周期DRX状态。 [0169] 小号 509 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 510 ,或者如果是,则执行 S 512 . [0170] 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 510 . [0171] 小号 508 和小号 509 为可选步骤,即在实际应用中实施本实施例时,移动终端可以选择执行S 508 和/或 509 执行 S 后 507 , 以及执行 S 的序列 508 和小号 509 不受限制。 本实施例以移动终端继续执行S为例 509 执行 S 后 508 使用确定移动终端处于DRX状态。 [0172] 小号 510 . 移动终端向目标小区对应的接入网元发起连接建立。 [0173] 可选的,移动终端向目标小区对应的接入网元发起连接建立后,移动终端与服务小区对应的接入网元保持连接。 [0174] 小号 511. 移动终端根据满足测量报告事件的进入条件的测量结果生成测量报告,该测量报告事件不同于指示信息对应的测量报告事件的进入条件。 [0175] 小号 512 . 移动终端将测量报告发送给服务小区对应的接入网元。 [0176] 如果 S 之前的一步 512 是小号 508 或 509 ,移动终端发送的测量报告为指示信息对应的测量报告事件的测量报告。 如果 S 之前的一步 512 是小号 511 ,移动终端发送的测量报告是移动终端根据测量报告事件的满足进入条件的测量结果生成的测量报告,不同于指示信息对应的测量报告事件的进入条件 . [0177] 当 S 前一步 512 是小号 508 或 509 ,表示即使移动终端接收到指示信息,目标小区的测量结果也满足该指示信息对应的测量上报事件的进入条件,移动终端生成对应的测量上报事件的测量报告 对于指示信息,移动终端根据S中的判断结果进行选择 508 和/或 509 ,以应用指示信息(即,执行 S 510 ). 或者,移动终端根据S中的判断结果进行选择 508 和/或 509 , 不应用指示信息; 仍然按照现有技术建立到目标小区的连接,即执行S 512 将测量报告发送给服务小区对应的接入网元; 然后,等待接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0178] 可以理解的是,现有技术中的通信过程中已经包含了关于测量报告生成的协议、配置等。 因此,在基于现有协议或配置应用本实施例时,需要调整和修改的内容较少,范围较小,有利于本实施例的实施。 [0179] 本实施例中,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的进入条件后,生成该指示信息对应的测量上报事件的测量报告,然后, 移动终端可以直接向目标小区对应的接入网元发起连接建立。 然而,现有技术中,当目标小区的测量结果满足测量上报(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.769 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.771 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10499298B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), CN105659666A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), EP3193534A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), EP3193534A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), US10142904B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.819 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.820 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), US10499298B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.831 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), US10805853B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.841 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), US20170251417A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), US20190075502A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.858 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), US20200068471A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270699(Integer), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10499298B2(String), US10499298B2(String), 1575302400(Integer), 270699(Integer), 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.888 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.889 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185022(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185022(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.899 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185022(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.903 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185022(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.910 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.911 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.912 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.934 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10805853B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10805853B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/669334(String), 1572364800(Integer), US10805853B2(String), 1602518400(Integer), 1602518400(Integer), 美国(String), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), 19(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.947 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185023(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\9e44fecfffd849bcb8cc63f624208eb6.png(String), 185023(Integer), 9e44fecfffd849bcb8cc63f624208eb6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.961 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10805853B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/669334(String), 1572364800(Integer), US10805853B2(String), 1602518400(Integer), 1602518400(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), \20230420\9e44fecfffd849bcb8cc63f624208eb6.png(String), 19(Integer), 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.974 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 1. A method, comprising:receiving, by the mobile terminal from an access network element corresponding to a target cell, measurement configuration information by using a radio resource control (RRC) connection established between the mobile terminal and the access network element corresponding to the target cell;measuring, by the mobile terminal, the target cell according to the measurement configuration information, to obtain a measurement result of the target cell; andinitiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; orinitiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information.(String), 1.一种方法,包括:移动终端通过移动终端与目标小区对应的接入网元之间建立的无线资源控制(RadioResourceControl,无线资源控制)连接从目标小区对应的接入网元接收测量配置信息;移动终端根据测量配置信息对目标小区进行测量,得到目标小区的测量结果;和当移动终端根据测量结果确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网网元的连接建立;或者当移动终端根据测量结果生成测量报告时,移动终端发起到目标小区对应的接入网网元的连接建立,移动终端确定该测量报告为测量报告的测量报告指示信息对应的事件,其中,所述指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 2. The method according to claim 1, wherein initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell comprises:skipping, by the mobile terminal, sending, to the access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiating connection establishment to the access network element corresponding to the target cell.(String), 2.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 3. The method according to claim 1, wherein:the initiating, by the mobile terminal, of the connection establishment to an access network element corresponding to the target cell further comprises:initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and the indication information, that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, and when the mobile terminal determines that a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orinitiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell when the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information and determines that a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 3.根据权利要求1所述的方法,其中:移动终端发起与目标小区对应的接入网元的连接建立还包括:当移动终端根据测量结果和指示信息确定测量结果满足对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网网元的连接建立接收到指示信息,当移动终端确定测量结果满足指示信息对应的测量上报事件进入条件的时长达到预定时长;或者移动终端在生成该指示信息对应的测量报告事件的测量报告并确定该测量的测量报告后的时长时,发起到目标小区对应的接入网网元的连接建立指示信息对应的上报事件产生达到预定时长。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 4. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell comprises:when the mobile terminal is in a discontinuous reception (DRX) state, initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell.(String), 4.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端处于非连续接收(DRX)状态时,移动终端向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 5. The method according to claim 4, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 5.根据权利要求4所述的方法,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 6. The method according to claim 1, wherein initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell comprises:when a mobility state estimation of the mobile terminal is greater than or equal to a speed threshold, initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell.(String), 6.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端的移动状态估计值大于或等于速度门限时,移动终端发起到目标小区对应的接入网元的连接建立。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 7. The method according to claim 1, further comprising:sending, by the mobile terminal, the mobility state estimation of the mobile terminal to the access network element corresponding to a serving cell, whereinthe indication information is sent after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold specified by the access network element corresponding to the serving cell.(String), 7.根据权利要求1所述的方法,还包括:移动终端向服务小区对应的接入网元发送移动终端的移动状态估计,其中在服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限后发送指示信息。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 8. The method according to claim 1, the initiating of the connection establishment comprises:correspondingly initiating, by the mobile terminal, a random access process to the target cell, and/or any one of the following processing:initiating, by the mobile terminal to the target cell, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 8.根据权利要求1所述的方法,发起连接建立包含:移动终端相应地发起对目标小区的随机接入过程,和/或以下任一处理:移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。9、一种配置在移动终端中的装置,包括:包括处理器可执行指令的存储介质;和耦合到存储介质的处理器,其中处理器可执行指令在由处理器执行时使装置:通过移动终端与目标小区对应的接入网元之间建立的无线资源控制(RadioResourceControl,无线资源控制)连接获取测量配置信息;根据测量配置信息对目标小区进行测量,得到目标小区的测量结果;和当测量结果满足指示信息对应的测量上报事件进入条件时,向目标小区对应的接入网元发起连接建立;或者当测量报告为指示信息对应的测量报告事件的测量报告时,向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示向目标小区对应的接入网元发起连接建立如果测量报告事件的测量报告对应于指示信息,则目标小区。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 9. An apparatus configured in a mobile terminal, comprising:a storage medium comprising processor-executable instructions; anda processor coupled to the storage medium, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:obtain measurement configuration information by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to a target cell;measure the target cell according to the measurement configuration information, to obtain a measurement result of the target cell; andinitiate connection establishment to the access network element corresponding to the target cell when the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; orinitiate connection establishment to the access network element corresponding to the target cell when a measurement report is a measurement report of a measurement reporting event corresponding to indication information, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell if the measurement report of the measurement reporting event is corresponding to the indication information.(String), 10.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,向目标小区对应的接入网元发起连接建立。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 10. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:skip sending, to the access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiate connection establishment to the access network element corresponding to the target cell.(String), 11.根据权利要求9所述的装置,其中:为了发起与目标小区对应的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当测量结果满足指示信息对应的测量上报事件进入条件,且测量结果满足测量上报进入条件时,发起到目标小区对应接入网元的连接建立指示信息对应的事件达到预定时长;或者在生成指示信息对应的测量报告事件的测量报告时,以及生成指示信息对应的测量报告事件的测量报告后的时长达到a时,向目标小区对应的接入网元发起连接建立预定的持续时间。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 11. The apparatus according to claim 9, wherein:to initiate the connection establishment to the access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:initiate the connection establishment to the access network element corresponding to the target cell when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, and when a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orinitiate the connection establishment to the access network element corresponding to the target cell when generating the measurement report of the measurement reporting event corresponding to the indication information and a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 12.根据权利要求9所述的装置,其中为了发起与目标小区对应的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当装置处于非连续接收(DRX)状态时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 12. The apparatus according to claim 9, wherein to initiate the connection establishment to the access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when the apparatus is in a discontinuous reception (DRX) state, initiate connection establishment to the access network element corresponding to the target cell.(String), 13.根据权利要求12所述的装置,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 13. The apparatus according to claim 12, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 14.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当该装置的移动性状态估计大于或等于速度门限时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 14. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when a mobility state estimation of the apparatus is greater than or equal to a speed threshold, initiate connection establishment to the access network element corresponding to the target cell.(String), 15.根据权利要求9所述的装置,其中处理器可执行指令在由处理器执行时使装置:向服务小区对应的接入网元发送所述装置的移动性状态估计,其中,所述指示信息是在服务小区对应的接入网元确定移动性状态估计大于或等于速度门限后发送的.16.根据权利要求9所述的装置,其中为了启动连接建立,处理器可执行指令在由处理器执行时使装置:相应地发起对目标小区的随机接入过程,和/或以下任一过程:向目标小区发起、RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 15. The apparatus according to claim 9, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:send the mobility state estimation of the apparatus to the access network element corresponding to a serving cell, wherein the indication information is sent after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold.(String), 17.一种存储程序代码的非暂时性计算机可读介质,供移动终端用于无线通信,其中程序代码包括以下指令:通过移动终端与目标小区对应的接入网元之间建立的无线资源控制(RadioResourceControl,无线资源控制)连接获取测量配置信息;根据测量配置信息对目标小区进行测量,得到目标小区的测量结果;和当测量结果满足指示信息对应的测量上报事件进入条件时,向目标小区对应的接入网元发起连接建立;或者当测量报告事件的测量报告对应指示信息时,向目标小区对应的接入网元发起连接建立,该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立如果移动终端生成指示信息对应的测量报告事件的测量报告,则目标小区。(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 16. The apparatus according to claim 9, wherein to initiate connection establishment, the processor-executable instructions, when executed by the processor, cause the apparatus to:correspondingly initiate a random access process to the target cell, and/or any one of the following processes:initiate to the target cell, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 18.根据权利要求17所述的非暂时性计算机可读介质,其中向目标小区对应的接入网元发起连接建立包括:跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 17. A non-transitory computer readable medium storing program codes for use by a mobile terminal for wireless communication, wherein the program codes comprise instructions for:obtaining measurement configuration information by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to the target cell;measuring a target cell according to the measurement configuration information, to obtain a measurement result of the target cell; andinitiating connection establishment to the access network element corresponding to the target cell when the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; orinitiating connection establishment to the access network element corresponding to the target cell when a measurement report of a measurement reporting event is corresponding to indication information, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information.(String), 19.根据权利要求17所述的非暂时性计算机可读介质,其中:向目标小区对应的接入网元发起连接建立还包括:当测量结果满足指示信息对应的测量上报事件的进入条件,且测量结果满足测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立指示信息对应的时间达到预定时长。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 18. The non-transitory computer readable medium according to claim 17, wherein initiating the connection establishment to the access network element corresponding to the target cell comprises:skipping sending, to the access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiating connection establishment to the access network element corresponding to the target cell.(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:01.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185023(Integer), 19. The non-transitory computer readable medium according to claim 17, wherein:the initiating of the connection establishment to the access network element corresponding to the target cell further comprises:initiating the connection establishment to the access network element corresponding to the target cell when the measurement result meets the entering condition of the measurement reporting event corresponding to indication information, and when a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration.(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.129 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.130 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185023(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. application Ser. No. 16/180,651, filed on Nov. 5, 2018, which is a continuation of U.S. application Ser. No. 15/473,407, filed on Mar. 29, 2017, now U.S. Pat. No. 10,142,904, which is a continuation of International Application No. PCT/CN2014/088061, filed on Sep. 30, 2014. All of the afore-mentioned patent applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present invention relate to the field of communications technologies, and in particular, to a mobile terminal control method and a mobile terminal. BACKGROUND [0003]Currently, a mobile terminal and life of a user are closely related to each other. Usually, the user performs a communication service such as chat by using the mobile terminal while being on a vehicle such as a bus or a subway. In this case, the mobile terminal also moves at high speed as the vehicle moves. Because the mobile terminal moves at relatively high speed, in terms of a physical location, after the mobile terminal enters from a coverage area of a previous serving cell to a coverage area of a new cell, quality of a communication service provided by the serving cell is deteriorated. In addition, because the mobile terminal cannot establish a connection to the new cell in a timely manner either, mobility of the mobile terminal is affected. For example, because the quality of the communication service provided by the serving cell is deteriorated, and the mobile terminal cannot establish a connection to the new cell in a timely manner either, a communication service currently performed by the mobile terminal is interrupted. [0004]Specifically, before establishing a connection to an access network element corresponding to the new cell, the mobile terminal needs to send a measurement report about the new cell to an access network element corresponding to the serving cell. The mobile terminal may establish a connection to a new cell only when the mobile terminal receives an indication that connection establishment is allowed and that is sent by the access network element corresponding to the serving cell. It may be understood that, by using the prior art, the mobile terminal needs to wait for a relatively long time period from discovering the new cell to establishing a connection to the new cell, and cannot establish a connection to the new cell in a timely manner to obtain a communication service provided by the new cell. Particularly, when the mobile terminal is in a discontinuous reception (DRX) state, an interval at which the mobile terminal measures the serving cell and an interval at which the mobile terminal measures the new cell become longer. For example, when a DRX cycle is 320 ms, and the mobile terminal needs to spend 5 times the DRX cycle performing radio resource management (RRM) measurement on a neighboring cell, the mobile terminal needs to spend a longer time period from discovering a new cell to establishing a connection to the new cell, and mobility of the mobile terminal cannot meet a basic requirement of the user. Therefore, how the mobile terminal establishes a connection to a new cell in a timely manner is an important aspect of improving performance of the mobile terminal. SUMMARY [0005]Embodiments of the present invention provide a mobile terminal control method and a mobile terminal, so as to improve mobility of the mobile terminal. [0006]According to a first aspect, an embodiment of the present invention provides a processing method for establishing a connection to an access network element by a mobile terminal, and the method includes: [0007]measuring, by a mobile terminal, a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and [0008]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or [0009]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information; or [0010]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and when the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information, where [0011]the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. [0012]According to a second aspect, an embodiment of the present invention provides a method for controlling a DRX state of a mobile terminal, and the method includes: [0013]performing, by a mobile terminal, radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and [0014]when the mobile terminal determines, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold, [0015]starting, by the mobile terminal, a timer, and before the timer expires, transitioning the mobile terminal from a DRX state to a non-DRX state, or transitioning the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shortening a cycle of the DRX state. [0016]According to a third aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes: [0017]a measurement module, configured to measure a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and [0018]a processing module, configured to: initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or [0019]initiate connection establishment to an access network element corresponding to the target cell when generating a measurement report according to the measurement result, and determining that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the processing module generates the measurement report of the measurement reporting event corresponding to the indication information; or [0020]initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the processing module generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the processing module generates the measurement report of the measurement reporting event corresponding to the indication information, where [0021]the indication information is obtained by the processing module in advance from the access network element corresponding to the serving cell. [0022]According to a fourth aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes: [0023]an obtaining module, configured to perform radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and [0024]a processing module, configured to: when determining, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold, [0025]start a timer, and before the timer expires, transition the mobile terminal from a DRX state to a non-DRX state, or transition the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shorten a cycle of the DRX state. [0026]According to the mobile terminal control method and the mobile terminal that are provided in the embodiments of the present invention, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. BRIEF DESCRIPTION OF THE DRAWINGS [0027]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0028]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0029]FIG. 3 is a schematic diagram of an RRC connection establishment process according to Embodiment 2 of the present invention; [0030]FIG. 4 is a schematic diagram of an RRC connection re-establishment process according to Embodiment 2 of the present invention; [0031]FIG. 5 is a schematic diagram of a cell update process according to Embodiment 2 of the present invention; [0032]FIG. 6 is a schematic diagram of a contention-based random access process according to Embodiment 2 of the present invention; [0033]FIG. 7 is a schematic diagram of a non-contention-based random access channel process according to Embodiment 2 of the present invention; [0034]FIG. 8 is a schematic flowchart of Embodiment 3 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0035]FIG. 9A and FIG. 9B are a schematic flowchart of Embodiment 4 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0036]FIG. 10A and FIG. 10B are a schematic flowchart of Embodiment 5 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0037]FIG. 11A and FIG. 11B are a schematic flowchart of Embodiment 6 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0038]FIG. 12A to FIG. 12C are a schematic flowchart of Embodiment 7 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0039]FIG. 13A to FIG. 13C are a schematic flowchart of Embodiment 8 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0040]FIG. 14A to FIG. 14C are a schematic flowchart of Embodiment 9 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0041]FIG. 15A to FIG. 15C are a schematic flowchart of Embodiment 10 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0042]FIG. 16 is a schematic flowchart of Embodiment 1 of a method for controlling a DRX state of a mobile terminal according to the present invention; [0043]FIG. 17 is a schematic structural diagram of Embodiment 1 of a mobile terminal according to the present invention; [0044]FIG. 18 is a schematic structural diagram of Embodiment 2 of a mobile terminal according to the present invention; [0045]FIG. 19 is a schematic structural diagram of Embodiment 3 of a mobile terminal according to the present invention; [0046]FIG. 20 is a schematic structural diagram of Embodiment 4 of a mobile terminal according to the present invention; [0047]FIG. 21 is a schematic structural diagram of Embodiment 5 of a mobile terminal according to the present invention; and [0048]FIG. 22 is a schematic structural diagram of Embodiment 6 of a mobile terminal according to the present invention. DETAILED DESCRIPTION [0049]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 1, this embodiment is executed by a mobile terminal, and specifically includes the following operations. [0050]S101. The mobile terminal measures a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell. [0051]The mobile terminal establishes an RRC (radio resource control) connection to a serving cell, and the measurement configuration information is obtained by the mobile terminal, by using the RRC connection, from an access network element (which may be specifically a base station that manages the serving cell) corresponding to the serving cell. Specifically, the measurement configuration information includes a configuration about a measurement reporting event and the measurement reporting event may be specifically an event A3, an event A4, an event A5, or the like. [0052]Specifically, the mobile terminal performs RRM measurement on the target cell according to the measurement configuration information, so as to obtain an RRM measurement result. The target cell may be a neighboring cell of the serving cell, or may be a corresponding cell. When the target cell is a corresponding cell, the mobile terminal needs to obtain an identity of the corresponding cell from the serving cell before the mobile terminal performs measurement. [0053]S102. When the mobile terminal determines, according to the measurement result of the target cell and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0054]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0055]By performing S102, the mobile terminal skips generating a measurement report of the measurement reporting event corresponding to the indication information, skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0056]Alternatively, after performing S101, the mobile terminal chooses to perform S103 instead of S102. [0057]S103. When the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0058]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to indication information. [0059]By performing S103, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0060]Alternatively, after performing S101, the mobile terminal chooses to perform S104 instead of S102 and 103. [0061]S104. When the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0062]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information. [0063]By performing S104, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0064]In any one operation of the foregoing S102, S103, or S104, the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. In one embodiment, the mobile terminal receives, by using the RRC connection, the indication information sent by the access network element corresponding to the serving cell. Specifically, the access network element corresponding to the serving cell may deliver the indication information while delivering the measurement configuration information to the mobile terminal, or may deliver the indication information to the mobile terminal before this embodiment is executed. In this embodiment, an example in which the measurement reporting event is the event A3 or the event A4 is used. When the measurement reporting event is specifically the event A3, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”. When the measurement reporting event is specifically the event A4, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Thresh”. Mn is the measurement result of the target cell, Ofn is a frequency specific offset of the target cell, and Ocn is a cell individual offset of the target cell. If the target cell is not configured with the cell individual offset, when the formulas are applied, a value of Ocn may be 0. Ms is a measurement result of the serving cell, Ofs is a frequency specific offset of the serving cell, Ocs is a cell individual offset of the serving cell, Hys is an event hysteresis parameter, Off is an event offset parameter, and Thresh is an event threshold parameter. Parameters such as Ofn, Ocn, Hys, Ofs, Ocs, and Off are obtained by the mobile terminal in advance. [0065]Specifically, in communication transmission, the indication information is specifically at least one piece of data. The at least one piece of data includes an identifier of the measurement reporting event. For example, if the at least one piece of data includes an identifier “A3”, it indicates that the measurement reporting event corresponding to the indication information is the event A3. Alternatively, the at least one piece of data is specifically a specific identifier. The specific identifier may be located in measurement configuration information, and is associated with the configuration about the measurement reporting event in the measurement configuration information. For example, if partial content of the measurement configuration information is a configuration about the event A3, and the specified identifier is associated with the configuration about the event A3 in the measurement configuration information, it may indicate that the measurement reporting event corresponding to the indication information is the event A3. [0066]In one embodiment, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0067]In one embodiment, the indication information may be specifically a direct re-establishment indication, a cell update indication, or a forward handover indication. [0068]In this embodiment, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0069]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 2, on the basis of the embodiment shown in FIG. 1, this embodiment is described in a implementation manner, and specifically includes the following operations. [0070]S201. A mobile terminal receives measurement configuration information and indication information that are sent by an access network element corresponding to a serving cell. [0071]The measurement configuration information and the indication information may be sent, to the mobile terminal by using same signaling, by the access network element corresponding to the serving cell, or may be sent, to the mobile terminal by using different signaling, by the access network element corresponding to the serving cell. [0072]S202. The mobile terminal measures a target cell, so as to obtain a measurement result of the target cell. [0073]The operation is specifically described in S101. However, it should be noted that, in addition to being a newly discovered neighboring cell, the target cell may be a specified cell described in the S101, and may be specifically specified by the indication information. That is, if the indication information further carries a cell identity, a cell corresponding to the cell identity carried in the indication information is the target cell. [0074]S203. The mobile terminal determines whether the measurement result of the target cell meets an entering condition of a measurement reporting event corresponding to the indication information, and if yes, the mobile terminal performs S204, or if no, this embodiment ends. [0075]In one embodiment, in this embodiment, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0076]For example, if the mobile terminal receives two pieces of indication information in S201, one of the two pieces of indication information is corresponding to an event A3, and the other is corresponding to an event A4. When the measurement result obtained in S202 meets an entering condition of either measurement reporting event of the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S 204. [0077]Alternatively, if one piece of indication information is obtained in S201, and the indication information is corresponding to an event A3 and an event A4, when the measurement result obtained in S202 meets an entering condition of either the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S204. [0078]Alternatively, if the indication information obtained in S201 is corresponding to an event A3, when the measurement result obtained in S202 meets an entering condition of the event A3, the mobile terminal performs the following S204. That is, when Mn meets “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, the mobile terminal performs S204. However, when Mn meets “Mn+Ofn+Ocn−Hys>Thresh” but does not meet “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, this embodiment ends, that is, an entering condition that is of a measurement reporting event and is met by the measurement result is not the entering condition of the measurement reporting event corresponding to the indication information. [0079]It should be additionally noted that, if the indication information is used to instruct the mobile terminal to initiate connection establishment to an access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal may directly perform S205 after determining, by performing S203, that the measurement result of the target cell meets the entering condition of the measurement reporting event corresponding to the indication information. However, to ensure that a control effect, on the mobile terminal, of a network-side device in a communications network is not affected and to give consideration to mobility of the mobile terminal as well, in this embodiment, preferably, the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. The mobile terminal performs S204 and S205 in sequence after determining, by performing S203, that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0080]S204. The mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. [0081]S205. The mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0082]The connection establis(String), 相关申请的交叉引用 [0001] 该申请是美国申请 Ser. 第 16/180,651 号,于 2018 年 11 月 5 日提交,是美国申请序列号的延续。 第 15/473,407 号,2017 年 3 月 29 日提交,现为美国专利。 美国专利第 10,142,904 号是 2014 年 9 月 30 日提交的国际申请号 PCT/CN2014/088061 的延续。所有上述专利申请均通过引用整体并入本文。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种移动终端控制方法及移动终端。 背景 [0003] 目前,移动终端与用户的生活息息相关。 通常,用户在诸如公共汽车或地铁的交通工具上通过使用移动终端进行诸如聊天的通信服务。 在这种情况下,移动终端也随着车辆的移动而高速移动。 由于移动终端移动速度较高,从物理位置上来说,移动终端从上一个服务小区的覆盖范围进入到新的小区覆盖范围后,服务小区提供的通信服务质量 恶化。 另外,由于移动终端也无法及时与新小区建立连接,影响了移动终端的移动性。 例如,由于服务小区提供的通信服务质量下降,移动终端也无法及时建立到新小区的连接,导致移动终端当前进行的通信服务中断。 [0004] 具体地,移动终端在与新小区对应的接入网元建立连接之前,需要向服务小区对应的接入网元发送关于新小区的测量报告。 只有当移动终端接收到服务小区对应的接入网元发送的允许建立连接的指示时,移动终端才可以建立到新小区的连接。 可以理解的是,采用现有技术,移动终端从发现新小区到与新小区建立连接需要等待较长的时间,不能及时与新小区建立连接。 获得新小区提供的通信服务的方式。 特别地,当移动终端处于非连续接收(DRX)状态时,移动终端测量服务小区的间隔和移动终端测量新小区的间隔变长。 例如,当DRX周期为320ms时,移动终端需要花费5倍的DRX周期对邻区进行无线资源管理(Radio Resource Management,无线资源管理)测量,则移动终端需要花费更长的时间才能发现新的小区。 小区与新小区建立连接,移动终端的移动性不能满足用户的基本需求。 因此,移动终端如何及时建立与新小区的连接是提高移动终端性能的重要方面。 概括 [0005] 本发明实施例提供一种移动终端控制方法及移动终端,以提高移动终端的移动性。 [0006] 第一方面,本发明实施例提供了一种移动终端与接入网元建立连接的处理方法,该方法包括: [0007] 移动终端根据测量配置信息对目标小区进行测量,以获取目标小区的测量结果,其中,移动终端获取测量配置信息,使用之间建立的无线资源控制RRC连接 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和 [0008]当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立; 或者 [0009] 当移动终端根据测量结果生成测量报告时,移动终端发起到目标小区对应的接入网元的连接建立,移动终端确定该测量报告为测量报告的测量报告 指示信息对应的事件,该指示信息用于在移动终端生成该指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立; 或者 [0010] 当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,当移动终端生成该指示信息对应的测量报告事件的测量报告时,该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,如果 测量结果满足指示信息对应的测量上报事件的进入条件,移动终端生成指示信息对应的测量上报事件的测量报告,其中 [0011] 指示信息是移动终端预先从服务小区对应的接入网元获取的。 [0012] 第二方面,本发明实施例提供了一种移动终端的DRX状态控制方法,该方法包括: [0013] 移动终端根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,以获取服务小区的下行无线链路质量; 和 [0014] 当移动终端通过估计下行无线链路质量,确定下行无线链路连续出现失步指示的次数达到预设门限时, [0015] 移动终端启动定时器,在定时器超时之前,将移动终端从DRX状态转变为非DRX状态,或者将移动终端从长周期DRX状态转变为短周期DRX状态 ,或者缩短DRX状态的周期。 [0016] 第三方面,本发明实施例提供了一种移动终端,该移动终端包括: [0017] 测量模块,用于根据测量配置信息对目标小区进行测量,以获取所述目标小区的测量结果,所述测量配置信息为所述移动终端通过与所述目标小区之间建立的无线资源控制RRC连接获得的 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和 [0018]处理模块,用于在根据所述测量结果和指示信息确定所述测量结果满足所述指示信息对应的测量上报事件的进入条件时,发起到所述目标小区对应的接入网元的连接建立 , 该指示信息用于指示处理模块如果测量结果满足该指示信息对应的测量上报事件的进入条件,则向目标小区对应的接入网元发起连接建立; 或者 [0019] 根据测量结果生成测量报告时,向目标小区对应的接入网元发起连接建立,确定该测量报告为指示信息对应的测量报告事件的测量报告,其中使用该指示信息 若处理模块生成指示信息对应的测量上报事件的测量报告,则指示处理模块向目标小区对应的接入网元发起连接建立; 或者 [0020] 当根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,发起到目标小区对应的接入网元的连接建立,处理模块生成 指示信息对应的测量上报事件的测量报告,指示信息用于在测量结果满足测量上报进入条件时,指示处理模块向目标小区对应的接入网元发起连接建立 指示信息对应的事件,处理模块生成指示信息对应的测量报告事件的测量报告,其中 [0021] 指示信息由处理模块预先从服务小区对应的接入网元获取。 [0022] 第四方面,本发明实施例提供一种移动终端,该移动终端包括: [0023] 获取模块,用于根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,获取服务小区的下行无线链路质量; 和 [0024] 处理模块,用于通过对所述下行无线链路质量的估计,确定所述下行无线链路连续出现失步指示的次数达到预设门限时, [0025] 启动定时器,在定时器超时前,将移动终端从DRX状态转移到非DRX状态,或者将移动终端从长周期DRX状态转移到短周期DRX状态,或者缩短周期 DRX 状态。 [0026]本发明实施例提供的移动终端控制方法及移动终端,通过指示信息指示移动终端在测量结果满足时,向目标小区对应的接入网元发起连接建立。 指示信息对应的测量上报事件的进入条件; 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 附图的简要说明 [0027] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图; [0028] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图; [0029] 图3为本发明实施例二的RRC连接建立过程示意图; [0030] 图4为本发明实施例二的RRC连接重建过程示意图; [0031] 图5为本发明实施例二的小区更新过程示意图; [0032] 图6为本发明实施例二的基于竞争的随机接入过程的示意图; [0033] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图; [0034] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图; [0035] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图; [0036] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图; [0037] 图11A和图11B为本发明移动终端与小区建立连接的处理方法实施例六的流程示意图; [0038] 图12A至图12C为本发明移动终端与小区建立连接的处理方法实施例七的流程示意图; [0039] 图13A至图13C为本发明移动终端与小区建立连接的处理方法实施例八的流程示意图; [0040] 图14A至图14C为本发明移动终端与小区建立连接的处理方法实施例九的流程示意图; [0041]图15A至图15C为本发明移动终端与接入网元建立连接的处理方法实施例十的流程示意图; [0042] 图16为本发明移动终端的DRX状态控制方法实施例一的流程示意图; [0043] 图17为本发明移动终端实施例一的结构示意图; [0044] 图18为本发明移动终端实施例二的结构示意图; [0045] 图19为本发明移动终端实施例三的结构示意图; [0046] 图20为本发明移动终端实施例四的结构示意图; [0047] 图21为本发明移动终端实施例五的结构示意图; 和 [0048] 图22为本发明移动终端实施例六的结构示意图。 详细说明 [0049] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图。 如图1所示,本实施例的执行主体为移动终端,具体包括以下操作。 [0050] 小号 101 . 移动终端根据测量配置信息对目标小区进行测量,以获得目标小区的测量结果。 [0051] 移动终端与服务小区建立RRC(无线资源控制)连接,移动终端通过RRC连接从接入网元(具体可以是管理基站的基站)获取测量配置信息 服务小区)对应于服务小区。 具体地,测量配置信息包括关于测量上报事件的配置,测量上报事件具体可以为事件A3、事件A4、事件A5等。 [0052] 具体的,移动终端根据测量配置信息对目标小区进行RRM测量,得到RRM测量结果。 目标小区可以是服务小区的邻区,也可以是对应小区。 当目标小区为对应小区时,移动终端在进行测量前需要从服务小区获取对应小区的标识。 [0053] 小号 102 . 当移动终端根据目标小区的测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立 到目标单元格。 [0054] 该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0055] 通过执行 S 102 , 移动终端跳过生成指示信息对应的测量报告事件的测量报告, 跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告, 发起 与目标小区对应的接入网元建立连接,使得移动终端能够及时发起与目标小区对应的接入网元的连接建立,提高了移动终端的移动性。 [0056] 或者,在执行 S 之后 101 , 移动端选择执行S 103 而不是S 102 . [0057] 小号 103. 当移动终端根据测量结果生成测量报告,且移动终端确定该测量报告为指示信息对应的测量报告事件的测量报告时,移动终端向指示信息对应的接入网元发起连接建立 目标细胞。 [0058] 该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 [0059] 通过执行 S 103 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0060] 或者,在执行 S 之后 101 , 移动端选择执行S 104 而不是S 102 和 103 . [0061] 小号 104 . 当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端生成对应的测量上报事件的测量报告。 指示信息,移动终端向目标小区对应的接入网元发起连接建立。 [0062] 该指示信息用于指示移动终端在测量结果满足指示信息对应的测量报告事件的进入条件并生成测量报告时,向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0063] 通过执行 S 104 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0064] 在上述 S 的任何一个操作中 102 , 小号 103 , 或小号 104,该指示信息是移动终端预先从服务小区对应的接入网元获取的。 在一个实施例中,移动终端通过RRC连接接收服务小区对应的接入网元发送的指示信息。 具体地,服务小区对应的接入网元可以在向移动终端下发测量配置信息的同时下发指示信息,也可以在本实施例执行前向移动终端下发指示信息。 本实施例以测量上报事件为事件A3或事件A4为例。 当测量上报事件具体为事件A3时,测量上报事件的进入条件为:“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”。 当测量上报事件具体为事件A4时,测量上报事件的进入条件为:“Mn+Ofn+Ocn-Hys>Thresh”。 Mn是目标小区的测量结果,Ofn是目标小区的频率特定偏移,Ocn是目标小区的小区个体偏移。 如果目标小区没有配置小区个体偏移,当应用公式时,Ocn的值可以为0。Ms是服务小区的测量结果,Ofs是服务小区的频率特定偏移,Ocs是 服务小区的小区个体偏移,Hys为事件迟滞参数,Off为事件偏移参数,Thresh为事件阈值参数。 Ofn、Ocn、Hys、Ofs、Ocs、Off等参数由移动终端预先获取。 [0065] 具体地,在通信传输中,指示信息具体为至少一个数据。 至少一个数据包括测量报告事件的标识。 例如,若该至少一个数据中包含标识“A3”,则表明该指示信息对应的测量上报事件为事件A3。 或者,所述至少一个数据具体为特定标识。 特定标识可以位于测量配置信息中,与测量配置信息中关于测量上报事件的配置相关联。 例如,如果测量配置信息的部分内容是关于事件A3的配置,并且指定标识与测量配置信息中关于事件A3的配置相关联,则可以指示该指示对应的测量上报事件 信息是事件A3。 [0066] 在一实施例中,所述指示信息至少有一条,所述指示信息对应的测量上报事件至少有一个。 [0067] 在一个实施例中,该指示信息具体可以为直接重建指示、小区更新指示或前向切换指示。 [0068]本实施例中,指示信息用于当测量结果满足指示信息对应的测量上报事件的进入条件时,指示移动终端向目标小区对应的接入网元发起连接建立。 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 [0069] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图。 如图2所示,在图1所示实施例的基础上,对本实施例的实施方式进行描述,具体包括以下操作。 [0070] 小号 201 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0071] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0072] 小号 202 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0073] 该操作在 S 中具体描述 101 . 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0074] 小号 203 . 移动终端判断目标小区的测量结果是否满足该指示信息对应的测量上报事件的进入条件,如果满足,移动终端执行S 204 ,否则,本实施例结束。 [0075] 在一个实施例中,在本实施例中,所述指示信息至少有一条,所述指示信息对应的测量上报事件至少有一个。 [0076] 例如,如果移动终端在S中接收到两条指示信息 201 ,两条指示信息之一对应事件A3,另一条对应事件A4。 当在 S 中获得的测量结果 202 满足事件A3或事件A4中任一测量上报事件的进入条件,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行以下S 204 . [0077] 或者,若在S中获取到一条指示信息 201,指示信息对应事件A3和事件A4,当S中得到的测量结果为 202 满足A3事件或A4事件的进入条件,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行以下S 204 . [0078] 或者,若S中获取的指示信息 201 对应一个事件A3,当S中得到的测量结果 202 满足事件A3的进入条件,移动终端执行以下S 204 . 即当Mn满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,移动终端执行S 204 . 而当Mn满足“Mn+Ofn+Ocn-Hys>Thresh”但不满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,本实施例结束,即进入条件为 测量上报事件的条件,测量结果满足的不是该指示信息对应的测量上报事件的进入条件。 [0079] 还需要说明的是,如果该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,则测量结果满足该指示信息对应的测量上报事件的进入条件 ,移动终端可以直接执行S 205 确定后,通过执行 S 203 ,则目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 但是,为保证通信网络中网络侧设备对移动终端的控制效果不受影响,同时兼顾移动终端的移动性,本实施例中,优选的,所述指示信息为 用于如果测量结果满足指示信息对应的测量上报事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成测量上报的测量报告 指示信息对应的事件。 移动终端执行S 204 和小号 205 确定后依次执行S 203 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0080] 小号 204 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0081] 小号 205 . 移动终端向目标小区对应的接入网元发起连接建立。 [0082] S中的连接建立 205 具体包括: [0083] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理: [0084] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 [0085] 图3为本发明实施例二的RRC连接建立过程示意图。 如图3所示,具体流程包括以下操作: [0086] C 11 . 移动终端向目标小区对应的接入网元发送RRC连接建立请求。 [0087] C 12 . 移动终端接收目标小区对应的接入网元发送的RRC连接建立消息。 [0088] C 13 . 移动终端向目标小区对应的接入网元发送RRC连接建立完成消息。 [0089] 图4为本发明实施例二的RRC连接重建过程示意图。 如图4所示,具体过程包括以下操作: [0090] C21 . 移动终端向目标小区对应的接入网元发送RRC连接重建请求。 [0091] C 22 . 移动终端接收目标小区对应的接入网元发送的RRC连接重建消息。 [0092] C 23 . 移动终端向目标小区对应的接入网元发送RRC连接重建完成消息。 [0093] 图5为本发明实施例二的小区更新过程示意图。 如图5所示,具体过程包括以下操作: [0094] C 31 . 移动终端向目标小区对应的接入网元发送小区更新请求。 [0095] C 32 . 移动终端接收目标小区对应的接入网元发送的小区更新消息。 [0096] C 33 . 移动终端向目标小区对应的接入网元发送小区更新完成消息。 [0097] C 33 为可选操作,可以根据实际网络情况执行也可以不执行。 [0098] 图6为本发明实施例二的基于竞争的随机接入信道过程示意图。 如图6所示,具体过程包括以下操作: [0099] C 41 . 移动终端向目标小区对应的接入网元发送消息1。 消息1具体为“Random Access Preamble”。 [0100] C 42 . 移动终端接收目标小区对应的接入网元发送的消息2。 消息2具体为“Random Access Response”。 [0101] C 43 . 移动终端向目标小区对应的接入网元发送消息3。 消息3具体为“Scheduled Transmission”。 [0102] C 44 . 移动终端接收目标小区对应的接入网元发送的消息4。 消息4具体为“Contention Resolution”。 [0103] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图。 如图7所示,具体过程包括以下操作: [0104] C 51 . 移动终端接收目标小区对应的接入网元发送的消息0。 消息 0 具体是“RA Preamble assignment”。 [0105] C 52 . 移动终端向目标小区对应的接入网元发送消息1。 消息1具体为“Random Access Preamble”。 [0106] C 53 . 移动终端接收目标小区对应的接入网元发送的消息2。 消息2具体为“Random Access Response”。 [0107] 还应该注意的是,当确定时,通过执行 S 203 , 本实施例结束, 表示移动终端不再继续执行S 204 和小号 205 ,但继续按照现有技术进行其他操作。 例如,若指示信息对应的测量上报事件为事件A3,但移动终端在S中判断 203目标小区的测量结果不满足事件A3的进入条件,但满足事件A4的进入条件,则移动终端根据满足进入条件的测量结果生成事件A4的测量报告 事件A4; 向服务小区对应的接入网元发送事件A4的测量报告; 等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到服务小区对应的接入网元下发给移动终端的允许建立连接的指示时,移动终端才建立到目标小区的连接。 [0108] 即,现有技术中,当目标小区的测量结果满足测量上报事件的进入条件时,移动终端首先需要生成测量报告,并将测量报告上报给目标小区对应的接入网元。 服务小区,然后需要等待服务小区对应的接入网元下发允许建立连接的指示。 在此过程中,移动终端需要花费较长的时间周期,不利于提高移动终端与目标小区对应的接入网元建立连接的效率。 但是,在本说明书中,假设目标小区的测量结果满足指示信息对应的测量报告事件的进入条件,移动终端生成指示信息对应的测量报告事件的测量报告,则 移动终端能够在移动终端与目标小区之间建立连接,提高了移动终端与目标小区对应的接入网元建立连接的效率,提高了移动终端的移动性。 [0109] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立,并且移动终端生成 指示信息对应的测量上报事件的测量报告。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,以及 直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0110] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图。 如图8所示,在图1所示实施例的基础上,对本实施例的一个优选实施方式进行说明,具体包括以下操作。 [0111] 小号 301 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0112] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0113] 小号 302 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0114] 该操作在 S 中具体描述 101. 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0115] 小号 303 . 移动终端根据测量结果生成测量报告。 [0116] 小号 304 . 移动终端判断该测量报告是否为该指示信息对应的测量报告事件的测量报告,如果是,则移动终端执行S 305 ,否则,本实施例结束。 [0117] 在本实施例中,该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 前提是在 S 中获得的测量结果 302 满足测量报告事件的进入条件,在S中生成测量报告 303 . 可以理解,当S中的测量结果满足测量上报事件的进入条件时 302 不是指示信息对应的测量报告事件的进入条件,S中生成的测量报告 303 也不是该指示信息对应的测量上报事件的测量报告。 [0118] 然而,如果移动终端确定,通过执行S 304 , S 中的测量报告 303 为指示信息对应的测量报告事件的测量报告,即当移动终端根据指示信息确定移动终端生成指示信息对应的测量报告事件的测量报告时,移动终端 终端可以不向服务小区对应的接入网元发送该指示信息对应的测量报告事件的测量报告,直接执行S 305 . [0119] 在一个实施例中,在本实施例中,所述指示信息至少有一条,所述指示信息对应的测量上报事件至少有一个。 [0120] 例如,如果移动终端在S中接收到两条指示信息 301 , 两条指示信息之一对应事件A3, 另一条对应事件A4, 当S中得到的测量结果 302 满足事件A3或事件A4中任一测量报告事件的进入条件,S中生成的测量报告 303 必然是指示信息对应的测量上报事件的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0121] 或者,若在S中获取到一条指示信息 301 ,指示信息对应事件A3和事件A4,当S中得到的测量结果为 302 满足事件A3或事件A4的进入条件,S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0122] 或者,若S中获取的指示信息 301 对应一个事件A3,当S中得到的测量结果 302满足事件A3的进入条件,S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . 然而,在一个实施例中,如果在S中获得的指示信息 301 对应事件A3,但是S中得到的测量结果 302 满足事件A4的进入条件,S中生成的测量报告 303 不是指示信息对应的测量报告,而是事件A4的测量报告。 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 即当Mn满足“Mn+Ofn+Ocn−Hys>Thresh”但不满足“Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”时,S中生成的测量报告 303 不是指示信息对应的测量报告。 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 [0123] 小号 305 . 移动终端向目标小区对应的接入网元发起连接建立。 [0124] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理: [0125] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 具体可以参考图3至图7所示的信令流程。 [0126] 本实施例中,指示信息用于指示移动终端跳过,如果移动终端生成该指示信息对应的测量报告事件的测量报告,则向服务小区对应的接入网元发送该测量 上报指示信息对应的测量上报事件。 因此,移动终端可以直接向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0127] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图。 如图9A和图9B所示,本实施例在图1所示实施例的基础上进行进一步说明,具体包括以下操作。 [0128] 小号 401 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0129] 移动状态估计(Mobility State Estimation,MSE)是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0130] 小号 402 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0131] 小号 403 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0132]该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0133] 小号 404 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0134] 当服务小区对应的接入网元学习时,通过执行S 402 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 403 向移动终端下发指示信息。 [0135] 测量配置信息和指示信息可以同时下发,即S 403 和小号 404 通过使用相同的信令来实现。 在一个实施例中,S 404 可以在 S 之前执行 403 ,或者可以在 S 之前或同时执行 402 ,或者可以在 S 之前或同时执行 401 . 例如,首先,移动终端接收到测量配置信息,然后,当确定移动终端在高速移动时,服务小区对应的接入网元下发指示信息。 此外,在一个实施例中,S 401 和小号 402 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0136] 小号 405 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0137] 在移动终端接收到指示信息之前,移动终端根据S-Measure发现目标小区。 即移动终端只有在获知服务小区的服务质量低于预设值时才对邻区进行RRM测量,以发现测量结果满足测量上报事件的目标小区。 但在本实施例中,移动终端接收到指示信息后,可以忽略S-Measure,即移动终端可以随时对邻区进行RRM测量,无需等到服务 服务小区的质量低于预设值,从而及时判断目标小区的测量结果是否满足测量上报事件的进入条件,从而进一步提高移动终端的移动性 改善。 [0138] 小号 406 . 移动终端确定该测量结果满足该指示信息对应的测量上报事件的进入条件。 [0139] 可以理解的是,如果移动终端与目标小区建立连接,则移动终端在任意时刻确定目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 ,弱化了网络侧设备(如基站或基站控制器)对移动终端的控制。 但是,移动终端处于短周期DRX状态或长周期DRX状态时,对移动性的影响较大。 因此,在一个实施例中,当本实施例的移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示与目标小区建立连接,即 , 移动终端还需要执行以下S 407 执行 S 后 406 . [0140] 小号 407 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 409 或 408 ,或者如果否,则执行 S410 . [0141] DRX状态为短周期DRX状态或长周期DRX状态。 [0142] 现有技术中,移动终端处于休眠状态的时长也会影响移动终端的移动性。 另外,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端处于休眠状态的时间较长,对移动终端的移动性影响更为严重。 . 而本实施例中,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示及时建立到目标小区的连接,以及 移动终端的移动性不受移动终端的短周期DRX状态或长周期DRX状态的影响。 [0143] 小号 408 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 409 ,或者如果是,则执行 S 410 . [0144] 当移动终端位于服务小区和目标小区的临界区域时,如果移动终端的移动速度较低,则移动终端更容易发生目标小区和服务小区之间的“乒乓切换”。 为了避免发生乒乓切换的情况,优选地,S 408 需要执行。 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 409 . [0145] 另外,移动终端指定的速度门限和服务小区对应的接入网元指定的速度门限可以相同,也可以不同。 另外,移动终端指定的速度门限可以由服务小区对应的接入网元为移动终端配置,或者在通信协议中指定,例如,移动终端的速度门限为 高机动状态的速度。 [0146] 此外,S 407 和小号 408 为可选操作,即本实施例在实际应用中实现时,移动终端可以选择执行S 407 和/或 408 执行 S 后 406 , 以及执行 S 的序列 407 和小号 408 不受限制。 在这个实施例中,一个例子中 S 408 在 S 之后执行 407 使用确定移动终端处于DRX状态。 [0147] 小号 409 . 移动终端向目标小区对应的接入网元发起连接建立。 [0148]本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 因此,当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立。 目标细胞。 即,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的进入条件后,可以不生成该指示信息对应的测量上报事件的测量报告,不发送 , 向服务小区对应的接入网元, 指示信息对应的测量报告事件的测量报告, 向目标小区对应的接入网元发起连接建立, 使得移动终端可以发起, 在 及时与目标小区对应的接入网元建立连接,提高移动终端的移动性。 [0149] 小号 410 . 移动终端生成指示信息对应的测量报告事件的测量报告,并向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 [0150] 在本实施例中,即使移动终端接收到指示信息,并且目标小区的测量结果满足该指示信息对应的测量报告事件的进入条件,移动终端也可以根据S中的判断结果进行选择。 407 和/或 408 ,应用指示信息(即,执行S 409 ). 或者,移动终端根据S中的判断结果进行选择 407 和/或 408 , 不应用指示信息; 仍然按照现有技术与目标小区对应的接入网元建立连接,即执行S 410 ; 然后,等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0151] 本实施例中,移动终端根据目标小区的测量结果确定该测量结果满足指示信息对应的测量上报事件的进入条件后,根据该指示信息的指示,移动终端可以跳过生成 指示信息对应的测量上报事件的测量报告, 并跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告, 使得移动终端可以直接 向目标小区对应的接入网元发起连接建立,提高移动终端的移动性。 [0152] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图。 如图10A和图10B所示,在图1或图2所示实施例的基础上,在一个优选的实施方式中,本实施例具体包括以下操作。 [0153] 小号 501 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0154]移动状态估计是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0155] 小号 502 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0156] 小号 503 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0157] 该指示信息用于当测量结果满足该指示信息对应的测量报告事件的进入条件并生成测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0158] 小号 504 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0159] 当服务小区对应的接入网元学习时,通过执行S 502 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 503 向移动终端下发指示信息。 [0160] 测量配置信息和指示信息可以同时下发,即S 503 和小号 504 通过使用相同的信令来实现。 在一个实施例中,S 504 可以在 S 之前执行 503 ,或者可以在 S 之前或同时执行 502 ,或者可以在 S 之前或同时执行 501 . 例如,首先,移动终端接收到测量配置信息,然后,接入网元在确定移动终端高速移动时,下发指示信息。 此外,在一个实施例中,S 501 和小号 502 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0161] 小号 505 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0162] 小号 506 . 移动终端判断测量结果是否满足指示信息对应的测量上报事件的进入条件,如果满足,则执行S 507 ,或者如果否,则执行 S 511 . [0163] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件且移动终端向目标小区对应的接入网元发起连接建立时。 生成指示信息对应的测量报告事件的测量报告。 因此,本实施例中的移动终端通过执行S来确定 506 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0164]在一个实施例中,若测量结果既不满足指示信息对应的测量上报事件的进入条件,也不满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件, 本实施例结束,即移动终端不再进行以下操作。 [0165] 但是,若测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件, 在该实施例中,根据现有技术,S 511 执行和小号 512 随后执行。 图9以测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件为例 指示信息。 [0166] 小号 507 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0167] 小号 508 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 510 或 509 ,或者如果否,则执行 S 512 . [0168] DRX状态为短周期DRX状态或长周期DRX状态。 [0169] 小号 509 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 510 ,或者如果是,则执行 S 512 . [0170] 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 510 . [0171] 小号 508 和小号 509 为可选操作,即本实施例在实际应用中实现时,移动终端可以选择执行S 508 和/或 509 执行 S 后 507 , 以及执行 S 的序列 508 和小号 509 不受限制。 本实施例以移动终端继续执行S为例 509 执行 S 后 508 使用确定移动终端处于DRX状态。 [0172] 小号 510 . 移动终端向目标小区对应的接入网元发起连接建立。 [0173] 在一个实施例中,移动终端向目标小区对应的接入网元发起连接建立后,移动终端与服务小区对应的接入网元保持连接。 [0174] 小号 511 . 移动终端根据满足测量报告事件的进入条件的测量结果生成测量报告,该测量报告事件不同于指示信息对应的测量报告事件的进入条件。 [0175] 小号 512 . 移动终端将测量报告发送给服务小区对应的接入网元。 [0176] 如果 S 之前的操作 512 是小号 508 或 509 ,移动终端发送的测量报告为指示信息对应的测量报告事件的测量报告。 如果 S 之前的操作 512 是小号 511 ,移动终端发送的测量报告是移动终端根据测量报告事件的满足进入条件的测量结果生成的测量报告,不同于指示信息对应的测量报告事件的进入条件 . [0177] 当 S 之前的操作 512 是小号 508或 509 ,表示即使移动终端接收到指示信息,目标小区的测量结果也满足该指示信息对应的测量上报事件的进入条件,移动终端生成对应的测量上报事件的测量报告 对于指示信息,移动终端根据S中的判断结果进行选择 508 和/或 509 ,以应用指示信息(即,执行 S 510 ). 或者,移动终端根据S中的判断结果进行选择 508 和/或 509 , 不应用指示信息; 仍然按照现有技术建立到目标小区的连接,即执行S 512 将测量报告发送给服务小区对应的接入网元; 然后,等待接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0178] 可以理解的是,现有技术中的通信过程中已经包含了关于测量报告生成的协议、配置等。 因此,在基于现有协议或配置应用本实施例时,需要调整和修改的内容较少,范围较小,有利于本实施例的实施。 [0179] 本实施例中,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.157 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), CN105659666A(String), 1047479(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), EP3193534A1(String), 1047480(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), EP3193534A4(String), 1047481(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.161 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), US10142904B2(String), 1047482(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.162 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), US10499298B2(String), 1047483(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.163 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), US10805853B2(String), 1047484(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), US20170251417A1(String), 1047485(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.165 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), US20190075502A1(String), 1047486(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), US20200068471A1(String), 1047487(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270699(Integer), WO2016049931A1(String), 1047488(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.170 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10499298B2(String), US10499298B2(String), 1575302400(Integer), 270699(Integer), 185022(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.173 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.174 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.175 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.175 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185023(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185023(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.185 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.185 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.185 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.187 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185023(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185023(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.202 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.227 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185023(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20220368007A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and mobile terminal antenna production method(String), 移动终端及移动终端天线的制作方法(String), US20220368007A1(String), A mobile terminal and a mobile terminal antenna production method. The mobile terminal uses an insulation film layer on an insulation rear housing as a carrier of a radiating element of an antenna, and the radiating element is located within the entire mobile terminal. A feed and an electric-conductor are disposed on a circuit board, and the electric-conductor is electrically connected to the feed. There is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 一种移动终端及移动终端天线的制作方法。 该移动终端采用绝缘后壳上的绝缘膜层作为天线辐射元件的载体,辐射元件位于整个移动终端内。 电路板上设有馈线及导电体,导电体电性连接馈线。 辐射元件与导电体之间存在间隙,导电体以电容耦合的方式间接耦合辐射元件。(String), US17/874597(String), 1658851200(Integer), US20220368007A1(String), 1668614400(Integer), 美国(String), 2(Integer), CN(String), 7(Integer), 9(Integer), CN108242592A | US11011850B2 | US11450946B2 | US20130101149A1 | US20150207208A1 | US20180332741A1 | US20190207318A1 | US20200321688A1 | WO2011051408A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185024(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.263 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.264 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d0feb1c04c64496b81e898bece07c835.png(String), 185024(Integer), d0feb1c04c64496b81e898bece07c835.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and mobile terminal antenna production method(String), 移动终端及移动终端天线的制作方法(String), US20220368007A1(String), A mobile terminal and a mobile terminal antenna production method. The mobile terminal uses an insulation film layer on an insulation rear housing as a carrier of a radiating element of an antenna, and the radiating element is located within the entire mobile terminal. A feed and an electric-conductor are disposed on a circuit board, and the electric-conductor is electrically connected to the feed. There is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 一种移动终端及移动终端天线的制作方法。 该移动终端采用绝缘后壳上的绝缘膜层作为天线辐射元件的载体,辐射元件位于整个移动终端内。 电路板上设有馈线及导电体,导电体电性连接馈线。 辐射元件与导电体之间存在间隙,导电体以电容耦合的方式间接耦合辐射元件。(String), US17/874597(String), 1658851200(Integer), US20220368007A1(String), 1668614400(Integer), 美国(String), 1(Integer), 2(Integer), CN(String), 7(Integer), 9(Integer), CN108242592A | US11011850B2 | US11450946B2 | US20130101149A1 | US20150207208A1 | US20180332741A1 | US20190207318A1 | US20200321688A1 | WO2011051408A1(String), \20230420\d0feb1c04c64496b81e898bece07c835.png(String), 20(Integer), 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.287 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 1. A mobile terminal, comprising:a mobile terminal body comprising a circuit board;an insulation rear housing that covers the mobile terminal body, the insulation rear housing comprising an inner side facing the mobile terminal body, wherein an insulation film layer covers the inner side of the insulation rear housing; andan antenna, comprising:a feed disposed on the circuit board;an electric-conductor disposed on the circuit board, wherein the electric-conductor is electrically connected to the feed; anda radiating element disposed on the insulation film layer, wherein there is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 1.移动终端,包括:一种移动终端本体,包括电路板;绝缘后壳覆盖移动终端本体,绝缘后壳包括面向移动终端本体的内侧,绝缘膜层覆盖绝缘后壳的内侧;和天线,包括:馈线设置于电路板上;一导电体,设置于电路板上,其中导电体电性连接至馈线。和辐射元件设置于绝缘膜层上,辐射元件与导电体之间具有间隙,导电体以电容耦合的方式间接耦合辐射元件。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 2. The mobile terminal according to claim 1, wherein the insulation rear housing is a glass rear housing.(String), 2.根据权利要求1所述的移动终端,其中绝缘后壳为玻璃后壳。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 3. The mobile terminal according to claim 1, wherein the radiating element comprises silver, aluminum, or copper.(String), 3.根据权利要求1所述的移动终端,其中辐射元件包括银、铝或铜。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 4. The mobile terminal according to claim 1, wherein a thickness of the radiating element is between 1 μm and 200 μm.(String), 4.根据权利要求1所述的移动终端,其中辐射元件的厚度介于1μm至200μm之间。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 5. The mobile terminal according to claim 4, wherein an impedance of the radiating element is less than 3 ohms.(String), 5.根据权利要求4所述的移动终端,其中辐射元件的阻抗小于3欧姆。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 6. The mobile terminal according to claim 1, wherein a square resistance of the radiating element is less than 1 ohm/□.(String), 6.根据权利要求1所述的移动终端,其中辐射元件的方块电阻小于1欧姆/□。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 7. The mobile terminal according to claim 1, wherein the insulation film layer is at least one of the following:an ink film layer, a decorative film layer, or an explosion-proof film layer.(String), 7.根据权利要求1所述的移动终端,其中绝缘膜层至少为以下之一:油墨膜层、装饰膜层或防爆膜层。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 8. The mobile terminal according to claim 1, wherein the mobile terminal body further comprises a support disposed on the circuit board, wherein the support is insulated and the electric-conductor is disposed on the support.(String), 8.根据权利要求1所述的移动终端,其中移动终端本体还包括设置在电路板上的支架,支架绝缘,导电体设置在支架上。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 9. The mobile terminal according to claim 1, wherein the antenna further comprises a ground disposed on the circuit board, the electric-conductor is electrically connected to the ground.(String), 9.根据权利要求1所述的移动终端,其中天线还包括一地线,设置于电路板上,导电体电性连接于地线。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 10. The mobile terminal according to claim 9, wherein,one end of the electric-conductor is electrically connected to the feed, and the other end of the electric-conductor is connected to the radiating element in a coupled manner; orone end of the electric-conductor is electrically connected to the ground, and the other end of the electric-conductor is connected to the radiating element in a coupled manner; orone end of the electric-conductor is electrically connected to the feed, the other end of the electric-conductor is electrically connected to the ground.(String), 10.根据权利要求9所述的移动终端,其中,导电体的一端与馈线电连接,另一端与辐射元件耦合连接。或者导电体的一端与地电性连接,另一端与辐射元件耦合连接。或者导电体的一端与馈线电连接,另一端与地电连接。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 11. The mobile terminal according to claim 1, wherein the electric-conductor is a metal spring plate.(String), 11.根据权利要求1所述的移动终端,其中导电体为金属弹片。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 12. The mobile terminal according to claim 11, wherein the metal spring plate is an inverted L-shaped metal spring plate or an inverted U-shaped metal spring plate.(String), 12.根据权利要求11所述的移动终端,其中金属弹片为倒L型金属弹片或倒U型金属弹片。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 13. The mobile terminal according to claim 1, wherein the insulation rear housing comprises a flat plate and a bent side wall, and an arc-shaped transition is used at a joint between the bent side wall and the flat plate.(String), 13.根据权利要求1所述的移动终端,其中绝缘后壳包括平板和折弯侧壁,折弯侧壁与平板的连接处采用弧形过渡。(String), 1(Integer), 12(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 14. The mobile terminal according to claim 13, wherein the radiating element is disposed on the flat plate of the insulation rear housing.(String), 14.根据权利要求13所述的移动终端,其中散热元件设置于绝缘后壳的平板上。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 15. The mobile terminal according to claim 13, wherein the radiating element is disposed with a certain distance from the edge of the insulation film layer.(String), 15.根据权利要求13所述的移动终端,其中辐射元件设置在距离绝缘膜层边缘一定距离处。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 16. The mobile terminal according to claim 13, wherein the radiating element is disposed on the bent side wall of the insulation rear housing.(String), 16.根据权利要求13所述的移动终端,其中散热元件设置于绝缘后壳的弯折侧壁上。17、一种移动终端天线制作方法包括:在绝缘膜层上设置辐射元件;将绝缘膜层设置于绝缘后壳的内侧;在移动终端本体中的电路板上制作馈电;和将导电体电性连接至馈源,其中辐射元件与导电体之间具有间隙,且导电体以电容耦合的方式间接耦合辐射元件。(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 17. A mobile terminal antenna production method comprising:disposing a radiating element on an insulation film layer;disposing the insulation film layer to an inner side of an insulation rear housing;producing a feed on a circuit board in a mobile terminal body; andelectrically connecting an electric-conductor to the feed, wherein there is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 18.根据权利要求17所述的移动终端的制作方法,其中辐射元件的厚度在1μm~200μm之间,f辐射元件的阻抗小于3欧姆或者辐射元件的方块电阻小于1欧姆/□。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 18. The mobile terminal production method according to claim 17, wherein a thickness of the radiating element is between 1 μm and 200 μm, and an impedance of the f radiating element is less than 3 ohms or a square resistance of the radiating element is less than 1 ohm/□.(String), 19.根据权利要求17所述的移动终端的制作方法,还包括:在电路板上设置一支架,其中支架绝缘。和将导电体设置于支架上。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 19. The mobile terminal production method according to claim 17, further comprising:disposing a support on the circuit board, wherein the support is insulated; anddisposing the electric-conductor on the support.(String), 20.根据权利要求17所述的移动终端的制作方法,其中绝缘后壳包括平板和折弯侧壁,折弯侧壁与平板的连接处采用弧形过渡,散热元件设置在绝缘边缘一定距离处膜层。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.290 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.290 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185024(Integer), 20. The mobile terminal production method according to claim 17, wherein the insulation rear housing comprises a flat plate and a bent side wall, an arc-shaped transition is used at a joint between the bent side wall and the flat plate, and the radiating element is disposed with a certain distance from the edge of the insulation film layer.(String), 1(Integer), 19(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185024(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 16/954,591, filed on Jun. 17, 2020, which is a national stage of International Application No. PCT/CN2019/098310, filed on Jul. 30, 2019, which claims priority to Chinese Patent Application No. 201810858567.0, filed on Jul. 31, 2018. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The embodiments relate to the field of antenna technologies, and a mobile terminal, and a mobile terminal antenna production method. BACKGROUND [0003]Currently, functions of smart phones are increasing each passing day, and the smart phones need to cover an increasingly wide communication range. A mobile phone apparatus also has increasing requirements for both an antenna and an antenna quantity. How to place more antennas in limited space is one of urgent problems to be resolved in the antenna structure field. Currently, common antenna designs all use a support, such as a laser direct structuring (LDS) technology or a metal bezel of a mobile phone as an antenna radiator. An antenna may be an IFA, a monopole antenna, or a loop antenna. However, with increasing requirements of various components and functions on a mobile phone end, the foregoing conventional method is limited in future application, and a clearance area required during antenna radiation is reduced accordingly. In addition, an LDS antenna structured on support plastic is usually placed inside a mobile phone body and is more liable to be affected by peripheral parts and components. Besides, because the antenna is comparatively short, the antenna is liable to be limited in space freedom or in efficiency and a bandwidth. SUMMARY [0004]The embodiments provide a mobile terminal and a mobile terminal antenna production method, so as to improve communication performance of the mobile terminal. [0005]According to a first aspect, a mobile terminal is provided. The mobile terminal includes a mobile terminal body and an insulation rear housing that covers the mobile terminal body. An insulation film layer covers an inner side of the insulation rear housing. The inner side of the insulation rear housing is a surface facing the mobile terminal body when the insulation rear housing covers the mobile terminal body. In addition, the mobile terminal further includes an antenna. The antenna includes a feed and a radiating element electrically connected to the feed. The feed is disposed on a circuit board in the mobile terminal body, and the radiating element is printed on the insulation film layer. It can be understood from the foregoing description that the insulation film layer on the insulation rear housing serves as a carrier of the radiating element of the antenna, and the radiating element is located within the entire mobile terminal, thereby effectively increasing a height of the radiating element of the antenna relative to the circuit board with the antenna not affecting an appearance of the mobile terminal (compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm). This reduces an impact caused by a metal component on the circuit board on antenna radiation, and further increases a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. [0006]When being disposed, the radiating antenna uses a metallic wire. The metallic wire may be a straight metallic wire, a curved metallic wire, or a spiral metallic wire, and a shape is not limited. The metallic wire may be prepared using different materials such as aluminum, copper, and silver. In an embodiment, the metallic wire is a silver wire. [0007]For a disposing position of the radiating antenna, the radiating antenna may be disposed in any position on the inner side of the insulation rear housing as needed, for example, a position on a side wall. [0008]To improve a radiation effect of the antenna, when the metallic wire is disposed, a thickness of the metallic wire is between 1 μm and 200 μm, and an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□. [0009]The insulation rear housing may be prepared using different materials, provided that insulation can be ensured. For example, the insulation rear housing is a glass rear housing or plastic rear housing. [0010]For the insulation film layer, film layers with different functions may be used. For example, the insulation film layer is an ink film layer, a decorative film layer, or an anti-explosion film layer. [0011]For the antenna, antennas of different types may be used. For example, the antenna is one or more of a GPS antenna, a Wi-Fi antenna, an NFC antenna, a millimeter-wave antenna, a diversity antenna, or a main antenna. [0012]When the feed and the radiating element are connected electrically, the antenna further includes an electric-conductor. The electric-conductor is electrically connected to the feed and/or a ground, and the electric-conductor is connected to the radiating element in a coupled manner. In other words, an electrical connection between the electric-conductor and the radiating element is implemented in a coupled manner. Compared with a manner, in a general conventional solution, in which a signal line of the circuit board is directly connected to the antenna, feeding in a coupled manner can avoid problems caused by direct electrical-connection feeding, such as uneven contact pressure and a problem that impedance of a contact point becomes unstable after a long period of time due to factors such as oxidation. [0013]When the electric-conductor is disposed, different solutions may be used. For example, in a solution, the mobile terminal further includes a circuit board that is disposed in the mobile terminal body, and the feed and the ground are disposed on the circuit board; and a support is disposed on the circuit board, and the electric-conductor is a metallic wire disposed on the support, where one end of the metallic wire is electrically connected to the feed, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the ground, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the feed, the other end of the metallic wire is electrically connected to the ground, and the metallic wire is connected to the radiating element in a coupled manner. In other words, the metallic wire is directly disposed on the support to implement a coupling connection. [0014]In another solution, the mobile terminal further includes a circuit board that is disposed in the mobile terminal body, and the feed and the ground are disposed on the circuit board; and the electric-conductor is a metal spring plate, where one end of the metal spring plate is electrically connected to the feed, and the other end of the metal spring plate is connected to the radiating element in a coupled manner; or one end of the metal spring plate is electrically connected to the ground, and the other end of the metal spring plate is connected to the radiating element in a coupled manner; or one end of the metal spring plate is electrically connected to the feed, the other end of the metal spring plate is electrically connected to the ground, and the metal spring plate is connected to the radiating element in a coupled manner. [0015]When the metal spring plate is used, the metal spring plate may be in different shapes. For example, the metal spring plate is an inverted L-shaped metal spring plate or an inverted U-shaped metal spring plate. [0016]According to a second aspect, a mobile terminal antenna production method is provided. The production method includes the following steps. [0017]Print a radiating element on an insulation film layer. For example, spray silver paste on the film layer, and then bake the silver paste and the insulation film layer at 50 degrees to 200 degrees for 30 minutes to 60 minutes, to form a metallic wire. [0018]Stick the insulation film layer to an inner side of an insulation rear housing. [0019]The insulation film layer on the insulation rear housing serves as a carrier of the radiating element of an antenna, and the radiating element is located within an entire mobile terminal, thereby effectively increasing a height of the radiating element of the antenna relative to a circuit board with the antenna not affecting an appearance of the mobile terminal (compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm). This reduces an impact caused by a metal component on the circuit board on antenna radiation, and further increases a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. [0020]The used silver paste includes 50-99 wt % silver powder, and viscosity of the silver paste is 10-20000 cps. [0021]After the metallic wire is formed, a thickness of the metallic wire is between 1 μm and 200 μm, and an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□, to ensure that the antenna can have good communication performance. [0022]The production method further includes: producing a feed and a ground on the circuit board and connecting an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner. [0023]When the electric-conductor is in different structural forms, different production manners may be used. For example, the connecting an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner, is: disposing a support on the circuit board, and printing a metallic wire on the support, where one end of the metallic wire is electrically connected to the feed, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the ground, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the feed, the other end of the metallic wire is electrically connected to the ground, and the metallic wire is connected to the radiating element in a coupled manner. [0024]When the electric-conductor is a metal spring plate, the connecting an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner, is: connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the ground electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the ground electrically, where the metal spring plate and the radiating element are connected in a coupled manner. In other words, the electric-conductor may be formed in different structural forms. BRIEF DESCRIPTION OF THE DRAWINGS [0025]FIG. 1 is a schematic structural diagram of a mobile terminal according to an embodiment; [0026]FIG. 2 is a sectional view at A-A in FIG. 1; [0027]FIG. 3 is a schematic structural diagram of another mobile terminal according to an embodiment; [0028]FIG. 4 is a schematic structural diagram of another mobile terminal according to an embodiment; [0029]FIG. 5 is a schematic structural diagram of an antenna according to an embodiment n; [0030]FIG. 6 is a schematic structural diagram of another antenna according to an embodiment; [0031]FIG. 7 is a schematic structural diagram of another antenna according to an embodiment; [0032]FIG. 8 is a schematic structural diagram of another antenna according to an embodiment; and [0033]FIG. 9 is a flowchart of producing a mobile terminal antenna according to an embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS [0034]To make the objectives, solutions, and advantages of the embodiments clearer, the following further describes the embodiments in detail with reference to the accompanying drawings. [0035]An embodiment provides a mobile terminal. The mobile terminal includes a mobile terminal body and an insulation rear housing 10 that covers the mobile terminal body. The insulation rear housing 10 is a phone housing of the mobile terminal. FIG. 1 and FIG. 2 show a structure of the insulation rear housing 10. First, as shown in FIG. 1 and FIG. 2, the insulation rear housing 10 is a rectangular structure and includes a flat plate and four bent side walls. During bending, as shown in FIG. 2, where FIG. 2 shows a sectional view at A-A in FIG. 1, a connection manner between the side wall and the flat plate is clearly shown in FIG. 2, where an arc-shaped transition is used at a joint between the bent side wall and the flat plate. In addition, during production, the insulation rear housing 10 is formed in an integrated structuring manner. However, the structure of the insulation rear housing 10 is not limited to the structure shown in FIG. 1 and FIG. 2, and a structure shown in FIG. 4 may be alternatively used. When the structure shown in FIG. 4 is used, the insulation rear housing 10 is an arc-shaped rear housing. However, the structure of the insulation rear housing 10 may alternatively be in another structural form. For ease of description, an inner side of the insulation rear housing 10 is defined. The inner side of the insulation rear housing 10 in this embodiment is a concave side of the insulation rear housing 10. When the insulation rear housing 10 is mounted on the mobile terminal body, the inner side faces the mobile terminal body. [0036]Different materials such as glass and plastic may be selected for the insulation rear housing 10 provided in this embodiment, provided that insulation can be implemented. For example, when a glass material is used, the insulation rear housing 10 is a glass rear housing 10. [0037]Still referring to FIG. 1, an insulation film layer 20 covers the inner side of the insulation rear housing 10. As a bearing structure, the insulation film layer 20 is configured to bear a radiating element 30 of an antenna. For the insulation film layer 20, film layers with different functions may be used. For example, the insulation film layer 20 is an ink film layer, a decorative film layer, or an anti-explosion film layer. A material used by the insulation film layer 20 may be plastic. When the insulation film layer 20 covers the inner side of the insulation rear housing 10, the insulation film layer 20 is adhered to the inner side of the insulation rear housing 10 by an adhesive or fixed to the inner side of the insulation rear housing 10 through vacuum adsorption. [0038]Still referring to FIG. 1 and FIG. 2, the mobile terminal provided in this embodiment further includes an antenna. For the antenna, antennas of different types may be used. For example, the antenna is one or more of a GPS antenna, a Wi-Fi antenna, an NFC antenna, a millimeter-wave antenna, a diversity antenna, or a main antenna. It can be understood that the antenna provided includes one or more of antennas of the foregoing several types but is not limited to the antennas of the foregoing listed types, and regardless of an antenna that is used, the antenna provided in this embodiment includes the following two structures: a feed and the radiating element 30. The feed is electrically connected to the radiating element 30. When the feed is disposed, the feed is disposed on a circuit board in the mobile terminal body. The circuit board may be a PCB board. To improve performance of the antenna, when the radiating element 30 is disposed, as shown in FIG. 1 and FIG. 2, the radiating element 30 is printed on the insulation film layer 20. The radiating element 30 uses a metallic wire and may be in different shapes. As shown in FIG. 1 and FIG. 2, the metallic wire may be a straight metallic wire, or may be in another structure, for example, a curved metallic wire, or a spiral metallic wire shown in FIG. 3. It can be understood from FIG. 1 and FIG. 3 that a shape of the radiating element 30 is not limited, and a different choice may be made as needed. In addition, for a disposing position of the radiating element 30, the radiating element 30 may be disposed in any position on the insulation film layer 20. It can be understood from FIG. 1 and FIG. 2 that there is not another structure on the insulation film layer 20. Therefore, a different position may be selected as needed for disposing the radiating element 30. As shown in FIG. 1 and FIG. 2, the radiating element 30 is disposed on the side wall of the insulation rear housing 10; and, as shown in FIG. 3, the radiating element 30 is disposed on the flat plate of the insulation rear housing 10. In addition, a quantity of radiating elements 30 is not limited. For example, there is one radiating element 30 shown in FIG. 1, and there are two radiating elements 30 shown in FIG. 4. In addition, the metallic wire may be prepared using different materials, such as aluminum, copper, and silver. In an embodiment, the metallic wire is a silver wire, which has good electrical conductivity. [0039]When the radiating element 30 is produced, the radiating element 30 is structured on the insulation film layer 20 by using a metal printing process. In this embodiment, the metallic wire is prepared using silver paste. Therefore, the following uses the silver paste as an example for description. First, a component of the silver paste used includes 50-99 wt % (mass percentage) silver powder, and viscosity of the formed silver paste is 10-20000 cps (mPa·s), to ensure that the silver paste can be stably adhered to the insulation film layer 20. During printing, first, the silver paste is sprayed or printed on the insulation film layer 20 (a decorative film layer, an anti-explosion film layer, or an ink film layer may be selected), and then, the silver paste and the insulation film layer 20 are baked at 50 degrees to 200 degrees for 30 min to 60 min (minutes), to increase adhesion on the insulation film layer 20. Then, the silver paste is formed to a thickness of 1 μm to 200 μm (micrometers). Further, it is ensured that an impedance of the prepared silver paste is less than 3 ohms (including 1 ohm) (a definition for testing: a value, expressed in ohms, measured between any two points on the antenna). In other words, a thickness of a printed metallic wire is between 1 μm and 200 μm, for example, 3 μm, 5 μm, 10 μm, 15 μm, or 20 μm. In addition, an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□, where the square resistance is defined as follows. When a length is represented by l, a width is represented by w, and a height is represented by d (that is, a thickness of the film), L (length)=l, and S (cross-sectional area)=w*d; and therefore, R=ρ*l/(w*d)=(ρ/d)*(l/w). Let l=w, and then, R=(ρ/d), where ρ is resistivity of a material. In this case, R is the square resistance and is expressed in ohm/□, where “□” indicates that a cross section of the metallic wire is a square. [0040]During disposing, two different manners may be used. One manner is: first printing the radiating element 30 on the insulation film layer 20 and then sticking the insulation film layer 20 into the insulation rear housing 10. The other manner is: first sticking the insulation film layer 20 into the insulation rear housing 10 and then printing the radiating element 30 on the insulation film layer 20. As shown in FIG. 2 and FIG. 4, when a position corresponding to the radiating element 30 is arc-shaped, the manner of first printing the radiating element 30 on the insulation film layer 20 greatly facilitates disposing of the radiating element 30. [0041]It can be understood from the foregoing description that the insulation film layer 20 on the inner side of the insulation rear housing 10 is configured to support the radiating element 30 of the antenna, so that the radiating element 30 is located within the entire mobile terminal, thereby effectively increasing a height of the radiating element 30 of the antenna relative to the circuit board with the antenna not affecting an appearance of the mobile terminal. Compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm, thereby reducing an impact caused by a metal component on the circuit board on antenna radiation, and further increasing a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. [0042]When the antenna is disposed, the antenna not only includes the radiating element 30, but also includes the feed and a ground, and the feed and the ground are electrically connected to the radiating element 30. To implement electrical connections of the feed and the ground to the radiating element 30, an electric-conductor is further disposed in the antenna provided in this embodiment. The electric-conductor is electrically connected to the feed and/or the ground, and the electric-conductor is connected to the radiating element 30 in a coupled manner. It should be understood that a coupling connection is an indirect coupling connection, that is, there is a gap between the radiating element 30 and the electric-conductor, and an electrical connection is implemented in a capacitively coupled manner. When the electric-conductor is disposed, the electric-conductor may be in different structural forms. The following describes implementations of two electric-conductors with reference to FIG. 5 and FIG. 7. [0043]As shown in FIG. 5, a feed is disposed on a circuit board 60 in a mobile terminal body, and a support 50 is further disposed on the circuit board 60. The support 50 is used as a support carrier to support an electric-conductor. In the structure shown in FIG. 5, the electric-conductor is a metallic wire 40. The metallic wire 40 is fixed on the support in a printing or flexible-plate sticking manner. In addition, a quantity of electric-conductors is in a one-to-one correspondence with a quantity of radiating elements 30. When two radiating elements 30 are used in FIG. 5, there are two corresponding electric-conductors, and there are also two corresponding supports 50. The support 50 may be in different structural forms. For example, in FIG. 5, the support 50 is a support block, and the support block is fixed on the circuit board 60 in a sticking manner. It can be understood that as a carrier, the support 50 should be insulated, to avoid affecting power feeding of the electric-conductor. FIG. 5 is a schematic diagram of an electrical connection between the metallic wire 40 and the feed. As shown in FIG. 6, a placement direction of a mobile terminal shown in FIG. 6 is used as a reference direction. A metallic wire 40 located on the right side is electrically connected to the ground, and two ends of a metallic wire 40 located on the left side are electrically connected to the ground and the feed separately. When the metallic wires 40 are electrically connected to the ground, a disposing manner of the metallic wires 40 is similar to that in FIG. 5, and an only difference lies in that one metallic wire 40 is connected to the feed on the circuit board 60, and the other metallic wire 40 is connected to the ground on the circuit board 60. When the two ends of the metallic wire 40 are separately connected to the feed and the ground, one end of the metallic wire 40 is connected to a feed point, and the other end of the metallic wire 40 is connected to the ground. The metallic wire 40 is connected to the radiating element 30 in a coupled manner. A coupling portion is a portion between the two ends. [0044]FIG. 7 shows a structure of another electric-conductor. In FIG. 7, the electric-conductor is a metal spring plate 70. One end of the metal spring plate 70 is fixed (electrically connected) to the feed, and the other end of the metal spring plate 70 is a free end. The free end of the metal spring plate 70 is connected to the radiating element 30 in a coupled manner. During disposing, as shown in FIG. 7, the metal spring plate 70 is an inverted L-shaped metal spring plate 70. However, a structural form of the metal spring plate 70 is not limited to the one specified in FIG. 7. The metal spring plate 70 may alternatively be an arc-shaped metal sheet, or a wavy metal spring plate 70, and both may be applied to the embodiments. For a material of the metal spring plate 70, the material may have good electrical conductivity and strength, such as copper, aluminum, or iron. As shown in FIG. 8, a placement direction of a mobile terminal shown in FIG. 8 is used as a reference direction. A metal spring plate 70 located on the right side is electrically connected to the ground, and two ends of a metal spring plate 70 located on the left side are electrically connected to the ground and the feed separately. When the metal spring plate 70 is electrically connected to the ground, a disposing manner of the metal spring plate 70 is similar to that in FIG. 7, and an only difference lies in that one metal spring plate 70 is connected to the feed on the circuit board 60, and the other metal spring plate 70 is connected to the ground on the circuit board 60. When the two ends of the metal spring plate 70 are separately connected to the feed and the ground, one end of the metal spring plate 70 is connected to a feed point, and the other end of the metal spring plate 70 is connected to the ground. The metal spring plate 70 is connected to the radiating element 30 in a coupled manner. A coupling portion is a portion between the two ends. In this case, the metal spring plate 70 is an inverted U-shaped structure. [0045]It can be understood from FIG. 5 to FIG. 8 that in the antenna, the electrical connection between the electric-conductor and the radiating element and an electrical connection between the electric-conductor and the ground are implemented in a coupled manner. Compared with a manner, in a general conventional solution, in which a signal line of the circuit board 60 is directly connected to the antenna, feeding in a coupled manner can avoid problems caused by direct electrical-connection feeding, such as uneven contact pressure and a problem that impedance of a contact point becomes unstable after a long period of time due to factors such as oxidation. [0046]In addition, the embodiments further provide an antenna production method. The method includes: printing a radiating element 30 on an insulation film layer 20 and sticking the insulation film layer 20 to an inner side of an insulation rear housing 10. The method includes two different manners: first printing a radiating element 30 on an insulation film layer 20, and then sticking the insulation film layer 20 into an insulation rear housing 10; or first sticking an insulation film layer 20 into an insulation rear housing 10, and then printing a radiating element 30 on the insulation film layer 20. As shown in FIG. 2 and FIG. 4, it can be understood from FIG. 1 and FIG. 4 that when a position corresponding to the radiating element 30 is arc-shaped, the manner of first printing the radiating element 30 on the insulation film layer 20 greatly facilitates disposing of the radiating element 30. [0047]The following describes the method in detail with reference to FIG. 9. [0048]Step 01: Spray silver paste on the insulation film layer 20. [0049]For example, a material of the used silver paste includes 50-99 wt % (mass percentage) silver powder, and viscosity of the silver paste is 10-20000 cps (mPa·s), so that the silver paste can be firmly adhered to the insulation film layer 20. [0050]Step 02: Bake the silver paste and the insulation film layer at 50 degrees to 200 degrees for 30 min to 60 min (minutes), to form a metallic wire. [0051]When the metallic wire is formed, a thickness of the metallic wire is between 1 μm and 200 μm (micrometers), for example, 3 μm, 5 μm, 10 μm, 15 μm, or 20 μm. In addition, an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□, to ensure that an antenna can have good communication performance. [0052]Step 03: Stick the insulation film layer 20 to an inner side of the insulation rear housing 10. [0053]For example, the insulation film layer 20 on which the metallic wire is printed is stuck into the insulation rear housing 10 by an adhesive. [0054]Step 04: Produce a feed and a ground on a circuit board and connect an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner. [0055]During disposing, when the electric-conductor is in different structural forms, different production manners may be used. For example, when the electric-conductor is a metallic wire, the fixing the electric-conductor on the feed may include disposing a support on the circuit board, and printing the metallic wire on the support, where one end of the metallic wire is electrically connected to the feed, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the ground, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the feed, the other end of the metallic wire is electrically connected to the ground, and the metallic wire is connected to the radiating element in a coupled manner. [0056]When the electric-conductor is a metal spring plate, the fixing of the electric-conductor on the feed is: connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the ground electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the ground electrically, where the metal spring plate and the radiating element are connected in a coupled manner. [0057]It can be understood from the foregoing description that the insulation film layer 20 on the insulation rear housing 10 serves as a carrier of the radiating element 30 of the antenna, and the radiating element 30 is located within an entire mobile terminal, thereby effectively increasing a height of the radiating element 30 of the antenna relative to the circuit board with the antenna not affecting an appearance of the mobile terminal. Compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm, thereby reducing an impact caused by a metal component on the circuit board on antenna radiation, and further increasing a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. In addition, in the antenna, an electrical connection between the electric-conductor and the radiating element is implemented in a coupled manner. Compared with a manner, in a general conventional solution, in which a signal line of the circuit board is directly connected to the antenna, feeding in a coupled manner can avoid problems caused by direct electrical-connection feeding, such as uneven contact pressure and a problem that impedance of a contact point becomes unstable after a long period of time due to factors such as oxidation. [0058]The foregoing descriptions are merely embodiments but are not intended as limiting. Any variation or replacement readily figured out by a person of ordinary skill in the art shall fall within the scope of the embodiments.(String), 交叉引用相关申请 [0001]该申请是美国专利申请Ser的延续。第16/954,591号,于2020年6月17日提交,这是国际申请号PCT/CN2019/098310的全国阶段,于2019年7月30日提交,要求中国专利申请号201810858567.0优先在2018年7月31日。所有上述申请均通过引用整体合并。 技术领域 [0002]该实施方案与天线技术和移动末端和移动末端天线生产方法有关。 背景 [0003]当前,智能手机的功能每天都在增加,智能手机需要涵盖日益广泛的沟通范围。手机设备对天线和天线数量也有越来越多的要求。如何在有限空间中放置更多天线是在天线结构场中解决的紧迫问题之一。目前,常见天线设计都使用了支持,例如激光直接结构(LDS)技术或手机的金属挡板作为天线散热器。天线可能是IFA,单极天线或环天线。但是,随着手机端各种组件和功能的需求不断增加,上述常规方法在将来的应用中受到限制,并且在天线辐射过程中所需的间隙区域相应降低。此外,在支撑塑料上结构的LDS天线通常放置在手机主体内,并且更容易受到外围部件和组件的影响。此外,由于天线相对较短,因此天线可能受到空间自由度或效率和带宽的限制。 概括 [0004]该实施例提供了移动终端和移动终端天线生产方法,以提高移动终端的通信性能。 [0005]根据第一个方面,提供了移动终端。移动终端包括一个移动终端主体和覆盖移动终端体的绝缘后壳体。绝缘膜层覆盖了绝缘后壳的内侧。当绝缘后壳覆盖移动端子体时,绝缘后壳的内侧是面向移动端子体的表面。此外,移动终端还包括天线。天线包括一个进料和一个辐射元件,并带有电馈电饲料。饲料被放置在移动端子体的电路板上,辐射元件印在绝缘膜层上。可以从上述描述中可以理解,即绝缘后壳上的绝缘膜层用作天线辐射元件的载体,并且辐射元件位于整个移动端子内,从而有效地增加了辐射的高度天线的元素相对于电路板的元素不影响移动端子的外观(与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6 mm的高度)。这减少了由金属组件对电路板对天线辐射的影响,并进一步增加了天线的带宽和效率,因此天线可以覆盖手持式通信系统中使用的频带。 [0006]处置时,辐射天线使用金属线。金属线可以是直线金属线,弯曲的金属线或螺旋金属线,并且形状不受限制。可以使用铝,铜和银等不同材料制备金属线。在实施方案中,金属线是银线。 [0007]对于辐射天线的处置位置,可以根据需要在绝缘后壳内侧的任何位置处置辐射天线,例如,侧壁上的位置。 [0008]为了改善天线的辐射效果,当将金属线处置时,金属线的厚度在1μm至200μm之间,金属线的阻抗小于3欧姆,或金属的平方电阻电线小于1欧姆/□。 [0009]只要可以确保绝缘材料,就可以使用不同的材料制备绝缘后外壳。例如,隔热后壳是玻璃后壳或塑料后壳。 [0010]对于绝缘膜层,可以使用具有不同功能的膜层。例如,绝缘膜层是墨水膜层,装饰膜层或反爆炸膜层。 [0011]对于天线,可以使用不同类型的天线。例如,天线是一个或多个GPS天线,Wi-Fi天线,NFC天线,毫米波天线,多样性天线或主天线。 [0012]当饲料和辐射元件电气连接时,天线进一步包括电导器。电导器将电动连接到饲料和/或接地,并且电导器以耦合方式连接到辐射元件。换句话说,电导器与辐射元件之间的电连接以耦合方式实现。与某种方式相比,在一般常规溶液中,电路板的信号线直接连接到天线,以耦合方式喂食可以避免由直接电 - 连接进料引起的问题,例如不均匀的接触压力和A由于氧化等因素,在长时间后,接触点的阻抗变得不稳定。 [0013]当处理电导器时,可以使用不同的溶液。例如,在解决方案中,移动终端进一步包括在移动终端机构中放置的电路板,并且将饲料和地面放在电路板上;并在电路板上丢弃支撑,电动导电器是在支撑上丢弃的金属线,其中金属线的一端是电到饲料的,并且金属线的另一端连接到以耦合方式辐射元件;或金属线的一端是电到地面的,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到饲料的,金属线的另一端是电连接到地面的,并且金属线以耦合方式连接到辐射元件。换句话说,金属线直接在支撑上处置以实现耦合连接。 [0014]在另一种解决方案中,移动终端进一步包括在移动终端机构中放置的电路板,并将饲料和地面放在电路板上;电导器是金属弹簧板,其中金属弹簧板的一端是电到饲料的,并且金属弹簧板的另一端以耦合方式连接到辐射元件。或金属弹簧板的一端电到电到地面,金属弹簧板的另一端以耦合方式连接到辐射元件。或金属弹簧板的一端是电到饲料的,金属弹簧板的另一端是电连接到地面的,金属弹簧板以耦合方式连接到辐射元件。 [0015]当使用金属弹簧板时,金属弹簧板可能​​具有不同的形状。例如,金属弹簧板是倒置的L形金属弹簧板或倒立的U形金属弹簧板。 [0016]根据第二个方面,提供了移动终端天线生产方法。生产方法包括以下步骤。 [0017]在绝缘膜层上打印一个辐射元件。例如,在膜层上喷涂银糊,然后在50度至200度的隔热膜层烘烤30分钟至60分钟,以形成金属线。 [0018]将绝缘膜层粘贴到隔热后壳的内侧。 [0019]绝缘后外壳上的绝缘膜层充当天线的辐射元件的载体,并且辐射元件位于整个移动端子内,从而有效地增加了天线相对于电路板的辐射元件的高度由于天线不影响移动端子的外观(与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6 mm的高度)。这减少了由金属组件对电路板对天线辐射的影响,并进一步增加了天线的带宽和效率,因此天线可以覆盖手持式通信系统中使用的频带。 [0020]用过的银糊剂包括50-99 wt%的银色粉末,银糊的粘度为10-20000 cps。 [0021]形成金属线后,金属线的厚度在1μm和200μm之间,金属线的阻抗小于3欧姆,或者金属线的平方电阻小于1欧姆/□,□,□,确保天线可以具有良好的沟通性能。 [0022]生产方法进一步包括:在电路板上产生进料和地面,并将电动导电器连接到饲料和/或电地面,在该电路板上电导器以耦合方式连接到辐射元件。 [0023]当电导器处于不同的结构形式时,可以使用不同的生产方式。例如,将电动导电器连接到饲料和/或电地面,在电动导电器以耦合方式连接到辐射元件的地方是:在电路板上处置支撑,并打印金属线在支撑上,金属线的一端是电到饲料的,并且金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到地面的,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到饲料的,金属线的另一端是电连接到地面的,并且金属线以耦合方式连接到辐射元件。 [0024]当电导器是金属弹簧板时,将电导器连接到进料和/或电地面,在该电板上,电导器以耦合方式连接到辐射元件的地面,是:连接一端的一端金属弹簧板用电到饲料,并以耦合方式将金属弹簧板的另一端连接到辐射元件。或将金属弹簧板的一端连接到地面,并以耦合方式将金属弹簧板的另一端连接到辐射元件;或将金属弹簧板的一端连接到电饲料,然后将金属弹簧板的另一端连接到地面,在那里金属弹簧板和辐射元件以耦合方式连接。换句话说,电导器可以以不同的结构形式形成。 附图的简要说明 [0025]如图。 1是根据实施方案的移动终端的示意图结构图; [0026]如图。 2是图2中的A-A的截面视图。 1; [0027]如图。 3是根据实施方案的另一个移动终端的示意图结构图; [0028]如图。 4是根据实施方案的另一个移动终端的示意图结构图; [0029]如图。 5是根据实施方案n的天线的示意图结构图; [0030]如图。 6是根据实施方案的另一个天线的示意图结构图; [0031]如图。 7是根据实施方案的另一个天线的示意性结构图。 [0032]如图。 8是根据实施方案的另一个天线的示意图结构图;和 [0033]如图。 9是根据实施方案生成移动末端天线的流程图。 实施例的详细说明 [0034]为了使实施方案的目标,解决方案和优势更清晰,以下内容进一步描述了有关附带图纸的详细说明。 [0035]一个实施例提供了移动终端。移动终端包括一个移动终端和绝缘后壳体10覆盖了移动终端体。绝缘后壳10是移动终端的电话外壳。如图。 1和图。 2显示绝缘后壳的结构10。首先,如图图所示。 1和图。 2,绝缘后壳10是矩形结构,包括平板和四个弯曲的侧壁。在弯曲期间,如图2所示。 2,图。 2在图中显示了A-A的截面视图。 1,侧壁和平板之间的连接方式如图2所示。 2,其中在弯曲侧壁和平板之间的关节上使用了弧形的过渡。此外,在生产过程中,隔热后壳体10以综合结构方式形成。但是,绝缘后壳的结构10不限于图2所示的结构。 1和图。 2,以及图中所示的结构。可以使用4。当图中所示的结构。使用4,隔热后壳10是弧形的后壳。但是,绝缘后壳的结构10可以或者可能是另一种结构形式。为了易于描述,隔热后壳的内侧10被定义为。绝缘后壳的内侧10在这个实施方案中,是绝缘后壳的凹面10。当绝缘后壳10内侧安装在移动终端主体上,面向移动终端主体。 [0036]可以选择不同的材料(例如玻璃和塑料)作为绝缘后壳10在此实施例中提供,只要可以实施绝缘。例如,当使用玻璃材料时,隔热材料后壳10是玻璃后壳10。 [0037]仍然指图。 1,绝缘膜层20覆盖绝缘后壳的内侧10。作为轴承结构,绝缘膜层20被配置为带有辐射元素30天线。对于绝缘膜层20,可以使用具有不同功能的膜层。例如,绝缘膜层20是墨水膜层,装饰膜层或反爆炸膜层。绝缘膜层使用的材料20可能是塑料。当绝缘膜层20覆盖绝缘后壳的内侧10,绝缘膜层20被粘附在隔热后壳的内侧10通过粘合剂或固定在绝缘后壳的内侧10通过真空吸附。 [0038]仍然指图。 1和图。 2,该实施方案中提供的移动末端进一步包括天线。对于天线,可以使用不同类型的天线。例如,天线是一个或多个GPS天线,Wi-Fi天线,NFC天线,毫米波天线,多样性天线或主天线。可以理解的是,所提供的天线包括上述几种类型的一个或多个天线,但不限于上述列出的类型的天线,无论使用的天线如何,此实施方案中提供的天线包括以下内容包括两个结构:饲料和辐射元件30。进料是电连接到辐射元件的30。饲料处置后,将饲料放在移动端子体的电路板上。电路板可以是PCB板。在辐射元件时提高天线的性能30被处置,如图2所示。 1和图。 2,辐射元件30印在隔热膜层上20。辐射元件30使用金属线,可能具有不同的形状。如图图所示。 1和图。 2,金属线可以是直线金属线,也可以是另一个结构,例如,弯曲的金属线或图2所示的螺旋金属线。 3.可以从图中理解。 1和图。 3辐射元件的形状30不限,可以根据需要做出不同的选择。另外,对于辐射元件的处置位置30,辐射元素30可以在绝缘膜层上的任何位置处置20。可以从图中理解。 1和图。 2隔热膜层没有另一个结构20。因此,可以根据需要选择不同的位置以处置辐射元件30。如图图所示。 1和图。 2,辐射元件30被处置在绝缘后壳的侧壁上10;并且,如图图所示。 3,辐射元件30被处置在隔热后壳的平板上10。另外,一定数量的辐射元素30不限。例如,有一个辐射元素30如图所示。 1,有两个辐射元素30如图所示。 4.此外,可以使用铝,铜和银等不同材料制备金属线。在实施方案中,金属线是银线,具有良好的电导率。 [0039]当辐射元素30生产,辐射元件30是在绝缘膜层上结构的20通过使用金属打印过程。在这个实施方案中,金属线是使用银糊制备的。因此,以下是使用银糊作为描述的示例。首先,所使用的银糊的组成部分包括50-99 wt%(质量百分比)银色粉末,形成的银糊的粘度为10-20000 cps(mpa·s),以确保稳定的银糊剂可以稳定到绝缘膜层20。在印刷过程中,首先将银糊喷涂或印刷在绝缘膜层上20(可以选择装饰膜层,反爆炸膜层或墨水膜层),然后是银糊和绝缘膜层20以50度至200度烘烤30分钟至60分钟(分钟),以增加隔热膜层的粘附20。然后,将银糊形成1μm至200μm的厚度(微米)。此外,确保制备的银糊的阻抗小于3欧姆(包括1欧姆)(测试的定义:以欧姆表示的值,在天线上的任何两个点之间测量)。换句话说,印刷金属线的厚度在1μm至200μm之间,例如3μm,5μm,10μm,15μm或20μm。另外,金属线的阻抗小于3欧姆,或者金属线的平方电阻小于1欧姆/□,在该方向性的定义如下所示。当长度由L表示时,宽度由W表示,并且高度由D表示(即膜的厚度),L(长度)= L和S(横截面区域)= W *d;因此,r =ρ*l/(w*d)=(ρ/d)*(l/w)。令l = w,然后r =(ρ/d),其中ρ是材料的电阻率。在这种情况下,r是平方电阻,以欧姆/□表示,其中“□”表示金属线的横截面为正方形。 [0040]在处置过程中,可以使用两种不同的举止。一种方式是:首先打印辐射元素30在绝缘膜层上20然后粘贴隔热膜层20进入隔热后外壳10。另一种方式是:首先粘贴隔热膜层20进入隔热后外壳10然后打印辐射元件30在绝缘膜层上20。如图图所示。 2和图。 4,当位置对应于辐射元件时30是弧形的,首先打印辐射元件的方式30在绝缘膜层上20大大促进处置辐射元件30。 [0041]可以从上述描述中可以理解出隔热膜层20在绝缘后壳的内侧10被配置为支持辐射元素30天线的辐射元件30位于整个移动终端内,从而有效地增加了辐射元件的高度30天线相对于电路板的天线不影响移动端子的外观。与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6毫米的高度,从而减少了由金属成分对电路板对天线辐射的影响,并进一步提高天线的带宽和效率天线可以覆盖手持通信系统中使用的频带。 [0042]当处置天线时,天线不仅包括辐射元件30,但还包括饲料和地面,饲料和地面是电到辐射元件的30。实现进料的电气连接以及地面到辐射元件30,在该实施方案中提供的天线中进一步处置了电导器。电导器将电导器电连接到饲料和/或地面,电导器连接到辐射元件30以耦合方式。应该理解,耦合连接是间接耦合连接,也就是说,辐射元素之间存在差距30电导器和电连接以电容耦合方式实现。当电导器处置电导器时,电导器可能采用不同的结构形式。以下描述了两个电导器的实现。 5和图。 7。 [0043]如图图所示。 5,将饲料放在电路板上60在移动终端机构和支持50进一步处置在电路板上60。支撑50被用作支撑电导器的支撑载体。在图中所示的结构中。 5,电导器是金属线40。金属线40以打印或灵活的板粘性方式固定在支撑上。另外,一数量的电导器在一对一的对应关系中,散发元件数量30。当两个辐射元素30在图中使用。 5,有两个相应的电导器,还有两个相应的支撑50。支撑50可能是不同的结构形式。例如,在图中。 5,支持50是一个支撑块,支撑块固定在电路板上60以一种粘性的方式。可以理解,作为载体,支持50应隔热,以避免影响电导器的功率喂养。如图。 5是金属线之间电连接的示意图40和饲料。如图图所示。 6,移动终端的位置方向。 6用作参考方向。金属线40位于右侧的电气连接到地面,金属线的两端40位于左侧的电气连接到地面和饲料。当金属电线40是电连接到地面的,是金属电线的处置方式40与图中的相似之处。 5,唯一的区别在于那一条金属线40已连接到电路板上的供稿60和另一根金属电线40连接到电路板上的地面60。当金属线的两端40分别连接到饲料和地面,金属线的一端40连接到进料点,而金属线的另一端连接40连接到地面。金属线40连接到辐射元件30以耦合方式。耦合部分是两端之间的一部分。 [0044]如图。 7显示了另一个电导器的结构。在图中。 7,电导器是金属弹簧板70。金属弹簧板的一端70固定(电连接)到饲料,而金属弹簧板的另一端70是自由的。金属弹簧板的自由端70连接到辐射元件30以耦合方式。在处置过程中,如图2所示。 7,金属弹簧板70是倒L形金属弹簧板70。但是,金属弹簧板的结构形式70不仅限于图2中指定的。 7.金属弹簧板70可以或者可能是弧形金属板或波浪状的金属弹簧板70,并且两者都可以应用于实施方案。对于金属弹簧板的材料70,该材料可能具有良好的电导率和强度,例如铜,铝或铁。如图图所示。 8,移动终端的位置方向。 8用作参考方向。金属弹簧板70位于右侧的电气连接到地面,金属弹簧板的两端70位于左侧的电气连接到地面和饲料。当金属弹簧板70是电连接到地面的,是金属弹簧板的处置方式70与图中的相似之处。 7,唯一的区别在于那个金属弹簧板70已连接到电路板上的供稿60,还有其他金属弹簧板70连接到电路板上的地面60。当金属弹簧板的两端70分别连接到饲料和地面,金属弹簧板的一端70连接到进料点,而金属弹簧板的另一端70连接到地面。金属弹簧板70连接到辐射元件30以耦合方式。耦合部分是两端之间的一部分。在这种情况下,金属弹簧板70是倒的U形结构。 [0045]可以从图中理解。 5到图。 8在天线中,电导器与辐射元件之间的电连接以及电导器与地面之间的电连接以耦合方式实现。与某种方式相比,在常规解决方案中,电路板的信号线60直接连接到天线,以耦合方式喂食可以避免直接电连接进料引起的问题,例如不均匀的接触压力和由于诸如诸如等因素(例如氧化。 [0046]此外,实施方案进一步提供了一种天线生产方法。该方法包括:打印辐射元素30在绝缘膜层上20并粘贴隔热膜层20到绝缘后壳的内侧10。该方法包括两种不同的举止:首先打印一个辐射元素30在绝缘膜层上20,然后粘贴隔热膜层20进入绝缘后壳10;或首先粘附隔热膜层20进入绝缘后壳10,然后打印一个辐射元素30在绝缘膜层上20。如图图所示。 2和图。 4,可以从图中理解。 1和图。 4当位置对应于辐射元件时30是弧形的,首先打印辐射元件的方式30在绝缘膜层上20大大促进处置辐射元件30。 [0047]以下内容详细介绍了该方法,参考图。 9。 [0048]步01:在绝缘膜层上喷涂银糊20。 [0049]例如,用过的银糊的材料包括50-99 wt%(质量百分比)银色粉末,银糊的粘度为10-20000 cps(mpa·s),以便将银糊牢固地粘附在绝缘膜层20。 [0050]步02:将银糊和绝缘膜层以50度至200度烘烤30分钟至60分钟(分钟),以形成金属线。 [0051]当形成金属线时,金属线的厚度为1μm至200μm(微米),例如3μm,5μm,10μm,15μm,或20μm。此外,金属线的阻抗小于3欧姆,或者金属线的平方电阻小于1欧姆/□,以确保天线可以具有良好的通信性能。 [0052]步03:粘贴隔热膜层20到绝缘后壳的内侧10。 [0053]例如,绝缘膜层20金属线印刷在上面10通过粘合剂。 [0054]步04:在电路板上产生一个进料和接地,并将电导器连接到饲料和/或电地面,在该电路板上电导器以耦合方式连接到辐射元件。 [0055]在处置过程中,当电导器处于不同的结构形式时,可以使用不同的生产方式。例如,当电导器是金属电线时,饲料上的电导器固定可能包括在电路板上放置支架,并在支撑板上打印金属线,其中金属线的一端是电气的连接到饲料,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到地面的,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到饲料的,金属线的另一端是电连接到地面的,并且金属线以耦合方式连接到辐射元件。 [0056]当电导器是金属弹簧板时,电动导体在进料上的固定是:将金属弹簧板的一端连接到电饲料,并将金属弹簧板的另一端连接到辐射元件以耦合方式;或将金属弹簧板的一端连接到地面,并以耦合方式将金属弹簧板的另一端连接到辐射元件;或将金属弹簧板的一端连接到电饲料,然后将金属弹簧板的另一端连接到地面,在那里金属弹簧板和辐射元件以耦合方式连接。 [0057]可以从上述描述中可以理解出隔热膜层20在隔热后壳体上10用作辐射元件的载体30天线和辐射元件30位于整个移动终端内,从而有效地增加了辐射元件的高度30天线相对于电路板的天线不影响移动端子的外观。与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6毫米的高度,从而减少了由金属成分对电路板对天线辐射的影响,并进一步提高天线的带宽和效率天线可以覆盖手持通信系统中使用的频带。另外,在天线中,电导器与辐射元件之间的电连接以耦合方式实现。与某种方式相比,在一般常规溶液中,电路板的信号线直接连接到天线,以耦合方式喂食可以避免由直接电 - 连接进料引起的问题,例如不均匀的接触压力和A由于氧化等因素,在长时间后,接触点的阻抗变得不稳定。 [0058]上述描述仅仅是实施方案,但并不是限制的。在艺术中有普通技能的人易于弄清楚的任何变异或替代品均应属于实施方案的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN110784564A(String), CN110784564B(String), CN111509367A(String), CN111509367B(String), CN112534796A(String), EP3709610A1(String), EP3709610A4(String), US11450946B2(String), US20200335854A1(String), US20220368007A1(String), WO2020024925A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.481 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.482 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN110784564A(String), CN110784564B(String), CN111509367A(String), CN111509367B(String), CN112534796A(String), EP3709610A1(String), EP3709610A4(String), US11450946B2(String), US20200335854A1(String), US20220368007A1(String), WO2020024925A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20220368007A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN110784564A(String), CN110784564B(String), CN111509367A(String), CN111509367B(String), CN112534796A(String), EP3709610A1(String), EP3709610A4(String), US11450946B2(String), US20200335854A1(String), US20220368007A1(String), WO2020024925A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), CN110784564A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), CN110784564B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), CN111509367A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.521 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), CN111509367B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), CN112534796A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.544 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), EP3709610A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), EP3709610A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), US11450946B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.569 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), US20200335854A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), US20220368007A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270700(Integer), WO2020024925A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.598 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20220368007A1(String), US20220368007A1(String), 1668614400(Integer), 270700(Integer), 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.611 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185024(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185024(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185024(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185024(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.646 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.657 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.658 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 实质审查(String), 1(Integer), 185024(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10165161B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Bracket assembly for mobile terminal and mobile terminal(String), 移动终端和移动终端支架总成(String), US10165161B2(String), A bracket assembly for use in a mobile terminal includes a metal support and a multi-contact spring. The metal support is configured to support an electronic component of the mobile terminal. The multi-contact spring includes a first pressure contact part, a second pressure contact part, a first elastic part, a second elastic part, and a fixing part. The multi-contact spring is fixed to a frame of the mobile terminal by a fastener extending through the fixing part into the frame. The first elastic part is connected to the first pressure contact part and the fixing part and is configured to provide a first restoring force to the first pressure contact part such that the first pressure contact part abuts against a metal cover of the mobile terminal and is grounded.(String), 一种用于移动终端的支架组件,包括金属支架和多触点弹簧。 金属支架用于支撑移动终端的电子元件。 多触点弹簧包括第一压接部、第二压接部、第一弹性部、第二弹性部和固定部。 多触点弹簧通过延伸穿过固定部进入框架的紧固件固定到移动终端的框架。 第一弹性部连接第一压接部和固定部,用于向第一压接部提供第一回复力,使第一压接部抵靠移动终端的金属盖并接地。 .(String), US15/793588(String), 1508860800(Integer), US10165161B2(String), 1545667200(Integer), 1545667200(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 10(Integer), CN105356077A | CN201995193U | CN202750132U | CN205609765U | US20140111684A1 | US20150062419A1 | US20180176346A1 | US20180176351A1 | US9759988B2 | WO2016032561A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185025(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0db2cff6b50847ae8d8729be20f9a58e.png(String), 185025(Integer), 0db2cff6b50847ae8d8729be20f9a58e.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Bracket assembly for mobile terminal and mobile terminal(String), 移动终端和移动终端支架总成(String), US10165161B2(String), A bracket assembly for use in a mobile terminal includes a metal support and a multi-contact spring. The metal support is configured to support an electronic component of the mobile terminal. The multi-contact spring includes a first pressure contact part, a second pressure contact part, a first elastic part, a second elastic part, and a fixing part. The multi-contact spring is fixed to a frame of the mobile terminal by a fastener extending through the fixing part into the frame. The first elastic part is connected to the first pressure contact part and the fixing part and is configured to provide a first restoring force to the first pressure contact part such that the first pressure contact part abuts against a metal cover of the mobile terminal and is grounded.(String), 一种用于移动终端的支架组件,包括金属支架和多触点弹簧。 金属支架用于支撑移动终端的电子元件。 多触点弹簧包括第一压接部、第二压接部、第一弹性部、第二弹性部和固定部。 多触点弹簧通过延伸穿过固定部进入框架的紧固件固定到移动终端的框架。 第一弹性部连接第一压接部和固定部,用于向第一压接部提供第一回复力,使第一压接部抵靠移动终端的金属盖并接地。 .(String), US15/793588(String), 1508860800(Integer), US10165161B2(String), 1545667200(Integer), 1545667200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 10(Integer), CN105356077A | CN201995193U | CN202750132U | CN205609765U | US20140111684A1 | US20150062419A1 | US20180176346A1 | US20180176351A1 | US9759988B2 | WO2016032561A1(String), \20230420\0db2cff6b50847ae8d8729be20f9a58e.png(String), 20(Integer), 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.703 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 1. A bracket assembly in a mobile terminal, the mobile terminal comprising a communication element, an electronic component, a frame, and a metal cover, the bracket assembly comprising:a metal support configured to support the electronic component of the mobile terminal; anda multi-contact spring comprising at least one first pressure contact part, at least one second pressure contact part, at least one first elastic part, at least one second elastic part, and at least one fixing part, wherein the multi-contact spring is fixed to the frame of the mobile terminal by the at least one fixing part, the at least one first elastic part is connected to the at least one first pressure contact part and the at least one fixing part and is configured to provide a first restoring force to the at least one first pressure contact part such that the at least one first pressure contact part abuts against the metal cover of the mobile terminal and is grounded, and the at least one second elastic part is connected to the at least one second pressure contact part and the at least one fixing part and is configured to provide a second restoring force to the at least one second pressure contact part such that the at least one second pressure contact part abuts against the metal support so as to ground the metal support to reduce signal interference of the metal support to the communication element.(String), 1.一种移动终端中的支架组件,该移动终端包括通信元件、电子元件、框架和金属盖,支架组件包括:金属支架,用于支撑移动终端的电子部件;和一种多接点弹簧,包括至少一第一压接部、至少一第二压接部、至少一第一弹性部、至少一第二弹性部及至少一固定部,其中,多接点弹簧为至少一固定部固定于移动终端的边框,至少一第一弹性部连接至少一第一压接部及至少一固定部,用以提供第一回复力至少一第一压接部使至少一第一压接部抵接移动终端的金属盖体并接地,至少一第二弹性部连接至少一第二压接部该至少一固定部与该至少一固定部,并用以提供一第二回复力至该至少一第二压接部,以使该至少一第二压接部抵靠该固定部。l支架将金属支架接地,减少金属支架对通讯元件的信号干扰。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 2. The bracket assembly as claimed in claim 1, wherein the at least one fixing part comprises a base piece having a pair of long sides and a pair of short sides connecting the long sides, the at least one first pressure contact part is elastically connected to the short sides by the at least one first elastic part, the base piece extends along one of the long sides and is bent to form a connecting piece, and the at least one second pressure contact part is elastically connected to the connecting piece by the at least one second elastic part.(String), 2.如权利要求1所述的支架组件,其中至少一固定部包括一基片,基片具有一对长边及一对连接长边的短边,至少一第一压接部通过至少一第一弹性件弹性连接至短边。基片沿其中一长边延伸并弯折形成连接片,至少一第二压接部通过至少一第二弹性部弹性连接于连接片。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 3. The bracket assembly as claimed in claim 2, wherein a number of the at least one first pressure contact part is two, a number of the at least one first elastic part is two, and each of the first pressure contact parts is elastically connected to one of the short sides by a respective one of the first elastic parts.(String), 3.如权利要求2所述的支架组件,其中至少一第一压接部的数量为二,至少一第一弹性部的数量为二,且各第一压接部分别通过一短边弹性连接于其中一短边。首先是弹性部件。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 4. The bracket assembly as claimed in claim 3, wherein the mobile terminal comprises a fastener, and the base piece comprises a fixing hole configured to insert the fastener to fix the multi-contact spring to the frame.(String), 4.如权利要求3所述的支架组件,其中移动终端包括固定件,基片包括固定孔,固定孔用于插入固定件以将多触点弹簧固定到框架。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 5. The bracket assembly as claimed in claim 4, wherein the frame comprises a convex part, the base piece extends along another of the long sides and is bent to form a plurality of bending ends, a bending direction of the bending ends with respect to the base piece is the same as a bending direction of the connecting piece, the bending ends, the base piece, and the connecting piece are connected in order, the base piece comprises a receiving space defined by a region among the bending ends, the base piece, and the connecting piece, and the convex part of the frame configured to fix the multi-contact spring is received in the receiving space so as to restrict rotation of the multi-contact spring with respect to the fastener.(String), 5.如权利要求4所述的支架组件,其中框架包括凸部,基部沿另一长边延伸并弯折形成多个弯折端,弯折端相对于基部的弯折方向与基部的弯折方向相同。连接件、弯折端、基件和连接件依次连接,基件包括由弯折端、基件和连接件之间的区域限定的容纳空间,以及凸起部分。用于固定多触点弹簧的框架容纳在容纳空间中以限制多触点弹簧相对于紧固件的转动。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 6. The bracket assembly as claimed in claim 1, wherein the metal support comprises a plurality of side walls connected in order and an accommodating space cooperatively defined by the side walls for accommodating the electronic component, the side walls comprises a wall away from a side of the accommodating space, and the second pressure contact part elastically abuts against the wall.(String), 6.如权利要求1所述的支架组件,其中金属支架包括多个依次连接的侧壁和由侧壁共同限定的容置电子元件的容置空间,侧壁包括远离容置空间一侧的壁,第二压接部弹性地连接。靠在墙上。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 7. The bracket assembly as claimed in claim 6, wherein the frame comprises a slot, and the wall comprises a plurality of fixing blocks convexly disposed on the wall for inserting into the slot of the frame such that the metal support is mounted on the frame.(String), 7.如权利要求6所述的支架组件,其中框架包含一槽孔,壁面包含多个固定块,凸设于壁面,用以插入框架的槽孔内,使金属支架安装于框架上。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 8. The bracket assembly as claimed in claim 1, further comprising a plurality of convex contacts disposed on a top of the first pressure contact part and a top of the second pressure contact part.(String), 8.如权利要求1所述的支架组件,还包括多个凸状接点设置于第一压接部的顶部与第二压接部的顶部。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 9. The bracket assembly as claimed in claim 1, wherein the first pressure contact part, the second pressure contact part, the first elastic part, the second elastic part, and the fixing part are an integral structure integrally formed by bending at least one of a metal material and a metal alloy material.(String), 9.如权利要求1所述的支架组件,其中第一压接部、第二压接部、第一弹性部、第二弹性部和固定部为金属材料和金属合金材料中的至少一种通过弯折一体成型的一体结构。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 10. A mobile terminal, comprising:a communication element disposed in the mobile terminal;a frame;a metal cover, being attached to the frame;an electronic component; anda bracket assembly, comprising:a metal support configured to support the electronic component of the mobile terminal; anda multi-contact spring comprising at least one first pressure contact part, at least one second pressure contact part, at least one first elastic part, at least one second elastic part, and at least one fixing part, wherein the multi-contact spring is fixed to the frame of the mobile terminal by the at least one fixing part, the at least one first elastic part is connected to the at least one first pressure contact part and the at least one fixing part and is configured to provide a first restoring force to the at least one first pressure contact part such that the at least one first pressure contact part abuts against the metal cover of the mobile terminal and is grounded, and the at least one second elastic part is connected to the at least one second pressure contact part and the at least one fixing part and is configured to provide a second restoring force to the at least one second pressure contact part such that the at least one second pressure contact part abuts against the metal support so as to ground the metal support to reduce signal interference of the metal support to the communication element.(String), 10.移动终端一个,包括:设置在移动终端中的通信元件;一个框架;金属盖,附接于框架;电子元件;和支架组件,包括:金属支架,用于支撑移动终端的电子部件;和一种多接点弹簧,包括至少一第一压接部、至少一第二压接部、至少一第一弹性部、至少一第二弹性部及至少一固定部,其中,多接点弹簧为至少一固定部固定于移动终端的边框,至少一第一弹性部连接至少一第一压接部及至少一固定部,用以提供第一回复力至少一第一压接部使至少一第一压接部抵接移动终端的金属盖体并接地,至少一第二弹性部连接至少一第二压接部该至少一固定部与该至少一固定部,并用以提供一第二回复力至该至少一第二压接部,以使该至少一第二压接部抵靠该固定部。l支架将金属支架接地,减少金属支架对通讯元件的信号干扰。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 11. The mobile terminal as claimed in claim 10, wherein the electronic component is a dual camera assembly.(String), 11.如权利要求10所述的移动终端,其中电子元件是双摄像头组件。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 12. The mobile terminal as claimed in claim 10, wherein the at least one fixing part comprises a base piece having a pair of long sides and a pair of short sides connecting the long sides, the at least one first pressure contact part is elastically connected to the short sides by the at least one first elastic part, the base piece extends along one of the long sides and is bent to form a connecting piece, and the at least one second pressure contact part is elastically connected to the connecting piece by the second at least one elastic part.(String), 12.如权利要求10所述的移动终端,其中至少一固定部包括一基片,基片具有一对长边及一对连接长边的短边,至少一第一压接部通过至少一第一弹性件弹性连接至短边。基片沿其中一长边延伸并弯折形成一连接件,至少一第二压接部通过至少一第二弹性件弹性连接于连接件。(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 13. The mobile terminal as claimed in claim 12, wherein a number of the at least one first pressure contact part is two, a number of the at least one first elastic part is two, and each of the first pressure contact parts is elastically connected to one of the short sides by a respective one of the first elastic parts.(String), 13.如权利要求12所述的移动终端,其中至少一第一压接部的数量为二,至少一第一弹性部的数量为二,且各第一压接部分别通过一短边弹性连接于其中一短边。首先是弹性部件。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 14. The mobile terminal as claimed in claim 13, wherein the mobile terminal comprises a fastener, and the base piece comprises a fixing hole configured to insert the fastener to fix the multi-contact spring to the frame.(String), 14.如权利要求13所述的移动终端,其中移动终端包括固定件,基片包括固定孔,固定孔用于插入固定件以将多触点弹簧固定到框架。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 15. The mobile terminal as claimed in claim 14, wherein the frame comprises a convex part, the base piece extends along another of the long sides and is bent to form a plurality of bending ends, a bending direction of the bending ends with respect to the base piece is the same as a bending direction of the connecting piece, the bending ends, the base piece, and the connecting piece are connected in order, the base piece comprises a receiving space defined by a region among the bending ends, the base piece, and the connecting piece, and the convex part of the frame configured to fix the multi-contact spring is received in the receiving space so as to restrict rotation of the multi-contact spring with respect to the fastener.(String), 15.如权利要求14所述的移动终端,其中框架包括凸部,基部沿另一长边延伸并弯折形成多个弯折端,弯折端相对于基部的弯折方向与基部的弯折方向相同。连接件、弯折端、基件和连接件依次连接,基件包括由弯折端、基件和连接件之间的区域限定的容纳空间,以及凸起部分。用于固定多触点弹簧的框架容纳在容纳空间中以限制多触点弹簧相对于紧固件的转动。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 16. The mobile terminal as claimed in claim 10, wherein the metal support comprises a plurality of side walls connected in order and an accommodating space cooperatively defined by the side walls for accommodating the electronic component, the side walls comprises a wall away from a side of the accommodating space, and the second pressure contact part elastically abuts against the wall.(String), 16.如权利要求10所述的移动终端,其中金属支架包括多个依次连接的侧壁和由侧壁共同限定的容置电子元件的容置空间,侧壁包括远离容置空间一侧的壁,第二压接部弹性地连接。靠在墙上。(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 17. The mobile terminal as claimed in claim 16, wherein the frame comprises a plurality of slots surrounding the metal support, and the wall comprises a plurality of fixing blocks convexly disposed on the wall for inserting into the slot of the frame such that the metal support is mounted on the frame.(String), 17.如权利要求16所述的移动终端,其中框架包括围绕金属支架的多个槽,壁包括多个固定块,其凸设在壁上,用于插入框架的槽中,从而将金属支架安装在框架上。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 18. The mobile terminal as claimed in claim 10, further comprising a plurality of convex contacts disposed on a top of the first pressure contact part and a top of the second pressure contact part.(String), 18.如权利要求10所述的移动终端,还包括多个凸状接点设置于第一压接部的顶部与第二压接部的顶部。(String), 1(Integer), 17(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 19. The mobile terminal as claimed in claim 16, wherein the electronic component comprises a first camera lens and a second camera lens arranged side by side with the first camera lens, and the first camera lens and the second camera lens are disposed in the accommodating space.(String), 19.如权利要求16所述的移动终端,其中电子元件包括第一镜头以及与第一镜头并排设置的第二镜头,第一镜头以及第二镜头设置于容置空间内。(String), 1(Integer), 18(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185025(Integer), 20. The mobile terminal as claimed in claim 19, wherein the metal cover comprises two shooting windows, and the first camera lens and the second camera lens take pictures through a respective window of the two shooting windows.(String), 20.如权利要求19所述的移动终端,其中金属盖体包括两个拍摄窗,第一镜头和第二镜头分别通过两个拍摄窗中的一个窗口进行拍摄。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185025(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority to Chinese Application No. 201611185479.6 filed Dec. 20, 2016. The entire disclosure of the above application is incorporated herein by reference in its entirety. BACKGROUND [0002]Field [0003]The present disclosure relates to the field of electronic equipment, and particularly to a bracket assembly for a mobile terminal and a mobile terminal having the bracket assembly. [0004]Background [0005]Widespread and growing use of smart phones increases the need for a support to stabilize electronic components, such as a camera device, inside a mobile phone. In consideration of rigidity, size, and installation requirements of the support, a metal support is usually used to stabilize the electronic component. However, because metal is conductive, the metal support easily interferes with electromagnetic signals from communication elements inside the mobile phone, and thus reducing communication performance of the communication elements inside the mobile phone. [0006]In present technology, the metal support, used to stabilize the electronic component inside the mobile phone, reduces user experience. BRIEF DESCRIPTION OF THE DRAWINGS [0007]In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person skilled in the art can obtain other figures according to these figures without paying the premise. [0008]FIG. 1 is an assembled view of a bracket assembly according to an embodiment of the present disclosure. [0009]FIG. 2 is an exploded view of the bracket assembly according to the embodiment of the present disclosure. [0010]FIGS. 3A, 3B, and 3C are schematic views of a multi-contact spring according to the embodiment of the present disclosure. [0011]FIG. 4 is a schematic view of a board according to the embodiment of the present disclosure. [0012]FIG. 5 is a schematic view of a metal support according to the embodiment of the present disclosure. [0013]FIG. 6 is a schematic view of a frame according to the embodiment of the present disclosure. [0014]FIG. 7 is a partially assembled view of a mobile terminal according to the embodiment of the present disclosure. [0015]FIG. 8 is a partially exploded view of the mobile terminal according to the embodiment of the present disclosure. DETAILED DESCRIPTION OF ILLUSTRATED EMBODIMENTS [0016]In combination with the drawings of the embodiments of the present disclosure, the following is related to a detailed and complete description of the technology of the embodiments of the present disclosure. It is obvious that the disclosed embodiments are only a part of the embodiments available to the present disclosure, rather than the all embodiments thereof. Based on the disclosed embodiments of the present disclosure, other embodiments obtained by a person skilled in the art without endeavor of creativity belong to the protected scope of the present embodiments of the present disclosure. [0017]Referring to FIGS. 1, 2, and 3A to 3C, a bracket assembly is disposed in a mobile terminal, and the mobile terminal includes a communication element for receiving or transmitting a signal. The communication element may be a board 30 or an antenna. The bracket assembly includes a metal support 10 and a multi-contact spring 20. The metal support 10 is configured to support an electronic component of the mobile terminal. The electronic component is, for example, a dual camera assembly. The multi-contact spring 20 includes at least one first pressure contact part 201, at least one second pressure contact part 202, at least one first elastic part 203, at least one second elastic part 204, and at least one fixing part 200. The multi-contact spring 20 is fixed to a frame 40 of the mobile terminal by the at least one fixing part 200. The at least one first elastic part 203 is connected to the at least one first pressure contact part 201 and the at least one fixing part 200 and is configured to provide a first restoring force to the at least one first pressure contact part 201 such that the at least one first pressure contact part 201 firmly abuts against a metal cover 60 of the mobile terminal. The at least one second elastic part 204 is connected to the at least one second pressure contact part 202 and the at least one fixing part 200 and is configured to provide a second restoring force to the at least one second pressure contact part 202 such that the at least one second pressure contact part 202 firmly abuts against the metal support 10. The metal support 10 is connected to the metal cover 60 via the multi-contact spring 20 and is grounded. The frame 40 may be a middle frame of the mobile terminal, and the metal cover 60 may be a metal back cover of the mobile terminal. In an embodiment, the mobile terminal may be an electronic equipment such as a mobile phone, a notebook computer, a tablet computer, etc. [0018]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with a ground electrode of the metal cover 60 without changing mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced, to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0019]Further, the multi-contact spring 20 connects current of the metal support 10 to the ground electrode of the metal cover 60. The multi-contact spring 20 can, on the one hand, reduce the overall electric potential of the metal support 10 and, on the other hand, static electricity of the metal support 10 is guided to the ground electrode so as to prevent the static electricity of the metal support 10 from flowing to the electronic component, to protect the electronic component. The ground electrode may be exposed copper on the board 30. The metal cover 60 is in communication with the board 30, and the first pressure contact part 201 of the multi-contact spring 20 abuts against the metal cover 60 to communicate with the exposed copper of the board 30. [0020]In an embodiment, the at least one fixing part 200 includes a base piece 200a having a pair of long sides 2001 and a pair of short sides 2002 connecting the long sides 2001. The at least one first pressure contact part 201 is elastically connected to the short sides 2002 by the at least one first elastic part 203, the base piece 200a extends along one of the long sides 2001 and is bent to form a connecting piece 200b, and the at least one second pressure contact part 202 is elastically connected to the connecting piece 200b by the at least one second elastic part 202. In an embodiment, the base piece 200a is a long strip, the pair of long sides 2001 are parallel to each other, and the pair of short sides 2002 are parallel to each other. The first pressure contact part 201 is elastically connected to an edge of the short side 2002 by the first elastic part 203. The first elastic part 203 applies an elastic force to the first pressure contact part 201, and when the first pressure contact part 201 is subjected to pressure opposite to a direction of the elastic force provided by the first elastic part 203, the first elastic part 203 causes the first pressure contact part 201 to firmly abuts against an object, which applies pressure to the first pressure contact part 201. In the embodiment, the object for applying pressure to the first pressure contact part 201 may be the metal cover 60. One of the long sides 2001 of the base piece 200a extends and is bent to form the connecting piece 200b. The connecting piece 200b is at an angle to the base piece 200a. For example, the connecting piece 200b and the base piece 200a are perpendicular to each other. The connecting piece 200b is connected to the second pressure contact part 202 and the fixing part 200. In detail, the second pressure contact part 202 is elastically connected to the connecting piece 200b by the second elastic part 204. The second elastic part 204 applies an elastic force to the second pressure contact part 202, and when the second pressure contact part 202 is subjected to pressure opposite to a direction of the elastic force provided by the second elastic part 204, the second elastic part 204 causes the second pressure contact part 202 to firmly abuts against an object, which applies pressure to the second pressure contact part 202. In the embodiment, the object for applying pressure to the second pressure contact part 202 may be the metal support 10. [0021]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with the ground electrode of the metal cover 60 without changing the mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0022]Further, a number of the at least one first pressure contact part 201 is two, a number of the at least one first elastic part 203 is two, and each of the first pressure contact parts 201 is elastically connected to one of the short sides 2002 by a respective one of the first elastic parts. The two first pressure contact parts 201 abut against a housing of the mobile terminal such that the metal support 10 is grounded, a number of contacts is increased, the overall electric potential of the metal support 10 is reduced, and interference of electromagnetic signals from the communication elements is reduced. [0023]Referring to FIGS. 3 and 4, in the embodiment, the bracket assembly includes a fastener 70, the base piece 200a includes a fixing hole 2003, and the frame 40 includes a convex part 400 having a threaded hole 402 configured to fix the multi-contact spring 20 to the convex part 400 by the fastener 70. In an embodiment, the fastener 70 may be a screw. The base piece 200a is locked to the frame 40 by the screw such that the multi-contact spring 20 is securely fixed to the frame 40. Therefore, the first pressure contact part 201 can stably abut against the metal cover 60, the second pressure contact part 202 can stably abut against the metal support 10, and structural stability of the bracket assembly is improved. [0024]In addition, the base piece 200a extends along another of the long sides 2001 and is bent to form a plurality of bending ends, a bending direction of the bending ends with respect to the base piece 200a is the same as a bending direction of the connecting piece 200b. The bending ends, the base piece 200a, and the connecting piece 200b are connected in order, the base piece 200a includes a receiving space defined by a region among the bending ends, the base piece 200a, and the connecting piece 200b. The convex part 400 of the frame 40 is received in the receiving space to restrict rotation of the multi-contact spring 20. In another embodiment, a number of the bent ends of each of the multi-contact spring 20 is two for firmly fixing the multi-contact spring 20 and the frame 40. [0025]Referring to FIG. 5, in the embodiment, the metal support 10 includes a plurality of side walls 102 connected in order and an accommodating space 11 cooperatively defined by the side walls 102 for accommodating the electronic component. In detail, the metal support 10 accommodates the electronic component to facilitate installation and stabilization of the electronic component. The electronic component may be a camera module, a speaker, a fingerprint module, a connector, etc. [0026]Further, the metal support 10 has a rectangular block shape. The metal support 10 may be made of aluminum alloy material, silver material, or iron material, etc. The metal support 10 is formed by shaping a metal block using an automatic numerical control milling process. That is, forming dimensions of the side walls 102 are machined by the numerical control milling process such that dimensional accuracy of the side wall 102 is high, the electronic component can be effectively stabilized and precisely positioned, and the position of the electronic component can be easily calibrated. In addition, the metal support 10 can also be effectively fixed to an external member such that the fixing position of the metal support 10 is precise and the metal support 10 is conveniently positioned. Therefore, the mounting position of the electronic component can be accurately improved and performance of the electronic component can be improved. The accommodating space 11 can accommodate one electronic component, two electronic components, or a plurality of electronic components such that the metal support 10 can fix the plurality of electronic components centrally to save space. [0027]In the embodiment, the side walls 102 include a wall away from a side of the accommodating space 11, and a pressure contact part (including the first pressure contact part 201 and the second pressure contact part 202) elastically abuts against the wall. Restoring force applied to the pressure contact part by an elastic part (including the first elastic part 203 and the second elastic part 204) causes the pressure contact part to firmly abut against the wall of the side wall 102 of the metal support 10 to ensure that the pressure contact part and the metal support 10 can be brought into stable contact. Therefore, loose contact between the multi-contact spring 20 and the metal support 10 does not occur easily when using the mobile terminal, and the structural stability of the mobile terminal is improved. In addition, the pressure contact part elastically contacts the wall of the metal support 10 to facilitate installation and removal of the metal support 10. The metal support 10 is removed from the mobile terminal by simply pulling out the metal support 10 in a direction perpendicular to the pressure contact part against the side wall 102. The metal support 10 is mounted on the mobile terminal by simply pushing the pressure contact part in advance and placing the metal support 10 in the mobile terminal. The difficulty of installation and removal of the metal support 10 is reduced. [0028]Referring to FIG. 6, in the embodiment, the bracket assembly is applied to the mobile terminal, and the metal support 10 is fixed to the frame 40. In detail, the wall away from a side of the accommodating space 11 includes a plurality of fixing blocks 104 convexly disposed on the wall. The frame 40 includes a plurality of slots 404 corresponding to the fixing blocks 104 for inserting the fixing blocks 104 such that the metal support 10 is mounted on the frame 40. The fixing blocks 104 of the metal support 10 engage with the slots 404 such that the metal support 10 is securely mounted on the frame 40 to improve structural stability of the mobile terminal. [0029]In the embodiment, the bracket assembly includes a plurality of convex contacts disposed on a top of the pressure contact part, and the convex contacts increases a contact area between the pressure contact part and the metal support 10, such that the pressure contact part firmly abuts against the side wall 102 of the metal support 10. [0030]In the embodiment, the first pressure contact part 201, the second pressure contact part 202, the first elastic part 203, the second elastic part 204, and the fixing part 200 are an integral structure integrally formed by bending at least one of a metal material and a metal alloy material. Therefore, manufacturing process of the elastic device is simplified and production materials of the elastic device is saved. [0031]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with a ground electrode of the metal cover 60 without changing a mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0032]Referring to FIGS. 7 and 8, an embodiment of the disclosure includes a mobile terminal 100. The mobile terminal 100 includes the metal cover 60, the board 30, the frame 40, and the bracket assembly. The multi-contact spring 20 is fixed to the frame 40, the first pressure contact part abuts against the grounded metal cover 60. The board 30 includes a ground electrode. The metal cover 60 is connected to the board 30. The second pressure contact part abuts against the metal support 10 to ground the metal support 10. The multi-contact spring 20 is fixed to the frame 40 of the mobile terminal 100 by the at least one fixing part 200. The at least one first elastic part 203 is connected to the at least one first pressure contact part 201 and the at least one fixing part 200 and is configured to provide a first restoring force to the at least one first pressure contact part 201 such that the at least one first pressure contact part 201 firmly abuts against the metal cover 60 of the mobile terminal 100. The at least one second elastic part 204 is connected to the at least one second pressure contact part 202 and the at least one fixing part 200 and is configured to provide a second restoring force to the at least one second pressure contact part 202 such that the at least one second pressure contact part 202 firmly abuts against the metal support 10. The metal support 10 is connected to the metal cover 60 via the multi-contact spring 20 and is grounded. The overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0033]The metal support 10 is configured to support an electronic component of the mobile terminal 100. The electronic component is for example a dual camera assembly 50. The electronic component includes a first camera lens 52 and a second camera lens 54 arranged side by side with the first camera lens 52, and the first camera lens 52 and the second camera lens 54 are disposed in the accommodating space 11 of the metal support 10. In detail, an image optical axis of the first camera lens 52 and an image optical axis of the second camera lens 54 are parallel such that the first camera lens 52 and the second camera lens 54 can be operated in concert to improve picture taking performance. [0034]In the embodiment, the frame 40 is used to fix the metal support 10. In detail, the wall away from a side of the accommodating space 11 includes a plurality of fixing blocks 104 convexly disposed on the wall. The frame 40 includes a plurality of slots 404 corresponding to the fixing blocks 104 for inserting the fixing blocks 104 such that the metal support 10 is mounted on the frame 40. The fixing blocks 104 of the metal support 10 engage with the slots 404 such that the metal support 10 is securely mounted on the frame 40 to improve structural stability of the mobile terminal. [0035]In the embodiment, the metal cover 60 is attached to the frame 40, and the board 30 is fixed between the metal cover 60 and the frame 40 for covering and protecting the electronic component inside the mobile terminal 100, and thus increasing appearance of the mobile terminal 100. The metal cover 60 may be a metal plate. Further, the metal cover 60 includes two shooting windows, and the first camera lens 52 and the second camera lens 54 take pictures through a respective window of the two shooting windows 62 to realize picture taking. In the embodiment, the shooting window 62 is a camera lens. [0036]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with a ground electrode of the metal cover 60 without changing a mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0037]The foregoing descriptions are merely exemplary embodiments of the present disclosure, rather than limiting the present disclosure. Various modifications and alterations may be made to the present disclosure for a person skilled in the art. Any modification, equivalent substitution, improvement or the like made within the spirit and principle of the present disclosure shall fall into the protection scope of the present disclosure.(String), 相关申请的交叉引用 [0001] 本申请要求于2016年12月20日提交的中国申请第201611185479.6号的优先权。上述申请的全部公开内容以引用的方式整体并入本文。 背景 [0002] 场地 [0003] 本发明涉及电子设备领域,尤其涉及一种用于移动终端的支架组件及具有该支架组件的移动终端。 [0004] 背景 [0005] 智能手机的广泛和不断增长的使用增加了对稳定手机内部电子元件(例如相机设备)的支持的需求。 考虑到支架的刚性、尺寸和安装要求,通常采用金属支架来稳定电子元件。 然而,由于金属具有导电性,金属支架容易干扰手机内部通讯元件的电磁信号,从而降低手机内部通讯元件的通讯性能。 [0006] 在现有技术中,用于稳定手机内部电子元件的金属支架降低了用户体验。 附图的简要说明 [0007] 为了更清楚地说明本发明或相关技术的实施例,下面对实施例中描述的附图进行简单介绍。 显然,附图只是本发明的一些实施例,本领域技术人员可以在不付出任何前提下,根据这些附图获得其他附图。 [0008] 图1是根据本发明实施例的支架组件的组装图。 [0009] 图2是根据本发明实施例的支架组件的分解图。 [0010] 图3A、3B和3C是根据本发明实施例的多触点弹簧的示意图。 [0011] 图4为本发明实施例提供的单板示意图。 [0012] 图5为本发明实施例的金属支架的示意图。 [0013] 图6是根据本发明实施例的框架的示意图。 [0014] 图7是根据本发明实施例的移动终端的部分组装图。 [0015] 图8是根据本发明实施例的移动终端的部分分解图。 图示实施例的详细说明 [0016] 下面结合本发明实施例的附图,对本发明实施例的技术进行详细、完整的描述。 显然,所公开的实施例只是本发明可以使用的一部分实施例,而不是全部的实施例。 基于本发明中所公开的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明实施例保护的范围。 [0017] 参考图1、2和3A至3C,支架组件设置在移动终端中,并且移动终端包括用于接收或发送信号的通信元件。 通信元件可以是板 30 或天线。 支架组件包括金属支架 10 和一个多触点弹簧 20 . 金属支撑 10 被配置为支持移动终端的电子组件。 电子元件例如是双摄像头组件。 多触点弹簧 20 包括至少一个第一压力接触部分 201 ,至少一个第二压力接触部分 202 ,至少一个第一弹性部 203 ,至少一第二弹性部 204 ,以及至少一个固定部 200 . 多触点弹簧 20 固定在一个框架上 40 移动终端通过至少一个固定部 200. 至少一个第一弹性部 203 连接至至少一第一压接部 201 以及至少一固定部 200 并且被配置为向至少一个第一压力接触部分提供第一恢复力 201 使得至少一个第一压力接触部分 201 牢固地靠在金属盖上 60 的移动终端。 至少一第二弹性部 204 连接至至少一第二压接部 202 以及至少一固定部 200 并且被配置为向至少一个第二压力接触部分提供第二恢复力 202 使得至少一第二压接部 202 牢固地紧靠在金属支架上 10 . 金属支撑 10 连接到金属盖 60 通过多触点弹簧 20 并且接地。 框架 40 可以是移动终端的中框,金属盖板 60 可以是移动终端的金属后盖。 在一个实施例中,移动终端可以是手机、笔记本电脑、平板电脑等电子设备。 [0018] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极连通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少,以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0019] 此外,多触点弹簧 20 连接金属支架的电流 10 到金属盖的接地电极 60 . 多触点弹簧 20 一方面可以降低金属支架的整体电势 10 另一方面,金属支架的静电 10 引导至接地电极,以防止金属支架产生静电 10 不流入电子元件,保护电子元件。 接地电极可能是板上裸露的铜 30 . 金属盖 60 正在与董事会沟通 30 , 和第一压力接触部分 201 多触点弹簧 20 紧靠金属盖 60 与电路板的裸露铜进行通信 30 . [0020] 在一个实施例中,所述至少一个固定部 200 包括一个基础件 200 a 有一对长边 2001 和一对短边 2002 连接长边 2001 . 至少一个第一压接部 201 弹性连接到短边 2002 由至少一个第一弹性部 203 , 基础件 200 a 沿长边之一延伸 2001 并弯曲形成连接件 200 b ,以及至少一第二压接部 202 与连接件弹性连接 200 b 由至少一第二弹性部 202 . 在一个实施例中,基件 200 a 是一条长条,一对长边 2001 彼此平行,并且一对短边 2002 彼此平行。 第一压接部分 201 弹性连接到短边的边缘 2002 由第一弹性部分 203 . 第一弹性部分 203 对第一压接部施加弹力 201 ,而当第一个压力接触部分 201受到与第一弹性部提供的弹力方向相反的压力 203 ,第一弹性部分 203 导致第一个压力接触部分 201 牢固地抵靠在第一压力接触部分上的物体上 201 . 在本实施例中,用于对第一压接部施加压力的物体 201 可能是金属盖 60 . 长边之一 2001 基础件 200 a 延伸并弯曲形成连接件 200 b . 连接件 200 b 与底座成一定角度 200 a . 例如连接件 200 b 和基础件 200 a 是相互垂直的。 连接件 200 b 与第二压接部连接 202 和固定部分 200 . 详细地说,第二压接部分 202 与连接件弹性连接 200 b 通过第二弹性部分 204 . 第二弹性部分 204 对第二压接部施加弹力 202 ,而当第二个压力接触部分 202 受到与第二弹性部提供的弹力方向相反的压力 204 , 第二弹性部分 204 导致第二个压力接触部分 202 牢固地抵靠在物体上,从而对第二压力接触部分施加压力 202 . 在本实施例中,用于对第二压接部施加压力的物体 202 可能是金属支架 10 . [0021] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极相通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0022] 进一步地,所述至少一个第一压接部的若干个 201 为二,至少一个第一弹性部的数量 203 为二,各第一压接部 201 弹性连接到短边之一 2002 通过相应的一个第一弹性部分。 两个第一压接件 201 紧靠移动终端的外壳,使得金属支架 10 接地,触点数量增加,金属支架的整体电势 10 减少,并且减少来自通信元件的电磁信号的干扰。 [0023] 参考图3和图4,在本实施例中,支架组件包括紧固件 70 , 基础件 200 a 包括一个固定孔 2003 , 和框架 40 包括一个凸出部分 400 有螺纹孔 402 配置固定多触点弹簧 20 到凸出部分 400 由紧固件 70 . 在一个实施例中,紧固件 70 可能是螺丝。 基础件 200 a 锁定在框架上 40 通过螺钉使多触点弹簧 20 牢固地固定在框架上 40 . 因此,第一压力接触部分 201 可以稳定地抵靠在金属盖上 60 ,第二压力接触部分 202 可以稳定地抵靠在金属支架上 10 ,提高了支架总成的结构稳定性。 [0024] 此外,基础件 200 a 沿着另一个长边延伸 2001弯折形成多个弯折端,弯折端相对于基件的弯折方向 200 a 与连接件的弯曲方向相同 200 b . 弯曲端,基片 200 a , 和连接件 200 b 按顺序连接,基片 200 a 包括由弯曲端之间的区域限定的接收空间,基件 200 a , 和连接件 200 b . 凸出部分 400 框架的 40 容纳在容纳空间中以限制多触点弹簧的旋转 20 . 在另一个实施例中,每个多触点弹簧的弯曲端的数量 20 是两个用于牢固固定多触点弹簧 20 和框架 40 . [0025] 参见图5,在本实施例中,金属支架 10 包括多个侧壁 102 有序连接和容纳空间 11 由侧壁共同定义 102 用于容纳电子元件。 详细来说,金属支架 10 容置电子元件,以方便电子元件的安装和稳定。 电子元件可以是摄像头模块、扬声器、指纹模块、连接器等。 [0026] 此外,金属支撑 10 具有矩形块形状。 金属支撑 10 可由铝合金材料、银材料或铁材料等制成。金属支架 10 是通过使用自动数控铣削工艺对金属块进行成型而形成的。 即,形成侧壁的尺寸 102 采用数控铣削工艺加工,使侧壁的尺寸精度 102 高,能有效稳定电子元件并精确定位,容易校准电子元件的位置。 此外,金属支架 10 也可以有效地固定在外部构件上,使金属支架的固定位置 10 是精确的和金属支持 10 位置方便。 因此,可以准确地改进电子元件的安装位置,并且可以提高电子元件的性能。 容纳空间 11 可以容纳一个电子元件、两个电子元件或多个电子元件,使得金属支架 10 可将多个电子元件集中固定,节省空间。 [0027] 在本实施例中,侧壁 102 包括远离容纳空间一侧的墙壁 11 ,以及压接部(包括第一压接部 201 第二压接部 202 ) 弹性地靠在墙上。 由弹性部(包括第一弹性部)对压接部施加的恢复力 203 和第二弹性部分 204 ) 使压接部分牢固地抵靠在侧壁的壁上 102 金属支架的 10 确保压接部分和金属支架 10 可以稳定接触。 因此,多触点弹簧之间的接触松动 20 和金属支架 10 在使用移动终端时不易发生,提高了移动终端的结构稳定性。 此外,压接部与金属支架的壁弹性接触。 10 便于金属支架的安装和拆卸 10 . 金属支撑 10 只需拉出金属支架即可从移动终端上取下 10 在垂直于压力接触部分靠在侧壁上的方向上 102 . 金属支撑 10 只需预先推动压接部分并放置金属支架即可安装在移动终端上 10 在移动端。 金属支架安装和拆卸的难点 10 降低了。 [0028]参见图6,在本实施例中,支架组件应用于移动终端,金属支架 10 固定在框架上 40 . 详细地,远离容纳空间一侧的墙壁 11 包括多个固定块 104 凸设置在墙上。 框架 40 包括多个插槽 404 对应固定块 104 用于插入固定块 104 这样金属支撑 10 安装在框架上 40 . 固定块 104 金属支架的 10 与插槽啮合 404 这样金属支撑 10 牢固地安装在框架上 40 提高移动终端的结构稳定性。 [0029] 在本实施例中,支架组件包括多个凸接点,凸接点设置于压接部的顶部,凸接点增加压接部与金属支架的接触面积。 10 ,使压接部牢固地抵靠在侧壁上 102 金属支架的 10 . [0030] 在本实施例中,第一压接部 201 ,第二压力接触部分 202 ,第一弹性部分 203 , 第二弹性部分 204 , 和固定部分 200 是通过弯曲金属材料和金属合金材料中的至少一种而一体形成的整体结构。 因此,简化了弹性装置的制造工艺,节省了弹性装置的生产材料。 [0031] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极连通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0032] 参见图7和图8,本发明实施例包括一种移动终端 100 . 移动终端 100 包括金属盖 60 , 董事会 30 , 框架 40 , 和支架组件。 多触点弹簧 20 固定在框架上 40 ,第一压接部抵靠接地金属盖 60 . 董事会 30 包括接地电极。 金属盖 60 连接到电路板 30 . 第二压接部抵靠金属支架 10 将金属支架接地 10 . 多触点弹簧 20 固定在框架上 40 移动终端的 100 由至少一个固定部分 200 . 至少一个第一弹性部 203 连接至至少一第一压接部 201 以及至少一固定部 200 并且被配置为向至少一个第一压力接触部分提供第一恢复力 201 使得至少一个第一压力接触部分 201 紧贴金属盖 60 移动终端的 100 . 至少一第二弹性部 204 连接至至少一第二压接部 202 以及至少一固定部 200 并且被配置为向至少一个第二压力接触部分提供第二恢复力 202 使得至少一第二压接部 202 牢固地紧靠在金属支架上 10 . 金属支撑 10 连接到金属盖 60 通过多触点弹簧 20 并且接地。 金属载体的总电势 10减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0033] 金属支撑 10 用于支持移动终端的电子元件 100 . 电子元件例如是双摄像头组件 50 . 电子元件包括第一相机镜头 52 和第二个相机镜头 54 与第一个相机镜头并排排列 52 , 和第一个相机镜头 52 和第二个相机镜头 54 设置于容置空间内 11 金属支架的 10 . 具体地,第一摄像镜头的图像光轴 52 第二镜头的影像光轴 54 是平行的,使得第一个相机镜头 52 和第二个相机镜头 54 可以协同操作,提高拍照性能。 [0034] 在本实施例中,框架 40 用于固定金属支架 10 . 详细地,远离容纳空间一侧的墙壁 11 包括多个固定块 104 凸设置在墙上。 框架 40 包括多个插槽 404 对应固定块 104 用于插入固定块 104 这样金属支撑 10 安装在框架上 40 . 固定块 104 金属支架的 10 与插槽啮合 404 这样金属支撑 10 牢固地安装在框架上 40 提高移动终端的结构稳定性。 [0035] 在本实施例中,金属罩 60 附在框架上 40 , 和董事会 30 固定在金属盖之间 60 和框架 40 用于覆盖和保护移动终端内部的电子元件 100 ,从而增加移动终端的外观 100 . 金属盖 60 可能是金属板。 此外,金属盖 60 包括两个拍摄窗口和第一个相机镜头 52 和第二个相机镜头 54 通过两个拍摄窗口各自的窗口拍照 62 实现拍照。 在本实施例中,拍摄窗口 62 是相机镜头。 [0036] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极连通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0037] 以上所述仅为本发明的较佳实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,可以对本公开进行各种修改和改变。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106603765A(String), CN106603765B(String), EP3340585A1(String), EP3340585B1(String), ES2729033T3(String), IN201714040209A(String), IN406229B(String), US10165161B2(String), US20180176426A1(String), WO2018113141A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.907 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106603765A(String), CN106603765B(String), EP3340585A1(String), EP3340585B1(String), ES2729033T3(String), IN201714040209A(String), IN406229B(String), US10165161B2(String), US20180176426A1(String), WO2018113141A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.909 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10165161B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.921 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106603765A(String), CN106603765B(String), EP3340585A1(String), EP3340585B1(String), ES2729033T3(String), IN201714040209A(String), IN406229B(String), US10165161B2(String), US20180176426A1(String), WO2018113141A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), CN106603765A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.931 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.932 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), CN106603765B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.943 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), EP3340585A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), EP3340585B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), ES2729033T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), IN201714040209A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), IN406229B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:02.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), US10165161B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), US20180176426A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270701(Integer), WO2018113141A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10165161B2(String), US10165161B2(String), 1545667200(Integer), 270701(Integer), 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185025(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 1(Integer), 185025(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185025(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 2(Integer), 185025(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.056 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.071 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185025(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.078 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.080 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.080 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20070111710A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.081 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Automotive mobile terminal connection system providing mobile terminal function to enable dynamic external user interface(String), 汽车移动终端连接系统提供移动终端功能以启用动态外部用户界面(String), US20070111710A1(String), There is provided a method and device of adapting a phone functionality matrix of an automotive mobile terminal connection device to function capabilities of a mobile terminal device connected to said automotive mobile terminal connection device, comprising the steps of receiving data containing an indication about said function capabilities supported by said mobile terminal device, and rewriting said phone functionality matrix according to said received data.(String), 提供了一种使汽车移动终端连接设备的电话功能矩阵适应连接到所述汽车移动终端连接设备的移动终端设备的功能能力的方法和设备,包括接收包含关于所述功能能力的指示的数据的步骤 由所述移动终端设备支持,并根据所述接收到的数据重写所述电话功能矩阵。(String), US10/570528(String), 1062950400(Integer), US20070111710A1(String), 1179331200(Integer), 美国(String), 2(Integer), 7(Integer), 27(Integer), US20010011033A1 | US20040203636A1 | US20060094455A1 | US20070060111A1 | US20070293258A1 | US5175869A | US5410739A | US5493703A | US5535274A | US5548802A | US5694318A | US5794161A | US5895431A | US5940775A | US6122502A | US6223062B1 | US6226497B1 | US6266544B1 | US6349223B1 | US6449475B1 | US6501949B1 | US6832099B2 | US6892051B2 | US6952576B2 | US7116939B1 | US7257426B1 | US7308289B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.091 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.092 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.092 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185026(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.101 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\69aca674428e4d9aaf9bd004ab8da296.png(String), 185026(Integer), 69aca674428e4d9aaf9bd004ab8da296.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.108 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.109 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.110 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Automotive mobile terminal connection system providing mobile terminal function to enable dynamic external user interface(String), 汽车移动终端连接系统提供移动终端功能以启用动态外部用户界面(String), US20070111710A1(String), There is provided a method and device of adapting a phone functionality matrix of an automotive mobile terminal connection device to function capabilities of a mobile terminal device connected to said automotive mobile terminal connection device, comprising the steps of receiving data containing an indication about said function capabilities supported by said mobile terminal device, and rewriting said phone functionality matrix according to said received data.(String), 提供了一种使汽车移动终端连接设备的电话功能矩阵适应连接到所述汽车移动终端连接设备的移动终端设备的功能能力的方法和设备,包括接收包含关于所述功能能力的指示的数据的步骤 由所述移动终端设备支持,并根据所述接收到的数据重写所述电话功能矩阵。(String), US10/570528(String), 1062950400(Integer), US20070111710A1(String), 1179331200(Integer), 美国(String), 2(Integer), 2(Integer), 7(Integer), 27(Integer), US20010011033A1 | US20040203636A1 | US20060094455A1 | US20070060111A1 | US20070293258A1 | US5175869A | US5410739A | US5493703A | US5535274A | US5548802A | US5694318A | US5794161A | US5895431A | US5940775A | US6122502A | US6223062B1 | US6226497B1 | US6266544B1 | US6349223B1 | US6449475B1 | US6501949B1 | US6832099B2 | US6892051B2 | US6952576B2 | US7116939B1 | US7257426B1 | US7308289B2(String), \20230420\69aca674428e4d9aaf9bd004ab8da296.png(String), 20(Integer), 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.118 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.119 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.120 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.121 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185026(Integer), 1. Method of adapting a phone functionality matrix of an automotive mobile terminal connection device to function capabilities of a mobile terminal device connected to said automotive mobile terminal connection device, comprising: receiving data containing an indication about said function capabilities supported by said mobile terminal device; rewriting said phone functionality matrix according to said received data; and sending said functionality matrix to a central car controller to enable said central car controller to build a user interface corresponding to said functionality matrix. 2. Method according to claim 1, wherein said data containing said indication of said function capabilities is received from a mobile terminal cradle. 3. Method according to claim 1, further comprising requesting said data containing said indication of said function capabilities from said mobile terminal device. 4. Method according to claim 1, wherein said data containing said indication of said function capabilities is received from said mobile terminal device by requesting type and software version thereof. 5. Method according to claim 1, wherein said data containing said indication of said function capabilities is provided to said automotive mobile terminal connection device by said mobile terminal cradle which derives type and software version from said mobile terminal device. 6. (canceled) 7. Software tool comprising program code means stored on a computer readable medium for carrying out the method of claim 1, when said software tool is run on a computer or network device. 8. Computer program product comprising program code means stored on a computer readable medium for carrying out the method of claim 1 when said program product is run on a computer or network device. 9. Computer program product comprising program code, downloadable from a server for carrying out the method of claim 1 when said program product is run on a computer or network device. 10. Computer data signal embodied in a carrier wave and representing a program that instructs a computer to perform the steps of the method of claim 1. 11. Automotive mobile terminal connection device, comprising an interface adapted to connect with a central car controller, a connector adapted to connect with a mobile terminal cradle which is adapted for physically receiving a mobile terminal device, characterized by a phone functionality matrix which comprises an indication of function capabilities of said mobile terminal device. 12. Automotive mobile terminal connection device according to claim 11, adapted to request data from said mobile terminal device, said data containing an indication of said function capabilities. 13. Automotive mobile terminal connection device according to claim 11, adapted to request said data containing said indication about said function capabilities of said mobile terminal device from said mobile terminal cradle. 14. Automotive mobile terminal connection device according to claim 11, adapted to request type and software version of said mobile terminal device. 15. Mobile terminal cradle for physically receiving a mobile terminal device, comprising a connector adapted to connect to an automotive mobile terminal connection device and an interface device adapted to request data from and send data to said mobile terminal device. 16. Mobile terminal cradle according to claim 15, adapted to request data from said mobile terminal device, said data containing an indication about function capabilities of said mobile terminal device. 17. Mobile terminal cradle according to claim 15, comprising a storage containing an indication about said function capabilities of said mobile terminal device. 18. Mobile terminal cradle according to claim 15, further comprising a processor adapted to convert a communication protocol of said mobile terminal device into a communication protocol supported by said automotive mobile terminal connection device. 19. Mobile terminal cradle according to claim 15, further comprising a charger adapted to charge the battery of said mobile terminal. 20. Mobile terminal cradle according to claim 15, adapted to provide a predetermined type of mobile terminal interface to said automotive mobile terminal connection device irrespective of the interface of the connected mobile terminal device.(String), 1.使汽车移动终端连接设备的电话功能矩阵适应与所述汽车移动终端连接设备连接的移动终端设备的功能能力的方法,包括:接收包含关于所述移动终端设备支持的所述功能能力的指示的数据;根据所述接收数据重写所述电话功能矩阵;以及将所述功能矩阵发送到中央汽车控制器,以使所述中央汽车控制器能够建立与所述功能矩阵相对应的用户界面。(String), 1(Integer), 0(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.132 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.133 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185026(Integer), [0001] The present invention relates to an automotive connection system to integrate a mobile phone terminal into the phone control systems of a car. More specifically, it relates to an connection system that is suitable to obtain and provide information about the mobile terminal function capabilities, thereby making it possible to build a corresponding user interface matching the specific features of the mobile terminal. [0002] As mobile terminals like mobile phones and PDAs have become very popular, the desire has aroused to use such terminals in a vehicle environment. Because usually the vehicles driver is the main user of the terminal, the necessity exists to operate the terminal in a kind of handsfree mode. To minimize the risks of using a mobile terminal during driving that are mainly due to the distraction caused by operating a terminal while at the same time controlling the car, different holder devices have been constructed. These range from rather simple mechanical holders, whose only purpose is to place the mobile terminal in an optimal position to the driver, to very sophisticated devices. The latter ones utilize certain internal car systems like the audio system, displays like those belonging to a navigation system, or controls, for example buttons placed on the steering wheel. The speakers of the audio system may so be used for playback purposes, while installed controls may suit to operate the terminal instead of using the terminals own controls. [0003] These common mobile terminal car integration kits suffer from one major drawback that is interoperability. Integrating such kits into a car might be a quite expensive and complicated task. Since they have to be adapted both to the specific type of car and the type of terminal, an obvious problem arises. While the average lifespan of a car may be about 10 years or more, typical product cycles of mobile terminals are much shorter, at best about 1-3 years. Buying a new terminal from the same manufacturer or even from a different manufacturer will most certainly lead to also purchasing a new car integration kit. That is because such kits, the more sophisticated they are, the more likely, they are adapted to both the proprietary communication protocol of the corresponding terminal and the also proprietary communication protocol of the car, or in other words the central car controller. So a new mobile terminal will almost certainly not fit into an already installed integration kit, neither mechanically nor electrically. Since the costs of such a kit are considerably high, installing a new integration kit will not be easily accepted by a user. Neither he may want to accept to be forced to further use a terminal that is far off the state of the art, just to keep the already installed integration kit. [0004] To overcome this drawback, different approaches have been made. One of the easiest ways may be to include only functions in the integration kit that are common to most terminals, like taking a call or hanging up, and using a kind of simple universal holder. Obviously this would give the user only very restricted possibilities to use more sophisticated features of both the terminal and the internal systems of the car. So the logical next step was using kits containing a part specific to a certain car and comprising a universal connector to connect with a terminal specific holder. For each type of mobile terminal a specific holder or cradle has been used which possesses a corresponding universal connector fitting into that of the integration kit. This cradle may be equipped to translate between the car specific part of the kit and the mobile terminal, i.e. converting the communication protocol of one to another. [0005] Though lacking the possibility to make use of more sophisticated features, this may already seem to be a solution to the problem of interoperability. But some details are not yet solved completely satisfactory. A crucial step is to communicate with the mobile terminal by the cradle. As of today, this is done in a kind of passive manner, i.e. that the cradle waits for data sent by the terminal. This could be information about an incoming call or message, or the signal that the user has successfully entered the correct PIN number on the terminal for example. Since types of terminals exist that do not show such a behaviour, i.e. that are not sending information automatically, this method will not work in every possible combination of integration kit and mobile terminal. If the terminal does not automatically send required information to the cradle, the kit will wait forever for needed data. [0006] Also, provided that the car specific part of the kit provides all functionality that the cars control and display systems can offer, certainly not all types of terminal will support all these functions. If the user tries to use one of the functions offered by the kit but not supported by the actual terminal, unwanted reactions may occur. In the best case the kit will send back an error message informing the user that the wanted function is not available with this terminal. Second best would be to simply ignore the user request. In the worst possible case this will lead to a malfunction of the terminal. Anyone of these possibilities is unwanted. If a user tries to use a function that seems to be present to him, he expects that it can be used. He certainly will not understand why a function is offered to him that cannot be used though. With regard to easy understanding of the operation this is quite undesirable and should be avoided at all. [0007] In order to adapt the car specific part of the kit to the special features of the mobile terminal and make the mobile terminal interoperable with systems of the car, information about the function capabilities of the terminal has to be provided. [0008] So obviously, the need for a mobile terminal car connection system exists, that incorporates the advantages already achieved by state of the art devices but avoids the aforementioned drawbacks. The objects of the present invention are thus to provide a mobile terminal car connection system that is completely interoperable with both internal car systems and present or future terminals from the same or even different manufacturers. That means a system that offers all functions to the user that are actually usable in a given combination of car and mobile terminal. And also one that is easily upgradable with minimal costs that may be caused by a change of the mobile terminal used. [0009] To achieve the aforementioned objects, the present invention provides a system for integrating a mobile terminal into the systems of a car, which is adapted to provide mobile terminal capability information to ensure complete interoperability of a given combination of car and mobile terminal. [0010] According to an aspect of the present invention a method is provided to adapt a phone functionality matrix of an automotive mobile terminal connection device to function capabilities supported by a mobile terminal device connected to the automotive mobile terminal connection device. The method comprises the steps of: [0011] receiving data containing an indication about the function capabilities supported by the mobile terminal device; and [0012] rewriting the phone functionality matrix according to the received data. [0013] It is preferred that the data containing an indication about said function capabilities supported by said mobile terminal device is received from a mobile terminal cradle. Since the mobile terminal cradle has to be specifically adapted to a certain type of mobile terminal device, it may also provide the data containing an indication about said function capabilities and thus send that data. [0014] It is preferred that the automotive mobile terminal connection device requests the data from the mobile terminal device. The automotive mobile terminal connection device may easily request that data utilizing for example standard AT commands common to GSM mobile phones. [0015] It is preferred that the data containing an indication of said function capabilities is received from the mobile terminal device by requesting type and software version thereof. Though this may require occasional software upgrades for the automotive mobile terminal connection device this is a way which is easy to implement to determine the function capabilities of the mobile terminal device. [0016] It is preferred that the data containing the indication of the function capabilities is provided to the automotive mobile terminal connection device by the mobile terminal cradle. The cradle derives type and software version from the mobile terminal device. This may especially be useful if a cradle is adapted to several mobile phones belonging to the same series, i.e. having the same bottom connector and interface protocol, but different function capabilities. Thus the cradle has to derive the supported function capabilities from type and software version of the mobile phone actually connected. [0017] It is preferred that the functionality matrix is sent to a central car controller to enable the central car controller to build a user interface corresponding to the functionality matrix. Since the central car controller is aware of the features of systems of the car, like those of controls and display systems for example, it is the device which is responsible for building a user interface. And thus data need to be provided to enable it to adapt this user interface to correspond to the function capabilities of the mobile terminal. [0018] According to another aspect of the present invention, an automotive mobile terminal connection device is provided. The automotive mobile terminal connection device comprises an interface suitable to connect with a central car controller and a connector to connect with a mobile terminal cradle which is adapted for physically receiving a mobile terminal device. It is characterized by a phone functionality matrix which reflects function capabilities of said mobile terminal device. [0019] It is preferred that the automotive mobile terminal connection device is adapted to request data from the mobile terminal device containing an indication of the function capabilities. As 10 described before, utilizing for instance standard GSM AT commands, this would be a flexible way to derive the function capabilities of the mobile terminal device. [0020] It is preferred that the automotive mobile terminal connection device is adapted to request the data containing the indication about the function capabilities of the mobile terminal device from the mobile terminal cradle. As also described before, the mobile terminal cradle would be an ideal location to store or otherwise provide information about the function capabilities of the mobile terminal device. [0021] It is preferred that the automotive mobile terminal connection device is adapted to request type and software version of the mobile terminal device. As described before this is an easy way to derive the function capabilities of the mobile terminal device, even though it has considerable disadvantages. [0022] According to yet another aspect of the present invention a mobile terminal cradle for physically receiving a mobile terminal device is provided. It comprises a connector adapted to connect to an automotive mobile terminal connection device, an interface device adapted to request user data from and send user data to the mobile terminal device. That means the cradle is adapted to actively request user data that may not be automatically provided by the mobile terminal device. This might be information about incoming messages or calls for example. One might also say that the cradle actively supports the communication with the automotive mobile terminal connection device. [0023] It is preferred that the mobile terminal cradle is adapted to request data from the mobile terminal device containing an indication about function capabilities of the mobile terminal device. That means that the cradle is enabled to actively obtain information about the functions supported by the mobile terminal device. This is useful for types of mobile terminals that do not provide such information automatically. [0024] It is preferred that the mobile terminal cradle comprises a storage which contains an indication about the function capabilities of the mobile terminal device. Since the cradle has to be specifically adapted to a certain type of mobile terminal device anyway, it is only logical to store information about the functions supported by that particular mobile terminal device in here. [0025] It is preferred that the mobile terminal cradle comprises a processor adapted to convert a communication protocol of the mobile terminal device into a communication protocol supported by the automotive mobile terminal connection device. That way, different types of mobile terminals may be used with the same automotive mobile terminal connection device, each having its own cradle. The communication protocols of different mobile terminal devices can so be translated to the automotive mobile terminal connection device. [0026] It is preferred that the mobile terminal cradle comprises a charger adapted to charge the battery of the mobile terminal. It should be obvious that is it comfortable to also provide a power source to the terminal which is part of the cradle, instead of a separate charging device. [0027] It is preferred that the mobile terminal cradle is adapted to simulate a predetermined type of mobile terminal device to said automotive mobile terminal connection device. That means, for the automotive mobile terminal connection device it seems as if always the same predetermined type of mobile terminal device is connected to the cradle, regardless of the type of mobile terminal device actually connected. This may be desirable, because thus the adaptation could be made easier, while at the same time losing some level of interoperability. If the type of terminal corresponding to this unified functionality only support few features, some more sophisticated features of the terminal actually connected would be lost. While otherwise, if the terminal actually connected supports less features than the terminal corresponding to the unified functionality the problem of presenting unusable features through the cars system would come up again. In certain circumstances this may though be a useful possibility. [0028] The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the present invention and serve, together with the description, to explain the principles of the invention. In the drawings, [0029]FIG. 1 schematically illustrates an embodiment of the present invention; [0030]FIG. 2 illustrates another embodiment of the present invention; [0031]FIG. 3 illustrates another embodiment of the present invention; and [0032]FIG. 4 illustrates yet another embodiment of the present invention. [0033] In FIG. 1 a mobile terminal car connection system according to the invention is schematically illustrated. A mobile terminal P is electrically connected to a cradle 4, in a bi-directional way, through an interface 12. So the terminal P can send data to be received by the cradle 4, and vice versa. The cradle 4 is connected with an automotive mobile terminal connection device 2. Cradle 4 and automotive mobile terminal connection device 2 are interconnected also in a bi-directional way, through connector 20 being part of the automotive mobile terminal connection device 2, and connector 24 being part of the cradle 4. Those two connectors 20 and 24 are standardized connectors, meaning that every cradle 4 equipped with a connector 24 can be connected to the automotive mobile terminal connection device 2. If the terminal P is a Nokia® mobile terminal, no processing of data received from the terminal P is necessary, because the automotive mobile terminal connection device 2 supports the Nokia® propietary communication protocol. The cradle 4 may optionally contain a processor 14, in case the cradle 4 is adapted for a non-Nokia® mobile terminal. The processor 14 translates data sent by the mobile terminal device P into the Nokia® protocol. In case a Nokia® terminal is connected to the mobile terminal connection device and no processing of data received from the terminal P is necessary and cradle 4 and/or processor 14 are thus not needed, a direct cable connection from automotive terminal connection device 2 to the mobile terminal P can be used. The automotive mobile terminal connection device 2 is bi-directionally connected with a central car controller 18 through an interface 22. The central car controller 18 is connected to an internal car display system 8 and internal car controls 10. Car controls 10 could be control buttons on the steering wheel (as shown in FIG. 2), or control keys of an integrated navigation system or the like. Those are connected bi-directionally with the automotive mobile terminal connection device 2 through central car controller 18 and interface 22, in order to send control commands given through the control keys to be handled by the terminal P and to receive feedback from the terminal P, for instance in order to light an LED in a control key after a function has been switched on. The cradle 4 may optionally include a charger 16, which is adapted to charge the battery of the mobile terminal device P. [0034] In FIG. 2 a typical configuration of the present invention is illustrated. Only the parts that may be visible to the user are shown here, while connections and other parts usually hidden are not shown. A mobile terminal device P is physically received in a cradle 4 and releasably attached thereto. The cradle 4 can be mounted in a position that is suitable, dependant on wether the terminals display and control keys are to be used, and if the terminals speakers or those belonging to the cars audio system will be used. An automotive mobile terminal connection device 2 can be mounted either visibly in a radio mounting slot or the like, or hidden in the glove box for example, provided the necessary connection with the cradle 4 is ensured. The cars radio system R may be utilized to control the terminal P and serve as a replacement of the terminals own display, if the radio system R is suitably equipped. Control buttons 10, for example incorporated into the steering wheel, may suit the purpose of controlling the terminals functions, while a display device 8, being for instance part of the cars navigation system, may also serve to act as a replacement for the terminals display. [0035] In FIG. 3 a possible functionality matrix is shown. In this case said matrix is rather simple, only containing certain features and the information if a mobile terminal can support them or not. It would easily be possible to expand the matrix, for example to give information not only if, but also how or in other words in what way or to what degree certain features are supported by the mobile terminal. For example for the cell “List SMS”, possible entries could then be “in order of receiving”, “in alphabetical order”, “only from persons in the phonebook” and the like. That way, a very fine-tuned matrix could be derived, to be provided to the central car controller in order to build a sophisticated user interface taking advantage of all the advanced features of the mobile terminal. [0036] In FIG. 4 a schematic diagram about second call initiation is illustrated. The automotive mobile terminal connection device 2 and the cradle 4 are shown, also a mobile phone P. Manual dialling on the mobile phone P is possible directly with an active single call or after seperately putting the active call on hold. State changes after user operations on the mobile phone P are only detectable from cyclic checking of the call list (CLCC). [0037] There are two major kinds of data exchanged between the mobile terminal device, the cradle and the automotive mobile terminal connection device of the present invention. On the one hand there is so-called user data. This can be either the contents of an SMS message, information about an incoming call or the like, sent from the mobile terminal device. Or user data that is sent to the mobile terminal device, for example commands like establishing a mobile connection, in other words dialling, changing the ring tone or the like. User data is thus sent in both directions from and to the mobile terminal device. On the other hand there is data containing an indication about functions supported by the mobile terminal. This kind of data is only sent in the direction from the mobile terminal device to the automotive mobile terminal connection device, either automatically or requested by the mobile terminal cradle oder the automotive mobile terminal connection device. [0038] Examples for user data that is either received or has to be requested are: [0039] Indication of entering a PIN number: [0040] The automotive mobile terminal connection device needs information about if the user has already entered his PIN to begin its operation. Some phones (type A) send a message through the bottom connector that the correct PIN number has been entered. Other phone types (type B) make it necessary to request a confirmation about if the PIN has been correctly entered. In the sense of the present invention the automotive mobile terminal connection device for example waits constantly for the confirmation of having entered the PIN. If a phone of type A with a corresponding cradle is installed, the cradle will wait for such corresponding message and send this message (maybe with a correspondingly adapted command) to the automotive mobile terminal connection device. In the case that a phone of type B is installed with the corresponding cradle, the cradle will periodically send a request to the phone, to obtain information if the PIN has been entered. If the phone of type B confirms this, the cradle will send a message indicating this to the automotive mobile terminal connection device. This message is identically to that sent with a phone of type A. [0041] Displaying incoming messages (SMS, MMS, Email and the like): [0042] similar to the aforementioned examples the phone may signal incoming messages and/or output them automatically, or the cradle has to periodically request information about wether a message has come in and relay that information. [0043] Example for user data which has to be requested: [0044] Requesting the phonebook of the mobile phone: [0045] In this case it is provided that the automotive mobile terminal connection device is adapted to display the phonebook through a display system of the car. The output of the phonebook through the bottom connector is different between mobile phones from different manufacturers or even with phones from the same manufacturer belonging to different series. According to the present invention the automotive mobile terminal connection device may for example expect that the phonebook is outputted in an alphabetical order and in a certain format. If the phonebook is sent in alphabetical order by a phone of type A, the corresponding data in principle only has to be relayed to the automotive mobile terminal connection device. If a phone of type B outputs the entries of its phonebook unsorted and in another format, the cradle will have to first sort the data and convert the format, before the data can be send to the automotive mobile terminal connection device. [0046] There are different possibilities for the automotive mobile terminal connection device to obtain the needed information about a terminals function capabilities or features, in order to adapt the functional matrix. The automotive mobile terminal connection device may utilize standard GSM AT commands to request the features of the mobile terminal. This is an elegant and flexible way to obtain that information, since GSM is a widely accepted standard for mobile communication and the AT commands are supported by most of the GSM mobile terminals. Another possible, but certainly not as flexible manner to obtain the needed data could be to request type and software version of the mobile terminal. With this information at hand, the automotive mobile terminal connection device could derive which features are supported performing a kind of database lookup. The obvious disadvantage of such a method is that of necessary software updates for future terminals whose interface and other details are not yet known. Without such updates of the internal database, the automotive mobile terminal connection device would not be able to recognize terminals new to the market. If new terminals are purchased in short periods of time and/or if a larger number of terminals are to be used with the same car, of different family members for example, this can cause unacceptable costs and efforts. Using one of the aforementioned ways, the automotive mobile terminal connection device is used to obtain the features of the mobile terminal by itself. [0047] A different yet also logical approach is to use the cradle to obtain the needed information about the terminals features. Since a cradle has to be adapted specifically to a certain type of terminal, this is a rather obvious solution. The information may either be hardcoded into the cradles circuit, if only one type of terminal is to be used with the cradle. Or for example a cradle suitable for a series of terminals from the same manufacturer with the same mechanical and electrical properties but different features is utilized. In this case there are methods known in the art that can be implemented to enable the cradle to determine the actual type or software version of the terminal and thus store the right list of features. If the terminal uses a standardized connection protocol, like the bluetooth handsfree protocol (HFP) for example, the cradle can derive the needed information about supported features from the kind of connection with the terminal either. Using one of the aforementioned ways, the cradle is used to provide data conatining an indication of the features of the mobile terminal. [0048] The present invention suggests an automotive mobile terminal connection system, adaptable to different mobile terminal devices via a terminal specific cradle connectable to the automotive mobile terminal connection device via a universal connector. So when different persons are using the same car possessing also different mobile terminal devices, each of them may use the connection system by simply utilizing a cradle adapted for his or her type of terminal device. Using future mobile terminal devices is thus possible by only replacing the cradle without the cost-intensive need to replace other parts of or even the whole equipment. The cradle is able to obtain data from the mobile terminal device which is not sent by the mobile terminal by itself. This includes user data as well as data containing an indication of the function capabilities of the mobile terminal device. I.e. the cradle actively supports communication between the automotive mobile terminal connection device and the mobile terminal device. The automotive mobile terminal connection device can adapt a matrix to match the function capabilities of the mobile terminal device, in order to provide this matrix to the central car controller. The central car controller can thus build a corresponding user interface, which offers only functions to the user that are both supported by the mobile terminal device and that can be controlled and/or displayed through one of the cars control or display systems. This eliminates incorrect operation and confusion of the user, and thus increases ease of use and comfort. (String), [0001] 本发明涉及一种将移动电话终端集成到汽车的电话控制系统中的汽车连接系统。 更具体地,它涉及一种连接系统,该连接系统适合于获取和提供关于移动终端功能能力的信息,从而使得构建与移动终端的特定特征相匹配的相应用户界面成为可能。 [0002] 随着移动电话和PDA之类的移动终端变得非常流行,在车辆环境中使用这样的终端的愿望已经产生。 因为通常车辆驾驶员是终端的主要用户,所以存在以一种免提模式操作终端的必要性。 为了尽量减少在驾驶期间使用移动终端的风险(主要是由于在控制汽车的同时操作终端而造成的分心),已经构建了不同的支架设备。 这些范围从相当简单的机械支架(其唯一目的是将移动终端放置在驾驶员的最佳位置)到非常复杂的设备。 后者利用某些内部汽车系统,如音频系统、显示器(如属于导航系统的显示器)或控件,例如放置在方向盘上的按钮。 音频系统的扬声器因此可以用于播放目的,而安装的控件可能适合于操作终端而不是使用终端自己的控件。 [0003] 这些常见的移动终端汽车集成套件存在一个主要缺点,即互操作性。 将此类套件集成到汽车中可能是一项非常昂贵且复杂的任务。 由于它们必须适应特定类型的汽车和终端类型,因此出现了一个明显的问题。 汽车的平均寿命可能约为 10 年或更长,而移动终端的典型产品周期要短得多,充其量只有 1-3 年左右。 从同一制造商或什至不同制造商购买新终端肯定会导致还购买新的汽车集成套件。 这是因为此类套件越复杂,就越有可能同时适应相应终端的专有通信协议和汽车的专有通信协议,或者换句话说,汽车中央控制器。 因此,无论是机械还是电气方面,新的移动终端几乎肯定不会适合已安装的集成套件。 由于这种套件的成本相当高,安装新的集成套件将不容易被用户接受。 他也可能不想被迫进一步使用一个与最先进技术相去甚远的终端,只是为了保留已经安装的集成工具包。 [0004] 为了克服这个缺点,已经采用了不同的方法。 最简单的方法之一可能是在集成套件中只包含大多数终端通用的功能,例如接听电话或挂断电话,并使用一种简单的通用支架。 显然,这会给用户提供非常有限的可能性来使用终端和汽车内部系统的更复杂的功能。 因此,合乎逻辑的下一步是使用包含特定于特定汽车的零件的套件,并包含一个通用连接器以连接到特定于终端的支架。 对于每种类型的移动终端,都使用了特定的支架或支架,它们具有适合集成套件的相应通用连接器。 该支架可以配备成在套件的汽车特定部分和移动终端之间进行转换,即将一种通信协议转换为另一种通信协议。 [0005]尽管无法使用更复杂的功能,但这似乎已经是互操作性问题的解决方案。 但是一些细节还没有完全圆满解决。 一个关键的步骤是通过底座与移动终端通信。 截至目前,这是以一种被动方式完成的,即支架等待终端发送的数据。 例如,这可能是有关来电或消息的信息,或者用户已在终端上成功输入正确 PIN 码的信号。 由于存在不显示此类行为的终端类型,即不会自动发送信息,因此此方法不适用于集成工具包和移动终端的所有可能组合。 如果终端没有自动将所需信息发送到底座,套件将永远等待所需数据。 [0006] 此外,如果套件的汽车特定部分提供汽车控制和显示系统可以提供的所有功能,当然不是所有类型的终端都支持所有这些功能。 如果用户尝试使用套件提供但实际终端不支持的其中一项功能,则可能会出现不需要的反应。 在最好的情况下,该套件将发回一条错误消息,通知用户该终端无法使用所需的功能。 次要的是简单地忽略用户请求。 在最坏的情况下,这将导致终端发生故障。 这些可能性中的任何一种都是不需要的。 如果一个用户试图使用一个似乎存在于他面前的功能,他希望它可以被使用。 他当然不会理解为什么提供给他的功能却不能使用。 就操作的容易理解而言,这是非常不希望的,应该完全避免。 [0007] 为了使套件的汽车特定部分适应移动终端的特殊功能并使移动终端与汽车系统互操作,必须提供有关终端功能的信息。 [0008] 因此,很明显,存在对移动终端汽车连接系统的需求,它结合了现有技术设备已经实现的优点,但避免了上述缺点。 因此,本发明的目的是提供一种移动终端汽车连接系统,该系统可与内部汽车系统以及来自相同或什至不同制造商的现有或未来终端完全互操作。 这意味着一个系统可以为用户提供在给定的汽车和移动终端组合中实际可用的所有功能。 还有一个可以很容易地以最小的成本升级的,这可能是由所使用的移动终端的变化引起的。 [0009] 为实现上述目的,本发明提供了一种将移动终端集成到汽车系统中的系统,其适于提供移动终端能力信息以确保给定的汽车和移动终端组合的完全互操作性。 [0010] 根据本发明的一个方面,提供了一种使汽车移动终端连接设备的电话功能矩阵适应连接到汽车移动终端连接设备的移动终端设备所支持的功能能力的方法。 该方法包括以下步骤: [0011]接收包含关于移动终端设备支持的功能能力的指示的数据; 和[0012] 根据接收到的数据重写电话功能矩阵。 [0013] 优选地,包含关于所述移动终端设备支持的所述功能能力的指示的数据是从移动终端支架接收的。 由于移动终端支架必须专门适配某种类型的移动终端设备,它还可以提供包含关于所述功能能力的指示的数据并因此发送该数据。 [0014] 优选的是,汽车移动终端连接设备请求来自移动终端设备的数据。 汽车移动终端连接设备可以容易地使用例如GSM移动电话通用的标准AT命令来请求数据。 [0015]优选地,通过请求其类型和软件版本从移动终端设备接收包含所述功能能力的指示的数据。 虽然这可能需要偶尔对汽车移动终端连接设备进行软件升级,但这是一种易于实施以确定移动终端设备的功能能力的方式。 [0016] 优选地,包含功能能力指示的数据由移动终端支架提供给汽车移动终端连接装置。 底座从移动终端设备中获取类型和软件版本。 如果一个支架适用于属于同一系列的多个移动电话,即具有相同的底部连接器和接口协议,但具有不同的功能能力,则这可能特别有用。 因此,底座必须从实际连接的手机的类型和软件版本中推导出支持的功能能力。 [0017] 优选地,将功能矩阵发送至汽车中央控制器,以使汽车中央控制器能够建立与功能矩阵相对应的用户界面。 由于汽车中央控制器了解汽车系统的特性,例如控制和显示系统的特性,因此它是负责构建用户界面的设备。 因此需要提供数据以使其能够适配该用户界面以对应于移动终端的功能能力。 [0018] 根据本发明的另一方面,提供了一种车载移动终端连接装置。 该车载移动终端连接装置包括适于与汽车中央控制器连接的接口和用于与适于物理接收移动终端设备的移动终端支架连接的连接器。 其特征在于反映所述移动终端设备的功能能力的电话功能矩阵。 [0019] 优选地,汽车移动终端连接设备适于从移动终端设备请求包含功能能力的指示的数据。 作为 10 如前所述,利用例如标准GSM AT命令,这将是获得移动终端设备的功能能力的灵活方式。 [0020] 优选地,汽车移动终端连接设备适于从移动终端支架请求包含关于移动终端设备的功能能力的指示的数据。 同样如前所述,移动终端支架将是存储或以其他方式提供关于移动终端设备的功能能力的信息的理想位置。 [0021] 优选地,车载移动终端连接装置适合请求移动终端装置的类型和软件版本。 如前所述,这是获得移动终端设备的功能能力的简单方法,尽管它具有相当大的缺点。 [0022] 根据本发明的又一方面,提供了一种用于物理地接收移动终端设备的移动终端支架。 它包括适于连接到汽车移动终端连接设备的连接器、适于向移动终端设备请求用户数据和向移动终端设备发送用户数据的接口设备。 这意味着支架适于主动请求可能不会由移动终端设备自动提供的用户数据。 例如,这可能是有关传入消息或呼叫的信息。 也可以说,通讯座主动支持与车载移动终端连接设备的通信。 [0023] 优选地,移动终端支架适于从移动终端设备请求包含关于移动终端设备的功能能力的指示的数据。 也就是说,使通讯座能够主动获取移动终端设备支持的功能信息。 这对于不自动提供此类信息的移动终端类型很有用。 [0024]优选地,移动终端支架包括存储器,该存储器包含关于移动终端设备的功能能力的指示。 由于底座无论如何都必须专门适配某种类型的移动终端设备,因此将关于该特定移动终端设备所支持的功能的信息存储在此处是合乎逻辑的。 [0025] 优选地,移动终端支架包括适于将移动终端设备的通信协议转换成汽车移动终端连接设备支持的通信协议的处理器。 这样,不同类型的移动终端可以与相同的汽车移动终端连接设备一起使用,每个移动终端都有自己的支架。 不同移动终端设备的通信协议可以这样转换到汽车移动终端连接设备。 [0026] 优选地,移动终端支架包括适于为移动终端的电池充电的充电器。 显而易见的是,还为作为支架一部分的终端而不是单独的充电设备提供电源是舒适的。 [0027] 优选地,移动终端支架适于模拟预定类型的移动终端设备到所述汽车移动终端连接设备。 这意味着,对于汽车移动终端连接装置而言,似乎总是相同的预定类型的移动终端装置连接到托架,而不管实际连接的移动终端装置的类型如何。 这可能是可取的,因为这样可以使适应更容易,同时失去一定程度的互操作性。 如果这种统一功能对应的终端类型只支持很少的特性,那么实际连接的终端的一些更复杂的特性就会丢失。 反之,如果实际连接的终端支持的特性比统一功能对应的终端少,又会出现无法通过车载系统呈现不可用特性的问题。 在某些情况下,这可能是一种有用的可能性。 [0028] 附图被包括以提供对本发明的进一步理解并且并入并构成本说明书的一部分。 附图图示了本发明的实施例并且与描述一起用于解释本发明的原理。 在图纸中, [0029] 图1示意性地说明了本发明的一个实施例; [0030] 图2说明本发明的另一个实施例; [0031] 图3说明本发明的另一个实施例; 和 [0032] 图4示出了本发明的又一实施例。 [0033] 在图1中示意性地图示了根据本发明的移动终端汽车连接系统。 移动终端P与通讯座电连接 4 ,以双向方式,通过一个接口 12 . 所以终端P可以发送数据给cradle接收 4 ,反之亦然。 摇篮 4 与车载移动终端连接装置连接 2 . 摇篮 4 与车载移动终端连接装置 2 也通过连接器以双向方式互连 20 作为汽车移动终端连接装置的一部分 2 , 和连接器 24 成为摇篮的一部分 4 . 那两个连接器 20 和 24 是标准化的连接器,这意味着每个通讯座 4 配备连接器 24 可连接车载移动终端连接设备 2 . 如果终端 P 是诺基亚移动终端,则不需要对从终端 P 接收到的数据进行处理,因为汽车移动终端连接设备 2 支持诺基亚专有的通信协议。 摇篮 4 可以选择包含一个处理器 14 , 以防摇篮 4 适用于非 Nokia® 移动终端。 处理器 14将移动终端设备 P 发送的数据转换为 Nokia® 协议。 如果 Nokia® 终端连接到移动终端连接设备并且不需要处理从终端 P 接收到的数据并且底座 4 和/或处理器 14 因此不需要,从汽车终端连接设备的直接电缆连接 2 可以使用到移动终端P。 车载移动终端连接装置 2 与中央汽车控制器双向连接 18 通过一个界面 22 . 中央轿厢控制器 18 连接到内部汽车显示系统 8 和内部汽车控制 10 . 汽车控制 10 可以是方向盘上的控制按钮(如图2所示),也可以是集成导航系统的控制键等。 与车载移动终端连接装置双向连接 2 通过中央轿厢控制器 18 和界面 22 ,以便发送通过控制键给出的控制命令,由终端 P 处理并接收来自终端 P 的反馈,例如,为了在打开功能后点亮控制键中的 LED。 摇篮 4 可以选择包括一个充电器 16 ,适用于为移动终端设备P的电池充电。 [0034] 在图2中说明了本发明的典型配置。 此处仅显示用户可能可见的部分,而未显示连接和其他通常隐藏的部分。 移动终端设备 P 被物理地接收在支架中 4 并可释放地附在其上。 摇篮 4 可以安装在合适的位置,具体取决于是否使用终端显示器和控制键,以及是否使用终端扬声器或属于汽车音响系统的扬声器。 一种车载移动终端连接装置 2 可以明显地安装在无线电安装槽等中,或者隐藏在手套箱中,例如,提供与支架的必要连接 4 得到保证。 汽车无线电系统R可用于控制终端P并用作终端自身显示器的替代,如果无线电系统R被适当装备的话。 控制按钮 10 ,例如并入方向盘,可能适合控制终端功能的目的,而显示设备 8 ,例如作为汽车导航系统的一部分,也可以作为终端显示器的替代品。 [0035] 在图3中,示出了可能的功能矩阵。 在这种情况下,所述矩阵相当简单,仅包含某些特征以及移动终端是否支持这些特征的信息。 可以很容易地扩展矩阵,例如不仅给出信息,而且给出移动终端支持某些特征的方式或方式或程度的信息。 例如对于单元格“List SMS”,可能的条目可以是“按接收顺序”、“按字母顺序”、“仅来自电话簿中的人”等。 这样,可以导出一个非常精细的矩阵,提供给汽车中央控制器,以便利用移动终端的所有高级功能构建复杂的用户界面。 [0036] 在图4中示出了关于发起第二呼叫的示意图。 车载移动终端连接装置 2 和摇篮 4 还显示了移动电话 P。在移动电话 P 上手动拨号可以直接使用活动的单个呼叫或在单独保持活动呼叫之后。 用户在移动电话 P 上操作后的状态变化只能通过循环检查呼叫列表 (CLCC) 来检测。 [0037]本发明的移动终端装置、支架与车载移动终端连接装置之间交换的数据主要有两种。 一方面是所谓的用户数据。 这可以是从移动终端设备发送的 SMS 消息的内容、关于来电的信息等。 或者发送到移动终端设备的用户数据,例如像建立移动连接的命令,换言之拨号、改变铃声等。 用户数据因此从移动终端设备双向发送和发送到移动终端设备。 另一方面,存在包含关于移动终端支持的功能的指示的数据。 这种数据仅在从移动终端设备到汽车移动终端连接设备的方向上自动发送或由汽车移动终端连接设备上的移动终端支架请求发送。 [0038] 已接收或必须请求的用户数据示例如下: [0039] 输入 PIN 码的指示:[0040] 汽车移动终端连接设备需要有关用户是否已经输入其 PIN 以开始其操作的信息。 某些电话(A 型)通过底部连接器发送一条消息,表明已输入正确的 PIN 码。 其他电话类型(B 类)需要请求确认是否已正确输入 PIN。 在本发明的意义上,汽车移动终端连接设备例如不断地等待输入PIN的确认。 如果安装了具有相应底座的类型A电话,则底座将等待这样的相应消息并将该消息(可能带有相应适配的命令)发送到汽车移动终端连接设备。 如果B型手机安装了相应的底座,则底座会定期向手机发送请求,以获取输入PIN码后的信息。 如果 B 型电话确认了这一点,则通讯座将向汽车移动终端连接设备发送一条消息,表明这一点。 此消息与使用 A 型电话发送的消息相同。[0041] 显示传入消息(短信、彩信、电子邮件等):[0042] 与上述示例类似,电话可能会发出传入消息的信号和/或自动输出它们,或者底座必须定期请求有关消息是否已传入的信息并转发该信息。[0043] 必须请求的用户数据示例:[0044] 查询手机电话本:[0045] 在这种情况下,汽车移动终端连接设备适合于通过汽车的显示系统显示电话簿。 不同厂商的手机甚至同一厂商不同系列的手机通过底部连接器输出的电话本是不同的。 根据本发明,汽车移动终端连接设备可以例如期望电话簿以字母顺序和特定格式输出。 如果A型电话按字母顺序发送电话簿,则原则上只需要将相应的数据中继到汽车移动终端连接设备即可。 如果B型电话以另一种格式未排序地输出其电话簿条目,则通讯座必须先对数据进行排序并转换格式,然后才能将数据发送到汽车移动终端连接设备。 [0046] 汽车移动终端连接设备有不同的可能性来获得关于终端功能能力或特性的所需信息,以便适配功能矩阵。 汽车移动终端连接装置可以利用标准GSM AT命令来请求移动终端的特征。 这是获取该信息的一种优雅而灵活的方式,因为 GSM 是广泛接受的移动通信标准,并且大多数 GSM 移动终端都支持 AT 命令。 另一种可能但肯定不那么灵活的获取所需数据的方式可能是请求移动终端的类型和软件版本。 有了手头的这些信息,汽车移动终端连接设备可以推导出支持哪些特征来执行一种数据库查找。 这种方法的明显缺点是需要为未来的终端进行必要的软件更新,而这些终端的界面和其他细节尚不清楚。 如果内部数据库没有这种更新,汽车移动终端连接设备将无法识别市场上的新终端。 如果在短时间内购买新终端和/或如果大量终端要用于同一辆车,例如不同家庭成员,这可能会导致不可接受的成本和工作量。 采用上述方式之一,利用车载移动终端连接装置自行获取移动终端的特征。 [0047] 一种不同但同样合乎逻辑的方法是使用通讯座获取有关终端功能的所需信息。 由于支架必须专门适应特定类型的终端,因此这是一个相当明显的解决方案。 如果只有一种类型的终端要与支架一起使用,则该信息可以硬编码到支架电路中。 或者例如适用于来自同一制造商的具有相同机械和电气特性但具有不同特征的一系列终端的支架。 在这种情况下,存在可以实施的本领域已知的方法以使支架能够确定终端的实际类型或软件版本并因此存储正确的特征列表。 如果终端使用标准化连接协议,例如蓝牙免提协议 (HFP),则底座也可以从与终端的连接类型中获取有关支持功能的所需信息。 使用前述方式之一,支架用于提供包含移动终端的特征的指示的数据。 [0048]本发明提出了一种汽车移动终端连接系统,通过可通过通用连接器连接到汽车移动终端连接设备的终端专用支架适用于不同的移动终端设备。 因此,当不同的人使用同样拥有不同移动终端设备的同一辆车时,他们中的每个人都可以通过简单地利用适合他或她的终端设备类型的支架来使用连接系统。 因此,仅需更换支架即可使用未来的移动终端设备,而无需更换设备的其他部分甚至整个设备,成本高昂。 底座能够从移动终端设备获取非移动终端自身发送的数据。 这包括用户数据以及包含移动终端设备的功能能力的指示的数据。 IE。 通讯座主动支持车载移动终端连接设备与移动终端设备之间的通信。 汽车移动终端连接设备可以适配一个矩阵来匹配移动终端设备的功能能力,以将该矩阵提供给汽车中央控制器。 中央汽车控制器因此可以建立相应的用户界面,其仅向用户提供移动终端设备支持的并且可以通过汽车控制或显示系统之一控制和/或显示的功能。 这消除了用户的不正确操作和混淆,从而增加了易用性和舒适性。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.148 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.148 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.148 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AT471058T(String), AU2003259428A1(String), CN100481848C(String), CN1839639A(String), DE60332970D1(String), DE60332970T2(String), EP1665845A1(String), EP1665845B1(String), US20070111710A1(String), WO2005025256A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.149 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.150 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AT471058T(String), AU2003259428A1(String), CN100481848C(String), CN1839639A(String), DE60332970D1(String), DE60332970T2(String), EP1665845A1(String), EP1665845B1(String), US20070111710A1(String), WO2005025256A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20070111710A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.158 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AT471058T(String), AU2003259428A1(String), CN100481848C(String), CN1839639A(String), DE60332970D1(String), DE60332970T2(String), EP1665845A1(String), EP1665845B1(String), US20070111710A1(String), WO2005025256A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.159 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.160 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), AT471058T(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), AU2003259428A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.175 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), CN100481848C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.183 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.183 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.183 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), CN1839639A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.190 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.190 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.190 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), DE60332970D1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), DE60332970T2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), EP1665845A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), EP1665845B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), US20070111710A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270702(Integer), WO2005025256A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.262 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20070111710A1(String), US20070111710A1(String), 1179331200(Integer), 270702(Integer), 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.273 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: NOKIA CORPORATION(String), PIETRUSZKA, JORG(String), SPILKER, JOCHEN(String), HANEBRINK, THOMAS(String), 诺基亚公司(String), PIETRUSZKA JORG(String), SPILKER JOCHEN(String), HANEBRINK THOMAS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: NOKIA CORPORATION(String), 诺基亚公司(String), 255(String), 0(Integer), 1681975546(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.276 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185026(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75925(Integer), 1(Integer), 185026(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: PIETRUSZKA, JORG(String), PIETRUSZKA JORG(String), 0(Integer), 1681975563(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.298 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SPILKER, JOCHEN(String), SPILKER JOCHEN(String), 0(Integer), 1681975563(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HANEBRINK, THOMAS(String), HANEBRINK THOMAS(String), 0(Integer), 1681975563(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185026(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75950(Integer), 2(Integer), 185026(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75951(Integer), 2(Integer), 185026(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75952(Integer), 2(Integer), 185026(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.362 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.363 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.363 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185026(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.371 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.372 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.373 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8145270B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Smart card and method for generating response message to be delivered to mobile terminal supporting mobile broadcast, and mobile terminal therefor(String), 用于生成响应消息以传递给支持移动广播的移动终端的智能卡和方法及其移动终端(String), US8145270B2(String), Provided is a method of efficiently processing a Short-Term Key Message (STKM) in the mobile broadcast supporting the mobile terminal. A structure of a response message according to processing the STKM in the smart card is also provided. In particular, a variety of information necessary for reproducing in the player is included in the response message and delivered to the mobile terminal, thereby the mobile terminal can easily obtain the desired information through the response message. Therefore, when the STKM is processed in the mobile terminal, there is no need to process operations except for a resending check, and the information does not need to be stored separately.(String), 提供了一种在支持移动终端的移动广播中有效处理短期密钥消息(STKM)的方法。 还提供了根据处理智能卡中的STKM的响应消息的结构。 特别地,在响应消息中包含播放器中再现所需的各种信息并传递给移动终端,从而移动终端可以通过响应消息容易地获得所需的信息。 因此,在移动终端处理STKM时,除了重发校验外,不需要其他操作,也不需要单独存储信息。(String), US12/260692(String), 1225209600(Integer), US8145270B2(String), 1332777600(Integer), 1332777600(Integer), 美国(String), 4(Integer), KR(String), 3(Integer), 7(Integer), KR100748470B1 | KR1020060031848A | KR1020070089027A | US20090316911A1 | US20100027787A1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.385 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185027(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\1b6278e32f1d451f9636971757b8f3c1.png(String), 185027(Integer), 1b6278e32f1d451f9636971757b8f3c1.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.396 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Smart card and method for generating response message to be delivered to mobile terminal supporting mobile broadcast, and mobile terminal therefor(String), 用于生成响应消息以传递给支持移动广播的移动终端的智能卡和方法及其移动终端(String), US8145270B2(String), Provided is a method of efficiently processing a Short-Term Key Message (STKM) in the mobile broadcast supporting the mobile terminal. A structure of a response message according to processing the STKM in the smart card is also provided. In particular, a variety of information necessary for reproducing in the player is included in the response message and delivered to the mobile terminal, thereby the mobile terminal can easily obtain the desired information through the response message. Therefore, when the STKM is processed in the mobile terminal, there is no need to process operations except for a resending check, and the information does not need to be stored separately.(String), 提供了一种在支持移动终端的移动广播中有效处理短期密钥消息(STKM)的方法。 还提供了根据处理智能卡中的STKM的响应消息的结构。 特别地,在响应消息中包含播放器中再现所需的各种信息并传递给移动终端,从而移动终端可以通过响应消息容易地获得所需的信息。 因此,在移动终端处理STKM时,除了重发校验外,不需要其他操作,也不需要单独存储信息。(String), US12/260692(String), 1225209600(Integer), US8145270B2(String), 1332777600(Integer), 1332777600(Integer), 美国(String), 2(Integer), 4(Integer), KR(String), 3(Integer), 7(Integer), KR100748470B1 | KR1020060031848A | KR1020070089027A | US20090316911A1 | US20100027787A1(String), \20230420\1b6278e32f1d451f9636971757b8f3c1.png(String), 12(Integer), 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.406 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.406 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.407 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 1. A smart card which is inserted into a mobile terminal supporting mobile broadcast, and which generates a response message according to a short-term key message process, the smart card comprising:an information extraction unit for, when a Short-Term Key Message (STKM) is delivered from the mobile terminal, extracting information necessary for decrypting and reproducing broadcast service data from the STKM; anda response message generation unit for generating a response message including the extracted information and for delivering the response message to the mobile terminal.(String), 1.一种智能卡,插入支持移动广播的移动终端,根据短时密钥消息过程产生响应消息,该智能卡包括:信息提取单元,用于当从移动终端传送短期密钥消息(STKM)时,从STKM提取解密和再现广播服务数据所需的信息;和响应消息生成单元,用于生成包括提取的信息的响应消息,并将该响应消息传递给移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 2. The smart card as claimed in claim 1, wherein the response message comprises:a tag field for indicating a response message on a Multimedia Broadcast/Multicast Service (MBMS) operation;a field for indicating an entire length of the response message;a field for indicating that the MBMS operation is successful; anda field to be inserted with the extracted information.(String), 2.如权利要求1所述的智能卡,其中响应消息包括:用于指示关于多媒体广播/多播服务(MBMS)操作的响应消息的标签字段;用于指示响应消息的整个长度的字段;MBMS操作成功字段;和要插入提取信息的字段。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 3. The smart card as claimed in claim 2, wherein the field to be inserted with the extracted information comprises:a field for indicating a sum of length of the extracted information;a field for identifying an MBMS Traffic Key (MTK);a field for indicating an actual MTK;a field for indicating whether the Traffic Encryption Key (TEK) is decrypted with the Terminal Binding Key (TBK);a field for indicating whether a Message Authentication Code (MAC) portion is included when the broadcast service data is received; anda field for indicating a traffic key lifetime.(String), 3.如权利要求2所述的智能卡,其中要插入提取信息的字段包括:字段,表示提取信息的长度总和;用于标识MBMS流量密钥(MTK)的字段;用于指示实际MTK的字段;用于指示流量加密密钥(TEK)是否被终端绑定密钥(TBK)解密的字段;用于指示在接收到广播服务数据时是否包括消息认证码(MAC)部分的字段;和用于指示流量密钥生命周期的字段。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 4. The smart card as claimed in claim 3, wherein the field to be inserted with the extracted information further comprises a field for indicating a length of a salt key when the salt key is available, and a field for indicating an actual salt key.(String), 4.如权利要求3所述的智能卡,其中待插入提取信息的字段还包括用于指示saltkey可用时的saltkey长度的字段,以及用于指示实际saltkey的字段。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 5. The smart card as claimed in claim 1, wherein the smart card comprises a Universal Subscriber Identity Module (USIM).(String), 5.如权利要求1所述的智能卡,其中智能卡包括通用用户识别模块(USIM)。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.408 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 6. The smart card as claimed in claim 1, wherein the response message indicates a result of processing the short-term key message of the smart card in accordance with a Generic Bootstrapping Architecture (GBA)_Universal Subscriber Identity Module (USIM) (GBA_U) scheme.(String), 6.如权利要求1所述的智能卡,其中响应消息指示根据通用自举架构(GBA)_通用用户识别模块(USIM)(GBA_U)方案处理智能卡的短期密钥消息的结果。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 7. A mobile terminal into which a smart card is inserted and which processes a short-term key message, the mobile terminal comprising:a receiving unit for receiving a Short-Term Key Message (STKM) over a broadcast network;a resending check unit for determining whether the received short-term key message is a new short-term key message, and delivering the received STKM to the smart card when the received STKM is a new STKM; anda decryption unit for obtaining information necessary for decrypting and reproducing broadcast service data from the response message by parsing the delivered response message when a response message is delivered from the smart card in response to delivery of the STKM.(String), 7.一种插入智能卡并处理短期密钥消息的移动终端,该移动终端包括:用于通过广播网络接收短期密钥消息(STKM)的接收单元;重发校验单元,用于判断接收到的短期密钥消息是否为新的短期密钥消息,当接收到的STKM为新的STKM时,将接收到的STKM传递给智能卡;和解密单元,用于在响应于STKM的传递从智能卡传递响应消息时,通过解析传递的响应消息,从响应消息中获取解密和再现广播服务数据所需的信息。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 8. The mobile terminal as claimed in claim 7, wherein the response message comprises:a tag field for indicating a response message on a Multimedia Broadcast/Multicast Service (MBMS) operation;a field for indicating an entire length of the response message;a field for indicating that the MBMS operation is successful; anda field to be inserted with information necessary for decrypting and reproducing the broadcast service data.(String), 8.如权利要求7所述的移动终端,其中响应消息包括:用于指示关于多媒体广播/多播服务(MBMS)操作的响应消息的标签字段;用于指示响应消息的整个长度的字段;MBMS操作成功字段;和将插入解密和再现广播服务数据所需的信息的字段。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 9. The mobile terminal as claimed in claim 7, wherein the information necessary for decrypting and reproducing the broadcast service data comprises at least one of:an MBMS traffic key IDentification (ID) for identifying an MBMS Traffic Key (MTK);MTK data;a terminal binding flag value for indicating whether a Traffic Encryption Key (TEK) must be decrypted with a Terminal Binding Key (TBK);a traffic authorization flag value for indicating whether a Message Authentication Code (MAC) portion is included when the broadcast service data is received; anda traffic key lifetime.(String), 9.如权利要求7所述的移动终端,其中解密和再现广播服务数据所需的信息至少包括以下之一:MBMSTrafficKeyIDentification(ID),用于识别MBMSTrafficKey(MTK);联发科数据;终端绑定标志值,用于指示流量加密密钥(TEK)是否必须用终端绑定密钥(TBK)解密;流量授权标志值,用于指示接收广播业务数据时是否包含消息认证码(MAC)部分;和交通密钥的生命周期。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 10. A method of generating a response message to be delivered to a mobile terminal supporting mobile broadcast in a smart card, the method comprising the steps of:receiving a Short-Term Key Message (STKM) from the mobile terminal;extracting information necessary for decrypting and reproducing broadcast service data from the STKM;generating a response message including the extracted information; anddelivering the response message to the mobile terminal.(String), 10.一种在智能卡中生成要传递给支持移动广播的移动终端的响应消息的方法,该方法包括步骤:从移动终端接收短期密钥消息(STKM);从STKM中提取解密和再现广播服务数据所需的信息;生成包括提取的信息的响应消息;和将响应消息传递给移动终端。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 11. The method as claimed in claim 10, wherein the response message comprises:a tag field for indicating a response message for a Multimedia Broadcast/Multicast Service (MBMS) operation;a field for indicating an entire length of the response message;a field for indicating that the MBMS operation is successful; anda field to be inserted with the extracted information.(String), 11.如权利要求10所述的方法,其中响应消息包括:用于指示多媒体广播/多播服务(MBMS)操作的响应消息的标签字段;用于指示响应消息的整个长度的字段;MBMS操作成功字段;和要插入提取信息的字段。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185027(Integer), 12. The method as claimed in claim 11, wherein the field to be inserted with the extracted information comprises:a field for indicating a sum of length of the extracted information;a field for identifying an MTK;a field for indicating an actual MTK;a field for indicating whether a TEK must be decrypted with a TBK;a field for indicating whether a Message Authentication Code (MAC) portion is included when the broadcast service data is received; anda field for indicating a traffic key lifetime.(String), 12.如权利要求11所述的方法,其中要插入提取信息的字段包括:字段,表示提取信息的长度总和;用于识别MTK的字段;用于指示实际MTK的字段;用于指示TEK是否必须用TBK解密的字段;用于指示在接收到广播服务数据时是否包括消息认证码(MAC)部分的字段;和用于指示流量密钥生命周期的字段。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.509 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.510 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185027(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to an application entitled “Smart Card and Method for Generating Response Message to be Delivered to Mobile Terminal Supporting Mobile Broadcast, and Mobile Terminal therefor” filed in the Korean Industrial Property Office on Nov. 29, 2007 and assigned Serial No. 2007-122969, the contents of which are hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile broadcast system, and more particularly to a method of processing a short-term key message in a terminal supporting mobile broadcast, and a terminal therefor. [0004]2. Description of the Related Art [0005]The Open Mobile Alliance (OMA) group researches standards for interworking among individual mobile solutions, and specifies two profiles as a broadcast standard established to be used appropriately for broadcast environment. One of the profiles is a Digital Rights Management (DRM) profile, and the other is a smart card profile. In the smart card profile, a video/audio stream encrypted with specific keys is transmitted to a terminal over a broadcast network. Further, a data stream having keys necessary for decrypting the encrypted video/audio stream is also transmitted to the mobile terminal over the same broadcast network, which is referred to as a Short-Term Key Message (STKM). [0006]In the smart card profile, the received STKM is subjected to a resending check by a Multimedia Internet KEYing (MIKEY) parser in the mobile terminal. Here, a Multimedia Broadcast/Multicast Service (MBMS) Traffic Key (MTK) included in the STKM is changed once every several seconds or minutes, and the STKM is transmitted every 0.5 seconds or every several seconds, thereby causing the mobile terminal to receive the same STKM several times or several tens of times until the key is updated once. Continuously performing a parsing and a key decryption every time the STKM is received results in a waste of mobile terminal resources. Therefore, as a method of reducing this resource waste, a resending check is essential. [0007]For the resending check, the STKM to be transmitted in a MIKEY message structure is used in the smart card profile. The MIKEY message structure is described as shown in FIG. 1 and the MTK is formatted by a simple binary encoding method, such as the MIKEY, in order to be transmitted. In particular, as a decision reference for the resending check, an MTK IDentification (ID) included in an MBMS EXT (Extension) 100 field in FIG. 1 is used. [0008]A procedure of the resending check will now be described with reference to FIG. 2. FIG. 2 shows an operational flowchart of a mobile terminal for a conventional resending check. [0009]Referring to FIG. 2, the mobile terminal determines whether an STKM is received, in step 200. If the STKM is received, the mobile terminal performs the resending check in step 205, and determines whether the received STKM is a new STKM in step 210. If the received STKM is not a new STKM, the mobile terminal goes to step 215 and discards the received STKM. If the received STKM is a new message, a parsing and key decryption process is performed on the mobile terminal or the smart card according to a location of a secure function. The process is classified into a Generic Bootstrapping Architecture (GBA)-Mobile Equipment (ME) (GBA_ME) scheme or a GBA_Universal Subscriber Identity Module (USIM) (GBA_U) scheme according to whether a location for processing the STKM in the smart card profile is a mobile terminal or a USIM, i.e., a smart card. In the GBA_U scheme, the STKM is delivered to a USIM by an Application Protocol Data Unit (APDU) command, and then the parsing and key decryption process is performed within the USIM. Then, the MTK or a Traffic Encryption Key (TEK) included in the STKM is delivered again to the mobile terminal. [0010]At this time, when a separate MIKEY parser is included in the mobile terminal for analyzing the STKM, the mobile terminal analyzes the MIKEY and stores the result information according to the analysis by performing the parsing operation, in step 220. Thereafter, the mobile terminal determines whether a response message is received from the USIM, in step 225. When the response message is received, the mobile terminal obtains the TEK by parsing the response message, in step 230. Subsequently, the mobile terminal delivers the stored result information and the TEK to a player, in step 235. [0011]In the player, a variety of information is required for reproducing a video/audio stream. However, in the case of the GBA_U scheme, a variety of information is included in the STKM, but the USIM delivers the only TEK. Therefore, since the mobile terminal must perform the parsing operation by using the separate MIKEY parser and have the values in a memory, the parsing operation causes memory and resources in the mobile terminal to be wasted. Moreover, independently from the parsing and key decryption procedure within the USIM, redundant operations are unnecessarily performed in the mobile terminal by analyzing the MIKEY and by analyzing the result information, which increases the load on the mobile terminal. SUMMARY OF THE INVENTION [0012]Accordingly, the present invention has been made to solve the above-mentioned problems occurring in the prior art, and the present invention provides a smart card and a method for generating a response message to be delivered to a mobile terminal supporting mobile broadcast in order to smoothly perform memory management and resource management in the mobile terminal, and provides a mobile terminal therefor. [0013]Also, the present invention provides a smart card and a method for generating a response message to be delivered to a mobile terminal supporting mobile broadcast, avoiding redundant operations of a USIM in the mobile terminal, and provides a mobile terminal therefor. [0014]In accordance with an aspect of the present invention, there is provided a smart card which is inserted into a mobile terminal supporting mobile broadcast and which generates a response message according to short-term key message processing, the smart card including an information extraction unit for, when a Short-Term Key Message (STKM) is delivered from the mobile terminal, extracting information necessary for decrypting and reproducing broadcast service data from the STKM; and a response message generation unit for generating a response message including the extracted information and for delivering the response message to the mobile terminal. [0015]In accordance with another aspect of the present invention, there is provided a mobile terminal into which a smart card is inserted and which processes a short-term key message, the mobile terminal including a receiving unit for receiving a Short-Term Key Message (STKM) over a broadcast network; a resending check unit for determining whether the received short-term key message is a new short-term key message, and delivering the received short-term key message to the smart card when the received short-term key message is a new short-term key message; and a decryption unit for obtaining information necessary for decrypting and reproducing broadcast service data from the response message by parsing the delivered response message when a response message is delivered from the smart card in response to delivery of the short-term key message. [0016]In accordance with another aspect of the present invention, there is provided a method of generating a response message to be delivered to a mobile terminal supporting mobile broadcast in a smart card, the method including receiving a Short-Term Key Message (STKM) from the mobile terminal; extracting information necessary for decrypting and reproducing broadcast service data from the short-term key message; generating a response message including the extracted information; and delivering the response message to the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 is a diagram illustrating a conventional Multimedia Internet KEYing (MIKEY) message structure; [0019]FIG. 2 is a operational flowchart illustrating a conventional resending check of a mobile terminal; [0020]FIG. 3 is a structure diagram illustrating a mobile terminal and a smart card according to an embodiment of the present invention; [0021]FIG. 4 is an operational flowchart between a mobile terminal and a smart card according to an embodiment of the present invention; and [0022]FIG. 5 is an exemplary diagram illustrating a Universal Subscriber Identity Module (USIM) response message structure according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT [0023]Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, the same elements will be designated by the same reference numerals although they are shown in different drawings. Further, in the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. [0024]The present invention provides a method of efficiently processing a Short-Term Key Message (STKM) in the mobile terminal supporting the mobile broadcast. For this purpose, the present invention provides an improved structure of a response message in processing the STKM in the smart card. Particularly, in the present invention, a variety of information necessary for reproducing in the player is included in the response message and delivered to the mobile terminal; thereby the mobile terminal can easily obtain the desired information through the response message. Therefore, when the STKM is processed in the mobile terminal, there is no need to process operations other than the resending check, and the information does not need to be stored separately. [0025]First, reference will now be made in brief to information related to an encryption key used for service protection and contents protection in the mobile broadcast system and usage thereof according to an embodiment of the present invention. After the mobile terminal is registered as a service subscriber to use service and contents broadcasting from a broadcast system, when the mobile terminal subscribes a corresponding service, an STKM used for decrypting an actual encrypted service and contents can be obtained. This STKM includes a Traffic Encryption Key (TEK), which is encrypted with a Service Encryption and Authentication Key (SEAK) having an integrated format of a Service Encryption Key (SEK) with a Service Authentication Key (SAK) in order to protect the TEK, and a Message Authentication Code (MAC) function can be applied. In the future, this TEK will be used to decrypt actual encrypted services and contents. [0026]Hereinafter, a smart card for generating a response message to be delivered to the mobile terminal supporting mobile broadcast and operations of the mobile terminal receiving the response message according to an embodiment of the present invention, will be described with reference to FIG. 3. [0027]Referring to FIG. 3, the mobile terminal 10 receives encrypted broadcast services from a server managing BroadCAST (BCAST) services, and these broadcast service may include a video/audio broadcast service, a file download service, etc. [0028]The mobile terminal 10 includes a Content Provider-Client (CP-C) 51, a Stream Distribution-Client (SD-C) 52, a File Distribution-Client (FD-C) 53, and a Content Provider-Decryption (CP-D) 54. [0029]First, the SD-C component 52 acts as a receiving unit for contents broadcasted in an encrypted stream format, and delivers the received contents to the CP-D component 54 to be decrypted. Further, the FD-C component 53 also acts as a receiving unit, and delivers contents broadcasted in an encrypted file format to the CP-D component 54 for decryption. The CP-C component 51 performs registration and subscription, and by this registration and subscription the CP-C component 51 serves to obtain an encryption key necessary for decrypting the encrypted contents and to deliver it the CP-D component 54. [0030]The mobile terminal 10 having the above structure can use the services by decrypting the encrypted contents with the TEK in the CP-D component 54 through the SD-C component 52 in case of the stream contents, or through the FD-C component 53 in case of the file contents. [0031]According to the embodiment of the present invention, when the STKM generated by combining information necessary for decrypting and reproducing the broadcast service data, etc., is transmitted to the FD-C component 53 of the mobile terminal 10, the transmitted STKM is delivered to a resending check unit (not shown) in order to determine whether this STKM is a new STKM. When the transmitted STKM is a new STKM as the decision result, the resending check unit delivers the STKM to the USIM 20 through an interface. [0032]The CP-D component 54, acting as a decryption unit corresponding to delivery of the STKM, serves to parse the response message from the USIM 20, and then obtains information necessary for decrypting and reproducing the broadcast service data from the response message. After obtaining the information necessary for decrypting and reproducing the broadcast service data, the CP-D component 54 uses the encryption key, such as the TEK, etc., to decrypt the broadcast service data, and uses other information to reproduce the broadcast service data in a stream format. [0033]On the other hand, the USIM 20 has a structure such that the USIM 20 is inserted into the mobile terminal 20 through an interface, including an information extraction unit 55 and a response message generation unit 56. The information extraction unit 55 serves to obtain the information necessary for decrypting and reproducing the encrypted broadcast service data from the STKM delivered from the mobile terminal 10 through an interface. This information necessary for decrypting and reproducing the broadcast service data includes an MBMS Traffic Key (MTK) IDentification (ID) for identifying the MTK, MTK data, a terminal binding flag value for indicating whether the TEK must be decrypted with a Terminal Binding Key (TBK), a traffic authorization flag value for indicating whether there is included a MAC portion when the broadcast service data is received, and a traffic key lifetime. In addition, the response message generation unit 56 serves to generate the STKM-processed result, i.e., the response message including the above information, and to deliver the result to the mobile terminal 10 through an interface. [0034]Hereinafter, operations between the mobile terminal and the smart card will now be described with reference to FIG. 4. In FIG. 4, the mobile terminal (hereinafter, Mobile Equipment (ME)) 10 is a terminal capable of receiving the BCAST service, and may be connected to a cellular network according to the mobile terminal performance. In the following description, it is assumed that the mobile terminal can connect to a cellular network. Further, in FIG. 4, as an example of a smart card that is inserted into the mobile terminal, the Universal Subscriber Identity Module (USIM) 20 will be described. [0035]First, the ME 10 determines whether the STKM is received from a broadcast network, in step 300. When the STKM is received, the ME 10 determines, in step 310, whether the received STKM is a new STKM by performing a resending check, in step 305. More specifically, if an MTK ID included in the received STKM is less than or equal to a previous received MTK ID, the mobile terminal determines that the received STKM is not a new STKM. If the MTK ID is greater than the previous received MTK ID, the mobile terminal determines that the received STKM is a new STKM, thereby performing the resending check. As the result of the resending check, when the received STKM is determined to be a new message, the ME 10 delivers the new STKM to the USIM 20, in step 315. [0036]Then, the USIM 20 parses the new STKM, in step 320. By performing parsing and decryption of this STKM, the USIM 20 extracts information necessary for decrypting and reproducing broadcast service data, in step 325. The MTK is also included in the extracted information. More specifically, because the STKM is delivered in a MIKEY message format, the USIM 20 parses the MIKEY message. Here, the MIKEY message includes the MTK, and if a salt key is available, the salt key is also included. When parsing this MIKEY message, the USIM 20 retrieves an MBMS Service Key (MSK) with a given MSK ID in an MBMS Extension field of the MIKEY message. If there is no necessary MSK, the USIM 20 determines that the MIKEY message processing is failed, and discards the MIKEY message. [0037]Unlike the above case, if there is a necessary MSK, the USIM 20 extracts the MTK protected by the MSK, as well as the salt key (if the salt key is available) and broadcast services, i.e., the information necessary for decrypting and reproducing a video/audio stream from the MIKEY message. By this extraction, the USIM 20 performs an MBMS Generation and Validation Function (MGV-F), using the MSK. When this MGV-F procedure is successful, the USIM 20 extracts the MTK from the MIKEY message. At this time, the USIM 20 stores other parameters, such as a key lifetime, an MTK ID extracted from the MIKEY message, etc. [0038]Therefore, when information necessary for decrypting and reproducing broadcast service data is extracted through the MIKEY message parsing, the USIM 20 generates a response message including the extracted information, in step 330. In other words, the response message indicates that the USIM 20 processes the STKM delivered from the ME 10 in accordance with the GBA_U (Generic Bootstrapping Architecture_USIM) scheme. [0039]When the USIM 20 delivers the generated response message to the ME 10, in step 335, the ME 10 performs decryption and reproduction of broadcast service data by using information included in the response message, in step 340, i.e., the ME 10 decrypts the broadcast service data and delivers information necessary for reproducing data to the player in order to reproduce the broadcast service in the player. [0040]In this manner, since the ME 10 can obtain the MTK as well as a variety of information from the USIM 20 without a separate MIKEY parser, there is no need to parse the MIKEY message without overlapping with the USIM 20, and no need to store the result information according to the parsing. [0041]The structure of the response message to be delivered to the mobile terminal is illustrated as shown in FIG. 5. FIG. 5 is an exemplary diagram illustrating a USIM response message structure according to an embodiment of the present invention, newly proposing the response message structure specified in 3rd Generation Partnership Project (3GPP) 31.102.v780. [0042]Referring to FIG. 5, the present invention provides a new structure of the response message in which, in addition to the TEK, broadcast service data, i.e., a variety of information necessary for decrypting and reproducing a video/audio stream (e.g., a traffic authorization flag value, a key lifetime, etc.) is included. [0043]As shown in FIG. 5, the response message schema table will be described below. The “Description” column indicates a meaning of a corresponding element or an attribute value, and the “Coding” column indicates the type of a corresponding element or an attribute value. [0044]FIG. 5 shows a field structure sequentially illustrating the response message defined according to the present invention, together with descriptions of each field of the response message. In the structure of this response message, the response message includes a one-byte tag field for indicating a response message on an MBMS operation, a field for indicating an entire length of the response message, a one-byte field for indicating that the MBMS operation is successful, and a key identifier TLV field to be inserted with a variety of actual information. A tag value of 53 is used for the tag field of the above fields in order for the ME 10 to identify the message delivered from the USIM 20 as a response message. Further, the tag field and the field for indicating the entire length are encrypted with a Basic Encoding Rules (BER)-Tag Length Value (TLV) data object. [0045]In particular, key identifier TLV field indicated by reference number 400 has the same structure as that of reference number 410, and is inserted with a variety of information, such as an MTK, a traffic authorization flag value, and a key lifetime, in a TLV format. This information is included in the STKM, and specifically, in the BCAST extension field or in other fields of the MIKEY message structure. Therefore, when the STKM delivered from the ME 10 is parsed and analyzed in the USIM 20, after extracting corresponding information from each field, the extracted information is gathered and included in the response message in an identical structure as shown in reference number 410. [0046]The schema table 410 of the key identifier TLV field 400 will be described below. The “Byte(s)” column indicates a location of corresponding element value or an attribute value; the “Length” column indicates a size of a corresponding element value or an attribute value; and the “M/O” column is used to determine whether a corresponding element value or an attribute value is an essential content. If the value is an essential content, the ‘M’ value is used, and if not, i.e., if the value is optional, the ‘O’ value is used. [0047]This response message structure includes “Length of key Identifier TLV” for indicating a sum of length of all information included in an actual key identifier TLV field 400, “MBMS Traffic Key ID” for identifying the MTK, “MBMS Traffic Key data” for indicating an actual MTK, “Terminal Binding Flag” for indicating whether the TEK is decrypted with the Terminal Binding Key (TBK), “Traffic Authentication Flag” for indicating whether a MAC portion is included when a video/audio stream is received, “Traffic Key Lifetime” for indicating the traffic key lifetime, “Salt Key Length” for indicating a length of the salt key when the salt key is available, and “Salt Key Data” for indicating an actual salt key, etc. [0048]When the response message having the above-mentioned structure is received, the mobile terminal controls decryption of a video/audio stream by using a variety of information necessary for the MTK and player as well as reproduction by a player. Therefore, in the existing mobile terminal, information necessary for decrypting and reproducing a video/audio stream is parsed and analyzed from the STKM in advance, and the STKM is then delivered to the USIM. However, in the present invention, simply the mobile terminal only processes the resending check and the response message. As described above, according to the present invention, the same processing procedures in both the mobile terminal and the USIM, that is, the procedures of key decryption after parsing and analyzing the STKM, can be prevented from being carried out repeatedly. [0049]According to the present invention, in the smart card profile GBA_U scheme, there is an advantage in that the procedures of parsing, analyzing, and key-decrypting the STKM can be prevented from being carried out repeatedly. Further, according to the present invention, since the mobile terminal only processes the response message from the USIM, a processing load on the mobile terminal can be reduced. Further, since there is no need to store the parsing and analyzing results in a separate memory, memory can be prevented from being used uselessly. [0050]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. § 119(a) 于 2007 年 11 月 29 日向韩国工业产权局提交的题为“智能卡和生成响应消息的方法,以传送到支持移动广播的移动终端及其移动终端”的申请,并分配了序列号 . 2007-122969,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动广播系统,尤其涉及一种在支持移动广播的终端中处理短期密钥消息的方法及其终端。 [0004] 2.相关技术的描述 [0005] 开放移动联盟 (OMA) 小组研究各个移动解决方案之间的互通标准,并将两个配置文件指定为广播标准,以适用于广播环境。 其中一个配置文件是数字版权管理 (DRM) 配置文件,另一个是智能卡配置文件。 在智能卡配置文件中,使用特定密钥加密的视频/音频流通过广播网络传输到终端。 此外,具有对加密的视频/音频流进行解密所需的密钥的数据流也通过相同的广播网络传输到移动终端,这被称为短期密钥消息(STKM)。 [0006] 在智能卡配置文件中,接收到的STKM由移动终端中的多媒体互联网密钥(MIKEY)解析器进行重发检查。 这里,包含在STKM中的多媒体广播/多播服务(MBMS)流量密钥(MTK)每隔几秒或几分钟改变一次,并且每隔0.5秒或每隔几秒发送一次STKM,从而使移动终端接收到 相同的 STKM 多次或数十次,直到密钥更新一次。 每次收到STKM都不断地进行解析和密钥解密,造成移动终端资源的浪费。 因此,作为减少这种资源浪费的方法,重新发送检查是必不可少的。 [0007] 对于重新发送检查,在智能卡配置文件中使用要在 MIKEY 消息结构中传输的 STKM。 MIKEY消息结构的描述如图3所示。 1和MTK被一个简单的二进制编码方法格式化,例如MIKEY,以便被传输。 特别是,作为重新发送检查的决策参考,MBMS EXT(扩展)中包含的 MTK IDentification(ID) 100 图中的字段。 1 被使用。 [0008] 现在将参考图3描述重新发送检查的过程。 2. 图。 图2示出了用于传统重发支票的移动终端的操作流程图。 [0009] 参考图。 2、移动终端判断是否收到STKM,在步骤 200 . 如果接收到 STKM,则移动终端在步骤 205 ,并判断接收到的STKM是否为新的STKM 210 . 如果接收到的STKM不是新的STKM,移动终端进入步骤 215 并丢弃接收到的 STKM。 如果接收到的STKM为新消息,则在移动终端或智能卡上根据安全功能的位置进行解析和密钥解密过程。 该过程根据在智能卡配置文件中处理STKM的位置是否为通用引导架构(GBA)-移动设备(ME)(GBA_ME)方案或GBA_通用用户识别模块(USIM)(GBA_U)方案。 移动终端或USIM,即智能卡。 在GBA_U方案中,STKM通过应用协议数据单元(APDU)命令传递给USIM,然后在USIM内部进行解析和密钥解密过程。 然后,将包含在STKM中的MTK或流量加密密钥(TEK)再次传递给移动终端。 [0010] 此时,当移动终端中包含单独的MIKEY解析器用于解析STKM时,移动终端通过执行解析操作来解析MIKEY并根据解析存储结果信息,在步骤 220. 此后,移动终端确定是否从USIM接收到响应消息,在步骤 225 . 当接收到响应消息时,移动终端通过解析响应消息获得TEK,在步骤 230 . 随后,移动终端将存储的结果信息和TEK传送给玩家,在步骤 235 . [0011] 在播放器中,再现视频/音频流需要各种信息。 然而,在 GBA_U 方案的情况下,STKM 中包含各种信息,但 USIM 提供唯一的 TEK。 因此,由于移动终端必须使用单独的MIKEY解析器进行解析操作,并将值保存在内存中,因此解析操作会浪费移动终端中的内存和资源。 此外,独立于USIM内的解析和密钥解密过程,通过分析MIKEY和分析结果信息,在移动终端中不必要地执行冗余操作,这增加了移动终端的负载。 发明内容 [0012] 因此,本发明旨在解决现有技术中出现的上述问题,并且本发明提供了一种智能卡和一种用于生成响应消息的方法,该响应消息被传送到支持移动广播的移动终端,以便 在移动终端中顺利进行内存管理和资源管理,并提供了一种移动终端。 [0013] 此外,本发明提供了一种智能卡和一种用于生成响应消息以传送到支持移动广播的移动终端的方法,避免了移动终端中USIM的冗余操作,并为此提供了一种移动终端。 [0014] 根据本发明的一个方面,提供了一种插入支持移动广播的移动终端并根据短期密钥消息处理生成响应消息的智能卡,该智能卡包括信息提取单元,用于 ,当从移动终端传送短期密钥消息(STKM)时,从STKM中提取解密和再现广播服务数据所需的信息; 响应消息生成单元,用于生成包括提取的信息的响应消息并将响应消息传送到移动终端。 [0015] 根据本发明的另一方面,提供了一种移动终端,其中插入了智能卡并且处理短期密钥消息,该移动终端包括用于接收短期密钥消息(STKM)的接收单元 )通过广播网络; 重发校验单元,用于判断接收到的短期密钥信息是否为新的短期密钥信息,当接收到的短期密钥信息为新的短期信息时,将接收到的短期密钥信息下发给智能卡 关键信息; 以及解密单元,用于在响应于短期密钥消息的传递而从智能卡传递响应消息时,通过解析传递的响应消息,从响应消息中获得解密和再现广播服务数据所需的信息。 [0016] 根据本发明的另一方面,提供了一种生成响应消息的方法,该响应消息将被传送到支持智能卡中的移动广播的移动终端,该方法包括从智能卡接收短期密钥消息(STKM)。 移动终端; 从短期密钥消息中提取解密和再现广播服务数据所需的信息; 生成包括提取信息的响应消息; 将响应消息下发给移动终端。 附图的简要说明 [0017] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0018] 如图。 附图说明图1是说明传统多媒体互联网键控(MIKEY)消息结构的示意图; [0019]如图。 图2是现有的移动终端重发检查的动作流程图。 [0020] 如图。 图3为本发明实施例的移动终端和智能卡的结构示意图。 [0021] 如图。 图4为本发明实施例移动终端与智能卡之间的操作流程图。 和 [0022] 如图。 图5是图示根据本发明实施例的通用用户识别模块(USIM)响应消息结构的示例图。 示例性实施例的详细说明 [0023] 在下文中,将参照附图描述本发明的示例性实施例。 在以下描述中,相同的元件将由相同的附图标记表示,尽管它们在不同的附图中示出。 此外,在本发明的以下描述中,当可能使本发明的主题不太清楚时,将省略对包含在本文中的已知功能和配置的详细描述。 [0024] 本发明提供了一种在支持移动广播的移动终端中有效处理短期密钥消息(STKM)的方法。 为此,本发明提供了一种改进的响应消息结构,用于处理智能卡中的STKM。 特别地,在本发明中,在播放器中再现所需的各种信息被包含在响应消息中并被传递到移动终端; 从而移动终端可以很容易地通过响应消息获得想要的信息。 因此,在移动终端处理STKM时,不需要处理重发校验以外的操作,也不需要单独存储信息。 [0025] 首先,现在将简要地参考与根据本发明实施例的在移动广播系统中用于服务保护和内容保护的加密密钥及其使用有关的信息。 在移动终端注册为服务订阅者以使用广播系统广播的服务和内容之后,当移动终端订阅相应的服务时,可以获得用于解密实际加密的服务和内容的STKM。 此 STKM 包括流量加密密钥 (TEK),该密钥使用服务加密和验证密钥 (SEAK) 加密,该密钥具有服务加密密钥 (SEK) 与服务验证密钥 (SAK) 的集成格式,以保护 TEK , 并且可以应用消息验证码 (MAC) 功能。 将来,此 TEK 将用于解密实际的加密服务和内容。 [0026] 在下文中,将参照图1描述根据本发明实施例的用于生成要传送到支持移动广播的移动终端的响应消息的智能卡以及接收响应消息的移动终端的操作。 3. [0027] 参考图。 3、移动端 10 从管理BroadCAST(BCAST)服务的服务器接收加密的广播服务,这些广播服务可以包括视频/音频广播服务、文件下载服务等。 [0028] 移动终端 10 包括一个内容提供者-客户端 (CP-C) 51 , 流分发客户端 (SD-C) 52 , 文件分发客户端 (FD-C) 53 ,以及内容提供者解密 (CP-D) 54 . [0029] 一、SD-C组件 52 充当以加密流格式广播的内容的接收单元,并将接收到的内容传递给 CP-D 组件 54 被解密。 此外,FD-C 组件 53 还充当接收单元,并将以加密文件格式广播的内容传送到 CP-D 组件 54 用于解密。 CP-C 组件 51 执行注册和订阅,并通过此注册和订阅 CP-C 组件 51 用于获取解密加密内容所需的加密密钥并将其传递给 CP-D 组件54 . [0030] 移动终端 10 具有上述结构的可以通过使用 CP-D 组件中的 TEK 对加密内容进行解密来使用服务 54 通过 SD-C 组件 52 在流内容的情况下,或通过 FD-C 组件 53 在文件内容的情况下。 [0031] 根据本发明的实施例,当通过组合解密和再现广播服务数据等所需的信息而生成的STKM被发送到FD-C组件时 53 移动终端的 10 ,发送的STKM被传递到重新发送检查单元(未示出)以确定该STKM是否是新的STKM。 当发送的STKM是新的STKM作为判定结果时,重发校验单元将STKM下发给USIM 20 通过一个界面。 [0032] CP-D 组件 54 ,作为对应于 STKM 交付的解密单元,用于解析来自 USIM 的响应消息 20 ,然后从响应消息中获得解密和再现广播服务数据所需的信息。 在获得解密和再现广播业务数据所需的信息后,CP-D组件 54 使用TEK等加密密钥对广播服务数据进行解密,并使用其他信息以流格式再现广播服务数据。 [0033] 另一方面,USIM 20 具有这样的结构,使得 USIM 20 插入移动终端 20 通过一个接口,包括一个信息提取单元 55 和响应消息生成单元 56 . 信息提取单元 55 用于从移动终端传送的 STKM 中获取解密和再现加密广播服务数据所需的信息 10 通过一个界面。 解密和再现广播服务数据所需的该信息包括用于识别 MTK、MTK 数据的 MBMS 流量密钥 (MTK) 标识 (ID)、用于指示是否必须用终端绑定密钥解密 TEK 的终端绑定标志值 ( TBK)、用于指示在接收到广播服务数据时是否包含MAC部分的流量授权标志值,以及流量密钥寿命。 此外,响应消息生成单元 56 用于生成STKM处理的结果,即包含上述信息的响应消息,并将结果传递给移动终端 10 通过一个界面。 [0034] 在下文中,现在将参照图1描述移动终端和智能卡之间的操作。 4. 在图 4、移动终端(以下简称移动设备(ME)) 10 是能够接收BCAST服务的终端,可以根据移动终端的性能连接到蜂窝网络。 在以下描述中,假设移动终端可以连接到蜂窝网络。 此外,在图 4 中。 参考图4,作为插入移动终端的智能卡的示例,通用用户识别模块(USIM) 20 将进行描述。 [0035] 首先,ME 10 确定是否从广播网络接收到 STKM,在步骤 300 . 当收到 STKM 时,ME 10 确定,在步骤 310 ,通过重发检查接收到的STKM是否为新的STKM,在步骤 305 . 更具体地,如果接收到的STKM中包括的MTK ID小于或等于先前接收到的MTK ID,则移动终端确定接收到的STKM不是新的STKM。 如果MTK ID大于之前接收到的MTK ID,则移动终端判断接收到的STKM是新的STKM,从而进行重发检查。 作为重发检查的结果,当确定收到的 STKM 是新消息时,ME 10 向 USIM 交付新的 STKM 20 , 在步 315 . [0036] 然后,USIM 20 在步骤中解析新的 STKM 320 . 通过对这个 STKM 进行解析和解密,USIM 20提取解密和再现广播服务数据所需的信息,在步骤 325 . MTK 也包含在提取的信息中。 更具体地说,因为 STKM 以 MIKEY 消息格式传递,所以 USIM 20 解析 MIKEY 消息。 这里,MIKEY 消息中包含 MTK,如果有可用的盐键,则还包含盐键。 当解析这个 MIKEY 消息时,USIM 20 在 MIKEY 消息的 MBMS 扩展字段中检索具有给定 MSK ID 的 MBMS 服务密钥 (MSK)。 如果没有必要的 MSK,USIM 20 确定MIKEY消息处理失败,丢弃MIKEY消息。 [0037] 与上述情况不同,如果有必要的 MSK,USIM 20 提取受 MSK 保护的 MTK,以及盐密钥(如果盐密钥可用)和广播服务,即从 MIKEY 消息中解密和再现视频/音频流所需的信息。 通过这种提取,USIM 20 使用 MSK 执行 MBMS 生成和验证功能 (MGV-F)。 当这个 MGV-F 程序成功时,USIM 20 从 MIKEY 消息中提取 MTK。 此时,USIM 20 存储其他参数,例如密钥生命周期、从 MIKEY 消息中提取的 MTK ID 等。 [0038] 因此,当通过 MIKEY 消息解析提取解密和再现广播服务数据所需的信息时,USIM 20 生成包含提取信息的响应消息,在步骤 330 . 换句话说,响应消息表明 USIM 20 处理从 ME 交付的 STKM 10 根据 GBA_U(通用自举体系结构_USIM)方案。 [0039] 当 USIM 20 将生成的响应消息传递给 ME 10 , 在步 335 , 主题 10 在步骤 340 ,即 ME 10 解密广播服务数据并将再现数据所需的信息传递给播放器,以便在播放器中再现广播服务。 [0040] 这样,由于 ME 10 可以从 USIM 获取 MTK 以及各种信息 20 如果没有单独的 MIKEY 解析器,则无需解析 MIKEY 消息而不与 USIM 重叠 20 ,无需根据解析存储结果信息。 [0041] 发送到移动终端的响应消息的结构如图1所示。 5. 图。 图5是说明根据本发明实施例的USIM响应消息结构的示例图,新提出3中指定的响应消息结构 rd 代合作伙伴计划 (3GPP) 31.102.v780。 [0042] 参考图。 如图5所示,本发明提供了响应消息的新结构,其中除了TEK之外,广播服务数据,即解密和再现视频/音频流所需的各种信息(例如,交通授权标志值) ,密钥寿命等)包括在内。 [0043] 如图所示。 参照图5,下面将描述响应消息模式表。 “Description”栏表示对应元素或属性值的含义,“Coding”栏表示对应元素或属性值的类型。 [0044] 如图。 图5示出了顺序说明根据本发明定义的响应消息的字段结构,以及响应消息的每个字段的描述。 在该响应消息的结构中,响应消息包括用于指示对MBMS操作的响应消息的一字节标签字段、用于指示响应消息的全长的字段、用于指示MBMS操作的一字节字段 操作成功后,一个关键标识符 TLV 字段将被插入各种实际信息。 标签值 53 用于上述字段的标签字段,以便 ME 10 识别从 USIM 传递的消息 20作为响应消息。 此外,标签字段和用于指示整个长度的字段用基本编码规则(BER)-标签长度值(TLV)数据对象加密。 [0045] 特别是,由参考号指示的密钥标识符 TLV 字段 400 具有与参考编号相同的结构 410 ,并以TLV格式插入MTK、流量授权标志值、密钥生存期等多种信息。 该信息包含在 STKM 中,特别是包含在 BCAST 扩展字段或 MIKEY 消息结构的其他字段中。 因此,当 STKM 从 ME 交付 10 在 USIM 中进行解析和分析 20 ,在从每个字段中提取相应的信息后,将提取的信息收集起来,并以与参考编号所示相同的结构包含在响应消息中 410 . [0046] 架构表 410 密钥标识符 TLV 字段 400 下面将进行描述。 “Byte(s)”列表示对应元素值或属性值的位置; “Length”列表示对应元素值或属性值的大小; “M/O”栏用于判断对应的元素值或属性值是否为必要内容。 如果该值是必要内容,则使用“M”值,如果不是,即如果该值是可选的,则使用“O”值。 [0047] 该响应消息结构包括“Length of key Identifier TLV”,用于指示包含在实际密钥标识符 TLV 字段中的所有信息的长度总和 400 , “MBMS Traffic Key ID”用于识别MTK,“MBMS Traffic Key data”用于指示实际MTK,“Terminal Binding Flag”用于指示TEK是否被终端绑定密钥(TBK)解密,“流量认证标志” 用于指示在接收到视频/音频流时是否包括MAC部分, “Traffic Key Lifetime”用于指示流量密钥寿命, “Salt Key Length”用于指示当盐密钥可用时盐密钥的长度,以及 “Salt Key Data”用于指示实际的盐键等。 [0048] 当接收到具有上述结构的响应消息时,移动终端通过使用MTK和播放器所需的各种信息以及播放器的再现来控制视频/音频流的解密。 因此,在现有的移动终端中,预先从STKM中解析和解析视频/音频流的解密和再现所需的信息,然后将STKM传递给USIM。 然而,在本发明中,简单的移动终端只处理重发检查和响应消息。 如上所述,根据本发明,可以避免重复执行移动终端和USIM中相同的处理过程,即在解析和分析STKM之后的密钥解密过程。 [0049] 根据本发明,在智能卡配置文件GBA_U方案中,具有可以防止重复执行STKM的解析、分析和密钥解密的过程的优点。 此外,根据本发明,由于移动终端仅处理来自USIM的响应消息,因此可以减轻移动终端的处理负荷。 此外,由于不需要将解析和分析结果存储在单独的存储器中,因此可以防止存储器被无用地使用。 [0050] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101473488B1(String), KR1020090056026A(String), US20090143105A1(String), US8145270B2(String), WO2009069893A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101473488B1(String), KR1020090056026A(String), US20090143105A1(String), US8145270B2(String), WO2009069893A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8145270B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101473488B1(String), KR1020090056026A(String), US20090143105A1(String), US8145270B2(String), WO2009069893A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270703(Integer), KR101473488B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270703(Integer), KR1020090056026A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.562 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270703(Integer), US20090143105A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.574 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.575 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270703(Integer), US8145270B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270703(Integer), WO2009069893A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.596 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8145270B2(String), US8145270B2(String), 1332777600(Integer), 270703(Integer), 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185027(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185027(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.622 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.623 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185027(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.625 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185027(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.634 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.635 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.636 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.636 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.647 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.648 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.650 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 185027(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.659 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7522940B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Methods and mobile terminals for display of mobile terminal density information(String), 移动终端密度信息的显示方法及移动终端(String), US7522940B2(String), A method of providing information on a mobile terminal can include displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server.(String), 一种提供关于移动终端的信息的方法可以包括根据基于由在无线通信网络中操作的移动终端向服务器报告的参数的可选上下文,在移动终端显示器上显示移动终端密度信息。(String), US10/989652(String), 1100534400(Integer), US7522940B2(String), 1240243200(Integer), 1240243200(Integer), 美国(String), 4(Integer), 4(Integer), 23(Integer), DE10237906A1 | EP1176840A1 | EP1191802A2 | JP1999223674A | JP2002341053A | JP2003329779A | US20030100317A1 | US20030134648A1 | US20040171390A1 | US20040185839A1 | US20050086004A1 | US20060009240A1 | US6182010B1 | US6236933B1 | US6427113B1 | US6526349B2 | US6539300B2 | US6567661B2 | US6594576B2 | US6804524B1 | US6810321B1 | US7188026B2 | WO2002027691A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.671 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185028(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\5edcbf95094b495da7f2407413d7dfaf.png(String), 185028(Integer), 5edcbf95094b495da7f2407413d7dfaf.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Methods and mobile terminals for display of mobile terminal density information(String), 移动终端密度信息的显示方法及移动终端(String), US7522940B2(String), A method of providing information on a mobile terminal can include displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server.(String), 一种提供关于移动终端的信息的方法可以包括根据基于由在无线通信网络中操作的移动终端向服务器报告的参数的可选上下文,在移动终端显示器上显示移动终端密度信息。(String), US10/989652(String), 1100534400(Integer), US7522940B2(String), 1240243200(Integer), 1240243200(Integer), 美国(String), 2(Integer), 4(Integer), 4(Integer), 23(Integer), DE10237906A1 | EP1176840A1 | EP1191802A2 | JP1999223674A | JP2002341053A | JP2003329779A | US20030100317A1 | US20030134648A1 | US20040171390A1 | US20040185839A1 | US20050086004A1 | US20060009240A1 | US6182010B1 | US6236933B1 | US6427113B1 | US6526349B2 | US6539300B2 | US6567661B2 | US6594576B2 | US6804524B1 | US6810321B1 | US7188026B2 | WO2002027691A1(String), \20230420\5edcbf95094b495da7f2407413d7dfaf.png(String), 20(Integer), 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 1. A method of providing information on a mobile terminal comprising:displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server, the method further comprising:applying the mobile terminal density information to the selectable context to generate a geographic display associated with the contex, wherein the geographic display associated with the context comprises a map and a plurality of grid of locations overlaid thereon;wherein the density information further comprises velocity information associated with the mobile terminals; andwherein selected ones of the plurality of grid locations are rendered with color and opacity values based on mobile terminal density information associated with the selected ones of the plurality of grid locations.(String), 1.一种在移动终端上提供信息的方法包括:基于在无线通信网络中运行的移动终端向服务器报告的参数,根据可选择的上下文在移动终端显示器上显示移动终端密度信息,该方法还包括:将移动终端密度信息应用​​于可选上下文以生成与上下文相关联的地理显示,其中与上下文相关联的地理显示包括地图和覆盖在其上的多个位置网格;其中,密度信息还包括与移动终端相关联的速度信息;和其中,基于与多个网格位置中的所选位置相关联的移动终端密度信息,用颜色和不透明度值渲染多个网格位置中的所选位置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 2. A method according to claim 1 further comprising:receiving the parameters from the mobile terminals at the server via ad-hoc reporting of the mobile terminals;compiling the parameters to provide the mobile terminal density information; andtransmitting the mobile terminal density information to the mobile terminal for display.(String), 2.根据权利要求1的方法还包括:通过移动终端的自组织上报,在服务器端接收来自移动终端的参数;编译参数以提供移动终端密度信息;和将移动终端密度信息发送给移动终端进行显示。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 3. A method according to claim 1 wherein a maximum opacity value is less than an opaque value so that the underlying map is visible through the plurality of grid locations overlaid thereon at the maximum opacity value.(String), 3.根据权利要求1的方法其中最大不透明度值小于不透明值,使得底层地图通过以最大不透明度值覆盖在其上的多个网格位置可见。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.697 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 4. A method according to claim 1 wherein the color values comprise a statistical representation of velocity of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 4.根据权利要求1的方法其中颜色值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的速度的统计表示。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 5. A method according to claim 1 wherein the opacity values comprise a statistical representation of a density of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 5.根据权利要求1的方法其中不透明度值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端密度的统计表示。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 6. A method according to claim 1 wherein the selectable context comprises a first selectable context selected from a plurality of selectable contexts, wherein some of the mobile terminal density information is suppressed according to the first selectable context and not suppressed according to a second selectable context.(String), 6.根据权利要求1所述的方法其中可选上下文包括从多个可选上下文中选择的第一可选上下文,其中一些移动终端密度信息根据第一可选上下文被抑制,并且根据第二可选上下文不被抑制。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 7. A method according to claim 1 wherein the selectable context comprises a shopping context, a commuting context, and/or an entertainment context.(String), 7.根据权利要求1的方法其中可选上下文包括购物上下文、通勤上下文和/或娱乐上下文。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 8. A method according to claim 7 wherein the selectable context comprises a sub-context.(String), 8.根据权利要求7的方法其中可选上下文包括子上下文。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 9. A method according to claim 1 carried out by a computer program product embodied in a computer readable medium executable by a processor.(String), 9.根据权利要求1所述的方法,由包含在可由处理器执行的计算机可读介质中的计算机程序产品执行。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 10. A method according to claim 1 carried out by a system comprising:a means for displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to server.(String), 10.根据权利要求1所述的方法,由系统执行包括:一种用于根据可选择的上下文在移动终端显示器上显示移动终端密度信息的装置,该上下文基于在无线通信网络中操作的移动终端向服务器报告的参数。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 11. A method according to claim 1 wherein the parameters comprise location information, velocity information, connectivity information, image information, and/or audio information.(String), 11.根据权利要求1所述的方法其中参数包括位置信息、速度信息、连通性信息、图像信息和/或音频信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 12. A mobile terminal comprising:a transceiver circuit configured to transmit/receive communications to/from a wireless communications network that provides service to the mobile terminal including parameters received from a server reported by mobile terminals operating in the wireless communications network to the server;a processor circuit, coupled to the transceiver, configured to provide mobile terminal density information according to a selectable context based on the parameters received from the server;a display, coupled to the processor circuit, configured to display the mobile terminal density information based on the parameters;wherein the processor circuit is further configured to provide a geographic display including the mobile terminal density information associated with the context;wherein the geographic display comprises a map and a plurality of grid of locations overlaid thereon;wherein the density information further comprises velocity information associated with the mobile terminals; andwherein selected ones of the plurality of grid locations are rendered with color and opacity values based on mobile terminal density information associated with the selected ones of the plurality of grid locations.(String), 12.移动终端包括:收发器电路,被配置为向/从无线通信网络发送/接收通信,该无线通信网络向移动终端提供服务,包括从服务器接收的参数,这些参数由在无线通信网络中操作的移动终端报告给服务器;处理器电路,耦合到收发器,被配置为基于从服务器接收的参数,根据可选择的上下文提供移动终端密度信息;显示器,与处理器电路耦合,用于根据参数显示移动终端密度信息;其中,处理器电路还被配置为提供包括与上下文关联的移动终端密度信息的地理显示;其中地理显示包括地图和覆盖在其上的多个位置网格;其中,密度信息还包括与移动终端相关联的速度信息;和其中,基于与多个网格位置中的所选位置相关联的移动终端密度信息,用颜色和不透明度值渲染多个网格位置中的所选位置。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 13. A mobile terminal according to claim 12 wherein the parameters comprise location information, velocity information, connectivity information, and/or audio information.(String), 13.根据权利要求12所述的移动终端其中参数包括位置信息、速度信息、连通性信息和/或音频信息。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 14. A mobile terminal according to claim 13 wherein the connectivity information comprises a value associated with a number of other devices in communication with the mobile terminal over a channel other than that used to transmit the parameters.(String), 14.根据权利要求13所述的移动终端其中-连接性信息包括与通过不同于用于传输参数的信道的信道与移动终端通信的许多其他设备相关联的值。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 15. A mobile terminal according to claim 13 wherein the velocity information is used as an inversely proportional indicator of the mobile terminal density information.(String), 15.根据权利要求13所述的移动终端其中速度信息作为移动终端密度信息的反比指标。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 16. A mobile terminal according to claim 12 wherein a maximum opacity value is less than an opaque value so that the underlying map is visible through the plurality of grid locations overlaid thereon at the maximum opacity value.(String), 16.根据权利要求12所述的移动终端其中最大不透明度值小于不透明值,使得底层地图通过以最大不透明度值覆盖在其上的多个网格位置可见。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 17. A mobile terminal according to 12 wherein the color values comprise a statistical representation of velocity of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 17.移动终端根据12其中颜色值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的速度的统计表示。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 18. A mobile terminal according to claim 12 wherein the opacity values comprise a statistical representation of a density of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 18.根据权利要求12所述的移动终端其中不透明度值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端密度的统计表示。(String), 1(Integer), 17(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 19. A mobile terminal according to claim 12 wherein the selectable context comprises a first selectable context selected from a plurality of selectable contexts, wherein some of the mobile terminal density information is suppressed according to the first selectable context and not suppressed according to a second selectable context.(String), 19.根据权利要求12所述的移动终端其中可选上下文包括从多个可选上下文中选择的第一可选上下文,其中一些移动终端密度信息根据第一可选上下文被抑制,并且根据第二可选上下文不被抑制。(String), 1(Integer), 18(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185028(Integer), 20. A mobile terminal according to claim 12 wherein the selectable context comprises shopping, commuting, crowding, parking, entertaining, and/or working.(String), 20.根据权利要求12所述的移动终端其中可选择的情境包括购物、通勤、拥挤、停车、娱乐和/或工作。(String), 1(Integer), 19(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.866 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185028(Integer), TECHNICAL FIELD OF THE INVENTION [0001]The invention generally relates to the field of electronics and, more particularly, to methods, mobile terminals, and computer program products for electronic communications. DESCRIPTION OF RELATED ART [0002]It is known to collect environmental parameters, such as weather-related parameters, from mobile terminals operating in a wireless communications network. For example, U.S. Pat. No. 6,567,661 to McDonnell et al. entitled “Distributed Telemetry Method and System” discusses a distributed telemetry method effected by coordinating the taking of readings or a parameter by mobile phone users. The parameter readings can be sent to a service system together with a location of the user. Collating the readings and location information may enable generation of a representation of the geographic variation of the measured parameter (see, for example, the abstract of McDonnell). [0003]It is further known to track in-vehicle cell phones within a given region to provide data for control of a traffic system. For example, U.S. Pat. No. 6,539,300 to Myr entitled “Method for Regional System Wide Optimal Signal Timing for Traffic Control Based on Wireless Phone Networks.” discusses obtaining signals from vehicular-based cellular phones to provide location information on the moving vehicles, which are input to an intelligent traffic control system to provide position information. Mathematical models may use the information and digital maps/algorithms to compute actual travel times (see, for example, the abstract of Myr). [0004]Other types of systems are discussed in the following references: EP 1191802; JP 11/223674; JP 2002/341053; JP 2003/329779; U.S. Pat. No. 6,236,933; US 2003/100317; WO 02/27691; U.S. Pat. No. 6,427,113; and DE 10237906. Notwithstanding the material discussed above, there is a need for improved usage of parameters collected from mobile terminals. SUMMARY [0005]Embodiments according to the invention can provide methods, mobile terminals, and computer program products for display of mobile terminal density information. Pursuant to these embodiments, a method of providing information on a mobile terminal can include displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server. [0006]In some embodiments according to the invention, the method further includes receiving the parameters from the mobile terminals at the server via ad-hoc reporting of the mobile terminals. The parameters can be compiled to provide the mobile terminal density information and the mobile terminal density information can be transmitted to the mobile terminal for display. [0007]In some embodiments according to the invention, the mobile terminal density information can be applied to the selectable context to generate a geographic display associated with the context. In some embodiments according to the invention, the geographic display associated with the context is a map and a plurality of grid of locations overlaid thereon. [0008]In some embodiments according to the invention, the density information further includes velocity information associated with the mobile terminals. Selected ones of the plurality of grid locations can be rendered with color and opacity values based on mobile terminal density information associated with the selected ones of the plurality of grid locations. [0009]In some embodiments according to the invention, a maximum opacity value is less than an opaque value so that the underlying map is visible through the plurality of grid locations overlaid thereon at the maximum opacity value. In some embodiments according to the invention, the color values are a statistical representation of velocity of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations. In some embodiments according to the invention, the opacity values are a statistical representation of a density of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations. [0010]In some embodiments according to the invention, the selectable context is a first selectable context selected from a plurality of selectable contexts, wherein some of the mobile terminal density information is suppressed according to the first selectable context and not suppressed according to a second selectable context. [0011]In some embodiments according to the invention, the selectable context can be a shopping context, a commuting context, and/or an entertainment context. In some embodiments according to the invention, the selectable context comprises a sub-context. In some embodiments according to the invention, the parameters can be location information, velocity information, connectivity information, image/video information and/or audio information. BRIEF DESCRIPTION OF THE DRAWINGS [0012]FIG. 1 is a schematic diagram that illustrates embodiments of a wireless communications network providing service to mobile terminals according to some embodiments of the invention. [0013]FIG. 2 is a block diagram that illustrates mobile terminals according to some embodiments of the invention. [0014]FIG. 3A is a schematic diagram that illustrates parameters collected reported by mobile terminals according to some embodiments of the invention. [0015]FIG. 3B is a schematic diagram that illustrates a mobile terminal density system according to some embodiments of the invention. [0016]FIG. 4 is a schematic diagram that illustrates a geographic display on a mobile terminal according to some embodiments of the invention. [0017]FIG. 5 is a schematic diagram that illustrates a geographic display on a mobile terminal according to some embodiments of the invention. [0018]FIG. 6A is a schematic diagram that illustrates a geographic display on a mobile terminal according to some embodiments of the invention. [0019]FIG. 6B is an enlarged view of a portion of FIG. 6A that illustrates a display of some mobile terminal density information according to a selectable context. [0020]FIG. 6C is an enlarged view of a portion of FIG. 6A that illustrates a display of some mobile terminal density information according to a selectable context. [0021]FIG. 7 is a flow chart that illustrates operations of mobile terminals according to some embodiments of the invention. DETAILED DESCRIPTION OF EMBODIMENTS ACCORDING TO THE INVENTION [0022]The invention is described more fully hereinafter with reference to the accompanying drawings, in which illustrative embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein the term “and/or” includes any and all combinations of one or more of the associated listed items. [0023]Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. [0024]It will be understood that although the terms first and second may be used herein to describe various components these components should not be limited by these terms. These terms are only used to distinguish one component from another. Thus, for example, a first component discussed below could be termed a second component without departing from the teachings of the present invention. [0025]The invention is described with reference to a flowchart and block diagrams of mobile terminals, communications networks, and operations thereof according to embodiments of the invention. It will be understood that each block of the flowchart and/or block diagrams, and combinations of blocks, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart and/or schematic block or blocks. [0026]It will be understood, that the invention may be practiced with any mobile terminal that operates in a communications network. A mobile terminal may be, for example, a single or dual mode cellular radiotelephone with or without a multi-line display; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a Personal Data Assistant (PDA) that can include a mobile terminal, pager. Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver: and a conventional laptop and/or palmtop receiver or other appliance all of which include a transceiver. [0027]It will be understood that mobile terminals according to the invention may operate in any type of wireless communications network. In some embodiments according to the invention, for example, the network may provide services broadly labeled as PCS (Personal Communications Services) including advanced digital cellular systems conforming to standards such as IS-136 and IS-95, lower-power systems such as DECT (Digital Enhanced Cordless Telephone), data communications services such as CDPD (Cellular Digital Packet Data), and other systems such as CDMA-2000, that are proposed using a format commonly referred to as Wideband Code Division Multiple Access (WCDMA). [0028]Mobile terminals according to the invention may also be used in celestial communications networks, such as satellite communications networks. The celestial wireless communications network may be employed to perform similar functions to those performed by the communications network of FIG. 1. In particular, the celestial wireless communication system typically includes one or more satellites that serve as relays or transponders between one or more earth stations and (satellite) mobile terminals. The satellites typically communicate with the satellite mobile terminals and earth stations via duplex communication links. Each earth station may, in turn, be connected to a Public Switched Telephone Network (PSTN) in a terrestrial communications networks, thereby allowing communications between the satellite mobile terminal, and other devices serviced by the network. [0029]FIG. 1 is a diagram that illustrates a wireless communications network (hereinafter “network”) 10 that supports communications in which mobile terminals 20 according to the invention can be used. Networks 10 are commonly employed to provide voice and data communications to subscribers using, for example, the standards discussed above. According to FIG. 1, a plurality of mobile terminals 20 can communicate with each other and other terminals, such as terminals 26, 28, via the network 10 and a PSTN 14. [0030]The wireless communications network 10 is organized as cells 1-2 that collectively can provide service to a geographic region. In particular, each of the cells can provide service to associated sub-regions included in the geographic region covered by the network 10. More or fewer cells can be included in the network 10, and the coverage area for the cells 1-2 may overlap. Each of the cells 1-2 may include an associated base station 30a-b. The base stations 30a-b can provide wireless communications between each other and the mobile terminals 20 in the associated geographic region to allow for communications therebetween. [0031]Each of the base stations 30a-b can transmit/receive data to/from the mobile terminals 20 over an associated control channel 22. For example, the base station 30a in cell 1 can communicate with the mobile terminal 20 over the control channel 22. The control channel 22 can be used, for example, to page the mobile terminal 20 in response to calls directed thereto or to transmit traffic channel assignments to the mobile terminal 20 over which a call associated therewith is to be conducted. The control channels 22 can be identified using control channel numbers or identifiers. For example, the mobile terminal 20 can store a channel number that identifies control channel 22 as the control channel on which it is currently camping. Although only one control channel is illustrated, it will be understood that each of the mobile terminals 20 may have a respective control channel 22 associated therewith. [0032]The mobile terminals 20 are configured to register with the network 10 when, for example, the mobile terminals are turned on. In particular, the mobile terminals use information, stored on a SIM card in the respective mobile terminal, to register with the network 10. Once the mobile terminals 20 are registered with the network 10, the mobile terminals 20 can receive service from the wireless communications network 10, such as placing and receiving calls via the wireless communications network 10 as the mobile terminals 20 move within the geographic region serviced by the network 10. [0033]The mobile terminals 20 may also be capable of sending and receiving messages over the respective control channel 22. In some embodiments according to the invention, the mobile terminals send/receive Short Message Service (SMS) or Enhanced Message Service (EMS) formatted messages, Multimedia Message Service (MMS), and/or Smartmessaging™ formatted messages. As is known to those skilled in the art, SMS and EMS messages can be transmitted on digital networks, such as GSM networks, allowing relatively small text messages (for example, 160 characters in size) to be sent and received via the network operator's message center to the mobile terminal 20, or from the Internet, using a so-called SMS (or EMS) “gateway” website. [0034]MMS is a messaging system for asynchronous mobile-to-mobile messaging, which enables communication of messages containing “rich media” content, i.e., content of types that tend to be more data-intensive than text, such as such as graphics, digital photographs, video, animation, sound files, and/or audio. MMS is standardized by the WAP Forum and the Third-Generation Partnership Project (3GPP) and is described in: “WAP MMS, Architecture Overview,” WAP-205, WAP Forum (Approved Version Apr. 25, 2001); “WAP MMS, Client Transactions Specification,” WAP-206, WAP Forum (Approved Version Jan. 15, 2002); “WAP MMS, Encapsulation Specification,” WAP-209, WAP Forum (Approved Version Jan. 5, 2002); “Requirements”, 3GPP specification 22.140; and “Architecture and Functionality,” 3GPP specification 23.140. [0035]WAP has been promulgated to enable application programs to be written to operate on a wide array of wireless communications networks by providing a standard for the presentation and delivery of wireless information and telephony services. As a result, various mobile terminals, such as mobile terminals, pagers, two-way radios, smartphones and communicators can utilize WAP to enable delivery of relevant information and services to mobile terminals. [0036]Accordingly, it will be understood that, as described further herein, the control channels 22 can be used to transmit mobile terminal density information to the mobile terminals 20 as an SMS, MMS, EMS or other type of message via a WAP client. In some embodiments according to the invention, the mobile terminal density information can be provided to the mobile terminals 20 via a “Midlet.” As is well known by those skilled in the art, a Midlet is a Java application designed to run on Java enabled devices such as cell phones and PDAs. A Midlet is based on the Java 2 Platform, Micro Edition, using the Connected Limited Device Configuration (CLDC), which defines a set of application programming interfaces and a virtual machine for resource-constrained devices, such as those discussed herein. Midlets are further discussed on the Internet at “www.sun.com.” It will be further understood that other information, such as maps and other dynamic graphical data may also be transmitted in a suitable message, including any or all of the above message types. [0037]FIG. 2 is a block diagram that illustrates a mobile terminal 20 according to some embodiments of the invention. According to some embodiments of the invention, mobile terminal density information is transmitted to the mobile terminal for display based on parameters reported by the mobile terminals. The mobile terminal density information may be a statistical representation of, for example, the number of mobile terminals estimated to be located within a geographic area at a particular time. [0038]As illustrated in FIG. 2, the mobile terminal 20 includes a transceiver circuit 242 that is operative to transmit and receive radio frequency communication signals to the network 10 via an antenna system 246. The antenna system 246 may include an antenna feed structure and one or more antennas. As is well known to those of skill in the art, a transmitter portion of the transceiver 242 converts the information which is to be transmitted by the mobile terminal 20 into electromagnetic signals suitable for radio communications. A receiver portion of the transceiver 242 demodulates electromagnetic signals which are received by the mobile terminal 20 from the network 10 to provide the information contained in the signals in a format which is understandable to the user. [0039]A user interface 244 of the mobile terminal 20 may include a variety of components, such as a display 254, a keypad 252, a speaker 256, and a microphone 250, operations of which are known to those of skill in the art. It will be understood that the functions of keypad 252 and the display 254 can be provided by a touch screen. The display may be used to provide images or graphics which the user can view, such as a map with a grid including collected parameters overlaid thereon, wherein the map represents a geographic area of interest to the user in a particular context, such as traveling to/from work, shopping, entertaining, or the like. [0040]A processor circuit 251 provides for overall operation of the mobile terminal 20 including coordination of communications via the transceiver circuit 242, the user interface 244, and other components and systems included in the mobile terminal 20. For example, the processor circuit 251 can provide communications signals to the transceiver 242 when the user speaks into the microphone 250 and receives communications signals from the transceiver 242 for the reproduction of audio through the speaker 256. The processor circuit 251 can generate characters for display on the display 254. For example, the processor circuit 251 can generate numbers for display when the user enters a telephone number on the keypad 252. The characters can also be generated by a character generator circuit which is not shown. [0041]The processor circuit 251 may be implemented using a variety of hardware and software. For example, operations of the processor circuit 251 may be implemented using special-purpose hardware, such as an Application Specific Integrated Circuit (ASIC) and programmable logic devices such as gate arrays, and/or software or firmware running on a computing device such as a microprocessor, microcontroller or digital signal processor (DSP). [0042]The mobile terminal 20 includes a SIM card 225. The SIM card 225 can be installed (or removed) from the mobile terminal 20 by inserting (or removing) the SIM card 225 into/from a SIM card holder. The SIM card 225 stores information, such as an International Mobile Subscriber Identity (IMSI) that identifies the subscriber to the network 10 and a secret key for authentication. In some embodiments according to the invention, the IMSI includes a 3-digit Mobile Country Code (MCC) which identifies the country and a 2-digit Mobile Network Code (MNC) which identifies the network within that country. It will be understood that the SIM card 225 can store data, such as maps representing geographic areas in which the mobile terminal may be used and can be displayed thereon. The SIM card 225 can also store selectable contexts that can be used to process the parameter data [0043]The SIM card 225 can also store selectable context information that can be applied to the mobile terminal density information provided to the mobile terminal 20. For example, the SIM card 225 may store selectable context such as a shopping context, an entertainment context, a traveling context, etc. It will be also understood that the selectable contexts stored by the SIM card 225 may be further subdivided into subcontexts. For example, the traveling context, discussed herein in reference to FIG. 4, may be further subdivided into a commuting to work context and a commuting from work context. In this way, the contexts may be hierarchically/logically related to one another so that each selectable context may be easier to locate and apply. [0044]In some embodiments according to the invention, the selectable context information can be stored in other types of internal or external non-volatile memory such as a Multi Media Card (MMC), a Secure Digital (SD) card, a Compact Flash (CF) card, a memory stick, and/or a Universal Serial Bus based non-volatile memory device. [0045]It will be understood that the selectable contexts can indicate which of the mobile terminal density information is to be displayed and which of the mobile terminal density information may be suppressed to, for example, simplify the display of mobile terminal density information for the user. The processor circuit 251 can apply the mobile terminal density information to the selectable context to provide a geographic display (on the display 254) that is associated with the selectable context. [0046]A memory 253 can store computer program instructions that, when executed by the processor circuit 251, carry out the operations described herein and shown in the figures. The memory 253 can be non-volatile memory, such as EEPROM (or flash memory), that retains the stored data while power is removed from the memory 253 to enable the storage of information, such as the WAP profile described above, to provide access to the network for the mobile terminal 20. [0047]The mobile terminal 20 may also include a camera 226 that is configured to generate image data corresponding to images sampled by the camera 226. For example, the camera 226 can be used to capture an image and/or video that may be reported as a parameter as discussed herein so that mobile terminal density information may be based on content of the image. [0048]The mobile terminal 20 shown in FIG. 2 also includes a geographic location circuit 260 that is configured to determine the geographic location of the mobile terminal using, for example, conventional GPS approaches (assisted or otherwise) known to those skilled in the art. It will be further understood that the geographic location circuit 260 can use other techniques to determine the mobile terminal geographic location information provided to the location server 135. As described herein, the mobile terminal geographic location information determined by the geographic location circuit 260 can be transmitted as a parameter on which the mobile terminal density information can be based. [0049]The mobile terminal 20 also includes a local wireless interface circuit 265 that can provide communication with the local wireless networks and devices associated therewith. In some embodiments according to the invention, the local wireless interface circuit 265 is a Bluetooth compliant interface. In some embodiments according to the invention, the local wireless interface circuit 265 is a WLAN compliant interface. [0050]The mobile terminal 20 can report parameters collected by the mobile terminal 20 to the network 10 via, for example, the base station 30. Some of the parameters that can be collected by the mobile terminal 20 include the geographic location of the mobile terminal, the velocity of the mobile terminal 20, an audio level sampled by the mobile terminal 20, image/video data, device type tag, and/or connectivity to other mobile terminals in the area. For example, the microphone 250 can be used to sample the ambient audio level in the local environment to provide the audio level parameter. The audio level parameter may be used to determine (at least in part) environmental parameters near the mobile terminal 20. A high audio level may indicate, for example, traffic congestion, construction, and other situations which may indicate higher or lower densities than may otherwise be evident. If the mobile terminal 20 samples an unusually high level of audio, it may be determined that there is an increased likelihood of congestion even though relatively few mobile terminals have been otherwise detected. In some embodiments according to the invention, the speaker 256 can be used to sample the ambient audio level in the local environment to provide the audio level parameter. [0051]The device type tag parameter can indicate the type of device that is reporting the parameters. The device type tag can include, for example, car (i.e., where the device is integrated into a car), personal digital assistant, laptop, cellphone, or the like. In some embodiments according to the invention, the device type tag parameter can change as the use or configuration of the device changes. For example, a cellphone device type tag may change (or be further defined) from “cellphone” to “cellphone/car” when the cellphone is connected to an auxiliary power outlet in a car. [0052]The connectivity parameter may indicate the presence of other mobile terminals in the area which may not be suitably equipped with geographic location circuits or may not participate in the same communications network. Accordingly, the presence of these otherwise undetected mobile terminals may be considered in determining mobile terminal density information. The connectivity parameter may be collected by the mobile terminal 20 using the local wireless interface circuit 265 that can detect, for example, the presence of a mobile terminal 270 within range of the local wireless interface circuit 265. It will be understood that the connectivity parameter can be further defined using the device type tag parameters described above. For example, each of the other mobile terminals in the area that are in communication with the mobile terminal 20 reporting the parameters can have an associated device type tag parameter so that when the connectivity parameter is reported, the system can further define what types of terminals are local to the mobile terminal 20 (which may be used to provide more accurate density information). [0053]In some embodiments according to the invention, the connectivity parameter may also specify a geographical location that the mobile terminal 20 retrieved from another device, such as the mobile terminal 270, if for example, the mobile terminal 20 is not itself equipped with a geographic location circuit or is temporarily unable to determine it's own position using a geographic location circuit. [0054]FIG. 3A is a schematic diagram that illustrates the collection of parameters that may be used to determine mobile terminal density information according to some embodiments of the invention. In particular, the mobile terminal 20 can collect connectivity information based on a number of other mobile terminals brought within range of the local wireless interface discussed above in reference to FIG. 2. Furthermore, the mobile terminal 20 may sample the ambient audio level to provide the audio level parameter which may also be used in determining the mobile terminal density information. [0055]It will be understood that the parameters collected by the mobile terminal 20 may be weighted based on the type of parameter which is collected or based on which other types of parameters are collected and/or how many mobile terminals are currently providing parameters within a particular geographic area. For example, the audio level parameter may be weighted comparatively less than location information reported by the mobile terminal 20 whereas the connectivity parameter may be weighted more than the audio level parameter but less than the location information reported by the mobile terminal. [0056]FIG. 3B is a schematic illustration depicting mobile terminals operating in a geographic area serviced by the network 10. According to FIG. 3B, mobile terminals 20 are shown at various positions within the geographic area including located on or at roadways, shopping areas, entertainment areas and other areas. The number of mobile terminals 20, as well as the spacings thereof, depicts the density of mobile terminals in the specific areas. For example, a first area 310 is relatively densely populated with mobile terminals 20 whereas a second area 312 is less densely populated with mobile terminals 20. A third area 313 includes an entertainment/shopping area populated by mobile terminals 20, which may be moving more slowly than those shown in the first and second areas 312 and 313 (or may even be stationary). [0057]According to some embodiments of the invention, mobile terminals 20 report parameters to a mobile terminal density information server (hereinafter the “server”) 305. It will be understood that the reporting of the parameters by the mobile terminals 20 can be done in an ad-hoc fashion wherein no request is required from the server 305 for the individual mobile terminals 20 to report parameters. It will be further understood that the reporting may be done in other ways, such as, using a synchronous type approach wherein mobile terminals 20 report at pre-assigned times or in response to a specific request from the server 305. It will be further understood that the server 305 may be directly connected to the network 10 or, alternatively, it may be indirectly coupled to the network 10 via a separate network, such as the Internet. In such embodiments where the server 305 is indirectly coupled to the network 10, the mobile terminal may report parameters via other networks, such as a WLAN, a Bluetooth network, etc. [0058]The server 305 receives the parameters from the mobile terminals 20 and compiles the parameters to provide the mobile terminal density information. As described above, the mobile terminal density information may be based upon various parameters reported by the mobile terminals such as geographic location, connectivity, velocity, image data, audio level, and other parameters. Furthermore, the parameters may be weighted differently in determining the mobile terminal density information to provide an overall more accurate indication of the density information for the user. For example, as described above, connectivity information may be used in conjunction with geographic information reported by a mobile terminal 20 to increase an estimate of the number of, for example, people at a specific geographic location even though the devices connected to the mobile terminal 20 may not be in communication with the network 10 or may not be equipped with geographic location circuitry as described above. [0059]The mobile terminal density information may be a statistical representation of, for example, the number of mobile terminals estimated to be located within a geographic area at a particular time. The statistical representation can be any type known to those skilled in the art, such as a moving average. [0060]It will be further understood that the parameters compiled by the server 305 to provide the mobile terminal density information may be treated as “context independent” so that the information may be interpreted differently depending on circumstances so that the data integrity of the server 305 may be preserved. Further, a context may be applied to the information as p(String), 发明技术领域 [0001] 本发明总体上涉及电子领域,更具体地,涉及用于电子通信的方法、移动终端和计算机程序产品。 相关技术说明 [0002] 已知从在无线通信网络中操作的移动终端收集环境参数,例如与天气相关的参数。 例如,美国专利。 麦克唐纳等人的第 6,567,661 号。 题为“分布式遥测方法和系统”讨论了一种分布式遥测方法,通过协调移动电话用户获取读数或参数来实现。 参数读数可以与用户的位置一起发送到服务系统。 整理读数和位置信息可以生成测量参数的地理变化的表示(例如,参见 McDonnell 的摘要)。 [0003] 还已知跟踪给定区域内的车载蜂窝电话以提供用于控制交通系统的数据。 例如,美国专利。 授予 Myr 的第 6,539,300 号,题为“基于无线电话网络的交通控制的区域系统范围最佳信号定时方法”。 讨论了从基于车辆的蜂窝电话获取信号以提供关于移动车辆的位置信息,这些信息被输入到智能交通控制系统以提供位置信息。 数学模型可以使用信息和数字地图/算法来计算实际旅行时间(例如,参见 Myr 的摘要)。 [0004] 以下参考文献中讨论了其他类型的系统:EP 1191802; JP 11/223674; JP 2002/341053; JP 2003/329779; 美国专利 第6,236,933号; 美国 2003/100317; WO 02/27691; 美国专利 第6,427,113号; 和 DE 10237906。尽管有上述材料,但仍需要改进对从移动终端收集的参数的使用。 概括 [0005] 根据本发明的实施例可以提供用于显示移动终端密度信息的方法、移动终端和计算机程序产品。 根据这些实施例,提供关于移动终端的信息的方法可以包括根据基于由在无线通信网络中操作的移动终端向服务器报告的参数的可选上下文,在移动终端显示器上显示移动终端密度信息。 [0006] 在根据本发明的一些实施例中,该方法还包括通过移动终端的自组织报告在服务器处从移动终端接收参数。 可以对参数进行编译,提供移动终端密度信息,并将移动终端密度信息传送到移动终端进行显示。 [0007] 在根据本发明的一些实施例中,可以将移动终端密度信息应用​​于可选上下文以生成与上下文相关联的地理显示。 在根据本发明的一些实施例中,与上下文相关联的地理显示是地图和覆盖在其上的多个位置网格。 [0008] 在根据本发明的一些实施例中,密度信息还包括与移动终端相关联的速度信息。 基于与多个网格位置中的选定位置相关联的移动终端密度信息,可以用颜色和不透明度值来渲染多个网格位置中的选定位置。 [0009] 在根据本发明的一些实施例中,最大不透明度值小于不透明值,使得通过以最大不透明度值覆盖在其上的多个网格位置可以看到底层地图。 在根据本发明的一些实施例中,颜色值是位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的速度的统计表示。 在根据本发明的一些实施例中,不透明度值是位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的密度的统计表示。 [0010]在根据本发明的一些实施例中,可选上下文是从多个可选上下文中选择的第一可选上下文,其中移动终端密度信息中的一些根据第一可选上下文被抑制并且根据第二可选上下文不被抑制。 [0011] 在根据本发明的一些实施例中,可选择的上下文可以是购物上下文、通勤上下文和/或娱乐上下文。 在根据本发明的一些实施例中,可选择的上下文包括子上下文。 在根据本发明的一些实施例中,参数可以是位置信息、速度信息、连接信息、图像/视频信息和/或音频信息。 附图的简要说明 [0012] 图1是图示根据本发明的一些实施例的向移动终端提供服务的无线通信网络的实施例的示意图。 [0013] 图2是说明根据本发明一些实施例的移动终端的框图。 [0014] 图3A是示出根据本发明一些实施例的由移动终端上报的参数收集的示意图。 [0015] 图3B是说明根据本发明一些实施例的移动终端密度系统的示意图。 [0016] 图4是示出根据本发明一些实施例的移动终端上的地理显示的示意图。 [0017] 图5是示出根据本发明一些实施例的移动终端上的地理显示的示意图。 [0018] 图6A是示出根据本发明一些实施例的移动终端上的地理显示的示意图。 [0019] 图6B是图6A的一部分的放大图,其示出了根据可选择的上下文显示一些移动终端密度信息。 [0020] 图6C是图6A的一部分的放大图,示出了根据可选择的上下文显示一些移动终端密度信息。 [0021] 图7是说明根据本发明一些实施例的移动终端的操作的流程图。 根据本发明的实施方案的详细说明 [0022] 下文将参照附图更全面地描述本发明,其中示出了本发明的说明性实施例。 然而,本发明可以以许多不同的形式体现,并且不应被解释为限于本文所阐述的实施例; 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明的范围充分传达给本领域技术人员。 相同的数字始终指代相同的元素。 如本文所用,术语“和/或”包括一个或多个相关列出的项目的任何和所有组合。 [0023] 除非另有定义,本文使用的所有术语(包括技术和科学术语)与本发明所属领域的普通技术人员通常理解的含义相同。 将进一步理解,术语,例如在常用字典中定义的术语,应被解释为具有与其在相关技术的上下文中的含义一致的含义,并且不会以理想化或过于正式的意义来解释,除非 在此明确如此定义。 [0024] 应当理解,尽管术语第一和第二可以在本文中用于描述各种组件,但这些组件不应受这些术语的限制。 这些术语仅用于区分一个组件与另一个组件。 因此,例如,在不背离本发明的教导的情况下,下面讨论的第一组件可以被称为第二组件。 [0025]参考根据本发明实施例的移动终端、通信网络及其操作的流程图和框图来描述本发明。 应当理解,流程图和/或框图的每个块,以及块的组合,可以由计算机程序指令来实现。 这些计算机程序指令可以被提供给通用计算机、专用计算机或其他可编程数据处理装置的处理器以生产机器,使得通过计算机或其他可编程数据处理装置的处理器执行的指令 ,创建用于实现流程图和/或示意图块或块中指定的功能的装置。 [0026] 应当理解,本发明可以用在通信网络中操作的任何移动终端来实践。 例如,移动终端可以是具有或不具有多线显示器的单模或双模蜂窝无线电话; 个人通信系统(PCS)终端,可以将蜂窝无线电话与数据处理、传真和数据通信能力相结合; 可以包括移动终端、寻呼机的个人数据助理 (PDA)。 Internet/Intranet 访问、Web 浏览器、管理器、日历和/或全球定位系统 (GPS) 接收器:以及传统的膝上型电脑和/或掌上型接收器或其他设备,所有这些都包括收发器。 [0027] 应当理解,根据本发明的移动终端可以在任何类型的无线通信网络中操作。 在根据本发明的一些实施例中,例如,网络可以提供广泛标记为PCS(个人通信服务)的服务,包括符合诸如IS-136和IS-95的标准的高级数字蜂窝系统、诸如DECT的低功率系统 (数字增强型无绳电话)、诸如 CDPD(蜂窝数字分组数据)之类的数据通信服务,以及诸如 CDMA-2000 之类的其他系统,它们被提出使用通常称为宽带码分多址 (WCDMA) 的格式。 [0028] 根据本发明的移动终端还可用于天体通信网络,例如卫星通信网络。 天体无线通信网络可用于执行与图1的通信网络执行的功能相似的功能。具体而言,天体无线通信系统通常包括一个或多个卫星,它们用作一个或多个地球站和地球站之间的中继器或转发器。 (卫星)移动终端。 卫星通常通过双工通信链路与卫星移动终端和地球站通信。 每个地球站又可以连接到陆地通信网络中的公共交换电话网络(PSTN),从而允许卫星移动终端和网络服务的其他设备之间的通信。 [0029] 图1是说明无线通信网络(以下称为“网络”)的图 10 支持移动终端的通信 20 根据本发明可以使用。 网络 10 例如,通常采用上述标准向用户提供语音和数据通信。 根据图1,多个移动终端 20 可以互相和其他终端通信,比如终端 26 , 28 , 通过网络 10 和一个 PSTN 14 . [0030] 无线通信网络 10 被组织为单元格 1 - 2 可以共同为一个地理区域提供服务。 特别地,每个小区可以为网络覆盖的地理区域中包括的相关子区域提供服务 10 . 网络中可以包含更多或更少的单元 10 ,以及小区的覆盖区域 1 - 2 可能重叠。 每个细胞 1 - 2 可能包括相关的基站 30 a - b . 基站 30 a - b 可以提供彼此与移动终端之间的无线通信 20在相关的地理区域中,以允许它们之间的通信。 [0031] 每个基站 30 a - b 可以向/从移动终端发送/接收数据 20 通过相关的控制信道 22 . 例如,基站 30 a 在单元格中 1 可与移动端通讯 20 通过控制通道 22 . 控制通道 22 可用于,例如,对移动终端进行寻呼 20 响应指向它的呼叫或向移动终端发送业务信道分配 20 将在其上进行与其相关联的呼叫。 控制通道 22 可以使用控制信道号或标识符来识别。 例如,移动终端 20 可以存储一个标识控制通道的通道号 22 作为它当前驻留的控制通道。 尽管仅图示了一个控制信道,但是应当理解,每个移动终端 20 可能有各自的控制通道 22 与之相关的。 [0032] 移动终端 20 配置为向网络注册 10 例如,当打开移动终端时。 特别地,移动终端使用存储在相应移动终端中的SIM卡上的信息向网络注册 10 . 一旦移动终端 20 在网络上注册 10 , 移动终端 20 可以接收来自无线通信网络的服务 10 ,例如通过无线通信网络拨打和接听电话 10 作为移动终端 20 在网络服务的地理区域内移动 10 . [0033] 移动终端 20 也可能能够通过相应的控制信道发送和接收消息 22 . 在根据本发明的一些实施例中,移动终端发送/接收短消息服务(SMS)或增强型消息服务(EMS)格式的消息、多媒体消息服务(MMS)和/或Smartmessaging TM 格式的消息。 如本领域技术人员所知,SMS和EMS消息可以在诸如GSM网络的数字网络上传输,允许通过网络运营商的消息发送和接收相对较小的文本消息(例如,160个字符大小) 中心到移动端 20 ,或从 Internet,使用所谓的 SMS(或 EMS)“网关”网站。 [0034] MMS 是一种用于异步移动到移动消息传递的消息传递系统,它支持包含“富媒体”内容的消息的通信,即比文本数据更密集的类型的内容,例如图形、数码照片 、视频、动画、声音文件和/或音频。 MMS 由 WAP 论坛和第三代合作伙伴项目 (3GPP) 标准化,并在以下内容中进行了描述:“WAP MMS,体系结构概述”,WAP-205,WAP 论坛(2001 年 4 月 25 日批准的版本); “WAP MMS,客户端交易规范”,WAP-206,WAP 论坛(2002 年 1 月 15 日批准的版本); “WAP MMS,封装规范”,WAP-209,WAP 论坛(2002 年 1 月 5 日批准版本); “要求”,3GPP 规范 22.140; 和“架构和功能”,3GPP 规范 23.140。 [0035] WAP 已被颁布,通过为无线信息和电话服务的呈现和传递提供标准,使编写的应用程序能够在广泛的无线通信网络上运行。 结果,各种移动终端,例如移动终端、寻呼机、双向无线电、智能手机和通信器,可以利用WAP来实现向移动终端传递相关信息和服务。 [0036] 因此,将理解,如本文进一步描述的,控制信道 22 可用于向移动终端传输移动终端密度信息 20 通过 WAP 客户端作为 SMS、MMS、EMS 或其他类型的消息。 在根据本发明的一些实施例中,可以将移动终端密度信息提供给移动终端 20通过“Midlet”。 正如本领域技术人员所熟知的,Midlet 是一种Java 应用程序,被设计为在支持Java 的设备上运行,例如手机和PDA。 Midlet 基于 Java 2 平台微型版,使用连接的有限设备配置 (CLDC),CLDC 定义了一组应用程序编程接口和用于资源受限设备的虚拟机,例如这里讨论的那些。 在 Internet 上的“www.sun.com”上进一步讨论了 Midlet。 将进一步理解,诸如地图和其他动态图形数据的其他信息也可以在合适的消息中传输,包括任何或所有上述消息类型。 [0037] 图2是说明移动终端的框图 20 根据本发明的一些实施例。 根据本发明的一些实施例,基于移动终端上报的参数将移动终端密度信息发送到移动终端进行显示。 移动终端密度信息可以是例如估计在特定时间位于地理区域内的移动终端的数量的统计表示。 [0038] 如图2所示,移动终端 20 包括收发器电路 242 用于向网络发送和接收射频通信信号 10 通过天线系统 246 . 天线系统 246 可以包括天线馈电结构和一个或多个天线。 如本领域技术人员所熟知的,收发器的发射器部分 242 转换移动终端要传输的信息 20 成适合无线电通信的电磁信号。 收发器的接收器部分 242 解调移动终端接收到的电磁信号 20 从网络 10 以用户可以理解的格式提供信号中包含的信息。 [0039] 用户界面 244 移动终端的 20 可能包括各种组件,例如显示器 254 , 键盘 252 , 扬声器 256 , 和一个麦克风 250 ,其操作是本领域技术人员已知的。 可以理解小键盘的功能 252 和显示器 254 可以通过触摸屏提供。 显示器可用于提供用户可以查看的图像或图形,例如具有网格的地图,该网格包括叠加在其上的收集的参数,其中该地图表示在特定上下文中用户感兴趣的地理区域,例如旅行到 /来自工作、购物、娱乐等。 [0040] 处理器电路 251 提供移动终端的整体操作 20 包括通过收发器电路协调通信 242 , 用户界面 244 ,以及移动终端中包含的其他组件和系统 20 . 例如处理器电路 251 可以向收发器提供通信信号 242 当用户对着麦克风说话时 250 并接收来自收发器的通信信号 242 用于通过扬声器再现音频 256 . 处理器电路 251 可以生成字符在显示器上显示 254 . 例如处理器电路 251 当用户在键盘上输入电话号码时,可以生成用于显示的数字 252 . 字符也可以由未示出的字符生成器电路生成。 [0041] 处理器电路 251 可以使用各种硬件和软件来实现。 例如,处理器电路的操作 251 可以使用专用硬件(例如专用集成电路(ASIC)和可编程逻辑设备(例如门阵列)和/或在计算设备(例如微处理器、微控制器或数字信号处理器)上运行的软件或固件)来实现。 数字信号处理器)。 [0042] 移动终端 20 包括一张 SIM 卡 225 . SIM 卡 225 可从移动终端安装(或移除)20 通过插入(或取出)SIM 卡 225 进/出 SIM 卡座。 SIM 卡 225 存储信息,例如识别网络订户的国际移动订户身份 (IMSI) 10 和一个用于身份验证的密钥。 在根据本发明的一些实施例中,IMSI包括标识国家的3位移动国家代码(MCC)和标识该国家内的网络的2位移动网络代码(MNC)。 可以理解为SIM卡 225 可以存储数据,例如表示可以使用移动终端并且可以在其上显示的地理区域的地图。 SIM 卡 225 还可以存储可用于处理参数数据的可选上下文 [0043] SIM 卡 225 还可以存储可选择的上下文信息,该上下文信息可以应用于提供给移动终端的移动终端密度信息 20 . 例如,SIM 卡 225 可以存储可选上下文,例如购物上下文、娱乐上下文、旅行上下文等。还可以理解,SIM卡存储的可选上下文 225 可以进一步细分为子上下文。 例如,本文参考图4讨论的旅行环境可以进一步细分为通勤上班环境和下班通勤环境。 以这种方式,上下文可以在层次/逻辑上彼此相关,从而可以更容易地定位和应用每个可选择的上下文。 [0044] 在根据本发明的一些实施例中,可选择的上下文信息可以存储在其他类型的内部或外部非易失性存储器中,例如多媒体卡(MMC)、安全数字(SD)卡、紧凑型闪存(CF) 卡、记忆棒和/或基于通用串行总线的非易失性存储设备。 [0045] 应当理解,可选择的上下文可以指示要显示哪个移动终端密度信息以及可以抑制哪个移动终端密度信息,例如,为用户简化移动终端密度信息的显示。 处理器电路 251 可以将移动终端密度信息应用​​到可选择的上下文中,以提供地理显示(在显示器上 254 ) 与可选择的上下文相关联。 [0046] 一段记忆 253 可以存储计算机程序指令,当由处理器电路执行时 251 ,执行此处描述和图中所示的操作。 记忆 253 可以是非易失性存储器,例如 EEPROM(或闪存),在断电时保留存储的数据 253 启用信息存储,例如上述 WAP 配置文件,为移动终端提供对网络的访问 20 . [0047] 移动终端 20 可能还包括一个相机 226 用于生成与相机采样的图像对应的图像数据 226 . 例如,相机 226 如本文所讨论的,可用于捕获可作为参数报告的图像和/或视频,使得移动终端密度信息可基于图像的内容。 [0048] 移动终端 20 图2所示还包括一个地理位置电路 260 其被配置为使用例如本领域技术人员已知的常规GPS方法(辅助或其他)来确定移动终端的地理位置。 可以进一步理解,地理位置电路 260 可以使用其他技术确定提供给定位服务器的移动终端地理位置信息 135 . 如本文所述,由地理位置电路确定的移动终端地理位置信息 260 可以作为移动终端密度信息可以基于的参数来传输。 [0049] 移动终端 20 还包括一个本地无线接口电路 265可以提供与本地无线网络和与其相关联的设备的通信。 在根据本发明的一些实施例中,本地无线接口电路 265 是蓝牙兼容接口。 在根据本发明的一些实施例中,本地无线接口电路 265 是 WLAN 兼容接口。 [0050] 移动终端 20 可上报手机端采集的参数 20 到网络 10 例如,通过基站 30 . 移动端可采集的部分参数 20 包括移动终端的地理位置、移动终端的速度 20 , 移动端采样的音频电平 20 、图像/视频数据、设备类型标签和/或与该地区其他移动终端的连接。 例如,麦克风 250 可用于对本地环境中的环境音频电平进行采样,以提供音频电平参数。 音频电平参数可用于确定(至少部分)移动终端附近的环境参数 20 . 高音频电平可以指示例如交通拥堵、施工和其他情况,这些情况可以指示比其他方式明显的更高或更低的密度。 如果移动端 20 如果对异常高水平的音频进行采样,则可以确定拥塞的可能性增加,即使以其他方式检测到相对较少的移动终端也是如此。 在根据本发明的一些实施例中,扬声器 256 可用于对本地环境中的环境音频电平进行采样,以提供音频电平参数。 [0051] 设备类型标签参数可以指示报告参数的设备类型。 设备类型标签可以包括例如汽车(即,设备被集成到汽车中的地方)、个人数字助理、膝上型电脑、手机等。 在根据本发明的一些实施例中,设备类型标签参数可以随着设备的使用或配置的改变而改变。 例如,当手机连接到汽车中的辅助电源插座时,手机设备类型标签可以从“手机”改变(或进一步定义)为“手机/汽车”。 [0052] 连接参数可以指示该区域中可能没有适当地配备有地理位置电路或者可能不参与同一通信网络的其他移动终端的存在。 因此,在确定移动终端密度信息时可以考虑这些否则未被检测到的移动终端的存在。 连接参数可以由移动终端采集 20 使用本地无线接口电路 265 例如,可以检测移动终端的存在 270 在本地无线接口电路范围内 265 . 应当理解,可以使用上述设备类型标签参数进一步定义连接参数。 例如,该区域中与该移动终端通信的其他移动终端中的每一个 20 上报参数可以有关联的设备类型标签参数,以便在上报连通性参数时,系统可以进一步定义移动终端本地的终端类型 20 (可用于提供更准确的密度信息)。 [0053] 在根据本发明的一些实施例中,连接参数还可以指定移动终端的地理位置 20 从其他设备检索,例如移动终端 270 ,例如,如果移动终端 20 本身没有配备地理位置电路或暂时无法使用地理位置电路确定自己的位置。 [0054] 图3A是图示根据本发明的一些实施例的可用于确定移动终端密度信息的参数的集合的示意图。 尤其是移动终端 20可以基于被带入以上参考图2讨论的本地无线接口范围内的多个其他移动终端来收集连接信息。此外,移动终端 20 可以对环境音频电平进行采样以提供也可以用于确定移动终端密度信息的音频电平参数。 [0055] 可以理解为移动端采集的参数 20 可以基于收集的参数的类型或基于收集哪些其他类型的参数和/或当前有多少移动终端在特定地理区域内提供参数来加权。 例如,音频电平参数的权重可能小于移动终端上报的位置信息 20 而连通性参数的权重可以大于音频电平参数,但小于移动终端上报的位置信息。 [0056] 图3B是描绘在由网络服务的地理区域中操作的移动终端的示意图 10 . 根据图 3B,移动终端 20 显示在地理区域内的不同位置,包括位于道路、购物区、娱乐区和其他区域上或处。 移动终端数量 20 ,以及它们的间距,描绘了特定区域中移动终端的密度。 例如,第一个区域 310 移动终端相对密集 20 而第二个区域 312 移动终端人口较少 20 . 第三个区域 313 包括一个由移动终端组成的娱乐/购物区 20 ,它的移动速度可能比第一个和第二个区域中显示的要慢 312 和 313 (甚至可能是静止的)。 [0057] 根据本发明的一些实施例,移动终端 20 向移动终端密度信息服务器(以下简称“服务器”)上报参数 305 . 可以理解的是,移动终端的参数上报 20 可以以 ad-hoc 方式完成,其中不需要来自服务器的请求 305 用于个人移动终端 20 报告参数。 将进一步理解,报告可以以其他方式完成,例如,使用同步类型的方法,其中移动终端 20 在预先指定的时间或响应来自服务器的特定请求进行报告 305 . 可以进一步理解,服务器 305 可以直接连接到网络 10 或者,它可以间接耦合到网络 10 通过单独的网络,例如 Internet。 在这样的实施例中,服务器 305 间接耦合到网络 10 ,移动终端可以通过其他网络上报参数,例如WLAN、蓝牙网络等。 [0058] 服务器 305 从移动终端接收参数 20 并编译参数以提供移动终端密度信息。 如上所述,移动终端密度信息可以基于移动终端报告的各种参数,例如地理位置、连接性、速度、图像数据、音频电平和其他参数。 此外,在确定移动终端密度信息时可以对参数进行不同的加权,以便为用户提供密度信息的整体更准确的指示。 例如,如上所述,连接信息可以与移动终端报告的地理信息结合使用 20 增加对特定地理位置的人数的估计,例如,即使设备连接到移动终端 20 可能无法与网络通信 10 或者可能没有配备如上所述的地理位置电路。 [0059]移动终端密度信息可以是例如估计在特定时间位于地理区域内的移动终端的数量的统计表示。 统计表示可以是本领域技术人员已知的任何类型,例如移动平均。 [0060] 进一步理解,服务器编译的参数 305 提供移动终端密度信息可能会被视为“上下文无关”,以便根据情况对信息进行不同的解释,从而保证服务器的数据完整性 305 可以保留。 此外,上下文可以作为解释的一部分由例如移动终端处的用户应用于信息。 因此,无需对服务器功能进行重大更改即可收集和报告新类型的参数 305 . 将进一步理解,在根据本发明的一些实施例中,可以基于一天中的时间应用可选择的上下文,例如在早上通勤期间或下午通勤期间,其中可以在不同时间应用不同上下文。 [0061] 服务器 305 向移动终端发送移动终端密度信息 20 (通过移动交换中心 15 )其中可选择的上下文可以应用于其上显示的移动终端密度信息。 可以理解的是,向移动终端发送的移动终端密度信息 20 只能包含移动终端的密度值。 在根据本发明的又一实施例中,向移动终端发送移动终端密度信息 20 可以包括移动终端密度值和移动终端密度值应用到的网格位置。 相应地,移动终端密度信息和网格位置可以叠加在移动终端显示的地图上 20 例如,传达与拥塞相关的信息,这些信息可能对用户在特定时间选择目的地或到特定目的地的更好路线有用。 [0062] 如上所述,移动终端密度信息可以通过移动终端在其上的控制信道发送。 20 正在露营。 或者,在根据本发明的一些实施例中,移动终端密度信息和网格位置可以使用诸如SMS或MMS格式的消息之类的消息来传输,如果移动终端如此配备的话。 或者,该信息可以通过GPRS或其他通用数据信道传输。 [0063] 在根据本发明的一些实施例中,从服务器发送到移动终端的移动终端密度信息 20 可以包括基于与特定网格位置相关联的移动终端密度信息的颜色和不透明度值。 例如,特定网格位置的颜色值可以指示位于对应于网格位置的地理区域中的移动终端的平均速度。 不透明度值可以表示位于对应于各个网格位置的地理区域中的移动终端的密度。 [0064] 可以组合颜色和不透明度值以将网格位置渲染到移动终端的显示上 20 传达有关该网格位置内的交通流量以及交通密度的信息。 例如,在根据本发明的一些实施例中,红色值可以指示该网格位置中的相对低的速度并且相对不透明的不透明度值可以指示相对高的交通密度。 相反,绿色值可以指示该网格位置中的相对较高的速度,而相对低的不透明度值可以指示相对较轻的交通。 在根据本发明的一些实施例中,可以限制不透明度值,使得最大不透明度值允许移动终端的显示器上的基础地图 20 即使不透明度相对较高,也可以通过网格位置查看。 [0065]图4是根据本发明一些实施例的移动终端密度信息的显示示意图。 具体地,在移动终端上显示图4所示的移动终端密度信息 20 由处理器电路 251 通过应用可选择的上下文,使得一些移动终端密度信息被抑制,而其他移动终端密度信息不被抑制,因此显示在移动终端上 20 . 在根据本发明的一些实施例中,图4中应用的可选择上下文可以是旅行上下文的子上下文,例如“通勤上班上下文”。 在“上班通勤”子上下文中,已知用户遵循从住宅到办公室的特定路线。 [0066] 因此,可以抑制与预定路线之外的网格位置相对应的移动终端密度信息。 例如,如图4所示,区域上网格位置对应的移动终端密度信息 313 可以抑制图3B中的。 同样,一个区域 415 对应于用户通常不从住宅到办公室行驶的高速公路也被抑制。 将进一步理解,可选择的上下文可以基于诸如周一至周五早上的工作日时间自动选择并应用于移动终端密度信息。 或者,该可选上下文可以由用户手动选择。 在根据本发明的更进一步的实施例中,可选择的上下文可以基于移动终端的地理位置自动选择 20 当用户在网络服务的区域中移动时 10 . [0067] 图5是示出根据本发明的一些实施例的可选上下文应用于移动终端密度信息的示意图。 特别地,与图4中应用的上下文相反,图5中应用的可选择上下文可以被称为“通勤回家”上下文。 在“通勤回家”上下文中,可以抑制与用户通常不经过的道路上的网格位置相对应的部分移动终端密度信息。 将进一步理解,与报告移动终端相关联的设备类型标签可以在“通勤回家”上下文中使用以确定是否应该显示或抑制密度信息。 例如,与报告移动终端相关联的“汽车”设备类型标签可能与该上下文中的显示器相关,而与“手机”设备类型标签相关联的密度信息被抑制。 [0068] 图6A是图示根据本发明的一些实施例的将可选上下文应用于移动终端密度信息的示意图。 特别地,图6A图示了可被称为“娱乐/购物”上下文的可选上下文的应用。 特别地,如图6A所示,通常与如图4和5所示的“通勤”上下文相关联的移动终端密度信息可以被抑制,而与已知与娱乐和购物相关的其他地理区域相关联的移动终端密度信息 可在移动端显示 20 . [0069] 图6B是图6A中A部分的放大图,其中移动终端上显示已知与娱乐相关的地理区域的移动终端密度信息 20 而已知与购物相关的移动终端密度信息被抑制。 相反,图6C是图6A中的部分A的放大图,其中应用了购物上下文,从而显示与购物相关联的移动终端信息并抑制与娱乐相关联的移动终端信息。 [0070]在根据本发明的又一实施例中,可以将这里称为“拥挤”的上下文应用于密度信息,从而可以抑制与与人群无关的移动终端相关的密度信息,而可以显示与人群或拥挤相关的密度信息 . 例如,在根据本发明的一些实施例中,用户可能希望找到比其他地方更受欢迎的当地海滩或娱乐区。 用户由此可以应用拥挤上下文以在移动终端上生成反映与不同地理位置相关联的拥挤程度的移动终端密度信息的显示。 还应理解,设备类型标签参数可用于基于由设备类型标签标识的设备类型来确定是否应抑制或显示与报告移动终端相关联的移动密度信息。 例如,“手机”设备类型标签可能与拥挤环境中移动终端密度信息的显示相关,而“汽车”设备类型标签可能不相关。 因此,可以抑制与汽车设备类型标签相关联的任何移动终端密度信息,而可以显示与蜂窝电话设备类型标签相关联的移动终端密度信息。 在根据本发明的进一步实施例中,设备类型标签可以应用在“停车”上下文中,其中例如与汽车相关联的设备类型标签被显示,而具有其他类型标签的移动终端报告的移动终端密度信息可以是 压制。 因此,用户可以更有效地定位停车可能更可用的区域,或者可替代地,可以避开停车不太可能可用的区域。 [0071] 根据图7,移动终端参数由移动终端报告并在服务器使用例如ad-hoc报告机制(块 705 )。 如上所述,参数可以包括地理位置信息、速度信息、连接信息、音频电平信息、设备类型标签等。服务器编译参数以提供移动终端密度信息(块 710 )。 移动终端密度信息可以通过对某些参数的权重大于或小于其他参数来编制。 例如,连接性参数信息可以指示报告移动终端附近的其他移动终端,因此可以指示增加的密度,否则这可能不明显,因为那些其他移动终端可能不在无线通信网络内操作。 [0072] 在根据本发明的一些实施例中,移动终端报告的速度信息可用于间接确定移动终端密度信息的指示。 例如,速度可以被认为与密度成反比,使得与地理位置相关联的相对高的速度值可以指示报告移动终端的相对低的密度信息。 另一方面,与地理位置相关联的相对低的速度值可以指示报告移动终端的相对高密度的信息。 [0073] 这些参数将被收集并与对应于最终将在移动终端的显示器上呈现(作为密度信息)的网格位置(i,j)的地理位置相关联。 将理解,与编译参数相关联的网格位置(i,j)对应于网络内的地理区域,该地理区域大到足以覆盖足以表示来自移动终端的足够数量的报告的区域。 将进一步理解,对应于网格位置(i,j)的地理区域也应该足够小以提供关于最终显示的移动终端密度信息的相对精细的细节。 将理解,网格位置(i,j)可以是统一的或基于例如从每个网格位置(i,j)报告多少参数而改变大小。 [0074]在根据本发明的一些实施例中,由移动终端报告的地理位置信息和速度参数与要显示的特定网格位置相关联。 例如,可以使用以下等式将特定网格位置的速度参数编译为随时间推移的移动平均值: 速度 i,j ←c·速度+(1−c)·速度 i,j n i,j ←n i,j +1 [0075] 其中 c=1/m,m 是移动平均值中包含的速度值的数量。 为了避免在特定网格位置处的速度值随时间饱和,读数计数可随时间降低,例如通过将值减小一定百分比的规则时间间隔。 尽管参考速度信息的编译描述了以上引用的方程,但是应当理解,相同或类似类型的处理可以用于编译移动终端报告的其他参数。 还应理解,如果移动终端配备有地理位置电路,例如GPS,还可以包括高度信息参数,从而可以为移动终端的二维显示呈现三维表示。 终端,其中呈现的第三维度可以表示作为高度函数的密度信息。 [0076] 将移动终端密度信息传送到移动终端(块 715 )。 如本文所讨论的,移动终端密度信息可以包括其密度的统计表示(例如移动平均值)并且还可以包括不透明度值,该不透明度值可以用于呈现网格上的位置,该网格覆盖在显示器上显示的地图上 的移动终端。 密度信息可以以可缩放矢量图形 (SVG) 格式传输。 正如本领域技术人员所熟知的,SVG是一种用于以XML描述二维图形和图形应用的语言。 SVG 1.1 是当前的 W3C 建议,构成当前 SVG 开发的核​​心,旨在用于资源有限的设备,例如 3GPP 平台第三代手机。 可选择的上下文应用于移动终端的密度信息,并以网格的形式叠加在地图上,以便在移动端显示(块 720 )。 [0077] 在不脱离本发明的精神和范围的情况下,本领域的普通技术人员在受益于本公开的情况下可以做出许多改变和修改。 因此,必须理解,所示实施例仅出于示例的目的而阐述,并且不应被视为限制由所附权利要求限定的本发明。 因此,所附权利要求应理解为不仅包括按字面阐述的元件的组合,而且包括用于以基本相同的方式执行基本相同的功能以获得基本相同的结果的所有等效元件。 因此,权利要求应理解为包括以上具体说明和描述的内容、概念上等同的内容以及包含本发明的基本思想的内容。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.883 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101099404A(String), CN101099404B(String), EP1815708A1(String), EP1815708B1(String), US20060105815A1(String), US7522940B2(String), WO2006053694A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.886 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101099404A(String), CN101099404B(String), EP1815708A1(String), EP1815708B1(String), US20060105815A1(String), US7522940B2(String), WO2006053694A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.887 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7522940B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101099404A(String), CN101099404B(String), EP1815708A1(String), EP1815708B1(String), US20060105815A1(String), US7522940B2(String), WO2006053694A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.896 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), CN101099404A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.906 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), CN101099404B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.913 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), EP1815708A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.922 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.923 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), EP1815708B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.929 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.930 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), US20060105815A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), US7522940B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.944 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270704(Integer), WO2006053694A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.952 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7522940B2(String), US7522940B2(String), 1240243200(Integer), 270704(Integer), 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.964 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185028(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 185028(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1681975544(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185028(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75924(Integer), 2(Integer), 185028(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:03.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费 | 权利转移(String), 2(Integer), 185028(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.012 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9549143B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US9549143B2(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择显示在外部显示设备上的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US13/950507(String), 1374681600(Integer), US9549143B2(String), 1484582400(Integer), 1484582400(Integer), 美国(String), 4(Integer), KR(String), 9(Integer), 16(Integer), EP1853061A1 | KR1020110016571A | KR1020110070589A | KR1020110088952A | TW201219871A | TW201224993A | US20020162120A1 | US20030076344A1 | US20110154396A1 | US20120017237A1 | US20120133645A1 | US20120137329A1 | US20130177891A1 | US8112371B1 | WO2011008387A2 | WO2011084950A2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185029(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e26fcd9228144bc0994b6708a48a98d7.png(String), 185029(Integer), e26fcd9228144bc0994b6708a48a98d7.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.034 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US9549143B2(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择显示在外部显示设备上的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US13/950507(String), 1374681600(Integer), US9549143B2(String), 1484582400(Integer), 1484582400(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 9(Integer), 16(Integer), EP1853061A1 | KR1020110016571A | KR1020110070589A | KR1020110088952A | TW201219871A | TW201224993A | US20020162120A1 | US20030076344A1 | US20110154396A1 | US20120017237A1 | US20120133645A1 | US20120137329A1 | US20130177891A1 | US8112371B1 | WO2011008387A2 | WO2011084950A2(String), \20230420\e26fcd9228144bc0994b6708a48a98d7.png(String), 20(Integer), 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 1. A mobile device comprising:a memory storing instructions; anda processor configured to execute the stored instructions to control the mobile device to perform:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects displayed on the external display device based on a first input of a user through the mobile device;requesting, to the external display device, additional information corresponding to the object based on a second input of the user through the mobile device;receiving, from the external display device, the additional information corresponding to the object;displaying a plurality pieces of information related to the object based on the additional information received from the external display device, the additional information including the plurality pieces of information related to the object;requesting a content corresponding to a piece of information from among the plurality pieces of information related to the object; andreceiving the content corresponding to the piece of information.(String), 1.移动设备包括:存储器存储指令;和处理器被配置为执行存储的指令以控制移动设备执行:基于用户通过移动设备的第一输入,向外部显示设备发送用于从显示在外部显示设备上的多个对象中选择对象的信号;基于用户通过移动设备的第二输入向外部显示设备请求对应于对象的附加信息;从外部显示设备接收对象对应的附加信息;基于从外部显示设备接收的附加信息显示与对象相关的多条信息,附加信息包括与对象相关的多条信息;请求与对象相关的多条信息中的一条信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 2. The mobile device of claim 1, wherein the processor is further configured to convert the signal for selecting the object according to a control protocol of the external display device.(String), 2.如权利要求1所述的移动设备,其中处理器还用于根据外部显示设备的控制协议转换用于选择对象的信号。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 3. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to transmit a signal for controlling a movement of a selection region for selecting the object displayed on the external display device.(String), 3.如权利要求1所述的移动设备,其中处理器还被配置为控制移动设备发送用于控制选择区域的移动的信号,该选择区域用于选择显示在外部显示设备上的对象。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 4. The mobile device of claim 3, wherein the processor is further configured to control the mobile device to transmit a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input.(String), 4.如权利要求3所述的移动设备,其中处理器还被配置为控制移动设备发送用于控制选择区域的移动方向、选择区域的移动速度和在外部显示器的屏幕上显示的对象的数量中的至少一项的信号基于第一个输入的设备。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 5. The mobile device of claim 3, wherein the processor is further configured to control the mobile device to display thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 5.如权利要求3所述的移动设备,其中处理器还被配置为在请求附加信息之前控制移动设备显示与其中设置有选择区域的对象对应的缩略图信息。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 6. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to receive link information of the additional information from the external display device based on the second input andreceive the content from a server based on the received link information.(String), 6.如权利要求1所述的移动设备,其中处理器还被配置为基于第二输入控制移动设备从外部显示设备接收附加信息的链接信息,并且基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 7. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to request the content based on a third input of the user through the mobile device.(String), 7.如权利要求1所述的移动设备,其中处理器还被配置为基于用户通过移动设备的第三输入来控制移动设备请求内容。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 8. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to request control authorization from the external display device and receive a control authorization acceptance message from the external display device prior to the transmitting of the signal for selecting the object.(String), 8.如权利要求1所述的移动设备,其中处理器进一步被配置为在发送用于选择对象的信号之前控制移动设备向外部显示设备请求控制授权并且从外部显示设备接收控制授权接受消息。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 9. The mobile device of claim 1, wherein the plurality of objects comprise at least one from among an icon, a link, a picture, a text, and an index item.(String), 9.如权利要求1所述的移动设备,其中多个对象包括图标、链接、图片、文本和索引项中的至少一个。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 10. The mobile device of claim 1, wherein the content comprise at least one from among a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG).(String), 10.如权利要求1所述的移动设备,其中内容包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 11. The mobile device of claim 1, wherein the additional information comprises at least one from among preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information.(String), 11.如权利要求1所述的移动设备,其中附加信息包括预览信息、试听信息、应用信息、用户评论信息、更新信息、报刊文章信息、商品信息、电影信息、游戏信息、广告图片信息、专辑信息中的至少一种。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 12. The mobile device of claim 1, wherein the processor is further configured to control the mobile device todetermine an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generate a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generate a signal for controlling the content displayed on the mobile device based on the user input.(String), 12.如权利要求1所述的移动设备,其中处理器还被配置为控制移动设备以确定移动设备的操作模式;和响应于确定操作模式是第一模式,基于用户输入产生用于控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,产生用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 13. A method in which a mobile device displays information, the method comprising:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects displayed on the external display device based on a first input of a user through the mobile device;requesting, to the external display device, additional information corresponding to the object based on a second input of the user through the mobile device;receiving, from the external display device, the additional information corresponding to the object;displaying a plurality pieces of information related to the object based on the additional information received from the external display device, the additional information including the plurality pieces of information related to the object;requesting a content corresponding to a piece of information from among the plurality pieces of information related to the object; andreceiving the content corresponding to the piece of information.(String), 13.一种方法其中移动设备显示信息,该方法包括:基于用户通过移动设备的第一输入,向外部显示设备发送用于从显示在外部显示设备上的多个对象中选择对象的信号;基于用户通过移动设备的第二输入向外部显示设备请求对应于对象的附加信息;从外部显示设备接收对象对应的附加信息;基于从外部显示设备接收的附加信息显示与对象相关的多条信息,附加信息包括与对象相关的多条信息;请求与对象相关的多条信息中的一条信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 14. The method of claim 13, wherein the transmitting the signal for selecting the object comprises transmitting a signal for controlling a movement of a selection region for selecting the object displayed on the external display device.(String), 14.如权利要求13所述的方法,其中发送用于选择对象的信号包括发送用于控制用于选择显示在外部显示设备上的对象的选择区域的移动的信号。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 15. The method of claim 14, wherein the transmitting the signal for controlling the movement of the selection region comprises transmitting a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input.(String), 15.如权利要求14所述的方法,其中发送用于控制选择区域的移动的信号包括发送用于控制选择区域的移动方向、选择区域的移动速度和显示在选择区域的屏幕上的对象的数量中的至少一项的信号基于第一输入的外部显示设备。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.049 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 16. The method of claim 14, further comprising displaying thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 16.如权利要求14所述的方法,还包括在请求附加信息之前,显示选择区域所在的对象对应的缩略图信息。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 17. The method of claim 13, wherein the receiving the additional information comprises receiving link information of the additional information from the external display device based on the second input and,wherein the receiving the content comprises receiving the content from a server based on the received link information.(String), 17.如权利要求13所述的方法,其中接收附加信息包括基于第二输入从外部显示设备接收附加信息的链接信息,以及,其中,接收内容包括基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 16(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 18. The method of claim 13, wherein the content comprise at least one from among a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG).(String), 18.如权利要求13所述的方法,其中内容包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。(String), 1(Integer), 17(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 19. The method of claim 13, further comprising:determining an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generating a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generating a signal for controlling the content displayed on the mobile device based on the user input.(String), 19.如权利要求13所述的方法,还包括:确定移动设备的操作模式;和响应于确定操作模式是第一模式,生成用于基于用户输入控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,生成用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 18(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.050 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185029(Integer), 20. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method of claim 13.(String), 20.一种非暂时性计算机可读记录介质有在其上记录用于执行权利要求13的方法的程序。(String), 1(Integer), 19(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185029(Integer), CROSS-REFERENCE TO RELATED PATENT APPLICATION [0001]This application claims priority from Korean Patent Application No. 10-2012-0081434, filed on Jul. 25, 2012, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference. BACKGROUND [0002]1. Field [0003]Exemplary embodiments relate to a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object, a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal, and a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0004]2. Description of the Related Art [0005]A smart television (TV) is a multifunctional TV capable of utilizing various functions such as web surfing, video on demand (VOD) watching, a social networking service (SNS), a game, etc. by combining a TV and an Internet access function and installing various applications. [0006]One characteristic of the smart TV is that a user and the TV can transmit and receive information from each other. This is a difference between the smart TV and an existing TV that merely transfers information unilaterally. Thus, the smart TV is also referred to as an interactive TV. [0007]However, it is very inconvenient for the user to use the various functions of the smart TV by using a standard remote controller. In particular, when the user browses or downloads contents, the user needs to manipulate the remote controller through several steps. [0008]Therefore, a control device or system for allowing the user to easily control the smart TV is needed. SUMMARY [0009]Exemplary embodiments provide a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object. [0010]Exemplary embodiments also provide a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal. [0011]Exemplary embodiments also provide a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0012]According to an aspect of an exemplary embodiment, there is provided a method in which a mobile terminal displays information, the method including: transmitting a first signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; transmitting a second signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0013]The transmitting of the first signal for selecting the object may include: converting the signal for selecting the object according to a control protocol of the external display device. [0014]The transmitting of the first signal for selecting the object may include: transmitting a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0015]The transmitting of the signal for controlling the movement of the selection region may include: transmitting a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen of the external display device based on the first input. [0016]The transmitting of the first signal for selecting the object may include: displaying thumbnail information of contents corresponding to the object on the screen of the mobile terminal. [0017]The thumbnail information may include at least one of an image of the contents corresponding to the object, a title of the contents, and a type of the contents. [0018]The transmitting of the first signal for selecting the object may include: displaying a movement direction of the mobile terminal on the screen according to the first input. [0019]The first input and the second input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0020]The first input may include a three-dimensional (3D) motion input for moving the mobile terminal in a 3D direction, wherein the second input includes a rotational motion input for rotating the mobile terminal by more than a predetermined angle. [0021]The transmitting of the second signal for requesting additional information may include: receiving the additional information from the display device. [0022]The transmitting of the second signal for requesting additional information may include: receiving link information of the additional information from the external display device based on the second input; and receiving the additional information from a server based on the received link information. [0023]The transmitting of the first signal for selecting the object to the display device may include: requesting control authorization from the external display device; and receiving a control authorization acceptance message from the external display device. [0024]The contents may include at least one of a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG). [0025]The additional information may include at least one of preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information. [0026]The method may further include: controlling the additional information displayed on the screen of the mobile terminal based on a third input of the user through the mobile terminal. [0027]The controlling of the additional information may include: controlling at least one of displaying of the additional information, playing of the additional information, and changing to previous additional information or next additional information based on the third input of the user through the mobile terminal. [0028]The method may further include: obtaining contents corresponding to the additional information displayed on the screen of the mobile terminal. [0029]According to an aspect of another exemplary embodiment, there is provided a method in which a display device provides information to a mobile terminal, the method including: selecting an object displayed on the display device by receiving a first input of a user through the mobile terminal; and transmitting additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal. [0030]The transmitting may include: extracting the additional information from contents corresponding to the selected object. [0031]The selecting of the object may include: receiving a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal; and moving the selection region according to the control signal. [0032]The selecting of the object may include: converting the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0033]The receiving may include: receiving the control signal for controlling the movement of the selection region from each of a plurality of mobile terminals. [0034]The method may further include: sensing at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0035]The selecting of the object may include: controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0036]The selecting of the object may include: transmitting thumbnail information of contents corresponding to the object to the mobile terminal. [0037]The transmitting of the additional information to the mobile terminal may include: transmitting link information of the additional information to the mobile terminal. [0038]The terminal may further include: receiving a request for transmission of contents corresponding to the selected object from the mobile terminal; and transmitting the contents corresponding to the selected object to the mobile terminal. [0039]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a communication unit which is configured to transmit a signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; an additional information obtaining unit which is configured to transmit a signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; a display which is configured to display the additional information received from the external display device; and a controller which is configured to control the communication unit, the additional information obtaining unit, and the display unit. [0040]The controller may convert the signal for selecting the object according to a control protocol of the external display device. [0041]The communication unit may transmit a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0042]The communication unit may transmit a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input. [0043]The display may display thumbnail information of contents corresponding to the object on a screen of the mobile terminal. [0044]The additional information obtaining unit may receive the additional information from the external display device. [0045]The communication unit may receive link information of the additional information from the external display device based on the second input, and wherein the additional information obtaining unit receives the additional information from a server based on the received link information. [0046]The controller may control the additional information displayed on the mobile terminal based on a third input of the user through the mobile terminal. [0047]The mobile terminal may further include: a contents obtaining unit which is configured to obtain content corresponding to the additional information displayed on the mobile terminal. [0048]According to an aspect of an exemplary embodiment, there is provided a display device including: a selection unit which is configured to select an object displayed on the display device based on a first input of a user through a mobile terminal; a communication unit which is configured to transmit additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal, and a controller which is configured to control the selection unit and the communication unit. [0049]The controller may extract the additional information from contents corresponding to the selected object. [0050]The selection unit may receive a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal and move the selection region according to the received control signal. [0051]The controller may convert the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0052]The display device may further include: a sensor which is configured to sense at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0053]The controller may control at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0054]The communication unit may transmit link information of the additional information to the mobile terminal. [0055]The communication unit may receive a request for transmission of contents corresponding to the selected object from the mobile terminal and transmit the contents corresponding to the selected object to the mobile terminal. [0056]According to an aspect of another exemplary embodiment, there is provided a method in which a mobile terminal generates a control signal, the method including: receiving a user input; determining an operation mode of the mobile terminal; and in response to determining the operation mode is a first mode, generating a first control signal for controlling an external display device based on the user input, and, in response to determining the operation mode is a second mode, generating a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0057]The contents may include contents corresponding to an object selected from the external display device or additional information corresponding to the object based on the first control signal. [0058]The user input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0059]The determining may include: determining the operation mode of the mobile terminal as the first mode in a case where the mobile terminal is in a vertical mode, and, determining the operation mode of the mobile terminal as the second mode in a case where the mobile terminal is in a horizontal mode. [0060]The determining may include: determining the operation mode of the mobile terminal based on information displayed on a screen of the mobile terminal. [0061]The determining may include: in response to determining the information displayed on the screen of the mobile terminal is thumbnail information of contents corresponding to the object displayed on the external display device or movement direction information of the mobile terminal, determining the operation mode of the mobile terminal as the first mode, and, in response to determining the information displayed on the screen of the mobile terminal is the contents corresponding to the object displayed on the external display device or additional information corresponding to the object, determining the operation mode of the mobile terminal as the second mode. [0062]The generating of the first control signal may include: converting the first control signal according to a control protocol of the external display device. [0063]The first mode may be a mode in which the object of the external display device is selected, and the second mode is a mode in which additional information corresponding to the selected object is displayed on the mobile terminal. [0064]The first control signal may include a signal for controlling a movement of a selection region for selecting the object of the external display device, and the second control signal may include a signal for controlling at least one of playing of the contents, editing of the contents, and transmission of the contents. [0065]The method may further include: receiving a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle; converting the operation mode from the first mode to the second mode based on the first rotational motion input; receiving a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle; and converting the operation mode from the second mode to the first mode based on the second rotational motion input. [0066]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a user input which is configured to receive a user input; an operation mode determining unit which is configured to determine an operation mode of the mobile terminal; and a controller which is configured, in response to the operation mode determining unit determining that the operation mode is a first mode, generate a first control signal for controlling an external display device based on the user input, and, in response to the operation mode determining unit determining that the operation mode is a second mode, generate a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0067]The user input may receive a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle and a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle, and wherein the controller converts the operation mode from the first mode to the second mode based on the first rotational motion input and the operation mode from the second mode to the first mode based on the second rotational motion input. [0068]According to an aspect of another exemplary embodiment, a method of displaying information of an external display device on a mobile terminal displays is provided. The method includes: receiving a user input into the mobile terminal about an object displayed on the external display device; transmitting a first signal to the external display device to select the object displayed on an external display device; receiving a second user input into the mobile terminal about additional information corresponding to the object displayed on the external display device; transmitting a second signal to the external display device to request additional information corresponding to the selected object; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0069]The transmitting the first signal may include converting the first signal to a control protocol of the external display device. [0070]The transmitting the first signal may include requesting control authorization from the external display device and receiving a control authorization acceptance message from the external display device. BRIEF DESCRIPTION OF THE DRAWINGS [0071]The above and other features and advantages will become more apparent by describing in detail exemplary embodiments with reference to the attached drawings in which: [0072]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment; [0073]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment; [0074]FIGS. 3A through 3C are views of screens on which a mobile terminal selects an object of an external display device, according to an exemplary embodiment; [0075]FIGS. 4A and 4B are views of screens on which a mobile terminal obtains additional information, according to an exemplary embodiment; [0076]FIG. 5 is a view of a screen on which contents are obtained, according to an exemplary embodiment; [0077]FIG. 6 is a view of a screen on which an object is displayed or reproduced, according to an exemplary embodiment; [0078]FIG. 7 is a flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0079]FIG. 8 is a detailed flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0080]FIG. 9 is a flowchart illustrating a method in which a display device senses an input of a mobile terminal and provides additional information, according to an exemplary embodiment; [0081]FIG. 10 is a flowchart illustrating a method in which a mobile terminal obtains additional information through a server, according to an exemplary embodiment; [0082]FIG. 11 is a flowchart illustrating a method in which a mobile terminal obtains contents, according to an exemplary embodiment; [0083]FIG. 12 is a flowchart illustrating a method in which a mobile terminal obtains contents through a server, according to an exemplary embodiment; [0084]FIG. 13 is a view of a screen on which each of a plurality of mobile terminals selects an object of a display device, according to an exemplary embodiment; [0085]FIG. 14 is a block diagram of a mobile terminal, according to an exemplary embodiment; [0086]FIG. 15 is a block diagram of a display device, according to an exemplary embodiment; [0087]FIG. 16 is a flowchart illustrating a method in which a display device provides information, according to an exemplary embodiment; and [0088]FIG. 17 is a flowchart illustrating a method in which a mobile terminal generates a control signal, according to an exemplary embodiment. DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS [0089]First, the terms used herein will be briefly described, and then the exemplary embodiments will be described in detail. [0090]Although the terms used herein are general terms that are widely used at present in consideration of the functions of the exemplary embodiments, they may vary according to the intention of one of ordinary skill in the art, a precedent, the appearance of new technology, or the like. In addition, in a particular case, the applicant may select the terms arbitrarily. In this case, the meanings of the terms will be described in detail in the detailed description of the exemplary embodiments. Thus, the terms used in the detailed description should not be only names of the terms but should be defined based on their meanings and contents in relation to the exemplary embodiments. [0091]When a unit “comprises” an element in the entire specification, the unit does not exclude another element but may further comprise another element unless the context clearly indicates otherwise. In addition, terms such as “ . . . unit”, “module”, and the like used herein indicate a unit for performing at least one function or operation and may be implemented by hardware or software or a combination thereof. [0092]Throughout the specification, an “object” refers to a target that may be selected by a user from a display device. Examples of the object include, but are not limited to, an icon, a link, a picture, a text, an index item, etc. [0093]In addition, “additional information” refers to information regarding contents corresponding to an object, and may have various forms according to types of contents. Examples of the additional information may include, but are not limited to, preview information, prelistening information, application information, user review information, advertisement image information, update information, newspaper article information, goods information, movie information, game information, album information, etc. [0094]In the present specification, “contents” may be displayed, reproduced, or stored in a mobile terminal, and may include, for example, still image contents (for example, a photo, a picture, etc.), text contents (for example, an electronic book (a poem and a novel), a letter, a business file, a web page, an electronic program guide (EPG), etc.), moving image contents (for example, a personal image, a movie, music video, a YouTube video, a TV program image, etc.), music contents (for example, music, a music performance, a radio broadcast, etc.), an application (a widget, a game, etc.) [0095]The exemplary embodiments will now be described more fully with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the inventive concept to those of ordinary skill in the art. For clarity, in the drawings, irrelevant portions with respect to the description are omitted, and similar reference numbers are added to similar portions throughout the entire specification. [0096]As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list. [0097]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment. [0098]Referring to FIG. 1, the information providing system according to an exemplary embodiment may include a mobile terminal 100 and an external display device 200. [0099]The mobile terminal 100 is a device that obtains contents from the outside and displays, reproduces, or stores the obtained contents. The mobile terminal 100 may be implemented in various ways. For example, the mobile terminal 100 described in the present specification may include a cellular phone, a smart phone, a laptop computer, a tablet personal computer (PC), an e-book terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, etc. [0100]The display device 200 is a device that may be of various types including a display panel. For example, the display device 200 described in the present specification may include a smart television (TV), an Internet protocol TV (IPTV), a digital TV (DTV), a computer, a laptop computer, an e-book terminal, a tablet PC, a digital broadcasting terminal, a consumer electronics (CE) device (for example, a refrigerator or an air conditioner having the display panel), etc. [0101]The display device 200 according to an exemplary embodiment may display an object list. The object list may include identification information regarding at least one piece of contents. Examples of the identification information may include a title of contents, an image and icon indicating contents, etc. [0102]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment. [0103]Referring to FIG. 2, the information providing system according to another exemplary embodiment may include the mobile terminal 100, the display apparatus 200, and a server 300. [0104]The mobile terminal 100 and the display apparatus 200 are the same as described with reference to FIG. 1, and thus descriptions thereof are omitted. [0105]The server 300 may communicate with the mobile terminal 100 or the display apparatus 200. According to an exemplary embodiment, the server 300 may receive a contents providing request from the mobile terminal 100 or the display device 200. In this case, the server 300 may provide contents to the mobile terminal 100 or the display device 200. The contents provided by the server 300 may be contents corresponding to an object selected by the display device 200 or additional information corresponding to the object. [0106]For example, in a case where the display device 200 selects an object relating to movie contents, the server 300 may provide the movie contents or preview video of the movie contents to the mobile terminal 100 or the display device 200. [0107]An example in which the mobile terminal 100 selects an object displayed on an external display device based on a user input and obtains and displays additional information corresponding to the selected object will now be described in brief with reference to FIGS. 3 through 6. [0108]FIGS. 3A through 3C are views of screens on which the mobile terminal 100 selects an object of the external display device 200, according to an exemplary embodiment. [0109]Referring to FIG. 3A, the display device 200 may display a plurality of objects indicating a plurality of pieces of contents. In this case, a user may use the mobile terminal 100 to select at least one of the plurality of objects displayed on the display device 200. [0110]For example, the user may move the mobile terminal 100 up and down and left and right (a first input) to select at least one of the plurality of objects displayed on the display device 200. In this regard, the display device 200 may display a location of a selection region (for example, a cursor and a pointer) corresponding to a movement of the mobile terminal 100 on a screen. [0111]Although a motion input is exemplarily used as the first input for selecting an object in FIG. 3A, the first input is not limited to the motion input. The first input may be a bending input, a key input, a voice input, and a touch input in addition to the motion input. [0112]According to an exemplary embodiment, the mobile terminal 100 may turn its screen off or may blacken its screen when selecting an object displayed on a screen of the display device 200 in such a way that users eyes are not distracted. [0113]According to another exemplary embodiment, the mobile terminal 100 may display thumbnail information such as an icon, an image, a title, etc. of contents relating to an object in which the selection region is disposed or a movement direction of the mobile terminal 100 as an arrow, etc. on the display device 200. [0114]Referring to FIG. 3B, the mobile terminal 100 may display a selection window (or a graphical user interface (GUI)) for selecting a category (for example, drama, movie, sports, etc.) of contents. In this regard, the mobile terminal 100 may receive a selection of at least one category from the user. The mobile terminal 100 may transmit information regarding the selected category to the display device 200. In this case, the display device 200 may filter and display an object regarding contents corresponding to the category selected by the user. [0115]Referring to FIG. 3C, the mobile terminal 100 may output a map or a GUI indicating objects displayed on the display device 200 from among all the objects. [0116]FIGS. 4A and 4B are views of screens on which the mobile terminal 100 obtains additional information, according to an exemplary embodiment. [0117]Referring to FIG. 4A, a user may move the mobile terminal 100, select an object of the display device 200, then rotate the mobile terminal 100, and request additional information corresponding to the selected object from the display device 200. [0118]In this case, the display device 200 may transmit the additional information corresponding to the selected object or link information (for example, a uniform resource identifier (URI)) of the additional information to the mobile terminal 100. In this regard, the mobile terminal 100 may display the obtained additional information on a screen. [0119]For example, as shown in FIG. 4A, in a case where the user moves the mobile terminal 100, selects an object illustrating Shrek, and converts a vertical mode of the mobile terminal 100 into a horizontal mode, the mobile terminal 100 may obtain and display additional information (for example, Movie Title: Shrek, Review: ★★★★⋆, Representative Image, and Advertisement Moving Image) relating to Shrek. [0120]According to an exemplary embodiment, referring to FIG. 4B, if the user wishes to select a new object, the user may select the object of the display device 200 again by converting the horizontal mode of the mobile terminal 100 into the vertical mode. [0121]Although a motion input is that an object is selected and then is that the mobile terminal 100 receives and displays additional information corresponding to the object in FIGS. 3A through 4B as a rotation input, an exemplary embodiment is not limited thereto. That is, according to an exemplary embodiment, the mobile terminal 100 may receive and display additional information regarding contents relating to an object in which a selection region is disposed from the display device 200 while selecting an object of the display device 200 as the motion input. According to an exemplary embodiment, a communication network over which the mobile terminal 100 transmits a signal for sele(String), 相关专利申请的交叉引用 [0001] 本申请要求于2012年7月25日向韩国知识产权局提交的韩国专利申请第10-2012-0081434号的优先权,其公开内容通过引用的方式整体并入本文。 背景 [0002] 1. 领域 [0003] 示例性实施例涉及用于通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与所选对象相对应的附加信息来显示信息的方法和移动终端、用于提供信息的方法和显示设备 通过基于移动终端的输入选择对象并向移动终端提供关于所选对象的附加信息,以及用于通过基于操作将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端 移动终端的模式。 [0004] 2.相关技术的描述 [0005] 智能电视(TV)是一种将电视与上网功能相结合,能够利用各种功能的多功能电视,如网上冲浪、视频点播(VOD)观看、社交网络服务(SNS)、游戏等。 并安装各种应用程序。 [0006] 智能电视的一个特点是用户和电视可以相互发送和接收信息。 这是智能电视与现有的仅单方面传输信息的电视的区别。 因此,智能电视也被称为互动电视。 [0007] 但是,用户使用标准遥控器来使用智能电视的各种功能是非常不方便的。 特别地,当用户浏览或下载内容时,需要通过几个步骤来操作遥控器。 [0008] 因此,需要一种让用户容易控制智能电视的控制装置或系统。 概括 [0009] 示例性实施例提供一种用于显示信息的方法和移动终端,该方法和移动终端通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与选择的对象相对应的附加信息来进行。 [0010] 示例性实施例还提供了一种用于通过基于移动终端的输入来选择对象并将关于所选择的对象的附加信息提供给移动终端来提供信息的方法和显示设备。 [0011] 示例性实施例还提供一种用于通过基于移动终端的操作模式将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端。 [0012] 根据示例性实施例的一方面,提供了一种移动终端显示信息的方法,该方法包括:基于第一输入将用于选择在外部显示设备上显示的对象的第一信号发送到外部显示设备 用户通过移动终端; 基于用户通过移动终端的第二输入向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0013] 发送第一选择对象信号可以包括: 根据外部显示设备的控制协议对选择对象信号进行转换。 [0014] 用于选择对象的第一信号的发送可以包括:发送用于控制选择区域的移动的信号,用于选择显示在外部显示设备上的对象。 [0015] 发送用于控制选择区域的移动的信号可以包括:发送用于控制选择区域的移动方向、选择区域的移动速度和屏幕上显示的对象的数量中的至少一项的信号。 基于第一输入的外部显示设备。 [0016]发送用于选择对象的第一信号可以包括:在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0017] 缩略图信息可以包括与对象对应的内容的图像、内容的标题和内容的类型中的至少一个。 [0018] 发送用于选择对象的第一信号可以包括:根据第一输入在屏幕上显示移动终端的移动方向。 [0019] 第一输入和第二输入可以包括运动输入、键输入、触摸输入、弯曲输入和语音输入中的至少一个。 [0020] 第一输入可以包括用于在3D方向上移动移动终端的三维(3D)运动输入,其中第二输入包括用于将移动终端旋转超过预定角度的旋转运动输入。 [0021] 发送用于请求附加信息的第二信号可以包括:从显示设备接收附加信息。 [0022] 用于请求附加信息的第二信号的发送可以包括:基于第二输入从外部显示设备接收附加信息的链接信息; 以及基于接收到的链接信息从服务器接收附加信息。 [0023] 将用于选择对象的第一信号发送给显示设备可以包括: 向外部显示设备请求控制授权; 接收来自外部显示设备的控制授权接受消息。 [0024] 内容可以包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。 [0025] 附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、广告图像信息和专辑信息中的至少一种。 [0026] 该方法还可以包括:基于用户通过移动终端的第三输入来控制在移动终端的屏幕上显示的附加信息。 [0027] 对附加信息的控制可以包括:基于用户通过移动终端的第三输入,控制附加信息的显示、附加信息的播放以及改变为上一个附加信息或下一个附加信息中的至少一个。 [0028] 该方法还可以包括:获取与显示在移动终端的屏幕上的附加信息对应的内容。 [0029] 根据另一示例性实施例的一方面,提供了一种显示装置向移动终端提供信息的方法,该方法包括:通过通过移动终端接收用户的第一输入来选择显示在显示装置上的对象。 ; 通过移动终端接收用户的第二输入,将与选择的对象对应的附加信息发送到移动终端。 [0030] 发送可以包括:从对应于所选对象的内容中提取附加信息。 [0031] 对象的选择可以包括:从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号; 根据控制信号移动选择区域。 [0032] 对象的选择可以包括:将接收到的第一输入转换为用于根据显示设备的控制协议控制选择区域的移动的控制信号。 [0033] 接收可以包括:从多个移动终端中的每一个接收用于控制选择区域的移动的控制信号。 [0034]该方法还可以包括:感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0035] 对象的选择可以包括:基于用户通过移动终端的第一输入,控制选择区域的移动方向、选择区域的移动速度以及屏幕上显示的对象的数量中的至少一个。 . [0036] 对象的选择可以包括:将对象对应的内容的缩略图信息发送给移动终端。 [0037] 向移动终端发送附加信息可以包括:向移动终端发送附加信息的链接信息。 [0038] 终端还可以包括: 从移动终端接收与选择的对象对应的内容的传输请求; 将选择的对象对应的内容发送给移动终端。 [0039] 根据另一示例性实施例的一方面,提供了一种移动终端,包括: 通信单元,被配置为基于用户的第一输入向外部显示设备发送用于选择在外部显示设备上显示的对象的信号。 通过移动终端; 附加信息获取单元,被配置为基于用户通过移动终端的第二输入向外部显示设备发送请求与所选对象对应的附加信息的信号; 显示器,用于显示从外部显示设备接收到的附加信息; 控制器,用于控制通信单元、附加信息获取单元和显示单元。 [0040] 控制器可以根据外部显示设备的控制协议转换用于选择对象的信号。 [0041] 通信单元可以发送用于控制选择区域的移动的信号,该选择区域用于选择显示在外部显示装置上的对象。 [0042] 通信单元可以基于第一输入发送用于控制选择区域的移动方向、选择区域的移动速度和显示在外部显示装置的屏幕上的对象的数量中的至少一个的信号。 [0043] 显示器可以在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0044] 附加信息获取单元可以从外部显示设备接收附加信息。 [0045] 通信单元可以基于第二输入从外部显示装置接收附加信息的链接信息,并且其中附加信息获取单元基于接收到的链接信息从服务器接收附加信息。 [0046] 控制器可以基于用户通过移动终端的第三输入来控制在移动终端上显示的附加信息。 [0047] 所述移动终端还可以包括: 内容获取单元,用于获取所述移动终端显示的附加信息对应的内容。 [0048] 根据示例性实施例的一方面,提供了一种显示装置,包括: 选择单元,被配置为基于用户通过移动终端的第一输入选择显示在显示装置上的对象; 通信单元,被配置为通过接收用户通过移动终端的第二输入,将与选择的对象对应的附加信息发送到移动终端,以及控制器,被配置为控制选择单元和通信单元。 [0049] 控制器可以从对应于所选对象的内容中提取附加信息。 [0050] 选择单元可以从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号,并且根据接收到的控制信号移动选择区域。 [0051] 控制器可以根据显示设备的控制协议将接收到的第一输入转换为用于控制选择区域的移动的控制信号。 [0052] 显示装置还可以包括:传感器,用于感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0053] 控制器可以基于用户通过移动终端的第一输入来控制选择区域的移动方向、选择区域的移动速度和显示在屏幕上的对象的数量中的至少一个。 [0054] 通信单元可以将附加信息的链接信息发送到移动终端。 [0055] 通信单元可以从移动终端接收对与所选对象相对应的内容的传输请求,并将与所选对象相对应的内容发送到移动终端。 [0056] 根据另一示例性实施例的一方面,提供了一种移动终端生成控制信号的方法,该方法包括:接收用户输入; 确定移动终端的操作模式; 并且响应于确定操作模式是第一模式,基于用户输入生成用于控制外部显示设备的第一控制信号,并且响应于确定操作模式是第二模式,生成用于控制外部显示设备的第二控制信号 基于用户输入控制在移动终端上显示的内容。 [0057] 内容可以包括与从外部显示设备选择的对象相对应的内容或与基于第一控制信号的对象相对应的附加信息。 [0058] 用户输入可以包括动作输入、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0059] 所述确定可以包括:在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第一模式,以及,在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第二模式。 终端处于水平模式。 [0060] 所述确定可以包括:根据所述移动终端的屏幕上显示的信息确定所述移动终端的操作模式。 [0061] 所述确定可以包括:响应于确定所述移动终端屏幕上显示的信息为所述外接显示设备上显示的对象对应的内容的缩略图信息或所述移动终端的移动方向信息,确定所述移动终端的操作模式。 终端作为第一模式,并且,响应于确定移动终端的屏幕上显示的信息是与外部显示设备上显示的对象对应的内容或与该对象对应的附加信息,确定移动终端的操作模式 终端作为第二种模式。 [0062] 第一控制信号的产生可以包括:根据外部显示设备的控制协议转换第一控制信号。 [0063] 第一模式可以是选择外部显示设备的对象的模式,第二模式是在移动终端上显示与选择的对象对应的附加信息的模式。 [0064] 第一控制信号可以包括用于控制用于选择外部显示设备的对象的选择区域的移动的信号,并且第二控制信号可以包括用于控制内容的播放、内容的编辑中的至少一个的信号。 ,以及内容的传输。 [0065]该方法还可以包括:接收用于将移动终端在第一方向上旋转预定角度的第一旋转运动输入; 基于第一旋转运动输入将操作模式从第一模式转换为第二模式; 接收用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入; 基于第二旋转运动输入,将操作模式从第二模式转换为第一模式。 [0066] 根据另一示例性实施例的一方面,提供了一种移动终端,包括: 用户输入,被配置为接收用户输入; 操作模式确定单元,用于确定移动终端的操作模式; 控制器,被配置为响应于操作模式确定单元确定操作模式是第一模式,基于用户输入产生用于控制外部显示装置的第一控制信号,并且响应于操作模式 确定单元确定操作模式是第二模式,基于用户输入产生用于控制在移动终端上显示的内容的第二控制信号。 [0067] 用户输入可以接收用于将移动终端沿第一方向旋转预定角度的第一旋转运动输入和用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入,并且其中控制器转换操作 基于第一旋转运动输入从第一模式到第二模式的模式和基于第二旋转运动输入从第二模式到第一模式的操作模式。 [0068] 根据另一示例性实施例的一方面,提供了一种在移动终端显示器上显示外部显示设备的信息的方法。 该方法包括:接收到移动终端的关于显示在外部显示设备上的对象的用户输入; 传送第一信号至外接显示装置以选择外接显示装置上显示的对象; 接收到移动终端的关于与显示在外部显示设备上的对象对应的附加信息的第二用户输入; 向外部显示设备发送第二信号以请求对应于所选对象的附加信息; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0069] 发送第一信号可以包括将第一信号转换为外部显示设备的控制协议。 [0070] 发送第一信号可以包括从外部显示设备请求控制授权和从外部显示设备接收控制授权接受消息。 附图的简要说明 [0071] 通过参考附图详细描述示例性实施例,上述和其他特征和优点将变得更加明显,其中: [0072] 图1是用于说明根据示例性实施例的信息提供系统的视图; [0073] 图2是用于说明另一实施方式的信息提供系统的图。 [0074] 图3A至图3C是根据示例性实施例的移动终端选择外部显示设备的对象的屏幕的视图; [0075] 图4A和4B是根据示例性实施例的移动终端在其上获得附加信息的屏幕的视图; [0076] 图5是根据示例性实施例的获取内容的屏幕的视图; [0077] 图6是根据示例性实施例的显示或再现对象的屏幕的视图; [0078] 图7是示出根据示例性实施例的移动终端显示信息的方法的流程图; [0079] 图8是示出根据示例性实施例的移动终端显示信息的方法的详细流程图; [0080]图9是示出根据示例性实施例的显示设备感测移动终端的输入并提供附加信息的方法的流程图; [0081] 图10是示出根据示例性实施例的移动终端通过服务器获取附加信息的方法的流程图; [0082] 图11是示出根据示例性实施例的移动终端获取内容的方法的流程图; [0083] 图12是示出根据示例性实施例的移动终端通过服务器获取内容的方法的流程图; [0084] 图13是根据示例性实施例的多个移动终端中的每一个选择显示装置的对象的屏幕的视图; [0085] 图14是根据示例性实施例的移动终端的框图; [0086] 图15是根据示例性实施例的显示装置的框图; [0087] 图16是示出根据示例性实施例的显示设备提供信息的方法的流程图; 和 [0088] 图17是示出根据示例性实施例的移动终端生成控制信号的方法的流程图。 示例性实施例的详细说明 [0089] 首先,将简要描述这里使用的术语,然后将详细描述示例性实施例。 [0090] 尽管这里使用的术语是考虑到示例性实施例的功能而目前广泛使用的通用术语,但是它们可以根据本领域普通技术人员的意图、先例、新技术的出现或 类似。 此外,在特定情况下,申请人可以任意选择条款。 在这种情况下,术语的含义将在示例性实施例的详细描述中详细描述。 因此,在详细描述中使用的术语不应仅仅是术语的名称,而应基于与示例性实施例相关的含义和内容来定义。 [0091] 当一个单元“包括”整个说明书中的一个元素时,该单元不排除另一个元素,而是可以进一步包括另一个元素,除非上下文另有明确说明。 此外,诸如“. . . 这里使用的“单元”、“模块”等表示用于执行至少一个功能或操作的单元,可以通过硬件或软件或其组合来实现。 [0092] 在整个说明书中,“对象”指的是可以由用户从显示设备中选择的目标。 对象的示例包括但不限于图标、链接、图片、文本、索引项等。 [0093] 另外,“附加信息”是指与对象对应的内容有关的信息,可以根据内容的种类而具有各种形式。 附加信息的示例可以包括但不限于预览信息、试听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息、 等等 [0094] 在本说明书中,“内容”可以在移动终端中显示、再现或存储,并且可以包括例如静止图像内容(例如照片、图片等)、文本内容(例如 、电子书(一首诗和一部小说)、一封信、一个商业文件、一个网页、一个电子节目指南(EPG)等)、运动图像内容(例如,个人图像、电影、音乐 视频、YouTube 视频、电视节目图像等)、音乐内容(例如,音乐、音乐表演、无线电广播等)、应用程序(小部件、游戏等) [0095]现在将参照附图更全面地描述示例性实施例。 然而,示例性实施例可以以许多不同的形式体现,并且不应被解释为限于本文所阐述的实施例; 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明构思充分传达给本领域普通技术人员。 为了清楚起见,在附图中,省略了与描述无关的部分,并且在整个说明书中类似的附图标记被添加到类似的部分。 [0096] 如本文所用,术语“和/或”包括一个或多个相关列出的项目的任何和所有组合。 诸如“至少一个”之类的表达式在元素列表之前时,会修改整个元素列表,而不是修改列表中的单个元素。 [0097] 图1是用于解释根据示例性实施例的信息提供系统的视图。 [0098] 参考图1,根据示例性实施例的信息提供系统可以包括移动终端 100 和一个外部显示设备 200 . [0099] 移动终端 100 是从外部获取内容并显示、再现或存储获取的内容的设备。 移动终端 100 可以以各种方式实现。 例如,移动终端 100 本说明书中描述的可以包括蜂窝电话、智能电话、膝上型计算机、平板个人计算机(PC)、电子书终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、 导航系统等 [0100] 显示装置 200 是一种可以是各种类型的设备,包括显示面板。 例如,显示设备 200 本说明书中描述的可以包括智能电视(TV)、互联网协议电视(IPTV)、数字电视(DTV)、计算机、膝上型计算机、电子书终端、平板电脑、数字广播终端 ,消费电子(CE)设备(例如,具有显示面板的冰箱或空调)等。 [0101] 显示装置 200 根据示例性实施例,可以显示对象列表。 对象列表可以包括关于至少一个内容的标识信息。 标识信息的示例可以包括内容的标题、指示内容的图像和图标等。 [0102] 图2是用于说明根据另一示例性实施例的信息提供系统的视图。 [0103] 参考图2,根据另一示例性实施例的信息提供系统可以包括移动终端 100 , 显示装置 200 , 和一个服务器 300 . [0104] 移动终端 100 和显示装置 200 与参考图1描述的相同,因此省略其描述。 [0105] 服务器 300 可与移动终端通信 100 或显示设备 200 . 根据示例性实施例,服务器 300 可以从移动终端接收内容提供请求 100 或显示设备 200 . 在这种情况下,服务器 300 可以向移动终端提供内容 100 或显示设备 200 . 服务器提供的内容 300 可以是显示设备选择的对象对应的内容 200 或与对象对应的附加信息。 [0106] 例如,在显示设备 200 选择与电影内容相关的对象,服务器 300 可向移动终端提供电影内容或电影内容的预览视频 100 或显示设备 200 . [0107] 以移动终端为例 100 现在将参照图3至图6简要描述基于用户输入选择在外部显示设备上显示的对象并获得并显示与所选择的对象相对应的附加信息。 [0108] 图3A到3C是移动终端在其上的屏幕的视图 100 选择外部显示设备的对象 200 ,根据示例性实施例。 [0109] 参照图3A,显示装置 200 可以显示指示多条内容的多个对象。 在这种情况下,用户可以使用移动终端 100 选择显示在显示设备上的多个对象中的至少一个 200 . [0110] 例如,用户可以移动移动终端 100 上下左右(第一输入)以选择显示设备上显示的多个对象中的至少一个 200 . 对此,显示设备 200 可以显示与移动终端的移动相对应的选择区域(例如,光标和指针)的位置 100 在屏幕上。 [0111] 尽管在图3A中示例性地使用动作输入作为用于选择对象的第一输入,但是第一输入不限于动作输入。 除了动作输入之外,第一输入可以是弯曲输入、键输入、语音输入和触摸输入。 [0112] 根据示例性实施例,移动终端 100 选择显示设备屏幕上显示的对象时,可能会关闭屏幕或将屏幕变黑 200 这样用户的眼睛就不会分心。 [0113] 根据另一示例性实施例,移动终端 100 可以显示与设置选择区域的对象或移动终端的移动方向有关的内容的缩略图信息,例如图标、图像、标题等 100 显示设备上的箭头等 200 . [0114] 参考图3B,移动终端 100 可以显示用于选择内容类别(例如,戏剧、电影、体育等)的选择窗口(或图形用户界面(GUI))。 对此,移动端 100 可以接收来自用户的至少一个类别的选择。 移动终端 100 可以将关于所选类别的信息发送到显示设备 200 . 在这种情况下,显示设备 200 可以过滤和显示关于与用户选择的类别相对应的内容的对象。 [0115] 参考图3C,移动终端 100 可以输出地图或图形用户界面指示显示设备上显示的对象 200 从所有对象中。 [0116] 图4A和4B是移动终端在其上的屏幕的视图 100 根据示例性实施例,获取附加信息。 [0117] 参考图4A,用户可以移动移动终端 100 , 选择显示设备的对象 200 ,然后旋转移动端 100 , 并向显示设备请求与所选对象对应的附加信息 200 . [0118] 在这种情况下,显示设备 200 可以将与选择的对象相对应的附加信息或附加信息的链接信息(例如,统一资源标识符(URI))发送到移动终端 100 . 对此,移动端 100 可以在屏幕上显示获得的附加信息。 [0119] 例如,如图4A所示,在用户移动移动终端的情况下 100 ,选择描绘史莱克的对象,并转换移动终端的垂直模式 100 进入横屏模式,移动端 100 可能会获取和显示与史莱克有关的附加信息(例如,电影名称:史莱克、评论:★★★★⋆、代表图像和广告动态图像)。 [0120] 根据示例性实施例,参照图4B,如果用户希望选择新对象,则用户可以选择显示设备的对象 200 再次通过转换移动端的水平模式 100 进入垂直模式。 [0121] 虽然动作输入是选择了一个对象然后是移动终端 100虽然接收和显示与图3A至图4B中的对象相对应的附加信息作为旋转输入,但示例性实施例不限于此。 也就是说,根据示例性实施例,移动终端 100 可以从显示装置接收和显示关于与其中设置了选择区域的对象有关的内容的附加信息 200 在选择显示设备的对象时 200 作为运动输入。 根据示例性实施例,移动终端在其上的通信网络 100 将用于选择对象的信号发送到显示设备 200 以及移动终端所通过的通信网络 100 从显示设备接收附加信息 200 可能彼此不同。 例如,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 通过蓝牙通信,然后从显示设备接收与所选对象对应的附加信息 200 通过 Wi-Fi 通信。 [0122] 图5是根据示例性实施例的在其上获得内容的屏幕的视图。 [0123] 用户可以确认关于与从显示设备获得的对象相对应的内容的附加信息 200 然后向显示设备请求相应的内容 200 或服务器 300 . 例如,用户可以通过显示设备确认关于电影史瑞克的附加信息(用户评论等) 200 然后从显示设备请求和下载电影内容史莱克 200 或服务器 300 . [0124] 图6是根据示例性实施例的显示或再现对象的屏幕的视图。 [0125] 参考图6,根据示例性实施例,移动终端 100 可以显示或再现从显示设备下载的内容 200 或服务器 300 . [0126] 根据另一示例性实施例,移动终端 100 可以通过流式传输内容来接收和再现内容。 [0127] 一种移动终端的方法 100 现在将在下面详细描述基于用户输入检索和/或显示信息。 [0128] 根据示例性实施例的显示信息的方法可以通过预定应用来实现。 也就是移动终端 100 可以驱动用于提供根据示例性实施例的显示信息的方法的应用。 移动终端 100 可以基于用户输入或自动驱动应用程序。 [0129] 移动端驱动的应用 100 可以是仅用于执行控制显示设备的过程的应用程序 200 或提供各种服务。 例如,该应用程序可以是用于提供远程控制服务、信使服务、社交网络服务(SNS)、多媒体内容播放服务等的应用程序。 [0130] 假设移动终端使用的方法 100 可以通过预定应用程序来执行参考图7至图12描述的显示信息。 [0131] 图7是示出移动终端的方法的流程图 100 根据示例性实施例,显示信息。 参照图7,移动终端的方法 100 根据示例性实施例的显示信息包括由移动终端顺序执行的操作 100 稍后将描述的图14的。 因此,虽然以下省略,但以上关于移动终端的描述 100 图14的方法也将适用于图7的方法,其中移动终端 100 显示信息。 [0132] 在操作 S 710 , 移动端 100 可以发送用于选择外部显示设备的对象的信号 200 到显示设备 200 基于第一输入。 在接收到第一输入的情况下,移动终端 100可以产生用于选择显示设备的对象的信号 200 基于第一个输入。 [0133] 根据示例性实施例,移动终端 100 可以根据显示设备的控制协议转换用于选择对象的信号 200 . 也就是移动终端 100 可以获得显示设备的标识信息(例如设备类型、设备ID、设备序列号等) 200 并将接收到的用户的第一输入转换为显示设备可识别的控制命令 200 基于显示设备的识别信息 200 . [0134] 根据示例性实施例的用于选择对象的信号可以包括用于控制选择对象的选择区域的移动的信号。 也就是说,在移动终端 100 移动终端检测到超过阈值的移动 100 可以产生用于控制显示装置的选择区域的移动的信号 200 基于有关检测到的运动的信息。 [0135] 例如,在陀螺仪传感器值小于阈值的情况下,移动终端 100 可以确定移动终端 100 不移动,可以不产生用于控制选择区域移动的信号,并且,每次陀螺传感器值改变预定值(例如,10度)时,可以产生用于将选择区域移动一个空间的控制信号 /sec) 大于阈值。 [0136] 根据另一示例性实施例的用于选择对象的信号可以包括信息(例如,移动终端的移动位置信息) 100 ) 关于第一个输入。 也就是移动终端 100 可以直接产生控制选择区域移动的信号并将其传输到显示装置 200 或者可以发送信息(例如,移动终端的移动位置信息) 100 ) 关于显示设备的第一个输入 200 . [0137] 在信息(例如,移动终端的移动位置信息 100 ) 关于第一个输入被传输到显示设备 200 , 显示设备 200 可以根据显示设备的控制协议将第一输入转换为用于控制选择区域的移动的信号 200 . [0138] 例如,在接收到小于阈值的陀螺传感器值的情况下,移动终端 100 可以确定移动终端 100 不移动并且可能不产生用于控制选择区域移动的信号。 移动终端 100 每当接收到大于阈值的预定陀螺传感器值(例如,10度/秒)时,可以生成用于将选择区域移动一个空间的控制信号。 [0139] 在生成控制信号之前,移动终端 100 可以通过身份验证来授权显示设备 200 通过显示设备 200 . 例如,移动终端 100 可以向显示设备请求控制授权 200 . 对此,移动端 100 可以通过发送移动终端的识别信息来请求控制授权 100 到显示设备 200 . 移动终端的识别信息 100 是识别移动终端的唯一信息 100 ,并且可能包括例如设备 ID、唯一序列号、媒体访问控制 (MAC) 地址、国际移动设备身份 (IMEI) 等。 [0140] 显示装置 200 可认证移动终端的控制权限 100 基于移动终端的识别信息 100 . 在认证成功的情况下,显示设备 200 可以向移动终端发送控制授权接受消息 100. 在这种情况下,移动终端 100 可以控制显示设备 200 . [0141] 在发送控制授权接受消息时,显示设备 200 可以注册移动终端的识别信息 100 在一个存储单元中。 因此,虽然移动终端 100 未经显示设备认证 200 不再是移动端 100 可以控制显示设备 200 . [0142] 在操作 S 720 , 移动端 100 可以获得与从显示设备中选择的对象相对应的附加信息 200 基于第二个输入。 即,在接收到第二输入的情况下,移动终端 100 可以从显示设备请求与基于第一输入选择的对象相对应的附加信息 200 . 在这种情况下,移动终端 100 可以从显示设备获取附加信息 200 或通过服务器 300 . 稍后将参考图8对此进行详细描述。 [0143] 在操作 S 730 , 移动端 100 可以在屏幕上显示获得的附加信息。 移动终端 100 可以在将附加信息存储在存储单元中之后通过下载来显示附加信息,或者可以通过流式传输附加信息来显示附加信息。 [0144] 根据示例性实施例的附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息等。 [0145] 这将在稍后参考图8更详细地描述。 图8是示出移动终端的方法的详细流程图 100 根据示例性实施例,显示信息。 [0146] 在操作 S 810 , 移动端 100 可以接收第一输入。 移动端的第一个输入 100 可以是动作输入(例如3D动作输入、旋转动作输入等)、按键输入、触摸输入、弯曲输入、语音输入、多模态输入等。即用户 可以移动移动终端 100 上(+Y 轴方向)和下(-Y 轴方向)和左(-X 轴方向)和右(+X 轴方向),触摸(轻拂、拖动、轻敲、平移等)屏幕(或 GUI显示在屏幕上)的移动终端 100 上下左右,操作移动(方向)键,弯曲移动终端的预定区域(左上,右上,左下,右下) 100 ,或输入包括移动命令的语音。 在操作 S 820 , 移动端 100 可以基于第一输入生成用于选择对象的信号。 例如,在第一输入为移动终端的动作输入的情况下 100 上下左右移动,移动端 100 可以根据移动终端的移动生成用于控制选择区域的移动的信号 100 . 即,在用户移动移动终端的情况下 100 向左(-X轴方向)移动预定值以上,移动终端 100 可以产生用于将选择区域向左移动一格的控制信号。 [0147] 在第一输入为上下左右触摸触摸屏的触摸输入的情况下,移动终端 100 可以根据用户的触摸手势产生用于控制选择区域的移动的信号。 例如,在用户使用手指或电子笔从左向右轻拂触摸屏超过预定距离的情况下,移动终端 100 可以产生用于将选择信号向右移动一个空间的控制信号。 [0148] 在第一输入是操作移动(方向)键的键输入的情况下,移动终端 100可以产生用于将选择区域移动到与方向键对应的位置的控制信号。 [0149] 在第一输入是移动终端的预定区域的弯曲输入的情况下 100 , 可以由柔性显示器形成, 弯曲, 移动终端 100 可以产生用于在对应于弯曲运动的方向上移动选择区域的控制信号。 “弯曲”可以是移动终端的弯曲或变形 100 通过外力。 “弯曲运动”可以是移动终端的弯曲运动或变形 100 . [0150] 例如,在用户弯曲移动终端顶部的情况下 100 , 移动端 100 在用户弯曲移动终端的左侧区域的情况下,可以生成用于将选择区域向上移动一格的控制信号 100 , 移动端 100 可以生成用于将选择区域向左移动一个空间的控制信号,并且在用户弯曲整个移动终端的情况下 100 , 移动端 100 可以产生用于选择包括当前选择区域的对象的控制信号。 [0151] 在第一输入为语音输入的情况下,移动终端 100 可以生成用于将选择区域移动到与语音输入对应的位置的控制信号。 例如,在用户说“向左移动三个空格”的情况下,移动终端 100 可以生成用于将选择区域向左移动三个空间的控制信号。 [0152] 在操作 S 830 , 移动端 100 可以将基于第一输入生成的用于选择对象的信号发送到显示装置 200 . 移动终端 100 根据示例性实施例,可以将用于选择对象的信号发送到显示装置 200 直接或通过服务器 300 . 移动终端 100 根据示例性实施例,还可以使用各种通信方法发送用于选择对象的信号。 [0153] 例如,在移动终端 100 和显示设备 200 在预定范围(局域距离)内,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 直接通过短距离无线通信(蓝牙、Zigbee、近场通信(NFC)、Wi-Fi直连(WFD)、超宽带(UWB)、红外数据协会(IrDA)等)。 移动终端 100 也可以通过移动通信网络(例如,2G/3G/4G、Wibro等)或无线局域网(LAN)(Wi-Fi:ad-hoc模式,基础设施模式)传输用于选择对象的信号 )。 [0154] 在操作 S 840 , 显示设备 200 可以根据移动终端的第一输入移动选择区域 100 . 例如,在第一输入为移动终端的动作输入的情况下 100 向左移动(-X 轴方向),显示设备 200 将选择区域向左移动。 [0155] 根据示例性实施例,显示装置 200 可以基于第一输入控制选择区域的移动速度。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 以高于阈值速度的速度向右移动,显示设备 200 可以将选择区域向右移动几个空格(例如,每3个空格),并且,如果用户移动移动终端 100 以低于阈值速度的速度向左移动,显示设备 200 可以将选择区域向左移动一格。 [0156] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户拖动移动终端的触摸屏 100 在高于阈值速度的速度下,显示设备 200 可以将选择区域移动几个空格,并且,如果用户拖动移动终端的触摸屏 100在低于阈值速度的速度下,显示设备 200 可以将选择区域移动一个空格。 [0157] 根据示例性实施例,在第一输入是弯曲输入的情况下,显示装置 200 可以基于用户弯曲移动终端的预定区域的次数来控制选择区域的移动速度 100 . 例如,在用户弯曲移动终端顶部的情况下 100 三、显示装置 200 可以将选择区域向上移动三个空格,并且在用户弯曲移动终端的右侧区域的情况下 100 两次,显示设备 200 可以将选择区域向右移动两个空格。 此外,显示装置的例子多种多样 200 根据第一个输入移动选择区域。 [0158] 根据示例性实施例,显示装置 200 可以基于第一输入调整屏幕上显示的对象的数量。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 在正面方向(+Z轴方向)上,显示装置 200 可能会减少屏幕上显示的对象数量,并且,如果用户移动移动终端 100 在后方(-Z轴方向),显示装置 200 可能会增加屏幕上显示的对象数量。 [0159] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户多点触摸移动终端的触摸屏上的至少两个点 100 并将两个点拖离对方,显示设备 200 可能会减少屏幕上显示的对象数量,并且如果用户将两个点拖得更近,则显示设备 200 可能会增加屏幕上显示的对象数量。 [0160] 根据示例性实施例,在第一输入是弯曲输入的情况下,如果用户弯曲移动终端的中心部分 100 为凸出,显示装置 200 可以减少屏幕上显示的对象的数量,并且,如果用户弯曲移动终端的中心部分 100 是凹的,显示装置 200 可能会增加屏幕上显示的对象数量。 [0161] 此外,显示装置的例子多种多样 200 根据第一个输入调整屏幕上显示的对象数量。 [0162] 根据示例性实施例,虽然显示装置 200 根据移动终端的第一输入选择对象 100 , 移动端 100 可以从显示装置接收并显示与其中设置有选择区域的对象相对应的内容的缩略图信息 200 . 例如,移动终端 100 可以显示与设置有选择区域的对象相对应的内容的图像、图标、标题、内容类型等。 移动终端可以显示与移动终端的当前位置相对应的选择区域的位置 100 以及选择区域在显示装置的整个屏幕上的移动方向 200 . [0163] 根据另一示例性实施例,移动终端 100 可能会关闭其屏幕或使其屏幕变黑,以使用户的眼睛不会从显示设备的屏幕上分心 200 在其上选择对象。 [0164] 在操作 S 850 , 显示设备 200 选择对象。 根据示例性实施例,显示装置 200 可以基于第一输入选择其中布置了移动的选择区域的对象。 [0165] 根据示例性实施例,显示装置 200 可以识别(强调)其中设置选择区域的对象。 例如,显示设备 200可以将设置选择区域的对象的边框表示为框,也可以将设置选择区域的对象相对于其他对象增大尺寸,或者制作闪烁等动画效果。 [0166] 在操作 S 860 , 移动端 100 可以接收第二个输入。 根据示例性实施例的第二输入可以是用于获得附加信息的用户输入。 移动端二次输入 100 根据示例性实施例,可以包括动作输入、键输入、弯曲输入和语音输入中的至少一种。 例如,用户可以旋转移动终端 100 以预定角度弯曲移动终端的中心部分 100 , 按下移动端的一个选择键 100 ,在请求附加信息的屏幕上触摸(轻敲)GUI,或输入请求附加信息的语音。 第二输入不限于此,并且可以存在多种示例。 [0167] 在操作 S 870 , 移动端 100 可以向显示设备请求与所选对象对应的附加信息 200 . 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 直接或通过服务器 300 . [0168] 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 通过短距离无线通信(蓝牙、Zigbee、NFC、WFD、UWB、IrDA等)、移动通信(例如2G/3G/4G、Wibro等)或无线局域网(Wi -Fi:ad-hoc 模式,基础设施模式)。 [0169] 在操作 S 880 , 显示设备 200 可以将与选择的对象对应的附加信息发送到移动终端 100 . 例如,在选择与电影内容相关的对象的情况下,显示设备 200 可将与电影内容有关的附加信息(代表场景、预览视频、制作信息、概要信息、演员、导演信息、用户评论信息等)传输到移动终端 100 . [0170] 在选择与应用相关的对象的情况下,显示设备 200 可以向移动终端发送关于应用程序的附加信息(例如,应用程序的说明、应用程序审查信息、应用程序更新信息等) 100 . [0171] 根据示例性实施例,在选择与照片有关的对象的情况下,显示装置 200 可以将包括照片的元数据(例如,拍摄地点、拍摄时间等)、与照片中的人物相关的信息(例如,报纸文章、外观电影、代表性音乐等)等附加信息传输到 移动终端 100 . [0172] 根据示例性实施例,在选择与音乐有关的对象的情况下,显示装置 200 可以向移动终端发送关于音乐的附加信息,包括专辑信息、音乐视频、预告视频、预听信息、报纸文章、歌手信息等 100 . [0173] 根据示例性实施例,在选择与网站有关的对象的情况下,显示装置 200 可能会向移动终端发送附加信息,包括有关网站的预览信息 100 . [0174] 根据示例性实施例,在选择与EPG有关的对象的情况下,显示装置 200 可以向移动终端发送关于EPG的附加信息,包括广播节目概要、每集的预览信息等 100 . 在选择与购物项目有关的对象的情况下,显示装置 200可以向移动终端发送关于购物项目的附加信息,包括商品信息、订单信息、推荐信息等 100 . [0175] 根据示例性实施例,显示装置 200 可以将先前存储在存储单元中的附加信息发送到移动终端 100 . 如果附加信息的链接信息仅存储在存储单元中,则显示设备 200 可能会收到来自服务器的附加信息 300 并将接收到的附加信息发送给移动终端 100 . 显示装置 200 可以在搜索引擎或网站中搜索与对象相关的附加信息,并将找到的附加信息提供给移动终端 100 . [0176] 在操作 S 890 , 移动端 100 可以显示获得的附加信息。 移动终端 100 可以基于用户输入控制显示的附加信息。 现在将参考图 9 对此进行详细描述。 [0177] 如上所述,根据示例性实施例,用户可以搜索和/或选择与显示在外部显示设备上的内容有关的对象 200 通过手机端的简单输入 100 并确认与所选对象有关的附加信息,以确定是否接收相应的内容。 [0178] 图9是示出显示装置的方法的流程图 200 感应移动终端的输入 100 并且根据示例性实施例提供附加信息。 此处省略图8和图9之间的重复描述。 [0179] 参考图9,根据示例性实施例,移动终端 100 可以在操作 S 中接收第一输入 910 和显示设备 200 可感应移动终端的输入 100 . [0180] 例如,在操作 S 920 , 显示设备 200 可以感测移动终端的第一输入 100 用于选择对象。 操作 S 930 通过 S 960 图9的对应于操作S 810 通过 S 860 与图8相同,因此这里将省略对其的重复描述。 在操作 S 970 , 显示设备 200 可以感测移动终端的第二输入 100 用于获取对应于所选对象的附加信息。 操作 S 980 通过 S 995 图9的对应于操作S 870 通过 S 890 与图8相同,因此这里将省略对其的重复描述。 [0181] 移动终端的第一输入和第二输入 100 可以包括运动输入(例如,3D运动输入、旋转运动输入等)、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0182] 根据示例性实施例,在第一输入和第二输入是动作输入的情况下,显示装置 200 可以感知移动终端的动作 100 通过相机。 例如,在用户移动移动终端的情况下 100 上下左右或旋转移动终端 100 , 显示设备 200 可感应移动终端的上下左右运动 100 或者移动终端的旋转 100 . [0183] 根据示例性实施例,在第一输入和第二输入是弯曲输入的情况下,显示装置 200 可以感测移动终端的弯曲运动 100 通过相机。 例如,显示设备 200 可以感测移动终端的弯曲位置(坐标值) 100 、弯曲方向、弯曲角度、弯曲速度、弯曲频率、弯曲运动发生时间、弯曲运动持续时间段等。 [0184] 根据示例性实施例,在第一输入和第二输入是触摸输入的情况下,显示装置 200可以通过摄像头感知用户的触摸手势。 [0185] 根据示例性实施例,在第一输入和第二输入是语音输入的情况下,显示装置 200 可以通过麦克风感测用户的语音输入。 [0186] 也就是说,根据示例性实施例,显示装置 200 可以感测第一输入或第二输入以验证从移动终端接收的用于选择对象的信号 100 或用于请求对应于对象的附加信息的信号。 例如,在显示设备 200 感测移动终端的动作输入 100 向右(+X轴方向)移动并从移动终端、显示设备接收用于将选择区域向左移动一格的控制信号 200 可以向移动终端请求控制信号 100 或者可能不跟随用于将选择区域向左移动一个空间的控制信号。 [0187] 根据另一示例性实施例,显示装置 200 可以感测第一输入或第二输入以直接生成用于移动用于选择对象的选择区域的控制命令、用于选择对象的控制命令以及用于将附加信息发送到移动终端的控制命令 100 . [0188] 图10是示出移动终端的方法的流程图 100 通过服务器获取附加信息 300 ,根据示例性实施例。 操作 S 1005 通过 S 1035 图10的对应于操作S 810 通过 S 870 与图8相同(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.249 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.252 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9549143B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.259 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.261 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), CN103577138A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), CN103577138B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.285 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), EP2690880A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), IN1206DELNP2015A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), JP2014027659A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), JP6335448B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), KR101971624B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), KR1020140019078A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.339 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), TW201412097A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.348 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.349 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), TWI574557B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), US20140028921A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), US20170118436A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), US9549143B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270705(Integer), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9549143B2(String), US9549143B2(String), 1484582400(Integer), 270705(Integer), 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185029(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185029(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185029(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185029(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.436 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.437 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.440 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.441 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.451 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.452 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.452 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.458 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.460 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8774071B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and system for intercommunication between mobile terminal and WiMAX base station, and mobile terminal(String), 移动终端与WiMAX基站互通的方法、系统及移动终端(String), US8774071B2(String), A method for intercommunication between a mobile terminal and a WiMAX base station comprises: connecting the mobile terminal with a WiMAX wireless data card via an interface (S102); obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information (S104); and using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station (S106). A system and a mobile terminal are used to implement the method.(String), 一种移动终端与WiMAX基站互通的方法,包括:通过接口(S)将移动终端与WiMAX无线数据卡连接起来。 102 ); 获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡的逻辑连接(S 104 ); 并使用WiMAX无线数据卡实现与WiMAX基站(S 106 )。 一种系统和移动终端用于实现该方法。(String), US13/060648(String), 1230220800(Integer), US8774071B2(String), 1404748800(Integer), 1404748800(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 12(Integer), CN101123577A | CN1859442A | CN1964276A | US20070038764A1 | US20070115899A1 | US20070173283A1 | US20070238448A1 | US20070253339A1 | US20080113692A1 | US20090016246A1 | US20110242964A1 | WO2007078663A2(String), 7(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.473 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185030(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.474 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\9f2d36521c1c462fb69bf22c7b218e8d.png(String), 185030(Integer), 9f2d36521c1c462fb69bf22c7b218e8d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.484 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.485 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.485 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.485 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and system for intercommunication between mobile terminal and WiMAX base station, and mobile terminal(String), 移动终端与WiMAX基站互通的方法、系统及移动终端(String), US8774071B2(String), A method for intercommunication between a mobile terminal and a WiMAX base station comprises: connecting the mobile terminal with a WiMAX wireless data card via an interface (S102); obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information (S104); and using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station (S106). A system and a mobile terminal are used to implement the method.(String), 一种移动终端与WiMAX基站互通的方法,包括:通过接口(S)将移动终端与WiMAX无线数据卡连接起来。 102 ); 获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡的逻辑连接(S 104 ); 并使用WiMAX无线数据卡实现与WiMAX基站(S 106 )。 一种系统和移动终端用于实现该方法。(String), US13/060648(String), 1230220800(Integer), US8774071B2(String), 1404748800(Integer), 1404748800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 12(Integer), CN101123577A | CN1859442A | CN1964276A | US20070038764A1 | US20070115899A1 | US20070173283A1 | US20070238448A1 | US20070253339A1 | US20080113692A1 | US20090016246A1 | US20110242964A1 | WO2007078663A2(String), \20230420\9f2d36521c1c462fb69bf22c7b218e8d.png(String), 7(Integer), 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 1. A method for intercommunication between a mobile terminal and a World Interoperability for Microwave Access (WiMAX) base station, with the mobile terminal being a dual mode terminal which supports two network systems, comprising:connecting the mobile terminal with a WiMAX wireless data card via an interface;obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information; andusing the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station, wherein using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station comprises:the mobile terminal registering with the WiMAX base station through the WiMAX wireless data card, which comprises:the mobile terminal realizing at least one of the following operations through an encapsulated application program interface: network searching, network access, and network authentication; andthe mobile terminal sending to the WiMAX base station an access request for registration; andthe mobile terminal entering the mode of intercommunication with the WiMAX base station.(String), 1.一种移动终端与全球微波接入互通(WiMAX)基站互通的方法,该移动终端为支持两种网络系统的双模终端,包括:移动终端与WiMAX无线数据卡通过接口连接;获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡之间的逻辑连接;和利用WiMAX无线数据卡实现与WiMAX基站的互通,其中,利用WiMAX无线数据卡实现与WiMAX基站的互通包括:移动终端通过WiMAX无线数据卡向WiMAX基站注册,包括:移动终端通过封装的应用程序接口实现以下至少一种操作:网络搜索、网络接入、网络认证。和移动终端向WiMAX基站发送注册接入请求;和移动终端进入与WiMAX基站互通模式。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 2. The method according to claim 1, wherein the interface is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card.(String), 2.根据权利要求1所述的方法,其中接口为通用串行总线接口,WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。3、一种互通系统,用于实现移动终端与全球微波接入互通(WiMAX)基站的互通,包括:移动终端包括:接口模块,用于连接WiMAX无线数据卡与移动终端;连接管理模块,用于选择与WiMAX基站连接的移动终端;和设备管理模块,用于获取和/或配置WiMAX无线数据卡的配置信息,通过WiMAX无线数据卡与WiMAX基站进行互通;其中,移动终端通过WiMAX无线数据卡向WiMAX基站进行注册,其间:移动终端通过封装的应用程序接口实现以下操作中的至少一种:网络搜索、网络接入、网络认证。和移动终端用于向WiMAX基站发送注册接入请求;和其中,WiMAX无线数据卡通过移动终端的接口模块与移动终端连接;和其中,WiMAX基站用于通过WiMAX无线数据卡实现与移动终端的互通。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 3. An intercommunication system, configured to realize the intercommunication between a mobile terminal and a World Interoperability for Microwave Access (WiMAX) base station, comprising:the mobile terminal comprising:an interface module, configured to connect a WiMAX wireless data card with the mobile terminal;a connection managing module, configured to select the mobile terminal to be connected with the WiMAX base station; anda device managing module, configured to obtain and/or configure configuration information of the WiMAX wireless data card, and intercommunicate with the WiMAX base station through the WiMAX wireless data card;wherein the mobile terminal is operative to register with the WiMAX base station through the WiMAX wireless data card, during which:the mobile terminal is operative to realize at least one of the following operations through an encapsulated application program interface: network searching, network access, and network authentication; andthe mobile terminal is operative to send to the WiMAX base station an access request for registration; andwherein, the WiMAX wireless data card is connected with the mobile terminal through the interface module of the mobile terminal; andwherein the WiMAX base station is configured to realize the intercommunication with the mobile terminal through the WiMAX wireless data card.(String), 4.根据权利要求3所述的对讲系统,其中移动终端还包括:电源模块,用于为WiMAX无线数据卡供电。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 4. The intercommunication system according to claim 3, wherein the mobile terminal further comprises:a power supply module, configured to supply power for the WiMAX wireless data card.(String), 5.根据权利要求3所述的对讲系统,其中接口模块为通用串行总线接口,WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 5. The intercommunication system according to claim 3, wherein the interface module is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card.(String), 6.根据权利要求3所述的对讲系统,其中连接管理模块,用于通过调用封装的应用程序接口执行以下操作中的至少一种:网络搜索、网络接入、网络断开、网络认证、频率范围配置、连接方式选择、搜索网络步长设置,认证选项的设置,以及切换选项的设置。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 6. The intercommunication system according to claim 3, wherein the connection managing module is configured to execute at least one of the following operations through invoking the encapsulated application program interface: network searching, network access, network disconnection, network authentication, frequency range configuration, connection mode selection, setting of search net step length, setting of authentication options, and setting of handover options.(String), 7.根据权利要求3所述的对讲系统,其中设备管理模块,用于通过调用封装后的应用程序接口实现以下操作中的至少一种:移动联盟开通、固件更新管理、设备参数配置和获取。(String), 1(Integer), 5(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.498 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185030(Integer), 7. The intercommunication system according to claim 3, wherein the device managing module is configured to realize at least one of the following operations through invoking the encapsulated application program interface: mobile alliance opening, firmware updating management, and configuration and acquisition of device parameters.(String), 1(Integer), 6(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.568 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.571 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.572 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185030(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, in particular to a method, a system and a mobile terminal for intercommunication between a mobile terminal and a world interoperability for microwave access (WiMAX) base station. BACKGROUND OF THE INVENTION [0002]WiMAX is a wideband wireless metropolitan area network (WMAN) technology based on the 802.16 series standards of Institute for Electrical and Electronic Engineers (IEEE). [0003]At present, the dual mode mobile phone of global system for mobile communications (GSM)/wireless fidelity (WiFi) based on IEEE 802.1b standard can realize seamless handover between the GSM network and wireless local area network (WLAN), and support unlicensed mobile access (UMA) technology. Users can make up the defect that the indoor signal of mobile terminal such as mobile phone is weak. When network of the mobile phone is busy or the signal is bad, the mobile phone user can perform voice communication through the WiFi network. In practical application, the handover between the two networks is realized through the voice over IP (VoIP) technology, and the expense using this technology is comparatively low and the technology can provide convenience for the mobile phone and wide frequency wireless phone. In addition, the use of the VoIP technology can also realize the functions of browsing web page, sending and receiving e-mail, short messages and multimedia messages and so on. As long as the mobile phone is moved to the areas covered by the wireless wideband, the user can make a free call worldwide by a network phone mode. [0004]In the present network, there are some areas still not covered by the GSM/WiFi networks, or some with bad signals of the GSM/WiFi networks. Aiming at the above-mentioned situations, the mobile phone terminal can realize the communication through the WiMAX network. Therefore, how to realize the intercommunication between the GSM/WiFi dual mode mobile phone and the WiMAX base station is a problem needed to be solved at present. SUMMARY OF THE PRESENT INVENTION [0005]The present invention is put forward aiming at the intercommunication problem between a GSM/WiFi dual mode mobile phone and a WiMAX base station at present. For this reason, the present invention aims to provide an improved intercommunication scheme between a mobile terminal and the WiMAX base station to solve at least one of above-mentioned problems. [0006]In order to achieve the above-mentioned aim, a method for intercommunication between a mobile terminal and a WiMAX base station is provided according to one aspect of the present invention. [0007]In the method for intercommunication between the mobile terminal and the WiMAX base station according to the present invention, the mobile terminal is a dual mode terminal which supports two network systems except the WiMAX. The method comprises: connecting the mobile terminal with a WiMAX wireless data card via an interface; obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information; and using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station. [0008]Preferably, that using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station comprises: the mobile terminal registering with the WiMAX base station through the WiMAX wireless data card; and the mobile terminal entering the mode of intercommunication with the WiMAX base station. [0009]Preferably, the step of the mobile terminal registering with the WiMAX base station through the WiMAX wireless data card comprises: the mobile terminal realizing at least one of the following operations through an encapsulated application program interface: network searching, network access, and network authentication; and the mobile terminal sending to the WiMAX base station an access request for registration. [0010]Preferably, the interface is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card. [0011]In order to achieve the above-mentioned aim, a mobile terminal is provided according to another aspect of the present invention. [0012]The mobile terminal according to the present invention comprises: an interface module, configured to connect a WiMAX wireless data card with the mobile terminal; a connection managing module, configured to select the mobile terminal to be connected with a WiMAX base station; and a device managing module, configured to obtain and/or configure configuration information of the WiMAX wireless data card, and intercommunicate with the WiMAX base station through the WiMAX wireless data card. [0013]Preferably, the mobile terminal further comprises: a power supply module, configured to supply power for the WiMAX wireless data card. [0014]Preferably, the interface module is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card. [0015]Preferably, the connection managing module is configured to execute at least one of the following operations through invoking encapsulated application program interface: network searching, network access, network disconnection, network authentication, frequency range configuration, connection mode selection, setting of search net step length, setting of authentication options, and setting of handover options. [0016]Preferably, the device managing module is configured to realize at least one of the following operations through invoking encapsulated application program interface: mobile alliance opening, firmware updating management, and configuration and acquisition of device parameters. [0017]In order to achieve the above-mentioned aim, an intercommunication system is further provided according to another aspect of the present invention. [0018]The intercommunication system according to the present invention, which is configured to realize the intercommunication between a mobile terminal and a WiMAX base station, comprises the mobile terminal which is mentioned above. Furthermore, the intercommunication system further comprises: the WiMAX wireless data card, connected with the mobile terminal through the interface module of the mobile terminal; and the WiMAX base station, configured to realize the intercommunication with the mobile terminal through the WiMAX wireless data card. [0019]In virtue of the technical scheme of the present invention, on the basis of small improvement to the software and/or hardware of existing mobile phone terminal (namely, mobile terminal), the present invention realizes the intercommunication between the mobile phone terminal and the WiMAX base station through the WiMAX Universal Serial Bus (USB) wireless data card, solves the problem that the GSM/WiFi dual mode mobile phone can not intercommunicate with the WiMAX base station, improves the compatibility of the mobile phone, and enable user can experience the wideband data service brought by WiMAX technology. BRIEF DESCRIPTION OF THE DRAWINGS [0020]The drawings in the specification provide a further understanding to the present invention and constitute a part of the application. The exemplary embodiments of the present invention and the explanation thereof are given thereafter by way of illustration only, and thus are not limitative of the present invention, and wherein: [0021]FIG. 1 is a flowchart of a method for intercommunication between a mobile terminal and a WiMAX base station according to the embodiment of the present invention; [0022]FIG. 2 is a flowchart of implementation of the software system of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention; [0023]FIG. 3 is a structure diagram of a mobile terminal according to the embodiment of the present invention; [0024]FIG. 4 is a schematic diagram of the hardware system structure of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention; [0025]FIG. 5 is a schematic diagram of the software system architecture of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention; and [0026]FIG. 6 is a structure diagram of the intercommunication system according to the embodiment of the present invention. DETAILED DESCRIPTION [0027]General Description of Functions [0028]In the present invention, the GSM, WiFi, WiMAX multimode terminal, voice service and data service are integrated, a group of voice call continuity (VCC) service components on the basis of IP multimedia subsystem (IMS)/Fixed-Mobile Convergence (FMC) are developed on high and middle grade intelligent mobile phones, and a uniform modularization platform is provided on multimode mobile phone terminals of various platforms and different systems, which can be beared on various wireless communication protocol stacks such as GSM/General Packet Radio Service (GPRS), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Wideband Code Division Multiple Access (WCDMA) and so on, and can also be beared on wideband wireless access modules such as the WiFi, WiMAX and so on, which can meet the development requirement of the FMC. [0029]In the technical solution of the present invention, the mobile terminal is connected with the WiMAX wireless data card via an interface; configuration information of the WiMAX wireless data card is obtained, and the logic connection between the mobile terminal and the WiMAX wireless data card is fulfilled according to the configuration information; and the WiMAX wireless data card is used to fulfill the intercommunication with the WiMAX base station. [0030]The preferable embodiments of the present invention will be detailed hereinafter in connection with the drawings. What should be understood is that the preferable embodiments detailed hereafter are only given by way of illustration and explanation, and thus are not limitative of the present invention. [0031]In the description hereafter, for the purpose of explanation, a plurality of specific details are given to provide thorough comprehension to the present invention. Nevertheless, obviously, the present invention can also be realized without the specific details. In addition, without departing from the spirit and scope defined by the claims appended, the embodiments of the present invention hereafter can be inter-combined with the details in the embodiments. [0032]Method Embodiment [0033]A method for intercommunication between a mobile terminal and WiMAX base station is provided according to the embodiment of the present invention. As mentioned above, in the present embodiment, the mobile terminal is a dual mode terminal which supports two network systems except the WiMAX, e.g. GSM/WiFi dual mode mobile phone. FIG. 1 is a flowchart of the method for intercommunication between a mobile terminal and WiMAX base station according to the embodiment of the present invention. As shown in FIG. 1, the method comprises the steps as follows (step S102-step S106): [0034]Step S102, connecting the mobile terminal with a WiMAX wireless data card via an interface; wherein preferably, in the present embodiment of the present invention, the interface used is an USB interface, and the WiMAX wireless data card is a WiMAX USB wireless data card; and, the mobile terminal provides an independent power supply to the WiMAX wireless data card; [0035]Step S104, obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information; and [0036]Step S106, using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station; wherein concretely, the mobile terminal registers with the WiMAX base station through the WiMAX wireless data card, and the mobile terminal enters the mode of intercommunication with the WiMAX base station after the registration. [0037]In the registering operation in step S106, the mobile terminal realizes at least one of the following operations through an encapsulated API: network searching, network access, and network authentication; and the mobile terminal sends to the WiMAX base station an access request for registration. [0038]In virtue of the embodiment, the wideband data service and the intercommunication of voice and data between the GSM/WiFi dual mode mobile phone and the WiMAX base station can be realized; and voice calling, the automatic handover, manual handover, and seamless handover among the modes such as WiFi/GSM/WiMAX and so on can be guaranteed. [0039]The above-mentioned technical solution will be detailed hereafter by taking the GSM/WiFi dual mode mobile phone as an example. FIG. 2 is a flowchart of implementation of the software system of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention. As shown in FIG. 2, the method comprises the steps as follows: [0040]Step S202, connecting GSM/WiFi dual mode mobile phone with the WiMAX USB wireless data card (corresponding to the step S102 in FIG. 1); [0041]Step S204, starting the device managing (DM) software, which is configured to control the information intercommunication between the WiMAX USB wireless data card and the OMA Server (namely, WiMAX base station) through sending instructions, and fulfilling the functions concerned by operators or users; wherein preferably, the DM mainly realizes OMA DM1.2, FUMO1.0 functions, and configuration and acquisition function of the device parameters (e.g. bootstrapping, provisioning, etc) (corresponding to the step S104 in FIG. 1); [0042]Step S206, selecting whether to connect with the WiMAX base station through the Connection Management (CM) software, wherein the CM realizes the functions of network searching, network access, network disconnection, network authentication and so on through invoking an encapsulated API, and can also realize the specific functions of frequency range configuration, connection mode selection (automatic mode or manual mode), setting of search net step length, setting of authentication options, and setting of handover options, and wherein if the selection result is yes, it executes step S208; and if the selection result is no, it executes step S212; [0043]Step S208, if selecting to connect with the WiMAX base station, then using the USB wireless data card to register the WiMAX network, and executing step S210; [0044]Step S210, the mobile phone entering the intercommunication mode with the WiMAX base station (corresponding to the step S106 in FIG. 1); [0045]Step S212, if selecting to connect with the GSM or WiFi network, then registering the GSM or WiFi network, and executing step S214; [0046]Step S214, the mobile phone entering the mode of intercommunication with the GSM or WiFi network. [0047]In virtue of the embodiment, in the remote area covered by the WiMAX base station, if the mobile phone can not search the GSM and WiFi network, the GSM/WiFi dual mode mobile phone according to the embodiment of the present invention can perform the data and voice services through the way of starting the WiMAX USB wireless data card to connect with the WiMAX base station, with the result of improving the ability of network coverage effectively. [0048]Device Embodiment [0049]A mobile terminal is provided according to the embodiment of the present invention. FIG. 3 is a structure diagram of the mobile terminal according to the embodiment of present invention. As shown in FIG. 3, the device comprises: an interface module 32, a connection managing module 34, and a device managing module 36. Each module will be detailed hereafter. [0050]Concretely, the interface module 32 is configured to connect a WiMAX wireless data card with the mobile terminal; wherein the interface module is a USB interface, and the WiMAX wireless data card is a WiMAX USB wireless data card. The connection managing module 34, connected with the interface module 32, is configured to select the mobile terminal to be connected with the WiMAX base station, and is further configured to execute at least one of the following operations through invoking an encapsulated application program interface: network searching, network access, network disconnection, network authentication, frequency range configuration, connection mode selection, setting of search net step length, setting of authentication options, and setting of handover options. The device managing module 36, connected with the interface module 32 and the connection managing module 34, is configured to obtain and/or configure configuration information of the WiMAX wireless data card, and intercommunicate with the WiMAX base station through the WiMAX wireless data card. Concretely, the device managing module realizes at least one of the following operations through invoking the encapsulated application program interface: Open Mobile Alliance DM1.2, updating management of firmware, and configuration and acquisition of device parameters. [0051]Preferably, the above-mentioned device can further comprise a power supply module (which is not shown in FIG. 3). The power supply module can be configured to supply power for the WiMAX wireless data card. [0052]In virtue of the embodiment, a mobile terminal which can intercommunicate with the WiMAX base station is provided to enable the user experience the wideband data service brought by WiMAX technology. [0053]The present invention will be detailed hereinafter with reference to the drawings and in connection with the embodiment of the intercommunication between the GSM/WiFi dual mode mobile phone (namely, mobile terminal) and the WiMAX base station. FIG. 4 is a schematic diagram of the hardware system structure of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention. As shown in FIG. 4, the hardware system structure comprises: a baseband processor 404, radio frequency part (including a Radio Frequency (RF) processor 406 and a radio frequency Power Amplifier (PA) 408), an internal memory 401, a display 402, a keyboard 403, a coprocessor 407 (including a loud speaker and a microphone) and so on. Additionally, the GSM/WiFi dual mode mobile phone further comprises other parts, such as a power supply module, a chord chip, a digital camera chip, an Mp3 chip, and an MPEG chip and so on (which are not shown in FIG. 4); wherein only one set of voice input device and voice output device is set in the mobile phone. [0054]The GSM/WiFi dual mode mobile phone is connected with the WiMAX USB wireless data card 405 through various interfaces which include, but are not limited to: USB, RS-232, Cardbus, Ethernet, and SDIO. As a data access device, the WiMAX USB wireless data card 405 preferably uses the serial data bus, which meets the USB2.0 criterion, to transmit data and realize the intercommunication between the WiMAX USB wireless data card and the GSM/WiFi dual mode mobile phone. The WiMAX USB wireless data card is provided with an independent power supply module, i.e., the mobile terminal, to supply power for the WiMAX wireless data card. [0055]In the above, the WiMAX USB wireless data card can realize the functions defined in the IEEE802.16 2005 protocol, specific interface (e.g. USB) drive function, chip enable bootstrap function (chip bootstrap is realized by the Bootloader program solidified on the chip of the WiMAX USB wireless data card, is configured to initialize the hardware of the WiMAX USB wireless data card, and establish the mapping of the internal memory space), and firmware download function and so on. The WiMAX USB wireless data card is in the form of firmware, and is downloaded from the mobile phone when the device is power on and started. In the terminal system, the data card is used as a data access device, the data card is provided with a physical interface which is connected with the mobile phone via the USB interface, and adopts the serial data bus, which meets the USB 2.0 criterion, to transmit data. [0056]Through adding a USB interface of the GSM/WiFi dual mode mobile phone, the embodiment improves the hardware design of the GSM/WiFi dual mode mobile phone, and provides hardware condition for the intercommunication between the GSM/WiFi dual mode mobile phone and the WiMAX base station. [0057]The hardware system structure of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station is detailed above. Hereafter, on the basis of the dual mode mobile phone as shown in FIG. 4, the software system architecture of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station is detailed. FIG. 5 is a schematic diagram of the software system architecture of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention. As shown in FIG. 5, the software architecture part mainly comprises a device (WiMAX USB wireless data card) side and a host (GSM/WiFi dual mode mobile phone) side. The structure of the software system architecture will be detailed hereafter. The software system architecture comprises: a USB input output (IO) drive 501, a GSM/WiFi protocol stack 502, a hardware drive 503, a system support software 504, an operating system 505, a Man-Machine Interface (MMI) frame 506, a basic application software 507, a Connection Management (CM) 508, a Device Management (DM) 509, and an encapsulated application program interface (API) 510. [0058]Concretely, the USB IO drive 501 belongs to the device side module, is configured to realize the functions defined in the IEEE802.16 3005 protocol, specific interface (e.g. USB) drive function, and chip enable bootstrap function and so on and in form of firmware, and is stored in the storage media of Flash/EEPROM and etc. of the device. [0059]As described hereafter, the term “storage media” means one or multiple kinds of devices for storing data, which include Read Only Memory (ROM), Random Access Memory (RAM), magnetic RAM, magnetic core memory, magnetic disc storage media, optical storage media, flash memory device and/or the other machine readable media for storing information. The term “machine readable media” includes but is not limited to: portable or fixed storing device, optical storing device, wireless channel, or the other media which can store, hold or load instructions and/or data. [0060]In the GSM/WiFi dual mode mobile phone, the GSM/WiFi protocol stack 502 is configured to realize the GSM/WiFi protocol. The hardware drive 503 is configured to realize the hardware drive of the mobile phone and the drive of the WiMAX USB wireless data card. Furthermore, in the present embodiment, the system support software 504 and the operating system 505 can adopt the operating system of Windows Mobile. The MMI frame 506 is realized by using the window mechanism of Windows Mobile. The basic application software 507 comprises the original call software, short message software, web page browsing software and the other application software of the GSM/WiFi dual mode mobile phone. The CM 508 and the DM 509 belong to the software application layer, and are configured to realize the setting of connection and instruction transmission between the WiMAX connection device and the WiMAX base station. The encapsulated API 510 is configured to provide interfaces for the CM and DM of the upper layer (software application layer), take the responsibility for the realization of the CM and DM functions, and communicate with the drive of the host through invoking the kernel function of the operating system 505. The host drive forwards the message to the WiMAX USB wireless data card through the bus. And then the WiMAX USB wireless data card makes corresponding operations according to the content of the message. [0061]In the realization process of the present embodiment, the CM 508 realizes the functions of network searching, network access, network disconnection, network authentication and so on through invoking the encapsulated API 510, can also realize the specific functions of frequency range configuration, connection mode selection (automatic or manual), setting of search net step length, setting of authentication options, and setting of handover options and so on; the DM 509 realizes the Open Mobile Alliance (OMA) DM1.2 function, Firmware Update Management Object (FUMO) 1.0 function, and device parameters (e.g. bootstrapping, automation configuration and so on) configuration and acquisition through invoking the encapsulated API 510. [0062]Through setting the GSM/WiFi dual mode mobile phone on the software, the embodiment provides software conditions for the realization of the voice and data intercommunication between the GSM/WiFi dual mode mobile phone and the WiMAX base station, and further lays a foundation for realizing the wideband data service, voice call service, IMS VoIP service and so on between the GSM/WiFi dual mode mobile phone and the WiMAX base station. [0063]What needs to be explained is that in the above-mentioned embodiments, the hardware, software, firmware, middleware, microcode, hardware description language or the combinations thereof can be used to realize the embodiments. When the hardware, software, firmware, middleware or microcode are used to realize the embodiment, the program code or code segments for executing necessary tasks can be stored in the machine readable media of the storage media. (A plurality of) processors can execute necessary tasks. The code segments can express any combination of process, function, subprogram, program, routine program, subroutine program, module, object, software package, cluster, or instruction, data structure, or program language. The code segment is coupled into another code segment or a hardware circuit through transmitting and/or receiving information, data, independent variable, or the memory contents. The information, independent variables, parameters, data and so on can be transferred, transmitted or sent in any suitable mode such as memorizer sharing, message passing, token passing, network transmission and so on. [0064]System Embodiment [0065]An intercommunication system is provided according to the embodiment of the present invention. The intercommunication system is configured to realize the intercommunication between the mobile terminal and the WiMAX base station. FIG. 6 is a structure diagram of the intercommunication system according to the embodiment of the present invention. As shown in FIG. 6, the system comprises the above mobile terminal 62 (preferably, the mobile terminal 62 can be the GSM/WiFi dual mode mobile phone based on the above-mentioned structure), and further comprises the WiMAX wireless data card 64 connected with the mobile terminal 62 through the interface module of the mobile terminal, and the WiMAX base station 66. [0066]Concretely, the WiMAX base station 66, connected with the WiMAX wireless data card 64, is configured to realize the intercommunication with the mobile terminal through the WiMAX wireless data card. Preferably, the mobile terminal 62 can be connected with the WiMAX wireless data card 64 through an interface; configuration information of the WiMAX wireless data card 64 is obtained, and the logic connection between the mobile terminal 62 and the WiMAX wireless data card 64 is fulfilled according to the configuration information; and the WiMAX wireless data card 64 is used to fulfill the intercommunication with the WiMAX base station 66, i.e., the mobile terminal 62 registers with the WiMAX base station 66 through the WiMAX wireless data card 64; and then the mobile terminal 62 enters the mode of intercommunication with the WiMAX base station 66. [0067]In virtue of the present embodiment, on the basis of minor improvement to the software and/or hardware of existing GSM/WiFi dual mode mobile phone, it realizes the intercommunication between the GSM/WiFi dual mode mobile phone terminal and the WiMAX base station through the WiMAX USB wireless data card, improves the compatibility of the mobile phone, and enables the user experience the wideband data service brought by WiMAX technology. [0068]Obviously, those skilled in the art shall understand that the above-mentioned modules and steps of the present invention can be realized by using general purpose calculating device, can be integrated in one calculating device or distributed on a network which consists of a plurality of calculating devices. Alternatively, the modules and the step of the present invention can be realized by using the executable program code of the calculating device. Consequently, the modules and the steps can be stored in the storage device and executed by the calculating device, or the modules and the steps are made into integrated circuit module respectively, or a plurality of modules or steps thereof are made into one integrated circuit module. In this way, the present invention is not restricted to any particular hardware and software combination. [0069]The descriptions above are only preferable embodiments of the present invention, which are not used to restrict the present invention. For those skilled in the art, the present invention may have various changes and variations. Any amendments, equivalent substitutions, improvements etc. within the spirit and principle of the present invention are all concluded in the scope of protection of the present invention.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端与全球微波接入互通(WiMAX)基站互通的方法、系统及移动终端。 发明背景 [0002] WiMAX是基于电气和电子工程师协会(IEEE)的802.16系列标准的宽带无线城域网(WMAN)技术。 [0003] 目前,基于IEEE 802.1b标准的全球移动通信系统(GSM)/无线保真(WiFi)双模手机可实现GSM网络与无线局域网(WLAN)的无缝切换,并支持免授权移动 接入(UMA)技术。 用户可以弥补手机等移动终端室内信号弱的缺陷。 当手机网络繁忙或信号不好时,手机用户可以通过WiFi网络进行语音通话。 在实际应用中,两个网络之间的切换是通过网络电话(VoIP)技术实现的,使用该技术的费用较低,可以为手机和宽频无线电话提供方便。 此外,利用VoIP技术还可以实现浏览网页、收发电子邮件、短信和彩信等功能。 只要将手机移到无线宽带覆盖的地区,用户就可以通过网络电话方式拨打全球免费电话。 [0004] 在目前的网络中,还有一些区域还没有被GSM/WiFi网络覆盖,或者GSM/WiFi网络信号不好。 针对上述情况,手机终端可以通过WiMAX网络实现通信。 因此,如何实现GSM/WiFi双模手机与WiMAX基站的互通是目前需要解决的问题。 发明内容 [0005] 本发明是针对目前GSM/WiFi双模手机与WiMAX基站的互通问题而提出的。 为此,本发明旨在提供一种改进的移动终端与WiMAX基站之间的互通方案,以解决上述问题中的至少一个。 [0006] 为实现上述目的,根据本发明的一个方面,提供了一种移动终端与WiMAX基站互通的方法。 [0007] 本发明的移动终端与WiMAX基站互通的方法中,所述移动终端为双模终端,支持除WiMAX之外的两种网络制式。 该方法包括:移动终端与WiMAX无线数据卡通过接口连接; 获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡之间的逻辑连接; 利用WiMAX无线数据卡实现与WiMAX基站的互通。 [0008] 优选地,利用WiMAX无线数据卡实现与WiMAX基站的互通包括: 移动终端通过WiMAX无线数据卡向WiMAX基站注册; 移动终端进入与WiMAX基站互通模式。 [0009] 优选地,移动终端通过WiMAX无线数据卡向WiMAX基站注册的步骤包括:移动终端通过封装的应用程序接口实现以下操作中的至少一种:网络搜索、网络接入、网络认证。 移动终端向WiMAX基站发送注册接入请求。 [0010] 优选地,所述接口为通用串行总线接口,所述WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。 [0011]为实现上述目的,根据本发明的另一方面,提供了一种移动终端。 [0012] 本发明的移动终端包括: 接口模块,用于连接WiMAX无线数据卡与移动终端; 连接管理模块,用于选择移动终端与WiMAX基站连接; 设备管理模块,用于获取和/或配置WiMAX无线数据卡的配置信息,通过WiMAX无线数据卡与WiMAX基站进行互通。 [0013] 优选地,移动终端还包括: 电源模块,用于为WiMAX无线数据卡供电。 [0014] 优选地,所述接口模块为通用串行总线接口,所述WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。 [0015] 优选地,连接管理模块用于通过调用封装的应用程序接口执行以下操作中的至少一种:网络搜索、网络接入、网络断开、网络认证、频率范围配置、连接方式选择、搜索网络步长设置。 ,认证选项的设置,以及切换选项的设置。 [0016] 优选地,所述设备管理模块用于通过调用封装的应用程序接口实现以下操作中的至少一种:移动联盟开通、固件更新管理、设备参数的配置和获取。 [0017] 为实现上述目的,根据本发明的另一方面,还提供了一种对讲系统。 [0018] 本发明的对讲系统,用于实现移动终端与WiMAX基站的互通,包括上述移动终端。 进一步地,所述对讲系统还包括: WiMAX无线数据卡,通过移动终端的接口模块与移动终端连接; WiMAX基站,用于通过WiMAX无线数据卡实现与移动终端的互通。 [0019] 利用本发明的技术方案,本发明在对现有手机终端(即移动终端)的软件和/或硬件进行小幅改进的基础上,实现了手机终端与WiMAX的互通。 基站通过WiMAX通用串行总线(USB)无线数据卡,解决了GSM/WiFi双模手机无法与WiMAX基站互通的问题,提高了手机的兼容性,让用户体验到 WiMAX技术带来的宽带数据服务。 附图的简要说明 [0020] 说明书中的附图提供对本发明的进一步理解,构成本申请的一部分。 以下给出本发明的示例性实施例及其解释仅是为了说明,而不是对本发明的限制,其中: [0021] 图1为本发明实施例的移动终端与WiMAX基站互通的方法流程图; [0022] 图2为本发明实施例的支持与WiMAX基站互通的GSM/WiFi双模手机软件系统的实现流程图; [0023] 图3为本发明实施例的移动终端的结构图; [0024] 图4为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的硬件系统结构示意图; [0025]图5为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的软件系统架构示意图; 和 [0026] 图6是根据本发明实施例的对讲系统的结构图。 详细说明 [0027] 功能概述 [0028] 本发明将GSM、WiFi、WiMAX多模终端、语音业务和数据业务融为一体,是一组基于IP多媒体子系统(IMS)/固定移动融合(FMC)的语音呼叫连续性(VCC)业务组件。 )在高中档智能手机上开发,为各平台、不同制式的多模手机终端提供统一的模块化平台,可承载GSM/General Packet Radio Service等多种无线通信协议栈( GPRS)、时分-同步码分多址(TD-SCDMA)、宽带码分多址(WCDMA)等,也可承载在WiFi、WiMAX等宽带无线接入模块上, 能够满足FMC的发展需求。 [0029] 本发明技术方案中,移动终端通过接口与WiMAX无线数据卡连接; 获取WiMAX无线数据卡的配置信息,根据配置信息实现移动终端与WiMAX无线数据卡之间的逻辑连接; WiMAX无线数据卡用于实现与WiMAX基站的互通。 [0030] 下面结合附图详细说明本发明的优选实施例。 应当理解的是,以下所详述的优选实施例仅用于举例说明,并不用于限制本发明。 [0031] 在下文的描述中,为了解释的目的,给出了多个具体细节以提供对本发明的透彻理解。 尽管如此,显然,本发明也可以在没有具体细节的情况下实现。 此外,在不脱离所附权利要求所界定的精神和范围的情况下,本发明的实施例可以与实施例中的细节相互组合。 [0032] 方法实施例 [0033] 本发明实施例提供了一种移动终端与WiMAX基站互通的方法。 如前所述,在本实施例中,移动终端为双模终端,支持除WiMAX之外的两种网络制式,例如移动终端。 GSM/WiFi双模手机。 图1为本发明实施例的移动终端与WiMAX基站互通方法的流程图。 如图1所示,该方法包括以下步骤(步骤S 102 -脚步 106 ): [0034] 脚步 102 、移动终端与WiMAX无线数据卡通过接口连接; 其中,优选地,本发明实施例中,所使用的接口为USB接口,所述WiMAX无线数据卡为WiMAX USB无线数据卡。 移动终端为WiMAX无线数据卡提供独立供电。 [0035] 脚步 104 、获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡之间的逻辑连接; 和 [0036] 脚步 106 、利用WiMAX无线数据卡实现与WiMAX基站的互通; 其中,具体地,移动终端通过WiMAX无线数据卡向WiMAX基站注册,注册后移动终端进入与WiMAX基站互通的模式。 [0037] 在步骤S的注册操作中 106,移动终端通过封装的API实现以下操作中的至少一种:网络搜索、网络访问、网络认证; 移动终端向WiMAX基站发送注册接入请求。 [0038] 通过本实施例,可以实现GSM/WiFi双模手机与WiMAX基站之间的宽带数据业务和语音数据互通。 语音通话,保证WiFi/GSM/WiMAX等模式间的自动切换、手动切换、无缝切换。 [0039] 下面以GSM/WiFi双模手机为例对上述技术方案进行详细说明。 图2为本发明实施例的支持与WiMAX基站互通的GSM/WiFi双模手机软件系统的实现流程图。 如图2所示,该方法包括以下步骤: [0040] 脚步 202 ,用WiMAX USB无线数据卡连接GSM/WiFi双模手机(对应步骤S 102 在图 1 中); [0041] 脚步 204 、启动设备管理(DM)软件,用于通过发送指令控制WiMAX USB无线数据卡与OMA Server(即WiMAX基站)之间的信息互通,实现运营商或用户关心的功能; 其中优选地,DM主要实现OMA DM1.2、FUMO1.0功能,以及设备参数的配置和获取功能(如bootstrapping、provisioning等)(对应步骤S 104 在图 1 中); [0042] 脚步 206 ,通过连接管理(CM)软件选择是否与WiMAX基站连接,CM通过调用封装的API实现网络搜索、网络接入、网络断开、网络认证等功能,也可以实现 频率范围配置、连接模式选择(自动模式或手动模式)、搜索网步长设置、认证选项设置、切换选项设置的具体功能,如果选择结果为是,则执行步骤S 208 ; 如果选择结果为否,则执行步骤S 212 ; [0043] 脚步 208 ,如果选择连接WiMAX基站,则使用USB无线数据卡注册WiMAX网络,执行步骤S 210 ; [0044] 脚步 210 ,手机进入与WiMAX基站互通模式(对应步骤S 106 在图 1 中); [0045] 脚步 212 ,如果选择连接GSM或WiFi网络,则注册GSM或WiFi网络,执行步骤S 214 ; [0046] 脚步 214 ,手机进入与GSM或WiFi网络互通模式。 [0047] 通过本实施例,在WiMAX基站覆盖的偏远地区,如果手机搜索不到GSM和WiFi网络,本发明实施例的GSM/WiFi双模手机可以进行数据传输。 和语音业务通过启动WiMAX USB无线数据卡与WiMAX基站连接的方式,有效提高网络覆盖能力。 [0048] 装置实施例 [0049] 根据本发明实施例,提供了一种移动终端。 图3是根据本发明实施例的移动终端的结构图。 如图3所示,该装置包括:接口模块 32 , 一个连接管理模块 34 , 和一个设备管理模块 36 . 下面将详细介绍每个模块。 [0050] 具体来说,接口模块 32 用于与移动终端连接WiMAX无线数据卡; 其中,接口模块为USB接口,WiMAX无线数据卡为WiMAX USB无线数据卡。 连接管理模块 34 , 与接口模块相连 32,用于选择与WiMAX基站连接的移动终端,还用于通过调用封装的应用程序接口执行以下至少一种操作:网络搜索、网络接入、网络断开、网络认证、 频率范围配置、连接方式选择、搜索网步长设置、认证选项设置、切换选项设置。 设备管理模块 36 , 与接口模块相连 32 和连接管理模块 34 ,用于获取和/或配置WiMAX无线数据卡的配置信息,通过WiMAX无线数据卡与WiMAX基站互通。 具体的,设备管理模块通过调用封装后的应用程序接口实现以下操作中的至少一种:打开移动联盟DM1.2、更新固件管理、配置和获取设备参数。 [0051] 优选地,上述装置还可以包括电源模块(图3中未示出)。 供电模块可以配置为WiMAX无线数据卡供电。 [0052] 通过本实施例,提供了一种能够与WiMAX基站互通的移动终端,使用户能够体验到WiMAX技术带来的宽带数据服务。 [0053] 下面结合附图,结合GSM/WiFi双模手机(即移动终端)与WiMAX基站互通的实施例,对本发明进行详细说明。 图4为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的硬件系统结构示意图。 如图4所示,硬件系统结构包括:基带处理器 404 ,射频部分(包括射频(RF)处理器 406 和射频功率放大器 (PA) 408 ), 内部存储器 401 , 一个显示器 402 , 键盘 403 , 一个协处理器 407 (包括扬声器和麦克风)等。 此外,GSM/WiFi双模手机还包括电源模块、和弦芯片、数码相机芯片、Mp3芯片、MPEG芯片等其他部分(图4中未显示) ); 其中,手机中只设置了一套语音输入设备和语音输出设备。 [0054] GSM/WiFi双模手机连接WiMAX USB无线数据卡 405 通过各种接口,包括但不限于:USB、RS-232、Cardbus、以太网和 SDIO。 WiMAX USB无线数据卡作为数据存取设备 405 优选采用符合USB2.0标准的串行数据总线传输数据,实现WiMAX USB无线数据卡与GSM/WiFi双模手机的互通。 WiMAX USB无线数据卡设有独立的供电模块即移动终端,为WiMAX无线数据卡供电。 [0055] 以上,WiMAX USB无线数据卡可以实现IEEE802.16 2005协议定义的功能,特定接口(如USB)驱动功能,芯片使能自举功能(芯片自举是通过固化在芯片上的Bootloader程序实现的) WiMAX USB无线数据卡,用于初始化WiMAX USB无线数据卡的硬件,建立内存空间的映射),以及固件下载功能等。 WiMAX USB无线数据卡以固件形式存在,在设备上电启动时从手机下载。 在终端系统中,数据卡作为数据访问设备,数据卡带有物理接口,通过USB接口与手机连接,采用串行数据总线,符合USB 2.0规范 , 传输数据。 [0056]本实施例通过增加GSM/WiFi双模手机的USB接口,改进了GSM/WiFi双模手机的硬件设计,为GSM/WiFi双模手机与WiMAX互通提供了硬件条件。 基站。 [0057] 上面详述了支持与WiMAX基站互通的GSM/WiFi双模手机的硬件系统结构。 下面以图4所示的双模手机为基础,详细说明支持与WiMAX基站互通的GSM/WiFi双模手机的软件系统架构。 图5为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的软件系统架构示意图。 如图5所示,软件架构部分主要包括设备(WiMAX USB无线数据卡)端和主机(GSM/WiFi双模手机)端。 下面将详细介绍软件系统架构的结构。 软件系统架构包括:USB输入输出(IO)驱动 501 , 一个 GSM/WiFi 协议栈 502 , 一个硬件驱动器 503 , 系统支持软件 504 , 一个操作系统 505 , 人机界面 (MMI) 框架 506 , 基础应用软件 507 , 连接管理 (CM) 508 , 设备管理 (DM) 509 , 以及封装的应用程序接口 (API) 510 . [0058] 具体来说,USB IO 驱动器 501 属于设备端模块,用于以固件的形式实现IEEE802.16 3005协议定义的功能、特定接口(如USB)驱动功能、芯片使能bootstrap功能等,存放在 设备的Flash/EEPROM等存储介质。 [0059] 下文所述,“存储介质”是指一种或多种用于存储数据的设备,包括只读存储器(ROM)、随机存取存储器(RAM)、磁RAM、磁芯存储器、磁盘存储介质、光 存储介质、闪存设备和/或其他用于存储信息的机器可读介质。 术语“机器可读介质”包括但不限于:便携式或固定存储设备、光存储设备、无线信道或其他可以存储、保存或加载指令和/或数据的介质。 [0060] GSM/WiFi双模手机中,GSM/WiFi协议栈 502 配置实现GSM/WiFi协议。 硬件驱动 503 配置实现手机的硬件驱动和WiMAX USB无线数据卡的驱动。 此外,在本实施例中,系统支持软件 504 和操作系统 505 可采用Windows Mobile操作系统。 人机界面框架 506 是利用Windows Mobile的窗口机制实现的。 基础应用软件 507 包括GSM/WiFi双模手机原有的通话软件、短信软件、网页浏览软件和其他应用软件。 CM 508 和DM 509 属于软件应用层,用于实现WiMAX连接设备与WiMAX基站之间的连接设置和指令传输。 封装的API 510 用于为上层(软件应用层)的CM和DM提供接口,负责CM和DM功能的实现,通过调用操作系统的内核函数与宿主机的驱动进行通信 505 . 主机驱动通过总线将报文转发给WiMAX USB无线数据卡。 然后WiMAX USB无线数据卡根据报文内容进行相应的操作。 [0061] 在本实施例的实现过程中,CM 508 通过调用封装的API实现网络搜索、网络访问、网络断开、网络认证等功能 510,还可以实现频率范围配置、连接方式选择(自动或手动)、搜索网步长设置、认证选项设置、切换选项设置等具体功能; DM 509 通过调用封装的API实现Open Mobile Alliance (OMA) DM1.2功能、Firmware Update Management Object (FUMO) 1.0功能,以及设备参数(如bootstrapping、automation configuration等)的配置和获取 510 . [0062] 本实施例通过在软件上对GSM/WiFi双模手机进行设置,为实现GSM/WiFi双模手机与WiMAX基站之间的语音和数据互通提供了软件条件,进一步为实现 GSM/WiFi双模手机与WiMAX基站之间的宽带数据业务、语音通话业务、IMS VoIP业务等。 [0063] 需要说明的是,在上述实施例中,可以采用硬件、软件、固件、中间件、微码、硬件描述语言或其组合来实现本实施例。 当采用硬件、软件、固件、中间件或微代码来实现本实施例时,执行必要任务的程序代码或代码段可以存储在存储介质中的机器可读介质中。 (多个)处理器可以执行必要的任务。 代码段可以表示过程、函数、子程序、程序、例程、子例程、模块、对象、软件包、簇或指令、数据结构或程序语言的任意组合。 代码段通过发送和/或接收信息、数据、自变量或存储器内容耦合到另一个代码段或硬件电路。 信息、自变量、参数、数据等可以以存储器共享、消息传递、令牌传递、网络传输等任何合适的方式传输、传输或发送。 [0064] 系统实施例 [0065] 根据本发明实施例,提供了一种对讲系统。 互通系统用于实现移动终端与WiMAX基站之间的互通。 图6是根据本发明实施例的对讲系统的结构图。 如图6所示,该系统包括上述移动终端 62 (最好是移动端 62 可以是基于上述结构的GSM/WiFi双模手机),还包括WiMAX无线数据卡 64 与移动端连接 62 通过移动终端接口模块,与WiMAX基站 66 . [0066] 具体来说,WiMAX基站 66 , 连接WiMAX无线数据卡 64 ,用于通过WiMAX无线数据卡实现与移动终端的互通。 优选地,移动终端 62 可连接WiMAX无线数据卡 64 通过接口; WiMAX无线数据卡配置信息 64 得到,移动端之间的逻辑连接 62 和WiMAX无线数据卡 64 根据配置信息完成; 和WiMAX无线数据卡 64 用于实现与WiMAX基站的互通 66 ,即移动端 62 向 WiMAX 基站注册 66 通过WiMAX无线数据卡 64 ; 然后是移动端 62 进入与WiMAX基站互通模式 66 . [0067] 本实施例在对现有GSM/WiFi双模手机的软件和/或硬件进行细微改进的基础上,通过以下方式实现GSM/WiFi双模手机终端与WiMAX基站的互通。 WiMAX USB无线数据卡,提高了手机的兼容性,让用户体验到WiMAX技术带来的宽带数据服务。 [0068] 显然,本领域的技术人员应该理解,本发明的上述模块和步骤可以使用通用计算装置来实现,可以集成在一个计算装置中,也可以分布在由多个计算装置组成的网络上。 设备。 可选地,本发明的模块和步骤可以通过计算装置的可执行程序代码来实现。 因此,模块和步骤可以存储在存储装置中并由计算装置执行,或者模块和步骤分别做成集成电路模块,或者多个模块或步骤做成一个集成电路模块。 . 这样,本发明不限于任何特定的硬件和软件组合。 [0069] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101345926A(String), EP2323280A1(String), EP2323280A4(String), US20110158217A1(String), US8774071B2(String), WO2010022575A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101345926A(String), EP2323280A1(String), EP2323280A4(String), US20110158217A1(String), US8774071B2(String), WO2010022575A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8774071B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101345926A(String), EP2323280A1(String), EP2323280A4(String), US20110158217A1(String), US8774071B2(String), WO2010022575A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270706(Integer), CN101345926A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.610 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270706(Integer), EP2323280A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270706(Integer), EP2323280A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.633 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270706(Integer), US20110158217A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270706(Integer), US8774071B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270706(Integer), WO2010022575A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8774071B2(String), US8774071B2(String), 1404748800(Integer), 270706(Integer), 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.679 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.680 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.681 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185030(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185030(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.691 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.692 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185030(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185030(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.708 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.709 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.720 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.721 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.721 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.725 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.725 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185030(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.740 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20170118436A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.742 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.743 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US20170118436A1(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择在外部显示设备上显示的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US15/386556(String), 1482249600(Integer), US20170118436A1(String), 1493222400(Integer), 美国(String), 2(Integer), KR(String), 9(Integer), 5(Integer), US20120017237A1 | US20130040623A1 | US20130041938A1 | US20130103446A1 | US8112371B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.750 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.750 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185031(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f66d77f2c2ed409d96405ded3ca1293d.png(String), 185031(Integer), f66d77f2c2ed409d96405ded3ca1293d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.761 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.762 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US20170118436A1(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择在外部显示设备上显示的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US15/386556(String), 1482249600(Integer), US20170118436A1(String), 1493222400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 9(Integer), 5(Integer), US20120017237A1 | US20130040623A1 | US20130041938A1 | US20130103446A1 | US8112371B1(String), \20230420\f66d77f2c2ed409d96405ded3ca1293d.png(String), 20(Integer), 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.772 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.772 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.773 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.774 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 1. A mobile device comprising:a display;a communication interface; anda processor configured to:control the communication interface to transmit, to an external display device, a signal for selecting an object from among a plurality of objects based on a first input of a user through the mobile device;control the communication interface to receive additional information corresponding to the object;control the display to display information related to the object based on the additional information, andcontrol the communication interface to request a content corresponding to the information related to the object; andcontrol the communication interface to receive the content corresponding to the information.(String), 1.移动设备包括:显示器;通信接口;和处理器配置为:基于用户通过移动设备的第一输入,控制通信接口向外部显示设备发送用于从多个对象中选择对象的信号;控制通信接口接收对象对应的附加信息;基于附加信息控制显示器显示与对象相关的信息,以及控制通信接口请求与对象相关的信息对应的内容;和控制通信接口接收信息对应的内容。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 2. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to request, to the external display device, the additional information corresponding to the object based on a second input of the user through the mobile device, andthe additional information including the information related to the object.(String), 2.如权利要求1所述的移动设备,其中处理器还被配置为基于用户通过移动设备的第二输入控制通信接口向外部显示设备请求与对象对应的附加信息,以及附加信息包括与对象相关的信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 3. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to convert the signal for selecting the object according to a control protocol of the external display device.(String), 3.如权利要求1所述的移动设备,其中处理器还用于控制移动设备根据外部显示设备的控制协议转换用于选择对象的信号。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 4. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to transmit a signal for controlling a movement of a selection region for selecting the object from among the plurality of objects displayed on the external display device.(String), 4.如权利要求1所述的移动设备,其中处理器还被配置为控制通信接口发送用于控制选择区域的移动的信号,该选择区域用于从显示在外部显示设备上的多个对象中选择对象。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 5. The mobile device of claim 4, wherein the processor is further configured to control the communication interface to transmit a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on a input of the user.(String), 5.如权利要求4所述的移动设备,其中处理器还被配置为控制通信接口发送用于控制选择区域的移动方向、选择区域的移动速度和显示在外部显示器的屏幕上的对象的数量中的至少一个的信号设备基于用户的输入。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 6. The mobile device of claim 4, wherein the processor is further configured to control the display to display thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 6.如权利要求4所述的移动设备,其中处理器还被配置为在请求附加信息之前控制显示器显示选择区域所在的对象对应的缩略图信息。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 7. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to receive link information as the additional information from the external display device and to receive the content from a server based on the received link information.(String), 7.如权利要求1所述的移动设备,其中处理器还被配置为控制通信接口从外部显示设备接收链接信息作为附加信息,并基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 8. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to request the content based on a third input of the user through the mobile device.(String), 8.如权利要求1所述的移动设备,其中处理器还被配置为基于用户通过移动设备的第三输入来控制通信接口请求内容。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 9. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to request control authorization from the external display device and receive a control authorization acceptance message from the external display device prior to the transmitting of the signal for selecting the object.(String), 9.如权利要求1所述的移动设备,其中处理器还被配置为在发送用于选择对象的信号之前,控制通信接口向外部显示设备请求控制授权并从外部显示设备接收控制授权接受消息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.776 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 10. The mobile device of claim 1, wherein the plurality of objects comprise at least one from among an icon, a link, a picture, a text, and an index item11. The mobile device of claim 1, wherein the content comprise at least one from among a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG).(String), 10.如权利要求1所述的移动设备,其中多个对象包括图标、链接、图片、文本和索引项中的至少一个11.如权利要求1所述的移动设备,其中内容包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 12. The mobile device of claim 1, wherein the additional information comprises at least one from among preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information.(String), 12.如权利要求1所述的移动设备,其中附加信息包括预览信息、试听信息、应用信息、用户评论信息、更新信息、报刊文章信息、商品信息、电影信息、游戏信息、广告图片信息、专辑信息中的至少一种。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 13. The mobile device of claim 1, wherein the processor is further configured to control the mobile device todetermine an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generate a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generate a signal for controlling the content displayed on the mobile device based on the user input.(String), 13.如权利要求1所述的移动设备,其中处理器还被配置为控制移动设备以确定移动设备的操作模式;和响应于确定操作模式是第一模式,基于用户输入产生用于控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,产生用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 14. A method in which a mobile device displays information, the method comprising:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects based on a first input of a user through the mobile device;receiving additional information corresponding to the object;displaying information related to the object based on the additional information;requesting a content corresponding to the information related to the object; andreceiving the content corresponding to the information.(String), 14.一种方法其中移动设备显示信息,该方法包括:基于用户通过移动设备的第一输入,向外部显示设备发送用于从多个对象中选择对象的信号;接收对应于对象的附加信息;基于附加信息显示与对象相关的信息;请求与对象相关的信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 15. The method of claim 14, wherein the transmitting the signal for selecting the object comprises transmitting a signal for controlling a movement of a selection region for selecting the object from among the plurality of objects displayed on the external display device.(String), 15.如权利要求14所述的方法,其中发送用于选择对象的信号包括发送用于控制选择区域的移动的信号,该选择区域用于从显示在外部显示设备上的多个对象中选择对象。(String), 1(Integer), 13(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 16. The method of claim 15, wherein the transmitting the signal for controlling the movement of the selection region comprises transmitting a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on a input of the user.(String), 16.如权利要求15所述的方法,其中发送用于控制选择区域的移动的信号包括发送用于控制选择区域的移动方向、选择区域的移动速度和显示在选择区域的屏幕上的对象的数量中的至少一项的信号基于用户输入的外部显示设备。(String), 1(Integer), 14(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 17. The method of claim 15, further comprising displaying thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 17.如权利要求15所述的方法,还包括在请求附加信息之前,显示选择区域所在的对象对应的缩略图信息。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 18. The method of claim 14, wherein the receiving the additional information comprises receiving link information from the external display device and,wherein the receiving the content comprises receiving the content from a server based on the received link information.(String), 18.如权利要求14所述的方法,其中接收附加信息包括从外部显示设备接收链接信息,并且,其中,接收内容包括基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 16(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 19. The method of claim 14, further comprising:determining an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generating a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generating a signal for controlling the content displayed on the mobile device based on the user input.(String), 19.如权利要求14所述的方法,还包括:确定移动设备的操作模式;和响应于确定操作模式是第一模式,基于用户输入生成用于控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,生成用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 17(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185031(Integer), 20. A non-transitory computer-readable recording medium having recorded thereon a program for executing a method in which a mobile device displays information,wherein the method comprising:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects based on a first input of a user through the mobile device;receiving additional information corresponding to the object;displaying information related to the object based on the additional information;requesting a content corresponding to the information related to the object; andreceiving the content corresponding to the information.(String), 20.一种非暂时性计算机可读记录介质有在其上记录用于执行移动设备显示信息的方法的程序,其中,所述方法包括:基于用户通过移动设备的第一输入,向外部显示设备发送用于从多个对象中选择对象的信号;接收对应于对象的附加信息;基于附加信息显示与对象相关的信息;请求与对象相关的信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.927 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185031(Integer), CROSS-REFERENCE TO RELATED PATENT APPLICATION [0001]This application is a continuation application of U.S. patent application Ser. No. 13/950,507, filed on Jul. 25, 2013, which claims priority from Korean Patent Application No. 10-2012-0081434, filed on Jul. 25, 2012, in the Korean Intellectual Property Office, the disclosures of which are incorporated herein in its entirety by reference. BACKGROUND [0002]1. Field [0003]Exemplary embodiments relate to a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object, a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal, and a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0004]2. Description of the Related Art [0005]A smart television (TV) is a multifunctional TV capable of utilizing various functions such as web surfing, video on demand (VOD) watching, a social networking service (SNS), a game, etc. by combining a TV and an Internet access function and installing various applications. [0006]One characteristic of the smart TV is that a user and the TV can transmit and receive information from each other. This is a difference between the smart TV and an existing TV that merely transfers information unilaterally. Thus, the smart TV is also referred to as an interactive TV. [0007]However, it is very inconvenient for the user to use the various functions of the smart TV by using a standard remote controller. In particular, when the user browses or downloads contents, the user needs to manipulate the remote controller through several steps. [0008]Therefore, a control device or system for allowing the user to easily control the smart TV is needed. SUMMARY [0009]Exemplary embodiments provide a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object. [0010]Exemplary embodiments also provide a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal. [0011]Exemplary embodiments also provide a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0012]According to an aspect of an exemplary embodiment, there is provided a method in which a mobile terminal displays information, the method including: transmitting a first signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; transmitting a second signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0013]The transmitting of the first signal for selecting the object may include: converting the signal for selecting the object according to a control protocol of the external display device. [0014]The transmitting of the first signal for selecting the object may include: transmitting a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0015]The transmitting of the signal for controlling the movement of the selection region may include: transmitting a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen of the external display device based on the first input. [0016]The transmitting of the first signal for selecting the object may include: displaying thumbnail information of contents corresponding to the object on the screen of the mobile terminal. [0017]The thumbnail information may include at least one of an image of the contents corresponding to the object, a title of the contents, and a type of the contents. [0018]The transmitting of the first signal for selecting the object may include: displaying a movement direction of the mobile terminal on the screen according to the first input. [0019]The first input and the second input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0020]The first input may include a three-dimensional (3D) motion input for moving the mobile terminal in a 3D direction, wherein the second input includes a rotational motion input for rotating the mobile terminal by more than a predetermined angle. [0021]The transmitting of the second signal for requesting additional information may include: receiving the additional information from the display device. [0022]The transmitting of the second signal for requesting additional information may include: receiving link information of the additional information from the external display device based on the second input; and receiving the additional information from a server based on the received link information. [0023]The transmitting of the first signal for selecting the object to the display device may include: requesting control authorization from the external display device; and receiving a control authorization acceptance message from the external display device. [0024]The contents may include at least one of a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG). [0025]The additional information may include at least one of preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information. [0026]The method may further include: controlling the additional information displayed on the screen of the mobile terminal based on a third input of the user through the mobile terminal. [0027]The controlling of the additional information may include: controlling at least one of displaying of the additional information, playing of the additional information, and changing to previous additional information or next additional information based on the third input of the user through the mobile terminal. [0028]The method may further include: obtaining contents corresponding to the additional information displayed on the screen of the mobile terminal. [0029]According to an aspect of another exemplary embodiment, there is provided a method in which a display device provides information to a mobile terminal, the method including: selecting an object displayed on the display device by receiving a first input of a user through the mobile terminal; and transmitting additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal. [0030]The transmitting may include: extracting the additional information from contents corresponding to the selected object. [0031]The selecting of the object may include: receiving a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal; and moving the selection region according to the control signal. [0032]The selecting of the object may include: converting the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0033]The receiving may include: receiving the control signal for controlling the movement of the selection region from each of a plurality of mobile terminals. [0034]The method may further include: sensing at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0035]The selecting of the object may include: controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0036]The selecting of the object may include: transmitting thumbnail information of contents corresponding to the object to the mobile terminal. [0037]The transmitting of the additional information to the mobile terminal may include: transmitting link information of the additional information to the mobile terminal. [0038]The terminal may further include: receiving a request for transmission of contents corresponding to the selected object from the mobile terminal; and transmitting the contents corresponding to the selected object to the mobile terminal. [0039]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a communication unit which is configured to transmit a signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; an additional information obtaining unit which is configured to transmit a signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; a display which is configured to display the additional information received from the external display device; and a controller which is configured to control the communication unit, the additional information obtaining unit, and the display unit. [0040]The controller may convert the signal for selecting the object according to a control protocol of the external display device. [0041]The communication unit may transmit a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0042]The communication unit may transmit a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input. [0043]The display may display thumbnail information of contents corresponding to the object on a screen of the mobile terminal. [0044]The additional information obtaining unit may receive the additional information from the external display device. [0045]The communication unit may receive link information of the additional information from the external display device based on the second input, and wherein the additional information obtaining unit receives the additional information from a server based on the received link information. [0046]The controller may control the additional information displayed on the mobile terminal based on a third input of the user through the mobile terminal. [0047]The mobile terminal may further include: a contents obtaining unit which is configured to obtain content corresponding to the additional information displayed on the mobile terminal. [0048]According to an aspect of an exemplary embodiment, there is provided a display device including: a selection unit which is configured to select an object displayed on the display device based on a first input of a user through a mobile terminal; a communication unit which is configured to transmit additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal, and a controller which is configured to control the selection unit and the communication unit. [0049]The controller may extract the additional information from contents corresponding to the selected object. [0050]The selection unit may receive a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal and move the selection region according to the received control signal. [0051]The controller may convert the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0052]The display device may further include: a sensor which is configured to sense at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0053]The controller may control at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0054]The communication unit may transmit link information of the additional information to the mobile terminal. [0055]The communication unit may receive a request for transmission of contents corresponding to the selected object from the mobile terminal and transmit the contents corresponding to the selected object to the mobile terminal. [0056]According to an aspect of another exemplary embodiment, there is provided a method in which a mobile terminal generates a control signal, the method including: receiving a user input; determining an operation mode of the mobile terminal; and in response to determining the operation mode is a first mode, generating a first control signal for controlling an external display device based on the user input, and, in response to determining the operation mode is a second mode, generating a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0057]The contents may include contents corresponding to an object selected from the external display device or additional information corresponding to the object based on the first control signal. [0058]The user input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0059]The determining may include: determining the operation mode of the mobile terminal as the first mode in a case where the mobile terminal is in a vertical mode, and, determining the operation mode of the mobile terminal as the second mode in a case where the mobile terminal is in a horizontal mode. [0060]The determining may include: determining the operation mode of the mobile terminal based on information displayed on a screen of the mobile terminal. [0061]The determining may include: in response to determining the information displayed on the screen of the mobile terminal is thumbnail information of contents corresponding to the object displayed on the external display device or movement direction information of the mobile terminal, determining the operation mode of the mobile terminal as the first mode, and, in response to determining the information displayed on the screen of the mobile terminal is the contents corresponding to the object displayed on the external display device or additional information corresponding to the object, determining the operation mode of the mobile terminal as the second mode. [0062]The generating of the first control signal may include: converting the first control signal according to a control protocol of the external display device. [0063]The first mode may be a mode in which the object of the external display device is selected, and the second mode is a mode in which additional information corresponding to the selected object is displayed on the mobile terminal. [0064]The first control signal may include a signal for controlling a movement of a selection region for selecting the object of the external display device, and the second control signal may include a signal for controlling at least one of playing of the contents, editing of the contents, and transmission of the contents. [0065]The method may further include: receiving a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle; converting the operation mode from the first mode to the second mode based on the first rotational motion input; receiving a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle; and converting the operation mode from the second mode to the first mode based on the second rotational motion input. [0066]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a user input which is configured to receive a user input; an operation mode determining unit which is configured to determine an operation mode of the mobile terminal; and a controller which is configured, in response to the operation mode determining unit determining that the operation mode is a first mode, generate a first control signal for controlling an external display device based on the user input, and, in response to the operation mode determining unit determining that the operation mode is a second mode, generate a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0067]The user input may receive a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle and a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle, and wherein the controller converts the operation mode from the first mode to the second mode based on the first rotational motion input and the operation mode from the second mode to the first mode based on the second rotational motion input. [0068]According to an aspect of another exemplary embodiment, a method of displaying information of an external display device on a mobile terminal displays is provided. The method includes: receiving a user input into the mobile terminal about an object displayed on the external display device; transmitting a first signal to the external display device to select the object displayed on an external display device; receiving a second user input into the mobile terminal about additional information corresponding to the object displayed on the external display device; transmitting a second signal to the external display device to request additional information corresponding to the selected object; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0069]The transmitting the first signal may include converting the first signal to a control protocol of the external display device. [0070]The transmitting the first signal may include requesting control authorization from the external display device and receiving a control authorization acceptance message from the external display device. BRIEF DESCRIPTION OF THE DRAWINGS [0071]The above and other features and advantages will become more apparent by describing in detail exemplary embodiments with reference to the attached drawings in which: [0072]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment; [0073]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment; [0074]FIGS. 3A through 3C are views of screens on which a mobile terminal selects an object of an external display device, according to an exemplary embodiment; [0075]FIGS. 4A and 4B are views of screens on which a mobile terminal obtains additional information, according to an exemplary embodiment; [0076]FIG. 5 is a view of a screen on which contents are obtained, according to an exemplary embodiment; [0077]FIG. 6 is a view of a screen on which an object is displayed or reproduced, according to an exemplary embodiment; [0078]FIG. 7 is a flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0079]FIG. 8 is a detailed flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0080]FIG. 9 is a flowchart illustrating a method in which a display device senses an input of a mobile terminal and provides additional information, according to an exemplary embodiment; [0081]FIG. 10 is a flowchart illustrating a method in which a mobile terminal obtains additional information through a server, according to an exemplary embodiment; [0082]FIG. 11 is a flowchart illustrating a method in which a mobile terminal obtains contents, according to an exemplary embodiment; [0083]FIG. 12 is a flowchart illustrating a method in which a mobile terminal obtains contents through a server, according to an exemplary embodiment; [0084]FIG. 13 is a view of a screen on which each of a plurality of mobile terminals selects an object of a display device, according to an exemplary embodiment; [0085]FIG. 14 is a block diagram of a mobile terminal, according to an exemplary embodiment; [0086]FIG. 15 is a block diagram of a display device, according to an exemplary embodiment; [0087]FIG. 16 is a flowchart illustrating a method in which a display device provides information, according to an exemplary embodiment; and [0088]FIG. 17 is a flowchart illustrating a method in which a mobile terminal generates a control signal, according to an exemplary embodiment. DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS [0089]First, the terms used herein will be briefly described, and then the exemplary embodiments will be described in detail. [0090]Although the terms used herein are general terms that are widely used at present in consideration of the functions of the exemplary embodiments, they may vary according to the intention of one of ordinary skill in the art, a precedent, the appearance of new technology, or the like. In addition, in a particular case, the applicant may select the terms arbitrarily. In this case, the meanings of the terms will be described in detail in the detailed description of the exemplary embodiments. Thus, the terms used in the detailed description should not be only names of the terms but should be defined based on their meanings and contents in relation to the exemplary embodiments. [0091]When a unit “comprises” an element in the entire specification, the unit does not exclude another element but may further comprise another element unless the context clearly indicates otherwise. In addition, terms such as “ . . . unit”, “module”, and the like used herein indicate a unit for performing at least one function or operation and may be implemented by hardware or software or a combination thereof. [0092]Throughout the specification, an “object” refers to a target that may be selected by a user from a display device. Examples of the object include, but are not limited to, an icon, a link, a picture, a text, an index item, etc. [0093]In addition, “additional information” refers to information regarding contents corresponding to an object, and may have various forms according to types of contents. Examples of the additional information may include, but are not limited to, preview information, prelistening information, application information, user review information, advertisement image information, update information, newspaper article information, goods information, movie information, game information, album information, etc. [0094]In the present specification, “contents” may be displayed, reproduced, or stored in a mobile terminal, and may include, for example, still image contents (for example, a photo, a picture, etc.), text contents (for example, an electronic book (a poem and a novel), a letter, a business file, a web page, an electronic program guide (EPG), etc.), moving image contents (for example, a personal image, a movie, music video, a YouTube video, a TV program image, etc.), music contents (for example, music, a music performance, a radio broadcast, etc.), an application (a widget, a game, etc.) [0095]The exemplary embodiments will now be described more fully with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the inventive concept to those of ordinary skill in the art. For clarity, in the drawings, irrelevant portions with respect to the description are omitted, and similar reference numbers are added to similar portions throughout the entire specification. [0096]As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list. [0097]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment. [0098]Referring to FIG. 1, the information providing system according to an exemplary embodiment may include a mobile terminal 100 and an external display device 200. [0099]The mobile terminal 100 is a device that obtains contents from the outside and displays, reproduces, or stores the obtained contents. The mobile terminal 100 may be implemented in various ways. For example, the mobile terminal 100 described in the present specification may include a cellular phone, a smart phone, a laptop computer, a tablet personal computer (PC), an e-book terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, etc. [0100]The display device 200 is a device that may be of various types including a display panel. For example, the display device 200 described in the present specification may include a smart television (TV), an Internet protocol TV (IPTV), a digital TV (DTV), a computer, a laptop computer, an e-book terminal, a tablet PC, a digital broadcasting terminal, a consumer electronics (CE) device (for example, a refrigerator or an air conditioner having the display panel), etc. [0101]The display device 200 according to an exemplary embodiment may display an object list. The object list may include identification information regarding at least one piece of contents. Examples of the identification information may include a title of contents, an image and icon indicating contents, etc. [0102]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment. [0103]Referring to FIG. 2, the information providing system according to another exemplary embodiment may include the mobile terminal 100, the display apparatus 200, and a server 300. [0104]The mobile terminal 100 and the display apparatus 200 are the same as described with reference to FIG. 1, and thus descriptions thereof are omitted. [0105]The server 300 may communicate with the mobile terminal 100 or the display apparatus 200. According to an exemplary embodiment, the server 300 may receive a contents providing request from the mobile terminal 100 or the display device 200. In this case, the server 300 may provide contents to the mobile terminal 100 or the display device 200. The contents provided by the server 300 may be contents corresponding to an object selected by the display device 200 or additional information corresponding to the object. [0106]For example, in a case where the display device 200 selects an object relating to movie contents, the server 300 may provide the movie contents or preview video of the movie contents to the mobile terminal 100 or the display device 200. [0107]An example in which the mobile terminal 100 selects an object displayed on an external display device based on a user input and obtains and displays additional information corresponding to the selected object will now be described in brief with reference to FIGS. 3 through 6. [0108]FIGS. 3A through 3C are views of screens on which the mobile terminal 100 selects an object of the external display device 200, according to an exemplary embodiment. [0109]Referring to FIG. 3A, the display device 200 may display a plurality of objects indicating a plurality of pieces of contents. In this case, a user may use the mobile terminal 100 to select at least one of the plurality of objects displayed on the display device 200. [0110]For example, the user may move the mobile terminal 100 up and down and left and right (a first input) to select at least one of the plurality of objects displayed on the display device 200. In this regard, the display device 200 may display a location of a selection region (for example, a cursor and a pointer) corresponding to a movement of the mobile terminal 100 on a screen. [0111]Although a motion input is exemplarily used as the first input for selecting an object in FIG. 3A, the first input is not limited to the motion input. The first input may be a bending input, a key input, a voice input, and a touch input in addition to the motion input. [0112]According to an exemplary embodiment, the mobile terminal 100 may turn its screen off or may blacken its screen when selecting an object displayed on a screen of the display device 200 in such a way that user's eyes are not distracted. [0113]According to another exemplary embodiment, the mobile terminal 100 may display thumbnail information such as an icon, an image, a title, etc. of contents relating to an object in which the selection region is disposed or a movement direction of the mobile terminal 100 as an arrow, etc. on the display device 200. [0114]Referring to FIG. 3B, the mobile terminal 100 may display a selection window (or a graphical user interface (GUI)) for selecting a category (for example, drama, movie, sports, etc.) of contents. In this regard, the mobile terminal 100 may receive a selection of at least one category from the user. The mobile terminal 100 may transmit information regarding the selected category to the display device 200. In this case, the display device 200 may filter and display an object regarding contents corresponding to the category selected by the user. [0115]Referring to FIG. 3C, the mobile terminal 100 may output a map or a GUI indicating objects displayed on the display device 200 from among all the objects. [0116]FIGS. 4A and 4B are views of screens on which the mobile terminal 100 obtains additional information, according to an exemplary embodiment. [0117]Referring to FIG. 4A, a user may move the mobile terminal 100, select an object of the display device 200, then rotate the mobile terminal 100, and request additional information corresponding to the selected object from the display device 200. [0118]In this case, the display device 200 may transmit the additional information corresponding to the selected object or link information (for example, a uniform resource identifier (URI)) of the additional information to the mobile terminal 100. In this regard, the mobile terminal 100 may display the obtained additional information on a screen. [0119]For example, as shown in FIG. 4A, in a case where the user moves the mobile terminal 100, selects an object illustrating Shrek, and converts a vertical mode of the mobile terminal 100 into a horizontal mode, the mobile terminal 100 may obtain and display additional information (for example, Movie Title: Shrek, Review: ★★★★⋆, Representative Image, and Advertisement Moving Image) relating to Shrek. [0120]According to an exemplary embodiment, referring to FIG. 4B, if the user wishes to select a new object, the user may select the object of the display device 200 again by converting the horizontal mode of the mobile terminal 100 into the vertical mode. [0121]Although a motion input is that an object is selected and then is that the mobile terminal 100 receives and displays additional information corresponding to the object in FIGS. 3A through 4B as a rotation input, an exemplary embodiment is not limited thereto. That is, according to an exemplary embodiment, the mobile terminal 100 may receive and display additional information regarding contents relating to an object in which a selection region is disposed from the display device 200 while selecting an object of the display device 200 as the motion input. According to (String), 相关专利申请的交叉引用 [0001] 本申请是美国专利申请系列的延续申请。 2013 年 7 月 25 日提交的第 13/950,507 号,要求于 2012 年 7 月 25 日在韩国知识产权局提交的韩国专利申请第 10-2012-0081434 号的优先权,其公开内容并入 在此全文引用。 背景 [0002] 1. 领域 [0003] 示例性实施例涉及用于通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与所选对象相对应的附加信息来显示信息的方法和移动终端、用于提供信息的方法和显示设备 通过基于移动终端的输入选择对象并向移动终端提供关于所选对象的附加信息,以及用于通过基于操作将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端 移动终端的模式。 [0004] 2.相关技术的描述 [0005] 智能电视(Smart TV)是一种将电视与上网功能相结合,能够利用网络冲浪、视频点播(VOD)观看、社交网络服务(SNS)、游戏等多种功能的多功能电视。 并安装各种应用程序。 [0006] 智能电视的一个特点是用户和电视可以相互发送和接收信息。 这是智能电视与现有的仅单方面传输信息的电视的区别。 因此,智能电视也被称为互动电视。 [0007] 但是,用户通过标准的遥控器来使用智能电视的各种功能是非常不方便的。 特别地,当用户浏览或下载内容时,用户需要通过几个步骤来操作遥控器。 [0008] 因此,需要一种让用户容易控制智能电视的控制装置或系统。 概括 [0009] 示例性实施例提供一种用于显示信息的方法和移动终端,该方法和移动终端通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与选择的对象相对应的附加信息来进行。 [0010] 示例性实施例还提供了一种用于通过基于移动终端的输入选择对象并向移动终端提供关于所选对象的附加信息来提供信息的方法和显示设备。 [0011] 示例性实施例还提供一种用于通过基于移动终端的操作模式将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端。 [0012] 根据示例性实施例的一方面,提供了一种移动终端显示信息的方法,该方法包括:基于第一输入将用于选择在外部显示设备上显示的对象的第一信号发送到外部显示设备 用户通过移动终端; 基于用户通过移动终端的第二输入向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0013] 发送第一选择对象信号可以包括: 根据外部显示设备的控制协议对选择对象信号进行转换。 [0014] 用于选择对象的第一信号的发送可以包括:发送用于控制选择区域的移动的信号,用于选择显示在外部显示设备上的对象。 [0015]发送用于控制选择区域的移动的信号可以包括:发送用于控制选择区域的移动方向、选择区域的移动速度和屏幕上显示的对象的数量中的至少一项的信号。 基于第一输入的外部显示设备。 [0016] 发送用于选择对象的第一信号可以包括:在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0017] 缩略图信息可以包括与对象对应的内容的图像、内容的标题和内容的类型中的至少一个。 [0018] 发送用于选择对象的第一信号可以包括:根据第一输入在屏幕上显示移动终端的移动方向。 [0019] 第一输入和第二输入可以包括运动输入、键输入、触摸输入、弯曲输入和语音输入中的至少一个。 [0020] 第一输入可以包括用于在3D方向上移动移动终端的三维(3D)运动输入,其中第二输入包括用于将移动终端旋转超过预定角度的旋转运动输入。 [0021] 发送用于请求附加信息的第二信号可以包括:从显示设备接收附加信息。 [0022] 用于请求附加信息的第二信号的发送可以包括:基于第二输入从外部显示设备接收附加信息的链接信息; 基于接收到的链接信息从服务器接收附加信息。 [0023] 将用于选择对象的第一信号发送给显示设备可以包括: 向外部显示设备请求控制授权; 接收来自外部显示设备的控制授权接受消息。 [0024] 内容可以包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。 [0025] 附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、广告图像信息和专辑信息中的至少一种。 [0026] 该方法还可以包括:基于用户通过移动终端的第三输入来控制在移动终端的屏幕上显示的附加信息。 [0027] 对附加信息的控制可以包括:基于用户通过移动终端的第三输入,控制附加信息的显示、附加信息的播放以及改变为上一个附加信息或下一个附加信息中的至少一个。 [0028] 该方法还可以包括:获取与显示在移动终端的屏幕上的附加信息对应的内容。 [0029] 根据另一示例性实施例的一方面,提供了一种显示设备向移动终端提供信息的方法,该方法包括:通过通过移动终端接收用户的第一输入来选择显示在显示设备上的对象 ; 通过移动终端接收用户的第二输入,将与选择的对象对应的附加信息发送到移动终端。 [0030] 发送可以包括:从对应于所选对象的内容中提取附加信息。 [0031] 对象的选择可以包括:从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号; 根据控制信号移动选择区域。 [0032] 对象的选择可以包括:将接收到的第一输入转换为用于根据显示设备的控制协议控制选择区域的移动的控制信号。 [0033] 接收可以包括:从多个移动终端中的每一个接收用于控制选择区域的移动的控制信号。 [0034] 该方法还可以包括:感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0035] 对象的选择可以包括:基于用户通过移动终端的第一输入,控制选择区域的移动方向、选择区域的移动速度以及屏幕上显示的对象的数量中的至少一个。 . [0036] 对象的选择可以包括:将对象对应的内容的缩略图信息发送给移动终端。 [0037] 向移动终端发送附加信息可以包括:向移动终端发送附加信息的链接信息。 [0038] 终端还可以包括: 从移动终端接收与选择的对象对应的内容的传输请求; 将选择的对象对应的内容发送给移动终端。 [0039] 根据另一示例性实施例的一个方面,提供了一种移动终端,包括: 通信单元,被配置为基于用户的第一输入向外部显示设备发送用于选择在外部显示设备上显示的对象的信号。 通过移动终端; 附加信息获取单元,被配置为基于用户通过移动终端的第二输入向外部显示设备发送请求与选择的对象对应的附加信息的信号; 显示器,用于显示从外部显示设备接收到的附加信息; 控制器,用于控制通信单元、附加信息获取单元和显示单元。 [0040] 控制器可以根据外部显示设备的控制协议转换用于选择对象的信号。 [0041] 通信单元可以发送用于控制选择区域的移动的信号,该选择区域用于选择显示在外部显示装置上的对象。 [0042] 通信单元可以基于第一输入发送用于控制选择区域的移动方向、选择区域的移动速度和显示在外部显示设备的屏幕上的对象的数量中的至少一个的信号。 [0043] 显示器可以在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0044] 附加信息获取单元可以从外部显示设备接收附加信息。 [0045] 通信单元可以基于第二输入从外部显示设备接收附加信息的链接信息,并且其中附加信息获取单元基于接收到的链接信息从服务器接收附加信息。 [0046] 控制器可以基于用户通过移动终端的第三输入来控制在移动终端上显示的附加信息。 [0047] 所述移动终端还可以包括: 内容获取单元,用于获取所述移动终端显示的附加信息对应的内容。 [0048] 根据示例性实施例的一方面,提供了一种显示装置,包括: 选择单元,被配置为基于用户通过移动终端的第一输入选择显示在显示装置上的对象; 通信单元,被配置为通过接收用户通过移动终端的第二输入来将与选择的对象对应的附加信息发送到移动终端,以及控制器,被配置为控制选择单元和通信单元。 [0049] 控制器可以从对应于所选对象的内容中提取附加信息。 [0050]选择单元可以从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号,并且根据接收到的控制信号移动选择区域。 [0051] 控制器可以根据显示装置的控制协议将接收到的第一输入转换为用于控制选择区域的移动的控制信号。 [0052] 显示装置还可以包括:传感器,用于感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0053] 控制器可以基于用户通过移动终端的第一输入来控制选择区域的移动方向、选择区域的移动速度和显示在屏幕上的对象的数量中的至少一个。 [0054] 通信单元可以将附加信息的链接信息发送到移动终端。 [0055] 通信单元可以从移动终端接收对与所选对象相对应的内容的传输请求,并将与所选对象相对应的内容发送到移动终端。 [0056] 根据另一示例性实施例的一方面,提供了一种移动终端生成控制信号的方法,该方法包括:接收用户输入; 确定移动终端的操作模式; 并且响应于确定操作模式是第一模式,基于用户输入生成用于控制外部显示设备的第一控制信号,并且响应于确定操作模式是第二模式,生成用于控制外部显示设备的第二控制信号 基于用户输入控制在移动终端上显示的内容。 [0057] 内容可以包括与从外部显示设备选择的对象相对应的内容或与基于第一控制信号的对象相对应的附加信息。 [0058] 用户输入可以包括动作输入、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0059] 所述确定可以包括:在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第一模式,以及,在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第二模式。 终端处于水平模式。 [0060] 所述确定可以包括:根据所述移动终端的屏幕上显示的信息确定所述移动终端的操作模式。 [0061] 所述确定可以包括:响应于确定所述移动终端屏幕上显示的信息为所述外接显示设备上显示的对象对应的内容的缩略图信息或所述移动终端的移动方向信息,确定所述移动终端的操作模式。 终端作为第一模式,并且,响应于确定移动终端的屏幕上显示的信息是与外部显示设备上显示的对象对应的内容或与该对象对应的附加信息,确定移动终端的操作模式 终端作为第二种模式。 [0062] 第一控制信号的产生可以包括:根据外部显示设备的控制协议转换第一控制信号。 [0063] 第一模式可以是选择外部显示设备的对象的模式,第二模式是在移动终端上显示与选择的对象对应的附加信息的模式。 [0064] 第一控制信号可以包括用于控制用于选择外部显示设备的对象的选择区域的移动的信号,并且第二控制信号可以包括用于控制内容的播放、内容的编辑中的至少一个的信号。 ,以及内容的传输。 [0065]该方法还可以包括:接收用于将移动终端在第一方向上旋转预定角度的第一旋转运动输入; 基于第一旋转运动输入将操作模式从第一模式转换为第二模式; 接收用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入; 基于第二旋转运动输入,将操作模式从第二模式转换为第一模式。 [0066] 根据另一示例性实施例的一方面,提供了一种移动终端,包括: 用户输入,被配置为接收用户输入; 操作模式确定单元,用于确定移动终端的操作模式; 控制器,被配置为响应于操作模式确定单元确定操作模式是第一模式,基于用户输入产生用于控制外部显示装置的第一控制信号,并且响应于操作模式 确定单元确定操作模式是第二模式,基于用户输入产生用于控制在移动终端上显示的内容的第二控制信号。 [0067] 用户输入可以接收用于将移动终端沿第一方向旋转预定角度的第一旋转运动输入和用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入,并且其中控制器转换操作 基于第一旋转运动输入从第一模式到第二模式的模式和基于第二旋转运动输入从第二模式到第一模式的操作模式。 [0068] 根据另一示例性实施例的一方面,提供了一种在移动终端显示器上显示外部显示设备的信息的方法。 该方法包括:接收到移动终端的关于显示在外部显示设备上的对象的用户输入; 传送第一信号至外接显示装置以选择外接显示装置上显示的对象; 接收到移动终端的关于与显示在外部显示设备上的对象对应的附加信息的第二用户输入; 向外部显示设备发送第二信号以请求对应于所选对象的附加信息; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0069] 发送第一信号可以包括将第一信号转换为外部显示设备的控制协议。 [0070] 发送第一信号可以包括从外部显示设备请求控制授权和从外部显示设备接收控制授权接受消息。 附图的简要说明 [0071] 通过参考附图详细描述示例性实施例,上述和其他特征和优点将变得更加明显,其中: [0072] 如图。 附图说明图1是用于说明实施方式的信息提供系统的图。 [0073] 如图。 图2是用于说明另一实施方式的信息提供系统的图。 [0074] 图 图3A至图3C是根据示例性实施例的移动终端选择外部显示设备的对象的屏幕的视图; [0075] 图 图4A和4B是根据示例性实施例的移动终端在其上获得附加信息的屏幕的视图; [0076] 如图。 图5是根据示例性实施例的获取内容的屏幕的视图; [0077] 如图。 图6是根据示例性实施例的显示或再现对象的屏幕的视图; [0078] 如图。 图7是示出根据示例性实施例的移动终端显示信息的方法的流程图; [0079] 如图。 图8是示出根据示例性实施例的移动终端显示信息的方法的详细流程图; [0080]如图。 图9是示出根据示例性实施例的显示设备感测移动终端的输入并提供附加信息的方法的流程图; [0081] 如图。 图10是示出根据示例性实施例的移动终端通过服务器获取附加信息的方法的流程图; [0082] 如图。 图11是示出根据示例性实施例的移动终端获取内容的方法的流程图; [0083] 如图。 图12是示出根据示例性实施例的移动终端通过服务器获取内容的方法的流程图; [0084] 如图。 图13是根据示例性实施例的多个移动终端中的每一个选择显示装置的对象的屏幕的视图; [0085] 如图。 图14是根据示例性实施例的移动终端的框图; [0086] 如图。 图15是根据示例性实施例的显示装置的框图; [0087] 如图。 图16是示出根据示例性实施例的显示装置提供信息的方法的流程图; 和 [0088] 如图。 图17是示出根据示例性实施例的移动终端生成控制信号的方法的流程图。 示例性实施例的详细说明 [0089] 首先,将简要描述这里使用的术语,然后将详细描述示例性实施例。 [0090] 尽管这里使用的术语是考虑到示例性实施例的功能而目前广泛使用的通用术语,但是它们可以根据本领域普通技术人员的意图、先例、新技术的出现或 类似。 此外,在特定情况下,申请人可以任意选择术语。 在这种情况下,术语的含义将在示例性实施例的详细描述中详细描述。 因此,在详细描述中使用的术语不应仅仅是术语的名称,而应基于与示例性实施例相关的含义和内容来定义。 [0091] 当一个单元“包括”整个说明书中的一个元素时,该单元不排除另一个元素,而是可以进一步包括另一个元素,除非上下文另有明确说明。 此外,诸如“. . . 这里使用的“单元”、“模块”等表示用于执行至少一个功能或操作的单元,可以通过硬件或软件或其组合来实现。 [0092] 在整个说明书中,“对象”指的是可以由用户从显示设备中选择的目标。 对象的示例包括但不限于图标、链接、图片、文本、索引项等。 [0093] 此外,“附加信息”指的是关于与对象对应的内容的信息,并且可以根据内容的类型而具有各种形式。 附加信息的示例可以包括但不限于预览信息、试听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息、 等等 [0094] 在本说明书中,“内容”可以在移动终端中显示、再现或存储,并且可以包括例如静止图像内容(例如照片、图片等)、文本内容(例如 、电子书(一首诗、一部小说)、一封信、一份商务文件、一个网页、一个电子节目指南(EPG)等)、运动图像内容(例如,个人图像、电影、音乐 视频、YouTube 视频、电视节目图像等)、音乐内容(例如,音乐、音乐表演、无线电广播等)、应用程序(小部件、游戏等) [0095]现在将参照附图更全面地描述示例性实施例。 然而,示例性实施例可以以许多不同的形式体现,并且不应被解释为限于本文所阐述的实施例; 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明构思充分传达给本领域普通技术人员。 为了清楚起见,在附图中,省略了与描述无关的部分,并且在整个说明书中类似的附图标记被添加到类似的部分。 [0096] 如本文所用,术语“和/或”包括一个或多个相关列出的项目的任何和所有组合。 诸如“至少一个”之类的表达式在元素列表之前时,会修改整个元素列表,而不是修改列表中的各个元素。 [0097] 如图。 附图说明图1是用于说明根据示例性实施例的信息提供系统的视图。 [0098] 参考图。 参照图1,根据示例性实施例的信息提供系统可以包括移动终端 100 和一个外部显示设备 200 . [0099] 移动终端 100 是从外部获取内容并显示、再现或存储获取的内容的设备。 移动终端 100 可以以各种方式实现。 例如,移动终端 100 本说明书中描述的可以包括蜂窝电话、智能电话、膝上型计算机、平板个人计算机(PC)、电子书终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、 导航系统等 [0100] 显示装置 200 是一种可以是各种类型的设备,包括显示面板。 例如,显示设备 200 本说明书中描述的可以包括智能电视(TV)、互联网协议电视(IPTV)、数字电视(DTV)、计算机、膝上型计算机、电子书终端、平板电脑、数字广播终端 ,消费电子(CE)设备(例如,具有显示面板的冰箱或空调)等。 [0101] 显示装置 200 根据示例性实施例,可以显示对象列表。 对象列表可以包括关于至少一个内容的标识信息。 标识信息的示例可以包括内容的标题、指示内容的图像和图标等。 [0102] 如图。 图2是用于说明根据另一示例性实施例的信息提供系统的视图。 [0103] 参考图。 参照图2,根据另一示例性实施例的信息提供系统可以包括移动终端 100 , 显示装置 200 , 和一个服务器 300 . [0104] 移动终端 100 和显示装置 200 与参考图1描述的相同。 与图1相同,因此省略其说明。 [0105] 服务器 300 可与移动终端通信 100 或显示设备 200 . 根据示例性实施例,服务器 300 可以从移动终端接收内容提供请求 100 或显示设备 200 . 在这种情况下,服务器 300 可以向移动终端提供内容 100 或显示设备 200 . 服务器提供的内容 300 可以是显示设备选择的对象对应的内容 200 或与对象对应的附加信息。 [0106] 例如,在显示设备 200 选择与电影内容相关的对象,服务器 300 可向移动终端提供电影内容或电影内容的预览视频 100 或显示设备 200 . [0107] 以移动终端为例 100 现在将参考图1至图3简要描述基于用户输入选择在外部显示设备上显示的对象并获得并显示与所选择的对象相对应的附加信息。 3 到 6。 [0108] 图 图3A到3C是移动终端在其上的屏幕的视图 100 选择外部显示设备的对象 200 ,根据示例性实施例。 [0109] 参考图。 3A、显示装置 200 可以显示指示多条内容的多个对象。 在这种情况下,用户可以使用移动终端 100 选择显示在显示设备上的多个对象中的至少一个 200 . [0110] 例如,用户可以移动移动终端 100 上下左右(第一输入)以选择显示设备上显示的多个对象中的至少一个 200 . 对此,显示设备 200 可以显示与移动终端的移动相对应的选择区域(例如,光标和指针)的位置 100 在屏幕上。 [0111] 尽管在图1中示例性地使用运动输入作为用于选择对象的第一输入。 如图3A所示,第一输入不限于动作输入。 除了动作输入之外,第一输入可以是弯曲输入、键输入、语音输入和触摸输入。 [0112] 根据示例性实施例,移动终端 100 选择显示设备屏幕上显示的对象时,可能会关闭屏幕或将屏幕变黑 200 这样用户的眼睛就不会分心。 [0113] 根据另一示例性实施例,移动终端 100 可以显示与设置选择区域的对象或移动终端的移动方向有关的内容的缩略图信息,例如图标、图像、标题等 100 显示设备上的箭头等 200 . [0114] 参考图。 3B、移动终端 100 可以显示用于选择内容类别(例如,戏剧、电影、体育等)的选择窗口(或图形用户界面(GUI))。 对此,移动端 100 可以接收来自用户的至少一个类别的选择。 移动终端 100 可以将关于所选类别的信息发送到显示设备 200 . 在这种情况下,显示设备 200 可以过滤和显示关于与用户选择的类别相对应的内容的对象。 [0115] 参考图。 3C、移动终端 100 可以输出地图或图形用户界面指示显示设备上显示的对象 200 从所有对象中。 [0116] 图 图4A和4B是移动终端在其上的屏幕的视图 100 根据示例性实施例,获取附加信息。 [0117] 参考图。 参照图4A,用户可以移动移动终端 100 , 选择显示设备的对象 200 ,然后旋转移动端 100 , 并向显示设备请求与所选对象对应的附加信息 200 . [0118] 在这种情况下,显示设备 200 可以将与选择的对象相对应的附加信息或附加信息的链接信息(例如,统一资源标识符(URI))发送到移动终端 100 . 对此,移动端 100 可以在屏幕上显示获得的附加信息。 [0119] 例如,如图所示。 参照图4A,在用户移动移动终端的情况下 100 ,选择描绘史莱克的对象,并转换移动终端的垂直模式 100 进入横屏模式,移动端 100 可能会获取和显示与史莱克有关的附加信息(例如,电影名称:史莱克、评论:★★★★⋆、代表图像和广告动态图像)。 [0120] 根据示例性实施例,参考图1。 参照图4B,如果用户希望选择新对象,则用户可以选择显示设备的对象 200 再次通过转换移动端的水平模式 100 进入垂直模式。 [0121] 虽然动作输入是选择了一个对象然后是移动终端 100接收并显示对应于图1和2中的对象的附加信息。 尽管将图3A到4B作为旋转输入,但示例性实施例不限于此。 也就是说,根据示例性实施例,移动终端 100 可以从显示装置接收和显示关于与其中设置了选择区域的对象有关的内容的附加信息 200 在选择显示设备的对象时 200 作为运动输入。 根据示例性实施例,移动终端在其上的通信网络 100 将用于选择对象的信号发送到显示设备 200 以及移动终端所通过的通信网络 100 从显示设备接收附加信息 200 可能彼此不同。 例如,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 通过蓝牙通信,然后从显示设备接收与所选对象对应的附加信息 200 通过 Wi-Fi 通信。 [0122] 如图。 图5是根据示例性实施例的在其上获得内容的屏幕的视图。 [0123] 用户可以确认关于与从显示设备获得的对象相对应的内容的附加信息 200 然后向显示设备请求相应的内容 200 或服务器 300 . 例如,用户可以通过显示设备确认关于电影史瑞克的附加信息(用户评论等) 200 然后从显示设备请求和下载电影内容史莱克 200 或服务器 300 . [0124] 如图。 图6是根据示例性实施例的显示或再现对象的屏幕的视图。 [0125] 参考图。 参照图6,根据示例性实施例,移动终端 100 可以显示或再现从显示设备下载的内容 200 或服务器 300 . [0126] 根据另一示例性实施例,移动终端 100 可以通过流式传输内容来接收和再现内容。 [0127] 一种移动终端的方法 100 现在将在下面详细描述基于用户输入检索和/或显示信息。 [0128] 根据示例性实施例的显示信息的方法可以通过预定应用来实现。 也就是移动终端 100 可以驱动用于提供根据示例性实施例的显示信息的方法的应用。 移动终端 100 可以基于用户输入或自动驱动应用程序。 [0129] 移动端驱动的应用 100 可以是仅用于执行控制显示设备的过程的应用程序 200 或提供各种服务。 例如,该应用程序可以是用于提供远程控制服务、信使服务、社交网络服务(SNS)、多媒体内容播放服务等的应用程序。 [0130] 假设移动终端使用的方法 100 显示参考图1和2描述的信息。 可以通过预定的应用来执行图7至图12的说明。 [0131] 如图。 图7是示出移动终端的方法的流程图 100 根据示例性实施例,显示信息。 参考图。 7、移动终端的方法 100 根据示例性实施例的显示信息包括由移动终端顺序执行的操作 100 图。 稍后将描述的图14。 因此,虽然以下省略,但以上关于移动终端的描述 100 图。 图14的方法也将适用于图14的方法。 7 其中移动终端 100 显示信息。 [0132] 在操作 S 710 , 移动端 100 可以发送用于选择外部显示设备的对象的信号 200 到显示设备 200 基于第一输入。 在接收到第一输入的情况下,移动终端100 可以产生用于选择显示设备的对象的信号 200 基于第一个输入。 [0133] 根据示例性实施例,移动终端 100 可以根据显示设备的控制协议转换用于选择对象的信号 200 . 也就是移动终端 100 可以获得显示设备的标识信息(例如设备类型、设备ID、设备序列号等) 200 并将接收到的用户的第一输入转换为显示设备可识别的控制命令 200 基于显示设备的识别信息 200 . [0134] 根据示例性实施例的用于选择对象的信号可以包括用于控制选择对象的选择区域的移动的信号。 也就是说,在移动终端 100 检测到超过阈值的移动,移动终端 100 可以产生用于控制显示装置的选择区域的移动的信号 200 基于有关检测到的运动的信息。 [0135] 例如,在陀螺仪传感器值小于阈值的情况下,移动终端 100 可以确定移动终端 100 不移动,可以不产生用于控制选择区域移动的信号,并且,每次陀螺传感器值改变预定值(例如,10度)时,可以产生用于将选择区域移动一个空间的控制信号 /sec) 大于阈值。 [0136] 根据另一示例性实施例的用于选择对象的信号可以包括信息(例如,移动终端的移动位置信息) 100 ) 关于第一个输入。 也就是移动终端 100 可以直接产生控制选择区域移动的信号并将其传输到显示装置 200 或者可以发送信息(例如,移动终端的移动位置信息) 100 ) 关于显示设备的第一个输入 200 . [0137] 在信息(例如,移动终端的移动位置信息 100 ) 关于第一个输入被传输到显示设备 200 , 显示设备 200 可以根据显示设备的控制协议将第一输入转换为用于控制选择区域的移动的信号 200 . [0138] 例如,在接收到小于阈值的陀螺传感器值的情况下,移动终端 100 可以确定移动终端 100 不移动并且可能不产生用于控制选择区域移动的信号。 移动终端 100 每当接收到大于阈值的预定陀螺传感器值(例如,10度/秒)时,可以生成用于将选择区域移动一个空间的控制信号。 [0139] 在生成控制信号之前,移动终端 100 可以通过身份验证来授权显示设备 200 通过显示设备 200 . 例如,移动终端 100 可以向显示设备请求控制授权 200 . 对此,移动端 100 可以通过发送移动终端的识别信息来请求控制授权 100 到显示设备 200 . 移动终端的识别信息 100 是识别移动终端的唯一信息 100 ,并且可能包括例如设备 ID、唯一序列号、媒体访问控制 (MAC) 地址、国际移动设备身份 (IMEI) 等。 [0140] 显示装置 200 可认证移动终端的控制权限 100 基于移动终端的识别信息 100 . 在认证成功的情况下,显示设备 200 可以向移动终端发送控制授权接受消息100 . 在这种情况下,移动终端 100 可以控制显示设备 200 . [0141] 在发送控制授权接受消息时,显示设备 200 可以注册移动终端的识别信息 100 在一个存储单元中。 因此,虽然移动终端 100 未经显示设备认证 200 不再是移动端 100 可以控制显示设备 200 . [0142] 在操作 S 720 , 移动端 100 可以获得与从显示设备中选择的对象相对应的附加信息 200 基于第二个输入。 即,在接收到第二输入的情况下,移动终端 100 可以从显示设备请求与基于第一输入选择的对象相对应的附加信息 200 . 在这种情况下,移动终端 100 可以从显示设备获取附加信息 200 或通过服务器 300 . 这将参照图3详细描述。 8 以后。 [0143] 在操作 S 730 , 移动端 100 可以在屏幕上显示获得的附加信息。 移动终端 100 可以在将附加信息存储在存储单元中之后通过下载来显示附加信息,或者可以通过流式传输附加信息来显示附加信息。 [0144] 根据示例性实施例的附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息等。 [0145] 这将参照图3更详细地描述。 8 以后。 如图。 图8是示出移动终端的方法的详细流程图 100 根据示例性实施例,显示信息。 [0146] 在操作 S 810 , 移动端 100 可以接收第一输入。 移动端的第一个输入 100 可以是动作输入(例如3D动作输入、旋转动作输入等)、按键输入、触摸输入、弯曲输入、语音输入、多模态输入等。即用户 可以移动移动终端 100 上(+Y 轴方向)和下(-Y 轴方向)和左(-X 轴方向)和右(+X 轴方向),触摸(轻拂、拖动、点击、平移等)屏幕(或 GUI显示在屏幕上)的移动终端 100 上下左右,操作移动(方向)键,弯曲移动终端预定区域(左上、右上、左下、右下) 100 ,或输入包括移动命令的语音。 在操作 S 820 , 移动端 100 可以基于第一输入生成用于选择对象的信号。 例如,在第一输入为移动终端的动作输入的情况下 100 上下左右移动,移动端 100 可以根据移动终端的移动生成用于控制选择区域的移动的信号 100 . 即,在用户移动移动终端的情况下 100 向左(-X轴方向)移动预定值以上,移动终端 100 可以产生用于将选择区域向左移动一格的控制信号。 [0147] 在第一输入为上下左右触摸触摸屏的触摸输入的情况下,移动终端 100 可以根据用户的触摸手势产生用于控制选择区域的移动的信号。 例如,在用户使用手指或电子笔从左向右轻拂触摸屏超过预定距离的情况下,移动终端 100 可以产生用于将选择信号向右移动一个空间的控制信号。 [0148] 在第一输入是操作移动(方向)键的键输入的情况下,移动终端 100可以产生用于将选择区域移动到与方向键对应的位置的控制信号。 [0149] 在第一输入是移动终端的预定区域的弯曲输入的情况下 100 , 可以由柔性显示器形成, 弯曲, 移动终端 100 可以产生用于在对应于弯曲运动的方向上移动选择区域的控制信号。 “弯曲”可以是移动终端的弯曲或变形 100 通过外力。 “弯曲运动”可以是移动终端的弯曲运动或变形 100 . [0150] 例如,在用户弯曲移动终端顶部的情况下 100 , 移动端 100 在用户弯曲移动终端的左侧区域的情况下,可以生成用于将选择区域向上移动一格的控制信号 100 , 移动端 100 可以生成用于将选择区域向左移动一个空间的控制信号,并且在用户弯曲整个移动终端的情况下 100 , 移动端 100 可以产生用于选择包括当前选择区域的对象的控制信号。 [0151] 在第一输入为语音输入的情况下,移动终端 100 可以生成用于将选择区域移动到与语音输入对应的位置的控制信号。 例如,在用户说“向左移动三个空格”的情况下,移动终端 100 可以生成用于将选择区域向左移动三个空间的控制信号。 [0152] 在操作 S 830 , 移动端 100 可以将基于第一输入生成的用于选择对象的信号发送到显示装置 200 . 移动终端 100 根据示例性实施例,可以将用于选择对象的信号发送到显示装置 200 直接或通过服务器 300 . 移动终端 100 根据示例性实施例,还可以使用各种通信方法发送用于选择对象的信号。 [0153] 例如,在移动终端 100 和显示设备 200 在预定范围(局域距离)内,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 直接通过短距离无线通信(蓝牙、Zigbee、近场通信(NFC)、Wi-Fi直连(WFD)、超宽带(UWB)、红外数据协会(IrDA)等)。 移动终端 100 也可以通过移动通信网络(例如,2G/3G/4G、Wibro等)或无线局域网(LAN)(Wi-Fi:ad-hoc模式,基础设施模式)传输用于选择对象的信号 )。 [0154] 在操作 S 840 , 显示设备 200 可以根据移动终端的第一输入移动选择区域 100 . 例如,在第一输入为移动终端的动作输入的情况下 100 向左移动(-X 轴方向),显示设备 200 将选择区域向左移动。 [0155] 根据示例性实施例,显示装置 200 可以基于第一输入控制选择区域的移动速度。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 以高于阈值速度的速度向右移动,显示设备 200 可以将选择区域向右移动几个空格(例如,每3个空格),并且,如果用户移动移动终端 100 以低于阈值速度的速度向左移动,显示设备 200 可以将选择区域向左移动一格。 [0156] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户拖动移动终端的触摸屏 100 在高于阈值速度的速度下,显示设备 200 可以将选择区域移动几个空格,并且,如果用户拖动移动终端的触摸屏 100在低于阈值速度的速度下,显示设备 200 可以将选择区域移动一个空格。 [0157] 根据示例性实施例,在第一输入是弯曲输入的情况下,显示装置 200 可以基于用户弯曲移动终端的预定区域的次数来控制选择区域的移动速度 100 . 例如,在用户弯曲移动终端顶部的情况下 100 三、显示装置 200 可以将选择区域向上移动三个空格,并且在用户弯曲移动终端的右侧区域的情况下 100 两次,显示设备 200 可以将选择区域向右移动两个空格。 此外,显示装置的例子多种多样 200 根据第一个输入移动选择区域。 [0158] 根据示例性实施例,显示装置 200 可以基于第一输入调整屏幕上显示的对象的数量。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 在正面方向(+Z轴方向)上,显示装置 200 可能会减少屏幕上显示的对象数量,并且,如果用户移动移动终端 100 在后方(-Z轴方向),显示装置 200 可能会增加屏幕上显示的对象数量。 [0159] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户多点触摸移动终端的触摸屏上的至少两个点 100 并将两个点拖离对方,显示设备 200 可能会减少屏幕上显示的对象数量,并且如果用户将两个点拖得更近,则显示设备 200 可能会增加屏幕上显示的对象数量。 [0160] 根据示例性实施例,在第一输入是弯曲输入的情况下,如果用户弯曲移动终端的中心部分 100 为凸出,显示装置 200 可以减少屏幕上显示的对象的数量,并且,如果用户弯曲移动终端的中心部分 100 是凹的,显示装置 200 可能会增加屏幕上显示的对象数量。 [0161] 此外,显示装置的例子多种多样 200 根据第一个输入调整屏幕上显示的对象数量。 [0162] 根据示例性实施例,虽然显示装置 200 根据移动终端的第一输入选择对象 100 , 移动端 100 可以从显示装置接收并显示与其中设置有选择区域的对象相对应的内容的缩略图信息 200 . 例如,移动终端 100 可以显示与设置有选择区域的对象相对应的内容的图像、图标、标题、内容类型等。 移动终端可以显示与移动终端的当前位置相对应的选择区域的位置 100 以及选择区域在显示装置的整个屏幕上的移动方向 200 . [0163] 根据另一示例性实施例,移动终端 100 可以关闭其屏幕或使其屏幕变黑,以使用户的眼睛不会从显示设备的屏幕上分心 200 在其上选择对象。 [0164] 在操作 S 850 , 显示设备 200 选择对象。 根据示例性实施例,显示装置 200 可以基于第一输入选择其中布置了移动的选择区域的对象。 [0165] 根据示例性实施例,显示装置 200 可以识别(强调)其中设置选择区域的对象。 例如,显示设备 200可以将设置选择区域的对象的边框表示为框,也可以将设置选择区域的对象相对于其他对象增大尺寸,或者制作闪烁等动画效果。 [0166] 在操作 S 860 , 移动端 100 可以接收第二个输入。 根据示例性实施例的第二输入可以是用于获得附加信息的用户输入。 移动端二次输入 100 根据示例性实施例,可以包括动作输入、键输入、弯曲输入和语音输入中的至少一种。 例如,用户可以旋转移动终端 100 以预定角度弯曲移动终端的中心部分 100 , 按下移动端的一个选择键 100 ,在请求附加信息的屏幕上触摸(轻敲)GUI,或输入请求附加信息的语音。 第二输入不限于此,并且可以存在多种示例。 [0167] 在操作 S 870 , 移动端 100 可以向显示设备请求与所选对象对应的附加信息 200 . 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 直接或通过服务器 300 . [0168] 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 通过短距离无线通信(蓝牙、Zigbee、NFC、WFD、UWB、IrDA等)、移动通信(例如2G/3G/4G、Wibro等)或无线局域网(Wi -Fi:ad-hoc 模式,基础设施模式)。 [0169] 在操作 S 880 , 显示设备 200 可以将与选择的对象对应的附加信息发送到移动终端 100 . 例如,在选择与电影内容相关的对象的情况下,显示设备 200 可将与电影内容有关的附加信息(代表场景、预览视频、制作信息、概要信息、演员、导演信息、用户评论信息等)传输到移动终端 100 . [0170] 在选择与应用相关的对象的情况下,显示设备 200 可以向移动终端发送关于应用程序的附加信息(例如,应用程序的说明、应用程序审查信息、应用程序更新信息等) 100 . [0171] 根据示例性实施例,在选择与照片有关的对象的情况下,显示装置 200 可以将包括照片的元数据(例如,拍摄地点、拍摄时间等)、与照片中的人物相关的信息(例如,报纸文章、外观电影、代表性音乐等)等附加信息传输到 移动终端 100 . [0172] 根据示例性实施例,在选择与音乐有关的对象的情况下,显示装置 200 可以向移动终端发送关于音乐的附加信息,包括专辑信息、音乐视频、预告视频、预听信息、报纸文章、歌手信息等 100 . [0173] 根据示例性实施例,在选择与网站有关的对象的情况下,显示装置 200 可能会向移动终端发送附加信息,包括有关网站的预览信息 100 . [0174] 根据示例性实施例,在选择与EPG有关的对象的情况下,显示装置 200 可以向移动终端发送关于EPG的附加信息,包括广播节目概要、每集的预览信息等 100 . 在选择与购物项目有关的对象的情况下,显示装置 200可以向移动终端发送关于购物项目的附加信息,包括商品信息、订单信息、推荐信息等 100 . [0175] 根据示例性实施例,显示装置 200 可以将先前存储在存储单元中的附加信息发送到移动终端 100 . 如果附加信息的链接信息仅存储在存储单元中,则显示设备 200 可能会收到来自服务器的附加信息 300 并将接收到的附加信息发送给移动终端 100 . 显示装置 200 可以在搜索引擎或网站中搜索与对象相关的附加信息,并将找到的附加信息提供给移动终端 100 . [0176] 在操作 S 890 , 移动端 100 可以显示获得的附加信息。 移动终端 100 可以基于用户输入控制显示的附加信息。 现在将参考图3详细描述这一点。 9. [0177] 如上所述,根据示例性实施例,用户可以搜索和/或选择与显示在外部显示设备上的内容有关的对象 200 通过手机端的简单输入 100 并确认与所选对象有关的附加信息,以确定是否接收相应的内容。 [0178] 如图。 图9是示出显示装置的方法的流程图 200 感应移动终端的输入 100 并且根据示例性实施例提供附加信息。 附图之间的冗余描述。 8和9在此省略。 [0179] 参考图。 参照图9,根据示例性实施例,移动终端 100 可以在操作 S 中接收第一输入 910 和显示设备 200 可感应移动终端的输入 100 . [0180] 例如,在操作 S 920 , 显示设备 200 可以感测移动终端的第一输入 100 用于选择对象。 操作 S 930 通过 S 960 图。 9 对应于操作 S 810 通过 S 860 图。 与图8相同,因此这里将省略对其的重复描述。 在操作 S 970 , 显示设备 200 可以感测移动终端的第二输入 100 用于获取与所选对象对应的附加信息。 操作 S 980 通过 S 995 图。 9 对应于操作 S 870 通过 S 890 图。 与图8相同,因此这里将省略对其的重复描述。 [0181] 移动终端的第一输入和第二输入 100 可以包括运动输入(例如,3D运动输入、旋转运动输入等)、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0182] 根据示例性实施例,在第一输入和第二输入是动作输入的情况下,显示装置 200 可以感知移动终端的动作 100 通过相机。 例如,在用户移动移动终端的情况下 100 上下左右或旋转移动终端 100 , 显示设备 200 可感应移动终端的上下左右运动 100 或者移动终端的旋转 100 . [0183] 根据示例性实施例,在第一输入和第二输入是弯曲输入的情况下,显示装置 200 可以感测移动终端的弯曲运动 100 通过相机。 例如,显示设备 200 可以感测移动终端的弯曲位置(坐标值) 100 、弯曲方向、弯曲角度、弯曲速度、弯曲频率、弯曲运动发生时间、弯曲运动持续时间段等。 [0184] 根据示例性实施例,在第一输入和第二输入是触摸输入的情况下,显示装置 200可以通过摄像头感知用户的触摸手势。 [0185] 根据示例性实施例,在第一输入和第二输入是语音输入的情况下,显示装置 200 可以通过麦克风感测用户的语音输入。 [0186] 也就是说,根据示例性实施例,显示装置 200 可以感测第一输入或第二输入以验证从移动终端接收的用于选择对象的信号 100 或用于请求对应于对象的附加信息的信号。 例如,在显示设备 200 感测移动终端的动作输入 100 向右(+X轴方向)移动并从移动终端、显示设备接收用于将选择区域向左移动一格的控制信号 200 可以向移动终端请求控制(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.953 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.954 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), CN103577138A(String), 1047532(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.957 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), CN103577138B(String), 1047533(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), EP2690880A1(String), 1047534(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), IN1206DELNP2015A(String), 1047535(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), JP2014027659A(String), 1047536(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.962 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), JP6335448B2(String), 1047537(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.963 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), KR101971624B1(String), 1047538(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), KR1020140019078A(String), 1047539(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), TW201412097A(String), 1047540(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), TWI574557B(String), 1047541(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), US20140028921A1(String), 1047542(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), US20170118436A1(String), 1047543(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), US9549143B2(String), 1047544(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270705(Integer), WO2014017759A1(String), 1047545(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.974 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.974 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.974 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9549143B2(String), US9549143B2(String), 1484582400(Integer), 270705(Integer), 185029(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185031(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185031(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185031(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.991 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185031(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:04.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.001 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185031(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.022 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.023 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20150067572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method for setting virtual keyboard of mobile terminal(String), 移动终端及移动终端虚拟键盘设置方法(String), US20150067572A1(String), Disclosed are a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. The method includes: setting a virtual keyboard on a corner of a display screen of a mobile terminal and displaying same in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; and after receiving expression information input through the key display area, displaying the expression information in the symbol display area. The disclosure displays a virtual keyboard on a display screen in the form of a sector area so that a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience.(String), 本发明公开了一种移动终端及移动终端虚拟键盘的设置方法。 该方法包括:将虚拟键盘设置在移动终端显示屏的一角,并以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为 扇形区为重点展示区; 接收到通过按键显示区输入的表情信息后,在符号显示区显示表情信息。 本发明将虚拟键盘以扇形区域的形式显示在显示屏上,方便用户单手在移动终端上输入信息,大大提高了用户的操作效率,改善了用户体验。(String), US14/389046(String), 1340035200(Integer), US20150067572A1(String), 1425484800(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 5(Integer), US20100131900A1 | US20100241985A1 | US20120062465A1 | US20120075194A1 | US20130234949A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185032(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.044 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\61f3e3bd426549ae8c43d3d643750150.png(String), 185032(Integer), 61f3e3bd426549ae8c43d3d643750150.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.053 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.054 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.055 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for setting virtual keyboard of mobile terminal(String), 移动终端及移动终端虚拟键盘设置方法(String), US20150067572A1(String), Disclosed are a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. The method includes: setting a virtual keyboard on a corner of a display screen of a mobile terminal and displaying same in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; and after receiving expression information input through the key display area, displaying the expression information in the symbol display area. The disclosure displays a virtual keyboard on a display screen in the form of a sector area so that a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience.(String), 本发明公开了一种移动终端及移动终端虚拟键盘的设置方法。 该方法包括:将虚拟键盘设置在移动终端显示屏的一角,并以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为 扇形区为重点展示区; 接收到通过按键显示区输入的表情信息后,在符号显示区显示表情信息。 本发明将虚拟键盘以扇形区域的形式显示在显示屏上,方便用户单手在移动终端上输入信息,大大提高了用户的操作效率,改善了用户体验。(String), US14/389046(String), 1340035200(Integer), US20150067572A1(String), 1425484800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 5(Integer), US20100131900A1 | US20100241985A1 | US20120062465A1 | US20120075194A1 | US20130234949A1(String), \20230420\61f3e3bd426549ae8c43d3d643750150.png(String), 16(Integer), 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.065 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 1. A method for setting a virtual keyboard of a mobile terminal, comprising:setting a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, wherein an arc-shaped area of the sector area is a symbol display area, and a remaining area of the sector area is a key display area;after receiving expression information which is input through the key display area, displaying the expression information in the symbol display area.(String), 1.根据权利要求2所述的移动终端虚拟键盘的设置方法,还包括:在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角之后,设置虚拟键盘的扇形区域在移动终端显示屏上的显示大小。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 2. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after inputting the expression information through the key display area, hiding the virtual keyboard when it is detected that the display screen is touched by a preset first operational motion in the key display area.(String), 12.根据权利要求3所述的移动终端虚拟键盘的设置方法,还包括:在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角之后,设置虚拟键盘的扇形区域在移动终端显示屏上的显示大小。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 3. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after inputting the expression information through the key display area, changing a display position of the sector area on the display screen when it is detected that the display screen is touched by a preset second operational motion in the key display area.(String), 13.根据权利要求4所述的移动终端虚拟键盘的设置方法,还包括:在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角之后,设置虚拟键盘的扇形区域在移动终端显示屏上的显示大小。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 4. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after displaying the expression information in the symbol display area, displaying one or more operational options around the symbol display area and perform operation according to a selected operational option when it is detected that the symbol display area has been pressed for a preset period of time.(String), 14.根据权利要求7所述的移动终端,其中设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域在显示器上的显示大小移动终端屏幕。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 5. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 15.根据权利要求8所述的移动终端,其中设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域在显示器上的显示大小移动终端屏幕。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 6. A mobile terminal comprising a setting module and a processing module, whereinthe setting module is configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, and provide a symbol display area and a key display area of the sector area for the processing module, wherein an arc-shaped area of the sector area is the symbol display area, and a remaining area of the sector area is the key display area;the processing module is configured to receive the symbol display area and the key display area in the sector area provided by the setting module, and after receiving expression information which is input through the key display area, display the expression information in the symbol display area.(String), 16.根据权利要求9所述的移动终端,其中设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域在显示器上的显示大小移动终端屏幕。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 7. The mobile terminal according to claim 6, further comprising:a virtual keyboard hiding module configured to, when it is detected that the display screen is touched by a preset first operational motion in the key display area, hide the virtual keyboard.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 8. The mobile terminal according to claim 6, further comprising:a sector area display position adjusting module configured to, when it is detected that the display screen is touched by a preset second operational motion in the key display area, change a display position of the sector area on the display screen.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 9. The mobile terminal according to claim 6, further comprising:an operational option prompt module configured to, after the expression information is displayed in the symbol display area and after it is detected that the symbol display area has been pressed for a preset period of time, display one or more operational options around the symbol display area and perform operation according to a selected operational option.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.069 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 10. The mobile terminal according to claim 6, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 11. The method for setting a virtual keyboard of a mobile terminal according to claim 2, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 12. The method for setting a virtual keyboard of a mobile terminal according to claim 3, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 13. The method for setting a virtual keyboard of a mobile terminal according to claim 4, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 12(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 14. The mobile terminal according to claim 7, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 15. The mobile terminal according to claim 8, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 14(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.070 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185032(Integer), 16. The mobile terminal according to claim 9, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185032(Integer), FIELD [0001]The disclosure relates to the field of mobile communication, and particularly to a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. BACKGROUND [0002]With the popularization of touch screens, display screens of mobile terminals tend to become larger. Existing 3.2-inch and 3.5-inch display screens have been gradually replaced by 4.0-inch, 4.3-inch and 5.3-inch screens, and even 6-inch and 7-inch display screens have even emerged. Since all existing virtual keyboards are square and located at the bottom of mobile terminals, when a display screen of a mobile terminal becomes larger, the resulting problem is that the whole screen is hardly covered by operation with one hand, thus reducing the operating efficiency and increasing the difficulty in operation and thereby affecting the user experience. SUMMARY [0003]The disclosure is to provide a mobile terminal and a method for setting a virtual keyboard of a mobile terminal to solve the problem of inconvenient input operation by a user with one hand on a mobile terminal having a large display screen in the existing technology. [0004]To solve the problem, the disclosure provides a method for setting a virtual keyboard of a mobile terminal on one hand, including the following steps: [0005]A virtual keyboard is set on a corner of a display screen of a mobile terminal and is displayed in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; [0006]after receiving expression information which is input through the key display area, the expression information is displayed in the symbol display area. [0007]Further, after the expression information is input through the key display area, the method may further include: when it is detected that the display screen is touched by a preset first operational motion in the key display area, the virtual keyboard is hided. [0008]Further, after the expression information is input through the key display area, the method may further include: when it is detected that the display screen is touched by a preset second operational motion in the key display area, the display position of the sector area is changed on the display screen. [0009]Further, after the expression information is displayed in the symbol display area, the method may further include: [0010]when it is detected that the symbol display area has been pressed for a preset period of time, one or more operational options is displayed around the symbol display area and operation is performed according to a selected operational option. [0011]Further, after the virtual keyboard is set on the corner of the display screen of the mobile terminal and is displayed in the form of the sector area, the method may further include: [0012]a display size of the sector area of the virtual keyboard is set on the display screen of the mobile terminal. [0013]The disclosure may further provide a mobile terminal on the other hand, including a setting module and a processing module, wherein [0014]the setting module is configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, and provide a symbol display area and a key display area of the sector area for the processing module, wherein the arc-shaped area of the sector area is the symbol display area, and the remaining area of the sector area is the key display area; [0015]the processing module is configured to receive the symbol display area and the key display area in the sector area provided by the setting module, and after receiving expression information input through the key display area, display the expression information in the symbol display area. [0016]Further, the mobile terminal may further include a virtual keyboard hiding module configured to, when it is detected that the display screen is touched by a preset first operational motion in the key display area, hide the virtual keyboard. [0017]Further, the mobile terminal may further include a sector area display position adjusting module configured to, when it is detected that the display screen is touched by a preset second operational motion in the key display area, change the display position of the sector area on the display screen. [0018]Further, the mobile terminal may further include an operational option prompt module configured to, after the expression information is displayed in the symbol display area and after it is detected that the symbol display area has been pressed for a preset period of time, display one or more operational options around the symbol display area and perform operation according to a selected operational option. [0019]Further, the setting module may be further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal. [0020]The disclosure has the following beneficial effect: [0021]The disclosure displays a virtual keyboard in the form of a sector area on a display screen so that a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS [0022]FIG. 1 is a flowchart of a method for setting a virtual keyboard of a mobile terminal in an embodiment of the disclosure; [0023]FIG. 2 is a diagram of the effect of displaying a virtual keyboard on a display screen of a mobile terminal in an embodiment of the disclosure; [0024]FIG. 3 is a comparison diagram of displaying and hiding a virtual keyboard on a display screen of a mobile terminal in an embodiment of the disclosure; [0025]FIG. 4 is a comparison diagram of displaying a virtual keyboard at the left and right ends of a display screen of a mobile terminal in an embodiment of the disclosure; [0026]FIG. 5 is a diagram of the effect of operating expression information in a symbol display area in an embodiment of the disclosure; [0027]FIG. 6 is a diagram of the effect of further operating expression information in a symbol display area in an embodiment of the disclosure; [0028]FIG. 7 is a structural diagram of a mobile terminal in an embodiment of the disclosure; and [0029]FIG. 8 is a structural diagram of another mobile terminal in an embodiment of the disclosure. DETAILED DESCRIPTION [0030]To solve the problem of inconvenient input operation of a user on a mobile terminal having a large display screen with one hand, the disclosure provides a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. The disclosure will be further described in details below in combination with the accompanying drawings and embodiments. It should be understood that the embodiments described herein are only used for explaining the disclosure, instead of limiting the disclosure. [0031]As shown in FIG. 1, an embodiment of the disclosure relates to a method for setting a virtual keyboard of a mobile terminal, including the following steps: [0032]Step 101: a virtual keyboard is set on a corner of a display screen of a mobile terminal and is displayed in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; [0033]here, the virtual keyboard is a keyboard displayed on the display screen of the mobile terminal, but not a physical keyboard really existing on the mobile terminal; the virtual keyboard may be a keyboard having an input mode like numbers, letters, symbols or strokes etc.; the size of the virtual keyboard is set according to a great amount of acquired data (the data of a moving range of a thumb when a user operates the mobile terminal with one hand), and the data tested at work; [0034]the physical size of the sector area, which is fixed within a range and is not related to the display screen of the mobile terminal, does not need to increase with the increase of the display screen of the mobile terminal; three display sizes including a large size, a medium sides and a small size may be set for the sector area for a user to select so as to be applicable to different thumb sizes of users; of course, more or less levels may be also provided; generally, the three sizes, i.e. the large size, the medium size, and the small size can meet the use requirement of most users; [0035]Step 102: after expression information input through the key display area is received, the expression information is displayed in the symbol display area; [0036]here, the expression information refers to information input by a user through the virtual keyboard, which may be a phone number, and may be also information including texts, numbers, letters and/or symbols etc.; [0037]since the virtual keyboard will shield a part of the display screen of the mobile terminal, a user may need to hide the virtual keyboard sometimes, i.e. not display the virtual keyboard on the display screen of the mobile terminal; in this case, the user only needs to touch the display screen of the mobile terminal with a preset first operational motion in the key display area, then the virtual keyboard will be hidden; the preset first operational motion may be any preset operational motion, e.g. a sweep with horizontal straight line, a sweep with a vertical straight line, a sweep with an arc in a specific direction, a sweep with curve of a specific shape of a number or a letter, or other similar operation; [0038]in addition, since users have different habits to operate with the left hand or the right hand, the virtual keyboard needs to be set at the lower left corner, the upper right corner, upper left corner or the lower right corner of the display screen of the mobile terminal for different users. Therefore, settings need to be provided for the left hand and the right hand to change the position of a sector-shaped dial plate on the screen; [0039]when the virtual keyboard is displayed on the mobile terminal and when a user touches the display screen with a preset second operational motion in the key display area, the display position of the sector area on the display screen is changed; the preset second operational motion may be any preset operational motion, e.g. a sweep with horizontal straight line, a sweep with a vertical straight line, a sweep with an arc in a specific direction, a sweep with curve of a specific shape of a number or a letter, or other similar operation; of course, the first operational motion cannot be the same with the second operational motion; in the embodiment, for example, when a user sweeps with a straight line from the left to the right in the key display area, the sector area of the virtual keyboard is displayed at the lower left corner of the display screen; when a user sweeps with a straight line from the right to the left in the key display area, the sector area of the virtual keyboard is displayed at the lower right corner of the display screen; when a user sweeps with a straight line from the top down in the key display area, the sector area of the virtual keyboard is displayed at the upper left corner of the display screen; when a user sweeps with a straight line from the bottom up in the key display area, the sector area of the virtual keyboard is displayed at the upper right corner of the sector area; [0040]in Step 102, after the expression information is displayed in the symbol display area, the following processing is further included: [0041]after a user presses the symbol display area for a preset period of time, one or more operational options is displayed around the symbol display area to guide the user to select an operational option to finish an operation, e.g. if a phone number is displayed in the symbol display area, after the user presses the displayed phone number for 3 s (it may be other time values, any setting), operational options, such as voice call, video call, save etc., are displayed around the phone number to guide the user to a further operation. [0042]Detailed description will be provided below by taking a virtual keyboard which is a dial plate as an example. [0043]FIG. 2 shows diagram of the effect of displaying a virtual keyboard on a display screen of a mobile terminal in the present embodiment, wherein a new dial plate is sector-shaped; the outermost sector area is a number display area and the remaining internal area is a number key area. [0044]FIG. 3 shows a comparison diagram of displaying and hiding a virtual keyboard on a display screen of a mobile terminal in the present embodiment. A dial plate can be hidden by dragging a number area within the dashed lines, specifically including: sliding in the number key area, and recognizing by the mobile terminal that the sliding direction is between 3 o'clock and 6 o'clock, then executing an operation of hiding the dial plate. [0045]FIG. 4 shows a comparison diagram of displaying a virtual keyboard at the left and right ends of a display screen of a mobile terminal in the present embodiment. A number key area is dragged to the left to switch a dial plate to a mode suitable to be used by the left hand, specifically including: sliding in the number key area, and recognizing by the mobile terminal that the sliding direction is between 6 o'clock and 9 o'clock, then executing an operation of changing a right hand-adaptive dial plate to a left hand-adaptive plate, i.e. changing the dial plate from being displayed at the lower right corner to being displayed at the lower left corner. [0046]In the present embodiment, 3 o'clock, 6 o'clock and 9 o'clock means that the middle point of the upper border line of the display screen of the mobile terminal is recorded as 12 o'clock; the middle point of the lower border line of the display screen of the mobile terminal is recorded as 6 o'clock, the middle point of the left border line of the display screen of the mobile terminal is recorded as 9 o'clock and the middle point of the right border lien of the display screen of the mobile terminal is recorded as 3 o'clock. [0047]FIG. 5 shows a diagram of the effect of operating expression information in a symbol display area in the present embodiment, wherein the dashed line oval represents a position that a user can press for a long period of time; after a number display area is pressed for a certain long period of time, an operational option which can be executed according to an entered number is displayed around the number display area of the display screen and the user is guided to perform the next gesture operation. In the present embodiment, if a finger of the user slides along the downward arrow towards the option item of Send Short Message Service (SMS), an operation of writing a text message to the number is executed; after the user is practiced, the operation of writing a text message to the number can be executed by a quick downward sliding operation after pressing the number display area. [0048]As shown in FIG. 6, if a gesture operation is performed once in FIG. 5, a subsequent operational option is required, then subsequent operational options are displayed on an interface and the user is guided to perform a secondary gesture operation. In the interface displayed in FIG. 5, if a finger of the user slides to the option item of Save Contact along the rightward arrow in the figure, then the option items of New Contact and Add to Contact are respectively displayed above and below the option item of Save Contact. At the moment, the finger of the user is located at the dashed line oval in FIG. 6, and an operation of creating a name card is executed if the finger slides upwards to the option item of New Contact. After the user is practiced, the operation of creating a name card can be executed by quickly siding rightwards and then upwards after pressing the number display area. [0049]As shown in FIG. 7, an embodiment of the disclosure further relates to a mobile terminal for realizing the method above, including a setting module 201 and a processing module 202, wherein [0050]the setting module 201 is configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, wherein the arc-shaped area of a sector area is a symbol display area, and the remaining area of the sector area is a key display area; and provide the symbol display area and key display area of the set sector area for the processing module 202, [0051]the processing module 202 is configured to receive the symbol display area and the key display area in the sector area provided by the setting module 201, and after receiving expression information which is input through the key display area, display the expression information in the symbol display area. [0052]To realize better technical effect, as shown in FIG. 8, an embodiment of the disclosure further relates to a mobile terminal for realizing the method above, including: [0053]a setting module 301, configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; the setting module 301 is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on a corner of the display screen of the mobile terminal, set a display size of the virtual keyboard on the display screen. [0054]A processing module 302 configured to, after receiving expression information input through the key display area, display the expression information in the symbol display area. [0055]The mobile terminal further includes a virtual keyboard hiding module 303 which is configured to receive from the processing module 302 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the virtual keyboard hiding module locates, and when it is detected that the display screen is touched by a user with a preset first operational motion in the key display area, hide the virtual keyboard; accordingly, the processing module 302 is further configured to send the virtual keyboard hiding module 303 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the processing module locates. [0056]The mobile terminal further includes a sector area display position adjusting module 304 configured to receive from the processing module 302 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the sector area display position adjusting module locates, and when it is detected that the display screen is touched by a user with a preset second operational motion in the key display area, change the display position of the sector area on the display screen; accordingly, the processing module 302 is further configured to send the sector area display position adjusting module 304 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the processing module locates. [0057]The mobile terminal further includes an operational option prompt module 305 configured to, receive the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the operational option prompt module locates from the processing module 302, and after displaying the expression information in the symbol display area and after it is detected that the symbol display area is pressed by a user for a preset period of time, display one or more operational options around the symbol display area and guide the user to select an operational option to complete an operation; accordingly, the processing module 302 is further configured to send the operational option prompt module 305 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the processing module locates. [0058]The mobile terminals in the embodiments above may be devices including mobile phones, Personal Digital Assistants (PDA) and tablet computers etc., and may be also other devices having a touch screen function and capable of processing data. [0059]It can be seen from the embodiments above that the disclosure displays a virtual keyboard in the form of a sector area in a display screen, and a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience. [0060]Although the preferred embodiments of the disclosure have been disclosed for the purpose of demonstration, it will be realized that various improvements, additions, and replacements are possible for those skilled in the art. Therefore, the scope of the disclosure is not intended to limited to the above embodiments.(String), 场地 [0001] 本发明涉及移动通信领域,尤其涉及一种移动终端及移动终端虚拟键盘的设置方法。 背景 [0002] 随着触摸屏的普及,移动终端的显示屏幕趋于变大。 现有的3.2英寸、3.5英寸的显示屏逐渐被4.0英寸、4.3英寸、5.3英寸的显示屏所取代,甚至出现了6英寸、7英寸的显示屏。 由于现有的虚拟键盘都是方形的,并且位于移动终端的底部,当移动终端的显示屏幕变大时,带来的问题是单手操作很难覆盖整个屏幕,降低了操作效率, 增加操作难度,影响用户体验。 概括 [0003] 本发明的目的在于提供一种移动终端及移动终端虚拟键盘的设置方法,以解决现有技术中用户在大显示屏移动终端上单手输入操作不便的问题。 [0004] 为解决上述问题,本发明一方面提供了一种移动终端虚拟键盘的设置方法,包括以下步骤: [0005] 虚拟键盘设置在移动终端显示屏的一角,以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,扇形的其余区域 area为重点显示区域; [0006] 接收到通过按键显示区输入的表情信息后,将表情信息显示在符号显示区中。 [0007] 进一步地,在通过按键显示区输入表情信息之后,该方法还可以包括: 当检测到按键显示区中预设的第一操作动作触碰显示屏时,隐藏虚拟键盘。 [0008] 进一步地,在通过按键显示区输入表情信息之后,该方法还包括:当检测到按键显示区中预设的第二操作动作触碰显示屏时,扇形区的显示位置为: 在显示屏幕上改变。 [0009] 进一步的,所述符号显示区显示所述表情信息后,所述方法还包括: [0010] 当检测到符号显示区域被按下预设时间时,在符号显示区域周围显示一个或多个操作选项,并根据选择的操作选项进行操作。 [0011] 进一步的,所述虚拟键盘设置在所述移动终端显示屏的一角,并以扇形区域的形式显示后,所述方法还包括: [0012] 在移动终端的显示屏上设置虚拟键盘扇区的显示大小。 [0013] 另一方面,本发明还可以提供一种移动终端,包括设置模块和处理模块,其中 [0014] 设置模块,用于设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角,并提供扇形区域的符号显示区域和按键显示区域供处理 模块,其中扇区的弧形区域为符号显示区,扇区的剩余区域为按键显示区; [0015] 处理模块,用于接收设置模块提供的扇区中的符号显示区和按键显示区,并在接收到通过按键显示区输入的表情信息后,在符号显示区中显示表情信息。 [0016] 进一步的,该移动终端还可以包括:虚拟键盘隐藏模块,用于在检测到所述按键显示区域中预设的第一操作动作触碰所述显示屏时,隐藏所述虚拟键盘。 [0017]进一步地,该移动终端还可以包括扇形区域显示位置调整模块,用于在检测到预设的第二操作动作在按键显示区域触碰显示屏时,改变扇形区域在按键显示区域的显示位置。 显示屏。 [0018] 进一步地,移动终端还可以包括操作选项提示模块,用于在符号显示区域显示表情信息后,检测到符号显示区域被按下预设时间后,显示一个或 更多操作选项围绕符号显示区,根据选中的操作选项进行操作。 [0019] 进一步地,设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域的显示大小 在移动终端的显示屏上。 [0020] 本发明具有以下有益效果: [0021] 本发明在显示屏上以扇形区域的形式显示虚拟键盘,使用户可以方便地用一只手在移动终端上输入信息,大大提高了用户的操作效率,改善了用户体验。 附图的简要说明 [0022] 图1为本发明实施例中移动终端虚拟键盘的设置方法流程图; [0023] 图2为本发明实施例中在移动终端的显示屏上显示虚拟键盘的效果图。 [0024] 图3为本发明实施例中移动终端显示屏显示和隐藏虚拟键盘的对比图。 [0025] 图4为本发明实施例中移动终端显示屏左右两端显示虚拟键盘的对比图。 [0026] 图5为本发明实施例中符号显示区操作表情信息的效果图。 [0027] 图6为本发明实施例中符号显示区进一步操作表情信息的效果图。 [0028] 图7为本发明实施例中移动终端的结构图; 和 [0029] 图8为本发明实施例的另一种移动终端的结构图。 详细说明 [0030] 为解决用户在大显示屏移动终端上单手输入操作不便的问题,本发明提供了一种移动终端及移动终端虚拟键盘的设置方法。 下面结合附图及实施例对本发明作进一步详细说明。 应当理解,此处所描述的实施例仅仅用于解释本发明,并不用于限制本发明。 [0031] 如图1所示,本发明实施例涉及一种移动终端虚拟键盘的设置方法,包括以下步骤: [0032] 步 101 :虚拟键盘设置在移动终端显示屏的一角,以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为符号显示区域。 扇区为重点显示区; [0033] 这里,虚拟键盘是显示在移动终端显示屏上的键盘,而不是移动终端上真实存在的物理键盘。 虚拟键盘可以是具有数字、字母、符号或笔画等输入方式的键盘。 虚拟键盘的大小是根据获取的大量数据(用户单手操作移动终端时拇指移动幅度的数据)和工作中测试的数据来设置的。 [0034]扇区的物理大小,固定在一个范围内,与移动终端的显示屏无关,不需要随着移动终端显示屏的增大而增大。 扇形区域可以设置大、中、小三种显示尺寸供用户选择,以适应不同拇指大小的用户。 当然,也可以提供更多或更少的层级。 一般来说,大号、中号、小号三种尺寸可以满足大部分用户的使用需求; [0035] 步 102 :接收到按键显示区输入的表情信息后,在符号显示区显示表情信息; [0036] 这里,表情信息是指用户通过虚拟键盘输入的信息,可以是电话号码,也可以是包括文字、数字、字母和/或符号等的信息。 [0037] 由于虚拟键盘会遮挡一部分移动终端的显示屏,用户有时可能需要隐藏虚拟键盘,即不在移动终端的显示屏上显示虚拟键盘。 此时,用户只需在按键显示区域以预设的第一操作动作触碰移动终端的显示屏,虚拟键盘就会被隐藏。 预设的第一操作动作可以是任何预设的操作动作,例如 水平直线扫掠、垂直直线扫掠、特定方向圆弧扫掠、数字或字母特定形状曲线扫掠等类似操作; [0038] 另外,由于用户用左手或右手操作的习惯不同,虚拟键盘需要设置在显示屏的左下角、右上角、左上角或右下角。 针对不同用户的移动终端。 因此,需要对左右手进行设置,改变扇形表盘在屏幕上的位置; [0039] 当虚拟键盘显示在移动终端上时,当用户在按键显示区域以预设的第二操作动作触碰显示屏时,改变扇形区域在显示屏上的显示位置。 预设的第二操作动作可以是任何预设的操作动作,例如 水平直线扫掠、垂直直线扫掠、特定方向圆弧扫掠、数字或字母特定形状曲线扫掠等类似操作; 当然,第一操作动作不能与第二操作动作相同; 在本实施例中,例如,当用户在按键显示区域从左向右直线扫动时,在显示屏的左下角显示虚拟键盘的扇形区域。 当用户在按键显示区由右向左直线扫动时,在显示屏右下角显示虚拟键盘的扇区。 当用户在按键显示区从上向下直线扫动时,在显示屏的左上角显示虚拟键盘的扇形区域。 当用户在按键显示区用直线自下而上扫过时,虚拟键盘的扇区显示在扇区的右上角。 [0040] 在步骤 102 ,在符号显示区显示表情信息后,还包括以下处理: [0041] 当用户按下符号显示区域预设时间后,符号显示区域周围显示一个或多个操作选项,以引导用户选择操作选项以完成操作,例如 如果符号显示区显示电话号码,用户长按显示的电话号码3s后(可以是其他时间值,任意设置),语音通话、视频通话、保存等操作选项, 在电话号码周围显示,以引导用户进行进一步的操作。 [0042]下面以虚拟键盘即拨号盘为例进行详细说明。 [0043] 图2为本实施例在移动终端的显示屏上显示虚拟键盘的效果图,其中新表盘为扇形。 最外面的扇区是数字显示区,其余的内部区是数字键区。 [0044] 图3示出了本实施例中移动终端显示屏显示和隐藏虚拟键盘的对比图。 可以通过拖动虚线内的数字区域来隐藏表盘,具体包括:在数字键区域滑动,移动端识别滑动方向为3点到6点之间,然后执行 隐藏表盘的操作。 [0045] 图4为本实施例中移动终端显示屏左右两端显示虚拟键盘的对比图。 向左拖动数字键区域,将表盘切换到适合左手使用的模式,具体包括:在数字键区域滑动,移动终端识别滑动方向在6°之间。 点钟和9点钟,然后执行将右手自适应表盘改为左手自适应表盘的操作,即将表盘由右下角显示改为左下角显示 . [0046] 在本实施例中,3点钟、6点钟和9点钟是指移动终端显示屏的上边框线的中点记为12点钟; 移动终端显示屏下边框线的中点记为6点,移动终端显示屏左边框线的中点记为9点,中间 记录移动终端显示屏右边框线的点为3点。 [0047] 图5为本实施例中符号显示区操作表情信息的效果图,其中虚线椭圆表示用户可以长时间按下的位置。 在数字显示区域被长按一定时间后,在显示屏的数字显示区域周围显示可根据输入的数字执行的操作选项,引导用户进行下一步的手势操作。 在本实施例中,如果用户的手指沿着向下的箭头向发送短信服务(SMS)选项项滑动,则执行向该号码写入短信的操作; 用户练习后,在按下号码显示区后,通过快速向下滑动操作,即可执行给号码写短信的操作。 [0048] 如图6所示,如果在图5中进行了一次手势操作,则需要进行后续的操作选项,则在界面上显示后续的操作选项,引导用户进行二次手势操作。 在图5显示的界面中,如果用户的手指沿着图中向右的箭头滑动到保存联系人选项,则在该选项的上方和下方分别显示新建联系人和添加到联系人选项。 的保存联系人。 此时,用户手指位于图6中虚线椭圆处,手指向上滑动至新建联系人选项,则执行创建名片的操作。 用户熟练后,按下数字显示区后快速向右再向上,即可执行制作名片的操作。 [0049] 如图7所示,本发明实施例还涉及一种实现上述方法的移动终端,包括设置模块 201 和一个处理模块 202 , 其中 [0050] 设置模块 201用于设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角,扇形区域的弧形区域为符号显示区域,其余区域为 扇区为重点显示区; 并为处理模块提供设置扇区的符号显示区和按键显示区 202 , [0051] 处理模块 202 用于接收设置模块提供的扇区中的符号显示区和按键显示区 201 ,接收到通过按键显示区输入的表情信息后,将表情信息显示在符号显示区。 [0052] 为实现更好的技术效果,如图8所示,本发明实施例还涉及一种实现上述方法的移动终端,包括: [0053] 设置模块 301 ,用于设置虚拟键盘在移动终端显示屏的一角以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为 扇区为重点显示区; 设置模块 301 还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘在显示屏上的显示尺寸。 [0054] 一个处理模块 302 用于接收到按键显示区输入的表情信息后,在符号显示区显示表情信息。 [0055] 移动终端还包括虚拟键盘隐藏模块 303 它被配置为从处理模块接收 302 虚拟键盘隐藏模块所在的移动终端显示屏的扇区的符号显示区和按键显示区,当检测到用户以预设的第一操作动作触摸显示屏时 按键显示区,隐藏虚拟键盘; 相应地,处理模块 302 还用于发送虚拟键盘隐藏模块 303 所述处理模块所在的移动终端显示屏的扇区中的符号显示区和按键显示区。 [0056] 移动终端还包括扇区显示位置调整模块 304 配置为从处理模块接收 302 扇区显示位置调整模块所在的移动终端显示屏的扇区的符号显示区和按键显示区,当检测到用户以预设的第二操作触摸显示屏时 在按键显示区移动,改变扇形区在显示屏上的显示位置; 相应地,处理模块 302 还用于发送扇区显示位置调整模块 304 所述处理模块所在的移动终端显示屏的扇区中的符号显示区和按键显示区。 [0057] 移动终端还包括操作选项提示模块 305 用于从所述处理模块接收所述移动终端显示屏的所述操作选项提示模块所在扇形区域的符号显示区域和按键显示区域 302 ,在符号显示区显示表情信息,并检测到用户按下符号显示区预设时间后,在符号显示区周围显示一个或多个操作选项,引导用户进行操作。 选择一个操作选项来完成一个操作; 相应地,处理模块 302 还用于发送操作选项提示模块 305 所述处理模块所在的移动终端显示屏的扇区中的符号显示区和按键显示区。 [0058]上述实施例中的移动终端可以是手机、个人数字助理(Personal Digital Assistant,PDA)、平板电脑等设备,也可以是其他具有触摸屏功能的能够处理数据的设备。 [0059] 从以上实施例可以看出,本发明在显示屏中以扇形区域的形式显示虚拟键盘,用户可以方便地在移动终端上单手输入信息,大大提高了操作效率。 用户,提升用户体验。 [0060] 尽管出于示范的目的而公开了本公开的优选实施例,但是对于本领域的技术人员来说将认识到各种改进、添加和替换是可能的。 因此,本发明的范围并非旨在限于上述实施例。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102681670A(String), EP2824553A1(String), EP2824553A4(String), US20150067572A1(String), WO2013152558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102681670A(String), EP2824553A1(String), EP2824553A4(String), US20150067572A1(String), WO2013152558A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.225 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20150067572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102681670A(String), EP2824553A1(String), EP2824553A4(String), US20150067572A1(String), WO2013152558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270707(Integer), CN102681670A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270707(Integer), EP2824553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270707(Integer), EP2824553A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.277 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270707(Integer), US20150067572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.288 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270707(Integer), WO2013152558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.301 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20150067572A1(String), US20150067572A1(String), 1425484800(Integer), 270707(Integer), 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.313 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.314 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), BAI, JINJIAN(String), 中兴通讯股份有限公司(String), BAI JINJIAN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185032(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185032(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: BAI, JINJIAN(String), BAI JINJIAN(String), 0(Integer), 1681975565(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185032(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75953(Integer), 2(Integer), 185032(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185032(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.375 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10554877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10554877B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/240348(String), 1546531200(Integer), US10554877B2(String), 1580745600(Integer), 1580745600(Integer), 美国(String), 4(Integer), CN(String), 1(Integer), 15(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2012208876A | US20110013061A1 | US20130156345A1 | US20150109513A1 | WO2014097792A1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185033(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.392 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7af214bca8c24c18980db2f22cb4e137.png(String), 185033(Integer), 7af214bca8c24c18980db2f22cb4e137.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.401 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10554877B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/240348(String), 1546531200(Integer), US10554877B2(String), 1580745600(Integer), 1580745600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 1(Integer), 15(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2012208876A | US20110013061A1 | US20130156345A1 | US20150109513A1 | WO2014097792A1(String), \20230420\7af214bca8c24c18980db2f22cb4e137.png(String), 14(Integer), 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.409 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.410 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 1. An image synthesis method for a mobile terminal, comprising:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel, wherein the initial location is a location of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data;wherein controlling the photosensitive element to generate the displacement at the initial location comprises:controlling, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location, comprising:controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 1.移动终端,包括:外壳、处理器、存储器、电路板和供电电路,其中,电路板设置在外壳围成的空间内,处理器和存储器设置在电路板上,供电电路用于为移动终端的电路或部件供电,存储器用于存储可执行文件程序代码,处理器用于通过读取内存中存储的可执行程序代码来运行与可执行程序代码对应的程序,执行:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦;控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素,其中,初始位置为感光元件在相位对焦时在移动终端中的位置基于移动终端中的感光元件的预设像素拍摄的物体;根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置;对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据;和根据第一感光数据与第二感光数据合成待摄对象的图像;其中,处理器还被配置为:通过微机电光学稳像系统控制感光元件在初始位置产生位移;和其中,处理器还被配置为:微机电光学稳像系统通过空间直角坐标系三轴方向的运动控制感光元件在初始位置产生位移,三轴方向的运动包括两个方向的平移运动水平面中的正交方向和绕垂直于水平面的轴的旋转运动。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 2. The image synthesis method according to claim 1, synthesizing the image of the object to be photographed according to the first photosensitive data and the second photosensitive data comprising:performing a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 12.根据权利要求11所述的移动终端,其中处理器还被配置为:将第二感光数据与第一感光数据进行补偿处理,根据补偿处理后的第二感光数据合成被摄体的图像。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 3. The image synthesis method according to claim 1, wherein the preset pixel is a masked pixel.(String), 13.根据权利要求11所述的移动终端,其中预设像素为屏蔽像素。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 4. The image synthesis method according to claim 1, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having a first module, a second module, a third module and a fourth module, andwhen performing the rotating movement, the method comprises at least one of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the method comprises at least one of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 14.根据权利要求11所述的移动终端,其中微机电光学防抖系统包括具有第一模块、第二模块、第三模块和第四模块的微机电系统,以及当执行旋转运动时,处理器被配置为执行以下至少一个动作:控制第一模块向上运动,第二模块向右运动,第三模块向左运动,第四模块向下运动,使微机电系统顺时针旋转;和控制第一模块向下运动,第二模块向左运动,第三模块向右运动,第四模块向上运动,使微机电系统逆时针旋转;和当执行平移运动时,处理器被配置为执行以下至少一个动作:控制第一模块和第四模块动作使微机电系统上下运动;和控制第二模块和第三模块采取动作使微机电系统左右移动。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 5. The image synthesis method according to claim 1, wherein the original pixel is a default pixel where a masked pixel is not reserved on the photosensitive element in the mobile terminal.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 6. An image synthesis apparatus for a mobile terminal, comprising a non-transitory computer-readable medium comprising computer-executable instructions stored thereon, and an instruction execution system which is configured by the instructions to implement acts of:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel, wherein the initial location is a location of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data;wherein the instruction execution system is further configured by the instructions to implement an act of:controlling, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location; andwherein the instruction execution system is further configured by the instructions to implement an act of:controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 7. The image synthesis apparatus according to claim 6, wherein the instruction execution system is further configured by the instructions to implement an act of:perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 8. The image synthesis apparatus according to claim 6, wherein the preset pixel is a masked pixel.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 9. The image synthesis apparatus according to claim 6, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having a first module, a second module, a third module and a fourth module, and when performing the rotating movement, the instruction execution system is further configured by the instructions to implement at least one act of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the instruction execution system is further configured by the instructions to implement at least one act of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 10. The image synthesis apparatus according to claim 6, wherein the original pixel is a default pixel where a masked pixel is not reserved on the photosensitive element in the mobile terminal.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 11. A mobile terminal, comprising: a housing, a processor, a memory, a circuit board and a power supply circuit, wherein,the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel, wherein the initial location is a location of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data;wherein the processor is further configured to:control the photosensitive element to generate the displacement at the initial location by a micro-electromechanical optical image stabilization system; andwherein the processor is further configured to:control, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 12. The mobile terminal according to claim 11, wherein the processor is further configured to:perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 13. The mobile terminal according to claim 11, wherein the preset pixel is a masked pixel.(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185033(Integer), 14. The mobile terminal according to claim 11, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having a first module, a second module, a third module and a fourth module, andwhen performing the rotating movement, the processor is configured to perform at least one act of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the processor is configured to perform at least one act of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.522 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.523 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185033(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The present application is a continuation application of a U.S. application Ser. No. 16/302,323, filed on Nov. 16, 2018, which is a national phase entry of International Application No. PCT/CN2017/087806, filed on Jun. 9, 2017, which claims priority from Chinese Patent Application No. 201610616090.6, filed on Jul. 29, 2016 by GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD., entitled “Image Synthesis Method and Device for Mobile Terminal, and Mobile Terminal”. The entire contents of the aforementioned applications are incorporated by reference herein. TECHNICAL FIELD [0002]The present disclosure relates to a field of mobile terminal technology, and in particular, to an image synthesis method and apparatus for a mobile terminal, and a mobile terminal. BACKGROUND [0003]Optical Image Stabilization (OIS) may effectively avoid image blur caused by jitter during a process of the user taking pictures with a mobile terminal. OIS uses a magnetically wrapped suspension lens to effectively overcome image blur caused by vibration of the mobile terminal. In the related art, the anti-shake is realized by a photosensitive element, of which the principles may be described as followings. The photosensitive element is fixed on a bracket that can move up, down, left, and right, and the direction and amplitude data of the shaking of the mobile terminal are sensed by a gyro sensor. After that, the gyro sensor transmits the data. Screening and amplification are performed on the data at the processor side to calculate the amount of movement of the photosensitive element that may compensate the jitter. During the process of the user taking pictures with the mobile terminal, it is also necessary to perform phase focusing on the scene to be photographed. In the related art, by hiding some masked pixels on the photosensitive element, and considering the distance between the pixels of the scene to be photographed and its changing factors, the focusing offset value may be determined to achieve the phase focusing. [0004]In this way, the masked pixels may only be used to detect the phase and cannot be used to display the image. The masked pixels may affect the quality of the image photographed. The higher the density of the masked pixels, the more accurate the phase focusing, but the worse the quality of the image photographed. SUMMARY [0005]The present disclosure aims to solve at least one of technical problems in the related art to some extent. [0006]Embodiments of the present disclosure provide an image synthesis method for the mobile terminal. The method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0007]Embodiments of the present disclosure also provide a micro-electromechanical optical image stabilization system. The system may include: a photosensitive element, configured to collect photosensitive data of an object to be photographed; and a micro-electromechanical system (MEMS), configured to control the photosensitive element to generate a displacement at an initial position. [0008]Embodiments of the present application propose a storage medium, when instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform an image synthesis method for the mobile terminal. The image synthesis method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0009]Additional aspects and advantages of embodiments of present disclosure will be given in part in the following descriptions, become apparent in part from the following descriptions, or be learned from the practice of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to make technical solutions according to embodiments of the present disclosure more apparent, drawings needed to be used in descriptions of the embodiments will be illustrated in the following. Obviously, the drawings to be illustrated in the following only represent some embodiments of the present disclosure, and other drawings can be obtained according to these drawings by those having ordinary skills in the related art without making creative labors. [0011]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a schematic diagram of preset pixels on a photosensitive element in an embodiment of the present disclosure. [0013]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0014]FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0015]FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) according to an embodiment of the present disclosure. [0016]FIG. 6 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0017]FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0018]FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0019]FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0020]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0021]The technical solutions in embodiments of the present disclosure are hereinafter described clearly and completely with reference to accompanying drawings in embodiments of the present disclosure. Apparently, embodiments described are a part of embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments in the present disclosure without creative labor shall fall in the protection scope of the present disclosure. [0022]The terms “first”, “second”, “third” and “fourth” and the like in the specification and claims of the present disclosure and the above drawings are used to distinguish different objects, and are not intended to describe a specific order. Moreover, the terms “comprise” and “have” and their variants are aim at covering non-exclusive “include”. For example, a process, a method, a system, a term or a device including a series of steps or units may be not limited to the listed steps or units, instead and alternatively, other steps or units which are not listed may be included, or other steps or units inherent for these process, method, term or device may be included in an embodiment. [0023]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. This embodiment takes an example where an image synthesis method for the mobile terminal is configured for an image synthesis apparatus for the mobile terminal. Embodiments of the present disclosure mat be applied during a process of a user paragraphing a subject to be photographed using the mobile terminal. [0024]Referring to FIG. 1, the image synthesis method of the mobile terminal may include followings. [0025]At block S11, a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0026]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0027]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0028]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0029]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0030]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, G, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0031]At block S12, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0032]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0033]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11. [0034]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0035]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0036]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0037]At block S13, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0038]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0039]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be controlled to return to the initial position to photograph the object to be photographed based on the preset pixel. [0040]At block S14, the object to be photographed is photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. [0041]In embodiments of the present disclosure, when the photosensitive element is controlled to return to the initial position, the object to be photographed is photographed based on the preset pixel, such that the photosensitive element collects the photosensitive data of the object to be photographed at the initial position as the second photosensitive data. [0042]In embodiments of the present disclosure, since the photosensitive element generates the displacement at the initial position, the original pixel is used to replace the masked pixel on the photosensitive element, and the obtained replaced pixel is the original pixel. Therefore, the mobile terminal may perform a compensation on the second photographic data based on the first photographic data so as to compensate for the masked pixel. [0043]At block S15, an image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. [0044]In embodiments of the present disclosure, the second photosensitive data are subjected to compensation processing using the first photosensitive data to synthesize an image of the object to be photographed according to the compensated second photosensitive data. [0045]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0046]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0047]Referring to FIG. 3, the micro-electromechanical optical image stabilization system may include a photosensitive element 100 and a micro-electromechanical system (MEMS) 200. The photosensitive element 100 is configured to collect photosensitive data of an object to be photographed. The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate a displacement at an initial position. [0048]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may include the photosensitive element 100. [0049]The photosensitive element 100 is configured to collect photosensitive data of the object to be photographed. [0050]In an embodiment, a masked pixel is set on the photosensitive element 100, in which the masked pixel is used to perform a phase focusing on the object to be photographed. [0051]In an embodiment, when the user uses the mobile terminal to photograph the object to be photographed, the phase focusing may be performed on the object to be photographed based on the preset pixel on the photosensitive element 100 in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0052]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may also include the MEMS 200. [0053]The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate the displacement at the initial position. [0054]In embodiments of the present disclosure, the initial position is the position of the photosensitive element in the mobile terminal when the phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal in act of block S11 in the embodiment shown in FIG. 1. [0055]In an embodiment, the photosensitive element 100 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0056]In embodiments of the present disclosure, the MEMS 200 may be used to carry the photosensitive element 100, and the photosensitive element 100 may be moved in a three-axis direction of the space rectangular coordinate system to provide an anti-shake function during the process of photographing with the mobile terminal. [0057]As an example, referring to FIG. 4, FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 41, a micro-electromechanical system (MEMS) 42, and a glue 43, in which the photosensitive element 41 and the MEMS 42 are coupled using a chip-on-board technology and a dispensing method. The photosensitive element 41 may be controlled to move by the MEMS 42. [0058]Referring to FIG. 5, FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) 200 according to an embodiment of the present disclosure. The MEMS 200 may be translated upwards and downwards, left and right, and may be rotated with an angle. For example, when the MEMS 200 needs to move upwards and downwards, module 1 and module 4 take actions to cause the MEMS 200 to move upwards and downwards; when the MEMS 200 needs to move to the left and right, module 2 or module 3 take actions to cause the MEMS 200 to move to the left or right; when the MEMS 200 needs to rotate clockwise, the module 1 moves upwards, the module 2 moves to the right, the module 4 moves downwards, and the module 3 moves to the left, such that MEMS 200 rotates clockwise; similarly, when the MEMS 200 needs to rotate counterclockwise, the module 1 moves downwards, the module 2 moves to the left, the module 4 moves upwards, and the module 3 moves to the right. [0059]According to actual needs, the movements in three-axis directions of the space rectangular coordinate system in the MEMS 200 (i.e., translating movements in two orthogonal directions in the horizontal plane, and a rotating movement around the axis perpendicular to the horizontal plane) may be realized by controlling the module 1, the module 2, the module 3, and/or the module 4, such that the MEMS 200 may pulls the photosensitive element 100 to generate the displacement at the initial position to compensate for the masked pixels during the process of photographing with the mobile terminal. [0060]In an embodiment, in some embodiments, referring to FIG. 6, the micro-electromechanical optical image stabilization system may also include: a printed circuit board (PCB) 300. [0061]In embodiments of the present disclosure, the micro-electromechanical optical image stabilization system may also include the printed circuit board (PCB) 300 coupled to the MEMS 200. [0062]In an embodiment, the PCB 300 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0063]In an embodiment, the PCB 300 is used to carry the weight of the MEMS 200 and the photosensitive element 100 and is used for routing. [0064]As an example, referring to FIG. 7, FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. The system may include: a micro-electromechanical system (MEMS) 71, a printed circuit board (PCB) 72, and a glue 73, win which the MEMS 71 is coupled to the PCB 72 using a chip-on-board technology and a dispensing method. [0065]As an example, referring to FIG. 8, FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 81, a micro-electromechanical system (MEMS) 82, a printed circuit board (PCB) 83, a glue 84, a silicon wire 85 and a gold wire 86, in which the silicon wire 85 is configured to carry the weight of the moving portion of the MEMS 82, the outer side of the silicon wire 85 is gold plated to generate electrical conductivity at the same time, and the silicon wire 85 is configured to transmit signals of the photosensitive element 81 and to supply power to the MEMS 82. The gold wire 86 is configured to transmit signals of the photosensitive element 81 and to supply power to the photosensitive element 81. [0066]As an example, referring to FIG. 9, FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 91, a micro-electromechanical system (MEMS) 92, a silicon wire 93 and a gold wire 94. [0067]In this embodiment, a printed circuit board (PCB) is coupled to the MEMS, such that the PCB may carry the weight of the MEMS and the photosensitive element, and may supply power to the micro-electromechanical optical image stabilization system to ensure a normal operation of the micro-electromechanical optical image stabilization system. [0068]In this embodiment, the photosensitive data of the object to be photographed may be collected by the photosensitive element, and the MEMS may control the photosensitive element to generate a displacement at the initial position. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0069]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. The image synthesis apparatus 100 of the mobile terminal may be implemented by software, hardware or a combination thereof. The image synthesis apparatus 100 of the mobile terminal may include: a processing module 101, a control module 102, a collecting module 103, a photographing module 104, and a synthesizing module 105. [0070]The processing module 101 is configured to perform a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0071]In an embodiment, the preset pixel is a masked pixel. [0072]The control module 102 is configured to control the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and to obtain a replaced pixel. [0073]In an embodiment, the control module 102 is also configured to: control, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial position. [0074]The collecting module 103 is configured to collect first photosensitive data of the object to be photographed based on the replaced pixel, and to control the photosensitive element to return to the initial location. [0075]The photographing module 104 is configured to photograph the object to be photographed, and to enable the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location. [0076]The synthesizing module 105 is configured to synthesize an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0077]In an embodiment, the synthesizing module 105 is also configured to: perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing. [0078]It should be noted that, the description of embodiments of the image synthesis method for the mobile terminal in the foregoing embodiments of FIGS. 1-2 is also applicable to the image synthesis apparatus for the mobile terminal. The implementation principles thereof are similar, which will not be described in detail herein. [0079]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0080]Embodiments of the disclosure also provide a mobile terminal. The mobile terminal may include a housing, a processor, a memory, a circuit board and a power supply circuit, in which the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute followings. [0081]At block S11′: a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0082]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0083]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0084]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0085]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0086]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, G, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0087]At block S12′, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0088]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0089]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11′. [0090]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0091]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0092]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0093]At block S13′, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0094]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0095]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be contro(String), 相关申请的交叉引用 [0001] 本申请是美国申请系列的延续申请。 2018 年 11 月 16 日提交的第 16/302,323 号,是 2017 年 6 月 9 日提交的国际申请 PCT/CN2017/087806 的国家阶段进入,要求中国专利申请第 201610616090.6 号的优先权, 2016年7月29日,广东​​OPPO移动通信股份有限公司提交,题为“移动终端的图像合成方法及装置,以及移动终端”。 上述申请的全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端的图像合成方法、装置及移动终端。 背景 [0003] 光学防抖(OIS)可以有效避免用户在使用移动终端拍照的过程中由于抖动而导致的图像模糊。 OIS采用磁性包裹的悬浮镜头,有效克服移动终端震动造成的图像模糊。 现有技术中,防抖是通过感光元件来实现的,其原理可以描述如下。 感光元件固定在可上下左右移动的支架上,通过陀螺仪传感器感知移动终端晃动的方向和幅度数据。 之后,陀螺仪传感器传输数据。 在处理器端对数据进行筛选和放大,计算出可以补偿抖动的感光元件的移动量。 在用户使用移动终端拍照的过程中,还需要对要拍照的场景进行相位对焦。 在相关技术中,通过在感光元件上隐藏一些被遮蔽的像素,并考虑被摄场景的像素之间的距离及其变化因素,可以确定聚焦偏移值来实现相位聚焦。 [0004] 这样,被掩蔽的像素只能用于检测相位而不能用于显示图像。 被遮盖的像素可能会影响所拍摄图像的质量。 被掩蔽的像素密度越高,相位聚焦越准确,但拍摄的图像质量越差。 概括 [0005] 本发明旨在在一定程度上解决现有技术中的至少一个技术问题。 [0006] 本发明实施例提供一种移动终端的图像合成方法。 该方法可以包括: 当用户通过移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素,采集被摄物体的第一感光数据,并控制感光元件返回初始位置; 对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成被摄物体的图像。 [0007] 本发明实施例还提供一种微机电光学防抖系统。 该系统可以包括: 感光元件,用于采集被摄物体的感光数据; 微机电系统(MEMS),用于控制光敏元件在初始位置产生位移。 [0008]本申请实施例提出一种存储介质,当存储介质中存储的指令由移动终端的处理器执行时,使移动终端执行该移动终端的图像合成方法。 该图像合成方法可以包括: 当用户通过移动终端拍摄待拍摄对象时,根据移动终端中的感光元件的预设像素对待拍摄对象进行相位对焦。 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素,采集被摄物体的第一感光数据,并控制感光元件返回初始位置; 对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成被摄物体的图像。 [0009] 本公开的实施例的另外的方面和优点将部分地在以下描述中给出,部分地从以下描述变得显而易见,或者从本公开的实施例的实践中获知。 附图的简要说明 [0010] 为使本发明实施例的技术方案更加清楚明白,以下对实施例说明中需要用到的附图进行说明。 显然,以下所绘示的附图仅代表本发明的部分实施例,本领域普通技术人员在不付出创造性劳动的情况下,可以根据这些附图获得其他附图。 [0011] 图1为本发明实施例提供的一种移动终端的图像合成方法流程示意图。 [0012] 图2为本发明实施例的感光元件上的预设像素示意图。 [0013] 图3为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 [0014] 图4为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 [0015] 图5是示出根据本公开实施例的微机电系统(MEMS)的结构的俯视图。 [0016] 图6为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0017] 图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0018] 图8为本发明实施例提供的另一种微机电光学防抖系统的结构示意图。 [0019] 图9为本发明实施例的微机电光学防抖系统的结构俯视图。 [0020] 图10为本发明实施例提供的一种移动终端的图像合成装置的结构示意图。 详细说明 [0021] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。 显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0022]本发明的说明书、权利要求书和上述附图中的“第一”、“第二”、“第三”、“第四”等术语用于区分不同的对象,并不旨在描述特定的顺序。 此外,术语“包含”和“具有”及其变体旨在涵盖非排他性的“包含”。 例如,包括一系列步骤或单元的过程、方法、系统、术语或设备可以不限于列出的步骤或单元,替代地,可以包括未列出的其他步骤或单元 或这些过程、方法、术语或设备固有的其他步骤或单元可以包括在实施例中。 [0023] 图1为本发明实施例提供的一种移动终端的图像合成方法流程示意图。 本实施例以移动终端的图像合成装置配置移动终端的图像合成方法为例。 本发明实施例可以应用于用户在移动终端对拍摄对象进行分段的过程中。 [0024] 参考图1,移动终端的图像合成方法可以包括以下内容。 [0025] 在 S 区 11 ,当用户通过移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 [0026] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0027] 在本发明实施例中,待拍摄对象可以是用户通过移动终端拍摄的场景、人物、事物等。 [0028] 在本发明实施例中,预设像素为掩蔽像素,预设像素成对设置。 [0029] 在一个实施例中,当用户使用移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 也就是说,通过在感光元件上保留一些被掩蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定聚焦偏移值,从而实现相位聚焦。 [0030] 请参阅图2,图2为本发明实施例提供的感光元件上预设像素的示意图。 例如,图2中标有字母的像素可以是预设像素,预设像素是成对设置的。 例如,可以将预设像素A、B、C、D、E、F、G、H、I、J标记为预设像素对A和B、预设像素对C和D、预设像素对E F、预设像素对G和H,以及预设像素对I和J。 [0031] 在 S 区 12 ,控制光敏元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0032] 在本发明的实施例中,可以通过微机电光学图像稳定系统控制光敏元件在初始位置产生位移。 [0033] 在本发明实施例中,所述初始位置为在移动终端中根据预先设置的感光元件的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块 S 11 . [0034] 在本发明实施例中,原始像素例如可以是在移动终端中的感光元件上没有预留掩蔽像素时的默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0035]在一个实施例中,可以通过微机电光学图像稳定系统控制光敏元件的移动,使得光敏元件在初始位置产生位移,以将被掩蔽的像素替换为原始像素以获得替换像素。 [0036] 作为示例,参见图2,图2中标有字母的像素为掩蔽像素,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到替换后的像素。 换言之,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,从而使得在彩色滤光片阵列前后对应相同滤光片位置的感光像素 移动不同,移动前的那些预设像素(保留的掩码像素)的位置被移动后的原始像素(默认像素)替换。 [0037] 在 S 区 13 ,首先根据替换的像素采集被摄物体的感光数据,并控制感光元件返回初始位置。 [0038] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据置换后的像素对被摄物体进行拍摄时采集的感光数据。 [0039] 在本发明实施例中,在采集到第一感光数据后,可以根据预设像素控制感光元件返回初始位置对被摄体进行拍摄。 [0040] 在 S 区 14 ,对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据。 [0041] 在本发明实施例中,当控制感光元件返回初始位置时,根据预设像素对被摄物体进行拍摄,从而使感光元件采集被摄物体的感光数据。 初始位置作为第二感光数据。 [0042] 在本发明实施例中,由于光敏元件在初始位置产生位移,因此使用原始像素替换光敏元件上的掩蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以基于第一拍照数据对第二拍照数据进行补偿,以补偿被掩蔽的像素。 [0043] 在 S 区 15 ,根据第一感光数据和第二感光数据合成被摄物体的图像。 [0044] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,以根据补偿后的第二感光数据合成被摄体的图像。 [0045] 在本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换的像素采集被摄体的第一感光数据,控制感光元件返回初始位置,可以对被摄体进行拍摄,使感光元件采集第二次感光 被摄物体在初始位置的数据。 根据第一感光数据和第二感光数据合成被摄物体的图像。 因此,可以有效提高相位聚焦的精度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0046]图3为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 [0047] 参考图3,微机电光学图像稳定系统可以包括感光元件 100 和微机电系统(MEMS) 200 . 感光元件 100 用于采集被摄物体的感光数据。 微机电系统 200 耦接至感光元件并用以控制感光元件 100 在初始位置产生位移。 [0048] 在本发明的实施例中,微机电光学影像稳定系统可包括感光元件 100 . [0049] 感光元件 100 用于采集被摄物体的感光数据。 [0050] 在一个实施例中,在光敏元件上设置掩蔽像素 100 ,其中被掩蔽的像素用于对被摄体进行相位对焦。 [0051] 在一个实施例中,当用户使用移动终端拍摄被摄体时,可以根据感光元件上的预设像素对被摄体进行相位对焦。 100 在移动端。 也就是说,通过在感光元件上保留一些被掩蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定聚焦偏移值,从而实现相位聚焦。 [0052] 在本公开的实施例中,微机电光学图像稳定系统还可以包括MEMS 200 . [0053] 微机电系统 200 耦接至感光元件并用以控制感光元件 100 在初始位置产生位移。 [0054] 在本发明实施例中,初始位置为移动终端中感光元件在遮挡作用下的预设像素,对被摄体进行相位对焦时移动终端中感光元件的位置。 小号 11 在图1所示的实施例中。 [0055] 在一个实施例中,光敏元件 100 和 MEMS 200 使用板上芯片技术和点胶方法进行耦合。 [0056] 在本公开的实施例中,MEMS 200 可用于承载感光元件 100 , 和感光元件 100 可以在空间直角坐标系的三轴方向上移动,以在使用移动终端拍照的过程中提供防抖功能。 [0057] 作为示例,请参阅图4,图4为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 该系统可以包括:感光元件 41 , 一种微机电系统 (MEMS) 42 , 和胶水 43 , 其中感光元件 41 和 MEMS 42 使用板上芯片技术和点胶方法进行耦合。 感光元件 41 可以由 MEMS 控制移动 42 . [0058] 请参阅图5,图5是微机电系统(MEMS)结构的俯视图 200 根据本公开的一个实施例。 微机电系统 200 可以向上和向下、向左和向右平移,并且可以旋转一个角度。 例如,当 MEMS 200 需要上下移动,模块 1 和模块 4 采取措施使 MEMS 200 上下移动; 当 MEMS 200 需要左右移动,模块 2 或模块 3 采取措施使 MEMS 200 向左或向右移动; 当 MEMS 200 需要顺时针旋转,模块 1 向上移动,模块 2向右移动,模块 4 向下移动,模块 3 向左移动,这样 MEMS 200 顺时针旋转; 同样,当 MEMS 200 需要逆时针旋转,模块 1 向下移动,模块 2 向左移动,模块 4 向上移动,模块 3 向右移动。 [0059] 根据实际需要,MEMS中空间直角坐标系三轴方向的运动 200 (即水平面两个正交方向的平移运动,以及绕垂直于水平面的轴的旋转运动)可以通过控制模块来实现 1 , 模块 2 , 模块 3 , 和/或模块 4 , 这样 MEMS 200 可拉光敏元件 100 在移动终端拍照过程中,在初始位置产生位移,以补偿被掩蔽的像素。 [0060] 在一个实施例中,在一些实施例中,参见图6,该微机电光学防抖系统还可以包括:印刷电路板(PCB) 300 . [0061] 在本公开的实施例中,微机电光学图像稳定系统还可以包括印刷电路板(PCB) 300 耦合到 MEMS 200 . [0062] 在一个实施例中,PCB 300 和 MEMS 200 使用板上芯片技术和点胶方法进行耦合。 [0063] 在一个实施例中,PCB 300 用于承载 MEMS 的重量 200 和感光元件 100 并用于路由。 [0064] 作为示例,请参阅图7,图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 该系统可以包括:微机电系统(MEMS) 71 ,印刷电路板(PCB) 72 , 和胶水 73 ,赢哪的MEMS 71 耦合到PCB 72 使用板上芯片技术和点胶方法。 [0065] 作为示例,请参阅图8,图8为本发明实施例提供的另一种微机电光学防抖系统的结构示意图。 该系统可以包括:感光元件 81 , 一种微机电系统 (MEMS) 82 ,印刷电路板(PCB) 83 , 胶水 84 , 一根硅线 85 和一根金线 86 , 其中硅线 85 被配置为承载 MEMS 的移动部分的重量 82 , 硅丝外侧 85 镀金同时产生导电性,而硅线 85 用于传输光敏元件的信号 81 并为 MEMS 供电 82 . 金线 86 用于传输光敏元件的信号 81 并为感光元件供电 81 . [0066] 作为示例,请参阅图9,图9为本发明实施例提供的一种微机电光学防抖系统的结构俯视图。 该系统可以包括:感光元件 91 , 一种微机电系统 (MEMS) 92 , 一根硅线 93 和一根金线 94 . [0067] 在本实施例中,印刷电路板(PCB)与MEMS耦合,使得PCB可以承载MEMS和感光元件的重量,并可以为微机电光学防抖系统供电,以保证正常工作。 微机电光学图像稳定系统的操作。 [0068]在本实施例中,可以通过光敏元件采集被摄体的光敏数据,MEMS可以控制光敏元件在初始位置产生位移。 因此,可以有效提高相位聚焦的精度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0069] 图10为本发明实施例提供的一种移动终端的图像合成装置的结构示意图。 图像合成装置 100 移动终端的实现可以通过软件、硬件或者两者的结合来实现。 图像合成装置 100 所述移动终端可以包括:处理模块 101 , 一个控制模块 102 , 采集模块 103 , 拍照模块 104 , 和一个合成模块 105 . [0070] 处理模块 101 用于当用户通过移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 [0071] 在一个实施例中,预设像素是掩蔽像素。 [0072] 控制模块 102 用于控制光敏元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0073] 在一个实施例中,控制模块 102 还用于通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0074] 采集模块 103 用于根据替换像素采集被摄物体的第一感光数据,并控制感光元件返回初始位置。 [0075] 拍照模块 104 用于对被摄体进行拍照,使感光元件在初始位置采集被摄体的第二感光数据。 [0076] 合成模块 105 用于根据第一感光数据和第二感光数据合成被摄物体的图像。 [0077] 在一个实施例中,合成模块 105 还用于: 将所述第二感光数据与所述第一感光数据进行补偿处理, 以根据所述补偿处理后的所述第二感光数据合成所述被摄体的图像。 [0078] 需要说明的是,上述图1-2实施例中对移动终端图像合成方法实施例的描述同样适用于移动终端图像合成装置。 其实现原理类似,在此不再赘述。 [0079] 在本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素采集被摄体的第一感光数据,控制感光元件返回初始位置,可以对被摄体进行拍摄,使感光元件采集第二次感光 被摄物体在初始位置的数据。 根据第一感光数据和第二感光数据合成被摄物体的图像。 因此,可以有效提高相位聚焦的准确度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0080]本发明实施例还提供了一种移动终端。 移动终端可以包括外壳、处理器、存储器、电路板和电源电路,其中电路板设置在外壳围成的空间内,处理器和存储器设置在电路板上, 供电电路用于为移动终端的电路或部件供电, 存储器用于存储可执行程序代码, 处理器用于通过读取存储在 执行以下操作的内存。 [0081] 在 S 区 11 ':用户在使用移动终端拍摄待摄物时,根据移动终端中感光元件的预设像素对待摄物进行相位对焦。 [0082] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0083] 在本发明实施例中,待拍摄对象可以是用户通过移动终端拍摄的场景、人物、事物等。 [0084] 在本发明实施例中,预设像素为掩蔽像素,预设像素成对设置。 [0085] 在一个实施例中,当用户使用移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 也就是说,通过在感光元件上保留一些被掩蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定聚焦偏移值,从而实现相位聚焦。 [0086] 请参阅图2,图2为本发明实施例提供的感光元件上预设像素的示意图。 例如,图2中标有字母的像素可以是预设像素,预设像素是成对设置的。 例如,可以将预设像素A、B、C、D、E、F、G、H、I、J标记为预设像素对A和B、预设像素对C和D、预设像素对E F、预设像素对G和H,以及预设像素对I和J。 [0087] 在 S 区 12 ',控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0088] 在本发明的实施例中,可以通过微机电光学图像稳定系统控制光敏元件在初始位置产生位移。 [0089] 在本发明实施例中,所述初始位置为在移动终端中根据预先设置的感光元件的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块 S 11 '。 [0090] 在本发明实施例中,原始像素例如可以是在移动终端中的感光元件上没有预留掩蔽像素时的默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0091] 在一个实施例中,可以通过微机电光学图像稳定系统控制光敏元件的移动,使得光敏元件在初始位置产生位移,以将被掩蔽的像素替换为原始像素以获得替换像素。 [0092]作为示例,参见图2,图2中标有字母的像素为掩蔽像素,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到替换后的像素。 换言之,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,从而使得在彩色滤光片阵列前后对应相同滤光片位置的感光像素 移动不同,移动前的那些预设像素(保留的掩码像素)的位置被移动后的原始像素(默认像素)替换。 [0093] 在 S 区 13 ',根据置换后的像素采集被摄物体的第一感光数据,并控制感光元件返回初始位置。 [0094] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据置换后的像素对被摄物体进行拍摄时采集的感光数据。 [0095] 在本发明实施例中,在采集到第一感光数据后,可以根据预设像素控制感光元件返回初始位置对被摄体进行拍摄。 [0096] 在 S 区 14 ',对被摄体进行拍照,使感光元件在初始位置采集被摄体的第二感光数据。 [0097] 在本发明实施例中,当控制感光元件返回初始位置时,根据预设像素对被摄物体进行拍摄,从而使感光元件采集被摄物体的感光数据。 初始位置作为第二感光数据。 [0098] 在本发明实施例中,由于光敏元件在初始位置产生位移,因此使用原始像素替换光敏元件上的掩蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以基于第一拍照数据对第二拍照数据进行补偿,以补偿被掩蔽的像素。 [0099] 在 S 区 15 ',根据第一感光数据和第二感光数据合成被摄物体的图像。 [0100] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,以根据补偿后的第二感光数据合成被摄体的图像。 [0101] 在本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换的像素采集被摄体的第一感光数据,控制感光元件返回初始位置,可以对被摄体进行拍摄,使感光元件采集第二次感光 被摄物体在初始位置的数据。 根据第一感光数据和第二感光数据合成被摄物体的图像。 因此,可以有效提高相位聚焦的精度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0102]装置的上述实施例是示例性的。 被描述为独立组件的单元可能在物理上是分开的,也可能不是。 显示为单元的组件可以是也可以不是物理单元,换言之,可以集成在一个位置或分布到多个网络单元。 可以根据实际需要选择其中的部分或者全部模块来实现本实施例方案的目的。 本领域技术人员无需做出创造性劳动即可理解并实施本发明。 [0103] 本发明实施例方法中的步骤可以根据实际需要依次调整、合并、删除。 [0104] 本发明实施例装置中的模块或单元可以根据实际需要进行组合、划分和删除。 [0105] 本发明实施例的模块或模块可以由通用集成电路(例如中央处理器CPU)或专用集成电路(ASIC)来实现。 [0106] 通过以上实施例的描述,本领域技术人员可以清楚地了解到,各种实现方式可以通过软件加必要的通用硬件平台的方式来实现,当然也可以通过硬件来实现。 基于这样的理解,上述技术方案本质上可以体现为软件产品的形式,也可以体现为软件产品的形式,可以存储在ROM/RAM、磁盘、光驱等计算机可读存储介质中。 盘等,并且包括用于使计算机设备(其可以是个人计算机、服务器或网络设备等)执行在各个实施例或实施例的部分中描述的方法的指令。 [0107] 上述实施例不构成对技术方案范围的限制。 凡在上述实施例的精神和原则之内所作的任何修改、等同替换、改进等,均应包含在本技术方案的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10554877B2(String), US20190141257A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: US10554877B2(String), US20190141257A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10554877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), US10554877B2(String), US20190141257A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270708(Integer), US10554877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270708(Integer), US20190141257A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.570 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10554877B2(String), US10554877B2(String), 1580745600(Integer), 270708(Integer), 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.581 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185033(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 1(Integer), 185033(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.595 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185033(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.597 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 2(Integer), 185033(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.607 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.608 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.609 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.619 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.620 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.621 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185033(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10848678B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.632 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10848678B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/302323(String), 1496937600(Integer), US10848678B2(String), 1606147200(Integer), 1606147200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 23(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2011075677A | JP2012208876A | US10554877B2 | US20110013061A1 | US20130156345A1 | US20140354833A1 | US20150109513A1 | US20150212336A1 | US20150229843A1 | WO2014003492A1 | WO2014014222A1 | WO2014097792A1 | WO2016099128A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185034(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.643 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.644 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.645 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\df8c245d822c4e20a2c86e53e4803c1c.png(String), 185034(Integer), df8c245d822c4e20a2c86e53e4803c1c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10848678B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/302323(String), 1496937600(Integer), US10848678B2(String), 1606147200(Integer), 1606147200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 23(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2011075677A | JP2012208876A | US10554877B2 | US20110013061A1 | US20130156345A1 | US20140354833A1 | US20150109513A1 | US20150212336A1 | US20150229843A1 | WO2014003492A1 | WO2014014222A1 | WO2014097792A1 | WO2016099128A1(String), \20230420\df8c245d822c4e20a2c86e53e4803c1c.png(String), 20(Integer), 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.666 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.667 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 1. An image synthesis method for a mobile terminal, comprising:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location, wherein the photosensitive element is controlled to generate the displacement at the initial location and to return to the initial location by at least two modules configured in the mobile terminal collaboratively, wherein the photosensitive element is controlled to be moved upwards and downwards by a first module and a fourth module, to be moved left and right by a second module and a third module, and to be rotated with an angle by the first module, the second module, the third module and the fourth module;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data.(String), 1.根据权利要求10所述的移动终端,其中处理器还被配置为:通过微机电光学稳像系统控制感光元件在初始位置产生位移。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 2. The image synthesis method according to claim 1, controlling the photosensitive element to generate the displacement at the initial location comprising:controlling, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location.(String), 12.根据权利要求10所述的移动终端,其中处理器还被配置为:将第二感光数据与第一感光数据进行补偿处理,根据补偿处理后的第二感光数据合成被摄体的图像。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 3. The image synthesis method according to claim 1, synthesizing the image of the object to be photographed according to the first photosensitive data and the second photosensitive data comprising:performing a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 13.根据权利要求10所述的移动终端,其中预设像素为屏蔽像素。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 4. The image synthesis method according to claim 1, wherein the preset pixel is a masked pixel.(String), 14.根据权利要求2所述的图像合成方法,其特征在于,所述微机电光学稳像系统控制所述感光元件在所述初始位置产生位移。包括:微机电光学稳像系统通过空间直角坐标系三轴方向的运动控制感光元件在初始位置产生位移,三轴方向的运动包括两个方向的平移运动水平面中的正交方向和绕垂直于水平面的轴的旋转运动。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 5. A micro-electromechanical optical image stabilization system, comprising:a photosensitive element, configured to collect photosensitive data of an object to be photographed; anda micro-electromechanical system coupled to the photosensitive element, configured to control the photosensitive element to generate a displacement at an initial position and to return to the initial location by at least two modules configured in the micro-electromechanical optical image stabilization system collaboratively, wherein the photosensitive element is controlled to be moved upwards and downwards by a first module and a fourth module, to be moved left and right by a second module and a third module, and to be rotated with an angle by the first module, the second module, the third module and the fourth module.(String), 15.根据权利要求14所述的图像合成方法,其中微机电光学防抖系统包括具有第一模块、第二模块、第三模块和第四模块的微机电系统,以及在进行旋转运动时,该方法包括以下至少之一:控制第一模块向上运动,第二模块向右运动,第三模块向左运动,第四模块向下运动,使微机电系统顺时针旋转;和控制第一模块向下运动,第二模块向左运动,第三模块向右运动,第四模块向上运动,使微机电系统逆时针旋转;和在执行平移动作时,该方法包括以下至少之一:控制第一模块和第四模块动作使微机电系统上下运动;和控制第二模块和第三模块采取动作使微机电系统左右移动。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 6. The micro-electromechanical optical image stabilization system according to claim 5, further comprising:a printed circuit board coupled to the micro-electromechanical system.(String), 16.根据权利要求1所述的图像合成方法,其中初始位置为根据移动终端中的感光元件的预设像素对被摄体进行相位对焦时移动终端中的感光元件的位置,原始像素为默认像素,其中a移动终端中的光敏元件上没有保留被遮蔽的像素。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 7. The micro-electromechanical optical image stabilization system according to claim 5, wherein the photosensitive element and the micro-electromechanical system are coupled using a chip-on-board technology and a dispensing method.(String), 17.根据权利要求5所述的微机电光学防抖系统,其中微机电系统被配置为通过执行以下动作来控制光敏元件在初始位置产生位移:通过空间直角坐标系三轴方向的运动控制感光元件在初始位置产生位移,三轴方向的运动包括水平面内两个正交方向的平移运动和围绕其旋转运动垂直于水平面的轴。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 8. The micro-electromechanical optical image stabilization system according to claim 6, wherein the printed circuit board and the micro-electromechanical system are coupled using a chip-on-board technology and a dispensing method.(String), 18.根据权利要求17所述的微机电光学防抖系统,其中微机电光学防抖系统包括具有第一模块、第二模块、第三模块和第四模块的微机电系统,以及当进行旋转运动时,微机电光学防抖系统被配置为进行以下至少之一:控制第一模块向上运动,第二模块向右运动,第三模块向左运动,第四模块向下运动,使微机电系统顺时针旋转;和控制第一模块向下运动,第二模块向左运动,第三模块向右运动,第四模块向上运动,使微机电系统逆时针旋转;和当执行平移运动时,微机电光学图像稳定系统被配置为执行以下至少之一:控制第一模块和第四模块动作使微机电系统上下运动;和控制第二模块和第三模块采取动作使微机电系统左右移动。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 9. The micro-electromechanical optical image stabilization system according to claim 7, wherein a masked pixel is set on the photosensitive element, and the masked pixel is configured to perform a phase focusing on the object to be photographed.(String), 19.根据权利要求5所述的微机电光学防抖系统,还包括:硅线,用于承载微机电系统运动部分的重量,传输光敏元件的信号,为微机电系统供电;和金线,用于传输光敏元件的信号并为光敏元件供电。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.668 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 10. A mobile terminal, comprising: a housing, a processor, a memory, a circuit board and a power supply circuit, wherein,the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location, wherein the photosensitive element is controlled to generate the displacement at the initial location and to return to the initial location by at least two modules configured in the mobile terminal collaboratively, wherein the photosensitive element is controlled to be moved upwards and downwards by a first module and a fourth module, to be moved left and right by a second module and a third module, and to be rotated with an angle by the first module, the second module, the third module and the fourth module;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data.(String), 20.如权利要求6所述的微机电光学防抖系统,其特征在于,所述印刷电路板用于承载所述微机电系统和所述感光元件的重量,所述印刷电路板还用于走线。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 11. The mobile terminal according to claim 10, wherein the processor is further configured to:control the photosensitive element to generate the displacement at the initial location by a micro-electromechanical optical image stabilization system.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 12. The mobile terminal according to claim 10, wherein the processor is further configured to:perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 13. The mobile terminal according to claim 10, wherein the preset pixel is a masked pixel.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 14. The image synthesis method according to claim 2, controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location comprising:controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 1(Integer), 13(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.669 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 15. The image synthesis method according to claim 14, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having the first module, the second module, the third module and the fourth module, andwhen performing the rotating movement, the method comprises at least one of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the method comprises at least one of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 16. The image synthesis method according to claim 1, wherein the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal, and the original pixel is a default pixel where a masked pixel is not reserved on the photosensitive element in the mobile terminal.(String), 1(Integer), 15(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 17. The micro-electromechanical optical image stabilization system according to claim 5, wherein the micro-electromechanical system is configured to control the photosensitive element to generate the displacement at the initial position by performing an act of:controlling the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 1(Integer), 16(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 18. The micro-electromechanical optical image stabilization system according to claim 17, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having the first module, the second module, the third module and the fourth module, andwhen performing the rotating movement, the micro-electromechanical optical image stabilization system is configured to perform at least one of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the micro-electromechanical optical image stabilization system is configured to perform at least one of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 19. The micro-electromechanical optical image stabilization system according to claim 5, further comprising:a silicon wire, configured to carry a weight of a moving portion of the micro-electromechanical system, and to transmit a signal of the photosensitive element and to supply power to the micro-electromechanical system; anda gold wire, configured to transmit the signal of the photosensitive element and to supply power to the photosensitive element.(String), 1(Integer), 18(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.670 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185034(Integer), 20. The micro-electromechanical optical image stabilization system according to claim 6, the printed circuit board being configured to carry weights of the micro-electromechanical system and the photosensitive element, the printed circuit board being further configured for routing.(String), 1(Integer), 19(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.832 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.833 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185034(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The present application is a U.S. national phase application of International Application No. PCT/CN2017/087806, filed on Jun. 9, 2017, which claims priority from Chinese Patent Application No. “201610616090.6” filed on Jul. 29, 2016 by GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD., entitled “Image Synthesis Method and Device for Mobile Terminal, and Mobile Terminal”. TECHNICAL FIELD [0002]The present disclosure relates to a field of mobile terminal technology, and in particular, to an image synthesis method and apparatus for a mobile terminal, and a mobile terminal. BACKGROUND [0003]Optical Image Stabilization (OIS) may effectively avoid image blur caused by jitter during a process of the user taking pictures with a mobile terminal. OIS uses a magnetically wrapped suspension lens to effectively overcome image blur caused by vibration of the mobile terminal. In the related art, the anti-shake is realized by a photosensitive element, of which the principles may be described as followings. The photosensitive element is fixed on a bracket that can move up, down, left, and right, and the direction and amplitude data of the shaking of the mobile terminal are sensed by a gyro sensor. After that, the gyro sensor transmits the data. Screening and amplification are performed on the data at the processor side to calculate the amount of movement of the photosensitive element that may compensate the jitter. During the process of the user taking pictures with the mobile terminal, it is also necessary to perform phase focusing on the scene to be photographed. In the related art, by hiding some masked pixels on the photosensitive element, and considering the distance between the pixels of the scene to be photographed and its changing factors, the focusing offset value may be determined to achieve the phase focusing. [0004]In this way, the masked pixels may only be used to detect the phase and cannot be used to display the image. The masked pixels may affect the quality of the image photographed. The higher the density of the masked pixels, the more accurate the phase focusing, but the worse the quality of the image photographed. SUMMARY [0005]The present disclosure aims to solve at least one of technical problems in the related art to some extent. [0006]Embodiments of the present disclosure provide an image synthesis method for the mobile terminal. The method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0007]Embodiments of the present disclosure also provide a micro-electromechanical optical image stabilization system. The system may include: a photosensitive element, configured to collect photosensitive data of an object to be photographed; and a micro-electromechanical system (MEMS), configured to control the photosensitive element to generate a displacement at an initial position. [0008]Embodiments of the present application propose a storage medium, when instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform an image synthesis method for the mobile terminal. The image synthesis method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0009]Additional aspects and advantages of embodiments of present disclosure will be given in part in the following descriptions, become apparent in part from the following descriptions, or be learned from the practice of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to make technical solutions according to embodiments of the present disclosure more apparent, drawings needed to be used in descriptions of the embodiments will be illustrated in the following. Obviously, the drawings to be illustrated in the following only represent some embodiments of the present disclosure, and other drawings can be obtained according these drawings by those having ordinary skills in the related art without making creative labors. [0011]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a schematic diagram of preset pixels on a photosensitive element in an embodiment of the present disclosure. [0013]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0014]FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0015]FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) according to an embodiment of the present disclosure. [0016]FIG. 6 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0017]FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0018]FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0019]FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0020]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0021]The technical solutions in embodiments of the present disclosure are hereinafter described clearly and completely with reference to accompanying drawings in embodiments of the present disclosure. Apparently, embodiments described are a part of embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments in the present disclosure without creative labor shall fall in the protection scope of the present disclosure. [0022]The terms “first”, “second”, “third” and “fourth” and the like in the specification and claims of the present disclosure and the above drawings are used to distinguish different objects, and are not intended to describe a specific order. Moreover, the terms “comprise” and “have” and their variants are aim at covering non-exclusive “include”. For example, a process, a method, a system, a term or a device including a series of steps or units may be not limited to the listed steps or units, instead and alternatively, other steps or units which are not listed may be included, or other steps or units inherent for these process, method, term or device may be included in an embodiment. [0023]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. This embodiment takes an example where an image synthesis method for the mobile terminal is configured for an image synthesis apparatus for the mobile terminal. Embodiments of the present disclosure may be applied during a process of a user paragraphing a subject to be photographed using the mobile terminal. [0024]Referring to FIG. 1, the image synthesis method of the mobile terminal may include followings. [0025]At block S11, a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0026]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0027]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0028]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0029]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0030]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0031]At block S12, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0032]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0033]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11. [0034]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0035]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0036]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0037]At block S13, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0038]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0039]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be controlled to return to the initial position to photograph the object to be photographed based on the preset pixel. [0040]At block S14, the object to be photographed is photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. [0041]In embodiments of the present disclosure, when the photosensitive element is controlled to return to the initial position, the object to be photographed is photographed based on the preset pixel, such that the photosensitive element collects the photosensitive data of the object to be photographed at the initial position as the second photosensitive data. [0042]In embodiments of the present disclosure, since the photosensitive element generates the displacement at the initial position, the original pixel is used to replace the masked pixel on the photosensitive element, and the obtained replaced pixel is the original pixel. Therefore, the mobile terminal may perform a compensation on the second photographic data based on the first photographic data so as to compensate for the masked pixel. [0043]At block S15, an image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. [0044]In embodiments of the present disclosure, the second photosensitive data are subjected to compensation processing using the first photosensitive data to synthesize an image of the object to be photographed according to the compensated second photosensitive data. [0045]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0046]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0047]Referring to FIG. 3, the micro-electromechanical optical image stabilization system may include a photosensitive element 100 and a micro-electromechanical system (MEMS) 200. The photosensitive element 100 is configured to collect photosensitive data of an object to be photographed. The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate a displacement at an initial position. [0048]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may include the photosensitive element 100. [0049]The photosensitive element 100 is configured to collect photosensitive data of the object to be photographed. [0050]In an embodiment, a masked pixel is set on the photosensitive element 100, in which the masked pixel is used to perform a phase focusing on the object to be photographed. [0051]In an embodiment, when the user uses the mobile terminal to photograph the object to be photographed, the phase focusing may be performed on the object to be photographed based on the preset pixel on the photosensitive element 100 in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0052]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may also include the MEMS 200. [0053]The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate the displacement at the initial position. [0054]In embodiments of the present disclosure, the initial position is the position of the photosensitive element in the mobile terminal when the phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal in act of block S11 in the embodiment shown in FIG. 1. [0055]In an embodiment, the photosensitive element 100 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0056]In embodiments of the present disclosure, the MEMS 200 may be used to carry the photosensitive element 100, and the photosensitive element 100 may be moved in a three-axis direction of the space rectangular coordinate system to provide an anti-shake function during the process of photographing with the mobile terminal. [0057]As an example, referring to FIG. 4, FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 41, a micro-electromechanical system (MEMS) 42, and a glue 43, in which the photosensitive element 41 and the MEMS 42 are coupled using a chip-on-board technology and a dispensing method. The photosensitive element 42 may be controlled to move by the MEMS 42. [0058]Referring to FIG. 5, FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) 200 according to an embodiment of the present disclosure. The MEMS 200 may be translated upwards and downwards, left and right, and may be rotated with an angle. For example, when the MEMS 200 needs to move upwards and downwards, module 1 and module 4 take actions to cause the MEMS 200 to move upwards and downwards; when the MEMS 200 needs to move to the left and right, module 2 or module 3 take actions to cause the MEMS 200 to move to the left or right; when the MEMS 200 needs to rotate clockwise, the module 1 moves upwards, the module 2 moves to the right, the module 4 moves downwards, and the module 3 moves to the left, such that MEMS 200 rotates clockwise; similarly, when the MEMS 200 needs to rotate counterclockwise, the module 1 moves downwards, the module 2 moves to the left, the module 4 moves upwards, and the module 3 moves to the right. [0059]According to actual needs, the movements in three-axis directions of the space rectangular coordinate system in the MEMS 200 (i.e., translating movements in two orthogonal directions in the horizontal plane, and a rotating movement around the axis perpendicular to the horizontal plane) may be realized by controlling the module 1, the module 2, the module 3, and/or the module 4, such that the MEMS 200 may pulls the photosensitive element 100 to generate the displacement at the initial position to compensate for the masked pixels during the process of photographing with the mobile terminal. [0060]In an embodiment, in some embodiments, referring to FIG. 6, the micro-electromechanical optical image stabilization system may also include: a printed circuit board (PCB) 300. [0061]In embodiments of the present disclosure, the micro-electromechanical optical image stabilization system may also include the printed circuit board (PCB) 300 coupled to the MEMS 200. [0062]In an embodiment, the PCB 300 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0063]In an embodiment, the PCB 300 is used to carry the weight of the MEMS 200 and the photosensitive element 100 and is used for routing. [0064]As an example, referring to FIG. 7, FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. The system may include: a micro-electromechanical system (MEMS) 71, a printed circuit board (PCB) 72, and a glue 73, in which the MEMS 71 is coupled to the PCB 72 using a chip-on-board technology and a dispensing method. [0065]As an example, referring to FIG. 8, FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 81, a micro-electromechanical system (MEMS) 82, a printed circuit board (PCB) 83, a glue 84, a silicon wire 85 and a gold wire 86, in which the silicon wire 85 is configured to carry the weight of the moving portion of the MEMS 82, the outer side of the silicon wire 85 is gold plated to generate electrical conductivity at the same time, and the silicon wire 85 is configured to transmit signals of the photosensitive element 81 and to supply power to the MEMS 82. The gold wire 86 is configured to transmit signals of the photosensitive element 81 and to supply power to the photosensitive element 81. [0066]As an example, referring to FIG. 9, FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 91, a micro-electromechanical system (MEMS) 92, a silicon wire 93 and a gold wire 94. [0067]In this embodiment, a printed circuit board (PCB) is coupled to the MEMS, such that the PCB may carry the weight of the MEMS and the photosensitive element, and may supply power to the micro-electromechanical optical image stabilization system to ensure a normal operation of the micro-electromechanical optical image stabilization system. [0068]In this embodiment, the photosensitive data of the object to be photographed may be collected by the photosensitive element, and the MEMS may control the photosensitive element to generate a displacement at the initial position. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0069]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. The image synthesis apparatus 100 of the mobile terminal may be implemented by software, hardware or a combination thereof. The image synthesis apparatus 100 of the mobile terminal may include: a processing module 101, a control module 102, a collecting module 103, a photographing module 104, and a synthesizing module 105. [0070]The processing module 101 is configured to perform a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0071]In an embodiment, the preset pixel is a masked pixel. [0072]The control module 102 is configured to control the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and to obtain a replaced pixel. [0073]In an embodiment, the control module 102 is also configured to: control, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial position. [0074]The collecting module 103 is configured to collect first photosensitive data of the object to be photographed based on the replaced pixel, and to control the photosensitive element to return to the initial location. [0075]The photographing module 104 is configured to photograph the object to be photographed, and to enable the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location. [0076]The synthesizing module 105 is configured to synthesize an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0077]In an embodiment, the synthesizing module 105 is also configured to: perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing. [0078]It should be noted that, the description of embodiments of the image synthesis method for the mobile terminal in the foregoing embodiments of FIGS. 1-2 is also applicable to the image synthesis apparatus for the mobile terminal. The implementation principles thereof are similar, which will not be described in detail herein. [0079]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0080]Embodiments of the disclosure also provide a mobile terminal. The mobile terminal may include a housing, a processor, a memory, a circuit board and a power supply circuit, in which the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute followings. [0081]At block S11′: a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0082]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0083]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0084]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0085]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0086]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, G, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0087]At block S12′, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0088]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0089]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11′. [0090]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0091]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0092]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0093]At block S13′, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0094]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0095]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be controlled to return to the initial position to photograph the object to be photographed based on the preset pixel. [0096]At block S14′, the object to be photographed is photographed, and the p(String), 相关申请的交叉引用 [0001] 本申请为国际申请号PCT/CN2017/087806于2017年6月9日提交的美国国家阶段申请,该申请要求广东OPPO于2016年7月29日提交的中国专利申请号“201610616090.6”的优先权 MOBILE TELECOMMUNICATIONS CORP., LTD., 题为“用于移动终端的图像合成方法和装置、以及移动终端”。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端图像合成方法、装置及移动终端。 背景 [0003] 光学图像稳定(OIS)可以有效避免用户在使用移动终端拍照的过程中由于抖动导致的图像模糊。 OIS采用磁悬浮悬浮镜头,有效克服移动终端震动带来的影像模糊。 在相关技术中,防抖是通过感光元件来实现的,其原理可以描述如下。 感光元件固定在可上下左右移动的支架上,通过陀螺仪传感器感知移动终端晃动的方向和幅度数据。 之后,陀螺仪传感器传输数据。 在处理器端对数据进行筛选放大,计算出可以补偿抖动的光敏元件的移动量。 用户在使用移动终端拍照的过程中,还需要对要拍摄的场景进行相位对焦。 相关技术中,可以通过在感光元件上隐藏一些被遮蔽的像素点,并考虑待拍摄场景的像素点之间的距离及其变化因素,确定对焦偏移值,从而实现相位对焦。 [0004] 这样,被遮蔽的像素点只能用于检测相位,不能用于显示图像。 被屏蔽的像素可能会影响所拍摄图像的质量。 被掩蔽像素的密度越高,相位聚焦越准确,但拍摄的图像质量越差。 概括 [0005] 本发明旨在在一定程度上解决相关技术中的至少一个技术问题。 [0006] 本发明实施例提供了一种移动终端的图像合成方法。 该方法可以包括:当用户使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据与第二感光数据合成待拍摄对象的图像。 [0007] 本发明实施例还提供一种微机电光学防抖系统。 该系统可以包括:感光元件,用于采集待拍摄物体的感光数据; 微机电系统(MEMS),用于控制感光元件在初始位置产生位移。 [0008]本发明实施例提出了一种存储介质,当移动终端的处理器执行该存储介质中存储的指令时,使移动终端执行用于移动终端的图像合成方法。 所述图像合成方法可以包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据与第二感光数据合成待拍摄对象的图像。 [0009] 本公开的实施例的其他方面和优点将部分地在下面的描述中给出,部分地从下面的描述中变得明显,或者从本公开的实施例的实践中获知。 附图的简要说明 [0010] 为使本发明实施例的技术方案更加清楚明白,下面对实施例的描述中需要用到的附图进行举例说明。 显然,下面所要说明的附图仅代表本发明的部分实施例,相关领域的普通技术人员在不付出创造性劳动的情况下,可以根据这些附图得到其他附图。 [0011] 图1为本发明实施例提供的一种移动终端图像合成方法的流程示意图。 [0012] 图2为本发明实施例中感光元件上预设像素的示意图。 [0013] 图3为本发明实施例的微机电光学防抖系统的结构示意图。 [0014] 图4为本发明实施例的微机电光学防抖系统的结构示意图。 [0015] 图5是示出根据本公开实施例的微机电系统(MEMS)的结构的俯视图。 [0016] 图6为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0017] 图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0018] 图8为本发明实施例提供的另一种微机电光学防抖系统的结构图。 [0019] 图9为本发明实施例的微机电光学防抖系统的结构俯视图。 [0020] 图10为本发明实施例提供的一种移动终端图像合成装置的结构示意图。 详细说明 [0021] 下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 显然,所描述的实施例都是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0022]本发明的说明书和权利要求书以及上述附图中的“第一”、“第二”、“第三”和“第四”等术语用于区分不同的对象,并不用于描述特定的顺序。 此外,术语“包含”和“具有”及其变体旨在涵盖非排他性的“包括”。 例如,包括一系列步骤或单元的过程、方法、系统、术语或装置可不限于所列步骤或单元,相反和备选地,可包括未列出的其他步骤或单元 或这些过程、方法、术语或设备固有的其他步骤或单元可以包括在一个实施例中。 [0023] 图1为本发明实施例提供的一种移动终端图像合成方法的流程示意图。 本实施例以移动终端图像合成装置配置移动终端图像合成方法为例。 本发明实施例可以应用在用户使用移动终端对被摄体进行分段的过程中。 [0024] 参考图1,移动终端的图像合成方法可以包括以下内容。 [0025] 在S座 11 用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 [0026] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0027] 在本发明实施例中,所述待拍摄对象可以是用户通过移动终端拍摄的景物、人物、事物等。 [0028] 在本发明实施例中,预设像素为屏蔽像素,预设像素成对设置。 [0029] 在一个实施例中,当用户使用移动终端对被摄体进行拍摄时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 也就是说,通过在感光元件上保留一些被遮蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定对焦偏移值,从而实现相位对焦。 [0030] 参见图2,图2为本发明实施例的感光元件上预设像素的示意图。 例如,图2中标有字母的像素点可以是预设像素点,预设像素点是成对设置的。 例如,预设像素A、B、C、D、E、F、H、I、J可以标记为预设像素对A和B、预设像素对C和D、预设像素对E和F ,预设像素对G和H,以及预设像素对I和J。 [0031] 在S座 12 ,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0032] 在本发明实施例中,可以通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0033] 在本发明实施例中,初始位置为移动终端中感光元件在动作时根据预设的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块S 11 . [0034] 在本发明实施例中,当移动终端中的感光元件上没有预留遮蔽像素时,原始像素例如可以是默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0035]在一个实施例中,可以通过微机电光学防抖系统控制感光元件的移动,使得感光元件在初始位置产生位移,用原始像素替换遮蔽像素,得到替换像素。 [0036] 举例来说,参见图2,图2中标有字母的像素点为被遮蔽的像素点,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到被替换的像素点。 换句话说,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,使得前后相同滤光片位置对应的感光像素。 运动不同,运动前那些预设像素(保留的屏蔽像素)的位置被运动后的原始像素(默认像素)替换。 [0037] 在S座 13 ,首先根据替换后的像素采集待摄物体的感光数据,控制感光元件返回初始位置。 [0038] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据替换后的像素对被摄体进行拍摄时采集的感光数据。 [0039] 在本发明实施例中,在采集到第一感光数据后,可以控制感光元件返回初始位置,以预设像素为基准对被摄体进行拍摄。 [0040] 在S座 14 ,对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据。 [0041] 在本发明实施例中,当控制感光元件返回初始位置时,以预设像素为基准对被摄体进行拍摄,使得感光元件在初始位置采集被摄体的感光数据。 初始位置作为第二感光数据。 [0042] 在本发明实施例中,由于感光元件在初始位置产生位移,因此使用原始像素替换感光元件上的遮蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以根据第一拍照数据对第二拍照数据进行补偿,以补偿被遮挡的像素点。 [0043] 在S座 15 之后,根据第一感光数据和第二感光数据合成被摄体的图像。 [0044] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,根据补偿后的第二感光数据合成被摄体的图像。 [0045] 本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素点采集被摄体的第一感光数据,控制感光元件回到初始位置,对被摄体进行拍摄,使感光元件采集第二感光数据。 待拍摄物体在初始位置的数据。 根据第一感光数据与第二感光数据合成待拍摄物的影像。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0046]图3为本发明实施例的微机电光学防抖系统的结构示意图。 [0047] 参见图3,微机电光学防抖系统可以包括光敏元件 100 和微机电系统(MEMS) 200 . 感光元件 100 用于采集被摄体的感光数据。 微机电系统 200 耦接感光元件,用以控制感光元件 100 在初始位置产生位移。 [0048] 在本发明的实施例中,微机电光学防抖系统可以包括光敏元件 100 . [0049] 感光元件 100 用于采集待拍摄物体的感光数据。 [0050] 在一个实施例中,所述感光元件上设置有遮蔽像素 100 ,其中被遮蔽的像素用于对被摄物体进行相位对焦。 [0051] 在一个实施例中,当用户使用移动终端对被摄体进行拍摄时,可以根据感光元件上的预设像素对被摄体进行相位对焦。 100 在移动端。 也就是说,通过在感光元件上保留一些被遮蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定对焦偏移值,从而实现相位对焦。 [0052] 在本发明实施例中,微机电光学防抖系统还可以包括MEMS 200 . [0053] 微机电系统 200 耦接感光元件,用以控制感光元件 100 在初始位置产生位移。 [0054] 在本发明实施例中,初始位置为根据移动终端中感光元件的预设像素对被摄体进行相位对焦时移动终端中感光元件的位置。 小号 11 在图1所示的实施例中。 [0055] 在一个实施例中,感光元件 100 和微机电系统 200 使用板上芯片技术和点胶方法耦合。 [0056] 在本公开的实施例中,MEMS 200 可用于承载感光元件 100 , 和感光元件 100 可以在空间直角坐标系的三轴方向上移动,以提供移动终端拍照过程中的防抖功能。 [0057] 作为示例,请参见图4,图4为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 该系统可能包括:光敏元件 41 , 微机电系统 (MEMS) 42 , 和胶水 43 , 其中光敏元件 41 和微机电系统 42 使用板上芯片技术和点胶方法耦合。 感光元件 42 可由 MEMS 控制移动 42 . [0058] 参见图5,图5是微机电系统(MEMS)的结构俯视图 200 根据本公开的实施例。 微机电系统 200 可以上下左右平移,也可以旋转一个角度。 例如,当 MEMS 200 需要上下移动,模块 1 和模块 4 采取措施导致 MEMS 200 向上和向下移动; 当MEMS 200 需要左右移动,模块 2 或模块 3 采取措施导致 MEMS 200 向左或向右移动; 当MEMS 200 需要顺时针旋转,模块 1 向上移动,模块 2向右移动,模块 4 向下移动,模块 3 向左移动,这样 MEMS 200 顺时针旋转; 同样,当 MEMS 200 需要逆时针旋转,模块 1 向下移动,模块 2 向左移动,模块 4 向上移动,模块 3 向右移动。 [0059] 根据实际需要,MEMS中空间直角坐标系的三轴方向运动 200 (即在水平面内两个正交方向的平移运动,以及绕垂直于水平面的轴的旋转运动)可以通过控制模块来实现 1 , 模块 2 , 模块 3 ,和/或模块 4 , 这样 MEMS 200 可拉光敏元件 100 在初始位置产生位移,以补偿移动端拍照过程中被遮挡的像素点。 [0060] 在一个实施例中,在一些实施例中,参见图6,该微机电光学防抖系统还可以包括:印刷电路板(PCB) 300 . [0061] 在本发明实施例中,微机电光学防抖系统还可以包括印刷电路板(PCB) 300 耦合到 MEMS 200 . [0062] 在一个实施例中,PCB 300 和微机电系统 200 使用板上芯片技术和点胶方法耦合。 [0063] 在一个实施例中,PCB 300 用于承载MEMS的重量 200 和感光元件 100 并用于路由。 [0064] 作为示例,请参见图7,图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 该系统可能包括:微机电系统(MEMS) 71 , 印刷电路板 (PCB) 72 , 和胶水 73 , 其中 MEMS 71 耦合到PCB 72 使用板上芯片技术和点胶方法。 [0065] 作为示例,请参见图8,图8为本发明实施例提供的另一种微机电光学防抖系统的结构图。 该系统可能包括:光敏元件 81 , 微机电系统 (MEMS) 82 , 印刷电路板 (PCB) 83 , 胶水 84 , 硅线 85 和一根金线 86 , 其中硅线 85 配置为承载 MEMS 移动部分的重量 82 , 硅线的外侧 85 镀金同时产生导电性,硅线 85 用于传输光敏元件的信号 81 并为 MEMS 供电 82 . 金线 86 用于传输光敏元件的信号 81 并给光敏元件供电 81 . [0066] 作为示例,请参阅图9,图9为本发明实施例的微机电光学防抖系统的结构俯视图。 该系统可能包括:光敏元件 91 , 微机电系统 (MEMS) 92 , 硅线 93 和一根金线 94 . [0067] 在本实施例中,印刷电路板(PCB)耦合到MEMS,使得PCB可以承载MEMS和感光元件的重量,并且可以为微机电光学防抖系统供电以保证正常的正常工作。 微机电光学图像稳定系统的操作。 [0068]本实施例中,可以通过感光元件采集被摄体的感光数据,MEMS可以控制感光元件在初始位置产生位移。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0069] 图10为本发明实施例提供的一种移动终端图像合成装置的结构示意图。 图像合成装置 100 移动终端的功能可以通过软件、硬件或其组合来实现。 图像合成装置 100 移动终端的组成部分可以包括:处理模块 101 , 一个控制模块 102 , 采集模块 103 , 拍照模块 104 , 和一个合成模块 105 . [0070] 处理模块 101 用于在用户使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 [0071] 在一个实施例中,预设像素为掩蔽像素。 [0072] 控制模块 102 用于控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0073] 在一个实施例中,控制模块 102 还用于: 通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0074] 采集模块 103 用于根据替换后的像素采集待摄对象的第一感光数据,并控制感光元件返回初始位置。 [0075] 拍照模块 104 用于对所述被摄体进行拍摄,使所述感光元件在所述初始位置采集所述被摄体的第二感光数据。 [0076] 合成模块 105 用于根据第一感光数据和第二感光数据合成被摄体的图像。 [0077] 在一个实施例中,合成模块 105 还用于: 将第二感光数据与第一感光数据进行补偿处理,根据补偿处理后的第二感光数据合成被摄体的图像。 [0078] 需要说明的是,上述图1-2实施例中对移动终端图像合成方法实施例的描述同样适用于移动终端图像合成装置。 其实现原理类似,在此不再赘述。 [0079] 本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素点采集被摄体的第一感光数据,控制感光元件回到初始位置,对被摄体进行拍摄,使感光元件采集第二感光数据。 待拍摄物体在初始位置的数据。 根据第一感光数据与第二感光数据合成待拍摄物的影像。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0080]本发明实施例还提供了一种移动终端。 该移动终端可以包括壳体、处理器、存储器、电路板和供电电路,其中,电路板设置在壳体围成的空间内,处理器和存储器设置在电路板上, 供电电路,用于为移动终端的电路或部件供电, 存储器,用于存储可执行程序代码, 处理器,用于通过读取存储在其中的可执行程序代码,运行与可执行程序代码对应的程序。 执行以下操作的内存。 [0081] 在S座 11 ':用户使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 [0082] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0083] 在本发明实施例中,所述待拍摄对象可以是用户通过移动终端拍摄的景物、人物、事物等。 [0084] 在本发明实施例中,预设像素为屏蔽像素,预设像素成对设置。 [0085] 在一个实施例中,当用户使用移动终端对被摄体进行拍摄时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 也就是说,通过在感光元件上保留一些被遮蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定对焦偏移值,从而实现相位对焦。 [0086] 参见图2,图2为本发明实施例的感光元件上预设像素的示意图。 例如,图2中标有字母的像素点可以是预设像素点,预设像素点是成对设置的。 例如,预设像素A、B、C、D、E、F、G、H、I、J可以标记为预设像素对A和B、预设像素对C和D、预设像素对E F、预设像素对G和H以及预设像素对I和J。 [0087] 在S座 12 ',控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0088] 在本发明实施例中,可以通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0089] 在本发明实施例中,初始位置为移动终端中感光元件在动作时根据预设的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块S 11 ’。 [0090] 在本发明实施例中,当移动终端中的感光元件上没有预留遮蔽像素时,原始像素例如可以是默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0091] 在一个实施例中,可以通过微机电光学防抖系统控制感光元件的移动,使得感光元件在初始位置产生位移,用原始像素替换遮蔽像素,得到替换像素。 [0092]举例来说,参见图2,图2中标有字母的像素点为被遮蔽的像素点,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到被替换的像素点。 换句话说,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,使得前后相同滤光片位置对应的感光像素。 运动不同,运动前那些预设像素(保留的屏蔽像素)的位置被运动后的原始像素(默认像素)替换。 [0093] 在S座 13 ',根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置。 [0094] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据替换后的像素对被摄体进行拍摄时采集的感光数据。 [0095] 在本发明实施例中,在采集到第一感光数据后,可以控制感光元件返回初始位置,以预设像素为基准对被摄体进行拍摄。 [0096] 在S座 14 ',对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据。 [0097] 在本发明实施例中,当控制感光元件返回初始位置时,以预设像素为基准对被摄体进行拍摄,使得感光元件在初始位置采集被摄体的感光数据。 初始位置作为第二感光数据。 [0098] 在本发明实施例中,由于感光元件在初始位置产生位移,因此使用原始像素替换感光元件上的遮蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以根据第一拍照数据对第二拍照数据进行补偿,以补偿被遮挡的像素点。 [0099] 在S座 15 '、根据第一感光数据和第二感光数据合成被摄体的图像。 [0100] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,根据补偿后的第二感光数据合成被摄体的图像。 [0101] 本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素点采集被摄体的第一感光数据,控制感光元件回到初始位置,对被摄体进行拍摄,使感光元件采集第二感光数据。 待拍摄物体在初始位置的数据。 根据第一感光数据与第二感光数据合成待拍摄物的影像。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0102]装置的上述实施例是示例性的。 被描述为独立组件的单元可能是物理上分离的,也可能不是。 以单元表示的部件可以是物理单元,也可以不是物理单元,即可以集成在一个位置上,也可以分布到多个网络单元中。 可以根据实际需要选择其中的部分或者全部模块来实现本实施例方案的目的。 本领域技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0103] 本发明实施例的方法中的步骤可以根据实际需要依次调整、合并、删减。 [0104] 本发明实施例的装置中的模块或单元可以根据实际需要进行合并、划分和删除。 [0105] 本发明实施例的模块或模块可以由通用集成电路(如中央处理器CPU)或专用集成电路(ASIC)来实现。 [0106] 通过以上实施例的描述,本领域的技术人员可以清楚地了解到,各种实施方式可以通过软件加必要的通用硬件平台的方式来实现,当然也可以通过硬件来实现。 基于这样的理解,上述技术方案可以本质上以软件产品的形式体现,也可以以软件产品的形式体现,该软件产品可以存储在ROM/RAM、磁盘、光盘等计算机可读取存储介质中。 盘等,并且包括用于使计算机设备(其可以是个人计算机、服务器或网络设备等)执行在各个实施例或实施例的部分中描述的方法的指令。 [0107] 上述实施例并不构成对技术方案范围的限制。 凡在上述实施例的精神和原则之内,所作的任何修改、等同替换、改进等,均属于本技术方案的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106101556A(String), CN106101556B(String), EP3474535A1(String), EP3474535A4(String), EP3474535B1(String), US10848678B2(String), US20190306429A1(String), WO2018019039A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106101556A(String), CN106101556B(String), EP3474535A1(String), EP3474535A4(String), EP3474535B1(String), US10848678B2(String), US20190306429A1(String), WO2018019039A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10848678B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106101556A(String), CN106101556B(String), EP3474535A1(String), EP3474535A4(String), EP3474535B1(String), US10848678B2(String), US20190306429A1(String), WO2018019039A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), CN106101556A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), CN106101556B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.884 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), EP3474535A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), EP3474535A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.901 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), EP3474535B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.908 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), US10848678B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.916 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), US20190306429A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270709(Integer), WO2018019039A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.937 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10848678B2(String), US10848678B2(String), 1606147200(Integer), 270709(Integer), 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.949 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.951 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD(String), OPPO广东移动通信有限公司(String), 0(Integer), 1681975565(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185034(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.960 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75954(Integer), 1(Integer), 185034(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185034(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.972 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 2(Integer), 185034(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.981 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.982 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.992 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.994 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:05.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185034(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.004 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for controlling application in the mobile terminal(String), 一种在移动终端中控制应用程序的方法及移动终端(String), US8914010B2(String), A method of controlling applications in a mobile terminal is provided. The method includes collecting acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved; identifying a motion trace indicating that the mobile terminal has been moved from the collected acceleration values; matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds.(String), 提供了一种控制移动终端中的应用程序的方法。 该方法包括当移动终端正在移动时,使用加速度传感器连续采集加速度值; 从采集的加速度值中识别移动终端移动的运动轨迹; 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。(String), US13/398248(String), 1329321600(Integer), US8914010B2(String), 1418659200(Integer), 1418659200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 3(Integer), US20090303204A1 | US20110304534A1 | WO2005103863A2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185035(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.019 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.019 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\bebe217291fa4f6abb79392dad8abf3b.png(String), 185035(Integer), bebe217291fa4f6abb79392dad8abf3b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for controlling application in the mobile terminal(String), 一种在移动终端中控制应用程序的方法及移动终端(String), US8914010B2(String), A method of controlling applications in a mobile terminal is provided. The method includes collecting acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved; identifying a motion trace indicating that the mobile terminal has been moved from the collected acceleration values; matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds.(String), 提供了一种控制移动终端中的应用程序的方法。 该方法包括当移动终端正在移动时,使用加速度传感器连续采集加速度值; 从采集的加速度值中识别移动终端移动的运动轨迹; 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。(String), US13/398248(String), 1329321600(Integer), US8914010B2(String), 1418659200(Integer), 1418659200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 3(Integer), US20090303204A1 | US20110304534A1 | WO2005103863A2(String), \20230420\bebe217291fa4f6abb79392dad8abf3b.png(String), 14(Integer), 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.043 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 1. A method of controlling applications in a mobile terminal, the method comprising:presetting a motion trace for the mobile terminal:binding the preset motion trace to a control command of an application, prior to collecting acceleration values:collecting the acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved;identifying a motion trace of the mobile device, indicating that the mobile terminal has been move, from the collected acceleration values;matching the identified motion trace with the preset motion trace; andexecuting a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds.(String), 1.一种在移动终端中控制应用程序的方法,该方法包括:为移动端预设运动轨迹:在采集加速度值之前,将预设运动轨迹绑定到应用程序的控制命令:移动终端移动时,通过加速度传感器持续采集加速度值;从采集到的加速度值中识别出移动设备的运动轨迹,表明移动终端已经移动;将识别出的运动轨迹与预设运动轨迹进行匹配;和如果匹配成功,则执行映射到预设运动轨迹的控制命令以控制移动终端中的应用程序。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 2. The method of claim 1, wherein each of the acceleration values is a vector including a value on an X-axis, a value on an Y-axis, and a value on an Z-axis, and wherein collecting the acceleration values comprises:performing sampling at a preset time interval, by the acceleration sensor, when the mobile terminal is moved, and storing in a first storage space including M groups of subspaces, values on the X-axis obtained in the sampling, storing in a second storage space including M groups of subspaces, values on the Y-axis obtained in the sampling, and storing in a third storage space including M groups of subspaces, values on the Z-axis obtained in the sampling,wherein M is a positive integer greater than or equal to 1.(String), 2.如权利要求1所述的方法,其中每个加速度值是一个向量,包括X轴上的值、Y轴上的值和Z轴上的值,其中采集加速度值包括:当移动终端移动时,加速度传感器按照预设的时间间隔进行采样,将采样得到的X轴上的值存储在包括M组子空间的第一存储空间中,存储在第二存储空间中包括M组子空间、采样得到的Y轴上的值,以及存储在包括M组子空间、采样得到的Z轴上的值的第三存储空间中,其中M为大于或等于1的正整数。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 3. The method of claim 2, wherein identifying of the motion trace comprises:determining M respective X-axis motion identifiers based on values in the M groups of subspaces for the values in the first storage space, wherein each of the X-axis motion identifiers is 1, −1 or 0, and wherein 1 denotes motion in an X-axis positive direction, −1 denotes motion in an X-axis negative direction, and 0 denotes no motion on the X-axis;determining M respective Y-axis motion identifiers based on values in the M groups of subspaces for the values in the second storage space, wherein each of the Y-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in a Y-axis positive direction, −1 denotes motion in a Y-axis negative direction, and 0 denotes no motion on the Y-axis;determining M respective Z-axis motion identifiers based on values in the M groups of subspaces for the values in the third storage space, wherein each of the Z-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in a Z-axis positive direction, −1 denotes motion in a Z-axis negative direction, and 0 denotes no motion on the Z-axis;wherein the M X-axis motion identifiers, the M Y-axis motion identifiers and the M Z-axis motion identifiers are used to represent a motion trace of motion of the mobile terminal.(String), 3.如权利要求2所述的方法,其中运动轨迹的识别包括:根据M组子空间中的值为第一存储空间中的值分别确定M个X轴运动标识,其中每个X轴运动标识为1、-1或0,1表示运动在X轴正方向,-1表示X轴负方向运动,0表示X轴不运动;根据M组子空间中的值为第二存储空间中的值分别确定M个Y轴运动标识,其中,每个Y轴运动标识为1、-1或0,其中1表示Y轴运动-轴正方向,-1表示Y轴负方向运动,0表示Y轴不运动;针对第三存储空间中的值,根据M组子空间中的值分别确定M个Z轴运动标识,其中每个Z轴运动标识为1、-1或0,1表示Z轴运动-轴正方向,-1表示Z轴负方向运动,0表示Z轴不运动;其中,M个X轴运动标识、M个Y轴运动标识和M个Z轴运动标识用于表示移动终端运动的运动轨迹。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 4. The method of claim 3, whereinthe M groups of subspaces of the first storage space include N data units for respectively storing N values on the X-axis that have been obtained in sampling most recently,the M groups of subspaces of the second storage space include N data units for respectively storing N values on the Y-axis that have been obtained in sampling most recently,the M groups of subspaces of the third storage space include N data units for respectively storing N values on the Z-axis that have been obtained in sampling most recently, andwherein N is an integer greater than or equal to 1.(String), 4.如权利要求3所述的方法,其中第一存储空间的M组子空间包括N个数据单元,分别存储最近采样得到的X轴上的N个值,第二存储空间的M组子空间包括N个数据单元,分别存储最近采样得到的Y轴上的N个值,第三存储空间的M组子空间包括N个数据单元,分别存储最近一次采样得到的N个Z轴值,其中N为大于或等于1的整数。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 5. The method of claim 4, wherein determining the M respective X-axis motion identifiers based on values in the M groups of subspaces, determining of the M respective Y-axis motion identifiers based on values in the M groups of subspaces, and determining of the M respective Z-axis motion identifiers based on values in the M groups of subspaces comprises:selecting a first group of subspaces as the current group;subtracting a still value from the N values stored in the current group and comparing the differences between the N values and the still value with a preset threshold value to obtain N comparison results, wherein the N comparison results are obtained as follows: if a difference is larger than the preset threshold value, the corresponding comparison result is 1; if a difference is smaller than the minus preset threshold value, the corresponding comparison result is −1; and if the absolute value of a difference is smaller than the preset threshold value, the corresponding comparison result is 0;counting the N comparison results of the current group and taking one of 1, −1 and 0 whose number of the N comparison results is the maximum as a motion identifier of a corresponding axis among the X-axis motion identifier, the Y-axis motion identifier, and the Z-axis motion identifier corresponding to the current group of subspace; andselecting the next group as the current group and returns to the second step unless all of the M groups of subspaces are processed.(String), 5.如权利要求4所述的方法,其中根据M组子空间中的值分别确定M个X轴运动标识,根据M组子空间中的值分别确定M个Y轴运动标识,以及确定M个相应的Z轴运动标识基于M组子空间中的值包括:选择第一组子空间作为当前组;将当前组中存储的N个值减去一个静止值,将N个值与静止值的差值与预设阈值进行比较,得到N个比较结果,其中,得到N个比较结果:如果差值是大于预设阈值,对应的比较结果为1;若差值小于负预设阈值,则对应的比较结果为-1;如果差的绝对值小于预设阈值,则对应的比较结果为0。统计当前组的N个比较结果,取X轴运动标识、Y轴运动中N个比较结果的个数最大的1、-1、0作为对应轴的运动标识标识符,以及当前子空间组对应的Z轴运动标识符;和选择下一组作为当前组并返回第二步,除非处理完所有M组子空间。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 6. The method of claim 5, further comprising:determining whether the motion identifier of the corresponding axis corresponding to the current group is 0; andcalculating a mean of the N values of the current group and updating the still value as the calculated mean.(String), 6.如权利要求5所述的方法,还包括:判断当前组对应的对应轴的运动标识是否为0;和计算当前组的N个值的平均值,并将静止值更新为计算平均值。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 7. The method of claim 1, wherein presetting a motion trace for the mobile terminal comprises:collecting acceleration values using the acceleration sensor continuously when the mobile terminal is being moved;identifying a motion trace indicating that the mobile terminal has been moved, from the collected acceleration values; displaying the identified motion trace to a user; andsaving the identified motion trace, when a confirmation instruction is received from the user; otherwise, returning to the first step.(String), 7.如权利要求1所述的方法,其中为移动终端预设运动轨迹包括:移动终端移动时,通过加速度传感器持续采集加速度值;从采集到的加速度值中识别移动终端移动过的运动轨迹;将识别出的运动轨迹展示给用户;和当接收到用户的确认指令时,保存识别出的运动轨迹;否则,返回第一步。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 8. A mobile terminal, comprising:an acceleration sensor for detecting an acceleration when the mobile terminal is being moved; anda controller for presetting a motion trace of the mobile terminal, binding the preset motion trace to a control command of an application, prior to collecting acceleration values, collecting the acceleration values continuously using the acceleration sensor, when the mobile terminal is being moved, identifying a motion trace of the mobile terminal, indicating that the mobile terminal has been moved, from the collected acceleration values, matching the identified motion trace with the preset motion trace, and executing a control command mapped to the preset motion trace to control applications in the mobile terminal, if the matching succeeds.(String), 8.移动终端,包括:加速度传感器,用于检测移动终端移动时的加速度;和控制器,用于预设移动终端的运动轨迹,将预设运动轨迹与应用程序的控制命令绑定,在采集加速度值之前,利用加速度传感器持续采集加速度值,在移动终端移动时,识别移动终端的运动轨迹,表示移动终端已经移动,根据采集到的加速度值,将识别出的运动轨迹与预设运动轨迹匹配,执行映射到预设运动轨迹的控制命令,控制应用程序中的应用程序移动端,如果匹配成功。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 9. The mobile terminal of claim 8, further comprising:a memory for providing first, second, and third storage spaces including respective M groups of subspaces,wherein the acceleration value is a vector including a value on the X-axis, a value on the Y-axis, and a value on the Z-axis and, when collecting the acceleration values, the controller performs sampling at a time interval preset by the acceleration sensor when the mobile terminal is being moved and stores values on the X-axis obtained during the sampling in the M groups of subspaces of the first storage space, stores values on the Y-axis obtained in the sampling in the M groups of subspaces of the second storage space, and stores values on the Z-axis obtained in the sampling in the M groups of subspaces of the third storage space,wherein M is a positive greater than or equal to 1.(String), 9.如权利要求8所述的移动终端,还包括:存储器,用于提供分别包括M组子空间的第一、第二和第三存储空间,其中,加速度值是一个向量,包括X轴的值、Y轴的值和Z轴的值,控制器在采集加速度值时,按照控制器预设的时间间隔进行采样。移动终端移动时的加速度传感器,将采样得到的X轴值存储在第一存储空间的M组子空间中,将采样得到的Y轴值存储在第一存储空间的M组子空间中。第二存储空间的子空间,将采样得到的Z轴上的值存储在第三存储空间的M组子空间中,其中M是大于或等于1的正数。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 10. The mobile terminal of claim 9, wherein, the controller determines M respective X-axis motion identifiers based on values in the M groups of subspaces for the values in the first storage space, when the motion trace is identified,wherein each of the X-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in an X-axis positive direction, −1 denotes motion in an X-axis negative direction, and 0 denotes no motion on the X-axis, determines M respective Y-axis motion identifiers based on values in the M groups of subspaces for the values in the second storage space,wherein each of the Y-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in Y-axis positive direction, −1 denotes motion in a Y-axis negative direction, and 0 denotes no motion on the Y-axis and determines M respective Z-axis motion identifiers based on values in the M groups of subspaces for the values in the third storage space,wherein each of the Z-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in a Z-axis positive direction, −1 denotes motion in a Z-axis negative direction, and 0 denotes no motion on the Z-axis, and the M X-axis motion identifiers, the M Y-axis motion identifiers and the M Z-axis motion identifiers are used to represent a motion trace of motion of the mobile terminal.(String), 10.如权利要求9所述的移动终端,其中,控制器在识别运动轨迹时,根据M组子空间中的值为第一存储空间中的值确定M个各自的X轴运动标识,其中,每个X轴运动标识为1、-1或0,其中1表示X轴正方向运动,-1表示X轴负方向运动,0表示X轴不运动axis,根据M组子空间中的值为第二存储空间中的值确定M个各自的Y轴运动标识,其中,每个Y轴运动标识为1、-1或0,其中1表示Y轴正方向运动,-1表示Y轴负方向运动,0表示Y轴不运动根据M组子空间中的值为第三存储空间中的值确定M个各自的Z轴运动标识,其中,每个Z轴运动标识为1、-1或0,其中1表示Z轴正方向运动,-1表示Z轴负方向运动,0表示Z轴不运动M个X轴运动标识、M个Y轴运动标识和M个Z轴运动标识用于表示移动终端运动的运动轨迹。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 11. The mobile terminal of claim 10, wherein the M groups of subspaces of the first storage space include N data units for respectively storing N values on the X-axis that have been obtained in sampling most recently, the M groups of subspaces of the second storage space include N data units for respectively storing N values on the Y-axis that have been obtained in sampling most recently and the M groups of subspaces of the third storage space include N data units for respectively storing N values on the Z-axis that have been obtained in sampling most recently,wherein N is an integer greater than or equal to 1.(String), 11.如权利要求10所述的移动终端,其中第一存储空间的M组子空间包括N个数据单元,分别存储最近一次采样得到的X轴上的N个值,第二存储空间的M组子空间包括N个数据单元,分别存储N个最近采样得到的Y轴上的值,第三存储空间的M组子空间包括N个数据单元,分别存储N个最近采样得到的Z轴上的值,其中N为大于或等于1的整数。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 12. The mobile terminal of claim 11, wherein, when determining the M respective X-axis motion identifiers based on values in the M groups of subspaces, determining of the M respective Y-axis motion identifiers based on values in the M groups of subspaces, and determining of the M respective Z-axis motion identifiers based on values in the M groups of subspaces, respectively, the controller subtracts a still value from the N values stored in the respective M groups and compares the differences between the N values and the still value with a preset threshold value to obtain N comparison results, and counts the N comparison results of the current group and takes one of 1, −1 and 0 whose number of the N comparison results is the maximum as a motion identifier of a corresponding axis among the X-axis motion identifier, the Y-axis motion identifier, and the Z-axis motion identifier corresponding to the current group of subspace,wherein the N comparison results are obtained as follows: if a difference is larger than the preset threshold value, the corresponding comparison result is 1; if a difference is smaller than the minus preset threshold value, the corresponding comparison result is −1; if the absolute value of a difference is smaller than the preset threshold value, the corresponding comparison result is 0.(String), 12.如权利要求11所述的移动终端,其中,当根据M组子空间中的值确定M个各自的X轴运动标识时,根据M组子空间中的值确定M个各自的Y轴运动标识,以及确定M个各自的Z轴运动控制器分别根据M组子空间中的值分别从存储的N个值中减去一个静止值,将N个值与静止值的差值与预设阈值进行比较,得到N个比较结果,统计当前组的N个比较结果,取N个比较结果中数量最多的1、-1、0作为X轴运动标识中对应轴的运动标识,Y-轴运动标识,以及当前子空间组对应的Z轴运动标识,其中,N个比较结果的获取方式为:若差值大于预设阈值,则对应的比较结果为1;若差值小于负预设阈值,则对应的比较结果为-1;如果差的绝对值小于预设的阈值,则对应的比较结果为0。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 13. The mobile terminal of claim 12, wherein the controller calculates a mean of the N values of the current group and updates the still value as the calculated mean, if the motion identifier on the corresponding axis is 0.(String), 13.如权利要求12所述的移动终端,其中控制器计算当前组的N个值的平均值,如果相应轴上的运动标识符为0,则将静止值更新为计算出的平均值。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185035(Integer), 14. The mobile terminal of claim 8, wherein, when presetting a motion trace for the mobile terminal, the controller continuously collects the acceleration values using the acceleration sensor when the mobile terminal is being moved, identifies a motion trace that the motile terminal has been moved, from the collected acceleration values, displays the identified motion trace to a user, and stores the identified motion trace, when a confirmation instruction is received from the user.(String), 14.如权利要求8所述的移动终端,其中,当为移动终端预设运动轨迹时,控制器通过加速度传感器不断采集移动终端移动时的加速度值,识别移动终端移动过的运动轨迹,根据采集到的加速度值,显示识别的当接收到用户的确认指令时,将运动轨迹发送给用户,并存储识别出的运动轨迹。(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.166 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185035(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to a Chinese Patent Application filed in the State Intellectual Property Office of the People's Republic of China on Feb. 16, 2011 and assigned Ser. No. 201110041328.4, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to mobile terminals and, more particularly, to a method and an apparatus for controlling applications in a mobile terminal. [0004]2. Background of the Invention [0005]Various mobile terminals such as a mobile terminal, a tablet computer, and a smart phone increasingly include more functions and, specifically, not only basic communications services, such as calling, but also various applications can be implemented. When an application is to be started or exited, a user performs the operation of start or exit by selecting the menus provided by the mobile terminal level by level. However, such operation is inconvenient. [0006]Some high-end mobile terminals also allow users to control special functions in applications in the mobile terminals. For example, a user may zoom into a picture or control a game by shaking the terminal. However, all of these controls are simple. More and more demands on control of applications have been made. Thus, it is difficult for simple shaking of the terminal to meet more complex user demands. SUMMARY OF THE INVENTION [0007]Accordingly, the present invention provides a method capable of easily controlling various applications of mobile terminals and the mobiles terminals. [0008]The present invention also provides a method for controlling applications of mobile terminal by user writing with the mobile terminal and the mobile terminal. [0009]In accordance with an aspect of the present invention, a method of controlling applications in a mobile terminal is provided. The method includes collecting acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved; identifying a motion trace indicating that the mobile terminal has been moved from the collected acceleration values; matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds. [0010]In accordance with another aspect of the present invention, a mobile terminal is provided. The terminal includes an acceleration sensor for detecting an acceleration when the mobile terminal is being moved; and a controller for collecting acceleration values using the acceleration sensor continuously when the mobile terminal is being moved, identifying a motion trace that the mobile terminal has been moved from the collected acceleration values, matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace if the matching succeeds, to control applications in the mobile terminal. [0011]Thus, according to the present invention, a user can write any types of characters and pictures, not only simple shakes with a handheld mobile terminal. Therefore, motion traces can be formed and control commands can thereby be mapped by the motion traces. Consequently, it is possible to easily control various applications in the mobile terminal by a user writing with a handheld mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0012]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0013]FIG. 1 illustrates a mobile terminal according to embodiments of the present invention; [0014]FIG. 2 illustrates a flowchart according to a first embodiment of the present invention; [0015]FIG. 3 illustrates a flowchart according to a second embodiment of the present invention; [0016]FIG. 4A illustrates queue 1 for storing sampled data on X-axis according to embodiments of the present invention; [0017]FIG. 4B illustrates queue 2 for storing sampled data on Y-axis according to embodiments of the present invention; [0018]FIG. 4C illustrates queue 3 for storing sampled data on Z-axis according to embodiments of the present invention; [0019]FIG. 5A illustrates writing the character of “L” with a mobile terminal according to embodiments of the present invention; [0020]FIG. 5B illustrates executing an application after the character “L” is written with a mobile terminal according to embodiments of the present invention; [0021]FIG. 6A illustrates writing the character of “Z” with a mobile terminal according to embodiments of the present invention; and [0022]FIG. 6B illustrates executing an application after the character “Z” is written with a mobile terminal according to embodiments of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0023]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, a detailed explanation of known related functions and constitutions may be omitted to avoid unnecessarily obscuring the subject matter of the present invention. [0024]Hereinafter, although embodiments of the present invention will be described with reference to a mobile terminal as an example, the embodiments of the present invention may be applied to other similar apparatuses. Further, embodiments of the present invention may be applied to other apparatuses by those skilled in the arts through some modifications without departing from the spirit and scope of the present invention. [0025]FIG. 1 is a block diagram of a mobile terminal according to embodiments of the present invention. Referring to FIG. 1, a controller 100 executes a function of a mobile terminal and also performs an application control according to embodiments of the present invention. When a user writes using the mobile terminal, the controller 100 identifies motion traces that the mobile terminal has been moved, from accelerations detected by an acceleration sensor 104. When the identified motion traces are matched with a preset motion trace, a corresponding application is controlled by executing a control command mapped to the preset motion trace. [0026]A communication unit 102 performs communication for a data communication function and a phone call executed by the controller 100. The acceleration sensor 104 detects the acceleration when the mobile terminal moves. A display 106 displays a screen according to the movement of the mobile terminal by a control of the controller 100. An input/output interface 108 provides a user interface for an input and an output by the user for the controller 100. A memory 110 stores data according to an execution by the controller 100 and stores acceleration values detected by the acceleration sensor 104. The memory 110 may further include an external memory or further include a storage device such as a Hard Disk Drive (HDD). [0027]FIG. 2 shows a flowchart according to an embodiment of the present invention. Referring to FIG. 2, the controller 100 continuously collects acceleration values using an acceleration sensor 104 when the mobile terminal is being moved in step 200. [0028]In practical applications, accelerations occur in the mobile terminal in general when a user holds a mobile terminal and writes with the handheld mobile terminal in a space. The acceleration sensor 104 detects an acceleration of the mobile terminal. A detected acceleration value is a vector including scalar quantity values on the coordinate axes of a three-dimensional space, i.e., a value on the X-axis, the Y-axis and the Z-axis. [0029]In step 202, the controller 100 identifies a motion trace indicating that the mobile terminal has been moved from the collected acceleration values. [0030]The detected acceleration values are representative of the accelerations of the mobile terminal and cannot represent a motion trace. However, a plurality of continuous accelerations can represent a certain trend of the motion of the mobile terminal. Thus, in this step, a motion trace of the mobile terminal can be identified. [0031]This method is described by taking the X-axis as an example. Assuming that an acceleration value on the X-axis of the mobile terminal is detected as 2 when the mobile terminal is moved to point A, an acceleration value on the X-axis of the mobile terminal is detected as 4 when the mobile terminal is moved to point B, and an acceleration value on the X-axis of the mobile terminal is detected as 6 when the mobile terminal is moved to point C during continuous detection, it can be derived that the mobile terminal is moved in the X-axis positive direction at all of points A, B and C and is moved in the positive direction from point A to point B, and then point C. A motion trace described in the present invention means a shape of trace formed by motion trends, rather than a trace formed by positions in the three-dimensional space where the mobile terminal is. Description is given only by taking the X-axis as the sample. Processing on the Y-axis and the Z-axis is similar to that on the X-axis and will not be described herein. [0032]The method of identifying a motion trace is described in detail below. [0033]First, it is assumed that a first storage space, a second storage space and a third storage space provided by the memory 110 are used to store respective sampled values. Among these storage spaces, the first storage space includes M groups of subspaces to store M groups of values on the X-axis, the second storage space includes M groups of subspaces to store M groups of values on the Y-axis, and the third storage space includes M groups of subspaces to store M groups of values on the Z-axis. Thus, when step 200 is carried out, the acceleration sensor 104 performs sampling at a preset time interval. In other words, at a certain sampling frequency, when the mobile terminal is being moved and stores values on the X-axis obtained in the sampling in the M groups of subspaces of the first storage space, stores values on the Y-axis obtained in the sampling in the M groups of subspaces of the second storage space, and stores values on the Z-axis obtained in the sampling in the M groups of subspaces of the third storage space. Herein, M is a positive integer greater than or equal to 1. [0034]With the sampled data stored in the above manner, the values on the X-axis, the Y-axis, and the Z-axis can be separately processed as follows to identify a motion trace. [0035]I) For values in the first storage space, i.e., collected values (scalar quantity values) on the X-axis, M respective X-axis motion identifiers are determined based on values in the M groups of subspaces. An X-axis motion identifier is 1, −1 or 0.1 denotes motion in the X-axis positive direction, −1 denotes motion in the X-axis negative direction, and 0 denotes no motion on the X-axis. [0036]II) For values in the second storage space, i.e., collected values (scalar quantity values) on the Y-axis, M respective Y-axis motion identifiers are determined based on values in the M groups of subspaces. A Y-axis motion identifier is 1, −1 or 0.1 denotes motion in the Y-axis positive direction, −1 denotes motion in the Y-axis negative direction, and 0 denotes no motion on the Y-axis. [0037]III) For values in the third storage space, i.e., collected values (scalar quantity values) on the Z-axis, M respective Z-axis motion identifiers are determined based on values in the M groups of subspaces. A Z-axis motion identifier is 1, −1 or 0.1 denotes motion in the Z-axis positive direction, −1 denotes motion in the Z-axis negative direction, and 0 denotes no motion on the Z-axis. [0038]That is, no matter whether the values on the X-axis are positive, negative or zero, they represent a motion trace formed of motion trends on the X-axis so long as they are converted into M motion identifiers. This is because, assuming that there is one piece of sampled data in each of the groups of subspaces and the groups of subspaces are stored successively in a certain order, e.g., an order of group 1 to group M, as described above, if a sampled value is positive, it is converted into a motion identifier 1, which represents motion in the X-axis positive direction; if a sampled data is negative, it is converted into a motion identifier −1, which represents motion in the X-axis negative direction; if a sampled data is 0, it is kept unchanged and represents no motion on the X-axis. Thus, M successive converted motion identifiers can represent a motion trend on the X-axis. For values on the Y-axis and Z-axis, they can be converted into motion identifiers based on the above principle to represent a motion trend on the Y-axis/Z-axis. [0039]Specifically, at least the following two methods are available to perform the above determining of M motion identifiers. [0040]A first method: directly determining M motion identifiers based on values in M groups of subspaces, respectively. This method is the same as that in the above example. As another example, supposing that there are 8 groups of subspaces in a first storage space and values in the 8 groups. [0041]of subspaces are 1, 2, 4, −2, −4, 2, 3 and 4, respectively, a motion identifier corresponding to a positive number is set as 1, a motion identifier corresponding to a negative number is set as −1, while a motion identifier corresponding to 0 is set as 0. Thus, the motion identifiers corresponding to the 8 groups of subspaces in the first storage space are 1, 1, 1, −1, −1, 1, 1, and 1, respectively. Values in the second storage space or third storage space are processed in the same manner. In sum, in the first method, motion identifiers are determined directly based on values in M groups of subspaces. Moreover, in the above example, it is assumed that M is equal to 8 and there is only one sample value in each subspace, while in practical HI applications, M and a number of sampled value in each subspace vary with sampling methods. [0042]A second method: determining M motion identifiers based on values in M groups of subspaces, a still value (i.e., representing that the terminal is not being moved), and a threshold value. In this method, an acceleration sensor 104 determines the mobile terminal's not being moved as being moved by mistake due to factors such as inaccurate operation of the user and/or an error of the sensor and thereby obtain a certain sampled value when a user writes with a handheld mobile terminal. To eliminate this error, a still value representing the terminal not being moved and a threshold value are set. A sampled value is compared with the still value. If the difference between the sampled value and the still value falls within a range of the threshold value, the mobile terminal is regarded as not having been moved. If the difference falls outside the range of the threshold value, the mobile terminal is determined as having been moved in a positive or negative direction based on the particular case. [0043]Additionally, in order to increase accuracy of the identification, a high sampling frequency is set for more samples. To make processing more convenient, N data units can be provided in each subspace to store sampled values that have been obtained. For example, each of the M groups of subspaces of a first storage space includes N data units for respectively storing N values on the X-axis that have been obtained in sampling; each of the M groups of subspaces of a second storage space includes N data units for respectively storing N values on the Y-axis that have been obtained in sampling; each of the M groups of subspaces of a third storage space includes N data units for respectively storing N values on the Z-axis that have been obtained in sampling. Herein, N is an integer greater than or equal to 1 [0044]Thus, to convert the values stored in the M groups of subspaces of each of the first, second and third storage spaces, the second method performs the following steps. [0045]For the X-axis, the method includes the following steps:[0046]x1. selecting a first group as the current group;[0047]x2. subtracting a first still value from the N values stored in the current group and comparing the differences between the N values and the first still value with a preset first threshold value to obtain N comparison results, wherein the N comparison results are obtained as follows. If a difference is larger than the preset first threshold value, the corresponding comparison result is 1; if a difference is smaller than the minus preset first threshold value (i.e., a negative preset first threshold value). the corresponding comparison result is −1; if the absolute value of a difference is smaller than the preset first threshold value, the corresponding comparison result is 0;[0048]x3. counting the N comparison results of the current group and taking one of 1, −1 and 0 whose number of the N comparison results is the maximum as the X-axis motion identifier corresponding to the current group of subspace;[0049]x4. selecting the next group as the current group and returning to x2 unless all of the M groups of subspaces are processed. [0050]Similar steps y1 to y4 and z1 to z4 occur for the Y-axis and Z-axis, respectively. [0051]As described above, the processing methods for values on the X-axis, Y-axis, and Z-axis are similar. All of these methods subtract a corresponding still value from the N data in a group of subspace, to compare the differences with a corresponding threshold value to determine whether the differences fall within or outside a range of the threshold, and to determine the motion identifier of the group of subspace based on results of the comparison. Since each storage space has M groups of subspaces, M motion identifiers are obtained in all of the these methods after the above processing is performed. The M motion identifiers can represent a motion trace on a certain axis as in the first method. Of course, a motion trace identified by the second method should be more accurate than that by the first method since factors such as inaccurate operation of a user and an error of the sensor is eliminated in the second method. [0052]Moreover, all of the first still value, the second still value and the third still value represent no motion. They are the same or different. Similarly, each of the first threshold value, the second threshold value and the third threshold value represents a certain range. [0053]Step 204, the controller 100 matches the identified motion trace with a preset motion trace, and executes a control command mapped to the preset motion trace to control an application in the mobile terminal if the matching succeeds. [0054]This step compares the X-axis motion identifier, the Y-axis motion identifier and the Z-axis motion identifier and determines whether the matching has succeeded based on the results of the comparisons. The control command mapped is automatically executed and thereby the application in the mobile terminal is controlled if the matching succeeds. [0055]In another embodiment of the present invention, it is assumed that a sampling frequency of the acceleration sensor 104 in a mobile terminal is 400 Hz, i.e., the acceleration sensor collects data once every 0.0025 seconds. That is, every second, 400 pieces of data on the X-axis, 400 pieces of data on the Y-axis and 400 pieces data on the Z-axis are collected. It is also assumed that each of a first storage space, a second storage space and a third storage space to store sampled data includes M groups of subspaces, each of which includes N data units. Herein, M=8, and N=50. In this embodiment, the first storage space, the second storage space and the third storage space are shown using queue 1, queue 2, queue 3, respectively. Each of the queues has 8 nodes and each of the nodes includes 50 data units. Moreover, the sampled data is stored in an order of queue head to queue tail when sampled data are HI stored. The data at the queue head is deleted and a node storing the new sampled data is inserted to the queue tail when data units of all of the nodes are occupied. That is, in this embodiment, each of the queues always stores the 400 sampled data that have been last obtained. Sampled data is stored in another data structure other than a queue. [0056]Moreover, it is also assumed in this embodiment that the controller 100 has an application control-setting module that operates in two modes, i.e., a motion trace-presetting mode and a motion trace-identifying mode. [0057]FIG. 3 shows a flowchart of the method of this embodiment. Referring to FIG. 3, the controller 100 allows the acceleration sensor 104 to perform sampling at an rate of 0.0025 second and to store values on the X-axis obtained in the sampling in queue 1, store values on the Y-axis obtained in the sampling in queue 2, while store values on the Z-axis obtained in the sampling in queue 3, when the mobile terminal is being moved in step 300. [0058]Queues 1, 2 and 3 in this step is shown as in FIGS. 4A to 4C, respectively. As described above, the sampled data is stored in the order of queue head to queue tail. For example, the first group of 50 data are placed at the head node of a queue when 50 pieces sampled data are obtained. After 0.125 seconds (50*0.0025 seconds), the second group of 50 sampled data is stored at the second node. After another 0.125 seconds, the third group of 50 sampled data is stored at the third node, and so on. When all of 8 nodes of a queue are full, data at the head node of the queue is deleted and the node storing the 50 sampled data that have been recently obtained is stored at the tail of the queue. In sum, each of queues 1, 2 and 3 always stores the 400 pieces of data that have been obtained lately. [0059]In step 302, the controller 100 determines whether the application control-setting module is running, and if so, step 304 is performed. Otherwise, step 306 is performed. [0060]In step 304, the controller 100 determines the current mode for the application control-setting module. If the current mode is the motion trace-presetting mode, step 312 is performed. If the current mode is the motion trace-identifying mode, step 306 is performed. [0061]In this embodiment, the application control-setting module is provided in the mobile terminal and the function of motion trace presetting or motion trace identifying is started by the application control-setting module. However, the application control-setting module is not provided in practical applications. Whether the application control-setting module is present does not affect the implementation of the solution, and steps 302 and 304 may be omitted. [0062]In step 306, 8 X-axis motion identifiers are determined from the values in queue 1, 8 Y-axis motion identifiers are determined from the values in queue 2, and 8 Z-axis motion identifiers are determined from the values in queue 3. [0063]Determining the 8 X-axis motion identifiers can be done in the method of the above steps x1 to x4, determining of the 8 Y-axis motion identifiers can be done in the method of the above steps y1 to y4, and determining of the 8 Z-axis motion identifiers can be done in the method of the above steps z1 to z4, all of which will not be described herein. [0064]All of the nodes of a queue do not store sampled data when sampling has just started. For example, only the head node of the queue stores sampled data while none of the other nodes stores data at 0.125 second. Thus, only the motion identifier corresponding to the head node of the queue can be determined. After 0.125 second, the second node of the queue also stored sampled data as described in step 300. Thus, the motion identifier corresponding to the second node can be determined. Herein, the queue and the motion identifiers are not specified and can be for the X-axis, Y-axis or Z-axis. [0065]Additionally, since an error may occur during operation, a first still value, a second still value and a third still value are be further updated in this step when the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers are determined. That is, between steps x3 and x4, the method further includes the following step to be performed when the 8 X-axis motion identifiers are determined. Determining whether the X-axis motion identifier corresponding to the current group is 0 and. if so, calculating a mean of the N values (N values on the X-axis) of the current group and updating the first still value as the calculated mean; otherwise, returning to step x4. A similar step can occur between steps y3 and y4 and z3 and z4. [0066]These steps are used to update the still values because during the operation by a user, a mobile terminal is substantially still if a motion identifier corresponding to the current group of data is 0. However, all of the N (in this embodiment, N is 50) pieces of data of the current group on each of the axes are not necessarily equal to the still value due to an error of operation or measurement. Thus, if the still value is set as a mean of the N values, the N values as a whole are closer to the still value, thereby, avoiding the case that the mobile terminal is not being moved is mistaken for being moved. [0067]In step 308, the identified motion trace is matched with a preset motion trace, and step 310 is performed if the matching succeeds. Otherwise, the process returns to step 300. [0068]Steps 300 to 308 form a large cycle, in which the acceleration sensor 104 in the mobile terminal performs sampling continuously and accesses the queues every 0.125 second. Accordingly, a motion trace is identified for the mobile terminal every 0.125 second. The identification may fail within the first one second from when sampling is started since all of the nodes in a queue do not store data and thus the determined 8 motion identifiers are inaccurate. However, all the nodes in the queue store sampled data after the one second. Thereby, effective 8 motion identifiers can be determined. As described in an embodiment above, X-axis motion identifiers, Y-axis motion identifiers and Z-axis motion identifiers represent a motion trace that a mobile terminal has been moved. In this embodiment, a preset motion trace is also represented using X-axis motion identifiers, Y-axis motion identifiers and Z-axis motion identifiers. Thus, whether the matching succeeds is determined by comparing the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers determined in step 306 with the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers of the preset motion trace, respectively. [0069]The matching does not necessarily succeed at once after the one second of sampling. However, as described in step 300, the acceleration sensor may continue with sampling, new motion identifiers may be determined from the sampled data that have been obtained lately for the mobile terminal, and matching with the preset motion trace is made in step 308 again. Once the matching succeeds, the next step 310 is performed. [0070]The matching in step 308 is performed in a manner of exact match or a manner of approximate matching in practical applications. The manner of exact matching means that the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers of an identified motion trace are the same as the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers of a preset motion trace, respectively. The manner of approximate matching means that the motion identifiers on the three axes are not completely the same but a number of pairs of motion identifiers being the same is larger than a preset matching threshold value. For example, a matching threshold value is preset as 6 and 7 motion identifiers on each of the axes of an identified motion trace are the same as those of a preset motion trace, respectively. In this case, the number, 7, is larger than the matching threshold value 6. This would be a case of matching succeeding. [0071]A time threshold value also can be set. Identification is not performed anymore (i.e., no return to step 300) to avoid an infinite loop when the threshold value is exceeded. [0072]In step 310, a control command mapped to the preset motion trace is executed to control an application in the mobile terminal, and this procedure is completed. [0073]In step 312, acceleration values are continuously collecting using an acceleration sensor 104 when a mobile terminal is being moved. The same method as that for step 300 can be used for this step and will not be described herein. [0074]In step 314, a motion trace that the mobile terminal has been moved is identified from the collected acceleration values and the identified motion trace is displayed to the user through the display 106. [0075]The same method as that in step 306 is used to identify the motion trace. Moreover, after the motion trace is identified, the motion trace is visualized as a character to be displayed to the user through the display 106 for the convenience of confirmation by the user. [0076]In step 316, whether a confirmation instruction is received from the user is determined, and if the confirmation instruction is received through the input/output interface 108, step 318 is performed. Otherwise, return to step 312. [0077]In step 318, the identified motion trace is saved and this procedure is completed. [0078]A preset motion trace occurs in steps 312 to 318. If there is an application control-setting module in a mobile terminal, this module also can provide functions of displaying, searching for, associating and deleting a preset motion trace for more exact operation by a user. Steps 312 to 318 make a preset motion trace and are not necessary in an identifying process. Thus, they can be omitted in identifying a motion trace and controlling an application. [0079]It is easy to bind a control command to a preset motion trace in applications. For example, a database is provided to store corresponding relationships between preset motion traces and control commands. Thus, after matching succeeds in step 308, the motion trace whose matching succeeds is searched for in the database and a corresponding control command is executed. [0080]FIGS. 5A, 5B, 6A, and 6B each show examples illustrating controlling an application in accordance with an embodiment of the present invention. As shown in FIG. 5A, a user writes the character, “L”, with a handheld mobile terminal in the air. A motion trace is formed during motion of the mobile terminal. Supposing that this motion trace is preset in the mobile terminal and is mapped to the control command of “Opening” the application “Notepad”, “Notepad” is automatically opened once the matching succeeds. The result is shown in FIG. 5B. [0081]In another example, as shown in FIG. 6A, a user writes the character, “Z”, with a handheld mobile terminal in the air. A motion trace is formed during motion of the mobile terminal. Assuming that this motion trace is preset in the mobile terminal and is mapped to the control command of “Opening” the application “instant messenger”, “instant messenger” is automatically opened once the matching succeeds. The result is shown in FIG. 6B. [0082]By applying this embodiment, a motion trace formed during motion of the mobile terminal is identified by means of an acceleration sensor 104 when a user writes with a handheld mobile terminal. A corresponding control command is started when the identified motion trace succeeds in matching with a preset motion trace. Thus, the objective of controlling an application is achieved. The user can write any characters and pictures not only simple shakes with the handheld mobile terminal. Thus, a lot of motion traces can be formed and a lot of control commands can thereby be mapped. Consequently, it is possible to easily control various applications in the mobile terminal by a user writing with a handheld mobile terminal. [0083]Embodiments of the present invention can be implemented by hardware, software, and a combination of the hardware and the software. For example, the software can be stored, regardless of possibility of omission or rewrite, in volatile or non-volatile storage devices such as memories such as a Read Only Memory (ROM), a Random Access Mem(String), 优先 [0001] 本申请根据 35 U.S.C. §119(a) 于 2011 年 2 月 16 日向中华人民共和国国家知识产权局提交的中国专利申请,并转让了序列号。 第 201110041328.4 号,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及移动终端,更具体地,涉及用于控制移动终端中的应用的方法和装置。 [0004] 二、发明背景 [0005] 移动终端、平板电脑、智能手机等各种移动终端的功能越来越多,具体来说,不仅可以实现通话等基本的通信服务,还可以实现各种应用。 当要启动或退出应用程序时,用户通过逐级选择移动终端提供的菜单来进行启动或退出操作。 然而,这样的操作是不方便的。 [0006] 一些高端移动终端还允许用户在移动终端中控制应用中的特殊功能。 例如,用户可以通过摇动终端放大图片或控制游戏。 但是,所有这些控件都很简单。 对应用程序的控制提出了越来越多的要求。 因此,终端的简单晃动难以满足更复杂的用户需求。 发明内容 [0007] 因此,本发明提供了一种能够容易地控制移动终端的各种应用的方法和移动终端。 [0008] 本发明还提供了一种用户通过移动终端书写控制移动终端应用的方法及移动终端。 [0009] 根据本发明的一个方面,提供了一种在移动终端中控制应用的方法。 该方法包括当移动终端正在移动时,使用加速度传感器连续采集加速度值; 从采集的加速度值中识别移动终端移动的运动轨迹; 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。 [0010] 根据本发明的另一方面,提供了一种移动终端。 终端包括加速度传感器,用于检测移动终端移动时的加速度; 控制器,用于在移动终端移动过程中连续使用加速度传感器采集加速度值,从采集的加速度值中识别移动终端已经移动的运动轨迹,将识别的运动轨迹与预设的运动轨迹进行匹配,执行 如果匹配成功,则映射到预设运动轨迹的控制命令,以控制移动终端中的应用程序。 [0011] 因此,根据本发明,用户可以书写任何类型的字符和图片,而不仅仅是用手持移动终端进行简单的摇晃。 因此,可以形成运动轨迹,从而可以通过运动轨迹映射控制命令。 因此,可以通过用户用手持移动终端书写来容易地控制移动终端中的各种应用。 附图的简要说明 [0012] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0013] 如图。 附图说明图1示出了根据本发明实施例的移动终端; [0014] 如图。 图2为本发明第一实施例的流程图。 [0015] 如图。 图3为本发明第二实施例的流程图。 [0016] 如图。 图4A图示了队列 1 根据本发明的实施例,用于存储X轴上的采样数据; [0017]如图。 图4B图示了队列 2 根据本发明的实施例,用于在Y轴上存储采样数据; [0018] 如图。 图4C图示了队列 3 根据本发明的实施例,用于存储Z轴上的采样数据; [0019] 如图。 图5A为本发明实施例用移动终端书写“L”字的示意图。 [0020] 如图。 图5B为本发明实施例在移动终端写入字符“L”后执行应用程序的示意图。 [0021] 如图。 图6A为本发明实施例用移动终端书写“Z”字的示意图。 和 [0022] 如图。 图6B示出了根据本发明的实施例在利用移动终端写入字符“Z”之后执行应用程序。 本发明实施方案的详细说明 [0023] 在下文中,将参照附图描述本发明的实施例。 在以下描述中,可能省略对已知相关功能和构成的详细说明以避免不必要地混淆本发明的主题。 [0024] 在下文中,虽然将参考移动终端作为示例来描述本发明的实施例,但是本发明的实施例可以应用于其他类似的装置。 此外,本领域技术人员在不脱离本发明的精神和范围的情况下,可以通过一些修改将本发明的实施例应用于其他装置。 [0025] 如图。 图1是根据本发明实施例的移动终端的框图。 参考图。 1、一个控制器 100 根据本发明的实施例,执行移动终端的功能并且还执行应用控制。 当用户使用移动终端书写时,控制器 100 根据加速度传感器检测到的加速度识别移动终端已移动的运动轨迹 104 . 当识别出的运动轨迹与预设运动轨迹匹配时,通过执行映射到预设运动轨迹的控制命令来控制相应的应用程序。 [0026] 通讯单元 102 为控制器执行的数据通信功能和电话进行通信 100 . 加速度传感器 104 检测移动终端移动时的加速度。 一个显示器 106 通过控制器的控制根据移动终端的移动显示屏幕 100 . 输入/输出接口 108 为控制器提供用户输入和输出的用户界面 100 . 一段记忆 110 根据控制器的执行存储数据 100 并存储加速度传感器检测到的加速度值 104 . 记忆 110 可以进一步包括外部存储器或者进一步包括诸如硬盘驱动器(HDD)的存储设备。 [0027] 如图。 图2示出了根据本发明实施例的流程图。 参考图。 2、控制器 100 使用加速度传感器连续收集加速度值 104 当移动终端在步中移动时 200 . [0028] 在实际应用中,当用户手持移动终端在空间中书写时,移动终端一般会出现加速度。 加速度传感器 104 检测移动终端的加速度。 检测到的加速度值是包括在三维空间的坐标轴上的标量值的向量,即在X轴、Y轴和Z轴上的值。 [0029] 在步骤 202 , 控制器 100 从收集的加速度值中识别指示移动终端已经移动的运动轨迹。 [0030]检测到的加速度值代表移动终端的加速度,不能代表运动轨迹。 然而,多个连续的加速度可以代表移动终端运动的某种趋势。 因此,在本步骤中,可以识别出移动终端的运动轨迹。 [0031] 该方法以X轴为例进行说明。 假设移动终端移动到A点时检测到移动终端X轴上的加速度值为2,则移动终端移动时检测到移动终端X轴上的加速度值为4 到B点,连续检测移动终端移动到C点时,检测到移动终端X轴加速度值为6,可以推导出移动终端在X轴正方向移动 从A点到B点,再到C点的正向运动。本发明所述的运动轨迹是指运动趋势形成的轨迹形状,而不是运动轨迹。 由移动终端所在的三维空间中的位置形成的轨迹。 仅以X轴为例进行说明。 Y轴和Z轴的处理与X轴的处理类似,在此不再赘述。 [0032] 下面详细描述识别运动轨迹的方法。 [0033] 首先,假设存储器提供第一存储空间、第二存储空间和第三存储空间 110 用于存储各自的采样值。 在这些存储空间中,第一存储空间包括M组子空间,用于在X轴上存储M组值,第二存储空间包括M组子空间,用于在Y轴上存储M组值,第三存储空间包括M组子空间,用于存储M组值。 存储空间包括 M 组子空间,用于在 Z 轴上存储 M 组值。 因此,当步 200 执行时,加速度传感器 104 以预设的时间间隔进行采样。 也就是说,在某个采样频率下,当移动终端正在移动时,将采样得到的X轴值存储在第一存储空间的M组子空间中,Y轴上的值存储在第一存储空间的M组子空间中。 在第二存储空间的M组子空间中进行采样,并将采样得到的Z轴上的值存储在第三存储空间的M组子空间中。 其中,M为大于或等于1的正整数。 [0034] 通过上述方式存储的采样数据,可以分别对X轴、Y轴和Z轴上的值进行如下处理以识别运动轨迹。 [0035] i)对于第一存储空间中的值,即X轴上的采集值(标量值),根据M组子空间中的值确定M个各自的X轴运动标识。 X轴运动标识为1,-1或0.1表示X轴正方向运动,-1表示X轴负方向运动,0表示X轴无运动。 [0036] II)对于第二存储空间中的值,即Y轴上的采集值(标量值),根据M组子空间中的值确定M个各自的Y轴运动标识。 Y轴运动标识为1,-1或0.1表示Y轴正方向运动,-1表示Y轴负方向运动,0表示Y轴无运动。 [0037] III)对于第三存储空间中的值,即Z轴上的采集值(标量值),根据M组子空间中的值确定M个各自的Z轴运动标识。 Z轴运动标识为1,-1或0.1表示Z轴正方向运动,-1表示Z轴负方向运动,0表示Z轴无运动。 [0038]即无论X轴上的数值是正数、负数还是零,只要转换成M个运动标识,它们就代表了X轴上运动趋势形成的运动轨迹。 这是因为,假设每组子空间中有一个采样数据,并且子空间组按照一定的顺序依次存储,例如组的顺序 1 到组M,如上所述,如果采样值为正,则将其转换为运动标识符 1 , 表示 X 轴正方向的运动; 如果采样数据为负数,则将其转换为运动标识符-1,表示X轴负方向的运动; 如果采样数据为 0,则保持不变,表示 X 轴上没有运动。 因此,M个连续转换的运动标识符可以代表X轴上的运动趋势。 对于Y轴和Z轴上的数值,可以根据上述原理转换为运动标识,表示Y轴/Z轴上的运动趋势。 [0039] 具体地,至少可以采用以下两种方法来进行上述M个运动标识的确定。 [0040] 第一种方法:分别根据M组子空间中的值直接确定M个运动标识。 该方法与上例相同。 再如,假设第一存储空间有8组子空间,8组中的值。 [0041] 子空间的个数分别为1、2、4、-2、-4、2、3、4,正数对应的运动标识符设为1,负数对应的运动标识符设为-1, 而0对应的运动标识设置为0。因此,第一存储空间中8组子空间对应的运动标识分别为1、1、1、-1、-1、1、1、1 . 第二存储空间或第三存储空间中的值的处理方式相同。 总之,在第一种方法中,运动标识符是直接基于M组子空间中的值来确定的。 此外,在上面的例子中,假设 M 等于 8,每个子空间中只有一个样本值,而在实际的 HI 应用中,M 和每个子空间中的采样值数量会随着采样方法的不同而变化。 [0042] 第二种方法:根据M组子空间中的值、静止值(即表示终端没有被移动)和阈值确定M个运动标识。 在该方法中,加速度传感器 104 由于用户的操作不准确和/或传感器的错误等因素,将移动终端没有移动判断为误移动,从而在用户使用手持移动终端书写时获得一定的采样值。 为了消除该错误,设置了表示终端未移动的静止值和阈值。 将采样值与静止值进行比较。 如果采样值与静止值之差在阈值范围内,则认为移动终端没有移动。 如果差值落在阈值的范围之外,则根据具体情况确定移动终端已经在正方向或负方向上移动。 [0043] 另外,为了提高识别的准确性,对更多的样本设置了较高的采样频率。 为了使处理更加方便,可以在每个子空间中提供N个数据单元来存储已经获得的采样值。 例如,第一存储空间的M组子空间中的每一个包括N个数据单元,用于分别存储采样得到的X轴上的N个值。 第二存储空间的M组子空间中的每一个包括N个数据单元,用于分别存储采样得到的Y轴上的N个值。 第三存储空间的M组子空间中的每组子空间包括N个数据单元,用于分别存储采样得到的Z轴上的N个值。 这里,N为大于或等于1的整数 [0044] 因此,为了转换存储在第一、第二和第三存储空间中的每一个的M组子空间中的值,第二方法执行以下步骤。 [0045]对于X轴,该方法包括以下步骤: [0046]x1。 选择第一组作为当前组;[0047] x2。 从当前组中存储的N个值中减去第一静止值,并将N个值与第一静止值的差值与预设的第一阈值进行比较,得到N个比较结果,其中,N个比较结果的得到如下。 如果差值大于预设的第一阈值,则对应的比较结果为1; 如果差值小于负预设第一阈值(即负预设第一阈值)。 对应的比较结果为-1; 如果差值的绝对值小于预设的第一阈值,则对应的比较结果为0。[0048] x3。 统计当前组的N个比较结果,取N个比较结果个数最大的1、-1和0之一作为当前组子空间对应的X轴运动标识;[0049] x4。 选择下一组作为当前组并返回 x2,除非所有 M 组子空间都被处理。 [0050] 类似的步骤 y1 到 y4 和 z1 到 z4 分别发生在 Y 轴和 Z 轴上。 [0051] 如上所述,X轴、Y轴和Z轴上的值的处理方法是相似的。 这些方法都是从一组子空间中的N个数据中减去一个对应的静止值,将差异与对应的阈值进行比较,判断差异是在阈值范围内还是在阈值范围外,从而确定运动标识。 基于比较结果的子空间组。 由于每个存储空间有M组子空间,经过上述处理,所有这些方法都得到了M个运动标识。 M个运动标识符可以表示在某个轴上的运动轨迹,如在第一种方法中。 当然,第二种方法识别的运动轨迹应该比第一种方法更准确,因为第二种方法消除了用户操作不准确、传感器错误等因素。 [0052] 此外,第一静止值、第二静止值和第三静止值均表示没有运动。 它们相同或不同。 类似地,第一阈值、第二阈值和第三阈值分别代表一定范围。 [0053] 步 204 , 控制器 100 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。 [0054] 本步骤将X轴运动标识、Y轴运动标识和Z轴运动标识进行比较,根据比较结果判断匹配是否成功。 映射的控制命令自动执行,从而在匹配成功时控制移动终端中的应用程序。 [0055] 在本发明的另一实施例中,假设加速度传感器的采样频率为 104 在移动终端中为 400 Hz,即加速度传感器每 0.0025 秒采集一次数据。 即,每秒收集400条X轴数据、400条Y轴数据和400条Z轴数据。 还假设用于存储采样数据的第一存储空间、第二存储空间和第三存储空间中的每一个包括M组子空间,每组子空间包括N个数据单元。 在此,M=8,N=50。 在本实施例中,第一存储空间、第二存储空间和第三存储空间使用队列来表示 1 , 队列 2 , 队列 3 , 分别。 每个队列有 8 个节点,每个节点包含 50 个数据单元。 此外,当采样数据被HI存储时,采样数据以队列头到队列尾的顺序存储。 当所有节点的数据单元都被占用时,删除队列头的数据,并在队列尾插入一个存储新采样数据的节点。 即,在本实施例中,每个队列总是存储最后一次获得的400个采样数据。 采样数据存储在队列以外的另一个数据结构中。 [0056] 此外,在本实施例中还假设控制器 100 具有应用控制设置模块,工作在两种模式下,即运动轨迹预设模式和运动轨迹识别模式。 [0057] 如图。 图3示出了本实施例的方法的流程图。 参考图。 3、控制器 100 允许加速度传感器 104 以 0.0025 秒的速率执行采样,并将在队列中采样中获得的值存储在 X 轴上 1 , 将采样得到的 Y 轴值存储在队列中 2 , 同时将采样得到的 Z 轴值存储在队列中 3 ,当移动终端在步中移动时 300 . [0058] 队列 1 , 2 和 3在这一步中,如图所示。 分别参照图4A至4C。 如上所述,采样数据以队列头到队列尾的顺序存储。 例如,当得到50条采样数据时,将第一组50条数据放在队列的头节点。 0.125秒(50*0.0025秒)后,第二组50个采样数据存储在第二个节点。 再过 0.125 秒,第三组 50 个采样数据存储在第三个节点,以此类推。 当一个队列的8个节点都满时,删除队列头节点的数据,将存储最近获得的50个采样数据的节点存储在队列的尾部。 总之,每个队列 1 , 2 和 3 总是存储最近获取的400条数据。 [0059] 在步骤 302 , 控制器 100 判断应用控制设置模块是否正在运行,如果是,则步骤 304 被执行。 否则,步 306 被执行。 [0060] 在步骤 304 , 控制器 100 确定应用程序控制设置模块的当前模式。 如果当前模式为运动轨迹预置模式,则步骤 312 被执行。 如果当前模式为运动轨迹识别模式,则步骤 306 被执行。 [0061] 在本实施例中,在移动终端中设置应用控制设置模块,通过应用控制设置模块启动运动轨迹预设或运动轨迹识别功能。 但实际应用中并未提供应用控制设置模块。 应用控制设置模块是否存在不影响方案的实现,步骤 302 和 304 可以省略。 [0062] 在步骤 306 , 8 个 X 轴运动标识符由队列中的值确定 1 , 8 个 Y 轴运动标识符由队列中的值确定 2 , 和 8 个 Z 轴运动标识符由队列中的值确定 3 . [0063] 确定8个X轴运动标识可以按照上述步骤x1到x4的方法,确定8个Y轴运动标识可以按照上述步骤y1到y4的方法,确定8个Y轴运动标识 Z轴运动识别可以按照上述步骤z1至z4的方法进行,在此不再赘述。 [0064] 当采样刚刚开始时,队列的所有节点都不会存储采样数据。 例如,只有队列的头节点存储采样数据,而其他节点均不存储 0.125 秒的数据。 因此,只能确定队列头节点对应的运动标识。 0.125 秒后,队列的第二个节点也存储采样数据,如步骤中所述 300 . 因此,可以确定对应于第二节点的运动标识符。 这里,队列和运动标识符没有指定,可以是X轴、Y轴或Z轴。 [0065] 另外,由于操作过程中可能会出现错误,因此在本步骤中,当8个X轴运动标识、8个Y轴运动标识和8个 Z轴运动标识符被确定。 也就是说,在步骤x3和x4之间,该方法还包括在确定8个X轴运动标识时要执行的以下步骤。 判断当前组对应的X轴运动标识是否为0和。 如果是,则计算当前组的 N 个值(X 轴上的 N 个值)的平均值,并将第一个静止值更新为计算的平均值; 否则,返回步骤 x4。 在步骤 y3 和 y4 以及 z3 和 z4 之间可以发生类似的步骤。 [0066]这些步骤用于更新静止值,因为在用户操作过程中,如果当前组数据对应的运动标识为0,则移动终端实质上是静止的。但是,所有的N(本实施例中,N为 50) 由于运算或测量误差,各轴当前组的数据不一定等于静止值。 这样,如果将静止值设置为N个值的平均值,则N个值整体上更接近于静止值,从而避免了移动终端没有被移动被误认为移动的情况。 [0067] 在步骤 308 ,识别出的运动轨迹与预设的运动轨迹相匹配,步 310 如果匹配成功则执行。 否则,过程返回步骤 300 . [0068] 脚步 300 至 308 形成一个大循环,其中加速度传感器 104 移动端连续采样,每0.125秒访问队列。 因此,每0.125秒为移动终端识别运动轨迹。 由于队列中的所有节点都不存储数据,因此确定的 8 个运动标识符不准确,因此识别可能会在采样开始后的第一秒内失败。 但是,队列中的所有节点都存储一秒钟后的采样数据。 因此,可以确定有效的8个运动标识符。 如以上实施例所述,X轴运动标识符、Y轴运动标识符和Z轴运动标识符表示移动终端已经移动的运动轨迹。 在本实施例中,还使用X轴运动标识符、Y轴运动标识符和Z轴运动标识符来表示预设的运动轨迹。 因此,通过比较步骤中确定的8个X轴运动标识符、8个Y轴运动标识符和8个Z轴运动标识符来确定匹配是否成功 306 分别与预设运动轨迹的8个X轴运动标识符、8个Y轴运动标识符和8个Z轴运动标识符。 [0069] 匹配不一定在采样一秒后立即成功。 但是,如步骤中所述 300 ,加速度传感器可以继续采样,可以从移动终端最近获取的采样数据中确定新的运动标识,并与预设的运动轨迹进行匹配。 308 再次。 一旦匹配成功,下一步 310 被执行。 [0070] 步内匹配 308 在实际应用中以精确匹配或近似匹配的方式进行。 精确匹配的方式是指识别出的运动轨迹的8个X轴运动标识符、8个Y轴运动标识符和8个Z轴运动标识符与8个X轴运动标识符、8个Y轴运动标识符相同。 轴运动标识符和预设运动轨迹的 8 个 Z 轴运动标识符。 近似匹配的方式是指三个轴上的运动标识不完全相同,但相同的运动标识对的数量大于预设的匹配阈值。 例如,预设匹配阈值,识别出的运动轨迹的每个轴上的6个和7个运动标识符分别与预设的运动轨迹相同。 在这种情况下,数字 7 大于匹配阈值 6。这将是匹配成功的情况。 [0071] 也可以设置时间阈值。 不再进行识别(即不返回步骤 300 ) 以避免在超过阈值时出现无限循环。 [0072] 在步骤 310 ,执行映射到预设运动轨迹的控制命令,控制移动终端中的应用程序,完成本流程。 [0073] 在步骤 312 , 加速度值使用加速度传感器不断收集 104 移动终端时。 与步骤相同的方法 300 可用于该步骤,此处不再赘述。 [0074] 在步骤 314,从采集的加速度值中识别出移动终端已经移动的运动轨迹,并将识别出的运动轨迹通过显示器显示给用户 106 . [0075] 方法同步骤 306 用于识别运动轨迹。 此外,在识别出运动轨迹后,将运动轨迹可视化为要通过显示器显示给用户的字符 106 为方便用户确认。 [0076] 在步骤 316 ,判断是否接收到用户的确认指令,以及是否通过输入/输出接口接收到确认指令 108 , 步 318 被执行。 否则返回步骤 312 . [0077] 在步骤 318 ,识别出的运动轨迹被保存,此过程完成。 [0078] 预设的运动轨迹分步出现 312 至 318 . 如果移动终端中有应用控制设置模块,该模块还可以提供显示、查找、关联和删除预设运动轨迹的功能,以便用户进行更准确的操作。 脚步 312 至 318 进行预设的运动轨迹,在识别过程中不是必需的。 因此,在识别运动轨迹和控制应用程序时可以省略它们。 [0079] 在应用程序中很容易将控制命令绑定到预设的运动轨迹。 例如,提供一个数据库来存储预设的运动轨迹与控制命令之间的对应关系。 因此,在匹配成功后 308 ,在数据库中查找匹配成功的运动轨迹并执行相应的控制命令。 [0080] 图 5A, 5 乙, 6 一个,和 6 B各自示出了说明根据本发明实施例控制应用的示例。 如图所示。 在图5A中,用户用手持移动终端在空中书写字符“L”。 移动终端在运动过程中形成运动轨迹。 假设该运动轨迹预设在移动终端中,并映射到“打开”应用“记事本”的控制命令,一旦匹配成功,“记事本”就会自动打开。 结果示于图3。 5B。 [0081] 在另一个示例中,如图 3 所示。 参照图6A,用户用手持移动终端在空中书写字符“Z”。 移动终端在运动过程中形成运动轨迹。 假设该动作轨迹预设在移动终端中,并映射到“打开”应用程序“即时通讯”的控制命令,一旦匹配成功,“即时通讯”就会自动打开。 结果示于图3。 6B。 [0082] 应用本实施例,通过加速度传感器识别移动终端运动过程中形成的运动轨迹 104 当用户使用手持移动终端书写时。 当识别出的运动轨迹与预设的运动轨迹匹配成功时,启动相应的控制命令。 从而达到控制应用程序的目的。 用户不仅可以用手持移动终端简单的摇一摇,还可以书写任何文字和图片。 因此,可以形成很多运动轨迹,从而可以映射很多控制命令。 因此,可以通过用户用手持移动终端书写来容易地控制移动终端中的各种应用。 [0083]本发明的实施例可以通过硬件、软件以及硬件和软件的结合来实现。 例如,软件可以存储在易失性或非易失性存储设备中,例如只读存储器(ROM)、随机存取存储器(RAM)、存储芯片、 设备或集成电路,以及光或磁可记录和机器可读的存储介质,例如压缩盘(CD)、数字多功能盘(DVD)、磁盘、磁带等。 可以包括在移动终端中的存储器是包括用于实现本发明的实施例的指令的程序或适合于存储程序的机器可读存储介质的示例。 因此,本发明包括包含代码的程序,以实现在说明书的某些权利要求中陈述的系统或方法,以及存储这种程序的机器可读存储介质。 此外,程序可以通过诸如通过有线或无线连接传输的通信信号之类的特定媒体以电子方式传输。 [0084] 根据本发明实施例的控制移动终端中应用程序的方法可以制作成程序的形式存储在存储介质中,移动终端可以通过下载程序向用户提供应用程序控制( 例如,应用程序)用于控制来自程序提供服务器的应用程序,安装下载的程序,并执行安装的程序。 即,当用于控制应用的程序安装在移动终端中时,执行该程序,然后将应用控制提供给用户。 节目提供服务器从移动终端接收对节目的传输请求,并响应传输请求将节目传输到移动终端。 节目提供服务器可以判断发出节目传输请求的移动终端是否为用户终端,进而进行用户鉴权和支付信息识别。 程序提供服务器可以包括存储程序的存储介质。 此外,存储介质可以位于程序提供服务器内部或程序提供服务器外部。 [0085] 尽管已经参照某些实施例及其附图显示和描述了本发明,但本领域技术人员将理解,在不背离本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变。 由所附权利要求及其等价物定义。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102647504A(String), CN102647504B(String), EP2490104A1(String), EP2490104B1(String), KR101892065B1(String), KR1020120094447A(String), US20120208555A1(String), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102647504A(String), CN102647504B(String), EP2490104A1(String), EP2490104B1(String), KR101892065B1(String), KR1020120094447A(String), US20120208555A1(String), US8914010B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102647504A(String), CN102647504B(String), EP2490104A1(String), EP2490104B1(String), KR101892065B1(String), KR1020120094447A(String), US20120208555A1(String), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.207 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), CN102647504A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), CN102647504B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.247 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.248 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), EP2490104A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), EP2490104B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.266 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), KR101892065B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.279 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), KR1020120094447A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.286 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), US20120208555A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.299 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270710(Integer), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8914010B2(String), US8914010B2(String), 1418659200(Integer), 270710(Integer), 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.323 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.324 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.326 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.327 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185035(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185035(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.338 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.340 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185035(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.341 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.342 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185035(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.351 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.352 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.353 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.363 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.364 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.365 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.366 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185035(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.376 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.378 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120323902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and file browsing method implemented by mobile terminal(String), 移动终端及移动终端实现的文件浏览方法(String), US20120323902A1(String), A mobile terminal and a file browsing method implemented by the mobile terminal are disclosed, including: a scanning module scans the files in the mobile terminal and acquires related information of each file in the mobile terminal; an indexing module creates a global index list according to the related information of the files; and a browsing module classifies and displays the files according to the file types in the global index list while searching a target file. According to the technical solution, the target file can be quickly and conveniently found from the mobile terminal.(String), 本发明公开了一种移动终端及其实现的文件浏览方法,包括:扫描模块对移动终端中的文件进行扫描,获取移动终端中各个文件的相关信息。 索引模块根据文件的相关信息创建全局索引列表; 浏览模块在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 根据本发明的技术方案,可以在移动终端上快速、方便地找到目标文件。(String), US13/581140(String), 1289923200(Integer), US20120323902A1(String), 1355932800(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 1(Integer), US20090106200A1(String), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.388 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.389 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185036(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.390 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c53dff6df5f64a9a94cf77d9ebd42df5.png(String), 185036(Integer), c53dff6df5f64a9a94cf77d9ebd42df5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.398 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.400 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and file browsing method implemented by mobile terminal(String), 移动终端及移动终端实现的文件浏览方法(String), US20120323902A1(String), A mobile terminal and a file browsing method implemented by the mobile terminal are disclosed, including: a scanning module scans the files in the mobile terminal and acquires related information of each file in the mobile terminal; an indexing module creates a global index list according to the related information of the files; and a browsing module classifies and displays the files according to the file types in the global index list while searching a target file. According to the technical solution, the target file can be quickly and conveniently found from the mobile terminal.(String), 本发明公开了一种移动终端及其实现的文件浏览方法,包括:扫描模块对移动终端中的文件进行扫描,获取移动终端中各个文件的相关信息。 索引模块根据文件的相关信息创建全局索引列表; 浏览模块在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 根据本发明的技术方案,可以在移动终端上快速、方便地找到目标文件。(String), US13/581140(String), 1289923200(Integer), US20120323902A1(String), 1355932800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 1(Integer), US20090106200A1(String), \20230420\c53dff6df5f64a9a94cf77d9ebd42df5.png(String), 10(Integer), 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 1. A mobile terminal, comprising a scanning module, an indexing module and a browsing module; wherein,the scanning module is configured to scan files in the mobile terminal and acquire related information of each file in the mobile terminal;the indexing module is configured to create a global index list according to the related information of the each file; andthe browsing module is configured to classify and display the files according to file types in the global index list while searching a target file.(String), 1.移动终端,包括扫描模块、索引模块和浏览模块;其中,扫描模块,用于扫描移动终端中的文件,获取移动终端中每个文件的相关信息;索引模块,用于根据每个文件的相关信息创建全局索引列表;和浏览模块用于在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 2. The mobile terminal according to claim 1, wherein,the browsing module is further configured to trigger the indexing module to update the global index list during manual update of the global index list.(String), 2.根据权利要求1所述的移动终端,其中,浏览模块还用于在手动更新全局索引列表时触发索引模块更新全局索引列表。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 3. The mobile terminal according to claim 1, further comprising: a file reading and writing module, and a searching module; wherein,the file reading and writing module is configured to, after file creation or deletion, create and delete an index item in the global index list through invoking an interface provided by the indexing module;the searching module is configured to search the target file in the global index list according to an input keyword of the target file; andthe browsing module is further configured to display the target file searched out.(String), 3.根据权利要求1所述的移动终端,还包括:文件读写模块和搜索模块;其中,文件读写模块用于在文件创建或删除后,通过调用索引模块提供的接口在全局索引列表中创建和删除索引项。查找模块,用于根据输入的目标文件关键字在全局索引列表中查找目标文件;和浏览模块还用于显示搜索到的目标文件。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 4. A file browsing method, comprising:scanning files in a mobile terminal and acquiring related information of each file in the mobile terminal; creating a global index list according to the acquired related information of the each file;classifying and displaying the files according to file types in the global index list while searching a target file.(String), 4.一种文件浏览方法,包括:扫描移动终端中的文件,获取移动终端中每个文件的相关信息;根据获取的每个文件的相关信息创建全局索引列表;在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 5. The method according to claim 4, wherein the acquiring related information of each file in the mobile terminal comprises:scanning every file node through a read-write interface provided by a file system, acquiring file names and file paths of all the files in a storage medium of the mobile terminal, obtaining extension names of the files based on the file names, and sending the file names, file paths and extension names of the files to an indexing module of the mobile terminal by a scanning module of the mobile terminal.(String), 5.根据权利要求4所述的方法,其中获取移动终端中每个文件的相关信息包括:通过文件系统提供的读写接口扫描每个文件节点,获取移动终端存储介质中所有文件的文件名和文件路径,根据文件名获取文件的扩展名,发送移动终端的扫描模块将文件的文件名、文件路径和扩展名传给移动终端的索引模块。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 6. The method according to claim 4, wherein the creating a global index list according to the acquired related information of the each file comprises:creating one index item for the each file by an indexing module of the mobile terminal according to the related information of the each file which is received by the index module;wherein index items of all the files constitute the global index list; each index item in the global index list includes a file name, a file path, an extension name, a file type and a file subtype of each file.(String), 6.根据权利要求4所述的方法,其中根据获取的每个文件的相关信息创建全局索引列表包括:移动终端的索引模块根据索引模块接收到的每个文件的相关信息,为每个文件创建一个索引项;其中,所有文件的索引项构成全局索引列表;全局索引列表中的每个索引项包括每个文件的文件名、文件路径、扩展名、文件类型和文件子类型。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 7. The method according to claim 6, further comprising:periodically updating the global index list by the indexing module; or after a new storage card is inserted into the mobile terminal, automatically updating the global index list by the indexing module; or after file creation or deletion, creating and deleting the index items in the global index list by a file reading and writing module of the mobile terminal through invoking an interface provided by the indexing module; or during manual update of the global index list, triggering the indexing module to update the global index list by a browsing module of the mobile terminal.(String), 7.根据权利要求6所述的方法,还包括:索引模块周期性更新全局索引列表;或者移动终端插入新的存储卡后,索引模块自动更新全局索引列表;或者,在文件创建或删除后,移动终端的文件读写模块通过调用索引模块提供的接口,在全局索引列表中创建和删除索引项。或者,在手动更新全局索引列表时,通过移动终端的浏览模块触发索引模块更新全局索引列表。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 8. The method according to claim 6, wherein the classifying and displaying the files according to file types in the global index list comprises:reading the global index list via an interface of the indexing module of the mobile terminal, classifying and displaying the files according to the file types and file sub-types of the files in the global index list by a browsing module of the mobile terminal.(String), 8.根据权利要求6所述的方法,其中将全局索引列表中的文件按文件类型分类显示包括:通过移动终端的索引模块的接口读取全局索引列表,移动终端的浏览模块根据全局索引列表中文件的文件类型和文件子类型对文件进行分类显示。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 9. The method according to claim 8, further comprising:selecting a file type of the target file from the file types displayed by the browsing module; displaying one or a plurality of file subtypes of this file type, selecting one file subtype from the plurality of file subtypes, displaying all files under this file subtype and selecting the target file from the all files under this file subtype by the browsing module.(String), 9.根据权利要求8所述的方法,还包括:从浏览模块显示的文件类型中选择目标文件的文件类型;浏览模块显示该文件类型的一个或多个文件子类型,从多个文件子类型中选择一个文件子类型,显示该文件子类型下的所有文件,并从该文件子类型下的所有文件中选择目标文件。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185036(Integer), 10. The method according to claim 9, further comprising:inputting a keyword of the target file;searching the target file in the global index list by a searching module of the mobile terminal according to the keyword, and displaying the found target file by the searching module.(String), 10.根据权利要求9所述的方法,还包括:输入目标文件的关键字;通过移动终端的搜索模块根据关键字在全局索引列表中搜索目标文件,并通过搜索模块显示搜索到的目标文件。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.497 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185036(Integer), TECHNICAL FIELD [0001]The present disclosure relates to the file browsing field of mobile terminals, particularly to a mobile terminal and a file browsing method implemented by the mobile terminal. BACKGROUND [0002]With the rapid development of mobile terminal technology, people make higher demands on both the function and convenience of mobile terminals. In the related art, the functions of mobile terminals are getting richer and the files used in mobile terminals keep increasing, including: text files such as short messages and e-books; hyper text files such as multimedia messages and mails; audio files; image files; video files; flash files; executable programs, and etc. Moreover, the storage space of mobile terminals, particularly intelligent mobile terminals, is increasing. Built-in flash, external flash storage cards and micro hard disks all become the storage media of mobile terminals. Consequently, the total storage capacity of a mobile terminal can be tens of Gigabytes (GB). [0003]In a mobile terminal, conventional file storage is organized in the form of directory tree, and different files are stored in different directories of different storage media. The thinking habit of a user who wants to browse files is that when he/she wants to browse an image, a video or a mail, firstly he/she thinks of the type of a target file. [0004]However, the form of the directory tree in the related art does not accord with user's thinking habit. When files are organized in the form of directory tree, a user can not find a target file unless he/she knows both the name and directory of the target file. Moreover, when a directory tree is adopted, a link is not established between a file type and a file position, and thus no prompt about the position of the target file is provided. Further, a mobile terminal has numerous storage media and directories, therefore it is unlikely for a user to quickly find a target file when browsing a target file, because he/she can not remember the storage path of the target file. [0005]Furthermore, mobile terminals have smaller screens and keyboards than computers do, the content displayed on a screen of a mobile terminal is limited, and it is rather inconvenient to perform scrolling, page turning and other operations, thereby increasing the difficulty of a user when he/she searches a target file from enormous files. SUMMARY [0006]In view of the above facts, the main object of the present disclosure is to provide a mobile terminal and a file browsing method implemented by the mobile terminal, which can conveniently and quickly find a target file in the mobile terminal. [0007]To achieve the foregoing object, the technical solution of the present disclosure is realized in the following way. [0008]The present disclosure provides a mobile terminal, including: a scanning module, an indexing module and a browsing module, wherein,[0009]the scanning module is configured to scan files in the mobile terminal and acquire related information of each file in the mobile terminal; [0010]the indexing module is configured to create a global index list according to the related information of the each file; and[0011]the browsing module is configured to classify and display the files according to file types in the global index list while searching a target file. [0012]In the foregoing mobile terminal,[0013]the browsing module may be further configured to trigger the indexing module to update the global index list during manual update of the global index list. [0014]The foregoing mobile terminal may further include: a file reading and writing module, and a searching module, wherein,[0015]the file reading and writing module is configured to, after file creation or deletion, create and delete an index item in the global index list through invoking an interface provided by the indexing module; [0016]the searching module is configured to search the target file in the global index list according to an input keyword of the target file; and[0017]the browsing module is further configured to display the target file searched out.[0018]The present disclosure provides a file browsing method, including:[0019]scanning files in a mobile terminal and acquiring related information of each file in the mobile terminal; creating a global index list according to the acquired related information of the each file; [0020]classifying and displaying the files according to file types in the global index list while searching a target file. [0021]In the foregoing method, the acquiring related information of each file in the mobile terminal may include: [0022]scanning every file node through a read-write interface provided by a file system, acquiring file names and file paths of all the files in a storage medium of the mobile terminal, obtaining extension names of the files based on the file names, and sending the file names, file paths and extension names of the files to an indexing module of the mobile terminal by a scanning module of the mobile terminal. [0023]In the foregoing method, the creating a global index list according to the acquired related information of the each file may include: [0024]creating one index item for the each file by an indexing module of the mobile terminal according to the related information of the each file which is received by the index module; [0025]wherein index items of all the files constitute the global index list; each index item in the global index list includes a file name, a file path, an extension name, a file type and a file subtype of each file. [0026]The foregoing method may further include: [0027]periodically updating the global index list by the indexing module; or after a new storage card is inserted into the mobile terminal, automatically updating the global index list by the indexing module; or after file creation or deletion, creating and deleting the index items in the global index list by a file reading and writing module of the mobile terminal through invoking an interface provided by the indexing module; or during manual update of the global index list, triggering the indexing module to update the global index list by a browsing module of the mobile terminal. [0028]In the foregoing method, the classifying and displaying the files according to file types in the global index list may include: [0029]reading the global index list via an interface of the indexing module of the mobile terminal, classifying and displaying the files according to the file types and file sub-types of the files in the global index list by a browsing module of the mobile terminal. [0030]The foregoing method may further include: [0031]selecting a file type of the target file from the file types displayed by the browsing module; displaying one or a plurality of file subtypes of this file type, selecting one file subtype from the plurality of file subtypes, displaying all files under this file subtype and selecting the target file from the all files under this file subtype by the browsing module. [0032]The foregoing method may further include: [0033]inputting a keyword of the target file; [0034]searching the target file in the global index list by a searching module of the mobile terminal according to the keyword, and displaying the found target file by the searching module. [0035]In the mobile terminal provided by the present disclosure and the file browsing method implemented by the mobile terminal, after the scanning module scans the files in the mobile terminal, the indexing module creates a global index list according to a scanning result. When a target file is found, the browsing module classifies and displays the files so that all video files in the mobile terminal are displayed under a video directory, and all audio files are displayed under an audio directory. The method by which enormous files in the mobile terminal are managed based on file types is more accordant with users' habits, so it increases the speed of searching a target file and can conveniently and quickly find the target file from the enormous files of the mobile terminal. The present disclosure is featured by simple operation, is particularly applicable to the mobile terminals with a small screen and a small keyboard, even without a keyboard, and significantly improves user experience and has a great market promotion value and a practical value. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a structural schematic diagram of composition of a mobile terminal provided by the present disclosure; and [0037]FIG. 2 is a flow schematic diagram of realization of a file browsing method provided by the present disclosure. DETAILED DESCRIPTION [0038]The basic idea of the present disclosure is: a scanning module scans files in a mobile terminal and acquires related information of each file in the mobile terminal; an indexing module creates a global index list according to the related information of the each file; a browsing module classifies and displays the files according to file types in the global index list while searching a target file.. [0039]The present disclosure will now be described with reference to the accompanying drawings and embodiments. [0040]FIG. 1 is a structural schematic diagram of composition of a mobile terminal provided by the present disclosure. As shown in FIG. 1, the mobile terminal comprises: a scanning module 11, an indexing module 12 and a browsing module 13; wherein, the scanning module 11 is configured to scan files in the mobile terminal and acquire related information of each file in the mobile terminal; [0041]the indexing module 12 is configured to create a global index list according to the related information of the each file; [0042]the browsing module 13 is configured to classify and display the files according to file types in the global index list while searching a target file. [0043]The browsing module 13 is further configured to trigger the indexing module 12 to update the global index list during manual update of the global index list. [0044]The mobile terminal further comprises: a file reading and writing module 14 and a searching module 15; wherein, [0045]the file reading and writing module 14 is configured to, after file creation or deletion, create and delete an index item in the global index list through invoking a CreatFileIndexItem interface and a DelFileIndexItem interface provided by the indexing module; [0046]the searching module 15 is configured to search the target file in the global index list according to an input keyword of the target file. [0047]The browsing module 13 is further configured to display the target file searched out. [0048]That the scanning module 11 acquires the related information of the each file in the mobile terminal refers to that: the scanning module 11 scans each file through a read-write interface provided by an existing file system in the mobile terminal, acquires file names and file paths of all the files in a storage medium of the mobile terminal, obtains extension names of the files based on the file names, and sends the file names, file paths and extension names of the files to the indexing module 12 of the mobile terminal. [0049]That the indexing module 12 creates a global index list according to the acquired related information of the each file refers to that: the indexing module 12 creates one index item for each file according to received related information of the each file. The index items of all the files constitute the global index list. Each index item in the global index list includes the file name, file path, an extension name, file type and file sub-type of each file. [0050]That the browsing module 13 classifies and displays the files according to file types in the global index list refers to that: the browsing module 13 reads the global index list via the GetFileIndexItem interface provided by the indexing module 12, organizes the files according to the file types and file sub-types of the files in the global index list, and classifies and displays the files. [0051]Based on the mobile terminal shown in FIG. 1, the present disclosure also provides a file browsing method for the mobile terminal. FIG. 2 is a flow schematic diagram of realization of the file browsing method provided by the present disclosure. As shown in FIG. 2, the method includes the following steps: [0052]Step 201, scanning files in the mobile terminal and acquiring related information of each file in the mobile terminal; [0053]specifically, the files in the mobile terminal are organized by an existing file system and stored in a storage medium in the mobile terminal. The file system contains a plurality of file nodes. Each file node corresponds to one file. A file node stores the file name, file path, file attribute and other related information of a file. All the file nodes are organized into a tree structure. The scanning module of the mobile terminal scans every file node through a read-write interface provided by the file system, and acquires the file names, file paths and other related information of all the files in the storage medium of the mobile terminal. A file name is a string. The part behind “.” of a string is the extension name of the string. The scanning module obtains the extension name of a file from a file name. [0054]Whenever the scanning module acquires related information of a file, it sends the related information to the indexing module via the CreatFileIndexItem interface provided by the indexing module of the mobile terminal. The related information includes the file name, file path and extension name of the file. [0055]Step 202, creating a global index list according to the acquired related information of the each file. [0056]Specifically, the indexing module of the mobile terminal creates an index item for every file according to the received related information of the each file. The index items of all the files constitute the global index list. Each index item in the global index list includes the file name, file path, extension name, file type, file sub-type and other fields of the file. The file type and file sub-type are set by the indexing module according to the extension name or file path of the file during the creation of an index item. Each index item corresponds to one file type and one file sub-type. The rule for correspondence between files and file types and that between files and file sub-types can be set through the SetFileTypeRule interface and SetFileSub-typeRule interface of the indexing module, separately. The correspondence rule may be that a specific extension name corresponds to a specific file type, or a specific file path corresponds to a specific file type. The file type may be audio, video, image, or text, etc.. The file sub-types are the further division of a file type, the specific division rule of which can be set through the SetFileSub-typeRule interface of the indexing module; for example, the file sub-type of audio can be mp3, wma or ogg, etc., and alternatively, file sub-types of audio can be classified by music styles, and etc. [0057]Wherein, when the indexing module sets a file type and a file sub-type in an index item, firstly it searches a file type corresponding to a file from among the existing file types according to the rule for correspondence between files and file types; when the file type is found, it sets the file type of the file to which the index item corresponds as the found file type. Then it searches a file sub-type corresponding to the file from among the existing file sub-types according to the rule for correspondence between files and file sub-types; when the file sub-type is found, it sets the file sub-type of the file to which the index item corresponds as the found file sub-type. If the corresponding file type is not found, it creates a new file type and set the file type of the file to which the index item corresponds as “Others” type; for example, the file type to which a file with an extension name of mp3 corresponds is audio, and the file type to which a file with an extension name of jpeg corresponds is image. [0058]The indexing module can also automatically update the global index list, periodically. The period can be determined based on a file increase/decrease frequency, which can be set as one day, one week or other time. When the indexing module automatically updates the global index list, it can trigger the scanning module to scan all the files in the storage of the mobile terminal. The update strategy may be that the indexing module deletes the existing global index list before update, and then re-creates a global index list according to the related information of the files sent by the scanning module, or the scanning module reads related information of a file from file nodes, and searches the file to which the related information corresponds in the global index list according to the related information of the file; If the file can be found, it means the file exists already; otherwise, the scanning module needs to send the related information of the file to the indexing module, then the indexing module creates a new index item in the global index list. [0059]Furthermore, when a new storage card is inserted into the mobile terminal, the indexing module can also automatically update the global index list. After file creation or deletion, the file reading and writing module of the mobile terminal can create and delete the index items in the global index list through invoking the CreatFileIndexItem interface and DelFileIndexItem interface provided by the indexing module. The modules in the mobile terminal may invoke the interfaces of the indexing module by function invocation or through a command. When the global index list is manually updated, the browsing module triggers the indexing module to update the global index list. [0060]Step 203, classifying and displaying the files according to the file types in the global index list while searching a target file. [0061]Specifically, during search of a target file, the browsing module of the mobile terminal is triggered by a key of the mobile terminal. The triggered browsing module reads the global index list through the GetFileIndexItem interface of the indexing module. According to the file types and file sub-types of the files in the global index list, the browsing module classifies and displays the files. For example, audio files, video files, text files and image files are displayed by the browsing module. [0062]The type of the target file is selected from the file types displayed by the browsing module. The browsing module displays one or a plurality of file sub-types under this file type and then selects one file sub-type from the plurality of file sub-types. The browsing module displays all the files under this file sub-type and selects the target file from them. For example, an image is needed to be inserted during edition of a multimedia message, the browsing module is triggered, and displays all image files stored in the mobile terminal; if there are many files under a file type or a file sub-type, the searching module of the mobile terminal may be triggered in order to find the target file faster. The keyword of the target file is input to the searching module, and the searching module searches the target file from among the files under this file type or file sub-type in the global index list; and then the target file is displayed through the browsing module. [0063]The foregoing descriptions are preferred embodiments of the present disclosure and are not intended to limit the present disclosure. All modifications, equivalent substitutes and improvements made without departing from the spirit and principle of the present disclosure shall be within the protection scope of the present disclosure.(String), 技术领域 [0001] 本发明涉及移动终端的文件浏览领域,尤其涉及一种移动终端及其实现的文件浏览方法。 背景 [0002] 随着移动终端技术的飞速发展,人们对移动终端的功能和便利性提出了更高的要求。 相关技术中,移动终端的功能越来越丰富,移动终端使用的文件也在不断增加,包括:短信、电子书等文本文件; 彩信、邮件等超文本文件; 音频文件; 图像文件; 视频文件; 闪存文件; 可执行程序等。而且,移动终端,特别是智能移动终端的存储空间越来越大。 内置闪存、外置闪存卡和微型硬盘都成为移动终端的存储介质。 因此,移动终端的总存储容量可以达到数十千兆字节(GB)。 [0003] 在移动终端中,传统的文件存储是以目录树的形式组织的,不同的文件存储在不同存储介质的不同目录下。 想要浏览文件的用户的思维习惯是,当他/她想要浏览图片、视频或邮件时,他/她首先想到的是目标文件的类型。 [0004] 然而,相关技术中目录树的形式并不符合用户的思维习惯。 当文件以目录树的形式组织时,用户除非知道目标文件的名称和目录,否则无法找到目标文件。 而且,当采用目录树时,文件类型和文件位置之间没有建立联系,因此不提示目标文件的位置。 进一步地,移动终端的存储介质和目录众多,用户在浏览目标文件时不太可能快速找到目标文件,因为他/她记不住目标文件的存储路径。 [0005] 此外,移动终端的屏幕和键盘都比电脑小,移动终端屏幕显示的内容有限,进行滚动、翻页等操作较为不便,增加了用户使用时的难度。 /she 从大量文件中搜索目标文件。 概括 [0006] 鉴于上述情况,本发明的主要目的在于提供一种移动终端及其实现的文件浏览方法,能够方便快捷地在移动终端中找到目标文件。 [0007] 为实现上述目的,本发明的技术方案是通过以下方式实现的。 [0008] 本发明提供了一种移动终端,包括:扫描模块、索引模块和浏览模块,其中, [0009]扫描模块,用于扫描移动终端中的文件,获取移动终端中每个文件的相关信息; [0010] 索引模块,用于根据每个文件的相关信息创建全局索引列表; 和 [0011] 浏览模块,用于在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0012] 在上述移动终端中, [0013] 浏览模块还可以用于在手动更新全局索引列表时触发索引模块更新全局索引列表。 [0014] 上述移动终端还可以包括:文件读写模块和搜索模块,其中, [0015] 文件读写模块用于在文件创建或删除后,通过调用索引模块提供的接口在全局索引列表中创建和删除索引项。 [0016] 查找模块,用于根据输入的目标文件关键字在全局索引列表中查找目标文件; 和 [0017] 浏览模块还用于显示搜索到的目标文件。[0018] 本发明提供一种文件浏览方法,包括:[0019] 扫描移动终端中的文件,获取移动终端中每个文件的相关信息; 根据获取的每个文件的相关信息创建全局索引列表; [0020] 在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0021] 上述方法中,获取移动终端中各文件的相关信息可以包括: [0022] 通过文件系统提供的读写接口扫描每个文件节点,获取移动终端存储介质中所有文件的文件名和文件路径,根据文件名获取文件的扩展名,发送 移动终端的扫描模块将文件的文件名、文件路径和扩展名传给移动终端的索引模块。 [0023]上述方法中,根据获取的每个文件的相关信息创建全局索引列表可以包括: [0024] 移动终端的索引模块根据索引模块接收到的每个文件的相关信息,为每个文件创建一个索引项; [0025] 其中,所有文件的索引项构成全局索引列表; 全局索引列表中的每个索引项包括每个文件的文件名、文件路径、扩展名、文件类型和文件子类型。 [0026] 上述方法还可以包括: [0027] 索引模块周期性更新全局索引列表; 或者移动终端插入新的存储卡后,索引模块自动更新全局索引列表; 或者,在文件创建或删除后,移动终端的文件读写模块通过调用索引模块提供的接口,在全局索引列表中创建和删除索引项。 或者,在手动更新全局索引列表时,通过移动终端的浏览模块触发索引模块更新全局索引列表。 [0028] 上述方法中,所述根据文件类型对全局索引列表中的文件进行分类展示可以包括: [0029] 通过移动终端的索引模块的接口读取全局索引列表,移动终端的浏览模块根据全局索引列表中文件的文件类型和文件子类型对文件进行分类显示。 [0030] 上述方法还可以包括: [0031] 从浏览模块显示的文件类型中选择目标文件的文件类型; 浏览模块显示该文件类型的一个或多个文件子类型,从多个文件子类型中选择一个文件子类型,显示该文件子类型下的所有文件,并从该文件子类型下的所有文件中选择目标文件。 [0032] 上述方法还可以包括: [0033] 输入目标文件的关键字; [0034] 通过移动终端的搜索模块根据关键字在全局索引列表中搜索目标文件,并通过搜索模块显示搜索到的目标文件。 [0035] 本发明提供的移动终端及其实现的文件浏览方法中,扫描模块扫描移动终端中的文件后,索引模块根据扫描结果创建全局索引列表。 当找到目标文件时,浏览模块将文件分类显示,使得移动终端中的所有视频文件显示在video目录下,所有音频文件显示在audio目录下。 这种基于文件类型管理移动端海量文件的方式更符合用户的使用习惯,提高了查找目标文件的速度,可以方便快捷地从手机海量文件中找到目标文件。 终端。 本发明操作简单,特别适用于小屏幕、小键盘甚至无键盘的移动终端,显着提高了用户体验,具有很大的市场推广价值和实用价值。 附图的简要说明 [0036] 图1为本发明提供的移动终端的组成结构示意图; 和 [0037] 图2为本发明提供的文件浏览方法的实现流程示意图。 详细说明 [0038] 本发明的基本思想是:扫描模块扫描移动终端中的文件,获取移动终端中每个文件的相关信息; 索引模块根据每个文件的相关信息创建全局索引列表; 浏览模块在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0039] 现在将参考附图和实施例描述本公开。 [0040] 图1为本发明提供的移动终端的组成结构示意图。 如图1所示,该移动终端包括:扫描模块 11 , 索引模块 12 和一个浏览模块 13 ; 其中,扫描模块 11 用于扫描移动终端中的文件,获取移动终端中每个文件的相关信息; [0041] 索引模块 12 用于根据每个文件的相关信息创建全局索引列表; [0042] 浏览模块 13 用于在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0043] 浏览模块 13 进一步配置为触发索引模块 12 在手动更新全局索引列表期间更新全局索引列表。 [0044] 移动终端还包括:文件读写模块 14 和一个搜索模块 15 ; 其中, [0045] 文件读写模块 14 用于在创建或删除文件后,通过调用索引模块提供的CreatFileIndexItem接口和DelFileIndexItem接口在全局索引列表中创建和删除索引项; [0046] 搜索模块 15 用于根据输入的目标文件关键字在全局索引列表中查找目标文件。 [0047] 浏览模块 13 还用于显示搜索到的目标文件。 [0048] 即扫描模块 11 获取移动端各个文件的相关信息是指:扫描模块 11 通过移动终端中现有文件系统提供的读写接口扫描每个文件,获取移动终端存储介质中所有文件的文件名和文件路径,根据文件名获取文件的扩展名 ,并将文件的文件名、文件路径和扩展名发送给索引模块 12 的移动终端。 [0049] 索引模块 12 根据获取的各个文件的相关信息创建全局索引列表指的是:索引模块 12 根据接收到的每个文件的相关信息,为每个文件创建一个索引项。 所有文件的索引项构成全局索引列表。 全局索引列表中的每个索引项包括每个文件的文件名、文件路径、扩展名、文件类型和文件子类型。 [0050] 即浏览模块 13 全局索引列表中按文件类型分类显示文件指的是:浏览模块 13 通过索引模块提供的GetFileIndexItem接口读取全局索引列表 12 , 根据全局索引列表中文件的文件类型和文件子类型对文件进行整理,并对文件进行分类展示。 [0051] 基于图1所示的移动终端,本发明还提供了一种移动终端的文件浏览方法。 图2为本发明提供的文件浏览方法的实现流程示意图。 如图2所示,该方法包括以下步骤: [0052] 步 201 、扫描移动终端中的文件,获取移动终端中每个文件的相关信息; [0053]具体地,移动终端中的文件由现有的文件系统组织,存储在移动终端中的存储介质中。 文件系统包含多个文件节点。 每个文件节点对应一个文件。 文件节点存储文件的文件名、文件路径、文件属性等相关信息。 所有的文件节点都被组织成一个树结构。 移动终端的扫描模块通过文件系统提供的读写接口扫描每个文件节点,获取移动终端存储介质中所有文件的文件名、文件路径等相关信息。 文件名是一个字符串。 “.”后面的部分 字符串的扩展名是字符串的扩展名。 扫描模块从文件名中获取文件的扩展名。 [0054] 每当扫描模块获取到文件的相关信息时,通过移动终端索引模块提供的CreatFileIndexItem接口将相关信息发送给索引模块。 相关信息包括文件的文件名、文件路径和扩展名。 [0055] 步 202 ,根据获取的每个文件的相关信息创建全局索引列表。 [0056] 具体地,移动终端的索引模块根据接收到的每个文件的相关信息,为每个文件创建一个索引项。 所有文件的索引项构成全局索引列表。 全局索引列表中的每个索引项包括文件的文件名、文件路径、扩展名、文件类型、文件子类型等字段。 文件类型和文件子类型由索引模块在创建索引项时根据文件的扩展名或文件路径设置。 每个索引项对应一种文件类型和一种文件子类型。 文件与文件类型、文件与文件子类型的对应规则可以分别通过索引模块的SetFileTypeRule接口和SetFileSub-typeRule接口设置。 对应规则可以是特定的扩展名对应特定的文件类型,或者特定的文件路径对应特定的文件类型。 文件类型可以是音频、视频、图片、文本等。文件子类型是文件类型的进一步划分,具体划分规则可以通过索引模块的SetFileSub-typeRule接口设置 ; 例如,音频的文件子类型可以是mp3、wma或ogg等,或者,音频的文件子类型可以按音乐风格等进行分类。 [0057] 其中,索引模块在索引项中设置文件类型和文件子类型时,首先根据文件与文件类型的对应关系规则,从现有的文件类型中查找文件对应的文件类型。 当找到文件类型时,将索引项对应的文件的文件类型设置为找到的文件类型。 然后根据文件与文件子类型的对应关系规则,从现有的文件子类型中查找该文件对应的文件子类型; 当找到文件子类型时,将索引项对应的文件的文件子类型设置为找到的文件子类型。 如果没有找到对应的文件类型,则新建一个文件类型,并将索引项对应的文件的文件类型设置为“Others”类型; 例如,扩展名为mp3的文件对应的文件类型为audio,扩展名为jpeg的文件对应的文件类型为image。 [0058]索引模块还可以定期自动更新全局索引列表。 周期可以根据文件增减频率来确定,可以设置为一天、一周或其他时间。 当索引模块自动更新全局索引列表时,可以触发扫描模块扫描移动终端存储中的所有文件。 更新策略可以是索引模块在更新前删除已有的全局索引列表,然后根据扫描模块发送的文件的相关信息重新创建全局索引列表,或者扫描模块读取一个文件的相关信息 从文件节点中查找文件,根据文件的相关信息在全局索引列表中查找相关信息对应的文件; 如果能找到该文件,说明该文件已经存在; 否则,扫描模块需要将文件的相关信息发送给索引模块,然后索引模块在全局索引列表中创建新的索引项。 [0059] 此外,当移动终端插入新的存储卡时,索引模块还可以自动更新全局索引列表。 在文件创建或删除后,移动终端的文件读写模块可以通过调用索引模块提供的CreatFileIndexItem接口和DelFileIndexItem接口在全局索引列表中创建和删除索引项。 移动终端中的模块可以通过函数调用或命令调用索引模块的接口。 当手动更新全局索引列表时,浏览模块触发索引模块更新全局索引列表。 [0060] 步 203 ,在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0061] 具体地,在搜索目标文件时,移动终端的浏览模块由移动终端的按键触发。 触发浏览模块通过索引模块的GetFileIndexItem接口读取全局索引列表。 浏览模块根据全局索引列表中文件的文件类型和文件子类型,对文件进行分类显示。 例如,浏览模块显示音频文件、视频文件、文本文件和图像文件。 [0062] 目标文件的类型是从浏览模块显示的文件类型中选择的。 浏览模块显示该文件类型下的一个或多个文件子类型,然后从多个文件子类型中选择一个文件子类型。 浏览模块显示该文件子类型下的所有文件,并从中选择目标文件。 例如,编辑彩信时需要插入图片,触发浏览模块,显示移动终端中存储的所有图片文件; 如果一种文件类型或文件子类型下的文件较多,则可以触发移动终端的搜索模块,以便更快地找到目标文件。 将目标文件的关键字输入查找模块,查找模块从全局索引列表中该文件类型或文件子类型下的文件中查找目标文件; 然后通过浏览模块显示目标文件。 [0063] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 凡在本发明的精神和原则的范围内,所做的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.511 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101916164A(String), EP2527965A1(String), EP2527965A4(String), US20120323902A1(String), WO2012019390A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101916164A(String), EP2527965A1(String), EP2527965A4(String), US20120323902A1(String), WO2012019390A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.514 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120323902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.524 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101916164A(String), EP2527965A1(String), EP2527965A4(String), US20120323902A1(String), WO2012019390A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.525 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270711(Integer), CN101916164A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270711(Integer), EP2527965A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.546 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270711(Integer), EP2527965A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270711(Integer), US20120323902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270711(Integer), WO2012019390A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120323902A1(String), US20120323902A1(String), 1355932800(Integer), 270711(Integer), 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.587 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.591 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185036(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.592 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185036(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.599 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.600 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.601 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185036(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185036(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.612 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.613 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.614 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.616 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.617 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.618 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.627 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.628 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.629 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.630 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.631 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185036(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.638 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130132567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, method and system for shielding mobile terminal from accessing wireless network information(String), 移动终端、屏蔽移动终端访问无线网络信息的方法及系统(String), US20130132567A1(String), The present invention relates to the technical field of information processing and provides a method for shielding a mobile terminal from accessing wireless network information, which is applied to ensure the mobile terminal to shield the information in a wireless network. The method comprises the steps of: receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command; querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; and generating a prompt according to the evaluation of the domain name. The present invention also provides a mobile terminal capable of shielding the information in the wireless network. The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information.(String), 本发明涉及信息处理技术领域,提供了一种屏蔽移动终端访问无线网络信息的方法,用于保证移动终端屏蔽无线网络中的信息。 该方法包括:接收访问命令,根据访问命令中的网页地址获取对应的域名。 查询域名的域名评价记录,获取域名评价,其中,域名评价记录包括域名和域名评价; 并根据对域名的评价产生提示。 本发明还提供了一种能够屏蔽无线网络中信息的移动终端。 本发明还提供了一种屏蔽移动终端访问无线网络信息的系统。(String), US13/697296(String), 1287590400(Integer), US20130132567A1(String), 1369238400(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080028100A1 | US20100058446A1 | US20130124304A1 | US7743405B2 | US8713188B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185037(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.653 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\491be48de33b407a8d3218a9a66ea4c5.png(String), 185037(Integer), 491be48de33b407a8d3218a9a66ea4c5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, method and system for shielding mobile terminal from accessing wireless network information(String), 移动终端、屏蔽移动终端访问无线网络信息的方法及系统(String), US20130132567A1(String), The present invention relates to the technical field of information processing and provides a method for shielding a mobile terminal from accessing wireless network information, which is applied to ensure the mobile terminal to shield the information in a wireless network. The method comprises the steps of: receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command; querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; and generating a prompt according to the evaluation of the domain name. The present invention also provides a mobile terminal capable of shielding the information in the wireless network. The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information.(String), 本发明涉及信息处理技术领域,提供了一种屏蔽移动终端访问无线网络信息的方法,用于保证移动终端屏蔽无线网络中的信息。 该方法包括:接收访问命令,根据访问命令中的网页地址获取对应的域名。 查询域名的域名评价记录,获取域名评价,其中,域名评价记录包括域名和域名评价; 并根据对域名的评价产生提示。 本发明还提供了一种能够屏蔽无线网络中信息的移动终端。 本发明还提供了一种屏蔽移动终端访问无线网络信息的系统。(String), US13/697296(String), 1287590400(Integer), US20130132567A1(String), 1369238400(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080028100A1 | US20100058446A1 | US20130124304A1 | US7743405B2 | US8713188B2(String), \20230420\491be48de33b407a8d3218a9a66ea4c5.png(String), 14(Integer), 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 1. A method for shielding a mobile terminal from accessing wireless network information, applied for the mobile terminal shielding the information in a wireless network and comprising:receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command;querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; andgenerating a prompt according to the evaluation of the domain name.(String), 1.一种屏蔽移动终端访问无线网络信息的方法,应用于屏蔽无线网络信息的移动终端,以及包括:接收访问命令,根据访问命令中的网页地址获取对应的域名;查询域名的域名评价记录,获取域名的评价,域名评价记录包括域名和域名的评价;和根据域名评价生成提示。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 2. The method for shielding the mobile terminal from accessing the wireless network information according to claim 1, wherein after the step of querying the domain name evaluation record of the domain name is executed, the method further comprises:storing the domain name evaluation record in a cache of the mobile terminal.(String), 2.根据权利要求1所述的屏蔽移动终端访问无线网络信息的方法,其中在执行查询域名的域名评价记录的步骤之后,该方法还包括:将域名评估记录存储在移动终端的缓存中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 3. The method for shielding the mobile terminal from accessing the wireless network information according to claim 2, wherein the domain name evaluation record is acquired in a mode that a domain name evaluation server connected with the mobile terminal accesses a website corresponding to the domain name and evaluates.(String), 3.根据权利要求2所述的屏蔽移动终端访问无线网络信息的方法,其中域名评估记录是通过与移动终端连接的域名评估服务器访问该域名对应的网站进行评估的方式获取的。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 4. The method for shielding the mobile terminal from accessing the wireless network information according to claim 1, wherein the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises:querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal;when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; andwhen the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name.(String), 4.根据权利要求1所述的屏蔽移动终端访问无线网络信息的方法,其中查询域名的域名评价记录,获取域名评价的步骤包括:查询移动终端缓存中是否存在该域名的域名评估记录;当缓存中存在域名的域名评估记录时,根据域名评估记录获取域名的评估;和当缓存中不存在该域名的域名评估记录时,从与移动终端连接的域名评估服务器查询该域名的域名评估记录,获取该域名的评估结果。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 5. The mobile terminal, comprising: a domain name resolution unit, a domain name query unit and an access prompting unit, whereinthe domain name resolution unit is configured to receive the access command and acquire the corresponding domain name according to the webpage address in the access command;the domain name query unit is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; andthe access prompting unit is configured to generate a prompt according to the evaluation of the domain name.(String), 5.移动端,包括:域名解析单元、域名查询单元和访问提示单元,其中域名解析单元用于接收访问命令,并根据访问命令中的网页地址获取对应的域名;域名查询单元,用于查询域名的域名评价记录,获取域名的评价;其中,域名评估记录包括域名和对域名的评估;和访问提示单元用于根据对域名的评估产生提示。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 6. The mobile terminal according to claim 5, further comprising:a cache unit, configured to store the domain name evaluation record after the domain name query unit queries the domain name evaluation record of the domain name.(String), 6.根据权利要求5所述的移动终端,还包括:缓存单元,用于在域名查询单元查询到域名的域名评估记录后,存储域名评估记录。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 7. The mobile terminal according to claim 5, wherein the domain name evaluation record is acquired in a mode that the domain name evaluation server connected with the mobile terminal accesses the website corresponding to the domain name and evaluates.(String), 7.根据权利要求5所述的移动终端,其中域名评估记录是通过与移动终端连接的域名评估服务器访问该域名对应的网站进行评估的方式获取的。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 8. The mobile terminal according to claim 5, wherein the domain name query unit comprises: a cache query module and a switching module, whereinthe cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; andthe switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit.(String), 8.根据权利要求5所述的移动终端,其中域名查询单元包括:缓存查询模块和切换模块,其中缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评估记录;和切换模块,用于当缓存单元中存在域名的域名评估记录时,根据域名评估记录获取域名的评估,并从域中查询域名的域名评估记录域名评估服务器与移动终端连接,当缓存单元中不存在该域名的域名评估记录时,获取该域名的评估结果。9、一种屏蔽移动终端访问无线网络信息的系统,包括:移动终端和域名评估服务器,其中域名评估服务器,用于通过访问域名对应的网站获取域名评估记录,评估并存储域名评估记录;其中,域名评估记录包括域名和对域名的评估;和移动终端包括:域名解析单元、域名查询单元和访问提示单元,其中域名解析单元,用于接收访问命令,根据访问命令中的网页地址获取对应的域名;域名查询单元,用于查询域名的域名评价记录,获取域名的评价;和访问提示单元用于根据对域名的评估产生提示。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 9. A system for shielding a mobile terminal from accessing the wireless network information, comprising: a mobile terminal and a domain name evaluation server, whereinthe domain name evaluation server is configured to acquire a domain name evaluation record by accessing a website corresponding to a domain name and evaluating and store the domain name evaluation record; wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; andthe mobile terminal comprises: a domain name resolution unit, a domain name query unit and an access prompting unit, whereinthe domain name resolution unit is configured to receive an access command and acquire a corresponding domain name according to a webpage address in the access command;the domain name query unit is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; andthe access prompting unit is configured to generate a prompt according to the evaluation of the domain name.(String), 10.根据权利要求9所述的屏蔽移动终端访问无线网络信息的系统,其中域名测评服务器包括:定时更新单元,用于定时启动访问所有网络,获取该域名对应的网站的测评记录并存储测评记录。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 10. The system for shielding the mobile terminal from accessing the wireless network information according to claim 9, wherein the domain name evaluation server comprises: a timing updating unit, configured to be started at time intervals to access all the networks, acquire the evaluation records of the websites corresponding to the domain names and store the evaluation records.(String), 11.根据权利要求2所述的屏蔽移动终端访问无线网络信息的方法,其中查询域名的域名评价记录,获取域名评价的步骤包括:查询移动终端缓存中是否存在该域名的域名评估记录;当缓存中存在域名的域名评估记录时,根据域名评估记录获取域名的评估;和当缓存中不存在该域名的域名评估记录时,从与移动终端连接的域名评估服务器查询该域名的域名评估记录,获取该域名的评估结果。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 11. The method for shielding the mobile terminal from accessing the wireless network information according to claim 2, wherein the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises:querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal;when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; andwhen the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name.(String), 12.根据权利要求3所述的屏蔽移动终端访问无线网络信息的方法,其中查询域名的域名评价记录,获取域名评价的步骤包括:查询移动终端缓存中是否存在该域名的域名评估记录;当缓存中存在域名的域名评估记录时,根据域名评估记录获取域名的评估;和当缓存中不存在该域名的域名评估记录时,从与移动终端连接的域名评估服务器查询该域名的域名评估记录,获取该域名的评估结果。(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 12. The method for shielding the mobile terminal from accessing the wireless network information according to claim 3, wherein the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises:querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal;when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; andwhen the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name.(String), 13.根据权利要求6所述的移动终端,其中域名查询单元包括:缓存查询模块和切换模块,其中缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评估记录;和切换模块,用于当缓存单元中存在域名的域名评估记录时,根据域名评估记录获取域名的评估,并从域中查询域名的域名评估记录域名评估服务器与移动终端连接,当缓存单元中不存在该域名的域名评估记录时,获取该域名的评估结果。(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 13. The mobile terminal according to claim 6, wherein the domain name query unit comprises: a cache query module and a switching module, whereinthe cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; andthe switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit.(String), 14.根据权利要求7所述的移动终端,其中域名查询单元包括:缓存查询模块和切换模块,其中缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评估记录;和切换模块,用于当缓存单元中存在域名的域名评估记录时,根据域名评估记录获取域名的评估,并从域中查询域名的域名评估记录域名评估服务器与移动终端连接,当缓存单元中不存在该域名的域名评估记录时,获取该域名的评估结果。(String), 1(Integer), 12(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.677 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185037(Integer), 14. The mobile terminal according to claim 7, wherein the domain name query unit comprises: a cache query module and a switching module, whereinthe cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; andthe switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.795 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.796 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.797 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185037(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the technical field of information processing, and in particular to a mobile terminal, a method and system for shielding a mobile terminal from accessing wireless network information. BACKGROUND OF THE INVENTION [0002]With the continuous development of the communication technology, wireless Internet access can be implemented and rapidly developed, and it takes an important effect in daily life and work of people. However, different from a conventional communication network, the wireless Internet includes a great amount of independent Wireless Application Protocol (WAP) websites (such as mobile phone websites) and World Wide Web (WWW) websites. These websites operate independently and can be directly or indirectly connected into the wireless Internet by various modes without signing the contract with telecom operators. Currently, thousands of the websites exist, contents broadcast by the websites are more and more complex, the websites are of varying quality and both bad and good websites are mixed up. The matched supervision measures and technical means are not completely provided and cannot be mentioned in the same breath with the supervision mechanism for the fixed Internet, which is formed by years of comprehensive treatment, so that loopholes are provided for criminals to spread obscene, pornographic and violent information and the social “cancer” is formed. [0003]Due to low frequency of a Central Processing Unit (CPU) and small memory space of embedded systems such as mobile terminals (e.g., a mobile phone, a Personal Digital Assistant (PDA) etc..) and the like, browsers operating on the mobile terminals generally only have a function of browsing the web and cannot be used for shielding obscene, pornographic, violent and illegal websites. However, the mobile terminals such as the mobile phone and the like are very common and most of users have a habit of spending leisure time in a mode of surfing the Internet by the mobile phones, so the user possibly contact the pornographic and violent information. Specifically, part of people (specifically, teenagers and the like) are short of awareness of preventing the violent and pornographic websites, and if the people are addicted to the violent and pornographic websites for a long time, the study and life can be seriously influenced so as to cause serious social problems. SUMMARY OF THE INVENTION [0004]The present invention provides a mobile terminal, a method and a system for shielding a mobile terminal from accessing wireless network information, thus the information in a wireless network is shielded according to the requirements of users. [0005]The present invention provides a method for shielding a mobile terminal from accessing the wireless network information, which is used for shielding the information in the wireless network for the mobile terminal. The mobile terminal is provided with a browser configured to access the wireless network. The method comprises: [0006]receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command; [0007]querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record includes the domain name and the evaluation of the domain name; and [0008]generating a prompt according to the evaluation of the domain name. [0009]Preferably, after the step of querying the domain name evaluation record of the domain name is executed, the method further comprises: [0010]storing the domain name evaluation record in a cache of the mobile terminal. [0011]Preferably, the domain name evaluation record is acquired in a mode that a domain name evaluation server connected with the mobile terminal accesses a website corresponding to the domain name and evaluates. [0012]Preferably, the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises: [0013]querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal; [0014]when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; and [0015]when the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name. [0016]The present invention also provides a mobile terminal, comprises a browser configured to access the wireless network. The mobile terminal further comprises: a domain name resolution unit, a domain name query unit and an access prompting unit, wherein [0017]the domain name resolution unit is configured to receive a access command and acquire the corresponding domain name according to the webpage address in the access command; [0018]the domain name query unit is configured to query a domain name evaluation record of the domain name and acquire the evaluation of the domain name; the domain name evaluation record comprises the domain name and the evaluation of the domain name; and [0019]the access prompting unit is configured to generate a prompt according to the evaluation of the domain name. [0020]Preferably, the mobile terminal further comprises: [0021]a cache unit configured to store the domain name evaluation record after the domain name query unit queries the domain name evaluation record of the domain name. [0022]Preferably, the domain name evaluation record is acquired in a mode that a domain name evaluation server connected with the mobile terminal accesses the website corresponding to the domain name and evaluates. [0023]Preferably, the query unit comprises a cache query module and a switching module, wherein [0024]the cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; and [0025]the switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit. [0026]The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information in the wireless network, the system comprises a mobile terminal and a domain name evaluation server, wherein [0027]the domain name evaluation server is configured to acquire a domain name evaluation record by accessing a website corresponding to the domain name and evaluating and store the domain name evaluation record; the domain name evaluation record comprises the domain name and the evaluation of the domain name; and [0028]the mobile terminal is provided with a browser configured to access the wireless network, and the mobile terminal further comprises a domain name resolution unit, a domain name query unit and a access prompting unit, wherein [0029]the domain name resolution unit is configured to receive a access command and acquire the corresponding domain name according to a webpage address in the access command; [0030]the domain name query unit is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; and [0031]the access prompting unit is configured to generate the prompt according to the evaluation of the domain name. [0032]Preferably, the domain name evaluation server comprises a timing updating unit configured to be started at time intervals to access the network, acquire the evaluation record of the website corresponding to the domain name and store the evaluation record. [0033]According to the method for shielding the mobile terminal from accessing the wireless network information, the mobile terminal or the system for shielding the mobile terminal from accessing the wireless network information, which is disclosed by the present invention, the domain name is acquired by resolving the webpage address, so that when the website is accessed, the browser firstly queries the domain name evaluation record of the domain name to acquire the evaluation of the website to be accessed and the user can select to stop accessing the website according to the evaluation to shield the information; furthermore, the browser can store the domain name evaluation record into the mobile terminal, and when accessing the webpage address next time, the browser firstly queries the mobile terminal and queries the domain name evaluation record related to the domain name in the domain name evaluation server if the evaluation record of the domain name corresponding to the webpage address to be accessed does not exist in the mobile terminal so as to further shield the information in the wireless network. BRIEF DESCRIPTION OF THE DRAWINGS [0034]FIG. 1 shows a flowchart of a method for shielding a mobile terminal from accessing wireless network information according to an embodiment of the present invention; [0035]FIG. 2 shows a flowchart of a method for querying a domain name evaluation record and acquiring evaluation of a domain name according to an embodiment of the present invention; [0036]FIG. 3 shows a structural diagram of a mobile terminal according to an embodiment of the present invention; [0037]FIG. 4 shows a structural diagram of a mobile terminal according to another embodiment of the present invention; and [0038]FIG. 5 shows a structural diagram of a system for shielding the mobile terminal from accessing the wireless network information according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0039]The implementation of the aims, the functional characteristics and the advantages of the present invention are further illustrated with reference to the accompanying drawings by combining embodiments. [0040]In the present invention, the mobile terminal can be a mobile phone, a Personal Digital Assistant (PDA) and the like, and the network can be a Wireless Application Protocol (WAP), a World Wide Web (WWW) and the like. By taking the mobile phone as the example, a method for shielding the mobile terminal from accessing wireless network information, the mobile terminal and a system for shielding the mobile terminal from accessing the wireless network information, which are disclosed by the present invention, are described in details as below. It should be understood that the specific embodiments described herein are only used to explain the present invention and shall not be construed as improper limitations on the same. [0041]FIG. 1 shows a flowchart of a method for shielding the mobile terminal from accessing the wireless network information according to an embodiment of the present invention, which is applied for the mobile terminal shielding the information in a wireless network. The mobile terminal is provided with a browser configured to access the wireless network. The method comprises the following steps: [0042]Step 10: the browser receives an access command and acquires a corresponding domain name according to a webpage address in the access command; in one embodiment, a domain name resolution function can be implemented by devices such as a Domain Name System (DNS) and the like, for example, if the webpage address is http://www.xxx.com/news, the corresponding domain name, i.e. www.xxx.com, can be acquired by the DNS. [0043]Step 20: a domain name evaluation record of the domain name is queried and evaluation of the domain name is acquired; the domain name evaluation record comprises the domain name and the evaluation of the domain name; a format of the domain name evaluation record can make reference to the Table 1: TABLE 1Domain nameViolencePornographyIllegality. . .www.xxx.comYesNoNo. . .www.yyy.com.cnNoYesNo. . .www.sina.comNoNoNoNo. . .. . .. . .. . .. . . [0044]There are various modes of acquiring the domain name evaluation record. For example, in one embodiment, a website corresponding to the domain name can be accessed, graphics and texts are identified mutually and the domain name evaluation record with the format shown in the Table 1 is established and stored in a database. In another embodiment, contents in the website can also be acquired and compared by a graphic-text comparing technology so as to acquire the domain name evaluation record and store the domain name evaluation record in the database. The link between the mobile terminal and the database can be established by communication protocols such as a Hyper Text Transfer Protocol (HTTP), a File Transfer Protocol (FTP) and the like so as to query the domain name evaluation record. [0045]There are various options for the format of the Table 1. Preset conditions such as violence, pornography, illegality and the like in the Table 1 can be set according to the requirements of a user, which are not detailed here. [0046]Step 30: a prompt is generated according to the evaluation of the domain name. In an embodiment, if the webpage address to be accessed is http://www.xxx.com/news and the evaluation that the domain name www.xxx.com of the website has violence information exists in the domain name evaluation record, the evaluation is displayed to prompt the user that if the user accesses the website, both the body and the mind of the user are possibly damaged, so that the user can select not to access the website to shield the harmful information. If the violent, pornographic and illegal harmful information does not exist in the website to be accessed, for example, the website to be accessed is http://www.sina.com and the evaluation of the domain name www.sina.com in the domain name evaluation record is normal, the browser directly accesses the website. [0047]By the method, the user can firstly acquire the evaluation of the website to be accessed when accessing the wireless network and can select to stop accessing the website according to the evaluation so as to shield the harmful information, purify the network environment and guarantee the physical and psychological health of the user. [0048]In the embodiment, Step 20 can further comprises a step of the domain name evaluation record is stored in a cache. For example, if acquiring the domain name evaluation of the webpage address corresponding to the domain name by querying the domain name evaluation record, the browser stores the domain name evaluation in the cache for prompting when accessing next time. In the embodiment, the browser is set to firstly query the cache so as to acquire the evaluation of the website corresponding to the domain name, thereby improving the query speed of the domain name evaluation record. [0049]In the embodiment, the domain name evaluation record can be acquired in a mode that a domain name evaluation server accesses the website corresponding to the domain name and evaluates. The domain name evaluation server is a server which is provided by an operator and is configured to carry out related evaluation on the domain name. By accessing all websites, the domain name evaluation server records evaluation information of the websites corresponding to different domain names, for example, whether the pornographic, violent and illegal information exists on the website corresponding to the domain name is recorded. The domain name evaluation server can provide a function of querying the domain name and return the evaluation information of the domain name, i.e. the website with the domain name is a violent, pornographic and illegal website or not. The domain name evaluation server can be provided by the country or a telecom operation corporation. The domain name information can be updated by manually carrying out analysis evaluation and can also be updated by carrying out analysis evaluation on different website domain names according to different modes such as keywords, image identification and the like. [0050]As shown in FIG. 2, Step 20 further comprises the steps of: [0051]Step 21: the browser queries whether the domain name evaluation record of the domain name exists in the cache; for example, in the embodiment, the browser can store the evaluation record of the website corresponding to the domain name when accessing the website last time to the cache so as to query the evaluation record when accessing the website next time. The speed of acquiring the evaluation of the website can be improved by querying a local record. [0052]Step 22: when the domain name evaluation record of the domain name exists in the cache, the evaluation of the domain name is acquired according to the domain name evaluation record; and if the domain name evaluation record exists in the cache, the browser prompts or directly accesses the webpage according to the evaluation corresponding to the domain name. [0053]Step 23: when the domain name evaluation record does not exist in the cache, the domain name evaluation record of the domain name is queried from the domain name evaluation server to acquire the evaluation of the domain name. If the evaluation of the website corresponding to the domain name does not exist in the cache, the domain name evaluation record is queried from the domain name evaluation server to acquire the evaluation of the domain name and then the browser prompts or directly accesses the webpage. [0054]FIG. 3 shows the structure of a mobile terminal 100 according to another embodiment of the present invention. The mobile terminal 100 comprises a browser 10 configured to access wireless networks and shield the information in the wireless networks. The mobile terminal 100 further comprises a domain name resolution unit 11, a domain name query unit 12 and an access prompting unit 13, wherein [0055]the domain name resolution unit 11 is configured to receive the access command and acquire the corresponding domain name according to the webpage address in the access command; in one embodiment, the domain name resolution unit 11 can extract the domain name in the webpage address according to the access command input into the browser 10, for example, in the embodiment, if the webpage address input into the browser 10 is http://www.xxx.com/news, the domain name www.xxx.com can be acquired by the domain name resolution unit 11. In a specific example, in the domain name resolution unit 11, the domain name resolution function can be implemented by devices such as the DNS and the like. [0056]The domain name query unit 12 is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; the domain name evaluation record comprises the domain name and the evaluation of the domain name; in one embodiment, by the domain name query unit 12, an access relation between the browser 10 and the database or the domain name evaluation server can be established and the domain name evaluation record is extracted from the database or the domain name evaluation server so as to query the evaluation of the website corresponding to the domain name. [0057]The access prompting unit 13 is configured to generate a prompt according to the evaluation of the domain name. For example, if a result that the obscene, violent or illegal information exists on the website to be accessed is obtained by carrying out query via the domain name query unit 12, the prompt of the harmful information is displayed by the access prompting unit 13 through a display screen of the mobile phone, or the harmful information is subjected to alarm prompting by voice and the like, so that the user stops continuously accessing the website to be accessed to shield the information. [0058]As shown in FIG. 4, in one embodiment, the mobile terminal 100 further comprises a cache unit 14 configured to store the domain name evaluation record. In general, for accelerating to browser, the browser of the existing mobile phone is provided with the browser cache configured to store documents requested recently into a user disk, and thus, when a visitor requests the page again, the browser can display the documents from the local disk so as to accelerate to browser the page. In the present invention, the evaluation obtained when the website was accessed last time can be stored by the cache of the browser so as to be queried when the website is accessed next time. The domain name query unit 12 further comprises a cache query module 15 and a switching module 16, wherein the cache query module 15 is configured to query the domain name evaluation record in the cache unit 14 to acquire the evaluation of the domain name before the website is accessed next time, thus the speed of querying the domain name can be improved by utilizing the cache query module 15. [0059]the switching module 16 is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record exists in the cache unit 14, and query the domain name evaluation record of the domain name from the domain name evaluation server 200 and acquire the evaluation of the domain name when the domain name evaluation record does not exist in the cache unit 14. [0060]The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information. The system comprises the mobile terminal 100 and the domain name evaluation server 200. As shown in FIG. 5, in one embodiment, the domain name evaluation server 200 is configured to acquire the domain name evaluation record by accessing the website corresponding to the domain name and evaluating and store the domain name evaluation record. The domain name evaluation server 200 communicates with wireless networks by the HTTP, the FTP and the like. The evaluation information of the websites corresponding to different domain names is recorded by accessing all the websites, for example, whether the pornographic, violent and illegal information exists on the website corresponding to the domain name is recorded. The domain name evaluation server can provide the function of querying the domain name and return the evaluation information of the domain name, i.e. the website with the domain name is a violent, pornographic and illegal website or not. The domain name evaluation server can be provided by the country or the telecom operation corporation. The domain name information can be updated by manually carrying out analysis evaluation and can also be updated by carrying out analysis evaluation on different website domain names according to different modes such as keywords, image identification and the like. [0061]In the network, the websites are updated frequently. For acquiring more comprehensive website health information, the website needs to be accessed according to the continuously updated webpage address to extract the domain name of the website and the website health information so as to continuously update the domain name evaluation record. On this basis, the present invention provides another embodiment. In the embodiment, the domain name evaluation server further comprises a timing updating unit 201 configured to be started at time intervals to access the network, acquire the evaluation of the website and update the domain name evaluation record. [0062]The descriptions above are only the preferable embodiment of the present invention, which are not used to restrict the present invention. For those skilled in the art, the present invention may have various changes and variations. Any amendments, equivalent substitutions, improvements, etc. within the principle of the present invention are all included in the scope of the protection of the present invention.(String), 发明领域 [0001] 本发明涉及信息处理技术领域,尤其涉及一种移动终端、屏蔽移动终端访问无线网络信息的方法及系统。 背景技术 [0002] 随着通信技术的不断发展,无线上网得以实现并迅速发展,在人们的日常生活和工作中发挥着重要作用。 然而,与传统的通信网络不同的是,无线互联网包括大量独立的无线应用协议(WAP)网站(如手机网站)和万维网(WWW)网站。 这些网站独立运营,无需与电信运营商签订合同,即可通过多种方式直接或间接接入无线互联网。 目前,网站数以千计,网站播放的内容越来越复杂,网站质量参差不齐,良莠不齐。 配套的监管措施和技术手段不完备,不能与多年综合整治形成的固网监管机制相提并论,为不法分子传播淫秽、色情、色情内容提供了漏洞。 暴力信息,形成社会“毒瘤”。 [0003] 由于中央处理器(CPU)的频率低,以及移动终端(例如,移动电话、个人数字助理(PDA)等)等嵌入式系统的存储空间小,在移动设备上运行的浏览器 终端一般只有浏览网页功能,不能用于屏蔽淫秽、色情、暴力和非法网站。 但是,手机等移动终端非常普遍,大部分用户都有通过手机上网的方式来消磨闲暇时间的习惯,因此用户可能会接触到色情和暴力信息。 具体来说,部分人群(特别是青少年等)缺乏防范暴力色情网站的意识,如果长期沉迷于暴力色情网站,会严重影响学习和生活 从而引发严重的社会问题。 发明内容 [0004] 本发明提供一种移动终端、屏蔽移动终端访问无线网络信息的方法及系统,从而根据用户的需求屏蔽无线网络中的信息。 [0005] 本发明提供一种屏蔽移动终端访问无线网络信息的方法,用于为移动终端屏蔽无线网络中的信息。 移动终端配备有用于访问无线网络的浏览器。 该方法包括: [0006] 接收访问命令,根据访问命令中的网页地址获取对应的域名; [0007] 查询域名的域名评价记录,获取域名评价,其中,域名评价记录包括域名和域名评价; 和 [0008] 根据对域名的评价产生提示。 [0009] 优选地,在执行查询域名的域名评价记录的步骤之后,该方法还包括: [0010] 将域名评价记录保存在移动终端的缓存中。 [0011] 优选地,域名评估记录是通过与移动终端连接的域名评估服务器访问该域名对应的网站并进行评估的方式获取的。 [0012] 优选地,所述查询域名的域名评价记录并获取域名评价的步骤包括: [0013] 查询移动终端缓存中是否存在该域名的域名评价记录; [0014]当缓存中存在该域名的域名评价记录时,根据该域名评价记录获取该域名的评价; 和 [0015] 当缓存中不存在该域名的域名评价记录时,从与移动终端连接的域名评价服务器中查询该域名的域名评价记录,获取该域名的评价。 [0016] 本发明还提供一种移动终端,包括用于访问无线网络的浏览器。 所述移动终端还包括:域名解析单元、域名查询单元和接入提示单元,其中 [0017] 域名解析单元,用于接收访问命令,根据访问命令中的网页地址获取对应的域名。 [0018] 域名查询单元,用于查询域名的域名评价记录,获取对域名的评价。 域名评价记录包括域名和域名评价; 和 [0019] 访问提示单元,用于根据对域名的评价产生提示。 [0020] 优选地,所述移动终端还包括: [0021] 缓存单元,用于在域名查询单元查询到域名的域名评价记录后,存储域名评价记录。 [0022] 优选地,所述域名评估记录是通过与所述移动终端连接的域名评估服务器访问所述域名对应的网站并进行评估的方式获取的。 [0023] 优选地,查询单元包括缓存查询模块和切换模块,其中 [0024] 缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评价记录。 和 [0025] 切换模块,用于当缓存单元中存在域名的域名评价记录时,根据域名评价记录获取域名的评价,并从域中查询该域名的域名评价记录。 与移动终端连接的域名评价服务器,当缓存单元中不存在该域名的域名评价记录时,获取该域名的评价。 [0026] 本发明还提供一种在无线网络中屏蔽移动终端访问无线网络信息的系统,该系统包括移动终端和域名评估服务器,其中 [0027] 域名评估服务器,用于通过访问域名对应的网站获取域名评估记录,并评估并存储域名评估记录。 域名评价记录包括域名和域名评价; 和 [0028] 所述移动终端设置有用于接入无线网络的浏览器,所述移动终端还包括域名解析单元、域名查询单元和接入提示单元,其中 [0029] 域名解析单元,用于接收访问命令,根据访问命令中的网页地址获取对应的域名。 [0030] 域名查询单元,用于查询域名的域名评价记录,获取对域名的评价。 和 [0031] 访问提示单元,用于根据对域名的评估生成提示。 [0032] 优选地,所述域名评价服务器包括定时更新单元,用于定时启动访问网络,获取所述域名对应的网站的评价记录,并存储所述评价记录。 [0033]本发明公开的移动终端访问无线网络信息的屏蔽方法、移动终端或移动终端访问无线网络信息的屏蔽系统,通过解析 网页地址,以便在访问网站时,浏览器首先查询该域名的域名评价记录,获取所访问网站的评价,用户可以根据评价选择停止访问该网站以屏蔽 资料; 另外,浏览器可以将域名评价记录保存到移动终端中,下次访问网页地址时,浏览器首先查询移动终端,在域名评价服务器中查询与该域名相关的域名评价记录 如果要访问的网页地址对应的域名的评价记录在移动终端中不存在,进一步屏蔽无线网络中的信息。 附图的简要说明 [0034] 图1示出了根据本发明实施例的屏蔽移动终端访问无线网络信息的方法的流程图。 [0035] 图2示出了根据本发明实施例的查询域名评价记录和获取域名评价的方法的流程图。 [0036] 图3示出了根据本发明实施例的移动终端的结构图; [0037] 图4示出了根据本发明另一实施例的移动终端的结构图; 和 [0038] 图5示出了根据本发明实施例的移动终端访问无线网络信息的屏蔽系统的结构图。 具体实施方式 [0039] 本发明的目的、功能特点和优点的实现,结合附图,结合实施例作进一步说明。 [0040] 在本发明中,移动终端可以是手机、个人数字助理(PDA)等,网络可以是无线应用协议(WAP)、万维网(WWW)等。 以手机为例,对本发明公开的一种屏蔽移动终端访问无线网络信息的方法、移动终端及屏蔽移动终端访问无线网络信息的系统进行说明。 详情如下。 应当理解,此处所描述的具体实施例仅用于解释本发明,不应理解为对本发明的不当限制。 [0041] 图1示出了根据本发明实施例的屏蔽移动终端访问无线网络信息的方法的流程图,该方法应用于移动终端屏蔽无线网络中的信息。 移动终端配备有用于访问无线网络的浏览器。 该方法包括以下步骤: [0042] 步 10 :浏览器接收访问命令,根据访问命令中的网页地址获取对应的域名。 在一个实施例中,域名解析功能可以通过域名系统(DNS)等设备来实现,例如,如果网页地址为http://www.xxx.com/news,则对应的域 域名,即 www.xxx.com,可以被 DNS 获取。 [0043] 步 20 :查询域名的域名评价记录,获取域名评价; 域名评价记录包括域名和域名评价; 域名评估记录的格式可以参考表1: 表格1 域名 暴力 色情 违法 . . . www.xxx.com 是的 不 不 . . . www.yyy.com.cn 不 是的 不 . . . 新浪网 不 不 不 不 . . . . . . . . . . . . . . . [0044]域名评估记录的获取方式有多种。 例如,在一个实施例中,可以访问该域名对应的网站,图文相互识别,建立如表1所示格式的域名评价记录并存储在数据库中。 在另一个实施例中,还可以通过图文比对技术获取网站中的内容并进行比对,从而获取域名评价记录,并将域名评价记录存储在数据库中。 移动终端与数据库之间可以通过HTTP、FTP等通信协议建立链接,查询域名评价记录。 [0045] 表1的格式有多种选择。表1中预设的暴力、色情、违法等条件可以根据用户的需要进行设置,在此不再赘述。 [0046] 步 30 :根据对域名的评价产生提示。 在一个实施例中,如果要访问的网页地址为http://www.xxx.com/news,并且在域名评价记录中存在该网站的域名www.xxx.com存在暴力信息的评价,则 显示评价提示用户,如果用户访问该网站,用户的身心都可能受到损害,以便用户可以选择不访问该网站,以屏蔽有害信息。 如果要访问的网站不存在暴力、色情、非法有害信息,例如要访问的网站是http://www.sina.com,域名www.sina.com的评价在 域名评价记录正常,浏览器直接访问网站。 [0047] 通过该方法,用户在访问无线网络时,可以首先获取对要访问的网站的评价,并可以根据评价选择停止访问该网站,从而屏蔽有害信息,净化网络环境,保证物理安全。 和用户的心理健康。 [0048] 在本实施例中,步骤 20 还可以包括将域名评价记录存储在缓存中的步骤。 例如,如果浏览器通过查询域名评价记录获得该域名对应的网页地址的域名评价,则浏览器将该域名评价保存在缓存中,以供下次访问时进行提示。 在本实施例中,设置浏览器首先查询缓存,以获取域名对应的网站的评价,从而提高了域名评价记录的查询速度。 [0049] 在本实施例中,可以通过域名评估服务器访问该域名对应的网站并进行评估的方式获取域名评估记录。 域名评估服务器是运营商提供的用于对域名进行相关评估的服务器。 域名评价服务器通过访问所有网站,记录不同域名对应的网站的评价信息,例如记录该域名对应的网站是否存在色情、暴力、非法信息。 域名评价服务器可以提供域名查询功能,返回域名评价信息,即该域名的网站是否为暴力、色情、非法网站。 域名评估服务器可以由国家或电信运营公司提供。 域名信息可以通过人工进行分析评估来更新,也可以根据关键词、图像识别等不同方式对不同的网站域名进行分析评估来更新。 [0050] 如图2所示,步骤 20 进一步包括以下步骤: [0051] 步 21:浏览器查询缓存中是否存在该域名的域名评价记录; 例如,在本实施例中,浏览器可以将上次访问该网站时该域名对应的网站的评价记录存储到缓存中,以便下次访问该网站时查询该评价记录。 通过查询本地记录可以提高获取网站评价的速度。 [0052] 步 22 :当缓存中存在该域名的域名评价记录时,根据该域名评价记录获取该域名的评价; 如果缓存中存在域名评价记录,则浏览器根据该域名对应的评价提示或直接访问网页。 [0053] 步 23 :当缓存中不存在域名评价记录时,向域名评价服务器查询该域名的域名评价记录,获取该域名的评价。 如果缓存中不存在该域名对应的网站的评价,则向域名评价服务器查询域名评价记录,获取该域名的评价,然后浏览器提示或直接访问该网页。 [0054] 图3显示了移动终端的结构 100 根据本发明的另一个实施例。 移动终端 100 包括一个浏览器 10 配置为访问无线网络并屏蔽无线网络中的信息。 移动终端 100 还包括域名解析单元 11 , 一个域名查询单元 12 和访问提示单元 13 , 其中 [0055] 域名解析单元 11 用于接收访问命令,根据访问命令中的网页地址获取对应的域名; 在一个实施例中,域名解析单元 11 可以根据浏览器输入的访问命令提取网页地址中的域名 10 ,例如,在本实施例中,如果网页地址输入到浏览器中 10 是http://www.xxx.com/news,域名www.xxx.com可以被域名解析单位获取 11 . 在一个具体的例子中,在域名解析单元中 11 ,域名解析功能可以通过DNS等设备来实现。 [0056] 域名查询单元 12 用于查询该域名的域名评价记录,获取该域名的评价; 域名评价记录包括域名和域名评价; 在一个实施例中,由域名查询单元 12 , 浏览器之间的访问关系 10 可以建立数据库或域名评价服务器,从数据库或域名评价服务器中提取域名评价记录,以查询该域名对应的网站的评价。 [0057] 接入提示单元 13 配置为根据对域名的评价生成提示。 例如,如果通过域名查询单元查询得到待访问网站上存在淫秽、暴力或非法信息的结果 12 , 有害信息的提示由访问提示单元显示 13 通过手机显示屏,或通过语音等方式对有害信息进行报警提示,使用户停止继续访问要访问的网站,屏蔽信息。 [0058] 如图4所示,在一个实施例中,移动终端 100 还包括缓存单元 14配置为存储域名评估记录。 一般来说,为了加速到浏览器,现有手机的浏览器都会设置浏览器缓存,用于将最近请求的文档存储到用户磁盘中,这样当访问者再次请求该页面时,浏览器就可以显示来自 本地磁盘以加速浏览页面。 在本发明中,可以将上次访问网站时得到的评价保存在浏览器的缓存中,以供下次访问网站时查询。 域名查询单元 12 还包括缓存查询模块 15 和一个开关模块 16 ,其中缓存查询模块 15 用于查询缓存单元中的域名评价记录 14 在下次访问网站前获取域名的评价,利用缓存查询模块提高域名查询速度 15 . [0059] 交换模块 16 用于当域名评价记录存在于缓存单元中时,根据域名评价记录获取对域名的评价 14 ,并从域名评估服务器查询该域名的域名评估记录 200 当缓存单元中不存在域名评价记录时,获取该域名的评价 14 . [0060] 本发明还提供了一种屏蔽移动终端访问无线网络信息的系统。 该系统包括移动终端 100 和域名评估服务器 200 . 如图5所示,在一个实施例中,域名评估服务器 200 用于通过访问域名对应的网站获取域名评价记录并评价并存储域名评价记录。 域名评估服务器 200 通过HTTP、FTP等方式与无线网络进行通信。 通过访问所有网站,记录不同域名对应的网站的评价信息,例如,记录该域名对应的网站是否存在色情、暴力、非法信息。 域名评价服务器可以提供域名查询功能,返回域名评价信息,即该域名的网站是否为暴力、色情、非法网站。 域名评估服务器可以由国家或电信运营公司提供。 域名信息可以通过人工进行分析评估来更新,也可以根据关键词、图像识别等不同方式对不同的网站域名进行分析评估来更新。 [0061] 在网络中,网站更新频繁。 为了获取更全面的网站健康信息,需要根据不断更新的网页地址访问网站,提取网站域名和网站健康信息,从而不断更新域名评估记录。 在此基础上,本发明提供了另一个实施例。 在本实施例中,域名评估服务器还包括定时更新单元 201 配置为定时启动访问网络,获取网站评价,更新域名评价记录。 [0062] 以上所述仅为本发明的较佳实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,本发明可以有各种变化和变化。 凡在本发明的原则之内所作的任何修改、等同替换、改进等,均包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101883180A(String), EP2571229A1(String), EP2571229A4(String), US20130132567A1(String), WO2011140784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101883180A(String), EP2571229A1(String), EP2571229A4(String), US20130132567A1(String), WO2011140784A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20130132567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101883180A(String), EP2571229A1(String), EP2571229A4(String), US20130132567A1(String), WO2011140784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270712(Integer), CN101883180A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270712(Integer), EP2571229A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270712(Integer), EP2571229A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.858 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.859 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270712(Integer), US20130132567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270712(Integer), WO2011140784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.880 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.880 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.880 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20130132567A1(String), US20130132567A1(String), 1369238400(Integer), 270712(Integer), 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.891 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), JIANG, MIN(String), DUAN, YONGJIAN(String), MENG, ZHAO(String), 中兴通讯股份有限公司(String), JIANG MIN(String), DUAN YONGJIAN(String), MENG ZHAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.892 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.893 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185037(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.894 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.895 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185037(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.902 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: JIANG, MIN(String), JIANG MIN(String), 0(Integer), 1681975566(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.914 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: DUAN, YONGJIAN(String), DUAN YONGJIAN(String), 0(Integer), 1681975566(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.925 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: MENG, ZHAO(String), MENG ZHAO(String), 0(Integer), 1681975566(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.936 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185037(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.938 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75955(Integer), 2(Integer), 185037(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.948 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75956(Integer), 2(Integer), 185037(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.955 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.956 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75957(Integer), 2(Integer), 185037(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.965 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.966 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.967 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.968 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.969 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.970 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.977 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.978 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.979 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.980 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185037(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.989 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.990 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10702769B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:06.993 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method for controlling mobile terminal by using touch input device(String), 移动终端及使用触摸输入设备控制移动终端的方法(String), US10702769B2(String), A mobile terminal for providing data to another mobile terminal through a touch input device includes: a touch screen configured to receive a touch input by the touch input device; a communication module configured to transmit and receive data through a communication connection with the touch input device; and a processor configured to, when a first touch input by the touch input device is received by the touch screen, provide, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to the other mobile terminal through the touch input device.(String), 一种通过触摸输入设备向另一移动终端提供数据的移动终端,包括: 触摸屏,用于接收触摸输入设备的触摸输入; 通信模块,被配置为通过与触摸输入设备的通信连接来发送和接收数据; 处理器,被配置为当触摸屏接收到触摸输入设备的第一触摸输入时,向触摸输入设备提供与当前在移动终端中执行的第一应用相关联的预定数据,使得 预定数据通过触摸输入设备提供给其他移动终端。(String), US15/752554(String), 1470931200(Integer), US10702769B2(String), 1594051200(Integer), 1594051200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 20(Integer), KR1020150054588A | KR1020150060364A | US20050025078A1 | US20070021216A1 | US20080256471A1 | US20090054108A1 | US20130046893A1 | US20130091238A1 | US20130106803A1 | US20130136370A1 | US20130181953A1 | US20140059159A1 | US20140059169A1 | US20150091917A1 | US20150135092A1 | US20160364600A1 | US8928587B1 | US9086746B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.002 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.003 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185038(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\452381f36b984a148ac9587542aa45a1.png(String), 185038(Integer), 452381f36b984a148ac9587542aa45a1.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.014 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.015 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for controlling mobile terminal by using touch input device(String), 移动终端及使用触摸输入设备控制移动终端的方法(String), US10702769B2(String), A mobile terminal for providing data to another mobile terminal through a touch input device includes: a touch screen configured to receive a touch input by the touch input device; a communication module configured to transmit and receive data through a communication connection with the touch input device; and a processor configured to, when a first touch input by the touch input device is received by the touch screen, provide, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to the other mobile terminal through the touch input device.(String), 一种通过触摸输入设备向另一移动终端提供数据的移动终端,包括: 触摸屏,用于接收触摸输入设备的触摸输入; 通信模块,被配置为通过与触摸输入设备的通信连接来发送和接收数据; 处理器,被配置为当触摸屏接收到触摸输入设备的第一触摸输入时,向触摸输入设备提供与当前在移动终端中执行的第一应用相关联的预定数据,使得 预定数据通过触摸输入设备提供给其他移动终端。(String), US15/752554(String), 1470931200(Integer), US10702769B2(String), 1594051200(Integer), 1594051200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 20(Integer), KR1020150054588A | KR1020150060364A | US20050025078A1 | US20070021216A1 | US20080256471A1 | US20090054108A1 | US20130046893A1 | US20130091238A1 | US20130106803A1 | US20130136370A1 | US20130181953A1 | US20140059159A1 | US20140059169A1 | US20150091917A1 | US20150135092A1 | US20160364600A1 | US8928587B1 | US9086746B1(String), \20230420\452381f36b984a148ac9587542aa45a1.png(String), 20(Integer), 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.026 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.029 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 1. A mobile device for providing data to another mobile device using a touch input device, the mobile device comprising:a touch screen configured to obtain a touch gesture input by the touch input device, wherein touch gesture inputs are user-defined shapes;a communication module configured to transmit and receive data through a communication connection with the touch input device; andat least one processor configured to provide, to the touch input device in response to obtaining by the touch screen a first touch gesture input from a user, predetermined data having data associated with a first application that is currently being executed in the mobile device and indicating information about an account logged into in the first application,wherein the predetermined data is provided to the other mobile device through the touch input device based on obtaining a second touch gesture input by the other mobile device, wherein the first touch gesture input and the second touch gesture input are different forms,wherein the predetermined data is provided to a second application that matches the first application, and the account is logged into in the second application based on the predetermined data provided, andwherein the predetermined data comprises data indicating information about an address of a webpage of the first application and the logged-in account.(String), 1.一种使用触摸输入设备向另一移动设备提供数据的移动设备,该移动设备包括:触摸屏,用于获取触摸输入设备输入的触摸手势,触摸手势输入为用户自定义形状;通信模块被配置为通过与触摸输入设备的通信连接来发送和接收数据;和至少一个处理器,被配置为响应于通过触摸屏获得来自用户的第一触摸手势输入,向触摸输入设备提供预定数据,该预定数据具有与当前正在移动设备中执行的第一应用相关联的数据并且指示有关在第一个应用程序中登录的帐户的信息,其中,基于获得由另一移动设备输入的第二触摸手势,通过触摸输入设备向另一移动设备提供预定数据,其中,第一触摸手势输入和第二触摸手势输入是不同形式,其中,将预定数据提供给与第一应用相匹配的第二应用,并根据提供的预定数据在第二应用中登录账号,以及其中,预定数据包括指示第一应用程序的网页地址和登录帐户的信息的数据。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 2. The mobile device of claim 1, wherein, based on the first touch gesture input being obtained by the touch screen, the at least one processor is further configured to determine a type of the first touch gesture input and to provide the predetermined data corresponding to the first application and the determined type to the touch input device.(String), 2.如权利要求1所述的移动设备,其中,基于触摸屏获得第一触摸手势输入,至少一个处理器还被配置为确定第一触摸手势输入的类型,并向触摸提供对应于第一应用的预定数据和确定的类型输入设备。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 3. The mobile device of claim 1, wherein, based on the first touch gesture input being obtained by the touch screen, the at least one processor is further configured to control display of a list of the predetermined data associated with the first application on the touch screen and to provide data selected from the displayed list by the user to the touch input device.(String), 3.如权利要求1所述的移动设备,其中,基于触摸屏获得的第一触摸手势输入,至少一个处理器还被配置为控制在触摸屏上显示与第一应用相关联的预定数据的列表,并提供从显示的列表中选择的数据由用户触摸输入设备。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 4. The mobile device of claim 1, wherein the predetermined data associated with the first application comprises at least one of an image or a text selected on an execution screen of the first application by the user, a file that is being edited in the first application, and a multimedia file that is being reproduced in the first application.(String), 4.如权利要求1所述的移动设备,其中与第一应用程序相关联的预定数据包括用户在第一应用程序的执行屏幕上选择的图像或文本、正在第一应用程序中编辑的文件和正在再现的多媒体文件中的至少一个在第一个应用程序中。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 5. The mobile device of claim 1, wherein, based on the second touch gesture input by the touch input device being obtained by a touch screen of the other mobile device, the predetermined data provided to the touch input device is transmitted from the touch input device to the other mobile device, and the transmitted predetermined data is provided to the second application executed by the other mobile device.(String), 5.如权利要求1所述的移动设备,其中,基于触摸输入设备输入的第二触摸手势被另一移动设备的触摸屏获取,将提供给触摸输入设备的预定数据从触摸输入设备传输至另一移动设备,传输的预定数据数据被提供给由另一移动设备执行的第二应用程序。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 6. The mobile device of claim 5, wherein the predetermined data comprises link information for downloading installation data for installing the second application that is the same as the first application.(String), 6.如权利要求5所述的移动设备,其中预定数据包括下载用于安装与第一应用相同的第二应用的安装数据的链接信息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 7. The mobile device of claim 5, wherein the predetermined data comprises setting data for setting the second application that is the same as the first application.(String), 7.如权利要求5所述的移动设备,其中预定数据包括用于设置与第一应用相同的第二应用的设置数据。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 8. The mobile device of claim 5, wherein the predetermined data comprises data indicating a state of the first application based on the first touch gesture input being obtained by the touch screen, anda state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application.(String), 8.如权利要求5所述的移动设备,其中预定数据包括指示基于由触摸屏获得的第一触摸手势输入的第一应用的状态的数据,以及通过使用提供给第二应用程序的预定数据,使第二应用程序的状态与第一应用程序的状态基本相同。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.030 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 9. The mobile device of claim 5, wherein the first application is a web browsing application, and the predetermined data comprises an address of a current webpage of the first application, andthe predetermined data is provided to the second application that is the web browsing application, and a web page corresponding to the address of the current webpage is opened in the second application.(String), 9.如权利要求5所述的移动设备,其中第一应用程序为网页浏览应用程序,预定数据包括第一应用程序的当前网页地址,以及将预定数据提供给第二应用程序即网页浏览应用程序,并在第二应用程序中打开当前网页地址对应的网页。(String), 1(Integer), 8(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 10. The mobile device of claim 5, wherein, in a case where the first application has a multimedia reproduction function and multimedia is paused in the first application based on the first touch gesture input being obtained by the touch screen, the predetermined data comprises data indicating a reproduction state of the multimedia and a paused reproduction position of the multimedia, andthe predetermined data is provided to the second application having the multimedia reproduction function, and reproduction of the multimedia is started in a paused state at a reproduction position in the second application.(String), 10.如权利要求5所述的移动设备,其中,在第一应用具有多媒体播放功能,并且基于触摸屏获得第一触摸手势输入,第一应用暂停多媒体的情况下,预定数据包括指示多媒体的播放状态的数据和暂停的多媒体的再现位置,以及预定数据被提供给具有多媒体再现功能的第二应用,并且多媒体的再现在第二应用中的再现位置处以暂停状态开始。(String), 1(Integer), 9(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 11. The mobile device of claim 5, wherein, in a case where the first application is a game application and a game is paused in the first application based on the first touch gesture input being obtained by the touch screen, the predetermined data comprises data indicating a progress state of the game and a paused position of the game, andthe predetermined data is provided to the second application that is the same as the first application, and the game is started in a paused state at the paused position in the second application.(String), 11.如权利要求5所述的移动设备,其中,在第一应用程序为游戏应用程序且第一应用程序基于触摸屏获得第一触摸手势输入暂停游戏的情况下,预定数据包括指示游戏进行状态的数据和暂停的比赛的位置,和预定数据被提供给与第一应用程序相同的第二应用程序,并且游戏在第二应用程序中的暂停位置处以暂停状态开始。(String), 1(Integer), 10(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 12. The mobile device of claim 5, wherein, in a case where the first application has an account login function, the first application is a web browsing application, and the account is logged into in the first application based on the first touch gesture input being obtained by the touch screen.(String), 12.如权利要求5所述的移动设备,其中,在第一应用具有账号登录功能的情况下,第一应用为网页浏览应用,基于触摸屏获取的第一触摸手势输入在第一应用中登录账号。(String), 1(Integer), 11(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 13. The mobile device of claim 1, wherein, based on a third touch gesture input by the touch input device being obtained by the touch screen, the at least one processor is further configured to receive the predetermined data provided to the touch input device from the touch input device, and to provide the predetermined data received from the touch input device to a third application in the mobile device.(String), 13.如权利要求1所述的移动设备,其中,基于触摸屏获取触摸输入装置输入的第三触摸手势,至少一处理器还用于接收触摸输入装置提供给触摸输入装置的预定数据,并提供预定数据从触摸输入设备接收到移动设备中的第三应用程序。(String), 1(Integer), 12(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 14. A method of controlling a mobile device by using a touch input device, the method comprising:obtaining a first touch gesture input by the touch input device on a touch screen of a first mobile device, wherein touch gesture inputs are user-defined shapes;providing, by the first mobile device, to the touch input device based on obtaining by the touch screen the first touch gesture input from a user, predetermined data having data, associated with a first application that is currently being executed in the first mobile device and indicating information about an account logged into in the first application;obtaining a second touch gesture input by the touch input device on a touch screen of a second mobile device; andproviding the predetermined data stored in the touch input device from the touch input device to the second mobile device based on obtaining the second touch gesture input by the second mobile device, wherein the first touch gesture input and the second touch gesture input are different forms,wherein the predetermined data is provided to a second application that matches the first application, and the account is logged into in the second application based on the predetermined data provided; andwherein the predetermined data comprises data indicating information about an address of a webpage of the first application and the logged-in account.(String), 14.一种通过触摸输入设备控制移动设备的方法,该方法包括:获取触控输入装置在第一移动装置的触控屏幕上输入的第一触控手势,其中触控手势输入为用户自定义形状;第一移动设备基于触摸屏获得用户的第一触摸手势输入,向触摸输入设备提供预定数据,该预定数据具有与第一移动设备中当前正在执行的第一应用相关联的数据,以及指示有关在第一个应用程序中登录的帐户的信息;获取触控输入装置在第二移动装置的触控屏幕上输入的第二触控手势;和基于获得第二移动设备的第二触摸手势输入,将触摸输入设备中存储的预定数据从触摸输入设备提供给第二移动设备,其中第一触摸手势输入和第二触摸手势输入是不同形式,其中,将预定数据提供给与第一应用相匹配的第二应用,并根据提供的预定数据在第二应用中登录账号。和其中,预定数据包括指示第一应用程序的网页地址和登录帐户的信息的数据。(String), 0(Integer), 13(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 15. The method of claim 14, wherein the predetermined data transmitted from the touch input device to the second mobile device is provided to the second application executed by the second mobile device.(String), 15.如权利要求14所述的方法,其中从触摸输入设备发送到第二移动设备的预定数据被提供给由第二移动设备执行的第二应用程序。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 16. The method of claim 15, wherein the predetermined data comprises link information for downloading installation data for installing the second application that is the same as the first application.(String), 16.如权利要求15所述的方法,其中预定数据包括下载用于安装与第一应用相同的第二应用的安装数据的链接信息。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 17. The method of claim 15, wherein the predetermined data comprises setting data for setting the second application that is the same as the first application.(String), 17.如权利要求15所述的方法,其中预定数据包括用于设置与第一应用相同的第二应用的设置数据。(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.031 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 18. The method of claim 15, wherein the predetermined data comprises data indicating a state of the first application based on the first touch gesture input being obtained by the touch screen, anda state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application.(String), 18.如权利要求15所述的方法,其中预定数据包括指示基于由触摸屏获得的第一触摸手势输入的第一应用的状态的数据,以及通过使用提供给第二应用程序的预定数据,使第二应用程序的状态与第一应用程序的状态基本相同。(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 19. The method of claim 14, wherein, based on a third touch gesture input by the touch input device being obtained by the touch screen of the first mobile device, the predetermined data transmitted from the first mobile device to the touch input device is transmitted to the first mobile device and provided to a third application in the first mobile device.(String), 19.如权利要求14所述的方法,其中,基于触摸输入设备输入的第三触摸手势被第一移动设备的触摸屏获取,将第一移动设备发送给触摸输入设备的预定数据发送给第一移动设备,并提供给第三在第一个移动设备中的应用程序。(String), 1(Integer), 18(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.032 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185038(Integer), 20. A computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, causes the computing device to:obtain a first touch gesture input by a touch input device on a touch screen of a first mobile device, wherein touch gesture inputs are user-defined shapes;provide, to the touch input device in response to obtaining by the touch screen the first touch gesture input from a user, predetermined data having data, associated with a first application that is currently being executed in the first mobile device and indicating information about an account logged into in the first application;obtain a second touch gesture input by the touch input device on a touch screen of a second mobile device; andprovide the predetermined data stored in the touch input device from the touch input device to the second mobile device based on obtaining the second touch gesture input by the second mobile device, wherein the first touch gesture input and the second touch gesture input are different forms,wherein the predetermined data is provided to a second application that matches the first application, and the account is logged into in the second application based on the predetermined data provided; andwherein the predetermined data comprises data indicating information about an address of a webpage of the first application and the logged-in account.(String), 20.计算机程序产品包括一种其中存储有计算机可读程序的计算机可读存储介质,其中计算机可读程序当在计算设备上执行时使计算设备:获取触控输入装置在第一移动装置的触控屏幕上输入的第一触控手势,其中触控手势输入为用户自定义形状;响应于触摸屏获得用户的第一触摸手势输入,向触摸输入设备提供预定数据,该预定数据具有与第一移动设备中当前正在执行的第一应用相关联并指示关于账户的信息的数据登录第一个应用程序;取得触控输入装置在第二移动装置的触控屏幕上输入的第二触控手势;和基于获得第二移动设备的第二触摸手势输入,将触摸输入设备中存储的预定数据从触摸输入设备提供给第二移动设备,其中第一触摸手势输入和第二触摸手势输入是不同形式,其中,将预定数据提供给与第一应用相匹配的第二应用,并根据提供的预定数据在第二应用中登录账号。和其中,预定数据包括指示第一应用程序的网页地址和登录帐户的信息的数据。(String), 0(Integer), 19(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185038(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The application is a 371 of International Patent Application No. PCT/KR2016/008877 filed Aug. 12, 2016, which claims priority to Chinese Patent Application No. 201510497976.9 filed Aug. 13, 2015, the disclosures of which are herein incorporated by reference in their entirety. TECHNICAL FIELD [0002]The present invention relates to a mobile terminal and a method of controlling the mobile terminal by using a touch input device, and more particularly, to a mobile terminal for providing data to another mobile terminal through a touch input device and a method of controlling the mobile terminal. BACKGROUND [0003]Recently, as electronic technology continues to develop, the application of touch control technology has gained popularity, and technology for controlling terminals through touch input and the touch input devices have attracted attention. Currently, a stylus pen is one from among representative touch input devices. [0004]The stylus pen may generate a touch input by touching the tip thereof to a touch screen, and may perform a control operation on a screen through a touch on the touch screen. In particular, the stylus pen is more suitable for operations such as writing, screen capture, and the like. For example, screen capture may be performed by designating a region that needs to be captured on the touch screen of the mobile terminal by using the stylus pen, and the captured screen is stored in the mobile terminal. Further, ideas of a user may be recorded at any time by performing writing in a memo application by using the stylus pen. [0005]The control technology of the mobile terminal according to the related art is limited to controlling one terminal through the touch input by using the touch input device. However, when a plurality of terminals are present, there is a need for a control technology capable of continuously executing an application between different terminals through a touch input. SUMMARY [0006]The present disclosure provides a mobile terminal for providing data to another mobile terminal through a touch input device and continuously executing an application, and a method of controlling the mobile terminal. [0007]According to an embodiment, it is possible to transmit data between different terminals through a touch input device and to continuously execute an application. DETAILED DESCRIPTION OF THE DRAWINGS [0008]FIG. 1A is a diagram schematically illustrating data being provided to another terminal through a stylus pen, according to an embodiment. [0009]FIG. 1B is a block diagram illustrating a configuration of a mobile terminal according to an embodiment. [0010]FIG. 2 is a block diagram illustrating an internal configuration of a touch input device according to an embodiment. [0011]FIG. 3 is a diagram illustrating a configuration of a stylus pen according to an embodiment. [0012]FIG. 4 is a diagram illustrating a structure in which the stylus pen according to an embodiment is inserted into the mobile terminal. [0013]FIG. 5 is a flowchart of a method of controlling a mobile terminal by using a touch input device, according to an embodiment. [0014]FIGS. 6 to 8 illustrate transmission and invoking of an image by using the stylus pen, according to an embodiment. [0015]FIGS. 9 to 11 illustrate transmission and invoking of a document file that is being edited in a memo application by using the stylus pen, according to an embodiment. [0016]FIGS. 12 to 14 illustrate continuous execution of a game application by using the stylus pen, according to an embodiment. [0017]FIGS. 15 to 17 illustrate continuous execution of a video streaming application by using the stylus pen, according to an embodiment. [0018]FIGS. 18 to 20 illustrate continuous execution of a web browsing application by using the stylus pen, according to an embodiment. [0019]FIGS. 21 to 23 illustrate continuous execution of a game application having an account login function by using the stylus pen, according to an embodiment. DETAILED DESCRIPTION [0020]In one embodiment, a mobile terminal for providing data to another mobile terminal through a touch input device includes: a touch screen configured to receive a touch input by the touch input device; a communication module configured to transmit and receive data through a communication connection with the touch input device; and a processor configured to, when a first touch input by the touch input device is received by the touch screen, provide, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to the other mobile terminal through the touch input device. [0021]In one embodiment, when the first touch input is received by the touch screen, the processor is further configured to determine a type of the first touch input and provide predetermined data corresponding to the first application and the determined type to the touch input device. [0022]In one embodiment, when the first touch input is received by the touch screen, the processor is further configured to control display of a list of the predetermined data associated with the first application on the touch screen and provide data selected from the displayed list by the user to the touch input device. [0023]In one embodiment, wherein the predetermined data associated with the first application includes at least one of an image or a text selected on an execution screen of the first application by the user, a file that is being edited in the first application, and a multimedia file that is being reproduced in the first application. [0024]In one embodiment, as a second touch input is input to the other mobile terminal by the touch input device, the predetermined data provided to the touch input device is transmitted from the touch input device to the other mobile terminal, and the transmitted predetermined data is provided to a second application executed by the other mobile terminal. [0025]In one embodiment, the predetermined data includes link information for downloading installation data for installing the second application that is the same as the first application. [0026]In one embodiment, the predetermined data includes setting data for setting the second application that is the same as the first application. [0027]In one embodiment, the predetermined data includes data indicating a state of the first application when the first touch input is received by the touch screen, and a state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application. [0028]In one embodiment, the first application is a web browsing application, and the predetermined data includes an address of a current webpage of the first application, and the predetermined data is provided to the second application that is the web browsing application, and a web page corresponding to the address of the webpage is opened in the second application. [0029]In one embodiment, in a case where the first application has a multimedia reproduction function and multimedia is paused in the first application when the first touch input is received by the touch screen, the predetermined data includes data indicating a reproduction state of the multimedia and a paused reproduction position of the multimedia, and the predetermined data is provided to the second application having the multimedia reproduction function, and the reproduction of the multimedia is started in a paused state at the reproduction position in the second application. [0030]In one embodiment, in a case where the first application is a game application and a game is paused in the first application when the first touch input is received by the touch screen, the predetermined data includes data indicating a progress state of the game and a paused position of the game, and the predetermined data is provided to the second application that is the same as the first application, and the game is started in the paused state at the position in the second application. [0031]In one embodiment, in a case where the first application has an account login function and an account is logged into in the first application when the first touch input is received by the touch screen, the predetermined data includes data indicating information about the logged-in account, and the predetermined data is provided to the second application that is the same as the first application, and the account is logged into in the second application. [0032]In one embodiment, when a third touch input by the touch input device is received by the touch screen, the processor is further configured to receive the predetermined data provided to the touch input device from the touch input device, and provide the predetermined data received from the touch input device to a third application in the mobile terminal. [0033]In one embodiment, a method of controlling a mobile terminal by using a touch input device includes: receiving a first touch input by the touch input device on a touch screen of a first mobile terminal; transmitting predetermined data associated with a first application that is currently being executed in the first mobile terminal from the first mobile terminal to the touch input device; receiving a second touch input by the touch input device on a touch screen of a second mobile terminal; and transmitting predetermined data stored in the touch input device from the touch input device to the second mobile terminal. [0034]In one embodiment, the predetermined data transmitted from the touch input device to the second mobile terminal is provided to a second application executed by the second mobile terminal. [0035]In one embodiment, the predetermined data includes link information for downloading installation data for installing the second application that is the same as the first application. [0036]In one embodiment, the predetermined data includes setting data for setting the second application that is the same as the first application. [0037]In one embodiment, the predetermined data includes data indicating a state of the first application when the first touch input is received by the touch screen, and a state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application. [0038]In one embodiment, when a third touch input by the touch input device is received by the touch screen of the first mobile terminal, the predetermined data transmitted from the first mobile terminal to the touch input device is transmitted to the first mobile terminal and provided to a third application in the first mobile terminal. MODE OF THE INVENTION [0039]The advantages and features of the present invention and methods for achieving them will become more apparent from the following embodiments that are described in detail in conjunction with the accompanying drawings. However, it should be understood that the present invention is not limited to the following embodiments, and various modifications can be made without departing from the scope of the present invention. The embodiments set forth herein are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. The present invention should be defined by the appended claims. Like reference numerals are assigned to like elements throughout. [0040]It will be understood that when a region is referred to as being “connected to” or “coupled to” another region, it may be directly connected or coupled to the other region or intervening regions may be present. It will be understood that terms such as “comprise”, “include”, and “have”, when used herein, specify the presence of stated elements, but do not preclude the presence or addition of one or more other elements. In addition, the term “unit” as used herein refers to software or hardware component such as FPGA or ASIC, and “unit” performs certain functions. However, “unit” is not limited to software or hardware. A “unit” may be configured in an addressable storage medium or configured to reproduce one or more processors. Thus, for example, a “unit” includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of programs codes, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and variables. Functions provided in the components and the “units” may be combined with a smaller number of components and “units” or may be separated from additional components and “units.” [0041]Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawing so that those of ordinary skill in the art can easily carry out the embodiments of the present invention. However, an embodiment may be implemented in various different forms and is not limited thereto. In order to clearly describe the embodiment in the drawings, portions not related to the description are omitted. [0042]The terms used herein are those general terms currently widely used in the art in consideration of functions in regard to the inventive concept, but the terms may vary according to the intention of those of ordinary skill in the art, precedents, or new technology in the art. In addition, specified terms may be selected by the applicant, and in this case, the detailed meaning thereof will be described in the detailed description of the inventive concept. Thus, the terms used herein should be understood not as simple names but based on the meaning of the terms and the overall description of the inventive concept. [0043]FIG. 1A is a diagram schematically illustrating that data is provided to another terminal through a stylus pen, according to an embodiment. [0044]Referring to FIG. 1A, when an image edit application is being executed in a mobile terminal 100 and a touch gesture having a shape “C” is input on a touch screen of the mobile terminal 100 by a stylus pen 300 in a state in which a cat image is selected by an operation of the stylus pen 300, the mobile terminal 100 transmits data including the selected cat image to the stylus pen 300 through a wireless communication connection. The data including the cat image is stored in a memory of the stylus pen 300. When an image edit application is being executed in another mobile terminal 101 and a touch gesture having a shape “P” is input on a touch screen of the mobile terminal 101 by the stylus pen 300, the other mobile terminal 101 receives data including the cat image from the stylus pen 300. The received data is provided to the image edit application that is being executed in the other mobile terminal 101, and the cat image is pasted on an existing image. [0045]FIG. 1B is a block diagram illustrating the configuration of the mobile terminal according to an embodiment. [0046]Referring to FIG. 1B, the mobile terminal 100 may include a touch screen 110, a communication module 120, and a processor 130. As described below with reference to FIG. 4, the mobile terminal 100 may further include a pen insertion hole 410, a data transmission interface 420, and/or a power supply interface 430. [0047]The communication module 120 is configured to form a communication connection with a touch input device and transmit and receive data through the communication connection. The communication module 120 may include a wired communication module 121 and/or a wireless communication module 122. [0048]As described below with reference to FIG. 4, the wired communication module 121 may form a wired communication connection with the stylus pen 300 in a state in which the stylus pen 300 is inserted into the pen insertion hole 410 such that a metal contact point 321 exposed on a pen body 310 of the stylus pen 300 is connected to the data transmission interface 420 in the pen insertion hole. The wired communication module 121 may form the wired communication connection with the touch input device in a state in which the touch input device is connected to the mobile terminal through a data line. [0049]When a wireless connection condition is satisfied, the wireless communication module 122 may automatically form a wireless communication connection with the touch input device. Alternatively, the wireless communication connection with the touch input device may be formed when a specific type of a touch input is received by the touch screen. When a wireless communication function of the mobile terminal is not activated, the wireless communication module 122 may first activate the wireless communication function and then form the wireless communication connection with the touch input device. The specific type of the touch input may be basically set by a system, or the user may directly define the specific type of the touch input according to a use habit. For example, the specific type of the touch input may be set as touching the touch screen by the touch input device. That is, when the touch screen is touched by the touch input device, the wireless communication module 122 may automatically form the wireless communication connection with the touch input device. [0050]The wireless communication module 122 may activate the wireless communication function of the mobile terminal, search for a touch input device capable of performing a wireless communication function, and form the wireless communication connection with the found touch input device after a connection command input by the user is received. [0051]The touch screen 110 is configured to receive or detect the touch input by the touch input device. A touch input mode that detects only first to third touch inputs set by the system or defined by the user may be set through the operation of the mobile terminal or the touch input device. [0052]The processor 130 may perform data transmission between the touch input device and the mobile terminal and may control an execution of an application in the mobile terminal. [0053]When the first touch input by the touch input device is received by the touch screen, the processor 130 provides, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to another mobile terminal through the touch input device. Before the processor 130 transmits the predetermined data associated with the first application to the touch input device, the processor 130 may read the predetermined data from a predetermined position or a predetermined interface. [0054]The first touch input may be basically set by the system, or the user may directly define the first touch input according to the use habit. In order to effectively distinguish the first touch input from a general touch input, the first touch input may be set as a touch gesture input. For example, the first touch input may be set as a touch gesture input having a shape of “C”. Before the first touch input is input, a touch input mode for detecting the first touch input may be set. [0055]According to an embodiment, the predetermined data associated with the first application may include at least one of an image or a text selected on an execution screen of the first application by the user, a file that is being edited in the first application, and a multimedia file that is being reproduced in the first application. For example, the image or the text selected on the execution screen of the first application by the user may be an image portion corresponding to a region selected in an image edited in an image edit application by the user, an image portion corresponding to a region selected on a currently displayed screen of an application by the user, and a text portion selected in a document edit application or a web browsing application by the user. The file that is being edited in the first application may be an image file that is being edited in an image edit application, a text file that is being edited in a document edit application, and a video file that is being edited in a video edit application. The multimedia file that is being reproduced in the first application may be an audio file that is being reproduced in an audio reproduction application and a video file that is being reproduced in a video reproduction application. However, the predetermined data associated with the first application is not limited to the above-described embodiment, and may include various data. According to an embodiment, the predetermined data associated with the first application may include link information for downloading installation data for installing a second application that is the same as the first application in another mobile terminal, and may include setting data for setting the second application that is the same as the first application in the other mobile terminal. [0056]According to an embodiment, the predetermined data associated with the first application may be previously determined as consistent data according to the type of the first application. That is, predetermined data corresponding to different applications may also be different from each other. For example, when the first application that is currently being executed in the mobile terminal is a document edit application, the predetermined data associated with the first application may be determined as at least one of an image or a text selected on the execution screen of the first application by the user, a document file that is being edited in the first application, and setting data for setting a document edit environment in the same application as the first application. In addition, when the first application that is currently being executed is a web browsing application that is in a logged-in state, the predetermined data associated with the first application may be determined as data indicating information about an address of a current webpage of the first application and a logged-in account. However, the predetermined data associated with the first application is not limited to the above-described example, and may include various combinations of data. [0057]According to an embodiment, when the first touch input is received by the touch screen, the processor 130 may control display of a list of the predetermined data associated with the first application on the touch screen and provide data selected from the displayed list by the user to the touch input device. [0058]According to an embodiment, when the first touch input is received by the touch screen, the processor 130 may determine the type of the first touch input and provide the predetermined data corresponding to the first application and the determined type to the touch input device. The predetermined data corresponding to the first application may be previously determined as described above. In the predetermined data corresponding to the first application, when the first touch input is a first type, the processor 130 may transmit first data corresponding to the first type to the touch input device, and when the first touch input is a second type, the processor 130 may transmit second data corresponding to the second type to the touch input device. Therefore, the touch input device may store a plurality of data (the first data and the second data) transmitted from the mobile terminal. As an example, when the first application that is currently being executed in the mobile terminal is a document edit application, the user may select whether to transmit a document file that is being edited in the first application or whether to transmit setting data for setting a document edit environment of an application that is the same as the first application, according to the type of the touch input. That is, when the first touch input that is the first type is received by the touch screen, the processor 130 may transmit a document file that is being edited to the touch input device, and when the first touch input that is the second type is received by the touch screen, the processor 130 may transmit the setting data to the touch input device. [0059]According to an embodiment, as a second touch input is input to another mobile terminal by the touch input device, the predetermined data provided to the touch input device may be transmitted from the touch input device to the other mobile terminal, and the transmitted predetermined data may be provided to a second application executed by the other mobile terminal. The second application may be the same application as the first application among applications installed on the other mobile terminal as described below. Alternatively, the second application may be an application capable of using data received from the touch input device among the applications installed on the other mobile terminal, or may be an application that is different from the first application. [0060]According to an embodiment, when a third touch input by the touch input device is received by the touch screen, the processor 130 may receive the predetermined data provided to the touch input device from the touch input device, and provide the predetermined data received from the touch input device to a third application in the mobile terminal 100. That is, the predetermined data transmitted from the mobile terminal 100 to the touch input device may be transmitted again to not another mobile terminal but the same mobile terminal 100 and used in the third application. The third application may be the same application as the first application among applications installed on the mobile terminal 100. Alternatively, the third application may be an application capable of using data received from the touch input device among applications installed on the mobile terminal 100, or may be an application that is different from the first application. [0061]FIG. 2 is a block diagram illustrating the internal configuration of the touch input device according to an embodiment. [0062]As illustrated in FIG. 2, the touch input device 200 may include a memory 210, a communication module 220, and a battery 230. The memory 210 in the touch input device 200 is configured to store data. The touch input device 200 may further include a control button for controlling operations of the components in the outside thereof, and various functions such as a function of setting a touch input mode for detecting first to third touch inputs may be executed through the control button. [0063]The memory 210 included in the touch input device 200 may be a non-plug-type storage device or a plug-type storage device. The communication module 220 in the touch input device 200 is configured to transmit and receive data through a communication connection with the mobile terminal. The communication module 220 may include a wired communication module 221 and/or a wireless communication module 222. The wireless communication module 222 may form a wireless communication connection with another device through any wireless connection. For example, the wireless communication module 222 may form the wireless communication connection with another device through Wi-Fi connection, Bluetooth (BT) connection, near-field communication (NFC) connection, or touch screen communication (HOTKNOT) connection. The touch input device 200 may exchange data with the mobile terminal through the wired communication module 221 or the wireless communication module 222. [0064]According to an embodiment, the touch input device 200 may provide data received from a first mobile terminal to a second mobile terminal. Specifically, as a first touch input is input to the first mobile terminal by the touch input device 200, predetermined data associated with a first application that is being executed in the first mobile terminal may be received from the first mobile terminal and stored in the touch input device 200, and as a second touch input is input to the second mobile terminal by the touch input device 200, the received predetermined data may be provided to the second mobile terminal. [0065]According to an embodiment, the touch input device 200 may be a stylus pen 300 as described with reference to FIG. 3. However, the touch input device 200 is not limited thereto and may be various types of devices for generating the touch input. [0066]FIG. 3 is a schematic diagram illustrating the configuration of the stylus pen according to an embodiment. [0067]As illustrated in FIG. 3, the stylus pen 300 may include a pen body 310, a data transmission interface 320, a charge interface 330, and a control button 340. As described above, various functions of the stylus pen 300 may be executed through the control button 340. In order to smoothly perform a communication connection between the stylus pen 300 and the mobile terminal, a data line and a control line in the wired communication module 221 may be integrated in the data transmission interface 320 disposed on the pen body 310. [0068]According to an embodiment, as illustrated in FIG. 3, the data transmission interface 320 disposed on the pen body 310 may be a plurality of metal contact points 321 exposed on the pen body 310. However, the configuration of the data transmission interface 320 is not limited to the metal contact points 321 illustrated in FIG. 3, and may be another type of a metal connector. The metal contact points 321 may be formed by inserting a metal plate into the pen body 310, spraying a conductive material to the pen body 310, or attaching a conductive material to the pen body 310. [0069]The stylus pen 300 may include the battery 230 so as to supply power thereto. In order to charge the battery 230, the stylus pen 300 may further include a charge module used to charge the battery 230 with power received from the outside. The charge module may perform a charge operation through the charge interface 330 or the data transmission interface 320. The charge interface 330 may be disposed on the pen body 310. In order to facilitate a charge operation and prevent an arbitrary contact of the charge interface 330, a plurality of invaginated metal contact points 331 may be set on the pen body 310. [0070]FIG. 4 is a diagram illustrating a structure in which the stylus pen according to the embodiment is inserted into the mobile terminal. [0071]The mobile terminal 400 according to the embodiment may include a pen insertion hole 410 for insertion of the stylus pen 300. In addition, a data transmission interface 420 and a power supply interface 430 may be provided in the pen insertion hole 410. As illustrated in FIG. 4, when the stylus pen 300 is inserted into the pen insertion hole 410 of the mobile terminal 400, a position of the data transmission interface 320 of the stylus pen 300 may correspond to a position of the data transmission interface 420 in the pen insertion hole 410 of the mobile terminal 400, such that the data transmission interface 320 of the stylus pen 300 is connected to the data transmission interface 420 in the pen insertion hole 410. In the same manner, when the stylus pen 300 is inserted into the pen insertion hole 410 of the mobile terminal 400, a position of the charge interface 330 of the stylus pen 300 may correspond to a position of the power supply interface 430 in the pen insertion hole 410 of the mobile terminal 400, such that the charge interface 330 of the stylus pen 300 is connected to the power supply interface 430 in the pen insertion hole 410. The power supply interface 430 in the pen insertion hole 410 of the mobile terminal 400 may be set as a plurality of elastic contact points capable of supplying power. [0072]FIG. 5 is a flowchart of a method of controlling a mobile terminal by using a touch input device, according to an embodiment. [0073]As illustrated in FIG. 5, the method of controlling the mobile terminal by using the touch input device may include: receiving a first touch input by the touch input device on a touch screen of a first mobile terminal (510); transmitting predetermined data associated with a first application that is currently being executed in the first mobile terminal from the first mobile terminal to the touch input device (520); receiving a second touch input by the touch input device on a touch screen of a second mobile terminal (530); and transmitti(String), 相关申请的交叉引用 [0001] 本申请为2016年8月12日提交的国际专利申请PCT/KR2016/008877的第371号,要求2015年8月13日提交的中国专利申请201510497976.9的优先权,其公开内容以引用方式并入本文。 他们的全部。 技术领域 [0002] 本发明涉及一种移动终端和通过使用触摸输入设备控制移动终端的方法,更具体地,涉及通过触摸输入设备向另一个移动终端提供数据的移动终端和控制移动终端的方法 终端。 背景 [0003] 近来,随着电子技术的不断发展,触控技术的应用逐渐普及,通过触控输入控制终端的技术和触控输入设备备受关注。 目前,触控笔是代表性的触控输入装置之一。 [0004] 触控笔可以通过将其笔尖触摸到触摸屏来产生触摸输入,并且可以通过在触摸屏上的触摸来对屏幕执行控制操作。 尤其是触控笔,更适合书写、截屏等操作。 例如,可以通过触控笔在移动终端的触摸屏上指定需要截屏的区域进行截屏,并将截屏存储在移动终端中。 此外,可以通过使用触控笔在备忘录应用中执行书写来随时记录用户的想法。 [0005] 现有技术的移动终端的控制技术仅限于通过触摸输入设备通过触摸输入来控制一个终端。 然而,当存在多个终端时,需要一种能够通过触摸输入在不同终端之间连续执行应用的控制技术。 概括 [0006] 本公开提供一种用于通过触摸输入设备向另一移动终端提供数据并连续执行应用的移动终端,以及控制移动终端的方法。 [0007] 根据实施例,可以通过触摸输入设备在不同终端之间传输数据并连续执行应用程序。 附图的详细说明 [0008] 如图。 图1A是示意性地示出根据实施例的通过触控笔向另一终端提供数据的图。 [0009] 如图。 图1B是图示根据实施例的移动终端的配置的框图。 [0010] 如图。 图2是表示实施方式的触摸输入装置的内部结构的框图。 [0011] 如图。 图3是图示根据实施例的触控笔的配置的图。 [0012] 如图。 图4是示出根据实施例的触控笔插入移动终端的结构的图。 [0013] 如图。 图5是根据实施例的通过使用触摸输入设备控制移动终端的方法的流程图。 [0014] 图 图6至图8示出了根据实施例的通过使用触控笔传输和调用图像。 [0015] 图 图9至图11示出了根据实施例的通过使用触控笔在备忘录应用程序中正在编辑的文档文件的传输和调用。 [0016] 图 图12至图14示出了根据实施例的通过使用触控笔连续执行游戏应用程序。 [0017] 图 图15至图17示出了根据实施例的通过使用触控笔连续执行视频流应用。 [0018] 图 图18至图20示出了根据实施例的通过使用触控笔连续执行网页浏览应用程序。 [0019] 图 图21至图23示出了根据实施例的通过使用触控笔连续执行具有帐户登录功能的游戏应用。 详细说明 [0020]在一个实施例中,一种用于通过触摸输入设备向另一移动终端提供数据的移动终端包括: 触摸屏,用于接收触摸输入设备的触摸输入; 通信模块,被配置为通过与触摸输入设备的通信连接来发送和接收数据; 处理器,被配置为当触摸屏接收到触摸输入设备的第一触摸输入时,向触摸输入设备提供与移动终端中当前正在执行的第一应用相关联的预定数据,使得 预定数据通过触摸输入设备提供给其他移动终端。 [0021] 在一个实施例中,当触摸屏接收到第一触摸输入时,处理器还被配置为确定第一触摸输入的类型并将与第一应用和确定的类型对应的预定数据提供给触摸输入设备。 [0022] 在一个实施例中,当触摸屏接收到第一触摸输入时,处理器还被配置为控制与第一应用相关联的预定数据的列表在触摸屏上的显示,并提供由触摸屏从显示的列表中选择的数据。 用户到触摸输入设备。 [0023] 在一个实施例中,与第一应用相关联的预定数据包括用户在第一应用的执行屏幕上选择的图像或文本、在第一应用中正在编辑的文件和多媒体中的至少一个。 在第一个应用程序中复制的文件。 [0024] 在一个实施例中,当触摸输入设备向另一移动终端输入第二触摸输入时,将提供给触摸输入设备的预定数据从触摸输入设备发送到另一移动终端,发送的预定数据为 提供给由另一个移动终端执行的第二应用程序。 [0025] 在一个实施例中,预定数据包括用于下载用于安装与第一应用相同的第二应用的安装数据的链接信息。 [0026] 在一个实施例中,预定数据包括用于设置与第一应用相同的第二应用的设置数据。 [0027] 在一个实施例中,预定数据包括指示当触摸屏接收到第一触摸输入时第一应用程序的状态的数据,并且通过使用预定数据使第二应用程序的状态与第一应用程序的状态基本相同。 提供给第二个应用程序的数据。 [0028] 在一个实施例中,第一应用程序是网页浏览应用程序,预定数据包括第一应用程序的当前网页的地址,预定数据提供给作为网页浏览应用程序的第二应用程序,以及网页 在第二个应用程序中打开对应于网页地址的网页。 [0029] 在一个实施例中,在第一应用程序具有多媒体再现功能并且当触摸屏接收到第一触摸输入时第一应用程序中的多媒体暂停的情况下,预定数据包括指示多媒体再现状态的数据和 暂停多媒体的再现位置,并将预定数据提供给具有多媒体再现功能的第二应用程序,在第二应用程序的再现位置处以暂停状态开始多媒体的再现。 [0030] 在一个实施例中,当第一应用程序为游戏应用程序,并且当触摸屏接收到第一触摸输入时,第一应用程序中的游戏暂停时,预定数据包括指示游戏进行状态的数据和 游戏暂停位置,将预定数据提供给与第一应用相同的第二应用,在第二应用中的该位置以暂停状态启动游戏。 [0031]在一个实施例中,当第一应用具有账号登录功能,并且当触摸屏接收到第一触摸输入时,在第一应用中登录了账号时,所述预定数据包括表示登录信息的数据。 账号,将预定数据提供给与第一应用相同的第二应用,并在第二应用中登录该账号。 [0032] 在一个实施例中,当触摸屏接收到触摸输入设备的第三触摸输入时,处理器还用于接收从触摸输入设备提供给触摸输入设备的预定数据,并提供从触摸输入设备接收的预定数据。 将触摸输入设备连接到移动终端中的第三应用程序。 [0033] 在一个实施例中,一种通过触摸输入设备控制移动终端的方法包括: 接收触摸输入设备在第一移动终端的触摸屏上的第一触摸输入; 将与当前在第一移动终端中执行的第一应用相关联的预定数据从第一移动终端发送到触摸输入设备; 在第二移动终端的触摸屏上接收触摸输入设备的第二触摸输入; 将存储在触摸输入装置中的预定数据从触摸输入装置发送到第二移动终端。 [0034] 在一个实施例中,从触摸输入设备传输到第二移动终端的预定数据被提供给由第二移动终端执行的第二应用程序。 [0035] 在一个实施例中,预定数据包括用于下载用于安装与第一应用相同的第二应用的安装数据的链接信息。 [0036] 在一个实施例中,预定数据包括用于设置与第一应用相同的第二应用的设置数据。 [0037] 在一个实施例中,预定数据包括指示当触摸屏接收到第一触摸输入时第一应用程序的状态的数据,并且通过使用预定数据使第二应用程序的状态与第一应用程序的状态基本相同。 提供给第二个应用程序的数据。 [0038] 在一个实施例中,当第一移动终端的触摸屏接收到触摸输入设备的第三触摸输入时,第一移动终端向触摸输入设备发送的预定数据被发送给第一移动终端并提供给 第一移动终端中的第三应用程序。 发明方式 [0039] 本发明的优点和特征以及实现它们的方法将从以下结合附图详细描述的实施例中变得更加明显。 然而,应当理解,本发明不限于以下实施例,并且可以在不脱离本发明的范围的情况下进行各种修改。 提供在此阐述的实施例是为了使本公开将彻底和完整,并将本发明的概念充分传达给本领域技术人员。 本发明应由所附权利要求限定。 相同的附图标记自始至终被分配给相同的元件。 [0040]应当理解,当一个区域被称为“连接到”或“耦合到”另一个区域时,它可以直接连接到或耦合到另一个区域,或者可以存在中间区域。 应当理解,诸如“包括”、“包括”和“具有”等术语,当在本文中使用时,指定了所述元素的存在,但不排除一种或多种其他元素的存在或添加。 此外,此处使用的术语“单元”是指诸如FPGA或ASIC之类的软件或硬件组件,并且“单元”执行某些功能。 然而,“单元”不限于软件或硬件。 “单元”可以配置在可寻址存储介质中或配置为再现一个或多个处理器。 因此,例如,“单元”包括诸如软件组件、面向对象软件组件、类组件和任务组件、进程、功能、属性、过程、子例程、程序代码段、驱动程序、固件、微代码等组件。 电路、数据、数据库、数据结构、表格、数组和变量。 组件和“单元”中提供的功能可以与较少数量的组件和“单元”组合,也可以与附加的组件和“单元”分离。 [0041] 下面将结合附图对本发明实施例进行详细说明,以便本领域普通技术人员能够容易地实施本发明实施例。 然而,实施例可以以各种不同的形式实现并且不限于此。 为了清楚地描述附图中的实施例,省略了与描述无关的部分。 [0042] 此处使用的术语是本领域当前广泛使用的那些考虑到发明构思的功能的通用术语,但是这些术语可以根据本领域普通技术人员的意图、先例或本领域的新​​技术而变化。 艺术。 此外,申请人可以选择特定的术语,并且在这种情况下,其详细含义将在发明构思的详细描述中描述。 因此,此处使用的术语不应被理解为简单的名称,而应基于术语的含义和本发明概念的整体描述来理解。 [0043] 如图。 图1A是示意性地示出根据实施例的通过触控笔向另一终端提供数据的图。 [0044] 参考图。 参考图1A,当图像编辑应用程序正在移动终端中执行时 100 在移动终端的触摸屏上输入形状为“C”的触摸手势 100 用手写笔 300 在通过触控笔的操作选择猫图像的状态下 300 , 移动端 100 将包括所选猫图像在内的数据传输到触控笔 300 通过无线通信连接。 包含猫图像的数据存储在触控笔的内存中 300 . 当图像编辑应用程序正在另一个移动终端中执行时 101 在移动终端的触摸屏上输入形状为“P”的触摸手势 101 用手写笔 300 ,其他移动终端 101 从触控笔接收包括猫图像在内的数据 300 . 将接收到的数据提供给正在其他移动终端中执行的图像编辑应用程序 101 ,并且猫图像被粘贴到现有图像上。 [0045] 如图。 图1B是图示根据实施例的移动终端的配置的框图。 [0046] 参考图。 1B、移动终端 100 可能包括触摸屏 110 , 一个通讯模块 120 , 和一个处理器 130 . 如下文参考图1所描述的。 4、移动端 100 还可以包括笔插入孔 410 , 数据传输接口 420 , 和/或电源接口 430 . [0047] 通讯模块 120 被配置为与触摸输入设备形成通信连接,并通过该通信连接发送和接收数据。 通讯模块 120 可以包括有线通信模块 121和/或无线通信模块 122 . [0048] 如下文参考图1所描述的。 4、有线通讯模块 121 可与触控笔形成有线通讯连接 300 在触控笔的状态下 300 插入笔插入孔 410 这样一个金属接触点 321 暴露在笔身上 310 手写笔的 300 连接到数据传输接口 420 在笔插入孔中。 有线通讯模块 121 可以在触摸输入设备通过数据线与移动终端连接的状态下与触摸输入设备形成有线通信连接。 [0049] 当满足无线连接条件时,无线通信模块 122 可自动与触控输入装置形成无线通讯连接。 或者,可以在触摸屏接收到特定类型的触摸输入时形成与触摸输入设备的无线通信连接。 当移动终端的无线通信功能未激活时,无线通信模块 122 可先启动无线通讯功能,然后与触控输入装置形成无线通讯连接。 触摸输入的具体类型基本上可以由系统设置,或者用户可以根据使用习惯直接定义触摸输入的具体类型。 例如,可以将触摸输入的具体类型设置为触摸输入设备触摸触摸屏。 即,当触摸屏被触摸输入设备触摸时,无线通信模块 122 可自动与触控输入装置形成无线通讯连接。 [0050] 无线通讯模块 122 可以激活移动终端的无线通信功能,搜索能够执行无线通信功能的触摸输入设备,并在接收到用户输入的连接命令后与找到的触摸输入设备形成无线通信连接。 [0051] 触摸屏 110 被配置为接收或检测触摸输入设备的触摸输入。 可以通过移动终端或触摸输入设备的操作来设置仅检测系统设置或用户定义的第一至第三触摸输入的触摸输入模式。 [0052] 处理器 130 可以执行触摸输入设备和移动终端之间的数据传输,并且可以控制移动终端中应用程序的执行。 [0053] 当触摸屏接收到触摸输入设备的第一次触摸输入时,处理器 130 向触摸输入设备提供与移动终端当前正在执行的第一应用相关联的预定数据,从而通过触摸输入设备将预定数据提供给另一个移动终端。 处理器前 130 将与第一应用相关联的预定数据传输到触摸输入设备,处理器 130 可以从预定位置或预定接口读取预定数据。 [0054] 第一触摸输入基本可以由系统设置,或者用户可以根据使用习惯直接定义第一触摸输入。 为了有效区分第一触摸输入和一般触摸输入,可以将第一触摸输入设置为触摸手势输入。 例如,第一触摸输入可以被设置为具有“C”形状的触摸手势输入。 在输入第一触摸输入之前,可以设置用于检测第一触摸输入的触摸输入模式。 [0055]根据实施例,与第一应用相关联的预定数据可以包括用户在第一应用的执行屏幕上选择的图像或文本、在第一应用中正在编辑的文件、以及正在编辑的文件中的至少一个。 在第一个应用程序中再现的多媒体文件。 例如,用户在第一应用程序的执行画面上选择的图像或文本可以是与用户在图像编辑应用程序中编辑的图像中选择的区域相对应的图像部分,与区域相对应的图像部分 用户在当前显示的应用程序屏幕上选择的文本部分,以及用户在文档编辑应用程序或网络浏览应用程序中选择的文本部分。 第一应用程序中正在编辑的文件可以是图像编辑应用程序中正在编辑的图像文件、文档编辑应用程序中正在编辑的文本文件以及视频编辑中正在编辑的视频文件 应用。 正在第一应用中再现的多媒体文件可以是正在音频再现应用中再现的音频文件和正在视频再现应用中再现的视频文件。 然而,与第一应用相关联的预定数据不限于上述实施例,并且可以包括各种数据。 根据一个实施例,与第一应用程序相关联的预定数据可以包括用于下载安装数据的链接信息,该安装数据用于在另一个移动终端中安装与第一应用程序相同的第二应用程序,并且可以包括用于设置第二应用程序的设置数据: 与其他移动终端中的第一个应用程序相同。 [0056] 根据一个实施例,与第一应用相关联的预定数据可以根据第一应用的类型预先确定为一致数据。 也就是说,对应于不同应用的预定数据也可以彼此不同。 例如,当移动终端当前正在执行的第一应用程序是文档编辑应用程序时,与第一应用程序关联的预定数据可以被确定为在移动终端的执行屏幕上选择的图像或文本中的至少一个。 用户的第一应用程序,在第一应用程序中正在编辑的文档文件,以及用于在与第一应用程序相同的应用程序中设置文档编辑环境的设置数据。 另外,当当前正在执行的第一应用程序是处于登录状态的网页浏览应用程序时,与第一应用程序关联的预定数据可以被确定为指示与当前网页的地址有关的信息的数据。 第一个应用程序和登录帐户。 然而,与第一应用相关联的预定数据不限于上述示例,并且可以包括各种数据组合。 [0057] 根据一个实施例,当触摸屏接收到第一触摸输入时,处理器 130 可以控制与第一应用相关联的预定数据的列表在触摸屏上的显示,并且将用户从显示的列表中选择的数据提供给触摸输入设备。 [0058] 根据一个实施例,当触摸屏接收到第一触摸输入时,处理器 130 可以确定第一触摸输入的类型并将与第一应用和确定的类型对应的预定数据提供给触摸输入设备。 可以如上所述预先确定对应于第一应用的预定数据。 在与第一应用程序对应的预定数据中,当第一触摸输入为第一类型时,处理器 130 可以将与第一类型对应的第一数据发送给触摸输入设备,当第一触摸输入为第二类型时,处理器 130可以将对应于第二类型的第二数据发送到触摸输入设备。 因此,触摸输入装置可以存储从移动终端发送的多个数据(第一数据和第二数据)。 例如,当移动终端中当前正在执行的第一应用程序是文档编辑应用程序时,用户可以选择是否发送正在第一应用程序中编辑的文档文件,或者是否发送设置数据用于设置 根据触摸输入的类型,与第一个应用程序相同的应用程序的文档编辑环境。 即,当触摸屏接收到第一类型的第一触摸输入时,处理器 130 可以将正在编辑的文档文件发送到触摸输入设备,当触摸屏接收到第二类型的第一触摸输入时,处理器 130 可以将设置数据发送到触摸输入设备。 [0059] 根据一个实施例,当触摸输入设备向另一个移动终端输入第二触摸输入时,提供给触摸输入设备的预定数据可以从触摸输入设备发送到另一个移动终端,并且发送的预定数据 可以提供给由另一个移动终端执行的第二应用程序。 第二应用程序可以是安装在其他移动终端上的应用程序中与第一应用程序相同的应用程序,如下所述。 或者,第二应用程序可以是安装在其他移动终端上的应用程序中能够使用从触摸输入装置接收到的数据的应用程序,或者可以是与第一应用程序不同的应用程序。 [0060] 根据一个实施例,当触摸屏接收到触摸输入设备的第三触摸输入时,处理器 130 可以从触摸输入设备接收提供给触摸输入设备的预定数据,并将从触摸输入设备接收的预定数据提供给移动终端中的第三应用程序 100 . 即移动终端发送的预定数据 100 到触摸输入设备可能会再次传输到不是另一个移动终端,而是同一个移动终端 100 并在第三个应用程序中使用。 第三应用程序可以是安装在移动终端上的应用程序中与第一应用程序相同的应用程序 100 . 或者,第三应用程序可以是安装在移动终端上的应用程序中能够使用从触摸输入装置接收到的数据的应用程序。 100 ,或者可能是与第一个应用程序不同的应用程序。 [0061] 如图。 图2是表示实施方式的触摸输入装置的内部结构的框图。 [0062] 如图所示。 2、触摸输入设备 200 可能包括记忆 210 , 一个通讯模块 220 , 和一个电池 230 . 记忆 210 在触摸输入设备中 200 被配置为存储数据。 触摸输入设备 200 可以进一步包括用于控制其外部的组件的操作的控制按钮,并且可以通过控制按钮执行各种功能,例如设置用于检测第一到第三触摸输入的触摸输入模式的功能。 [0063] 记忆 210 包含在触摸输入设备中 200 可以是非插接式存储设备或插接式存储设备。 通讯模块 220 在触摸输入设备中 200 被配置为通过与移动终端的通信连接发送和接收数据。 通讯模块 220 可以包括有线通信模块 221 和/或无线通信模块 222 . 无线通讯模块 222 可以通过任何无线连接与另一设备形成无线通信连接。 例如,无线通信模块 222可以通过Wi-Fi连接、蓝牙(BT)连接、近场通信(NFC)连接或触摸屏通信(HOTKNOT)连接与另一设备形成无线通信连接。 触摸输入设备 200 可通过有线通信模块与移动终端交换数据 221 或无线通讯模块 222 . [0064] 根据一个实施例,触摸输入设备 200 可以将从第一移动终端接收到的数据提供给第二移动终端。 具体地,当触摸输入设备向第一移动终端输入第一触摸输入时 200 可以从第一移动终端接收与在第一移动终端中执行的第一应用相关联的预定数据,并将其存储在触摸输入设备中 200 ,并且作为第二次触摸输入由触摸输入设备输入到第二移动终端 200 ,可以将接收到的预定数据提供给第二移动终端。 [0065] 根据一个实施例,触摸输入设备 200 可能是手写笔 300 如参考图1所描述的。 3.然而,触摸输入设备 200 不限于此,并且可以是用于产生触摸输入的各种类型的装置。 [0066] 如图。 图3是图示根据实施例的触控笔的配置的示意图。 [0067] 如图所示。 3、触控笔 300 可能包括笔身 310 , 数据传输接口 320 , 一个充电接口 330 , 和一个控制按钮 340 . 如上所述,触控笔的各种功能 300 可以通过控制按钮执行 340 . 为了顺利进行触控笔之间的通讯连接 300 以及移动终端、有线通信模块中的数据线和控制线 221 可集成在数据传输接口中 320 设置在笔身上 310 . [0068] 根据一个实施例,如图所示。 3、数据传输接口 320 设置在笔身上 310 可以是多个金属接触点 321 暴露在笔身上 310 . 但是,数据传输接口的配置 320 不限于金属接触点 321 如图所示。 3、可能是另一种金属连接器。 金属接触点 321 可以通过将金属板插入笔身来形成 310 ,在笔身喷涂导电材料 310 ,或将导电材料连接到笔身 310 . [0069] 触控笔 300 可能包括电池 230 从而为其供电。 为了给电池充电 230 , 触控笔 300 还可以包括用于给电池充电的充电模块 230 用从外部获得的力量。 充电模块可以通过充电接口进行充电操作 330 或数据传输接口 320 . 收费接口 330 可以设置在笔身上 310 . 为了方便充电操作,防止随意接触充电接口 330 ,多个内陷金属接触点 331 可设置在笔身上 310 . [0070] 如图。 图4是示出根据实施例的触控笔插入移动终端的结构的图。 [0071] 移动终端 400 根据实施例可以包括笔插入孔 410 用于插入触控笔 300 . 另外,一个数据传输接口 420 和一个电源接口 430 可在笔插入孔中设置 410 . 如图所示。 4、当手写笔 300 插入笔插入孔 410 移动终端的 400 ,数据传输接口的位置 320 手写笔的 300 可以对应数据传输接口的位置 420 在笔插入孔中 410移动终端的 400 , 这样数据传输接口 320 手写笔的 300 连接到数据传输接口 420 在笔插入孔中 410 . 以同样的方式,当触控笔 300 插入笔插入孔 410 移动终端的 400 ,充电接口的位置 330 手写笔的 300 可以对应电源接口的位置 430 在笔插入孔中 410 移动终端的 400 , 这样充电接口 330 手写笔的 300 连接到电源接口 430 在笔插入孔中 410 . 电源接口 430 在笔插入孔中 410 移动终端的 400 可以设置为多个能够供电的弹性触点。 [0072] 如图。 图5是根据实施例的通过使用触摸输入设备控制移动终端的方法的流程图。 [0073] 如图所示。 参照图5,通过触摸输入设备控制移动终端的方法可以包括:接收触摸输入设备在第一移动终端的触摸屏上的第一触摸输入( 510 ); 将与当前在第一移动终端中执行的第一应用相关联的预定数据从第一移动终端发送到触摸输入设备( 520 ); 在第二移动终端的触摸屏上接收触摸输入设备的第二触摸输入( 530 ); 将存储在触摸输入装置中的预定数据从触摸输入装置发送到第二移动终端( 540 )。 [0074] 运行中 510 ,第一移动终端接收触摸输入设备在第一移动终端的触摸屏上的第一触摸输入。 运行中 520 ,第一移动终端响应于接收到第一触摸输入,通过与触摸输入设备的通信连接将与第一移动终端中当前正在执行的第一应用程序相关联的预定数据发送到触摸输入设备。 [0075] 根据实施例,当触摸屏接收到第一触摸输入时,第一移动终端可以确定第一触摸输入的类型并将与第一应用和确定的类型对应的预定数据提供给触摸输入设备。 如上所述,可以根据第一应用的类型预先确定对应于第一应用的预定数据。 例如,在第一应用对应的预定数据中,当第一触摸输入为第一类型时,第一移动终端可以向触摸输入设备发送第一类型对应的第一数据,当第一触摸输入为 第二类,第一移动终端可以将第二类对应的第二数据发送给触摸输入设备。 因此,触摸输入装置可以存储从第一移动终端发送的多个数据(第一数据和第二数据)。 [0076] 运营中 510 和 520 , 与移动端的操作相同 100 和触摸输入设备 200 参考图1和2描述。 可以由第一移动终端和触摸输入设备执行图1B至图4。 [0077] 运行中 530 ,第二移动终端接收触摸输入设备在第二移动终端的触摸屏上的第二触摸输入。 [0078] 第二触摸输入可以基本由系统设置,或者用户可以根据使用习惯直接定义第二触摸输入。 为了有效地区分第二触摸输入与一般触摸输入,可以将第二触摸输入设置为触摸手势输入。 例如,可以将第二触摸输入设置为具有“P”形状的触摸手势输入。 在向触摸屏输入第二触摸输入之前,可以在移动终端中设置用于检测第二触摸输入的触摸输入模式。 [0079] 运行中 540,将存储在触摸输入设备中的预定数据从触摸输入设备发送到第二移动终端。 也就是说,第二移动终端响应于第二触摸输入的接收,通过与触摸输入装置的通信连接从触摸输入装置接收存储在触摸输入装置中的预定数据。 [0080] 根据实施例,当触摸屏接收到第二触摸输入时,第二移动终端可以确定第二触摸输入的类型,并从触摸输入设备接收与确定的类型对应的预定数据。 例如,在从第一移动终端发送的多个数据(第一数据和第二数据)被存储在触摸输入设备中的情况下,第二移动终端可以从存储在触摸输入设备中的数据中接收第一数据。 当第二触摸输入为第三类型时,触摸输入设备,并且当第二触摸输入为第四类型时,可以从存储在触摸输入设备中的数据中接收第二数据。 [0081] 根据一个实施例,当触摸屏接收到第二触摸输入时,第二移动终端可以接收最新存储在触摸输入设备中并且尚未发送到移动终端的预定数据。 在这种情况下,通过多次输入第二触摸输入,第二移动终端可以在不同时刻按照存储时间的倒序接收存储在触摸输入设备中的预定数据。 可以从触摸输入装置的存储器中删除存储在触摸输入装置的存储器中的数据中已经发送到移动终端的数据。 [0082] 运行中 540 ,可以将已经从触摸输入设备发送到第二移动终端的预定数据提供给由第二移动终端执行的第二应用程序。 第二应用程序可以是安装在第二移动终端上的应用程序中与第一应用程序相同的应用程序。 或者,第二应用程序可以是安装在第二移动终端上的应用程序中能够使用从触摸输入装置接收到的数据的应用程序,或者可以是与第一应用程序不同的应用程序。 或者,第二应用程序可以是不同于第一应用程序但能够通过使用从触摸输入装置接收到的数据来执行预定处理的应用程序。 例如,当从触摸输入设备接收到的数据是包括用户选择的图像的数据时,第二应用程序可以是能够像图像编辑应用程序一样粘贴相应图像的应用程序,并且当从触摸接收到的数据时 输入设备是文档文件,第二应用程序可以是能够打开和编辑对应的文档文件的文档编辑应用程序或能够打开和查看对应的文档文件的文档查看器应用程序。 [0083] 根据实施例,通过触摸输入装置从第一移动终端发送到第二移动终端的预定数据可以包括指示当触摸屏接收到第一触摸输入时第一应用的状态的数据,以及 通过使用提供给第二应用的预定数据,可以使第二应用与第一应用的状态基本相同。 [0084] 根据实施例,通过触摸输入装置从第一移动终端发送到第二移动终端的预定数据可以包括用于下载用于安装与第一应用相同的第二应用的安装数据的链接信息,以及第二应用 可以通过安装数据安装在第二移动终端上。 [0085]根据一个实施例,通过触摸输入设备从第一移动终端发送到第二移动终端的预定数据可以包括用于设置与第一应用相同的第二应用的设置数据,并且第二应用可以设置在 通过将设置数据提供给第二应用程序,以与第一应用程序相同的方式。 [0086] 根据一个实施例,在预定数据从第一移动终端发送到触摸输入设备之后,当触摸输入设备的第三触摸输入被第一移动终端的触摸屏接收到时,从第一移动终端发送的预定数据 触摸输入设备的移动终端可以被传输到第一移动终端并提供给第一移动终端中的第三应用程序。 [0087] 根据一个实施例,第一应用可以是网页浏览应用,第一移动终端通过触摸输入设备向第二移动终端提供的预定数据可以包括第一应用的当前网页的地址。 可以将预定数据提供给作为网页浏览应用的第二应用,并且可以在第二应用中打开与当前网页的地址对应的网页。 [0088] 根据一个实施例,在第一应用具有多媒体再现功能并且当触摸屏接收到第一触摸输入时第一应用中的多媒体暂停的情况下,从第一移动终端向第二移动终端提供预定数据 通过触摸输入装置可以包括指示多媒体的再现状态和多媒体被暂停的再现位置的数据。 可以将预定数据提供给具有多媒体再现功能的第二应用程序,并且可以在处于再现位置的暂停状态的第二应用程序中开始多媒体的再现。 [0089] 根据一个实施例,在第一应用是游戏应用并且当触摸屏接收到第一触摸输入时在第一应用中暂停游戏的情况下,从第一移动终端向第二移动终端提供预定数据 通过触摸输入设备可以包括指示游戏的进展状态和游戏暂停的位置的数据。 可以将预定数据提供给与第一应用程序相同的第二应用程序,并且可以在处于上述位置的暂停状态的第二应用程序中开始游戏。 [0090] 根据一个实施例,当第一应用程序具有账号登录功能,并且当触摸屏接收到第一触摸输入时,在第一应用程序中登录了账号时,第一移动终端通过以下方式向第二移动终端提供预定数据。 触摸输入设备可以包括指示关于已登录帐户的信息的数据,并且可以通过向与第一应用相同的第二应用提供预定数据来登录第二应用中的帐户。 [0091] 根据实施例,第一应用可以具有多媒体流功能,并且从第一移动终端通过触摸输入设备提供给第二移动终端的预定数据可以包括在第一应用中流的多媒体的网络地址 . 可以将预定数据提供给与第一应用相同的第二应用,并且可以在第二应用中流式传输与网络地址对应的多媒体。 [0092] 运营中 530 和 540 , 操作与移动端相同 100 和触摸输入设备 200 参考图1和2描述。 可以由第二移动终端和触摸输入设备来执行图1B至图4的操作。 [0093]根据一个实施例,通过使用触摸输入设备控制移动终端的方法还可以包括:当触摸屏接收到第二触摸输入时,在第二移动终端中没有执行第二应用程序的情况下,执行 在将从触摸输入设备接收到的数据提供给第二应用程序之前,第二应用程序。 [0094] 将参考图1至图3描述与通过触摸输入设备在第一移动终端和第二移动终端之间传输数据并连续执行应用的方法有关的具体实施例。 6 至 23 日。 [0095] 将参照图1至图3描述通过触摸输入装置从第一移动终端向第二移动终端的第二应用提供与第一应用相关联的预定数据的情况。 参照图6至图23,但本发明不限于此。 例如,在将与第一应用相关联的预定数据提供给触摸输入设备之后,可以将与第一应用相关联的预定数据从触摸输入设备提供给安装在第一移动终端上的第三应用。 [0096] 图 图6至图8说明了使用触控笔传输和调用图像 300 ,根据一个实施例。 [0097] 参考图。 参照图6,在第一移动终端中执行图像编辑应用程序 100 ,通过手写笔的操作选择猫图像 300 ,并通过触控笔在触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将猫图像传输到触控笔 300 通过无线通信连接。 [0098] 参考图。 参照图7,在第二移动终端中执行图像编辑应用,图像编辑应用中存在现有的椅子图像。 [0099] 参考图。 如图8所示,触控笔在第二移动终端的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 300 ,第二移动终端接收到手写笔中存储的猫图片 300 来自触控笔 300 通过无线通信连接。 将接收到的数据提供给第二移动终端中正在执行的图像编辑应用程序,并将猫图像粘贴到图像编辑应用程序中的现有桌面图像上。 [0100] 参考图。 参照图6至图8,在一个实施例中,用户选择的图像可以存储在触控笔中 300 实时,图像可以在另一个移动终端或同一个移动终端中继续使用。 [0101] 图 图9至图11示出了使用触控笔在备忘录应用程序中正在编辑的文档文件的传输和调用 300 ,根据一个实施例。 [0102] 参考图。 9、在第一移动终端的备忘录应用中输入文字“TODAY'S WEATHER”后 100 ,触控笔在弹出式菜单中选择用于检测第一触摸输入的触摸输入模式 300 . [0103] 参考图。 参照图10,通过触控笔在第一移动终端的触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 ,并显示与备忘录应用程序相关联的预定数据列表,以便选择传输到触控笔的数据 300 . 该列表包括两个项目“SAVE TRACK”和“SAVE RESULT”。 在这两项中,“SAVE TRACK”表示发送用于设置备忘录应用的文档编辑环境的设置数据,“SAVE RESULT”表示发送正在备忘录应用中编辑的文档文件。 在与备忘录应用关联的预定数据列表中,用户选择“保存结果”,第一移动终端 100 将备忘录应用程序中正在编辑的文档文件传输到触控笔 300 通过无线通信连接。 [0104]参考图。 如图11所示,触控笔在第二移动终端主界面的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 300 ,以及第二个移动终端 101 接收存储在触控笔中的文档文件 300 通过无线通信连接。 由于备忘录应用不在第二移动终端中执行 101 当在第二移动终端输入第二触摸输入时 101 ,第二个移动终端 101 首先执行备忘录应用程序,然后加载从手写笔接收到的文档文件 300 在备忘录应用程序中。 [0105] 参考图。 参照图9至图11,在一个实施例中,可以将正在编辑的文档文件传送到触控笔 300 ,并且可以在另一个移动终端或同一移动终端中执行连续文档编辑。 [0106] 图 图12至图14示出了通过使用触控笔连续执行游戏应用程序 300 ,根据一个实施例。 [0107] 参考图。 12、在第一移动终端正在执行的游戏应用中暂停游戏 100 ,并通过触控笔在触摸屏上输入形状为“N”的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将游戏的进度状态和游戏的暂停位置传送到触控笔 300 通过无线通信连接。 [0108] 参考图。 参照图13,在第二移动终端的主界面中的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 接收指示游戏进度状态和游戏暂停位置的数据,存储在触控笔中 300 , 来自触控笔 300 通过无线通信连接。 [0109] 参考图。 14、游戏应用在第二移动终端中执行 101 ,从手写笔接收的数据 300 提供给游戏应用程序,在第一移动终端中游戏暂停的位置以暂停状态启动游戏。 用户可以在游戏应用的界面中选择“继续玩”以继续玩游戏。 [0110] 参考图。 参照图12至图14,在一个实施例中,用户可以通过触控笔在另一个终端或同一终端继续玩暂停的游戏 300 . [0111] 图 图15到17示出了通过使用触控笔连续执行视频流应用 300 ,根据一个实施例。 [0112] 参考图。 15、在第一移动终端的视频流应用中暂停视频流 100 ,并通过触控笔在触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 . 第一个移动终端 100 将指示视频的再现状态和视频的暂停再现位置的数据发送到触控笔 300 通过无线通信连接以及正在流式传输的视频的网络地址。 [0113] 参考图。 参照图16,在第二移动终端的主界面中的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 从触控笔接收 300 、指示正在流式传输的多媒体的网络地址、视频的再现状态和视频的暂停位置的数据,这些数据存储在触控笔中 300 ,通过无线通信连接。 [0114] 参考图。 参照图17,由于在第二移动终端中输入第二触摸输入时不执行视频流应用 101 ,首先在第二移动终端中执行视频流应用。 第二个移动终端 101 提供从触控笔接收的数据 300到视频流应用程序。 对应于网络地址的多媒体基于提供的数据在视频流应用中被流化,并且多媒体的再现在再现位置处以暂停状态开始。 为了继续继续播放视频,用户可以在视频流应用的界面中点击播放重启按钮。 [0115] 参考图。 参照图15至图17,在一个实施例中,用户可以通过使用触控笔在另一个移动终端或同一移动终端中继续流式传输视频 300 . [0116] 图 图18至图20示出了通过使用触控笔连续执行网页浏览应用程序 300 ,根据一个实施例。 [0117] 参考图。 参照图18,在第一移动终端上显示网页浏览应用的当前网页 100 ,并通过触控笔在触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将当前网页的地址传送到手写笔 300 通过无线通信连接。 [0118] 参考图。 参照图19,在第二移动终端的主界面中的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 接收存储在手写笔中的网页地址 300 通过无线通信连接。 [0119] 参考图。 参照图20,由于在第二移动终端中输入第二触摸输入时不执行网页浏览应用 101 ,网页浏览应用程序首先在第二移动终端中执行 101 . 第二个移动终端 101 提供从触控笔接收的数据 300 向执行的网页浏览应用程序,在网页浏览应用程序中打开与当前网页的地址对应的网页。 [0120] 参考图。 参照图18至图20,在一个实施例中,可以通过使用触控笔继续使用网络浏览应用的当前网页 300 . [0121] 图 图21至23示出了通过使用触控笔连续执行具有帐户登录功能的游戏应用程序 300 ,根据一个实施例。 [0122] 参考图。 参照图21,在第一移动终端中执行的游戏应用中暂停游戏 100 处于登录状态,触控笔在触摸屏上输入“O”字形的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将表示登录帐户信息的数据和表示游戏进度状态和游戏暂停位置的数据传输到触控笔 300 通过无线通信连接。 [0123] 参考图。 如图22所示,在第二移动终端主界面的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 接收指示登录帐户信息的数据和指示游戏进度状态和游戏暂停位置的数据,这些数据存储在触控笔中 300 ,通过无线通信连接。 [0124] 参考图。 23、游戏应用在第二移动终端中执行 101 ,并将接收到的数据提供给游戏应用程序。 根据提供的数据,根据登录账户的信息执行登录,在游戏应用中以暂停状态启动反映进度状态的游戏。 [0125] 参考图。 参照图21至图23,在一个实施例中,在第一移动终端暂停游戏后 100 ,用户可以在第二移动终端继续玩暂停的游戏 101 通过使用触控笔 300 ,无需额外的操作,如账户登录和存储数据的加载。 [0126]图 图6至图23仅示出了通过使用触控笔连续执行移动终端的应用的示例 300 根据实施例。 比如手写笔之间的通讯连接 300 移动终端不限于无线通信连接,也可以是有线通信连接。 有线通信连接可以通过触控笔之间的数据线形成 300 和移动终端。 此外,第一触摸输入和第二触摸输入不限于具有“C”和“P”形状的触摸手势输入,还可以是其他类型的触摸手势输入或其他类型的触摸输入。 根据一个实施例,第一触摸输入和第二触摸输入不是触摸屏上的触摸输入,而是对应于触摸输入设备中形成的触摸按钮的触摸或触摸中形成的控制按钮的按下。 输入设备。 根据另一实施例,第一触摸输入和第二触摸输入可以对应于对显示在触摸屏上的预定图标的选择。 可以理解的是,虽然已经将应用的执行示例描述为在两个移动终端中执行,但是本发明不限于此,可以在更多的终端中通过触摸输入设备来实现应用的持续执行。 或同一个终端。 [0127] 应当理解,尽管此处可以使用术语“第一”、“第二”等来描述不同的组件,但是这些组件不应受这些术语的限制。 这些组件仅用于区分一个组件与另一个组件。 例如,第一组件可以被命名为第二组件。 类似地,在不脱离实施例的范围的情况下,可以将第二组件命名为第一组件。 [0128] 应当理解,当组件或层被称为“在”、“连接到”、“耦合到”或“接触”另一个组件或另一层时,它可以直接位于、连接到、耦合到 ,或接触其他组件或其他层,或可能存在居间的组件或层。 相反,应当理解,当组件或层被称为“直接在”、“直接连接到”、“直接耦合”或“直接接触”另一个组件或另一层时,没有中间组件或 层不存在。 [0129] 应当理解,根据实施例的通过触摸输入设备控制移动终端的方法也可以体现为计算机可读记录介质上的计算机可读代码。 计算机可读记录介质可以是能够存储可由计算机系统读取的数据的任何数据存储设备。 计算机可读记录介质可以是只读存储器(ROM)、随机存取存储器(RAM)、CD-ROM、磁带、软盘、光数据存储设备和载体(通过有线传输数据 或无线传输线)。 计算机可读记录介质还可以分布在网络连接的计算机系统上,使得计算机可读代码以分布式方式存储和执行。 此外,在本发明的范围内,具有本发明所属领域的普通技术的普通程序员可以容易地推断出用于实现本发明的功能程序、代码和代码段。 [0130] 尽管已经参照其特定实施例示出和描述了本公开,但是应当理解,本领域的技术人员可以在形式和细节上做出各种改变而不背离由所附所定义的本发明的精神和范围 索赔。 [0131] 尽管已经参照附图具体示出和描述了本发明,但是应当理解,本领域普通技术人员将认识到可以以其他特定形式实践一个实施例而不背离其精神或基本特征 . 因此,应当理解,上述实施例在所有方面都是说明性的而非限制性的。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.237 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106445199A(String), KR1020170020286A(String), US10702769B2(String), US20190083881A1(String), WO2017026835A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.238 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106445199A(String), KR1020170020286A(String), US10702769B2(String), US20190083881A1(String), WO2017026835A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.239 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10702769B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.250 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106445199A(String), KR1020170020286A(String), US10702769B2(String), US20190083881A1(String), WO2017026835A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.251 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270713(Integer), CN106445199A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.260 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270713(Integer), KR1020170020286A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.272 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270713(Integer), US10702769B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.284 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270713(Integer), US20190083881A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270713(Integer), WO2017026835A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.304 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10702769B2(String), US10702769B2(String), 1594051200(Integer), 270713(Integer), 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.316 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.317 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG TIANJIN MOBILE DEVELOPMENT CENTER(String), 三星电子株式会社(String), 天津三星通信技术研究有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.319 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.321 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185038(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185038(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SAMSUNG TIANJIN MOBILE DEVELOPMENT CENTER(String), 天津三星通信技术研究有限公司(String), 0(Integer), 1681975567(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.344 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.345 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185038(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.346 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.347 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75958(Integer), 2(Integer), 185038(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.356 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.357 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.358 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.359 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.360 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.361 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.368 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.369 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.370 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.372 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.372 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.372 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185038(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.380 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160112578A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.382 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for automatic network search of mobile terminal and mobile terminal(String), 移动终端自动寻网方法及移动终端(String), US20160112578A1(String), Disclosed are an automatic network search method for a mobile terminal and a mobile terminal, and relates to the field of mobile communication. The method includes: it is judged whether there is a subscribed operator to which a user identification card is associated or not in network operators at a roaming destination when the mobile terminal is in a roaming state; the search network is performed automatically according to a priority of a network mode supported by the user identification card and the network of the subscribed operator if there is the subscribed operator with which the user identification card is associated; and the search network is performed automatically according to the priority of the network mode supported by the user identification card if there is no subscribed operator with the user identification card is associated. By the disclosure, a network required by a user may be automatically found simply and rapidly, and the mobile terminal may automatically roam, so that user experiences are improved.(String), 本发明公开了一种移动终端自动寻网方法及移动终端,涉及移动通信领域。 该方法包括:当移动终端处于漫游状态时,判断漫游目的地的网络运营商中是否存在用户识别卡所关联的签约运营商。 如果有用户识别卡关联的签约运营商,则根据用户身份证支持的网络模式和签约运营商的网络的优先级自动进行寻网。 如果没有与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级自动进行搜索网络。 通过本发明,可以简单快速地自动找到用户所需的网络,实现移动终端自动漫游,提高用户体验。(String), US14/783187(String), 1376236800(Integer), US20160112578A1(String), 1461168000(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080214240A1 | US20090186651A1 | US20100075711A1 | US20100099412A1 | US20110300844A1(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.391 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.392 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.392 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185039(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.394 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.395 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7f1cce2cf077490690091a304f678675.png(String), 185039(Integer), 7f1cce2cf077490690091a304f678675.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.402 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.404 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for automatic network search of mobile terminal and mobile terminal(String), 移动终端自动寻网方法及移动终端(String), US20160112578A1(String), Disclosed are an automatic network search method for a mobile terminal and a mobile terminal, and relates to the field of mobile communication. The method includes: it is judged whether there is a subscribed operator to which a user identification card is associated or not in network operators at a roaming destination when the mobile terminal is in a roaming state; the search network is performed automatically according to a priority of a network mode supported by the user identification card and the network of the subscribed operator if there is the subscribed operator with which the user identification card is associated; and the search network is performed automatically according to the priority of the network mode supported by the user identification card if there is no subscribed operator with the user identification card is associated. By the disclosure, a network required by a user may be automatically found simply and rapidly, and the mobile terminal may automatically roam, so that user experiences are improved.(String), 本发明公开了一种移动终端自动寻网方法及移动终端,涉及移动通信领域。 该方法包括:当移动终端处于漫游状态时,判断漫游目的地的网络运营商中是否存在用户识别卡所关联的签约运营商。 如果有用户识别卡关联的签约运营商,则根据用户身份证支持的网络模式和签约运营商的网络的优先级自动进行寻网。 如果没有与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级自动进行搜索网络。 通过本发明,可以简单快速地自动找到用户所需的网络,实现移动终端自动漫游,提高用户体验。(String), US14/783187(String), 1376236800(Integer), US20160112578A1(String), 1461168000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080214240A1 | US20090186651A1 | US20100075711A1 | US20100099412A1 | US20110300844A1(String), \20230420\7f1cce2cf077490690091a304f678675.png(String), 15(Integer), 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.416 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 1. An automatic network search method for a mobile terminal, comprising:when the mobile terminal is in a roaming state, judging whether there is, in a plurality of network operators at a roaming destination, a subscribed operator with which a user identification card is associated;based on that there is the subscribed operator with which the user identification card is associated, automatically searching for a network according to a priority of network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator; andbased on that there is no subscribed operator with which the user identification card is associated, automatically searching for a network according to the priority of the network mode supported by the user identification card.(String), 1.根据权利要求2所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 2. The method according to claim 1, wherein before judging whether there is, in the plurality of network operators at the roaming destination, the subscribed operator with which the user identification card is associated when the mobile terminal is in the roaming state, the method further comprises:judging whether the mobile terminal is in the roaming state or not; andbased on that the mobile terminal is not in the roaming state, automatically searching for the network according to a network search manner set by the mobile terminal.(String), 12.根据权利要求3所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 3. The method according to claim 2, wherein before judging whether the mobile terminal is in the roaming state or not, the method further comprises:detecting one or more card slots of the mobile terminal in real time;reading information about an operator which issues the user identification card and information about a network mode supported by the user identification card when it is detected that the user identification card is inserted into one of the one or more card slots; andstoring the information about the operator which issues the user identification card and information about the network mode supported by the user identification card.(String), 13.根据权利要求4所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 4. The method according to claim 3, wherein judging whether the mobile terminal is in the roaming state or not comprises:searching, according to the network mode, for a network in an area where the mobile terminal is located to obtain at least one parameter of the network in the area where the mobile terminal is located; andcomparing the at least one parameter of the network in the area where the mobile terminal is located with at least one network parameter in the information about the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not.(String), 14.根据权利要求5所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.417 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 5. The method according to claim 4, wherein searching, according to the network mode, for the network in the area where the mobile terminal is located to obtain the at least one parameter of the network in the area where the mobile terminal is located comprises:when the user identification card supports multiple network modes, sequentially searching for networks corresponding to the corresponding network modes according to priorities of the multiple network modes until the at least one parameter of the network in the area where the mobile terminal is located is obtained.(String), 15.根据权利要求6所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 6. The method according to claim 5, wherein comparing the at least one parameter of network in the area where the mobile terminal is located with the at least one network parameter in the information of the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not comprises:based on that the at least one parameter of the network in the area where the mobile terminal is located is matched with the at least one network parameter in the information of the operator which issues the user identification card, determining that the mobile terminal is in a non-roaming state, otherwise determining that the mobile terminal is in the roaming state.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 7. The method according to claim 1, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 8. A mobile terminal for searching for a network automatically, comprising:a subscribed operator determination component configured to, when the mobile terminal is in a roaming state, judge whether there is, in a plurality of network operators at a roaming destination, a subscribed operator to which a user identification card is associated; anda network search component configured to, when there is the subscribed operator with which the user identification card is associated, automatically search for a network according to a priority of a network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator, and automatically search for the network according to the priority of the network mode supported by the user identification card when there is no subscribed operator to which the user identification card is associated.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 9. The mobile terminal according to claim 8, further comprising:a roaming determination component configured to judge whether the mobile terminal is in the roaming state or not to enable the network search component to automatically search for the network according to a network search manner set by the mobile terminal under the condition that the mobile terminal is not in the roaming state.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 10. The mobile terminal according to claim 9, further comprising:a detection component configured to detect one or more card slots of the mobile terminal in real time;an in-card information acquisition component configured to, when it is detected that the user identification card is inserted into one of the one or more card slots, read information about an operator which issues the user identification card and information about the network mode supported by the User identification card; anda storage component configured to store the information about the operator which issues the user identification card and information about the supported network mode.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 11. The method according to claim 2, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 12. The method according to claim 3, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.418 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 13. The method according to claim 4, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 12(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 14. The method according to claim 5, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 13(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.419 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185039(Integer), 15. The method according to claim 6, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 14(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185039(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of mobile communication, and in particular to an automatic network search method for a mobile terminal and a related mobile terminal. BACKGROUND [0002]Mobile technology changes life, mobile terminals spread all over the world at present, and one or more operators may operate mobile networks in many countries and areas in the world. Due to upgrading of network systems or regulation of national policies in different times, each operator may operate networks of many systems, and issued mobile telephone cards may be developed from single-mode cards to dual-mode cards and then to multimode cards in the future. In order to compete for customers and solve the problem of frequent mobile phone changing without card (number) changing of users, terminals of the operators support double card slots instead of single card slots, and may be developed to support multiple card slots in the future. [0003]Along with increasing population movement, a terminal must meet requirements of many mobile users on automatic roaming as much as possible, which promotes continuous upgrading of card slots in the terminal from support to single-mode cards to dual-mode cards and then to multimode cards. Diversity of network systems and complexity in mobile terminals cause variability of network search of the mobile terminals, and how to enable a terminal to rapidly and accurately find a network required by a user is a complicated problem. [0004]At present, there are two methods for solving the problem: [0005]1: when a mobile terminal roams to an area of another network operator, it is necessary for a user to search for and switch a network in a manual manner, such a manner has a high requirement on professional knowledge of the user and requires the user to find the network by many operating steps and then switch the network, and if the user does not perform manual searching and complete switching, the mobile terminal may fail to roam, which may cause influence on normal occurrence of a service of the user as well as poor user experiences; and [0006]2: the terminal automatically and randomly searches the whole frequency band for the network after being started, and in such a manner, intentionality is poor and the network is usually searched for a longer time, which wastes time of the user and is unfavourable for life of a battery of the terminal. SUMMARY [0007]The embodiment of the disclosure provides an automatic network search method for a mobile terminal and a mobile terminal, which may better solve a problem about automatic and rapid network search of the mobile terminal. [0008]According to one aspect of the embodiment of the disclosure, an automatic network search method for a mobile terminal is provided, which includes: [0009]when the mobile terminal is in a roaming state, judging whether there is, in a plurality of network operators at a roaming destination, a subscribed operator with which a user identification card is associated; [0010]based on that there is the subscribed operator with which the user identification card is associated, automatically searching for a network according to a priority of network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator; and [0011]based on that there is no subscribed operator with which the user identification card is associated, automatically searching for a network according to the priority of the network mode supported by the user identification card. [0012]Preferably, before judging whether there is, in the plurality of network operators at the roaming destination, the subscribed operator with which the user identification card is associated when the mobile terminal is in the roaming state, the method further comprises: judging whether the mobile terminal is in the roaming state or not; and based on that the mobile terminal is not in the roaming state, automatically searching for the network according to a network search manner set by the mobile terminal. [0013]Preferably, before judging whether the mobile terminal is in the roaming state or not, the method further comprises: detecting one or more card slots of the mobile terminal in real time; reading information about an operator which issues the user identification card and information about a network mode supported by the user identification card when it is detected that the user identification card is inserted into one of the one or more card slots; and storing the information about the operator which issues the user identification card and information about the network mode supported by the user identification card. [0014]Preferably, judging whether the mobile terminal is in the roaming state or not comprises: searching, according to the network mode, for a network in an area where the mobile terminal is located to obtain at least one parameter of the network in the area where the mobile terminal is located; and comparing the at least one parameter of the network in the area where the mobile terminal is located with at least one network parameter in the information about the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not. [0015]Preferably, searching, according to the network mode, for the network in the area where the mobile terminal is located to obtain the at least one parameter of the network in the area where the mobile terminal is located comprises: when the user identification card supports multiple network modes, sequentially searching for networks corresponding to the corresponding network modes according to priorities of the multiple network modes until the at least one parameter of the network in the area where the mobile terminal is located is obtained. [0016]Preferably, comparing the at least one parameter of network in the area where the mobile terminal is located with the at least one network parameter in the information of the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not comprises: based on that the at least one parameter of the network in the area where the mobile terminal is located is matched with the at least one network parameter in the information of the operator which issues the user identification card, determining that the mobile terminal is in a non-roaming state, otherwise determining that the mobile terminal is in the roaming state. [0017]Preferably, the method further includes: [0018]when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards. [0019]According to the other aspect of the embodiment of the disclosure, a mobile terminal for searching a network automatically is provided, which includes: [0020]a subscribed operator determination component configured to, when the mobile terminal is in a roaming state, judge whether there is, in a plurality of network operators at a roaming destination, a subscribed operator to which a user identification card is associated ; and a network search component configured to, when there is the subscribed operator with which the user identification card is associated, automatically search for a network according to a priority of a network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator, and automatically search for the network according to the priority of the network mode supported by the user identification card when there is no subscribed operator to which the user identification card is associated. [0021]Preferably, the mobile terminal further includes: [0022]a roaming determination component configured to judge whether the mobile terminal is in the roaming state or not to enable the network search component to automatically search for the network according to a network search manner set by the mobile terminal under the condition that the mobile terminal is not in the roaming state. [0023]Preferably, the mobile terminal further includes: [0024]a detection component configured to detect one or more card slots of the mobile terminal in real time; [0025]an in-card information acquisition component configured to, when it is detected that the user identification card is inserted into one of the one or more card slots, read information about an operator which issues the user identification card and information about the network mode supported by the User identification card; and [0026]a storage component configured to store the information about the operator which issues the user identification card and information about the supported network mode. [0027]Compared with the related art, the embodiment of the disclosure has beneficial effects as follows: [0028]by the embodiment of the disclosure, a network required by a user may be automatically found simply and rapidly by pertinent network search, and the mobile terminal may automatically roam, so that user experiences are improved. BRIEF DESCRIPTION OF THE DRAWINGS [0029]FIG. 1 is a functional block diagram of an automatic network search method for a mobile terminal according to an embodiment of the disclosure; [0030]FIG. 2 is a structure diagram of a mobile terminal according to an embodiment of the disclosure; [0031]FIG. 3 is a working flowchart of a mobile terminal for searching a network automatically according to an embodiment of the disclosure; and [0032]FIG. 4 is a flowchart of an automatic network search method for a mobile terminal according to an embodiment of the disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS [0033]The preferred embodiment of the disclosure is described below with reference to the drawings in detail. It is should be understood that the preferred embodiment described below is only adopted to explain the disclosure and not intended to limit the disclosure. [0034]In an embodiment of the disclosure, when a terminal detects that a user identification card (for example: a Subscriber Identity Module (SIM) card and a User Identity Module (UIM) card, called card hereinafter for short) is inserted into a current card slot, information about an operator which issues the card and information about a network mode supported by the card are read and stored, the terminal determines an area where the card is currently located and judges weather the terminal is in a roaming state after being started. A network is automatically searched according to a network search manner set by the terminal if the terminal is in a non-roaming state, and if the terminal is in the roaming state, information about a network corresponding to a subscribed operator, at a roaming destination, to which the operator issuing the card has subscribed is acquired from a storage component of the terminal according to the area where the terminal is currently located, and then the network is automatically searched according to a priority of the network mode supported by the card and a network mode of the subscribed operator, so that a function of finishing automatically selecting the network without user intervention is realized. [0035]FIG. 1 is a functional block diagram of an automatic network search method for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 1, the method includes the following steps: [0036]Step 101: it is judged whether there is a subscribed operator, with which of a user identification card is associated, in a plurality of network operators at a roaming destination when a mobile terminal is in a roaming state. [0037]Before Step 101, the method further includes: one or more card slots of the mobile terminal in real time are detected. When it is detected that the user identification card is inserted into one of the one or more card slots, information about an operator which issues the user identification card and a network mode supported by the user identification card is read and stored. A network in an area where the mobile terminal is located is searched to obtain at least one parameter of the network in the area where the mobile terminal is located according to the network mode. The at least one parameter of the network in the area where the mobile terminal is located is compared with a network parameter in the information about the subscribed operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not. Preferably, when the user identification card supports multiple network modes, networks corresponding to the corresponding network modes are sequentially searched according to priorities of the multiple network modes until the at least one parameter of the network in the area where the mobile terminal is located is obtained. [0038]When the at least one parameter of the network in the area where the mobile terminal is located is matched with the at least one network parameter in the information about the subscribed operator which issues the user identification card, it is determined that the mobile terminal is in a non-roaming state, otherwise the mobile terminal is in the roaming state. When the mobile terminal is in the non-roaming state, the network is automatically searched according to a network search manner set by the mobile terminal. [0039]Step 102: if there is the subscribed operator with which the user identification card is associated, an automatic search network is performed according to a priority of the network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator. [0040]Step 103: if there is no subscribed operator with which the user identification card is associated, an automatic search network is performed according to the priority of the network mode supported by the user identification card. [0041]A mobile terminal may include one or more (including two or more than two) card slots, for example, sequentially numbered as card slots 1, 2, 3 . . . , and the card slots with smaller numbers are formed in front. If the mobile terminal includes only one card slot, the card slot is a main card slot, and if the mobile terminal includes multiple card slots, card slot 1 defaults to be the main card slot, the other card slots are additional card slots, and one of the additional card slots may be set to be the main card slot by user. [0042]For a main card slot, if a terminal detects that a card has been inserted into the main card slot when being started, the terminal reads and stores information about an operator which issues the card and a network mode supported by the card. The terminal searches for a network according to a first-priority network mode supported by the card, and judges an area where the card is currently located and whether the terminal is currently in a roaming state or not. An optimal network is selected automatically according to the roaming state of the terminal, an area operated by the operator and the network mode supported by the card. A network system including, but not limited to, network systems such as Long Term Evolution (LTE), Code Division Multiple Access (CDMA) (1X, Evolution-Data Optimized (EVDO)), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) and Global System for Mobile Communications (GSM). [0043]For an additional card slot, steps of a network search manner is consistent with the steps for the main card slot. The terminal is started. The terminal reads and stores information of an operator which issues the card and a network mode supported by the card if the terminal detects that a card has been inserted into the additional card slot. and the terminal judges an area where the terminal is currently located and a roaming state of the terminal. A search network is performed according to a network search manner set by the terminal if the terminal is in a non-roaming state, and if the terminal is located in a roaming destination, it is necessary to automatically research for a network according to a priority of the network mode supported by the card and a priority of a network mode operated by a subscribed operator, at the roaming destination, with which the operator issuing the card is associated. [0044]It is necessary to additionally consider that: when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, the user identification cards inserted in high-priority card slots preferably use the conflicting hardware resources and/or network resources according to the priorities of the multiple card slots corresponding to the multiple user identification cards. That is, when the hardware resources and network resources of the terminal conflict with the card slots, for example, a network conflict of the same system occurs to the main card slot and the additional card slots, the hardware resources and the network resources are preferably used by the main card slot (or the card slots with smaller numbers), and when the main card slot or the card slots with smaller numbers are recovered into other systems, the conflict is released, and the additional card slots may be recovered into non-conflicting states. [0045]One embodiment of the disclosure further provides a mobile terminal for searching a network automatically, which includes: [0046]a subscribed operator determination component configured to judge whether there is a subscribed operator with which a user identification card is associated or not in a plurality of network operators at a roaming destination when the mobile terminal is in a roaming state; [0047]a network search component configured to automatically search for a network according to a priority of a network mode supported by the user identification card and a priority of the network of the subscribed operator if there is the subscribed operator with which the user identification card is associated, and automatically search for a network according to the priority of the network mode supported by the user identification card if there is no subscribed operator with which the user identification card is associated; [0048]a detection component configured to detect one or more card slots of the mobile terminal in real time; [0049]an in-card information acquisition component configured to read information of an operator which issues the user identification card and the network mode supported by the user identification card when it is detected that the user identification card is inserted into one of the one or more card slots; [0050]a storage component configured to store the information about the operator which issues the user identification card and the supported network mode; and [0051]a roaming determination component configured to judge whether the mobile terminal is in the roaming state or not to enable the network search component to automatically search for the network according to a network search manner set by the mobile terminal if the mobile terminal is not in the roaming state. [0052]The network search component is further configured to automatically search for a network corresponding to the network mode supported by the user identification card when the mobile terminal is in the roaming state and the operator which issues the user identification card has not subscribed to a subscribed operator in an area where the mobile terminal is located, and is configured to, when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enable the user identification card in higher priority card slot to preferably use the conflicting hardware resources and/or network resources according to the priorities of multiple card slots corresponding to the multiple user identification cards. [0053]FIG. 2 is a structure diagram of a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 2, the mobile terminal includes a master control component 201, a card slot and management component 202, a network selection component 203, a receiving/sending component 204, a storage component 205, a display component 206 and a power component 207, wherein [0054]the master control component 201 mainly controls coordinated operation of the whole terminal system. [0055]The card slot and management component 202 provides card slots for the terminal system and their corresponding interfaces for card data reading and writing and the like and functions such as management, and determines that the terminal is currently in a roaming state according to read information about the operator which issues the user identification card inserted in the card slot and temporary network related information (network parameters) acquired in a searching process of the network selection component 203. That is, the card slot and management component 202 realizes functions of the abovementioned detection component, in-card information acquisition component and roaming determination component. [0056]The network selection component 203 is configured to execute network search, network authentication, network switching, a power-saving network search strategy and the like according to the roaming state of the terminal and information of subscribed operator in the storage component 205. That is, the network selection component 203 realizes functions of the abovementioned subscribed operator determination component and network search component. [0057]The receiving/sending component 204 is configured to send data to be sent by the terminal to a network side, or receive data sent to the terminal by the network side, wherein a type of the data is a service type or a data type, and the receiving/sending component is a gateway for interaction between the terminal and a network. [0058]The storage component 205 is configured to store related information such as temporary data, service data and historical data in a running process of the terminal, store information (including, but not limited to, related information such as the name of the network operator, the network parameters of the network operator (a Master Control Code (MCC), a Mobile Network Code (MNC) and the like), the network mode, priorities of networks to be selected by a user within an operating area and the subscribed operators) to which the card in the current card slot of the terminal has subscribed. The information about the operator can be updated automatically, and for example, when the operator which issues the user identification card has newly updated subscribed operator information, the user is notified for manual upgrading or the terminal is notified for automatic upgrading in background. [0059]The display component 206 is configured to display the current state of the terminal and feed back information of the terminal to the user. [0060]The power component 207 provides power for the terminal, and provides a power distribution and management function involved in the terminal system. [0061]FIG. 3 is a working flowchart of a mobile terminal for automatically searching a network according to an embodiment of the disclosure, and the flow includes the following steps: [0062]Step 301: the terminal is powered on, and configuration of a main card slot and additional card slots (if existing) of the current terminal is acquired from a card slot and management component. [0063]If the terminal includes only one card slot, Step 302 is executed, and if the terminal further has the additional card slots, Step 308 is executed. [0064]Step 302: the terminal detects whether a card is currently inserted into the main card slot or not, and if the terminal detects that the card has been inserted into the main card slot, the terminal reads and stores information about an operator which issues the card and a network mode supported by the terminal, and turns to Step 303. [0065]Step 303: the terminal searches for a network at first according to priorities of networks operated by the operator which issues the card, and judges an area where the terminal is currently located and whether the terminal is currently in a roaming state or not according to the network parameters after the network is successfully searched, Step 304 is executed if the terminal is in a non-roaming state, and Step 305 is executed if the terminal is in the roaming state. [0066]Step 304: if the terminal is currently in the non-roaming state, the search network is automatically performed according to a network search manner set by the terminal, the network search manner includes an automatic mode or a CDMA-only or other single network-only mode. [0067]Step 305: if the terminal is currently in the roaming state, an operator information table stored by a storage component is looked up according to the area, where the terminal is located, determined in Step 303, information of the network operated by a subscribed operator, at a roaming destination, to which the operator issuing the card has subscribed is acquired, Step 306 is executed if there is the subscribed operator, and Step 307 is executed if there is no subscribed operator. [0068]Step 306: if there is a subscribed operator, at the roaming destination, to which the operator issuing the card has subscribed, the search network is sequentially and automatically performed according to the network mode supported by the card and a priority of the network of the subscribed operator. [0069]Step 307: if there is not a subscribed operator, at the roaming destination, to which the operator issuing the card has subscribed, the search network is sequentially and automatically performed according to the priority of the network mode supported by the card. [0070]Step 308: if the terminal includes an additional card slot, a network search flow is the same as the network search flow for the main card slot, but it is necessary to additionally consider that when there is a conflict between hardware resources and/or network resources of the terminal and the number of the card slots, for example, a network conflict of the same system occurs to the main card slot and the additional card slot, the hardware resources and the network resources are preferably used by the main card slot (or the card slots with smaller numbers), and when the main card slot or the card slot with smaller number are recovered into other system, the conflict is released, and the additional card slot or the card slot with larger number may be recovered into the state before conflicting. [0071]FIG. 4 is a flowchart of an automatic network search method for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 4, the method includes the following steps: [0072]Step 401: the terminal is powered on, and configuration of a main card slot and additional card slots (if existing) of the current terminal is acquired from a card slot and management component. [0073]If the terminal includes only one card slot, Step 402 is executed; and if the terminal further has an additional card slot, Step 408 is executed. [0074]Step 402: if the terminal is powered on and it is detected that a card has been inserted into the main card slot, the terminal reads and stores information about an operator which issues the card and a network mode supported by the card, and turns to Step 403. [0075]Scenario 1 4021: the terminal reads information about that a CDMA GSM dual-mode card of China Telecom is inserted into the main card slot, the operator is China Telecom, network parameters MCC and MNC are 46002 and the network modes are CDMA and GSM. [0076]Scenario 2 4022: the terminal reads information about that a CDMA GSM dual-mode card of a branch of China Telecom in Macao is inserted into the main card slot, the operator is the branch of China Telecom in Macao, the network parameters MCC and MNC are 45502 and the network modes are CDMA and GSM. [0077]Scenario 3 4023: the terminal reads information about that a CDMA GSM dual-mode card of Softbank of Japan is inserted into the main card slot, the operator is Softbank of Japan, the network parameters MCC and MNC are 44020 and the network modes are CDMA and GSM. [0078]Step 403: due to the fact that the network modes supported by the card in the card slot are CDMA and GSM, the terminal preferably searches for a CDMA network with a higher priority, finds MCC and MNC are 46002, judges that the terminal is currently in Mainland China according to country code 460, and compares and matches Mainland China with operator information read from the card to determine that the terminal is in a roaming state. [0079]For scenario 1 4021 in Step 402, the terminal is determined to be in a non-roaming state, and Step 404 is executed. [0080]For scenario 2 4022 and scenario 3 4023 in Step 402, the MCC and MNC of the terminal are determined to be mismatched with MCC and MNC contained in the information about the operator which issues the card, the terminal is determined to be in the roaming state, and Step 405 is executed. [0081]Step 404: the terminal is in the non-roaming state, and the search network is automatically performed according to a network search manner (such as an automatic mode) set by the terminal. [0082]For scenario 1 4021 in Step 402, a CDMA network of Mainland China is searched, network China Telecom 46002 is found, then it is determined that searching is successful and the terminal passes authentication, the terminal successfully resides in the network, and enters a standby state. The network search process is completed. [0083]Step 405: if the terminal is currently in the roaming state, an operator information table stored by a storage component is queried to judge whether there is a subscribed operator, at the roaming destination, to which the operator issues the card has subscribed. [0084]For scenario 2 4022, there is the subscribed operator China Telecom in Mainland China, and Step 406 is executed. [0085]For scenario 3 4023, if Softbank has not subscribed to any subscribed operator in Mainland China, Step 407 is executed. [0086]Step 406: if the operator which issues the card has the subscribed operator at the roaming destination, the search network is sequentially and automatically performed according to the network mode supported by the card and a priority of the network of the subscribed operator. [0087]For scenario 2 4022, for a card issued by the branch of China Telecom in Macao, the CDMA network of China Telecom is preferably searched, and if the terminal successfully searches for the CDMA network 46002 and passes authentication, the terminal succeeds in network search and residence. [0088]Step 407: if the operator which issues the card has not the subscribed operator at the roaming destination, the network is sequentially and automatically searched according to the priority of the network mode supported by the card. [0089]For scenario 3 4023, for a card issued by Softbank of Japan, a CDMA network is preferably searched, it is determined that the network search fails if 46002 is successfully found but the terminal cannot reside for reasons such as insufficient signal intensity, the terminal automatically searches for the next mode GSM, and for example, if a GSM network of China Mobile is successfully found and the terminal successfully resides and passes authentication, the card roams to the GSM network of China Mobile and is successfully registered. [0090]Step 408: a network search flow for the additional card slot is the same as the network search flow for the main card slot, but when there is a conflict between hardware resources and/or network resources of the terminal and the number of the card slots, for example, a network conflict of the same system occurs to the main card slot and the additional card slot, the hardware resources and the network resources are preferably used by the main card slot (or the card slot with smaller number), and when the main card slot or the card slot with smaller numbers are recovered into other system, the conflict is released, and the additional card slot or the card slot with larger numbers may be recovered into the state before conflicting. [0091]In Step 408, if a CDMA/GSM dual-mode card is in(String), 技术领域 [0001] 本发明涉及移动通信领域,尤其涉及一种移动终端自动搜网的方法及相关移动终端。 背景 [0002] 移动技术改变生活,目前移动终端遍布全球,一个或多个运营商可能在全球多个国家和地区运营移动网络。 由于不同时期网络系统的升级或国家政策的调整,每个运营商可能运营多个制式的网络,发行的手机卡未来可能会从单模卡发展到双模卡再到多模卡 . 为争夺客户,解决用户频繁换机不换卡(号)的问题,运营商终端支持双卡槽,不再支持单卡槽,未来可能会发展为支持多卡槽 . [0003] 随着人口流动的增加,终端必须尽可能满足众多移动用户对自动漫游的需求,这促使终端卡槽不断升级,从支持单模卡到双模卡再到多模卡 . 网络制式的多样性和移动终端的复杂性导致移动终端的网络搜索存在差异,如何使终端能够快速、准确地找到用户需要的网络是一个复杂的问题。 [0004] 目前解决问题的方法有两种: [0005] 1:当移动终端漫游到另一个网络运营商的区域时,需要用户手动搜索和切换网络,这种方式对用户的专业知识要求很高,需要用户 需要通过很多操作步骤找到网络,然后切换网络,如果用户不手动搜索并完成切换,移动终端可能无法漫游,也可能影响用户业务的正常进行 糟糕的用户体验; 和 [0006] 2:终端开机后自动全频段随机搜索网络,这种方式主观性差,搜索网络的时间通常较长,浪费用户时间,不利于生活 终端的电池。 概括 [0007] 本发明实施例提供了一种移动终端自动搜网的方法及移动终端,可以更好地解决移动终端自动快速搜网的问题。 [0008] 根据本发明实施例的一个方面,提供了一种移动终端的自动网络搜索方法,包括: [0009] 当移动终端处于漫游状态时,判断漫游目的地的多个网络运营商中是否存在用户识别卡关联的签约运营商; [0010] 基于存在用户识别卡关联的签约运营商,根据用户识别卡支持的网络模式优先级和签约运营商对应的网络优先级自动搜索网络; 和 [0011] 基于没有用户识别卡关联的签约运营商,根据用户识别卡支持的网络模式的优先级自动搜索网络。 [0012] 优选地,在判断所述移动终端处于漫游状态时,所述漫游目的地的多个网络运营商中是否存在所述用户识别卡关联的签约运营商之前,所述方法还包括:判断所述移动终端是否 是否处于漫游状态; 基于移动终端未处于漫游状态,根据移动终端设置的网络搜索方式自动搜索网络。 [0013]优选地,在判断移动终端是否处于漫游状态之前,该方法还包括: 实时检测移动终端的一个或多个卡槽; 当检测到用户识别卡插入一个或多个卡槽之一时,读取发行用户识别卡的运营商信息和用户识别卡支持的网络模式信息; 存储发行用户识别卡的运营商信息和用户识别卡支持的网络模式信息。 [0014] 优选地,判断移动终端是否处于漫游状态包括:根据网络模式搜索移动终端所在区域的网络,获取移动终端所在区域的网络的至少一个参数。 移动终端位于; 将移动终端所在区域的网络的至少一参数与发行用户识别卡的运营商信息中的至少一网络参数进行比较,判断移动终端是否处于漫游状态。 . [0015] 优选地,根据网络模式搜索移动终端所在区域的网络,获取移动终端所在区域的网络的至少一个参数包括: 当用户识别卡支持多个时 网络模式,根据多种网络模式的优先级依次搜索对应的网络模式对应的网络,直到获取移动终端所在区域的网络的至少一个参数。 [0016] 优选地,将所述移动终端所在区域的至少一网络参数与签发用户识别卡的运营商信息中的所述至少一网络参数进行比较,判断移动终端是否处于漫游状态或者 不包括:基于移动终端所在区域的网络的至少一参数与发行用户标识卡的运营商的信息中的至少一网络参数匹配,确定移动终端 处于非漫游状态,否则判定移动终端处于漫游状态。 [0017] 优选地,该方法还包括: [0018] 当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。 多个用户识别卡对应的多个卡槽的优先级。 [0019] 根据本发明实施例的另一个方面,提供了一种自动搜索网络的移动终端,包括: [0020] 签约运营商判断模块,用于当移动终端处于漫游状态时,判断漫游目的地的多个网络运营商中是否存在与用户识别卡关联的签约运营商; 网络搜索模块,用于当存在用户识别卡关联的签约运营商时,根据用户识别卡支持的网络模式的优先级和对应的网络的优先级自动搜索网络 签约的运营商,当没有签约的运营商关联用户识别卡时,根据用户识别卡支持的网络模式的优先级自动搜索网络。 [0021] 优选地,所述移动终端还包括: [0022] 漫游判断模块,用于判断移动终端是否处于漫游状态,使网络搜索模块在移动终端未处于漫游状态的情况下,根据移动终端设置的网络搜索方式自动搜索网络。 处于漫游状态。 [0023]优选地,所述移动终端还包括: [0024] 检测模块,用于实时检测移动终端的一个或多个卡槽; [0025] 卡内信息获取模块,用于在检测到所述用户识别卡插入所述一个或多个卡槽之一时,读取所述用户识别卡的发行运营商信息和支持的网络模式信息 用户识别卡; 和 [0026] 存储模块,用于存储发行用户识别卡的运营商信息和支持的网络模式信息。 [0027] 与现有技术相比,本发明实施例具有以下有益效果: [0028] 通过本发明实施例,可以通过有针对性的网络搜索,简单快速地自动找到用户需要的网络,并实现移动终端的自动漫游,提高了用户体验。 附图的简要说明 [0029] 图1是根据本发明实施例的移动终端自动搜网方法的功能框图; [0030] 图2是根据本发明实施例的移动终端的结构图; [0031] 图3是根据本发明实施例的移动终端自动搜网的工作流程图; 和 [0032] 图4是根据本发明实施例的移动终端自动搜网方法的流程图。 具体实施方式 [0033] 下面结合附图对本发明的优选实施例进行详细说明。 应当理解,下述所描述的优选实施例仅仅用于解释本发明,并不用于限定本发明。 [0034] 在本发明的一个实施例中,当终端检测到用户识别卡(例如:SIM卡和UIM卡,以下简称卡)插入当前卡时 读取并存储卡槽、发卡运营商信息和卡支持的网络模式信息,终端启动后判断卡当前所在区域,判断终端是否处于漫游状态。 如果终端处于非漫游状态,则根据终端设置的网络搜索方式自动搜索网络,如果终端处于漫游状态,则在漫游目的地获取签约运营商对应的网络信息 根据终端当前所在区域从终端的存储组件中获取发卡运营商签约的网络,然后根据卡支持的网络模式的优先级自动搜索网络, 签约运营商的网络模式,从而实现无需用户干预即可完成自动选网的功能。 [0035] 图1是根据本发明实施例的移动终端自动搜网方法的功能框图,如图1所示,该方法包括以下步骤: [0036] 步 101 :判断移动终端处于漫游状态时,在漫游目的地的多个网络运营商中是否存在与用户识别卡关联的签约运营商。 [0037] 步骤前 101,该方法还包括:实时检测移动终端的一个或多个卡槽。 当检测到用户识别卡插入一个或多个卡槽之一时,读取并存储发行用户识别卡的运营商和用户识别卡支持的网络模式的信息。 根据网络制式搜索移动终端所在区域的网络,获取移动终端所在区域的网络的至少一个参数。 将移动终端所在区域的网络的至少一个参数与签发用户识别卡的签约运营商信息中的网络参数进行比较,判断移动终端是否处于漫游状态。 优选地,当用户识别卡支持多种网络制式时,根据多种网络制式的优先级依次搜索相应网络制式对应的网络,直至获取移动终端所在区域网络的至少一个参数。 . [0038] 当移动终端所在区域网络的至少一参数与签发用户识别卡的签约运营商信息中的至少一网络参数匹配时,确定移动终端处于 非漫游状态,否则移动终端处于漫游状态。 当移动终端处于非漫游状态时,根据移动终端设置的网络搜索方式自动搜索网络。 [0039] 步 102 :如果存在用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级和签约运营商对应的网络的优先级进行自动搜网。 [0040] 步 103 :如果没有用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级进行自动搜网。 [0041] 移动终端可以包括一个或多个(包括两个或两个以上)卡槽,例如依次编号为卡槽1、2、3。 . . , 数字较小的卡槽在前面。 如果移动终端只有一个卡槽,则该卡槽为主卡槽,如果移动终端有多个卡槽,则默认1号卡槽为主卡槽,其他卡槽为附加卡槽, 用户可以将其中一个附加卡槽设置为主卡槽。 [0042] 对于主卡槽,如果终端在启动时检测到有卡插入主卡槽,则终端读取并存储该卡的发卡运营商信息和该卡支持的网络模式。 终端根据卡支持的优先网络模式搜索网络,判断卡当前所在的区域以及终端当前是否处于漫游状态。 根据终端的漫游状态、运营商运营区域和卡片支持的网络模式,自动选择最优网络。 网络系统包括但不限于长期演进(LTE)、码分多址(CDMA)(1X,Evolution-Data Optimized(EVDO))、宽带码分多址(WCDMA)、时间等网络系统 同步码分多址 (TD-SCDMA) 和全球移动通信系统 (GSM)。 [0043]对于附加卡槽,网络搜索方式的步骤与主卡槽的步骤一致。 终端已启动。 终端在检测到有卡插入附加卡槽时,读取并存储卡的发卡运营商信息和卡支持的网络模式。 终端判断终端当前所在的区域和终端的漫游状态。 如果终端处于非漫游状态,则按照终端设置的网络搜索方式进行搜索,如果终端位于漫游目的地,则需要按照优先级自动搜索网络 卡支持的网络模式的优先级以及在漫游目的地由发行卡的运营商关联的订阅运营商运营的网络模式的优先级。 [0044] 还需要考虑:当移动终端的多个用户识别卡的硬件资源和/或网络资源发生冲突时,插入高优先级卡槽的用户识别卡优先使用冲突的硬件资源和/或 或者根据多个用户识别卡对应的多个卡槽的优先级分配网络资源。 即,当终端的硬件资源和网络资源与卡槽发生冲突时,例如主卡槽和副卡槽发生同系统网络冲突时,优选硬件资源和网络资源。 主卡槽(或编号较小的卡槽)使用,当主卡槽或编号较小的卡槽回收到其他系统时,冲突解除,附加卡槽可能回收到非 - 冲突状态。 [0045] 本发明实施例还提供了一种自动搜索网络的移动终端,包括: [0046] 签约运营商判断模块,用于当移动终端处于漫游状态时,判断漫游目的地的多个网络运营商中是否存在与用户识别卡关联的签约运营商; [0047] 网络搜索模块,用于如果存在与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级和签约运营商网络的优先级自动搜索网络, 如果没有与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级自动搜索网络; [0048] 检测模块,用于实时检测移动终端的一个或多个卡槽; [0049] 卡内信息获取模块,用于在检测到所述用户识别卡插入所述一个或多个卡槽之一时,读取所述用户识别卡的发行运营商信息和用户识别卡支持的网络模式 ; [0050] 存储模块,用于存储发行用户识别卡的运营商信息和支持的网络模式; 和 [0051] 漫游判断模块,用于判断移动终端是否处于漫游状态,若移动终端未处于漫游状态,则网络搜索模块根据移动终端设置的网络搜索方式自动搜索网络 状态。 [0052]网络搜索模块,还用于当移动终端处于漫游状态,且发行用户识别卡的运营商未签约签约运营商时,自动搜索用户识别卡支持的网络模式对应的网络。 移动终端所在区域,用于当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,优先使用优先级高的卡槽中的用户识别卡 根据多个用户识别卡对应的多个卡槽的优先级,冲突的硬件资源和/或网络资源。 [0053] 图2为本发明实施例提供的一种移动终端的结构图,如图2所示,该移动终端包括总控组件 201 、卡槽和管理组件 202 , 一个网络选择组件 203 , 接收/发送组件 204 , 一个存储组件 205 , 显示组件 206 和一个电源组件 207 , 其中 [0054] 主控组件 201 主要控制整个终端系统的协调运行。 [0055] 卡槽及管理组件 202 为终端系统提供卡槽及其对应的接口,用于卡数据读写等功能和管理等功能,根据读取到的发卡运营商信息判断终端当前处于漫游状态 插入卡槽和网络选择模块搜索过程中获取的临时网络相关信息(网络参数) 203 . 即卡槽和管理组件 202 实现了上述检测模块、卡内信息获取模块和漫游判断模块的功能。 [0056] 网络选择组件 203 用于根据终端的漫游状态和存储模块中签约运营商的信息,执行网络搜索、网络认证、网络切换、省电网络搜索策略等。 205 . 即网络选择组件 203 实现上述签约运营商确定模块和网络搜索模块的功能。 [0057] 接收/发送组件 204 用于向网络侧发送终端要发送的数据,或接收网络侧向终端发送的数据,其中,数据的类型为业务类型或数据类型,接收/发送模块为 终端与网络交互的网关。 [0058] 存储组件 205 用于存储终端运行过程中的临时数据、业务数据、历史数据等相关信息,存储信息(包括但不限于网络运营商名称、网络参数等相关信息) 卡所在的网络运营商(Master Control Code(MCC)、Mobile Network Code(MNC)等)、网络模式、用户在操作区域内选择的网络优先级以及签约的运营商) 终端当前卡槽已订阅。 运营商信息可以自动更新,例如,当发放用户识别卡的运营商有最新更新的签约运营商信息时,通知用户手动升级或通知终端后台自动升级。 [0059] 显示组件 206 用于显示终端的当前状态,并向用户反馈终端的信息。 [0060] 电源组件 207 为终端提供电源,提供终端系统涉及的电源分配和管理功能。 [0061]图3是根据本发明实施例的移动终端自动搜网的工作流程图,该流程包括以下步骤: [0062] 步 301 :终端上电,从卡槽和管理组件获取当前终端的主卡槽和附加卡槽(如果存在)的配置。 [0063] 如果终端只有一个卡槽,步骤 302 执行,若终端还具有附加卡槽,步骤 308 被执行。 [0064] 步 302 :终端检测当前主卡槽中是否插入了卡片,如果终端检测到主卡槽中插入了卡片,则终端读取并存储发卡运营商信息和 终端支持的网络模式,转步骤 303 . [0065] 步 303 :终端首先根据发卡运营商运营的网络的优先级搜索网络,根据网络参数判断终端当前所在区域以及终端当前是否处于漫游状态 搜索网络成功后,步骤 304 终端处于非漫游状态时执行,步骤 305 如果终端处于漫游状态则执行。 [0066] 步 304 :若终端当前处于非漫游状态,则根据终端设置的搜网方式自动进行搜网,搜网方式包括自动方式或CDMA-only或其他单一网络-only方式 . [0067] 步 305 :若终端当前处于漫游状态,则根据步骤中确定的终端所在区域,查找存储模块存储的运营商信息表 303 , 获取发卡运营商签约的漫游目的地签约运营商运营的网络信息, 步骤 306 如果有订阅的操作员,则执行,并且步骤 307 如果没有订阅的操作员,则执行。 [0068] 步 306 :如果漫游目的地有发卡运营商签约的签约运营商,则根据卡支持的网络模式和签约运营商的网络优先级顺序自动搜索网络 . [0069] 步 307 :如果漫游目的地没有签约的运营商,发卡运营商签约,则根据卡支持的网络模式的优先级顺序自动搜索网络。 [0070] 步 308 :如果终端包含附加卡槽,则网络搜索流程与主卡槽的网络搜索流程相同,但需要额外考虑当硬件资源和/或网络资源之间存在冲突时 终端和卡槽数量,例如主卡槽和副卡槽出现同系统网络冲突,硬件资源和网络资源优先使用主卡槽(或副卡槽) 号较小的卡槽),当主卡槽或编号较小的卡槽恢复到其他系统时,冲突解除,附加卡槽或编号较大的卡槽可以恢复到之前的状态 矛盾的。 [0071] 图4为本发明实施例提供的一种移动终端自动搜网方法的流程图,如图4所示,该方法包括以下步骤: [0072] 步 401 :终端上电,从卡槽和管理组件获取当前终端的主卡槽和附加卡槽(如果存在)的配置。 [0073] 如果终端只有一个卡槽,步骤 402 被执行; 如果终端还有额外的卡槽,步骤 408 被执行。 [0074] 步 402 :如果终端上电,检测到有卡插入主卡槽,终端读取并存储发卡运营商信息和卡支持的网络模式,转步骤 403 . [0075] 场景一4021:终端读取到主卡槽中插入了一张中国电信的CDMA GSM双模卡,运营商为中国电信,网络参数MCC和MNC为46002,网络制式为CDMA和GSM。 [0076] 场景2 4022:终端读取主卡槽插入中国电信澳门分公司的CDMA GSM双模卡信息,运营商为中国电信澳门分公司,网络参数MCC和MNC 是45502,网络模式是CDMA和GSM。 [0077] 场景3 4023:终端读取到主卡槽中插入日本软银的CDMA GSM双模卡,运营商为日本软银,网络参数MCC和MNC为44020,网络模式为CDMA 和全球移动通信系统。 [0078] 步 403 :由于卡槽中的卡支持的网络模式为CDMA和GSM,终端优先搜索优先级高的CDMA网络,发现MCC和MNC为46002,判断终端当前在大陆 中国根据国家代码460,将中国大陆与从卡中读取的运营商信息进行比对,确定终端处于漫游状态。 [0079] 对于Step中的场景1 4021 402 ,确定终端处于非漫游状态,步骤 404 被执行。 [0080] 对于Step中的场景2 4022和场景3 4023 402 ,确定终端的MCC和MNC与发卡运营商信息中的MCC和MNC不匹配,确定终端处于漫游状态, 步骤 405 被执行。 [0081] 步 404 :终端处于非漫游状态,按照终端设置的搜网方式(如自动模式)自动搜网。 [0082] 对于Step中的场景1 4021 402 ,搜索中国大陆CDMA网络,搜索到网络中国电信46002,则确定搜索成功,终端鉴权通过,终端成功入网,进入待机状态。 网络搜索过程完成。 [0083] 步 405 :若终端当前处于漫游状态,则查询存储模块存储的运营商信息表,判断漫游目的地是否有运营商签约的运营商发卡签约的运营商。 [0084] 对于场景2 4022,有中国大陆签约运营商中国电信,步骤 406 被执行。 [0085] 对于场景3 4023,如果Softbank在中国大陆没有签约任何运营商,步骤 407 被执行。 [0086] 步 406 :如果发卡运营商在漫游目的地有签约运营商,则根据卡支持的网络模式和签约运营商网络的优先级顺序自动搜索网络。 [0087] 对于场景2 4022,对于中国电信澳门分行发行的卡,优先搜索中国电信的CDMA网络,如果终端成功搜索到CDMA网络46002并认证通过,则终端搜索网络成功, 住宅。 [0088] 步 407 :如果发卡运营商在漫游目的地没有签约运营商,则按照卡支持网络模式的优先级依次自动搜索网络。 [0089]场景3 4023,对于日本软银发行的卡,优先搜索CDMA网络,如果成功搜索到46002,则判断网络搜索失败,但由于信号强度不足等原因导致终端无法驻留,终端自动 搜索下一制式GSM,如成功搜索到中国移动GSM网络,终端成功驻留并认证通过,卡漫游到中国移动GSM网络,注册成功。 [0090] 步 408 :副卡位的网络搜索流程与主卡位的网络搜索流程相同,但是当终端的硬件资源和/或网络资源与卡位的数量存在冲突时,对于 例如主卡槽和副卡槽出现同系统网络冲突,硬件资源和网络资源优先使用主卡槽(或编号较小的卡槽),当主卡槽 将卡槽或编号较小的卡槽恢复到其他系统,解除冲突,可以将新增的卡槽或编号较大的卡槽恢复到冲突前的状态。 [0091] 在步骤 408 ,如果CDMA/GSM双模卡插入主卡槽,卡成功注册到CDMA网络,终端搜网时CDMA网络信号质量低于驻留门限,终端 主卡槽和副卡槽只有一套GSM射频电路,主卡槽的卡最好漫游到GSM网络,而副卡槽的卡只能离线 等待状态。 CDMA网络信号质量恢复正常后,主卡槽恢复注册到CDMA网络,副卡槽以省电模式周期性寻找GSM网络,鉴权成功,入驻 在 GSM 网络中可能被允许。 [0092] 本发明实施例支持终端为单卡槽的情况,也支持双卡槽、三卡槽及更多卡槽的移动终端,卡槽中的卡可以是最简单的单模卡, 也可以是双模卡、多模卡等各种条件的组合。 [0093] 本发明实施例涉及的网络制式包括GSM、CDMA、WCDMA、CDMA2000(1x/EVDO)、TD-SCDMA以及后续的LTE-A等多种制式。 [0094] 综上所述,本发明实施例的技术效果如下:本发明实施例实现逻辑清晰,无需用户手动操作即可自动搜索网络,给用户带来了极大的方便,方便了用户使用。 经验得到改善。 [0095] 以上虽然对本发明进行了详细的说明,但本发明并不限于此,本领域的技术人员可以根据本发明的原理做出各种修改。 因此,凡是依据本发明的原则所做的修改,均应落入本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104105166A(String), CN104105166B(String), EP2986059A1(String), EP2986059A4(String), US20160112578A1(String), WO2014166185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.553 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104105166A(String), CN104105166B(String), EP2986059A1(String), EP2986059A4(String), US20160112578A1(String), WO2014166185A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.555 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20160112578A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104105166A(String), CN104105166B(String), EP2986059A1(String), EP2986059A4(String), US20160112578A1(String), WO2014166185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), CN104105166A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.573 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), CN104105166B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.584 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.585 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), EP2986059A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), EP2986059A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), US20160112578A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.615 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), WO2014166185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.624 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20160112578A1(String), US20160112578A1(String), 1461168000(Integer), 270714(Integer), 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.636 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.637 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.639 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.640 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.641 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185039(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.642 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185039(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.649 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.651 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185039(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.652 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 2(Integer), 185039(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.660 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.661 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.662 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.663 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.676 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185039(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10638311B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Communication method for mobile terminal and mobile terminal(String), 移动终端的通信方法及移动终端(String), US10638311B2(String), Embodiments of the present disclosure disclose a secure communication method for a mobile terminal and a mobile terminal. The secure communication method may include: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performing, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and outputting, by using the secure virtual kernel, communication content obtained by performing the preset policy-based processing.(String), 本发明实施例公开了一种移动终端的安全通信方法及移动终端。 所述安全通信方法可以包括:当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序 从访问安全虚拟内核和公共虚拟内核之间的共享内存到访问无线通信连接需要调用的外围设备; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设的基于策略的处理; 使用安全虚拟内核输出经过预设的基于策略的处理得到的通信内容。(String), US15/795491(String), 1509033600(Integer), US10638311B2(String), 1588003200(Integer), 1588003200(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 29(Integer), CN102045712A | CN102209318A | CN102271191A | CN102307346A | CN102413462A | CN102761409A | CN102857914A | CN103197991A | CN103249036A | CN103457958A | CN103577740A | CN1585539A | EP2648129A1 | KR1020130062219A | US20070270170A1 | US20120216242A1 | US20130145475A1 | US20130179403A1 | US20140007120A1 | US20140045545A1 | US20140148123A1 | US20140281560A1 | US20170011206A1 | US20170220823A1 | US20190104114A1 | US20190166638A1 | WO2014137343A1 | WO2014141206A1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.698 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.699 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185040(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.701 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.702 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\a4836c763d3d43978eb09beeb7ad4b36.png(String), 185040(Integer), a4836c763d3d43978eb09beeb7ad4b36.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.710 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.711 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.712 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.713 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.713 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Communication method for mobile terminal and mobile terminal(String), 移动终端的通信方法及移动终端(String), US10638311B2(String), Embodiments of the present disclosure disclose a secure communication method for a mobile terminal and a mobile terminal. The secure communication method may include: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performing, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and outputting, by using the secure virtual kernel, communication content obtained by performing the preset policy-based processing.(String), 本发明实施例公开了一种移动终端的安全通信方法及移动终端。 所述安全通信方法可以包括:当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序 从访问安全虚拟内核和公共虚拟内核之间的共享内存到访问无线通信连接需要调用的外围设备; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设的基于策略的处理; 使用安全虚拟内核输出经过预设的基于策略的处理得到的通信内容。(String), US15/795491(String), 1509033600(Integer), US10638311B2(String), 1588003200(Integer), 1588003200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 29(Integer), CN102045712A | CN102209318A | CN102271191A | CN102307346A | CN102413462A | CN102761409A | CN102857914A | CN103197991A | CN103249036A | CN103457958A | CN103577740A | CN1585539A | EP2648129A1 | KR1020130062219A | US20070270170A1 | US20120216242A1 | US20130145475A1 | US20130179403A1 | US20140007120A1 | US20140045545A1 | US20140148123A1 | US20140281560A1 | US20170011206A1 | US20170220823A1 | US20190104114A1 | US20190166638A1 | WO2014137343A1 | WO2014141206A1(String), \20230420\a4836c763d3d43978eb09beeb7ad4b36.png(String), 12(Integer), 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.725 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.726 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.726 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 1. A secure communication method for a mobile terminal, wherein an application processor of the mobile terminal comprises a secure virtual kernel and a common virtual kernel which share a central processing unit (CPU), a memory, a bus, and a peripheral that are of the mobile terminal, and wherein a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel, the secure communication method comprising:when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by the mobile terminal, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and from accessing a peripheral used by the wireless communication connection;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing; andwherein before the wireless communication connection is established between the mobile terminal and the other mobile terminal, the secure communication method further comprises:prohibiting, by the mobile terminal, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition.(String), 1.根据权利要求7所述的移动终端,其中:无线通讯连接所使用的外设包括录像装置,通讯内容包括录制的视频信号。处理单元包括:第二加密子单元,用于当通信内容为视频录制设备录制的视频信号时,通过安全虚拟内核对录制的视频信号进行加密处理,第二编码子单元,用于使用安全虚拟内核对加密处理后的视频信号进行编码,得到待发送的视频信号;和输出单元,用于通过安全虚拟内核控制移动终端向另一移动终端发送待发送视频信号。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.726 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 2. The method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises an audio recording device, and the communication content comprises a recorded audio signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is an audio signal recorded by the audio recording device, performing, by the mobile terminal, encryption processing on the recorded audio signal by using the secure virtual kernel, andcoding, by the mobile terminal by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal.(String), 12.根据权利要求7所述的移动终端,其中:无线通讯连接所使用的外设包括显示器,通讯内容包括接收到的视频信号。处理单元还包括:第二解码子单元,用于当通信内容为移动终端接收到的视频信号时,使用安全虚拟内核对接收到的视频信号进行解码;第二解密子单元,用于利用安全虚拟内核对解码后的视频信号进行解密处理,得到待播放视频信号;和输出单元用于通过安全虚拟内核控制显示器播放待播放视频信号。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.726 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 3. The method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is an audio signal received by the mobile terminal, decoding, by the mobile terminal, the audio signal by using the secure virtual kernel, andperforming, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by the mobile terminal by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 4. The method according to claim 2, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is an audio signal received by the mobile terminal, decoding, by the mobile terminal, the audio signal by using the secure virtual kernel, andperforming, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by the mobile terminal by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 5. The secure communication method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises a video recording device, and the communication content comprises a recorded video signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is a video signal recorded by the video recording device, performing, by the mobile terminal, encryption processing on the recorded video signal by using the secure virtual kernel, andcoding, by the mobile terminal by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 6. The secure communication method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises a display, and the communication content comprises a received video signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is a video signal received by the mobile terminal, decoding, by the mobile terminal, the received video signal by using the secure virtual kernel, andperforming, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by the mobile terminal by using the secure virtual kernel, the display to play the to-be-played video signal.(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 7. A mobile terminal, wherein an application processor of the mobile terminal comprises a secure virtual kernel and a common virtual kernel which share a central processing unit (CPU), a memory, a bus, and a peripheral that are of the mobile terminal, and a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel, the mobile terminal comprising:a first setting unit, configured to: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibit, by means of setting, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and accessing a peripheral to be used by the wireless communication connection;a processing unit, configured to perform, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection;an output unit, configured to output, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing; anda second setting unit, configured to prohibit, by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition.(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 8. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises an audio recording device, and the communication content comprises a recorded audio signal;the processing unit comprises:a first encryption subunit, configured to: when the communication content is an audio signal recorded by the audio recording device, perform encryption processing on the recorded audio signal by using the secure virtual kernel, anda first coding subunit, configured to code, by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; andthe output unit is configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 9. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;the processing unit comprises:a first decoding subunit, configured to: when the communication content is an audio signal received by the mobile terminal, decode the audio signal by using the secure virtual kernel, anda first decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andthe output unit is configured to control, by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.727 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 10. The mobile terminal according to claim 8, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;the processing unit comprises:a first decoding subunit, configured to: when the communication content is an audio signal received by the mobile terminal, decode the audio signal by using the secure virtual kernel, anda first decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andthe output unit is configured to control, by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 11. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises a video recording device, and the communication content comprises a recorded video signal;the processing unit comprises:a second encryption subunit, configured to: when the communication content is a video signal recorded by the video recording device, perform encryption processing on the recorded video signal by using the secure virtual kernel, anda second coding subunit, configured to code, by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; andthe output unit is configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal.(String), 1(Integer), 10(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.728 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185040(Integer), 12. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises a display, and the communication content comprises a received video signal;the processing unit further comprises:a second decoding subunit, configured to: when the communication content is a video signal received by the mobile terminal, decode the received video signal by using the secure virtual kernel, anda second decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; andthe output unit is configured to control, by using the secure virtual kernel, the display to play the to-be-played video signal.(String), 1(Integer), 11(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185040(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2015/098761, filed on Dec. 24, 2015, which claims priority to Chinese Patent Application No. 201510217336.8, filed on Apr. 30, 2015. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present application relates to the communications field, and in particular, to a secure communication method for a mobile communications terminal and a mobile communications terminal. BACKGROUND [0003]With development of mobile communications technologies, mobile terminals have been widely popular, and the mobile terminals have become necessities in daily life of a user. When working, shopping, or taking recreation by using a mobile terminal, the user transmits private information. The private information may be eavesdropped on by a criminal, and therefore lead to serious consequences such as privacy disclosure and a property loss of the user. Mobile communication security has been increasingly concerned about by the government, the society, and the user, and network security and information security issues have even risen to a national strategic height. [0004]In the prior art, before a call is initiated or answered by using a mobile terminal, a process that includes a recording module is usually searched and ended, so as to prevent call content from being secretly recorded, thereby preventing a background process from eavesdropping. [0005]In the foregoing method, the background process is prevented from eavesdropping when an operating system of the mobile terminal is trusted. However, nowadays, as functions of mobile terminals are increasingly abundant, architectures of operating systems of the mobile terminals are increasingly complex, and there is a growing quantity of security vulnerabilities. Therefore, a communication security technology that can be used to prevent attacks from the operating systems needs to be urgently developed. SUMMARY [0006]Embodiments of the present disclosure disclose a secure communication method for a mobile terminal and a mobile terminal, to prevent an operating system from eavesdropping on communication content of a user, and improve communication security of the mobile terminal. [0007]A first aspect of the embodiments of the present disclosure discloses a secure communication method for a mobile terminal, where an application processor of the mobile terminal includes a secure virtual kernel and a common virtual kernel, the secure virtual kernel and the common virtual kernel share a central processing unit CPU, a memory, a bus, and a peripheral that are of the mobile terminal, and a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel; and [0008]the secure communication method includes: [0009]when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by the mobile terminal by means of setting, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; [0010]performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and [0011]outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing. [0012]With reference to the first aspect, in a first feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio recording device, and the communication content includes a recorded audio signal; [0013]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0014]when the communication content is an audio signal recorded by the audio recording device, performing, by the mobile terminal, encryption processing on the recorded audio signal by using the secure virtual kernel; and [0015]coding, by the mobile terminal by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; and [0016]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0017]controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal. [0018]With reference to the first aspect or the first feasible implementation of the first aspect, in a second feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio playing device, and the communication content includes a received audio signal; [0019]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0020]when the communication content is an audio signal received by the mobile terminal, decoding, by the mobile terminal, the audio signal by using the secure virtual kernel; and [0021]performing, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; and [0022]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0023]controlling, by the mobile terminal by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal. [0024]With reference to any one of the first aspect, or the first to the second feasible implementations of the first aspect, in a third feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a video recording device, and the communication content includes a recorded video signal; [0025]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0026]when the communication content is a video signal recorded by the video recording device, performing, by the mobile terminal, encryption processing on the recorded video signal by using the secure virtual kernel; and [0027]coding, by the mobile terminal by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; and [0028]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0029]controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal. [0030]With reference to any one of the first aspect, or the first to the third feasible implementations of the first aspect, in a fourth feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a display, and the communication content includes a received video signal; [0031]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0032]when the communication content is a video signal received by the mobile terminal, decoding, by the mobile terminal, the received video signal by using the secure virtual kernel; and [0033]performing, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; and [0034]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0035]controlling, by the mobile terminal by using the secure virtual kernel, the display to play the to-be-played video signal. [0036]With reference to any one of the first aspect, or the first to the fourth feasible implementations of the first aspect, in a fifth feasible implementation, before the wireless communication connection is established between the mobile terminal and the another mobile terminal, the secure communication method further includes: [0037]prohibiting, by the mobile terminal by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition. [0038]A second aspect of the embodiments of the present disclosure provides a mobile terminal, where an application processor of the mobile terminal includes a secure virtual kernel and a common virtual kernel, the secure virtual kernel and the common virtual kernel share a central processing unit CPU, a memory, a bus, and a peripheral that are of the mobile terminal, and a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel; and [0039]the mobile terminal includes: [0040]a first setting unit, configured to: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibit, by means of setting, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; [0041]a processing unit, configured to perform, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and [0042]an output unit, configured to output, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing. [0043]With reference to the second aspect, in a first feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio recording device, and the communication content includes a recorded audio signal; [0044]the processing unit includes: [0045]a first encryption subunit, configured to: when the communication content is an audio signal recorded by the audio recording device, perform encryption processing on the recorded audio signal by using the secure virtual kernel; and [0046]a first coding subunit, configured to code, by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; and [0047]the output unit is specifically configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal. [0048]With reference to the second aspect or the first feasible implementation of the second aspect, in a second feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio playing device, and the communication content includes a received audio signal; [0049]the processing unit includes: [0050]a first decoding subunit, configured to: when the communication content is an audio signal received by the mobile terminal, decode the audio signal by using the secure virtual kernel; and [0051]a first decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; and [0052]the output unit is specifically configured to control, by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal. [0053]With reference to any one of the second aspect, or the first to the second feasible implementations of the second aspect, in a third feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a video recording device, and the communication content includes a recorded video signal; [0054]the processing unit includes: [0055]a second encryption subunit, configured to: when the communication content is a video signal recorded by the video recording device, perform encryption processing on the recorded video signal by using the secure virtual kernel; and [0056]a second coding subunit, configured to code, by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; and [0057]the output unit is specifically configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal. [0058]With reference to any one of the second aspect, or the first to the third feasible implementations of the second aspect, in a fourth feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a display, and the communication content includes a received video signal; [0059]the processing unit includes: [0060]a second decoding subunit, configured to: when the communication content is a video signal received by the mobile terminal, decode the received video signal by using the secure virtual kernel; and [0061]a second decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; and [0062]the output unit is specifically configured to control, by using the secure virtual kernel, the display to play the to-be-played video signal. [0063]With reference to any one of the second aspect, or the first to the fourth feasible implementations of the second aspect, in a fifth feasible implementation, the mobile terminal further includes: [0064]a second setting unit, configured to prohibit, by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection. [0065]In the embodiments of the present disclosure, when a wireless communication connection is established between a mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, the mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performs, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and then outputs, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing, so that an operating system and the program running in the common virtual kernel can be prevented from obtaining unprocessed communication content, and the operating system can also be prevented from eavesdropping on the communication content by using the shared memory or the related peripheral, thereby improving communication security of the mobile terminal. BRIEF DESCRIPTION OF DRAWINGS [0066]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0067]FIG. 1 is a schematic flowchart of an embodiment of a secure communication method for a mobile terminal in the present disclosure; [0068]FIG. 2 is a schematic flowchart of another embodiment of a secure communication method for a mobile terminal in the present disclosure; [0069]FIG. 3 is a schematic flowchart of still another embodiment of a secure communication method for a mobile terminal in the present disclosure; [0070]FIG. 4 is a schematic structural diagram of an embodiment of a mobile terminal in the present disclosure; [0071]FIG. 5 is a schematic structural diagram of another embodiment of a mobile terminal in the present disclosure; [0072]FIG. 6 is a schematic structural diagram of still another embodiment of a mobile terminal in the present disclosure; and [0073]FIG. 7 is a schematic structural diagram of yet another embodiment of a mobile terminal in the present disclosure. DETAILED DESCRIPTION [0074]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0075]With reference to the accompanying drawings, the following describes in detail a secure communication method for a mobile terminal and a mobile terminal that are provided in the embodiments of the present disclosure. In the embodiments of the present disclosure, the mobile terminal includes but is not limited to a terminal that may be used for communication, such as a mobile phone, a personal computer, or a notebook computer. [0076]Referring to FIG. 1, FIG. 1 is a schematic flowchart of an embodiment of a secure communication method for a mobile terminal in the present disclosure. As shown in FIG. 1, in this embodiment, the secure communication method includes the following steps. [0077]S101. When a wireless communication connection is established between a mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, the mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection. [0078]In this embodiment of the present disclosure, a CPU (central processing unit) of the mobile terminal includes at least an application processor. When the mobile terminal is a mobile phone, the CPU of the mobile terminal further includes a baseband processor. The application processor includes a secure virtual kernel and a common virtual kernel, and the secure virtual kernel and the common virtual kernel share a CPU, a memory, a peripheral, and a bus that are of the mobile terminal. In a specific implementation, the secure virtual kernel exclusively occupies some application processor hardware resources, and the program in the common virtual kernel is prohibited from accessing the application processor resources exclusively occupied by the secure virtual kernel. [0079]In a specific implementation, a baseband system of the mobile terminal runs in the baseband processor; some security modules run in the secure virtual kernel; and an operating system of the mobile terminal runs in the common virtual kernel, such as Android, iOS, or Windows Phone. [0080]In a feasible implementation, the mobile terminal may be a mobile terminal that uses an ARM (advanced reduced instruction set computing machine) processor and that is based on a TrustZone technology. [0081]Optionally, the wireless communication connection may include but is not limited to: a common telephone connection, a network voice connection (including a network telephone connection or another voice connection between real-time communications clients), a network video connection, or the like. [0082]In some feasible implementations, in this embodiment of the present disclosure, when short message communication or mail communication may be further performed between the mobile terminal and the another mobile terminal, the program in the common virtual kernel is prohibited, by means of setting, from accessing the shared memory between the secure virtual kernel and the common virtual kernel and assessing the peripheral that needs to be called for the short message communication or the mail communication. The peripheral that needs to be called for the short message communication or the mail communication may include one or more of a push-button, a keyboard, a tablet, or a display. [0083]In some feasible implementations, it may be determined, by detecting some trigger actions of the mobile terminal, that the wireless communication connection is established between the mobile terminal and the another mobile terminal; for example, when it is detected that the mobile terminal performs a dialing operation, or when it is detected that the mobile terminal logs in to a real-time communications client, it may be considered that the wireless communication connection is established between the mobile terminal and the another mobile terminal. [0084]In some feasible implementations, it may be determined, by detecting some interrupt signals related to the wireless communication connection, that the wireless communication connection is established between the mobile terminal and the another mobile terminal; for example, when an incoming call is made by the another mobile terminal, the application processor receives incoming call information interrupt request sent by the baseband processor. [0085]Optionally, that the wireless communication connection meets the preset security processing trigger condition may be: The other mobile terminal that establishes the wireless communication connection to the mobile terminal meets a security condition set by the mobile terminal, for example, the wireless communication connection is a wireless communication connection between the mobile terminal and a buddy in an address book, or may be: A type of the wireless communication connection meets a security type set by the mobile terminal, for example, the wireless communication connection is a telephone connection. [0086]In some feasible implementations, after being powered on, the mobile terminal may prohibit, by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition. For example, when detecting any incoming call signal or detecting an incoming call signal of the buddy in the address book, the baseband system sends the incoming call information interrupt request to the application processor. Because the program in the common virtual kernel is prohibited, by means of presetting, from accessing the incoming call information interrupt request, the application processor processes the incoming call information interrupt request by using the secure virtual kernel after receiving the incoming call information interrupt request. [0087]Optionally, when the wireless communication connection relates to a voice call (such as a common telephone call, a network telephone call, or a voice session initiated by using a real-time communications client), the peripheral that needs to be called includes at least an audio recording device and an audio playing device. In a specific implementation, the audio recording device and the audio playing device may be a same device, for example, a microphone of the mobile terminal. [0088]Optionally, when the wireless communication connection relates to a video call, the peripheral that needs to be called includes at least a video recording device, an audio recording device, an audio playing device, and a display, such as a camera, a microphone, and a display that are of the mobile terminal. [0089]In some feasible implementations, the mobile terminal may set, to a security interrupt and by using a GIC (generic interrupt controller) or a TZIC (TrustZone interrupt controller), the interrupt information related to the wireless communication connection, so that the interrupt information is accessed only in the secure virtual kernel. In a specific implementation, the GIC or the TZIC is connected to all interrupt sources of the mobile terminal, and may first intercept an interrupt request of the mobile terminal; and the GIC or the TZIC hands over, to the secure virtual kernel, an interrupt request related to the wireless communication connection for processing. [0090]In some feasible implementations, the mobile terminal divides a physical memory into multiple memory areas by using a TZASC (TrustZone address space controller), and configures, by using software running in the secure virtual kernel, some memory areas to be secure memory areas or non-secure memory areas, and the TZASC may prohibit the program running in the common virtual kernel from accessing the secure memory area. [0091]In some feasible implementations, the mobile terminal configures a security attribute of the peripheral by using a TZPC (TrustZone protection controller), classifies the peripheral as a secure peripheral or a non-secure peripheral, and prohibits the program running in the common virtual kernel from accessing the secure peripheral. [0092]S102. The mobile terminal performs, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection. [0093]Optionally, the communication content corresponding to the wireless communication connection includes communication content to be sent by the mobile terminal and communication content received by the mobile terminal. [0094]Optionally, for the to-be-sent communication content, the preset policy-based processing may include one or more of encryption, analog-to-digital conversion, coding, modulation, or the like. For the received communication content, the preset policy-based processing may include one or more of decryption, demodulation, decoding, digital-to-analog conversion, or the like. The preset policy-based processing is performed by using the secure virtual kernel of the mobile terminal, and the program in the common virtual kernel cannot access communication content obtained before the preset policy-based processing is performed. [0095]In a specific implementation, because there is a large amount of code in an operating system running in a common virtual kernel, there is a relatively large quantity of security vulnerabilities. Because there is a small amount of code in a module running in a secure virtual kernel, security can be easily verified. Preset policy-based processing is performed on communication content by using the secure virtual kernel, so that the operating system running in the common virtual kernel can be prevented from obtaining communication content obtained before the preset policy-based processing is performed, and the operating system can be prevented from eavesdropping on the communication content. [0096]S103. The mobile terminal outputs, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing. [0097]In a specific implementation, after performing the preset policy-based processing on the communication content to be sent by the mobile terminal, the mobile terminal may send the to-be-sent communication content by using a radio frequency module or a wireless network connection module. Communication content of a telephone call or a short message may be sent by using the radio frequency module of the mobile terminal; and communication content of a mail, a network voice call, a video call, or the like may be sent by using the wireless network connection module. In this embodiment of the present disclosure, the network connection module may be a Wi-Fi module, and is configured to enable the mobile terminal to access the Internet. [0098]After performing the preset policy-based processing on the communication content received by the mobile terminal, the mobile terminal may output the received communication content. Optionally, if the received communication content is a voice, the received communication content may be output by using an audio playing device (for example, a microphone); if the received communication content is a video, the received communication content may be output by using a display and an audio playing device; or if the received communication content is a text or a picture, the received communication content may be output by using a display. [0099]In this embodiment of the present disclosure, when a wireless communication connection is established between a mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, the mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performs, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and then outputs, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing, so that an operating system and the program running in the common virtual kernel can be prevented from obtaining unprocessed communication content, and the operating system can also be prevented from eavesdropping on the communication content by using the shared memory or the related peripheral, thereby improving communication security of the mobile terminal. [0100]Referring to FIG. 2, FIG. 2 is a schematic flowchart of another embodiment of a secure communication method for a mobile terminal in the present disclosure. As shown in FIG. 2, in this embodiment, the secure communication method includes the following steps. [0101]S201. A mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing interrupt information related to a wireless communication connection that meets a preset security processing trigger condition. [0102]Optionally, the wireless communication connection may include but is not limited to: a common telephone connection, a network voice connection (including a network telephone connection or another voice connection between real-time communications clients), a network video connection, or the like. [0103]In some feasible implementations, in addition to the interrupt info/Elation related to the wireless communication connection that meets the preset security processing trigger condition, the mobile terminal may further prohibit, by means of setting, the program in the common virtual kernel from accessing some interrupt signals related to a specific type of the wireless communication connection, such as a short message or a mail. [0104]Optionally, that the wireless communication connection meets the preset security processing trigger condition may be: Another mobile terminal that establishes the wireless communication connection to the mobile terminal meets a security condition set by the mobile terminal, for example, the wireless communication connection is a wireless communication connection between the mobile terminal and a buddy in an address book, or may be: A type of the wireless communication connection meets a security type set by the mobile terminal, for example, the wireless communication connection is a telephone connection. [0105]In a specific implementation, after being powered on, the mobile terminal(String), 相关申请的交叉引用 [0001] 本申请是2015年12月24日提交的国际申请号PCT/CN2015/098761的继续申请,该国际申请要求2015年4月30日提交的中国专利申请号201510217336.8的优先权。上述申请的公开内容是 特此通过引用整体并入。 技术领域 [0002] 本申请涉及通信领域,尤其涉及一种移动通信终端的安全通信方法及移动通信终端。 背景 [0003] 随着移动通信技术的发展,移动终端得到了广泛的普及,移动终端已经成为用户日常生活中的必需品。 用户在使用移动终端工作、购物或娱乐时,会传递隐私信息。 隐私信息可能被不法分子窃听,从而导致用户隐私泄露、财产损失等严重后果。 移动通信安全越来越受到政府、社会和用户的关注,网络安全和信息安全问题甚至上升到国家战略高度。 [0004] 现有技术中,在使用移动终端发起或接听电话之前,通常会搜索并结束包含录音模块的进程,以防止通话内容被偷录,从而防止后台进程窃听。 [0005] 上述方法在移动终端操作系统可信的情况下,防止后台进程窃听。 然而,如今,随着移动终端的功能越来越丰富,移动终端的操作系统架构也越来越复杂,安全漏洞也越来越多。 因此,迫切需要开发一种能够防止操作系统攻击的通信安全技术。 概括 [0006] 本发明实施例公开了一种移动终端的安全通信方法及移动终端,以防止操作系统窃听用户的通信内容,提高移动终端的通信安全性。 [0007] 本发明实施例的第一方面公开了一种移动终端的安全通信方法,移动终端的应用处理器包括安全虚拟内核和公共虚拟内核,安全虚拟内核和公共虚拟内核共享一个安全虚拟内核。 禁止移动终端的中央处理器CPU、内存、总线和外设以及公共虚拟内核中的程序访问安全虚拟内核的应用处理器资源。 和 [0008] 安全通信方法包括: [0009] 当移动终端与另一移动终端建立无线通信连接,且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核与普通虚拟内核共享内存,访问无线通信连接需要调用的外设; [0010] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 和 [0011] 移动终端通过安全虚拟内核输出经过预设策略处理得到的通信内容。 [0012] 结合第一方面,在第一种可行的实现方式中,所述无线通信连接需要调用的外设包括录音设备,所述通信内容包括录制的音频信号; [0013]移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0014] 当通信内容为录音设备录制的音频信号时,移动终端利用安全虚拟内核对录制的音频信号进行加密处理。 和 [0015] 移动终端利用安全虚拟内核对加密处理后的音频信号进行编码,得到待发送的音频信号; 和 [0016] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0017] 通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号。 [0018] 结合第一方面或第一方面的第一种可行的实现方式,在第二种可行的实现方式中,所述无线通信连接需要调用的外设包括音频播放设备,所述通信内容包括接收到的音频信号; [0019] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0020] 当通信内容为移动终端接收到的音频信号时,移动终端使用安全虚拟内核对音频信号进行解码; 和 [0021] 移动终端利用安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号; 和 [0022] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0023] 移动终端通过安全虚拟内核控制音频播放设备播放待播放的音频信号。 [0024] 结合第一方面或第一方面的第一种至第二种可行的实现方式中的任一种,在第三种可行的实现方式中,所述无线通信连接需要调用的外设包括录像设备,所述通信 内容包括录制的视频信号; [0025] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0026] 当通信内容为视频录制设备录制的视频信号时,移动终端利用安全虚拟内核对录制的视频信号进行加密处理。 和 [0027] 移动终端利用安全虚拟内核对加密处理后的视频信号进行编码,得到待发送的视频信号; 和 [0028] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0029] 通过安全虚拟内核控制移动终端向另一移动终端发送待发送视频信号。 [0030] 结合第一方面或第一方面的第一种至第三种可行的实现方式中的任一种,在第四种可行的实现方式中,所述无线通信连接需要调用的外设包括显示器,所述通信内容包括: 接收到的视频信号; [0031] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0032]当通信内容为移动终端接收到的视频信号时,移动终端利用安全虚拟内核对接收到的视频信号进行解码; 和 [0033] 移动终端利用安全虚拟内核对解码后的视频信号进行解密处理,得到待播放的视频信号; 和 [0034] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0035] 移动终端通过安全虚拟内核控制显示器播放待播放的视频信号。 [0036] 结合第一方面或第一方面的第一种至第四种可行的实现方式中的任一种,在第五种可行的实现方式中,在移动终端与另一移动终端之间建立无线通信连接之前,安全通信方法 进一步包括: [0037] 移动终端通过设置禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0038] 本发明实施例的第二方面提供了一种移动终端,该移动终端的应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享中央处理器CPU, 禁止移动终端的内存、总线和外设以及公共虚拟内核中的程序访问安全虚拟内核的应用处理器资源。 和 [0039] 移动端包括: [0040] 第一设置单元,用于当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟机中的程序 内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; [0041] 处理单元,用于通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 和 [0042] 输出单元,用于通过所述安全虚拟内核输出所述预设策略处理得到的通信内容。 [0043] 结合第二方面,在第一种可行的实现方式中,所述无线通信连接需要调用的外设包括录音设备,所述通信内容包括录制的音频信号; [0044] 处理单元包括: [0045] 第一加密子单元,用于当通信内容为录音设备录制的音频信号时,通过安全虚拟内核对录制的音频信号进行加密处理; 和 [0046] 第一编码子单元,用于使用安全虚拟内核对加密处理后的音频信号进行编码,得到待发送的音频信号; 和 [0047] 输出单元具体用于通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号。 [0048] 结合第二方面或第二方面的第一种可行的实现方式,在第二种可行的实现方式中,所述无线通信连接需要调用的外设包括音频播放设备,所述通信内容包括接收到的音频信号; [0049] 处理单元包括: [0050] 第一解码子单元,用于当所述通信内容为所述移动终端接收到的音频信号时,使用所述安全虚拟内核对所述音频信号进行解码; 和 [0051] 第一解密子单元,用于利用安全虚拟内核对解码后的音频信号进行解密处理,得到待播放音频信号; 和 [0052] 输出单元具体用于通过安全虚拟内核控制音频播放设备播放待播放音频信号。 [0053] 结合第二方面或第二方面的第一种至第二种可行的实现方式中的任一种,在第三种可行的实现方式中,所述无线通信连接需要调用的外设包括录像设备,所述通信 内容包括录制的视频信号; [0054] 处理单元包括: [0055] 第二加密子单元,用于当通信内容为视频录制设备录制的视频信号时,通过安全虚拟内核对录制的视频信号进行加密处理; 和 [0056] 第二编码子单元,用于使用安全虚拟内核对加密处理后的视频信号进行编码,得到待发送的视频信号; 和 [0057] 输出单元具体用于通过安全虚拟内核控制移动终端向另一移动终端发送待发送视频信号。 [0058] 结合第二方面或第二方面的第一种至第三种可行的实现方式中的任一种,在第四种可行的实现方式中,所述无线通信连接需要调用的外设包括显示器,所述通信内容包括: 接收到的视频信号; [0059] 处理单元包括: [0060] 第二解码子单元,用于当通信内容为移动终端接收到的视频信号时,使用安全虚拟内核对接收到的视频信号进行解码; 和 [0061] 第二解密子单元,用于利用安全虚拟内核对解码后的视频信号进行解密处理,得到待播放视频信号; 和 [0062] 输出单元具体用于通过安全虚拟内核控制显示器播放待播放视频信号。 [0063] 结合第二方面或第二方面的第一种至第四种可行的实现方式中的任一种,在第五种可行的实现方式中,所述移动终端还包括: [0064] 第二设置单元,用于通过设置禁止公共虚拟内核中的程序访问与无线通信连接相关的中断信息。 [0065] 本发明实施例中,当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止程序在 普通虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 然后通过安全虚拟内核输出经过预设的基于策略的处理得到的通信内容,从而可以防止操作系统和运行在普通虚拟内核中的程序获得未经处理的通信内容,并且操作 还可以防止系统通过共享内存或相关外设窃听通信内容,提高移动终端的通信安全性。 附图说明 [0066]为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简要说明。 显然,以下描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有做出创造性劳动的情况下,仍然可以从这些附图中获得其他附图。 [0067] 图1为本发明移动终端安全通信方法一个实施例的流程示意图; [0068] 图2为本发明移动终端安全通信方法另一实施例的流程示意图; [0069] 图3为本发明移动终端安全通信方法又一实施例的流程示意图; [0070] 图4为本发明移动终端一个实施例的结构示意图; [0071] 图5为本发明移动终端另一实施例的结构示意图; [0072] 图6为本发明移动终端又一实施例的结构示意图; 和 [0073] 图7为本发明移动终端又一实施例的结构示意图。 详细说明 [0074] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 显然,所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0075] 下面结合附图对本发明实施例提供的一种移动终端的安全通信方法及移动终端进行详细说明。 在本发明实施例中,移动终端包括但不限于手机、个人电脑、笔记本电脑等可用于通信的终端。 [0076] 参见图1,图1为本发明移动终端安全通信方法实施例的流程示意图。 如图1所示,在本实施例中,安全通信方法包括以下步骤。 [0077] 小号 101 . 当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问共享 安全虚拟内核和公共虚拟内核之间的内存,以及访问需要为无线通信连接调用的外设。 [0078] 本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0079] 具体实施中,移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0080]在一种可行的实施方式中,移动终端可以是采用ARM(高级精简指令集计算机)处理器的基于TrustZone技术的移动终端。 [0081] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0082] 在一些可行的实施方式中,在本发明实施例中,当移动终端与另一移动终端之间还可以进行短信通信或邮件通信时,通过设置禁止公共虚拟内核中的程序访问。 访问安全虚拟内核和普通虚拟内核之间的共享内存,评估短信通信或邮件通信需要调用的外设。 短信通信或邮件通信需要调用的外设可以包括按键、键盘、平板电脑、显示器中的一种或多种。 [0083] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进行拨号操作时,或者当检测到移动终端登录到实时通信客户端时,可以认为移动终端之间建立了无线通信连接。 和另一个移动终端。 [0084] 在一些可行的实施方式中,可以通过检测与无线通信连接相关的一些中断信号,确定移动终端与另一移动终端建立无线通信连接。 例如,当另一移动终端来电时,应用处理器接收基带处理器发送的来电信息中断请求。 [0085] 可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的其他移动终端满足移动终端设置的安全条件,例如,无线通信连接为a 移动终端与通讯录中的好友之间的无线通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0086] 在一些可行的实施方式中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 例如,当基带系统检测到任何来电信号或检测到通讯录中好友的来电信号时,向应用处理器发送来电信息中断请求。 由于通过预先设置禁止普通虚拟内核中的程序访问来电信息中断请求,应用处理器在接收到来电信息中断请求后,通过安全虚拟内核处理来电信息中断请求。 [0087] 可选地,当无线通信连接涉及语音通话时(如普通电话、网络电话、实时通信客户端发起的语音会话),需要调用的外设至少包括: 录音装置及录音播放装置。 在具体实现中,录音设备和音频播放设备可以为同一设备,例如移动终端的麦克风。 [0088]可选地,当无线通信连接涉及视频通话时,需要通话的外设至少包括视频录制设备、录音设备、音频播放设备和显示器,例如摄像头、麦克风、 以及移动终端的显示器。 [0089] 在一些可行的实施方式中,移动终端可以通过GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息为 只能在安全虚拟内核中访问。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0090] 在一些可行的实施方式中,移动终端通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域或非安全内存区域。 -secure memory areas,TZASC可以禁止运行在common virtual kernel中的程序访问secure memory area。 [0091] 在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0092] 小号 102 . 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理。 [0093] 可选的,无线通信连接对应的通信内容包括移动终端要发送的通信内容和移动终端接收的通信内容。 [0094] 可选的,对于待发送的通信内容,预设的基于策略的处理可以包括加密、模数转换、编码、调制等中的一种或多种。 对于接收到的通信内容,预设的基于策略的处理可以包括解密、解调、解码、数模转换等中的一种或多种。 预设策略处理是通过移动终端的安全虚拟内核进行的,普通虚拟内核中的程序无法访问预设策略处理前获取的通信内容。 [0095] 在具体实现中,由于运行在普通虚拟内核中的操作系统代码量较大,因此存在的安全漏洞数量较多。 由于在安全的虚拟内核中运行的模块中的代码量很小,因此可以很容易地验证安全性。 通过安全虚拟内核对通信内容进行预设的策略处理,可以避免运行在普通虚拟内核中的操作系统获取进行预设策略处理前获得的通信内容,操作系统 可以防止窃听通信内容。 [0096] 小号 103 . 移动终端通过安全虚拟内核输出经过预设策略处理得到的通信内容。 [0097]具体实施中,移动终端在对移动终端要发送的通信内容进行预设的策略处理后,可以通过射频模块或无线网络连接模块发送该要发送的通信内容。 . 可以通过移动终端的射频模块发送电话或短信的通信内容; 可以通过无线网络连接模块发送邮件、网络语音通话、视频通话等通信内容。 在本发明实施例中,网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0098] 在对移动终端接收到的通信内容进行预设的基于策略的处理后,移动终端可以输出接收到的通信内容。 可选的,如果接收到的通信内容为语音,则可以通过音频播放设备(例如麦克风)输出接收到的通信内容; 如果接收到的通讯内容为视频,则可以通过显示器和音频播放设备输出接收到的通讯内容。 或者,如果接收到的通信内容为文本或图片,则可以通过显示器输出接收到的通信内容。 [0099] 本发明实施例中,当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,该移动终端通过设置的方式禁止程序在 普通虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 然后通过安全虚拟内核输出经过预设的基于策略的处理得到的通信内容,从而可以防止操作系统和运行在普通虚拟内核中的程序获得未经处理的通信内容,并且操作 还可以防止系统通过共享内存或相关外设窃听通信内容,提高移动终端的通信安全性。 [0100] 参见图2,图2为本发明移动终端安全通信方法另一实施例的流程示意图。 如图2所示,在本实施例中,安全通信方法包括以下步骤。 [0101] 小号 201 . 移动终端通过设置禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0102] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0103] 在一些可行的实施方式中,移动终端除了满足预设安全处理触发条件的与无线通信连接相关的中断信息/Elation外,还可以通过设置的方式禁止公共虚拟内核中的程序访问某些 与特定类型的无线通信连接相关的中断信号,例如短消息或邮件。 [0104]可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的另一移动终端满足移动终端设置的安全条件,例如,无线通信连接是无线的。 移动终端与通讯录中的好友之间的通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0105] 在具体实施中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 当移动终端接收到满足预设安全处理触发条件的与无线通信连接相关的中断信息时,移动终端将中断信息交由安全虚拟内核处理。 [0106] 在一些可行的实施方式中,移动终端可以通过GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息为 只能在安全虚拟内核中访问。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0107] 小号 202 . 当移动终端与另一移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问共享 安全虚拟内核和公共虚拟内核之间的内存,以及访问需要为无线通信连接调用的外设。 [0108] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进行拨号操作时,或者当检测到移动终端进入拨号界面时,可以认为移动终端与另一移动终端建立了电话连接。 [0109] 在一些可行的实施方式中,可以通过检测与无线通信连接相关的一些中断信号,确定移动终端与另一移动终端建立无线通信连接。 例如,当另一移动终端来电时,移动终端的应用处理器接收基带处理器发送的来电信息中断请求。 [0110] 本实施例以无线通信连接为语音连接为例进行说明。 语音连接包括电话连接或网络语音连接,语音连接需要调用的外设至少包括录音设备和音频播放设备。 在具体实现中,录音设备和音频播放设备可以为同一设备,例如移动终端的麦克风。 [0111]本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0112] 具体实施中,移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0113] 在一种可行的实施方式中,移动终端可以是采用ARM处理器的基于TrustZone技术的移动终端。 [0114] 在一些可行的实施方式中,移动终端通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域或非安全内存区域。 -secure memory areas,TZASC可以禁止运行在common virtual kernel中的程序访问secure memory area。 [0115] 在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0116] 小号 203 . 当无线通信连接对应的通信内容为录音设备录制的音频信号时,移动终端通过安全虚拟内核对录制的音频信号进行加密处理。 [0117] 在本发明实施例中,当无线通信连接为语音连接时,无线通信连接对应的通信内容包括移动终端录制的音频信号和移动终端接收的音频信号。 移动终端录制的音频信号是本移动终端用户在通话过程中要传达给另一移动终端用户的通话内容,移动终端接收到的音频信号是本移动终端用户要传达给另一移动终端用户的通话内容。 另一移动终端的用户在通话过程中与移动终端的用户通话。 具体地,录制的音频信号由移动终端的录音设备(例如麦克风)录制。 安全虚拟内核在从录音设备中获取到录制的音频信号后,可以对录制的音频信号进行加密处理,以防止移动通信链路受到窃听攻击时通话内容泄露。 [0118] 小号 204 . 移动终端通过安全虚拟内核对加密处理得到的音频信号进行编码,得到待发送的音频信号。 [0119] 在一些可行的实施方式中,当无线通信连接为电话连接时,利用安全虚拟内核对加密处理得到的音频信号进行编码可以包括:利用安全虚拟内核指示基带处理器。 移动终端对加密处理后的音频信号进行模数转换、语音编码、信道编码、物理层加密调制。 可选地,为了提高通话质量,还可以指示基带处理器对录制的音频信号进行交织、均衡、滤波等其他处理。 [0120]在一些可行的实施方式中,当所述无线通信连接为网络语音连接时,所述利用安全虚拟内核对加密处理得到的音频信号进行编码具体可以包括: 利用硬件资源或者软件资源进行 对加密处理得到的音频信号进行安全虚拟内核的构建、模数转换、语音编码、信道编码、物理层加密。 可选地,为了提高网络语音通话质量,还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0121] 小号 205 . 通过安全虚拟内核控制移动终端向另一移动终端发送待发送的音频信号。 [0122] 在一些可行的实施方式中,当无线通信连接为电话连接时,通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号可以包括:控制通过使用 安全虚拟内核,移动终端的射频模块,用于将待发送的音频信号发送给另一移动终端。 [0123] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号可以包括: 利用安全虚拟内核,移动终端的无线网络连接模块(例如Wi-Fi模块)将待发送的音频信号发送至另一移动终端。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 安全虚拟内核在获取到待发送音频信号后,可以将待发送音频信号发送给普通虚拟内核,并指示普通虚拟内核将待发送音频信号发送给其他虚拟内核。 移动终端通过使用无线网络连接模块。 [0124] 小号 206 . 当无线通信连接对应的通信内容为移动终端接收到的音频信号时,移动终端通过安全虚拟内核对音频信号进行解码。 [0125] 在一些可行的实施方式中,当无线通信连接为电话连接时,移动终端通过射频模块接收另一移动终端通过手机网络发送的音频信号。 此时,通过安全虚拟内核对音频信号进行解码可以包括:通过安全虚拟内核指示基带处理器进行解调、声道解码、物理层解密、语音解码、数字解码等处理。 对接收到的音频信号进行模拟转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0126] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,移动终端通过无线网络连接模块接收另一移动终端通过互联网发送的音频信号。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 普通虚拟内核控制无线网络连接模块接收另一移动终端发送的音频信号,并将接收到的音频信号传输给安全虚拟内核进行处理。 此时,利用安全虚拟内核对音频信号进行解码可以包括:利用安全虚拟内核对接收到的音频信号进行声道解码、物理层解密、语音解码和数模转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0127] 小号 207. 移动终端通过安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号。 [0128] 在一些可行的实施方式中,另一移动终端在对接收到的音频信号进行编码发送之前,首先对接收到的音频信号进行上层加密,以防止移动通信链路受到窃听攻击时通话内容泄露。 移动终端接收上层加密处理后的音频信号。 移动终端在对音频信号进行解码后,还需要对音频信号进行解密处理。 [0129] 小号 208 . 移动终端通过安全虚拟内核控制音频播放设备播放待播放的音频信号。 [0130] 安全虚拟内核对接收到的音频信号进行一系列处理后,安全虚拟内核可以控制移动终端的音频播放设备播放待播放的音频信号。 移动终端的音频播放设备可以是麦克风。 [0131] 本发明实施例中,当一个移动终端与另一个移动终端之间建立语音连接,并且该语音连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共节目。 虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问相关的外设,如录音设备或音频播放设备; 通过安全虚拟内核对移动终端录制的音频信号和移动终端接收的音频信号进行处理; 然后使用安全虚拟内核输出处理后的通信内容,可以防止操作系统和运行在普通虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听通信内容 通过共享内存或相关外设读取内容,提高了移动终端的通信安全性。 [0132] 参见图3,图3为本发明移动终端安全通信方法的又一实施例的流程示意图。 如图3所示,在本实施例中,安全通信方法包括以下步骤。 [0133] 小号 301 . 移动终端通过设置禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0134] 在具体实现中,对于S的具体实现 301 ,参考步骤S中描述的实现 201 在图2所示的实施例中,在此不再赘述。 [0135] 小号 302 . 当移动终端与另一移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问共享 安全虚拟内核和公共虚拟内核之间的内存,以及访问需要为无线通信连接调用的外设。 [0136] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进入网络电话程序画面,或者当检测到移动终端选择了实时通信客户端的视频通话选项时,可以认为是视频通话连接。 在移动终端和另一个移动终端之间建立。 [0137]在一些可行的实施方式中,可以通过检测一些与网络语音连接相关的中断信号,确定移动终端与另一移动终端之间建立了电话连接。 例如,当另一移动终端发送视频通话连接请求时,应用处理器检测到视频通话连接中断请求。 [0138] 本实施例以无线通信连接为视频通话连接为例进行说明。 视频通话连接需要调用的外设包括视频录制设备、录音设备、音频播放设备和显示器。 在具体实现中,视频录制设备可以是移动终端的摄像头,录音设备和音频播放设备可以是同一设备,例如移动终端的麦克风。 [0139] 本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0140] 具体实施中,移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0141] 在一种可行的实施方式中,移动终端可以是采用ARM处理器的基于TrustZone技术的移动终端。 [0142] 在一些可行的实施方式中,移动终端可以通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域,或者 非安全内存区,TZASC可以禁止公共虚拟内核中运行的程序访问安全内存区。 [0143] 在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0144] 小号 303 . 当无线通信连接对应的通信内容为移动终端录制的音视频信号时,移动终端通过安全虚拟内核对录制的音视频信号进行加密处理。 [0145] 在本发明实施例中,当无线通信连接为视频通话连接时,无线通信连接对应的通信内容包括移动终端录制的音视频信号和移动终端接收的音视频信号。 移动终端录制的音视频信号包括移动终端的录像设备录制的视频信号和移动终端的录音设备录制的音频信号。 [0146] 在移动终端与另一移动终端进行视频通话过程中,移动终端通过安全虚拟内核从录像设备和录音设备获取录制的音视频信号后,可以进行加密处理 在录制的音频和视频信号上,以防止在对移动通信链路进行窃听攻击时泄露通话内容。 [0147] 小号 304. 移动终端通过安全虚拟内核对加密处理后的音视频信号进行编码,得到待发送的音视频信号。 [0148] 在一些可行的实施方式中,所述利用安全虚拟内核对加密处理后的音视频信号进行编码,可以包括: 利用安全虚拟内核对加密后的视频信号进行编码和物理层加密,并进行处理 利用安全虚拟内核对加密后的音频信号进行模数转换、语音编码、信道编码、物理层加密等。 视频信号的编码标准可以根据视频通话连接的分辨率要求或压缩率要求来选择,例如H.261、H.262、H.263、H.264、MPEG-2或MPEG -4。 本发明对此不作限制。 可选地,为了提高视频通话质量,还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0149] 小号 305 . 通过安全虚拟内核控制移动终端向其他移动终端发送待发送的音视频信号。 [0150] 在一些可行的实施方式中,为了节省移动终端用户的开销,通过移动终端的无线网络连接模块将待发送的音视频信号发送给其他移动终端。 [0151] 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 此时,安全虚拟内核可以将待发送的音视频信号发送至普通虚拟内核,并指示普通虚拟内核将待发送的音视频信号发送至另一移动终端。 使用无线网络连接模块和互联网。 无线网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0152] 小号 306 . 当无线通信连接对应的通信内容为移动终端接收到的音视频信号时,移动终端通过安全虚拟内核对接收到的音视频信号进行解码。 [0153] 在一些可行的实施方式中,为了节省移动终端用户的开销,移动终端通过无线网络连接模块接收另一移动终端发送的音视频信号。 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 此时,普通虚拟内核控制无线网络连接模块接收其他移动终端发送的音视频信号,并将接收到的音视频信号传输给安全虚拟内核进行处理。 接收到的音频和视频信号可以包括视频信号和音频信号。 [0154] 在一种可行的实施方式中,利用安全虚拟内核对接收到的音视频信号进行解码可以包括: 利用安全虚拟内核对接收到的视频信号进行解码具体如下: 对视频信号进行物理层解密和视频解码。 在接收到的音频和视频信号中; 所述安全虚拟内核对接收到的音频信号进行解码具体为:对接收到的音视频信号中的音频信号进行物理层解密、信道解码、语音解码、数模转换等处理。 . 视频信号的解码标准可以包括H.261、H.262、H.263、H.264、MPEG-2、MPEG-4等,具体根据视频播放时选择的编码标准确定。 被编码。 可选地,为了提高视频通话质量,还可以对接收到的音视频信号中的音频信号进行均衡、声道分离、解交织等其他处理。 [0155]在具体实现中,移动终端可以通过安全虚拟内核分别对接收到的音频信号和视频信号进行解码,得到解码后的音频信号和解码后的视频信号。 [0156] 小号 307 . 移动终端通过安全虚拟内核对解码后的音视频信号进行解密处理,得到待播放的音视频信号。 [0157] 在一些可行的实施方式中,在对移动终端接收到的音视频信号进行编码压缩发送之前,另一移动终端首先对接收到的音视频信号进行上层加密,以防止窃听攻击时通话内容泄露 在移动通信链路上。 移动终端接收经过上层加密处理后的音视频信号。 在使用安全虚拟内核对音视频信号进行解码后,移动终端还需要使用安全虚拟内核对音视频信号进行解密处理。 [0158] 在具体实现中,移动终端可以通过安全虚拟内核分别对解码后的音频信号和解码后的视频信号进行解密处理,得到待播放的音频信号和待播放的视频。 信号。 [0159] 小号 308 . 移动终端通过安全虚拟内核控制音频播放设备和显示器播放待播放的音视频信号。 [0160] 安全虚拟内核对接收到的音视频信号进行一系列处理得到待播放的音视频信号后,安全虚拟内核可以控制移动终端的音频播放设备和显示器进行播放。 播放待播放的音视频信号。 待播放音视频信号中的待播放音频信号可以通过移动终端的音频播放设备(例如麦克风)进行播放,待播放视频信号在 可以通过移动终端的显示器播放待播放的音视频信号。 [0161] 本发明实施例中,当一个移动终端与另一个移动终端之间建立视频通话连接,并且该视频通话连接满足预设的安全处理触发条件时,移动终端通过设置禁止节目在 通用虚拟内核访问安全虚拟内核和通用虚拟内核之间的共享内存,访问相关的外围设备,如视频录制设备、录音设备、音频播放设备或显示器; 利用安全虚拟内核对移动终端录制的音视频信号和移动终端接收的音视频信号进行处理; 然后使用安全虚拟内核输出处理后的通信内容,可以防止操作系统和运行在普通虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听通信内容 通过共享内存或相关外设读取内容,提高了移动终端的通信安全性。 [0162] 参见图4,图4为本发明移动终端一个实施例的结构示意图。 如图4所示,本实施例中,移动终端包括第一设置单元 401 , 一个处理单元 402 , 和一个输出单元 403 . [0163] 第一设定单位 401 用于当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核和公共虚拟内核之间的共享内存以及访问需要为无线通信连接调用的外设。 [0164]本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0165] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0166] 在一些可行的实施方式中,在本发明实施例中,当移动终端与另一移动终端之间还可以进行短信通信或邮件通信时,通过设置禁止公共虚拟内核中的程序访问。 访问安全虚拟内核和普通虚拟内核之间的共享内存,评估短信通信或邮件通信需要调用的外设。 短信通信或邮件通信需要调用的外设可以包括按键、键盘、平板电脑、显示器中的一种或多种。 [0167] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进行拨号操作时,或者当检测到移动终端登录到实时通信客户端时,可以认为移动终端之间建立了无线通信连接。 和另一个移动终端。 [0168] 在一些可行的实施方式中,可以通过检测与无线通信连接相关的一些中断信号,确定移动终端与另一移动终端建立无线通信连接。 例如,当另一移动终端来电时,应用处理器接收基带处理器发送的来电信息中断请求。 [0169] 可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的其他移动终端满足移动终端设置的安全条件,例如,无线通信连接为a 移动终端与通讯录中的好友之间的无线通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0170] 在一些可行的实施方式中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 例如,当基带系统检测到任何来电信号或检测到通讯录中好友的来电信号时,向应用处理器发送来电信息中断请求。 由于通过预先设置禁止普通虚拟内核中的程序访问来电信息中断请求,应用处理器在接收到来电信息中断请求后,通过安全虚拟内核处理来电信息中断请求。 [0171]参见图5,该移动终端可以是采用ARM处理器的基于TrustZone技术的移动终端。 移动终端的片上系统(SoC)集成了CPU、直接存储器存取(DMA)、安全随机存取存储器(RAM)、安全启动只读存储器(ROM)、中断控制器( GIC或TZIC)、TZASC、TZPC、动态存储控制器(DMC)、动态随机存取存储器(DRAM)等。 [0172] SoC 中的组件通过使用高级可扩展接口 (AXI) 总线连接。 安全RAM和安全ROM分别通过软件或硬件机制隔离,用于存储运行在安全虚拟内核中的模块。 TZASC被配置为对共享内存(即DRAM)的安全属性进行分类,可以被配置为将DRAM的一部分设置为安全内存区域,而将DRAM的其余部分设置为非安全内存区域 内存区域。 当普通虚拟内核发起对安全内存区域的访问请求时,该访问请求被拒绝。 SoC通过TZPC配置外设的安全属性,通过AXI-to-APB桥与外设进行通信。 AXI-to-APB桥可以感知当前被事务访问的外设的安全属性,并且当公共虚拟内核的事务访问安全外设时,AXI-to-APB拒绝访问。 SoC可以通过使用GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息仅在安全虚拟机中被访问 核心。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0173] 在一些可行的实施方式中,当移动终端为手机时,移动终端包括应用处理器和基带处理器,应用处理器包括安全虚拟内核S和通用虚拟内核NS,安全虚拟内核和通用虚拟内核 虚拟内核共享移动终端的CPU、内存、外设和总线。 禁止普通虚拟内核中的程序访问安全虚拟内核的硬件资源。 移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0174] 可选地,当无线通信连接涉及语音通话时(如普通电话、网络电话、或其他通过实时通信客户端发起的语音会话),需要调用的外设至少包括 录音装置及录音播放装置。 在具体实现中,录音设备和音频播放设备可以为同一设备,例如移动终端的麦克风。 [0175] 可选地,当无线通信连接涉及视频通话时,需要通话的外设至少包括视频录制设备、录音设备、音频播放设备和显示器,例如摄像头、麦克风、 以及移动终端的显示器。 [0176] 在一些可行的实施方式中,移动终端通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域或非安全内存区域。 -secure memory areas,TZASC可以禁止运行在common virtual kernel中的程序访问secure memory area。 [0177]在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0178] 处理单元 402 用于通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理。 [0179] 可选的,无线通信连接对应的通信内容包括移动终端要发送的通信内容和移动终端接收的通信内容。 [0180] 可选的,对于待发送的通信内容,预设的基于策略的处理可以包括加密、模数转换、编码、调制等中的一种或多种。 对于接收到的通信内容,预设的基于策略的处理可以包括解密、解调、解码、数模转换等中的一种或多种。 预设策略处理是通过移动终端的安全虚拟内核进行的,普通虚拟内核中的程序无法访问预设策略处理前获取的通信内容。 [0181] 在具体实现中,由于运行在普通虚拟内核中的操作系统代码量较大,因此存在的安全漏洞数量较多。 由于在安全的虚拟内核中运行的模块中的代码量很小,因此可以很容易地验证安全性。 通过安全虚拟内核或基带处理器对通信内容进行预设的策略处理,可以避免运行在普通虚拟内核中的操作系统获取进行预设策略处理前的通信内容, 可以防止操作系统窃听通信内容。 [0182] 输出单元 403 用于通过安全虚拟内核输出经过预设策略处理得到的通信内容。 [0183] 具体实施中,移动终端在对移动终端要发送的通信内容进行预设的策略处理后,可以通过射频模块或无线网络连接模块发送该要发送的通信内容。 . 可以通过移动终端的射频模块发送电话或短信的通信内容; 可以通过网络连接模块发送邮件、网络语音通话、视频通话等通信内容。 在本发明实施例中,网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0184] 在对移动终端接收到的通信内容进行预设的基于策略的处理后,移动终端可以输出接收到的通信内容。 可选的,如果接收到的通信内容为语音,则可以通过音频播放设备(例如麦克风)输出接收到的通信内容; 如果接收到的通讯内容为视频,则可以通过显示器和音频播放设备输出接收到的通讯内容。 或者,如果接收到的通信内容为文本或图片,则可以通过显示器输出接收到的通信内容。 [0185]本发明实施例中,当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,该移动终端通过设置的方式禁止程序在 普通虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 然后通过安全虚拟内核输出经过预设的基于策略的处理得到的通信内容,从而可以防止操作系统和运行在普通虚拟内核中的程序获得未经处理的通信内容,并且操作 还可以防止系统通过共享内存或相关外设窃听通信内容,提高移动终端的通信安全性。 [0186] 参见图6,图6为本发明移动终端又一实施例的结构示意图。 如图6所示,本实施例中,移动终端包括第一设置单元 601 , 一个处理单元 602 , 一个输出单元 603 , 和第二个设定单位 604 . [0187] 第二设定单位 604 用于通过设置禁止普通虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0188] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0189] 在一些可行的实施方式中,移动终端除了满足预设的安全处理触发条件的与无线通信连接相关的中断信息外,还可以通过设置的方式,禁止公共虚拟内核中的程序访问一些中断信号。 与特定类型的无线通信连接有关,例如短消息或邮件。 [0190] 可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的另一移动终端满足移动终端设置的安全条件,例如,无线通信连接是无线的。 移动终端与通讯录中的好友之间的通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0191] 在具体实施中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 当移动终端接收到满足预设安全处理触发条件的与无线通信连接相关的中断信息时,移动终端将中断信息交由安全虚拟内核处理。 [0192] 在一些可行的实施方式中,第二设置单元 604可以通过GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息仅在安全虚拟内核中被访问。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0193] 第一设定单位 601 用于当移动终端与另一移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核和普通虚拟内核之间的共享内存,以及访问无线通信连接需要调用的外设。 [0194] 在一些可行的实现中,第一个设置单元 601 可以执行第一设置单元执行的实现 401 如图4所示实施例所述。在本实施例中,无线通信连接为语音连接,包括电话连接或网络语音连接。 此时,无线通信连接需要调用的外设包括录音设备和音频播放设备,第一设置单元 601 可以具体用于通过设置禁止公共虚拟内核中的程序访问安全虚拟内核和公共虚拟内核之间的共享内存以及访问移动设备的录音设备和音频播放设备。 终端。 判断移动终端与其他移动终端建立语音连接的具体实现参见步骤S的相关描述 202 在图2所示的实施例中。 [0195] 在一些可行的实现中,处理单元 602 可以执行由处理单元执行的实现 402 描述在图4所示的实施例中。在该实施例中,处理单元 602 可能包括第一加密子单元 6021 , 第一个编码亚单位 6022 , 第一个解码子单元 6023 , 和第一个解密子单元 6024 . [0196] 第一加密子单元 6021 用于当通信内容为录音设备录制的音频信号时,通过安全虚拟内核对录制的音频信号进行加密处理。 [0197] 在本发明实施例中,当无线通信连接为语音连接时,无线通信连接对应的通信内容包括移动终端录制的音频信号和移动终端接收的音频信号。 移动终端录制的音频信号是本移动终端用户在通话过程中要传达给另一移动终端用户的通话内容,移动终端接收到的音频信号是本移动终端用户要传达给另一移动终端用户的通话内容。 另一移动终端的用户在通话过程中与移动终端的用户通话。 [0198] 具体地,录制的音频信号由移动终端的录音设备(例如麦克风)录制。 安全虚拟内核从录音设备获取录制的音频信号后,可以通过第一加密子单元对录制的音频信号进行加密处理 6021 ,以防止在对移动通信链路进行窃听攻击时泄露通话内容。 [0199] 第一编码亚单位 6022 用于通过安全虚拟内核对加密处理得到的音频信号进行编码,得到待发送的音频信号。 [0200]在一些可行的实施方式中,当无线通信连接为电话连接时,利用安全虚拟内核对加密处理得到的音频信号进行编码可以包括:利用安全虚拟内核指示基带处理器: 移动终端对加密处理后的音频信号进行模数转换、语音编码、信道编码、物理层加密调制。 可选地,为了提高通话质量,还可以指示基带处理器对录制的音频信号进行交织、均衡、滤波等其他处理。 [0201] 在一些可行的实施方式中,当所述无线通信连接为网络语音连接时,所述利用安全虚拟内核对加密处理得到的音频信号进行编码具体可以包括: 利用硬件资源或者软件资源进行 对加密处理得到的音频信号进行安全虚拟内核的构建、模数转换、语音编码、信道编码、物理层加密。 可选地,为了提高网络语音通话质量,还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0202] 第一解码子单元 6023 用于当通信内容为移动终端接收到的音频信号时,通过安全虚拟内核对音频信号进行解码。 [0203] 在一些可行的实施方式中,当无线通信连接为电话连接时,移动终端通过射频模块接收另一移动终端通过手机网络发送的音频信号。 此时,通过安全虚拟内核对音频信号进行解码可以包括:通过安全虚拟内核指示基带处理器进行解调、声道解码、物理层解密、语音解码、数字解码等处理。 对接收到的音频信号进行模拟转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0204] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,移动终端通过无线网络连接模块接收其他移动终端通过互联网发送的音频信号。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 普通虚拟内核控制无线网络连接模块接收其他移动终端发送的音频信号,并将接收到的音频信号传输给安全虚拟内核进行处理。 此时,利用安全虚拟内核对音频信号进行解码可以包括:利用安全虚拟内核对接收到的音频信号进行声道解码、物理层解密、语音解码和数模转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0205] 第一解密子单元 6024 用于通过安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号。 [0206] 在一些可行的实施方式中,另一移动终端在对接收到的音频信号进行编码发送之前,首先对接收到的音频信号进行上层加密,以防止移动通信链路受到窃听攻击时通话内容泄露。 移动终端接收上层加密处理后的音频信号。 解码音频信号后,第一个解密子单元 6024 对音频信号进行解密处理。 [0207] 在一些可行的实现中,输出单元 603 可以执行由输出单元执行的实现 403在图4所示的实施例中描述。在本发明实施例中,输出单元 603 还可以具体用于: 通过安全虚拟内核控制移动终端向其他移动终端发送待发送音频信号。 或者,通过安全虚拟内核控制音频播放设备播放待播放的音频信号。 [0208] 在一些可行的实施方式中,当无线通信连接为电话连接时,通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号可以包括:控制通过使用 安全虚拟内核,移动终端的射频模块,用于将待发送的音频信号发送给其他移动终端。 [0209] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,通过安全虚拟内核控制移动终端向其他移动终端发送待发送音频信号可以包括: 利用安全虚拟内核,移动终端的无线网络连接模块(例如Wi-Fi模块)将待发送的音频信号发送给其他移动终端。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 安全虚拟内核在获取到待发送音频信号后,可以将待发送音频信号发送给普通虚拟内核,并指示普通虚拟内核将待发送音频信号发送给其他虚拟内核。 移动终端通过使用无线网络连接模块。 [0210] 安全虚拟内核对接收到的音频信号进行一系列处理后,安全虚拟内核可以控制移动终端的音频播放设备播放待播放的音频信号。 移动终端的音频播放设备可以是麦克风。 本发明实施例中,当一个移动终端与另一个移动终端之间建立语音连接,并且该语音连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共节目。 虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问相关的外设,如录音设备或音频播放设备; 利用移动终端的安全虚拟内核和基带处理器获取并处理音频信号; 然后将处理后的音频信号发送或输出给其他移动终端,可以防止操作系统和运行在公共虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听。 通过共享内存或相关外设获取通信内容,提高移动终端的通信安全性。 [0211] 参见图7,图7为本发明移动终端又一实施例的结构示意图。 如图7所示,本实施例中,移动终端包括第一设置单元 701 , 一个处理单元 702 , 一个输出单元 703 , 和第二个设定单位 704 . [0212] 第二设定单位 704 用于通过设置禁止普通虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0213] 在一些可行的实施方式中,第二设置单元 704 可以执行第二设置单元执行的实现 604 在图6所示的实施例中描述。 [0214] 第一设定单位 701用于当所述移动终端与另一移动终端之间建立无线通信连接,并且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核和公共虚拟内核之间的共享内存以及访问需要为无线通信连接调用的外设。 [0215] 在一些可行的实现中,第一个设置单元 701 可以执行第一设置单元执行的实现 401 如图4所示的实施例所述。在本实施例中,无线通信连接为视频通话连接,无线通信连接需要调用的外设包括视频录制设备、录音设备、音频播放设备 设备和显示器。 在这种情况下,第一个设置单元 701 可以具体用于通过设置禁止公共虚拟内核中的程序访问安全虚拟内核和公共虚拟内核之间的共享内存以及访问视频录制设备、音频录制设备、音频播放设备 , 以及移动终端的显示。 确定移动终端与其他移动终端建立视频通话连接的具体实现参见步骤S的相关描述 302 在图3所示的实施例中。 [0216] 在一些可行的实现中,处理单元 702 可以执行由处理单元执行的实现 402 描述在图4所示的实施例中。在该实施例中,处理单元 702 可能包括第一加密子单元 7021 , 第二个加密子单元 7022 , 第一个编码亚单位 7023 , 第二个编码亚基 7024 , 第一个解码子单元 7025 , 第二个解码子单元 7026 , 第一个解密子单元 7027 , 和第二个解密子单元 7028 . [0217] 第一加密子单元 7021 用于当通信内容为录音设备录制的音频信号时,通过安全虚拟内核对录制的音频信号进行加密处理。 [0218] 第二个加密子单元 7021 用于当通信内容为视频录制设备录制的视频信号时,通过安全虚拟内核对录制的视频信号进行加密处理。 [0219] 在本发明实施例中,当无线通信连接为视频通话连接时,无线通信连接对应的通信内容包括移动终端录制的音频信号、移动终端录制的视频信号、音频信号。 移动终端接收到的视频信号,以及移动终端接收到的视频信号。 [0220] 在移动终端与另一移动终端进行视频通话过程中,移动终端通过安全虚拟内核从视频录制设备和音频录制设备获取录制的音频信号和录制的视频信号后,可以执行 对录制的音频信号和录制的视频信号进行加密处理,以防止在移动通信链路被窃听攻击时泄露通话内容。 [0221] 在一种可行的实现方式中,可以通过第一加密子单元进行加密处理 7021 , 对移动终端录制的音视频信号中的音频信号进行加密处理, 采用第二加密子单元 7022 ,关于移动终端录制的音视频信号中的视频信号。 [0222] 第一编码亚单位 7023 用于通过安全虚拟内核对加密处理得到的音频信号进行编码,得到待发送的音频信号。 [0223] 第二编码亚基 7024用于通过安全虚拟内核对加密处理得到的视频信号进行编码,得到待发送的视频信号。 [0224] 在一些可行的实现中,第一个编码子单元 7023 可以具体用于对加密后的音频信号进行模数转换、语音编码、信道编码、物理层加密等处理。 可选地,为了提高视频通话质量,第一编码子单元 7023 还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0225] 在一些可行的实现中,第二个编码子单元 7024 可以具体用于对加密后的视频信号进行编码和物理层加密。 视频信号的编码标准可以根据视频通话连接的分辨率要求或压缩率要求来选择,例如H.261、H.262、H.263、H.264、MPEG-2或MPEG -4。 本发明对此不作限制。 [0226] 第一解码子单元 7025 用于当通信内容为移动终端接收到的音频信号时,通过安全虚拟内核对音频信号进行解码。 [0227] 第二解码子单元 7026 用于当通信内容为移动终端接收到的视频信号时,通过安全虚拟内核对接收到的视频信号进行解码。 [0228] 在一些可行的实施方式中,为了节省移动终端用户的开销,移动终端通过无线网络连接模块接收其他移动终端发送的音频信号和视频信号。 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 在这种情况下,普通虚拟内核控制无线网络连接模块接收其他移动终端发送的音频信号和视频信号,然后将接收到的音频信号和视频信号传输给安全虚拟内核用于 加工。 [0229] 在一个可行的实现中,第一个解码子单元 7025 可以具体用于对接收到的音频信号进行物理层解密、通道解码、语音解码、数模转换等处理。 可选地,为了提高视频通话质量,第一解码子单元 7025 还可以对接收到的音视频信号中的音频信号进行均衡、声道分离、解交织等其他处理。 [0230] 在一个可行的实现中,第二解码子单元 7026 可以具体用于对接收到的视频信号进行物理层解密和视频解码。 视频信号的解码标准可以包括H.261、H.262、H.263、H.264、MPEG-2、MPEG-4等,具体根据视频播放时选择的编码标准确定。 被编码。 [0231] 第一解密子单元 7027 用于通过安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号。 [0232] 第二解密子单元 7028 用于通过安全虚拟内核对解码后的视频信号进行解密处理,得到待播放的视频信号。 [0233]在一些可行的实施方式中,在对移动终端接收到的音频信号和视频信号进行编码压缩发送之前,另一移动终端首先对接收到的音频信号和视频信号进行上层加密以防止泄露。 对移动通信链路的窃听攻击期间的通话内容。 移动终端接收经过上层加密处理后的音频信号和视频信号。 在使用安全虚拟内核对音频信号和视频信号进行解码后,移动终端还需要使用安全虚拟内核对音频信号和视频信号进行解密处理。 [0234] 在一种可行的实现方式中,可以通过第一解密子单元进行解密处理 7027 , 对移动终端接收到的音频信号进行解密处理, 利用第二解密子单元 7028 ,关于移动终端接收到的视频信号。 [0235] 在一些可行的实现中,输出单元 703 可以执行由输出单元执行的实现 403 如图4所示的实施例中描述的。在本实施例中,无线通信连接为视频通话连接,输出单元 703 可以具体用于: 通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号和待发送视频信号。 或者,通过安全虚拟内核控制音频播放设备播放待播放的音频信号,通过安全虚拟内核控制显示器播放待播放的视频信号。 [0236] 在一些可行的实施方式中,为了节省移动终端用户的开销,可以通过移动终端的无线网络连接模块将待发送的音频信号和待发送的视频信号发送至另一移动终端。 . 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 此时,移动终端的安全虚拟内核可以将待发送的音频信号和待发送的视频信号发送给普通虚拟内核,并指示普通虚拟内核发送待发送的视频信号。 通过无线网络连接模块和互联网将音频信号和待发送的视频信号发送给其他移动终端。 无线网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0237] 安全虚拟内核对接收到的音频信号和视频信号进行一系列处理得到待播放的音频信号和待播放的视频信号后,安全虚拟内核就可以控制音频播放设备 移动终端的显示器,用于播放待播放的音频信号和待播放的视频信号。 待播放的音频信号可以通过移动终端的音频播放设备(例如麦克风)进行播放,待播放的视频信号可以通过移动终端的显示器进行播放。 [0238]本发明实施例中,当一个移动终端与另一个移动终端之间建立视频通话连接,并且该视频通话连接满足预设的安全处理触发条件时,移动终端通过设置禁止节目在 通用虚拟内核访问安全虚拟内核和通用虚拟内核之间的共享内存,访问相关的外围设备,如视频录制设备、录音设备、音频播放设备或显示器; 利用安全虚拟内核对移动终端录制的音视频信号和移动终端接收的音视频信号进行处理; 然后使用安全虚拟内核输出处理后的通信内容,可以防止操作系统和运行在普通虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听通信内容 通过共享内存或相关外设读取内容,提高了移动终端的通信安全性。 [0239] 需要说明的是,为便于描述,上述方法实施例均以一系列动作来表示。 然而,本领域的技术人员应该理解,本申请不限于所描述的动作顺序,因为根据本申请,一些步骤可以以其他顺序或同时执行。 本领域技术人员还应该理解,说明书中所描述的实施例仅为示例,所涉及的动作和模块并不一定是本申请所必须的。 [0240] 在上述实施例中,对各个实施例的描述都各有侧重。 一个实施例中没有详述的部分,可以参见其他实施例的相关描述。 [0241] 本领域普通技术人员可以理解,实施例中方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 存储介质可以包括闪存、只读存储器(ROM)、随机存取存储器(RAM)、磁盘和光盘。 [0242] 以上对本申请实施例提供的一种移动终端的安全通信方法及移动终端进行了详细描述。 本文通过具体的例子描述了本申请的原理和实现方式,以上对实施例的描述仅仅为了帮助理解本申请的方法和核心思想。 另外,本领域的普通技术人员可以根据本申请的思想,在具体实施方式和适用范围上对本申请作出变更和修改。 总之,本说明书的内容不应理解为对本申请的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106211144A(String), CN106211144B(String), EP3282735A1(String), EP3282735A4(String), IN201737039680A(String), IN426841B(String), KR101940164B1(String), KR1020170140344A(String), US10638311B2(String), US20180054732A1(String), WO2016173284A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.854 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.855 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106211144A(String), CN106211144B(String), EP3282735A1(String), EP3282735A4(String), IN201737039680A(String), IN426841B(String), KR101940164B1(String), KR1020170140344A(String), US10638311B2(String), US20180054732A1(String), WO2016173284A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.856 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10638311B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106211144A(String), CN106211144B(String), EP3282735A1(String), EP3282735A4(String), IN201737039680A(String), IN426841B(String), KR101940164B1(String), KR1020170140344A(String), US10638311B2(String), US20180054732A1(String), WO2016173284A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), CN106211144A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), CN106211144B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.882 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), EP3282735A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.890 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), EP3282735A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.897 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), IN201737039680A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.905 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), IN426841B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.915 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), KR101940164B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.926 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), KR1020170140344A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.935 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), US10638311B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.942 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), US20180054732A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.950 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270715(Integer), WO2016173284A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.958 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.959 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10638311B2(String), US10638311B2(String), 1588003200(Integer), 270715(Integer), 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.971 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.973 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.975 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185040(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.976 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185040(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.983 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.984 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.986 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185040(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.988 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185040(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.995 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.996 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.997 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.998 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:07.999 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.000 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.010 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.011 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.013 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185040(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.024 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.025 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10291756B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.027 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, receiver for a mobile terminal, receiver and camera assembly for a mobile terminal(String), 移动终端、移动终端的接收器、移动终端的接收器和摄像头组件(String), US10291756B2(String), The embodiments of the present disclosure provide a mobile terminal, including a housing, a display screen, a camera and a receiver. The display screen is mounted to the housing and has a first aperture. The camera is mounted in the housing and is aligned with the first aperture. The receiver is mounted between the display screen and the camera and transmits a sound signal through the first aperture. The received has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture. In the solution, as the camera is disposed below the receiver along the thickness direction of the mobile terminal, it is unnecessary to provide independent apertures for the camera and the receiver in the display screen.(String), 本发明实施例提供一种移动终端,包括外壳、显示屏、摄像头和接收器。 显示屏安装在外壳上并具有第一孔。 相机安装在外壳中并与第一光圈对齐。 接收器安装在显示屏和摄像头之间,通过第一孔传输声音信号。 接收器具有光信号通道,摄像头通过光信号通道和第一光圈获取外界光信号。 在该方案中,由于摄像头沿移动终端的厚度方向设置在接收器下方,因此无需在显示屏中为摄像头和接收器设置独立的开孔。(String), US15/867256(String), 1515513600(Integer), US10291756B2(String), 1557763200(Integer), 1557763200(Integer), 美国(String), 4(Integer), CN(String), 13(Integer), 12(Integer), CN101652980A | CN105991807A | CN106453722A | CN106453726A | CN106936954A | CN1914900A | CN204119279U | CN205610701U | US20100165182A1 | US20100315570A1 | US20130094126A1 | US20170019512A1(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.036 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185041(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.038 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.039 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\311ee4f724c84d459a91a01e5aa0fac0.png(String), 185041(Integer), 311ee4f724c84d459a91a01e5aa0fac0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.046 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.047 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.048 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, receiver for a mobile terminal, receiver and camera assembly for a mobile terminal(String), 移动终端、移动终端的接收器、移动终端的接收器和摄像头组件(String), US10291756B2(String), The embodiments of the present disclosure provide a mobile terminal, including a housing, a display screen, a camera and a receiver. The display screen is mounted to the housing and has a first aperture. The camera is mounted in the housing and is aligned with the first aperture. The receiver is mounted between the display screen and the camera and transmits a sound signal through the first aperture. The received has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture. In the solution, as the camera is disposed below the receiver along the thickness direction of the mobile terminal, it is unnecessary to provide independent apertures for the camera and the receiver in the display screen.(String), 本发明实施例提供一种移动终端,包括外壳、显示屏、摄像头和接收器。 显示屏安装在外壳上并具有第一孔。 相机安装在外壳中并与第一光圈对齐。 接收器安装在显示屏和摄像头之间,通过第一孔传输声音信号。 接收器具有光信号通道,摄像头通过光信号通道和第一光圈获取外界光信号。 在该方案中,由于摄像头沿移动终端的厚度方向设置在接收器下方,因此无需在显示屏中为摄像头和接收器设置独立的开孔。(String), US15/867256(String), 1515513600(Integer), US10291756B2(String), 1557763200(Integer), 1557763200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 13(Integer), 12(Integer), CN101652980A | CN105991807A | CN106453722A | CN106453726A | CN106936954A | CN1914900A | CN204119279U | CN205610701U | US20100165182A1 | US20100315570A1 | US20130094126A1 | US20170019512A1(String), \20230420\311ee4f724c84d459a91a01e5aa0fac0.png(String), 11(Integer), 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.059 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 1. A mobile terminal, comprising:a housing;a display screen mounted to the housing and having a first aperture;a camera mounted in the housing and being aligned with the first aperture;a receiver mounted between the display screen and the camera and configured to transmit a sound signal through the first aperture;wherein the receiver has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture.(String), 1.移动终端,包括:住房;显示屏安装于外壳并具有第一孔径;安装在外壳内并对准第一光圈的摄像头;接收器,安装在显示屏和摄像头之间,用于通过第一孔径传输声音信号;其中,接收器具有光信号通道,而相机通过光信号通道和第一光圈来获取外部光信号。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 2. The mobile terminal according to claim 1, wherein the receiver comprises a transparent diaphragm, and the transparent diaphragm is aligned with the first aperture.(String), 2.根据权利要求1所述的移动终端,其中接收器包括透明膜片,透明膜片对准第一孔径。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 3. The mobile terminal according to claim 2, wherein the receiver further comprises a permanent magnet, the permanent magnet is disposed at a side of the diaphragm adjacent to the camera, and the permanent magnet has a second aperture aligned with the camera.(String), 3.根据权利要求2所述的移动终端,其中接收器还包括永磁体,永磁体设置在膜片邻近摄像头的一侧,永磁体具有与摄像头对准的第二孔径。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 4. The mobile terminal according to claim 3, wherein the receiver further comprises a magnetically conductive sheet and a magnetically conductive plate, the magnetically conductive sheet and the magnetically conductive plate are disposed at two sides of the permanent magnet respectively, and the magnetically conductive sheet and the magnetically conductive plate are respectively provided with a third aperture and a fourth aperture aligned with the second aperture.(String), 4.根据权利要求3所述的移动终端,其中接收器还包括导磁片和导磁板,导磁片和导磁板分别设置在永磁体的两侧,导磁片和导磁板分别设有第三孔径和与第二孔径对齐的第四孔径。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 5. The mobile terminal according to claim 4, wherein the transparent diaphragm, the third aperture, the second aperture, and the fourth aperture form the light signal passage.(String), 5.根据权利要求4所述的移动终端,其中透明光阑、第三孔径、第二孔径及第四孔径形成光信号通道。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 6. The mobile terminal according to claim 4, wherein the magnetically conductive plate is U-shaped, the permanent magnet and the magnetically conductive sheet are disposed at a bottom of the magnetically conductive plate, extension portions at two sides of the magnetically conductive plate extend upwards to two sides of the permanent magnet and the magnetically conductive sheet.(String), 6.根据权利要求4所述的移动终端,其中导磁板呈U型,永磁体和导磁片设置在导磁板的底部,导磁板两侧的延伸部向上延伸至永磁体和导磁片的两侧导电片。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.060 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 7. The mobile terminal according to claim 1, wherein the mobile terminal further comprises a sensor assembly, the sensor assembly is mounted in the housing, and the sensor assembly emits and receives a signal through the light signal passage and the first aperture.(String), 7.根据权利要求1所述的移动终端,其中移动终端还包括传感器组件,传感器组件安装在壳体内,传感器组件通过光信号通道和第一孔径发射和接收信号。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 8. The mobile terminal according to claim 7, wherein the camera is provided with a step, a step surface of the step faces the display screen, and the sensor assembly is mounted onto the step.(String), 8.根据权利要求7所述的移动终端,其中摄像头设有台阶,台阶的台阶面朝向显示屏,传感器组件安装在台阶上。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 9. The mobile terminal according to claim 7, wherein the sensor assembly comprises a signal emitter and a signal receiver, and the signal emitter and the signal receiver are disposed at two sides of the camera respectively.(String), 9.根据权利要求7所述的移动终端,其中传感器组件包括信号发射器和信号接收器,信号发射器和信号接收器分别设置在摄像头的两侧。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 10. The mobile terminal according to claim 7, wherein the sensor assembly further comprises an ambient light sensor, and the ambient light sensor receives an ambient light signal through the light signal passage and the first aperture.(String), 10.根据权利要求7所述的移动终端,其中传感器组件还包括环境光传感器,环境光传感器通过光信号通道和第一孔径接收环境光信号。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185041(Integer), 11. The mobile terminal according to claim 1, wherein the first aperture is disposed at a top middle of the display screen.(String), 11.根据权利要求1所述的移动终端,其中第一光圈设置于显示屏幕的顶部中间。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.151 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.152 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185041(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The application claims priority to and benefits of Chinese Patent Application Serial No. 201710132219.0, filed with the State Intellectual Property Office of P. R. china on Mar. 7, 2017, the entire content of which is incorporated herein by reference. FIELD [0002]The present disclosure relates to a field of communication technology, and particularly to a mobile terminal, a receiver for a mobile terminal, and a receiver and camera assembly for a mobile terminal. BACKGROUND [0003]In a conventional mobile terminal (such as a smartphone), a receiver is mounted in the mobile terminal. An aperture is provided in a top of the receiver, and the receiver sends a sound wave outwardly through the aperture, so as to allow the mobile terminal to transmit a sound signal to a user. [0004]On the other hand, a camera is also mounted in the mobile terminal, and the camera has an aperture at a top as well, so as to enable the camera to acquire an external image through the aperture. [0005]However, in this kind of design solution, it is required to provide a plurality of apertures in a screen, so as to realize functions of the receiver and the camera. The plurality of the apertures needs to occupy a large area of the screen of the mobile terminal, which causes a low ratio of a display area to the screen. SUMMARY [0006]Embodiments of the present disclosure provide a mobile terminal, including a housing, a display screen, a camera and a receiver, in which: the display screen is mounted to the housing and has a first aperture; the camera is mounted in the housing and is aligned with the first aperture; the phone is mounted between the display screen and the camera and transmits a sound signal through the first aperture; the receiver has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture. [0007]Embodiments of the present disclosure further provide a receiver configured to be mounted in a mobile terminal, including a vibration section and a magnetic circuit section, the vibration section including a transparent diaphragm, a through hole being formed in the magnetic circuit section, the transparent diaphragm and the through hole forming a light signal passage. [0008]Embodiments of the present disclosure further provide a receiver and camera assembly configured to be mounted in a mobile terminal, including a receiver, a camera, the receiver having a light signal passage, the camera being aligned with the light signal passage. BRIEF DESCRIPTION OF THE DRAWINGS [0009]To describe the technical solutions in the embodiments of the present disclosure more clearly, the accompanying drawings required for describing the embodiments are briefly introduced in the following. Apparently, the accompanying drawings in the following description illustrate merely some embodiments of the present disclosure, and those ordinarily skilled in the art can also derive other drawings from these accompanying drawings without creative efforts. [0010]FIG. 1 is a schematic view of a mobile terminal provided in an embodiment of the present disclosure. [0011]FIG. 2 is an exploded view of a mobile terminal provided in an embodiment of the present disclosure. [0012]FIG. 3 is a schematic view of a cover plate provided in an embodiment of the present disclosure. [0013]FIG. 4 is a schematic view of a display screen provided in an embodiment of the present disclosure. [0014]FIG. 5 is a first schematic view of a camera provided in an embodiment of the present disclosure. [0015]FIG. 6 is a second schematic view of a camera provided in an embodiment of the present disclosure. [0016]FIG. 7 is a sectional view of a receiver provided in an embodiment of the present disclosure. [0017]FIG. 8 is a schematic view where a receiver, a camera and a sensor assembly are mounted to a circuit board in an embodiment of the present disclosure. [0018]FIG. 9 is a first sectional view of the mobile terminal in FIG. 1 taken along P-P direction. [0019]FIG. 10 is a second sectional view of the mobile terminal in FIG. 1 taken along P-P direction. [0020]FIG. 11 is a third sectional view of the mobile terminal in FIG. 1 taken along P-P direction. [0021]FIG. 12 is a schematic view of a receiver and camera assembly provided in an embodiment of the present disclosure. DETAILED DESCRIPTION [0022]The technical solutions of the embodiments of the present disclosure are clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are only a part instead of all the embodiments of the present disclosure. All of the other embodiments derived by those ordinarily skilled in the art without creative effort based on the embodiments in the present disclosure belong to a protection scope of the present disclosure. [0023]In the specification, it is to be understood that terms such as “central”, “longitudinal”, “lateral”, “length”, “width”, “thickness”, “upper”, “lower”, “front”, “rear”, “left”, “right”, “vertical”, “horizontal”, “top”, “bottom”, “inner”, “outer”, “clockwise” and “counterclockwise”, should be construed to refer to the orientation as then described or as shown in the drawings under discussion. These relative terms are for convenience of description and do not require that the present disclosure be constructed or operated in a particular orientation. In addition, terms such as “first” and “second” are used herein for purposes of description and are not intended to indicate or imply relative importance or significance. Thus, features limited by “first” and “second” are intended to indicate or imply including one or more than one these features. In the description of the present disclosure, the term “a plurality of” means two or more than two, unless specified otherwise. [0024]In the present disclosure, unless specified or limited otherwise, the terms “mounted”, “connected”, “joined”, “fixed” and the like are used broadly, and may be, for example, fixed connections, detachable connections, or integral connections; may also be mechanical or electrical connections; may also be direct connections or indirect connections via intervening structures; may also be inner communications of two elements. The above terms can be understood by those skilled in the art according to specific situations. [0025]In the description of the present disclosure, a structure in which a first feature is “on” a second feature may include an embodiment in which the first feature directly contacts the second feature, and may also include an embodiment in which an additional feature is formed between the first feature and the second feature so that the first feature does not directly contact the second feature, unless otherwise specified. Furthermore, a first feature “on”, “above”, or “on top of” a second feature may include an embodiment in which the first feature is right “on”, “above” or “on top of” the second feature, and may also include an embodiment in which the first feature is not right “on”, “above” or “on top of” the second feature, or just means that the first feature has a sea level elevation larger than the sea level elevation of the second feature. While first feature “beneath”, “below” or “on bottom of” a second feature may include an embodiment in which the first feature is right “beneath”, “below” or “on bottom of” the second feature, and may also include an embodiment in which the first feature is not right “beneath”, “below” or “on bottom of” the second feature, or just means that the first feature has a sea level elevation smaller than the sea level elevation of the second feature. [0026]The following disclosure provides many different embodiments or examples to realize different structures of the present disclosure. To simplify the disclosure of the present disclosure, components and configurations in particular examples are elaborated. Of course, they are illustrative, and are not intended to limit the present disclosure. Moreover, reference numbers and/or letters may be repeated in different examples of the present disclosure for the purpose of simplicity and clarity, which shall not be constructed to indicate the relationships among various embodiments and/or configurations. In addition, the present disclosure provides examples of various specific processes and materials, but applicability of other processes and/or utilization of other materials are conceivable for those skilled in the art. [0027]Referring to FIGS. 1 and 2, a mobile terminal 100 includes a cover plate 10, a display screen 20, a circuit board 30, a battery 40 and a housing 50. The cover plate 10 is mounted to the display screen 20 so as to cover the display screen 20. Referring to FIG. 3, the cover plate 10 has a first through hole 101 and a second through hole 102. The first through hole 101 and the second through hole 102 are disposed at two ends of the cover plate 10 respectively. The first through hole 101 can be configured to enable a receiver in the mobile terminal 100 to transmit a sound signal outwardly through the first through hole. The second through hole 102 can be configured to enable a fingerprint unit in the mobile terminal 100 to acquire use finger information through the second through hole 102. [0028]In some embodiments, the first through hole 101 can be disposed at a top middle of the cover plate 10, and the second through hole 102 can be disposed at a bottom middle of the cover plate 10. [0029]The cover plate 10 can be a transparent glass cover plate. In some embodiments, the cover plate 10 can be a glass cover plate made of a material such as sapphire. [0030]The display screen 20 is mounted to the housing 50 so as to form a display surface of the mobile terminal 100. Referring to FIG. 4, the display screen 20 includes a display area 201 and a non-display area 202. The display area 201 is configured to display information like image and text. The non-display area 202 does not display information. The non-display area 202 can be provided with a functional assembly such as the fingerprint unit and a touch circuit. [0031]The display area 201 is provided with a third through hole 203. The third through hole 203 is aligned with the first through hole 101 in the cover plate 10. The third through hole 203 can be configured so that the camera in the mobile terminal 100 can acquire an external image signal through the third through hole, a proximity sensor in the mobile terminal 100 can emit and receive a signal through the third through hole, and the receiver in the mobile terminal 100 can transmit the sound signal outwardly through the third through hole. [0032]The non-display area 202 is provided with a fourth through hole 204. The fourth through hole 204 is aligned with the second through hole 102 in the cover plate 10. The fourth through hole 204 can be configured so that the fingerprint unit in the mobile terminal 100 can acquire the user fingerprint information through the fourth through hole. In some embodiments, the third through hole 203 can be disposed at a top middle of the display area 201, and the fourth through hole 204 can be disposed at a bottom middle of the non-display area 202. [0033]The circuit board 30 is mounted in the housing 50. The circuit board 30 can be a main board of the mobile terminal 100 and functional assemblies such as the camera, the proximity sensor, and the receiver can be integrated in the circuit board 30. Meanwhile, the display screen 20 can be electrically connected to the circuit board 30. [0034]Referring to FIG. 5, the camera 31 can be integrated in the circuit board 30. The camera 31 includes a base 311 and a camera lens 312. The camera lens 312 is mounted to the base 311. A contour of the base 311 can be rectangular, circular or in other shapes. A contour size of the base 311 is larger than a contour size of the camera lens 312, so that a step 310 can be formed at a mounting face of the camera lens 312 and the base 311. A step surface of the step 310 faces the display screen 20 in the mobile terminal 100. [0035]The sensor assembly 32 is mounted to the step 310. The sensor assembly 32 includes a signal emitter 321 and a signal receiver 322. The signal emitter 321 and the signal receiver 322 can compose the proximity sensor. The signal emitter 321 and the signal receiver 322 are electrically connected to the circuit board 30. [0036]The signal emitter 321 is configured to emit a signal, and the signal receiver 322 is configured to receive a reflected signal formed by reflecting the emitted signal by an external object. The mobile terminal 100 can judge a distance state between the mobile terminal 100 and the external object according to strength of the reflected signal so as to control a display state of the display screen 20. [0037]The above-mentioned signal can be a light signal such as an infrared ray, a laser and the like, and can also be other types of signals. [0038]The signal emitter 321 and the signal receiver 322 can be disposed at different sides of the camera lens 312 along a width direction of the mobile terminal 100. The signal emitter 321 and the signal receiver 322 can also be disposed at different sides of the camera lens 312 along a length direction of the mobile terminal 100. [0039]As the camera 31 is formed with the step 310 and hence the sensor assembly 32 can be mounted on the step 310, it is unnecessary to provide an independent aperture for the sensor assembly 32 in the mobile terminal 100. Thus, occupation of the sensor assembly 32 on the display area in the screen of the mobile terminal 100 is reduced, that is, a ratio of the display area to the screen is increased. [0040]Referring to FIG. 6, the sensor assembly 32 further includes an ambient light sensor 323. The ambient light sensor 323 is disposed around the camera lens 312 and mounted on the step 310. The ambient light sensor 323 is also electrically connected to the circuit board 30. The ambient light sensor 323 is configured to receive an ambient light signal. The mobile terminal 100 can also adjust brightness of the display screen 20 according to strength of the ambient light signal. [0041]Referring to FIG. 7, the receiver 33 can be integrated in the circuit board 30. The receiver 33 can be comprised of a vibration section 33-1, a magnetic circuit section 33-2 and a supporting section 33-3. The supporting section 33-3 is formed as a casing of the receiver 33. The magnetic circuit section 33-2 is mounted in the casing so as to form a magnetic circuit. The vibration section 33-1 is mounted above the magnetic circuit section 33-2 and produces sound through vibration. [0042]The vibration section 33-1 includes a diaphragm 331 and a voice coil 332. The voice coil 332 is disposed at a side of the diaphragm 331 and connected with the diaphragm 331. The connection between the voice coil 332 and the diaphragm 331 can be realized by a plurality of methods. For example, the voice coil 332 can be connected with the diaphragm 331 in an adhesive method. [0043]The diaphragm 331 can be a transparent diaphragm so as to allow a light signal to pass through. A shape of the diaphragm 331 matches a shape of the receiver 33. The shape of the diaphragm 331 can be circular. [0044]The diaphragm 331 can be an elastic diaphragm and can vibrate up and down along a thickness direction of the diaphragm. When the diaphragm 331 vibrates, air at two sides of the diaphragm vibrates therewith so as to produce sound. [0045]The voice coil 332 is formed by winding a conductive wire upon an insulation frame, the wire having an insulating outer layer. The conductive wire on the voice coil 332 is configured to be connected to an audio-frequency circuit inside the mobile terminal 100. [0046]The magnetic circuit section 33-2 includes a permanent magnet 333, a magnetically conductive sheet 334 and a magnetically conductive plate 335. The magnetically conductive sheet 334 can be disposed at a side (N pole) of the permanent magnet 333, and the magnetically conductive plate 335 is disposed at the other side (S pole) of the permanent magnet 333. The magnetically conductive sheet 334 and the magnetically conductive plate 335 are configured to conduct a magnetic induction line emitted by the permanent magnet 333 so as to form a closed magnetic circuit. The magnetic induction line emitted by the N pole of the permanent magnet 333 passes through the magnetically conductive sheet 334, then passes through the magnetically conductive plate 335, and finally enters the S pole of the permanent magnet 333, so as to form a closed loop circuit. The magnetically conductive sheet 334 can be an iron sheet, and the magnetically conductive plate 335 can be a thin iron plate. The shapes of the magnetically conductive sheet 334 and the magnetically conductive plate 335 can be square, rectangular, or circular. The magnetically conductive sheet 334, the permanent magnet 333, and the magnetically conductive plate 335 can be fastened in the adhesive manner. [0047]The permanent magnet 333 has an aperture 330, the magnetically conductive sheet 334 is provided with an aperture 340, and the magnetically conductive plate 335 has an aperture 350. The aperture 340 and the aperture 350 are both aligned with the aperture 330. [0048]The transparent diaphragm 331, the aperture 340, the aperture 330 and the aperture 350 together form a light signal passage so as to allow the light signal to pass through. [0049]In some embodiments, the permanent magnet 333 is a nanometer permanent magnet. That is, permanent magnetic material particles are uniformly coated with a layer of soft magnetic material by nanotechnology, or the permanent magnetic material and the soft magnetic material are combined together by a chemical process such as a replacement reaction, so as to obtain permanent magnetic nanoparticles. Then, the nanometer permanent magnet is manufactured by techniques such as high-pressure molding or high-temperature sintering. The nanometer permanent magnet has higher magnetic induction intensity inside relative to an ordinary Nd—Fe—B permanent magnet. Thus, with the same volume of the permanent magnet, the receiver adopting the nanometer permanent magnet has a higher sound pressure level. [0050]In some embodiments, the magnetically conductive plate 335 is U-shaped. The permanent magnet 333 and the magnetically conductive sheet 334 are disposed at a bottom of the U shape of the magnetically conductive plate 335. Extension portions at two sides of the magnetically conductive plate 335 extend upwards to two sides of the permanent magnet 333 and the magnetically conductive sheet 334. A gap is formed between each of the side extension portions of the magnetically conductive plate 335 and the corresponding side of two sides of the permanent magnet 333 and the magnetically conductive sheet 334, and the voice coil 332 is disposed in the gap. [0051]The supporting section 33-3 includes a support 336 and a protection cover 337. The support 336 is formed in an annular shape. A peripheral protrusion is provided at a periphery of an end of the support 336. The protection cover 337 is formed in an annular shape. An aperture can be provided in a center of the protection cover 337, so that the sound produced by the diaphragm 331 can be transmitted outwardly. A section of the protection cover 337 exhibits a reversed L shape. A periphery of the protection cover 337 is provided with a peripheral recess. With the peripheral protrusion of the support 336 fitted with the peripheral recess of the protection cover 337, the protection cover 337 is mounted to the support 336. The diaphragm 331 is mounted to the support 336 by means of a mounting portion at an edge of the diaphragm. The mounting portion at the edge of the diaphragm 331 can be mounted to the support 336 in the adhesive method. [0052]In some embodiments, the support 336 is made of nanomaterial. The protection cover 337 can also be made of nanomaterial. Both of the support 336 and the protection cover 337 can be integrally formed by the nanomaterial through injection molding. The support 336 and the protection cover 337 made of nanomaterial have higher strength, which can improve mechanical reliability of the receiver 33. [0053]Referring to FIG. 8, in the mobile terminal 100, the camera 31 and the receiver 33 are both mounted to the circuit board 30. The camera 31 is aligned with the light signal passage 34 of the receiver 33. The sensor assembly 32 can be mounted on the step of the camera 31. Meanwhile, a sensor assembly 32 is electrically connected to the circuit board 30. The sensor assembly 32 includes the signal emitter 321 and the signal receiver 322. The signal emitter 321 and the signal receiver 322 can be disposed at two sides of the camera lens of the camera 31 respectively. [0054]Reference is still made to FIGS. 1 and 2. [0055]The battery 40 is mounted inside the housing 50 and configured to provide electrical energy for the mobile terminal 100. [0056]The housing 50 is configured to form an external contour of the mobile terminal 100. The housing 50 can be made of plastic or metal. The housing 50 can be formed integrally. [0057]Referring to FIG. 9, FIG. 9 is a section view of the mobile terminal illustrated in FIG. 1 taken along P-P direction. The cover plate 10 is mounted to the housing 50. The cover plate 10 has an aperture 110. The display screen 20 is also mouthed to the housing 50. The display screen 20 has an aperture 210 (namely the above-mentioned third through hole 203, there is no strict difference between terms “aperture” and “through hole” in the descriptions). The cover plate 10 covers the display screen 20. The aperture 210 is aligned with the aperture 110. The circuit board 30 is mounted in the housing 50. [0058]The camera 31 and the receiver 33 are mounted to the circuit board 30. The receiver 33 is disposed between the camera 31 and the display screen 20. The receiver 33 is aligned with the aperture 210 and the aperture 110 so that the receiver 33 can transmit the sound signal outwardly through the aperture 210 and the aperture 110. The receiver 33 has the light signal passage 34. The camera 31 is aligned with the light signal passage 34 so that the camera 31 can acquire the light signal from the outside through the light signal passage 34, the aperture 210 and the aperture 110. [0059]As the camera 31 is disposed below the receiver 33 along the thickness direction of the mobile terminal 100, it is unnecessary to provide independent apertures for the camera 31 and the receiver 33 in the display screen 20. Thus, occupation of the apertures in the display screen 20 relative to the display area is reduced, and the ratio of the display area to the screen of the mobile terminal 100 is increased. [0060]In some embodiments, as illustrated in FIG. 10, the sensor assembly 32 can be mounted to the circuit board 30. The sensor assembly 32 is aligned with the light signal passage 34 in the receiver 33 so as to allow the sensor assembly 32 to receive and/or emit signals through the light signal passage 34, the aperture 210 and the aperture 110. The sensor assembly 32 includes the signal emitter 321 and the signal receiver 322. The signal emitter 321 and the signal receiver 322 can be disposed at two sides of the camera 31 respectively. In some embodiments, the sensor assembly 32 can further include the ambient light sensor. The ambient light sensor can be disposed around the camera 31. [0061]In some embodiments, as illustrated in FIG. 11, the camera 31 is formed with the step 310. The step surface of the step 310 faces the display screen 20, and the sensor assembly 32 can be disposed on the step 310. The sensor assembly 32 includes the signal emitter 321 and the signal receiver 322. The signal emitter 321 and the signal receiver 322 can be disposed at two sides of the camera lens of the camera 31 respectively. [0062]In some embodiments, the sensor assembly 32 can further include the ambient light sensor. The ambient light sensor can be disposed on the step 310 and around the camera lens of the camera 31. [0063]As illustrated in FIG. 12, a receiver and camera assembly configured to be mounted in a mobile terminal is provided in embodiments of the present disclosure, including a receiver 33, a camera 31. The receiver 33 has a light signal passage 34, and the camera 31 is aligned with the light signal passage 34. The receiver 33 and the camera 31 can be integrated. Specifically, the receiver 33 and the camera 31 can be mounted to a mounting plate 35. The mounting plate 35 can be configured to be connected to a circuit board of the mobile terminal. [0064]The mobile terminal provided by the embodiment of the present disclosure is described in detail above, and specific examples are used herein to describe the principle and embodiments of the present disclosure. The description of the foregoing embodiments is merely intended to help understand the present disclosure. Meanwhile, those skilled in the art can make modifications to the specific embodiments and application scope according to the idea of the present disclosure. To sum up, the contents of the description should not be construed as limiting the present disclosure.(String), 相关申请的交叉引用 [0001] 本申请要求于2017年3月7日向中华人民共和国国家知识产权局提交的申请号为201710132219.0的中国专利申请的优先权,将其全部内容引用于此。 场地 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端、移动终端接收器、移动终端接收器和摄像头组件。 背景 [0003] 在传统的移动终端(例如智能手机)中,接收器安装在移动终端中。 接收器的顶部设有孔,接收器通过孔向外发出声波,从而使移动终端向用户发送声音信号。 [0004] 另一方面,移动终端中还安装有摄像头,摄像头的顶部也设置有光圈,以实现摄像头通过光圈获取外界图像。 [0005] 然而,在这种设计方案中,需要在屏幕上设置多个开孔,以实现接收器和摄像头的功能。 多个开孔需要占据移动终端屏幕的较大面积,导致显示面积屏占比较低。 概括 [0006] 本发明实施例提供一种移动终端,包括外壳、显示屏、摄像头和听筒,所述显示屏安装在所述外壳上并具有第一开孔; 摄像头安装在外壳内并对准第一光圈; 手机安装于显示屏幕与摄像头之间,并通过第一开孔传送声音信号。 接收器具有光信号通道,摄像头通过光信号通道与第一光圈获取外界光信号。 [0007] 本发明实施例还提供一种接收器,用于安装在移动终端中,包括振动部分和磁路部分,振动部分包括透明振膜,磁路部分上形成有通孔,透明振膜 通孔形成光信号通道。 [0008] 本发明实施例还提供了一种接收器和摄像头组件,用于安装在移动终端中,包括接收器、摄像头,接收器具有光信号通道,摄像头对准光信号通道。 附图的简要说明 [0009] 为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简单介绍。 显然,以下描述中的附图仅仅是本发明的部分实施例,本领域普通技术人员在没有做出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0010] 图1为本发明实施例提供的一种移动终端的示意图。 [0011] 图2为本发明实施例提供的移动终端的分解图。 [0012] 图3为本发明实施例提供的盖板的示意图。 [0013] 图4为本发明实施例提供的显示屏的示意图。 [0014] 图5为本发明实施例提供的摄像头的第一示意图。 [0015] 图6为本发明实施例提供的摄像头的第二示意图。 [0016] 图7为本发明实施例提供的接收器的剖视图。 [0017] 图8为本发明实施例中接收器、摄像头和传感器组件安装到电路板上的示意图。 [0018] 图9为图1中移动终端沿P-P方向的第一剖视图。 [0019]图10为图1中移动终端沿P-P方向的剖视图之二。 [0020] 图11为图1中移动终端沿P-P方向的剖视图之三。 [0021] 图12为本发明实施例提供的接收器和摄像头组件的示意图。 详细说明 [0022] 下面结合本发明实施例中的附图,对本发明实施例的技术方案进行清楚、完整的描述。 显然,所描述的实施例只是本发明的一部分实施例,而不是所有实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0023] 在说明书中,应当理解诸如“中央”、“纵向”、“横向”、“长度”、“宽度”、“厚度”、“上部”、“下部”、“前部”、“ 后”、“左”、“右”、“垂直”、“水平”、“顶部”、“底部”、“内部”、“外部”、“顺时针”和“逆时针”,应解释为指 然后描述的方向或在讨论中的附图中所示的方向。 这些相关术语是为了描述的方便,并不要求本公开在特定方向上被构造或操作。 此外,本文中使用的诸如“第一”和“第二”等术语是为了描述的目的,并不旨在指示或暗示相对重要性或重要性。 因此,由“第一”和“第二”限定的特征旨在指示或暗示包括这些特征中的一个或多个。 在本公开的描述中,除非另有说明,否则术语“多个”是指两个或两个以上。 [0024] 在本发明中,除非另有说明或限制,术语“安装”、“连接”、“接合”、“固定”等具有广泛的使用意义,例如可以是固定连接、可拆卸连接或整体连接 连接; 也可以是机械或电气连接; 也可以是直接连接或通过中间结构的间接连接; 也可能是两个元素的内部通信。 本领域技术人员可以根据具体情况理解上述术语。 [0025] 在本发明的描述中,第一特征在第二特征“之上”的结构可以包括第一特征直接接触第二特征的实施例,也可以包括形成附加特征的实施例 在第一特征和第二特征之间,使得第一特征不直接接触第二特征,除非另有说明。 此外,第一特征“在”第二特征“之上”、“之上”或“之上”可包括其中第一特征恰好在第二特征“之上”、“之上”或“之上”的实施例, 并且还可以包括第一特征不在第二特征“之上”、“上方”或“之上”的实施例,或者仅仅意味着第一特征的海平面高度大于 第二个特点。 虽然第一特征“在”第二特征“下方”、“下方”或“底部”可以包括第一特征正好在第二特征“下方”、“下方”或“底部”的实施例,并且也可以 包括第一个特征不在第二个特征“下方”、“下方”或“底部”的实施例,或者仅表示第一个特征的海平面高度小于第二个特征的海平面高度 . [0026]以下公开提供许多不同的实施例或例子来实现本公开的不同结构。 为了简化本公开的公开,详细说明了特定示例中的组件和配置。 当然,它们是示例性的,并不旨在限制本公开。 此外,为了简单和清楚的目的,在本公开的不同示例中可以重复附图标记和/或字母,其不应被构造为指示各种实施例和/或配置之间的关系。 此外,本公开提供了各种具体工艺和材料的示例,但是本领域技术人员可以想到其他工艺的应用和/或其他材料的利用。 [0027] 参考图1和图2,移动终端 100 包括一个盖板 10 , 显示屏 20 , 电路板 30 , 一块电池 40 和一个住房 50 . 盖板 10 安装在显示屏上 20 以覆盖显示屏 20 . 参见图3,盖板 10 有一个第一通孔 101 和第二个通孔 102 . 第一个通孔 101 和第二个通孔 102 设置于盖板的两端 10 分别。 第一个通孔 101 可以配置为启用移动终端中的接收器 100 通过第一通孔向外传输声音信号。 第二个通孔 102 可配置为启用移动终端中的指纹单元 100 通过第二通孔获取用户手指信息 102 . [0028] 在一些实施例中,第一通孔 101 可以设置在盖板的顶部中间 10 , 和第二个通孔 102 可以设置在盖板的底部中间 10 . [0029] 盖板 10 可以是透明的玻璃盖板。 在一些实施例中,盖板 10 可以是由蓝宝石等材料制成的玻璃盖板。 [0030] 显示屏 20 安装在外壳上 50 从而形成移动终端的显示面 100 . 参考图4,显示屏幕 20 包括一个展示区 201 和非展示区 202 . 展示区 201 用于显示图像和文本等信息。 非展示区 202 不显示信息。 非展示区 202 可设置指纹单元、触摸电路等功能组件。 [0031] 展示区 201 设有第三通孔 203 . 第三个通孔 203 与第一个通孔对齐 101 在盖板 10 . 第三个通孔 203 可以配置让手机端的摄像头 100 可以通过移动终端中的接近传感器第三通孔获取外部图像信号 100 可以通过第三通孔发射和接收信号,移动终端中的接收器 100 可通过第三通孔向外传输声音信号。 [0032] 非展示区 202 设有第四通孔 204 . 第四个通孔 204 与第二个通孔对齐 102 在盖板 10 . 第四个通孔 204 可配置移动终端中的指纹单元 100 可以通过第四通孔获取用户指纹信息。 在一些实施例中,第三通孔 203 可以设置在显示区域的顶部中间 201 , 和第四个通孔 204 可以设置在非显示区域的底部中间 202 . [0033] 电路板 30 安装在外壳中 50 . 电路板 30 可以是移动终端的主板 100摄像头、接近传感器、接收器等功能组件可以集成在电路板上 30 . 同时,显示屏 20 可以电连接到电路板 30 . [0034] 参考图5,相机 31 可以集成在电路板上 30 . 相机 31 包括一个基地 311 和一个相机镜头 312 . 相机镜头 312 安装在底座上 311 . 底座轮廓 311 可以是矩形、圆形或其他形状。 底座轮廓尺寸 311 大于相机镜头的轮廓尺寸 312 , 所以一步 310 可以形成在相机镜头的安装面上 312 和基地 311 . 台阶的台阶面 310 面对显示屏 20 在移动端 100 . [0035] 传感器总成 32 安装在台阶上 310 . 传感器总成 32 包括一个信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可以组成接近传感器。 信号发射器 321 和信号接收器 322 电连接到电路板 30 . [0036] 信号发射器 321 被配置为发射信号,并且信号接收器 322 被配置为接收由外部物体反射发射信号形成的反射信号。 移动端 100 可以判断移动终端之间的距离状态 100 以及外界物体根据反射信号的强弱来控制显示屏的显示状态 20 . [0037] 上述信号可以是红外线、激光等光信号,也可以是其他类型的信号。 [0038] 信号发射器 321 和信号接收器 322 可以设置在相机镜头的不同侧面 312 沿移动终端的宽度方向 100 . 信号发射器 321 和信号接收器 322 也可以设置在相机镜头的不同侧面 312 沿着移动终端的长度方向 100 . [0039] 作为相机 31 是用台阶形成的 310 因此传感器组件 32 可以安装在台阶上 310 ,无需为传感器组件提供独立的孔径 32 在移动端 100 . 因此,传感器组件的占用 32 在移动终端屏幕的显示区域 100 减小,即显示区域与屏幕的比例增大。 [0040] 参考图 6,传感器组件 32 还包括一个环境光传感器 323 . 环境光传感器 323 设置于相机镜头周围 312 并安装在台阶上 310 . 环境光传感器 323 也电连接到电路板 30 . 环境光传感器 323 被配置为接收环境光信号。 移动端 100 还可以调节显示屏的亮度 20 根据环境光信号的强度。 [0041] 参考图7,接收器 33 可以集成在电路板上 30 . 收件人 33 可以由振动部分组成 33 - 1 , 磁路部分 33 - 2 和一个支持部分 33 - 3 . 支撑部分 33 - 3 形成为接收器的外壳 33 . 磁路部分 33 - 2 安装在外壳内形成磁路。 振动部分 33 - 1 安装在磁路部分上方 33 - 2 并通过振动产生声音。 [0042] 振动部分 33 - 1 包括隔膜 331 和一个音圈 332 . 音圈 332位于隔膜的一侧 331 并与隔膜相连 331 . 音圈之间的连接 332 和隔膜 331 可以通过多种方法实现。 例如,音圈 332 可接膜片 331 在粘合方法中。 [0043] 隔膜 331 可以是透明膜片以允许光信号通过。 横膈膜的形状 331 匹配接收器的形状 33 . 隔膜的形状 331 可以是圆形的。 [0044] 隔膜 331 可以是弹性膜片,可以沿膜片的厚度方向上下振动。 当隔膜 331 振动时,振膜两侧的空气随之振动而发出声音。 [0045] 音圈 332 由导线缠绕在绝缘框架上形成,该导线具有绝缘外层。 音圈上的导线 332 用于连接移动终端内部的音频电路 100 . [0046] 磁路部分 33 - 2 包括一个永磁体 333 , 导磁片 334 和导磁板 335 . 导磁片 334 可置于永磁体一侧(N极) 333 , 导磁板 335 设置在永磁体的另一侧(S极) 333 . 导磁片 334 和导磁板 335 被配置为传导由永磁体发出的磁感应线 333 从而形成闭合磁路。 永磁体N极发出的磁感应线 333 穿过导磁片 334 , 然后穿过导磁板 335 ,最后进入永磁体的S极 333 ,从而形成闭环电路。 导磁片 334 可以是铁皮,导磁板 335 可以是薄铁板。 导磁片的形状 334 和导磁板 335 可以是正方形、长方形或圆形。 导磁片 334 , 永磁体 333 , 导磁板 335 可以用粘着的方式固定。 [0047] 永磁体 333 有光圈 330 , 导磁片 334 设有光圈 340 , 导磁板 335 有光圈 350 . 光圈 340 和光圈 350 都与光圈对齐 330 . [0048] 透明隔膜 331 , 孔径 340 , 孔径 330 和光圈 350 共同形成光信号通道,以供光信号通过。 [0049] 在一些实施例中,永磁体 333 是纳米永磁体。 即通过纳米技术在永磁材料颗粒上均匀地包覆一层软磁材料,或者通过置换反应等化学过程将永磁材料与软磁材料结合在一起,从而得到永磁纳米颗粒 . 然后,通过高压成型或高温烧结等工艺制造纳米永磁体。 该纳米永磁体相对于普通的Nd-Fe-B永磁体内部具有更高的磁感应强度。 因此,在永磁体体积相同的情况下,采用纳米永磁体的接收机具有更高的声压级。 [0050] 在一些实施例中,导磁板 335 是U形的。 永磁体 333 和导磁片 334 设置于导磁板的U形底部 335. 导磁板两侧延伸部 335 向上延伸至永磁体两侧 333 和导磁片 334 . 导磁板的各侧延伸部之间形成有间隙 335 和永磁体两侧的对应边 333 和导磁片 334 , 和音圈 332 设置于间隙中。 [0051] 支撑部分 33 - 3 包括支持 336 和保护罩 337 . 支撑 336 形成为环状。 支架一端周边设有一周边凸起 336 . 保护罩 337 形成为环状。 保护盖中央可开孔 337 , 这样振膜发出的声音 331 可以向外传播。 一段保护盖 337 呈倒L形。 保护罩周边 337 设有外围凹槽。 与支架的外围突起 336 与保护盖的周边凹槽相配 337 , 防护罩 337 安装在支架上 336 . 隔膜 331 安装在支架上 336 通过隔膜边缘的安装部分。 膜片边缘的安装部分 331 可以安装到支架上 336 在粘合法中。 [0052] 在一些实施例中,支持 336 由纳米材料制成。 保护罩 337 也可以由纳米材料制成。 两者都支持 336 和保护罩 337 纳米材料可通过注塑成型一体成型。 支撑 336 和保护罩 337 由纳米材料制成,具有更高的强度,可以提高接收器的机械可靠性 33 . [0053] 参见图8,在移动终端中 100 , 相机 31 和接收器 33 都安装在电路板上 30 . 相机 31 与光信号通道对齐 34 接收者的 33 . 传感器总成 32 可以安装在相机的台阶上 31 . 同时,传感器组件 32 与电路板电连接 30 . 传感器总成 32 包括信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可设置于相机镜头两侧 31 分别。 [0054] 仍然参考图1和图2。 [0055] 电池 40 安装在外壳内 50 用于为移动终端提供电能 100 . [0056] 住房 50 用于形成移动终端的外轮廓 100 . 住房 50 可以由塑料或金属制成。 住房 50 可以一体成型。 [0057] 参见图9,图9为图1所示移动终端沿P-P方向的剖视图。 盖板 10 安装在外壳上 50 . 盖板 10 有光圈 110 . 显示屏 20 也被吹到房屋 50 . 显示屏 20 有光圈 210 (即上述第三个通孔 203 , 描述中术语“孔径”和“通孔”之间没有严格区别)。 盖板 10 覆盖显示屏 20 . 光圈 210 与光圈对齐 110 . 电路板 30 安装在外壳中 50 . [0058] 相机 31 和接收器 33 安装在电路板上 30 . 收件人 33 置于相机之间 31 和显示屏 20 . 收件人 33 与光圈对齐210 和光圈 110 以便接收者 33 可以通过孔径向外传输声音信号 210 和光圈 110 . 收件人 33 有光信号通道 34 . 相机 31 与光信号通道对齐 34 这样相机 31 可通过光信号通道从外部获取光信号 34 , 孔径 210 和光圈 110 . [0059] 作为相机 31 置于接收器下方 33 沿移动终端的厚度方向 100 ,不需要为相机提供独立的光圈 31 和接收器 33 在显示屏上 20 . 从而占据显示屏的开孔 20 相对于显示区域缩小,显示区域占移动终端屏幕的比例 100 增加。 [0060] 在一些实施例中,如图 10 所示,传感器组件 32 可以安装到电路板上 30 . 传感器总成 32 与光信号通道对齐 34 在接收器中 33 以便让传感器组装 32 通过光信号通道接收和/或发射信号 34 , 孔径 210 和光圈 110 . 传感器总成 32 包括信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可置于摄像头两侧 31 分别。 在一些实施例中,传感器组件 32 还可以包括环境光传感器。 环境光传感器可以设置在摄像头周围 31 . [0061] 在一些实施例中,如图 11 所示,相机 31 是用台阶形成的 310 . 台阶的台阶面 310 面对显示屏 20 和传感器组件 32 可以放在台阶上 310 . 传感器总成 32 包括信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可设置于相机镜头两侧 31 分别。 [0062] 在一些实施例中,传感器组件 32 还可以包括环境光传感器。 环境光感测器可设置于台阶上 310 以及相机镜头周围 31 . [0063] 如图12所示,本发明实施例提供了一种用于安装在移动终端中的接收器和摄像头组件,包括: 33 , 相机 31 . 收件人 33 有光信号通道 34 , 和相机 31 与光信号通道对齐 34 . 收件人 33 和相机 31 可以集成。 具体来说,接收方 33 和相机 31 可以安装到安装板上 35 . 安装板 35 可以配置为连接到移动终端的电路板。 [0064] 以上对本发明实施例提供的移动终端进行了详细描述,这里通过具体的例子来说明本发明的原理和实施方式。 上述实施例的描述只是为了帮助理解本发明。 同时,本领域的技术人员可以根据本公开的思想对具体实施例和适用范围进行修改。 综上所述,说明书的内容不应视为对本发明的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.167 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.168 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2018229784A1(String), AU2018229784B2(String), CN106936954A(String), CN106936954B(String), CN111447309A(String), CN111447309B(String), EP3373564A1(String), EP3373564B1(String), ES2790250T3(String), HK1236704A(String), HK1236704A1(String), IN201834001094A(String), JP2020503767A(String), JP6783393B2(String), SG11201906191TA(String), SG11201906191TB(String), TW201834436A(String), TWI658719B(String), US10291756B2(String), US10834245B2(String), US20180262602A1(String), US20190230204A1(String), WO2018161720A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.169 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2018229784A1(String), AU2018229784B2(String), CN106936954A(String), CN106936954B(String), CN111447309A(String), CN111447309B(String), EP3373564A1(String), EP3373564B1(String), ES2790250T3(String), HK1236704A(String), HK1236704A1(String), IN201834001094A(String), JP2020503767A(String), JP6783393B2(String), SG11201906191TA(String), SG11201906191TB(String), TW201834436A(String), TWI658719B(String), US10291756B2(String), US10834245B2(String), US20180262602A1(String), US20190230204A1(String), WO2018161720A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.171 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10291756B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.179 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.179 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.179 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2018229784A1(String), AU2018229784B2(String), CN106936954A(String), CN106936954B(String), CN111447309A(String), CN111447309B(String), EP3373564A1(String), EP3373564B1(String), ES2790250T3(String), HK1236704A(String), HK1236704A1(String), IN201834001094A(String), JP2020503767A(String), JP6783393B2(String), SG11201906191TA(String), SG11201906191TB(String), TW201834436A(String), TWI658719B(String), US10291756B2(String), US10834245B2(String), US20180262602A1(String), US20190230204A1(String), WO2018161720A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), AU2018229784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), AU2018229784B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.195 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.196 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), CN106936954A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.208 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.208 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.208 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), CN106936954B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.224 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), CN111447309A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.240 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), CN111447309B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), EP3373564A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.270 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.271 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), EP3373564B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), ES2790250T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.302 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), HK1236704A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.318 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), HK1236704A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), IN201834001094A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.343 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), JP2020503767A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.354 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.355 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), JP6783393B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.367 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), SG11201906191TA(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.379 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), SG11201906191TB(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), TW201834436A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.396 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.397 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), TWI658719B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.405 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), US10291756B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), US10834245B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.424 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.425 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), US20180262602A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.434 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), US20190230204A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.442 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270716(Integer), WO2018161720A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10291756B2(String), US10291756B2(String), 1557763200(Integer), 270716(Integer), 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.461 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.462 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.463 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.464 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.465 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185041(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.467 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 1(Integer), 185041(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.476 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1681975542(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185041(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.480 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75922(Integer), 2(Integer), 185041(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.487 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.488 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.489 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.499 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.512 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.513 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8731625B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method of write protection for memory card in the mobile terminal(String), 移动终端及移动终端中存储卡的写保护方法(String), US8731625B2(String), A mobile terminal and method to write protect a memory card in the mobile terminal. The mobile terminal comprises a body, a battery and a battery cover. The battery cover has a short-circuit connecting member. A memory card socket accommodates a pluggable memory card. A writing control unit has input and output ports, and when the battery cover is jointed with the body, the input and output ports contact the short-circuit connecting member to form a short-circuit connection therebetween; the writing control unit detects whether the battery cover is removed by outputting a test signal from the output port and detecting for the test signal at the input port; if the battery cover is removed, the test signal is not detected at the input port and data is prohibited from being written into the memory card.(String), 一种移动终端和对移动终端中的存储卡进行写保护的方法。 移动终端包括机身、电池和电池盖。 电池盖具有短路连接件。 存储卡插槽可容纳可插拔存储卡。 写控制单元具有输入输出端口,当电池盖与本体接合时,输入输出端口与短路连接件接触,形成短路连接。 写入控制单元通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除。 如果取下电池盖,则输入端口检测不到测试信号,数据被禁止写入存储卡。(String), US13/409664(String), 1330531200(Integer), US8731625B2(String), 1400515200(Integer), 1400515200(Integer), 美国(String), 4(Integer), CN(String), 3(Integer), 4(Integer), EP1531385A2 | EP2280490A2 | GB2270445A | US20080018541A1(String), 13(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.527 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185042(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b971fd38c87d42e2943740fe38f7808d.png(String), 185042(Integer), b971fd38c87d42e2943740fe38f7808d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.537 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.538 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method of write protection for memory card in the mobile terminal(String), 移动终端及移动终端中存储卡的写保护方法(String), US8731625B2(String), A mobile terminal and method to write protect a memory card in the mobile terminal. The mobile terminal comprises a body, a battery and a battery cover. The battery cover has a short-circuit connecting member. A memory card socket accommodates a pluggable memory card. A writing control unit has input and output ports, and when the battery cover is jointed with the body, the input and output ports contact the short-circuit connecting member to form a short-circuit connection therebetween; the writing control unit detects whether the battery cover is removed by outputting a test signal from the output port and detecting for the test signal at the input port; if the battery cover is removed, the test signal is not detected at the input port and data is prohibited from being written into the memory card.(String), 一种移动终端和对移动终端中的存储卡进行写保护的方法。 移动终端包括机身、电池和电池盖。 电池盖具有短路连接件。 存储卡插槽可容纳可插拔存储卡。 写控制单元具有输入输出端口,当电池盖与本体接合时,输入输出端口与短路连接件接触,形成短路连接。 写入控制单元通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除。 如果取下电池盖,则输入端口检测不到测试信号,数据被禁止写入存储卡。(String), US13/409664(String), 1330531200(Integer), US8731625B2(String), 1400515200(Integer), 1400515200(Integer), 美国(String), 2(Integer), 4(Integer), CN(String), 3(Integer), 4(Integer), EP1531385A2 | EP2280490A2 | GB2270445A | US20080018541A1(String), \20230420\b971fd38c87d42e2943740fe38f7808d.png(String), 13(Integer), 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 1. A mobile terminal comprising a body, a battery and a battery cover, wherein,the battery cover is provided with a short-circuit connecting member;the body comprises:a memory card socket configured to accommodate a pluggable memory card;a writing control unit including an input port and an output port, the writing control unit configured such that, in response to the battery cover being joined with the body, the input port and the output port of the writing control unit both electrically contact the short-circuit connecting member, so as to form a short-circuit connection between the input port and the output port;wherein the writing control unit is configured to detect whether the battery cover is removed by outputting a test signal from the output port and detecting for the test signal at the input port, whereby it is determined that the battery cover is removed when the test signal is not detected at the input port and data is prohibited from being written into the memory card when the battery cover is removed;a communication module, wherein the short-circuit connecting member is an antenna of the communication module; anda state detection unit configured to detect whether the communication module is under a working state, wherein the writing control unit stops a detection of the battery cover and/or allows data to be written into the memory card if the state detection unit detects that the communication module is under the working state.(String), 1.移动端包括本体、电池和电池盖,其中,电池盖设有短路连接件;主体包括:存储卡插槽,用于容纳可插拔的存储卡;写入控制单元,包括输入端口和输出端口,写入控制单元配置成响应于电池盖与主体接合,写入控制单元的输入端口和输出端口均电接触短路-电路连接件,以在输入端口和输出端口之间形成短路连接;其中,写入控制单元被配置为通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除,从而当测试信号是时确定电池盖被移除。取下电池盖时输入口未检测到数据禁止写入存储卡;通信模块,其中短路连接件为通信模块的天线;和状态检测单元,用于检测通信模块是否处于工作状态,其中,如果状态检测单元检测到通信,则写入控制单元停止检测电池盖和/或允许数据写入存储卡模块处于工作状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 2. The mobile terminal according to claim 1, wherein,when the test signal is detected at the input port, the writing control unit determines that the battery cover is not removed, and allows data to be written into the memory card.(String), 2.根据权利要求1所述的移动终端,其中,当输入端口检测到测试信号时,写入控制单元判断电池盖未被移除,并允许数据写入存储卡。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.550 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 3. The mobile terminal according to claim 1, wherein,the communication module is a Bluetooth module or a Wireless Local Area Network communication module.(String), 3.根据权利要求1所述的移动终端,其中,通信模块为蓝牙模块或无线局域网通信模块。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 4. The mobile terminal according to claim 1, wherein the body further comprises:a state detection unit configured to detect whether the communication module is under an working state.(String), 4.根据权利要求1所述的移动终端,其中该主体还包括:状态检测单元,用于检测通信模块是否处于工作状态。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 5. The mobile terminal according to claim 4, wherein, the writing control unit is further configured to detect regularly or at a time when there is data to be stored into the memory card, whether the battery cover is removed, in case the state detection unit detects that the communication module is not under the working state.(String), 5.根据权利要求4所述的移动终端,其中,写入控制单元还用于在状态检测单元检测到通信模块不处于工作状态时,定时或在有数据需要存储到存储卡时检测电池盖是否被取下.6.根据权利要求4所述的移动终端,其中,写入控制单元还用于当状态检测单元检测到通信模块处于工作状态时,停止检测电池盖和/或允许数据写入存储卡。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 6. The mobile terminal according to claim 4, wherein,the writing control unit is further configured to stop a detection of the battery cover and/or allow data to be written into the memory card, in case the state detection unit detects that the communication module is under the working state.(String), 7.根据权利要求1所述的移动终端,其中该主体还包括:切换单元,连接天线、写入控制单元和通信模块,用于将天线的工作模式切换为通信模式或检测模式,使得通信模块在通信模式下连接天线。,而写控制单元的输入端口和输出端口在检测模式下通过天线短路连接。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 7. The mobile terminal according to claim 1, wherein the body further comprises:a switching unit connected to the antenna, the writing control unit and the communication module, and configured to switch an operation mode of the antenna into a communication mode or a detection mode, so that the communication module is connected to the antenna under the communication mode, while the input port and the output port of the writing control unit are in short-circuit connection via the antenna under the detection mode.(String), 8.根据权利要求1所述的移动终端,其中,写入控制单元还用于当状态检测单元检测到通信模块不处于工作状态时,控制切换电路切换到检测模式。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 8. The mobile terminal according to claim 1, wherein,the writing control unit is further configured to control the switching circuit to switch into the detection mode, in case the state detection unit detects that the communication module is not under the working state.(String), 9.根据权利要求8所述的移动终端,其中,状态检测单元通过检测天线的信号强度来检测通信模块的工作状态;切换单元还用于当状态检测单元检测到天线的信号强度低于预定阈值或者信号强度的衰减量大于a时,将天线的工作模式切换为检测模式。预定阈值。10、一种移动终端中存储卡写保护的方法、移动终端包含本体、电池和电池盖,本体上设有存储卡座,用于容纳可插拔的存储卡和通信模块,电池盖上设有短路连接件,短路连接件为天线。通信模块,该方法包括:短路形成步骤,当电池盖与本体接合时,通过电池盖上的短路连接件在本体上设置的第一端口和第二端口之间形成短路连接;状态检测步骤,检测通信模块是否处于工作状态;短路检测步骤,通过在第二端口检测第一端口输入的测试信号来判断短路连接是否断开,从而判断电池盖是否脱离本体。和写保护步骤,当确定电池盖被从主体移除时,禁止数据写入存储卡,并且其中,写保护步骤还包括在检测到数据的情况下允许数据写入存储卡通信模块处于工作状态。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 9. The mobile terminal according to claim 8, wherein,the state detection unit detects the working state of the communication module by detecting a signal strength of the antenna;the switching unit is further configured to switch the operation mode of the antenna into the detection mode, in case the state detection unit detects that the signal strength of the antenna is lower than a predetermined threshold or a decrement of the signal strength is larger than a predetermined threshold.(String), 11.根据权利要求10所述的方法,其中写保护步骤还包括:当确定电池盖未从本体上取下时,允许向存储卡写入数据。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 10. A method of write protection for a memory card in a mobile terminal, the mobile terminal comprises a body, a battery and a battery cover, and the body is provided with a memory card socket configured to accommodate a pluggable memory card and a communication module, wherein the battery cover is provided with a short-circuit connecting member that is an antenna of the communication module, the method comprising:a short-circuit forming step that forms a short-circuit connection between a first port and a second port provided on the body, via the short-circuit connecting member on the battery cover when the battery cover is joined with the body;a state detecting step that detects whether the communication module is under a working state;a short-circuit detecting step that determines whether the short-circuit connection is disconnected by detecting at the second port for a test signal input from the first port, so as to determine whether the battery cover is removed from the body; anda write protection step that prohibits data from being written into the memory card when it is determined that the battery cover is removed from the body, and wherein the write protection step further comprises allowing data to be written into the memory card in case it is detected that the communication module is under the working state.(String), 12.根据权利要求1所述的方法,其中,短路检测步骤定期或在存储卡中有数据存储时进行,以防状态检测步骤检测到通信模块不处于工作状态。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 11. The method according to claim 10, wherein the write protection step further comprises: allowing data to be written into the memory card when it is determined that the battery cover is not removed from the body.(String), 13.根据权利要求12所述的方法,还包括:在通信模块处于工作状态期间,当通信模块的天线信号强度低于预定阈值或天线信号强度衰减时,执行短路检测步骤。大于预定阈值。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 12. The method according to claim 1, wherein,the short-circuit detecting step is performed regularly or at a time when there is data to be stored into the memory card, in case it is detected in the state detecting step that the communication module is not under the working state.(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185042(Integer), 13. The method according to claim 12, further comprising:during a period in which the communication module is under the working state, performing the short-circuit detecting step in case a signal strength of the antenna of the communication module is lower than a predetermined threshold or a decrement of the signal strength of the antenna is larger than a predetermined threshold.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.654 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.655 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185042(Integer), TECHNICAL FIELD [0001]The present invention relates to the field of electronic technology, and particularly, to a mobile terminal, and a method of write protection for a memory card in the mobile terminal. DESCRIPTION OF THE RELATED ART [0002]A smartphone with an independent operating system, used like a personal computer, can support the user to self-install programs such as software and games provided by a third party service provider, and can continually extend the functions of the smartphone through such programs. Thus the smartphone becomes more and more popular. Since various software may be self-installed by the user, the memory capacity of the smartphone per se often does not meet the demand for memory space. For this reason, the smartphone is usually provided with a memory card socket, so as to extend the memory space of the smartphone by inserting a pluggable memory card into the memory card socket. Thus, the memory card is of vital importance to the smartphone. In the current market, conventional memory cards for a smartphone, for example, include Multimedia Card (MMC), Secure Digital Memory Card (SD card) and TransFlash (TF) card, in which the SD card includes standard SD card, Elite Pro high speed card, miniSD card (also called as uSD card) and ultra speed SD card, etc. [0003]In some versions (e.g., Android 2.2 and above) of the operating system of a smartphone, application programs in the internal Flash can be written into the memory card. If the memory card is pulled out when a program is being written into the memory card, at least some data will not be successfully written into the memory card during the process of writing the program into the memory card, and a data loss will be caused, which may cause the memory card to be unusable, i.e., there is a risk of corrupting the memory card, and the return rate of the memory card is increased. SUMMARY OF THE INVENTION [0004]The present invention is proposed with respect to the above problem in the prior art. The present invention is related to a mobile terminal and a method of write protection for a memory card in the mobile terminal capable of stopping writing data into the memory card in time when the memory card is pulled out, so as to effectively provide a protection of the writing operation on the memory card. [0005]According to an aspect of the present invention, a mobile terminal is provided, including a body, a battery and a battery cover, wherein the battery cover is provided with a short-circuit connecting member; the body includes: a memory card socket configured to accommodate a pluggable memory card; and a write control unit, when the battery cover is jointed with the body, an input port and an output port of the writing control unit can both electrically contact the short-circuit connecting member, so as to form a short-circuit connection between the input port and the output port; wherein, the writing control unit detects whether the battery cover is removed by outputting a test signal from the output port and detecting the test signal at the input port; it is determined that the battery cover is removed when the test signal is not detected at the input port, and then data is prohibited from being written into the memory card. [0006]According to another aspect, when the test signal is detected at the input port, the writing control unit determines that the battery cover is not removed, and allows data to be written into the memory card. [0007]According to another aspect, the body further includes a communication module. According to another aspect, the short-circuit connecting member is an antenna of the communication module in the mobile terminal. [0008]According to another aspect, the communication module is a Bluetooth module or a Wireless Local Area Network (WLAN) communication module. [0009]According to another aspect, the body further includes a state detection unit configured to detect whether the communication module is under an working state. [0010]According to another aspect, the writing control unit is further configured to detect regularly or at a time when there is data to be stored into the memory card, whether the battery cover is removed, in case the state detection unit detects that the communication module is not under the working state. [0011]According to another aspect, the writing control unit is further configured to stop a detection of the battery cover and/or allow data to be written into the memory card, in case the state detection unit detects that the communication module is under the working state. [0012]According to another aspect, the body further includes a switching unit connected to the antenna, the writing control unit and the communication module, and configured to switch an operation mode of the antenna into a communication mode or a detection mode, so that the communication module is connected to the antenna under the communication mode, while the input port and the output port of the writing control unit are in short-circuit connection via the antenna under the detection mode. [0013]According to another aspect, the body further includes a state detection unit configured to detect whether the communication module is under an working state. [0014]According to another aspect, the writing control unit is further configured to control the switching circuit to switch into the detection mode, in case the state detection unit detects that the communication module is not under the working state. [0015]According to another aspect, the writing control unit stops a detection of the battery cover and/or allows data to be written into the memory card, in case the state detection unit detects that the communication module is under the working state. According to another aspect, the state detection unit detects the working state of the communication module by detecting a signal strength of the antenna; the switching unit is further configured to switch the operation mode of the antenna into the detection mode, in case the state detection unit detects that the signal strength of the antenna is lower than a predetermined threshold or a decrement of the signal strength is larger than a predetermined threshold. [0016]According to another aspect of the present invention, a method of write protection for a memory card in a mobile terminal is provided, the mobile terminal includes a body, a battery and a battery cover, and the body is provided with a memory card socket configured to accommodate a pluggable memory card, wherein the battery cover is provided with a short-circuit connecting member, the method comprising: a short-circuit forming step that forms a short-circuit connection between a first port and a second port provided on the body, via the short-circuit connecting member on the battery cover when the battery cover is jointed with the body; a short-circuit detecting step that determines whether the short-circuit connection is disconnected by detecting at the second port, a test signal input from the first port, so as to determine whether the battery cover is removed from the body; a write protection step that prohibits data from being written into the memory card when it is determined that the battery cover is removed from the body. [0017]According to another aspect, the write protection step further includes: allowing data to be written into the memory card when it is determined that the battery cover is not removed from the body. [0018]According to another aspect, the body further includes a communication module. According to another aspect, the short-circuit connecting member is an antenna of the communication module. [0019]According to another aspect, the method further includes a state detecting step that detects whether the communication module is under an working state. [0020]According to another aspect, the short-circuit detecting step is performed regularly or at a time when there is data to be stored into the memory card, in case it is detected in the state detecting step that the communication module is not under the working state. [0021]According to another aspect, the method further includes: allowing data to be written into the memory card in case it is detected in the state detecting step that the communication module is under the working state [0022]According to another aspect, the method further includes: during a period in which the communication module is under the working state, performing the short-circuit detecting step in case a signal strength of the antenna of the communication module is lower than a predetermined threshold or a decrement of the signal strength of the antenna is larger than a predetermined threshold. [0023]Features described and/or illustrated with respect to one embodiment can be used in one or more other embodiments in a same or similar way, and/or combine with or replace features in other embodiments. To be noted, the term “include/comprise/have” herein refers to existence of feature, component, step and assembly, not excluding existence or addition of one or more other features, components, steps, assemblies or a combination thereof. [0024]Many aspects of the present invention can be understood better with reference to the following drawings. The constituent parts of the drawings are not necessarily drafted in proportion or to scale, but are presented just for illustrating the present invention more clearly. For the convenience of illustrating and describing some parts of the present invention, and promoting the understanding of the embodiments, some parts of the drawings may be enlarged, e.g., enlarging those parts with respect to other parts in an exemplary apparatus practically manufactured according to the present invention. Elements and features described in a drawing or embodiment of the present invention can be combined with elements and features illustrated in one or more other drawings or embodiments. In addition, same or corresponding reference signs are used to represent same or corresponding constituent parts in all the drawings, and they also can be used to represent same or corresponding constituent parts in more than one of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS [0025]The accompanying drawings constitute a part of the specification, illustrate the embodiments of the present invention and together with the description serve to explain the present invention. The drawings described as follows illustrate several exemplary embodiments of the present invention, and a person skilled in the art can obtain other drawings based on these drawings without paying any creative effort. In the drawings: [0026]FIG. 1 is a schematic diagram of a battery cover provided with a short-circuit connecting member in an embodiment of the present invention; [0027]FIG. 2 is a schematic diagram of a battery cover detection apparatus in an embodiment of the present invention; [0028]FIG. 3 is a block diagram of a cell phone in an embodiment of the present invention; [0029]FIG. 4 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; [0030]FIG. 5 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; [0031]FIG. 6 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; [0032]FIG. 7 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; and [0033]FIG. 8 is a flowchart of a write protection method of a memory card in an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0034]These and further aspects and features of the present invention will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the invention have been disclosed in detail as being indicative of some of the ways in which the principles of the invention may be employed, but it is understood that the invention is not limited correspondingly in scope. Rather, the invention includes all changes, modifications and equivalents coming within the spirit and terms of the appended claims. [0035]To be noted, in order to avoid the present invention from being vague due to unnecessary details, the drawings only illustrate device structure and/or processing step closely associated with the solution of the present invention, and other details not so necessary to understand the present invention are omitted. [0036]In the design of some cell phones, the memory card socket is physically provided on an inner side of the battery cover of the cell phone (i.e., the side closer to the battery). Thus, the battery cover would be removed before the memory card is inserted or pulled out. For such designs of the cell phone, the present invention determines whether the memory card has a risk of being pulled out by detecting whether the battery cover is opened (i.e., removed). If the battery cover is not opened, the memory card will not be pulled out, and a program and/or other data can be safely written into the memory card. If the battery cover is opened, the memory card has a risk of being pulled out and the program and other data will be stopped from being written into the memory card, so as to realize a write protection of the memory card in the cell phone. In the embodiment of the present invention, the memory card may be MMC card, SD card, various memory sticks or any other type of pluggable memory card that can be used in the cell phone. [0037]Next, a cell phone will be taken as an example to describe the solution of the present invention that protects the memory card more detailedly. However, it shall be appreciated that the present invention is applicable to not only a cell phone, but also a [0038]PDA and other mobile terminal using a memory card in configuration that the battery cover of such mobile terminals needs to be opened before the memory card is pushed in or pulled out. [0039]Embodiment 1 [0040]In this embodiment, it is detected whether a battery cover of the cell phone is opened through a short-circuit connecting member provided on the battery cover. In this embodiment, the cell phone includes a body, a battery and a battery cover 1001. The battery cover 1001 is provided with a short-circuit connecting member 1002, as illustrated in FIG. 1. The short-circuit connecting member 1002 may be made of a metal material (including a alloy), or a non-metal conductive material such as carbon fiber. The short-circuit connecting member 1002 is preferably, but not limited to, a strip or strap-shaped sheet. It may be bonded onto the battery cover through an adhesive material, or formed on the battery cover through metal insert molding or deposition. For example, the metal sheet 1002 may be provided on the inner surface, the outer surface or the inside of the battery cover. In case of being provided on the outer surface or the inside of the battery cover, the metal sheet 1002 exposes two connecting contact points (also called as connection pads) 1005 on the inner surface of the battery cover. [0041]In this embodiment, the body of the cell phone includes not only a memory card socket (not illustrated) for accommodating the memory card and conventional components (e.g., processor, display, input unit and communication module), but also a writing control unit 120, as illustrated in FIG. 2. The writing control unit 120 includes an output port A1 and an input port A2. When the battery cover is jointed with (e.g., attached to, connected to) the body of the cell phone, the output port A1 and the input port A2 of the writing control unit 120 electrically contact the short-circuit connecting member 1002, so as to form a short-circuit connection between the output port A1 and the input port A2. The output port A1 and the input port A2 may electrically contact the short-circuit connecting member 1002 through terminals 1004 (e.g., but not limited to, pogo pins or spring fingers). When the battery cover 1001 is removed from the body of the cell phone (as illustrated by the dotted line in FIG. 2), the short-circuit connecting member 1002 no longer contacts the output port A1 or the input port A2, thus the short-circuit connection between the output port A1 and the input port A2 is disconnected. [0042]In this embodiment of the present invention, when it is to be detected whether the battery cover is removed, the writing control unit 120 may output a test signal at the output port A1 and detect (i.e., receive) the test signal at the input port A2. The test signal for example may be, but not limited to, square wave, sine wave, triangular wave or sawtooth wave. When the test signal is detected (i.e., received) at the input port A2, it means that the short-circuit connection between the output port A1 and the input port A2 is not disconnected, and thus the battery cover is not removed. When the test signal is not detected (i.e., received) at the input port A2, it means that the short-circuit connection between the output port A1 and the input port A2 is disconnected, and thus the battery cover is removed. In case the battery cover is removed, the user may pull out the memory card. In order to prevent data loss and memory card corrupting caused by writing data into the memory card during the process of pulling out the memory card, the writing control unit 120 prohibits (including stopping) a program or other data from being written into the memory card when it is determined that the battery cover is removed, and allows the program or other data to be written into the memory card when it is determined that the battery cover is not removed. [0043]In FIG. 2, pull-up resistors R1 and R2 may be used to pull up the levels of the ports A1 and A2. The resistances of the pull-up resistors R1 and R2 may be the same or different from each other. For example, the pull-up resistors R1 and R2 may be 5.2 KΩ, respectively. This value is just exemplary, and other values may be set in practice. [0044]In an embodiment of the present invention, the writing control unit 120 may regularly (e.g., at an interval of 0.1 s, 0.5 s or 1 s; these values are just exemplary, and other values may be adopted) send a test signal through the output port A1, determine whether the battery cover is removed by checking whether the test signal is received at the input port A2, and correspondingly control (prohibits or allows) the data such as a program to be written into the memory card. [0045]In another embodiment of the present invention, the writing control unit 120 may be started only when data (e.g., program, application or other data) is to be written into the memory card. The writing control unit 120 sends a test signal through the output port A1, and determines whether the battery cover is removed by checking whether the test signal is received at the input port A2. The writing control unit 120 allows the data to be written into the memory card when it is determined that the battery cover is not removed, or prohibits (including stopping) the data from being written into the memory card when it is determined that the battery cover is removed. [0046]By detecting the battery cover, the writing control unit 120 as mentioned above effectively provides a write protection when the battery cover is opened. Thus, the corrupting of the memory card and the failure in running of an application program caused by the data writing error can be prevented, the data writing security of the memory card is improved, and the return rate of the memory card is effectively reduced. [0047]FIG. 3 is a block diagram of a cell phone 1 in an embodiment of the present invention, including the aforementioned writing control unit 120. This drawing is exemplary and other types of structures may be used to replace the illustrated structure, so as to realize the telecom function or other functions. As illustrated in FIG. 3, the cell phone 1 includes a CPU 100, a communication module 110, a writing control unit 120, an audio processor 130, a memory 140, a camera 150, a display 160, an input unit 180 and a power supply 170. The CPU 100 (sometimes called as a controller or an operation control, and may include a microprocessor or other processor device and/or logic device) receives an input and controls operations of respective parts of the cell phone 1. The input unit 180 provides an input to the CPU 100. The input unit 180 for example is a key or a touch input device. The camera 150 is configured to take image data and provide it to the CPU 100 for a conventional usage, e.g., storage, transmission, etc. [0048]The power supply 170 is configured to supply power to the cell phone 1. The display 160 is configured to display an object to be displayed, such as images and text. The display 160 for example may be, but not limited to, an LCD display. The input unit 180 for example may be the key itself and/or a signal regulating circuit, a decoding circuit or other appropriate circuit that provides the CPU 100 with information for operating one or more keys in a conventional way. The memory 140 is coupled to the CPU 100. The memory 140 may be a solid state memory, e.g., ROM, RAM, SIM card, etc. The memory 140 also may be such a memory that stores information even when the power is off and can be selectively erased and provided with more data. An example of the memory sometimes is called EPROM. The memory 140 further may be a device of other certain type. The memory 140 includes a buffer memory 141 (sometimes called as buffer). The memory 140 may include an application/function storage section 142 configured to store an application program or a function program, or operation flow of the cell phone 1 to be performed through the CPU 100. The memory 140 may further include a data storage section 143 configured to store data, such as contact list, digital data, picture, sound and/or any other data used by the cell phone 1. Various drive programs for performing the communication function of the cell phone 1 and/or other functions (e.g., message transfer application, address list application, etc.) of the cell phone 1 may be included in a drive program storage section 144 of the memory 140. [0049]The communication module 110 is a transmitter/receiver 110 that transmits and receives signals via an antenna 111. The communication module (transmitter/receiver) 110 is coupled to the CPU 100 to provide an input signal and receive an output signal, which may be the same as the case of a conventional cell phone. Based on different communication technologies, a cell phone may be provided with multiple communication modules 110, e.g., cellular network module, bluetooth module and/or Wireless Local Area Network (WLAN) module, etc. The communication module (transmitter/receiver) 110 is also coupled to a loudspeaker 131 and a microphone 132 via an audio processor 130, so as to provide an audio output via the loudspeaker 131 and receives an audio input from the microphone 132, thus the conventional telecom functions can be realized. The audio processor 130 may include any appropriate buffer, decoder, amplifier, etc. In addition, the audio processor 130 is further coupled to the CPU 100, so that a sound recording can be performed on the cell phone through the microphone 132, and the sound stored in the cell phone can be played through the loudspeaker 131. [0050]Embodiment 2 [0051]In the design of some cell phones, the antenna of a communication module such as the Bluetooth module or the WLAN module is provided on the battery cover of the cell phone. Based on such a design of some cell phones, the antenna of the communication module provided on the battery cover is used as the short-circuit connecting member 1002 in this embodiment. [0052]FIG. 4 is a schematic diagram of a battery cover detection apparatus in this embodiment. As illustrated in FIG. 4, the antenna 1003 of the communication module (e.g. [0053]the Bluetooth module or the WLAN module) provided on the battery cover is used as the short-circuit connecting member to perform a short-circuit connection between the output port A1 and the input port A2 of the writing control unit 120. The communication module 110 may be electrically connected to the antenna 1003 through two terminals 1004 (e.g., but not limited to, pogo pins or spring fingers) which also serve as the terminals for an electrical connection from the output port A1 and the input port A2 of the writing control unit 120 to the antenna. That is, the communication module 110 and the writing control unit 120 are connected to the antenna through the common terminals. [0054]Reference is made to FIGS. 4 and 5. As illustrated in FIG. 4, a switching unit 113 is provided between the antenna 1003 and a matching circuit 112 of the communication module 110, and further is connected to the writing control unit 120, so as to switch the operation mode of the antenna 1003 into a communication mode (in which the antenna 1003 is connected to the matching circuit 112) or a detection mode (in which the antenna 1003 is connected to the input and output ports of the writing control unit 120). When the switching unit 113 switches the operation mode of the antenna into the communication mode (as illustrated in FIG. 4), a detection of the open or closed state of the battery cover cannot be carried out, and then it may be deemed that the battery cover detection function is disabled. When the switching unit 113 switches the operation mode of the antenna into the detection mode (as illustrated in FIG. 5), the detection of the open or closed state of the battery cover can be carried out, and then it may be deemed that the battery cover detection function is enabled. In an embodiment of the present invention, the writing control unit 120 may enable the switching unit 113 through a pin A3, so as to control the switching unit 113 to switch between the communication mode and the detection mode. [0055]In case the communication module is under a working state, the antenna is under the communication mode and is being used. Since the antenna is provided on the battery cover, it can be determined that the battery cover is certainly in a closed state, i.e., jointed with the body of the cell phone. Thus, it is unnecessary to detect the battery cover at that time, and the writing control unit 120 may allow the data such as a program to be written into the memory card when the communication module is under the working state. In order to detect the working state of the communication module, the cell phone is further provided with a state detection unit 121 connected to the communication module and the writing control unit 120 or disposed in any one of the communication module and the writing control unit (FIG. 4 illustrates the case that the state detection unit 121 is disposed in the writing control unit), so as to detect whether the communication module is in the working state. When the state detection unit 121 detects that the communication module is in the working state, the writing control unit 120 no longer detects the state of the battery cover. In an embodiment of the present invention, the state detection unit 121 may detect the working state of the communication module by detecting the antenna signal quality (e.g., antenna signal strength, etc.) in the communication module or other parameter indicating that the antenna is being used. [0056]In an embodiment of the present invention, when the state detection unit 121 detects that the communication module is not in the working state, the writing control unit 120 may control the switching unit 113 through the pin A3 to switch into the detection mode regularly (e.g., at an interval of 1 s (i.e., 1 second), 2 s, 3 s or other value), i.e., to enable the detection function for the battery cover. During a period in which the detection function is enabled, the writing control unit 120 may constantly or regularly (e.g., at an interval of 0.25 s, 0.5 s, 1 s or other value) send a test signal through the output port A1, determine whether the battery cover is removed by checking whether the test signal is received at the input port A2, and correspondingly control (prohibits or allows) the data such as a program to be written into the memory card. [0057]In another embodiment of the present invention, in case the state detection unit 121 detects that the communication module is not in the working state, the writing control unit 120 may control the switching unit 113 through the pin A3 to switch into the detection mode only when data (e.g., program, application or other data) is to be written into the memory card, so that the writing control unit 120 detects whether the battery cover is removed, and correspondingly controls (prohibits or allows) the data such as a program to be written into the memory card. [0058]Further, during a period in which the communication module is under the working state, there is a possibility that the antenna and the communication module may be disconnected from each other when the state detection unit 121 detects that the connection between the communication module and the network suddenly becomes worse, for example the signal quality declines sharply, e.g., the antenna signal strength is lower than a predetermined threshold (for example, but not limited to, −90 dBm) or the is variation of the antenna signal strength (for example the variation (decrement) between two antenna signal strengths detected successively) is larger than a predetermined threshold (for example, but not limited to, 20 dB). In that case, the writing control unit 120 may control the switching unit 113 through the pin A3 to switch into the detection mode, so as to detect whether the battery cover is removed, and correspondingly control (prohibits or allows) the data such as a program to be written into the memory card. [0059]When the communication module 110 is to be used again for a communication, the communication module 110 may send an instruction signal to the writing control unit 120, which enables the switching unit 113 through the pin A3 to switch from the detection mode into the communication mode, so that the communication module 110 performs a communication through the antenna, and the writing control unit 120 stops detecting the battery cover at that time. [0060]This embodiment also provides a write protection for the memory card, so as to prevent the corrupting of the memory card and a failure in running of an application program caused by a data writing error, improve the data writing security of the memory card, and effectively reduce the return rate of the memory card. [0061]In another embodiment of the present invention, alternatively, the communication module 110 and the writing control unit 120 may be connected to the antenna through their respective terminals instead of the common terminals, so as to realize the communication function and the battery cover detection function, respectively, as illustrated in FIG. 6. In that case, the switching unit 113 and the pin A3 of the writing control unit 120 may be omitted. But the working state of the communication module 110 still can be detected through the state detection unit 121. In case the communication module 110 is under the working state, the writing control unit 120 may allow the data such as a program to be written into the memory card; while in case the communication module 110 is not under the working state, the writing control unit 120 may detect regularly (e.g., periodically) or at a time when there is data to be written into the memory card, whether the battery cover is removed and correspondingly control (prohibit or allow) the data such as a program to be written into the memory card. [0062]In another embodiment of the invention, the antenna 111 of the communication module 110 and the short-circuit connecting member 1002, which establishes a short-circuit connection between the output port A1 and the input port A2 of the writing control unit 120, may be separately provided at different positions on the battery cover 1001. In that case, the communication module 110 and the short-circuit connecting member 1002 may independently realize their respective functions, i.e., the communication function and the battery cover detection function, as illustrated in FIG. 7. [0063]Alternatively, the writing control unit 120 may be connected to the communication module 110 through the state detection unit 121, so that the writing control unit 120, according to the detection of the sta(String), 技术领域 [0001] 本发明涉及电子技术领域,具体涉及一种移动终端及移动终端中存储卡的写保护方法。 相关技术的描述 [0002] 具有独立操作系统的智能手机,像个人电脑一样使用,可以支持用户自行安装第三方服务商提供的软件、游戏等程序,并可以通过这些程序不断扩展智能手机的功能。 因此,智能手机变得越来越流行。 由于用户可能会自行安装各种软件,因此智能手机本身的内存容量往往不能满足内存空间的需求。 为此,智能手机通常设置有存储卡插槽,通过在存储卡插槽中插入可插拔的存储卡来扩展智能手机的存储空间。 因此,存储卡对于智能手机来说至关重要。 在目前市场上,传统的智能手机存储卡,例如,包括多媒体卡(MMC)、安全数字存储卡(SD卡)和TransFlash(TF)卡,其中SD卡包括标准SD卡、Elite Pro high speed卡、miniSD卡(也称uSD卡)和超高速SD卡等。 [0003] 在某些版本的智能手机操作系统(如Android 2.2及以上)中,可以将内部Flash中的应用程序写入存储卡中。 如果在向存储卡写入程序的过程中拔出存储卡,在向存储卡写入程序的过程中,至少会有部分数据无法成功写入存储卡,造成数据丢失 ,这可能会导致存储卡无法使用,即存在损坏存储卡的风险,增加了存储卡的退货率。 发明内容 [0004] 本发明是针对现有技术中存在的上述问题而提出的。 本发明涉及一种移动终端及移动终端中存储卡的写保护方法,能够在存储卡被拔出时及时停止向存储卡写入数据,从而有效地提供对存储卡的保护。 对存储卡的写入操作。 [0005] 根据本发明的一个方面,提供了一种移动终端,包括本体、电池和电池盖,所述电池盖上设置有短路连接件; 主体包括:存储卡插槽,用于容纳可插拔的存储卡; 以及写入控制单元,当电池盖与本体接合时,写入控制单元的输入端口和输出端口均能够电接触短路连接件,从而在电池盖与本体之间形成短路连接。 输入端口和输出端口; 其中,写入控制单元通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除。 当输入端口未检测到测试信号时,判断为取下电池盖,禁止向存储卡写入数据。 [0006] 根据另一方面,当在输入端口检测到测试信号时,写入控制单元确定电池盖未被移除,并允许数据写入存储卡。 [0007] 根据另一方面,主体还包括通信模块。 根据另一方面,短路连接件是移动终端中的通信模块的天线。 [0008] 根据另一方面,通信模块是蓝牙模块或无线局域网(WLAN)通信模块。 [0009] 根据另一方面,本体还包括状态检测单元,用于检测通信模块是否处于工作状态。 [0010]另一方面,所述写入控制单元还用于在所述状态检测单元检测到所述通信模块被关闭时,定期或在有数据需要存储到所述存储卡时检测所述电池盖是否被移除。 不在工作状态。 [0011] 根据另一方面,写入控制单元还用于当状态检测单元检测到通信模块处于工作状态时,停止检测电池盖和/或允许数据写入存储卡。 [0012] 根据另一方面,本体还包括切换单元,连接到天线、写入控制单元和通信模块,用于将天线的工作模式切换为通信模式或检测模式,使得通信模块 在通信模式下,与天线相连,而在检测模式下,写入控制单元的输入端口和输出端口通过天线短接。 [0013] 根据另一方面,本体还包括状态检测单元,用于检测通信模块是否处于工作状态。 [0014] 根据另一方面,写入控制单元还用于当状态检测单元检测到通信模块不处于工作状态时,控制切换电路切换到检测模式。 [0015] 根据另一方面,当状态检测单元检测到通信模块处于工作状态时,写入控制单元停止检测电池盖和/或允许数据写入存储卡。 根据另一方面,状态检测单元通过检测天线的信号强度来检测通信模块的工作状态; 切换单元还用于当状态检测单元检测到天线的信号强度低于预定阈值或者信号强度的衰减量大于a时,将天线的工作模式切换为检测模式。 预定阈值。 [0016] 根据本发明的另一个方面,提供了一种移动终端中存储卡的写保护方法,该移动终端包括本体、电池和电池盖,本体上设置有存储卡插槽,该插槽配置有 容纳可插拔存储卡,其中,电池盖设有短路连接件,该方法包括: 短路形成步骤,在主体上设置的第一端口和第二端口之间形成短路连接 、电池盖与本体接合时通过电池盖上的短路连接件; 短路检测步骤,通过在第二端口检测第一端口输入的测试信号,判断短路连接是否断开,从而判断电池盖是否脱离本体。 写保护步骤,当确定电池盖已从机体上取下时,禁止数据写入存储卡。 [0017] 根据另一个方面,写保护步骤还包括:当确定电池盖未从本体移除时,允许将数据写入存储卡。 [0018] 根据另一方面,主体还包括通信模块。 根据另一方面,短路连接件是通信模块的天线。 [0019] 根据另一方面,该方法还包括状态检测步骤,检测通信模块是否处于工作状态。 [0020] 根据另一方面,短路检测步骤定期或在存储卡中有数据存储时执行,以防状态检测步骤检测到通信模块不处于工作状态 . [0021]另一方面,该方法还包括:当状态检测步骤检测到通信模块处于工作状态时,允许向存储卡写入数据。 [0022] 根据另一个方面,该方法还包括:在通信模块处于工作状态期间,当通信模块的天线的信号强度低于预定阈值时,执行短路检测步骤,或者 天线信号强度的衰减量大于预定阈值。 [0023] 关于一个实施例描述和/或图示的特征可以相同或相似的方式用于一个或多个其他实施例,和/或与其他实施例中的特征组合或替换。 需要说明的是,此处的术语“包括/包含/具有”是指特征、组件、步骤和组件的存在,不排除存在或添加一个或多个其他特征、组件、步骤、组件或其组合。 [0024] 参考以下附图可以更好地理解本发明的许多方面。 附图的组成部分不一定按比例或比例绘制,只是为了更清楚地说明本发明而呈现。 为了便于说明和描述本发明的某些部分,以及促进对实施例的理解,附图中的某些部分可能被放大,例如,相对于根据实施例实际制造的示例性装置中的其他部分放大这些部分 本发明。 本发明的附图或实施例中描述的元素和特征可以与一个或多个其他附图或实施例中所示的元素和特征组合。 另外,在所有附图中,相同或相应的附图标记用于表示相同或相应的组成部分,也可以在一个以上的实施例中使用相同或相应的附图标记来表示相同或相应的组成部分。 附图的简要说明 [0025] 附图构成说明书的一部分,用于说明本发明的实施例,并与说明书一起用于解释本发明。 以下所描述的附图为本发明的几个优选实施例,本领域技术人员在不付出创造性劳动的情况下,基于这些附图所获得的其他附图。 在图纸中: [0026] 图1为本发明实施例中设置有短路连接件的电池盖的示意图; [0027] 图2为本发明实施例的电池盖检测装置的示意图; [0028] 图3是本发明实施例中手机的框图; [0029] 图4为本发明另一实施例的电池盖检测装置的示意图; [0030] 图5为本发明另一实施例的电池盖检测装置的示意图; [0031] 图6为本发明另一实施例的电池盖检测装置的示意图; [0032] 图7为本发明另一实施例的电池盖检测装置的示意图; 和 [0033] 图8为本发明实施例的存储卡写保护方法的流程图。 优选实施例的详细说明 [0034] 参考以下描述和附图,本发明的这些和进一步的方面和特征将是显而易见的。 在描述和附图中,本发明的特定实施例已经被详细地公开为指示可以采用本发明的原理的一些方式,但是应当理解本发明不相应地限制在范围上。 相反,本发明包括落入所附权利要求的精神和条款内的所有变化、修改和等同物。 [0035]需要说明的是,为避免不必要的细节使本发明含糊不清,附图仅说明与本发明方案密切相关的装置结构和/或工艺步骤,其他细节对理解本发明不是必需的。 发明省略。 [0036] 在一些手机的设计中,存储卡插槽物理上设置在手机电池盖的内侧(即靠近电池的一侧)。 因此,在插入或拔出存储卡之前,电池盖将被移除。 对于这样的手机设计,本发明通过检测电池盖是否被打开(即取下)来判断存储卡是否存在被拔出的风险。 如果不打开电池盖,则不会拔出存储卡,可以安全地将程序和/或其他数据写入存储卡。 如果电池盖被打开,存储卡有被拔出的风险,程序和其他数据将停止写入存储卡,从而实现手机中存储卡的写保护。 在本发明实施例中,存储卡可以是MMC卡、SD卡、各种记忆棒或者其他任何一种可以在手机中使用的可插拔存储卡。 [0037] 下面以手机为例,对本发明保护存储卡的方案进行更详细的说明。 然而,应当理解,本发明不仅适用于手机,还适用于 [0038] PDA等使用存储卡的移动终端的配置是,在推入或拔出存储卡之前需要打开电池盖。 [0039] 实施例一 [0040] 在本实施例中,通过设置在电池盖上的短路连接件来检测手机电池盖是否被打开。 在本实施例中,手机包括机身、电池和电池盖。 1001 . 电池盖 1001 设有短路连接件 1002 ,如图1所示。短路连接件 1002 可以由金属材料(包括合金)或碳纤维等非金属导电材料制成。 短路连接件 1002 优选但不限于条状或带状片材。 它可以通过粘合材料粘合到电池盖上,或者通过金属嵌件成型或沉积形成在电池盖上。 例如,金属板 1002 可以设置在电池盖的内表面、外表面或内侧。 如果设置在电池盖的外表面或内侧,金属片 1002 暴露两个连接触点(也称为连接垫) 1005 在电池盖的内表面上。 [0041] 在本实施例中,手机的机身不仅包括用于容纳存储卡和常规部件(例如处理器、显示器、输入单元和通信模块)的存储卡插槽(未示出),还包括写入控制单元。 120 ,如图2所示。写入控制单元 120 包括一个输出端口A 1 和一个输入端口A 2 . 当电池盖与手机机身接合(如贴附、连接)时,输出端口A 1 和输入端口A 2 写控制单元 120 电接触短路连接件 1002 ,从而形成输出端口A之间的短路连接 1 和输入端口A 2 . 输出口A 1 和输入端口A 2 可以电接触短路连接件 1002 通过终端 1004 (例如但不限于弹簧针或弹簧夹)。 当电池盖 1001 从手机机身上取下(如图2中虚线所示),短路连接件 1002 不再接触输出端口A 1 或输入端口A 2 ,因此输出端口A之间的短路连接 1和输入端口A 2 已断开连接。 [0042] 本发明实施例中,当检测电池盖是否被取下时,写入控制单元 120 可在输出端口A输出测试信号 1 检测(即接收)输入端口A的测试信号 2 . 测试信号例如可以是但不限于方波、正弦波、三角波或锯齿波。 当在输入端口 A 检测到(即接收到)测试信号时 2 ,这意味着输出端口A之间的短路连接 1 和输入端口A 2 未断开,因此电池盖未取下。 当在输入端口 A 未检测到(即接收到)测试信号时 2 ,这意味着输出端口A之间的短路连接 1 和输入端口A 2 断开连接,从而取下电池盖。 如果取下电池盖,用户可以拔出存储卡。 为了防止在拔出存储卡的过程中向存储卡写入数据而导致数据丢失和损坏存储卡,写入控制单元 120 禁止(包括停止)在确定电池盖被移除时将程序或其他数据写入存储卡,并在确定电池盖被移除时允许程序或其他数据写入存储卡 没有被删除。 [0043] 图2中,上拉电阻R 1 和R 2 可用于拉高端口 A 的电平 1 和一个 2 . 上拉电阻R的阻值 1 和R 2 可以彼此相同或不同。 例如,上拉电阻 R 1 和R 2 可能分别为 5.2 KΩ。 该值只是示例性的,实际中还可以设置其他值。 [0044] 在本发明的一个实施例中,写入控制单元 120 可以有规律地(例如,以0.1s、0.5s或1s的间隔;这些值只是示例性的,可以采用其他值)通过输出端口A发送测试信号 1 ,通过检查输入端口A是否收到测试信号来判断电池盖是否被取下 2 ,并相应地控制(禁止或允许)将程序等数据写入存储卡。 [0045] 在本发明的另一个实施例中,写入控制单元 120 仅当数据(例如,程序、应用程序或其他数据)要写入存储卡时才可启动。 写入控制单元 120 通过输出端口A发送测试信号 1 ,通过检测输入端口A是否接收到测试信号来判断电池盖是否被移除 2 . 写入控制单元 120 当确定电池盖未被取下时允许数据写入存储卡,或者当确定电池盖被取下时禁止(包括停止)数据写入存储卡。 [0046] 通过检测电池盖,写控制单元 120 如上所述,当电池盖打开时,有效地提供了写保护。 从而可以防止数据写入错误导致存储卡损坏和应用程序无法运行,提高了存储卡数据写入的安全性,有效降低了存储卡的报废率。 [0047] 图3是手机的框图 1 在本发明的一个实施例中,包括上述的写入控制单元 120 . 该图是示例性的,可以用其他类型的结构代替所示结构,以实现电信功能或其他功能。 如图3所示,手机 1 包括一个中央处理器 100 , 通信模块 110 , 一个写控制单元 120 , 音频处理器 130 , 一段记忆 140 , 相机 150 , 一个显示器 160 , 一个输入单元 180 和电源 170 . 中央处理器 100(有时称为控制器或操作控制器,可能包括微处理器或其他处理器设备和/或逻辑设备)接收输入并控制手机各部分的操作 1 . 输入单元 180 向 CPU 提供输入 100 . 输入单元 180 例如是按键或触摸输入设备。 相机 150 配置为获取图像数据并将其提供给 CPU 100 用于常规用途,例如存储、传输等。 [0048] 电源 170 配置为手机供电 1 . 显示器 160 用于显示待显示对象,例如图片、文字等。 显示器 160 例如可以是但不限于LCD显示器。 输入单元 180 例如可以是钥匙本身和/或信号调节电路、解码电路或提供CPU的其他适当电路 100 具有以常规方式操作一个或多个键的信息。 记忆 140 耦合到CPU 100 . 记忆 140 可以是固态存储器,例如 ROM、RAM、SIM 卡等。存储器 140 也可以是这样的存储器,即使在电源关闭时也能存储信息,并且可以选择性地擦除并提供更多数据。 存储器的一个例子有时称为 EPROM。 记忆 140 进一步可能是其他某种类型的设备。 记忆 140 包括一个缓冲存储器 141 (有时称为缓冲区)。 记忆 140 可能包括一个应用程序/功能存储部分 142 用于存储应用程序或功能程序,或手机的操作流程 1 通过CPU执行 100 . 记忆 140 还可以包括数据存储部分 143 配置为存储数据,例如联系人列表、数字数据、图片、声音和/或手机使用的任何其他数据 1 . 执行手机通信功能的各种驱动程序 1 和/或手机的其他功能(例如,消息传输应用程序、地址列表应用程序等) 1 可以包含在驱动程序存储部分中 144 记忆的 140 . [0049] 通信模块 110 是一个发射器/接收器 110 通过天线发送和接收信号 111 . 通信模块(发射器/接收器) 110 耦合到CPU 100 提供输入信号和接收输出信号,可以与传统手机的情况相同。 基于不同的通信技术,一部手机可以配备多个通信模块 110 ,例如,蜂窝网络模块、蓝牙模块和/或无线局域网 (WLAN) 模块等。 通信模块(发射器/接收器) 110 也耦合到扬声器 131 和麦克风 132 通过音频处理器 130 ,以便通过扬声器提供音频输出 131 并接收来自麦克风的音频输入 132 ,从而实现常规的电信功能。 音频处理器 130 可能包括任何适当的缓冲器、解码器、放大器等。此外,音频处理器 130 进一步耦合到CPU 100 ,这样就可以通过麦克风在手机上进行录音 132 ,并且可以通过扬声器播放手机中存储的声音 131 . [0050] 实施例二 [0051] 在一些手机的设计中,蓝牙模块或WLAN模块等通信模块的天线设置在手机的电池盖上。 基于一些手机的这种设计,将设置在电池盖上的通信模块的天线用作短路连接件 1002 在这个实施例中。 [0052] 图4为本实施例的电池盖检测装置的示意图。 如图 4 所示,天线 1003 通信模块(例如 [0053]设置在电池盖上的蓝牙模块或WLAN模块)作为短路连接件,将输出端口A之间进行短路连接 1 和输入端口A 2 写控制单元 120 . 通信模块 110 可以电连接到天线 1003 通过两个终端 1004 (例如,但不限于弹簧针或弹簧夹),它们也用作输出端口 A 的电气连接端子 1 和输入端口A 2 写控制单元 120 到天线。 即通信模块 110 和写控制单元 120 通过公共端子连接到天线。 [0054] 参考图4和图5。如图4所示,切换单元 113 天线之间提供 1003 和匹配电路 112 通信模块 110 ,进一步连接到写控制单元 120 ,从而切换天线的工作模式 1003 进入通信模式(其中天线 1003 连接到匹配电路 112 )或检测模式(其中天线 1003 接写控制单元的输入输出端口 120 ). 当切换单元 113 将天线的工作模式切换为通信模式(如图4所示),则无法进行电池盖开启或关闭状态的检测,则可认为电池盖检测功能被关闭 . 当切换单元 113 将天线的工作模式切换为检测模式(如图5所示),即可进行电池盖打开或关闭状态的检测,则可认为电池盖检测功能已启用 . 在本发明的一个实施例中,写入控制单元 120 可以启用开关单元 113 通过引脚 A 3 ,从而控制开关单元 113 在通信模式和检测模式之间切换。 [0055] 在通信模块处于工作状态的情况下,天线处于通信模式并且正在被使用。 由于天线设置在电池盖上,因此可以确定电池盖肯定处于闭合状态,即与手机机身接合。 因此,此时无需检测电池盖,写入控制单元 120 可以允许通信模块在工作状态下将程序等数据写入存储卡。 为了检测通信模块的工作状态,手机还设置有状态检测单元 121 连接通讯模块和写控制单元 120 或者设置在通信模块和写控制单元中的任一个(图4说明了状态检测单元的情况 121 设置于写入控制单元),以检测通信模块是否处于工作状态。 当状态检测单元 121 检测到通信模块处于工作状态,写入控制单元 120 不再检测电池盖的状态。 在本发明的一个实施例中,状态检测单元 121 可以通过检测通信模块中的天线信号质量(例如,天线信号强度等)或其他指示天线正在使用的参数来检测通信模块的工作状态。 [0056] 在本发明的一个实施例中,当状态检测单元 121 检测到通讯模块不在工作状态,写入控制单元 120 可以控制开关单元 113 通过引脚 A 3 定时切换到检测模式(如间隔1s(即1秒)、2s、3s或其他值),即开启电池盖检测功能。 在启用检测功能期间,写入控制单元 120可以不断地或有规律地(例如,以0.25s、0.5s、1s或其他值的间隔)通过输出端口A发送测试信号 1 ,通过检查输入端口A是否收到测试信号来判断电池盖是否被取下 2 ,并相应地控制(禁止或允许)将程序等数据写入存储卡。 [0057] 在本发明的另一个实施例中,如果状态检测单元 121 检测到通讯模块不在工作状态,写入控制单元 120 可以控制开关单元 113 通过引脚 A 3 只有当数据(例如,程序、应用程序或其他数据)被写入存储卡时才切换到检测模式,使得写入控制单元 120 检测电池盖是否被取下,并相应控制(禁止或允许)向存储卡写入程序等数据。 [0058] 进一步地,在通信模块处于工作状态期间,状态检测单元有可能导致天线与通信模块断开连接。 121 检测到通信模块与网络的连接突然变差,例如信号质量急剧下降,例如天线信号强度低于预定阈值(例如但不限于-90dBm)或 是天线信号强度的变化量(例如连续检测到的两个天线信号强度之间的变化量(减量))大于预定阈值(例如但不限于20dB)。 在这种情况下,写入控制单元 120 可以控制开关单元 113 通过引脚 A 3 切换到检测模式,检测电池盖是否被取下,并相应地控制(禁止或允许)向存储卡写入程序等数据。 [0059] 当通信模块 110 再次用于通信,通信模块 110 可以向写控制单元发送指令信号 120 ,这使得开关单元 113 通过引脚 A 3 从检测模式切换到通信模式,使通信模块 110 通过天线进行通信,写控制单元 120 那时停止检测电池盖。 [0060] 本实施例还对存储卡进行了写保护,以防止数据写入错误导致存储卡损坏和应用程序无法运行,提高了存储卡数据写入的安全性,有效地 降低存储卡的退货率。 [0061] 在本发明的另一个实施例中,可选地,通信模块 110 和写控制单元 120 可以通过各自的端子而不是公共端子连接到天线,从而分别实现通信功能和电池盖检测功能,如图6所示。在这种情况下,切换单元 113 和引脚A 3 写控制单元 120 可以省略。 但通讯模块的工作状态 110 仍然可以通过状态检测单元进行检测 121 . 万一通信模块 110 处于工作状态,写控制单元 120 可以允许将程序等数据写入存储卡; 而万一通信模块 110 不在工作状态下,写控制单元 120 可以定时(例如周期性)或在有数据写入内存卡时检测电池盖是否被取下,并相应地控制(禁止或允许)程序等数据写入内存 卡片。 [0062] 在本发明的另一个实施例中,天线 111 通信模块 110 和短路连接件 1002 ,它建立了输出端口A之间的短路连接1 和输入端口A 2 写控制单元 120 , 可分别设置在电池盖上的不同位置 1001 . 在这种情况下,通信模块 110 和短路连接件 1002 可以独立实现各自的功能,即通信功能和电池盖检测功能,如图7所示。 [0063] 或者,写控制单元 120 可以连接到通信模块 110 通过状态检测单元 121 , 使写控制单元 120 , 根据状态检测单元的检测 121 ,允许将程序等数据写入存储卡中,以防通信模块 110 处于工作状态,而万一通信模块 110 不在工作状态下,写控制单元 120 定时(例如周期性地)或在有数据写入存储卡时,检测电池盖是否被取下,并相应地控制(禁止或允许)向存储卡写入程序等数据 . 状态检测单元 121 可以连接到通信模块 110 和写控制单元 120 ,或设置于任一通讯模块 110 和写控制单元 120 . 或者,当通信模块的天线 110 和短路连接件 1002 单独提供,通信模块的天线 110 可以设置在手机机身上的其他位置,而不是在电池盖上。 下面结合上述手机的结构,对本发明实施例的存储卡的写保护方法进行说明。 如图8所示,存储卡的写保护可以通过以下步骤实现: [0064] 小号 800 :短路形成步骤,在第一端口(例如,输出端口A)之间形成短路连接 1 )和第二个端口(例如,输入端口A 2 ) 设置在手机机身上,当电池盖与机体接合(例如,附接至、连接至)时,通过电池盖上的短路连接件。 [0065] 短路连接件例如可以是金属片或其他导电片。 在本发明的一个实施例中,短路连接件为手机的通信模块(例如蓝牙模块或WLAN通信模块)的天线。 [0066] 小号 804 :短路检测步骤,通过在第二端口检测第一端口输入的测试信号,判断短路连接是否断开,从而判断电池盖是否脱离本体。 当第二端口检测不到来自第一端口的测试信号时,判断短路连接断开; 当第二端口检测到来自第一端口的测试信号时,判断短路连接没有断开,电池盖没有从手机机身上取下。 [0067] 小号 806 :写保护步骤,当短路检测步骤判断为电池盖脱离本体时,禁止(包括停止)向存储卡写入数据。 [0068] 这样可以防止拔出存储卡时数据写入错误导致存储卡损坏和应用程序无法运行,提高了存储卡数据写入的安全性,并且 有效降低存储卡的退货率。 [0069] 该方法还可以包括:S 808 ,当在短路检测步骤中确定电池盖未从机体上移除时,允许将数据写入存储卡。 [0070] 如果短路连接件为手机中通信模块的天线,则在S之前,该方法还可以包括以下步骤: 804 : [0071] 小号 802 :状态检测步骤,检测通信模块是否处于工作状态。 [0072] 例如,可以通过检测天线的信号强度来检测通信模块的工作状态: [0073] 在那种情况下,短路检测步骤S 804 如果在状态检测步骤中确定通信模块不处于工作状态,则定时或在有数据写入存储卡时执行。 [0074] 该方法还可以包括: [0075] 小号 803 :若状态检测步骤判断通信模块处于工作状态,则停止检测电池盖和/或允许数据写入存储卡。 [0076] 在本发明的一个实施例中,该方法还可以包括:步骤S 805 :在通信模块处于工作状态期间,执行短路检测步骤S 804 当通信模块的天线的信号强度低于预定阈值或天线信号强度的衰减量大于预定阈值时。 [0077] 本发明的方法并不局限于按照这里描述的时间顺序执行,可以按照其他时间顺序依次执行、并发执行或独立执行。 因此,此处描述的方法的执行顺序不构成对本发明技术范围的限制。 [0078] 上述描述和附图说明了本发明的各种不同特征。 应当理解,本领域的技术人员可以通过编写适当的计算机代码来实现上述描述和图示的步骤和过程。 [0079] 在此公开了本发明的实施例。 本领域的技术人员很容易认识到本发明在其他环境下还有其他应用。 事实上,还存在许多其他的实施例和实现方式。 所附权利要求并不旨在将本发明的范围限制为上述实施例。 [0080] 关于一个实施例描述和/或图示的特征可以相同或相似的方式用于一个或多个其他实施例,和/或与其他实施例中的特征组合或替换。 [0081] 应当理解,本发明实施例的多个部分可以通过硬件、软件、固件或其组合来实现。 在上述实施例中,多个步骤或方法可以通过存储在存储器中并由适当的指令执行系统执行的软件或固件来实现。 例如,如果通过硬件实现,例如在替代实施例中,可以通过组合以下现有技术中的任何一种或组合来实现:分立逻辑电路,具有用于实现数字信号的逻辑功能的逻辑门电路, 具有适当组合逻辑门电路、可编程门阵列(PGA)、现场可编程门阵列(FPGA)等的专用集成电路(ASIC)。 [0082] 当上述方法中的全部或部分步骤是通过程序指令相关硬件实现时,该程序可以存储在计算机可读取存储介质中,例如ROM/RAM、磁盘、光盘等。 [0083] 流程图或其他方式所描述的任何过程或方法描述或方框,都可以理解为包括一个或多个用于实现特定逻辑功能或过程步骤中可执行指令的代码的模块、段或部分,以及优选实施例的范围 还包括其他实现方式,其中功能可以不同于所示出或讨论的顺序执行,包括基于相关功能的基本同时的方式或相反的顺序,并且这是本领域技术人员应当理解的。 [0084]以上实施例对本发明的目的、技术方案及有益效果进行了进一步详细的说明。 应当理解,以上所述仅为本发明的实施例而已,并不用于限定本发明的保护范围。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.672 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.673 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102682830A(String), CN102682830B(String), US20120231730A1(String), US8731625B2(String), WO2012123792A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.674 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102682830A(String), CN102682830B(String), US20120231730A1(String), US8731625B2(String), WO2012123792A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.675 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8731625B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.682 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102682830A(String), CN102682830B(String), US20120231730A1(String), US8731625B2(String), WO2012123792A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270717(Integer), CN102682830A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270717(Integer), CN102682830B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.704 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270717(Integer), US20120231730A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270717(Integer), US8731625B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.724 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270717(Integer), WO2012123792A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.739 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8731625B2(String), US8731625B2(String), 1400515200(Integer), 270717(Integer), 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.751 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY MOBILE COMMUNICATIONS AB(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼移动通信株式会社(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SONY MOBILE COMMUNICATIONS AB(String), 索尼移动通信株式会社(String), 0(Integer), 1681975568(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.764 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185042(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 185042(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.775 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75959(Integer), 1(Integer), 185042(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.786 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1681975544(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185042(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75924(Integer), 2(Integer), 185042(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.800 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.802 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.815 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.816 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.818 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费 | 权利转移(String), 2(Integer), 185042(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10382204B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal privacy protection method and protection apparatus, and mobile terminal(String), 移动终端隐私保护方法、保护装置、移动终端(String), US10382204B2(String), A mobile terminal privacy protection method and protection apparatus, and a mobile terminal, where the method includes obtaining an application start instruction, actively obtaining a biometric feature of a user according to the application start instruction, and displaying an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature. The encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. Hence, the present disclosure can protect privacy in the mobile terminal without being easily perceived.(String), 一种移动终端隐私保护方法、保护装置及移动终端,该方法包括:获取应用启动指令,根据应用启动指令主动获取用户的生物特征,显示加密内容列表和未加密内容 如果获取的用户的生物特征与预设的生物特征匹配,则对应的应用程序列表。 应用程序的加密内容列表是根据应用程序中的加密内容生成的,应用程序的未加密内容列表是根据应用程序中的未加密内容生成的,应用程序中的加密内容是获取时未呈现的内容 用户的生物特征与预设的生物特征不匹配。 因此,本公开可以保护移动终端中的隐私而不易被察觉。(String), US15/561344(String), 1427731200(Integer), US10382204B2(String), 1565625600(Integer), 1565625600(Integer), 美国(String), 4(Integer), 10(Integer), 33(Integer), CN102467462A | CN102880560A | CN102902935A | CN103427990A | CN103581417A | CN103605459A | CN104239107A | CN104239778A | EP2713298A1 | JP1995092908A | JP2001051987A | JP2002259081A | JP2010541046A | JP2011509459A | JP2013152641A | JP2014514654A | JP2015021363A | JPWO2014077213A1 | US20070113097A1 | US20090083847A1 | US20090210722A1 | US20110072264A1 | US20120252411A1 | US20120291121A1 | US20130318625A1 | US20140085460A1 | US20140095870A1 | US20140292666A1 | US20140298268A1 | US20160042166A1 | US20160212103A1 | US4775595A(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185043(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8e3c442330934eb382cb6a19c0c6eee5.png(String), 185043(Integer), 8e3c442330934eb382cb6a19c0c6eee5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.849 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.851 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal privacy protection method and protection apparatus, and mobile terminal(String), 移动终端隐私保护方法、保护装置、移动终端(String), US10382204B2(String), A mobile terminal privacy protection method and protection apparatus, and a mobile terminal, where the method includes obtaining an application start instruction, actively obtaining a biometric feature of a user according to the application start instruction, and displaying an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature. The encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. Hence, the present disclosure can protect privacy in the mobile terminal without being easily perceived.(String), 一种移动终端隐私保护方法、保护装置及移动终端,该方法包括:获取应用启动指令,根据应用启动指令主动获取用户的生物特征,显示加密内容列表和未加密内容 如果获取的用户的生物特征与预设的生物特征匹配,则对应的应用程序列表。 应用程序的加密内容列表是根据应用程序中的加密内容生成的,应用程序的未加密内容列表是根据应用程序中的未加密内容生成的,应用程序中的加密内容是获取时未呈现的内容 用户的生物特征与预设的生物特征不匹配。 因此,本公开可以保护移动终端中的隐私而不易被察觉。(String), US15/561344(String), 1427731200(Integer), US10382204B2(String), 1565625600(Integer), 1565625600(Integer), 美国(String), 3(Integer), 4(Integer), 10(Integer), 33(Integer), CN102467462A | CN102880560A | CN102902935A | CN103427990A | CN103581417A | CN103605459A | CN104239107A | CN104239778A | EP2713298A1 | JP1995092908A | JP2001051987A | JP2002259081A | JP2010541046A | JP2011509459A | JP2013152641A | JP2014514654A | JP2015021363A | JPWO2014077213A1 | US20070113097A1 | US20090083847A1 | US20090210722A1 | US20110072264A1 | US20120252411A1 | US20120291121A1 | US20130318625A1 | US20140085460A1 | US20140095870A1 | US20140292666A1 | US20140298268A1 | US20160042166A1 | US20160212103A1 | US4775595A(String), \20230420\8e3c442330934eb382cb6a19c0c6eee5.png(String), 15(Integer), 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.863 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 1. A mobile terminal privacy protection method; comprising:obtaining an application start instruction;actively obtaining a biometric feature of a user according to the application start instruction; anddisplaying an encrypted content list and an unencrypted content list of an application when the obtained biometric feature of the user matches a preset biometric feature,wherein the encrypted content list of the application is generated according to encrypted content in the application,wherein the unencrypted content list of the application is generated according to unencrypted content in the application, andwherein the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature,wherein before obtaining the application start instruction, the method further comprises:obtaining an unlock instruction entered by the user on a lock screen interface;actively obtaining the biometric feature of the user according to the unlock instruction;displaying an encrypted application icon and an unencrypted application icon when the obtained biometric feature of the user matches the preset biometric feature; anddisplaying the unencrypted application icon when the biometric feature of the user is not obtained and when the obtained biometric feature of the user does not match the preset biometric feature.(String), 1.根据权利要求10所述的移动终端,其中输入设备还被配置为:主动获取用户的面部特征;输入设备还用于主动获取用户的眼睛虹膜特征;或者输入设备还用于主动获取用户的指纹。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 2. The method according to claim 1, wherein after actively obtaining the biometric feature of the user, the method further comprises:displaying the unencrypted content list of the application when the biometric feature of the user is not obtained; anddisplaying the unencrypted content list of the application when the obtained biometric feature of the user does not match the preset biometric feature.(String), 12.根据权利要求10所述的移动终端,其中输入装置还用于通过移动终端的触摸屏主动获取用户在操作未加密内容列表时输入的指纹,输出装置还用于显示加密内容列表和未加密内容列表当主动获取的指纹与预设的生物特征相​​匹配时,应用程序的应用程序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 3. The method according to claim 1, wherein actively obtaining the biometric feature of the user comprises:actively obtaining a facial feature of the user;actively obtaining an eye iris feature of the user; oractively obtaining a fingerprint of the user.(String), 13.根据权利要求10所述的移动终端,其中处理器还用于获取用户输入的打开加密内容列表中的第一条目的第一指令,输出设备还用于根据第一指令呈现第一条目对应的内容,其中,输入装置还用于根据第一指令获取用户输入的生物特征,其中处理器还用于当用户输入的生物特征与预设生物特征匹配时将第一条目设置为未加密状态特征。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 4. The method according to claim 2, wherein after displaying the unencrypted content list of the application, the method further comprises:actively obtaining, using a touchscreen of a mobile terminal, a fingerprint entered by the user when operating the unencrypted content list; anddisplaying the encrypted content list and the unencrypted content list of the application when the actively obtained fingerprint matches the preset biometric feature.(String), 14.根据权利要求10所述的移动终端,其中处理器还用于获取用户输入的第二指令打开未加密内容列表中的第二条目,其中输出设备还用于根据第二指令呈现第二条目对应的内容,其中,输入装置还用于根据第二指令获取用户输入的生物特征,其中处理器还用于当用户输入的生物特征与预设生物特征匹配时将第二条目设置为加密状态特征。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 5. The method according to claim 2, wherein after displaying the encrypted content list and the unencrypted content list of the application, the method further comprises:obtaining a first instruction entered by the user to open a first entry in the encrypted content list;presenting, according to the first instruction, content corresponding to the first entry;obtaining, according to the first instruction, a biometric feature entered by the user; andsetting the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 15.根据权利要求10所述的移动终端,其中输入设备还被配置为:获取移动终端所在的地理位置和环境信息;和当移动终端所在的地理位置信息与预设的地理位置信息匹配时,或当环境信息与预设的环境信息匹配时,根据应用启动指令主动获取用户的生物特征。(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 6. The method according to claim 2, wherein after displaying the encrypted content list and the unencrypted content list of the application, the method further comprises:obtaining a second instruction entered by the user to open a second entry in the unencrypted content list;presenting, according to the second instruction, content corresponding to the second entry;obtaining, according to the second instruction, a biometric feature entered by the user; andsetting the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 1(Integer), 5(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 7. The method according to claim 1, wherein actively obtaining the biometric feature of the user further comprises:obtaining information about a geographic location and an environment in which a mobile terminal is located; andwhen the information about the geographic location in which the mobile terminal is located matches preset geographic location information or when the environment information matches preset environment information.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.864 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 8. A mobile terminal privacy protection method, comprising:obtaining an unlock instruction entered by a user on a lock screen interface;actively obtaining a biometric feature of the user according to the unlock instruction; andpresenting an unlocked first interface when the obtained biometric feature of the user matches a preset biometric feature;presenting a second unlocked interface when the obtained biometric feature of the user does not match the preset biometric feature,wherein an interface element of the unlocked second interface comprises an unencrypted application icon,wherein interface elements of the unlocked first interface comprise an encrypted application icon and the unencrypted application icon, andwherein the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 9. The mobile terminal privacy protection method according to claim 8, wherein actively obtaining the biometric feature of the user further comprises:obtaining information about a geographic location and an environment in which a mobile terminal is located; andactively obtaining the biometric feature of the user according to an application start instruction when the information about the geographic location in which the mobile terminal is located matches preset geographic location information or when the environment information matches preset environment information.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 10. A mobile terminal, comprising:a processor configured to obtain an application start instruction;an input device coupled to the processor and configured to actively obtain a biometric feature of a user according to the application start instruction; andan output device coupled to the processor and the input device and configured to display an encrypted content list and an unencrypted content list of an application when the obtained biometric feature of the user matches a preset biometric feature,wherein the encrypted content list of the application is generated according to encrypted content in the application,wherein the unencrypted content list of the application is generated according to unencrypted content in the application, andwherein the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature,wherein the processor is further configured toobtain an unlock instruction entered by the user on a lock screen interface;actively obtain the biometric feature of the user according to the unlock instruction;display an encrypted application icon and an unencrypted application icon when the obtained biometric feature of the user matches the preset biometric feature; anddisplay the unencrypted application icon when the biometric feature of the user is not obtained and when the obtained biometric feature of the user does not match the preset biometric feature.(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 11. The mobile terminal according to claim 10, wherein the input device is further configured to:actively obtain a facial feature of the user;the input device is further configured to actively obtain an eye iris feature of the user; orthe input device is further configured to actively obtain a fingerprint of the user.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 12. The mobile terminal according to claim 10, wherein the input device is further configured to actively obtain, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and wherein the output device is further configured to display the encrypted content list and the unencrypted content list of the application when the actively obtained fingerprint matches the preset biometric feature.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 13. The mobile terminal according to claim 10, wherein the processor is further configured to obtain a first instruction entered by the user to open a first entry in the encrypted content list, wherein the output device is further configured to present, according to the first instruction, content corresponding to the first entry, wherein the input device is further configured to obtain, according to the first instruction, a biometric feature entered by the user, and wherein the processor is further configured to set the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 14. The mobile terminal according to claim 10, wherein the processor is further configured to obtain a second instruction entered by the user to open a second entry in the unencrypted content list, wherein the output device is further configured to present, according to the second instruction, content corresponding to the second entry, wherein the input device is further configured to obtain, according to the second instruction, a biometric feature entered by the user, and wherein the processor is further configured to set the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.865 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185043(Integer), 15. The mobile terminal according to claim 10, wherein the input device is further configured to:obtain information about a geographic location and an environment in which the mobile terminal is located; andactively obtain the biometric feature of the user according to the application start instruction when the information about the geographic location in which the mobile terminal is located matches preset geographic location information or when the environment information matches preset environment information.(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.985 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:08.987 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185043(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a U.S. National Stage of International Patent Application No. PCT/CN2015/075517 filed on Mar. 31, 2015, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present disclosure relates to the terminal field, and in particular, to a mobile terminal privacy protection method and protection apparatus, and a mobile terminal. BACKGROUND [0003]As technologies and interpersonal communication develop, a mobile terminal has become an important means for people's communication. The mobile terminal is generally a personal article, but because of factors such as an interpersonal relationship, hard-to-refuse, or politeness, people cannot totally prevent the mobile terminal from being used by other people. There is lots of people's privacy in the mobile terminal, such as a short message service message, a contact, a call log, a photo, and an instant messaging message. People expect that the privacy can be protected when the mobile terminal is used by the other people. To resolve a mobile terminal privacy protection problem, a privacy protection mode is set in most mobile terminals to ensure that a user other than an owner is hard to obtain privacy in the mobile terminal in the privacy protection mode. [0004]In other approaches, the privacy protection mode may be implemented in multiple manners. One method is returning, when the mobile terminal is in the privacy protection mode, virtual data when an application in the terminal is opened. For example, in the privacy protection mode, an opened album may display a blank or only display a non-private photo set by a user. A defect of the method is that setting of the returned virtual data is relatively complex and tedious, and if there are many applications, the setting is more tedious. In addition, if the virtual data setting is not realistic enough, the method is easily perceived by another user, which causes unnecessary embarrassment. [0005]Another method is entering different modes by setting different authentication manners. For example, a privacy mode and a normal operation mode correspond to different passwords, patterns, personal identification number (PIN) codes, and fingerprints. A setting of the method is relatively convenient, but in the method, a user is generally prompted to enter a password, draw a pattern, or scan a fingerprint, and therefore a used mode is easily perceived by the user. For example, the mobile terminal is set to enter different modes according to different passwords. Generally, the normal mode is entered when a correct password is entered, and the privacy protection mode is entered when an incorrect password is entered. In this case, the mobile terminal prompts the user to enter a password, and a lock screen can be unlocked by the user entering any incorrect password. The user knows that the entered password is an incorrect password but the lock screen is unlocked, and therefore the user perceives that the privacy protection mode is entered. Another defect of the method is that authentication information needs to be entered only when the lock screen is to be unlocked, and after the lock screen is unlocked, privacy protection cannot be implemented when the user operates an application. [0006]It can be seen that, in the other approaches, there is no mobile terminal privacy protection method that is convenient and efficient and further can avoid being easily perceived by a user. SUMMARY [0007]In view of this, an objective of embodiments of the present disclosure is to provide a mobile terminal privacy protection method and protection apparatus, and a mobile terminal in order to resolve problems that a user easily perceives that privacy in the mobile terminal is protected and privacy is not protected when an application is used. [0008]To resolve the foregoing technical problems, the embodiments of the present disclosure disclose the following technical solutions. [0009]According to a first aspect, a mobile terminal privacy protection method is provided, and the method includes obtaining an application start instruction, actively obtaining a biometric feature of a user according to the application start instruction, and displaying an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature, where the encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0010]With reference to the first aspect, in a first possible implementation manner of the first aspect, after the actively obtaining a biometric feature of a user, the method further includes displaying the unencrypted content list of the application if the biometric feature of the user is not obtained, or displaying the unencrypted content list of the application if the obtained biometric feature of the user does not match the preset biometric feature. [0011]With reference to the first aspect and the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, actively obtaining a biometric feature of a user includes actively obtaining a facial feature of the user, actively obtaining an eye iris feature of the user, or actively obtaining a fingerprint of the user. [0012]With reference to the first possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, after displaying the unencrypted content list of the application, the method further includes actively obtaining, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and displaying the encrypted content list and the unencrypted content list of the application if the actively obtained fingerprint matches the preset biometric feature. [0013]With reference to the first possible implementation manner of the first aspect and the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, after displaying the encrypted content list and the unencrypted content list of the application, the method further includes obtaining a first instruction that is entered by the user to open a first entry in the encrypted content list, presenting, according to the first instruction, content corresponding to the first entry, obtaining, according to the first instruction, a biometric feature entered by the user, and setting the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature. [0014]With reference to the first possible implementation manner of the first aspect and the third possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, after displaying the encrypted content list and the unencrypted content list of the application, the method further includes obtaining a second instruction that is entered by the user to open a second entry in the unencrypted content list, presenting, according to the second instruction, content corresponding to the second entry, obtaining, according to the second instruction, a biometric feature entered by the user, and setting the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature. [0015]With reference to any one of the first aspect to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, before obtaining an application start instruction, the method further includes obtaining an unlock instruction entered by the user on a lock screen interface, actively obtaining the biometric feature of the user according to the unlock instruction, and displaying an encrypted application icon and an unencrypted application icon if the obtained biometric feature of the user matches the preset biometric feature, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0016]With reference to the first aspect, in a seventh possible implementation manner of the first aspect, after actively obtaining the biometric feature of the user according to the unlock instruction, the method further includes displaying the unencrypted application icon if the biometric feature of the user is not obtained, or displaying the unencrypted application icon if the obtained biometric feature of the user does not match the preset biometric feature. [0017]With reference to any one of the first aspect to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, actively obtaining a biometric feature of a user according to the application start instruction further includes obtaining information about a geographic location and an environment in which the mobile terminal is located, and actively obtaining the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0018]According to a second aspect, a mobile terminal privacy protection method is provided, and the method includes obtaining an unlock instruction entered by a user on a lock screen interface, actively obtaining a biometric feature of the user according to the unlock instruction, and presenting an unlocked first interface if the obtained biometric feature of the user matches a preset biometric feature, where interface elements of the first interface include an encrypted application icon and an unencrypted application icon, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0019]With reference to the second aspect, in a first possible implementation manner of the second aspect, an unlocked second interface is presented if the obtained biometric feature of the user does not match the preset biometric feature. An interface element of the second interface includes the unencrypted application icon. [0020]With reference to the second aspect and the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, actively obtaining a biometric feature of the user according to the unlock instruction further includes obtaining information about a geographic location and an environment in which the mobile terminal is located, and actively obtaining the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0021]According to a third aspect, a mobile terminal privacy protection apparatus is provided, and the apparatus includes an instruction obtaining unit configured to obtain an application start instruction, a biometric feature obtaining unit configured to actively obtain a biometric feature of a user according to the application start instruction, and a display unit configured to display an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature, where the encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0022]With reference to the third aspect, in a first possible implementation manner of the third aspect, the display unit is further configured to display the unencrypted content list of the application if the biometric feature of the user is not obtained, or the display unit is further configured to display the unencrypted content list of the application if the obtained biometric feature of the user does not match the preset biometric feature. [0023]With reference to the third aspect and the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the biometric feature obtaining unit includes a photography subunit configured to actively obtain a facial feature of the user, the biometric feature obtaining unit includes a photography subunit configured to actively obtain an eye iris feature of the user, or the biometric feature obtaining unit includes a fingerprint obtaining subunit configured to actively obtain a fingerprint of the user. [0024]With reference to the first possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the fingerprint obtaining subunit is further configured to actively obtain, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and the display unit is further configured to display the encrypted content list and the unencrypted content list of the application if the actively obtained fingerprint matches the preset biometric feature. [0025]With reference to the first possible implementation manner of the third aspect and the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the instruction obtaining unit is further configured to obtain a first instruction that is entered by the user to open a first entry in the encrypted content list. The display unit is further configured to present, according to the first instruction, content corresponding to the first entry. The biometric feature obtaining unit is further configured to obtain, according to the first instruction, a biometric feature entered by the user, and the apparatus further includes a setting unit configured to set the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature. [0026]With reference to the first possible implementation manner of the third aspect and the third possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the instruction obtaining unit is further configured to obtain a second instruction that is entered by the user to open a second entry in the unencrypted content list. The display unit is further configured to present, according to the second instruction, content corresponding to the second entry. The biometric feature obtaining unit is further configured to obtain, according to the second instruction, a biometric feature entered by the user, and the setting unit is further configured to set the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature. [0027]With reference to any one of the third aspect to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the instruction obtaining unit is further configured to obtain an unlock instruction entered by the user on a lock screen interface. The biometric feature obtaining unit is further configured to actively obtain the biometric feature of the user according to the unlock instruction, and the display unit is further configured to display an encrypted application icon and an unencrypted application icon if the obtained biometric feature of the user matches the preset biometric feature, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0028]With reference to the third aspect, in a seventh possible implementation manner of the third aspect, the display unit is further configured to display the unencrypted application icon if the biometric feature of the user is not obtained, or the display unit is further configured to display the unencrypted application icon if the obtained biometric feature of the user does not match the preset biometric feature. [0029]With reference to any one of the third aspect to the seventh possible implementation manner of the third aspect, in an eighth possible implementation manner of the third aspect, the apparatus further includes a geographic location and environment information obtaining unit configured to obtain information about a geographic location and an environment in which the mobile terminal is located, where the biometric feature obtaining unit is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0030]According to a fourth aspect, a mobile terminal privacy protection apparatus is provided, and the apparatus includes an instruction obtaining unit configured to obtain an unlock instruction entered by a user on a lock screen interface, a biometric feature obtaining unit configured to actively obtain a biometric feature of the user according to the unlock instruction, and a display unit configured to present an unlocked first interface if the obtained biometric feature of the user matches a preset biometric feature, where interface elements of the first interface include an encrypted application icon and an unencrypted application icon, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0031]With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the display unit is further configured to present an unlocked second interface if the obtained biometric feature of the user does not match the preset biometric feature. An interface element of the second interface includes the unencrypted application icon. [0032]With reference to the fourth aspect and the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the apparatus further includes a geographic location and environment information obtaining unit configured to obtain information about a geographic location and an environment in which the mobile terminal is located, where the biometric feature obtaining unit is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0033]According to a fifth aspect, a mobile terminal is provided, and the mobile terminal includes a processor configured to obtain an application start instruction, an input device configured to actively obtain a biometric feature of a user according to the application start instruction, and an output device configured to display an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature, where the encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0034]With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the output device is further configured to display the unencrypted content list of the application if the biometric feature of the user is not obtained, or the output device is further configured to display the unencrypted content list of the application if the obtained biometric feature of the user does not match the preset biometric feature. [0035]With reference to the fifth aspect and the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the input device is further configured to actively obtain a facial feature of the user, the input device is further configured to actively obtain an eye iris feature of the user, or the input device is further configured to actively obtain a fingerprint of the user. [0036]With reference to the first possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the input device is further configured to actively obtain, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and the output device is further configured to display the encrypted content list and the unencrypted content list of the application if the actively obtained fingerprint matches the preset biometric feature. [0037]With reference to the first possible implementation manner of the fifth aspect and the third possible implementation manner of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the processor is further configured to obtain a first instruction that is entered by the user to open a first entry in the encrypted content list. The output device is further configured to present, according to the first instruction, content corresponding to the first entry. The input device is further configured to obtain, according to the first instruction, a biometric feature entered by the user, and the processor is further configured to set the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature. [0038]With reference to the first possible implementation manner of the fifth aspect and the third possible implementation manner of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, the processor is further configured to obtain a second instruction that is entered by the user to open a second entry in the unencrypted content list. The output device is further configured to present, according to the second instruction, content corresponding to the second entry. The input device is further configured to obtain, according to the second instruction, a biometric feature entered by the user, and the processor is further configured to set the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature. [0039]With reference to any one of the fifth aspect to the fifth possible implementation manner of the fifth aspect, in a sixth possible implementation manner of the fifth aspect, the processor is further configured to obtain an unlock instruction entered by the user on a lock screen interface. The input device is further configured to actively obtain the biometric feature of the user according to the unlock instruction, and the output device is further configured to display an encrypted application icon and an unencrypted application icon if the obtained biometric feature of the user matches the preset biometric feature, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0040]With reference to the fifth aspect, in a seventh possible implementation manner of the fifth aspect, the output device is further configured to display the unencrypted application icon if the biometric feature of the user is not obtained, or the output device is further configured to display the unencrypted application icon if the obtained biometric feature of the user does not match the preset biometric feature. [0041]With reference to any one of the fifth aspect to the seventh possible implementation manner of the fifth aspect, in an eighth possible implementation manner of the fifth aspect, the input device is further configured to obtain information about a geographic location and an environment in which the mobile terminal is located, and the input device is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0042]According to a sixth aspect, a mobile terminal is provided, and the mobile terminal includes a processor configured to obtain an unlock instruction entered by a user on a lock screen interface, an input device configured to actively obtain a biometric feature of the user according to the unlock instruction, and an output device configured to present an unlocked first interface if the obtained biometric feature of the user matches a preset biometric feature, where interface elements of the first interface include an encrypted application icon and an unencrypted application icon, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0043]With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the output device is further configured to present an unlocked second interface if the obtained biometric feature of the user does not match the preset biometric feature. An interface element of the second interface includes the unencrypted application icon. [0044]With reference to the sixth aspect and the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the input device is further configured to obtain information about a geographic location and an environment in which the mobile terminal is located, and the input device is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0045]The embodiments of the present disclosure provide a mobile terminal privacy protection method. A biometric feature of a user is actively obtained after an application start instruction is obtained, and encrypted content and unencrypted content are displayed if the obtained biometric feature matches a preset biometric feature in order to avoid leakage of user privacy in a mobile terminal and protect the user privacy. In addition, a method for actively obtaining the biometric feature cannot be easily perceived by the user. [0046]It should be understood that, the above general descriptions and the following detailed descriptions are merely examples and cannot limit the protection scope of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS [0047]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0048]FIG. 1 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure, [0049]FIG. 2 shows a schematic diagram of displaying a content list according to an embodiment of the present disclosure, [0050]FIG. 3 shows a schematic diagram of displaying an unencrypted content list according to an embodiment of the present disclosure, [0051]FIG. 4 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure, [0052]FIG. 5 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure, [0053]FIG. 6 shows a schematic diagram of displaying an encrypted content list and an unencrypted content list according to an embodiment of the present disclosure, [0054]FIG. 7 shows a schematic structural diagram of a mobile terminal privacy protection apparatus according to an embodiment of the present disclosure, [0055]FIG. 8 shows a schematic structural diagram of a mobile terminal privacy protection apparatus according to an embodiment of the present disclosure, [0056]FIG. 9 shows a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure, and [0057]FIG. 10 shows a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. [0058]The specific embodiments of the present disclosure have been shown using the foregoing accompanying drawings, and more detailed descriptions are provided in the following. These accompanying drawings and text descriptions are not intended to limit a conception scope of the present disclosure in any manner, but to describe a concept of the present disclosure for a person skilled in the art with reference to the specific embodiments. DESCRIPTION OF EMBODIMENTS [0059]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0060]To completely understand the present disclosure, the following detailed description mentions many specific details. However, a person skilled in the art should understand that the present disclosure may be implemented without these specific details. In other embodiments, detailed descriptions of a well known method, process, component, and circuit are omitted such that the embodiments are described without being unnecessarily blurred. [0061]The embodiments of the present disclosure provide a mobile terminal privacy protection method and protection apparatus, and a mobile terminal, to protect user privacy in the mobile terminal without being easily perceived by another user. [0062]FIG. 1 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure. As shown in FIG. 1, the method includes the following steps. [0063]Step 101: Obtain an application start instruction. [0064]An application unit in a mobile terminal may also be referred to as an application, such as an album, a short message service, and a call log. To start the application, a user may touch an application icon, and after the application icon is touched, the application start instruction is generated. [0065]Step 102: Actively obtain a biometric feature of a user according to the application start instruction. [0066]Further, in an implementation manner of actively obtaining the biometric feature, the user does not need to be prompted, the biometric feature of the user can be obtained without permission of the user, and the biometric feature of the user can be obtained when an input instruction for the biometric feature of the user is not obtained. The manner of active obtaining is relatively covert and is not easily perceived by the user. [0067]Step 10(String), 相关申请的交叉引用 [0001] 本申请是于2015年3月31日提交的美国国家阶段国际专利申请PCT/CN2015/075517,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及终端领域,尤其涉及一种移动终端隐私保护方法、保护装置及移动终端。 背景 [0003] 随着科技和人际交往的发展,移动终端已经成为人们交流的重要手段。 移动终端一般是个人物品,但由于人际关系、难以拒绝或礼貌等因素,人们并不能完全阻止移动终端被他人使用。 移动终端中有很多人的隐私,比如短信业务消息、联系人、通话记录、照片、即时通讯消息等。 人们期望移动终端在被他人使用时能够保护隐私。 为了解决移动终端的隐私保护问题,大多数移动终端都设置了隐私保护模式,以保证在隐私保护模式下,除了所有者之外的其他用户很难获得移动终端中的隐私。 [0004] 在其他方式中,隐私保护方式可以有多种实现方式。 一种方法是,当移动终端处于隐私保护模式时,返回终端中打开应用程序时的虚拟数据。 例如,在隐私保护模式下,打开的相册可以显示空白或者只显示用户设置的非隐私照片。 该方法的一个缺陷是返回的虚拟数据的设置比较复杂繁琐,如果应用较多,则设置比较繁琐。 此外,如果虚拟数据设置不够逼真,则该方法容易被其他用户察觉,造成不必要的尴尬。 [0005] 另一种方法是通过设置不同的认证方式进入不同的模式。 例如,隐私模式和正常操作模式对应不同的密码、图案、个人识别码(PIN)码和指纹。 该方法的设置较为方便,但该方法中一般会提示用户输入密码、绘制图案或扫描指纹,因此所使用的方式容易被用户感知。 例如,设置移动终端根据不同的密码进入不同的模式。 一般情况下,密码输入正确时进入正常模式,密码输入错误时进入隐私保护模式。 此时,移动终端提示用户输入密码,用户输入错误的密码即可解锁锁屏。 用户知道输入的密码是错误的,但是锁屏被解锁,用户感知到进入了隐私保护模式。 该方法的另一个缺陷在于,只有在锁屏解锁时才需要输入认证信息,锁屏解锁后,无法实现用户操作应用程序时的隐私保护。 [0006] 可见,在其他方式中,还没有一种既方便、高效又能避免被用户轻易察觉的移动终端隐私保护方法。 概括 [0007] 有鉴于此,本发明实施例的目的在于提供一种移动终端隐私保护方法、保护装置及移动终端,以解决移动终端中用户容易感知到隐私受到保护和隐私保护的问题。 使用应用程序时不受保护。 [0008] 为解决上述技术问题,本发明实施例公开了以下技术方案。 [0009]第一方面,提供了一种移动终端隐私保护方法,该方法包括获取应用启动指令、根据应用启动指令主动获取用户的生物特征、显示加密内容列表和未加密内容 如果获取的用户生物特征与预设生物特征相​​匹配,则对应应用的列表,其中,应用的加密内容列表根据应用中的加密内容生成,应用的未加密内容列表根据未加密的内容生成 在应用程序中,应用程序中的加密内容为当获取的用户生物特征与预设生物特征不匹配时不呈现的内容。 [0010] 结合第一方面,在第一方面的第一种可能的实现方式中,所述主动获取用户的生物特征之后,所述方法还包括:若用户的生物特征未被获取,则显示应用的未加密内容列表。 如果获取的用户生物特征与预设生物特征不匹配,则显示应用的未加密内容列表。 [0011] 结合第一方面及第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,主动获取用户的生物特征包括主动获取用户的面部特征、主动获取眼睛 用户的虹膜特征,或者主动获取用户的指纹。 [0012] 结合第一方面的第一种可能的实现方式,在第一方面的第三种可能的实现方式中,所述显示应用程序的未加密内容列表后,还包括:通过移动终端的触摸屏主动获取: 用户在操作未加密内容列表时输入的指纹,如果主动获取的指纹与预设的生物特征匹配,则显示应用的加密内容列表和未加密内容列表。 [0013] 结合第一方面的第一种可能的实现方式和第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中,在显示应用程序的加密内容列表和未加密内容列表之后, 该方法还包括获取用户输入的打开加密内容列表中的第一条目的第一指令, 根据第一指令呈现第一条目对应的内容, 根据第一指令获取生物特征 当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态。 [0014] 结合第一方面的第一种可能的实现方式和第一方面的第三种可能的实现方式,在第一方面的第五种可能的实现方式中,在显示应用程序的加密内容列表和未加密内容列表之后, 该方法还包括获取用户输入的打开未加密内容列表中第二条目的第二指令, 根据第二指令呈现第二条目对应的内容, 根据第二指令获取生物特征 当用户输入的生物特征与预设生物特征匹配时,将第二条目设置为加密状态。 [0015]结合第一方面至第一方面的第五种可能的实现方式中的任一项,在第一方面的第六种可能的实现方式中,在获取应用启动指令之前,所述方法还包括:获取用户输入的解锁指令 在锁屏界面,根据解锁指令主动获取用户的生物特征,如果获取的用户生物特征与预设生物特征匹配,则显示加密应用图标和未加密应用图标,其中加密应用图标 是当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0016] 结合第一方面,在第一方面的第七种可能的实现方式中,所述方法在根据解锁指令主动获取用户的生物特征后,还包括:若用户的生物特征为非加密状态,则显示未加密的应用程序图标。 如果获取的用户生物特征与预设生物特征不匹配,则显示未加密的应用程序图标。 [0017] 结合第一方面至第一方面的第七种可能的实现方式中的任一项,在第一方面的第八种可能的实现方式中,根据所述应用启动指令主动获取用户的生物特征,还包括:获取有关信息 移动终端所处的地理位置和环境,如果移动终端所处的地理位置信息与预设的地理位置信息匹配,则根据应用启动指令主动获取用户的生物特征和/ 或者环境信息是否与预设环境信息匹配。 [0018] 第二方面,提供了一种移动终端隐私保护方法,该方法包括获取用户在锁屏界面输入的解锁指令,根据解锁指令主动获取用户的生物特征,并呈现 若获取的用户生物特征与预设生物特征相​​匹配,则解锁第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标,加密应用图标为未加密应用图标。 获取的用户生物特征与预设生物特征不匹配。 [0019] 结合第二方面,在第二方面的第一种可能的实现方式中,若获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0020] 结合第二方面及第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,根据解锁指令主动获取用户的生物特征,还包括:获取地理位置信息; 移动终端所处的环境,如果移动终端所处的地理位置信息与预设的地理位置信息相匹配和/或环境是否匹配,则根据应用启动指令主动获取用户的生物特征 信息匹配预设的环境信息。 [0021]第三方面,提供了一种移动终端隐私保护装置,该装置包括:指令获取单元,用于获取应用启动指令;生物特征获取单元,用于根据应用主动获取用户的生物特征 启动指令,显示单元,用于当获取的用户生物特征与预设生物特征匹配时,显示对应应用的加密内容列表和未加密内容列表,应用的加密内容列表是根据加密生成的 应用中的内容,根据应用中的未加密内容生成应用的未加密内容列表,应用中的加密内容为当获取的用户生物特征与预设生物特征不匹配时不呈现的内容 . [0022] 结合第三方面,在第三方面的第一种可能的实现方式中,所述显示单元,还用于若未获取到所述用户的生物特征,则显示所述应用程序的未加密内容列表,或者所述显示单元进一步被检测到。 用于当获取的用户生物特征与预设生物特征不匹配时,显示应用的未加密内容列表。 [0023] 结合第三方面及第三方面的第一种可能的实现方式,在第三方面的第二种可能的实现方式中,所述生物特征获取单元包括:摄像子单元,用于主动获取用户的面部特征,所述生物特征 特征获取单元包括摄像子单元,用于主动获取用户的眼睛虹膜特征,或者生物特征获取单元包括指纹获取子单元,用于主动获取用户的指纹。 [0024] 结合第三方面的第一种可能的实现方式,在第三方面的第三种可能的实现方式中,所述指纹获取子单元,还用于:通过所述移动终端的触摸屏,主动获取用户输入的指纹。 对未加密内容列表进行操作, 显示单元还用于当主动获取的指纹与预设生物特征匹配时,显示应用程序的加密内容列表和未加密内容列表。 [0025] 结合第三方面的第一种可能的实现方式和第三方面的第三种可能的实现方式,在第三方面的第四种可能的实现方式中,所述指令获取单元,还用于获取由输入的第一指令。 用户打开加密内容列表中的第一个条目。 显示单元还用于根据第一指令呈现第一条目对应的内容。 所述生物特征获取单元,还用于根据所述第一指令获取用户输入的生物特征,所述装置还包括设置单元,用于在用户输入生物特征时,将第一条目设置为未加密状态。 用户匹配预设的生物特征。 [0026] 结合第三方面的第一种可能的实现方式和第三方面的第三种可能的实现方式,在第三方面的第五种可能的实现方式中,所述指令获取单元,还用于获取由输入的第二指令。 用户打开未加密内容列表中的第二个条目。 显示单元还用于根据第二指令呈现第二条目对应的内容。 生物特征获取单元还用于根据第二指令获取用户输入的生物特征,设置单元还用于当用户输入的生物特征匹配时将第二条目设置为加密状态 预设的生物特征。 [0027]结合第三方面至第三方面的第五种可能的实现方式中的任一项,在第三方面的第六种可能的实现方式中,所述指令获取单元还用于获取用户在锁上输入的开锁指令 屏幕界面。 生物特征获取单元还用于根据解锁指令主动获取用户的生物特征,显示单元还用于当获取的用户生物特征匹配时显示加密应用图标和未加密应用图标。 预设生物特征,其中加密应用图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0028] 结合第三方面,在第三方面的第七种可能的实现方式中,所述显示单元还用于若未获取到所述用户的生物特征,则显示未加密的应用程序图标,或者所述显示单元还用于显示 如果获取的用户生物特征与预设生物特征不匹配,则未加密的应用程序图标。 [0029] 结合第三方面至第三方面的第七种可能的实现方式中的任一项,在第三方面的第八种可能的实现方式中,所述装置还包括: 地理位置和环境信息获取单元,用于获取地理信息 所述移动终端所处的地理位置和环境, 所述生物特征获取单元还用于如果所述移动终端所处的地理位置信息,则根据所述应用启动指令主动获取用户的生物特征 匹配预设的地理位置信息和/或环境信息是否匹配预设的环境信息。 [0030] 第四方面,提供一种移动终端隐私保护装置,该装置包括:指令获取单元,用于获取用户在锁屏界面输入的解锁指令;生物特征获取单元,用于主动获取生物特征信息。 显示单元根据解锁指令显示用户的特征,显示单元用于在获取的用户的生物特征与预设的生物特征匹配时呈现解锁的第一界面,第一界面的界面元素包括加密的应用图标和未加密的应用图标。 应用程序图标,其中加密应用程序图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0031] 结合第四方面,在第四方面的第一种可能的实现方式中,所述显示单元还用于在获取的用户生物特征与预设生物特征不匹配时,呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0032] 结合第四方面及第四方面的第一种可能的实现方式,在第四方面的第二种可能的实现方式中,所述装置还包括:地理位置和环境信息获取单元,用于获取地理位置和环境信息。 所述移动终端所处的环境,所述生物特征获取单元还用于当所述移动终端所处的地理位置信息与预设地理信息匹配时,根据所述应用启动指令主动获取用户的生物特征 位置信息和/或环境信息是否与预设环境信息匹配。 [0033]第五方面,提供了一种移动终端,该移动终端包括:处理器,用于获取应用启动指令;输入装置,用于根据应用启动指令主动获取用户的生物特征;输出端 装置,用于当获取的用户生物特征与预设生物特征匹配时,显示对应应用程序的加密内容列表和未加密内容列表,其中,应用程序的加密内容列表是根据应用程序中的加密内容生成的, 根据应用程序中的未加密内容生成应用程序的未加密内容列表,应用程序中的加密内容为当获取的用户生物特征与预设生物特征不匹配时不呈现的内容。 [0034] 结合第五方面,在第五方面的第一种可能的实现方式中,所述输出设备还用于若未获取到所述用户的生物特征,则显示所述应用程序的未加密内容列表,或者所述输出设备进一步被检测到。 用于当获取的用户生物特征与预设生物特征不匹配时,显示应用的未加密内容列表。 [0035] 结合第五方面及第五方面的第一种可能的实现方式,在第五方面的第二种可能的实现方式中,所述输入设备,还用于主动获取所述用户的面部特征,所述输入设备还用于 主动获取用户的虹膜特征,或者输入设备还用于主动获取用户的指纹。 [0036] 结合第五方面的第一种可能的实现方式,在第五方面的第三种可能的实现方式中,所述输入设备还用于通过所述移动终端的触摸屏主动获取用户在操作时输入的指纹。 未加密内容列表, 输出装置还用于当主动获取的指纹与预设生物特征匹配时, 显示应用程序的加密内容列表和未加密内容列表。 [0037] 结合第五方面的第一种可能的实现方式和第五方面的第三种可能的实现方式,在第五方面的第四种可能的实现方式中,所述处理器还用于获取用户输入的第一指令 打开加密内容列表中的第一个条目。 输出设备还用于根据第一指令呈现第一条目对应的内容。 输入设备还用于根据第一指令获取用户输入的生物特征,处理器还用于当用户输入的生物特征与预设生物特征匹配时将第一条目设置为未加密状态 特征。 [0038] 结合第五方面的第一种可能的实现方式和第五方面的第三种可能的实现方式,在第五方面的第五种可能的实现方式中,所述处理器还用于获取用户输入的第二指令 打开未加密内容列表中的第二个条目。 输出设备还用于根据第二指令呈现第二条目对应的内容。 输入设备还用于根据第二指令获取用户输入的生物特征,处理器还用于当用户输入的生物特征与预设生物特征匹配时将第二条目设置为加密状态 特征。 [0039]结合第五方面至第五方面任一种可能的实现方式,在第五方面的第六种可能的实现方式中,所述处理器还用于获取用户在锁屏界面输入的解锁指令 . 输入装置还用于根据解锁指令主动获取用户的生物特征,输出装置还用于当获取的用户生物特征与预设匹配时显示加密应用图标和未加密应用图标。 生物特征,其中,加密应用图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0040] 结合第五方面,在第五方面的第七种可能的实现方式中,所述输出设备还用于在未获取到所述用户的生物特征的情况下显示未加密的应用程序图标,或者所述输出设备还用于显示 如果获取的用户生物特征与预设生物特征不匹配,则未加密的应用程序图标。 [0041] 结合第五方面至第五方面的第七种可能的实现方式中的任一项,在第五方面的第八种可能的实现方式中,所述输入设备还用于获取所述输入设备所在的地理位置和环境信息。 所述移动终端, 所述输入装置还用于若所述移动终端所处的地理位置信息与预设的地理位置信息匹配和/或 环境信息与预设环境信息匹配。 [0042] 第六方面,提供了一种移动终端,所述移动终端包括:处理器,用于获取用户在锁屏界面输入的解锁指令;输入装置,用于根据所述输入设备主动获取用户的生物特征。 解锁指令, 输出设备, 用于当获取的用户生物特征与预设生物特征匹配时, 呈现解锁的第一界面, 其中, 第一界面的界面元素包括加密应用图标和未加密应用图标, 其中, 加密应用图标 应用图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0043] 结合第六方面,在第六方面的第一种可能的实现方式中,所述输出设备还用于在获取的用户生物特征与预设生物特征不匹配时,呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0044] 结合第六方面及第六方面的第一种可能的实现方式,在第六方面的第二种可能的实现方式中,所述输入设备还用于获取所述移动终端所在的地理位置和环境信息。 定位,输入设备还用于当移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息时,根据应用启动指令主动获取用户的生物特征。 匹配预设的环境信息。 [0045] 本发明实施例提供了一种移动终端隐私保护方法。 获取应用启动指令后,主动获取用户的生物特征,如果获取的生物特征与预设的生物特征匹配,则显示加密内容和未加密内容,以避免移动终端用户隐私泄露,保护用户隐私。 用户隐私。 另外,主动获取生物特征的方法不易被用户感知。 [0046]应当理解,上面的一般描述和下面的详细描述仅仅是示例,并不限制本公开的保护范围。 附图说明 [0047] 为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简要说明。 下面描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0048] 图1示出了根据本发明一个实施例的移动终端隐私保护方法的流程图, [0049] 图2示出了根据本发明实施例的显示内容列表的示意图, [0050] 图3示出了根据本发明实施例的显示未加密内容列表的示意图, [0051] 图4示出了根据本发明一个实施例的移动终端隐私保护方法的流程图, [0052] 图5示出了根据本发明一个实施例的移动终端隐私保护方法的流程图, [0053] 图6示出了根据本发明实施例的显示加密内容列表和未加密内容列表的示意图, [0054] 图7示出了根据本发明实施例的移动终端隐私保护装置的结构示意图, [0055] 图8示出了根据本发明实施例的移动终端隐私保护装置的结构示意图, [0056] 图9示出了根据本发明实施例的移动终端的结构示意图,以及 [0057] 图10示出了根据本发明实施例的移动终端的结构示意图。 [0058] 已经利用前述附图示出了本公开的具体实施例,并且在下文中提供更详细的描述。 这些附图和文字说明并不以任何方式限制本发明的构思范围,而是通过具体实施例为本领域技术人员描述本发明的构思。 具体实施方式 [0059] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0060] 为了完全理解本公开,以下详细描述提及许多具体细节。 然而,本领域技术人员应当理解,没有这些具体细节也可以实施本公开。 在其他实施例中,省略了众所周知的方法、过程、组件和电路的详细描述,使得描述实施例时不会不必要地模糊。 [0061] 本发明实施例提供一种移动终端隐私保护方法、保护装置及移动终端,以保护移动终端中的用户隐私不易被其他用户察觉。 [0062] 图1示出了根据本公开实施例的移动终端隐私保护方法的流程图。 如图1所示,该方法包括以下步骤。 [0063] 步 101 :获取应用启动指令。 [0064]移动终端中的应用单元也可以称为应用,例如相册、短信业务、通话记录等。 为了启动应用,用户可以触摸应用图标,触摸应用图标后,生成应用启动指令。 [0065] 步 102 :根据应用启动指令主动获取用户的生物特征。 [0066] 进一步地,在主动获取生物特征的实施方式中,不需要提示用户,无需用户许可即可获取用户的生物特征,在输入时获取用户的生物特征。 未获取用户生物特征的说明。 主动获取的方式比较隐蔽,不易被用户察觉。 [0067] 步 103 :若获取的用户生物特征与预设生物特征匹配,则显示对应应用程序的加密内容列表和未加密内容列表。 [0068] 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 简言之,加密内容可以是用户不希望其他用户看到的设置了密码的内容。 [0069] 用户可以将应用单元中的具体内容设置为可以包括加密状态或未加密状态的状态。 加密内容是用户不希望其他用户看到的内容。 例如,对于相册中的照片,用户可以为不希望其他用户看到的照片设置密码。 [0070] 当获取的用户生物特征与预设生物特征不匹配时,不呈现的内容包括至少一种元素。 该元素可以是文字、图片、视频等。 通常,一个元素以一个条目的形式呈现。 加密内容列表可以以列表的形式呈现加密内容。 [0071] 在本发明实施例中,可以对列表进行广义的理解。 对于不同的应用,内容列表可以有不同的形式,可以是条列表,也可以是块列表。 例如,如果应用程序是短信服务或即时通讯程序,则内容列表可以是发送方的电话号码列表,如图2所示的条形短信服务消息列表,以及图2所示的列表。 2 仅显示电话号码或发件人姓名。 如果应用是相册,则内容列表可以是图3所示的照片块缩略图列表,两者 301 和 302 图 3 中的是照片缩略图。 如果应用程序是录音软件或音乐播放软件,则内容列表可以是文件名列表。 [0072] 本发明实施例的方法在接收到应用启动指令后,主动获取用户的生物特征,如果获取的生物特征与预设生物特征匹配的结果显示为机密内容且未加密 内容,可以避免移动终端用户隐私泄露,保护用户隐私。 另外,主动获取生物特征的方法不易被用户感知。 [0073] 在本公开的一个实施例中,经过步骤 103 ,在主动获取用户的生物特征之后,还包括若未获取到用户的生物特征,则显示应用程序的未加密内容列表,若获取到生物特征,则显示应用程序的未加密内容列表。 用户的特征与预设的生物特征不匹配。 [0074]在本发明的一个实施例中,主动获取用户的生物特征包括主动获取用户的面部特征、主动获取用户的眼睛虹膜特征或主动获取用户的指纹。 [0075] 可以通过两种方式获得指纹。 一种方式是通过专门的指纹获取器获取指纹,另一种方式是通过移动终端的屏幕获取指纹。 移动终端指纹获取器的位置随着移动终端的型号不同而不同。 例如,iPhone的指纹获取单元在home键处,华为手机的指纹获取单元在手机背面。 [0076] 部分机型的手机屏幕可以作为屏幕指纹获取器,通过用户在移动终端屏幕上的触摸可以直接获取用户的指纹。 通过触摸屏幕获取用户的指纹更加隐蔽。 [0077] 主动获取可以避免所有者以外的用户察觉到获取了生物特征用于后续验证,以保护移动终端中的隐私,避免可能造成的尴尬。 [0078] 在本发明的另一实施例中,生物特征获取单元还可以为音频获取单元,用于获取用户的语音。 [0079] 在本发明的另一个实施例中,在显示应用程序的未加密内容列表之后,还包括通过移动终端的触摸屏主动获取用户在操作未加密内容列表时录入的指纹,并显示加密后的内容。 如果主动获取的指纹与预设的生物特征匹配,则为应用的内容列表和未加密内容列表。 [0080] 如果应用启动时车主没有正对摄像头,或者因为光线问题或距离问题,可能导致摄像头获取的面部特征或虹膜特征模糊或变形,或者主动获取的指纹模糊。 因此,后续的匹配很难成功,从而所有者很难获得所有想要的信息。 本发明实施例中,在因上述问题显示未加密内容列表后,在未加密内容列表中进入时,通过用户在移动终端屏幕上的触摸,主动获取用户的指纹。 选择内容列表是为了避免误判给业主带来的不便。 [0081] 在本发明的一个实施例中,在显示应用程序的加密内容列表和未加密内容列表之后,该方法还包括获取用户输入的打开加密内容列表中的第一条目的第一指令,呈现, 根据第一指令,第一条目对应的内容, 根据第一指令获取用户输入的生物特征,当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态 特征。 [0082] 在本发明的另一个实施例中,在显示应用程序的加密内容列表和未加密内容列表之后,该方法还包括获取用户输入的打开未加密内容列表中的第二条目的第二指令,呈现, 根据第二指令,第二表项对应的内容, 根据第二指令获取用户输入的生物特征,当用户输入的生物特征与预设生物特征匹配时,将第二表项设置为加密状态 特征。 [0083]所有者在查看加密内容和未加密内容后,在列表中选择条目时,可以通过主动输入生物特征改变所选条目的状态,即将加密内容设置为未加密内容或将未加密内容设置为加密内容 内容。 例如,用户在隐私内容列表中打开一张照片,当用户查看该照片时,手指再次触碰home键主动触发指纹采集命令,或者短时间长按屏幕进行指纹采集。 主动触发屏幕指纹采集指令。 指纹比对成功后,可以切换照片的状态,如果照片是加密的,则可以将照片的状态切换为未加密,如果照片未加密,则可以将照片的状态切换为加密 . 本实施例中,通过主动触发生物特征获取命令来切换应用内容的加密状态或非加密状态的方法方便、高效,且相对隐蔽,不易被其他用户察觉。 [0084] 在本发明的一个实施例中,该方法在接收到应用启动指令之前,还包括获取用户在锁屏界面输入的解锁指令,根据解锁指令主动获取用户的生物特征,并显示 如果获取的用户生物特征与预设生物特征匹配,则为加密应用图标,如果为未加密应用图标,则为未加密应用图标。 [0085] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0086] 在根据解锁指令主动获取用户的生物特征后,还包括若未获取到用户的生物特征则显示未加密的应用程序图标,若获取到的用户的生物特征则显示未加密的应用程序图标。 与预设的生物识别特征不匹配。 [0087] 在本发明的一个实施例中,根据应用启动指令主动获取用户的生物特征还包括获取移动终端所在的地理位置和环境信息,主动获取用户的生物特征。 根据应用启动指令,移动终端所在的地理位置信息是否与预设的地理位置信息匹配和/或环境信息是否与预设的环境信息匹配。 [0088] 通常,用户通过在移动终端中触摸应用程序的图标来启动应用程序。 本实施例的方法在接收到解锁指令后主动获取用户的生物特征,并根据是否获取到生物特征以及获取到的生物特征与用户的匹配情况显示不同的应用图标。 预设生物特征。 可以隐藏所有者不希望其他用户看到或使用的应用程序,进一步避免移动终端中用户隐私的泄露,以保护用户隐私。 另外,主动获取的方式不容易被用户感知。 [0089] 图4示出了根据本公开实施例的移动终端隐私保护方法的流程图。 如图4所示,该方法包括以下步骤。 [0090] 步 401 :获取用户在锁屏界面输入的解锁指令。 [0091] 步 402 :根据解锁指令主动获取用户的生物特征。 [0092] 步 403 :若获取的用户生物特征与预设生物特征匹配,则呈现解锁的第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标。 [0093] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0094]如果获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0095] 通常,用户通过在移动终端中触摸应用程序的图标来启动应用程序。 本实施例的方法在接收到解锁指令后主动获取用户的生物特征,根据是否获取到生物特征以及获取到的生物特征与预设生物特征的匹配情况显示不同的界面。 功能,不同的界面显示不同的应用程序图标。 可以隐藏所有者不希望其他用户看到或使用的应用程序,进一步避免移动终端中用户隐私的泄露,以保护用户隐私。 另外,主动获取的方式不容易被用户感知。 [0096] 在本发明的一个实施例中,根据解锁指令主动获取用户的生物特征还包括获取移动终端所处的地理位置和环境信息,根据解锁指令主动获取用户的生物特征。 如果移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则向应用程序启动指令发送消息。 [0097] 为了进一步保护用户隐私,可以根据移动终端的地理位置信息和环境信息来确定显示的内容。 环境信息可以包括温度、湿度、海拔等。 [0098] 图5示出了根据本公开实施例的移动终端隐私保护方法的流程图。 图5所示的方法以指纹采集为例进行说明。 如图5所示,该方法包括以下步骤。 [0099] 步 501 :获取用户在锁屏界面输入的解锁指令。 [0100] 步 502 :根据解锁指令,通过用户在屏幕上的触摸,主动获取用户的指纹。 [0101] 步 503 :判断是否获取到指纹,如果未获取到指纹,执行步骤 504 ,或者如果获取到指纹,执行步骤 505 . [0102] 步 504 :显示未加密内容列表,执行步骤 507 . [0103] 参见图3所示本发明实施例未加密内容列表的显示示意图,图3所示的应用场景以相册为例。 如图3所示,未加密的内容只有两张照片 301 和 302 根据用户设置。 [0104] 步 505 :判断获取到的指纹是否匹配预留指纹,如果获取到的指纹匹配到预留指纹,则执行步骤 506 , 或者获取到的指纹与预留指纹不匹配,执行步骤 507 . [0105] 步 506 :显示加密内容列表和未加密内容列表。 [0106] 图6示出了根据本发明实施例的显示加密内容列表和未加密内容列表的示意图。 图6所示的应用场景与图3所示相同。如图6所示,根据用户设置,未加密的照片被 301 和 302 ,加密的照片是 303 , 304 , 之类的。 [0107] 步 507 :接收用户从未加密列表中选择照片缩略图,通过用户触摸屏幕主动获取指纹,执行步骤 503 . [0108] 本发明实施例提供的移动终端隐私保护方法,能够在移动终端中保护隐私,不易被用户察觉。 [0109] 图7示出了根据本发明实施例的移动终端隐私保护装置的结构示意图。 如图7所示,该装置包括指令获取单元 701 用于获取应用启动指令、生物特征获取单元 702 用于根据应用启动指令主动获取用户的生物特征,显示单元 703 用于当获取的用户生物特征与预设生物特征匹配时,显示相应应用程序的加密内容列表和未加密内容列表。 [0110] 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 [0111] 显示单元 703 还用于如果未获取到用户的生物特征,则显示应用程序的未加密内容列表,或者显示单元 703 还用于若获取的用户生物特征与预设生物特征不匹配,则显示应用的未加密内容列表。 [0112] 在本公开的一个实施例中,生物特征获取单元 702 包括用于主动获取用户面部特征的拍照子单元(未示出),或生物特征获取单元 702 包括用于主动获取用户的眼睛虹膜特征的摄像子单元(未示出),或者生物特征获取单元 702 包括指纹获取子单元(未示出),用于主动获取用户的指纹。 [0113] 在本发明的一个实施例中,指纹获取子单元还用于通过移动终端的触摸屏主动获取用户在操作未加密内容列表时输入的指纹。 [0114] 显示单元 703 还用于若主动获取的指纹与预设生物特征匹配,则显示应用的加密内容列表。 [0115] 在本发明的一个实施例中,指令获取单元 701 还用于获取用户输入的打开加密内容列表中第一项的第一指令。 [0116] 显示单元 703 还用于根据第一指令呈现第一条目对应的内容。 [0117] 生物特征获取单元 702 还用于根据第一指令获取用户输入的生物特征。 [0118] 该装置还包括设置单元(未示出),用于当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态。 [0119] 指令获取单元 701 还用于获取用户输入的打开未加密内容列表中的第二条目的第二指令。 [0120] 显示单元 703 还用于根据第二指令呈现第二条目对应的内容。 [0121] 生物特征获取单元 702 还用于根据第二指令获取用户输入的生物特征。 [0122] 显示单元 703 还用于当用户输入的生物特征与预设生物特征匹配时,将第二条目设置为加密状态。 [0123] 在本发明的一个实施例中,指令获取单元 701 还用于获取用户在锁屏界面输入的解锁指令。 [0124] 生物特征获取单元 702还用于根据解锁指令主动获取用户的生物特征。 [0125] 显示单元 703 还用于若获取的用户生物特征与预设生物特征匹配,则显示加密应用图标和未加密应用图标。 [0126] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0127] 显示单元 703 还用于如果未获取到用户的生物特征,则显示未加密的应用程序图标,或者显示单元 703 还用于若获取的用户生物特征与预设生物特征不匹配,则显示未加密的应用程序图标。 [0128] 该装置还包括地理位置和环境信息获取单元(未示出),用于获取移动终端所在的地理位置和环境信息。 [0129] 生物特征获取单元 702 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0130] 获取地理位置信息和环境信息可以进一步提高本发明实施例的安全性。 [0131] 图8示出了根据本发明实施例的移动终端保护装置的结构示意图。 如图8所示,该装置包括指令获取单元 801 用于获取用户在锁屏界面输入的解锁指令,生物特征获取单元 802 用于根据解锁指令主动获取用户的生物特征,显示单元 803 用于在获取的用户生物特征与预设生物特征匹配时呈现解锁的第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标。 [0132] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0133] 显示单元 803 还用于若获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0134] 在本发明的一个实施例中,该装置还包括地理位置和环境信息获取单元(未示出),用于获取移动终端所在的地理位置和环境信息。 [0135] 生物特征获取单元 802 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0136] 本发明实施例提供的移动终端隐私保护装置可以保护移动终端中的隐私,不易被其他用户察觉,避免尴尬。 [0137] 图9示出了根据本发明实施例的移动终端的结构示意图。 如图9所示,移动终端包括处理器 901 配置为获取应用启动指令、输入设备 902 用于根据应用启动指令主动获取用户的生物特征,以及输出装置 903用于当获取的用户生物特征与预设生物特征匹配时,显示相应应用程序的加密内容列表和未加密内容列表。 移动终端还包括存储器和总线,其中处理器 901 , 输入设备 902 , 输出设备 903 和内存使用总线相互耦合。 [0138] 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 [0139] 在本公开的一个实施例中,输出设备 903 还用于如果未获取到用户的生物特征,则显示应用的未加密内容列表,或者输出设备 903 还用于若获取的用户生物特征与预设生物特征不匹配,则显示应用的未加密内容列表。 [0140] 在本公开的一个实施例中,输入设备 902 还用于主动获取用户的面部特征,输入设备 902 还用于主动获取用户的眼睛虹膜特征,或者输入设备 902 还用于主动获取用户的指纹。 [0141] 在本公开的一个实施例中,输入设备 902 还用于通过移动终端的触摸屏(未示出)主动获取用户在操作未加密内容列表时录入的指纹。 [0142] 输出设备 903 还用于若主动获取的指纹与预设生物特征匹配,则显示应用的加密内容列表。 [0143] 在本公开的一个实施例中,处理器 901 还用于获取用户输入的打开加密内容列表中第一项的第一指令。 [0144] 输出设备 903 还用于根据第一指令呈现第一条目对应的内容。 [0145] 输入设备 902 还用于根据第一指令获取用户输入的生物特征。 [0146] 处理器 901 还用于当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态。 [0147] 处理器 901 还用于获取用户输入的打开未加密内容列表中的第二条目的第二指令。 [0148] 输出设备 903 还用于根据第二指令呈现第二条目对应的内容。 [0149] 输入设备 902 还用于根据第二指令获取用户输入的生物特征。 [0150] 处理器 901 还用于当用户输入的生物特征与预设生物特征匹配时,将第二条目设置为加密状态。 [0151] 在本公开的一个实施例中,处理器 901 还用于获取用户在锁屏界面输入的解锁指令。 [0152] 输入设备 902 还用于根据解锁指令主动获取用户的生物特征。 [0153] 输出设备 903 还用于若获取的用户生物特征与预设生物特征匹配,则显示加密应用图标和未加密应用图标。 [0154] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0155]在本公开的一个实施例中,输出设备 903 还用于如果未获取到用户的生物特征,则显示未加密的应用程序图标,或者输出设备 903 还用于若获取的用户生物特征与预设生物特征不匹配,则显示未加密的应用程序图标。 [0156] 在本公开的一个实施例中,输入设备 902 还用于获取移动终端所在的地理位置和环境信息。 [0157] 输入设备 902 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0158] 图10示出了根据本发明实施例的移动终端的结构示意图。 如图10所示,移动终端包括处理器 1001 用于获取用户在锁屏界面输入的解锁指令,输入设备 1002 用于根据解锁指令主动获取用户的生物特征,以及输出装置 1003 用于在获取的用户生物特征与预设生物特征匹配时呈现解锁的第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标。 移动终端还包括存储器和总线,其中处理器 1001 , 输入设备 1002 , 输出设备 1003 和内存使用总线相互耦合。 [0159] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0160] 在本公开的一个实施例中,输出设备 1003 还用于若获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0161] 在本公开的一个实施例中,输入设备 1002 还用于获取移动终端所在的地理位置和环境信息。 [0162] 输入设备 1002 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0163] 根据本公开的移动终端可以保护用户隐私,并且隐私保护不容易被其他用户察觉以避免尴尬。 [0164] 本发明实施例提供一种移动终端隐私保护方法、装置及移动终端。 获取应用启动指令,根据应用启动指令主动获取用户的生物特征,如果获取的用户生物特征与预设匹配,则显示对应应用的加密内容列表和未加密内容列表 生物特征。 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 本发明可以保护移动终端中的隐私,不易被察觉,避免不必要的尴尬,提高用户的使用体验。 [0165]系统实施例基本对应于方法实施例。 相关之处参见方法实施例的部分说明即可。 所描述的系统实施例仅仅是示例。 描述为分立部分的单元在物理上可以是独立的也可以不是,作为单元显示的部分可以是物理单元也可以不是物理单元,可以位于一个位置,也可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部模块来实现本实施例方案的目的。 本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0166] 可以在由计算机执行的可执行计算机指令的一般上下文中描述本公开,例如,程序模块。 通常,程序单元包括用于执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等。 本公开还可以在分布式计算环境中实践,在分布式计算环境中任务由通过通信网络连接的远程处理设备执行。 在分布式计算环境中,程序模块可以位于本地和远程计算机存储介质中,包括存储设备。 [0167] 本领域普通技术人员可以理解,上述方法实施例中的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中,例如只读存储器(ROM)、随机存取存储器(RAM)、磁盘或光盘。 [0168] 需要说明的是,在本说明书中,诸如第一和第二等关系术语仅用于区分一个实体或操作与另一个实体或操作,并不一定要求或暗示这些实体或操作之间存在任何实际关系或顺序。 此外,术语“包括”、“包含”或它们的任何其他变体旨在涵盖非排他性的包含,使得包括一系列要素的过程、方法、物品或设备不仅包括那些 元素,但也包括未明确列出的其他元素,或进一步包括此类过程、方法、物品或设备固有的元素。 前面带有“的元素包括一个 . . . ” 在没有更多限制的情况下,不排除在包含该元素的过程、方法、物品或设备中存在其他相同元素。 [0169] 总之,以上所述仅为本发明的实施例而已,并不用于限定本发明的保护范围。 本说明书通过具体示例来说明本发明的原理和实施方式。 以上实施例的描述仅仅用于帮助理解本发明的方法和核心思想。 此外,本领域的技术人员可以根据本发明的思想,对具体的实施方式和适用范围进行修改。 因此,本说明书的内容不应理解为对本发明的限制。 因此,本说明书的内容不应理解为对本发明的限制。 凡在本发明的精神和原则的范围内,所做的任何修改、等同替换、改进等,均属于本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.005 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.006 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106233294A(String), CN106233294B(String), CN112597469A(String), EP3252637A1(String), EP3252637A4(String), EP3252637B1(String), EP4080387A1(String), ES2923905T3(String), JP2018517960A(String), JP6571203B2(String), US10382204B2(String), US11394555B2(String), US20180062846A1(String), US20190334721A1(String), US20220385471A1(String), WO2016154898A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.008 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106233294A(String), CN106233294B(String), CN112597469A(String), EP3252637A1(String), EP3252637A4(String), EP3252637B1(String), EP4080387A1(String), ES2923905T3(String), JP2018517960A(String), JP6571203B2(String), US10382204B2(String), US11394555B2(String), US20180062846A1(String), US20190334721A1(String), US20220385471A1(String), WO2016154898A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.009 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10382204B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.016 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106233294A(String), CN106233294B(String), CN112597469A(String), EP3252637A1(String), EP3252637A4(String), EP3252637B1(String), EP4080387A1(String), ES2923905T3(String), JP2018517960A(String), JP6571203B2(String), US10382204B2(String), US11394555B2(String), US20180062846A1(String), US20190334721A1(String), US20220385471A1(String), WO2016154898A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.018 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), CN106233294A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.028 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), CN106233294B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.035 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), CN112597469A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.045 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), EP3252637A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.057 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.058 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), EP3252637A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.067 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.068 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), EP3252637B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.075 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), EP4080387A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.082 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), ES2923905T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.092 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.093 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), JP2018517960A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.105 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), JP6571203B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.116 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), US10382204B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.125 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.125 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.125 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), US11394555B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.135 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), US20180062846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.144 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), US20190334721A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.154 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), US20220385471A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270718(Integer), WO2016154898A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10382204B2(String), US10382204B2(String), 1565625600(Integer), 270718(Integer), 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.189 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.191 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.191 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.191 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.192 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.193 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185043(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.194 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 1(Integer), 185043(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.203 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1681975537(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.204 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.205 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185043(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.206 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.206 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.206 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75908(Integer), 2(Integer), 185043(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.229 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.230 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.231 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.232 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.233 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.234 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.235 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.236 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.253 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.254 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.255 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.256 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.257 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185043(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.274 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.275 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120259775A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.278 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Application Method of Mobile Terminal Electronic Wallet and Mobile Terminal(String), 移动终端电子钱包应用方法及移动终端(String), US20120259775A1(String), Disclosed in the present invention is an application method for a mobile terminal electronic wallet, including: monitoring a transaction event carried out by the mobile terminal via the NFC chip; when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; and sending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing the consumption situation of the transaction event to a user. Also disclosed in the present invention is a mobile terminal, wherein, an acquiring module is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after a monitoring module monitors the transaction event; and a sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application but cannot be displayed automatically is solved.(String), 本发明公开了一种移动终端电子钱包的应用方法,包括:通过NFC芯片监听移动终端进行的交易事件; 当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息; 将交易消息发送给JAVA模块,启动相应的JAVA应用程序,将交易事件的消费情况提供给用户。 本发明还公开了一种移动终端,其中,获取模块,用于在监听模块监听到交易事件后,获取UICC通过NFC芯片发送的交易事件的交易消息; 发送模块,用于将交易消息发送给JAVA模块,启动相应的JAVA应用程序,但无法自动显示。(String), US13/513778(String), 1271779200(Integer), US20120259775A1(String), 1349884800(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 3(Integer), US20080121687A1 | US20100083280A1 | US20100136913A1(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.305 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185044(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\adc87adfc730452d8430b992133fe0af.png(String), 185044(Integer), adc87adfc730452d8430b992133fe0af.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.320 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.322 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Application Method of Mobile Terminal Electronic Wallet and Mobile Terminal(String), 移动终端电子钱包应用方法及移动终端(String), US20120259775A1(String), Disclosed in the present invention is an application method for a mobile terminal electronic wallet, including: monitoring a transaction event carried out by the mobile terminal via the NFC chip; when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; and sending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing the consumption situation of the transaction event to a user. Also disclosed in the present invention is a mobile terminal, wherein, an acquiring module is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after a monitoring module monitors the transaction event; and a sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application but cannot be displayed automatically is solved.(String), 本发明公开了一种移动终端电子钱包的应用方法,包括:通过NFC芯片监听移动终端进行的交易事件; 当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息; 将交易消息发送给JAVA模块,启动相应的JAVA应用程序,将交易事件的消费情况提供给用户。 本发明还公开了一种移动终端,其中,获取模块,用于在监听模块监听到交易事件后,获取UICC通过NFC芯片发送的交易事件的交易消息; 发送模块,用于将交易消息发送给JAVA模块,启动相应的JAVA应用程序,但无法自动显示。(String), US13/513778(String), 1271779200(Integer), US20120259775A1(String), 1349884800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 3(Integer), US20080121687A1 | US20100083280A1 | US20100136913A1(String), \20230420\adc87adfc730452d8430b992133fe0af.png(String), 6(Integer), 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.333 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.334 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185044(Integer), 1. An application method for a mobile terminal electronic wallet with a near field communication (NFC) chip being integrated into the mobile terminal, comprising:monitoring a transaction event carried out by the mobile terminal via the NFC chip;when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; andsending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing a consumption situation of the transaction event to a user.(String), 1、一种移动终端集成近场通信(NFC)芯片的移动终端电子钱包的应用方法,包括:通过NFC芯片监测移动终端进行的交易事件;当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息;和将交易消息发送给JAVA模块,启动相应的JAVA应用,向用户提供交易事件的消费情况。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185044(Integer), 2. The method according to claim 1, wherein sending the transaction message to a JAVA module and starting up a corresponding JAVA application further comprises:the JAVA module receiving the transaction message and invoking a PUSH interface to start up the corresponding JAVA application.(String), 2.根据权利要求1所述的方法,其中向JAVA模块发送交易消息并启动相应的JAVA应用程序还包括:JAVA模块接收交易消息,调用PUSH接口启动相应的JAVA应用。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185044(Integer), 3. The method according to claim 2, wherein invoking a PUSH interface to start up the corresponding JAVA application further comprises:acquiring PUSH register information about the application from a set PUSH register information list; andparsing the PUSH register information about the application and starting up the corresponding JAVA application.(String), 3.根据权利要求2所述的方法,其中调用PUSH接口启动对应的JAVA应用还包括:从设置的PUSH注册信息列表中获取应用的PUSH注册信息;和解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185044(Integer), 4. A mobile terminal in which an NFC chip is integrated, comprising a JAVA module and further comprising a monitoring module, an acquiring module, a sending module, and a display module, whereinthe monitoring module is used for monitoring a transaction event carried out by the mobile terminal via the NFC chip;the acquiring module is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after the monitoring module monitors the transaction event;the sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application; andthe display module is used for providing a consumption situation regarding the transaction event to a user.(String), 4.移动端其中集成NFC芯片,包括JAVA模块,还包括监控模块、获取模块、发送模块和显示模块,其中监听模块用于监听移动终端通过NFC芯片进行的交易事件;获取模块,用于在监听模块监听到交易事件后,通过NFC芯片获取UICC发送的交易事件的交易消息;发送模块,用于将交易消息发送给JAVA模块,并启动相应的JAVA应用程序;和显示模块用于向用户提供交易事件的消费情况。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.335 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185044(Integer), 5. The mobile terminal according to claim 4, further comprising a JAVA virtual machine, whereinthe JAVA module is further used for receiving the transaction message and starting up the JAVA virtual machine; andthe JAVA virtual machine is used for invoking a PUSH interface to start up the corresponding JAVA application.(String), 5.根据权利要求4所述的移动终端,还包括JAVA虚拟机,其中JAVA模块还用于接收交易消息和启动JAVA虚拟机。和JAVA虚拟机用于调用PUSH接口启动相应的JAVA应用程序。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.336 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185044(Integer), 6. The mobile terminal according to claim 5, wherein the JAVA virtual machine is further used for acquiring PUSH register information about the application from a set PUSH register information list; and parsing the PUSH register information about the application and starting up the corresponding JAVA application.(String), 6.根据权利要求5所述的移动终端,其中JAVA虚拟机还用于从设定的PUSH注册信息列表中获取应用程序的PUSH注册信息;解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.386 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.387 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185044(Integer), TECHNICAL FIELD [0001]The present invention relates to the communication field, and particularly, to an application method for a mobile terminal electronic wallet and a mobile terminal. BACKGROUND OF THE RELATED ART [0002]With the development of the near field communication (NFC) technology, the near field consumption also has been significantly changed. The mobile terminal such as mobile phone becomes a secure, convenient, rapid and fashionable contactless payment and ticket tool. The mobile terminal becomes a transportation card and a bank card, so that the mobile phone can be swiped for consumption just as swiping the transportation card and the bank card. People especially like the easy usage, convenience and rapidness of contactless payment of the NFC and wish to no longer carry on a wallet. The transaction can be done only by making the mobile terminal approach the device terminal without presenting the payment card. [0003]The solutions for realizing near field consumption with the NFC technology are mainly as follows: 1. profiled pasting card in which a token is pasted on the mobile phone, such as the Bank in Palm service in Chongqing city; 2. SIMpass, i.e. dual SIM cards, such as Watchdata solution; 3. NFC, wherein an NFC chip is integrated in the mobile phone and the single wire protocol (SWP) SIM card is not supported; 4. eNFC, wherein the chip and SIM card supporting the SWP protocol have to be integrated; 5. 2.4G radio frequency (abbreviated as RF) SIM, wherein a 2.4G communication module is integrated in the SIM card, and the SIM card has to be directly changed. In this case, the chip and SIM card supporting the SWP protocol need to be integrated with eNFC, which currently is a very popular technical solution. [0004]Since NFC has broad market prospect, the mobile operators are positively promoting the development of this industry chain, and the electronic wallet and electronic ticket service are especially valued. Currently, the process of using the NFC electronic wallet to consume is as shown in FIG. 1, after the NFC chip of the mobile phone is activated, micro payment function can be realized by a POS machine when the mobile phone is in the card emulation state. [0005]Referring to FIG. 1, the POS machine initiates a consumption request, the NFC chip forwards the request to the SIM card, the SIM card would respond, and after the transaction is over, the user can check the transaction situation of the mobile phone wallet by opening the JAVA client. [0006]FIG. 2 is a schematic diagram of the working principle of consuming using an NFC electronic wallet, referring to FIG. 2, it includes a universal integrated circuit card (UICC), an NFC radio frequency chip (MicroRead) and a mobile phone processor. The part relevant to the application is totally placed in the smart SIM card, i.e. UICC, and the MicroRead is integrated in the mainboard of the mobile phone. The MicroRead communicates with the mobile phone processor via a UART interface, and communicates with the application part in the UICC via the SWP protocol. After the mobile phone has transacted with the POS machine, the UICC can send message to the mobile phone processor via the MicroRead. [0007]There is a problem in the above operation: assuming that the mobile phone is in the standby interface, after the mobile phone has carries out a transaction, the user will habitually check the balance of the electronic wallet, however, currently, the application carry out a query manually on the market, the user has to enter JAVA and then start up the application, which greatly affects the user experience. [0008]In summary, it can be known that the problem that the balance of the electronic wallet can only be checked manually and cannot be displayed automatically always exists in the related art, therefore, it is necessary to propose an improved technical means to solve this problem. SUMMARY OF THE INVENTION [0009]The present invention is proposed in view of the problem in the related art that the balance of the electronic wallet can only be checked manually and cannot be displayed automatically, for this end, the main object of the present invention is to provide an application method for a mobile terminal electronic wallet and a mobile terminal, wherein[0010]the present invention provides an application method for a mobile terminal electronic wallet with an near field communication (NFC) chip being integrated into the mobile terminal, including: monitoring a transaction event carried out by the mobile terminal via the NFC chip; when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; and sending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing the consumption situation of the transaction event to a user. [0011]Preferably, sending the transaction message to a JAVA module and starting up a corresponding JAVA application further comprises: the JAVA module receiving the transaction message and invoking a PUSH interface to start up the corresponding JAVA application. [0012]Preferably, invoking a PUSH interface to start up the corresponding JAVA application further comprises: acquiring PUSH register information about the application from a set PUSH register information list; and parsing the PUSH register information about the application and starting up the corresponding JAVA application. [0013]The present invention provides a mobile terminal in which an NFC chip is integrated, comprising a JAVA module and further comprising a monitoring module, an acquiring module, a sending module, and a display module, wherein[0014]the monitoring module is used for monitoring a transaction event carried out by the mobile terminal via the NFC chip; the acquiring module is used for acquiring a transaction message regarding the transaction event sent by a UICC via the NFC chip after the monitoring module monitors the transaction event; the sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application; and the display module is used for providing the consumption situation regarding the transaction event to a user. [0015]Preferably, this mobile terminal further comprises a JAVA virtual machine, wherein[0016]the JAVA module is further used for receiving the transaction message and starting up the JAVA virtual machine; and the JAVA virtual machine is used for invoking a PUSH interface to start up the corresponding JAVA application. [0017]Preferably, the JAVA virtual machine is further used for acquiring PUSH register information about the application from a set PUSH register information list; and parsing the PUSH register information about the application and starting up the corresponding JAVA application. [0018]As compared to the related art, in the above technical solution according to the present invention, the transaction message sent by the UICC via the NFC chip is used to activate the PUSH function of JAVA and start up a relevant JAVA application, thereby realizing the purpose of automatically starting up the application, thus automatically displaying the consumption situation to the user and enhancing user experience. BRIEF DESCRIPTION OF DRAWINGS [0019]FIG. 1 is a schematic diagram of the process of using an NFC electronic wallet application to consume in the related art; [0020]FIG. 2 is a schematic diagram of the working principle of using an NFC electronic wallet application to consume in the related art; [0021]FIG. 3 is a flowchart of an application method for a mobile terminal electronic wallet according to the embodiments of the present invention; [0022]FIG. 4 is a flowchart of starting up PUSH when a mobile terminal carries out a transaction event according to the embodiments of the present invention; [0023]FIG. 5 is a flowchart of the process of starting up an application by PUSH according to the embodiments of the present invention; and [0024]FIG. 6 is a block diagram of a mobile terminal according to the embodiments of the present invention. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0025]The main concept of the present invention lies in: when the mobile terminal uses the electronic wallet to consume, the transaction message sent by the UICC via the NFC chip is used to activate the PUSH function of JAVA and start up the relevant JAVA application, so as to realize the purpose of automatically starting up the application. It needs to be noted that a JAVA application to be automatically started up needs to be installed on the mobile terminal according to the embodiments of the present invention, and at the same time, this application is PUSH registered. [0026]In order to make the object, technical solution and advantages of the present invention more clear, the present invention will be further described in detail in conjunction with the accompanying drawings and particular embodiments. [0027]FIG. 3 is a flowchart of an application method for a mobile terminal electronic wallet according to the embodiments of the present invention, and as shown in the figure, this method includes:[0028]in step S302, it is to monitor a transaction event carried out by the mobile terminal via the NFC chip. [0029]In step S304, when a transaction event happens, it is to acquire a transaction message regarding the transaction event sent by the UICC via the NFC chip. [0030]In step S306, it is to send the transaction message to a JAVA module, start up a corresponding JAVA application, and provide the consumption situation of the transaction event to a user. [0031]Hereinafter, the above processing details will be described in detail in conjunction with FIG. 4 and FIG. 5. [0032]FIG. 4 is a flowchart of starting up PUSH when a mobile terminal carries out a transaction event according to the embodiments of the present invention. Hereinafter, a mobile phone is taken as an example for description. As shown in FIG. 4, this processing flow includes:[0033]in step S401, it is to activate the NFC chip. [0034]In step S402, the platform starts to monitor a card swiping event and registers for a callback function A, and A is mainly used for sending message to the upper application, such as transaction message. [0035]In step S403, the POS machine sends a transaction request to carry out a consumption operation. [0036]In step S404, the mobile phone responds and feeds back the information of whether the operation is successful to the POS machine. [0037]In step S405, the UICC sends message to the NFC chip. [0038]In step S406, after having received the message, the NFC chip will start up the callback function A registered in the step S402, and if no message is received, no operation will be performed. [0039]In step S407, it is to start up the virtual machine and application and send the message to the JAVA module. [0040]The above processing corresponds to the steps S302 and S304. [0041]FIG. 5 is a flowchart of the process of starting up an application by PUSH according to the embodiments of the present invention. It needs to be noted that the self-starting application must have been PUSH registered, and the register information is stored into a PUSH register information list in the JAVA module. As shown in FIG. 5, this processing flow includes:[0042]in step S501, the JAVA module receives message. [0043]In step S502, the JAVA module starts up the JAVA virtual machine. [0044]In step S503, the JAVA virtual machine acquires the PUSH register information about the application from the PUSH register information list. [0045]In step S504, the JAVA virtual machine parses the PUSH register information about the application and sets the information about the application to be started up. [0046]In step S505, it is to start up the JAVA client application. [0047]In step S506, it is to provide the consumption situation about the transaction event to the user, for example, it is to prompt the user whether to display the consumption situation on the screen of the mobile terminal, if the user selects displaying, then it is to display the balance of the mobile phone wallet on the screen, etc. [0048]The above processing corresponds to step S306. [0049]After the above processing, the consumption situation can be prompted to the user automatically, enhancing the user experience. [0050]FIG. 6 is a block diagram of a mobile terminal in which an NFC chip is integrated according to the embodiments of the present invention. As shown in FIG. 6, this mobile terminal comprises: a monitoring module 10, an acquiring module 20, a sending module 30, and a display module 40, wherein[0051]the monitoring module 10 is used for monitoring a transaction event carried out by the mobile terminal via the NFC chip. [0052]The acquiring module 20 is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after the monitoring module 10 monitors the transaction event. [0053]The sending module 30 is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application. [0054]The display module 40 is used for providing the consumption situation regarding the transaction event to a user. [0055]Moreover, this mobile terminal further comprises: a JAVA module for receiving the transaction message and starting up a JAVA virtual machine; and the JAVA virtual machine for invoking a PUSH interface to start up the corresponding JAVA application. In particular, the JAVA virtual machine acquires PUSH register information about the application from a preset PUSH register information list; and parses the PUSH register information about the application and starts up the corresponding JAVA application. [0056]In summary, in the above technical solution according to the present invention, the transaction message sent by the UICC via the NFC chip is used to activate the PUSH function of JAVA and start up a relevant JAVA application, thereby realizing the purpose of automatically starting up the application, automatically displaying the consumption situation to the user and enhancing user experience. [0057]Above description is only to illustrate the preferred embodiments but not to limit the present invention. Various alternations and changes to the present invention are apparent to those skilled in the art. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the scope defined by the claims of the present invention.(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端电子钱包的应用方法及移动终端。 相关技术背景 [0002] 随着近场通信(NFC)技术的发展,近场消费也发生了显着变化。 手机等移动终端成为安全、方便、快捷、时尚的非接触式支付购票工具。 移动终端变成交通卡和银行卡,像刷交通卡和银行卡一样刷手机消费。 人们尤其喜欢NFC非接触式支付的易用性、方便性和快捷性,并希望不再随身携带钱包。 无需出示支付卡,只需让移动终端靠近设备终端即可完成交易。 [0003] 利用NFC技术实现近场消费的解决方案主要有: 1.仿形粘贴卡,将令牌粘贴在手机上,如重庆市的掌上银行业务。 2. SIMpass,即双SIM卡,如握奇解决方案; 3、NFC,手机中集成了NFC芯片,不支持单线协议(SWP)SIM卡; 4. eNFC,其中支持SWP协议的芯片和SIM卡必须集成; 5、2.4G射频(简称RF)SIM卡,SIM卡内集成2.4G通信模块,直接换SIM卡即可。 在这种情况下,支持SWP协议的芯片和SIM卡需要集成eNFC,这是目前非常流行的技术方案。 [0004] 由于NFC具有广阔的市场前景,移动运营商正在积极推动这一产业链的发展,电子钱包和电子票务业务尤为看重。 目前使用NFC电子钱包消费的流程如图1所示,激活手机的NFC芯片后,手机处于卡模拟状态时,可以通过POS机实现小额支付功能 . [0005] 参考图1,POS机发起消费请求,NFC芯片将请求转发给SIM卡,SIM卡响应,交易结束后,用户可以通过以下方式查看手机钱包交易情况 打开 JAVA 客户端。 [0006] 图2是使用NFC电子钱包消费的工作原理示意图,参见图2,它包括通用集成电路卡(UICC)、NFC射频芯片(MicroRead)和手机处理器。 与应用相关的部分完全放在智能SIM卡中,即UICC,MicroRead集成在手机主板中。 MicroRead通过UART接口与手机处理器通信,通过SWP协议与UICC中的应用部分通信。 手机与POS机交易完成后,UICC可以通过MicroRead向手机处理器发送消息。 [0007] 上述操作存在一个问题:假设手机处于待机界面,当手机进行交易后,用户会习惯性地查看电子钱包余额,而目前应用执行 市面上的手动查询,用户要先输入JAVA再启动应用,非常影响用户体验。 [0008] 综上所述,可知电子钱包的余额只能人工查询,无法自动显示的问题一直存在于相关技术中,因此,有必要提出一种改进的技术手段来解决该问题。 发明内容 [0009] 本发明是针对相关技术中电子钱包余额只能人工查询,不能自动显示的问题而提出的,为此,本发明的主要目的在于提供一种应用方法 一种移动终端电子钱包及移动终端,其中 [0010]本发明提供了一种移动终端集成近场通信(NFC)芯片的移动终端电子钱包的应用方法,包括:通过NFC芯片监听移动终端进行的交易事件; 当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息; 将交易消息发送给JAVA模块,启动相应的JAVA应用,将交易事件的消费情况提供给用户。 [0011] 优选地,向JAVA模块发送交易消息并启动相应的JAVA应用还包括: JAVA模块接收交易消息并调用PUSH接口启动相应的JAVA应用。 [0012] 优选地,调用PUSH接口启动对应的JAVA应用还包括: 从设置的PUSH注册信息列表中获取该应用的PUSH注册信息; 解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。 [0013] 本发明提供了一种集成有NFC芯片的移动终端,包括JAVA模块,还包括监控模块、获取模块、发送模块和显示模块,其中, [0014] 监听模块用于监听移动终端通过NFC芯片进行的交易事件; 获取模块,用于在监听模块监听到交易事件后,通过NFC芯片获取UICC发送的交易事件的交易消息; 发送模块,用于将交易消息发送给JAVA模块,并启动相应的JAVA应用程序; 显示模块用于向用户提供交易事件的消费情况。 [0015] 优选地,该移动终端还包括JAVA虚拟机,其中 [0016] JAVA模块还用于接收交易消息和启动JAVA虚拟机。 JAVA虚拟机用于调用PUSH接口启动相应的JAVA应用。 [0017] 优选地,所述JAVA虚拟机还用于从设置的PUSH注册信息列表中获取应用程序的PUSH注册信息; 解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。 [0018] 与相关技术相比,本发明的上述技术方案中,利用UICC通过NFC芯片发送的交易消息,来激活JAVA的PUSH功能,启动相关的JAVA应用,从而实现了目的 自动启动应用,自动向用户展示消费情况,提升用户体验。 附图说明 [0019] 图1为相关技术中使用NFC电子钱包应用进行消费的流程示意图; [0020] 图2为相关技术中使用NFC电子钱包应用进行消费的工作原理示意图; [0021] 图3为本发明实施例的移动终端电子钱包的应用方法流程图; [0022] 图4为本发明实施例移动终端进行交易事件时启动PUSH的流程图; [0023] 图5是根据本发明实施例的通过PUSH启动应用程序的过程的流程图; 和 [0024] 图6是根据本发明实施例的移动终端的框图。 本发明的优选实施例 [0025] 本发明的主要思想在于:移动终端使用电子钱包进行消费时,利用UICC通过NFC芯片发送的交易报文,激活JAVA的PUSH功能,启动相关的JAVA应用,从而 从而实现应用自动启动的目的。 需要说明的是,本发明实施例的移动终端需要安装一个自动启动的JAVA应用,同时该应用是PUSH注册的。 [0026] 为使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及具体实施例对本发明进行进一步详细说明。 [0027] 图3为本发明实施例提供的一种移动终端电子钱包的应用方法流程图,如图所示,该方法包括: [0028]在步骤S 302 ,是监听移动终端通过NFC芯片进行的交易事件。 [0029] 在步骤S 304 ,当交易事件发生时,通过NFC芯片获取UICC发送的交易事件的交易消息。 [0030] 在步骤S 306 ,就是将交易消息发送给一个JAVA模块,启动相应的JAVA应用程序,将交易事件的消费情况提供给用户。 [0031] 下面结合图4和图5对上述处理细节进行详细说明。 [0032]图4为本发明实施例移动终端进行交易事件时启动PUSH的流程图。 下面以手机为例进行说明。 如图4所示,该处理流程包括: [0033]在步骤S 401 ,就是激活NFC芯片。 [0034] 在步骤S 402 ,平台开始监听一个刷卡事件,注册一个回调函数A,A主要用于向上层应用发送消息,比如交易消息。 [0035] 在步骤S 403 ,POS机发送交易请求进行消费操作。 [0036] 在步骤S 404 ,手机响应并向POS机反馈操作是否成功信息。 [0037] 在步骤S 405 ,UICC向NFC芯片发送消息。 [0038] 在步骤S 406 ,NFC芯片收到消息后,会启动步骤S中注册的回调函数A 402 , 如果没有收到消息,则不会执行任何操作。 [0039] 在步骤S 407 ,就是启动虚拟机和应用,向JAVA模块发送消息。 [0040] 以上处理对应步骤S 302 和小号 304 . [0041] 图5是根据本发明实施例的通过PUSH启动应用程序的过程的流程图。 需要注意的是,自启动应用必须已经PUSH注册过,注册信息存储在JAVA模块中的一个PUSH注册信息列表中。 如图5所示,该处理流程包括: [0042]在步骤S 501 ,JAVA模块接收消息。 [0043] 在步骤S 502 ,JAVA模块启动JAVA虚拟机。 [0044] 在步骤S 503 ,JAVA虚拟机从PUSH寄存器信息列表中获取应用程序的PUSH寄存器信息。 [0045] 在步骤S 504 ,JAVA虚拟机解析应用程序的PUSH寄存器信息,设置要启动的应用程序信息。 [0046] 在步骤S 505 ,就是启动JAVA客户端应用程序。 [0047] 在步骤S 506 ,就是向用户提供交易事件的消费情况,比如提示用户是否在移动端的屏幕上显示消费情况,如果用户选择显示,则显示 屏幕上的手机钱包余额等。 [0048] 以上处理对应步骤S 306 . [0049] 经过上述处理后,可以自动向用户提示消费情况,提升用户体验。 [0050] 图6是根据本发明实施例的集成有NFC芯片的移动终端的框图。 如图6所示,该移动终端包括: 监控模块 10 , 获取模块 20 , 发送模块 30 , 和一个显示模块 40 , 其中 [0051]监控模块 10 用于监听移动终端通过NFC芯片进行的交易事件。 [0052] 获取模块 20 用于在监控模块之后通过NFC芯片获取UICC发送的交易事件的交易消息 10 监听事务事件。 [0053] 发送模块 30 用于向JAVA模块发送交易消息,并启动相应的JAVA应用程序。 [0054] 显示模组 40 用于向用户提供交易事件的消费情况。 [0055] 进一步地,该移动终端还包括: JAVA模块,用于接收交易消息并启动JAVA虚拟机; JAVA虚拟机调用PUSH接口启动相应的JAVA应用程序。 具体地,JAVA虚拟机从预设的PUSH注册信息列表中获取应用程序的PUSH注册信息; 并解析应用程序的PUSH注册信息,启动对应的JAVA应用程序。 [0056]综上所述,在本发明的上述技术方案中,利用UICC通过NFC芯片发送的交易消息来激活JAVA的PUSH功能,启动相关的JAVA应用,从而实现自动启动的目的 应用,自动向用户展示消费情况,提升用户体验。 [0057] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 本发明的各种更改和变化对于本领域的技术人员来说是显而易见的。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.399 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.411 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.412 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101789151A(String), EP2500875A1(String), EP2500875A4(String), US20120259775A1(String), WO2010148737A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.413 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101789151A(String), EP2500875A1(String), EP2500875A4(String), US20120259775A1(String), WO2010148737A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.414 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.415 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120259775A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101789151A(String), EP2500875A1(String), EP2500875A4(String), US20120259775A1(String), WO2010148737A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270719(Integer), CN101789151A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.438 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.439 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270719(Integer), EP2500875A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.449 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.450 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270719(Integer), EP2500875A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.459 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270719(Integer), US20120259775A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.469 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270719(Integer), WO2010148737A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.479 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120259775A1(String), US20120259775A1(String), 1349884800(Integer), 270719(Integer), 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.491 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.492 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), GUI, ZUHONG(String), 中兴通讯股份有限公司(String), GUI ZUHONG(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.493 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.494 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.495 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185044(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.496 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185044(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUI, ZUHONG(String), GUI ZUHONG(String), 0(Integer), 1681975569(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185044(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75960(Integer), 2(Integer), 185044(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.526 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.528 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.529 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.531 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.539 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.540 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.541 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.542 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.543 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185044(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.551 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.552 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9952741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.554 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal application icon management method and mobile terminal(String), 移动终端应用图标管理方法及移动终端(String), US9952741B2(String), Disclosed are a mobile terminal application icon management method and a mobile terminal. The mobile terminal application icon management method comprises: presetting class information about an application, and establishing a mapping relation table among an application class, a screen serial number of a display screen and an application icon; receiving an object moving instruction, obtaining regular pattern information corresponding to a moved object according to the object moving instruction, and displaying the regular pattern information; and after the moved object is successfully moved to the corresponding region of a regular pattern, updating the corresponding mapping relation table among the application class, the screen serial number of a display screen and the application icon. The present invention simplifies the management operation process of an application icon, and achieves batch management and multimodal management of an application icon, thereby greatly facilitating the management operation of a user in respect of an application icon.(String), 本发明公开了一种移动终端应用图标管理方法及移动终端。 移动终端应用图标管理方法,包括:预先设置应用的类信息,建立应用类、显示屏的屏序号和应用图标之间的映射关系表; 接收对象移动指令,根据对象移动指令获取移动对象对应的规则图案信息,并显示规则图案信息; 移动对象成功移动到规则图案的对应区域后,更新应用类、显示屏的屏序号和应用图标之间对应的映射关系表。 本发明简化了应用程序图标的管理操作流程,实现了应用程序图标的批量管理和多模式管理,极大地方便了用户对应用程序图标的管理操作。(String), US14/382592(String), 1336924800(Integer), US9952741B2(String), 1524499200(Integer), 1524499200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 15(Integer), CN102236525A | CN102306080A | CN102306084A | CN102360266A | CN102364438A | EP2426898A2 | US20040155907A1 | US20070050811A1 | US20100333030A1 | US20110258582A1 | US20120052918A1 | US5544302A | US7068288B1 | US7350158B2 | US7693877B1(String), 8(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.564 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185045(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.566 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.567 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\23ad2f6e14b64e7db92ed0a068aa5773.png(String), 185045(Integer), 23ad2f6e14b64e7db92ed0a068aa5773.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.576 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.577 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.578 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal application icon management method and mobile terminal(String), 移动终端应用图标管理方法及移动终端(String), US9952741B2(String), Disclosed are a mobile terminal application icon management method and a mobile terminal. The mobile terminal application icon management method comprises: presetting class information about an application, and establishing a mapping relation table among an application class, a screen serial number of a display screen and an application icon; receiving an object moving instruction, obtaining regular pattern information corresponding to a moved object according to the object moving instruction, and displaying the regular pattern information; and after the moved object is successfully moved to the corresponding region of a regular pattern, updating the corresponding mapping relation table among the application class, the screen serial number of a display screen and the application icon. The present invention simplifies the management operation process of an application icon, and achieves batch management and multimodal management of an application icon, thereby greatly facilitating the management operation of a user in respect of an application icon.(String), 本发明公开了一种移动终端应用图标管理方法及移动终端。 移动终端应用图标管理方法,包括:预先设置应用的类信息,建立应用类、显示屏的屏序号和应用图标之间的映射关系表; 接收对象移动指令,根据对象移动指令获取移动对象对应的规则图案信息,并显示规则图案信息; 移动对象成功移动到规则图案的对应区域后,更新应用类、显示屏的屏序号和应用图标之间对应的映射关系表。 本发明简化了应用程序图标的管理操作流程,实现了应用程序图标的批量管理和多模式管理,极大地方便了用户对应用程序图标的管理操作。(String), US14/382592(String), 1336924800(Integer), US9952741B2(String), 1524499200(Integer), 1524499200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 15(Integer), CN102236525A | CN102306080A | CN102306084A | CN102360266A | CN102364438A | EP2426898A2 | US20040155907A1 | US20070050811A1 | US20100333030A1 | US20110258582A1 | US20120052918A1 | US5544302A | US7068288B1 | US7350158B2 | US7693877B1(String), \20230420\23ad2f6e14b64e7db92ed0a068aa5773.png(String), 8(Integer), 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.586 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.588 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 1. A method for application icon management in a mobile terminal, comprising:presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;receiving an object moving instruction;determining, according to the object moving instruction, an object to be moved to be a class of applications or an icon of an application;acquiring information on a rule graph corresponding to the object to be moved according to the object moving instruction, by:in response to determining the object to be moved to be the class of the applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens;in response to determining the object to be moved to be the icon of the application, acquiring information on a double-layer annular graph marked with the sequence numbers of the screens and classes of applications;calculating space remaining in each of the screens;comparing the space remaining in the each of the screens with space to be occupied by the object to be moved;displaying the information on the rule graph, by:in response to determining the object to be moved to be the class of the applications, displaying the single-layer annular graph marked with the sequence numbers of the screens, by showing a sequence number of a screen in bright yellow when there is enough space remaining in the screen for storing icons of the applications belonging to the class of the applications, and showing the sequence number of the screen in black when the screen does not have sufficient free space for storing the icons of the applications belonging to the class of the applications;in response to determining the object to be moved to be the icon of the application, displaying the double-layer annular graph marked with the sequence numbers of the screens and the classes of applications, by showing a sequence number of a screen and any class of applications in the screen in bright yellow when there is enough space remaining in the screen for storing the icon of the application, and showing the sequence number of the screen and the any class of applications in the screen in black when the screen does not have sufficient free space for storing the icon of the application;after the class of the applications is moved to and released in an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen is shown in bright yellow;or, after the icon of the application is moved to and released in an area containing a sequence number of a target screen or an area containing a target class of applications contained in a target screen in the double-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen or the target class of applications is shown in bright yellow;in response to determining that there is enough space remaining in the target screen for storing the object to be moved, highlighting the area containing the sequence number of the target screen or the area containing the target class of applications, indicating that the object to be moved is moved successfully;updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move;when no object is moved within a preset period of time, cancelling display of the rule graph.(String), 1、一种移动终端应用图标管理方法,包括:预先设置应用所属类别信息,建立应用类别、屏幕、应用之间的映射关系表;接收物体移动指令;根据对象移动指令确定待移动对象为应用类别或应用图标;根据物体移动指令获取待移动物体对应的规则图信息,通过:响应于确定移动对象为应用类别,获取单层环状图信息,该环状图标有屏幕序号;响应于确定移动对象为应用程序的图标,获取标记有应用程序的屏幕序号和类别的双层环形图信息;计算每个屏幕中剩余的空间;将每个屏幕中剩余的空间与要移动的对象占用的空间进行比较;通过以下方式在规则图上显示信息:响应确定移动对象为应用类别,显示单层环状图,标记屏幕序号,当剩余空间足够时,将屏幕序号显示为亮黄色在用于存储属于应用程序类别的应用程序图标的屏幕中,当屏幕没有足够的可用空间用于存储属于应用程序类别的应用程序图标时,以黑色显示屏幕序号;响应于确定待移动对象为应用程序的图标,通过显示屏幕序号和任意类别,显示标记有屏幕序号和应用程序类别的双层环形图当屏幕中有足够的剩余空间用于存储应用程序的图标时,屏幕中的应用程序以亮黄色显示,当屏幕没有足够的空间时,以黑色显示屏幕的序列号和屏幕中的任何类别的应用程序用于存储应用程序图标的可用空间;在单层环形图中将应用类移动到包含目标屏幕序号的区域释放后,判断目标屏幕是否剩余足够的空间用于存储移动对象,通过检测目标屏幕的序号是否显示为亮黄色;或者,应用程序的图标移动到双层环图中包含目标屏幕序号的区域或包含目标屏幕包含的应用程序的目标类的区域并释放后,判断是否有通过检测目标屏幕或目标应用类别的序号是否显示为亮黄色,在目标屏幕中剩余足够的空间用于存储待移动的对象;响应于确定目标屏幕中有足够的剩余空间用于存储待移动对象,突出显示包含目标屏幕序号的区域或包含目标应用类别的区域,指示待移动对象移动成功;在将待移动对象成功移动到规则图上的区域后,根据移动更新应用类、屏幕、应用之间的映射关系表;当在预设时间内没有物体移动时,取消显示规则图。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 2. The method according to claim 1, wherein the establishing a table of mapping relation among a class of applications, a screen, and an application comprises:respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.(String), 2.根据权利要求1所述的方法,其中建立一类应用、屏幕、应用之间的映射关系表包括:分别建立一类应用程序到屏幕的映射表、一类应用程序到一类应用程序的映射表和一类应用程序到屏幕的映射表。屏幕中的应用程序类别。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 3. The method according to claim 2, wherein the updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move comprises:after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on a current screen and application class layout displayed on the target screen; orafter the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen.(String), 3.根据权利要求2所述的方法,其中将待移动对象成功移动到规则图上的区域后,根据移动更新一类应用程序、屏幕、应用程序的映射关系表包括:当待移动类应用成功移动到单层环形图中目标屏幕序号所在区域后,更新类应用到屏幕的映射表。刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局;或者应用的待移动图标被成功移动到双层环图中目标屏幕或目标应用类的序号区域后,更新应用到类应用的映射表,或将应用程序映射到屏幕的表;刷新当前屏幕上显示的应用程序图标布局和目标屏幕上显示的应用程序图标布局。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.589 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 4. The method according to claim 2, further comprising: after the presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application,updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application.(String), 4.根据权利要求2所述的方法,还包括:在预先设置应用所属类别的信息,并建立应用类别、屏幕和应用之间的映射关系表之后,根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 5. A mobile terminal, comprising:a processor; andmemory storing instructions executable by the processor,wherein the processor isconfigured for:presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;receiving an object moving instruction;determining, according to the object moving instruction, an object to be moved to be a class of applications or an icon of an application;acquiring information on a rule graph corresponding to the object to be moved according to the object moving instruction, by:in response to determining the object to be moved to be the class of the applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens;in response to determining the object to be moved to be the icon of the application, acquiring information on a double-layer annular graph marked with the sequence numbers of the screens and classes of applications;calculating space remaining in each of the screens;comparing the space remaining in the each of the screens with space to be occupied by the object to be moved;displaying the information on the rule graph, by:in response to determining the object to be moved to be the class of the applications, displaying the single-layer annular graph marked with the sequence numbers of the screens, by showing a sequence number of a screen in bright yellow when there is enough space remaining in the screen for storing icons of the applications belonging to the class of the applications, and showing the sequence number of the screen in black when the screen does not have sufficient free space for storing the icons of the applications belonging to the class of the applications;in response to determining the object to be moved to be the icon of the application, displaying the double-layer annular graph marked with the sequence numbers of the screens and the classes of applications, by showing a sequence number of a screen and any class of applications in the screen in bright yellow when there is enough space remaining in the screen for storing the icon of the application, and showing the sequence number of the screen and the any class of applications in the screen in black when the screen does not have sufficient free space for storing the icon of the application;after the class of the applications is moved to and released in an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen is shown in bright yellow;or, after the icon of the application is moved to and released in an area containing a sequence number of a target screen or an area containing a target class of applications contained in a target screen in the double-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen or the target class of applications is shown in bright yellow;in response to determining that there is enough space remaining in the target screen for storing the object to be moved, highlighting the area containing the sequence number of the target screen or the area containing the target class of applications, indicating that the object to be moved is moved successfully;updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move;when no object is moved within a preset period of time, cancelling display of the rule graph.(String), 5.移动终端,包括:处理器;和存储器存储处理器可执行的指令,其中处理器是配置为:预先设置应用所属类别信息,建立应用类别、屏幕、应用之间的映射关系表;接收物体移动指令;根据对象移动指令确定待移动对象为应用类别或应用图标;根据物体移动指令获取待移动物体对应的规则图信息,通过:响应于确定移动对象为应用类别,获取单层环状图信息,该环状图标有屏幕序号;响应于确定移动对象为应用程序的图标,获取标记有应用程序的屏幕序号和类别的双层环形图信息;计算每个屏幕中剩余的空间;将每个屏幕中剩余的空间与要移动的对象占用的空间进行比较;通过以下方式在规则图上显示信息:响应确定移动对象为应用类别,显示单层环状图,标记屏幕序号,当剩余空间足够时,将屏幕序号显示为亮黄色在用于存储属于应用程序类别的应用程序图标的屏幕中,当屏幕没有足够的可用空间用于存储属于应用程序类别的应用程序图标时,以黑色显示屏幕序号;响应于确定待移动对象为应用程序的图标,通过显示屏幕序号和任意类别,显示标记有屏幕序号和应用程序类别的双层环形图当屏幕中有足够的剩余空间用于存储应用程序的图标时,屏幕中的应用程序以亮黄色显示,当屏幕没有足够的空间时,以黑色显示屏幕的序列号和屏幕中的任何类别的应用程序用于存储应用程序图标的可用空间;在单层环形图中将应用类移动到包含目标屏幕序号的区域释放后,判断目标屏幕是否剩余足够的空间用于存储移动对象,通过检测目标屏幕的序号是否显示为亮黄色;或者,应用程序的图标移动到双层环图中包含目标屏幕序号的区域或包含目标屏幕包含的应用程序的目标类的区域并释放后,判断是否有通过检测目标屏幕或目标应用类别的序号是否显示为亮黄色,在目标屏幕中剩余足够的空间用于存储待移动的对象;响应于确定目标屏幕中有足够的剩余空间用于存储待移动对象,突出显示包含目标屏幕序号的区域或包含目标应用类别的区域,指示待移动对象移动成功;在将待移动对象成功移动到规则图上的区域后,根据移动更新应用类、屏幕、应用之间的映射关系表;当在预设时间内没有物体移动时,取消显示规则图。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 6. The mobile terminal according to claim 5, wherein the establishing a table of mapping relation among a class of applications, a screen, and an application comprises:respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.(String), 6.根据权利要求5所述的移动终端,其中建立一类应用、屏幕、应用之间的映射关系表包括:分别建立一类应用程序到屏幕的映射表、一类应用程序到一类应用程序的映射表和一类应用程序到屏幕的映射表。屏幕中的应用程序类别。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 7. The mobile terminal according to claim 6, wherein the updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move comprises:after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on a current screen and application class layout displayed on the target screen; orafter the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen.(String), 7.根据权利要求6所述的移动终端,其中将待移动对象成功移动到规则图上的区域后,根据移动更新一类应用程序、屏幕、应用程序的映射关系表包括:当待移动类应用成功移动到单层环形图中目标屏幕序号所在区域后,更新类应用到屏幕的映射表。刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局;或者应用的待移动图标被成功移动到双层环图中目标屏幕或目标应用类的序号区域后,更新应用到类应用的映射表,或将应用程序映射到屏幕的表;刷新当前屏幕上显示的应用程序图标布局和目标屏幕上显示的应用程序图标布局。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.590 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185045(Integer), 8. The mobile terminal according to claim 6, wherein the processor is further configured for: after presetting the information on the class to which the application belongs, and establishing the table of mapping relation among a class of applications, a screen, and an application,updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application.(String), 8.根据权利要求6所述的移动终端,其中处理器还用于:在预先设置应用所属类别的信息,并建立应用类别、屏幕和应用之间的映射关系表之后,根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.664 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.665 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185045(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of mobile terminal techniques, and in particular to a method for application icon management in a mobile terminal, and a mobile terminal. BACKGROUND [0002]With the upgrading of communication products, a mobile terminal such as a mobile phone or a Personal Digital Assistant (PDA) has become an indispensable communication tool, and various convenient and recreational applications appear on a mobile terminal. [0003]On an existing mobile terminal, icons of various applications are either displayed all in one screen or displayed in multiple screens. Although icon display by multiple screens can facilitate a user in finding an application to some extent, but an existing method for application icon management in a mobile terminal has the following disadvantages: [0004](1) display of icons of various applications is not managed by class; [0005](2) one application icon management operation can handle only one icon at a time, instead of batch management of multiple icons; [0006](3) the icon of an application can be moved only after the application is installed; [0007](4) a user can complete a move of an icon of an application only after dragging the icon to a target screen. SUMMARY [0008]In view of this, it is desired that embodiments of the disclosure provide a method for application icon management in a mobile terminal, and a mobile terminal, capable of implementing batch management and multi-mode management of icons of applications of a mobile terminal. [0009]To this end, the disclosure provides a method for application icon management in a mobile terminal, including steps of: [0010]presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application; [0011]receiving an icon object moving instruction, acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph; and [0012]updating, after successfully moving the icon object to be moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application according to the move. [0013]In an embodiment, the step of establishing a table of mapping relation among a class of applications, a screen, and an application may include a step of: [0014]respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen. [0015]In an embodiment, the steps of acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph may include steps of: [0016]when it is determined according to the icon object moving instruction that the icon object to be moved is a class of applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens, and displaying the information on the rule graph, wherein [0017]after the class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, it is determined whether there is enough space remaining in the target screen for storing the class of applications to be moved; and [0018]when there is enough space remaining in the target screen for storing the class of applications to be moved, the class of applications to be moved is moved to the area containing the sequence number of the target screen successfully. [0019]In an embodiment, the steps of acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph may include steps of: [0020]when it is determined according to the icon object moving instruction that the icon object to be moved is an icon of an application, acquiring information on a double-layer annular graph marked with sequence numbers of screens and classes of applications, and displaying the information on the rule graph, wherein [0021]after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, it may be determined whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and [0022]when there is enough space remaining in the target screen or the screen containing the target class of applications for storing the to-be-moved icon of the application, the to-be-moved icon of the application is moved to the area containing the sequence number of the target screen or the target class of applications successfully. [0023]In an embodiment, the step of updating, after successfully moving the icon object to be moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application according to the move may include steps of: [0024]after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on the current screen and application class layout displayed on the target screen; or [0025]after the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen. [0026]In an embodiment, the method may further include a step of: after the steps of presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application, [0027]updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application. [0028]The disclosure further provides a mobile terminal, including [0029]a presetting module configured for: presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application; [0030]a managing module configured for: receiving an icon object moving instruction; acquiring information on a single-layer annular graph or a double-layer annular graph according to the icon object moving instruction; and updating, after successfully moving the icon object to be moved to an area on the single-layer annular graph or the double-layer annular graph, a table of mapping relation among a class of applications, a screen, and an application according to the move; and [0031]a displaying module configured for: displaying the information on the rule graph. [0032]In an embodiment, the managing module may be further configured for: [0033]after a class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the class of applications to be moved; [0034]after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, determining whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and [0035]updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application. [0036]In an embodiment, the displaying module may be further configured for: [0037]refreshing application class layout and application icon layout displayed on a current screen and on a target screen according to the table of mapping relation among a class of applications, a screen, and an application updated by the managing module. [0038]In an embodiment, the mobile terminal may further include an installing module configured for: installing a new application; and after the new application is installed successfully, sending the managing module an icon management message corresponding to the installation, wherein [0039]the managing module may be further configured for: updating a table mapping an application to a class of applications according to the icon management message; and [0040]the displaying module may be further configured for: displaying icons of applications by class according to the table mapping an application to a class of applications updated by the managing module. [0041]With the method for application icon management in a mobile terminal according to the disclosure, icons of installed applications are managed rapidly by screen or by class on a respective rule graph, such that with the disclosure, compared with an existing method for application icon management in a mobile terminal, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user. Moreover, with the disclosure, it is possible to set in an installation phase of a new application a class to which the new application belongs, and directly manage display of the icon of the new application by class, thereby saving any icon display management after the new application is installed. BRIEF DESCRIPTION OF THE DRAWINGS [0042]FIG. 1 is a flowchart of a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0043]FIG. 2 is a flowchart of managing icon-display-by-screen by moving a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0044]FIG. 3 is a flowchart of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0045]FIG. 4 is a schematic diagram of a structure of a single-layer annular graph displayed on a current screen in case an icon object to be moved is a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0046]FIG. 5 is a schematic diagram of a structure of a double-layer annular graph displayed on a current screen in case an icon object to be moved is an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0047]FIG. 6 is a flowchart, in installing a new application, of setting a class to which the new application belongs and directly managing display of the icon of the new application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0048]FIG. 7 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure; and [0049]FIG. 8 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure. [0050]Implementation, features, and advantages of the disclosure will be further described with reference to accompanying drawings in combination with embodiments. DETAILED DESCRIPTION [0051]According to embodiments of the disclosure, information on a class to which an application belongs is preset, and a table of mapping relation among a class of applications, a screen, and an application is established; an icon object moving instruction is received, information on a rule graph corresponding to an icon object to be moved is acquired according to the icon object moving instruction, and the information on the rule graph is displayed; and after the icon object to be moved is successfully moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application is updated according to the move. [0052]A technical solution of the disclosure will be further elaborated with reference to the accompanying drawings in combination with specific embodiments. It should be understood that the specific embodiments described herein are only used to interpret the disclosure instead of limiting the disclosure. [0053]FIG. 1 is a flowchart of a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in FIG. 1, the method includes steps as follows. [0054]In Step S101, information on a class to which an application belongs is preset, and a table of mapping relation among a class of applications, a screen, and an application is established. [0055]In an embodiment, in addition to a default class of applications in a mobile terminal, a new class of applications may be added, and an existing class of applications may be modified or deleted through an application class customizing interface. Then, a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen are established respectively in advance according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen. [0056]The table mapping a class of applications to a screen (Class_Screen) indicates mapping relation between a class of applications and a screen of the mobile terminal (i.e., table Class_Screen hereafter). [0057]The table mapping an application to a class of applications (App_Class) indicates mapping relation between an application and a class of applications (i.e., table App_Class hereafter). [0058]The table mapping an application to a screen (App_Screen) indicates mapping relation between an application and a screen of the mobile terminal ((i.e., table App_Screen hereafter), where an application with its icon stored in the screen is not classified. Main fields of the table Class_Screen are as shown in Table 1, main fields of the table App_Class are as shown in Table 2, and main fields of the table App_Screen are as shown in Table 3. [0059]TABLE 1Fielddescriptiona classthe class contained in the screen with the sequencenumbera sequencethe sequence number of a screen in the mobilenumber of aterminalscreen [0060]TABLE 2Fielddescriptionanan application belonging to the class of applicationsapplicationa classa class of applications contained in a screen of themobile terminal [0061]TABLE 3Fielddescriptionan applicationan unclassified applicationa sequencethe sequence number of a screen in the mobilenumber of a screenterminal [0062]In Step S102, an icon object moving instruction is received, information on a rule graph corresponding to an icon object to be moved is acquired according to the icon object moving instruction, and the information on the rule graph is displayed. [0063]In an embodiment, when it is determined according to the icon object moving instruction that the icon object to be moved is a class of applications, information on a single-layer annular graph marked with sequence numbers of screens is acquired, and the single-layer annular graph is displayed on a current screen. When it is determined according to the icon object moving instruction that the icon object to be moved is an icon of an application, information on a double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and the double-layer annular graph is displayed on a current screen. [0064]In Step S103, after the icon object to be moved is moved successfully to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application is updated according to the move. [0065]In an embodiment, after the icon object to be moved is moved successfully to the area on the rule graph, the table mapping a class of applications to a screen, the table mapping an application to a class of applications, or the table mapping an application to a screen may be updated. [0066]With the method for application icon management in a mobile terminal according to the disclosure, icons of installed applications are managed rapidly by screen or by class on a respective rule graph, such that with the disclosure, compared with an existing method for application icon management in a mobile terminal, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user. [0067]FIG. 2 is a flowchart of managing icon-display-by-screen by moving a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in FIG. 2, the flow of managing icon-display-by-screen by moving a class of applications according to the disclosure includes steps as follows. [0068]In Step S201, an icon object is moved. [0069]In an embodiment, after information on a class to which an application belongs is preset in the mobile terminal, and a table of mapping relation among a class of applications, a screen, and an application is established, an icon object of a class of applications or an icon of an application is dragged into a target screen or a target class of applications. [0070]In Step S202, it is determined according to an icon object moving instruction whether the icon object is a class of applications or an icon of an application. [0071]In an embodiment, when the icon object is moved, the type of the icon object (a class of applications or an icon of an application) needs to be determined in the first place according to the icon object moving instruction, and when the icon object is a class of applications, the flow goes to step S203. [0072]In Step S203, information on a single-layer annular graph marked with sequence numbers of screens is acquired; and space remaining in each screen is calculated and compared with space to be occupied by the class of applications. [0073]In an embodiment, when it is determined that the icon object is a class of applications, information on a single-layer annular graph marked with sequence numbers of screens is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the class of applications. Here, the information on the single-layer annular graph may include a total size of the graph, a total number of screens in the mobile terminal, size of an area containing a sequence number of a screen, an identifier of a color of an area, an identifier of a color of storage space occupied by each class of applications and icons of applications belonging to the each class in a screen, and the like. [0074]In Step S204, the single-layer annular graph marked with sequence numbers of screens is displayed on a current screen. [0075]In an embodiment, the single-layer annular graph displayed here, as shown in FIG. 4, includes 4 screens with sequence numbers 1, 2, 3, 4, respectively; and areas containing the sequence numbers of screens may be distinguished from each other by color. When there is enough space remaining in a screen, as calculated by the mobile terminal, for storing icons of all applications belonging to the class of applications, the sequence number of the screen is shown in bright yellow. When the screen does not have sufficient free space, as calculated by the mobile terminal, for storing icons of applications belonging to the class of applications, the sequence number of the screen is shown in black. Here, sequence numbers of screens 1, 3, 4 are shown in bright yellow, indicating that each of screen 1, screen 3, and screen 4 has sufficient free space for storing icons of all applications belonging to the class of applications. The sequence number of screen 2 is shown in black, indicating that the screen 2 has insufficient free space for storing icons of all applications belonging to the class of applications. [0076]In Step S205, the class of applications is moved into an area containing a sequence number of a target screen in the single-layer annular graph, and is then released. [0077]In Step S206, it is determined whether there is enough space remaining in the target screen for storing the class of applications; if there is, the flow goes to step S207; otherwise if there is insufficient space, the flow goes to Step S211. [0078]In an embodiment, it is detected whether the sequence number of the target screen is shown in a bright yellow font. If the sequence number of the target screen is shown in a bright yellow font, it means that there is enough space remaining in the target screen for storing the class of applications. Otherwise if the sequence number of the target screen is not shown in a bright yellow font, it means that space remaining in the target screen is insufficient for storing the class of applications, and a user may be notified that space remaining in the target screen is insufficient for storing the class of applications. [0079]As shown in FIG. 4, sequence numbers of screens 1, 3, 4 are shown in a bright yellow font, and the sequence number of screen 2 is shown in a black font. A class of applications in the screen 1 can be moved to the area containing the sequence number 4 or the area containing the sequence number 3, but can not be moved to the area containing the sequence number 2. [0080]In Step S207, the area containing the sequence number of the target screen in the single-layer annular graph is highlighted. [0081]In an embodiment, for example, as shown in FIG. 4, if a class of applications in the screen with sequence number 1 is moved to the area containing the sequence number 4, then the area containing the sequence number 4 will be highlighted, indicating that the class of applications is moved successfully. [0082]In Step S208, information on the area containing the sequence number of the target screen is recorded, an icon management message corresponding to the move of the class of applications is sent, and a table Class_Screen is updated. [0083]In an embodiment, after the class of applications is moved successfully, information on the area containing the sequence number of the target screen is recorded, and an icon management message is sent to a managing module of the mobile terminal. The icon management message includes an icon management type MsgType 2, indicating that the current moving operation involves move of a class of applications. After receiving the icon management message, the managing module updates the table Class_Screen, that is, updates the mapping relation between a class of applications and a screen. [0084]In Step S209, application class layout displayed on the current screen and application class layout displayed on the target screen are refreshed. [0085]In an embodiment, displayed layout of any class of applications on the current screen and on the target screen, and of icons of applications belonging to the any class of applications, are refreshed according to the table Class_Screen updated in step S208. [0086]In Step S210, display of the single-layer annular graph is cancelled. [0087]In an embodiment, when no class of applications is moved within a preset period of time, display of the single layer annular graph is cancelled. [0088]In Step S211, a user is notified that space remaining in the target screen is insufficient for storing the class of applications. [0089]If it is determined in Step S206 that space remaining in the target screen is insufficient for storing the class of applications, a notification that space remaining in the target screen is insufficient for storing the class of applications is provided on the current screen. [0090]FIG. 3 is a flowchart of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in FIG. 3, the flow of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application according to the disclosure includes steps as follows. [0091]In Step S301, an icon object is moved. [0092]In an embodiment, after information on a class to which an application belongs is preset in the mobile terminal, and a table of mapping relation among a class of applications, a screen, and an application is established, an icon object of a class of applications or an icon of an application is dragged into a target screen or a target class of applications. [0093]In Step S302, it is determined according to an icon object moving instruction whether the icon object is a class of applications or an icon of an application. [0094]In an embodiment, when the icon object is moved, the type of the icon object (a class of applications or an icon of an application) needs to be determined in the first place according to the icon object moving instruction, and when the icon object is an icon of an application, the flow goes to step S303. [0095]In Step S303, information on a double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the icon of the application. [0096]In an embodiment, when it is determined that the icon object is an icon of an application, information on the double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the icon of the application. [0097]Here, the information on the double-layer annular graph may include: a total size of the graph; a total number of screens in the mobile terminal; any class of applications already in each screen, and a number of classes of applications already in each screen; size of an area containing a class of applications; size of an area containing a sequence number of a screen; an identifier of a color of an area, an identifier of a color of storage space occupied by any class of applications and icons of applications belonging to the class in a screen, and the like. [0098]In Step S304, the double-layer annular graph marked with sequence numbers of screens and classes of applications is displayed on a current screen. [0099]In an embodiment, the double-layer annular graph displayed here, as shown in FIG. 5, includes four classes of applications, namely, everyday, office, game and system. Classes of applications displayed in a same screen occupy continuous areas in the double-layer annular graph and the continuous areas are in the same color. In an embodiment, the two classes of everyday and office are located in screen 1, the game is located in screen 2, the system is located in screen 3, and currently no icon of an application belonging to a class of applications is stored in screen 4. When there is enough space remaining in a screen, as calculated by the mobile terminal, for storing the icon of the application, the sequence number of the screen and any class of applications in the screen are shown in bright yellow. When the screen does not have sufficient free space, as calculated by the mobile terminal, for storing the icon of the application, the sequence number of the screen and any class of applications in the screen are shown in black. Here, the classes “everyday” and “office” and the sequence number “1” of the screen containing the classes “everyday” and “office” are in a bright yellow font; the class “system” and the sequence number “3” of the screen containing the class system are in a bright yellow font too; but class “game” and the sequence number “2” of the screen containing class game are in a black font. This indicates that the icon of the application may be stored in either screen 1 or screen 3, but may not be stored in screen 2, as space remaining in screen 2 is insufficient. [0100]In Step S305, the icon of the application is moved into an area containing a sequence number of a target screen or into an area containing a target class of applications in the double-layer annular graph, and is then released. [0101]In Step S306, it is determined whether the area contains the sequence number of a target screen or contains a target class of applications; If the area contains a target class of applications, the flow goes to Step S307; otherwise if the area contains the sequence number of a target screen, the flow goes to Step S313. [0102]In an embodiment, after the icon of the application is moved into an area containing a sequence number of a screen or containing a class of applications in the double-layer annular graph, and is then released, it is detected whether the area is occupied by a class of applications or a sequence number of a screen. If the area is occupied by a class of applications, the flow goes to Step S307. If the area is occupied by a sequence number of a screen, the flow goes to Step S313. [0103]As shown in FIG. 5, the icon of an application belonging to the class “system” in screen 3 may be moved to an area containing the sequence number “1” or “4”, or to an area containing the class “everyday” or “office” in screen 1 (namely, to an area with a bright yellow font); but cannot be moved to an area containing the sequence number “2” or to an area containing the class “game” (namely, cannot be moved to an area with a black font). [0104]In Step S307, it is determined whether there is enough space remaining in a screen containing the target class of applications for storing the icon of the application; if space remaining in the target screen is sufficient for storing the icon of the application, the flow goes to step S308; otherwise if space remaining in the target screen is insufficient for storing the icon of the application, the flow goes to Step S312. [0105]In an embodiment, it is detected whether the target class of applications is shown in a bright yellow font, if the target class of applications is shown in a bright yellow font, it means that there is enough space remaining for storing the icon of the application. Otherwise if the target class of applications is not shown in a bright yellow font, it means that space remaining is insufficient for storing the icon of the application. [0106]In Step S308, the area containing the target class of applications in the double-layer annular graph is highlighted. [0107]In Step S309, information on the area containing the target class of applications is recorded, and an icon management message corresponding to the move of the icon of the application is sent, and a table of mapping relation corresponding to the move of the icon of the application is updated. [0108]In an embodiment, after the icon of the application is moved successfully, the information on the area containing the target class of applications is recorded, and the icon management message corresponding to the move of the icon of the application is sent to a managing module of the mobile terminal. The icon management message includes an icon management type MsgType 3, indicating that the current moving operation involves move of an icon of an application into a target class of applications. After receiving the icon management message, the managing module of the mobile terminal checks the table App_Class to determine whether a mapping relation between the application and a class of applications exist, i.e., checks whether the application has been classified. If the application has not been classified, then the table App_Screen is called, and a mapping relation between the application and a screen in the table App_Screen is deleted; in addition, the table App_Class is called, and a mapping relation between the application and the target (String), 技术领域 [0001] 本发明涉及移动终端技术领域,尤其涉及一种移动终端中应用图标管理的方法及移动终端。 背景 [0002] 随着通讯产品的更新换代,手机、个人数字助理(Personal Digital Assistant,PDA)等移动终端已经成为不可或缺的通讯工具,各种方便、娱乐性的应用也出现在移动终端上。 [0003] 在现有的移动终端上,各种应用程序的图标要么一屏显示,要么多屏显示。 虽然多屏显示图标可以在一定程度上方便用户查找应用,但是现有的移动终端应用图标管理方法存在以下不足: [0004] (1) 各种应用的图标显示不按类管理; [0005] (2)一次应用图标管理操作一次只能处理一个图标,而不是批量管理多个图标; [0006] (3) 应用程序的图标必须在应用程序安装后才能移动; [0007] (4)用户只有将应用程序的图标拖动到目标屏幕后,才能完成对应用程序图标的移动。 概括 [0008] 有鉴于此,本发明实施例期望提供一种移动终端中的应用程序图标管理方法及移动终端,能够实现对移动终端应用程序图标的批量管理和多模式管理。 [0009] 为此,本发明提供了一种移动终端中应用图标的管理方法,包括以下步骤: [0010] 预先设置应用所属类别信息,建立应用类别、屏幕、应用之间的映射关系表; [0011] 接收图标对象移动指令,根据图标对象移动指令获取待移动图标对象对应的规则图信息,并显示规则图信息; 和 [0012] 将待移动图标对象成功移动到规则图上的区域后,根据移动更新应用类、屏幕、应用之间的映射关系表。 [0013] 在一个实施例中,建立一类应用程序、屏幕和应用程序之间的映射关系表的步骤可以包括以下步骤: [0014] 分别建立一类应用程序到屏幕的映射表、一类应用程序到一类应用程序的映射表和一类应用程序到屏幕的映射表。 屏幕中的应用程序类别。 [0015] 在一个实施例中,根据所述图标对象移动指令获取待移动图标对象对应的规则图信息,并显示所述规则图信息的步骤包括: [0016] 当根据图标对象移动指令确定待移动图标对象为一类应用时,获取标记有屏幕序号的单层环形图信息,并在规则图上显示该信息, 其中 [0017] 将待移动类应用移动到单层环形图中包含目标屏幕序号的区域后,判断目标屏幕中是否剩余足够的空间用于存储待移动类应用 感动; 和 [0018] 当目标屏幕剩余足够的空间用于存储待移动应用类别时,成功将待移动应用类别移动到包含目标屏幕序号的区域。 [0019] 在一个实施例中,根据所述图标对象移动指令获取待移动图标对象对应的规则图信息,并显示所述规则图信息的步骤包括: [0020]当根据图标对象移动指令确定待移动的图标对象为应用程序的图标时,获取标记有屏幕序号和应用程序类别的双层环形图信息,并显示该信息。 规则图,其中 [0021] 待移动的应用程序图标移动到双层环形图中包含目标屏幕或目标类应用程序序号的区域后,可以判断是否有足够的剩余空间。 目标屏幕或包含应用程序目标类的屏幕,用于存储应用程序的待移动图标; 和 [0022] 当目标屏幕或包含目标类应用程序的屏幕剩余足够的空间用于存储应用程序的待移动图标时,将该应用程序的待移动图标移动到包含序列的区域 成功的目标屏幕或目标类应用程序的数量。 [0023] 在一个实施例中,在将待移动图标对象成功移动到规则图上的区域后,根据移动更新应用类别、屏幕和应用之间的映射关系表的步骤可以包括以下步骤: 的: [0024] 当待移动类应用成功移动到单层环形图中目标屏幕序号所在区域后,更新类应用到屏幕的映射表。 刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局; 要么 [0025] 应用的待移动图标被成功移动到双层环图中目标屏幕或目标应用类的序号区域后,更新应用到类应用的映射表 ,或将应用程序映射到屏幕的表; 刷新当前屏幕上显示的应用程序图标布局和目标屏幕上显示的应用程序图标布局。 [0026] 在一个实施例中,该方法还可以包括以下步骤:在预先设置应用所属类别的信息,建立应用类别、屏幕和应用之间的映射关系表的步骤之后, [0027] 根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。 [0028] 本发明还提供一种移动终端,包括 [0029] 预设模块,用于预设应用所属类别的信息,建立应用类别、屏幕和应用之间的映射关系表; [0030] 管理模块,用于接收图标对象移动指令; 根据图标对象移动指令获取单层环状图或双层环状图的信息; 在将待移动图标对象成功移动到单层环状图或双层环状图上的区域后,根据 移动; 和 [0031] 显示模块,用于显示规则图的信息。 [0032] 在一个实施例中,管理模块还可以用于: [0033] 在将待移动类应用移动到单层环形图中包含目标屏幕序号的区域后,判断目标屏幕中是否剩余足够的空间用于存储该类待移动应用。 [0034] 待移动的应用程序图标移动到双层环图中包含目标屏幕或目标类应用程序序号的区域后,判断目标屏幕是否有足够的剩余空间或 包含应用程序目标类的屏幕,用于存储应用程序的待移动图标; 和 [0035]根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。 [0036] 在一个实施例中,显示模块还可以用于: [0037] 根据管理模块更新的应用类、屏幕、应用的映射关系表,刷新当前屏幕和目标屏幕显示的应用类布局和应用图标布局。 [0038] 在一个实施例中,移动终端还可以包括安装模块,用于安装新的应用程序; 在新应用安装成功后,向管理模块发送安装对应的图标管理消息,其中 [0039] 管理模块还可以用于: 根据图标管理消息更新应用程序到应用程序类别的映射表。 和 [0040] 显示模块还可以用于: 根据管理模块更新的应用程序到应用程序类别的映射表,按类别显示应用程序的图标。 [0041] 本发明的移动终端中的应用图标管理方法,在各自的规则图上对已安装应用的图标进行分屏或分类的快速管理,与现有的应用图标管理方法相比, 通过移动终端,简化了图标管理,实现了应用程序图标的批量管理和多模式管理,大大方便了用户对应用程序图标的管理。 并且,通过本发明,可以在新应用的安装阶段设置新应用所属的类,直接按类管理新应用的图标显示,省去安装后的图标显示管理。 安装了新的应用程序。 附图的简要说明 [0042] 图1是根据本发明实施例的移动终端中应用程序图标管理方法的流程图; [0043] 图2是根据本发明实施例的移动终端中应用图标管理方法中通过移动类应用来管理分屏图标显示的流程图。 [0044] 图3是根据本发明实施例的移动终端中的应用程序图标管理方法中通过移动应用程序的图标来管理分屏显示或分类显示图标的流程图。 [0045] 图4是根据本发明实施例的移动终端应用图标管理方法中待移动图标对象为一类应用时当前屏幕显示的单层环状图的结构示意图。 披露; [0046] 图5为本发明移动终端应用图标管理方法中待移动图标对象为应用图标时当前屏幕显示的双层环状图的结构示意图 披露; [0047] 图6是根据本发明实施例的一种移动终端应用图标管理方法在安装新应用时设置新应用所属类别并直接管理新应用图标显示的流程图。 披露; [0048] 图7是根据本发明实施例的移动终端的模块化结构示意图; 和 [0049] 图8是根据本发明实施例的移动终端的模块化结构示意图。 [0050] 本发明的实施方式、特点和优点将参照附图并结合实施例作进一步说明。 详细说明 [0051]根据本发明实施例,预先设置应用所属类别的信息,建立应用类别、屏幕和应用之间的映射关系表。 接收图标对象移动指令,根据图标对象移动指令获取待移动图标对象对应的规则图信息,并显示规则图信息; 当待移动图标对象成功移动到规则图上的某个区域后,根据移动更新应用类、屏幕、应用之间的映射关系表。 [0052] 下面参照附图并结合具体实施例对本发明的技术方案作进一步详细说明。 应当理解,此处所描述的具体实施例仅仅用于解释本发明,并不用于限制本发明。 [0053] 图1是根据本发明实施例的移动终端中应用程序图标管理方法的流程图。 如图1所示,该方法包括以下步骤。 [0054] 在步骤S 101 ,预先设置应用所属类别的信息,建立应用类别、屏幕、应用之间的映射关系表。 [0055] 在一个实施例中,除了移动终端中默认的应用类之外,还可以通过应用类定制接口来增加新的类应用,以及修改或删除现有的类应用。 然后,在存储应用程序的图标时,根据从属关系,预先分别建立应用程序到屏幕的映射表、应用程序到应用程序类的映射表和应用程序到屏幕的映射表。 屏幕并在屏幕中存储一类应用程序。 [0056] 类别应用到屏幕的映射表(Class_Screen)表示类别应用与移动终端屏幕的映射关系(以下即Class_Screen表)。 [0057] 一个应用到一类应用的映射表(App_Class)表示一个应用和一类应用之间的映射关系(即下文的App_Class表)。 [0058] 应用到屏幕的映射表(App_Screen)表示应用与移动终端屏幕的映射关系(以下简称App_Screen表),其中图标存储在屏幕中的应用不做分类。 主要字段 Class_Screen表如表1所示,App_Class表主要字段如表2所示,App_Screen表主要字段如表3所示。 [0059] 表格1 场地 描述 一类 带有序列的屏幕中包含的类 数字 一个序列 手机屏幕的序号 的数量 终端 屏幕 [0060] 表 2 场地 描述 一个 属于应用程序类别的应用程序 应用 一类 屏幕中包含的一类应用程序 移动端 [0061] 表3 场地 描述 一个应用程序 未分类的申请 一个序列 手机屏幕的序号 屏数 终端 [0062] 在步骤S 102 ,接收图标对象移动指令,根据图标对象移动指令获取待移动图标对象对应的规则图信息,并显示规则图信息。 [0063] 在一个实施例中,当根据图标对象移动指令确定待移动的图标对象为一类应用时,获取标记有屏幕序号的单层环状图信息,并获取单层环状图信息。 当前屏幕显示环状图。 当根据图标对象移动指令确定待移动的图标对象为应用程序图标时,获取标记有屏幕序号和应用程序类别的双层环形图信息,得到双层环形图信息。 在当前屏幕上显示图层环状图。 [0064] 在步骤S 103 待移动图标对象成功移动到规则图上的某个区域后,根据移动更新应用类、屏幕、应用之间的映射关系表。 [0065]在一个实施例中,待移动图标对象被成功移动到规则图上的区域后,一类应用到屏幕的映射表,一应用到一类应用的映射表,或一应用映射表 屏幕可能会更新。 [0066] 本发明的移动终端中的应用图标管理方法,在各自的规则图上对已安装应用的图标进行分屏或分类的快速管理,与现有的应用图标管理方法相比, 通过移动终端,简化了图标管理,实现了应用程序图标的批量管理和多模式管理,大大方便了用户对应用程序图标的管理。 [0067] 图2是根据本发明实施例的移动终端中应用图标管理方法中通过移动类应用来管理分屏图标显示的流程图。 如图2所示,本发明移动类应用管理分屏图标显示的流程包括以下步骤。 [0068] 在步骤S 201 , 图标对象被移动。 [0069] 在一个实施例中,在移动终端中预先设置应用所属类别的信息,并建立类别应用、屏幕和应用之间的映射关系表后,类别应用的图标对象 或者应用程序的图标被拖到目标屏幕或目标应用程序类别中。 [0070] 在步骤S 202 ,根据图标对象移动指令判断图标对象是一类应用还是应用的图标。 [0071] 在一个实施例中,在移动图标对象时,首先需要根据图标对象移动指令确定图标对象的类型(应用程序的类别或应用程序的图标),当图标对象 是一类应用程序,流程转到步骤S 203 . [0072] 在步骤S 203 , 获取单层环状图的信息, 标注有屏幕序号; 计算每个屏幕中剩余的空间,并将其与应用程序类别占用的空间进行比较。 [0073] 在一个实施例中,当确定图标对象为一类应用时,获取标记有屏幕序号的单层环状图信息,计算每个屏幕剩余空间并与待占用空间进行比较 按应用类别。 这里,单层环状图的信息可以包括图的总大小、移动终端的屏幕总数、包含屏幕序号的区域大小、区域颜色标识 、每类应用程序占用的存储空间的颜色标识、属于每类应用程序在屏幕中的图标等。 [0074] 在步骤S 204 ,当前屏幕显示单层环状图,标有屏幕序号。 [0075] 在一个实施例中,这里显示的单层环状图,如图4所示,包括4个带序号的画面 1 , 2 , 3 , 4 , 分别; 包含屏幕序号的区域可以通过颜色相互区分。 当移动终端计算出屏幕剩余空间足够存储属于该应用类别的所有应用的图标时,屏幕序号以亮黄色显示。 当移动终端计算出屏幕没有足够的空闲空间来存储属于应用程序类别的应用程序的图标时,屏幕的序号显示为黑色。 这里,屏幕的序号 1 , 3 , 4 以亮黄色显示,表示每屏 1 , 屏幕 3 , 和屏幕 4 有足够的可用空间来存储属于该应用程序类别的所有应用程序的图标。 屏幕序号 2 显示为黑色,表示该画面2 没有足够的可用空间来存储属于该应用程序类别的所有应用程序的图标。 [0076] 在步骤S 205 ,该类应用被移动到单层环状图中包含目标屏幕序号的区域,然后被释放。 [0077] 在步骤S 206 ,判断目标屏幕是否有足够的剩余空间用于存储应用程序的类别; 如果存在,则流程转到步骤S 207 ; 否则如果空间不足,则流程转到步骤S 211 . [0078] 在一个实施例中,检测目标屏幕的序号是否以亮黄色字体显示。 如果目标屏幕的序列号以亮黄色字体显示,则表示目标屏幕中有足够的剩余空间来存储应用程序的类别。 否则,如果目标屏幕的序号没有以亮黄色字体显示,则表示目标屏幕剩余空间不足以存储应用类别,可以提示用户目标屏幕剩余空间不足。 不足以存储应用程序的类别。 [0079] 如图4所示,屏幕序号 1 , 3 , 4 以亮黄色字体显示,屏幕序号 2 以黑色字体显示。 屏幕中的一类应用 1 可以移动到包含序列号的区域 4 或包含序列号的区域 3 , 但不能移动到包含序号的区域 2 . [0080] 在步骤S 207 , 单层环形图中包含目标屏幕序号的区域高亮显示。 [0081] 在一个实施例中,例如,如图4所示,如果一类应用程序在屏幕中带有序号 1 被移动到包含序列号的区域 4 ,然后是包含序列号的区域 4 会高亮显示,表示该类应用迁移成功。 [0082] 在步骤S 208 ,记录包含目标屏幕序号的区域信息,发送应用类移动对应的图标管理消息,更新表Class_Screen。 [0083] 在一个实施例中,应用类别移动成功后,记录目标屏幕序号所在区域的信息,并向移动终端的管理模块发送图标管理消息。 图标管理消息包括图标管理类型MsgType 2,表示当前移动操作涉及一类应用程序的移动。 管理模块收到图标管理消息后,更新Class_Screen表,即更新一类应用程序与屏幕的映射关系。 [0084] 在步骤S 209 ,刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局。 [0085] 在一个实施例中,根据步骤S更新的表Class_Screen,刷新当前屏幕和目标屏幕上任意类应用程序的显示布局,以及属于任意类应用程序的图标。 208 . [0086] 在步骤S 210 , 取消单层环形图的显示。 [0087] 在一个实施例中,当在预设时间内没有类应用移动时,取消单层环形图的显示。 [0088] 在步骤S 211 ,通知用户目标屏幕中剩余的空间不足以存储应用程序的类别。 [0089] 如果在步骤S中确定 206 当目标屏幕剩余空间不足以存储应用类别时,在当前屏幕提示目标屏幕剩余空间不足以存储应用类别。 [0090]图3是根据本发明实施例的移动终端中应用程序图标管理方法中通过移动应用程序图标来管理分屏显示或分类显示图标的流程图。 如图3所示,本发明通过移动应用程序的图标来管理分屏或分屏图标显示的流程包括以下步骤。 [0091] 在步骤S 301 , 图标对象被移动。 [0092] 在一个实施例中,在移动终端中预先设置应用所属类别的信息,并建立类别应用、屏幕和应用之间的映射关系表后,类别应用的图标对象 或者应用程序的图标被拖到目标屏幕或目标应用程序类别中。 [0093] 在步骤S 302 ,根据图标对象移动指令判断图标对象是一类应用还是应用的图标。 [0094] 在一个实施例中,在移动图标对象时,首先需要根据图标对象移动指令确定图标对象的类型(应用程序的类别或应用程序的图标),当图标对象 为应用程序图标,转步骤S 303 . [0095] 在步骤S 303 ,获取标记有屏幕序号和应用类别的双层环形图信息,计算每个屏幕的剩余空间,并与应用图标占用的空间进行比较。 [0096] 在一个实施例中,当确定图标对象为应用程序的图标时,获取标记有屏幕序号和应用程序类别的双层环形图的信息,计算并比较各屏幕的剩余空间。 应用程序图标占用的空间。 [0097] 这里,双层环形图的信息可以包括: 图的总大小; 移动终端的屏幕总数; 每个屏幕中已有的任何类别的应用程序,以及每个屏幕中已有的多个类别的应用程序; 包含一类应用程序的区域的大小; 包含屏幕序列号的区域的大小; 区域颜色的标识、屏幕中任意类应用程序和属于该类应用程序的图标所占用的存储空间的颜色标识等。 [0098] 在步骤S 304 ,当前屏幕显示双层环状图,标有屏幕序号和应用类别。 [0099] 在一个实施例中,这里显示的双层环形图,如图5所示,包括日常、办公、游戏和系统四类应用。 同屏显示的应用类别在双层环状图中占据连续区域,连续区域颜色相同。 在一个实施例中,日常和办公两个类位于屏幕中 1 , 游戏位于屏幕 2 , 系统位于屏幕 3 , 目前屏幕上没有存储属于一类应用程序的图标 4 . 当移动终端计算出屏幕中有足够的剩余空间用于存储应用程序的图标时,屏幕的序号和屏幕中的任何类别的应用程序都以亮黄色显示。 当移动终端计算出屏幕没有足够的可用空间来存储应用程序的图标时,屏幕的序号和屏幕中的任何类别的应用程序都以黑色显示。 在这里,类别“日常”和“办公室”以及序列号“ 1 包含“日常”和“办公室”类的屏幕的“”为亮黄色字体; 类“系统”和序列号“ 3 包含班级系统的屏幕也是亮黄色字体; 但是类“游戏”和序列号“ 2 包含类游戏的画面为黑色字体。 这表明应用程序的图标可能存储在任一屏幕中 1 或屏幕 3, 但可能不会存储在屏幕中 2 , 作为屏幕剩余空间 2 是不够的。 [0100] 在步骤S 305 ,将应用程序的图标移动到双层环形图中包含目标屏幕序号的区域或包含目标类应用程序的区域,然后释放。 [0101] 在步骤S 306 ,判断该区域是否包含目标屏幕序号或包含目标类应用; 如果该区域包含目标类别的应用程序,则流程转到步骤 S 307 ; 否则,如果该区域包含目标屏幕的序号,则流程转到步骤S 313 . [0102] 在一个实施例中,将应用程序的图标移动到双层环形图中包含屏幕序号或某类应用程序的区域释放后,检测该区域是否被占用 一类应用程序或屏幕的序列号。 如果该区域被一类应用占用,则流程转到步骤S 307 . 如果该区域被屏幕序号占用,则流程进入步骤S 313 . [0103] 如图5所示,属于“系统”类的应用程序在屏幕中的图标 3 可以移动到包含序列号“ 1 “ 要么 ” 4 ”,或屏幕中包含“日常”或“办公室”类的区域 1 (即到亮黄色字体的区域); 但不能移动到包含序列号“ 2 ”或包含类“游戏”的区域(即不能移动到黑色字体的区域)。 [0104] 在步骤S 307 ,判断包含目标类应用程序的屏幕中是否剩余足够的空间用于存储应用程序的图标; 如果目标屏幕剩余空间足以存储应用程序的图标,则流程进入步骤S 308 ; 否则如果目标屏幕剩余空间不足以存储应用程序的图标,则流程进入步骤S 312 . [0105] 在一个实施例中,检测目标类应用程序是否显示为亮黄色字体,如果目标类应用程序显示为亮黄色字体,则表示该应用程序的图标有足够的剩余空间存储。 . 否则,如果目标类别的应用程序没有以亮黄色字体显示,则表示剩余空间不足以存储该应用程序的图标。 [0106] 在步骤S 308 ,双层环形图中包含目标类应用程序的区域被突出显示。 [0107] 在步骤S 309 ,记录目标类应用所在区域的信息,发送应用图标移动对应的图标管理消息,更新应用图标移动对应的映射关系表 . [0108]在一个实施例中,应用程序的图标移动成功后,记录目标类应用程序所在区域的信息,并将应用程序图标移动对应的图标管理消息发送给管理模块。 移动终端。 图标管理消息包括图标管理类型MsgType 3,表示当前移动操作涉及将应用程序的图标移动到目标类应用程序中。 移动终端的管理模块接收到图标管理消息后,查询App_Class表,判断该应用是否存在与应用类别的映射关系,即查询该应用是否已经分类。 如果还没有对应用进行分类,则调用表App_Screen,删除表App_Screen中的应用与屏幕的映射关系; 另外,调用App_Class表,在App_Class表中增加应用程序与应用程序目标类的映射关系。 之前对应用进行分类时,调用表App_Class,更新应用与应用类别的映射关系。 [0109] 在步骤S 310 ,刷新当前屏幕显示的应用程序图标布局和目标屏幕显示的应用程序图标布局。 [0110] 在一个实施例中,根据步骤S更新的表格刷新当前屏幕显示的应用程序图标布局和目标屏幕显示的应用程序图标布局。 309 . [0111] 在步骤S 311 , 取消双层环状图的显示。 [0112] 在一个实施例中,当在预设时间内没有移动应用程序图标时,取消显示双层环形图。 [0113] 在步骤S 312 ,通知用户包含目标类应用程序的屏幕中剩余的空间不足以存储应用程序的图标。 [0114] 在一个实施例中,如果在步骤S中确定 307 包含目标类应用程序的屏幕中剩余空间不足以存储应用程序的图标,则在包含目标类应用程序的屏幕中剩余空间不足以存储应用程序图标的通知被提供在 当前屏幕。 [0115] 在步骤S 313 ,判断目标屏幕是否有足够的剩余空间用于存储应用程序的图标; 如果有足够的空间,则流程转到步骤 S 314 ; 否则如果目标屏幕剩余空间不足以存储应用程序的图标,则流程进入步骤S 316 . [0116] 在一个实施例中,当移动终端检测到释放应用程序图标的区域中包含屏幕序号时,判断目标屏幕中是否剩余足够的空间用于存储应用程序图标。 即检测目标屏幕的序号是否以亮黄色字体显示。 如果目标屏幕的序列号以亮黄色字体显示,则表示目标屏幕中有足够的剩余空间来存储应用程序的图标。 否则,如果目标屏幕的序号没有以亮黄色字体显示,则表示目标屏幕剩余空间不足以存储应用程序的图标。 [0117] 在步骤S 314 , 双层环形图中包含目标屏幕序号的区域被高亮显示。 [0118] 在步骤S 315 ,记录包含目标屏幕序号的区域信息,发送应用程序图标移动对应的图标管理消息,应用程序图标移动对应的映射关系表 已更新。 [0119]在一个实施例中,应用程序的图标移动成功后,记录目标屏幕序号所在区域的信息,并向管理端发送应用程序图标移动对应的图标管理消息。 移动端模块。 图标管理消息包括图标管理类型MsgType 4,表示当前移动操作涉及将应用程序的图标移动到目标屏幕中。 移动终端的管理模块接收到图标管理消息后,查询App_Class表,判断该应用是否存在与应用类别的映射关系,即查询该应用是否已经分类。 如果应用没有分类,则调用表App_Screen,更新应用与屏幕的映射关系; 之前对应用进行分类时,调用表App_Class,删除应用与表App_Class中任意类应用的映射关系,调用表App_Screen增加应用与目标屏幕的映射关系 在表 App_Screen 中。 然后根据更新后的表格刷新屏幕上显示的应用类布局和应用图标布局。 当在预设时间内没有移动应用程序图标时,取消显示双层环形图。 [0120] 在步骤S 316 ,通知用户目标屏幕中剩余的空间不足以存储应用程序的图标。 [0121] 如果在步骤S中确定 313 当目标屏幕剩余空间不足以存储应用程序图标时,在当前屏幕提示目标屏幕剩余空间不足以存储应用程序图标。 [0122] 图6是根据本发明实施例的一种移动终端应用图标管理方法在安装新应用时设置新应用所属类别并直接管理新应用图标显示的流程图。 披露。 如图6所示,在安装新应用时,设置新应用所属类别,直接管理新应用图标显示的流程包括如下步骤。 [0123] 在步骤S 601 ,读取用于安装新应用程序的包文件。 [0124] 在本发明的一个实施例中,移动终端在安装新应用时,会读取用于安装新应用的打包文件,该打包文件可以包括应用的图标、安装应用的包的名称等信息。 安装应用程序所需的硬件环境。 [0125] 在步骤S 602 ,计算每个屏幕中剩余的空间。 [0126] 在步骤S 603 ,判断屏幕中是否有足够的剩余空间用于存储新应用的图标; 如果屏幕中有足够的剩余空间来存储新应用程序的图标,则流程转到步骤S 604 ; 否则,如果没有屏幕有足够的可用空间来存储新应用程序的图标,则流程转到步骤S 610 . [0127] 在步骤S 604 ,具有足够用于存储新应用程序的图标的可用空间的屏幕的序列号,以及包含在具有序列号的屏幕中的一类应用程序,被读取。 [0128] 在一个实施例中,当移动终端检测到屏幕中有足够的剩余空间用于存储新应用的图标时,移动终端将记录并读取具有足够的空闲空间用于存储新应用的图标的屏幕的序号。 应用程序和屏幕中包含的任何类别的应用程序以及序列号。 [0129] 在步骤S 605 ,显示具有足以存储新应用程序图标的可用空间的屏幕的序号,以及包含在具有序号的屏幕中的一类应用程序。 [0130]在一个实施例中,移动终端在当前屏幕上显示具有足以存储新应用程序图标的空闲空间的屏幕序号,以及带有该序号的屏幕包含的应用程序类别,以供用户选择 要安装的新应用程序的类。 [0131] 在步骤S 606 ,根据显示的应用类别选择新应用所属的应用类别,使用打包文件安装新应用。 [0132] 在步骤S 607 ,发送图标管理消息。 [0133] 在一个实施例中,图标管理消息包括安装应用程序的包的文件名、应用程序所属的类、显示应用程序的屏幕的序号和新应用程序的图标管理类型MsgType。 应用所属的类是在安装新应用时选择的类,MsgType为1,表示在安装新应用时,移动终端直接按类管理应用图标的显示。 [0134] 在步骤S 608 ,根据图标管理消息更新表App_Class。 [0135] 在一个实施例中,移动终端的管理模块根据图标管理消息调用App_Class表更新应用程序与应用程序类别的映射关系。 [0136] 在步骤S 609 ,读取App_Class表,刷新显示中属于所选应用类别的应用图标布局。 [0137] 在一个实施例中,移动终端在更新App_Class表后,读取App_Class表,刷新显示中属于所选应用类别的应用的图标布局,实现对新应用图标显示的直接管理。 [0138] 在步骤S 610 ,用户会收到无法安装新应用程序的通知。 [0139] 当检测到没有屏幕有足够的空闲空间来存放新应用的图标时,在当前屏幕提示无法安装新应用。 [0140] 本发明的移动终端中的应用图标管理方法,通过在安装新应用时设置新应用所属的类,可以直接对新应用的图标按类显示进行管理,从而节省了任何费用。 新应用安装后图标显示管理。 [0141] 图7是根据本发明实施例的移动终端的模块化结构示意图。 如图7所示,本实施例的移动终端包括: [0142] 预设模块 701 配置为:预先设置应用所属类别的信息,建立应用类别、屏幕、应用之间的映射关系表。 [0143] 一个管理模块 702 配置为:接收图标对象移动指令; 根据图标对象移动指令获取单层环状图或双层环状图的信息; 在将待移动图标对象成功移动到单层环状图或双层环状图上的区域后,根据 移动; 和 [0144] 显示模块 703 配置为:向管理模块发送图标对象移动指令 702 根据管理模块获取的单层环状图或双层环状图的信息在当前屏幕显示单层环状图或双层环状图 702 . [0145] 预置模块 701可以通过应用类定制界面在移动终端默认类应用的基础上增加新的类应用,修改或删除现有类应用。 然后,在存储应用程序的图标时,根据从属关系,预先分别建立应用程序到屏幕的映射表、应用程序到应用程序类的映射表和应用程序到屏幕的映射表。 屏幕并在屏幕中存储一类应用程序。 [0146] 与现有的移动终端中的应用程序图标管理方法相比,本实施例的移动终端在移动一类应用程序或应用程序的图标时,简化了图标管理,实现了批量管理和多模式管理。 实现了应用程序的图标,极大地方便了用户对应用程序图标的管理。 [0147] 管理模块 702 可以进一步配置为: [0148] 在将待移动类应用移动到单层环形图中包含目标屏幕序号的区域后,判断目标屏幕中是否剩余足够的空间用于存储该类待移动应用。 应用类别成功移动到单层环状图中的区域后,接收显示模块发送的图标管理消息 703 根据图标管理信息更新一类应用程序到屏幕的映射表。 [0149] 显示模块 703 可以进一步配置为: [0150] 类应用成功移动到单层环状图中的区域后,将类应用移动对应的图标管理消息发送给管理模块 702 ,根据管理模块更新的一类应用到屏幕的映射表,刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局。 [0151] 管理模块 702 可以进一步配置为: [0152] 待移动的应用程序图标移动到双层环图中包含目标屏幕或目标类应用程序序号的区域后,判断目标屏幕是否有足够的剩余空间或 包含应用程序目标类的屏幕,用于存储应用程序的待移动图标; 将应用程序的图标成功移动到双层环形图中目标类应用程序所在的区域后,接收显示模块发送的图标管理消息 703 根据图标管理消息更新应用程序到应用程序类别的映射表; 和 [0153] 将应用的图标移动到双层环形图中目标屏幕序号所在区域成功后,接收展示模块发送的图标管理消息 703 根据图标管理信息更新应用程序到屏幕的映射表。 [0154] 显示模块 703 可以进一步配置为: [0155] 将应用程序的图标移动到双层环形图中目标类应用程序所在的区域后,向管理模块发送应用程序图标移动对应的图标管理消息 702 ,根据管理模块更新的一个应用到一类应用的映射表,刷新当前屏幕显示的应用图标布局和目标屏幕显示的应用图标布局 702 ; 和 [0156] 将应用程序的图标成功移动到双层环形图中包含目标屏幕序号的区域后,向管理模块发送应用程序图标移动对应的图标管理消息 702,根据管理模块更新的应用到屏幕的映射表,刷新当前屏幕显示的应用图标布局和目标屏幕显示的应用图标布局 702 . [0157] 管理模块 702 可以进一步配置为: [0158] 通知显示模块 703 如果在预设时间内没有检测到图标对象移动操作,则取消单层环状图或双层环状图的显示。 [0159] 图8是根据本发明实施例的移动终端的模块化结构示意图。 如图8所示,在上一实施例的移动终端的基础上,本实施例的移动终端还包括: [0160] 一个安装模块 804 配置为安装新的应用程序。 [0161] 具体来说,安装模块 804 可以进一步配置为: [0162] 安装新应用时,根据预置模块预置的应用所属类别信息,确定新应用所属类别 801 表Class_Screen、表App_Class和表App_Screen,将应用安装对应的图标管理消息发送给管理模块 802 通知管理模块 802 更新表 App_Class。 [0163] 管理模块 802 可以进一步配置为: [0164] 接收安装模块发送的图标管理消息 804 更新App_Class表,即根据新应用安装时预先设置的类信息(选择新应用所属的类)。 [0165] 显示模块 803 可以进一步配置为: [0166] 新应用安装完成后,根据安装时选择的类,按类显示新应用的图标。 [0167] 与现有的移动终端中的应用程序图标管理方法相比,本实施例的移动终端在移动一类应用程序或应用程序的图标时,简化了图标管理,实现了批量管理和多模式管理。 实现了应用程序的图标,极大地方便了用户对应用程序图标的管理。 并且,本实施例的移动终端,可以在新应用的安装阶段设置新应用所属的类,直接按类管理新应用的图标显示,从而节省 新应用安装后任意图标显示管理。 [0168] 所描述的仅为本发明的实施例而已,并不用于限定本发明的保护范围。 凡使用本发明的说明书及附图所做的等效结构和流程改动,或者将本发明直接或间接应用于其他相关技术领域,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.683 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103309554A(String), CN103309554B(String), EP2824552A1(String), EP2824552A4(String), EP2824552B1(String), US20150026617A1(String), US9952741B2(String), WO2013131321A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.684 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.685 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103309554A(String), CN103309554B(String), EP2824552A1(String), EP2824552A4(String), EP2824552B1(String), US20150026617A1(String), US9952741B2(String), WO2013131321A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.686 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9952741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.693 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.694 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103309554A(String), CN103309554B(String), EP2824552A1(String), EP2824552A4(String), EP2824552B1(String), US20150026617A1(String), US9952741B2(String), WO2013131321A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.695 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), CN103309554A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), CN103309554B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.714 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), EP2824552A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.721 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.721 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), EP2824552A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.729 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), EP2824552B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.738 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), US20150026617A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.746 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.746 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.746 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), US9952741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.754 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270720(Integer), WO2013131321A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9952741B2(String), US9952741B2(String), 1524499200(Integer), 270720(Integer), 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LIANG, XIAOHUI(String), 中兴通讯股份有限公司(String), LIANG XIAOHUI(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1681974673(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.782 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185045(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.783 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75903(Integer), 1(Integer), 185045(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIANG, XIAOHUI(String), LIANG XIAOHUI(String), 0(Integer), 1681975569(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.798 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.799 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185045(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.801 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75961(Integer), 2(Integer), 185045(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.809 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.810 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.811 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75903(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.812 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.814 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.824 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.826 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.827 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.828 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185045(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.836 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.837 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.839 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.840 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal having smart card coupled with RFID tag and method for performing RFID function in such mobile terminal(String), 具有与RFID标签耦合的智能卡的移动终端以及在这种移动终端中执行RFID功能的方法(String), US7374100B2(String), Disclosed is a mobile terminal equipped with a smart card coupled with an RFID tag and a method for performing an RFID function in the mobile terminal. The smart card includes a user information processing section for storing user information and generating a user information signal including user information, an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data, and a main calculating section connected to the user information processing section in order to control a generation and a transmission of the user information signal and connected to the RFID information processing section order to command a generation and a transmission of the RFID signal. When the RFID tag detects an approach of an RFID interrogator, the RFID tag requests a CPU of the smart card to perform the RFID function. Thus, the CPU of the smart card transmits a mode transition signal to a processor of the mobile terminal in order to indicate a mode transition into an RFID mode. Then, the RFID function is carried out.(String), 公开了一种配备有与RFID标签耦合的智能卡的移动终端以及在移动终端中执行RFID功能的方法。 智能卡包括:用户信息处理部分,用于存储用户信息并生成包含用户信息的用户信息信号;RFID信息处理部分,用于存储RFID数据并生成包含RFID数据的RFID信号;以及主计算部分,连接到智能卡。 用户信息处理部分为了控制用户信息信号的生成和传输并且连接到RFID信息处理部分以命令RFID信号的生成和传输。 当RFID标签检测到RFID询问器的接近时,RFID标签请求智能卡的CPU执行RFID功能。 因此,智能卡的CPU向移动终端的处理器发送模式转换信号以指示模式转换到RFID模式。 然后,执行RFID功能。(String), US10/970102(String), 1098288000(Integer), US7374100B2(String), 1211212800(Integer), 1211212800(Integer), 美国(String), 4(Integer), KR(String), 5(Integer), 25(Integer), EP1522955A1 | JP1998098542A | JP2002247157A | KR1020020040455A | US20010004236A1 | US20020002534A1 | US20020165780A1 | US20030006280A1 | US20040016796A1 | US20040059884A1 | US20040121793A1 | US20040203352A1 | US4075632A | US4360810A | US4739328A | US4782345A | US4786907A | US4816839A | US4835377A | US4853705A | US5394439A | US5640002A | US5991749A | US6775632B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.850 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185046(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.852 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.853 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\581bf7786f664305b70f8147e4d7e86f.png(String), 185046(Integer), 581bf7786f664305b70f8147e4d7e86f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.860 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.861 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.862 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal having smart card coupled with RFID tag and method for performing RFID function in such mobile terminal(String), 具有与RFID标签耦合的智能卡的移动终端以及在这种移动终端中执行RFID功能的方法(String), US7374100B2(String), Disclosed is a mobile terminal equipped with a smart card coupled with an RFID tag and a method for performing an RFID function in the mobile terminal. The smart card includes a user information processing section for storing user information and generating a user information signal including user information, an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data, and a main calculating section connected to the user information processing section in order to control a generation and a transmission of the user information signal and connected to the RFID information processing section order to command a generation and a transmission of the RFID signal. When the RFID tag detects an approach of an RFID interrogator, the RFID tag requests a CPU of the smart card to perform the RFID function. Thus, the CPU of the smart card transmits a mode transition signal to a processor of the mobile terminal in order to indicate a mode transition into an RFID mode. Then, the RFID function is carried out.(String), 公开了一种配备有与RFID标签耦合的智能卡的移动终端以及在移动终端中执行RFID功能的方法。 智能卡包括:用户信息处理部分,用于存储用户信息并生成包含用户信息的用户信息信号;RFID信息处理部分,用于存储RFID数据并生成包含RFID数据的RFID信号;以及主计算部分,连接到智能卡。 用户信息处理部分为了控制用户信息信号的生成和传输并且连接到RFID信息处理部分以命令RFID信号的生成和传输。 当RFID标签检测到RFID询问器的接近时,RFID标签请求智能卡的CPU执行RFID功能。 因此,智能卡的CPU向移动终端的处理器发送模式转换信号以指示模式转换到RFID模式。 然后,执行RFID功能。(String), US10/970102(String), 1098288000(Integer), US7374100B2(String), 1211212800(Integer), 1211212800(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 5(Integer), 25(Integer), EP1522955A1 | JP1998098542A | JP2002247157A | KR1020020040455A | US20010004236A1 | US20020002534A1 | US20020165780A1 | US20030006280A1 | US20040016796A1 | US20040059884A1 | US20040121793A1 | US20040203352A1 | US4075632A | US4360810A | US4739328A | US4782345A | US4786907A | US4816839A | US4835377A | US4853705A | US5394439A | US5640002A | US5991749A | US6775632B1(String), \20230420\581bf7786f664305b70f8147e4d7e86f.png(String), 20(Integer), 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.870 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.871 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.872 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 1. A smart card mounted on a single SIM card comprising:a user information processing section for storing user information and generating a user information signal including user information;an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data; anda main calculating section connected to the user information processing section in order to control generation and transmission of the user information signal, and connected to the RFID information processing section in order to command generation and transmission of the RFID signal.(String), 1.智能卡安装在单张SIM卡上包括:用户信息处理部分,用于存储用户信息并生成包括用户信息的用户信息信号;RFID信息处理部分,用于存储RFID数据并生成包括RFID数据的RFID信号;和主计算部分连接到用户信息处理部分以控制用户信息信号的产生和传输,并且连接到RFID信息处理部分以命令RFID信号的产生和传输。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 2. The smart card as claimed in claim 1, wherein the user information processing section includes a user information memory section for storing user information and a user program memory section including a program for generating the user information signal.(String), 2.如权利要求1所述的智能卡,其中用户信息处理部分包括用于存储用户信息的用户信息存储部分和包括用于生成用户信息信号的程序的用户程序存储部分。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.873 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 3. The smart card as claimed in claim 1, wherein the RFID information processing section includes an RFID information memory section for storing RFID information and an RFID function section for generating the RFID signal.(String), 3.如权利要求1所述的智能卡,其中RFID信息处理部分包括用于存储RFID信息的RFID信息存储部分和用于产生RFID信号的RFID功能部分。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 4. The smart card as claimed in claim 3, wherein the RFID function section includes an RFID CODEC section and an RFID modulation section.(String), 4.如权利要求3所述的智能卡,其中RFID功能部分包括RFIDCODEC部分和RFID调制部分。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 5. The smart card as claimed in claim 1, wherein the user information processing section includes a user information memory section for storing user information and a user program memory section for storing a program generating a signal having the user information, and the RFID information processing section includes an RFID information memory section for storing RFID information and an RFID function section for generating the RFID signal.(String), 5.如权利要求1所述的智能卡,其中用户信息处理部分包括用于存储用户信息的用户信息存储部分和用于存储产生具有用户信息的信号的程序的用户程序存储部分,RFID信息处理部分包括用于存储RFID信息的RFID信息存储部分和RFID功能部分,用于产生RFID信号。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 6. The smart card as claimed in claim 5, wherein the user information memory section includes the RFID information memory section.(String), 6.如权利要求5所述的智能卡,其中用户信息存储部分包括RFID信息存储部分。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 7. The smart card as claimed in claim 6, wherein the user program memory section includes the RFID function section.(String), 7.如权利要求6所述的智能卡,其中用户程序存储部分包括RFID功能部分。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 8. The smart card as claimed in claim 1, further comprising a plurality of external pins, including a power pin, a clock pin, and a data input/output pin.(String), 8.如权利要求1所述的智能卡,还包括多个外部引脚,包括电源引脚、时钟引脚和数据输入/输出引脚。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 9. The smart card as claimed in claim 8, wherein one of the plurality of external pins is connected to an RFID antenna.(String), 9.如权利要求8所述的智能卡,其中多个外部引脚之一连接到RFID天线。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 10. The smart card as claimed in claim 9, wherein the main calculating section transmits the RFID signal to the RFID antenna connected to the smart card.(String), 10.如权利要求9所述的智能卡,其中主计算部分将RFID信号发送到连接到智能卡的RFID天线。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 11. The smart card as claimed in claim 1, further comprising an interrupt section which is connected to the main calculating section and which provides to the main calculating section an interrupt signal to indicate an RFID mode.(String), 11.如权利要求1所述的智能卡,还包括中断部分,连接到主计算部分,并向主计算部分提供中断信号以指示RFID模式。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.874 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 12. The smart card as claimed in claim 1, further comprising a clock generator for providing RFID clocks to the RFID information processing section.(String), 12.如权利要求1所述的智能卡,还包括时钟发生器,用于向RFID信息处理部分提供RFID时钟。(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 13. The smart card as claimed in claim 12, wherein the main calculating section generates a control signal for controlling the clock generator.(String), 13.如权利要求12所述的智能卡,其中主计算部分产生用于控制时钟发生器的控制信号。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 14. The smart card as claimed in claim 1, further comprising a clock generator for providing RFID clocks to the main calculating section.(String), 14.如权利要求1所述的智能卡,还包括时钟发生器,用于向主计算部分提供RFID时钟。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 15. A mobile terminal comprising:a smart card mounted on a single SIM card that includes a user information processing section for generating a user information signal including user information and installed in the mobile terminal for storing user information, the smart card including an RFID tag;a main calculating section connected to the user information processing section in order to control generation and transmission of the user information signal, and connected to the RFID information processing section in order to command generation and transmission of the RFID signal; anda processor in communication with the smart card so as to grant or reject an RFID function of the smart card.(String), 15.移动终端包括:智能卡安装在单个SIM卡上,包括用户信息处理部分,用于生成包含用户信息的用户信息信号,安装在移动终端中用于存储用户信息,该智能卡包括RFID标签;主计算部分,与用户信息处理部分相连,控制用户信息信号的产生和传输;与RFID信息处理部分相连,控制RFID信号的产生和传输;和处理器与智能卡通信以授予或拒绝智能卡的RFID功能。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 16. A method for performing an RFID function in a mobile terminal equipped with a smart card mounted on a single SIM card and having an RFID tag, the method comprising:detecting an approach of an RFID interrogator by using the RFID tag;requesting a CPU of the smart card to perform the RFID function by utilizing the RFID tag;transmitting a mode transition signal to a processor of the mobile terminal by using the CPU of the smart card to indicate a mode transition into an RFID mode; andperforming the RFID function by using the smart card after transmitting the mode transition signal.(String), 16.一种用于在配备有安装在单个SIM卡上的智能卡的移动终端中执行RFID功能的方法,以及有一种RFID标签,该方法包括:通过使用RFID标签检测RFID询问器的接近;利用RFID标签请求智能卡的CPU执行RFID功能;通过智能卡的CPU向移动终端的处理器发送模式转换信号,指示模式转换为RFID模式;和在传送模式转换信号后,使用智能卡执行射频识别功能。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 17. The method as claimed in claim 16, wherein the mode transition signal includes a flag representing an execution of the RFID function.(String), 17.如权利要求16所述的方法,其中模式转换信号包括表示RFID功能执行的标志。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 18. The method as claimed in claim 16, further comprising a step of transmitting a response signal from the mobile terminal to the smart card in response to the mode transition signal.(String), 18.如权利要求16所述的方法,还包括响应于模式转换信号,从移动终端向智能卡发送响应信号的步骤。(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 19. The method as claimed in claim 18, wherein the response signal includes information representing a grant of the RFID function.(String), 19.如权利要求18所述的方法,其中响应信号包括表示授予RFID功能的信息。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:09.875 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185046(Integer), 20. The method as claimed in claim 18, wherein the response signal includes information representing a rejection of the RFID function.(String), 20.如权利要求18所述的方法,其中响应信号包括表示拒绝RFID功能的信息。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.041 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.042 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185046(Integer), PRIORITY [0001]This application claims priority to an application entitled “Mobile Terminal Having Smart Card Coupled With RFID Tag and Method For Performing RFID Function in Such Mobile Terminal” filed in the Korean Industrial Property Office on Nov. 27, 2003 and assigned Serial No. 2003-85300, the contents of which are hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal having an RFID (radio frequency identification) tag, the usage and importance of which have increased, and a detachable SIM (subscriber identification module), the usage and importance of which have also increased, and more particularly to a circuit in which an RFID tag is integrally coupled with an SIM, a mobile terminal circuit having the circuit and a method for performing an RFID function in a mobile communication terminal. [0004]2. Description of the Related Art [0005]An RFID transponder or a tag has been developed in an agriculture department of U.S. National Laboratory to identify livestock. The tag having an electric code capable of identifying an animal is inserted into or attached to the animal. In addition, an interrogator capable of interpreting such electrical code is installed in an animal stable, thereby conveniently checking whether the animal has returned to the stable. The interrogator transmits an RF signal to the tag, and the electric code stored in the tag is returned to the interrogator through a modulator of the tag. This is called a backscatter modulation. An RFID tag has an antenna coil through which a modulation signal is transmitted to the interrogator. Such systems are described in U.S. Pat. Nos. 4,075,632 and 4,360,810, the contents of which are incorporated by reference herein. [0006]As RFID techniques make great strides, other techniques for identifying moving objects have been applied to various fields. For example, the techniques have been utilized for vehicles, ocean conveyance containers, or railroad vehicles. Information stored in a tag of such a transportation device is used for a location tracking, a content identification, and so forth. Techniques in relation to such fields are disclosed in U.S. Pat. Nos. 4,739,328, 4,782,345, 4,786,907, 4,816,839, 4,835,377, and 4,853,705, the contents of which are incorporated by reference herein. [0007]Recently, the RFID technique has been tested in many kinds of fields. A communication system used in such fields has come into the spotlight, owing to wide applicability. For instance, since a mobile communication system has many subscribers, in a case where the mobile communication system employing new techniques such as RFID is industrialized, it is possible to easily make profits. Also, since a current mobile communication is stabilized in the aspect of profitability, vendors request to develop applications capable of making supplementary value. [0008]FIG. 1 shows a structure of a passive RFID tag. A tag shown in FIG. 1 is MCRF200 available from Microchip Technology, Inc. [0009]A modulation circuit 209 is a part for connecting antenna coils (not shown) to RFID circuit elements. As an RFID interrogator (not shown) approaches an RFID tag, according to Faraday's law, the antenna coil generates induced electromotive force through an inductive coupling between the RFID interrogator and the RFID tag. Voltage intensity of the antenna coil varies depending on a modulated signal outputted from the modulation circuit 209. [0010]A rectifying section 202 rectifies AC voltage of the induced electromotive force in order to supply DC voltage to other components. A clock generating section 201 generates a system clock by extracting carrier frequency from a signal transferred from the RFID interrogator. The clock generating section 201 supplies other circuit components of the RFID tag with a baud rate, a modulation rate, and a programming rate. A row decoder 204 and a column decoder 207 extract ID data stored in a memory 206 at a clock rate and encode an extracted ID data by means of an NRZ (Non Return to Zero) Direct method, a Differential Biphase method, or a Manchester Biphase method before modulation, thereby generating a serial data stream. [0011]A modulation control section 203 modulates the serial data stream transferred from the decoders 204 and 207 by using a predetermined method, such as an FSK (Frequency Sift keying) method or a PSK (Phase Shift Keying) and the like, and transfers the serial data stream to the modulation circuit 209. A counter 205 counts clocks outputted from the clock generating section 201, so as to provide the clocks to the row decoder 204 and the column decoder 207. [0012]In a case in which a mobile communication system employs an RFID technique, it is expected to provide various supplementary services suitable for cellular systems. In this case, it is absolutely necessary that current RFID equipment are properly combined with current cellular systems. It has already mentioned that an RFID tag (e.g., a card-type RFID tag) is combined with an existing mobile terminal. An example of the RFID tag is disclosed in Korean Patent laid-open publication No. 2002-0090929 entitled “mobile communication terminal apparatus”. [0013]However, since a generally-used RFID tag is only provided for an existing mobile terminal circuit without modifying it or performing an adaptation process, the problem occurs that such an RFID tag is not adaptable for the miniaturization and portability of the existing mobile terminal which are essential features of a mobile terminal. [0014]Meanwhile, a mobile telephone having a GSM (Global System for Mobile telecommunication) mode generally uses a SIM card for identifying subscribers. The SIM card has a small-sized card shape and is used while being set in a slot provided on a rear side of a body of a GSM mode mobile telephone. [0015]FIG. 2 shows a structure of a conventional SIM card for a mobile terminal. [0016]A SIM card used for mobile communication systems, such as GSM systems, is defined in GSM 11.11 Standard, GSM 11.12 Standard, and ISO/IEC 7816. In these standard documents, physical characteristics and electrical signals and transmission protocols of the SIM card and a logical model for the SIM card are explained. The SIM card has 8 external pins. Contact pins C1, C2, C3, C5, and C6 refer to voltage Vcc, a reset RST, a clock CLK, a ground GND, and program voltage Vpp, respectively. A contact pin C7 is an external pin for data input/output I/O and is connected to an antenna for identifying radio frequency. Also, contact pins C4 and C8 RFUs are reserved. [0017]The SIM card internally has a Read Only Memory (ROM) 304 including an operation system operating the SIM card, a Central Processing Unit (CPU) 300 controlling an SIM card operation, a Random Access Memory (RAM) 302 which is a data processing block, and an Electrically Erasable Programmable Read Only Memory (EEPROM) 306 storing identity information of the SIM card. [0018]The SIM card is a kind of a smart card. If an RFID tag having functions of the smart card is separately provided for a mobile communication terminal capable of detaching the SIM card, wasteful factors occur. If the SIM card and the RFID tag are separately provided for the mobile communication, it is difficult to manage the RFID tag for service vendors, who provide various services using the SIM card and pursue added value creation through the various services. Accordingly, it is impossible for the service vendors to acquire the expected advantages resulting from employing the RFID tag, which are namely an increase of profit by means of an RFID service, an increase of the number of subscribers, and an expansion of a service range. [0019]There exists a method in which the SIM card provides additional functions besides a primary function for authenticating mobile terminal users. For instance, a SIM/WIM card which achieves a WIM (Wireless Application Protocol Identify Module) function for providing application services is formulated as WAP Provisioning Smart Card WAP-186-PROVSC-20010710-a Version by the WAP forum. Toolkit applications providing additional services by dynamically using the SIM card are defined in the GSM 11.14 Standard. [0020]The above-mentioned forum or standards only defines file structures and protocols for providing application services, and do not define hardware or software protocols accompanied with combination or connection between the RFID tag and the SIM card. Also, the above-mentioned forum or standards do not solve all existing problems. SUMMARY OF THE INVENTION [0021]Accordingly, the present invention has been made to solve the above-mentioned problems occurring in the prior art, and an object of the present invention is to provide a smart card coupled with an RFID tag. [0022]Another object of the present invention is to provide a mobile terminal capable of mounting a smart card coupled with an RFID tag thereon and a method for performing an identification function in a mobile terminal. [0023]In order to accomplish the above objects, according to a first aspect of the present invention, there is provided a smart card comprising: a user information processing section for storing user information and generating a user information signal including user information; an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data; and a main calculating section connected to the user information processing section, in order to control generation and transmission of the user information signal, and connected to the RFID information processing section in order to command generation and transmission of the RFID signal. [0024]In order to accomplish the above objects, according to a second aspect of the present invention, there is provided a mobile terminal comprising: a smart card installed in the mobile terminal for storing user information, the smart card including an RFID tag; and a processor in communication with the smart card so as to grant or reject an RFID function of the smart card. [0025]In order to accomplish the above objects, according to a third aspect of the present invention, there is provided a method for performing an RFID function in a mobile terminal equipped with a smart card having an RFID tag, the method comprising: detecting an approach of an RFID interrogator by using the RFID tag; requesting a CPU of the smart card to perform the RFID function by utilizing the RFID tag detecting the approach of the RFID interrogator; transmitting a mode transition signal to a processor of the mobile terminal by using the CPU of the smart card to indicate a mode transition into an RFID mode; and performing the RFID function by using the smart card after transmitting the mode transition signal. BRIEF DESCRIPTION OF THE DRAWINGS [0026]The above objects and other features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0027]FIG. 1 is a block diagram of a conventional radio frequency identification (RFID) tag; [0028]FIG. 2 is a block diagram of a conventional SIM card; [0029]FIG. 3 is a block diagram of an SIM card coupled with an RFID tag according to a first embodiment of the present invention; [0030]FIG. 4 is a block diagram of an SIM card coupled with an RFID tag according to a second embodiment of the present invention; [0031]FIG. 5 is a block view showing a logical structure of an SIM card according to one embodiment of the present invention; [0032]FIG. 6 is a view showing an EF structure for storing RFID data according to one embodiment of the present invention; [0033]FIG. 7 is a view showing a mode transition of an SIM card according to one embodiment of the present invention; [0034]FIG. 8 is a view showing a signal exchange between a mobile terminal and a SIM card according to one embodiment of the present invention; [0035]FIG. 9 is a block view showing a structure of an ATR signal shown in FIG. 8; and [0036]FIG. 10 is a schematic view showing a structure of a mobile terminal equipped with a SIM card having an RFID section. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0037]Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. Although certain functions, such as elements of a specific circuit, are specifically defined in the following description of the present invention, it will be obvious to those skilled in the art that such definitions of functions are merely to improve understanding of the present invention and that the present invention can be carried out without such specific elements. Also, in the following description of the present invention, the same reference numerals are used to designate the same or similar components and a detailed description of known functions and configurations incorporated herein are omitted to avoid making the subject matter of the present invention unclear. [0038]A SIM card coupled with an RFID tag is an improvement of a conventional SIM card in view of hardware configuration, logical structure, and operational procedure. 1) Hardware Configuration [0039]FIGS. 3 and 4 are block diagrams of a SIM card coupled with an RFID tag according to exemplary embodiments of the present invention. [0040]FIG. 3 is a view showing the structure of the SIM card coupled with the RFID tag according to a first embodiment of the present invention. In FIG. 3, several already-known components of the SIM card are not illustrated. In addition, RFID data shown as a dotted-block in FIG. 3 represent that an RFID memory section can be provided in an EEPROM 404 or in an ROM 410. [0041]In a conventional RFID tag, ID (identification) data are generally stored in an EEPROM. However, the SIM card also includes the EEPROM. Thus, a margin space of the EEPROM can be utilized as a storage space of RFID data. That is, the EEPROM 404 stores RFID data as well as intrinsic data of the SIM card. [0042]An RFID CODEC section 406 and an RFID modulation section 408 are provided in the ROM 410 of the SIM card. The ROM 410 of the SIM card is a digital logic circuit for realizing an operating system by using a digital CODEC and a modulation section. [0043]A CPU 402 transfers an order to the ROM 410 such that a required function can be carried out. At this time, since RFID data is stored based on a logical structure of a conventional SIM card, RFID data can be processed as another SIM card data. In other words, functional instruction words, such as SELECTION, STATUS, READ BINARY, and UPDATE BINARY, described in “8. Description of the functions” of GSM 11.11 standard document can be used in software capable of operating RFID functions of the SIM card. [0044]Connection pins C4 and C8, usage of which is now reserved, are connected to an RFID antenna coil (not shown) through a coil connecting section 412 connected to an interrupt section 414. Induced electromotive force is generated from the RFID antenna coil when an RFID interrogator (not shown) approaches the RFID antenna coil and induced electromotive force is transferred to the interrupt section 414 through the coil connecting section 412, thereby creating the interrupt. Upon detecting the interrupt, the CPU 402 recognizes that extracting and processing of RFID data are required. Thus, the CPU 402 reads RFID data stored in a memory section (EEPROM 404 or ROM 410) and stores RFID data in a RAM 400. In addition, the CPU 402 controls the RFID CODEC section 406 and the RFID modulation section 408 so as to process RFID data. An RFID signal outputted from the RFID modulation section 408 is transmitted to the RFID interrogator through the coil connecting section 412 with a predetermined frequency determined by the RFID system. [0045]In addition, the CPU 402 not only detects the creation of interrupt from the interrupt section 414, but also recognizes a time for carrying out the RFID functions through various manners, such as a software timer. [0046]When seeing the first embodiment of the present invention in view of usable power, RFID functional blocks, such as the EEPROM 404, RFID CODEC section 406, and RFID modulation section 408 receive supply voltage Vcc, which is stable voltage of a mobile terminal, through a connection terminal C1 of the SIM card. Thus, a problem caused by a conventional power supply of induced electromotive force, which is unstable depending on peripheral environment, can be solved. [0047]When seeing the first embodiment of the present invention in view of a clock CLK, the clock supplied to a connection pin C3 is typically in a standard range of 1 MHz to 5 MHz from a clock supply of the mobile terminal. When the RFID signal is transferred to the coil connecting section 412, the CPU 402 varies the clock CLK according to the RFID system and transmits the RFID signal by synchronizing the RFID signal with the varied clock CLK. [0048]FIG. 4 is a view showing a structure of the SIM card coupled with the RFID tag according to a second embodiment of the present invention. In FIG. 4, several already-known components of the SIM card are not illustrated. [0049]Referring to FIG. 4, an RFID CODEC section 508 and an RFID modulation section 510 are provided in the SIM card in such a manner that the RFID CODEC section 508 and the RFID modulation section 510 are separate from a memory section. [0050]A clock modulation section 516 modulates a clock CLK transmitted from a mobile terminal through a connection pin C3 of the SIM card, thereby generating an RFID clock signal 518 and a SIM clock signal 520. The RFID clock signal 518 has a frequency required for operating RFID functional blocks, such as the RFID CODEC section 508 and the RFID modulation section 510. The SIM clock signal has a frequency required for operating SIM functional blocks, such as a CPU 500, a RAM 502, a ROM 504, and an EEPROM 506. [0051]Selectively, the RFID clock signal 518 can be used as a reference when the CPU 500 finally generates the RFID signal, without using the RFID clock signal 518 for the operation of the above RFID functional blocks. In this case, the above RFID functional blocks may use the clock signal identical to the clock signal of the SIM functional blocks. That is, the above RFID functional blocks may use the SIM clock signal 520. The clock is generated by means of the clock modulation section 516 and is controlled by means of a control signal 522 applied from the CPU 500. [0052]The CPU 500 reads RFID data stored in the memory section, such as the EEPROM 506 or the ROM 504, and stores RFID data in the RAM 502. In addition, the CPU 500 transfers RFID data to the RFID CODEC section 508 so as to convert RFID data into the RFID signal through the RFID modulation section 510. The RFID signal is transferred to a coil connecting section 514 and is propagated to an exterior through an antenna coil (not shown) connected to the coil connecting section 514. 2) Logical Structure [0053]A logical structure of the SIM card used in a GSM mobile terminal is prescribed in a GSM 11.11 standard document. In order to provide the RFID functions according to the present invention, it is required to vary the logical structure of the SIM card. However, the variation may be carried out within a predetermined range capable of maintaining flexibility. [0054]FIG. 5 is a block view showing the logical structure of the SIM card according to one embodiment of the present invention. [0055]The logical structure of the SIM card includes a master file (MF), a dedicated file (DF), and an elementary file (EF). The MF is selected when the SIM card is initially operated and is designated as a present directory. The DF is used for providing multi-functions required for various business services, such a telecom service, a Global System for Mobile communications (GSM), a Digital Cellular System 1800 (DCS1800) or an Interim Standard 41 (IS41). The DF has the EF, which stores data utilized for each service. [0056]In order to realize the present invention, a new DF and a new EF corresponding to the new DF are added to the conventional SIM logical system. As shown in FIG. 5, the new DF includes a DFRFID for the RFID function. An EF6 stores RFID data for the purpose of the service. [0057]In the SIM logical system, a file ID “7F2X” is allotted to the DF for new services. Thus, by storing RFID data in the EF corresponding to the DF having the file ID of 7F2X, it is possible to store data for the RFID service in the conventional SIM logical structure without using conventional instruction words. Such files for the RFID service are stored in the EEPROM 406 shown in FIG. 3 and the EEPROM 506 shown in FIG. 4. [0058]FIG. 6 is a view showing an EF structure for storing RFID data according to an exemplary embodiment of the present invention. [0059]Since the EF is based on GSM standardization, the EF is realized as an extensible file of the SIM logical structure so that conventional software can be continuously used. [0060]A variable range of an “identifier” may depend on the file ID of the DF. For instance, if the DFRFID has a file ID of 7F2X, the identifier has 6F2X, 6F3X or 6F4X. A “structure” is a file structure of the EF. Transparent type, linear fixed type, and cyclic type EFs are standardized. The transparent type EF is adaptable for a sequence of bytes, such as RF data. [0061]A “file size” is a size of RFID data to be stored (for example, 4 bytes). Software instruction words for controlling RFID data stored in the EF include READ, UPDATE, INVALIDATE, and REHABILITATE, which are based on the standardization of the GSM. In addition, executive conditions for the instruction words include CHV1 (card holder verification 1) and ADM (administration). The CHV1 represents a software task allowing a card holder to access thereto, and the ADM represents a software task allowing an administrator of the SIM card to access thereto. 3) Operation Procedure [0062]By providing the RFID function to the conventional SIM card, a mode of the SIM card and an interface between a mobile terminal and the SIM card are varied. [0063]FIG. 7 is a view showing a mode transition of the SIM card according to one embodiment of the present invention. [0064]A mode of the SIM card can be shifted into a specific mode or a negotiable mode after transmitting an ATR (answer-to-reset) signal in response to a reset request from the mobile terminal. The specific mode is divided into a telecom mode (for example, GSM mode) and an RFID mode. Application software of the mobile terminal requests the negotiable mode through a signal exchange between the mobile terminal and the SIM card. A mode transition of a smart card into the RFID mode according to a request of the mobile terminal is one example of the negotiable mode. [0065]The mode transition is displayed by a specific mode byte TA(2) of the ATR signal, which is prescribed in ISO/IEC 7816-3. The ATR signal is the sequence of bytes transferred to the mobile terminal from the SIM card as an answer for a reset request of the mobile terminal. The ATR signal is an asynchronous transmission. [0066]FIG. 8 is a view showing the signal exchange between the mobile terminal and the SIM card according to one embodiment of the present invention. [0067]When the CPU of the SIM card having the RFID function recognizes an approach of the RFID interrogator, via the interrupt section, the CPU of the SIM card indicates the approach of the RFID interrogator to the CPU of the mobile terminal by using the ATR signal. Upon receiving the ATR signal indicating an operation of the RFID function from the SIM card, the mobile terminal grants the RFID function depending on an application program or an operational state of the mobile terminal, so that the SIM card can perform the RFID function. In addition, if it is required that mobile terminal request a primary function of the SIM card, that is, when it is required to primarily request a user's identification for a communication system or when the mobile terminal cannot perform the RFID function, the mobile terminal may reject the RFID function. In addition, without considering the priority, the mobile terminal can be designed such that the mobile terminal is converted into an RFID mode when the CPU of the mobile terminal recognizes the approach of the RFID interrogator. [0068]FIG. 9 is a block view showing a structure of the ATR signal shown in FIG. 8. [0069]The ATR signal, which is prescribed in ISO/IEC 7816-3, is a combination of bytes transmitted in series. Usage of each byte is prescribed in ISO/IEC 7816-3. In addition, usage of some bytes is reserved. Thus, the SIM card can indicate the start of the RFID function to the mobile terminal by using the ATR signal. For instance, the ATR signal including beats (for example, beats having a lower four-beat value of “1111”) capable of indicating the RFID mode can be made in the specific mode byte TA(2). The specific mode byte TA(2) may be used to indicate that a mode has been already shifted into the RFID mode from the specific mode after a cold reset (that is, when the SIM card having the RFID mode receives a request, which does not relate to the RFID, from the mobile terminal. For example, when the mobile terminal requests the user's ID). In addition, the specific mode byte TA(2) may be used to indicate the start of the RFID mode as the RFID interrogator approaches the SIM card (that is, notifying of a transition into the RFID mode from a communication mode). [0070]According to another embodiment of the present invention, a bit indicating the RFID mode can be added to the lower four-bits of a TD(i), which is an interface byte. According to the standardization of ISO/IEC 7816-3, lower four-bits of the TD(i) and TA(2) are defined as a parameter T, wherein usage of some parameters (T=5 to 13) is reserved to use them in the future. Therefore, usage of some T values for the purpose of the RFID does not violate the standardization of ISO/IEC 7816-3, so that the SIM card can be flexibly used in a conventional system. [0071]FIG. 10 is a schematic view showing a structure of a mobile terminal equipped with an SIM card having an RFID section. [0072]Reference numeral 900 represents a processor of the mobile terminal ME. An example of the processor is a mobile station modem (MSM) chip called “mobile processor” available from the Qualcomm company. [0073]Reference numeral 950 represents the SIM card. The SIM card having the RFID section is installed in the mobile terminal in order to signal a mode transition into an RFID mode. To this end, a CPU 912, a SIM section 914 and an RFID section 916 of the SIM card 950 are only illustrated in FIG. 10. Already-known components of the SIM card 950 are not illustrated in FIG. 10. [0074]The SIM section 914 is a user information processing section for storing user information and generating a user information signal including user information. In addition, the user information processing section includes a user information memory section for storing user information and a user program memory section having a program generating a user information signal. The user information memory section includes the EEPROM 404 and the user program memory section includes the ROM 410, as shown in FIG. 3. In addition, the user information memory section includes the EEPROM 506 and the user program memory section includes the ROM 504 as shown in FIG. 4. [0075]The RFID section 916 is an RFID information processing section capable of storing and processing RFID data and generating an RFID signal including RFID data. In addition, the RFID information processing section includes an RFID information memory section for storing RFID information and an RFID function section for generating the RFID signal. The RFID information memory section can be provided in the EEPROM 404 or ROM 410, and the RFID function section includes the RFID CODEC section 406 and the RFID modulation section 410 as shown in FIG. 3. In addition, the RFID information memory section can be provided in the EEPROM 506 or ROM 504, and the RFID function section includes the RFID CODEC section 508 and the RFID modulation section 510, as shown in FIG. 4. [0076]The CPU 912 is a main calculating section connected to the user information processing section to command the generation of the user information signal so as to transmit the user information signal, and connected to the RFID information processing section to command generation of the RFID signal in order to transmit the RFID signal. The CPU 912 corresponds to the CPU 402 shown in FIG. 3 and the CPU 500 shown in FIG. 4. [0077]When an RFID interrogator (not shown) approaches the mobile terminal MT within a predetermined distance, the RFID section 916 of the SIM card 950 installed in the mobile terminal MT detects the approach of the RFID interrogator. Upon detecting the RFID interrogator, the RFID section 916 transfers detecting data to the CPU 912 of the SIM card 950 so that the SIM card 950 recognizes that the RFID function must be carried out. Accordingly, the CPU 912 of the SIM card 950 transmits a signal to the processor 900 of the mobile terminal so as to convert a mode of the mobile terminal into the RFID mode. In addition, a mode of the SIM card 950 is converted into an RFID function mode for performing the RFID function. [0078]According to the present invention, the mobile terminal can provide stable clocks and a stable power supply to the RFID functional blocks, rather than receiving power from the RFID interrogator or providing clocks to the functional blocks that use the coil connecting section and that extract the clocks from a carrier wave signal transmitted from the RFID interrogator, thereby stabilizing the system. Conventional systems may become unstable depending on RF feeding environment if carrier wave signals and induced electromotive force are deteriorated. [0079]As described above, the present invention performing the RFID function by utilizing the SIM card has advantages that include: [0080]First, the SIM card can be detachably installed in the mobile terminal so as to perform the RFID functions, but the portability and miniaturization of the mobile terminal, which are important matters, are not thereby improved. If the RFID tag is separately fabricated from the SIM card, the mobile terminal may not satisfy the portability and miniaturization requirements. [0081]Second, in a functional aspect, the present invention may upgrade the conventional SIM card, so it is possible to create a new demand for the SIM card. [0082]Third, since an RFID technique is provided through the SIM card, an advanced RFID technique can be applied to the conventional mobile communication system. If the RFID tag is fabricated separate from the SIM card, the RFID tag may be fixed in the mobile terminal, so it is difficult to apply the advanced RFID technique to the mobile terminal. [0083]Fourth, an earning rate of a service provider providing a service to subscribers by managing the SIM card may increase. This is because the RFID technique, which is a basis for new services, is adopted in the SIM card, making it possible to provide additional techniques based on a conventional payment charge system and a conventional user management system. If the RFID tag is fabricated separately from the SIM card, it is difficult to provide new services that utilize the RFID tag, resulting in a decreased earning rate of the service provider. [0084]While the present invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请要求于 2003 年 11 月 27 日在韩国工业产权局提交并转让序列号为 2003-85300 的题为“具有与 RFID 标签耦合的智能卡的移动终端和在这种移动终端中执行 RFID 功能的方法”的申请的优先权 ,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及具有RFID(射频识别)标签的移动终端,其使用和重要性增加,以及可拆卸的SIM(订户识别模块),其使用和重要性也增加,更具体地讲 本发明涉及一种RFID标签与SIM整体耦合的电路、具有该电路的移动终端电路以及用于在移动通信终端中执行RFID功能的方法。 [0004] 2.相关技术的描述 [0005] 美国国家实验室的一个农业部门已经开发了一种 RFID 应答器或标签来识别牲畜。 具有能够识别动物的电码的标签被插入或附在动物身上。 此外,在畜栏内安装了能够解读这种电码的询问器,从而方便地检查动物是否已经返回畜栏。 读写器向标签发射射频信号,存储在标签中的电码通过标签的调制器返回读写器。 这称为反向散射调制。 RFID标签具有天线线圈,调制信号通过该天线线圈传输到询问器。 此类系统在美国专利 5,500,000 中进行了描述。 美国专利 4,075,632 和 4,360,810,其内容通过引用并入本文。 [0006] 随着 RFID 技术取得长足进步,用于识别移动物体的其他技术已应用于各个领域。 例如,这些技术已用于车辆、海运集装箱或铁路车辆。 存储在这种运输设备的标签中的信息用于位置跟踪、内容识别等。 与这些领域相关的技术在美国专利 5,500,000 中公开。 美国专利 4,739,328、4,782,345、4,786,907、4,816,839、4,835,377 和 4,853,705,其内容通过引用并入本文。 [0007] 近来,RFID技术已经在多种领域进行了测试。 由于广泛的适用性,用于此类领域的通信系统已成为人们关注的焦点。 例如,由于移动通信系统的订户多,因此在采用RFID等新技术的移动通信系统工业化的情况下,可以容易地获利。 此外,由于当前的移动通信在盈利能力方面稳定,厂商要求开发能够产生附加价值的应用程序。 [0008] 如图。 图1示出了无源RFID标签的结构。 图 1 所示的标签。 1 是可从 Microchip Technology, Inc. 获得的 MCRF200。 [0009] 调制电路 209 是用于将天线线圈(未显示)连接到RFID电路元件的部件。 当RFID询问器(未示出)接近RFID标签时,根据法拉第定律,天线线圈通过RFID询问器和RFID标签之间的感应耦合产生感应电动势。 天线线圈的电压强度根据调制电路输出的调制信号而变化 209 . [0010] 整流段 202 对感应电动势的交流电压进行整流,以便为其他部件提供直流电压。 时钟产生部分 201 通过从RFID询问器传输的信号中提取载波频率来生成系统时钟。 时钟生成部分 201 为RFID标签的其他电路组件提供波特率、调制率和编程率。 行解码器 204 和一个列解码器 207 提取存储在内存中的 ID 数据 206以时钟速率,在调制前通过NRZ(不归零)直接法、差分双相法或曼彻斯特双相法对提取的ID数据进行编码,从而产生串行数据流。 [0011] 调制控制部分 203 调制从解码器传输的串行数据流 204 和 207 通过预定的方法,例如FSK(Frequency Sift Keying)方法或PSK(Phase Shift Keying)等,将串行数据流传输到调制电路 209 . 一个柜台 205 对时钟生成部分输出的时钟进行计数 201 ,以便为行解码器提供时钟 204 和列解码器 207 . [0012] 在移动通信系统采用RFID技术的情况下,期望提供适合蜂窝系统的各种补充服务。 在这种情况下,当前的 RFID 设备与当前的蜂窝系统正确结合是绝对必要的。 已经提到RFID标签(例如,卡片式RFID标签)与现有的移动终端相结合。 在题为“移动通信终端设备”的韩国专利公开第2002-0090929号中公开了RFID标签的示例。 [0013] 然而,由于普遍使用的RFID标签只提供给现有的移动终端电路,而没有对其进行修改或适配处理,因此存在这样的RFID标签不适应现有移动终端的小型化和便携性的问题。 移动终端的基本功能。 [0014] 同时,具有GSM(全球移动电信系统)模式的移动电话通常使用SIM卡来识别用户。 SIM卡具有小尺寸的卡片形状,并且被设置在设置在GSM模式移动电话的机身后侧的插槽中使用。 [0015] 如图。 图2示出了传统的用于移动终端的SIM卡的结构。 [0016] GSM 11.11 标准、GSM 11.12 标准和 ISO/IEC 7816 中定义了用于移动通信系统,例如 GSM 系统的 SIM 卡。在这些标准文件中,SIM 卡的物理特性和电信号和传输协议以及 SIM 卡的逻辑模型进行了说明。 SIM 卡有 8 个外部引脚。 触针 C 1 , C 2 , C 3 , C 5 , 和 C 6 分别指电压Vcc、复位RST、时钟CLK、地GND和编程电压Vpp。 A 触针 C 7 是用于数据输入/输出 I/O 的外部引脚,并连接到用于识别射频的天线。 此外,触针 C 4 和 C 8 RFU 被保留。 [0017] SIM 卡内部有一个只读存储器 (ROM) 304 包括操作 SIM 卡的操作系统、中央处理器 (CPU) 300 控制 SIM 卡操作,随机存取存储器 (RAM) 302 这是一个数据处理块和一个电可擦可编程只读存储器(EEPROM) 306 存储SIM卡的身份信息。 [0018] SIM卡是一种智能卡。 如果为能够分离SIM卡的移动通信终端单独设置具有智能卡功能的RFID标签,则会出现浪费的因素。 如果为移动通信分别提供SIM卡和RFID标签,则难以为使用SIM卡提供各种服务并通过各种服务寻求增值创造的服务供应商管理RFID标签。 因此,服务供应商无法获得使用RFID标签所带来的预期优势,即通过RFID服务增加利润、增加用户数量和扩大服务范围。 . [0019]存在一种方法,其中SIM卡提供除了用于认证移动终端用户的主要功能之外的附加功能。 例如,实现WIM(Wireless Application Protocol Identification Module)功能提供应用服务的SIM/WIM卡被WAP论坛制定为WAP Provisioning Smart Card WAP-186-PROVSC-20010710-a版本。 GSM 11.14 标准中定义了通过动态使用 SIM 卡提供附加服务的工具包应用程序。 [0020] 上述论坛或标准仅定义了提供应用服务的文件结构和协议,并未定义RFID标签与SIM卡结合或连接的硬件或软件协议。 此外,上述论坛或标准并不能解决所有现有问题。 发明内容 [0021] 因此,本发明旨在解决现有技术中出现的上述问题,本发明的目的在于提供一种与RFID标签相结合的智能卡。 [0022] 本发明的另一个目的是提供一种能够安装其上耦合有RFID标签的智能卡的移动终端以及用于在移动终端中执行识别功能的方法。 [0023] 为了实现上述目的,根据本发明的第一方面,提供了一种智能卡,包括: 用户信息处理部分,用于存储用户信息并产生包括用户信息的用户信息信号; RFID信息处理部分,用于存储RFID数据并产生包括RFID数据的RFID信号; 主计算部分连接到用户信息处理部分,以控制用户信息信号的生成和传输,并连接到RFID信息处理部分,以命令生成和传输RFID信号。 [0024] 为了实现上述目的,根据本发明的第二方面,提供了一种移动终端,包括: 智能卡,安装在移动终端中,用于存储用户信息,智能卡包括RFID标签; 处理器与智能卡通信,以授予或拒绝智能卡的RFID功能。 [0025] 为了实现上述目的,根据本发明的第三方面,提供了一种在配备有具有RFID标签的智能卡的移动终端中执行RFID功能的方法,该方法包括: 使用RFID标签的RFID读写器; 利用RFID标签检测RFID读写器的接近,请求智能卡的CPU执行RFID功能; 通过智能卡的CPU向移动终端的处理器发送模式转换信号,指示模式转换到RFID模式; 发送模式转换信号后,利用智能卡执行RFID功能。 附图的简要说明 [0026] 本发明的上述目的和其他特征和优点将通过以下结合附图的详细描述而更加明显,其中: [0027] 如图。 附图说明图1是传统射频识别(RFID)标签的框图; [0028] 如图。 图2是现有SIM卡的框图。 [0029] 如图。 图3是根据本发明第一实施例的结合RFID标签的SIM卡的框图。 [0030] 如图。 图4是根据本发明第二实施例的结合RFID标签的SIM卡的框图。 [0031] 如图。 图5是表示本发明一实施方式的SIM卡的逻辑结构的框图。 [0032] 如图。 图6是表示本发明的一实施方式的RFID数据存储用EF结构的图。 [0033] 如图。 图7是表示本发明的一个实施方式的SIM卡的模式转换的图。 [0034]如图。 图8为本发明一实施例的移动终端与SIM卡的信号交换示意图。 [0035] 如图。 图9是表示图8所示的ATR信号的结构的框图。 8个; 和 [0036] 如图。 图10是示出配备有具有RFID部分的SIM卡的移动终端的结构的示意图。 优选实施例的详细说明 [0037] 在下文中,将参照附图描述本发明的优选实施例。 尽管在本发明的以下描述中具体定义了某些功能,例如特定电路的元件,但是对于本领域技术人员来说,这些功能的定义仅仅是为了提高对本发明的理解,并且 本发明可以在没有这些特定元件的情况下实施。 此外,在本发明的以下描述中,相同的附图标记用于表示相同或相似的部件,并且省略了包含在本文中的已知功能和配置的详细描述以避免使本发明的主题不清楚。 [0038] 结合RFID标签的SIM卡是对传统SIM卡的硬件配置、逻辑结构和操作流程的改进。 1) 硬件配置 [0039] 图 图3和4是根据本发明示例性实施例的与RFID标签耦合的SIM卡的框图。 [0040] 如图。 图3为本发明第一实施例的结合RFID标签的SIM卡的结构示意图。 在图。 在图3中,未示出SIM卡的几个已知组件。 此外,RFID数据在图1中以虚线块表示。 图3表示可以在EEPROM中提供RFID存储部分 404 或在 ROM 中 410 . [0041] 在传统的RFID标签中,ID(识别)数据通常存储在EEPROM中。 但是,SIM 卡也包含 EEPROM。 因此,EEPROM的余量空间可以用作RFID​​数据的存储空间。 也就是说,EEPROM 404 存储 RFID 数据以及 SIM 卡的固有数据。 [0042] 一个 RFID CODEC 部分 406 和一个 RFID 调制部分 408 在 ROM 中提供 410 SIM 卡。 只读存储器 410 SIM卡的一个数字逻辑电路是利用数字CODEC和调制部分实现操作系统的数字逻辑电路。 [0043] 一个中央处理器 402 将订单转移到 ROM 410 以便可以执行所需的功能。 此时,由于RFID数据是基于传统SIM卡的逻辑结构存储的,RFID数据可以作为另一个SIM卡数据处理。 换言之,在“8. GSM 11.11标准文档中的“功能描述”可用于能够操作SIM卡RFID功能的软件。 [0044] 连接针 C 4 和 C 8 ,现在保留使用,通过线圈连接部分连接到RFID天线线圈(未显示) 412 连接到中断部分 414 . 当 RFID 询问器(未显示)接近 RFID 天线线圈并将感应电动势传递到中断部分时,RFID 天线线圈会产生感应电动势 414 通过线圈连接部分 412 ,从而产生中断。 在检测到中断时,CPU 402 认识到需要提取和处理 RFID 数据。 因此,CPU 402 读取存储在内存部分(EEPROM 404 或只读存储器 410 ) 并将 RFID 数据存储在 RAM 中 400 . 此外,CPU 402 控制 RFID CODEC 部分 406 和 RFID 调制部分 408 以处理RFID数据。 从 RFID 调制部分输出的 RFID 信号 408 通过线圈连接部分传输到RFID读写器 412 具有由 RFID 系统确定的预定频率。 [0045] 此外,CPU 402 不仅从中断部分检测到中断的创建 414 ,还可以通过软件定时器等多种方式识别执行RFID功能的时间。 [0046] 当从可用功率的角度来看本发明的第一实施例时,RFID功能块,例如EEPROM 404 , RFID CODEC部分 406 , 和 RFID 调制部分 408 通过连接端C接收移动终端的稳定电压Vcc 1 SIM 卡。 因此,可以解决由感应电动势的传统电源引起的问题,该感应电动势取决于周边环境而不稳定。 [0047] 当从时钟 CLK 来看本发明的第一实施例时,提供给连接引脚 C 的时钟 3 典型地在来自移动终端的时钟供应的1MHz到5MHz的标准范围内。 当 RFID 信号传送到线圈连接部分时 412 , 中央处理器 402 根据RFID系统改变时钟CLK并且通过将RFID信号与改变的时钟CLK同步来传输RFID信号。 [0048] 如图。 图4是表示本发明的第二实施方式的与RFID标签结合的SIM卡的结构的图。 在图。 在图4中,未示出SIM卡的几个已知组件。 [0049] 参考图。 4、一个RFID CODEC部分 508 和一个 RFID 调制部分 510 在 SIM 卡中以这样的方式提供,即 RFID CODEC 部分 508 和 RFID 调制部分 510 与内存部分分开。 [0050] 时钟调制部分 516 通过连接引脚 C 调制从移动终端发送的时钟 CLK 3 SIM卡,从而产生RFID时钟信号 518 和一个 SIM 时钟信号 520 . RFID时钟信号 518 具有操作 RFID 功能块所需的频率,例如 RFID CODEC 部分 508 和 RFID 调制部分 510 . SIM 时钟信号具有操作 SIM 功能块(例如 CPU)所需的频率 500 , 一个内存 502 , 一个只读存储器 504 , 和一个 EEPROM 506 . [0051] 选择性地,RFID时钟信号 518 CPU时可以作为参考 500 最后生成RFID信号,不使用RFID时钟信号 518 用于上述 RFID 功能块的操作。 在这种情况下,上述RFID功能块可以使用与SIM功能块的时钟信号相同的时钟信号。 即上述RFID功能块可以使用SIM时钟信号 520 . 时钟由时钟调制部分产生 516 并由控制信号控制 522 从 CPU 应用 500 . [0052] 中央处理器 500 读取存储在内存部分(如 EEPROM)中的 RFID 数据 506 或ROM 504 , 并将 RFID 数据存储在 RAM 中 502 . 此外,CPU 500 将 RFID 数据传输到 RFID CODEC 部分 508 从而通过RFID调制部分将RFID数据转换成RFID信号 510 . RFID信号被传送到线圈连接部分 514 并且通过连接到线圈连接部分的天线线圈(未示出)传播到外部 514 . 2) 逻辑结构 [0053] GSM 11.11标准文档中规定了用于GSM移动终端的SIM卡的逻辑结构。 为了提供根据本发明的RFID功能,需要改变SIM卡的逻辑结构。 然而,可以在能够保持灵活性的预定范围内进行变化。 [0054] 如图。 图5是表示本发明一实施方式的SIM卡的逻辑结构的框图。 [0055]SIM卡的逻辑结构包括主文件(MF)、专用文件(DF)和基本文件(EF)。 MF在SIM卡初始操作时被选择并被指定为当前目录。 DF用于提供各种商业服务所需的多功能,例如电信服务、全球移动通信系统(GSM)、数字蜂窝系统1800(DCS1800)或临时标准41(IS41)。 DF 有 EF,它存储用于每个服务的数据。 [0056] 为了实现本发明,在传统的SIM逻辑系统中增加了新的DF和对应于新DF的新EF。 如图所示。 5、新的DF包括一个DF RFID 用于 RFID 功能。 英孚 6 为服务目的存储 RFID 数据。 [0057] 在SIM逻辑系统中,文件ID“7F2X”被分配给DF用于新服务。 因此,通过将RFID数据存储在与具有7F2X的文件ID的DF对应的EF中,可以在不使用常规指令字的情况下以常规SIM逻辑结构存储用于RFID服务的数据。 RFID 服务的此类文件存储在 EEPROM 中 406 如图所示。 3和EEPROM 506 如图所示。 4. [0058] 如图。 图6是示出根据本发明示例性实施例的用于存储RFID数据的EF结构的视图。 [0059] 由于EF是基于GSM标准化的,所以EF被实现为SIM逻辑结构的可扩展文件,从而可以继续使用常规软件。 [0060] “标识符”的可变范围可能取决于 DF 的文件 ID。 例如,如果 DF RFID 文件 ID 为 7F2X,标识符有 6F2X、6F3X 或 6F4X。 “结构”是 EF 的文件结构。 透明型、线性固定型和循环型 EF 已标准化。 透明类型 EF 适用于一系列字节,例如 RF 数据。 [0061] “文件大小”是要存储的RFID数据的大小(例如,4字节)。 用于控制存储在 EF 中的 RFID 数据的软件指令字包括 READ、UPDATE、INVALIDATE 和 REHABILITATE,它们基于 GSM 的标准化。 此外,指令词的执行条件包括 CHV 1 (持卡人验证 1 ) 和 ADM(管理)。 CHV 1 代表允许持卡人访问的软件任务,并且ADM代表允许SIM卡的管理员访问的软件任务。 3) 操作程序 [0062] 通过为传统的SIM卡提供RFID功能,改变了SIM卡的模式以及移动终端与SIM卡的接口。 [0063] 如图。 图7是表示本发明的一个实施方式的SIM卡的模式转换的图。 [0064] SIM卡的模式可以在响应于来自移动终端的重置请求而发送ATR(重置应答)信号之后转换为特定模式或可协商模式。 具体模式分为电信模式(如GSM模式)和RFID模式。 移动终端的应用软件通过移动终端与SIM卡之间的信号交换请求协商模式。 根据移动终端的请求将智能卡模式转换为RFID模式是可协商模式的一个示例。 [0065] 模式转换由特定模式字节 TA( 2 ) 的 ATR 信号,这是在 ISO/IEC 7816-3 中规定的。 ATR信号是从SIM卡传送到移动终端的字节序列,作为对移动终端复位请求的应答。 ATR 信号是异步传输。 [0066] 如图。 图8为本发明一实施例的移动终端与SIM卡的信号交换示意图。 [0067]当具有RFID功能的SIM卡的CPU通过中断部分识别到RFID询问器的接近时,SIM卡的CPU通过ATR信号向移动终端的CPU指示RFID询问器的接近。 移动终端在从SIM卡接收到指示RFID功能操作的ATR信号后,根据应用程序或移动终端的操作状态授予RFID功能,从而SIM卡可以执行RFID功能。 另外,如果需要移动终端请求SIM卡的主要功能,即需要主要请求用户对通信系统的身份识别或移动终端不能执行RFID功能时,移动终端 可能拒绝 RFID 功能。 此外,在不考虑优先级的情况下,移动终端可以设计成当移动终端的CPU识别到RFID询问器的接近时,将移动终端转换为RFID模式。 [0068] 如图。 图9是表示图8所示的ATR信号的结构的框图。 8. [0069] ISO/IEC 7816-3 中规定的 ATR 信号是串行传输的字节组合。 ISO/IEC 7816-3 中规定了每个字节的使用。 此外,保留了一些字节的使用。 因此,SIM卡可以通过ATR信号向移动终端指示RFID功能的启动。 例如,可以在特定模式字节TA( 2 )。 特定模式字节 TA( 2 )可用于表示在冷复位后(即当具有RFID模式的SIM卡收到与RFID无关的请求时,从特定模式转移到RFID模式) 移动终端。例如,当移动终端请求用户的ID时)。 此外,特定模式字节 TA( 2 ) 可用于在 RFID 询问器接近 SIM 卡时指示 RFID 模式的开始(即,通知从通信模式转换到 RFID 模式)。 [0070] 根据本发明的另一个实施例,可以将指示RFID模式的位添加到作为接口字节的TD(i)的低四位。 根据 ISO/IEC 7816-3 的标准化,TD(i) 和 TA( 2 )被定义为参数T,其中一些参数(T=5到13)的使用被保留以供将来使用。 因此,将一些T值用于RFID的目的并不违反ISO/IEC 7816-3的标准化,因此SIM卡可以灵活地用于常规系统中。 [0071] 如图。 图10是示出配备有具有RFID部分的SIM卡的移动终端的结构的示意图。 [0072] 参考数字 900 代表移动终端ME的处理器。 处理器的一个示例是可从高通公司获得的称为“移动处理器”的移动站调制解调器 (MSM) 芯片。 [0073] 参考数字 950 代表 SIM 卡。 具有RFID部分的SIM卡安装在移动终端中,以便用信号通知模式转换到RFID模式。 为此,一个CPU 912 , SIM 部分 914 和一个 RFID 部分 916 SIM卡的 950 仅在图 1 中说明。 10. SIM卡的已知组件 950 在图 1 中未示出。 10. [0074] SIM 部分 914 是用户信息处理部分,用于存储用户信息并生成包括用户信息的用户信息信号。 此外,用户信息处理部分包括用于存储用户信息的用户信息存储部分和具有生成用户信息信号的程序的用户程序存储部分。 用户信息存储部分包括 EEPROM 404 用户程序存储器部分包括 ROM 410 ,如图所示。 3. 另外,用户信息存储部分包括 EEPROM 506 用户程序存储器部分包括 ROM 504 如图所示。 4. [0075]RFID部分 916 是RFID信息处理部分,能够存储和处理RFID数据并生成包括RFID数据的RFID信号。 此外,RFID信息处理部分包括用于存储RFID信息的RFID信息存储部分和用于生成RFID信号的RFID功能部分。 可在 EEPROM 中提供 RFID 信息存储部分 404 或只读存储器 410 , RFID功能部分包括RFID CODEC部分 406 和 RFID 调制部分 410 如图所示。 3.另外,可在EEPROM中提供RFID信息存储部分 506 或只读存储器 504 , RFID功能部分包括RFID CODEC部分 508 和 RFID 调制部分 510 ,如图所示。 4. [0076] 中央处理器 912 是主计算部分,连接到用户信息处理部分以命令生成用户信息信号以发送用户信息信号,并连接到RFID信息处理部分以命令生成RFID信号以发送 射频识别信号。 中央处理器 912 对应CPU 402 如图所示。 3和CPU 500 如图所示。 4. [0077] 当RFID询问器(未示出)在预定距离内接近移动终端MT时,RFID部分 916 SIM卡的 950 安装在移动终端 MT 中检测到 RFID 询问器的接近。 在检测到 RFID 询问器后,RFID 部分 916 将检测数据传输到 CPU 912 SIM卡的 950 使 SIM 卡 950 认识到必须执行 RFID 功能。 因此,CPU 912 SIM卡的 950 向处理器发送信号 900 将移动终端的模式转换为RFID模式。 另外,SIM卡的一种模式 950 转换成RFID功能模式以执行RFID功能。 [0078] 根据本发明,移动终端可以向RFID功能块提供稳定的时钟和稳定的电源,而不是从RFID询问器接收电力或向使用线圈连接部分并提取时钟的功能块提供时钟 来自 RFID 读写器发送的载波信号,从而稳定系统。 如果载波信号和感应电动势劣化,传统系统可能会因射频馈电环境而变得不稳定。 [0079] 如上所述,本发明利用SIM卡执行RFID功能的优点包括: [0080] 首先,SIM卡可以可拆卸地安装在移动终端中以执行RFID功能,但是作为重要事项的移动终端的便携性和小型化并没有因此得到改善。 如果RFID标签与SIM卡分开制作,移动终端可能无法满足便携性和小型化的要求。 [0081] 其次,在功能方面,本发明可以对传统的SIM卡进行升级,从而可以为SIM卡创造新的需求。 [0082] 第三,由于通过SIM卡提供了RFID技术,先进的RFID技术可以应用于传统的移动通信系统。 如果RFID标签与SIM卡分开制作,RFID标签可能会固定在移动终端中,因此很难将先进的RFID技术应用到移动终端中。 [0083] 第四,通过管理SIM卡向订户提供服务的服务提供商的盈利率可能会增加。 这是因为在SIM卡中采用了作为新服务基础的RFID技术,使得可以提供基于传统支付收费系统和传统用户管理系统的附加技术。 如果RFID标签与SIM卡分开制造,则难以提供利用RFID标签的新服务,导致服务提供商的盈利率下降。 [0084]尽管本发明已经参照其某些优选实施例进行了展示和描述,但本领域技术人员将理解,在不背离所定义的本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变 根据所附权利要求。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.061 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN100342393C(String), CN1627321A(String), EP1536573A2(String), EP1536573A3(String), EP1536573B1(String), JP2005166047A(String), KR100566260B1(String), KR1020050051508A(String), US20050116050A1(String), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.063 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN100342393C(String), CN1627321A(String), EP1536573A2(String), EP1536573A3(String), EP1536573B1(String), JP2005166047A(String), KR100566260B1(String), KR1020050051508A(String), US20050116050A1(String), US7374100B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.064 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.072 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN100342393C(String), CN1627321A(String), EP1536573A2(String), EP1536573A3(String), EP1536573B1(String), JP2005166047A(String), KR100566260B1(String), KR1020050051508A(String), US20050116050A1(String), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.073 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), CN100342393C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.083 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.084 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), CN1627321A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.096 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), EP1536573A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.106 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), EP1536573A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.114 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), EP1536573B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.124 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), JP2005166047A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.131 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), KR100566260B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.138 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), KR1020050051508A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.146 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.146 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.146 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), US20050116050A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.155 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270721(Integer), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.164 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7374100B2(String), US7374100B2(String), 1211212800(Integer), 270721(Integer), 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.176 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.178 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.180 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185046(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.181 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.182 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185046(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.197 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.198 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.199 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185046(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.200 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.201 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185046(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.218 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.219 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.221 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.222 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.223 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.241 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.242 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.243 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.245 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185046(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.265 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.267 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9986457B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.269 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal device, wireless communication method for mobile terminal device, carrier server device, and communication speed control method in carrier server device(String), 移动终端设备、移动终端设备的无线通信方法、运营商服务器设备以及运营商服务器设备中的通信速度控制方法(String), US9986457B2(String), Excellent communication is to be enabled even in a communication environment with poor line quality. A mobile terminal acquires communication state information indicating a state of communication with a base station, and sends this communication state information to a carrier server device through the base station. The carrier server device receives this communication state information, and, based on this communication state information, controls the communication speed of content data to be transmitted from a web server to the mobile terminal device through the base station. The carrier server device sends this content data having the controlled communication speed to the mobile terminal through the base station.(String), 即使在线路质量较差的通信环境中也能实现出色的通信。 移动终端获取表示与基站的通信状态的通信状态信息,并通过基站将该通信状态信息发送给运营商服务器设备。 运营商服务器设备接收该通信状态信息,并且基于该通信状态信息,控制要从网络服务器通过基站发送到移动终端设备的内容数据的通信速度。 运营商服务器设备通过基站将该具有受控通信速度的内容数据发送到移动终端。(String), US14/901691(String), 1402848000(Integer), US9986457B2(String), 1527523200(Integer), 1527523200(Integer), 美国(String), 4(Integer), JP(String), 2(Integer), 19(Integer), JP2010080135A | JP2012151769A | JP2013148182A | JP2014007328A | JP2014083008A | JPWO2012176771A1 | US20020101827A1 | US20030191856A1 | US20060140369A1 | US20070115796A1 | US20100113037A1 | US20120166665A1 | US20130016221A1 | US20130215813A1 | US20140105035A1 | US20140241161A1 | US6185414B1 | US6757245B1 | US8340678B1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.289 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185047(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.291 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.292 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\119d10a58d844b7c9446dff20f6d3d79.png(String), 185047(Integer), 119d10a58d844b7c9446dff20f6d3d79.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.307 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.308 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.309 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal device, wireless communication method for mobile terminal device, carrier server device, and communication speed control method in carrier server device(String), 移动终端设备、移动终端设备的无线通信方法、运营商服务器设备以及运营商服务器设备中的通信速度控制方法(String), US9986457B2(String), Excellent communication is to be enabled even in a communication environment with poor line quality. A mobile terminal acquires communication state information indicating a state of communication with a base station, and sends this communication state information to a carrier server device through the base station. The carrier server device receives this communication state information, and, based on this communication state information, controls the communication speed of content data to be transmitted from a web server to the mobile terminal device through the base station. The carrier server device sends this content data having the controlled communication speed to the mobile terminal through the base station.(String), 即使在线路质量较差的通信环境中也能实现出色的通信。 移动终端获取表示与基站的通信状态的通信状态信息,并通过基站将该通信状态信息发送给运营商服务器设备。 运营商服务器设备接收该通信状态信息,并且基于该通信状态信息,控制要从网络服务器通过基站发送到移动终端设备的内容数据的通信速度。 运营商服务器设备通过基站将该具有受控通信速度的内容数据发送到移动终端。(String), US14/901691(String), 1402848000(Integer), US9986457B2(String), 1527523200(Integer), 1527523200(Integer), 美国(String), 3(Integer), 4(Integer), JP(String), 2(Integer), 19(Integer), JP2010080135A | JP2012151769A | JP2013148182A | JP2014007328A | JP2014083008A | JPWO2012176771A1 | US20020101827A1 | US20030191856A1 | US20060140369A1 | US20070115796A1 | US20100113037A1 | US20120166665A1 | US20130016221A1 | US20130215813A1 | US20140105035A1 | US20140241161A1 | US6185414B1 | US6757245B1 | US8340678B1(String), \20230420\119d10a58d844b7c9446dff20f6d3d79.png(String), 12(Integer), 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.328 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.329 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.330 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 1. A mobile terminal device comprising:processing circuitry configured to acquire communication state information indicating a state of communication with a base station;a transmitter configured to transmit the communication state information to a carrier server device through the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas, off-line areas, or crowd density information; anda receiver configured to receive content data from a provider server through the carrier server device and the base station, while a communication speed is controlled based on the communication state information,wherein the processing circuitry is further configured to receive updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, andwherein when the updated communication speed corresponds to data size reduction, a data size reduction history is generated, wherein the carrier server device calculates a reward for the provider server based on the data size reduction history.(String), 1.移动终端设备包括:处理电路,被配置为获取指示与基站的通信状态的通信状态信息;发送器,被配置为通过基站向运营商服务器设备发送通信状态信息,其中通信状态信息基于由运营商服务器设备提供给移动终端设备的数据库来更新,其中数据库被提供给移动设备终端设备基于移动终端设备的位置,数据库为在线区域、离线区域或人群密度信息的数据库;和接收器被配置为通过运营商服务器设备和基站从提供商服务器接收内容数据,同时基于通信状态信息控制通信速度,其中,处理电路还被配置为基于移动终端设备的特定动作接收更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时隙,和其中,当更新的通信速度对应于数据大小减少时,生成数据大小减少历史,其中运营商服务器设备基于数据大小减少历史计算对提供商服务器的奖励。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 2. The mobile terminal device according to claim 1, wherein the communication state information is an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value.(String), 2.如权利要求1所述的移动终端装置,其中通信状态信息为根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计线路速度与阈值进行比较得到的线路质量信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 3. The mobile terminal device according to claim 1, wherein the processing circuitry is further configured to set a time-out period related to connection to the provider server or downloading of the content data from the provider server based on the communication state information.(String), 3.根据权利要求1所述的移动终端设备,其中处理电路还被配置为基于通信状态信息设置与连接到提供商服务器或从提供商服务器下载内容数据相关的超时期限。4、一种移动终端设备的无线通信方法,包括:信息获取步骤,获取表示与基站的通信状态的通信状态信息;信息传输步骤,通过基站向运营商服务器设备传输通信状态信息,其中通信状态信息基于运营商服务器设备提供给移动终端设备的数据库进行更新,其中数据库被提供给移动终端设备基于移动终端设备的位置和数据库是在线区域离线区域数据库,或者人群密度信息;和数据接收步骤,通过运营商服务器设备和基站从供应商服务器接收内容数据,同时基于通信状态信息控制通信速度,进一步的信息获取步骤,基于移动终端设备的特定动作接收更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时间段,以及其中,当更新的通信速度对应于数据大小减少时,生成数据大小减少历史,其中运营商服务器设备基于数据大小减少历史计算对提供商服务器的奖励。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 4. A wireless communication method for a mobile terminal device, comprising:an information acquisition step of acquiring communication state information indicating a state of communication with a base station;an information transmission step of transmitting the communication state information to a carrier server device through the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas off-line areas, or crowd density-information; anda data reception step of receiving content data from a provider server through the carrier server device and the base station, while a communication speed is controlled based on the communication state information,a further information acquisition step of receiving updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, andwherein when the updated communication speed corresponds to data size reduction, a data size reduction history is generated, wherein the carrier server device calculates a reward for the provider server based on the data size reduction history.(String), 5.运营商服务器设备包括:接收器被配置为通过基站从移动终端设备接收通信状态信息,通信状态信息指示与基站的通信状态,其中通信状态信息基于提供给移动终端设备的数据库被更新运营商服务器设备,其中数据库是根据移动终端设备的位置提供给移动终端设备的,数据库是在线区域、离线区域或人群密度信息的数据库。和处理电路,配置为基于通信状态信息控制内容数据的通信速度,内容数据通过基站从供应商服务器发送到移动终端设备,处理电路还被配置为基于移动终端设备的特定动作提供更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时隙,以及其中,当更新的通信速度对应于数据大小减少时,生成数据大小减少历史,其中处理电路基于数据大小减少历史计算提供者服务器的奖励。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 5. A carrier server device comprising:a receiver configured to receive communication state information from a mobile terminal device through a base station, the communication state information indicating a state of communication with the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas, off-line areas, or crowd density information; andprocessing circuitry configured to control a communication speed of content data based on the communication state information, the content data being transmitted from a provider server to the mobile terminal device through the base station,the processing circuitry further configured to provide updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, andwherein when the updated communication speed corresponds to data size reduction, a data size reduction history is generated, wherein the processing circuitry calculates a reward for the provider server based on the data size reduction history.(String), 6.根据权利要求5所述的运营商服务器设备,其中通信状态信息为根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计线路速度与阈值进行比较得到的线路质量信息。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 6. The carrier server device according to claim 5, wherein the communication state information is an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value.(String), 7.根据权利要求5所述的运营商服务器设备,其中处理电路还被配置为将通信状态信息所指示的通信状态划分为多个等级,以及根据各个级别控制通信速度。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 7. The carrier server device according to claim 5, wherein the processing circuitry is further configured todivide the communication state indicated by the communication state information into a plurality of levels, andcontrol the communication speed in accordance with the respective levels.(String), 8.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为根据内容的细节改变通信速度的控制值。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.331 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 8. The carrier server device according to claim 5, wherein the processing circuitry is configured to change a control value for the communication speed in accordance with specifics of content.(String), 9.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为根据移动终端设备的用户的动作的细节改变通信速度的控制值。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 9. The carrier server device according to claim 5, wherein the processing circuitry is configured to change a control value for the communication speed in accordance with specifics of an action of a user of the mobile terminal device.(String), 10.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为当更新的通信速度对应于数据大小时减小要通过基站发送到移动终端设备的内容数据的大小。(String), 1(Integer), 8(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 10. The carrier server device according to claim 5, wherein the processing circuitry is configured to reduce size of the content data to be transmitted to the mobile terminal device through the base station, when the updated communication speed corresponds to data size reduction.(String), 11.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为根据通信状态信息判断线路质量是否良好,在线路质量好的情况下,将优惠券设置为可用状态,不限制通信速度,以及当线路质量不好时,将优惠券设置为不可用状态,并将通信速度限制在预定值。12、一种运营商服务器设备中的通信速度控制方法,包括:信息接收步骤,通过基站从移动终端设备接收通信状态信息,通信状态信息指示与基站的通信状态,其中通信状态信息基于提供给移动终端设备的数据库被更新由运营商服务器设备,其中数据库是根据移动终端设备的位置提供给移动终端设备的,数据库是在线区域、离线区域或人群密度信息的数据库。和速度控制步骤,控制当内容数据通过基站从供应商服务器发送到移动终端设备时的通信速度,该通信速度基于通信状态信息被控制,通信速度提供步骤,基于移动终端设备的特定动作提供更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时间段,以及奖励计算步骤,当更新的通信速度对应于数据量减少时,生成数据量减少历史,其中基于数据量减少历史计算提供者服务器的奖励。(String), 1(Integer), 9(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 11. The carrier server device according to claim 5, wherein the processing circuitry is configured todetermine whether line quality is good based on the communication state information,set a coupon into a usable state and not restrict the communication speed when the line quality is good, andset the coupon into an unusable state and restrict the communication speed to a predetermined value when the line quality is not good.(String), 1(Integer), 10(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.332 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185047(Integer), 12. A communication speed control method in a carrier server device, comprising:an information reception step of receiving communication state information from a mobile terminal device through a base station, the communication state information indicating a state of communication with the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas, off-line areas, or crowd density information; anda speed control step of controlling a communication speed at a time when content data is transmitted from a provider server to the mobile terminal device through the base station, the communication speed being controlled based on the communication state information,a communication speed providing step of providing updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, anda reward calculating step of, when the updated communication speed corresponds to data size reduction, generating a data size reduction history, wherein a reward is calculated for the provider server based on the data size reduction history.(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.426 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.427 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.428 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185047(Integer), TECHNICAL FIELD [0001]The present technology relates to a mobile terminal device, a wireless communication method for a mobile terminal device, a carrier server device, and a communication speed control method in a carrier server device. BACKGROUND ART [0002]In conventional cellular networks or Wireless Local Area Networks (WLANs), service quality is secured by controlling error rates and transmission speeds by varying control parameters in the physical layers (PHY) in accordance with the states of wireless transmission paths, or controlling retransmission and congestion through Medium Access Control (MAC). However, the control is not sufficient. [0003]In a communication environment with poor line quality, throughput is low. For example, Patent Document 1 discloses a method of measuring or estimating line quality. In an environment with low throughput, services are preferably provided at low prices. In an environment with high throughput, services are preferably provided at high prices. [0004]There have been systems with which speed restrictions are lifted upon payment of additional charge (with a coupon). For example, a user pays for the coupon, and manually validates the coupon on the Internet through a personal computer (PC), so that the speed restrictions are lifted. CITATION LIST Patent Document [0005]Patent Document 1: JP 2011-10267 A SUMMARY OF THE INVENTION Problems to be Solved by the Invention [0006]The present technology aims to enable excellent communication even in a communication environment with poor line quality. Solutions to Problems [0007]A concept of the present technology lies in a mobile terminal device that includes: [0008]an information acquiring unit that acquires communication state information indicating a state of communication with a base station; [0009]an information transmitting unit that transmits the communication state information to a carrier server device through the base station; and [0010]a data receiving unit that receives content data from a web server through the carrier server device and the base station, while a communication speed is controlled based on the communication state information. [0011]In the present technology, the information acquiring unit acquires the communication state information indicating a state of communication with the base station. For example, the communication state information may be an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value. The information transmitting unit sends the communication state information to the carrier server device through the base station. While the communication speed is controlled based on the communication state information, the data receiving unit receives content data from the web server through the carrier server device and the base station. [0012]As described above, in the present technology, the communication state information indicating a communication state with the base station is acquired, and is transmitted to the carrier server device. Accordingly, the communication speed of the content data to be transmitted from the web server can be set in accordance with the communication state information, and excellent communication can be conducted even in a communication environment with poor line quality. That is, the wireless resource that can be allotted to other users can be increased, and line load can be reduced, for example. Also, the most basic communication environment is provided, so that a more stable system can be established, for example. [0013]In the present technology, the mobile terminal device may further include a time-out period setting unit that sets a time-out period related to connection to the web server or downloading of the content data from the web server based on the communication state information, for example. In this case, the time-out period is shortened in an environment with poor line quality, for example, and accordingly, unnecessarily long occupation of a wireless line is prevented. [0014]Another concept of the present technology lines in a carrier server device that include: [0015]an information receiving unit that receives communication state information from a mobile terminal device through a base station, the communication state information indicating a state of communication with the base station; and [0016]a speed control unit that controls a communication speed at a time when content data is sent from a web server to the mobile terminal device through the base station, the communication speed being controlled based on the communication state information. [0017]In the present technology, from the mobile terminal device through the base station, the information receiving unit receives the communication state information indicating a state of communication with this base station. For example, the communication state information may be an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value. [0018]Based on the communication state information, the speed control unit controls the communication speed at a time when content data is transmitted from the web server to the mobile terminal device through the base station. For example, the speed control unit may divide the communication state indicated by the communication state information into more than one level, and control the communication speed in accordance with the respective levels. [0019]As described above, in the present technology, the communication speed at a time when content data is sent from the web server to the mobile terminal device through the base station is controlled based on the communication state information indicating a state of communication between the mobile terminal device and the base station. Accordingly, the communication speed of the content data to be transmitted from the web server can be set in accordance with the communication state information, and excellent communication can be conducted even in a communication environment with poor line quality. That is, the wireless resource that can be allotted to other users can be increased, and line load can be reduced, for example. Also, the most basic communication environment is provided, so that a more stable system can be established, for example. [0020]In the present technology, the speed control unit may change the control value for the communication speed in accordance with the specifics of content, for example. Also, the speed control unit may change the control value for the communication speed in accordance with the specifics of an action of the user of the mobile terminal device, for example. With this, the mobile terminal device can acquire content data at the communication speed in accordance with the specifics of the content or the specifics of an action of the user. [0021]In the present technology, the carrier server device may further include a data size control unit that reduces the size of the content data to be transmitted to the mobile terminal device through the base station, when the speed control unit controls the communication speed to become lower, for example. With this, the time required for transmitting content data can be shortened, and long occupation of the wireless resource can be prevented. [0022]In the present technology, the speed control unit may also determine whether line quality is good based on the communication state information, set a coupon into a usable state and not restrict the communication speed when the line quality is good, and set the coupon into an unusable state and restrict the communication speed to a predetermined value when the line quality is not good, for example. In this case, the coupon is automatically put into the unusable state when the communication environment is degraded. Thus, a fee structure that is satisfactory to users can be provided. Effects of the Invention [0023]According to the present technology, excellent communication can be conducted even in a communication environment with poor line quality. That is, the wireless resource that can be allotted to other users can be increased, and line load can be reduced, for example. Also, the most basic communication environment is provided, so that a more stable system can be established, for example. The advantageous effects described in this specification are merely examples, and the advantageous effects of the present technology are not limited to them and may include additional effects. BRIEF DESCRIPTION OF DRAWINGS [0024]FIG. 1 is a block diagram showing an example configuration of a mobile-phone system as an embodiment. [0025]FIG. 2 is a diagram showing an example structure of a mobile terminal. [0026]FIG. 3 is a diagram for explaining the function units at least included in the mobile terminal and the carrier server. [0027]FIG. 4 is a diagram showing an example of a charge screen that is displayed on the mobile terminal when a user performs an operation to increase the remaining amount in a coupon with this mobile terminal. [0028]FIG. 5 is a flowchart showing an example of the procedures in a process of putting the coupon into an on- or off-state. [0029]FIG. 6 is a diagram showing an example of the service parameters that are stored and managed in a parameter management table. [0030]FIG. 7 is a diagram schematically showing an example configuration of a speed control system in the carrier server. [0031]FIG. 8 is a diagram schematically showing an example configuration of a speed control system in a case where a set speed R0 is changed in accordance with the specifics of content (content type, priority, and the like). [0032]FIG. 9 is a diagram schematically showing an example configuration of a speed control system in a case where the set speed R0 is changed in accordance with the specifics of an action of the user. [0033]FIG. 10 is a diagram schematically showing an example configuration of a data size control system. [0034]FIGS. 11(a) to 11(c) are diagrams for explaining a structure for enabling a data size reduction process on the side of the provider server. [0035]FIG. 12 is a diagram for explaining a business model in which a mobile-phone operator pays a reward to a provider. MODES FOR CARRYING OUT THE INVENTION [0036]The following is a description of a mode for carrying out the invention (the mode will be hereinafter referred to as the “embodiment”). Explanation will be made in the following order. [0037]1. Embodiment [0038]2. Modifications 1. Embodiment [0039][Example Configuration of a Mobile-Phone System] [0040]FIG. 1 shows an example configuration of a mobile-phone system 10 as an embodiment. This mobile-phone system 10 includes: a communication network 11 of the telecommunications carrier that runs this mobile-phone system; a base station 12 of the mobile-phone system; and a mobile terminal 13 of each subscriber who subscribes to the mobile-phone system. [0041]This mobile-phone system 10 also includes a carrier server (proxy server) 15 that controls connection between the communication network 11 and the Internet 15. A server (provider server) 16 of an Internet provider to which the user of the mobile terminal 13 subscribe is connected as a web server to the Internet 15, for example. [0042]FIG. 2 shows an example structure of the mobile terminal 13. This mobile terminal 13 includes an antenna 101, a communication interface unit (communication I/F unit) 102, a control unit 103, and a user interface unit (user I/F unit) 104. [0043]The antenna 101 receives radio waves from the base station 12, outputs the received signal to the communication I/F unit 102, and outputs a signal from the communication I/F unit 102 in the form of radio waves. The communication I/F unit 102 is an interface for conducting communication (data communication) with the base station 12, and establishes a link to the base station 12 or cuts off an established link to the base station 12. [0044]The control unit 103 is formed with a CPU, a ROM, a RAM, and the like, and controls operation of the entire device. The user I/F unit 104 is formed with a keyboard, a tablet, an input pen, a display, or a speaker, for example, and receives an information input from the user, supplies the information input to the control unit 103, and, to the user, presents information supplied from the control unit 103. [0045]FIG. 3 shows the function units at least included in the mobile terminal 13 and the carrier server 14. The mobile terminal 13 includes an information acquiring unit 131, an information transmitting unit 132, a data receiving unit 133, and a time-out period setting unit 134. The information acquiring unit 131 acquires communication state information indicating a state of communication with the base station 12. In this embodiment, the communication state information may be an estimated line speed Ro estimated from a congestion degree and an interference wave intensity, and/or a line quality flag Fq obtained by comparing the estimated line speed Ro with a threshold value Rt, for example. [0046]The estimated line speed Ro is now explained. In estimating a line speed, (1) line quality, or a signal-to-interference ratio (SIR) of a signal from the base station 12, is determined, (2) the maximum speed corresponding to this SIR is determined, and (3) an effective communication rate is determined at last. [0047]Here, the line quality is calculated from a congestion degree and an interference wave intensity. The congestion degree is the ratio of the occupied bandwidth to the allowed bandwidth of the base station. The interference waves are signals from other base stations in the neighborhood, and are the interference waves that reach the terminal. Even where the congestion degree is low, if the interference waves are strong, the congestion degree appears to be equivalently high. The maximum speed is determined from a speed table that is specified in accordance with the line quality and the wireless system specifications, for example. The effective communication rate is calculated by applying a certain conversion formula to the maximum speed. This effective communication rate calculation is disclosed in JP 2012-9987 A, for example. The congestion degree Kcong in this publication is a congestion degree in a broad sense including interference waves, and is equivalent to line quality. Further, the SIR indicates the SIR of the reference signal (that is, SIR_CPICH), and reflects the excess bandwidth of the base station, rather than simply reflecting signal intensity. In LTE, a value called Reference Signal Received Quality (RSRQ) may also be used. [0048]Next, the line quality flag Fq is explained. The line quality flag Fq is obtained by comparing the estimated line speed Ro with the threshold value Rt. For example, where Ro>Rt, Fq is set to “1”, and “line quality is good” is displayed. Where Ro≤Rt, on the other hand, Fq is set to “0”, and “line quality is not good” is displayed. [0049]Here, the threshold value Rt is a constant value of 150 kbps, for example. Alternatively, this threshold value Rt may be determined based on a frequency distribution graph of transmission speeds used by the user. For example, in a case where the frequency distribution is polarized, the threshold value Rt is determined to be the intermediate value. Also, the threshold value Rt may be determined to be the standard deviation σ or a value a predetermined number of times larger than the standard deviation σ. Alternatively, frequency distribution graphs may be created for the respective types of content viewed by the user, and threshold values may be determined for the respective types of content. In this case, the line quality flag Fq is obtained for each of the types of content. [0050]Instead of the two-valued line quality flag Fq, a multivalued line quality index Iq may be used. The line quality index Iq is obtained by comparing the estimated line speed Ro with more than one threshold value Rt. [0051]The line quality information (the line quality flag Fq or the line quality index Iq) may be incremented or decremented with the use of a database supplied from the carrier server 14, for example. This database is a database of off-line areas (poor reception areas), on-line areas (good reception areas), or crowd density information. Current location information obtained by a GPS function (not shown) of the mobile terminal 13 is transmitted to the carrier server 14, so that the carrier server 14 can recognize where the user is located, and provide an appropriate database to the mobile terminal 13. [0052]The line quality information varies with time. If there is statistical information indicating that the line is often congested or the line quality is often poor in that area according to statistics, the statistical information can be used as previous knowledge that, even if the line quality information indicates good quality at the moment, the line quality tends to soon deteriorate. In such a location, good line quality cannot be expected to last long, and therefore, the line quality index Iq is downgraded, for example. [0053]The information transmitting unit 132 sends the communication state information acquired by the information acquiring unit 131 to the carrier server 14 through the base station 12. While the communication speed is controlled based on the communication state information, the data receiving unit 133 receives content data from the provider server 16 through the carrier server device 14 and the base station 12. [0054]Based on the communication state information, the time-out period setting unit 134 sets a time-out period related to connection to the provider server 16 (connection time-out period), and a time-out period related to downloading of content data from the provider server 16 (communication completion time-out period). The set value of this time-out period exists in an HTTP module in the mobile terminal 13. [0055]If the communication state is not good in this case, the time-out period is shortened. For example, the time-out period is set at two or more, or three or more levels, so that, as the estimated line speed becomes lower, the time-out period becomes shorter. With this, the time-out period is shortened in an environment with poor line quality, and accordingly, unnecessarily long occupation of the wireless line is prevented. Such a time-out period can also be set in the carrier server 14. [0056]Meanwhile, the carrier server 14 includes an information receiving unit 141, a data transmitting unit 142, a speed control unit 143, a data size control unit 144, and a parameter managing unit 145. From the mobile terminal 13 through the base station 12, the information receiving unit 141 receives the communication state information indicating a state of communication with this base station 12. As described above, this communication state information is the estimated line speed Ro calculated from a congestion degree and an interference wave intensity, and/or the line quality information (the line quality flag Fq or the line quality index Iq) obtained by comparing the estimated line speed Ro with the threshold value Rt. The data transmitting unit 142 transmits content data from the provider server 16 having its communication speed and data size controlled as necessary, to the mobile terminal 13 via the base station 12. [0057]Based on the communication state information received by the information receiving unit 141, the speed control unit 143 controls the communication speed at which content data is transmitted from the provider server 16 to the mobile terminal 13 through the base station 12. The speed control unit 143 determines the line quality information (the line quality flag Fq or the line quality index Iq) from the estimated line speed Ro as the communication state information in the same manner as in the above described mobile terminal 13, and controls the communication speed based on this line quality information. Alternatively, the speed control unit 143 controls the communication speed based on the line quality information (the line quality flag Fq or the line quality index Iq) as the communication state information. [0058]In this case, the communication speed is controlled to be set at two or more, or three or more levels. For example, the communication speed is controlled to be set at two levels depending on whether the estimated line speed Ro is higher than the threshold value Rt. In a case where the threshold value Rt is 150 kbps, for example, the speed control unit 143 restricts the communication speed to 150 kbps when Ro≤Rt and the line quality is not good, but does not restrict the communication speed when Ro>Rt and the line quality is good. [0059]In this case, the coupon is in an off-state (unusable state) when Ro≤Rt, and the coupon is in an on-state (usable state) when Ro>Rt. It should be noted that the coupon can be used only when there is a remaining amount in the coupon. FIG. 4 shows an example of a charge screen that is displayed on the mobile terminal 13 when the user performs an operation to increase the remaining amount in the coupon with this mobile terminal 13, for example. As the user places a check in a desired item in the check column, and presses the charge button, the remaining amount in the coupon is increased. [0060]The flowchart in FIG. 5 shows an example of the procedures in the process of putting the coupon into an on- or off-state. In step ST1, the speed control unit 143 starts the process, and then moves on to the procedure in step ST2. In step ST2, the speed control unit 143 determines whether there is a remaining amount in the coupon. [0061]If there is a remaining amount in the coupon, the speed control unit 143 in step ST3 determines whether Ro>Rt. If Ro>Rt, the speed control unit 143 in step ST4 puts the coupon into the on-state (usable state). In this state, the speed control unit 143 does not restrict the communication speed. After that, the speed control unit 143 in step ST6 ends the process. [0062]If not Ro>Rt, on the other hand, the speed control unit 143 in step ST5 puts the coupon into the off-state (unusable state). In this state, the speed control unit 143 restricts the communication speed to 150 kbps. After that, the speed control unit 143 in step ST6 ends the process. [0063]Even where the coupon is in the on-state (usable state), if all the remaining amount in the coupon is spent on usage of the line, the speed control unit 143 immediately puts the coupon into the off-state (unusable state), and restricts the communication speed to 150 kbps. [0064]The parameter managing unit 145 manages the service parameters of each user, using a parameter management table. FIG. 6 shows an example of the service parameters that are stored and managed in the parameter management table. In this example, the remaining amount in the coupon and the coupon status are managed under the user ID. [0065]FIG. 7 schematically shows an example configuration of a speed control system 150 in the carrier server 14. This speed control system 150 includes a switch 151, a transmission speed measuring unit 152, and a control unit 153. The transmission speed measuring unit 152 measures the number R1 of bytes per second in content data flowing from the provider server 16 into the mobile terminal 13, for example. The control unit 153 compares the measured number R1 of bytes with a set speed R0, and controls switching on and off of the switch 151 based on the comparison result, so that R1 becomes equal to R0. [0066]Although the communication speed is not restricted when the coupon is in the on-state in the above description, the value of the communication speed may be restricted when the coupon is in the on-state. Although the communication speed is restricted to 150 kbps when the coupon is in the off-state in the above description, the speed value may be more finely restricted. [0067]Normally, the set speed R0 is determined by the ratio between a content size and an expected reaction time. The content size and the expected reaction time are determined by the type of the content and the state of the user. For example, the speed control unit 143 may change the set speed R0 in accordance with the specifics of the content (content type or priority). With this, the reaction time corresponding to the content type or priority (the time until web pages become available for access) can be achieved. For example, the data size is normally small in the case of text content, and the data size is normally large in the case of image content. Therefore, the set speed R0 is reduced in the case of text content, and the set speed R0 is increased in the case of image content. Also, as for the same image content, the priority is determined to be higher if the user is more interested in the image content, and the set speed R0 is made higher if the priority is higher, for example. [0068]FIG. 8 schematically shows an example configuration of a speed control system 150A in a case where the set speed R0 is changed in accordance with the specifics of content (content type, priority, and the like). In FIG. 8, the components equivalent to components shown in FIG. 7 are denoted by the same reference numerals as those used in FIG. 7, and detailed explanation of them is not repeated herein. The speed control system 150A includes a switch 151, a transmission speed measuring unit 152, a control unit 153, a speed table 154, and a content analyzing unit 155. [0069]The content analyzing unit 155 identifies the specifics of content (content type, priority, and the like) by analyzing the content data flowing from the provider server 16 into the mobile terminal 13. The content analyzing unit 155 may identify the content type in accordance with the reference URL on the web page, the MIME format information in the http header, the address information in the http header or the IP header, data size information, or the like. Also, the content analyzing unit 155 may identify the content type in accordance with the extension of the reference URL, such as mp4, av, mov, or jpg. [0070]The content analyzing unit 155 may also identify priority by taking the user's situation into consideration. For example, the user often views entertainment information pages when in a residential area, and often view shop information pages when in a commercial area. Alternatively, the specifics of content (content, type, priority, and the like) may be identified on the side of the mobile terminal 13, and be transmitted to the carrier server 14. In that case, the content analyzing unit 155 becomes unnecessary. [0071]The result of the identification of the specifics of the content is supplied to the speed table 154. The speed table 154 outputs the set speed R0 corresponding to the result of the identification of the content specifics and the service status (the remaining amount in the coupon and the coupon status) (see FIG. 6) to the control unit 153. [0072]The speed control unit 143 may also change the set speed R0 in accordance with the specifics of an action of the user. For example, the specifics of an action of the user are identified based on the user information shown below. Specifically, the user information may be a timetable, a memorandum, a log-in ID, a log-in time, a log-in location, a log-out time, a log-out location, a purchase history, an access history, a history of locations of actions, area information (indicating an industrial area, a commercial area, a residential area, or a transportation facility), or the like. [0073]FIG. 9 schematically shows an example configuration of a speed control system 150B in a case where the set speed R0 is changed in accordance with the specifics of an action of the user. In FIG. 9, the components equivalent to components shown in FIG. 7 are denoted by the same reference numerals as those used in FIG. 7, and detailed explanation of them is not repeated herein. The speed control system 150B includes a switch 151, a transmission speed measuring unit 152, a control unit 153, a speed table 156, and a user action identifying unit 157. [0074]The user action identifying unit 157 identifies the specifics of an action of the user based on user information. For example, a place (a poor reception area or a good reception area) to which the user is now heading can be identified from a timetable. Also, a check can be made whether the user is located in a place or a time slot in which image content is often viewed, for example. [0075]The result of the identification of the specifics of an action of the user is supplied to the speed table 156. The speed table 156 outputs the set speed R0 corresponding to the result of the identification of the specifics of the action of the user and the service status (the remaining amount in the coupon and the coupon status) (see FIG. 6) to the control unit 153. [0076]Referring back to FIG. 3, the data size control unit 144 reduces the data size of content data to be transmitted from the provider server 16 to the mobile terminal 13 through the base station 12 based on the communication state information received by the information receiving unit 141. In a case where the estimated line speed Ro is equal to or lower than the threshold value Rt, and the communication speed is restricted to 150 kbps, for example, the data size is reduced. [0077]When web content includes an image or a moving image, for example, the data size control unit 144 performs control to reduce the data size by performing a process to reduce the resolution of the image or the moving image, or performing a process to remove the data of the image or the moving image. Also, the data size control unit 144 performs a process to reduce the data size of moving image content or image (still image) content, but does not perform the process on text content or mail, for example. That is, control is performed to reduce the data size in accordance with the viewing specifics. [0078]As the data size is reduced in the above manner, the time required for content data transmission can be shortened, and long occupation of the wireless resource can be prevented even in a case where the communication speed is restricted to a low value. [0079]FIG. 10 schematically shows an example configuration of a data size control system 160. The data size control system 160 includes a size reduction processing unit 161 and a content analyzing unit 162. The content analyzing unit 162 identifies the specifics of content (content type, content structure, and the like) by analyzing the content data flowing from the provider server 16 into the mobile terminal 13. [0080]In a case where the communication speed is restricted, the size reduction processing unit 161 performs a size reduction process based on the result of the determination on the content specifics. When web content includes an image or a moving image, for example, a process to reduce the resolution of the image or the moving image is performed, or a process to remove the data of the image or the moving image is performed, so that the data size is reduced. [0081]The data size reduction process may not be performed in the carrier server 14. Instead, communication speed restriction information or a data size reduction request may be sent from the carrier server 14 to the provider server 16, and the data size reduction process may be performed on the side of the provider server 16. [0082]FIG. 11(a) shows an example of web content including an image, a moving image, and the like. When there is no data size reduction request, the provider server 16 sends the web content shown in FIG. 11(a) to the mobile terminal 13, as shown in FIG. 11(b). When there is a data size reduction request, however, the provider server 16 sends the web content minus the image, the moving image, and the like of a large data size, to the mobile terminal 13, as shown in FIG. 11(c). [0083]It should be noted that the provider that runs the provider server 16 and the mobile-phone operator may be the same, or may not be the same. In a case where the provider and the mobile-phone operator are not the same, it is also possible to employ a business model that, when the data size reduction process is performed on the side of the provider server 16 as described above, the mobile-phone operator may pay a reward as a token of gratitude to the provider fo(String), 技术领域 [0001] 本 技术涉及移动终端设备、移动终端设备的无线通信方法、运营商服务器设备以及运营商服务器设备中的通信速度控制方法。 背景技术 [0002] 在传统的蜂窝网络或无线局域网 (WLAN) 中,通过根据无线传输路径的状态改变物理层 (PHY) 中的控制参数或控制重传和拥塞来控制错误率和传输速度来确保服务质量 通过媒体访问控制 (MAC)。 然而,控制是不够的。 [0003] 在线路质量较差的通信环境中,吞吐量较低。 例如,专利文献1公开了一种测量或估计线路质量的方法。 在吞吐量低的环境中,最好以低价提供服务。 在具有高吞吐量的环境中,优选地以高价格提供服务。 [0004] 有一些系统可以通过支付额外费用(使用优惠券)取消速度限制。 例如,用户支付优惠券,并通过个人计算机(PC)在互联网上手动验证优惠券,从而取消了速度限制。 引文清单 专利文献 [0005] 专利文献1:JP 2011-10267 A 发明内容 本发明要解决的问题 [0006] 本技术旨在即使在线路质量较差的通信环境中也能实现良好的通信。 问题解决方案 [0007] 本技术的一个概念在于一种移动终端设备,包括: [0008] 信息获取单元,获取指示与基站的通信状态的通信状态信息; [0009] 信息发送单元,通过基站将通信状态信息发送给运营商服务器装置; 和 [0010] 数据接收单元,其通过运营商服务器设备和基站从网络服务器接收内容数据,同时基于通信状态信息控制通信速度。 [0011] 在本技术中,信息获取单元获取指示与基站的通信状态的通信状态信息。 例如,通信状态信息可以是根据拥塞程度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较获得的线路质量信息。 信息发送单元通过基站向运营商服务器设备发送通信状态信息。 在基于通信状态信息控制通信速度的同时,数据接收单元通过运营商服务器设备和基站从网络服务器接收内容数据。 [0012] 如上所述,在本技术中,指示与基站的通信状态的通信状态信息被获取,并且被发送到运营商服务器设备。 因此,可以根据通信状态信息来设置要从网络服务器发送的内容数据的通信速度,并且即使在线路质量差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 [0013] 在本技术中,移动终端设备还可以包括超时时段设置单元,该超时时段设置单元基于通信状态信息设置与连接到网络服务器或从网络服务器下载内容数据相关的超时时间, 例如。 在这种情况下,例如,在线路质量差的环境中,超时周期被缩短,因此,防止了无线线路的不必要的长时间占用。 [0014]运营商服务器设备中的本技术线的另一个概念包括: [0015] 信息接收单元,通过基站从移动终端设备接收通信状态信息,该通信状态信息指示与基站的通信状态; 和 [0016] 速度控制单元,当内容数据通过基站从网络服务器发送到移动终端设备时控制通信速度,通信速度基于通信状态信息来控制。 [0017] 在本技术中,从移动终端装置通过基站,信息接收单元接收指示与该基站的通信状态的通信状态信息。 例如,通信状态信息可以是根据拥塞程度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较获得的线路质量信息。 [0018] 基于通信状态信息,速度控制单元在内容数据通过基站从网络服务器发送到移动终端设备时控制通信速度。 例如,速度控制单元可以将通信状态信息所指示的通信状态划分为多于一个级别,并根据各个级别来控制通信速度。 [0019] 如上所述,在本技术中,基于指示移动终端之间的通信状态的通信状态信息,控制通过基站从网络服务器向移动终端设备发送内容数据时的通信速度。 设备和基站。 因此,可以根据通信状态信息来设置要从网络服务器发送的内容数据的通信速度,并且即使在线路质量差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 [0020] 在本技术中,速度控制单元例如可以根据内容的具体情况改变通信速度的控制值。 此外,例如,速度控制单元可以根据移动终端设备的用户的动作的细节来改变通信速度的控制值。 由此,移动终端装置能够以与内容的内容或用户的动作的内容相应的通信速度来取得内容数据。 [0021] 在本技术中,运营商服务器设备还可以包括数据大小控制单元,当速度控制单元控制通信速度变得更低时,该数据大小控制单元减小要通过基站发送到移动终端设备的内容数据的大小。 , 例如。 由此,可以缩短发送内容数据所需的时间,并且可以防止无线资源的长时间占用。 [0022] 在本技术中,速度控制单元还可以根据通信状态信息判断线路质量是否良好,将优惠券设置为可用状态,在线路质量良好时不限制通讯速度,将优惠券设置为 例如,当线路质量不好时,将通信速度限制在不可用状态并限制在预定值。 在这种情况下,当通信环境恶化时,优惠券会自动进入不可用状态。 因此,可以提供用户满意的费用结构。 本发明的效果 [0023]根据本技术,即使在线路质量较差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 本说明书中描述的有益效果仅仅是示例,并且本技术的有益效果不限于它们并且可以包括附加效果。 附图说明 [0024] 图1是示出作为实施例的移动电话系统的示例配置的框图。 [0025] 图2是表示移动终端的结构例的图。 [0026] 图3是用于说明至少包含在移动终端和运营商服务器中的功能单元的图。 [0027] 图4是示出当用户使用移动终端执行增加优惠券中的剩余金额的操作时在移动终端上显示的收费画面的示例的图。 [0028] 图5是表示将优惠券设为开或关的处理的步骤的一个例子的流程图。 [0029] 图6是示出在参数管理表中存储和管理的服务参数的示例的图。 [0030] 图7是示意性地示出运营商服务器中的速度控制系统的示例配置的图。 [0031] 图8是示意性地表示设定速度R的情况下的速度控制系统的结构例的图。 0 根据内容的具体情况(内容类型、优先级等)改变。 [0032] 图9是示意性地表示设定速度R的情况下的速度控制系统的结构例的图。 0 根据用户动作的具体情况改变。 [0033] 图10是示意性地示出数据大小控制系统的示例配置的图。 [0034] 图11(a)~图11(c)是用于说明在提供者服务器侧能够进行数据大小削减处理的结构的图。 [0035] 图12是用于说明移动电话运营商向提供者支付报酬的商业模式的图。 实施本发明的方式 [0036] 以下是用于实施本发明的模式的描述(该模式将在下文中称为“实施例”)。 将按以下顺序进行说明。 [0037] 一、实施例 [0038] 2. 修改 一、实施例 [0039] [移动电话系统的示例配置] [0040] 图 1 显示了移动电话系统的示例配置 10 作为一个实施例。 这个手机系统 10 包括:通信网络 11 运行该移动电话系统的电信运营商; 一个基站 12 手机系统; 和一个移动终端 13 每个订阅移动电话系统的用户。 [0041] 这个手机系统 10 还包括一个运营商服务器(代理服务器) 15 控制通信网络之间的连接 11 和互联网 15 . 一个服务器(提供者服务器) 16 移动终端用户所在的互联网提供商的 13 subscribe 作为 Web 服务器连接到 Internet 15 , 例如。 [0042] 图2示出了移动终端的示例结构 13 . 这个移动终端 13 包括天线 101 ,一个通讯接口单元(通讯I/F单元) 102 , 一个控制单元 103 , 和一个用户接口单元(用户 I/F 单元) 104 . [0043] 天线 101 从基站接收无线电波 12 , 将接收到的信号输出到通信 I/F 单元 102 , 并从通信 I/F 单元输出信号 102 以无线电波的形式。 通讯接口单元102 是用于与基站进行通信(数据通信)的接口 12 ,并建立到基站的链接 12 或切断与基站的已建立链接 12 . [0044] 控制单元 103 由CPU、ROM、RAM等构成,控制装置整体的动作。 用户接口单元 104 由例如键盘、平板电脑、输入笔、显示器或扬声器构成,并接收来自用户的信息输入,将输入的信息提供给控制单元 103 ,并且,向用户呈现从控制单元提供的信息 103 . [0045] 图3示出了移动终端中至少包括的功能单元 13 和运营商服务器 14 . 移动终端 13 包括信息获取单元 131 , 一个信息传输单元 132 , 一个数据接收单元 133 , 和超时时间设置单元 134 . 信息获取单元 131 获取指示与基站的通信状态的通信状态信息 12 . 在本实施例中,通信状态信息可以是根据拥塞度和干扰波强度估计的估计线路速度Ro,和/或通过将估计的线路速度Ro与阈值Rt进行比较而获得的线路质量标志Fq,例如 . [0046] 现在解释估计的线速度Ro。 在估计线路速度时,(1)线路质量,或来自基站的信号的信干比(SIR) 12 , 确定, (2) 确定该 SIR 对应的最大速度, (3) 最后确定有效通信速率。 [0047] 这里,线路质量是根据拥塞度和干扰波强度计算的。 拥塞度是基站占用带宽与允许带宽之比。 干扰波是来自附近其他基站的信号,是到达终端的干扰波。 即使在拥塞度较低的地方,如果干扰波强,则拥塞度看起来也相当高。 例如,最大速度由根据线路质量和无线系统规范指定的速度表确定。 有效通信速率是通过对最大速度应用一定的换算公式来计算的。 例如,在JP 2012-9987 A中公开了这种有效通信速率计算。 本公报中的拥塞度Kcong是包括干扰波在内的广义的拥塞度,相当于线路质量。 进一步的,SIR表示参考信号的SIR(即SIR_CPICH),反映基站的超额带宽,而不是简单地反映信号强度。 在 LTE 中,也可以使用称为参考信号接收质量 (RSRQ) 的值。 [0048] 接着,说明线路质量标志Fq。 通过将估计的线路速度Ro与阈值Rt进行比较来获得线路质量标志Fq。 例如,在Ro>Rt的情况下,将Fq设置为“1”,并显示“线路质量好”。 另一方面,在Ro≤Rt的情况下,将Fq设为“0”,显示“线路质量不好”。 [0049] 这里,阈值Rt例如是150kbps的恒定值。 或者,该阈值Rt可以基于用户使用的传输速度的频率分布图来确定。 例如,在频率分布被极化的情况下,阈值Rt被确定为中间值。 此外,阈值Rt可以被确定为标准偏差σ或比标准偏差σ大预定倍数的值。 或者,可以针对用户观看的各个类型的内容创建频率分布图,并且可以针对各个类型的内容确定阈值。 在这种情况下,针对每种内容类型获得线路质量标志Fq。 [0050]代替二值线路质量标志Fq,可以使用多值线路质量指标Iq。 通过将估计的线路速度Ro与一个以上的阈值Rt进行比较来获得线路质量指数Iq。 [0051] 线路质量信息(线路质量标志Fq或线路质量指标Iq)可以通过使用从运营商服务器提供的数据库来增加或减少 14 , 例如。 该数据库是离线区域(接收不良区域)、在线区域(接收良好区域)或人群密度信息的数据库。 通过移动终端的GPS功能(未图示)获取的当前位置信息 13 被传送到运营商服务器 14 ,以便运营商服务器 14 可以识别用户所在的位置,并为移动终端提供合适的数据库 13 . [0052] 线路质量信息随时间变化。 如果有统计信息表明该区域的线路经常拥塞或者线路质量经常较差,则该统计信息可以作为先验知识,即使线路质量信息表明当前质量良好, 线路质量往往会很快恶化。 在这样的位置,不能期望良好的线路质量持续很长时间,因此,例如,线路质量指标Iq被降级。 [0053] 信息传递单元 132 发送信息获取单元获取的通信状态信息 131 到运营商服务器 14 通过基站 12 . 在基于通信状态信息控制通信速度的同时,数据接收单元 133 从提供者服务器接收内容数据 16 通过运营商服务器设备 14 和基站 12 . [0054] 基于通信状态信息,超时时间设置单元 134 设置与提供者服务器连接相关的超时时间 16 (连接超时时间),以及与从提供商服务器下载内容数据相关的超时时间 16 (通信完成超时时间)。 该超时时间的设定值存在于移动端的一个HTTP模块中 13 . [0055] 如果在这种情况下通信状态不好,则缩短超时时间。 例如,超时时间被设置为两个或更多,或者三个或更多级别,使得随着估计的线速度变得更低,超时时间变得更短。 由此,在线路质量差的环境中,超时时间被缩短,因此,防止了无线线路的不必要的长时间占用。 这样的超时时间也可以在运营商服务器中设置 14 . [0056] 同时,运营商服务器 14 包括信息接收单元 141 , 一个数据传输单元 142 , 一个速度控制单元 143 , 一个数据大小控制单元 144 , 和一个参数管理单元 145 . 从移动端 13 通过基站 12 ,信息接收单元 141 接收指示与该基站的通信状态的通信状态信息 12 . 如上所述,该通信状态信息是根据拥塞度和干扰波强度计算的估计线路速度Ro,和/或通过比较估计的线路质量信息(线路质量标志Fq或线路质量指标Iq) 线速度 Ro 与阈值 Rt。 数据传输单元 142 从提供者服务器传输内容数据 16 根据需要控制其与移动终端的通信速度和数据大小 13 通过基站 12 . [0057] 基于信息接收单元接收到的通信状态信息 141 , 速度控制单元 143 控制从提供商服务器传输内容数据的通信速度 16 到移动终端 13 通过基站 12 . 速度控制单元 143以与上述移动终端相同的方式,根据估计的线路速度Ro确定线路质量信息(线路质量标志Fq或线路质量指标Iq)作为通信状态信息 13 ,并根据此线路质量信息控制通信速度。 或者,速度控制单元 143 基于作为通信状态信息的线路质量信息(线路质量标志Fq或线路质量指标Iq)控制通信速度。 [0058] 在这种情况下,通信速度被控制为设置为两个或更多,或者三个或更多级别。 例如,根据估计的线路速度Ro是否高于阈值Rt,将通信速度控制为设置为两个级别。 例如,在阈值 Rt 为 150kbps 的情况下,速度控制单元 143 当Ro≤Rt且线路质量不好时将通信速度限制在150 kbps,但在Ro>Rt且线路质量良好时不限制通信速度。 [0059] 在这种情况下,当Ro≤Rt时,优惠券处于关闭状态(不可用状态),而当Ro>Rt时,优惠券处于开启状态(可用状态)。 需要注意的是,优惠券只有在优惠券中有余额时才能使用。 图4示出了在移动终端上显示的充电屏幕的示例 13 当用户使用该移动终端进行增加优惠券余额的操作时 13 , 例如。 当用户在支票栏中勾选想要的项目并按下收费按钮时,优惠券中的剩余金额增加。 [0060] 图5中的流程图示出了将优惠券置于开启或关闭状态的过程中的过程的示例。 在步骤 ST 1 , 速度控制单元 143 开始该过程,然后继续进行步骤 ST 中的过程 2 . 在步骤 ST 2 , 速度控制单元 143 判断优惠券是否有余额。 [0061] 如果优惠券中有剩余金额,则速度控制单元 143 在步骤 ST 3 确定是否 Ro>Rt。 如果 Ro>Rt,则速度控制单元 143 在步骤 ST 4 将优惠券置于开启状态(可用状态)。 在这种状态下,速度控制单元 143 不限制通讯速度。 之后,速度控制单元 143 在步骤 ST 6 结束进程。 [0062] 如果不是 Ro>Rt,另一方面,速度控制单元 143 在步骤 ST 5 将优惠券置于关闭状态(不可用状态)。 在这种状态下,速度控制单元 143 将通信速度限制为 150 kbps。 之后,速度控制单元 143 在步骤 ST 6 结束进程。 [0063] 即使在优惠券处于开启状态(可用状态)的情况下,如果优惠券中的所有剩余金额都用于线路使用,则速度控制单元 143 立即将优惠券置于关闭状态(不可用状态),并将通信速度限制为 150 kbps。 [0064] 参数管理单元 145 使用参数管理表管理每个用户的服务参数。 图6示出了在参数管理表中存储和管理的服务参数的示例。 在本例中,优惠券的剩余金额和优惠券状态在用户ID下进行管理。 [0065] 图7示意性地示出了速度控制系统的示例配置 150 在运营商服务器中 14 . 这种速度控制系统 150 包括一个开关 151 , 一个传输速度测量单元 152 , 和一个控制单元 153 . 传输速度测量单元 152 测量数字 R 1 从提供者服务器流出的内容数据中每秒的字节数 16 进入移动终端 13 , 例如。 控制单元 153 比较实测数 R 1 具有设定速度 R 的字节数 0 , 并控制开关的开启和关闭 151 基于比较结果,使得 R 1 等于 R 0 . [0066]尽管在以上描述中当优惠券处于开启状态时通信速度不受限制,但是当优惠券处于开启状态时可以限制通信速度的值。 尽管在以上描述中当优惠券处于关闭状态时通信速度被限制为150kbps,但是速度值可以被更精细地限制。 [0067] 通常,设定速度 R 0 由内容大小和预期反应时间之间的比率决定。 内容大小和预期反应时间由内容类型和用户状态决定。 例如,速度控制单元 143 可改变设定速度 R 0 根据内容的具体情况(内容类型或优先级)。 这样,可以实现对应于内容类型或优先级的反应时间(直到网页变为可访问的时间)。 例如,文本内容的数据量通常较小,而图​​像内容的数据量通常较大。 因此,设定速度 R 0 在文本内容的情况下减少,设定速度R 0 在图像内容的情况下增加。 并且,对于相同的图像内容,如果用户对图像内容更感兴趣,则确定优先级更高,并且设定速度R 0 例如,如果优先级更高,则设置更高。 [0068] 图8示意性地示出了速度控制系统的示例配置 150 A 在设定速度 R 的情况下 0 根据内容的具体情况(内容类型、优先级等)改变。 在图8中,与图7中所示的部件等效的部件用与图7中使用的相同的附图标记表示,并且在此不再重复对其的详细说明。 速度控制系统 150 A 包括一个开关 151 , 一个传输速度测量单元 152 , 一个控制单元 153 , 速度表 154 和内容分析单元 155 . [0069] 内容分析单元 155 通过分析从提供商服务器流出的内容数据来识别内容的细节(内容类型、优先级等) 16 进入移动终端 13 . 内容分析单元 155 可以根据网页上的引用URL、http头中的MIME格式信息、http头或IP头中的地址信息、数据大小信息等来识别内容类型。 此外,内容分析单元 155 可以根据引用URL的扩展名来识别内容类型,例如mp4、av、mov或jpg。 [0070] 内容分析单元 155 也可以通过考虑用户的情况来确定优先级。 例如,用户在住宅区时常查看娱乐信息页面,而在商业区时常查看商店信息页面。 或者,可以在移动终端侧识别内容的细节(内容、类型、优先级等) 13 ,并传送到运营商服务器 14 . 在这种情况下,内容分析单元 155 变得不必要。 [0071] 将内容细节的识别结果提供给速度表 154 . 速度表 154 输出设定速度R 0 对应于识别内容细节和服务状态的结果(优惠券中的剩余金额和优惠券状态)(见图6)到控制单元 153 . [0072] 速度控制单元 143 也可以改变设定速度R 0 根据用户操作的具体情况。 例如,基于如下所示的用户信息来识别用户的动作的细节。 具体地,用户信息可以是时间表、备忘录、登录ID、登录时间、登录地点、退出时间、退出地点、购买历史、访问历史 、行动位置的历史、区域信息(指示工业区、商业区、住宅区或交通设施)等。 [0073]图9示意性地示出了速度控制系统的示例配置 150 B 在设定速度 R 的情况下 0 根据用户动作的具体情况改变。 在图9中,与图7中所示的部件等效的部件由与图7中使用的相同的附图标记表示,并且在此不再重复对其的详细说明。 速度控制系统 150 B 包括一个开关 151 , 一个传输速度测量单元 152 , 一个控制单元 153 , 速度表 156 ,以及用户动作识别单元 157 . [0074] 用户动作识别单元 157 基于用户信息识别用户动作的细节。 例如,可以从时间表中识别用户现在正前往的地点(差的接待区或好的接待区)。 此外,例如,可以检查用户是否位于经常观看图像内容的地点或时间段。 [0075] 用户动作细节的识别结果被提供给速度表 156 . 速度表 156 输出设定速度R 0 对应于识别用户的动作细节和服务状态(优惠券中的剩余金额和优惠券状态)的结果(见图6)到控制单元 153 . [0076] 返回参考图3,数据大小控制单元 144 减少要从提供商服务器传输的内容数据的数据大小 16 到移动终端 13 通过基站 12 基于信息接收单元接收到的通信状态信息 141 . 在估计线路速度Ro等于或低于阈值Rt并且通信速度被限制为例如150kbps的情况下,数据大小被减小。 [0077] 例如,当网络内容包括图像或运动图像时,数据大小控制单元 144 通过执行降低图像或运动图像的分辨率的处理,或者执行去除图像或运动图像的数据的处理,执行控制以减小数据大小。 此外,数据大小控制单元 144 执行减少运动图像内容或图像(静止图像)内容的数据大小的处理,但不执行例如文本内容或邮件的处理。 即,执行控制以根据观看细节来减小数据大小。 [0078] 通过以上述方式减小数据大小,可以缩短内容数据传输所需的时间,并且即使在通信速度被限制为低值的情况下也可以防止无线资源的长时间占用。 [0079] 图10示意性地示出了数据大小控制系统的示例配置 160 . 数据大小控制系统 160 包括一个尺寸缩小处理单元 161 和内容分析单元 162 . 内容分析单元 162 通过分析从提供商服务器流出的内容数据,识别内容的细节(内容类型、内容结构等) 16 进入移动终端 13 . [0080] 在通信速度受到限制的情况下,尺寸缩减处理单元 161 基于对内容细节的确定结果执行尺寸减小处理。 当网络内容包括图像或运动图像时,例如,执行降低图像或运动图像的分辨率的处理,或者执行去除图像或运动图像的数据的处理,以便 数据大小减小。 [0081] 数据大小缩减过程可能不在运营商服务器中执行 14 . 相反,可以从运营商服务器发送通信速度限制信息或数据大小减少请求 14 到提供者服务器 16 ,并且可以在提供者服务器端执行数据大小缩减处理 16 . [0082]图11(a)示出了包括图像、运动图像等的网络内容的示例。 当没有数据大小缩减请求时,提供者服务器 16 将图11(a)所示的网页内容发送到移动终端 13 , 如图 11(b) 所示。 但是,当有数据大小减少请求时,提供程序服务器 16 将网页内容减去大数据量的图像、动态图像等发送到移动终端 13 , 如图 11(c) 所示。 [0083] 需要注意的是,运行provider server的provider 16 和手机运营商可能相同,也可能不同。 在提供商和移动电话运营商不同的情况下,也可以采用在提供商服务器侧执行数据大小缩减处理的商业模式 16 如上所述,移动电话运营商可以支付奖励作为对解决网络拥塞的提供商的感谢。 [0084] 图12示出了在这种情况下要执行的示例操作。 在这种情况下,提供商(运营商 B)向移动电话运营商(运营商 A)发送有关数据大小缩减处理历史的信息。 移动电话运营商根据历史信息计算奖励金额,并将奖励支付给提供者。 在运营商服务器侧执行数据大小缩减处理的情况下 14 ,也可以支付奖励作为对提供者的感谢。 [0085] 如上所述,在移动电话系统中 10 如图1所示,通信状态信息指示与基站的通信状态 12 被移动端获取 13 ,并将此通信状态信息发送到运营商服务器 14 通过基站 12 . 基于该通信状态信息,运营商服务器 14 控制要从提供商服务器(网络服务器)传输的内容数据的通信速度 16 到移动终端 13 通过基站 12 . 因此,要从提供商服务器发送的内容数据的通信速度 16 到移动终端 13 通过基站 12 例如,可以根据通信状态信息进行设置,即使在线路质量较差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 [0086] 此外,在手机系统中 10 如图1所示,移动终端 13 或运营商服务器 14 设置与提供程序服务器连接相关的超时时间 16 或从提供商服务器下载内容数据 16 基于通信状态信息。 由此,例如,在线路质量差的环境中,超时时间被缩短,因此,防止了无线线路的不必要的长时间占用。 在通信因超时而中断后,进行重传/重连以重新获取信息。 以这种方式,在某些情况下可以更快地获取信息。 [0087] 此外,在手机系统中 10 如图1所示,运营商服务器 14 根据内容的具体情况或用户的动作改变通信速度的控制值。 因此,移动终端 13 可以从提供者服务器获取内容数据 16 例如,以与内容的细节或用户的动作的细节相对应的通信速度,并且即使在通信速度受到限制时也进行相对顺畅的通信。 [0088] 此外,在手机系统中 10 如图1所示,当控制通信速度下降到较低值时,运营商服务器 14 可以减少要传输到移动终端的内容数据的大小 13通过基站 12 . 因此,例如,可以缩短发送内容数据所需的时间,并且可以防止无线资源的长时间占用。 [0089] 此外,在手机系统中 10 如图1所示,运营商服务器 14 根据通讯状态信息,将优惠券置于开启状态(可用状态),线路质量良好时不限制通讯速度,但运营商服务器 14 当线路质量不好时,根据通信状态信息将优惠券置于关闭状态(不可用状态),并将通信速度限制在预定值。 因此,例如,当通信环境恶化时,优惠券自动进入不可用状态。 因此,可以提供用户满意的费用结构。 2. 修改 [0090] 尽管上面已经参照附图描述了本技术的实施例,但是本技术不限于这些示例。 显然,本领域的普通技术人员可以在此处要求保护的技术精神的范围内做出各种变化或修改,并且应该理解,这些变化或修改都在本技术的范围内。 例如,移动终端被描述为移动电话设备,但不一定是移动电话设备,也可以是PDA、游戏机或小型PC等便携式信息处理设备。 [0091] 本技术也可以体现在下面描述的结构中。 [0092] (一)一种移动终端设备,包括: [0093] 信息获取单元,获取指示与基站的通信状态的通信状态信息; [0094] 信息发送单元,通过基站将通信状态信息发送给运营商服务器装置; 和 [0095] 数据接收单元,其通过运营商服务器设备和基站从网络服务器接收内容数据,同时基于通信状态信息控制通信速度。 [0096] (2)根据(1)所述的移动终端装置,其中,所述通信状态信息是根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较而获得的线路质量信息 . [0097] (3)(1)或(2)所述的移动终端设备,还包括: [0098] 超时时间设置单元,其基于通信状态信息设置与连接到网络服务器或从网络服务器下载内容数据相关的超时时间。 [0099] (4)一种移动终端设备的无线通信方法,包括: [0100] 信息获取步骤,获取指示与基站的通信状态的通信状态信息; [0101] 信息传输步骤,通过基站将通信状态信息传输给运营商服务器设备; 和 [0102] 数据接收步骤,通过运营商服务器设备和基站从网络服务器接收内容数据,同时基于通信状态信息控制通信速度。 [0103] (5) 一种运营商服务器设备,包括: [0104] 信息接收单元,通过基站从移动终端设备接收通信状态信息,该通信状态信息指示与基站的通信状态; 和 [0105] 速度控制单元,基于通信状态信息控制内容数据的通信速度,内容数据通过基站从网络服务器发送到移动终端设备。 [0106](6)根据(5)所述的运营商服务器装置,其中,所述通信状态信息是根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较而获得的线路质量信息 . [0107] (7)根据(5)或(6)所述的运营商服务器设备,其中,速度控制单元将由通信状态信息指示的通信状态划分为多个等级,并且根据各个等级控制通信速度。 [0108] (8)根据(5)至(7)中任一项所述的运营商服务器设备,其中,所述速度控制单元根据内容的细节改变用于通信速度的控制值。 [0109] (9)根据(5)至(8)中任一项所述的运营商服务器装置,其中,所述速度控制单元根据所述移动终端装置的用户的动作的细节来改变所述通信速度的控制值。 [0110] (10)如(5)至(9)中任一项所述的运营商服务器设备,进一步包括 [0111] 数据大小控制单元,当速度控制单元控制通信速度变低时,减小要通过基站发送到移动终端设备的内容数据的大小。 [0112] (11)根据(5)至(10)中任一项所述的运营商服务器设备,其中,速度控制单元基于通信状态信息确定线路质量是否良好,将优惠券设置为可用状态并且不限制通信速度 当线路质量良好时,将优惠券设置为不可用状态,并在线路质量不好时将通信速度限制在预定值。 [0113] (12)一种运营商服务器设备中的通信速度控制方法,包括: [0114] 信息接收步骤,通过基站从移动终端装置接收通信状态信息,该通信状态信息指示与基站的通信状态; 和 [0115] 速度控制步骤,在内容数据通过基站从网络服务器发送到移动终端设备时控制通信速度,基于通信状态信息控制通信速度。 参考符号列表 [0116]10 手机系统[0117]11 电信运营商通信网络[0118]12 基站[0119]13 移动端[0120]14 运营商服务器[0121]15 互联网[0122]16 提供者服务器(网络服务器)[0123]101 天线[0124]102 无线接口单元[0125]103 控制单元[0126]104 用户界面单元[0127]131 信息获取单元[0128]132 信息传递单元[0129]133 数据接收单元[0130]134 超时时间设置单位[0131]141 信息接收单位[0132]142 数据传输单元[0133]143 速度控制单元[0134]144 数据大小控制单元[0135]150 , 150 一个, 150 B 速度控制系统[0136]151 转变[0137]152 传输速度测量单元[0138]153 控制单元[0139]154 速度表[0140]155 内容分析单元[0141]156 速度表[0142]157 用户动作识别单元[0143]160 数据大小控制系统[0144]161 小型化处理单元[0145]162 内容分析单元(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.444 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160373954A1(String), US9986457B2(String), WO2014208389A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.446 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.447 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: US20160373954A1(String), US9986457B2(String), WO2014208389A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.448 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9986457B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.455 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), US20160373954A1(String), US9986457B2(String), WO2014208389A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.456 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270722(Integer), US20160373954A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.468 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270722(Integer), US9986457B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.478 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270722(Integer), WO2014208389A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.490 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9986457B2(String), US9986457B2(String), 1527523200(Integer), 270722(Integer), 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.500 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.501 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY CORPORATION(String), 索尼公司(String), 索尼公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.502 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.503 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.504 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.505 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185047(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.506 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 1(Integer), 185047(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.515 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.516 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.517 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.518 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185047(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.519 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.519 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.519 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75898(Integer), 2(Integer), 185047(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.530 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.532 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.533 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75898(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.534 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.535 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.536 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.545 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.547 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.548 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.549 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185047(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.560 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.561 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.563 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method of executing control mode of radio frequency unit in mobile terminal and mobile terminal for performing the same(String), 在移动终端中执行射频单元控制模式的方法及用于执行该方法的移动终端(String), US20080125034A1(String), A method of executing a control mode of a radio frequency (RF) unit in a mobile terminal and a mobile terminal for performing the same are provided. The mobile terminal includes an RF unit to receive electric waves and a controller. The controller compares the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity and the comparison result determines whether the controller turns the RF unit off.(String), 提供了一种在移动终端中执行射频(RF)单元的控制模式的方法以及用于执行该方法的移动终端。 移动终端包括接收电波的RF单元和控制器。 控制器将RF单元中接收到的电波的强度与电波强度的参考值进行比较,比较结果确定控制器是否关闭RF单元。(String), US11/771235(String), 1183046400(Integer), US20080125034A1(String), 1211990400(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030081694A1 | US20040114737A1 | US20050185737A1 | US20070076137A1 | US20090010367A1 | US4249165A | US4369443A | US4370753A | US4437095A | US4449248A | US5301225A | US5566364A | US5799256A | US6078816A | US7356351B1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.579 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.580 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185048(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.582 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.583 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2a70a28a8851424791c73514ae214d6c.png(String), 185048(Integer), 2a70a28a8851424791c73514ae214d6c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.593 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.594 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of executing control mode of radio frequency unit in mobile terminal and mobile terminal for performing the same(String), 在移动终端中执行射频单元控制模式的方法及用于执行该方法的移动终端(String), US20080125034A1(String), A method of executing a control mode of a radio frequency (RF) unit in a mobile terminal and a mobile terminal for performing the same are provided. The mobile terminal includes an RF unit to receive electric waves and a controller. The controller compares the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity and the comparison result determines whether the controller turns the RF unit off.(String), 提供了一种在移动终端中执行射频(RF)单元的控制模式的方法以及用于执行该方法的移动终端。 移动终端包括接收电波的RF单元和控制器。 控制器将RF单元中接收到的电波的强度与电波强度的参考值进行比较,比较结果确定控制器是否关闭RF单元。(String), US11/771235(String), 1183046400(Integer), US20080125034A1(String), 1211990400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030081694A1 | US20040114737A1 | US20050185737A1 | US20070076137A1 | US20090010367A1 | US4249165A | US4369443A | US4370753A | US4437095A | US4449248A | US5301225A | US5566364A | US5799256A | US6078816A | US7356351B1(String), \20230420\2a70a28a8851424791c73514ae214d6c.png(String), 12(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.602 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.603 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.604 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 1. A mobile terminal, comprising:a radio frequency (RF) unit to receive electric waves; anda controller to compare the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity,wherein the comparison result determines whether the controller turns the RF unit off.(String), 1.移动终端,包括:用于接收电波的射频(RF)单元;和控制器将射频单元接收到的电波强度与电波强度参考值进行比较,其中,比较结果决定控制器是否关闭射频单元。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 2. The mobile terminal of claim 1, wherein the controller comprises:a numerical value comparison unit to compare the intensity of the received electric waves with the reference value of electric wave intensity; anda power controller to turn off the RF unit by not supplying power to the RF unit if the intensity of the received electric waves is less than the reference value of electric wave intensity.(String), 2.如权利要求1所述的移动终端,其中控制器包括:数值比较单元,将接收到的电波强度与电波强度参考值进行比较;和如果接收到的电波的强度小于电波强度的参考值,则功率控制器通过不向RF单元供电来关闭RF单元。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 3. The mobile terminal of claim 2, wherein the controller further comprises a numerical value conversion unit to convert the intensity of the received electric waves to a numerical value.(String), 3.如权利要求2所述的移动终端,其中控制器还包括数值转换单元,用于将接收到的电波的强度转换为数值。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 4. The mobile terminal of claim 2, wherein the controller turns on the RF unit if, after turning off the RF unit, it determines that a preset time period from a time at which the RF unit was turned off has elapsed.(String), 4.如权利要求2所述的移动终端,其中如果在关闭RF单元之后,控制器确定从RF单元被关闭的时间起经过预设时间段,则控制器打开RF单元。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 5. The mobile terminal of claim 4, wherein the controller controls the RF unit to continuously receive the electric waves by sustaining a turn-on state of the RF unit if the intensity of the received electric waves is greater than or equal to the reference value of electric wave intensity.(String), 5.如权利要求4所述的移动终端,其中当接收到的电波强度大于或等于电波强度参考值时,控制器通过维持射频单元的开启状态来控制射频单元持续接收电波。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 6. The mobile terminal of claim 1, further comprising an input unit to input a control mode of the RF unit to turn the RF unit on and off.(String), 6.如权利要求1所述的移动终端,还包括输入单元输入RF单元的控制模式以打开和关闭RF单元。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.605 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 7. The mobile terminal of claim 6, wherein the controller controls the RF unit to change to a control mode according to the input of the input unit and receive electric waves at a interval during a preset time period.(String), 7.如权利要求6所述的移动终端,其中控制器根据输入单元的输入控制射频单元改变为控制模式,并在预设时间段内每隔一段时间接收电波。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 8. A method of executing a control mode of a radio frequency (RF) unit in a mobile terminal, comprising;receiving electric waves in the RF unit;comparing the intensity of the received electric waves with a reference value of electric wave intensity; andturning off the RF unit if the intensity of the received electric waves is less than the reference value of electric wave intensity.(String), 8.一种执行移动终端中射频(RF)单元的控制模式的方法,包括;在RF单元中接收电波;将接收到的电波强度与电波强度参考值进行比较;和如果接收到的电波强度小于电波强度参考值,则关闭射频单元。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 9. The method of claim 8, further comprising determining whether a control mode of the RF unit is preset if the intensity of the received electric waves is less than the reference value of electric wave intensity.(String), 9.如权利要求8所述的方法,还包括如果接收到的电波强度小于电波强度参考值,则判断射频单元的控制模式是否预设。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 10. The method of claim 8, further comprising:determining whether a preset time period has elapsed from a time at which the RF unit is turned off;turning on the RF unit if the preset time period has elapsed; andreceiving the electric waves in the RF unit.(String), 10.如权利要求8所述的方法,还包括:判断射频单元关闭后是否经过预设时间;如果预设时间段已经过去,则打开射频单元;和在RF单元中接收电波。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 11. The method of claim 10, further comprising sustaining a turn-on state of the RF unit if the intensity of the received electric waves is greater than or equal to the reference value of electric wave intensity.(String), 11.如权利要求10所述的方法,还包括如果接收到的电波强度大于或等于电波强度参考值,则维持射频单元开启状态。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.606 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185048(Integer), 12. The method of claim 8, further comprising changing a state of receiving the electric waves at an interval during a preset time period to a state of receiving the electric waves at another interval during the preset time period if a control mode of the RF unit is selected; andreceiving the electric waves at the changed interval during the preset time period in the RF unit.(String), 12.如权利要求8所述的方法,还包括如果选择了RF单元的控制模式,则将在预设时间段内以一定间隔接收电波的状态改变为在预设时间段内以另一间隔接收电波的状态;和在RF单元中在预设时间段内以改变的间隔接收电波。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.705 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.706 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.707 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185048(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority from and the benefit of Korean Patent Application No. 10-2006-0116332, filed on Nov. 23, 2006, which is hereby incorporated by reference for all purposes as if fully set forth herein. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method of executing a control mode of a radio frequency (RF) unit in a mobile terminal and a mobile terminal for performing the same, and more particularly, to a method of executing a control mode of an RF unit for receiving electric waves to control consumption of battery power by turning the RF unit on or off according to the intensity of received electric waves, and a mobile terminal for performing the same. [0004]2. Discussion of the Background [0005]A conventional mobile terminal is activated at time slots to set a communication environment to receive electric waves from a base station. The mobile terminal transmits power according to the intensity of received electric waves. That is, the mobile terminal enables the intensity of electric waves transmitted from the mobile terminal to be weak if the intensity of the received electric waves is strong and enables the intensity of electric waves transmitted from the mobile terminal to be strong if the intensity of the received electric waves is weak, whereby reception efficiency of electric waves may improve. [0006]Because transmission power increases in a weak electric wave area, battery power of the mobile terminal may be rapidly consumed in a weak electric wave area, whereby the battery may not be effectively controlled. SUMMARY OF THE INVENTION [0007]The present invention provides a method of controlling an RF unit of a mobile terminal according to the intensity of a signal received in the mobile terminal. [0008]The present invention further provides a method of controlling an RF unit of a mobile terminal in a low electric wave area such that the efficiency of a battery of the mobile terminal may improve. [0009]Additional features of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. [0010]The present invention discloses a mobile terminal including an RF unit to receive electric waves and a controller. The controller compares the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity and the comparison result determines whether the controller turns the RF unit off. [0011]The present invention also discloses a method of executing a control mode of an RF unit in a mobile terminal, including receiving electric waves in the RF unit, comparing the intensity of the received electric waves with a reference value of electric wave intensity, and turning off the RF unit if the intensity of the received electric waves is less than the reference value of electric wave intensity. [0012]It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. [0014]FIG. 1 is a block diagram showing a configuration of a mobile terminal for executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0015]FIG. 2 is a flowchart showing a method of executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0016]FIG. 3 is a flowchart showing a method of executing a control mode of an RF unit according to another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS [0017]The invention is described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements. [0018]It will be understood that when an element or layer is referred to as being “on” or “connected to” another element or layer, it can be directly on or directly connected to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on” or “directly connected to” another element or layer, there are no intervening elements or layers present. [0019]A mobile terminal according to exemplary embodiments of the present invention includes information communication devices and multimedia devices such as a mobile communication terminal, a mobile phone, a Personal Digital Assistant (PDA), and a smart phone, and applications thereof. [0020]FIG. 1 is a block diagram showing a configuration of a mobile terminal for executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0021]Referring to FIG. 1, the mobile terminal includes an RF unit 101, an input unit 103, a controller 105, a power controller 107, a numerical value conversion unit 109, a numerical value comparison unit 111, a display unit 113, a memory unit 115, and an audio unit 117. [0022]The RF unit 101 performs wireless communication between the mobile terminal and a mobile communication network. For example, the RF unit 101 transmits and receives voice data, character messages, and multimedia messages through the mobile communication network. The RF unit 101 receives electric waves at an interval that is set by the controller 105 and provides the received electric waves to the controller 105. [0023]The input unit 103 may include a general keypad. Further, the input unit 103 may include a touch screen, a touch pad, and a scroll wheel. The input unit 103 receives a user manipulation signal to control the operation of the mobile terminal and provides the signal to the controller 105. [0024]The controller 105 controls the general operation of units in the mobile terminal. The controller 105 includes a modem and a codec having a transmitter to encode and modulate a signal to be transmitted by the RF unit 101 and a receiver to demodulate and decode the received signal. [0025]Particularly, the controller 105 controls the RF unit 101 to enter a control mode, compares the intensity of electric waves received in the RF unit 101 with a reference value of electric wave intensity, and turns the RF unit 101 on or off according to the compared result. For this, the controller 105 includes a power controller 107, a numerical value conversion unit 109, and a numerical value comparison unit 111. Further, the controller 105 terminates and sustains a control mode of the RF unit 101 in response to an input signal provided by the input unit 103. [0026]The power controller 107 may turn the RF unit 101 off by not supplying power to the RF unit 101 or turn the RF unit 101 on by supplying power to the RF unit 101. [0027]The numerical value conversion unit 109 converts the intensity of electric waves received in the RF unit 101 to a numerical value and provides the numerical value to the numerical value comparison unit 111. [0028]The numerical value comparison unit 111 compares the numerical value, which corresponds to the intensity of received electric waves, with a reference value of electric wave intensity and provides the compared result to the power controller 107. [0029]The display unit 113 displays information relating to the operation state, the operation result, and other information performed in units of the mobile terminal by the f the controller 105. The display unit 113 may include a display device such as a liquid crystal display (LCD), organic light emitting diodes (OLED), or a plasma display panel (PDP). [0030]The controller 105 controls the memory unit 115 to store information (for example, information about a setting state and a menu) related to the operation of the mobile terminal. [0031]The memory unit 115 stores the intensity of received electric waves as a reference value to be referred to when changing to a control mode to turn the RF unit 101 on or off. The memory unit 115 also stores a preset time period and an interval at which electric waves are to be received from a base station in a control mode of the RF unit 101. [0032]The memory unit 115 stores the preset time period as a reference period during which the RF unit 101 is turned on and stores a power saving numerical value of a function, including light brightness and light time, in a power saving mode of the mobile terminal. [0033]The audio unit 117 converts an analog audio signal that is input through a microphone MIC to a digital signal and converts a digital audio signal output from the controller 105 into an analog audio signal and reproduces the signal through a speaker SPK. [0034]FIG. 2 is a flowchart showing a method of executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0035]Referring to FIG. 2, a control mode of the RF unit 101 is selected by a user (S201), and the mobile terminal enters a power saving mode (S203). The control mode of the RF unit 101 is a mode that is set to reduce battery power consumption when the mobile terminal moves to a weak electric wave area. The power saving mode is a mode that is set to convert a function such as light brightness and/or light time of the mobile terminal to a preset power saving numerical value. [0036]The controller 105 controls the RF unit 101 to receive electric waves at an interval during the preset time period (S205). [0037]Specifically, the controller 105 controls the RF unit 101 to receive electric waves at intervals before entering the control mode of the RF unit 101, and the intervals may be time slots. In the case of time slots, the mobile terminal receives electric waves from a base station at time slots, each of which corresponds to an intrinsic slot cycle index allocated by the base station according to system settings. Thereafter, the controller 105 controls the RF unit 101 to enter the control mode and receive electric waves at the intervals during the preset time period. [0038]For example, if the preset time period is 3 minutes and the interval is 20 seconds, the controller 105 controls the RF unit 101 to receive electric waves 9 times at intervals of 20 seconds over a 3 minute period. The interval may be a receiving interval (for example, every 20 seconds), the receiving number of times (for example, 9 times), or a time slot. [0039]The controller 105 controls the numerical value conversion unit 109 to measure the intensity of the received electric waves and convert the intensity of the received electric waves to a numerical value, and provides the converted numerical value to the numerical value comparison unit 111 (S207). [0040]The controller 105 controls the numerical value comparison unit 111 to determine whether the intensity of the received electric waves is greater than or equal to a reference value of electric wave intensity (S209). If the intensity of the received electric waves is greater than or equal to the reference value of electric wave intensity, the controller 105 determines whether a request to sustain the control mode of the RF unit 101 has been received (S211). If a request to sustain the control mode of the RF unit 101 is received, the controller 105 sustains the control mode of the RF unit 101 (S213) and continues to receive electric waves. The controller 105 repeats the process by returning to step S205 while sustaining a control mode of the RF unit 101 at step S213. [0041]If a request to sustain the control mode of the RF unit 101 is not received at step S211, the controller 105 terminates the control mode of the RF unit 101 (S215) and the process returns to step S205. [0042]In another exemplary embodiment, if the intensity of the received electric waves is greater than or equal to a reference value of electric wave intensity at step S209, steps S211 and S215 may be omitted, and the process may continue at step S213. [0043]If the intensity of the received electric waves is less than the reference value of electric wave intensity at step S209, the controller 105 turns the RF unit 101 off (S217). When a preset time period has elapsed (219), the controller 105 turns the RF unit 101 on (S221). [0044]The controller 105 determines whether a request to terminate the control mode of the RF unit 101 has been received (S223). If a request to terminate the control mode of the RF unit 101 is not received, the process returns to step S205 and the RF unit 101 continues to receive the electric waves controlled by the controller 105. If a request to terminate the control mode of the RF unit 101 is received, the controller 105 terminates the control mode of the RF unit 101 (S225). [0045]For example, if the preset time period is set to 1 hour, the controller 105 turns the RF unit 101 on after 1 hour has elapsed from the time at which the RF unit 101 was turned off and receives electric waves. A turn-off state of the RF unit 101 is a state in which power is blocked from being supplied to the RF unit 101, and a turn-on state of the RF unit 101 is a state in which power is supplied to the RF unit 101 and thus, electric waves are continuously received. [0046]FIG. 3 is a flowchart showing a method of executing a control mode of an RF unit according to another exemplary embodiment of the present invention. [0047]Referring to FIG. 3, the controller 105 controls the RF unit 101 to receive electric waves at intervals (S301). The intervals may be time slots. For example, the mobile terminal may receive electric waves from a base station at time slots, each of which corresponds to an intrinsic slot cycle index allocated by the base station according to system settings. [0048]The controller 105 controls the numerical value conversion unit 109 to measure the intensity of the received electric waves and convert the intensity of the received electric waves to a numerical value (S303). The controller 105 then provides the numerical value to the numerical value comparison unit 111. [0049]The controller 105 controls the numerical value comparison unit 111 to determine whether the numerical value, which corresponds to the intensity of the received electric waves, is greater than or equal to a reference value of electric wave intensity (S305). If the numerical value is greater than or equal to the reference value of electric wave intensity, the controller 105 sustains a control mode of the RF unit 101 (S307), continues to receive the electric waves, and repeats the process by returning to step S301. [0050]If the numerical value is less than the reference value at step S305, the controller 105 determines whether a control mode of the RF unit 101 is set (S309). If a control mode of the RF unit 101 is not set, the process continues at step S307. [0051]If a control mode of the RF unit 101 is set, the controller 105 turns the RF unit 101 off (S311). When the controller 105 determines that a preset time period has elapsed after the RF unit 101 was turned off (S313), the controller 105 turns on the RF unit 101 (S315) and repeats the process by returning to step S301. [0052]As described above, according to exemplary embodiments of the present invention, by controlling the RF unit of the mobile terminal according to the intensity of a received signal, a battery may be effectively managed. [0053]Further, by turning the RF unit off in a weak electric wave area, battery power consumption used to receive electric waves may be reduced. [0054]Further, by turning only the RF unit off in the mobile terminal, another function of the mobile terminal may be used without restriction even when the RF unit of the mobile terminal is turned off. [0055]It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.(String), 相关申请的交叉引用 [0001] 本申请要求于 2006 年 11 月 23 日提交的韩国专利申请第 10-2006-0116332 号的优先权和权益,为了所有目的,该申请通过引用并入本文,就好像在本文中完整阐述一样。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明涉及一种在移动终端中执行射频(RF)单元的控制模式的方法以及用于执行该方法的移动终端,更具体地,涉及一种在移动终端中执行射频(RF)单元的控制模式的方法。 接收电波以通过根据接收到的电波的强度打开或关闭RF单元来控制电池电力的消耗,以及用于执行相同操作的移动终端。 [0004] 2. 背景讨论 [0005] 传统的移动终端在时隙被激活以设置通信环境以接收来自基站的电波。 移动终端根据接收到的电波的强度发射功率。 也就是说,如果接收到的电波的强度强,则移动终端使从移动终端发射的电波的强度弱,如果接收到的电波的强度强,则使从移动终端发射的电波的强度强。 接收的电波较弱,由此可以提高电波的接收效率。 [0006] 由于在电波较弱的区域发射功率增加,移动终端的电池电量在电波较弱的区域会快速消耗,从而无法有效控制电池。 发明内容 [0007] 本发明提供一种根据在移动终端中接收到的信号的强度来控制移动终端的RF单元的方法。 [0008] 本发明还提供了一种在低电波区域控制移动终端的RF单元的方法,从而可以提高移动终端的电池效率。 [0009] 本发明的附加特征将在以下描述中阐述,并且部分将从描述中显而易见,或者可以通过本发明的实践来了解。 [0010] 本发明公开了一种移动终端,包括用于接收电波的RF单元和控制器。 控制器将RF单元中接收到的电波的强度与电波强度的参考值进行比较,比较结果确定控制器是否关闭RF单元。 [0011] 本发明还公开了一种在移动终端中执行RF单元的控制模式的方法,包括在RF单元中接收电波,将接收到的电波的强度与电波强度的参考值进行比较,以及关闭 如果接收到的电波的强度小于电波强度的参考值,则 RF 单元。 [0012] 应当理解,前面的一般描述和下面的详细描述都是示例性和解释性的,并且旨在提供对所要求保护的本发明的进一步解释。 附图的简要说明 [0013] 附图被包括在内以提供对本发明的进一步理解并且被并入并构成本说明书的一部分,它们说明了本发明的实施例,并且与描述一起用于解释本发明的原理。 [0014] 图1是示出根据本发明示例性实施例的用于执行RF单元的控制模式的移动终端的配置的框图。 [0015] 图2是示出根据本发明示例性实施例的执行RF单元的控制模式的方法的流程图。 [0016] 图3是示出根据本发明另一示例性实施例的执行RF单元的控制模式的方法的流程图。 图示实施例的详细说明 [0017]下文参照附图更全面地描述本发明,其中示出了本发明的实施例。 然而,本发明可以以许多不同的形式来实施并且不应被解释为限于本文所阐述的实施例。 相反,提供这些实施例是为了使本公开是彻底的,并且将向本领域技术人员充分传达本发明的范围。 在附图中,为了清楚起见,可能夸大了层和区域的尺寸和相对尺寸。 图中相同的附图标记表示相同的元件。 [0018] 应当理解,当一个元件或层被称为“在”或“连接到”另一个元件或层时,它可以直接在另一个元件或层上或直接连接到另一个元件或层,或者中间的元件或层可以是 当下。 相反,当一个元素被称为“直接在”或“直接连接到”另一个元素或层时,不存在中间的元素或层。 [0019] 根据本发明示例性实施例的移动终端包括信息通信设备和多媒体设备,例如移动通信终端、移动电话、个人数字助理(PDA)和智能电话,及其应用。 [0020] 图1是示出根据本发明示例性实施例的用于执行RF单元的控制模式的移动终端的配置的框图。 [0021] 参考图1,移动终端包括RF单元 101 , 一个输入单元 103 , 一个控制器 105 , 电源控制器 107 , 一个数值转换单元 109 , 数值比较单元 111 , 一个显示单元 113 , 一个记忆单元 115 , 和一个音频单元 117 . [0022] 射频单元 101 执行移动终端和移动通信网络之间的无线通信。 例如,射频单元 101 通过移动通信网络发送和接收语音数据、字符消息和多媒体消息。 射频单元 101 以控制器设定的间隔接收电波 105 并将接收到的电波提供给控制器 105 . [0023] 输入单元 103 可能包括一个通用键盘。 此外,输入单元 103 可以包括触摸屏、触摸板和滚轮。 输入单元 103 接收用户操作信号以控制移动终端的操作并将信号提供给控制器 105 . [0024] 控制器 105 控制移动终端中单元的一般操作。 控制器 105 包括调制解调器和编解码器,该编解码器具有发射器以编码和调制要由RF单元发射的信号 101 接收器对接收到的信号进行解调和解码。 [0025] 特别是控制器 105 控制射频单元 101 进入控制模式,比较射频单元接收到的电波强度 101 具有电波强度的参考值,并转动射频单元 101 根据比较结果打开或关闭。 为此,控制器 105 包括一个电源控制器 107 , 一个数值转换单元 109 , 和一个数值比较单元 111 . 此外,控制器 105 终止并维持射频单元的控制模式 101 响应输入单元提供的输入信号 103 . [0026] 电源控制器 107 可以转动射频单元 101 通过不向 RF 单元供电来关闭 101 或转动射频单元 101 通过向 RF 单元供电来开启 101 . [0027] 数值转换单位 109 转换 RF 单元中接收到的电波强度 101 到数值并将数值提供给数值比较单元 111 . [0028] 数值比较单元 111将对应于接收电波强度的数值与电波强度的参考值进行比较,并将比较结果提供给功率控制器 107 . [0029] 显示单元 113 显示与操作状态、操作结果相关的信息,以及由控制器以移动终端为单位执行的其他信息 105 . 显示单元 113 可以包括诸如液晶显示器(LCD)、有机发光二极管(OLED)或等离子显示面板(PDP)的显示装置。 [0030] 控制器 105 控制内存单​​元 115 存储与移动终端的操作相关的信息(例如,关于设置状态和菜单的信息)。 [0031] 记忆单元 115 将接收到的电波强度存储为在切换到控制模式以转动 RF 单元时要参考的参考值 101 打开或关闭。 记忆单元 115 还存储在RF单元的控制模式下要从基站接收电波的预设时间段和间隔 101 . [0032] 记忆单元 115 存储预设时间段作为参考时间段,在此期间RF单元 101 开启并存储移动终端省电模式下功能的省电数值,包括灯光亮度和点亮时间。 [0033] 音频单元 117 将通过麦克风 MIC 输入的模拟音频信号转换为数字信号,并转换从控制器输出的数字音频信号 105 转换成模拟音频信号并通过扬声器 SPK 再现信号。 [0034] 图2是示出根据本发明示例性实施例的执行RF单元的控制模式的方法的流程图。 [0035] 参见图2,射频单元的控制方式 101 由用户选择(S 201 ),移动终端进入省电模式(S 203 )。 射频单元的控制方式 101 是移动终端移动到电波较弱的区域时为降低电池耗电量而设置的模式。 省电模式是设置为将移动终端的光照亮度和/或光照时间等功能转换为预设的省电数值的模式。 [0036] 控制器 105 控制射频单元 101 在预设时间段内以一定间隔接收电波(S 205 )。 [0037] 具体来说,控制器 105 控制射频单元 101 在进入射频单元的控制模式之前每隔一段时间接收电波 101 , 间隔可以是时隙。 在时隙的情况下,移动终端在时隙从基站接收电波,每个时隙对应于基站根据系统设置分配的固有时隙周期索引。 此后,控制器 105 控制射频单元 101 进入控制模式,在预设时间间隔内接收电波。 [0038] 例如,如果预设时间段为 3 分钟,间隔时间为 20 秒,则控制器 105 控制射频单元 101 在 3 分钟内以 20 秒的间隔接收 9 次电波。 该间隔可以是接收间隔(例如每20秒)、接收次数(例如9次)或时隙。 [0039] 控制器 105 控制数值转换单元 109 测量接收电波的强度并将接收电波的强度转换为数值,并将转换后的数值提供给数值比较单元 111 (S 207 )。 [0040] 控制器 105 控制数值比较单元 111 判断接收到的电波强度是否大于或等于电波强度参考值(S 209)。 如果接收到的电波强度大于或等于电波强度参考值,控制器 105 判断请求是否维持射频单元的控制模式 101 已收到(S 211 )。 如果请求维持射频单元的控制模式 101 收到,控制器 105 维持射频单元的控制模式 101 (S 213 ) 并继续接收电波。 控制器 105 通过返回步骤 S 重复该过程 205 同时维持射频单元的控制模式 101 在步骤 S 213 . [0041] 如果请求维持射频单元的控制模式 101 在步骤 S 未收到 211 , 控制器 105 终止射频单元的控制模式 101 (S 215 ) 并且过程返回到步骤 S 205 . [0042] 在另一示例性实施例中,如果在步骤S接收到的电波的强度大于或等于电波强度的参考值 209 , 步骤 S 211 和 S 215 可以省略,该过程可以在步骤S继续 213 . [0043] 如果在步骤S接收电波的强度小于电波强度的参考值 209 , 控制器 105 转动射频单元 101 关(S 217 )。 当预设时间段已过时( 219 ), 控制器 105 转动射频单元 101 上(S 221 )。 [0044] 控制器 105 判断是否请求终止射频单元的控制模式 101 已收到(S 223 )。 如果请求终止 RF 单元的控制模式 101 没有收到,返回步骤S 205 和射频单元 101 继续接收控制器控制的电波 105 . 如果请求终止 RF 单元的控制模式 101 收到,控制器 105 终止射频单元的控制模式 101 (S 225 )。 [0045] 例如,如果预设时间段设置为 1 小时,则控制器 105 转动射频单元 101 从 RF 单元开始经过 1 小时后亮起 101 被关闭并接收电波。 RF单元的关闭状态 101 是阻止向 RF 单元供电的状态 101 ,以及射频单元的开启状态 101 是向 RF 单元供电的状态 101 因此,电波被连续接收。 [0046] 图3是示出根据本发明另一示例性实施例的执行RF单元的控制模式的方法的流程图。 [0047] 参照图3,控制器 105 控制射频单元 101 每隔一段时间接收电波(S 301 )。 间隔可以是时隙。 例如,移动终端可以在时隙从基站接收电波,每个时隙对应于基站根据系统设置分配的固有时隙周期索引。 [0048] 控制器 105 控制数值转换单元 109 测量接收到的电波的强度并将接收到的电波的强度转换为数值(S 303 )。 控制器 105 然后将数值提供给数值比较单元 111 . [0049] 控制器 105 控制数值比较单元 111 判断接收到的电波强度对应的数值是否大于或等于电波强度的参考值(S 305 )。 如果数值大于或等于电波强度参考值,控制器 105 维持射频单元的控制模式 101 (S 307 ),继续接收电波,并返回步骤S重复该过程 301 . [0050] 如果数值小于步骤 S 的参考值305 , 控制器 105 判断射频单元的控制模式是否 101 设置(S 309 )。 如果射频单元的控制模式 101 未设置,该过程在步骤 S 继续 307 . [0051] 如果射频单元的控制模式 101 设置,控制器 105 转动射频单元 101 关(S 311 )。 当控制器 105 确定在 RF 单元之后经过了预设时间段 101 被关闭(S 313 ), 控制器 105 打开射频单元 101 (S 315 ) 并通过返回步骤 S 重复该过程 301 . [0052] 如上所述,根据本发明的示例性实施例,通过根据接收信号的强度控制移动终端的RF单元,可以有效地管理电池。 [0053] 此外,通过在电波较弱的区域关闭RF单元,可以减少用于接收电波的电池功耗。 [0054] 此外,通过仅关闭移动终端中的RF单元,即使当移动终端的RF单元被关闭时,也可以不受限制地使用移动终端的另一功能。 [0055] 对于本领域的技术人员来说,在不脱离本发明的精神或范围的情况下,可以对本发明进行各种修改和变化是显而易见的。 因此,本发明旨在覆盖本发明的修改和变化,只要它们落入所附权利要求及其等同物的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.719 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.720 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.720 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100782510B1(String), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.721 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.722 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100782510B1(String), US20080125034A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.723 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.733 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100782510B1(String), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.734 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270723(Integer), KR100782510B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.745 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270723(Integer), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.752 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.753 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20080125034A1(String), US20080125034A1(String), 1211990400(Integer), 270723(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.763 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.765 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.766 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.767 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185048(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.768 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 1(Integer), 185048(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.777 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.778 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1681974671(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.779 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.780 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185048(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.781 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75900(Integer), 2(Integer), 185048(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.788 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.789 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.790 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.791 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.792 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.793 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.794 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 249(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.803 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.804 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.805 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.806 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.807 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.813 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.821 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Parameters: 1837(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.823 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Preparing: UPDATE os_task SET type=?, uid=?, ctime=?, tid=?, mfields=?, mun=?, endtime=?, status=?, filename=?, filesize=?, downexcel=?, old_name=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.825 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Parameters: 1(Integer), 1(Integer), 1681975531(Integer), 249(Integer), 0(Integer), 99(Integer), 1681975570(Integer), 2(Integer), e7f4b27fca7e420d940b1f8bfe612406.XLSX(String), 6093542(Long), \20230420\e7f4b27fca7e420d940b1f8bfe612406.XLSX(String), 手机-美国.XLSX(String), 1837(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:10.834 DEBUG 14812 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:22.950 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:22.951 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:22.953 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.005 DEBUG 14812 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.005 DEBUG 14812 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 1(Integer), 1(Integer), 0(Integer), 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.006 DEBUG 14812 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.016 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.017 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.017 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.018 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.018 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 249(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.019 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.312 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.312 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.313 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.313 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.313 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:23.314 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.413 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.413 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: QUERY_GROUP(String), ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.415 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 50 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.427 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.428 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.432 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.432 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 37(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.433 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.433 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.433 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 37(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.434 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.435 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.435 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.436 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.436 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.437 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.437 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.438 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.438 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 38(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.439 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.439 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.439 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 38(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.440 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.442 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.443 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 39(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.443 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.444 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.444 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 39(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.445 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.445 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.446 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.447 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.447 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.447 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.448 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.448 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.735 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.735 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.736 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.777 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a WHERE a.id in (select tid from os_distribution_doing where uid=? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.778 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.780 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.802 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.802 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.803 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.805 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.805 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:29.806 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.154 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_thematic a WHERE (a.id IN (SELECT tid FROM os_distribution_doing WHERE uid = ?) OR a.creat_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.154 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Parameters: 1(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.155 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.155 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id,a.product_id,a.structure_id,a.is_category, u.`name` as create_name, (select count(*) from os_thematic_file where zid = a.id and type = 1) as report_num from os_thematic a left join os_distribution u on u.id = a.creat_id WHERE (a.id in (select tid from os_distribution_doing where uid=? ) or a.creat_id = ? ) order by a.`create_time` desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.155 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Parameters: 1(Integer), 1(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.157 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.169 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.170 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:30.172 DEBUG 14812 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.559 DEBUG 14812 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.560 DEBUG 14812 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.561 DEBUG 14812 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.651 DEBUG 14812 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.651 DEBUG 14812 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.652 DEBUG 14812 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.655 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.655 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.656 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.657 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.658 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.658 DEBUG 14812 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.786 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.787 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 249(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:31.788 DEBUG 14812 [http-nio-8877-exec-8] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.097 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.097 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.098 DEBUG 14812 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.136 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.136 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.138 DEBUG 14812 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.309 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.310 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.312 DEBUG 14812 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 108 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.336 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.336 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.343 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.344 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.344 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 249(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.350 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.351 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.351 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184865(Integer), 184866(Integer), 184867(Integer), 184868(Integer), 184869(Integer), 184870(Integer), 184871(Integer), 184872(Integer), 184873(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.352 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.353 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.353 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75876(Integer), 75877(Integer), 75878(Integer), 75879(Integer), 75880(Integer), 75881(Integer), 75882(Integer), 75883(Integer), 75884(Integer), 75885(Integer), 75886(Integer), 75887(Integer), 75888(Integer), 75889(Integer), 75890(Integer), 75891(Integer), 75892(Integer), 75893(Integer), 75894(Integer), 75895(Integer), 75896(Integer), 75897(Integer), 75898(Integer), 75899(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.355 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.362 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.362 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 184865(Integer), 184866(Integer), 184867(Integer), 184868(Integer), 184869(Integer), 184870(Integer), 184871(Integer), 184872(Integer), 184873(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.364 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.370 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.371 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 184865(Integer), 184866(Integer), 184867(Integer), 184868(Integer), 184869(Integer), 184870(Integer), 184871(Integer), 184872(Integer), 184873(Integer), 184950(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.372 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.373 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.373 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 184865(Integer), 184866(Integer), 184867(Integer), 184868(Integer), 184869(Integer), 184870(Integer), 184871(Integer), 184872(Integer), 184873(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.374 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.385 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.385 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 184865(Integer), 184866(Integer), 184867(Integer), 184868(Integer), 184869(Integer), 184870(Integer), 184871(Integer), 184872(Integer), 184873(Integer), 184950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.387 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.394 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.395 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 270583(Integer), 270584(Integer), 270585(Integer), 270586(Integer), 270587(Integer), 270588(Integer), 270589(Integer), 270590(Integer), 270591(Integer), 270633(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.396 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 30 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.396 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.397 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: null, null, null, null, null, null, null, null, null, null [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.398 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.398 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.399 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: null, null, null, null, null, null, null, null, null, null [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.400 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.400 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.400 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.401 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.402 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.402 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 184865(Integer), 184866(Integer), 184867(Integer), 184868(Integer), 184869(Integer), 184870(Integer), 184871(Integer), 184872(Integer), 184873(Integer), 184950(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:32.404 DEBUG 14812 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.654 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.655 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.657 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.659 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ?,? [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.659 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 249(Integer), 100(Long), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.663 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.664 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.664 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185041(Integer), 185042(Integer), 185043(Integer), 185044(Integer), 185045(Integer), 185046(Integer), 185047(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.665 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.666 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.666 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75922(Integer), 75898(Integer), 75959(Integer), 75924(Integer), 75908(Integer), 75903(Integer), 75960(Integer), 75961(Integer), 75900(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.667 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.668 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.668 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 185041(Integer), 185042(Integer), 185043(Integer), 185044(Integer), 185045(Integer), 185046(Integer), 185047(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.669 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.669 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.669 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 185041(Integer), 185042(Integer), 185043(Integer), 185044(Integer), 185045(Integer), 185046(Integer), 185047(Integer), 185048(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.670 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.670 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.670 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 185041(Integer), 185042(Integer), 185043(Integer), 185044(Integer), 185045(Integer), 185046(Integer), 185047(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.671 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.672 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.672 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 185041(Integer), 185042(Integer), 185043(Integer), 185044(Integer), 185045(Integer), 185046(Integer), 185047(Integer), 185048(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.672 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.673 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.673 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 270716(Integer), 270717(Integer), 270718(Integer), 270719(Integer), 270720(Integer), 270721(Integer), 270722(Integer), 270723(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.674 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 72 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.675 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.675 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: null, null, null, null, null, null, null, null [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.676 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.677 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.677 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: null, null, null, null, null, null, null, null [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.678 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.678 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.678 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.679 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.680 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.680 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 185041(Integer), 185042(Integer), 185043(Integer), 185044(Integer), 185045(Integer), 185046(Integer), 185047(Integer), 185048(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:26:34.681 DEBUG 14812 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:44.440 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:44.458 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:44.526 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.013 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.014 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.035 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.036 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.054 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.054 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.055 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.074 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.074 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.074 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.094 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.094 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.116 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.116 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.118 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.119 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.137 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.137 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.138 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.157 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.158 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.158 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.177 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.177 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.178 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.197 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.198 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.198 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.217 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.218 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.237 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.237 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.238 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.238 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.257 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.257 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.258 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.277 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.277 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.328 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.329 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: QUERY_GROUP(String), ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.350 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 50 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.624 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.625 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.643 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.892 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.892 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.911 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.915 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id,a.product_id,a.structure_id,a.is_category, u.`name` as create_name, (select count(*) from os_thematic_file where zid = a.id and type = 1) as report_num from os_thematic a left join os_distribution u on u.id = a.creat_id order by a.`create_time` desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.915 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Parameters: 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:45.936 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.015 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.016 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.035 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.035 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.036 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.059 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.144 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.145 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.165 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.169 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.169 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:46.189 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.028 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.029 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.064 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.197 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.198 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.215 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.224 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.225 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:49.242 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.504 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.505 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.522 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.526 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.526 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.531 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.532 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 103(Integer), 1(Integer), 0(Integer), 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.544 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.544 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.545 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 226(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.551 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.553 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.553 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.563 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:32:53.572 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:03.476 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:03.477 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById ==> Parameters: 226(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:03.498 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:03.526 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Preparing: SELECT id,uid AS userId,tenantId,tid AS projectId,addtime AS createTime,remark,type FROM os_distribution_doing WHERE (tid = ? AND uid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:03.526 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList ==> Parameters: 226(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:03.546 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectUserMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:04.276 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert ==> Preparing: INSERT INTO os_task ( type, uid, ctime, tid, mfields, mun, status, filename, filesize, downexcel, old_name ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:04.276 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert ==> Parameters: 1(Integer), 103(Integer), 1681975984(Integer), 226(Integer), 0(Integer), 99(Integer), 0(Integer), 39cf12ffed8b43b1b325f88d7b1ecb49.XLSX(String), 6093542(Long), \20230420\39cf12ffed8b43b1b325f88d7b1ecb49.XLSX(String), 手机-美国.XLSX(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:04.317 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.TaskMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:04.688 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:04.688 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 103(Integer), 1(Integer), 0(Integer), 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:04.709 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:06.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:06.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184925(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d76d7af4f80547f699bd91b7ea54b7d7.png(String), 184925(Integer), d76d7af4f80547f699bd91b7ea54b7d7.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.257 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal system, mobile terminal, external device, and input/output method of mobile terminal(String), 移动终端系统、移动终端、外部设备以及移动终端的输入/输出方法(String), US20100093394A1(String), A mobile terminal system including a mobile terminal and an external device is provided. The mobile terminal includes a first external device interface to output screen information to the external device and to receive operation information from the external device. The external device includes a display section to display and output the screen information, a user input section used when a user inputs the operation information on the mobile terminal, and a second external device interface to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 提供了一种移动终端系统,包括移动终端和外部设备。 移动终端包括第一外部设备接口以将屏幕信息输出到外部设备并从外部设备接收操作信息。 外部设备包括用于显示和输出屏幕信息的显示部分、当用户在移动终端上输入操作信息时使用的用户输入部分、以及用于从移动终端接收屏幕信息并输出的第二外部设备接口。 向移动终端发送通过用户输入部分输入的操作信息。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), US12/578279(String), 1255363200(Integer), US20100093394A1(String), 1271260800(Integer), 美国(String), 2(Integer), 2(Integer), JP(String), 3(Integer), 15(Integer), US20010052798A1 | US20030034898A1 | US20040051499A1 | US20060077046A1 | US20060082818A1 | US20060220878A1 | US20070030881A1 | US20080179963A1 | US20080239408A1 | US20090086105A1 | US20110136541A1 | US5847447A | US6781635B1 | US7976394B2 | US8004615B2(String), \20230420\d76d7af4f80547f699bd91b7ea54b7d7.png(String), 15(Integer), 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.374 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 1. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 1.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 2. A mobile terminal system including a mobile terminal and an external device, comprising:a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device;a display section which is provided in the external device in order to display and output the screen information;a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; anda second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 2.移动端系统包含一种移动终端及外部设备,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息,并接收来自外部设备的操作信息;显示部分,设置在外部设备中以显示和输出屏幕信息;用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用;和第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 0(Integer), 1(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 3. The mobile terminal system according to claim 2,wherein the coil provided in the first external device interface is a coil for power reception,the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coils.(String), 3.根据权利要求2所述的移动终端系统,其中第一外部设备接口中设置的线圈为受电线圈,第二外部设备接口中设置的线圈为电力传输线圈,以及利用线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 4. The mobile terminal system according to claim 1 or 2,wherein the mobile terminal is a mobile phone, andthe screen information is video data or still image data received through a mobile phone network.(String), 4.根据权利要求1或2所述的移动终端系统,其中移动终端为手机,屏幕信息是通过手机网络接收到的视频数据或静止图像数据。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 5. The mobile terminal system according to claim 1 or 3,wherein the first and second external device interfaces perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and also reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 5.根据权利要求1或3所述的移动终端系统,其中第一和第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 6. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 6.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 7. A mobile terminal that operates in the mobile terminal system according to claim 1, comprising:a display section which outputs screen information;a user input section which is used when a user inputs operation information on the mobile terminal;a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; anda processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface.(String), 7.一种移动终端,运行在如权利要求1所述的移动终端系统中,包括:输出屏幕信息的显示部分;当用户在移动终端上输入操作信息时使用的用户输入部分;第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息;和处理器,将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 8. The mobile terminal according to claim 7,wherein the coil provided in the first external device interface is a coil for power reception, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the first external device interface and a coil for power transmission provided in the second external device interface.(String), 8.根据权利要求7所述的移动终端,其中第一外部设备接口中设置的线圈为受电线圈,利用第一外部设备接口中设置的线圈与第二外部设备接口中设置的电力传输线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 9. The mobile terminal according to claim 6 or 8,wherein the first external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 9.根据权利要求6或8所述的移动终端,其中第一外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 10. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; anda display section which outputs the screen information received from the mobile terminal.(String), 10.一种在如权利要求1所述的移动终端系统中运行的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 11. An external device that operates in the mobile terminal system according to claim 1, comprising:a user input section which is used when a user inputs operation information on the mobile terminal;a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; anda display section which outputs the screen information received from the mobile terminal.(String), 11.一种运行在如权利要求1所述的移动终端系统中的外部设备,包括:当用户在移动终端上输入操作信息时使用的用户输入部分;第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息;和显示部分,输出从移动终端接收的屏幕信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 12. The external device according to claim 11,wherein the coil provided in the second external device interface is a coil for power transmission, anda battery in the mobile terminal is charged by using electromagnetic induction between the coil provided in the second external device interface and a coil for power reception provided in the first external device interface.(String), 12.根据权利要求11所述的外部设备,其中第二外部设备接口中设置的线圈为电力传输线圈,以及利用设置在第二外部设备接口中的线圈与设置在第一外部设备接口中的用于受电的线圈之间的电磁感应对移动终端中的电池进行充电。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 13. The external device according to claim 10 or 12,wherein the second external device interface performs parallel-to-serial conversion of transmission data and superimposes the converted data on the power signal and also reproduces received data superimposed on the power signal by performing serial-to-parallel conversion of the received data.(String), 13.根据权利要求10或12所述的外部设备,其中第二外部设备接口执行传输数据的并行到串行转换并将转换后的数据叠加到电源信号上,并且还通过执行接收到的数据的串行到并行转换来再现叠加到电源信号上的接收到的数据。(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 14. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal.(String), 14.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184925(Integer), 15. An input/output method of a mobile terminal in the mobile terminal system according to claim 1, comprising the steps of:outputting the screen information from the first external device interface provided in the mobile terminal;performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device;outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; andoperating the mobile terminal according to the operation information input to the first external device interface,wherein each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils.(String), 15.根据权利要求1所述的移动终端系统中移动终端的输入输出方法,包括步骤:从移动终端提供的第一外部设备接口输出屏幕信息;在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息;和根据输入到第一外接设备界面的操作信息操作移动终端,其中,第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。(String), 1(Integer), 14(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111496(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184925(Integer), BACKGROUND OF THE INVENTION [0001]1. Field of the Invention [0002]The present invention relates to a mobile terminal system including a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal, a mobile terminal, an external device, and an input/output method of the mobile terminal. In particular, the present invention relates to a mobile terminal system which outputs image data and sound data received in a mobile terminal to the outside through an external device and which allows the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0003]2. Description of the Related Art [0004]Mobile phones have succeeded the carphones pioneered as a mobile communications system, and have rapidly spread since the 1990s as the terminals become small, light, and inexpensive and the service charges become low. Moreover, with the spread of computers and the development of broadband network techniques including the Internet, E-mail and web search/access can be performed on mobile phones and various applications, such as music or video reproduction and games, can be executed. [0005]However, although the range of application of mobile phones is diversified, there are many restrictions in input and output since a portable size is necessary for mobile phones. For example, the screen size is diagonally about 5 to 10 cm. In this case, high-resolution display causes problems in visibility, for example, characters with the same font size become very small, even though the resolution is increasing due to the development of flat panel manufacturing technology in recent years. [0006]Furthermore, an input section provided in the mobile phone generally has only a numeric keypad of 0 to 9, keys by which up and down and left and right input operations are possible, and some other keys. Compared with a keyboard of a personal computer provided with 60 to 100 keys, the number of keys of the mobile phone is small and the input operation is also difficult. [0007]In recent years, the mobile phone with tens of keys similar to the QWERTY type keyboard has also appeared. However, each of the keys is small due to the portability restriction on the device size. For this reason, the input operation is still difficult. [0008]In order to cope with such a problem, a method of connecting a mobile phone to an external device with a relatively large screen or an input device which is easy to perform an input operation may be considered. [0009]For example, a display processing system using a mobile terminal is proposed. In the display processing system, an image displayed on a liquid crystal screen of a mobile phone can be displayed on a television screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2001-352373). [0010]In addition, a screen display device which has an entry for connecting a mobile phone is proposed. The screen display device displays image data received in the mobile phone on a large screen (for example, refer to Japanese Unexamined Patent Application Publication No. 2002-116843). [0011]In addition, a mobile phone with a separate monitor is proposed. The mobile phone displays data displayed on a monitor built in the mobile phone or downloaded display data on the separate monitor (for example, refer to Japanese Unexamined Patent Application Publication No. 2003-78597). [0012]However, in order to transmit or receive data by connecting a mobile phone to an external device, a plurality of signal transmission lines for input/output of a video signal, input/output of a sound signal, input/output of a user operation signal, and the like is necessary (refer to FIG. 10). That is, for the connection between the mobile phone and the external device, a plurality of cables is used for video, sound, and user operation or a plug cable having a terminal with many poles is used. In the former case where a plurality of cables is used, the connection and disconnection operations of the cables are troublesome for the user. Moreover, in the latter method of using the plug cable, there is a problem that it becomes difficult to secure the place for disposing the plug in the main body of the small mobile phone as the number of poles increases. In addition, problems also occur such as the device becoming expensive due to the cost of components, such as connectors, and difficulty in obtaining a contact point between the connectors with sufficient strength. [0013]In addition, when the classification of input or output signal changes with the model of the mobile phone, the number of poles of the plug also changes. In this case, the connectors for the external device are not compatible among different models, which is inconvenient. SUMMARY OF THE INVENTION [0014]In view of the above, it is desirable to provide a mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0015]In addition, it is desirable to provide a mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, a mobile terminal, an external device, and an input/output method of the mobile terminal. [0016]According to a first embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0017]The “system” referred to herein means a logical group of a plurality of devices (or functional modules for realizing specific functions), and it does not matter whether the devices or the functional modules exist in a single housing. [0018]According to a second embodiment of the present invention, a mobile terminal system including a mobile terminal and an external device includes: a first external device interface which is provided in the mobile terminal in order to output screen information to the external device and to receive operation information from the external device; a display section which is provided in the external device in order to display and output the screen information; a user input section which is provided in the external device and is used when a user inputs the operation information on the mobile terminal; and a second external device interface which is provided in the external device in order to receive the screen information from the mobile terminal and to output to the mobile terminal the operation information input through the user input section. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0019]Here, according to a third embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the power supply, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0020]In addition, according to a fourth embodiment of the present invention, the mobile terminal may be a mobile phone, and the screen information may be video data or still image data received through a mobile phone network. [0021]In addition, according to a fifth embodiment of the present invention, the first and second external device interfaces may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0022]In addition, according to a sixth embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface for transmitting the screen information to the external device and receiving the operation information from the external device through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0023]In addition, according to a seventh embodiment of the present invention, a mobile terminal that operates in the mobile terminal system according to the first embodiment of the present invention includes: a display section which outputs screen information; a user input section which is used when a user inputs operation information on the mobile terminal; a first external device interface which includes a coil and transmits the screen information to the external device and receives the operation information from the external device using the electric field of the coil; and a processor which outputs the screen information to the display section or the first external device interface and performs an operation of the mobile terminal according to the operation information input by the user input section or the operation information read from the first external device interface. [0024]Here, according to an eighth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0025]In addition, according to a ninth embodiment of the present invention, the first external device interface of the mobile terminal may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0026]In addition, according to a tenth embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface for receiving the screen information from the mobile terminal and transmitting the operation information to the mobile terminal through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal; and a display section which outputs the screen information received from the mobile terminal. [0027]In addition, according to an eleventh embodiment of the present invention, an external device that operates in the mobile terminal system according to the first embodiment of the present invention includes: a user input section which is used when a user inputs operation information on the mobile terminal; a second external device interface which includes a coil and receives the screen information from the mobile terminal and transmits the operation information to the mobile terminal using the electric field of the coil; and a display section which outputs the screen information received from the mobile terminal. [0028]Here, according to a twelfth embodiment of the present invention, the coil provided in the first external device interface may be a coil for power reception, the coil provided in the second external device interface may be a coil for power transmission, and a battery in the mobile terminal may be charged by using electromagnetic induction between the coils. That is, the “power signal” superimposed on the screen information and the operation information is assumed to include not only a current signal transmitted on a power cable but also various forms of signals transmitted on the media used for the supply of power, such as a magnetic signal in a non-contact charge mechanism that uses electromagnetic induction between the coil for power transmission and the coil for power reception. [0029]In addition, according to a thirteenth embodiment of the present invention, the second external device interface of the external device may perform parallel-to-serial conversion of transmission data and superimpose the converted data on the power signal and may reproduce received data superimposed on the power signal by performing serial-to-parallel conversion of the received data. [0030]In addition, according to a fourteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Transmission of the screen information and the operation information between the first and second external device interfaces is performed through a power signal used for the supply of power to the mobile terminal or for charging a battery in the mobile terminal. [0031]In addition, according to a fifteenth embodiment of the present invention, an input/output method of a mobile terminal in the mobile terminal system according to the first embodiment of the present invention includes the steps of: outputting the screen information from the first external device interface provided in the mobile terminal; performing display output of the screen information, which has been input to the second external device interface provided in the external device, in the display section of the external device; outputting the operation information, which has been input through the user input section of the external device, from the second external device interface; and operating the mobile terminal according to the operation information input to the first external device interface. Each of the first and second external device interfaces includes a coil, and transmission of the screen information and the operation information is performed using the electric field between the coils. [0032]According to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system that includes a mobile terminal which receives image data and sound data, such as a mobile phone, and an external device connected to the mobile terminal and that can output the image data and the sound data received in the mobile terminal to the outside through the external device and allow the performance of a user operation on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0033]Moreover, according to the embodiments of the present invention, it is possible to provide the excellent mobile terminal system in which a mobile terminal and an external device are connected to each other by an interface with a simple configuration so that image data and sound data received in the mobile terminal can be output to the outside through the external device and a user operation can be performed on the mobile terminal through the external device, the mobile terminal, the external device, and the input/output method of the mobile terminal. [0034]According to the first to third, sixth to eighth, tenth to twelfth, fourteenth, and fifteenth embodiments of the present invention, the received data can be displayed on the large screen and the mobile terminal can be operated by the input from an easy-to-use keyboard simply by placing the mobile terminal, in which the size of the display device or input device is not sufficient, on the external device. [0035]In addition, according to the fourth embodiment of the present invention, video data or still image data downloaded from the Internet to the mobile phone can be displayed using the large screen of the external device. [0036]In addition, according to the fifth, ninth, and thirteenth embodiments of the present invention, transmission using a small number of contact points is performed between the mobile phone and the external device. This is advantageous in that the connection interface is simplified, the component cost for the connection section is reduced, the device is small-sized, and deterioration of the contact point is prevented. These effects can be further improved by applying wireless connection, such as electric field transmission, to the connection interface. [0037]Moreover, according to the embodiments of the present invention, since it is sufficient to provide a simple connection interface with an external device, restrictions in the design can be reduced. [0038]Additional purposes, characteristics, and advantages of the present invention will be apparent from the detailed description made in the following embodiment of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS [0039]FIG. 1 is a diagram schematically illustrating the configuration of a mobile terminal system according to an embodiment of the present invention; [0040]FIG. 2 is a diagram illustrating an example of the configuration of transmitting the parallel data serially; [0041]FIG. 3 is a characteristic curve illustrating the frequency spectrum of a signal on a power line; [0042]FIG. 4A is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0043]FIG. 4B is a diagram illustrating another example of the serializer which transmits the parallel data serially; [0044]FIG. 5 is a diagram illustrating a write sequence example of a bus in a mobile phone and a bus in an external device when performing a write operation from the mobile phone to an LCD of the external device; [0045]FIG. 6 is a diagram illustrating a read sequence example of a bus in the mobile phone and a bus in the external device when performing an operation of reading the input information on a keyboard of the external device from the mobile phone; [0046]FIG. 7 is a diagram illustrating an interrupt sequence example of the bus in the mobile phone and the bus in the external device when an interrupt occurs on the keyboard of the external device; [0047]FIG. 8 is a diagram illustrating a format example of a transmission frame between the mobile phone and the external device; [0048]FIG. 9 is an illustration of an application image of the mobile terminal system shown in FIG. 1; and [0049]FIG. 10 is a diagram illustrating an example of the configuration of a past mobile terminal system. DESCRIPTION OF THE PREFERRED EMBODIMENTS [0050]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. [0051]FIG. 1 is a schematic diagram illustrating the configuration of a mobile terminal system according to an embodiment of the present invention. The system shown in FIG. 1 includes a mobile phone, which receives image data and sound data, and an external device, which outputs the image data and the sound data to the outside or which is used when a user operates the mobile phone. [0052]A mobile phone 100 includes a processor 101, various input/output devices 104 to 106, and an external device interface 107 for interfacing with an external device 120. Moreover, although the mobile phone 100 includes circuit modules for radio communications and the like, they are not shown because they are not directly related with the gist of the present invention. [0053]The processor 101 is connected to the various input/output devices 104 to 106 by a bus signal line group 110, a chip select signal 111, and an interrupt signal 112. [0054]The bus signal line group 110 includes signal lines, such as address, data, and enable. In addition to the various input/output devices 104 to 106, the bus signal line group 110 is also connected to the external device interface 107. [0055]The chip select signal 111 is a signal which is used when the processor 101 selects a circuit chip of one of the various input/output devices 104 to 106 through a bus interface 102. In addition, the interrupt signal 112 is a signal, which is used when the various input/output devices 104 to 106 notify the processor 101 of the occurrence of an event, and is input to an interrupt controller 103. The chip select signal 111 and the interrupt signal 112 are prepared in a quantity equal to the number of input/output devices and are also connected to the external device interface 107. [0056]First, an operation on the side of the mobile phone 100 will be described. [0057]When outputting data to the screen of an LCD 104, the processor 101 outputs image data to the LCD 104 using the bus interface 102. When outputting the data to the LCD 104, the bus interface 102 enables the chip select signal 111 connected to the LCD 104 so that the LCD 104 receives the image data from the processor 101 and displays the data on the screen. For example, video data or still image data downloaded through the mobile phone network from a web site on the Internet can be displayed on the screen of the LCD 104. [0058]In addition, also when outputting data to a speaker 105 or other output devices (not shown), the processor 101 similarly enables only the chip select signal 111 connected to the corresponding output device so that the output device receives the data from the processor 101 and reproduces and outputs the data. For example, sound data, such as music, downloaded through the mobile phone network from a web site on the Internet can be reproduced in the speaker 105. [0059]On the other hand, when there is a user input operation on a keyboard 106, the keyboard 106 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. The processor 101 which has received the interrupt receives the data, which has been input on the keyboard 106, through the bus 110. In this case, the bus interface 102 enables the chip select signal 111 connected to the keyboard 106 so that the keyboard 106 can output the data to the bus 110 and the processor 101 can receive the data. [0060]In addition, the same is true for the cases where an input operation has been performed by other input devices (not shown). That is, the input device generates an interrupt in response to the user input operation and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. On the other hand, the bus interface 102 enables the chip select signal 111 connected to the corresponding input device so that the input device outputs the data to the bus 110 and the processor 101 receives the data. [0061]Having described the data input/output operations between the input/output devices 104 to 106 and the processor 101, it may be understood that read and write operations of common registers for each input/output device are similarly realized by the above-described bus access method. [0062]In the system shown in FIG. 1, the mobile phone 100 is connected to the external device 120 through the external device interfaces 107 and 121. The external device 120 includes various enhanced input/output devices as user interfaces, such as an LCD 122 with a relatively large screen, a multi-channel speaker 123, and a large-sized keyboard 124 with tens of keys, such as alphanumeric keys. In addition, although not shown, the external device 120 may have a charge function for the mobile phone 100. [0063]In the past, a method of using a plug cable was commonly adopted for connection between a mobile phone and an external device. In this case, however, there are some problems as already stated. On the other hand, in the present embodiment, the external device interfaces 107 and 121 perform parallel-to-serial conversion of the address information and data information transmitted through the bus and then transmit this information under the conditions in which it is superimposed on a power interface 113. For this reason, neither the number of cables nor the number of poles of the plug is increased. [0064]Next, a method of transmitting and receiving data under the conditions in which the external device 120 is connected to the mobile phone 100 will be described. [0065]First, the case where the screen information of the mobile phone 100 is output to the external device 120 will be described. [0066]The bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the external device interface 107 can receive from the processor 101 the data to be displayed on the screen. In this case, it is assumed that the chip select signal 111 includes the classification indicating that transmitted data is screen information. [0067]The external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. [0068]The external device interface 121 of the external device 120 includes a bus interface function (not shown) and an interrupt controller function (not shown). In addition, the external device interface 121 converts the serial data, which has been received from the mobile phone 100 through the power interface 113, into parallel data to thereby restore it as the same data as in the mobile phone 100 which includes the classification of the chip select signal 111, the address information, and the data information. Then, the external device interface 121 transmits the data to the LCD 122 through a bus 133 by enabling a chip select signal 131 connected to the LCD 122. Thus, the LCD 122 displays and reproduces the same screen information as in the mobile phone 100. For example, video data or still image data downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be displayed on the screen of the LCD 122 in the external device 120. [0069]Moreover, the same is true for the case where the other output information on the side of the mobile phone 100 is output to the external device 120. [0070]For example, when the sound information is output to the external device 120, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107 so that the data for sound output is transmitted from the processor 101 to the external device interface 107. In this case, the chip select signal 111 includes the classification indicating that the transmitted data is sound information. Then, the external device interface 107 performs parallel-to-serial conversion of the classification of the chip select signal 111 and the address information and data information transmitted through the bus 110 and transmits such data to the power interface 113. On the other hand, the external device interface 121 of the external device 120 reproduces the same data as in the mobile phone 100 by performing serial-to-parallel conversion of the classification of the received chip select signal 111, the address information, and the data information and then transmits the data to the speaker 123 through the bus 133 by enabling the chip select signal 131 connected to the speaker 123. Thus, the speaker 123 reproduces and outputs the same sound information as in the mobile phone 100. For example, sound data, such as music, downloaded from a web site on the Internet to the mobile phone 100 through the mobile phone network can be reproduced in the speaker 123 of the external device 120. [0071]Next, a processing operation when a user input operation is performed using an input device of the external device 120 will be described. [0072]For example, when there is a user input operation on the keyboard 124, the keyboard 124 generates an interrupt and notifies the external device interface 121 through an interrupt signal 132. [0073]Upon receiving the interrupt signal, the external device interface 121 receives the data input on the keyboard 124 through the bus 133 by enabling the chip select signal 131 connected to the keyboard 124. Then, the external device interface 121 performs parallel-to-serial conversion of the classification of the chip select signal 131 and the address information and data information transmitted through the bus 132 and transmits such data to the power interface 113. [0074]Then, the external device interface 107 of the mobile phone 100 converts the serial data, which has been received from the external device 120 through the power interface 113, into parallel data to thereby restore it as the same data as in the external device 120 which includes the classification of the chip select signal 131, the address information, and the data information. In addition, the external device interface 107 generates an interrupt and notifies the interrupt controller 103 of the processor 101 through the interrupt signal 112. [0075]When the processor 101 receives the interrupt, the bus interface 102 enables the chip select signal 111 connected to the external device interface 107. In response to this, the external device interface 107 outputs the data to the bus 110. Thus, the processor 101 can receive the data input by the keyboard 124 of the external device 120. [0076]Moreover, the same is true for the case where other input information on the side of the external device 120 (String), 发明背景 [0001] 一、发明领域 [0002] 本发明涉及一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,移动终端,外部设备,以及输入/输出 移动端的方法。 具体地,本发明涉及一种移动终端系统,其通过外部设备向外部输出在移动终端中接收到的图像数据和声音数据,并且允许通过外部设备在移动终端上执行用户操作, 移动终端、外部设备和移动终端的输入/输出方法。 [0003] 二、相关技术说明 [0004] 移动电话作为移动通信系统的先驱,继承了车载电话的先河,随着终端的小型化、轻量化、低价化和服务费的降低,从1990年代开始迅速普及。 此外,随着计算机的普及和包括因特网在内的宽带网络技术的发展,可以在手机上进行电子邮件和网络搜索/访问,并且可以执行各种应用,例如音乐或视频播放和游戏。 [0005] 然而,虽然手机的应用范围多种多样,但由于手机需要便携的尺寸,因此在输入和输出方面存在很多限制。 例如,屏幕尺寸对角线约5至10厘米。 在这种情况下,尽管近年来由于平板制造技术的发展分辨率越来越高,但高分辨率显示会导致可见性问题,例如,相同字体大小的字符变得非常小。 [0006] 另外,手机中设置的输入部分一般只有0到9的数字键盘,以及可以进行上下左右输入操作的按键,以及其他一些按键。 与个人电脑的键盘有60到100个按键相比,手机的按键数量少,输入操作也比较困难。 [0007] 近几年,也出现了类似QWERTY键盘的几十个按键的手机。 然而,由于设备大小的便携性限制,每个密钥都很小。 为此,输入操作还是有难度的。 [0008] 为了解决这样的问题,可以考虑将移动电话连接到具有相对大屏幕的外部设备或易于执行输入操作的输入设备的方法。 [0009] 例如,提出了使用移动终端的显示处理系统。 在显示处理系统中,显示在移动电话的液晶屏幕上的图像可以显示在电视屏幕上(例如,参考日本未审查专利申请公开No.2001-352373)。 [0010] 此外,还提出了一种屏幕显示装置,其具有用于连接手机的入口。 屏幕显示设备在大屏幕上显示在移动电话中接收到的图像数据(例如,参考日本未审查专利申请公开No.2002-116843)。 [0011] 此外,还提出了一种带有独立显示器的移动电话。 移动电话显示在移动电话内置的监视器上显示的数据或在单独的监视器上下载的显示数据(例如,参考日本未审查专利申请公开No.2003-78597)。 [0012]然而,为了通过将移动电话连接到外部设备来发送或接收数据,用于视频信号的输入/输出、声音信号的输入/输出、用户操作信号的输入/输出的多条信号传输线 ,等等是必要的(参考图10)。 也就是说,对于移动电话和外部设备之间的连接,使用多根电缆用于视频、声音和用户操作,或者使用具有多极端子的插头电缆。 在使用多根电缆的前一种情况下,电缆的连接和断开操作对用户来说很麻烦。 此外,在后一种使用插头电缆的方法中,随着极数的增加,存在难以确保小型移动电话主体中用于布置插头的位置的问题。 此外,还存在由于连接器等部件的成本而导致装置变得昂贵、连接器之间的接触点难以获得足够强度的问题。 [0013] 另外,随着手机型号不同,输入或输出信号的分类发生变化时,插头的极数也会发生变化。 在这种情况下,外部设备的连接器在不同型号之间不兼容,这很不方便。 发明内容 [0014] 鉴于上述情况,期望提供一种移动终端系统,包括接收图像数据和声音数据的移动终端,例如手机,以及连接到移动终端并能够输出图像数据的外部设备。 以及移动终端中接收到的声音数据通过外部设备发送到外部并允许用户通过外部设备在移动终端上执行操作、移动终端、外部设备以及移动设备的输入/输出方法 终端。 [0015] 此外,期望提供一种移动终端系统,其中移动终端和外部设备通过具有简单配置的接口相互连接,使得在移动终端中接收的图像数据和声音数据可以输出到 外部设备通过外部设备可以在移动终端上进行用户操作、移动终端、外部设备和移动终端的输入/输出方法。 [0016] 根据本发明第一实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作。 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0017] 这里所说的“系统”是指多个设备(或实现特定功能的功能模块)的逻辑集合,与设备或功能模块是否存在于一个外壳内无关。 [0018]根据本发明的第二实施例,一种包括移动终端和外部设备的移动终端系统,包括:第一外部设备接口,设置在移动终端中,用于向外部设备输出屏幕信息和接收操作 来自外部设备的信息; 显示部分,设置在外部设备中以显示和输出屏幕信息; 用户输入部分,设置在外部设备中,当用户在移动终端上输入操作信息时使用; 第二外部设备接口,设置在外部设备中,以接收来自移动终端的屏幕信息,并将通过用户输入部分输入的操作信息输出到移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0019] 这里,根据本发明的第三实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 即,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括电力电缆上传输的电流信号,还包括用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0020] 另外,根据本发明的第四实施例,移动终端可以是手机,屏幕信息可以是通过手机网络接收的视频数据或静止图像数据。 [0021] 此外,根据本发明的第五实施例,第一和第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据 通过对接收到的数据进行串并转换。 [0022] 此外,根据本发明的第六实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,用于通过电源信号向外部设备发送屏幕信息和接收来自外部设备的操作信息,用于为移动终端供电或为移动终端中的电池充电; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0023] 此外,根据本发明的第七实施例,在根据本发明第一实施例的移动终端系统中运行的移动终端包括:显示部分,输出屏幕信息; 当用户在移动终端上输入操作信息时使用的用户输入部分; 第一外部设备接口,包括线圈,利用线圈的电场向外部设备发送屏幕信息,并从外部设备接收操作信息; 处理器将屏幕信息输出到显示部分或第一外部设备接口,并根据用户输入部分输入的操作信息或从第一外部设备接口读取的操作信息执行移动终端的操作。 [0024]这里,根据本发明的第八实施例,设置在第一外部设备接口中的线圈可以是用于电力接收的线圈,设置在第二外部设备接口中的线圈可以是用于电力传输的线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0025] 此外,根据本发明的第九实施例,移动终端的第一外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在功率信号上,并且可以再现叠加在功率信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0026] 此外,根据本发明的第十实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用。 终端; 第二外部设备接口,用于接收来自移动终端的屏幕信息,并通过电源信号向移动终端发送操作信息,用于为移动终端供电或为移动终端中的电池充电; 显示部分输出从移动终端接收的屏幕信息。 [0027] 此外,根据本发明的第十一实施例,在根据本发明第一实施例的移动终端系统中操作的外部设备包括:用户输入部分,当用户在移动设备上输入操作信息时使用该用户输入部分。 终端; 第二外部设备接口,包括线圈,接收来自移动终端的屏幕信息,并利用线圈的电场向移动终端发送操作信息; 显示部分输出从移动终端接收的屏幕信息。 [0028] 这里,根据本发明的第十二实施例,第一外部设备接口中设置的线圈可以是用于电力接收的线圈,第二外部设备接口中设置的线圈可以是电力传输线圈,并且电池在 可以利用线圈之间的电磁感应为移动终端充电。 也就是说,假设叠加在屏幕信息和操作信息上的“电源信号”不仅包括在电源线上传输的电流信号,还包括在用于供电的介质上传输的各种形式的信号,例如 非接触式充电机构中的磁信号,该机构使用电力传输线圈和电力接收线圈之间的电磁感应。 [0029] 此外,根据本发明的第十三实施例,外部设备的第二外部设备接口可以执行传输数据的并行到串行转换并将转换后的数据叠加在电力信号上,并且可以再现叠加在电源信号上的接收数据。 通过对接收到的数据执行串并转换来输出功率信号。 [0030]另外,根据本发明的第十四实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口之间的屏幕信息和操作信息的传输是通过用于为移动终端供电或为移动终端中的电池充电的电源信号来执行的。 [0031] 另外,根据本发明第十五实施例,根据本发明第一实施例的移动终端系统中的移动终端的输入/输出方法包括以下步骤:从第一外部设备输出屏幕信息 移动终端提供的界面; 在外部设备的显示部中显示输出输入到设置于外部设备的第二外部设备接口的画面信息。 从第二外部设备接口输出已经通过外部设备的用户输入部分输入的操作信息; 根据输入到第一外部设备接口的操作信息操作移动终端。 第一和第二外部设备接口中的每一个都包括线圈,并且使用线圈之间的电场来执行屏幕信息和操作信息的传输。 [0032] 根据本发明的实施例,可以提供出色的移动终端系统,其包括接收图像数据和声音数据的移动终端,例如移动电话,以及连接到移动终端的外部设备,并且能够 将在移动终端中接收到的图像数据和声音数据通过外部设备输出到外部,并允许用户通过外部设备在移动终端上进行操作,移动终端,外部设备,输入/输出 移动端的方法。 [0033] 此外,根据本发明的实施例,可以提供出色的移动终端系统,其中移动终端和外部设备通过具有简单配置的接口彼此连接,使得接收到的图像数据和声音数据 移动终端中的信息可以通过外部设备输出到外部,用户可以通过外部设备对移动终端进行操作,移动终端,外部设备,移动终端的输入/输出方法。 [0034] 根据本发明的第一至第三、第六至第八、第十至第十二、第十四和第十五实施例,可以在大屏幕上显示接收到的数据,并且可以通过来自易于操作的输入来操作移动终端。 - 只需将显示设备或输入设备的尺寸不够大的移动终端放在外部设备上即可使用键盘。 [0035] 此外,根据本发明的第四实施例,可以使用外部设备的大屏幕来显示从互联网下载到移动电话的视频数据或静止图像数据。 [0036]此外,根据本发明的第五、第九和第十三实施例,在移动电话和外部设备之间执行使用少量接触点的传输。 这是有利的,因为简化了连接接口,降低了连接部分的组件成本,设备尺寸小,并且防止了接触点的劣化。 通过对连接接口应用无线连接,例如电场传输,可以进一步改善这些效果。 [0037] 此外,根据本发明的实施例,由于提供简单的与外部设备的连接接口就足够了,因此可以减少设计上的限制。 [0038] 本发明的其他目的、特征和优点将通过以下结合附图对本发明的实施例的详细描述而显而易见。 附图的简要说明 [0039] 图1是表示本发明的一个实施方式的移动终端系统的概略结构的图。 [0040] 图2是表示串行发送并行数据的结构例的图。 [0041] 图3是电力线上信号的频谱特性曲线。 [0042] 图4A是表示串行地发送并行数据的串行器的另一例的图。 [0043] 图4B是表示串行地发送并行数据的串行器的另一例的图。 [0044] 图5是表示从移动电话向外部设备的LCD进行写入时的移动电话内的总线和外部设备的总线的写入顺序例的图。 [0045] 图6是表示进行从移动电话读取外部设备的键盘的输入信息的操作时的移动电话内的总线和外部设备的总线的读取顺序例的图。 [0046] 图7是表示在外部设备的键盘上发生中断时的移动电话内的总线和外部设备内的总线的中断时序例的图。 [0047] 图8是表示移动电话与外部设备之间的传输帧的格式例的图。 [0048] 图9为图1所示的移动终端系统的应用程序图像示意图。 和 [0049] 图10是表示以往的便携终端系统的结构例的图。 优选实施例的描述 [0050] 在下文中,将参考附图描述本发明的实施例。 [0051] 图1是图示根据本发明实施例的移动终端系统的配置的示意图。 图1所示的系统包括接收图像数据和声音数据的移动电话,以及将图像数据和声音数据输出到外部或者当用户操作移动电话时使用的外部设备。 [0052] 一部手机 100 包括一个处理器 101 , 各种输入输出设备 104 到 106 , 和一个外部设备接口 107 用于连接外部设备 120 . 而且,虽然手机 100 包括无线电通信等电路模块,由于与本发明的主旨无直接关系,故未图示。 [0053] 处理器 101 连接到各种输入/输出设备 104 到 106 通过总线信号线组 110 , 片选信号 111 , 和一个中断信号 112 . [0054] 总线信号线组 110 包括信号线,例如地址、数据和启用。 除了各种输入/输出设备 104 到 106 ,总线信号线组 110 也连接到外部设备接口 107 . [0055] 片选信号 111 是处理器使用的信号 101 选择各种输入/输出设备之一的电路芯片 104 到 106 通过总线接口 102 . 此外,中断信号 112 是信号,在各种输入/输出设备时使用 104 到 106 通知处理者 101 一个事件的发生,并被输入到一个中断控制器 103 . 片选信号 111 和中断信号 112 准备了与输入/输出设备数量相等的数量,并连接到外部设备接口 107 . [0056] 一、手机端的一个操作 100 将被描述。 [0057] 将数据输出到 LCD 屏幕时 104 , 处理器 101 输出图像数据到LCD 104 使用总线接口 102 . 向 LCD 输出数据时 104 , 总线接口 102 启用片选信号 111 连接到液晶显示器 104 这样液晶显示器 104 从处理器接收图像数据 101 并将数据显示在屏幕上。 例如,通过手机网络从 Internet 上的网站下载的视频数据或静止图像数据可以显示在 LCD 的屏幕上 104 . [0058] 此外,当向扬声器输出数据时 105 或其他输出设备(未显示),处理器 101 同样只启用片选信号 111 连接到相应的输出设备,以便输出设备接收来自处理器的数据 101 并再现和输出数据。 例如,可以在扬声器中再现通过手机网络从互联网网站下载的音乐等声音数据 105 . [0059] 另一方面,当用户在键盘上进行输入操作时 106 , 键盘 106 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . 处理器 101 接收到中断 接收到键盘输入的数据 106 , 通过公交车 110 . 在这种情况下,总线接口 102 启用片选信号 111 连接到键盘 106 这样键盘 106 可以将数据输出到总线 110 和处理器 101 可以接收数据。 [0060] 另外,对于由其他输入设备(未图示)进行了输入操作的情况也是同样的。 即输入设备响应用户输入操作产生中断,通知中断控制器 103 处理器的 101 通过中断信号 112 . 另一方面,总线接口 102 启用片选信号 111 连接到相应的输入设备,使输入设备输出数据到总线 110 和处理器 101 接收数据。 [0061] 描述了输入/输出设备之间的数据输入/输出操作 104 到 106 和处理器 101 可以理解,对于每个输入/输出设备的公共寄存器的读写操作是通过上述总线访问方法类似地实现的。 [0062] 在图1所示的系统中,手机 100 连接到外部设备 120 通过外部设备接口 107 和 121 . 外部设备 120 包括各种增强型输入/输出设备作为用户界面,例如 LCD 122 屏幕比较大,多声道喇叭 123 , 和一个大尺寸的键盘 124 带有数十个键,例如字母数字键。 此外,虽然没有显示,外部设备 120 可能有手机充电功能 100 . [0063]以往,手机与外部设备的连接通常采用插头线的方式。 然而,在这种情况下,存在已经提到的一些问题。 另一方面,在本实施例中,外部设备接口 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些信息 113 . 为此,既没有增加电缆的数量,也没有增加插头的极数。 [0064] 接下来介绍一种在外部设备不可用的情况下发送和接收数据的方法 120 已连接手机 100 将被描述。 [0065] 一、手机屏幕信息的情况 100 输出到外部设备 120 将被描述。 [0066] 总线接口 102 启用片选信号 111 连接到外部设备接口 107 使外部设备接口 107 可以从处理器接收 101 要显示在屏幕上的数据。 在这种情况下,假定片选信号 111 包括指示传输的数据是屏幕信息的分类。 [0067] 外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . [0068] 外部设备接口 121 外部设备的 120 包括总线接口功能(未显示)和中断控制器功能(未显示)。 此外,外部设备接口 121 转换从手机接收到的串口数据 100 通过电源接口 113 , 转化为并行数据从而恢复为与手机中相同的数据 100 其中包括片选信号的分类 111 、地址信息和数据信息。 然后,外部设备接口 121 将数据传输到 LCD 122 通过公共汽车 133 通过使能片选信号 131 连接到液晶显示器 122 . 因此,液晶 122 显示和再现与手机相同的屏幕信息 100 . 例如,从互联网网站下载到手机的视频数据或静止图像数据 100 通过手机网络可以显示在液晶屏上 122 在外部设备中 120 . [0069] 而且,其他手机端输出信息的情况也是如此 100 输出到外部设备 120 . [0070] 例如,当声音信息输出到外部设备时 120 , 总线接口 102 启用片选信号 111 连接到外部设备接口 107 以便声音输出的数据从处理器传输 101 到外部设备接口 107 . 在这种情况下,片选信号 111 包括指示传输的数据是声音信息的分类。 然后,外部设备接口 107 对片选信号的分类进行并串转换 111 以及通过总线传输的地址信息和数据信息 110 并将这些数据传输到电源接口 113 . 另一方面,外部设备接口 121 外部设备的 120 再现与手机中相同的数据 100 通过对接收到的片选信号进行分类串并转换 111 ,地址信息,数据信息,然后将数据传输给扬声器 123 通过公共汽车 133 通过使能片选信号 131 连接到扬声器 123 . 因此,演讲者123 再现和输出与手机相同的声音信息 100 . 例如,从互联网上的网站下载到手机中的音乐等声音数据 100 通过手机网络可以在音箱中重现 123 外部设备的 120 . [0071] 接下来,使用外部设备的输入设备进行用户输入操作时的处理操作 120 将被描述。 [0072] 例如,当键盘上有用户输入操作时 124 , 键盘 124 产生中断并通知外部设备接口 121 通过中断信号 132 . [0073] 接收到中断信号后,外部设备接口 121 接收键盘输入的数据 124 通过公共汽车 133 通过使能片选信号 131 连接到键盘 124 . 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0074] 然后,外部设备接口 107 手机的 100 转换从外部设备接收到的串行数据 120 通过电源接口 113 , 转换为并行数据,从而将其恢复为与外部设备中相同的数据 120 其中包括片选信号的分类 131 、地址信息和数据信息。 此外,外部设备接口 107 产生中断并通知中断控制器 103 处理器的 101 通过中断信号 112 . [0075] 当处理器 101 接收到中断,总线接口 102 启用片选信号 111 连接到外部设备接口 107 . 响应于此,外部设备接口 107 将数据输出到总线 110 . 因此,处理器 101 可以接收键盘输入的数据 124 外部设备的 120 . [0076] 此外,对于外部设备侧的其他输入信息的情况也是如此 120 被输入到手机 100 . [0077] 即输入设备响应用户输入操作等产生中断通知给外部设备接口 121 . 接收到中断信号后,外部设备接口 121 通过总线接收数据 133 通过使能片选信号 131 连接到相应的输入设备。 然后,外部设备接口 121 对片选信号的分类进行并串转换 131 以及通过总线传输的地址信息和数据信息 132 并将这些数据传输到电源接口 113 . [0078] 外部设备接口 107 手机的 100 对片选信号的分类进行串并转换 131 、地址信息、从外部设备接收到的数据信息 120 ,从而恢复与外部设备中相同的数据 120 . 此外,外部设备接口 107 通知中断控制器 103 处理器的 101 通过中断信号 112 有来自外部设备的输入 120 . 然后,总线接口 102 启用片选信号 111 连接到外部设备 120 这样处理器 101 从外部设备接收输入数据 120 . [0079] 描述了输入/输出设备之间的数据输入/输出操作 122 到 124 外部设备的 120 和处理器 101 手机的 100,可以理解为外部设备的每个输入/输出设备的公共寄存器的读写操作 120 通过上述总线访问方法类似地实现。 [0080] 在本实施例中,手机与手机之间的接口 100 和外部设备 120 通过采用外部设备接口的方法简化了 107 和 121 将总线传输的地址信息和数据信息进行并串转换,然后在叠加到电源接口的条件下传输这些数据 113 . [0081] 图2例示了串行传输并行数据的配置示例。 图2所示的传输系统包括串行器 200 和反序列化器 210 它们通过电源线相互连接 220 作为电源接口 113 . 假设这对序列化器 200 和反序列化器 210 双向设置于外部设备接口 107 手机的 100 和外部设备接口 121 外部设备的 120 . [0082] 序列化器 200 包括一个 PS(并行到串行)转换器 201 将并行信号转换为串行信号,PLL 部分 202 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 203 通过向串行信号添加标头等来执行编码,时序控制器 204 它控制传输时间,和一个司机 205 . [0083] 另一方面,反序列化器 210 包括一个接收器 212 , 解码器 213 它通过从报头、时钟恢复 (CR) 部分检测数据的头部来解码编码数据 214 它使用参考时钟 (Ref. CLK)、SP(串行到并行)转换器从接收到的数据中提取时钟 215 它将串行信号转换为原始并行信号,以及一个时序控制器 216 它控制接收时间。 [0084] 因此,输入到串行器的并行数据 P-DATA 和用于串行数据的时钟 P-CLK 200 转换为串行信号,通过解串器恢复为原来的并行数据P-DATA和时钟P-CLK 210 . [0085] 在图 2 所示的示例中,电源线 220 用作传输线,在叠加在电源线上的条件下传输串行信号 220 从外部设备 120 到手机 100 . 叠加部分 206 将传输信号叠加在用于供电的功率信号上。 基本上,叠加部分 206 将传输信号与电源线耦合 220 通过一个电容器并将电源信号与电源线耦合 220 通过扼流圈。 [0086] 到达解串器的传输信号 210 通过电源线 220 通过分离部分与电源信号分离 212 . 类似于叠加部分 206 , 在分离部分 211 ,在通过电容器切断直流分量之后提取传输信号,并且通过扼流圈从传输信号中切断功率信号。 [0087] 此外,可以提及曼彻斯特编码作为编码器中应用的编码方法的示例 203 和解码器 213. 在曼彻斯特编码中,当传输一个二进制值“0”时,它在位段中间由高电平变为低电平。 另一方面,当传输二进制值“1”时,它在比特部分的中间从低电平相反地变为高电平。 换言之,在曼彻斯特编码中,通过两次扩展频带来去除传输信号的DC分量。 由于曼彻斯特码的优点在于不包括直流分量并且容易提取时钟,因此认为曼彻斯特码适合与具有直流分量的电力叠加在同一传输线上。 电力线上信号的频谱 220 如图3所示。在图3中,附图标记 301 表示曼彻斯特码的频谱。 已知曼彻斯特码可以在不包括直流分量的情况下与功率信号一起传输。 [0088] 串行传输并行数据的串行器和解串行器的另一配置示例在图4A和4B中示出。 [0089] 序列化器 400 包括一个PS转换器 401 将并行信号转换为串行信号,PLL 部分 402 它从并行数据的时钟 (P-CLK) 生成串行时钟,编码器 403 通过向串行信号添加标头等来执行编码,时序控制器 404 它控制传输时间,和一个司机 405 . 编码器编码的串行信号 403 被传输到一个线圈 406 通过司机 405 然后传输到解串器 410 通过线圈之间的电磁耦合。 [0090] 另一方面,反序列化器 410 包括一个线圈 411 它与线圈进行电磁耦合 406 在序列化器的一侧 400 , 一个差分接收器 412 , 放大器 413 放大由电磁耦合降低的信号电平,解码器 414 它从报头中检测数据的头部并对编码数据进行解码,时钟恢复(CR)部分 415 它使用参考时钟 (Ref. CLK)、SP 转换器从接收到的数据中提取时钟 416 它将串行信号转换为原始并行信号,以及一个时序控制器 417 它控制接收时间。 [0091] 当采用图2或图4A、4B所示的串行传输作为电源接口时 113 连接外部设备 120 和手机 100 相互之间,可以将数据叠加在电源信号上,并且可以在从外部设备进行充电的同时进行数据传输 120 到手机 100 . 此外,根据图4A和4B所示的串行传输方法,可以使用线圈在电场中传输数据。 结果,由于可以通过无线连接发送和接收数据,因此连接外部设备的电缆 120 用手机 100 变得不必要。 [0092] 接下来是手机之间进行数据收发时的总线访问操作 100 和外部设备 120 将被描述。 下面根据美国英特尔公司的80总线架构来描述总线访问操作。 然而,本发明不限于此。 [0093] 图 5 说明了总线的写入序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 从手机执行写入操作时 100 到液晶显示器 122 外部设备的 120 . [0094] 在手机里 100 ,处理器断言(启用)具有 LCD 分类的片选信号 101 . 随后,总线上的写信号 110 由处理器断言 101 然后将写数据传输到总线 110 . [0095] 通过这样的操作,数据被写入外部设备接口 107 手机的100 . 然后,外部设备接口 107 将请求写入的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0096] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 随后,外部设备接口 121 断言连接到 LCD 的片选信号 122 , 断言总线上的写信号 133 ,然后将写数据传输到总线 110 . 因此,将数据写入LCD 122 被执行。 结果,液晶 122 可以显示和再现与手机相同的屏幕信息 100 . [0097] 此外,可以理解为在每个移动电话中执行相同的总线写入序列 100 和外部设备 120 同样在手机输出其他信息的情况下 100 写入外部设备 120 . [0098] 图 6 说明了总线的读取序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 执行读取键盘输入信息的操作时 124 外部设备的 120 从手机 100 . [0099] 在手机里 100 ,具有键盘分类的片选信号被断言,然后总线上的读取信号 110 由处理器断言 101 . 然后,外部设备接口 107 手机的 100 将请求读取的信号(地址信息和数据信息)进行并串转换,并将转换后的信号串行传输到外部设备 120 通过电源接口 113 . [0100] 外部设备接口 121 外部设备的 120 提取片选信号的分类 111 ,地址信息和数据信息通过将接收到的串行数据转换成并行数据。 然后,外部设备接口 121 断言连接到键盘的片选信号 124 然后在总线上断言读取信号 133 . 然后,键盘 124 将输入数据传输到总线 110 . [0101] 从键盘读取数据后 124 , 外接设备接口 121 将数据转换成串口数据串口传输给手机 100 通过电源接口 113 . [0102] 外部设备接口 107 手机的 100 提取键盘上的输入数据 124 通过将接收到的串行数据转换成并行数据,然后传输到总线 110 在读信号被断言的期间。 因此,处理器 101 可以从键盘读取输入数据 124 外部设备的 120 . [0103] 此外,可以理解,在每个移动电话中执行相同的总线读取序列 100 和外部设备 120 同样在外部设备的其他输入信息的情况下 120 在手机中读取 100 . [0104] 图 7 说明了总线的中断序列示例 110 在手机里 100 和公共汽车 133 在外部设备中 120 当键盘发生中断时 124 外部设备的 120 . [0105] 键盘 124 断言中断信号 132 当中断发生时。 外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113. 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 断言中断信号 112 . [0106] 处理器收到中断信号后 101 根据上述过程执行总线访问(读或写)。 例如,总线接口 102 启用片选信号 111 连接到外部设备接口 107 , 这样处理器 101 读取键盘上的输入数据 124 从外部设备 120 通过公共汽车 110 . [0107] 随后,当键盘 124 否定中断信号 132 通过释放中断,外部设备接口 121 外部设备的 120 将接收到的中断信号进行并串转换,串传给手机 100 通过电源接口 113 . [0108] 当外部设备接口 107 手机的 100 从键盘中提取中断信号 124 通过对接收到的数据执行串并转换,外部设备接口 107 否定中断信号 112 . 结果在手机端也释放了键盘中断 100 . [0109] 图 8 说明了移动电话之间的传输帧的格式示例 100 和外部设备 120 . [0110] 图8所示的传输帧在报头部分包括数据类型、设备类型和数据长度字段。 [0111] 数据类型字段长度为2位,用于区分传输帧对应的读、写、中断发生和中断释放。 例如0×00表示读,0×01表示写,0×02表示中断。 [0112] 设备类型字段,长度为2比特,用于区分传输帧是对哪个设备的读或写请求,或者是区分传输帧是来自哪个设备的中断发生或释放请求。 例如0×00表示LCD,0×01表示键盘,0×02表示扬声器。 [0113] 数据长度字段具有1个字节的长度,并且传输帧的数据(有效载荷)部分的长度例如以比特数来描述。 [0114] 此外,位 0 到最后一位连接在传输帧的数据部分。 [0115] 此外,图8所示的传输帧格式只是一个例子,本发明不限于此。 可以使用根据应用本发明的系统适当定义的任何传输帧格式。 此外,传输帧中可以包括使用校验和的错误检测和错误纠正等功能。 [0116] 图9是图1所示的移动终端系统的应用程序图像的图示。 [0117] 外部设备 901 包括液晶显示器 901 带有相对较大的屏幕和键盘 903 使用 QWERTY 排列中的所有键。 通过放置手机 904 在连接部分 902 , 手机屏幕 904 可以显示在LCD上 901 和手机 904 可以通过键盘上的用户输入进行操作 903 . [0118] 一个联络点 905 与手机连接 904 在连接部分提供 902 , 这样手机 904 可以充电,可以通过触点进行数据传输 905 . [0119] 然而,当如图 4A 和 4B 所示执行使用线圈的电场传输时,接触点 905 外部设备之间 900 和手机 904不存在,通过线圈进行通信 906 在外部设备中提供 900 . [0120] 本申请包含与 2008 年 10 月 15 日向日本专利局提交的日本优先权专利申请 JP 2008-266856 中公开的主题相关的主题,其全部内容通过引用并入本文。 [0121] 本领域技术人员应当理解,可以根据设计要求和其他因素进行各种修改、组合、子组合和变更,只要它们在所附权利要求或其等同物的范围内。(String), 111496(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.890 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:07.890 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101729662A(String), CN101729662B(String), JP2010098484A(String), JP4893722B2(String), US20100093394A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), CN101729662A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), CN101729662B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), JP2010098484A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270642(Integer), JP4893722B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.259 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270642(Integer), US20100093394A1(String), 1046837(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100093394A1(String), US20100093394A1(String), 1271260800(Integer), 270642(Integer), 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), HIDAKA, ISAO(String), 索尼公司(String), HIDAKA ISAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184925(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 184925(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HIDAKA, ISAO(String), HIDAKA ISAO(String), 255(String), 0(Integer), 1681971126(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 75781(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184925(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75781(Integer), 2(Integer), 184925(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75781(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.908 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.908 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.930 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.994 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10075579B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.995 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:08.995 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.014 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.015 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.015 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 226(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.040 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.311 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.311 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.331 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.334 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.336 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 103(Integer), 1(Integer), 0(Integer), 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.337 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.338 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184926(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.356 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.358 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\23b6d7318e7b415b9419e53767227fdf.png(String), 184926(Integer), 23b6d7318e7b415b9419e53767227fdf.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, user interface method in the mobile terminal, and cover of the mobile terminal(String), 移动终端、移动终端中的用户界面方法及移动终端的外壳(String), US10075579B2(String), A mobile terminal, a method in the mobile terminal, and a cover of the mobile terminal are provided for processing input. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined, and a second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area while the cover is closed over the touch screen is detected and the first input as a first control command is processed.(String), 本 发明提供一种移动终端、移动终端中的方法及移动终端的外壳,用于处理输入。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域,并定义了与封面的非窗口区域对应的移动终端的触摸屏的第二区域。 检测当盖板在触摸屏上关闭时第二区域中的第一输入,并且处理作为第一控制命令的第一输入。(String), US14/603760(String), 1421942400(Integer), US10075579B2(String), 1536595200(Integer), 1536595200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 7(Integer), 40(Integer), JP2006277739A | JP2008097966A | KR101285669B1 | KR1020080108839A | KR1020110025939A | KR1020130004769A | KR200464076Y1 | KR2020120005719U | US20040248621A1 | US20080062348A1 | US20100238119A1 | US20110065474A1 | US20110260980A1 | US20120098760A1 | US20120250241A1 | US20130083465A1 | US20130109435A1 | US20130181935A1 | US20130300679A1 | US20140073377A1 | US20140128131A1 | US20140185206A1 | US20140198070A1 | US20140204511A1 | US20140274214A1 | US20140292589A1 | US20140357330A1 | US20150105128A1 | US20150138021A1 | US20150155903A1 | US20150229754A1 | US20150280770A1 | US20160154512A1 | US20160277053A1 | US9307129B2 | WO2001028190A1(String), \20230420\23b6d7318e7b415b9419e53767227fdf.png(String), 31(Integer), 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 31 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 1. A method of processing input in a mobile terminal, the method comprising:identifying a first area of a touch screen of the mobile terminal corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 1.一种在移动终端中处理输入的方法,该方法包括:通过接收来自外壳的信息识别移动终端的触摸屏的第一区域对应于外壳的窗口区域和触摸屏的第二区域对应于外壳的非窗口区域;检测触摸屏上方的移动终端盖板是否合上;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 2. The method of claim 1, further comprising determining a type of the cover, wherein the first area and the second area are defined according to the type of the cover.(String), 2.如权利要求1所述的方法,还包括判断封面的类型,其中第一区域与第二区域是根据封面的类型定义的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 3. The method of claim 1, further comprising determining whether an event has occurred, while the cover is closed over the touch screen of the mobile terminal, wherein the first area and the second area are defined according to occurrence of the event.(String), 3.如权利要求1所述的方法,还包括在移动终端的触摸屏上盖合上时判断事件是否发生,其中第一区域和第二区域是根据事件的发生定义的。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 4. The method of claim 1, further comprising:detecting a third input in the first area while the cover is closed over the touch screen;processing the third input as a third control command; anddetecting a fourth input in the second area while the cover is closed over the touch screen; and processing the fourth input as a fourth control command,wherein the third input and the fourth input are of a same type, which is different from that of the first input and the second input.(String), 4.如权利要求1所述的方法,还包括:在触摸屏上盖合上时检测第一区域中的第三输入;将第三输入处理为第三控制命令;和在触摸屏上盖合上时检测第二区域中的第四输入;并将第四输入处理为第四控制命令,其中,第三输入与第四输入为同一类型,与第一输入与第二输入不同。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 5. The method of claim 1, further comprising receiving cover type information from the cover.(String), 5.如权利要求1所述的方法,还包括从封面接收封面类型信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 6. The method of claim 5, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 6.如权利要求5所述的方法,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 7. The method of claim 1, further comprising activating a part of the touch screen according to the first and second areas, while the cover is closed over the touch screen.(String), 7.如权利要求1所述的方法,还包括根据第一区域和第二区域激活触摸屏的一部分,同时关闭触摸屏上的盖体。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 8. The method of claim 1, further comprising, when the cover is closed over the touch screen, activating a screen of the first area and a touch sensing area of the second area.(String), 8.如权利要求1所述的方法,还包括,当盖合于触控屏幕上时,激活第一区域的屏幕和第二区域的触控感应区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 9. The method of claim 1, wherein processing the first input comprises displaying information in the first area according to the first input detected in the second area.(String), 9.如权利要求1所述的方法,其中处理第一输入包括根据在第二区域中检测到的第一输入在第一区域中显示信息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 10. The method of claim 9, wherein the information comprises at least one of music play information, a camera preview, busy call information, and information about at least one application.(String), 10.如权利要求9所述的方法,其中该信息包括音乐播放信息、相机预览、忙音信息和至少一个应用程序的信息中的至少一种。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 11. A mobile terminal comprising:a touch screen; anda processor configured to:identify a first area of the touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detect whether the cover of the mobile terminal is closed over the touch screen,detect an input in the touch screen while the cover is closed over the touch screen, determine whether the input is a first input in the first area or a second input in the second area, process a first control command according to the first input in the first area, and a second control command according to the second input in the second area,wherein the first input and the second input are a same gesture type, andwherein the first control command and the second control command are different control command.(String), 11.移动终端包括:触摸屏;和处理器配置为:通过接收来自外壳的信息,识别对应于移动终端外壳的窗口区域的触摸屏的第一区域和对应于外壳的非窗口区域的触摸屏的第二区域;检测触摸屏上方移动终端的盖板是否合上,在触摸屏上盖合上时检测触摸屏中的输入,判断输入是第一区域中的第一输入还是第二区域中的第二输入,根据第一区域中的第一输入处理第一控制命令第一区域,以及根据第二区域中的第二输入的第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 12. The mobile terminal of claim 11, wherein the non-window area of the cover includes a keypad configured to apply a key input, and the processor is further configured to detect the key input applied through the keypad of the non-window area of the cover in the second area.(String), 12.如权利要求11所述的移动终端,其中所述盖板的非窗口区域包括键盘,用于进行键输入,所述处理器还用于在所述第二区域中检测通过所述盖板的非窗口区域的键板施加的键输入。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 13. The mobile terminal of claim 12, wherein the processor is further configured to receive a text input as a result of detecting the key input through the keypad and control execution of a function according to the text input.(String), 13.如权利要求12所述的移动终端,其中处理器还被配置为接收作为检测通过小键盘的键输入的结果的文本输入,并根据文本输入控制功能的执行。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 14. The mobile terminal of claim 11, further comprising a receiver configured to receive cover type information from the cover,wherein the processor is further configured to check the cover type information about the cover and define the first and second areas according to the cover type information.(String), 14.如权利要求11所述的移动终端,还包括接收器,配置为从封面接收封面类型信息,其中,处理器还用于检查封面的封面类型信息,并根据封面类型信息定义第一区域和第二区域。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 15. The mobile terminal of claim 14, further comprising a memory configured to store the cover type information.(String), 15.如权利要求14所述的移动终端,还包括存储器,用于存储封面类型信息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 16. The mobile terminal of claim 14, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 16.如权利要求14所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 17. The mobile terminal of claim 11, wherein the window area of the cover is transparent or semi-transparent and the non-window area of the cover is opaque.(String), 17.如权利要求11所述的移动终端,其中盖板开窗区为透明或半透明,盖板非开窗区为不透明。(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 18. The mobile terminal of claim 11, wherein the processor is further configured to set different touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen.(String), 18.如权利要求11所述的移动终端,其中处理器还被配置为在触摸屏的第一区域和第二区域设置不同的触摸输入灵敏度以感测触摸输入。(String), 1(Integer), 17(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 19. The mobile terminal of claim 11, wherein the processor is further configured to set touch input sensitivities for sensing touch inputs in the first area and the second area of the touch screen according to whether the cover is closed over the touch screen.(String), 19.如权利要求11所述的移动终端,其中处理器还被配置为根据触摸屏上的盖子是否关闭来设置用于感测触摸屏的第一区域和第二区域中的触摸输入的触摸输入灵敏度。(String), 1(Integer), 18(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 20. The mobile terminal of claim 11, further comprising a battery packet disposed inside a rear surface of the mobile terminal,wherein the touch screen is formed on a front surface of the mobile terminal, andwherein the cover comprises:a battery cover unit provided on the rear surface of the mobile terminal, for protecting the battery packet; anda front cover unit connected to the battery cover unit, for covering the touch screen of the mobile terminal.(String), 20.如权利要求11所述的移动终端,还包括电池包设置在移动终端的后表面内,其中,触摸屏形成在移动终端的前表面上,并且其中,覆盖物包括:电池盖单元,设置在移动终端的背面,用于保护电池包;和前盖单元,与电池盖单元连接,用于盖住移动终端的触摸屏。(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 21. The mobile terminal of claim 11, wherein the cover comprises:a front cover unit configured to cover a front surface of the mobile terminal;a rear cover unit configured to cover a rear surface of the mobile terminal; anda connection unit configured to connect the front cover unit to the rear cover unit.(String), 21.如权利要求11所述的移动终端,其中封面包括:前盖单元,被配置为覆盖移动终端的前表面;后盖单元,被配置为覆盖移动终端的后表面;和连接单元被配置为将前盖单元连接到后盖单元。(String), 1(Integer), 20(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 22. The mobile terminal of claim 11, further comprising a magnetic force sensor configured to sense a change of an external magnetic force,wherein the processor is further configured to control the touch screen according to the change of the external magnetic force sensed by the magnetic force sensor.(String), 22.如权利要求11所述的移动终端,还包括磁力传感器,配置为感测外部磁力的变化,其中,处理器还用于根据磁力传感器感应到的外部磁力的变化控制触摸屏。(String), 1(Integer), 21(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 23. A mobile terminal comprising:a cover including a transparent or semi-transparent window area and an opaque non-window area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, for covering a touch screen of the mobile terminal;the touch screen including a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of a front cover unit of the cover; anda processor configured to:identify the first area of the touch screen corresponding to the window area of the cover of the mobile terminal and the second area of the touch screen corresponding to the non-window area of the cover by receiving information from the cover;control the touch screen to display a visual object on a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, wherein one of the visual object and another visual object are not displayed on a second area of the touch screen corresponding to a non-window area of the cover while the cover is closed over the touch screen,activate touch sensing for the second area of the touch screen while the cover is closed over the touch screen,control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the cover is closed over the touch screen.(String), 23.移动终端包括:覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域,覆盖物包括被配置为向移动终端应用多个有区别的键输入的键盘,用于覆盖移动终端的触摸屏;触摸屏包括对应于盖体的窗口区域的第一区域和对应于盖体的非窗口区域的第二区域,其中键盘包括雕刻或印刷在盖体的外表面上的多个区别键。封面的封面单元;和处理器配置为:通过接收外壳的信息识别移动终端外壳窗口区域对应的触摸屏第一区域和外壳非窗口区域对应的触摸屏第二区域;控制触摸屏在触摸屏的与移动终端的外壳的窗口区域对应的第一区域上显示视觉对象,其中在触摸的第二区域上不显示视觉对象和另一个视觉对象中的一个盖板关闭时对应于盖板非窗口区域的屏幕覆盖在触摸屏上,当盖子在触摸屏上关闭时,激活触摸屏第二区域的触摸感应,根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时盖子在触摸屏上方关闭。(String), 0(Integer), 22(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 24. The mobile terminal of claim 23, wherein the processor is further configured to receive cover type information from the cover.(String), 24.如权利要求23所述的移动终端,其中处理器还被配置为从封面接收封面类型信息。(String), 1(Integer), 23(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 25. The mobile terminal of claim 24, wherein the processor is further configured to check the cover type information and determine the first area and the second area of the touch screen according to the cover type information.(String), 25.如权利要求24所述的移动终端,其中处理器还用于检查覆盖物类型信息,并根据覆盖物类型信息确定触摸屏的第一区域和第二区域。(String), 1(Integer), 24(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 26. The mobile terminal of claim 24, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover.(String), 26.如权利要求24所述的移动终端,其中封面类型信息包括封面的窗口区域的大小和位置中的至少一项信息和封面的非窗口区域的大小和位置中的至少一项信息。(String), 1(Integer), 25(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 27. A cover for a mobile terminal, comprising:a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal; anda rear cover unit configured to cover a rear surface of the mobile terminal,wherein the front cover unit includes a transparent or semi-transparent window area and an opaque non-window area,a cover type information provider configured to provide cover type information to the mobile terminal, wherein the cover type information comprises information about at least one of a size and a position of the window area of the cover and information about at least one of a size and a position of the non-window area of the cover, andwherein the non-window area of the front cover unit includes an input area, which includes a keypad configured to apply a plurality of distinctive key inputs to the mobile terminal, and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area, wherein the keypad includes a plurality of distinctive keys that are engraved into or printed on an outer surface of the front cover unit.(String), 27.一种移动终端的外壳,包括:前盖单元被配置为覆盖形成在移动终端的前表面上的触摸屏;和后盖单元,被配置为覆盖移动终端的后表面,其中,前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域,封面类型信息提供器,被配置为向移动终端提供封面类型信息,其中,封面类型信息包括关于封面的窗口区域的大小和位置中的至少一项的信息以及关于大小和位置中的至少一项的信息。盖子的非窗口区域的位置,以及其中,前盖单元的非窗口区域包括输入区域,输入区域包括配置为向移动终端应用多个不同的键输入的小键盘,并且当前盖单元覆盖移动终端的触摸屏时,通过非窗口区域的输入区域向触摸屏施加输入,其中键盘包括雕刻到或印刷在前盖单元的外表面上的多个有区别的键。(String), 0(Integer), 26(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 28. The cover of claim 27, wherein the front cover unit comprises a magnetic force applier configured to generate a magnetic force.(String), 28.权利要求27的覆盖物,其中前盖单元包括配置成产生磁力的磁力施加器。(String), 1(Integer), 27(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 29. The cover of claim 27, wherein the input applied through the non-window area is applied in a part of the non-window area visually distinguished from another part of the non-window area.(String), 29.权利要求27的覆盖物,其中通过非窗口区域施加的输入被施加在非窗口区域的一部分中,在视觉上与非窗口区域的另一部分区别开来。(String), 1(Integer), 28(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 30. The cover of claim 27, wherein at least a part of the non-window area is formed of at least one of conductive silicon, an anti-static electric material, and silver nylon.(String), 30.权利要求27的覆盖物,其中非窗口区域的至少一部分由导电硅、抗静电材料和银尼龙中的至少一种形成。(String), 1(Integer), 29(Integer), 26(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:09.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184926(Integer), 31. An article of manufacture for processing input in a mobile terminal, comprising a non-transitory machine readable medium containing one or more programs which when executed implement the steps of:identify a first area of a touch screen corresponding to a window area of a cover of the mobile terminal and a second area of the touch screen corresponding to a non-window area of the cover by receiving information from the cover;detecting whether the cover of the mobile terminal is closed over the touch screen;activating touch sensing for the second area of the touch screen while the cover is closed over the touch screen;detecting an input in the touch screen while the cover is closed over the touch screen;determining whether the input is a first input in the first area or a second input in the second area;processing a first control command according to the first input in the first area and a second control command according to the second input in the second area,wherein the first input and the second input are of a same gesture type, andwherein the first control command and the second control command are different control command.(String), 31.一种用于处理移动终端输入的制品,包括包含一个或多个程序的非暂时性机器可读介质,这些程序在执行时执行以下步骤:通过接收来自外壳的信息识别移动终端的外壳的窗口区域对应的触摸屏的第一区域和外壳的非窗口区域对应的触摸屏的第二区域;检测触摸屏上方的移动终端盖板是否合上;当盖子关闭在触摸屏上方时,激活触摸屏的第二区域的触摸感应;在触摸屏上的盖子关闭时检测触摸屏中的输入;判断输入是第一区域中的第一输入还是第二区域中的第二输入;根据第一区域中的第一输入处理第一控制命令和根据第二区域中的第二输入处理第二控制命令,其中第一输入和第二输入是相同的手势类型,并且其中,第一控制指令与第二控制指令为不同的控制指令。(String), 0(Integer), 30(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111497(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.275 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184926(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to a Korean patent application filed in the Korean Intellectual Property Office on Feb. 11, 2014 and assigned Serial No. 10-2014-0015272, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal, and more particularly, to a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal. [0004]2. Description of the Related Art [0005]Mobile terminals such as, for example, smartphones, Personal Computers (PCs), tablets, and the like, provide various useful functions to users through many applications. [0006]Such mobile terminals are evolving to enable users to use various types of information through the various functions. [0007]In general, a cover is configured so as to cover an entire display formed on the front surface of a mobile terminal. Since the screen of the display is covered with the cover, a user may not use the display screen. SUMMARY OF THE INVENTION [0008]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal, a User Interface (UI) method in the mobile terminal, and a cover of the mobile terminal, which even though the mobile terminal is covered with the cover, enable a user to view at least a part of a display screen of the mobile terminal. [0009]Another aspect of the present invention is to provide a mobile terminal, a UI method in the mobile terminal, and a cover of the mobile terminal, which provide a window area to show a part of a display screen of the mobile terminal when the cover covers the display screen of the mobile terminal and which enable a user to identify an area of the display screen corresponding to the window area of the cover so that display on the area corresponding to the window area of the cover may be controlled in various manners. [0010]In accordance with an aspect of the present invention, a method is provided for processing input in a mobile terminal. A first area of a touch screen of the mobile terminal corresponding to a window area of the cover is defined. A second area of the touch screen of the mobile terminal corresponding to a non-window area of the cover is defined. A first input in the second area is detected while the cover is closed over the touch screen. The first input is processed as a first control command. [0011]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a touch screen and a processor. The processor is configured to define a first area of the touch screen corresponding to a window area of a cover of the mobile terminal, to define a second area of the touch screen corresponding to a non-window area of the cover, to detect a first input in the second area while the cover is closed over the touch screen, and to process the first input as a first control command. [0012]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a cover including a transparent or semi-transparent window area and an opaque non-window area, for covering a touch screen of the mobile terminal. The mobile terminal also includes a touch screen that includes a first area corresponding to the window area of the cover and a second area corresponding to the non-window area of the cover. The mobile terminal further includes a processor configured to control display of information in the first area of the touch screen according to an input to the second area of the touch screen, while the touch screen is covered with the cover. [0013]In accordance with another aspect of the present invention, a cover for a mobile terminal is provided that includes a front cover unit configured to cover a touch screen formed on a front surface of the mobile terminal. The cover also includes a rear cover unit configured to cover a rear surface of the mobile terminal. The front cover unit includes a transparent or semi-transparent window area and an opaque non-window area. The non-window area of the front cover unit includes an input area. and while the front cover unit covers the touch screen of the mobile terminal, an input is applied to the touch screen through the input area of the non-window area. [0014]In accordance with another aspect of the present invention, an article of manufacture is provided for processing input in a mobile terminal. The article of manufacture includes a machine readable medium containing one or more programs which when executed implement the steps of: defining a first area of the touch screen corresponding to a window area of a cover of the mobile terminal; defining a second area of the touch screen corresponding to a non-window area of the cover; detecting a first input in the second area while the cover is closed over the touch screen; and processing the first input as a first control command. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0016]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention; [0017]FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention; [0018]FIG. 2B is a diagram illustrating a rear surface of a cover of a mobile terminal, according to an embodiment of the present invention; [0019]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention; [0020]FIGS. 4A and 4B are diagrams illustrating configurations of a front cover unit, according to embodiments of the present invention; [0021]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention; [0022]FIG. 6 is a diagram illustrating an operation for determining whether a mobile terminal is covered with a cover, according to an embodiment of the present invention; [0023]FIG. 7 is a block diagram of a mobile terminal, according to an embodiment of the present invention; [0024]FIG. 8 is a flowchart illustrating a UI operation using a first area and a second area defined on a touch screen, respectively corresponding to a window area and a cover input area of a cover, in a mobile terminal, according to an embodiment of the present invention; [0025]FIGS. 9, 10, 11, and 12 are diagrams illustrating touch screen areas defined for various types of covers, according to embodiments of the present invention; [0026]FIG. 13 is a diagram illustrating touch inputs, according to an embodiment of the present invention; [0027]FIG. 14 is a flowchart illustrating an operation for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0028]FIGS. 15A and 15B are diagrams illustrating screens for controlling music play information using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0029]FIG. 16 is a flowchart illustrating an operation for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0030]FIG. 17 is a diagram illustrating a screen for controlling a camera preview using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0031]FIG. 18 is a flowchart illustrating an operation for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0032]FIGS. 19A, 19B, 20A, and 20B are diagrams illustrating screens for controlling a busy call using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0033]FIG. 21 is a flowchart illustrating an operation for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0034]FIGS. 22A, 22B, 23A, and 23B are diagrams illustrating screens for controlling an application using a first area and a second area defined on a touch screen in a mobile terminal, according to an embodiment of the present invention; [0035]FIGS. 24A, 24B, and 24C are diagrams illustrating a cover having a keypad formed on it according to another embodiment of the present invention; [0036]FIG. 25 is a diagram illustrating a keypad formed on a front cover unit, according to an embodiment of the present invention; [0037]FIGS. 26A, 26B, and 26C are diagrams illustrating keys formed on a front cover unit, according to an embodiment of the present invention; [0038]FIGS. 27A and 27B are diagrams illustrating a full screen and a mini screen respectively, according to an embodiment of the present invention; [0039]FIGS. 28A, 28B, 28C, 28D, and 28E are diagrams illustrating mini screens of 1st to 5th types, respectively, according to an embodiment of the present invention; [0040]FIGS. 29A, 29B, 29C, 29D, and 29E are diagrams illustrating mini screens of 6th to 10th types, according to an embodiment of the present invention; [0041]FIGS. 30A and 30B are diagrams illustrating mini screens of 11th and 12th types, according to an embodiment of the present invention; [0042]FIG. 31 is a diagram illustrating a mini screen of a 13th type, according to an embodiment of the present invention; [0043]FIGS. 32A and 32B are diagrams illustrating a method for controlling display of a mini screen, according to an embodiment of the present invention; [0044]FIGS. 33A, 33B, 33C, 34A, 34B, 34C, 34D, and 34E are diagrams illustrating operations triggered by text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0045]FIGS. 35A, 35B, 35C, 35D, and 35E are diagrams illustrating operations triggered by different types of text inputs through a keypad of a front cover unit in a mobile terminal, according to an embodiment of the present invention; [0046]FIGS. 36A, 36B, 36C, 36D, and 36E are diagrams illustrating an operation for performing a call function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0047]FIGS. 37A, 37B, and 37C are diagrams illustrating an operation for performing a message function, upon receipt of an input through a mini screen or a keypad of a front cover unit, while the front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0048]FIGS. 38A, 38B, 38C, 38D, 38E, 38F, and 38G are diagrams illustrating operations for performing various application functions, upon selection of applications on a mini screen while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention; [0049]FIGS. 39A and 39B are diagrams illustrating an application requiring a text input, according to an embodiment of the present invention; and [0050]FIGS. 40A and 40B are diagrams illustrating a cover open request message displayed while a front cover unit is closed in a mobile terminal, according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0051]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0052]The terms and words used in the following description are not limited to the meanings provided in a standard dictionary, but, are merely used to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the disclosure. [0053]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0054]Use of the term “substantially” means that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those of skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide. [0055]A mobile terminal according to various embodiments of the present invention may be embodied as an electronic device equipped with a display, such as, for example, a touch screen that can be covered with a cover. For example, the mobile terminal may be any of a video phone, a mobile phone, a smartphone, an International Mobile Telecommunication 2000 (IMT 2000) terminal, a Wideband Code Division Multiple Access (WCDMA) terminal, a Universal Mobile Telecommunication System (UMTS) terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a Digital Multimedia Broadcasting (DMB) terminal, an e-book reader, a laptop Personal Computer (PC), a tablet PC, a digital camera, and the like. [0056]FIGS. 1A and 1B are diagrams illustrating exterior perspective views of a mobile terminal engaged with a cover, according to an embodiment of the present invention. FIG. 2A is a diagram illustrating a cover of a mobile terminal, according to an embodiment of the present invention. FIG. 2B is a diagram illustrating the rear surface of a cover of a mobile terminal, according to an embodiment of the present invention. [0057]Referring to FIGS. 1A, 1B, 2A, and 2B, a mobile terminal 100 may be engaged with a cover 200. A display device that displays screens for multiple functions, for example, a touch screen 140 is provided on a front surface of the mobile terminal 100. A bezel 102 is formed around at least a part of the periphery of the touch screen 140 on the front surface of the mobile terminal 100. A home button 105, a speaker, a camera, a sensor, and the like, may be formed in the bezel 102. A battery 170 is mounted on a rear surface of the mobile terminal 100 to supply power to the mobile terminal 100. The battery 170 may be detachably formed on the rear surface of the mobile terminal 100, or may be built in the mobile terminal 100 so that a user may not remove the battery 170 from the mobile terminal 100. A rear cover unit 220 is provided on the rear surface of the mobile terminal 100. Connection ports 180 are provided on the rear surface of the mobile terminal 100, inside the rear cover unit 220, for electrical connection. The rear cover unit 220 is able to be engaged with the rear surface of the mobile terminal 100, covering the battery 170. The cover 200 is configured to cover at least a part of the front surface of the mobile terminal 100. When the cover 200 covers the front surface of the mobile terminal 100, a front cover unit 210 covers at least a part of the touch screen 140. Further, when the cover 200 covers the front surface of the mobile terminal 100, the front cover unit 210 covers at least a part of the bezel 102. When the front cover unit 210 covers at least a part of the touch screen 140, the remaining part of the touch screen 140 is exposed outwardly through a window area 201a formed in the front cover unit 210. The mobile terminal 100 may control display of content such as, for example, a clock, text, a number, a caller number, a user environment setting, or the like, in the part of the touch screen 140 exposed through the window area 201a of the front cover unit 210. [0058]The front cover unit 210 of the cover 200 may be flipped open or closed. When the front cover unit 210 of the cover 200 is opened, the entire area of the touch screen 140 of the mobile terminal 100 is exposed outward, as illustrated in FIG. 1A. If the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 of the mobile terminal 100 is covered with the front cover unit 210, as illustrated in FIG. 1B. Referring to FIG. 1B, when the front cover unit 210 of the cover 200 is closed, at least a part of the touch screen 140 corresponding to the window area 201a is exposed outward, while the remaining part of the touch screen 140 is covered. [0059]Further, when the front cover unit 210 of the cover 200 is closed, a part (for example, a speaker) formed in the bezel 102 of the mobile terminal 100 is exposed outwardly through an opening 201b formed in the front cover unit 210. While only one opening 201b is shown in FIG. 1B, a plurality of openings may be formed in the front cover unit 210 so that even though the front cover unit 210 is closed, a plurality of parts (for example, a speaker, a camera, and the like) formed in the bezel 102 may be exposed outwardly through the plurality of openings. [0060]Referring to FIGS. 2A and 2B, the cover 200 includes the front cover unit 210 and the rear cover unit 220. The cover 200 further includes a connection unit 203 interposed between the front cover unit 210 and the rear cover unit 220, for connecting the front cover unit 210 to the rear cover unit 220. The connection unit 203 may cover a part of a side surface of the mobile terminal 100. [0061]The front cover unit 210 covers the front surface of the mobile terminal 100 and includes the window area, or screen projector, 201a to expose a part of the touch screen 140. The window area 201a may be formed of a transparent or semi-transparent material or may be formed into an opening in the front cover unit 210 so that when the cover 200 covers the front surface of the mobile terminal 100, a user may view information displayed on the touch screen 140 through the window area 201a. Accordingly, the user may view information displayed on the touch screen 140 inside the front cover unit 210 through the window area 201a from outside of the front cover unit 210. Therefore, even though the front cover unit 210 is closed, the user may view short information displayed on the touch screen 140 through the window area 201a and may enter a user command through the front cover unit 210 to execute a function related to the displayed information. The rear cover unit 220 is formed as a battery cover 220a in FIG. 2B, by way of example. Referring to FIG. 2B, the rear cover unit 220 covers the rear surface of the mobile terminal 100. The rear cover unit 220 may be mounted fixedly or detachably on the rear surface of the mobile terminal 100. The front cover unit 210 may be connected to a side surface of the rear cover unit 220. The connection unit 203 may be formed between the front cover unit 210 and the rear cover unit 220. In this case, the connection unit 203 may have one side surface connected to a side surface of the rear cover unit 220 and the other side surface connected to a side surface of the front cover unit 210. The rear cover unit 220 and the front cover unit 210 may be bent upon the connection unit 203. The rear cover unit 220 is engaged with the rear surface of the mobile terminal 100. When the front cover unit 210 is flipped closed, the rear cover unit 220 surrounds at least a part of a side surface of the mobile terminal 100. Thus, the mobile terminal 100 may not slip off from the cover 200. In addition, a connector unit 202a is formed in the rear cover unit 220. The connector unit 202a provides cover type information about the cover 200. The cover type information may include information about the position of a window area and an input area formed in the front cover unit 210 of the cover 200. The connector unit 202a may provide the cover type information about the cover 200 to the mobile terminal 100 by electrically connecting to the connection ports 180 formed on the rear surface of the mobile terminal 100. For example, a plurality of connection ports 181 and 182 may be formed on the rear surface of the mobile terminal 100. The connector unit 202a of the cover 200 may be electrically engaged with at least one of the connection ports 181 and 182. The mobile terminal 100 may identify the type of the cover 200 depending on whether the connector unit 202a of the cover 200 is connected to both or one of the connection ports 181 and 182. In another example, irrespective of which connection port the connector unit 202a of the cover 200 is connected to, the mobile terminal 100 may identify the type of the cover 200. [0062]FIG. 3 is a diagram illustrating a mobile terminal and a cover, according to another embodiment of the present invention. [0063]In FIG. 3, the rear cover unit 220 is formed as a rear case 220b. Referring to FIG. 3, the cover 200 includes the front cover unit 210, the connection unit 203, and the rear case 220b. The mobile terminal 100 may be fixedly inserted in the rear case 220b. The mobile terminal 100 with a battery cover 220a engaged with its rear surface may be inserted in the rear case 220b. [0064]The rear case 220b includes a base 221, at least one sidewall 222 formed along the periphery of the base 221, and a catching portion 223. The sidewall 222 is formed substantially straight up and perpendicular from the plane of the base 221. A bottom of the sidewall 220 is connected to the base 221 and the catching portion 223 is formed in an upper end of the sidewall 222. An inner space defined by the base 221 and the sidewall 222 has a size and a shape corresponding to the size and shape of the mobile terminal 100. If the mobile terminal 100 is accommodated in the inner space, the catching portion 223 may prevent slip-off of the mobile terminal 100 from the inner space. The front cover unit 210 is connected to one side surface of the rear case 220b. The connection unit 203 may be formed between the front cover unit 210 and the rear case 220b. In this case, the connection unit 203 has one side surface connected to a side surface of the rear case 220b and the other side surface connected to a side surface of the front cover unit 210. The rear case 220b and the front cover unit 210 may be bent upon the connection unit 203. [0065]If the window area 201a and the input area 201b are formed at predetermined positions on the front cover unit 210 of the cover 200, when the cover 200 is closed, the mobile terminal 100 may display information through the window area 201a and receive a user input through the input area 201b despite having no knowledge of cover type information about the cover 200. [0066]In an embodiment of the present invention, a cover type information transmitter 224 may further be formed in the cover 200 for providing cover type information about the cover 200 to the mobile terminal 100 via short-range communication. The cover type information transmitter 224 may transmit the cover type information about the cover 200 to the mobile terminal 100 by a short-range communication scheme such as, for example, Near Field Communication (NFC), Radio Frequency Identification (RFID), Bluetooth, Wireless Fidelity (WiFi) Direct, or the like. The mobile terminal 100 may then identify the type of the cover 200 based on the cover type information received from the cover 100 by the short-range communication scheme. [0067]While it has been described above, with reference to FIG. 3, that the rear cover unit 220 of the cover 200 is configured as a case, the shapes of the rear cover unit 220 and the connection unit 203 may be changed as long as the front cover unit 210 is detachably mounted to the mobile terminal 100 and flipped open or closed. [0068]FIGS. 4A and 4B are diagrams illustrating configurations of the front cover unit, according to embodiments of the present invention. FIG. 4A illustrates the window area 201a formed of a transparent or semi-transparent material in the front cover unit 210, and FIG. 4B illustrates the window area 201a formed into a cutout opening in the front cover unit 210. [0069]Referring to FIG. 4A, the front cover unit 210 includes an outer member 211a, an inner member 212a, and a transparent member 213a. The outer member 211a, which forms an outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. An outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms an inner surface of the front cover unit 210, is engaged with a bottom surface of the transparent member 213a, while a bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. An inner hole 2121 is formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The transparent member 213a is interposed between the outer member 211a and the inner member 212a and brings the outer hole 2111 and the inner hole 212 into close contact. A first area defined at a predetermined position of the touch screen 140, for example, in an upper part of the touch screen 140 may be exposed outwardly through the transparent member 213a, the outer hole 2111, and the inner hole 2121. That is, even though the first area of the touch screen 140 is covered with the front cover unit 210, the transparent member 213a may be formed of a material containing a transparent or semi-transparent material so that the user may view information displayed in the first area of the touch screen 140 through the window area 201a. For example, the transparent member 213a may be formed of a transparent or semi-transparent film. The transparent member 213a is larger is size than the window area 201a. In FIG. 4A, the transparent member 213a is as large as the outer member 211a and the inner member 212a. The transparent member 213a may be formed of a material containing a conductive material such as, for example, conductive silicon. Further, the outer member 211a, the inner member 212a, and the transparent member 213a may be formed of a material containing at least one of an anti-static electricity material, silver, and nylon fabric. Accordingly, upon receipt of a touch input in the window area 201a from the user, the touch input may be sensed in the first area of the touch screen 140 corresponding to the window area 201a. For example, when a call is incoming, a notification indicating the call incoming is displayed at a position of the touch screen 140 corresponding to the window area 201a. If the user touches the window area 201a or manipulates a predetermined key, for example, a side key, the call may be connected immediately. [0070]Referring to FIG. 4B, the front cover unit 210 includes the outer member 211a and the inner member 212a to define the window area 201a and cover the touch screen 140, for protection. The outer member 211a, which forms the outer surface of the front cover unit 210, may be formed of a hard material having a predetermined elasticity, such as, for example, polyurethane. The outer member 211a may be formed into a shape that may cover at least a part of the front surface of the mobile terminal 100. The outer hole 2111 is formed to define the window area 201a on the outer member 211a. The inner member 212a, which forms the inner surface of the front cover unit 210, is engaged with a bottom surface of the outer member 211a, while the bottom surface of the inner member 212a directly contacts the touch screen 140. To keep the touch screen 140 scratch-free when the inner member 212a contacts the touch screen 140, the interior of the inner member 212a may be lined with a soft material, such as, for example, Chamude. The inner hole 2121 may be formed at a position of the inner member 212a corresponding to the outer hole 2111, to define the window area 201a. The outer hole 2111 and the inner hole 2121 are formed having the same size. An opening formed by the outer hole 2111 and the inner hole 2121 may form the window area 201a. Therefore, even though the first area of the touch screen 140 is covered with the front cover unit 210, the user may view information displayed on the touch screen 140 through the opening of the window area 201a. Further, the user may apply a touch input to the touch screen 140 through the window area 201a. Then the mobile terminal 100 may sense the touch input in the first area of the touch screen 140 corresponding to the window area 201a. [0071]In an embodiment of the present invention, the remaining area of the front cover unit 210, except the window area 201a, is a non-window area. At least a part of the non-window area may be defined as an input area (hereinafter, referred to as a ‘cover input area’) in which a user input may be applied. For example, the whole non-window area may be the cover input area. Or a predetermined part of the non-window area may be the cover input area. The cover input area may refer to an area in which a touch input on the outer surface of the outer member 211a can be detected by the touch screen 140, with the front cover unit 210 covering the touch screen 140. Therefore, a user gesture made in the cover input area corresponding to at least a part of the non-window area may be sensed by the touch screen 140. [0072]For example, when the user makes a user gesture in the cover input area of the front cover unit 210, the user gesture may be sensed in a second area of the touch screen 140 corresponding to the cover input area. In various embodiments of the present invention, the window area 201a of the front cover unit 210 may be formed in a first cover area of the front cover unit 210 and the non-window area may be formed in a second cover area other than the first cover area in the front cover unit 210. [0073]FIGS. 5A, 5B, 5C, and 5D are diagrams illustrating various types of covers, according to embodiments of the present invention. [0074]Referring to FIG. 5A, a window area 511 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 511, is defined as a non-window area 521 in a first-type cover, according to an embodiment of the present invention. The whole non-window area 521 may be a cover input area in the first-type cover. [0075]Referring to FIG. 5B, a window area 512 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 512, is defined as the non-window area 521 in a second-type cover, according to an embodiment of the present invention. In the second-type cover, an area of a predetermined size in the non-window area 521 under the window area 512 may be defined as a cover input area 522. In FIG. 5B, the cover input area 522 may be substantially as wide as the window area 512 along a horizontal direction and may extend up to the vicinity of the window area 512 and down to the vicinity of a bottom end of the front cover unit 210. Accordingly, for example, the cover input area 522 may occupy most of the non-window area 521 under the window area 512. [0076]Referring to FIG. 5C, a window area 513 is defined in a part of an upper portion of the front cover unit 210 and the remaining area of the front cover unit 210, except the window area 513, is defined as the non-window area 521 in a third-type cover, according to an embodiment the present invention. In the third-type cover, a small area at a center of the non-(String), 优先 [0001] 本申请根据 35 U.S.C. § 119(a) 于 2014 年 2 月 11 日向韩国知识产权局提交并转让序列号 10-2014-0015272 的韩国专利申请,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及一种移动终端,更具体地,涉及一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳。 [0004] 2.相关技术的描述 [0005] 诸如智能手机、个人计算机(PC)、平板电脑等的移动终端通过许多应用程序向用户提供各种有用的功能。 [0006] 这样的移动终端正在发展以使用户能够通过各种功能使用各种类型的信息。 [0007] 通常,盖被配置为覆盖形成在移动终端的前表面上的整个显示器。 由于显示器的屏幕被覆盖物覆盖,用户可能不使用显示屏幕。 发明内容 [0008] 做出本发明以至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面提供了一种移动终端、移动终端中的用户界面(UI)方法以及移动终端的外壳,即使移动终端被外壳覆盖,也使得用户能够查看 移动终端的显示屏的至少一部分。 [0009] 本发明的另一方面在于提供一种移动终端、移动终端中的UI方法以及移动终端的封面,当封面覆盖时,提供窗口区域以显示移动终端的显示屏幕的一部分。 移动终端的显示屏,使用户能够识别与封面的窗口区域对应的显示屏的区域,从而可以以各种方式控制在与封面的窗口区域对应的区域上的显示。 [0010] 根据本发明的一个方面,提供了一种用于在移动终端中处理输入的方法。 定义了与封面的窗口区域对应的移动终端的触摸屏的第一区域。 定义了移动终端的触摸屏上与封面的非窗口区域对应的第二区域。 当盖子在触摸屏上关闭时,检测到第二区域中的第一输入。 第一输入被处理为第一控制命令。 [0011] 根据本发明的另一方面,提供了一种包括触摸屏和处理器的移动终端。 处理器用于定义触摸屏的第一区域对应于移动终端的封面的窗口区域, 定义触摸屏的第二区域对应于封面的非窗口区域, 检测第一 合上触摸屏时在第二区域输入,并将第一输入处理为第一控制命令。 [0012] 根据本发明的另一方面,提供了一种移动终端,其包括用于覆盖移动终端的触摸屏的覆盖物,该覆盖物包括透明或半透明的窗口区域和不透明的非窗口区域。 该移动终端还包括触摸屏,该触摸屏包括与封面的窗口区域对应的第一区域和与封面的非窗口区域对应的第二区域。 移动终端还包括处理器,被配置为根据对触摸屏的第二区域的输入控制触摸屏的第一区域中的信息显示,同时触摸屏被覆盖物覆盖。 [0013]根据本发明的另一方面,提供了一种用于移动终端的盖,其包括被配置为覆盖形成在移动终端的前表面上的触摸屏的前盖单元。 盖还包括被配置为覆盖移动终端的后表面的后盖单元。 前盖单元包括透明或半透明的窗口区域和不透明的非窗口区域。 前盖单元的非窗口区域包括输入区域。 在前盖单元覆盖移动终端的触摸屏的同时,通过非窗口区域的输入区域对触摸屏进行输入。 [0014] 根据本发明的另一方面,提供了一种用于处理移动终端中的输入的制品。 所述制品包括包含一个或多个程序的机器可读介质,所述程序在执行时实现以下步骤: 定义与移动终端的封面的窗口区域相对应的触摸屏的第一区域; 定义触摸屏的第二区域,对应于盖板的非窗口区域; 当盖板合上触摸屏时,检测第二区域中的第一输入; 处理第一输入作为第一控制命令。 附图的简要说明 [0015] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0016] 图 附图说明图1A和图1B是示出了根据本发明实施例的与盖子接合的移动终端的外部透视图; [0017] 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图; [0018] 如图。 图2B是示出根据本发明实施例的移动终端机盖的背面的图; [0019] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图; [0020] 图 图4A和4B是示出根据本发明实施例的前盖单元的构造的图; [0021] 图 图5A、5B、5C和5D是示出根据本发明实施例的各种类型的盖的图; [0022] 如图。 图6是说明根据本发明的一个实施例的确定移动终端是否被覆盖物覆盖的操作的图。 [0023] 如图。 图7是根据本发明实施例的移动终端的框图; [0024] 如图。 图8是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的分别对应于封面的窗口区域和封面输入区域的第一区域和第二区域的UI操作的流程图 ; [0025] 图 图9、10、11和12是示出根据本发明实施例的为各种类型的封面定义的触摸屏区域的图; [0026] 如图。 图13是说明根据本发明的实施例的触摸输入的图; [0027] 如图。 图14是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制音乐播放信息的操作的流程图; [0028] 图 图15A和15B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制音乐播放信息的屏幕的图; [0029] 如图。 图16是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的操作的流程图; [0030] 如图。 图17是示出根据本发明实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制相机预览的屏幕的图; [0031]如图。 图18是示出根据本发明实施例的使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的操作的流程图; [0032] 图 图19A、19B、20A和20B是示出了根据本发明的实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制占线呼叫的屏幕的图; [0033] 如图。 图21是示出根据本发明的实施例的在移动终端中使用定义在触摸屏上的第一区域和第二区域来控制应用程序的操作的流程图; [0034] 图 图22A、22B、23A和23B是示出根据本发明实施例的用于使用定义在移动终端中的触摸屏上的第一区域和第二区域来控制应用的屏幕的图; [0035] 图 图24A、24B和24C是示出根据本发明另一实施例的具有形成在其上的小键盘的盖的图; [0036] 如图。 图25是示出根据本发明实施例的形成在前盖单元上的小键盘的图; [0037] 图 图26A、26B和26C是图示根据本发明实施例的形成在前盖单元上的键的图; [0038] 图 图27A和27B是分别示出了根据本发明实施例的全屏和小屏幕的图; [0039] 图 图28A、28B、28C、28D和28E是图解1的迷你屏幕的图。 st 到 5 th 分别根据本发明的一个实施例的类型; [0040] 图 图29A、29B、29C、29D和29E是图解说明6的迷你屏幕的图 th 到 10 th 类型,根据本发明的一个实施例; [0041] 图 图30A和30B是图解说明11的迷你屏幕的图 th 和 12 th 类型,根据本发明的一个实施例; [0042] 如图。 图31是说明13的小屏幕的图 th 类型,根据本发明的一个实施例; [0043] 图 图32A和32B是图示根据本发明实施例的用于控制迷你屏幕的显示的方法的图; [0044] 图 图33A、33B、33C、34A、34B、34C、34D和34E是示出根据本发明实施例的通过移动终端中的封面单元的小键盘由文本输入触发的操作的图; [0045] 图 图35A、35B、35C、35D和35E是图示根据本发明实施例的通过移动终端中的封面单元的键盘的不同类型的文本输入触发的操作的图; [0046] 图 图36A、36B、36C、36D和36E是示出在移动终端中在前盖单元关闭的同时通过前盖单元的小屏幕或键盘接收输入时执行呼叫功能的操作的图 ,根据本发明的一个实施例; [0047] 图 图37A、图37B和图37C是示出在移动终端中前盖单元关闭时,在通过前盖单元的小屏幕或键盘接收输入时执行消息功能的操作的图。 本发明的实施例; [0048] 图 图38A、图38B、图38C、图38D、​​图38E、图38F和图38G是示出根据本发明实施例的在移动终端中在前盖单元关闭的同时在迷你屏幕上选择应用时执行各种应用功能的操作的图。 本发明; [0049] 图 图39A和39B是图示根据本发明实施例的需要文本输入的应用程序的图; 和 [0050] 图 图40A和40B是示出根据本发明实施例的在移动终端中前盖单元关闭时显示的盖打开请求消息的图。 本发明实施方案的详细说明 [0051]下面结合附图对本发明实施例进行详细描述。 尽管它们在不同的附图中示出,但是相同或相似的部件可以用相同或相似的附图标记表示。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0052] 以下描述中使用的术语和词语不限于标准字典中提供的含义,而仅用于使本公开内容能够清晰一致地理解。 因此,本领域技术人员应该清楚,提供本发明实施例的以下描述仅用于说明目的,而不是用于限制本公开的目的。 [0053] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0054] 使用术语“基本上”是指不需要精确地实现所列举的特性、参数或值,而是偏差或变化,包括例如公差、测量误差、测量精度限制和本领域技术人员已知的其他因素。 该技术可能以不排除该特性旨在提供的效果的数量出现。 [0055] 根据本发明的各种实施例的移动终端可以被实施为配备有显示器的电子设备,例如,可以用盖子覆盖的触摸屏。 例如,移动终端可以是可视电话、移动电话、智能手机、国际移动电信2000(IMT 2000)终端、宽带码分多址(WCDMA)终端、通用移动电信系统(UMTS)中的任何一种。 ) 终端、个人数字助理 (PDA)、便携式多媒体播放器 (PMP)、数字多媒体广播 (DMB) 终端、电子书阅读器、膝上型个人电脑 (PC)、平板电脑、数码相机、 之类的。 [0056] 图 图1A和1B是示出根据本发明实施例的与盖接合的移动终端的外部透视图的图。 如图。 图2A是示出根据本发明实施例的移动终端的外壳的图。 如图。 图2B是图示根据本发明实施例的移动终端的盖的后表面的图。 [0057] 参考图。 参考图1A、1B、2A和2B,移动终端 100 可能与盖子接合 200 . 显示多种功能的屏幕的显示设备,例如触摸屏 140 设置在移动终端的正面 100 . 一个挡板 102 围绕触摸屏的外围的至少一部分形成 140 在移动终端的正面 100 . 一个主页按钮 105 、扬声器、照相机、传感器等可以形成在边框中 102 . 一块电池 170 安装在移动终端的背面 100 给移动终端供电 100 . 电池 170 可以可拆卸地形成在移动终端的背面 100 ,或者可以内置在移动端 100 以免用户取出电池 170 从移动终端 100 . 后盖单元 220 设置在移动终端的背面 100 . 连接端口 180 设置在移动终端的背面 100 , 后盖单元内部 220 , 用于电气连接。 后盖单元 220 能够与移动终端的背面接合 100 , 覆盖电池 170 . 封面 200 被配置为覆盖移动终端的前表面的至少一部分 100 . 当封面 200 覆盖移动终端的正面 100 , 一个前盖单元 210 至少覆盖触摸屏的一部分 140 . 此外,当封面 200覆盖移动终端的正面 100 , 前盖单元 210 至少覆盖挡板的一部分 102 . 当前盖单元 210 至少覆盖触摸屏的一部分 140 ,触摸屏的剩余部分 140 通过窗口区域向外暴露 201 a 形成在前盖单元中 210 . 移动终端 100 可以控制内容的显示,例如时钟、文本、数字、呼叫者号码、用户环境设置等,在触摸屏的部分中 140 通过窗口区域暴露 201 a 前盖单元的 210 . [0058] 前盖单元 210 封面的 200 可以翻转打开或关闭。 当前盖单元 210 封面的 200 打开时,触摸屏的整个区域 140 移动终端的 100 外露,如图所示。 1A。 如果前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 移动终端的 100 被前盖单元盖住 210 ,如图所示。 1B。 参考图。 1B、当前盖单元 210 封面的 200 关闭,至少有一部分触摸屏 140 对应窗口区域 201 a 外露,而触摸屏的其余部分 140 被覆盖。 [0059] 此外,当前盖单元 210 封面的 200 封闭,形成在边框中的一部分(例如,扬声器) 102 移动终端的 100 通过开口向外暴露 201 b 形成在前盖单元中 210 . 虽然只有一个开口 201 b 如图所示。 如图1B所示,可以在前盖单元中形成多个开口 210 这样即使前盖单元 210 封闭,在边框中形成多个部件(例如,扬声器、相机等) 102 可以通过多个开口向外暴露。 [0060] 参考图。 2A和2B,盖 200 包括前盖单元 210 和后盖单元 220 . 封面 200 还包括连接单元 203 夹在前盖单元之间 210 和后盖单元 220 , 用于连接前盖单元 210 到后盖单元 220 . 连接单元 203 可以覆盖移动终端侧面的一部分 100 . [0061] 前盖单元 210 覆盖移动终端的正面 100 并包括窗口区域或屏幕投影仪, 201 a 露出触摸屏的一部分 140 . 窗口区域 201 a 可以由透明或半透明材料形成,或者可以形成在前盖单元中的开口中 210 这样当封面 200 覆盖移动终端的正面 100 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域 201 a . 因此,用户可以查看显示在触摸屏上的信息 140 前盖单元内部 210 通过窗口区域 201 a 从前盖单元外部 210 . 因此,即使前盖单元 210 关闭时,用户可以查看触摸屏上显示的简短信息 140 通过窗口区域 201 a 并且可以通过前盖单元输入用户命令 210 执行与显示信息相关的功能。 后盖单元 220 形成为电池盖 220 a 在图 例如,图2B。 参考图。 2B、后盖单元 220 覆盖移动终端的背面 100 . 后盖单元 220 可以固定或可拆卸地安装在移动终端的背面 100 . 前盖单元 210 可以连接到后盖单元的侧表面220 . 连接单元 203 可以形成在前盖单元之间 210 和后盖单元 220 . 在这种情况下,连接单元 203 可以具有连接到后盖单元的侧表面的一个侧表面 220 另一个侧面连接到前盖单元的侧面 210 . 后盖单元 220 和前盖单元 210 可能弯曲在连接单元上 203 . 后盖单元 220 与移动终端的背面接合 100 . 当前盖单元 210 翻转关闭,后盖单元 220 包围移动终端的侧表面的至少一部分 100 . 因此,移动终端 100 不能从封面上滑落 200 . 此外,连接器单元 202 a 形成在后盖单元中 220 . 连接器单元 202 a 提供有关封面的封面类型信息 200 . 封面类型信息可以包括关于形成在前封面单元中的窗口区域和输入区域的位置的信息 210 封面的 200 . 连接器单元 202 a 可以提供关于封面的封面类型信息 200 到移动终端 100 通过电连接到连接端口 180 形成在移动终端的背面 100 . 例如,多个连接端口 181 和 182 可以形成在移动终端的背面 100 . 连接器单元 202 a 封面的 200 可以与至少一个连接端口电接合 181 和 182 . 移动终端 100 可以识别封面的类型 200 取决于连接器单元是否 202 a 封面的 200 连接到两个或一个连接端口 181 和 182 . 在另一个示例中,无论连接器单元是哪个连接端口 202 a 封面的 200 连接到移动终端 100 可以识别封面的类型 200 . [0062] 如图。 图3是示出根据本发明另一实施例的移动终端和外壳的图。 [0063] 在图。 3、后盖单元 220 形成为后壳 220 b . 参考图。 3、封面 200 包括前盖单元 210 , 连接单元 203 , 和后壳 220 b . 移动终端 100 可固定插入后壳 220 b . 移动终端 100 带电池盖 220 a 与其后表面啮合可以插入后壳 220 b. [0064] 后壳 220 b 包括一个基地 221 , 至少一个侧壁 222 沿底座周边形成 221 , 和一个捕捉部分 223 . 侧壁 222 形成为基本上笔直向上并垂直于基部的平面 221 . 侧壁的底部 220 连接到底座 221 和捕捉部分 223 形成于侧壁的上端 222 . 由底座定义的内部空间 221 和侧壁 222 具有与移动终端的大小和形状相对应的大小和形状 100 . 如果移动端 100 容纳在内部空间中的抓持部分 223 可防止移动终端滑落 100 从内部空间。 前盖单元 210 连接到后壳的一侧表面 220 b . 连接单元 203 可以形成在前盖单元之间 210 和后壳 220 b . 在这种情况下,连接单元 203 具有连接到后壳的侧面的一个侧面 220 b 另一个侧面连接到前盖单元的侧面 210 . 后壳 220 b 和前盖单元 210 可能弯曲在连接单元上 203 . [0065] 如果窗口区域 201 a 和输入区域 201 b 形成在前盖单元上的预定位置 210 封面的 200 , 当覆盖 200 关闭,移动端 100 可以通过窗口区域显示信息 201 a 并通过输入区域接收用户输入 201 b 尽管不知道关于封面的封面类型信息 200 . [0066] 在本发明的一个实施例中,一种覆盖式信息发送器 224 可以进一步形成在盖中 200 用于提供有关封面的封面类型信息 200 到移动终端 100 通过短距离通信。 盖式信息发射器 224 可以传输关于封面的封面类型信息 200 到移动终端 100 通过短距离通信方案,例如近场通信(NFC)、射频识别(RFID)、蓝牙、无线保真(WiFi) Direct等。 移动终端 100 然后可以识别封面的类型 200 基于从封面收到的封面类型信息 100 通过短距离通信方案。 [0067] 虽然上面已经描述了,但参考图1。 3、即后盖单元 220 封面的 200 配置为外壳,后盖单元的形状 220 和连接单元 203 只要前盖单元可以更改 210 可拆卸地安装在移动终端上 100 并翻转打开或关闭。 [0068] 图 图4A和4B是图示根据本发明实施例的前盖单元的配置的图。 如图。 图4A说明了窗口区域 201 a 在前盖单元中由透明或半透明材料制成 210 ,和图。 图4B图示了窗口区域 201 a 在前盖单元中形成一个切口 210 . [0069] 参考图。 4A、前盖单元 210 包括一个外部成员 211 a , 一个内部成员 212 a , 和一个透明的成员 213 a . 外部成员 211 a ,其形成前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 一个外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,其形成前盖单元的内表面 210 ,与透明构件的底面接合 213 a ,而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 一个内孔 2121 形成在内构件的位置 212 a 对应外孔 2111 , 定义窗口区域 201 a . 透明成员 213 a 夹在外构件之间 211 a 和内部成员 212 a 并带来外孔 2111 和内孔 212 密切接触。 第一区域定义在触摸屏的预定位置 140 ,例如,在触摸屏的上部 140 可以通过透明构件向外暴露 213 a , 外孔 2111 , 和内孔 2121 . 也就是说,即使触摸屏的第一个区域 140被前盖单元盖住 210 , 透明构件 213 a 可以由包含透明或半透明材料的材料形成,以便用户可以查看显示在触摸屏的第一区域中的信息 140 通过窗口区域 201 a . 例如,透明构件 213 a 可以由透明或半透明膜形成。 透明成员 213 a 大于窗口区域的大小 201 a . 在图。 4A、透明件 213 a 与外部成员一样大 211 a 和内部成员 212 a . 透明成员 213 a 可以由包含导电材料的材料形成,例如导电硅。 此外,外部构件 211 a , 内部成员 212 a , 和透明构件 213 a 可以由包含抗静电材料、银和尼龙织物中的至少一种的材料形成。 因此,当在窗口区域中接收到触摸输入时 201 a 来自用户的触摸输入可以在触摸屏的第一区域中被感测到 140 对应窗口区域 201 a . 例如,当有来电时,在触摸屏的位置显示来电的通知 140 对应窗口区域 201 a . 如果用户触摸窗口区域 201 a 或者操作预定键,例如侧键,可以立即接通通话。 [0070] 参考图。 4B、前盖单元 210 包括外部成员 211 a 和内部成员 212 a 定义窗口区域 201 a 并覆盖触摸屏 140 ,为了保护。 外部成员 211 a ,它形成了前盖单元的外表面 210 可以由具有预定弹性的硬质材料形成,例如聚氨酯。 外部成员 211 a 可以形成为可以覆盖移动终端的前表面的至少一部分的形状 100 . 外孔 2111 形成定义窗口区域 201 a 在外部成员上 211 a . 内部成员 212 a ,它形成前盖单元的内表面 210 ,与外构件的底面接合 211 a , 而内构件的底面 212 a 直接接触触摸屏 140 . 保持触摸屏 140 内部构件无划痕 212 a 接触触摸屏 140 , 内部构件的内部 212 a 可以衬有柔软的材料,例如Chamude。 内孔 2121 可以形成在内部构件的位置处 212 a 对应外孔 2111 , 定义窗口区域 201 a . 外孔 2111 和内孔 2121 形成具有相同的尺寸。 由外孔形成的开口 2111 和内孔 2121 可以形成窗口区域 201 a . 因此,即使触摸屏的第一区域 140 被前盖单元盖住 210 ,用户可以查看触摸屏上显示的信息 140 通过窗口区域的开口 201 a . 此外,用户可以将触摸输入应用到触摸屏 140 通过窗口区域 201 a . 然后是移动端 100 可以感应触摸屏第一区域的触摸输入 140 对应窗口区域 201 a. [0071] 在本发明的一个实施例中,前盖单元的剩余区域 210 , 除了窗口区域 201 a, 是非窗口区域。 非窗口区域的至少一部分可以被定义为可以应用用户输入的输入区域(以下称为“覆盖输入区域”)。 例如,整个非窗口区域可以是封面输入区域。 或者,非窗口区域的预定部分可以是封面输入区域。 覆盖输入区域可以是指在外部构件的外表面上进行触摸输入的区域 211 a 可通过触摸屏检测 140 , 带前盖单元 210 覆盖触摸屏 140 . 因此,在对应于至少部分非窗口区域的覆盖输入区域中做出的用户手势可以被触摸屏感测到 140 . [0072] 例如,当用户在封面单元的封面输入区域中做出用户手势时 210 ,可以在触摸屏的第二区域中感测到用户手势 140 对应于封面输入区域。 在本发明的各个实施例中,窗口区域 201 a 前盖单元的 210 可以形成在前盖单元的第一盖区域中 210 并且非窗口区域可以形成在前盖单元中除第一覆盖区域之外的第二覆盖区域中 210 . [0073] 图 图5A、5B、5C和5D是图示根据本发明实施例的各种类型的盖的图。 [0074] 参考图。 5A、窗口区域 511 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 511 , 定义为非窗口区域 521 在根据本发明的一个实施例的第一种盖子中。 整个非窗口区域 521 可以是第一类封面中的封面输入区域。 [0075] 参考图。 5B、窗口区域 512 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 512 , 定义为非窗口区域 521 在根据本发明的一个实施例的第二种盖中。 在第二种盖板中,非窗区域中的预定大小的区域 521 窗下区域 512 可以定义为一个覆盖输入区域 522 . 在图。 5B、覆盖输入区域 522 可以基本上与窗口区域一样宽 512 沿水平方向并可能延伸到窗口区域附近 512 并向下至前盖单元的底端附近 210 . 因此,例如,封面输入区域 522 可能占据大部分非窗口区域 521 窗下区域 512 . [0076] 参考图。 5C、窗口区域 513 被限定在前盖单元的上部的一部分中 210 和前盖单元的剩余区域 210 , 除了窗口区域 513 , 定义为非窗口区域 521 在根据本发明的一个实施例的第三种盖子中。 第三种封面中,非窗口区域中心的一小块区域 521 窗下区域 513 可以定义为一个覆盖输入区域 523 . 封面输入区 523 在第三类覆盖中小于覆盖输入区域 522 以第二类封面为例。 [0077] 参考图。 5D,一个窗口区域 514 在前盖单元的右侧部分拉长 210 沿前盖单元的长度方向 210 ,以及前盖单元的剩余区域 210 , 除了窗口区域 514 , 定义为非窗口区域 521 在根据本发明的实施例的第四类盖中。 封面输入区 524 在非窗口区域的一部分定义 521 在窗口区域的左侧 514 . [0078] 而单个窗口区域 511 , 512 , 513 , 和 514 形成在前盖单元中 210在图 参照图5A、5B、5C和5D,作为示例,可以改变窗口区域的位置或数量。 例如,窗口区域 511 , 512 , 513 , 和 514 可以设置在前盖单元的中心 210 或者可以沿水平方向拉长。 因此窗口区域的位置 511 , 512 , 513 , 和 514 可能会有所不同。 虽然已经描述了在前盖单元中定义了一个窗口区域 210 在本发明的实施例中,可以在前盖单元中定义多个窗口区域 210 ,根据本发明的各种实施例。 此外,至少一部分非窗口区域 521 可用作覆盖输入区域。 例如,整个或部分非窗口区域 521 可以定义为覆盖输入区域。 在覆盖输入区域中进行的用户手势(例如,触摸输入)的输入时,可以在触摸屏的第二区域中检测到用户手势 140 对应于封面输入区域。 [0079] 移动终端 100 可以将窗口区域与封面单元中的封面输入区域区分开来 210 ,根据上述各种类型的封面。 因此,移动端 100 可以定义触摸屏上的第一和第二区域 140 对应前盖单元的窗口区域和封面输入区域 210 , 分别。 [0080] 在本发明的各个实施例中,前盖单元 210 移动终端的 100 可能会覆盖触摸屏 140 在移动终端的正面 100 和移动终端 100 可判断是否触摸屏 140 已被前盖单元盖住 210 . [0081] 如图。 图6是示出根据本发明实施例的用于确定移动终端是否被覆盖物覆盖的操作的图。 [0082] 参考图。 6、封面 200 包括一个磁力施加器 691 , 在前盖单元的内部 210 ,提供有关封面的封面类型信息 200 . [0083] 磁力施加器 691 例如,可以是永磁体并且可以施加磁力。 磁力施加器 691 可以产生对应于封面类型信息的磁力。 [0084] 例如,如果前盖单元 210 覆盖移动终端的正面 100 , 一个传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 , 和移动终端 100 可确定前盖单元是否 210 已经覆盖了移动终端的正面 100 基于磁力传感器的传感结果 692 传感器单元 160 . 此外,当前盖单元 210 覆盖移动终端的正面 100 , 传感器单元 160 包括至少一个磁力传感器 692 可以感应从磁力施加器施加的磁力 691 对应封面类型信息,移动端 100 可以确定封面的封面类型信息 200 基于磁力传感器的传感结果 692 传感器单元 160 . [0085] 在本发明的一个实施例中,触摸屏 140 移动终端的 100 可以独立显示屏幕并感知触摸。 移动终端 100 可以激活触摸屏的显示屏 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . 或者手机端 100 可以激活触摸屏的触摸感应区域 140 完全或部分根据第一和第二区域取决于前盖单元 210 已经覆盖了触摸屏 140 . [0086] 例如,如果前盖单元 210 没有覆盖触摸屏 140 , 移动端 100 可以激活触摸屏的全屏显示 140 以及触摸屏的全触摸感应区域。 [0087] 另一方面,如果前盖单元 210 已经覆盖了触摸屏 140 , 移动端 100 可以在触摸屏的显示屏上激活第一区域的信息显示和触摸感应,仅对第二区域进行触摸感应 140 . 在这种情况下,可以在触摸屏的显示屏幕中停用除第一和第二区域之外的剩余区域 140 . [0088] 移动终端 100 可以从封面类型信息提供者那里接收封面类型信息 710 封面的 200 . 封面类型信息提供者 710 可能是连接器单元之一 202 a ,盖式信息发射器 224 , 和磁力施加器 691 . [0089] 如图。 图7是移动终端的框图 100 ,根据本发明的一个实施例。 [0090] 参考图。 7、移动端 100 包括一个控制器 110 , 一个通讯单元 120 , 一段记忆 130 , 触摸屏 140 , 和一个输入/输出 (I/O) 单元 150 . [0091] 控制器 110 包括一个中央处理器 (CPU) 111 . 控制器 110 可以包括数字信号处理器(DSP)并且可以被称为处理器。 控制器 110 包括一个只读存储器 (ROM) 112 用于存储控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 用于存储从移动终端外部接收的信号或数据 100 或用作移动终端执行操作的内存空间 100 . 中央处理器 111 可以包括一个或多个核心。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线互连。 控制器 110 可以控制通信单元 120 , 记忆 130 , 触摸屏 140 , 和 I/O 单元 150 . 例如,控制器 110 可为移动终端提供整体控制 100 并且可以控制上述组件之间的信号流。 [0092] 控制器 110 可以区分前盖单元中的窗口区域和封面输入区域 210 封面的 200 根据封面的类型 200 . 因此,控制器 110 可以在触摸屏上定义第一和第二区域 140 ,对应前盖单元的窗口区域和封面输入区域 210 . [0093] 当前盖单元 210 关闭,从而覆盖触摸屏 140 , 控制器 110 可以激活触摸屏的第一和第二区域 140 , 同时停用触摸屏的剩余区域 140 . 因此,控制器 110 可以检测到触摸屏的第一和第二区域的用户手势输入 140 通过前盖单元 210 . [0094] 控制器 110 可以控制触摸屏不同区域的不同触摸输入灵敏度的设置 140 . 例如,控制器 110 可以在触摸屏的第二区域设置更大的触摸输入灵敏度 140 比在触摸屏的第一个区域 140 . 例如,如果前盖单元 210 关闭,控制器 110 可以将触摸屏的第二区域的触摸输入灵敏度设置为大于第一区域的触摸输入灵敏度 140 . 触摸屏第一区和第二区的触摸输入灵敏度 140 可以设置为足够大以容纳触摸屏 140 检测在前盖单元上做出的用户手势 210 , 即使前盖单元 210 覆盖触摸屏 140 . [0095] 此外,控制器 110可以控制设置不同的触摸输入灵敏度,以根据前盖单元是否在触摸屏的第一和第二区域中感测触摸输入 210 覆盖触摸屏 140 . 例如,如果封面 200 不覆盖触摸屏 140 , 控制器 110 可以控制整个触摸屏上相同的触摸输入灵敏度的设置 140 . 另一方面,如果前盖单元 210 覆盖触摸屏 140 , 控制器 110 可以控制在第二区域中设置比在第一区域中更高的触摸输入灵敏度。 因此,即使当窗口区域比非窗口区域厚或窗口区域在非窗口区域关闭时打开,也可以正常感测到第二区域的触摸输入。 控制器 110 可以识别封面的类型 200 并判断前盖单元是否 210 覆盖触摸屏的显示屏 140 通过传感器单元接收封面类型信息 160 , 连接端口 180 ,或封面类型信息接收器 190 . 控制器 110 可以定义区域,例如包括对应于前盖单元的窗口区域的第一区域 210 第二区域对应于前盖单元的盖输入区域 210 , 在触摸屏上 140 根据封面类型。 例如,虽然封面 200 前盖单元的 210 覆盖触摸屏的显示屏 140 , 控制器 110 可以确定是否发生了事件。 当事件发生时,控制器 110 可在触摸屏上定义 140 ,区域包括例如第一区域对应于封面的窗口区域 200 ,例如,前盖单元 210 第二个区域对应于封面的封面输入区域 200 ,例如,前盖单元 210 . 事件可以包括预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 可能还有许多其他事件。 该事件可以是任何事件,只要它触发在显示屏幕上包括第一和第二区域的区域的定义。 [0096] 通讯单元 120 可连接移动终端 100 通过一根或多根天线连接到外部设备,并且可以与外部设备进行通信。 外部设备可以包括另一设备、便携式电话、智能手机、平板PC和服务器。 通讯单元 120 可以包括各种通信模块,例如移动通信模块、NFC模块、蓝牙模块等,并且可以通过各种通信方案例如移动通信、NFC、蓝牙等与外部设备进行通信。 喜欢。 [0097] 例如,移动终端 100 可以向便携式电话、智能手机、平板电脑或具有输入到移动终端的电话号码的其他设备发送无线信号或从其接收无线信号 100 ,用于通过移动通信模块进行语音通话、视频通话、短消息服务(SMS)或多媒体消息服务(MMS)。 此外,移动终端 100 可以通过NFC模块或蓝牙模块从外部设备接收信息。 在本发明的各个实施例中,通信单元 120 除了NFC模块和蓝牙模块之外,还可以包括无线局域网(WLAN)模块和另一短程通信模块中的至少一个,并且可以通过WLAN模块和短程通信中的至少一个接收信息 模块。 WLAN模块可以在控制器的控制下连接到互联网 110在安装了无线接入点 (AP) 的地方。 WLAN模块可以支持电气和电子工程师协会(IEEE)的WLAN标准IEEE802.11x。 短距离通信模块可以在移动终端之间进行短距离无线通信 100 和控制器控制下的外部设备 110 . 短距离通信可以符合红外数据协会(IrDA)等。 [0098] 记忆 130 可根据控制器的操作存储输入/输出信号或数据 110 , 通讯单元 120 , 触摸屏 140 , 和 I/O 单元 150 , 在控制器的控制下 110 . 记忆 130 可以存储多个用于控制移动终端的程序 100 或控制器 110 、多个应用程序以及用于执行各种功能的程序和数据。 [0099] 术语“存储器”可能包括 ROM 112 和内存 113 控制器内 110 ,或安装在移动终端上的存储卡(例如,安全数字(SD)卡、记忆棒等) 100 . 记忆 130 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)、固态驱动器(SSD)等。 [0100] 记忆 130 可以是机器可读介质(例如,计算机可读介质)。 机器可读介质可以定义为向机器提供数据以便机器可以执行特定功能的介质。 机器可读介质可以是存储介质。 记忆 130 可以包括非易失性介质和易失性介质。 所有这些媒体都应该是一种类型,可以为向机器读取命令的物理设备提供可检测的命令。 机器可读介质包括但不限于软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、光盘中的至少一种。 穿孔卡、纸带、RAM、可编程 ROM (PROM)、可擦除 PROM (EPROM) 和 Flash-EPROM。 在本发明的一个实施例中,存储器 130 可以存储封面类型信息。 [0101] 触摸屏 140 可以向用户提供各种图形用户界面(GUI)。 例如,触摸屏 140 可以通过用户的身体部位(例如,手指)或触摸输入单元接收各种手势输入,包括至少一个触摸输入或接近输入 158 (例如,一支笔)。 触摸屏 140 例如,可以实现为电阻型、电容型、电磁共振(EMR)型或它们的组合。 [0102] 在本发明的一个实施例中,触摸屏 140 可以在控制器的控制下显示应用程序的执行屏幕、消息屏幕、消息写入屏幕、消息接收屏幕等 110 . 此外,触摸屏 140 可以在显示屏的预定部分区域显示信息,例如触摸屏的第一区域 140 对应窗口区域 201 a ,而不在第一区域以外的区域显示信息。 [0103] 输入输出模块 150 包括一个按钮 152 , 麦克风 154 , 扬声器 156 , 和输入单元 158 , I/O 模块 150 不受限制。 可以提供光标控件,例如鼠标、轨迹球、操纵杆或光标方向键,用于与控制器通信 110 以及用于控制触摸屏上的光标移动 140 . [0104] 一个或多个按钮 152 可在移动终端中提供 100 并且可以向控制器提供与用户的按压相对应的各种输入信号 110 . [0105] 麦克风 154 可以接收来自各种声源的语音或声音,并在控制器的控制下将接收到的语音或声音转换为电信号 110 . [0106] 演讲者 156可以将与各种信号(例如,无线信号、广播信号、数字音频文件、数字视频文件等)对应的声音与应用程序的执行一起输出到移动终端的外部 100 在控制器的控制下 110 . [0107] 输入单元 158 可以是被配置为插入并保存在移动终端内部的设备或对象 100 ,或者单独配置。 在前一种情况下,输入单元 158 可以从移动终端中取出或插入移动终端 100 . 输入单元 158 可以是用户的手指,也可以是触控笔(以下简称笔)等输入工具,可以通过接近或触摸触摸屏来输入用户手势 140 . [0108] 移动终端 100 还可以包括传感器单元 160 . 传感器单元 160 可以包括至少一个磁力传感器 692 . 传感器单元 160 可以感应到永磁体施加的磁力 691 封面的 200 . [0109] 移动终端 100 还可以包括连接端口 180 . 连接端口 180 可以连接到连接器单元 202 a 封面的 200 . 一旦连接端口 180 连接到连接器单元 202 a , 连接端口 180 可能会收到有关封面的封面类型信息 200 从连接器单元 202 a. [0110] 移动终端 100 还可以包括封面类型信息接收器 190 . 封面式信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 . 如果覆盖类型信息接收器 190 被配置为短距离通信模块,当前盖单元 210 覆盖移动终端的正面 100 , 覆盖类型信息接收器 190 可以从封面类型信息发送器接收封面类型信息 224 , 和控制器 110 可确定前盖单元是否 210 覆盖触摸屏 140 基于从封面类型信息接收器接收的封面类型信息 190 . [0111] 如图。 图8是示出使用定义在触摸屏上的第一区域和第二区域的UI操作的流程图 140 ,分别对应封面的窗口区域和封面输入区域 200 在移动端 100 ,根据本发明的一个实施例。 [0112] 参考图。 8、移动端 100 标识封面的封面类型 200 , 在步 810 . 例如,控制器 110 移动终端的 100 可以识别封面的封面类型 200 通过感应从盖子施加的磁力 200 或通过接收有关封面的封面类型信息 200 从封面 200 . 关于封面的封面类型信息 200 可以包括关于在封面上定义的窗口区域和封面输入区域的位置信息 200 . 关于封面的封面类型信息 200 可能包括封面标识符 (ID) 和控制器 110 可以确定封面的窗口区域和封面输入区域的位置 200 使用封面 ID。 在这种情况下,关于窗口区域的位置和封面的封面输入区域的信息 200 各种封面ID可以预先存储在内存中 130 . 封面类型信息还可以包括关于封面的大小和位置中的至少一项的信息 200 以及封面的非窗口区域的位置 200 . [0113] 在步骤 820 , 控制器 110 确定触摸屏的触摸屏区域 140 包括对应于盖的窗口区域的第一区域 200 以及对应于封面的封面输入区域的第二区域 200 ,基于关于封面的封面类型信息200 . [0114] 带前盖单元 210 封面的 200 关闭,控制器 110 判断触摸屏上是否输入了用户手势 140 通过前盖单元 210 , 在步 830 . [0115] 如果在触摸屏的第二区域检测到用户手势 140 对应前盖单元的封面输入区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 在一步 840 . [0116] 如果在触摸屏的第一区域检测到用户手势 140 对应前盖单元的窗口区域 210 , 控制器 110 在移动终端中执行与检测到的用户手势对应的操作 100 , 在步 850 . [0117] 例如,使用触摸屏 140 移动终端的 100 用前盖单元盖住 210 , 控制器 110 可以判断移动终端是否发生了事件 100 并且可以在触摸屏的第一区域显示与事件对应的信息 140 对应前盖单元的窗口区域 210 . 控制器 110 根据对触摸屏的第二区域的用户手势输入执行预定操作 140 ,对应前盖单元的封面输入区域 210 . 事件可以包括例如预定按钮输入事件、接收事件和通知事件中的至少一种。 接收事件可以包括例如来电事件和消息接收事件。 通知事件可以包括例如时间警报事件、日程警报事件等。 这些事件纯粹是示范性的。 本领域技术人员可以清楚地理解,触发触摸屏第一区域显示信息的各种事件 140 在触摸屏的第二区域接收用户手势 140 可以实施。 [0118] 此外,例如,控制器 110 可以在触摸屏的显示画面中识别窗口区域对应的第一区域和覆盖输入区域对应的第二区域 140 ,基于关于封面的封面类型信息,并且可以激活第一区域作为信息显示区域和第二区域作为触摸输入区域。 这里,也可以在第一区域中感测触摸输入。 [0119] 图 图9、图10和图11是图示根据本发明实施例的用于各种类型的盖子的触摸屏区域的配置的图。 [0120] 参考图。 9、窗口区 910 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 920 , 和整个非窗口区域 920 是封面中的封面输入区域 200 ,根据本发明的一个实施例。 [0121] 在本实施例中,移动终端 100 激活第一区域 911 对应窗口区域 910 和第二个区域 921 对应非窗口区域 920 ,即触摸屏屏幕上的覆盖输入区域 140 . 可以显示信息并且可以在第一区域中感测触摸输入 911 ,而可以感测到触摸输入但信息可能不会显示在第二区域中 921 . [0122] 参考图。 10、窗口区 1010 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1020 ,以及一个覆盖输入区域 1030 在非窗口区域的一部分定义 1020 窗下区域 1010 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1011 对应窗口区域 1010 和第二个区域 1031对应覆盖输入区域 1030 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1011 ,而在第二区域中可以感测到触摸输入 1031 . 也可以在第一区域中感测到触摸输入 1011 . [0123] 参考图。 11、窗口区 1110 定义在前盖单元的上部 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1120 ,以及一个覆盖输入区域 1130 在非窗口区域的一部分定义 1120 窗下区域 1110 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1111 对应窗口区域 1110 和第二个区域 1131 对应覆盖输入区域 1130 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1111 ,而在第二区域中可以感测到触摸输入 1131 . 也可以在第一区域中感测到触摸输入 1111 . [0124] 参考图。 12、窗口区 1210 定义在前盖单元的右侧 210 , 前盖单元的剩余面积 210 被定义为非窗口区域 1220 ,以及一个覆盖输入区域 1230 在非窗口区域的一部分定义 1220 在窗口区域的左侧 1210 在封面 200 ,根据本发明的另一个实施例。 在本实施例中,移动终端 100 激活第一区域 1211 对应窗口区域 1210 和第二个区域 1231 对应覆盖输入区域 1230 在触摸屏的屏幕上 140 . 信息可能会显示在第一区域 1211 ,而在第二区域中可以感测到触摸输入 1231 . 也可以在第一区域中感测到触摸输入 1211 . [0125] 在本发明的实施例中,可以以各种方式应用触摸输入。 如图。 图13是图示根据本发明实施例的触摸输入的图。 参考图。 参照图13,触摸输入可以包括双击、向上滑动或(String), 111497(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.513 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.514 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2015216023A1(String), CN104834353A(String), CN104834353B(String), EP2905681A1(String), EP2905681B1(String), JP2017511919A(String), KR1020150094231A(String), KR102245289B1(String), US10075579B2(String), US20150229754A1(String), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), AU2015216023A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), CN104834353A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270643(Integer), CN104834353B(String), 1046908(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), EP2905681A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), EP2905681B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.713 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), JP2017511919A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), KR1020150094231A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), KR102245289B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270643(Integer), US10075579B2(String), 1046849(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), US20150229754A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270643(Integer), WO2015122661A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10075579B2(String), US10075579B2(String), 1536595200(Integer), 270643(Integer), 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:10.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 270668(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 270668(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.086 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184926(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 184926(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.191 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184926(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 184926(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:11.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184927(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.074 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.074 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\01777dfeccee408a87bbec02dbd39cb3.png(String), 184927(Integer), 01777dfeccee408a87bbec02dbd39cb3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, mobile terminal auxiliary device and method for controlling the same(String), 移动终端、移动终端辅助装置及其控制方法(String), US9749858B2(String), Methods and apparatuses are provided for controlling a mobile terminal and a mobile terminal auxiliary device. Information on at least one of the mobile terminal and the mobile terminal auxiliary device and security-related information on the at least one of the mobile terminal and the mobile terminal auxiliary device are stored. It is determined whether the mobile terminal and the mobile terminal auxiliary device exist within a predetermined available distance. If the mobile terminal and the mobile terminal auxiliary device exist within the predetermined available distance, it is determined whether the mobile terminal or the mobile terminal auxiliary device has been registered by using the stored information.(String), 提供了一种移动终端的控制方法和装置以及移动终端辅助设备。 存储关于移动终端和移动终端辅助设备至少之一的信息以及关于移动终端和移动终端辅助设备至少之一的安全相关信息。 确定移动终端和移动终端辅助设备是否存在于预定的可用距离内。 如果移动终端和移动终端辅助设备存在于预定可用距离内,则使用存储的信息判断移动终端或移动终端辅助设备是否已经注册。(String), US14/509670(String), 1412697600(Integer), US9749858B2(String), 1503936000(Integer), 1503936000(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 16(Integer), US20020111138A1 | US20080287062A1 | US20110173447A1 | US20120139879A1 | US20120206555A1 | US20120258665A1 | US20120281686A1 | US20120322376A1 | US20130143499A1 | US20130257777A1 | US20140115690A1 | US20140298672A1 | US20140378056A1 | US9154954B2 | US9179310B2 | US9398133B2(String), \20230420\01777dfeccee408a87bbec02dbd39cb3.png(String), 20(Integer), 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 1. A method for controlling a mobile terminal auxiliary device, the method comprising:storing information on at least one mobile terminal and security-related information on each of the at least one mobile terminal;determining whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal; andif the mobile terminal exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile terminal.(String), 1.一种移动终端辅助设备的控制方法,该方法包括:存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;根据移动终端发射的信号强度,判断移动终端是否存在于移动终端辅助设备的预定可用范围内;和如果移动终端在预定可用范围内,则解除移动终端的锁定状态,包括显示锁定图像。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 2. The method of claim 1, wherein determining whether the mobile terminal exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 2.如权利要求1所述的方法,其中判断移动终端是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端是否在预定可用范围内。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 3. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;receiving, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal;comparing the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 3.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;从移动终端接收关于触摸信号在移动终端的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端辅助设备的触摸信号的时间进行比较;和如果触摸时间信息与检测到移动终端辅助设备的触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 4. The method of claim 2, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal auxiliary device;transmitting, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device; andreceiving, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 4.如权利要求2所述的方法,其中检测使用信号包括:检测移动终端辅助设备的触摸信号;向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;和从移动终端接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 5. The method of claim 1, further comprising:determining whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device; andif the mobile terminal does not exist within the predetermined connection range, deleting information on the mobile terminal.(String), 5.如权利要求1所述的方法,还包括:判断移动终端是否存在于移动终端辅助设备的预定连接范围内;和如果预定连接范围内不存在移动终端,则删除移动终端上的信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 6. A method for controlling a mobile terminal, the method comprising:storing information on at least one mobile terminal auxiliary device;determining whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device; andif the mobile terminal auxiliary device exists within the predetermined available range, releasing a locked state, which includes displaying a locked image, of the mobile device.(String), 6.一种移动终端的控制方法,该方法包括:在至少一个移动终端辅助设备上存储信息;根据移动终端辅助设备发送的信号强度判断移动终端辅助设备是否存在于距移动终端预定可用范围内;和如果移动终端辅助设备存在于预定可用范围内,则解除移动设备的锁定状态,包括显示锁定图像。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 7. The method of claim 6, wherein determining whether the mobile terminal auxiliary device exists within the predetermined available range comprises:detecting a use signal of the mobile terminal auxiliary device; anddetermining whether the mobile terminal auxiliary device exists within the predetermined available range, when the use signal is detected.(String), 7.如权利要求6所述的方法,其中判断移动终端辅助设备是否存在于预定可用范围内包括:检测移动终端辅助设备的使用信号;和当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 8. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;receiving, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device;comparing the received touch time information with a time when the touch signal of the mobile terminal is detected; andif the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determining that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 8.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息;将接收到的触摸时间信息与检测到移动终端触摸信号的时间进行比较;和若触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 9. The method of claim 7, wherein detecting the use signal comprises:detecting a touch signal of the mobile terminal;transmitting, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal; andreceiving, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 9.如权利要求7所述的方法,其中检测使用信号包括:检测移动终端的触摸信号;向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息;和从移动终端辅助设备接收移动终端辅助设备是否触摸到移动终端的信息。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 10. The method of claim 6, further comprising:determining whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal; andif the mobile terminal auxiliary device does not exist within the predetermined connection range, deleting information on the mobile terminal auxiliary device.(String), 10.如权利要求6所述的方法,还包括:判断移动终端辅助设备是否存在于移动终端的预定连接范围内;和如果预定连接范围内不存在移动终端辅助设备,则删除移动终端辅助设备的信息。11、一种移动终端辅助设备包括:与至少一个移动终端通信的通信单元;存储器,存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息;和控制器,基于从移动终端发送的信号的强度确定移动终端是否存在于移动终端辅助设备的预定可用范围内,并且如果是则释放移动终端的锁定状态,包括显示锁定图像移动终端存在于预定的可用范围内。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 11. A mobile terminal auxiliary device comprising:a communication unit that communicates with at least one mobile terminal;a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal; anda controller that determines whether a mobile terminal exists within a predetermined available range from the mobile terminal auxiliary device based on an intensity of signals transmitted from the mobile terminal, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal exists within the predetermined available range.(String), 12.如权利要求11所述的装置,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端是否存在于预定可用范围内。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 12. The device of claim 11, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal exists within the predetermined available range, when the use signal is detected.(String), 13.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,从移动终端接收触摸时间信息,检测移动终端触摸信号的时间,将接收到的触摸时间信息与触摸发生的时间进行比较检测到移动终端辅助设备的信号,如果触摸时间信息与检测到移动终端辅助设备触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸设备。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 13. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, receive, from the mobile terminal, touch time information on a detection time of the touch signal at the mobile terminal, compare the received touch time information with a time when the touch signal of the mobile terminal auxiliary device is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal auxiliary device is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 14.如权利要求12所述的装置,其中控制器控制检测移动终端辅助设备的触摸信号,向移动终端发送关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,并从移动终端接收触摸时间信息移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 14. The device of claim 12, wherein the controller controls to detect a touch signal of the mobile terminal auxiliary device, transmit, to the mobile terminal, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, and receive, from the mobile terminal, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 15.如权利要求11所述的装置,其中控制器控制判断移动终端是否存在于移动终端辅助设备的预定连接范围内,如果移动终端不存在于预定连接范围内,则删除移动终端上的信息。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 15. The device of claim 11, wherein the controller controls to determine whether the mobile terminal exists within a predetermined connection range of the mobile terminal auxiliary device, and if the mobile terminal does not exist within the predetermined connection range, delete information on the mobile terminal.(String), 16.移动终端包括:通信单元,与至少一个移动终端辅助设备进行通信;存储器,存储关于至少一个移动终端辅助设备的信息;和控制器,基于从移动终端辅助设备发送的信号强度确定移动终端辅助设备是否存在于距移动终端的预定可用范围内,并释放移动终端的锁定状态,包括显示锁定图像如果移动终端辅助设备存在于预定可用范围内,则终端。(String), 1(Integer), 14(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 16. A mobile terminal comprising:a communication unit that communicates with at least one mobile terminal auxiliary device;a memory that stores information on the at least one mobile terminal auxiliary device; anda controller that determines whether a mobile terminal auxiliary device exists within a predetermined available range from the mobile terminal based on an intensity of signals transmitted from the mobile terminal auxiliary device, and releases a locked state, which includes displaying a locked image, of the mobile terminal if the mobile terminal auxiliary device exists within the predetermined available range.(String), 17.如权利要求16所述的移动终端,其中控制器控制检测移动终端辅助设备的使用信号,当检测到使用信号时,判断移动终端辅助设备是否存在于预定可用范围内。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 17. The mobile terminal of claim 16, wherein the controller controls to detect a use signal of the mobile terminal auxiliary device, and determine whether the mobile terminal auxiliary device exists within the predetermined available range when the use signal is detected.(String), 18.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,从移动终端辅助设备接收关于移动终端辅助设备的触摸信号的检测时间的触摸时间信息,将接收到的触摸时间信息与触摸时间进行比较。检测到移动终端的触摸信号,如果触摸时间信息与检测到移动终端触摸信号的时间相同,则确定移动终端辅助设备对移动终端进行了触摸。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 18. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, receive, from the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal auxiliary device, compare the received touch time information with a time when the touch signal of the mobile terminal is detected, and if the touch time information is identical to the time when the touch signal of the mobile terminal is detected, determine that the touch on the mobile terminal has been made by the mobile terminal auxiliary device.(String), 19.如权利要求17所述的移动终端,其中控制器控制检测移动终端的触摸信号,向移动终端辅助设备发送关于移动终端触摸信号的检测时间的触摸时间信息,并从移动终端辅助设备接收触摸时间信息。移动终端辅助设备是否接触到移动终端。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 19. The mobile terminal of claim 17, wherein the controller controls to detect a touch signal of the mobile terminal, transmit, to the mobile terminal auxiliary device, touch time information on a detection time of the touch signal of the mobile terminal, and receive, from the mobile terminal auxiliary device, information on whether the mobile terminal auxiliary device has touched the mobile terminal.(String), 20.如权利要求16所述的移动终端,其中控制器判断移动终端辅助设备是否存在于移动终端的预定连接范围内,如果移动终端辅助设备不存在于预定连接范围内,则控制删除关于移动终端辅助设备的信息。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184927(Integer), 20. The mobile terminal of claim 16, wherein the controller determines whether the mobile terminal auxiliary device exists within a predetermined connection range of the mobile terminal, and if the mobile terminal auxiliary device does not exist within the predetermined connection range, controls to delete information on the mobile terminal auxiliary device.(String), 1(Integer), 19(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111498(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184927(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to Korean Patent Application No. 10-2013-0119737, filed on Oct. 8, 2013, the content of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a mobile terminal and a mobile terminal auxiliary device, and more particularly, to a control method by which security related functions of the mobile terminal can be executed without an additional authentication process by registration between the mobile terminal and the mobile terminal auxiliary device. [0004]2. Description of the Related Art [0005]Terminals are classified into mobile/portable terminals and stationary terminals according to their mobility. Mobile terminals are divided into handheld terminals and vehicle mount terminals according to whether a user can carry the terminals. [0006]Terminals have been implemented with multimedia players that have multiple functions such as, for example, photographing still images or moving images, reproducing music files or movie files, playing games, receiving broadcasts, or the like. [0007]In order to support and strengthen the functions of the terminals, structures and/or software of the terminals can be improved. [0008]In addition, various terminal auxiliary devices have been used for convenient use of the terminals. Particularly, electronic pens, such as styluses, may be used as terminal auxiliary devices. [0009]The terminal and the pen are connected with each other wirelessly or using a wire, and the terminal receives a user input by using the pen. Therefore, the user can input specific texts, symbols, images, or the like more easily, accurately and faster. [0010]Pens are widely used in the terminals as accessories. Further, with the improvement of technology, the pens can transfer more precise illustrations and designs of a user to electronic devices. [0011]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0012]As shown in FIG. 1A, when a user touches specific contents such as, for example, a memo, a schedule, an email, or a diary, which are displayed in a display unit of a mobile terminal 100, by using a mobile terminal auxiliary device, such as, for example, an electronic pen 150, an operation of pre-viewing the corresponding contents may be executed. The touch of the electronic pen 150 may be performed by a proximity touch and/or a contact touch. [0013]In addition, as shown in FIG. 1B, when the mobile terminal auxiliary device, for example, the electronic pen 150, which is connected with the mobile terminal, is taken out from the mobile terminal while a screen 110 of the mobile terminal is turned off, the mobile terminal may be configured to automatically switch to a locked image 120. Here, the locked image means an image followed by a waiting image in which the mobile terminal can be used. That is, the mobile terminal may wait for instructions for releasing security, such as a password input of a user. When the user inputs the instruction for releasing security, the locked state of the mobile terminal may be released, and the mobile terminal may switch to the waiting image to thereby execute operations thereof. [0014]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device. [0015]Referring to FIG. 2A, in contents 210 such as, for example, a memo, when other people's accesses are restricted through a locking setup by a user, a preview function by the mobile terminal auxiliary device 150 of FIG. 1A may be deactivated. That is, in the case of a memo that is set to be locked, although someone touches the corresponding contents by the mobile terminal auxiliary device, the preview function may not be executed unless the password is entered by the user. [0016]In addition, as shown in FIG. 2B, although a locked image 230 is displayed by taking out the mobile terminal auxiliary device from the mobile terminal while a screen 220 of the mobile terminal is turned off, the terminal may be switched to an available state, i.e., the waiting state, only by inputting the instruction for releasing security, such as by entering the password by the user. [0017]Further, although not shown in the drawings, even while using the mobile terminal by the mobile terminal auxiliary device, for example, the electronic pen, if the mobile terminal does not continuously receive usage instruction inputs, i.e., the touch signal inputs, the screen of the mobile terminal will be turned off soon and the security function will be resumed. [0018]Furthermore, even though the user obtains the authority to access the contents or releases the locked state of the mobile terminal through the security process, if the mobile terminal is not used for a while or it is required to be turned off and then turned on, the user is required to repeat the security process. SUMMARY OF THE INVENTION [0019]The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a mobile terminal auxiliary device that may be authenticated through a security process when it is connected with a mobile terminal, so that repetition of the security process may be removed when the mobile terminal auxiliary device is required to be used afterwards, to thereby enhance the usability of the mobile terminal. [0020]Another aspect of the present invention provides convenience in using applications, which can be used only by the process of logging on or releasing a locked state by means of a mobile terminal auxiliary device. [0021]An additional aspect of the present invention prevents a screen of a mobile terminal from being turned off or a locked state from being resumed during the use of the mobile terminal, by continuously checking the use of the mobile terminal using a low power technology without an additional operation of a mobile terminal auxiliary device. [0022]A further aspect of the present invention allows, when a user wishes to use each of a plurality of mobile terminals, or authentication is required, the user to control each mobile terminal by the authenticated mobile terminal auxiliary device and use the mobile terminal without the security checking process to thereby provide convenient use thereof. [0023]Another aspect of the present invention allows each mobile terminal to identify the user through the corresponding mobile terminal auxiliary device, and a UI of the mobile terminal to be configured with specific values predefined according to the setup or user's desire. [0024]In accordance with an aspect of the present invention, a method is provided for controlling a mobile terminal auxiliary device. Information on at least one mobile terminal and security-related information on each of the at least one mobile terminal are stored. It is determined whether a mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device. If the mobile terminal exists within the predetermined available distance, it is determined whether the mobile terminal has been registered by using the stored information on the at least one mobile terminal. If the mobile terminal has been registered, security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, is transmitted to the mobile terminal. [0025]In accordance with another aspect of the present invention, a method is provided for controlling a mobile terminal. Information on at least one mobile terminal auxiliary device is stored. It is determined whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal. If the mobile terminal auxiliary device exists within the predetermined available distance, it is determined whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device. If the mobile terminal auxiliary device has been registered, predetermined security-related information is applied according to the mobile terminal auxiliary device. [0026]In accordance with another aspect of the present invention, a mobile terminal auxiliary device is provided that includes a communication unit that communicates with at least one mobile terminal, and a memory that stores information on the at least one mobile terminal and security-related information on each of the at least one mobile terminal. The mobile terminal auxiliary device also includes a controller that determines whether the mobile terminal exists within a predetermined available distance from the mobile terminal auxiliary device, determines whether the mobile terminal has been registered by using the stored information on at least one mobile terminal if the mobile terminal exists within the predetermined available distance, and controls the communication unit to transmit security-related information on the mobile terminal from the stored security-related information on each of the at least one mobile terminal, to the mobile terminal, if the mobile terminal has been registered. [0027]In accordance with another aspect of the present invention, a mobile terminal is provided that includes a communication unit that communicates with at least one mobile terminal auxiliary device, and a memory that stores information on the at least one mobile terminal auxiliary device. The mobile terminal also includes a controller that determines whether a mobile terminal auxiliary device exists within a predetermined available distance from the mobile terminal, determines whether the mobile terminal auxiliary device has been registered by using the information on the at least one mobile terminal auxiliary device if the mobile terminal auxiliary device exists within the predetermined available distance, and controls to apply predetermined security-related information according to the mobile terminal auxiliary device if the mobile terminal auxiliary device has been registered. BRIEF DESCRIPTION OF THE DRAWINGS [0028]The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: [0029]FIGS. 1A and 1B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0030]FIGS. 2A and 2B are diagrams illustrating manipulation of a mobile terminal by using a mobile terminal auxiliary device; [0031]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention; [0032]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention; [0033]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention; [0034]FIG. 6 is a flowchart illustrating the operation of a mobile terminal auxiliary device, according to an embodiment of the present invention; [0035]FIG. 7 is a flowchart illustrating the operation of a mobile terminal, according to an embodiment of the present invention; [0036]FIGS. 8A and 8B are diagrams illustrating registration between a mobile terminal and a mobile terminal auxiliary device and the operation thereof, according to an embodiment of the present invention; [0037]FIGS. 9A and 9B are diagrams illustrating an available distance, according to an embodiment of the present invention; [0038]FIG. 10 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to an embodiment of the present invention; [0039]FIG. 11 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by the mobile terminal auxiliary device, according to another embodiment of the present invention; [0040]FIG. 12 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in used by a mobile terminal, according to an embodiment of the present invention; [0041]FIG. 13 is a flowchart illustrating a determination of whether a mobile terminal auxiliary device is in use by a mobile terminal, according to another embodiment of the present invention; [0042]FIGS. 14A-14C are diagrams illustrating a determination of whether a mobile terminal auxiliary device has been used, according to an embodiment of the present invention; [0043]FIGS. 15A-15D are diagrams illustrating uses of mobile terminals and mobile terminal auxiliary devices, according to an embodiment of the present invention; [0044]FIG. 16 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal auxiliary device and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0045]FIG. 17 is a flowchart illustrating deregistration of a mobile terminal auxiliary device and a mobile terminal in a mobile terminal and use of a plurality of mobile terminals depending on a plurality of users, according to an embodiment of the present invention; [0046]FIG. 18 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to an embodiment of the present invention; and [0047]FIG. 19 is a diagram illustrating a method for managing a mobile terminal auxiliary device, according to another embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0048]Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention. [0049]Hereinafter, a mobile terminal associated with the present invention will be described in detail with reference to drawings. The suffixes of component elements used in the following descriptions, such as, a “module” and a “unit”, are assigned or used together only for ease of description, but they do not have distinguishing meanings or roles. [0050]A mobile terminal described in the embodiments of the present invention may be embodied as a portable phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation terminal, and the like. However, it is apparent to those skilled in the art that a configuration according to embodiments of the present invention are also applied to a stationary terminal such as, for example, a digital TV, a desktop computer, and the like. [0051]Mobile terminal auxiliary devices of the embodiments of the present invention may include electronic pens, such as styluses, which can communicate with a mobile terminal. In addition, it is obvious for those skilled in the art that the mobile terminal auxiliary devices of the present invention may be applied to stationary terminals such as TVs, desktop computers, or the like, as well as the mobile terminals. [0052]FIG. 3 is a block diagram illustrating a mobile terminal auxiliary device, according to an embodiment of the present invention. [0053]A mobile terminal auxiliary device 300 includes a communication unit 310, a memory 320, and a controller 330. The mobile terminal auxiliary device is not limited to the elements of FIG. 3, and it may further include other elements, or some of the elements may be omitted. For example, the mobile terminal auxiliary device 300 may further include an output unit, such as, for example, an audio output module, an alarm unit, and a display unit, and a user input unit for receiving a user input. [0054]The communication unit 310 may include at least one module enabling wireless communication between the mobile terminal auxiliary device 300 and a mobile terminal. For example, the communication unit 310 may include a short-range communication module for near field communication. Here, the short-range communication technology may adopt Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra wideband (UWB), ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a Bluetooth (BT) module and a Bluetooth low energy (BLE) module. [0055]The communication unit 310 may allow the mobile terminal auxiliary device 300 and the mobile terminal to register with each other by communicating with the mobile terminal, as described in greater detail below. [0056]The memory 320 may store programs for processing and controlling of the controller 330 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like). The memory 320 may store frequency of use for the data. [0057]The memory 320 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., a secure digital (SD) memory, an XD memory, or the like), a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a programmable ROM (PROM), a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal auxiliary device 300 may operate in relation to a web storage for providing a storage function of the memory 320 on the Internet. [0058]In general, the controller 330 controls overall operations of the mobile terminal auxiliary device 300. For example, the controller 330 may control to perform an operation of registering the mobile terminal auxiliary device 300 and the mobile terminal with each other. In addition, in the case of using the mobile terminal auxiliary device 300 through authentication between the mobile terminal and the mobile terminal auxiliary device 300, the controller 330 may control to use the mobile terminal without an additional security checking process, which is described in greater detail below. [0059]The mobile terminal auxiliary device 300 may further include a user input unit. The user input unit generates input data for controlling operations of the mobile terminal auxiliary device by a user. The user input unit may include at least one of buttons provided on the front, back, or side surface of the mobile terminal auxiliary device, touch sensors (a pressure type/a capacitive type), keypads, dome switches, jog wheels, jog switches, or the like, but it is not limited thereto. [0060]FIG. 4 is a block diagram illustrating an electronic pen, according to an embodiment of the present invention. [0061]The mobile terminal auxiliary device, according to an embodiment of the present invention, may be embodied as an electronic pen 400, such as a stylus. The electronic pen 400 includes a communication unit 410, a memory 420, a controller 430, a touch recognition unit 440, and the like, but it is not limited thereto. For example, the electronic pen 400 may further include a power supply, such as a battery 450, and the power supply may receive external power and internal power to be supplied to each element to operate under the control of the controller 430. The power supply may include at least one of connection ports, a power supply controller, and a charge monitoring unit, as well as the battery 450. [0062]The communication unit 410 may include at least one module enabling wireless communication between the electronic pen 400 and a mobile terminal. According to an embodiment of the present invention, the communication unit 410 may include at least one of a BT module or a BLE module. [0063]The communication unit 410 may allow the electronic pen 400 and the mobile terminal to be registered with respect to each other by communicating with the mobile terminal, as described in greater detail below. [0064]The memory 420 may store programs for processing and controlling of the controller 430 and perform a function of temporarily storing input/output data (e.g., information on the mobile terminal, identification information on the mobile terminal, identification information on the mobile terminal auxiliary device, security related information, or the like), as described in detail above. [0065]In general, the controller 430 controls overall operations of the electronic pen 400. For example, the controller 430 may control to perform an operation of registering the electronic pen 400 and the mobile terminal with each other. In addition, in the case of using the electronic pen 400 through authentication between the mobile terminal and the electronic pen 400, the controller 430 may control to use the mobile terminal without an additional security checking process, as described in detail below. [0066]The touch recognition unit 440 may recognize touch signals of the electronic pen 400. When the touch signal of the electronic pen 400 is input, the controller 430 controls to perform a predetermined operation according to the touch signal input. According to an embodiment of the present invention, in addition to the touch recognition unit 440, the electronic pen 400 may further include a user input unit for generating input data of a user. The user input unit may include at least one of buttons provided on the side surface of the electronic pen, a keypad, a dome switch, a jog wheel, a jog switch, or the like, but it is not limited thereto. [0067]FIG. 5 is a block diagram illustrating a mobile terminal, according to an embodiment of the present invention. [0068]A mobile terminal 500 includes a communication unit 510, a memory 520, a controller 530, a user input unit 540, and an output unit 550. The elements shown in FIG. 5 are not essential to the mobile terminal, and the mobile terminal may further include other elements, or some of the elements may be omitted. [0069]The communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and a wireless communication system, or the mobile terminal 500 and a network where the mobile terminal 500 is located. In addition, the communication unit 510 may include at least one module enabling wireless communication between the mobile terminal 500 and the mobile terminal auxiliary device. For example, the communication unit 510 may include a broadcast receiving module, a mobile communication module, a wireless Internet module, a short-range communication module, a location information module, and the like. [0070]The broadcast receiving module receives broadcast signals and/or broadcast-related information from external broadcast management servers through broadcasting channels. The broadcasting channels may include a satellite channel and a ground wave channel. At least two broadcast receiving modules may be provided in the mobile terminal 500 to concurrently receive broadcasts through at least two broadcasting channels or to switch between at least two broadcasting channels. [0071]The mobile communication module transmits and receives wireless signals to and from at least one of base stations, other terminals, and servers in mobile communication networks, such as, for example, global system for mobile communication (GSM), code division multiple access (CDMA), wideband CDMA (WCDMA) (but not limited thereto). The wireless signals may include voice call signals, video call signals, or various data according to transmission and reception of text/multimedia messages. [0072]The wireless Internet module for connecting the wireless Internet may be built in the mobile terminal 500 or externally provided. The wireless Internet may utilize the technologies of wireless LAN (WLAN), Wi-Fi, wireless broadband (Wibro), world interoperability for microwave access (Wimax), high speed downlink packet access (HSDPA), GSM, CDMA, WCDMA, long term evolution (LTE), or the like. [0073]The wireless Internet connection through Wibro, HSDPA, GSM, CDMA, WCDMA, and LTE is made by wireless mobile communication networks. Accordingly, the wireless Internet module that connects with the wireless Internet through the mobile communication networks may be regarded as a type of mobile communication module. [0074]The short-range communication module refers to a module for near field communication. The short-range communication technology may adopt BT, RFID, IrDA, UWB, ZigBee, or the like. According to an embodiment of the present invention, the short-range communication module may be at least one of a BT module and a BLE module. [0075]The user input unit 540 generates input data for controlling operations of the mobile terminal by a user. The user input unit 540 may include buttons 543 on the front, back or side surface of the mobile terminal 500, and a touch sensor (a pressure type/a capacitive type) 545. The user input unit 540 may further include keypads, dome switches, jog wheels, jog switches, or the like. [0076]The output unit 550 may generate outputs related to a sense of sight, a sense of hearing, or a sense of touch, and includes a display unit 555, but it is not limited thereto. For example, the output unit 550 may include an audio output module, an alarm module, and a haptic module. [0077]The display unit 555 displays (outputs) information processed in the mobile terminal 500. For example, when the mobile terminal 500 is in a phone call mode, the display unit 555 displays a user interface (UI) or a graphic user interface (GUI) related to the phone call. When the mobile terminal 500 is in a video call mode or photographing mode, the display unit 555 displays images, which are photographed and/or received, using the UI or the GUI. [0078]The display unit 555 may include at least one of a liquid crystal display (LCD), a thin film transistor-LCD (TFT LCD), an organic light-emitting diode (OLED), a flexible display, and a 3D display. [0079]Some of the above displays may be configured to be transparent or light-penetrable in order to view the outside therethrough, which are called transparent displays, typically, including transparent OLEDs (TOLEDs). The back structure of the display unit 555 may be also configured to be light-penetrable. According to the above structure, a user can see objects behind the terminal through the area of the display unit 555 of the terminal. [0080]Two or more display units 555 may be provided according to the type of mobile terminal 500. For example, a plurality of display units may be arranged to be spaced from each other or to be integral on the same plane, or may be disposed on different planes in the mobile terminal 500. [0081]In the case of the display unit 555 and the touch sensor 545, which are formed in a layer structure or integrally (hereinafter, referred to as a “touch screen”), the display unit 555 may be used as the input device as well as the output device. The touch sensor may be formed to be a laminate with the display unit 555 in the case of, for example, touch films, touch sheets, touch pads, or the like, or may be integrally formed with the display unit 555. [0082]The touch sensor may be configured to convert the change of pressure acting on the specific portion of the display unit 555 or the change of capacitance generating on the specific portion of the display unit 555 to electric signals. The touch sensor may be configured to detect the touch pressure as well as the touch point and the touch area. [0083]Upon a touch input on the touch sensor, the corresponding signals are transmitted to a touch controller. The touch controller processes the signals and transmits the corresponding data to the controller 530. Accordingly, the controller 530 may recognize which area of the display unit 555 has been touched. [0084]Although not shown in the drawing, a proximity sensor may be disposed inside or around the touch screen of the mobile terminal 500. The proximity sensor may detect objects approaching a predetermined detection surface, or objects around the proximity sensor, by using an electromagnetic field force or an infrared ray without mechanical contacts. The proximity sensor has a long life span and various utilization compared to a contact type sensor. [0085]The proximity sensor may include a transparent photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillating proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor an infrared proximity sensor, or the like. [0086]Hereinafter, for convenience of explanation, the term “proximity touch” may refer to an operation in which a pointer approaches the touch screen where the proximity sensor is installed to be thereby recognized without a contact, and the term “contact touch” may refer to an operation of touching of the pointer on the screen. A proximity touch point of the pointer on the touch screen may denote the point on the screen which vertically corresponds to the location of the pointer in the state of the proximity touch. Hereinafter, the term “touch” may encompass the proximity touch as well as the contact touch. [0087]According to an embodiment of the present invention, the proximity touch may include a hovering input. [0088]The proximity sensor detects the proximity touch and a proximity touch pattern (e.g., a proximity touch distance, a proximity touch direction, a proximity touch speed, a proximity touch time, a proximity touch point, a proximity touch movement state, or the like). Information corresponding to the detected proximity touch and the proximity touch pattern may be displayed on the touch screen. [0089]The memory 520 may store programs for processing and controlling of the controller 530 and perform a function of temporarily storing input/output data (e.g., a telephone number list, messages, audio, still images, moving images, information on the mobile terminal, identification information on the mobile terminal, information on the mobile terminal auxiliary device, security related information, or the like). The memory 520 may store frequency of use for the data. [0090]In addition, the memory 520 may store data on various vibrations and sounds, which are output upon the touch input on the touch screen. [0091]The memory 520 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD memory, an XD memory, or the like), a RAM, an SRAM, a ROM, an EEPROM, a PROM, a magnetic memory, a magnetic disk, and an optical disk. The mobile terminal 500 may operate in relation to a web storage for providing a storage function of the memory 520 on the Internet. [0092]The mobile terminal 500 may further include an audio/video (A/V) input unit for inputting audio signals or video signals, and a sensing unit for generating sensing signals to sense the current state of the mobile terminal 500, such as, for example, the opening/closing state of the mobile terminal 500, the location of the mobile terminal 500, contact of users, directions of the mobile terminal, and acceleration/deceleration of the mobile terminal, and to thereby control operations of the mobile terminal 500. [0093]In addition, the mobile terminal 500 may include an interface unit that plays a role of a path for all external devices connected with the mobile terminal 500. The interface unit receives data or power from the external devices and transfers the same to each element of the mobile terminal 500. The interface unit also allows data to be transmitted to the external devices from the mobile terminal 500. For example, the interface unit may include a wireless/wired headset port, an external charge port, a wireless/wired data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, or the like. [0094]In addition, the mobile terminal 500 may further include a power supply that receives external power and internal power and supplies the same to each element for operations under the control of the controller(String), 优先 [0001] 本申请根据 35 U.S.C. 要求优先权 2013 年 10 月 8 日提交的韩国专利申请号 10-2013-0119737 的 §119(a),其内容通过引用并入本文。 发明背景 [0002] 一、发明领域 [0003] [0001] 本发明总体上涉及移动终端和移动终端辅助设备,并且更具体地,涉及一种控制方法,通过该方法可以执行移动终端的安全相关功能而无需通过移动终端和移动终端之间的注册的附加认证过程 终端辅助设备。 [0004] 二、相关技术说明 [0005] 终端根据其移动性分为移动/便携终端和固定终端。 移动终端根据用户是否可以携带终端分为手持终端和车载终端。 [0006] 终端已经实现了具有多种功能的多媒体播放器,例如拍摄静止图像或运动图像、再现音乐文件或电影文件、玩游戏、接收广播等。 [0007] 为了支持和加强终端的功能,可以改进终端的结构和/或软件。 [0008] 此外,为了方便终端的使用,还使用了各种终端辅助设备。 特别地,电子笔,例如手写笔,可以用作终端辅助设备。 [0009] 终端和笔通过无线或有线方式相互连接,终端通过笔接收用户输入。 因此,用户可以更方便、更准确、更快速地输入特定的文字、符号、图像等。 [0010] 笔作为配件广泛应用于终端。 此外,随着技术的进步,笔可以将用户更精确的插图和设计转移到电子设备上。 [0011] 图1A和1B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0012] 如图1A所示,当用户触摸移动终端的显示单元中显示的特定内容,例如备忘录、日程、电子邮件或日记时 100 ,通过使用移动终端辅助设备,例如电子笔 150 ,可以执行预览相应内容的操作。 电子笔的触感 150 可以通过接近触摸和/或接触触摸来执行。 [0013] 另外,如图1B所示,当移动终端辅助设备,例如电子笔 150 ,与移动终端连接,从移动终端中取出,同时屏幕 110 关闭移动终端,移动终端可配置为自动切换到锁定图像 120 . 这里,锁定图像是指跟随有移动终端可以使用的等待图像的图像。 也就是说,移动终端可以等待解除安全的指令,例如用户的密码输入。 当用户输入解锁指令时,可以解除移动终端的锁定状态,移动终端可以切换到等待画面,从而执行其操作。 [0014] 图2A和2B是图示通过使用移动终端辅助设备来操纵移动终端的图。 [0015] 参考图2A,在内容 210 例如备忘录,当用户通过锁定设置限制他人访问时,移动终端辅助设备的预览功能 150 可以停用图1A的。 也就是说,在设置为锁定的备忘录的情况下,即使有人通过移动终端辅助设备触摸了相应的内容,也可能无法执行预览功能,除非用户输入密码。 [0016] 此外,如图 2B 所示,虽然锁定图像 230 通过从移动终端中取出移动终端辅助设备来显示,同时屏幕 220移动终端关机后,用户只需输入解除安全的指令,如输入密码,即可将终端切换到可用状态,即等待状态。 [0017] 此外,虽然未在附图中示出,但是即使在通过移动终端辅助设备例如电子笔使用移动终端时,如果移动终端没有持续接收到使用指令输入,即触摸信号输入,则屏幕 移动终端的 将很快关闭并恢复安全功能。 [0018] 进一步地,即使用户通过安全过程获得了访问内容的权限或者解除了移动终端的锁定状态,如果移动终端暂时不使用或者需要关机再开机, 用户需要重复安全过程。 发明内容 [0019] 做出本发明以至少解决上述问题和/或缺点并且提供至少下述优点。 相应地,本发明的一个方面提供了一种移动终端辅助设备,在与移动终端连接时,可以通过安全流程进行认证,从而在需要移动终端辅助设备时,可以免去重复的安全流程。 之后使用,从而提高移动终端的可用性。 [0020] 本发明的另一个方面提供了使用应用程序的便利性,仅通过移动终端辅助设备登录或解除锁定状态的过程就可以使用这些应用程序。 [0021] 本发明的另一方面通过使用低功率技术持续检查移动终端的使用而无需额外的额外的,防止移动终端的屏幕在移动终端的使用期间被关闭或锁定状态被恢复 移动终端辅助设备的操作。 [0022] 本发明的另一方面允许,当用户希望使用多个移动终端中的每一个,或者需要认证时,用户通过认证的移动终端辅助设备控制每个移动终端并且在没有安全性的情况下使用移动终端 检查过程,从而提供方便的使用。 [0023] 本发明的另一个方面允许每个移动终端通过相应的移动终端辅助设备来识别用户,并且移动终端的UI被配置有根据设置或用户期望预定义的特定值。 [0024] 根据本发明的一方面,提供了一种移动终端辅助设备的控制方法。 存储关于至少一个移动终端的信息和关于至少一个移动终端中的每一个的安全相关信息。 判断移动终端辅助设备在预定可用距离内是否存在移动终端。 如果移动终端存在于预定可用距离内,则利用存储的至少一个移动终端的信息判断移动终端是否已经注册。 如果移动终端已经注册,则从存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息被发送到移动终端。 [0025] 根据本发明的另一方面,提供了一种用于控制移动终端的方法。 存储至少一个移动终端辅助设备的信息。 判断移动终端的预定可用距离内是否存在移动终端辅助设备。 如果移动终端辅助设备存在于预定可用距离内,则通过至少一个移动终端辅助设备的信息判断移动终端辅助设备是否已经注册。 如果移动终端辅助设备已经注册,则根据移动终端辅助设备应用预定的安全相关信息。 [0026]根据本发明的另一个方面,提供了一种移动终端辅助设备,包括与至少一个移动终端通信的通信单元,以及存储关于至少一个移动终端的信息和关于移动终端的安全相关信息的存储器。 每个至少一个移动终端。 移动终端辅助设备还包括控制器,判断移动终端是否存在于距离移动终端辅助设备的预定可用距离内,如果移动终端是移动终端,则使用存储在至少一个移动终端上的信息判断移动终端是否已经注册。 终端存在于预定可用距离内,并且控制通信单元将存储的关于至少一个移动终端中的每一个的安全相关信息中的关于移动终端的安全相关信息发送到移动终端,如果移动终端具有 已注册。 [0027] 根据本发明的另一方面,提供了一种移动终端,包括与至少一个移动终端辅助设备通信的通信单元,以及存储关于至少一个移动终端辅助设备的信息的存储器。 移动终端还包括控制器,确定移动终端辅助设备是否存在于距移动终端的预定可用距离内,如果是,则使用关于至少一个移动终端辅助设备的信息确定移动终端辅助设备是否已经注册。 移动终端辅助设备存在于预定可用距离内,如果移动终端辅助设备已经注册,则根据移动终端辅助设备控制应用预定安全相关信息。 附图的简要说明 [0028] [0010] 结合附图,通过以下详细描述,本发明的上述和其他方面、特征和优点将更加明显,其中: [0029] 图1A和1B是说明通过使用移动终端辅助设备来操作移动终端的图; [0030] 图2A和2B是说明通过使用移动终端辅助设备来操作移动终端的图; [0031] 图3是示出根据本发明实施例的移动终端辅助设备的框图; [0032] 图4是示出根据本发明实施例的电子笔的框图; [0033] 图5是示出根据本发明实施例的移动终端的框图; [0034] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图; [0035] 图7是示出根据本发明实施例的移动终端的操作的流程图; [0036] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的示图; [0037] 图9A和9B是说明根据本发明实施例的可用距离的图; [0038] 图10是本发明一个实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0039] 图11是本发明另一实施例的移动终端辅助设备判断移动终端辅助设备是否在使用中的流程图。 [0040] 图12是示出根据本发明实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0041] 图13是示出根据本发明另一实施例的确定移动终端辅助设备是否正在被移动终端使用的流程图; [0042]图14A-14C是根据本发明实施例的判断移动终端辅助设备是否被使用的示意图。 [0043] 图15A-15D是图示根据本发明的实施例的移动终端和移动终端辅助设备的使用的图; [0044] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0045] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图; [0046] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图; 和 [0047] 图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 本发明实施例的详细描述 [0048] 下面结合附图详细描述本发明的实施例。 相同或相似的组件可由相同或相似的附图标记指示,尽管它们在不同的附图中示出。 可以省略本领域已知的构造或过程的详细描述以避免模糊本发明的主题。 [0049] 在下文中,将参考附图详细描述与本发明相关联的移动终端。 下文描述中所使用的组成元件的后缀,例如“模块”、“单元”,只是为了描述的方便而指定或一起使用,并不具有区分的含义或作用。 [0050] 本发明实施例中描述的移动终端可以实现为便携式电话、智能电话、膝上型计算机、数字广播终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、导航仪 终端等。 然而,对于本领域技术人员显而易见的是,根据本发明的实施例的配置也适用于固定终端,例如数字电视、台式计算机等。 [0051] 本发明实施例的移动终端辅助设备可以包括可以与移动终端通信的电子笔,例如手写笔。 另外,对于本领域技术人员来说显而易见的是,本发明的移动终端辅助装置可以应用于电视、台式电脑等固定终端,也可以应用于移动终端。 [0052] 图3是图示根据本发明实施例的移动终端辅助设备的框图。 [0053] 一种移动终端辅助设备 300 包括一个通信单元 310 , 一段记忆 320 , 和一个控制器 330 . 移动终端辅助设备不限于图3中的元件,还可以包括其他元件,或者可以省略部分元件。 例如移动端辅助设备 300 还可以包括输出单元,例如音频输出模块、警报单元和显示单元,以及用于接收用户输入的用户输入单元。 [0054] 通信单元 310 可以包括至少一个实现移动终端辅助设备之间无线通信的模块 300 和移动终端。 例如,通信单元 310可以包括用于近场通信的短程通信模块。 这里,短距离通信技术可以采用蓝牙、射频识别(RFID)、红外数据协会(IrDA)、超宽带(UWB)、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是蓝牙(BT)模块和蓝牙低功耗(BLE)模块中的至少一种。 [0055] 通信单元 310 可允许移动终端辅助设备 300 移动终端通过与移动终端通信相互注册,如下面更详细的描述。 [0056] 记忆 320 可以存储用于控制器处理和控制的程序 330 并执行暂时存储输入/输出数据(例如,移动终端信息、移动终端识别信息、移动终端辅助设备识别信息、安全相关信息等)的功能。 记忆 320 可以存储数据的使用频率。 [0057] 记忆 320 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,安全数字(SD)存储器、XD存储器等)、随机存储器的至少一种存储介质 存取存储器(RAM)、静态随机存取存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁存储器、磁盘和光盘 . 移动终端辅助设备 300 可关于网络存储操作以提供存储器的存储功能 320 在网上。 [0058] 一般来说,控制器 330 控制移动终端辅助设备的整体操作 300 . 例如,控制器 330 可以控制执行注册移动终端辅助设备的操作 300 和移动终端相互连接。 另外,在使用移动终端辅助设备的情况下 300 通过移动终端与移动终端辅助设备之间的鉴权 300 , 控制器 330 可以控制使用移动终端而无需额外的安全检查过程,这在下面更详细地描述。 [0059] 移动终端辅助设备 300 还可以包括用户输入单元。 用户输入单元生成用于控制用户对移动终端辅助设备的操作的输入数据。 用户输入单元可以包括设置在移动终端辅助设备的前表面、后表面或侧表面上的按钮、触摸传感器(压力型/电容型)、小键盘、圆顶开关、滚轮、滚轮中的至少一个 等,但不限于此。 [0060] 图4是示出根据本发明实施例的电子笔的框图。 [0061] 根据本发明实施例的移动终端辅助设备可以具体化为电子笔 400 ,例如手写笔。 电子笔 400 包括一个通信单元 410 , 一段记忆 420 , 一个控制器 430 , 一个触摸识别单元 440 等,但不限于此。 例如,电子笔 400 还可以包括电源,例如电池 450 ,电源可以接收外部电源和内部电源供应给每个元件以在控制器的控制下运行 430 . 电源可以包括连接端口、电源控制器和充电监控单元中的至少一个,以及电池 450 . [0062] 通信单元 410 可包括至少一个模块,使电子笔之间能够进行无线通信 400 和移动终端。 根据本发明的一个实施例,通信单元 410 可以包括BT模块或BLE模块中的至少一个。 [0063] 通信单元 410 可以让电子笔 400移动终端通过与移动终端通信进行相互注册,如下面更详细的描述。 [0064] 记忆 420 可以存储用于控制器处理和控制的程序 430 并执行临时存储输入/输出数据(例如,关于移动终端的信息、关于移动终端的标识信息、关于移动终端辅助设备的标识信息、安全相关信息等)的功能,如上文详细描述的 . [0065] 一般来说,控制器 430 控制电子笔的整体操作 400 . 例如,控制器 430 可控制执行注册电子笔的操作 400 和移动终端相互连接。 另外,在使用电子笔的情况下 400 通过移动终端与电子笔之间的认证 400 , 控制器 430 可以控制使用移动终端而无需额外的安全检查过程,如下面详细描述的。 [0066] 触摸识别单元 440 可以识别电子笔的触摸信号 400 . 当电子笔的触摸信号 400 是输入,控制器 430 控制根据触摸信号输入执行预定操作。 根据本发明的一个实施例,除了触摸识别单元 440 , 电子笔 400 还可以包括用于生成用户的输入数据的用户输入单元。 用户输入单元可包括设置在电子笔的侧面上的按钮、小键盘、圆顶开关、滚轮、滚轮开关等中的至少一个,但不限于此。 [0067] 图5是图示根据本发明实施例的移动终端的框图。 [0068] 移动终端 500 包括一个通信单元 510 , 一段记忆 520 , 一个控制器 530 , 一个用户输入单元 540 , 和一个输出单元 550 . 图5所示的元件不是移动终端所必需的,移动终端还可以包括其他元件,或者可以省略一些元件。 [0069] 通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 和无线通信系统,或移动终端 500 以及移动终端所在的网络 500 位于。 此外,通信单元 510 可以包括至少一个模块,使移动终端之间能够进行无线通信 500 以及移动终端辅助设备。 例如,通信单元 510 可以包括广播接收模块、移动通信模块、无线上网模块、近距离通信模块、位置信息模块等。 [0070] 广播接收模块通过广播频道从外部广播管理服务器接收广播信号和/或广播相关信息。 广播频道可以包括卫星频道和地面波频道。 移动终端中可以设置至少两个广播接收模块 500 通过至少两个广播频道同时接收广播或者在至少两个广播频道之间切换。 [0071] 移动通信模块向移动通信网络(例如全球移动通信系统(GSM)、码分多址(CDMA) )、宽带码分多址(WCDMA)(但不限于此)。 根据文本/多媒体消息的发送和接收,无线信号可以包括语音呼叫信号、视频呼叫信号或各种数据。 [0072] 移动终端中可以内置无线上网模块,用于连接无线上网 500或外部提供。 无线互联网可能利用无线局域网(WLAN)、Wi-Fi、无线宽带(Wibro)、全球微波接入互操作性(Wimax)、高速下行链路分组接入(HSDPA)、GSM、CDMA、WCDMA、长期 演进(LTE)等。 [0073] 通过 Wibro、HSDPA、GSM、CDMA、WCDMA 和 LTE 的无线互联网连接是由无线移动通信网络实现的。 因此,通过移动通信网络与无线互联网连接的无线互联网模块可以被认为是一种移动通信模块。 [0074] 近距离通信模块是指用于近场通信的模块。 短距离通信技术可以采用BT、RFID、IrDA、UWB、ZigBee等。 根据本发明的一个实施例,短距离通信模块可以是BT模块和BLE模块中的至少一种。 [0075] 用户输入单元 540 生成用于控制用户对移动终端的操作的输入数据。 用户输入单元 540 可能包括按钮 543 在移动终端的正面、背面或侧面 500 和触摸传感器(压力式/电容式) 545 . 用户输入单元 540 还可以包括小键盘、圆顶开关、滚轮、滚轮等。 [0076] 输出单元 550 可以产生与视觉、听觉或触觉相关的输出,并且包括显示单元 555 ,但不限于此。 例如,输出单元 550 可以包括音频输出模块、警报模块和触觉模块。 [0077] 显示单元 555 显示(输出)移动端处理的信息 500 . 例如,当移动端 500 处于通话模式时,显示单元 555 显示与电话呼叫相关的用户界面 (UI) 或图形用户界面 (GUI)。 当移动端 500 处于视频通话模式或拍照模式时,显示单元 555 使用 UI 或 GUI 显示拍摄和/或接收的图像。 [0078] 显示单元 555 可以包括液晶显示器(LCD)、薄膜晶体管-LCD(TFT LCD)、有机发光二极管(OLED)、柔性显示器和3D显示器中的至少一种。 [0079] 上述显示器中的一些可以被配置为透明或透光的以通过其观察外部,这被称为透明显示器,典型地包括透明有机发光二极管(TOLED)。 显示单元背面结构 555 也可以配置为透光的。 根据上述结构,用户可以通过显示单元的区域看到终端后面的物体。 555 终端。 [0080] 两个或多个显示单元 555 可根据移动终端类型提供 500 . 例如,多个显示单元可以相互间隔设置,也可以一体设置在同一平面上,也可以设置在移动终端的不同平面上。 500 . [0081] 在显示单元的情况下 555 和触摸传感器 545 ,它们以层结构或一体形成(以下称为“触摸屏”),显示单元 555 既可以作为输入设备,也可以作为输出设备。 触摸传感器可以形成为与显示单元的层压体 555 在例如触摸膜、触摸片、触摸板等的情况下,或者可以与显示单元一体形成 555 . [0082] 触摸传感器可以被配置为转换作用在显示单元的特定部分上的压力变化 555 或显示单元特定部分产生的电容变化 555 到电信号。 触摸传感器可以被配置为检测触摸压力以及触摸点和触摸面积。 [0083]在触摸传感器上有触摸输入时,相应的信号被传输到触摸控制器。 触摸控制器处理信号并将相应的数据传输给控制器 530 . 因此,控制器 530 可以识别显示单元的哪个区域 555 被感动了。 [0084] 虽然未在图中示出,但是接近传感器可以设置在移动终端的触摸屏内部或周围 500 . 接近传感器可以在没有机械接触的情况下通过使用电磁场力或红外线来检测接近预定检测表面的物体或接近传感器周围的物体。 与接触式传感器相比,接近传感器具有较长的使用寿命和多种用途。 [0085] 接近传感器可以包括透明光电传感器、直接反射光电传感器、镜面反射光电传感器、高频振荡接近传感器、电容式接近传感器、磁性接近传感器、红外接近传感器等。 [0086] 在下文中,为了便于解释,术语“接近触摸”可以指指针接近安装有接近传感器的触摸屏从而在没有接触的情况下被识别的操作,术语“接触触摸”可以指代 指针在屏幕上的触摸操作。 指针在触摸屏上的接近触摸点可以表示接近触摸状态下指针在屏幕上垂直对应的位置的点。 在下文中,术语“触摸”可以包括接近触摸以及接触触摸。 [0087] 根据本发明的实施例,接近触摸可以包括悬停输入。 [0088] 接近传感器检测接近触摸和接近触摸模式(例如,接近触摸距离、接近触摸方向、接近触摸速度、接近触摸时间、接近触摸点、接近触摸移动状态等) . 可以在触摸屏上显示与检测到的接近触摸和接近触摸模式相对应的信息。 [0089] 记忆 520 可以存储用于控制器处理和控制的程序 530 并执行临时存储输入/输出数据(例如,电话号码列表、消息、音频、静止图像、运动图像、关于移动终端的信息、关于移动终端的识别信息、关于移动终端辅助设备的信息、 安全相关信息等)。 记忆 520 可以存储数据的使用频率。 [0090] 此外,内存 520 可以存储关于在触摸屏上的触摸输入时输出的各种振动和声音的数据。 [0091] 记忆 520 可以包括闪存类型、硬盘类型、多媒体卡微型类型、卡类型存储器(例如,SD存储器、XD存储器等)、RAM、SRAM的至少一种存储介质, ROM、EEPROM、PROM、磁存储器、磁盘和光盘。 手机端 500 可关于网络存储操作以提供存储器的存储功能 520 在网上。 [0092] 手机端 500 还可以包括用于输入音频信号或视频信号的音频/视频(A/V)输入单元,以及用于产生感测信号以感测移动终端的当前状态的感测单元 500 ,例如,移动终端的打开/关闭状态 500 , 移动端的位置 500 、用户的接触、移动终端的方向、移动终端的加减速,从而控制移动终端的操作 500 . [0093] 此外,移动端 500 可以包括接口单元,该接口单元为与移动终端连接的所有外部设备起到通路的作用 500 . 接口单元从外部设备接收数据或电源,并将其传输到移动终端的每个元素 500. 接口单元还允许数据从移动终端传输到外部设备 500 . 例如,接口单元可以包括无线/有线耳机端口、外部充电端口、无线/有线数据端口、存储卡端口、用于连接具有识别模块的设备的端口、音频输入/输出端口(I /O)端口、视频I/O端口、耳机端口等。 [0094] 此外,移动端 500 还可以包括电源,其接收外部电源和内部电源并将其提供给每个元件以在控制器的控制下运行 530 . 电源可以包括例如电池、连接端口、电源控制器和充电监控单元。 [0095] 电池可以是可充电的内置型,并且可以结合到终端的主体以可拆卸地充电。 连接端口可以是外部充电器电连接到的接口之一,以便提供用于电池充电的电力。 [0096] 上述实施例可以通过使用例如软件、硬件或其组合由计算机可读或等效介质来实现。 [0097] 在硬件方面,本发明实施例可以采用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理器件(DSPD)、可编程逻辑器件(PLD)中的至少一种来实现, 现场可编程门阵列 (FPGA)、处理器、控制器、微控制器、微处理器或用于执行其他功能的电气单元。 本发明的一些实施例可以通过控制器来实现 530 . [0098] 在软件方面,本发明实施例的流程和功能可以通过单独的软件模块来实现。 每个软件模块可以执行这里描述的至少一个功能和操作。 软件代码可以由合适的程序语言编写的软件应用程序来实现。 软件代码可以存储在内存中 520 并且可以由控制器执行 530 . [0099] 图6是示出根据本发明实施例的移动终端辅助设备的操作的流程图。 [0100] 参见图6,在步骤 610 ,移动终端辅助设备的控制器控制将至少一个移动终端的信息存储在存储器中。 即,移动终端辅助设备通过移动终端辅助设备与移动终端之间的注册,存储有至少一个要使用该移动终端辅助设备的移动终端的信息。 当用户试图通过使用移动终端辅助设备连接已注册的移动终端时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0101] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0102] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行鉴权的情况下,控制移动终端辅助设备存储该信息。 移动终端。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入安全信息例如预定密码来识别用户,然后移动终端发送其自身的信息。 将自己的识别信息发送给移动终端辅助设备。 然后,移动终端辅助设备将接收到的移动终端的标识信息存储在存储器中。 [0103]移动终端的信息例如是移动终端的标识或随机生成的固有号码,但不限于此。 [0104] 根据本发明的一个实施例,移动终端辅助设备与移动终端之间的注册由单独的服务器执行。 例如,当移动终端和移动终端辅助设备通过近距离通信连接时,通过输入预定的安全信息来识别用户,然后移动终端辅助设备将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端辅助设备将移动终端的信息发送给服务器,或者移动终端将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 然后,在通过与移动终端或移动终端辅助设备的无线和有线通信使用移动终端或移动终端辅助设备的情况下,服务器发送关于这些设备是否已经注册到彼此的信息。 [0105] 根据本发明的一个实施例,在步骤 610 ,移动终端辅助设备还存储有至少一个移动终端的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端辅助设备存储移动终端设置信息以允许用户根据用户的期望设置移动终端或内容。 [0106] 返回参考图6,在步骤 620 ,移动终端辅助设备的控制器判断在预定可用距离内是否存在移动终端。 根据本发明的实施例,移动终端辅助设备通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端是否存在于预定可用距离内。 信号强度例如是接收信号强度指示符(RSSI)。 [0107] 根据本发明的一个实施例,当检测到使用移动终端辅助设备的信号时,移动终端辅助设备测量信号强度。 例如,当通过包括在移动终端辅助设备中的用户输入单元输入用户指令时,控制器确定移动终端是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0108] 如果移动终端存在于预定可用距离内,则移动终端辅助设备的控制器基于步骤中存储的至少一个移动终端的信息来判断检测到的移动终端是否为已注册的移动终端 610 . 例如,移动终端辅助设备的控制器判断是否在步骤中检测到移动终端的标识信息 620与移动终端辅助设备的存储器中存储的移动终端的标识信息相同。 可选地,控制器判断是否为随机生成的内在数,该内在数存储在步骤检测到的移动终端中 620 与随机生成的固有数相同,存储在移动终端辅助设备的内存中。 [0109] 根据本发明的一个实施例,如果检测到的移动终端是已注册的移动终端,则控制器向移动终端发送安全相关信息,步骤 640 . [0110] 图中示出了安全相关信息存储在移动终端辅助设备中,但本发明不限于此。 例如,移动终端可以在移动终端与移动终端辅助设备注册的过程中存储安全相关信息,步骤 610 . 或者,安全相关信息可以存储在服务器中。 在这种情况下,步骤 640 ,其中安全相关信息被发送到移动终端,可以被省略。 [0111] 图7是示出根据本发明实施例的移动终端的操作的流程图。 [0112] 参见图7,在步骤 710 ,移动终端的控制器控制在存储器中存储关于至少一个移动终端辅助设备的信息。 即,移动终端通过移动终端辅助设备与移动终端之间的注册,存储至少一个移动终端辅助设备的信息,该移动终端辅助设备将与移动终端进行注册。 当用户试图通过使用移动终端辅助设备与移动终端连接时,移动终端执行与用户输入对应的功能,而无需额外输入安全相关信息。 [0113] 根据本发明的一个实施例,当移动终端与移动终端辅助设备通过例如BT或BTLE模块的短距离通信首次连接时,触发相互注册的过程。 [0114] 进一步地,根据本发明的一个实施例,在利用移动终端中存储的用于用户标识的安全信息对移动终端辅助设备进行认证的情况下,控制移动终端将该信息存储在移动终端上。 终端辅助设备。 例如,当移动终端辅助设备与移动终端通过短距离通信连接时,通过输入预定密码等安全信息来识别用户,然后移动终端辅助设备发送自己的标识 信息到移动终端。 然后,移动终端将接收到的移动终端辅助设备的标识信息存储在存储器中。 [0115] 移动终端辅助设备的信息例如为移动终端辅助设备的标识或随机生成的固有编号,但不限于此。 [0116]根据本发明的一个实施例,移动终端辅助设备和移动终端之间的注册也可以由单独的服务器进行,​​如上面关于图6所描述的。例如,当移动终端和移动终端 辅助设备通过短距离通信相互连接,通过输入预定的安全信息来识别用户,然后移动终端将自己的识别信息发送给服务器。 根据本发明的一个实施例,移动终端将移动终端辅助设备的信息发送给服务器,或者移动终端辅助设备将自身的标识信息发送给服务器。 服务器存储接收到的移动终端的标识信息和移动终端辅助设备的标识信息。 此外,在通过与移动终端和移动终端辅助设备的无线和有线通信来使用移动终端或移动终端辅助设备的情况下,服务器发送关于设备是否已经相互注册的信息。 [0117] 根据本发明的一个实施例,在步骤 710 ,移动终端还存储有至少一个移动终端辅助设备的安全相关信息。 安全相关信息例如包括移动终端解除锁定状态的密码、特定应用程序解除锁定状态的密码、电子邮件、SNS等基于账户的应用程序的登录信息。 . 另外,如果特定应用被配置为仅通过移动终端中的移动终端辅助设备执行,则存储用于执行特定应用的安全信息。 例如,在使用移动终端进行支付的情况下,移动终端和移动终端辅助设备被配置为只有当使用注册的移动终端辅助设备进行支付时才批准支付。 此外,移动终端辅助设备存储用于支付的安全信息。 根据本发明的实施例,移动终端存储移动终端设置信息以允许用户根据移动终端辅助设备根据用户的期望设置移动终端或内容。 [0118] 再参考图7,在步骤 720 ,移动终端的控制器判断预定可用距离内是否存在移动终端辅助设备。 根据本发明的实施例,移动终端通过包括在通信单元中的短程通信模块测量信号强度,并基于测量的信号确定移动终端辅助设备是否存在于预定可用距离内。 信号的强度例如是RSSI。 [0119] 根据本发明的一个实施例,当检测到使用移动终端的信号时,由移动终端测量信号强度。 例如,当通过包括在移动终端中的用户输入单元输入用户指令时,控制器确定移动终端辅助设备是否存在于预定可用距离内。 通过用户输入单元的用户指令是通过诸如按钮的硬件开关输入触摸信号或选择信号。 [0120] 如果移动终端辅助设备存在于预定可用距离内,则在步骤 730 ,移动终端的控制器根据步骤中存储的至少一个移动终端辅助设备的信息,判断检测到的移动终端辅助设备是否为已注册的移动终端辅助设备 710 . 例如,移动终端的控制器判断是否在步骤中检测到移动终端辅助设备的标识信息 720与移动终端辅助设备的标识信息相同,存储在移动终端的内存中。 或者,控制器判断是否为随机生成的固有数,存储在步骤检测到的移动终端辅助设备中 720 与随机生成的固有数相同,存储在移动终端的内存中。 [0121] 在步 740 ,移动终端应用存储在步骤中的移动终端辅助设备上的安全相关信息 710 . [0122] 图中示出了安全相关信息存储在移动终端中,但本发明不限于此。 根据本发明的一个实施例,移动终端辅助设备或服务器存储移动终端辅助设备的安全相关信息。 若确定步骤中检测到的移动终端辅助设备 720 为注册的移动端辅助设备,在步骤 730 、 移动终端的通信单元接收来自移动终端辅助设备或服务器的安全相关信息。 移动终端的控制器应用接收到的安全相关信息。 [0123] 图8A和8B是图示根据本发明实施例的移动终端和移动终端辅助设备之间的注册及其操作的图。 图9A和9B是图示根据本发明实施例的可用距离的图。 [0124] 参考图8A,移动终端之间的注册 800 以及移动终端辅助设备 850 被处理。 根据本发明的一个实施例,移动终端辅助设备 850 具体表现为电子笔,包括手写笔。 [0125] 移动端之间的注册 800 以及移动终端辅助设备 850 移动端通信时触发 800 以及移动终端辅助设备 850 首次制作,例如,通过 BT 或 BTLE 模块的短距离通信。 [0126] 根据本发明的一个实施例,移动终端之间的注册过程 800 以及移动终端辅助设备 850 执行,当注册移动终端辅助设备的消息 850 输入到移动端 800 . 注册移动终端辅助设备的消息以弹窗形式显示,但不限于此,消息可以为移动终端按键输入的形式。 [0127] 移动端之间的注册流程 800 以及移动终端辅助设备 850 执行,当移动终端辅助设备通过移动终端认证时 800 通过安全信息对用户进行标识,如图8A所示。 例如,当在移动终端中输入预定密码或特定图案时 800 , 移动端之间的注册 800 以及移动终端辅助设备 850 被处理。 [0128] 移动端之间注册时 800 以及移动终端辅助设备 850 处理完毕,移动端 800 在移动终端辅助设备上存储信息 850 . 移动端 800 接收移动终端的标识信息 800 从移动端辅助设备 850 通过通信单元。 另外,根据本发明的一个实施例,移动终端辅助设备 850 在移动端存储信息 800 . 移动终端辅助设备 850 接收移动终端辅助设备的识别信息 850 从移动端 800 通过通信单元。 或者,根据本发明的一个实施例,移动终端 800以及移动终端辅助设备 850 存储随机生成的相同内在数。 [0129] 根据本发明的一个实施例,移动终端和移动终端辅助设备之间的注册是由单独的服务器进行的,这在上面参考图6和图7进行了详细描述。 [0130] 存储的信息包括移动终端的安全相关信息 800 或移动终端辅助设备 850 . 即该信息中包含解除移动终端锁定状态的密码 800 或移动终端辅助设备 850 、特定应用程序的密码以及电子邮件和 SNS 的登录信息。 例如,当多个移动终端辅助设备 850 已注册到移动终端 800 , 移动端 800 对已注册的移动终端辅助设备的使用进行不同的限制 850 . 即移动端 800 不允许第一移动终端辅助设备访问特定应用,而允许第二移动终端辅助设备访问所有应用。 当第一移动终端辅助设备注册到移动终端时,存储用于限制第一移动终端辅助设备访问特定应用的安全信息。 进一步地,当第二移动终端辅助设备注册到移动终端时,存储允许第二移动终端辅助设备访问所有应用的安全信息。 [0131] 如图8B所示,如果移动终端 800 以及移动终端辅助设备 850 位于预定的可用距离内 870 , 它们可能相互关联。 [0132] 根据本发明的一个实施例,移动终端 800 以及移动终端辅助设备 850 通过通信单元中包含的短距离通信模块测量信号强度,判断移动终端是否 800 以及移动终端辅助设备 850 存在于预定可用距离内 870 基于测量的信号。 测量信号强度,当移动终端辅助设备有信号使用时 850 或移动端 800 根据本发明的实施例,检测到。 [0133] 如图9A所示,移动终端 900 测量移动终端辅助设备的通信信号强度 950 . RSSI 是通过短距离通信模块测量的。 根据本发明的一个实施例,它被配置为即使移动终端 900 以及移动终端辅助设备 950 存在于连接距离内 980 他们之间可以通过短距离通信进行通信,只有当移动终端时,他们才能真正相互连接 900 以及移动终端辅助设备 950 存在于预定的可用距离内 970 . 因此,第二个连接装置 960 无法与移动端连接 900 . [0134] 如图9B所示,由于信号强度根据与移动终端的距离而降低 900 , 判断移动终端辅助设备是否 950 存在于预定可用距离内 970 从移动端 900 通过测量信号的强度。 [0135] 如移动端辅助设备 950 存在于可用距离之外 980 , 移动端 900 以及移动终端辅助设备 950 完全断开连接。 根据本发明实施例,确定移动终端辅助设备 950 丢失,如下面更详细的描述。 [0136] 回到图8B,如果移动终端 800以及移动终端辅助设备 850 存在于预定可用距离内 870 , 移动端 800 以及移动终端辅助设备 850 确定它们是否已经相对于彼此注册,如上文关于图6和图7所述。 [0137] 如果确定移动端 800 以及移动终端辅助设备 850 已经相互注册,移动端 800 基于移动终端上的安全相关信息使用 800 或移动终端辅助设备 850 . [0138] 图10是示出根据本发明实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0139] 根据本发明的一个实施例,移动终端辅助设备体现为包括触摸传感器的电子笔。 在移动终端与移动终端辅助设备接触的情况下,确定移动终端和移动终端辅助设备正在使用中。 [0140] 即使移动终端辅助设备输入了触摸信号,移动终端辅助设备的控制器也无法判断移动终端辅助设备触摸了哪个物体。 也就是说,即使移动终端辅助设备在移动终端以外的物体上进行触摸,然后通过触摸输入单元输入触摸信号,移动终端辅助设备也不能识别物体,而是感应到触摸信号。 只要。 [0141] 同样,当移动终端接收到包括触摸传感器的触摸屏上的触摸信号时,移动终端无法确定是哪个物体触摸了触摸屏。 也就是说,即使是移动终端的触摸屏上的触摸信号,也可能是移动终端辅助设备以外的其他指针,例如手指输入的触摸信号。 在这种情况下,移动终端仅确定触摸点,而不能确定哪个物体产生触摸信号。 [0142] 相应地,为了判断移动终端辅助设备是否被使用,需要预先判断移动终端上的触摸是否是由移动终端辅助设备进行的。 [0143] 参见图10,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1010 . 控制器提取关于触摸信号的检测的时间信息。 [0144] 在步 1020 ,移动终端辅助设备从移动终端接收移动终端检测到触摸信号的时间的触摸时间信息。 即,当触摸信号也输入到移动终端时,移动终端将输入触摸信号的时间信息发送给移动终端辅助设备,移动终端辅助设备接收该信息。 [0145] 在步 1030 ,移动终端辅助设备比较步骤中接收到的移动终端检测到的触摸信号的时间信息 1020 ,带有step的移动终端辅助设备中检测到触摸信号的时间信息 1010 . 即,移动终端辅助设备判断触摸信号在移动终端辅助设备中的输入时间与触摸信号在移动终端中的输入时间是否相同。 [0146] 如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间不同,则确定输入到移动终端辅助设备的触摸信号是触摸产生的,而不是触摸产生的。 移动终端,而是其他带有移动终端辅助设备的对象。 [0147]如果移动终端辅助设备中触摸信号的输入时间与移动终端中触摸信号的输入时间相同,则控制器确定移动终端辅助设备触摸到移动终端,进而移动终端。 辅助设备正在使用中。 [0148] 此外,虽然未在图中示出,但是根据本发明的实施例,移动终端辅助设备将确定结果发送到移动终端。 [0149] 图11是示出根据本发明另一实施例的移动终端辅助设备确定移动终端辅助设备是否在使用中的流程图。 [0150] 参见图11,移动终端辅助设备检测移动终端辅助设备的触摸信号,步骤 1110 . 控制器提取关于触摸信号检测的时间信息。 [0151] 在步 1120 ,移动终端辅助设备将检测到触摸信号的时间信息发送给移动终端。 另外,移动终端辅助设备从移动终端接收移动终端辅助设备是否触摸移动终端的信息,步骤 1130 . [0152] 在图11的实施例中,与图10的实施例不同的是,移动终端判断移动终端辅助设备是否被使用过。 另外,移动终端用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端辅助设备。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端被配置为不向移动终端辅助设备发送单独的响应信号。 [0153] 移动终端辅助设备在步骤中利用接收到的信息判断移动终端辅助设备是否已经针对移动终端使用过 1130 . [0154] 图12是示出根据本发明实施例的确定移动终端辅助设备是否被移动终端使用的流程图。 [0155] 参见图12,移动终端检测针对移动终端的触摸信号,步骤 1210 . 控制器提取关于触摸信号的检测的时间信息。 [0156] 在步 1220 ,移动终端从移动终端辅助设备接收到移动终端辅助设备检测到触摸信号的时间信息。 即,当移动终端辅助设备也输入了触摸信号时,移动终端辅助设备向移动终端发送触摸信号输入时间的信息,移动终端接收该信息。 [0157] 在步 1230 ,移动终端比对步骤中接收到的移动终端辅助设备检测到的触摸信号的时间信息 1220 , 与检测移动终端辅助设备触摸信号的时间信息同步 1210 . 即移动终端可以判断触摸信号在移动终端中的输入时间与触摸信号在移动终端辅助设备中的输入时间是否相同。 [0158] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间不同,则确定移动终端辅助设备中的触摸信号是触摸产生的,而不是移动终端产生的。 终端,而是与移动终端辅助设备的其他对象。 [0159] 如果移动终端中触摸信号的输入时间与移动终端辅助设备中触摸信号的输入时间相同,则移动终端的控制器确定移动终端辅助设备触摸了移动终端, 步骤 1240,则该移动终端辅助设备正在使用中。 [0160] 此外,根据本发明的实施例,移动终端将确定结果发送到移动终端辅助设备。 [0161] 图13是示出根据本发明另一实施例的确定移动终端是否辅助移动终端的流程图。 [0162] 参见图13,移动终端检测移动终端的触摸信号,步骤 1310 . 此时,控制器提取触摸信号检测的时间信息。 [0163] 在步 1320 ,移动终端将检测到触摸信号的时间信息发送给移动终端辅助设备。 另外,移动终端从移动终端辅助设备接收移动终端辅助设备是否触摸了移动终端的信息,步骤 1330 . [0164] 在图13的实施例中,与图12的实施例不同的是,移动终端辅助设备判断移动终端辅助设备是否被使用过。 另外,移动终端辅助设备用于将移动终端辅助设备是否在移动终端上被触摸的信息发送给移动终端。 根据本发明的一个实施例,当确定移动终端辅助设备没有在移动终端上进行触摸时,移动终端辅助设备被配置为不向移动终端发送单独的响应信号。 [0165] 移动终端利用接收到的信息判断移动终端辅助设备是否针对移动终端使用过, 1330 . [0166] 图14A-14C是图示根据本发明实施例的确定移动终端辅助设备是否已经被使用的图。 [0167] 参见图14A,移动终端辅助设备 1450 移动终端屏幕进入预定可用距离内 1400 被关闭。 移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于预定的可用距离内。 比如移动端 1400 通过与移动终端辅助设备的近距离通信测量RSSI 1450 , 判断移动端辅助设备是否 1450 基于信号的测量强度,存在于预定可用距离内。 [0168] 即使是移动端 1400 以及移动终端辅助设备 1450 存在于预定的可用距离内,根据本发明的一个实施例,移动终端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 仅当移动终端辅助设备存在于预定可用距离内时 1450 正在使用中。 [0169] 如图14B所示,根据参考图10至图13描述的方法确定移动终端辅助设备的使用。 [0170] 例如,当移动终端辅助设备 1450 触摸移动终端 1400 , 移动端辅助设备 1450 检测触摸信号。 移动终端辅助设备 1450 提取触摸信号检测的时间信息。 此外,移动终端 1400 还提取移动终端辅助设备触摸时检测到触摸信号的时间信息 1450 . [0171] 移动终端辅助设备 1450 传输检测到移动终端辅助设备触摸信号的信​​息 1450 到手机端 1400. 或者,根据本发明的一个实施例,移动终端 1400 传输检测到移动终端触摸信号的信​​息 1400 到移动端辅助设备 1450 . [0172] 手机端 1400 比较触摸信号输入到移动终端辅助设备的时间 1450 ,从移动终端辅助设备接收 1450 , 随着触摸信号输入到移动端的时间 1400 . 或者,根据本发明的一个实施例,移动终端辅助设备 1450 比较触摸信号输入到移动端的时间 1400 , 从移动端接收 1400 , 随着触摸信号输入到移动终端辅助设备的时间 1450 . [0173] 如果触摸信号输入到移动终端 1400 以及移动终端辅助设备 1450 同时,移动端的控制器 1400 或移动终端辅助设备 1450 确定移动终端辅助设备 1450 触动了移动端 1400 . [0174] 随后,移动端 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 和移动端 1400 ,它们存在于预定的可用距离内,已经相对于彼此注册。 如果确定移动端 1400 以及移动终端辅助设备 1450 已经相对于彼此注册,如图14C所示,移动终端 1400 可以通过应用预定的安全相关信息将其转为使用状态。 [0175] 根据本发明的一个实施例,移动终端后 1400 或移动终端辅助设备 1450 判断移动端辅助设备是否 1450 或移动端 1400 存在于可用距离内,若移动终端辅助设备 1450 存在于可用距离内,判断是否存在移动终端辅助设备 1450 正在使用中。 [0176] 例如,即使是移动终端辅助设备 1450 在移动终端的可用距离内被检测到 1400 ,如果是移动端辅助设备 1450 未使用时,无需判断是否为移动终端辅助设备 1450 已注册。 反之,如果移动终端辅助设备 1450 正在使用中,应判断是否为移动终端辅助设备 1450 已注册。 据此,移动终端 1400 判断移动端辅助设备是否 1450 判断是否为移动终端辅助设备后注册的 1450 是否存在于可用距离内以及检测到的移动终端辅助设备是否存在 1450 正在使用中。 [0177] 图15A-15D是图示根据本发明实施例的移动终端和移动终端辅助设备的使用的图。 [0178] 参考图15A,一个用户针对一个移动终端使用一个移动终端辅助设备。 用户根据他或她的需要配置移动终端。 相应地,在移动终端与移动终端辅助设备之间的注册过程中,可以将包括移动终端的设置信息在内的安全相关信息存储在移动终端或移动终端辅助设备中。 之后,当用户通过移动终端辅助设备使用移动终端时,根据预先存储的设置信息对移动终端进行配置,从而使用户能够方便地使用移动终端。 [0179]或者,如图15B所示,一个用户可以通过使用一个移动终端辅助设备来使用多个移动终端。 用户在多个移动终端上使用具有一致性的特定信息。 因此,根据本发明的实施例,用户在移动终端辅助设备中存储他或她想要的包括设置信息的安全信息。 另外,当用户从第一移动终端切换到第二移动终端时,用户根据存储在移动终端辅助设备中的设置信息配置和使用第二移动终端。 [0180] 如图15C所示,多个用户通过各自的移动终端辅助设备使用一个移动终端。 用户在保护隐私的同时与其他用户共享移动终端的内容。 相应地,每个用户在移动终端辅助设备中存储包括密码的安全相关信息,该密码防止其他人查看他或她在移动终端中的私人信息。 备选地,可以配置为将安全相关信息存储在移动终端中,并且仅当预定的移动终端辅助设备与移动终端连接时才去激活安全。 [0181] 如图15D所示,多个用户通过多个移动终端辅助设备使用多个移动终端。 在这种情况下,用户在多个移动终端上使用一致的特定信息,并在保护隐私的同时与其他用户共享移动终端的内容。 在这种情况下,每个用户在移动终端辅助设备中存储安全相关信息,包括他或她想要的设置信息和防止其他人查看他或她在移动终端中的私人信息的密码。 根据本发明实施例,安全相关信息存储在移动终端中。 [0182] 图16是示出根据本发明实施例的移动终端辅助设备和移动终端辅助设备中的移动终端的注销以及取决于多个用户的多个移动终端的使用的流程图。 [0183] 参见图16,在步骤 1610 ,移动终端辅助设备判断注册的移动终端是否存在预定的连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0184] 如果预定连接距离内不存在移动终端,则确定移动终端辅助设备与移动终端断开连接,移动终端辅助设备删除内存中存储的移动终端信息, 步骤 1630 . [0185] 根据本发明的一个实施例,当确定在连接距离内不存在已注册的移动终端时,移动终端辅助设备判断在预定断开参考时间内是否检测到移动终端,步骤 1620 . 即,移动终端辅助设备判断移动终端是否在预定断开参考时间内不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端,则移动终端辅助设备删除正在运行的移动终端的信息 1630 . [0186] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除移动终端辅助设备中存储的第一移动终端的信息。 [0187]然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 此时,移动终端辅助设备在第一移动终端断开连接后,判断第二移动终端是否连接断开参考时间 1620 . 判断结果为,如果第二移动终端在预定的参考时间内连接上,则移动终端辅助设备不删除第一移动终端的信息,而是保留第一移动终端的信息。 [0188] 图17是示出根据本发明的实施例的移动终端中的移动终端辅助设备和移动终端的注销以及取决于多个用户使用多个移动终端的流程图。 [0189] 参见图17,在步骤 1710 ,移动终端判断注册的移动终端辅助设备是否存在预定连接距离。 即,如图9A和9B所示,判断移动终端是否 900 以及移动终端辅助设备 950 彼此间隔超过预定的连接距离 980 . 在预定的连接距离内可以进行近距离通信 980 ,根据本发明的一个实施例。 [0190] 若预定连接距离内不存在移动终端辅助设备,则确定移动终端辅助设备与移动终端断开连接,移动终端删除内存中存储的移动终端辅助设备信息, 步 1730 . [0191] 根据本发明的一个实施例,当确定连接距离内不存在已注册的移动终端辅助设备时,移动终端判断是否在预定断开参考时间内检测到移动终端辅助设备。 也就是说,移动终端可以判断在预定断开参考时间内移动终端辅助设备是否不存在于预定连接距离内。 如果在预定的断开时间内没有检测到移动终端辅助设备,则移动终端删除正在运行的移动终端辅助设备的信息 1730 . [0192] 根据本发明的一个实施例,如图15B-15D所示,虽然移动终端辅助设备与第一移动终端断开连接,但是移动终端辅助设备与第二移动终端连接。 此时,删除第一移动终端中存储的移动终端辅助设备信息。 [0193] 然而,根据本发明的实施例,用户在使用第二移动终端之后再次使用第一移动终端。 第一移动终端在与第一移动终端断开后,判断移动终端辅助设备是否与第二移动终端连接,步骤 1720 . 判断结果为,若移动终端附属设备与第二移动终端连接,则第一移动终端不删除,而是保留移动终端附属设备的信息。 [0194]第一移动终端从服务器接收移动终端辅助设备是否与第二移动终端连接的信息。 也就是说,当移动终端辅助设备与至少一个移动终端相互注册时,服务器存储至少一个移动终端与移动终端辅助设备的注册状态信息。 另外,移动终端或移动终端辅助设备周期性或特定事件发生时,向服务器发送移动终端辅助设备与哪个移动终端连接以及移动终端辅助设备是否在使用中的信息。 进一步地,服务器存储接收到的移动终端辅助设备和移动终端的使用状态信息。 [0195] 如果确定移动终端辅助设备与所有移动终端断开连接,不再使用,根据本发明实施例,移动终端和移动终端辅助设备的注册状态信息 被删除。 根据本发明的一个实施例,服务器向移动终端或移动终端辅助设备发送注销指令。 之后,接收到注销指令的移动终端或移动终端附属设备删除存储在移动终端附属设备或移动终端上的信息。 [0196] 图18是图示根据本发明实施例的用于管理移动终端辅助设备的方法的图。 [0197] 参考图18,服务器 1830 管理移动终端辅助设备相互注册信息 1850 以及至少一台移动终端 1810 和/或 1820 . [0198] 移动终端辅助设备 1850 离开第二移动终端的可用距离区域 1820 , 而移动端辅助设备 1850 与第二移动终端结合使用 1820 . 随后,移动终端辅助设备 1850 进入第一移动终端的可用距离区域 1810 与第一移动终端连接 1810 用来。 [0199] 移动终端 1810 和 1820 传输是否与移动终端辅助设备连接的信息 1850 到服务器 1830 . 服务器 1830 从移动终端接收关于连接状态的信息 1810 和 1820 , 并存储相同的。 [0200] 根据本发明的一个实施例,第二移动终端 1820 接收到移动终端辅助设备的信息 1850 与第二移动终端断开连接 1820 , 但它与第一​​移动终端连接 1810 , 从服务器 1830 . 即第二移动终端 1820 确定移动终端辅助设备 1850 未丢失但与第一移动终端连接 1810 在使用中。 因此,第二移动终端 1820 不删除但维护移动终端辅助设备上的信息 1850 . [0201] 然而,虽然未在图中示出,但是当移动终端辅助设备 1850 连第一个移动终端都没有连接 1810 , 第二移动端 1820 接收到移动终端辅助设备的信息 1850 从服务器断开所有移动终端 1830 . 第二移动终端 1820 确定移动终端辅助设备 1850 丢失了。 第二移动终端 1820 删除移动终端辅助设备信息 1850 以及与安全相关的信息。 第一个移动终端 1820 同时删除移动端辅助设备信息 1850 以及与安全相关的信息。 [0202]图19是图示根据本发明另一实施例的用于管理移动终端辅助设备的方法的图。 [0203] 参见图19,移动终端辅助设备 1950 管理关于至少一个移动终端的注册信息 1910 或者 1920 . [0204] 移动终端辅助设备 1950 确定与移动终端的连接状态 1910 和 1920 . [0205] 例如移动端辅助设备 1950 离开第二移动终端的可用距离区域 1920 而移动终端辅助设备 1950 与第二移动终端结合使用 1920 . 随后,移动终端辅助设备 1950 进入第一移动终端的可用距离区域 1910 从而与第一移动终端连接 1910 用来。 [0206] 根据本发明的一个实施例,移动终端辅助设备 1950 判断移动端辅助设备是否 1950 与第一移动终端连接 1910 在预定的断开时间内。 即如果移动终端辅助设备 1950 与第二移动终端断开连接 1920 , 并与第一移动终端相连 1910 , 移动端辅助设备 1950 不认为丢失。 据此,移动终端辅助设备 1950 不删除但维护移动终端上的信息 1910 和 1920 以及与安全相关的信息。 [0207] 然而,当移动终端辅助设备 1950 连第一个移动终端都没有连接 1910 , 移动端辅助设备 1950 因未与任何移动终端连接,确定丢失。 移动终端辅助设备 1950 删除手机端信息 1910 和 1920 ,以及与安全相关的信息。 [0208] 根据本发明的一个实施例,在移动终端中注册移动终端辅助设备时,可以将电子邮件、SNS等应用程序的账户信息存储在移动终端辅助设备的内存中。 移动终端辅助设备在使用移动终端时,移动终端辅助设备可以将存储的账户信息发送给移动终端。 移动终端可以根据接收到的账号信息,自动登录对应的账号,无需输入登录密码。 [0209] 或者,根据本发明的一个实施例,移动终端辅助设备存储移动终端锁定状态解除的信息。 此时,在通过移动终端辅助设备的特定按键开启移动终端的显示单元,并通过移动终端辅助设备触摸移动终端的显示单元的情况下,移动终端可以 无需输入密码即可转换为等待模式。 [0210] 另外,根据本发明的一个实施例,在移动终端和移动终端辅助设备在使用过程中持续测量RSSI,从而可以判断移动终端辅助设备是否存在于预定的可用距离内。 如果判断结果为移动终端辅助设备在可用距离内,则确定移动终端辅助设备正在使用中,从而可以控制移动终端的显示单元保持开启。 [0211] 根据本发明的一个实施例,在使用移动终端进行支付时,使用已注册的移动终端辅助设备可以很容易地批准支付,或者只有通过签名等安全过程才能批准支付。 通过已注册的移动终端辅助设备进行。 [0212]此外,根据本发明的一个实施例,通过输入单元放大或缩小显示在移动终端的显示单元上的特定对象,例如移动终端辅助设备上的按钮。 [0213] 此外,根据本发明的实施例,所描述的方法可以通过记录有程序的记录介质中的计算机可读代码来实现。 计算机可读介质包括其中存储有计算机系统可读数据的所有类型的记录设备。 计算机可读记录介质可以包括ROM、RAM、CD-ROM、磁带、软盘、光学数据存储器等。 计算机可读记录介质可以以载波的形式实现(例如,通过互联网传输)。 计算机可以包括终端的控制器或移动终端辅助设备的控制器。 [0214] 对于本领域的技术人员来说显而易见的是,在不脱离本发明的范围和本质特征的情况下可以进行各种修改。 [0215] 虽然本发明已参照其某些实施例进行了展示和描述,但本领域技术人员将理解,在不脱离本发明所定义的精神和范围的情况下,可以在其中进行形式和细节的各种改变 附加索赔。(String), 111498(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.705 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.705 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.856 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR1020150041337A(String), KR102138034B1(String), US20150099486A1(String), US9749858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), KR1020150041337A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), KR102138034B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:12.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270644(Integer), US20150099486A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270644(Integer), US9749858B2(String), 1046854(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9749858B2(String), US9749858B2(String), 1503936000(Integer), 270644(Integer), 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184927(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 184927(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184927(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 184927(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 184927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.955 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:13.955 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184928(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\06feb445573641918c4f6e5463d3bd1e.png(String), 184928(Integer), 06feb445573641918c4f6e5463d3bd1e.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.157 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Multi-standby mobile terminal and method of performing conference call using the same(String), 多待移动终端及使用该移动终端进行电话会议的方法(String), US20090186607A1(String), A multi-standby mobile terminal and a method for performing a conference call using the same are provided. The method of performing a conference call includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal, requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network, and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 提供了一种多待移动终端和使用该多待移动终端进行电话会议的方法。 执行电话会议的方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端是多待移动终端,通过第三者请求与第二移动终端的通信。 移动终端存在于第二无线通信网络中,并且通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议,当 通信请求为电话会议请求,将合成声音信号发送给第三移动终端。(String), US12/346068(String), 1230566400(Integer), US20090186607A1(String), 1248278400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 9(Integer), US20030072421A1 | US20030092433A1 | US20060291419A1 | US20070082699A1 | US20070111743A1 | US20090291675A1 | US6904023B2 | US7869806B2 | US8244228B1(String), \20230420\06feb445573641918c4f6e5463d3bd1e.png(String), 20(Integer), 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 1. A multi-standby mobile terminal comprising:a first communication module for forming a communication channel with a first wireless communication network;a second communication module for forming a communication channel with a second wireless communication network; anda first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and for outputting the synthesized sound signal to the second communication module.(String), 1.一种进行电话会议的方法,该方法包括:连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中第二移动终端包括多待移动终端;通过存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信;和当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成为第二移动终端的第一混音器中的合成声音信号来执行电话会议,以及将合成后的声音信号发送给第三移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 2. The multi-standby mobile terminal of claim 1, further comprising a second audio mixer for synthesizing sound signals, input from the first communication module and the second communication module, to a synthesized sound signal, and outputting the synthesized sound signal to a speaker.(String), 12.如权利要求11所述的方法,其中电话会议的执行还包括如果第一移动终端和第二移动终端之间的通信终止,则终止第三混音器的功能。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 3. The multi-standby mobile terminal of claim 2, further comprising a third audio mixer for synthesizing sound signals, input from the second communication module and the microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the first communication module.(String), 13.如权利要求11所述的方法,其中进行电话会议还包括将从第一移动终端和第三移动终端输入的声音信号合成为第二移动终端的第二混音器中的合成声音信号,并将合成声音信号输出到第二移动终端的扬声器移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 4. The multi-standby mobile terminal of claim 1, further comprising:a first antenna for transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and for receiving a frequency to be used for the GSM wireless communication network; anda second antenna for transmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and for receiving a frequency to be used for the CDMA wireless communication network.(String), 14.如权利要求11所述的方法,还包括:通过全球移动通信系统(GSM)无线通信网络发送和接收声音信号和数据,并接收用于GSM无线通信网络的频率;和通过码分多址(CDMA)无线通信网络发送和接收声音信号和数据,以及接收要用于CDMA无线通信网络的频率。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 5. The multi-standby mobile terminal of claim 4, wherein the first communication module forms the communication channel with the GSM wireless communication network and transmits and receives a wireless signal to and from a first mobile terminal.(String), 15.如权利要求14所述的方法,其中第一无线通信网络包括GSM无线通信网络并且向第一移动终端发送无线信号以及从第一移动终端接收无线信号。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 6. The multi-standby mobile terminal of claim 4, wherein the second communication module forms the communication channel with the CDMA wireless communication network and transmits and receives a wireless signal to and from a third mobile terminal.(String), 16.如权利要求14所述的方法,其中第二无线通信网络包括CDMA无线通信网络并且向第三移动终端发送无线信号以及从第三移动终端接收无线信号。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 7. The multi-standby mobile terminal of claim 5, wherein the first communication module demodulates a wireless signal received from the first mobile terminal and modulates the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 17.如权利要求15所述的方法,还包括对从第一移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第三移动终端的合成声音信号进行调制。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 8. The multi-standby mobile terminal of claim 6, wherein the second communication module demodulates a wireless signal received from the third mobile terminal and modulates a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 18.如权利要求16所述的方法,还包括对从第三移动终端接收的无线信号进行解调,并对第二移动终端的合成声音信号和第一移动终端的合成声音信号进行调制。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 9. The multi-standby mobile terminal of claim 3, further comprising a controller for terminating a function of the first audio mixer, if communication through the second communication module terminates.(String), 19.如权利要求13所述的方法,其中进行电话会议包括将从第二移动终端和第三移动终端输入的声音信号在第二移动终端的第三混音器中合成为合成声音信号,并将合成声音信号发送给第一移动终端。(String), 1(Integer), 8(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 10. The multi-standby mobile terminal of claim 9, wherein the controller terminates a function of the third audio mixer, if communication through the first communication module terminates.(String), 20.如权利要求19所述的方法,其中电话会议的执行还包括如果第二移动终端和第三移动终端之间的通信终止,则终止第一混音器的功能。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 11. A method for performing a conference call, the method comprising:connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal comprises a multi-standby mobile terminal;requesting communication with the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; andperforming a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 12. The method of claim 11, wherein the performing of the conference call further comprises terminating a function of the third audio mixer, if communication between the first mobile terminal and the second mobile terminal terminates.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 13. The method of claim 11, wherein the performing of the conference call further comprises synthesizing sound signals input from the first mobile terminal and the third mobile terminal, to a synthesized sound signal in a second audio mixer of the second mobile terminal and outputting the synthesized sound signal to a speaker of the second mobile terminal.(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 14. The method of claim 11, further comprising:transmitting and receiving a sound signal and data through a Global System for Mobile communication (GSM) wireless communication network and receiving a frequency to be used for the GSM wireless communication network; andtransmitting and receiving a sound signal and data through a Code Division Multiple Access (CDMA) wireless communication network and receiving a frequency to be used for the CDMA wireless communication network.(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 15. The method of claim 14, wherein the first wireless communication network comprises the GSM wireless communication network and transmits and receives a wireless signal to and from the first mobile terminal.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 16. The method of claim 14, wherein the second wireless communication network comprises the CDMA wireless communication network and transmits and receives a wireless signal to and from the third mobile terminal.(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 17. The method of claim 15, further comprising demodulating a wireless signal received from the first mobile terminal and modulating the synthesized sound signal of the second mobile terminal and the synthesized sound signal of the third mobile terminal.(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 18. The method of claim 16, further comprising demodulating a wireless signal received from the third mobile terminal and modulating a synthesized sound signal of the second mobile terminal and a synthesized sound signal of the first mobile terminal.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 19. The method of claim 13, wherein the performing of the conference call comprises synthesizing sound signals input from the second mobile terminal and the third mobile terminal, to a synthesized sound signal in a third audio mixer of the second mobile terminal and transmitting the synthesized sound signal to the first mobile terminal.(String), 1(Integer), 18(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184928(Integer), 20. The method of claim 19, wherein the performing of the conference call further comprises terminating a function of the first audio mixer, if communication between the second mobile terminal and the third mobile terminal terminates.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111499(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184928(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Jan. 17, 2008 in the Korean Intellectual Property Office and assigned Serial No. 10-2008-0005296, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same. More particularly, the present invention relates to a multi-standby mobile terminal and a method of performing a conference call using the same that enable a communication connection between several mobile terminals existing in different wireless communication networks. [0004]2. Description of the Related Art [0005]Due to rapid technology development, mobile terminals having various functions, such as voice communication, short message service, audiovisual communication, an electronic scheduler and Internet, are now available. A multi-standby mobile terminal that can perform a communication connection with two or more wireless communication networks, such as a dual-standby mobile terminal that supports a Code Division Multiple Access (CDMA) wireless communication network and a Global System for Mobile communication (GSM) wireless communication network, is now provided. The dual-standby mobile terminal may be in a communication standby state in both a CDMA wireless communication network service area and a GSM wireless communication network service area. That is, in a state where the dual-standby mobile terminal is connected for communication with a mobile terminal using a CDMA wireless communication network, the dual-standby mobile terminal can receive a communication request from a mobile terminal using a GSM wireless communication network and be connected with the mobile terminal for communication. [0006]A mobile terminal service provider provides, as an additional service, a conference call function in which several persons can simultaneously form a communication channel and perform a phone conference. [0007]A conventional multi-standby mobile terminal cannot perform a conference call. However, the conventional multi-standby mobile terminal can only perform simultaneous standby and individual communication with mobile terminals using different wireless communication networks. [0008]Therefore, a need exists for a method and apparatus that enable a multi-standby mobile terminal to perform a conference call using different wireless communication networks. SUMMARY OF THE INVENTION [0009]An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a multi-standby mobile terminal and a method for performing a conference call using the same that enable mobile terminals in different wireless communication networks to perform a conference call. [0010]In accordance with an aspect of the present invention, a multi-standby mobile terminal is provided. The mobile terminal includes a first communication module for forming a communication channel with a first wireless communication network, a second communication module for forming a communication channel with a second wireless communication network, and a first audio mixer for synthesizing sound signals, input from the first communication module and a microphone, to a synthesized sound signal, and outputting the synthesized sound signal to the second communication module. [0011]In accordance with another aspect of the present invention, a method of performing a conference call is provided. The method includes connecting a first mobile terminal existing in a first wireless communication network and a second mobile terminal, wherein the second mobile terminal is a multi-standby mobile terminal; requesting communication to the second mobile terminal, by a third mobile terminal existing in a second wireless communication network; and performing a conference call by synthesizing sound signals, input from the first mobile terminal and the second mobile terminal, to a synthesized sound signal in a first audio mixer of the second mobile terminal, when the communication request is a request for a conference call, and transmitting the synthesized sound signal to the third mobile terminal. [0012]Other aspects, disadvantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0014]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention; [0015]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention; and [0016]FIG. 3 is a flowchart illustrating a method for performing a conference call according to an exemplary embodiment of the present invention. [0017]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0018]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0019]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0020]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0021]In the following description, a dual-standby mobile terminal that can perform a communication connection with a CDMA wireless communication network and a GSM wireless communication network, such as a multi-standby mobile terminal, are described. However, the present invention is not limited thereto. That is, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a communication connection with various wireless communication networks, such as a General Packet Radio Service (GPRS), an Enhanced Data GSM Environment (EDGE), a Universal Mobile Telecommunications System (UMTS) and a Wideband Code Division Multiple Access (WCDMA). [0022]A configuration of a multi-standby mobile terminal according to an exemplary embodiment of the present invention and a method of performing a conference call using the multi-standby mobile terminal are described with reference to the accompanying drawings. [0023]FIG. 1 is a diagram illustrating a conference call system using a multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0024]Referring to FIG. 1, a first mobile terminal 100 is a mobile terminal for supporting a GSM wireless communication network 150, a third mobile terminal 300 is a mobile terminal for supporting a CDMA wireless communication network 350 and a second mobile terminal 200 is a multi-standby mobile terminal for supporting both the GSM and CDMA wireless communication networks 150 and 350. The first mobile terminal 100 and the third mobile terminal 300 may also be a multi-standby mobile terminal. [0025]In the following description, in a state where the first mobile terminal 100 and the second mobile terminal 200 are connected for communication, if the third mobile terminal 300 requests communication between several persons, it is assumed that the second mobile terminal 200 may perform a conference call function. That is, in a state where the second mobile terminal 200 and the first mobile terminal 100 are connected for communication using the GSM wireless communication network 150, the third mobile terminal 300 may request, through the CDMA wireless communication network 350, communication between several persons to the second mobile terminal 200. Alternatively, the second mobile terminal 200 may request communication between several persons to the third mobile terminal 300. In this case, a conference call function of the second mobile terminal 200 is activated. Thus, communication between the first mobile terminal 100, the second mobile terminal 200 and the third mobile terminal 300 may be performed. [0026]A conference call function of the second mobile terminal 200 is described later with reference to FIG. 2. [0027]When a conference call function is activated, if a sound signal of the first mobile terminal 100 is transmitted to the second mobile terminal 200, the second mobile terminal 200 synthesizes its own sound signal and a sound signal of the first mobile terminal 100 using an audio mixer and transmits the synthesized sound signal to the third mobile terminal 300. That is, the third mobile terminal 300 may receive sound signals of the second mobile terminal 200 and the first mobile terminal 100 through the synthesized sound signal. [0028]Similarly, if a sound signal of the third mobile terminal 300 is transmitted to the second mobile terminal 200, the second mobile terminal 200 may synthesize its own sound signal and a sound signal of the third mobile terminal 300 using an audio mixer. The second mobile terminal 200 then transmits the synthesized sound signal to the first mobile terminal 100. That is, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300 through the synthesized sound signal. [0029]The second mobile terminal 200 synthesizes a sound signal transmitted from the first mobile terminal 100 and a sound signal transmitted from the third mobile terminal 300 using the audio mixer and outputs the synthesized sound signal through a speaker (SPK) of the second mobile terminal 200. Thereby, the first mobile terminal 100 may receive sound signals of the second mobile terminal 200 and the third mobile terminal 300, the second mobile terminal 200 may receive sound signals of the first mobile terminal 100 and the third mobile terminal 300, and the third mobile terminal 300 may receive sound signals of the first mobile terminal 100 and the second mobile terminal 200. Thus, a conference call may be performed. [0030]FIG. 2 is a block diagram illustrating a configuration of the multi-standby mobile terminal according to an exemplary embodiment of the present invention. [0031]FIG. 2 illustrates, as the multi-standby mobile terminal 200 according to an exemplary embodiment of the present invention, a dual-standby mobile terminal that may perform a communication connection with the GSM wireless communication network and the CDMA wireless communication network. However, the multi-standby mobile terminal of the present invention is not limited to the dual-standby mobile terminal. [0032]The dual-standby mobile terminal may have slots in which a CDMA card and a GSM card are mounted or one slot for mounting a dual card in which a CDMA card and a GSM card are integrated. [0033]Referring to FIG. 2, a dual-standby mobile terminal (hereinafter, the second mobile terminal 200) according to an exemplary embodiment of the present invention includes a first antenna 401, a second antenna 402, a first communication module 410, a second communication module 420, a controller 450 and an audio mixer 460 including a first audio mixer 461, a second audio mixer 462 and a third audio mixer 463. [0034]The first antenna 401 transmits and receives a sound signal and data through the GSM wireless communication network 150 and receives a frequency to be used for the GSM wireless communication network 150. [0035]The second antenna 402 transmits and receives a sound signal and data through the CDMA wireless communication network 350 and receives a frequency to be used for the CDMA wireless communication network 350. [0036]FIG. 2 illustrates the first antenna 401 and the second antenna 402 as separate antennas. However the first antenna 401 and the second antenna 402 may be formed as one antenna. When the first antenna 401 and the second antenna 402 are formed as one antenna, the dual-standby mobile terminal 200 includes a means for dividing a frequency band into a CDMA frequency band and a GSM frequency band. For example, the dual-standby mobile terminal 200 divides a signal received by the antenna using a duplexer (not shown) into signals of a CDMA frequency band and signals of a GSM frequency band. The dual-standby mobile terminal 200 transmits the signal of the GSM frequency band to the first communication module 410 and the signal of the CDMA frequency band to the second communication module 420. [0037]The first communication module 410 and the second communication module 420 each include a transmission/reception signal divider (not shown) for dividing a transmission/reception signal, a Radio Frequency (RF) transmitter (not shown) for up-converting a frequency of a signal to be transmitted and amplifying the signal, an RF receiver (not shown) for low-noise amplifying a received signal and down-converting a frequency of the signal and a modem for modulating and demodulating a sound signal. [0038]Hereinafter, for convenience of description, it is assumed that the first communication module 410 forms a communication channel with the GSM wireless communication network 150 and transmits and receives a wireless signal to and from the first mobile terminal 100 using a GSM wireless communication method. Also, the second communication module 420 forms a communication channel with the CDMA wireless communication network 350 and transmits and receives a wireless signal to and from the third mobile terminal 300 using a CDMA wireless communication method. [0039]The first communication module 410 demodulates a wireless signal received from the first mobile terminal 100 and modulates a sound signal input from a microphone (MIC) of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the first communication module 410 modulates a sound signal of the second mobile terminal 200 and a sound signal of the third mobile terminal 300 synthesized in the audio mixer 460 and transmits the modulated sound signal to the first mobile terminal 100. [0040]The second communication module 420 demodulates a wireless signal received from the third mobile terminal 300 and modulates a sound signal input from the MIC of the second mobile terminal 200 to a wireless signal. More particularly, when performing a conference call, the second communication module 420 modulates a sound signal of the second mobile terminal 200 and a sound signal of the first mobile terminal 100 synthesized in the audio mixer 460 and transmits the modulated sound signal to the third mobile terminal 300. [0041]The controller 450 controls general operations of the second mobile terminal 200 and a signal flow of elements of the second mobile terminal 200. More particularly, the controller 450 controls the first communication module 410 and the second communication module 420. In more detail, the controller 450 controls the first communication module 410 and the second communication module 420 to perform a communication connection with the GSM communication network 150 and CDMA communication network 350, respectively. When a communication connection request is received by the first communication module 410 or the second communication module 420, the controller 450 activates the corresponding first communication module 410 or second communication module 420 to perform communication. [0042]Further, in a state where the first mobile terminal 100 and the second mobile terminal 200 perform communication through the GSM wireless communication network 150, if the third mobile terminal 300 requests communication between several persons through the CDMA wireless communication network 350, the controller 450 of the second mobile terminal 200 performs a conference call function. If a communication request received from the third mobile terminal 300 is not a request for communication between several persons, the controller 450 performs an individual communication function. That is, in order to perform individual communication with the third mobile terminal 300, the controller 450 terminates functions other than a communication connection function of the first communication module 410. Further, the controller 450 controls the audio mixer 460 to block transmission and reception of a sound signal to and from the first mobile terminal 100. [0043]Similarly, in order to perform individual communication with the first mobile terminal 100, the controller 450 terminates functions other than a communication connection function of the second communication module 420, and blocks transmission and reception of a sound signal to and from the third mobile terminal 300. [0044]The controller 450 may perform a conference call function for activating both the first communication module 410 and the second communication module 420. Specifically, when the controller 450 activates both the first communication module 410 and the second communication module 420, a sound signal of the first mobile terminal 100 is modulated in the second mobile terminal 200, the modulated sound signal is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the third mobile terminal 300. Likewise, a sound signal of the third mobile terminal 300 is synthesized with a sound signal of the second mobile terminal 200 in the audio mixer 460 and the synthesized signal is transmitted to the first mobile terminal 100. Thereby, a conference call for voice communication between mobile terminals in different wireless communication networks is performed. [0045]When the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0046]While performing a conference call, when communication with either the first mobile terminal 100 or the third mobile terminal 300 terminates, the controller 450 controls a conference call termination function of the audio mixer 460. A detailed description thereof is described later. [0047]The controller 450 may be included in the first communication module 410 or in the second communication module 420. In this case, the communication module 410 or 420 including the controller 450 becomes a main communication module and controls signal flows of the entire system, including the signal flows of another communication module. [0048]When performing a conference call, the first audio mixer 461 synthesizes a sound signal of the first mobile terminal 100 received from the first communication module 410 and a sound signal received from the MIC of the second mobile terminal 200. The first audio mixer 461 outputs the synthesized sound signal to the second communication module 420. The synthesized sound signal output to the second communication module 420 is modulated and transmitted to the third mobile terminal 300 via the second antenna 402. That is, when performing a conference call, a sound signal of the first mobile terminal 100 is input to the first audio mixer 461, via the first communication module 410 of the second mobile terminal 200, and synthesized by the first audio mixer 461 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the second communication module 420 of the second mobile terminal 200 and transmitted to the third mobile terminal 300 through the second antenna 402. [0049]While performing a conference call, when communication with the third mobile terminal 300 terminates, the first audio mixer 461 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the first audio mixer 461 is activated only when performing communication with the third mobile terminal 300. [0050]The second audio mixer 462 synthesizes a sound signal of the first mobile terminal 100 output from the first communication module 410 and a sound signal of the third mobile terminal 300 output from the second communication module 420. The synthesized sound signal is output through a speaker (SPK) of the second mobile terminal 200. The SPK may be mounted on the mobile terminal or may be an earphone of the mobile terminal or a separate audio speaker receiving the synthesized sound signal. [0051]The third audio mixer 463 synthesizes a sound signal of the third mobile terminal 300 received from the second communication module 420 and a sound signal received from the MIC of the second mobile terminal 200. The third audio mixer 463 outputs the synthesized sound signal to the first communication module 410. The synthesized sound signal output to the first communication module 410 is modulated and transmitted to the first mobile terminal 100, via the first antenna 401. That is, when performing a conference call, a sound signal of the third mobile terminal 300 is input to the third audio mixer 463 via the second communication module 420 of the second mobile terminal 200 and synthesized by the third audio mixer 463 together with a signal input from the MIC of the second mobile terminal 200. The synthesized sound signal is input to the first communication module 410 of the second mobile terminal 200 and transmitted to the first mobile terminal 100 from the first antenna 401. [0052]While performing a conference call, when communication with the first mobile terminal 100 terminates, the third audio mixer 463 terminates a conference call function. In an exemplary implementation, in order to prevent unnecessary power consumption, the third audio mixer 463 is activated only when performing communication with the first mobile terminal 100. [0053]FIG. 3 is a flowchart illustrating a method of performing a conference call according to an exemplary embodiment of the present invention. [0054]Referring to FIGS. 1 to 3, the first mobile terminal 100 and the second mobile terminal 200 are connected for communication through the GSM wireless communication network 150 in step S500. In this case, the second mobile terminal 200 transmits and receives a wireless signal to and from the first mobile terminal 100 from the first antenna 401 and the first communication module 410. [0055]The controller 450 of the second mobile terminal 200 controls the second communication module 420 to await a communication connection request. Further, when forming a communication channel with the first mobile terminal 100, the controller 450 of the second mobile terminal 200 activates the second audio mixer 462 and the third audio mixer 463 and sustains the first audio mixer 461 in an inactive state. Specifically, when the first mobile terminal 100 and the second mobile terminal 200 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the second audio mixer 462 and the third audio mixer 463. When the second mobile terminal 200 and the third mobile terminal 300 perform individual communication, the controller 450 of the second mobile terminal 200 activates only the first audio mixer 461 and the second audio mixer 462. When performing a conference call, the controller 450 of the second mobile terminal 200 activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0056]The third mobile terminal 300 requests communication to the second mobile terminal 200 through the CDMA wireless communication network 350 in step S502. Although not shown in FIG. 3, alternatively the second mobile terminal 200 may request communication to the third mobile terminal 300 through the CDMA wireless communication network 350. [0057]When a communication request from the third mobile terminal 300 is received, the controller 450 of the second mobile terminal 200 notifies the reception of a communication request to a user of the second mobile terminal 200, by controlling a display unit to display that a communication connection request from another wireless communication network is received or by outputting a reception sound, for example. [0058]The second mobile terminal 200 determines whether a conference call is to be performed according to the communication request received from the CDMA wireless communication network 350 in step S504. [0059]If a conference call is not to be performed, the second mobile terminal 200 performs individual communication with either the first mobile terminal 100 or the third mobile terminal 300, according to the user's selection in step S506. The individual communication is performed by controlling the first communication module 410 and the second communication module 420. For example, when individual communication with the first mobile terminal 100 is intended, the controller 450 of the second mobile terminal 200 controls to sustain only a communication connection state of the second communication module 420 and to turn off other functions. [0060]If it is determined that a conference call is to be performed in step S504, the second mobile terminal 200 activates a conference call function in step S508. The controller 450 activates both the first communication module 410 and the second communication module 420 of the second mobile terminal 200, and activates the first audio mixer 461, second audio mixer 462 and third audio mixer 463. [0061]The second mobile terminal 200 is connected for communication with the third mobile terminal 300 in the CDMA wireless communication network 350 in step S510, thereby forming a conference call with the first mobile terminal 100 and the third mobile terminal 300. [0062]When forming a conference call between the first mobile terminal 100 and the third mobile terminal 300, the first audio mixer 461 of the second mobile terminal 200 synthesizes a sound signal of the first mobile terminal 100 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the second communication module 420. The output sound signal of the first mobile terminal 100 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the third mobile terminal 100 from the second antenna 402. [0063]The third audio mixer 463 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the second mobile terminal 200 and outputs the synthesized sound signal to the first communication module 410. The output sound signal of the third mobile terminal 300 and the output sound signal of the second mobile terminal 200 are transmitted as the synthesized sound signal to the first mobile terminal 100 from the first antenna 401. [0064]The second audio mixer 462 of the second mobile terminal 200 synthesizes a sound signal of the third mobile terminal 300 and a sound signal of the first mobile terminal 100. The second audio mixer 462 outputs the synthesized sound signal through the SPK of the second mobile terminal 200. [0065]While performing a conference call, when communication between the first mobile terminal 100 and the second mobile terminal 200 terminates, the controller 450 of the second mobile terminal 200 terminates functions of the third audio mixer 463 in order to prevent unnecessary power consumption. Alternatively, when communication between the second mobile terminal 200 and the third mobile terminal 300terminates, the controller 450 of the second mobile terminal 200 terminates functions of the first audio mixer 461 in order to prevent unnecessary power consumption. [0066]As described above, a multi-standby mobile terminal according to exemplary embodiments of the present invention may perform a conference call with mobile terminals using different wireless communication networks. Thus, a conference call may be performed without subscribing to an additional service. Accordingly, user convenience may be improved. [0067]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.(String), 优先 [0001] 此申请根据 35 U.S.C. 2008 年 1 月 17 日向韩国知识产权局提交并转让序列号为 10-2008-0005296 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种多待移动终端以及使用该多待移动终端进行电话会议的方法。 更具体地,本发明涉及一种多待移动终端以及使用该多待移动终端执行电话会议的方法,其使得存在于不同无线通信网络中的多个移动终端之间能够进行通信连接。 [0004] 2.相关技术的描述 [0005] 由于技术的快速发展,具有多种功能的移动终端,例如语音通信、短消息服务、视听通信、电子日程安排和互联网已经面世。 可以与两个或多个无线通信网络进行通信连接的多待移动终端,例如支持码分多址(CDMA)无线通信网络和全球移动通信系统(GSM)的双待移动终端 ) 无线通信网络,现提供。 双待移动终端在CDMA无线通信网络服务区和GSM无线通信网络服务区都可以处于通信待机状态。 即,在双待移动终端与使用CDMA无线通信网络的移动终端进行通信连接的状态下,双待移动终端可以接收来自使用GSM无线通信网络的移动终端的通信请求,并且 与移动终端连接进行通信。 [0006] 移动终端服务提供商作为附加服务提供电话会议功能,其中几个人可以同时形成通信信道并进行电话会议。 [0007] 传统的多待移动终端无法进行电话会议。 然而,传统的多待机移动终端只能与使用不同无线通信网络的移动终端进行同时待机和单独通信。 [0008] 因此,需要一种使多待移动终端能够使用不同的无线通信网络进行电话会议的方法和装置。 发明内容 [0009] 本发明的一个方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一方面在于提供一种多待移动终端以及使用该多待移动终端进行电话会议的方法,使得不同无线通信网络中的移动终端能够进行电话会议。 [0010] 根据本发明的一个方面,提供了一种多待移动终端。 该移动终端包括用于与第一无线通信网络形成通信信道的第一通信模块、用于与第二无线通信网络形成通信信道的第二通信模块、以及用于合成声音信号的第一混音器,从第一无线通信网络输入。 通信模块和麦克风,以合成声音信号,并将合成声音信号输出到第二通信模块。 [0011]根据本发明的另一方面,提供了一种执行电话会议的方法。 该方法包括连接存在于第一无线通信网络中的第一移动终端和第二移动终端,其中,第二移动终端是多待移动终端; 由存在于第二无线通信网络中的第三移动终端请求与第二移动终端的通信; 当通信请求是电话会议请求时,通过将从第一移动终端和第二移动终端输入的声音信号合成到第二移动终端的第一混音器中的合成声音信号来进行电话会议, 将合成的声音信号发送给第三移动终端。 [0012] 本发明的其他方面、缺点和显着特征对于本领域技术人员而言将从以下详细描述中变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0013] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0014] 如图。 附图说明图1是示出根据本发明示例性实施例的使用多待移动终端的电话会议系统的图; [0015] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图; 和 [0016] 如图。 图3是示出根据本发明示例性实施例的用于执行电话会议的方法的流程图。 [0017] 在整个附图中,应当注意,相同的附图标记用于描述相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0018] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,省略了对众所周知的功能和结构的描述。 [0019] 以下描述和权利要求中使用的术语和词语不限于书目含义,而是仅由发明人使用以实现对本发明的清晰和一致的理解。 因此,本领域技术人员应该清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0020] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0021] 在以下描述中,描述了可以与CDMA无线通信网络和GSM无线通信网络进行通信连接的双待移动终端,例如多待移动终端。 然而,本发明不限于此。 即,根据本发明示例性实施例的多待机移动终端可以执行与各种无线通信网络的通信连接,例如通用分组无线服务(GPRS)、增强型数据GSM环境(EDGE)、通用 移动电信系统 (UMTS) 和宽带码分多址 (WCDMA)。 [0022]参照附图描述根据本发明示例性实施例的多待移动终端的配置以及使用多待移动终端执行电话会议的方法。 [0023] 如图。 图1是图示根据本发明示例性实施例的使用多待移动终端的电话会议系统的图。 [0024] 参考图。 1、第一个移动终端 100 是支持GSM无线通信网络的移动终端 150 ,第三个移动终端 300 是支持CDMA无线通信网络的移动终端 350 和第二个移动终端 200 是支持GSM和CDMA无线通信网络的多待机移动终端 150 和 350 . 第一个移动终端 100 第三个移动终端 300 也可以是多待移动终端。 [0025] 在下面的描述中,在第一移动终端 100 第二移动终端 200 连接进行通信,如果第三个移动终端 300 请求多人之间的通信,假设第二个移动终端 200 可以执行电话会议功能。 即,在第二移动终端 200 和第一个移动终端 100 使用 GSM 无线通信网络进行通信 150 , 第三个移动终端 300 可通过 CDMA 无线通信网络请求 350 , 几个人之间的通信到第二个移动终端 200 . 或者,第二移动终端 200 可以向第三移动终端请求多人之间的通信 300 . 在这种情况下,第二移动终端的电话会议功能 200 被激活。 这样,第一移动终端之间的通信 100 ,第二个移动终端 200 第三个移动终端 300 可以执行。 [0026] 第二移动终端的电话会议功能 200 稍后将参考图10进行描述。 2. [0027] 开启电话会议功能时,如果第一移动终端的声音信号 100 发送到第二移动终端 200 ,第二个移动终端 200 合成自己的声音信号和第一移动终端的声音信号 100 使用混音器将合成的声音信号发送给第三移动终端 300 . 即第三移动终端 300 可以接收第二移动终端的声音信号 200 和第一个移动终端 100 通过合成的声音信号。 [0028] 同理,如果第三移动终端的声音信号 300 发送到第二移动终端 200 ,第二个移动终端 200 可以合成自己的声音信号和第三移动终端的声音信号 300 使用音频混音器。 第二个移动终端 200 然后将合成的声音信号发送给第一移动终端 100 . 即第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 通过合成的声音信号。 [0029] 第二个移动终端 200 合成从第一移动终端发送的声音信号 100 第三移动终端发送的声音信号 300 使用音频混合器并通过第二移动终端的扬声器(SPK)输出合成的声音信号 200 . 由此,第一移动终端 100 可以接收第二移动终端的声音信号 200 第三个移动终端 300 ,第二个移动终端 200 可以接收第一移动终端的声音信号 100 第三个移动终端 300 ,以及第三个移动终端 300 可以接收第一移动终端的声音信号 100 第二移动终端200 . 因此,可以执行电话会议。 [0030] 如图。 图2是示出根据本发明示例性实施例的多待移动终端的配置的框图。 [0031] 如图。 如图2所示,作为多待移动终端 200 根据本发明的示例性实施例,提供一种可以与GSM无线通信网络和CDMA无线通信网络进行通信连接的双待移动终端。 然而,本发明的多待移动终端不限于双待移动终端。 [0032] 双待移动终端可以具有安装CDMA卡和GSM卡的插槽,或者一个用于安装集成了CDMA卡和GSM卡的双卡的插槽。 [0033] 参考图。 2、双待移动终端(以下简称第二移动终端 200 )根据本发明的示例性实施例包括第一天线 401 ,第二根天线 402 ,第一通信模块 410 ,第二个通信模块 420 , 一个控制器 450 和一个混音器 460 包括第一个混音器 461 ,第二个音频混音器 462 和第三个混音器 463 . [0034] 第一个天线 401 通过 GSM 无线通信网络发送和接收声音信号和数据 150 并接收用于GSM无线通信网络的频率 150 . [0035] 第二个天线 402 通过CDMA无线通信网络发送和接收声音信号和数据 350 并接收用于CDMA无线通信网络的频率 350 . [0036] 如图。 图2说明了第一天线 401 和第二根天线 402 作为单独的天线。 但是第一个天线 401 和第二根天线 402 可以形成为一个天线。 当第一根天线 401 和第二根天线 402 组成一根天线,双待移动终端 200 包括用于将频带划分为CDMA频带和GSM频带的装置。 例如双待移动终端 200 使用双工器(未示出)将天线接收到的信号分成CDMA频带的信号和GSM频带的信号。 双待移动终端 200 将GSM频段的信号传输给第一通信模块 410 以及CDMA频段的信号到第二通信模块 420 . [0037] 第一通讯模块 410 第二通信模块 420 每个都包括用于划分发送/接收信号的发送/接收信号分配器(未示出)、用于对要发送的信号的频率进行上变频和放大信号的射频(RF)发送器(未示出)、RF 接收器(未示出)用于低噪声放大接收信号并下变频信号的频率,以及用于调制和解调声音信号的调制解调器。 [0038] 以下,为了描述方便,假设第一通信模块 410 与GSM无线通信网络形成通信通道 150 向第一移动终端发送和从第一移动终端接收无线信号 100 使用GSM无线通信方法。 此外,第二通信模块 420 与CDMA无线通信网络形成通信通道 350 向第三移动终端发送和从第三移动终端接收无线信号 300 使用CDMA无线通信方法。 [0039] 第一通讯模块 410 解调从第一移动终端接收到的无线信号 100 调制从第二移动终端的麦克风(MIC)输入的声音信号 200 到无线信号。 更具体地,在进行电话会议时,第一通信模块 410 调制第二移动终端的声音信号200 第三移动终端的声音信号 300 在混音器中合成 460 将调制后的声音信号发送给第一移动终端 100 . [0040] 第二通讯模块 420 解调从第三移动终端接收的无线信号 300 调制从第二移动终端的MIC输入的声音信号 200 到无线信号。 更具体地说,当进行电话会议时,第二通信模块 420 调制第二移动终端的声音信号 200 以及第一移动终端的声音信号 100 在混音器中合成 460 将调制后的声音信号发送给第三移动终端 300 . [0041] 控制器 450 控制第二移动终端的一般操作 200 第二移动终端的元件的信号流 200 . 更具体地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 . 更详细地说,控制器 450 控制第一通讯模块 410 第二通信模块 420 与 GSM 通信网络进行通信连接 150 和CDMA通信网络 350 , 分别。 当第一通信模块接收到通信连接请求时 410 或第二通信模块 420 , 控制器 450 激活相应的第一通信模块 410 或第二个通信模块 420 进行通信。 [0042] 进一步地,在第一移动终端 100 第二移动终端 200 通过GSM无线通信网络进行通信 150 ,如果是第三个移动终端 300 通过 CDMA 无线通信网络请求多人之间的通信 350 , 控制器 450 第二个移动终端 200 执行电话会议功能。 如果收到来自第三移动终端的通信请求 300 不是几个人之间的通信请求,控制器 450 执行单独的通信功能。 即,为了与第三移动终端进行单独通信 300 , 控制器 450 终止第一通信模块的通信连接功能以外的功能 410 . 此外,控制器 450 控制音频混音器 460 阻止与第一移动终端之间的声音信号的发送和接收 100 . [0043] 类似地,为了与第一移动终端进行单独的通信 100 , 控制器 450 终止第二通信模块的通信连接功能以外的功能 420 ,并阻止与第三移动终端之间的声音信号的发送和接收 300 . [0044] 控制器 450 可以执行电话会议功能以激活第一通信模块 410 第二通信模块 420 . 具体来说,当控制器 450 激活第一个通信模块 410 第二通信模块 420 ,第一移动终端的声音信号 100 在第二个移动终端中调制 200 ,调制后的声音信号与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第三移动终端 300 . 同样,第三移动终端的声音信号 300 与第二移动终端的声音信号合成 200 在混音器中 460 合成后的信号发送给第一移动终端 100 . 从而,在不同无线通信网络中的移动终端之间进行语音通信的电话会议。 [0045] 当第一个移动终端 100第二移动终端 200 执行单独的通信,控制器 450 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0046] 在进行电话会议时,与第一移动终端中的任一个通信时 100 或者第三个移动终端 300 终止,控制器 450 控制混音器的电话会议终止功能 460 . 稍后描述其详细描述。 [0047] 控制器 450 可以包括在第一通信模块中 410 或在第二个通讯模块中 420 . 在这种情况下,通信模块 410 或者 420 包括控制器 450 成为主要的通信模块,控制整个系统的信号流,包括另一个通信模块的信号流。 [0048] 进行电话会议时,第一个混音器 461 合成第一移动终端的声音信号 100 从第一通信模块接收 410 以及从第二移动终端的MIC接收到的声音信号 200 . 第一个混音器 461 将合成的声音信号输出到第二通信模块 420 . 合成声音信号输出至第二通信模块 420 调制后发送到第三移动终端 300 通过第二根天线 402 . 即在进行电话会议时,第一移动终端的声音信号 100 输入到第一个混音器 461 ,通过第一通讯模块 410 第二个移动终端 200 ,并由第一个混音器合成 461 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第二通信模块 420 第二个移动终端 200 并传送至第三移动终端 300 通过第二根天线 402 . [0049] 进行电话会议时,与第三移动终端通信时 300 终止,第一个混音器 461 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第一混音器 461 仅在与第三移动终端进行通信时激活 300 . [0050] 第二个混音器 462 合成第一移动终端的声音信号 100 第一个通信模块的输出 410 第三移动终端的声音信号 300 第二通信模块的输出 420 . 合成的声音信号通过第二移动终端的扬声器(SPK)输出 200 . SPK可以安装在移动终端上,也可以是移动终端的耳机或接收合成声音信号的单独的音频扬声器。 [0051] 第三个混音器 463 合成第三移动终端的声音信号 300 从第二通信模块接收 420 以及从第二移动终端的MIC接收到的声音信号 200 . 第三个混音器 463 将合成的声音信号输出到第一通信模块 410 . 合成声音信号输出至第一通讯模块 410 被调制并发送到第一移动终端 100 ,通过第一根天线 401 . 即在进行电话会议时,第三移动终端的声音信号 300 输入到第三个混音器 463 通过第二个通信模块 420 第二个移动终端 200并由第三个混音器合成 463 连同从第二个移动终端的MIC输入的信号 200 . 合成声音信号被输入到第一通信模块 410 第二个移动终端 200 并传送至第一移动终端 100 从第一根天线 401 . [0052] 在进行电话会议时,与第一移动终端通信时 100 终止,第三个混音器 463 终止电话会议功能。 在一个示例性实施方式中,为了避免不必要的功耗,第三混音器 463 仅在与第一移动终端进行通信时激活 100 . [0053] 如图。 图3是示出根据本发明示例性实施例的执行电话会议的方法的流程图。 [0054] 参考图。 1到3、第一移动终端 100 第二移动终端 200 通过 GSM 无线通信网络连接进行通信 150 在步骤 S 500 . 在这种情况下,第二移动终端 200 向第一移动终端发送和从第一移动终端接收无线信号 100 从第一根天线 401 和第一通信模块 410 . [0055] 控制器 450 第二个移动终端 200 控制第二通信模块 420 等待通信连接请求。 此外,当与第一移动终端形成通信信道时 100 , 控制器 450 第二个移动终端 200 激活第二个混音器 462 和第三个混音器 463 并维持第一个混音器 461 处于非活动状态。 具体地,当第一移动终端 100 第二移动终端 200 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第二个混音器 462 和第三个混音器 463 . 当第二个移动终端 200 第三个移动终端 300 执行单独的通信,控制器 450 第二个移动终端 200 仅激活第一个混音器 461 和第二个混音器 462 . 进行电话会议时,控制器 450 第二个移动终端 200 激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0056] 第三个移动终端 300 请求与第二移动终端的通信 200 通过CDMA无线通信网络 350 在步骤 S 502 . 尽管图 1 中未显示。 3、备选第二个移动终端 200 可以请求与第三移动终端的通信 300 通过CDMA无线通信网络 350 . [0057] 当来自第三移动终端的通信请求时 300 收到,控制器 450 第二个移动终端 200 通知第二移动终端的用户接收到通信请求 200 例如,通过控制显示单元显示接收到来自另一无线通信网络的通信连接请求或者通过输出接收声音。 [0058] 第二个移动终端 200 根据从CDMA无线通信网络接收到的通信请求,确定是否进行电话会议 350 在步骤 S 504 . [0059] 如果不进行电话会议,则第二移动终端 200 与第一移动终端进行单独通信 100 或者第三个移动终端 300 ,根据用户在步骤S中的选择 506 . 通过控制第一通信模块进行单独通信 410 第二通信模块 420 . 例如,当与第一移动终端单独通信时 100旨在,控制器 450 第二个移动终端 200 控制以仅维持第二通信模块的通信连接状态 420 并关闭其他功能。 [0060] 如果在步骤S中确定要进行电话会议 504 ,第二个移动终端 200 在步骤 S 中激活电话会议功能 508 . 控制器 450 激活第一个通信模块 410 第二通信模块 420 第二个移动终端 200 , 并激活第一个混音器 461 , 第二个混音器 462 和第三个混音器 463 . [0061] 第二个移动终端 200 连接用于与第三移动终端通信 300 在CDMA无线通信网络中 350 在步骤 S 510 ,从而与第一移动终端形成电话会议 100 第三个移动终端 300 . [0062] 第一移动终端之间进行电话会议时 100 第三个移动终端 300 , 第一个混音器 461 第二个移动终端 200 合成第一移动终端的声音信号 100 第二移动终端的声音信号 200 并将合成声音信号输出至第二通信模块 420 . 第一移动终端的输出声音信号 100 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第三移动终端 100 从第二根天线 402 . [0063] 第三个混音器 463 第二个移动终端 200 合成第三移动终端的声音信号 300 第二移动终端的声音信号 200 并将合成声音信号输出至第一通讯模块 410 . 第三移动终端的输出声音信号 300 以及第二移动终端的输出声音信号 200 作为合成声音信号发送到第一移动终端 100 从第一根天线 401 . [0064] 第二个混音器 462 第二个移动终端 200 合成第三移动终端的声音信号 300 以及第一移动终端的声音信号 100 . 第二个混音器 462 通过第二移动终端的SPK输出合成的声音信号 200 . [0065] 在进行电话会议时,在第一移动终端之间进行通信时 100 第二移动终端 200 终止,控制器 450 第二个移动终端 200 终止第三个混音器的功能 463 以防止不必要的功耗。 或者,当第二移动终端之间进行通信时 200 第三个移动终端 300 终止,控制器 450 第二个移动终端 200 终止第一个混音器的功能 461 以防止不必要的功耗。 [0066] 如上所述,根据本发明示例性实施例的多待机移动终端可以与使用不同无线通信网络的移动终端进行电话会议。 因此,可以在不订阅附加服务的情况下执行电话会议。 因此,可以提高用户便利性。 [0067] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String), 111499(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.890 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101489322A(String), EP2081370A1(String), KR1020090079379A(String), US20090186607A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270645(Integer), CN101489322A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270645(Integer), EP2081370A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:14.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270645(Integer), KR1020090079379A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270645(Integer), US20090186607A1(String), 1046859(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20090186607A1(String), US20090186607A1(String), 1248278400(Integer), 270645(Integer), 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.083 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184928(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.198 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.199 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.199 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 184928(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.235 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1662111618(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25448(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184928(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25448(Integer), 2(Integer), 184928(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.334 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.334 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.356 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25448(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.413 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.414 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.433 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.434 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.434 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 226(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.457 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120276924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.707 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.707 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.722 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.723 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 103(Integer), 1(Integer), 0(Integer), 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.727 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.727 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.727 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.742 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.746 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:15.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 184929(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d6a4d38a1d784f5291f8de766721917b.png(String), 184929(Integer), d6a4d38a1d784f5291f8de766721917b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System and method for positioning mobile terminal, and mobile terminal(String), 移动终端定位系统、方法及移动终端(String), US20120276924A1(String), The disclosure discloses a method for positioning a mobile terminal, which comprises: a server sends a push notification to a mobile terminal; the mobile terminal performs self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal, and sends the geographical position information to the server; the server receives and displays the geographical position information sent by the mobile terminal. The disclosure also discloses a system for positioning a mobile terminal for implementing the method for positioning a mobile terminal and a mobile terminal. With such method and device, the server can be used to send a push notification to the mobile terminal after a user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal.(String), 本发明公开了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端收到推送通知后进行自我定位,获取移动终端的地理位置信息,并将地理位置信息发送给服务器。 服务器接收并显示移动终端发送的地理位置信息。 本发明还公开了一种用于实现上述移动终端定位方法的移动终端定位系统及移动终端。 通过这样的方法和装置,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位其地理位置信息,并将地理位置信息发送至服务器,以帮助用户检索移动终端。(String), US13/519896(String), 1279468800(Integer), US20120276924A1(String), 1351699200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 4(Integer), US20070015505A1 | US20080293397A1 | US20080320573A1 | US20120142329A1(String), \20230420\d6a4d38a1d784f5291f8de766721917b.png(String), 16(Integer), 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 1. A method for positioning a mobile terminal, comprising:sending, by a server, a push notification to a mobile terminal;performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal;sending, by the mobile terminal, the geographical position information to the server; andreceiving and outputting, by the server, the geographical position information sent by the mobile terminal.(String), 1.根据权利要求9所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 2. The method according to claim 1, further comprising: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal,sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andperforming, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command.(String), 12.根据权利要求2所述的方法,还包括:在服务器向移动终端发送推送通知的步骤之前,移动终端在检测到SIM卡被更换后,向服务器发送移动终端的国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息正在启动。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 3. The method according to claim 1, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 13.根据权利要求12所述的方法,还包括:服务器根据接收到的移动终端的IMEI与IMSI的匹配信息,更新之前的移动终端的IMEI与IMSI的匹配信息,并进一步判断更新后的IMEI是否为在服务器注册的移动终端的IMEI。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 4. The method according to claim 3, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 14.根据权利要求6所述的系统,其中移动终端还包括SIM卡检测模块和匹配信息发送模块,其中SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 5. A system for positioning a mobile terminal, comprising a server and a mobile terminal, whereinthe server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; andthe mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 15.根据权利要求14所述的系统,其中服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前移动终端的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为移动终端在服务器注册的IMEI.16.根据权利要求10所述的移动终端,还包括:SIM卡检测模块,用于检测移动终端的SIM卡是否被更换;和匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码IMEI和国际移动用户识别码IMSI的匹配信息。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 6. The system according to claim 5, whereinthe server is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; andthe mobile terminal further comprises a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 7. The system according to claim 5, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 8. The system according to claim 7, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 9. A mobile terminal, comprising a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 10. The mobile terminal according to claim 9, further comprising a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 11. The mobile terminal according to claim 9, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 12. The method according to claim 2, further comprising: before the step of sending, by the server, the push notification to the mobile terminal,sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 13. The method according to claim 12, further comprising:updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 14. The system according to claim 6, wherein the mobile terminal further comprises a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, whereinthe SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; andthe matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed.(String), 1(Integer), 13(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 15. The system according to claim 14, whereinthe server is further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 184929(Integer), 16. The mobile terminal according to claim 10, further comprising:a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; anda matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.595 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.595 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.595 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 111500(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 184929(Integer), TECHNICAL FIELD [0001]The disclosure relates to the technology of mobile communications, particularly to a system and method for positioning a mobile terminal and to a mobile terminal. BACKGROUND [0002]With the continuous development of mobile communication technologies, a mobile terminal, such as a mobile phone, a Personal Digital Assistant (PDA) and the like is no longer used as a simple communication tool only. Because the above mobile terminal has advantages of small volume, easiness in taking, convenience in use and the like, it has gradually become a personal information storage carrier for the user. Many users of the mobile terminal get used to storing important personal information involving personal information security, such as contacts, photos, schedules and the like in the mobile terminal. [0003]After the mobile terminal is lost, its operator cannot help the user retrieve the lost mobile terminal because the operator only provides Subscriber Identity Module (SIM) card loss reporting and re-issuing services, and cannot provide specific position information of the mobile terminal. SUMMARY [0004]The disclosure mainly aims to provide a system and method for positioning a mobile terminal, and also provide a mobile terminal, with which geographical position information of a lost mobile terminal can be provided to a user to help the user retrieve the mobile terminal. [0005]The disclosure provides a method for positioning a mobile terminal, which comprises: sending, by a server, a push notification to a mobile terminal; performing, by the mobile terminal, self-positioning after receiving the push notification, to acquire geographical position information regarding the mobile terminal; sending, by the mobile terminal, the geographical position information to the server; and receiving and outputting, by the server, the geographical position information sent by the mobile terminal. [0006]Preferably, the method may further comprise: after the step of receiving and outputting, by the server, the geographical position information sent by the mobile terminal, sending, by the server, a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and performing, by the mobile terminal, automatic locking and/or deleting, by the mobile terminal, data in a memory, after receiving the locking command and/or the deleting command. [0007]Preferably, the method may further comprise: before the step of sending, by the server, the push notification to the mobile terminal, sending, by the mobile terminal, matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server, when detecting that a Subscriber Identity Module (SIM) card has been changed after being started. [0008]Preferably, the method may further comprise: updating, by the server, previous matching information between the IMEI and the IMSI of the mobile terminal according to the received matching information between the IMEI and the IMSI of the mobile terminal, and further judging, by the server, whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0009]A system for positioning a mobile terminal, comprises a server and a mobile terminal, wherein the server is configured to send a push notification to the mobile terminal, and to receive geographical position information sent by the mobile terminal; and the mobile terminal further comprises a positioning module, which is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0010]Preferably, the server may be further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol; and the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving the locking command; the deleting module is configured to delete data in a memory of the mobile terminal after receiving the deleting command. [0011]Preferably, the mobile terminal may further comprise a Subscriber Identity Module (SIM) card detecting module and a matching information sending module, wherein the SIM card detecting module is configured to detect whether an SIM card of the mobile terminal is changed; and the matching information sending module is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) of the mobile terminal to the server when the SIM card is changed. [0012]Preferably, the server may be further configured to update previous matching information between the IMEI and the IMSI of the mobile terminal after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server. [0013]A mobile terminal comprises a positioning module, which is configured to perform self-positioning after receiving a push notification from a server, so as to acquire geographical position information regarding the mobile terminal, and to send the geographical position information to the server. [0014]Preferably, the mobile terminal may further comprise a locking module and a deleting module, wherein the locking module is configured to lock the mobile terminal after receiving a locking command sent by the server; and the deleting module is configured to delete data in a memory of the mobile terminal after receiving a deleting command sent by the server. [0015]Preferably, the mobile terminal may further comprise: a Subscriber Identity Module (SIM) card detecting module, which is configured to detect whether an SIM card of the mobile terminal is changed; and a matching information sending module, which is configured to send matching information between an International Mobile Equipment Identity (IMEI) and an International Mobile User Identity (IMSI) to the server when the SIM card of the mobile terminal is changed. [0016]With the system and method for positioning a mobile terminal, and the mobile terminal provided by the disclosure, the server can be used to send a push notification to the mobile terminal after the user finds that the mobile terminal is lost. The mobile terminal positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0017]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure; [0018]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure; [0019]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure; [0020]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure; [0021]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure; and [0022]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0023]The achievement of the purpose of the disclosure, functional characteristics and advantages of the disclosure will be described with reference to the embodiments and drawings in detail. DETAILED DESCRIPTION [0024]The technical solution of the disclosure is described below with reference to the drawings of the description and the specific embodiments in detail. [0025]FIG. 1 shows a schematic diagram of a flow of an embodiment of a method for protecting data in a mobile terminal of the disclosure. [0026]After a mobile terminal is lost, when a finder or a thief does not turn off the mobile terminal, its user logs in a server in time to report loss, and registers an International Mobile Equipment Identity (IMEI) of the mobile terminal. As shown in FIG. 1, a method for protecting data in a mobile terminal of the disclosure comprises the following steps. [0027]Step S101: a server sends a push notification to a mobile terminal. [0028]In this embodiment, the push notification can be sent to the mobile terminal through the server so as to notify the mobile terminal to be positioned via the push notification. In addition, the mobile terminal is registered with an inbound network connection for a positioning program, and the mobile terminal monitors whether the push notification sent by the monitoring mobile terminal is received on the registered inbound network connection. The inbound network connection is registered for the positioning program in a static registration manner or a dynamic registration manner. The static registration will be taken as an example in this embodiment for description. [0029]The server inquires an International Mobile Subscriber Identity (IMSI) of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends the push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0030]Furthermore, a Java Application Description (JAD) file of the mobile terminal is further provided with the MIDlet-Push-<1>attribute, for example the attribute is set as: [0031]MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; after the attribute is added, it indicates a connection protocol adopted is a Short Messaging Service (SMS) protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0032]Step S102: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0033]In the embodiment, the positioning program is a location Application Programming Interface (API) for Java 2 Micro Edition (J2ME) program, which meets Java Specification Request (JSR) 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a Global Positioning System (GPS), a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0034]Step S103: the mobile terminal sends the geographical position information to the server. [0035]In the embodiment, the geographical position information comprises longitude and latitude information of the mobile terminal. [0036]Step S104: the server receives and displays the geographical position information sent by the mobile terminal. [0037]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0038]Step S105: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0039]In the embodiment, the server sends a Lock And Wipe Management Object (LAWMO) command to the mobile terminal according to a Device Management (DM) protocol defined by Open Mobile Alliance (OMA). The server sends the locking command to the mobile terminal through the device management protocol in a Synchronization Markup Language (SyncML) protocol set. [0040]Step S106: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S105 and step S106 are not the necessary steps. [0041]In the embodiment, the server can be used to send the push notification to the mobile terminal after the user finds the mobile terminal is lost; the mobile terminal positions the geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal. [0042]FIG. 2 shows a schematic diagram of a flow of another embodiment of a method for protecting data in a mobile terminal of the disclosure. [0043]When a mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change a Subscriber Identity Module (SIM) card, when the finder or the thief turns on the mobile terminal again, the mobile terminal will protect data based on the following steps. [0044]Step S201: the mobile terminal detects whether an SIM card is changed after being started; if yes, turn to step S202; otherwise, turn to step S205. [0045]In the embodiment, after the mobile terminal is started, it automatically starts the SIM card verification kit to verify whether the IMSI of the SIM card is changed; if yes, it indicates the SIM card of the mobile terminal is changed. The method for automatically starting the SIM card detection function after startup is as follows: [0046]the MIDlet-1-Type:autostart attribute is added in the Java application description file of the terminal, and meanwhile an autostart permission is also added in the Java application description file in the specific format of: [0047]MIDlet-Permissions:javax.microedition.midlet.AutoStart Permission. [0048]Step S202: the mobile terminal sends matching information between an IMEI and an IMSI to the server. [0049]In the embodiment, the mobile terminal sends matching information between an IMEI and an IMSI to a server through a short message. [0050]Step S203: the server updates the matching information between the IMEI and the IMSI of the mobile terminal. [0051]In the embodiment, after receiving the short message, the server updates the matching information between the IMEI and the IMSI of the mobile terminal through modifying an IMSI number corresponding to the IMEI of the mobile terminal. [0052]Step S204: the server judges whether the updated IMEI is an IMEI of the mobile terminal registered at the server; if yes, turn to step S205; otherwise, the flow is terminated. [0053]Step S205: the server sends a push notification to the mobile terminal. [0054]In the embodiment, the server inquires an IMSI number of the mobile terminal according to the IMEI of the mobile terminal registered by the user, acquires a mobile phone number of the mobile terminal according to the IMSI number, and then sends a push notification to the mobile terminal according to the mobile phone number to require the mobile terminal to be positioned. [0055]In addition, the Java application description file of the mobile terminal is provided with the MIDlet-Push-<1>attribute, which is: [0056]MIDlet-Push-1:sms://:8080, MIDletLocation, 13900000000. After the attribute is added, it indicates a connection protocol adopted is an SMS protocol, a registered listening port number is 8080, a type name of MIDlet is MIDletLocation, and the effective source of the push notification is the server with the number of 13900000000. Besides the SMS protocol, the disclosure can also use a transmission control protocol or a user datagram protocol of course, which is not restricted in the disclosure. [0057]Step S206: after receiving the push notification, the mobile terminal performs self-positioning to acquire geographical position information regarding the mobile terminal. [0058]In the embodiment, the positioning program is a location API for J2ME program, which meets JSR 179 specification. The location API for J2ME program is an optional package of J2ME configured to position the mobile equipment. In this embodiment, the location API for J2ME program can utilize a satellite positioning method based on a GPS, a positioning method of a cellular network, or a Bluetooth-based short-range positioning method, or may combine the above manners. [0059]Step S207: the mobile terminal sends the geographical position information to the server. [0060]In the embodiment, the geographical position information comprises at least longitude and latitude information of the mobile terminal. [0061]Step S208: the server receives and displays the geographical position information sent by the mobile terminal. [0062]In the embodiment, the server can call a map program to display the longitude and latitude information of the mobile terminal, and now the user can see a specific position of the mobile terminal, and retrieve the mobile terminal according to the geographical position information. [0063]Step S209: the server sends a locking command and/or a deleting command to the mobile terminal according to a device management protocol. [0064]In the embodiment, the server sends an LAWMO command to the mobile terminal according to a device management protocol defined by open mobile alliance. The server sends the locking command to the mobile terminal through the device management protocol in a SyncML protocol set. [0065]Step S210: after receiving the locking command and/or the deleting command, the mobile terminal performs automatic locking and/or deleting data in a memory. After the mobile terminal automatically locks, no operation can be performed on the mobile terminal before unlocking. Of course, if the mobile user only desires to know the specific position of the mobile terminal without performing locking and/or deleting operation on the mobile terminal, step S209 and step S210 are not the necessary steps. [0066]In the embodiment, when the mobile terminal is lost, if a finder or a thief turns off the mobile terminal due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal; the mobile terminal positions geographical position information thereof after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal. Therefore, data in the lost mobile terminal is prevented from being leaked, and personal information security of the user is ensured. [0067]FIG. 3 shows a schematic diagram of a structure of an embodiment of a system for positioning a mobile terminal of the disclosure. [0068]The system for positioning a mobile terminal comprises a server 10 and a mobile terminal 20, wherein the mobile terminal 20 comprises a positioning module 201. [0069]The server is configured to send a push notification to the mobile terminal 20, and to receive geographical position information sent by the mobile terminal 20; the positioning module 201 is configured to perform self-positioning after receiving the push notification, so as to acquire the geographical position information regarding the mobile terminal 20, and to send the geographical position information to the server 10. [0070]In the embodiment, the server 10 can be used to send a push notification to the mobile terminal 20 after the user finds that the mobile terminal 20 is lost. The mobile terminal 20 locates geographical position information thereof through the positioning module 201 and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. [0071]FIG. 4 shows a schematic diagram of a structure of another embodiment of a system for positioning a mobile terminal of the disclosure. [0072]The server 10 is further configured to send a locking command and/or a deleting command to the mobile terminal according to a device management protocol. Besides the positioning module 201, the mobile terminal 20 further comprises a locking module 205 and a deleting module 204, an SIM card detecting module 202 and a matching information sending module 203. [0073]The locking module 205 is configured to lock the mobile terminal 20 after receiving the locking command. The deleting module 204 is configured to delete data in a memory after receiving the deleting command. The SIM card detecting module 202 is configured to detect whether an SIM card of the mobile terminal is changed. The matching information sending module 203 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card is changed. [0074]The server 10 is further configured to update the matching information between the IMEI and the IMSI of the mobile terminal 20 registered at the server after receiving the matching information between the IMEI and the IMSI, and to judge whether the updated IMEI is an IMEI of the mobile terminal registered at the server 10. [0075]In the embodiment, after the mobile terminal 20 is lost, if a finder or a thief turns off the mobile terminal 20 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 20 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 20 is changed; if the SIM card is not changed, the server 10 is directly used to send a push notification to the mobile terminal 20; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 20; the mobile terminal 20 positions geographical position information thereof through the positioning module 201 after receiving the push notification, and sends the geographical position information to the server 10 to help the user retrieve the mobile terminal 20. Therefore, data in the mobile terminal 20 is prevented from being leaked, and personal information security of the user is ensured. [0076]FIG. 5 shows a schematic diagram of a structure of an embodiment of a mobile terminal of the disclosure. [0077]The mobile terminal 30 comprises a positioning module 301, which is configured to perform self-positioning after receiving a push notification to acquire geographical position information regarding the mobile terminal 30, and send the geographical position information to a server. [0078]In the embodiment, the server can be used to send a push notification to the mobile terminal 30 after the user finds that the mobile terminal 30 is lost. The mobile terminal 30 positions geographical position information thereof and sends the geographical position information to the server to help the user retrieve the mobile terminal 30. [0079]FIG. 6 shows a schematic diagram of a structure of another embodiment of the mobile terminal of the disclosure. [0080]Besides the positioning module 301, the mobile terminal 40 further comprises a locking module 302, a deleting module 303, an SIM card detecting module 304, and a matching information sending module 305. [0081]The locking module 302 is configured to lock the mobile terminal 40 after receiving a locking command sent by a server; the deleting module 303 is configured to delete data in a memory after receiving a deleting command sent by the server. The SIM card detecting module 304 is configured to detect whether an SIM card is changed. The matching information sending module 305 is configured to send matching information between an IMEI and an IMSI to the server when the SIM card of the mobile terminal is changed. [0082]In the embodiment, after the mobile terminal 40 is lost, if a finder or a thief turns off the mobile terminal 40 due to low battery or the desire to change an SIM card, when the finder or the thief turns on the mobile terminal 40 again, the mobile terminal firstly verifies whether the SIM card of the mobile terminal 40 is changed; if the SIM card is not changed, the server is directly used to send a push notification to the mobile terminal 40; and if the SIM card is changed, the IMSI after the SIM card is changed is firstly acquired, then a push notification is sent to the mobile terminal 40; the mobile terminal 40 positions geographical position information thereof through the positioning module 301 after receiving the push notification, and sends the geographical position information to the server to help the user retrieve the mobile terminal 40. Therefore, data in the mobile terminal 40 is prevented from being leaked, and personal information security of the user is ensured. [0083]The above is only the preferred embodiment of the disclosure and not intended to limit the scope of the patent, and any equivalent structure or equivalent flow transformation based on the description and drawings of the disclosure, which is directly or indirectly applied in other related technical fields shall fall within the scope of patent protection of the disclosure.(String), 技术领域 [0001] 本发明涉及移动通信技术,尤其涉及一种移动终端定位系统、方法及移动终端。 背景 [0002] 随着移动通信技术的不断发展,移动终端,如手机、个人数字助理(Personal Digital Assistant,PDA)等,不再仅仅是一种简单的通信工具。 由于上述移动终端具有体积小、携带方便、使用方便等优点,逐渐成为用户个人信息的存储载体。 很多移动终端的用户习惯于在移动终端中存储联系人、照片、日程等涉及个人信息安全的重要个人信息。 [0003] 移动终端丢失后,其运营商无法帮助用户找回丢失的移动终端,因为运营商仅提供SIM卡挂失和补发服务,无法提供移动终端的具体位置信息。 概括 [0004] 本发明的主要目的在于提供一种移动终端的定位系统及方法,还提供一种移动终端,能够将丢失的移动终端的地理位置信息提供给用户,以帮助用户找回移动终端。 [0005] 本发明提供了一种移动终端的定位方法,包括:服务器向移动终端发送推送通知; 移动终端接收到推送通知后进行自定位,获取移动终端的地理位置信息; 移动终端向服务器发送地理位置信息; 服务器接收并输出移动终端发送的地理位置信息。 [0006] 优选地,该方法还包括: 在服务器接收并输出移动终端发送的地理位置信息的步骤之后,服务器根据移动终端发送锁定命令和/或删除命令。 设备管理协议; 移动终端在接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 [0007] 优选地,该方法还包括: 在服务器向移动终端发送推送通知之前,移动终端发送国际移动设备识别码(IMEI)与国际移动用户识别码的匹配信息。 移动终端(IMSI)在启动后检测到SIM卡被更换时发送给服务器。 [0008] 优选地,该方法还包括:服务器根据接收到的移动终端的IMEI和IMSI的匹配信息更新之前的移动终端的IMEI和IMSI的匹配信息,进一步判断, 服务器,更新后的IMEI是否为在服务器注册的移动终端的IMEI。 [0009] 一种移动终端定位系统,包括服务器和移动终端,服务器用于向移动终端发送推送通知,并接收移动终端发送的地理位置信息; 移动终端还包括定位模块,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0010] 优选地,服务器还可以用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 移动终端还可以包括锁定模块和删除模块,锁定模块用于接收到锁定命令后锁定移动终端。 删除模块,用于接收到删除命令后,删除移动终端内存中的数据。 [0011] 优选地,所述移动终端还包括SIM卡检测模块和匹配信息发送模块,所述SIM卡检测模块用于检测所述移动终端的SIM卡是否被更换。 匹配信息发送模块,用于在更换SIM卡时,向服务器发送移动终端的国际移动设备识别码(IMEI)与国际移动用户识别码(IMSI)的匹配信息。 [0012] 优选地,服务器还用于在接收到IMEI与IMSI的匹配信息后,更新之前的IMEI与IMSI的匹配信息,并判断更新后的IMEI是否为注册的移动终端的IMEI 在服务器上。 [0013] 一种移动终端,包括定位模块,用于接收到服务器的推送通知后进行自定位,获取移动终端的地理位置信息,并将该地理位置信息发送给服务器。 [0014] 优选地,所述移动终端还包括锁定模块和删除模块,所述锁定模块用于接收到所述服务器发送的锁定命令后,锁定所述移动终端。 删除模块,用于接收到服务器发送的删除命令后,删除移动终端内存中的数据。 [0015] 优选地,所述移动终端还包括: SIM卡检测模块,用于检测所述移动终端的SIM卡是否被更换; 匹配信息发送模块,用于在移动终端更换SIM卡时,向服务器发送国际移动设备识别码(IMEI)和国际移动用户识别码(IMSI)的匹配信息。 [0016] 本发明提供的移动终端定位系统、方法及移动终端,可以在用户发现移动终端丢失后,通过服务器向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 附图的简要说明 [0017] 图1为本发明移动终端数据保护方法实施例的流程示意图; [0018] 图2为本发明移动终端数据保护方法另一实施例的流程示意图; [0019] 图3示出了本发明移动终端定位系统实施例的结构示意图; [0020] 图4为本发明移动终端定位系统另一实施例的结构示意图; [0021] 图5示出了本发明移动终端一个实施例的结构示意图; 和 [0022] 图6示出了本发明移动终端另一实施例的结构示意图。 [0023] 本发明目的的实现、功能特点和优点将结合实施例和附图进行详细说明。 详细说明 [0024] 下面结合说明书附图和具体实施例对本发明的技术方案进行详细说明。 [0025] 图1示出了本发明移动终端数据保护方法实施例的流程示意图。 [0026] 移动终端丢失后,当捡到者或小偷没有关闭移动终端时,其用户及时登录服务器挂失,并注册移动终端的国际移动设备识别码(IMEI)。 如图1所示,本发明的移动终端中的数据保护方法包括以下步骤。 [0027] 脚步 101:服务器向移动终端发送推送通知。 [0028] 本实施例中,可以通过服务器向移动终端发送推送通知,以通过推送通知通知移动终端进行定位。 另外,移动终端注册有定位程序的入站网络连接,移动终端监听是否在注册的入站网络连接上接收到监控移动终端发送的推送通知。 入站网络连接以静态注册方式或动态注册方式注册到定位程序。 本实施例以静态注册为例进行说明。 [0029] 服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI,根据IMSI号码获取移动终端的手机号码,然后发送推送通知给 移动终端根据手机号码要求移动终端进行定位。 [0030] 进一步地,移动终端的JAD文件中还设置有MIDlet-Push-<1>属性,例如该属性设置为: [0031] MIDlet-Push-1:sms://:8080,MIDletLocation, 13900000000; 添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation,推送通知的有效源为服务器 13900000000个数。除了SMS协议之外,本发明当然还可以使用传输控制协议或用户数据报协议,本发明对此不作限制。 [0032] 脚步 102 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0033] 在本实施例中,定位程序为Java 2 Micro Edition(J2ME)程序的定位应用程序编程接口(API),其符合Java Specification Request(JSR)179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以利用基于全球定位系统(Global Positioning System,简称GPS)的卫星定位方法、蜂窝网络的定位方法、或者基于蓝牙的近距离定位方法,或者可以结合上述方法 礼貌。 [0034] 脚步 103 :移动终端向服务器发送地理位置信息。 [0035] 在本实施例中,地理位置信息包括移动终端的经纬度信息。 [0036] 脚步 104 :服务器接收并显示移动终端发送的地理位置信息。 [0037] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0038] 脚步 105 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0039] 在该实施例中,服务器根据开放移动联盟(OMA)定义的设备管理(DM)协议向移动终端发送锁定和擦除管理对象(LAWMO)命令。 服务器通过同步标记语言(SyncML)协议集中的设备管理协议向移动终端发送锁定命令。 [0040] 脚步 106 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S105 和步骤S 106 不是必要的步骤。 [0041] 本实施例中,可以通过服务器在用户发现移动终端丢失后向移动终端发送推送通知。 移动终端定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户找回移动终端。 [0042] 图2示出了本发明移动终端数据保护方法另一实施例的流程示意图。 [0043] 当移动终端丢失时,如果捡到者或小偷因电池电量低或想更换用户身份模块(SIM)卡而关闭移动终端,当捡到者或小偷再次打开移动终端时, 移动端将按照以下步骤保护数据。 [0044] 脚步 201 :移动终端开机后检测SIM卡是否被更换; 如果是,转步骤S 202 ; 否则转步骤S 205 . [0045] 本实施例中,移动终端启动后,自动启动SIM卡验证工具,验证SIM卡的IMSI是否发生变化; 如果是,则说明移动终端的SIM卡已更换。 开机后自动启动SIM卡检测功能的方法如下: [0046] 在终端的Java应用描述文件中增加了MIDlet-1-Type:autostart属性,同时在Java应用描述文件中也增加了自动启动权限,具体格式为: [0047] MIDlet-权限:javax.microedition.midlet.AutoStart 权限。 [0048] 脚步 202 :移动终端向服务器发送IMEI和IMSI的匹配信息。 [0049] 本实施例中,移动终端通过短消息向服务器发送IMEI和IMSI的匹配信息。 [0050] 脚步 203 :服务器更新移动终端IMEI和IMSI的匹配信息。 [0051] 本实施例中,服务器接收到短消息后,通过修改移动终端的IMEI对应的IMSI号,更新IMEI与移动终端的IMSI的匹配信息。 [0052] 脚步 204 :服务器判断更新后的IMEI是否为在服务器注册的移动终端的IMEI; 如果是,转步骤S 205 ; 否则,流程终止。 [0053] 脚步 205 :服务器向移动端发送推送通知。 [0054] 在本实施例中,服务器根据用户注册的移动终端的IMEI查询移动终端的IMSI号码,根据IMSI号码获取移动终端的手机号码,然后向客户端发送推送通知。 移动终端根据手机号码要求移动终端进行定位。 [0055] 另外,在移动端的Java应用描述文件中设置了MIDlet-Push-<1>属性,即: [0056] MIDlet-Push-1:sms://:8080,MIDletLocation,13900000000。添加该属性后表示采用的连接协议为SMS协议,注册的监听端口号为8080,MIDlet的类型名称为MIDletLocation, 推送通知的有效来源为号码为13900000000的服务器。 除了SMS协议之外,本发明当然还可以采用传输控制协议或用户数据报协议,本发明对此不做限制。 [0057] 脚步 206 :移动终端接收到推送通知后,进行自定位,获取移动终端的地理位置信息。 [0058]在本实施例中,定位程序为J2ME程序的定位API,符合JSR 179规范。 J2ME定位API程序是J2ME的一个可选包,配置用于定位移动设备。 在本实施例中,用于J2ME程序的定位API可以采用基于GPS的卫星定位方法、蜂窝网络的定位方法或基于蓝牙的近距离定位方法,也可以结合上述方式。 [0059] 脚步 207 :移动终端向服务器发送地理位置信息。 [0060] 在本实施例中,地理位置信息至少包括移动终端的经纬度信息。 [0061] 脚步 208 :服务器接收并显示移动终端发送的地理位置信息。 [0062] 本实施例中,服务器可以调用地图程序显示移动终端的经纬度信息,此时用户可以看到移动终端的具体位置,并根据地理位置信息检索移动终端。 [0063] 脚步 209 :服务器根据设备管理协议向移动终端发送锁定命令和/或删除命令。 [0064] 本实施例中,服务器根据开放移动联盟定义的设备管理协议向移动终端发送LAWMO命令。 服务器通过SyncML协议集中的设备管理协议向移动终端发送锁定命令。 [0065] 脚步 210 :移动终端接收到锁定命令和/或删除命令后,自动锁定和/或删除内存中的数据。 移动终端自动锁定后,解锁前不能对移动终端进行任何操作。 当然,如果移动用户只想知道移动终端的具体位置,而不需要对移动终端进行锁定和/或删除操作,步骤S 209 和步骤S 210 不是必要的步骤。 [0066] 在本实施例中,当移动终端丢失时,如果捡到者或小偷因电池电量低或想换SIM卡而关闭移动终端,当捡到者或小偷再次打开移动终端时,手机 终端首先验证移动终端的SIM卡是否被更换; 若SIM卡未更换,则直接通过服务器向移动终端发送推送通知。 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知。 移动终端接收到推送通知后定位自身的地理位置信息,并将地理位置信息发送给服务器,以帮助用户检索移动终端。 从而避免了丢失移动终端中的数据泄露,保证了用户的个人信息安全。 [0067] 图3示出了本发明移动终端定位系统实施例的结构示意图。 [0068] 一种移动终端定位系统,包括服务器 10 和移动终端 20 , 其中移动终端 20 包括一个定位模块 201 . [0069] 服务器配置为向移动终端发送推送通知 20 ,接收移动终端发送的地理位置信息 20 ; 定位模块 201 用于接收到推送通知后进行自定位,以获取移动终端的地理位置信息 20 ,并将地理位置信息发送给服务器 10 . [0070] 在本实施例中,服务器 10 可用于向移动端发送推送通知 20 用户发现移动端后 20 丢失了。 移动端 20 通过定位模块定位其地理位置信息 201 并将地理位置信息发送给服务器 10帮助用户找回移动终端 20 . [0071] 图4示出了本发明移动终端定位系统另一实施例的结构示意图。 [0072] 服务器 10 还用于根据设备管理协议向移动终端发送锁定命令和/或删除命令。 除了定位模块 201 , 移动端 20 还包括锁定模块 205 和一个删除模块 204 , SIM卡检测模块 202 以及匹配的信息发送模块 203 . [0073] 锁定模块 205 配置为锁定移动端 20 收到锁定命令后。 删除模块 204 用于接收到删除命令后删除内存中的数据。 SIM卡检测模块 202 用于检测移动终端的SIM卡是否被更换。 匹配信息发送模块 203 用于在更换SIM卡时向服务器发送IMEI和IMSI的匹配信息。 [0074] 服务器 10 还用于更新移动终端的IMEI与IMSI的匹配信息 20 接收到IMEI与IMSI的匹配信息后在服务器注册,判断更新后的IMEI是否为在服务器注册的移动终端的IMEI 10 . [0075] 在本实施例中,移动终端后 20 丢失,如果发现者或小偷关闭移动终端 20 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 20 再次,移动终端首先验证移动终端的SIM卡是否为 20 已更改; 如果SIM卡没换过,服务器 10 直接用于向移动端发送推送通知 20 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 20 ; 移动终端 20 通过定位模块定位其地理位置信息 201 收到推送通知后,将地理位置信息发送给服务器 10 帮助用户找回移动终端 20 . 因此,移动终端中的数据 20 防止泄露,保障用户个人信息安全。 [0076] 图5示出了本发明移动终端一个实施例的结构示意图。 [0077] 移动端 30 包括一个定位模块 301 ,用于接收到推送通知后进行自定位,获取移动终端的地理位置信息 30 ,并将地理位置信息发送给服务器。 [0078] 在本实施例中,服务器可以用于向移动终端发送推送通知 30 用户发现移动端后 30 丢失了。 移动端 30 对其地理位置信息进行定位,并将地理位置信息发送给服务器,以帮助用户检索移动终端 30 . [0079] 图6示出了本发明移动终端另一实施例的结构示意图。 [0080] 除了定位模块 301 , 移动端 40 还包括锁定模块 302 , 删除模块 303 , SIM卡检测模块 304 , 以及匹配的信息发送模块 305 . [0081] 锁定模块 302 配置为锁定移动端 40 收到服务器发送的锁定命令后; 删除模块 303 用于接收到服务器发送的删除命令后,删除内存中的数据。 SIM卡检测模块 304用于检测SIM卡是否被更换。 匹配信息发送模块 305 用于当移动终端的SIM卡更换时,向服务器发送IMEI和IMSI的匹配信息。 [0082] 在本实施例中,移动终端后 40 丢失,如果发现者或小偷关闭移动终端 40 由于电池电量低或想要更换 SIM 卡,当发现者或小偷打开移动终端时 40 再次,移动终端首先验证移动终端的SIM卡是否为 40 已更改; 若SIM卡未更换,则直接使用服务器向移动终端发送推送通知 40 ; 如果更换SIM卡,则先获取更换SIM卡后的IMSI,然后向移动终端发送推送通知 40 ; 移动终端 40 通过定位模块定位其地理位置信息 301 收到推送通知后,将地理位置信息发送给服务器,帮助用户找回移动终端 40 . 因此,移动终端中的数据 40 防止泄露,保障用户个人信息安全。 [0083] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的范围,任何基于本发明的说明书和附图所作的等效结构或等效流程变换,直接或间接应用于其他相关技术领域 落入本发明的专利保护范围。(String), 111500(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101835143A(String), EP2509375A1(String), EP2509375A4(String), US20120276924A1(String), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270683(Integer), CN101835143A(String), 1046942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), EP2509375A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), EP2509375A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.955 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.955 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270683(Integer), US20120276924A1(String), 1046865(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:16.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270683(Integer), WO2011137605A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101835143A(String), CN101835143A(String), 1284480000(Integer), 270683(Integer), 184967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.059 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.059 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LI, JINMIN(String), XU, LING(String), SHI(String), YUE, HUI(String), 中兴通讯股份有限公司(String), LI JINMIN(String), XU LING(String), 德世股份有限公司(String), YUE HUI(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184929(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 184929(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LI, JINMIN(String), LI JINMIN(String), 0(Integer), 1681975997(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: XU, LING(String), XU LING(String), 0(Integer), 1681975997(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHI(String), 德世股份有限公司(String), 0(Integer), 1681975997(Integer), 1(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: YUE, HUI(String), YUE HUI(String), 0(Integer), 1681975997(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 184929(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75817(Integer), 2(Integer), 184929(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75818(Integer), 2(Integer), 184929(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75819(Integer), 2(Integer), 184929(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75820(Integer), 2(Integer), 184929(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75817(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 184929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.834 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:17.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185928(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f785db5d5d704237b772c2f005a2ac1b.png(String), 185928(Integer), f785db5d5d704237b772c2f005a2ac1b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of providing Karaoke service to mobile terminals using a wireless connection between the mobile terminals(String), 使用移动终端之间的无线连接向移动终端提供卡拉OK服务的方法(String), US7142807B2(String), A method of providing a Karaoke service to mobile terminals through wireless connection between them. The mobile terminals are grouped as a service group and one of them is designated as a master mobile terminal and the other mobile terminals as slave mobile terminals. The master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service content to be received from the Karaoke service provider in all the mobile terminals of the service group. If the master mobile terminal transmits a play command to the slave mobile terminals, all the mobile terminals start to play Karaoke music according to the service contents.(String), 一种通过移动终端之间的无线连接向移动终端提供卡拉OK服务的方法。 移动终端被分组为一个服务组,其中一个被指定为主移动终端,而其他移动终端被指定为从移动终端。 主移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制从服务组的所有移动终端中的卡拉OK服务提供商接收的服务内容。 如果主移动终端向从移动终端发送播放命令,则所有移动终端根据服务内容开始播放卡拉OK音乐。(String), US10/761970(String), 1074614400(Integer), US7142807B2(String), 1164643200(Integer), 1164643200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 3(Integer), 9(Integer), JP2000122671A | US5588842A | US5689081A | US5691494A | US5824934A | US5885085A | US6062868A | US6074215A | USRE37131E1(String), \20230420\f785db5d5d704237b772c2f005a2ac1b.png(String), 15(Integer), 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 1. A method of providing a Karaoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals having a wireless connection function to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating all other mobile terminals as slave mobile terminals;connecting the master mobile terminal to a Karaoke service provider through a mobile communication network and controlling service content to be received from theKaraoke service provider in all the mobile terminals of the service group; and playing Karaoke music according to the service content by all the mobile terminals in the service group when the master mobile terminal transmits a play command to the slave mobile terminals, wherein the master and slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 1.一种通过无线连接向移动终端提供卡拉OK服务的方法,包括步骤:将移动终端与具有无线连接功能的移动终端分组为一个服务组,以接收卡拉OK业务;指定其中一个移动终端为主移动终端;将所有其他移动终端指定为从属移动终端;通过移动通信网络将主移动终端连接到卡拉OK服务提供商,并控制从主移动终端接收的服务内容服务组所有移动终端中的卡拉OK服务商;主移动终端向从移动终端发送播放命令时,服务组内的所有移动终端根据服务内容播放卡拉OK音乐,其中主从移动终端根据导频时钟信号进行同步在播放步骤中同时播放。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 2. The method of claim 1, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 2.如权利要求1所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 3. The method of claim 1, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 3.如权利要求1所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 4. The method of claim 1, wherein the step of controlling the service content to be received comprises the steps of:searching for the service content from the Karaoke service provider;transmitting information about the service content to the slave mobile terminals in the service group; andreceiving the service content from the Karaoke service provider according to the service content information in the master mobile terminal and the slave mobile terminals to receive.(String), 4.如权利要求1所述的方法,其中控制接收服务内容的步骤包括:从卡拉OK服务提供商处搜索服务内容;向服务组中的从属移动终端发送服务内容信息;和主移动终端和从移动终端根据服务内容信息从卡拉OK服务商处接收服务内容。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 5. The method of claim 1, wherein the step of controlling the service content comprises the steps of:searching for the service content from the Karaoke service provider;receiving the service content from the Karaoke service provider in the master mobile terminal; andtransmitting the service content from the master mobile terminal to the slave mobile terminals by wireless connections between the master mobile terminal and the slave mobile terminals.(String), 5.如权利要求1所述的方法,其中控制服务内容的步骤包括以下步骤:从卡拉OK服务提供商处搜索服务内容;在主移动终端中接收来自卡拉OK服务提供商的服务内容;和通过主移动终端和从移动终端之间的无线连接将主移动终端的业务内容传输到从移动终端。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 6. A method of providing a Kraoke service to a mobile terminal through a wireless connection, comprising the steps of:grouping the mobile terminal with mobile terminals to receive the Karaoke service together as a service group;designating one of the mobile terminals as a master mobile terminal;designating the other mobile terminals as slave mobile terminals;receiving, in the slave mobile terminals, service contents from a Karaoke service provider under control of the master mobile terminal; andplaying Karaoke music according to the service contents if the slave mobile terminals receive a play command from the master mobile terminal, wherein the master and the slave mobile terminals are synchronized according to a pilot channel clock signal for simultaneously playing in the playing step.(String), 6.一种通过无线连接向移动终端提供Kraoke服务的方法,包括步骤:将移动终端与接收卡拉OK业务的移动终端分组为一个业务组;指定其中一个移动终端为主移动终端;指定其他移动终端为从移动终端;从属移动终端接收主移动终端控制下的卡拉OK服务商的服务内容;和如果从移动终端接收到主移动终端的播放命令,则根据业务内容播放卡拉OK音乐,其中在播放步骤中,主从移动终端根据导频时钟信号同步同步播放。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 7. The method of claim 6, wherein the wireless connection is carried out by one of Bluetooth, IRDA (Infrared Data Association), and wireless LAN (Local Area Network).(String), 7.如权利要求6所述的方法,其中无线连接通过蓝牙、IRDA(红外数据协会)和无线LAN(局域网)之一进行。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 8. The method of claim 6, further comprising the step of, when a call connection is attempted for the mobile terminal, releasing the mobile terminal from the service group and connecting a call to the mobile terminal.(String), 8.如权利要求6所述的方法,还包括步骤:当移动终端尝试呼叫连接时,将移动终端从服务组中释放,并连接移动终端的呼叫。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 9. The method of claim 6, wherein the step ofreceiving the service contents, comprises the steps of:transmitting information about the service contents from the Karaoke service provider to the slave mobile terminals through the master mobile terminal; andconnecting the slave mobile terminals to the Karaoke service provider and transmitting the service contents to the slave mobile terminal.(String), 9.如权利要求6所述的方法,其中的步骤接收服务内容,包括以下步骤:将卡拉OK服务商的服务内容信息通过主移动终端传输给从移动终端;和将从移动终端连接到卡拉OK服务提供商,并将服务内容传输到从移动终端。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 10. The method of claim 6, wherein the slave mobile terminals receive the service contents from the master mobile terminal by the wireless connection.(String), 10.如权利要求6所述的方法,其中从移动终端通过无线连接从主移动终端接收服务内容。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 11. The method of claim 6, wherein the slave mobile terminals are further grouped as a predetermined number of sub-service groups according to a number of channels.(String), 11.如权利要求6所述的方法,其中从属移动终端根据频道数进一步分组为预定数量的子业务组。(String), 1(Integer), 10(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 12. The method of claim 11, wherein each of the sub-service groups receives different sound data and plays Karaoke music according to the sound data.(String), 12.如权利要求11所述的方法,其中每个子服务组接收不同的声音数据,并根据声音数据播放卡拉OK音乐。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 13. The method of claim 12, wherein the sound data is from one of a left channel and a right channel for stereo sound.(String), 13.如权利要求12所述的方法,其中声音数据来自立体声的左声道和右声道之一。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 14. The method of claim 12, wherein the sound data is from one of channels for digital surround sound 5.1.(String), 14.如权利要求12所述的方法,其中声音数据来自数字环绕声5.1的通道之一。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185928(Integer), 15. The method of claim 12, wherein the sound data is from one of a predetermined number of sound sources divided from multiple sound sources.(String), 15.如权利要求12所述的方法,其中声音数据来自多个声源划分的预定数量的声源之一。(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 112498(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 185928(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119 to an application entitled “Method of Providing Karaoke Service to Mobile Terminals Using Wireless Connection between the Mobile Terminals” filed in the Korean Industrial Property Office on Feb. 13, 2003 and assigned Serial No. 2003-8989, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to a method of providing a service through a mobile terminal, and in particular, to a method of providing a Karaoke service to a mobile terminal, and providing a computer-readable recording medium to record a program thereon for performing the Karaoke service method. [0004]2. Description of the Related Art [0005]Due to its portability and convenience, the mobile terminal has emerged as a necessity in daily living. Commonly, mobile terminals are equipped with a variety of functions including phonebook and scheduler. Accordingly, they serve as a personal information manager in addition to a means for making phone calls. 2.5th generation mobile terminals, based on IS (International Standard)-95C, and 3rd generation mobile terminals such as IMT (International Mobile Communication)-2000 terminals provide additional multimedia service for personal entertainment purposes. [0006]A Karaoke function, a type of personal entertainment service, plays songs across various genres with lyrics and animation through a mobile terminal. FIG. 1 illustrates a mobile communication system for providing a conventional Karaoke service. Referring to FIG. 1, the Karaoke service is provided over a typical mobile communication network. Hence, the Karaoke service is provided directly from a service provider (SP) over the mobile communication network rather than a service from the mobile communication network itself. [0007]The mobile communication system is comprised of a mobile terminal 11 for receiving the Karaoke service over the mobile communication network, a home location register (HLR) 12 and an authentication center (AC) 13 for providing the registration information of the mobile terminal 11, a mobile communication network 14 for connecting SPs to users, and a Karaoke SP 15 for providing the Karaoke service. [0008]In operation, the user of the mobile terminal 11 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 then authenticates the user through the HLR 12 and the AC 13 and provides the audio data stored in its database to the user. The mobile terminal 11 plays the song with its lyric displayed using the received audio data, enabling the user to sing along. [0009]In general, a user enjoys Karaoke music with others rather than alone. The volume of music that a single mobile terminal plays depends on its speaker and is usually not loud enough for a plurality of users to enjoy the music. In addition, no matter how good the speaker is, it cannot offer enough volume for them with the single sound source. [0010]In view of diverse voice services and rapid changes in their formats, the Karaoke SP 15 attempts to attract mobile subscribers with new features such as accompaniment with multichannel surround sound effects including stereo, or accompaniment with higher-note polyphonic sound through the existing mobile terminal limited to a 40-note polyphonic sound capacity. However, with the service deployment depending on the performance of an individual mobile terminal in the conventional technology, the benefits of those services are often elusive. SUMMARY OF THE INVENTION [0011]It is, therefore, an object of the present invention to provide a Karaoke service method using wireless connections between mobile terminals that are equipped with a Karaoke function, for playing music accompaniment concurrently through the mobile terminals by synchronizing them, and a computer-readable recording medium for recording a program thereon for performing the Karaoke service. [0012]It is another object of the present invention to provide a Karaoke service method for playing music with a high volume, surround sound effects, and various sound sources. [0013]The above and other objects are achieved by providing a method of providing a Karaoke service to a mobile terminal through wireless connections, and a computer-readable recording medium having a program thereon to perform the Karaoke service. [0014]According to one aspect of the present invention, in the Karaoke service method, the mobile terminal is grouped as a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group. The master mobile terminal transmits a play command to the slave mobile terminals, and all the mobile terminals start to play Karaoke music according to the service contents. [0015]According to another aspect of the present invention, in the Karaoke service method, a mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal. Upon receiving a play command from a master mobile terminal, it starts to play Karaoke music according to the service contents. [0016]According to a further aspect of the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. In the first function, a mobile terminal is grouped in a service group with mobile terminals having a wireless connection function to receive the Karaoke service. One of the mobile terminals is designated as a master mobile terminal and the other mobile terminals are designated as slave mobile terminals. The mobile terminal designated as the master mobile terminal in the first function is connected to a Karaoke service provider through a mobile communication network and controls service contents to be received from the Karaoke service provider in all the mobile terminals of the service group in the second function. The master mobile terminal transmits a play command to the slave mobile terminals, and then all the mobile terminals start to play Karaoke music according to the service contents in the third function. [0017]According to still another aspect o the present invention, a computer-readable recording medium has a program recorded thereon to perform first, second, and third functions in a mobile terminal having a processor. The program performs first, second, and third functions. In the first function, the mobile terminal is grouped in a service group with mobile terminals to receive the Karaoke service and is designated as a master or slave mobile terminal in the service group. If the mobile terminal is designated as a slave mobile terminal, the mobile terminal receives service contents from a Karaoke service provider under the control of the master mobile terminal in the second function. Upon receiving a play command from the master mobile terminal, a slave mobile terminal starts to play Karaoke music according to the service contents in the third function. BRIEF DESCRIPTION OF THE DRAWINGS [0018]The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which: [0019]FIG. 1 illustrates a mobile communication system that provides a conventional Karaoke service to a mobile terminal; [0020]FIG. 2 illustrates the configuration of a mobile communication system that provides a Karaoke service to a plurality of mobile terminals through wireless connections between them according to an embodiment of the present invention; [0021]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention; [0022]FIG. 4 illustrates examples of screen displays in a mobile terminal for receiving the Karaoke service through wireless connection with other mobile terminals according to the embodiment of the present invention; and [0023]FIGS. 5A and 5B illustrate embodiments of contents reception for the Karaoke service through wireless connections with other mobile terminals according to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0024]Preferred embodiments of the present invention will be described in detail herein below with reference to the accompanying drawings. In the following description, well-known functions and constructions are not described in detail since they would obscure the invention in unnecessary detail. [0025]FIG. 2 illustrates a mobile communication system for providing a Karaoke service to mobile terminals through wireless connections between them according to an embodiment of the present invention. Referring to FIG. 2, the mobile communication system is comprised of a master mobile terminal 21 that receives the Karaoke service over a mobile communication network 14, slave mobile terminals 22 connected to the master mobile terminal 21, for receiving the same Karaoke service, the HLR 12 and the SC 13 for providing registration information for the mobile terminals 21 and 22, the mobile communication network 14 for connecting SPs to mobile subscribers, and a Karaoke SP 15 for providing a Karaoke service. [0026]In operation, the master mobile terminal 21 is connected to the slave mobile terminals 22, forming a service group. The user of the master mobile terminal 21 selects an intended song and requests its audio data from the Karaoke SP 15 through the mobile communication network 14. The Karaoke SP 15 authenticates the user through the HLR 12 and the AC 13 and transmits the audio data to the master mobile terminal 21 and the slave mobile terminals 22. When the master mobile terminal 21 transmits a play command to the slave mobile terminals 22, the master and slave mobile terminals 21 and 22 start to simultaneously play the song, displaying its lyrics using the audio data, enabling users sing along. [0027]This method of providing the Karaoke service to mobile terminals by synchronizing them will be described below with reference to FIG. 3. [0028]FIG. 3 is a flowchart illustrating an operation for providing the Karaoke service to mobile terminals through wireless connections between them according to the embodiment of the present invention. Referring to FIG. 3, the mobile terminals equipped with the functions of wireless Internet browsing, Karaoke music playing, and wireless connection are grouped in a service group in step 31. The wireless connections refer to connections between mobile terminals by Bluetooth, IRDA (Infrared Data Association), or wireless LAN (Local Area Network). The service group, corresponding to a working group in a PC (Personal Computer) network, is set by assigning the same wireless connection address to the mobile terminals. Thus, interference from other mobile terminals having a different wireless connection address is avoided. [0029]In step 32, one of the mobile terminals in the service group is designated as a mater mobile terminal with the other mobile terminals designated as slave terminals. The designation of master and slave MT's will be described in more detail hereinbelow with reference to FIG. 4. [0030]FIG. 4 illustrates examples of screen displays related to the Karaoke service in a mobile terminal according to the embodiment of the present invention. Referring to FIG. 4, a service group window 41 displays a wireless connection address assigned commonly to mobile terminals in the same service group, and a mobile terminal state window 42 displays the state of the mobile terminal, i.e., master or slave. [0031]To provide the Karaoke service in various modes, a slave grouping can be further divided into a slave channel 1, a slave channel 2, etc. If the Karaoke SP provides multichannel sound, that is, the audio is divided into discrete channels, center, left front, right front, left rear, and right rear, slave channel 1 outputs one of the channels such as the right channel for stereo sound or the left rear channel for digital surround sound 5.1, slave channel 2 outputs another channel, and the other channels output their respective channel sound. When sound from multiple sound sources is divided into 16- to 40-note polyphonic sounds, each channel may output its assigned sounds. [0032]The mobile terminal state is set to “master” only for a master mobile terminal. The master mobile terminal can remotely control the Internet and Karaoke functions of the slave mobile terminals through the wireless connections between them. [0033]Returning to FIG. 3, after the master mobile terminal 21 selects a song and requests the song from the Karaoke SP 15 through the mobile communication network 14, the master and slave mobile terminals 21 and 22 receive service contents related to the song from the Karaoke SP 15 in step 33. The contents reception is carried out in two ways, which will be described later with reference to FIGS. 5A and 5B. [0034]When the master mobile terminal 21 sends a play command to the slave mobile terminals 22 through wireless connection, for example, by Bluetooth, IRDA, or wireless LAN, all the mobile terminals 21 and 22 in the service group start to play the song simultaneously, synchronized according to a pilot channel clock signal in step 34. [0035]Upon request for a call setup for any mobile terminal in the service group during the music accompaniment playing, the mobile terminal is released from synchronization and connected to a call. The call setup request acts as an interrupt to the Karaoke service. [0036]FIGS. 5A and 5B illustrate embodiments of the contents reception in the Karaoke service using wireless connection between mobile terminals according to the present invention. Referring to FIG. 5A, a mobile terminal 51 is designated as a master and mobile terminals 52 are designated as slaves in a service group. After the service group is set in step 31 and the master and slave mobile terminals 51 and 52 are designated in step 32, the mobile terminals 51 and 52 receive service contents (i.e., Karaoke audio data) from the Karaoke SP 15 in step 33 in FIG. 4. [0037]Describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in the Karaoke SP 15 through the mobile communication network 14 in step 501 and transmits a contents receive command to the slave mobile terminals 52 in step 502. Since the master mobile terminal 51 can remotely control the wireless Internet function of the slave mobile terminals 52, the master mobile terminal 51 and the slave mobile terminals 52 under the control of the master mobile terminal 51 receive the same service contents in step 503. [0038]Referring to FIG. 5B, describing step 33 in more detail, the master mobile terminal 51 selects a song from a music database in step504 and receives receive service contents from the Karaoke SP 15 through the mobile communication network 14 in step 505. The master mobile terminal 51 then transmits the service contents to the slave mobile terminals by wireless connection in step 506. [0039]The contents receiving method illustrated in FIG. 5A enables each mobile terminal to receive a different channel or a different sound source since master and slave mobile terminals all access the Karaoke SP. If the SP prohibits content duplication and reproduction, retransmission of the service contents from the master mobile terminal to the slave mobile terminals is not permitted. In this sense, the method of FIG. 5A is useful. When accessing the SP, each slave mobile terminal transmits a packet indicating a slave channel to receive corresponding channel contents. [0040]Alternatively, rates for using service contents are saved and the same data can be broadcast to mobile terminals in the same service group in the content receiving method illustrated in FIG. 5B. [0041]As described above, the present invention offers the following benefits: (1) provision of Karaoke music with high volume, surround sound effects, and multiple sound sources improves the quality of the Karaoke service; (2) since a plurality of mobile terminals download the same audio data from an SP and users enjoy the Karaoke service through their mobile terminals together rather than alone, the number of service connections is increased and the novel service deployment attracts more customers from an SP's point of view; (3) the extension of the use of wireless data communication between mobile terminals enables mobile terminal manufacturers to create new customer demands; and (4) a program for carrying out the Karaoke service can be written on a computer-readable recording medium (e.g., CD ROM, RAM, floppy disk, hard disk, and optomagnetic disk). [0042]While the present invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. § 119 于 2003 年 2 月 13 日向韩国工业产权局提交的题为“使用移动终端之间的无线连接向移动终端提供卡拉 OK 服务的方法”的申请,编号为 2003-8989,其内容为 通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明总体上涉及一种通过移动终端提供服务的方法,具体地,涉及一种向移动终端提供卡拉OK服务的方法,以及提供一种计算机可读记录介质以在其上记录用于执行该服务的程序的计算机可读记录介质。 卡拉OK服务方法。 [0004] 2.相关技术的描述 [0005] 由于其便携性和便利性,移动终端已成为日常生活中的必需品。 通常,移动终端配备有电话簿、日程安排等多种功能。 因此,除了拨打电话之外,它们还充当个人信息管理器。 2.5 th 一代移动终端,基于IS(国际标准)-95C,和3 rd 一代移动终端,例如 IMT(国际移动通信)-2000 终端,为个人娱乐目的提供额外的多媒体服务。 [0006] 卡拉OK功能是一种个人娱乐服务,通过移动终端播放带有歌词和动画的各种类型的歌曲。 如图。 图1图示了用于提供传统卡拉OK服务的移动通信系统。 参考图。 如图1所示,卡拉OK服务是通过典型的移动通信网络提供的。 因此,卡拉OK服务是直接从移动通信网络上的服务提供商(SP)提供的,而不是来自移动通信网络本身的服务。 [0007] 移动通信系统由移动终端组成 11 为了通过移动通信网络接收卡拉 OK 服务,归属位置寄存器 (HLR) 12 和认证中心(AC) 13 用于提供移动终端的注册信息 11 , 移动通信网络 14 用于将 SP 连接到用户,以及卡拉 OK SP 15 提供卡拉OK服务。 [0008] 在操作中,移动终端的用户 11 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 然后通过 HLR 对用户进行身份验证 12 和交流 13 并将存储在其数据库中的音频数据提供给用户。 移动终端 11 使用接收到的音频数据播放带有歌词的歌曲,使用户能够跟着唱。 [0009] 一般而言,用户与他人而不是单独一起享受卡拉OK音乐。 单个移动终端播放的音乐音量取决于其扬声器,并且通常不足以让多个用户欣赏音乐。 另外,再好的音箱,单声源也无法为他们提供足够的音量。 [0010] 鉴于语音服务的多样化和格式的快速变化,卡拉 OK SP 15 试图通过新功能来吸引移动用户,例如伴奏包括立体声在内的多声道环绕声效果,或通过现有的仅限于 40 音符复音容量的移动终端伴奏更高音符的复音。 然而,在传统技术中,服务部署依赖于单个移动终端的性能,这些服务的好处往往难以捉摸。 发明内容 [0011] 因此,本发明的一个目的是提供一种卡拉OK服务方法,该方法使用配备有卡拉OK功能的移动终端之间的无线连接,通过移动终端同步来同时播放音乐伴奏,以及一种计算机可读记录。 用于在其上记录用于执行卡拉OK服务的程序的介质。 [0012]本发明的另一目的在于提供一种卡拉OK服务方法,用于播放具有高音量、环绕声效果和多种音源的音乐。 [0013] 通过提供一种通过无线连接向移动终端提供卡拉OK服务的方法,以及其上具有用于执行卡拉OK服务的程序的计算机可读记录介质来实现上述和其他目的。 [0014] 根据本发明的一个方面,在卡拉OK服务方法中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容。 主移动终端向从移动终端发送播放命令,所有移动终端根据服务内容开始播放卡拉OK音乐。 [0015] 根据本发明的另一方面,在卡拉OK服务方法中,将移动终端与移动终端分组在服务组中以接收卡拉OK服务,并指定为服务组中的主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 主移动终端收到播放指令后,根据服务内容开始播放卡拉OK音乐。 [0016] 根据本发明的另一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 在第一功能中,移动终端与具有无线连接功能的移动终端组成一个服务组,以接收卡拉OK服务。 移动终端之一被指定为主移动终端,而其他移动终端被指定为从移动终端。 在第一功能中被指定为主移动终端的移动终端通过移动通信网络连接到卡拉OK服务提供商,并在第二功能中控制服务组的所有移动终端中从卡拉OK服务提供商接收的服务内容 . 主移动终端向从移动终端发送播放命令,然后所有移动终端根据第三功能中的服务内容开始播放卡拉OK音乐。 [0017] 根据本发明的又一方面,一种计算机可读记录介质具有记录在其上的程序以在具有处理器的移动终端中执行第一、第二和第三功能。 该程序执行第一、第二和第三功能。 在第一个功能中,将移动终端与移动终端分组在一个服务组中以接收卡拉OK服务,并在服务组中将移动终端指定为主移动终端或从移动终端。 如果移动终端被指定为从移动终端,则移动终端在第二功能中在主移动终端的控制下从卡拉OK服务提供商接收服务内容。 从移动终端接收到主移动终端的播放命令后,根据第三功能中的服务内容开始播放卡拉OK音乐。 附图的简要说明 [0018] 本发明的上述和其他目的、特征和优点将在以下结合附图的详细描述中变得更加明显,其中: [0019] 如图。 附图说明图1示出了向移动终端提供传统卡拉OK服务的移动通信系统; [0020]如图。 图2示出了根据本发明实施例的通过多个移动终端之间的无线连接向多个移动终端提供卡拉OK服务的移动通信系统的配置。 [0021] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 [0022] 如图。 图4示出了根据本发明实施例的通过与其他移动终端的无线连接来接收卡拉OK服务的移动终端中的屏幕显示示例。 和 [0023] 图 图5A和5B示出了根据本发明通过与其他移动终端的无线连接来接收卡拉OK服务的内容的实施例。 优选实施例的详细说明 [0024] 下面结合附图对本发明的优选实施例进行详细说明。 在以下描述中,没有详细描述众所周知的功能和结构,因为它们会以不必要的细节模糊本发明。 [0025] 如图。 图2图示了根据本发明实施例的用于通过移动终端之间的无线连接向移动终端提供卡拉OK服务的移动通信系统。 参考图。 2、移动通信系统由主移动终端组成 21 通过移动通信网络接收卡拉 OK 服务的 14 , 从移动终端 22 连接到主移动终端 21 ,为了接收相同的卡拉 OK 服务,HLR 12 和 SC 13 为移动终端提供注册信息 21 和 22 , 移动通信网络 14 用于将 SP 连接到移动用户,以及卡拉 OK SP 15 提供卡拉 OK 服务。 [0026] 在操作中,主移动终端 21 连接到从移动终端 22 ,形成服务群。 主移动终端用户 21 选择想要的歌曲并从 Karaoke SP 请求其音频数据 15 通过移动通信网络 14 . 卡拉 OK SP 15 通过 HLR 对用户进行身份验证 12 和交流 13 并将音频数据传输到主移动终端 21 和从移动终端 22 . 当主控移动终端 21 向从移动终端发送播放命令 22 ,主从移动终端 21 和 22 开始同时播放歌曲,使用音频数据显示歌词,让用户跟着唱。 [0027] 下面将参照图3描述通过同步移动终端向移动终端提供卡拉OK服务的这种方法。 3. [0028] 如图。 图3是示出根据本发明实施例的通过移动终端之间的无线连接向移动终端提供卡拉OK服务的操作的流程图。 参考图。 3、将具备无线上网浏览、卡拉OK音乐播放、无线连接功能的移动终端分步归入一个服务组 31 . 无线连接是指移动终端之间通过蓝牙、IRDA(红外数据协会)或无线LAN(局域网)的连接。 通过为移动终端分配相同的无线连接地址来设置服务组,对应于PC(个人计算机)网络中的工作组。 因此,避免了来自具有不同无线连接地址的其他移动终端的干扰。 [0029] 在步骤 32 ,服务组中的一个移动终端被指定为主移动终端,其他移动终端被指定为从终端。 下文将参考图1更详细地描述主MT和从MT的指定。 4. [0030]如图。 图4图示了根据本发明实施例的移动终端中与卡拉OK服务相关的屏幕显示的示例。 参考图。 4、一个服务组窗口 41 显示同一服务组内移动终端通用分配的无线连接地址,移动终端状态窗口 42 显示移动终端的状态,即主或从。 [0031] 为了提供各种模式的卡拉OK服务,一个从属分组可以进一步划分为一个从属频道 1 , 从属通道 2 等。如果Karaoke SP提供多声道声音,即音频分为离散声道,中、左前、右前、左后、右后,从声道 1 输出其中一个声道,例如用于立体声的右声道或用于数字环绕声的左后声道 5 . 1 , 从通道 2 输出另一个通道,其他通道输出各自通道的声音。 当来自多个声源的声音被分成 16 到 40 音符的复音时,每个通道都可以输出其分配的声音。 [0032] 移动终端状态仅针对主移动终端设置为“主”。 主移动终端可以通过它们之间的无线连接远程控制从移动终端的上网和卡拉OK功能。 [0033] 返回图。 3、掌握移动端后 21 选择一首歌曲并向卡拉 OK SP 请求歌曲 15 通过移动通信网络 14 ,主从移动终端 21 和 22 从卡拉 OK SP 接收与歌曲相关的服务内容 15 在一步 33 . 内容接收以两种方式进行,这将在后面参考图3和图4进行描述。 参见图 5A 和 5B。 [0034] 当主控移动终端 21 向从移动终端发送播放命令 22 通过无线连接,例如通过蓝牙、IRDA或无线局域网,所有移动终端 21 和 22 在服务组中同时开始播放歌曲,根据一个导频通道时钟信号同步 34 . [0035] 在音乐伴奏播放期间,在服务组中的任何移动终端请求建立呼叫时,移动终端从同步中释放并连接到呼叫。 呼叫建立请求充当卡拉 OK 服务的中断。 [0036] 图 图5A和5B示出了根据本发明的使用移动终端之间的无线连接的卡拉OK服务中的内容接收的实施例。 参考图。 5A、移动终端 51 被指定为主机和移动终端 52 被指定为服务组中的从属设备。 步骤中设置服务组后 31 以及主从移动终端 51 和 52 在步骤中指定 32 , 移动终端 51 和 52 从卡拉 OK SP 接收服务内容(即卡拉 OK 音频数据) 15 在一步 33 在图 4. [0037] 描述步骤 33 更详细地说,主移动终端 51 从卡拉 OK SP 中的音乐数据库中选择一首歌曲 15 通过移动通信网络 14 在一步 501 向从移动终端发送内容接收命令 52 在一步 502 . 自主移动端 51 可远程控制从属移动终端的无线上网功能 52 ,主移动终端 51 和从移动终端 52 在主移动终端的控制下 51 在步骤中接收相同的服务内容 503 . [0038] 参考图。 5B,描述步骤 33 更详细地说,主移动终端 51 在步骤中从音乐数据库中选择一首歌曲 504 并从卡拉 OK SP 接收接收服务内容 15 通过移动通信网络 14 在一步 505 . 主控移动终端 51然后在步骤中通过无线连接将服务内容传输到从移动终端 506 . [0039] 图1所示的内容接收方法。 由于主移动终端和从移动终端都访问卡拉OK SP,因此图5A使每个移动终端能够接收不同的频道或不同的声源。 如果SP禁止内容复制和再现,则不允许将服务内容从主移动终端重传到从移动终端。 在这个意义上,图1的方法。 5A很有用。 在接入SP时,每个从移动终端发送一个指示从信道的分组以接收相应的信道内容。 [0040] 或者,在图1所示的内容接收方法中,可以保存使用服务内容的费率并将相同的数据广播到相同服务组中的移动终端。 5B。 [0041] 如上所述,本发明提供以下益处: (1)提供具有高音量、环绕声效果和多声源的卡拉OK音乐,提高了卡拉OK服务的质量。 (2)由于多个移动终端从一个SP下载相同的音频数据,用户通过他们的移动终端一起而不是单独享受卡拉OK服务,增加了服务连接的数量,新颖的业务部署吸引了更多来自SP的客户 观点看法; (3)移动终端之间无线数据通信使用的延伸,使移动终端制造商能够创造新的客户需求; (4)可以将用于进行卡拉OK服务的程序写入计算机可读取的记录介质(例如CD ROM、RAM、软盘、硬盘、光磁盘)上。 [0042] 尽管本发明已经参照其某些优选实施例进行了展示和描述,但本领域技术人员将理解,在不背离所定义的本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变 根据所附权利要求。(String), 112498(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:18.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN1295910C(String), CN1522010A(String), KR100532288B1(String), KR1020040073057A(String), US20040162062A1(String), US7142807B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271643(Integer), CN1295910C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271643(Integer), CN1522010A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271643(Integer), KR100532288B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271643(Integer), KR1020040073057A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271643(Integer), US20040162062A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271643(Integer), US7142807B2(String), 1049459(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7142807B2(String), US7142807B2(String), 1164643200(Integer), 271643(Integer), 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.320 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185928(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185928(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185928(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185928(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:19.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185929(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\472693a08f1446658f7b5a895cf77182.png(String), 185929(Integer), 472693a08f1446658f7b5a895cf77182.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of changing standby order of waiting mobile terminals in mobile terminal(String), 移动终端中更改等待移动终端待机顺序的方法(String), US7801528B2(String), A method for changing a standby order of waiting mobile terminals includes displaying a standby order of a plurality of mobile terminals according to an audiovisual communication request order when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal, sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a standby order change request, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message, and displaying the changed standby order.(String), 一种用于改变等待移动终端的待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求,而第一移动终端时,根据视听通信请求顺序显示多个移动终端的待机顺序。 与第二移动终端进行视听通信,当第一移动终端接收到待机指令变更请求时,从第一移动终端向移动通信网络发送待机指令变更请求消息,当第一移动终端接收到待机指令变更请求时,变更第一移动终端的待机指令。 移动终端从移动通信网络接收对应于待机命令更改请求消息的待机命令更改完成消息,并显示更改后的待机命令。(String), US11/769201(String), 1182873600(Integer), US7801528B2(String), 1284998400(Integer), 1284998400(Integer), 美国(String), 2(Integer), 4(Integer), KR(String), 2(Integer), 12(Integer), KR1020000042764A | KR1020050017736A | KR1020050053912A | KR1020070012088A | US20020009987A1 | US20030104830A1 | US20060223593A1 | US20080132254A1(String), \20230420\472693a08f1446658f7b5a895cf77182.png(String), 17(Integer), 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 1. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals, according to the order in which the audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;sending a standby order change request message from the first mobile terminal to a mobile communication network when the first mobile terminal receives a request to change the standby order;changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message from the mobile communication network corresponding to the standby order change request message; anddisplaying the changed standby order.(String), 1.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序,而第一移动终端终端与第二移动终端进行视听通信;当第一移动终端接收到待机顺序变更请求时,第一移动终端向移动通信网络发送待机顺序变更请求消息;当第一移动终端从移动通信网络接收到与待机顺序变更请求消息对应的待机顺序变更完成消息时,变更第一移动终端的待机顺序;和显示更改后的待机顺序。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 2. The method of claim 1, further comprising:changing the standby order at the mobile communication network in response to the standby order change request message sent by the first mobile terminal.(String), 2.如权利要求1所述的方法,还包括:响应于第一移动终端发送的待机顺序改变请求消息,改变移动通信网络处的待机顺序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 3. The method of claim 2, further comprising sending the changed standby order to the first mobile terminal through the mobile communication network.(String), 3.如权利要求2所述的方法,还包括通过移动通信网络向第一移动终端发送变更后的待机指令。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 4. The method of claim 1, further comprising performing audiovisual communication with another mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 4.如权利要求1所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与另一移动终端进行视听通信。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 5. A method for changing a standby order in a mobile communication system, comprising:displaying a standby order of a plurality of mobile terminals according to the order in which audiovisual communication request orders of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal performs audiovisual communication with a second mobile terminal;determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals;changing the standby order if the first mobile terminal approves the requested change of the standby order; anddisplaying the changed standby order.(String), 5.一种在移动通信系统中改变待机顺序的方法,包括:当第一移动终端接收到来自多个移动终端的视听通信请求时,根据接收到多个移动终端的视听通信请求命令的顺序显示多个移动终端的待机顺序,而第一移动终端与第二移动终端进行视听通信;当第一移动终端接收到多个移动终端中的第三移动终端的待机顺序变更请求消息时,判断第一移动终端是否同意请求的待机顺序变更;如果第一移动终端同意请求更改备用订单,则更改备用订单;和显示更改后的待机顺序。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 6. The method of claim 5, wherein determining whether the first mobile terminal approves the requested change of the standby order comprises:receiving the standby order change request message of the third mobile terminal from a mobile communication network; andsending a standby order change approval message to the mobile communication network when the standby order change request is approved in response to the received standby order change request message.(String), 6.如权利要求5所述的方法,其中判断第一移动终端是否同意请求的待机顺序变更包括:从移动通信网络接收第三移动终端的待机顺序变更请求消息;和当响应于接收到的备用订单变更请求消息批准备用订单变更请求时,向移动通信网络发送备用订单变更批准消息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 7. The method of claim 6, wherein changing the standby order comprises:receiving a standby order change completion message from the mobile communication network; andchanging the standby order according to the standby order change completion message.(String), 7.如权利要求6所述的方法,其中更改备用订单包括:接收来自移动通信网络的备用订单变更完成消息;和根据备用订单变更完成消息变更备用订单。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 8. The method of claim 6, wherein receiving the standby order change request message of the third mobile terminal comprises:sending a standby order change request message from the third mobile terminal to the mobile communication network; andreceiving the standby order change request message of the third mobile terminal from the mobile communication network in the first mobile terminal.(String), 8.如权利要求6所述的方法,其中接收第三移动终端的待机顺序变更请求消息包括:第三移动终端向移动通信网络发送待机顺序变更请求消息;和第一移动终端中从移动通信网络接收第三移动终端的待机顺序变更请求消息。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 9. The method of claim 8, wherein changing the standby order comprises:receiving the standby order change approval message sent from the first mobile terminal in the mobile communication network; andchanging the standby order.(String), 9.如权利要求8所述的方法,其中更改备用订单包括:接收移动通信网络中的第一移动终端发送的备用订单变更批准消息;和更改待机顺序。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 10. The method of claim 9, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal.(String), 10.如权利要求9所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端发送待机顺序改变完成消息。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 11. The method of claim 8, wherein the standby order change request message sent from the third mobile terminal is sent by the mobile communication network to the first mobile terminal and to a fourth mobile terminal of the plurality of mobile terminals.(String), 11.如权利要求8所述的方法,其中第三移动终端发送的待机顺序变更请求消息由移动通信网络发送给第一移动终端和多个移动终端中的第四移动终端。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 12. The method of claim 11, wherein changing the standby order comprises:receiving response messages to the standby order change request message from the first mobile terminal and from the fourth mobile terminal in the communication network; andchanging the standby order.(String), 12.如权利要求11所述的方法,其中更改备用订单包括:从通信网络中的第一移动终端和第四移动终端接收对待机顺序改变请求消息的响应消息;和更改待机顺序。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 13. The method of claim 12, wherein the mobile communication network changes the standby order according to the response messages if the response messages received from the first mobile terminal and from the fourth mobile terminal are identical.(String), 13.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息相同,则移动通信网络根据响应消息改变待机顺序。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 14. The method of claim 12, wherein the mobile communication network changes the standby order according to the response message of the first mobile terminal if the response messages received from the first mobile terminal and from the fourth mobile terminal are not identical.(String), 14.如权利要求12所述的方法,其中如果从第一移动终端和第四移动终端接收到的响应消息不相同,则移动通信网络根据第一移动终端的响应消息改变待机顺序。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 15. The method of claim 14, wherein changing the standby order further comprises sending a standby order change completion message from the mobile communication network to the first mobile terminal, the third mobile terminal, and the fourth mobile terminal.(String), 15.如权利要求14所述的方法,其中改变待机顺序进一步包括从移动通信网络向第一移动终端、第三移动终端和第四移动终端发送待机顺序改变完成消息。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.441 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 16. The method of claim 12, wherein the response message to the standby order change request message is one of a standby order change approval message and a standby order change non-approval message.(String), 16.如权利要求12所述的方法,其中备用订单变更请求消息的响应消息为备用订单变更批准消息和备用订单变更不批准消息之一。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.441 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185929(Integer), 17. The method of claim 5, further comprising performing audiovisual communication with a mobile terminal according to the standby order when the first mobile terminal ends audiovisual communication with the second mobile terminal or converts a state of audiovisual communication with the second mobile terminal to a standby state.(String), 17.如权利要求5所述的方法,还包括当第一移动终端结束与第二移动终端的视听通信或将与第二移动终端的视听通信状态转为待机状态时,根据待机指令与移动终端进行视听通信。(String), 1(Integer), 16(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById ==> Parameters: 112499(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Preparing: UPDATE os_patent_instruction_text SET patent_id=?, manual=?, manual_out=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById ==> Parameters: 185929(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority from and the benefit of Korean Patent Application No. 10-2007-0004601, filed on Jan. 16, 2007, which is hereby incorporated by reference for all purposes as if fully set forth herein. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method of providing an audiovisual communication service in a mobile terminal, and more particularly, to a method of changing a standby order of waiting mobile terminals in a mobile terminal. [0004]2. Discussion of the Background [0005]As technology of mobile terminals has developed, an improved mobile terminal having a camera unit using an H.324M protocol including an H.245 protocol that allows for audiovisual communication has been provided. [0006]In conventional audiovisual communication technology, when a first mobile terminal receives a request for audiovisual communication from a third mobile terminal while the first mobile terminal is performing audiovisual communication with a second mobile terminal, the first mobile terminal stores information about the third mobile terminal. Thereafter, when the first mobile terminal ends audiovisual communication with the second mobile terminal, the first mobile terminal displays information about the third mobile terminal and performs audiovisual communication with the third mobile terminal. [0007]However, in the conventional audiovisual communication technology, even when the third mobile terminal urgently requests audiovisual communication with the first mobile terminal, the third mobile terminal may have to wait until the first mobile terminal ends audiovisual communication with the second mobile terminal. SUMMARY OF THE INVENTION [0008]The present invention provides a method of changing a standby order of at least two mobile terminals requesting audiovisual communication while a first mobile terminal is performing audiovisual communication. [0009]The present invention further provides a method of changing a standby order of mobile terminals in a standby state according to a standby order change request received from one of at least two mobile terminals waiting for audiovisual communication with the first mobile terminal while the first mobile terminal is performing audiovisual communication. [0010]The present invention further provides a method of displaying information about a mobile terminal requesting audiovisual communication while a first mobile terminal is performing audiovisual communication with a second mobile terminal. [0011]Additional features of the invention will be set forth in the description which follow, and in part will be apparent from the description, or may be learned by practice of the invention. [0012]The present invention discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, sending a standby order change request message to a mobile communication network from the first mobile terminal when the first mobile terminal receives a request to change the standby order, changing the standby order at the first mobile terminal when the first mobile terminal receives a standby order change completion message corresponding to the standby order change request message, and displaying the changed standby order. [0013]The present invention also discloses a method for changing a standby order in a mobile communication system including displaying a standby order of a plurality of mobile terminals, according to the order in which audiovisual communication requests of the plurality of mobile terminals were received, when a first mobile terminal receives requests for audiovisual communication from the plurality of mobile terminals while the first mobile terminal is performing audiovisual communication with a second mobile terminal, determining whether the first mobile terminal approves a requested change of the standby order when the first mobile terminal receives a standby order change request message of a third mobile terminal of the plurality of mobile terminals, changing the standby order if the first mobile terminal approves the requested change of the standby order, and displaying the changed standby order. [0014]It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. [0016]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0017]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0018]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0019]FIG. 4 is a flowchart showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0020]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0021]FIG. 6 is a flowchart showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0022]FIG. 7 is a message flow diagram showing another method of performing audiovisual communication with waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS [0023]The invention is described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements. [0024]It will be understood that when an element or layer is referred to as being “on” or “connected to” another element or layer, it can be directly on or directly connected to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on” or “directly connected to” another element or layer, there are no intervening elements or layers present. [0025]Exemplary embodiments according to the present invention exemplify a mobile terminal that includes a camera unit and is capable of performing audiovisual communication. That is, a mobile terminal according to exemplary embodiments of the present invention may include an information communication device or multimedia device, such as a mobile communication terminal, a mobile phone, a Personal Digital Assistant (PDA), a smart phone, or a notebook computer, that includes a camera unit and is capable of performing audiovisual communication, and applications thereof. [0026]Exemplary embodiments according to the present invention exemplify audiovisual communication. However, the present exemplary embodiments are not limited to audiovisual communication and may be applied to voice communication. [0027]FIG. 1 is a diagram showing a system for providing an audiovisual communication service to mobile terminals according to an exemplary embodiment of the present invention. [0028]Referring to FIG. 1, the system includes a first mobile terminal 100, a second mobile terminal 200, a third mobile terminal 300, a fourth mobile terminal 400, and a mobile communication network 500. [0029]The first mobile terminal may perform audiovisual communication with the second mobile terminal 200 and may receive a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400 while performing audiovisual communication with the second mobile terminal 200. A configuration of the first mobile terminal 100 is described with reference to FIG. 2, and the same configuration may also be applied to the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 and thus, individual descriptions thereof are omitted. [0030]The mobile communication network 500 includes a node to perform the function of a base station, a radio access network (RAN), which is a sub system of the node, a mobile switching center (MSC)/visitor location register (VLR) corresponding to a core network of a circuit switched domain, a home location register (HLR), and a gateway MSC. [0031]The MSC manages call control and mobility of the first mobile terminal 100, and the VLR and the HLR make up a matching device of subscriber information and register and manage information about mobile terminals belonging to the mobile communication network 500 including the first mobile terminal 100. [0032]In the following description, the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 belong to the same mobile communication network 500. However the first mobile terminal 100, the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400 may belong to different mobile communication networks and may be connected through different gateway MSCs. However, it is assumed that a series of processes performed in the RAN, MSC/VLR, HLR, and gateway MSC are performed in the mobile communication network 500. [0033]FIG. 2 is a block diagram showing a configuration of a mobile terminal according to another exemplary embodiment of the present invention. [0034]Referring to FIG. 2, the mobile terminal 100 includes a radio frequency (RF) unit 101, an input unit 103, a controller 105, a camera unit 107, an image processor 109, a display unit 111, a memory unit 113, and an audio unit 115. [0035]The RF unit 101 performs general wireless communication with the second mobile terminal 200, the third mobile terminal 300, the fourth mobile terminal 400, and the mobile communication network 500. For example, the RF unit 101 transmits and receives voice data, character messages, and multimedia messages using the mobile communication network 500. The RF unit 101 sends image data acquired from the camera unit 107 of the first mobile terminal 100 to the second mobile terminal 200 when the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 200. The RF unit 101 further receives image data acquired by the camera unit of the second mobile terminal 200 and image data acquired by the camera units of the third mobile terminal 300 and the fourth mobile terminal 400 requesting audiovisual communication. The image data of the second mobile terminal 200 may be still and/or moving picture data, and the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be still and/or moving image data. Further, when the third mobile terminal 300 and the fourth mobile terminal 400 perform audiovisual communication with the first mobile terminal 100, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may change to moving picture data. [0036]The input unit 103 may include a general keypad. The input unit 103 may include a touch screen, a touch pad, and a scroll wheel. The input unit 103 receives a user manipulation signal to control operation of the first mobile terminal 100 and provides the manipulation signal to the controller 105. [0037]The controller 105 controls the general operation of the first mobile terminal 100. Particularly, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200, receives a request for audiovisual communication from the third mobile terminal 300 and the fourth mobile terminal 400, and sets a standby order of audiovisual communication requests. The controller 105 displays image data (namely, image data of a user of the second mobile terminal 200) of the second mobile terminal 200 performing audiovisual communication in the display unit 111. The controller 105 displays image data from each mobile terminal requesting audiovisual communication, in the order in which the audiovisual communication requests were received, on the display unit 111 of the first terminal 100. [0038]In more detail, the image data of the third mobile terminal 300 and the fourth mobile terminal 400 may be image data mapped to the corresponding mobile terminal and stored in a phone book (not shown) of the first mobile terminal 100. The image data may also be image data acquired by camera units of the third mobile terminal 300 and the fourth mobile terminal 400 when requesting audiovisual communication and may be sent with the request for audiovisual communication. The controller 105 may display the image data of the third mobile terminal 300 and the fourth mobile terminal 400 with thumb-nail type still image data. The controller 105 may also display image data of the second mobile terminal 200, with which the first mobile terminal 100 is performing audiovisual communication, including moving picture data. [0039]The controller 105 sends a standby order change request message REQ_MSG from the first mobile terminal 100 to the mobile communication network 500 through the RF unit 101, receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the changed standby order in the display unit 111. [0040]The controller 105 further receives a standby order change request message REQ_MSG from the mobile terminal having the highest standby position through the mobile communication network 500 and sends a standby order change approval message ACC_MSG to the mobile communication network 500 through the RF unit 101. Thereafter, the controller 105 receives a standby order change completion message RES_MSG from the mobile communication network 500 through the RF unit 101, changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400, and displays the standby order in the display unit 111. [0041]When the controller 105 determines that the first mobile terminal 100 has ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 controls the RF unit 101 to perform audiovisual communication with the mobile terminal having the highest standby position. In the exemplary embodiments, to “end” the audiovisual communication is to terminate a communication channel formed to perform audiovisual communication with the second mobile terminal 200, and to “convert” an audiovisual communication state to a standby state is to convert to a standby state in order to perform audiovisual communication with another mobile terminal while maintaining the communication channel formed to perform audiovisual communication with the second mobile terminal 200. [0042]The camera unit 107 generates a user's image data to send through the RF unit 101. The camera unit 107 includes an image sensor to convert a photo signal of a subject to an analog signal and a signal processor to convert the analog signal to a digital signal. That is, the camera unit 107 converts a photo signal collected through a lens to a digital signal and generates image data with the converted digital signal. [0043]The image processor 109 processes image data generated in the camera unit 107 and image data received through the RF unit 101 into a format corresponding to the display unit 111. [0044]The controller 105 controls the display unit 111 to display various operation states, operation results, and other information from the units of the first mobile terminal 100. The display unit 111 may include a display device such as a liquid crystal display (LCD), organic light emitting diodes (OLED), or a plasma display panel (PDP). [0045]The display unit 111 displays image data input through the RF unit 101 and the camera unit 107 and processed in the image processor 109 in real time, thereby performing audiovisual communication or displaying a photographed image. [0046]The memory unit 113 stores information (for example, information about a setting state and a menu) related to operation of a program allowing the controller 105 to control the first mobile terminal 100. The memory unit 113 stores the standby order of the third mobile terminal 300 and the fourth mobile terminal 400. The memory unit 113 stores image data received from the second mobile terminal 200, the third mobile terminal 300, and the fourth mobile terminal 400, and may also store image data mapped to a corresponding terminal in a phone book (not shown) of the first mobile terminal 100. [0047]The audio unit 115 converts an analog audio signal that is input through a microphone MIC to a digital signal, provides the digital signal to the controller 105, converts a digital audio signal that is output from the controller 105 into an analog audio signal, and reproduces the analog audio signal through a speaker SPK. [0048]FIGS. 3A and 3B are message flow diagrams showing a method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0049]Referring to FIGS. 3A and 3B, while the first mobile terminal 100 performs audiovisual communication with the second mobile terminal 100 (S301), the mobile communication network 500 receives a request for audiovisual communication from the third mobile terminal 300 (S303). At step S301, the first mobile terminal 100 is in an audiovisual communication state, the camera unit 107 of the first mobile terminal 100 acquires an image of a user of the first mobile terminal 100, the image processor 109 processes the user image, the display unit 111 displays the user image, and the microphone MIC and the speaker SPK are converted to an operation state. [0050]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S305). [0051]The third mobile terminal 300 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S307). If the third mobile terminal 300 sustains an audiovisual communication standby state, the third mobile terminal 300 sends a standby state sustenance message to the mobile communication network 500 (S309). [0052]Thereafter, the mobile communication network 500 sends information about the third mobile terminal 300 to the first mobile terminal 100 (S311) and forms a communication channel between the first mobile terminal 100 and the third mobile terminal 300. The information about the third mobile terminal 300 may include contact information and image data of the third mobile terminal 300. [0053]The mobile communication network 500 receives a request for audiovisual communication from the fourth mobile terminal 400 (S313), and sends a message regarding the state of the first mobile terminal 100 to the fourth mobile terminal 400 to notify the fourth mobile terminal 400 that the first mobile terminal 100 is performing audiovisual communication (S315). [0054]The fourth mobile terminal 400 determines whether to sustain an audiovisual communication standby state according to the message from the first mobile terminal 100 received through the mobile communication network 500 (S317). If the fourth mobile terminal 400 sustains an audiovisual communication standby state, the fourth mobile terminal 400 sends a standby state sustenance message to the mobile communication network 500 (S319). [0055]Thereafter, the mobile communication network 500 sends information about the fourth mobile terminal 400 to the first mobile terminal 100 (S321) and forms a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400. The information about the fourth mobile terminal 400 may include contact information and image data of the fourth mobile terminal 400. [0056]The first mobile terminal 100 determines that a communication channel between the first mobile terminal 100 and the third mobile terminal 300 was formed at step S311, and that a communication channel between the first mobile terminal 100 and the fourth mobile terminal 400 is formed at step S321. [0057]Thereafter, the first mobile terminal 100 sets and displays a standby order of the mobile terminals that have requested audiovisual communication by listing the mobile terminals in the order in which their requests were received (S323). In the present exemplary embodiment, because the third mobile terminal 300 requested audiovisual communication earlier than the fourth mobile terminal 400, the third mobile terminal 300 has the highest standby position. [0058]When the first mobile terminal 100 wants to change the displayed standby order (S325), the first mobile terminal 100 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S327). The request to change the standby order is input by selecting image data of the third mobile terminal 300 and the fourth mobile terminal 400 displayed in a change mode or a standby order. [0059]The mobile communication network 500 receives the standby order change request message REQ_MSG and changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 (S329). [0060]The mobile communication network 500 temporarily stores the changed standby order (S331) and sends a standby order change completion message RES_MSG informing the first mobile terminal 100 of the standby order change of the third mobile terminal 300 and the fourth mobile terminal 400 (S333). [0061]The first mobile terminal 100 changes and displays the standby order according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S335). [0062]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S337), the mobile communication network 500 refers to the changed standby order that was temporarily stored at step 331 (S339) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S341). [0063]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S343). [0064]FIG. 4 is a flowchart showing a method of changing the standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0065]Referring to FIG. 4, the controller 105 controls the RF unit 101 to perform audiovisual communication with the second mobile terminal 200 (S401). The controller 105 displays moving picture data received in real time from the second mobile terminal 200 in the display unit 111. When the mobile terminal 100 receives a request for audiovisual communication from at least one mobile terminal while performing audiovisual communication (S403), the controller 105 determines whether the number of the mobile terminals requesting audiovisual communication is at least two (S405). [0066]If there are at least two mobile terminals requesting audiovisual communication, the controller 105 sets a standby order according to the order in which the requests for audiovisual communication were received and displays the set standby order on the display unit 111 (S407). The controller 105 displays image data received from the mobile terminals requesting audiovisual communication or image data mapped to a phone number of the mobile terminals and stored in a phone book (not shown) on the display unit 111 in the order in which their audiovisual communication requests were received. [0067]The controller 105 determines whether the set standby order has changed (S409). If the set standby order has not change, the process continues at step S419. [0068]If the set standby order has changed, the controller 105 controls the RF unit 101 to send a message REQ_MSG requesting that the standby order of the mobile terminals (here, the third mobile terminal 300 and the fourth mobile terminal 400) be changed through the mobile communication network 500 (S411). [0069]Thereafter, the controller 105 receives a standby order change completion message RES_MSG sent from the mobile communication network 500 through the RF unit 101 (S415). The controller 105 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the received standby order change completion message RES_MSG and displays the changed standby order on the display unit 111 (S417). [0070]The controller 105 determines whether the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S419). If the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the controller 105 determines whether mobile terminals waiting for audiovisual communication exist, and if mobile terminals waiting for audiovisual communication exist, the first mobile terminal 100 performs audiovisual communication with the mobile terminal having the highest standby position (S421). The first mobile terminal 100 may perform audiovisual communication with the fourth mobile terminal 400, whose standby order position is changed to the highest position at step S417, or with the third mobile terminal 300, which has the highest position in the standby order set at step S407. [0071]If the number of the mobile terminals requesting audiovisual communication is not at least two at step 405, the controller 105 determines whether the first mobile terminal 100 has either ended audiovisual communication with the second mobile terminal 200 or converted a state of audiovisual communication with the second mobile terminal 200 to a standby state (S423). When the first mobile terminal 100 either ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state, the first mobile terminal 100 performs audiovisual communication with the mobile terminal requesting audiovisual communication (S425). [0072]FIGS. 5A and 5B are message flow diagrams showing another method of changing a standby order of waiting mobile terminals in a mobile terminal according to another exemplary embodiment of the present invention. [0073]Referring to FIGS. 5A and 5B, steps S501 to S523 of FIG. 5A are substantially the same as steps S301 to S323 of FIG. 3A and thus description thereof is omitted. [0074]If the fourth mobile terminal 400 having a standby order position that is lower than that of the third mobile terminal 300 sends a standby order change request message REQ_MSG through the mobile communication network 500 (S525), the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100 (S527), and the mobile communication network 500 sends the standby order change request message REQ_MSG to the third mobile terminal 300 (S529). The standby order change request message REQ_MSG may be sent by the fourth mobile terminal 400 at the same time the fourth mobile terminal 400 sends an audiovisual communication request message to the mobile communication network 500 at step S513. [0075]The first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG (S531), and the third mobile terminal 300 approves the change of the standby order in response to the standby order change request message REQ_MSG (S533). [0076]The first mobile terminal 100 then sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S535), and the third mobile terminal 300 sends a standby order change approval message ACC_MSG to the mobile communication network 500 to confirm approval of the change of the standby order (S537). [0077]The mobile communication network 500 changes the standby order of the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change approval message ACC_MSG received from the first mobile terminal 100 at step S535 and from the third mobile terminal 300 at step S537 (S539). [0078]The mobile communication network 500 temporarily stores a changed standby order (S541) and sends a standby order change completion message RES_MSG to the first mobile terminal 100(S543), the third mobile terminal 300 (S545), and the fourth mobile terminal 400(S547). [0079]The first mobile terminal 100 changes and displays the standby order set at the third mobile terminal 300 and the fourth mobile terminal 400 according to the standby order change completion message RES_MSG received from the mobile communication network 500 (S549). [0080]Thereafter, when the first mobile terminal 100 ends audiovisual communication with the second mobile terminal 200 or converts a state of audiovisual communication with the second mobile terminal 200 to a standby state (S551), the mobile communication network 500 refers to the changed standby order temporarily stored at step S541 (S553) and enables the first mobile terminal 100 to perform audiovisual communication with the fourth mobile terminal 400, which has the highest standby position due to the change of the standby order (S555). [0081]The mobile communication network 500 sends a message regarding the state of the first mobile terminal 100 to the third mobile terminal 300 to notify the third mobile terminal 300 that the first mobile terminal 100 is performing audiovisual communication (S557). [0082]Another method of changing a standby order of waiting mobile terminals according to another exemplary embodiment of the present invention (not shown in the Figures) is described as follows. [0083]When the mobile communication network 500 receives a standby order change request message REQ_MSG from the fourth mobile terminal 400, the mobile communication network 500 sends the standby order change request message REQ_MSG to the first mobile terminal 100. [0084]Thereafter, if the first mobile terminal 100 approves the change of the standby order in response to the standby order change request message REQ_MSG, the first mobile terminal 100 sends a standby order change approval message ACC_MSG confirming the approval to the mobile communication network 500. When th(String), 相关申请的交叉引用 [0001] 本申请要求于 2007 年 1 月 16 日提交的韩国专利申请号 10-2007-0004601 的优先权和权益,其在此通过引用并入所有目的,就好像在此完全阐述一样。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种在移动终端中提供视听通信服务的方法,更具体地,涉及一种在移动终端中改变等待移动终端的待机顺序的方法。 [0004] 2. 背景讨论 [0005] 随着移动终端技术的发展,已经提供了一种改进的移动终端,其具有使用H.324M协议的相机单元,该H.324M协议包括允许视听通信的H.245协议。 [0006] 在传统的视听通信技术中,当第一移动终端在与第二移动终端进行视听通信时,当第一移动终端接收到来自第三移动终端的视听通信请求时,第一移动终端存储关于第三移动终端的信息。 之后,当第一移动终端结束与第二移动终端的视听通信时,第一移动终端显示第三移动终端的信息,并与第三移动终端进行视听通信。 [0007] 然而,在现有的视听通信技术中,即使第三移动终端紧急请求与第一移动终端进行视听通信,第三移动终端也可能不得不等待,直到第一移动终端结束与第二移动终端的视听通信。 发明内容 [0008] 本发明提供了一种在第一移动终端正在执行视听通信时改变请求视听通信的至少两个移动终端的待机顺序的方法。 [0009] 本发明还提供了一种根据从等待与第一移动终端进行视听通信的至少两个移动终端之一接收到的待机顺序改变请求来改变处于待机状态的移动终端的待机顺序的方法,同时第一移动终端是 进行视听交流。 [0010] 本发明还提供了一种在第一移动终端正在与第二移动终端进行视听通信时显示关于请求视听通信的移动终端的信息的方法。 [0011] 本发明的附加特征将在随后的描述中阐述,并且部分地从描述中变得显而易见,或者可以通过本发明的实践来了解。 [0012] 本发明公开了一种用于在移动通信系统中改变待机顺序的方法,包括当第一移动终端时,根据接收到多个移动终端的视听通信请求的顺序,显示多个移动终端的待机顺序。 当第一移动终端正在与第二移动终端进行视听通信时,终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到来自第一移动终端的待机命令更改请求消息到移动通信网络时 请求更改待机命令,当第一移动终端接收到与待机命令更改请求消息对应的待机命令更改完成消息时,在第一移动终端更改待机命令,并显示更改后的待机命令。 [0013]本发明还公开了一种在移动通信系统中改变待机顺序的方法,包括根据接收到多个移动终端的视听通信请求的顺序显示多个移动终端的待机顺序。 当第一移动终端与第二移动终端进行视听通信时,移动终端接收来自多个移动终端的视听通信请求,当第一移动终端接收到待机时,确定第一移动终端是否批准请求的待机顺序变更 所述多个移动终端中的第三移动终端的订单更改请求消息,如果第一移动终端批准请求的待机订单更改,则更改待机订单,并显示更改后的待机订单。 [0014] 应当理解,前面的一般描述和下面的详细描述都是示例性和解释性的,并且旨在提供对所要求保护的本发明的进一步解释。 附图的简要说明 [0015] 附图被包括以提供对本发明的进一步理解并且被并入并构成本说明书的一部分,它们说明了本发明的实施例,并且与描述一起用于解释本发明的原理。 [0016] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0017] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0018] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0019] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0020] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0021] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0022] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 图示实施例的详细说明 [0023] 下文参照附图更全面地描述本发明,其中示出了本发明的实施例。 然而,本发明可以以许多不同的形式来体现,并且不应被解释为限于这里阐述的实施例。 相反,提供这些实施例是为了使本公开是彻底的,并且将向本领域技术人员充分传达本发明的范围。 在附图中,为了清楚起见,可能夸大了层和区域的尺寸和相对尺寸。 图中相同的附图标记表示相同的元件。 [0024] 应当理解,当一个元件或层被称为“在”另一个元件或层上或“连接到”另一个元件或层时,它可以直接在另一个元件或层上或直接连接到另一个元件或层,或者中间的元件或层可以是 当下。 相反,当一个元素被称为“直接在”或“直接连接到”另一个元素或层时,不存在中间的元素或层。 [0025]根据本发明的示例性实施例举例说明了包括照相机单元并且能够执行视听通信的移动终端。 也就是说,根据本发明示例性实施例的移动终端可以包括信息通信设备或多媒体设备,例如移动通信终端、移动电话、个人数字助理(PDA)、智能电话或笔记本电脑 包括照相机单元并能够进行视听通信的计算机及其应用。 [0026] 根据本发明的示例性实施例举例说明了视听通信。 然而,本示例性实施例不限于视听通信并且可以应用于语音通信。 [0027] 如图。 图1是示出根据本发明示例性实施例的用于向移动终端提供视听通信服务的系统的图。 [0028] 参考图。 1、系统包括第一移动终端 100 ,第二个移动终端 200 ,第三个移动终端 300 ,第四个移动终端 400 , 和一个移动通信网络 500 . [0029] 第一移动终端可以与第二移动终端进行视听通信 200 并且可以接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 在与第二移动终端进行视听通信的同时 200 . 第一移动终端的配置 100 参照图1描述。 如图2所示,同样的配置也可以应用于第二移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 因此,省略其个别描述。 [0030] 移动通信网络 500 包括执行基站功能的节点、作为节点的子系统的无线接入网络 (RAN)、对应于一个核心网络的移动交换中心 (MSC)/访问者位置寄存器 (VLR) 电路交换域、归属位置寄存器 (HLR) 和网关 MSC。 [0031] MSC管理第一移动终端的呼叫控制和移动性 100 ,VLR和HLR组成用户信息匹配装置,注册和管理属于移动通信网络的移动终端信息 500 包括第一移动终端 100 . [0032] 在下面的描述中,第一移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 属于同一个移动通信网络 500 . 然而第一款移动终端 100 ,第二个移动终端 200 , 第三个移动终端 300 ,以及第四个移动终端 400 可能属于不同的移动通信网络,可能通过不同的网关MSC连接。 然而,假设在移动通信网络中执行在RAN、MSC/VLR、HLR和网关MSC中执行的一系列处理 500 . [0033] 如图。 图2是示出根据本发明另一示例性实施例的移动终端的配置的框图。 [0034] 参考图。 2、移动端 100 包括一个射频 (RF) 单元 101 , 一个输入单元 103 , 一个控制器 105 , 一个相机单元 107 , 图像处理器 109 , 一个显示单元 111 , 一个记忆单元 113 , 和一个音频单元 115 . [0035] 射频单元 101 与第二移动终端进行一般无线通信 200 , 第三个移动终端 300 ,第四个移动终端 400 , 和移动通信网络 500 . 例如,射频单元 101 使用移动通信网络发送和接收语音数据、字符消息和多媒体消息 500 . 射频单元 101 发送从相机单元获取的图像数据 107第一个移动终端 100 到第二个移动终端 200 当第一个移动终端 100 与第二移动终端进行视听通信 200 . 射频单元 101 还接收第二移动终端的摄像单元获取的图像数据 200 第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 请求视听通信。 第二移动终端的图像数据 200 可以是静止和/或运动图像数据,第三移动终端的图像数据 300 和第四个移动终端 400 可以是静止和/或运动图像数据。 进一步地,当第三移动终端 300 和第四个移动终端 400 与第一移动终端进行视听通信 100 ,第三个移动终端的图像数据 300 和第四个移动终端 400 可能会更改为运动图像数据。 [0036] 输入单元 103 可能包括一个通用键盘。 输入单元 103 可以包括触摸屏、触摸板和滚轮。 输入单元 103 接收用户操作信号以控制第一移动终端的操作 100 并向控制器提供操纵信号 105 . [0037] 控制器 105 控制第一移动终端的一般操作 100 . 特别是控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 ,接收来自第三移动终端的视听通信请求 300 和第四个移动终端 400 ,并设置视听通信请求的待机顺序。 控制器 105 显示图像数据(即第二移动终端用户的图像数据) 200 )的第二个移动终端 200 在显示单元中进行视听通信 111 . 控制器 105 在显示单元上按照接收到视听通信请求的顺序显示来自请求视听通信的每个移动终端的图像数据 111 第一个终端的 100 . [0038] 更详细地说,第三移动终端的图像数据 300 和第四个移动终端 400 可以是映射到对应的移动终端并存储在第一移动终端的电话簿(未示出)中的图像数据 100 . 图像数据也可以是第三移动终端的摄像单元获取的图像数据 300 和第四个移动终端 400 当请求视听通信时,可能会与视听通信请求一起发送。 控制器 105 可以显示第三移动终端的图像数据 300 和第四个移动终端 400 缩略图类型的静止图像数据。 控制器 105 还可以显示第二移动终端的图像数据 200 ,其中第一款移动终端 100 正在执行视听通信,包括运动图像数据。 [0039] 控制器 105 从第一移动终端发送备用订单更改请求消息REQ_MSG 100 到移动通信网络 500 通过射频单元 101 ,接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面中显示更改后的待机顺序 111 . [0040] 控制器 105 进一步通过移动通信网络从具有最高待机位置的移动终端接收待机顺序更改请求消息REQ_MSG 500 向移动通信网络发送待命订单变更批准消息ACC_MSG 500 通过射频单元 101 . 此后,控制器 105 接收来自移动通信网络的备用订单更改完成消息RES_MSG 500通过射频单元 101 ,更改第三个移动终端的待机顺序 300 和第四个移动终端 400 , 并在人机界面显示待机命令 111 . [0041] 当控制器 105 确定第一移动终端 100 已结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 控制射频单元 101 与待机位置最高的移动终端进行视听通信。 在示例性实施例中,“结束”视听通信是终止形成用于与第二移动终端进行视听通信的通信信道 200 ,并且将视听通信状态“转换”为待机状态是为了在保持与第二移动终端执行视听通信而形成的通信信道的同时,转换为待机状态以便与另一个移动终端执行视听通信。 200 . [0042] 相机单元 107 生成用户的图像数据以通过射频单元发送 101 . 相机单元 107 包括将对象的照片信号转换为模拟信号的图像传感器和将模拟信号转换为数字信号的信号处理器。 也就是相机单元 107 将通过镜头采集的照片信号转换为数字信号,并利用转换后的数字信号生成图像数据。 [0043] 图像处理器 109 处理相机单元中生成的图像数据 107 和通过射频单元接收的图像数据 101 转换成与显示单元对应的格式 111 . [0044] 控制器 105 控制显示单元 111 显示第一移动终端各单元的各种操作状态、操作结果等信息 100 . 显示单元 111 液晶显示器(LCD)、有机发光二极管(OLED)或等离子体显示面板(PDP)等显示装置可以包括显示装置。 [0045] 显示单元 111 显示通过射频单元输入的图像数据 101 和相机单元 107 并在图像处理器中处理 109 实时,从而进行视听通信或显示拍摄的图像。 [0046] 记忆单元 113 存储与允许控制器的程序的操作有关的信息(例如,关于设置状态和菜单的信息) 105 控制第一移动终端 100 . 记忆单元 113 存储第三移动终端的待机指令 300 和第四个移动终端 400 . 记忆单元 113 存储从第二移动终端接收的图像数据 200 , 第三个移动终端 300 ,以及第四个移动终端 400 ,并且还可以将映射到对应终端的图像数据存储在第一移动终端的电话簿(未示出)中 100 . [0047] 音频单元 115 将通过麦克风 MIC 输入的模拟音频信号转换为数字信号,将数字信号提供给控制器 105 , 转换从控制器输出的数字音频信号 105 转换成模拟音频信号,并通过扬声器SPK再现模拟音频信号。 [0048] 图 图3A和3B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的消息流程图。 [0049] 参考图。 参照图3A和3B,同时第一移动终端 100 与第二移动终端进行视听通信 100 (S 301 )、移动通信网络 500 接收来自第三移动终端的视听通信请求 300 (S 303 )。 在步骤 S 301 ,第一款移动终端 100 处于视听通信状态,摄像单元 107 第一个移动终端100 获取第一移动终端用户的图像 100 , 图像处理器 109 处理用户图像,显示单元 111 显示用户图像,并将麦克风MIC和扬声器SPK转换为操作状态。 [0050] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三终端 300 那是第一个移动终端 100 正在进行视听交流(S 305 )。 [0051] 第三个移动终端 300 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 307 )。 如果是第三个移动终端 300 第三移动终端保持视听通信待机状态 300 向移动通信网络发送待机状态维持消息 500 (S 309 )。 [0052] 此后,移动通信网络 500 发送关于第三个移动终端的信息 300 到第一移动终端 100 (S 311 )并形成第一移动终端之间的通信通道 100 第三个移动终端 300 . 第三移动终端信息 300 可以包括第三移动终端的联系方式和图像数据 300 . [0053] 移动通信网络 500 接收来自第四移动终端的视听通信请求 400 (S 313 ),并发送有关第一移动终端状态的消息 100 到第四个移动终端 400 通知第四移动终端 400 那是第一个移动终端 100 正在进行视听交流(S 315 )。 [0054] 第四款移动终端 400 根据来自第一移动终端的消息判断是否维持视听通信待机状态 100 通过移动通信网络接收 500 (S 317 )。 如果第四个移动终端 400 第四移动终端保持视听通信待机状态 400 向移动通信网络发送待机状态维持消息 500 (S 319 )。 [0055] 此后,移动通信网络 500 发送第四个移动终端的信息 400 到第一移动终端 100 (S 321 )并形成第一移动终端之间的通信通道 100 和第四个移动终端 400 . 第四移动终端信息 400 可以包括第四移动终端的联系信息和图像数据 400 . [0056] 第一个移动终端 100 确定第一移动终端之间的通信信道 100 第三个移动终端 300 在步骤 S 形成 311 ,以及第一移动终端之间的通信信道 100 和第四个移动终端 400 在步骤 S 形成 321 . [0057] 此后,第一移动终端 100 通过按照接收到请求的顺序列出移动终端,设置并显示请求视听通信的移动终端的待机顺序(S 323 )。 在本示例性实施例中,由于第三移动终端 300 在第四台移动终端之前请求视听通信 400 , 第三个移动终端 300 具有最高的待机位置。 [0058] 当第一个移动终端 100 想要更改显示的待机顺序(S 325 ),第一款移动终端 100 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 327 )。 通过选择第三移动终端的图像数据输入更改待机顺序的请求 300和第四个移动终端 400 以更改模式或待机顺序显示。 [0059] 移动通信网络 500 接收待机顺序变更请求消息REQ_MSG,变更第三移动终端的待机顺序 300 和第四个移动终端 400 (S 329 )。 [0060] 移动通信网络 500 临时存储更改后的待机订单(S 331 )并发送备用订单变更完成消息RES_MSG通知第一移动终端 100 第三个移动终端的待机订单变更 300 和第四个移动终端 400 (S 333 )。 [0061] 第一个移动终端 100 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG更改并显示待机命令 500 (S 335 )。 [0062] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 337 )、移动通信网络 500 指在步骤中临时存储的已更改的备用订单 331 (S 339 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 341 )。 [0063] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 343 )。 [0064] 如图。 图4是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的方法的流程图。 [0065] 参考图。 4、控制器 105 控制射频单元 101 与第二移动终端进行视听通信 200 (S 401 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . 当移动端 100 在执行视听通信时从至少一个移动终端接收视听通信请求(S 403 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 405 )。 [0066] 如果有至少两个移动终端请求视听通信,则控制器 105 根据接收视听通信请求的顺序设置待机命令,并在显示单元上显示设置的待机命令 111 (S 407 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0067] 控制器 105 判断设置的待机顺序是否改变(S 409 )。 如果设置的待机顺序没有改变,则过程继续到步骤S 419 . [0068] 如果设置的待机顺序发生了变化,控制器 105 控制射频单元 101 发送消息REQ_MSG,请求移动终端(这里是第三个移动终端)的待机命令 300 和第四个移动终端 400 ) 通过移动通信网络进行更改 500 (S 411 )。 [0069] 此后,控制器 105 接收移动通信网络发送的备用订单变更完成消息RES_MSG 500 通过射频单元 101 (S 415 )。 控制器 105更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据接收到的待机指令变更完成消息RES_MSG,在人机界面上显示变更后的待机指令 111 (S 417 )。 [0070] 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 419 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 421 )。 第一个移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单位置在步骤 S 更改为最高位置 417 ,或与第三个移动终端 300 ,它在步骤 S 中设置的待机顺序中的最高位置 407 . [0071] 如果在步骤中请求视听通信的移动终端的数量不是至少两个 405 , 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 423 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 425 )。 [0072] 图 图5A和5B是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的消息流程图。 [0073] 参考图。 参见图5A和5B,步骤S 501 到 S 523 图。 图5A与步骤S基本相同 301 到 S 323 图。 与图3A相同,因此省略其描述。 [0074] 如果第四个移动终端 400 待机订单仓位低于第三移动终端 300 通过移动通信网络发送备用订单更改请求消息REQ_MSG 500 (S 525 )、移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 (S 527 ) 和移动通信网络 500 向第三移动终端发送备用订单变更请求消息REQ_MSG 300 (S 529 )。 待命订单变更请求消息REQ_MSG可以由第四移动终端发送 400 同时第四个移动终端 400 向移动通信网络发送视听通信请求消息 500 在步骤 S 513 . [0075] 第一个移动终端 100 响应备用订单更改请求消息REQ_MSG(S 531 ),以及第三个移动终端 300 响应备用订单更改请求消息REQ_MSG(S 533 )。 [0076] 第一个移动终端 100 然后向移动通信网络发送备用订单更改批准消息ACC_MSG 500 确认批准备用订单的更改(S 535 ),以及第三个移动终端 300 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500确认批准备用订单的更改(S 537 )。 [0077] 移动通信网络 500 更改第三个移动终端的待机顺序 300 和第四个移动终端 400 根据从第一移动终端接收到的待命订单变更批准消息ACC_MSG 100 在步骤 S 535 并从第三个移动终端 300 在步骤 S 537 (S 539 )。 [0078] 移动通信网络 500 临时存储更改的备用订单(S 541 )并向第一移动终端发送备用订单变更完成消息RES_MSG 100 (S 543 ),第三个移动终端 300 (S 545 )、第四个移动终端 400 (S 547 )。 [0079] 第一个移动终端 100 更改并显示在第三个移动终端设置的待机指令 300 和第四个移动终端 400 根据从移动通信网络接收到的待机命令更改完成消息RES_MSG 500 (S 549 )。 [0080] 此后,当第一移动终端 100 结束与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 551 )、移动通信网络 500 指的是在步骤 S 临时存储的更改后的待机命令 541 (S 553 ) 并启用第一个移动终端 100 与第四移动终端进行视听通信 400 ,由于待机顺序的变化,待机位置最高(S 555 )。 [0081] 移动通信网络 500 发送关于第一移动终端状态的消息 100 到第三个移动终端 300 通知第三移动终端 300 那是第一个移动终端 100 正在进行视听交流(S 557 )。 [0082] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0083] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 . [0084] 此后,如果第一移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG批准待命订单变更 100 向移动通信网络发送确认批准的备用订单更改批准消息ACC_MSG 500 . 当移动通信网络 500 接收待命订单变更批准消息ACC_MSG,移动通信网络 500 相应地更改备用顺序。 移动通信网络 500 暂存变更后的待命订单,并向第一移动终端发送待命订单变更完成消息RES_MSG 100 . [0085] 下面描述根据本发明另一示例性实施例的改变等待移动终端的待机顺序的另一方法(图中未示出)。 [0086] 当移动通信网络 500 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 , 移动通信网络 500 向第一移动终端发送备用订单变更请求消息REQ_MSG 100 第三个移动终端 300 . 如果第一个移动终端 100 第一移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 100 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . 如果是第三个移动终端 300第三移动终端响应待命订单变更请求消息REQ_MSG不批准待命订单变更请求 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 . [0087] 当至少一个第一移动终端 100 第三个移动终端 300 向移动通信网络发送备用订单更改未批准消息 N_ACC_MSG 500 , 移动通信网络 500 不改变待命订单,向第一移动终端发送待命订单变更不批准消息N_ACC_MSG 100 , 第三个移动终端 300 ,以及第四个移动终端 400 . [0088] 进一步地,如果第一移动终端 100 批准备用订单和第三个移动终端的更改 300 在接收到来自移动通信网络的待命订单更改不批准消息N_ACC_MSG时,响应待命订单更改请求消息REQ_MSG不批准待命订单的更改 500 通知它待机顺序没有改变,因为第三个移动终端 300 不批准备用订单变更,第一个移动端 100 可以向移动通信网络发送备用订单更改请求消息REQ_MSG 500 从而可以强制改变第三移动终端的待机顺序 300 和第四个移动终端 400 . [0089] 如图。 图6是示出根据本发明另一示例性实施例的在移动终端中改变等待移动终端的待机顺序的另一方法的流程图。 [0090] 参考图。 6、控制器 105 控制射频单元 101 让第一个移动终端 100 与第二移动终端进行视听通信 200 (S 601 )。 控制器 105 显示从第二移动终端实时接收的运动图像数据 200 在显示单元中 111 . [0091] 当控制器 105 在进行视听通信时从至少一个移动终端接收视听通信请求(S 603 ), 控制器 105 判断请求视听通信的移动终端的数量是否至少为两个(S 605 )。 [0092] 如果有至少两个移动终端请求视听通信,则控制器 105 在视听通信请求命令中设置待机命令并在显示单元中显示该命令 111 (S 607 )。 控制器 105 在显示单元上显示从请求视听通信的移动终端接收的图像数据或映射到移动终端的电话号码并存储在电话簿(未示出)中的图像数据 111 按照收到他们的视听通信请求的顺序。 [0093] 如果控制器 105 从第四移动终端接收待机订单变更请求消息REQ_MSG 400 (S 609 ), 控制器 105 判断移动端是否 100 响应备用订单更改请求消息,批准备用订单的更改(S 611 )。 如果移动端 100 不批准备用订单的变更,流程继续步骤S 619 . [0094] 如果移动端 100 批准备用订单的更改,控制器 105 向移动通信网络发送备用订单更改批准消息 ACC_MSG 500 (S 613 )。 [0095] 控制器 105 判断移动端是否 100 从移动通信网络接收备用订单更改完成消息RES_MSG 500 (S 615 )。 如果移动端 100 未收到来自移动通信网络的备用订单更改完成消息 RES_MSG 500 , 过程在步骤 S 继续 619 . 如果移动端 100接收来自移动通信网络的备用订单更改完成消息RES_MSG 500 , 控制器 105 根据接收到的待机命令更改完成消息RES_MSG更改待机命令,并在人机界面显示更改后的待机命令 111 (S 617 )。 [0096] 控制器 105 判断第一移动终端是否 100 已结束与第二个移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 619 )。 当第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态,控制器 105 判断是否存在等待视听通信的移动终端,如果存在等待视听通信的移动终端,则第一移动终端 100 与待机位置最高的移动终端进行视听通信(S 621 )。 例如,第一移动终端 100 可以与第四移动终端进行视听通信 400 ,其备用订单仓位已在步骤 S 变为最高仓位 617 ,或与第三个移动终端 300 在步骤 S 中设置的待机顺序中的最高位置 607 . [0097] 如果在步骤S请求视听通信的移动终端的数量不是至少两个 605 , 控制器 105 判断第一移动终端是否 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 到待机状态(S 623 )。 如果第一个移动终端 100 任一端与第二移动终端的视听通信 200 或转换与第二移动终端的视听通信状态 200 进入待机状态,第一移动终端 100 与请求视听通信的移动终端进行视听通信(S 625 )。 [0098] 如图。 图7是示出根据本发明另一示例性实施例的在移动终端中与等待的移动终端执行视听通信的另一方法的消息流程图。 [0099] 参考图。 7、同时第一移动终端 100 与第二移动终端进行视听通信 200 通过移动通信网络 500 (S 701 )、移动通信网络 500 接收与第一移动终端进行视听通信的请求 100 从第三个移动终端 300 (S 703 )。 [0100] 移动通信网络 500 形成第一移动终端之间的通信通道 100 第三个移动终端 300 并发送关于第三移动终端的信息 300 连同对第一移动终端的视听通信请求 100 (S 705 )。 第三移动终端信息 300 可以是第三移动终端的用户信息(例如电话号码) 300 和/或包括第三移动终端的图像数据的信息 300 . [0101] 第一个移动终端 100 显示从第三移动终端接收到的图像数据 300 (S 707 )。 第一个移动终端 100 可以进一步显示消息(例如弹出窗口)以批准与第三移动终端的视听通信的连接 300 . [0102] 如果第一个移动终端 100 批准与第三个移动终端的视听通信 300 (S 709 )、移动通信网络 500 结束第一移动终端之间的视听通信 100 第二移动终端 200或者转换第一移动终端之间的视听通信状态 100 第二移动终端 200 到待机状态(S 711 )。 此后,移动通信网络 500 实现第一移动终端之间的视听通信 100 第三个移动终端 300 (S 713 )。 [0103] 如上所述,根据本发明,通过在第一移动终端与第二移动终端执行视听通信时改变至少两个请求视听通信的移动终端的待机顺序,可以与选择的请求视听的移动终端执行视听通信 通信,可以为第一移动终端的用户提供更大的便利。 [0104] 此外,通过在第一移动终端与第二移动终端进行视听通信的同时,根据从请求视听通信的至少两个移动终端中的具有较低待机位置的移动终端接收到的用于改变待机命令的请求来改变待机命令, 可以与选择的请求视听通信的移动终端进行视听通信,这可以为具有较低待机位置的待机状态的移动终端的用户提供更大的便利。 [0105] 另外,通过在第一移动终端与第二移动终端进行视听通信的同时显示关于请求视听通信的移动终端的信息,用户可以容易地检查处于待机状态的移动终端。 [0106] 对于本领域的技术人员来说,在不脱离本发明的精神或范围的情况下,可以对本发明进行各种修改和变化是显而易见的。 因此,本发明旨在覆盖本发明的修改和变化,只要它们落入所附权利要求及其等同物的范围内。(String), 112499(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:20.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100790787B1(String), US20080171563A1(String), US7801528B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100790787B1(String), US20080171563A1(String), US7801528B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271644(Integer), KR100790787B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271644(Integer), US20080171563A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271644(Integer), US7801528B2(String), 1049463(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7801528B2(String), US7801528B2(String), 1284998400(Integer), 271644(Integer), 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185929(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.295 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.295 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.295 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185929(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185929(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185929(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.507 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 185929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:21.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185930(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b10085b15f8b46068da83b750abf145b.png(String), 185930(Integer), b10085b15f8b46068da83b750abf145b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for obtaining location information about mobile terminal(String), 移动终端及获取移动终端位置信息的方法(String), US9451580B2(String), The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal. The method for obtaining location information about the mobile terminal comprises: turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal.(String), 本发明实施例提供一种移动终端及获取移动终端位置信息的方法。 获取移动终端位置信息的方法包括:打开移动终端的卫星定位模块,获取移动终端当前位置信息后关闭卫星定位模块,并将当前位置信息作为初始位置信息。 ; 移动终端的传感模块采集移动终端的运动信息,并根据该运动信息计算移动终端的位移变化量; 根据初始位置信息和移动终端的位移变化,获取移动终端的实际位置信息。(String), US14/436195(String), 1374163200(Integer), US9451580B2(String), 1474300800(Integer), 1474300800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 5(Integer), 27(Integer), CN101464155A | CN102169182A | CN102243315A | CN102901975A | CN1914517A | JP1988108285A | JP1989278879A | JP1990212713A | JP1991237788A | JP1994111196A | JP1995001210A | JP2001059738A | JP2002255664A | JP2006242578A | JP2006279266A | JP2008063815A | JP2008067681A | JP2010038712A | JP2010038798A | JP2010120968A | JP2011149925A | JP2011164089A | JP2011176576A | JP2013029915A | US20100253503A1 | US20130102268A1 | US20160007405A1(String), \20230420\b10085b15f8b46068da83b750abf145b.png(String), 10(Integer), 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 1. A method for obtaining location information about a mobile terminal, comprising:turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information;a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information;obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal;wherein, the motion information comprises:acceleration information and initial velocity information;further comprising a correction step to the initial velocity after calculating the initial velocity; wherein, the correction step comprises:judging whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then no need to correct the initial velocity; if not, then re-calculating the initial velocity.(String), 1、一种获取移动终端位置信息的方法,包括:开启移动终端的卫星定位模块,获取到移动终端的当前位置信息后关闭卫星定位模块,将当前位置信息作为初始位置信息。移动终端的感知模块采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量;根据初始位置信息和移动终端的位移变化获取移动终端的实际位置信息;其中,运动信息包括:加速度信息和初速度信息;还包括计算初速度后对初速度进行修正的步骤;其中,校正步骤包括:判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内;如果是,则无需修正初速度;如果不是,则重新计算初始速度。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 2. The method according to claim 1, further comprising: periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal, updating the initial location information, and setting the variation of displacement as zero.(String), 2.根据权利要求1所述的方法,还包括:周期性开启移动终端的卫星定位模块,获取移动终端的当前位置信息,更新初始位置信息,并将位移变化量设置为零。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 3. The method according to claim 2, wherein, the step of periodically turning on the satellite locating module of the mobile terminal comprises:starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value;orjudging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module.(String), 3.根据权利要求2所述的方法,其中,周期性开启移动终端的卫星定位模块的步骤包括:当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块;or判断位移变化量是否达到预设位移阈值;如果是,则打开卫星定位模块。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 4. The method according to claim 1, wherein, the step of collecting the initial velocity information of the mobile terminal comprises:judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period.(String), 4.根据权利要求1所述的方法,其中,采集移动终端的初始速度信息的步骤包括:判断移动终端在初始位置的运动状态;如果处于静止状态,则初速度为零;如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 5. The method according to claim 4, wherein, the step of calculating displacement changing information of the mobile terminal through the motion information comprises:decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; andcalculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction.(String), 5.根据权利要求4所述的方法,其中,通过运动信息计算移动终端的位移变化信息的步骤包括:分解经度方向、纬度方向和高度方向的加速度和初速度;和根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 6. A mobile terminal, comprising a processor, configured to:obtain current location information about the mobile terminal through a satellite locating module comprising a global positioning system (GPS) module or an assisted global positioning system (AGPS) module;turn on the satellite locating module, and turn off the satellite locating module after the information is obtained;collect motion information about the mobile terminal through a sensor, and calculate variation of displacement of the mobile terminal according to the motion information; andobtain actual location information about the mobile terminal through processing the initial location information and the variation of displacement of the mobile terminal;wherein, the motion information comprises: acceleration information and initial velocity information;wherein, the processor is further configured to:judge whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then need not to correct the initial velocity; if not, then re-calculate the initial velocity.(String), 6.移动终端,包括一个处理器,配置为:通过包括全球定位系统(GPS)模块或辅助全球定位系统(AGPS)模块的卫星定位模块获取移动终端的当前位置信息;开启卫星定位模块,获取信息后关闭卫星定位模块;通过传感器采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量;和通过处理初始位置信息和移动终端的位移变化,得到移动终端的实际位置信息;其中,运动信息包括:加速度信息和初速度信息;其中,处理器还用于:判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内;如果是,则无需修正初速度;如果不是,则重新计算初始速度。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 7. The mobile terminal according to claim 6, wherein, the processor is further configured to: control the satellite locating module to periodically turn on to obtain the current location information of the mobile terminal, update the initial location information, and set the variation of displacement as zero.(String), 7.根据权利要求6所述的移动终端,其中,处理器还用于:控制卫星定位模块周期性开启,获取移动终端的当前位置信息,更新初始位置信息,并将位移变化量设置为零。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 8. The mobile terminal according to claim 7, wherein, the processor is configured to periodically turn on the satellite locating module of the mobile terminal by the following mode:starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value;orjudging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module.(String), 8.根据权利要求7所述的移动终端,其中,处理器用于通过以下方式周期性开启移动终端的卫星定位模块:当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块;or判断位移变化量是否达到预设位移阈值;如果是,则打开卫星定位模块。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 9. The mobile terminal according to claim 6, wherein, the processor is configured to collect the initial velocity information of the mobile terminal by the following mode:judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period.(String), 9.根据权利要求6所述的移动终端,其中,处理器,用于通过以下方式采集移动终端的初始速度信息:判断移动终端在初始位置的运动状态;如果处于静止状态,则初速度为零;如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185930(Integer), 10. The mobile terminal according to claim 9, wherein, the processor is configured to calculate the displacement changing information of the mobile terminal by the following mode:decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; andcalculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction.(String), 10.根据权利要求9所述的移动终端,其中,处理器用于通过以下方式计算移动终端的位移变化信息:分解经度方向、纬度方向和高度方向的加速度和初速度;和根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185930(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is the 35 U.S.C. §371 national stage of PCT Application No. PCT/CN2013/079701, filed Jul. 19, 2013, which is herein incorporated by reference in its entirety and which also claims priority to, and the benefit of, Chinese Patent Application No. 201210396171.1, filed Oct. 18, 2012, which is herein incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present document relates to the wireless communication field, and in particular, to a mobile terminal and a method for obtaining location information about a mobile terminal. BACKGROUND [0003]Because of the characteristics, such as all-weather, high-accuracy and automatic measuring, possessed by the global positioning system (GPS) technology, as the advanced measurement means and new productivity, it had already been integrated into various application fields, such as the national economic construction, the national defense construction and the social development. [0004]Along with the end of cold war and the flourishing development of the global economy, the U.S. government announce to cancel the SA policy during the year 2000 to year 2006, on the premise of guaranteeing the U.S.A. national security not at risk, and the GPS civil signal precision is improved in the world wide, and the precision to locate the simple point by using the C/A code is raised to 10 meters from 100 meters, which will further promote the application of the GPS technology, raise the productivity, the working performance, the scientific level and the living quality of people, and stimulate the growth of the GPS market. [0005]The main function of the assisted global positioning system (A-GPS) technology is to be able to provide the high-accuracy location information for the terminal user. After the mobile operator adopts the location service based on the A-GPS locating technology, the terminal user can know the current position of oneself or others conveniently and swiftly, which is especially suitable for the vehicle tracing and the navigation system and the vehicles with special tasks (armor cash carrier, ambulance, fire vehicle, etc.), and is able to increase the vehicle security, the transportation efficiency and the service quality by a large margin. At present, as the domestic mobile communication market is growing day by day, especially along with the coming of the commercial usage of 3G, China Mobile and China Unicom have all made and put out their own A-GPS schemes. [0006]The product functions of the mobile terminals are more and more comprehensive at present, and most mobile terminals have the satellite positioning function, such as the GPS, the A-GPS, etc., and the user can know one's own location at any time. But the satellite locating module, such as the GPS module or the A-GPS module, needs to frequently read the location information along with the movement of the user and the constant change of the location, which leads to the problems, for example, the power consumption of the satellite locating module, such as the GPS module or the A-GPS module, is greater, the data updating will be delayed, etc. SUMMARY [0007]The embodiment of the present document provides a mobile terminal and a method for obtaining location information about a mobile terminal, which can reduce the power consumption of the satellite locating module. [0008]The embodiment of the present document provides a method for obtaining location information about a mobile terminal, comprising: [0009]turning on a satellite locating module of the mobile terminal, turning off the satellite locating module after current location information about the mobile terminal is obtained, and regarding the current location information as initial location information; [0010]a sensing module of the mobile terminal collecting motion information about the mobile terminal, and calculating variation of displacement of the mobile terminal according to the motion information; and [0011]obtaining actual location information about the mobile terminal according to the initial location information and the variation of displacement of the mobile terminal. [0012]Preferably, the method further comprises: periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal, updating the initial location information, and setting the variation of displacement as zero. [0013]Preferably, the step of periodically turning on the satellite locating module of the mobile terminal comprises: [0014]starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value;[0015]or [0016]judging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module. [0017]Preferably, the motion information comprises: acceleration information and initial velocity information. [0018]Preferably, the step of collecting the initial velocity information of the mobile terminal comprises: [0019]judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period. [0020]Preferably, the method further comprises a correction step to the initial velocity after calculating the initial velocity; wherein, [0021]the correction step comprises: [0022]judging whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then no need to correct the initial velocity; if not, then re-calculating the initial velocity. [0023]Preferably, the step of calculating displacement changing information of the mobile terminal through the motion information specifically comprises: [0024]decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; and [0025]calculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction. [0026]The embodiment of the present document provides a mobile terminal, comprising: a satellite locating module, a sensing module, a control module and a location information processing module; wherein, [0027]the satellite locating module is configured to: obtain current location information about the mobile terminal, and transmit the location information to the location information processing module; [0028]the control module is configured to: turn on the satellite locating module, and turn off the satellite locating module after the satellite locating module completes obtaining the information; [0029]the sensing module is configured to: collect motion information about the mobile terminal, and calculate variation of displacement of the mobile terminal according to the motion information, and transmit the variation of displacement to the location information processing module; and [0030]the location information processing module is configured to: obtain actual location information about the mobile terminal through processing the initial location information and the variation of displacement of the mobile terminal. [0031]Preferably, the control module is further configured to: control the satellite locating module periodically turn on to obtain the current location information of the mobile terminal, update the initial location information, and control the sensing module to set the variation of displacement as zero. [0032]Preferably, the satellite locating module is a global positioning system (GPS) module or an assisted global positioning system (AGPS) module. [0033]Preferably, the control module is configured to periodically turn on the satellite locating module of the mobile terminal by the following mode: [0034]starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value; [0035]or [0036]judging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module. [0037]Preferably, the motion information comprises: acceleration information and initial velocity information. [0038]Preferably, the sensing module is configured to collect the initial velocity information of the mobile terminal by the following mode: [0039]judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period. [0040]Preferably, the sensing module is further configured to: [0041]judge whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then need not to correct the initial velocity; if not, then re-calculate the initial velocity. [0042]Preferably, the sensing module is configured to calculate the displacement changing information of the mobile terminal by the following mode: [0043]decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; and [0044]calculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction. [0045]The embodiment of the present document provides a method for obtaining location information about a mobile terminal, which can reduce the power consumption of the module for obtaining the location information about the mobile terminal Wherein, the satellite locating module is turned off after the location information about the mobile terminal is obtained, then the motion information about the mobile terminal is collected through the sensing module of the mobile terminal, and the displacement changing information of the mobile terminal is calculated through the motion information, and then the actual location information is obtained according to the initial location information and the displacement changing information, to reduce the power consumption of the satellite locating module without requirement on obtaining the current location information of the mobile terminal and updating frequently by using the satellite locating module. [0046]In addition, the terminal only needs to calculate the displacement changing information through the motion information about the mobile terminal, and thus calculates the actual location information, which can reduce the appearance of the data update delay and improve the accuracy of the location information after the frequent updating and obtaining the location information are avoided. BRIEF DESCRIPTION OF DRAWINGS [0047]FIG. 1 is a basic flow chart of a method for obtaining location information about a mobile terminal according to embodiment one of the present document. [0048]FIG. 2 is a flow chart of obtaining an initial velocity according to embodiment one of the present document. [0049]FIG. 3 is a diagram of decomposing an acceleration according to embodiment one of the present document. [0050]FIG. 4 is a structure diagram of a mobile terminal according to embodiment one of the present document. PREFERRED EMBODIMENTS OF THE PRESENT DOCUMENT [0051]The embodiment of the present document is described in detail with reference to the accompanying drawings hereinafter. It should be illustrated that, in the case of not conflicting, the embodiments in the present application and features in these embodiments can be combined with each other. [0052]In the embodiment of the present document, the mobile terminal detects the motion state of the terminal itself and calculates the displacement variation information, and then calculates the actual location of the mobile terminal by combining with the initial location information read by the satellite locating module (such as the GPS or the A-GPS module), to prevent the module for obtaining the location information (such as the GPS or the A-GPS module) from frequently reading the current location information of the mobile terminal, reducing the power consumption of the satellite locating module (such as the GPS or the A-GPS module). [0053]The embodiment of the present document is described in detail with reference to the accompanying drawings hereinafter. Embodiment One [0054]Please refer to FIG. 1, a method for obtaining location information about a mobile terminal according to the present embodiment includes the following steps. [0055]In step 101, a satellite locating module of the mobile terminal is turned on, the satellite locating module is turned off after current location information about the mobile terminal is obtained, and the current location information is regarded as initial location information. [0056]In step 102, a sensing module of the mobile terminal collects motion information about the mobile terminal, and calculates variation of displacement of the mobile terminal according to the motion information. [0057]In step 103, actual location information about the mobile terminal is obtained according to the initial location information and the variation of displacement of the mobile terminal. [0058]The method of the present embodiment can further include: periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal, updating the initial location information, and setting the variation of displacement as zero. [0059]The above-mentioned period for turning on the satellite locating module of the mobile terminal can be preset, the displacement variation information of the mobile terminal can be calculated through obtaining the motion information about the mobile terminal and according to the motion information before starting the next period, and then the actual location of the mobile terminal at the corresponding moment is calculated according to the initial location information and the displacement changing information, to reduce the frequency of obtaining the location information and reduce the power consumption of the corresponding module. [0060]In the method for obtaining the location information about the mobile terminal of the present embodiment, the procedure of periodically turning on the satellite locating module of the mobile terminal to obtain the current location information of the mobile terminal can include: [0061]starting a timer when the satellite locating module is turned off, and turning on the satellite locating module when time reaches a preset time threshold value; [0062]or [0063]judging whether the variation of displacement reaches a preset displacement threshold value; and if yes, then turning on the satellite locating module. [0064]For example, the satellite locating module can be set to turn on every minute to obtain the current location information, and the satellite locating module also can be set to turn on every kilometer to obtain the current location information of the mobile terminal. In this way, the satellite locating module of the mobile terminal is in the closing or dormant state in most of the time, which can reduce the power consumption of the satellite locating module. [0065]The motion information obtained in the above-mentioned step 102 can include: acceleration information and initial velocity information. [0066]The acceleration information obtained in the above-mentioned step 102 can include: the acceleration information of the mobile terminal obtained through the acceleration sensor of the mobile terminal. [0067]There are more and more functions of the mobile terminal at present, which support, on the hardware, the sensors of various applications, such as GPS, acceleration, proximity, electronic compass, etc., and support Wi-Fi, BT, NFC, etc., on the transmission technology; and the GPS (AGPS) has already been widely used on the intelligence terminal devices, such as, the mobile phone, the tablet computer, etc. In the method of the present embodiment, the sensor of the mobile terminal can be utilized to obtain the motion information, such as, the acceleration information and the initial velocity information. [0068]Taking obtaining the location information with the GPS or the AGPS and obtaining the acceleration information with the sensor as the example, the GPS or AGPS module obtains the current location information as the initial location information; when the mobile terminal moves, the sensor obtains the acceleration information and the initial velocity information of the mobile terminal and calculates the variation of displacement, and then can calculate the location information at the corresponding moment according to the initial location information. It is unnecessary for the mobile terminal to use the GPS or AGPS module to obtain the current location information for update again, reducing the frequency of reading the data by the GPS or AGPS module and reducing the power consumption of the module, and the delay of the data update is reduced and the accuracy grade of the location information is improved because the number of updating the data is reduced. [0069]The GPS (AGPS) module generally reads the data once every second, and there is the problem that the power consumption is big and the location update is delayed. The power consumption of the sensor module is generally less than 1/10 of the GPS (AGPS) module. By using the sensor assisted GPS (AGPS) module, the power consumption of the GPS (AGPS) module can be reduced through reducing the frequency of reading the data by the GPS (AGPS) module; and the location information can be updated at a high frequency at the same time, which solves the problem of the data update delay. Regarding the device location read by the GPS (AGPS) module as the original point, the sensor detects the acceleration of the device, calculates the displacement increment of the device, and thus calculates the actual location of the device at the corresponding moment, and updates the location information of the device in time; the GPS (AGPS) module reads the location information again, if it is read successfully, then the initial location of the device is updated (that is, the original point of the last displacement), the displacement increment is set as 0, and the displacement increment is re-calculated, by this circulation. [0070]The above-mentioned obtaining the initial velocity information of the mobile terminal includes: [0071]judging a motion state of the mobile terminal at an initial location; if being in an static state, then the initial velocity being zero; if being in a motion state, then calculating an initial velocity of a present period according to the variation of displacement of a last period and the acceleration information obtained in the last period. [0072]When the satellite locating module of the mobile terminal, during the static state, turns on the satellite locating module, then the initial velocity is zero; if it is in the motion state, it can calculate the final velocity of the last period according to the variation of displacement and the acceleration of the last period, thus obtaining the initial velocity of the present period. [0073]The method of the present embodiment also includes the correction to the initial velocity after calculating the initial velocity. [0074]The correction includes: [0075]judging whether a difference value, between the variation of displacement of the last period obtained through the calculation via the motion information and the variation of displacement obtained directly through acquiring the location information twice by the satellite locating module, is within a preset range; if yes, then no need to correct the initial velocity; if not, then re-calculating the initial velocity. [0076]As shown in FIG. 2, the obtaining of the initial velocity V0 can be: judging the motion state of the device by using the sensors, such as, the acceleration sensor, etc. If the device turns on the locating application such as, the GPS, etc. in the static state, then V0 is 0, and the velocity at corresponding moment is calculated in real time and recorded according to the acceleration detected by the sensor. If the locating application, such as the GPS, etc., is turned on when the device moves, the displacement is calculated by using the location information read by the GPS (AGPS) module twice, and the velocity at corresponding moment is calculated by the displacement calculation formula according to the acceleration information of the device detected by the sensor. Errors exist in both of the above-mentioned two situations, and the initial velocity can be corrected constantly by the corresponding policy. For example, when the difference of the location information read by the (AGPS) module and the data calculated by the sensor is greater than a certain threshold value, the corresponding initial velocity is re-calculated according to the location information read by the (AGPS) module this time and the last time and the acceleration information of the device detected by the sensor. In order to reduce the error, when calculating the initial velocity, the time interval of the location information read by the GPS (AGPS) module twice can be reduced to the best. [0077]After obtaining the acceleration information and the initial velocity information, in the above-mentioned step 102, the displacement changing information of the mobile terminal calculated according to the motion information includes: [0078]decomposing the acceleration and the initial velocity in a longitude direction, a latitude direction and a height direction; and [0079]calculating the variation of displacement of the mobile terminal in the longitude direction, the latitude direction and the height direction according to an acceleration component and an initial velocity component decomposed in the longitude direction, the latitude direction and the height direction. [0080]Similarly, taking obtaining the location information with the GPS or the AGPS and obtaining the acceleration information with the sensor as the example, as shown in FIG. 3: the acceleration of the device can be monitored in real time through the sensor, such as, the acceleration, etc., and the acceleration is decomposed into the horizontal plane component (X axle, Y axle direction) and the vertical component (Z axis direction). By combining with the sensors, such as the electronic compass, etc., the coordinates of the sensors, such as the acceleration, etc., can be connected with the earth location coordinate; the acceleration and the initial velocity V0 are decomposed into the longitude and latitude direction and the height direction respectively; the displacement increments of the longitude and latitude direction and the height direction are calculated, and converted into the displacement increments in the longitude and latitude and the altitude direction; and the actual location of the device at the corresponding moment within the time period between the two readings by the GPS (AGPS) module by combining with the initial location of the device (the device location detected by the GPS or the AGPS). The direction sensor, such as, the electronic compass, etc., can also not be used: during the initialization, the relative relation of the coordinate of the sensor, etc., such as, the acceleration, etc., and the earth location coordinate is calculated, the azimuthal variation situation of the device is monitored through the sensor, such as the acceleration, etc., and the relative relation of the coordinate of the sensor, etc., such as, the acceleration, etc., and the earth location coordinate is constantly recorded. [0081]As shown in FIG. 4, corresponding to the above-mentioned method for obtaining location information about a mobile terminal, the present embodiment further provides a mobile terminal, comprising: a satellite locating module, a sensing module, a control module and a location information processing module; wherein, [0082]the satellite locating module is configured to: obtain current location information about the mobile terminal, and transmit the location information to the location information processing module; [0083]the control module is configured to: turn on the satellite locating module, and turn off the satellite locating module after the satellite locating module completes obtaining the information; [0084]the sensing module is configured to: collect motion information about the mobile terminal, and calculate variation of displacement of the mobile terminal according to the motion information, and transmit the variation of displacement to the location information processing module; and [0085]the location information processing module is configured to: obtain actual location information about the mobile terminal through processing the initial location information and the variation of displacement of the mobile terminal. [0086]The above-mentioned control module is further configured to: control the satellite locating module periodically turn on to obtain the current location information of the mobile terminal, update the initial location information, and control the sensing module to set the variation of displacement as zero. [0087]The satellite locating module is a global positioning system (GPS) module or an assisted global positioning system (AGPS) module. [0088]The motion information collection module in the present embodiment can be a sensor. Embodiment Two [0089]Based on the method for obtaining location information about the mobile terminal in the embodiment one, the present embodiment regards configuring the GPS or AGPS module mobile phone as the example. The device location read by the GPS (AGPS) module is used as the original point, the device acceleration is detected by using the acceleration sensor and the electronic compass, the device displacement increment is calculated, and thus the actual location of the device at the corresponding moment is calculated, and the device location information is updated in time. The GPS (AGPS) module reads the location information again, and the initial location of the device is updated (that is, the original point of the previous displacement), the displacement increment is set as 0, and the displacement increment is re-calculated, and circulate in this way. The specific time threshold value or displacement threshold value of the location information read by the GPS (AGPS) module can be set up, to make the reading frequency a bit lower, for example, reading once every minute, which can enable the GPS (AGPS) module in the dormant state with the low power consumption in most of the time. [0090]Obtaining the device motion information mainly includes: obtaining and processing the acceleration, and obtaining the initial velocity. [0091]For the obtaining and processing of the acceleration: [0092]the device acceleration is obtained through the acceleration sensor, the acceleration is decomposed into the horizontal plane component and the vertical component (the present embodiment does not consider the change in the height direction of the device, while only monitors the displacement of the horizontal direction); by combining with the electronic compass, the horizontal component of the acceleration is decomposed into ax and ay in the longitude and latitude direction, that is, X and Y direction; the decomposition diagram of the device acceleration is as FIG. 2. [0093]The frequency of reading the acceleration by using the acceleration sensor is set as reading once every 10 ms, that is, t=10 ms. [0094]The device acceleration is read respectively as: a1, a2, . . . an (it is assumed that the acceleration value is read n times by the acceleration sensor during the two reading periods of the GPS). [0095]The direction components of X-axis are respectively: ax1, ax2 . . . axn. [0096]The direction components of Y-axis are respectively: ay1, ay2 . . . ayn. [0097]For the obtaining of the initial velocity: [0098]the obtaining of the initial velocity V0 is: judging the motion state of the device by using the sensors, such as the acceleration, etc.; if the device in the static state turns on the locating application, such as, the GPS, etc., then V0 is 0, and the velocity at corresponding moment is calculated in real time and recorded according to the acceleration detected by the sensor; if the locating application, such as, the GPS, etc., is turned on when the device moves, the displacement is calculated by using the location information read by the GPS (AGPS) module twice, and then the velocity at corresponding moment is calculated according to the acceleration information of the device detected by the acceleration sensor and the electronic compass. Errors exist in both of the above-mentioned two situations, and the initial velocity can be corrected constantly by the corresponding policy. For example, when the difference of the location information read by the (AGPS) module and the data calculated by the acceleration sensor and the electronic compass is greater than a certain threshold value, the corresponding initial velocity is re-calculated according to the location information read by the (AGPS) this time and the last time and the acceleration information of the device detected by the acceleration sensor and the electronic compass. The obtaining procedure of the device velocity is as FIG. 3. [0099]When the device is under the static state, V0x=V0y=V0=0. [0100]When the device is under the motion state, the gaining mode for the V0x and V0y is as follows: (the conversions of the longitude and latitude unit and the distance unit are involved hereinafter, which are omitted in the present text.) [0101]Assuming that the device locations read by the GPS (AGPS) module twice are at point A and point B respectively, the distance between the two points is AB; the reading frequency of the GPS (AGPS) module is once every minute, that is, the time interval T for reading the point A and point B=60 s; assuming that the frequency of reading the acceleration by using the acceleration sensor is reading once for every 10 ms, that is, t=10 ms. [0102]ABx is the component of the X-axis direction, and ABy is the component of the Y-axis direction, [0103]then: ABx=V0x×Δt+(V0x+½×ax1×Δt)Δt+ . . . (V0x+ax1×Δt+ . . . ½axn×Δt)Δt  ①[0104](ax1, ax2, . . . , axn are the X-axis components of the acceleration values read by the acceleration sensor at different moments within the T period). ABy=V0y×Δt+(V0y+½×ay1×Δt)Δt+ . . . (V0y+ay1×Δt+ . . . ½ayn×Δt)Δt   ②[0105](ay1, ay2, . . . , ayn are the Y-axis components of the acceleration values read by the acceleration sensor at different moments within the T period). [0106]V0x and V0y can be gained through the above ① and ②. [0107]The velocity at the final moment in the T period is the initial velocity of the next T period, that is: [0108]the initial velocity of the X-axis direction in the next T period is: V0x+ax1×Δt+ . . . axn×Δt; [0109]the initial velocity of the Y-axis direction in the next T period is: V0y+ay1×Δt+ . . . ayn×Δt. [0110]The correction policy for the initial velocity: [0111]the displacement increment in the period calculated by the sensor is compared with the location distance read by the GPS (AGPS) module; and if it is greater than 2 m, then the initial velocity is corrected. The correction mode can adopt obtaining the initial velocity again, and the method is the same with the abo(String), 相关申请的交叉引用 [0001] 此应用程序是 35 U.S.C. §371 国家阶段 PCT 申请号 PCT/CN2013/079701,于 2013 年 7 月 19 日提交,其全部内容通过引用并入本文,并要求中国专利申请号 201210396171.1 的优先权和权益, 于 2012 年 10 月 18 日提交,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及无线通信领域,尤其涉及一种移动终端及获取移动终端位置信息的方法。 背景 [0003] 由于全球定位系统(GPS)技术所具有的全天候、高精度、自动测量等特点,作为先进的测量手段和新的生产力,已经融入到各个应用领域,如 国民经济建设、国防建设和社会发展。 [0004] 随着冷战的结束和全球经济的蓬勃发展,美国政府宣布在保证美国国家安全不受威胁的前提下,于2000年至2006年取消SA政策,GPS民用 全球范围内信号精度的提高,利用C/A码定位单点的精度从100米提高到10米,将进一步推动GPS技术的应用,提高生产效率,提高工作效率。 性能、科学水平和人们的生活质量,并刺激 GPS 市场的增长。 [0005] 辅助全球定位系统(A-GPS)技术的主要作用是能够为终端用户提供高精度的位置信息。 移动运营商采用基于A-GPS定位技术的定位服务后,终端用户可以方便快捷地获知自己或他人的当前位置,特别适用于车辆追踪导航系统和特殊车辆。 任务(装甲运钞车、救护车、消防车等),能够大幅提高车辆安全性、运输效率和服务质量。 目前,随着国内移动通信市场的日益壮大,尤其是随着3G商用的到来,中国移动和中国联通都纷纷制定并推出了自己的A-GPS方案。 [0006] 目前移动终端的产品功能越来越全面,大部分移动终端都具有卫星定位功能,如GPS、A-GPS等,用户可以随时知道自己所在的位置。 但是GPS模块或A-GPS模块等卫星定位模块需要随着用户的移动和位置的不断变化而频繁读取位置信息,从而导致问题,例如 GPS模块或A-GPS模块等卫星定位模块功耗较大,数据更新会延迟等。 概括 [0007] 本发明实施例提供一种移动终端及获取移动终端位置信息的方法,能够降低卫星定位模块的功耗。 [0008] 本发明实施例提供了一种获取移动终端位置信息的方法,包括: [0009] 开启移动终端的卫星定位模块,获取到移动终端的当前位置信息后关闭卫星定位模块,将当前位置信息作为初始位置信息。 [0010] 移动终端的感知模块采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量; 和 [0011] 根据初始位置信息和移动终端的位移变化获取移动终端的实际位置信息。 [0012]优选地,该方法还包括:周期性开启移动终端的卫星定位模块,获取移动终端的当前位置信息,更新初始位置信息,并将位移变化量设置为零。 [0013] 优选地,所述周期性开启移动终端的卫星定位模块的步骤包括: [0014] 当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块; [0015]or [0016] 判断位移变化量是否达到预设位移阈值; 如果是,则打开卫星定位模块。 [0017] 优选地,所述运动信息包括:加速度信息和初速度信息。 [0018] 优选地,所述采集移动终端的初始速度信息的步骤包括: [0019] 判断移动终端在初始位置的运动状态; 如果处于静止状态,则初速度为零; 如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。 [0020] 优选地,该方法还包括计算初速度后对初速度进行修正的步骤; 其中, [0021] 校正步骤包括: [0022] 判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内; 如果是,则无需修正初速度; 如果不是,则重新计算初始速度。 [0023] 优选地,通过运动信息计算移动终端的位移变化信息的步骤具体包括: [0024] 分解经度方向、纬度方向和高度方向的加速度和初速度; 和 [0025] 根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。 [0026] 本发明实施例提供了一种移动终端,包括:卫星定位模块、感知模块、控制模块和位置信息处理模块; 其中, [0027] 卫星定位模块,用于获取移动终端当前的位置信息,并将该位置信息发送给位置信息处理模块; [0028] 控制模块用于开启卫星定位模块,在卫星定位模块获取信息完成后关闭卫星定位模块。 [0029] 传感模块,用于采集移动终端的运动信息,根据运动信息计算移动终端的位移变化量,并将位移变化量发送给位置信息处理模块。 和 [0030] 位置信息处理模块,用于通过对初始位置信息和移动终端的位移变化量进行处理,得到移动终端的实际位置信息。 [0031] 优选地,所述控制模块还用于:控制卫星定位模块周期性开启,获取移动终端的当前位置信息,更新初始位置信息,控制传感模块将位移变化量设置为零。 [0032] 优选地,所述卫星定位模块为全球定位系统(GPS)模块或辅助全球定位系统(AGPS)模块。 [0033]优选地,所述控制模块用于通过以下方式周期性开启所述移动终端的卫星定位模块: [0034] 当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块; [0035] 要么 [0036] 判断位移变化量是否达到预设位移阈值; 如果是,则打开卫星定位模块。 [0037] 优选地,所述运动信息包括:加速度信息和初速度信息。 [0038] 优选地,所述传感模块用于通过以下方式采集所述移动终端的初始速度信息: [0039] 判断移动终端在初始位置的运动状态; 如果处于静止状态,则初速度为零; 如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。 [0040] 优选地,所述传感模块还用于: [0041] 判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内; 如果是,则无需修正初速度; 如果不是,则重新计算初始速度。 [0042] 优选地,所述传感模块用于通过以下方式计算所述移动终端的位移变化信息: [0043] 分解经度方向、纬度方向和高度方向的加速度和初速度; 和 [0044] 根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。 [0045] 本发明实施例提供了一种获取移动终端位置信息的方法,能够降低移动终端位置信息获取模块的功耗,其中,卫星定位模块获取到位置信息后关闭。 获取移动终端,然后通过移动终端的传感模块采集移动终端的运动信息,通过运动信息计算移动终端的位移变化信息,然后根据移动终端的实际位置信息得到 对初始位置信息和位移变化信息,不需要使用卫星定位模块获取移动终端的当前位置信息和频繁更新,从而降低卫星定位模块的功耗。 [0046] 另外,终端只需通过移动终端的运动信息计算位移变化信息,从而计算出实际的位置信息,可以减少数据更新延迟的出现,提高定位信息后的准确度。 避免频繁更新和获取位置信息。 附图说明 [0047] 图1为本发明实施例一提供的移动终端位置信息获取方法的基本流程图。 [0048] 图2为本发明实施例一的获取初速度的流程图。 [0049] 图3为本发明实施例一的加速度分解图。 [0050] 图4为本发明实施例一提供的移动终端的结构图。 本文件的优选实施例 [0051]下面结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。 [0052] 本发明实施例中,移动终端检测终端自身的运动状态并计算出位移变化信息,再结合卫星定位模块读取的初始位置信息计算出移动终端的实际位置( 如GPS或A-GPS模块),避免获取位置信息的模块(如GPS或A-GPS模块)频繁读取移动终端当前位置信息,降低功耗 卫星定位模块(如GPS或A-GPS模块)。 [0053] 下面结合附图对本发明实施例进行详细说明。 实施例一 [0054] 请参考图1,本实施例提供的一种获取移动终端位置信息的方法包括以下步骤。 [0055] 在步 101 、打开移动终端的卫星定位模块,获取到移动终端的当前位置信息后关闭卫星定位模块,将当前位置信息作为初始位置信息。 [0056] 在步 102 移动终端的传感模块采集移动终端的运动信息,并根据运动信息计算移动终端的位移变化量。 [0057] 在步 103 ,根据初始位置信息和移动终端的位移变化得到移动终端的实际位置信息。 [0058] 本实施例的方法还可以包括:周期性开启移动终端的卫星定位模块,获取移动终端的当前位置信息,更新初始位置信息,并将位移的变化量设置为零。 [0059] 上述开启移动终端卫星定位模块的周期可以预先设置,通过获取移动终端的运动信息,根据该运动信息计算移动终端的位移变化信息,然后再开始下一次启动。 时间段,然后根据初始位置信息和位移变化信息计算移动终端在相应时刻的实际位置,以减少获取位置信息的频率,降低相应模块的功耗。 [0060] 在本实施例的获取移动终端位置信息的方法中,周期性开启移动终端的卫星定位模块获取移动终端当前位置信息的过程可以包括: [0061] 当卫星定位模块关闭时启动定时器,当时间达到预设的时间阈值时开启卫星定位模块; [0062] 要么 [0063] 判断位移变化量是否达到预设位移阈值; 如果是,则打开卫星定位模块。 [0064] 例如,可以将卫星定位模块设置为每分钟开启一次获取当前位置信息,也可以将卫星定位模块设置为每公里开启一次获取移动终端的当前位置信息。 这样,移动终端的卫星定位模块大部分时间处于关闭或休眠状态,可以降低卫星定位模块的功耗。 [0065] 上述步骤得到的运动信息 102 可以包括:加速度信息和初速度信息。 [0066]上述步骤得到的加速度信息 102 可以包括:通过移动终端的加速度传感器获取的移动终端的加速度信息。 [0067] 目前移动终端的功能越来越多,在硬件上支持各种应用的传感器,如GPS、加速度、接近度、电子罗盘等,支持Wi-Fi、BT、NFC、 等等,关于传输技术; 而GPS(AGPS)已经广泛应用于手机、平板电脑等智能终端设备上。在本实施例的方法中,可以利用移动终端的传感器获取 运动信息,例如加速度信息和初速度信息。 [0068] 以通过GPS或AGPS获取位置信息,通过传感器获取加速度信息为例,GPS或AGPS模块获取当前位置信息作为初始位置信息; 当移动终端移动时,传感器获取移动终端的加速度信息和初始速度信息,计算出位移的变化量,然后根据初始位置信息计算出相应时刻的位置信息。 移动终端无需再使用GPS或AGPS模块获取当前位置信息进行再次更新,减少了GPS或AGPS模块读取数据的频率,降低了模块的功耗,延迟 由于减少了更新数据的次数,减少了数据更新,提高了位置信息的准确度。 [0069] GPS(AGPS)模块一般每秒读取一次数据,存在功耗大和位置更新延迟的问题。 传感器模块的功耗一般小于全球定位系统(AGPS)模块的1/10。 通过使用传感器辅助GPS(AGPS)模块,可以通过降低GPS(AGPS)模块读取数据的频率来降低​​GPS(AGPS)模块的功耗; 并且可以同时高频更新位置信息,解决了数据更新延迟的问题。 以GPS(AGPS)模块读取的设备位置为原点,传感器检测设备的加速度,计算设备的位移增量,从而计算出相应时刻设备的实际位置,并更新 及时获取设备的位置信息; GPS(AGPS)模块再次读取位置信息,如果读取成功,则更新设备的初始位置(即上次位移的原点),位移增量设置为0, 位移增量被重新计算,通过这个循环。 [0070] 上述获取移动终端的初始速度信息包括: [0071] 判断移动终端在初始位置的运动状态; 如果处于静止状态,则初速度为零; 如果处于运动状态,则根据上一周期的位移变化和上一周期获得的加速度信息计算当前周期的初速度。 [0072] 当移动终端的卫星定位模块在静止状态下开启卫星定位模块时,则初速度为零; 如果处于运动状态,则可以根据位移的变化和上一周期的加速度计算出上一周期的终速度,从而得到本周期的初速度。 [0073] 本实施例的方法还包括计算初速度后对初速度的修正。 [0074] 更正包括: [0075]判断通过运动信息计算得到的上一周期的位移变化量与卫星定位模块两次获取位置信息直接得到的位移变化量的差值是否在预设范围内; 如果是,则无需修正初速度; 如果不是,则重新计算初始速度。 [0076] 如图2所示,初始速度V0的获取可以是:通过加速度传感器等传感器判断设备的运动状态。如果设备开启了GPS等定位应用 等在静止状态下,则V0为0,根据传感器检测到的加速度,实时计算并记录相应时刻的速度。 如果设备移动时开启了GPS等定位应用,则利用GPS(AGPS)模块两次读取的位置信息计算位移,并通过 根据传感器检测到的设备加速度信息的位移计算公式。 上述两种情况都存在误差,可以通过相应的策略不断修正初速度。 例如,当(AGPS)模块读取的位置信息与传感器计算的数据的差值大于某个阈值时,根据(AGPS)读取的位置信息重新计算相应的初速度 ) 模块本次和上次以及传感器检测到的设备的加速度信息。 为了减小误差,在计算初速度时,GPS(AGPS)模块两次读取位置信息的时间间隔可以减小到最佳。 [0077] 在获取加速度信息和初速度信息后,在上述步骤中 102 ,根据运动信息计算出的移动终端的位移变化信息包括: [0078] 分解经度方向、纬度方向和高度方向的加速度和初速度; 和 [0079] 根据在经度方向、纬度方向和高度方向上分解的加速度分量和初速度分量,计算移动终端在经度方向、纬度方向和高度方向的位移变化量。 [0080] 类似地,以通过GPS或AGPS获取位置信息,通过传感器获取加速度信息为例,如图3所示:可以通过传感器实时监测设备的加速度,例如, 加速度等,并将加速度分解为水平面分量(X轴、Y轴方向)和垂直分量(Z轴方向)。 结合电子罗盘等传感器,可将加速度等传感器的坐标与地球位置坐标相连接; 加速度和初速度V0分别分解为经纬度方向和高度方向; 计算经纬度方向和高度方向的位移增量,并换算成经纬度和高度方向的位移增量; GPS(AGPS)模块在两次读数之间的时间段内,结合设备的初始位置(GPS或AGPS检测到的设备位置),得到设备在相应时刻的实际位置。 方向传感器,如电子罗盘等,也可以不用:初始化时,传感器坐标等,如加速度等,与地球位置的相对关系 计算坐标,通过传感器监测设备的方位变化情况,如加速度等,以及传感器坐标等的相对关系,如加速度等, 不断记录地球位置坐标。 [0081]如图4所示,对应于上述获取移动终端位置信息的方法,本实施例还提供了一种移动终端,包括:卫星定位模块、感知模块、控制模块和位置信息处理模块。 模块; 其中, [0082] 卫星定位模块,用于获取移动终端当前的位置信息,并将该位置信息发送给位置信息处理模块; [0083] 控制模块用于开启卫星定位模块,在卫星定位模块获取信息完成后关闭卫星定位模块。 [0084] 传感模块,用于采集移动终端的运动信息,根据运动信息计算移动终端的位移变化量,并将位移变化量发送给位置信息处理模块。 和 [0085] 位置信息处理模块,用于通过对初始位置信息和移动终端的位移变化量进行处理,得到移动终端的实际位置信息。 [0086] 上述控制模块还用于:控制卫星定位模块周期性开启,获取移动终端当前位置信息,更新初始位置信息,控制传感模块将位移变化量设置为零。 [0087] 卫星定位模块为全球定位系统(GPS)模块或辅助全球定位系统(AGPS)模块。 [0088] 本实施例中的动作信息采集模块可以是传感器。 实施例二 [0089] 基于实施例一中的获取移动终端位置信息的方法,本实施例以配置GPS或AGPS模块手机为例。 以GPS(AGPS)模块读取的设备位置为原点,利用加速度传感器和电子罗盘检测设备加速度,计算设备位移增量,从而得到设备实际所在位置 计算对应时刻,及时更新设备位置信息。 GPS(AGPS)模块再次读取位置信息,更新设备初始位置(即之前位移的原点),位移增量设置为0,重新计算位移增量 , 并以此方式循环。 可以设置GPS(AGPS)模块读取位置信息的具体时间阈值或位移阈值,使读取频率低一点,例如每分钟读取一次,这样可以使GPS(AGPS) ) 模块大部分时间处于低功耗休眠状态。 [0090] 获取设备运动信息主要包括:获取并处理加速度,获取初始速度。 [0091] 对于加速度的获取和处理: [0092] 通过加速度传感器获取设备加速度,将加速度分解为水平面分量和垂直分量(本实施例不考虑设备高度方向的变化,只监测水平方向的位移) ; 结合电子罗盘,将加速度的水平分量分解为经纬方向即X、Y方向的ax和ay; 设备加速分解图如图2。 [0093] 加速度传感器读取加速度的频率设置为每10ms读取一次,即t=10ms。 [0094] 设备加速度分别读取为:a1,a2,...。 . . an(假设在GPS的两次读取周期内,加速度传感器读取了n次加速度值)。 [0095] X轴的方向分量分别为:ax1,ax2。 . . 斧头。 [0096]Y轴的方向分量分别为:ay1,ay2。 . . 艾恩。 [0097] 为了获得初始速度: [0098] 初始速度V0的获取是:利用加速度等传感器判断设备的运动状态。 如果设备在静止状态下开启GPS等定位应用,则V0为0,根据传感器检测到的加速度,实时计算并记录相应时刻的速度。 如果设备移动时开启了GPS等定位应用,则利用GPS(AGPS)模块两次读取的位置信息计算位移,进而计算出相应时刻的速度 根据加速度传感器和电子罗盘检测到的设备加速度信息。 上述两种情况都存在误差,可以通过相应的策略不断修正初速度。 例如,当(AGPS)模块读取的位置信息与加速度传感器、电子罗盘计算的数据相差大于一定阈值时,根据位置信息重新计算相应的初速度 由(AGPS)读取本次和上次以及加速度传感器和电子罗盘检测到的设备的加速度信息。 设备速度的获取过程如图3所示。 [0099] 当器件处于静态时,V0x=V0y=V0=0。 [0100] 设备处于运动状态时,V0x和V0y的增益方式如下:(下文涉及经纬度单位和距离单位的换算,本文不再赘述。) [0101] 假设GPS(AGPS)模块两次读取到的设备位置分别在A点和B点,两点之间的距离为AB; GPS(AGPS)模块的读取频率为每分钟一次,即读取A点和B点的时间间隔T=60s; 假设加速度传感器读取加速度的频率为每10ms读取一次,即t=10ms。 [0102] ABx为X轴方向的分量,ABy为Y轴方向的分量, [0103] 然后: ABx=V 0 x×Δt +( V 0 x+ ½× 斧头 1×Δ t )Δ t + 。 . . ( V 0 x+轴 1×Δ t+ . . . ½ axn×Δt )Δ t ① [0104](ax1、ax2、...、axn为T周期内不同时刻加速度传感器读取的加速度值的X轴分量)。 ABy=V 0 y×Δt +( V 0 y+ ½× 哎呀 1×Δ t )Δ t + 。 . . ( V 0 y+y 1×Δ t+ . . . ½ ayn×Δt )Δ t ②[0105] (ay1,ay2,...,ayn为T周期内不同时刻加速度传感器读取的加速度值的Y轴分量)。 [0106] V0x和V0y可以通过上面的①和②得到。 [0107] T周期最后时刻的速度为下一个T周期的初速度,即: [0108] 下一个T周期X轴方向初速度为: V 0 x+轴 1×Δ 吨+。 . . axn×Δt; [0109] 下一个T周期Y轴方向初速度为: V 0 y+y 1×Δ 吨+。 . . ayn×Δt。 [0110] 初速度修正策略: [0111] 将传感器计算出的周期内的位移增量与GPS(AGPS)模块读取的定位距离进行比较; 如果大于2m,则修正初速度。 校正方式可以采用重新获取初速度,方法与上述获取初速度的方式相同。 [0112] 获取加速度信息和初速度信息后计算设备的位移增量,然后根据初始位置信息计算设备的实际位置,具体过程如下。 [0113] 在GPS(AGPS)模块的读取周期T内,利用GPS(AGPS)读取周期T开始时读取的位置S0和传感器计算的位移增量ΔS,可以确定设备的位置P : P=S 0+Δ S. [0114]假设Px、Py为器件在X、Y方向的位置; S0x和S0y分别为T周期起点在X、Y方向的初始位置; ΔSx、ΔSy分别为X、Y方向的位移增量。 然后, [0115] 第k次读取加速度时设备的位置为: Px=S 0 x+ΔSx; △ Sx=V 0 x×Δt +( V 0 x+ ½× 斧头 1×Δ t )Δ t + 。 . . ( V 0 x+轴 1×Δ t+ . . . ½ axk×Δt )Δ t; Py=S 0 y+ΔSy; △ Sy=V 0 y×Δt +( V 0 y+ ½× 哎呀 1×Δ t )Δ t + 。 . . ( V 0 y+y 1×Δ t+ . . . ½ ayk×Δt )Δ t. [0116] 每次计算的设备位置信息是实时更新的,设备位置信息的更新频率可达10ms一次。 可以为用户提供连续的运动路径,解决了数据更新延迟等体验问题。 [0117] T周期结束后,GPS(AGPS)模块再次读取设备位置,新读取的设备位置作为下一周期的初始位置。 将新读取的设备位置与传感器计算出的位置进行比较,以决定是否修正初始速度。 [0118] 通过上述方法,可以使GPS(AGPS)模块大部分时间处于低功耗休眠状态,降低GPS(AGPS)模块的功耗; 可以同时高频率更新位置信息,解决数据更新延迟问题。 [0119] 本领域技术人员可以理解,上述方法中的全部或部分步骤可以通过程序指令相关的硬件部件来完成,该程序可以存储在一个计算机可读取存储介质中,例如只读存储器。 可选地,上述实施例中的全部或部分步骤可以由一个或多个集成电路实现。 相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。 本文档不限制任何特定形式的硬件和软件的结合。 [0120] 以上所述是本发明实施例结合优选实施方式所做的详细说明,不能认定本发明实施例的实施只局限于这些说明。 对于本文件所属领域的技术人员来说,在不脱离本文件实施例构思的情况下,还可以做出若干简单的推演或替换,所有推演或替换均应视为体现在本文件的范围内 随附的权利要求。 工业实用性 [0121] 本发明实施例能够降低移动终端位置信息获取模块的功耗。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102901975A(String), JP2016502647A(String), JP6072266B2(String), KR101784860B1(String), KR1020150065783A(String), US20150304985A1(String), US9451580B2(String), WO2013182147A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.754 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102901975A(String), JP2016502647A(String), JP6072266B2(String), KR101784860B1(String), KR1020150065783A(String), US20150304985A1(String), US9451580B2(String), WO2013182147A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102901975A(String), JP2016502647A(String), JP6072266B2(String), KR101784860B1(String), KR1020150065783A(String), US20150304985A1(String), US9451580B2(String), WO2013182147A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270714(Integer), CN102901975A(String), 1047013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), JP2016502647A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), JP6072266B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), KR101784860B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), KR1020150065783A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:22.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), US20150304985A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), US9451580B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270714(Integer), WO2013182147A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN102901975A(String), CN102901975A(String), 1359475200(Integer), 270714(Integer), 184998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.191 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185930(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185930(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.295 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185930(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185930(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.646 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:23.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7809352B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for protecting information in a mobile terminal and a mobile terminal(String), 一种移动终端信息保护方法及移动终端(String), US7809352B2(String), A mobile terminal and a method for protecting information in a mobile terminal, the method includes: sending an information protection command to a mobile terminal via current home mobile switching center of the mobile terminal; the mobile terminal receiving and decoding the command, and executing a protection operation on the information in the mobile terminal according to a protection range defined by the command. When the mobile terminal roams, an information protection command is sent to its current home mobile switching center via a home location register for the mobile terminal. When the mobile terminal is powered off, the command is stored in the home location register, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the command. Thus, information to be protected in a mobile telephone may be deleted or locked via remote operation.(String), 一种移动终端及移动终端中的信息保护方法,该方法包括:通过移动终端当前归属的移动交换中心向移动终端发送信息保护命令; 移动终端接收并解码命令,并根据命令定义的保护范围对移动终端中的信息执行保护操作。 当移动终端漫游时,通过移动终端的归属位置寄存器向其当前归属的移动交换中心发送信息保护命令。 当移动终端关机时,该命令存储在归属位置寄存器中,当移动终端再次开机并通知归属位置寄存器时,归属位置寄存器发送该命令。 因此,可以通过远程操作删除或锁定移动电话中需要保护的信息。(String), US11/595882(String), 1163347200(Integer), US7809352B2(String), 1286208000(Integer), 1286208000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 10(Integer), CN1645951A | CN1809097A | KR1020050078741A | US20040038668A1 | US20050170811A1 | US20060293029A1 | US6741851B1 | US7360078B1 | US7539160B2(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185931(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\77a68cdcb7104ea9a9e5e5f6d91562e0.png(String), 185931(Integer), 77a68cdcb7104ea9a9e5e5f6d91562e0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for protecting information in a mobile terminal and a mobile terminal(String), 一种移动终端信息保护方法及移动终端(String), US7809352B2(String), A mobile terminal and a method for protecting information in a mobile terminal, the method includes: sending an information protection command to a mobile terminal via current home mobile switching center of the mobile terminal; the mobile terminal receiving and decoding the command, and executing a protection operation on the information in the mobile terminal according to a protection range defined by the command. When the mobile terminal roams, an information protection command is sent to its current home mobile switching center via a home location register for the mobile terminal. When the mobile terminal is powered off, the command is stored in the home location register, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the command. Thus, information to be protected in a mobile telephone may be deleted or locked via remote operation.(String), 一种移动终端及移动终端中的信息保护方法,该方法包括:通过移动终端当前归属的移动交换中心向移动终端发送信息保护命令; 移动终端接收并解码命令,并根据命令定义的保护范围对移动终端中的信息执行保护操作。 当移动终端漫游时,通过移动终端的归属位置寄存器向其当前归属的移动交换中心发送信息保护命令。 当移动终端关机时,该命令存储在归属位置寄存器中,当移动终端再次开机并通知归属位置寄存器时,归属位置寄存器发送该命令。 因此,可以通过远程操作删除或锁定移动电话中需要保护的信息。(String), US11/595882(String), 1163347200(Integer), US7809352B2(String), 1286208000(Integer), 1286208000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 10(Integer), CN1645951A | CN1809097A | KR1020050078741A | US20040038668A1 | US20050170811A1 | US20060293029A1 | US6741851B1 | US7360078B1 | US7539160B2(String), \20230420\77a68cdcb7104ea9a9e5e5f6d91562e0.png(String), 17(Integer), 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 1. A method for protecting information in a mobile terminal, comprising:sending a plurality of information protection commands to a mobile terminal via current home mobile switching center of the mobile terminal; andthe mobile terminal receiving the information protection commands and executing an operation indicated by the information protection commands on the information in the mobile terminal according to a protection range defined by the information protection commands, wherein the information protection commands includes parameters for defining an information protection range;wherein the information protection commands comprise an information delete command and an information lock command;wherein the mobile terminal locks the information according to the information lock command; andwherein after receiving the information delete command, the mobile terminal deletes the information which was previously locked by the mobile terminal.(String), 1.根据权利要求1所述的移动终端信息保护方法,其中请求执行操作的用户不知道移动终端的位置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 2. The method for protecting information in a mobile terminal according to claim 1, wherein, when the mobile terminal is powered off, the information protection commands are stored in a home location register for the mobile terminal, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the information protection commands.(String), 12.根据权利要求1所述的移动终端信息保护方法,其中请求执行操作的用户不知道移动终端是开机还是关机。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 3. The method for protecting information in a mobile terminal according to claim 2, wherein the method further comprises: after the mobile terminal executes the protection operation, it returns a response of the operation result.(String), 13.移动终端,包括:数据存储单元,用于存储用户保存的信息;信令收发单元,用于接收多个信息保护命令,其中信息保护命令包括定义信息保护范围的参数,信息保护命令包括信息删除命令和信息锁定命令;和信令处理执行单元,用于对从信令收发单元接收到的信息保护命令进行解码,并对数据存储单元中存储的用户信息执行信息保护命令指示的操作,其中,信令处理执行单元对信息进行锁定根据信息锁定命令,移动终端接收到信息删除命令后,删除先前锁定的信息。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 4. The method for protecting information in a mobile terminal according to claim 1, wherein the information protection range comprises at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information.(String), 14.根据权利要求13所述的移动终端,其中数据存储单元包括通讯录存储区、短信存储区、通话记录存储区、笔记本存储区、备忘存储区和备忘存储区中的至少一个。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 5. The method for protecting information in a mobile terminal according to claim 4, wherein the method further comprises: after the mobile terminal executes the protection operation, it returns a response of the operation result.(String), 15.根据权利要求13所述的移动终端,其中信息保护范围包括通讯录、短信、通话记录、笔记本、备忘、备忘等与隐私信息相关的存储区域中的至少一种。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 6. The method for protecting information in a mobile terminal according to claim 1, wherein the method further comprises: after the mobile terminal executes the protection operation, it returns a response of the operation result.(String), 16.一种移动终端信息保护方法,包括:通过移动终端当前的归属呼叫会话控制功能(CSCF)实体向移动终端发送多个信息保护命令;和移动终端接收并解码信息保护命令,并根据信息保护命令定义的保护范围对移动终端中的信息执行信息保护命令指示的操作,其中信息保护命令包括用于定义信息的参数保护范围;其中,信息保护命令包括信息删除命令和信息锁定命令;其中,移动终端根据信息锁定命令对信息进行锁定;和其中,移动终端接收到信息删除命令后,删除移动终端之前锁定的信息。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 7. The method for protecting information in a mobile terminal according to claim 1, wherein the information protection range comprises an address book, a short message record, a call record, a notebook, a memorandum, a reminder note, information stored on a SIM card, or combinations thereof8. The method for protecting information in a mobile terminal according to claim 1, wherein the information protection range comprises some, but not all of: an address book, a short message record, a call record, a notebook, a memorandum, a reminder note, and information stored on a SIM card.(String), 17.根据权利要求16所述的移动终端信息保护方法,其中当移动终端关机时,信息保护命令存储在移动终端的归属用户服务器中,当移动终端再次开机并通知归属用户服务器时,归属用户服务器发送信息保护命令。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 9. The method for protecting information in a mobile terminal according to claim 1, wherein the parameters for defining the information protection range are two bytes in length.(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 10. The method for protecting information in a mobile terminal according to claim 1, wherein the mobile terminal is in a home area and is powered on.(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 11. The method for protecting information in a mobile terminal according to claim 1, wherein a location of the mobile terminal is unknown to a user requesting execution of the operation.(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 12. The method for protecting information in a mobile terminal according to claim 1, wherein whether the mobile terminal is powered on or off is unknown to a user requesting execution of the operation.(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 13. A mobile terminal, comprising:a data storage unit, for storing information saved by a subscriber;a signaling transceiving unit, for receiving a plurality of information protection commands, wherein the information protection commands include parameters for defining an information protection range, the information protection commands comprise an information delete command and an information lock command; anda signaling processing and execution unit, for decoding the information protection commands received from the signaling transceiving unit, and executing an operation indicated by the information protection commands on subscriber information stored in the data storage unit, wherein the signaling processing and execution unit locks the information according to the information lock command, and deletes the information which was previously locked by the mobile terminal after receiving the information delete command.(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 14. The mobile terminal according to claim 13, wherein the data storage unit comprises at least one of an address book storage area, a short message storage area, a call record storage area, a notebook storage area, a memorandum storage area and a reminder note storage area.(String), 1(Integer), 12(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 15. The mobile terminal according to claim 13, wherein the information protection range comprises at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information.(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 16. A method for protecting information in a mobile terminal, comprising:sending a plurality of information protection commands to a mobile terminal via a current home call session control function (CSCF) entity of the mobile terminal; andthe mobile terminal receiving and decoding the information protection commands and executing an operation indicated by the information protection commands on the information in the mobile terminal according to a protection range defined by the information protection commands, wherein the information protection commands includes parameters for defining an information protection range;wherein the information protection commands comprise an information delete command and an information lock command;wherein the mobile terminal locks the information according to the information lock command; andwherein after receiving the information delete command, the mobile terminal deletes the information which was previously locked by the mobile terminal.(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185931(Integer), 17. The method for protecting information in a mobile terminal according to claim 16, wherein when the mobile terminal is powered off, the information protection commands are stored in a home subscriber server for the mobile terminal, and when the mobile terminal is powered on again and informs the home subscriber server, the home subscriber server sends the information protection commands.(String), 1(Integer), 15(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185931(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the field of communication, in particular, to a method for protecting information in a mobile terminal and a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the continual development of modern mobile communication technology, mobile telephones have been widely used as a kind of convenient communication tool. The continual combination of mobile telephone technology, computer technology and the like makes a mobile telephone integrated with various functions, such as information storage function including address book, short message, notebook and memorandum, which play an important role in our daily life. Such information stored in a mobile telephone is usually personal privacy and it may be very important for the subscriber of the mobile telephone. [0003]Because mobile telephones are small in volume, they are prone to be lost or stolen. When a mobile telephone of a subscriber is stolen or lost unfortunately, the subscriber may report the loss to a service provider via telephone or in a mobile business hall, so that unnecessary economic loss of call charge will be avoided. However, an implicit loss caused by the leakage of private information stored in the mobile telephone cannot be avoided. For example, short messages communicated with customers will leak out trade secret and business information, which will incur heavy economic loss of the subscriber. SUMMARY OF THE INVENTION [0004]The embodiments of the invention provide a method for protecting information in a mobile terminal and a mobile terminal, which may prevent the private information in a mobile terminal from leaking by remote control. [0005]A technical solution according to an embodiment of the present invention is to provide a method for protecting information in a mobile terminal, which includes:[0006]sending an information protection command to a mobile terminal via current home mobile switching center of the mobile terminal; and[0007]the mobile terminal receiving the information protection command and executing an operation indicated by the information protection command on the information in the mobile terminal according to a protection range defined by the information protection command, wherein the information protection command includes parameters for defining an information protection range. [0008]When the mobile terminal is powered off, the information protection command is stored in a home location register for the mobile terminal, and when the mobile terminal is powered on again and informs the home location register, the home location register sends the information protection command. [0009]The information protection range includes at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information. [0010]The information protection command includes at least one of an information delete command and an information lock command. [0011]In the method, after the mobile terminal executes the protection operation, it returns a response of the operation result. [0012]An embodiment of the invention further provides a mobile terminal, which includes:[0013]a data storage unit, for storing information saved by a subscriber;[0014]a signaling transceiving unit, for receiving an information protection command;[0015]a signaling processing and execution unit, for decoding the information protection command received from the signaling transceiving unit, and executing an operation indicated by the information protection command on subscriber information stored in the data storage unit, wherein the information protection command includes parameters for defining an information protection range. [0016]The data storage unit includes at least one of an address book storage area, a short message storage area, a call record storage area, a notebook storage area, a memorandum storage area and a reminder note storage area. [0017]In the mobile terminal according to the embodiment of the invention, the information protection range includes at least one of address book, short message, call record, notebook, memorandum, reminder note and other storage areas related to private information. The information protection command includes at least one of an information delete command and an information lock command. [0018]An embodiment of the invention further provides another method for protecting information in a mobile terminal, which includes:[0019]sending an information protection command to a mobile terminal via a current home call session control function (CSCF) entity of the mobile terminal;[0020]the mobile terminal receiving and decoding the information protection command, and executing an operation indicated by the information protection command on the information in the mobile terminal according to a protection range defined by the information protection command, wherein the information protection command includes parameters for defining an information protection range. [0021]The method further includes: when the mobile terminal is powered off, the information protection command is stored in a home subscriber server for the mobile terminal, and when the mobile terminal is powered on again and informs the home subscriber server, the home subscriber server sends the information protection command. [0022]The mobile terminal and the method for protecting information in the mobile terminal according to the embodiments of the invention may have the following beneficial effects: when a mobile terminal of a subscriber, such as a mobile telephone, is lost, or when information in a terminal needs to be remotely protected (the owner of the terminal cannot operate on it on site) for other reasons, a protection command may be sent to the remote mobile terminal via a maintenance and management system of a mobile switching center or a home location register, and information to be protected in the terminal may be deleted or locked, so that trouble and loss caused by information leakage will be avoided. BRIEF DESCRIPTION OF THE DRAWINGS [0023]FIG. 1 shows a structural diagram of a communication network for realizing information protection in a mobile terminal according to an embodiment of the invention; [0024]FIG. 2 shows a flow chart of the first embodiment of a method for protecting information in a mobile terminal according to the invention; [0025]FIG. 3 shows a flow chart of the second embodiment of a method for protecting information in a mobile terminal according to the invention; [0026]FIG. 4 shows a structural diagram of parameters carried in an information delete command in an embodiment of the invention; [0027]FIG. 5 shows a flow chart of information protection executed in a mobile terminal according to an embodiment of the invention; [0028]FIG. 6 shows an architecture diagram of a multimedia system based on IP according to an embodiment of the invention; [0029]FIG. 7 shows a structural diagram of a communication network of a multimedia system based on IP for realizing information protection in a mobile terminal according to an embodiment of the invention. DETAILED DESCRIPTION OF THE INVENTION [0030]The invention will now be further described in conjunction with the drawings and embodiments of the invention. [0031]FIG. 1 shows a structural diagram of a communication network for realizing information protection in a mobile terminal according to an embodiment of the invention. As shown in FIG. 1, a typical mobile communication network (such as GSM network) mainly includes a mobile station, a base station subsystem, a mobile switching subsystem and an operation and maintenance center, etc. A mobile station, i.e. a mobile terminal 101 of a subscriber, may perform speech encoding, channel encoding, information encryption, information modulation and demodulation, and information transmitting and receiving. For example, in GSM communication system, mobile terminal 101 may be equipped with a Subscriber Identity Module (SIM) card, in which all of the information needed to authenticate a subscriber identity is stored. The mobile terminal 101 cannot access a network until a SIM card is inserted. However, the invention is not limited to such a communication system, and it can also be applied to other communication systems without using SIM cards (GSM system) or UIM cards (CDMA system), such as PHS(Personal handy-phone system) and various foreign communication systems without using subscriber cards. The base station subsystem mainly performs such functions as channel allocation in a coverage area, accessing and paging of a subscriber, and information transmission, etc. The base station subsystem includes a base station transceiver (BTS) 102 directly in communication with the mobile terminal 101 via a wireless interface, and a base station controller (BSC) 103 connected with a mobile switching center (MSC) 104, wherein the base station transceiver 102 is responsible for wireless transmission and the base station controller 103 is responsible for control and management. A base station subsystem usually includes a base station controller and one or more base station transceivers. The base station transceiver 102 may be connected directly with the base station controller 103, or it may also be connected with a remote base station controller via a base station interface equipment. The mobile switching subsystem performs communication switching function and manages a database needed by subscriber data and mobility at the same time. The mobile switching subsystem includes a mobile switching center (MSC) 104, a visitor location register (VLR) 105, a home location register (HLR) 106, an authentication center and an equipment identity register (not shown) etc. The mobile switching center 104 controls mobile terminal 101 within its coverage area, provides processing, control and bearer path for calls and services, and obtains all the data needed to process a subscriber call request from three databases, i.e., the visitor location register 105, the home location register 106 and the authentication center. Similarly, the mobile switching center 104 may update the above databases according to the latest data. The visitor location register 105 stores subscriber data related to the mobile terminals within a controlled area of the mobile switching center 104, wherein the subscriber data includes parameters such as subscriber number, location area information, subscriber status and services available to a subscriber. The visitor location register 105 is a dynamic subscriber database for storing necessary data obtained from the home location register 106 of a mobile subscriber. Once the mobile subscriber leaves a controlled area of the visitor location register, it will be registered in another visitor location register, and the previous visitor location register will cancel data record of the mobile subscriber. The home location register 106 mainly stores two kinds of information: parameters related to mobile subscribers, including such data as mobile subscriber identification number, accessibility, subscriber type, etc., and information related to current locations of mobile subscribers by which call routing to a mobile terminal may be established. Therefore, each mobile subscriber should be registered at its home location register. An operation and maintenance center (OMC) 107, which is provided with an OMC operating platform to realize the man-machine interface of the operation and maintenance center 107, manages the switching entities of the whole mobile communication system. [0032]FIG. 1 shows a schematic diagram of a typical mobile communication network for implementing an embodiment of the invention. However, the invention is not limited to that. The mobile communication network includes various existing mobile communication networks, such as GSM, GPRS, CDMA etc., for example, a multimedia system based on IP shown in FIG. 6. The call session control function (CSCF) entity shown in FIG. 6 acts as a mobile switching center, while the home subscriber server (HSS) acts as an HLR. The messaging function between the CSCF and HSS entities keeps unchanged. In addition, the base station and the base station controller are not shown in FIG. 6, and the structure of a mobile access network under the IMS networking also keeps unchanged. FIG. 7 shows the structure of a communication network of a multimedia system based on IP for realizing information protection in a mobile terminal according to an embodiment of the invention, the principle of which is the same as that in FIG. 1 and will not be described in detail here. The mobile terminal according to the embodiment includes mobile telephone, SIP terminal, personal digital assistant (PDA), mobile business assistant and other handheld terminals that are capable of accessing a mobile communication network for mobile communication. [0033]When a mobile terminal of a subscriber is lost, or when information in a terminal needs to be remotely protected (the owner of the terminal cannot operate on it on site) for other reasons, there exist three cases: the subscriber knows definitely that the terminal is within the home area (not roamed across mobile switching centers) and is powered on; the subscriber does not know whether his/her mobile terminal is within the home area; and the mobile terminal is powered off. [0034]FIG. 2 shows a flow chart of a method for protecting information in a mobile terminal according to an embodiment of the invention in the first case. As shown in FIG. 2, when current home mobile switching center of the mobile terminal is known, the subscriber may send an information delete command to his/her mobile terminal via the mobile switching center, and the mobile terminal will delete related information therein based on the content of the command. The particular steps are as follows: [0035]Firstly, the subscriber requests for a credible identity verification to an authentication center of the mobile communication network, which can be realized by various subscriber identifying methods in the prior art. For example, the subscriber may go to a business hall of the network service provider, and a staff member of the business hall may verify the subscriber identity by verifying the subscriber identity card and then operate via a man-machine platform of the operation and maintenance center. The subscriber may also employ a procedure similar to reporting the loss of a mobile telephone, that is, the subscriber may be verified through his/her service password via telephone. [0036]Then in step 202, the mobile switching center sends an information delete command to the base station controller within its controlled area. The information delete command may contain parameters for defining an operation range of information delete, indicating which information to be deleted. For example, information stored in a mobile telephone, such as address book, short message record, call record, notebook, memorandum, reminder note, etc. and/or information stored in the SIM card of the subscriber, or one or a combination of more than one of the above items may be selected. [0037]In step 204, after the base station controller receives the information delete command from the mobile switching center, it will modulate and transmit the information delete command to an air interface via one or more base station transceivers within its coverage area. [0038]In step 206, the mobile terminal receives the information delete command via a corresponding air interface and deletes data within the specified range as indicated by the information delete command and the parameters contained therein. After the operation is performed, the mobile terminal returns a response message to the base station controller to indicate whether the operation succeeds. [0039]In step 208, after the base station controller receives the response message via one or more base station transceivers connected with it, it passes the response message to the mobile switching center. Then, the mobile switching center may inform the subscriber of the operation response via the man-machine platform of the operation and maintenance center. [0040]If the embodiment is implemented in the network architecture shown in FIG. 6, the mobile switching center or the visitor location register of FIG. 2 will be replaced by the call session control function (CSCF) entity of FIG. 6. [0041]For the second case in which a mobile terminal roams across mobile switching centers, a flow chart of the method for protecting information in a mobile terminal according to an embodiment of the invention is shown in FIG. 3. [0042]Firstly, in step 302, information of the current location and status of the mobile terminal needs to be obtained via a home location register, and an information delete command is sent to the current home mobile switching center of the mobile terminal via the home location register. The information delete command may contain parameters for defining an operation range of information delete, in which information to be deleted is indicated. For example, information stored in a mobile telephone such as address book, short message record, call record, notebook, memorandum, reminder note, etc. and/or information stored in the SIM card of the subscriber, or one or a combination of more than one of the above items may be selected. [0043]Then in step 304, the current home mobile switching center of the mobile terminal transfers the information delete command to a base station controller of its controlled area. [0044]In step 306, the base station controller transmits the information delete command received from the mobile switching center to an air interface via one or more base station transceivers within its coverage area. [0045]In step 308, the mobile terminal receives the information delete command via a corresponding air interface and deletes data within the specified range as indicated by the information delete command and the parameters contained therein. After the operation is performed, the mobile terminal returns a response message to the base station controller to indicate whether the operation succeeds. [0046]Then in step 310, after the base station controller receives the response message via one or more base station transceivers connected with it, it passes the response message to the mobile switching center. [0047]In step 312, the current home mobile switching center of the mobile terminal passes the response message received from its base station controller to the home location register, and the home location register informs the subscriber of the operation response via the man-machine platform of the operation and maintenance center. [0048]Similarly, if information protection is realized in the network architecture shown in FIG. 6 when a mobile terminal roams across mobile switching centers, the mobile switching center or the visitor location register of FIG. 3 should be replaced by the call session control function (CSCF) entity of FIG. 6, and the home location register of FIG. 3 should be replaced by the home subscriber server (HSS) of FIG. 6. [0049]If a mobile terminal is powered off and cannot receive an information delete command when a subscriber requires to delete information in the mobile terminal, an “information delete” flag may be set in a corresponding location in a home location register, which indicates that the mobile terminal needs information protection, and at the same time, parameters and parameter contents related to the information delete command may be stored in the home location register. When the mobile terminal is powered on again, a location update procedure will be triggered and the current home mobile switching center of the mobile terminal will send a message to inform the home location register of the subscriber of the latest location and status of the mobile terminal. At this time, the home location register may start the above information delete operation based on the “information delete” flag and related parameters stored therein. [0050]In the method for protecting information in a mobile terminal according to the embodiment, the information delete command sent to and received and executed by the mobile terminal contains parameters for defining a delete operation range. The parameters may be encoded in various ways. For example, the parameters may be in TLV format, that is, the parameters may comprise parameter name T, parameter length L and parameter content V. FIG. 4 shows one form of such a parameter, wherein Octet 1 refers to parameter name, Octet 2 refers to parameter length and Octet 3 to Octet k refer to parameter content. As a result, one or more contents may be included in the parameter. As for parameter “delete range”, the length of parameter name may be 1 byte, or 3 bytes or the like. For example, it may be set as 0x01, or any other value, so long as it is different from the names of other existing parameters. The length of the parameter may be 0x02, which indicates that the length of the parameter is 2 bytes. It may also be defined longer, for example 3 bytes, so as to represent more parameter contents. The parameter content indicating a “delete range” may be represented by 2 bytes, for example: [0051]byte 10x010x02. . .Mobile TerminalSubscriber CardStorage AreaStorage Areabyte 20x010x020x03. . .Short MessageAddress BookNotebookStorage AreaStorage AreaStorage Area [0052]Parameter content may be in a more compact format or in any other format. For example, parameter content may be compressed in one byte. [0053]The mobile terminal according to an embodiment of the invention mainly includes a signaling transceiving unit, a signaling processing and execution unit, and a data storage unit. The signaling transceiving unit is responsible for receiving a message from an air interface and passing the message command to the signaling processing and execution unit. It is also responsible for processing messages from the signaling processing and execution unit and sending the processed messages to an air interface via wireless signals. The signaling processing and execution unit is responsible for identifying an information delete command from the message received from the signaling transceiving unit, decoding the message, resolving the “delete range” parameter and contents of the parameter therein, performing data delete operation according to the contents of the parameter so as to delete corresponding information in the data storage unit, and creating a response message to be sent to a base station controller. The data storage unit is used to store data saved by the subscriber. the data storage unit includes a mobile terminal storage area and a subscriber card storage area in respect of physical entities for storing, and includes an address book storage area, a short message storage area, a call record storage area, a notebook storage area, a memorandum storage area, and a reminder note storage area, etc. in respect of the contents stored therein. Each storage area in the data storage unit may be added, deleted, modified, queried or locked, etc. After an operation is executed, an execution result will be returned to the invoker. [0054]FIG. 5 shows a flow chart of information protection executed in a mobile terminal according to an embodiment of the invention. As shown in FIG. 5, a particular operation flow in a mobile terminal is as follows: [0055]In step 402, the signaling transceiving unit of the mobile terminal receives an information delete command in the form of wireless signal from a base station transceiver via an air interface, and demodulates the wireless signal. Various message contents are resolved and then passed to the signaling processing and execution unit. [0056]In step 404, after the signaling processing and execution unit identifies the received message as an information delete command, it decodes the message and resolves a parameter “delete range” and the content of the parameter contained therein. [0057]In step 406, the signaling processing and execution unit deletes data in specific storage areas of the data storage unit according to the content of the parameter “delete range”. For example, a deleting operation range indicated in a two-byte parameter content “delete range” of the above example includes “address book storage area”, “short message storage area” and “notebook storage area” of the “mobile terminal storage area” and the “subscriber card storage area”, thus the signaling processing and execution unit will delete the contents of all address books, all short messages and all notebooks in the data storage unit as indicated by the parameter “delete range”. [0058]In step 408, after the deleting operation is performed, the data storage unit returns a data deletion result to the signaling processing and execution unit. [0059]In step 410, the signaling processing and execution unit creates an information delete response message containing the operation result according to the deletion result, and passes the response message to the signaling transceiving unit. [0060]In step 412, the signaling transceiving unit modulates the information delete response message created by the signaling processing and execution unit, and sends it to an air interface in the form of wireless signal. [0061]In another embodiment of the invention, a subscriber may send an information lock command to his/her mobile terminal via a mobile switching center. The mobile terminal locks the related information therein according to parameter contents of the information lock command so as to prevent illegal access. The method for sending an information lock command and the method for processing the information lock command by a mobile terminal according to the embodiment are similar to those for the above information delete command. The information lock command contains parameters for defining a lock range, which can be encoded in similar ways to those for the above information delete command. The information lock command may be used in cases in which a subscriber cannot be sure whether his/her mobile terminal is lost indeed. If it is found out that the mobile terminal is not lost, the subscriber may operate on the mobile terminal to unlock it and regain access to related data. This can be realized in various ways of the prior art. If it is found out that the mobile terminal is lost indeed, then the subscriber may send an information delete command via the mobile switching center to permanently delete the related information in the mobile terminal. [0062]It should be understood that the above detailed description of the particular embodiments is only illustrative of the present invention and should not be construed as limiting the scope of the invention which is defined by the appended claims.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端中的信息保护方法及移动终端。 发明背景 [0002] 随着现代移动通讯技术的不断发展,手机作为一种便捷的通讯工具得到了广泛的应用。 移动电话技术、计算机技术等的不断结合,使得手机集多种功能于一体,例如通讯录、短信、笔记本、备忘录等信息存储功能,在我们的日常生活中扮演着重要的角色。 这些存储在移动电话中的信息通常属于个人隐私,对于移动电话用户而言可能非常重要。 [0003] 由于手机体积小,容易丢失或被盗。 当用户的手机不幸被盗或丢失时,用户可以通过电话或到移动营业厅向服务提供商挂失,从而避免不必要的话费经济损失。 但是,手机中存储的隐私信息泄露所带来的隐性损失是无法避免的。 例如,与客户通信的短信会泄露商业秘密和商业信息,给用户带来巨大的经济损失。 发明内容 [0004] 本发明实施例提供一种移动终端中信息的保护方法及移动终端,能够防止移动终端中的隐私信息被远程控制泄露。 [0005] 本发明实施例提供的技术方案是提供一种移动终端中的信息保护方法,包括: [0006]通过移动终端当前归属移动交换中心向移动终端发送信息保护命令; 和[0007] 移动终端接收信息保护命令,并根据信息保护命令定义的保护范围,对移动终端中的信息执行信息保护命令指示的操作,其中,信息保护命令包括用于定义信息保护范围的参数 . [0008] 当移动终端关机时,信息保护命令存储在移动终端的归属位置寄存器中,当移动终端再次开机并通知归属位置寄存器时,归属位置寄存器发送信息保护命令。 [0009] 信息保护范围包括通讯录、短信、通话记录、笔记本、备忘录、备忘等与隐私信息相关的存储区域中的至少一种。 [0010] 信息保护命令包括信息删除命令和信息锁定命令中的至少一种。 [0011] 该方法中,移动终端执行保护操作后,返回操作结果响应。 [0012] 本发明实施例还提供一种移动终端,包括: [0013] 数据存储单元,用于存储用户保存的信息;[0014] 信令收发单元,用于接收信息保护命令;[0015] 信令处理和执行单元,用于对从信令收发单元接收到的信息保护命令进行解码,并对数据存储单元中存储的用户信息执行信息保护命令指示的操作,其中,信息保护命令包括用于定义 信息保护范围。 [0016] 数据存储单元包括通讯录存储区、短信存储区、通话记录存储区、笔记本存储区、备忘录存储区和备忘存储区中的至少一个。 [0017] 在根据本发明实施例的移动终端中,信息保护范围包括通讯录、短信、通话记录、笔记本、备忘录、备忘和其他与隐私信息相关的存储区域中的至少一种。 信息保护命令包括信息删除命令和信息锁定命令中的至少一种。 [0018] 本发明实施例还提供了另一种移动终端中的信息保护方法,包括: [0019] 通过移动终端当前的归属呼叫会话控制功能(CSCF)实体向移动终端发送信息保护命令;[0020] 移动终端接收并解码信息保护命令,根据信息保护命令定义的保护范围,对移动终端中的信息执行信息保护命令指示的操作,其中,信息保护命令包括用于定义信息保护命令的参数 信息保护范围。 [0021] 该方法还包括:当移动终端关机时,将信息保护命令存储在移动终端的归属用户服务器中,当移动终端再次开机并通知归属用户服务器时,归属用户服务器发送 信息保护命令。 [0022]根据本发明实施例的移动终端及移动终端中的信息保护方法,可以具有以下有益效果:当用户的移动终端如手机丢失时,或者当终端中的信息丢失时。 其他原因需要远程保护(终端所有者不能现场操作),可以通过移动交换中心维护管理系统或归属位置寄存器向远程移动终端发送保护命令, 终端中需要保护的信息可以被删除或锁定,从而避免信息泄露带来的麻烦和损失。 附图的简要说明 [0023] 图1示出了根据本发明实施例的在移动终端中实现信息保护的通信网络的结构图; [0024] 图2为本发明移动终端信息保护方法第一实施例的流程图; [0025] 图3为本发明移动终端信息保护方法第二实施例的流程图; [0026] 图4为本发明实施例中信息删除命令携带的参数结构图; [0027] 图5示出了根据本发明实施例的在移动终端中执行的信息保护的流程图。 [0028] 图6示出了根据本发明实施例的基于IP的多媒体系统的架构图。 [0029] 图7示出了根据本发明实施例的用于在移动终端中实现信息保护的基于IP的多媒体系统的通信网络结构图。 发明详述 [0030] 下面结合附图和实施例对本发明作进一步说明。 [0031] 图1示出了根据本发明实施例的用于在移动终端中实现信息保护的通信网络的结构图。 如图1所示,一个典型的移动通信网络(如GSM网络)主要包括移动台、基站子系统、移动交换子系统和运维中心等。移动台,即移动终端 101 一个用户,可以进行语音编码、信道编码、信息加密、信息调制解调、信息发送和接收。 例如,在 GSM 通信系统中,移动终端 101 可以配备用户身份模块 (SIM) 卡,其中存储了验证用户身份所需的所有信息。 移动端 101 在插入 SIM 卡之前无法访问网络。 但是,本发明不限于这样的通信系统,也可以应用于不使用SIM卡(GSM系统)或UIM卡(CDMA系统)的其他通信系统,例如PHS(Personal handy-phone system)和 不使用用户卡的各种外国通信系统。 基站子系统主要完成覆盖区域内的信道分配、用户接入和寻呼、信息传输等功能。基站子系统包括基站收发信机(BTS) 102 直接与移动终端通信 101 通过无线接口和基站控制器 (BSC) 103 与移动交换中心 (MSC) 相连 104 ,其中基站收发器 102 负责无线传输和基站控制器 103 负责控制和管理。 基站子系统通常包括基站控制器和一个或多个基站收发器。 基站收发器 102 可以直接与基站控制器相连 103,也可以通过基站接口设备与远程基站控制器相连。 移动交换子系统执行通信交换功能,同时管理用户数据和移动性所需的数据库。 移动交换子系统包括移动交换中心(MSC) 104 , 访客位置寄存器 (VLR) 105 , 归属位置寄存器 (HLR) 106 、认证中心和设备身份寄存器(未示出)等。移动交换中心 104 控制移动端 101 在其覆盖范围内,为呼叫和服务提供处理、控制和承载路径,并从访客位置寄存器三个数据库中获取处理用户呼叫请求所需的所有数据 105 , 归属地寄存器 106 和认证中心。 同样,移动交换中心 104 可能会根据最新数据更新上述数据库。 访客位置寄存器 105 在移动交换中心的受控区域内存储与移动终端相关的用户数据 104 其中,用户数据包括用户号码、位置区域信息、用户状态和用户可获得的服务等参数。 访客位置寄存器 105 是一个动态用户数据库,用于存储从归属位置寄存器获得的必要数据 106 一个移动用户。 一旦移动用户离开访问者位置寄存器的控制区域,它将在另一个访问者位置寄存器中注册,之前的访问者位置寄存器将取消该移动用户的数据记录。 家庭位置寄存器 106 主要存储两种信息:与移动用户相关的参数,包括移动用户标识号、可接入性、用户类型等数据,以及与移动用户当前位置相关的信息,通过这些信息可以建立到移动终端的呼叫路由 . 因此,每个移动用户都应该在其归属位置寄存器中进行注册。 运维中心(OMC) 107 ,配备OMC操作平台,实现运维中心人机界面 107 ,管理整个移动通信系统的交换实体。 [0032] 图1示出了用于实施本发明实施例的典型移动通信网络的示意图。 然而,本发明不限于此。 移动通信网络包括现有的各种移动通信网络,例如GSM、GPRS、CDMA等,例如图6所示的基于IP的多媒体系统。图6所示的呼叫会话控制功能(CSCF)实体作为 移动交换中心,而归属用户服务器 (HSS) 充当 HLR。 CSCF和HSS实体之间的消息传递功能保持不变。 另外,图6中没有显示基站和基站控制器,IMS组网下的移动接入网络结构也保持不变。 图7示出了根据本发明实施例的基于IP实现移动终端信息保护的多媒体系统的通信网络结构,其原理与图1相同,在此不再赘述。 细节在这里。 本实施例的移动终端包括移动电话、SIP终端、个人数字助理(Personal Digital Assistant,PDA)、移动商务助理等能够接入移动通信网络进行移动通信的手持终端。 [0033] 当用户的移动终端丢失,或其他原因需要对终端信息进行远程保护(终端所有者无法现场操作)时,存在三种情况: 用户明确知道终端 在家庭区域内(未跨移动交换中心漫游)并且已开机; 用户不知道自己的移动终端是否在归属地范围内; 移动终端关机。 [0034]图2示出了第一种情况下根据本发明实施例的移动终端中的信息保护方法的流程图。 如图2所示,当移动终端当前归属的移动交换中心已知时,用户可以通过移动交换中心向其移动终端发送信息删除命令,移动终端将根据移动终端删除其中的相关信息。 命令的内容。 具体步骤如下: [0035] 首先,用户向移动通信网络的认证中心请求可信身份验证,这可以通过现有技术中的各种用户识别方法来实现。 例如,用户可以前往网络服务提供商的营业厅,营业厅的工作人员可以通过验证用户身份证来验证用户身份,然后通过运维人机平台进行操作。 中央。 用户也可以采用类似手机挂失的流程,即通过电话通过服务密码对用户进行验证。 [0036] 然后一步 202 ,移动交换中心向其控制区域内的基站控制器发送信息删除命令。 信息删除命令中可以包含定义信息删除操作范围的参数,指示删除哪些信息。 例如,手机中存储的通讯录、短信记录、通话记录、笔记本、备忘、备忘等信息和/或用户SIM卡中存储的信息,或其中一种或多种的组合 可以选择以上项目中的一项以上。 [0037] 在步 204 基站控制器接收到来自移动交换中心的信息删除命令后,将信息删除命令调制后通过其覆盖范围内的一个或多个基站收发器发送至空中接口。 [0038] 在步 206 ,移动终端通过相应的空口接收信息删除命令,根据信息删除命令及其中包含的参数,删除指定范围内的数据。 操作完成后,移动终端向基站控制器返回响应消息,指示操作是否成功。 [0039] 在步 208 ,基站控制器通过与之相连的一个或多个基站收发器接收到响应消息后,将响应消息传递给移动交换中心。 然后,移动交换中心可以通过操作维护中心的人机平台将操作响应告知用户。 [0040] 如果该实施例在图6所示的网络架构中实现,则图2的移动交换中心或访问者位置寄存器将被图6的呼叫会话控制功能(CSCF)实体代替。 [0041] 针对移动终端漫游跨越移动交换中心的第二种情况,本发明实施例的移动终端信息保护方法的流程图如图3所示。 [0042] 首先,一步 302 ,需要通过归属位置寄存器获取移动终端的当前位置和状态信息,并通过归属位置寄存器向移动终端的当前归属移动交换中心发送信息删除命令。 信息删除命令中可以包含定义信息删除操作范围的参数,其中指示要删除的信息。 例如,手机中存储的通讯录、短信记录、通话记录、笔记本、备忘、备忘等信息和/或用户SIM卡中存储的信息,或其中一种或多种的组合 可以选择以上项目之一。 [0043] 然后一步 304 ,移动终端的当前归属移动交换中心将信息删除命令传递给其控制区的基站控制器。 [0044] 在步 306,基站控制器通过其覆盖范围内的一个或多个基站收发器,将接收到的来自移动交换中心的信息删除命令发送至空中接口。 [0045] 在步 308 ,移动终端通过相应的空口接收信息删除命令,根据信息删除命令及其中包含的参数,删除指定范围内的数据。 操作完成后,移动终端向基站控制器返回响应消息,指示操作是否成功。 [0046] 然后一步 310 ,基站控制器通过与之相连的一个或多个基站收发器接收到响应消息后,将响应消息传递给移动交换中心。 [0047] 在步 312 ,移动终端的当前归属移动交换中心将从其基站控制器接收到的响应消息传递给归属位置寄存器,归属位置寄存器通过运维人机平台将操作响应通知用户 中央。 [0048] 类似地,如果在图6所示的网络架构中实现移动终端漫游跨移动交换中心时的信息保护,则图3的移动交换中心或访问者位置寄存器应该由呼叫会话控制功能(CSCF)实体代替 图6的归属位置寄存器和图3的归属位置寄存器应该由图6的归属订户服务器(HSS)代替。 [0049] 如果当用户要求删除移动终端中的信息时,移动终端处于关机状态,无法接收到信息删除命令,则可以在归属位置寄存器中的相应位置设置“信息删除”标志,表示该移动终端 终端需要信息保护,同时归属位置寄存器中可以存储与信息删除命令相关的参数和参数内容。 当移动终端再次开机时,将触发位置更新流程,移动终端当前归属移动交换中心发送消息通知用户归属位置寄存器该移动终端的最新位置和状态 . 此时,归属位置寄存器可以根据其中存储的“信息删除”标志和相关参数启动上述信息删除操作。 [0050] 本实施例提供的移动终端中的信息保护方法,向移动终端发送接收并执行的信息删除命令中包含定义删除操作范围的参数。 可以以各种方式对参数进行编码。 例如,参数可以是TLV格式,即参数可以包括参数名称T、参数长度L和参数内容V。图4示出了这种参数的一种形式,其中Octet 1 指参数名,Octet 2 指参数长度和Octet 3 到Octet k 参考参数内容。 结果,参数中可以包括一个或多个内容。 对于参数“删除范围”,参数名的长度可以是1个字节,也可以是3个字节等。 例如,可以设置为0x01,或者其他任何值,只要与其他已有参数的名称不同即可。 参数的长度可以是0x02,表示参数的长度是2个字节。 也可以定义的更长一些,比如3个字节,以表示更多的参数内容。 表示“删除范围”的参数内容可以用2个字节来表示,例如: [0051] 字节 1 0x01 0x02 . . . 手机端 用户卡 储藏区域 储藏区域 字节 2 0x01 0x02 0x03 . . . 短消息 地址簿 笔记本 储藏区域 储藏区域 储藏区域 [0052] 参数内容可以采用更紧凑的格式或任何其他格式。 例如,参数内容可以压缩成一个字节。 [0053]本发明实施例的移动终端主要包括信令收发单元、信令处理执行单元和数据存储单元。 信令收发单元负责从空中接口接收消息,并将消息命令传递给信令处理执行单元。 它还负责处理来自信令处理执行单元的消息,并将处理后的消息通过无线信号发送到空中接口。 信令处理执行单元负责从信令收发单元接收到的报文中识别信息删除命令,对报文进行解码,解析其中的“删除范围”参数和参数内容,根据内容进行数据删除操作 参数删除数据存储单元中的相应信息,并生成响应消息发送给基站控制器。 数据存储单元用于存储用户保存的数据。 数据存储单元包括移动终端存储区和用户卡存储区,就存储物理实体而言,包括通讯录存储区、短信存储区、通话记录存储区、笔记本存储区、 备忘录存储区和备忘存储区等就存储在其中的内容而言。 数据存储单元中的每个存储区域都可以进行增删改查、查询或锁定等操作,执行完一个操作后,会返回一个执行结果给调用者。 [0054] 图5示出了根据本发明实施例的在移动终端中执行的信息保护的流程图。 如图5所示,移动终端中的具体操作流程如下: [0055] 在步 402 移动终端的信令收发单元通过空中接口从基站收发器接收无线信号形式的信息删除命令,并对无线信号进行解调。 解析各种消息内容,然后传递给信令处理和执行单元。 [0056] 在步 404 信令处理与执行单元将接收到的消息识别为信息删除命令后,对该消息进行解码,解析出参数“删除范围”以及其中包含的参数内容。 [0057] 在步 406 、信令处理与执行单元根据参数“删除范围”的内容删除数据存储单元的特定存储区域中的数据。 例如,上述例子的二字节参数内容“删除范围”所指示的删除操作范围包括“移动终端存储区”的“通讯录存储区”、“短信存储区”和“笔记本存储区” ”和“用户卡存储区”,则信令处理执行单元将删除参数“删除范围”所指示的数据存储单元中的所有通讯录、所有短信和所有笔记本的内容。 [0058] 在步 408 ,在执行删除操作后,数据存储单元向信令处理执行单元返回数据删除结果。 [0059] 在步 410 ,信令处理执行单元根据删除结果创建包含操作结果的信息删除响应消息,并将该响应消息传递给信令收发单元。 [0060] 在步 412 、信令收发单元对信令处理执行单元生成的信息删除响应消息进行调制,以无线信号的形式发送至空中接口。 [0061]在本发明的另一个实施例中,用户可以通过移动交换中心向他/她的移动终端发送信息锁定命令。 移动终端根据信息锁定命令的参数内容锁定其中的相关信息,以防止非法访问。 本实施例的移动终端发送信息锁定命令的方法和处理信息锁定命令的方法与上述信息删除命令类似。 信息锁定命令中包含定义锁定范围的参数,其编码方式与上述信息删除命令类似。 信息锁定命令可以用于用户不能确定自己的移动终端是否确实丢失的情况。 如果发现移动终端没有丢失,用户可以在移动终端上操作解锁,重新获取相关数据。 这可以通过现有技术的各种方式来实现。 如果发现移动终端确实丢失,则用户可以通过移动交换中心发送信息删除命令,永久删除移动终端中的相关信息。 [0062] 应当理解,以上对特定实施例的详细描述仅是对本发明的说明,不应被解释为限制由所附权利要求限定的本发明的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.737 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.737 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN100471312C(String), CN101161006A(String), CN101161006B(String), CN1874596A(String), US20070111728A1(String), US7809352B2(String), WO2007054004A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN100471312C(String), CN101161006A(String), CN101161006B(String), CN1874596A(String), US20070111728A1(String), US7809352B2(String), WO2007054004A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN100471312C(String), CN101161006A(String), CN101161006B(String), CN1874596A(String), US20070111728A1(String), US7809352B2(String), WO2007054004A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270831(Integer), CN100471312C(String), 1047310(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:24.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270831(Integer), CN101161006A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270831(Integer), CN101161006B(String), 1047304(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270831(Integer), CN1874596A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270831(Integer), US20070111728A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270831(Integer), US7809352B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270831(Integer), WO2007054004A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN100471312C(String), CN100471312C(String), 1237305600(Integer), 270831(Integer), 185115(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 270827(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 270827(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185931(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185931(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185931(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.496 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.496 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.496 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185931(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185931(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:25.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20150067795A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Control method and device for mobile terminal, and mobile terminal(String), 移动终端的控制方法、装置及移动终端(String), US20150067795A1(String), The present invention relates to the field of mobile communications, and provides a control method and device of a mobile terminal, and the mobile terminal. The control method of a mobile terminal comprises: a control device of a mobile terminal receiving a first switching instruction that instructs switching the mobile terminal to a security mode; and the control device of the mobile terminal performing control processing on the mobile terminal according to the first switching instruction, and switching the mobile terminal to the security mode, so that the mobile terminal does not send service data to a base station. The technical solution of the present invention can effectively protect the information security of the mobile terminal.(String), 本发明涉及移动通信领域,提供了一种移动终端的控制方法、装置及移动终端。 一种移动终端的控制方法,包括:移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,使得移动终端不向基站发送业务数据。 本发明的技术方案能够有效保护移动终端的信息安全。(String), US14/391580(String), 1340553600(Integer), US20150067795A1(String), 1425484800(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 9(Integer), CN201515419U | US20050267650A1 | US20100279626A1 | US20110065375A1 | US20110241827A1 | US20120052879A1 | US20120299847A1 | US20150082422A1 | US8126431B2(String), 18(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185932(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\be168f9c7b044c159c3d5b8455f7ce09.png(String), 185932(Integer), be168f9c7b044c159c3d5b8455f7ce09.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Control method and device for mobile terminal, and mobile terminal(String), 移动终端的控制方法、装置及移动终端(String), US20150067795A1(String), The present invention relates to the field of mobile communications, and provides a control method and device of a mobile terminal, and the mobile terminal. The control method of a mobile terminal comprises: a control device of a mobile terminal receiving a first switching instruction that instructs switching the mobile terminal to a security mode; and the control device of the mobile terminal performing control processing on the mobile terminal according to the first switching instruction, and switching the mobile terminal to the security mode, so that the mobile terminal does not send service data to a base station. The technical solution of the present invention can effectively protect the information security of the mobile terminal.(String), 本发明涉及移动通信领域,提供了一种移动终端的控制方法、装置及移动终端。 一种移动终端的控制方法,包括:移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,使得移动终端不向基站发送业务数据。 本发明的技术方案能够有效保护移动终端的信息安全。(String), US14/391580(String), 1340553600(Integer), US20150067795A1(String), 1425484800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 9(Integer), CN201515419U | US20050267650A1 | US20100279626A1 | US20110065375A1 | US20110241827A1 | US20120052879A1 | US20120299847A1 | US20150082422A1 | US8126431B2(String), \20230420\be168f9c7b044c159c3d5b8455f7ce09.png(String), 18(Integer), 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 1. A control method for a mobile terminal, comprising:receiving, by a control device for the mobile terminal, a first switching instruction which instructs switching the mobile terminal to a security mode; andperforming, by the control device for the mobile terminal, control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station.(String), 1.根据权利要求8所述的移动终端的控制装置,其中第一切换指令携带密码,并且其中,控制模块用于根据预设的关闭密码对第一切换指令携带的密码进行验证,在验证通过后关闭移动终端的上行业务通道。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 2. The control method for the mobile terminal according to claim 1, wherein performing, by the control device for the mobile terminal, control processing on the mobile terminal according to the first switching instruction comprises:disabling, by the control device for the mobile terminal, an uplink service channel of the mobile terminal.(String), 12.根据权利要求10所述的移动终端的控制装置,其中第二切换指令携带密码,并且其中,所述控制模块,用于根据预设的开启密码对所述第二切换指令携带的密码进行验证,在所述第二切换指令携带的密码验证通过后,开启所述移动终端的上行业务通道。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 3. The control method for the mobile terminal according to claim 2, further comprising:after disabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal,prompting, by the control device for the mobile terminal, a user whether to switch the mobile terminal from the security mode to a normal mode when the mobile terminal receives an external signal.(String), 13.移动终端,包括8.根据权利要求7所述的控制装置。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 4. The control method for the mobile terminal according to claim 3, further comprising:after prompting the user whether to switch the mobile terminal from the security mode to the normal mode,receiving, by the control device for the mobile terminal, a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; andenabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode.(String), 14.移动终端,包括9.根据权利要求8所述的控制装置。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 5. The control method for the mobile terminal according to claim 2, wherein the first switching instruction carries a password, andwherein disabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal comprises:verifying, by the control device for the mobile terminal, the password carried by the first switching instruction according to a preset disabling password, and disabling the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification.(String), 15.移动终端,包括10.根据权利要求9所述的控制装置。(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 6. The control method for the mobile terminal according to claim 4, wherein the second switching instruction carries a password, andwherein enabling, by the control device for the mobile terminal, the uplink service channel of the mobile terminal comprises:verifying, by the control device for the mobile terminal, the password carried by the second switching instruction according to a preset enabling password, and enabling the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification.(String), 16.移动终端,包括11.根据权利要求10所述的控制装置。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 7. A control device for a mobile terminal, comprising:an input module, configured to receive a first switching instruction which instructs switching the mobile terminal to a security mode; anda control module, configured to perform control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station.(String), 17.移动终端,包括12.根据权利要求11所述的控制装置。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 8. The control device for the mobile terminal according to claim 7, wherein the control module is configured to disable an uplink service channel of the mobile terminal so as to switch the mobile terminal to the security mode.(String), 18.移动终端,包括13.根据权利要求12所述的控制装置。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 9. The control device for the mobile terminal according to claim 8, further comprising:a prompting module, configured to, when the mobile terminal receives an external signal, prompt a user whether to switch the mobile terminal from the security mode to a normal mode.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 10. The control device for the mobile terminal according to claim 9, wherein the input module is further configured to receive a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode, andwherein the control module is further configured to enable an uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 11. The control device for the mobile terminal according to claim 8, wherein the first switching instruction carries a password, andwherein the control module is configured to verify the password carried by the first switching instruction according to a preset disabling password and disable the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification.(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 12. The control device for the mobile terminal according to claim 10, wherein the second switching instruction carries a password, andwherein the control module is configured to verify the password carried by the second switching instruction according to a preset enabling password and enable the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 13. A mobile terminal, comprising the control device according to claim 7.(String), 1(Integer), 12(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 14. A mobile terminal, comprising the control device according to claim 8.(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 15. A mobile terminal, comprising the control device according to claim 9.(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 16. A mobile terminal, comprising the control device according to claim 10.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 17. A mobile terminal, comprising the control device according to claim 11.(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185932(Integer), 18. A mobile terminal, comprising the control device according to claim 12.(String), 1(Integer), 17(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185932(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of communications, and in particular to a control method and a control device for a mobile terminal, and the mobile terminal. BACKGROUND [0002]Along with the increasing popularization of the mobile terminal, the mobile terminal has more and more functions, and thus the mobile terminal has become an essential communication tool for the daily life of a user. [0003]However, with the continuous expansion of a wireless network, the user stores more and more privacy in the mobile terminal, and along with the development of science and technology, there are more and more eavesdropping methods, so that a hacker or a virus may steal information about an individual and a company by controlling the mobile terminal. For example, during a business meeting, if the mobile terminal is carried to a meeting site, although the mobile terminal is set into a silent mode, meeting contents can still be leaked through the mobile terminal, so that the privacy of the individual and secretes of the company are greatly threatened. SUMMARY [0004]A technical problem to be solved by the embodiments of the disclosure is to provide a control method and a control device for a mobile terminal, and the mobile terminal, which can effectively ensure the information security of the mobile terminal. [0005]In order to solve the technical problem above, the embodiments of the disclosure provides the following technical solutions [0006]According to an aspect, a control method for a mobile terminal is provided, including that: [0007]a control device for the mobile terminal receives a first switching instruction which instructs switching the mobile terminal to a security mode; and [0008]the control device for the mobile terminal performs control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0009]Preferably, the step the control device for the mobile terminal performs control processing on the mobile terminal according to the first switching instruction may include that: [0010]the control device for the mobile terminal disables an uplink service channel of the mobile terminal. [0011]Preferably, after the control device for the mobile terminal disables the uplink service channel of the mobile terminal, the method may further include that: [0012]the control device for the mobile terminal prompts, when the mobile terminal receives an external signal, a user whether to switch the mobile terminal from the security mode to a normal mode or not. [0013]Preferably, after the control device prompts the user whether to switch the mobile terminal from the security mode to the normal mode, the method may further include that: [0014]the control device for the mobile terminal receives a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and [0015]the control device for the mobile terminal enables the uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode. [0016]Preferably, the first switching instruction may carry a password, and the step that the control device for the mobile terminal disables the uplink service channel of the mobile terminal may include that: [0017]the control device for the mobile terminal verifies the password carried by the first switching instruction according to a preset disabling password, and disables the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification. [0018]Preferably, the second switching instruction may carry a password, and the step that the control device for the mobile terminal enables the uplink service channel of the mobile terminal may include that: [0019]the control device for the mobile terminal verifies the password carried by the second switching instruction according to a preset enabling password, and enables the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification. [0020]The embodiment of the disclosure also provides a control device for a mobile terminal, including: [0021]an input module, configured to receive a first switching instruction which instructs switching the mobile terminal to a security mode; and [0022]a control module, configured to perform control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0023]Preferably, the control module may be configured to disable an uplink service channel of the mobile terminal so as to switch the mobile terminal to the security mode. [0024]Preferably, the device may further include: [0025]a prompting module, configured to, when the mobile terminal receives an external signal, prompt a user whether to switch the mobile terminal from the security mode to a normal mode or not. [0026]Preferably, the input module may be further configured to receive a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and [0027]the control module may be further configured to enable the uplink service channel of the mobile terminal according to the second switching instruction, so as to switch the mobile terminal to the normal mode. [0028]Preferably, the first switching instruction may carry a password, and [0029]the control module may be configured to verify the password carried by the first switching instruction according to a preset disabling password and disable the uplink service channel of the mobile terminal after the password carried by the first switching instruction passes the verification. [0030]Preferably, the second switching instruction may carry a password, and [0031]the control module may be configured to verify the password carried by the second switching instruction according to a preset enabling password and enable the uplink service channel of the mobile terminal after the password carried by the second switching instruction passes the verification. [0032]The embodiment of the disclosure further provides a mobile terminal, including the above-mentioned control device. [0033]The embodiments of the disclosure have the following beneficial effects that: [0034]in the above solution, under the security mode, the control device for the mobile terminal performs control processing on the mobile terminal to disable the mobile terminal to transmit the service data to the base station and make the mobile terminal only to receive the external signal. The signal transmission operating function of the mobile terminal is disabled, so that the information security of the mobile terminal can be effectively ensured, and the mobile terminal can be prevented from being freely controlled by a hacker or a virus for eavesdropping and stealing the privacy of an individual or secretes of a company. BRIEF DESCRIPTION OF THE DRAWINGS [0035]FIG. 1 is a flowchart of a control method for a mobile terminal according to an embodiment of the disclosure. [0036]FIG. 2 is a structural diagram of a control device for a mobile terminal according to an embodiment of the disclosure. [0037]FIG. 3 is a flowchart of a control method for a mobile terminal according to example 1 of the disclosure. [0038]FIG. 4 is a flowchart of a control method for a mobile terminal according to example 2 of the disclosure. [0039]FIG. 5 is a flowchart of a control method for a mobile terminal according to example 3 of the disclosure. DETAILED DESCRIPTION [0040]In order to make clearer the technical problem to be solved by the embodiments of the disclosure, the technical scheme and the advantages, detailed description will be given below with reference to the drawings and specific embodiments. [0041]For the problem that a hacker or a virus may steal information about an individual and a company by controlling a mobile terminal in the relevant art, the embodiments of the disclosure provide a control method and a control device for the mobile terminal as well as the mobile terminal, which can effectively ensure the information security of the mobile terminal. [0042]FIG. 1 is a flowchart of a control method for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 1, the embodiment includes that: [0043]S101: a control device for the mobile terminal receives a first switching instruction which instructs switching the mobile terminal to a security mode; and [0044]S102: the control device for the mobile terminal performs control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0045]The first switching instruction may be an instruction input by a user of the mobile terminal, or may be an instruction transmitted to the control device for the mobile terminal by external equipment. [0046]The mobile terminal may be disabled to transmit the service data to the base station through many methods: before transmitting the service data to the base station, the mobile terminal is required to perform a series of processing, such as coding and mapping, on the service data, and a certain step can be interrupted to disable the mobile terminal to transmit the service data to the base station. [0047]Preferably, the control device for the mobile terminal may disable the mobile terminal to transmit the service data to the base station by disabling an uplink service channel of the mobile terminal. [0048]Preferably, the control device for the mobile terminal may prompt, when the mobile terminal receives an external signal, the user whether to switch the mobile terminal from the security mode to a normal mode or not. [0049]Preferably, after prompting the user, the control device for the mobile terminal receives a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and the control device for the mobile terminal enables the uplink service channel of the mobile terminal according to the second switching instruction, that is switching the mobile terminal to the normal mode. [0050]Preferably, the first switching instruction may carry a password, and the control device for the mobile terminal verifies the password carried by the first switching instruction according to a preset disabling password and disables the uplink service channel of the mobile terminal after the verification succeeds. [0051]Preferably, the second switching instruction may carry a password, and the control device for the mobile terminal verifies the password carried by the second switching instruction according to a preset enabling password and enables the uplink service channel of the mobile terminal after the verification succeeds. [0052]According to the control method for the mobile terminal in the embodiment of the disclosure, under the security mode, the control device for the mobile terminal performs control processing on the mobile terminal to disable the mobile terminal to transmit the service data to the base station, as a result, the mobile terminal only receives the external signal. Since the signal transmission function of the mobile terminal is disabled, the information security of the mobile terminal can be effectively ensured, and the mobile terminal can be prevented from being freely controlled by the hacker or the virus for eavesdropping and stealing the privacy of the individual and the secretes of the company. [0053]FIG. 2 is a structural diagram of a control device for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 2, the embodiment includes: [0054]an input module 20, configured to receive a first switching instruction which instructs switching the mobile terminal to a security mode; and [0055]a control module 21, configured to perform control processing on the mobile terminal according to the first switching instruction to switch the mobile terminal to the security mode, so as to disable the mobile terminal to transmit service data to a base station. [0056]Preferably, the control module 21 is configured to disable an uplink service channel of the mobile terminal so as to switch the mobile terminal to the security mode. [0057]Preferably, the control device further includes: [0058]a prompting module, configured to prompt, when the mobile terminal receives an external signal, a user whether to switch the mobile terminal from the security mode to a normal mode or not. [0059]Preferably, the input module 20 is further configured to receive a second switching instruction, input by the user, which instructs switching the mobile terminal to the normal mode; and [0060]the control module 21 is further configured to enable the uplink service channel of the mobile terminal according to the second switching instruction so as to switch the mobile terminal to the normal mode. [0061]Preferably, the first switching instruction carries a password, and [0062]the control module 21 is configured to verify the password carried by the first switching instruction according to a preset disabling password and disable the uplink service channel of the mobile terminal after the verification succeeds. [0063]Preferably, the second switching instruction carries a password, and [0064]the control module 21 is configured to verify the password carried by the second switching instruction according to a preset enabling password and enable the uplink service channel of the mobile terminal after the verification succeeds. [0065]According to the control device for the mobile terminal in the embodiment of the disclosure, under the security mode, the control device for the mobile terminal performs control processing on the mobile terminal to disable the mobile terminal to transmit the service data to the base station, as a result, the mobile terminal only receives the external signal. Since the signal transmission function of the mobile terminal is disabled, the information security of the mobile terminal can be effectively ensured, and the mobile terminal can be prevented from being freely controlled by the hacker or the virus for eavesdropping and stealing the privacy of the individual and the secretes of the company. [0066]The embodiment of the disclosure further provides a mobile terminal, which includes the above-mentioned control device for the mobile terminal. [0067]The control method for the mobile terminal of the disclosure is further described below with reference to specific examples. EXAMPLE 1 [0068]In this example, when the user requires to protect the information security of the mobile terminal, the mobile terminal can be switched to the security mode; and when the user requires to enable the uplink service channel, the mobile terminal is switched to the normal mode. As shown in FIG. 3, the embodiment includes the following steps. [0069]Sa1: the control device in the mobile terminal receives the first switching instruction input by the user, in which the first switching instruction instructs the mobile terminal to be switched to the security mode. Specifically, the control device in the mobile terminal may determine that the user requires to switch the mobile terminal to the security mode according to a key-press operation of the user and switches the mobile terminal to the security mode. [0070]Furthermore, the control device in the mobile terminal may also prompt the user to input a password, verify the password according to a preset disabling password after the user inputs the password, and disable the uplink service channel of the mobile terminal after the password passes verification, and then the mobile terminal is switched to the security mode. If the password input by the user is inconsistent with the preset disabling password, the control device in the mobile terminal does not disable the uplink service channel of the mobile terminal, and the mobile terminal cannot be switched to the security mode. [0071]Sa2: under the security mode, on uplink channels from the mobile terminal to the base station, transmission functions such as voice transmission and data transmission on all service channels, except signalling interaction between the mobile terminal and the base station, are disabled, the mobile terminal is kept in a minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. When the user needs to make a call, reply to a short message or surf the Internet, the control device in the mobile terminal determines that the user needs to use the uplink service channel according to the key-press operation of the user, and prompts the user whether to switch the mobile terminal from the security mode to the normal mode or not. [0072]Sa3: the user inputs the second switching instruction which instructs the mobile terminal to be switched to the normal mode according to the prompting of the control device in the mobile terminal. Specifically, the control device in the mobile terminal determines that the user needs to switch the mobile terminal to the normal mode according to the key-press operation of the user, and switches the mobile terminal to the security mode. [0073]Furthermore, the control device in the mobile terminal may also prompt the user to input the password. After the user inputs the password, the control device in the mobile terminal verifies the password input by the user according to the preset enabling password, enables the uplink service channel of the mobile terminal after the password passes verification, and switches the mobile terminal to the normal mode. If the password input by the user is inconsistent with the preset enabling password, the control device in the mobile terminal does not enable the uplink service channel of the mobile terminal, and the mobile terminal cannot be switched to the normal mode. EXAMPLE 2 [0074]In this example, when the user needs to protect the information security of the mobile terminal, the mobile terminal is switched to the security mode; and when the user needs to answer an incoming call, the mobile terminal is switched to the normal mode. FIG. 4 is a flowchart of receiving an incoming call under the security mode of a mobile terminal, and as shown in FIG. 4, the embodiment includes the following steps. [0075]Sb1: the control device in the mobile terminal controls the mobile terminal to be in the security mode, under which on uplink channels from the mobile terminal to the base station, the function of transmitting voices, data and the like on all service channels, except signalling interaction between the mobile terminal and the base station, is disabled, the mobile terminal is kept in the minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. [0076]Sb2: the mobile terminal receives an incoming call, and the control device in the mobile terminal displays the incoming call to the user, and prompts the user whether to answer the incoming call or not. [0077]Sb3: upon the user selects to answer the incoming call, the control device in the mobile terminal determines whether the user selects to answer the incoming call or not according to an operation of the user. Specifically, the control device in the mobile terminal determines that the user selects to answer the incoming call according to an answer key pressing operation of the user. Thus, the mobile terminal is required to be switched from the security mode to the normal mode for the user to answer the incoming call, the control device in the mobile terminal prompts the user to input the password, compares the password input by the user with the preset enabling password, and enables the uplink service channel of the mobile terminal to switch the mobile terminal to the normal mode if the password input by the user is consistent with the preset enabling password, as a result, the user can answer the incoming call in the normal mode; and if the password input by the user is inconsistent with the preset enabling password, the user cannot answer the incoming call. EXAMPLE 3 [0078]In this example, when the user requires to protect the information security of the mobile terminal, the mobile terminal is switched to the security mode; and when the user needs to reply to a short message, the mobile terminal is switched to the normal mode. FIG. 5 is a flowchart of replying to a received short message under the security mode of a mobile terminal, and as shown in FIG. 5, the embodiment includes the following steps. [0079]Sc1: the control device in the mobile terminal controls the mobile terminal to be in the security mode, under which on uplink channels from the mobile terminal to the base station, the function of transmitting voices, data and the like on all service channels, except signalling interaction between the mobile terminal and the base station, is disabled, the mobile terminal is kept in the minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. [0080]Sc2: the mobile terminal receives the short message, and the user reads the short message. [0081]Sc3: the control device in the mobile terminal determines whether the user selects to reply to the short message or not according to an operation of the user. Specifically, the control device in the mobile terminal determines that the user selects to reply to the short message according to a short message edition key pressing operation of the user. Thus, the mobile terminal is required to be switched from the security mode to the normal mode for the user to reply to the short message. The control device in the mobile terminal prompts the user to input an enabling password, compares the password input by the user with the preset enabling password, and enables the uplink service channel of the mobile terminal to switch the mobile terminal to the normal mode if the password input by the user is consistent with the preset enabling password, and the user can reply to the short message in the normal mode; and if the password input by the user is inconsistent with the preset enabling password, the user cannot reply to the short message. EXAMPLE 4 [0082]In this example, when entering a specific area, the mobile terminal is switched to the security mode; and when the user requires to enable the uplink service channel, the mobile terminal is switched to the normal mode. The embodiment includes the following steps. [0083]Sd1: the control device in the mobile terminal receives the first switching instruction which instructs the mobile terminal to be switched to the security mode. Specifically, when the user enters a specific area such as a meeting room, related equipment in the meeting room transmits the first switching instruction to the control device in the mobile terminal, instructing the mobile terminal to be switched to the security mode. [0084]Sd2: under the security mode, on uplink channels from the mobile terminal to the base station, the function of transmitting voices, data and the like on all service channels, except signalling interaction between the mobile terminal and the base station, is disabled, the mobile terminal is kept in the minimum network access state, only the external signal receiving function is reserved, and the signal transmission function is disabled. When the user needs to make a call, reply to a short message or surf the Internet, the control device in the mobile terminal determines that the user needs to use the uplink service channel according to the key-press operation of the user, and prompts the user whether to switch the mobile terminal from the security mode to the normal mode or not. [0085]Sd3: the user inputs the second switching instruction according to the prompting of the control device in the mobile terminal to make the mobile terminal to be switched to the normal mode. Specifically, the control device in the mobile terminal determines that the user needs to switch the mobile terminal to the normal mode according to the key-press operation of the user, and switch the mobile terminal to the security mode. [0086]Furthermore, the control device in the mobile terminal may also prompt the user to input the password. After the user inputs the password, the control device in the mobile terminal verifies the password input by the user according to the preset enabling password, and enables the uplink service channel of the mobile terminal to switch the mobile terminal to the normal mode after the password passes verification. If the password input by the user is inconsistent with the preset enabling password, the control device in the mobile terminal does not enable the uplink service channel of the mobile terminal, the mobile terminal thus cannot be switched to the normal mode. [0087]According to the disclosure, the mobile terminal can be switched from the normal mode to the security mode. Under the security mode, the control device in the mobile terminal disables the uplink service channel of the mobile terminal to make the mobile terminal only to receive the external signal, and the signal transmission function of the mobile terminal is disabled, so that it is able to prevent an axe-grinding person to steal the secretes of the company or the privacy of the individual through the mobile terminal when the user of the mobile terminal is at a meeting or in another important and secrete place, and thus the information security of the mobile terminal can be effectively protected. [0088]Multiple functional parts described in the specification are called modules, so that the independence of implementation modes for the functional parts is specially emphasized. [0089]In the embodiments of the disclosure, the modules may be implemented as software for the convenient execution of various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of a computer instruction, and may for example be structured into an object, a process or a function. However, executable codes of the identified module may not be physically positioned together, but can include different instructions stored at different bits, and these instructions form the module and implement a specified purpose of the module when being logically combined together. [0090]Actually, the executable code module may be a single instruction or multiple instructions, and may even be distributed on different code segments, in different programs and across multiple pieces of memory equipment. Similarly, operating data may be identified in the module, implemented in any proper way and structured in a data structure of any proper type. The operating data may be collected as a single dataset, or may be distributed at different positions (or at different memory equipments), and may at least partially exist on a system or a network as an electronic signal only. [0091]In the case the module may be implemented by means of software, in consideration of the level of a conventional hardware process, for the module which may be implemented by the software, the skilled in the art may construct a hardware circuit to realize a corresponding function of the module without regard to the cost, in which the hardware circuit includes a conventional Very Large Scale Integrated (VLSI) circuit or a gate array and a conventional semiconductor such as a logic chip and a transistor or other discrete components. The module may also be implemented by means of programmable hardware equipment such as a field programmable gate array, a programmable array logic and programmable logic equipment. [0092]In each method embodiment of the disclosure, the sequence number of each step cannot be intended to limit the sequence of the steps, and for the skilled in the art, changes, without paying creative work, in the sequence of the steps also fall within the scope of protection of the disclosure. [0093]The above are only preferred embodiments of the disclosure, it should be noted that the skilled in the art can make various improvements and elaborations without departing from the disclosure, and these improvements and elaborations shall also fall within the scope of protection of the disclosure.(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的控制方法、控制装置及移动终端。 背景 [0002] 随着移动终端的日益普及,移动终端的功能越来越多,移动终端已经成为用户日常生活中必不可少的通讯工具。 [0003] 然而,随着无线网络的不断扩大,用户在移动终端中存储的隐私越来越多,随着科技的发展,窃听手段也越来越多,黑客或病毒可能窃取 通过控制移动终端获取有关个人和公司的信息。 例如,在商务会议中,如果携带移动终端到会场,虽然移动终端设置为静音模式,但仍然可以通过移动终端泄露会议内容,使个人隐私和泄密 公司受到极大的威胁。 概括 [0004] 本发明实施例所要解决的技术问题是提供一种移动终端的控制方法、控制装置及移动终端,能够有效保障移动终端的信息安全。 [0005] 为了解决上述技术问题,本发明实施例提供以下技术方案 [0006] 根据一个方面,提供了一种移动终端的控制方法,包括: [0007] 移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 和 [0008] 移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0009] 优选地,所述移动终端的控制装置根据第一切换指令对移动终端进行控制处理的步骤包括: [0010] 移动终端的控制装置关闭移动终端的上行业务信道。 [0011] 优选地,所述移动终端的控制装置关闭所述移动终端的上行业务信道后,所述方法还包括: [0012] 移动终端控制装置在移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到正常模式。 [0013] 优选地,所述控制装置提示用户是否将移动终端从安全模式切换到正常模式后,所述方法还包括: [0014] 移动终端控制装置接收用户输入的指示将移动终端切换到正常模式的第二切换指令; 和 [0015] 移动终端的控制装置根据第二切换指令开启移动终端的上行业务信道,以将移动终端切换到正常模式。 [0016] 优选地,第一切换指令可以携带密码,移动终端的控制装置关闭移动终端的上行业务信道包括: [0017] 移动终端的控制装置根据预设的关闭密码对第一切换指令携带的密码进行验证,验证通过后关闭移动终端的上行业务通道。 [0018] 优选地,第二切换指令可以携带密码,移动终端的控制装置开启移动终端的上行业务信道的步骤可以包括: [0019]移动终端的控制装置根据预设的开启密码对第二切换指令携带的密码进行验证,验证通过后开启移动终端的上行业务通道。 [0020] 本发明实施例还提供了一种移动终端的控制装置,包括: [0021] 输入模块,用于接收指示将移动终端切换到安全模式的第一切换指令; 和 [0022] 控制模块,用于根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0023] 优选地,控制模块可以用于关闭移动终端的上行业务通道,以将移动终端切换到安全模式。 [0024] 优选地,该装置还可以包括: [0025] 提示模块,用于当移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到普通模式。 [0026] 优选地,所述输入模块还用于接收用户输入的第二切换指令,所述第二切换指令指示将移动终端切换至正常模式。 和 [0027] 控制模块还可以用于根据第二切换指令开启移动终端的上行业务信道,以将移动终端切换到正常模式。 [0028] 优选地,第一切换指令可以携带密码,以及 [0029] 控制模块,可以用于根据预设的关闭密码验证第一切换指令携带的密码,在验证通过后关闭移动终端的上行业务通道。 [0030] 优选地,第二切换指令可以携带密码,以及 [0031] 控制模块,可以用于根据预设的开启密码对第二切换指令携带的密码进行验证,在验证通过后,开启移动终端的上行业务通道。 [0032] 本发明实施例还提供了一种移动终端,包括上述控制装置。 [0033] 本发明实施例具有以下有益效果: [0034] 上述方案中,在安全模式下,移动终端的控制装置对移动终端进行控制处理,禁止移动终端向基站发送业务数据,使移动终端只能接收外部信号。 关闭移动终端的信号传输操作功能,可以有效保障移动终端的信息安全,防止移动终端被黑客或病毒随意控制,窃听窃取用户隐私。 个人或公司的秘密。 附图的简要说明 [0035] 图1是根据本发明实施例的移动终端的控制方法的流程图。 [0036] 图2是根据本发明实施例的移动终端的控制装置的结构图。 [0037] 图3是根据本发明实施例一的移动终端的控制方法的流程图。 [0038] 图4是根据本发明实施例二的移动终端的控制方法的流程图。 [0039] 图5是根据本发明实施例三的移动终端的控制方法的流程图。 详细说明 [0040]为使本发明实施例所要解决的技术问题、技术方案及优点更加清楚,下面将结合附图及具体实施例进行详细说明。 [0041] 针对相关技术中黑客或病毒通过控制移动终端窃取个人和公司信息的问题,本发明实施例提供了一种移动终端的控制方法、控制装置及移动终端。 终端,可有效保障移动终端的信息安全。 [0042] 图1为本发明实施例提供的一种移动终端的控制方法流程图,如图1所示,该实施例包括: [0043] 小号 101 :移动终端的控制装置接收指示将移动终端切换到安全模式的第一切换指令; 和 [0044] 小号 102 :移动终端的控制装置根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0045] 第一切换指令可以是移动终端的用户输入的指令,也可以是外部设备向移动终端的控制装置发送的指令。 [0046] 可以通过多种方式使移动终端无法向基站发送业务数据:在向基站发送业务数据之前,需要移动终端对业务进行编码、映射等一系列处理。 数据,可以中断某个步骤,使移动终端不能向基站发送业务数据。 [0047] 优选地,移动终端的控制装置可以通过关闭移动终端的上行业务信道来关闭移动终端向基站发送业务数据。 [0048] 优选地,移动终端的控制装置可以在移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到正常模式。 [0049] 优选地,在提示用户后,移动终端的控制装置接收用户输入的第二切换指令,该第二切换指令指示将移动终端切换到正常模式; 移动终端的控制装置根据第二切换指令开启移动终端的上行业务信道,即将移动终端切换到正常模式。 [0050] 优选地,第一切换指令可以携带密码,移动终端的控制装置根据预设的关闭密码对第一切换指令携带的密码进行验证,验证成功后关闭移动终端的上行业务通道。 [0051] 优选地,第二切换指令可以携带密码,移动终端的控制装置根据预设的开启密码对第二切换指令携带的密码进行验证,验证成功后开启移动终端的上行业务信道。 [0052] 根据本发明实施例的移动终端的控制方法,在安全模式下,移动终端的控制装置对移动终端进行控制处理,禁止移动终端向基站发送业务数据, 结果,移动终端仅接收外部信号。 由于关闭了移动终端的信号传输功能,可以有效保障移动终端的信息安全,防止移动终端被黑客或病毒随意控制,窃听、窃取个人隐私 以及公司的秘密。 [0053] 图2为本发明实施例提供的一种移动终端的控制装置的结构图,如图2所示,该实施例包括: [0054]输入模块 20 , 用于接收指示将移动终端切换到安全模式的第一切换指令; 和 [0055] 一个控制模块 21 ,用于根据第一切换指令对移动终端进行控制处理,将移动终端切换到安全模式,以禁止移动终端向基站传输业务数据。 [0056] 优选地,控制模块 21 用于关闭移动终端的上行业务通道,使移动终端切换到安全模式。 [0057] 优选地,所述控制装置还包括: [0058] 提示模块,用于当移动终端接收到外部信号时,提示用户是否将移动终端从安全模式切换到普通模式。 [0059] 优选地,输入模块 20 还用于接收用户输入的指示将移动终端切换至正常模式的第二切换指令; 和 [0060] 控制模块 21 还用于根据第二切换指令开启移动终端的上行业务信道,以将移动终端切换到正常模式。 [0061] 优选地,第一切换指令携带密码,以及 [0062] 控制模块 21 用于根据预设的关闭密码验证第一切换指令携带的密码,验证成功后关闭移动终端的上行业务通道。 [0063] 优选地,第二切换指令携带密码,以及 [0064] 控制模块 21 用于根据预设的开启密码对第二切换指令携带的密码进行验证,验证成功后开启移动终端的上行业务通道。 [0065] 根据本发明实施例的移动终端控制装置,在安全模式下,移动终端控制装置对移动终端进行控制处理,以禁止移动终端向基站发送业务数据, 结果,移动终端仅接收外部信号。 由于关闭了移动终端的信号传输功能,可以有效保障移动终端的信息安全,防止移动终端被黑客或病毒随意控制,窃听、窃取个人隐私 以及公司的秘密。 [0066] 本发明实施例还提供了一种移动终端,包括上述的移动终端的控制装置。 [0067] 下面结合具体例子对本发明移动终端的控制方法作进一步说明。 示例 1 [0068] 本例中,当用户需要保护移动终端的信息安全时,可以将移动终端切换到安全模式; 当用户要求开启上行业务信道时,移动终端切换到正常模式。 如图3所示,该实施例包括以下步骤。 [0069] 萨 1 :移动终端中的控制装置接收用户输入的第一切换指令,第一切换指令指示移动终端切换到安全模式。 具体地,移动终端中的控制装置可以根据用户的按键操作确定用户要求将移动终端切换到安全模式,将移动终端切换到安全模式。 [0070]进一步地,移动终端中的控制装置还可以提示用户输入密码,用户输入密码后根据预设的关闭密码验证密码,验证通过后关闭移动终端的上行业务通道。 ,然后移动终端切换到安全模式。 如果用户输入的密码与预设的关闭密码不一致,则移动终端中的控制装置不关闭移动终端的上行业务通道,移动终端不能切换到安全模式。 [0071] 萨 2 :在安全模式下,在移动终端到基站的上行信道上,除移动终端与基站之间的信令交互外,所有业务信道上的语音传输和数据传输等传输功能均被关闭,移动终端 保持最小入网状态,只保留外部信号接收功能,信号发送功能关闭。 当用户需要打电话、回复短信或上网时,移动终端中的控制装置根据用户的按键操作确定用户需要使用上行业务信道,并提示 用户是否将移动终端从安全模式切换到正常模式。 [0072] 萨 3 :用户根据移动终端中的控制装置的提示,输入第二切换指令,指示移动终端切换到正常模式。 具体地,移动终端中的控制装置根据用户的按键操作确定用户需要将移动终端切换到普通模式,将移动终端切换到安全模式。 [0073] 进一步地,移动终端中的控制装置还可以提示用户输入密码。 用户输入密码后,移动终端中的控制装置根据预设的开启密码对用户输入的密码进行验证,密码验证通过后开启移动终端的上行业务通道,将移动终端切换到 正常模式。 如果用户输入的密码与预设的开启密码不一致,则移动终端中的控制装置不开启移动终端的上行业务通道,移动终端无法切换到正常模式。 例 2 [0074] 本例中,当用户需要保护移动终端的信息安全时,将移动终端切换到安全模式; 当用户需要接听来电时,将移动终端切换到正常模式。 图4为移动终端安全模式下接听来电的流程图,如图4所示,本实施例包括以下步骤。 [0075] 锑 1 :移动终端中的控制设备控制移动终端处于安全模式,在该模式下,在移动终端到基站的上行信道上,除了信令之外的所有业务信道上传输语音、数据等的功能 关闭移动终端与基站的交互,移动终端保持最小入网状态,只保留对外信号接收功能,关闭信号发送功能。 [0076] 锑 2 :移动终端收到来电,移动终端中的控制装置将来电显示给用户,并提示用户是否接听来电。 [0077] 锑 3:当用户选择接听来电时,移动终端中的控制装置根据用户的操作判断用户是否选择接听来电。 具体地,移动终端中的控制装置根据用户的接听按键操作确定用户选择接听来电。 因此,用户来电时需要将移动终端从安全模式切换到普通模式,移动终端中的控制装置提示用户输入密码,将用户输入的密码与用户输入的密码进行比对。 预设的开启密码,如果用户输入的密码与预设的开启密码一致,则开启移动终端的上行业务通道,将移动终端切换到正常模式,从而用户可以接听来电 在正常模式下; 如果用户输入的密码与预设的启用密码不一致,则用户无法接听来电。 例 3 [0078] 本例中,当用户需要保护移动终端的信息安全时,将移动终端切换到安全模式; 当用户需要回复短信时,将移动终端切换到正常模式。 图5为移动终端在安全模式下回复收到的短信的流程图,如图5所示,本实施例包括以下步骤。 [0079] 科学 1 :移动终端中的控制设备控制移动终端处于安全模式,在该模式下,在移动终端到基站的上行信道上,除了信令之外的所有业务信道上传输语音、数据等的功能 关闭移动终端与基站的交互,移动终端保持最小入网状态,只保留对外信号接收功能,关闭信号发送功能。 [0080] 科学 2 :移动终端收到短信,用户阅读短信。 [0081] 科学 3 :移动终端中的控制装置根据用户的操作判断用户是否选择回复短信。 具体地,移动终端中的控制装置根据用户的短信编辑按键操作确定用户选择回复短信。 因此,用户回复短信时需要将移动终端从安全模式切换到正常模式。 移动终端中的控制装置提示用户输入开启密码,将用户输入的密码与预设的开启密码进行比对,开启移动终端的上行业务通道,将移动终端切换到正常模式。 用户输入的密码与预设的启用密码一致,用户可以在正常模式下回复短信; 如果用户输入的密码与预设的开启密码不一致,则用户无法回复短信。 例 4 [0082] 本例中,当进入特定区域时,移动终端切换到安全模式; 当用户要求开启上行业务信道时,移动终端切换到正常模式。 该实施例包括以下步骤。 [0083] 标准差 1 :移动终端中的控制装置接收到第一切换指令,指示移动终端切换到安全模式。 具体地,当用户进入会议室等特定区域时,会议室中的相关设备向移动终端中的控制装置发送第一切换指令,指示移动终端切换到安全模式。 [0084] 标准差 2:在安全模式下,在移动终端到基站的上行信道上,除移动终端与基站之间的信令交互外,所有业务信道上传输语音、数据等功能均被关闭,移动终端 终端保持最小入网状态,只保留外部信号接收功能,信号发送功能关闭。 当用户需要打电话、回复短信或上网时,移动终端中的控制装置根据用户的按键操作确定用户需要使用上行业务信道,并提示 用户是否将移动终端从安全模式切换到正常模式。 [0085] 标准差 3 :用户根据移动终端中控制装置的提示输入第二切换指令,使移动终端切换到正常模式。 具体地,移动终端中的控制装置根据用户的按键操作确定用户需要将移动终端切换到普通模式,将移动终端切换到安全模式。 [0086] 进一步地,移动终端中的控制装置还可以提示用户输入密码。 用户输入密码后,移动终端中的控制装置根据预设的开启密码对用户输入的密码进行验证,密码后开启移动终端的上行业务通道,将移动终端切换到正常模式。 通过验证。 如果用户输入的密码与预设的开启密码不一致,则移动终端中的控制装置不开启移动终端的上行业务通道,从而使移动终端无法切换到正常模式。 [0087] 根据本发明,移动终端可以从正常模式切换到安全模式。 在安全模式下,移动终端中的控制装置关闭移动终端的上行业务通道,使移动终端只能接收外部信号,关闭移动终端的信号传输功能,使其能够 当移动终端用户在开会或其他重要隐秘场所时,防止斧磨人通过移动终端窃取公司机密或个人隐私,从而保障公司的信息安全。 移动终端可以得到有效的保护。 [0088] 将规范中描述的多个功能部分称为模块,特别强调功能部分实现方式的独立性。 [0089] 在本发明实施例中,模块可以实现为软件形式,以方便各类处理器的执行。 例如,识别的可执行代码模块可以包括计算机指令的一个或多个物理或逻辑块,并且可以例如被构造成对象、过程或函数。 但是,识别出的模块的可执行代码在物理上不一定是放在一起的,而是可以包括存储在不同位的不同指令,这些指令在逻辑上组合在一起时形成模块并实现模块的特定目的。 [0090] 实际上,可执行代码模块可以是单条指令,也可以是多条指令,甚至可以分布在不同的代码段上,分布在不同的程序中,分布在多个存储设备上。 类似地,操作数据可以在模块中被识别,以任何适当的方式实现并且被构造成任何适当类型的数据结构。 运行数据可以作为单个数据集收集,也可以分布在不同的位置(或不同的存储设备),并且可以至少部分地仅作为电子信号存在于系统或网络上。 [0091]在该模块可以通过软件实现的情况下,考虑到传统硬件工艺的水平,对于可以通过软件实现的模块,本领域技术人员可以构造硬件电路来实现相应的功能 模块的设计不考虑成本,其中硬件电路包括常规的超大规模集成电路(VLSI)电路或门阵列,以及常规的半导体,例如逻辑芯片和晶体管或其他分立元件。 该模块还可以通过现场可编程门阵列、可编程阵列逻辑、可编程逻辑设备等可编程硬件设备实现。 [0092] 在本发明各方法实施例中,各步骤的序号不能用来限定步骤的先后顺序,对于本领域的技术人员而言,在没有做出创造性劳动的情况下,对步骤顺序的改动也属于本发明的范围。 公开的保护范围。 [0093] 以上所述仅为本发明的优选实施例而已,应当知晓,本领域的技术人员在不脱离本发明的前提下,还可以做出各种改进和阐述,这些改进和阐述也应属于本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:26.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103379484A(String), CN103379484B(String), EP2840822A1(String), EP2840822A4(String), EP2840822B1(String), MX2014012656A(String), MX337095B(String), US20150067795A1(String), WO2013155790A1(String), WO2013155790A9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103379484A(String), CN103379484B(String), EP2840822A1(String), EP2840822A4(String), EP2840822B1(String), MX2014012656A(String), MX337095B(String), US20150067795A1(String), WO2013155790A1(String), WO2013155790A9(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103379484A(String), CN103379484B(String), EP2840822A1(String), EP2840822A4(String), EP2840822B1(String), MX2014012656A(String), MX337095B(String), US20150067795A1(String), WO2013155790A1(String), WO2013155790A9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), CN103379484A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.157 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270782(Integer), CN103379484B(String), 1047173(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), EP2840822A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), EP2840822A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), EP2840822B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), MX2014012656A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), MX337095B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.369 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.370 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.370 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), US20150067795A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), WO2013155790A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270782(Integer), WO2013155790A9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN103379484B(String), CN103379484B(String), 1503936000(Integer), 270782(Integer), 185066(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LIU, JIANTAO(String), 中兴通讯股份有限公司(String), LIU JIANTAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185932(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185932(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIU, JIANTAO(String), LIU JIANTAO(String), 0(Integer), 1681976007(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185932(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75821(Integer), 2(Integer), 185932(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75821(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.817 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:27.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185932(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9078133B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method, system and mobile terminal for configuring and applying locking strategy of mobile terminal(String), 移动终端锁定策略的配置和应用方法、系统及移动终端(String), US9078133B2(String), The disclosure provides a method for configuring a locking strategy of a mobile terminal, comprising: setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal and transmitting the relevant information to the mobile terminal, when the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal; or, inputting, at the mobile terminal, relevant information of a locking strategy which needs to be executed, and storing the inputted relevant information of the locking strategy which needs to be executed. The disclosure further provides a method for applying a locking strategy of a mobile terminal as well as a system and a terminal mobile for configuring a locking strategy of a mobile terminal. According to the technical solutions of the disclosure, the locking strategy of the mobile terminal can be conveniently and flexibly configured.(String), 本发明提供一种移动终端锁定策略的配置方法,包括:在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并将该相关信息发送给移动终端。 ,当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息; 或者,在移动终端输入需要执行的锁定策略的相关信息,并存储输入的需要执行的锁定策略的相关信息。 本发明还提供了一种移动终端锁定策略的应用方法、移动终端锁定策略配置系统和终端手机。 根据本发明的技术方案,可以方便灵活地配置移动终端的锁定策略。(String), US13/880796(String), 1297267200(Integer), US9078133B2(String), 1436198400(Integer), 1436198400(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 11(Integer), CN101163309A | CN1655643A | CN1845622A | KR1020010065039A | KR1020060100086A | US20070050622A1 | US20090203356A1 | US20100255813A1 | US20120094636A1(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185933(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2e0502ea1749484384de75809081295f.png(String), 185933(Integer), 2e0502ea1749484384de75809081295f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method, system and mobile terminal for configuring and applying locking strategy of mobile terminal(String), 移动终端锁定策略的配置和应用方法、系统及移动终端(String), US9078133B2(String), The disclosure provides a method for configuring a locking strategy of a mobile terminal, comprising: setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal and transmitting the relevant information to the mobile terminal, when the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal; or, inputting, at the mobile terminal, relevant information of a locking strategy which needs to be executed, and storing the inputted relevant information of the locking strategy which needs to be executed. The disclosure further provides a method for applying a locking strategy of a mobile terminal as well as a system and a terminal mobile for configuring a locking strategy of a mobile terminal. According to the technical solutions of the disclosure, the locking strategy of the mobile terminal can be conveniently and flexibly configured.(String), 本发明提供一种移动终端锁定策略的配置方法,包括:在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并将该相关信息发送给移动终端。 ,当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息; 或者,在移动终端输入需要执行的锁定策略的相关信息,并存储输入的需要执行的锁定策略的相关信息。 本发明还提供了一种移动终端锁定策略的应用方法、移动终端锁定策略配置系统和终端手机。 根据本发明的技术方案,可以方便灵活地配置移动终端的锁定策略。(String), US13/880796(String), 1297267200(Integer), US9078133B2(String), 1436198400(Integer), 1436198400(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 11(Integer), CN101163309A | CN1655643A | CN1845622A | KR1020010065039A | KR1020060100086A | US20070050622A1 | US20090203356A1 | US20100255813A1 | US20120094636A1(String), \20230420\2e0502ea1749484384de75809081295f.png(String), 11(Integer), 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.731 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.731 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 1. A method for configuring a locking strategy of a mobile terminal, comprising:setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal;generating an Attention (AT) command according to the relevant information of the locking strategy which needs to be executed by the mobile terminal;transmitting the AT command to the mobile terminal, wherein the AT command comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal; andwhen the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal.(String), 1.根据权利要求2所述的方法,其中存储需要由移动终端执行的锁定策略的相关信息包括:移动终端解析AT指令获取移动终端的锁定策略的相关信息,将相关信息写入固定区域中。移动终端的FLASH并将存储结果发送给锁定策略设置终端;锁定策略设置终端根据存储结果提示锁定策略是否更新成功。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 2. The method according to claim 1, further comprising: when the mobile terminal determines that the mobile terminal is currently locked, prompting to reconfigure a locking strategy via the locking strategy setting terminal.(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 3. The method according to claim 1, wherein storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal parsing the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writing the relevant information in a fixed region of a FLASH of the mobile terminal and transmitting a storage result to the locking strategy setting terminal; the locking strategy setting terminal prompting whether or not the locking strategy is updated successfully according to the storage result.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 4. A method for configuring a locking strategy of a mobile terminal, comprising:inputting, at a mobile terminal, relevant information of a locking strategy which needs to be executed; anda command processing program installed in the mobile terminal in advance parsing the instruction that is received and writing the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal;the FLASH transmitting a storage result to the command processing program of the mobile terminal;the command processing program prompting whether or not the locking strategy is updated successfully according to the storage result.(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 5. The method according to claim 4, wherein inputting, at the mobile terminal, the relevant information the locking strategy which needs to be executed comprises:inputting, in a command receiving program installed in the mobile terminal in advance, the relevant information of the locking strategy which needs to be executed by the mobile terminal;the command receiving program generating an instruction according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmitting the instruction to the command processing program installed in the mobile terminal in advance, wherein the instruction comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 6. A method for applying a locking strategy of a mobile terminal, comprising:obtaining relevant information of a locking strategy which needs to be executed by a mobile terminal, when determining that an ID of a scheme in the relevant information indicates that the locking strategy has been configured, locking the mobile terminal according to the locking strategy corresponding to the relevant information;wherein obtaining the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: during a power-on process of the mobile terminal, a power-on module of the mobile terminal reading the relevant information of the locking strategy which needs to be executed by the mobile terminal, wherein the relevant information of the locking strategy which needs to be executed by the mobile terminal is stored in a fixed region of a FLASH of the mobile terminal;locking the mobile terminal according to the locking strategy corresponding to the relevant information comprises: the power-on module of the mobile terminal finding, in the mobile terminal, the locking strategy corresponding to the relevant information according to the relevant information that is obtained and executing the locking strategy to lock the mobile terminal.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 7. The method according to claim 6, further comprising:when determining that the ID of the scheme in the relevant information indicates that the locking strategy has not been configured, performing a normal power-on process.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 8. A system for configuring a locking strategy of a mobile terminal, wherein the system comprises: a locking strategy setting terminal and a mobile terminal, whereinthe locking strategy setting terminal is configured to set relevant information of a locking strategy which needs to be executed by the mobile terminal, generate an Attention (AT) command according to the relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmit the AT command to the mobile terminal, wherein the AT command comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal;the mobile terminal is configured to, when the mobile terminal determines that the mobile terminal is currently unlocked, store the relevant information of the locking strategy which needs to be executed by the mobile terminal.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 9. The system according to claim 8, whereinthe locking strategy setting terminal is further configured to, when the mobile terminal determines that the mobile terminal is currently locked, prompt to reconfigure a locking strategy via the locking strategy setting terminal.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 10. A mobile terminal for implementing configuration of a locking strategy of a mobile terminal, wherein the mobile terminal comprises: a command receiving program module and a command processing program module, whereinthe command receiving program module is configured for input of relevant information of a locking strategy which needs to be executed;the command processing program module is configured to parse the instruction that is received and writing the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal, receive a storage result from the FLASH, and prompt whether or not the locking strategy is updated successfully according to the storage result.(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185933(Integer), 11. The method according to claim 2, wherein storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal parsing the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writing the relevant information in a fixed region of a FLASH of the mobile terminal and transmitting a storage result to the locking strategy setting terminal; the locking strategy setting terminal prompting whether or not the locking strategy is updated successfully according to the storage result.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.971 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.971 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:28.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185933(Integer), TECHNICAL FIELD [0001]The disclosure relates to a mobile terminal locking technology, and more particularly, to a method, a system and a mobile terminal for configuring and applying a locking strategy of a mobile terminal. BACKGROUND [0002]Currently, more and more mobile terminals are being applied broadly and mobile terminal products can be customized by mobile communication operators according to their requirements. A mobile communication operator may require locking a network, a card or a mobile terminal etc. when customizing a mobile terminal product. Locking the mobile terminal is a special requirement for the mobile terminal and the customized mobile terminal can only use a specific mobile network, or a specific Subscriber Identity Module (SIM) card/Universal Subscriber Identity Module (USIM) card. Locking the card is a special requirement for the card, after the card is locked, it is required that the card can be only used on a certain mobile terminal and cannot be used on other mobile terminals. Locking a network, a card and a mobile terminal can effectively solve problems of secret change of a network by a user, unauthorized distribution of goods and loss of customers etc. [0003]In related technologies, in order to lock a network or a card for the mobile terminal and lock the mobile terminal, a locking strategy is usually written in a mobile terminal when the mobile terminal is researched and developed. Therefore, the locking strategy is fixed and cannot be modified even by a mobile communication operator. With the development of mobile terminal technologies and continuous growth of services of mobile communication operators, the number of users is growing, along with increasing demands of the mobile communication operators. How to increase research and development efficiency, production efficiency and the configuration flexibility for customers to the greatest extent is a problem to be solved. SUMMARY [0004]In view of the above, the disclosure provides a method, a system and a mobile terminal for configuring and applying a locking strategy of a mobile terminal, so that the locking strategy of the mobile terminal can be conveniently and flexibly configured. [0005]The disclosure provides the following technical solution. [0006]The disclosure provides a method for configuring a locking strategy of a mobile terminal, comprising: [0007]setting, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by a mobile terminal and transmitting the relevant information to the mobile terminal; and [0008]when the mobile terminal determines that the mobile terminal is currently unlocked, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0009]In the method above, the method further comprises: when the mobile terminal determines that the mobile terminal is currently locked, prompting to operate over again via the locking strategy setting terminal. [0010]In the method above, setting, at the locking strategy setting terminal, the relevant information of the locking strategy which needs to be executed by the mobile terminal and transmitting the relevant information to the mobile terminal comprises: [0011]inputting, at the locking strategy setting terminal, the relevant information of the locking strategy which needs to be executed by the mobile terminal, generating an Attention (AT) command according to the relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmitting the AT command to the mobile terminal, wherein the AT command comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0012]In the method above, storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal parsing the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writing the relevant information in a fixed region of a FLASH of the mobile terminal and transmitting a storage result to the locking strategy setting terminal; the locking strategy setting terminal prompting whether or not the locking strategy is updated successfully according to the storage result. [0013]The disclosure also provides a method for configuring a locking strategy of a mobile terminal, comprising: [0014]inputting, at a mobile terminal, relevant information of a locking strategy which needs to be executed; and [0015]storing the inputted relevant information of the locking strategy which needs to be executed. [0016]In the method above, inputting, at the mobile terminal, the relevant information the locking strategy which needs to be executed comprises: inputting, in a command receiving program installed in the mobile terminal in advance, the relevant information of the locking strategy which needs to be executed by the mobile terminal; the command receiving program generating an instruction according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmitting the instruction to a command processing program installed in the mobile terminal in advance, wherein the instruction comprises the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0017]In the method above, storing the inputted relevant information of the locking strategy which needs to be executed comprises: the command processing program of the mobile terminal parsing the instruction that is received and writing the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal; the FLASH transmitting a storage result to the command processing program of the mobile terminal; the command processing program prompting whether or not the locking strategy is updated successfully according to the storage result. [0018]The disclosure also provides a method for applying a locking strategy of a mobile terminal, comprising: [0019]obtaining relevant information of a locking strategy which needs to be executed by a mobile terminal, when determining that an ID of a scheme in the relevant information indicates that the locking strategy has been configured, locking the mobile terminal according to the locking strategy corresponding to the relevant information. [0020]In the method above, the method further comprises: when determining that the ID of the scheme in the relevant information indicates that the locking strategy has not been configured, performing a normal power-on process. [0021]In the method above, obtaining the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: during a power-on process of the mobile terminal, a power-on module of the mobile terminal reading the relevant information of the locking strategy which needs to be executed by the mobile terminal, wherein the relevant information of the locking strategy which needs to be executed by the mobile terminal is stored in a fixed region of a FLASH of the mobile terminal; [0022]locking the mobile terminal according to the locking strategy corresponding to the relevant information comprises: the power-on module of the mobile terminal finding, in the mobile terminal, the locking strategy corresponding to the relevant information according to the relevant information that is obtained and executing the locking strategy to lock the mobile terminal. [0023]The disclosure also provides a system for configuring a locking strategy of a mobile terminal, comprising: a locking strategy setting terminal and a terminal, wherein the locking strategy setting terminal is configured to set relevant information of a locking strategy which needs to be executed by the mobile terminal and transmit the relevant information to the mobile terminal; [0024]the mobile terminal is configured to, when the mobile terminal determines that the mobile terminal is currently unlocked, store the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0025]In the system above, [0026]the locking strategy setting terminal is further configured to, when the mobile terminal determines that the mobile terminal is currently locked, prompt to operate over again via the locking strategy setting terminal. [0027]The disclosure also provides a mobile terminal for implementing configuration of a locking strategy of a mobile terminal, comprising: a command receiving program module and a command processing program module, wherein [0028]the command receiving program module is configured for input of relevant information of a locking strategy which needs to be executed; [0029]the command processing program module is configured to store, in a memory, the inputted relevant information of the locking strategy which needs to be executed. [0030]The method, system and mobile terminal for configuring and applying a locking strategy of a mobile terminal provided by the disclosure is able to set, at a locking strategy setting terminal, relevant information of a locking strategy which needs to be executed by the mobile terminal, transmit the relevant information to the mobile terminal, and store the relevant information of the locking strategy which needs to be executed by the mobile terminal when the mobile terminal determines that the mobile terminal is currently unlocked. By doing so, the locking strategy of the mobile terminal can be configured in batches without power-on of the mobile terminal. It is safe, simple and convenient during production of the mobile terminal and the mobile terminal can be upgraded easily, thus greatly improving the production efficiency. [0031]The disclosure can also input, at the mobile terminal, the relevant information of the locking strategy which needs to be executed and store the relevant information of the locking strategy which needs to be executed. A mobile communication operator can operate the mobile terminal directly and switch to required locking strategy at any time. [0032]To sum up, the locking strategy of the mobile terminal can be configured flexibly so that the mobile communication operator is able to manage sales and maintenance of the mobile terminal flexibly without modifying the locking strategy by the manufacturer of the mobile terminal, thus effectively lowering research, development and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS [0033]FIG. 1 is a flowchart illustrating a first method for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; [0034]FIG. 2 is a schematic diagram illustrating a graphical user interface of a command transmission program in accordance with an embodiment of the disclosure; [0035]FIG. 3 is a flowchart illustrating a second method for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; [0036]FIG. 4 is a flowchart illustrating a method for realizing application of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; [0037]FIG. 5 is a structural diagram illustrating a system for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure; and [0038]FIG. 6 is a structural diagram illustrating a mobile terminal for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS [0039]When a mobile communication operator needs to configure or update a locking strategy of a mobile terminal, two methods for configuring a locking strategy of a mobile terminal in accordance with embodiment of the disclosure can be adopted. The basic principle of the embodiments of the disclosure is that: relevant information of a locking strategy which needs to be executed by a mobile terminal is set at a locking strategy setting terminal and transmitted to the mobile terminal, when the mobile terminal determines that the mobile terminal is currently unlocked, the relevant information of the locking strategy which needs to be executed by the mobile terminal is stored; or, the relevant information of the locking strategy which needs to be executed is inputted at the mobile terminal, and the inputted relevant information of the locking strategy which needs to be executed is stored. [0040]The disclosure is further described below in details according to the accompanying drawings and the embodiments. [0041]A method for configuring a locking strategy of a mobile terminal provided by an embodiment of the disclosure is as shown in FIG. 1 and comprises the following steps. [0042]Step 101: Relevant information of a locking strategy which needs to be executed by a mobile terminal is set at a locking strategy setting terminal and transmitted to the mobile terminal. [0043]More specifically, a command transmission program of the mobile terminal is installed at the locking strategy setting terminal in advance and a graphical user interface of a command transmission program is entered after the installation is completed, wherein the locking strategy setting terminal may be a computer, e.g. a Personal Computer (PC). FIG. 2 is a schematic diagram illustrating a graphical user interface of a command transmission program in accordance with the embodiment of the disclosure. As shown in FIG. 2, the relevant information, i.e. a province and a scheme of the mobile terminal, of the locking strategy which needs to be executed by the mobile terminal is inputted in the graphical user interface of the command transmission program. The province may be expressed by a 2-byte ID which corresponds to a province ID in an Integrate Circuit Card Identity (ICCID) of a SIM/USIM card of the mobile terminal. The scheme is the locking strategy which needs to be executed by the mobile terminal and expressed by a 2-byte ID. Different IDs represent different schemes, therefore the relevant information which needs to be executed by the mobile terminal is actually a 4-byte code. The command transmission program of the locking strategy setting terminal generates an AT command comprising the relevant information according to the relevant information of the locking strategy which needs to be executed by the mobile terminal and transmits the AT command to the mobile terminal via a communication link between the locking strategy setting terminal and the mobile terminal, wherein the communication link may be a physical link such as a Universal Serial Bus (USB) and a Bluetooth. If the USB is applied as the communication link, the mobile terminal does not need to be powered on when the locking strategy of the mobile terminal is configured, and the AT command can be delivered to the mobile terminal by the locking strategy setting terminal. [0044]Step 102: The mobile terminal determines whether or not the mobile terminal is locked currently, if the mobile terminal is unlocked currently, Step 103 is executed, and if the mobile terminal is locked currently, Step 104 is executed. [0045]More specifically, the mobile terminal is in an idle state which may be a power-off state or a state indicating that the mobile terminal is being powered on. After receiving the AT command transmitted by the locking strategy setting terminal, a command processing program of the mobile terminal reads a flag bit of a fixed region of a FLASH in the mobile terminal, determines that the mobile terminal is a mobile terminal with a card lock and a mobile terminal lock according to the flag bit and triggers a card lock and mobile terminal lock verification program of the mobile terminal. The network lock and mobile terminal lock verification program determines whether or not the fixed region of the FLASH in the mobile terminal is null, if so, it represents that the locking strategy has not been configured in the mobile terminal, i.e. the mobile terminal is not locked and Step 103 is performed; otherwise, the locking strategy has been configured in the mobile terminal, i.e. the mobile terminal has been locked, and Step 104 is performed. [0046]Step 103: The mobile terminal stores the received relevant information of the locking strategy which needs to be executed and terminates the current processing flow. [0047]More specifically, the command processing program installed in the mobile terminal in advance parses the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writes the IDs of the province and the locking strategy which needs to be executed by the mobile terminal in the relevant information into the fixed region of the FLASH of the mobile terminal via an interface function. The mobile terminal transmits a storage result to the locking strategy setting terminal via a communication link, wherein the storage result comprises: successful storage and storage failure. The locking strategy setting terminal performs prompting via a display according to the storage result, specifically, the locking strategy setting terminal prompts that the locking strategy is updated successfully if the storage is successful, and prompts that the updating of the locking strategy fails if the storage fails. [0048]Step 104: The mobile terminal prompts to operate over again via the locking strategy setting terminal. [0049]More specifically, when the mobile terminal determines that the mobile terminal is locked, a result that the configuration of the locking strategy fails is transmitted to the locking strategy setting terminal via a communication link, and the locking strategy setting terminal which receives the result prompts that operations need to be performed over again, i.e. the mobile terminal needs to be unlocked first before the locking strategy is configured over again. [0050]FIG. 3 is a flowchart illustrating the second method for realizing configuration of a locking strategy of a mobile terminal in accordance with an embodiment of the disclosure. As shown in FIG. 3, the method comprises the following steps. [0051]Step 301: Relevant information of a locking strategy which needs to be executed is inputted at a mobile terminal. [0052]More specifically, a command receiving program is installed at the mobile terminal in advance and a graphical user interface of the command receiving program is entered after the installation is completed. The relevant information of the locking strategy which needs to be executed by the mobile terminal is inputted in the graphical user interface. The relevant information comprises a province and a scheme of the mobile terminal, e.g. *983*ZZXX, wherein ZZ is an ID of the scheme which may be any combinations of numbers, e.g. 58 or 59 etc. and is configured to express different schemes; XX expresses an ID of the province and ZZ may be the same for the same province. The command receiving program of the mobile terminal generates an instruction comprising the relevant information according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal, and transmits the instruction to a command processing program installed in the mobile terminal in advance. [0053]Step S302: The inputted relevant information of the locking strategy which needs to be executed is stored. [0054]More specifically, the command processing program of the mobile terminal parses the received instruction to obtain the relevant information of the locking strategy which needs to be executed by the mobile terminal, and writes the ID of the province and the locking strategy which needs to be executed by the mobile terminal in the relevant information into a fixed region of a FLASH of the mobile terminal via an interface function, for example, if the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal is *983*5810, then 5810 is written in the fixed region of the FLASH of the mobile terminal. The FLASH transmits a storage result to a command processing program, wherein the storage result comprises: successful storage and storage failure. The command processing program of the mobile terminal performs prompting via a screen according to the storage result, specifically, the command processing program prompts that the locking strategy is updated successfully if the storage is successful, and prompts that the updating of the locking strategy fails if the storage fails. [0055]Based on the method for configuring a locking strategy of a mobile terminal above, an embodiment of the disclosure also provides a method for applying a locking strategy of a mobile terminal. As shown in FIG. 4, the method comprises the following steps. [0056]Step 401: Relevant information of a locking strategy which needs to be executed by a mobile terminal is obtained. [0057]More specifically, during a power-on process of the mobile terminal, a power-on module of the mobile terminal utilizes an interface function to read the relevant information, i.e. a 4-byte code, of the locking strategy which needs to be executed, wherein the relevant information is stored in a fixed region of a FLASH of the mobile terminal. [0058]Step 402: It is determined whether or not an ID of a scheme in the relevant information is 0, if it is not 0, Step 403 is performed, and if it is 0, Step 404 is performed. [0059]More specifically, according to the read relevant information, the power-on module of the mobile terminal determines whether the last two bytes in the relevant information, i.e. the ID of the scheme, is 0, if it is not 0, it represents that the locking strategy of the mobile terminal has been configured and Step 403 is performed; and if it is 0, the locking strategy of the mobile terminal has not been configured and Step 404 is performed. [0060]Step 403: The mobile terminal is locked according to the locking strategy corresponding to the relevant information, and the current processing flow is ended. [0061]More specifically, since the locking strategy of the mobile terminal has been configured, the power-on module of the mobile terminal finds, in the mobile terminal, the locking strategy corresponding to the relevant information according to the obtained relevant information and executes the locking strategy to lock the mobile terminal. Executing the locking strategy to lock the mobile terminal belongs to an existing technology, which will not be repeated here. The locking strategy in the mobile terminal is pre-stored, in a form of a code, in a program of the mobile terminal. There may be one or more locking strategies in the embodiment of the disclosure and switching among different locking strategies of the mobile terminal can be realized using the two methods above. [0062]Step 404: A normal power-on process is performed. [0063]More specifically, since the locking strategy of the mobile terminal is not configured in the mobile terminal, the mobile terminal can be powered on normally. The normal power-on process of the mobile terminal is performed, which belongs to an existing technology and will not be repeated here. [0064]To realize the methods above, an embodiment of the disclosure also provides a system for configuring a locking strategy of a mobile terminal. As shown in FIG. 5, the system comprises: a locking strategy setting terminal 51 and a terminal 52, wherein the locking strategy setting terminal 51 is configured to set relevant information of a locking strategy which needs to be executed by a mobile terminal and transmit the relevant information to the mobile terminal 52; and [0065]the mobile terminal 52 is configured to, when the mobile terminal determines that the mobile terminal is currently unlocked, store the relevant information of the locking strategy which needs to be executed by the mobile terminal. [0066]The locking strategy setting terminal 51 is further configured to, when the mobile terminal 52 determines that the mobile terminal 52 is currently locked, prompt to operate over again. [0067]Setting, at the locking strategy setting terminal 51, the relevant information of the locking strategy which needs to be executed by the mobile terminal and transmitting the relevant information to the mobile terminal 52 comprises: the relevant information of the locking strategy which needs to be executed by the mobile terminal is inputted at the locking strategy setting terminal 51, and according to the relevant information of the locking strategy which needs to be executed by the mobile terminal, an AT command comprising the relevant information is generated and transmitted to the mobile terminal 52. [0068]Storing the relevant information of the locking strategy which needs to be executed by the mobile terminal comprises: the mobile terminal 52 parses the AT command to obtain the relevant information of the locking strategy of the mobile terminal, writes the relevant information in a fixed region of a FLASH of the mobile terminal 52 and transmits a storage result to the locking strategy setting terminal 51; the locking strategy setting terminal 51 prompts whether or not the locking strategy is updated successfully according to the storage result. [0069]An embodiment of the disclosure also provides a mobile terminal for implementing configuration of a locking strategy of a mobile terminal. As shown in FIG. 6, the mobile terminal comprises: a command receiving program module 61 and a command processing program module 62, wherein [0070]the command receiving program module 61 is configured for input of relevant information of a locking strategy which needs to be executed; [0071]the command processing program module 62 is configured to store, in a memory, the relevant information of the locking strategy which needs to be executed. [0072]Inputting the relevant information of the locking strategy which needs to be executed comprises: the relevant information of the locking strategy which needs to be executed by the mobile terminal is inputted in the command receiving program module 61 in the mobile terminal; the command receiving program module 61 generates an instruction comprising the relevant information according to the inputted relevant information of the locking strategy which needs to be executed by the mobile terminal and transmits the instruction to the command processing program module 62 installed in the mobile terminal in advance. [0073]Storing the inputted relevant information of the locking strategy which needs to be executed comprises: the command processing program module 62 of the mobile terminal parses the received instruction and writes the obtained relevant information of the locking strategy which needs to be executed by the mobile terminal in a fixed region of a FLASH of the mobile terminal; the FLASH transmits a storage result to the command processing program module 61 of the mobile terminal; the command processing program module 62 prompts whether or not the locking strategy is updated successfully according to the storage result. [0074]The above are only preferred embodiments of the disclosure and should not be used for limiting the scope of protection of the disclosure. Any modifications, equivalent replacements, improvements and the like within the principle of the disclosure shall fall within the scope of protection of the disclosure.(String), 技术领域 [0001] 本发明涉及移动终端锁定技术,尤其涉及一种移动终端锁定策略配置及应用的方法、系统及移动终端。 背景 [0002] 目前,越来越多的移动终端得到广泛应用,移动通信运营商可以根据自己的需求定制移动终端产品。 移动通信运营商在定制移动终端产品时,可能会要求锁网、锁卡或移动终端等。 锁定移动终端是对移动终端的特殊要求,定制的移动终端只能使用特定的移动网络,或者特定的SIM卡/USIM卡。 锁卡是对卡的一种特殊要求,卡锁后要求卡只能在某个移动终端上使用,不能在其他移动终端上使用。 锁网、锁卡、锁移动终端,可有效解决用户私自更改网络、擅自配送商品、客户流失等问题。 [0003] 在相关技术中,为了给移动终端锁网或锁卡,从而对移动终端进行锁定,通常在研发移动终端时,会在移动终端中编写锁定策略。 因此,锁定策略是固定的,即使是移动通信运营商也不能修改。 随着移动终端技术的发展和移动通信运营商业务的不断增长,用户数量不断增长,对移动通信运营商的需求也越来越大。 如何最大程度地提高研发效率、生产效率和为客户配置的灵活性,是需要解决的问题。 概括 [0004] 有鉴于此,本发明提供了一种移动终端锁定策略的配置及应用方法、系统及移动终端,能够方便灵活地配置移动终端的锁定策略。 [0005] 本发明提供以下技术方案。 [0006] 本发明提供了一种移动终端的锁定策略配置方法,包括: [0007] 在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并将相关信息发送给移动终端; 和 [0008] 当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息。 [0009] 上述方法中,所述方法还包括: 当移动终端确定移动终端当前处于锁定状态时,通过锁定策略设置终端提示重新操作。 [0010] 上述方法中,在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息并发送给移动终端,包括: [0011] 在锁定策略设置端输入移动端需要执行的锁定策略的相关信息,根据移动端需要执行的锁定策略的相关信息生成AT命令。 终端,向移动终端发送AT指令,AT指令中包含移动终端需要执行的锁定策略的相关信息。 [0012]上述方法中,存储移动终端需要执行的锁定策略的相关信息包括:移动终端解析AT命令获取移动终端的锁定策略的相关信息,将相关信息写入 移动终端FLASH的固定区域,并将存储结果发送给锁定策略设置终端; 锁定策略设置终端根据存储结果提示锁定策略是否更新成功。 [0013] 本发明还提供了一种移动终端的锁定策略配置方法,包括: [0014] 在移动终端输入需要执行的锁定策略的相关信息; 和 [0015] 存储输入的需要执行的锁定策略的相关信息。 [0016] 上述方法中,在移动终端输入需要执行的锁定策略的相关信息包括: 在预先安装在移动终端的命令接收程序中输入需要执行的锁定策略的相关信息。 由移动终端执行; 命令接收程序根据输入的移动终端需要执行的锁定策略的相关信息生成指令,并将该指令发送给预先安装在移动终端中的命令处理程序,其中,该指令包括相关的 移动终端需要执行的锁定策略信息。 [0017] 上述方法中,存储输入的需要执行的锁定策略的相关信息包括:移动终端的命令处理程序解析接收到的指令并写入获取的需要执行的锁定策略的相关信息。 移动终端在移动终端FLASH的固定区域; FLASH将存储结果传输给移动终端的命令处理程序; 命令处理程序根据存储结果提示锁定策略是否更新成功。 [0018] 本发明还提供了一种应用移动终端锁定策略的方法,包括: [0019] 获取移动终端需要执行的锁定策略的相关信息,当确定相关信息中的方案ID表示已经配置了锁定策略时,根据该锁定策略对应的锁定策略对移动终端进行锁定 相关信息。 [0020] 上述方法中,所述方法还包括: 当确定相关信息中方案的ID表示未配置锁定策略时,执行正常开机流程。 [0021] 上述方法中,获取移动终端需要执行的锁定策略的相关信息包括:在移动终端开机过程中,移动终端的开机模块读取锁定策略的相关信息。 需要由移动终端执行的锁定策略,其中需要由移动终端执行的锁定策略的相关信息存储在移动终端的FLASH的固定区域中; [0022] 根据相关信息对应的锁定策略锁定移动终端包括: 移动终端开机模块根据获取的相关信息在移动终端中找到相关信息对应的锁定策略并执行 锁定移动端的锁定策略。 [0023] 本发明还提供了一种移动终端的锁定策略配置系统,包括:锁定策略设置终端和终端,锁定策略设置终端用于设置需要执行的锁定策略的相关信息。 移动终端,并将相关信息传输至移动终端; [0024]移动终端,用于当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息。 [0025] 在上面的系统中, [0026] 锁定策略设置端,还用于当移动终端确定移动终端当前处于锁定状态时,通过锁定策略设置端提示重新操作。 [0027] 本发明还提供了一种移动终端,用于实现移动终端锁定策略的配置,包括:命令接收程序模块和命令处理程序模块,其中, [0028] 命令接收程序模块,用于输入需要执行的锁定策略的相关信息; [0029] 命令处理程序模块,用于将输入的需要执行的锁定策略的相关信息存储在内存中。 [0030] 本发明提供的移动终端锁定策略的配置及应用方法、系统及移动终端,能够在锁定策略设置终端设置移动终端需要执行的锁定策略的相关信息, 将相关信息发送给移动终端,并存储当移动终端确定当前移动终端处于解锁状态时移动终端需要执行的锁定策略的相关信息。 这样,可以在移动终端不开机的情况下,批量配置移动终端的锁定策略。 移动终端生产过程中安全、简单、方便,移动终端升级方便,大大提高了生产效率。 [0031] 本发明还可以在移动终端输入需要执行的锁定策略的相关信息,并存储需要执行的锁定策略的相关信息。 移动通信运营商可以直接操作移动终端,随时切换到需要的锁定策略。 [0032] 综上所述,移动终端的锁定策略可以灵活配置,使得移动通信运营商无需移动终端厂商修改锁定策略,就可以灵活地管理移动终端的销售和维护,从而有效降低研发成本。 、开发和维护成本。 附图的简要说明 [0033] 图1为本发明实施例移动终端锁定策略配置的第一种实现方法流程图; [0034] 图2为根据本发明一实施例的命令传输程序的图形用户界面的示意图。 [0035] 图3为本发明实施例移动终端锁定策略配置的第二种实现方法流程图。 [0036] 图4为本发明实施例移动终端锁定策略应用的实现方法流程图。 [0037] 图5是根据本发明实施例的移动终端的锁定策略配置实现系统结构图。 和 [0038] 图6是根据本发明实施例的实现移动终端锁定策略配置的移动终端结构图。 具体实施方式 [0039]当移动通信运营商需要配置或更新移动终端的锁定策略时,可以采用本发明实施例提供的两种配置移动终端锁定策略的方法。 本发明实施例的基本原理是:当移动终端确定移动终端时,在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并发送给移动终端。 终端当前处于解锁状态,存储移动终端需要执行的锁定策略的相关信息; 或者,在移动终端输入需要执行的锁定策略的相关信息,并存储输入的需要执行的锁定策略的相关信息。 [0040] 下面结合附图及实施例对本发明作进一步详细说明。 [0041] 本发明实施例提供的一种移动终端的锁定策略配置方法如图1所示,包括以下步骤。 [0042] 步 101 :在锁定策略设置端设置移动终端需要执行的锁定策略的相关信息,并发送给移动终端。 [0043] 更具体的,所述锁定策略设置终端预先安装有移动终端的指令传输程序,安装完成后进入指令传输程序的图形化用户界面,其中所述锁定策略设置终端可以为电脑, 例如 个人计算机 (PC)。 图2为根据本发明实施例的命令传输程序的图形用户界面的示意图。 如图2所示,在命令发送程序的图形用户界面中输入移动终端需要执行的锁定策略的相关信息,即移动终端的省份和方案。 省份可以用2字节的ID表示,该ID对应移动终端的SIM/USIM卡的ICCID中的省份ID。 该方案是移动终端需要执行的锁定策略,用一个2字节的ID表示。 不同的ID代表不同的方案,因此移动终端需要执行的相关信息实际上是一个4字节的代码。 锁定策略设置终端的命令发送程序根据移动终端需要执行的锁定策略的相关信息生成包含相关信息的AT命令,并通过与移动终端之间的通信链路将AT命令发送给移动终端。 锁定策略设置终端和移动终端,其中,所述通信链路可以为通用串行总线(USB)、蓝牙等物理链路。 如果采用USB作为通信链路,则在配置移动终端的锁定策略时,移动终端无需开机,可以通过锁定策略设置终端向移动终端下发AT命令。 [0044] 步 102 :移动终端判断当前移动终端是否处于锁定状态,如果当前移动终端处于解锁状态,步骤 103 被执行,如果当前移动端处于锁定状态,步骤 104 被执行。 [0045]更具体地,移动终端处于空闲状态,空闲状态可以是关机状态或者指示移动终端正在开机的状态。 移动终端的指令处理程序接收到锁定策略设置终端发送的AT指令后,读取移动终端中FLASH固定区域的标志位,确定移动终端为卡锁移动终端 移动终端锁根据标志位触发移动终端的卡锁和移动终端锁验证程序。 网络锁和移动终端锁验证程序判断移动终端FLASH的固定区域是否为空,如果为空,则表示移动终端没有配置锁定策略,即移动终端没有 锁定和步骤 103 执行; 否则,移动端已经配置了锁定策略,即移动端已经被锁定,步骤 104 被执行。 [0046] 步 103 :移动终端存储接收到的需要执行的锁定策略的相关信息,并结束当前处理流程。 [0047] 更具体的,预先安装在移动终端中的指令处理程序解析AT指令获取移动终端锁定策略的相关信息,写入省份ID和需要移动执行的锁定策略 终端中的相关信息通过接口函数存入移动终端FLASH的固定区域。 移动终端通过通信链路向锁定策略设置终端发送存储结果,存储结果包括:存储成功和存储失败。 锁定策略设置终端根据存储结果通过显示器进行提示,具体的,锁定策略设置终端如果存储成功则提示锁定策略更新成功,如果存储失败则提示锁定策略更新失败。 失败。 [0048] 步 104 :移动端通过锁定策略设置端提示重新操作。 [0049] 更具体地,当移动终端确定移动终端被锁定时,通过通信链路向锁定策略设置终端发送锁定策略配置失败的结果,接收到该结果的锁定策略设置终端提示: 需要重新操作,即需要先解锁移动终端,再重新配置锁定策略。 [0050] 图3为本发明实施例移动终端锁定策略配置的第二种实现方法流程图。 如图3所示,该方法包括以下步骤。 [0051] 步 301 :在移动端输入需要执行的锁定策略的相关信息。 [0052] 更具体地,移动终端预先安装命令接收程序,安装完成后进入命令接收程序的图形用户界面。 在图形用户界面中输入移动终端需要执行的锁定策略的相关信息。 相关信息包括移动终端的省份和方案,例如: *983*ZZXX,其中ZZ是方案的ID,可以是数字的任意组合,例如 58或59等,用于表达不同的方案; XX表示省份的ID,同一个省份ZZ可以相同。 移动终端的命令接收程序根据输入的移动终端需要执行的锁定策略的相关信息生成包括相关信息的指令,并将该指令发送给安装在移动终端中的命令处理程序 进步。 [0053] 脚步 302 :存储输入的需要执行的锁定策略的相关信息。 [0054]更具体的,移动终端的命令处理程序解析接收到的指令,得到移动终端需要执行的锁定策略的相关信息,写入省份ID和需要执行的锁定策略 移动终端通过接口函数将相关信息中的相关信息写入移动终端FLASH的固定区域,例如输入移动终端需要执行的锁定策略的相关信息为*983*5810 ,则5810写入移动终端FLASH的固定区域。 FLASH向命令处理程序发送存储结果,存储结果包括:存储成功和存储失败。 移动终端的命令处理程序根据存储结果进行屏幕提示,具体的,如果存储成功则命令处理程序提示锁定策略更新成功,如果存储成功则提示锁定策略更新失败。 存储失败。 [0055] 基于上述移动终端锁定策略的配置方法,本发明实施例还提供了一种移动终端锁定策略的应用方法。 如图4所示,该方法包括以下步骤。 [0056] 步 401 :获取移动终端需要执行的锁定策略的相关信息。 [0057] 具体的,在移动终端开机过程中,移动终端的开机模块通过接口函数读取需要执行的锁定策略的相关信息,即4字节代码, 其中,相关信息存储在移动终端的FLASH的固定区域中。 [0058] 步 402 :判断相关信息中scheme的ID是否为0,如果不为0,则Step 403 执行,如果为0,则Step 404 被执行。 [0059] 具体的,移动终端开机模块根据读取到的相关信息,判断相关信息的最后两个字节,即方案的ID是否为0,如果不为0,则表示 已配置移动端的锁定策略,步骤 403 执行; 为0表示移动端的锁定策略没有配置,步骤 404 被执行。 [0060] 步 403 :根据相关信息对应的锁定策略锁定移动终端,结束本次处理流程。 [0061] 具体的,由于已经配置了移动终端的锁定策略,移动终端的开机模块根据获取的相关信息在移动终端中查找到相关信息对应的锁定策略,并执行锁定策略 锁定移动终端。 执行锁定策略锁定移动终端属于现有技术,在此不再赘述。 移动终端中的锁定策略以代码的形式预先存储在移动终端的程序中。 本发明实施例中的锁定策略可以有一种或多种,​​通过上述两种方法可以实现移动终端不同锁定策略之间的切换。 [0062] 步 404 :执行正常的上电过程。 [0063] 更具体的,由于移动终端中没有配置移动终端的锁定策略,所以移动终端可以正常开机。 进行移动终端的正常开机过程,属于现有技术,在此不再赘述。 [0064] 为实现上述方法,本发明实施例还提供了一种移动终端锁定策略配置系统。 如图5所示,该系统包括:锁定策略设置端 51 和一个终端 52 , 其中锁定策略设置终端 51用于设置移动终端需要执行的锁定策略的相关信息,并将相关信息发送给移动终端 52 ; 和 [0065] 移动端 52 用于当移动终端确定移动终端当前处于解锁状态时,存储移动终端需要执行的锁定策略的相关信息。 [0066] 锁定策略设置终端 51 还用于,当移动终端 52 确定移动端 52 当前被锁定,提示重新操作。 [0067] 设置,在锁定策略设置端 51 , 移动端需要执行的锁定策略的相关信息,并将相关信息发送给移动端 52 包括:在锁定策略设置端输入移动终端需要执行的锁定策略的相关信息 51 ,根据移动终端需要执行的锁定策略的相关信息,生成包含相关信息的AT命令发送给移动终端 52 . [0068] 存储移动终端需要执行的锁定策略的相关信息包括:移动终端 52 解析AT指令获取移动终端锁定策略的相关信息,将相关信息写入移动终端FLASH的固定区域 52 并将存储结果发送给锁定策略设置端 51 ; 锁定策略设置终端 51 根据存储结果提示锁定策略是否更新成功。 [0069] 本发明实施例还提供了一种移动终端,用于实现移动终端的锁定策略配置。 如图6所示,该移动终端包括:命令接收程序模块 61 和命令处理程序模块 62 , 其中 [0070] 命令接收程序模块 61 用于输入需要执行的锁定策略的相关信息; [0071] 命令处理程序模块 62 用于在内存中存储需要执行的锁定策略的相关信息。 [0072] 输入需要执行的锁定策略的相关信息包括:在命令接收程序模块中输入移动终端需要执行的锁定策略的相关信息。 61 在移动终端; 命令接收程序模块 61 根据输入的移动终端需要执行的锁定策略的相关信息,生成包括相关信息的指令,并将该指令发送给命令处理程序模块 62 提前安装在移动端。 [0073] 存储输入的需要执行的锁定策略的相关信息包括: 命令处理程序模块 62 移动终端解析接收到的指令,将获取的需要移动终端执行的锁定策略的相关信息写入移动终端FLASH的固定区域; FLASH将存储结果传送给命令处理程序模块 61 移动终端; 命令处理程序模块 62 根据存储结果提示锁定策略是否更新成功。 [0074] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的保护范围。 凡在本发明的原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101977373A(String), EP2632198A1(String), EP2632198A4(String), US20130231089A1(String), US9078133B2(String), WO2012051816A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.183 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101977373A(String), EP2632198A1(String), EP2632198A4(String), US20130231089A1(String), US9078133B2(String), WO2012051816A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101977373A(String), EP2632198A1(String), EP2632198A4(String), US20130231089A1(String), US9078133B2(String), WO2012051816A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270781(Integer), CN101977373A(String), 1047162(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270781(Integer), EP2632198A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270781(Integer), EP2632198A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270781(Integer), US20130231089A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270781(Integer), US9078133B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270781(Integer), WO2012051816A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101977373A(String), CN101977373A(String), 1297785600(Integer), 270781(Integer), 185065(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZHANG, LI(String), HAN, CHUNYUAN(String), ZHANG, QIANG(String), JI, BAOLING(String), 中兴通讯股份有限公司(String), ZHANG LI(String), HAN CHUNYUAN(String), ZHANG QIANG(String), JI BAOLING(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185933(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185933(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHANG, LI(String), ZHANG LI(String), 0(Integer), 1681976009(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HAN, CHUNYUAN(String), HAN CHUNYUAN(String), 0(Integer), 1681976009(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHANG, QIANG(String), ZHANG QIANG(String), 0(Integer), 1681976009(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: JI, BAOLING(String), JI BAOLING(String), 0(Integer), 1681976009(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185933(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75822(Integer), 2(Integer), 185933(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75823(Integer), 2(Integer), 185933(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75824(Integer), 2(Integer), 185933(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75825(Integer), 2(Integer), 185933(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75822(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:29.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.065 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.065 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185933(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Keypad battery pack, mobile terminal available for different keypad battery packs, and method of changing keypad of mobile terminal(String), 键盘电池组、可用于不同键盘电池组的移动终端、以及更换移动终端键盘的方法(String), US20080004085A1(String), A keypad battery pack, a mobile terminal available for different keypad battery packs, and a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack are provided. The mobile terminal has a keypad formed on a battery pack as well as on a front surface of the mobile terminal, thereby expanding a keypad-placement area to a rear surface of the mobile terminal. As a result, keys of the keypad are arranged on both surfaces of the mobile terminal, and thus a key arrangement space has room for an additional key, thereby enabling easy adding of a key. Further, the keypads of the mobile terminal are arranged on the rear surface and the front surface according to functions of the keypads, thereby providing a keypad structure suitable for a mobile terminal having an additional function. Further, the mobile terminal may selectively mount a plurality of battery packs having different types and arrangements of keypads.(String), 提供了一种键盘电池组、可用于不同键盘电池组的移动终端、以及通过用不同的电池组更换电池组来改变移动终端的键盘的方法。 移动终端具有形成在电池组上以及移动终端前表面上的小键盘,从而将小键盘放置区域扩展到移动终端的后表面。 结果,小键盘的按键布置在移动终端的两个表面上,因此按键布置空间具有容纳额外按键的空间,从而能够容易地添加按键。 进一步地,移动终端的小键盘根据小键盘的功能设置在后表面和前表面,从而提供适用于具有附加功能的移动终端的小键盘结构。 此外,移动终端可以选择性地安装具有不同类型和排列的键盘的多个电池组。(String), US11/770428(String), 1182960000(Integer), US20080004085A1(String), 1199289600(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 7(Integer), US20020082042A1 | US20030153349A1 | US20030181226A1 | US20030211834A1 | US20060282407A1 | US20070057851A1 | US7571384B1(String), 30(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185934(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\aab520c75cd24159aa8ce4f09eb0ba0c.png(String), 185934(Integer), aab520c75cd24159aa8ce4f09eb0ba0c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.817 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Keypad battery pack, mobile terminal available for different keypad battery packs, and method of changing keypad of mobile terminal(String), 键盘电池组、可用于不同键盘电池组的移动终端、以及更换移动终端键盘的方法(String), US20080004085A1(String), A keypad battery pack, a mobile terminal available for different keypad battery packs, and a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack are provided. The mobile terminal has a keypad formed on a battery pack as well as on a front surface of the mobile terminal, thereby expanding a keypad-placement area to a rear surface of the mobile terminal. As a result, keys of the keypad are arranged on both surfaces of the mobile terminal, and thus a key arrangement space has room for an additional key, thereby enabling easy adding of a key. Further, the keypads of the mobile terminal are arranged on the rear surface and the front surface according to functions of the keypads, thereby providing a keypad structure suitable for a mobile terminal having an additional function. Further, the mobile terminal may selectively mount a plurality of battery packs having different types and arrangements of keypads.(String), 提供了一种键盘电池组、可用于不同键盘电池组的移动终端、以及通过用不同的电池组更换电池组来改变移动终端的键盘的方法。 移动终端具有形成在电池组上以及移动终端前表面上的小键盘,从而将小键盘放置区域扩展到移动终端的后表面。 结果,小键盘的按键布置在移动终端的两个表面上,因此按键布置空间具有容纳额外按键的空间,从而能够容易地添加按键。 进一步地,移动终端的小键盘根据小键盘的功能设置在后表面和前表面,从而提供适用于具有附加功能的移动终端的小键盘结构。 此外,移动终端可以选择性地安装具有不同类型和排列的键盘的多个电池组。(String), US11/770428(String), 1182960000(Integer), US20080004085A1(String), 1199289600(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 7(Integer), US20020082042A1 | US20030153349A1 | US20030181226A1 | US20030211834A1 | US20060282407A1 | US20070057851A1 | US7571384B1(String), \20230420\aab520c75cd24159aa8ce4f09eb0ba0c.png(String), 30(Integer), 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 1. A keypad battery pack having a first surface and a second surface and including a battery therein, the keypad battery pack comprising:a keypad formed on the first surface; anda battery terminal formed on the second surface.(String), 1.键盘电池组一个有第一表面和第二表面并且在其中包括电池,键盘电池组包括:形成于第一表面上的键盘;和电池端子形成在第二表面上。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 2. The keypad battery pack of claim 1, wherein the keypad has a 3×4 key arrangement.(String), 2.如权利要求1所述的键盘电池组,其中键盘采用3×4键排列。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 3. The keypad battery pack of claim 1, wherein the keypad has a 5×4 key arrangement.(String), 3.如权利要求1所述的键盘电池组,其中键盘采用5×4键排列。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 4. The keypad battery pack of claim 1, wherein the keypad includes a search key.(String), 4.如权利要求1所述的键盘电池组,其中键盘包括一个搜索键。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 5. The keypad battery pack of claim 1, further comprising a key scan control unit electrically connected to the keypad and the battery terminal for recognizing a specific key input of the keypad.(String), 5.如权利要求1所述的键盘电池组,还包括按键扫描控制单元电性连接于键盘与电池端,用以识别键盘的特定按键输入。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 6. A mobile terminal comprising:a terminal body having a front surface and a rear surface,a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface; anda battery pack having an inner surface contacted with the rear surface of the terminal body and an outer surface facing the same direction as the rear surface of the terminal body, and having a rear keypad formed on the outer surface, wherein the battery pack is mounted on the battery mounting area of the terminal body to be electrically connected to the terminal body.(String), 6.移动端包括:具有前表面和后表面的终端主体,前显示单元形成在前表面上,后显示单元和电池安装区域形成在后表面上;和电池组,其内表面与终端主体的后表面接触,外表面与终端主体的后表面朝向相同的方向,并且具有形成在外表面上的后键盘,其中安装有电池组在终端主体的电池安装区域上以与终端主体电连接。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 7. The mobile terminal of claim 6, wherein the terminal body further comprises a front keypad formed on the front surface.(String), 7.如权利要求6所述的移动终端,其中终端机体还包括形成在前表面上的前键盘。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 8. The mobile terminal of claim 6, wherein the terminal body further comprises a charging terminal formed on the battery mounting area, the battery pack further comprises a battery terminal formed on the inner surface, and the charging terminal and the battery terminal are electrically connected to each other by contact.(String), 8.如权利要求6所述的移动终端,其中终端本体还包括形成在电池安装区上的充电端子,电池组还包括形成在内表面上的电池端子,充电端子与电池端子通过接触电连接。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 9. The mobile terminal of claim 7, wherein a type of the front keypad is different from a type of the rear keypad.(String), 9.如权利要求7所述的移动终端,其中前键盘的类型与后键盘的类型不同。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 10. The mobile terminal of claim 7, wherein at least one of the front keypad and the rear keypad has one of a 3×4 key arrangement and a 5×4 key arrangement.(String), 10.如权利要求7所述的移动终端,其中前键盘和后键盘中的至少一个具有3×4键排列和5×4键排列之一。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 11. The mobile terminal of claim 7, wherein at least one of the front keypad and the rear keypad includes a search key.(String), 11.如权利要求7所述的移动终端,其中前键盘和后键盘中的至少一个包括搜索键。(String), 1(Integer), 10(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 12. The mobile terminal of claim 7, wherein the terminal body further comprises a first key scan control unit electrically connected to the front keypad for recognizing a specific key input.(String), 12.如权利要求7所述的移动终端,其中终端机体还包括第一按键扫描控制单元,电连接到前置键盘,用于识别特定的按​​键输入。(String), 1(Integer), 11(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 13. The mobile terminal of claim 12, wherein the terminal body further comprises a second key scan control unit electrically connected to the rear keypad for recognizing a specific key input.(String), 13.如权利要求12所述的移动终端,其中终端机体还包括第二键扫描控制单元,电连接到后键盘,用于识别特定键输入。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 14. The mobile terminal of claim 12, wherein the battery pack further comprises a second key scan control unit electrically connected to the rear keypad for recognizing a specific key input.(String), 14.如权利要求12所述的移动终端,其中电池组还包括第二按键扫描控制单元,电连接至后键盘,用于识别特定按键输入。(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 15. The mobile terminal of claim 8, wherein the charging terminal and the battery terminal each have a serial communication terminal.(String), 15.如权利要求8所述的移动终端,其中充电端和电池端各有一个串行通信端。(String), 1(Integer), 14(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 16. The mobile terminal of claim 6, wherein a size of the front display unit is larger than a size of the rear display unit.(String), 16.如权利要求6所述的移动终端,其中前显示单元的尺寸大于后显示单元的尺寸。(String), 1(Integer), 15(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 17. The mobile terminal of claim 6, wherein the front display unit is formed over an entire front surface of the terminal body.(String), 17.如权利要求6所述的移动终端,其中前显示单元形成在终端机体的整个前表面上。(String), 1(Integer), 16(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 18. A mobile terminal comprising:a terminal body having a front surface and a rear surface,a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface;a first battery pack having an inner surface and an outer surface, mounted on the battery mounting area of the terminal body such that the inner surface is contacted with the rear surface of the terminal body to be electrically connected to the terminal body, and having a first keypad formed on the outer surface facing the same direction as the rear surface of the terminal body; anda second battery pack having an inner surface and an outer surface, and having a second keypad formed on the outer surface that is of a different type from a type of the first keypad.(String), 18.移动终端包括:具有前表面和后表面的终端主体,前显示单元形成在前表面上,后显示单元和电池安装区域形成在后表面上;第一电池组具有内表面和外表面,安装在终端主体的电池安装区域上,使得内表面与终端主体的后表面接触以电连接到终端主体,并且具有第一键盘形成在与终端机身后表面同向的外表面上;和第二电池组具有内表面和外表面,并且具有形成在外表面上的第二键盘,第二键盘的类型与第一键盘的类型不同。(String), 0(Integer), 17(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 19. The mobile terminal of claim 18, wherein the terminal body further comprises a front keypad formed on the front surface.(String), 19.如权利要求18所述的移动终端,其中终端机体还包括形成在前表面上的前键盘。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 20. The mobile terminal of claim 18, wherein the terminal body further comprises a charging terminal formed on the battery mounting area, and each of the first and second battery packs further comprises a battery terminal formed on the respective inner surfaces thereof to be electrically connected to the charging terminal.(String), 20.如权利要求18所述的移动终端,其中终端本体还包括形成在电池安装区上的充电端子,并且第一电池组和第二电池组中的每一个还包括形成在其各自的内表面上以电连接到充电端子的电池端子。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 21. The mobile terminal of claim 19, wherein a type of the front keypad is different from a type of the first keypad and a type of the second keypad.(String), 21.如权利要求19所述的移动终端,其中前键盘的类型不同于第一键盘的类型和第二键盘的类型。(String), 1(Integer), 20(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 22. The mobile terminal of claim 19, wherein the front keypad includes a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and another has a 5×4 key arrangement.(String), 22.如权利要求19所述的移动终端,其中正面键盘包括搜索键,第一键盘和第二键盘中的一个为3×4按键排列,另一个为5×4按键排列。(String), 1(Integer), 21(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 23. The mobile terminal of claim 18, wherein the first keypad and the second keypad each include a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and the other has a 5×4 key arrangement.(String), 23.如权利要求18所述的移动终端,其中第一键盘和第二键盘均包括搜索键,第一键盘和第二键盘中的一个为3×4的按键排列,另一个为5×4的按键排列。(String), 1(Integer), 22(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 24. The mobile terminal of claim 19, wherein the terminal body further comprises a first key scan control unit electrically connected to the front keypad for recognizing a specific key input.(String), 24.如权利要求19所述的移动终端,其中终端机体还包括第一按键扫描控制单元,电连接到前置键盘,用于识别特定的按​​键输入。(String), 1(Integer), 23(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 25. The mobile terminal of claim 24, wherein the terminal body further comprises a second key scan control unit electrically connected to the first keypad or to the second keypad for recognizing a specific key input.(String), 25.如权利要求24所述的移动终端,其中终端机体还包括电连接到第一键盘或第二键盘的第二键扫描控制单元,用于识别特定键输入。(String), 1(Integer), 24(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 26. The mobile terminal of claim 24, wherein the first battery pack further comprises a second key scan control unit electrically connected to the first keypad for recognizing a specific key input, and the second battery pack further comprises a third key scan control unit electrically connected to the second keypad for a specific key input.(String), 26.如权利要求24所述的移动终端,其中第一电池组还包括第二按键扫描控制单元,电性连接第一键盘,用于识别特定按键输入;第二电池组还包括第三按键扫描控制单元,电性连接第二键盘,用于识别特定按键输入。(String), 1(Integer), 25(Integer), 23(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 27. The mobile terminal of claim 20, wherein the charging terminal and the battery terminal each have a serial communication terminal.(String), 27.如权利要求20所述的移动终端,其中充电端和电池端各有一个串行通信端。(String), 1(Integer), 26(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 28. The mobile terminal of claim 18, wherein a size of the front display unit is larger than a size of the rear display unit.(String), 28.如权利要求18所述的移动终端,其中前显示单元的尺寸大于后显示单元的尺寸。(String), 1(Integer), 27(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 29. The mobile terminal of claim 18, wherein the front display unit is formed over an entire front surface of the terminal body.(String), 29.如权利要求18所述的移动终端,其中前显示单元形成在终端机体的整个前表面上。30、一种移动终端键盘的更换方法、移动终端有终端机体,其前表面带有前显示单元,后表面带有后显示单元和电池安装区,第一电池组安装在电池安装区上,外表面带有第一键盘,以及第二电池包装具有带第二键盘的外表面,该第二键盘的类型与第一键盘的类型不同,该方法包括:从电池安装区取出第一电池组;和在电池安装区安装第二电池组。(String), 1(Integer), 28(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:30.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185934(Integer), 30. A method for changing a keypad of a mobile terminal, the mobile terminal having a terminal body having a front surface with a front display unit and a rear surface with a rear display unit and battery mounting area, a first battery pack mounted on the battery mounting area and having an outer surface with a first keypad, and a second battery pack having an outer surface with a second keypad that is of a different type from a type of the first keypad, the method comprising:removing the first battery pack from the battery mounting area; andmounting the second battery pack on the battery mounting area.(String), 0(Integer), 29(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185934(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to a Korean Patent Application entitled “KEYPAD BATTERY PACK, MOBILE TERMINAL AVAILABLE FOR DIFFERENT KEYPAD BATTERY PACKS, AND METHOD OF CHANGING KEYPAD OF MOBILE TERMINAL” filed in the Korean Intellectual Property Office on Jun. 28, 2006 and assigned Serial No. 2006-0058861, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal, in particular, to a keypad battery pack, a mobile terminal available for different keypad battery packs, and a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack. [0004]2. Description of the Related Art [0005]Mobile terminals, for example mobile phones and Personal Digital Assistants (PDAs), have been remarkably developed and now are widely used in modern life. As use of mobile terminals becomes more common, users' demands have become more varied. Accordingly, mobile terminals have been developed to conveniently provide more functions. For example, mobile terminals are provided with various additional functions such as multimedia, wireless Internet, or digital broadcast transmitting and receiving, as well as common functions such as calling, message transmitting and receiving, or personal information management. [0006]A mobile terminal generally has a keypad as an input means for receiving a user's input. As a mobile terminal is provided with various additional functions, a new key for performing and controlling the additional functions is added to a typical keypad. However, a mobile terminal has a limited keypad-placement area, and thus it is not easy to additionally place a new key on the limited keypad-placement area. [0007]Meanwhile, various keypads are provided for different nations, manufacturers or product types. The types of keypads mainly include 3-×*4 keys of a typical telephone key arrangement and 5×4 keys of a QWERTY key arrangement of a keyboard. Generally, a key arrangement of a keypad is preset in a mobile terminal manufacturing process, and thus it is impossible to change the key arrangement thereafter. In other words, generally a keypad of a mobile terminal has a fixed key arrangement. Thus, if a user having a mobile terminal of a specific key arrangement (for example, 3×4 keys) wants to change to another key arrangement (for example, 5×4 keys), the user must replace the mobile terminal with a new mobile terminal having another key arrangement. SUMMARY OF THE INVENTION [0008]In order to solve the above problems, the present invention expands a keypad-placement area of a mobile terminal, thereby enabling easier addition of keys. [0009]The present invention further provides a keypad structure suitable for a mobile terminal having various additional functions. [0010]The present invention further provides a mobile terminal and method for alternately using keypads having different key arrangements. [0011]The present invention further provides a mobile terminal and method for replacing keypads according to purpose. [0012]The present invention further improves convenience and satisfaction of a user of a mobile terminal. [0013]Typically, a keypad is formed on a front surface of a mobile terminal, and a battery pack is formed on a rear surface of the mobile terminal. The present invention utilizes the rear surface of the mobile terminal, which has previously been used only as a battery pack mounting area, as a keypad-placement area. [0014]Therefore, the present invention provides a keypad battery pack, i.e. a battery pack having a keypad thereon. The present invention further provides a mobile terminal for alternately mounting keypad battery packs of different types. The present invention further provides a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack. [0015]A mobile terminal according to an exemplary embodiment of the present invention includes a terminal body having a front surface and a rear surface, a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface; a battery pack having an inner surface contacted with the rear surface of the terminal body and an outer surface facing the same direction as the rear surface of the terminal body, and having a rear keypad formed on the outer surface, wherein the battery pack is mounted on the battery mounting area of the terminal body to be electrically connected to the terminal body. [0016]The terminal body may further include a front keypad formed on the front surface. The terminal body may further include a charging terminal formed on the battery mounting area, and the battery pack may further include a battery terminal formed on the inner surface, wherein the charging terminal and the battery terminal are electrically connected to each other by contact. [0017]A type of the front keypad may be different from a type of the rear keypad. At least one of the front keypad and the rear keypad may have one of a 3×4 and a 5×4 key arrangement, and may include a search key. [0018]The terminal body may further include a first key scan control unit and a second key scan control unit electrically connected to the front keypad and the rear keypad, respectively, for recognizing a specific key input. Alternatively, the terminal body may further include a first key scan control unit and the battery pack further includes a second key scan control unit. [0019]The charging terminal and the battery terminal may each have a serial communication terminal. A size of the front display unit may be larger than a size of the rear display unit, and the front display unit may be formed over an entire front surface of the terminal body. [0020]A mobile terminal according to another embodiment of the present invention includes a terminal body having a front surface and a rear surface, a front display unit formed on the front surface, and a rear display unit and a battery mounting area formed on the rear surface; a first battery pack having an inner surface and an outer surface mounted on the battery mounting area of the terminal body such that the inner surface is contacted with the rear surface of the terminal body to be electrically connected to the terminal body, and having a first keypad formed on the outer surface facing the same direction as the rear surface of the terminal body; and a second battery pack having an inner surface and an outer surface, and having a second keypad formed on the outer surface that is of a different type from a type of the first keypad. [0021]The terminal body may further include a front keypad formed on the front surface. The terminal body may further include a charging terminal formed on the battery mounting area, and each of the first and second battery packs may further include a battery terminal formed on the respective inner surfaces thereof to be electrically connected to the charging terminal. [0022]A type of the front keypad may be different from a type of the first keypad and a type of the second keypad. The front keypad may include a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and the other has a 5*4 key arrangement. The first keypad and the second keypad may each include a search key, and one of the first keypad and the second keypad has a 3×4 key arrangement and the other has a 5×4 key arrangement. [0023]The terminal body may further include a first key scan control unit electrically connected to the front keypad for recognizing a specific key input. The terminal body may further include a second key scan control unit electrically connected to the first keypad or to the second keypad for recognizing a specific key input. Alternatively, the first battery pack may further include a second key scan control unit electrically connected to the first keypad for recognizing a specific key input, and the second battery pack further includes a third key scan control unit electrically connected to the second keypad for recognizing a specific key input. [0024]The charging terminal and the battery terminal may each have a serial communication terminal. A size of the front display unit may be larger than a size of the rear display unit, and the front display unit may be formed over the entire front surface of the terminal body. [0025]According to another exemplary embodiment of the present invention, a method for changing a keypad of a mobile terminal having a terminal body having a front surface with a front display unit and a rear surface with a rear display unit and battery mounting area, a first battery pack mounted on the battery mounting area and having an outer surface with a first keypad, and a second battery pack having an outer surface with a second keypad that is of a different type from a type of the first keypad, includes removing the first battery pack from the battery mounting area; and mounting the second battery pack on the battery mounting area. BRIEF DESCRIPTION OF THE DRAWINGS [0026]The objects, features, and advantages of the present invention will become more apparent from the following detailed description in conjunction with the accompanying drawings, in which: [0027]FIG. 1A is a perspective view illustrating an example of a keypad battery pack in accordance with an exemplary embodiment of the present invention, and FIG. 1B is a perspective view illustrating another example of a keypad battery pack in accordance with an exemplary embodiment of the present invention; [0028]FIG. 2 is a perspective view illustrating a front surface of a mobile terminal having a keypad battery pack in accordance with an exemplary embodiment of the present invention; [0029]FIG. 3A is a perspective view illustrating a rear surface of the mobile terminal having the keypad battery pack of FIG. 2, and FIG. 3B is an exploded perspective view illustrating the rear surface of the mobile terminal having the keypad battery pack of FIG. 2; [0030]FIG. 4A is a perspective view illustrating a front surface of a mobile terminal having a keypad battery pack in accordance with another exemplary embodiment of the present invention, and FIG. 4B is a perspective view illustrating a rear surface of the mobile terminal having the keypad battery pack of FIG. 4A; [0031]FIG. 5 is a perspective view illustrating a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack in accordance with another exemplary embodiment of the present invention; and [0032]FIG. 6 is a block diagram illustrating an internal configuration of a mobile terminal in accordance with another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0033]Exemplary embodiments of the present invention are described with reference to the accompanying drawings in detail. The same reference numbers are used throughout the drawings to refer to the same or like parts. Detailed descriptions of well-known functions and structures incorporated herein may be omitted to avoid obscuring the subject matter of the present invention. [0034]FIG. 1A is a perspective view illustrating an example of a keypad battery pack in accordance with an exemplary embodiment of the present invention, and FIG. 1B is a perspective view illustrating another example of a keypad battery pack in accordance with an exemplary embodiment of the present invention. [0035]As shown in FIGS. 1A and 1B, the keypad battery packs 10 and 20 of the present invention are characterized in that keypads 12 and22 are formed on typical battery packs having batteries (not shown) included therein. For example, the batteries include Lithium-ion (Li-ion) battery cells or Lithium-ion polymer battery cells. The present invention is not directly related to types or internal configurations of batteries and is not limited in this regard. [0036]The battery packs 10 and 20 have first surfaces 11a and 21a and second surfaces 11b and 21b, respectively, and the keypads 12 and 22 are formed on the first surfaces 11a and 12a of the battery packs 10 and 20, respectively. Although not shown in FIGS. 1A and 1B, battery terminals 15 (shown in FIG. 3B) are positioned on the second surfaces 11b and 21b of the battery packs 10 and 20. When the battery packs 10 and 20 are mounted on mobile terminals, the first surfaces 11a and 21a become outer surfaces and the second surfaces 11b and 21b become inner surfaces. [0037]The keypads 12 and 22 of the battery packs 10 and 20 may have a 3×4 key arrangement as shown in FIG. 1a, or a 5×4 key arrangement as shown in FIG. 1b. If required, the keypads 12 and 22 may include a search key (or a direction key). As such, the keypads 12 and 22 of the battery pack 10 and 20 may have different key arrangements and types. In other words, the present invention does not focus on specific types and arrangements of the keypads 12 and 22 of the battery packs 10 and 20. In the present invention, it is important that the keypads 12 and 22 are formed on the battery packs 10 and 20, and that various types and arrangements of the keypads 12 and 22 are applied. [0038]The keypad battery packs 10 and 20 of the present invention may further have a key scan control unit 18 (shown in FIG. 6). As described later, the key scan control unit 18 is electrically connected to the keypads 12 and 22 and the battery terminals 15, and recognizes a specific key input (i.e. which key is pressed) of the keypads 12 and 22. [0039]Hereinafter, a mobile terminal having the keypad battery pack of the present invention is described in detail through exemplary embodiments. [0040]FIG. 2 is a perspective view illustrating a front surface of a mobile terminal 100 having a keypad battery pack 10 in accordance with an exemplary embodiment of the present invention. FIG. 3A is a perspective view illustrating a rear surface 31b of the mobile terminal 100 having the keypad battery pack 10 of FIG. 2, and FIG. 3B is an exploded perspective view illustrating the rear surface 31b of the mobile terminal 100 having the keypad battery pack 10 of FIG. 2. [0041]As shown in FIGS. 2, 3A, and 3B, the mobile terminal 100 includes a terminal body 30 and the battery pack 10. The terminal body 30 has a front surface 31a and a rear surface 31b, and the battery pack 10 has an outer surface 11a and an inner surface 11b corresponding to the first surface 11a and the second surface 11b, respectively, of the battery pack 10 of FIG. 1a. The inner surface 11b of the battery pack 10 is contacted with the rear surface 31b of the terminal body 30, and the outer surface 11a of the battery pack 10 faces the same direction as the rear surface 31b of the terminal body 30. [0042]The front surface 31a of the terminal body 30 has a front display unit 33a and a front keypad 32, and the rear surface 31b of the terminal body 30 has a rear display unit 33b and a battery mounting area 34. The front display unit 33a and the rear display unit 33b may include Liquid Crystal Displays (LCDs). The front display unit 33a and the rear display unit 33b may be equal to or different from each other in size and resolution of a screen. The front keypad 32 shown in FIG. 2 includes a search key and a function key. As shown in FIG. 3B, the battery pack 10 is mounted on the battery mounting area 34, and the battery mounting area 34 has a typical configuration suitable for attaching and detaching the battery pack 10. A push button 36 or another fastening means may be formed at a portion of the battery mounting area for fastening the battery pack 10. [0043]The battery pack 10 is mounted on the battery mounting area 34 of the terminal body 30. The battery pack 10 has a rear keypad 12 formed on the outer surface 11a. The rear keypad 12 shown in FIG. 3A has a 3×4 key arrangement. As shown in FIG. 3B, the inner surface 11b of the battery pack 10 has the aforementioned battery terminal 15, and the battery mounting area 34 of the terminal body 30 has a charging terminal 35. When the battery pack 10 is mounted on the terminal body 30, the battery terminal 15 and the charging terminal 35 are electrically connected to each other by contact. The battery terminal 15 and the charging terminal 35 each have a serial communication terminal. A sill 16 may be formed at a portion of the battery pack 10 corresponding to the push button 36. [0044]A type of the front keypad 32 formed on the front surface 31a of the terminal body 30 is different from a type of the rear keypad 12 of the battery pack 10 mounted on the rear surface 31b of the terminal body 30. For example, as shown in FIGS. 2 and 3A, the front keypad 32 may include a search key, and the rear keypad 12 may have a 3*4 key arrangement. Alternatively, the front keypad 32 may include a search key, and the rear keypad may have a 5×4 key arrangement. Alternatively, the front keypad 32 may have a 3×4 or 5×4 key arrangement, and the rear keypad 12 may include a search key. [0045]As described above, in exemplary embodiments, different types of the front keypad 32 and the rear keypad 12 are arranged on the front surface and the rear surface of the mobile terminal 100. Keys are dispersed on both surfaces of the mobile terminal 100, which reduces a keypad occupation area, compared with a keypad arrangement formed only on one surface of a mobile terminal. In other words, an area available for a keypad is expanded to the rear surface of the mobile terminal 100, and thus the mobile terminal 100 has room for additional keys in a key arrangement space, thereby enabling easier addition of keys. [0046]Such an advantage allows an effective keypad arrangement in the mobile terminal 100 having various additional functions. For example, as shown in FIGS. 2 and 3A, the front surface 31a has the keypad 32 for performing a multimedia function, and the rear surface 31b has the keypad 12 for performing a basic function. By separating the front keypad 32 and the rear keypad 12 and arranging the keypads 32 and 12 on both surfaces of the mobile terminal 100, a key arrangement space of the mobile terminal 100 is effectively utilized and operation of the keypads is facilitated. Further, the keypad 32 for performing a multimedia function has a relatively small number of keys, and thus the size of the corresponding display unit 33a may be increased, thereby improving user satisfaction. [0047]The front surface and the rear surface of the mobile terminal of the present invention may be configured in a different manner to those of the above exemplary embodiment. FIG. 4A is a perspective view illustrating a front surface 131a of a mobile terminal 200 having a keypad battery pack 110 in accordance with another exemplary embodiment of the present invention, and FIG. 4B is a perspective view illustrating a rear surface 131b of the mobile terminal 200 having the keypad battery pack of 110FIG. 4A. [0048]As shown in FIG. 4A, the mobile terminal 200 of this exemplary embodiment includes a terminal body 130 having a front surface 131a with a front display 133a. However, the front surface 131a does not have a front keypad, compared with the above-mentioned exemplary embodiment. As shown in FIG. 4b, the terminal body 130 has a rear surface 131b with a rear display unit 133b, and a battery pack 110 is mounted on the rear surface 131b. The battery pack 110 has an outer surface 111a with a rear keypad 112. Because the front surface 131a of the terminal body 130 does not have a keypad, the rear keypad 112 has a typical configuration of a 3*4 key arrangement with a search key. [0049]As described above, the keypad 112 of the present invention may be formed only on the rear surface 131b of the mobile terminal 200. Accordingly, the front display unit 133a may be expanded to utilize the whole front surface 131a of the mobile terminal 200, and thus may be used as an exclusive display unit of a wide screen for receiving a digital broadcast, such as Digital Media Broadcasting (DMB). The front display 133a may be provided with a typical touch-screen function, and as shown in FIG. 4A, speakers 140a and 140b may be arranged at opposite sides of the front display unit 133a. [0050]Referring to FIGS. 2 and 3A, a key scan control unit (not shown) for recognizing a specific key input may be formed on the terminal body 30 only or on both the terminal body 30 and the battery pack 10. When the key scan control unit is formed on the terminal body 30 only, the terminal body 30 has a first key scan control unit and a second key scan control unit electrically connected to the front keypad 32 and the rear keypad 12, respectively. When the key scan control unit is formed on both the terminal body 30 and the battery pack 10, the terminal body 30 has a first key scan control unit electrically connected to the front keypad 32 and the battery pack 10 has a second key scan control unit electrically connected to the rear keypad 12. In the former case, the second key scan control unit is formed on the terminal body 30, and thus the terminal body 30 and the battery pack 10 may require additional terminals for electrically connecting the rear key pad 12 to the second key scan control unit. In the latter case, the second key scan control unit is formed on the battery pack 10, and thus a key input signal recognized by the key scan control unit may be transmitted to the terminal body 30 through a typical serial communication terminal. [0051]In particular, the mobile terminal 100 of the present invention may use different types of keypad battery packs. Referring to FIGS. 1A and 1B, the keypad battery packs 10 and 20 may be identical in battery type, overall shape and size, but may differ in type of the keypads 12 and 22. Accordingly, the mobile terminal 100 of the present invention may selectively mount the battery packs 10 and 20 having different types of keypads and use keys according to purpose. [0052]Hereinafter, a method for changing a keypad of a mobile terminal by replacing a keypad battery pack with a different keypad battery pack is described in detail through exemplary embodiments. [0053]Hereinafter, the keypad battery pack 10 shown in FIG. 1B is referred to as a first battery pack, and the keypad battery pack 20 shown in FIG. 1B is referred to as a second battery pack. Further, the keypad 32 of the terminal body 30 shown in FIG. 2 is referred to as a front keypad, the keypad 12 of the first battery pack 10 as a first keypad, and the keypad22 of the second battery pack 20 as a second keypad. [0054]FIG. 5 is a perspective view illustrating a method for changing a keypad of a mobile terminal by replacing a battery pack with a different battery pack in accordance with another exemplary embodiment of the present invention. [0055]Referring to FIGS. 2 and 5, when the first battery pack 10 and the second battery pack 20 are alternately mounted on the mobile terminal 100, the front keypad 32, the first keypad 12 and the second keypad 22 are different in types. For example, as shown in the drawings, the front keypad 32 includes a search key, the first keypad 12 has a 3×4 key arrangement, and the second keypad 22 has a 5×4 key arrangement. [0056]When the first battery pack 10 mounted on the mobile terminal 100 is replaced with the second battery pack 20, the first battery pack 10 is first removed from the battery mounting area 34. When the push button 36 of the terminal body 30 is pressed, the push button 36 fastened in the sill 16 of the first battery pack 10 is released to separate the first battery pack 10 from the battery mounting area 34. [0057]Next, the second battery pack 20 is mounted on the battery mounting area 34. When the second battery pack 20 is mounted such that a sill (not shown) of the second battery pack 20 is aligned with the push button 36, the second battery pack 20 is coupled to the terminal body 30. At the same time, a battery terminal (not shown) of the second battery pack 20 and the charging terminal 35 of the terminal body 30 are electrically connected to each other by contact. [0058]A coupling method of the terminal body 30 and the battery pack 20 includes a sliding method or an insertion method, and the present invention is not limited in this regard. [0059]Although the present invention uses three types of keypads 32, 12 and 22, the key scan control unit may be formed in two methods as described above. When the first key scan control unit and the second key scan control unit are both formed on the terminal body 30, a key input of the front keypad 32 is recognized by the first key scan control unit, and a key input of the first keypad 12 or of the second keypad 22, according to which keypad is mounted on the terminal body 30, is recognized by the second key scan control unit. When only the first key scan control unit is formed on the terminal body 30, a key input of the front keypad 32 is recognized by the first key scan control unit, the first battery pack 10 has a second key scan control unit for recognizing a key input of the first keypad 12, and the second battery pack 20 has a third key scan control unit for recognizing a key input of the second keypad 22. [0060]The above-mentioned method of the present invention may be applied to a mobile terminal in which a front surface has a front display unit but no a front keypad. [0061]FIG. 6 is a block diagram illustrating an internal configuration of a mobile terminal in accordance with another exemplary embodiment of the present invention. Referring to FIG. 6, as previously described, the mobile terminal 100 includes the terminal body 30 and the battery pack 10. [0062]The terminal body 30 includes a front keypad 32, a front display unit 33a, a rear display unit 33b, a charging terminal 35, a wireless communication unit 37, a control unit 38 having a first key scan control unit 38a, and a memory unit 39. The battery pack 10 includes a rear keypad 12, a battery terminal 15, a battery 17, and a second key scan control unit 18. Alternatively, the mobile terminal 100 may have only the rear keypad 12 without the front keypad 32. [0063]The front keypad 32 and the rear keypad 12 receive an operation signal of a user for controlling operation of the mobile terminal 100. The front keypad 32 outputs an input signal to the first key scan control unit 38a, and the rear keypad 12 outputs an input signal to the second key scan control unit 18. For example, the front keypad 32 performs a multimedia function, and the rear keypad 12 performs a basic function. [0064]The first key scan control unit 38a recognizes a specific key input of the front keypad 32, and the second key scan control unit 18 recognizes a specific key input of the rear key pad 12. In other words, each of the key scan control units 38a and 18 receives an input signal from the corresponding keypads 32 and 12 and recognizes which key is pressed. In particular, the second key scan control unit 18 recognizes a key input signal, and then outputs the signal to the control unit 38 through the battery terminal 15 and the charging terminal 35. Alternatively, the second key scan control unit 18 may be formed on the terminal body 30 instead of on the battery pack 10. [0065]The control unit 38 controls the whole operation of the mobile terminal 100. In particular, the control unit 38 receives a key input signal from the key scan control units 38a and 18, and controls a corresponding operation. [0066]The front display unit 33a and the rear display unit 33b display various information related to operation of the mobile terminal 100. The front and rear display units 33a and 33b may include LCDs, and their screens may have equal or different size and resolution. For example, when the front keypad 32 consists of only a search key and a function key for performing a multimedia function, a screen size of the front display unit 33a formed on the same surface as the front keypad 32 may be larger than that of the rear display unit 33b. In particular, when the mobile terminal does not have a front keypad, the front display unit 33a may have a size corresponding to that of an entire front surface of the terminal body 30. [0067]The wireless communication unit 37 performs a communication function, i.e. a basic function of the mobile terminal 100. The memory unit 39 stores various programs and data necessary for operation of the mobile terminal 100. [0068]The battery 17 supplies power necessary for operation of the mobile terminal 100, and may be a typical Lithium-ion battery cell. [0069]The charging terminal 35 and the battery terminal 15 are electrically connected to each other by contact. Each of the charging terminal 35 and the battery terminal 15 has positive/negative terminals for power supply and may further have a serial communication terminal for transmitting a key input signal. Alternatively, when the second key scan control unit 18 is formed on the terminal body 30, each of the charging terminal 35 and the battery terminal 15 may further have terminals for transmitting a key scan signal. [0070]As described above, the present invention forms a keypad on a rear surface as well as on a front surface of a mobile terminal, thereby expanding a keypad-placement area to the rear surface of the mobile terminal. Accordingly, keys are arranged on both surfaces of the mobile terminal, and thus the mobile terminal has room for additional keys in a key arrangement space, thereby enabling easer addition of keys. [0071]Further, when keypads are arranged on both surfaces of the mobile terminal, the present invention may effectively disperse the keypads according to function. For example, the present invention may separate a keypad for performing a basic function from a keypad for performing a multimedia function. This may enable effective space utilization and an easy operation of the keypad, thereby improving the convenience of a user. A display unit formed on the same surface as a keypad for performing a multimedia function may thus be expanded, thereby improving the satisfaction of a user. Accordingly, the present invention may provide a keypad structure suitable for a mobile terminal having an additional function such as a multimedia function. [0072]Further, the present invention may form a typical keypad and display unit on only a rear surface of a mobile terminal, on which a battery pack is mounted, and form another display unit on the entire front surface of the mobile terminal. Thus, the present invention may provide a structure of a mobile terminal suitable for an exclusive display unit having a wider screen for receiving a digital broadcast. [0073]Further, the mobile terminal of the present invention may selectively mount a plurality of battery packs having different keypad types and arrangements. Thus, the present invention may replace a keypad with a more suitable keypad according to purpose. [0074]Although exemplary embodiments of the present invention have been described in detail hereinabove, it should be understood that many variations and modifications of the basic inventive concept herein described, which may appear to those skilled in the art, will still fall within the spirit and scope of the exemplary embodiments of the present invention as defined in the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. 2006 年 6 月 28 日在韩国知识产权局提交的题为“KEYPAD BATTERY PACK, MOBILE TERMINAL AVAILABLE FOR DIFFERENT KEYPAD BATTERY PACKS, AND METHOD OF CHANGING KEYPAD OF MOBILE TERMINAL”的韩国专利申请§119(a) 美国专利号2006-0058861,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动终端,尤其涉及一种键盘电池组,一种可用于不同键盘电池组的移动终端,以及一种通过用不同的电池组更换电池组来更换移动终端的键盘的方法。 [0004] 2.相关技术的描述 [0005] 移动终端,例如手机和个人数字助理(PDA),已经得到了长足的发展,现在已经广泛应用于现代生活中。 随着移动终端的使用越来越普遍,用户的需求也越来越多样化。 因此,已经开发了移动终端以方便地提供更多功能。 例如,移动终端具备多媒体、无线互联网、数字广播收发等各种附加功能,以及通话、消息收发、个人信息管理等通用功能。 [0006] 移动终端通常具有小键盘作为用于接收用户输入的输入装置。 由于为移动终端提供了各种附加功能,因此将用于执行和控制附加功能的新键添加到典型的小键盘。 然而,移动终端具有有限的键盘放置区域,因此在有限的键盘放置区域上额外放置新键并不容易。 [0007] 同时,针对不同的国家、制造商或产品类型提供了各种键盘。 键盘的类型主要包括典型电话按键排列的3-×*4键和键盘的QWERTY按键排列的5×4键。 通常,在移动终端的制造过程中,键盘的按键排列方式是预先设定好的,因此之后的按键排列方式是无法改变的。 换言之,通常移动终端的小键盘具有固定的按键排列。 因此,如果具有特定按键排列(例如,3×4按键)的移动终端的用户想要更改为另一种按键排列(例如,5×4按键),则用户必须将移动终端更换为新的按键排列。 具有另一种按键排列的移动终端。 发明内容 [0008] 为了解决上述问题,本发明扩大了移动终端的键盘放置区域,从而能够更容易地添加按键。 [0009] 本发明还提供一种适用于具有各种附加功能的移动终端的键盘结构。 [0010] 本发明还提供一种用于交替使用具有不同按键排列的小键盘的移动终端和方法。 [0011] 本发明还提供了一种根据用途更换键盘的移动终端和方法。 [0012] 本发明进一步提高了移动终端用户的便利性和满意度。 [0013] 通常,键盘形成在移动终端的前表面上,而电池组形成在移动终端的后表面上。 本发明利用以前仅用作电池组安装区域的移动终端的后表面作为键盘放置区域。 [0014] 因此,本发明提供一种键盘电池组,即其上具有键盘的电池组。 本发明还提供一种用于交替安装不同类型的键盘电池组的移动终端。 本发明还提供一种通过用不同的电池组更换电池组来改变移动终端的键盘的方法。 [0015]根据本发明示例性实施例的移动终端包括具有前表面和后表面的终端主体、形成在前表面上的前显示单元、以及形成在后表面上的后显示单元和电池安装区域 ; 电池组,其内表面与终端主体的后表面接触,外表面与终端主体的后表面朝向相同的方向,并具有形成在外表面上的后键盘,其中安装有电池组 在终端本体的电池安装区域上与终端本体电连接。 [0016] 终端主体还可以包括形成在前表面上的前键盘。 端子主体还可以包括形成在电池安装区域上的充电端子,电池组还可以包括形成在内表面上的电池端子,其中充电端子和电池端子通过接触彼此电连接。 [0017] 前键盘的类型可以与后键盘的类型不同。 前小键盘和后小键盘中的至少一个可以具有3×4和5×4键排列之一,并且可以包括搜索键。 [0018] 终端主体还可以包括分别电连接到前键盘和后键盘的第一键扫描控制单元和第二键扫描控制单元,用于识别特定键输入。 或者,终端主体还可以包括第一键扫描控制单元,并且电池组还可以包括第二键扫描控制单元。 [0019] 充电端子和电池端子可以各自具有串行通信端子。 前显示单元的尺寸可以大于后显示单元的尺寸,并且前显示单元可以形成在终端主体的整个前表面上。 [0020] 根据本发明的另一实施例的移动终端包括具有前表面和后表面的终端主体、形成在前表面上的前显示单元、以及形成在后表面上的后显示单元和电池安装区域。 第一电池组具有安装在终端主体的电池安装区域上的内表面和外表面,使得内表面与终端主体的后表面接触以电连接到终端主体,并且具有第一 键盘形成在与终端主体后表面同向的外表面上; 第二电池组,具有内表面和外表面,并且具有形成在外表面上的第二键区,该第二键区的类型与第一键区的类型不同。 [0021] 终端主体还可以包括形成在前表面上的前键盘。 端子主体还可以包括形成在电池安装区域上的充电端子,并且第一电池组和第二电池组中的每一个还可以包括形成在其各自内表面上以电连接到充电端子的电池端子。 [0022] 前键盘的类型可以不同于第一键盘的类型和第二键盘的类型。 前小键盘可以包括搜索键,并且第一小键盘和第二小键盘中的一个具有3×4键排列,另一个具有5×4键排列。 第一小键盘和第二小键盘均可以包括搜索键,并且第一小键盘和第二小键盘中的一个具有3×4键排列,另一个具有5×4键排列。 [0023] 终端主体还可以包括与前键盘电连接的第一键扫描控制单元,用于识别特定键输入。 终端主体还可以包括第二键扫描控制单元,该第二键扫描控制单元电连接到第一键区或第二键区,用于识别特定键输入。 或者,第一电池组还可以包括与第一键区电连接以识别特定键输入的第二键扫描控制单元,并且第二电池组还包括与第二键区电连接以识别特定键输入的第三键扫描控制单元。 特定的键输入。 [0024]充电端子和电池端子可以各自具有串行通信端子。 前显示单元的尺寸可以大于后显示单元的尺寸,并且前显示单元可以形成在终端主体的整个前表面上。 [0025] 根据本发明的另一示例性实施例,一种用于更换具有终端主体的移动终端的键盘的方法,终端主体具有带有前显示单元的前表面和带有后显示单元和电池安装区域的后表面,第一电池 安装在电池安装区域上并具有外表面的第二电池组和第二电池组,第二电池组的外表面具有与第一键盘的类型不同的类型的第二键盘,包括移除第一电池组 从电池安装区域; 将第二个电池组安装在电池安装区。 附图的简要说明 [0026] 本发明的目的、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0027] 如图。 附图说明图1A是示出根据本发明示例性实施例的键盘电池组的示例的透视图。 图1B是示出根据本发明示例性实施例的键盘电池组的另一个示例的透视图; [0028] 如图。 图2是示出根据本发明示例性实施例的具有键盘电池组的移动终端的前表面的透视图; [0029] 如图。 图3A是示出具有图1的键盘电池组的移动终端的后表面的透视图。 2,和图。 图3B是示出具有图1的键盘电池组的移动终端的后表面的分解透视图。 2; [0030] 如图。 图4A是示出了根据本发明另一示例性实施例的具有键盘电池组的移动终端的前表面的透视图。 图4B是示出具有图3的键盘电池组的移动终端的后表面的透视图。 4A; [0031] 如图。 图5是示出根据本发明另一示例性实施例的通过用不同的电池组更换电池组来改变移动终端的键盘的方法的透视图; 和 [0032] 如图。 图6是示出根据本发明另一示例性实施例的移动终端的内部配置的框图。 示例性实施例的详细描述 [0033] 参考附图详细描述了本发明的示例性实施例。 贯穿附图使用相同的参考数字来指代相同或相似的部分。 为了避免混淆本发明的主题,可以省略这里并入的众所周知的功能和结构的详细描述。 [0034] 如图。 附图说明图1A是示出根据本发明示例性实施例的键盘电池组的示例的透视图。 图1B是示出根据本发明示例性实施例的键盘电池组的另一示例的透视图。 [0035] 如图所示。 1A和1B,键盘电池组 10 和 20 本发明的特征在于键盘 12 和 22 形成在其中包括电池(未示出)的典型电池组上。 例如,电池包括锂离子(Li-ion)电池或锂离子聚合物电池。 本发明与电池的类型或内部配置没有直接关系,并且在这方面不受限制。 [0036] 电池组 10 和 20 有第一个表面 11 a 和 21 a 和第二个表面 11 b 和 21 b, 分别和键盘 12 和 22 形成在第一表面上 11 a 和 12 a 电池组10 和 20 , 分别。 虽然未在图 5 中显示。 1A和1B,电池端子 15 (如图3B所示)位于第二表面上 11 b 和 21 b 电池组 10 和 20 . 当电池组 10 和 20 安装在移动终端上,第一表面 11 a 和 21 a 成为外表面和第二表面 11 b 和 21 b 变成内表面。 [0037] 键盘 12 和 22 电池组 10 和 20 可以具有如图3所示的3×4键布置。 1 a, 或如图 3 所示的 5×4 键排列。 1 b. 如果需要,键盘 12 和 22 可能包括搜索键(或方向键)。 因此,键盘 12 和 22 电池组的 10 和 20 可能有不同的键排列和类型。 换言之,本发明不专注于键盘的特定类型和布置 12 和 22 电池组 10 和 20 . 在本发明中,重要的是小键盘 12 和 22 形成在电池组上 10 和 20 ,以及各种类型和排列的键盘 12 和 22 被应用。 [0038] 键盘电池组 10 和 20 本发明还可以具有键扫描控制单元 18 (如图 6 所示)。 如后所述,键扫描控制单元 18 电连接到键盘 12 和 22 和电池端子 15 , 并识别键盘的特定键输入(即按下哪个键) 12 和 22 . [0039] 在下文中,通过示例性实施例详细描述具有本发明的键盘电池组的移动终端。 [0040] 如图。 图2是示出移动终端的前表面的透视图 100 有一个键盘电池组 10 根据本发明的示例性实施例。 如图。 图3A是表示背面的立体图 31 b 移动终端的 100 有键盘电池组 10 图。 2,和图。 图3B是表示背面的分解立体图 31 b 移动终端的 100 有键盘电池组 10 图。 2. [0041] 如图所示。 2、 3 一个,和 3 B、移动端 100 包括一个终端体 30 和电池组 10 . 终端机身 30 有一个前表面 31 a 和后表面 31 b, 和电池组 10 有一个外表面 11 a 和一个内表面 11 b 对应于第一个表面 11 a 和第二个表面 11 b, 分别是电池组 10 图。 1 a. 内表面 11 b 电池组的 10 与后表面接触 31 b 终端体的 30 , 和外表面 11 a 电池组的 10 面向与背面相同的方向 31 b 终端体的 30 . [0042] 前表面 31 a 终端体的 30 有一个前置显示单元 33 a 和一个前键盘 32 , 和后表面 31 b 终端体的 30 有一个后显示单元 33 b 和电池安装区 34 . 前显示单元 33 a 和后显示单元 33 b 可能包括液晶显示器 (LCD)。 前显示单元 33 a 和后显示单元 33 b 屏幕的大小和分辨率可以相同或不同。 前键盘 32如图所示。 图2包括搜索键和功能键。 如图所示。 3B、电池组 10 安装在电池安装区域 34 , 和电池安装区域 34 具有适合连接和拆卸电池组的典型配置 10 . 一个按钮 36 或者可以在电池安装区域的一部分处形成其他紧固装置,用于紧固电池组 10 . [0043] 电池组 10 安装在电池安装区域 34 终端体的 30 . 电池组 10 有一个后键盘 12 形成在外表面上 11 a. 后键盘 12 如图所示。 图3A具有3×4键布置。 如图所示。 3B、内表面 11 b 电池组的 10 具有上述电池端子 15 , 和电池安装区域 34 终端体的 30 有充电终端 35 . 当电池组 10 安装在终端机体上 30 , 电池端子 15 和充电终端 35 通过接触彼此电连接。 电池端子 15 和充电终端 35 每个都有一个串行通讯终端。 窗台 16 可以形成在电池组的一部分 10 对应于按钮 36 . [0044] A型前键盘 32 形成于前表面 31 a 终端体的 30 不同于一种类型的后键盘 12 电池组的 10 安装在背面 31 b 终端体的 30 . 例如,如图所示。 2和3A,前键盘 32 可能包括搜索键和后键盘 12 可能有 3*4 的按键排列。 或者,前键盘 32 可以包括搜索键,并且后键盘可以具有 5×4 键排列。 或者,前键盘 32 可能有 3×4 或 5×4 按键排列,后键盘 12 可能包括搜索关键字。 [0045] 如上所述,在示例性实施例中,不同类型的前键盘 32 和后键盘 12 设置在移动终端的正面和背面 100 . 按键分散在移动终端的两面 100 ,与仅形成在移动终端的一个表面上的键盘布置相比,减小了键盘占用面积。 换言之,可用于键盘的区域被扩展到移动终端的背面 100 ,因此移动终端 100 在按键布置空间中具有额外按键的空间,从而可以更轻松地添加按键。 [0046] 这样的优点允许在移动终端中有效的键盘布置 100 具有各种附加功能。 例如,如图所示。 2和3A,前表面 31 a 有键盘 32 用于执行多媒体功能,以及背面 31 b 有键盘 12 用于执行基本功能。 通过分离前键盘 32 和后键盘 12 并安排键盘 32 和 12 在移动终端的两个表面上 100 ,移动终端的按键排列空间 100 有效利用,方便了键盘的操作。 此外,键盘 32 用于执行多媒体功能的按键数量相对较少,因此相应的显示单元的大小 33 a 可以增加,从而提高用户满意度。 [0047] 本发明的移动终端的前表面和后表面可以以与上述示例性实施例不同的方式配置。 如图。 图4A是表示正面的立体图 131 a 移动终端的 200 有一个键盘电池组 110 根据本发明的另一个示例性实施例,以及 图4B是表示背面的立体图 131b 移动终端的 200 有键盘电池组 110 如图。 4A。 [0048] 如图所示。 4A、移动终端 200 该示例性实施例的包括终端主体 130 具有前表面 131 a 带前置显示屏 133 a. 然而,前表面 131 a 与上述示例性实施例相比,没有前键盘。 如图所示。 4 b, 终端体 130 有一个后表面 131 b 带后显示单元 133 b, 和一个电池组 110 安装在背面 131 b. 电池组 110 有一个外表面 111 a 带后键盘 112 . 因为正面 131 a 终端体的 130 没有键盘,后键盘 112 具有 3*4 键排列和搜索键的典型配置。 [0049] 如上所述,键盘 112 本发明的可仅在后表面上形成 131 b 移动终端的 200 . 因此,前显示单元 133 a 可以扩展以利用整个前表面 131 a 移动终端的 200 ,因此可以用作宽屏幕的专用显示单元,用于接收数字广播,例如数字媒体广播(DMB)。 前显示器 133 a 可以具有典型的触摸屏功能,如图1所示。 4A、扬声器 140 a 和 140 b 可以布置在前显示单元的相对两侧 133 a. [0050] 参考图。 参照图2和3A,用于识别特定键输入的键扫描控制单元(未示出)可以形成在终端主体上 30 仅在终端主体上或在两个终端主体上 30 和电池组 10 . 当键扫描控制单元形成在终端机体上时 30 只是,终端体 30 具有一第一按键扫描控制单元及一第二按键扫描控制单元电性连接至前键盘 32 和后键盘 12 , 分别。 当键扫描控制单元形成在两个终端机身上时 30 和电池组 10 , 终端体 30 具有一第一按键扫描控制单元,电性连接前键盘 32 和电池组 10 具有一第二按键扫描控制单元,电性连接后键盘 12 . 在前一种情况下,第二键扫描控制单元形成在终端主体上 30 ,因此终端体 30 和电池组 10 可能需要额外的端子来电连接后键盘 12 到第二键扫描控制单元。 在后一种情况下,第二键扫描控制单元形成在电池组上 10 ,因此可以将键扫描控制单元识别的键输入信号传输到终端主体 30 通过一个典型的串行通信终端。 [0051] 尤其是移动终端 100 本发明的实施例可以使用不同类型的键盘电池组。 参考图。 1A和1B,键盘电池组 10 和 20 电池类型、整体形状和尺寸可能相同,但键盘类型可能不同 12 和 22 . 因此,移动终端 100 本发明可以选择性地安装电池组 10 和 20 具有不同类型的键盘并根据用途使用按键。 [0052] 在下文中,通过示例性实施例详细描述通过用不同的键盘电池组更换键盘电池组来改变移动终端的键盘的方法。 [0053] 以下,键盘电池组 10 如图所示。 图1B称为第一电池组,键盘电池组 20 如图所示。 图1B的电池组被称为第二电池组。 此外,键盘 32 终端体的 30 如图所示。 2被称为前键盘,键盘12 第一个电池组 10 作为第一个键盘,和键盘 22 第二个电池组 20 作为第二个键盘。 [0054] 如图。 图5是示出根据本发明另一示例性实施例的通过用不同的电池组更换电池组来改变移动终端的键盘的方法的透视图。 [0055] 参考图。 2和5,当第一个电池组 10 和第二个电池组 20 交替安装在移动终端上 100 , 前键盘 32 , 第一个键盘 12 和第二个键盘 22 类型不同。 例如,如图所示,前键盘 32 包括一个搜索键,第一个键盘 12 有一个 3×4 按键排列,第二个键盘 22 有一个 5×4 键排列。 [0056] 当第一个电池组 10 安装在移动终端上 100 更换为第二个电池组 20 ,第一个电池组 10 首先从电池安装区域移除 34 . 当按下按钮 36 终端体的 30 被按下,按钮 36 固定在窗台上 16 第一个电池组 10 被释放以分离第一个电池组 10 从电池安装区域 34 . [0057] 接下来,第二个电池组 20 安装在电池安装区域 34 . 当第二个电池组 20 安装成使得第二电池组的窗台(未示出) 20 与按钮对齐 36 ,第二个电池组 20 耦合到终端机体 30 . 同时,第二电池组的电池端子(未图示) 20 和充电终端 35 终端体的 30 通过接触彼此电连接。 [0058] 一种端子体的耦合方法 30 和电池组 20 包括滑动方式或插入方式,本发明不以此为限。 [0059] 尽管本发明使用三种类型的键盘 32 , 12 和 22 ,键扫描控制单元可以以如上所述的两种方法形成。 当第一按键扫描控制单元和第二按键扫描控制单元均形成在终端机体上时 30 , 前键盘的一键输入 32 被第一按键扫描控制单元识别,并且第一键盘的按键输入 12 或第二个键盘 22 ,根据哪个键盘安装在终端机身上 30 ,由第二键扫描控制单元识别。 当终端主体上仅形成第一键扫描控制单元时 30 , 前键盘的一键输入 32 被第一个按键扫描控制单元识别,第一个电池组 10 具有第二键扫描控制单元,用于识别第一键盘的键输入 12 , 和第二个电池组 20 具有第三键扫描控制单元,用于识别第二键盘的键输入 22 . [0060] 本发明的上述方法可以应用于前表面具有前显示单元但没有前键盘的移动终端。 [0061] 如图。 图6是示出根据本发明另一示例性实施例的移动终端的内部配置的框图。 参考图。 参照图6,如前所述,移动终端 100 包括终端体 30 和电池组 10 . [0062] 终端本体 30 包括一个前键盘 32 , 一个前置显示单元 33 a, 后显示单元 33 b, 一个充电终端 35 , 一个无线通信单元 37 , 一个控制单元 38 具有第一键扫描控制单元 38 a, 和一个内存单元 39 . 电池组 10 包括一个后键盘 12 , 一个电池端子 15 , 一个电池 17,以及第二键扫描控制单元 18 . 或者,移动终端 100 可能只有后键盘 12 没有前键盘 32 . [0063] 前键盘 32 和后键盘 12 接收用户的操作信号,用于控制移动终端的操作 100 . 前键盘 32 向第一键扫描控制单元输出输入信号 38 a, 和后键盘 12 向第二键扫描控制单元输出输入信号 18 . 例如,前键盘 32 执行多媒体功能,后键盘 12 执行基本功能。 [0064] 第一键扫描控制单元 38 a 识别前键盘的特定键输入 32 ,以及第二键扫描控制单元 18 识别后键盘的特定键输入 12 . 换言之,每个键扫描控制单元 38 a 和 18 从相应的键盘接收输入信号 32 和 12 并识别按下了哪个键。 特别地,第二键扫描控制单元 18 识别按键输入信号,然后将信号输出到控制单元 38 通过电池端子 15 和充电终端 35 . 或者,第二键扫描控制单元 18 可以形成在终端本体上 30 而不是在电池组上 10 . [0065] 控制单元 38 控制移动端的整体操作 100 . 特别是控制单元 38 从按键扫描控制单元接收按键输入信号 38 a 和 18 , 并控制相应的操作。 [0066] 前显示单元 33 a 和后显示单元 33 b 显示与移动终端操作相关的各种信息 100 . 前后显示单元 33 a 和 33 b 可能包括 LCD,它们的屏幕可能具有相同或不同的尺寸和分辨率。 例如,当正面键盘 32 仅由一个搜索键和一个用于执行多媒体功能的功能键组成,前显示单元的屏幕尺寸 33 a 形成在与前键盘相同的表面上 32 可能大于后置显示单元 33 b. 特别地,当移动终端没有前置键盘时,前置显示单元 33 a 可以具有与终端主体的整个前表面的尺寸相对应的尺寸 30 . [0067] 无线通信单元 37 执行通信功能,即移动终端的基本功能 100 . 记忆单元 39 存储移动终端操作所需的各种程序和数据 100 . [0068] 电池 17 提供移动终端运行所需的电源 100 ,并且可能是典型的锂离子电池。 [0069] 充电终端 35 和电池端子 15 通过接触彼此电连接。 每个充电端子 35 和电池端子 15 具有用于供电的正/负端子,还可以具有用于传输按键输入信号的串行通信端子。 或者,当第二键扫描控制单元 18 形成在端子本体上 30 , 每个充电端 35 和电池端子 15 还可以具有用于发送键扫描信号的端子。 [0070] 如上所述,本发明在移动终端的后表面以及前表面上形成小键盘,从而将小键盘放置区域扩展到移动终端的后表面。 相应地,在移动终端的两个表面上都布置了按键,因此移动终端在按键布置空间中具有用于额外按键的空间,从而能够更容易地添加按键。 [0071]此外,当键盘布置在移动终端的两个表面上时,本发明可以根据功能有效地分散键盘。 例如,本发明可以将用于执行基本功能的小键盘与用于执行多媒体功能的小键盘分开。 这可以实现有效的空间利用和键盘的简单操作,从而提高用户的便利性。 因此可以扩展形成在与用于执行多媒体功能的小键盘相同的表面上的显示单元,从而提高用户的满意度。 因此,本发明可以提供一种适用于具有诸如多媒体功能的附加功能的移动终端的小键盘结构。 [0072] 此外,本发明可以仅在其上安装有电池组的移动终端的后表面上形成典型的小键盘和显示单元,并且在移动终端的整个前表面上形成另一个显示单元。 因此,本发明可以提供一种适用于具有更宽屏幕的专用显示单元的移动终端结构,用于接收数字广播。 [0073] 此外,本发明的移动终端可以选择性地安装具有不同键盘类型和布置的多个电池组。 因此,本发明可以根据目的用更合适的小键盘代替小键盘。 [0074] 尽管上文已经详细描述了本发明的示例性实施例,但应当理解,对于本领域技术人员来说可能出现的本文描述的基本发明概念的许多变化和修改仍将落入本发明的精神和范围内。 如在所附权利要求中定义的本发明的示例性实施例。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101098534A(String), EP1874008A1(String), KR100757232B1(String), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101098534A(String), EP1874008A1(String), KR100757232B1(String), US20080004085A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101098534A(String), EP1874008A1(String), KR100757232B1(String), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270887(Integer), CN101098534A(String), 1047438(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270887(Integer), EP1874008A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270887(Integer), KR100757232B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270887(Integer), US20080004085A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101098534A(String), CN101098534A(String), 1199203200(Integer), 270887(Integer), 185171(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:31.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185934(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185934(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185934(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185934(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.283 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.283 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and composite photographing method using multiple mobile terminals(String), 移动终端和使用多个移动终端的合成拍摄方法(String), US20100004020A1(String), A mobile terminal and composite photographing method using multiple mobile terminals are provided. The composite photographing method uses multiple mobile terminals. A master mobile terminal composes an incomplete composite photograph, generates a participant list of slave mobile terminals, and sends the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list. The first slave mobile terminal receives the incomplete composite photograph and participant list, further composes the received composite photograph, determines whether the composed composite photograph is complete, sends, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list, and sends, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing. Hence, several users at distinct locations can jointly produce a composite photograph.(String), 提供了一种移动终端和使用多个移动终端的合成拍摄方法。 复合拍摄方法使用多个移动终端。 主移动终端对不完整的合成照片进行合成,生成从移动终端的参与者列表,并将不完整的合成照片和参与者列表发送给参与者列表中的第一从移动终端。 第一从移动终端接收到不完整的合成照片和参与者列表,进一步对接收到的合成照片进行合成,判断合成的合成照片是否完整,当合成的合成照片不完整时,将合成的合成照片发送给第二从移动终端 在参与者列表中,当合成的合成照片完成后,将合成的合成照片发送给所有参与合成拍摄的移动终端。 因此,不同位置的几个用户可以共同产生合成照片。(String), US12/496149(String), 1246377600(Integer), US20100004020A1(String), 1262793600(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 20(Integer), US20030236830A1 | US20040131278A1 | US20060078173A1 | US20060204032A1 | US20070146798A1 | US20070188626A1 | US20070263995A1 | US20090128644A1 | US20090136225A1 | US20090254572A1 | US20090322788A1 | US20110116679A1 | US5953050A | US6005987A | US6388654B1 | US6900904B1 | US7391910B2 | US7627311B2 | US7734116B2 | US7889381B2(String), 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:32.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185935(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f204eeffb48742f199841f7a09c2c1bf.png(String), 185935(Integer), f204eeffb48742f199841f7a09c2c1bf.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and composite photographing method using multiple mobile terminals(String), 移动终端和使用多个移动终端的合成拍摄方法(String), US20100004020A1(String), A mobile terminal and composite photographing method using multiple mobile terminals are provided. The composite photographing method uses multiple mobile terminals. A master mobile terminal composes an incomplete composite photograph, generates a participant list of slave mobile terminals, and sends the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list. The first slave mobile terminal receives the incomplete composite photograph and participant list, further composes the received composite photograph, determines whether the composed composite photograph is complete, sends, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list, and sends, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing. Hence, several users at distinct locations can jointly produce a composite photograph.(String), 提供了一种移动终端和使用多个移动终端的合成拍摄方法。 复合拍摄方法使用多个移动终端。 主移动终端对不完整的合成照片进行合成,生成从移动终端的参与者列表,并将不完整的合成照片和参与者列表发送给参与者列表中的第一从移动终端。 第一从移动终端接收到不完整的合成照片和参与者列表,进一步对接收到的合成照片进行合成,判断合成的合成照片是否完整,当合成的合成照片不完整时,将合成的合成照片发送给第二从移动终端 在参与者列表中,当合成的合成照片完成后,将合成的合成照片发送给所有参与合成拍摄的移动终端。 因此,不同位置的几个用户可以共同产生合成照片。(String), US12/496149(String), 1246377600(Integer), US20100004020A1(String), 1262793600(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 20(Integer), US20030236830A1 | US20040131278A1 | US20060078173A1 | US20060204032A1 | US20070146798A1 | US20070188626A1 | US20070263995A1 | US20090128644A1 | US20090136225A1 | US20090254572A1 | US20090322788A1 | US20110116679A1 | US5953050A | US6005987A | US6388654B1 | US6900904B1 | US7391910B2 | US7627311B2 | US7734116B2 | US7889381B2(String), \20230420\f204eeffb48742f199841f7a09c2c1bf.png(String), 22(Integer), 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 1. A composite photographing method using multiple mobile terminals, the method comprising:composing, by a master mobile terminal, an incomplete composite photograph;generating, by a master mobile terminal, a participant list of slave mobile terminals;sending, by the master mobile terminal, the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list;receiving, by the first slave mobile terminal, the incomplete composite photograph and participant list;further composing, by the first slave mobile terminal, the received composite photograph;determining, by the first slave mobile terminal, whether the composed composite photograph is complete;sending, by the first slave mobile terminal, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list; andsending, when the composed composite photograph is complete, by the first slave mobile terminal, the composed composite photograph to all mobile terminals having participated in composite photographing.(String), 1.一种使用多个移动终端的合成拍摄方法,该方法包括:主控移动终端合成一张不完整的合成照片;主移动终端生成从移动终端的参与者列表;主移动终端将不完整合成照片和参会名单发送给参会名单中的第一从移动终端;第一从移动终端接收不完整合成照片和参会人员名单;第一从移动终端对接收到的合成照片进行进一步合成;第一从移动终端判断合成的合成照片是否完整;第一从移动终端在合成合成照片不完整时,将合成合成照片发送给参会者列表中的第二从移动终端;和第一从移动终端在完成合成照片后,将合成照片发送给所有参与合成的移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 2. The method of claim 1, wherein a mobile terminal in a composite shot mode one of composes and further composes a composite photograph by inserting a taken picture into at least one photo-section of the composite photograph.(String), 2.如权利要求1所述的方法,其中移动终端在合成照片模式之一中通过将拍摄的照片插入合成照片的至少一个照片部分来合成并进一步合成合成照片。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 3. The method of claim 2, wherein the second slave mobile terminal comprises a mobile terminal in the participant list that has not yet participated in composite photographing.(String), 3.如权利要求2所述的方法,其中第二从移动终端包括参与列表中尚未参与合影的移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 4. The method of claim 2, wherein each of the mobile terminals participating in composite photographing belongs to the participant list.(String), 4.如权利要求2所述的方法,其中每个参与合影的移动终端都属于参与列表。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 5. The method of claim 1, wherein transmission of a composite photograph is performed through one of a radio frequency module and a short-range wireless module.(String), 5.如权利要求1所述的方法,其中合成照片的传输通过射频模块和近距离无线模块之一进行。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 6. A composite photographing method using multiple mobile terminals, the method comprising:composing, by a master mobile terminal, an incomplete composite photograph;generating, by the master mobile terminal, a participant list of one or more slave mobile terminals;setting, by the master mobile terminal, photo-section information for the slave mobile terminals;sending, by the master mobile terminal, the incomplete composite photograph and photo-section information to slave mobile terminals in the participant list;receiving, by each of the slave mobile terminals, the incomplete composite photograph and photo-section information;further composing, by each of the slave mobile terminals, the received composite photograph utilizing the photo-section information;sending, by each of the slave mobile terminals, the composed composite photograph to the master mobile terminal; andcombining, by the master mobile terminal, the incomplete composite photographs received from the slave mobile terminals together into a complete composite photograph.(String), 6.一种使用多个移动终端的合成拍摄方法,该方法包括:主控移动终端合成一张不完整的合成照片;主移动终端生成一个或多个从移动终端的参与者列表;主移动终端为从移动终端设置照片切片信息;主移动终端向参会名单中的从移动终端发送不完整的合成照片和照片切片信息;各从属移动终端接收不完整合成照片和照片切面信息;各从属移动终端将接收到的合成照片进一步利用照片切面信息进行合成;各从移动终端将合成后的合成照片发送给主移动终端;和主移动终端将从从移动终端接收到的不完整合成照片组合成一张完整合成照片。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 7. The method of claim 6, wherein a mobile terminal in a composite shot mode one of composes and further composes a composite photograph by inserting a taken picture into at least one photo-section of the composite photograph based on the photo-section information.(String), 7.如权利要求6所述的方法,其中移动终端在合成照片模式下,根据照片断面信息,将拍摄的照片插入到合成照片的至少一个照片断面中,合成并进一步合成一张合成照片。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 8. The method of claim 7, further comprising sending, by the master mobile terminal, the complete composite photograph to all mobile terminals participating in composite photographing.(String), 8.如权利要求7所述的方法,还包括主控移动终端将完整的合成照片发送给所有参与合成的移动终端。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 9. The method of claim 7, wherein the incomplete composite photographs from the slave mobile terminals to the master mobile terminal are one of a first type composite photograph including both an image selected in composite shot mode and a taken picture, a second type composite photograph including only a taken picture, and a third type composite photograph including a taken picture and associated photo-section indicator in a selected image.(String), 9.如权利要求7所述的方法,其中从移动终端到主移动终端的不完整合成照片为:第一类合成照片,包括合成拍摄模式下选择的图像和拍摄的照片;第二类合成照片,仅包括拍摄照片;第三类合成照片。类型合成照片,包括所选图像中的拍摄照片和相关照片部分指示符。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 10. The method of claim 9, wherein the incomplete composite photograph from the master mobile terminal to the slave mobile terminals comprises a composite photograph whose photo-section assigned to the master mobile terminal is one of empty and filled with a taken picture.(String), 10.如权利要求9所述的方法,其中主移动终端向从移动终端发送的不完整合成照片包括分配给主移动终端的照片部分为空填充照片的合成照片。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 11. The method of claim 6, wherein transmission of a composite photograph is performed through one of a radio frequency module and a short-range wireless module.(String), 11.如权利要求6所述的方法,其中合成照片的传输通过射频模块和近距离无线模块之一进行。(String), 1(Integer), 10(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 12. A mobile terminal comprising:an input unit for composing a composite photograph and for generating a participant list;a communication unit for transmitting a composite photograph and the participant list; anda control unit for sending a composed incomplete composite photograph and the participant list to a first mobile terminal in the participant list, for further composing, upon reception of an incomplete composite photograph, the received composite photograph, for sending, when the composed composite photograph is incomplete, the composed composite photograph to a second mobile terminal in the participant list, and for sending, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing.(String), 12.移动终端包括:输入单元,用于合成照片和生成参与者列表;用于传输合成照片和参与者列表的通信单元;和控制单元,用于将合成的不完整合成照片和参会者名单发送至参会者列表中的第一移动终端,用于在接收到不完整合成照片后,将接收到的合成照片进一步合成,用于发送,当合成的合成照片为不完整时,将合成后的合成照片发送给参与列表中的第二个移动终端,当合成后的合成照片完成时,将合成后的合成照片发送给所有参与合成的移动终端。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 13. The mobile terminal of claim 12, wherein the input unit comprises:a camera unit for composing a composite photograph in a composite shot mode by taking a picture and inserting the picture into at least one photo-section of the composite photograph; anda key input unit for generating the participant list.(String), 13.如权利要求12所述的移动终端,其中输入单元包括:相机单元,用于通过拍摄一张照片并将该照片插入到合成照片的至少一个照片区中,以合成拍摄模式合成合成照片;和用于生成参与者列表的键输入单元。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 14. The mobile terminal of claim 13, wherein the second mobile terminal comprises a mobile terminal in the participant list that has not yet participated in composite photographing.(String), 14.如权利要求13所述的移动终端,其中第二移动终端包括参与列表中尚未参与合影的移动终端。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 15. The mobile terminal of claim 13, wherein each of the mobile terminals participating in composite photographing belongs to the participant list.(String), 15.如权利要求13所述的移动终端,其中每个参与合影的移动终端都属于参与列表。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 16. The mobile terminal of claim 12, wherein the communication unit comprises one of a radio frequency module and a short-range wireless module.(String), 16.如权利要求12所述的移动终端,其中通信单元包括射频模块和近距离无线模块之一。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 17. A mobile terminal comprising:an input unit for composing a composite photograph, for generating a participant list, and for setting photo-section information assigning photo-sections of a composite photograph to different mobile terminals in the participant list;a communication unit for transmitting a composite photograph and the photo-section information; anda control unit for sending an incomplete composite photograph and the photo-section information to one or more mobile terminals in the participant list, for further composing, upon reception of an incomplete composite photograph from a first mobile terminal, the received composite photograph, for sending the composed composite photograph to the first mobile terminal, and for combining, upon reception of incomplete composite photographs matching with the incomplete composite photograph having been sent, the received incomplete composite photographs into a complete composite photograph.(String), 17.移动终端包括:合成照片输入单元,生成参会名单,并设置参会名单中不同移动终端分配合成照片照片分片的照片分片信息;传输合成照片和照片切片信息的通信单元;和控制单元,用于向参加者列表中的一个或多个移动终端发送不完整合成照片和照片切片信息,用于进一步合成,在接收到来自第一移动终端的不完整合成照片后,接收到的合成照片,用于发送将合成后的合成照片发送给第一移动终端,用于在接收到与已发送的不完整合成照片匹配的不完整合成照片时,将接收到的不完整合成照片合成为完整合成照片。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 18. The mobile terminal of claim 17, wherein the input unit comprises:a camera unit for composing a composite photograph in a composite shot mode by taking a picture and inserting the picture into at least one photo-section of the composite photograph; anda key input unit for generating the participant list and for setting the photo-section information.(String), 18.如权利要求17所述的移动终端,其中输入单元包括:相机单元,用于通过拍摄一张照片并将该照片插入到合成照片的至少一个照片区中,以合成拍摄模式合成合成照片;和按键输入单元,用于生成与会者名单和设置照片切片信息。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 19. The mobile terminal of claim 18, wherein the control unit sends the complete composite photograph to all mobile terminals participating in composite photographing.(String), 19.如权利要求18所述的移动终端,其中控制单元将完整的合成照片发送给所有参与合成的移动终端。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 20. The mobile terminal of claim 18, wherein the incomplete composite photograph sent to the first mobile terminal comprises one of a first type composite photograph including both an image selected in composite shot mode and a taken picture, a second type composite photograph including only a taken picture, and a third type composite photograph including a taken picture and associated photo-section indicator in a selected image.(String), 20.如权利要求18所述的移动终端,其中发送给第一移动终端的不完整合成照片包括:第一类合成照片,包括合成拍摄模式下选择的图像和拍摄的照片;第二类合成照片,仅包括拍摄照片;第三类合成照片,包括所选图像中的已拍摄照片和相关照片部分指示器。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 21. The mobile terminal of claim 20, wherein the incomplete composite photograph sent to mobile terminals in the participant list comprises a composite photograph whose photo-section is one of empty and filled with a taken picture.(String), 21.如权利要求20所述的移动终端,其中与会者列表中发送至移动终端的不完整合成照片包括照片部分为空白且填充有拍摄照片的合成照片。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185935(Integer), 22. The mobile terminal of claim 17, wherein the communication unit comprises one of a radio frequency module and a short-range wireless module.(String), 22.如权利要求17所述的移动终端,其中通信单元包括射频模块和近距离无线模块之一。(String), 1(Integer), 21(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185935(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. § 119(a) of a Korean patent application filed in the Korean Intellectual Property Office on Jul. 2, 2008 and assigned Serial No. 10-2008-0063874, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal. More particularly, the present invention relates to a mobile terminal and composite photographing method using multiple mobile terminals wherein multiple mobile terminals at distinct locations can jointly produce a composite photograph. [0004]2. Description of the Related Art [0005]With electronic components becoming smaller and lighter, modern mobile terminals are becoming increasingly miniaturized. In addition to basic call-handling functions, to satisfy diverse user needs, commercially available mobile terminals have various advanced features including camera-related functions. [0006]A camera-equipped mobile terminal can provide various shot modes including still shot, continuous shot, composite shot, night shot, self-shot, and video shot. More particularly in a composite shot, several pictures are taken and combined into a single composite photograph. Here, multiple pictures are taken by the same mobile terminal. That is, a single mobile terminal can be used to produce a composite photograph. To produce a composite photograph composed of pictures of several persons, these persons may have to be present at the same place and time. [0007]In composite shot mode, a multi-photo framing feature can be used to produce a photograph from multiple separately taken pictures. To use the multi-photo framing feature, these pictures have to be taken by the same mobile terminal, and, if the pictures are related to persons, the persons may have to be present at the same place and time. SUMMARY OF THE INVENTION [0008]An aspect of the present invention is to address the above-mentioned problems and/or disadvantages and to provide at least the advantages described blow. Accordingly, an aspect of the present invention is to provide a mobile terminal and a composite photographing method that enable multiple mobile terminals to jointly produce a composite photograph. [0009]Another aspect of the present invention is to provide a mobile terminal and a composite photographing method that reduce communication costs by utilizing short-range wireless communication to transmit a picture for composite photography. [0010]In accordance with an aspect of the present invention, a composite photographing method using multiple mobile terminals is provided. The method includes composing, by a master mobile terminal, an incomplete composite photograph, generating, by the master mobile terminal, a participant list of slave mobile terminals, sending, by the master mobile terminal, the incomplete composite photograph and participant list to a first slave mobile terminal in the participant list, receiving, by the first slave mobile terminal, the incomplete composite photograph and participant list, further composing, by the first slave mobile terminal, the received composite photograph, determining, by the first slave mobile terminal, whether the composed composite photograph is complete, sending, by the first slave mobile terminal, when the composed composite photograph is incomplete, the composed composite photograph to a second slave mobile terminal in the participant list, and sending, when the composed composite photograph is complete, by the first slave mobile terminal, the composed composite photograph to all mobile terminals having participated in composite photographing. [0011]In accordance with another aspect of the present invention, a composite photographing method using multiple mobile terminals is provided. The method includes composing, by a master mobile terminal, an incomplete composite photograph, generating, by the master mobile terminal, a participant list of one or more slave mobile terminals, setting, by the master mobile terminal, photo-section information for the slave mobile terminals, sending, by the master mobile terminal, the incomplete composite photograph and photo-section information to slave mobile terminals in the participant list, receiving, by each of the slave mobile terminals, the incomplete composite photograph and photo-section information, further composing, by each of the slave mobile terminals, the received composite photograph utilizing the photo-section information, sending, by each of the slave mobile terminals, the composed composite photograph to the master mobile terminal, and combining, by the master mobile terminal, the incomplete composite photographs received from the slave mobile terminals together into a complete composite photograph. [0012]In accordance with yet another aspect of the present invention, a mobile terminal is provided. The terminal includes an input unit for composing a composite photograph and for generating a participant list, a communication unit for transmitting a composite photograph and the participant list, and a control unit for sending a composed incomplete composite photograph and the participant list to a first mobile terminal in the participant list, for further composing, upon reception of an incomplete composite photograph, the received composite photograph, for sending, when the composed composite photograph is incomplete, the composed composite photograph to a second mobile terminal in the participant list, and for sending, when the composed composite photograph is complete, the composed composite photograph to all mobile terminals having participated in composite photographing. [0013]In accordance with still another aspect of the present invention, a mobile terminal is provided. The terminal includes an input unit for composing a composite photograph, for generating a participant list, and for setting photo-section information assigning photo-sections of a composite photograph to different mobile terminals in the participant list, a communication unit for transmitting a composite photograph and the photo-section information, and a control unit for sending an incomplete composite photograph and the photo-section information to one or more mobile terminals in the participant list, for further composing, upon reception of an incomplete composite photograph from a first mobile terminal, the received composite photograph, for sending the composed composite photograph to the first mobile terminal, and for combining, upon reception of incomplete composite photographs matching with the incomplete composite photograph having been sent, the received incomplete composite photographs into a complete composite photograph. [0014]In a feature of exemplary embodiments of the present invention, several users at distinct locations can jointly produce a composite photograph, thereby enhancing user convenience. For example, when family members living at distinct locations desire to take a family photograph, a first member carrying a mobile terminal may select a multi-photo frame, take a facial image, insert the facial image in a photo-section of the multi-photo frame, and may send the multi-photo frame to a second member carrying a mobile terminal. Then, the second member may take a facial image, insert the facial image in another photo-section of the multi-photo frame, and may send the multi-photo frame to a third member carrying a mobile terminal. This process can be continued until a final family photograph is produced. [0015]In addition, short-range wireless communication such as Bluetooth and the like can be used to transmit component images of a composite photograph, thereby reducing communication costs. [0016]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 illustrates communication between mobile terminals for composite photographing according to an exemplary embodiment of the present invention. [0019]FIG. 2 is a block diagram illustrating a mobile terminal capable of producing a composite photograph according to an exemplary embodiment of the present invention; [0020]FIG. 3 is a sequence diagram of a first composite photographing method using mobile terminals based on Radio Frequency (RF) communication according to an exemplary embodiment of the present invention; [0021]FIGS. 4A to 4D are screen representations illustrating steps in the first composite photographing method according to an exemplary embodiment of the present invention; [0022]FIG. 5 is a flowchart illustrating the first composite photographing method based on RF communication according to an exemplary embodiment of the present invention; [0023]FIG. 6 is a sequence diagram of the first composite photographing method based on short-range wireless communication according to an exemplary embodiment of the present invention; [0024]FIG. 7 is a sequence diagram of a second composite photographing method using mobile terminals based on RF communication according to an exemplary embodiment of the present invention; [0025]FIGS. 8A to 8D are screen representations illustrating steps in the second composite photographing method according to an exemplary embodiment of the present invention; [0026]FIGS. 9A and 9B illustrate component images transmitted during execution of the second composite photographing method according to an exemplary embodiment of the present invention; [0027]FIG. 10 is a flowchart illustrating the second composite photographing method based on RF communication according to an exemplary embodiment of the present invention; and [0028]FIG. 11 is a sequence diagram of the second composite photographing method based on short-range wireless communication according to an exemplary embodiment of the present invention. [0029]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0030]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0031]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0032]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0033]For the purpose of description, a mobile terminal is used as an example in exemplary embodiments of the present invention, however the present invention is not limited thereto. The mobile terminal of exemplary embodiments of the present invention is a terminal for user convenience, and may be any information and communication appliance or multimedia appliance, such as a mobile terminal, mobile phone, wired/wireless phone, Portable Multimedia Player (PMP), Personal Digital Assistant (PDA), smart phone, and MP3 player. The mobile terminal may include one or both of a radio frequency module and short-range communication module. While a Bluetooth module is described herein as the short-range communication module as an example, any other short-range communication module may be utilized. [0034]FIG. 1 illustrates communication between mobile terminals for composite photographing according to an exemplary embodiment of the present invention. [0035]Referring to FIG. 1, the system for transmission of component images and production of a composite photograph includes a plurality of mobile terminals 100a to 100n, and a Multimedia Message Service Center (MMSC) 200. In FIG. 1, each of the mobile terminals 100a to 100n includes a communication unit (107 in FIG. 2) that is implemented with a Radio Frequency (RF) module. That is, the mobile terminals 100a to 100n communicate with the MMSC 200 using their RF modules. In the flowing description, FIG. 1 is not applied to the case where the mobile terminals 100a to 100n each include a communication unit implemented with a short-range wireless module. FIG. 1 can be applied to the case where the mobile terminals 100a to 100n each include a communication unit implemented with both a short-range wireless module and RF module. [0036]The mobile terminals 100a to 100n each can make a voice call, use a Short Message Service (SMS), Multimedia Message Service (MMS) and Enhanced Message Service (EMS), and include an MP3 player for playback of a desired song. The mobile terminals 100a to 100n each can include a camera unit (101 in FIG. 2) to take a picture of a target object. [0037]One of the mobile terminals 100a to 100n can take a picture through a camera unit for a composite photograph, and send an MMS message containing the taken picture to another one thereof. That is, the first mobile terminal 100a sends to the MMSC 200 an MMS message containing a picture with a request for delivery of the MMS message containing a picture to the second mobile terminal 100b. The MMSC 200 sends a reply to the first mobile terminal 100a, and sends an MMS notification to the second mobile terminal 100b. The second mobile terminal 100b sends a reply to the MMSC 200, connects to the MMSC 200, and retrieves the corresponding MMS message together with information on the first mobile terminal 100a. [0038]In the following description, the first mobile terminal 100a acts as a master mobile terminal that initiates composite photographing by composing an MMS message containing a picture for a composite photograph, and a participant list. The remaining mobile terminals 100b to 100n act as slave mobile terminals that receive an incomplete composite photograph and insert a taken picture into the incomplete composite photograph. The mobile terminal 100n acts as a mobile terminal that produces a final composite photograph by inserting a taken picture into the incomplete composite photograph. [0039]In composite shot mode, the first mobile terminal 100a, which acts as the master mobile terminal, takes a picture, prepares an incomplete composite photograph by inserting the taken picture into a photo-section of the incomplete composite photograph, and generates a list of mobile terminals participating in composite photographing (i.e. a participant list including the mobile terminals 100b to 100n). Then, the first mobile terminal 100a selects a slave mobile terminal in the participant list, for example the second mobile terminal 100b, and sends the incomplete composite photograph, participant list and sender terminal information on the first mobile terminal 100a through the MMSC 200 to the second mobile terminal 100b. Upon reception, the second mobile terminal 100b takes a picture and inserts the taken picture into a photo-section of the received incomplete composite photograph. When the resulting composite photograph has an empty photo-section (i.e. still incomplete), the second mobile terminal 100b selects another mobile terminal in the participant list, for example the third mobile terminal 100c, and sends the incomplete composite photograph, participant list and sender terminal information on the first and second mobile terminals 100a and 100b through the MMSC 200 to the third mobile terminal 100c. [0040]Finally after repeating similar steps, the n-th mobile terminal 100n takes a picture, obtains a complete composite photograph by inserting the picture into a photo-section of the incomplete composite photograph, and sends the complete composite photograph through the MMSC 200 to the mobile terminals 100a to 100n−1 in the participant list. [0041]The mobile terminals 100a to 100n are connected to the MMSC 200 through a mobile communication network 300. The mobile communication network 300 is a wired/wireless communication network, and may be a network using telephone lines, coaxial cables or optical fibers, a packet switched network, an Integrated Services Digital Network (ISDN), a broadband-ISDN, and the like. [0042]The MMSC 200 is a message service system that can provide not only basic services including voice messages and short text messages but also various multimedia services including Internet electronic mails. The MMSC 200 receives a composite photograph from a mobile terminal and sends the received composite photograph to another mobile terminal. The MMSC 200 includes an MMS server 201 and a subscriber database 203. [0043]The MMS server 201 defines roles of components in the MMSC 200, and controls the components. The MMS server 201 handles and stores MMS messages to be transmitted. The subscriber database 203 contains subscriber specific information, and provides information on delivery and rendering schemes for MMS messages. The subscriber specific information may include subscription information and addressing information of users or subscribers. The MMSC 200 may further include an MMS relay for transferring messages between different messaging systems, an MMS message storage for storing messages, and an MMS user agent for displaying final results of a process in the MMS architecture. [0044]Next, a description is given of a mobile terminal for composite photographing. FIG. 2 is a block diagram illustrating a mobile terminal capable of producing a composite photograph according to an exemplary embodiment of the present invention. [0045]Referring to FIG. 2, the mobile terminal includes a camera unit 101, image processing unit 103, display unit 105, communication unit 107, key input unit 109, storage unit 111, and control unit 113. [0046]The camera unit 101 captures an image of a target object and generates a corresponding image signal. The camera unit 101 includes a lens for forming an image, an image sensor for converting an optical signal corresponding to the formed image into an electrical signal, and an image signal processor for converting the analog electrical signal from the image sensor into digital data. More particularly, when in composite shot mode, the camera unit 101 takes a picture to be inserted into a photo-section of a multi-photo frame. The camera unit 101 may take one or more pictures for the multi-photo frame. [0047]The image processing unit 103 generates screen data to display an image signal from the camera unit 101. The image processing unit 103 includes an image codec to compress image data in a preset format or to decompress compressed image data, for display on the display unit 105. [0048]The display unit 105 displays various information related to the state and operation of the mobile terminal. In particular, the display unit 105 displays a screen for a composite photograph during a composite shot mode. The composite photograph may include an image or characters related to an image. In an exemplary embodiment, for a composite photograph, the composite shot mode is entered after activation of the camera unit 101, a multi-photo framing function is selected during composite shot mode, and a picture of a target object is taken. That is, the display unit 105 displays a multi-photo frame during the composite shot mode. The display unit 105 displays a picture that was taken for a photo-section of the multi-photo frame according to a user input. A master mobile terminal initiating composite photographing displays a participant list screen on the display unit 105. [0049]A slave mobile terminal displays a received composite photograph on the display unit 105, and displays, if the received composite photograph is incomplete, an image composition screen according to a user input. That is, the display unit 105 displays a picture that was taken for a selected photo-section of the multi-photo frame. [0050]As described further below, when the communication unit 107 is a short-range wireless module such as a Bluetooth module, in order to send a composite photograph, the display unit 105 displays a list of Bluetooth device addresses found by inquiry and response procedures between Bluetooth-enabled devices. After issuing a remote name request, if remote names of the found devices are available, the display unit 105 displays a list of the remote names. [0051]The communication unit 107 can be implemented as at least one of an RF module and a short-range wireless module to establish a wireless channel. FIGS. 3 and 5 are related to the composite photographing method in the case of the communication unit 107 being implemented as an RF module, and FIG. 6 is related to the composite photographing method in the case of the communication unit 107 being implemented as a short-range wireless module such as a Bluetooth module. The communication unit 107 may be implemented to include both an RF module as a first unit and a short-range wireless module as a second unit. [0052]When the communication unit 107 is implemented as an RF module, it includes an RF transmitter for upconverting the frequency of a signal to be transmitted and amplifying the signal, and an RF receiver for low-noise amplifying a received signal and downconverting the frequency of the received signal. [0053]When the communication unit 107 is implemented as a short-range wireless module, for example, a Bluetooth module, it can connect to a Bluetooth-enabled device through Bluetooth communication. The short-range wireless module may be any wireless module that can establish a short-range wireless channel for signal exchange, such as a Bluetooth module, IrDA module or Zigbee module. [0054]The Bluetooth protocol operates in the Industrial, Scientific and Medical (ISM) band of 2.4 GHz, and this ISM band is a license-free band. Bluetooth employs a 2 MHz wide lower guard band and a 3.5 MHz wide upper guard band to reduce interference. Bluetooth uses frequency hopping with a hopping rate of 1600 hops per second. [0055]The Bluetooth module collects information on discovered Bluetooth-enabled devices. The collected information may include a Bluetooth address (BD_ADDR), which is a device specific address, device class, page scan repetition mode, and clock offset of a connectable device. By issuing a remote name request to each discovered device, the Bluetooth module may receive a user friendly name of the discovered device as a reply. [0056]The key input unit 109 receives an input signal from the user for controlling the operation of the mobile terminal. In particular, the key input unit 109 receives user input signals for selecting the composite shot mode, composing a composite photograph, activating the camera unit 101, selecting a multi-photo frame, taking a picture of a target object, generating a participant list, and selecting a mobile terminal to which the composite photograph is to be sent. [0057]The storage unit 111 stores programs and data necessary for the operation of the mobile terminal. In particular, the storage unit 111 includes a photo-frame section 211 for the composite shot mode after activation of the camera unit 101. The photo-frame section 211 stores composite photographs in the form of a multi-photo frame, as illustrated in FIG. 4A, which includes multiple photo-sections each accommodating a picture. Multi-photo frames may be pre-stored in the storage unit 111 at the manufacturing process, or may be received from the outside. [0058]The control unit 113 controls overall operations of components in the mobile terminal. In particular, the control unit 113 controls the composite photographing function based on multiple mobile terminals. For the first mobile terminal 100a, the control unit 113 composes an incomplete composite photograph and generates a participant list. Here, composition of an incomplete composite photograph indicates insertion of a taken picture into at least one photo-section of a given multi-photo frame during the composite shot mode. This involves selection of a multi-photo frame as illustrated in FIG. 4A, and insertion of a taken picture into a photo-section as illustrated in FIG. 4B. The control unit 113 sends the incomplete composite photograph to a selected mobile terminal in the participant list. [0059]For the second mobile terminal 100b, in response to reception of an incomplete composite photograph, participant list and sender terminal information, the control unit 113 further composes the incomplete composite photograph. After the composition, the incomplete composite photograph may become complete without an empty photo-section in the multi-photo frame, or may remain incomplete with an empty photo-section. When the composite photograph is complete, the control unit 113 sends the complete composite photograph to all the mobile terminals in the participant list, for example, the first mobile terminal 100a. If the composite photograph remains incomplete, the control unit 113 sends the incomplete composite photograph, participant list, and sender terminal information on the first and second mobile terminals 100a and 100b to another mobile terminal in the participant list that has not yet participated in the composite photographing. [0060]For the n-th mobile terminal 100n, in response to reception of an incomplete composite photograph, participant list and sender terminal information, the control unit 113 further composes the incomplete composite photograph. When the composite photograph is complete, the control unit 113 sends the complete composite photograph to all the mobile terminals in the participant list. Here, completeness of a composite photograph may be determined by determining the presence of an empty photo-section in the multi-photo frame. The mobile terminals in the participant list are those mobile terminals that have participated in composite photographing. [0061]When the communication unit 107 is a Bluetooth module, in order to send a composite photograph, the control unit 113 activates the Bluetooth module and controls the Bluetooth module to issue an inquiry to find a Bluetooth-enabled mobile terminal. If a response is received, the Bluetooth module issues a remote name request to the discovered mobile terminal. Upon reception of a response, the control unit 113 lists the user friendly name of the discovered mobile terminal on the display unit 105. Thereafter, the control unit 113 selects one of listed mobile terminals, performs pairing with the selected mobile terminal, establishes a Bluetooth connection to the selected mobile terminal, and sends the composite photograph. [0062]Next, a description is given of a composite photographing method using multiple mobile terminals. FIGS. 3 and 5 are related to the case where the communication unit is implemented as an RF module. FIG. 3 is a sequence diagram of a first composite photographing method using mobile terminals based on RF communication according to an exemplary embodiment of the present invention. FIGS. 4A to 4D are screen representations illustrating steps in the first composite photographing method according to an exemplary embodiment of the present invention. [0063]Referring to FIG. 3, the first mobile terminal 100a composes an MMS message containing a composite photograph, generates a participant list, and selects the second mobile terminal 100b in step S301. In this step, the first mobile terminal 100a composes an incomplete composite photograph. That is, the first mobile terminal 100a inserts a picture that was taken into at least one photo-section of a given multi-photo frame during a composite shot mode. A screen for a composed composite photograph is illustrated in FIG. 4B. The first mobile terminal 100a selects a multi-photo frame as illustrated in FIG. 4A, takes a facial picture of the user or another person, and inserts the picture into a first photo-section 10 as illustrated in FIG. 4B. [0064]Then, the first mobile terminal 100a generates a list of mobile terminals carried by participants of the composite photographing. The participants may be family members of the user of the first mobile terminal 100a. To produce a family photograph for family members at distinct locations, the user of the first mobile terminal 100a takes the facial picture as illustrated in FIG. 4B, generates a participant list of mobile terminals carried by family members, and selects a mobile terminal, for example the second mobile terminal 100b, in the participant list. The participant list may be made through a menu or option key available after composition of the composite photograph. [0065]Thereafter, the first mobile terminal 100a sends, to the MMSC 200, the composed MMS message containing the composite photograph with a request for delivery of composed MMS message containing the composite photograph to the second mobile terminal 100b in step S303. The MMSC 200 sends a reply to the first mobile terminal 100a in step S305. [0066]The MMSC 200 sends an MMS notification to the second mobile terminal 100b in step S307, and the second mobile terminal 100b sends a reply to the MMSC 200 in step S309. [0067]The second mobile terminal 100b connects to the MMSC 200 in step S311, and retrieves the corresponding MMS message together with the participant list and the sender terminal information on the first mobile terminal 100a in step S313. Here, the sender terminal information includes a telephone number of the first mobile terminal 100a. [0068]The second mobile terminal 100b further composes the received composite photograph, and selects the n-th mobile terminal 100n as the recipient for an MMS message containing the composed composite photograph in step S315. The composite photograph composed at this step is illustrated in FIG. 4C. That is, the second mobile terminal 100b receives the composite photograph with the non-empty first photo-section 10 as illustrated in FIG. 4B, and further composes the composite photograph by taking a facial picture and inserting the picture into a second photo-section 20 of the composite photograph as illustrated in FIG. 4C. The second mobile terminal 100b selects the n-th mobile terminal 100n in the participant list as the recipient for the composed composite photograph. [0069]The second mobile terminal 100b sends, to the MMSC 200, an MMS message containing the composite photograph with a request for delivery of the MMS message containing the composite photograph to the n-th mobile terminal 100n in step S317. The MMSC 200 sends a reply to the second mobile terminal 100b in step S319. [0070]The MMSC 200 sends an MMS notification to the n-th mobile terminal 100n in step S321, and the n-th mobile terminal 100n sends a reply to the MMSC 200 in step S323. [0071]The n-th mobile terminal 100n connects to the MMSC 200 in step S325, and retrieves the corresponding MMS message together with the participant list and the sender terminal information on the first and second mobile terminals 100a and 100b in step S327. In the participant list, each listed mobile terminal may have a checkbox. When the second mobile terminal 100b further composes a composite photograph as described above, it can place a checkmark in the associated checkbox and send the composed composite photograph and the participant list to the n-th mobile terminal 100n. In other words, after a mobile terminal further composes a composite photograph, the mobile terminal places a checkmark in the associated checkbox of the partici(String), 优先 [0001] 此申请根据 35 U.S.C. 2008 年 7 月 2 日向韩国知识产权局提交并转让序列号 10-2008-0063874 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动终端。 更具体地,本发明涉及一种移动终端和使用多个移动终端的合成拍摄方法,其中不同位置的多个移动终端可以共同产生合成照片。 [0004] 2.相关技术的描述 [0005] 随着电子元件越来越小、越来越轻,现代移动终端越来越小型化。 除了基本的呼叫处理功能外,为了满足多样化的用户需求,市售的移动终端还具有包括相机相关功能在内的各种高级功能。 [0006] 配备相机的移动终端可以提供多种拍摄模式,包括静止拍摄、连拍、合成拍摄、夜拍、自拍和视频拍摄。 更具体地说,在合成照片中,拍摄几张照片并将其组合成一张合成照片。 这里,多张图片是由同一个移动终端拍摄的。 即,可以使用单个移动终端来产生合成照片。 为了产生由几个人的照片组成的合成照片,这些人可能必须出现在相同的地点和时间。 [0007] 在复合拍摄模式下,可以使用多张照片取景功能从多张单独拍摄的照片中生成一张照片。 要使用多照片取景功能,这些照片必须由同一个移动终端拍摄,并且如果这些照片与人有关,则这些人可能必须在相同的地点和时间出现。 发明内容 [0008] 本发明的一个方面是解决上述问题和/或缺点并提供至少所描述的优点。 因此,本发明的一个方面是提供一种移动终端和合成拍摄方法,使得多个移动终端能够共同产生合成照片。 [0009] 本发明的另一方面在于提供一种移动终端和一种合成拍摄方法,其通过利用短距离无线通信来传输用于合成拍摄的图片来降低通信成本。 [0010] 根据本发明的一个方面,提供了一种使用多个移动终端的合成拍摄方法。 该方法包括:主移动终端合成不完整的合成照片;主移动终端生成从移动终端的参与者列表;主移动终端将不完整的合成照片和参与者列表发送到第一 参与者列表中的从移动终端,第一从移动终端接收不完整的合成照片和参与者列表,第一从移动终端进一步合成接收到的合成照片,第一从移动终端确定是否 合成照片完成时,第一从移动终端在合成照片不完整时,将合成照片发送给参与者列表中的第二从移动终端,当合成照片完成时,发送, 由第一从移动终端将合成的合成照片发送给所有具有同等水平的移动终端 参与复合摄影。 [0011]根据本发明的另一方面,提供了一种使用多个移动终端的合成拍摄方法。 该方法包括由主移动终端合成一张不完整的合成照片,由主移动终端生成一个或多个从移动终端的参与者列表,由主移动终端设置从移动终端的照片片段信息。 移动终端,主移动终端向参与者列表中的从移动终端发送不完整的合成照片和照片部分信息,每个从移动终端接收不完整的合成照片和照片部分信息,进一步 每个从移动终端利用照片片段信息对接收到的合成照片进行合成,每个从移动终端将合成的合成照片发送到主移动终端,并由主移动终端组合, 将从移动终端接收到的不完整的合成照片组合成一张完整的合成照片。 [0012] 根据本发明的又一方面,提供了一种移动终端。 该终端包括用于合成照片并生成参与者列表的输入单元、用于发送合成照片和参与者列表的通信单元、以及用于将合成的不完整合成照片和参与者列表发送到第一移动设备的控制单元 所述参与者列表中的终端, 用于在接收到不完整的合成照片时, 将接收到的合成照片进一步合成, 用于在合成的合成照片不完整时, 将合成的合成照片发送到参与者列表中的第二移动终端, 以及 当合成的合成照片完成后,将合成的合成照片发送给所有参与合成拍摄的移动终端。 [0013] 根据本发明的又一方面,提供了一种移动终端。 该终端包括:输入单元,用于合成照片,生成参与者列表,以及设置照片部分信息,将合成照片的照片片段分配给参与者列表中的不同移动终端;通信单元,用于发送合成照片 以及照片片段信息,以及控制单元,用于在接收到来自第一移动终端的不完整合成照片时,将不完整合成照片和照片片段信息发送到参与者列表中的一个或多个移动终端,以进行进一步合成 ,接收的合成照片,用于将合成的合成照片发送给第一移动终端,用于在接收到与已发送的不完整的合成照片匹配的不完整的合成照片后,将接收到的不完整的合成照片组合成完整的合成照片。 [0014] 在本发明示例性实施例的一个特征中,不同位置的几个用户可以共同产生合成照片,从而提高用户便利性。 例如,当居住在不同地点的家庭成员想要拍摄家庭照片时,携带移动终端的第一成员可以选择多相框,拍摄面部图像,将面部图像插入到多相框的照片部分中。 相框,并可以将多相相框发送给携带移动终端的第二成员。 然后,第二成员可以拍摄人脸图像,将该人脸图像插入到多相框的另一个照片部分中,并可以将多相框发送给携带移动终端的第三成员。 这个过程可以继续进行,直到制作出最终的全家福。 [0015] 另外,可以使用蓝牙等短距离无线通信来传输合成照片的组成图像,从而降低通信成本。 [0016] 本发明的其他方面、优点和显着特征对于本领域技术人员来说将从以下详细描述中变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0017]本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0018] 图1图示了根据本发明示例性实施例的用于合成拍摄的移动终端之间的通信。 [0019] 图2是示出根据本发明示例性实施例的能够产生合成照片的移动终端的框图; [0020] 图3是根据本发明示例性实施例的使用基于射频(RF)通信的移动终端的第一合成拍摄方法的时序图; [0021] 图4A至4D是示出根据本发明示例性实施例的第一合成拍摄方法中的步骤的屏幕表示; [0022] 图5是示出根据本发明示例性实施例的基于RF通信的第一合成拍摄方法的流程图; [0023] 图6是根据本发明示例性实施例的基于短距离无线通信的第一合成拍摄方法的时序图; [0024] 图7是根据本发明示例性实施例的基于RF通信的使用移动终端的第二合成拍摄方法的时序图; [0025] 图8A至8D是示出根据本发明示例性实施例的第二合成拍摄方法中的步骤的屏幕表示; [0026] 图9A和图9B示出了根据本发明示例性实施例的在执行第二合成拍摄方法期间发送的分量图像; [0027] 图10是示出根据本发明示例性实施例的基于RF通信的第二合成拍摄方法的流程图; 和 [0028] 图11是根据本发明示例性实施例的基于短距离无线通信的第二合成拍摄方法的时序图。 [0029] 在整个附图中,应当注意,相似的附图标记用于描绘相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0030] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,省略了对众所周知的功能和结构的描述。 [0031] 以下描述和权利要求中使用的术语和词语不限于书目含义,而是仅由发明人使用以实现对本发明的清晰和一致的理解。 因此,本领域技术人员应该清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0032] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0033]为了描述的目的,在本发明的示例性实施例中使用移动终端作为示例,然而本发明不限于此。 本发明示例性实施例的移动终端为方便用户使用的终端,可以是任何信息通信设备或多媒体设备,例如移动终端、手机、有线/无线电话、便携式多媒体播放器(PMP)、 个人数字助理 (PDA)、智能手机和 MP3 播放器。 移动终端可以包括射频模块和短程通信模块之一或两者。 尽管本文将蓝牙模块描述为作为示例的短距离通信模块,但是可以使用任何其他短距离通信模块。 [0034] 图1图示了根据本发明示例性实施例的用于合成拍摄的移动终端之间的通信。 [0035] 参见图1,该组件图像传输和合成照片制作系统包括多个移动终端 100 a 至 100 n , 和一个多媒体信息服务中心 (MMSC) 200 . 在图1中,每个移动终端 100 a 至 100 n 包括一个通信单元( 107 在图 2) 中,它是用射频 (RF) 模块实现的。 也就是说,移动终端 100 a 至 100 n 与 MMSC 通信 200 使用他们的射频模块。 在流动描述中,图1不应用于移动终端的情况 100 a 至 100 n 每个都包括一个用短距离无线模块实现的通信单元。 图1可以应用于移动终端的情况 100 a 至 100 n 每个都包括一个用短距离无线模块和RF模块实现的通信单元。 [0036] 移动终端 100 a 至 100 n 每个都可以拨打语音电话,使用短消息服务 (SMS)、多媒体消息服务 (MMS) 和增强型消息服务 (EMS),并包括一个用于播放所需歌曲的 MP3 播放器。 移动终端 100 a 至 100 n 每个都可以包括一个摄像头单元( 101 在图 2) 中拍摄目标物体的照片。 [0037] 移动终端之一 100 a 至 100 n 可以通过用于合成照片的照相机单元拍照,并将包含所拍照片的彩信发送给另一方。 即第一移动终端 100 a 发送到 MMSC 200 包含图片的MMS消息,请求将包含图片的MMS消息传送到第二移动终端 100 b . 多媒体信息中心 200 回复第一移动终端 100 a ,并向第二移动终端发送彩信通知 100 b . 第二个移动终端 100 b 向 MMSC 发送回复 200 , 连接到 MMSC 200 ,并检索对应的彩信和第一移动终端的信息 100 a. [0038] 在下面的描述中,第一移动终端 100 a 充当主移动终端,通过编写包含用于合成照片的图片和参与者列表的MMS消息来发起合成拍摄。 剩下的移动终端 100 b 至 100 n 作为从移动终端接收不完整的合成照片并将拍摄的照片插入到不完整的合成照片中。 移动终端 100 n 充当移动终端,通过将拍摄的照片插入到不完整的合成照片中来产生最终的合成照片。 [0039] 合拍模式下,第一款移动端 100 a,作为主移动终端,拍照,通过将拍摄的照片插入到不完整的合成照片的照片部分中来准备不完整的合成照片,并生成参与合成拍摄的移动终端列表(即参与者列表) 包括移动终端 100 b 至 100 n )。 那么,第一移动终端 100 a 在参与者列表中选择一个从移动终端,例如第二个移动终端 100 b ,并在第一移动终端上发送不完整的合成照片、参与者列表和发送者终端信息 100 a 通过 MMSC 200 到第二个移动终端 100 b . 第二个移动终端接收到 100 b 拍摄照片并将拍摄的照片插入接收到的不完整合成照片的照片部分。 当得到的合成照片有一个空的照片部分(即仍然不完整)时,第二移动终端 100 b 在参与者列表中选择另一个移动终端,例如第三个移动终端 100 c ,并在第一和第二移动终端上发送不完整的合成照片、参与者列表和发送者终端信息 100 a 和 100 b 通过 MMSC 200 到第三个移动终端 100 c. [0040] 最后重复类似步骤后,第n个移动终端 100 n 拍照,将图片插入到不完整的合成照片的照片部分,得到完整的合成照片,并通过MMSC发送完整的合成照片 200 到移动终端 100 a 至 100 n− 1 在参与者列表中。 [0041] 移动终端 100 a 至 100 n 连接到 MMSC 200 通过移动通信网络 300 . 移动通信网络 300 是有线/无线通信网络,可以是使用电话线、同轴电缆或光纤的网络、分组交换网络、综合业务数字网络(ISDN)、宽带-ISDN等。 [0042] 多媒体信息中心 200 是一个消息服务系统,不仅可以提供包括语音消息和短文本消息在内的基本服务,还可以提供包括互联网电子邮件在内的各种多媒体服务。 多媒体信息中心 200 从移动终端接收合成照片,并将接收到的合成照片发送到另一个移动终端。 多媒体信息中心 200 包括彩信服务器 201 和订户数据库 203 . [0043] 彩信服务器 201 定义 MMSC 中组件的角色 200 , 并控制组件。 彩信服务器 201 处理和存储要传输的 MMS 消息。 订户数据库 203 包含订户特定信息,并提供有关 MMS 消息的传递和呈现方案的信息。 订户特定信息可以包括订户信息和用户或订户的寻址信息。 多媒体信息中心 200 还可以包括用于在不同消息系统之间传输消息的MMS中继、用于存储消息的MMS消息存储器、以及用于显示MMS体系结构中处理的最终结果的MMS用户代理。 [0044] 接下来,描述用于合成拍摄的移动终端。 图2是示出根据本发明示例性实施例的能够产生合成照片的移动终端的框图。 [0045] 参考图2,移动终端包括相机单元 101 , 图像处理单元 103 , 显示单元 105 , 通讯单元 107 , 按键输入单元 109 , 存储单元 111 , 和控制单元 113 . [0046] 相机单元 101 捕获目标物体的图像并生成相应的图像信号。 相机单元 101包括用于形成图像的镜头、用于将与形成的图像对应的光信号转换为电信号的图像传感器、以及用于将来自图像传感器的模拟电信号转换为数字数据的图像信号处理器。 更具体地说,当处于复合拍摄模式时,相机单元 101 拍摄要插入到多相框的照片部分的照片。 相机单元 101 可以为多相框拍摄一张或多张照片。 [0047] 图像处理单元 103 生成屏幕数据以显示来自相机单元的图像信号 101 . 图像处理单元 103 包括图像编解码器,用于以预设格式压缩图像数据或解压缩压缩的图像数据,以在显示单元上显示 105 . [0048] 显示单元 105 显示与移动终端的状态和操作相关的各种信息。 特别是显示单元 105 在合成拍摄模式期间显示合成照片的屏幕。 合成照片可以包括图像或与图像相关的字符。 在示例性实施例中,对于合成照片,在激活相机单元之后进入合成拍摄模式 101 ,在合成拍摄模式下选择多照片取景功能,对目标物体进行拍照。 也就是显示单元 105 在合成拍摄模式中显示多张相框。 显示单元 105 显示根据用户输入为多相框的照片部分拍摄的照片。 发起合成拍摄的主移动终端在显示单元上显示参与者列表屏幕 105 . [0049] 从移动终端在显示单元上显示接收到的合成照片 105 ,并且如果接收到的合成照片不完整,则根据用户输入显示图像合成屏幕。 也就是显示单元 105 显示为多相框的选定照片部分拍摄的照片。 [0050] 如下文进一步描述的,当通信单元 107 是蓝牙模块等短距离无线模块,为了发送合成照片,显示单元 105 显示通过蓝牙设备之间的查询和响应过程找到的蓝牙设备地址列表。 发出远程名称请求后,如果找到的设备的远程名称可用,则显示单元 105 显示远程名称列表。 [0051] 通讯单元 107 可以实现为RF模块和短距离无线模块中的至少一种以建立无线信道。 图3和图5涉及通信单元情况下的合成拍摄方法 107 以RF模块实现,图6为通信单元情况下的复合拍照方法 107 被实现为短距离无线模块,例如蓝牙模块。 通讯单元 107 可以实施为包括作为第一单元的RF模块和作为第二单元的短距离无线模块。 [0052] 当通讯单元 107 被实现为RF模块,它包括用于对要发送的信号的频率进行上变频和放大信号的RF发射器,以及用于对接收信号进行低噪声放大和对接收信号的频率进行下变频的RF接收器。 [0053] 当通讯单元 107 被实现为短距离无线模块,例如蓝牙模块,它可以通过蓝牙通信连接到具有蓝牙功能的设备。 近距离无线模块可以是蓝牙模块、IrDA模块或Zigbee模块等任何能够建立近距离无线信道进行信号交换的无线模块。 [0054] 蓝牙协议在 2.4 GHz 的工业、科学和医疗 (ISM) 频段中运行,该 ISM 频段是免许可频段。 蓝牙采用 2 MHz 宽的下保护频带和 3.5 MHz 宽的上保护频带来减少干扰。 蓝牙使用跳频,跳频为每秒 1600 跳。 [0055]蓝牙模块收集有关发现的蓝牙设备的信息。 收集的信息可以包括蓝牙地址(BD_ADDR),它是设备特定地址、设备类别、页面扫描重复模式和可连接设备的时钟偏移。 通过向每个发现的设备发出远程名称请求,蓝牙模块可以接收发现的设备的用户友好名称作为回复。 [0056] 按键输入单元 109 接收来自用户的输入信号,用于控制移动终端的操作。 特别是按键输入单元 109 接收用于选择合成拍摄模式、合成照片、激活相机单元的用户输入信号 101 ,选择多相框,对目标对象进行拍照,生成参与者列表,选择要发送合成照片的移动终端。 [0057] 存储单元 111 存储移动终端操作所需的程序和数据。 特别是存储单元 111 包括一个相框部分 211 用于激活相机单元后的合成拍摄模式 101 . 相框部分 211 如图4A所示,它以多相框的形式存储合成照片,其包括多个照片部分,每个照片部分容纳一张图片。 多张相框可预先存储在存储单元中 111 在制造过程中,或可能从外部接收。 [0058] 控制单元 113 控制移动终端中组件的整体操作。 特别是控制单元 113 控制基于多个移动终端的合成拍照功能。 对于第一个移动终端 100 a , 控制单元 113 合成一张不完整的合成照片并生成参与者列表。 这里,不完整合成照片的合成表示在合成拍摄模式期间将拍摄的照片插入给定多照片帧的至少一个照片部分。 这包括选择如图4A所示的多照片帧,以及将拍摄的图片插入到如图4B所示的照片部分中。 控制单元 113 将不完整的合成照片发送到参与者列表中选定的移动终端。 [0059] 对于第二个移动终端 100 b ,响应于接收到不完整的合成照片、参与者列表和发送者终端信息,控制单元 113 进一步构成不完整的合成照片。 在合成之后,不完整的合成照片可能在多相框中没有空白的照片部分而变得完整,或者可能保持不完整的有空白的照片部分。 合成照片完成后,控制单元 113 将完整的合成照片发送给参与者列表中的所有移动终端,例如第一台移动终端 100 a . 如果合成照片仍然不完整,控制单元 113 在第一和第二移动终端上发送不完整的合成照片、参与者列表和发送者终端信息 100 a 和 100 b 发送到参与者列表中尚未参与合成拍摄的另一个移动终端。 [0060] 对于第n个移动终端 100 n ,响应于接收到不完整的合成照片、参与者列表和发送者终端信息,控制单元 113 进一步构成不完整的合成照片。 合成照片完成后,控制单元 113 将完整的合成照片发送到参与者列表中的所有移动终端。 这里,可以通过确定多照片帧中是否存在空白照片部分来确定合成照片的完整性。 参与列表中的移动终端为参与过合成拍摄的移动终端。 [0061] 当通讯单元 107 是蓝牙模块,为了发送合成照片,控制单元 113激活蓝牙模块并控制蓝牙模块发出查询以查找具有蓝牙功能的移动终端。 如果接收到响应,蓝牙模块向发现的移动终端发出远程名称请求。 收到响应后,控制单元 113 在显示单元上列出发现的移动终端的用户友好名称 105 . 此后,控制单元 113 选择列出的移动终端之一,与选择的移动终端进行配对,与选择的移动终端建立蓝牙连接,并发送合成照片。 [0062] 接下来,描述使用多个移动终端的合成拍摄方法。 图3和5与通信单元被实现为RF模块的情况有关。 图3是根据本发明示例性实施例的使用基于RF通信的移动终端的第一合成拍摄方法的时序图。 图4A至图4D是示出根据本发明示例性实施例的第一合成拍摄方法中的步骤的屏幕表示。 [0063] 参见图3,第一移动终端 100 a 撰写包含合成照片的彩信,生成参与者列表,并选择第二移动终端 100 b 在步骤 S 301 . 本步骤中,第一移动终端 100 a 构成一张不完整的合成照片。 即第一移动终端 100 a 插入在合成拍摄模式期间拍摄到给定多照片帧的至少一个照片部分的照片。 图4B示出了合成合成照片的屏幕。 第一个移动终端 100 a 选择如图4A所示的多相框,拍摄用户或其他人的面部照片,并将照片插入到第一照片部分 10 如图4B所示。 [0064] 那么,第一移动终端 100 a 生成合成拍摄参与者携带的移动终端列表。 参与者可以是第一移动终端用户的家庭成员 100 a . 为了为不同地点的家庭成员制作家庭照片,第一移动终端的用户 100 a 拍摄如图4B所示的人脸照片,生成家庭成员携带的移动终端的参与者列表,并选择移动终端,例如第二移动终端 100 b ,在参与者列表中。 可以通过合成照片合成后可用的菜单或选项键来制作参与者列表。 [0065] 此后,第一移动终端 100 a 发送到 MMSC 200 ,包含合成照片的合成MMS消息,请求将包含合成照片的合成MMS消息传送到第二移动终端 100 b 在步骤 S 303 . 多媒体信息中心 200 回复第一移动终端 100 a 在步骤 S 305 . [0066] 多媒体信息中心 200 向第二移动终端发送彩信通知 100 b 在步骤 S 307 ,以及第二个移动终端 100 b 向 MMSC 发送回复 200 在步骤 S 309 . [0067] 第二个移动终端 100 b 连接到 MMSC 200 在步骤 S 311 ,并在第一移动终端上检索相应的彩信以及参与者列表和发送者终端信息 100 a 在步骤 S 313 . 这里,发送方终端信息包括第一移动终端的电话号码 100 a. [0068] 第二个移动终端 100 b 进一步对接收到的合成照片进行构图,选择第n个移动终端 100 n 作为包含步骤 S 中合成的合成照片的 MMS 消息的接收者 315 . 该步骤合成的合成照片如图4C所示。 即第二移动终端100 b 接收具有非空第一照片部分的合成照片 10 如图4B所示,并进一步通过拍摄面部照片并将照片插入第二照片部分来构成合成照片 20 如图4C所示的合成照片。 第二个移动终端 100 b 选择第n个移动终端 100 n 在参与者列表中作为合成合成照片的接收者。 [0069] 第二个移动终端 100 b 发送到 MMSC 200 ,包含合成照片的MMS消息,请求将包含合成照片的MMS消息传送到第n个移动终端 100 n 在步骤 S 317 . 多媒体信息中心 200 向第二移动终端发送回复 100 b 在步骤 S 319 . [0070] 多媒体信息中心 200 向第n个移动终端发送彩信通知 100 n 在步骤 S 321 ,以及第n个移动终端 100 n 向 MMSC 发送回复 200 在步骤 S 323 . [0071] 第n个移动终端 100 n 连接到 MMSC 200 在步骤 S 325 ,并在第一和第二移动终端上检索相应的彩信以及参与者列表和发送者终端信息 100 a 和 100 b 在步骤 S 327 . 在参与者列表中,每个列出的移动终端都可以有一个复选框。 当第二个移动终端 100 b 再如上述合成一张合成照片,可以在相关的复选框打勾,将合成的合成照片和参与者列表发送给第n个移动终端 100 n . 换言之,移动终端进一步合成一张合成照片后,移动终端在参与者列表的相关复选框中打勾,并将参与者列表和合成照片都发送给下一个移动终端。 因此,接收到合成照片和参与者列表的下一个移动终端可以很容易地识别出参与合成拍摄的移动终端,并在参与者列表中选择要发送合成照片的下一个移动终端。 [0072] 第n个移动终端 100 n 将接收到的合成照片进一步合成,生成完整的合成照片,并在步骤S中选择参与者列表中的所有移动终端 329 . 在该步骤中完成的合成照片如图4D所示。 即第n个移动终端 100 n 接收具有非空第一和第二照片部分的合成照片 10 和 20 如图4C所示,并进一步通过拍摄面部照片并将照片插入第三照片部分来构成合成照片 30 如图 4D 所示的合成照片。 第n个移动终端 100 n 选择参与者列表中的所有移动终端(第一和第二移动终端 100 a 和 100 b ) 作为完整合成照片的接收者。 [0073] 第n个移动终端 100 n 发送到 MMSC 200 ,包含完整合成照片的MMS消息,并请求将包含完整合成照片的MMS消息传送到参与者列表中的所有移动终端(第一和第二移动终端 100 a 和 100 b ) 在步骤 S 331 . 多媒体信息中心 200 向第n个移动终端发送回复 100 n 在步骤 S 333 . [0074] 多媒体信息中心 200 向第一移动终端发送彩信通知 100 a 在步骤 S 335 和第二移动终端 100 b 在步骤 S 337 . 第一个移动终端 100 a 向 MMSC 发送回复 200 在步骤 S 339 ,以及第二个移动终端 100 b 向 MMSC 发送回复200 在步骤 S 341 . [0075] 第一个移动终端 100 a 连接到 MMSC 200 在步骤 S 343 , 并在步骤 S 中检索相应的 MMS 消息 347 . 第二个移动终端 100 b 连接到 MMSC 200 在步骤 S 345 , 并在步骤 S 中检索相应的 MMS 消息 349 . [0076] 在以上描述中,三个移动终端参与合成拍摄。 然而,本发明不限于此,参与的移动终端的数量可以根据给定的多照片帧中的照片片段的数量或参与列表中的条目的数量而变化。 此外,合成照片的产生不限于选择与多照片取景相关的特定功能。 [0077] 接下来,对使用多个移动终端的第一合成拍摄方法给出另一种描述。 图5是根据本发明示例性实施例的基于RF通信的使用移动终端的第一合成拍摄方法的流程图。 [0078] 参照图5,控制单元 113 第一个移动终端 100 a 确定是否在步骤 S 中发出了对合成拍摄模式的请求 361 . 在合成拍摄模式下,相机单元 101 如图4A所示,激活并显示多相框。 [0079] 当发出合成拍摄模式的请求时,控制单元 113 编写包含合成照片的 MMS 消息,并在步骤 S 中生成参与者列表 363 . 本步骤,如图4B所示,第一移动终端 100 a 通过将图片插入第一个照片部分来组成不完整的合成照片 10 给定的多相框。 参与者列表是参与合成拍摄的移动终端的列表。 [0080] 控制单元 113 判断步骤S中是否选择了参与者列表中的移动终端 365 . 假设用户选择了第二移动终端 100 b 作为合成照片的收件人。 如果没有选择移动终端,则控制单元 113 返回步骤 S 363 . [0081] 当第二个移动终端 100 b 被选中时,控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 请求将包含合成照片的MMS消息传送到第二移动终端 100 b 在步骤 S 367 . 控制单元 113 向MMSC发送参与者列表和发送者终端信息 200 在步骤 S 369 . [0082] 在步骤 S 未发出合成拍摄模式请求时 361 , 控制单元 113 判断步骤S中是否接收到包含合成照片的彩信 371 . 可以与合成照片一起接收参与者列表和发送者终端信息。 [0083] 当接收到包含合成照片的彩信时,控制单元 113 在步骤 S 中确定合成照片是否完成 373 . 如结合图3所述,接收到的合成照片可能是来自例如第二移动终端的不完整照片 100 b ,或者可以是完整的,例*自第n个移动终端 100 n . 控制单元 113 可以通过检测合成照片中是否存在空白照片部分(即多相框)来确定合成照片的完整性。 如果接收到的合成照片如在图 4D 的情况下是完整的,则控制单元 113 根据用户输入执行操作。 例如,控制单元 113 将接收到的合成照片存储在存储单元中 111 . [0084] 如果接收到的合成照片不完整,控制单元 113 进一步合成步骤S中的合成照片 375. 也就是说,如果接收到的合成照片不完整,如图 4B 的情况,或者 4 C、控制单元 113 激活相机单元 101 拍照,将图片插入合成照片的空白照片部分,并存储合成照片。 [0085] 控制单元 113 确定在步骤S中是否发出传输合成合成照片的请求 377 . 如果发出传输请求,控制单元 113 在步骤S中确定合成的合成照片是否完整 379 . 如结合图3所述,在步骤S合成的合成照片 375 例如,可能是来自第二移动终端的不完整的 100 b ,或者是完整的,例*自第n个移动终端 100 n . 即步骤S合成的合成照片 375 可以像图4C的情况那样不完整,或者像图4D的情况那样完整。 控制单元 113 当合成照片中不存在空白照片部分时,将合成照片视为完整照片。 [0086] 如果合成的合成照片不完整,控制单元 113 在参与者列表中选择一个移动终端,例如第n个移动终端 100 n , 在步骤 S 381 . 控制单元 113 当合成照片中存在空白照片部分时,认为合成照片不完整。 控制单元 113 在参与者列表中选择一个尚未参与合成拍摄的移动终端。 [0087] 控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 请求将包含合成照片的MMS消息传送到第n个移动终端 100 n 在步骤 S 383 , 并进入步骤 S 369 . [0088] 如果在步骤 S 合成的合成照片不完整 379 , 控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 在步骤S中请求向参与者列表中的所有移动终端发送包含合成照片的MMS消息 385 . 这里,假设参与者列表移动和发送者终端信息标识相同的移动终端。 当参与者列表移动和发送终端信息不标识相同的移动终端时,将完整的合成照片发送到发送终端信息标识的实际参与合成拍摄的移动终端。 参与者列表中的移动终端可能不参与合成拍摄。 [0089] 此后,控制单元 113 进入步骤 S 369 . [0090] 接下来,对使用多个移动终端的第一合成拍摄方法给出另一种描述。 图6是根据本发明示例性实施例的基于短距离通信的使用移动终端的第一合成拍摄方法的时序图。 在图6中,移动终端使用蓝牙通信作为短距离通信进行合成拍摄。 [0091] 参见图6,第一移动终端 100 a 合成一张不完整的合成照片,生成参与者列表,并在步骤S中激活蓝牙模块选择移动终端作为合成照片的接收者 401 . [0092] 第一个移动终端 100 a 列出获取的移动终端的远程名称,例如选择第二个移动终端 100 b 根据在步骤 S 中获得的远程名称在参与者列表中 403 . 第一个移动终端 100 a 启动蓝牙模块,发现启用蓝牙的移动终端,向发现的移动终端发出远程名称请求,从响应的移动终端获取远程名称,并显示获取的远程名称。 第一个移动终端 100 a 使用获取的远程名称,例如选择第二移动终端 100 b 在参与者列表中。 [0093] 第一个移动终端 100 a 与第二移动终端进行配对 100 b , 并在步骤 S 中建立蓝牙连接 405 . 第一个移动终端 100 a 在第一移动终端上发送合成照片、参与者列表和发送者终端信息 100 a 到第二个移动终端 100 b 在步骤 S 407 . [0094] 第二个移动终端 100 b 进一步对接收到的合成照片进行合成,并在步骤S中激活蓝牙模块传输合成的合成照片 409 . [0095] 第二个移动终端 100 b 列出获取的移动终端的远程名称,例如选择第n个移动终端 100 n 根据在步骤 S 中获得的远程名称在参与者列表中 411 . [0096] 第二个移动终端 100 b 与第n个移动终端进行配对 100 n , 并在步骤 S 中建立蓝牙连接 413 . 第二个移动终端 100 b 在第一和第二移动终端上发送合成照片、参与者列表和发送者终端信息 100 a 和 100 b 到第n个移动终端 100 n 在步骤 S 415 . [0097] 第n个移动终端 100 n 进一步对接收到的合成照片进行合成,并在步骤S中激活蓝牙模块传输合成的合成照片 417 . [0098] 第n个移动终端 100 n 列出获取的移动终端的远程名称,并根据步骤S中获取的远程名称选择参与者列表中的所有移动终端 419 . 这里,参与列表中的移动终端是参与过合成拍摄的移动终端(例如,第一移动终端和第二移动终端) 100 a 和 100 b )。 [0099] 第n个移动终端 100 n 与第二移动终端进行配对 100 b 并在步骤S中与其建立蓝牙连接 421 ,并将合成照片发送至第二移动终端 100 b 在步骤 S 425 . 第n个移动终端 100 n 与第一移动终端进行配对 100 a 并在步骤S中与其建立蓝牙连接 423 ,并将合成照片发送至第一移动终端 100 a 在步骤 S 427 . [0100] 接下来,描述使用多个移动终端的第二合成拍摄方法。 省略与第一合成拍摄方法的要素基本相同或对应的要素的描述。 [0101] 在第二种合成拍摄方法中,主移动终端向参与者列表中的一个或多个从移动终端发送合成照片,每个从移动终端进一步合成合成照片并将未完成的合成照片发送给主移动终端, 主移动终端将不完整的合成照片组合在一起成为最终的合成照片。 [0102] 返回参考图1,移动终端之一 100 a 至 100 n 可以通过摄像单元拍照形成初始合成照片,并将包含合成照片的彩信发送给另一方。 即第一移动终端 100 a 作为主机发送MMSC 200 包含合成照片的MMS消息,请求将包含合成照片的MMS消息传送到第二至第n个移动终端 100 b 至 100 n 充当奴隶。 这里,合成照片可以是第一形式,其具有填充有由第一移动终端拍摄的照片的照片部分 100 a (如图8B所示),或者在没有照片部分的第二种形式中,该照片部分填充了由第一移动终端拍摄的照片 100 a (如图 8A 所示)。 在发送合成照片的同时,还向第二至第n移动终端发送照片片段信息 100 b 至 100 n. [0103] 收到 MMS 消息后,MMSC 200 回复第一移动终端 100 a ,向第二至第n个移动终端发送彩信通知 100 b 至 100 n . 第二至第n移动终端中的每一个 100 b 至 100 n 向 MMSC 发送回复 200 , 连接到 MMSC 200 ,并检索对应的包含合成照片的彩信以及第一移动终端的发送方终端信息 100 a 和照片部分信息。 照片部分信息由第一移动终端给出 100 a ,并且表示接收移动终端(第二到第n移动终端)进入的合成照片(或多相框)的照片部分 100 b 至 100 n ) 是插入图片。 [0104] 第二至第n移动终端中的每一个 100 b 至 100 n 进一步对接收到的合成照片进行拍照,并将图片插入到照片片段信息所指示的合成照片的照片片段中。 第2至第n移动终端 100 b 至 100 n 将他们合成的合成照片发送到第一台移动终端 100 a ,然后将接收到的合成照片组合成一张完整的合成照片。 此后,第一移动终端 100 a 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n 参加过复合摄影。 [0105] 参考图2,通信单元 107 可以实现为RF模块和短距离无线模块中的至少一种。 图7和图10涉及在通信单元的情况下的第二合成拍摄方法 107 以RF模块实现,图11为通信单元情况下的第二种合成拍摄方法 107 被实现为像蓝牙模块一样的短距离无线模块。 [0106] 对于第一个移动终端 100 a 作为主机,控制单元 113 合成一张不完整的合成照片,生成参与者列表,并设置照片部分信息。 这里,不完整合成照片的合成表示在合成拍摄模式期间将拍摄的照片插入给定多照片帧的至少一个照片部分。 照片片段信息指定将图片插入到多相框的每个照片片段中的移动终端。 控制单元 113 将合成照片和照片片段信息发送至参与者列表中的至少一个从移动终端。 在从第二至第n移动终端接收合成照片时 100 b 至 100 n , 控制单元 113 将接收到的合成照片组合成一张完整的合成照片。 此后,控制单元 113 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n. [0107] 对于第二至第n个移动终端之一 100 b 至 100 n 作为从机,响应于接收到合成照片、参与者列表、照片部分信息和发送者终端信息,控制单元 113进一步对接收到的合成照片进行拍照,并将图片插入到照片片段信息所指示的合成照片的照片片段中。 控制单元 113 然后将合成的合成照片发送到第一移动终端 100 a ,即发件人。 [0108] 合成照片或多相框可以采用多种形式。 例如,第一种合成照片可以包括如图8B至8D所示的取景图像和拍摄的照片,第二种合成照片可以仅包括如图9A所示的拍摄的照片,而第三种合成照片可以 如图9B所示,在取景图像中包括拍摄的照片和相关的照片部分(未示出)。 [0109] 即,第一种合成照片作为多照片帧被传送,其照片部分包括如图8B至8D所示的拍摄照片。 如图9A所示,第二类型的合成照片作为包括在给定位置拍摄的照片而没有取景图像的多照片帧传送。 第二类合成照片作为具有相关照片部分信息的拍摄照片传输。 [0110] 在与图 8A 至 8D 以及图 9A 和 9B 相关的情况下,第一移动终端 100 a 将仅包括取景图像的合成照片发送到第二至第n移动终端 100 b 至 100 n . 即,在给定的多照片帧中,分配给第一移动终端的照片片段 100 a 是空的。 第二至第n移动终端中的每一个 100 b 至 100 n 将拍摄的照片插入接收到的多相框的指定照片部分。 当第一个移动终端 100 a 将在指定照片分区拍摄的多照片帧作为合成照片发送,第一移动终端拍摄的面部照片 100 a 应该出现在,例如,第一个照片部分 10 在图 8C 或 8 D. [0111] 接下来,描述使用多个移动终端的第二合成拍摄方法。 图7和10与通信单元被实现为RF模块的情况有关。 [0112] 图7是根据本发明示例性实施例的使用基于RF通信的移动终端的第二合成拍摄方法的时序图。 图8A至图8D是示出根据本发明示例性实施例的第二合成拍摄方法中的步骤的屏幕表示。 图9A和9B示出了根据本发明示例性实施例的可在移动终端之间传送的合成照片的形式。 [0113] 参见图7,第一移动终端 100 a 编写包含合成照片的彩信,生成参与者列表,并在步骤S中为参与者列表中的每个移动终端设置照片片段信息 501 . 本步骤中,第一移动终端 100 a 构成一张不完整的合成照片。 即第一移动终端 100 a 在合成拍摄模式期间,将拍摄的照片插入给定多照片帧的至少一个照片部分。 图8B示出了合成合成照片的屏幕。 第一个移动终端 100 a 选择如图8A所示的多照片帧,拍摄用户或其他人的面部照片,并将照片插入到第一照片部分 10 如图8B所示。 [0114] 那么,第一移动终端 100 a 生成合成拍摄参与者携带的移动终端列表。 可以通过合成照片合成后可用的菜单或选项键来制作参与者列表。 此外,第一款移动终端 100 a 通过在参与者列表中将单个照片部分分配给移动终端来设置照片部分信息。 例如,第一移动终端 100 a 可以选择如图 8A 所示的多相框,并分配第二个照片部分 20 和第三个照片部分 30 分别到第一移动终端 100 a 第n个移动终端 100 n . 可以通过可用于合成拍摄的菜单或选项键来分配照片部分。 [0115] 此后,第一移动终端 100 a 发送到 MMSC 200 ,包含合成照片的合成MMS消息,请求将包含合成照片的MMS消息传送到第二至第n个移动终端 100 b 至 100 n 在步骤 S 503 . [0116] 这里,如前所述,合成照片可以包括在分配给第一移动终端的照片部分的拍摄照片 100 a 如图8B所示,或者可以不包括如图8A所示的拍摄图片。 在下面的描述中,第一移动终端 100 a 将如图8A所示的仅包括取景图像的合成照片发送到第二至第n移动终端 100 b 至 100 n. [0117] 多媒体信息中心 200 回复第一移动终端 100 a 在步骤 S 505 . 多媒体信息中心 200 向第二至第n个移动终端发送彩信通知 100 b 至 100 n 在步骤 S 507 和 S 509 ,以及第二至第n个移动终端 100 b 至 100 n 向 MMSC 发送回复 200 在步骤 S 511 和 S 513 . [0118] 第2至第n移动终端 100 b 至 100 n 连接到 MMSC 200 在步骤 S 515 和 S 517 ,并在第一移动终端上检索相应的彩信以及照片片段信息和发送者终端信息 100 a 在步骤 S 519 和 S 521 . [0119] 第二至第n移动终端中的每一个 100 b 至 100 n 进一步对接收到的合成照片进行构图,选择第一移动终端 100 a 作为步骤 S 中的收件人 523 和 S 525 . 第二和第n个移动终端合成的不完整照片 100 b 和 100 n 在图8C和8D中示出。 即第二移动终端 100 b 通过将拍摄的照片插入第二个照片部分,进一步合成接收到的合成照片 20 如图8C所示,第n个移动终端 100 n 通过将拍摄的照片插入第三个照片部分,进一步合成接收到的合成照片 30 如图 8D 所示。 此后,第二至第n移动终端中的每一个 100 b 至 100 n 选择第一个移动终端 100 a 作为合成合成照片的接收者。 [0120] 第二至第n移动终端中的每一个 100 b 至 100 n 发送到 MMSC 200 ,包含合成照片的MMS消息,请求将包含合成照片的MMS消息传送到第一移动终端 100 a 在步骤 S 527 和 S 529 . 多媒体信息中心 200 向第二至第n个移动终端中的每一个发送回复 100 b 至 100 n 在步骤 S 531 和 S 533 . [0121] 多媒体信息中心 200 向第一移动终端发送彩信通知 100 a 在步骤 S 535 ,以及第一台移动终端 100 a 向 MMSC 发送回复 200 在步骤 S 537 . [0122] 第一个移动终端 100 a 连接到 MMSC 200 在步骤 S 539 , 并在步骤 S 中检索相应的 MMS 消息 541. 如前所述,在该步骤接收到的合成照片可以采用各种形式。 例如,第一种合成照片可以包括如图8B至8D所示的取景图像和拍摄的照片,第二种合成照片可以仅包括如图9A所示的拍摄的照片,而第三种合成照片可以 如图9B所示,在取景图像中包括拍摄的照片和相关的照片部分(未示出)。 [0123] 第一个移动终端 100 a 在步骤S中将接收到的合成照片组合成一张完整的合成照片 543 . 后来,第一个移动终端 100 a 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n 参加过复合摄影。 [0124] 在与步骤 S 相关的描述中 535 到 S 541 ,在 MMSC 之间进行一次彩信通知、回复、连接和彩信检索 200 和第一个移动终端 100 a . 每当 MMS 消息到达 MMSC 时,这些操作可能会执行一次 200 从第二个到第n个移动终端 100 b 至 100 n. [0125] 在以上描述中,三个移动终端参与合成拍摄。 然而,本发明不限于此,参与的移动终端的数量可以变化。 此外,合成照片的产生不限于选择与多照片取景相关的特定功能。 [0126] 接下来,给出使用多个移动终端的第二合成拍摄方法的另一描述。 图10是根据本发明示例性实施例的基于RF通信的使用移动终端的第二合成拍摄方法的流程图。 [0127] 参照图10,控制单元 113 第一个移动终端 100 a 确定是否在步骤 S 中发出了对合成拍摄模式的请求 561 . 在合成拍摄模式下,相机单元 101 如图8A所示,激活并显示多相框。 [0128] 当发出合成拍摄模式的请求时,控制单元 113 编写包含合成照片的彩信,生成参与者列表,并在步骤S中将合成照片的照片片段分配给参与者列表中的移动终端 563 . 在该步骤,如图8B所示,控制单元 113 通过将图片插入第一个照片部分来组成不完整的合成照片 10 . 参与者列表为参与合成拍摄的移动终端列表(第2至第n移动终端 100 b 至 100 n )。 控制单元 113 将合成照片的照片片段分配给第二至第n个移动终端 100 b 至 100 n . 例如,第二个照片部分 20 和第三个照片部分 20 分别分配给第二移动终端 100 b 和 n -th 移动终端 100 n. [0129] 控制单元 113 判断步骤S中是否发出转移请求 565 . 当发出传输请求时,控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 在步骤S中请求将包含合成照片的MMS消息传送到参与者列表中的移动终端 567 . 控制单元 113 将照片部分信息和发送者终端信息发送到MMSC 200 在步骤 S 569 . [0130] 在步骤 S 中未发出合成拍摄模式请求时 561 , 控制单元 113 判断步骤S中是否接收到包含合成照片的彩信 571 . 可以与合成照片一起接收照片片段信息和发送者终端信息。 [0131]当接收到合成照片时,控制单元 113 判断接收到的合成照片是否与步骤S中发送的合成照片匹配 573 . 如结合图7所述,第一移动终端 100 a 可将合成照片发送至第二至第n个移动终端 100 b 至 100 n ,然后从第二到第n个移动终端中的每一个接收进一步合成的合成照片 100 b 至 100 n. [0132] 如果接收到的合成照片与已发送的合成照片不匹配,则控制单元 113 进一步对步骤S中接收到的合成照片进行合成 575 . 如结合图7针对第二至第n移动终端所描述的 100 b 至 100 n ,第二至第n个移动终端中的每一个 100 b 至 100 n 可以接收如图8A所示的合成照片,并进一步合成接收到的合成照片。 即第二移动终端 100 b 将拍摄的照片插入第二个照片部分 20 如图8C所示,第n个移动终端 100 n 将拍摄的照片插入第三个照片部分 30 如图 8D 所示。 [0133] 控制单元 113 确定在步骤S中是否发出传输合成合成照片的请求 577 . 如果发出传输请求,控制单元 113 向 MMSC 发送包含合成照片的 MMS 消息 200 在步骤S中请求将包含合成的合成照片的MMS消息传送到发送方移动终端 579 . 多媒体信息中心 200 在步骤S中将MMS消息传递给发送方移动终端 581 . 合成的合成照片是不完整的,如图 8B 或 8 C,并且可以采用如图 8B 所示的第一种类型中的一种或 8 C、第二类如图9A所示,第三类如图9B所示。 [0134] 如果接收到的合成照片与在步骤S中发送的合成照片匹配 573 , 控制单元 113 在步骤S中将多张接收到的合成照片组合成一张完整的合成照片 583 . 如上所述,接收到的合成照片可以采取各种形式。 此后,控制单元 113 判断步骤S中是否发出完整合成照片的传输请求 585 . 如果发出传输请求,控制单元 113 向 MMSC 发送包含完整合成照片的 MMS 消息 200 请求将包含完整合成照片的MMS消息传递给在步骤S中参与合成拍摄的移动终端 587 . [0135] 接下来,给出使用多个移动终端的第二合成拍摄方法的另一描述。 在图11中,移动终端使用蓝牙通信进行合成拍摄。 图11是根据本发明示例性实施例的使用基于短距离通信的移动终端的第二合成拍摄方法的时序图。 在图11中,蓝牙通信将用作短距离通信的示例。 [0136] 参见图11,第一移动终端 100 a 合成一张不完整的合成照片,生成参与者列表,设置照片部分信息,并在步骤S中激活蓝牙模块选择移动终端作为合成照片的接收者 601 . 第一个移动终端 100 a 通过将合成照片的照片部分分配给参与者列表中的移动终端来设置照片部分信息。 可以通过可用于合成拍摄的菜单或选项键来分配照片部分。 第一个移动终端 100 a 激活蓝牙模块以选择移动终端作为合成照片的接收者。 [0137]第一个移动终端 100 a 列出获取的移动终端的远程名称,例如选择第2到第n个移动终端 100 b 至 100 n 根据在步骤 S 中获得的远程名称在参与者列表中 603 . 第一个移动终端 100 a 启动蓝牙模块,发现启用蓝牙的移动终端,向发现的移动终端发出远程名称请求,从响应的移动终端获取远程名称,并显示获取的远程名称。 第一个移动终端 100 a 使用获取的远程名称选择第二至第n个移动终端 100 b 至 100 n 在参与者列表中。 [0138] 第一个移动终端 100 a 与第二至第n个移动终端进行配对 100 b 至 100 n ,并在步骤 S 中与它们中的每一个建立蓝牙连接 605 和 S 607 . 第一个移动终端 100 a 在第一移动终端上发送合成照片、照片片段信息和发送者终端信息 100 a 到第2到第n个移动终端 100 b 至 100 n 在步骤 S 609 和 S 611 . [0139] 第二至第n移动终端中的每一个 100 b 至 100 n 进一步对接收到的合成照片进行合成,并在步骤S中激活蓝牙模块传输合成的合成照片 613 和 S 615 . 例如,第二个移动终端 100 b 通过将拍摄的照片插入第二个照片部分,进一步合成接收到的合成照片 20 如图8C所示,第n个移动终端 100 n 通过将拍摄的照片插入第三个照片部分,进一步合成接收到的合成照片 30 如图 8D 所示。 [0140] 第二至第n移动终端中的每一个 100 b 至 100 n 列出获取的移动终端远程名称,并选择发送方移动终端 100 a 在步骤 S 617 和 S 619 . 第二至第n移动终端中的每一个 100 b 至 100 n 与第一移动终端进行配对 100 a 并在步骤 S 中与其建立蓝牙连接 621 和 S 623 . 第二至第n移动终端中的每一个 100 b 至 100 n 将合成照片发送至第一移动终端 100 a 在步骤 S 625 和 S 627 . [0141] 第一个移动终端 100 a 在步骤S中将接收到的合成照片组合成一张完整的合成照片 629 . 后来,第一个移动终端 100 a 可以将完整的合成照片发送到第二到第n个移动终端 100 b 至 100 n 参加过复合摄影。 [0142] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如在 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101065339B1(String), KR1020100003847A(String), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101065339B1(String), KR1020100003847A(String), US20100004020A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101065339B1(String), KR1020100003847A(String), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271645(Integer), KR101065339B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271645(Integer), KR1020100003847A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271645(Integer), US20100004020A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:33.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100004020A1(String), US20100004020A1(String), 1262793600(Integer), 271645(Integer), 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.008 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185935(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185935(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1662111618(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25448(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185935(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25448(Integer), 2(Integer), 185935(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.262 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.262 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25448(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.315 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.315 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.315 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.369 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.370 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 放弃(String), 2(Integer), 185935(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160156760A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal alarm method and device, and mobile terminal(String), 移动终端报警方法、装置、移动终端(String), US20160156760A1(String), Disclosed is an alarm method for a mobile terminal. After a pre-alarm function of the mobile terminal is enabled, pre-alarm information is generated and output when an input operation performed on the mobile terminal is detected. Moreover, an alarm device for a mobile terminal, and the mobile terminal provided with the alarm device are disclosed. By the technical solution of the disclosure, automatic pre-alarm can be implemented for a smart mobile terminal; when the mobile terminal is operated accidentally, a notification can be given to a user at once, thus the security of the mobile terminal is ensured, and the user experience is improved; moreover, the structure of the mobile terminal does not need to be changed, and the production cost can be saved.(String), 本发明公开了一种移动终端的报警方法。 开启移动终端的预警功能后,当检测到对移动终端的输入操作时,生成并输出预警信息。 此外,还公开了一种移动终端的告警装置及具有该告警装置的移动终端。 通过本发明的技术方案,可以实现智能移动终端的自动预警; 当移动终端被误操作时,可以第一时间通知用户,保证了移动终端的安全,提高了用户体验。 并且不需要改变移动终端的结构,可以节省生产成本。(String), US14/771609(String), 1377446400(Integer), US20160156760A1(String), 1464796800(Integer), 美国(String), 2(Integer), CN(String), 6(Integer), 1(Integer), US20090298469A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.955 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.955 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:34.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185936(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b9596e65b8344ed98f0e746f06bcafcd.png(String), 185936(Integer), b9596e65b8344ed98f0e746f06bcafcd.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal alarm method and device, and mobile terminal(String), 移动终端报警方法、装置、移动终端(String), US20160156760A1(String), Disclosed is an alarm method for a mobile terminal. After a pre-alarm function of the mobile terminal is enabled, pre-alarm information is generated and output when an input operation performed on the mobile terminal is detected. Moreover, an alarm device for a mobile terminal, and the mobile terminal provided with the alarm device are disclosed. By the technical solution of the disclosure, automatic pre-alarm can be implemented for a smart mobile terminal; when the mobile terminal is operated accidentally, a notification can be given to a user at once, thus the security of the mobile terminal is ensured, and the user experience is improved; moreover, the structure of the mobile terminal does not need to be changed, and the production cost can be saved.(String), 本发明公开了一种移动终端的报警方法。 开启移动终端的预警功能后,当检测到对移动终端的输入操作时,生成并输出预警信息。 此外,还公开了一种移动终端的告警装置及具有该告警装置的移动终端。 通过本发明的技术方案,可以实现智能移动终端的自动预警; 当移动终端被误操作时,可以第一时间通知用户,保证了移动终端的安全,提高了用户体验。 并且不需要改变移动终端的结构,可以节省生产成本。(String), US14/771609(String), 1377446400(Integer), US20160156760A1(String), 1464796800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 6(Integer), 1(Integer), US20090298469A1(String), \20230420\b9596e65b8344ed98f0e746f06bcafcd.png(String), 20(Integer), 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.191 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 1. An alarm method for a mobile terminal, after a pre-alarm function of the mobile terminal is enabled, the method comprising:generating and outputting pre-alarm information when detecting that an input operation is performed on the mobile terminal.(String), 1.移动终端,带有报警装置包含:处理模块,用于开启移动终端的预警功能,当检测到移动终端有输入操作时,生成预警信息;和输出模块,用于输出预警信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 2. The alarm method for a mobile terminal according to claim 1, before the pre-alarm function of the mobile terminal is enabled, the method further comprising:setting the pre-alarm function for the mobile terminal.(String), 12.根据权利要求2所述的移动终端的报警方法,其中为移动终端设置预警功能包括:创建预警功能菜单,在预警功能菜单中设置预警功能开关,并设置预警输出方式;其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 3. The alarm method for a mobile terminal according to claim 1, wherein setting the pre-alarm function for the mobile terminal comprises:creating a pre-alarm function menu, setting a pre-alarm function switch in the pre-alarm function menu and setting a pre-alarm output way;wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 13.根据权利要求12所述的移动终端的报警方法,其中检测到移动终端有输入操作时,生成并输出预警信息,包括:当检测到移动终端的触摸屏或功能键被按下或检测到移动终端的应用程序输入了启用指令时,生成预警信息,并根据设置输出预警信息预报警输出方式。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 4. The alarm method for a mobile terminal according to claim 3, wherein generating and outputting pre-alarm information when detecting that the input operation is performed on the mobile terminal comprises:when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal, generating the pre-alarm information, and outputting the pre-alarm information according to the set pre-alarm output way.(String), 14.根据权利要求7所述的移动终端报警装置,其中设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 5. The alarm method for a mobile terminal according to claim 1, further comprising:setting a pre-alarm area on a touch screen of the mobile terminal; andwhen the pre-alarm function is not enabled, enabling the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, disabling the pre-alarm function when detecting that the pre-alarm area is clicked; or, counting clicking times of continuously clicking the pre-alarm area, and enabling or disabling the pre-alarm function by counting the clicking times.(String), 15.根据权利要求14所述的移动终端报警装置,其中处理模块用于在检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用的启用指令时,生成预警信息。相应的,输出模块用于根据设置的预警输出方式输出预警信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 6. An alarm device for a mobile terminal, comprising a processing module and an output module, whereinthe processing module is configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; andthe output module is configured to output the pre-alarm information.(String), 16.根据权利要求11所述的移动终端,其中报警装置还包括设置模块,用于设置移动终端的预警功能。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 7. The alarm device for a mobile terminal according to claim 6, further comprising a setting module which is configured to set the pre-alarm function for the mobile terminal.(String), 17.根据权利要求11所述的移动终端,其中设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 8. The alarm device for a mobile terminal according to claim 6, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 18.根据权利要求16所述的移动终端,其中设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息不同于移动终端的来电或短信提醒消息。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 9. The alarm device for a mobile terminal according to claim 8, wherein the processing module is configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal;and correspondingly, the output module is configured to output the pre-alarm information according to the set pre-alarm output way.(String), 19.根据权利要求17所述的移动终端,其中处理模块用于在检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用的启用指令时,生成预警信息。相应的,输出模块用于根据设置的预警输出方式输出预警信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 10. The alarm device for a mobile terminal according to claim 6, wherein the setting module is further configured to set a pre-alarm area on a touch screen of the mobile terminal; andcorrespondingly, when the pre-alarm function is not enabled, the processing module enables the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, the processing module disables the pre-alarm function when detecting that the pre-alarm area is clicked; or, the processing module counts clicking times of continuously clicking the pre-alarm area, and enables or disables the pre-alarm function by counting the clicking times.(String), 20.根据权利要求11所述的移动终端,其中设置模块还用于在移动终端的触摸屏上设置预警区域;和相应地,当预警功能未开启时,处理模块在检测到预警区域被点击时开启预警功能。当开启预警功能时,处理模块检测到预警区域被点击时,关闭预警功能。或者,处理模块统计连续点击预警区域的点击次数,通过统计点击次数来开启或关闭预警功能。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 11. A mobile terminal, provided with the alarm device which comprises:a processing module configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; andan output module configured to output the pre-alarm information.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 12. The alarm method for a mobile terminal according to claim 2, wherein setting the pre-alarm function for the mobile terminal comprises:creating a pre-alarm function menu, setting a pre-alarm function switch in the pre-alarm function menu and setting a pre-alarm output way;wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 13. The alarm method for a mobile terminal according to claim 12, wherein generating and outputting pre-alarm information when detecting that the input operation is performed on the mobile terminal comprises:when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal, generating the pre-alarm information, and outputting the pre-alarm information according to the set pre-alarm output way.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 14. The alarm device for a mobile terminal according to claim 7, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 15. The alarm device for a mobile terminal according to claim 14, wherein the processing module is configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal;and correspondingly, the output module is configured to output the pre-alarm information according to the set pre-alarm output way.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 16. The mobile terminal according to claim 11, wherein the alarm device further comprises a setting module which is configured to set the pre-alarm function for the mobile terminal.(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 17. The mobile terminal according to claim 11, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 18. The mobile terminal according to claim 16, wherein the setting module is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way,wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 19. The mobile terminal according to claim 17, wherein the processing module is configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal;and correspondingly, the output module is configured to output the pre-alarm information according to the set pre-alarm output way.(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185936(Integer), 20. The mobile terminal according to claim 11, wherein the setting module is further configured to set a pre-alarm area on a touch screen of the mobile terminal; andcorrespondingly, when the pre-alarm function is not enabled, the processing module enables the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, the processing module disables the pre-alarm function when detecting that the pre-alarm area is clicked; or, the processing module counts clicking times of continuously clicking the pre-alarm area, and enables or disables the pre-alarm function by counting the clicking times.(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185936(Integer), TECHNICAL FIELD [0001]The present disclosure relates to alarm technology, and more particularly to an alarm method and an alarm device for a mobile terminal, and the mobile terminal. BACKGROUND [0002]With the rapid development of the communication technology, user equipment becomes more and more popular. Particularly, a smart terminal, such as a smart phone, is more popular with users due to its fastness and convenience. Generally, the private information of a user, such as a bank card number and an ID number of a family member, is collected in the smart phone, which may bring convenience to the user but may also cause a security problem. When the smart phone is stolen or the private information is snooped, a loss may be caused to the user. [0003]At present, the following methods are adopted to ensure the security of information in the smart phone: a fingerprint identifier is built-in in the smart phone and the smart phone is started via the fingerprint of the user; or, the communication content, such as conversation and a short message, is encrypted and decrypted. Although the security of the information in the smart phone can be protected, the production cost of the smart phone may be increased undoubtedly by methods of arranging a fingerprint identifier in the smart phone which try to change the structure of the smart phone to achieve the aim of protecting the security of information. In terms of the method for ensuring the security by encrypting and decrypting the conversation content, interference information is usually added in a short message and cannot be found until the short message is decrypted successfully, thus, the waste of software and hardware processing resources of the smart phone is caused inevitably. SUMMARY [0004]In view of this, the main objective of the embodiments of the present disclosure is to provide an alarm method and device for a mobile terminal, and the mobile terminal, so as to implement automatic pre-alarm for a smart mobile terminal without changing the structure of the smart mobile terminal, improve the user experience, and save the production cost and the processing resources. [0005]To this end, the technical solution of the embodiments of the present disclosure is implemented as follows: [0006]An embodiment of the present disclosure provides an alarm method for a mobile terminal, after a pre-alarm function of the mobile terminal is enabled, the method includes: [0007]when it is detected that an input operation is performed on the mobile terminal, pre-alarm information is generated and output. [0008]In the solution, before the pre-alarm function of the mobile terminal is enabled, the method may further include that the pre-alarm function is set for the mobile terminal. [0009]In the solution, the step that the pre-alarm function is set for the mobile terminal may include: [0010]a pre-alarm function menu is created, a pre-alarm function switch is set in the pre-alarm function menu, and a pre-alarm output way is set, wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal. [0011]In the solution, the step that when it is detected that input operation is performed on the mobile terminal, pre-alarm information is generated and output may include: [0012]when it is detected that a touch screen or a function key of the mobile terminal is pressed or it is detected that an enabling instruction is input for an application of the mobile terminal, pre-alarm information is generated, and the pre-alarm information is output according to the set pre-alarm output way. [0013]In the solution, the method may further include: [0014]a pre-alarm area is set on the touch screen of the mobile terminal; [0015]when the pre-alarm function is not enabled, the pre-alarm function is enabled when it is detected that the pre-alarm area is clicked; when the pre-alarm function is enabled, the pre-alarm function is disabled when it is detected that the pre-alarm area is clicked; or, clicking times of continuously clicking the pre-alarm area is counted, and the pre-alarm function is enabled or disabled by counting the clicking times. [0016]An embodiment of the present disclosure further provides an alarm device for a mobile terminal, and the device includes a processing module and an output module, wherein [0017]the processing module is configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; and [0018]the output module is configured to output the pre-alarm information. [0019]In the solution, the device may further include a setting module which is configured to set the pre-alarm function for the mobile terminal. [0020]In the solution, the setting module may be further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu, and set a pre-alarm output way, wherein the pre-alarm information is different from a call or short message reminder message of the mobile terminal. [0021]In the solution, the processing module may be configured to generate the pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or detecting that an enabling instruction is input for an application of the mobile terminal; [0022]and correspondingly, the output module may be configured to output the pre-alarm information according to the set pre-alarm output way. [0023]In the solution, the setting module may be further configured to set a pre-alarm area on the touch screen of the mobile terminal; and [0024]correspondingly, when the pre-alarm function is not enabled, the processing module enables the pre-alarm function when detecting that the pre-alarm area is clicked; when the pre-alarm function is enabled, the processing module disables the pre-alarm function when detecting that the pre-alarm area is clicked; or, the processing module counts clicking times of continuously clicking the pre-alarm area, and enables or disables the pre-alarm function by counting the clicking times. [0025]An embodiment of the present disclosure further provides a mobile terminal, which is provided with the alarm device in the above solutions. [0026]According to the alarm method and the alarm device for a mobile terminal, and the mobile terminal in which the alarm device is arranged provided by the embodiments of the present disclosure, the pre-alarm function is set to be enabled; when it is detected that the touch screen or the function key of the mobile terminal is pressed or it is detected that an enabling instruction is input for an application of the mobile terminal, the pre-alarm information is generated; and the pre-alarm information is output according to the set pre-alarm output way. Through the technical solution of the embodiments of the present disclosure, automatic pre-alarm can be implemented for a smart mobile terminal; when the mobile terminal is operated accidentally, a notification can be given to a user at once, so that the security of the mobile terminal is ensured, and the user experience is improved; moreover, the structure of the mobile terminal does not need to be changed, and the production cost can be saved. BRIEF DESCRIPTION OF THE DRAWINGS [0027]FIG. 1 is a schematic diagram showing the flow of an alarm method for a mobile terminal according to an embodiment of the present disclosure; and [0028]FIG. 2 is a schematic diagram showing the composition structure of an alarm device for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0029]An embodiment of the present disclosure provides an alarm method for a mobile terminal, as shown in FIG. 1, the method includes: [0030]Step 11: A pre-alarm function of the mobile terminal is enabled. [0031]Here, the pre-alarm function is set for the mobile terminal in advance. The step that the pre-alarm function is set for the mobile terminal may include: a pre-alarm function menu is created, a pre-alarm function is set to be enabled in the pre-alarm function menu, and a pre-alarm output way is set, wherein the pre-alarm output way includes an audio way, a video way or a combined way of audio and video. The mobile terminal includes a smart phone and a feature phone. [0032]A pre-alarm area is set on a touch screen of the mobile terminal; when the pre-alarm function is not enabled, the pre-alarm function is enabled when it is detected that the pre-alarm area is clicked; when the pre-alarm function is enabled, the pre-alarm function is disabled when it is detected that the pre-alarm area is clicked; or, clicking times of continuously clicking the pre-alarm area is counted, and the pre-alarm function is enabled or disabled by counting the click times, for example, the pre-alarm function is enabled if the counted times is an odd number and the pre-alarm function is disabled if the counted times is an even number. [0033]Step 12: When it is detected that an input operation is performed on the mobile terminal, alarm information is generated and output. [0034]In the embodiment, the pre-alarm information includes at least one of the following ways: ringtone, vibration and touch panel glittering. The pre-alarm information is different from a call or short message reminder message of the mobile terminal. [0035]A pre-alarm identifier 1 represents that the pre-alarm function of the smart phone is enabled, and a pre-alarm identifier 0 represents that the pre-alarm function is disenabled. [0036]When the pre-alarm function is enabled, namely, the pre-alarm identifier is 1, pre-alarm information, such as ringtone, is generated and output when it is detected that the touch screen or the function key of the mobile terminal is pressed. [0037]Or, when the pre-alarm function is enabled, namely, the pre-alarm identifier is 1, pre-alarm information, such as ringtone, may be generated and output when it is detected that an enabling instruction is input for an application of the mobile terminal, such as a message box and a phone book. For example, when a message box button or a phone book button is clicked, pre-alarm information such as ringtone is generated and output. [0038]After the pre-alarm function is enabled, the screen of the mobile terminal is locked if it is detected that no input operation is performed on the mobile terminal within a preset time, wherein the preset time can be adjusted according to the frequency of utilization of the mobile terminal. [0039]Based on the alarm method for a mobile terminal, an embodiment of the present disclosure further provides an alarm device for a mobile terminal. FIG. 2 is a schematic diagram showing the composition structure of an alarm device for a mobile terminal, as shown in FIG. 2, the device includes a processing module 22 and an output module 23, wherein [0040]the processing module 22 is configured to enable a pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that an input operation is performed on the mobile terminal; and [0041]the output module 23 is configured to output the pre-alarm information. [0042]Preferably, the device further includes a setting module 21, wherein the setting module 21 is configured to set a pre-alarm function for the mobile terminal and is further configured to create a pre-alarm function menu, set a pre-alarm function switch in the pre-alarm function menu and set a pre-alarm output way; the pre-alarm information is different from a call or a short message reminder message of the mobile terminal. [0043]The processing module 22 is configured to enable the pre-alarm function of the mobile terminal, and generate pre-alarm information when detecting that a touch screen or a function key of the mobile terminal is pressed or an enabling instruction is input for an application of the mobile terminal, such as clicking a message box button or a phone book button; [0044]and correspondingly, the output module 23 is configured to output the pre-alarm information according to the set pre-alarm output way. [0045]The pre-alarm output way includes: an audio way, a video way or a combined way of audio and video; and correspondingly, the pre-alarm information includes at least one of the following ways: ringtone, vibration and touch panel glittering. [0046]The setting module 21 is further configured to set a pre-alarm area in the pre-alarm function menu; correspondingly, when the pre-alarm function is not enabled, the pre-alarm function is enabled when the processing module 22 detects that the pre-alarm area is clicked; when the pre-alarm function is enabled, the pre-alarm function is disabled when the processing module 22 detects that the pre-alarm area is clicked; or, the processing module 22 counts clicking times of continuously clicking the pre-alarm area and enables or disables the pre-alarm function by counting the clicking times. For example, the pre-alarm function is enabled when the clicking times is an odd number and is disabled when the clicking times is an even number. [0047]After the pre-alarm function is enabled, the screen of the mobile terminal is locked if the processing module 22 detects that no input operation is performed on the mobile terminal within a preset time, wherein the preset time is preset in the processing module 22 and can be adjusted according to the frequency of utilization of the mobile terminal. [0048]In the actual application, the setting module 21, the processing module 22 and the output module 23 can be implemented by the Central Processing Unit (CPU), the Digital Signal Processor (DSP) or the Field Programmable Gate Array (FPGA) and the like; and the CPU, DSP and FPGA can be arranged in the mobile terminal. [0049]Those skilled in the art shall understand that the implementing functions of each processing module in the alarm device for a mobile terminal in FIG. 2 can be understood in reference to the related description of the alarm method for a mobile terminal. Those skilled in the art shall understand that the function of each processing unit of the alarm device for a mobile terminal in FIG. 2 can be implemented either by a program running on a processor or by a specific logic circuit. [0050]The present disclosure further records a mobile terminal, including the alarm device in FIG. 2. [0051]According to the alarm method and the alarm device for a mobile terminal, and the mobile terminal provided by the embodiments of the present disclosure, a pre-alarm function is set to be enabled at first, and after the pre-alarm function of the mobile terminal is enabled, when it is detected that the touch screen or the function key of the mobile terminal is pressed or it is detected that an enabling instruction is input for an application of the mobile terminal, pre-alarm information is generated, and the pre-alarm information is output according to a set pre-alarm output way to remind a user that the mobile terminal is being turned on. Through the technical solution of the embodiments of the present disclosure, automatic pre-alarm can be implemented on the smart mobile terminal without changing the structure of the smart mobile terminal, thereby saving the production cost and the processing resources, and improving the user experience. [0052]Provided with the alarm device, the mobile terminal in the embodiment of the present disclosure also has the technical effects. [0053]The above are only the preferred embodiments of the present disclosure, and are not intended to limit the scope of protection of the claims of the present disclosure.(String), 技术领域 [0001] 本发明涉及报警技术,尤其涉及一种移动终端的报警方法、报警装置及移动终端。 背景 [0002] 随着通信技术的飞速发展,用户设备越来越普及。 尤其是智能终端,如智能手机,以其快捷、方便等特点更受用户欢迎。 通常,智能手机中收集了用户的隐私信息,如银行卡号、家庭成员的身份证号等,这在给用户带来方便的同时也可能带来安全问题。 当智能手机被盗或隐私信息被窥探时,可能会给用户造成损失。 [0003] 目前,为保证智能手机信息安全,主要有以下几种方式: 智能手机内置指纹识别器,通过用户指纹启动智能手机; 或者,对通话、短信等通信内容进行加密解密。 虽然可以保护智能手机中信息的安全,但通过在智能手机中设置指纹识别器,试图改变智能手机的结构来达到目的,无疑会增加智能手机的生产成本。 保护信息安全。 对于通过对通话内容进行加解密来保证安全的方法,通常在短信中加入干扰信息,只有在短信解密成功后才能发现干扰信息,浪费了终端的软硬件处理资源。 智能手机是不可避免的。 概括 [0004] 有鉴于此,本发明实施例的主要目的在于提供一种移动终端的报警方法、装置及移动终端,以在不改变结构的情况下实现智能移动终端的自动预警。 智能移动终端,提升用户体验,节约生产成本和加工资源。 [0005] 为此,本发明实施例的技术方案是这样实现的: [0006] 本发明实施例提供了一种移动终端的报警方法,在开启移动终端的预警功能后,该方法包括: [0007] 当检测到移动终端有输入操作时,生成并输出预警信息。 [0008] 上述方案中,在开启移动终端的预警功能之前,该方法还可以包括:为移动终端设置预警功能。 [0009] 上述方案中,为移动终端设置预警功能的步骤可以包括: [0010] 创建预警功能菜单,在预警功能菜单中设置预警功能开关,并设置预警输出方式,其中预警信息不同于来电或短信提醒 移动终端的消息。 [0011] 上述方案中,所述在检测到移动终端有输入操作时,生成并输出预警信息的步骤可以包括: [0012] 当检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用程序的启用指令时,生成预警信息,该预警信息为 按设置的预警输出方式输出。 [0013] 上述方案中,所述方法还可以包括: [0014] 在移动终端的触摸屏上设置预警区域; [0015] 当未开启预警功能时,检测到点击预警区域时开启预警功能; 当开启预警功能时,检测到点击预警区域时关闭预警功能; 或者,对连续点击预警区域的点击次数进行统计,通过对点击次数的统计来开启或关闭预警功能。 [0016] 本发明实施例还提供了一种移动终端的报警装置,该装置包括处理模块和输出模块,其中 [0017] 处理模块,用于开启移动终端的预警功能,当检测到移动终端有输入操作时,生成预警信息; 和 [0018] 输出模块,用于输出预警信息。 [0019] 上述方案中,所述装置还包括设置模块,用于为所述移动终端设置预警功能。 [0020] 上述方案中,设置模块还用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式,其中,预警信息 不同于移动终端的来电或短信提醒消息。 [0021] 上述方案中,所述处理模块,具体用于在检测到所述移动终端的触摸屏或功能键被按下时,或者检测到输入了对所述移动终端的应用的启用指令时,生成所述预警信息; [0022] 相应的,输出模块可以用于根据设置的预警输出方式输出预警信息。 [0023] 上述方案中,所述设置模块还用于在所述移动终端的触摸屏上设置预警区域; 和 [0024] 相应地,当预警功能未开启时,处理模块在检测到预警区域被点击时开启预警功能。 当开启预警功能时,处理模块检测到预警区域被点击时,关闭预警功能。 或者,处理模块统计连续点击预警区域的点击次数,通过统计点击次数来开启或关闭预警功能。 [0025] 本发明实施例还提供了一种移动终端,包括上述方案中的报警装置。 [0026] 本发明实施例提供的移动终端的报警方法、报警装置及设置有报警装置的移动终端,设置为开启预警功能; 当检测到移动终端的触摸屏或功能键被按下或检测到输入了对移动终端的应用程序的启用指令时,生成预警信息。 并按照设置的预警输出方式输出预警信息。 通过本发明实施例的技术方案,可以实现智能移动终端的自动预警; 当移动终端被误操作时,可以第一时间通知用户,保证了移动终端的安全,提高了用户体验。 并且不需要改变移动终端的结构,可以节省生产成本。 附图的简要说明 [0027] 图1为本发明实施例提供的移动终端告警方法的流程示意图; 和 [0028] 图2为本发明实施例的移动终端报警装置的组成结构示意图。 详细说明 [0029] 本发明实施例提供了一种移动终端的告警方法,如图1所示,该方法包括: [0030] 步 11 :开启移动终端预警功能。 [0031]这里,预先为移动终端设置了预警功能。 为移动终端设置预警功能的步骤可以包括:创建预警功能菜单,在预警功能菜单中设置开启预警功能,并输出预警信号。 设置方式,其中,预警输出方式包括音频方式、视频方式或音视频结合方式。 移动终端包括智能手机和功能手机。 [0032] 在移动终端的触摸屏上设置预警区域; 当未开启预警功能时,检测到点击预警区域时开启预警功能; 当开启预警功能时,检测到点击预警区域时关闭预警功能; 或者,对连续点击预警区域的点击次数进行计数,通过对点击次数的计数来开启或关闭预警功能,例如,如果计数次数为奇数,则开启预警功能; 如果计数次数为偶数,则禁用预警功能。 [0033] 步 12 :当检测到移动终端有输入操作时,产生并输出告警信息。 [0034] 在本实施例中,预警信息包括以下方式中的至少一种:铃声、振动、触摸屏闪烁。 预警信息不同于移动终端的来电或短信提醒消息。 [0035] 预警标识符 1 表示开启智能手机的预警功能,预警标识0表示关闭预警功能。 [0036] 当开启预警功能,即预警标识为1时,检测到触摸屏或移动终端的功能键被按下时,产生并输出铃声等预警信息 . [0037] 或者,当开启预警功能时,即预警标识为1时,可以在检测到为应用程序输入开启指令时,生成并输出铃声等预警信息。 移动端,如消息框、电话簿。 例如,当点击消息框按钮或电话簿按钮时,生成并输出铃声等预警信息。 [0038] 开启预警功能后,如果检测到在预设时间内没有对移动终端进行任何输入操作,则锁定移动终端的屏幕,其中,预设时间可以根据用户的使用频率进行调整。 移动终端。 [0039] 基于上述移动终端的报警方法,本发明实施例还提供了一种移动终端的报警装置。 图2为一种移动终端报警装置的组成结构示意图,如图2所示,该装置包括处理模块 22 和一个输出模块 23 , 其中 [0040] 处理模块 22 用于开启移动终端的预警功能,当检测到移动终端有输入操作时,生成预警信息; 和 [0041] 输出模块 23 用于输出预警信息。 [0042] 优选地,所述装置还包括设置模块 21 , 其中设置模块 21 用于为移动终端设置预警功能,进一步用于创建预警功能菜单,在预警功能菜单中设置预警功能开关,设置预警输出方式。 预警信息不同于移动终端的来电或短信提醒消息。 [0043] 处理模块 22 用于开启移动终端的预警功能,当检测到移动终端的触摸屏或功能键被按下,或者为移动终端的应用输入开启指令时,生成预警信息, 例如点击消息框按钮或电话簿按钮; [0044]相应地,输出模块 23 用于按照设置的预警输出方式输出预警信息。 [0045] 预警输出方式包括:音频方式、视频方式或音视频结合方式; 相应的,所述预警信息包括以下至少一种方式:铃声、振动、触摸屏闪烁。 [0046] 设置模块 21 还用于在预警功能菜单中设置预警区域; 相应地,当预报警功能未开启时,处理模块开启预报警功能 22 检测到预警区域被点击; 预报警功能开启时,处理模块预报警功能关闭 22 检测到预警区域被点击; 或者,处理模块 22 统计连续点击预警区域的点击次数,通过统计点击次数来开启或关闭预警功能。 例如,当点击次数为奇数时开启预警功能,当点击次数为偶数时关闭预警功能。 [0047] 启用预警功能后,如果处理模块锁定移动终端屏幕 22 检测到移动终端在预设时间内没有输入操作,该预设时间预先设置在处理模块中 22 并且可以根据移动终端的使用频率进行调整。 [0048] 在实际应用中,设置模块 21 , 处理模块 22 和输出模块 23 可由中央处理器(CPU)、数字信号处理器(DSP)或现场可编程门阵列(FPGA)等实现; CPU、DSP和FPGA可以设置在移动终端中。 [0049] 本领域技术人员应当理解,图2中的移动终端报警装置中各处理模块的实现功能可以参照移动终端报警方法的相关描述来理解。 本领域的技术人员应该理解,图2中的移动终端报警装置的各处理单元的功能可以通过运行在处理器上的程序实现,也可以通过具体的逻辑电路实现。 [0050] 本发明还记载了一种移动终端,包括图2中的报警装置。 [0051] 本发明实施例提供的移动终端的报警方法、报警装置及移动终端,首先设置开启预警功能,开启手机的预警功能后 终端开启时,当检测到移动终端的触摸屏或功能键被按下或检测到移动终端的应用输入了开启指令时,产生预警信息,并预报警 -按照设定的预报警输出方式输出报警信息,提醒用户移动终端正在开机。 通过本发明实施例的技术方案,可以在不改变智能移动终端结构的情况下,在智能移动终端上实现自动预警,节省了生产成本和处理资源,提高了用户体验。 [0052] 设置有报警装置,本发明实施例的移动终端还具有技术效果。 [0053] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104023118A(String), EP2963903A2(String), EP2963903A4(String), EP2963903B1(String), JP2016513435A(String), KR1020150123880A(String), US20160156760A1(String), WO2013189439A2(String), WO2013189439A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104023118A(String), EP2963903A2(String), EP2963903A4(String), EP2963903B1(String), JP2016513435A(String), KR1020150123880A(String), US20160156760A1(String), WO2013189439A2(String), WO2013189439A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20160156760A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104023118A(String), EP2963903A2(String), EP2963903A4(String), EP2963903B1(String), JP2016513435A(String), KR1020150123880A(String), US20160156760A1(String), WO2013189439A2(String), WO2013189439A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.917 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.917 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.917 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), CN104023118A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), EP2963903A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:35.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), EP2963903A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), EP2963903B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), JP2016513435A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.094 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), KR1020150123880A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), US20160156760A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), WO2013189439A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271646(Integer), WO2013189439A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20160156760A1(String), US20160156760A1(String), 1464796800(Integer), 271646(Integer), 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185936(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.385 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.385 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.385 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185936(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185936(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185936(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185936(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:36.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130111351A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for remotely controlling mobile terminal and mobile terminal(String), 远程控制移动终端的方法及移动终端(String), US20130111351A1(String), The present invention discloses a method for remotely controlling a mobile terminal and a mobile terminal, wherein the method comprises: receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; and sending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled. By way of the present invention, the effect of remotely controlling mobile terminals is achieved, and the application of assisting others to solve problems or sharing a mobile terminal with others via videophones is achieved, which greatly enriches the contents of videophones and provides wider application space for the business application of videophones.(String), 本发明公开了一种移动终端的远程控制方法及移动终端,该方法包括: 第一移动终端接收对待控界面的触屏操作, 发送待控界面 第二移动终端在视频通话过程中,获取该操作的第一触屏坐标; 第一移动终端将第一触屏坐标转换为待控制界面的界面坐标; 第一移动终端向第二移动终端发送界面坐标,以控制待控制界面。 通过本发明,实现了远程控制移动终端的效果,实现了通过可视电话协助他人解决问题或与他人共享移动终端的应用,极大的丰富了可视电话的内容,提供了更广阔的应用空间 用于可视电话的商业应用。(String), US13/259707(String), 1289491200(Integer), US20130111351A1(String), 1367424000(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 9(Integer), US20060015598A1 | US20080148316A1 | US20080256472A1 | US20090104943A1 | US20090298469A1 | US20100321379A1 | US20110231796A1 | US6325756B1 | US7120433B2(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185937(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.369 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c82b06b5a3ac4fc4ad9bf5058e8331e4.png(String), 185937(Integer), c82b06b5a3ac4fc4ad9bf5058e8331e4.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for remotely controlling mobile terminal and mobile terminal(String), 远程控制移动终端的方法及移动终端(String), US20130111351A1(String), The present invention discloses a method for remotely controlling a mobile terminal and a mobile terminal, wherein the method comprises: receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; and sending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled. By way of the present invention, the effect of remotely controlling mobile terminals is achieved, and the application of assisting others to solve problems or sharing a mobile terminal with others via videophones is achieved, which greatly enriches the contents of videophones and provides wider application space for the business application of videophones.(String), 本发明公开了一种移动终端的远程控制方法及移动终端,该方法包括: 第一移动终端接收对待控界面的触屏操作, 发送待控界面 第二移动终端在视频通话过程中,获取该操作的第一触屏坐标; 第一移动终端将第一触屏坐标转换为待控制界面的界面坐标; 第一移动终端向第二移动终端发送界面坐标,以控制待控制界面。 通过本发明,实现了远程控制移动终端的效果,实现了通过可视电话协助他人解决问题或与他人共享移动终端的应用,极大的丰富了可视电话的内容,提供了更广阔的应用空间 用于可视电话的商业应用。(String), US13/259707(String), 1289491200(Integer), US20130111351A1(String), 1367424000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 9(Integer), US20060015598A1 | US20080148316A1 | US20080256472A1 | US20090104943A1 | US20090298469A1 | US20100321379A1 | US20110231796A1 | US6325756B1 | US7120433B2(String), \20230420\c82b06b5a3ac4fc4ad9bf5058e8331e4.png(String), 16(Integer), 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 1. A method for remotely controlling a mobile terminal, comprising:receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation;converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; andsending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled.(String), 1.根据权利要求2所述的方法,其中第一移动终端将第一触屏坐标转换为待控制界面的界面坐标的步骤包括:第一移动终端根据第一触屏坐标、第一移动终端的触屏分辨率和视频分辨率,将第一触屏坐标转换为待控制界面的界面坐标。第一个移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 2. The method according to claim 1, wherein the method further comprises:receiving, by the second mobile terminal, the interface coordinate;converting the interface coordinate into a second touch-screen coordinate of the second mobile terminal; andperforming operation control to the interface to be controlled according to the second touch-screen coordinate.(String), 12.根据权利要求2所述的方法,其中第一移动终端向第二移动终端发送界面坐标的步骤包括:第一移动终端将接口坐标封装成H.245协议的坐标消息,坐标消息用于传输接口坐标的信息;和向第二移动终端发送坐标消息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 3. The method according to claim 1, wherein the step of converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled comprises:converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the first mobile terminal, and a video resolution of the first mobile terminal.(String), 13.根据权利要求2所述的方法,其中在第一移动终端接收视频通话中第二移动终端发送的对待控制界面的触屏操作之前,还包括:第一移动终端和第二移动终端通过H.245协议进行触屏信息传递能力交互,触屏信息传递能力用于支持第一移动终端和第二移动终端传递触屏信息界面坐标信息;和确认第一移动终端和第二移动终端均支持触屏信息传递能力。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 4. The method according to claim 1, wherein the step of sending, by the first mobile terminal, the interface coordinate to the second mobile terminal comprises:encapsulating, by the first mobile terminal, the interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transmitting the information of the interface coordinate; andsending the coordinate message to the second mobile terminal.(String), 14.根据权利要求7所述的移动终端,其中第一转换模块,用于根据第一触摸屏坐标、移动终端触摸屏的分辨率和移动终端的视频分辨率,将第一触摸屏坐标转换为待控制界面的第一界面坐标。移动终端。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 5. The method according to claim 1, wherein before the step of receiving, by the first mobile terminal, the touch-screen operation to the interface to be controlled sent by a second mobile terminal during a video call, the method further comprises:performing, by the first mobile terminal and the second mobile terminal, touch-screen information transfer capability exchange using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the first mobile terminal and the second mobile terminal to transfer the interface coordinate information; andconfirming that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 15.根据权利要求7所述的移动终端,其中第一控制模块包括:封装模块,用于将第一接口坐标封装成H.245协议的坐标消息,坐标消息用于传递接口坐标的信息;和发送模块,用于向所述另一移动终端发送所述坐标消息,以控制所述另一移动终端的待控制界面。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 6. A mobile terminal, comprising:an acquiring module, configured to receive a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by the other mobile terminal during a video call, and acquire a first touch-screen coordinate of the operation;a first converting module, configured to convert the first touch-screen coordinate into a first interface coordinate of the interface to be controlled; anda first control module, configured to send the first interface coordinate to the other mobile terminal to control the interface to be controlled.(String), 16.根据权利要求7所述的移动终端,其中移动终端还包括:交换模块,用于通过H.245协议与其他移动终端进行触屏信息传递能力交换,所述触屏信息传递能力用于支持移动终端与其他移动终端传递界面坐标信息;和确认模块,用于确认第一移动终端和第二移动终端均支持触屏信息传递能力。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 7. The mobile terminal according to claim 6, wherein the mobile terminal further comprises:a receiving module, configured to receive a second interface coordinate sent by the other mobile terminal;a second converting module, configured to convert the second interface coordinate into a second touch-screen coordinate; anda second control module, configured to perform operation control to the interface to be controlled of the mobile terminal according to the second touch-screen coordinate.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 8. The mobile terminal according to claim 6, wherein the first converting module is configured to convert the first touch-screen coordinate into the first interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the mobile terminal and a video resolution of the mobile terminal.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 9. The mobile terminal according to claim 6, wherein the first control module comprises:an encapsulating module, configured to encapsulate the first interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transferring the information of the interface coordinate; anda sending module, configured to send the coordinate message to the other mobile terminal to control the interface to be controlled of the other mobile terminal.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 10. The mobile terminal according to claim 6, wherein the mobile terminal further comprises:an exchanging module, configured to perform touch-screen information transfer capability exchange with the other mobile terminal using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the mobile terminal and the other mobile terminal to transfer interface coordinate information; anda confirmation module, configured to confirm that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 11. The method according to claim 2, wherein the step of converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled comprises:converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the first mobile terminal, and a video resolution of the first mobile terminal.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 12. The method according to claim 2, wherein the step of sending, by the first mobile terminal, the interface coordinate to the second mobile terminal comprises:encapsulating, by the first mobile terminal, the interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transmitting the information of the interface coordinate; andsending the coordinate message to the second mobile terminal.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 13. The method according to claim 2, wherein before the step of receiving, by the first mobile terminal, the touch-screen operation to the interface to be controlled sent by a second mobile terminal during a video call, the method further comprises:performing, by the first mobile terminal and the second mobile terminal, touch-screen information transfer capability exchange using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the first mobile terminal and the second mobile terminal to transfer the interface coordinate information; andconfirming that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 1(Integer), 12(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 14. The mobile terminal according to claim 7, wherein the first converting module is configured to convert the first touch-screen coordinate into the first interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the mobile terminal and a video resolution of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 15. The mobile terminal according to claim 7, wherein the first control module comprises:an encapsulating module, configured to encapsulate the first interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transferring the information of the interface coordinate; anda sending module, configured to send the coordinate message to the other mobile terminal to control the interface to be controlled of the other mobile terminal.(String), 1(Integer), 14(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185937(Integer), 16. The mobile terminal according to claim 7, wherein the mobile terminal further comprises:an exchanging module, configured to perform touch-screen information transfer capability exchange with the other mobile terminal using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the mobile terminal and the other mobile terminal to transfer interface coordinate information; anda confirmation module, configured to confirm that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability.(String), 1(Integer), 15(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185937(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, and in particular to a method for remotely controlling a mobile terminal and a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the rapid development of mobile multimedia services and the gradual business application of 3G domestically, the videophone service, which has been developed and applied in the personal communication field rapidly, becomes the landmark service of 3G. The Videophone service is a point-to-point video communication service, which can make use of the telephone network to transmit the images and voice signals of the call parties bi-directionally and in real time. The video terminals can achieve an effect of face-to-face communication and realize the dream of “hear the voice and also see the people” when calling. [0003]However, when this new function of videophone is used, the following situations such as: the users do not know how to use one certain function of the mobile terminal and need the assistance of others; or the terminal cannot be used normally and needs the assistance of others to analyze the reason; or it is desired to share the contents in this terminal with other users during calling, may also often appear in practical application. [0004]As to the above situations, a video terminal and a method for achieving the share of interface contents thereof are provided in the related art. According to the method, a switch unit and an interface content processing unit are set in the video terminal, wherein the switch unit is used for receiving the switch instructions from the outside and selecting to acquire video data by a viewfinder or acquire cache data by an LCD data display cache area to collect sending data; and the interface content processing unit is used for processing the data from the LCD data display cache area and converting the same to the data which complies with the encoding input format requirements and outputting the same. During the video call, the real-time share of the terminal interface contents during video call is achieved in manner of the data transmission of video call through the switch requirements of the user and the interface content processing unit. Herein, the terminal which initiates the share is defined as a second terminal, and the other party is a first terminal In this method, although the first terminal can share the current interface contents of the second terminal, the first terminal can only accept the current interface of the second terminal passively but cannot operate the current interface actively, such as switch the interface actively and so on. Therefore, the remote coordination control demands of the users still cannot be satisfied. SUMMARY OF THE INVENTION [0005]According to the present invention, a method for remotely controlling a mobile terminal and a mobile terminal are provided to solve the above problem that the remote coordination control demands of the users cannot be satisfied by the video mobile terminal. [0006]According to one aspect of the present invention, a method for remotely controlling a mobile terminal is provided, wherein the method comprises: receiving, by a first mobile terminal, a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled; and sending, by the first mobile terminal, the interface coordinate to the second mobile terminal to control the interface to be controlled. [0007]Furthermore, this method for remotely controlling a mobile terminal further comprises: receiving, by the second mobile terminal, the interface coordinate; converting the interface coordinate into a second touch-screen coordinate of the second mobile terminal; and performing operation control to the interface to be controlled according to the second touch-screen coordinate. [0008]Furthermore, the step of converting, by the first mobile terminal, the first touch-screen coordinate into an interface coordinate of the interface to be controlled comprises: converting, by the first mobile terminal, the first touch-screen coordinate into the interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the first mobile terminal, and a video resolution of the first mobile terminal. [0009]Furthermore, the step of sending, by the first mobile terminal, the interface coordinate to the second mobile terminal comprises: encapsulating, by the first mobile terminal, the interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transmitting the information of the interface coordinate; and sending the coordinate message to the second mobile terminal. [0010]Furthermore, before the step of receiving, by the first mobile terminal, a touch-screen operation to the interface to be controlled sent by a second mobile terminal during a video call, the method further comprises: performing, by the first mobile terminal and the second mobile terminal, touch-screen information transfer capability exchange using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the first mobile terminal and the second mobile terminal to transfer the interface coordinate information; and confirming that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability. [0011]According to another aspect of the present invention, a mobile terminal is provided, wherein the mobile terminal comprises: an acquiring module, configured to receive a touch-screen operation to an interface to be controlled, wherein the interface to be controlled is sent by the other mobile terminal during a video call, and acquiring a first touch-screen coordinate of the operation; a first converting module, configured to convert the first touch-screen coordinate into a first interface coordinate of the interface to be controlled; and a first control module, configured to send the first interface coordinate to the other mobile terminal to control the interface to be controlled. [0012]Furthermore, this mobile terminal further comprises: a receiving module, configured to receive a second interface coordinate sent by the other mobile terminal; a second converting module, configured to convert the second interface coordinate into a second touch-screen coordinate; and a second control module, configured to perform operation control to the interface to be controlled of the mobile terminal according to the second touch-screen coordinate. [0013]Furthermore, the first converting module is configured to convert the first touch-screen coordinate into the first interface coordinate of the interface to be controlled according to the first touch-screen coordinate, a resolution of a touch screen of the mobile terminal and a video resolution of the mobile terminal. [0014]Furthermore, the first control module comprises: an encapsulating module, configured to encapsulate the first interface coordinate into a coordinate message of the H.245 protocol, wherein the coordinate message is used for transferring the information of the interface coordinate; and a sending module, configured to send the coordinate message to the other mobile terminal to control the interface to be controlled of the other mobile terminal. [0015]Furthermore, this mobile terminal further comprises: an exchange module, configured to perform touch-screen information transfer capability exchange with another mobile terminal using the H.245 protocol, wherein the touch-screen information transfer capability is used for supporting the mobile terminal and the other mobile terminal to transfer interface coordinate information; and a confirmation module, configured to confirm that both the first mobile terminal and the second mobile terminal support the touch-screen information transfer capability. [0016]By way of the present invention, the problem in the related art that the video mobile terminal cannot meet the remote coordination control demand of the users is solved by using a first mobile terminal to perform operation control to the application interface of a second mobile terminal via a videophone and a touch screen, the effect of remotely controlling mobile terminals is achieved, and the application of assisting others to solve problems or sharing a mobile terminal with others via videophones is achieved, which greatly enriches the contents of videophones and provides wider application space for the business application of videophones. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The drawings illustrated here provide a further understanding of the present invention and form a part of the present application. The exemplary embodiments and the description thereof are used to explain the present invention without unduly limiting the present invention, wherein: [0018]FIG. 1 is a schematic diagram of the data structure of a capability set according to an embodiment of the present invention; [0019]FIG. 2 is a schematic diagram of a capability format according to an embodiment of the present invention; [0020]FIG. 3 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment I of the present invention; [0021]FIG. 4 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment II of the present invention; [0022]FIG. 5 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment III of the present invention; [0023]FIG. 6 is a schematic diagram of a coordinate transfer and conversion process according to an embodiment of the present invention; [0024]FIG. 7 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment IV of the present invention; [0025]FIG. 8 is a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment V of the present invention; [0026]FIG. 9 is a structural block diagram of a mobile terminal according to Embodiment VI of the present invention; [0027]FIG. 10 is a structural block diagram of mobile terminals according to Embodiment VII of the present invention; and [0028]FIG. 11 is a flow chart of the steps of applying the mobile terminals shown in FIG. 10 to perform remote control. DETAILED DESCRIPTION OF THE EMBODIMENTS [0029]The embodiments of the present invention will be described hereinafter in detail in conjunction with the drawings thereof. It needs to be noted that the embodiments of the present application and the features in the embodiments can be combined with each other if no conflict exists. [0030]All the mobile terminals related in the embodiments of the present invention support videophone and are touch-screen mobile terminals. [0031]In the mobile videophone field, the most common communication protocol is the H.324 protocol set, which includes the H.223 multiplexing protocol, the H.245 system control protocol, the H.263 video encoding protocol, the G.723.1 audio encoding protocol and so on. The method of a video mobile terminal performing remote control and the video mobile terminal according to the embodiments of the present invention are based on the H.324 video communication protocol and make certain supplement to the H.245 control protocol to achieve remote control. [0032]The H.245 protocol is a control signaling protocol and mainly used for the end-to-end H.245 information exchange between terminals which are communicating. In the H.245 protocol, the capability exchange process is a process which needs to be firstly carried out after the establishment of H.245 call, the objective of which is to ensure that the sent multimedia signals can be received and encoded by a terminal. The terminal enables the other side to know the capability combination which the terminal can receive by sending its “capability set”. The other side does not have to understand all these capabilities, and the other side only needs to store the capability portion which can be understood and may be used so as to facilitate the other side to establish a logic channel. [0033]The terminal capability set contains a capability table in a message, wherein the table lists all the operation modes allowed by the terminal and each mode is assigned with a corresponding sequence number (capability number). Several capability numbers consist of a “selectable capability set” structure, which describes a media channel capability of the terminal and indicates that the terminal can work based on any mode therein. Several “selectable capability set” consist of a “simultaneous capability” structure, which indicates that this terminal can use a set of capabilities to work simultaneously. At last, several “simultaneous capability” can further consist of a “capability description set” structure, which contains a set of capability descriptions, with each description consisted of a simultaneous capability and a capability description sequence number. This data structure gives the total capability of the terminal, the particular data structure of which is as shown in FIG. 1. [0034]In the present invention, the characteristics of the above H.245 protocol are used and new capabilities are defined in the H.245 capability set: touch-screen information transfer capability, which supports the call parties to transfer coordinate information; and new message types are defined in the H.245 protocol, i.e. coordinate message, so as to enable the terminals which have touch-screen information transfer capability to send, receive, and feed back the coordinate information. [0035]In particular, the new touch-screen information transfer capability defined in the H.245 is as follows: [0036]H.245 uses ASN.1 (Abstract Syntax Notation 1) standard to define its own message structure, the message data of which uses binary encoding based on PER (Packed Encoding Rule) rule. The above capability definition format in the embodiments of the present invention is as shown in FIG. 2. [0037]According to the above capability format, the new coordinate message defined in the H.245 protocol of the embodiments of the present invention is as follows: [0038]the representation mode of coordinate message format and that of ordinary messages are consistent, and the difference only lies in the type field in the message (the corresponding type is “coordinate information”) which is used for differentiating from other message types. In addition, the coordinate location information is converted into data which complies with the encoding input format requirements and outputted and delivered in the videophone. [0039]The mobile terminal initiates an operation (such as click to select and pull) using the touch screen via the touch point coordinate information, and transfers the coordinate information during the video call using the new touch-screen information transfer capability and the coordinate message defined in H.245 to remotely control another mobile terminal, thus greatly facilitating the use of users, meeting the demand of users to perform remote cooperation control, and also accelerating the popularization of video terminals. [0040]All the mobile terminals in the following embodiments of the present invention can use the above improved H.245 protocol. [0041]Referring to FIG. 3, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment I of the present invention, and the method comprises the following steps. [0042]Step S102: a first mobile terminal receives a touch-screen operation of an interface to be controlled, wherein the interface to be controlled is sent by a second mobile terminal during a video call, and the first mobile terminal acquires a first touch-screen coordinate of this operation. [0043]In this step, when the first mobile terminal receives the application interface to be controlled of the second mobile terminal sent by the second mobile terminal during the video call, the user of the first mobile terminal performs operation to this application interface using a touch screen, such as click or pull, etc., so as to achieve the remote control of a corresponding application interface on the second mobile terminal. At this moment, the first mobile terminal acquires the coordinate when the user performs operation to the touch screen, i.e. the first touch-screen coordinate. If this operation is the click operation, then the touch-screen coordinate of the click point can be only acquired, and if this operation is the pull operation, then the touch-screen coordinates of the starting touch point and the ending touch point can be acquired, or the touch-screen coordinates of the middle touch points during the pull can be further included. [0044]Step S104: the first mobile terminal converts the first touch-screen coordinate into an interface coordinate of the interface to be controlled. [0045]In this step, since the coordinate origin and the coordinate range of the touch screen may be different from those of the interface to be controlled, it needs to convert the touch-screen coordinate into the interface coordinate of the interface to be controlled. [0046]Step S106: the first mobile terminal sends the interface coordinate to the second mobile terminal to control the interface to be controlled. [0047]In this step, the first mobile terminal can send the interface coordinate to the second mobile terminal to perform remote control to the interface to be controlled by the touch-screen information transfer capability and coordinate message newly defined by the H.245 protocol. Of course, this embodiment is not limited to the H.245 protocol, and any protocol or message which can send the interface coordinate to the second mobile terminal can achieve the solution of this embodiment, which is not limited by the present invention. [0048]In the related art, the first mobile terminal can only accept the current interface contents of the second mobile terminal passively, and cannot perform operation to it actively, which cannot meet the remote cooperation control demand of the users. By way of this embodiment, the first mobile terminal uses the touch screen to operate the interface to be controlled of the second mobile terminal and converts the coordinate operated by the touch screen into the interface coordinate of the interface to be controlled and sends it to the second mobile terminal, and the second mobile terminal performs corresponding operations according to the received coordinate, thus achieving the remote control of the second mobile terminal by the first mobile terminal and meeting the remote cooperation control demand of the users. [0049]Referring to FIG. 4, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment II of the present invention, wherein the method comprises the following steps [0050]Step S202: a second mobile terminal initiates a video call and starts the H.245 call control process with a first mobile terminal [0051]Step S204: the second mobile terminal performs capability exchange with the first mobile terminal and confirms that both parties support the touch-screen information transfer capability. [0052]The above capability exchange process can be initiated by the first mobile terminal during the video call. The capability exchange with the second mobile terminal is performed, and that both parties support the touch-screen information transfer capability is confirmed. [0053]Step S206: the second mobile terminal sends an interface to be controlled to the first mobile terminal. [0054]In this embodiment, taking the desktop interface of the second mobile terminal as an interface to be controlled for example, the second mobile terminal sends its desktop interface to the first mobile terminal. [0055]Step S208: the first mobile terminal displays the interface to be controlled and receives an operation of clicking one certain location of the touch screen by a user. [0056]In this embodiment, taking clicking the short message folder location on the desktop interface for example, the user of the first mobile terminal clicks the corresponding location of the short message folder on the desktop interface sent by the second mobile terminal via the touch screen. [0057]Step S210: the first mobile terminal detects this click and generates a touch-screen coordinate of the touch point. [0058]In this step, the first mobile terminal detects the location of the short message folder on the desktop interface clicked by the user and generates the touch-screen coordinate of this location. [0059]Step S212: the first mobile terminal judges whether the touch-screen coordinate of this touch point is in the interface to be controlled. If yes, then perform step S214; otherwise, then judge that this click is an operation to this mobile terminal, and respond to a corresponding operation of this click touch point. [0060]This step is an optional step, especially when the range of the interface to be controlled and that of the touch screen interface are the same. [0061]Step S214: the first mobile terminal converts the touch-screen coordinate of this touch point into an interface coordinate of the interface to be controlled. [0062]In this step, the first mobile terminal converts this touch-screen coordinate into the coordinate of the short message folder in the desktop interface according to this touch-screen coordinate, the video resolution of the first mobile terminal, and the touch-screen resolution of the first mobile terminal. The particular conversion process can be performed by reference to the coordinate transfer and conversion shown in FIG. 6, which will not be described here redundantly. [0063]Step S216: the first mobile terminal sends the interface coordinate to the second mobile terminal. [0064]In this step, the first mobile terminal sends the interface coordinate to the second mobile terminal via a coordinate message of H.245. [0065]Step S218: the second mobile terminal receives the interface coordinate and converts it to be the touch-screen coordinate of the second mobile terminal. [0066]In this step, the second mobile terminal converts the interface coordinate into the touch-screen coordinate of the second mobile terminal according to the interface coordinate, the video resolution of the second mobile terminal, and the touch-screen resolution of the second mobile terminal. [0067]Step S220: the second mobile terminal responds to this touch-screen coordinate and performs operations to its interface to be controlled. [0068]In this step, the second mobile terminal performs corresponding click operation to the short message folder corresponding to this touch-screen coordinate on the desktop interface in response to this touch-screen coordinate according to the touch-screen coordinate converted from the interface coordinate. [0069]In this embodiment, the second mobile terminal achieves effective control to its interface to be controlled by receiving the interface coordinate sent by the first mobile terminal and then converting the interface coordinate into its own touch-screen coordinate. [0070]Referring to FIG. 5, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment III of the present invention, and the method comprises the following steps. [0071]Step S302: a second mobile terminal initiates a video call and starts the H.245 call control process with a first mobile terminal. [0072]Step S304: the first mobile terminal initiates control switch during the video call to perform capability exchange with the second mobile terminal and confirm that both parties support the touch-screen information transfer capability. [0073]Step S306: the second mobile terminal sends an interface to be controlled to the first mobile terminal. [0074]In this embodiment, taking the e-book interface of the second mobile terminal as an interface to be controlled for example, the second mobile terminal sends its e-book interface to the first mobile terminal. [0075]Step S308: the first mobile terminal displays the interface to be controlled and receives a pull operation of a user on the touch screen. [0076]In this embodiment, taking pulling the scrollbar of the e-book interface for example, the user of the first mobile terminal pulls the corresponding location of the vertical or horizontal scrollbar in the e-book interface sent by the second mobile terminal from top to down via the touch screen. [0077]Step S310: the first mobile terminal detects this operation and generates a touch-screen coordinates of the pulled starting touch point and the ending touch point. [0078]In this step, the first mobile terminal detects the touch-screen operation of the user, judges that this operation type is a pull touch-screen operation according to the press time, and generates the touch-screen coordinates of the pulled starting touch point and the ending touch point. The generated touch-screen coordinates can further include one to more touch point coordinates of the middle touch point during the pull so as to improve the accuracy of the pull operation. [0079]Step S312: the first mobile terminal converts the touch-screen coordinates of the starting touch point and the ending touch point into the interface coordinates of the interface to be controlled. [0080]In this step, the first mobile terminal converts the touch-screen coordinates of the starting touch point and the ending touch point into coordinates of the starting touch point and the ending touch point in the e-book interface according to the touch-screen coordinates of the starting touch point and the ending touch point, the video resolution of the first mobile terminal, and the touch-screen resolution of the first mobile terminal. The particular conversion process can be performed by reference to the coordinate transfer and conversion shown in FIG. 6, which will not be described here redundantly. [0081]Step S314: the first mobile terminal sends the interface coordinate to the second mobile terminal. [0082]In this step, the first mobile terminal sends the interface coordinate to the second mobile terminal via a coordinate message of H.245. [0083]Step S316: the second mobile terminal receives the interface coordinate and converts it into the touch-screen coordinate of the second mobile terminal. [0084]In this step, the second mobile terminal converts the interface coordinate into the touch-screen coordinates of the starting touch point and the ending touch point corresponding to the second mobile terminal according to the interface coordinate, the video resolution of the second mobile terminal, and the touch-screen resolution of the second mobile terminal. [0085]Step S318: the second mobile terminal responds to the touch-screen coordinates of the starting touch point and the ending touch point and performs operations to its interface to be controlled. [0086]In this step, the second mobile terminal performs pull operation to the e-book interface corresponding to this touch-screen coordinate according to the touch-screen coordinates of the starting touch point and the ending touch point converted from the interface coordinate so as to perform downward page turning view and the like to this e-book. [0087]Referring to FIG. 6, it shows a schematic diagram of a coordinate transfer and conversion process according to the embodiments of the present invention. [0088]The mobile terminal and videophone relates to a plurality of resolutions mainly including: video resolution, such as SQCIF, CIF, and QCIF, which are all common standardized image formats, and in which, SQCIF=128×965 pixels, CIF=352×288 pixels, QCIF=176×144 pixels; and LCD resolution which is generally 4*3 ratio, such as 320*240; and touch-screen resolution which can be defined by the terminal itself, such as 900*900. [0089]The final conversion results of the same coordinate under different resolutions are different. As shown FIG. 6, the coordinate transfer and conversion process is as follows: [0090]Step S402: after the user of the first mobile terminal clicks the touch screen, the coordinate of the touch point is touch-screen coordinate, and the coordinate of the touch point needs to be converted into interface coordinate according to the touch-screen resolution and video resolution; [0091]Step S404: since what is displayed in the first mobile terminal is the current application interface of the LCD of the second mobile terminal, this interface coordinate is converted into the LCD coordinate of the second mobile terminal; and [0092]Step S406: the LCD coordinate of the second mobile terminal is converted into the touch-screen coordinate of the second mobile terminal. [0093]The LCD display screen and the touch screen both have their own resolution indexes, which is equivalent to their coordinate systems, assuming that their coordinate systems are (x, y) and (X, Y) respectively. Taking the resolution of the LCD display screen to be 1024*600 for example, its coordinate origin (0, 0) is at the top left corner, the coordinate of the bottom right corner is (1024, 600), while the touch screen also has its own coordinate origin O (this coordinate origin is physical and fixed at one certain location in the screen, and it is very possible that this origin has already been cut away during assembly but it has no effect to coordination determination) [0094]During practical application, two two-dimensional linear coordinate systems are corresponding to each other in manner of sampling, i.e. (X, Y)→(x, y), the particular practice is: (1) the coordinates of the four corners of the LCD screen are used as sampling values (since in the situation that there is no other tools, the definite coordinates of these four points (x1, y1), (x2, y2), (x3, y3), and (x4, y4) are only known); (2) set an input device detection program before running, respectively click the four corners of the LCD, and read out the corresponding touch-screen coordinate values of these points (X1, Y1), (X2, Y2), (X3, Y3), and (X4, Y4) in the program; (3) substitute these four sampling values into the following equations: x=aX+bY+c and y=eX+fY+g; solve 7 coefficients (a, b, c, d, e, f, s) in these equations, and then the correlation of two coordinate systems can be obtained. [0095]The above situation can be used widely and is comprehensive and of high accuracy. However, there are too many unknown numbers to be solved and there are also too many sampling values; and in fact, the current assembly process can totally ensure the phase difference between the two coordinate systems to be an integral multiple of 90 degree, that is, the above correspondence equation can be simplified as the following: {x=aX+b, y=cY+d} or {x=aY+b, y=cX+d} [0096]Thus, it only needs 2 groups of sampling values to determine the corresponding coefficients. [0097]For example, the LCD resolution is 320*240, and the coordinate origin is at the top left corner; and the touch-screen resolution is 900*900, and the coordinate origin is at the top left corner, then the conversion formula is as follows: xLCD=[320*(x−x2)/(x1−x2)], yLCD=[240*(y−y2)/(y1−y2)] [0098]If the coordinate origins are inconsistent, for example, the LCD coordinate origin is at the bottom right corner and the touch screen origin is at the top left corner, then it can further perform the following conversion: xLCD=320−[320*(x−x2)/(x1−x2)] yLCD=240−[240*(y−y2)/(y1−y2)] [0099]Then, the correlation of two coordinate systems is definite, and all touch-screen coordinates are converted into corresponding coordinates in the LCD coordinate system according to this correspondence formula. [0100]Coordination conversion between touch screen and LCD can be achieved according to the above method. [0101]Referring to FIG. 7, it shows a flow chart of the steps of a method for remotely controlling a mobile terminal according to Embodiment IV of the present invention. This embodiment can describe the present invention from the perspective of videophone message transmission protocol procedure, which comprises the following steps. [0102]Step S502: a calling subscriber initiates a video (String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的远程控制方法及移动终端。 发明背景 [0002] 随着移动多媒体业务的快速发展和国内3G业务的逐步应用,可视电话业务在个人通信领域得到了迅速的发展和应用,成为3G的标志性业务。 可视电话业务是一种点对点的视频通信业务,它可以利用电话网络,双向、实时地传输呼叫方的图像和语音信号。 视频终端可以达到面对面交流的效果,实现通话时“闻声见人”的梦想。 [0003] 但是,在使用可视电话这一新功能时,会出现以下情况:用户不知道如何使用移动终端的某项功能,需要他人的帮助; 或终端无法正常使用,需要他人协助分析原因; 或者在通话过程中希望与其他用户共享本终端中的内容,在实际应用中也可能经常出现。 [0004] 针对上述情况,相关技术中提供了一种视频终端及其实现界面内容共享的方法。 该方法在视频终端中设置有切换单元和界面内容处理单元,切换单元用于接收来自外部的切换指令,选择取景器获取视频数据或缓存器获取缓存数据。 LCD数据显示缓存区收集发送数据; 接口内容处理单元,用于对来自LCD数据显示缓存区的数据进行处理,转换为符合编码输入格式要求的数据输出。 在视频通话过程中,通过用户的切换需求和界面内容处理单元,以视频通话数据传输的方式实现视频通话中终端界面内容的实时共享。 这里,定义发起分享的终端为第二终端,对方为第一终端。在该方法中,虽然第一终端可以分享第二终端当前的界面内容,但第一终端只能接受当前的界面内容。 第二终端被动界面,但不能主动操作当前界面,如主动切换界面等。 因此,仍然无法满足用户远程协同控制的需求。 发明内容 [0005] 本发明提供了一种远程控制移动终端的方法及移动终端,以解决上述视频移动终端无法满足用户远程协同控制需求的问题。 [0006] 根据本发明的一个方面,提供了一种远程控制移动终端的方法,该方法包括:第一移动终端接收对待控制界面的触屏操作,其中,所述待控制界面 controlled由第二移动终端在视频通话时发送,获取操作的第一触屏坐标; 第一移动终端将第一触屏坐标转换为待控制界面的界面坐标; 第一移动终端将界面坐标发送给第二移动终端以控制待控制界面。 [0007] 进一步地,该移动终端远程控制方法还包括:第二移动终端接收界面坐标; 将界面坐标转换为第二移动终端的第二触屏坐标; 根据第二触屏坐标对待控制界面进行操作控制。 [0008]进一步地,所述第一移动终端将所述第一触屏坐标转换为所述待控制界面的界面坐标包括:所述第一移动终端将所述第一触屏坐标转换为待控制界面的界面坐标。 根据第一触屏坐标、第一移动终端的触屏分辨率和第一移动终端的视频分辨率控制界面。 [0009] 进一步地,第一移动终端向第二移动终端发送接口坐标包括:第一移动终端将接口坐标封装成H.245协议的坐标消息,其中,坐标消息为 用于传递界面坐标信息; 向第二移动终端发送坐标信息。 [0010] 进一步地,在所述第一移动终端接收视频通话中第二移动终端发送的对所述待控界面的触屏操作之前,所述方法还包括:所述第一移动终端和所述第一移动终端执行: 第二移动终端,采用H.245协议的触屏信息传递能力交互,触屏信息传递能力用于支持第一移动终端和第二移动终端传递界面坐标信息; 确认第一移动终端和第二移动终端均支持触屏信息传递能力。 [0011] 根据本发明的另一方面,提供了一种移动终端,其中,所述移动终端包括: 获取模块,用于接收对待控界面的触屏操作,所述待控界面由所述待控界面发送。 视频通话中的其他移动终端,获取操作的第一触屏坐标; 第一转换模块,用于将所述第一触摸屏坐标转换为所述待控界面的第一界面坐标; 第一控制模块,用于将所述第一界面坐标发送给所述另一移动终端,以控制所述待控制界面。 [0012] 进一步地,该移动终端还包括: 接收模块,用于接收另一移动终端发送的第二界面坐标; 第二转换模块,用于将第二界面坐标转换为第二触摸屏坐标; 第二控制模块,用于根据第二触屏坐标对移动终端的待控界面进行操作控制。 [0013] 进一步地,第一转换模块,用于根据第一触摸屏坐标、移动终端触摸屏的分辨率和视频分辨率,将第一触摸屏坐标转换为待控制界面的第一界面坐标。 的移动终端。 [0014] 进一步地,所述第一控制模块包括: 封装模块,用于将所述第一接口坐标封装为H.245协议的坐标消息,所述坐标消息用于传递所述接口坐标的信息。 发送模块,用于向所述另一移动终端发送所述坐标消息,以控制所述另一移动终端的待控制界面。 [0015] 进一步地,该移动终端还包括:交换模块,用于通过H.245协议与另一移动终端进行触屏信息传递能力交换,触屏信息传递能力用于支持移动终端和 其他移动终端传递界面坐标信息; 确认模块,用于确认第一移动终端和第二移动终端均支持触屏信息传递能力。 [0016]本发明通过第一移动终端通过以下方式对第二移动终端的应用界面进行操作控制,解决了相关技术中视频移动终端无法满足用户远程协同控制需求的问题。 可视电话和触摸屏,实现远程控制移动终端的效果,实现通过可视电话协助他人解决问题或与他人共享移动终端等应用,极大地丰富了可视电话的内容,提供了更广阔的应用空间 用于可视电话的商业应用。 附图的简要说明 [0017] 此处所示的附图提供对本发明的进一步理解并且构成本申请的一部分。 示例性实施例及其描述用于解释本发明而不不当限制本发明,其中: [0018] 图1是本发明一个实施例的能力集的数据结构示意图; [0019] 图2为本发明实施例的能力格式示意图; [0020] 图3为本发明实施例一提供的远程控制移动终端的方法的步骤流程图; [0021] 图4为本发明实施例二提供的远程控制移动终端的方法的步骤流程图; [0022] 图5为本发明实施例三的远程控制移动终端的方法的步骤流程图; [0023] 图6是根据本发明实施例的坐标传递和转换过程的示意图; [0024] 图7为本发明实施例四提供的远程控制移动终端的方法的步骤流程图; [0025] 图8为本发明实施例五远程控制移动终端的方法的步骤流程图; [0026] 图9为本发明实施例六的移动终端的结构框图; [0027] 图10为本发明实施例七的移动终端的结构框图; 和 [0028] 图11是应用图10所示的移动终端进行远程控制的步骤流程图。 具体实施方式 [0029] 下面结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。 [0030] 本发明实施例涉及的移动终端均支持可视电话,且为触摸屏移动终端。 [0031] 在移动可视电话领域,最常见的通信协议是H.324协议集,其中包括H.223复用协议、H.245系统控制协议、H.263视频编码协议、G.723.1音频编码协议 协议等。 本发明实施例提供的视频移动终端进行远程控制的方法及视频移动终端基于H.324视频通信协议,对H.245控制协议进行一定的补充,实现远程控制。 [0032]H.245协议是一种控制信令协议,主要用于通信终端之间端到端的H.245信息交换。 在H.245协议中,能力交换过程是H.245呼叫建立后首先需要进行的过程,其目的是保证发送的多媒体信号能够被终端接收和编码 . 终端通过发送自己的“能力集”,让对方知道自己可以接收到的能力组合。 对方不必了解所有这些能力,对方只需要存储可以理解并可以使用的能力部分,以方便对方建立逻辑通道。 [0033] 终端能力集在消息中包含一个能力表,该表列出了终端允许的所有操作模式,并为每个模式分配了相应的序号(能力号)。 若干个能力号组成一个“可选能力集”结构,描述了终端的媒体通道能力,表示终端可以基于其中的任何模式工作。 多个“可选能力集”组成一个“同时能力”结构,表示该终端可以使用一组能力同时工作。 最后,多个“同时能力”可以进一步组成一个“能力描述集”结构,该结构包含一组能力描述,每一个描述由一个同时能力和一个能力描述序号组成。 该数据结构给出了终端的总体能力,具体数据结构如图1所示。 [0034] 本发明利用了上述H.245协议的特点,在H.245能力集中定义了新的能力: 触摸屏信息传递能力,支持呼叫方传递坐标信息; H.245协议定义了新的消息类型,即坐标消息,使具有触摸屏信息传输能力的终端能够发送、接收和反馈坐标信息。 [0035] 特别地,H.245中定义的新的触摸屏信息传递能力如下: [0036] H.245使用ASN.1(Abstract Syntax Notation 1)标准定义自己的消息结构,其消息数据使用基于PER(Packed Encoding Rule)规则的二进制编码。 上述本发明实施例中的能力定义格式如图2所示。 [0037] 根据上述能力格式,本发明实施例的H.245协议中定义的新坐标消息如下: [0038] 坐标报文格式的表示方式与普通报文一致,区别仅在于报文中的类型字段(对应的类型为“坐标信息”),用于与其他报文类型区分开来。 另外,将坐标位置信息转换成符合编码输入格式要求的数据在可视电话中输出下发。 [0039] 移动终端通过触摸点坐标信息发起触摸屏操作(如点击选择和拉动),并在视频通话中使用新的触摸屏信息传递能力和定义的坐标消息传递坐标信息 H.245远程控制另一个移动终端,极大地方便了用户的使用,满足了用户远程协作控制的需求,也加速了视频终端的普及。 [0040] 本发明以下实施例中的移动终端均可以使用上述改进的H.245协议。 [0041] 参见图3,其示出了根据本发明实施例一的远程控制移动终端的方法的步骤流程图,该方法包括以下步骤。 [0042] 脚步 102:第一移动终端接收待控界面的触屏操作,其中,所述待控界面是视频通话中第二移动终端发送的,第一移动终端获取该待控界面的第一触屏坐标 手术。 [0043] 本步骤中,当第一移动终端在视频通话中接收到第二移动终端发送的第二移动终端的待控制应用界面时,第一移动终端的用户通过触摸屏对该应用界面进行操作, 例如点击或拉动等,以实现对第二移动终端上相应应用界面的远程控制。 此时,第一移动终端获取用户对触摸屏进行操作时的坐标,即第一触摸屏坐标。 如果本次操作是点击操作,则只能获取点击点的触屏坐标,如果本次操作是拉动操作,则可以获取起始触摸点和结束触摸点的触摸屏坐标 获取,或者可以进一步包括拉动过程中中间触摸点的触摸屏坐标。 [0044] 脚步 104 :第一移动终端将第一触屏坐标转换为待控制界面的界面坐标。 [0045] 在该步骤中,由于触摸屏的坐标原点和坐标范围可能与待控界面的坐标原点和坐标范围不同,因此需要将触摸屏坐标转换为待控界面的界面坐标。 [0046] 脚步 106 :第一移动终端将界面坐标发送给第二移动终端控制待控制界面。 [0047] 本步骤中,第一移动终端可以将界面坐标发送给第二移动终端,以实现对H.245协议新定义的触摸屏信息传递能力和坐标消息控制的界面进行远程控制。 当然,本实施例不限于H.245协议,任何能够将接口坐标发送给第二移动终端的协议或消息均可实现本实施例的方案,本发明对此不做限制。 [0048] 相关技术中,第一移动终端只能被动地接受第二移动终端当前的界面内容,不能主动对其进行操作,无法满足用户的远程协作控制需求。 通过本实施例,第一移动终端通过触摸屏操作第二移动终端的待控界面,并将触摸屏操作的坐标转换为待控界面的界面坐标,发送给第二移动终端。 第二移动终端,第二移动终端根据接收到的坐标进行相应的操作,从而实现第一移动终端对第二移动终端的远程控制,满足用户的远程协作控制需求。 [0049] 参见图4,其示出了根据本发明实施例二的一种远程控制移动终端的方法的步骤流程图,该方法包括以下步骤 [0050] 脚步 202 :第二个移动终端发起视频通话,开始与第一个移动终端的H.245呼叫控制流程 [0051] 脚步 204 :第二移动终端与第一移动终端进行能力交互,确认双方均支持触屏信息传递能力。 [0052] 上述能力交换过程可以由第一移动终端在视频通话过程中发起。 与第二移动终端进行能力交互,确认双方均支持触屏信息传递能力。 [0053] 脚步 206 :第二移动终端向第一移动终端发送待控制界面。 [0054]在本实施例中,以第二移动终端的桌面界面作为待控制界面为例,第二移动终端将其桌面界面发送给第一移动终端。 [0055] 脚步 208 :第一移动终端显示待控制界面,并接收用户点击触摸屏某个位置的操作。 [0056] 在本实施例中,以点击桌面界面的短信文件夹位置为例,第一移动终端的用户通过触摸屏点击第二移动终端发送的桌面界面的短信文件夹的对应位置。 [0057] 脚步 210 :第一移动终端检测到该点击,生成触摸点的触屏坐标。 [0058] 本步骤中,第一移动终端检测用户点击的桌面界面上短信文件夹的位置,并生成该位置的触屏坐标。 [0059] 脚步 212 :第一移动终端判断该触摸点的触屏坐标是否在待控制界面中。 如果是,则执行步骤S 214 ; 否则,则判断本次点击是对本移动终端的操作,并响应本次点击触点的相应操作。 [0060] 该步骤为可选步骤,尤其是在需要控制的界面范围与触摸屏界面范围相同的情况下。 [0061] 脚步 214 :第一移动终端将该触摸点的触屏坐标转换为待控制界面的界面坐标。 [0062] 在该步骤中,第一移动终端根据该触摸屏坐标、第一移动终端的视频分辨率和第一移动终端的触摸屏分辨率,将该触摸屏坐标转换为桌面界面中短信文件夹的坐标。 第一个移动终端。 具体的转换过程可以参考图6所示的坐标传递和转换,在此不再赘述。 [0063] 脚步 216 :第一移动终端将接口坐标发送给第二移动终端。 [0064] 本步骤中,第一移动终端将接口坐标通过H.245的坐标消息发送给第二移动终端。 [0065] 脚步 218 :第二移动终端接收界面坐标,转换为第二移动终端的触屏坐标。 [0066] 本步骤中,第二移动终端根据界面坐标、第二移动终端的视频分辨率和第二移动终端的触屏分辨率,将界面坐标转换为第二移动终端的触屏坐标。 [0067] 脚步 220 :第二移动终端响应该触屏坐标,对其待控制界面进行操作。 [0068] 本步骤中,第二移动终端根据界面坐标转换后的触屏坐标,响应该触屏坐标,对桌面界面上该触屏坐标对应的短信文件夹进行相应的点击操作。 [0069] 在本实施例中,第二移动终端通过接收第一移动终端发送的界面坐标,然后将界面坐标转换为自身的触屏坐标,实现对其待控界面的有效控制。 [0070] 参见图5,其示出了根据本发明实施例三的远程控制移动终端的方法的步骤流程图,该方法包括以下步骤。 [0071] 脚步 302 :第二个移动终端发起视频呼叫,并启动与第一个移动终端的H.245呼叫控制过程。 [0072] 脚步 304:第一移动终端在视频通话过程中发起控制切换,与第二移动终端进行能力交换,确认双方均支持触屏信息传递能力。 [0073] 脚步 306 :第二移动终端向第一移动终端发送待控制界面。 [0074] 在本实施例中,以第二移动终端的电子书界面作为待控制界面为例,第二移动终端将其电子书界面发送给第一移动终端。 [0075] 脚步 308 :第一移动终端显示待控制界面,并接收用户在触摸屏上的拉动操作。 [0076] 本实施例中,以拉动电子书界面的滚动条为例,第一移动终端的用户从上到下拉动第二移动终端发送的电子书界面中垂直或水平滚动条的对应位置。 通过触摸屏。 [0077] 脚步 310 :第一移动终端检测到该操作,生成拉动的起始触摸点和结束触摸点的触屏坐标。 [0078] 本步骤中,第一移动终端检测用户的触屏操作,根据按下时间判断该操作类型为拉动触屏操作,并生成拉动起始触摸点的触屏坐标和 结束接触点。 生成的触摸屏坐标还可以包括拉动过程中中间触摸点的一个或多个触摸点坐标,以提高拉动操作的准确性。 [0079] 脚步 312 :第一移动终端将起始触摸点和结束触摸点的触摸屏坐标转换为待控制界面的界面坐标。 [0080] 本步骤中,第一移动终端根据触摸屏坐标将起始触摸点和结束触摸点的触摸屏坐标转换为电子书界面中起始触摸点和结束触摸点的坐标。 起始触摸点和结束触摸点、第一移动终端的视频分辨率和第一移动终端的触摸屏分辨率。 具体的转换过程可以参考图6所示的坐标传递和转换,在此不再赘述。 [0081] 脚步 314 :第一移动终端将接口坐标发送给第二移动终端。 [0082] 本步骤中,第一移动终端将接口坐标通过H.245的坐标消息发送给第二移动终端。 [0083] 脚步 316 :第二移动终端接收界面坐标,转换为第二移动终端的触屏坐标。 [0084] 本步骤中,第二移动终端根据界面坐标、第二移动终端的视频分辨率,将界面坐标转换为第二移动终端对应的起始触摸点和结束触摸点的触屏坐标。 第二移动终端的触摸屏分辨率。 [0085] 脚步 318 :第二移动终端响应起始触摸点和结束触摸点的触屏坐标,对其待控制界面进行操作。 [0086] 本步骤中,第二移动终端根据界面坐标转换的起始触摸点和结束触摸点的触摸屏坐标,对该触摸屏坐标对应的电子书界面进行拉动操作,以执行 对该电子书进行向下翻页查看等操作。 [0087] 参见图6,其示出了根据本发明实施例的坐标传递和转换过程的示意图。 [0088]移动终端和可视电话涉及多种分辨率,主要包括:视频分辨率,如SQCIF、CIF、QCIF等,都是常见的标准化图像格式,其中,SQCIF=128×965像素,CIF=352×288 像素,QCIF=176×144像素; LCD分辨率一般为4*3比例,如320*240; 触摸屏分辨率可由终端自行定义,如900*900。 [0089] 同一坐标在不同分辨率下最终的转换结果是不同的。 如图6所示,坐标传递和转换过程如下: [0090] 脚步 402 :第一移动终端用户点击触摸屏后,触摸点坐标为触摸屏坐标,需要根据触摸屏分辨率和视频分辨率将触摸点坐标转换为界面坐标 ; [0091] 脚步 404 :由于第一移动终端显示的是第二移动终端LCD的当前应用界面,所以将该界面坐标转换为第二移动终端的LCD坐标; 和 [0092] 脚步 406 :将第二移动终端的LCD坐标转换为第二移动终端的触摸屏坐标。 [0093] LCD显示屏和触摸屏都有自己的分辨率指标,相当于它们的坐标系,假设它们的坐标系分别为(x,y)和(X,Y)。 以液晶显示屏的分辨率为1024*600为例,其坐标原点(0, 0)在左上角,右下角的坐标为(1024, 600),而触摸屏也 有自己的坐标原点O(这个坐标原点是物理的,固定在屏幕的某个位置,很可能这个原点在组装时已经被切掉了,但对坐标确定没有影响) [0094] 在实际应用中,两个二维线性坐标系以采样方式相互对应,即(X,Y)→(x,y),具体做法是:(1) 以液晶屏作为采样值(由于在没有其他工具的情况下,确定这四个点的坐标(x1,y1),(x2,y2),(x3,y3),(x4,y4) 只知道); (2)运行前设置一个输入设备检测程序,分别点击LCD的四个角,读出这几个点(X1,Y1),(X2,Y2),(X3,Y3)对应的触摸屏坐标值 ), 和 (X4, Y4) 在程序中; (3)将这四个采样值代入如下方程:x=aX+bY+c和y=eX+fY+g; 求解这些方程中的7个系数(a、b、c、d、e、f、s),即可得到两个坐标系的相关性。 [0095] 上述情况适用范围广,内容全面,准确性高。 但是,需要求解的未知数太多,采样值也太多; 事实上,目前的装配工艺完全可以保证两个坐标系的相位差为 90 度,即上述对应方程可以简化为: {x=aX+b, y=cY+d} 或者 { x=aY+b, y=cX+d} [0096] 这样,它只需要 2 组的采样值来确定相应的系数。 [0097] 例如LCD分辨率为320*240,坐标原点在左上角; 触摸屏分辨率为900*900,坐标原点在左上角,则换算公式如下: x 液晶屏=[320*( x−x 2)/( x 1− x 2)], y 液晶屏=[240*( y−y 2)/( y 1− y 2)] [0098] 如果坐标原点不一致,比如LCD坐标原点在右下角,触摸屏坐标原点在左上角,那么还可以进一步进行如下转换: x LCD=320−[320*( x−x 2)/( x 1− x 2)] y LCD=240−[240*( y−y 2)/( y 1− y 2)] [0099] 然后确定两个坐标系的相关性,根据这个对应关系式将所有触摸屏坐标转换成LCD坐标系中对应的坐标。 [0100] 触摸屏与LCD的配合转换可按上述方法实现。 [0101] 参见图7,其示出了根据本发明实施例四的远程控制移动终端的方法的步骤流程图。 本实施例从可视电话消息传输协议流程的角度来描述本发明,包括以下步骤。 [0102] 脚步 502 :主叫用户向被叫用户发起视频通话。 [0103] 脚步 504 :主叫用户与被叫用户建立无线链路成功。 [0104] 脚步 506 :主叫用户和被叫用户进行移动电平分层,双方协商相同的移动电平。 [0105] 在这种情况下,移动层主要描述了双方能够支持的音视频编码格式,以保证通信双方的终端能够正常通信。 [0106] 脚步 508 :分层成功后,双方发起H.245呼叫控制流程,建立控制通道,进行能力交换。 [0107] 在该步骤中,双方交换H.245中新定义的触摸屏信息传递能力,以确认双方都支持双方在可视电话中传递坐标信息的能力。 [0108] 脚步 510 :被叫方发起切换指令,以其当前触摸屏的显示界面作为被控界面,将图片数据或图像信息传送给主叫方。 [0109] 脚步 512 :主叫方在被控界面任意位置点击,转换触摸点的坐标信息,然后将该坐标信息以H.245呼叫控制协议的方式发送给被叫用户。 同时启动重传定时器机制。 如果超时仍未收到对方的响应消息,则启动H.245协议中的循环延时判断过程,判断被叫是否可达。 如果不可达,则放弃此呼叫; 如果可达,则继续通话,将坐标信息再次发送给被叫方。 [0110] 脚步 514 :被叫接收到坐标信息后,反馈给主叫确认接收。 [0111] 脚步 516 :主叫方点击可视电话通话窗口界面,重复步骤S 510 到小号 514 使被叫用户能够及时响应相应的操作。 [0112] 脚步 518 :主叫停止对被叫发起控制操作,被叫收到停止发送信号后恢复界面显示。 [0113] 脚步 520 :主叫用户挂断电话,移除协议栈和无线链路,通话结束。 [0114] 参见图8,其示出了根据本发明实施例五的远程控制移动终端的方法的步骤流程图。 在本实施例中,将相互通信的双方定义为移动终端A和B。当是普通视频通话时,每个移动终端将显示两个视频,其中一个是对端的视频或界面,参考 一个是主视频,另一个是移动端当前的相机界面,称为辅助视频。 [0115] 脚步 602 :A和B视频通话过程中,A发起控制请求,B接受请求并确认。 [0116] 在该步骤中,也可以由B发起控制切换请求。 [0117]脚步 604 :双方通话界面切换。 [0118] 此时A的主视频显示的是B当前屏幕显示的应用界面,B的主视频显示的是A的摄像头视频,此时B需要设置主视频在某个时间点显示 尺寸较小的角或设置为不显示,以方便终端A对其进行远程操作控制。 [0119] 脚步 606 :A通过主视频中的触摸屏进行操作,并将该操作的坐标信息通过可视电话发送给B。 [0120] 脚步 608 : B接收到A发送的坐标信息并响应相应的操作,B进行应用界面刷新。 [0121] 脚步 610 :A的主视频界面显示B刷新后的应用界面,重复步骤S的操作 606 到小号 608 . [0122] 脚步 612 :A端或B端任意一方发起结束请求,结束遥控,恢复到普通视频通话界面。 [0123] 参见图9,其示出了根据本发明实施例六的移动终端的结构框图,包括以下模块: [0124] 获取模块 702 ,用于接收对待控制界面的触屏操作,所述待控界面为视频通话中另一移动终端发送的,并获取该操作的第一触屏坐标; 第一转换模块 704 , 用于将第一触屏坐标转换为待控制界面的第一界面坐标; 和第一控制模块 706 ,用于将第一界面坐标发送给其他移动终端控制待控制界面。 [0125] 优选地,本实施例的移动终端还包括:接收模块 708 ,用于接收其他移动终端发送的第二接口坐标; 第二个转换模块 710 , 用于将第二界面坐标转换为第二触屏坐标; 和第二个控制模块 712 ,用于根据第二触屏坐标对移动终端的待控制界面进行操作控制。 [0126] 优选地,第一转换模块 704 用于根据第一触屏坐标、移动终端的触屏分辨率和移动终端的视频分辨率,将第一触屏坐标转换为待控制界面的第一界面坐标。 [0127] 优选地,第一控制模块 706 包括:封装模块 7062 将第一接口坐标封装成H.245协议的坐标消息,坐标消息用于传递接口坐标的信息; 和发送模块 7064 用于向另一移动终端发送坐标消息以控制另一移动终端的待控制界面。 [0128] 优选地,本实施例的移动终端还包括:交换模块 714 ,用于通过H.245协议与另一移动终端进行触屏信息传递能力交互,所述触屏信息传递能力用于支持所述移动终端与所述另一移动终端传递界面坐标信息; 和一个确认模块 716 , 用于确认移动终端与另一移动终端均支持触屏信息传递能力。 [0129]参见图10,其示出了根据本发明实施例七的移动终端的结构示意图。 为了描述方便,本实施例将界面坐标的生成部分和发送部分设置在第一移动终端上,将界面坐标的接收部分和操作部分设置在第二移动终端上。 但是,本领域的技术人员应该理解,上述第一移动终端和第二移动终端可以是同一个移动终端,以达到对另一个移动终端进行远程控制并能够接收到另一个移动终端的远程控制的目的。 终端。 [0130] 其中,第一移动终端包括:可视电话通话接口,用于接收第二移动终端发送的待控界面,并通过本移动终端的触摸屏对该待控界面进行操作。 触摸屏检测装置(相当于获取模块),用于检测用户的触摸屏操作,并生成所操作的触摸点的触摸屏坐标; 触摸屏控制器,用于响应本终端用户的触摸屏操作,将触摸屏坐标发送给辅助处理模块,判断触摸点是否在待控制界面范围内; 类似; 辅助处理模块(相当于第一转换模块),用于将触摸屏坐标转换为界面坐标; 可视电话控制模块(相当于第一控制模块、交换模块和确认模块),用于通过H.245协议与第二移动终端进行能力交换,传递接口坐标等。 [0131] 其中,第二移动终端包括:可视电话控制模块(相当于接收模块),用于通过H.245协议与第二移动终端进行能力交互,接收接口坐标等。 辅助处理模块(相当于第二转换模块),用于将界面坐标转换为本终端的触屏坐标; 触摸屏控制器(相当于第二控制模块),用于根据界面坐标转换的触摸屏坐标响应第一移动终端的遥控操作等; 终端CPU,用于对触摸屏和系统进行控制等。 [0132] 参见图11,其示出了应用图10所示的移动终端进行远程控制的步骤流程图,包括以下步骤。 [0133] 脚步 902 :第一移动终端用户显示第二移动终端用户通过可视电话界面发送的待控制界面; 第一移动终端的用户点击触摸屏的某个位置; 触摸屏检测装置检测到该点击,并生成该点击的触摸点的坐标信息。 [0134] 脚步 904 :触摸屏检测装置将该坐标信息传递给触摸屏控制器,触摸屏控制器判断该触摸点是否在待控制界面内。 若是,则判断对第二移动终端进行遥控操作,继续步骤S 906 ,触摸屏控制器不执行任何操作; 若否,则判断对本终端进行操作,触摸屏控制器响应对本终端的相应操作。 [0135] 脚步 906 :触摸屏控制器为辅助处理模块提供坐标信息,辅助处理模块根据该坐标信息计算出该触摸点的坐标在待控界面中的界面坐标,视频分辨率,触摸 -屏幕分辨率。 [0136] 脚步 908:第一移动终端辅助处理模块向可视电话控制模块提供接口坐标。 [0137] 脚步 910 :第一移动终端的可视电话模块通过H.245协议将接口坐标传递给可视电话控制模块。 [0138] 脚步 912 :第二移动终端的可视电话控制模块将接口坐标传递给第二移动终端的辅助处理模块,辅助处理模块根据该接口坐标将该接口坐标转换为第二移动终端的触摸屏坐标 、LCD 分辨率和触摸屏分辨率。 [0139] 脚步 914 :第二移动终端的辅助处理模块将转换后的触摸屏坐标传递给第二移动终端的触摸屏控制器。 [0140] 脚步 916 :第二移动终端的触摸屏控制器响应界面坐标转换后的触摸屏坐标进行相应的操作。 [0141] 显然,本领域的技术人员应该理解,本发明的上述模块和步骤可以使用通用计算设备来实现,可以集成在一个计算设备中,也可以分布在由多个计算设备组成的网络上。 可选地,本发明的模块和步骤可以通过使用计算装置的可执行程序代码来实现,从而存储在存储装置中并由计算装置执行,在某些情况下,可以执行 此处所示或所述步骤以外的顺序,或分别制成集成电路模块,或多个模块或其步骤制成一个集成电路模块。 这样,本发明不限于任何特定的硬件和软件组合。 [0142] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:37.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101893964A(String), EP2472997A1(String), EP2472997A4(String), US20130111351A1(String), WO2012009904A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.036 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.036 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101893964A(String), EP2472997A1(String), EP2472997A4(String), US20130111351A1(String), WO2012009904A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101893964A(String), EP2472997A1(String), EP2472997A4(String), US20130111351A1(String), WO2012009904A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270876(Integer), CN101893964A(String), 1047413(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270876(Integer), EP2472997A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.141 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270876(Integer), EP2472997A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270876(Integer), US20130111351A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270876(Integer), WO2012009904A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101893964A(String), CN101893964A(String), 1290528000(Integer), 270876(Integer), 185160(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), HUANG, LIANFANG(String), LIU, YANG(String), FANG, WEN(String), 中兴通讯股份有限公司(String), HUANG LIANFANG(String), LIU YANG(String), FANG WEN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185937(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185937(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HUANG, LIANFANG(String), HUANG LIANFANG(String), 0(Integer), 1681976018(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIU, YANG(String), LIU YANG(String), 0(Integer), 1681976018(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: FANG, WEN(String), FANG WEN(String), 0(Integer), 1681976018(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185937(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75826(Integer), 2(Integer), 185937(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75827(Integer), 2(Integer), 185937(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75828(Integer), 2(Integer), 185937(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75826(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.737 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.737 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:38.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185937(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7941123B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and system for downloading data to mobile terminals and for implementing data sharing between mobile terminals(String), 一种向移动终端下载数据并实现移动终端间数据共享的方法及系统(String), US7941123B2(String), The invention discloses a method and system for downloading data to mobile terminals, a mobile terminal that utilizes the method, and a method and a system for implementing data sharing between mobile terminals. The method for data downloading includes: dividing data to be downloaded into multiple data task segments by a master mobile terminal, and allocating the data task segments to one or more mobile terminals; downloading the data by the mobile terminals in accordance with the allocated data task segments; judging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure. The system for data downloading includes: a server, at least a master mobile terminal, and at least a slave mobile terminal.(String), 本发明公开了一种向移动终端下载数据的方法和系统、利用该方法的移动终端、以及实现移动终端之间数据共享的方法和系统。 所述数据下载方法包括:由移动主终端将待下载数据划分为多个数据任务段,并将所述数据任务段分配给一个或多个移动终端。 移动终端按照分配的数据任务段下载数据; 主控移动终端判断是否有数据任务段未下载; 如果是,将数据任务段分配给至少一个已完成下载数据任务段的移动终端。 如果否,则终止下载程序。 该数据下载系统包括:服务器、至少一个主移动终端和至少一个从移动终端。(String), US11/502845(String), 1155225600(Integer), US7941123B2(String), 1304956800(Integer), 1304956800(Integer), 美国(String), 4(Integer), CN | CN | CN(String), 5(Integer), 13(Integer), CN1425990A | CN1578222A | KR1020050048719A | KR1020050053389A | US20020059400A1 | US20030013444A1 | US20040058652A1 | US20050059379A1 | WO2004003008A2 | WO2004043008A1 | WO2004066160A1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185938(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\01bc95c6203144f6a17140c7320af2b4.png(String), 185938(Integer), 01bc95c6203144f6a17140c7320af2b4.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and system for downloading data to mobile terminals and for implementing data sharing between mobile terminals(String), 一种向移动终端下载数据并实现移动终端间数据共享的方法及系统(String), US7941123B2(String), The invention discloses a method and system for downloading data to mobile terminals, a mobile terminal that utilizes the method, and a method and a system for implementing data sharing between mobile terminals. The method for data downloading includes: dividing data to be downloaded into multiple data task segments by a master mobile terminal, and allocating the data task segments to one or more mobile terminals; downloading the data by the mobile terminals in accordance with the allocated data task segments; judging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure. The system for data downloading includes: a server, at least a master mobile terminal, and at least a slave mobile terminal.(String), 本发明公开了一种向移动终端下载数据的方法和系统、利用该方法的移动终端、以及实现移动终端之间数据共享的方法和系统。 所述数据下载方法包括:由移动主终端将待下载数据划分为多个数据任务段,并将所述数据任务段分配给一个或多个移动终端。 移动终端按照分配的数据任务段下载数据; 主控移动终端判断是否有数据任务段未下载; 如果是,将数据任务段分配给至少一个已完成下载数据任务段的移动终端。 如果否,则终止下载程序。 该数据下载系统包括:服务器、至少一个主移动终端和至少一个从移动终端。(String), US11/502845(String), 1155225600(Integer), US7941123B2(String), 1304956800(Integer), 1304956800(Integer), 美国(String), 3(Integer), 4(Integer), CN | CN | CN(String), 5(Integer), 13(Integer), CN1425990A | CN1578222A | KR1020050048719A | KR1020050053389A | US20020059400A1 | US20030013444A1 | US20040058652A1 | US20050059379A1 | WO2004003008A2 | WO2004043008A1 | WO2004066160A1(String), \20230420\01bc95c6203144f6a17140c7320af2b4.png(String), 14(Integer), 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 1. A method for downloading data to mobile terminals, wherein a master mobile terminal is adapted to control one or more mobile terminal, the method comprising:obtaining information about size of data to be downloaded from a server by the master mobile terminal;calculating, by the master mobile terminal, task segments to be downloaded by the mobile terminals;dividing the data to be downloaded into multiple data task segments by the master mobile terminal, and allocating the data task segments to one or more mobile terminals;downloading the data by the mobile terminals in accordance with the allocated data task segments; andjudging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure.(String), 1.根据权利要求10所述的方法,还包括:下载完成后,将下载组中从移动终端的下载数据发送给主移动终端;主移动终端将一个或多个其他移动终端下载的数据发送给下载组中的从移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 2. The method according to claim 1, further comprising the step of sending a request to at least one mobile terminal from the master mobile terminal through a local network before the master mobile terminal allocates the data task segments to the one or more mobile terminals.(String), 12.根据权利要求10所述的方法,其中所述步骤,发送数据下载请求的移动终端加入下载组,包括以下步骤:下载组中的主移动终端邀请发送数据下载请求的移动终端加入下载组;发送数据下载请求的移动终端对主移动终端进行鉴权,鉴权成功则加入下载组。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 3. The method according to claim 1, further comprising the step of obtaining information about the size of the data to be downloaded and determining the size of a data task segment by the master mobile terminal according to the size of the data before dividing the data into multiple data task segments.(String), 13.根据权利要求10所述的方法,还包括:根据下载请求中携带的信息,包括下载数据的ID、类型、大小和定位步骤中获取的位置信息,判断是否满足移动终端的数据下载要求。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 4. The method according to claim 1, wherein in the case that a mobile terminal does not download a data task segment within a predefined duration, the master mobile terminal allocates this data task segment to one or more other mobile terminals.(String), 14.根据权利要求10所述的方法,还包括:通过CELLID或AGPS获取下载组中处于下载状态的主移动终端的位置信息;和/或通过CELLID或AGPS定位发送数据下载请求的移动终端。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 5. The method according to claim 1, wherein a mobile terminal, that has finished downloading of an allocated data task segment, obtains IDs of one or more other mobile terminals from the master mobile terminal, and sends the data of the downloaded task segment to the one or more other mobile terminals in accordance with the obtained IDs.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 6. The method according to claim 1, further comprising the steps of:reporting a message from a mobile terminal, that has finished downloading of an allocated data task segment, to the master mobile terminal indicating the allocated task segment has been downloaded;notifying one or more other mobile terminals of the message by the master mobile terminal;obtaining the downloaded data task segment by the one or more other mobile terminals from that mobile terminal that has finished downloading of the allocated data task segment.(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 7. The method according to claim 1, further comprising the steps of:when the master mobile terminal has downloaded a data task segment, sending the downloaded data task segment to one or more other mobile terminals;when a slave mobile terminal of the one or more mobile terminals has downloaded a data task segment allocated by the master mobile terminal, sending the downloaded data task segment to the master mobile terminal;storing the data task segment by the master mobile terminal and sending this data task segment to one or more other mobile terminals.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 8. A system for data downloading, comprising a server, at least one master mobile terminal, and at least one slave mobile terminal; wherein:the master mobile terminal is configured to control the at least one slave mobile terminal;the master mobile terminal obtains information about size of data to be downloaded from the server;the master mobile terminal calculates task segments to be downloaded by one or more of the master mobile terminal and the at least one slave mobile terminal;the master mobile terminal is designed to divide the data to be downloaded into multiple data task segments, allocate the data task segments to one or more of the master mobile terminal and the at least one slave mobile terminal, and send the data segments downloaded by the one or more of the master mobile terminal and the at least one slave mobile terminal to one or more other mobile terminals;the at least one slave mobile terminal is designed to download a data segment allocated by the master mobile terminal and send the downloaded data segment to the master mobile terminal;the master mobile terminal is connected to the at least one of slave mobile terminal through a network;the server is designed to store data to be downloaded; andeach of the mobile terminal is connected to the server via a communication network so as to download data.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 9. The system according to claim 8, wherein the network is a Bluetooth local network, an infrared local network and/or an Ultra Wide Band local network.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 10. The method according to claim 1, further comprising the following steps of:obtaining location information of the master mobile terminal in a download group as well as characteristic information of data being downloaded;locating a mobile terminal that sent a data download request and verifying whether the data download request is met and the master mobile terminal is located in the download group within local connections;the mobile terminal that sent the data download request joining the download group as a slave mobile terminal in order to download data.(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 11. The method according to claim 10, further comprising:sending downloaded data from a slave mobile terminal in the download group to the master mobile terminal after the download is completed;sending the data, which is downloaded by one or more other mobile terminals, by the master mobile terminal to the slave mobile terminal in the download group.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 12. The method according to claim 10, wherein the step, that the mobile terminal that sent the data download request joining the download group, comprising the steps of :inviting the mobile terminal that sent the data download request to join the download group by the master mobile terminal in the download group;the mobile terminal, that sent the data download request, authenticating the master mobile terminal, and, if the authentication is successful, joining the download group.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 13. The method according to claim 10, further comprising:determining whether the data download requirement of the mobile terminal is met in accordance with the information, including ID, type, and size of data to be downloaded, carried in the download request and the location information obtained in the locating step.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185938(Integer), 14. The method according to claim 10, further comprising:obtaining location information of the master mobile terminal in the download group, which is in a downloading state, with CELL ID or AGPS; and/orlocating the mobile terminal that sent the data download request with CELL ID or AGPS.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:39.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185938(Integer), FIELD OF THE PRESENT INVENTION [0001]The present invention relates to information communication technology field, and more particularly, to a method and a system for downloading data to mobile terminals and for implementing data sharing between mobile terminals. BACKGROUND OF THE PRESENT INVENTION [0002]With the development of mobile communication technology, mobile terminals can also be used for entertainment, such as viewing a movie and downloading large-size software, besides the basic communication function. Our entertainment space can be widened if a mobile terminal may be used for entertainment, for example, during a journey or in remote areas where mobile service coverage is available, due to the portability of the mobile terminal. The mobile terminal can be utilized not only to browse news and information through Internet, but also to view movies. [0003]In the prior art, a mobile terminal can access the internet through GPRS (General Packet Radio Service) or by dialing up, and download movies in form of media streams so as to view the movies. However, with such a download technique, each mobile terminal can only download data separately. If a same movie is to be viewed with multiple mobile terminals, each of the mobile terminals has to download that movie respectively, resulting in repeated download and the waste of bandwidth. In addition, with the above download technique, the download speed is usually lower than the playback speed, resulting in poor movie viewing experience. Furthermore, since each mobile terminal has to download the movie, a large part of bandwidth will be occupied, and the occupation time of bandwidth resource will be increased, thereby the cost will be increased accordingly. [0004]Streaming media is a new network transmission technique, which, in brief, refers to the transmission of multimedia files over network with streaming technique. The streaming technique is a network transmission technique, which, by compressing and loading continuous video and audio data onto the servers at the website, enables the users to view and listen while downloading, instead of waiting the entire compressed file to be downloaded to the mobile terminal. [0005]With the development of the radio technology, the bandwidth of wireless data access is continuously increased, and the processing capacity of a mobile terminal is improved, and a wide variety of high-quality streaming media services become matured. Though the streaming media platform, a mobile terminal can play news, movies, or music in audio/video streams at a low code rate and low speed, and play streaming media in live broadcast services; the mobile terminal can download services and media files. In addition, media files may be copyright-protected with the DRM (Digital Right Management) technique. [0006]In the prior art, the method for playing with a mobile terminal is that, the mobile terminal establishes a connection to the network first; then, the mobile terminal downloads the data streams of streaming media from network side while playing the data streams in real time. This method is mainly characterized by its real-time and heavy occupation of network bandwidth. [0007]In practical applications, there is often the case that two users wish to view a same streaming media at the same time. With the method described above, each of the two users has to establish a connection to the network respectively, as shown in FIG. 1. Then, each of the two users has to establish an over-the-air channel and download the streaming media via the air interface of the over-the-air channel, and play the streaming media locally respectively. [0008]In the above described method for playing streaming media with a mobile terminal: [0009]Overload of the device at the network side may occur, if there are many users downloading and viewing streaming media at the same time. [0010]Too many resources may be occupied. The waste of the resources will occur when two users download the same content, if the two users are not distant from each other and are in the same cell of a base station. Furthermore, two many data connections should not be established in one cell. [0011]This method suppresses the users' enthusiasm to view streaming media to a certain degree, because the users have to not only buy the copyright but also pay the download expense. SUMMARY OF THE PRESENT INVENTION [0012]The present invention is to provide a method for downloading data to mobile terminals, a system for downloading data, and a mobile terminal that utilizes that method. The present invention also provides a method and a system for implementing data sharing between mobile terminals, which implements data sharing and transmission between mobile terminals. [0013]The present invention provides a method for downloading data to mobile terminals, so that the mobile terminal can join a shared download within the local connections. [0014]In one aspect of the present invention, the method for downloading data to mobile terminals may include: [0015]dividing data to be downloaded into multiple data task segments by a master mobile terminal, and allocating the data task segments to one or more mobile terminals; [0016]downloading the data by the mobile terminals in accordance with the allocated data task segments; [0017]judging by the master mobile terminal whether there are any data task segments that have not been downloaded; and if yes, allocating the data task segments to at least one mobile terminal that has finished downloading data task segment; and if no, terminating the download procedure. [0018]Preferably, the method may further comprise the step of sending a request to at least one mobile terminal from the master mobile terminal through a local network before the master mobile terminal allocates the data task segments to the individual mobile terminals. [0019]Preferably, the method may further comprise the step of obtaining the size of the data to be downloaded and determining the size of a data task segment by the master mobile terminal according to the size of the data before dividing the data into multiple data task segments. [0020]Alternatively, in the case that a mobile terminal does not download a data task segment within a predefined duration, the master mobile terminal will allocate this data task segment to one or more other mobile terminals. [0021]Wherein, a mobile terminals, that has finished downloading of an allocated data task segment, obtains IDs of one or more other mobile terminals from the master mobile terminal, and sends the data of the downloaded task segment to the one or more other mobile terminals in accordance with the obtained IDs. [0022]Preferably, the method may further include the steps of: [0023]reporting a message from a mobile terminal, that has finished downloading of an allocated data task segment, to the master mobile terminal indicating the allocated task segment has been downloaded; [0024]notifying one or more other mobile terminals of the message by the master mobile terminal; [0025]obtaining the downloaded data task segment by the one or more other mobile terminals from that mobile terminal that has finished downloading of the allocated data task segment. [0026]Preferably, the method may further include the steps of: [0027]when the master mobile terminal has downloaded a data task segment, sending the downloaded data task segment to one or more other mobile terminals; [0028]when a slave mobile terminal has downloaded a data task segment allocated by the master mobile terminal, sending the downloaded data task segment to the master mobile terminal; storing the data task segment by the master mobile terminal and sending this data task segment to one or more other mobile terminals. [0029]The present invention also provides a system for data downloading, the system include a server, at least one master mobile terminal, and at least one slave mobile terminal; wherein: [0030]the master mobile terminal is designed to control the slave mobile terminals to download data segments and send the data segments downloaded by the master mobile terminal and/or the at least one slave mobile terminal to one or more other mobile terminals; [0031]the at least one slave mobile terminal is designed to download a data segment allocated by the master mobile terminal and send the downloaded data segment to the master mobile terminal; [0032]the master mobile terminal is connected to the at least one of slave mobile terminal through a network; [0033]the server is designed to store data to be downloaded; each of the mobile terminals is connected to the server via a communication network so as to download data. [0034]Wherein the network may be a Blue Teeth local network, an infrared local network and/or an Ultra Wide Band local network. [0035]The present invention also provides a mobile terminal, which is connected to one or more other mobile terminals through a network, including: [0036]a control unit, designed to control the mobile terminals connected therewith to download data and implement sharing of the downloaded data; [0037]a download unit, designed to obtain the size of data to be downloaded and execute download task in accordance with the task segments to be downloaded. [0038]Preferably, the control unit may include: [0039]a calculating unit, designed to calculate the task segments of data to be downloaded with the size of data to be downloaded; [0040]an allocating unit, designed to allocate the calculated task segments to the mobile terminals according to a predefined rule and distribute a data segment downloaded by a mobile terminal to one or more other mobile terminals. [0041]In another aspect of the present invention, the method for downloading data to mobile terminals may include the following steps of: [0042]obtaining location information of a master mobile terminal in a download group as well as characteristic information of data being downloaded; [0043]locating a mobile terminal that sent a data download request and verifying whether the data download request is met and the master mobile terminal is located in a download group within local connections; po the mobile terminal that sent the data download request joining the download group as a slave mobile terminal in order to download data. [0044]Preferably, the method may further include: [0045]sending downloaded data from a slave mobile terminal in the download group to the master mobile terminal after the download is completed; sending the data, which is downloaded by one or more other mobile terminals, by the master mobile terminal to the slave mobile terminal in the download group. [0046]Wherein the step, that the mobile terminal that sent the data download request joining the download group, may include the steps of: [0047]inviting the mobile terminal that sent the data download request to join the download group by the master mobile terminal in the download group; [0048]the mobile terminal, that sent the data download request, authenticating the master mobile terminal, and, if the authentication is successful, joining the download group. [0049]Preferably, the method may further includes: [0050]determining whether the data download requirement of the mobile terminal is met in accordance with the information, including ID, type, and size of data to be downloaded, carried in the download request and the location information obtained in the locating step. [0051]Preferably, the method may further include: [0052]obtaining location information of the master mobile terminal in the download group, which is in a downloading state, with CELL ID or AGPS; and/or [0053]locating the mobile terminal that sent the data download request with CELL ID or AGPS. [0054]The present invention also provides a mobile terminal, which may include: [0055]a network data flow control module, designed to establish a connection with network side and download data from the network side, and send the downloaded data to a network data storage and control module; [0056]a network data storage and control module, designed to buffer the data from the network data flow control module and send the buffered data to a local data flow control module according to a request message; [0057]a local data flow control module, designed to send a request message to the network data storage and control module and send the data stored in the network data storage and control module to one or more other mobile terminals according to a predefined QoS. [0058]The mobile terminal may further include: [0059]a data sharing and communication management module, designed to receive a data connection request message from one or more other mobile terminals, perform authentication and encryption operations for one or more other mobile terminals, and send the authenticated result to the local data flow control module. [0060]Optionally, the terminal may further include: [0061]a local application data application module, designed to send a request to the network data storage and control module and receive data from the network data storage and control module. [0062]The present invention also provides another mobile terminal, which includes: [0063]a network data storage and control module, designed to receive and buffer data from a master mobile terminal and send the buffered data to a local application data application module and a local data flow control module according to a request message; [0064]a local application data application module, designed to send a request message to the network data storage and control module and receive data from the network data storage and control module; [0065]a local data flow control module, designed to send a request message to the network data storage and control module and send the data from the network data storage and control module to other slave mobile terminals according to a predefined QoS. [0066]The mobile terminal may further include: [0067]a data sharing and communication management module, designed to receive a data connection request message from other slave mobile terminals, perform authentication and encryption control operations for other slave mobile terminals, and send the authenticated result to the local data flow control module. [0068]In another aspect of the present invention, the system for implementing data sharing between mobile terminals provided in the present invention may include: [0069]a master mobile terminal, designed to establish a connection with network side and download data from the network side, establish a local data sharing network with slave mobile terminals in a wired or wireless manner, and send the downloaded data to the slave mobile terminals through the local data sharing network; [0070]one or more slave mobile terminals, designed to establish a local data sharing network with the master mobile terminal in a wired or wireless manner, receive data from the master mobile terminal, and send the received data to other slave mobile terminals. [0071]The network formed by the master mobile terminal and all the other mobile terminals are of a star shaped structure, a chain shaped structure, or a tree structure. [0072]The present invention also provides another system for implementing data sharing between mobile terminals, which may include: [0073]a master mobile terminal, designed to establish a connection with network side and download data from the network side, establish a local data sharing network with one or more slave master mobile terminals in a wired or wireless manner, and send the downloaded data to the one or more slave master mobile terminals through the local data sharing network; [0074]one or more slave master mobile terminals, designed to receive streaming media data from the master mobile terminal and process the data accordingly, receive a data connection request from one or more other mobile terminals, perform access admission control operations, such as authentication, encryption, etc., for one or more other mobile terminals, and transmit the streaming media to one or more other mobile terminals according to a predefined QoS; in the case that an abnormity occurs in the master mobile terminal, the slave master mobile terminals receive shared data from one or more other mobile terminals and substitutes the master mobile terminal to implement the download function; [0075]at least one mobile terminal device, designed to establish a local data sharing network with the master mobile terminal in a wired or wireless manner, receive data from the master mobile terminal through the local data sharing network, and send the received data to the slave master mobile terminals. [0076]In the present invention, multiple mobile terminals are enabled to download data segments of a data respectively and share the downloaded data segments among them, thus the download time may be reduced and the download speed may be increased, for example, if there are N mobile terminals downloading data, the download time may be reduced to 1/N of the time required by a single mobile terminal, and the download speed may be increased u N times, which is adaptive to the playback speed of a movie, thereby improving the experience of the users. [0077]By locating the mobile terminal that sent the data download request, and by verifying if the data download requirement of the mobile terminal is met and the master mobile terminal is located in the shared download group within local connections in accordance with the location information of the master mobile terminal in the shared download group and characteristic information of the data being downloaded, the mobile terminal that sent the data download request is enabled to join the shared download group as a slave mobile terminal and perform the shared data download. In the present invention, a mobile terminal can join an appropriate shared download group in the local network at any time, without the need of negotiating with other mobile terminals. Therefore, the difficulties in implementation of shared data download may be mitigated, and the applicability of shared data download may be improved. [0078]It can be seen that, with the above technical scheme, network resources can be saved, the load over the equipment at network side may be reduced, and multiple mobile terminals may be enabled to play back the streaming media while a mobile terminal downloads the streaming media, thereby reducing the cost in downloading data by mobile terminals. BRIEF DESCRIPTION OF THE DRAWINGS [0079]FIG. 1 is a schematic diagram illustrating two users connect to the network respectively in the prior art; [0080]FIG. 2 is a flow diagram of a download method according to an embodiment of the present invention; [0081]FIG. 3 is a flow diagram of a download system according to an embodiment of the present invention; [0082]FIG. 4 is a schematic diagram of a mobile terminal according to an embodiment of the present invention; [0083]FIG. 5 is a flow diagram of the method for downloading data to mobile terminals according to another embodiment of the present invention; [0084]FIG. 6 shows the principle of a method for data sharing between mobile terminals according to an embodiment of the present invention; [0085]FIG. 7 is a processing flow chart of a method for data sharing between mobile terminals according to an embodiment of the present invention; [0086]FIG. 8 is a schematic diagram of a serial structure formed by a master mobile terminal and slave mobile terminals; [0087]FIG. 9 is a schematic diagram of a star shaped structure formed by a master mobile terminal and slave mobile terminals; [0088]FIG. 10 is a structural diagram of a master mobile terminal according to an embodiment of the present invention; [0089]FIG. 11 is a structural diagram of a slave mobile terminal according to an embodiment of the present invention; [0090]FIG. 12 is a structural diagram of a system according to an embodiment of the present invention; [0091]FIG. 13 is a structural diagram of a system according to another embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0092]The method for downloading data to mobile terminals and the supporting system thereof provided in an embodiment of the present invention utilize multiple mobile terminals to download the individual data segments of a data respectively, in which one mobile terminal (also referred to as the master mobile terminal) controls the download progress and sending the data downloaded by each mobile terminal to the other mobile terminals. Thereby, the download may be speeded up. The core idea of the method and the system for data sharing between mobile terminals according to an embodiment of the present invention is that, a mobile terminal establishes a connection to the network side to download streaming media, while other mobile terminals receive and play the streaming media through the local data sharing network. [0093]Hereunder the embodiments of the present invention will be described with reference to the attached drawings. [0094]Here we suppose that mobile terminals A, B, C, . . . , and N wish to obtain data “DATA” from the server. The mobile terminals A, B, C, . . . , and N download data through a communication network (e.g., a 3 G network, a GPRS network, etc.). The mobile terminals A, B, C, . . . , and N are connected through a high speed local network, which can be a local network constructed with Blue Tooth, infrared, or UWB technique. The transmission rate of the local network is required to be much higher than that of the communication network for over-the-air download. More generally, the transmission rate of the local network is at least higher than the product of the number of mobile terminals and the over-the-air download rate. [0095]Due to the fact that a local network usually has a small radius of coverage (e.g., a radius of 10 m) but a high transmission rate (e.g., much higher than the transmission rate of a communication network), the mobile terminals described in the present invention should be within the coverage. In contrast, the system network has a lower transmission rate but a wider coverage. [0096]In order to implement the embodiment of the present invention, one of the mobile terminals A, B, C, . . . , and N is designated as the master mobile terminal. This master mobile terminal only downloads data, but also allocates task segments for data downloading and distributes the download tasks to the other mobile terminals. The other mobile terminals are designated as slave mobile terminals, which are mainly responsible for data downloading. [0097]To simplify the description, here we suppose that the mobile terminal A is the master mobile terminal and the mobile terminals B, C, . . . , and N are slave mobile terminals, as shown in FIG. 2. Hereunder the process that the mobile terminals A, B, C, . . . , and N cooperate for data downloading will be described. [0098]Step S01, The master mobile terminal A originates an invitation to the mobile terminals B, C, . . . , and N through the local network for data downloading. [0099]Step S02, A part or all of slave mobile terminals B, C, . . . , and N accept the invitation from the master mobile terminal A. The master mobile terminal A records the IDs of the slave mobile terminals that have accepted the invitation. To simplify the description, hereunder we suppose all the slave mobile terminals accept the invitation from the master mobile terminal A. [0100]Step S03, The master mobile terminal A obtains from the server the information about the size of DATA file to be downloaded. [0101]Step S04, The master mobile terminal A calculates the task segments to be downloaded by the mobile terminals A, B, C, . . . , and N with a predefined algorithm. [0102]The algorithm can be an average allocation algorithm, that is, the task for downloading DATA is divided into several (e.g., M, here it is supposed that N<1)), it is considered that this mobile terminal has failed. In that case, the master mobile terminal can reallocate the data task segment, which has been allocated to this mobile terminal, to another mobile terminal. [0106]Step S07, After a mobile terminal has finished the download of the allocated task segments, the other mobile terminals is enabled to obtain the downloaded task segment data. In the embodiments of the present invention, there are three ways for the other mobile terminals to be enabled to obtain the downloaded task segment data. The first way, the mobile terminal sends the downloaded task segment data to the other slave mobile terminals. At this time, the mobile terminal has to obtain from the master mobile terminal A the IDs of all slave mobile terminals involved in download, and then send the task segment data depending on the mobile terminal IDs. The second way, the mobile terminal reports a task segment download completion message to the master mobile terminal, which in turn notifies the other slave mobile terminals of the message, so that the other slave mobile terminals can obtain the downloaded data from that mobile terminal. The third way, when the slave mobile terminals B, C, . . . , and N finish the task segments allocated by the master mobile terminal A, the downloaded task segment data will be sent to the master mobile terminal A. The master mobile terminal A stores the task segment data sent from the slave mobile terminals B, C, . . . , or N, and sends the data to the other slave mobile terminals. When its own task segments is completed, the master mobile terminal A stores the task segment data and sends the data to the slave mobile terminals B, C, . . . , and N. [0107]Step S08, The master mobile terminal A judges whether the download of “DATA” is finished. If the download is finished, the master mobile terminal A terminates the download procedure. Otherwise, the master mobile terminal A executes step S05, i.e., the master mobile terminal A allocates task segments that have not been finished to the mobile terminals that have finished their task segments, and S05-S08 is repeated, till the download is completed. [0108]FIG. 3 shows a data download system provided in an embodiment if the present invention. The system includes a server that stores and manages the data to be downloaded and at least two mobile terminals. [0109]At least one of the mobile terminals is the master mobile terminal, which is adapted to control other mobile terminal(s) to download a data segment, and send the downloaded data to mobile terminal(s). The slave mobile terminal(s) is (are) adapted to download data segments allocated by the master mobile terminal and send the downloaded data segments to the master mobile terminal. The mobile terminals are connected with each other through a local network and are connected to the server through a communication network (e.g., a 3 G network, a GPRS network, etc.), so as to download data from the server. The local network is a high-speed local wireless network, such as a local network constructed with Blue Teeth, infrared, or UWB (Ultra Wide Band) technique, with a transmission rate much higher than that of the over-the-air download communication network. In general, the transmission rate of the local network is at least higher than the product of the number of mobile terminals and the over-the-air download rate. Due to the fact that a local network usually has a small coverage radius (e.g., a radius of 10m) but a high transmission rate (e.g., much higher than the transmission rate of a communication network), the mobile terminals described in this embodiment of the present invention should be within the coverage. However, the system network has a lower transmission rate but a wider coverage. [0110]As shown in FIG. 4, a mobile terminal, i.e., as the master mobile terminal, provided in the embodiment of the present invention may include: [0111]a control unit, adapted to control the data download of the individual mobile terminals and implement the sharing of the downloaded data; a download unit, adapted to obtain the size of data to be downloaded and execute a download task in accordance with the download task segments. [0112]The control unit may include: a calculating unit, adapted to calculate the individual task segments for downloading data depending upon the size of the data to be downloaded; a allocating unit, adapted to allocate the individual calculated task segments to the mobile terminals with a predefined algorithm, so that the mobile terminals can execute the download task depending upon the allocated task segments. The allocating unit is also adapted to send the data segments downloaded by a slave mobile terminal to the other slave mobile terminals. [0113]The server is designed to store the data to be downloaded. [0114]It is to be noted that the master mobile terminal must be a mobile terminal according to the embodiments of the present invention, and the slave mobile terminal can be mobile terminals according to the embodiments of the present invention or existing mobile terminals. [0115]In the embodiments of the present invention, multiple mobile terminals are enabled to download data segments of a data respectively and share the downloaded data segments among them, thus the download time may be reduced and the download speed may be increased, for example, if there are N mobile terminals downloading data, the download time may be reduced to 1/N of the time required by a single mobile terminal, and the download speed may be increased u N times, which is adaptive to the playback speed of a movie, thereby meeting the requirement of the users. In addition, the method according to the embodiment of the present invention, compared with the method of downloading entire DATA by each mobile terminal respectively, can save the bandwidth occupied by downloading, since each of the N mobile terminals needs to download only a specific data segment. [0116]A mobile terminal according to the embodiments of the present invention can join a shared download group that meets its data download requirement and has a master mobile terminal within its local connections, by obtaining the location informat(String), 发明领域 [0001] 本发明涉及信息通信技术领域,尤其涉及一种向移动终端下载数据并实现移动终端间数据共享的方法及系统。 背景技术 [0002] 随着移动通信技术的发展,移动终端除了具备基本的通信功能外,还可以用于娱乐,如看电影、下载大型软件等。 由于移动终端的便携性,如果可以使用移动终端进行娱乐,例如在旅途中或在移动服务覆盖的偏远地区,可以拓宽我们的娱乐空间。 移动终端不仅可以用来通过互联网浏览新闻和信息,还可以用来观看电影。 [0003] 现有技术中,移动终端可以通过GPRS(General Packet Radio Service,通用分组无线业务)或拨号上网,并以媒体流的形式下载电影,以供观看电影。 然而,采用这种下载技术,每个移动终端只能单独下载数据。 如果要用多个移动终端观看同一部电影,则每个移动终端都必须分别下载该电影,造成重复下载和带宽的浪费。 另外,采用上述下载技术,下载速度通常低于播放速度,导致观影体验不佳。 此外,由于每个移动终端都要下载电影,因此会占用很大一部分带宽,增加带宽资源的占用时间,从而增加成本。 [0004] 流媒体是一种新兴的网络传输技术,简单来说就是利用流媒体技术在网络上传输多媒体文件。 流媒体技术是一种网络传输技术,通过将连续的视频、音频数据压缩加载到网站的服务器上,使用户边下载边看边听​​,而不是等待整个压缩文件下载到手机上 终端。 [0005] 随着无线技术的发展,无线数据接入的带宽不断增加,移动终端的处理能力不断提高,各种高质量的流媒体服务也日趋成熟。 通过流媒体平台,移动终端可以在音视频流中进行低码率低速播放新闻、电影或音乐,以及在直播业务中播放流媒体; 移动终端可以下载服务和媒体文件。 此外,媒体文件可能受到 DRM(数字版权管理)技术的版权保护。 [0006] 现有技术中,移动终端的玩法是,移动终端先与网络建立连接; 然后,移动终端在实时播放数据流的同时,从网络侧下载流媒体数据流。 该方法的主要特点是实时性强,占用网络带宽大。 [0007] 在实际应用中,经常会出现两个用户希望同时观看同一个流媒体的情况。 采用上述方法,两个用户分别需要建立网络连接,如图1所示。然后,两个用户分别建立无线信道,通过网络下载流媒体。 无线频道的空中接口,分别在本地播放流媒体。 [0008] 在上述移动终端播放流媒体的方法中: [0009] 如果有很多用户同时下载和观看流媒体,可能会导致网络侧设备过载。 [0010] 可能占用太多资源。 当两个用户下载相同的内容时,如果两个用户相距不远,并且在一个基站的同一个小区内,就会造成资源浪费。 此外,不应在一个小区中建立两个多数据连接。 [0011]这种方式在一定程度上抑制了用户观看流媒体的积极性,因为用户不仅要购买版权,还要支付下载费用。 发明内容 [0012] 本发明的目的在于提供一种移动终端数据下载方法、数据下载系统及应用该方法的移动终端。 本发明还提供了一种实现移动终端间数据共享的方法及系统,实现了移动终端间的数据共享和传输。 [0013] 本发明提供了一种向移动终端下载数据的方法,使得移动终端可以在本地连接内加入共享下载。 [0014] 在本发明的一个方面,所述向移动终端下载数据的方法可以包括: [0015] 主移动终端将待下载数据划分为多个数据任务段,将数据任务段分配给一个或多个移动终端; [0016] 移动终端根据分配的数据任务段下载数据; [0017] 主移动终端判断是否有未下载的数据任务段; 若是,则将数据任务段分配给至少一个数据任务段下载完成的移动终端。 如果否,则终止下载过程。 [0018] 优选地,该方法还包括在主移动终端为各个移动终端分配数据任务段之前,通过本地网络从主移动终端向至少一个移动终端发送请求的步骤。 [0019] 优选地,该方法还包括在将数据划分为多个数据任务段之前,主移动终端根据数据大小确定待下载数据的大小并确定数据任务段的大小的步骤。 [0020] 或者,在移动终端在预定时间内没有下载数据任务段的情况下,主移动终端将该数据任务段分配给一个或多个其他移动终端。 [0021] 其中,完成分配的数据任务段下载的移动终端从主移动终端获取一个或多个其他移动终端的ID,并将下载的任务段的数据发送给主移动终端中的一个或多个其他移动终端。 根据获得的ID。 [0022] 优选地,该方法还可以包括以下步骤: [0023] 分配数据任务段下载完成的移动终端向主移动终端上报分配任务段下载完毕的消息; [0024] 主移动终端将该消息通知一个或多个其他移动终端; [0025] 一个或多个其他移动终端从已完成下载分配的数据任务段的移动终端获取下载的数据任务段。 [0026] 优选地,该方法还可以包括以下步骤: [0027] 当主移动终端下载数据任务段时,将下载的数据任务段发送给一个或多个其他移动终端; [0028] 当从移动终端下载了主移动终端分配的数据任务段后,将下载的数据任务段发送给主移动终端; 主移动终端存储数据任务段,并将该数据任务段发送给一个或多个其他移动终端。 [0029] 本发明还提供了一种数据下载系统,该系统包括服务器、至少一个主移动终端和至少一个从移动终端; 其中: [0030] 主移动终端用于控制从移动终端下载数据段,并将主移动终端和/或至少一个从移动终端下载的数据段发送给一个或多个其他移动终端。 [0031]至少一个从移动终端,用于下载主移动终端分配的数据段,并将下载的数据段发送给主移动终端; [0032] 主移动终端通过网络连接到从移动终端中的至少一个; [0033] 服务器用于存储要下载的数据; 每个移动终端通过通信网络连接到服务器以下载数据。 [0034] 其中,网络可以是蓝牙局域网、红外局域网和/或超宽带局域网。 [0035] 本发明还提供了一种移动终端,通过网络连接一个或多个其他移动终端,包括: [0036] 控制单元,用于控制与其连接的移动终端下载数据,并实现下载数据的共享; [0037] 下载单元,用于获取待下载数据的大小,并根据待下载的任务段执行下载任务。 [0038] 优选地,所述控制单元可以包括: [0039] 计算单元,用于计算待下载数据的任务段和待下载数据的大小; [0040] 分配单元,用于将计算出的任务段按照预定规则分配给移动终端,并将移动终端下载的数据段分配给其他一个或多个移动终端。 [0041] 在本发明的另一个方面,所述的移动终端下载数据的方法可以包括以下步骤: [0042] 获取下载组中主移动终端的位置信息以及正在下载的数据的特征信息; [0043] 定位发送数据下载请求的移动终端,并验证是否满足数据下载请求以及主移动终端位于本地连接内的下载组; p 发送数据下载请求的移动终端作为从移动终端加入下载组以便下载数据。 [0044] 优选地,该方法还可以包括: [0045] 下载完成后,将下载组中从移动终端的下载数据发送给主移动终端; 主移动终端将一个或多个其他移动终端下载的数据发送给下载组中的从移动终端。 [0046] 其中,发送数据下载请求的移动终端加入下载组的步骤可以包括: [0047] 下载组中的主移动终端邀请发送数据下载请求的移动终端加入下载组; [0048] 发送数据下载请求的移动终端对主移动终端进行鉴权,鉴权成功则加入下载组。 [0049] 优选地,该方法还可以包括: [0050] 根据下载请求中携带的信息,包括下载数据的ID、类型、大小和定位步骤中获取的位置信息,判断是否满足移动终端的数据下载要求。 [0051] 优选地,该方法还可以包括: [0052] 通过CELL ID或AGPS获取下载组中处于下载状态的主移动终端的位置信息; 和/或 [0053] 通过CELL ID或AGPS定位发送数据下载请求的移动终端。 [0054] 本发明还提供了一种移动终端,包括: [0055] 网络数据流控制模块,用于与网络侧建立连接并从网络侧下载数据,并将下载的数据发送给网络数据存储和控制模块; [0056]网络数据存储及控制模块,用于缓存来自网络数据流控模块的数据,并根据请求报文将缓存的数据发送给本地数据流控模块; [0057] 本地数据流控制模块,用于向网络数据存储与控制模块发送请求消息,并将网络数据存储与控制模块中存储的数据按照预定义的QoS发送给一个或多个其他移动终端。 [0058] 移动终端还可以包括: [0059] 数据共享与通信管理模块,用于接收来自一个或多个其他移动终端的数据连接请求消息,对一个或多个其他移动终端进行鉴权和加密操作,并将鉴权结果发送给本地数据流控制模块。 [0060] 可选的,该终端还可以包括: [0061] 本地应用数据应用模块,用于向网络数据存储与控制模块发送请求,并接收来自网络数据存储与控制模块的数据。 [0062] 本发明还提供了另一种移动终端,包括: [0063] 网络数据存储及控制模块,用于接收和缓存来自主移动终端的数据,并根据请求消息将缓存的数据发送给本地应用数据应用模块和本地数据流控制模块; [0064] 本地应用数据应用模块,用于向网络数据存储与控制模块发送请求消息,并接收来自网络数据存储与控制模块的数据; [0065] 本地数据流控制模块,用于向网络数据存储与控制模块发送请求消息,并将来自网络数据存储与控制模块的数据按照预定义的QoS发送给其他从属移动终端。 [0066] 移动终端还可以包括: [0067] 数据共享与通信管理模块,用于接收其他从属移动终端的数据连接请求消息,对其他从属移动终端进行鉴权和加密控制操作,并将鉴权结果发送给本地数据流控模块。 [0068] 在本发明的另一方面,本发明提供的实现移动终端间数据共享的系统,包括: [0069] 主移动终端,旨在与网络侧建立连接并从网络侧下载数据,以有线或无线方式与从移动终端建立本地数据共享网络,并将下载的数据通过 本地数据共享网络; [0070] 一个或多个从移动终端,用于通过有线或无线方式与主移动终端建立本地数据共享网络,接收来自主移动终端的数据,并将接收到的数据发送给其他从移动终端。 [0071] 主移动终端与所有其他移动终端组成的网络可以是星形结构、链形结构或树形结构。 [0072] 本发明还提供了另一种实现移动终端间数据共享的系统,包括: [0073] 主移动终端,设计用于与网络侧建立连接并从网络侧下载数据,以有线或无线方式与一个或多个从主移动终端建立本地数据共享网络,并将下载的数据发送到从主移动终端 一个或多个从主移动终端通过本地数据共享网络; [0074]一个或多个从主移动终端,用于接收来自主移动终端的流媒体数据并进行相应的数据处理,接收来自一个或多个其他移动终端的数据连接请求,执行接入准入控制操作,例如认证、加密、 等,针对一个或多个其他移动终端,按照预先定义的QoS向一个或多个其他移动终端传输流媒体; 当主移动终端出现异常时,从属主移动终端接收来自一个或多个其他移动终端的共享数据,并替代主移动终端实现下载功能。 [0075] 至少一个移动终端设备,用于与主移动终端以有线或无线方式建立本地数据共享网络,通过本地数据共享网络接收来自主移动终端的数据,并将接收到的数据发送给从主移动终端 移动终端。 [0076] 本发明能够使多个移动终端分别下载一个数据的数据段,并在它们之间共享下载的数据段,从而可以减少下载时间,提高下载速度,例如,如果有N个移动终端 终端下载数据,下载时间可以减少到单个移动终端所需时间的1/N,下载速度可以提高uN倍,自适应电影播放速度,提升体验 的用户。 [0077] 通过定位发送数据下载请求的移动终端,根据主移动终端的位置信息验证是否满足移动终端的数据下载要求,以及主移动终端是否位于本地连接内的共享下载组中 共享下载组中的移动终端和正在下载的数据的特征信息,使得发送数据下载请求的移动终端作为从移动终端加入共享下载组并进行共享数据下载。 在本发明中,移动终端可以随时加入本地网络中合适的共享下载组,而不需要与其他移动终端协商。 因此,可以降低共享数据下载的实现难度,提高共享数据下载的适用性。 [0078] 可见,采用上述技术方案,可以节省网络资源,降低网络侧设备的负载,实现一个移动终端下载流媒体的同时,实现多个移动终端播放流媒体。 媒体,从而降低移动终端下载数据的成本。 附图的简要说明 [0079] 图1为现有技术中两个用户分别接入网络的示意图; [0080] 图2是本发明一个实施例的下载方法的流程图; [0081] 图3是根据本发明一个实施例的下载系统的流程图; [0082] 图4是本发明一个实施例的移动终端的示意图; [0083] 图5为本发明另一实施例的移动终端数据下载方法的流程图。 [0084] 图6示出了根据本发明实施例的移动终端之间的数据共享方法的原理。 [0085] 图7为本发明实施例的移动终端间数据共享方法的处理流程图; [0086] 图8是主移动终端和从移动终端组成的串联结构示意图; [0087] 图9是主移动终端和从移动终端组成的星形结构示意图; [0088] 图10是本发明一个实施例的主移动终端的结构图; [0089] 图11为本发明实施例的从移动终端的结构图; [0090] 图12为本发明实施例的系统结构图; [0091] 图13为本发明另一实施例的系统结构图。 具体实施方式 [0092] 本发明实施例提供的移动终端数据下载方法及其配套系统利用多个移动终端分别下载数据的各个数据段,其中一个移动终端(也称为主移动终端) ) 控制下载进度并将每个移动终端下载的数据发送给其他移动终端。 从而,可以加速下载。 本发明实施例的移动终端数据共享方法及系统的核心思想是,移动终端与网络侧建立连接下载流媒体,其他移动终端接收并播放流媒体。 媒体通过本地数据共享网络。 [0093] 下面将参考附图描述本发明的实施例。 [0094] 这里我们假设移动终端 A, B, C, . . . , 和 N 希望从服务器获取数据“DATA”。 移动终端A、B、C、……。 . . ,N通过通信网络(如3G网络、GPRS网络等)下载数据。 移动终端A、B、C、……。 . . , 和 N 通过高速本地网络连接,可以是蓝牙、红外或 UWB 技术构建的本地网络。 无线下载要求本地网络的传输速率远高于通信网络的传输速率。 更一般地,本地网络的传输速率至少高于移动终端数量与空中下载速率的乘积。 [0095] 由于本地网络通常具有较小的覆盖半径(例如半径为10 m)但传输速率较高(例如远高于通信网络的传输速率),因此在本文中描述的移动终端 本发明应在保护范围之内。 相比之下,系统网络的传输速率较低,但覆盖范围较广。 [0096] 为了实施本发明实施例,移动终端A、B、C、...中的一个。 . . , N 被指定为主移动终端。 该主移动终端只进行数据下载,还分配数据下载任务段,将下载任务分发给其他移动终端。 其他移动终端被指定为从移动终端,主要负责数据下载。 [0097] 为简化描述,这里假设移动终端A为主移动终端,移动终端B、C、...。 . . ,和N为从属移动终端,如图2所示。以下是移动终端A,B,C,...的过程。 . . , 和 N 协作进行数据下载将被描述。 [0098] 脚步 01 ,主移动终端A向移动终端B,C,...发出邀请。 . . , N 通过本地网络进行数据下载。 [0099] 脚步 02 ,部分或全部从属移动终端B,C,。 . . , N接受主移动终端A的邀请。主移动终端A记录接受邀请的从移动终端的ID。 为了简化描述,下面假设所有从移动终端都接受了主移动终端A的邀请。 [0100] 脚步 03 ,主移动终端A从服务器获取待下载DATA文件的大小信息。 [0101] 脚步 04 ,主移动终端A计算移动终端A,B,C,...需要下载的任务段。 . . , 和 N 具有预定义的算法。 [0102]该算法可以是平均分配算法,即将下载DATA的任务分成若干个(例如M,这里假设N<1)确定)时,则认为该移动终端发生故障。 在这种情况下,主移动终端可以将已经分配给该移动终端的数据任务段重新分配给另一个移动终端。 [0106] 脚步 07 ,当一个移动终端完成分配的任务段的下载后,使其他移动终端能够获取下载的任务段数据。 在本发明实施例中,可以通过三种方式使其他移动终端获取下载的任务段数据。 第一种方式,移动终端将下载的任务段数据发送给其他从属移动终端。 此时,移动终端需要从主移动终端A获取参与下载的所有从移动终端的ID,然后根据移动终端ID发送任务段数据。 第二种方式,移动终端向主移动终端上报任务段下载完成消息,主移动终端再将该消息通知给其他从移动终端,以便其他从移动终端可以从该移动终端获取下载的数据。 第三种方式,当从属移动终端B,C,...。 . . , N完成主移动终端A分配的任务段,下载的任务段数据将发送给主移动终端A。主移动终端A存储从移动终端B、C、 . . . , 或 N, 将数据发送给其他从属移动终端。 当自己的任务段完成后,主移动终端A存储任务段数据,并将数据发送给从移动终端B、C、...。 . . , 和 N. [0107] 脚步 08,主移动终端A判断“DATA”下载是否完成。 如果下载完成,则主移动终端A终止下载过程。 否则,主移动终端A执行步骤S 05 ,即主移动终端A将未完成的任务段分配给完成任务段的移动终端,S 05 -S 08 如此反复,直到下载完成。 [0108] 图3示出了本发明实施例提供的数据下载系统。 该系统包括存储和管理待下载数据的服务器和至少两个移动终端。 [0109] 其中至少一个移动终端为主移动终端,用于控制其他移动终端下载数据段,并将下载的数据发送给移动终端。 从移动终端,用于下载主移动终端分配的数据段,并将下载的数据段发送给主移动终端。 移动终端之间通过局域网连接,并通过通信网络(例如3G网络、GPRS网络等)连接到服务器,从服务器下载数据。 本地网络是一种高速本地无线网络,例如使用Blue Teeth、红外线或UWB(Ultra Wide Band)技术构建的本地网络,其传输速率远高于空中下载通信。 网络。 一般来说,本地网络的传输速率至少要高于移动终端数量与无线下载速率的乘积。 由于本地网络通常覆盖半径小(如10m半径),但传输速率高(如远高于通信网络的传输速率),本实施例描述的移动终端 本发明应在保护范围之内。 但系统网络传输速率较低,但覆盖范围较广。 [0110] 如图4所示,本发明实施例提供的移动终端,即作为主移动终端,可以包括: [0111] 控制单元,用于控制各个移动终端的数据下载,并实现下载数据的共享; 下载单元,用于获取待下载数据的大小,并根据下载任务段执行下载任务。 [0112] 控制单元可以包括: 计算单元,用于根据待下载数据的大小计算下载数据的各个任务段; 分配单元,用于将计算出的各个任务段按照预定算法分配给移动终端,使得移动终端可以根据分配的任务段执行下载任务。 分配单元还用于将从移动终端下载的数据段发送给其他从移动终端。 [0113] 服务器用于存储要下载的数据。 [0114] 需要说明的是,主移动终端必须是本发明实施例提供的移动终端,从移动终端可以是本发明实施例提供的移动终端,也可以是现有的移动终端。 [0115] 本发明实施例能够使多个移动终端分别下载一个数据的数据段,并在它们之间共享下载的数据段,从而可以减少下载时间,提高下载速度,例如,如果有 当N个移动终端下载数据时,下载时间可以减少到单个移动终端所需时间的1/N,下载速度可以提高uN倍,自适应电影的播放速度,从而 满足用户的需求。 另外,根据本发明实施例的方法,与每个移动终端分别下载整个DATA的方法相比,可以节省下载所占用的带宽,因为N个移动终端中的每一个只需要下载一个特定的数据。 部分。 [0116]本发明实施例的移动终端通过获取主移动终端在共享下载组中的位置信息,可以加入满足自身数据下载需求且本地连接内有主移动终端的共享下载组。 正在下载的数据的特征信息。 [0117] 下面,将参照附图描述根据本发明实施例的另一种用于将数据下载到移动终端的方法。 [0118] 共享下载组中的移动终端通过通信网络(例如3G网络、GPRS网络等)从服务器下载数据。 共享下载组中有主控移动端。 主移动终端不仅进行数据下载,还分配下载任务,将下载任务分发给其他移动终端。 其他移动终端作为从移动终端,主要负责自己的下载任务。 共享下载组中的移动终端通过本地网络相互连接,本地网络是采用蓝牙、红外或UWB(超宽带)技术构建的高速本地网络,传输速率远高于普通网络。 的通信网络。 [0119] 图5为本发明实施例提供的另一种移动终端数据下载方法的流程图; 其中数据下载流程如下: [0120] 脚步 10 、服务器获取并存储处于共享下载状态的共享下载组中的主移动终端的位置信息以及正在下载的数据的特征信息。 特征信息包括正在下载的数据的文件名、类型和大小。 [0121] 本发明实施例中,服务器可以利用CELL ID或AGPS(Assisted Global Positioning System)获取主移动终端的位置信息,下面分别进行说明: [0122] 通过CELL ID获取主移动终端位置信息的原理是:服务器根据当前服务基站的位置和小区覆盖范围定位主移动终端; 若小区为全向小区,则主移动终端位于以服务基站为圆心、小区覆盖半径为半径的圆内。 如果小区是定向小区,则可以进一步确定主移动终端所在的扇区。 [0123] 利用AGPS获取主移动终端位置信息的原理是:主移动终端利用AGPS信息捕获卫星信号并接收测量信息,然后将测量信息发送给定位服务中心 ,它计算出移动终端的当前位置并将信息发送到服务器。 [0124] 脚步 11 , 服务器接收到移动终端X的数据下载请求后,通过CELL ID或AGPS定位移动终端X。 [0125] 脚步 12 , 根据信息(即文件名、类型、 和下载数据的大小)以及通过定位获得的位置信息。 这里假设,在确定的共享下载组Y中,移动终端A为主移动终端,移动终端B、C、...。 . . , 和 N 是从属移动终端。 [0126] 脚步 13 ,服务器向共享下载组Y中的主移动终端A发送通知,通知移动终端X要加入共享下载组。 [0127] 脚步 14 ,主移动终端A邀请移动终端X加入共享下载组Y [0128] 脚步 15,移动终端X接受邀请并对主移动终端A进行鉴权,鉴权成功则移动终端X加入共享下载组Y并执行步骤S 16 ; 若鉴权失败,则移动终端X无法加入分享下载组,流程结束。 [0129] 移动终端X可以通过多种认证方式对主移动终端A进行认证。 例如,在步骤S 11 ,移动终端X在向服务器发送数据下载请求时,生成一个随机数并将该随机数发送给服务器。 在步骤S 13 ,服务器将通知连同随机数发送给主移动终端A。主移动终端A在邀请移动终端X加入分享下载组时将该随机数发送给移动终端X。 移动终端X收到随机数后,与本地存储的随机数进行比较; 如果两个随机数相同,则移动终端X认为主移动终端认证成功。 否则认为认证失败。 [0130] 小号 16 ,主移动终端A向组内的从移动终端发送查询消息,查询各从移动终端当前的下载进度,然后根据各从移动终端的下载情况确定剩余待下载数据的大小 从移动终端。 [0131] 脚步 17 ,主移动终端A根据步骤S确定的剩余数据大小,重新分配下载任务给共享下载组中的所有移动终端,包括移动终端X 16 ; [0132] 主移动终端A可以采用平均分配算法对下载任务进行重新分配,即将下载任务分成若干(例如M,这里假设N< Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AT467191T(String), DE602006014067D1(String), DE602006014067T2(String), EP1752886A1(String), EP1752886B1(String), US20070037563A1(String), US7941123B2(String), WO2007019770A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AT467191T(String), DE602006014067D1(String), DE602006014067T2(String), EP1752886A1(String), EP1752886B1(String), US20070037563A1(String), US7941123B2(String), WO2007019770A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7941123B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AT467191T(String), DE602006014067D1(String), DE602006014067T2(String), EP1752886A1(String), EP1752886B1(String), US20070037563A1(String), US7941123B2(String), WO2007019770A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.235 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), AT467191T(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), DE602006014067D1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), DE602006014067T2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), EP1752886A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), EP1752886B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), US20070037563A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), US7941123B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271647(Integer), WO2007019770A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7941123B2(String), US7941123B2(String), 1304956800(Integer), 271647(Integer), 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185938(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185938(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.737 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.737 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185938(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185938(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:40.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185938(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9906723B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for selection between front-facing camera and rear-facing camera of mobile terminal and mobile terminal(String), 移动终端前置摄像头和后置摄像头选择方法及移动终端(String), US9906723B2(String), A method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which are used to implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal is presented. The method in the embodiments of the present disclosure includes receiving, by a mobile terminal, a photographing request initiated by a user; determining, by the mobile terminal, a distance between the mobile terminal and the user; and if the distance is greater than or equal to a preset numeric value, turning on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turning on a rear-facing camera of the mobile terminal. The embodiments of the present disclosure can implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal.(String), 提出了一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,用于实现移动终端前置摄像头和后置摄像头的自动选择。 . 本发明实施例的方法包括:移动终端接收用户发起的拍照请求; 移动终端确定移动终端与用户的距离; 若距离大于或等于预设数值,则开启移动终端的前置摄像头。 或者如果距离小于预设数值,则开启移动终端的后置摄像头。 本发明实施例可以实现移动终端前置摄像头和后置摄像头的自动选择。(String), US15/220564(String), 1469548800(Integer), US9906723B2(String), 1519660800(Integer), 1519660800(Integer), 美国(String), 4(Integer), CN(String), 8(Integer), 35(Integer), CN101299847A | CN101299847B | CN101521696A | CN102629979A | CN102685306A | CN103037083A | CN103227869A | CN103391366A | CN103516900A | CN103795864A | EP2661068A2 | JP2003298884A | JP2005217768A | JP2007032117A | JP2007312039A | JP2009132664A | JP2012522415A | JP2013526099A | JP2013536240A | KR1020090007166A | KR1020110056094A | US20070019000A1 | US20090017867A1 | US20100245287A1 | US20110216209A1 | US20120081592A1 | US20130002722A1 | US20140118600A1 | US20140139667A1 | US20160373646A1 | US6864912B1 | US8451312B2(String), 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185939(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2590048e35d44f83b1fb8aa9b5d88829.png(String), 185939(Integer), 2590048e35d44f83b1fb8aa9b5d88829.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for selection between front-facing camera and rear-facing camera of mobile terminal and mobile terminal(String), 移动终端前置摄像头和后置摄像头选择方法及移动终端(String), US9906723B2(String), A method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which are used to implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal is presented. The method in the embodiments of the present disclosure includes receiving, by a mobile terminal, a photographing request initiated by a user; determining, by the mobile terminal, a distance between the mobile terminal and the user; and if the distance is greater than or equal to a preset numeric value, turning on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turning on a rear-facing camera of the mobile terminal. The embodiments of the present disclosure can implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal.(String), 提出了一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,用于实现移动终端前置摄像头和后置摄像头的自动选择。 . 本发明实施例的方法包括:移动终端接收用户发起的拍照请求; 移动终端确定移动终端与用户的距离; 若距离大于或等于预设数值,则开启移动终端的前置摄像头。 或者如果距离小于预设数值,则开启移动终端的后置摄像头。 本发明实施例可以实现移动终端前置摄像头和后置摄像头的自动选择。(String), US15/220564(String), 1469548800(Integer), US9906723B2(String), 1519660800(Integer), 1519660800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 8(Integer), 35(Integer), CN101299847A | CN101299847B | CN101521696A | CN102629979A | CN102685306A | CN103037083A | CN103227869A | CN103391366A | CN103516900A | CN103795864A | EP2661068A2 | JP2003298884A | JP2005217768A | JP2007032117A | JP2007312039A | JP2009132664A | JP2012522415A | JP2013526099A | JP2013536240A | KR1020090007166A | KR1020110056094A | US20070019000A1 | US20090017867A1 | US20100245287A1 | US20110216209A1 | US20120081592A1 | US20130002722A1 | US20140118600A1 | US20140139667A1 | US20160373646A1 | US6864912B1 | US8451312B2(String), \20230420\2590048e35d44f83b1fb8aa9b5d88829.png(String), 22(Integer), 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 1. A method for selection between a front-facing camera and a rear-facing camera of a mobile terminal, comprising:receiving, by the mobile terminal, a photographing request initiated by a user;determining, by the mobile terminal, a distance between the mobile terminal and the user; andturning on the front-facing camera of the mobile terminal when the distance is greater than or equal to a preset numeric value; andturning on the rear-facing camera of the mobile terminal when the distance is less than the preset numeric value.(String), 1.根据权利要求1所述的方法,其中在开启移动终端的前置摄像头之前或开启移动终端的后置摄像头之前,该方法还包括:向用户发送查询请求,查询请求用于询问用户是否同意开启前置摄像头或后置摄像头;获取用户的回复;当回复为同意开启前置摄像头或后置摄像头或在一段时间内没有收到回复时,触发开启移动终端的前置摄像头或移动终端的后置摄像头预设时间段;和当回复拒绝开启前置摄像头或后置摄像头时,触发移动终端的默认动作。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 2. The method according to claim 1, wherein the determining, by the mobile terminal, a distance between the mobile terminal and the user comprises determining, by the mobile terminal, a distance between the mobile terminal and a face of the user.(String), 12.移动终端,包括:一个前置摄像头和一个后置摄像头;接收器,用于接收用户发起的拍照请求;和处理器配置为:确定移动终端与用户之间的距离;当距离大于或等于预设数值时,开启移动终端的前置摄像头;和当距离小于预设数值时,开启移动终端的后置摄像头。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 3. The method according to claim 2, wherein determining, by the mobile terminal, the distance between the mobile terminal and the face of the user comprises:determining, by the mobile terminal, a distance between the mobile terminal and a preset position on the face of the user; ordetermining, by the mobile terminal, an overall distance between the mobile terminal and at least two preset positions on the face of the user.(String), 13.根据权利要求12所述的移动终端,其中处理器还用于确定移动终端与用户面部之间的距离。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 4. The method according to claim 1, wherein the preset numeric value is set by the mobile terminal by default.(String), 14.根据权利要求13所述的移动终端,其中处理器还被配置为:确定移动终端与用户面部预设位置之间的距离;和确定移动终端与用户面部至少两个预设位置之间的总体距离。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 5. The method according to claim 4, wherein the photographing request comprises at least a first application request and a second application request; wherein the preset numeric value is a first preset numeric value when the photographing request is the first application request; wherein the preset numeric value is a second preset numeric value when the photographing request is the second application request, and wherein the first preset numeric value is different from the second preset numeric value.(String), 15.根据权利要求12所述的移动终端,其中该预设数值由移动终端默认设置。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 6. The method according to claim 5, further comprising:acquiring a first probability and a second probability, wherein the first probability is a probability of using the front-facing camera in a first application state, and wherein the second probability is a probability of using the front-facing camera in a second application state; andseparately adjusting the first preset numeric value and the second preset numeric value according to the first probability and the second probability, such that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value.(String), 16.根据权利要求15所述的移动终端,其中拍摄请求至少包括第一应用请求和第二应用请求,其中,当拍摄请求为第一应用请求时,预设数值为第一预设数值,当拍摄请求为第一应用请求时,预设数值为第二预设数值。拍照请求为第二应用请求,其中第一预设数值与第二预设数值不同。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 7. The method according to claim 4, further comprising:acquiring, by the mobile terminal, usage information about the user's usage of the front-facing camera and the rear-facing camera; andadjusting the preset numeric value according to the usage information.(String), 17.根据权利要求16所述的移动终端,其中处理器还被配置为:获取第一概率和第二概率,其中第一概率为用户在第一应用状态下使用前置摄像头的概率,第二概率为用户使用前置摄像头的概率处于第二应用状态;和根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。(String), 1(Integer), 6(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 8. The method according to claim 4, further comprising:acquiring, by the mobile terminal, personal information of the user; andadjusting the preset numeric value according to the personal information.(String), 18.根据权利要求15所述的移动终端,其中处理器还被配置为:获取用户使用前置摄像头和后置摄像头的使用信息;和根据使用信息调整预设数值。(String), 1(Integer), 7(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 9. The method according to claim 4, further comprising:acquiring, by the mobile terminal, a factor of an environment in which the mobile terminal is currently located; andadjusting the preset numeric value according to the factor of the environment in which the user is currently located.(String), 19.根据权利要求15所述的移动终端,其中处理器还被配置为:获取用户的个人信息;和根据个人信息调整预设数值。(String), 1(Integer), 8(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 10. The method according to claim 1, further comprising acquiring the preset numeric value from the user prior to determining the distance between the mobile terminal and the user.(String), 20.根据权利要求15所述的移动终端,其中处理器还被配置为:获取用户当前所处环境的因素;和根据用户当前所处环境因素调整预设数值。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 11. The method according to claim 1, wherein before the turning on the front-facing camera of the mobile terminal or before the turning on the rear-facing camera of the mobile terminal, the method further comprises:sending an inquiry request to the user, wherein the inquiry request is used to ask the user whether to agree to turn on the front-facing camera or the rear-facing camera;acquiring a reply from the user;triggering the turning on of the front-facing camera of the mobile terminal or the rear-facing camera of the mobile terminal when the reply is agreeing to turn on the front-facing camera or the rear-facing camera or no reply is received within a preset time period; andtriggering a default action of the mobile terminal when the reply is refusing to turn on the front-facing camera or the rear-facing camera.(String), 21.根据权利要求12所述的移动终端,其中处理器还用于在确定移动终端与用户之间的距离之前,获取用户的预设数值。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 12. A mobile terminal, comprising:a front-facing camera and a rear-facing camera;a receiver configured to receive a photographing request initiated by a user; anda processor configured to:determine a distance between the mobile terminal and the user;turn on the front-facing camera of the mobile terminal when the distance is greater than or equal to a preset numeric value; andturn on the rear-facing camera of the mobile terminal when the distance is less than the preset numeric value.(String), 22.根据权利要求12所述的移动终端,其中处理器还被配置为:向用户发送查询请求,查询请求用于询问用户是否同意开启前置摄像头或后置摄像头;获取用户的回复;当回复为同意开启前置摄像头或后置摄像头时,触发开启移动终端前置摄像头或开启移动终端后置摄像头;和当回复拒绝开启前置摄像头或后置摄像头时,触发移动终端的默认动作。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 13. The mobile terminal according to claim 12, wherein the processor is further configured to determine a distance between the mobile terminal and a face of the user.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 14. The mobile terminal according to claim 13, wherein the processor is further configured to:determine a distance between the mobile terminal and a preset position on the face of the user; anddetermine an overall distance between the mobile terminal and at least two preset positions on the face of the user.(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 15. The mobile terminal according to claim 12, wherein the preset numeric value is set by the mobile terminal by default.(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 16. The mobile terminal according to claim 15, wherein the photographing request comprises at least a first application request and a second application request, wherein the preset numeric value is a first preset numeric value when the photographing request is the first application request, wherein the preset numeric value is a second preset numeric value when the photographing request is the second application request, and wherein the first preset numeric value is different from the second preset numeric value.(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 17. The mobile terminal according to claim 16, wherein the processor is further configured to:acquire a first probability and a second probability, wherein the first probability is a probability of using the front-facing camera by the user in a first application state, and wherein the second probability is a probability of using the front-facing camera by the user in a second application state; andseparately adjust the first preset numeric value and the second preset numeric value according to the first probability and the second probability, such that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value.(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 18. The mobile terminal according to claim 15, wherein the processor is further configured to:acquire usage information about the user's usage of the front-facing camera and the rear-facing camera; andadjust the preset numeric value according to the usage information.(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 19. The mobile terminal according to claim 15, wherein the processor is further configured to:acquire personal information of the user; andadjust the preset numeric value according to the personal information.(String), 1(Integer), 18(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 20. The mobile terminal according to claim 15, wherein the processor is further configured to:acquire a factor of an environment in which the user is currently located; andadjust the preset numeric value according to the factor of the environment in which the user is currently located.(String), 1(Integer), 19(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 21. The mobile terminal according to claim 12, wherein the processor is further configured to acquire the preset numeric value from the user prior to determining the distance between the mobile terminal and the user.(String), 1(Integer), 20(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:41.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185939(Integer), 22. The mobile terminal according to claim 12, wherein the processor is further configured to:send an inquiry request to the user, wherein the inquiry request is used to ask the user whether to agree to turn on the front-facing camera or the rear-facing camera;acquire a reply from the user;trigger turning on the front-facing camera of the mobile terminal or turning on the rear-facing camera of the mobile terminal when the reply is agreeing to turn on the front-facing camera or the rear-facing camera; andtrigger a default action of the mobile terminal when the reply is refusing to turn on the front-facing camera or the rear-facing camera.(String), 1(Integer), 21(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185939(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a continuation of International Application No. PCT/CN2014/081100, filed on Jun. 30, 2014, which claims priority to Chinese Patent Application No. 201410043609.7, filed on Jan. 29, 2014, both of which are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of mobile communications, and in particular, to a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal. BACKGROUND [0003]Front-facing and rear-facing cameras are generally configured on existing mobile terminals (especially, mobile phones), where the rear-facing camera has many functions and is used mostly for photographing scenery and other people, while the front-facing camera is usually used only for self-photographing and video calling. [0004]When a user turns on a camera, an existing terminal generally turns on the rear-facing camera by default. When the user needs to switch to the front-facing camera, the user usually taps an independent button on a screen to implement a switch between the front-facing camera and the rear-facing camera. [0005]However, this manner requires the user to perform manual switching, and is rather complex. SUMMARY [0006]Embodiments of the present disclosure provide a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which can implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal. [0007]A first aspect of the embodiments of the present disclosure provides a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal, including receiving, by a mobile terminal, a photographing request initiated by a user; determining, by the mobile terminal, a distance between the mobile terminal and the user; and if the distance is greater than or equal to a preset numeric value, turning on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turning on a rear-facing camera of the mobile terminal. [0008]With reference to the first aspect of the embodiments of the present disclosure, in a first implementation manner of the first aspect of the embodiments of the present disclosure, the determining, by the mobile terminal, a distance between the mobile terminal and the user includes determining, by the mobile terminal, a distance between the mobile terminal and a face of the user. [0009]With reference to the first implementation manner of the first aspect of the embodiments of the present disclosure, in a second implementation manner of the first aspect of the embodiments of the present disclosure, the determining, by the mobile terminal, a distance between the mobile terminal and a face of the user includes determining, by the mobile terminal, a distance between the mobile terminal and a preset position on the face of the user; or determining, by the mobile terminal, an overall distance between the mobile terminal and at least two preset positions on the face of the user. [0010]With reference to the first aspect of the embodiments of the present disclosure, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a third implementation manner of the first aspect of the embodiments of the present disclosure, the preset numeric value is set by the mobile terminal by default. [0011]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in a fourth implementation manner of the first aspect of the embodiments of the present disclosure, the photographing request includes at least a first application request and a second application request; when the photographing request is the first application request, the preset numeric value is a first preset numeric value; when the photographing request is the second application request, the preset numeric value is a second preset numeric value; and the first preset numeric value is different from the second preset numeric value. [0012]With reference to the fourth implementation manner of the first aspect of the embodiments of the present disclosure, in a fifth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring a first probability and a second probability, where the first probability is a probability of using the front-facing camera in a first application state, and the second probability is a probability of using the front-facing camera in a second application state; and separately adjusting the first preset numeric value and the second preset numeric value according to the first probability and the second probability, so that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value. [0013]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in a sixth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring, by the mobile terminal, information about the user's usage of the front-facing camera and the rear-facing camera, and adjusting the preset numeric value according to the usage information. [0014]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in a seventh implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring, by the mobile terminal, personal information of the user, and adjusting the preset numeric value according to the personal information. [0015]With reference to the third implementation manner of the first aspect of the embodiments of the present disclosure, in an eighth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring, by the mobile terminal, a factor of an environment in which the user is currently located, and adjusting the preset numeric value according to the factor of the environment in which the user is currently located. [0016]With reference to the first aspect of the embodiments of the present disclosure, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a ninth implementation manner of the first aspect of the embodiments of the present disclosure, the method further includes acquiring the preset numeric value entered by the user. [0017]With reference to the first aspect of the embodiments of the present disclosure, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a tenth implementation manner of the first aspect of the embodiments of the present disclosure, before the turning on a front-facing camera of the mobile terminal or before the turning on a rear-facing camera of the mobile terminal, the method further includes sending an inquiry request to the user, where the inquiry request is used to ask the user whether to agree to turn on the camera; acquiring a reply from the user; and when the reply is agreeing to turn on the camera or no reply is received within a preset time period, triggering the turning on of the front-facing camera of the mobile terminal or the rear-facing camera of the mobile terminal; or when the reply is refusing to turn on the camera, triggering a default action of the mobile terminal. [0018]A second aspect of the embodiments of the present disclosure provides a mobile terminal, including a front-facing camera and a rear-facing camera; a receiving module configured to receive a photographing request initiated by a user; a determining module configured to determine a distance between the mobile terminal and the user; and a control module configured to, when the distance is greater than or equal to a preset numeric value, turn on the front-facing camera of the mobile terminal; or when the distance is less than the preset numeric value, turn on the rear-facing camera of the mobile terminal. [0019]With reference to the second aspect of the embodiments of the present disclosure, in a first implementation manner of the second aspect of the embodiments of the present disclosure, the determining module is configured to determine a distance between the mobile terminal and a face of the user. [0020]With reference to the first implementation manner of the second aspect of the embodiments of the present disclosure, in a second implementation manner of the second aspect of the embodiments of the present disclosure, the determining module is configured to determine a distance between the mobile terminal and a preset position on the face of the user; or the determining module is configured to determine an overall distance between the mobile terminal and at least two preset positions on the face of the user. [0021]With reference to the second aspect, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in a third implementation manner of the second aspect of the embodiments of the present disclosure, the preset numeric value is set by the mobile terminal by default. [0022]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in a fourth implementation manner of the second aspect of the embodiments of the present disclosure, the photographing request includes at least a first application request and a second application request; when the photographing request is the first application request, the preset numeric value is a first preset numeric value; when the photographing request is the second application request, the preset numeric value is a second preset numeric value; and the first preset numeric value is different from the second preset numeric value. [0023]With reference to the fourth implementation manner of the second aspect of the embodiments of the present disclosure, in a fifth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a first acquiring module configured to acquire a first probability and a second probability, where the first probability is a probability of using the front-facing camera by the user in a first application state, and the second probability is a probability of using the front-facing camera by the user in a second application state; and a first adjusting module configured to separately adjust the first preset numeric value and the second preset numeric value according to the first probability and the second probability, so that the first probability corresponds to the first preset numeric value and the second probability corresponds to the second preset numeric value. [0024]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in a sixth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a second acquiring module configured to acquire information about the user's usage of the front-facing camera and the rear-facing camera; and a second adjusting module configured to adjust the preset numeric value according to the usage information. [0025]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in a seventh implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a third acquiring module configured to acquire personal information of the user, and adjust the preset numeric value according to the personal information; and a third adjusting module configured to adjust the preset numeric value according to the personal information. [0026]With reference to the third implementation manner of the second aspect of the embodiments of the present disclosure, in an eighth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a fourth acquiring module configured to acquire a factor of an environment in which the user is currently located; and a fourth adjusting module configured to adjust the preset numeric value according to the factor of the environment in which the user is currently located. [0027]With reference to the second aspect of the embodiments of the present disclosure, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in a ninth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes a fifth acquiring module configured to acquire the preset numeric value entered by the user. [0028]With reference to the second aspect of the embodiments of the present disclosure, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in a tenth implementation manner of the second aspect of the embodiments of the present disclosure, the mobile terminal further includes an inquiry module configured to send an inquiry request to the user, where the inquiry request is used to ask the user whether to agree to turn on the camera; a sixth acquiring module configured to acquire a reply from the user; a first triggering unit configured to, when the reply is agreeing to turn on the camera, trigger the control module to turn on the front-facing camera of the mobile terminal or turn on the rear-facing camera of the mobile terminal; and a second triggering unit configured to, when the reply is refusing to turn on the camera, trigger a default action of the mobile terminal. [0029]It can be seen from the foregoing technical solutions that the embodiments of the present disclosure have the following advantages. [0030]In the embodiments of the present disclosure, it is determined whether a distance between a mobile terminal and a user is greater than a preset numeric value, so as to automatically determine whether to turn on a front-facing camera of the mobile terminal or turn on a rear-facing camera of the mobile terminal, thereby implementing automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal, avoiding a case in which the user needs to perform manual selection, and improving user experience for the mobile terminal. BRIEF DESCRIPTION OF DRAWINGS [0031]FIG. 1 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure; [0032]FIG. 2 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0033]FIG. 3 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0034]FIG. 4 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0035]FIG. 5 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0036]FIG. 6 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0037]FIG. 7 is a flowchart of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to another embodiment of the present disclosure; [0038]FIG. 8 is a schematic diagram of a mobile terminal according to an embodiment of the present disclosure; [0039]FIG. 9 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0040]FIG. 10 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0041]FIG. 11 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0042]FIG. 12 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0043]FIG. 13 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0044]FIG. 14 is a schematic diagram of a mobile terminal according to another embodiment of the present disclosure; [0045]FIG. 15 is a schematic diagram of a mobile phone according to an embodiment of the present disclosure; and [0046]FIG. 16 is a structural diagram of an inner part of a mobile phone according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0047]Embodiments of the present disclosure provide a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal and a mobile terminal, which are used to implement automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal. [0048]To make persons skilled in the art understand the technical solutions in the present disclosure better, the following clearly and completely describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Thespe described embodiments are merely a part rather than all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]In the specification, claims, and accompanying drawings of the present disclosure, the terms “first”, “second”, “third”, “fourth”, and so on (if existent) are intended to distinguish between similar objects but do not necessarily indicate a specific order or sequence. It should be understood that the data termed in such a way are interchangeable in proper circumstances so that the embodiments of the present disclosure described herein can be implemented in other orders than the order illustrated or described herein. Moreover, the terms “include”, “contain” and any other variants mean to cover the non-exclusive inclusion, for example, a process, method, system, product, or device that includes a list of steps or units is not necessarily limited to those units, but may include other units not expressly listed or inherent to such a process, method, system, product, or device. [0050]Referring to FIG. 1, an embodiment of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure includes the following steps. [0051]Step 101. A mobile terminal receives a photographing request initiated by a user. [0052]The mobile terminal may be a mobile phone, a tablet computer, or another mobile terminal having a camera, where a front-facing camera and a rear-facing camera are disposed on the mobile terminal, the front-facing camera refers to a camera that is located at a same side as a display screen of the mobile terminal, and the rear-facing camera refers to a camera that is located at the other side of the mobile terminal opposite to the display screen of the mobile terminal. When a user needs to take a picture, the user may trigger a photographing function of the mobile terminal. The mobile terminal receives a photographing request initiated by the user, and prepares to turn on a camera to enter a photographing state. [0053]Step 102. The mobile terminal determines a distance between the mobile terminal and the user. [0054]A distance measurement module that can measure a distance between the mobile terminal and the user is disposed in the mobile terminal, where the distance measurement module may be an independently disposed distance sensor or proximity sensor, or may be a distance sensor that is configured in the camera of the mobile terminal to implement an automatic focus function. Certainly, in an actual application, the distance measurement module may be another sensor or module that can implement the same function. [0055]It should be noted that, there are two cases herein. In a first case, the camera of the mobile terminal is off when the user initiates the photographing request to the mobile terminal. The mobile terminal determines a distance between the mobile terminal and the user when the user initiates the photographing request to the mobile terminal, so as to determine, according to the distance, whether to turn on the front-facing camera or turn on the rear-facing camera. The mobile terminal may first turn on a default camera after receiving the photographing request initiated by the user, and then determine, according to the distance, whether to switch to or additionally turn on the front-facing camera or the rear-facing camera, or directly determine, according to the distance, whether to turn on the front-facing camera or the rear-facing camera, which is not limited herein. [0056]In the first case, the distance measurement module may detect the distance between the mobile terminal and the user all the time, and when receiving the photographing request initiated by the user, the mobile terminal determines a current distance according to the distance measurement module thereof; or the distance measurement module detects the distance between the mobile terminal and the user only when the screen is on, and when receiving the photographing request initiated by the user, the mobile terminal determines a current distance according to the distance measurement module thereof; or the distance measurement module may detect a current distance between the mobile terminal and the user only when the mobile terminal receives the photographing request initiated by the user, and the mobile terminal determines, according to the distance measurement module thereof, the distance measured by the distance measurement module. [0057]In a second case, when receiving the photographing request initiated by the user, the mobile terminal is currently in a photographing state. In the whole photographing process of the mobile terminal, the distance measurement module detects the distance between the mobile terminal and the user in real time; the mobile terminal determines a current distance according to the distance measurement module thereof, and determines, according to the distance, whether to switch from a currently used camera to the other camera or whether the other camera needs to be simultaneously turned on. [0058]It should be noted that, in the foregoing description, the distance, between the mobile terminal and the user, measured by the distance measurement module may be an instantaneous value that is currently measured between the mobile terminal and the user, or may be an average value or a sample value of distances between the mobile terminal and the user within preset duration. Certainly, the foregoing description is merely an example, and is not limited herein. [0059]Step 103. If the distance is greater than or equal to a preset numeric value, turn on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turn on a rear-facing camera of the mobile terminal. [0060]After determining the distance between the mobile terminal and the user, the mobile terminal determines whether the distance is greater than or less than the preset numeric value. If the distance is greater than or equal to the preset numeric value, the front-facing camera is turned on; or the distance is less than the preset numeric value, the rear-facing camera is turned on. In the foregoing first case, after receiving the photographing request initiated by the user, the mobile terminal may directly select, according to the distance, to turn on a corresponding camera; or the mobile terminal may first turn on a default camera, and if a camera corresponding to the distance is different from the default camera, switch from the default camera to the camera corresponding to the distance, or additionally turn on the camera corresponding to the distance, that is, simultaneously turn on the front-facing camera and the rear-facing camera. [0061]In the foregoing second case, if the camera corresponding to the distance is different from a currently used camera, the mobile terminal switches from the currently used camera to the camera corresponding to the distance, or the mobile terminal additionally turns on the camera corresponding to the distance, that is, simultaneously turns on the front-facing camera and the rear-facing camera. [0062]In this embodiment, it is determined whether a distance between a mobile terminal and a user is greater than a preset numeric value, so as to automatically determine whether to turn on a front-facing camera of the mobile terminal or turn on a rear-facing camera of the mobile terminal, thereby implementing automatic selection between the front-facing camera and the rear-facing camera of the mobile terminal, avoiding a case in which the user needs to perform manual selection, and improving user experience for the mobile terminal. [0063]In the foregoing embodiment, a distance between a mobile terminal and a user is determined, so as to determine whether to turn on a front-facing camera or a rear-facing camera. In an actual application, the distance may be a distance between the mobile terminal and a face of the user, and the following describes a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure. Referring to FIG. 2, another embodiment of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure includes the following steps. [0064]Step 201. A mobile terminal receives a photographing request initiated by a user. [0065]The mobile terminal may be a mobile phone, a tablet computer, or another mobile terminal having a camera, where a front-facing camera and a rear-facing camera are disposed on the mobile terminal, the front-facing camera refers to a camera that is located at a same side as a display screen of the mobile terminal, and the rear-facing camera refers to a camera that is located at the other side of the mobile terminal opposite to the display screen of the mobile terminal. When a user needs to take a picture, the user may trigger a photographing function of the mobile terminal. The mobile terminal receives a photographing request initiated by the user, and prepares to turn on a camera to enter a photographing state. [0066]Step 202. The mobile terminal determines a distance between the mobile terminal and a face of the user. [0067]When the distance measurement module in the mobile terminal measures the distance between the mobile terminal and the user, the distance measurement module may measure the distance between the mobile terminal and the face of the user. During measurement of the distance, the distance may be a distance between the mobile terminal and a specific preset position on the face of the user, for example, the distance is a distance between the mobile terminal and a central point between the two eyes of the user, or a distance between the mobile terminal and the nose of the user; or the distance may be an overall distance between the mobile terminal and at least two preset positions on the face of the user, for example, the distance is equal to an average value of distances between the mobile terminal and the two eyes of the user, or an average value of distances between the mobile terminal and the five sense organs of the user. Certainly, the foregoing description is merely an example, and is not limited herein. [0068]Certainly, in an actual application, the mobile terminal may not determine the distance between the mobile terminal and the face of the user, but determine a distance between the mobile terminal and another portion of the user, which is not limited herein. Preferably, the mobile terminal may receive a setting by the user for a specific definition of the distance. [0069]In an actual application, the determining a distance between the mobile terminal and a face of the user may be determining a distance between a camera of the mobile terminal and the face of the user, or determining a distance between another position on the mobile terminal and the face of the user, or determining an overall distance between at least two positions on the mobile terminal and the face of the user, which is not limited herein. [0070]Step 203. If the distance is greater than or equal to a preset numeric value, turn on a front-facing camera of the mobile terminal; or if the distance is less than the preset numeric value, turn on a rear-facing camera of the mobile terminal. [0071]After determining the distance between the mobile terminal and the user, the mobile terminal determines whether the distance is greater than or less than the preset numeric value. If the distance is greater than or equal to the preset numeric value, the front-facing camera is turned on; or the distance is less than the preset numeric value, the rear-facing camera is turned on. In the foregoing first case, after receiving the photographing request initiated by the user, the mobile terminal may directly select, according to the distance, to turn on a corresponding camera; or the mobile terminal may first turn on a default camera, and if a camera corresponding to the distance is different from the default camera, switch from the default camera to the camera corresponding to the distance, or additionally turn on the camera corresponding to the distance, that is, simultaneously turn on the front-facing camera and the rear-facing camera. [0072]In the foregoing second case, if the camera corresponding to the distance is different from a currently used camera, the mobile terminal switches from the currently used camera to the camera corresponding to the distance, or the mobile terminal additionally turns on the camera corresponding to the distance, that is, simultaneously turns on the front-facing camera and the rear-facing camera. [0073]In this embodiment, the determining of the distance between the mobile terminal and the face of the user conforms better to a self-photographing behavior often performed by the user using the mobile terminal in an actual application, so that the mobile terminal more accurately determines, according to the distance, whether to turn on the front-facing camera or the rear-facing camera, so as to better meet an actual requirement of the user. [0074]In the foregoing embodiment, if the determined distance is greater than or equal to the preset numeric value, the front-facing camera is turned on; otherwise, the rear-facing camera is turned on. In an actual application, the preset numeric value may be set by the mobile terminal by default, and the following describes a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure. Referring to FIG. 3, another embodiment of a method for selection between a front-facing camera and a rear-facing camera of a mobile terminal according to an embodiment of the present disclosure includes the following steps. [0075]Step 301. A mobile terminal receives a photographing request initiated by a user. [0076]The mobile terminal may be a mobile phone, a tablet computer, or another mobile terminal having a camera, where a front-facing camera and a rear-facing camera are disposed on the mobile terminal, the front-facing camera refers to a camera that is located at a same side as a display screen of the mobile terminal, and the rear-facing camera refers to a camera that is located at the other side of the mobile terminal opposite to the display screen of the mobile terminal. When a user needs to take a picture, the user may trigger a photographing function of the mobile terminal. The mobile terminal receives a photographing request initiated by the user, and pre(String), 相关申请的交叉引用 [0001] 本申请是2014年6月30日提交的国际申请PCT/CN2014/081100的继续申请,该申请要求2014年1月29日提交的中国专利申请201410043609.7的优先权,在此将其并入 全文参考。 技术领域 [0002] 本发明涉及移动通信领域,尤其涉及一种移动终端前置摄像头和后置摄像头的选择方法及移动终端。 背景 [0003] 前置和后置摄像头一般配置在现有的移动终端(尤其是手机)上,后置摄像头功能很多,主要用于拍摄风景和其他人,而前置摄像头通常用于 仅用于自拍和视频通话。 [0004] 当用户开启摄像头时,现有终端一般默认开启后置摄像头。 当用户需要切换前置摄像头时,用户通常通过点击屏幕上的独立按钮来实现前置摄像头和后置摄像头的切换。 [0005] 但是这种方式需要用户手动切换,比较复杂。 概括 [0006] 本发明实施例提供一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,能够实现移动终端前置摄像头和后置摄像头的自动选择。 移动终端。 [0007] 本发明实施例的第一方面提供了一种移动终端前置摄像头和后置摄像头的选择方法,包括:移动终端接收用户发起的拍照请求; 移动终端确定移动终端与用户的距离; 若距离大于或等于预设数值,则开启移动终端的前置摄像头。 或者如果距离小于预设数值,则开启移动终端的后置摄像头。 [0008] 结合本发明实施例第一方面,在本发明实施例第一方面的第一种实施方式中,所述移动终端确定所述移动终端与所述用户的距离包括: ,通过移动终端,移动终端与用户的面部之间的距离。 [0009] 结合本发明实施例第一方面的第一种实施方式,在本发明实施例第一方面的第二种实施方式中,所述移动终端确定所述移动终端之间的距离 所述用户面部包括:所述移动终端确定所述移动终端与所述用户面部预设位置的距离; 或者,移动终端确定移动终端与用户面部的至少两个预设位置的总距离。 [0010] 结合本发明实施例的第一方面,或第一方面的第一实施方式,或第一方面的第二实施方式,在本发明实施例第一方面的第三实施方式中 ,预设数值由移动端默认设置。 [0011] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第四种实施方式中,所述拍照请求至少包括第一应用请求和第二应用 要求; 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值。 第一预设数值与第二预设数值不同。 [0012]结合本发明实施例第一方面的第四种实施方式,在本发明实施例第一方面的第五种实施方式中,所述方法还包括获取第一概率和第二概率,其中 第一概率为在第一应用状态下使用前置摄像头的概率,第二概率为在第二应用状态下使用前置摄像头的概率。 根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。 [0013] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第六种实施方式中,所述方法还包括:所述移动终端获取所述移动终端的信息。 用户对前置摄像头和后置摄像头的使用情况,并根据使用信息调整预设数值。 [0014] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第七种实施方式中,所述方法还包括:所述移动终端获取用户的个人信息。 用户,并根据个人信息调整预设数值。 [0015] 结合本发明实施例第一方面的第三种实施方式,在本发明实施例第一方面的第八种实施方式中,所述方法还包括:所述移动终端获取因子: 用户当前所处环境,根据用户当前所处环境因素调整预设数值。 [0016] 结合本发明实施例的第一方面,或第一方面的第一实施方式,或第一方面的第二实施方式,在本发明实施例第一方面的第九种实施方式中 ,该方法还包括获取用户输入的预设数值。 [0017] 结合本发明实施例的第一方面,或者第一方面的第一实施方式,或者第一方面的第二实施方式,在本发明实施例第一方面的第十实施方式中 ,在开启移动终端前置摄像头之前或开启移动终端后置摄像头之前,该方法还包括向用户发送查询请求,该查询请求用于向用户询问 用户是否同意开启摄像头; 获取用户的回复; 当回复为同意开启摄像头或在预设时间内未收到回复时,触发开启移动终端前置摄像头或移动终端后置摄像头。 或者当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0018] 本发明实施例的第二方面提供了一种移动终端,包括前置摄像头和后置摄像头。 接收模块,用于接收用户发起的拍摄请求; 确定模块,用于确定移动终端与用户之间的距离; 控制模块,用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0019]结合本发明实施例的第二方面,在本发明实施例的第二方面的第一种实施方式中,所述确定模块,用于确定所述移动终端与所述用户的面部的距离。 . [0020] 结合本发明实施例第二方面的第一种实施方式,在本发明实施例第二方面的第二种实施方式中,所述确定模块,用于确定所述移动终端与所述移动终端之间的距离。 用户脸上的预设位置; 或者,所述确定模块,用于确定所述移动终端与所述用户面部的至少两个预设位置之间的总距离。 [0021] 结合第二方面,或第二方面的第一种实施方式,或第二方面的第二种实施方式,在本发明实施例的第二方面的第三种实施方式中,设置预设数值 手机端默认。 [0022] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第四种实施方式中,所述拍照请求至少包括第一应用请求和第二应用 要求; 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值。 第一预设数值与第二预设数值不同。 [0023] 结合本发明实施例第二方面的第四种实施方式,在本发明实施例第二方面的第五种实施方式中,所述移动终端还包括第一获取模块,用于获取第一 概率和第二概率,其中第一概率是用户在第一应用状态下使用前置摄像头的概率,第二概率是用户在第二应用状态下使用前置摄像头的概率 状态; 第一调整模块,用于根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应于第一预设数值,第二概率对应于第二 预设数值。 [0024] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第六种实施方式中,所述移动终端还包括第二获取模块,用于获取有关信息。 用户对前置摄像头和后置摄像头的使用情况; 第二调整模块,用于根据使用信息调整预设数值。 [0025] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第七种实施方式中,所述移动终端还包括第三获取模块,用于获取个人信息 用户,并根据个人信息调整预设数值; 第三调整模块,用于根据个人信息调整预设数值。 [0026] 结合本发明实施例第二方面的第三种实施方式,在本发明实施例第二方面的第八种实施方式中,所述移动终端还包括第四获取模块,用于获取因子 用户当前所处的环境; 第四调整模块,用于根据用户当前所处环境的因素调整预设数值。 [0027]结合本发明实施例的第二方面,或第二方面的第一种实施方式,或第二方面的第二种实施方式,在本发明实施例第二方面的第九种实施方式中 进一步地,所述移动终端还包括第五获取模块,用于获取用户输入的预设数值。 [0028] 结合本发明实施例的第二方面,或第二方面的第一种实施方式,或第二方面的第二实施方式,在本发明实施例第二方面的第十种实施方式中 进一步地,所述移动终端还包括询问模块,用于向所述用户发送询问请求,所述询问请求用于询问所述用户是否同意开启摄像头。 第六获取模块,用于获取用户的回复; 第一触发单元,用于当回复为同意开启摄像头时,触发控制模块开启移动终端前置摄像头或开启移动终端后置摄像头; 第二触发单元,用于当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0029] 从上述技术方案可以看出,本发明实施例具有以下优点。 [0030] 本发明实施例通过判断移动终端与用户的距离是否大于预设数值,从而自动判断是否开启移动终端前置摄像头或开启 移动终端的后置摄像头,从而实现了移动终端前置摄像头和后置摄像头之间的自动选择,避免了用户需要手动选择的情况,提高了用户的使用体验。 移动终端。 附图说明 [0031] 图1为本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0032] 图2是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0033] 图3是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0034] 图4是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0035] 图5是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0036] 图6是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0037] 图7是根据本发明另一实施例的移动终端前置摄像头和后置摄像头选择方法的流程图。 [0038] 图8为本发明实施例提供的移动终端示意图; [0039] 图9为本发明另一实施例的移动终端的示意图; [0040] 图10是根据本发明另一实施例的移动终端的示意图; [0041] 图11是根据本发明另一实施例的移动终端的示意图; [0042] 图12为本发明另一实施例的移动终端的示意图; [0043] 图13是根据本发明另一实施例的移动终端的示意图; [0044]图14是根据本发明另一实施例的移动终端的示意图; [0045] 图15为本发明实施例提供的手机示意图; 和 [0046] 图16为本发明实施例提供的手机内部结构示意图。 具体实施方式 [0047] 本发明实施例提供一种移动终端前置摄像头和后置摄像头的选择方法及移动终端,用于实现前置摄像头和后置摄像头的自动选择。 的移动终端。 [0048] 为使本领域技术人员更好地理解本发明的技术方案,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 以上所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 在本公开的说明书、权利要求书和附图中,术语“第一”、“第二”、“第三”、“第四”等(如果存在)旨在区分相似的对象,但不一定 表示特定的顺序或顺序。 应当理解,以这种方式命名的数据在适当的情况下是可以互换的,使得在此描述的本公开的实施例可以以除了在此图示或描述的顺序之外的其他顺序来实施。 此外,术语“包括”、“包含”和任何其他变体意味着涵盖非排他性包含,例如,包括步骤或单元列表的过程、方法、系统、产品或设备不一定受到限制 这些单元,但可能包括未明确列出的其他单元或此类过程、方法、系统、产品或设备所固有的单元。 [0050] 参见图1,根据本发明实施例的移动终端前置摄像头和后置摄像头的选择方法实施例包括以下步骤。 [0051] 步 101 . 移动终端接收用户发起的拍照请求。 [0052] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 [0053] 步 102 . 移动终端确定移动终端与用户之间的距离。 [0054] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0055]需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0056] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0057] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离; 移动终端根据其测距模块确定当前距离,并根据距离确定是从当前使用的摄像头切换到其他摄像头还是需要同时开启其他摄像头。 [0058] 需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0059] 步 103 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0060] 在确定移动终端与用户之间的距离后,移动终端判断该距离是否大于或小于预设数值。 如果距离大于等于预设数值,则开启前置摄像头; 或距离小于预设数值,开启后置摄像头。 在上述第一种情况下,移动终端在接收到用户发起的拍照请求后,可以直接根据距离选择开启对应的摄像头。 或者,移动终端可以先开启默认摄像头,如果距离对应的摄像头与默认摄像头不同,则从默认摄像头切换到距离对应的摄像头,或者额外开启距离对应的摄像头 ,即同时开启前置摄像头和后置摄像头。 [0061]上述第二种情况,如果距离对应的摄像头与当前使用的摄像头不同,则移动终端从当前使用的摄像头切换到距离对应的摄像头,或者移动终端额外开启距离对应的摄像头。 距离,即同时开启前置摄像头和后置摄像头。 [0062] 本实施例通过判断移动终端与用户的距离是否大于预设数值,从而自动判断是开启移动终端前置摄像头还是开启后置摄像头 移动终端的摄像头,从而实现了移动终端前置摄像头和后置摄像头的自动选择,避免了用户需要手动选择的情况,提高了移动终端的用户体验。 [0063] 在上述实施例中,通过确定移动终端与用户之间的距离,来确定是开启前置摄像头还是开启后置摄像头。 在实际应用中,该距离可以是移动终端与用户面部之间的距离,下面描述根据实施例的移动终端前置摄像头和后置摄像头的选择方法 本公开的内容。 参见图2,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0064] 步 201 . 移动终端接收用户发起的拍照请求。 [0065] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 [0066] 步 202 . 移动终端确定移动终端与用户面部之间的距离。 [0067] 当移动终端中的距离测量模块测量移动终端与用户之间的距离时,距离测量模块可以测量移动终端与用户面部之间的距离。 在测量距离时,该距离可以是移动终端到用户面部特定预设位置的距离,例如,距离是移动终端到用户两只眼睛中心点的距离。 用户,或者移动终端到用户鼻子的距离; 或者,该距离可以是移动终端到用户面部至少两个预设位置的总距离,例如,该距离等于移动终端到用户两只眼睛的距离的平均值, 或者移动终端与用户五种感觉器官的距离平均值。 当然,以上所述仅为举例,在此不做限定。 [0068] 当然,在实际应用中,移动终端可以不确定移动终端与用户面部的距离,而是确定移动终端与用户其他部分的距离,此处不做限定。 优选地,移动终端可以接收用户对距离的特定定义的设置。 [0069]在实际应用中,确定移动终端与用户面部的距离可以是确定移动终端的摄像头与用户面部的距离,也可以是确定移动终端上其他位置与用户面部的距离。 用户的面部,或者确定移动终端上至少两个位置与用户面部的总距离,在此不做限定。 [0070] 步 203 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0071] 在确定移动终端与用户之间的距离后,移动终端判断该距离是否大于或小于预设数值。 如果距离大于等于预设数值,则开启前置摄像头; 或距离小于预设数值,开启后置摄像头。 在上述第一种情况下,移动终端在接收到用户发起的拍照请求后,可以直接根据距离选择开启对应的摄像头。 或者,移动终端可以先开启默认摄像头,如果距离对应的摄像头与默认摄像头不同,则从默认摄像头切换到距离对应的摄像头,或者额外开启距离对应的摄像头 ,即同时开启前置摄像头和后置摄像头。 [0072] 上述第二种情况,如果距离对应的摄像头与当前使用的摄像头不同,则移动终端从当前使用的摄像头切换到距离对应的摄像头,或者移动终端额外开启距离对应的摄像头。 距离,即同时开启前置摄像头和后置摄像头。 [0073] 在本实施例中,移动终端与用户面部距离的确定更符合用户在实际应用中使用移动终端经常进行的自拍行为,从而使移动终端更准确地确定, 根据距离,开启前置摄像头或后置摄像头,以更好地满足用户的实际需求。 [0074] 在上述实施例中,如果确定的距离大于或等于预设数值,则开启前置摄像头; 否则,后置摄像头已打开。 在实际应用中,该预设数值可以由移动终端默认设置,下面对根据本发明实施例的移动终端前置摄像头和后置摄像头的选择方法进行说明 披露。 参见图3,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0075] 步 301 . 移动终端接收用户发起的拍照请求。 [0076]所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0077] 步 302 . 移动终端确定移动终端与用户之间的距离。 [0078] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0079] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0080] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0081] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0082]需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0083] 步 303 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0084] 本实施例中,预设数值由移动终端默认设置。 具体举例来说,移动终端可以默认设置该预设数值为移动终端销售区域内成年人平均臂长的0.7倍至1倍。 [0085] 当用户发起不同的拍照请求时,用户分别使用前置摄像头和后置摄像头的情况可能会有所不同。 因此,优选地,在本实施例中,在根据距离是否小于预设数值来判断是开启前置摄像头还是开启后置摄像头时,针对不同的拍摄请求,预设数值 移动端默认设置不同。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0086] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0087] 当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0088] 在本实施例中,移动终端针对不同的拍照请求默认设置不同的预设数值,使得移动终端可以根据实际情况更灵活地自动开启前置摄像头或后置摄像头,提高用户使用体验。 经验。 [0089] 在上述实施例中,针对不同的拍摄请求,移动终端默认设置的预设数值是不同的。 在实际应用中,对于不同的拍照请求,移动终端还可以根据其他方法调整不同拍照请求对应的预设数值。 下面对根据本发明实施例的移动终端前置摄像头和后置摄像头的选择方法进行说明。 参见图4,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0090] 步 401 . 移动终端接收用户发起的拍照请求。 [0091] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0092] 步 402 . 移动终端确定移动终端与用户之间的距离。 [0093] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0094] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0095] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者测距模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍照请求时,根据自身测距模块或距离确定当前距离 只有当移动终端接收到用户发起的拍照请求时,测量模块才可以检测到移动终端与用户之间的当前距离,移动终端根据其测距模块确定测距模块测得的距离 . [0096] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0097]需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0098] 步 403 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0099] 本实施例中,预设数值由移动终端默认设置。 不同的拍摄请求对应不同的预设数值。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0100] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0101] 步 404 . 获取第一概率和第二概率,第一概率为在第一应用状态下使用前置摄像头的概率,第二概率为在第二应用状态下使用前置摄像头的概率。 [0102] 移动终端统计摄像头分别应用于第一应用和第二应用的次数以及前置摄像头和后置摄像头分别在两个不同应用中的使用次数,然后计算出a 在移动终端的摄像头的第一应用状态和第二应用状态下分别使用前置摄像头的第一概率和第二概率。 举一个具体的例子,移动终端统计摄像头的应用次数,得到摄像头应用到第一应用的次数为589次,摄像头应用到第二个应用的次数为589次。 应用为628,其中摄像头处于第一应用状态时使用前置摄像头的次数为342,摄像头处于第二应用状态时使用前置摄像头的次数为 381. 因此,通过计算可以得到在第一个应用状态下使用前置摄像头的第一概率为342/589,第二个应用状态下使用前置摄像头的第二个概率为381/628 . [0103] 当然,在实际应用中,也可以获取前置摄像头在其他应用状态下的使用概率,或者只获取前置摄像头在最常用的两种应用状态下的使用概率,或者只获取前置摄像头在其他应用状态下的使用概率。 统计用户选择的两种应用状态的前置摄像头,此处不做限定。 [0104]在计算出第一概率和第二概率后,移动终端可以按照预设的时间间隔更新这两个概率,也可以在每次使用相机后更新数据,在此不做限定。 [0105] 步 405 . 根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。 [0106] 获取第一概率和第二概率后,若第一概率大于第二概率,则调整第一预设数值和/或第二预设数值,使得第一预设数值小于第二 预设数值。 举个具体的例子,第一个概率是摄像头在视频通话状态时使用前置摄像头的概率,第二个概率是摄像头处于拍照状态时使用前置摄像头的概率, 并且第一个概率大于第二个概率。 因此,移动终端根据第一概率大于第二概率调整第一预设数值和/或第二预设数值,使得第一预设数值小于第二预设数值。 [0107] 当调整第一预设数值和/或第二预设数值使得第一预设数值小于第二预设数值时,可以使第一预设数值与第二预设数值的比例成比例 第二概率与第一概率的比值; 或者,可以使第一预设数值与第二预设数值的差与第二概率与第一概率的差成正比。 当然,在实际应用中,还可以采用其他方式,使得第一概率对应于第一预设数值,第二概率对应于第二预设数值,在此不做限定。 [0108] 在实际应用中,移动终端可以以预设的时间间隔调整第一预设数值和第二预设数值,例如,移动终端在第一概率和第二概率之后调整第一预设数值和第二预设数值。 概率更新,或者可以在每次使用相机后调整第一预设数值和第二预设数值。 [0109] 本实施例中,移动终端根据摄像头在不同应用状态下使用前置摄像头的概率不同,设置不同应用状态对应的预设数值,以实现移动终端自动开启前置摄像头。 根据实际情况更灵活地选择前置摄像头或后置摄像头,提高用户体验。 [0110] 在上述实施例中,移动终端默认设置的预设数值分别根据第一概率和第二概率进行调整。 在实际应用中,移动终端还可以通过其他方法调整预设数值,下面对本发明实施例提供的移动终端前置摄像头和后置摄像头的选择方法进行说明。 . 参见图5,根据本发明实施例的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0111] 步 501 . 移动终端接收用户发起的拍照请求。 [0112]所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0113] 步 502 . 移动终端确定移动终端与用户之间的距离。 [0114] 移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0115] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0116] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,移动终端根据其测距模块确定当前距离或 测距模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍照请求时,根据其测距模块或测距确定当前距离 只有当移动终端接收到用户发起的拍照请求时,模块才可以检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定测距模块测得的距离。 [0117] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0118]需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0119] 步 503 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0120] 本实施例中,预设数值由移动终端默认设置。 不同的拍摄请求对应不同的预设数值。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0121] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0122] 步 504 . 移动终端获取用户对前置摄像头和后置摄像头的使用信息,并根据使用信息调整预设数值。 [0123] 移动终端获取用户使用前置摄像头和后置摄像头的信息,该使用信息包括用户使用前置摄像头和后置摄像头的所有记录,例如频率 前置摄像头和后置摄像头分开使用的频率,用户从一个摄像头切换到另一个摄像头的频率,以及用户使用前置摄像头和后置摄像头时移动终端与用户之间的距离 - 单独面对相机。 移动终端在获取到用户对前置摄像头和后置摄像头的使用信息后,根据使用信息进行计算分析,并根据分析结果调整预设数值。 [0124]例如,移动终端确定使用记录中移动终端与用户之间的所有距离的值或确定一些样本值,并计算用户使用前置摄像头的概率和使用后置摄像头的概率。 每个确定的距离值对应的面向相机,然后找出与使用前置相机的概率与使用后置相机的概率之差小于或等于的情况对应的所有目标距离 等于0,并将预设数值调整为所有目标距离之一。 举一个具体的例子,移动终端确定该使用记录中移动终端与用户之间的所有距离的取值范围为0厘米(cm)至60厘米。 当距离值为30cm时,使用后置摄像头的概率为95%,使用前置摄像头的概率为5%; 当距离为40cm时,使用后置摄像头的概率为40%,使用前置摄像头的概率为60%; 距离为50cm时,使用后置摄像头的概率为30%,使用前置摄像头的概率为70%。 因此,可以将预设数值调整为40厘米。 或者,在所有距离值中,使用前置摄像头的概率均低于5%,说明用户很少使用前置摄像头,因此可以将预设数值设置为较大的值, 例如,可能等于手臂长度的 0.95 倍。 [0125] 又如,移动终端在确定开启前置摄像头后,根据移动终端与用户的距离,确定开启前置摄像头还是后置摄像头时 或者后置摄像头,在打开前置摄像头或者后置摄像头之前,移动终端还向用户发送询问请求,询问请求用于询问用户是否同意开启 在相机上; 若用户同意开启摄像头或在预设时间内未收到回复,则移动终端继续开启摄像头; 或者如果用户拒绝开启摄像头,则在第一种情况下,移动终端继续开启默认摄像头,在第二种情况下,移动终端继续使用原有摄像头。 此外,移动终端对用户的反馈进行统计分析。 如果移动终端询问用户是否开启前置摄像头时一致概率超过50%,而移动终端询问用户是否开启后置摄像头时一致概率低于50%,则 移动终端将预设数值增加预定值。 [0126] 需要说明的是,以上描述仅为举例,在此不做限定。 [0127] 当然,在实际应用中,移动终端在对前置摄像头和后置摄像头的使用信息进行分析计算之前,还可以进一步对两个摄像头的使用信息进行分类,其中使用信息, 将前置摄像头和后置摄像头对应的每种拍照请求分类为同一类型,然后对每种使用信息进行分析计算,分别调整对应的预设数值 不同的拍摄要求。 [0128] 移动终端可以按照预设的时间间隔更新前置摄像头和后置摄像头的使用信息,也可以在每次使用摄像头后更新使用信息,在此不做限定。 同理,移动终端可以按照预设的时间间隔调整预设数值,也可以在每次使用相机后调整预设数值,在此不做限定。 [0129]在本实施例中,移动终端获取用户对前置摄像头和后置摄像头的使用信息,并根据使用信息调整预设数值,使移动终端能够自动开启前置摄像头和后置摄像头。 根据实际情况更准确地选择前置摄像头或后置摄像头,从而提高用户体验。 [0130] 在上述实施例中,移动终端默认设置的预设数值是根据用户对前置摄像头和后置摄像头的使用信息进行调整的。 在实际应用中,移动终端可以根据用户的个人信息调整预设的数值,下面对本实施例提供的移动终端前置摄像头和后置摄像头的选择方法进行说明。 本公开的内容。 参见图6,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0131] 步 601 . 移动终端接收用户发起的拍照请求。 [0132] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0133] 步 602 . 移动终端确定移动终端与用户之间的距离。 [0134] 移动终端中设置有可以测量移动终端与用户之间距离的测距模块,测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0135] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0136]在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0137] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0138] 需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0139] 步 603 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0140] 本实施例中,预设数值由移动终端默认设置。 具体举例来说,移动终端可以将预设数值默认设置为移动终端销售区域内成年人平均臂长的0.7倍至1倍。 [0141] 当用户发起不同的拍照请求时,用户分别使用前置摄像头和后置摄像头的情况可能会有所不同。 因此,优选地,在本实施例中,在根据距离是否小于预设数值来判断是开启前置摄像头还是开启后置摄像头时,针对不同的拍摄请求,预设数值 移动端默认设置不同。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0142] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0143]当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0144] 步 604 . 移动终端获取用户的个人信息,并根据个人信息调整预设数值。 [0145] 移动终端可以从移动终端内部存储的应用程序中获取用户的个人信息,也可以从运营商处获取用户的个人信息,也可以由用户输入个人信息。 当然,在实际应用中,移动终端可以从其他来源获取用户的个人信息。 示例仅在本文中描述,并且不受限制。 移动终端获取的用户个人信息可以包括用户的年龄、身高、臂长、性别等信息。 移动终端获取到用户的个人信息后,根据个人信息调整预设数值。 例如,如果用户是女性,由于女性自拍的概率较高,移动终端可以将预设数值减少预定值; 或者如果用户年龄在50岁以上,则用户自拍的概率较低,因此,移动终端可以将预设数值增加预定值。 或者,如果用户的臂长为56cm,则可以将用户臂长的倍数(例如0.7倍)作为预设数值。 当然,以上所述仅为举例,在此不做限定。 [0146] 在本实施例中,移动终端获取用户的个人信息,并根据个人信息调整预设数值,以使移动终端能够更准确地自动开启前置摄像头或后置摄像头。 用户的个人实际情况,从而提高用户体验。 [0147] 在上述实施例中,移动终端默认设置的预设数值是根据用户的个人信息进行调整的。 在实际应用中,移动终端可以根据用户当前所处的环境因素来调整预设数值,下面介绍前置摄像头和后置摄像头的选择方法。 根据本发明实施例的移动终端。 参见图7,本发明实施例提供的移动终端前置摄像头和后置摄像头选择方法的另一实施例包括以下步骤。 [0148] 步 701 . 移动终端接收用户发起的拍照请求。 [0149] 所述移动终端可以是手机、平板电脑或其他具有摄像头的移动终端,所述移动终端上设置有前置摄像头和后置摄像头,所述前置摄像头是指具有摄像头的摄像头。 后置摄像头与移动终端的显示屏位于同一侧,后置摄像头是指位于移动终端与移动终端显示屏相对的另一侧的摄像头。 当用户需要拍照时,用户可以触发移动终端的拍照功能。 移动终端接收到用户发起的拍照请求,准备开启摄像头进入拍照状态。 拍摄请求至少包括第一应用请求和第二应用请求。 具体的,所述拍照请求包括视频拍摄请求和拍照请求,或者还包括视频通话请求。 当然,以上所述仅为举例,在此不做限定。 [0150] 步 702 . 移动终端确定移动终端与用户之间的距离。 [0151]移动终端中设置有能够测量移动终端与用户之间距离的测距模块,该测距模块可以是独立设置的距离传感器或接近传感器,也可以是配置在移动终端中的距离传感器。 移动端的摄像头实现自动对焦功能。 当然,在实际应用中,测距模块可以是其他可以实现相同功能的传感器或模块。 [0152] 需要说明的是,这里有两种情况。 第一种情况,当用户向移动终端发起拍照请求时,移动终端的摄像头是关闭的。 移动终端在用户向移动终端发起拍照请求时,确定移动终端与用户之间的距离,从而根据距离确定是开启前置摄像头还是开启后置摄像头。 面对相机。 移动终端在接收到用户发起的拍照请求后,可以先开启默认摄像头,然后根据距离确定是否切换或追加开启前置摄像头或后置摄像头,或者 直接根据距离决定开启前置摄像头还是后置摄像头,在此不做限定。 [0153] 在第一种情况下,测距模块可以一直检测移动终端与用户之间的距离,当移动终端接收到用户发起的拍照请求时,根据其测距模块确定当前距离。 或者,距离测量模块仅在屏幕开启时检测移动终端与用户之间的距离,移动终端在接收到用户发起的拍摄请求时,根据其距离测量模块确定当前距离。 或者,距离测量模块可以仅在移动终端接收到用户发起的拍照请求时,检测移动终端与用户之间的当前距离,移动终端根据其测距模块确定由移动终端测量的距离。 距离测量模块。 [0154] 第二种情况,移动终端在接收到用户发起的拍照请求时,当前处于拍照状态。 在移动终端的整个拍照过程中,测距模块实时检测移动终端与用户之间的距离,移动终端根据其测距模块确定当前距离。 [0155] 需要说明的是,在上述描述中,距离测量模块测量的移动终端与用户之间的距离可以是当前测量的移动终端与用户之间的瞬时值,也可以是平均值 预设时间内移动终端与用户的距离值或样本值。 当然,以上所述仅为举例,在此不做限定。 [0156] 步 703 . 若距离大于或等于预设数值,则开启移动终端前置摄像头; 或者如果距离小于预设数值,打开移动终端的后置摄像头。 [0157] 本实施例中,预设数值由移动终端默认设置。 具体举例来说,移动终端可以将预设数值默认设置为移动终端销售区域内成年人平均臂长的0.7倍至1倍。 [0158]当用户发起不同的拍照请求时,用户分别使用前置摄像头和后置摄像头的情况可能会有所不同。 因此,优选地,在本实施例中,在根据距离是否小于预设数值来判断是开启前置摄像头还是开启后置摄像头时,针对不同的拍摄请求,预设数值 移动端默认设置不同。 当移动终端接收到的用户发起的拍照请求为第一应用请求时,若距离大于或等于第一预设数值,则开启移动终端前置摄像头; 或者,如果距离小于第一预设数值,则开启移动终端的后置摄像头。 当移动终端接收到的用户发起的拍照请求为第二应用请求时,若距离大于或等于第二预设数值,则开启移动终端前置摄像头; 或者如果距离小于第二预设数值,则开启移动终端的后置摄像头。 第一预设数值与第二预设数值不同。 [0159] 当然,在实际应用中,用户发起的拍照请求不仅可以包括第一应用请求和第二应用请求,还可以包括第三应用请求、第四应用请求、第五应用请求等。 . 除第一应用请求和第二应用请求外,其他应用请求对应的预设数值可以全部或部分相同,也可以不同,此处不做限定。 [0160] 当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0161] 步 704 . 移动终端获取用户当前所处环境的因子,并根据用户当前所处的环境因子调整预设数值。 [0162] 移动终端可以通过设置在其中的检测器或者其他传感模块获取用户当前所处的环境因素,其中,用户当前所处的环境因素可以包括光线等环境因素。 用户当前所处环境的强度或温度,或用户是在房间内还是在房间外,或用户所处环境的运动状态,并根据 不同的环境因素。 举一个具体的例子,移动终端设置的预设数值的初始值对应于预设的光强参考值。 当移动终端接收到用户发起的拍照请求时,移动终端检测用户当前所处环境的光照强度,并根据预设表格将预设数值调整为预定值。 预设表中设置了不同光强与预设数值的不同具体数值一一对应,光强越小对应预设数值越小。 [0163] 在本实施例中,移动终端获取用户当前所处环境的因子,并根据用户当前所处的环境因子调整预设数值,使移动终端能够自动转向 更准确地根据用户的个人实际情况设置在前置摄像头或后置摄像头上,从而提高用户体验。 [0164]当然,在实际应用中,预设数值也可以不由移动终端默认设置,而可以由用户手动输入。 这样,用户可以根据自己的实际情况设置预设数值,从而使移动终端可以根据个人实际情况更准确地自动开启前置摄像头或后置摄像头。 用户,从而提升用户体验。 [0165] 在上述所有实施例中,当移动终端根据移动终端与用户的距离确定开启前置摄像头还是后置摄像头时,在确定开启前置摄像头后, 前置摄像头或后置摄像头在开启前置摄像头或后置摄像头之前,移动终端进一步向用户发送询问请求,询问请求用于询问用户是否同意 打开相机; 若用户同意开启摄像头或在预设时间内未收到回复,则移动终端触发摄像头开启; 或者如果用户拒绝开启摄像头,则移动终端触发移动终端的默认动作。 第一种情况,默认动作是继续开启移动终端的默认摄像头,第二种情况,默认动作是继续使用原有摄像头。 移动终端在向用户发送查询请求时,可以通过在屏幕上出现的弹窗显示文字来询问用户; 或者,移动终端可以通过语音询问用户是否同意开启摄像头。 用户可以通过点击移动终端屏幕上的预设区域,或者通过语音命令,或者通过摇动终端,或者通过按下移动终端上的物理按键或者虚拟按键来响应来自移动终端的询问。 . 当然,以上所述仅为举例,在此不做限定。 [0166] 或者,移动终端也可以不询问用户,而是直接通知用户前置摄像头或后置摄像头开启。 例如,移动终端可以通过在屏幕上显示文本或图像或其他标志来通知用户,或者通过发出声音或振动来通知用户。 当然,以上所述仅为举例,在此不做限定。 [0167] 为便于理解,下面结合实际应用场景对本实施例的移动终端前置摄像头和后置摄像头的选择方法进行说明。 [0168] 手机默认设置预设数值的初始值为35cm。 手机的摄像头目前处于关闭状态。 手机接收用户发起的拍照请求,手机中的测距模块检测当前手机摄像头与用户鼻子之间的距离。 手机根据测距模块确定测距模块检测到的距离为40cm。 [0169] 手机判断距离大于手机默认设置的预设数值,并通过语音询问用户是否同意开启手机前置摄像头。 手机获取用户的语音指令后,对语音指令进行分析,识别出用户同意开启前置摄像头,然后开启手机前置摄像头。 [0170]此外,手机还会更新手机中存储的用户使用前置摄像头和后置摄像头的信息,更新后的数据如下: 手机与用户鼻子35厘米,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%; 距离为40cm时,使用后置摄像头的概率为52%,使用前置摄像头的概率为48%; 当距离为45cm时,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%。 因此,手机将预设数值的具体数值调整为40厘米。 [0171] 以上对本发明实施例的移动终端前置摄像头和后置摄像头的选择方法进行了描述,下面对本发明实施例的移动终端进行说明。 参见图8,本发明实施例的移动终端实施例包括前置摄像头和后置摄像头。 接收模块 801 用于接收用户发起的拍照请求; 确定模块 802 用于确定移动终端与用户之间的距离; 和一个控制模块 803 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0172] 本实施例中,移动终端通过控制模块判断移动终端与用户的距离是否大于预设数值,从而自动判断是否开启移动终端的前置摄像头。 或者打开移动终端的后置摄像头,从而实现了移动终端前置摄像头和后置摄像头之间的自动选择,避免了用户需要手动选择的情况,提高了用户 移动端体验。 [0173] 在上述实施例中,移动终端与用户之间的距离可以是移动终端与用户面部之间的距离。 该距离可以是移动终端到用户面部特定预设位置的距离,例如,该距离是移动终端到用户两只眼睛的中心点的距离,或者是两眼之间的距离。 移动终端和用户的鼻子; 或者,该距离可以是移动终端到用户面部至少两个预设位置的总距离,例如,该距离等于移动终端到用户两只眼睛的距离的平均值, 或者移动终端与用户五种感觉器官的距离平均值。 当然,以上所述仅为举例,在此不做限定。 [0174] 当然,在实际应用中,该距离可以不是确定的移动终端与用户面部之间的距离,而可以是移动终端与用户其他部分的距离,在此不做限定。 优选地,移动终端可以接收用户对距离的特定定义的设置。 [0175] 在实际应用中,确定移动终端与用户面部的距离可以是确定移动终端的摄像头与用户面部的距离,也可以是确定移动终端上其他位置与用户面部的距离。 用户的面部,或者确定移动终端上至少两个位置与用户面部的总距离,在此不做限定。 [0176]上述实施例中,控制模块用于当确定的距离大于或等于预设数值时,开启前置摄像头; 或者当距离小于预设数值时,开启后置摄像头。 在实际应用中,预设数值可以由移动终端默认设置。 优选地,接收模块接收到的拍摄请求至少包括第一应用请求和第二应用请求。 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值,第一预设数值与第二预设数值不同。 这样,移动终端可以针对不同的拍照请求默认设置不同的预设数值,使得移动终端可以根据实际情况更灵活地自动开启前置摄像头或后置摄像头,从而提高 用户体验。 当然,在实际应用中,移动终端默认设置的对应于用户发起的不同拍摄请求的预设数值可以全部相同,在此不做限定。 [0177] 在实际应用中,当移动终端分别调整第一预设数值和第二预设数值,使得这两个预设数值不同时,可以根据分别使用前置摄像头的概率进行调整。 相机的第一应用状态和第二应用状态。 下面对本发明实施例的移动终端进行说明。 参见图9,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 901 用于接收用户发起的拍照请求; 确定模块 902 用于确定移动终端与用户之间的距离; 和一个控制模块 903 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0178] 在本实施例中,移动终端还包括第一获取模块 904 用于获取第一概率和第二概率,第一概率为用户在第一应用状态下使用前置摄像头的概率,第二概率为用户使用前置摄像头的概率。 处于第二应用状态的用户; 以及第一调整模块 905 用于根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应第一预设数值,第二概率对应第二预设数值。 [0179] 本实施例中,移动终端根据摄像头在不同应用状态下使用前置摄像头的概率不同,设置不同应用状态对应的预设数值,以实现移动终端自动开启前置摄像头。 根据实际情况更灵活地选择前置摄像头或后置摄像头,提高用户体验。 [0180] 在上述实施例中,移动终端默认设置的预设数值分别根据第一概率和第二概率进行调整。 在实际应用中,移动终端可以通过其他方法调整预设数值,下面对本发明实施例提供的移动终端进行说明。 参见图10,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1001 用于接收用户发起的拍照请求; 确定模块1002 用于确定移动终端与用户之间的距离; 和一个控制模块 1003 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0181] 在本实施例中,移动终端还包括第二获取模块 1004 用于获取用户使用前置摄像头和后置摄像头的信息; 第二调整模块 1005 用于根据使用信息调整预设数值。 [0182] 在本实施例中,移动终端获取用户对前置摄像头和后置摄像头的使用信息,并根据使用信息调整预设数值,使得移动终端可以自动开启前置摄像头和后置摄像头。 根据实际情况更准确地选择前置摄像头或后置摄像头,从而提高用户体验。 [0183] 上述实施例中,移动终端根据用户使用前置摄像头和后置摄像头的信息,调整移动终端默认设置的预设数值。 在实际应用中,移动终端还可以利用用户的个人信息对预设数值进行调整,下面对本发明实施例提供的移动终端进行说明。 参见图11,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1101 用于接收用户发起的拍照请求; 确定模块 1102 用于确定移动终端与用户之间的距离; 和一个控制模块 1103 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0184] 在本实施例中,移动终端还包括第三获取模块 1104 用于获取用户的个人信息,并根据个人信息调整预设数值; 第三调整模块 1105 用于根据个人信息调整预设数值。 [0185] 在本实施例中,移动终端获取用户的个人信息,并根据个人信息调整预设数值,使得移动终端能够更准确地根据个人信息自动开启前置摄像头或后置摄像头。 用户的个人实际情况,从而提高用户体验。 [0186] 上述实施例中,移动终端根据用户的个人信息,对移动终端默认设置的预设数值进行调整。 在实际应用中,移动终端还可以根据用户当前所处的环境对预设数值进行调整,下面对本发明实施例的移动终端进行说明。 参见图12,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1201 用于接收用户发起的拍照请求; 确定模块 1202 用于确定移动终端与用户之间的距离; 和一个控制模块 1203 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0187] 在本实施例中,移动终端还包括第四获取模块 1204 用于获取用户当前所处环境的因子; 第四调整模块 1205用于根据用户当前所处环境的因素调整预设数值。 [0188] 在本实施例中,移动终端获取用户当前所处环境的因子,并根据用户当前所处的环境因子调整预设数值,使移动终端能够自动转向 更准确地根据用户的个人实际情况设置在前置摄像头或后置摄像头上,从而提高用户体验。 [0189] 在上述实施例中,预设数值是由移动终端默认设置的。 在实际应用中,预设数值可以由用户手动输入,下面对本发明实施例提供的移动终端进行说明。 参见图13,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头。 接收模块 1301 用于接收用户发起的拍照请求; 确定模块 1302 用于确定移动终端与用户之间的距离; 和一个控制模块 1303 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0190] 在本实施例中,移动终端还包括第五获取模块 1304 用于获取用户输入的预设数值。 [0191] 在本实施例中,移动终端可以使用户根据用户的实际情况设置预设数值,从而使移动终端能够更准确地自动开启前置摄像头或后置摄像头。 用户的个人实际情况,从而提高用户体验。 [0192] 在上述实施例中,移动终端根据移动终端与用户的距离来确定开启前置摄像头还是后置摄像头。 在实际应用中,在开启前置摄像头或后置摄像头之前,还可以向用户发送查询请求,下面对本发明实施例的移动终端进行说明。 参见图14,本发明实施例提供的移动终端的另一实施例包括前置摄像头和后置摄像头; 接收模块 1401 用于接收用户发起的拍照请求; 确定模块 1402 用于确定移动终端与用户之间的距离; 和一个控制模块 1403 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,打开移动终端的后置摄像头。 [0193] 在本实施例中,移动终端还包括查询模块 1404 用于向用户发送查询请求,该查询请求用于询问用户是否同意开启摄像头; 第六获取模块 1405 配置为获取用户的回复; 第一触发单元 1406 用于当回复为同意开启摄像头或在预设时间内未收到回复时,触发开启移动终端前置摄像头或移动终端后置摄像头; 和第二个触发单元 1407 用于当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0194] 在本实施例中,移动终端可以通过询问用户来确定是自动开启前置摄像头还是后置摄像头,以便开启的摄像头更好地满足用户的需求,从而 改善用户体验。 [0195]为便于理解,下面以实际应用场景对本实施例的移动终端进行说明。 [0196] 手机默认设置预设数值的初始值为35cm。 手机的摄像头目前处于关闭状态。 手机的接收模块接收用户发起的拍照请求,手机中的测距模块检测当前手机摄像头与用户鼻子之间的距离。 手机的判断模块根据测距模块确定测距模块检测到的距离为40cm。 [0197] 手机判断距离大于手机默认设置的预设数值,通过查询模块向用户发出语音,询问用户是否同意开启手机前置摄像头。 手机。 第六获取模块获取用户的语音命令。 当第六获取模块通过分析语音指令识别出用户同意开启摄像头时,第一触发单元触发控制模块开启手机前置摄像头。 [0198] 此外,第二获取模块获取用户对前置摄像头和后置摄像头的使用信息,更新使用信息并存储更新后的使用信息,更新后的数据如下: 手机的摄像头与用户鼻子的距离为35厘米,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%; 距离为40cm时,使用后置摄像头的概率为52%,使用前置摄像头的概率为48%; 当距离为45cm时,使用后置摄像头的概率为60%,使用前置摄像头的概率为40%。 因此,手机的第二调整模块将预设数值的具体数值调整为40cm。 [0199] 参见图15,本实施例以手机为例对本发明进行说明。 [0200] 需要注意的是,手机 100 图中所示仅为移动终端的示例,手机 100 可以包括比图中所示的组件更多或更少的组件,或者可以组合两个或更多组件,或者可以使用不同的组件部署。 图中所示的组件可以以硬件、软件或包括一个或多个信号处理和/或专用集成电路的硬件和软件的组合来实现。 [0201] 这里以手机为例进行具体说明。 如图15所示,手机上设置有前置摄像头和后置摄像头,手机还包括内存 11 , 一个中央处理器 13 (CPU),外围接口 14 , 射频 (RF) 电路 15 , 音频电路 16 , 一个扬声器 17 ,电源管理集成芯片 18 , 输入/输出 (I/O) 子系统 19 , 另一个输入/控制设备 110 , 和一个外部端口 111 ,其中这些组件使用一条或多条通信总线或信号线相互通信 112 . [0202] 需要说明的是,本实施例提供的手机仅仅是移动终端的一个示例。 本发明实施例所涉及的服务器可以包括比图15所示的组件更多或更少的组件,或者可以组合两个或多个组件,或者可以使用不同的组件部署或设置。 并且这些组件可以以硬件、软件或包括一个或多个信号处理和/或专用集成电路的硬件和软件的组合来实现。 [0203] 下面对本发明实施例提供的信息推送手机进行详细说明。 [0204] 记忆 11 CPU可以访问 13 和外围接口 14, 记忆 11 存储器可以包括高速随机存取存储器,也可以包括非易失性存储器,例如,一个或多个磁存储设备、闪存或其他非易失性固态存储器。 [0205] 外围接口可以将设备的输入和输出外围设备连接到 CPU 13 和记忆 11 . [0206] I/O 子系统 19 可以连接设备上的输入和输出外围设备,例如触摸屏 113 (相当于前述实施例中的显示器)和另一个输入/控制设备 110 , 到外围接口 14 . I/O 子系统 19 可能包括显示控制器 191 和一个或多个输入控制器 192 用于控制另一个输入/控制设备 110 . 一个或多个输入控制器 192 从另一个输入/控制设备接收电信号 110 或将电信号发送到另一个输入/控制设备 110 ,其中另一个输入/控制设备 110 可以包括物理按钮(按下按钮、摇杆按钮等)、拨盘、滑动开关、操纵杆、点击滚轮。 需要注意的是,输入控制器 192 可与以下任一组件连接:键盘、红外端口、通用串行总线(USB)接口、鼠标等定点设备。 [0207] 触摸屏 113 作为移动终端与用户之间的输入接口和输出接口,向用户显示可视输出,可视输出可以包括图片、文字、图标、视频等。 [0208] 显示控制器 191 在 I/O 子系统中 19 从触摸屏接收电信号 113 或向触摸屏发送电信号 113 . 触摸屏 113 检测触摸屏上的触摸; 显示控制器 191 将检测到的触摸转换为与触摸屏上显示的用户界面对象的交互 113 ,即人机交互,其中用户界面对象显示在触摸屏上 113 可以是游戏运行图标、链接到相应网络的图标等。 需要说明的是,该装置还可以包括光学鼠标,该光学鼠标是不显示可见输出的触敏面,或者是由触摸屏形成的触敏面的延伸。 [0209] 射频电路 15 主要用于建立手机与无线网络(即网络侧)之间的通信,实现手机与无线网络之间的数据收发,如短信业务消息的收发 和电子邮件(E-mail)。 射频电路 15 接收和发送射频信号,该射频信号也称为电磁信号; 射频电路 15 将电信号转换为电磁信号或将电磁信号转换为电信号,并使用该电磁信号与通信网络和其他设备进行通信。 射频电路 15 可以包括用于执行这些功能的已知电路,包括但不限于天线系统、RF收发器、一个或多个放大器、调谐器、一个或多个振荡器、数字信号处理器、CODEC芯片组、用户 身份模块 (SIM) 等。 [0210] 音频电路 16 主要配置为从外设接口接收音频数据 14 ,将音频数据转换为电信号,并将电信号发送到扬声器 17 . [0211] 扬声器 17 用于通过射频电路恢复手机从无线网络接收到的语音信号 15 发声,并向用户播放声音。 [0212] 电源管理集成芯片 18 配置为为连接到 CPU 的硬件供电 13 、I/O 子系统和外围接口,并执行电源管理。 [0213]图16是手机内部结构图。 在本发明实施例中,软件部分存储在存储器中 11 可能包括操作系统 21 , 通信模块 22 , 触控/移动模块 23 , 一个图形模块 24 , 和一个功能模块 26 . [0214] 操作系统 21 (例如,Darwin、RTXC、LINUX、UNIX、OS X、WINDOWS 或 VxWorks® 等嵌入式操作系统)包括用于控制和管理常见系统任务(例如,内存管理、控制 通过存储设备、电源管理等),并促进硬件部分和软件部分之间的通信。 [0215] 通讯模块 22 配置为使用一个或多个外部端口与另一设备通信 111 ,并且还包括用于处理RF电路接收到的数据的各种软件部分 15 和/或外部端口 111 . [0216] 触控/移动模块 23 可能会检测到触摸屏上的触摸 113 (结合显示控制器 191 ) 和另一个触敏设备(例如,触摸板或物理点击滚轮)。 触控/移动模块 23 包括用于执行和检测各种与触摸相关的操作的各种软件部分,其中操作例如判断是否发生触摸、判断触摸是否移动以及在触摸屏上跟踪移动 113 ,并判断触摸是否已经中断(即触摸是否已经停止)。 确定触摸点的移动可以包括确定触摸的速率(幅度值)、速度(幅度值和方向)和/或加速度(幅度值和/或方向的变化) 观点。 这些操作可以应用于单个触摸(例如,用一根手指触摸)或应用于多个同时触摸(例如,“多点触摸”/用多个手指触摸)。 在一些实施例中,触摸/移动模块 23 和显示控制器 191 进一步检测触摸板上的触摸。 [0217] 图形模块 24 包括用于在触摸屏上显示图像的各种已知软件部件 113 ,包括用于改变显示图像亮度的部分,例如,用于接收来自中央处理器的指令的图形用户界面 13 并在触摸屏上显示各类软件 113 . [0218] 功能模块 26 可能包括以下模块一个接收模块 261 用于接收用户发起的拍照请求; 确定模块 262 用于确定移动终端与用户之间的距离; 和一个控制模块 263 用于当距离大于或等于预设数值时,开启移动终端的前置摄像头; 或者当距离小于预设数值时,开启移动终端的后置摄像头。 [0219] 射频电路 15 接收网络侧或其他设备发送的信息,该消息可以是上述实施例中的第一用户的终端号码和推荐率计算参数。 可以理解的是,接收到的消息可以是其他类型的信息,本发明实施例对此不做限定。 本领域技术人员可以知道,接收到的信息可以携带多种数据类型的数据。 可能只有一种数据类型的数据,也可能有两种或多种数据类型的数据。 [0220] 中央处理器 13 识别射频电路接收到的信息中数据的数据类型 15 ; 根据对应关系列表将数据存储到与数据的数据类型对应的功能模块中,对应关系列表为数据类型与功能模块对应关系的列表,其中功能模块 26 可能是一个控制模块 263 和确定模块 262. 可以理解的是,在本发明实施例中,中央处理器的一种方式 13 识别各种格式的数据可以是上述实施例的方式,在此不再赘述。 [0221] 判断模块 262 被配置为确定移动终端与用户面部之间的距离。 [0222] 判断模块 262 用于确定移动终端与用户面部预设位置的距离; 或确定模块 262 用于确定移动终端与用户面部的至少两个预设位置之间的总距离。 [0223] 预设数值由移动终端默认设置。 [0224] 拍摄请求至少包括第一应用请求和第二应用请求。 当拍摄请求为第一申请请求时,预设数值为第一预设数值。 当拍摄请求为第二应用请求时,预设数值为第二预设数值,第一预设数值与第二预设数值不同。 [0225] 所述功能模块还包括第一获取模块,用于获取第一概率和第二概率,所述第一概率为用户在第一应用状态下使用前置摄像头的概率,所述第二概率为概率 用户在第二应用状态下使用前置摄像头; 第一调整模块,用于根据第一概率和第二概率分别调整第一预设数值和第二预设数值,使得第一概率对应于第一预设数值,第二概率对应于第二 预设数值。 [0226] 所述功能模块还包括第二获取模块,用于获取用户使用前置摄像头和后置摄像头的信息。 第二调整模块,用于根据使用信息调整预设数值。 [0227] 所述功能模块还包括第三获取模块,用于获取用户的个人信息,并根据个人信息调整预设数值。 第三调整模块,用于根据个人信息调整预设数值。 [0228] 所述功能模块还包括第四获取模块,用于获取用户当前所处的环境; 第四调整模块,用于根据预设对应表,将预设数值的具体数值调整为与用户当前所处环境对应的数值,预设对应表存储映射关系 预设数值的不同环境和不同具体数值之间。 [0229] 所述功能模块还包括第五获取模块,用于获取用户输入的预设数值。 [0230] 所述功能模块还包括询问模块,用于向所述用户发送询问请求,所述询问请求用于询问所述用户是否同意开启摄像头。 第六获取模块,用于获取用户的回复; 第一触发单元,用于当回复为同意开启摄像头或在预设时间内未收到回复时,触发控制模块开启移动终端的前置摄像头或后置摄像头 移动终端; 第二触发单元,用于当回复为拒绝开启摄像头时,触发移动终端的默认动作。 [0231]在本发明实施例中,计算模块根据推荐评分计算参数计算第一用户的每个终端号码的推荐评分,发送模块将每个推荐评分发送给第二用户,以便第二用户 选择呼叫推荐等级最高的终端号码,从而准确高效地选择被呼叫号码,避免呼叫失败操作。 [0232] 在本发明的上述实施例中,服务器包括但不限于手机、PDA、平板电脑等移动通信设备的服务器。 [0233] 需要说明的是,本领域普通技术人员可以理解,实施例中方法的全部或部分过程可以通过计算机程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 当程序运行时,执行实施例中方法的流程。 上述存储介质可以包括磁盘、光盘、只读存储器(ROM)或随机存取存储器(RAM)。 [0234] 本领域技术人员可以清楚地了解到,为描述的方便和简洁,上述系统、装置和单元的具体工作过程可以参见上述方法实施例中的对应过程。 ,此处不再赘述。 [0235] 在本申请提供的几个实施例中,应当理解,所公开的系统、装置和方法可以通过其他方式实现。 例如,所描述的装置实施例仅仅是示例性的。 例如,单元划分仅仅是逻辑上的功能划分,实际实现中还可以是其他的划分。 例如,可以将多个单元或组件组合或集成到另一个系统中,或者可以忽略或不执行某些特征。 此外,显示或讨论的相互耦合或直接耦合或通信连接可以通过一些接口来实现。 装置或单元之间的间接耦合或通信连接可以以电子、机械或其他形式实现。 [0236] 被描述为独立部分的单元可以是物理上独立的,也可以不是物理上的,作为单元显示的部分可以是物理单元,也可以不是物理单元,可以位于一个位置,或者可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部单元来实现本实施例方案的目的。 [0237] 另外,本发明实施例中的功能单元可以集成在一个处理单元中,也可以是各个单元在物理上单独存在,或者两个或多个单元集成在一个单元中。 集成单元可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。 [0238] 当集成单元以软件功能单元的形式实现并作为独立产品销售或使用时,集成单元可以存储在计算机可读存储介质中。 基于这样的理解,本发明的技术方案本质上,或者对现有技术有贡献的部分,或者全部或者部分技术方案,可以以软件产品的形式来实现。 该软件产品存储在存储介质中,包括若干指令,用于指示计算机设备(可以是个人计算机、服务器或网络设备)执行本发明实施例中描述的方法的全部或部分步骤。 本公开。 上述存储介质包括U盘、移动硬盘、ROM、RAM、磁盘、光盘等任何可以存储程序代码的介质。 [0239]上述实施例仅用于说明本发明的技术方案,并不用于限制本发明。 尽管结合前述实施例对本发明进行了详细描述,但本领域普通技术人员应当理解,对于前述实施例中描述的技术方案,仍然可以进行修改或者对部分技术特征进行等效替换,而不 脱离本发明实施例技术方案的精神和范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103795864A(String), CN103795864B(String), EP3089434A1(String), EP3089434A4(String), EP3089434B1(String), EP3386174A1(String), EP3386174B1(String), ES2663245T3(String), JP2017511626A(String), JP6293295B2(String), KR101843810B1(String), KR1020160108507A(String), US20160337588A1(String), US9906723B2(String), WO2015113372A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103795864A(String), CN103795864B(String), EP3089434A1(String), EP3089434A4(String), EP3089434B1(String), EP3386174A1(String), EP3386174B1(String), ES2663245T3(String), JP2017511626A(String), JP6293295B2(String), KR101843810B1(String), KR1020160108507A(String), US20160337588A1(String), US9906723B2(String), WO2015113372A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103795864A(String), CN103795864B(String), EP3089434A1(String), EP3089434A4(String), EP3089434B1(String), EP3386174A1(String), EP3386174B1(String), ES2663245T3(String), JP2017511626A(String), JP6293295B2(String), KR101843810B1(String), KR1020160108507A(String), US20160337588A1(String), US9906723B2(String), WO2015113372A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.477 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.477 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.477 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), CN103795864A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270896(Integer), CN103795864B(String), 1047472(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), EP3089434A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), EP3089434A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), EP3089434B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), EP3386174A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), EP3386174B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), ES2663245T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), JP2017511626A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), JP6293295B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), KR101843810B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), KR1020160108507A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), US20160337588A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), US9906723B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:42.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270896(Integer), WO2015113372A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN103795864B(String), CN103795864B(String), 1474992000(Integer), 270896(Integer), 185180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185939(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185939(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.223 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185939(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185939(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185939(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9781547B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for establishing WLAN by mobile terminal, and mobile terminal(String), 移动终端建立WLAN的方法及移动终端(String), US9781547B2(String), Provided are a method for establishing a WLAN by a mobile terminal and a mobile terminal. The method comprises: when the mobile terminal needs to establish a WLAN with other terminals, the mobile terminal starts Bluetooth, and modifies a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; and starts Bluetooth search to acquire Bluetooth MAC addresses of other terminals with the identifiers contained in the name of the Bluetooth device; and a Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN.(String), 提供了一种移动终端建立WLAN的方法及移动终端。 该方法包括:当移动终端需要与其他终端建立WLAN时,移动终端启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 启动蓝牙搜索,以蓝牙设备名称中包含的标识获取其他终端的蓝牙MAC地址; 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。(String), US14/913467(String), 1384358400(Integer), US9781547B2(String), 1506960000(Integer), 1506960000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 5(Integer), CN103037533A | CN103179635A | US20090207445A1 | US20140206346A1 | WO2007057758A2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:43.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185940(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f412197c1bab4d34b057aae6a8a463ca.png(String), 185940(Integer), f412197c1bab4d34b057aae6a8a463ca.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.183 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for establishing WLAN by mobile terminal, and mobile terminal(String), 移动终端建立WLAN的方法及移动终端(String), US9781547B2(String), Provided are a method for establishing a WLAN by a mobile terminal and a mobile terminal. The method comprises: when the mobile terminal needs to establish a WLAN with other terminals, the mobile terminal starts Bluetooth, and modifies a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; and starts Bluetooth search to acquire Bluetooth MAC addresses of other terminals with the identifiers contained in the name of the Bluetooth device; and a Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN.(String), 提供了一种移动终端建立WLAN的方法及移动终端。 该方法包括:当移动终端需要与其他终端建立WLAN时,移动终端启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 启动蓝牙搜索,以蓝牙设备名称中包含的标识获取其他终端的蓝牙MAC地址; 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。(String), US14/913467(String), 1384358400(Integer), US9781547B2(String), 1506960000(Integer), 1506960000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 5(Integer), CN103037533A | CN103179635A | US20090207445A1 | US20140206346A1 | WO2007057758A2(String), \20230420\f412197c1bab4d34b057aae6a8a463ca.png(String), 12(Integer), 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 1. A method for establishing a Wireless Local Area Network (WLAN) by a mobile terminal, comprising:when the mobile terminal needs to establish the WLAN with other terminals, starting a Bluetooth device in the mobile terminal, and modifying a name of the Bluetooth device in the mobile terminal to a character string that contains an identifier;starting Bluetooth search, to acquire Bluetooth Media Access Control (MAC) addresses of the other terminals with the identifier contained in a name of a Bluetooth device in each of the other terminals; andcomparing a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN.(String), 1.一种移动终端建立无线局域网的方法,包括:当移动终端需要与其他终端建立WLAN时,启动移动终端中的蓝牙设备,将移动终端中的蓝牙设备的名称修改为包含标识的字符串。启动蓝牙搜索,获取其他终端的蓝牙媒体访问控制(MAC)地址,以及其他终端中蓝牙设备名称中包含的标识;和分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 2. The method according to claim 1, wherein comparing the Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets the pre-set condition, setting the mobile terminal as the wireless access point of the WLAN comprises:performing character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when a character string of the Bluetooth MAC address of the mobile terminal is a maximum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from the other terminals with the identifier contained in the name of the Bluetooth device; orperforming character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when the character string of the Bluetooth MAC address of the mobile terminal is a minimum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start the wireless access function, receive and agree with the wireless access request of the other terminals with the identifier contained in the name of the Bluetooth device.(String), 2.根据权利要求1所述的方法,其中将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点包括:分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为移动终端的蓝牙MAC地址和获取蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求;或者对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为移动终端的蓝牙MAC地址和获取的蓝牙MAC地址中的最小值时蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 3. The method according to claim 2, wherein setting, when the Bluetooth MAC address of the mobile terminal meets the pre-set condition, the mobile terminal as the wireless access point of the WLAN further comprises:verifying the wireless access request sent by the other terminals with the identifier contained in the name of the Bluetooth device.(String), 3.根据权利要求2所述的方法,其中设置,当移动终端的蓝牙MAC地址满足预设条件时,移动终端作为WLAN的无线接入点还包括:通过蓝牙设备名称中包含的标识验证其他终端发送的无线接入请求。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 4. The method according to claim 1, wherein after the Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, the method further comprises:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, searching for the wireless access point and sending the wireless access request.(String), 4.根据权利要求1所述的方法,其中将移动终端的蓝牙MAC地址分别与获取的蓝牙MAC地址进行比较后,该方法还包括:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 5. The method according to claim 1, wherein starting the Bluetooth search to acquire the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device comprises:starting the Bluetooth search, setting a search condition as containing the identifier in the name of the Bluetooth device, and acquiring the Bluetooth MAC addresses of the other terminals with the identifier contained in the name of the Bluetooth device.(String), 5.根据权利要求1所述的方法,其中启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址,包括:启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,并获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。6、一种建立无线局域网的移动终端,包括:启动及修改模块,用于当移动终端需要与其他终端建立WLAN时,启动移动终端中的蓝牙设备,并将移动终端的蓝牙设备名称修改为包含标识的字符串;搜索获取模块,用于启动蓝牙搜索,获取其他终端的蓝牙媒体访问控制(MAC)地址,以及其他终端中蓝牙设备名称中包含的标识;和比较执行模块,用于分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为无线接入点无线局域网。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 6. A mobile terminal for establishing a Wireless Local Area Network, comprising:a start and modification component configured to, when the mobile terminal needs to establish the WLAN with other terminals, start a Bluetooth device in the mobile terminal, and modify a name of the Bluetooth device of the mobile terminal to a character string that contains an identifier;a search and acquisition component configured to start Bluetooth search, to acquire Bluetooth media access control (MAC) addresses of the other terminals with the identifier contained in a name of a Bluetooth device in each of the other terminals; anda comparison and execution component configured to compare a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, set the mobile terminal as a wireless access point of the WLAN.(String), 7.根据权利要求6所述的移动终端,其中比较和执行组件配置为:分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串是移动终端的蓝牙MAC地址和获取蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求;或者分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为移动终端的蓝牙MAC地址和获取蓝牙MAC地址,将移动终端设置为无线接入点,启动无线接入功能,接收并同意其他终端的无线接入请求,该终端带有蓝牙设备名称中的标识。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 7. The mobile terminal according to claim 6, wherein the comparison and execution component is configured to:perform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when a character string of the Bluetooth MAC address of the mobile terminal is a maximum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from the other terminals with the identifier contained in a name of a Bluetooth device; orperform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when a character string of the Bluetooth MAC address of the mobile terminal is a minimum one of the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start the wireless access function, receive and agree with the wireless access request from the other terminals with the identifier contained in the name of the Bluetooth device.(String), 8.根据权利要求7所述的移动终端,其中比较执行组件进一步配置为:通过蓝牙设备名称中包含的标识符验证其他终端发送的无线接入请求。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 8. The mobile terminal according to claim 7, wherein the comparison and execution component is further configured to:verify the wireless access request sent by the other terminals with the identifier contained in the name of the Bluetooth device.(String), 9.根据权利要求6所述的移动终端,其中比较执行组件进一步配置为:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 9. The mobile terminal according to claim 6, wherein the comparison and execution component is further configured to:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, search for the wireless access point and send the wireless access request.(String), 10.根据权利要求6所述的移动终端,其中搜索和获取组件进一步配置为:启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 10. The mobile terminal according to claim 6, wherein the search and acquisition component is further configured to:start the Bluetooth search, set a search condition as containing the identifier in the name of the Bluetooth device, and acquire the Bluetooth MAC addresses of the other terminals with the identifier contained in the name of the Bluetooth device.(String), 11.根据权利要求2所述的方法,其中将移动终端的蓝牙MAC地址分别与获取的蓝牙MAC地址进行比较后,该方法还包括:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 11. The method according to claim 2, wherein after the Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses respectively, the method further comprises:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, searching for the wireless access point and sending the wireless access request.(String), 12.根据权利要求7所述的移动终端,其中比较执行组件进一步配置为:当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185940(Integer), 12. The mobile terminal according to claim 7, wherein the comparison and execution component is further configured to:when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, search for the wireless access point and send the wireless access request.(String), 1(Integer), 11(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.511 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.511 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185940(Integer), TECHNICAL FIELD [0001]The present disclosure relates to the technical field of mobile communications, and in particular to a method for establishing a Wireless Local Area Network (WLAN) by a mobile terminal, and the mobile terminal. BACKGROUND [0002]With the popularization of mobile intelligent devices, the need for establishing a WLAN between mobile terminals in a short distance to share files is increasing. In establishing the WLAN between mobile terminals in a short distance, one of the mobile terminals is required to serve as a wireless access point (Access Point, referred to as AP for short), and other mobile terminals join the AP, so that the WLAN is established for communication. [0003]However, in the related art, the establishment of the WLAN among mobile terminals requires a user to have a certain network technologies base, which brings difficulty to the operation of common users; in addition, users of different mobile terminals are required to coordinate and determine, in the process of establishing the WLAN, which side serves as a wireless access point and which side serves as a common request access end, and the operation is quite complex, thereby reducing the interest of a user in establishing a WLAN for files sharing, and being not beneficial to the promotion of applications related to a WLAN of a mobile terminal. SUMMARY [0004]The embodiments of the present disclosure provide a method for establishing a WLAN by a mobile terminal, and a mobile terminal, so as to more conveniently and quickly establish a WLAN. [0005]The embodiments of the present disclosure provide a method for establishing a WLAN by a mobile terminal, comprising: [0006]when the mobile terminal needs to establish a WLAN with other terminals, starting Bluetooth, and modifying a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; [0007]starting Bluetooth search to acquire Bluetooth media access control (Media Access Control, referred to as MAC for short) addresses of other terminals with the identifier contained in the name of the Bluetooth device; and [0008]comparing a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN. [0009]Preferably, comparing the Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, setting the mobile terminal as a wireless access point of the WLAN comprises: [0010]performing character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in a name in a Bluetooth device; or [0011]performing character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the Bluetooth MAC addresses, setting the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in the name of the Bluetooth device. [0012]Preferably, setting the mobile terminal as the wireless access point of the WLAN when the Bluetooth MAC address of the mobile terminal meets the pre-set condition further comprises: [0013]verifying the wireless access request sent by other terminals with the identifier contained in the name of the Bluetooth device. [0014]Preferably, after comparing the Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, the method further comprises: [0015]when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, searching for the wireless access point and sending the wireless access request. [0016]Preferably, starting Bluetooth search to acquire the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device comprises: [0017]starting the Bluetooth search, setting a search condition as containing the identifier in the name of the Bluetooth device, and acquiring the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device. [0018]The embodiments of the present disclosure further provide a mobile terminal for establishing a WLAN, wherein the device comprises: [0019]a start and modification component configured to start Bluetooth when the mobile terminal needs to establish a WLAN with other terminals, and modify a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier; [0020]a search and acquisition component configured to start Bluetooth search to acquire Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device; and [0021]a comparison and execution component configured to compare a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, set the mobile terminal as a wireless access point of the WLAN. [0022]Preferably, the comparison and execution component is configured to: [0023]perform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in the name of the Bluetooth device; or [0024]perform character string comparison on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC address, and when a character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the Bluetooth MAC addresses, set the mobile terminal as the wireless access point to start a wireless access function, receive and agree with a wireless access request from other terminals with the identifier contained in the name of the Bluetooth device. [0025]Preferably, the comparison and execution component is further configured to: [0026]verify the wireless access request sent by other terminals with the identifier contained in the name of the Bluetooth device. [0027]Preferably, the comparison and execution component is further configured to: [0028]when the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, search for the wireless access point and send the wireless access request. [0029]Preferably, the search and acquisition component is further configured to: [0030]start the Bluetooth search, set a search condition as containing the identifier in the name of the Bluetooth device, and acquire the Bluetooth MAC addresses of other terminals with the identifier contained in the name of the Bluetooth device. [0031]The method for establishing a WLAN by a mobile terminal, and the mobile terminal are provided by the embodiments of the present disclosure, in which Bluetooth MAC addresses of other terminals intending to establish the WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when a character string of a Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as a wireless access point to start a wireless access function to receive a wireless access request of other terminals so as to establish the WLAN; and since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. BRIEF DESCRIPTION OF THE DRAWINGS [0032]FIG. 1 shows a schematic flowchart of a method for establishing a WLAN by a mobile terminal according to a preferred embodiment of the present disclosure; and [0033]FIG. 2 shows a structural schematic diagram of a mobile terminal for establishing a WLAN in a preferred embodiment of the present disclosure. [0034]To make the technical solutions of the present disclosure more clear, the present disclosure is further described in detail hereinafter in conjunction with the drawings. DETAILED DESCRIPTION OF THE EMBODIMENTS [0035]The solution of the embodiments of the present disclosure is mainly: Bluetooth MAC addresses of other terminals intending to establish a WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when a character string of a Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as a wireless access point to start a wireless access function to receive a wireless access request from other terminals so as to establish the WLAN. Since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved. [0036]As shown in FIG. 1, the preferred embodiment of the present disclosure provides a method for establishing a WLAN by a mobile terminal. [0037]In the step S101, when a mobile terminal needs to establish a WLAN with other terminals, Bluetooth is started, and a name of a Bluetooth device of the mobile terminal is modified to a character string that contains an identifier. [0038]In the present embodiment, the mobile terminal has a Bluetooth function, and when the mobile terminal needs to establish the WLAN with other terminals, Bluetooth is started, and the name of the Bluetooth device thereof is modified to the character string that contains the identifier, wherein the identifier may be a feature field for setting an identification for several terminals that need to establish the WLAN for identification, so that the interference of other unrelated terminals is avoided. [0039]In step S102, Bluetooth search is started to acquire Bluetooth MAC addresses, of other terminals with the identifier above contained in a name of a Bluetooth device. [0040]After modifying the name of the Bluetooth device thereof to the character string that contains the identifier, the mobile terminal uses Bluetooth for search, and sets a search condition as containing the identifier above in the name of the Bluetooth device, so as to ensure that the identified terminals are other terminals needing to establish the WLAN, thereby avoiding wasting time searching other unrelated terminals, and saving the time for search. [0041]After other terminals with the identifier above contained in the name of the Bluetooth device are searched, the Bluetooth MAC addresses of the Bluetooth devices containing the identifier above in the name of the Bluetooth device are acquired and recorded. An MAC address is also called physical address for representing an identifier of each site on the Internet, with a hexadecimal number being adopted, six bytes in total (48-bit). A Bluetooth MAC address of each terminal is unique, and is not the same as that of other terminals, and therefore the acquired and recorded Bluetooth MAC addresses of the Bluetooth devices containing the identifier above in the name of the Bluetooth device and the several terminals needing to establish the WLAN are in one-to-one correspondence. [0042]In Step S103, a Bluetooth MAC address of the mobile terminal is compared with the acquired Bluetooth MAC addresses, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, the mobile terminal is set as a wireless access point of the WLAN. [0043]Comparison of a character string size is performed on a Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when the comparison is performed, the comparison is begun from a first character in the leftmost of the character string, and if a character size is compared, the comparison is stopped, and the character string with a large character is great; and if the character is the same, the next character continues to be compared in sequence from left to right until the character size is compared, and a character string with a large character is determined to be great. [0044]When the character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the acquired Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request from other terminals with the identifier above contained in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point; and in one optional implementation of the present embodiment, when the character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the acquired Bluetooth MAC addresses, the mobile terminal may further be set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request of other terminals containing the identifier above in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point. [0045]When the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, that is to say, the character string of the Bluetooth MAC address of the mobile terminal is neither the maximum one in all the acquired Bluetooth MAC addresses nor is it the minimum one in all the acquired Bluetooth MAC addresses, it indicates that the maximum or minimum character string is one of the acquired Bluetooth MAC addresses, a terminal corresponding thereto serving as the wireless access point starts a wireless access function, and then the mobile terminal only needs to search for the wireless access point and sends a wireless access request to the searched wireless access point, i.e. being able to join the established WLAN, which is also quite convenient. [0046]Thereby, only via the Bluetooth on the mobile terminal, a user may determine which side serves as the wireless access point and which side serves as a common request access end in several terminals that need to establish the WLAN, so as to establish the WLAN, which is very convenient and quick. [0047]In one optional implementation of the present embodiment, if the mobile terminal serving as the wireless access point starts its own wireless access function, after receiving the wireless access requests from other terminals with the identifier above contained in the name of the Bluetooth device, the mobile terminal also further verifies the wireless access request above, and after the verification performed by the mobile terminal succeeds, a terminal corresponding to the successfully-verified wireless access request is joined in the established WLAN, such that the mobile terminal serving as the wireless access point needing to establish the WLAN can screen other terminals that request to join the WLAN, which is more flexible, ensures that other terminals joining the WLAN are reliable and verified and agreed by the wireless access point, and improves the security of the WLAN. [0048]Through the above-mentioned solution of the present embodiment, Bluetooth MAC addresses of other terminals intending to establish the WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when the character string of the Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start a wireless access function to receive a wireless access request from other terminals so as to establish the WLAN; and since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. [0049]As shown in FIG. 2, a preferred embodiment of the present disclosure provides a mobile terminal for establishing a WLAN. The device comprises: a start and modification component 201, a search and acquisition component 202 and a comparison and execution component 203. [0050]The start and modification component 201 is configured to start Bluetooth when the mobile terminal needs to establish a WLAN with other terminals, and modify a name of a Bluetooth device of the mobile terminal to a character string that contains an identifier. [0051]In the present embodiment, the mobile terminal has a Bluetooth function, and when the mobile terminal needs to establish a WLAN with other terminals, Bluetooth is started, and the name of a Bluetooth device thereof is modified to a character string that contains an identifier, wherein the identifier may be a feature field for setting an identification for identifying several terminals that need to establish the WLAN, so that the interference of other unrelated terminals is avoided. [0052]The search and acquisition component 202 is configured to start Bluetooth search to acquire Bluetooth MAC addresses from other terminals with the identifier contained in the name of the Bluetooth device. [0053]After modifying the name of the Bluetooth device thereof to the character string that contains the identifier, the mobile terminal uses Bluetooth for search, and sets a search condition as containing the identifier above in the name of the Bluetooth device, so as to ensure that the identified terminals are other terminals needing to establish the WLAN, thereby avoiding wasting time searching other unrelated terminals, and saving the time for search. [0054]After other terminals with the identifier above contained in the name of the Bluetooth device are found, the Bluetooth MAC addresses of the Bluetooth devices containing the identifier above in the name of the Bluetooth device are acquired and recorded. An MAC address is also called physical address for representing an identifier of each site on the Internet, with a hexadecimal number being adopted, six bytes in total (48-bit). A Bluetooth MAC address of each terminal is unique, and is not the same as that of other terminals, and therefore the acquired and recorded Bluetooth MAC addresses of the Bluetooth device containing the identifier above in the name of the Bluetooth device and the several terminals needing to establish the WLAN are in one-to-one correspondence. [0055]The comparison and execution component 203 is configured to compare a Bluetooth MAC address of the mobile terminal with the acquired Bluetooth MAC addresses respectively, and when the Bluetooth MAC address of the mobile terminal meets a pre-set condition, set the mobile terminal as a wireless access point of the WLAN. [0056]Comparison of a character string size is performed on the Bluetooth MAC address of the mobile terminal and the acquired Bluetooth MAC addresses respectively, and when the comparison is performed, the comparison is begun from a first character in the leftmost of the character string, and if the character size is compared, the comparison is stopped, and the character string with a large character is great; and if the character is the same, the next character continues to be compared in sequence from left to right until the character size is compared, and a character string with a large character is determined to be great. [0057]When the character string of the Bluetooth MAC address of the mobile terminal is the maximum one in all the acquired Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request from other terminals with the identifier above contained in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point; and in one optional implementation of the present embodiment, when the character string of the Bluetooth MAC address of the mobile terminal is the minimum one in all the acquired Bluetooth MAC addresses, the mobile terminal may further be set as the wireless access point to start its own wireless access function to receive and agree with a wireless access request from other terminals with the identifier above contained in the name of the Bluetooth device, so as to establish the WLAN using the mobile terminal as the wireless access point. [0058]When the Bluetooth MAC address of the mobile terminal does not meet the pre-set condition, that is, the character string of the Bluetooth MAC address of the mobile terminal is neither the maximum one in all the acquired Bluetooth MAC addresses nor is it the minimum one in all the acquired Bluetooth MAC addresses, it indicates that the maximum or minimum character string is one of the acquired Bluetooth MAC addresses, a terminal corresponding thereto serving as the wireless access point starts a wireless access function, and then the mobile terminal only needs to search for the wireless access point and sends a wireless access request to the found wireless access point, i.e. being able to join the established WLAN, which is also quite convenient. [0059]Thereby, only via the Bluetooth on the mobile terminal, a user may determine which side serves as the wireless access point and which side serves as a common request access end in several terminals that need to establish the WLAN, so as to establish the WLAN, which is very convenient and quick. [0060]In one optional implementation of the present embodiment, if the mobile terminal serving as the wireless access point starts its own wireless access function, after receiving the wireless access request from other terminals with the identifier contained in the name of the Bluetooth device, the mobile terminal also further verifies the wireless access request above, and after the verification performed by the mobile terminal succeeds, a terminal corresponding to the successfully-verified wireless access request is joined in the established WLAN, such that the mobile terminal serving as the wireless access point needing to establish the WLAN can screen other terminals that request to join the WLAN, which is more flexible, ensures that other terminals joining the WLAN are reliable and verified and agreed by the wireless access point, and improves the security of the WLAN. [0061]Through the above-mentioned solution of the present embodiment, since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. [0062]The method for establishing a WLAN by a mobile terminal, and the mobile terminal are provided by the present disclosure, in which Bluetooth MAC addresses of other terminals intending to establish the WLAN are acquired through Bluetooth search of a mobile terminal according to a character string containing an identifier, and when the character string of the Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as the wireless access point to start a wireless access function to receive a wireless access request of other terminals so as to establish the WLAN; and since a user is not required to coordinate and determine the wireless access point and a common request access end, the quickness and simplicity of establishing the WLAN by the user via the mobile terminal are improved, and sharing files by the user by establishing the WLAN is greatly facilitated. [0063]It can be clearly understood by persons skilled in the art that, for the purpose of convenient and brief description, only the foregoing division of the functional units and components is taken as an example for illustration, in actual applications, the foregoing functions can be allocated for being completed by different functional units or components according to the needs, i.e. dividing the internal structure of an apparatus into different functional units or components to complete all or some of the foregoing functions. Various functional units and components in the embodiments may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit, and the foregoing integrated unit may be implemented in a form of hardware, or may also be implemented in a form of a software function unit. In addition, the specific names of all functional units and components are only intended to distinguish between each other, but are not used to limit the protection scope of the present application. For the specific working process of the units and components in the foregoing apparatus, reference may be made to the corresponding process in the foregoing method embodiments, and details are not described herein again. [0064]The foregoing descriptions are only preferable embodiments of the present disclosure, and the patent scope of the present disclosure is not limited thereto. Any equivalent structure or process variation made by using the content of the description and drawings of the present disclosure, or any direct or indirect application of them in other relevant technical fields, shall all fall within the patent protection scope of the present disclosure INDUSTRIAL APPLICABILITY [0065]The above-mentioned technical solution provided by the present disclosure may be applied to the process of establishing a WLAN, in which the technical solution that Bluetooth MAC addresses of other terminals intending to establish the WLAN is acquired by using a character string containing an identifier through Bluetooth search of a mobile terminal, and when a character string of a Bluetooth MAC address of the mobile terminal is the maximum or minimum one in all the Bluetooth MAC addresses, the mobile terminal is set as a wireless access point to start a wireless access function is adopted to receive a wireless access request from other terminals so as to establish the WLAN, thereby improving the quickness and simplicity of establishing a WLAN by a user via a mobile terminal, and greatly facilitating a user to share files by establishing a WLAN.(String), 技术领域 [0001] 本发明涉及移动通信技术领域,尤其涉及一种移动终端建立无线局域网的方法及移动终端。 背景 [0002] 随着移动智能设备的普及,移动终端之间近距离建立无线局域网共享文件的需求越来越大。 在近距离移动终端之间建立WLAN时,需要其中一个移动终端作为无线接入点(Access Point,简称AP),其他移动终端加入该AP,从而实现WLAN 建立通信。 [0003] 然而,在相关技术中,移动终端之间建立WLAN需要用户具有一定的网络技术基础,这给普通用户的操作带来了困难; 另外,不同移动终端的用户在建立WLAN的过程中需要协调确定哪一侧作为无线接入点,哪一侧作为共同请求接入端,操作较为复杂,从而 降低了用户建立WLAN进行文件共享的兴趣,不利于移动终端WLAN相关应用的推广。 概括 [0004] 本发明实施例提供一种移动终端建立WLAN的方法及移动终端,能够更加方便快捷地建立WLAN。 [0005] 本发明实施例提供一种移动终端建立WLAN的方法,包括: [0006] 当移动终端需要与其他终端建立WLAN时,启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串; [0007] 启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙媒体访问控制(Media Access Control,简称MAC)地址; 和 [0008] 分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。 [0009] 优选地,分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点,包括: [0010] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最大的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意蓝牙设备名称中包含标识的其他终端的无线接入请求; 要么 [0011] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最小的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求。 [0012] 优选地,当移动终端的蓝牙MAC地址满足预设条件时,设置移动终端为WLAN的无线接入点还包括: [0013] 通过蓝牙设备名称中包含的标识验证其他终端发送的无线接入请求。 [0014] 优选地,将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址分别进行比较后,该方法还包括: [0015]当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。 [0016] 优选地,启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址,包括: [0017] 启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,并获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。 [0018] 本发明实施例还提供了一种建立WLAN的移动终端,其特征在于,所述装置包括: [0019] 启动及修改模块,用于在移动终端需要与其他终端建立WLAN时启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串; [0020] 搜索获取模块,用于启动蓝牙搜索,获取蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址; 和 [0021] 比较执行模块,用于分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为无线接入点 无线局域网。 [0022] 优选地,所述比较执行模块被配置为: [0023] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最大的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求; 要么 [0024] 将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行字符串比较,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最小的一个时,将移动终端设置为 无线接入点启动无线接入功能,接收并同意其他带有蓝牙设备名称中标识的终端的无线接入请求。 [0025] 优选地,所述比较执行模块还用于: [0026] 通过蓝牙设备名称中包含的标识符验证其他终端发送的无线接入请求。 [0027] 优选地,所述比较执行模块还用于: [0028] 当移动终端的蓝牙MAC地址不满足预设条件时,搜索无线接入点并发送无线接入请求。 [0029] 优选地,所述搜索获取模块还用于: [0030] 启动蓝牙搜索,将搜索条件设置为包含蓝牙设备名称中的标识,获取带有蓝牙设备名称中包含的标识的其他终端的蓝牙MAC地址。 [0031]本发明实施例提供了一种移动终端建立WLAN的方法及移动终端,通过移动终端的蓝牙搜索,获取其他有意建立WLAN的终端的蓝牙MAC地址。 包含标识的字符串,当移动终端的蓝牙MAC地址的字符串为所有蓝牙MAC地址中最大或最小的一个时,将移动终端设置为无线接入点,启动无线接入功能以 接收其他终端的无线接入请求,建立WLAN; 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性,用户通过建立WLAN共享文件 大大方便了。 附图的简要说明 [0032] 图1示出了根据本发明一个优选实施例的移动终端建立WLAN的方法的流程示意图; 和 [0033] 图2示出了本发明优选实施例中用于建立WLAN的移动终端的结构示意图。 [0034] 为使本发明的技术方案更加清楚明白,下面结合附图对本发明作进一步详细说明。 具体实施方式 [0035] 本发明实施例的方案主要是:根据包含标识的字符串通过移动终端的蓝牙搜索获取其他有意建立WLAN的终端的蓝牙MAC地址,当蓝牙MAC的字符串为 移动终端的地址为所有蓝牙MAC地址中最大或最小的一个,则将移动终端设置为无线接入点,启动无线接入功能,接收其他终端的无线接入请求,建立WLAN。 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性。 [0036] 如图1所示,本发明优选实施例提供了一种移动终端建立WLAN的方法。 [0037] 在步骤S 101 ,当移动终端需要与其他终端建立WLAN时,启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 [0038] 本实施例中,移动终端具有蓝牙功能,当移动终端需要与其他终端建立WLAN时,启动蓝牙,并将其蓝牙设备名称修改为包含标识的字符串, 其中,标识可以是特征字段,用于为需要建立WLAN进行识别的多个终端设置标识,避免其他无关终端的干扰。 [0039] 在步骤S 102 ,开始搜索蓝牙,获取蓝牙设备名称中包含上述标识的其他终端的蓝牙MAC地址。 [0040] 移动终端将自身的蓝牙设备名称修改为包含该标识的字符串后,使用蓝牙进行搜索,将搜索条件设置为蓝牙设备名称中包含上述标识,从而保证 识别出的终端是其他需要建立WLAN的终端,避免了浪费时间搜索其他不相关的终端,节省了搜索的时间。 [0041]在搜索到蓝牙设备名称中包含上述标识的其他终端后,获取并记录蓝牙设备名称中包含上述标识的蓝牙设备的蓝牙MAC地址。 MAC地址也称为物理地址,表示Internet上各个站点的标识,采用十六进制数,共6字节(48位)。 每个终端的蓝牙MAC地址是唯一的,不与其他终端相同,因此获取和记录的蓝牙设备名称中包含上述标识的蓝牙设备的蓝牙MAC地址和需要的多个终端 建立WLAN是一一对应的。 [0042] 在步骤S 103 ,将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。 [0043] 分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串大小的比较,比较时,从字符串最左边的第一个字符开始比较,如果 比较字符大小,停止比较,字符大的字符串为大; 如果字符相同,则继续从左到右依次比较下一个字符,直到比较字符大小,确定字符大的字符串为大。 [0044] 当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最大的一个时,移动终端设置为无线接入点,启动自身的无线接入功能,接收并同意无线接入 其他终端请求蓝牙设备名称中包含上述标识,建立以移动终端为无线接入点的WLAN; 并且在本实施例的一种可选实施方式中,当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最小的一个时,还可以将移动终端设置为无线接入点,启动其无线接入点。 自身的无线接入功能,接收并同意蓝牙设备名称中包含上述标识的其他终端的无线接入请求,从而建立以移动终端为无线接入点的WLAN。 [0045] 当移动终端的蓝牙MAC地址不满足预设条件时,即移动终端的蓝牙MAC地址字符串既不是获取的所有蓝牙MAC地址中最大的,也不是 获取的所有蓝牙MAC地址中最小的一个,表示最大或最小的字符串为获取的蓝牙MAC地址之一,其对应的作为无线接入点的终端启动无线接入功能,则移动终端 只需要搜索无线接入点,向搜索到的无线接入点发送无线接入请求,即可加入已建立的WLAN,也相当方便。 [0046] 从而,用户仅通过移动终端上的蓝牙,就可以在多个需要建立WLAN的终端中确定哪一侧作为无线接入点,哪一侧作为共同请求接入端,从而建立WLAN, 非常方便快捷。 [0047]在本实施例的一种可选实施方式中,如果作为无线接入点的移动终端启动了自身的无线接入功能,则在接收到蓝牙设备名称中包含上述标识的其他终端的无线接入请求后,该移动终端 终端还对上述无线接入请求进行验证,在移动终端验证成功后,将验证成功的无线接入请求对应的终端加入到已建立的WLAN中,使得移动终端作为无线接入点 需要建立WLAN的可以屏蔽其他请求加入WLAN的终端,更加灵活,保证其他加入WLAN的终端是可靠的,并且是经过无线接入点验证同意的,提高了WLAN的安全性。 [0048] 通过本实施例的上述方案,根据包含标识的字符串通过移动终端的蓝牙搜索获取其他有意建立WLAN的终端的蓝牙MAC地址,当该蓝牙MAC地址的字符串 移动终端的MAC地址为所有蓝牙MAC地址中最大或最小的一个,则将移动终端设置为无线接入点,启动无线接入功能,接收其他终端的无线接入请求,建立WLAN。 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性,用户通过建立WLAN共享文件 大大方便了。 [0049] 如图2所示,本发明一个优选实施例提供了一种建立WLAN的移动终端。 该装置包括:启动和修改组件 201 ,一个搜索和获取组件 202 以及比较和执行组件 203 . [0050] 启动和修改组件 201 用于在移动终端需要与其他终端建立WLAN时启动蓝牙,将移动终端的蓝牙设备名称修改为包含标识的字符串。 [0051] 本实施例中,移动终端具有蓝牙功能,当移动终端需要与其他终端建立WLAN时,启动蓝牙,并将其蓝牙设备名称修改为包含标识的字符串, 其中,标识可以是特征字段,用于设置标识,用于标识需要建立WLAN的若干个终端,从而避免其他无关终端的干扰。 [0052] 搜索和获取组件 202 用于启动蓝牙搜索,从其他终端获取蓝牙设备名称中包含的标识的蓝牙MAC地址。 [0053] 移动终端将自身的蓝牙设备名称修改为包含该标识的字符串后,使用蓝牙进行搜索,将搜索条件设置为蓝牙设备名称中包含上述标识,从而保证 识别出的终端是其他需要建立WLAN的终端,避免了浪费时间搜索其他不相关的终端,节省了搜索的时间。 [0054] 在搜索到蓝牙设备名称中包含上述标识的其他终端后,获取并记录蓝牙设备名称中包含上述标识的蓝牙设备的蓝牙MAC地址。 MAC地址也称为物理地址,表示Internet上各个站点的标识,采用十六进制数,共6字节(48位)。 每个终端的蓝牙MAC地址是唯一的,不与其他终端相同,因此获取和记录的蓝牙设备的蓝牙MAC地址包含蓝牙设备名称中的上述标识以及需要的多个终端 建立WLAN是一一对应的。 [0055]比较和执行组件 203 用于分别将移动终端的蓝牙MAC地址与获取的蓝牙MAC地址进行比较,当移动终端的蓝牙MAC地址满足预设条件时,将移动终端设置为WLAN的无线接入点。 [0056] 分别对移动终端的蓝牙MAC地址和获取的蓝牙MAC地址进行字符串大小比较,比较时从字符串最左边的第一个字符开始比较,如果 比较字符大小,停止比较,字符大的字符串为大; 如果字符相同,则继续从左到右依次比较下一个字符,直到比较字符大小,确定字符大的字符串为大。 [0057] 当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最大的一个时,移动终端设置为无线接入点,启动自身的无线接入功能,接收并同意无线接入 其他终端请求蓝牙设备名称中包含上述标识,建立以移动终端为无线接入点的WLAN; 并且在本实施例的一种可选实施方式中,当移动终端的蓝牙MAC地址字符串为获取的所有蓝牙MAC地址中最小的一个时,还可以将移动终端设置为无线接入点,启动其无线接入点。 自身的无线接入功能,接收并同意蓝牙设备名称中包含上述标识的其他终端的无线接入请求,从而建立以移动终端为无线接入点的WLAN。 [0058] 当移动终端的蓝牙MAC地址不满足预设条件时,即移动终端的蓝牙MAC地址字符串既不是获取的所有蓝牙MAC地址中最大的,也不是最小的 获取的所有蓝牙MAC地址中的一个,表示最大或最小字符串为获取的蓝牙MAC地址之一,其对应的作为无线接入点的终端启动无线接入功能,则移动终端只需要 搜索无线接入点,向搜索到的无线接入点发送无线接入请求,即可以加入已建立的WLAN,也很方便。 [0059] 从而,用户仅通过移动终端上的蓝牙,就可以在多个需要建立WLAN的终端中确定哪一侧作为无线接入点,哪一侧作为共同请求接入端,从而建立WLAN, 非常方便快捷。 [0060] 在本实施例的一种可选实施方式中,如果作为无线接入点的移动终端开启了自身的无线接入功能,则移动终端在接收到来自其他终端的无线接入请求后,该无线接入请求带有蓝牙设备名称中包含的标识, 还进一步对上述无线接入请求进行验证,在移动终端验证成功后,将验证成功的无线接入请求对应的终端加入到已建立的WLAN中,使得作为无线接入点的移动终端需要 建立WLAN可以屏蔽其他请求加入WLAN的终端,更加灵活,保证其他加入WLAN的终端是可靠的,并且是经过无线接入点验证同意的,提高了WLAN的安全性。 [0061] 通过本实施例的上述方案,由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性, 大大方便了用户通过建立WLAN来共享文件。 [0062]本发明提供一种移动终端建立WLAN的方法及移动终端,通过移动终端的蓝牙搜索,根据包含以下内容的字符串获取其他有意建立WLAN的终端的蓝牙MAC地址。 标识,当移动终端的蓝牙MAC地址字符串为所有蓝牙MAC地址中最大或最小的一个时,将移动终端设置为无线接入点,启动无线接入功能,接收无线信号 其他终端接入请求建立WLAN; 由于不需要用户协调确定无线接入点和共同请求的接入端,提高了用户通过移动终端建立WLAN的快捷性和简便性,用户通过建立WLAN共享文件 大大方便了。 [0063] 本领域的技术人员可以清楚地了解到,为描述的方便和简洁起见,仅以上述功能单元和组件的划分为例进行说明,在实际应用中,可以将上述功能进行分配 根据需要由不同的功能单元或部件来完成,即将装置的内部结构划分为不同的功能单元或部件来完成上述全部或部分功能。 实施例中的各个功能单元和部件可以集成为一个处理单元,或者各个单元物理上单独存在,或者两个或多个单元集成为一个单元,上述集成的单元可以采用硬件的形式实现 ,或者也可以以软件功能单元的形式实现。 另外,各功能单元和部件的具体名称只是为了相互区分,并不用于限定本申请的保护范围。 上述装置中各单元和部件的具体工作过程可以参见上述方法实施例中的对应过程,在此不再赘述。 [0064] 以上所述仅为本发明的优选实施例而已,并不限于本发明的专利范围。 利用本发明的说明书和附图的内容而作出的等效结构或工艺变化,或者将其直接或间接应用于其他相关技术领域,均属于本发明的专利保护范围 工业实用性 [0065] 本发明提供的上述技术方案可以应用于建立WLAN的过程中,其中通过包含标识符的字符串获取其他有意建立WLAN的终端的蓝牙MAC地址的技术方案 搜索移动终端的蓝牙,当移动终端的蓝牙MAC地址字符串为所有蓝牙MAC地址中最大或最小的一个时,将移动终端设置为无线接入点,启动无线接入功能 本发明通过接收其他终端的无线接入请求建立WLAN,提高了用户通过移动终端建立WLAN的快捷性和简便性,大大方便了用户通过建立WLAN共享文件。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104427579A(String), KR1020160045772A(String), US20160212572A1(String), US9781547B2(String), WO2014169633A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104427579A(String), KR1020160045772A(String), US20160212572A1(String), US9781547B2(String), WO2014169633A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104427579A(String), KR1020160045772A(String), US20160212572A1(String), US9781547B2(String), WO2014169633A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270942(Integer), CN104427579A(String), 1047589(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270942(Integer), KR1020160045772A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270942(Integer), US20160212572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270942(Integer), US9781547B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270942(Integer), WO2014169633A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104427579A(String), CN104427579A(String), 1426608000(Integer), 270942(Integer), 185226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:44.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185940(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185940(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185940(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185940(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.261 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权 | 权利转移(String), 3(Integer), 185940(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.538 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.538 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8825010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Cell locking method for mobile terminal and mobile terminal capable of locking cell(String), 移动终端的小区锁定方法及能够锁定小区的移动终端(String), US8825010B2(String), A cell locking method for a mobile terminal and a mobile terminal capable of locking a cell are disclosed in the present invention. The method includes: the mobile terminal acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell; judging whether the SID, NID, BASE ID and PN are already stored in a database of the mobile terminal, if yes, then setting the mobile terminal to a normal status; judging whether the SID, the NID, and the PN are already stored in the database of the mobile terminal and the database is not full, or whether the BASE ID and PN are already stored in the database of the mobile terminal, if yes, then transferring to D; and D. writing the SID, NID, BASE ID and PN into the database of the mobile terminal.(String), 本发明公开了一种移动终端的小区锁定方法及能够锁定小区的移动终端。 该方法包括:移动终端获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN)。 判断SID、NID、BASE ID和PN是否已经存储在移动终端的数据库中,如果是,则将移动终端设置为正常状态。 判断SID、NID、PN是否已经存入移动终端数据库且数据库未满,或者BASE ID和PN是否已经存入移动终端数据库,如果是,则 转移到 D; D.将SID、NID、BASE ID和PN写入移动终端的数据库。(String), US13/501299(String), 1282665600(Integer), US8825010B2(String), 1409587200(Integer), 1409587200(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 12(Integer), CN100428820C | CN101072439A | CN101668285A | US20040048597A1 | US20060217130A1 | US20080287140A1 | US20090098873A1 | US20090129327A1 | US20090135731A1 | US20100002611A1 | US20100279705A1 | US8054803B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:45.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185941(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\896cb8bebb7944029d9eab4a0f0c8b83.png(String), 185941(Integer), 896cb8bebb7944029d9eab4a0f0c8b83.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Cell locking method for mobile terminal and mobile terminal capable of locking cell(String), 移动终端的小区锁定方法及能够锁定小区的移动终端(String), US8825010B2(String), A cell locking method for a mobile terminal and a mobile terminal capable of locking a cell are disclosed in the present invention. The method includes: the mobile terminal acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell; judging whether the SID, NID, BASE ID and PN are already stored in a database of the mobile terminal, if yes, then setting the mobile terminal to a normal status; judging whether the SID, the NID, and the PN are already stored in the database of the mobile terminal and the database is not full, or whether the BASE ID and PN are already stored in the database of the mobile terminal, if yes, then transferring to D; and D. writing the SID, NID, BASE ID and PN into the database of the mobile terminal.(String), 本发明公开了一种移动终端的小区锁定方法及能够锁定小区的移动终端。 该方法包括:移动终端获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN)。 判断SID、NID、BASE ID和PN是否已经存储在移动终端的数据库中,如果是,则将移动终端设置为正常状态。 判断SID、NID、PN是否已经存入移动终端数据库且数据库未满,或者BASE ID和PN是否已经存入移动终端数据库,如果是,则 转移到 D; D.将SID、NID、BASE ID和PN写入移动终端的数据库。(String), US13/501299(String), 1282665600(Integer), US8825010B2(String), 1409587200(Integer), 1409587200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 12(Integer), CN100428820C | CN101072439A | CN101668285A | US20040048597A1 | US20060217130A1 | US20080287140A1 | US20090098873A1 | US20090129327A1 | US20090135731A1 | US20100002611A1 | US20100279705A1 | US8054803B2(String), \20230420\896cb8bebb7944029d9eab4a0f0c8b83.png(String), 14(Integer), 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 1. A cell locking method for a mobile terminal, wherein said method comprises:searching, by the mobile terminal, a current cell at a current location to acquire a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of said cell;judging, by the mobile terminal, whether said SID, said NID, said BASE ID and said PN of the current cell are already stored in a database of said mobile terminal;when said SID, said NID, said BASE ID and said PN of the current cell are all already stored in the database of said mobile terminal, setting said mobile terminal to a normal status for normal operation;when said SID, said NID and said PN are already stored in the database of said mobile terminal, but said BASE ID is not stored in the database and said database is not full, writing said BASE ID, with said SID, said NID and said PN, into the database, and setting said mobile terminal into the normal status for normal operation;when said BASE ID and said PN are already stored in the database of said mobile terminal, but said SID and said NID are not stored in the database, writing said SID and said NID, with said BASE ID and said PN, into the database, and setting said mobile terminal into the normal status for normal operation;for any other judgment results, setting said mobile terminal to a lock status for not normal operation.(String), 1.根据权利要求10所述的移动终端的小区锁定方法,其中在将移动终端设置为锁定状态时,该方法还包括:若该移动终端响应或发起业务连接,则禁止该移动终端访问或响应系统,并向系统返回指定的错误码。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 2. The cell locking method for a mobile terminal according to claim 1, wherein before the step of searching, by the mobile terminal, a current cell at a current location, the method further comprises an initialization procedure, and said initialization procedure comprises:setting a number N of limited dials;limiting a maximum number of BASE IDs simultaneously supported by the mobile terminal of a user;after the user acquiring the mobile terminal dials a (N+1)th non-emergent number, acquiring and storing, by the mobile terminal, said SID, said NID, said BASE ID and said PN in a system parameter message and a PN sequence set stored in said mobile terminal according to a current network signaling.(String), 12.根据权利要求1所述的移动终端的小区锁定方法,其中在将移动终端设置为锁定状态时,该方法还包括:若该移动终端响应或发起业务连接,则禁止该移动终端访问或响应系统,并向系统返回指定的错误码。13、一种可锁定小区的移动终端,其中所述移动终端包括当前小区参数获取单元、数据存储单元、参数比较单元、数据库写入单元和状态设置单元,其中当前小区参数获取单元,用于获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASEID)和伪随机数(PN);数据存储单元,用于存储移动终端的数据库,数据库包括SID、NID、BASEID和PN参数。参数比较单元,用于将当前小区参数获取单元获取的SID、NID、BASEID和PN与存储在所述数据存储单元中的参数通过以下方式进行比较:当当前小区的所述SID、所述NID、所述BASEID和所述PN均已存储在所述移动终端的数据库中时,向状态设置单元发送第一比较结果,当所述SID、所述NID和所述PN已经存储在所述移动终端的数据库中,但是所述BASEID未存储在数据库中且所述数据库未满时,向数据库写入单元发送第二比较结果,以及状态设置单元,当所述BASEID和所述PN已存储在所述移动终端的数据库中,但所述SID和所述NID未存储在数据库中时,向数据库写入单元和状态设置单元发送第三比较结果,以及当比较结果不满足上述任一比较结果时,向状态设置单元发送第四比较结果;数据库写入单元,用于在接收到第二比对结果时,将所述BASEID、所述SID、所述NID和所述PN写入所述数据库。当接收到第三比对结果时,将所述SID和所述NID与所述BASEID和所述PN一起写入数据库;状态设置单元,用于在接收到第一比较结果、第二比较结果或第三比较结果时,将所述移动终端设置为正常状态,进行正常工作。当接收到第四比较结果时,将所述移动终端设置为非正常操作的锁定状态。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 3. The cell locking method for a mobile terminal according to claim 2, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 14.根据权利要求13所述的移动终端,其中所述移动终端还包括解锁单元,所述解锁单元与所述数据存储单元连接,用于根据接收到的解锁指令或解锁短信清空所述数据库中的SID、NID、BASEID和PN,并重置锁定的小区配置。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 4. The cell locking method for a mobile terminal according to claim 2, wherein said PN sequence set comprises an active set, a candidate set and a neighbor set.(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 5. The cell locking method for a mobile terminal according to claim 4, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 6. The cell locking method for a mobile terminal according to claim 1, wherein after the mobile terminal is set to the lock status, the method further comprises an unlock procedure, and said unlock procedure comprises:determining, by an operator, whether identity and requirement of said user is legal according to a cell unlock request of the user;when the identity and requirement of said user is legal, sending, by the operator, an unlock instruction or unlock short message to the user terminal;after receiving said unlock instruction or said unlock short message, emptying, by the mobile terminal, the SID, NID, BASE ID and PN stored in said database and resetting locked cell configuration.(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 7. The cell locking method for a mobile terminal according to claim 6, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 8. The cell locking method for a mobile terminal according to claim 6, wherein when the cell unlock request of said user is sent to the operator by dialing a specified service number, the operator sends said unlock short message to the user terminal.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 9. The cell locking method for a mobile terminal according to claim 8, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 10. The cell locking method for a mobile terminal according to claim 6, wherein when the cell unlock request of said user is sent to the operator by sending said user terminal to the operator, the operator sends said unlock instruction to the user terminal by using a tool.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 11. The cell locking method for a mobile terminal according to claim 10, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 12. The cell locking method for a mobile terminal according to claim 1, wherein when setting the mobile terminal to the lock status, the method further comprises: if said mobile terminal responds or initiates a service connection, then forbidding said mobile terminal to access or to respond to the system and sending back a specified error code to the system.(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 13. A mobile terminal capable of locking a cell, wherein said mobile terminal comprises a current cell parameter acquisition unit, a data storage unit, a parameter comparison unit, a database writing-in unit and a status setting unit, whereinthe current cell parameter acquisition unit is used for acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell;the data storage unit is used for storing a database of the mobile terminal, wherein, the database includes SID, NID, BASE ID and PN parameters;the parameter comparison unit is used for comparing the SID, NID, BASE ID and PN acquired by the current cell parameter acquisition unit with the parameters stored in said data storage unit by the following ways:when said SID, said NID, said BASE ID and said PN of the current cell are all already stored in the database of said mobile terminal, sending a first comparison result to the status setting unit,when said SID, said NID and said PN are already stored in the database of said mobile terminal, but said BASE ID is not stored in the database and said database is not full, sending a second comparison result to the database writing-in unit and the status setting unit,when said BASE ID and said PN are already stored in the database of said mobile terminal, but said SID and said NID are not stored in the database, sending a third comparison result to the database writing-in unit and the status setting unit, andwhen the comparison result does not meet any one of the above comparison results, sending a fourth comparison result to the status setting unit;the database writing-in unit is used for: when receiving the second comparison result, writing said BASE ID, with said SID, said NID and said PN, into said database; when receiving the third comparison result, writing said SID and said NID, with said BASE ID and said PN, into the database;the status setting unit is used for: when receiving the first comparison result, the second comparison result, or the third comparison result, setting said mobile terminal to a normal status for normal operation; when receiving the fourth comparison result, setting said mobile terminal to a lock status for not normal operation.(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185941(Integer), 14. The mobile terminal according to claim 13, wherein said mobile terminal further comprises an unlock unit which is connected to said data storage unit and is used for emptying the SID, NID, BASE ID and PN in said database according to a received unlock instruction or unlock short message and resetting the locked cell configuration.(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185941(Integer), TECHNICAL FIELD [0001]The present invention relates to the technical field of wireless communication, and in particularly, to a cell locking method for a mobile terminal and a mobile terminal capable of locking a cell. BACKGROUND OF THE RELATED ART [0002]With the rapid development of the mobile communication technology, the mobile terminal also exhibits diversified development, and the requirement on limiting the mobility of the mobile terminal also appears, i.e. limit the mobile terminal to only work in a specified cell. Currently, there are two common cell locking methods for the mobile terminal. [0003]The first method is to lock the base station ID and system ID. In this method, the number of base stations which can be locked by the mobile terminal is firstly determined, each time the mobile terminal searches out a new base station, then the mobile terminal adds the base station to a base station list, and if the number of the base stations in the base station list reaches a specified number, then the mobile station stops updating the base station list; after having been registered into the base station, the terminal firstly compares to determine whether ID of this base station is already in the base station list, if it is contained in the base station list, then the terminal provides normal service, otherwise the terminal provides limited service. [0004]The second method is to establish duplex channels between the system side and the mobile terminal, in which the system side issues a control command to the mobile terminal so as to configure the subscription list of the terminal, and the mobile terminal continuously monitors the system, reports information according to the requirements, and determines whether or not to provide normal service. [0005]However, during implementation of the present invention, the inventors have found out that the above currently available cell locking methods for a mobile terminal has the following defects: first, the base station has respiratory effect, which means that, in the Code Division Multiple Access (CDMA) system, when the interference signal in a cell is very strong, the actual effective coverage area of the base station will be reduced; and when the interference signal in a cell is very weak, the actual effective coverage area of the base station will be increased. In a word, the respiratory effect exhibits that the coverage radius constricts as the number of users increases. The main reason leading to the respiratory effect is that the CDMA system is a self-interference system, where the increasing of user leads to the increasing of interference and affects the coverage. Due to the existence of respiratory effect, after the signal coverage of the base station becomes larger, the terminal located at the coverage boundary of the base station will be in the subscribed cell, but when the signal coverage of the base station becomes smaller, the terminal will be out of the coverage of the subscribed cell, then the terminal will be in a lock status, thus the service provided by the terminal is limited, and such phenomenon is called ping-pong effect. Secondly, in the abovementioned methods in the related art, although a plurality of base stations can be locked, there is no association among the locked base stations, and it is only judged whether the base station currently providing the service is in the subscribed base station list, if the current base station is not in the subscribed base station list and the number (preset in the terminal in advance) of the subscribed base stations does not reach the specified upper limit, then the base station currently providing the service is added into the subscription list and provides normal service, or the base station currently providing the service is in the subscribed base station list, then normal service will be provided; and if the current base station is not in the subscription list and the subscription list is full, then the terminal only provides limited service. Because there is no restriction relationship among the locked base stations, it leads to that these base stations may form individual islands, which conflicts with the object of locking a cell. SUMMARY OF THE INVENTION [0006]The problem to be solved by the present invention is to provide a cell locking method for a mobile terminal and a mobile terminal capable of locking a cell so as to overcome the defects of the ping-pong effect and island effect in related art. [0007]In order to reach the abovementioned object, the technical solution of the present invention provides a cell locking method for a mobile terminal, and said method includes the steps of: step A. the mobile terminal searching a cell at a current location to acquire a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of the cell; step B. judging whether said SID, said NID, said BASE ID and said PN are already stored in a database of said mobile terminal, if yes, then setting the mobile terminal to a normal status and transferring to step E, otherwise transferring to step C; step C. judging whether said SID, said NID, and said PN are already stored in the database station of said mobile terminal and said database is not full, or said BASE ID and said PN are already stored in the database of said mobile terminal, if yes, then transferring to step D, otherwise setting said mobile terminal to a lock status and transferring to step E; step D. writing said SID, said NID, said BASE ID and said PN into the database of said mobile terminal and setting said mobile terminal into a normal status and transferring to step E; and step E. finishing the lock procedure. [0008]Furthermore, before step A, the method further includes an initialization procedure, and said initialization procedure includes: setting the number N of limited dials; limiting the maximum number of BASE ID simultaneously supported by a user terminal; said user terminal, after a user acquiring the user terminal dials a (N+1)th non-emergent number, acquiring and storing said SID, said NID, said BASE ID and said PN in a system parameter message and a PN sequence set stored in said user terminal according to a current network signaling. [0009]Furthermore, said PN sequence set includes an active set, a candidate set and a neighbor set. [0010]Furthermore, after the mobile terminal is set into the lock status, the method further includes an unlock procedure F, and said F includes: step F1. an operator determining whether identity and requirement of said user is legal according to a cell unlock request of the user, if yes, then transferring to step F2, otherwise ending; step F2. the operator sending an unlock instruction or unlock short message to the user terminal; step F3. after receiving said unlock instruction or said unlock short message, the user terminal emptying the SID, NID, BASE ID and PN stored in said database and resetting locked cell configuration. [0011]Furthermore, when the cell unlock request of said user is sent to the operator by dialing a specified service number, the operator sends said unlock short message to the user terminal. [0012]Furthermore, when the cell unlock request of said user is sent to the operator by sending said user terminal to the operator, the operator sends said unlock instruction to the user terminal by using a tool. [0013]Furthermore, when setting the mobile terminal to the lock status, the method further comprises: if said user terminal responds or initiates a service connection, then forbidding said user terminal to access or to respond to the system and sending back a specified error code to the system. [0014]The technical solution of the present invention also provides a mobile terminal capable of locking a cell, and said mobile terminal includes a current cell parameter acquisition unit, a data storage unit, a parameter comparison unit, a database writing-in unit and a status setting unit; wherein [0015]the current cell parameter acquisition unit is used for acquiring a system identification (SID), a network identification (NID), a base station identifier (BASE ID) and a pseudo-random number (PN) of a current cell; the parameter comparison unit is used for comparing the parameter acquired by the parameter acquiring unit of said current cell with a parameter stored in said data storage unit; the database writing-in unit is used for writing data into said database according to the comparison result of said parameter comparison unit; and the status setting unit is used for setting the status of said mobile terminal according to the comparison result of said parameter comparison unit. [0016]Furthermore, said database writing unit is further used for writing said SID, said NID, said BASE ID and said PN into the database of said mobile terminal when said comparison result is that said SID, said NID and said PN acquired by the current cell parameter acquisition unit are the same as the SID, NID and PN stored in said database and said database is not full, or when said BASE ID and said PN acquired by the current cell parameter acquisition unit are the same as the BASE ID and PN stored in said database. [0017]Furthermore, said status setting unit is further used for setting said mobile terminal into the normal status when said comparison result is that said SID, said NID, said BASE ID and said PN acquired by the current cell parameter acquisition unit are the same as the SID, NID, BASE ID and PN stored in said database, or when said SID, said NID and said PN acquired by the current cell parameter acquisition unit are the same as the SID, NID and PN stored in said database and said database is not full, or when said BASE ID and said PN acquired by the current cell parameter acquisition unit are the same as the BASE ID and PN stored in said database, otherwise setting said mobile terminal into the lock status. [0018]Furthermore, said mobile terminal further includes an unlock unit which is connected to said data storage unit and is used for emptying the SID, NID, BASE ID and PN in said database according to a received unlock instruction or unlock short message and reset locked cell configuration The beneficial effects of the present invention compared with related art are as follows: [0019]by the present invention, the operating costs is reduced without adding or modifying the configuration of the network side; in addition, by the present invention, a certain cell can be strictly locked, which solves the ping-pong effect generated by spasmodically locking a certain cell at some special locations by the terminal due to the network respiratory effect, and also will not lead to island effect. BRIEF DESCRIPTION OF DRAWINGS [0020]FIG. 1 is a flowchart of a cell locking method for a mobile terminal in an example of the present invention. [0021]FIG. 2 is a flowchart of an initialization procedure in an example of the present invention. [0022]FIG. 3 is a flowchart of unlock of an example of the present invention. [0023]FIG. 4 is a flowchart of a mobile terminal responding to a system after locking a cell using the present invention. [0024]FIG. 5 is a flowchart of a mobile terminal accessing a system after locking a cell using the present invention. [0025]FIG. 6 is a schematic diagram of a mobile terminal capable of locking a cell in an example of the present invention. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0026]Hereinafter, the particular embodiments of the present invention will be further described in detail in conjunction with the accompanying drawings and examples. The following examples are used for describing the present invention, but not for limiting the scope of the present invention. [0027]In the examples of the present invention, the cells in a CDMA network are defined as a set P of several {SID, NID, BASE ID, PN}, and it can be known from the network characteristics that all the SIDs and NIDs are the same in the same cell, a set B of the BASE ID is the base station registered by the current terminal and the neighbor base station, and the BASE ID of the current base station can be acquired from a system parameter message sent by the base station; and the PN set of the cell where the terminal is located is S. Such a cell structure is for adapting to the respiratory effect of the CDMA network, and avoiding the ping-pong effect caused by the respiratory effect, and at the same time it also can avoid the island effect caused by only locking the BASE ID in the conventional cell locking solution. In this case, said SID is the abbreviation of system identification which indicates the System ID; said NID is the abbreviation of network identification which indicates the network ID; said BASE ID indicates the base station ID; and said PN is the abbreviation of pseudo-random number which indicates pseudo-random code. Example 1 [0028]A cell locking method for a mobile terminal in the example of the present invention is as shown in FIG. 1 and includes the steps as follows. [0029]Step s101. The mobile terminal searches a cell at a current location, and the mobile terminal, when receiving a system parameter message, reads Pj={SIDj, NIDj, BASE IDj, PNj} from the system parameter message. [0030]Step s102. It is judged whether Pj belongs to P; if yes, then transfer to step s107, otherwise transfer to step s103. [0031]Step s103. It is judged whether SIDj=SID, NIDj=NID, PNjεS, BASE IDj!εB, and the number of elements in B is less than the maximum number M of the BASE ID simultaneously supported by the user terminal, if yes, then transfer to step s104, otherwise transfer to step s105. [0032]Step s104. Pj is added to the set P, i.e. P+={Pj}; BASE IDj is added to set B, i.e. B+={BASE IDj}; B and P are stored, and transfer to step s107. [0033]Step s105. It is judged whether BASE IDjεB, PNjεS, and Pj!εP, if yes, then transfer to step s106, otherwise transfer to step s108. [0034]Step s106. Pj is added to set P, i.e. P+={Pj}, then P is stored and transfer to step s107. [0035]Step s107. The mobile terminal is set to a normal status and transfer to step s109. [0036]Step s108. The mobile terminal is set to a lock status and transfer to step s109. [0037]Step s109. The lock procedure is ended. Example 2 [0038]Before example 1, the present invention further includes an initialization procedure, and the flow of the initialization procedure in the example of the present invention is as shown in FIG. 2 and includes the following steps. [0039]Step s201, the number of limited dials N which is 5 in this example is set. [0040]Step s202, the user, after having acquired the user terminal, dials the telephone. [0041]Step s203, it is judged whether the number of times of non-emergent number dialed by the user is greater than N; if yes, then transfer to step s204, otherwise transfer to step s202. [0042]Step s204, the user terminal acquires Pi={SID, NID, BASE ID, PN} in the system parameter message sent by the current base station and the PN set S maintained by the terminal, wherein the PN sequence set S includes an active set, a candidate set and a neighbor set. [0043]Step s205, the user terminal initializes the set P={Pi}, B={BASE ID}, and automatically stores S, P, B, SID and NID. Example 3 [0044]When the mobile terminal is in the lock status, the user can alter the subscribed cell by way of an unlock procedure, and an unlock procedure in the example of the present invention is as shown in FIG. 3, which includes the steps as follows. [0045]Step s301, the user requests a cell unlock. [0046]Herein, the user can request cell unlock toward the operator by two manners, among which one manner is to send the request to the operator by dialing a specified service number, another manner is to send the user terminal to the operator. [0047]Step s302, the operator determines whether the identity and the requirement of the user is legal according to the cell unlock request of the user, if yes, then transfer to step s303, otherwise end. [0048]Step s303, when the cell unlock request of the user is sent to the operator by dialing a specified service number, the operator sends an unlock short message to the user terminal; and when the cell unlock request of the user is sent to the operator by sending the user terminal thereto, the operator sends an unlock instruction to the user terminal by using a tool. [0049]Step s304, after having received the unlock instruction or unlock short message, the user terminal empties the SID, NID, BASE ID and PN in the database and resets the locked cell configuration. [0050]After having reset the locked cell configuration, the user terminal restarts the cell locking procedure. [0051]Herein, after the mobile terminal locks a cell using the present invention, its procedure of responding to the system is as shown in FIG. 4, and its procedure of accessing the system is as shown in FIG. 5. When the mobile terminal responds or initiates a service connection, the status of the current mobile terminal will be first checked. If the mobile terminal is in the normal status, then the terminal normally accesses or responds to the system. If the mobile terminal is in the lock status, then it is checked whether the user alters the subscribed cell by way of unlock procedures such as an Over The Air Parameter Administration (OTAPA), an unlock short message or dialing a specified number, etc., if yes, then unlock is performed and the normally access or responding to the system is performed, otherwise, a specified error code is sent back to the system and the access or respond to the system is forbidden. [0052]The schematic diagram of a mobile terminal capable of locking a cell in the example of the present invention is as shown in FIG. 6, in which the mobile terminal includes a current cell parameter acquisition unit 61, a parameter comparison unit 62, a status setting unit 63, a database writing-in unit 64, a data storage unit 65 and an unlock unit 66. Among them, the parameter comparison unit 62 is respectively connected to the current parameter acquisition unit 61, status setting unit 63, database writing-in unit 64 and data storage unit 65; and the data storage unit 65 is respectively connected to the database writing-in unit 64 and unlock unit 66. [0053]The current cell parameter acquisition unit 61 is used for acquiring the SID, NID, BASE ID and PN of the current cell. [0054]The data storage unit 65 is used for storing the database of the mobile terminal, wherein, the database includes the SID, NID, BASE ID and PN parameters in the database. [0055]The parameter comparison unit 62 is used for comparing the parameter acquired by parameter acquiring unit 61 of the current cell with the parameter stored in data storage unit 65. [0056]The database station writing-in unit 64 is used for writing data into the database according to the comparison result of the parameter comparison unit 62; writing the SID, NID, BASE ID and PN into the database of the mobile terminal when the comparison result is that the SID, NID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID and PN stored in the database and the database is not full, or when the BASE ID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, the BASE ID and PN stored in the database. [0057]The status setting unit 63 is used for setting the status of the mobile terminal according to the comparison result of parameter comparison unit 62; setting the mobile terminal into a normal status when the comparison result is that the SID, NID, BASE ID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID, BASE ID and PN stored in the database, or when the SID, NID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID and PN stored in the database and the database is not full, or when the BASE ID and PN acquired by parameter acquiring unit 61 of the current cell are the same as the SID, NID and PN stored in PN database, otherwise, setting the mobile terminal to a lock status. [0058]The unlock unit 66 is used for emptying the SID, NID, BASE ID and PN in the database and resetting the locked cell configuration according to the received unlock instruction or unlock short message. [0059]When using the present invention, the operating costs can be reduced without adding or modifying the configuration of the network side; and the present invention can strictly lock a certain cell, which solves the ping-pong effect generated by spasmodically locking a certain cell at some special location by the terminal due to the network respiratory effect, and also will not lead to island effect. [0060]What is described above is merely preferred embodiments of the present invention, and it should be pointed out that several improvements and modifications can also be made without departing from the technical principle of the present invention for those skilled in the art, and these improvements and modifications should also be regarded as the scope of protection of the present invention.(String), 技术领域 [0001] 本发明涉及无线通信技术领域,尤其涉及一种移动终端的小区锁定方法和能够锁定小区的移动终端。 背景技术 [0002] 随着移动通信技术的飞速发展,移动终端也呈现多元化发展,也出现了限制移动终端移动性的要求,即限制移动终端只能工作在特定小区。 目前,移动终端常用的小区锁定方式有两种。 [0003] 第一种方法是锁定基站ID和系统ID。 该方法首先确定移动终端可以锁定的基站数量,每次移动终端搜索到新的基站,移动终端将该基站添加到基站列表中,如果 基站列表中的基站数量达到指定数量,则移动台停止更新基站列表。 终端注册到基站后,首先比较判断该基站的ID是否已经在基站列表中,如果在基站列表中,则终端提供正常服务,否则终端提供 有限的服务。 [0004] 第二种方法是在系统侧和移动终端之间建立双工信道,系统侧向移动终端下发控制命令,配置终端的订阅列表,移动终端持续监控系统, 根据要求上报信息,确定是否提供正常服务。 [0005] 但是,发明人在实施本发明的过程中发现,上述现有的移动终端小区锁定方法存在以下缺陷:首先,基站具有呼吸效应,也就是说,在码分多址中, (CDMA)系统,当小区内的干扰信号很强时,基站的实际有效覆盖范围会缩小; 当小区内的干扰信号很弱时,会增加基站的实际有效覆盖范围。 总之,呼吸效应表现为覆盖半径随着用户数量的增加而缩小。 导致呼吸效应的主要原因是CDMA系统是一个自干扰系统,用户的增加导致干扰的增加,影响覆盖。 由于呼吸效应的存在,当基站的信号覆盖范围变大后,位于基站覆盖边界的终端会在签约小区内,但当基站的信号覆盖范围变小时, 终端将超出订阅小区的覆盖范围,终端将处于锁定状态,从而终端提供的服务受到限制,这种现象称为乒乓效应。 其次,在上述相关技术的方法中,虽然可以锁定多个基站,但是锁定的基站之间没有关联,仅判断当前提供服务的基站是否在签约基站中。 列表,如果当前基站不在订阅基站列表中,且订阅基站数量(终端预先设置)未达到指定上限,则将当前提供服务的基站加入 订阅列表并提供正常服务,或当前提供服务的基站在订阅基站列表中,则提供正常服务; 如果当前基站不在订阅列表中且订阅列表已满,则终端仅提供有限服务。 由于锁定的基站之间没有限制关系,导致这些基站可能形成单独的孤岛,这与锁定小区的目的相冲突。 发明内容 [0006]本发明要解决的问题是提供一种移动终端的小区锁定方法及能够锁定小区的移动终端,以克服相关技术中存在的乒乓效应和孤岛效应的缺陷。 [0007] 为了达到上述目的,本发明的技术方案提供了一种移动终端的小区锁定方法,该方法包括以下步骤: 步骤A、移动终端搜索当前位置的小区以获取系统 小区标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN); 步骤B、判断所述SID、所述NID、所述BASE ID和所述PN是否已经存储在所述移动终端的数据库中,如果是,则将移动终端设置为正常状态并转至步骤E,否则转至步骤 C; 步骤C.判断所述SID、所述NID和所述PN是否已经存储在所述移动终端的数据库站中并且所述数据库未满,或者所述BASE ID和所述PN已经存储在所述移动终端的数据库中, 如果是,则转入步骤D,否则将所述移动终端设置为锁定状态,转入步骤E。 步骤D、将所述SID、所述NID、所述BASE ID和所述PN写入所述移动终端的数据库中,并将所述移动终端设置为正常状态,转入步骤E。 步骤E,完成锁定程序。 [0008] 进一步地,在步骤A之前,该方法还包括初始化过程,所述初始化过程包括: 设置受限拨号数N; 限制用户终端同时支持的BASE ID的最大数量; 所述用户终端,在用户获取用户终端拨打第(N+1)个非紧急号码后,获取并存储所述SID、所述NID、所述BASE ID和所述PN在系统参数消息和存储的PN序列集合中 在所述用户终端中根据当前网络信令。 [0009] 进一步地,所述PN序列集包括激活集、候选集和邻居集。 [0010] 进一步地,在移动终端进入锁定状态后,该方法还包括解锁流程F,所述F包括: 步骤F 1 . 运营商根据用户的小区解锁请求判断所述用户的身份和要求是否合法,如果是,则转入步骤F 2 , 否则结束; 步骤 F 2 . 运营商向用户终端发送解锁指令或解锁短信; 步骤 F 3 . 用户终端接收到所述解锁指令或所述解锁短信后,清空所述数据库中存储的SID、NID、BASE ID和PN,并重置锁定小区配置。 [0011] 进一步地,当所述用户的小区解锁请求通过拨打指定的业务号码发送给运营商时,运营商向用户终端发送所述解锁短信。 [0012] 进一步地,当通过向运营商发送所述用户终端向运营商发送所述用户的小区解锁请求时,运营商通过工具向用户终端发送所述解锁指令。 [0013] 进一步地,在将移动终端设置为锁定状态时,该方法还包括:若所述用户终端响应或发起业务连接,则禁止所述用户终端访问或响应系统,并返回指定的错误码给所述用户终端。 系统。 [0014] 本发明的技术方案还提供了一种能够锁定小区的移动终端,所述移动终端包括当前小区参数获取单元、数据存储单元、参数比较单元、数据库写入单元和状态设置。 单元; 其中 [0015]当前小区参数获取单元,用于获取当前小区的系统标识(SID)、网络标识(NID)、基站标识(BASE ID)和伪随机数(PN)。 参数比较单元,用于将所述当前小区的参数获取单元获取的参数与所述数据存储单元中存储的参数进行比较。 数据库写入单元,用于根据所述参数比较单元的比较结果将数据写入所述数据库; 状态设置单元,用于根据所述参数比较单元的比较结果设置所述移动终端的状态。 [0016] 进一步地,所述数据库写入单元还用于当所述比对结果为当前小区参数获取的所述SID、所述NID和所述PN时,将所述SID、所述NID、所述BASE ID和所述PN写入所述移动终端的数据库中。 获取单元与所述数据库中存储的SID、NID和PN相同且所述数据库未满,或者当当前小区参数获取单元获取的所述BASE ID和所述PN与存储在其中的BASE ID和PN相同时 说数据库。 [0017] 进一步地,所述状态设置单元还用于当所述比较结果为所述当前小区参数获取单元获取的所述SID、所述NID、所述BASE ID和所述PN与SID相同时,将所述移动终端设置为正常状态。 ,所述数据库中存储的NID、BASE ID和PN,或者当所述SID时,当前小区参数获取单元获取的所述NID和所述PN与所述数据库中存储的SID、NID和PN相同且所述数据库未满 ,或者当当前小区参数获取单元获取的所述BASE ID和所述PN与所述数据库中存储的BASE ID和PN相同时,否则将所述移动终端设置为锁定状态。 [0018] 进一步地,所述移动终端还包括解锁单元,与所述数据存储单元连接,用于根据接收到的解锁指令或解锁短信清空所述数据库中的SID、NID、BASE ID和PN,并重置锁定小区配置。 本发明与现有技术相比的有益效果如下: [0019] 通过本发明,在不增加或修改网络侧配置的情况下,降低了运营成本。 另外,通过本发明,可以对某个小区进行严格锁定,解决了终端由于网络呼吸效应在某些特殊位置痉挛锁定某个小区产生的乒乓效应,也不会导致 孤岛效应。 附图说明 [0020] 图1为本发明实施例中移动终端的小区锁定方法的流程图。 [0021] 图2是本发明示例中的初始化过程的流程图。 [0022] 图3为本发明实施例解锁流程图。 [0023] 图4是使用本发明的移动终端在锁定小区后响应系统的流程图。 [0024] 图5为本发明移动终端锁定小区后接入系统的流程图。 [0025] 图6为本发明实施例移动终端可锁定小区的示意图。 本发明的优选实施方案 [0026] 下面结合附图和实施例对本发明的具体实施方式作进一步的详细说明。 以下实施例用于描述本发明,但不用于限制本发明的范围。 [0027]在本发明实施例中,将CDMA网络中的小区定义为若干个{SID, NID, BASE ID, PN}的集合P,从网络特性可知,所有的SID和NID都是 同一个小区,BASE ID的集合B为当前终端和邻居基站注册的基站,当前基站的BASE ID可以从基站发送的系统参数消息中获取 ; 终端所在小区的PN集合为S。这样的小区结构是为了适应CDMA网络的呼吸效应,避免呼吸效应引起的乒乓效应,同时 也可以避免传统小区锁定方案中只锁定BASE ID所带来的孤岛效应。 在这种情况下,SID是系统标识的缩写,表示系统ID; 所述NID是网络标识的缩写,表示网络ID; 所述BASE ID表示基站ID; 所述PN为pseudo-random number的缩写,表示伪随机码。 示例 1 [0028] 本发明实施例的移动终端的小区锁定方法如图1所示,包括以下步骤。 [0029] 脚步 101 . 移动终端搜索当前位置的小区,移动终端在接收到系统参数消息时,从系统参数消息中读取Pj={SIDj,NIDj,BASE IDj,PNj}。 [0030] 脚步 102 . 判断Pj是否属于P; 如果是,则转移到步骤s 107 , 否则转到步骤 s 103 . [0031] 脚步 103 . 判断是否SIDj=SID,NIDj=NID,PNjεS,BASE IDj!εB,且B中的元素个数小于用户终端同时支持的BASE ID的最大个数M,如果是,则转入 脚步 104 , 否则转到步骤 s 105 . [0032] 脚步 104 . Pj被添加到集合P中,即P+={Pj}; BASE IDj 添加到集合 B,即 B+={BASE IDj}; B和P被存储,并转移到步骤s 107 . [0033] 脚步 105 . 判断是否有BASE IDjεB、PNjεS、Pj!εP,如果是,则转步骤s 106 , 否则转到步骤 s 108 . [0034] 脚步 106 . 将 Pj 添加到集合 P,即 P+={Pj},然后将 P 存储并转移到步骤 s 107 . [0035] 脚步 107 . 移动终端设置为正常状态,转步骤s 109 . [0036] 脚步 108 . 移动终端设置为锁定状态,转步骤s 109 . [0037] 脚步 109 . 锁定过程结束。 示例 2 [0038] 在实施例一之前,本发明还包括初始化流程,本发明实施例中的初始化流程流程如图2所示,包括以下步骤。 [0039] 脚步 201 ,在本例中设定为5的限定拨号数N。 [0040] 脚步 202 ,用户在获得用户终端后拨打电话。 [0041] 脚步 203 ,判断用户拨打非紧急号码的次数是否大于N; 如果是,则转移到步骤s 204 , 否则转到步骤 s 202 . [0042] 脚步 204 ,用户终端获取当前基站发送的系统参数消息中的Pi={SID, NID, BASE ID, PN}和终端维护的PN集合S,其中PN序列集合S包括激活集,a 候选集和邻居集。 [0043] 脚步 205 ,用户终端初始化集合P={Pi},B={BASE ID},并自动存储S、P、B、SID和NID。 示例 3 [0044] 当移动终端处于锁定状态时,用户可以通过解锁流程改变订阅小区,本发明实施例的解锁流程如图3所示,包括如下步骤。 [0045] 脚步 301 ,用户请求小区解锁。 [0046]这里,用户可以通过两种方式向运营商请求小区解锁,其中一种方式是通过拨打指定的服务号码向运营商发送请求,另一种方式是将用户终端发送给运营商。 [0047] 脚步 302 ,运营商根据用户的小区解锁请求判断用户的身份和要求是否合法,如果是,则转步骤s 303 ,否则结束。 [0048] 脚步 303 ,当用户通过拨打指定业务号码向运营商发送小区解锁请求时,运营商向用户终端发送解锁短信; 当通过用户终端向运营商发送用户的小区解锁请求给运营商时,运营商通过工具向用户终端发送解锁指令。 [0049] 脚步 304 ,用户终端收到解锁指令或解锁短信后,清空数据库中的SID、NID、BASE ID和PN,并重新设置锁定小区配置。 [0050] 在重置锁定小区配置后,用户终端重新启动小区锁定过程。 [0051] 这里,移动终端使用本发明锁定小区后,其响应系统的流程如图4所示,其接入系统的流程如图5所示。当移动终端响应或发起一个 服务连接,首先检查当前移动终端的状态。 如果移动终端处于正常状态,则终端正常访问或响应系统。 如果移动终端处于锁定状态,则检查用户是否通过空中参数管理(OTAPA)、解锁短消息或拨打指定号码等解锁程序改变订阅小区。 ,如果是,则解锁,正常访问或响应系统,否则返回指定的错误码,禁止访问或响应系统。 [0052] 本发明实施例的可锁定小区的移动终端示意图如图6所示,该移动终端包括当前小区参数获取单元 61 , 参数比较单元 62 ,一个状态设置单元 63 , 数据库写入单元 64 , 一个数据存储单元 65 和一个解锁单元 66 . 其中,参数比较单元 62 分别连接到当前参数采集单元 61 , 状态设置单元 63 , 数据库写入单元 64 和数据存储单元 65 ; 和数据存储单元 65 分别连接到数据库写入单元 64 并解锁单元 66 . [0053] 当前小区参数获取单元 61 用于获取当前小区的SID、NID、BASE ID和PN。 [0054] 数据存储单元 65 用于存储移动终端的数据库,其中,数据库包括数据库中的SID、NID、BASE ID和PN参数。 [0055] 参数比较单元 62 用于比较参数获取单元获取的参数 61 当前单元格的参数与存储在数据存储单元中的参数 65 . [0056] 数据库站写入单元 64 用于根据参数比较单元的比较结果将数据写入数据库 62 ; 当比对结果为参数获取单元获取的SID、NID和PN时,将SID、NID、BASE ID和PN写入移动终端的数据库 61 当前小区的SID、NID、PN与数据库中存储的SID、NID、PN相同且数据库未满,或参数获取单元获取的BASE ID、PN时 61 当前单元格的名称与存储在数据库中的 SID、BASE ID 和 PN 相同。 [0057] 状态设定单元 63 用于根据参数比较单元的比较结果设置移动终端的状态 62; 当比对结果为参数获取单元获取的SID、NID、BASE ID和PN时,将移动终端设置为正常状态 61 当前小区的SID、NID、BASE ID、PN与数据库中存储的SID、NID、BASE ID、PN相同,或者参数获取单元获取的SID、NID、PN时 61 当前小区的SID、NID、PN与数据库中存储的SID、NID、PN相同且数据库未满,或参数获取单元获取的BASE ID、PN时 61 与存储在PN数据库中的SID、NID和PN相同,否则将移动终端设置为锁定状态。 [0058] 解锁单元 66 用于根据接收到的解锁指令或解锁短信清空数据库中的SID、NID、BASE ID和PN,并重置锁定小区配置。 [0059] 使用本发明,无需增加或修改网络侧的配置,即可降低运营成本; 本发明可以严格锁定某个小区,解决了由于网络呼吸效应,终端在某个特殊位置痉挛性锁定某个小区产生的乒乓效应,也不会导致孤岛效应。 [0060] 以上所述仅为本发明的较佳实施例而已,需要指出的是,对于本领域的技术人员来说,在不脱离本发明的技术原理的情况下,还可以进行若干改进和变型,这些改进和变型 也应视为本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: BR112012009106A2(String), CN101668285A(String), CN101668285B(String), EP2472924A1(String), EP2472924A4(String), EP2472924B1(String), ES2505246T3(String), US20120202463A1(String), US8825010B2(String), WO2011047577A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: BR112012009106A2(String), CN101668285A(String), CN101668285B(String), EP2472924A1(String), EP2472924A4(String), EP2472924B1(String), ES2505246T3(String), US20120202463A1(String), US8825010B2(String), WO2011047577A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8825010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), BR112012009106A2(String), CN101668285A(String), CN101668285B(String), EP2472924A1(String), EP2472924A4(String), EP2472924B1(String), ES2505246T3(String), US20120202463A1(String), US8825010B2(String), WO2011047577A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), BR112012009106A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), CN101668285A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), CN101668285B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), EP2472924A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), EP2472924A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.953 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), EP2472924B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:46.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), ES2505246T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), US20120202463A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), US8825010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271648(Integer), WO2011047577A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8825010B2(String), US8825010B2(String), 1409587200(Integer), 271648(Integer), 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.162 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.162 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185941(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185941(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185941(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185941(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.471 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.471 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185941(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.731 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:47.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20110258451A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for updating mobile terminal software and mobile terminal(String), 移动终端软件更新方法及移动终端(String), US20110258451A1(String), Disclosed are a method for updating mobile terminal software and a mobile terminal. The method comprises the following steps: the mobile terminal software and/or the tool software used for updating the mobile terminal software perform hand-shaking according to encrypted hand-shaking data sent by the other party; wherein in the case that said hand-shaking is successful, the mobile terminal software or the tool software carries out verification of new mobile terminal software according to the pre-encrypted feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software, and determines whether the update is allowable according to the verification result. By introducing the two authentications of both the handshaking data and of the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by a software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the prior art in preventing such unlocking and language modification, ensures to the largest extend the terminal security, and effectively protects the interests of providers.(String), 本发明公开了一种移动终端软件更新方法及移动终端。 该方法包括以下步骤:移动终端软件和/或用于更新移动终端软件的工具软件根据对方发送的加密握手数据进行握手。 其中,在所述握手成功的情况下,移动终端软件或工具软件根据预先加密的移动终端软件的特征标识和新移动终端的特征标识,对新的移动终端软件进行验证。 软件,并根据验证结果判断是否允许更新。 本发明通过引入握手数据和特征标识的两种认证,极大地消除了终端被软件修改的可能性,避免了相关技术中终端解锁和语言修改,克服了现有技术的不足。 防止此类解锁和语言修改,最大限度地保证终端安全,有效保护提供商的利益。(String), US13/141202(String), 1250006400(Integer), US20110258451A1(String), 1319040000(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 10(Integer), US20030172090A1 | US20080233947A1 | US5418837A | US5887254A | US6029065A | US6091765A | US6223290B1 | US6449476B1 | US6859650B1 | US7031665B1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185942(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7b2fdb9257b94aa39c66a71d162ecea0.png(String), 185942(Integer), 7b2fdb9257b94aa39c66a71d162ecea0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for updating mobile terminal software and mobile terminal(String), 移动终端软件更新方法及移动终端(String), US20110258451A1(String), Disclosed are a method for updating mobile terminal software and a mobile terminal. The method comprises the following steps: the mobile terminal software and/or the tool software used for updating the mobile terminal software perform hand-shaking according to encrypted hand-shaking data sent by the other party; wherein in the case that said hand-shaking is successful, the mobile terminal software or the tool software carries out verification of new mobile terminal software according to the pre-encrypted feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software, and determines whether the update is allowable according to the verification result. By introducing the two authentications of both the handshaking data and of the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by a software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the prior art in preventing such unlocking and language modification, ensures to the largest extend the terminal security, and effectively protects the interests of providers.(String), 本发明公开了一种移动终端软件更新方法及移动终端。 该方法包括以下步骤:移动终端软件和/或用于更新移动终端软件的工具软件根据对方发送的加密握手数据进行握手。 其中,在所述握手成功的情况下,移动终端软件或工具软件根据预先加密的移动终端软件的特征标识和新移动终端的特征标识,对新的移动终端软件进行验证。 软件,并根据验证结果判断是否允许更新。 本发明通过引入握手数据和特征标识的两种认证,极大地消除了终端被软件修改的可能性,避免了相关技术中终端解锁和语言修改,克服了现有技术的不足。 防止此类解锁和语言修改,最大限度地保证终端安全,有效保护提供商的利益。(String), US13/141202(String), 1250006400(Integer), US20110258451A1(String), 1319040000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 10(Integer), US20030172090A1 | US20080233947A1 | US5418837A | US5887254A | US6029065A | US6091765A | US6223290B1 | US6449476B1 | US6859650B1 | US7031665B1(String), \20230420\7b2fdb9257b94aa39c66a71d162ecea0.png(String), 16(Integer), 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 1. A method for updating mobile terminal software, comprising:mobile terminal software and/or tool software used for updating the mobile terminal software performing hand-shaking according to encrypted hand-shaking data sent by the other party; andif the hand-shaking is successful, the mobile terminal software or the tool software carrying out verification of new mobile terminal software according to a pre-encrypted feature identifier of the mobile terminal software and a feature identifier of the new mobile terminal software, and determining whether the update is allowable according to the verification result.(String), 1.根据权利要求2所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 2. The method for updating mobile terminal software according to claim 1, wherein the hand-shaking comprises:one party of the mobile terminal software and/or the tool software decrypting the encrypted hand-shaking data from the other party, and determining whether the decrypted hand-shaking data is identical to preset hand-shaking data; andif the determining result is yes, the mobile terminal software determining that the hand-shaking is successful, otherwise, the mobile terminal software determining that the hand-shaking is failed.(String), 12.根据权利要求3所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 3. The method for updating mobile terminal software according to claim 2, wherein in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises:the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the encrypted hand-shaking data from the tool software; andthe mobile terminal software decrypting the encrypted hand-shaking data from the tool software, and comparing the decrypted hand-shaking data with the preset hand-shaking data.(String), 13.根据权利要求4所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 4. The method for updating mobile terminal software according to claim 2, wherein in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises:the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the specific parameters served as the hand-shaking data encrypted and sent by the tool software; andthe mobile terminal software decrypting the encrypted hand-shaking data from the tool software to obtain the specific parameters, performing the calculation on the specific parameters according to the preset algorithm, and comparing the calculated result of the specific parameters with the preset hand-shaking data.(String), 14.根据权利要求5所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 5. The method for updating mobile terminal software according to claim 1, wherein the processing for verifying the new mobile terminal software by the mobile terminal software or the tool software comprises:the mobile terminal software or the tool software decrypting the pre-encrypted feature identifier of the mobile terminal software;the mobile terminal software or the tool software comparing the decrypted feature identifier of the mobile terminal software with the feature identifier of the new mobile terminal software;if the feature identifier of the mobile terminal software is identical to the feature identifier of the new mobile terminal software, determining that the new mobile terminal software passes the verification; andif the feature identifier of the mobile terminal software is different from the feature identifier of the new mobile terminal software, determining that the new mobile terminal software does not pass the verification.(String), 15.根据权利要求6所述的移动终端软件更新方法,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 6. The method for updating mobile terminal software according to claim 5, wherein the processing for determining whether the update is allowable according to the verification result comprises:if the new mobile terminal software passes the verification, the tool software updating the mobile terminal software by using the new mobile terminal software; andif the new mobile terminal software does not pass the verification, stopping the update processing.(String), 16.根据权利要求9所述的移动终端,其中移动终端软件的特征标识和新移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 7. The method for updating mobile terminal software according to claim 1, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 8. A mobile terminal, comprising:a hand-shaking data module, configured to generate hand-shaking data, determine whether the hand-shaking between mobile terminal software and tool software is successful according to hand-shaking data from the tool software and the generated hand-shaking data, and return the determination result to the tool software;a feature identifier module, configured to store the encrypted preset feature identifier which is used for the mobile terminal software or the tool software to carry out the verification of the new mobile terminal software for updating the mobile terminal software;an encryption module, configured to encrypt the hand-shaking data generated by the hand-shaking data module and the unencrypted feature identifier; anda communication command module, configured to send the hand-shaking data encrypted by the encryption module to the tool software, and receive the encrypted hand-shaking data from the tool software.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 9. The mobile terminal according to claim 8, wherein the hand-shaking data module is configured to compare the hand-shaking data from the tool software with the generated hand-shaking data, determine the hand-shaking is successful if the hand-shaking data from the tool software is identical to the generated hand-shaking data, and determine the hand-shaking is failed if the hand-shaking data from the tool software is different from the generated hand-shaking data.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 10. The mobile terminal according to claim 8, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 11. The method for updating mobile terminal software according to claim 2, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 12. The method for updating mobile terminal software according to claim 3, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 13. The method for updating mobile terminal software according to claim 4, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 12(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 14. The method for updating mobile terminal software according to claim 5, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 13(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 15. The method for updating mobile terminal software according to claim 6, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 14(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185942(Integer), 16. The mobile terminal according to claim 9, wherein the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier.(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185942(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, and more particularly, to a method for updating mobile terminal software and a mobile terminal. BACKGROUND OF THE INVENTION [0002]At present, along with the rapid development of global mobile communication market, the competitions among various operators are also intense. Especially in the terminal product market, operators release various series of promotion policies one after another to attract users, and sell terminals to users with great preferential benefit; and some operators even give terminals to users for free. [0003]However, considering of theirs own benefits, operators generally adopt a series of restrictive measures. The common restrictive manner is to restrict a terminal, so that the terminal can only be used in the network of the operator giving the user with preferential benefit, or it is required to insert a specified card to enable the terminal into the usable state. Such restrictive manner is usually called as network-locking or card-locking. [0004]Though operators can restrict the usage of their terminals, it is still possible that the terminals of network-locking or card-locking may be modified by some lawbreakers via some methods, so that the modified terminals lose the function of network-locking or card-locking, which releases the restriction of operators and makes the terminals capable of being used by other operators or other networks; or makes the terminals used by inserting cards apart from the specified card, and it is even possible to change the interface of the terminal to other languages and further causes the changed terminal to be used in the network of the operators with other languages, which obviously damages the benefits of operators seriously. [0005]Therefore, an important issue is how to prevent network-locking and card-locking terminal from being changed to an unlocked terminal by software (i.e. avoiding the unlocking), and to prevent language A of terminals from being changed to language B by software (i.e. avoid modification of language), so as to protect the benefits of operators. [0006]At present, there are a few methods provided in the mobile terminal field, for preventing the software of the mobile terminal device from being modified illegally, wherein one method is to record the value stored in PAF-ROM and necessary data such as international mobile equipment identity (IMEI) simultaneously in a memory area that can only be programmed once, and with such values as the basic data, a comparison is made to determine whether it is abnormal changed software, when being changed by the software, so as to determine whether the software is illegally changed. The problem of the above method is that a portion of the terminal must be divided as a memory that can only be programmed once, or a programmable read only memory (PROM) chip must be added independently, so that the cost of implementation is high; moreover, the determination of the above method is focused on the changed result, and it is necessary to prevent the changed terminal from being used continuously after determining that the software of terminal is illegally changed, which has lag and is unable to prevent the terminal from being changed by software in fact. [0007]There is no effective solution provided in the related art to solve the problem that it is impossible for preventing the terminal from being changed by software. SUMMARY OF THE INVENTION [0008]The present invention is provided to solve the problem that it is impossible for preventing the terminal from being changed by software in the related art; and the major objective of the present invention is to provide a method for updating mobile terminal software and mobile terminal to solve the above problem. [0009]To achieve the above objectives, according to one aspect of the present invention, a method for updating mobile terminal software is provided. [0010]The method for updating mobile terminal software comprises the following steps: mobile terminal software and/or tool software used for updating the mobile terminal software performing hand-shaking according to encrypted hand-shaking data sent by the other party; if the hand-shaking is successful, the mobile terminal software or the tool software carrying out verification of new mobile terminal software according to a pre-encrypted feature identifier of the mobile terminal software and a feature identifier of the new mobile terminal software, and determining whether the update is allowable according to the verification result. [0011]The above hand-shaking comprises the following steps: one party of the mobile terminal software and/or the tool software decrypting the encrypted hand-shaking data from the other party, and determining whether the decrypted hand-shaking data is identical to preset hand-shaking data; if the determining result is yes, the mobile terminal software determining that the hand-shaking is successful, otherwise, the mobile terminal software determining that the hand-shaking is failed. [0012]On the one hand, in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises: the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the encrypted hand-shaking data from the tool software; and the mobile terminal software decrypting the encrypted hand-shaking data from the tool software, and comparing the decrypted hand-shaking data with the preset hand-shaking data. [0013]On the other hand, in the case of determining whether the hand-shaking is successful by the mobile terminal software, the processing for performing the hand-shaking comprises: the mobile terminal software performing the calculation on preset parameter(s) by using a preset algorithm to obtain the preset hand-shaking data, and receiving the specific parameters served as the hand-shaking data encrypted and sent by the tool software; and the mobile terminal software decrypting the encrypted hand-shaking data from the tool software to obtain the specific parameters, performing the calculation on the specific parameters according to the preset algorithm, and comparing the calculated result of the specific parameters with the preset hand-shaking data. [0014]In addition, the processing for verifying the new mobile terminal software by the mobile terminal software or the tool software comprises: the mobile terminal software or the tool software decrypting the pre-encrypted feature identifier of the mobile terminal software; the mobile terminal software or the tool software comparing the decrypted feature identifier of the mobile terminal software with the feature identifier of the new mobile terminal software; if the feature identifier of the mobile terminal software is identical to the feature identifier of the new mobile terminal software, determining that the new mobile terminal software passes the verification; and if the feature identifier of the mobile terminal software is different from the feature identifier of the new mobile terminal software, determining that the new mobile terminal software does not pass the verification. [0015]The processing for determining whether the update is allowable according to the verification result comprises: if the new mobile terminal software passes the verification, the tool software updating the mobile terminal software by using the new mobile terminal software; and if the new mobile terminal software does not pass the verification, stopping the update processing. [0016]Preferably, the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier. [0017]To achieve the above objectives, according to another aspect of the present invention, a mobile terminal device is provided. [0018]The mobile terminal comprises: a hand-shaking data module, configured to generate hand-shaking data, determine whether the hand-shaking between mobile terminal software and tool software is successful according to hand-shaking data from the tool software and the generated hand-shaking data, and return the determination result to the tool software; a feature identifier module, configured to store the encrypted preset feature identifier which is used for the mobile terminal software or the tool software to carry out the verification of the new mobile terminal software for updating the mobile terminal software; an encryption module, configured to encrypt the hand-shaking data generated by the hand-shaking data module and the unencrypted feature identifier; and a communication command module, configured to send the hand-shaking data encrypted by the encryption module to the tool software, and receive the encrypted hand-shaking data from the tool software. [0019]The hand-shaking data module is configured to compare the hand-shaking data from the tool software with the generated hand-shaking data, determine the hand-shaking is successful if the hand-shaking data from the tool software is identical to the generated hand-shaking data, and determine the hand-shaking is failed if the hand-shaking data from the tool software is different from the generated hand-shaking data. [0020]Preferably, the feature identifier of the mobile terminal software and the feature identifier of the new mobile terminal software comprise at least one of the following: an operator identifier, a network-locking card-locking identifier, and a language identifier. [0021]By means of the above technical solution of the present invention, by introducing the two authentications of both the handshaking data and the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by a software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the technology of preventing such unlocking and language modification in the prior art, ensures maximum terminal security, and effectively protects the interests of providers. BRIEF DESCRIPTION OF THE DRAWINGS [0022]The accompanying drawings described herein are used for further illustrating the present invention and constitute a part of the application. The illustrative embodiments of the present invention and the description thereof are used for further explaining the present invention and are not used for limiting unduly the protection scope thereof, in which: [0023]FIG. 1 is a flowchart illustrating the method for updating mobile terminal software according to method embodiment of the present invention; [0024]FIG. 2 is a flowchart illustrating a processing example of the method for updating mobile terminal software according to method embodiment of the present invention; and [0025]FIG. 3 is a block diagram illustrating the mobile terminal according to device embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Function Summary [0026]To solve the problem that the terminal can easily be changed by software in the related art, the present invention implements the unidirectional/bidirectional hand-shaking of the tool software (software for performing the update) and the mobile terminal software (the software to be updated) and the verification of the new software of the mobile terminal (the software that will replace the mobile terminal software) performed by the mobile terminal software by taking into account the feature that the changing of software needs pass through a data line, a built-in data interface of mobile terminal and the data line connected to the interface, so as to eliminate the possibility of illegally updating the mobile terminal software during the illegal changing process rather than based on the illegally-changed result, thereby protecting to the largest extend the mobile terminal in the nondestructive manner. Method Embodiment [0027]In accordance with the embodiment of the present invention, a method for updating mobile terminal software is provided for preventing the mobile terminal software of the mobile terminal from being illegally updated. [0028]FIG. 1 is a flowchart illustrating the method for updating mobile terminal software according to method embodiment of the present invention. As shown in FIG. 1, the method comprises the following steps S102-S104. [0029]Step S102, mobile terminal software and/or tool software used for updating the mobile terminal software perform hand-shaking according to encrypted hand-shaking data sent by the other part, that is to say, one party of the mobile terminal software and the tool software used for updating the mobile terminal software performs an unidirectional hand-shaking of both parties according to the encrypted hand-shaking data sent by the other party, or the mobile terminal software and the tool software used for updating the mobile terminal software perform the bidirectional hand-shaking of both parties according to the encrypted hand-shaking data that both parties send to each other. [0030]Step S104, if said hand-shaking is successful, the mobile terminal software or the tool software carries out verification of new mobile terminal software according to a pre-encrypted feature identifier of the mobile terminal software (the feature identifier may be a identification group, of which the composition may be combined and adjusted freely according to the practical requirement, for example, it may include one or the combination of an operator identifier, a network-locking card-locking identifier and a language identifier, and further include information such as a version number) and a feature identifier of the new mobile terminal software required for updating the mobile terminal software, and determines whether the update is allowable according to the verification result, i.e. determines whether it is allowable that the new mobile terminal software is used to update the mobile terminal software. [0031]In step S102, The processing for performing the unidirectional or bidirectional hand-shaking specifically comprises the following steps: no matter it is unidirectional hand-shaking or bidirectional hand-shaking, one party of the mobile terminal software and the tool software needs to decrypt the encrypted hand-shaking data from the other party, and determines whether the decrypted hand-shaking data are identical to the preset hand-shaking data, wherein if said determining result is yes, the hand-shaking is determined to be successful; otherwise, the hand-shaking is determined to be failed. [0032]Moreover, in step S102, the hand-shaking data may be generated randomly by the mobile terminal software according to some information; the mobile terminal software and the legal tool software both know the content of hand-shaking data. By introducing the hand-shaking data, it is guaranteed that the illegal tool software can not implement successfully the hand-shaking communication; at the same time, by encrypting the hand-shaking data, it is guaranteed that the correct hand-shaking data can not be monitored from the transmission packet. The method for encrypting the hand-shaking data may adopt a same set of encryption algorithm negotiated and shared by the mobile terminal software and the tool software. [0033]Additionally, if the unidirectional hand-shaking is performed, the encrypted hand-shaking data may be transmitted as a command by the tool software served as the master control side to the mobile terminal software. After receiving and decrypting the hand-shaking data, the mobile terminal software served as the receiving side compares the hand-shaking data with its hand-shaking data firmly stored (in read only memory). The encrypted hand-shaking data may also be transmitted to the tool software by the mobile terminal software served as the master control side via a command response packet. After receiving and decrypting the hand-shaking data, the tool software served as the receiving side compares the hand-shaking data with its hand-shaking data firmly stored (in read only memory). Preferably, no matter the hand-shaking data is in the mobile terminal software or in the tool software, the hand-shaking data is set as read only attribute, so that the hand-shaking data can not be changed through any external manner. [0034]In the above processing, the hand-shaking data may be calculated according to the preset parameters (for example, the terminal serial number that can be acquired by the mobile terminal software and the tool software); and the parameters can also be directly served as the hand-shaking data for encrypted transmission. In general, such preset parameters may be stored in the tool software and/or the mobile terminal software. The initiating side of hand-shaking may be any one of the terminal software and the tool software. [0035]However, preferably, the final result determination may be performed at the mobile terminal software side to prevent some pirated tools from skipping the step for determining whether the hand-shaking is successful, which further guarantees the security of update. [0036]The manner for performing the hand-shaking success determination at the terminal side may be one of the following manners. [0037](Manner 1) the mobile terminal software performs calculation on preset parameters by using preset algorithm(s) to obtain preset hand-shaking data, and receives the encrypted hand-shaking data from the tool software; and the mobile terminal software decrypts the encrypted hand-shaking data from the tool software, and compares the decrypted hand-shaking data with preset hand-shaking data. [0038](Manner 2) the mobile terminal software performs calculation on preset parameters by using preset algorithm(s) to obtain preset hand-shaking data, and receives the specific parameters served as the hand-shaking data encrypted and sent by the tool software; the mobile terminal software decrypts the encrypted hand-shaking data from the tool software to obtain the specific parameters, performs calculation on the specific parameters according to the preset algorithm(s), and compares the calculation result of the specific parameters with the preset hand-shaking data. [0039]It should be noted that, in the above Manner 2, the specific parameters are severed as the hand-shaking data, and the processing for the calculation of the specific parameters is performed at the terminal side. [0040]In addition, in step 104, the processing of verifying new mobile terminal software performed by the mobile terminal software or tool software comprises following steps: the mobile terminal software or the tool software decrypts the pre-encrypted feature identifier of the mobile terminal software; and the mobile terminal software or the tool software compares the decrypted feature identifier of the mobile terminal software with the feature identifier of the new mobile terminal software wherein if the feature identifier of the mobile terminal software is identical to the feature identifier of the new mobile terminal software, it is determined that the new mobile terminal software passes the verification and the update is allowed; and if the feature identifier of the mobile terminal software is different from the feature identifier of the new mobile terminal software, it is determined that the new mobile terminal software does not pass the verification and the update processing is stopped. [0041]In the case of verifying the new mobile terminal software by the tool software, the tool software needs to send a command for acquiring the feature identifier of mobile terminal software to the mobile terminal software; moreover, in the process of the mobile terminal software sending its feature identifier to the tool software, the feature identifier may be encrypted and then be transmitted, which enhances the security of the update process. [0042]On the other hand, in the case of verifying the new mobile terminal software by the mobile terminal software, it is necessary for receiving the feature identifier of the new mobile terminal software from the tool software; and the feature identifier of the new mobile terminal software may be encrypted and then be transmitted, which enhances the security of the update process. [0043]The verification of the new mobile terminal software performed by the tool software is described as example. [0044]FIG. 2 is a flowchart illustrating an example of the method for updating mobile terminal software according to the method embodiment of the present invention. As shown in FIG. 2, in practical application, in the case of verifying the new mobile terminal software by the tool software, the method for updating mobile terminal software according to the present embodiment may comprise the following steps 201-206. [0045]Step 201, a personal computer (PC) capable of executing tool software is connected to a terminal via a data line, and starts to communicate with the terminal. [0046]Step 202, the software of the terminal itself and the tool software transmit encrypted hand-shaking data. [0047]Step 203, it is determined whether the hand-shaking is successful, wherein in the case of the unidirectional hand-shaking, if the tool software served as the master control side sends the encrypted hand-shaking data in step 202, the mobile terminal software determines whether the hand-shaking data are correct, encrypts the determination result and returns it to the tool software via a command response packet, and if the mobile terminal software served as the master control side sends the encrypted hand-shaking data in step 202, the tool software determines whether the hand-shaking data are correct, and returns the encrypted determination result; and in the case of the bidirectional hand-shaking, each of the two sides needs to determine whether the hand-shaking data of the other side is correct, and returns the encrypted determination result to the other side (steps 202 and 203 correspond to the above step S102). [0048]Step 204, it can be determined whether the hand-shaking is successful according to the determination result of step 203, wherein if the hand-shaking is failed, the tool software terminates the procedure; and if the hand-shaking is successful, the tool software sends a specific command to the mobile terminal software to acquire the encrypted feature identifier of mobile terminal software, wherein the specific command is negotiated between the tool software and the mobile terminal software in a special manner, the algorithm for encrypting the feature identifier may be negotiated by the mobile terminal software and the tool software together, and the algorithm for encrypting the feature identifier may be the same as the algorithm for encrypting the hand-shaking data; and the encryption transmission of the feature identifier guarantees that the real data can not be monitored during transmission, which enhances the protection of terminal security. [0049]Step 205, it is determined whether the acquired decrypted feature identifier is identical to the feature identifier of the mobile terminal software to be updated (i.e. the above new mobile terminal software) (steps 204 and 205 correspond to the above step S104). [0050]Step 206, if the comparing result of step 205 is “being identical”, it is started to update the mobile terminal software (which can have the update procedure in which the tool software replaces the mobile terminal software with the new mobile terminal software), otherwise, the procedure is terminated. Device Embodiment [0051]In the present embodiment, a mobile terminal is provided for implementing the above method for updating mobile terminal software and the mobile terminal can avoid the illegal update of its terminal software. [0052]FIG. 3 is a block diagram illustrating the mobile terminal according to the device embodiment of the present invention. As shown in FIG. 3, the mobile terminal according to the present embodiment comprises: a hand-shaking data module 10, a feature identifier module 20, an encryption module 30, a communication command module 40, of which the above structure is described hereinafter. [0053]The hand-shaking data module 10 is used for generating the hand-shaking data, reading the hand-shaking data from the tool software, determining whether the hand-shaking of the mobile terminal software and the tool software is successful according to the hand-shaking data from the tool software and the generated hand-shaking data, and returning the determination result to the tool software. [0054]The feature identifier module 20 is used for storing the encrypted preset feature identifier, so that the mobile terminal software or the tool software carries out the verification of the new mobile terminal software for replacing the mobile terminal software, by using the stored feature identifier; [0055]The encryption module (may also be referred to as encryption algorithm module) 30 is used for encrypting the hand-shaking data generated by the hand-shaking data module 10 and the unencrypted feature identifier, so as to avoid that the transmitted hand-shaking data and the feature identifier of the mobile terminal software are monitored in the process of communication. [0056]The communication command module 40 is used for sending the hand-shaking data encrypted by the encryption module 30 to the tool software, receiving the encrypted hand-shaking data from the tool software, and encoding, packing and transmitting the feature identifier of the mobile terminal software. Preferably, during the implementation of the present invention, the command transmitted by the communication command module can be separated from other general commands, so as to further guarantee the security of terminal. [0057]The hand-shaking data module 10 may compare the hand-shaking data from the tool software with the generated hand-shaking data, determine the hand-shaking is successful if the hand-shaking data from the tool software are the same as the generated hand-shaking data, otherwise, determine the hand-shaking is failed. Herein, the generated hand-shaking data may be the hand-shaking data which calculated according preset parameters (for example the serial number of terminal), or may be the extracted preset parameters; moreover, during the hand-shaking, the processing described in the above Manner 1 and Manner 2 can be referred to for the detailed processing. [0058]The method of the encryption module 30 for encrypting the hand-shaking data generated by the hand-shaking data module 10 may be the same as or different from the method for encrypting the unencrypted feature identifier. [0059]Preferably, the feature identifier is at least one of the following: an operator identifier, a network-locking card-locking identifier, a language identifier. The feature identifier herein may be an identification group, of which the composition may be adjusted and changed according to the practical requirements, which is not listed herein one by one any more. [0060]It can be seen from the above that, in the technical solution of the present invention, the software of the terminal itself and the tool software both have a set of negotiated encryption algorithm. When the mobile terminal software is changed through the data line, it is only possible to replace the mobile terminal software with the network-locking card-locking software of the local operator and the mobile terminal software of the local operator language, which effectively avoids the illegal software update of terminal and guarantees the security of terminal. [0061]To sum up, by introducing the two authentications of both the handshaking data and the feature identifier, this invention greatly eliminates the possibility that the terminal may be modified by software, avoids terminal unlocking and modification of language in the relevant technology, overcomes the deficiencies of the prior art in preventing such unlocking and language modification, ensures to the largest extent the terminal security, and effectively protects the interests of operators; in addition, the security may be ensured only by adding a little processing, which is implemented simply and reliably. [0062]The foregoing is only preferred embodiments of the present invention and is not for use in limiting the protection scope thereof, and for those skilled in the art, there may be various modifications and changes to the present invention. Any modification, equivalent replacement and improvement made under the spirit and principle of the present invention should be included in the protection scope thereof.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端软件更新方法及移动终端。 发明背景 [0002] 目前,随着全球移动通信市场的快速发展,各运营商之间的竞争也十分激烈。 特别是在终端产品市场,运营商纷纷出台各种系列的促销政策吸引用户,并以极大的优惠力度向用户销售终端; 有些运营商甚至免费向用户提供终端。 [0003] 但是,考虑到自身的利益,运营商一般会采取一系列的限制措施。 常见的限制方式是对终端进行限制,使终端只能在给用户优惠的运营商的网络中使用,或者需要插入指定的卡才能使终端进入可用状态。 这种限制方式通常称为锁网或锁卡。 [0004] 虽然运营商可以对其终端的使用进行限制,但锁网或锁卡终端仍有可能被一些不法分子通过某种方法进行改造,使改造后的终端失去锁网或卡锁功能。 锁定,解除对运营商的限制,使终端可以被其他运营商或其他网络使用; 或将插卡使用的终端与指定的卡分开,甚至可以将终端的界面更改为其他语言,进而导致更改后的终端在其他语言的运营商网络中使用,显然 严重损害了经营者的利益。 [0005] 因此,一个重要的问题是如何防止锁网卡锁终端被软件更改为未解锁的终端(即避免解锁),以及如何防止终端的语言A被软件更改为语言B(即无法解锁)。 避免修改语言),以保护运营商的利益。 [0006] 目前,移动终端领域提供了几种防止移动终端设备的软件被非法修改的方法,其中一种方法是记录PAF-ROM中存储的值和必要的数据,如国际移动设备 同时在一个只能被编程一次的内存区域中,与基本数据等值进行比较,判断是否是异常修改的软件,当被软件修改时,判断是否 软件被非法更改。 上述方法的问题在于必须将终端的一部分划分为只能一次编程的存储器,或者必须单独添加可编程只读存储器(PROM)芯片,实现成本高; 而且,上述方法的判定主要针对变更后的结果,在判定终端软件被非法变更后,需要防止变更后的终端继续使用,存在滞后性,无法阻止终端被盗用。 实际上是由软件改变的。 [0007] 相关技术中没有提供有效的方案来解决无法通过软件改变终端的问题。 发明内容 [0008] 为解决相关技术中无法防止终端被软件更改的问题而提出本发明; 本发明的主要目的在于提供一种移动终端软件更新方法及移动终端,以解决上述问题。 [0009] 为实现上述目的,根据本发明的一个方面,提供了一种移动终端软件的更新方法。 [0010]该移动终端软件更新方法包括以下步骤:移动终端软件和/或用于更新移动终端软件的工具软件根据对方发送的加密握手数据进行握手; 若握手成功,则移动终端软件或工具软件根据预加密的移动终端软件特征标识和新移动终端软件特征标识对新移动终端软件进行校验,确定 根据验证结果是否允许更新。 [0011] 上述握手包括以下步骤:移动终端软件和/或工具软件的一方对另一方加密后的握手数据进行解密,并判断解密后的握手数据是否与预设的握手数据相同。 抖动数据; 若判断结果为是,移动终端软件判断握手成功,否则移动终端软件判断握手失败。 [0012] 一方面,在移动终端软件判断握手是否成功的情况下,进行握手的处理包括:移动终端软件使用预设的参数对预设参数进行计算。 算法获取预设的握手数据,并从工具软件接收加密后的握手数据; 移动终端软件对来自工具软件的加密后的握手数据进行解密,并将解密后的握手数据与预设的握手数据进行比对。 [0013] 另一方面,在移动终端软件判断握手是否成功的情况下,进行握手的处理包括:移动终端软件使用预设的参数对预设参数进行计算。 算法获取预设的握手数据,接收工具软件加密发送的握手数据的具体参数; 移动终端软件从工具软件中解密加密后的握手数据,得到特定参数,根据预设算法对特定参数进行计算,并将特定参数的计算结果与预设握手进行比较 数据。 [0014] 进一步地,所述移动终端软件或工具软件对新的移动终端软件进行验证的处理包括: 移动终端软件或工具软件对移动终端软件的预加密特征标识进行解密; 移动终端软件或工具软件将解密后的移动终端软件特征标识与新移动终端软件的特征标识进行比较; 如果移动终端软件的特征标识与新的移动终端软件的特征标识相同,则确定新的移动终端软件通过验证; 如果移动终端软件的特征标识与新的移动终端软件的特征标识不同,则确定新的移动终端软件未通过验证。 [0015] 所述根据验证结果判断是否允许更新的处理包括:如果新的移动终端软件验证通过,则工具软件使用新的移动终端软件更新移动终端软件。 如果新的移动终端软件没有通过验证,则停止更新处理。 [0016] 优选地,所述移动终端软件的特征标识和所述新的移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。 [0017] 为实现上述目的,根据本发明的另一方面,提供了一种移动终端设备。 [0018]移动终端包括:握手数据模块,用于生成握手数据,根据来自工具软件的握手数据和生成的握手信息,判断移动终端软件与工具软件握手是否成功。 摇动数据,并将判断结果返回给工具软件; 特征标识模块,用于存储加密后的预设特征标识,用于移动终端软件或工具软件对新的移动终端软件进行验证,以更新移动终端软件; 加密模块,用于对握手数据模块生成的握手数据和未加密的特征标识进行加密; 通信命令模块,用于将加密模块加密后的握手数据发送给工具软件,并从工具软件接收加密后的握手数据。 [0019] 握手数据模块,用于将工具软件的握手数据与生成的握手数据进行比对,如果工具软件的握手数据与生成的握手数据相同,则握手成功。 -握手数据,如果来自工具软件的握手数据与生成的握手数据不一致,则判定握手失败。 [0020] 优选地,所述移动终端软件的特征标识和所述新的移动终端软件的特征标识包括以下至少之一:运营商标识、锁网锁卡标识、语言标识。 [0021] 通过本发明的上述技术方案,通过引入握手数据和特征标识的两次认证,大大消除了终端被软件修改的可能性,避免了终端解锁和语言修改。 在相关技术中,克服了现有技术中防止此类解锁和语言修改技术的不足,最大限度地保证了终端安全,有效保护了提供商的利益。 附图的简要说明 [0022] 此处所描述的附图用于进一步说明本发明,构成本申请的一部分。 本发明的示例性实施例及其说明用于进一步解释本发明,并不用于不当限制本发明的保护范围,其中: [0023] 图1为本发明方法实施例的移动终端软件更新方法的流程图; [0024] 图2为本发明方法实施例的移动终端软件更新方法的处理示例流程图。 和 [0025] 图3是示出根据本发明的设备实施例的移动终端的框图。 优选实施例的详细说明 功能概要 [0026] 为了解决相关技术中终端容易被软件更改的问题,本发明实现了工具软件(进行更新的软件)和移动终端软件(待更新的软件)的单向/双向握手。 更新)和移动终端软件对移动终端新软件(将替代移动终端软件的软件)的验证,考虑到软件更改需要通过数据线的特点,内置了一个 -in移动终端的数据接口及连接该接口的数据线,杜绝在非法更改过程中对移动终端软件进行非法更新的可能性,而不是基于非法更改的结果,从而最大程度地保护 以无损方式访问移动终端。 方法实施例 [0027] 根据本发明实施例,提供了一种移动终端软件的更新方法,以防止移动终端的移动终端软件被非法更新。 [0028] 图1为本发明方法实施例的移动终端软件更新方法的流程图。 如图1所示,该方法包括以下步骤S 102 -S 104 . [0029] 脚步 102 、移动终端软件和/或用于更新移动终端软件的工具软件根据另一方发送的加密握手数据进行握手,即移动终端软件的一方和所使用的工具软件 更新移动终端软件根据对方发送的加密握手数据对双方进行单向握手,或者移动终端软件和更新移动终端软件的工具软件进行双向握手。 双方根据双方发送给对方的加密握手数据进行握手。 [0030] 脚步 104 ,如果所述握手成功,则移动终端软件或工具软件根据预先加密的移动终端软件的特征标识(特征标识可以是标识组,其中 组成可以根据实际需要自由组合调整,例如可以包括运营商标识、锁网锁卡标识和语言标识中的一种或组合,还可以包括版本等信息 number)和更新移动终端软件所需的新移动终端软件的特征标识,根据验证结果判断是否允许更新,即判断是否允许使用新移动终端软件更新移动终端软件。 移动端软件。 [0031] 在步骤S 102 ,进行单向或双向握手的处理具体包括以下步骤:无论是单向握手还是双向握手,移动终端软件和工具软件的一方需要对加密后的握手信息进行解密。 来自对方的握手数据,判断解密后的握手数据与预设的握手数据是否相同,若判断结果为是,则确定握手成功。 否则,确定握手失败。 [0032] 此外,在步骤S 102 ,握手数据可以是移动终端软件根据一些信息随机生成的; 移动终端软件和合法工具软件都知道握手数据的内容。 通过引入握手数据,保证非法工具软件无法成功实现握手通信; 同时,通过对握手数据进行加密,保证无法从传输包中监听到正确的握手数据。 对握手数据进行加密的方法可以采用移动终端软件和工具软件协商共享的同一套加密算法。 [0033] 另外,如果是单向握手,则可以由作为主控端的工具软件将加密后的握手数据作为命令发送给移动终端软件。 作为接收方的移动终端软件在接收并解密握手数据后,将握手数据与其牢固存储的握手数据(在只读存储器中)进行比较。 也可以由作为主控端的移动终端软件通过命令响应包将加密后的握手数据发送给工具软件。 作为接收方的工具软件在接收并解密握手数据后,将握手数据与其牢固存储的握手数据(在只读存储器中)进行比较。 优选地,无论握手数据是在移动终端软件中还是在工具软件中,都将握手数据设置为只读属性,使得握手数据无法通过任何外部方式进行更改。 [0034]在上述处理中,可以根据预先设置的参数(例如,移动终端软件和工具软件可以获取的终端序列号)计算握手数据; 参数也可以直接作为握手数据进行加密传输。 通常,这些预设参数可以存储在工具软件和/或移动终端软件中。 握手的发起方可以是终端软件和工具软件中的任意一种。 [0035] 但优选地,最终结果判断可以在移动终端软件侧进行,避免部分盗版工具跳过判断握手是否成功的步骤,进一步保证更新的安全性。 [0036] 终端侧进行握手成功判断的方式可以为以下方式之一。 [0037] (方式一)移动终端软件通过预设算法对预设参数进行计算,得到预设的握手数据,并从工具软件接收加密后的握手数据; 移动终端软件对来自工具软件的加密后的握手数据进行解密,并将解密后的握手数据与预设的握手数据进行比对。 [0038] (方式二)移动终端软件通过预设算法对预设参数进行计算得到预设握手数据,并接收工具软件加密发送的握手数据具体参数; 移动终端软件对来自工具软件的加密握手数据进行解密,得到特定参数,根据预设算法对特定参数进行计算,并将特定参数的计算结果与预设握手数据进行比较。 震动数据。 [0039] 需要说明的是,在上述方式二中,将特定参数分割为握手数据,在终端侧进行特定参数的计算处理。 [0040] 此外,在步 104 、 移动终端软件或工具软件对新的移动终端软件进行验证的处理包括以下步骤: 移动终端软件或工具软件对预加密的移动终端软件特征标识进行解密; 移动终端软件或工具软件将解密后的移动终端软件的特征标识与新的移动终端软件的特征标识进行比较,如果移动终端软件的特征标识与新的移动终端的特征标识相同 软件,确定新的移动终端软件通过验证,允许更新; 如果移动终端软件的特征标识与新的移动终端软件的特征标识不同,则确定新的移动终端软件未通过验证,停止更新处理。 [0041] 在工具软件对新的移动终端软件进行验证时,工具软件需要向移动终端软件发送获取移动终端软件特征标识的命令; 并且,移动终端软件在向工具软件发送其特征标识的过程中,可以对特征标识进行加密后传输,增强了更新过程的安全性。 [0042] 另一方面,在移动终端软件对新的移动终端软件进行验证时,需要从工具软件中接收新的移动终端软件的特征标识; 并且可以对新的移动终端软件的特征标识进行加密后传输,增强了更新过程的安全性。 [0043] 以工具软件对新的移动终端软件的验证为例进行说明。 [0044]图2是示出根据本发明方法实施例的更新移动终端软件的方法的示例的流程图。 如图2所示,在实际应用中,在通过工具软件验证新的移动终端软件的情况下,本实施例的移动终端软件更新方法可以包括以下步骤 201 - 206 . [0045] 步 201 ,可执行工具软件的个人计算机(PC)通过数据线连接到终端,并开始与终端通信。 [0046] 步 202 ,终端自身的软件和工具软件传输加密的握手数据。 [0047] 步 203 ,判断握手是否成功,其中在单向握手的情况下,如果作为主控端的工具软件在步骤中发送加密的握手数据 202 ,移动终端软件判断握手数据是否正确,将判断结果加密后通过命令响应包返回给工具软件,如果作为主控端的移动终端软件发送加密后的握手数据 数据同步 202 ,工具软件判断握手数据是否正确,并返回加密后的判断结果; 而在双向握手的情况下,双方都需要判断对方的握手数据是否正确,并将加密后的判断结果返回给对方(步骤 202 和 203 对应上面的步骤S 102 ). [0048] 步 204 ,可以根据step的判断结果判断握手是否成功 203 ,其中如果握手失败,则工具软件终止流程; 如果握手成功,则工具软件向移动终端软件发送特定命令以获取移动终端软件的加密特征标识,其中该特定命令是工具软件与移动终端软件以特殊方式协商的。 方式中,特征标识的加密算法可以由移动终端软件和工具软件共同协商,特征标识的加密算法可以与握手数据的加密算法相同。 特征标识的加密传输保证了真实数据在传输过程中无法被监听,增强了对终端安全的保护。 [0049] 步 205 ,判断获取的解密后的特征标识与待更新的移动终端软件(即上述新的移动终端软件)的特征标识是否相同(步骤 204 和 205 对应上面的步骤S 104 ). [0050] 步 206 , 如果步骤的比较结果 205 为“相同”,则开始更新移动终端软件(可以有工具软件用新的移动终端软件替换移动终端软件的更新流程),否则流程结束。 装置实施例 [0051] 本实施例提供了一种移动终端,用于实现上述移动终端软件的更新方法,移动终端可以避免其终端软件被非法更新。 [0052] 图3是示出根据本发明装置实施例的移动终端的框图。 如图3所示,本实施例的移动终端包括: 握手数据模块 10 ,特征标识符模块 20 , 一个加密模块 30 , 通信命令模块 40 ,其上述结构在下文中描述。 [0053] 握手数据模块 10用于生成握手数据,从工具软件中读取握手数据,根据来自工具软件的握手数据判断移动终端软件与工具软件握手是否成功,以及 生成的握手数据,将判断结果返回给工具软件。 [0054] 特征标识符模块 20 用于存储加密后的预设特征标识,以便移动终端软件或工具软件使用存储的特征标识对新的移动终端软件进行验证,以替换移动终端软件。 [0055] 加密模块(也可称为加密算法模块) 30 用于对握手数据模块生成的握手数据进行加密 10 以及未加密的特征标识,避免通信过程中传输的握手数据和移动终端软件的特征标识被监听。 [0056] 通信命令模块 40 用于发送加密模块加密后的握手数据 30 发送给工具软件,接收来自工具软件的加密后的握手数据,对移动终端软件的特征标识进行编码、打包和传输。 优选地,在实施本发明的过程中,可以将通信命令模块发送的命令与其他通用命令分开,进一步保证终端的安全性。 [0057] 握手数据模块 10 可以将来自工具软件的握手数据与生成的握手数据进行比较,如果来自工具软件的握手数据与生成的握手数据相同,则判断握手成功,否则,判断 握手失败。 其中,生成的握手数据可以是根据预设参数(例如终端序列号)计算得到的握手数据,也可以是提取的预设参数。 并且,在握手过程中,具体处理可以参考上述方式一和方式二中描述的处理。 [0058] 加密模块的方法 30 用于对握手数据模块生成的握手数据进行加密 10 与未加密特征标识的加密方法可以相同也可以不同。 [0059] 优选地,所述特征标识为以下至少之一:运营商标识、锁网锁卡标识、语言标识。 这里的特征标识可以是一个标识组,其组成可以根据实际需要进行调整和变化,在此不再一一列举。 [0060] 由上可见,在本发明的技术方案中,终端自身的软件和工具软件均具有一套协商的加密算法。 通过数据线更换手机端软件时,只能更换手机端软件为当地运营商的锁网锁卡软件和当地运营商语言的手机端软件,有效避免了 终端的非法软件更新,保证终端的安全。 [0061] 综上所述,本发明通过引入握手数据和特征标识两种认证方式,极大地杜绝了终端被软件修改的可能性,避免了相关技术中的终端解锁和语言修改,克服了现有技术的不足。 防止此类解锁和语言修改的现有技术,最大限度地保证了终端安全,有效保护了运营商的利益。 另外,只需增加少量处理即可保证安全性,实现简单可靠。 [0062]以上所述仅为本发明的优选实施例而已,并不用于限制本发明的保护范围,对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:48.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101437224A(String), EP2381711A1(String), EP2381711A4(String), US20110258451A1(String), WO2010072073A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101437224A(String), EP2381711A1(String), EP2381711A4(String), US20110258451A1(String), WO2010072073A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101437224A(String), EP2381711A1(String), EP2381711A4(String), US20110258451A1(String), WO2010072073A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270935(Integer), CN101437224A(String), 1047569(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270935(Integer), EP2381711A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.240 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270935(Integer), EP2381711A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270935(Integer), US20110258451A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270935(Integer), WO2010072073A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101437224A(String), CN101437224A(String), 1242748800(Integer), 270935(Integer), 185219(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), YANG, CUIHONG(String), SUN, DENGYUN(String), 中兴通讯股份有限公司(String), YANG CUIHONG(String), SUN DENGYUN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185942(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185942(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: YANG, CUIHONG(String), YANG CUIHONG(String), 0(Integer), 1681976029(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SUN, DENGYUN(String), SUN DENGYUN(String), 0(Integer), 1681976029(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185942(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75829(Integer), 2(Integer), 185942(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75830(Integer), 2(Integer), 185942(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75829(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:49.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10063685B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Automatic execution method and device for operation of mobile terminal, and mobile terminal(String), 移动终端操作自动执行方法、装置及移动终端(String), US10063685B2(String), Embodiments of the present disclosure provide a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal. The method for automatically executing an operation of a mobile terminal includes: acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal, herein the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current; determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; and executing a preset operation according to the current state.(String), 本发明实施例提供一种自动执行移动终端操作的方法、装置及移动终端。 自动执行移动终端操作的方法包括:获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度,其中移动终端的当前移动/静止情况信息包括指示: 移动终端当前静止或移动终端当前移动; 根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态; 根据当前状态执行预设操作。(String), US15/329252(String), 1414944000(Integer), US10063685B2(String), 1535385600(Integer), 1535385600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 10(Integer), CN102884841A | CN103780748A | CN103943106A | CN202907027U | US20060116175A1 | US20110273378A1 | US20110304648A1 | US20120094714A1 | US20140028445A1 | US7676340B2(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185943(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\28719a60815c4162aec02f1062523bde.png(String), 185943(Integer), 28719a60815c4162aec02f1062523bde.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Automatic execution method and device for operation of mobile terminal, and mobile terminal(String), 移动终端操作自动执行方法、装置及移动终端(String), US10063685B2(String), Embodiments of the present disclosure provide a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal. The method for automatically executing an operation of a mobile terminal includes: acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal, herein the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current; determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; and executing a preset operation according to the current state.(String), 本发明实施例提供一种自动执行移动终端操作的方法、装置及移动终端。 自动执行移动终端操作的方法包括:获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度,其中移动终端的当前移动/静止情况信息包括指示: 移动终端当前静止或移动终端当前移动; 根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态; 根据当前状态执行预设操作。(String), US15/329252(String), 1414944000(Integer), US10063685B2(String), 1535385600(Integer), 1535385600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 10(Integer), CN102884841A | CN103780748A | CN103943106A | CN202907027U | US20060116175A1 | US20110273378A1 | US20110304648A1 | US20120094714A1 | US20140028445A1 | US7676340B2(String), \20230420\28719a60815c4162aec02f1062523bde.png(String), 17(Integer), 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.632 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.666 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 1. A method for automatically executing an operation of a mobile terminal, comprising:acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of a mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current;determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; andexecuting a preset operation according to the current state,wherein said determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature comprises:when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state; andwhen the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state, and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, determining the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state.(String), 1.一种自动执行移动终端操作的方法,包括:获取移动终端当前动/静情况信息、内部温度和当前环境温度,其中,移动终端当前动/静情况信息包括表示移动终端当前静止或移动中的信息目前;根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态;和根据当前状态执行预设操作,其中,所述根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态包括:当移动终端当前处于移动状态时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则确定移动终端当前处于暴露环境中,并移动状态;若内部温度与当前环境温度的差值大于或等于预设第一温度阈值且小于或等于预设第二温度阈值,则确定移动终端当前状态为移动终端处于在浅隐蔽环境和移动状态下;若内部温度与当前环境温度的差值大于预设的第二温度阈值,则确定移动终端当前处于深隐环境和移动状态。和当前移动终端静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则确定移动终端当前处于暴露环境中,并静止状态,若内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端当前状态为处于隐藏环境和静止状态.2.根据权利要求1所述的方法,其中所述获取移动终端当前动/静情况信息包括:通过加速度传感器获取移动终端的运动加速度;和根据移动加速度获取移动终端当前的移动/静止情况信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 2. The method according to claim 1, wherein said acquiring current moving/stationary situation information of a mobile terminal comprises:acquiring a movement acceleration of the mobile terminal through an acceleration sensor; andacquiring the current moving/stationary situation information of the mobile terminal according to the movement acceleration.(String), 3.根据权利要求1所述的方法,其中所述获取移动终端的内部温度和当前环境温度包括:通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度;和通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前环境温度。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 3. The method according to claim 1, wherein said acquiring an internal temperature and a current environment temperature of a mobile terminal comprises:acquiring the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal; andacquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal.(String), 4.根据权利要求3所述的方法,其中第二温度传感器为多个第二温度传感器。所述通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前环境温度包括:通过多个第二温度传感器获取多个环境温度;和获取多个环境温度的期望值作为当前环境温度。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 4. The method according to claim 3, wherein the second temperature sensor is a plurality of second temperature sensors; and said acquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal comprises:acquiring a plurality of environment temperatures through the plurality of second temperature sensors; andacquiring an expected value of the plurality of environment temperatures as the current environment temperature.(String), 5.根据权利要求1所述的方法,其中,在根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端当前状态之前,该方法还包括:根据移动终端当前的CPU使用率和待机电流大小分别确定第一温度阈值、第二温度阈值和第三温度阈值。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 5. The method according to claim 1, wherein, before determining the current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature, the method further comprises:determining the first temperature threshold, the second temperature threshold and the third temperature threshold respectively according to a current CPU use rate and a standby current magnitude of the mobile terminal.(String), 6.非暂时性计算机程序,包括一种程序指令,其特征在于,所述程序指令在移动终端执行时,所述移动终端能够执行权利要求1所述的方法。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 6. A non-transitory computer program, comprising program instructions, wherein, when the program instructions are executed by a mobile terminal, the mobile terminal can execute the method according to claim 1.(String), 7.一种承载根据权利要求6的计算机程序的载体。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.670 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 7. A carrier carrying the computer program according to claim 6.(String), 8.一种自动执行移动终端操作的装置,包括:获取模块,用于获取移动终端的当前动/静状态信息、内部温度和当前环境温度,其中,移动终端当前动/静状态信息包括表示移动终端在当前或静止状态的信息。移动终端当前正在移动;第一确定模块,用于根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态;和执行模块,用于根据当前状态执行预设操作,其中,第一判断模块包括:第一判断子模块,用于当移动终端当前处于移动状态时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则将移动终端当前状态判断为:移动终端处于暴露环境和移动状态;若内部温度与当前环境温度之差大于或等于预设第一温度阈值且小于或等于预设第二温度阈值,则确定移动终端当前状态为移动终端处于浅隐环境和移动状态;如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则确定移动终端的当前状态为深隐蔽环境和移动状态。和第二判断子模块,用于当前移动终端静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则判断移动终端当前状态为:移动终端处于暴露环境和静止状态;如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端的当前状态为处于隐藏环境和静止状态。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.670 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 8. A device for automatically executing an operation of a mobile terminal, comprising:an acquisition module arranged to acquire current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current;a first determination module arranged to determine a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; andan execution module arranged to execute a preset operation according to the current state,wherein the first determination module comprises:a first determination sub-module arranged to, when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, determine that the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state; anda second determination sub-module arranged to, when the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state; and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state.(String), 9.根据权利要求8所述的装置,其中采集模块包括:第一获取子模块,用于通过加速度传感器获取移动终端的运动加速度;和第二获取子模块,用于根据移动加速度获取移动终端当前的移动/静止情况信息。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.670 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 9. The device according to claim 8, wherein the acquisition module comprises:a first acquisition sub-module arranged to acquire a movement acceleration of the mobile terminal through an acceleration sensor; anda second acquisition sub-module arranged to acquire the current moving/stationary situation information of the mobile terminal according to the movement acceleration.(String), 10.一个移动终端,包括:10.根据权利要求9所述的内部温度传感器、外部温度传感器、加速度传感器以及自动执行移动终端操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.670 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 10. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 9, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 11.根据权利要求8所述的装置,其中采集模块包括:第三获取子模块,用于通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度;和第四获取子模块,用于通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前的环境温度。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.670 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 11. The device according to claim 8, wherein the acquisition module comprises:a third acquisition sub-module arranged to acquire the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal; anda fourth acquisition sub-module arranged to acquire the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal.(String), 12.根据权利要求11所述的装置,其中第二温度传感器为多个第二温度传感器。第四采集子模块包括:第一获取单元,用于通过多个第二温度传感器获取多个环境温度;和第二获取单元,用于获取所述多个环境温度中的期望值作为当前环境温度。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 12. The device according to claim 11, wherein the second temperature sensor is a plurality of second temperature sensors; and the fourth acquisition sub-module comprises:a first acquisition unit arranged to acquire a plurality of environment temperatures through the plurality of second temperature sensors; anda second acquisition unit arranged to acquire an expected value of the plurality of environment temperatures as the current environment temperature.(String), 13.移动终端,包括:13.根据权利要求12所述的移动终端内部温度传感器、外部温度传感器、加速度传感器及自动执行操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 13. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 12, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 14.移动终端,包括:12.根据权利要求11所述的移动终端内部温度传感器、外部温度传感器、加速度传感器及自动执行操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 14. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 11, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 15.根据权利要求8所述的装置,还包括:第二确定模块,用于根据移动终端当前的CPU使用率和待机电流大小,分别确定第一温度阈值、第二温度阈值和第三温度阈值。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 15. The device according to claim 8, further comprising:a second determination module arranged to respectively determine the first temperature threshold, the second temperature threshold and the third temperature threshold according to a current CPU use rate and a standby current magnitude of the mobile terminal.(String), 16.移动终端,包括:16.根据权利要求15所述的内部温度传感器、外部温度传感器、加速度传感器以及自动执行移动终端操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 14(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 16. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 15, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 17.移动终端,包括:9.根据权利要求8所述的内部温度传感器、外部温度传感器、加速度传感器以及自动执行移动终端操作的装置,其特征在于,内部温度传感器用于获取移动终端的内部温度;外部温度传感器用于获取移动终端的当前环境温度;和加速度传感器,用于获取移动终端当前的动/静止情况信息,其中,移动终端当前的动/静止情况信息包括表示移动终端当前静止或移动终端当前移动的信息。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:50.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185943(Integer), 17. A mobile terminal, comprising: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the device for automatically executing an operation of a mobile terminal according to claim 8, wherein,the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal;the external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal; andthe acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal, wherein the current moving/stationary situation information of the mobile terminal comprises information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current.(String), 1(Integer), 16(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.032 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185943(Integer), TECHNICAL FIELD [0001]The present disclosure relates to a terminal application technology, and in particular to an operation of a mobile terminal. BACKGROUND [0002]When people use mobile phones in daily life, different magnitudes of vibration or volume will be set according to different scenarios. On traditional functional mobile phones, such mode is referred as a scenario mode. However, that function is gradually faded on smart phones, but demands of users are not changed thereby. For example, when a user is in an office, volume needs to be turned down; and when a mobile phone is put in a pocket or a bag, to avoid misses of calls and short messages, the volume of the mobile phone needs to be turned up; and when the user sleeps, the volume and the vibration need to be turned off or a flight mode is turned on. In daily life, since the users forgot to adjust volume, vibration and the like, great inconvenience is brought to mobile phone users. SUMMARY [0003]Embodiments of the present disclosure provide a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal, which can determine a current state of a mobile terminal according to an internal temperature, a current environment temperature and current moving/stationary situation information of the mobile terminal, to automatically execute a corresponding preset operation, such that the mobile terminal can automatically adjust related settings according to different scenarios. [0004]According to one aspect of the present disclosure, an embodiment of the present disclosure provides a method for automatically executing an operation of a mobile terminal. The method includes: acquiring current moving/stationary situation information, an internal temperature and a current environment temperature of a mobile terminal, herein the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current; determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature; and executing a preset operation according to the current state. [0005]In an exemplary embodiment, acquiring current moving/stationary situation information of the mobile terminal includes: acquiring a movement acceleration of the mobile terminal through an acceleration sensor; and acquiring the current moving/stationary situation information of the mobile terminal according to the movement acceleration. [0006]In an exemplary embodiment, acquiring an internal temperature and a current environment temperature of a mobile terminal includes: acquiring the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal; and acquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0007]In an exemplary embodiment, the second temperature sensor is a plurality of second temperature sensors; and acquiring the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal includes: acquiring a plurality of environment temperatures through the plurality of second temperature sensors; and acquiring an expected value of the plurality of environment temperatures as the current environment temperature. [0008]In an exemplary embodiment, determining a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature includes the following operations. [0009]When the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state. [0010]When the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state; and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, it is determined the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state. [0011]In an exemplary embodiment, before determining the current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature, the method further includes: respectively determining the first temperature threshold, the second temperature threshold and the third temperature threshold according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0012]According to another aspect of the present disclosure, an embodiment of the present disclosure further provides a device for automatically executing an operation of a mobile terminal. The device includes an acquisition module, a first determination module and an execution module. The acquisition module is arranged to acquire current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. The first determination module is arranged to determine a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature. The execution module is arranged to execute a preset operation according to the current state. [0013]In an exemplary embodiment, the acquisition module includes a first acquisition sub-module and a second acquisition sub-module. The first acquisition sub-module is arranged to acquire a movement acceleration of the mobile terminal through an acceleration sensor. The second acquisition sub-module is arranged to acquire the current moving/stationary situation information of the mobile terminal according to the movement acceleration. [0014]In an exemplary embodiment, the acquisition module includes a third acquisition sub-module and a fourth acquisition sub-module. The third acquisition sub-module is arranged to acquire the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal. The fourth acquisition sub-module is arranged to acquire the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0015]In an exemplary embodiment, the second temperature sensor is a plurality of second temperature sensors. The fourth acquisition sub-module includes a first acquisition unit and a second acquisition unit. The first acquisition unit is arranged to acquire a plurality of environment temperatures through the plurality of second temperature sensors. The second acquisition unit is arranged to acquire an expected value of the plurality of environment temperatures as the current environment temperature. [0016]In an exemplary embodiment, the first determination module includes a first determination sub-module and a second determination sub-module. [0017]The first determination sub-module is arranged to, when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold and is smaller than or equal to a preset second temperature threshold, determine that the current state of the mobile terminal as that the mobile terminal is in a shallow hidden environment and a moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset second temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a deep hidden environment and a moving state. [0018]The second determination sub-module arranged to, when the mobile terminal is stationary at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a stationary state; and if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset third temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in a hidden environment and a stationary state. [0019]In an exemplary embodiment, the device further includes: a second determination module arranged to respectively determine the first temperature threshold, the second temperature threshold and the third temperature threshold according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0020]According to another aspect of the present disclosure, an embodiment of the present disclosure further provides a mobile terminal, including: an internal temperature sensor, an external temperature sensor, an acceleration sensor and the automobile execution device for the operation of the mobile terminal. Herein, the internal temperature sensor is arranged to acquire an internal temperature of the mobile terminal. The external temperature sensor is arranged to acquire a current environment temperature of the mobile terminal. The acceleration sensor is arranged to acquire current moving/stationary situation information of the mobile terminal. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. [0021]According to another aspect of the present disclosure, an embodiment of the present disclosure further provides a computer program and a carrier thereof. The computer program includes program instructions, and when the program instructions are executed by a mobile terminal, the mobile terminal can execute the method for automatically executing an operation of a mobile terminal. [0022]The above-mentioned technical solution of the embodiments of the present disclosure has the following beneficial effects: [0023]The method and device for automatically executing an operation of a mobile terminal, and the mobile terminal provided by the embodiments of the present disclosure can determine a current state of a mobile terminal according to an internal temperature, a current environment temperature and current moving/stationary situation information of the mobile terminal, to automatically execute a corresponding preset operation, such that the mobile terminal can automatically adjust related settings according to different scenarios. BRIEF DESCRIPTION OF DRAWINGS [0024]FIG. 1 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 1 of the present disclosure. [0025]FIG. 2 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 2 of the present disclosure. DETAILED DESCRIPTION [0026]The embodiments of the present disclosure will be described below in detail with reference to the drawings. It needs to be stated that the embodiments in the present disclosure and the features in the embodiments may be mutually and freely combined under the situation of no conflict. Although a logic sequence is illustrated in flowcharts, the illustrated or described steps may be executed according to a sequence different from a sequence here under certain circumstances. [0027]Aiming at the situation that calls are missed since terminal users often forget to adjust settings of mobile terminals according to different scenarios in the related art, an embodiment of the present disclosure provides a method and device for automatically executing an operation of a mobile terminal, and a mobile terminal, which can determine a current state of a mobile terminal according to an internal temperature, a current environment temperature and current moving/stationary situation information of the mobile terminal, to automatically execute a corresponding preset operation, such that the mobile terminal can automatically adjust related settings according to different scenarios. [0028]FIG. 1 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 1 of the present disclosure. As illustrated in FIG. 1, the method includes the following steps S100-S104. [0029]In step S100, current moving/stationary situation information, an internal temperature and a current environment temperature of a mobile terminal are acquired. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. [0030]In step S102, a current state of the mobile terminal is determined according to the current moving/stationary situation information, the internal temperature and the current environment temperature. [0031]In step S104, a preset operation is executed according to the current state. [0032]In the method for automatically executing an operation of a mobile terminal, by acquiring the moving/stationary situation that the mobile terminal is stationary or moving at current and the internal temperature and the current environment temperature of the mobile terminal, the current state of the mobile terminal is determined and thus a preset operation corresponding to the current state is executed. [0033]According to the method for automatically executing an operation of a mobile terminal provided by the embodiment of the present disclosure, since the current state of the mobile terminal can be determined according to the current moving/stationary situation, the internal temperature and the current ambient temperature of the mobile terminal and the corresponding preset operation is executed, the mobile terminal can automatically adjust related settings according to different scenarios. [0034]In one specific embodiment of the present disclosure, the step S100 may specifically include the following operations. A movement acceleration of the mobile terminal is acquired through an acceleration sensor. The current moving/stationary situation information of the mobile terminal is acquired according to the movement acceleration. [0035]The mobile terminal may acquire the movement acceleration of the mobile terminal through the acceleration sensor and determine that the mobile terminal is stationary or moving according to the movement acceleration. For example, if the times of movement of the mobile terminal and a time interval of movement at each time detected by the acceleration sensor within a period of time t are smaller than preset thresholds, it may be determined that the mobile terminal is stationary. The purpose of doing that is to avoid the situation that certain vibration of the mobile terminal is mistakenly considered as the movement of the mobile terminal. For example, when the mobile terminal is put on a table and the mobile terminal is stationary, if the table is touched and shakes, the acceleration sensor will detect movement acceleration within short time. If it is determined that the mobile terminal is moving according to the movement acceleration, misjudgment will be caused. To avoid similar situations, a threshold may be set. [0036]In one specific embodiment of the present disclosure, the step S100 may specifically include the following operations. The internal temperature of the mobile terminal is acquired through a first temperature sensor arranged inside the mobile terminal. The current environment temperature of the mobile terminal is acquired through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0037]The mobile terminal may acquire the internal temperature and the current environment temperature of the mobile terminal through temperature sensors. Specifically, the internal temperature of the mobile terminal is acquired through a temperature sensor arranged inside the mobile terminal. The temperature sensor may be a temperature sensor self-contained by a chip used by the mobile terminal, and may also be a temperature sensor which is separately arranged. The current environment temperature is acquired through a temperature sensor arranged on the surface of the housing of the mobile terminal. [0038]In one specific embodiment of the present disclosure, the second temperature sensor is a plurality of second temperature sensors. The operation of acquiring the current environment temperature of the mobile terminal through the second temperature sensors includes the following operations. A plurality of environment temperatures are acquired through the plurality of second temperature sensors. An expected value of the plurality of environment temperatures is acquired as the current environment temperature. [0039]To enable the acquired current environment temperature to be more accurate, the current environment temperature may be obtained through temperatures acquired by a plurality of temperature sensors arranged on the surface of the housing of the mobile terminal. Specifically, the distribution of the temperature values measured by the plurality of temperature sensors may be analyzed and an expected value of the plurality of temperature values is acquired as the current environment temperature. [0040]In a specific embodiment of the present disclosure, the step S102 may specifically include the following operations. When the mobile terminal is stationary at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in an exposed environment and a stationary state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset first temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in a hidden environment and a stationary state. When the mobile terminal is moving at current, if the difference between the internal temperature and the current environment temperature is smaller than a preset second temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in an exposed environment and moving state; if the difference between the internal temperature and the current environment temperature is greater than or equal to the preset second temperature threshold and is smaller than or equal to a preset third temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in a shallow hidden environment and moving state; and if the difference between the internal temperature and the current environment temperature is greater than the preset third temperature threshold, the current state of the mobile terminal is determined as that the mobile terminal is in a deep hidden environment and moving state. [0041]When the mobile terminal is stationary, environments in which the mobile terminal is located may be divided into two types. Herein, a first type is exposed environment, i.e., the mobile terminal is placed in an open space, e.g., on a tabletop; and a second type is hidden environment, i.e., the mobile terminal is placed in a closed space, e.g., in a drawer, a bag or a pocket of clothes which are not put on by a user. When the mobile terminal is in a hidden environment, since heat is not easy to dissipate in the closed space, the internal temperature and the current environment temperature of the mobile terminal have a great difference. Therefore, the environment in which the mobile terminal is located can be determined according to the difference between the internal temperature and the current environment temperature of the mobile terminal. [0042]When the mobile terminal is moving, environments in which the mobile terminal is located may be divided into three types. Herein, a first type is an exposed environment, i.e., the mobile terminal is placed in an open space, e.g., on a tabletop; a second type is a deep hidden environment, i.e., the mobile terminal is placed in a pocket of clothes which are put on by a user; and a third type is a shallow hidden environment, i.e., the mobile terminal is placed in other closed spaces, e.g., a bag. When the mobile terminal is placed in the pocket of the clothes which are put on by the user, since the mobile terminal is carried with the user, the automatic operation executed by the mobile terminal may be distinguished from the automatic operation executed when the mobile terminal is in other closed spaces. When the mobile terminal is in a deep hidden environment, i.e., the pocket of the clothes which are put on by the user, since the mobile terminal is carried with the user, the current environment temperature of the mobile terminal will be influenced by body temperature of the user; and simultaneously, since the internal space of the pocket is small, at this moment the difference between the internal temperature and the current environment temperature of the mobile terminal is greater than the difference therebetween when the mobile terminal is in a shallow hidden environment. Therefore, the environment in which the mobile terminal is located can be determined according to the difference between the internal temperature and the current environment temperature of the mobile terminal. [0043]In the method for automatically executing an operation of a mobile terminal provided by the embodiment of the present disclosure, the current state of the mobile terminal is determined by comparing the difference between the internal temperature and the current environment temperature of the mobile terminal with the preset first temperature threshold, second temperature threshold or third temperature threshold. However, actually the difference between the internal temperature and the current environment temperature of the mobile terminal will be influenced by factors a current CPU use rate and a standby current magnitude of the mobile terminal. Therefore, if the adopted preset first temperature threshold, second temperature threshold or third temperature threshold is a fixed value, a judgment result will be caused to be inaccurate. [0044]Therefore, in an exemplary embodiment, in the method for automatically executing an operation of a mobile terminal, before the current state of the mobile terminal is determined according to the current moving/stationary situation information, the internal temperature and the current environment temperature, the method further includes the following step. The first temperature threshold, the second temperature threshold and the third temperature threshold are respectively determined according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0045]By respectively determining the first temperature threshold, the second temperature threshold and the third temperature threshold according to the current CPU use rate and the standby current magnitude of the mobile terminal, the influence caused by the current CPU use rate and the standby current magnitude of the mobile terminal is avoided and the current state of the mobile terminal can be more accurately determined. [0046]FIG. 2 illustrates a flowchart of a method for automatically executing an operation of a mobile terminal provided by embodiment 2 of the present disclosure. As illustrated in FIG. 2, the method includes the following steps S200-S228. [0047]In step S200, movement information of a mobile terminal is acquired through an acceleration sensor, and an internal temperature and a current environment temperature of the mobile terminal are acquired through temperature sensors. [0048]In step S202, whether the mobile terminal is moving is judged. If yes, step S204 is executed, and if no, step S220 is executed. Specifically, if the movement information detected by the acceleration sensor within a period of time indicates that the mobile terminal is stationary, or the movement information of the mobile terminal detected by the acceleration sensor within such period of time indicates that the mobile terminal is moved but a time interval of movement is smaller than a preset threshold, it is considered that the mobile terminal is stationary. If the movement information detected by the acceleration sensor within a period of time indicates that the mobile terminal is moving, or the movement information of the mobile terminal detected by the acceleration sensor within such period of time indicates that the mobile terminal is moved and the time interval of movement is greater than the preset threshold, it is considered as that the mobile terminal is moving. [0049]In step S204, whether a difference between the internal temperature and the current environment temperature is smaller than a preset first threshold F1 is judged. If yes, step S206 is executed, and if no, step S210 is executed. Herein, the first threshold F1 is a variable which is determined according to a current CPU use rate and a standby current magnitude of the mobile terminal. [0050]In step S206, the mobile terminal is in an exposed environment and is moving, e.g., a user holds the mobile terminal in a hand. [0051]In step S208, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a mute mode. [0052]In step S210, whether the difference between the internal temperature and the current environment temperature is greater than or equal to a preset second threshold F2 is judged. If yes, step S212 is executed, and if no, step S216 is executed. Herein, the second threshold F2 is a variable which is determined according to the current CPU use rate and the standby current magnitude of the mobile terminal. [0053]In step S212, the mobile terminal is in a shallow hidden environment and is moving, e.g., the user places the mobile terminal in a bag backpacked by the user during walking. [0054]In step S214, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a ringing mode and a ring volume magnitude is set. [0055]In step S216, the mobile terminal is in a deep hidden environment and is moving, e.g., the user places the mobile terminal in a pocket of clothes which are put on during walking. [0056]In step S218, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a vibration mode. [0057]In step S220, whether the difference between the internal temperature and the current environment temperature is smaller than a preset third threshold F3 is judged. If yes, step S222 is executed, and if no, step S226 is executed. Herein, the third threshold F3 is a variable which is determined according to the current CPU use rate and the standby current magnitude of the mobile terminal. [0058]In step S222, the mobile terminal is in an exposed environment and is stationary, e.g., the mobile terminal is placed on a table. [0059]In step S224, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a mute mode. [0060]In step S226, the mobile terminal is in a hidden environment and is stationary, e.g., the mobile terminal is placed in a bag or a drawer. [0061]In step S228, the mobile terminal executes a corresponding preset operation, e.g., the mobile terminal is adjusted to be in a ringing mode and a ring volume is set. [0062]An embodiment of the present disclosure further provides a device for automatically executing an operation of a mobile terminal, including an acquisition module, a first determination module and an execution module. The acquisition module is arranged to acquire current moving/stationary situation information, an internal temperature and a current environment temperature of the mobile terminal. Herein, the current moving/stationary situation information of the mobile terminal includes information indicating that the mobile terminal is stationary at current or the mobile terminal is moving at current. The first determination module is arranged to determine a current state of the mobile terminal according to the current moving/stationary situation information, the internal temperature and the current environment temperature. The execution module is arranged to execute a preset operation according to the current state. [0063]In the device for automatically executing an operation of a mobile terminal, the acquisition module includes a first acquisition sub-module and a second acquisition sub-module. The first acquisition sub-module is arranged to acquire a movement acceleration of the mobile terminal through an acceleration sensor. The second acquisition sub-module is arranged to acquire the current moving/stationary situation information of the mobile terminal according to the movement acceleration. [0064]In the device for automatically executing an operation of a mobile terminal, the acquisition module includes a third acquisition sub-module and a fourth acquisition sub-module. The third acquisition sub-module is arranged to acquire the internal temperature of the mobile terminal through a first temperature sensor arranged inside the mobile terminal. The fourth acquisition sub-module is arranged to acquire the current environment temperature of the mobile terminal through a second temperature sensor arranged on a surface of a housing of the mobile terminal. [0065]In the device for automatically executing an operation of a mobile terminal, the second temperature sensor is a plurality of second temperature sensors; and the fourth acquisition sub-module includes a first acquisition unit and a second acquisition unit. The first acquisition unit is arranged to acquire a plurality of environment temperatures through the plurality of second temperature sensors. The second acquisition unit is arranged to acquire an expected value of the plurality of environment temperatures as the current environment temperature. [0066]In the device for automatically executing an operation of a mobile terminal, the first determination module includes a first determination sub-module and a second determination sub-module. [0067]The first determination sub-module is arranged to, when the mobile terminal is moving at current, if a difference between the internal temperature and the current environment temperature is smaller than a preset first temperature threshold, determine the current state of the mobile terminal as that the mobile terminal is in an exposed environment and a moving state; if the(String), 技术领域 [0001] 本发明涉及一种终端应用技术,尤其涉及一种移动终端的操作。 背景 [0002] 人们在日常生活中使用手机时,会根据不同的场景设置不同幅度的震动或音量。 在传统的功能手机上,这种模式被称为场景模式。 不过,该功能在智能手机上逐渐淡出,但用户的需求并没有因此而改变。 例如,当用户在办公室时,需要调低音量; 手机放在口袋或包里时,为了避免漏接电话和短信,需要调高手机音量。 并且当用户睡觉时,需要关闭音量和振动或者开启飞行模式。 在日常生活中,由于用户忘记调节音量、振动等,给手机用户带来了极大的不便。 概括 [0003] 本发明实施例提供一种自动执行移动终端操作的方法、装置及移动终端,能够根据内部温度、当前环境温度和当前移动/静止确定移动终端的当前状态。 移动终端的情境信息,自动执行相应的预设操作,使移动终端能够根据不同的场景自动调整相关设置。 [0004] 根据本公开的一个方面,本公开的实施例提供了一种自动执行移动终端的操作的方法。 该方法包括:获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度,其中,移动终端的当前移动/静止情况信息包括移动终端当前处于静止状态或当前处于静止状态的信息。 移动终端在当前移动; 根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态; 根据当前状态执行预设操作。 [0005] 优选地,获取移动终端当前的移动/静止情况信息包括: 通过加速度传感器获取移动终端的移动加速度; 根据移动加速度获取移动终端当前的移动/静止情况信息。 [0006] 在一个示例性实施例中,获取移动终端的内部温度和当前环境温度包括: 通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度; 通过设置在移动终端外壳表面的第二温度传感器获取移动终端当前的环境温度。 [0007] 在一个示例性实施例中,第二温度传感器是多个第二温度传感器; 通过设置在移动终端机壳表面的第二温度传感器获取移动终端当前的环境温度包括: 通过多个第二温度传感器获取多个环境温度; 获取多个环境温度的期望值作为当前环境温度。 [0008] 在示例性实施例中,根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态包括以下操作。 [0009]当移动终端当前移动时,如果内部温度与当前环境温度的差值小于预设的第一温度阈值,则确定移动终端当前状态为暴露环境 和移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值且小于或等于预设的第二温度阈值,则确定移动终端的当前状态为 终端处于浅层隐藏环境和移动状态; 如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则确定移动终端当前的状态为移动终端处于深度隐藏环境和移动状态。 [0010] 当移动终端当前静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则判断移动终端当前状态为暴露环境 和静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端的当前状态为移动终端处于隐藏环境和静止状态。 [0011] 在一个示例性实施例中,在根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态之前,该方法还包括:分别确定第一温度阈值、第二温度阈值和 第三温度阈值根据移动终端当前的CPU使用率和待机电流大小。 [0012] 根据本发明的另一方面,本发明实施例还提供一种自动执行移动终端操作的装置。 该装置包括获取模块、第一判断模块和执行模块。 获取模块用于获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 第一确定模块用于根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态。 执行模块用于根据当前状态执行预设操作。 [0013] 在一个示例性实施例中,获取模块包括第一获取子模块和第二获取子模块。 第一获取子模块用于通过加速度传感器获取移动终端的运动加速度。 第二获取子模块用于根据移动加速度获取移动终端当前的移动/静止情况信息。 [0014] 在一个示例性实施例中,获取模块包括第三获取子模块和第四获取子模块。 第三获取子模块用于通过移动终端内部的第一温度传感器获取移动终端的内部温度。 第四获取子模块用于通过设置在移动终端机壳表面的第二温度传感器获取移动终端当前的环境温度。 [0015]在示例性实施例中,第二温度传感器是多个第二温度传感器。 第四获取子模块包括第一获取单元和第二获取单元。 第一获取单元用于通过多个第二温度传感器获取多个环境温度。 第二获取单元用于获取多个环境温度的期望值作为当前环境温度。 [0016] 在一个示例性实施例中,第一确定模块包括第一确定子模块和第二确定子模块。 [0017] 第一判断子模块,用于在移动终端当前移动时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则判断移动终端当前的状态为: 移动终端处于暴露环境和移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值且小于或等于预设的第二温度阈值,则确定移动终端的当前状态为移动终端 处于浅隐环境和运动状态; 如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则判断移动终端当前的状态为移动终端处于深度隐藏环境和移动状态。 [0018] 第二确定子模块,用于当移动终端当前静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则确定移动终端当前状态为 移动终端处于暴露环境和静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端当前的状态为移动终端处于隐藏环境和静止状态。 [0019] 优选地,该装置还包括: 第二确定模块,用于根据移动终端当前的CPU使用率和待机电流大小分别确定第一温度阈值、第二温度阈值和第三温度阈值。 [0020] 根据本发明的另一方面,本发明实施例还提供了一种移动终端,包括:内部温度传感器、外部温度传感器、加速度传感器和用于移动终端操作的汽车执行装置。 这里,内部温度传感器用于获取移动终端的内部温度。 外部温度传感器用于获取移动终端的当前环境温度。 加速度传感器用于获取移动终端当前的移动/静止情况信息。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 [0021] 根据本发明的另一方面,本发明实施例还提供了一种计算机程序及其载体。 计算机程序包括程序指令,当程序指令被移动终端执行时,移动终端可以执行自动执行移动终端操作的方法。 [0022] 本发明实施例的上述技术方案具有以下有益效果: [0023]本发明实施例提供的移动终端自动执行操作的方法和装置,以及移动终端可以根据内部温度、当前环境温度和当前移动/静止确定移动终端的当前状态 移动终端的情境信息,自动执行相应的预设操作,使移动终端能够根据不同的场景自动调整相关设置。 附图说明 [0024] 图1为本发明实施例一提供的一种自动执行移动终端操作的方法的流程图。 [0025] 图2为本发明实施例二提供的一种自动执行移动终端操作的方法流程图。 详细说明 [0026] 下面结合附图对本发明实施例进行详细说明。 需要说明的是,本发明实施例和实施例中的特征可以在不冲突的情况下相互自由组合。 尽管在流程图中示出了逻辑顺序,但是在某些情况下,可以根据与此处的顺序不同的顺序来执行示出或描述的步骤。 [0027] 针对相关技术中终端用户根据不同的场景,经常忘记调整移动终端的设置而导致漏接电话的情况,本发明实施例提供了一种自动执行移动终端操作的方法及装置, 移动终端,可根据移动终端的内部温度、当前环境温度和当前移动/静止情况信息确定移动终端的当前状态,自动执行相应的预设操作,使移动终端能够 根据不同场景自动调整相关设置。 [0028] 图1为本发明实施例一提供的一种自动执行移动终端操作的方法的流程图。 如图1所示,该方法包括以下步骤S 100 -S 104 . [0029] 在步骤 S 100 ,获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 [0030] 在步骤 S 102 ,根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态。 [0031] 在步骤 S 104 ,根据当前状态执行预设操作。 [0032] 一种自动执行移动终端操作的方法,通过获取移动终端当前静止或移动的移动/静止情况以及移动终端的内部温度和当前环境温度,获取移动终端的当前状态。 终端被确定,从而执行与当前状态对应的预设操作。 [0033] 根据本发明实施例提供的自动执行移动终端操作的方法,由于可以根据当前移动/静止情况、内部温度和当前环境温度确定移动终端的当前状态。 并执行相应的预设操作,移动终端可以根据不同的场景自动调整相关设置。 [0034] 在本发明的一个具体实施例中,步骤S 100具体可以包括以下操作。 通过加速度传感器获取移动终端的运动加速度。 根据移动加速度获取移动终端当前的移动/静止情况信息。 [0035] 移动终端可以通过加速度传感器获取移动终端的移动加速度,并根据移动加速度判断移动终端是静止的还是移动的。 例如,如果移动终端的移动次数和加速度传感器在一段时间t内检测到的每次移动的时间间隔小于预设阈值,则可以确定移动终端是静止的。 这样做的目的是为了避免将移动终端的某些振动误认为是移动终端的移动。 例如,当移动终端放在桌子上且移动终端静止时,如果桌子被触摸和晃动,加速度传感器将在短时间内检测到运动加速度。 如果根据移动加速度判断移动终端正在移动,则会造成误判。 为了避免类似情况,可以设置阈值。 [0036] 在本发明的一个具体实施例中,步骤S 100 具体可以包括以下操作。 通过设置在移动终端内部的第一温度传感器获取移动终端的内部温度。 移动终端当前的环境温度是通过设置在移动终端外壳表面的第二温度传感器获取的。 [0037] 移动终端可以通过温度传感器获取移动终端的内部温度和当前环境温度。 具体地,通过设置在移动终端内部的温度传感器获取移动终端的内部温度。 温度传感器可以是移动终端使用的芯片自带的温度传感器,也可以是单独设置的温度传感器。 当前环境温度是通过设置在移动终端外壳表面的温度传感器获取的。 [0038] 在本发明的一个具体实施例中,所述第二温度传感器为多个第二温度传感器。 通过第二温度传感器获取移动终端当前环境温度的操作包括以下操作。 通过多个第二温度传感器获取多个环境温度。 获取多个环境温度的期望值作为当前环境温度。 [0039] 为了使获取的当前环境温度更加准确,可以通过设置在移动终端外壳表面的多个温度传感器获取的温度来获取当前环境温度。 具体地,可以分析多个温度传感器测量的温度值的分布,获取多个温度值的期望值作为当前环境温度。 [0040] 在本发明的一个具体实施例中,步骤S 102具体可以包括以下操作。 当移动终端当前静止时,如果内部温度与当前环境温度的差值小于预设的第一温度阈值,则确定移动终端的当前状态为处于暴露环境中,并且 静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值,则确定移动终端的当前状态为移动终端处于隐藏环境和静止状态。 当移动终端在当前移动时,如果内部温度与当前环境温度的差值小于预设的第二温度阈值,则确定移动终端的当前状态为移动终端处于暴露环境中, 移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第二温度阈值且小于或等于预设的第三温度阈值,则确定移动终端的当前状态为移动终端 处于浅隐环境和运动状态; 若内部温度与当前环境温度的差值大于预设的第三温度阈值,则确定移动终端当前状态为深隐环境移动状态。 [0041] 当移动终端静止时,移动终端所处的环境可以分为两种。 这里,第一类是暴露环境,即移动终端放置在开放空间,例如桌面上; 第二种是隐蔽环境,即将移动终端放置在封闭的空间内,如抽屉、包或用户不穿的衣服口袋中。 当移动终端处于隐蔽环境时,由于在封闭空间内热量不易散发,因此移动终端内部温度与当前环境温度存在较大差异。 因此,可以根据移动终端内部温度与当前环境温度的差值来确定移动终端所处的环境。 [0042] 当移动终端在移动时,移动终端所处的环境可以分为三种。 这里,第一类是暴露环境,即移动终端放置在空旷的空间,例如桌面上; 第二种是深度隐蔽环境,即移动终端放置在用户穿上的衣服口袋中。 第三种是浅隐蔽环境,即移动终端放置在其他封闭空间,例如包中。 当移动终端放置在用户所穿衣服的口袋中时,由于移动终端是随身携带的,因此移动终端执行的自动操作可以与移动终端执行的自动操作区分开来。 在其他封闭空间。 当移动终端处于较深的隐蔽环境,即用户穿上的衣服口袋时,由于移动终端是随身携带的,因此移动终端当前的环境温度会受到体温的影响 用户的; 同时,由于口袋内部空间较小,此时移动终端内部温度与当前环境温度的差值大于移动终端处于浅隐藏环境时的差值。 因此,可以根据移动终端内部温度与当前环境温度的差值来确定移动终端所处的环境。 [0043]本发明实施例提供的一种自动执行移动终端操作的方法,通过将移动终端内部温度与当前环境温度的差值与预设值进行比较,确定移动终端的当前状态。 第一温度阈值、第二温度阈值或第三温度阈值。 然而,实际上移动终端内部温度与当前环境温度的差异会受到移动终端当前CPU使用率和待机电流大小等因素的影响。 因此,如果采用预设的第一温度阈值、第二温度阈值或第三温度阈值为固定值,将导致判断结果不准确。 [0044] 因此,在示例性实施例中,在自动执行移动终端操作的方法中,在根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态之前, 该方法还包括以下步骤。 第一温度阈值、第二温度阈值和第三温度阈值分别根据移动终端的当前CPU使用率和待机电流大小确定。 [0045] 通过根据移动终端当前CPU使用率和待机电流大小分别确定第一温度阈值、第二温度阈值和第三温度阈值,当前CPU使用率和待机电流大小对移动终端的影响 避免了移动终端,可以更准确的判断移动终端的当前状态。 [0046] 图2为本发明实施例二提供的一种自动执行移动终端操作的方法流程图。 如图2所示,该方法包括以下步骤S 200 -S 228 . [0047] 在步骤 S 200 ,通过加速度传感器获取移动终端的运动信息,通过温度传感器获取移动终端的内部温度和当前环境温度。 [0048] 在步骤 S 202 ,判断移动终端是否在移动。 如果是,步骤 S 204 被执行,如果没有,步骤S 220 被执行。 具体地,如果加速度传感器在一段时间内检测到的移动信息表明移动终端是静止的,或者加速度传感器在这段时间内检测到移动终端的移动信息表明移动终端是移动的,但是 移动的时间间隔小于预设阈值,则认为移动终端静止。 如果加速度传感器在一段时间内检测到的移动信息表明移动终端正在移动,或者加速度传感器在该时间段内检测到移动终端的移动信息表明移动终端移动了,则该时间 移动间隔大于预设阈值,则认为移动终端正在移动。 [0049] 在步骤 S 204 ,内部温度与当前环境温度的差值是否小于预设的第一阈值F 1 被判断。 如果是,步骤 S 206 被执行,如果没有,步骤S 210 被执行。 其中,第一阈值 F 1 是根据移动终端当前CPU使用率和待机电流大小确定的变量。 [0050] 在步骤 S 206 ,移动终端处于暴露环境中并且正在移动,例如,用户将移动终端握在手中。 [0051] 在步骤 S 208 ,移动终端执行相应的预设操作,例如将移动终端调整为静音模式。 [0052] 在步骤 S 210 ,内部温度与当前环境温度的差值是否大于或等于预设的第二阈值F 2被判断。 如果是,步骤 S 212 被执行,如果没有,步骤S 216 被执行。 这里,第二阈值 F 2 是根据当前CPU使用率和移动终端的待机电流大小确定的变量。 [0053] 在步骤 S 212 ,移动终端处于浅层隐蔽环境中,正在移动,例如,用户在行走时将移动终端放在用户背包的包中。 [0054] 在步骤 S 214 ,移动终端执行相应的预设操作,例如将移动终端调整为响铃模式,设置响铃音量大小。 [0055] 在步骤 S 216 ,移动终端处于深隐环境中,并且正在移动,例如,用户将移动终端放置在行走时穿上的衣服口袋中。 [0056] 在步骤 S 218 ,移动终端执行相应的预设操作,例如将移动终端调整为振动模式。 [0057] 在步骤 S 220 ,内部温度与当前环境温度的差值是否小于预设的第三阈值F 3 被判断。 如果是,步骤 S 222 被执行,如果没有,步骤S 226 被执行。 这里,第三阈值 F 3 是根据当前CPU使用率和移动终端的待机电流大小确定的变量。 [0058] 在步骤 S 222 ,移动终端处于暴露环境中并且是静止的,例如,移动终端被放置在桌子上。 [0059] 在步骤 S 224 ,移动终端执行相应的预设操作,例如将移动终端调整为静音模式。 [0060] 在步骤 S 226 ,移动终端处于隐蔽环境中,是静止的,例如,移动终端被放置在包或抽屉中。 [0061] 在步骤 S 228 ,移动终端执行相应的预设操作,例如,将移动终端调整为响铃模式并设置响铃音量。 [0062] 本发明实施例还提供一种自动执行移动终端操作的装置,包括获取模块、第一判断模块和执行模块。 获取模块用于获取移动终端当前的移动/静止情况信息、内部温度和当前环境温度。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 第一确定模块用于根据当前移动/静止情况信息、内部温度和当前环境温度确定移动终端的当前状态。 执行模块用于根据当前状态执行预设操作。 [0063] 在自动执行移动终端操作的装置中,获取模块包括第一获取子模块和第二获取子模块。 第一获取子模块用于通过加速度传感器获取移动终端的运动加速度。 第二获取子模块用于根据移动加速度获取移动终端当前的移动/静止情况信息。 [0064] 在自动执行移动终端操作的装置中,获取模块包括第三获取子模块和第四获取子模块。 第三获取子模块用于通过移动终端内部的第一温度传感器获取移动终端的内部温度。 第四获取子模块用于通过设置在移动终端机壳表面的第二温度传感器获取移动终端当前的环境温度。 [0065]在移动终端自动执行操作的装置中,第二温度传感器为多个第二温度传感器。 第四获取子模块包括第一获取单元和第二获取单元。 第一获取单元用于通过多个第二温度传感器获取多个环境温度。 第二获取单元用于获取多个环境温度的期望值作为当前环境温度。 [0066] 在自动执行移动终端操作的装置中,第一判断模块包括第一判断子模块和第二判断子模块。 [0067] 第一判断子模块,用于在移动终端当前移动时,若内部温度与当前环境温度的差值小于预设的第一温度阈值,则判断移动终端当前的状态为: 移动终端处于暴露环境和移动状态; 如果内部温度与当前环境温度的差值大于或等于预设的第一温度阈值且小于或等于预设的第二温度阈值,则确定移动终端的当前状态为移动终端 处于浅隐环境和运动状态; 如果内部温度与当前环境温度的差值大于预设的第二温度阈值,则判断移动终端当前的状态为移动终端处于深度隐藏环境和移动状态。 [0068] 第二判断子模块,用于当移动终端当前静止时,若内部温度与当前环境温度的差值小于预设的第三温度阈值,则判断移动终端当前的状态为 移动终端处于暴露环境和静止状态; 如果内部温度与当前环境温度的差值大于或等于预设的第三温度阈值,则确定移动终端当前的状态为移动终端处于隐藏环境和静止状态。 [0069] 在自动执行移动终端操作的装置中,该装置还包括第二确定模块,用于根据当前CPU使用率和待机电流分别确定第一温度阈值、第二温度阈值和第三温度阈值。 移动终端的规模。 [0070] 本发明实施例还提供一种移动终端,包括内置温度传感器、外置温度传感器、加速度传感器和用于移动终端运行的汽车执行装置。 内部温度传感器用于获取移动终端的内部温度。 外部温度传感器用于获取移动终端的当前环境温度。 加速度传感器用于获取移动终端当前的移动/静止情况信息。 这里,移动终端当前的移动/静止情况信息包括移动终端当前静止或移动终端当前移动的信息。 [0071] 本领域普通技术人员可以理解,上述方法中的全部或部分步骤可以通过程序指令相关硬件来完成,该程序可以存储在只读存储器等计算机可读存储介质中。 等等。 或者,上述实施例中的全部或部分步骤也可以采用一个或多个集成电路来实现。 相应地,上述实施例中的各个模块/单元可以通过硬件实现,也可以通过软件功能模块实现。 本公开不限于任何特定形式的硬件和软件的组合。 [0072]当然,本发明还可以有其他各种环境。 本领域的技术人员可以在不脱离本发明的原则和实质的情况下,根据本发明进行各种相应的修改和变化。 但是,这种相应的修改和变化仍应包含在本发明权利要求的保护范围之内。 工业适用性 [0073] 根据本发明实施例提供的移动终端自动执行操作的方法、装置及移动终端,通过获取当前移动/静止情况信息、内部温度,确定移动终端的当前状态。 移动终端当前的环境温度; 根据当前状态执行预设操作,使移动终端可以根据不同场景自动调整相关设置。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105338167A(String), CN105338167B(String), EP3179704A1(String), EP3179704A4(String), EP3179704B1(String), US10063685B2(String), US20170272567A1(String), WO2015154446A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105338167A(String), CN105338167B(String), EP3179704A1(String), EP3179704A4(String), EP3179704B1(String), US10063685B2(String), US20170272567A1(String), WO2015154446A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105338167A(String), CN105338167B(String), EP3179704A1(String), EP3179704A4(String), EP3179704B1(String), US10063685B2(String), US20170272567A1(String), WO2015154446A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), CN105338167A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270773(Integer), CN105338167B(String), 1047140(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), EP3179704A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), EP3179704A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), EP3179704B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), US10063685B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), US20170272567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270773(Integer), WO2015154446A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN105338167B(String), CN105338167B(String), 1588867200(Integer), 270773(Integer), 185057(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185943(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185943(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.731 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185943(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185943(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:51.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185943(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130104163A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Encryption method for television service of mobile terminal, mobile terminal and server(String), 移动终端电视业务加密方法、移动终端及服务器(String), US20130104163A1(String), The disclosure provides an encryption method for a television service of a mobile terminal, a mobile terminal and a server. The method comprises: a mobile terminal ordering and obtaining a program that has not been subscribed; the mobile terminal encrypting the program to shield a part of data of the program; and the mobile terminal playing the program that is encrypted. The encryption method for the television service of the mobile terminal, the mobile terminal and the server provided in the disclosure can encrypt the program, which is ordered but has not been subscribed by the user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program, thus certain experience can be enjoyed by the user, and the content of the program is protected.(String), 本发明提供一种移动终端的电视业务加密方法、移动终端及服务器。 该方法包括:移动终端订购并获取未订阅的节目; 移动终端对程序进行加密,以屏蔽程序的部分数据; 移动终端播放加密后的节目。 本发明提供的移动终端电视业务加密方法、移动终端和服务器可以在移动终端侧或服务器侧对用户已点播但尚未订阅的节目进行加密,从而 将节目的部分数据屏蔽后播放节目,用户可以享受到一定的体验,节目内容受到保护。(String), US13/700954(String), 1288800000(Integer), US20130104163A1(String), 1366819200(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 11(Integer), EP2079228A1 | US20040019787A1 | US20050070248A1 | US20070092082A1 | US20070201695A1 | US20080134232A1 | US20100333130A1 | US20110019816A1 | US4225884A | WO2006134517A2 | WO2008053576A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185944(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2569edae4fd143ce9bfe60aec5473c89.png(String), 185944(Integer), 2569edae4fd143ce9bfe60aec5473c89.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.707 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.707 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Encryption method for television service of mobile terminal, mobile terminal and server(String), 移动终端电视业务加密方法、移动终端及服务器(String), US20130104163A1(String), The disclosure provides an encryption method for a television service of a mobile terminal, a mobile terminal and a server. The method comprises: a mobile terminal ordering and obtaining a program that has not been subscribed; the mobile terminal encrypting the program to shield a part of data of the program; and the mobile terminal playing the program that is encrypted. The encryption method for the television service of the mobile terminal, the mobile terminal and the server provided in the disclosure can encrypt the program, which is ordered but has not been subscribed by the user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program, thus certain experience can be enjoyed by the user, and the content of the program is protected.(String), 本发明提供一种移动终端的电视业务加密方法、移动终端及服务器。 该方法包括:移动终端订购并获取未订阅的节目; 移动终端对程序进行加密,以屏蔽程序的部分数据; 移动终端播放加密后的节目。 本发明提供的移动终端电视业务加密方法、移动终端和服务器可以在移动终端侧或服务器侧对用户已点播但尚未订阅的节目进行加密,从而 将节目的部分数据屏蔽后播放节目,用户可以享受到一定的体验,节目内容受到保护。(String), US13/700954(String), 1288800000(Integer), US20130104163A1(String), 1366819200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 11(Integer), EP2079228A1 | US20040019787A1 | US20050070248A1 | US20070092082A1 | US20070201695A1 | US20080134232A1 | US20100333130A1 | US20110019816A1 | US4225884A | WO2006134517A2 | WO2008053576A1(String), \20230420\2569edae4fd143ce9bfe60aec5473c89.png(String), 16(Integer), 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 1. An encryption method for a television service of a mobile terminal, comprising:a mobile terminal ordering and obtaining a program that has not been subscribed;the mobile terminal encrypting the program to shield a part of data of the program; andthe mobile terminal playing the program that is encrypted.(String), 1、一种移动终端电视业务的加密方法,包括:移动终端点播获取未订阅节目;移动终端对节目进行加密,屏蔽节目的部分数据;和移动终端播放加密后的节目。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 2. The encryption method for the television service of the mobile terminal according to claim 1, wherein the step of the mobile terminal ordering and obtaining the program that has not been subscribed comprises:when ordering the program that has not been subscribed, the mobile terminal sending an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; anddownloading and obtaining the program with the decryption key.(String), 2.根据权利要求1所述的移动终端电视业务的加密方法,其中移动终端点播并获取未订阅节目的步骤包括:在点播未订阅的节目时,移动终端发送移动终端的识别码和移动终端用户识别卡的卡号,获取节目的解密密钥。和下载并获取带有解密密钥的程序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 3. The encryption method for the television service of the mobile terminal according to claim 1, wherein the identification code of the mobile terminal is a model number of the mobile terminal.(String), 3.根据权利要求1所述的移动终端电视业务的加密方法,其中移动终端的识别码为移动终端的型号。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 4. The encryption method for the television service of the mobile terminal according to claim 1, wherein the step of encrypting the program to shield a part of data of the program comprises:creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/orperforming audio mixing on a part of audio data of the program.(String), 4.根据权利要求1所述的移动终端电视业务的加密方法,其中对程序进行加密以屏蔽程序的部分数据的步骤包括:建立至少一色彩干扰区,并将该至少一色彩干扰区覆盖于节目的部分视频数据上;和/或对节目的部分音频数据进行混音。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 5. (canceled)6. (canceled)7. (canceled)8. (canceled)9. An encryption method for a television service of a mobile terminal, comprising:when a mobile terminal orders a program that has not been subscribed, a server encrypting the program to shield a part of data of the program, and creating a new channel for the program that is encrypted; andthe server sending information about the new channel and a decryption key to the mobile terminal.(String), 5.(已取消)6.(已取消)7.(已取消)8.(已取消)9、一种移动终端电视业务的加密方法,包括:当移动终端点播未订阅的节目时,服务器对节目进行加密,屏蔽节目的部分数据,并为加密后的节目创建新的频道。和服务器向移动终端发送新频道信息和解密密钥。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 10. The encryption method for the television service of the mobile terminal according to claim 9, wherein the step of encrypting the program to shield a part of data of the program comprises:creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/orperforming audio mixing on a part of audio data of the program.(String), 10.根据权利要求9所述的移动终端电视业务的加密方法,其中对程序进行加密以屏蔽程序的部分数据的步骤包括:建立至少一色彩干扰区,并将该至少一色彩干扰区覆盖于节目的部分视频数据上;和/或对节目的部分音频数据进行混音。11、一种服务器,用于移动终端的电视业务,其中服务器包括:加密模块,用于当移动终端点播未订阅的节目时,对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道;和发送模块,用于向移动终端发送新频道信息和解密密钥。(String), 1(Integer), 5(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 11. A server, used for a television service of a mobile terminal, wherein the server comprises:an encryption module, configured to, when a mobile terminal orders a program that has not been subscribed, encrypt the program to shield a part of data of the program, and create a new channel for the program that is encrypted; anda sending module, configured to send information about the new channel and a decryption key to the mobile terminal.(String), 12.根据权利要求11所述的服务器,其中加密模块还包括:视频干扰单元,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上;和/或音频干扰单元,用于对节目的部分音频数据进行混音。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 12. The server according to claim 11, wherein the encryption module further comprises:a video interference unit, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/oran audio interference unit, configured to perform audio mixing on a part of audio data of the program.(String), 13.根据权利要求2所述的移动终端电视业务的加密方法,其中移动终端的识别码为移动终端的型号。(String), 1(Integer), 7(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 13. The encryption method for the television service of the mobile terminal according to claim 2, wherein the identification code of the mobile terminal is a model number of the mobile terminal.(String), 14.根据权利要求2所述的移动终端电视业务的加密方法,其中对程序进行加密以屏蔽程序的部分数据的步骤包括:建立至少一色彩干扰区,并将该至少一色彩干扰区覆盖于节目的部分视频数据上;和/或对节目的部分音频数据进行混音。(String), 1(Integer), 8(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 14. The encryption method for the television service of the mobile terminal according to claim 2, wherein the step of encrypting the program to shield a part of data of the program comprises:creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/orperforming audio mixing on a part of audio data of the program.(String), 15.(已取消)16.(已取消)(String), 1(Integer), 9(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:52.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185944(Integer), 15. (canceled)16. (canceled)(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185944(Integer), FIELD OF THE INVENTION [0001]The disclosure relates to the technical field of communications, in particular to an encryption method for a television service of a mobile terminal, a mobile terminal and a server. BACKGROUND OF THE INVENTION [0002]A television service of a mobile terminal such as a mobile phone is actually realized in such a way that: a streaming media technology is utilized to launch a mobile terminal television as a data service, and what users see is downloaded video data. In a current encryption method for a television service of a mobile terminal, all television programs provided by a service provider are encrypted, a user is authorized by the service provider only when the user has subscribed a mobile terminal television program, then the user can order the subscribed program. Such encryption method for the television service of the mobile terminal has one defect: usually, users want to watch a part of data of a program before subscribing the program to decide whether to subscribe the program depending on the experience, however, according to the current encryption method for the television service of the mobile terminal, for users who have not subscribed the program, data is completely shielded and cannot be watched, the users cannot have experience of the program, therefore, the popularization of the television service of the mobile phone is limited. SUMMARY OF THE INVENTION [0003]The disclosure provides an encryption method for a television service of a mobile terminal, a mobile terminal and a server, so that the service provider can popularize the television service of the mobile terminal such as a mobile phone better. [0004]The disclosure proposes an encryption method for a television service of a mobile terminal, comprising: a mobile terminal ordering and obtaining a program that has not been subscribed; the mobile terminal encrypting the program to shield a part of data of the program; and the mobile terminal playing the program that is encrypted. [0005]Preferably, the step of the mobile terminal ordering and obtaining the program that has not been subscribed comprises: when ordering the program that has not been subscribed, the mobile terminal sending an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; and downloading and obtaining the program with the decryption key. [0006]Preferably, the identification code of the mobile terminal is a model number of the mobile terminal. [0007]Preferably, the step of encrypting the program to shield a part of data of the program comprises: creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/or, performing audio mixing on a part of audio data of the program. [0008]The disclosure proposes a mobile terminal, comprising: an obtaining module, configured to order and obtain a program that has not been subscribed; an encryption module, configured to encrypt the program to shield a part of data of the program; and a playing module, configured to play the program that is encrypted. [0009]Preferably, the obtaining module comprises: an authentication module, configured to, when ordering the program that has not been subscribed, send an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; and a downloading module, configured to download and obtain the program with the decryption key. [0010]Preferably, the identification code of the mobile terminal is a model number of the mobile terminal. [0011]Preferably, the encryption module comprises: a video interference unit, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit, configured to perform audio mixing on a part of audio data of the program. [0012]The disclosure proposes an encryption method for a television service of a mobile terminal, comprising: when a mobile terminal orders a program that has not been subscribed, a server encrypting the program to shield a part of data of the program, and creating a new channel for the program that is encrypted; and the server sending information about the new channel and a decryption key to the mobile terminal. [0013]Preferably, the step of encrypting the program to shield a part of data of the program comprises: creating at least one color interference region, and covering the at least one color interference region on a part of video data of the program; and/or, performing audio mixing on a part of audio data of the program. [0014]The disclosure proposes a server, used for a television service of a mobile terminal, wherein the server comprises: an encryption module, configured to, when a mobile terminal orders a program that has not been subscribed, encrypt the program to shield a part of data of the program, and create a new channel for the program that is encrypted; and a sending module, configured to send information about the new channel and a decryption key to the mobile terminal. [0015]Preferably, the encryption module further comprises: a video interference unit, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit, configured to perform audio mixing on a part of audio data of the program. [0016]The encryption method for the television service of the mobile terminal, the mobile terminal and the server provided in the disclosure can encrypt the program, which is ordered but has not been subscribed by the user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program, thus certain experience can be enjoyed by the user, and the content of the program is protected, therefore the television service of the mobile terminal such as a mobile phone can be popularized greatly. BRIEF DESCRIPTION OF THE DRAWINGS [0017]FIG. 1 is a flow chart of an embodiment of an encryption method for a television service of a mobile terminal in the disclosure; [0018]FIG. 2 is a structure diagram of an embodiment of a mobile terminal in the disclosure; [0019]FIG. 3 is a structure diagram of an encryption module in an embodiment of the mobile terminal in the disclosure; [0020]FIG. 4 is a flow chart of an embodiment of another encryption method for a television service of a mobile terminal in the disclosure; [0021]FIG. 5 is a structure diagram of an embodiment of a server in the disclosure; and [0022]FIG. 6 is a structure diagram of an encryption module in an embodiment of the server in the disclosure. [0023]The implementation, functions, characteristics and advantages of the disclosure will be further described below with reference to drawings in combination with embodiments. DETAILED DESCRIPTION OF THE EMBODIMENTS [0024]An encryption method for a television service of a mobile terminal, a mobile terminal and a server provided in the embodiments of the disclosure can encrypt a program, which is ordered but has not been subscribed by a user, at the mobile terminal side or the server side so as to play the program after shielding a part of data of the program. [0025]With reference to FIG. 1, a flow chart of an embodiment of an encryption method for a television service of a mobile terminal in the disclosure is shown, and the method comprises the steps as follows. [0026]Step 101: a mobile terminal orders and obtains a program that has not been subscribed. [0027]Preferably, if a program sending end encrypts the program, when ordering the program that has not been subscribed, the mobile terminal can send an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal to the program sending end to obtain a decryption key of the program; and then, the mobile terminal can download the program with the decryption key. [0028]Step 102: the mobile terminal encrypts the program to shield a part of data of the program. [0029]Step 103: the mobile terminal plays the program that is encrypted. [0030]Step 102 is specifically as follows: [0031]at least one color interference region is created, and the at least one color interference region is covered on a part of video data of the program; and/or, perform audio mixing on a part of audio data of the program. [0032]By taking a case that the mobile terminal sends the identification code of the mobile terminal and the card number of the user identification card to the program sending end as an example, the working principle of the encryption method for the television service of the mobile terminal in the preferable embodiment of the disclosure will be described in details below. [0033]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, and sends the identification code of the mobile terminal and the card number of the user identification card of the mobile terminal after establishing a data link with the server; the server locally inquires a user subscription list of the user according to the card number of the user identification card of the mobile terminal, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the server further checks the identification code of the mobile terminal, which is generally the model number of the mobile terminal, and the server will send a decryption key of the program that is ordered by the mobile terminal to the mobile terminal if only the mobile terminal has a specific model number, that is, the mobile terminal has a multimedia information encryption function. [0034]After obtaining the decryption key, the mobile terminal downloads the program that is ordered (program on demand) with the decryption key. [0035]It should be noted that, the mobile terminal may not send the identification code of the mobile terminal and the card number of the user identification card to the program sending end, instead, it directly obtains the program and then judges whether the program is a program that has not been subscribed, if so, the mobile terminal encrypts the program. [0036]After downloading the program that is ordered, the mobile terminal encrypts data of the program to shield a part of data of the program, so that the mobile terminal user can have experience on the program, but cannot watch the complete program. The encryption process is described as follows. [0037]The program downloaded by the mobile terminal comprises video data and audio data. The video data exist in a format of bitmap in the mobile terminal after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the mobile terminal can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0038]wherein ‘MEMSET’ is an encryption function for encrypting the program, and ‘pDATA’ is a temporary variable for indicating the location of the color interference region. [0039]The color interference region is covered at the very center of the video data of the downloaded program, so that, when playing the program, the mobile terminal can play the program normally, but the user can not watch the complete program. [0040]The mobile terminal also can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the audio data downloaded and decoded by the mobile terminal for purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)); }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0041]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0042]The encryption for the video data and the audio data of the download program can be performed alternatively or simultaneously. [0043]Attention should be paid that the encryption for contents of the program by the mobile terminal is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0044]In the method, the program is encrypted at the mobile terminal side, so that the mobile terminal can protect the contents of the television program that has not been subscribed while providing certain experience on the television program for the user, therefore, the television service of the mobile phone is popularized greatly. [0045]With reference to FIG. 2 and FIG. 3, a structure diagram of an embodiment of a mobile terminal in the disclosure is shown, and the mobile terminal comprises: [0046]an obtaining module 01, configured to order and obtain a program that has not been subscribed; [0047]an encryption module 30, configured to encrypt the program to shield a part of data of the program; and [0048]a playing module 40, configured to play the program that is encrypted. [0049]The obtaining module 01 comprises: [0050]an authentication module 10, configured to, when ordering the program that has not been subscribed, send an identification code of the mobile terminal and a card number of a user identification card of the mobile terminal, to obtain a decryption key of the program; and [0051]a downloading module 20, configured to download and obtain the program with the decryption key. [0052]The encryption module 30 further comprises: [0053]a video interference unit 32, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit 33, configured to perform audio mixing on a part of audio data of the program. [0054]The working principle of the mobile terminal in the embodiment will be described in details below. [0055]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, after establishing a data link with the server, the authentication module 10 sends the identification code of the mobile terminal and the card number of the user identification card of the mobile terminal; the server locally inquires a user subscription list of the card number, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the server further checks the identification code of the mobile terminal, which is generally the model number of the mobile terminal, and the server will send a decryption key of the program that is ordered by the mobile terminal to the mobile terminal if only the mobile terminal has a specific model number, that is, the mobile terminal has a multimedia information encryption function. [0056]After the mobile terminal obtains the decryption key, the downloading module 20 downloads the program that is ordered with the decryption key. [0057]After the mobile terminal downloads the program that is ordered, the encryption module 30 encrypts the program to shield a part of data of the program, so that the mobile terminal user can have experience on the program, but cannot watch the complete program. The encryption process is described as follows. [0058]The program downloaded by the mobile terminal comprises video data and audio data. The video data exist in a format of bitmap in the mobile terminal after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the video interference unit 32 can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0059]The video interference unit 32 covers the color interference region at the very center of the video data of the downloaded program so as to complete the encryption. The playing module 40 can play the program, but can not play the complete program, what the user watch is only the program which is coated with the color region in the center. [0060]The audio interference unit 33 of the mobile terminal can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the audio data downloaded and decoded by the mobile terminal for purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0061]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0062]The video interference unit 32 and the audio interference unit 33 can exist separately or simultaneously. [0063]Attention should be paid that the encryption for contents of the program by the mobile terminal is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0064]The program is encrypted by the mobile terminal, so that the mobile terminal can protect the contents of the television program that has not been subscribed while providing certain experience on the television program for the user, therefore, the television service of the mobile phone is popularized greatly. [0065]With reference to FIG. 4, a flow chart of an embodiment of another encryption method for a television service of a mobile terminal in the disclosure is shown, and the method comprises: [0066]Step 201: when a mobile terminal orders a program that has not been subscribed, a server encrypts the program to shield a part of data of the program, and creates a new channel for the program that is encrypted; [0067]Step 202: the server sends information about the channel and a decryption key to the mobile terminal. [0068]Step 201 is specifically as follows: [0069]at least one color interference region is created, and the at least one color interference region is covered on a part of video data of the program; and/or, [0070]perform audio mixing on a part of audio data of the program. [0071]The working principle of the method in the embodiment will be described in details below. [0072]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, and sends a card number of a user identification card to the server after establishing a data link with the server; the server locally inquires a user subscription list of the user according to the card number of the user identification card of the mobile terminal, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the server encrypts the program to shield a part of data of the program, and creates a new channel for the program that is encrypted. The encryption process is described as follows. [0073]Video data of the program provided by the server exists in a format of bitmap after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the server can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0074]The color interference region is covered at the very center of the video data of the program, so as to complete the encryption for the video data of the program. [0075]The server also can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the original audio data for the purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0076]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0077]The encryption for the video data and the audio data can be performed alternatively or simultaneously. [0078]The server creates a new channel for the program that is encrypted and sends information about the new channel and the decryption key of the new channel to the mobile terminal. After receiving the information about the new channel, the mobile terminal automatically switches to the channel and plays the program with the decryption key, wherein the program played by the mobile terminal is a program, a part of data of which are shielded, not a complete program. [0079]Attention should be paid to that the encryption for contents of the program by the server is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0080]In the method, the program is encrypted at the server side serving as a data source, so that the mobile terminal users can have certain experience on a television program that has not been subscribed, and the content of the program is protected, therefore, the television service of the mobile phone is popularized greatly. [0081]With reference to FIG. 5 and FIG. 6, a structure diagram of an embodiment of a server in the disclosure is shown, the server is used for a television service of a mobile terminal, and the server comprises: [0082]an encryption module 50, configured to, when a mobile terminal orders a program that has not been subscribed, encrypt the program to shield a part of data of the program, and create a new channel for the program that is encrypted; and [0083]a sending module 60, configured to send information about the new channel and a decryption key to the mobile terminal. [0084]The encryption module 50 comprises: [0085]a video interference unit 52, configured to create at least one color interference region, and cover the at least one color interference region on a part of video data of the program; and/or, an audio interference unit 53, configured to perform audio mixing on a part of audio data of the program. [0086]The working principle of the server in the embodiment will be described in details below. [0087]A mobile terminal such as a mobile phone initiates an order request of a certain program to the server providing the television service of the mobile terminal, and sends a card number of a user identification card to the server after establishing a data link with the server; the server locally inquires a user subscription list of the user according to the card number of the user identification card of the mobile terminal, so as to obtain whether the card number has subscribed the program, whether the program is a free program and other information, if finding that the card number has not subscribed the program and the program is not a free program, the encryption module 50 encrypts the program to shield a part of data of the program, and creates a new channel for the program that is encrypted. The encryption process is described as follows. [0088]Video data of the program provided by the server exists in a format of bitmap after being decoded, and the data array of the bitmap is a linear array. For example, the size of the video data is 320*240, then the video interference unit 52 can create one color interference region, for example one black rectangular interference region with a size of 160*120. The creation process can be the following sentences:  For (i = 0, i < 240, i++){MEMSET (pDATA + 160, 0, 160*2);} [0089]The video interference unit 52 covers the color interference region at the very center of the video data of the program so as to complete the partial encryption for the data of the program. [0090]The audio interference unit 53 of the server can encrypt audio data to shield a part of the audio data of the program. Other audio data is selectively added into the original audio data for the purpose of audio mixing, the method is described as follows: add other audio data after the audio data,if((sample1 < 0) && (sample2 < 0)) { value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }else{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1)); } [0091]wherein ‘sample1’ is the original audio data, ‘sample2’ is the audio data to be mixed into the original audio data, and ‘value’ is the encrypted audio data. [0092]The video interference unit 52 and the audio interference unit 53 can exist separately or simultaneously. [0093]The encryption module 50 creates a new channel for the program that is encrypted, the sending module 60 sends information about the new channel and the decryption key of the new channel to the mobile terminal. After receiving the information about the new channel, the mobile terminal automatically switches to the channel and plays the program with the decryption key, wherein the program played by the mobile terminal is a program, a part of data of which are shielded, not a complete program. [0094]Attention should be paid to that the encryption for contents of the program by the server is not limited to the above encryption method, and other similar methods with an encryption effect also can be employed. [0095]In the embodiment, the server encrypts the program, so that the mobile terminal can have certain experience on a television program that has not been subscribed, and the content of the program is protected, therefore, the television service of the mobile phone is popularized greatly. [0096]The above contents just describe preferable embodiments of the disclosure and are not intended to limit the patent scope of the disclosure. Any equivalent structure or equivalent flow transform made by utilizing contents of the specification and drawings in the disclosure, or any direct or indirect application in other relevant technical fields, should be comprised within the patent protection scope of the disclosure.(String), 发明领域 [0001] 本发明涉及通信技术领域,尤其涉及一种移动终端电视业务的加密方法、移动终端及服务器。 发明背景 [0002] 手机等移动终端的电视业务实际上是这样实现的:利用流媒体技术推出移动终端电视作为数据业务,用户看到的是下载的视频数据。 现有的移动终端电视业务加密方法中,服务提供商提供的所有电视节目都是加密的,用户只有在订阅了移动终端电视节目后,才能得到服务提供商的授权,用户才能点播。 订阅的节目。 这种移动终端电视服务的加密方式有一个缺陷:用户通常希望在订阅节目之前先观看节目的一部分数据,以根据体验决定是否订阅该节目,但根据目前的 手机电视服务的加密方法,对于没有订阅节目的用户,数据完全屏蔽,无法收看,用户无法体验节目,因此,手机电视服务的普及 是有限的。 发明内容 [0003] 本发明提供了一种移动终端电视业务的加密方法、移动终端及服务器,以便于服务提供商更好地推广手机等移动终端电视业务。 [0004] 本发明提出了一种移动终端电视业务的加密方法,包括:移动终端订购并获取未订阅的节目; 移动终端对节目进行加密,屏蔽节目的部分数据; 移动终端播放加密后的节目。 [0005] 优选地,移动终端点播并获取未订阅节目的步骤包括:移动终端在点播未订阅节目时,发送移动终端的识别码和用户识别卡的卡号。 移动终端,获取程序的解密密钥; 下载并获取带有解密密钥的程序。 [0006] 优选地,移动终端的识别码为移动终端的型号。 [0007] 优选地,对节目进行加密以屏蔽节目的部分数据的步骤包括:创建至少一个颜色干扰区域,并将至少一个颜色干扰区域覆盖在节目的部分视频数据上。 和/或,对节目的部分音频数据进行混音。 [0008] 本发明提出了一种移动终端,包括: 获取模块,用于点播并获取未订阅的节目; 加密模块,用于对程序进行加密,屏蔽程序的部分数据; 播放模块,用于播放加密后的节目。 [0009] 优选地,所述获取模块包括: 鉴权模块,用于在点播未订阅的节目时,发送移动终端的识别码和移动终端用户识别卡的卡号,以获取解密码 程序的关键; 下载模块,用于下载并获取带有解密密钥的程序。 [0010] 优选地,移动终端的识别码为移动终端的型号。 [0011] 优选地,所述加密模块包括: 视频干扰单元,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上。 和/或,音频干扰单元,用于对节目的部分音频数据进行混音。 [0012]本发明提出了一种移动终端电视业务的加密方法,包括:当移动终端点播未订阅的节目时,服务器对该节目进行加密,屏蔽该节目的部分数据,并创建新的频道。 对于加密的程序; 服务器向移动终端发送新频道信息和解密密钥。 [0013] 优选地,对节目进行加密以屏蔽节目的部分数据的步骤包括:创建至少一个颜色干扰区域,并将至少一个颜色干扰区域覆盖在节目的部分视频数据上。 和/或,对节目的部分音频数据进行混音。 [0014] 本发明提出了一种服务器,用于移动终端的电视业务,该服务器包括: 加密模块,用于当移动终端点播未订阅的节目时,对该节目进行加密,以屏蔽部分数据。 程序,并为加密的程序创建一个新的频道; 发送模块,用于向移动终端发送新频道信息和解密密钥。 [0015] 优选地,所述加密模块还包括: 视频干扰单元,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上。 和/或,音频干扰单元,用于对节目的部分音频数据进行混音。 [0016] 本发明提供的移动终端电视业务的加密方法、移动终端及服务器,可以在移动终端侧或服务器侧对用户点播但未订阅的节目进行加密,以便 将节目的部分数据屏蔽后再播放,可以给用户带来一定的体验,节目的内容也得到了保护,可以极大地普及手机等移动终端的电视业务。 . 附图的简要说明 [0017] 图1为本发明移动终端电视业务加密方法的一个实施例的流程图; [0018] 图2为本发明移动终端一个实施例的结构图; [0019] 图3为本发明移动终端实施例中加密模块的结构图; [0020] 图4为本发明另一种移动终端电视业务加密方法的实施例流程图。 [0021] 图5为本发明服务器一个实施例的结构图; 和 [0022] 图6为本发明服务器实施例中加密模块的结构图。 [0023] 下面参照附图并结合实施例对本发明的实施方式、功能、特点和优点作进一步说明。 具体实施方式 [0024] 本发明实施例提供的一种移动终端电视业务的加密方法、移动终端及服务器,能够在移动终端侧或服务器对用户点播未订阅的节目进行加密。 屏蔽部分节目数据后播放节目。 [0025] 参见图1,示出了本发明移动终端电视业务加密方法的一个实施例的流程图,该方法包括以下步骤。 [0026] 步 101 :移动终端点播并获取未订阅的节目。 [0027] 优选地,如果节目发送端对节目进行加密,则移动终端在点播未订阅的节目时,可以向节目发送端发送移动终端的识别码和移动终端用户识别卡的卡号。 结束获取程序的解密密钥; 然后,移动终端可以使用解密密钥下载程序。 [0028] 步 102:移动端对节目进行加密,屏蔽节目的部分数据。 [0029] 步 103 :移动终端播放加密后的节目。 [0030] 步 102 具体如下: [0031] 产生至少一色彩干扰区,且至少一色彩干扰区覆盖于节目的部分视频数据上。 和/或,对节目的部分音频数据进行混音。 [0032] 以移动终端向节目发送端发送移动终端识别码和用户识别卡卡号为例,说明移动终端电视业务加密方法的工作原理。 下面对本发明的优选实施例进行详细说明。 [0033] 手机等移动终端向提供移动终端电视服务的服务器发起某个节目的点播请求,发送移动终端的识别码和移动终端用户识别卡的卡号 与服务器建立数据链接后; 服务器根据移动终端用户识别卡的卡号在本地查询用户的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息, 如果发现该卡号没有订阅节目且该节目不是免费节目,则服务器进一步核对移动终端的识别码,一般为移动终端的型号,服务器会发送解密 如果移动终端具有特定型号,即移动终端具有多媒体信息加密功能,则移动终端向移动终端订购的节目的密钥。 [0034] 移动终端获得解密密钥后,下载使用解密密钥点播的节目(节目点播)。 [0035] 需要说明的是,移动终端可以不向节目发送端发送移动终端的识别码和用户识别卡的卡号,而是直接获取节目,再判断节目是否为节目。 如果没有订阅,则移动终端对节目进行加密。 [0036] 移动终端下载订购的节目后,对节目数据进行加密,屏蔽部分节目数据,使移动终端用户可以体验节目,但不能观看完整的节目。 加密过程描述如下。 [0037] 移动终端下载的节目包括视频数据和音频数据。 视频数据解码后以位图的形式存在于移动终端中,位图的数据数组为线性数组。 例如,视频数据的大小为320*240,则移动终端可以创建一个彩色干扰区域,例如一个黑色矩形干扰区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0038] 其中‘MEMSET’是一个加密函数,用于对程序进行加密,‘pDATA’是一个临时变量,用于指示颜色干扰区域的位置。 [0039] 颜色干扰区域覆盖在下载节目的视频数据的最中心,使得在播放节目时,移动终端可以正常播放节目,但用户无法观看到完整的节目。 [0040] 移动终端还可以对音频数据进行加密,屏蔽节目的部分音频数据。 在移动终端下载解码的音频数据中选择性地加入其他音频数据进行混音,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)); }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0041] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0042]下载程序的视频数据和音频数据的加密可以交替进行,也可以同时进行。 [0043] 需要注意的是,移动终端对节目内容的加密并不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0044] 该方法在移动终端侧对节目进行加密,使得移动终端在为用户提供一定的电视节目体验的同时,可以保护未订阅的电视节目的内容,从而实现电视服务。 手机大为普及。 [0045] 参考图2和图3,示出了本发明移动终端一个实施例的结构图,该移动终端包括: [0046] 获取模块 01 , 用于订购并获取未订购的节目; [0047] 加密模块 30 ,用于对程序进行加密,屏蔽程序的部分数据; 和 [0048] 播放模块 40 ,配置为播放加密的节目。 [0049] 获取模块 01 包含: [0050] 认证模块 10 ,用于在点播未订阅的节目时,发送移动终端的识别码和移动终端用户识别卡的卡号,获取节目的解密密钥; 和 [0051] 一个下载模块 20 ,配置为下载并获取带有解密密钥的程序。 [0052] 加密模块 30 还包括: [0053] 视频干扰单元 32 ,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上; 和/或,音频干扰单元 33 ,用于对节目的部分音频数据进行混音。 [0054] 下面对本实施例的移动终端的工作原理进行详细说明。 [0055] 手机等移动终端向提供该移动终端电视服务的服务器发起某个节目的点播请求,与该服务器建立数据链路后,鉴权模块 10 发送移动终端识别码和移动终端用户识别卡卡号; 服务器在本地查询该卡号的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息,若发现该卡号未订阅该节目,则 程序不是免费程序,服务器进一步核对移动终端的识别码,一般为移动终端的型号,服务器将移动终端订购的程序的解密密钥发送给 移动终端如果只有移动终端具有特定型号,即移动终端具有多媒体信息加密功能。 [0056] 移动终端获得解密密钥后,下载模块 20 下载使用解密密钥订购的程序。 [0057] 移动端下载订购的程序后,加密模块 30 对节目进行加密,屏蔽节目的部分数据,使移动端用户可以体验节目,但不能观看完整的节目。 加密过程描述如下。 [0058] 移动终端下载的节目包括视频数据和音频数据。 视频数据解码后以位图的形式存在于移动终端中,位图的数据数组为线性数组。 比如视频数据的大小是320*240,那么视频干扰单元 32 可以创建一个颜色的干涉区域,例如一个黑色的矩形干涉区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0059] 视频干扰单元 32 覆盖下载节目视频数据最中心的颜色干扰区域,完成加密。 播放模块 40 可以播放节目,但不能播放完整的节目,用户看到的只是中间涂有彩色区域的节目。 [0060] 音频干扰单元 33 移动端可以对音频数据进行加密,屏蔽节目的部分音频数据。 在移动终端下载解码的音频数据中选择性地加入其他音频数据进行混音,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0061] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0062] 视频干扰单元 32 和音频干扰单元 33 可以单独存在,也可以同时存在。 [0063] 需要注意的是,移动终端对节目内容的加密并不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0064] 节目通过移动终端加密,使得移动终端在为用户提供一定的电视节目体验的同时,可以保护未订阅的电视节目内容,从而普及手机电视业务 大大。 [0065] 参见图4,示出了本发明另一种移动终端电视业务加密方法的实施例流程图,该方法包括: [0066] 步 201 :当移动终端点播未订阅的节目时,服务器对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道; [0067] 步 202 :服务器向移动终端发送信道信息和解密密钥。 [0068] 步 201 具体如下: [0069] 产生至少一色彩干扰区,且至少一色彩干扰区覆盖于节目的部分视频数据上。 和/或, [0070] 对节目的部分音频数据进行混音。 [0071] 下面对本实施例方法的工作原理进行详细说明。 [0072] 手机等移动终端向提供该移动终端电视服务的服务器发起某个节目的点播请求,与该服务器建立数据链路后,向该服务器发送用户识别卡的卡号; 服务器根据移动终端用户识别卡的卡号在本地查询用户的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息, 如果发现该卡号未订阅该节目且该节目不是免费节目,则服务器对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道。 加密过程描述如下。 [0073] 服务器提供的节目的视频数据解码后以位图的形式存在,位图的数据数组为线性数组。 例如视频数据的大小为320*240,则服务器可以创建一个颜色的干扰区域,例如一个黑色的矩形干扰区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0074] 颜色干扰区域覆盖在节目视频数据的最中心,从而完成对节目视频数据的加密。 [0075] 服务器还可以对音频数据进行加密,屏蔽节目的部分音频数据。 在原始音频数据中有选择地加入其他音频数据,以达到混音的目的,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0076] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0077] 视频数据和音频数据的加密可以交替进行,也可以同时进行。 [0078] 服务器为加密后的节目创建新的频道,并将新频道的信息和新频道的解密密钥发送给移动终端。 移动终端接收到新频道信息后,自动切换到该频道并播放带有解密密钥的节目,其中移动终端播放的节目为部分数据被屏蔽的节目,并非完整节目 程序。 [0079] 需要注意的是,服务器对节目内容的加密不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0080] 该方法在作为数据源的服务器端对节目进行加密,使移动终端用户对未订阅的电视节目有一定的体验,节目内容受到保护,因此, 手机电视业务大为普及。 [0081] 参考图5和图6,示出了本发明服务器一个实施例的结构图,该服务器用于移动终端的电视业务,该服务器包括: [0082] 加密模块 50 ,用于当移动终端点播未订阅的节目时,对该节目进行加密,屏蔽该节目的部分数据,并为加密后的节目创建新的频道; 和 [0083] 发送模块 60 ,用于向移动终端发送新频道信息和解密密钥。 [0084] 加密模块 50 包含: [0085] 视频干扰单元 52 ,用于创建至少一个颜色干扰区域,并将所述至少一个颜色干扰区域覆盖在所述节目的部分视频数据上; 和/或,音频干扰单元 53 ,用于对节目的部分音频数据进行混音。 [0086] 下面详细说明本实施例中服务器的工作原理。 [0087] 手机等移动终端向提供该移动终端电视服务的服务器发起某个节目的点播请求,与该服务器建立数据链路后,向该服务器发送用户识别卡的卡号; 服务器根据移动终端用户识别卡的卡号在本地查询用户的用户订阅列表,获取该卡号是否订阅了该节目,该节目是否为免费节目等信息, 如果发现卡号没有订阅节目且节目不是免费节目,则加密模块 50 对节目进行加密,屏蔽节目的部分数据,为加密后的节目创建新的频道。 加密过程描述如下。 [0088] 服务器提供的节目的视频数据解码后以位图的形式存在,位图的数据数组为线性数组。 比如视频数据的大小是320*240,那么视频干扰单元 52 可以创建一个颜色的干涉区域,例如一个黑色的矩形干涉区域,大小为160*120。 创建过程可以是如下语句:  对于 (i = 0, i < 240, i++) { MEMSET (pDATA + 160, 0, 160*2); } [0089] 视频干扰单元 52 覆盖节目视频数据最中心的颜色干扰区域,完成对节目数据的部分加密。 [0090] 音频干扰单元 53 服务器端可以对音频数据进行加密,屏蔽节目的部分音频数据。 在原始音频数据中有选择地加入其他音频数据,以达到混音的目的,具体方法如下: 在音频数据之后添加其他音频数据, 如果((样本 1 < 0)&&(样本 2 < 0)){ value = sample1 + sample2 − (sample1 * sample2 / −(pow(2,16-1)−1)) ; }别的{ value = sample1 + sample2 − (sample1 * sample2 / (pow(2,16-1)−1));  } [0091] 其中‘sample1’为原始音频数据,‘sample2’为要混入原始音频数据的音频数据,‘value’为加密后的音频数据。 [0092] 视频干扰单元 52 和音频干扰单元 53 可以单独存在,也可以同时存在。 [0093] 加密模块 50 为加密的程序创建一个新的通道,发送模块 60 向移动终端发送新频道信息和新频道的解密密钥。 移动终端接收到新频道信息后,自动切换到该频道并播放带有解密密钥的节目,其中移动终端播放的节目为部分数据被屏蔽的节目,并非完整节目 程序。 [0094] 需要注意的是,服务器对节目内容的加密不限于上述加密方式,也可以采用其他具有加密效果的类似方式。 [0095] 本实施例通过服务器对节目进行加密,使得移动终端对未订阅的电视节目有一定的体验,节目内容受到保护,极大地普及了手机电视业务。 . [0096] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的专利范围。 凡利用本发明说明书和附图的内容所作出的等效结构或等效流程变换,或者在其他相关技术领域的直接或间接应用,均应包含在本发明的专利保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101883241A(String), EP2579589A1(String), EP2579589A4(String), US20130104163A1(String), WO2011150627A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101883241A(String), EP2579589A1(String), EP2579589A4(String), US20130104163A1(String), WO2011150627A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101883241A(String), EP2579589A1(String), EP2579589A4(String), US20130104163A1(String), WO2011150627A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271129(Integer), CN101883241A(String), 1048050(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271129(Integer), EP2579589A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271129(Integer), EP2579589A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271129(Integer), US20130104163A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271129(Integer), WO2011150627A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101883241A(String), CN101883241A(String), 1289318400(Integer), 271129(Integer), 185413(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), HE, LIPENG(String), ZHANG, SHUYAN(String), 中兴通讯股份有限公司(String), HE LIPENG(String), ZHANG SHUYAN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185944(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185944(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HE, LIPENG(String), HE LIPENG(String), 0(Integer), 1681976033(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHANG, SHUYAN(String), ZHANG SHUYAN(String), 0(Integer), 1681976033(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185944(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75831(Integer), 2(Integer), 185944(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75832(Integer), 2(Integer), 185944(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.848 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.848 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75831(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:53.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185944(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.125 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20220353819A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Reducing Power Consumption of Mobile Terminal and Mobile Terminal(String), 降低移动终端功耗的方法及移动终端(String), US20220353819A1(String), A method for reducing power consumption of a mobile terminal and a mobile terminal are provided. The method includes: A mobile terminal establishes a Wi-Fi connection to an electronic device by using a Wi-Fi module; the mobile terminal interacts with a server by using the Wi-Fi connection; if the mobile terminal doesn't send or receive a packet within a first time period, the mobile terminal controls the Wi-Fi module to enter a sleep state; and after the Wi-Fi module enters the sleep state, if the mobile terminal needs to send a heartbeat packet, the mobile terminal may establish a Bluetooth connection to the electronic device by using a Bluetooth module, and send the heartbeat packet by using the Bluetooth connection.(String), 提供了一种降低移动终端功耗的方法和移动终端。 该方法包括:移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接; 移动终端通过Wi-Fi连接与服务器交互; 如果移动终端在第一时间段内没有发送或接收数据包,则移动终端控制Wi-Fi模块进入休眠状态。 Wi-Fi模块进入休眠状态后,如果移动终端需要发送心跳包,移动终端可以通过蓝牙模块与电子设备建立蓝牙连接,通过蓝牙发送心跳包 联系。(String), US17/812755(String), 1657814400(Integer), US20220353819A1(String), 1667404800(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 0(Integer), 18(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185945(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\afc05d4ca130404b9c1ba28211a95c8f.png(String), 185945(Integer), afc05d4ca130404b9c1ba28211a95c8f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Reducing Power Consumption of Mobile Terminal and Mobile Terminal(String), 降低移动终端功耗的方法及移动终端(String), US20220353819A1(String), A method for reducing power consumption of a mobile terminal and a mobile terminal are provided. The method includes: A mobile terminal establishes a Wi-Fi connection to an electronic device by using a Wi-Fi module; the mobile terminal interacts with a server by using the Wi-Fi connection; if the mobile terminal doesn't send or receive a packet within a first time period, the mobile terminal controls the Wi-Fi module to enter a sleep state; and after the Wi-Fi module enters the sleep state, if the mobile terminal needs to send a heartbeat packet, the mobile terminal may establish a Bluetooth connection to the electronic device by using a Bluetooth module, and send the heartbeat packet by using the Bluetooth connection.(String), 提供了一种降低移动终端功耗的方法和移动终端。 该方法包括:移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接; 移动终端通过Wi-Fi连接与服务器交互; 如果移动终端在第一时间段内没有发送或接收数据包,则移动终端控制Wi-Fi模块进入休眠状态。 Wi-Fi模块进入休眠状态后,如果移动终端需要发送心跳包,移动终端可以通过蓝牙模块与电子设备建立蓝牙连接,通过蓝牙发送心跳包 联系。(String), US17/812755(String), 1657814400(Integer), US20220353819A1(String), 1667404800(Integer), 美国(String), 1(Integer), 2(Integer), CN(String), 5(Integer), 0(Integer), \20230420\afc05d4ca130404b9c1ba28211a95c8f.png(String), 18(Integer), 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 1. A method, comprising:establishing, by a mobile terminal, a Wi-Fi connection to an electronic device by using a Wi-Fi module of the mobile terminal, and interacting, by the mobile terminal, with a server by using the Wi-Fi connection;controlling, by the mobile terminal, the Wi-Fi module to enter a sleep state; andwhile the Wi-Fi module is in the sleep state, when the mobile terminal has a to-be-sent first packet, sending, by the mobile terminal, the to-be-sent first packet to the electronic device using a Bluetooth connection established by a Bluetooth module of the mobile terminal, wherein the first packet is a heartbeat packet or a packet used to establish a transport layer link.(String), 1.一种方法,包括:移动终端通过移动终端的Wi-Fi模块与电子设备建立Wi-Fi连接,并通过该Wi-Fi连接与服务器交互;移动终端控制Wi-Fi模块进入休眠状态;和在Wi-Fi模块处于休眠状态时,当移动终端有待发送的第一包时,移动终端通过已建立的蓝牙连接向电子设备发送待发送的第一包通过移动终端的蓝牙模块,其中,第一报文为心跳报文或用于建立传输层链路的报文。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 2. The method according to claim 1, further comprising:while the Wi-Fi module is in the sleep state, when the mobile terminal has the to-be-sent first packet, waking up, by the mobile terminal, the Bluetooth module, and establishing the Bluetooth connection to the electronic device using the Bluetooth module.(String), 2.根据权利要求1所述的方法,还包括:在Wi-Fi模块处于休眠状态时,当移动终端有待发送的第一个数据包时,移动终端唤醒蓝牙模块,并通过蓝牙与电子设备建立蓝牙连接模块。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 3. The method according to claim 1, further comprising:after the mobile terminal sends the to-be-sent first packet, when the mobile terminal does not send or receive another packet within a second time period after sending the to-be-sent first packet, controlling the Bluetooth module to enter a sleep state.(String), 3.根据权利要求1所述的方法,还包括:移动终端发送待发送的第一个数据包后,当移动终端在发送该待发送的第一个数据包后的第二时间段内没有发送或接收到另一个数据包时,控制蓝牙模块进入休眠状态.4.根据权利要求1所述的方法,其特征在于,所述蓝牙连接为标准蓝牙连接或蓝牙低功耗连接。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 4. The method according to claim 1, wherein the Bluetooth connection is a standard Bluetooth connection or a Bluetooth low energy connection.(String), 5.根据权利要求1所述的方法,其特征在于,所述电子设备为无线路由器、Wi-Fi设备或具有热点能力的移动终端中的任一种。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 5. The method according to claim 1, wherein the electronic device is any one of a wireless router, a Wi-Fi device, or a mobile terminal with a hotspot capability.(String), 6.根据权利要求1所述的方法,还包括:Wi-Fi模块进入休眠状态后,当移动终端有待发送的第二包或待接收的第二包时,移动终端唤醒Wi-Fi模块,重新建立移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接,并通过Wi-Fi连接传输第二封包,其中移动终端保持或断开移动终端与电子设备之间的蓝牙连接移动终端唤醒后。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 6. The method according to claim 1, further comprising:after the Wi-Fi module enters the sleep state, when the mobile terminal has a to-be-sent second packet or a to-be-received second packet, waking up, by the mobile terminal, the Wi-Fi module, reestablishing a Wi-Fi connection between the mobile terminal and the electronic device by using the Wi-Fi module, and transmitting the second packet using the Wi-Fi connection, wherein the mobile terminal retains or disconnects the Bluetooth connection between the mobile terminal and the electronic device after the mobile terminal wakes up.(String), 7.根据权利要求1所述的方法,还包括:Wi-Fi模块进入休眠状态后,当移动终端有待发送首包时,在移动终端通过自身建立的蓝牙连接发送待发送首包之前蓝牙模块发送至电子设备,移动终端接收用户开启第一功能的指示,或者移动终端在判断满足第一条件时开启第一功能,其中第一功能是移动终端降低功耗的功能,第一条件包括:移动终端的电池电量小于预设值,移动终端启用的应用数量大于预设数量,移动终端终端启用任何一个或多个预设应用程序。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 7. The method according to claim 1, further comprising:after the Wi-Fi module enters the sleep state, when the mobile terminal has the to-be-sent first packet, and before sending, by the mobile terminal, the to-be-sent first packet by using the Bluetooth connection established by the Bluetooth module to the electronic device, receiving, by the mobile terminal, an indication for enabling a first function from a user, or enabling, by the mobile terminal, the first function when determining that a first condition is met, wherein the first function is a function of reducing power consumption of the mobile terminal, and the first condition comprises: a battery level of the mobile terminal is less than a preset value, a quantity of applications enabled by the mobile terminal is greater than a preset quantity, and the mobile terminal enables any one or more of preset applications.(String), 8.根据权利要求1所述的方法,其特征在于,所述心跳包在所述移动终端与所述服务器之间进行交换。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 8. The method according to claim 1, wherein the heartbeat packet is exchanged between the mobile terminal and the server.(String), 9.一种计算机可读存储介质,包括计算机指令,其中当所述计算机指令在移动终端上运行时,所述移动终端执行根据权利要求1所述的方法。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 9. A computer readable storage medium, comprising computer instructions, wherein when the computer instructions are run on a mobile terminal, the mobile terminal performs the method according to claim 1.(String), 10.一种方法,包括:电子设备通过电子设备的Wi-Fi模块分别与N个移动终端建立Wi-Fi连接,N个移动终端通过Wi-Fi连接与服务器交互,电子设备建立一个与服务器的通信连接;和当N个移动终端的所有Wi-Fi模块进入休眠状态时,电子设备控制电子设备的Wi-Fi模块进入休眠状态;和当N个移动终端中的M个移动终端的Wi-Fi模块进入休眠状态时,电子设备分别通过电子设备的蓝牙模块与M个移动终端建立蓝牙连接,发送待发送或M个移动终端的待接收的第一包,其中每个第一包为心跳包或用于建立传输层链路的包,M和N为正整数,M小于或等于N。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 10. A method, comprising:respectively establishing, by an electronic device, Wi-Fi connections to N mobile terminals using a Wi-Fi module of the electronic device, wherein the N mobile terminals interact with a server by using the Wi-Fi connections, and the electronic device establishes a communication connection to the server; andwhen all Wi-Fi modules of the N mobile terminals enter a sleep state, controlling, by the electronic device, a Wi-Fi module of the electronic device to enter the sleep state; andwhen Wi-Fi modules of M mobile terminals in the N mobile terminals enter a sleep state, respectively establishing, by the electronic device, Bluetooth connections to the M mobile terminals using a Bluetooth module of the electronic device, to transmit to-be-sent or to-be-received first packets of the M mobile terminals, wherein each first packet is a heartbeat packet or a packet used to establish a transport layer link, M and N are positive integers, and M is less than or equal to N.(String), 11.根据权利要求10所述的方法,其中,所述蓝牙连接是标准蓝牙连接或蓝牙低功耗连接。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 11. The method according to claim 10, wherein the Bluetooth connection is a standard Bluetooth connection or a Bluetooth low energy connection.(String), 12.根据权利要求10所述的方法,其特征在于,所述电子设备为无线路由器、随行的Wi-Fi设备或具有热点能力的移动终端中的任一种。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 12. The method according to claim 10, wherein the electronic device is any one of a wireless router, an accompanying Wi-Fi device, or a mobile terminal with a hotspot capability.(String), 13.一种电子设备,包括处理器、存储器、Wi-Fi模块和蓝牙模块,其中存储器、Wi-Fi模块和蓝牙模块耦合到处理器;存储器被配置为存储计算机程序代码;计算机程序代码包括计算机指令;当处理器从存储器读取计算机指令时,电子设备执行根据权利要求10所述的方法。(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 13. An electronic device, comprising a processor, a memory, a Wi-Fi module, and a Bluetooth module, wherein the memory, the Wi-Fi module, and the Bluetooth module are coupled to the processor; the memory is configured to store computer program code; the computer program code comprises computer instructions; and when the processor reads the computer instructions from the memory, the electronic device performs the method according to claim 10.(String), 14.根据权利要求10所述的方法,其特征在于,所述心跳包在所述移动终端与所述服务器之间进行交换。(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 14. The method according to claim 10, wherein the heartbeat packet is exchanged between the mobile terminal and the server.(String), 15.一种计算机可读存储介质,包括计算机指令,其中当所述计算机指令在电子设备上运行时,所述电子设备执行根据权利要求10所述的方法。(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 15. A computer readable storage medium, comprising computer instructions, wherein when the computer instructions are run on an electronic device, the electronic device performs the method according to claim 10.(String), 16.一种芯片系统,包括一个或多个处理器,其中当所述一个或多个处理器执行指令时,使所述电子设备执行根据权利要求10所述的方法。(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 16. A chip system, comprising one or more processors, wherein when the one or more processors execute instructions, the electronic device is caused to perform the method according to claim 10.(String), 17.一种电子设备系统,包括一个或多个移动终端和根据权利要求10所述的电子设备。(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 17. An electronic device system, comprising one or more mobile terminals and the electronic device according to claim 10.(String), 18.一种移动终端,包括:处理器;一段记忆;触摸屏;一个Wi-Fi模块;和蓝牙模块,其中存储器、触摸屏、Wi-Fi模块和蓝牙模块耦合到处理器;其中,所述存储器用于存储计算机程序代码,所述计算机程序代码包括可由所述处理器执行的计算机指令,当所述计算机指令被执行时,使所述移动终端:通过Wi-Fi模块与电子设备建立Wi-Fi连接,移动终端通过Wi-Fi连接与服务器交互;控制Wi-Fi模块进入休眠状态;和在Wi-Fi模块处于休眠状态时,当移动终端有待发送的第一包时,通过蓝牙模块建立的蓝牙连接将待发送的第一包发送给电子设备,其中第一个数据包是心跳数据包或用于建立传输层链路的数据包。(String), 1(Integer), 16(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:54.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185945(Integer), 18. A mobile terminal, comprising:a processor;a memory;a touchscreen;a Wi-Fi module; anda Bluetooth module, wherein the memory, the touchscreen, the Wi-Fi module, and the Bluetooth module are coupled to the processor;wherein the memory is configured to store computer program code, the computer program code comprises computer instructions executable by the processor, and when the computer instructions are executed, the mobile terminal is caused to:establish a Wi-Fi connection to an electronic device by using the Wi-Fi module, and interacting, by the mobile terminal, with a server by using the Wi-Fi connection;control the Wi-Fi module to enter a sleep state; andwhile the Wi-Fi module is in the sleep state, when the mobile terminal has a to-be-sent first packet, send the to-be-sent first packet to the electronic device using a Bluetooth connection established by the Bluetooth module, wherein the first packet is a heartbeat packet or a packet used to establish a transport layer link.(String), 0(Integer), 17(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185945(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2020/127544, filed on Nov. 9, 2020, which claims priority to Chinese Patent Application No. 202010043528.2, filed on Jan. 15, 2020. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]This application relates to the field of mobile terminal technologies, and in particular, to a method for reducing power consumption of a mobile terminal and a mobile terminal. BACKGROUND [0003]With the development of electronic technologies, mobile terminals provide increasingly more functions, enriching people's lives. When using an application on a mobile terminal, a user usually needs to access a network, to be specific, establish, by using one or more networks, a communication connection to a server corresponding to the application. [0004]Wi-Fi has a lower tariff and a higher network speed. Therefore, Wi-Fi is preferred for users to access the network. The mobile terminal may establish, by using a configured Wi-Fi module, a communication connection to the server in a connection manner of a wireless local area network (for example, a Wi-Fi network) by using the internet or a mobile communications network. Alternatively, the mobile terminal establishes, by using a Wi-Fi module, a communication connection to an accompanying Wi-Fi device (or referred to as a mobile Wi-Fi device) in a connection manner of a wireless local area network (for example, a Wi-Fi network), and accesses a mobile communications network by using the accompanying Wi-Fi device, to interact with the server. [0005]As a network access time of the user increases, a working time of the Wi-Fi module also extends, and power consumption of the Wi-Fi module is very high. It can be learned that power consumption of the Wi-Fi module is one of important indicators that affect a battery life of the mobile terminal. Therefore, how to reduce the power consumption of the Wi-Fi module in the mobile terminal is always a hot topic researched by manufacturers. SUMMARY [0006]This application provides a method for reducing power consumption of a mobile terminal and a mobile terminal, to reduce power consumption of a Wi-Fi module in the mobile terminal, thereby helping prolong a standby time of the mobile terminal. [0007]To achieve the foregoing objective, embodiments of this application provide the following technical solutions. [0008]According to a first aspect, a method for reducing power consumption of a mobile terminal is provided. The mobile terminal has a Wi-Fi module and a Bluetooth module. The method includes: The mobile terminal establishes a Wi-Fi connection to an electronic device by using the Wi-Fi module, and the mobile terminal interacts with a server by using the Wi-Fi connection. If the mobile terminal does not send or receive a packet within a first time period, the mobile terminal controls the Wi-Fi module to enter a sleep state, where the packet includes a first packet and a second packet, or the packet includes a second packet. The first packet is a heartbeat packet or a packet used to establish a transport layer link, and the second packet is a packet other than the first packet. After the Wi-Fi module enters the sleep state, if the mobile terminal has a to-be-sent first packet, the mobile terminal sends the to-be-sent first packet by using a Bluetooth connection established by the Bluetooth module to the electronic device. [0009]It can be learned that, when the Wi-Fi module of the mobile terminal is in the sleep state, if the mobile terminal only needs to send the first packet, the mobile terminal does not wake up the Wi-Fi module, but wakes up the Bluetooth module having lower power consumption than the Wi-Fi module, and sends the first packet in a Bluetooth mode, to reduce power consumption of the Wi-Fi module. In this way, overall power consumption of the mobile terminal is reduced, and a battery life of the mobile terminal is prolonged. [0010]In a possible implementation, the method further includes: After the Wi-Fi module enters the sleep state, if the mobile terminal has the to-be-sent first packet, the mobile terminal wakes up the Bluetooth module, and establishes the Bluetooth connection to the electronic device by using the Bluetooth module. [0011]In some examples, after the Wi-Fi module enters the sleep state, the mobile terminal starts to establish the Bluetooth connection to the electronic device. Alternatively, after the Wi-Fi module enters the sleep state, the mobile terminal establishes the Bluetooth connection to the electronic device only when determining that a first packet needs to be sent. In some other examples, the mobile terminal may alternatively establish the Bluetooth connection to the electronic device before the Wi-Fi module enters the sleep state. Therefore, a plurality of occasions for establishing the Bluetooth connection between the mobile terminal and the electronic device are provided. [0012]In a possible implementation, the method further includes: After the mobile terminal sends the to-be-sent first packet, if the mobile terminal does not send or receive another packet within a second time period, the mobile terminal controls the Bluetooth module to enter a sleep state. This helps further reduce power consumption of the Bluetooth module. [0013]In a possible implementation, the Bluetooth connection is a classic Bluetooth connection or a Bluetooth low energy connection. [0014]In a possible implementation, the electronic device is any one of a wireless router, an accompanying Wi-Fi device, or a mobile terminal with a hotspot capability. [0015]In a possible implementation, after the Wi-Fi module enters the sleep state, the method further includes: If the mobile terminal has a to-be-sent second packet or a to-be-received second packet, the mobile terminal wakes up the Wi-Fi module, reestablishes a Wi-Fi connection between the mobile terminal and the electronic device by using the Wi-Fi module, and transmits the second packet by using the Wi-Fi connection, and the mobile terminal retains or disconnects the Bluetooth connection between the mobile terminal and the electronic device. [0016]In a possible implementation, after the Wi-Fi module enters the sleep state, if the mobile terminal has a to-be-sent first packet, before the mobile terminal sends the to-be-sent first packet by using the Bluetooth connection established by the Bluetooth module to the electronic device, the method further includes: The mobile terminal receives an indication for enabling a first function from a user, or the mobile terminal enables the first function when determining that a first condition is met, where the first function is a function of reducing power consumption of the mobile terminal, and the first condition includes: a battery level of the mobile terminal is less than a preset value, a quantity of applications enabled by the mobile terminal is greater than a preset quantity, and the mobile terminal enables any one or more of preset applications. [0017]In a possible implementation, the heartbeat packet is a heartbeat packet exchanged between the mobile terminal and the server. [0018]According to a second aspect, a method for reducing power consumption of a mobile terminal is provided. An electronic device has a Wi-Fi module and a Bluetooth module, and the electronic device establishes a communication connection to a server. The method includes: The electronic device respectively establishes Wi-Fi connections to N mobile terminals by using the Wi-Fi module, so that the N mobile terminals interact with the server by using the Wi-Fi connections. If Wi-Fi modules of M mobile terminals in the N mobile terminals enter a sleep state, the electronic device respectively establishes Bluetooth connections to the M mobile terminals by using the Bluetooth module, to transmit to-be-sent or to-be-received first packets of the M mobile terminals. The first packet is a heartbeat packet or a packet used to establish a transport layer link, M and N are positive integers, and M is less than or equal to N. Therefore, power consumption of the M mobile terminals is reduced. [0019]In a possible implementation, after the Wi-Fi modules of the M mobile terminals in the N mobile terminals enter the sleep state, where M is less than N, the method further includes: The electronic device transmits, by using a Wi-Fi connection, packets to be sent or to be received by mobile terminals other than the M mobile terminals and whose Wi-Fi modules do not enter the sleep state. [0020]In a possible implementation, the method further includes: If all Wi-Fi modules of the N mobile terminals enter the sleep state, that is, if M is equal to N, the electronic device controls the Wi-Fi module of the electronic device to enter the sleep state. [0021]In a possible implementation, the Bluetooth connection is a classic Bluetooth connection or a Bluetooth low energy connection. [0022]In a possible implementation, the electronic device is any one of a wireless router, an accompanying Wi-Fi device, or a mobile terminal with a hotspot capability. [0023]In a possible implementation, the heartbeat packet is a heartbeat packet exchanged between the mobile terminal and the server. [0024]According to a third aspect, a mobile terminal is provided, including a processor, a memory, a touchscreen, a Wi-Fi module, and a Bluetooth module. The memory, the touchscreen, the Wi-Fi module, and the Bluetooth module are coupled to the processor, and the memory is configured to store computer program code. The computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the mobile terminal performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0025]According to a fourth aspect, an electronic device is provided, including a processor, a memory, a Wi-Fi module, and a Bluetooth module. The memory, the Wi-Fi module, and the Bluetooth module are coupled to the processor, and the memory is configured to store computer program code. The computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the electronic device performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0026]According to a fifth aspect, an apparatus is provided. The apparatus is included in a mobile terminal, and the apparatus has a function of implementing behavior of the mobile terminal in any method in the foregoing aspects and the possible implementations of the foregoing aspects. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or the software includes at least one module or unit corresponding to the foregoing function, for example, a communication module or unit, or a control module or unit. [0027]According to a sixth aspect, an apparatus is provided. The apparatus is included in an electronic device, and the apparatus has a function of implementing behavior of the electronic device in any method in the foregoing aspects and the possible implementations of the foregoing aspects. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or the software includes at least one module or unit corresponding to the foregoing function, for example, a communication module or unit, or a control module or unit. [0028]According to a seventh aspect, a computer readable storage medium is provided, including computer instructions. When the computer instructions are run on a mobile terminal, the mobile terminal performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0029]According to an eighth aspect, a computer readable storage medium is provided, including computer instructions. When the computer instructions are run on an electronic device, the electronic device performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0030]According to a ninth aspect, a computer program product is provided. When the computer program product runs on a computer, the computer performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. [0031]According to a tenth aspect, a chip system is provided, including a processor. When the processor executes instructions, the processor performs the method according to any one of the foregoing aspects and the possible implementations of the foregoing aspects. BRIEF DESCRIPTION OF THE DRAWINGS [0032]FIG. 1 is a schematic structural diagram of a communications system according to an embodiment of this application; [0033]FIG. 2A is a schematic structural diagram 1 of a mobile terminal according to an embodiment of this application; [0034]FIG. 2B is a schematic structural diagram 2 of a mobile terminal according to an embodiment of this application; [0035]FIG. 3 is a schematic diagram of some user interfaces of a mobile terminal according to an embodiment of this application; [0036]FIG. 4 is a schematic flowchart of a method for reducing power consumption of a mobile terminal according to an embodiment of this application; [0037]FIG. 5A is a schematic flowchart of another method for reducing power consumption of a mobile terminal according to an embodiment of this application; [0038]FIG. 5B is a schematic flowchart of another method for reducing power consumption of a mobile terminal according to an embodiment of this application; and [0039]FIG. 6 is a schematic structural diagram of a chip system according to an embodiment of this application. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0040]In the embodiments of this application, words such as “example” or “for example” are used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as “example” or “for example” in the embodiments of this application should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the words such as “example” or “for example” is intended to present a relative concept in a specific manner. [0041]The following terms “first” and “second” are merely intended for a purpose of description, and shall not be understood as an indication or implication of relative importance or implicit indication of a quantity of indicated technical features. Therefore, a feature limited by “first” or “second” may explicitly or implicitly include one or more features. In the descriptions of the embodiments of this application, unless otherwise stated, “a plurality of” means two or more than two. [0042]Applications installed on a mobile terminal generally provide rich functions for a user. When using the application on the mobile terminal, the user usually needs to access a network, to be specific, establish, by using one or more networks, a communication connection to a server corresponding to the application. Currently, the mobile terminal may establish, by using a configured modem, a communication connection to the server in a wireless communication connection manner such as 2G/3G/4G/5G by using a mobile communications network. Alternatively, the mobile terminal may establish, by using a configured Wi-Fi module, a communication connection to the server in a connection manner of a wireless local area network (for example, a Wi-Fi network) by using the internet or a mobile communications network. In an example, the mobile terminal establishes a communication connection to a wireless router by using a Wi-Fi wireless connection technology, and accesses the internet by using the wireless router, to interact with the server. Alternatively, the mobile terminal establishes a communication connection to an accompanying Wi-Fi device (or referred to as a mobile Wi-Fi device) by using a Wi-Fi wireless connection technology, and accesses a mobile communications network by using the accompanying Wi-Fi device, to interact with the server. [0043]Wi-Fi has a lower tariff and a higher network speed. Therefore, Wi-Fi is preferred for network access. It can be learned that power consumption of the Wi-Fi module is one of important indicators that affect a battery life of the mobile terminal. Currently, some solutions have been used to reduce the power consumption of the Wi-Fi module. For example, when the mobile terminal has no data transmission, the Wi-Fi module may be controlled to enter a sleep state. Subsequently, when the mobile terminal has data transmission, the Wi-Fi module is woken up to continue to work. [0044]It may be noted that after the Wi-Fi module enters the sleep state, because a large quantity of applications are installed on the mobile terminal, the Wi-Fi module is frequently woken up when these applications send heartbeat packets. In the embodiments of this application, when an application sends a heartbeat packet, the mobile terminal does not wake up the Wi-Fi module, but wakes up a Bluetooth module having lower power consumption than the Wi-Fi module, and sends a heartbeat packet of each application in a Bluetooth mode, to reduce the power consumption of the Wi-Fi module. In this way, overall power consumption of the mobile terminal is reduced, and the battery life of the mobile terminal is prolonged. [0045]FIG. 1 is a schematic structural diagram of a communications system according to an embodiment of this application. The communications system includes a mobile terminal 100 and an electronic device 200. Various applications may be installed and run on the mobile terminal 100, to provide rich functions for a user. Generally, the mobile terminal 100 may access the internet or a mobile communications network through the electronic device 200, to communicate with a server corresponding to each application. [0046]For example, the mobile terminal 100 in this application may be a mobile phone, a tablet computer, a personal computer (PC), a personal digital assistant (PDA), a smartwatch, a netbook, a wearable electronic device, an augmented reality (AR) device, a virtual reality (VR) device, a vehicle-mounted device, a smart car, a smart stereo, a robot, and the like. A specific form of the mobile terminal is not specifically limited in this application. [0047]FIG. 2A is a schematic structural diagram of the mobile terminal 100. The mobile terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identification module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, an optical proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like. [0048]It may be understood that the structure shown in this embodiment of the present invention constitutes no specific limitation on the mobile terminal 100. In some other embodiments of this application, the mobile terminal 100 may include more or fewer components than those shown in the figure, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. [0049]The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural network processing unit (NPU). Different processing units may be independent components, or may be integrated into one or more processors. [0050]The controller may generate an operation control signal based on instruction operation code and a time sequence signal, to control instruction fetching and instruction execution. [0051]A memory may be further disposed in the processor 110, and is configured to store instructions and data. In some embodiments, the memory in the processor 110 is a cache. The memory may store instructions or data that is used or cyclically used by the processor 110. If the processor 110 needs to use the instructions or the data again, the instructions or the data may be invoked directly from the memory. This avoids repeated access and reduces a waiting time of the processor 110, thereby improving efficiency of the system. [0052]In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (SIM) interface, a universal serial bus (USB) interface, and/or the like. [0053]The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include a plurality of I2C buses. The processor 110 may be separately coupled to the touch sensor, a charger, a flash, the camera 193, and the like by using different I2C bus interfaces. For example, the processor no may be coupled to the touch sensor by using an I2C interface, so that the processor no communicates with the touch sensor by using the I2C bus interface, to implement a touch function of the mobile terminal 100. [0054]The I2S interface may be used for audio communication. In some embodiments, the processor no may include a plurality of I2S buses. The processor no may be coupled to the audio module 170 by using an I2S bus, to implement communication between the processor no and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 by using the I2S interface, to implement a function of answering a call by using a Bluetooth headset. [0055]The PCM interface may also be used for audio communication to sample, quantize, and encode an analog signal. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by using a PCM bus interface. In some embodiments, the audio module 170 may alternatively transmit an audio signal to the wireless communication module 160 by using the PCM interface, to implement a function of answering a call by using a Bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication. [0056]The UART interface is a universal serial data bus used for asynchronous communication. The bus may be a bidirectional communications bus. The bus implements conversion between serial communication and parallel communication for data to be transmitted. In some embodiments, the UART interface is generally configured to connect the processor no to the wireless communication module 160. For example, the processor no communicates with a Bluetooth module in the wireless communication module 160 by using the UART interface, to implement a Bluetooth function. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 by using the UART interface, to implement a function of playing music by using a Bluetooth headset. [0057]The MIPI interface may be configured to connect the processor 110 to peripheral devices such as the display 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), and the like. In some embodiments, the processor 110 communicates with the camera 193 by using the CSI interface, to implement a photographing function of the mobile terminal 100. The processor 110 communicates with the display 194 by using the DSI interface, to implement a display function of the mobile terminal 100. [0058]The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal, or may be configured as a data signal. In some embodiments, the GPIO interface may be configured to connect the processor 110 to the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may alternatively be configured as an I2C interface, an I2S interface, a UART interface, an MIPI interface, or the like. [0059]The USB interface 130 is an interface that complies with a USB standard specification, and may be specifically a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be configured to connect to the charger to charge the mobile terminal 100, or may be configured to transmit data between the mobile terminal 100 and a peripheral device. The USB interface 130 may alternatively be configured to connect to a headset, to play audio by using the headset. The interface may alternatively be configured to connect to another mobile terminal, for example, an AR device. [0060]It may be understood that the interface connection relationship between modules shown in this embodiment of the present invention is merely an example for description, and does not constitute a structural limitation on the mobile terminal 100. In some other embodiments of this application, the mobile terminal 100 may alternatively use an interface connection manner different from that in the foregoing embodiment, or a combination of a plurality of interface connection manners. [0061]The charging management module 140 is configured to receive charging input from the charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger by using the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input by using a wireless charging coil of the mobile terminal 100. When charging the battery 142, the charging management module 140 may further supply power to the mobile terminal by using the power management module 141. [0062]The power management module 141 is configured to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may be further configured to monitor parameters such as a battery capacity, a quantity of battery cycles, and a battery health status (leakage and impedance). In some other embodiments, the power management module 141 may alternatively be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 may alternatively be disposed in a same device. [0063]A wireless communication function of the mobile terminal 100 may be implemented by using the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like. [0064]The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the mobile terminal 100 may be configured to cover a single or more communication bands. Different antennas may be further multiplexed to improve antenna utilization. For example, the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In some other embodiments, the antenna may be used in combination with a tuning switch. [0065]The mobile communication module 150 may provide a wireless communication solution that is applied to the mobile terminal 100 and that includes 2G/3G/4G/5G or the like. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 may receive an electromagnetic wave by using the antenna 1, perform processing such as filtering and amplification on the received electromagnetic wave, and transmit the received electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may further amplify a signal modulated by the modem processor, and convert the signal into an electromagnetic wave by using the antenna 1 for radiation. In some embodiments, at least some function modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some function modules of the mobile communication module 150 and at least some modules of the processor 110 may be disposed in a same device. [0066]The modem processor may include a modulator and a demodulator. The modulator is configured to modulate a low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low frequency baseband signal. Then, the demodulator transmits the low frequency baseband signal obtained through demodulation to the baseband processor for processing. After being processed by the baseband processor, the low frequency baseband signal is transmitted to the application processor. The application processor outputs an audio signal by using an audio device (not limited to the speaker 170A, the receiver 170B, or the like), or display an image or a video by using the display 194. In some embodiments, the modem processor may be an independent device. In some other embodiments, the modem processor may be independent of the processor 110, and disposed in a same device with the mobile communication module 150 or another function module. [0067]The wireless communication module 160 may provide a wireless communication solution that is applied to the mobile terminal 100 and that includes a wireless local area network (WLAN) (for example, a Wireless Fidelity (Wi-Fi) network), Bluetooth (BT), a global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), or the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives an electromagnetic wave by using the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signal, and sends a processed signal to the processor 110. The wireless communication module 160 may further receive a to-be-sent signal from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into an electromagnetic wave by using the antenna 2 for radiation. [0068]In some embodiments of this application, when determining that all applications have no data transmission, the processor 110 may indicate a WLAN module (for example, a Wi-Fi module) in the wireless communication module to enter a sleep state. When the WLAN module is in the sleep state, if an application needs to send a heartbeat packet, the processor 110 indicates a BT module in the wireless communication module to establish a communication connection between the mobile terminal 100 and the electronic device 200, and send a heartbeat packet of each application by using the communication connection. When determining that one or more applications need to send data (non-heartbeat packets), the processor 110 wakes up the WLAN module, establishes a WLAN connection between the mobile terminal 100 and the electronic device, and transmits the dat(String), 相关申请的交叉引用 [0001] 本申请是2020年11月9日提交的国际申请PCT/CN2020/127544的继续申请,该申请要求2020年1月15日提交的中国专利申请202010043528.2的优先权。上述申请的公开内容是 特此通过引用将其全部内容并入本文。 技术领域 [0002] 本申请涉及移动终端技术领域,尤其涉及一种降低移动终端功耗的方法及移动终端。 背景 [0003] 随着电子技术的发展,移动终端提供了越来越多的功能,丰富了人们的生活。 用户在移动终端上使用应用程序时,通常需要访问网络,具体而言,通过一个或多个网络与该应用程序对应的服务器建立通信连接。 [0004] Wi-Fi资费更低,网速更高。 因此,Wi-Fi 是用户接入网络的首选方式。 移动终端可以通过配置的Wi-Fi模块通过互联网或移动通信网络以无线局域网(例如Wi-Fi网络)的连接方式与服务器建立通信连接 . 或者,移动终端通过Wi-Fi模块,以无线局域网的连接方式(例如 ,Wi-Fi 网络),并通过随附的 Wi-Fi 设备访问移动通信网络,与服务器交互。 [0005] 随着用户上网时间的增加,Wi-Fi模块的工作时间也随之延长,Wi-Fi模块的功耗非常高。 可以看出,Wi-Fi模块的功耗是影响移动终端续航的重要指标之一。 因此,如何降低移动终端中Wi-Fi模块的功耗一直是厂商研究的热点。 概括 [0006] 本申请提供一种降低移动终端功耗的方法及移动终端,以降低移动终端中Wi-Fi模块的功耗,从而有助于延长移动终端的待机时间。 [0007] 为实现上述目的,本申请实施例提供以下技术方案。 [0008] 根据第一方面,提供了一种用于降低移动终端的功耗的方法。 移动终端具有Wi-Fi模块和蓝牙模块。 该方法包括:移动终端通过Wi-Fi模块与电子设备建立Wi-Fi连接,移动终端通过Wi-Fi连接与服务器交互。 如果移动终端在第一时间段内没有发送或接收数据包,则移动终端控制Wi-Fi模块进入休眠状态,该数据包包括第一数据包和第二数据包,或者该数据包包括第二数据包。 包。 第一报文为心跳报文或用于建立传输层链路的报文,第二报文为第一报文以外的报文。 Wi-Fi模块进入休眠状态后,如果移动终端有待发送的第一包,移动终端通过蓝牙模块建立的蓝牙连接将待发送的第一包发送给电子设备。 设备。 [0009] 可以了解到,当移动终端的Wi-Fi模块处于休眠状态时,如果移动终端只需要发送第一个数据包,移动终端不会唤醒Wi-Fi模块,而是唤醒 蓝牙模块的功耗低于Wi-Fi模块,并以蓝牙模式发送第一包,以降低Wi-Fi模块的功耗。 这样,降低了移动终端的整体功耗,延长了移动终端的电池寿命。 [0010]在一种可能的实现方式中,该方法还包括: Wi-Fi模块进入休眠状态后,若移动终端有待发送的第一包,则移动终端唤醒蓝牙模块,建立蓝牙连接 使用蓝牙模块的电子设备。 [0011] 在一些示例中,在Wi-Fi模块进入休眠状态后,移动终端开始与电子设备建立蓝牙连接。 或者,在Wi-Fi模块进入休眠状态后,移动终端仅在确定需要发送第一包时才与电子设备建立蓝牙连接。 在一些其他示例中,移动终端也可以在Wi-Fi模块进入休眠状态之前与电子设备建立蓝牙连接。 因此,提供了移动终端与电子设备之间建立蓝牙连接的多种场合。 [0012] 在一种可能的实现方式中,该方法还包括: 移动终端发送待发送的第一包后,如果移动终端在第二时间段内没有发送或接收到其他包,则移动终端控制蓝牙模块进入 一种睡眠状态。 这有助于进一步降低蓝牙模块的功耗。 [0013] 在一种可能的实现方式中,蓝牙连接为经典蓝牙连接或蓝牙低功耗连接。 [0014] 在一种可能的实现方式中,电子设备为无线路由器、随行的Wi-Fi设备或具有热点能力的移动终端中的任一种。 [0015] 在一种可能的实现方式中,在Wi-Fi模块进入休眠状态后,该方法还包括: 若移动终端有待发送的第二包或待接收的第二包,则移动终端唤醒 Wi-Fi模块,通过Wi-Fi模块重新建立移动终端与电子设备的Wi-Fi连接,并通过Wi-Fi连接发送第二数据包,移动终端保持或断开蓝牙连接 在移动终端和电子设备之间。 [0016] 在一种可能的实现方式中,在Wi-Fi模块进入休眠状态后,如果移动终端有待发送的第一包,则在移动终端通过蓝牙连接发送该待发送的第一包之前 所述蓝牙模块发送至所述电子设备,所述方法还包括: 所述移动终端接收用户开启第一功能的指示,或者所述移动终端在确定满足第一条件时开启所述第一功能,所述第一功能为 移动终端降低功耗的功能,第一条件包括:移动终端的电池电量小于预设值,移动终端启用的应用数量大于预设数量,移动终端 终端启用任何一个或多个预设应用程序。 [0017] 在一种可能的实现方式中,所述心跳包为移动终端与服务器之间交互的心跳包。 [0018] 根据第二方面,提供了一种降低移动终端功耗的方法。 电子装置具有Wi-Fi模块及蓝牙模块,电子装置与服务器建立通讯连接。 该方法包括:电子设备通过Wi-Fi模块分别与N个移动终端建立Wi-Fi连接,以使N个移动终端通过Wi-Fi连接与服务器进行交互。 如果N个移动终端中的M个移动终端的Wi-Fi模块进入休眠状态,则电子设备通过蓝牙模块分别与M个移动终端建立蓝牙连接,发送待发送或待接收 M个移动终端的第一个数据包。 第一报文为心跳报文或用于建立传输层链路的报文,M和N为正整数,M小于或等于N,从而降低了M个移动终端的功耗。 [0019]在一种可能的实现方式中,N个移动终端中的M个移动终端的Wi-Fi模块进入休眠状态后,M小于N,该方法还包括: 电子设备通过Wi-Fi连接进行传输 ,除M个移动终端外,其Wi-Fi模块未进入睡眠状态的移动终端要发送或要接收的数据包。 [0020] 在一种可能的实现方式中,该方法还包括: 若N个移动终端的Wi-Fi模块全部进入休眠状态,即M等于N,则电子设备控制电子设备的Wi-Fi模块 进入睡眠状态。 [0021] 在一种可能的实现方式中,蓝牙连接为经典蓝牙连接或蓝牙低功耗连接。 [0022] 在一种可能的实现方式中,电子设备为无线路由器、随行的Wi-Fi设备或具有热点能力的移动终端中的任一种。 [0023] 在一种可能的实现方式中,所述心跳包为移动终端与服务器之间交互的心跳包。 [0024] 第三方面,提供一种移动终端,包括处理器、存储器、触摸屏、Wi-Fi模块和蓝牙模块。 存储器、触摸屏、Wi-Fi模块和蓝牙模块耦合到处理器,并且存储器被配置为存储计算机程序代码。 所述计算机程序代码包括计算机指令,当所述处理器从所述存储器中读取所述计算机指令时,所述移动终端执行上述任一方面的方法以及上述方面的可能实现方式。 [0025] 第四方面,提供一种电子装置,包括处理器、存储器、Wi-Fi模块以及蓝牙模块。 存储器、Wi-Fi模块和蓝牙模块耦合到处理器,并且存储器被配置为存储计算机程序代码。 所述计算机程序代码包括计算机指令,当所述处理器从所述存储器中读取所述计算机指令时,所述电子设备执行上述任一方面的方法以及上述方面的可能实施方式。 [0026] 根据第五方面,提供了一种装置。 该装置包括在移动终端中,具有实现上述方面的任一方法和上述方面的可能实现方式中的移动终端的行为的功能。 该功能可以通过硬件来实现,也可以通过硬件执行相应的软件来实现。 硬件或软件包括与上述功能对应的至少一个模块或单元,例如通信模块或单元,或者控制模块或单元。 [0027] 根据第六方面,提供了一种装置。 该装置包括在电子设备中,具有实现电子设备在上述方面和上述方面的可能实现方式中的任一种方法中的行为的功能。 该功能可以通过硬件来实现,也可以通过硬件执行相应的软件来实现。 硬件或软件包括与上述功能对应的至少一个模块或单元,例如通信模块或单元,或者控制模块或单元。 [0028] 根据第七方面,提供了一种计算机可读存储介质,包括计算机指令。 当计算机指令在移动终端上运行时,移动终端执行上述任一方面的方法及上述方面的可能实现方式。 [0029] 根据第八方面,提供了一种计算机可读存储介质,包括计算机指令。 当计算机指令在电子设备上运行时,电子设备执行上述任一方面的方法以及上述方面的可能实现方式。 [0030]根据第九方面,提供了一种计算机程序产品。 当计算机程序产品在计算机上运行时,计算机执行上述任一方面的方法以及上述方面的可能实现方式。 [0031] 第十方面,提供一种芯片系统,包括处理器。 当处理器执行指令时,处理器执行上述任一方面的方法以及上述方面的可能实现方式。 附图的简要说明 [0032] 图1为本申请实施例提供的一种通信系统的结构示意图; [0033] 图2A是结构示意图 1 根据本申请的一个实施例的移动终端的; [0034] 图2B为结构示意图 2 根据本申请的一个实施例的移动终端的; [0035] 图3为本申请实施例提供的移动终端部分用户界面示意图; [0036] 图4为本申请实施例提供的一种降低移动终端功耗的方法的流程示意图; [0037] 图5A为本申请实施例提供的另一种降低移动终端功耗的方法的流程示意图; [0038] 图5B为本申请实施例提供的另一种降低移动终端功耗的方法的流程示意图; 和 [0039] 图6为本申请实施例提供的一种芯片系统的结构示意图。 说明性实施例的详细说明 [0040] 在本申请实施例中,“示例”或“例如”等词语用于表示举例、说明或描述。 在本申请的实施例中描述为“示例”或“例如”的任何实施例或设计方案不应被解释为比另一个实施例或设计方案更优选或具有更多优点。 确切地说,使用“example”或“for example”等词语是为了以特定的方式呈现一个相对的概念。 [0041] 以下术语“第一”和“第二”仅用于描述目的,不应被理解为相对重要性的指示或暗示或所指示的技术特征的数量的隐含指示。 因此,受“第一”或“第二”限制的特征可以明确或隐含地包括一个或多个特征。 在本申请实施例的描述中,除非另有说明,“多个”是指两个或两个以上。 [0042] 安装在移动终端上的应用程序通常为用户提供丰富的功能。 用户在移动终端上使用应用程序时,通常需要接入网络,具体而言,通过一个或多个网络与该应用程序对应的服务器建立通信连接。 目前,移动终端可以通过配置的调制解调器,通过移动通信网络以2G/3G/4G/5G等无线通信连接方式与服务器建立通信连接。 或者,移动终端可以通过配置的Wi-Fi模块,通过互联网或移动设备以无线局域网(例如Wi-Fi网络)的连接方式与服务器建立通信连接。 通讯网络。 在一个示例中,移动终端通过Wi-Fi无线连接技术与无线路由器建立通信连接,并通过无线路由器访问互联网,与服务器交互。 或者,移动终端通过Wi-Fi无线连接技术与随行Wi-Fi设备(或称为移动Wi-Fi设备)建立通信连接,并通过随行Wi-Fi接入移动通信网络。 Fi 设备,用于与服务器交互。 [0043]Wi-Fi资费更低,网速更高。 因此,Wi-Fi 是首选的网络访问方式。 可以看出,Wi-Fi模块的功耗是影响移动终端续航的重要指标之一。 目前,已经采用了一些方案来降低Wi-Fi模块的功耗。 例如,当移动终端没有数据传输时,可以控制Wi-Fi模块进入休眠状态。 随后,当移动终端有数据传输时,唤醒Wi-Fi模块继续工作。 [0044] 需要注意的是,Wi-Fi模块进入休眠状态后,由于移动终端安装了大量的应用程序,这些应用程序在发送心跳包时会频繁地唤醒Wi-Fi模块。 在本申请实施例中,当应用发送心跳包时,移动终端不会唤醒Wi-Fi模块,而是唤醒功耗比Wi-Fi模块低的蓝牙模块,并发送心跳包 蓝牙模式下的每个应用程序,以降低Wi-Fi模块的功耗。 这样,降低了移动终端的整体功耗,延长了移动终端的电池寿命。 [0045] 图1为本申请实施例提供的一种通信系统的结构示意图。 该通信系统包括移动终端 100 和一个电子设备 200 . 可以在移动终端上安装和运行各种应用程序 100 , 为用户提供丰富的功能。 一般来说,移动端 100 可以通过电子设备访问互联网或移动通信网络 200 ,与每个应用程序对应的服务器进行通信。 [0046] 例如,移动终端 100 在此应用中可以是手机、平板电脑、个人电脑 (PC)、个人数字助理 (PDA)、智能手表、上网本、可穿戴电子设备、增强现实 (AR) 设备、虚拟现实 (VR)设备、车载设备、智能汽车、智能音响、机器人等。 本申请对移动终端的具体形式不作具体限定。 [0047] 图2A是移动终端的结构示意图 100 . 移动终端 100 可能包括处理器 110 ,一个外部存储器接口 120 , 内部存储器 121 , 一个通用串行总线 (USB) 接口 130 , 充电管理模块 140 , 电源管理模块 141 , 一个电池 142 , 天线 1 , 天线 2 , 移动通信模块 150 , 无线通讯模块 160 , 一个音频模块 170 , 扬声器 170 A、接收器 170 B、麦克风 170 C、耳机插孔 170 D、传感器模块 180 , 关键 190 , 一个马达 191 , 一个指标 192 , 相机 193 , 一个显示器 194 ,一个用户识别模块(SIM)卡接口 195 ,等等。 传感器模块 180 可包括压力传感器、陀螺仪传感器、气压传感器、磁传感器、加速度传感器、距离传感器、光学接近传感器、指纹传感器、温度传感器、触摸传感器、环境光传感器、 骨传导传感器等。 [0048] 可以理解的是,本发明实施例所示的结构不构成对移动终端的具体限制 100 . 在本申请的其他一些实施例中,移动终端 100 可以包括比图中所示更多或更少的组件,或者组合一些组件,或者拆分一些组件,或者具有不同的组件布置。 所示组件可以以硬件、软件或软件和硬件的组合来实现。 [0049] 处理器 110 可以包括一个或多个处理单元。 例如,处理器 110可包括应用处理器 (AP)、调制解调器处理器、图形处理单元 (GPU)、图像信号处理器 (ISP)、控制器、视频编解码器、数字信号处理器 (DSP)、基带处理器和/ 或神经网络处理单元(NPU)。 不同的处理单元可以是独立的组件,也可以集成到一个或多个处理器中。 [0050] 控制器可以基于指令操作码和时序信号产生操作控制信号,以控制指令获取和指令执行。 [0051] 处理器中还可以设置存储器 110 ,并且被配置为存储指令和数据。 在一些实施例中,处理器中的存储器 110 是一个缓存。 存储器可以存储处理器使用或循环使用的指令或数据 110 . 如果处理器 110 需要再次使用指令或数据时,可以直接从内存中调用指令或数据。 这避免了重复访问并减少了处理器的等待时间 110 ,从而提高系统的效率。 [0052] 在一些实施例中,处理器 110 可以包括一个或多个接口。 该接口可以包括内部集成电路(I2C)接口、内部集成电路声音(I2S)接口、脉冲编码调制(PCM)接口、通用异步接收器/发送器(UART)接口、移动工业处理器接口 (MIPI)、通用输入/输出(GPIO)接口、订户身份模块(SIM)接口、通用串行总线(USB)接口等。 [0053] I2C 接口是双向同步串行总线,包括串行数据线 (SDA) 和串行时钟线 (SCL)。 在一些实施例中,处理器 110 可以包括多个I2C总线。 处理器 110 可以单独耦合到触摸传感器、充电器、闪光灯、相机 193 等通过使用不同的 I2C 总线接口。 例如,处理器no可以通过I2C接口与触摸传感器耦合,使得处理器no通过I2C总线接口与触摸传感器通信,实现移动终端的触摸功能。 100 . [0054] I2S 接口可用于音频通信。 在一些实施例中,处理器可以包括多个I2S总线。 处理器no可以耦合到音频模块 170 使用I2S总线,实现处理器No与音频模块的通信 170 . 在一些实施例中,音频模块 170 可以向无线通信模块发送音频信号 160 通过I2S接口,实现蓝牙耳机接听电话的功能。 [0055] PCM 接口也可用于音频通信以对模拟信号进行采样、量化和编码。 在一些实施例中,音频模块 170 以及无线通讯模块 160 可以通过使用PCM总线接口来耦合。 在一些实施例中,音频模块 170 可替代地向无线通信模块发送音频信号 160 通过PCM接口,实现蓝牙耳机接听电话的功能。 I2S 接口和 PCM 接口都可以用于音频通信。 [0056] UART 接口是用于异步通信的通用串行数据总线。 总线可以是双向通信总线。 总线对要传输的数据实现串行通信和并行通信的转换。 在一些实施例中,UART接口通常被配置为将处理器no连接到无线通信模块 160 . 例如,处理器不与无线通信模块中的蓝牙模块通信 160 通过使用UART接口,实现蓝牙功能。 在一些实施例中,音频模块 170 可以向无线通信模块发送音频信号 160 通过UART接口,实现蓝牙耳机播放音乐的功能。 [0057] MIPI接口可配置为连接处理器 110到显示器等外围设备 194 和相机 193 . MIPI接口包括相机串行接口(CSI)、显示器串行接口(DSI)等。 在一些实施例中,处理器 110 与相机通信 193 通过CSI接口,实现移动终端的拍照功能 100 . 处理器 110 与显示器通信 194 通过DSI接口,实现移动终端的显示功能 100 . [0058] GPIO 接口可以通过软件进行配置。 GPIO接口可以配置为控制信号,也可以配置为数据信号。 在一些实施例中,GPIO接口可以被配置为连接处理器 110 到相机 193 , 显示器 194 , 无线通讯模块 160 , 音频模块 170 , 传感器模块 180 ,等等。 GPIO接口也可以配置为I2C接口、I2S接口、UART接口、MIPI接口等。 [0059] USB接口 130 是符合USB标准规范的接口,具体可以是Mini USB接口、Micro USB接口、USB Type C接口等。 USB接口 130 可配置为连接充电器为移动终端充电 100 ,或者可以配置为在移动终端之间传输数据 100 和外围设备。 USB接口 130 或者,可以配置为连接到耳机,通过使用耳机播放音频。 该接口可以替代地被配置为连接到另一个移动终端,例如,AR设备。 [0060] 可以理解的是,本发明实施例所示的各模块之间的接口连接关系仅为举例说明,并不构成对移动终端的结构限制 100 . 在本申请的其他一些实施例中,移动终端 100 也可以采用与上述实施例不同的接口连接方式,或者多种接口连接方式的组合。 [0061] 充电管理模块 140 配置为接收来自充电器的充电输入。 充电器可以是无线充电器或有线充电器。 在一些有线充电实施例中,充电管理模块 140 可通过USB接口接收来自有线充电器的充电输入 130 . 在一些无线充电实施例中,充电管理模块 140 可以通过移动终端的无线充电线圈接收无线充电输入 100 . 给电池充电时 142 ,充电管理模块 140 还可以通过电源管理模块为移动终端供电 141 . [0062] 电源管理模块 141 配置为连接电池 142 ,充电管理模块 140 , 和处理器 110 . 电源管理模块 141 从电池接收输入 142 和/或充电管理模块 140 , 并为处理器供电 110 , 内部存储器 121 , 显示器 194 , 相机 193 , 无线通讯模块 160 ,等等。 电源管理模块 141 还可以用于监测电池容量、电池循环次数、电池健康状态(漏电和阻抗)等参数。 在一些其他实施例中,电源管理模块 141 或者可以设置在处理器中 110 . 在一些其他实施例中,电源管理模块 141 和充电管理模块 140 或者可以将其设置在同一设备中。 [0063] 一种移动终端的无线通信功能 100 可以通过使用天线来实现 1 , 天线 2 , 移动通信模块 150 , 无线通讯模块 160 、调制解调器处理器、基带处理器等。 [0064] 天线 1 和天线 2 被配置为发送和接收电磁波信号。 移动终端中的每个天线 100 可以被配置为覆盖单个或多个通信频带。 可以进一步复用不同的天线以提高天线利用率。 例如,天线 1 可以复用为无线局域网的分集天线。 在一些其他实施例中,天线可以与调谐开关结合使用。 [0065] 移动通信模块 150 可提供应用于移动终端的无线通信解决方案 100 其中包括2G/3G/4G/5G等。 移动通信模块 150 可以包括至少一个滤波器、开关、功率放大器、低噪声放大器(LNA)等。 移动通信模块 150 可以通过天线接收电磁波 1 ,对接收到的电磁波进行滤波、放大等处理,并将接收到的电磁波传送到调制解调器处理器进行解调。 移动通信模块 150 可以进一步放大调制解调处理器调制的信号,并通过天线将信号转换为电磁波 1 为辐射。 在一些实施例中,移动通信模块的至少一些功能模块 150 可以设置在处理器中 110 . 在一些实施例中,移动通信模块的至少一些功能模块 150 以及处理器的至少一些模块 110 可以设置在同一设备中。 [0066] 调制解调器处理器可以包括调制器和解调器。 调制器用于将要发送的低频基带信号调制成中高频信号。 解调器被配置为将接收到的电磁波信号解调为低频基带信号。 然后,解调器将解调得到的低频基带信号传送给基带处理器进行处理。 低频基带信号经过基带处理器处理后,传送到应用处理器。 应用处理器通过音频设备(不限于扬声器)输出音频信号 170 A、接收器 170 B等),或使用显示器显示图像或视频 194 . 在一些实施例中,调制解调器处理器可以是独立设备。 在一些其他实施例中,调制解调器处理器可以独立于处理器 110 ,并与移动通讯模块设置于同一装置中 150 或其他功能模块。 [0067] 无线通讯模块 160 可提供应用于移动终端的无线通信解决方案 100 其中包括无线局域网 (WLAN)(例如,无线保真 (Wi-Fi) 网络)、蓝牙 (BT)、全球导航卫星系统 (GNSS)、调频 (FM)、近场通信 ( NFC)、红外线(IR)等。 无线通讯模块 160 可以是集成了至少一个通信处理模块的一个或多个设备。 无线通讯模块 160 使用天线接收电磁波 2 ,对电磁波信号进行调频和滤波处理,将处理后的信号发送给处理器 110 . 无线通讯模块 160 还可以从处理器接收待发送信号 110 ,对信号进行调频放大,利用天线将信号转换成电磁波 2 为辐射。 [0068] 在本申请的一些实施例中,当确定所有应用都没有数据传输时,处理器 110 可以指示无线通信模块中的WLAN模块(例如,Wi-Fi模块)进入休眠状态。 当 WLAN 模块处于休眠状态时,如果应用程序需要发送心跳包,处理器 110 表示无线通信模块中的BT模块建立移动终端之间的通信连接100 和电子设备 200 ,并通过通信连接发送每个应用程序的心跳包。 当确定一个或多个应用程序需要发送数据(非心跳包)时,处理器 110 唤醒WLAN模块,建立移动终端之间的WLAN连接 100 以及电子装置,并通过WLAN连接传输一个或多个应用程序的数据。 也就是说,当移动终端上的应用程序 100 只需要发送心跳包,移动端 100 不唤醒WLAN模块,而是使用功耗比WLAN模块低的BT模块建立通信连接。 这样就降低了WLAN模块的功耗,降低了移动终端的整体功耗。 100 降低了。 [0069] 在一些实施例中,天线 1 移动终端的 100 耦接移动通讯模块 150 , 和天线 2 耦接无线通讯模块 160 ,让移动端 100 可以通过使用无线通信技术与网络和其他设备进行通信。 无线通信技术可以包括诸如全球移动通信系统(GSM)、通用分组无线电服务(GPRS)、码分多址(CDMA)、宽带码分多址(WCDMA)、时分码等技术。 分多址 (TD-SCDMA)、长期演进 (LTE)、BT、GNSS、WLAN、NFC、FM 和/或 IR。 GNSS可以包括全球定位系统(GPS)、全球导航卫星系统(GLONASS)、北斗导航卫星系统(BDS)、准天顶卫星系统(QZSS)和/或基于卫星的增强系统( SBAS)。 [0070] 移动终端 100 使用GPU实现显示功能,显示 194 、应用处理器等。 GPU是用于图像处理的微处理器,与显示器相连 194 和应用处理器。 GPU 被配置为执行图形渲染的数学和几何计算。 处理器 110 可以包括一个或多个GPU,它们执行程序指令以生成或改变显示信息。 [0071] 显示器 194 被配置为显示图像、视频等。 显示器 194 包括显示面板。 显示面板可以是液晶显示器(LCD)、有机发光二极管(OLED)、有源矩阵有机发光二极管(AMOLED)、柔性发光二极管(FLED)、mini-LED 、微型LED、微型OLED、量子点发光二极管(QLED)等。 在一些实施例中,移动终端 100 可能包括一个或 N 个显示器 194 ,其中 N 是大于 1 的正整数。 [0072] 移动终端 100 可以通过ISP实现拍照功能,摄像头 193 、视频编解码器、GPU、显示器 194 、应用处理器等。 [0073] ISP配置为处理摄像头反馈的数据 193 . 例如,在拍摄过程中,快门打开,光线通过镜头传输到相机的感光元件,将光信号转换为电信号。 相机的感光元件将电信号传送给ISP进行处理,使ISP将电信号转换成肉眼可见的图像。 ISP可以进一步对图像的噪声、亮度和肤色进行算法优化。 ISP可以进一步优化拍摄场景的参数,例如曝光和色温。 在一些实施例中,ISP可以设置在相机中 193 . [0074] 相机 193被配置为捕获静态图像或视频。 镜头为物体产生光学影像,并将光学影像投射到感光元件上。 光敏元件可以是电荷耦合器件(CCD)或互补金属氧化物半导体(CMOS)光电晶体管。 感光元件将光信号转换为电信号,然后将电信号传输到ISP,转换为数字图像信号。 ISP将数字图像信号输出到DSP进行处理。 DSP将数字图像信号转换为RGB或YUV等标准格式的图像信号。 在一些实施例中,移动终端 100 可能包括一个或 N 个摄像头 193 ,其中 N 是大于 1 的正整数。 [0075] 数字信号处理器被配置为处理数字信号,并且可以处理除了数字图像信号之外的另一个数字信号。 例如,当移动终端 100 选择频率,数字信号处理器用于对该频率的能量进行傅里叶变换。 [0076] 视频编解码器被配置为压缩或解压缩数字视频。 移动终端 100 可能支持一种或多种视频编解码器。 这样,移动终端 100 可以播放或录制多种编码格式的视频,例如,运动图像专家组(MPEG)-1、MPEG-2、MPEG-3和MPEG-4。 [0077] NPU 是一种神经网络 (NN) 计算处理器。 NPU通过借鉴生物神经网络结构的经验,例如借鉴人脑神经元之间传输方式的经验,对输入信息进行快速处理,进而不断进行自学习。 NPU可用于实现移动终端智能认知等应用 100 例如,图像识别、面部识别、语音识别和文本理解。 [0078] 外部存储器接口 120 可用于连接micro SD卡等外置存储卡,扩展移动终端的存储能力 100 . 外部存储卡通过外部存储接口与处理器通讯 120 ,实现数据存储功能。 例如,音乐或视频等文件存储在外部存储卡中。 [0079] 内部存储器 121 可以被配置为存储计算机可执行程序代码,并且可执行程序代码包括指令。 内部存储器 121 可以包括程序存储区和数据存储区。 程序存储区可以存储操作系统、至少一种功能(例如,声音播放功能或图像播放功能)所需的应用程序等。 数据存储区域可以存储在使用移动终端的过程中创建的数据(例如,音频数据或地址簿) 100 ,等等。 此外,内部存储器 121 可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储设备、闪存设备或通用闪存(universal flash storage,UFS)。 处理器 110 执行移动终端的各种功能应用和数据处理 100 通过运行存储在内部存储器中的指令 121 和/或存储在处理器中的存储器中的指令。 [0080] 移动终端 100 可以通过音频模块实现音乐播放或录音等音频功能 170 , 演讲者 170 A、接收器 170 B、麦克风 170 C、耳机插孔 170 D、应用处理器等。 [0081] 音频模块 170 用于将数字音频信息转换为模拟音频信号输出,还用于将模拟音频输入转换为数字音频信号。 音频模块 170 还可被配置为对音频信号进行编码和解码。 在一些实施例中,音频模块 170 可以设置在处理器中 110 ,或者音频模块的一些功能模块170 可以设置在处理器中 110 . [0082] 演讲者 170 A,也称为“喇叭”,被配置为将音频电信号转换为声音信号。 移动终端 100 可用于听音乐或使用扬声器听免提通话 170 一个。 [0083] 收件人 170 B,也称为“听筒”,用于将音频电信号转换为声音信号。 当移动端 100 用于接听电话或收听语音信息,放置听筒即可收听语音 170 B 接近人耳。 [0084] 麦克风 170 C,也称为“麦克风”或“麦克风”,用于将声音信号转换为电信号。 在拨打电话或发送语音信息时,用户可以将麦克风放在 170 C 靠近人嘴发声,向麦克风输入声音信号 170 C. 至少一个麦克风 170 C可以设置在移动终端中 100 . 在一些其他实施例中,两个麦克风 170 C可以设置在移动终端中 100 . 除了采集声音信号外,麦克风还可以实现降噪功能。 在一些其他实施例中,三个、四个或更多麦克风 170 C可以设置在移动终端中 100 ,用于采集声音信号、降噪、识别声源、实现定向录音等功能。 [0085] 耳机插孔 170 D 配置为连接到有线耳机。 耳机插孔 170 D可能是USB接口 130 ,或者可以是 3.5 毫米开放移动终端平台 (OMTP) 标准接口或美国蜂窝电信工业协会 (CTIA) 标准接口。 [0086] 钥匙 190 包括电源键、音量键等。 钥匙 190 可以是机械键,也可以是触摸键。 移动终端 100 可以接收按键输入,并生成与移动终端的用户设置和功能控制相关的按键信号输入 100 . [0087] 电机 191 可能会产生振动警报。 电机 191 可用于产生来电振动提示,或产生触摸操作振动反馈。 例如,在不同的应用程序(例如拍照和音频播放)上进行的触摸操作可以对应不同的振动反馈效果。 电机 191 可以进一步实现对显示器不同区域的触摸操作 194 以对应不同的振动反馈效果。 不同的应用场景(如时间提醒、信息接收、闹钟、游戏等)也可能对应不同的震动反馈效果。 也可以定制触摸操作的振动反馈效果。 [0088] 指标 192 可以是指示灯,可以用于指示充电状态和电量变化,也可以用于指示消息、未接电话、通知等。 [0089] SIM卡接口 195 配置为连接到 SIM 卡。 SIM卡可以插入SIM卡接口 195 或从 SIM 卡接口中移除 195 , 实现与移动终端的联系或分离 100 . 移动终端 100 可以支持一个或N个SIM卡接口,其中N为大于1的正整数。 SIM卡接口 195 可以支持nano-SIM卡、micro-SIM卡、SIM卡等。 同一个SIM卡接口可以插入多张卡 195 同时。 多个卡可以是相同类型或不同类型。 SIM卡接口 195 可能与不同类型的 SIM 卡兼容。 SIM卡接口 195 也可能与外部存储卡兼容。 移动终端 100 通过SIM卡与网络进行交互,实现通话、数据通信等功能。 在一些实施例中,移动终端 100使用eSIM,即嵌入式SIM卡。 eSIM卡可嵌入移动终端 100 , 和移动端分不开 100 . [0090] 一种移动终端的软件系统 100 可以使用分层架构、事件驱动架构、微内核架构、微服务架构或云架构。 本发明实施例以分层架构的Android系统为例,对移动终端的软件结构进行说明。 100 . [0091] 图2B是移动终端的软件结构框图 100 根据本发明的这个实施例。 [0092] 在分层架构中,软件被划分为多个层次,每一层都有明确的作用和职责。 层通过使用软件接口相互通信。 在一些实施例中,Android系统自上而下分为四层,分别为应用层、应用框架层、Android运行时(Android runtime)和系统库、内核层。 [0093] 如图2B所示,应用层可以包括一系列应用包,包括移动终端出厂前预配置的应用,或者用户安装后在应用市场等方式安装的应用。 移动终端出厂。 这些应用包括但不限于相机、图库、日历、电话、地图、导航、WLAN、蓝牙、音乐、视频、短信、浏览器、微信、淘宝、支付宝等应用(图中只展示了一部分) )。 这些应用大多需要网络访问,例如导航、浏览器、微信、淘宝和支付宝。 [0094] 应用程序框架层为应用程序层的应用程序提供应用程序编程接口(API)和编程框架。 应用程序框架层包括一些预定义的功能。 [0095] 如图2B所示,应用框架层可以包括窗口管理器、内容提供器、视图系统、电话管理器、资源管理器、通知管理器等。 窗口管理器用于管理窗口程序。 窗口管理器可以获取显示大小、判断是否有状态栏、锁屏、截屏等。 内容提供者被配置为存储和获取数据并使应用程序可以访问数据。 数据可以包括视频、图像、音频、拨打和接听的电话、浏览历史和书签、地址簿等。 视图系统包括视觉控件,例如,用于显示文本的控件和用于显示图片的控件。 视图系统可以被配置为构建应用程序。 显示界面可以包括一个或多个视图。 例如,包括SMS通知图标的显示界面可以包括用于显示文本的视图和用于显示图片的视图。 手机管家,用于提供移动终端的通讯功能 100 例如,通话状态管理(包括通话连接和断开等)。 资源管理器为应用程序提供各种资源,例如本地化字符串、图标、图片、布局文件和视频文件。 通知管理器使应用程序能够在状态栏中显示通知信息,该信息可用于传达通知类型的消息,该消息可以在短暂停留后自动消失而无需用户交互。 例如,通知管理器用于指示下载完成、提供消息提醒等。 通知管理器还可以提供以图表或滚动条文本的形式出现在系统顶部状态栏的通知,例如后台运行的应用程序的通知,还可以提供 以对话窗口的形式出现在屏幕上的通知。 例如状态栏显示文字信息、播放提示音、移动终端振动、指示灯闪烁等。 [0096]在本申请的一些实施例中,应用框架层还可以包括第一模块,用于收集各应用在应用层向服务器发送的数据包,并根据数据包的类型确定是否要 唤醒 Wi-Fi 模块或唤醒蓝牙模块。 例如,当确定应用层的应用程序在特定时间段内没有任何应用程序发送数据包时,第一模块可以通过内核层的Wi-Fi驱动程序指示Wi-Fi模块休眠。 又例如,当应用层的应用程序确定需要发送心跳包时,第一模块可以通过内核层的蓝牙驱动程序唤醒蓝牙模块,并通过建立的链路发送心跳包。 蓝牙模块。 如果蓝牙模块不处于休眠状态,则可以通过蓝牙模块建立的链路直接发送心跳包。 又例如,当应用层的应用程序确定需要发送数据包(非心跳数据包)时,第一模块可以通过内核层的Wi-Fi驱动程序唤醒Wi-Fi模块,并发送 应用程序的数据包通过Wi-Fi模块建立的链接。 [0097] 在本申请的另一个实施例中,第一模块还可以用于在应用层采集应用的心跳包,并在一段时间内集中发送应用的心跳包。 另外,在集中发送应用程序的心跳包时,通过内核层的蓝牙驱动程序唤醒蓝牙模块,通过蓝牙链路发送心跳包。 [0098] 在本申请的一些其他实施例中,所述第一模块还可以用于识别报文(如设备ID、设备IP地址、端口号和所使用的协议信息、TCP链路建立报文等) 在移动终端之间建立传输层链路 100 和电子设备 200 ,唤醒蓝牙模块,并通过蓝牙链路传输用于建立传输层链路的数据包。 需要说明的是,这种情况下,蓝牙链路只建立了物理层链路,没有建立传输层链路。 例如,控制报文(如用于广播移动终端地址的报文) 100 ) 移动端之间 100 和电子设备 200 可以携带传输层链路的报文。 换言之,可以预先建立传输层链路。 随后,当移动终端需要建立蓝牙链路或Wi-Fi链路时,在建立相应的物理层链路后,移动终端可以直接使用预先建立的传输层链路。 现有技术中,物理层Wi-Fi链路或物理层蓝牙链路建立后,还需要进一步建立传输层链路来传输报文。 在本申请实施例的方法中,与传统技术相比,由于提前建立了传输层链路,在移动终端唤醒Wi-Fi模块或蓝牙模块后,可以快速启动报文传输,从而 提高Wi-Fi模块或蓝牙模块的工作效率,有助于降低Wi-Fi模块或蓝牙模块的功耗。 因此,降低了移动终端的整体功耗。 [0099] Android 运行时包括一个内核库和一个虚拟机。 Android 运行时调度和管理 Android 系统。 [0100] 内核库包括两部分:一是Java语言需要调用的函数,二是Android的内核库。 [0101]应用层和应用框架层运行在虚拟机中。 虚拟机将应用层和应用框架层的Java文件作为二进制文件执行。 虚拟机被配置为执行对象生命周期管理、堆栈管理、线程管理、安全和异常管理以及垃圾收集等功能。 [0102] 系统库可以包括多个功能模块,例如表面管理器、媒体库、三维图形处理库(例如OpenGL ES)、二维图形引擎(例如SGL)。 [0103] 表面管理器被配置为管理显示子系统并为多个应用提供2D和3D层的融合。 [0104] 媒体库支持各种常见音视频格式、静态图片文件等的播放和录制。 媒体库可支持MPEG-4、H.264、MP3、AAC、AMR、JPG、PNG等多种音视频编码格式。 [0105] 三维图形处理库用于实现三维图形绘制、图像渲染、合成、图层处理等。 [0106] 2D图形引擎是用于2D绘图的绘图引擎。 [0107] 内核层是介于硬件和软件之间的一层。 内核层至少包括显示驱动程序、摄像头驱动程序、音频驱动程序和传感器驱动程序。 [0108] 电子设备 200 在这个应用程序中是一个可以为移动终端提供无线网络访问功能的设备 100 例如,无线路由器、便携式 Wi-Fi 设备(也称为随附的 Wi-Fi 设备或移动 Wi-Fi 设备)或客户端设备 (CPE),或者可能是提供 移动端热点 100 例如,可以是手机或平板电脑。 在这个应用程序中,电子设备 200 具有蓝牙模块,该蓝牙模块可以提供经典蓝牙(或称为传统蓝牙)功能和/或蓝牙低功耗功能。 [0109] 需要说明的是,对于电子设备的结构 200 ,参考移动端的结构 100 在图 2A 中。 电子设备 200 可以具有比图2A所示结构更多或更少的组件,或者组合一些组件,或者拆分一些组件,或者具有不同的组件布置。 所示组件可以以硬件、软件或软件和硬件的组合来实现。 [0110] 例如,当电子设备 200 是路由器,电子设备 200 可以包括处理器、存储器、无线通信模块、天线、电源模块、被配置为连接到互联网的网络接入模块等。 无线通信模块包括Wi-Fi模块和蓝牙模块。 Wi-Fi模块可用于与移动终端建立Wi-Fi连接 100 . 这样,移动终端 100 可以通过电子设备的网络访问模块访问互联网 200 . 蓝牙模块可用于与移动终端建立蓝牙连接(经典蓝牙连接或BLE连接) 100 ,让移动端 100 可以通过电子设备的网络访问模块访问互联网 200 . [0111] 其他内容参见移动终端相关结构说明 100 在图 2A 中。 细节不在此描述。 [0112] 又例如,当电子设备 200 是随附的 Wi-Fi 设备,电子设备 200 可以包括处理器、存储器、无线通信模块、天线、电源模块、移动通信模块等。 移动通信模块可以被配置为提供应用于电子设备的无线通信解决方案 100 其中包括2G/3G/4G/5G等。 [0113]无线通信模块包括Wi-Fi模块和蓝牙模块。 Wi-Fi模块可用于与移动终端建立Wi-Fi连接 100 . 这样,移动终端 100 可通过电子设备的移动通信模块接入移动通信网络 200 . 蓝牙模块可用于与移动终端建立蓝牙连接(经典蓝牙连接或BLE连接) 100 ,让移动端 100 可通过电子设备的移动通信模块接入移动通信网络 200 . [0114] 其他内容参见移动终端相关结构说明 100 在图 2A 中。 细节不在此描述。 [0115] 以下实施例中的所有技术方案均可以在移动终端中实现 100 具有上述硬件架构和软件架构。 [0116] 下面结合附图对本申请实施例提供的技术方案进行详细说明。 [0117] 例如,默认情况下,移动终端可以一直使用本申请实施例提供的方法,以降低移动终端的功耗。 或者,默认情况下,在特定场景下,移动终端可以采用本申请实施例提供的方法来降低移动终端的功耗。 例如,默认情况下,当电量低于预设值时(例如电量低于20%),移动终端可以自动开始使用本申请实施例提供的方法,以减少 移动终端的功耗。 又例如,默认情况下,当启用的应用程序的数量大于预设数量(例如5个)时,移动终端可以自动开始使用本申请实施例提供的方法,以降低应用程序的功耗。 移动终端。 又例如,当确定移动终端启用特定应用程序时(例如,特定应用程序是需要频繁发送心跳包的应用程序,例如即时通讯应用程序),移动终端自动开始使用 本申请实施例提供的方法,以降低移动终端的功耗。 [0118] 在其他一些示例中,也可以在移动终端中设置开关,用户可以通过该开关手动开启或关闭本申请实施例提供的降低移动终端功耗的功能。 例如,如图 ( 1 ) 在图 3 中,一个开关控制 301 可以设置在“设置”应用中的“WLAN”设置页面,供用户手动开启或关闭移动终端的省电功能。 再举一个例子,如( 2 ) 在图 3 中,一个开关控制 302 可以设置在“设置”应用程序中,供用户手动开启或关闭移动终端的省电功能。 [0119] 图4为本申请实施例提供的一种降低移动终端功耗的方法流程示意图。 详情如下: [0120] 小号 401 :移动终端与电子设备建立Wi-Fi通信连接和蓝牙通信连接,并通过电子设备与服务器交互。 [0121] 在一些实施例中,移动终端自动开启省电功能或用户手动开启省电功能后,移动终端可以自动开启或提示用户开启手机的Wi-Fi功能和蓝牙功能。 终端,分别与电子设备建立Wi-Fi连接和蓝牙连接。 蓝牙连接可以是经典的蓝牙连接,也可以是低功耗蓝牙(Bluetooth low energy,BLE)连接。 [0122]如果移动终端首次与电子设备建立Wi-Fi连接,用户需要选择电子设备对应的Wi-Fi名称、输入密码等,或者使用扫描等其他方式 快速响应码,用于建立移动终端与电子设备之间的Wi-Fi连接。 如果移动终端不是第一次与电子设备建立Wi-Fi连接,移动终端会存储电子设备对应的Wi-Fi名称和密码等信息,移动终端可以自动建立Wi-Fi连接。 - 与电子设备的 Fi 连接。 [0123] 与建立Wi-Fi连接类似,如果移动终端首次与电子设备建立蓝牙连接,用户需要进行选择电子设备对应的蓝牙名称等操作,然后移动终端 终端建立与电子设备的蓝牙连接。 如果移动终端之前已经与电子设备建立了蓝牙连接,则移动终端存储该电子设备对应的蓝牙名称等信息,随后移动终端可以自动与电子设备建立蓝牙连接。 [0124] 在其他一些实施例中,移动终端在开启Wi-Fi功能时,还可以询问用户是否开启功耗降低功能。 如果用户选择开启省电功能,移动终端可以自动开启或提示用户开启移动终端的蓝牙功能。 移动终端与电子设备建立Wi-Fi连接和蓝牙连接的过程与上述实施例相同,在此不再赘述。 [0125] 在其他一些实施例中,移动终端在开启Wi-Fi功能并与电子设备建立Wi-Fi连接后,还可以判断该电子设备是否为预设设备。 预设设备是能够支持本申请实施例提供的方法,能够与移动终端建立Wi-Fi连接和蓝牙连接的设备。 如果移动终端确定电子设备为预设设备,则移动终端自动开启省电功能,自动开启蓝牙功能,并与电子设备建立蓝牙连接。 [0126] 在其他一些实施例中,在同时开启Wi-Fi功能和蓝牙功能后,移动终端还可以自动开启功耗降低功能,或者询问用户是否开启功耗降低功能。 移动终端与电子设备建立Wi-Fi连接和蓝牙连接的过程参见上述实施例。 细节不在此描述。 [0127]需要说明的是,在一些示例中,移动终端与电子设备建立Wi-Fi连接和蓝牙连接后,移动终端首先通过Wi-Fi连接向电子设备发送数据包,然后 电子设备将接收到的数据包发送给服务器。 或者,电子设备从服务器接收到要发送给移动终端的数据包,然后电子设备通过Wi-Fi连接将数据包发送给移动终端。 换言之,移动终端通过电子设备与服务器进行通信。 移动终端通过Wi-Fi连接与电子设备进行通信。 在这个过程中,由于一段时间内没有数据包传输,蓝牙连接可能会自动断开。 移动终端的蓝牙模块也可以处于休眠状态。 在一些其他示例中,当移动终端通过使用Wi-Fi连接发送数据包时,移动终端可以替代地保持与电子设备的蓝牙连接。 在其他一些示例中,移动终端与电子设备建立Wi-Fi连接后,移动终端和电子设备均开启蓝牙功能,但此时不建立蓝牙连接。 然而,应当注意,移动终端和电子设备之间已经预先建立了连接。 也就是说,在这种情况下,移动终端和电子设备都存储了彼此的蓝牙地址等信息,以便移动终端和电子设备能够快速建立连接并随后发送数据包。 [0128] 小号 402 :移动终端在确定第一时间段内没有数据包发送时,控制Wi-Fi模块进入休眠状态。 [0129] Wi-Fi模块进入休眠状态也可以理解为Wi-Fi模块处于低功耗工作模式。 在低功耗工作模式下,暂停Wi-Fi模块的大部分功能,以降低整个Wi-Fi模块的功耗。 例如,Wi-Fi模块进入睡眠状态包括Wi-Fi模块处于睡眠模式或深度睡眠模式。 在休眠模式下,移动终端的系统运行时钟保持不变,Wi-Fi模块可以通过串口或网络数据包唤醒,GPIO(通用输入输出)端口保持输出。 深度睡眠模式下,移动终端系统运行时钟减半,Wi-Fi模块可通过串口或网络数据包唤醒,GPIO口保持输出,唤醒响应时间 略长于睡眠模式。 [0130] 当移动终端在第一时间段内既没有向电子设备发送数据包也没有接收到电子设备的数据包时,移动终端可以控制移动终端的Wi-Fi模块进入休眠状态,以降低电量 Wi-Fi 模块的消耗。 在一个示例中,当移动终端在第一时间段内不需要发送或接收任何数据包时,即当移动终端不需要发送或接收随后的第二个数据包时(例如,与 移动终端上的各个应用的服务)和后面的第一个报文(例如,应用的心跳报文或用于建立传输层链路的报文),移动终端可以控制移动终端的Wi-Fi模块 进入睡眠状态。 又如,当移动终端在第一时间段内不需要发送或接收后续的第二报文(例如,与移动终端上各个应用的业务相关的报文)时,移动终端可以控制Wi -移动终端的Fi模块进入休眠状态。 也就是说,当移动终端在第一时间内只需要发送第一包时,移动终端也可以控制移动终端的Wi-Fi模块进入休眠状态,唤醒蓝牙模块,发送 第一个数据包通过使用蓝牙模块。 [0131]例如,当移动终端处于亮屏状态时,移动终端上的应用程序不会通过电子设备向服务器请求数据包,服务器也不会通过电子设备向移动终端发送数据包。 . 在这种情况下,在第一时间段之后,移动终端可以断开与电子设备的Wi-Fi连接,并控制移动终端的Wi-Fi模块进入休眠状态。 [0132] 又例如,当移动终端在特定时间段内没有接收到用户的操作,并且移动终端没有运行视频应用等应用时,移动终端关闭屏幕并进入屏幕关闭 状态。 当移动终端处于熄屏状态且移动终端未运行音频相关应用时,经过第一时间段后,移动终端可以断开与电子设备的Wi-Fi连接,并控制Wi-Fi 移动终端的Fi模块进入休眠状态。 [0133] 小号 403 :当Wi-Fi模块处于休眠状态时,如果移动终端确定需要发送第一包,则移动终端唤醒蓝牙模块并以蓝牙连接的方式向电子设备发送第一包, 然后电子装置将第一封包传送至伺服器。 第一报文是移动终端上的应用程序的心跳报文,或者是用于建立传输层链路的报文。 心跳包是移动终端上的应用程序与该应用程序对应的服务器之间交互的心跳包,可以包括移动终端向服务器发送的心跳请求,以及服务器向移动终端返回的心跳响应。 . [0134] 如上所述,在步骤 S 403 ,移动终端与电子设备之间已建立蓝牙连接(例如BLE连接)。 移动终端和电子设备分别存储彼此的蓝牙地址等信息。 在确定需要发送第一包后,移动终端可以唤醒蓝牙模块,与电子设备建立蓝牙连接。 接着,通过蓝牙连接将第一封包发送至电子装置,以使电子装置进一步将第一封包发送至服务器。 或者,移动终端与电子设备始终保持蓝牙连接,此时可以直接通过蓝牙连接传输第一数据包。 [0135] 需要注意的是,移动终端维护与电子设备的Wi-Fi连接和蓝牙连接的信息。 具体的,移动终端可以保证在发送第一数据包时,移动终端可以自动连接到电子设备对应的蓝牙连接,将第一数据包发送给电子设备,避免连接到其他电子设备发送数据包。 将第一封包传送至另一电子装置,确保封包传输安全。 [0136] 在本申请的一些实施例中,第一报文为需要在移动终端与电子设备之间传输的心跳报文。 当移动终端处于休眠状态时,移动终端上运行的各个应用程序仍需要周期性地向该应用程序对应的服务器发送心跳包,以通知服务器该应用程序在线。 现有技术中,当移动终端上运行的应用程序需要向服务器发送心跳包时,移动终端唤醒Wi-Fi模块,与电子设备建立Wi-Fi连接,发送心跳包 通过使用 Wi-Fi 连接。 当移动终端上运行的应用较多时,发送心跳包的场合也较多。 因此,唤醒Wi-Fi模块的场合也更多。 也就是说,Wi-Fi模块处于工作状态的时间较长,功耗较高。 [0137]但是,在本申请实施例中,当确定移动终端的应用需要发送心跳包时,移动终端可以不唤醒Wi-Fi模块,而是唤醒功耗更低的蓝牙模块(相比 Wi-Fi 模块),并通过蓝牙连接发送心跳包。 因此,可以降低移动终端的整体功耗。 [0138] 在本申请的其他一些实施例中,移动终端也可以选择收集各个应用程序需要发送的心跳包,并在特定的时间段内集中发送心跳包。 当心跳包以集中方式发送时,蓝牙模块被唤醒,心跳包通过蓝牙连接发送至电子设备。 然后,电子装置将心跳封包发送至应用程序对应的服务器。 [0139] 在本申请的一些其他实施例中,第一报文也可以是用于建立传输的报文(如设备ID、设备IP地址、端口号和所使用协议的信息、TCP链路建立报文等)。 层链接由移动终端。 在某些场景下,移动终端可以通过蓝牙链路传输用于建立传输层链路的报文。 需要说明的是,这种情况下,蓝牙链路只建立了物理层链路,没有建立传输层链路。 例如,移动终端与电子设备之间的控制报文(如用于广播移动终端地址的报文)可以携带传输层链路的报文。 换言之,可以预先建立传输层链路。 例如,可以周期性地建立传输层链路。 随后,当移动终端需要建立蓝牙链路或Wi-Fi链路时,在建立相应的物理层链路后,移动终端可以直接使用预先建立的传输层链路。 由于预先建立了传输层链路,移动终端唤醒Wi-Fi模块或蓝牙模块后,可以快速启动数据包传输,从而提高Wi-Fi模块或蓝牙模块的工作效率,帮助 降低Wi-Fi模块或蓝牙模块的功耗。 因此,降低了移动终端的整体功耗。 [0140] 需要说明的是,在一些示例中,移动终端唤醒蓝牙模块发送第一包后,如果一段时间内没有发送第一包,则移动终端控制蓝牙模块断开蓝牙连接, 电子设备进入休眠状态,以降低功耗。 或者,在一些场景中,在一段时间内以集中的方式周期性地发送第一包。 例如,多个应用的​​心跳包在一段时间内以集中的方式周期性发送。 在这种情况下,移动终端在确定一个周期内的第一个数据包都发送完毕后,可以直接控制蓝牙模块断开与电子设备的蓝牙连接,进入休眠状态,等待下一个周期。 换言之,移动终端在发送一个周期的第一个数据包后,不需要等待一段时间来断开与电子设备的蓝牙连接。 这有助于进一步降低蓝牙模块的功耗。 在其他一些示例中,在移动终端唤醒蓝牙模块发送第一数据包后,移动终端可以不断开连接。 换言之,移动终端与电子设备长期保持蓝牙连接。 [0141] 小号 404:如果移动终端确定需要发送第二个数据包,则移动终端唤醒Wi-Fi模块,以Wi-Fi连接的方式将第二个数据包发送给电子设备,然后电子设备再发送第二个数据包。 数据包到服务器。 或者,当确定服务器向电子设备下发要发送给移动终端的第二数据包时,电子设备恢复与移动终端的Wi-Fi连接。 该场景下,移动终端唤醒Wi-Fi模块,并以Wi-Fi连接方式接收电子设备发送的第二报文。 [0142] 第二报文是与第一报文不同的另一个需要移动终端发送的报文,可以包括与移动终端上的各个应用的业务相关的报文(例如业务数据)。 [0143] 在本申请的一些实施例中,当移动终端确定需要发送第二个数据包时,如果移动终端仍然保持与电子设备的蓝牙连接,则移动终端可以主动断开蓝牙连接,建立Wi-Fi连接 ,并以Wi-Fi连接方式发送第二个数据包。 在一些示例中,如果此时移动终端仍需要向电子设备发送第一数据包,则移动终端也可以通过Wi-Fi连接的方式发送第一数据包,然后再发送第二数据包。 在其他一些示例中,如果移动终端确定第一报文是具有低延迟要求的报文或者是不重要的报文(例如,用于建立物理层链路的报文),则移动终端可以首先发送 Wi-Fi连接方式的第二个数据包,然后发送第一个数据包或直接丢弃第一个数据包。 [0144] 在本申请的一些其他实施例中,当移动终端与电子设备保持Wi-Fi连接时,如果移动终端检测到移动终端需要发送第一包,则移动终端可以直接通过Wi-Fi进行传输。 -Fi 连接。 [0145] 下面结合具体场景举例说明本申请实施例提供的方法。 [0146] 场景一:移动终端(如手机、平板电脑、智能音箱)与无线路由器建立Wi-Fi连接,通过无线路由器接入网络。 开启移动终端和无线路由器的蓝牙功能,移动终端和无线路由器之间已经建立了蓝牙连接。 [0147] 举例来说,如果移动终端在第一时间段内没有发送任何数据包(包括心跳包),则移动终端断开与无线路由器的Wi-Fi连接,并控制手机中配置的Wi-Fi模块。 终端进入休眠状态。 又例如,如果移动终端在第一时间段内不需要发送除心跳包以外的包(即第二包),则移动终端断开与无线路由器的Wi-Fi连接,并控制无线路由器的Wi-Fi连接。 移动终端中配置的Wi-Fi模块进入休眠状态。 当移动终端在第一时间段只需要发送心跳包时,移动终端也可以唤醒蓝牙模块,以蓝牙连接的方式发送心跳包。 [0148]当移动终端配置的Wi-Fi模块处于休眠状态时,如果移动终端检测到移动终端上运行的应用需要发送心跳包(无其他包),移动终端唤醒蓝牙模块 在移动终端中配置,与电子设备建立蓝牙连接(例如BLE),并通过蓝牙连接发送心跳包。 移动终端唤醒蓝牙模块后与电子设备建立蓝牙连接的过程可参见本领域相关技术,在此不再赘述。 在一些示例中,在发送心跳包后,如果移动终端在第二时间段内没有发送包,则移动终端断开与无线路由器的蓝牙连接,并控制移动终端中配置的蓝牙模块进入 睡眠状态。 [0149] 如果移动终端上的应用需要发送一个包(非心跳包,例如应用的业务相关包),移动终端唤醒移动终端的Wi-Fi模块,建立一个Wi - 与电子设备的 Fi 连接,并使用 Wi-Fi 连接发送数据包。 移动终端在唤醒Wi-Fi模块后与电子设备建立Wi-Fi连接的过程可参见本领域相关技术,在此不再赘述。 [0150] 如果无线路由器需要向移动终端发送来自服务器的数据包(非心跳数据包),则无线路由器与移动终端建立Wi-Fi连接,并通过 无线网络连接。 无线路由器与电子设备建立Wi-Fi连接的过程可参见本领域相关技术,在此不再赘述。 [0151] 场景二:移动终端(如手机、平板电脑、智能音箱等)与随行Wi-Fi设备建立Wi-Fi连接,通过随行Wi-Fi设备接入网络。 移动终端与随附的Wi-Fi设备的蓝牙功能开启,且移动终端与随附的Wi-Fi设备之间已预先建立了蓝牙连接。 [0152] 与场景一不同的是,随行Wi-Fi设备也是移动终端,配置有Wi-Fi模块,Wi-Fi模块的功耗是随行Wi-Fi设备的一种主要功耗。 随行Wi-Fi设备还配置有移动通信模块,该移动通信模块可用于提供应用于随行Wi-Fi设备的无线通信方案,包括2G/3G/4G/5G等。 也就是说,移动终端通过Wi-Fi连接与随身Wi-Fi设备进行交互,通过随身Wi-Fi设备的移动通信模块接入移动通信网络,实现网络接入功能。 [0153] 如果移动终端与随行Wi-Fi设备连接,则在确定与移动终端没有数据包传输时,随行Wi-Fi设备也可以控制随行Wi-Fi设备的Wi-Fi模块进入 睡眠状态。 随后,当随行Wi-Fi设备接收到网络侧下发的数据包,需要将该数据包发送给移动终端时,随行Wi-Fi设备唤醒Wi-Fi模块,并建立Wi-Fi连接到移动终端。 移动终端,传输网络侧下发的报文。 [0154] 以附带的Wi-Fi设备连接一个移动终端为例进行说明。 图5A和图5B为本申请实施例提供的另一种降低移动终端功耗的方法的流程示意图。 详情如下: [0155] 首先参见图5A,从随附的Wi-Fi设备一侧,降低移动终端功耗的方法包括步骤S 500 到步骤 S 505 , 如下: [0156] 小号 500. 打开随附的 Wi-Fi 设备。 [0157] 小号 501 . 随附的 Wi-Fi 设备确定是否存在与其他移动终端的 Wi-Fi 连接。 如果随行Wi-Fi设备判断一段时间内没有Wi-Fi连接,则随行Wi-Fi设备执行步骤S 502 . 如果随行Wi-Fi设备确定有Wi-Fi连接,则随行Wi-Fi设备执行步骤S 503 . [0158] 小号 502 . 随附的 Wi-Fi 设备控制 Wi-Fi 模块进入睡眠状态。 [0159] Wi-Fi 模块进入休眠状态,有助于降低随附 Wi-Fi 设备的功耗。 然后,随行的Wi-Fi设备继续监测是否有Wi-Fi连接,即执行步骤S 501 . [0160] 小号 503 . 附带的Wi-Fi设备判断是否需要在第一时间段传输数据(非心跳包)。 如果需要传输数据,则随附的 Wi-Fi 设备执行步骤 S 504 . 如果不需要传输数据,则随附的 Wi-Fi 设备执行步骤 S 505 . [0161] 例如,随行Wi-Fi设备具体判断随行Wi-Fi设备是否在第一时间段内从网络侧设备接收到需要发送给移动终端的数据,或者随行Wi-Fi设备是否 从移动终端接收需要发送到网络侧的数据。 [0162] 小号 504 . 随附的 Wi-Fi 设备通过使用 Wi-Fi 连接将数据传输到移动终端。 [0163] 然后,伴随的Wi-Fi设备继续监测是否需要传输数据,即执行步骤S 503 . [0164] 小号 505 . 随附的Wi-Fi设备控制Wi-Fi模块进入休眠状态,通过蓝牙连接向移动终端发送心跳包。 [0165] 当确定需要发送心跳包时,随行的Wi-Fi设备唤醒蓝牙模块(如果蓝牙模块不处于休眠状态则不需要唤醒),并通过蓝牙连接发送心跳包( 例如,一个 BLE 连接)在随附的 Wi-Fi 设备和移动终端之间。 然后,伴随的Wi-Fi设备继续监测是否需要传输数据,即执行步骤S 503 . 需要注意的是,在步骤 S 之后 503 ,如果随附的Wi-Fi设备确定需要传输数据,则在步骤S之前 504 ,如果Wi-Fi模块处于休眠状态,则伴随的Wi-Fi设备首先唤醒Wi-Fi模块,然后通过Wi-Fi模块传输数据。 [0166] 参见图5B,从移动终端一侧,降低移动终端功耗的方法包括步骤S 506 到步骤 S 511 , 如下: [0167] 小号 506 . 移动终端处于屏幕关闭状态。 [0168] 如果移动终端不处于熄屏状态,则移动终端处于数据传输场景或者不处于低功耗场景的概率较大。 因此,此处以移动终端处于屏幕关闭状态为例进行说明。 [0169] 小号 507 . 移动终端在第一时间段内判断是否需要传输数据(非心跳包)。 如果需要传输数据,移动终端执行步骤S 508 . 如果不需要传输数据,移动终端执行步骤S 509 . [0170] 例如,移动终端判断移动终端是否有数据需要发送给随附的Wi-Fi设备。 [0171] 小号 508 . 移动终端通过Wi-Fi模块提供的Wi-Fi连接将数据传输到随附的Wi-Fi设备。 [0172] 然后,移动终端继续监听是否需要传输数据,即执行步骤S 507 . [0173] 小号 509. 移动终端控制Wi-Fi模块进入休眠状态。 [0174] 小号 510 . 移动终端判断是否需要发送心跳包。 如果需要发送心跳包,移动终端执行步骤S 511 . 如果不需要发送心跳包,移动终端执行步骤S 507 . [0175] 小号 511 . 移动终端通过蓝牙连接向随附的Wi-Fi设备发送心跳包。 [0176] 移动终端可以唤醒蓝牙模块(如果蓝牙模块不处于休眠状态则不需要唤醒),并通过蓝牙连接(例如BLE连接)将心跳包传输到随附的Wi-Fi 设备。 然后,移动终端执行步骤S 507 . 需要注意的是,在步骤 S 之后 507 ,如果移动终端确定需要传输数据,则在步骤S之前 508 ,如果Wi-Fi模块处于休眠状态,移动终端首先唤醒Wi-Fi模块,然后通过Wi-Fi模块传输数据。 [0177] 在本申请实施例中,当随行Wi-Fi设备与移动终端之间只需要传输心跳包时,随行Wi-Fi设备与移动终端通过蓝牙连接传输心跳包。 功耗更低的蓝牙模块(与 Wi-Fi 模块相比)。 整体降低了随行Wi-Fi设备和移动终端分别唤醒各自Wi-Fi模块的概率,降低了任一Wi-Fi模块的工作时间,降低了随行Wi-Fi设备的功耗 降低了移动终端的功耗。 [0178] 也就是说,在这种场景下,除了移动终端的功耗之外,还可以降低随行Wi-Fi设备的功耗,延长随行Wi-Fi设备的待机时间。 [0179] 如果N个移动终端连接到随行Wi-Fi设备,当确定与所有N个移动终端都连接到随行Wi-Fi设备没有数据包传输时,随行Wi-Fi设备控制的Wi-Fi模块 伴随的 Wi-Fi 设备进入睡眠状态。 随后,当确定N个移动终端中的任意一个或多个移动终端只需要发送一个心跳包时,随行的Wi-Fi设备分别与一个或多个移动终端建立蓝牙连接,以发送每个移动终端之间交换的心跳包。 终端和网络侧。 当确定N个移动终端中的任意一个或多个需要传输数据(非心跳包)时,随行的Wi-Fi设备唤醒Wi-Fi模块,分别与其中一个或多个建立Wi-Fi连接。 更多的移动终端来传输数据。 [0180] 如果N个移动终端中的M个移动终端(M大于等于1且小于N)的Wi-Fi模块进入休眠状态,则伴随的Wi-Fi设备单独建立蓝牙连接(即M个蓝牙连接) 发送给M个移动终端,并通过M个蓝牙连接分别传输各个移动终端与网络侧交换的心跳包。 需要说明的是,随附的Wi-Fi设备仍然使用Wi-Fi连接来传输其他(N-M)个移动终端与网络侧之间交换的数据包。 [0181] 本场景的其他内容请参见场景一的描述及前述相关内容。 细节不在此描述。 [0182] 场景三:移动终端(如手机、平板电脑、智能音箱)通过其他移动终端(如手机、平板电脑、智能音箱)提供的热点接入网络 扬声器)。 开启两个移动终端的蓝牙功能,并且两个移动终端之间已经建立了蓝牙连接。 [0183] 该场景的详细介绍请参考其他场景中相关内容的描述。 [0184]本申请实施例还提供了一种芯片系统。 如图6所示,该芯片系统包括至少一个处理器 1101 和至少一个接口电路 1102 . 处理器 1101 和接口电路 1102 可以通过一条线相互连接。 比如接口电路 1102 可以被配置为从另一个设备(例如,移动终端的存储器)接收信号 100 )。 再比如接口电路 1102 可以配置为将信号发送到另一个设备(例如,处理器 1101 )。 比如接口电路 1102 可以读取存储在内存中的指令,并将指令发送到处理器 1101 . 当处理器执行指令时 1101 ,移动终端可以执行移动终端执行的步骤 100 (例如,移动电话)在前述实施例中。 当然,芯片系统还可以包括其他分立器件。 本申请实施例对此不作具体限定。 [0185] 本申请实施例还提供了一种装置。 该装置包括在移动终端或电子设备中,具有实现上述实施例中任一方法的移动终端或电子设备的行为的功能。 该功能可以通过硬件来实现,也可以通过硬件执行相应的软件来实现。 硬件或软件包括与上述功能对应的至少一个模块或单元,例如检测模块或单元,或者确定模块或单元。 [0186] 本申请实施例还提供了一种计算机可读存储介质,包括计算机指令。 当计算机指令在移动终端或电子设备上运行时,移动终端或电子设备执行上述实施例中的任一方法。 [0187] 本申请实施例还提供了一种计算机程序产品。 当计算机程序产品在计算机上运行时,计算机执行上述实施例中的任何方法。 [0188] 可以理解,为了实现上述功能,终端包括相应的硬件结构和/或软件模块,用于执行各个功能。 本领域普通技术人员应该容易意识到,结合本说明书中所公开的实施例中描述的示例的单元和算法步骤,本申请实施例可以通过硬件或者硬件与计算机的结合来实现。 软件。 功能是由硬件执行还是由计算机软件驱动的硬件取决于具体的应用和技术方案的设计约束。 本领域技术人员可以针对每个特定的应用使用不同的方法来实现所描述的功能,但不应认为其实现超出了本发明实施例的范围。 [0189] 在本申请实施例中,可以基于上述方法示例对终端等进行功能模块划分。 例如,可以根据对应的功能划分得到每个功能模块,或者可以将两个或多个功能集成到一个处理模块中。 集成模块可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。 需要说明的是,在本发明实施例中,模块划分只是一个例子,只是逻辑上的功能划分。 在实际实现中,还可以采用另一种划分方式。 [0190]上述实施方式的描述使本领域技术人员可以清楚地了解到,为了描述的方便和简洁,以对上述功能模块的划分为例进行说明。 在实际应用中,上述功能可以根据需要分配到不同的模块中实现。 换言之,将装置的内部结构划分为不同的功能模块来实现上述全部或部分功能。 上述系统、装置和单元的详细工作过程参见上述方法实施例中的对应过程,在此不再赘述。 [0191] 本申请实施例中的功能单元可以集成在一个处理单元中,也可以每个单元在物理上单独存在,或者两个或多个单元集成在一个单元中。 集成单元可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。 [0192] 当集成单元以软件功能单元的形式实现并作为独立产品销售或使用时,集成单元可以存储在计算机可读存储介质中。 基于这样的理解,本申请实施例的技术方案本质上,或者对现有技术有贡献的部分,或者全部或者部分技术方案,可以以软件产品的形式来实现。 计算机软件产品存储在存储介质中,包括若干指令,用于指示计算机设备(可以是个人计算机、服务器或网络设备)执行实施例中描述的方法的全部或部分步骤 这个应用程序的。 上述存储介质包括:闪存、移动硬盘、只读存储器、随机存取存储器、磁盘、光盘等任何可以存储程序代码的介质。 [0193] 以上所述仅为本申请的具体实施方式,并非用于限定本申请的保护范围。 在本申请所公开的技术范围内的任何变更或替换,均应包含在本申请的保护范围之内。 因此,本申请的保护范围应以权利要求的保护范围为准。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN113133095A(String), CN113133095B(String), EP3923617A1(String), EP3923617A4(String), JP2023510259A(String), US20220353819A1(String), WO2021143314A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.370 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN113133095A(String), CN113133095B(String), EP3923617A1(String), EP3923617A4(String), JP2023510259A(String), US20220353819A1(String), WO2021143314A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN113133095A(String), CN113133095B(String), EP3923617A1(String), EP3923617A4(String), JP2023510259A(String), US20220353819A1(String), WO2021143314A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270804(Integer), CN113133095A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.442 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270804(Integer), CN113133095B(String), 1047234(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.476 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.477 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.477 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270804(Integer), EP3923617A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270804(Integer), EP3923617A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270804(Integer), JP2023510259A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270804(Integer), US20220353819A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 270804(Integer), WO2021143314A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN113133095B(String), CN113133095B(String), 1661443200(Integer), 270804(Integer), 185088(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185945(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185945(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185945(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185945(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:55.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.043 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.043 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 实质审查(String), 1(Integer), 185945(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10419919B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.594 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.594 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 移动终端的网络注册方法、存储介质及移动终端(String), US10419919B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端和存储介质。 移动终端的网络注册方法实现如下。 元素T i 响应于确定在移动终端注册第一网络时发生预定异常事件而读取时间数组中的。 i为1至N之间的正整数,N为正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时,得到第一计时时间。 判断第一次计数时间是否达到T i . 如果第一个计数时间达到T,则获得第一个身份 i . 第一标识为第一网络注册时注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/072025(String), 1497283200(Integer), US10419919B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185946(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\37a56adbee144e5ebc899381ca493dca.png(String), 185946(Integer), 37a56adbee144e5ebc899381ca493dca.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 移动终端的网络注册方法、存储介质及移动终端(String), US10419919B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端和存储介质。 移动终端的网络注册方法实现如下。 元素T i 响应于确定在移动终端注册第一网络时发生预定异常事件而读取时间数组中的。 i为1至N之间的正整数,N为正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时,得到第一计时时间。 判断第一次计数时间是否达到T i . 如果第一个计数时间达到T,则获得第一个身份 i . 第一标识为第一网络注册时注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/072025(String), 1497283200(Integer), US10419919B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), \20230420\37a56adbee144e5ebc899381ca493dca.png(String), 20(Integer), 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 1. A network registration method of a mobile terminal, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity.(String), 1.根据权利要求9所述的移动终端,其中处理器还被配置为:当第一次计时时间未达到T时,继续控制移动终端注册第二网络i.12.根据权利要求9所述的移动终端,其中预定异常事件包括跟踪区域更新(TAU)被拒绝。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 2. The method according to claim 1, wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity.(String), 13.根据权利要求9所述的移动终端,其中处理器还被配置为:获取TAU被拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 3. The method according to claim 2, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 14.根据权利要求9所述的移动终端,其中处理器还被配置为:设置元素T的值i根据用户命令在时间数组中。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 4. The method according to claim 2, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 15.一种非暂时性计算机可读存储介质,有其中存储有当移动终端的处理器执行时使移动终端执行网络注册方法的指令,包括:读取时间数组{T1,T2,...,Ti,Ti+1,...,Tn}响应于确定移动终端注册第一网络时发生预定异常事件,其中i介于1和N之间,N为正整数;禁止移动终端注册第一网络,控制移动终端注册第二网络;启动定时器进行计时,得到第一计时时间;判断第一次计时时间是否达到Ti;在第一计数时间达到Ti时获取第一标识,其中,第一标识为移动终端在注册第一网络时注册的小区的相邻小区的跟踪区标识;和控制移动终端根据第一标识重新注册第一网络。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 5. The method according to claim 1, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 16.根据权利要求15所述的非暂时性计算机可读存储介质,其中在根据第一标识控制移动终端重新注册第一网络之后,该方法还包括:判断移动终端重新注册第一网络时是否发生预定异常事件;当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间;判断第二次计时是否达到Ti+1;第二次计时时间达到T时获得第二身份i+1,其中,第二标识为移动终端在重新注册第一网络时注册的小区的相邻小区的跟踪区标识;和控制移动终端根据第二标识重新注册第一网络。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 6. The method according to claim 1, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 17.根据权利要求15所述的非暂时性计算机可读存储介质,其中在判断第一次计数时间是否达到T后i,该方法还包括:当第一次计时时间未达到T时,继续控制移动终端注册第二网络i.18.根据权利要求15所述的非暂时性计算机可读存储介质,其中预定异常事件包括跟踪区域更新(TAU)被拒绝。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 7. The method according to claim 1, further comprising:obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 19.根据权利要求15所述的非暂时性计算机可读存储介质,还包括:获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 8. The method according to claim 1, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 20.根据权利要求15所述的非暂时性计算机可读存储介质,还包括:设置元素T的值i根据用户命令在时间数组中。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 9. A mobile terminal, comprising:a housing;a processor;a memory; anda circuit board and a power supply circuit,wherein, the circuit board is disposed inside a space enclosed by the housing; the processor and the memory are disposed on the circuit board; the power supply circuit is configured to supply power for respective circuits or components of the mobile terminal; the memory is configured to store executable program codes; and the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform:reading an element Ti, in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 10. The mobile terminal according to claim 9, wherein the processor is further configured to:determine whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, control the mobile terminal to re-register the second network, and reset the timer for timing again to obtain a second counted time;determine whether the second counted time reaches Ti+1;obtain a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when re-registering the first network; andcontrol the mobile terminal to re-register the first network according to the second identity.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 11. The mobile terminal according to claim 9, wherein the processor is further configured to:continue to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 12. The mobile terminal according to claim 9, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 13. The mobile terminal according to claim 9, wherein the processor is further configured to:obtain information about TAU being rejected, and send the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 14. The mobile terminal according to claim 9, wherein the processor is further configured to:set a value of the element Ti in the time array according to a user command.(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 15. A non-transitory computer-readable storage medium, having stored therein instructions that, when executed by a processor of a mobile terminal, cause the mobile terminal to execute a network registration method, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is between 1 and N, and N is a positive integer;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity.(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 16. The non-transitory computer-readable storage medium according to claim 15, wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity.(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 17. The non-transitory computer-readable storage medium according to claim 15, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 18. The non-transitory computer-readable storage medium according to claim 15, wherein the predetermined abnormal event comprises tracking area update (TAU) being rejected.(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 19. The non-transitory computer-readable storage medium according to claim 15, further comprising:obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 1(Integer), 18(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:56.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185946(Integer), 20. The non-transitory computer-readable storage medium according to claim 15, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 19(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185946(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a National phase application of International Application No. PCT/CN2017/088117 filed on Jun. 13, 2017, which claims priority to Chinese Patent Application No. 201610460475.8 filed on Jun. 21, 2016 and titled with “NETWORK REGISTRATION METHOD AND APPARATUS FOR MOBILE TERMINAL, AND MOBILE TERMINAL”, the entire contents of which are incorporated herein by reference. FIELD [0002]The present disclosure relates to the communication technology field, and more particularly, to a network registration method of a mobile terminal, a storage medium and a mobile terminal. BACKGROUND [0003]With continuous development of communication technologies, most areas of the country have been covered by 4G network, and users can quickly access to Internet by connecting the mobile terminals to the 4G network. In the related art, when the mobile terminal receives a response indicating that TAU (Tracking Area Update) is rejected, the mobile terminal stops registering the 4G network and does not search for networks of cells with different TAI (Tracking Area Identity). [0004]In this way, when the current TAU is rejected by the network, a success rate of registering the network by the mobile terminal is low. SUMMARY [0005]The present disclosure aims to solve at least one of the problems existing in the related art to some extent at least. [0006]Embodiments of the present disclosure provide a network registration method of a mobile terminal. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. [0007]Embodiments of the present disclosure provide a mobile terminal. The mobile terminal includes a housing, a processor, a memory, a circuit board and a power supply circuit. The circuit board is disposed inside a space enclosed by the housing. The processor and the memory are disposed on the circuit board. The power supply circuit is configured to supply power for respective circuits or components of the mobile terminal. The memory is configured to store executable program codes. The processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform: reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. [0008]Embodiments of the present disclosure provide a non-transitory storage medium. When instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform a network registration method. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. [0009]It is to be understood that, both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to explain technical solutions of the present disclosure more clearly, drawings required to be used in the description of embodiments will now be illustrated briefly. Obviously, drawings in the following description are some embodiments of the present disclosure, and further drawings can be obtained by those skilled in the art based on these drawings, without creative labor. [0011]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0013]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0014]FIG. 4 is a block diagram of a network registration apparatus of a mobile terminal according to an embodiment of the present disclosure. [0015]FIG. 5 is a block diagram of a network registration apparatus of a mobile terminal according to another embodiment of the present disclosure. DETAILED DESCRIPTION [0016]Technical solutions in embodiments of the present disclosure will be described clearly and completely in the following with reference to drawings in embodiments of the present disclosure. Obviously, the embodiments described are merely illustrative, and are not exhaustive. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without creative labor belong to the protection scope of the present disclosure. [0017]Terms such as “first”, “second”, “third” and “four” in the description, claims and drawings of the present disclosure are used to distinguish different objects, and are not used to describe specific order. In addition, terms such as “including” and “having” and their variants intend to cover non-exclusive inclusion. For example, procedures, methods, systems, products or apparatus including a series of steps or units are not limited to listed steps or units, but alternatively further include steps or units which are not listed, or alternatively further include other steps or units inherent to these procedures, methods, products and apparatus. [0018]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in a network registration apparatus of a mobile terminal for illustration. Embodiments of the present disclosure may be applied in a procedure when the user uses the mobile terminal to register 4G network, or may be applied in a procedure of registering 3G network or 2G network, which are not limited. The mobile terminal may be hardware devices with various operating systems, such as a smart phone, a tablet PC, a PDA, and an E-book. [0019]The network registration method of the mobile terminal can include following actions in blocks illustrated in FIG. 1. The method can begin at block S11. [0020]At block S11, an element Ti in a time array is read in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, in which the time array is {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, i is a positive integer between 1 and N, and N is a positive integer. [0021]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0022]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0023]Alternatively, the predetermined abnormal event includes TAU being rejected. [0024]The first network is 4G network. [0025]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0026]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the network with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0027]A value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0028]At S12, the mobile terminal is prohibited from registering the first network, and is controlled to register a second network. [0029]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0030]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti, thus effectively ensuring that the mobile terminal can normally access to Internet. [0031]At S13, the timer is started to time, to obtain a first counted time. [0032]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0033]At S14, it is determined whether the first counted time reaches Ti. [0034]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0035]In some embodiments, as illustrated in FIG. 2, following action may be performed after S14. [0036]At S21, when the first counted time does not reach T1, the mobile terminal is continuously controlled to register the second network. [0037]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0038]At S15, when the first counted time reaches Ti, a first identity is obtained, in which the first identity is the TAI of an adjacent cell of a cell where the mobile terminal is when registering the first network. [0039]In embodiments of the present disclosure, when the first counted time reached Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0040]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0041]At S16, the mobile terminal is controlled to re-register the first network according to the first identity. [0042]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the times reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0043]In this embodiment, by controlling the mobile terminal to register the second network when the predetermined abnormal event occurs during the mobile terminal registers the first network, it can ensure that the user registers the network successfully, and by obtaining the first identity (the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network) when the first counted time reaches Ti, and controlling the mobile terminal to re-register the first network according to the first identity, the mobile terminal can register the network of the cell with different TAI when the current TAU is rejected by the network, thus effectively enhancing the success rate of registering the network. [0044]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in the network registration apparatus of the mobile terminal for illustration. [0045]The network registration method of the mobile terminal includes following actions in blocks illustrated in FIG. 3. The method can begin at block S301. [0046]At S301, the value of the element Ti in the time array is set according to a user command. [0047]In this embodiment, the value of the element Ti in the time array may be preset by the user based on this own demand. [0048]For example, the mobile terminal may receive the command input by the user on the screen, and sets the value of the element Ti in the time array according to the user command. The values of the elements Ti in the time array may be sequentially input by the user on the screen, or may be selectively input by the user, which is not limited. [0049]In this action, the time Ti of the time array is set by the user, and thus personalized setting of the time array may be realized, the generality of the network registration method of the mobile terminal may be improved, and the success rate of the network registration of the mobile terminal may be enhanced. [0050]At S302, it is determined whether the predetermined abnormal event occurs when the mobile terminal registers the first network, and if yes, S303 is executed, and if no, S315 is executed. [0051]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0052]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0053]Alternatively, the predetermined abnormal event includes TAU being rejected. [0054]The first network is 4G network. [0055]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. This embodiment is applied in the procedure in which the mobile terminal registers the network, and is applied after the TAU is rejected. [0056]Alternatively, it is possible to determine whether the event of the TAU being rejected by the network occurs during the mobile terminal registers the 4G network, to trigger subsequent actions. [0057]At S303, the element Ti in the time array is read, in which the time array is {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, i is a positive integer between 1 and N, and N is a positive integer. [0058]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the networks with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0059]The value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0060]At S304, the mobile terminal is prohibited from registering the first network, and is controlled to register the second network. [0061]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0062]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti, thus effectively ensuring that the mobile terminal can normally access to Internet. [0063]At S305, the timer is started to time, to obtain the first counted time. [0064]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0065]At S306, it is determined whether the first counted time reaches Ti, and if yes, S308 is executed, and if no, S307 is executed. [0066]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0067]At S307, the mobile terminal is continuously controlled to register the second network. [0068]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0069]At S308, the first identity is obtained, in which the first identity is the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network. [0070]In embodiments of the present disclosure, when the first counted time reaches Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0071]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0072]At S309, the mobile terminal is controlled to re-register the first network according to the first identity. [0073]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the timer reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0074]At S310, it is determined whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network, and if yes, S311 is executed, and if no, S315 is executed. [0075]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0076]Alternatively, it is determined whether the TAU is rejected by the network when the mobile terminal re-registers the first network, to trigger subsequent actions. [0077]At S311, the mobile terminal is controlled to re-register the second network, and the timer is reset to time again to obtain the second counted time. [0078]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T2. Alternatively, when the mobile terminal alternately reads the element Ti+1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti+1, thus effectively ensuring that the mobile terminal can normally access to Internet. [0079]While the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the second counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti+1 according to the second counted time, which is not limited. [0080]At S312, it is determined whether the second counted time reaches Ti+1. [0081]In embodiments of the present disclosure, it is possible to determine whether the second counted time reaches Ti+1, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0082]At S313, when the second counted time reaches Ti+1, the second identity is obtained, in which the second identity is the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network. [0083]In embodiments of the present disclosure, when the second counted time reaches Ti+1, the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0084]The TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0085]At S314, the mobile terminal is controlled to re-register the first network according to the second identity. [0086]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network due to the TAU being rejected, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T2, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T2. Then, when the counted time of the timer reaches T2, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T3 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T3. When the re-counted time reaches T3, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0087]At S315, information about the TAU being rejected is obtained and sent to the server, such that the server backs up the predetermined abnormal event according to the information. [0088]Alternatively, the mobile terminal obtains the information about the TAU being rejected by the network, and sends the information to the server, such that the server backs up the predetermined abnormal event according to the information. [0089]In this embodiment, the time Ti of the time array is set by the user, and thus personalized setting of the time array can be realized, and generality of the network registration method of the mobile terminal can be improved. By controlling the mobile terminal to register the second network when the predetermined abnormal event occurs during the mobile terminal registers the first network, it can ensure that the user registers the network successfully, and by obtaining the first identity (the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network) when the first counted time reaches Ti, obtaining the second identity (the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network) when the second counted time reaches Ti+1, and controlling the mobile terminal to re-register the first network according to the first identity or the second identity, the mobile terminal can register the network of the cell with different TAI when the current TAU is rejected by the network, thus effectively enhancing the success rate of registering the network. [0090]In order to illustrate the actions of the above embodiments more clearly, an example is given as follows. [0091]As an example, when the time array is {1 min, 6 min, 12 min}, it indicates that the mobile terminal reads the element 1 min in the time array {1 min, 6 min, 12 min} when the mobile terminal fails to register the 4G network the first time due to the TAU being rejected. In the time interval of 1 min, the mobile terminal is prohibited from registering the first network, and switches to register the 2G or 3G network. The mobile terminal accesses to the 2G or 3G network in the time interval of 1 min. then, when the counted time of the timer reaches 1 min, the mobile terminal is controlled to re-register the 4G network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the 4G network. If the registration fails, the mobile terminal reads the element 6 min in the time array {1 min, 6 min, 12 min}, and re-starts the timer for timing. In the time interval of 6 min, the mobile terminal switches to register the 2G or 3G network again. When the re-counted time reaches 6 min, the mobile terminal is controlled to register the 4G network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the 4G network the second time. If the registration successes, the mobile terminal accesses to the 4G network. If the registration fails, the mobile terminal reads the last element 12 min in the time array {1 min, 6 min, 12 min} and re-starts the timer for timing. In the time interval of 12 min, the mobile terminal switches to register the 2G or 3G network again. When the re-counted time reaches 12 min, the mobile terminal is controlled to register the 4G network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the 4G network the third time. By that analogy, the mobile terminal then re-searches for the 4G network every 12 min. In this way, it can ensure that the user can register the network with other rate when the TAU is rejected by the network, avoiding the connectionless network service state. [0092]FIG. 4 is a block diagram of a network registration apparatus of a mobile terminal according to an embodiment of the present disclosure. The network registration apparatus 40 of the mobile terminal may be (String), 相关申请的交叉引用 [0001] 本申请为于2017年6月13日提交的国际申请号PCT/CN2017/088117的国家阶段申请,要求于2016年6月21日提交的申请号为201610460475.8的“网络注册方法及方法”的中国专利申请的优先权。 APPARATUS FOR MOBILE TERMINAL, AND MOBILE TERMINAL”,其全部内容通过引用并入本文。 场地 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端的网络注册方法、存储介质和移动终端。 背景 [0003] 随着通信技术的不断发展,全国大部分地区已被4G网络覆盖,用户可以通过移动终端接入4G网络快速上网。 相关技术中,当移动终端接收到拒绝TAU(Tracking Area Update)响应时,移动终端停止注册4G网络,不再搜索不同TAI(Tracking Area Identity)小区的网络。 [0004] 这样,当当前TAU被网络拒绝时,移动终端注册网络的成功率较低。 概括 [0005] 本发明旨在至少在一定程度上解决相关技术中存在的问题中的至少一个。 [0006] 本发明实施例提供了一种移动终端的网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中,i为1至N之间的正整数,N为正整数; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 [0007] 本发明实施例提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器,用于通过读取内存中存储的可执行程序代码,运行与可执行程序代码对应的程序,以执行:读取元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中,i为1至N之间的正整数,N为正整数; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 [0008]本公开的实施例提供了一种非暂时性存储介质。 当移动终端的处理器执行存储在存储介质中的指令时,使移动终端执行网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中,i为1至N之间的正整数,N为正整数; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 [0009] 应当理解,前述的一般描述和以下的详细描述都只是示例性和解释性的,而不是对本公开的限制。 附图的简要说明 [0010] 为了更加清楚地说明本发明的技术方案,现对实施例描述中需要用到的附图进行简要说明。 显然,以下描述中的附图仅为本发明的一些实施例,本领域技术人员基于这些附图在没有做出创造性劳动的情况下所获得的进一步的附图。 [0011] 图1是根据本发明实施例的移动终端的网络注册方法的流程图。 [0012] 图2是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0013] 图3是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0014] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 [0015] 图5是根据本发明另一实施例的移动终端的网络注册装置的框图。 详细说明 [0016] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 显然,所描述的实施例仅仅是示例性的,而不是穷举性的。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0017] 本发明的说明书、权利要求书和附图中的“第一”、“第二”、“第三”、“四”等术语用于区分不同的对象,不用于描述具体顺序。 此外,诸如“包括”和“具有”及其变体等术语旨在涵盖非排他性包含。 例如,包括一系列步骤或单元的程序、方法、系统、产品或装置不限于列出的步骤或单元,而是还包括未列出的步骤或单元,或者还包括其他固有的步骤或单元 这些程序、方法、产品和设备。 [0018]图1是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 本发明实施例可以应用在用户使用移动终端注册4G网络的过程中,也可以应用在注册3G网络或2G网络的过程中,不做限定。 移动终端可以是智能手机、平板电脑、PDA、电子书等各种操作系统的硬件设备。 [0019] 移动终端的网络注册方法可以包括图1所示的块中的以下动作。该方法可以从块S开始 11 . [0020] 在S座 11 , 元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0021] 本发明实施例以移动终端注册4G网络为例进行说明。 [0022] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0023] 或者,预定异常事件包括TAU被拒绝。 [0024] 第一个网络是4G网络。 [0025] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0026] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0027] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0028] 在小号 12 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0029] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0030] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0031] 在小号 13 ,定时器开始计时,得到第一个计时时间。 [0032] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0033] 在小号 14 , 判断第一个计数时间是否达到T i . [0034] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0035] 在一些实施例中,如图2所示,可以在S之后执行以下动作 14 . [0036] 在小号 21 , 当第一次计数时间没有达到 T 1 ,继续控制移动终端注册第二网络。 [0037] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0038] 在小号 15 , 当第一个计数时间到达 T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0039] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0040] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0041] 在小号 16 ,控制移动终端根据第一标识重新注册第一网络。 [0042] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0043]本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0044] 图3是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 [0045] 移动终端的网络注册方法包括图3所示方框内的以下动作。该方法可以从方框S开始 301 . [0046] 在小号 301 , 元素 T 的值 i 根据用户命令设置时间数组中的。 [0047] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0048] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0049] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0050] 在小号 302 , 判断移动终端注册第一网络时是否发生预定异常事件, 如果是, S 303 被执行,如果没有,S 315 被执行。 [0051] 本发明实施例以移动终端注册4G网络为例进行说明。 [0052] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0053] 或者,预定异常事件包括TAU被拒绝。 [0054] 第一个网络是4G网络。 [0055] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0056] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0057] 在小号 303 , 元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0058] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0059] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0060] 在小号 304 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0061] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0062] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0063] 在小号 305 ,定时器开始计时,得到第一个计时的时间。 [0064] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0065] 在小号 306 , 判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0066] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0067] 在小号 307 ,继续控制移动终端注册第二网络。 [0068] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0069] 在小号 308 ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的邻区TAI。 [0070] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0071] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0072] 在小号 309,控制移动终端根据第一标识重新注册第一网络。 [0073] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0074] 在小号 310 ,判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0075] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0076] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0077] 在小号 311 ,控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0078] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0079] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0080] 在小号 312 ,判断第二次计数时间是否达到T i+1 . [0081] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0082] 在小号 313 , 当第二次计数时间到达 T i+1,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0083] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0084] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0085] 在小号 314 ,控制移动终端根据第二标识重新注册第一网络。 [0086] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0087] 在小号 315 ,获取TAU被拒绝的信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0088] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0089] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 网络注册成功率。 [0090] 为了更清楚地说明上述实施例的作用,举例如下。 [0091]例如,当时间数组为{1分钟,6分钟,12分钟}时,表示移动终端在发生故障时读取时间数组{1分钟,6分钟,12分钟}中的元素1分钟 由于TAU被拒绝,第一次注册4G网络。 在1分钟的时间间隔内,禁止移动终端注册第一网络,切换注册2G或3G网络。 移动终端以1分钟的时间间隔接入2G或3G网络。 然后,当定时器计时到1分钟时,根据邻区TAI控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}中的元素6分钟,重新启动定时器进行计时。 在6分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到6分钟时,根据移动终端第二次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}的最后一个元素12分钟,重新启动定时器进行计时。 在12分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到12分钟时,根据移动终端第三次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 以此类推,移动终端每12分钟重新搜索一次4G网络。 这样可以保证用户在TAU被网络拒绝的情况下可以注册到其他速率的网络,避免无连接的网络服务状态。 [0092] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 网络注册设备 40 移动终端的功能可以通过软件、硬件或其组合来实现。 网络注册设备 40 移动终端的可以包括阅读模块 401 , 第一控制模块 402 , 一个起始模块 403 , 第一判断模块 404 , 处理模块 405 和第二个控制模块 406 . [0093] 阅读模块 401 被配置为读取元素 T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1至N之间的正整数,N为正整数。 [0094] 或者,预定异常事件包括TAU被拒绝。 [0095] 第一控制模块 402 用于禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0096] 启动模块 403 用于启动定时器进行计时,得到第一计时时间。 [0097] 第一判断模块 404 配置为判断第一个计数时间是否达到T i . [0098] 处理模块 405 被配置为当第一次计数时间达到T时获得第一身份 i 其中,第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识。 [0099] 第二控制模块 406 用于控制移动终端根据第一标识重新注册第一网络。 [0100] 或者,在一些实施例中,如图5所示,网络注册装置 40 移动终端还可以包括第二判断模块 407 , 第三个控制模块 408 , 第三判断模块 409 , 第一获取模块410 , 第四控制模块 411 , 第二个获取模块 412 , 和一个设置模块 413 . [0101] 第二判断模块 407 用于判断移动终端重新注册第一网络时是否发生预定异常事件。 [0102] 第三控制模块 408 用于当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间。 [0103] 第三判断模块 409 用于判断第二次计数时间是否达到T i+1 . [0104] 第一个获取模块 410 用于在秒计数时间达到T时获取第二身份 i+1 其中,第二标识为移动终端在重新注册第一网络时所在小区的相邻小区的跟踪区标识。 [0105] 第四个控制模块 411 用于控制移动终端根据第二标识重新注册第一网络。 [0106] 或者,处理模块 405 还用于当第一计时时间未达到T时,继续控制移动终端注册第二网络 i . [0107] 第二个获取模块 412 用于获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0108] 设置模块 413 被配置为设置元素T的值 i 根据用户命令在时间数组中。 [0109] 需要说明的是,结合图1-图3对移动终端的网络注册方法实施例的说明同样适用于移动终端的网络注册装置,其原理类似,在此不再赘述。 [0110] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i 以及根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率。 网络。 [0111] 本发明实施例还提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器用于通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0112] 在小号 11 ′, 一个元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0113] 本发明实施例以移动终端注册4G网络为例进行说明。 [0114] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0115] 或者,预定异常事件包括TAU被拒绝。 [0116]第一个网络是4G网络。 [0117] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0118] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0119] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0120] 在小号 12 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0121] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0122] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0123] 在小号 13 ',启动定时器计时,得到第一计时时间。 [0124] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0125] 在小号 14 ′,判断第一个计数时间是否达到T i . [0126] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0127] 在另一实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0128] 在小号 21 ′,当第一次计数时间未达到 T 1 ,继续控制移动终端注册第二网络。 [0129]本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0130] 在小号 15 ′,当第一个计数时间到达T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0131] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0132] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0133] 在小号 16 ',控制移动终端根据第一标识重新注册第一网络。 [0134] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0135] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0136] 在另一个实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0137] 在小号 301 ′,元素T的值 i 根据用户命令设置时间数组中的。 [0138] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0139] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0140] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0141] 在小号 302 ',判断移动终端注册第一网络时是否发生预定异常事件,如果是,S 303 被执行,如果没有,S 315 被执行。 [0142] 本发明实施例以移动终端注册4G网络为例进行说明。 [0143] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0144] 或者,预定异常事件包括TAU被拒绝。 [0145] 第一个网络是4G网络。 [0146] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0147] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0148] 在小号 303 ′,元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} i是1到N之间的正整数,N是正整数。 [0149] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0150] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0151] 在小号 304 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0152] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0153] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1. 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0154] 在小号 305 ',启动定时器计时,得到第一个计时时间。 [0155] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0156] 在小号 306 ′,判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0157] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0158] 在小号 307 ',继续控制移动终端注册第二网络。 [0159] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0160] 在小号 308 ',获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0161] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0162] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0163] 在小号 309 ',控制移动终端根据第一标识重新注册第一网络。 [0164] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 z ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0165] 在小号 310 ',判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0166] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0167] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0168] 在小号 311 ',控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0169] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0170] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0171] 在小号 312 ′,判断第二次计时是否达到T i+1 . [0172] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0173] 在小号 313 ′,当第二次计数时间到达T i+1 ,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0174] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0175] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0176] 在小号 314 ',控制移动终端根据第二标识重新注册第一网络。 [0177] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,在第二次注册第一网络时,根据移动终端注册所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0178] 在小号 315 ',获取TAU被拒绝的信息并发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0179] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0180] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 网络注册成功率。 [0181] 上述装置实施例仅仅是示例性的,其中作为单独的部件示出的单元在物理上可以是分离的,也可以不是物理分离的,作为单元示出的部件可以是物理单元也可以不是物理单元,即可以位于一个空间内,或者可以是物理单元。 分布到多个网络单元。 可以根据实际需要选择其中的部分或全部模块来实现本发明的目的。 本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0182] 本发明方法实施例中的动作可以根据实际需要进行调整、合并或者删除。 [0183] 本发明装置实施例中的模块或单元可以根据实际需要进行合并、划分和删除。 [0184] 本发明实施例中的模块或单元可以采用通用集成电路(如CPU)实现,也可以采用专用集成电路(ASIC)实现。 [0185]通过以上对实施例的描述,本领域的技术人员可以清楚地了解到,各个实施例可以通过软件结合必要的通用硬件平台来实现,也可以通过硬件来实现。 基于这种理解,上述技术方案的本质或者对相关技术有贡献的部分可以以软件产品的形式体现。 计算机软件产品可以存储在计算机可读存储介质中,例如ROM/RAM、磁盘、CD等,可以包括若干指令,用于使计算机设备(可以是个人计算机、服务器或 网络设备)执行各个实施例或实施例的部分描述的方法。 [0186] 上述实施方式并不构成对本发明保护范围的限制。 凡在本发明的精神和范围内所作的任何修改、等同或者改进,均包含在本技术方案的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271206(Integer), CN105933884A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), CN105933884B(String), 1048249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271206(Integer), US10419919B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271206(Integer), US10419920B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271206(Integer), US20190045350A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271206(Integer), US20190141514A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271206(Integer), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN105933884B(String), CN105933884B(String), 1522339200(Integer), 271206(Integer), 185490(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185946(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 1(Integer), 185946(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:57.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD.(String), OPPO广东移动通信有限公司(String), 0(Integer), 1681976037(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185946(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75833(Integer), 2(Integer), 185946(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75833(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.141 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185946(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10419920B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 一种移动终端的网络注册方法、存储介质和移动终端(String), US10419920B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端及存储介质。 移动终端的网络注册方法实现如下。 一个元素 T i 响应于确定移动终端注册第一网络时发生预定异常事件,读取时间数组中的时间数组。 i是1到N之间的正整数,N是正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时以获得第一计数时间。 判断第一个计数时间是否达到T i . 如果第一个计数时间达到 T,则获取第一个身份 i . 第一标识为注册第一网络时所注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/201705(String), 1543248000(Integer), US10419920B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185947(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\33814fce4d3d463d8eaaee8ebfe889a6.png(String), 185947(Integer), 33814fce4d3d463d8eaaee8ebfe889a6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:58.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network registration method for mobile terminal, storage medium, and mobile terminal(String), 一种移动终端的网络注册方法、存储介质和移动终端(String), US10419920B2(String), Provided are a network registration method for a mobile terminal, a mobile terminal and a storage medium. The network registration method for a mobile terminal is implemented as follows. An element Ti in a time array is read in response of determining that a predetermined abnormal event occurs when a mobile terminal registers a first network. i is a positive integer between 1 and N, and N is a positive integer. The mobile terminal is prohibited from registering the first network. The mobile terminal is controlled to register a second network. A timer is started for timing to obtain a first counted time. It is determined whether the first counted time reaches Ti. A first identity is acquired if the first counted time reaches Ti. The first identifier is a tracking area identity of an adjacent cell of a registered cell when the first network is registered. The mobile terminal is controlled to re-register the first network again according to the first identity.(String), 提供了一种移动终端的网络注册方法、移动终端及存储介质。 移动终端的网络注册方法实现如下。 一个元素 T i 响应于确定移动终端注册第一网络时发生预定异常事件,读取时间数组中的时间数组。 i是1到N之间的正整数,N是正整数。 禁止移动终端注册第一网络。 控制移动终端注册第二网络。 启动定时器进行计时以获得第一计数时间。 判断第一个计数时间是否达到T i . 如果第一个计数时间达到 T,则获取第一个身份 i . 第一标识为注册第一网络时所注册小区的相邻小区的跟踪区域标识。 控制移动终端根据第一标识重新注册第一网络。(String), US16/201705(String), 1543248000(Integer), US10419920B2(String), 1568649600(Integer), 1568649600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 13(Integer), CN102256323A | CN103747469A | CN103906090A | CN104581675A | CN104602292A | CN105472677A | CN105933884A | US10097987B2 | US20110263239A1 | US20120258766A1 | US20150131437A1 | US20150245256A1 | US9071951B2(String), \20230420\33814fce4d3d463d8eaaee8ebfe889a6.png(String), 12(Integer), 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 1. A network registration method of a mobile terminal, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity;wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity;obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 1.根据权利要求10所述的非暂时性计算机可读存储介质,还包括:设置元素T的值i根据用户命令在时间数组中。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 2. The method according to claim 1, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 12.根据权利要求9所述的非暂时性计算机可读存储介质,还包括:设置元素T的值i根据用户命令在时间数组中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 3. The method according to claim 2, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 4. The method according to claim 1, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 5. A mobile terminal, comprising:a housing;a processor;a memory; anda circuit board and a power supply circuit,wherein, the circuit board is disposed inside a space enclosed by the housing; the processor and the memory are disposed on the circuit board; the power supply circuit is configured to supply power for respective circuits or components of the mobile terminal; the memory is configured to store executable program codes; and the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform:reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity;wherein the processor is further configured to:determine whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, control the mobile terminal to re-register the second network, and reset the timer for timing again to obtain a second counted time;alternately read an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determine whether the second counted time reaches Ti+1;obtain a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when re-registering the first network; andcontrol the mobile terminal to re-register the first network according to the second identity;obtain information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 6. The mobile terminal according to claim 5, wherein the processor is further configured to:continue to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 7. The mobile terminal according to claim 6, wherein the processor is further configured to:set a value of the element Ti in the time array according to a user command.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 8. The mobile terminal according to claim 5, wherein the processor is further configured to:set a value of the element Ti in the time array according to a user command.(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 9. A non-transitory computer-readable storage medium, having stored therein instructions that, when executed by a processor of a mobile terminal, cause the mobile terminal to execute a network registration method, comprising:reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user;prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network;starting a timer for timing, to obtain a first counted time;determining whether the first counted time reaches Ti;obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when registering the first network; andcontrolling the mobile terminal to re-register the first network according to the first identity;wherein after controlling the mobile terminal to re-register the first network according to the first identity, the method further comprises:determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network;when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time;alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1;obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; andcontrolling the mobile terminal to re-register the first network according to the second identity;obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 10. The non-transitory computer-readable storage medium according to claim 9, wherein after determining whether the first counted time reaches Ti, the method further comprises:continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 11. The non-transitory computer-readable storage medium according to claim 10, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185947(Integer), 12. The non-transitory computer-readable storage medium according to claim 9, further comprising:setting a value of the element Ti in the time array according to a user command.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185947(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a Continuation Application of U.S. application Ser. No. 16/072,025, filed Jul. 23, 2018, which is a National Stage Entry of International Application No. PCT/CN2017/088117, filed Jun. 13, 2017 which claims priority to Chinese Patent Application No. 201610460475.8 filed by on Jun. 21, 2016 and titled with “NETWORK REGISTRATION METHOD AND APPARATUS FOR MOBILE TERMINAL, AND MOBILE TERMINAL”, the entire contents of which are incorporated herein by reference. FIELD [0002]The present disclosure relates to the communication technology field, and more particularly, to a network registration method of a mobile terminal, a storage medium and a mobile terminal. BACKGROUND [0003]With continuous development of communication technologies, most areas of the country have been covered by 4G network, and users can quickly access to Internet by connecting the mobile terminals to the 4G network. In the related art, when the mobile terminal receives a response indicating that TAU (Tracking Area Update) is rejected, the mobile terminal stops registering the 4G network and does not search for networks of cells with different TAI (Tracking Area Identity). [0004]In this way, when the current TAU is rejected by the network, a success rate of registering the network by the mobile terminal is low. SUMMARY [0005]The present disclosure aims to solve at least one of the problems existing in the related art to some extent at least. [0006]Embodiments of the present disclosure provide a network registration method of a mobile terminal. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. After controlling the mobile terminal to re-register the first network according to the first identity, the method further includes: determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network; when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time; alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1; obtaining a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; and controlling the mobile terminal to re-register the first network according to the second identity; obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information. [0007]Embodiments of the present disclosure provide a mobile terminal. The mobile terminal includes a housing, a processor, a memory, a circuit board and a power supply circuit. The circuit board is disposed inside a space enclosed by the housing. The processor and the memory are disposed on the circuit board. The power supply circuit is configured to supply power for respective circuits or components of the mobile terminal. The memory is configured to store executable program codes. The processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory, so as to perform: reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. The processor is further configured to: determine whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network; when the predetermined abnormal event occurs, control the mobile terminal to re-register the second network, and reset the timer for timing again to obtain a second counted time; alternately read an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determine whether the second counted time reaches Ti+1; obtain a second identity when the second counted time reaches Ti+1, wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when re-registering the first network; and control the mobile terminal to re-register the first network according to the second identity; obtain information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information. [0008]Embodiments of the present disclosure provide a non-transitory storage medium. When instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform a network registration method. The method includes: reading an element Ti in a time array {T1, T2, . . . , Ti, . . . , Tn} in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, wherein i is a positive integer between 1 and N, and N is a positive integer, the predetermined abnormal event comprises tracking area update (TAU) being rejected, values of the elements Ti in the time array are sequentially input by the user on the screen or selectively input by the user; prohibiting the mobile terminal from registering the first network, and controlling the mobile terminal to register a second network; starting a timer for timing, to obtain a first counted time; determining whether the first counted time reaches Ti; obtaining a first identity when the first counted time reaches Ti, wherein the first identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is when registering the first network; and controlling the mobile terminal to re-register the first network according to the first identity. After controlling the mobile terminal to re-register the first network according to the first identity, the method further includes: determining whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network; when the predetermined abnormal event occurs, controlling the mobile terminal to re-register the second network, and resetting the timer for timing again to obtain a second counted time; alternately reading an element Ti+1 in the time array {T1, T2, . . . , Ti, . . . , Tn}, and determining whether the second counted time reaches Ti+1; obtaining a second identity when the second counted time reaches wherein the second identity is a tracking area identity of an adjacent cell of a cell where the mobile terminal is registered when re-registering the first network; and controlling the mobile terminal to re-register the first network according to the second identity; obtaining information about TAU being rejected, and sending the information to a server, such that the server backs up the predetermined abnormal event according to the information. [0009]It is to be understood that, both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to explain technical solutions of the present disclosure more clearly, drawings required to be used in the description of embodiments will now be illustrated briefly. Obviously, drawings in the following description are some embodiments of the present disclosure, and further drawings can be obtained by those skilled in the art based on these drawings, without creative labor. [0011]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0013]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to another embodiment of the present disclosure. [0014]FIG. 4 is a block diagram of a network registration apparatus of a mobile terminal according to an embodiment of the present disclosure. [0015]FIG. 5 is a block diagram of a network registration apparatus of a mobile terminal according to another embodiment of the present disclosure. DETAILED DESCRIPTION [0016]Technical solutions in embodiments of the present disclosure will be described clearly and completely in the following with reference to drawings in embodiments of the present disclosure. Obviously, the embodiments described are merely illustrative, and are not exhaustive. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without creative labor belong to the protection scope of the present disclosure. [0017]Terms such as “first”, “second”, “third” and “four” in the description, claims and drawings of the present disclosure are used to distinguish different objects, and are not used to describe specific order. In addition, terms such as “including” and “having” and their variants intend to cover non-exclusive inclusion. For example, procedures, methods, systems, products or apparatus including a series of steps or units are not limited to listed steps or units, but alternatively further include steps or units which are not listed, or alternatively further include other steps or units inherent to these procedures, methods, products and apparatus. [0018]FIG. 1 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in a network registration apparatus of a mobile terminal for illustration. Embodiments of the present disclosure may be applied in a procedure when the user uses the mobile terminal to register 4G network, or may be applied in a procedure of registering 3G network or 2G network, which are not limited. The mobile terminal may be hardware devices with various operating systems, such as a smart phone, a tablet PC, a PDA, and an E-book. [0019]The network registration method of the mobile terminal can include following actions in blocks illustrated in FIG. 1. The method can begin at block S11. [0020]At block S11, an element Ti in a time array is read in response to determining that a predetermined abnormal event occurs when the mobile terminal registers a first network, in which the time array is {T1, . . . , T2, Ti, Ti+1, . . . , Tn}, is a positive integer between 1 and N, and N is a positive integer. [0021]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0022]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0023]Alternatively, the predetermined abnormal event includes TAU being rejected. [0024]The first network is 4G network. [0025]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0026]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the network with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0027]A value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0028]At S12, the mobile terminal is prohibited from registering the first network, and is controlled to register a second network. [0029]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0030]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of thus effectively ensuring that the mobile terminal can normally access to Internet. [0031]At S13, the timer is started to time, to obtain a first counted time. [0032]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0033]At S14, it is determined whether the first counted time reaches Ti. [0034]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0035]In some embodiments, as illustrated in FIG. 2, following action may be performed after S14. [0036]At S21, when the first counted time does not reach T1, the mobile terminal is continuously controlled to register the second network. [0037]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0038]At S15, when the first counted time reaches Ti, a first identity is obtained, in which the first identity is the TAI of an adjacent cell of a cell where the mobile terminal is when registering the first network. [0039]In embodiments of the present disclosure, when the first counted time reached Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0040]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0041]At S16, the mobile terminal is controlled to re-register the first network according to the first identity. [0042]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the times reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0043]In this embodiment, by controlling the mobile terminal to register the second network when the predetermined abnormal event occurs during the mobile terminal registers the first network, it can ensure that the user registers the network successfully, and by obtaining the first identity (the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network) when the first counted time reaches Ti, and controlling the mobile terminal to re-register the first network according to the first identity, the mobile terminal can register the network of the cell with different TAI when the current TAU is rejected by the network, thus effectively enhancing the success rate of registering the network. [0044]FIG. 3 is a flow chart of a network registration method of a mobile terminal according to an embodiment of the present disclosure. The network registration method is configured in the network registration apparatus of the mobile terminal for illustration. [0045]The network registration method of the mobile terminal includes following actions in blocks illustrated in FIG. 3. The method can begin at block S301. [0046]At S301, the value of the element Ti in the time array is set according to a user command. [0047]In this embodiment, the value of the element Ti in the time array may be preset by the user based on this own demand. [0048]For example, the mobile terminal may receive the command input by the user on the screen, and sets the value of the element Ti in the time array according to the user command. The values of the elements Ti in the time array may be sequentially input by the user on the screen, or may be selectively input by the user, which is not limited. [0049]In this action, the time Ti of the time array is set by the user, and thus personalized setting of the time array may be realized, the generality of the network registration method of the mobile terminal may be improved, and the success rate of the network registration of the mobile terminal may be enhanced. [0050]At S302, it is determined whether the predetermined abnormal event occurs when the mobile terminal registers the first network, and if yes, S303 is executed, and if no, S315 is executed. [0051]Embodiments of the present disclosure are illustrated in a case in which the mobile terminal registers the 4G network. [0052]The execution body of embodiments of the present disclosure may be, for example, a built-in modem of the mobile terminal. [0053]Alternatively, the predetermined abnormal event includes TAU being rejected. [0054]The first network is 4G network. [0055]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. This embodiment is applied in the procedure in which the mobile terminal registers the network, and is applied after the TAU is rejected. [0056]Alternatively, it is possible to determine whether the event of the TAU being rejected by the network occurs during the mobile terminal registers the 4G network, to trigger subsequent actions. [0057]At S303, the element Ti in the time array is read, in which the time array is {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, i is a positive integer between 1 and N, and N is a positive integer. [0058]In embodiments of the present disclosure, when the mobile terminal fails to register the network due to the TAU being rejected, the time array may be started and the element Ti in the time array may be read. For example, when the mobile terminal initially fails to register the first network, the element T1 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and the mobile terminal is controlled to register the networks with different rate, for example, 2G network or 3G network, during the time interval of T1, to ensure that the mobile terminal can normally access to Internet. When the mobile fails to register the first network the second time, the element T2 may be read from the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, and so on. The element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, to enhance the success rate of registering the first network by the mobile terminal, which is not limited. [0059]The value of the element Ti in the time array may be set by the user based on his own demand, or may be preset by the manufacturer of the mobile terminal, which is not limited. [0060]At S304, the mobile terminal is prohibited from registering the first network, and is controlled to register the second network. [0061]In embodiments of the present disclosure, the second network has a transmission rate different from the first network. For example, the second network may be 2G network, or 3G network, which is not limited. [0062]In embodiments of the present disclosure, when the mobile terminal initially fails to register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T1. Alternatively, when the mobile terminal alternately reads the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti, thus effectively ensuring that the mobile terminal can normally access to Internet. [0063]At S305, the timer is started to time, to obtain the first counted time. [0064]In embodiments of the present disclosure, while the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the first counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti according to the first counted time, which is not limited. [0065]At S306, it is determined whether the first counted time reaches Ti, and if yes, S308 is executed, and if no, S307 is executed. [0066]In embodiments of the present disclosure, it is possible to determine whether the first counted time reaches Ti, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0067]At S307, the mobile terminal is continuously controlled to register the second network. [0068]In this action, by continuing to control the mobile terminal to register the second network when the first counted time does not reach Ti, it can ensure that the user can register the network with different rate when the TAU is rejected by the network, avoiding the connectionless network service state, and effectively improving the user experience. [0069]At S308, the first identity is obtained, in which the first identity is the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network. [0070]In embodiments of the present disclosure, when the first counted time reaches Ti, the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0071]The TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0072]At S309, the mobile terminal is controlled to re-register the first network according to the first identity. [0073]In embodiments of the present disclosure, when the mobile terminal fails to register the first network the first time due to the TAU being rejected, the mobile terminal reads the element T1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T1, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T1. Then, when the counted time of the timer reaches T1, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T2. When the re-counted time reaches T2, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0074]At S310, it is determined whether the predetermined abnormal event occurs when the mobile terminal re-registers the first network, and if yes, S311 is executed, and if no, S315 is executed. [0075]It can be understood that, during the procedure in which the user uses the mobile terminal to access the 4G network, a response indicting a failure of registering the network may occur, in which the failure of registering the network may be caused by the TAU being rejected, or may be caused by other reasons. [0076]Alternatively, it is determined whether the TAU is rejected by the network when the mobile terminal re-registers the first network, to trigger subsequent actions. [0077]At S311, the mobile terminal is controlled to re-register the second network, and the timer is reset to time again to obtain the second counted time. [0078]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network and when the mobile terminal fails to register the first network due to the TAU being rejected, it is possible to control the mobile terminal to switch to register the network with different rate, for example, 2G network or 3G network, in the time interval of T2. Alternatively, when the mobile terminal alternately reads the element Ti+1 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}, the mobile terminal may switch to register the network with different rate in the time interval of Ti+1, thus effectively ensuring that the mobile terminal can normally access to Internet. [0079]While the mobile terminal is prohibited from registering the first network and is controlled to register the second network, the timer may be started to time, to obtain the second counted time. The mobile terminal may determine whether the duration of registering the second network reaches Ti+1 according to the second counted time, which is not limited. [0080]At S312, it is determined whether the second counted time reaches Ti+1. [0081]In embodiments of the present disclosure, it is possible to determine whether the second counted time reaches Ti+1, to determine whether to trigger the mobile terminal to re-register the first network, which is not limited. [0082]At S313, when the second counted time reaches Ti+1, the second identity is obtained, in which the second identity is the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network. [0083]In embodiments of the present disclosure, when the second counted time reaches Ti+1, the TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained, to control the mobile terminal to re-register the first network according to the TAI of the adjacent cell. [0084]The TAI of the adjacent cell of the cell where the mobile terminal is when re-registering the first network may be obtained by technologies in the related art, which will not be elaborated here. [0085]At S314, the mobile terminal is controlled to re-register the first network according to the second identity. [0086]In embodiments of the present disclosure, when the mobile terminal fails to re-register the first network due to the TAU being rejected, the mobile terminal reads the element T2 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn}. In the time interval of T2, the mobile terminal is prohibited from registering the first network, but switches to register the second network, and accesses to the second network in the time interval of T2. Then, when the counted time of the timer reaches T2, the mobile terminal is controlled to re-register the first network according to the TAI of the adjacent cell. If the registration successes, the mobile terminal accesses to the first network. If the registration fails, the mobile terminal reads the element T3 in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} and resets the timer for timing again, and switches to register the second network again in the time interval of T3. When the re-counted time reaches T3, the mobile terminal is controlled to register the first network again according to the TAI of the adjacent cell of the cell where the mobile terminal is when registering the first network the second time. By that analogy, the element Ti in the time array {T1, T2, . . . , Ti, Ti+1, . . . , Tn} is read alternately, until the mobile terminal registers the first network successfully, which is not limited. [0087]At S315, information about the TAU being rejected is obtained and se(String), 相关申请的交叉引用 [0001] 该申请是美国申请序列号的延续申请。 2018年7月23日提交的第16/072,025号国际申请进入国家阶段,2017年6月13日提交的PCT/CN2017/088117号要求2017年6月13日提交的中国专利申请201610460475.8的优先权 . 21, 2016,标题为“用于移动终端的网络注册方法和装置,以及移动终端”,其全部内容通过引用并入本文。 场地 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端的网络注册方法、存储介质及移动终端。 背景 [0003] 随着通信技术的不断发展,全国大部分地区已被4G网络覆盖,用户可以通过移动终端接入4G网络快速上网。 相关技术中,当移动终端接收到拒绝TAU(Tracking Area Update)响应时,移动终端停止注册4G网络,不再搜索不同TAI(Tracking Area Identity)小区的网络。 [0004] 这样,当当前TAU被网络拒绝时,移动终端注册网络的成功率较低。 概括 [0005] 本发明旨在至少在一定程度上解决相关技术中存在的问题中的至少一个。 [0006] 本发明实施例提供了一种移动终端的网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1和N之间的正整数,N为正整数,预定异常事件包括跟踪区域更新(TAU)为 拒绝,元素 T 的值 i 时间数组中的是用户在屏幕上依次输入或者是用户选择性输入; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 在根据第一标识控制移动终端重新注册第一网络之后,该方法还包括: 判断移动终端重新注册第一网络时是否发生预定异常事件; 当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间; 交替读取元素 T i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n},判断第二次计时是否达到T i+1 ; 第二次计时时间达到T时获得第二身份 i+1 ,其中,所述第二标识为所述移动终端在重新注册第一网络时注册的小区的相邻小区的跟踪区标识; 控制移动终端根据第二身份重新注册第一网络; 获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0007]本发明实施例提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器,用于通过读取内存中存储的可执行程序代码,运行与可执行程序代码对应的程序,以执行:读取元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1和N之间的正整数,N为正整数,预定异常事件包括跟踪区域更新(TAU)为 拒绝,元素 T 的值 i 时间数组中的是用户在屏幕上依次输入或者是用户选择性输入; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i , 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 处理器还用于判断移动终端重新注册第一网络时是否发生预定异常事件; 当预定异常事件发生时,控制移动终端重新注册第二网络,并重新设置定时器重新计时,得到第二计时时间。 交替读取一个元素 T i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n},判断第二次计数时间是否达到T i+1 ; 当第二次计数时间达到T时获得第二个身份 i+1 ,其中,所述第二标识为所述移动终端在重新注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第二身份重新注册第一网络; 获取TAU被拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0008] 本公开的实施例提供了一种非暂时性存储介质。 当移动终端的处理器执行存储在存储介质中的指令时,使移动终端执行网络注册方法。 该方法包括:读取一个元素T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1和N之间的正整数,N为正整数,预定异常事件包括跟踪区域更新(TAU)为 拒绝,元素 T 的值 i 时间数组中的是用户在屏幕上依次输入或者是用户选择性输入; 禁止移动终端注册第一网络,控制移动终端注册第二网络; 启动定时器进行计时,得到第一计时时间; 判断第一个计数时间是否到达T i ; 当第一个计数时间到达T时获得第一个身份 i, 其中, 第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识; 控制移动终端根据第一标识重新注册第一网络。 在根据第一标识控制移动终端重新注册第一网络之后,该方法还包括: 判断移动终端重新注册第一网络时是否发生预定异常事件; 当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间; 交替读取元素 T i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i ,. . . , 吨 n},判断第二次计时是否达到T i+1 ; 在第二计数时间到达时获取第二标识,其中,第二标识为移动终端在重新注册第一网络时注册的小区的相邻小区的跟踪区标识; 控制移动终端根据第二身份重新注册第一网络; 获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0009] 应当理解,前述的一般描述和以下的详细描述都只是示例性和解释性的,而不是对本公开的限制。 附图的简要说明 [0010] 为了更加清楚地说明本发明的技术方案,现对实施例描述中需要用到的附图进行简要说明。 显然,以下描述中的附图仅为本发明的一些实施例,本领域技术人员基于这些附图在没有做出创造性劳动的情况下所获得的进一步的附图。 [0011] 图1是根据本发明实施例的移动终端的网络注册方法的流程图。 [0012] 图2是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0013] 图3是根据本发明另一实施例的移动终端的网络注册方法的流程图。 [0014] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 [0015] 图5是根据本发明另一实施例的移动终端的网络注册装置的框图。 详细说明 [0016] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 显然,所描述的实施例仅仅是示例性的,而不是穷举性的。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0017] 本发明的说明书、权利要求书和附图中的“第一”、“第二”、“第三”、“四”等术语用于区分不同的对象,不用于描述具体顺序。 此外,诸如“包括”和“具有”及其变体等术语旨在涵盖非排他性包含。 例如,包括一系列步骤或单元的程序、方法、系统、产品或装置不限于列出的步骤或单元,而是还包括未列出的步骤或单元,或者还包括其他固有的步骤或单元 这些程序、方法、产品和设备。 [0018]图1是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 本发明实施例可以应用在用户使用移动终端注册4G网络的过程中,也可以应用在注册3G网络或2G网络的过程中,不做限定。 移动终端可以是智能手机、平板电脑、PDA、电子书等各种操作系统的硬件设备。 [0019] 移动终端的网络注册方法可以包括图1所示的块中的以下动作。该方法可以从块S开始 11 . [0020] 在S座 11 , 元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 ,. . . , 吨 2 , 吨 i , 吨 i+1 ,. . . , 吨 n},是1到N之间的正整数,N是正整数。 [0021] 本发明实施例以移动终端注册4G网络为例进行说明。 [0022] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0023] 或者,预定异常事件包括TAU被拒绝。 [0024] 第一个网络是4G网络。 [0025] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0026] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0027] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0028] 在小号 12 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0029] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0030] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在时间间隔内切换注册不同速率的网络,从而有效保证移动终端可以正常上网。 [0031] 在小号 13 ,定时器开始计时,得到第一个计时时间。 [0032] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0033] 在小号 14 , 判断第一个计数时间是否达到T i . [0034] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0035] 在一些实施例中,如图2所示,可以在S之后执行以下动作 14 . [0036] 在小号 21 , 当第一次计数时间没有达到 T 1 ,继续控制移动终端注册第二网络。 [0037] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0038] 在小号 15 , 当第一个计数时间到达 T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0039] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0040] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0041] 在小号 16 ,控制移动终端根据第一标识重新注册第一网络。 [0042] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0043]本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0044] 图3是根据本发明实施例的移动终端的网络注册方法的流程图。 该网络注册方法配置在移动终端的网络注册装置中进行说明。 [0045] 移动终端的网络注册方法包括图3所示方框内的以下动作。该方法可以从方框S开始 301 . [0046] 在小号 301 , 元素 T 的值 i 根据用户命令设置时间数组中的。 [0047] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0048] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0049] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0050] 在小号 302 , 判断移动终端注册第一网络时是否发生预定异常事件, 如果是, S 303 被执行,如果没有,S 315 被执行。 [0051] 本发明实施例以移动终端注册4G网络为例进行说明。 [0052] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0053] 或者,预定异常事件包括TAU被拒绝。 [0054] 第一个网络是4G网络。 [0055] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0056] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0057] 在小号 303 , 元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0058] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0059] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0060] 在小号 304 ,禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0061] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0062] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0063] 在小号 305 ,定时器开始计时,得到第一个计时的时间。 [0064] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0065] 在小号 306 , 判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0066] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0067] 在小号 307 ,继续控制移动终端注册第二网络。 [0068] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0069] 在小号 308 ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的邻区TAI。 [0070] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0071] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0072] 在小号 309,控制移动终端根据第一标识重新注册第一网络。 [0073] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0074] 在小号 310 ,判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0075] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0076] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0077] 在小号 311 ,控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0078] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0079] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0080] 在小号 312 ,判断第二次计数时间是否达到T i+1 . [0081] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0082] 在小号 313 , 当第二次计数时间到达 T i+1,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0083] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0084] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0085] 在小号 314 ,控制移动终端根据第二标识重新注册第一网络。 [0086] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0087] 在小号 315 ,获取TAU被拒绝的信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0088] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0089] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 注册网络的成功率。 [0090] 为了更清楚地说明上述实施例的作用,举例如下。 [0091]例如,当时间数组为{1分钟,6分钟,12分钟}时,表示移动终端在发生故障时读取时间数组{1分钟,6分钟,12分钟}中的元素1分钟 由于TAU被拒绝,第一次注册4G网络。 在1分钟的时间间隔内,禁止移动终端注册第一网络,切换注册2G或3G网络。 移动终端以1分钟的时间间隔接入2G或3G网络。 然后,当定时器计时到1分钟时,根据邻区TAI控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}中的元素6分钟,重新启动定时器进行计时。 在6分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到6分钟时,根据移动终端第二次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 如果注册成功,则移动终端接入4G网络。 如果注册失败,则移动端读取时间数组{1分钟,6分钟,12分钟}的最后一个元素12分钟,重新启动定时器进行计时。 在12分钟的时间间隔内,移动终端再次切换注册2G或3G网络。 当重计时间达到12分钟时,根据移动终端第三次注册4G网络时所在小区的邻区TAI,控制移动终端重新注册4G网络。 以此类推,移动终端每12分钟重新搜索一次4G网络。 这样可以保证用户在TAU被网络拒绝的情况下可以注册到其他速率的网络,避免无连接的网络服务状态。 [0092] 图4是根据本发明实施例的移动终端的网络注册装置的框图。 网络注册设备 40 移动终端的功能可以通过软件、硬件或其组合来实现。 网络注册设备 40 移动终端的可以包括阅读模块 401 , 第一控制模块 402 , 一个起始模块 403 , 第一判断模块 404 , 处理模块 405 和第二个控制模块 406 . [0093] 阅读模块 401 被配置为读取元素 T i 在时间数组中 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}响应于确定移动终端注册第一网络时发生预定异常事件,其中i为1至N之间的正整数,N为正整数。 [0094] 或者,预定异常事件包括TAU被拒绝。 [0095] 第一控制模块 402 用于禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0096] 启动模块 403 用于启动定时器进行计时,得到第一计时时间。 [0097] 第一判断模块 404 配置为判断第一个计数时间是否达到T i . [0098] 处理模块 405 被配置为当第一次计数时间达到T时获得第一身份 i 其中,第一标识为移动终端注册第一网络时所在小区的相邻小区的跟踪区标识。 [0099] 第二控制模块 406 用于控制移动终端根据第一标识重新注册第一网络。 [0100] 或者,在一些实施例中,如图5所示,网络注册装置 40 移动终端还可以包括第二判断模块 407 , 第三个控制模块 408 , 第三判断模块 409 , 第一获取模块410 , 第四控制模块 411 , 第二个获取模块 412 , 和一个设置模块 413 . [0101] 第二判断模块 407 用于判断移动终端重新注册第一网络时是否发生预定异常事件。 [0102] 第三控制模块 408 用于当预定异常事件发生时,控制移动终端重新注册第二网络,并重置定时器重新计时,得到第二计时时间。 [0103] 第三判断模块 409 用于判断第二次计数时间是否达到T i+1 . [0104] 第一个获取模块 410 用于在秒计数时间达到T时获取第二身份 i+1 其中,第二标识为移动终端在重新注册第一网络时所在小区的相邻小区的跟踪区标识。 [0105] 第四个控制模块 411 用于控制移动终端根据第二标识重新注册第一网络。 [0106] 或者,处理模块 405 还用于当第一计时时间未达到T时,继续控制移动终端注册第二网络 i . [0107] 第二个获取模块 412 用于获取TAU被拒绝的信息,并将该信息发送给服务器,使得服务器根据该信息备份预定的异常事件。 [0108] 设置模块 413 被配置为设置元素T的值 i 根据用户命令在时间数组中。 [0109] 需要说明的是,结合图1-图3对移动终端的网络注册方法实施例的说明同样适用于移动终端的网络注册装置,其原理类似,在此不再赘述。 [0110] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i 以及根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率。 网络。 [0111] 本发明实施例还提供了一种移动终端。 该移动终端包括外壳、处理器、存储器、电路板和供电电路。 电路板设置于壳体所围成的空间内。 处理器与存储器配置于电路板上。 供电电路,用于为移动终端的各个电路或部件供电。 存储器被配置为存储可执行程序代码。 处理器用于通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0112] 在小号 11 ′, 一个元素 T i 响应于移动终端注册第一网络时确定发生预定异常事件,读取时间数组中的in,时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0113] 本发明实施例以移动终端注册4G网络为例进行说明。 [0114] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0115] 或者,预定异常事件包括TAU被拒绝。 [0116]第一个网络是4G网络。 [0117] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0118] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0119] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0120] 在小号 12 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0121] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0122] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . ,T},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0123] 在小号 13 ',启动定时器计时,得到第一计时时间。 [0124] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0125] 在小号 14 ′,判断第一个计数时间是否达到T i . [0126] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0127] 在另一个实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0128] 在小号 21 ′,当第一次计数时间未达到 T 1 ,继续控制移动终端注册第二网络。 [0129] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0130] 在小号 15 ′,当第一个计数时间到达T i ,获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0131] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0132] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0133] 在小号 16 ',控制移动终端根据第一标识重新注册第一网络。 [0134] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当次数的计数时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . ,T}并重新设置定时器重新计时,在T的时间间隔内切换到重新注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0135] 本实施例通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(TAI of 移动终端注册第一个网络时所在小区的邻区)第一个计数时间到达T时 i ,并且根据第一标识控制移动终端重新注册第一网络,当当前TAU被网络拒绝时,移动终端可以注册不同TAI的小区的网络,有效提高注册成功率 网络。 [0136] 在另一个实施例中,处理器被配置为通过读取存储在存储器中的可执行程序代码来运行与可执行程序代码对应的程序,以执行以下动作。 [0137] 在小号 301 ′,元素T的值 i 根据用户命令设置时间数组中的。 [0138] 在这个实施例中,元素T的值 i 时间数组中的时间可以由用户根据自己的需求预先设置。 [0139] 例如,移动终端可以接收用户在屏幕上输入的命令,设置元素T的值 i 根据用户命令在时间数组中。 元素 T 的值 i 时间数组中的信息可以是用户在屏幕上依次输入的,也可以是用户选择性输入的,不做限定。 [0140] 在这个动作中,时间 T i 时间序列的长度由用户设置,从而可以实现时间序列的个性化设置,可以提高移动终端网络注册方法的通用性,可以提高移动终端网络注册的成功率 得到加强。 [0141] 在小号 302 ',判断移动终端注册第一网络时是否发生预定异常事件,如果是,S 303 被执行,如果没有,S 315 被执行。 [0142] 本发明实施例以移动终端注册4G网络为例进行说明。 [0143] 本发明实施例的执行主体例如可以是移动终端内置的调制解调器。 [0144] 或者,预定异常事件包括TAU被拒绝。 [0145] 第一个网络是4G网络。 [0146] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 本实施例应用于移动终端注册网络的过程中,在TAU被拒绝后应用。 [0147] 或者,也可以在移动终端注册4G网络的过程中判断TAU被网络拒绝的事件是否发生,以触发后续动作。 [0148] 在小号 303 ′,元素 T i 在时间数组中读取,其中时间数组为{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},i是1到N之间的正整数,N是正整数。 [0149] 在本发明实施例中,当移动终端因TAU被拒绝而无法注册网络时,可以启动时间数组,将元素T i 在时间数组中可以读取。 例如,当移动终端最初注册第一网络失败时,元素T 1 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},控制移动终端在时间间隔T内注册不同速率的网络,例如2G网络或3G网络 1 , 保证移动端可以正常上网。 当移动台第二次注册第一个网络失败时,元素 T 2 可以从时间数组中读取{T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}, 等等。 元素T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,以提高移动终端注册第一网络的成功率,不限。 [0150] 元素 T 的值 i 时间数组中的in可以由用户根据自己的需求进行设置,也可以由移动终端的厂商预先设置,在此不做限定。 [0151] 在小号 304 ',则禁止移动终端注册第一网络,控制移动终端注册第二网络。 [0152] 在本公开的实施例中,第二网络具有不同于第一网络的传输速率。 例如,第二网络可以是2G网络,也可以是3G网络,不作限定。 [0153] 在本发明实施例中,当移动终端最初注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册网络 不同速率,例如2G网络或3G网络,在时间间隔T 1 . 或者,当移动终端交替读取元素T时 i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i ,从而有效保证移动终端可以正常上网。 [0154] 在小号 305 ',启动定时器计时,得到第一个计时时间。 [0155] 在本发明实施例中,在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器进行计时,得到第一计时时间。 移动终端可以判断注册第二网络的时长是否达到T i 按第一次计算时间计算,不限时。 [0156] 在小号 306 ′,判断第一个计数时间是否达到T i ,如果是,S 308 被执行,如果没有,S 307 被执行。 [0157] 在本发明实施例中,可以判断第一次计时时间是否达到T i ,判断是否触发移动终端重新注册第一网络,不做限定。 [0158] 在小号 307 ',继续控制移动终端注册第二网络。 [0159] 本次动作中,通过在第一次计时时间未达到T时,继续控制移动终端注册第二网络 i ,可以保证用户在TAU被网络拒绝时,能够以不同的速率注册网络,避免无连接的网络服务状态,有效提升用户体验。 [0160] 在小号 308 ',获取第一标识,第一标识为移动终端注册第一网络时所在小区的相邻小区的TAI。 [0161] 在本发明实施例中,当第一次计数时间达到T i ,可以获取移动终端注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0162] 移动终端注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0163] 在小号 309 ',控制移动终端根据第一标识重新注册第一网络。 [0164] 在本发明实施例中,当移动终端因TAU被拒绝而第一次注册第一网络失败时,移动终端读取元素T 1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 1 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 1 . 然后,当定时器的计时时间达到T 1 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 2 . 当重计时间到达T 2 ,根据第二次注册第一网络时移动终端所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0165] 在小号 310',判断移动终端重新注册第一网络时是否发生预定异常事件,如果是,S 311 被执行,如果没有,S 315 被执行。 [0166] 可以理解的是,在用户使用移动终端接入4G网络的过程中,可能会出现注册网络失败的响应,其中注册网络失败可能是由于TAU是 被拒绝,或者可能是其他原因造成的。 [0167] 或者,在移动终端重新注册第一网络时,判断TAU是否被网络拒绝,以触发后续动作。 [0168] 在小号 311 ',控制移动终端重新注册第二网络,定时器重新计时,得到第二计时时间。 [0169] 在本发明实施例中,当移动终端重新注册第一网络失败时,以及当移动终端因TAU被拒绝而无法注册第一网络时,可以控制移动终端切换到注册第一网络。 不同速率的网络,例如2G网络或3G网络,在时间间隔T 2 . 或者,当移动终端交替读取元素T时 i+1 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n},移动终端可以在T的时间间隔内切换到不同速率的网络注册 i+1 ,从而有效保证移动终端可以正常上网。 [0170] 在禁止移动终端注册第一网络,控制移动终端注册第二网络的同时,可以启动定时器计时,得到第二计时时间。 移动终端可以判断注册第二网络的时长是否达到T i+1 按秒计时,不限时。 [0171] 在小号 312 ′,判断第二次计时是否达到T i+1 . [0172] 在本发明实施例中,可以判断第二计时时间是否达到T i+1 ,判断是否触发移动终端重新注册第一网络,不做限定。 [0173] 在小号 313 ′,当第二次计数时间到达T i+1 ,获取第二标识,第二标识为移动终端重新注册第一网络时所在小区的邻小区的TAI。 [0174] 在本发明实施例中,当第二计时时间达到T i+1 ,可以获取移动终端在重新注册第一网络时所在小区的邻区TAI,以控制移动终端根据邻区TAI重新注册第一网络。 [0175] 移动终端重新注册第一网络时所在小区的邻区TAI可以通过现有技术获得,在此不再赘述。 [0176] 在小号 314 ',控制移动终端根据第二标识重新注册第一网络。 [0177] 在本发明实施例中,当移动终端因TAU被拒绝而无法重新注册第一网络时,移动终端读取元素T 2 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n}. 在 T 的时间间隔内 2 ,移动终端被禁止注册第一网络,转注册第二网络,并在T时间间隔内接入第二网络 2 . 然后,当定时器的计时时间达到T 2 ,根据邻区的TAI控制移动终端重新注册第一网络。 如果注册成功,则移动终端接入第一网络。 如果注册失败,移动端读取元素T 3 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 并重新设置定时器重新计时,并在T的时间间隔内再次切换注册第二个网络 3 . 当重计时间到达T 3 ,在第二次注册第一网络时,根据移动终端注册所在小区的邻区TAI,控制移动终端重新注册第一网络。 以此类推,元素 T i 在时间数组 {T 1 , 吨 2 ,. . . , 吨 i , 吨 i+1 ,. . . , 吨 n} 交替读取,直到移动终端成功注册第一个网络,不做限制。 [0178] 在小号 315 ',获取TAU被拒绝的信息并发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0179] 或者,移动终端获取TAU被网络拒绝的信息,并将该信息发送给服务器,以便服务器根据该信息备份预定的异常事件。 [0180] 在这个实施例中,时间T i 时间序列的长度由用户设置,可以实现时间序列的个性化设置,提高移动终端网络注册方法的通用性。 通过在移动终端注册第一网络的过程中发生预定异常事件时控制移动终端注册第二网络,可以保证用户注册网络成功,并通过获取第一标识(相邻小区的TAI) 移动终端注册第一个网络时所在的小区)当第一个计数时间到达T时 i , 当第二次计数时间达到T时,获取第二标识(移动终端重新注册第一网络时所在小区的邻区TAI) i+1 ,并且控制移动终端根据第一标识或第二标识重新注册第一网络,移动终端可以在当前TAU被网络拒绝时注册不同TAI的小区的网络,从而有效地增强了 网络注册成功率。 [0181] 上述装置实施例仅仅是示例性的,其中作为单独的部件示出的单元在物理上可以是分离的,也可以不是物理分离的,作为单元示出的部件可以是物理单元也可以不是物理单元,即可以位于一个空间内,或者可以是物理单元。 分布到多个网络单元。 可以根据实际需要选择其中的部分或全部模块来实现本发明的目的。 本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0182] 本发明方法实施例中的动作可以根据实际需要进行调整、合并或者删除。 [0183] 本发明装置实施例中的模块或单元可以根据实际需要进行合并、划分和删除。 [0184] 本发明实施例中的模块或单元可以采用通用集成电路(如CPU)实现,也可以采用专用集成电路(ASIC)实现。 [0185] 通过以上对实施例的描述,本领域的技术人员可以清楚地了解到,各个实施例可以通过软件结合必要的通用硬件平台来实现,也可以通过硬件来实现。 基于这种理解,上述技术方案的本质或者对相关技术有贡献的部分可以以软件产品的形式体现。 计算机软件产品可以存储在计算机可读存储介质中,例如ROM/RAM、磁盘、CD等,可以包括若干指令,用于使计算机设备(可以是个人计算机、服务器或 网络设备)执行各个实施例或实施例的部分描述的方法。 [0186] 上述实施方式并不构成对本发明保护范围的限制。 凡在本发明的精神和范围内所作的任何修改、等同或者改进,均包含在本技术方案的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105933884A(String), CN105933884B(String), US10419919B2(String), US10419920B2(String), US20190045350A1(String), US20190141514A1(String), WO2017219897A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), CN105933884A(String), 1049595(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.612 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), CN105933884B(String), 1048249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.649 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), US10419919B2(String), 1049596(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), US10419920B2(String), 1049597(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), US20190045350A1(String), 1049598(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), US20190141514A1(String), 1049599(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271206(Integer), WO2017219897A1(String), 1049600(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN105933884B(String), CN105933884B(String), 1522339200(Integer), 271206(Integer), 185490(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185947(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 1(Integer), 185947(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:33:59.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185947(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 2(Integer), 185947(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.374 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185947(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10469652B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, method for mobile terminal to set font display state, and storage medium(String), 移动终端、移动终端设置字体显示状态的方法及存储介质(String), US10469652B2(String), Disclosed are a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. The method may comprise: acquiring, by a mobile terminal, a current shake level; searching, by the mobile terminal, a corresponding relationship between a shake level and a font display state according to the current shake level, to acquire a font display state corresponding to the current shake level of the mobile terminal; and setting, by the mobile terminal, a default font display state as the font display state corresponding to the current shake level of the mobile terminal.(String), 本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 该方法可以包括: 移动终端获取当前抖动程度; 移动终端根据当前抖动级别查找抖动级别与字体显示状态的对应关系,获取移动终端当前抖动级别对应的字体显示状态; 移动终端设置默认字体显示状态为移动终端当前抖动级别对应的字体显示状态。(String), US15/511022(String), 1418572800(Integer), US10469652B2(String), 1572883200(Integer), 1572883200(Integer), 美国(String), 4(Integer), CN(String), 3(Integer), 27(Integer), CN102239471A | CN102541254A | CN103176623A | CN103176694A | CN103200323A | CN103246441A | CN103248749A | CN103309582A | JP2003169125A | JP2005006161A | JP2005012297A | JP2006201006A | US20080254837A1 | US20090186659A1 | US20100103197A1 | US20110208472A1 | US20120081281A1 | US20130235058A1 | US20130254657A1 | US20130293589A1 | US20150177826A1 | US20150192424A1 | US20150212611A1 | US20150248378A1 | US20150296034A1 | US20160259420A1 | US9430450B1(String), 9(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185948(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.933 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0fcb0eee096547098f99d16d85e47890.png(String), 185948(Integer), 0fcb0eee096547098f99d16d85e47890.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:00.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, method for mobile terminal to set font display state, and storage medium(String), 移动终端、移动终端设置字体显示状态的方法及存储介质(String), US10469652B2(String), Disclosed are a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. The method may comprise: acquiring, by a mobile terminal, a current shake level; searching, by the mobile terminal, a corresponding relationship between a shake level and a font display state according to the current shake level, to acquire a font display state corresponding to the current shake level of the mobile terminal; and setting, by the mobile terminal, a default font display state as the font display state corresponding to the current shake level of the mobile terminal.(String), 本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 该方法可以包括: 移动终端获取当前抖动程度; 移动终端根据当前抖动级别查找抖动级别与字体显示状态的对应关系,获取移动终端当前抖动级别对应的字体显示状态; 移动终端设置默认字体显示状态为移动终端当前抖动级别对应的字体显示状态。(String), US15/511022(String), 1418572800(Integer), US10469652B2(String), 1572883200(Integer), 1572883200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 3(Integer), 27(Integer), CN102239471A | CN102541254A | CN103176623A | CN103176694A | CN103200323A | CN103246441A | CN103248749A | CN103309582A | JP2003169125A | JP2005006161A | JP2005012297A | JP2006201006A | US20080254837A1 | US20090186659A1 | US20100103197A1 | US20110208472A1 | US20120081281A1 | US20130235058A1 | US20130254657A1 | US20130293589A1 | US20150177826A1 | US20150192424A1 | US20150212611A1 | US20150248378A1 | US20150296034A1 | US20160259420A1 | US9430450B1(String), \20230420\0fcb0eee096547098f99d16d85e47890.png(String), 9(Integer), 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 1. A method for a mobile terminal to set a font display state comprising:acquiring, by the mobile terminal, a current jitter level;searching, by the mobile terminal, a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; andsetting, by the mobile terminal, a default font display state as the font display state corresponding to the current jitter level of the mobile terminal;wherein acquiring, by the mobile terminal, the current jitter level comprises:acquiring, by the mobile terminal, a first acceleration range absolute value within a first preset time period, and comparing the first acceleration range absolute value with a preset acceleration range absolute value threshold;acquiring, by the mobile terminal, at least two second acceleration range absolute values within a second preset time period when the first acceleration range absolute value is larger than the preset acceleration range absolute value threshold;acquiring, by the mobile terminal, a third acceleration range absolute value, which is larger than the preset acceleration range absolute value threshold, from each of the at least two second acceleration range absolute values; andacquiring, by the mobile terminal, an average value of the third acceleration range absolute values when a number of the third acceleration range absolute values is not smaller than a first preset number; andwherein searching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the current jitter level, to acquire the font display state corresponding to the current jitter level of the mobile terminal, comprises:searching, by the mobile terminal, a correspondence relationship between an acceleration range absolute value and the font display state according to the average value, to acquire a font display state corresponding to the average value.(String), 1、一种移动终端设置字体显示状态的方法包括:移动终端获取当前的抖动水平;移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态;和移动终端将默认的字体显示状态设置为移动终端当前抖动等级对应的字体显示状态;其中,移动终端获取当前抖动水平包括:移动终端获取第一预设时间段内的第一加速度范围绝对值,将第一加速度范围绝对值与预设加速度范围绝对值阈值进行比较;当第一加速度范围绝对值大于预设加速度范围绝对值阈值时,移动终端在第二预设时间段内获取至少两个第二加速度范围绝对值;移动终端分别从至少两个第二加速度范围绝对值中获取大于预设加速度范围绝对值阈值的第三加速度范围绝对值;和当第三加速度范围绝对值的个数不小于第一预设数量时,移动终端获取第三加速度范围绝对值的平均值;和其中,移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态,包括:移动终端根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取平均值对应的字体显示状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 2. The method according to claim 1, wherein acquiring, by the mobile terminal, the first acceleration range absolute value within the first preset time period comprises:acquiring, by the mobile terminal, a first original acceleration and a second original acceleration within the first preset time period;processing, by the mobile terminal, the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively;processing, by the mobile terminal, the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively; andperforming, by the mobile terminal, an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value.(String), 2.根据权利要求1所述的方法,其中移动终端获取第一预设时间段内的第一加速度范围绝对值包括:移动终端获取第一预设时间内的第一原始加速度和第二原始加速度;移动终端通过低通滤波器处理第一原始加速度和第二原始加速度,分别获取第一加速度中值和第二加速度中值;移动终端通过高通滤波器处理第一加速度中值和第二加速度中值,分别获取第一加速度和第二加速度;和移动终端对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 3. The method according to claim 1, wherein when a current font display state of the mobile terminal is not the default font display state, the method further comprises:acquiring, by the mobile terminal, at least two fourth acceleration range absolute values within a third time period;acquiring, by the mobile terminal, an updated jitter level when a number of those larger than the preset acceleration range absolute value threshold among the at least two fourth acceleration range absolute values is not smaller than a second preset number;searching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; andsetting, by the mobile terminal, the current font display state as the font display state corresponding to the updated jitter level of the mobile terminal.(String), 3.根据权利要求1所述的方法,其中当移动终端当前的字体显示状态不是默认字体显示状态时,该方法还包括:移动终端在第三时间段内获取至少两个第四加速度范围绝对值;当所述至少两个第四加速度范围绝对值中大于预设加速度范围绝对值阈值的个数不小于第二预设个数时,移动终端获取更新后的抖动水平;移动终端根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态;和移动终端将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 4. A mobile terminal comprising a processor and a memory for storing instructions executable by the processor, wherein the processor is arranged to:acquire a current jitter level;search a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; andset a default font display state as the font display state corresponding to the current jitter level of the mobile terminal;wherein the processor is further arranged to:acquire a first acceleration range absolute value within a first preset time period, and compare the first acceleration range absolute value with a preset acceleration range absolute value threshold;acquire at least two second acceleration range absolute values within a second preset time period when the first acceleration range absolute value is larger than the preset acceleration range absolute value threshold;acquire a third acceleration range absolute value, which is larger than the preset acceleration range absolute value threshold, from each of the at least two second acceleration range absolute values;acquire an average value of the third acceleration range absolute values when a number of the third acceleration range absolute values is not smaller than a first preset number; andsearch a correspondence relationship between an acceleration range absolute value and the font display state according to the average value, to acquire a font display state corresponding to the average value.(String), 4.移动端包括处理器和用于存储可由处理器执行的指令的存储器,其中处理器被布置成:获取当前抖动水平;根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态;和设置默认字体显示状态为移动终端当前抖动等级对应的字体显示状态;其中,处理器还被布置成:在第一预设时间段内获取第一加速度范围绝对值,并将第一加速度范围绝对值与预设加速度范围绝对值阈值进行比较;当第一加速度范围绝对值大于预设加速度范围绝对值阈值时,在第二预设时间段内获取至少两个第二加速度范围绝对值;从至少两个第二加速度范围绝对值中的每一个获取大于预设加速度范围绝对值阈值的第三加速度范围绝对值;当第三加速度范围绝对值的个数不小于第一预设数量时,获取第三加速度范围绝对值的平均值;和根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取该平均值对应的字体显示状态。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 5. The mobile terminal according to claim 4, wherein the processor is further arranged to:acquire a first original acceleration and a second original acceleration within the first preset time period;process the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively;process the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively; andperform an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value.(String), 5.根据权利要求4所述的移动终端,其中处理器还被布置成:在第一预设时间段内获取第一原始加速度和第二原始加速度;通过低通滤波器处理第一原始加速度和第二原始加速度,分别获得第一加速度中值和第二加速度中值;通过高通滤波器对第一加速度中值和第二加速度中值进行处理,分别得到第一加速度和第二加速度。和对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 6. The mobile terminal according to claim 4, wherein when a current font display state of the mobile terminal is not the default font display state, the processor is further arranged to:acquire at least two fourth acceleration range absolute values within a third time period;acquire an updated jitter level when a number of those larger than the preset acceleration range absolute value threshold among the at least two fourth acceleration range absolute values is not smaller than a second preset number;search the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; andset the current font display state as the font display state corresponding to the updated jitter level of the mobile terminal.(String), 6.根据权利要求4所述的移动终端,其中当移动终端当前的字体显示状态不是默认字体显示状态时,处理器还用于:在第三时间段内获取至少两个第四加速度范围绝对值;当至少两个第四加速度范围绝对值中大于预设加速度范围绝对值阈值的个数不小于第二预设个数时,获取更新的抖动水平;根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态;和将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.059 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 7. A non-transitory computer storage medium storing a computer program for performing a method for a mobile terminal to set a font display state, the method comprising:acquiring, by the mobile terminal, a current jitter level;searching, by the mobile terminal, a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; andsetting, by the mobile terminal, a default font display state as the font display state corresponding to the current jitter level of the mobile terminal;wherein acquiring, by the mobile terminal, the current jitter level comprises:acquiring, by the mobile terminal, a first acceleration range absolute value within a first preset time period, and comparing the first acceleration range absolute value with a preset acceleration range absolute value threshold;acquiring, by the mobile terminal, at least two second acceleration range absolute values within a second preset time period when the first acceleration range absolute value is larger than the preset acceleration range absolute value threshold;acquiring, by the mobile terminal, a third acceleration range absolute value, which is larger than the preset acceleration range absolute value threshold, from each of the at least two second acceleration range absolute values; andacquiring, by the mobile terminal, an average value of the third acceleration range absolute values when a number of the third acceleration range absolute values is not smaller than a first preset number; andwherein searching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the current jitter level, to acquire the font display state corresponding to the current litter level of the mobile terminal, comprises:searching, by the mobile terminal, a correspondence relationship between an acceleration range absolute value and the font display state according to the average value, to acquire a font display state corresponding to the average value.(String), 7.一种非暂时性计算机存储介质,存储用于执行移动终端设置字体显示状态的方法的计算机程序,该方法包括:移动终端获取当前的抖动水平;移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态;和移动终端将默认的字体显示状态设置为移动终端当前抖动等级对应的字体显示状态;其中,移动终端获取当前抖动水平包括:移动终端获取第一预设时间段内的第一加速度范围绝对值,将第一加速度范围绝对值与预设加速度范围绝对值阈值进行比较;当第一加速度范围绝对值大于预设加速度范围绝对值阈值时,移动终端在第二预设时间段内获取至少两个第二加速度范围绝对值;移动终端分别从至少两个第二加速度范围绝对值中获取大于预设加速度范围绝对值阈值的第三加速度范围绝对值;和当第三加速度范围绝对值的个数不小于第一预设数量时,移动终端获取第三加速度范围绝对值的平均值;和其中,移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前乱码等级对应的字体显示状态,包括:移动终端根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取平均值对应的字体显示状态。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.059 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 8. The non-transitory computer storage medium according to claim 7, wherein acquiring, by the mobile terminal, the first acceleration range absolute value within the first preset time period comprises:acquiring, by the mobile terminal, a first original acceleration and a second original acceleration within the first preset time period;processing, by the mobile terminal, the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively;processing, by the mobile terminal, the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively; andperforming, by the mobile terminal, an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value.(String), 8.根据权利要求7所述的非暂时性计算机存储介质,其中移动终端获取第一预设时间段内的第一加速度范围绝对值包括:移动终端获取第一预设时间内的第一原始加速度和第二原始加速度;移动终端通过低通滤波器处理第一原始加速度和第二原始加速度,分别获取第一加速度中值和第二加速度中值;移动终端通过高通滤波器处理第一加速度中值和第二加速度中值,分别获取第一加速度和第二加速度;和移动终端对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.059 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185948(Integer), 9. The non-transitory computer storage medium according to claim 7, wherein when a current font display state of the mobile terminal is not the default font display state, the method further comprises:acquiring, by the mobile terminal, at least two fourth acceleration range absolute values within a third time period;acquiring, by the mobile terminal, an updated jitter level when a number of those larger than the preset acceleration range absolute value threshold among the at least two fourth acceleration range absolute values is not smaller than a second preset number; andsearching, by the mobile terminal, the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; andsetting, by the mobile terminal, the current font display state as the font display state corresponding to the updated jitter level of the mobile terminal.(String), 9.根据权利要求7所述的非暂时性计算机存储介质,其中当移动终端当前的字体显示状态不是默认字体显示状态时,该方法还包括:移动终端在第三时间段内获取至少两个第四加速度范围绝对值;当所述至少两个第四加速度范围绝对值中大于预设加速度范围绝对值阈值的个数不小于第二预设个数时,移动终端获取更新后的抖动水平;和移动终端根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态;和移动终端将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185948(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of mobile terminals, and in particular to a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. BACKGROUND [0002]Currently, a mobile terminal is widely used in daily life of users. During the use of the mobile terminal, for example when a user is on a public transportation, the user cannot see clearly the content on a screen of the terminal because of an external jitter, thereby causing user asthenopia. SUMMARY [0003]In order to solve the technical problem described above, the disclosure discloses a mobile terminal, a method for the mobile terminal to set a font display state and a storage medium. [0004]The technical solution of the disclosure is implemented as follows. [0005]According to a first aspect, the disclosure discloses a method for a mobile terminal to set a font display state including: a mobile terminal acquires a current jitter level; the mobile terminal searches a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal; and the mobile terminal sets a default font display state as the font display state corresponding to the current jitter level of the mobile terminal. [0006]According to a second aspect, the disclosure discloses a mobile terminal including an acquiring unit, a searching unit and a setting unit. The acquiring unit is arranged to acquire a current jitter level. The searching unit is arranged to search a correspondence relationship between a jitter level and a font display state according to the current jitter level, to acquire a font display state corresponding to the current jitter level of the mobile terminal. The setting unit is arranged to set a default font display state as the font display state corresponding to the current jitter level of the mobile terminal. [0007]According to a third aspect, the disclosure discloses a computer storage medium storing a computer program for performing the method for a mobile terminal to set a font display state as described above. [0008]The disclosure discloses a mobile terminal, a method for the mobile terminal to set a font display state, and a storage medium. A jitter degree of a mobile terminal is acquired and a font state displayed on the screen of the mobile terminal is set according to the jitter degree. Thus a user can see the content on the screen of the mobile terminal clearly when external jitter exists, and the user asthenopia can be avoided. BRIEF DESCRIPTION OF THE DRAWINGS [0009]FIG. 1 is a flowchart of a method for a mobile terminal to set a font display state; [0010]FIG. 2 is a flowchart of a method for a mobile terminal to acquire a current jitter level; [0011]FIG. 3 is a structural diagram of a mobile terminal according to an embodiment of the disclosure; [0012]FIG. 4 is a block diagram of a mobile terminal according to an embodiment of the disclosure; [0013]FIG. 5 is a block diagram of font sizes according to an embodiment of the disclosure; [0014]FIG. 6 is a table showing acceleration with respect to time periods according to an embodiment of the disclosure. DETAILED DESCRIPTION [0015]The technical solution in embodiments of the disclosure will be described clearly and completely below with reference to the drawings in the embodiments of the disclosure. [0016]In the embodiments of the disclosure, a jitter degree of a mobile terminal is acquired at first, and then a font state displayed on the mobile terminal screen is correspondingly set according to the jitter degree. The font state may include, but not limited to a font size, a font type and a font color etc. The embodiments of the disclosure are described with the font size (in FIG. 5) being as an example. It will be understood that other font states may be set according to the technical solution in embodiments of the disclosure. [0017]Refer to FIG. 1 which shows a method for a mobile terminal to set a font display state according to an embodiment of the disclosure. The method may be used in a mobile terminal. For example, rather than limit, the mobile terminal may include, but not limited to a portable terminal device such as a phone, a tablet computer or a notebook computer etc. The method may include the following steps. [0018]At step S101, a mobile terminal acquires a current jitter level. It is important to note that the current jitter level is a basis for setting a font display state. Only if the jitter level is acquired accurately, the font state as which the font display state should be set can be determined. [0019]For example, as shown in FIG. 2, the mobile terminal acquiring the current jitter level may include steps S201-S204. [0020]At step S201, the mobile terminal acquires a first acceleration range absolute value within a preset first time period (in FIG. 6), and compares the first acceleration range absolute value with a preset acceleration range absolute value threshold. It is important to note that the step S201 is used for judging whether the jitter is caused by an external shake, which is a necessary condition for acquiring the current jitter level. Thus, the acceleration range absolute value threshold may be set to judge whether the jitter is caused by the external shake. [0021]Alternatively, the mobile terminal acquiring the first acceleration range absolute value within the preset first time period may include the following steps. Firstly, the mobile terminal detects and acquires two accelerations, i.e. a first original acceleration and a second original acceleration, within the preset first time period through a built-in acceleration sensor. Then, the first original acceleration and the second original acceleration are processed through a low-pass filter, to acquire a first acceleration median and a second acceleration median, respectively. Then, the first acceleration median and the second acceleration median are processed through a high-pass filter, to acquire a first acceleration and a second acceleration, respectively. At last, an absolute value computation is implemented on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value. [0022]It is important to note that the preset first time period T1 is a time interval between the two acceleration detections of the acceleration sensor, which may be set in default by a system, or set by a user. The first original acceleration and the second original acceleration detected and acquired by the acceleration sensor may be represented by a vector synthesis of acceleration components on three orthogonal coordinate axis. [0023]Generally, the first original acceleration and the second original acceleration may be interfered by gravity. Thus, preferably, in the embodiment, the first original acceleration and the second original acceleration are processed by the mobile terminal through the low-pass filter, then the first acceleration median and the second acceleration median are processed through the high-pass filter, to acquire the first acceleration and the second acceleration respectively. In such a way, the interference of the gravity may be eliminated. It will be understood that the first acceleration and the second acceleration may also be represented by the vector synthesis of acceleration components on three orthogonal coordinate axis. In the embodiment, the module value of the first acceleration can be represented as follows: a1=√{square root over (x12+y12+z12)} where, a1 is the module value of the first acceleration in a unit of m/s2, x1 is a component value of the first acceleration in x-axis direction, y1 is a component value of the first acceleration in y-axis direction, z1 is a component value of the first acceleration in z-axis direction, and units of x1, y1 and z1 are m/s2. [0024]Correspondingly, the module value of the second acceleration can be represented as follows: a2=√{square root over (x22+y22+z22)} where, a2 is the module value of the second acceleration in a unit of m/s2; x2 is a component value of the second acceleration in x-axis direction, y2 is a component value of the second acceleration in y-axis direction, z2 is a component value of the second acceleration in z-axis direction, and units of x2, y2 and z2 are m/s2. [0025]Preferably, the first acceleration range absolute value can be obtained through the following formula: a=|a2−a1| where, a is the first acceleration range absolute value, a1 is the module value of the first acceleration, a2 is the module value of the second acceleration, and units of a, a1 and a2 are m/s2. [0026]At step S202, when the first acceleration range absolute value is larger than the acceleration range absolute value threshold, the mobile terminal acquires at least two second acceleration range absolute values within a preset second time period (in FIG. 6). It is important to note that when the first acceleration range absolute value is larger than the acceleration range absolute value threshold, it may be determined that the jitter is caused by the external environment. Subsequently, it is needed to detect the duration time of the jitter. For example, in the embodiment, the mobile terminal acquires N second acceleration range absolute values within the second time period T2, where N≥2. It will be understood that the second acceleration range absolute values is acquired in the same way as the first acceleration range absolute value is acquired in S201, and will not be repeated here again. [0027]At step S203, the mobile terminal acquires a third acceleration range absolute value, which is larger than the acceleration range absolute value threshold, from the second acceleration range absolute values. In the embodiment, among N second acceleration range absolute values, the mobile terminals may count a number of the second acceleration range absolute values larger than the acceleration range absolute value threshold, to acquire M third acceleration range absolute values, where M≥1. [0028]At step S204, when the number of the third acceleration range absolute values is not smaller than a preset first number, the mobile terminal acquires an average value of the third acceleration range absolute values. It is important to note that in the embodiment, the mobile terminal compares M with the preset first number, and when M is smaller than the preset first number, it means that the jitter occurs occasionally or the jitter degree is not violent. At this point, there is no need for the mobile terminal to adjust the font display state. When M is not smaller than the preset first number, it means that the jitter is not occasional, but lasts for a certain time and has affected the reading of the user. At this point, the jitter degree is evaluated through the average value of the third acceleration range absolute values, which is a worst estimation of the jitter level. [0029]Alternatively, for those skilled in the art, it is possible to evaluate the jitter degree through the last acquired third acceleration range absolute value, which is not repeated here again. [0030]At step S102, the mobile terminal searches a correspondence relationship between the jitter level and the font display state according to the current jitter level, to acquire the font display state corresponding to the current jitter level of the mobile terminal. Preferably, the correspondence relationship between the jitter level and the font display state can be represented by a mapping table shown in table 1, or can be represented by other methods capable of expressing the correspondence relationship, which are not limited in the embodiment: [0031]TABLE 1Jitter levelFont display stateFirst jitter levelFirst font display stateSecond jitter levelSecond font display stateThird jitter levelThird font display state [0032]In the embodiment, it can be seen from S201-S204 that the jitter level is represented by the average value of the third acceleration range absolute values. Thus, preferably, the average value of the third acceleration range absolute values can be correspondingly divided into four sections, which are corresponding to the font display sizes one by one. Thus a correspondence relationship represented in Table 2 is obtained: [0033]TABLE 2Acceleration range absolute value(unit: m/s2)Font display size0-3Normal font4-6Middle-small font7-9Middle-large font10-12Large font [0034]At step S103, the mobile terminal sets a default font display state as the font display state corresponding to the current jitter level of the mobile terminal. [0035]It is important to note that after the end of the above process, the font display state is changed from the default font display state to a font display state corresponding to the current jitter level. However, in general, the jitter changes over time, and one jitter level will not last for a long time. In order to adapt to the changes, the font display state needs to be adjusted on time according to changes of the jitter level. [0036]Preferably, when the current font display state of the mobile terminal is not the default font display state, the method further includes: the mobile terminal acquiring at least two fourth acceleration range absolute values within a third time period; when the number of the fourth acceleration range absolute value(s) among at least two fourth acceleration range absolute values larger than the acceleration range absolute value threshold is not smaller than a second preset number, the mobile terminal acquiring an updated jitter level; the mobile terminal searching the correspondence relationship between the jitter level and the font display state according to the updated jitter level, to acquire a font display state corresponding to the updated jitter level of the mobile terminal; and the mobile terminal setting the current font display state to the font display state corresponding to the updated jitter level of the mobile terminal. [0037]It will be understood that a level difference between the font display state corresponding to the updated jitter level of the mobile terminal and the current font display state can be level-skipped. For example, currently displayed normal font size can be set as a middle-large font or a large font, and it will not be repeated here again in the embodiment of the disclosure. [0038]The disclosure discloses a method for a mobile terminal to set a font display state. A jitter degree of the mobile terminal may be acquired and the font state displayed on the mobile terminal screen may be set according to the jitter degree. Thus a user can see the content on the mobile terminal screen clearly when external shake exists, and the user asthenopia can be avoided. [0039]Based on a technical concept which is the same as the above embodiment, as shown in FIG. 3, a structure of a mobile terminal 30 is provided in the embodiment of the disclosure. For example, rather than limit, the mobile terminal may include, but not limited to, a portable terminal device such as a phone, a tablet computer or a notebook computer etc. The mobile terminal 30 may include an acquiring unit 301, a searching unit 302 and a setting unit 303. The acquiring unit 301 is arranged to acquire a current jitter level. The searching unit 302 is arranged to search a correspondence relationship between a jitter level and a font display state according to the current jitter level acquired by the acquiring unit 301, to acquire a font display state corresponding to the current jitter level. The setting unit 303 is arranged to set a default font display state as the font display state corresponding to the current jitter level obtained by the searching unit 302. [0040]In an example, the acquiring unit 301 is arranged to: acquire a first acceleration range absolute value within a preset first time period, and compare the first acceleration range absolute value with a preset acceleration range absolute value threshold; when the first acceleration range absolute value is larger than the acceleration range absolute value threshold, acquire at least two second acceleration range absolute values within a preset second time period; and acquire a third acceleration range absolute value, which is larger than the acceleration range absolute value threshold, from the second acceleration range absolute values; and when the number of the third acceleration range absolute values is not smaller than a preset first number, acquire an average value of the third acceleration range absolute values. [0041]Correspondingly, the searching unit 302 is arranged to search a correspondence relationship between the acceleration range absolute value and the font display state according to the average value, to acquire the font display state corresponding to the average value. [0042]Preferably, the acquiring unit 301 is arranged to: acquire a first original acceleration and a second original acceleration within the first time period; process the first original acceleration and the second original acceleration through a low-pass filter, to acquire a first acceleration median and a second acceleration median respectively; process the first acceleration median and the second acceleration median through a high-pass filter, to acquire a first acceleration and a second acceleration respectively; and perform an absolute value computation on a difference value between a module value of the first acceleration and a module value of the second acceleration, to acquire the first acceleration range absolute value. [0043]In an example, when the current font display state of the mobile terminal 30 is not the default font display state, the acquiring unit 301 is further arranged to: acquire at least two fourth acceleration range absolute values within a third time period; when the number of the forth acceleration range absolute value(s), which is larger than the acceleration range absolute value threshold, among the at least two fourth acceleration range absolute values is not smaller than a second preset number, acquire an updated jitter level. The searching unit 302 is further arranged to search the correspondence relationship between the jitter level and the font display state according to the updated jitter level acquired by the acquiring unit 301, to acquire the font display state corresponding to the updated jitter level of the mobile terminal. The setting unit 303 is further arranged to set the current font display state as the font display state corresponding to the updated jitter level acquired by the searching unit 302. [0044]The disclosure discloses a mobile terminal. A jitter degree of the mobile terminal is acquired and the font state displayed on the mobile terminal screen is set according to the jitter degree. Thus a user can see the content on the mobile terminal screen clearly when external shake exists, and the user asthenopia can be avoided. [0045]Those skilled in the art should understand that the embodiments of the disclosure can be provided as a method, a system or a computer program product. Thus, forms of hardware embodiments, software embodiments or embodiments integrating software and hardware can be adopted in the disclosure. Moreover, a form of the computer program product implemented on one or more computer available storage media (including, but not limited to, a disk memory, an optical memory and the like) containing computer available program codes can be adopted in the disclosure. [0046]The disclosure is described with reference to flowcharts and/or block diagrams of the method, the equipment (system) and the computer program product according to the embodiments of the disclosure. It should be understood that each flow and/or block in the flowcharts and/or the block diagrams and a combination of the flows and/or the blocks in the flowcharts and/or the block diagrams can be realized by computer program instructions. These computer program instructions can be provided for a general computer, a dedicated computer, an embedded processor or processors of other programmable data processing devices to generate a machine, so that an apparatus (in FIG. 4) for realizing functions assigned in one or more flows of the flowcharts and/or one or more blocks of the block diagrams is generated via instructions executed by the computers or the processors of the other programmable data processing devices. [0047]These computer program instructions can also be stored in a computer readable memory capable of guiding the computers or the other programmable data processing devices to work in a specific mode, so that a manufactured product including an instruction apparatus is generated via the instructions stored in the computer readable memory, and the instruction apparatus realizes the functions assigned in one or more flows of the flowcharts and/or one or more blocks of the block diagrams. [0048]These computer program instructions can also be loaded to the computers or the other programmable data processing devices, so that processing realized by the computers is generated by executing a series of operation steps on the computers or the other programmable devices, and therefore the instructions executed on the computers or the other programmable devices provide a step of realizing the functions assigned in one or more flows of the flowcharts and/or one or more blocks of the block diagrams. [0049]Correspondingly, the disclosure further discloses a computer storage medium, wherein a computer program is stored in it and the computer program is used for performing the method for the mobile terminal to set the font display state in embodiment of the disclosure. [0050]The above description is only the preferred embodiments of the disclosure, not intended to limit the scope of protection of the disclosure. INDUSTRIAL APPLICABILITY [0051]Based on each embodiment of the disclosure, by acquiring a jitter degree of a mobile terminal and setting a font state displayed on the mobile terminal screen according to the jitter degree, a user can see the content on the mobile terminal screen clearly when external shake exists, and the user asthenopia can be avoided.(String), 技术领域 [0001] 本发明涉及移动终端领域,尤其涉及一种移动终端、移动终端设置字体显示状态的方法及存储介质。 背景 [0002] 目前,移动终端广泛应用于用户的日常生活中。 在移动终端的使用过程中,例如用户在乘坐公共交通工具时,由于外界抖动,导致用户无法看清终端屏幕上的内容,从而导致用户视疲劳。 概括 [0003] 为解决上述技术问题,本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 [0004] 本发明的技术方案是这样实现的。 [0005] 第一方面,本发明公开了一种移动终端设置字体显示状态的方法,包括:移动终端获取当前抖动等级; 移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态; 移动终端设置默认的字体显示状态作为移动终端当前抖动等级对应的字体显示状态。 [0006] 第二方面,本发明公开了一种移动终端,包括获取单元、搜索单元和设置单元。 获取单元用于获取当前的抖动水平。 查找单元,用于根据当前抖动级别查找抖动级别与字体显示状态的对应关系,获取移动终端当前抖动级别对应的字体显示状态。 设置单元用于设置默认的字体显示状态作为移动终端当前抖动程度对应的字体显示状态。 [0007] 第三方面,本发明公开了一种计算机存储介质,存储有计算机程序,该计算机程序用于执行上述移动终端设置字体显示状态的方法。 [0008] 本发明公开了一种移动终端、移动终端设置字体显示状态的方法及存储介质。 获取移动终端的抖动程度,根据抖动程度设置移动终端屏幕显示的字体状态。 从而在存在外部抖动的情况下,用户可以清晰地看到移动终端屏幕上的内容,避免用户视疲劳。 附图的简要说明 [0009] 图1为移动终端设置字体显示状态的方法流程图; [0010] 图2为移动终端获取当前抖动水平的方法流程图; [0011] 图3是根据本发明实施例的移动终端的结构图; [0012] 图4是根据本发明一个实施例的移动终端的框图; [0013] 图5为根据本发明一实施例的字体大小的方块图。 [0014] 图6是显示根据本公开的实施例的相对于时间段的加速度的表格。 详细说明 [0015] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 [0016] 本发明实施例首先获取移动终端的抖动程度,然后根据抖动程度相应设置移动终端屏幕显示的字体状态。 字体状态可以包括但不限于字体大小、字体类型和字体颜色等。本发明实施例以字体大小(图5)为例进行说明。 可以理解,根据本发明实施例的技术方案还可以设置其他字体状态。 [0017]参见图1,其示出了根据本发明实施例的移动终端设置字体显示状态的方法。 该方法可以用于移动终端。 例如,但不限于,移动终端可以包括但不限于手机、平板电脑或笔记本电脑等便携式终端设备。该方法可以包括以下步骤。 [0018] 在步骤S 101 ,移动终端获取当前的抖动水平。 需要注意的是,当前抖动级别是设置字体显示状态的基础。 只有准确获取抖动水平,才能确定字体显示状态应设置为何种字体状态。 [0019] 例如,如图2所示,移动终端获取当前抖动水平可以包括步骤S 201 -S 204 . [0020] 在步骤S 201 、移动终端在预设的第一时间段内(图6)获取第一加速度范围绝对值,并将第一加速度范围绝对值与预设的加速度范围绝对值阈值进行比较。 重要的是要注意步骤S 201 用于判断抖动是否由外部抖动引起,是获取当前抖动水平的必要条件。 因此,可以通过设置加速度范围绝对值阈值来判断抖动是否由外部抖动引起。 [0021] 或者,移动终端在预设的第一时间段内获取第一加速度范围绝对值可以包括以下步骤。 首先,移动终端通过内置的加速度传感器在预设的第一时间段内检测并获取两个加速度,即第一原始加速度和第二原始加速度。 然后,第一原始加速度和第二原始加速度通过低通滤波器处理,分别获得第一加速度中值和第二加速度中值。 然后,第一加速度中值和第二加速度中值经过高通滤波器处理,分别得到第一加速度和第二加速度。 最后,对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。 [0022] 需要注意的是,预设的第一时间段T 1 为加速度传感器两次检测加速度之间的时间间隔,可以由系统默认设置,也可以由用户设置。 加速度传感器检测获取的第一原始加速度和第二原始加速度可以用三个正交坐标轴上的加速度分量的矢量合成来表示。 [0023] 通常,第一原始加速度和第二原始加速度可能受到重力的干扰。 因此,优选地,在本实施例中,第一原始加速度和第二原始加速度由移动终端通过低通滤波器处理,然后第一加速度中值和第二加速度中值通过高通滤波器处理,以 分别获取第一加速度和第二加速度。 这样,可以消除重力的干扰。 可以理解,第一加速度和第二加速度也可以用三个正交坐标轴上的加速度分量的矢量合成来表示。 在本实施例中,第一加速度的模值可以表示为: a 1 =√{对( x 1 2 +y 1 2 +z 1 2 )} 哪里,一个 1 是第一个加速度的模值,单位为m/s 2 , X 1 是x轴方向第一加速度的分量值,y 1 是y轴方向第一加速度的分量值,z 1 为z轴方向第一加速度的分量值,单位为x 1 , 是 1 和 1 是米/秒 2 . [0024]相应地,二次加速度的模值可以表示为: a 2 =√{对( x 2 2 +y 2 2 +z 2 2 )} 哪里,一个 2 是第二个加速度的模值,单位为m/s 2 ; X 2 是x轴方向第二个加速度的分量值,y 2 为y轴方向二次加速度分量值,z 2 为z轴方向二次加速度的分量值,单位为x 2 , 是 2 和 2 是米/秒 2 . [0025] 优选地,所述第一加速度范围绝对值可以通过以下公式得到: 一=|一个 2 −a 1 | 其中,a为第一加速度范围绝对值,a 1 是第一加速度的模值,a 2 为二次加速度的模值,单位为a,a 1 和一个 2 是米/秒 2 . [0026] 在步骤S 202 ,当第一加速度范围绝对值大于加速度范围绝对值阈值时,移动终端在预设的第二时间段内获取至少两个第二加速度范围绝对值(图6)。 需要说明的是,当第一加速度范围绝对值大于加速度范围绝对值阈值时,可以确定抖动是由外部环境引起的。 随后,需要检测抖动的持续时间。 例如,本实施例中,移动终端在第二时间段T内获取N个第二加速度范围绝对值。 2 ,其中 N≥2。 可以理解,第二加速度范围绝对值的获取方式与S中获取第一加速度范围绝对值的方式相同。 201 ,这里不再赘述。 [0027] 在步骤S 203 ,移动终端从第二加速度范围绝对值中获取大于加速度范围绝对值阈值的第三加速度范围绝对值。 本实施例中,移动终端可以统计N个第二加速度范围绝对值中大于加速度范围绝对值阈值的第二加速度范围绝对值的个数,得到M个第三加速度范围绝对值,M≥1。 [0028] 在步骤S 204 ,当第三加速度范围绝对值的个数不小于预设的第一数量时,移动终端获取第三加速度范围绝对值的平均值。 需要说明的是,在本实施例中,移动终端将M与预设的第一数进行比较,当M小于预设的第一数时,表示抖动是偶发的或者抖动程度不剧烈。 此时,移动端无需调整字体显示状态。 当M不小于预设的第一个数时,说明抖动不是偶然的,而是持续了一定时间,已经影响了用户的阅读。 此时,通过第三加速度范围绝对值的平均值来评估抖动程度,这是对抖动水平的最差估计。 [0029] 或者,对于本领域的技术人员,也可以通过上次获取的第三加速度范围绝对值来评价抖动程度,在此不再赘述。 [0030] 在步骤S 102 ,移动终端根据当前抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端当前抖动等级对应的字体显示状态。 优选地,抖动级别与字体显示状态的对应关系可以用表1所示的映射表来表示,也可以用其他能够表达该对应关系的方法来表示,本实施例对此不作限定: [0031] 表格1 抖动水平 字体显示状态 第一抖动水平 第一个字体显示状态 第二抖动水平 第二字体显示状态 第三抖动等级 第三种字体显示状态 [0032] 在实施例中,从S可以看出201 -S 204 抖动水平由第三加速度范围绝对值的平均值表示。 因此,优选地,第三加速度范围绝对值的平均值可以对应地分为四个部分,与字体显示大小一一对应。 从而得到如表2所示的对应关系: [0033] 表 2 加速度范围绝对值 (单位:米/秒 2 ) 字体显示大小 0-3 普通字体 4-6 中小字体 7-9 中大字体 10-12 大字体 [0034] 在步骤S 103 ,移动终端设置默认的字体显示状态作为移动终端当前抖动等级对应的字体显示状态。 [0035] 需要说明的是,在上述过程结束后,字体显示状态由默认的字体显示状态变为当前抖动级别对应的字体显示状态。 但是,一般情况下,抖动会随着时间的推移而变化,一个抖动级别不会持续很长时间。 为了适应变化,需要根据抖动程度的变化及时调整字体显示状态。 [0036] 优选地,当移动终端当前的字体显示状态不是默认字体显示状态时,该方法还包括: 移动终端在第三时间段内获取至少两个第四加速度范围绝对值; 当至少两个第四加速度范围绝对值中大于加速度范围绝对值阈值的第四加速度范围绝对值的个数不小于第二预设个数时,移动终端获取更新的抖动水平; 移动终端根据更新后的抖动等级查找抖动等级与字体显示状态的对应关系,获取移动终端更新后的抖动等级对应的字体显示状态; 移动终端将当前字体显示状态设置为更新后的移动终端抖动等级对应的字体显示状态。 [0037] 可以理解,移动终端更新后的抖动等级对应的字体显示状态与当前字体显示状态之间的等级差可以跳级。 例如,当前显示的正常字体大小可以设置为中大号字体或大号字体,本发明实施例在此不再赘述。 [0038] 本发明公开了一种移动终端设置字体显示状态的方法。 可以获取移动终端的抖动程度,根据抖动程度设置移动终端屏幕显示的字体状态。 从而在有外界晃动的情况下,用户可以清晰的看到移动终端屏幕上的内容,避免用户视疲劳。 [0039] 基于与上述实施例相同的技术构思,如图3所示,移动终端的结构 30 在本发明实施例中提供。 例如,但不限于,移动终端可以包括但不限于手机、平板电脑或笔记本电脑等便携式终端设备。移动终端 30 可能包括收购单位 301 , 一个搜索单元 302 和一个设置单元 303 . 收单单位 301 被布置为获取当前抖动水平。 搜寻单位 302 用于根据获取单元获取的当前抖动等级查找抖动等级与字体显示状态的对应关系 301 , 获取当前抖动等级对应的字体显示状态。 设定单位 303 设置为设置默认字体显示状态为搜索单元获取的当前抖动级别对应的字体显示状态 302 . [0040] 在一个例子中,获取单元 301用于在预设的第一时间段内获取第一加速度范围绝对值,并将第一加速度范围绝对值与预设的加速度范围绝对值阈值进行比较; 当第一加速度范围绝对值大于加速度范围绝对值阈值时,在预设的第二时间段内获取至少两个第二加速度范围绝对值; 从第二加速度范围绝对值中获取大于加速度范围绝对值阈值的第三加速度范围绝对值。 当第三加速度范围绝对值的数量不小于预设的第一数量时,获取第三加速度范围绝对值的平均值。 [0041] 相应地,搜索单元 302 用于根据平均值查找加速度范围绝对值与字体显示状态的对应关系,获取该平均值对应的字体显示状态。 [0042] 优选地,获取单元 301 用于在第一时间段内获取第一原始加速度和第二原始加速度; 通过低通滤波器处理第一原始加速度和第二原始加速度,分别获得第一加速度中值和第二加速度中值; 通过高通滤波器对第一加速度中值和第二加速度中值进行处理,分别得到第一加速度和第二加速度。 对第一加速度的模值与第二加速度的模值的差值进行绝对值计算,得到第一加速度范围绝对值。 [0043] 示例中,当移动终端当前字体显示状态 30 不是默认字体显示状态,获取单元 301 还用于在第三时间段内获取至少两个第四加速度范围绝对值; 当至少两个第四加速度范围绝对值中大于加速度范围绝对值阈值的第四加速度范围绝对值的个数不小于第二预设个数时,获取更新后的抖动水平。 搜寻单位 302 还用于根据获取单元获取的更新后的抖动等级,查找抖动等级与字体显示状态的对应关系 301 , 获取更新后的移动终端抖动等级对应的字体显示状态。 设定单位 303 还用于将当前字体显示状态设置为搜索单元获取的更新后的抖动等级对应的字体显示状态 302 . [0044] 本发明公开了一种移动终端。 获取移动终端的抖动程度,根据抖动程度设置移动终端屏幕显示的字体状态。 从而在有外界晃动的情况下,用户可以清晰的看到移动终端屏幕上的内容,避免用户视疲劳。 [0045] 本领域的技术人员应该理解,本公开的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本发明可以采用硬件实施例、软件实施例或软硬件结合的实施例的形式。 此外,本发明可采用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光存储器等)上实现计算机可用程序代码的计算机程序产品的形式。 [0046]本发明是参照根据本发明实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述的。 应当理解,流程图和/或框图中的每个流程和/或框以及流程图和/或框图中的流程和/或框的组合可以由计算机程序指令实现。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或其他可编程数据处理设备的处理器生成机器,从而实现一个或多个流程分配的功能的装置(图4) 流程图的一部分和/或框图的一个或多个块经由由计算机或其他可编程数据处理设备的处理器执行的指令生成。 [0047] 这些计算机程序指令也可以存储在能够引导计算机或其他可编程数据处理设备以特定模式工作的计算机可读存储器中,从而通过存储在计算机中的指令生成包括指令装置的制造产品 可读存储器,指令装置实现流程图的一个或多个流程和/或方框图的一个或多个块中指定的功能。 [0048] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备中,使得计算机实现的处理是通过在计算机或其他可编程设备上执行一系列操作步骤而产生的,因此在计算机或其他可编程数据处理设备上执行的指令 计算机或其他可编程设备提供实现在流程图的一个或多个流程和/或框图的一个或多个块中分配的功能的步骤。 [0049] 相应地,本发明还公开了一种计算机存储介质,其中存储有计算机程序,该计算机程序用于执行本发明实施例中移动终端设置字体显示状态的方法。 [0050] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。 工业实用性 [0051] 基于本发明各实施例,通过获取移动终端的抖动程度,并根据抖动程度设置移动终端屏幕显示的字体状态,使得用户在存在外部抖动时,能够清晰的看到移动终端屏幕上的内容。 ,可以避免用户疲劳。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104320534A(String), CN104320534B(String), US10469652B2(String), US20190158651A1(String), WO2015131604A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104320534A(String), CN104320534B(String), US10469652B2(String), US20190158651A1(String), WO2015131604A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104320534A(String), CN104320534B(String), US10469652B2(String), US20190158651A1(String), WO2015131604A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271205(Integer), CN104320534A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271205(Integer), CN104320534B(String), 1048241(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.559 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.559 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271205(Integer), US10469652B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271205(Integer), US20190158651A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271205(Integer), WO2015131604A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104320534B(String), CN104320534B(String), 1520524800(Integer), 271205(Integer), 185489(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.743 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.743 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185948(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185948(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185948(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185948(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:01.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.042 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.043 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.118 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185948(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9455952B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for setting functional module name of mobile terminal, and mobile terminal(String), 一种设置移动终端功能模块名称的方法及移动终端(String), US9455952B2(String), The embodiment of the present document discloses a method for setting functional module names of a mobile terminal, which includes: setting the name of a mobile terminal; according to the set name of the mobile terminal, generating functional module names corresponding to functional modules in the mobile terminal. The embodiment of the present document further discloses a mobile terminal. The solution disclosed in the embodiment of the present document can be used to automatically modify the names of various functional modules in a mobile terminal by setting the name of the mobile terminal, thus reducing the user's operation steps and also improving the user experience.(String), 本发明实施例公开了一种移动终端功能模块名称设置方法,包括:设置移动终端名称; 根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称。 本发明实施例还公开了一种移动终端。 采用本发明实施例公开的方案,可以通过设置移动终端的名称,自动修改移动终端中各个功能模块的名称,从而减少了用户的操作步骤,也提高了用户体验。(String), US14/761949(String), 1372262400(Integer), US9455952B2(String), 1474905600(Integer), 1474905600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 16(Integer), CN102281350A | CN102469453A | EP1838047A2 | US20060276133A1 | US20090181653A1 | US20110019599A1 | US20110117849A1 | US20120164947A1 | US20120315839A1 | US20140120906A1 | US20140129652A1 | US20150373179A1 | US7801485B2 | US8126399B1 | US8626233B2 | WO2007027660A2(String), 8(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185949(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8a7910f81e63429db88c5690940874c9.png(String), 185949(Integer), 8a7910f81e63429db88c5690940874c9.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for setting functional module name of mobile terminal, and mobile terminal(String), 一种设置移动终端功能模块名称的方法及移动终端(String), US9455952B2(String), The embodiment of the present document discloses a method for setting functional module names of a mobile terminal, which includes: setting the name of a mobile terminal; according to the set name of the mobile terminal, generating functional module names corresponding to functional modules in the mobile terminal. The embodiment of the present document further discloses a mobile terminal. The solution disclosed in the embodiment of the present document can be used to automatically modify the names of various functional modules in a mobile terminal by setting the name of the mobile terminal, thus reducing the user's operation steps and also improving the user experience.(String), 本发明实施例公开了一种移动终端功能模块名称设置方法,包括:设置移动终端名称; 根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称。 本发明实施例还公开了一种移动终端。 采用本发明实施例公开的方案,可以通过设置移动终端的名称,自动修改移动终端中各个功能模块的名称,从而减少了用户的操作步骤,也提高了用户体验。(String), US14/761949(String), 1372262400(Integer), US9455952B2(String), 1474905600(Integer), 1474905600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 16(Integer), CN102281350A | CN102469453A | EP1838047A2 | US20060276133A1 | US20090181653A1 | US20110019599A1 | US20110117849A1 | US20120164947A1 | US20120315839A1 | US20140120906A1 | US20140129652A1 | US20150373179A1 | US7801485B2 | US8126399B1 | US8626233B2 | WO2007027660A2(String), \20230420\8a7910f81e63429db88c5690940874c9.png(String), 8(Integer), 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 1. A method for setting functional module names of a mobile terminal, the method comprising:setting a name of the mobile terminal;according to the name of the mobile terminal, generating functional module names corresponding to various functional modules in the mobile terminal;displaying the functional module names;prompting a user to confirm the functional module names; andaccording to a current state of each functional module, saving the corresponding functional module name of each functional module, wherein the current state comprises a non-startup state, a turned-off state and a turned-on state.(String), 1.一种设置移动终端功能模块名称的方法,该方法包括:设置移动终端名称;根据移动终端的名称,生成移动终端中各个功能模块对应的功能模块名称;显示功能模块名称;提示用户确认功能模块名称;和根据每个功能模块的当前状态,保存每个功能模块对应的功能模块名称,其中,当前状态包括未启动状态、关闭状态和开启状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 2. The method of claim 1, wherein said according to a current state of each functional module, saving the corresponding functional module name of each functional module comprises:when the current state of the functional module is the non-startup state, saving the functional module name corresponding to the functional module into a database;when the current state of the functional module is the turned-off state, saving the functional module name corresponding to the functional module into a configuration file of the functional module;when the current state of the functional module is the turned-on state, replacing and saving the functional module name corresponding to the functional module into the configuration file of the functional module.(String), 2.如权利要求1所述的方法,其中所述根据各功能模块的当前状态,保存各功能模块对应的功能模块名称包括:当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中;当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中;当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换保存到功能模块的配置文件中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 3. The method of claim 1, wherein before executing said generating functional module names corresponding to various functional modules in the mobile terminal according to the set name of the mobile terminal, the method further comprises:judging a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 3.如权利要求1所述的方法,其中在执行所述根据设置的移动终端名称生成移动终端中各个功能模块对应的功能模块名称之前,该方法还包括:判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 4. The method of claim 2, wherein before executing said generating functional module names corresponding to various functional modules in the mobile terminal according to the set name of the mobile terminal, the method further comprises:judging a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 4.如权利要求2所述的方法,其中在执行所述根据设置的移动终端名称生成移动终端中各个功能模块对应的功能模块名称之前,该方法还包括:判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 5. A mobile terminal, comprising a processor and a storage device, wherein the storage device stores processor-executable programs with following modules:a setting module, configured to: set a name of a mobile terminal; anda name generating module, configured to: according to the name of the mobile terminal, generate functional module names corresponding to various functional modules in the mobile terminal;a displaying module, configured to: display the functional module names;a prompting module, configured to: prompt a user to confirm the functional module names; anda saving module, configured to: according to a current state of each functional module, save the corresponding functional module name of each functional module, wherein the current state comprises a non-startup state, a turned-off state and a turned-on state.(String), 5.移动终端,包括处理器和存储设备,其中存储设备存储具有以下模块的处理器可执行程序:设置模块,用于设置移动终端的名称;和名称生成模块,用于根据移动终端的名称,生成移动终端中各个功能模块对应的功能模块名称;显示模块,用于显示功能模块名称;提示模块,用于提示用户确认功能模块名称;和保存模块,用于根据各功能模块的当前状态,保存各功能模块对应的功能模块名称,其中,当前状态包括非开机状态、关机状态和开机状态.6.如权利要求5所述的移动终端,其中保存模块配置为:当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中;当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中;当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换并保存到功能模块的配置文件中。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 6. The mobile terminal of claim 5, wherein the saving module is configured to:when the current state of the functional module is the non-startup state, save the functional module name corresponding to the functional module into a database;when the current state of the functional module is the turned-off state, save the functional module name corresponding to the functional module into a configuration file of the functional module;when the current state of the functional module is the turned-on state, replace and save the functional module name corresponding to the functional module into the configuration file of the functional module.(String), 7.如权利要求5所述的移动终端,还包括:判断模块,用于判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 7. The mobile terminal of claim 5, further comprising:a judging module, configured to: judge a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 8.如权利要求6所述的移动终端,还包括:判断模块,用于判断移动终端支持功能模块的情况;其中,所述功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:02.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185949(Integer), 8. The mobile terminal of claim 6, further comprising:a judging module, configured to: judge a condition of the mobile terminal supporting the functional modules; wherein the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.141 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.141 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185949(Integer), TECHNICAL FIELD [0001]The present document relates to the field of mobile communication technologies, and more particularly, to a method for setting functional module names of a mobile terminal and the mobile terminal. BACKGROUND OF THE RELATED ART [0002]Currently, technologies such as Bluetooth, portable wireless fidelity (WIFI) hot spots, WIFI Direct have been more widely used in high-end mobile terminals, and the Bluetooth and the portable WIFI hotspot have already been common features. Through the Bluetooth, users can easily exchange and share information with various types of equipment; through the portable WIFI hotspot, users can share the mobile network of the mobile terminal with other equipment, and through the WIFI Direct, the users can conveniently achieve directly connecting, transferring data, or sharing applications with other equipment. [0003]However, because currently the mobile terminals usually identify Bluetooth devices with default device names, and use a default value or a random value to identify WIFI hot spots and WIFI Direct devices, and no matter whether to uniformly use an identification or randomly generate an identification, it causes disorder for the user to distinguish, because when a user uses the abovementioned function, usually the user is just for one person, and then connects to his device, but rarely knows what the device name of the other party is. In order to identify the user's device, the current practice is that, in modules such as Bluetooth, portable WIFI hotspot, WIFI Direct, the user can individually modify the name of each module. However, the operation of this method has some complexity and limitations. SUMMARY OF THE INVENTION [0004]The embodiment of the present document provides a method for setting functional module names of a mobile terminal and the mobile terminal, and it is designed to automatically modify the names of various functional modules in a mobile terminal to reduce the user's operation steps and enhance the user experience. [0005]The present document provides a method for setting functional module names of a mobile terminal, comprising: [0006]setting the name of a mobile terminal; [0007]according to the set name of the mobile terminal, generating functional module names corresponding to functional modules in the mobile terminal. [0008]Preferably, after executing said generating the functional module names corresponding to the functional modules in the mobile terminal, it further comprises: [0009]displaying the functional module names. [0010]Preferably, after executing said displaying the functional module names, it further comprises: [0011]prompting a user to confirm the functional module names. [0012]Preferably, after executing said prompting the user to confirm the functional module names, it further comprises: [0013]according to the current states of the functional modules, saving the functional module names; the current states of the functional modules comprise non-startup state, turned-off state and turned-on state. [0014]Preferably, said saving the functional module names according to the current states of the functional modules comprises: [0015]when the current state of the functional module is the non-startup state, saving the functional module name corresponding to the functional module into a database; [0016]when the current state of the functional module is the turned-off state, saving the functional module name corresponding to the functional module into a configuration file of the functional module; [0017]when the current state of the functional module is the turned-on state, replacing and saving the functional module name corresponding to the functional module into the configuration file of the functional module. [0018]Preferably, before executing said generating functional module names corresponding to various functional modules in the mobile terminal in accordance with the set name of the mobile terminal, it further comprises: [0019]judging the condition of the mobile terminal supporting the functional modules; the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0020]The embodiment of the present document further provides a mobile terminal, comprising: [0021]a setting module, configured to: set the name of a mobile terminal; [0022]a name generating module, configured to: according to the set name of the mobile terminal, generate functional module names corresponding to functional modules in the mobile terminal. [0023]Preferably, the mobile terminal further comprises: [0024]a displaying module, which is configured to: display the functional module names. [0025]Preferably, the mobile terminal further comprises: [0026]a prompting module, configured to: prompt a user to confirm the functional module names. [0027]Preferably, the mobile terminal further comprises: [0028]a saving module, which is configured to: according to the current states of the functional modules, save the functional module names; the current states of the functional modules comprise a non-startup state, a turned-off state and a turned-on state. [0029]Preferably, the saving module is configured to: [0030]when the current state of the functional module is the non-startup state, save the functional module name corresponding to the functional module into a database; [0031]when the current state of the functional module is the turned-off state, save the functional module name corresponding to the functional module into a configuration file of the functional module; [0032]when the current state of the functional module is the turned-on state, replace and save the functional module name corresponding to the functional module into the configuration file of the functional module. [0033]Preferably, the mobile terminal further comprises: [0034]a judging module, configured to: judge the condition of the mobile terminal supporting the functional modules; the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0035]In the embodiment of the present document, it sets the name of a mobile terminal and then generates functional module names corresponding to functional modules in the mobile terminal according to the set name of the mobile terminal. By setting the name of the mobile terminal, the names of various functional modules in the mobile terminal can be automatically modified, thus reducing the user's operation steps and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a flow chart of a first embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0037]FIG. 2 is a flow chart of a second embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0038]FIG. 3 is a flow chart of a third embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0039]FIG. 4 is a flow chart of a fourth embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document; [0040]FIG. 5 is a flow chart of saving the functional module names in the method for setting functional module names of a mobile terminal in accordance with the present document; [0041]FIG. 6 is a flow chart of a fifth embodiment of the method for setting the functional module names of a mobile terminal in accordance with the present document; [0042]FIG. 7 is a schematic diagram of the structure of a first embodiment of a mobile terminal in accordance with the present document; [0043]FIG. 8 is a schematic diagram of the structure of a second embodiment of the mobile terminal in accordance with the present document; [0044]FIG. 9 is a schematic diagram of the structure of a third embodiment of the mobile terminal in accordance with the present document; [0045]FIG. 10 is a schematic diagram of the structure of a fourth embodiment of the mobile terminal in accordance with the present document; [0046]FIG. 11 is a schematic diagram of the structure of a fifth embodiment of the mobile terminal in accordance with the present document. [0047]Object implementations, functions and features and advantages of the present document will be further described in conjunction with the embodiments and with reference to the accompanying drawings. PREFERRED EMBODIMENTS OF THE INVENTION [0048]It should be understood that the specific embodiments described herein are only for explaining the present document and are not intended to limit the present document. In the case of no conflict, embodiments and features in the embodiments of the present application can be combined with each other. [0049]The embodiment of the present document provides a method for setting functional module names of a mobile terminal, which automatically generates corresponding functional module names for various functional modules supported by the mobile terminal by setting the name of the mobile terminal, and displays the functional module names to the user for the user to confirm whether to save the names or not, and the user can also modify the functional module names by himself/herself. [0050]Referring to FIG. 1FIG. 1 is a flow chart of a first embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0051]The method for setting functional module names of a mobile terminal provided in the present embodiment comprises: [0052]in step S10, it is to set the name of a mobile terminal; [0053]In the present embodiment, an entry can be added in the setting module of the mobile terminal for a user to enter the name of the mobile terminal, and the user can set the name of the mobile terminal through the entry. Before setting the functional module names corresponding to various functional modules in the mobile terminal, the name of the mobile terminal is first set. The name of the mobile terminal can be set by the user by himself/herself, which can play a role of identifying the user's mobile terminal device, and in the present embodiment, in order to ensure that it has a different name from the ones that other surrounding mobile terminals have, preferably the user's full name is used as the name of mobile terminal. [0054]In step S20, according to the set name of the mobile terminal, it is to generate a functional module name corresponding to the functional module in the mobile terminal; [0055]after the name of the mobile terminal is set, functional module names corresponding to various functional modules are automatically generated according to the functional modules supported by the mobile terminal as well as the name of the mobile terminal. In the present embodiment, a functional module name can be the set name of the mobile terminal plus the function name of the functional module. [0056]In the embodiment of the present document, it sets the name of a mobile terminal and then generates functional module names corresponding to functional modules in the mobile terminal according to the set name of the mobile terminal. By setting the name of the mobile terminal, the names of various functional modules in the mobile terminal can be automatically modified, thus reducing the user's operation steps and improving the user experience. [0057]Refer to FIG. 2, and FIG. 2 is a flow chart of a second embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0058]Based on the abovementioned embodiment, after executing the step S20, the method further comprises: [0059]in step S30, it is to display the functional module names. [0060]After functional module names corresponding to various functional modules are automatically generated according to the name of the mobile terminal, the generated functional module names are displayed to the user through an interface, and in the present embodiment, the respective functional modules and the corresponding functional module names can be listed in the interface of the mobile terminal. [0061]After functional module names corresponding to various functional modules are automatically generated according to the set name of the mobile terminal, the generated functional module names are displayed to the user, so as to provide a foundation for the user to confirm the functional module names. [0062]Refer to FIG. 3, and FIG. 3 is a flow chart of a third embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0063]Based on the abovementioned embodiment, after performing the step S30, the method further comprises: [0064]in step S40, it is to prompt the user to confirm the functional module names. [0065]The generated functional module names are displayed in the interface of the mobile terminal, meanwhile, a confirmation button is set for the user to confirm the functional module names corresponding to various functional modules, prompting the user to perform confirming. In this case, if the user accepts the automatically generated functional module names, then the user clicks the confirmation; and if the user does not accept them, then the user can make modifications by himself/herself and click the confirmation after modifications, thus completing the setting of names of functional modules of the mobile terminal. [0066]The generated functional module names are displayed, and the user is prompted to confirm the functional module names displayed in the interface, thus ensuring that the names of various functional modules of the mobile terminal can be automatically modified by setting the name of the mobile terminal. [0067]Refer to FIG. 4, and FIG. 4 is a flow chart of a fourth embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0068]Based on the abovementioned embodiment, after performing the step S40, the method further comprises: [0069]in step S50, it is to save the functional module names according to the current states of the functional modules; the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state. [0070]After the user accepts the displayed and automatically generated functional module names and clicks the confirmation, or after the user modifies the functional module names by himself/herself and clicks the confirmation, at this time, it is to judge the current states of the functional modules, and according to the difference of the current states, perform different savings on the functional module names. In this embodiment, the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state, wherein the non-startup state refers to that the functional module of the mobile terminal has never been started up in these circumstances that it was out of the factory, or restored with the factory settings, or upgraded; the turned-off state refers to that the functional module was started up but it is currently in the turned-off state; and the turned-on state refers to that the functional module is currently in the turned-on state. [0071]After the user confirms the automatically generated functional module names or the user modifies the functional module names by himself/herself, according to the current states of the functional modules, the functional module names are saved, to facilitate finding and using the functional module names when starting up the functional modules next time, which provides a premise guarantee for reducing the user's operation steps. [0072]Refer to FIG. 5, and FIG. 5 is a flow chart of saving the functional module names in the method for setting functional module names of a mobile terminal in accordance with the present document. [0073]Based on the abovementioned embodiment, in step S50, when the current state of a functional module is the non-startup state, proceed to step S51; when the current state of a functional module is the turned-off state, proceed to step S52; when the current state of a functional module is the turned-on state, proceed to step S53. [0074]In step S51, it is to save the functional module name corresponding to the functional module into the database; [0075]when determining that the current state of a functional module is the non-startup state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has not been generated, then the functional module name is stored in the database of the mobile terminal. In this embodiment, a record is generated according to the functional module name, and the record takes the functional module as the key and the functional module name as the value, and the record is saved in the database. After the functional module is started up, the database is searched to judge whether there is a record which takes the functional module as the key and the functional module name as the value therein, and if yes, the functional module name in the record is displayed and written into the configuration file of the functional module, then the value is cleared, and when the functional module is turned on next time, the value in the database will not be used again, but the configuration file is directly searched and the value therein is used. [0076]In step S52, it is to save the functional module name corresponding to a functional module into the configuration file of the functional module; [0077]when determining that the current state of a functional module is the turned-off state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has been generated, and at this time, it is to directly save the functional module name into the configuration file. [0078]In step S53, it is to replace and save the functional module name corresponding to the functional module into the configuration file of the functional module. [0079]When determining that the current state of a functional module is the turned-on state, because various functional modules in the mobile terminal have corresponding processing procedures of changing names, when the current state of a functional module is the turned-on state, it is to first trigger the processing procedure of changing names of the functional module, and replace the name previously stored in the configuration file with the currently generated functional module name and save the currently generated functional module name in the configuration file. [0080]When the current state of a functional module is the non-startup state, the turned-off state or the turned-on state, it is to respectively save the functional module name corresponding to the functional module into the database, or into the configuration file, or replace and save it into the configuration file, which ensures to reduce the user's operation steps and enhance the user experience. [0081]Refer to FIG. 6, and FIG. 6 is a flow chart of a fifth embodiment of the method for setting functional module names of a mobile terminal in accordance with the present document. [0082]Based on the first embodiment of the method for setting the functional module name of a mobile terminal in the present document, before performing the step S20, it further comprises: [0083]in step S60, it is to judge the condition of the mobile terminal supporting the functional modules; and the functional modules comprise at least a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0084]Before generating functional module names corresponding to the functional modules according to the set name of the mobile terminal, it is to first judge the functional modules supported by the mobile terminal, that is, judge which functional modules are supported by the mobile terminal. In this embodiment, the functional modules comprise a Bluetooth module, a WIFI hotspot module, a WIFI Direct module and other modules, and when the mobile terminal communicates with other mobile terminals through these modules, it needs to provide a name which can be identified by the other party. [0085]After setting the name of mobile terminal, it needs to, before generating functional module names corresponding to various functional modules of the mobile terminal according to the name, first judge which functional modules are supported by the mobile terminal, so as to generate functional module names of these functional modules, thus providing the foundation for automatically modifying the names of various functional modules of the mobile terminal according to the name of the mobile terminal. [0086]Refer to FIG. 7, and FIG. 7 is a schematic diagram of the structure of a first embodiment of the mobile terminal in accordance with the present document. [0087]The mobile terminal provided in the present embodiment comprises: [0088]a setting module 10, which is configured to: set the name of the mobile terminal; [0089]a name generating module 20, configured to: according to the set name of the mobile terminal, generate functional module names corresponding to the functional modules in the mobile terminal; [0090]In the present embodiment, an entry can be added in the setting module of the mobile terminal for the user to enter the name of the mobile terminal, and the user can set the name of the mobile terminal through the entry. Before setting functional module names corresponding to various functional modules in the mobile terminal, the name of the mobile terminal is firstly set through the setting module 10. The name of the mobile terminal is set by the user by himself/herself, which can play a role of identifying the user's mobile terminal device, and in this embodiment, in order to ensure that the name is different from the ones that other surrounding mobile terminals have, preferably the user's full name is used as the name of the mobile terminal. [0091]After setting the name of the mobile terminal, the name generating module 20 automatically generates functional module names corresponding to various functional modules according to the functional modules supported by the mobile terminal as well as the name of the mobile terminal. In the present embodiment, a functional module name can be set as the name of the mobile terminal plus the function name of the functional module. [0092]In the embodiment of the present document, it sets the name of a mobile terminal and then generates functional module names corresponding to functional modules in the mobile terminal according to the set name of the mobile terminal. By setting the name of the mobile terminal, the names of various functional modules in the mobile terminal can be automatically modified, thus reducing the user's operation steps and improving the user experience. [0093]Refer to FIG. 8, and FIG. 8 is a schematic diagram of the structure of a second embodiment of the mobile terminal in accordance with the present document. [0094]Based on the abovementioned embodiment, the mobile terminal further comprises: [0095]a displaying module 30, configured to: display the functional module names. [0096]After functional module names corresponding to various functional modules according to the name of the mobile terminal are automatically generated, the displaying module 30 displays the generated functional module names to the user through the interface, and in this embodiment, various functional modules and the corresponding functional module names may be listed in the interface of the mobile terminal. [0097]After the functional module names corresponding to various functional modules according to the set name of the mobile terminal are automatically generated, the generated functional module names are displayed to the user, so as to provide the foundation for the user to confirm the functional module names. [0098]Refer to FIG. 9, and FIG. 9 is a schematic diagram of the structure of a third embodiment of the mobile terminal in accordance with the present document. [0099]Based on the abovementioned embodiment, the mobile terminal further comprises: [0100]a prompting module 40, configured to: prompt the user to confirm the functional module names. [0101]the generated functional module names are displayed in the interface of the mobile terminal, meanwhile the prompting module 40 is provided with a confirmation button for the user to confirm the functional module names corresponding to various functional modules, prompting the user to perform confirming. In this case, if the user accepts the automatically generated functional module names, then the user clicks the confirmation; and if the user does not accept the names, the user can make modifications by himself/herself and then click the confirmation after the modification, so as to complete the setting of names of the functional modules of the mobile terminal. [0102]Displaying the generated functional module names and prompting the user to confirm the functional module names displayed in the interface can further ensure that the names of various functional modules of the mobile terminal can be automatically modified by setting the name of the mobile terminal. [0103]Refer to FIG. 10, and FIG. 10 is a schematic diagram of the structure of a fourth embodiment of the mobile terminal in accordance with the present document. [0104]Based on the abovementioned embodiment, the mobile terminal further comprises: [0105]a saving module 50, which is configured to: according to the current states of the functional modules, save the functional module names; the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state. [0106]After the user accepts the displayed and automatically generated functional module names and clicks the confirmation, or after the user modifies the functional module names by himself/herself and clicks the confirmation, at this time, the saving module 50 judges the current states of the functional modules, and perform different savings on the functional module names according to the difference of the current states. In this embodiment, the current states of the functional modules comprise the non-startup state, the turned-off state and the turned-on state, wherein the non-startup state refers to that the functional module of the mobile terminal has never been started up in these circumstances that it was out of the factory, or restored with the factory settings, or upgraded; the turned-off state refers to that the functional module was started up but it is currently in the turned-off state; and the turned-on state refers to that the functional module is currently in the turned-on state. [0107]After the user confirms the automatically generated functional module names, or the user modifies the functional module names by himself/herself, the functional module names are saved according to the current states of the functional modules, so as to facilitate finding and using the functional module names when starting up the functional modules next time, which provides a premise guarantee for reducing the user's operation steps. [0108]In the abovementioned embodiment, the saving module 50 is configured to: [0109]when the current state of a functional module is the non-startup state, save the functional module name corresponding to the functional module into a database; [0110]when the current state of a functional module is the turned-off state, save the functional module name corresponding to the functional module into a configuration file of the functional module; [0111]when the current state of a functional module is the turned-on state, replace and save the functional module name corresponding to the functional module into the configuration file of the functional module. [0112]when determining that the current state of a functional module is the non-startup state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has not been generated, at this time, the functional module name is stored in the database of the mobile terminal. In this embodiment, a record is generated according to the functional module name, and the record takes the functional module as the key and the functional module name as the value, and the record is saved in the database. When the functional module is started up, it is to search in the database to judge whether there is a record which takes the functional module as the key and the functional module name as the value therein, and if yes, display the functional module name in the record and write it into the configuration file of the functional module, and then clear the value, and when the functional module is started up next time, the value in the database will not be used again, and the configuration file is directly searched and the value therein is used. [0113]When determining that the current state of a functional module is the turned-off state, it indicates that the configuration file, which is used to store the functional module name, of the functional module has been generated, at this time, it is to directly save the functional module name in the configuration file. [0114]When determining that the current state of a functional module is the turned-on state, because various functional module in the mobile terminal has corresponding processing procedures of changing names, when the current state of the functional module is the turned-on state, it is to first trigger the processing procedures of changing names of the functional module, and replace the name previously stored in the configuration file with the currently generated functional module name and save the currently generated functional module name in the configuration file. [0115]When the current state of the functional module is the non-startup state, the turned-off state or the turned-on state, it is to respectively save the functional module name corresponding to the functional module into the database, or into the configuration file, or replace and save it in the configuration file, which ensures to reduce the user's operation steps and enhance the user experience. [0116]Refer to FIG. 11, and FIG. 11 is a schematic diagram of the structure of a fifth embodiment of the mobile terminal in accordance with the present document. [0117]Based on the abovementioned embodiment, the mobile terminal further comprises: [0118]a judging module 60, configured to: judge the condition of the mobile terminal supporting the mobile modules; the functional modules at least comprise a Bluetooth module, a WIFI hotspot module and a WIFI Direct module. [0119]Before generating a functional module name corresponding to a functional module according to the set name of the mobile terminal, the functional modules supported by the mobile terminal are firstly judged through the judging module 40, that is, it judges which functional modules are supported by the mobile terminal. In this embodiment, the functional modules comprise a Bluetooth module, a WIFI hotspot module, a WIFI Direct module and other modules, and when the mobile terminal communicates with other mobile terminals through these modules, it needs to provide a name which can be identified by the other party. [0120]After setting the name of mobile terminal, it needs to, before generating functional module names corresponding to various functional modules of the mobile terminal according to the name, first judge which functional modules are supported by the mobile terminal, so as to generate functional module names of these functional modules, thus providing the foundation for automatically modifying the names of various functional modules of the mobile terminal according to the name of the mobile terminal. [0121]In another embodiment, it further provides a kind of software which is used to perform the technical solution described in the abovementioned embodiments and the preferred embodiments. [0122]In another embodiment, it further provides a storage medium, and the storage medium stores the above software, and the storage medium includes, but is not limited to: compact disc, floppy disk, hard disk, flash memory or the like. [0123]Obviously, a person skilled in the art should understand that the respective modules or steps in the embodiments of the present document can be implemented with general-purpose computing devices, and they can be concentrat(String), 技术领域 [0001] 本发明涉及移动通信技术领域,尤其涉及一种移动终端功能模块名称的设置方法及移动终端。 相关技术背景 [0002] 目前,蓝牙、便携式WIFI热点、WIFI Direct等技术在高端移动终端中的应用越来越广泛,蓝牙和便携式WIFI热点已经成为普遍特征。 通过蓝牙,用户可以方便地与各类设备进行信息交换和共享; 通过随身WIFI热点,用户可以与其他设备共享移动终端的移动网络,通过WIFI Direct,用户可以方便地实现与其他设备的直接连接、传输数据或共享应用。 [0003] 但是,由于目前移动终端通常使用默认设备名称来识别蓝牙设备,使用默认值或随机值来识别WIFI热点和WIFI直连设备,无论是统一使用标识还是随机生成标识, 造成用户辨别混乱,因为当用户使用上述功能时,通常用户只是针对一个人,然后连接到他的设备,而很少知道对方的设备名称是什么。 为了识别用户的设备,目前的做法是,在蓝牙、便携式WIFI热点、WIFI Direct等模块中,用户可以单独修改每个模块的名称。 然而,这种方法的操作具有一定的复杂性和局限性。 发明内容 [0004] 本发明实施例提供一种移动终端功能模块名称的设置方法及移动终端,旨在自动修改移动终端中各功能模块的名称,以减少用户的操作步骤,提高用户使用体验。 经验。 [0005] 本发明提供了一种移动终端功能模块名称的设置方法,包括: [0006] 设置移动终端名称; [0007] 根据设置的移动终端名称,生成移动终端中功能模块对应的功能模块名称。 [0008] 优选地,在执行所述生成移动终端中的功能模块对应的功能模块名称之后,还包括: [0009] 显示功能模块名称。 [0010] 优选地,在执行所述显示功能模块名称之后,还包括: [0011] 提示用户确认功能模块名称。 [0012] 优选地,在执行所述提示用户确认功能模块名称之后,还包括: [0013] 根据功能模块的当前状态,保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0014] 优选地,所述根据功能模块的当前状态保存功能模块名称包括: [0015] 当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中; [0016] 当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0017] 当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换保存到功能模块的配置文件中。 [0018] 优选地,在执行所述根据设置的移动终端名称生成移动终端中各功能模块对应的功能模块名称之前,还包括: [0019]判断移动终端支持功能模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0020] 本发明实施例还提供一种移动终端,包括: [0021] 设置模块,用于设置移动终端的名称; [0022] 名称生成模块,用于根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称。 [0023] 优选地,所述移动终端还包括: [0024] 显示模块,用于显示功能模块名称。 [0025] 优选地,所述移动终端还包括: [0026] 提示模块,用于提示用户确认功能模块名称。 [0027] 优选地,所述移动终端还包括: [0028] 保存模块,用于根据功能模块的当前状态,保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0029] 优选地,所述保存模块用于: [0030] 当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中; [0031] 当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0032] 当功能模块的当前状态为开机状态时,将功能模块对应的功能模块名称替换并保存到功能模块的配置文件中。 [0033] 优选地,所述移动终端还包括: [0034] 判断模块,用于判断移动终端支持该功能模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0035] 在本发明实施例中,设置移动终端的名称,然后根据设置的移动终端名称生成移动终端中的功能模块对应的功能模块名称。 通过设置移动终端的名称,可以自动修改移动终端中各个功能模块的名称,减少了用户的操作步骤,提高了用户体验。 附图的简要说明 [0036] 图1为本发明移动终端功能模块名称设置方法第一实施例的流程图; [0037] 图2为本发明移动终端功能模块名称设置方法第二实施例的流程图; [0038] 图3为本发明移动终端功能模块名称设置方法第三实施例的流程图; [0039] 图4为本发明移动终端功能模块名称设置方法第四实施例的流程图。 [0040] 图5为本发明移动终端功能模块名称设置方法中保存功能模块名称的流程图; [0041] 图6为本发明移动终端功能模块名称设置方法第五实施例的流程图; [0042] 图7为本发明移动终端第一实施例的结构示意图; [0043] 图8为本发明移动终端第二实施例的结构示意图; [0044] 图9为本发明移动终端第三实施例的结构示意图; [0045]图10为本发明移动终端第四实施例的结构示意图; [0046] 图11为本发明移动终端第五实施例的结构示意图。 [0047] 本发明目的的实现、功能特点和优点将结合实施例并参照附图进行进一步说明。 本发明的优选实施例 [0048] 应当理解,此处所描述的具体实施例仅仅用于解释本发明,并不用于限制本发明。 在不冲突的情况下,本申请实施例中的实施例及特征可以相互组合。 [0049] 本发明实施例提供了一种设置移动终端功能模块名称的方法,通过设置移动终端的名称,自动为移动终端支持的各种功能模块生成对应的功能模块名称,并显示功能模块名称。 供用户确认是否保存名称,用户也可以自行修改功能模块名称。 [0050] 参见图1图1为本发明移动终端功能模块名称设置方法第一实施例的流程图。 [0051] 本实施例提供的设置移动终端功能模块名称的方法包括: [0052] 在步骤S 10 , 设置移动终端名称; [0053] 本实施例中,可以在移动终端的设置模块中增加一个入口,供用户输入移动终端的名称,用户可以通过该入口设置移动终端的名称。 在设置移动终端中各个功能模块对应的功能模块名称之前,首先设置移动终端的名称。 移动终端的名称可以由用户自己设置,可以起到识别用户移动终端设备的作用,本实施例中,为了保证其与实际使用的名称不同 其他周边移动终端有,优选使用用户的全名作为移动终端的名称。 [0054] 在步骤S 20 、根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称; [0055] 设置移动终端的名称后,根据移动终端支持的功能模块以及移动终端的名称,自动生成各个功能模块对应的功能模块名称。 在本实施例中,功能模块名称可以为移动终端的设置名称加上功能模块的功能名称。 [0056] 在本发明实施例中,设置移动终端的名称,然后根据设置的移动终端名称生成移动终端中的功能模块对应的功能模块名称。 通过设置移动终端的名称,可以自动修改移动终端中各个功能模块的名称,减少了用户的操作步骤,提高了用户体验。 [0057] 参见图2,图2为本发明移动终端功能模块名称设置方法第二实施例的流程图。 [0058] 基于上述实施例,执行步骤S后 20 ,该方法还包括: [0059] 在步骤S 30 , 显示功能模块名称。 [0060]根据移动终端的名称自动生成各个功能模块对应的功能模块名称后,将生成的功能模块名称通过界面显示给用户,本实施例中,各个功能模块和对应的功能模块 名称可以列在移动终端的界面中。 [0061] 根据设置的移动终端名称自动生成各个功能模块对应的功能模块名称后,将生成的功能模块名称显示给用户,为用户确认功能模块名称提供依据。 [0062] 参见图3,图3为本发明移动终端功能模块名称设置方法第三实施例的流程图。 [0063] 基于上述实施例,在执行完步骤S后 30 ,该方法还包括: [0064] 在步骤S 40 , 提示用户确认功能模块名称。 [0065] 将生成的功能模块名称显示在移动终端的界面中,同时设置确认按钮供用户确认各个功能模块对应的功能模块名称,提示用户进行确认。 在这种情况下,如果用户接受自动生成的功能模块名称,则用户点击确认; 如果用户不接受,则用户可以自行修改,修改后点击确认,从而完成移动终端功能模块名称的设置。 [0066] 显示生成的功能模块名称,并提示用户确认界面显示的功能模块名称,从而保证移动终端的各个功能模块的名称可以通过设置移动终端的名称自动修改。 [0067] 参见图4,图4为本发明移动终端功能模块名称设置方法第四实施例的流程图。 [0068] 基于上述实施例,在执行完步骤S后 40 ,该方法还包括: [0069] 在步骤S 50 ,根据功能模块的当前状态保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0070] 用户接受显示的自动生成的功能模块名称并点击确认后,或者用户自行修改功能模块名称并点击确认后,此时判断功能模块的当前状态 ,并根据当前状态的不同,对功能模块名称进行不同的保存。 在本实施例中,功能模块的当前状态包括非启动状态、关机状态和开机状态,其中,非启动状态是指移动终端的功能模块从未启动过 在这些情况下,它是出厂的,或者恢复出厂设置,或者升级; 关闭状态是指功能模块已经启动,但当前处于关闭状态。 开启状态是指功能模块当前处于开启状态。 [0071] 用户确认自动生成的功能模块名称或用户自行修改功能模块名称后,根据功能模块的当前状态,保存功能模块名称,方便用户在使用时查找和使用功能模块名称。 下次启动功能模块,为减少用户的操作步骤提供了前提保证。 [0072] 参见图5,图5为本发明移动终端功能模块名称设置方法中保存功能模块名称的流程图。 [0073]基于上述实施例,在步骤S中 50 , 当功能模块当前状态为非启动状态时,转步骤S 51 ; 当功能模块当前状态为关闭状态时,转步骤S 52 ; 当功能模块当前状态为开启状态时,转步骤S 53 . [0074] 在步骤S 51 ,就是将功能模块对应的功能模块名称存入数据库; [0075] 当判断功能模块的当前状态为非启动状态时,说明还没有生成该功能模块的用于存储功能模块名称的配置文件,则存储功能模块名称 在移动终端的数据库中。 在本实施例中,根据功能模块名称生成一条记录,该记录以功能模块为键,功能模块名称为值,保存在数据库中。 功能模块启动后,查找数据库,判断其中是否存在以功能模块为key,功能模块名称为value的记录,如果有,则显示记录中的功能模块名称 并写入功能模块的配置文件,然后清空该值,下次开启该功能模块时,不再使用数据库中的值,而是直接查找配置文件,将其中的值 用来。 [0076] 在步骤S 52 ,将一个功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0077] 当判断功能模块的当前状态为关闭状态时,表示该功能模块的用于存储功能模块名称的配置文件已经生成,此时, 直接将功能模块名称保存到配置文件中。 [0078] 在步骤S 53 ,就是将功能模块对应的功能模块名替换保存到功能模块的配置文件中。 [0079] 当确定功能模块的当前状态为开机状态时,由于移动终端中的各个功能模块都有相应的更名处理过程,当功能模块的当前状态为开机状态时, 首先触发更改功能模块名称的处理流程,将配置文件中先前保存的名称替换为当前生成的功能模块名称,并将当前生成的功能模块名称保存在配置文件中。 [0080] 当功能模块当前状态为非启动状态、关机状态或开机状态时,分别将该功能模块对应的功能模块名称保存到数据库中,或者保存到配置文件中 ,或者替换保存到配置文件中,保证减少用户的操作步骤,提升用户体验。 [0081] 参见图6,图6为本发明移动终端功能模块名称设置方法第五实施例的流程图。 [0082] 基于本发明移动终端功能模块名称设置方法实施例一,在执行步骤S之前 20 ,它还包括: [0083] 在步骤S 60 ,判断移动终端支持该功能模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0084]在根据设置的移动终端名称生成功能模块对应的功能模块名称之前,首先判断移动终端支持的功能模块,即判断移动终端支持哪些功能模块。 本实施例中,功能模块包括蓝牙模块、WIFI热点模块、WIFI直连模块等模块,移动终端在通过这些模块与其他移动终端进行通信时,需要提供一个名称,该名称可以通过 对方。 [0085] 设置好移动终端的名称后,需要在根据名称生成移动终端的各个功能模块对应的功能模块名称之前,先判断移动终端支持哪些功能模块,从而生成功能模块名称 这些功能模块的名称,从而为根据移动终端的名称自动修改移动终端的各个功能模块的名称提供了基础。 [0086] 请参阅图7,图7为本发明移动终端第一实施例的结构示意图。 [0087] 本实施例提供的移动终端包括: [0088] 设置模块 10 ,用于设置移动终端的名称; [0089] 名称生成模块 20 ,用于根据设置的移动终端名称,生成与移动终端中的功能模块对应的功能模块名称; [0090] 本实施例中,可以在移动终端的设置模块中增加一个入口,供用户输入移动终端的名称,用户可以通过该入口设置移动终端的名称。 在设置移动终端中各个功能模块对应的功能模块名称之前,首先通过设置模块设置移动终端的名称 10 . 移动终端的名称由用户自己设置,可以起到识别用户移动终端设备的作用,本实施例中为了保证该名称与周围其他移动设备的名称不同 终端具有,优选地使用用户的全名作为移动终端的名称。 [0091] 设置好手机端名字后,名字生成模块 20 根据移动终端支持的功能模块以及移动终端的名称,自动生成各个功能模块对应的功能模块名称。 在本实施例中,功能模块名称可以设置为移动终端的名称加上功能模块的功能名称。 [0092] 在本发明实施例中,设置移动终端的名称,然后根据设置的移动终端名称生成移动终端中的功能模块对应的功能模块名称。 通过设置移动终端的名称,可以自动修改移动终端中各个功能模块的名称,减少了用户的操作步骤,提高了用户体验。 [0093] 请参阅图8,图8为本发明移动终端第二实施例的结构示意图。 [0094] 在上述实施例的基础上,所述移动终端还包括: [0095] 显示模块 30 ,配置为:显示功能模块名称。 [0096] 根据移动终端名称自动生成各个功能模块对应的功能模块名称后,显示模块 30 将生成的功能模块名称通过界面显示给用户,本实施例中可以在移动终端的界面中列出各种功能模块以及对应的功能模块名称。 [0097]根据设置的移动终端名称自动生成各个功能模块对应的功能模块名称后,将生成的功能模块名称显示给用户,为用户确认功能模块名称提供依据。 [0098] 请参阅图9,图9为本发明移动终端第三实施例的结构示意图。 [0099] 在上述实施例的基础上,所述移动终端还包括: [0100] 提示模块 40 ,配置为:提示用户确认功能模块名称。 [0101] 生成的功能模块名称显示在移动端界面,同时提示模块 40 设有确认按钮供用户确认各个功能模块对应的功能模块名称,提示用户进行确认。 在这种情况下,如果用户接受自动生成的功能模块名称,则用户点击确认; 如果用户不接受名称,用户可以自行修改,修改完成后点击确认,即可完成移动终端功能模块名称的设置。 [0102] 显示生成的功能模块名称并提示用户确认界面显示的功能模块名称,可以进一步保证移动终端的各个功能模块的名称可以通过设置移动终端的名称自动修改。 [0103] 请参阅图10,图10为本发明移动终端第四实施例的结构示意图。 [0104] 在上述实施例的基础上,所述移动终端还包括: [0105] 一个保存模块 50 ,用于根据功能模块的当前状态,保存功能模块名称; 功能模块的当前状态包括非启动状态、关闭状态和开启状态。 [0106] 用户接受显示的自动生成的功能模块名称并点击确认后,或用户自行修改功能模块名称并点击确认后,此时保存模块 50 判断功能模块的当前状态,根据当前状态的不同,对功能模块名称进行不同的保存。 在本实施例中,功能模块的当前状态包括非启动状态、关机状态和开机状态,其中,非启动状态是指移动终端的功能模块从未启动过 在这些情况下,它是出厂的,或者恢复出厂设置,或者升级; 关闭状态是指功能模块已经启动,但当前处于关闭状态。 开启状态是指功能模块当前处于开启状态。 [0107] 用户确认自动生成的功能模块名称,或用户自行修改功能模块名称后,根据功能模块当前状态保存功能模块名称,方便查找和使用功能模块 下次启动功能模块时命名,为减少用户的操作步骤提供了前提保证。 [0108] 在上述实施例中,保存模块 50 配置为: [0109] 当功能模块的当前状态为非启动状态时,将该功能模块对应的功能模块名称保存到数据库中; [0110] 当功能模块的当前状态为关闭状态时,将该功能模块对应的功能模块名称保存到该功能模块的配置文件中; [0111]当功能模块的当前状态为开启状态时,将该功能模块对应的功能模块名称替换并保存到该功能模块的配置文件中。 [0112] 当判断功能模块的当前状态为非启动状态时,说明该功能模块的用于存储功能模块名称的配置文件还没有生成,此时,该功能模块 名称存储在移动终端的数据库中。 在本实施例中,根据功能模块名称生成一条记录,该记录以功能模块为键,功能模块名称为值,保存在数据库中。 功能模块启动时,在数据库中查找,判断其中是否有以功能模块为键,功能模块名称为值的记录,如果有,则在中显示功能模块名称 记录写入功能模块的配置文件,然后清空该值,下次启动功能模块时,数据库中的值不再使用,直接查找配置文件, 使用其中的值。 [0113] 当判断一个功能模块的当前状态为关闭状态时,说明该功能模块的用于存储功能模块名称的配置文件已经生成,此时直接 在配置文件中保存功能模块名称。 [0114] 当确定功能模块的当前状态为开机状态时,由于移动终端中的各个功能模块都有相应的更名处理过程,当功能模块的当前状态为开机状态时, 首先触发更改功能模块名称的处理流程,将配置文件中先前保存的名称替换为当前生成的功能模块名称,并将当前生成的功能模块名称保存在配置文件中。 [0115] 当功能模块当前状态为非启动状态、关机状态或开机状态时,分别将该功能模块对应的功能模块名称保存到数据库中,或者保存到配置文件中 ,或者替换保存在配置文件中,保证减少用户的操作步骤,提升用户体验。 [0116] 请参阅图11,图11为本发明移动终端第五实施例的结构示意图。 [0117] 在上述实施例的基础上,所述移动终端还包括: [0118] 判断模块 60 ,用于判断移动终端支持移动模块的情况; 功能模块至少包括蓝牙模块、WIFI热点模块和WIFI直连模块。 [0119] 在根据设置的移动终端名称生成功能模块对应的功能模块名称之前,首先通过判断模块判断移动终端支持的功能模块 40 ,即判断移动终端支持哪些功能模块。 本实施例中,功能模块包括蓝牙模块、WIFI热点模块、WIFI直连模块等模块,移动终端在通过这些模块与其他移动终端进行通信时,需要提供一个名称,该名称可以通过 对方。 [0120] 设置好移动终端的名称后,需要在根据名称生成移动终端的各个功能模块对应的功能模块名称之前,先判断移动终端支持哪些功能模块,从而生成功能模块名称 这些功能模块的名称,从而为根据移动终端的名称自动修改移动终端的各个功能模块的名称提供了基础。 [0121]在另一个实施例中,还提供了一种软件,用于执行上述实施例及优选实施例中描述的技术方案。 [0122] 在另一个实施例中,还提供了一种存储介质,该存储介质存储有上述软件,该存储介质包括但不限于:光盘、软盘、硬盘、闪存等。 [0123] 显然,本领域的技术人员应该理解,本发明实施例中的各个模块或步骤可以用通用的计算设备来实现,它们可以集中在单个计算设备上,也可以分布在由以下设备组成的网络中。 多个计算设备,备选地,它们可以由计算装置可执行的程序代码来执行,以便它们可以存储在存储装置中并由计算装置执行,并且在某些情况下,以不同于 也可以单独制作成单独的集成电路模块,或者将其中的部分模块或步骤制作成单个集成电路模块来实现。 因此,本文档不限于任何特定的硬件和软件组合。 [0124] 以上所述仅为本发明的较佳实施例而已,并不用于限制本发明的专利范围,任何利用本发明的说明书及附图所作的等同结构或等同过程变换,均属于本发明的范围。 直接或者间接应用于其他相关技术的,应当纳入本文件的专利保护范围。 工业实用性 [0125] 本发明实施例通过设置移动终端的名称,自动修改移动终端各功能模块的名称,减少了用户的操作步骤,提高了用户体验。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103856622A(String), EP2930915A1(String), EP2930915A4(String), EP2930915B1(String), US20150372974A1(String), US9455952B2(String), WO2013182100A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103856622A(String), EP2930915A1(String), EP2930915A4(String), EP2930915B1(String), US20150372974A1(String), US9455952B2(String), WO2013182100A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103856622A(String), EP2930915A1(String), EP2930915A4(String), EP2930915B1(String), US20150372974A1(String), US9455952B2(String), WO2013182100A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271087(Integer), CN103856622A(String), 1047924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271087(Integer), EP2930915A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271087(Integer), EP2930915A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271087(Integer), EP2930915B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271087(Integer), US20150372974A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271087(Integer), US9455952B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271087(Integer), WO2013182100A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN103856622A(String), CN103856622A(String), 1402416000(Integer), 271087(Integer), 185371(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185949(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185949(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185949(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185949(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:03.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.032 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185949(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.240 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20150249630A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and System for Controlling Message of Mobile Terminal and Mobile Terminal(String), 移动终端消息控制方法及系统及移动终端(String), US20150249630A1(String), A method and system for controlling a message of a mobile terminal and the mobile terminal including an application platform for receiving a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal. The application platform displays information to be processed in the message to be processed. With the method and system for controlling a message of a mobile terminal, flexibility in control over the message of the mobile terminal is improved, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved.(String), 一种移动终端消息控制方法及系统,该移动终端包括:应用平台,用于接收该移动终端的待处理消息,该待处理消息由管理平台转发,其中,该待处理消息被发送至移动终端。 移动端管理平台。 应用平台在待处理消息中显示待处理信息。 通过本发明的移动终端消息控制方法及系统,提高了移动终端消息控制的灵活性,提高了移动终端消息控制的易用性,提高了用户对信息的感知能力。 待处理得到改进。(String), US14/426696(String), 1375200000(Integer), US20150249630A1(String), 1441209600(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 7(Integer), US20040082348A1 | US20040158609A1 | US20050091670A1 | US20070239830A1 | US20090141879A1 | US20100093379A1 | US20100240401A1(String), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\aa5e25a2085a4a8da7720ff57aa40430.png(String), 185950(Integer), aa5e25a2085a4a8da7720ff57aa40430.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and System for Controlling Message of Mobile Terminal and Mobile Terminal(String), 移动终端消息控制方法及系统及移动终端(String), US20150249630A1(String), A method and system for controlling a message of a mobile terminal and the mobile terminal including an application platform for receiving a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal. The application platform displays information to be processed in the message to be processed. With the method and system for controlling a message of a mobile terminal, flexibility in control over the message of the mobile terminal is improved, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved.(String), 一种移动终端消息控制方法及系统,该移动终端包括:应用平台,用于接收该移动终端的待处理消息,该待处理消息由管理平台转发,其中,该待处理消息被发送至移动终端。 移动端管理平台。 应用平台在待处理消息中显示待处理信息。 通过本发明的移动终端消息控制方法及系统,提高了移动终端消息控制的灵活性,提高了移动终端消息控制的易用性,提高了用户对信息的感知能力。 待处理得到改进。(String), US14/426696(String), 1375200000(Integer), US20150249630A1(String), 1441209600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 7(Integer), US20040082348A1 | US20040158609A1 | US20050091670A1 | US20070239830A1 | US20090141879A1 | US20100093379A1 | US20100240401A1(String), \20230420\aa5e25a2085a4a8da7720ff57aa40430.png(String), 10(Integer), 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 1. A method for controlling a message of a mobile terminal, comprising:receiving, by an application platform, a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal; anddisplaying, by the application platform, information to be processed in the message to be processed.(String), 1、一种移动终端的消息控制方法,包括:应用平台接收管理平台转发的移动终端的待处理消息,该待处理消息由移动终端发送给管理平台;和应用平台在待处理消息中显示待处理信息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 2. The method according to claim 1, wherein before receiving, by the application platform, the message to be processed of the mobile terminal, which is forwarded by the management platform, the method further comprises:transmitting, by the mobile terminal, the message to be processed to the management platform according to a transmission rule, wherein the transmission rule comprises at least one of: information for indicating a type of the information to be processed, which is to be transmitted, and information for indicating a filtering condition for transmission of the information to be processed, which is to be transmitted.(String), 2.根据权利要求1所述的方法,其中应用平台接收管理平台转发的移动终端待处理消息之前,该方法还包括:移动终端根据传输规则向管理平台传输待处理消息,其中传输规则包括以下至少之一:用于指示待传输的待处理信息的类型的信息,用于指示传输待处理信息的过滤条件的信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 3. The method according to claim 2, wherein the transmission rule is directly set on the mobile terminal; and/or, the application platform transmits the set transmission rule to the mobile terminal.(String), 3.根据权利要求2所述的方法,其中传输规则直接在移动终端设置;和/或,应用平台将设置的传输规则发送给移动终端。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 4. The method according to claim 23, wherein the application platform transmitting the set transmission rule to the mobile terminal comprises:transmitting, by the application platform, an authentication message and the transmission rule to the management platform, wherein an identifier of the mobile terminal is carried in the authentication message; andperforming, by the management platform, subscribing relationship authentication on the mobile terminal, and under a condition that the mobile terminal passes the subscribing relationship authentication, transmitting the transmission rule to the mobile terminal according to the identifier of the mobile terminal.(String), 4.根据权利要求23所述的方法,其中应用平台向移动终端发送设置的传输规则,包括:应用平台向管理平台发送鉴权消息和传输规则,鉴权消息中携带移动终端的标识;和管理平台对移动终端进行订阅关系认证,在移动终端通过订阅关系认证的情况下,根据移动终端的标识向移动终端发送传输规则。(String), 1(Integer), 3(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 5. The method according to claim 1, wherein before receiving, by the application platform, the message to be processed of the mobile terminal, which is forwarded by the management platform, the method further comprises:performing, by the management platform, format check on the message to be processed, and performing the subscribing relationship authentication on the mobile terminal; andunder a condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, forwarding, by the management platform, the message to be processed to the application platform according to a subscribing relationship of the mobile terminal.(String), 5.根据权利要求1所述的方法,其中应用平台接收管理平台转发的移动终端待处理消息之前,该方法还包括:管理平台对待处理的消息进行格式校验,并对移动终端进行订阅关系认证;和在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,管理平台根据移动终端的订阅关系将待处理消息转发给应用平台。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 6. The method according to claim 1, wherein displaying, by the application platform, the information to be processed comprises:performing, by the application platform, permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; andunder a condition that the message to be processed passes the permission authentication, displaying, by the application platform, the information to be processed.(String), 6.根据权利要求1所述的方法,其中应用平台显示待处理信息包括:应用平台对待处理消息进行权限认证,权限用于表示是否允许在应用平台上展示待处理消息中的待处理信息。和在待处理消息通过权限认证的情况下,应用平台展示待处理信息。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 7. The method according to claim 1, wherein after displaying, by the application platform, the information to be processed, the method further comprises:transmitting, by the application platform, a reply message for the information to be processed to the management platform, wherein the reply message comprises: reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed; andperforming, by the management platform, authentication on the reply message, and under a condition that the reply message passes the authentication, transmitting the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forwarding the reply message to the mobile terminal for the mobile terminal to transmit the reply message to the source equipment of the information to be processed.(String), 7.根据权利要求1所述的方法,其中在应用平台显示待处理信息后,该方法还包括:应用平台向管理平台发送待处理信息的回复消息,该回复消息包括:待处理信息的回复信息、移动终端的标识和信息来源标识被处理;和管理平台对回复消息进行鉴权,在回复消息鉴权通过的情况下,根据回复消息中携带的转发标识将回复消息发送给待处理信息的源设备,或者将回复消息转发给移动终端,以便移动终端将回复消息发送给待处理信息的源设备。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 8. The method according to claim 1, wherein the information to be processed comprises at least one of: a short message to be processed, a missed call, QQ information to be processed and Microsoft Network (MSN) information to be processed.(String), 8.根据权利要求1所述的方法,其中所述待处理信息包括以下至少之一:待处理短信、未接来电、待处理QQ信息、待处理微软网络(MSN)信息。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 9. A mobile terminal, comprising:an acquiring component, configured to acquire information to be processed of the mobile terminal and generate a message to be processed, wherein the message to be processed comprises the information to be processed; anda first transmitting component, configured to transmit the message to be processed to a management platform and forward the message to be processed to an application platform through the management platform, wherein the application platform displays the information to be processed.(String), 9.移动终端,包括:获取模块,用于获取移动终端的待处理信息,并生成待处理消息,所述待处理消息包括所述待处理信息;和第一发送模块,用于将待处理消息发送给管理平台,并通过管理平台将待处理消息转发给应用平台,应用平台显示待处理信息。10、一种移动终端消息控制系统,其中该系统包括:如权利要求9所述的移动终端;管理平台,用于将移动终端发送的待处理消息转发给应用平台;应用平台,用于接收待处理消息,并显示待处理消息中的待处理信息。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:04.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185950(Integer), 10. A system for controlling a message of a mobile terminal, wherein the system comprises: the mobile terminal according to claim 9; a management platform, configured to forward the message to be processed, which is transmitted by the mobile terminal, to the application platform; and the application platform, configured to receive the message to be processed and display information to be processed in the message to be processed.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185950(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of communication, including, e.g., a method and system for controlling a message of a mobile terminal, and a mobile terminal. BACKGROUND [0002]In the related art, most of mobile phone services are controlled by an operator side. For example, the operator side may forward an incoming call of a user by a call forwarding service, and may prompt the user of a missed call by services such as a call reminding service and SmartCall. It can be seen that most of the mobile phone services need to be implemented by subscribing to specific services of an operator. [0003]For at least one problem in a related art, there is yet no effective solution. SUMMARY [0004]The embodiments of the disclosure provides a method and system for controlling a message of a mobile terminal and the mobile terminal, so as to at least solve the problem that a user needs to subscribe to a specific service of an operator to remind of information to be processed in a related art. [0005]According to an embodiment of the disclosure, a method for controlling a message of a mobile terminal is provided, including that: an application platform receives a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal; and the application platform displays information to be processed in the message to be processed. [0006]According to an embodiment of the disclosure, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the mobile terminal transmits the message to be processed to the management platform according to a transmission rule, wherein the transmission rule includes at least one of: information for indicating a type of the information to be processed, which is to be transmitted, and information for indicating a filtering condition for transmission of the information to be processed, which is to be transmitted. [0007]According to an embodiment of the disclosure, the transmission rule is directly set on the mobile terminal; and/or, the application platform transmits the set transmission rule to the mobile terminal. [0008]According to an embodiment of the disclosure, the application platform transmits the set transmission rule to the mobile terminal includes that: the application platform transmits an authentication message and the transmission rule to the management platform, wherein an identifier of the mobile terminal is carried in the authentication message; and the management platform performs subscribing relationship authentication on the mobile terminal, and under a condition that the mobile terminal passes the subscribing relationship authentication, transmits the transmission rule to the mobile terminal according to the identifier of the mobile terminal. [0009]According to an embodiment of the disclosure, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the management platform performs format check on the message to be processed, and performs the subscribing relationship authentication on the mobile terminal; and under a condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, the management platform forwards the message to be processed to the application platform according to a subscribing relationship of the mobile terminal. [0010]According to an embodiment of the disclosure, the application platform displays the information to be processed includes that: the application platform performs permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; and under a condition that the message to be processed passes the permission authentication, the application platform displays the information to be processed. [0011]According to an embodiment of the disclosure, after the application platform displays the information to be processed, the method for controlling the message of the mobile terminal further includes that: the application platform transmits a reply message for the information to be processed to the management platform, wherein the reply message includes: reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed; and the management platform performs authentication on the reply message, and under a condition that the reply message passes the authentication, transmits the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forwards the reply message to the mobile terminal, and the mobile terminal transmits the reply message to the source equipment of the information to be processed. [0012]According to an embodiment of the disclosure, the information to be processed includes at least one of: a short message to be processed, a missed call, QQ information to be processed and Microsoft Network (MSN) information to be processed. [0013]According to another aspect of the disclosure, a mobile terminal is provided, including: an acquiring component, configured to acquire information to be processed of the mobile terminal and generate a message to be processed, wherein the message to be processed includes the information to be processed; and a first transmitting component, configured to transmit the message to be processed to a management platform and forward the message to be processed to an application platform through the management platform, wherein the application platform displays the information to be processed. [0014]According to a third aspect of the disclosure, a system for controlling a message of a mobile terminal is provided, where the system comprises: any above-mentioned mobile terminal; a management platform, configured to forward the message to be processed, which is transmitted by the mobile terminal, to an application platform; and the application platform, configured to receive the message to be processed and display information to be processed in the message to be processed. [0015]According to the disclosure, the mobile terminal generates the message to be processed by using the information to be processed on the mobile terminal, transmits the message to be processed to the management platform, and forwards the message to be processed to the application platform through the management platform, and the application platform displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. BRIEF DESCRIPTION OF THE DRAWINGS [0016]The drawings are described here to provide further understanding of the disclosure, and form a part of the disclosure. The schematic embodiments and description of the disclosure are adopted to explain the disclosure, and do not form improper limits to the disclosure. In the drawings: [0017]FIG. 1 is a flowchart of a method for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0018]FIG. 2 is a structure diagram of a mobile terminal according to an embodiment of the disclosure; [0019]FIG. 3 is a structure diagram of another mobile terminal according to an embodiment of the disclosure; [0020]FIG. 4 is a structure diagram of a system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0021]FIG. 5 is a structure diagram of another system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0022]FIG. 6 is a structure diagram of a third system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0023]FIG. 7 is a structure diagram of a fourth system for controlling a message of a mobile terminal according to an embodiment of the disclosure; [0024]FIG. 8 is a flowchart of controlling a short message and a missed call of a user by utilizing a method for controlling a message of a mobile terminal according to an embodiment of the disclosure; and [0025]FIG. 9 is a flowchart of controlling a QQ/MSN message of a mobile phone of a user by utilizing a method for controlling a message of a mobile terminal according to an embodiment of the disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS [0026]The disclosure is described below with reference to the drawings and the embodiments in detail. It is important to note that the embodiments of the disclosure and the characteristics in the embodiments can be combined under the condition of no conflicts. [0027]A method for controlling a message of a mobile terminal is provided in the embodiment of the disclosure, and as shown in FIG. 1, the method for controlling the message of the mobile terminal includes S102 to S104. [0028]S102: an application platform receives a message to be processed of the mobile terminal, which is forwarded by a management platform, wherein the message to be processed is transmitted to the management platform by the mobile terminal. [0029]S104: the application platform displays information to be processed in the message to be processed. [0030]By the steps, the mobile terminal generates the message to be processed by using the information to be processed on the mobile terminal, transmits the message to be processed to the management platform, and forwards the message to be processed to the application platform through the management platform, and the application platform displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. [0031]According to an embodiment of the disclosure, in order to facilitate the authentication over the mobile terminal and improve the security of the information, the message to be processed can further include: an identifier of the mobile terminal and a source identifier of the information to be processed, besides the information to be processed. [0032]In order to flexibly transmit the information to be processed on the mobile terminal to meet requirements of different application scenarios, in the preferred embodiment, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the mobile terminal transmits the message to be processed to the management platform according to a transmission rule, wherein the transmission rule includes at least one of: information for indicating a type of the information to be processed, which is to be transmitted, and information for indicating a filtering condition for transmission of the information to be processed, which is to be transmitted. That is, the transmission rule can be set according to a habit or requirement of the user; the information indicating the type of the information to be processed, which is to be transmitted, for example, which information to be processed is to be transmitted and which information to be processed is not to be transmitted can be set according to the requirement. For example, according to the requirement, information to be processed such as short message information and a missed call can be set to be transmitted, QQ information to be processed can be set not to be transmitted, and the information of all types can also be set to be transmitted; and the filtering condition of the information to be processed, which is to be transmitted, can also be set, for example, if the short message information to be processed is set to be transmitted, a time frame in which the short message information to be processed is to be transmitted can further be set in order to the user to conveniently perceive the information to be processed. [0033]In order to meet the requirements of different application scenarios and improve the setting flexibility of the transmission rule, in the preferred embodiment, the transmission rule is directly set on the mobile terminal; and/or, the application platform transmits the set transmission rule to the mobile terminal, that is, different manners for setting the transmission rule can be selected according to different application scenarios, the transmission rule can be directly set on the mobile terminal, and can also be set through the application platform. Setting operation is conducted on an application display interface of the application platform, then the application platform transmits the set transmission rule to the mobile terminal through the management platform, and the mobile terminal performs setting according to the received transmission rule. [0034]In order to improve the security of the information, in the preferred embodiment, before the application platform receives the message to be processed of the mobile terminal, which is forwarded by the management platform, the method for controlling the message of the mobile terminal further includes that: the management platform performs format check on the message to be processed, and performs subscribing relationship authentication on the mobile terminal; and under the condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, the management platform forwards the message to be processed to the application platform according to a subscribing relationship of the mobile terminal. That is, after the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, the message to be processed is transmitted to the application platform, so that the security of the information is improved. [0035]In order to correctly display the information to be processed, in the preferred embodiment, that the application platform displays the information to be processed includes that: the application platform performs permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; and under the condition that the message to be processed passes the permission authentication, the application platform displays the information to be processed. That is, after that the information to be processed can be displayed is determined, the information to be processed is displayed. [0036]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, after the application platform displays the information to be processed, the method for controlling the message of the mobile terminal further includes that: the application platform transmits a reply message for the information to be processed to the management platform, wherein the reply message includes: reply information for the information to be processed, the identifier of the mobile terminal and a source identifier of the information to be processed; and the management platform performs authentication on the reply message, and under the condition that the reply message passes the authentication, transmits the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forwards the reply message to the mobile terminal, and the reply message is transmitted by the mobile to the source equipment of the information to be processed. That is, the user can process the information to be processed through the management platform, and directly transmits the processed rely message to the source equipment of the information to be processed through the management platform; and the information to be processed can also be processed through the management platform, the management platform forwards the processed reply message to the mobile terminal, and the mobile terminal automatically transmits the received reply message to the source equipment of the information to be processed. [0037]In order to meet application requirements of different users and improve the practicability, in the preferred embodiment, the information to be processed can include at least one of: a short message to be processed, a missed call, QQ information to be processed, MSN information to be processed and the like. [0038]In the preferred embodiment, a preferred mobile terminal is provided, and as shown in FIG. 2, the mobile terminal includes: an acquiring component 202, which is configured to acquire the information to be processed of the mobile terminal and generate a message to be processed, wherein the message to be processed includes the information to be processed; and a first transmitting component 204, connected to the acquiring component 202, which is configured to transmit the message to be processed to a management platform and forward the message to be processed to an application platform through the management platform, wherein the application platform displays the information to be processed. [0039]In the preferred embodiment, the acquiring component 202 generates the message to be processed by using the information to be processed on the mobile terminal, the first transmitting component 204 transmits the message to be processed to the management platform, and forwards the message to be processed to the application platform through the management platform, and the application platform displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. [0040]In order to meet the requirements of different application scenarios and improve the setting flexibility of a transmission rule, in the preferred embodiment, as shown in FIG. 3, the mobile terminal further includes: a first setting component 206, which is configured to set the transmission rule. [0041]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, as shown in FIG. 3, the mobile terminal further includes: a receiving component 208, which is configured to receive a reply message for the information to be processed, which is forwarded by the management platform, wherein the reply message is transmitted by the application platform, and the reply message includes reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed; and a first forwarding component 210, connected to the receiving component 208, which is configured to forward the reply message to source equipment of the information to be processed. [0042]In the preferred embodiment, a preferred system for controlling a message of a mobile terminal is provided, and as shown in FIG. 4, the system for controlling the message of the mobile terminal includes: the mobile terminal 402; a management platform 404, connected to the mobile terminal 402, which is configured to forward a message to be processed, which is transmitted by the mobile terminal, to an application platform; and the application platform 406, connected to the management platform 404, which is configured to receive the message to be processed and display information to be processed in the message to be processed. [0043]In the preferred embodiment, the mobile terminal 402 generates the message to be processed by using the information to be processed on the mobile terminal 402, transmits the message to be processed to the management platform 404, and forwards the message to be processed to the application platform 406 through the management platform 404, and the application platform 406 displays the information to be processed in the message to be processed, so that the user can be reminded of the information to be processed without subscribing to the specific service of the operator, and flexibility in control over the message of the mobile terminal is improved; and meanwhile, the application platform displays the information to be processed in the message to be processed to notify the information to be processed to the user, so that the user can be reminded of the information to be processed even though the mobile terminal is not around, usability in control over the message of the mobile terminal is improved, and the perceptibility of the user over the information to be processed is improved. [0044]In order to meet the requirements of different application scenarios and improve the setting flexibility of a transmission rule, in the preferred embodiment, as shown in FIG. 5, the application platform includes: a second setting rule 4062, which is configured to set the transmission rule and transmit the set transmission rule to the mobile terminal. [0045]In order to correctly display the information to be processed, in the preferred embodiment, as shown in FIG. 5, the application platform 406 further includes: a first authentication component 4064, which is configured to perform permission authentication on the message to be processed, wherein a permission is used for indicating whether the information to be processed in the message to be processed is permitted to be displayed on the application platform or not; and a display component 4066, connected to the first authentication component 4064, which is configured to, under the condition that the message to be processed passes the permission authentication, display the information to be processed. [0046]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, as shown in FIG. 5, the application platform 406 further includes: a second transmission component 4068, which is configured to transmit a reply message for the information to be processed to the management platform, wherein the reply message includes: reply information for the information to be processed, an identifier of the mobile terminal and a source identifier of the information to be processed. [0047]In order to improve the security of the information, in the preferred embodiment, as shown in FIG. 6, the management platform 404 includes: a second authentication component 4042, which is configured to perform format check on the message to be processed and perform subscribing relationship authentication on the mobile terminal; and a second forwarding component 4044, connected to the second authentication component 4042, which is configured to, under the condition that the message to be processed passes the format check and the mobile terminal passes the subscribing relationship authentication, forward the message to be processed to the application platform according to a subscribing relationship of the mobile terminal. [0048]In order to improve the flexibility of operation of the user over the information to be processed, in the preferred embodiment, the second forwarding component 4044 is further configured to perform authentication on the reply message for the information to be processed, and under the condition that the reply message passes the authentication, transmit the reply message to source equipment of the information to be processed according to a forwarding identifier carried in the reply message, or forward the reply message to the mobile terminal for the mobile terminal to transmit the reply message to the source equipment of the information to be processed. [0049]Each preferred embodiment is described below with reference to the drawings in detail. [0050]In the preferred embodiment, the mobile terminal takes a smart mobile phone as an example, FIG. 7 is a structure diagram of a fourth system for controlling a message of a mobile terminal, and as shown in FIG. 7, the system for controlling the message of the mobile terminal includes: the mobile terminal 702, wherein the mobile terminal 702 includes a missed information detection unit, which is configured to receive and process missed information of a user, such as missed call information, a missed short message, missed QQ information and missed MSN information. A function of the missed information detection unit can be realized through software, for example, by certain software, message contents such as the missed short message, the missed call information, the missed QQ information and the missed MSN information, and message sources such as a mobile phone number, a QQ number and an MSN number can be extracted from the mobile phone. The message can be transparently transmitted to a specific management platform in a certain format according to a set mode (equivalent to the above transmission rule); the management platform 704, which is configured to perform application and terminal access, terminal and application management and data transparent-transmission between the terminal and an application; and an application platform 706, wherein the application platform 706 can include: an authentication component 7062 (equivalent to the first authentication component 4064), which is configured to perform authentication on a message between the terminal and the application according to a set filtering condition, a background processing component 7064, which is configured to receive the missed information of the user from the management platform and process and transmit the information to a missed information display component, and the missed information display component 7066 (equivalent to the display component 4066), which is configured to display the information processed by the background processing component 7064. [0051]By the system for controlling the message of the mobile terminal, the user can control certain information of the mobile phone without subscribing to a certain service of an operator, and can receive a short message, know a missed call and communicate with a user of a chatting tool such as QQ, MSN and the like on the mobile phone even under the condition of not carrying the mobile phone. However, in order to flexibly transmit the information to be processed, the transmission rule for the message to be processed such as the short message, the missed call, a QQ message and an MSN message can be set on the mobile phone at first, wherein the transmission rule indicates which message needs to be forwarded, a filtering condition for forwarding and the like; there are two manners for setting the transmission rule, one is to set the transmission rule on the software of the mobile phone by the user, and the other is to set the transmission rule through a display interface (such as a web page) of the application platform by the user. The setting of the transmission rule through the display interface of the application platform can be implemented by the following steps that: [0052]S1: the user operates the application display interface, sets a forwarding rule, and submits the set forwarding rule. [0053]S2: the application platform performs message authentication to determine whether the user is permitted to use a function of transmitting the information to be processed to the application platform or not. [0054]S3: an application background processes, packs and converts an authentication message into a message format consistent with the management platform. [0055]S4: the management platform receives the authentication message from the application platform, performs subscribing relationship authentication and the like, extracts the identification information, such as to which user the message is to be transmitted, of the mobile terminal from the authentication message, and transparently transmits the message if the condition is met, and turns to S5. [0056]S5: the mobile phone terminal receives an automatic forwarding message from the management platform, parses the automatic forwarding message, and performs automatic forwarding setting according to an instruction. [0057]FIG. 8 is a flowchart of controlling a short message and a missed call of a user by utilizing a method for controlling a message of a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 8, the flow can include the following steps that: [0058]S802: a mobile phone terminal receives a short message (including a Fetion message) and a missed call, the short message (including the Fetion message) and the missed call are processed and packed into a message to be processed by the software in the mobile phone terminal, the message to be processed including: a mobile phone terminal number, a source mobile phone number and contents (short message contents or the missed call), and the mobile phone terminal transparently transmits the data of the message to be processed to a management platform. [0059]S804: the management platform performs message format check and subscribing relationship authentication on the message to be processed, and transparently transmits the data to a corresponding application platform according to a subscribing relationship. [0060]S806: an application background of the application platform parses the message to be processed, which is transmitted by the management platform, converts a message format of the message to be processed, and transmits the message to be processed to an authentication component (equivalent to the first authentication component 4064) of the application platform. [0061]S808: the authentication component performs internal subscribing relationship authentication, permission authentication and the like on the received message, and transmits the contents of the message passing the authentication to a user display component (equivalent to the display component 4066). [0062]S810: a user (user A) can directly reply the short message on a display interface of the application platform, and can select to directly forward a reply message through the management platform if the management platform can transmit the short message or to reply the short message through the mobile phone if the management platform cannot transmit the short message; for example, for reply contents, the message is forwarded to the management platform through the authentication component and a message processing component; the management platform forwards the reply message to a source mobile phone of the short message or the mobile phone terminal according to a forwarding identifier of the short message, and if being(String), 技术领域 [0001] 本发明涉及通信领域,例如包括一种移动终端的消息控制方法、系统及移动终端。 背景 [0002] 相关技术中,大部分手机业务由运营商侧控制。 例如,运营商侧可以通过呼叫转移业务来转移用户的来电,也可以通过来电提醒业务、SmartCall等业务提示用户有未接来电。 可以看出,大部分的手机业务都需要通过订阅运营商的特定业务来实现。 [0003] 对于相关技术中的至少一个问题,目前还没有有效的解决方案。 概括 [0004] 本发明实施例提供了一种控制移动终端消息的方法、系统及移动终端,以至少解决用户需要订阅运营商的特定业务来提醒信息的问题。 在相关技术中处理。 [0005] 根据本发明的一个实施例,提供了一种移动终端的消息控制方法,包括:应用平台接收管理平台转发的移动终端的待处理消息,其中,所述消息发送至 待处理通过移动终端传输至管理平台; 应用平台在待处理消息中显示待处理信息。 [0006] 根据本发明的一个实施例,在应用平台接收到管理平台转发的移动终端待处理消息之前,控制移动终端消息的方法还包括:移动终端发送 根据传输规则向管理平台发送待处理消息,其中,所述传输规则包括以下至少之一:用于指示待传输的待处理信息的类型的信息,以及用于指示过滤条件的信息 传输要处理的信息,即要传输的信息。 [0007] 根据本发明的一个实施例,传输规则直接设置在移动终端上; 和/或,应用平台将设置的传输规则发送给移动终端。 [0008] 根据本发明的一个实施例,应用平台向移动终端发送设置的传输规则包括:应用平台向管理平台发送鉴权消息和传输规则,其中,移动终端的标识携带在 认证信息; 管理平台对移动终端进行订阅关系认证,在移动终端通过订阅关系认证的情况下,根据移动终端的标识向移动终端发送传输规则。 [0009] 根据本发明的一个实施例,在应用平台接收到管理平台转发的移动终端待处理消息之前,控制移动终端消息的方法还包括:管理平台进行格式化 检查待处理的消息,并在移动终端上进行订阅关系认证; 在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,管理平台根据移动终端的订阅关系将待处理消息转发给应用平台。 [0010]根据本发明的一个实施例,应用平台展示待处理信息包括: 应用平台对待处理消息进行权限认证,权限用于指示消息中的待处理信息是否可以访问。 待处理是否允许在应用平台上展示; 在待处理消息通过权限认证的情况下,应用平台展示待处理信息。 [0011] 根据本发明的一个实施例,在应用平台显示待处理信息后,控制移动终端消息的方法还包括:应用平台向管理平台发送针对待处理信息的回复消息。 ,其中,回复消息包括:待处理信息的回复信息、移动终端的标识和待处理信息的来源标识; 管理平台对回复消息进行鉴权,在回复消息鉴权通过的情况下,根据回复消息中携带的转发标识将回复消息发送给待处理信息的源设备,或者转发 回复消息给移动终端,移动终端将回复消息发送给待处理信息的源设备。 [0012] 根据本发明的一个实施例,所述待处理信息包括以下至少之一:待处理短信、未接来电、待处理QQ信息、待处理微软网络(MSN)信息。 [0013] 根据本发明的另一方面,提供了一种移动终端,包括: 获取模块,用于获取移动终端的待处理信息并生成待处理消息,所述待处理消息包括待处理信息。 处理; 第一发送模块,用于将待处理消息发送给管理平台,并通过管理平台将待处理消息转发给应用平台,应用平台显示待处理信息。 [0014] 根据本发明的第三方面,提供了一种移动终端的消息控制系统,该系统包括: 上述任一种移动终端; 管理平台,用于将移动终端发送的待处理消息转发给应用平台; 应用平台,用于接收待处理消息,并显示待处理消息中的待处理信息。 [0015] 根据本发明,移动终端利用移动终端上的待处理信息生成待处理消息,将待处理消息发送给管理平台,并通过管理平台转发待处理消息给应用平台。 管理平台,应用平台将待处理信息显示在待处理消息中,用户无需订阅运营商的特定服务即可提醒待处理信息,消息控制灵活 改进了移动端; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 附图的简要说明 [0016] 此处描述的附图是为了提供对本公开的进一步理解,并且构成本公开的一部分。 本发明中的示意性实施例和说明用于解释本发明,并不对本发明构成不当限制。 在图纸中: [0017]图1是根据本发明实施例的移动终端的消息控制方法的流程图; [0018] 图2是根据本发明实施例的移动终端的结构图; [0019] 图3为本发明实施例提供的另一种移动终端的结构图; [0020] 图4是根据本发明实施例的移动终端的消息控制系统的结构图。 [0021] 图5为本发明实施例提供的另一种移动终端消息控制系统的结构图; [0022] 图6是根据本发明实施例的第三种移动终端消息控制系统的结构图; [0023] 图7是根据本发明实施例的第四种移动终端消息控制系统的结构图; [0024] 图8是根据本发明实施例的利用移动终端的消息控制方法控制用户的短信和未接来电的流程图; 和 [0025] 图9为根据本发明实施例的利用控制移动终端消息的方法控制用户手机QQ/MSN消息的流程图。 具体实施方式 [0026] 下面结合附图和实施例对本发明进行详细说明。 需要说明的是,在不冲突的情况下,本发明中的实施例及实施例中的特征可以相互组合。 [0027] 本发明实施例提供了一种移动终端的消息控制方法,如图1所示,该移动终端的消息控制方法包括: 102 到小号 104 . [0028] 小号 102 :应用平台接收管理平台转发的移动终端的待处理消息,该待处理消息由移动终端发送给管理平台。 [0029] 小号 104 :应用平台在待处理消息中显示待处理信息。 [0030] 通过上述步骤,移动终端利用移动终端上的待处理信息生成待处理消息,将待处理消息发送给管理平台,通过管理将待处理消息转发给应用平台。 平台,应用平台将待处理信息显示在待处理消息中,用户无需订阅运营商的特定服务即可提醒待处理信息,灵活控制消息 改进了移动端; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0031] 根据本发明的一个实施例,为了便于对移动终端进行鉴权,提高信息的安全性,待处理消息还可以包括:移动终端的标识和待处理信息的来源标识。 processed,除了要处理的信息。 [0032]为了灵活地在移动终端上传输待处理信息以满足不同应用场景的需求,在优选实施例中,应用平台在接收到管理平台转发的移动终端待处理消息之前, 所述移动终端的消息控制方法还包括: 移动终端根据传输规则向管理平台发送待处理消息, 其中, 传输规则包括以下至少之一: 指示消息类型的信息 待传输的待处理信息和用于指示传输待传输的待处理信息的过滤条件的信息。 即可以根据用户的习惯或需求设置传输规则; 表示待处理信息的类型的信息,例如,哪些待处理信息需要传输,哪些待处理信息不需要传输,可以根据需要进行设置。 例如,根据需要,可以设置发送短信信息、未接来电等需要处理的信息,可以设置不发送需要处理的QQ信息,还可以设置所有类型的信息。 设置为传输; 并且还可以设置待发送的待处理信息的过滤条件,例如,如果待处理的短消息信息设置为发送,则发送该短消息信息的时间范围 为了方便用户感知待处理的信息,还可以进一步设置待处理的待传输信息。 [0033] 为了满足不同应用场景的需求,提高传输规则设置的灵活性,在优选实施例中,传输规则直接设置在移动终端上; 和/或,应用平台将设置的传输规则发送给移动终端,即可以根据不同的应用场景选择不同的传输规则设置方式,传输规则可以直接在移动终端上设置,可以 也可以通过应用平台进行设置。 在应用平台的应用显示界面进行设置操作,然后应用平台通过管理平台将设置的传输规则发送给移动终端,移动终端根据接收到的传输规则进行设置。 [0034] 为了提高信息的安全性,在优选实施例中,在应用平台接收到管理平台转发的移动终端待处理消息之前,控制移动终端消息的方法还包括: 即:管理平台对待处理的消息进行格式校验,并对移动终端进行订阅关系认证; 在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,管理平台根据移动终端的订阅关系将待处理消息转发给应用平台。 即待处理消息通过格式校验,移动终端通过订阅关系认证后,将待处理消息传输至应用平台,提高了信息的安全性。 [0035]为了正确显示待处理信息,在优选实施例中,应用平台显示待处理信息包括: 应用平台对待处理消息进行权限认证,其中,权限用于指示是否允许。 待处理消息中的待处理信息是否允许在应用平台上展示; 在待处理消息通过权限认证的情况下,应用平台展示待处理信息。 即在确定可以显示待处理信息后,显示待处理信息。 [0036] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,在应用平台显示待处理信息后,控制移动终端消息的方法还包括:应用 平台向管理平台发送待处理信息的回复消息,该回复消息包括:待处理信息的回复信息、移动终端的标识和待处理信息的来源标识; 管理平台对回复消息进行鉴权,在回复消息鉴权通过的情况下,根据回复消息中携带的转发标识将回复消息发送给待处理信息的源设备,或者转发 回复消息给移动终端,回复消息由移动终端发送给待处理信息的源设备。 即用户可以通过管理平台对待处理信息进行处理,并通过管理平台将处理后的依赖报文直接发送给待处理信息的源设备; 还可以通过管理平台对待处理信息进行处理,管理平台将处理后的回复消息转发给移动终端,移动终端自动将接收到的回复消息发送给待处理信息的源设备。 [0037] 为了满足不同用户的应用需求,提高实用性,在优选实施例中,待处理信息可以包括以下至少之一:待处理短信、未接来电、待处理QQ信息、MSN信息 待处理之类的。 [0038] 在本优选实施例中,提供了一种优选的移动终端,如图2所示,该移动终端包括: 获取模块 202 ,用于获取移动终端的待处理信息,并生成待处理消息,所述待处理消息包括所述待处理信息; 和第一传输组件 204 , 连接到获取组件 202 ,用于将所述待处理消息传输至管理平台,并通过所述管理平台将所述待处理消息转发至应用平台,所述应用平台展示所述待处理信息。 [0039] 在优选实施例中,获取组件 202 移动终端上的待处理信息生成待处理消息,第一发送部件 204将待处理的消息传输给管理平台,通过管理平台将待处理的消息转发给应用平台,应用平台将待处理的信息显示在待处理的消息中,以便用户可以 无需订阅运营商的特定服务即可提醒需要处理的信息,提高了移动终端消息控制的灵活性; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0040] 为了满足不同应用场景的需求,提高传输规则设置的灵活性,在优选实施例中,如图3所示,移动终端还包括: 第一设置模块 206 , 用于设置传输规则。 [0041] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,如图3所示,移动终端还包括: 接收模块 208 ,用于接收管理平台转发的对待处理信息的回复消息,其中,回复消息由应用平台发送,回复消息包括对待处理信息的回复信息, 移动终端的标识和待处理信息的来源标识; 和第一个转发组件 210 , 连接到接收组件 208 ,用于将回复消息转发给待处理信息的源设备。 [0042] 在本优选实施例中,还提供了一种优选的移动终端消息控制系统,如图4所示,所述移动终端消息控制系统包括: 移动终端 402 ; 管理平台 404 , 连接到移动端 402 ,用于将移动终端发送的待处理消息转发给应用平台; 和应用平台 406 , 连接到管理平台 404 ,用于接收待处理消息,并显示待处理消息中的待处理信息。 [0043] 在优选实施例中,移动终端 402 利用移动端的待处理信息生成待处理消息 402 , 将待处理的消息传送给管理平台 404 ,并将待处理的消息转发给应用平台 406 通过管理平台 404 , 以及应用平台 406 在待处理消息中显示待处理信息,使用户无需订阅运营商的特定服务即可提醒待处理信息,提高了对移动终端消息的控制灵活性。 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0044] 为了满足不同应用场景的需求,提高传输规则设置的灵活性,在优选实施例中,如图5所示,应用平台包括: 第二设置规则 4062 ,用于设置传输规则,并将设置的传输规则发送给移动终端。 [0045]为了正确显示待处理信息,在优选实施例中,如图5所示,应用平台 406 还包括:第一认证组件 4064 ,用于对所述待处理消息进行权限认证,其中,权限用于指示所述待处理消息中的所述待处理信息是否允许在所述应用平台上展示。 和一个显示组件 4066 , 连接到第一个认证组件 4064 ,用于在待处理消息通过权限认证的情况下,显示待处理信息。 [0046] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,如图5所示,应用平台 406 还包括:第二传输组件 4068 ,用于向所述管理平台发送所述待处理信息的回复消息,所述回复消息包括:所述待处理信息的回复信息、所述移动终端的标识和所述待处理信息的来源标识 处理。 [0047] 为了提高信息的安全性,在优选实施例中,如图6所示,管理平台 404 包括:第二个身份验证组件 4042 ,用于对待处理的消息进行格式检查,并对移动终端进行订阅关系认证; 和第二个转发组件 4044 , 连接到第二个身份验证组件 4042 ,用于在待处理消息通过格式校验且移动终端通过订阅关系认证的情况下,根据移动终端的订阅关系将待处理消息转发给应用平台。 [0048] 为了提高用户对待处理信息的操作灵活性,在优选实施例中,第二转发组件 4044 还用于对所述待处理信息的回复消息进行鉴权,在所述回复消息鉴权通过的情况下,根据所述待处理信息中携带的转发标识将所述回复消息发送给所述待处理信息的源设备 回复消息,或者将回复消息转发给移动终端,以便移动终端将回复消息发送给待处理信息的源设备。 [0049] 下面结合附图详细描述每个优选实施例。 [0050] 在本优选实施例中,移动终端以智能手机为例,图7为第四种移动终端消息控制系统的结构图,如图7所示,该消息控制系统为: 移动终端包括:移动终端 702 , 其中移动终端 702 包括漏接信息检测单元,用于接收并处理用户的漏接信息,例如漏接电话信息、漏接短信、漏接QQ信息、漏接MSN信息等。 漏接信息检测单元的功能可以通过软件实现,例如通过某种软件实现漏接短信、漏接电话信息、漏接QQ信息、漏接MSN信息等消息内容,以及漏接消息来源等。 可以从手机中提取手机号、QQ号和MSN号。 消息可以按照设定的模式以一定的格式透传到特定的管理平台(相当于上面的传输规则); 管理平台 704 ,用于进行应用与终端的接入、终端与应用的管理以及终端与应用之间的数据透传; 和应用平台 706 , 其中应用平台 706 可以包括:身份验证组件 7062 (相当于第一个认证组件 4064),用于根据设定的过滤条件对终端与应用之间的消息进行鉴权,后台处理组件 7064 ,用于从管理平台接收用户的遗漏信息,处理并传递给遗漏信息展示组件,所述遗漏信息展示组件 7066 (相当于显示组件 4066 ), 用于显示后台处理组件处理后的信息 7064 . [0051] 通过本发明的移动终端消息控制系统,用户无需开通运营商的某项服务,即可控制手机的某些信息,并可接收短信、知晓未接来电、与某运营商的用户进行通话。 即使在不携带手机的情况下,也可以在手机上使用QQ、MSN等聊天工具。 但是,为了灵活传输待处理信息,可以先在手机上设置短消息、未接来电、QQ消息、MSN消息等待处理消息的传输规则,其中 传输规则表示需要转发哪些消息、转发的过滤条件等; 设置传输规则有两种方式,一种是用户在手机软件上设置传输规则,另一种是通过手机的显示界面(如网页)设置传输规则。 用户的应用平台。 通过应用平台的显示界面设置传输规则可以通过以下步骤实现: [0052] 小号 1 :用户操作应用展示界面,设置转发规则,提交设置的转发规则。 [0053] 小号 2 :应用平台进行消息鉴权,判断用户是否允许使用将待处理信息传送给应用平台的功能。 [0054] 小号 3 :应用后台对认证消息进行处理、打包、转换为与管理平台一致的消息格式。 [0055] 小号 4 :管理平台接收应用平台的鉴权消息,进行订阅关系鉴权等,从鉴权消息中提取移动终端的标识信息,如向哪个用户发送消息,透传 如果满足条件则消息,并转向 S 5 . [0056] 小号 5 :手机终端接收来自管理平台的自动转发消息,解析自动转发消息,根据指令进行自动转发设置。 [0057] 图8是根据本发明实施例的利用移动终端的消息控制方法控制用户的短信和未接来电的流程图,如图8所示,该流程可以包括: 步骤: [0058] 小号 802 :手机终端收到短信(包括飞信短信)和未接来电,将短信(包括飞信短信)和未接来电处理打包成短信,由手机中的软件进行处理 终端,待处理消息包括:手机终端号码,源手机号码和内容(短信内容或未接来电),手机端透传待处理消息数据给管理端 平台。 [0059] 小号 804 :管理平台对待处理的消息进行消息格式校验和订阅关系认证,并根据订阅关系将数据透传给相应的应用平台。 [0060] 小号 806:应用平台的应用后台解析管理平台传来的待处理消息,转换待处理消息的消息格式,将待处理消息传给鉴权组件(相当于第一个) 认证组件 4064 ) 的应用平台。 [0061] 小号 808 :认证组件对接收到的消息进行内部订阅关系认证、权限认证等,并将认证通过的消息内容发送给用户显示组件(相当于显示组件 4066 ). [0062] 小号 810 :用户(用户A)可以在应用平台的显示界面上直接回复短信,如果管理平台可以转发短信或者回复短信,可以选择直接通过管理平台转发回复消息 管理平台无法发送短信时通过手机; 例如,对于回复内容,通过鉴权组件和消息处理组件将消息转发给管理平台。 管理平台根据短信的转发标识将回复消息转发给短信的源手机或手机终端,如果是管理平台转发的,则直接发送回复消息(the transmitted message 包括手机终端号码)通过管理平台认证; 否则,回复消息经管理平台鉴权后转发至手机终端,由手机终端软件进行消息处理,自动发送。 [0063] 在本优选实施例中,该应用场景只是举例说明而不做限定,该应用场景为用户手机登录QQ、MSN等聊天工具,但不能或未随身携带, 且用户所在网络不支持聊天工具的登录, 图9为利用根据本发明的控制移动终端消息的方法控制用户手机QQ/MSN消息的流程图 对于本发明的一个实施例,如图9所示,该流程可以包括以下步骤: [0064] 小号 902 :手机终端接收QQ或MSN消息内容,对QQ或MSN消息内容进行处理,由手机终端中的软件按照时序打包生成待处理消息,其中待处理消息为 处理包括:手机终端号码、源QQ或MSN号码及内容,将待处理消息的数据透传给管理平台。 [0065] 小号 904 :管理平台对待处理的消息进行消息格式校验和订阅关系认证,并根据订阅关系将数据透传给相应的应用平台。 [0066] 小号 906 :应用平台的应用后台解析管理平台传来的待处理消息,转换待处理消息的消息格式,将待处理消息传给鉴权组件(相当于第一个) 认证组件 4064 ) 的应用平台。 [0067] 小号 908 :认证组件对接收到的消息进行内部订阅关系认证、权限认证等,并将认证通过的消息内容发送给用户显示组件(相当于显示组件 4066 ). [0068] 小号 910 :用户回复消息,回复消息经过鉴权模块和消息处理模块处理后,传给管理平台。 [0069] 小号 912:管理平台进行回复消息格式认证、订阅关系认证等,并将数据透传至手机端。 [0070] 小号 914 :手机端提取并格式化回复信息,按时间顺序自动回复QQ/MSN消息。 [0071] 在上述优选实施例中,不需要用户直接在用户手机的界面上处理漏话,用户手机未携带的漏话(待处理信息) 用户可以快速获取用户,用户可以通过应用界面回复消息,提高了用户体验。 [0072] 综上所述,本优选实施例实现了以下技术效果: 移动终端利用移动终端上的待处理信息生成待处理消息,将待处理消息发送给管理平台,转发消息 待处理信息通过管理平台发送至应用平台,应用平台将待处理信息显示在待处理消息中,使用户无需订阅特定服务即可提醒待处理信息 运营商,提高了对移动终端消息控制的灵活性; 同时,应用平台在待处理消息中显示待处理信息,将待处理信息通知给用户,使得用户在移动终端不在身边时也能提醒该待处理信息。 ,提高了对移动终端消息控制的易用性,提高了用户对待处理信息的感知度。 [0073] 显然,本领域的技术人员应该知道,本发明的各个组成部分或步骤可以由一个通用的计算设备来实现,这些组成部分或步骤可以集中在单个计算设备上,也可以分布在多个计算设备组成的网络上。 设备,并且可以可选地由计算设备可执行的可编程代码来实现,使得组件或步骤可以存储在存储设备中以与计算设备一起执行,或者可以形成每个集成电路组件,或者其中的多个组件或步骤 可以组成一个单一的集成电路元件来实现。 因此,本公开不限于任何特定的硬件和软件组合。 [0074] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明,本领域的技术人员可以对本发明做出各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2884464A1(String), CN103685688A(String), CN103685688B(String), EP2894937A2(String), EP2894937A4(String), US20150249630A1(String), WO2013174353A2(String), WO2013174353A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2884464A1(String), CN103685688A(String), CN103685688B(String), EP2894937A2(String), EP2894937A4(String), US20150249630A1(String), WO2013174353A2(String), WO2013174353A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2884464A1(String), CN103685688A(String), CN103685688B(String), EP2894937A2(String), EP2894937A4(String), US20150249630A1(String), WO2013174353A2(String), WO2013174353A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), CA2884464A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), CN103685688A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271380(Integer), CN103685688B(String), 1048711(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), EP2894937A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), EP2894937A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.538 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), US20150249630A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), WO2013174353A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271380(Integer), WO2013174353A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN103685688B(String), CN103685688B(String), 1470153600(Integer), 271380(Integer), 185664(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185950(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185950(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185950(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:05.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185950(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for inputting function of mobile terminal using user's grip posture while holding mobile terminal(String), 使用用户握持移动终端的握持姿势输入移动终端功能的方法和装置(String), US8055305B2(String), An apparatus for and a method of inputting a function of a mobile terminal such as a mobile phone, in which a grip posture of a user who holds the mobile terminal is recognized and a function corresponding to the recognized grip posture is detected. The method includes: recognizing a grip posture of a user who uses the mobile terminal; detecting a function corresponding to the recognized grip posture; and performing the detected function. Accordingly, by considering user's grip postures formed when performing the functions of a mobile terminal such as a mobile phone, specific functions are respectively matched to a plurality of grip postures, a grip posture of a user who is holding the mobile terminal is recognized, and a function corresponding to the recognized grip posture is automatically performed without any operation such as an additional key input operation. Therefore, a complex input unit or input method is not required even when diverse functions are provided by the mobile terminal, and the user can easily and conveniently use the mobile terminal.(String), 一种用于输入诸如移动电话的移动终端的功能的设备和方法,其中识别持有移动终端的用户的握持姿势并且检测与识别的握持姿势相对应的功能。 该方法包括:识别使用移动终端的用户的握持姿势; 检测与识别出的握持姿势对应的功能; 并执行检测到的功能。 因此,通过考虑用户在执行手机等移动终端的功能时形成的握持姿势,将特定功能分别与多个握持姿势相匹配,识别出手持移动终端的用户的握持姿势,并 自动执行与识别的握持姿势对应的功能,无需任何操作,例如额外的键输入操作。 因此,即使移动终端提供多种功能,也不需要复杂的输入单元或输入方法,用户可以轻松方便地使用移动终端。(String), US11/476631(String), 1151510400(Integer), US8055305B2(String), 1320681600(Integer), 1320681600(Integer), 美国(String), 4(Integer), KR(String), 2(Integer), 19(Integer), KR1020060028295A | US20010014616A1 | US20010044318A1 | US20020115469A1 | US20020198006A1 | US20040157647A1 | US20040204016A1 | US20050035955A1 | US20050143124A1 | US20050250553A1 | US20060084482A1 | US20060238513A1 | US20060248478A1 | US20080214250A1 | US6298230B1 | US7098894B2 | US7440003B2 | USRE40116E1(String), 31(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\80334ee6bc644737a74b8e885fe3d49c.png(String), 185951(Integer), 80334ee6bc644737a74b8e885fe3d49c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for inputting function of mobile terminal using user's grip posture while holding mobile terminal(String), 使用用户握持移动终端的握持姿势输入移动终端功能的方法和装置(String), US8055305B2(String), An apparatus for and a method of inputting a function of a mobile terminal such as a mobile phone, in which a grip posture of a user who holds the mobile terminal is recognized and a function corresponding to the recognized grip posture is detected. The method includes: recognizing a grip posture of a user who uses the mobile terminal; detecting a function corresponding to the recognized grip posture; and performing the detected function. Accordingly, by considering user's grip postures formed when performing the functions of a mobile terminal such as a mobile phone, specific functions are respectively matched to a plurality of grip postures, a grip posture of a user who is holding the mobile terminal is recognized, and a function corresponding to the recognized grip posture is automatically performed without any operation such as an additional key input operation. Therefore, a complex input unit or input method is not required even when diverse functions are provided by the mobile terminal, and the user can easily and conveniently use the mobile terminal.(String), 一种用于输入诸如移动电话的移动终端的功能的设备和方法,其中识别持有移动终端的用户的握持姿势并且检测与识别的握持姿势相对应的功能。 该方法包括:识别使用移动终端的用户的握持姿势; 检测与识别出的握持姿势对应的功能; 并执行检测到的功能。 因此,通过考虑用户在执行手机等移动终端的功能时形成的握持姿势,将特定功能分别与多个握持姿势相匹配,识别出手持移动终端的用户的握持姿势,并 自动执行与识别的握持姿势对应的功能,无需任何操作,例如额外的键输入操作。 因此,即使移动终端提供多种功能,也不需要复杂的输入单元或输入方法,用户可以轻松方便地使用移动终端。(String), US11/476631(String), 1151510400(Integer), US8055305B2(String), 1320681600(Integer), 1320681600(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 19(Integer), KR1020060028295A | US20010014616A1 | US20010044318A1 | US20020115469A1 | US20020198006A1 | US20040157647A1 | US20040204016A1 | US20050035955A1 | US20050143124A1 | US20050250553A1 | US20060084482A1 | US20060238513A1 | US20060248478A1 | US20080214250A1 | US6298230B1 | US7098894B2 | US7440003B2 | USRE40116E1(String), \20230420\80334ee6bc644737a74b8e885fe3d49c.png(String), 31(Integer), 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 1. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing a grip posture comprises:receiving output signals from a plurality of touch sensors on the mobile terminal; andrecognizing the grip posture using the output signals from the touch sensors, wherein the recognizing the grip posture using the output signals comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, and a distance between adjacent contact points in each portion of the mobile terminal using the sensor output signals; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, and the distance between adjacent contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 1.一种移动终端功能的输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:接收来自移动终端上的多个触摸传感器的输出信号;和利用触摸传感器的输出信号识别握持姿势,其中,利用输出信号识别握持姿势包括:将移动终端的表面分成多个部分;使用传感器输出信号检测移动终端的每个部分中的接触点的数量、每个检测到的接触点的接触宽度以及相邻接触点之间的距离;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度以及移动终端的每个部分中相邻接触点之间的距离来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 2. The method of claim 1, wherein the plurality of touch sensors are arranged on a surface of the mobile terminal at regular intervals.(String), 2.如权利要求1所述的方法,其中多个触摸传感器以规则的间隔排列在移动终端的表面上。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 3. The method of claim 1, wherein the plurality of touch sensors are arranged in each of the portions at different intervals according to how frequently the user touches each portion when the user grips the mobile terminal.(String), 3.如权利要求1所述的方法,其中多个触摸传感器根据用户在握持移动终端时触摸每个部分的频率,以不同的间隔布置在每个部分中。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 4. The method of claim 3, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 4.如权利要求3所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 5. The method of claim 1, wherein, in the recognizing the grip posture using the output signals, the user's grip posture is recognized from the output signals by using one of an artificial neuron network, a template matching, a hidden Markov model, and a support vector machine (SVM).(String), 5.如权利要求1所述的方法,其中,在使用输出信号识别握持姿势中,通过使用人工神经元网络、模板匹配、隐马尔可夫模型和支持向量机(SVM)中的一种从输出信号识别用户的握持姿势。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 6. The method of claim 5, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 6.如权利要求5所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 7. The method of claim 1, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 7.如权利要求1所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 8. The method of claim 1, wherein the grip posture includes at least one of a right hand/vertical grip, a right hand/horizontal grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/horizontal grip, and a left hand/vertical grip.(String), 8.如权利要求1所述的方法,其中握持姿势包括右手/竖握、右手/横握、双手/横握、双手/竖握、左手/横握、左手/竖握中的至少一种.9.如权利要求8所述的方法,其中当识别的握持姿势为右手/竖握时,识别的握持姿势对应的功能为通话功能。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 9. The method of claim 8, wherein the function corresponding to the recognized grip posture is a phone call function when the recognized grip posture is a right hand/vertical grip.(String), 10.如权利要求8所述的方法,其中当识别的握持姿势为双手/竖握时,识别的握持姿势对应的功能为文本输入功能。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 10. The method of claim 8, wherein the function corresponding to the recognized grip posture is a text input function when the recognized grip posture is a both hands/vertical grip.(String), 11.如权利要求8所述的方法,其中当识别的握持姿势为右手/横握时,识别的握持姿势对应的功能为拍照功能。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 11. The method of claim 8, wherein the function corresponding to the recognized grip posture is a photography function when the recognized grip posture is a right hand/horizontal grip.(String), 12.如权利要求8所述的方法,其中当识别的握持姿势为双手/横握时,识别的握持姿势对应的功能为游戏功能。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 12. The method of claim 8, wherein the function corresponding to the recognized grip posture is a game function when the recognized grip posture is a both hands/horizontal grip.(String), 13.如权利要求1所述的方法,其中检测功能包括基于键输入和移动终端的当前功能中的至少一个来检测与识别的握持姿势相对应的多个功能之一。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 13. The method of claim 1, wherein the detecting a function comprises detecting one of plural functions corresponding to the recognized grip posture based on at least one of a key input and a current function of the mobile terminal.(String), 14.如权利要求1所述的方法,还包括,当至少两个函数对应于识别的握持姿势时:显示功能;和在显示的功能中接收用户想要执行的功能。(String), 1(Integer), 12(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 14. The method of claim 1, further comprising, when at least two functions correspond to the recognized grip posture:displaying the functions; andreceiving a function that the user wants to perform among the displayed functions.(String), 15.一种存储用于执行权利要求1的方法的程序的非暂时性计算机可读记录介质。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 15. A non-transitory computer readable recording medium storing a program for executing the method of claim 1.(String), 16.一种移动终端功能的输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:将移动终端的表面分成多个部分;检测移动终端各部分的接触点个数、每个检测到的接触点的接触宽度和相邻接触点之间的距离;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度以及移动终端的每个部分中相邻接触点之间的距离来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 14(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 16. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing the grip posture comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, and a distance between adjacent contact points in each portion of the mobile terminal; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, and the distance between adjacent contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 17.如权利要求16所述的方法,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 17. The method of claim 16, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 18.一种包含在移动终端中的功能输入装置,该装置包括:握持姿势识别单元,用于识别用户握持移动终端的握持姿势,其中识别出的握持姿势是多种握持姿势中的一种;和功能检测单元,用于检测对应于识别的握持姿势的功能,其中,所述握持姿势识别单元包括:多个触摸传感器;接触检测单元,用于基于来自单独部分中的触摸传感器的输出信号来检测用户是否接触移动终端的表面被划分成的单独部分;和握持姿势确定单元,使用每个部分的检测结果来确定用户的握持姿势,其中,接触检测单元检测接触点的数量、每个检测到的接触点的接触宽度以及每个部分中的相邻接触点之间的距离,并且抓握姿势确定单元使用检测到的接触点的数量来确定用户的抓握姿势,每个检测到的接触点的接触宽度,以及每个部分相邻接触点之间的距离,以及其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 18. A function input apparatus included in a mobile terminal, the apparatus comprising:a grip posture recognition unit to recognize a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture,wherein the grip posture recognition unit comprises:a plurality of touch sensors;a contact detection unit to detect whether the user contacts individual portions into which the surface of the mobile terminal is divided based on output signals from touch sensors in the individual portions; anda grip posture determining unit to determine the user's grip posture using the detection result for each portion,wherein the contact detection unit detects a number of contact points, a contact width of each detected contact point, and a distance between adjacent contact points in each portion, and the grip posture determining unit determines the user's grip posture using the detected number of contact points, the contact width of each detected contact point, and the distance between adjacent contact points at each portion, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 19.如权利要求18所述的功能输入装置,其中多个触摸传感器以一定间隔排列在移动终端表面。(String), 0(Integer), 17(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 19. The function input apparatus of claim 18, wherein the plurality of touch sensors are arranged on the surface of the mobile terminal at regular intervals.(String), 20.如权利要求18所述的功能输入装置,其中多个触摸传感器根据用户在握持移动终端时触摸每个部分的频率,以不同的间隔布置在每个部分上。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 20. The function input apparatus of claim 18, wherein the plurality of touch sensors are arranged on each of the portions at different intervals according to how frequently the user touches each portion when the user grips the mobile terminal.(String), 21.如权利要求20所述的功能输入装置,其中移动终端的多个部分包括前侧、后侧、上部、底部、左侧和右侧。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 21. The function input apparatus of claim 20, wherein the plurality of portions of the mobile terminal include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side.(String), 22.如权利要求18所述的功能输入装置,其中抓握姿势识别单元使用人工神经元网络、模板匹配、隐马尔可夫模型和支持向量机(SVM)中的一种来识别用户的抓握姿势。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 22. The function input apparatus of claim 18, wherein the grip posture recognition unit recognizes the user's grip posture using one of an artificial neuron network, a template matching, a hidden Markov model, and a support vector machine (SVM).(String), 23.如权利要求18所述的功能输入装置,其中握持姿势包括右手/横握、右手/竖握、双手/横握、双手/竖握、左手/横握、左手/竖握中的至少一种.24.如权利要求18所述的功能输入装置,其中功能检测单元接收来自用户的键输入,确定移动终端的当前功能,并基于键输入和移动终端的当前功能中的至少一个来检测与识别的握持姿势相对应的多个功能之一.25.如权利要求18所述的功能输入装置,还包括:显示单元向用户显示信息;和用户输入单元接收来自用户的输入,其中,当两个或更多功能对应于识别的握持姿势时,显示单元显示对应于识别的握持姿势的功能,并且用户输入单元接收显示的功能中用户想要执行的功能。(String), 1(Integer), 21(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 23. The function input apparatus of claim 18, wherein the grip posture includes at least one of a right hand/horizontal grip, a right hand/vertical grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/horizontal grip, and a left hand/vertical grip.(String), 26.功能输入装置、装置包括:传感器单元具有多个单独检测用户与移动终端的接触的触摸传感器,检测到的接触定义检测到的握持姿势;抓握姿势识别单元基于从传感器单元检测到的抓握姿势来识别抓握姿势,其中识别出的抓握姿势是多个抓握姿势之一;和功能检测单元,用于检测对应于识别的握持姿势的功能,其中,所述握持姿势识别单元包括:特征提取单元,用于提取检测到的握持姿势的特征数据;和存储器检索部,检索存储器,输出与检测出的握持姿势的特征数据对应的存储在存储器中的特征数据中定义的握持姿势,作为识别出的握持姿势,其中,特征数据包括各部分接触点的个数、检测到的各接触点的接触宽度、各部分相邻接触点之间的距离,用于判断用户的握持姿势,以及其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 22(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 24. The function input apparatus of claim 18, wherein the function detection unit receives a key input from a user, determines a current function of the mobile terminal, and detects one of plural functions corresponding to the recognized grip posture based on at least one of the key input and the current function of the mobile terminal.(String), 27.如权利要求26所述的装置,还包括功能执行单元执行检测到的功能。(String), 1(Integer), 23(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 25. The function input apparatus of claim 18, further comprising:a display unit displaying information to a user; anda user input unit receiving an input from a user,wherein, when two or more functions corresponds to the recognized grip posture, the display unit displays the functions corresponding to the recognized grip posture and the user input unit receives a function that the user wants to perform among the displayed functions.(String), 28.一种移动终端的功能输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:接收来自移动终端上的多个触摸传感器的输出信号;和利用触摸传感器的输出信号识别握持姿势,其中,利用输出信号识别握持姿势包括:将移动终端的表面分成多个部分;使用传感器输出信号检测移动终端的每个部分中的接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及检测到的接触点的总宽度;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及移动终端的每个部分中检测到的接触点的总宽度来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。29、一种移动终端功能的输入方法,该方法包括:识别用户握持移动终端的握持姿势,其中,识别的握持姿势为多种握持姿势中的一种;和检测与识别的握持姿势对应的功能,其中,识别握持姿势包括:将移动终端的表面分成多个部分;检测接触点的个数,每个检测到的接触点的接触宽度,相邻接触点之间的距离,以及移动终端各部分检测到的接触点的总宽度;和使用检测到的接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及移动终端的每个部分中检测到的接触点的总宽度来确定用户的握持姿势,其中使用至少一个计算机系统执行该方法,并且其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 24(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 26. A function input apparatus, the apparatus comprising:a sensor unit having a plurality of touch sensors individually detecting a user's contact with the mobile terminal, the detected contact defining a detected grip posture;a grip posture recognition unit to recognize a grip posture based on the detected grip posture from the sensor unit, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture,wherein the grip posture recognition unit comprises:a characteristic extraction unit to extract characteristic data of a detected grip posture; anda memory search unit to search a memory and to output as the recognized grip posture a grip posture which is defined in characteristic data stored in the memory that corresponds to the characteristic data of detected grip posture,wherein the characteristic data comprises a number of contact points in each portion, a contact width of each detected contact point, and a distance between adjacent contact points in each portion, which are used to determine the user's grip posture, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 30.一种包含在移动终端中的功能输入装置,该装置包括:握持姿势识别单元,用于识别用户握持移动终端的握持姿势,其中识别出的握持姿势是多种握持姿势中的一种;和功能检测单元,用于检测对应于识别的握持姿势的功能,其中,所述握持姿势识别单元包括:多个触摸传感器;接触检测单元,用于基于来自单独部分中的触摸传感器的输出信号来检测用户是否接触移动终端的表面被划分成的单独部分;和握持姿势确定单元,使用每个部分的检测结果来确定用户的握持姿势,其中,接触检测单元检测接触点的数量、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及每个部分中检测到的接触点的总宽度,并且抓握姿势确定单元确定用户的抓握使用检测到的接触点数量的姿势、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及每个部分检测到的接触点的总宽度,以及其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 0(Integer), 25(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 27. The apparatus of claim 26, further comprising a function performing unit performing the detected function.(String), 31.一种功能输入装置、装置包括:传感器单元具有多个单独检测用户与移动终端的接触的触摸传感器,检测到的接触定义检测到的握持姿势;抓握姿势识别单元基于从传感器单元检测到的抓握姿势来识别抓握姿势,其中识别出的抓握姿势是多个抓握姿势之一;和功能检测单元,用于检测识别出的握持姿势对应的功能,其中,所述握持姿势识别单元包括:特征提取单元,用于提取检测到的握持姿势的特征数据;和存储器检索部,检索存储器,输出与检测出的握持姿势的特征数据对应的存储在存储器中的特征数据中定义的握持姿势,作为识别出的握持姿势,其中,特征数据包括每个部分的接触点个数、每个检测到的接触点的接触宽度、相邻接触点之间的距离以及每个部分检测到的接触点的总宽度,用于判断用户的握持情况。姿势,和其中,识别出的握持姿势改变了移动终端屏幕的功能和显示方向。(String), 1(Integer), 26(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 28. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing a grip posture comprises:receiving output signals from a plurality of touch sensors on the mobile terminal; andrecognizing the grip posture using the output signals from the touch sensors, wherein the recognizing the grip posture using the output signals comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal using the sensor output signals; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, the distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 27(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 29. A method of inputting a function of a mobile terminal, the method comprising:recognizing a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anddetecting a function corresponding to the recognized grip posture,wherein the recognizing the grip posture comprises:dividing the surface of the mobile terminal into a plurality of portions;detecting a number of contact points, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal; anddetermining the user's grip posture using the detected number of contact points, the contact width of each detected contact point, the distance between adjacent contact points, and a total width of detected contact points in each portion of the mobile terminal,wherein the method is performed using at least one computer system, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 28(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 30. A function input apparatus included in a mobile terminal, the apparatus comprising:a grip posture recognition unit to recognize a grip posture of a user gripping the mobile terminal, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture,wherein the grip posture recognition unit comprises:a plurality of touch sensors;a contact detection unit to detect whether the user contacts individual portions into which the surface of the mobile terminal is divided based on output signals from touch sensors in the individual portions; anda grip posture determining unit to determine the user's grip posture using the detection result for each portion,wherein the contact detection unit detects a number of contact points, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion, and the grip posture determining unit determines the user's grip posture using the detected number of contact points, the contact width of each detected contact point, the distance between adjacent contact points, and a total width of detected contact points at each portion, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 29(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:06.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185951(Integer), 31. A function input apparatus, the apparatus comprising:a sensor unit having a plurality of touch sensors individually detecting a user's contact with the mobile terminal, the detected contact defining a detected grip posture;a grip posture recognition unit to recognize a grip posture based on the detected grip posture from the sensor unit, wherein the recognized grip posture is one of a plurality of grip postures; anda function detection unit to detect a function corresponding to the recognized grip posture, wherein the grip posture recognition unit comprises:a characteristic extraction unit to extract characteristic data of a detected grip posture; anda memory search unit to search a memory and to output as the recognized grip posture a grip posture which is defined in characteristic data stored in the memory that corresponds to the characteristic data of detected grip posture,wherein the characteristic data comprises a number of contact points in each portion, a contact width of each detected contact point, a distance between adjacent contact points, and a total width of detected contact points in each portion, which are used to determine the user's grip posture, andwherein the recognized grip posture changes function and display orientation of a screen of the mobile terminal.(String), 0(Integer), 30(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185951(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application claims the priority of Korean Patent Application No. 10-2005-0056933, filed on Jun. 29, 2005, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method and apparatus for receiving a desired function from a user in a mobile terminal such as a mobile phone, and more particularly, to a method and apparatus for inputting a function of a mobile terminal, in which a grip posture of a user who holds the mobile terminal is recognized and a function corresponding to the recognized grip posture is executed. [0004]2. Description of Related Art [0005]Typically, when using a mobile terminal, a user selects a function such as making a phone call, or sending or receiving a text message, and inputs Korean characters, English characters and numbers using a plurality of buttons included in the mobile terminal. [0006]Recent mobile terminals such as mobile phones have developed to combine the typical main functions of the mobile terminals, which include a phone call and a text message function, with another electronic machine functions. For instance, mobile phones now have various functions such as an MP3 file playing function of an MP3 player, an image recording and viewing function of a digital camera, a digital dictionary function, and a digital TV function. [0007]An increase in functions of mobile terminals usually results in an increase in price, size and complexity, which is not desirable to users. Therefore, it is important to keep the device size as small as possible while maximizing the number of device functions. [0008]Even when it is not difficult to add various functions to mobile terminals or miniaturize the devices for the mobile terminals with the development of technology, technical problems to be solved for providing a user interface that allows users to promptly and easily input complicated functions and control the terminal are increased. For example, a user interface that reduces key input steps necessary for performing a specific function, or easily managing, searching and playing a number of digital contents such as pictures, browsing images, music contents, e-mails, and the like is required. [0009]For instance, to download the latest music ringtones by accessing the Internet wireless using a mobile phone, a user presses a wireless Internet access button, selects, for example, a My Phone Bell menu after accessing the wireless Internet, then selects a Ringtones menu which is a sub menu of the My Phone Bell menu, and finally selects the Latest Ringtones menu which is a sub menu of the Ringtones menu. In this case, the user needs to press buttons a total of four times. [0010]In the case of a mobile terminal, an increase in the number of buttons for inputting a plurality of functions as described above may be impossible due to the limited size of the terminal, and can make a user input operation complicated. Moreover, when the number of buttons for key input is not increased, the number of key pressing times for selecting a specific function is increased. BRIEF SUMMARY [0011]An aspect of the present invention provides a method and apparatus for inputting a function of the mobile terminal in which general grip postures of a user holding the mobile terminal are recognized and a function corresponding to each grip posture is automatically performed without any additional operation such as a key input operation. [0012]According to an aspect of the present invention, there is provided a method of inputting a function of a mobile terminal, the method including: recognizing a grip posture of a user gripping the mobile terminal; detecting a function corresponding to the recognized grip posture; and performing the detected function. [0013]The recognizing of the grip posture may include: receiving output signals from a plurality of touch sensors formed on the mobile terminal; and recognizing the grip posture of the user using the output signals from the touch sensors. [0014]The plurality of touch sensors may be arranged on a surface of the mobile terminal at regular intervals, or the surface of the mobile terminal may be divided into a plurality of portions, and then the plurality of touch sensors may be arranged in each portion of the mobile terminal at different intervals according to how frequently the user touches each portion of the mobile terminal when the user holds the mobile terminal. [0015]The plurality of portions of the mobile terminal may include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side of the mobile terminal. The recognizing of the grip posture using the sensor output signals may comprise: dividing the surface of the mobile terminal into a plurality of portions; detecting at least one of the number of contact points, the contact width, and a distance between adjacent contact points in each portion of the mobile terminal using the sensor output signals; and determining the user's grip posture using at least one of the detected number of contact points, the contact width, and a distance between adjacent contact points in each portion of the mobile terminal. [0016]In the recognizing of the grip posture using the sensor output signals, the user's grip posture may be recognized from the sensor output signals by using one of an artificial neuron network, a template matching, a hidden Markov model, and an SVM (support vector machine). [0017]The recognizing of the grip posture may include: dividing the surface of the mobile terminal into a plurality of portions; detecting at least one of the number of contact points, a contact width, and a distance between adjacent contact points in each portion of the mobile terminal; and determining the user's grip posture using at least one of the detected number of contact points, a contact width, and a distance between adjacent contact points in each portion of the mobile terminal. [0018]The plurality of portions of the mobile terminal may include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side of the mobile terminal. The grip posture may include at least one of a right hand/horizontal grip, a right hand/vertical grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/vertical grip, and a left hand/vertical grip. [0019]A function corresponding to the recognized grip posture may be a phone call function when the recognized grip posture is a right hand/vertical grip, a text input function when the recognized grip posture is a both hands/vertical grip, a photography function when the recognized grip posture is a right hand/horizontal grip, or a game function when the recognized grip posture is a both hands/horizontal grip. [0020]The detecting of the function may include detecting one of the functions corresponding to the recognized grip based on at least one of the key input and the current function of the mobile terminal. [0021]If two or more functions correspond to the recognized grip posture, the method may further include: displaying the functions; and receiving a function that the user wants to perform among the displayed two or more functions. [0022]According to another aspect of the present invention, there is provided a function input apparatus included in a mobile terminal, the apparatus including: a grip posture recognition unit recognizing a grip posture of a user gripping the mobile terminal; a function detection unit detecting a function corresponding to the recognized grip posture; and a function performing unit performing the detected function. [0023]The grip posture recognition unit may include a plurality of touch sensors, and recognize the user's grip posture using output signals of the touch sensors. [0024]The plurality of touch sensors may be arranged on the surface of the mobile terminal at regular intervals, or the surface of the mobile terminal may divided into a plurality of portions, and then the plurality of touch sensors may be arranged on each portion of the mobile terminal at different intervals according to how frequently the user touches each portion of the mobile terminal when the user holds the mobile terminal. [0025]The plurality of portions of the mobile terminal may include a front side, a rear side, an upper portion, a bottom portion, a left side and a right side of the mobile terminal. [0026]The grip posture recognition unit may include: a contact detection unit detecting at least one of the number of contact points, a contact width, and a distance between adjacent contact points in each portion; and a grip posture determining unit determining the user's grip posture using at least one of the detected number of contact points, the contact width, and the distance between adjacent contact points at each portion. [0027]The grip posture recognition unit may recognize the user's grip posture from the sensor output signals using one of an artificial neuron network, a template matching, a hidden Markov model, and an SVM. [0028]The grip posture may include at least one of a right hand/horizontal grip, a right hand/vertical grip, a both hands/horizontal grip, a both hands/vertical grip, a left hand/horizontal grip, and a left hand/vertical grip. [0029]A function corresponding to the recognized grip posture may be a phone call function when the recognized grip posture is a right hand/vertical grip, a text input function when the recognized grip posture is a both hands/vertical grip, a photography function when the recognized grip posture is a right hand/horizontal grip, or a game function when the recognized grip posture is a both hands/horizontal grip. [0030]The function detection unit may receive a key input from a user for determine a current function of the mobile terminal when more than one functions are selected by the user's hand grip pattern. Then, the function is determined by combining the key input and the current recognized hand grip pattern. [0031]The function input apparatus may further include: a display unit displaying information to a user; and a user input unit receiving an input from a user, wherein, when two or more functions corresponds to the recognized grip posture, the display unit displays the functions corresponding to the recognized grip posture and the user input unit receives a function that the user wants to perform among the displayed two or more functions from the user. [0032]According to another aspect of the present invention, there is provided a function input apparatus, the apparatus including: a sensor unit having a plurality of touch sensors individually detecting a user's contact with the mobile terminal, the detected contact defining a detected grip posture; a grip posture recognition unit recognizing a grip posture based on the detected grip posture from the sensor unit; and a function detection unit detecting a function corresponding to the recognized grip posture. [0033]The apparatus may further include a function performing unit performing the detected function. [0034]The grip posture recognition unit may include: a characteristic extraction unit extracting characteristic data of a detected grip posture; and a memory search unit searching a memory and outputting as the recognized grip posture a grip posture which is defined in characteristic data stored in the memory that corresponds to the characteristic data of detected grip posture. [0035]Other aspects of the present invention provide computer-readable recording media storing programs for executing the aforementioned methods of the present invention. [0036]Additional and/or other aspects and advantages of the present invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention BRIEF DESCRIPTION OF THE DRAWINGS [0037]The above and/or other aspects and advantages of the present invention will become apparent and more readily appreciated from the following detailed description, taken in conjunction with the accompanying drawings of which: [0038]FIG. 1 is a flowchart illustrating a method of inputting a function into a mobile terminal according to an embodiment of the present invention; [0039]FIGS. 2A and 2B are diagrams for explaining arrangements of touch sensors included in a mobile terminal; [0040]FIG. 3 is a view for explaining a method of dividing user's hands into a plurality of portions for defining a user's grip posture; [0041]FIGS. 4A, 4B, 4C and 4D are views illustrating user's grip postures when holding the mobile terminal; [0042]FIG. 5 is a diagram for explaining a method of defining contact points of the mobile terminal according to the user's grip posture; [0043]FIG. 6 is a flowchart illustrating a function detecting operation of FIG. 1; [0044]FIG. 7 is a block diagram of a function input apparatus of a mobile terminal according to an embodiment of the present invention; and [0045]FIG. 8 is a block diagram of a grip posture recognition unit of the function input apparatus shown in FIG. 7. DETAILED DESCRIPTION OF EMBODIMENTS [0046]Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below to explain the present invention by referring to the figures. [0047]FIG. 1 is a flowchart illustrating a method of inputting a function into a mobile terminal according to an embodiment of the present invention. The method illustrated in FIG. 1 will be, for ease of explanation only, described in connection with FIG. 7, which is a block diagram of a function input apparatus included in a mobile terminal according to an embodiment of the present invention. [0048]Referring to FIGS. 1 and 7, when a user holds the mobile terminal for use, a plurality of touch sensors included in a sensor unit 700 individually detect whether the user touches the mobile terminal and output signals corresponding to the detection results (operation 100). The plurality of touch sensors may be arranged on a surface of the mobile terminal at regular intervals. Alternatively, the surface of the mobile terminal can be divided into several portions, and the touch sensors may be arranged in each portion at different intervals according to the user touch frequency in each portion. Since the average width of an adult's finger is 15 mm, a unit used for each touch sensor sensing whether the user touches the mobile terminal can be, by way of a limiting example, less than about 15 mm. [0049]FIG. 2A is a diagram for explaining an approach of dividing the surface of the mobile terminal for the arrangement of the touch sensors. The surface of the mobile terminal is divided into several portions, that is, a front side 200, a rear side 210, an upper portion 220, a bottom portion 230, a left side 250, and a right side 240. The intervals at which the touch sensors are arranged on the plurality of portions divided as described above are set as follows. [0050]The touch frequency on each portion when the user holds the mobile terminal is detected, and the touch sensors are arranged on the frequently touched portions at relatively small intervals and the touch sensors are arranged on the less frequently touched portions at relatively large intervals. For example, the upper portion 220 and the bottom portion 230 are less touched when the user holds the mobile terminal, and thus, the touch sensors are arranged at relatively larger intervals on the upper portion 220 or the bottom portion 230. Meanwhile, since the left and right sides 240 and 250 are frequently touched, the touch sensors may be arranged at relatively smaller intervals in these regions. [0051]The touch frequency on each divided portion may be determined when a user experimentally holds the mobile terminal to perform all functions available in the mobile terminal several times. [0052]FIG. 2B is a diagram for explaining another approach of dividing the surface of the mobile terminal into a plurality of portions for the arrangement of the touch sensors. The surface of the mobile terminal is divided into a liquid crystal display (LCD) 260, a front side 270, a first rear side portion 280, a second rear side portion 290, a third rear side portion 295, an upper portion 220, a bottom portion 270, a left side 250, and a right side 260. As shown in FIG. 2B, when the surface of the mobile terminal is divided into more portions and the intervals between the touch sensors arranged on each portion are adjusted according to the touch frequency, the touch sensors can be more efficiently used. [0053]A grip posture recognition unit 710 receives output signals from the touch sensors of the sensor unit 700, and recognizes a grip posture of a user who holds the mobile terminal (operation 110). FIG. 8 is a block diagram of the grip posture recognition unit 710. The grip posture recognition unit 710 includes a characteristic extraction unit 800, a memory search unit 810, and a memory 820. [0054]The characteristic extraction unit 800 extracts characteristic data of the grip posture of the user who holds the mobile terminal using the sensor output signals received from the sensor unit 700. The memory 820 stores characteristic data defining the grip postures. The memory search unit 810 searches the memory 820, and outputs as the user's grip posture a grip posture which is defined in the characteristic data stored in the memory 820 and identical to the characteristic data of the user's grip posture that is extracted by the characteristic extraction unit 800. A method of defining the characteristic data of each of the grip postures will be described below. [0055]FIG. 3 illustrates views for explaining an approach of dividing both hands of a user into a plurality of portions for defining grip postures. Each hand is divided into six portions (L1-L6 for the left hand and R1-R6 for the right hand). A grip posture may be defined according to which portions of each hand shown in FIG. 3 touch which portions of the mobile terminal shown in FIG. 2A or 2B. [0056]FIG. 4A illustrates a right hand of the user who is vertically holding the mobile terminal. Table 1 shows which portions of the right hand touch which portions of the mobile terminal. [0057]TABLE 1UpperBottomLeftRightRearportionportionsidesidesideR11R2R31R41R51R6 [0058]In Table 1, the portions of the hands and the mobile terminal marked with ‘1’ are the portions which are in contact with each other. Referring to Table 1, a right hand/vertical grip posture is defined as a pattern where the thumb (R1) of the right hand of the user contacts the right side of the mobile terminal and a middle finger R3, a third finger R4, and a pinky finger R5 of the right hand contact the left side. [0059]The grip posture may be further defined by portions of the hand and the mobile terminal which can contact each other depending on circumstances as shown in Table 2. In table 2, the portions of the right hand that can touch the portions of the mobile terminal depending on circumstances are further marked by ‘*’, which can be added to define the right hand/vertical grip posture of Table 1. [0060]TABLE 2UpperBottomLeftRightRearportionportionsidesidesideR11R2*R31R41R51R6* [0061]Referring to Table 2, the right hand/vertical grip posture may be further defined as a pattern where a forefinger R2 of the right hand can contact the left side of the mobile terminal and a palm R6 of the right hand can contact the right side, in addition to the contacting portions defined in Table 1. [0062]The grip posture defined by combination of the contacting portions of the hand contacting portions of the mobile terminal may be defined by the number of contact points in each portion of the mobile terminal, the width of each contact point, a distance between adjacent contact points, and the width of the contact points. By doing this, the characteristic data of the defined grip posture can be easily extracted from the output signals of the touch sensors. As shown in FIG. 5, it is assumed that, when there are two contact points 500 and 510, the respective widths of contact points 500 and 510 are K1 and K2, the distance between the adjacent contact points 500 and 510 is d12, and the total width of the contact points 500 and 510 is L. [0063]The right hand/vertical grip posture defined in Table 2 may be defined as shown in Table 3. [0064]TABLE 3UpperBottomLeftRightRearportionportionsidesidesideNumber of contact3 or 41 or 2pointsWidth of contact0.5 cm < k1 cm ⁢(X,Y)=X-Y=∑i=1n⁢(xi-yi)2(4) [0089]According to Equations 3 and 4, the input X is classified into a grip posture to which data Y* belongs. [0090]In yet another example of the present embodiment, a grip posture may be recognized using a hidden Markov model. The hidden Markov model is a set of states connected via transitions and output functions associated with each state. A model is composed of two kinds of probabilities: a transition probability needed for transition and an output probability indicating a conditional probability of observing an output symbol included in a finite alphabet at each state. Since similarity between an input pattern and a reference pattern is estimated, the hidden Markov model may provide a plurality of candidates. In addition, since temporal-spatial change is represented with probabilities in a state and a transition, it is not necessary to additionally consider the temporal-spatial change in the reference pattern during a matching process. [0091]Besides the above-described pattern recognition methods, other diverse pattern recognition methods may be used to recognize the user's grip posture using the sensor output signals. [0092]The function detection unit 720 receives the user's grip posture from the grip posture recognition unit 710, and detects a function corresponding to the grip posture (operation 120). A memory (not shown) may store functions corresponding to individual grip patterns recognizable by the grip posture recognition unit 710. The function detection unit 720 may search the memory to detect the function corresponding to the input user's grip posture. [0093]When using a phone call function, a user generally holds the mobile terminal vertically with a right hand as illustrated in FIG. 4B, and thus the right hand/vertical grip posture may correspond to the phone call function. [0094]When using a character input function to send a text message, the user generally holds the mobile terminal vertically with both hands as illustrated in FIG. 4C, and therefore the both hand/vertical grip posture may correspond to the character input function. [0095]When a user plays a game using the mobile terminal, the user typically holds the mobile terminal horizontally with both hands, and hence the both hands/horizontal grip posture may correspond to a game function. [0096]If two or more functions corresponding to the same grip posture are present, the functions may be stored in the memory. [0097]FIG. 6 is a flowchart illustrating an example of the function detecting operation (operation 120). Referring to FIG. 6, the function detection unit 720 searches for a function corresponding to the recognized grip type (operation 600). The function detection unit 720 checks if two or more functions has been found (operation 610). If there are two or more functions found, the function detection unit 720 displays names of the functions on an LCD (not shown) (operation 620). The function detection unit 720 receives a desired function selected from the displayed functions by a user using an input unit such as a keypad formed on the mobile terminal (operation 630). [0098]When the function detection unit 720 finds and outputs the function corresponding to the user's current grip type, the function performing unit 730 performs the detected function (operation 130). In the case of a phone call function, the function performing unit 730 may display a screen for inputting a phone number or searching stored phone numbers on an LCD formed on the mobile terminal. [0099]Embodiments of the present invention include computer-readable code on a computer-readable recording medium. The computer-readable recording medium is any data storage device that can store data which can be thereafter read by a computer system. Examples of the computer-readable recording medium include read-only memory (ROM), and random-access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, optical data storage devices. The computer-readable recording medium can also be distributed over network coupled computer systems so that the computer-readable code is stored and executed in (String), 相关申请的交叉引用 [0001] 本申请要求于2005年6月29日向韩国知识产权局提交的韩国专利申请No.10-2005-0056933的优先权,其公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明涉及一种在移动终端(例如手机)中从用户接收期望功能的方法和装置,更具体地,涉及一种用于输入移动终端的功能的方法和装置,其中握持姿势 识别持有移动终端的用户的姿势,并执行与识别的握持姿势对应的功能。 [0004] 2.相关技术说明 [0005] 通常,当使用移动终端时,用户选择诸如拨打电话或发送或接收文本消息的功能,并使用移动终端中包括的多个按钮输入韩文字符、英文字符和数字。 [0006] 最近的移动终端,例如手机,已经发展为将移动终端的典型主要功能,包括电话和短信功能,与另一种电子机器功能相结合。 例如,现在的手机具有多种功能,例如MP3播放器的MP3文件播放功能、数码相机的图像记录和查看功能、数字词典功能和数字电视功能。 [0007] 移动终端功能的增加通常会导致价格、尺寸和复杂性的增加,这是用户所不希望的。 因此,重要的是保持设备尺寸尽可能小,同时最大限度地增加设备功能的数量。 [0008] 即使随着技术的发展向移动终端添加各种功能或使移动终端的设备小型化并不困难,但提供用户界面以使用户能够快速轻松地输入复杂功能并控制移动终端的技术问题仍需解决。 终端增加。 例如,需要减少执行特定功能或容易地管理、搜索和播放诸如图片、浏览图像、音乐内容、电子邮件等的许多数字内容所需的键输入步骤的用户界面。 [0009] 例如,要通过手机无线上网下载最新的音乐铃声,用户按下无线上网按钮,在接入无线互联网后选择例如我的电话铃菜单,然后选择铃声菜单, 是我的电话铃菜单的子菜单,最后选择最新铃声菜单,它是铃声菜单的子菜单。 在这种情况下,用户总共需要按下按钮四次。 [0010] 在移动终端的情况下,由于终端的尺寸有限,如上所述增加用于输入多个功能的按钮的数量是不可能的,并且会使用户输入操作变得复杂。 此外,当用于键输入的按钮数量不增加时,用于选择特定功能的按键次数增加。 简要概述 [0011] 本发明的一方面提供了一种用于输入移动终端的功能的方法和设备,其中识别持有移动终端的用户的一般握持姿势,并且自动执行与每个握持姿势对应的功能,而无需任何附加操作,例如 一键输入操作。 [0012] 根据本发明的一个方面,提供了一种输入移动终端的功能的方法,该方法包括:识别用户握持移动终端的握持姿势; 检测与识别出的握持姿势对应的功能; 并执行检测到的功能。 [0013] 握持姿势的识别可以包括:接收来自移动终端上形成的多个触摸传感器的输出信号; 使用触控传感器的输出信号识别用户的握持姿势。 [0014]多个触摸传感器可以等间隔排列在移动终端的表面,也可以将移动终端的表面分割成多个部分,然后将多个触摸传感器分别排列在移动终端的每个部分。 当用户手持移动终端时,根据用户触摸移动终端各个部分的频率,移动终端的间隔不同。 [0015] 移动终端的多个部分可以包括移动终端的前侧、后侧、上部、底部、左侧和右侧。 使用传感器输出信号识别握持姿势可以包括: 将移动终端的表面划分为多个部分; 使用传感器输出信号检测移动终端的每个部分中的接触点的数量、接触宽度和相邻接触点之间的距离中的至少一项; 使用检测到的接触点的数量、接触宽度和移动终端的每个部分中相邻接触点之间的距离中的至少一种来确定用户的握持姿势。 [0016] 在使用传感器输出信号识别握持姿势时,可以通过使用人工神经元网络、模板匹配、隐马尔可夫模型和SVM(支持向量机)中的一种从传感器输出信号中识别用户的握持姿势。 )。 [0017] 握持姿势的识别可以包括:将移动终端的表面划分为多个部分; 检测移动终端各部分中接触点的数量、接触宽度和相邻接触点之间的距离中的至少一种; 使用检测到的接触点的数量、接触宽度和移动终端的每个部分中相邻接触点之间的距离中的至少一种来确定用户的握持姿势。 [0018] 移动终端的多个部分可以包括移动终端的前侧、后侧、上部、底部、左侧和右侧。 握持姿势可以包括右手/水平握持、右手/垂直握持、双手/水平握持、双手/垂直握持、左手/垂直握持和左手/垂直握持中的至少一种。 紧握。 [0019] 识别出的握持姿势对应的功能可以是识别出的握持姿势为右手/竖握时的电话功能,识别的握持姿势为双手/竖握时的文字输入功能,识别出的握持姿势时的拍照功能。 握持姿势是右手/水平握持,或者当识别的握持姿势是双手/水平握持时的游戏功能。 [0020] 功能的检测可以包括基于键输入和移动终端的当前功能中的至少一个来检测与识别的握持相对应的功能之一。 [0021] 如果识别出的握持姿势对应两个或多个功能,该方法还可以包括:显示功能; 接收所显示的两个或多个功能中用户想要执行的功能。 [0022] 根据本发明的另一方面,提供了一种包括在移动终端中的功能输入装置,该装置包括: 握持姿势识别单元,识别握持移动终端的用户的握持姿势; 功能检测单元检测与识别出的握持姿势对应的功能; 功能执行单元执行检测到的功能。 [0023] 握持姿势识别单元可以包括多个触摸传感器,并且使用触摸传感器的输出信号来识别用户的握持姿势。 [0024] 多个触摸传感器可以等间隔地设置在移动终端的表面,也可以将移动终端的表面分成多个部分,然后将多个触摸传感器设置在移动终端的各个部分上。 在用户手持移动终端时,根据用户触摸移动终端各个部分的频率,以不同的间隔设置终端。 [0025]移动终端的多个部分可以包括移动终端的前侧、后侧、上部、底部、左侧和右侧。 [0026] 握持姿势识别单元可以包括:接触检测单元,检测每个部分中的接触点的数量、接触宽度和相邻接触点之间的距离中的至少一个; 握持姿势确定单元使用检测到的接触点的数量、接触宽度和每个部分的相邻接触点之间的距离中的至少一个来确定用户的握持姿势。 [0027] 握持姿势识别单元可以使用人工神经元网络、模板匹配、隐马尔可夫模型和SVM中的一种从传感器输出信号中识别用户的握持姿势。 [0028] 握持姿势可以包括右手/水平握持、右手/垂直握持、双手/水平握持、双手/垂直握持、左手/水平握持和左手/垂直握持中的至少一种。 紧握。 [0029] 识别出的握持姿势对应的功能可以是识别出的握持姿势为右手/竖握时的电话功能,识别的握持姿势为双手/竖握时的文字输入功能,识别出的握持姿势时的拍照功能。 握持姿势是右手/水平握持,或者当识别的握持姿势是双手/水平握持时的游戏功能。 [0030] 当用户的手握模式选择了多个功能时,功能检测单元可以接收来自用户的键输入以确定移动终端的当前功能。 然后,通过组合键输入和当前识别的手握模式来确定功能。 [0031] 功能输入装置还可以包括:显示单元,向用户显示信息; 用户输入单元,接收来自用户的输入,其中,当识别出的握持姿势对应两个或更多功能时,显示单元显示与识别出的握持姿势对应的功能,并且用户输入单元接收用户想要的功能 在显示的用户的两个或多个功能中执行。 [0032] 根据本发明的另一方面,提供了一种功能输入装置,该装置包括: 传感器单元,具有多个触摸传感器,分别检测用户与移动终端的接触,检测到的接触定义检测到的握持姿势; 握持姿势识别单元基于从传感器单元检测到的握持姿势识别握持姿势; 功能检测部检测与识别出的把持姿势对应的功能。 [0033] 该设备还可以包括执行检测到的功能的功能执行单元。 [0034] 握持姿势识别单元可以包括:特征提取单元,提取检测到的握持姿势的特征数据; 存储器检索部检索存储器,将与检测出的握持姿势的特征数据对应的存储器中存储的特征数据中定义的握持姿势作为识别握持姿势输出。 [0035] 本发明的其他方面提供了存储用于执行本发明的上述方法的程序的计算机可读记录介质。 [0036] 本发明的附加和/或其他方面和优点将部分地在下面的描述中阐述,并且部分地从描述中显而易见,或者可以通过本发明的实践来了解 附图的简要说明 [0037] 本发明的上述和/或其他方面和优点将从以下结合附图的详细描述中变得明显和更容易理解,其中: [0038] 图1是示出根据本发明实施例的向移动终端输入功能的方法的流程图; [0039] 图2A和图2B是用于说明移动终端所具备的触摸传感器的配置的图。 [0040]图3是用于说明将用户的手分割成多个部分来定义用户的握持姿势的方法的图。 [0041] 图4A, 4 乙, 4 C 和 4 D是说明用户握持移动终端时的握持姿势的图; [0042] 图5是说明根据用户的握持姿势定义移动终端的接触点的方法的图。 [0043] 图6是说明图1的功能检测动作的流程图。 [0044] 图7是根据本发明实施例的移动终端的功能输入装置的框图。 和 [0045] 图8是图7所示的功能输入装置的握持姿势识别部的框图。 具体实施方式 [0046] 现在将详细参考本发明的实施例,其示例在附图中示出,其中相同的附图标记始终指代相同的元件。 下面通过参考附图描述实施例以解释本发明。 [0047] 图1是图示根据本发明实施例的将功能输入到移动终端的方法的流程图。 为了便于说明,将结合图7描述图1所示的方法,图7是根据本发明实施例的移动终端中包括的功能输入装置的框图。 [0048] 参照图1和图7,当用户手持移动终端使用时,传感器单元中包括的多个触摸传感器 700 单独检测用户是否触摸移动终端并输出与检测结果对应的信号(操作 100 )。 多个触摸传感器可以以规则的间隔布置在移动终端的表面上。 或者,也可以将移动终端的表面分成若干部分,根据用户在每一部分的触摸频率,将触摸传感器以不同的间隔排列在每一部分中。 由于成人手指的平均宽度为15mm,作为限制性示例,用于感测用户是否触摸移动终端的每个触摸传感器的单位可以小于约15mm。 [0049] 图2A是用于说明为了配置触摸传感器而划分移动终端的表面的方法的图。 移动终端的表面分为几个部分,即正面 200 , 背面 210 , 上部 220 , 底部 230 , 左侧 250 , 和右侧 240 . 将触摸传感器布置在如上所述划分的多个部分上的间隔设置如下。 [0050] 检测用户手持移动终端时各部位的触摸频率,将触摸传感器以较小的间距布置在频繁触摸的部分上,将触摸传感器以较大的间距布置在触摸频率较低的部分上。 例如,上半部分 220 和底部 230 用户手持移动终端时触摸较少,因此触摸传感器在上部的间距相对较大 220 或底部 230 . 同时,由于左右两侧 240 和 250 对于被频繁触摸的区域,触摸传感器可以以相对较小的间隔布置在这些区域中。 [0051] 每个划分部分的触摸频率可以在用户实验性地握持移动终端执行移动终端中的所有可用功能数次时确定。 [0052] 图2B是用于说明将移动终端的表面划分为多个部分以用于触摸传感器的布置的另一种方法的图。 移动终端的表面分为液晶显示器(LCD) 260 , 正面 270 ,第一后侧部分 280 ,第二后侧部分 290 ,第三后侧部分 295 , 上部220 , 底部 270 , 左侧 250 , 和右侧 260 . 如图2B所示,当移动终端的表面被划分为更多部分,并根据触摸频率调整设置在每个部分上的触摸传感器之间的间隔时,可以更有效地使用触摸传感器。 [0053] 握持姿势识别单元 710 接收来自传感器单元的触摸传感器的输出信号 700 ,并识别持有移动终端的用户的握持姿势(操作 110 )。 图8是握持姿势识别单元的框图 710 . 握持姿势识别单元 710 包括一个特征提取单元 800 , 一个内存搜索单元 810 , 和记忆 820 . [0054] 特征提取单元 800 使用从传感器单元接收的传感器输出信号,提取持有移动终端的用户的握持姿势的特征数据 700 . 记忆 820 存储定义握持姿势的特征数据。 内存搜索单元 810 搜索记忆 820 ,并且将在存储在存储器中的特征数据中定义的握持姿势作为用户的握持姿势输出 820 与特征提取单元提取的用户握持姿势的特征数据相同 800 . 下面将描述定义每个握持姿势的特征数据的方法。 [0055] 图3示出了用于解释将用户的双手分成多个部分以定义握持姿势的方法的视图。 每只手分为六个部分(L 1 -L 6 对于左手和 R 1 -R 6 右手)。 可以根据图3中所示的每只手的哪些部分触摸图2A中所示的移动终端的哪些部分或 2 B. [0056] 图4A图示了垂直握住移动终端的用户的右手。 表1显示了右手的哪些部分触摸了移动终端的哪些部分。 [0057] 表格1 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 1 R2 R3 1 R4 1 R5 1 R6 [0058] 在表1中,手和移动终端标有“1”的部分是相互接触的部分。 参考表 1,右手/垂直握持姿势定义为拇指(R 1 ) 用户右手接触移动终端右侧和中指R 3 , 第三个手指 R 4 , 和一个小指 R 5 右手接触左侧。 [0059] 握持姿势可以进一步由手和移动终端的可以根据情况相互接触的部分定义,如表2所示。在表2中,右手可以接触移动终端的部分的部分取决于 在情况下进一步用'*'标记,可以添加它来定义表1的右手/垂直握持姿势。 [0060] 表 2 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 1 R2 * R3 1 R4 1 R5 1 R6 * [0061] 参见表2,右手/竖握姿势可以进一步定义为食指R 2 右手可以接触到移动终端的左侧和手掌R 6 除了表 1 中定义的接触部分外,右手的手可以接触右侧。 [0062] 由移动终端的手接触部分的接触部分的组合定义的握持姿势可以由移动终端的每个部分中的接触点的数量、每个接触点的宽度、相邻接触点之间的距离、 和接触点的宽度。 通过这样做,可以容易地从触摸传感器的输出信号中提取定义的握持姿势的特征数据。 如图 5 所示,假设当有两个接触点时 500 和 510 , 各自的接触点宽度 500 和 510 是 K 1 和 K 2 , 相邻接触点之间的距离 500 和 510 是 d 12,以及接触点的总宽度 500 和 510 是 L。 [0063] 表 2 中定义的右手/垂直握持姿势可定义如表 3 所示。 [0064] 表3 上 底部 剩下 正确的 后部 部分 部分 边 边 边 联系人数量 3 or 4 1 or 2 积分 接触宽度 0.5 厘米 < k 1 厘米 < (k) 点 k < 10 厘米 总宽度 2 厘米 < 2 厘米 < 接触点 (L) 长 < 9.5 厘米 长 < 11 厘米 之间的距离 d < 3 厘米 d < 3 厘米 联络点(d) [0065] 图4B示出了水平握住移动终端的用户的右手。 在表 4 和表 5 中,定义了右手/水平握持姿势。 [0066] 表 4 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 * R2 1 R3 1 R4 * R5 R6 1 [0067] 表 5 上 底部 剩下 正确的 后部 部分 部分 边 边 边 数量 1 0 or 1 1 1 or 2 联络点 宽度 1 厘米 < 1 厘米 < 1 厘米 < 1 厘米 < 接触点 k < 4 k < 2.5 k < 3.5 k < 8 (k) 厘米 厘米 厘米 厘米 总宽度 1 厘米 < 1 厘米 < 1 厘米 < 1 厘米 < 联络点 L < 4 L < 2.5 L < 3.5 L < 10 (L) 厘米 厘米 厘米 厘米 距离 d < 2 之间 厘米 接触 (d) 点 [0068] 图4C示出了垂直握住移动终端的用户的双手。 在表6和表7中,定义了图4C所示的双手/垂直握持姿势。 [0069] 表 6 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 R2 * 1 R3 * 1 R4 * R5 R6 1 L1 L2 * 1 L3 * 1 L4 * L5 L6 1 [0070] 表 7 上 底部 剩下 正确的 后部 部分 部分 边 边 边 数量 1, 2 or 3 1, 2, or 4, 5, or 联络点 3 6 宽度 1 厘米 < 1 厘米 < 0.5 厘米 < 接触点 k < 10 厘米 k < 10 厘米 k < 10 厘米 (k) 总宽度 1 厘米 < 1 厘米 < 长 < 10 厘米 联络点 长 < 10 厘米 长 < 10 厘米 (L) 距离 0.5 厘米 < 0.5 厘米 < 0.5 厘米 < 之间 d < 8 厘米 d < 8 厘米 d < 7 厘米 接触 (d) 点 [0071] 图4D示出了水平握住移动终端的用户的双手。 在表8和表9中,定义了图4D所示的双手/水平握持姿势。 [0072] 表 8 上 底部 剩下 正确的 后部 部分 部分 边 边 边 R1 R2 * R3 1 R4 1 R5 R6 * L1 L2 * L3 1 L4 * L5 L6 * [0073] 表 9 上 底部 剩下 正确的 后部 部分 部分 边 边 边 数量 0 or 1 0 or 1 3-6 联络点 宽度 1 厘米 < 1 厘米 < 0.5 厘米 < 接触点 k < 4 厘米 k < 4 厘米 k < 7 厘米 (k) 总宽度 1 厘米 < 1 厘米 < 长 < 11 厘米 联系方式 长 < 4 厘米 长 < 4 厘米 点数 (L) 距离 0.5 厘米 < 之间 d < 9 厘米 联络点 (d) [0074] 如上所述定义的每个握持姿势的特征数据存储在存储器中 820 ,以及特征提取单元 800 提取用户当前握持姿势的特征数据,该特征数据与内存中存储的特征数据一致 820 ,来自接收到的传感器输出信号。 [0075] 特征提取单元 800 可以使用接收到的传感器输出信号提取每个部分中的接触点的数量、每个接触点的宽度、相邻接触点之间的距离以及接触点的总宽度。 [0076] 握持姿势识别单元 710 可以使用模式识别方法从接收到的传感器输出信号中识别用户的握持姿势。 [0077] 模式识别方法可以包括以下过程。 [0078] 首先,从用户那里收集大量关于 {input X, class C} 的数据。 然后,将收集到的数据分为学习数据和测试数据。 接下来,将学习数据提供给模式识别系统,并执行学习操作。 模式识别系统的模型参数根据学习数据而改变。 然后,只有输入 X 被提供给模式识别系统,因此系统输出 C 类。 [0079] 根据本实施例的示例,模式识别方法可以使用人工神经元网络。 人工神经元网络是通过简化生物的神经传递过程并对其进行数学分析而获得的模型。 在人工神经网络中,通过根据连接类型调整神经元之间连接的权重的学习过程来分析操作。 这个过程类似于人们学习和记忆的过程。 通过这个过程,可以进行推理、分类、预测等。 在人工神经网络中,一个神经元对应一个节点,神经元之间的连接强度对应于节点间弧上的权重。 人工神经网络可以是包括多个单层感知器的多层感知器神经网络并且可以使用反向传播学习来学习。 [0080] 反向传播学习是通过将 Widrow-Hoff 学习规则推广到多层网络和非线性可微传递函数来实现的,通常用于字符识别和非线性预测。 神经网络中的每个节点使用多个不同的可微传递函数之一来生成输出。 公式 1 中所示的对数 sigmoid 传递函数 (logsig) 使用最广泛。 [0081] f ⁡ ( x ) = 1 1 + ⅇ - x ( 1 ) [0082] 该函数根据从负无穷到正无穷的输入值输出一个从 0 到 1 的值。 在使用反向传播算法减小期望输出值和实际输出值之间的偏差的同时学习期望函数。 [0083]当从传感器输出的信号输入到人工神经网络输入层上的节点时,信号在每个节点中发生变化,然后传输到中间层。 以同样的方式,信号被传输到最后一层,输出一个运动模式。 节点之间的连接强度(以下称为“节点连接强度”)被调整为使得从人工神经网络输出的激活值与在学习期间为各个模式定义的激活值之间的差异减小。 另外,根据delta学习规则,下层根据上层的反向传播结果来调整节点连接强度,以使误差最小化。 根据增量学习规则,调整节点连接强度,使得输入/输出函数最小化目标输出与从包括非线性神经元在内的网络中的所有单个输入模式获得的输出之间的误差平方和。 [0084] 在通过上述学习过程学习所有预定握持姿势后,人工神经网络接收来自传感器单元的运动信号 700 (图7)并将该信号识别为预定握持姿势之一。 [0085] 必要时,可以根据用户的选择操作人工神经网络以重新学习握持姿势。 例如,当用户选择要重新学习的握持姿势并多次做出与选择的握持姿势对应的动作时,人工神经网络可以重新学习反映用户做出的动作的握持姿势。 [0086] 在本实施例的另一示例中,可以使用SVM(支持向量机)来识别用户的握持姿势。 这里,N维向量空间由运动信号的N维特征形成。 在根据学习数据找到合适的超平面后,可以使用超平面对模式进行分类。 每个模式都可以由公式 2 定义。 类=1 如果 W T X+b≥ 0 类=0 如果 W T X+b< 0  (2) 其中 W 是权重矩阵,X 是输入向量,b 是偏移量。 [0087] 在本实施例的又一示例中,可以使用模板匹配来识别握持姿势。 在这种情况下,在从学习数据中选择用于分类握持姿势的模板数据之后,找到与当前输入最接近的模板数据项,并将当前输入分类为与该模板数据项对应的握持姿势。 换句话说,关于输入数据 X=P(x 1 , . . . X n ) 和第 i 个数据项 Y i =P(y 1 , . . . 是的 n ) 在学习数据中,Y* 可以定义为 Y *=分钟 i 距离( X,Y i )  (3) 其中距离 (X, Y) 可以使用 [0088] Distance ⁢ ⁢ ( X , Y ) = X - Y = ∑ i = 1 n ⁢ ( x i - y i ) 2 ( 4 ) [0089] 根据等式3和4,输入X被分类为数据Y*所属的握持姿势。 [0090] 在本实施例的又一示例中,可以使用隐马尔可夫模型来识别握持姿势。 隐马尔可夫模型是一组通过与每个状态相关的转换和输出函数连接的状态。 模型由两种概率组成:转移所需的转移概率和指示在每个状态下观察包含在有限字母表中的输出符号的条件概率的输出概率。 由于估计输入模式和参考模式之间的相似性,隐马尔可夫模型可以提供多个候选。 另外,由于时间-空间变化是用状态和转移的概率来表示的,所以在匹配过程中不需要额外考虑参考模式的时间-空间变化。 [0091] 除了上述模式识别方法之外,其他多种模式识别方法可以用于使用传感器输出信号来识别用户的握持姿势。 [0092] 功能检测单元 720 从握持姿势识别单元接收用户的握持姿势 710,并检测与握持姿势对应的功能(操作 120 )。 存储器(未示出)可以存储与握持姿势识别单元可识别的各个握持模式相对应的功能 710 . 功能检测单元 720 可以搜索内存以检测与输入的用户的握持姿势对应的功能。 [0093] 在使用电话功能时,用户一般如图4B所示用右手垂直握持移动终端,因此右手/垂直握持姿势可以对应电话功能。 [0094] 在使用字符输入功能发送短信时,用户一般如图4C所示,双手垂直握持移动终端,因此双手/垂直握持姿势可以对应字符输入功能。 [0095] 当用户使用移动终端玩游戏时,用户通常双手水平握持移动终端,因此双手/水平握持姿势可以对应游戏功能。 [0096] 如果存在对应于相同握持姿势的两个或更多个功能,则可以将这些功能存储在存储器中。 [0097] 图6是表示功能检测动作的一个例子的流程图(动作 120 )。 参见图6,功能检测单元 720 搜索与识别的握持类型对应的功能(操作 600 )。 功能检测单元 720 检查是否找到了两个或多个函数(操作 610 )。 如果发现两个或更多功能,功能检测单元 720 在 LCD 上显示功能名称(未显示)(操作 620 )。 功能检测单元 720 接收用户使用移动终端上形成的键盘等输入单元从显示的功能中选择的所需功能(操作 630 )。 [0098] 当功能检测单元 720 查找并输出用户当前握持类型对应的功能,功能执行单元 730 执行检测到的功能(操作 130 )。 在电话功能的情况下,功能执行单元 730 可以在移动终端上形成的LCD上显示用于输入电话号码或搜索存储的电话号码的屏幕。 [0099] 本发明的实施例包括计算机可读记录介质上的计算机可读代码。 计算机可读记录介质是可以存储数据的任何数据存储设备,该数据随后可以被计算机系统读取。 计算机可读记录介质的示例包括只读存储器(ROM)和随机存取存储器(RAM)、CD-ROM、磁带、软盘、光学数据存储设备。 计算机可读记录介质还可以分布在网络耦合的计算机系统上,使得计算机可读代码以分布式方式存储和执行。 [0100] 根据本发明的上述实施例,在使用用户的握持姿势在移动终端中输入功能的装置和方法中,考虑了在执行诸如移动电话的移动终端的功能时形成的用户握持姿势 ,具体功能分别与多种握持姿势相匹配。 当用户手持移动终端时,识别用户的握持姿势,并自动执行与识别的握持姿势对应的功能,而无需任何额外的操作,例如按键输入操作。 因此,即使当移动终端提供多种功能时,也不需要复杂的输入单元或输入方法,并且用户可以容易且方便地使用移动终端。 [0101] 尽管已经示出和描述了本发明的几个实施例,但是本发明不限于所描述的实施例。 相反,本领域技术人员应当理解,可以对这些实施例进行改变而不背离本发明的原理和精神,本发明的范围由权利要求及其等同物限定。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100668341B1(String), KR1020070001440A(String), US20070002016A1(String), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100668341B1(String), KR1020070001440A(String), US20070002016A1(String), US8055305B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100668341B1(String), KR1020070001440A(String), US20070002016A1(String), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.807 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.807 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.807 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271649(Integer), KR100668341B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271649(Integer), KR1020070001440A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271649(Integer), US20070002016A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271649(Integer), US8055305B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8055305B2(String), US8055305B2(String), 1320681600(Integer), 271649(Integer), 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:07.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185951(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185951(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185951(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185951(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7561063B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminals including location management systems and location management methods for mobile terminals(String), 移动终端,包括位置管理系统和移动终端的位置管理方法(String), US7561063B2(String), Methods of managing a location of a mobile terminal include obtaining a position of the mobile terminal, estimating a distance from the mobile terminal to a destination point, generating an estimated time for the mobile terminal to reach the destination point, and generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. Related mobile terminals are also disclosed.(String), 管理移动终端位置的方法包括获取移动终端的位置、估计从移动终端到目的地点的距离、生成移动终端到达目的地点的估计时间、以及如果发生移动终端则生成警报。 移动终端到达目的地点的估计时间达到阈值时间。 还公开了相关的移动终端。(String), US11/714053(String), 1173024000(Integer), US7561063B2(String), 1247500800(Integer), 1247500800(Integer), 美国(String), 4(Integer), 11(Integer), 8(Integer), US20030060979A1 | US20050165543A1 | US5790974A | US6360101B1 | US6958692B1 | WO2001029512A1 | WO2002015148A1 | WO2002071365A1(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:08.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\993ddc9dbda447c2a6ec064637617fcb.png(String), 185952(Integer), 993ddc9dbda447c2a6ec064637617fcb.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminals including location management systems and location management methods for mobile terminals(String), 移动终端,包括位置管理系统和移动终端的位置管理方法(String), US7561063B2(String), Methods of managing a location of a mobile terminal include obtaining a position of the mobile terminal, estimating a distance from the mobile terminal to a destination point, generating an estimated time for the mobile terminal to reach the destination point, and generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. Related mobile terminals are also disclosed.(String), 管理移动终端位置的方法包括获取移动终端的位置、估计从移动终端到目的地点的距离、生成移动终端到达目的地点的估计时间、以及如果发生移动终端则生成警报。 移动终端到达目的地点的估计时间达到阈值时间。 还公开了相关的移动终端。(String), US11/714053(String), 1173024000(Integer), US7561063B2(String), 1247500800(Integer), 1247500800(Integer), 美国(String), 3(Integer), 4(Integer), 11(Integer), 8(Integer), US20030060979A1 | US20050165543A1 | US5790974A | US6360101B1 | US6958692B1 | WO2001029512A1 | WO2002015148A1 | WO2002071365A1(String), \20230420\993ddc9dbda447c2a6ec064637617fcb.png(String), 17(Integer), 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 1. A method of managing a location of a mobile terminal, comprising:obtaining a position of the mobile terminal measuring a current speed of the mobile terminal;estimating a distance from the mobile terminal to a destination point wherein estimating the distance from the mobile terminal to a destination point comprises generating a route between the position of the mobile terminal and the destination point based on a movement constraint of the mobile terminal;generating an estimated time for the mobile terminal to reach the destination point wherein generating the estimated time for the mobile terminal to reach the destination point comprises generating the estimated time in response to the current speed of the mobile terminal and the generated route; andgenerating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time.(String), 1.一种移动终端位置管理方法,包括:获取移动终端的位置,测量移动终端的当前速度;估计移动终端到目的地点的距离其中,估计移动终端到目的地点的距离包括基于移动终端的移动约束生成移动终端的位置和目的地点之间的路线;生成移动终端到达目的地点的预估时间,其中生成移动终端到达目的地点的预估时间包括响应于移动终端的当前速度和生成的路线生成预估时间;和如果移动终端到达目的地点的估计时间达到阈值时间,则生成警报。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 2. The method of claim 1, wherein generating the route is performed in response to an operational mode of the mobile terminal.(String), 2.如权利要求1所述的方法,其中生成路线是响应于移动终端的操作模式而执行的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 3. The method of claim 2, wherein the operational mode comprises a pedestrian operational mode, and wherein the movement constraint comprises at least one of a building, a bridge, a gate, or a fence.(String), 3.如权利要求2所述的方法,其中操作模式包括行人操作模式,并且其中运动限制包括建筑物、桥梁、大门或栅栏中的至少一个。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 4. The method of claim 2, wherein the operational mode comprises a vehicular operational mode, and wherein the movement constraint comprises a road.(String), 4.如权利要求2所述的方法,其中操作模式包括车辆操作模式,并且其中移动约束包括道路。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 5. The method of claim 1, wherein generating the estimated time for the mobile terminal to reach the destination point comprises generating the estimated time assuming the mobile terminal travels the route at an average speed and/or at a maximum speed.(String), 5.如权利要求1所述的方法,其中生成移动终端到达目的地点的估计时间包括假设移动终端以平均速度和/或最大速度行进路线来生成估计时间。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 6. The method of claim 1, further comprising:obtaining traffic information indicative of traffic in an area between the mobile terminal and the destination point;wherein generating the estimated time for the mobile terminal to reach the destination point comprises generating the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point.(String), 6.如权利要求1所述的方法,还包括:获取指示移动终端和目的地点之间的区域中的交通的交通信息;其中生成移动终端到达目的地点的估计时间包括响应于移动终端的位置和目的地点之间的区域中的交通生成估计时间。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 7. The method of claim 6, wherein generating the route comprises generating a quickest route between the position of the mobile terminal and the destination point in response to the traffic in the area between the mobile terminal and the destination point.(String), 7.如权利要求6所述的方法,其中生成路线包括响应于移动终端和目的地点之间的区域中的交通生成移动终端的位置和目的地点之间的最快路线。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 8. The method of claim 1, wherein generating the alert comprises generating the alert if the estimated time for the mobile terminal to reach the destination point exceeds the threshold time.(String), 8.如权利要求1所述的方法,其中生成警报包括如果移动终端到达目的地点的估计时间超过阈值时间则生成警报。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 9. The method of claim 1, wherein generating the alert comprises generating the alert if the estimated time for the mobile terminal to reach the destination point is less than the threshold time.(String), 9.如权利要求1所述的方法,其中生成警报包括如果移动终端到达目的地点的估计时间小于阈值时间则生成警报。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 10. The method of claim 1, further comprising displaying an information box associated with the mobile terminal, the information box comprising an estimated time for the mobile terminal to reach the destination point.(String), 10.如权利要求1所述的方法,还包括显示与移动终端相关联的信息框,该信息框包括移动终端到达目的地点的估计时间。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 11. The method of claim 1, further comprising dynamically updating the geo-temporal boundary in response to a passage of time.(String), 11.如权利要求1所述的方法,还包括动态更新地理时间边界以响应时间的流逝。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 12. A method of managing locations of a plurality of mobile terminals, comprising:obtaining positions of the plurality of mobile terminals measuring a current speed of the mobile terminal;estimating distances from the plurality of mobile terminals to a destination point wherein estimating the distances from the plurality of mobile terminals to a destination point comprises generating routes between the positions of the mobile terminals and the destination point based on movement constraints of the mobile terminals;generating estimated times for the mobile terminals to reach the destination point wherein generating the estimated times for the mobile terminals to reach the destination point comprises generating the estimated times in response to the current speeds of the mobile terminals and the generated routes; andgenerating an alert if the estimated time for at least one of the mobile terminals to reach the destination point reaches a threshold time.(String), 12.一种管理多个移动终端位置的方法,包括:测量移动终端的当前速度,获取多个移动终端的位置;估计多个移动终端到目的地点的距离其中,估计多个移动终端到目的地点的距离包括基于移动终端的移动约束生成移动终端的位置和目的地点之间的路线;生成移动终端到达目的地点的估计时间,其中生成移动终端到达目的地点的估计时间包括响应于移动终端的当前速度和生成的路线生成估计时间;和如果至少一个移动终端到达目的地点的估计时间达到阈值时间,则生成警报。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 13. A mobile terminal, comprisinga location management unit configured to obtain a position of a mobile terminal; anda controller configured to estimate a distance from the position of the mobile terminal to a destination point by generating a route between the position of the mobile terminal and the destination point based on a movement constraint of the mobile terminal, configured to measure a current speed of the mobile terminal, configured to generate an estimated time for the mobile terminal to reach the destination point in response to the current speed of the mobile terminal and the generated route, and configured to generate an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time.(String), 13.移动终端,包括位置管理单元,用于获取移动终端的位置;和控制器被配置为通过基于移动终端的移动约束生成移动终端的位置与目的地点之间的路线来估计从移动终端的位置到目的地点的距离,被配置为测量当前速度移动终端,用于响应于移动终端当前的速度和生成的路线,生成移动终端到达目的地点的预计时间,如果移动终端预计到达时间,则生成提醒目的点到达阈值时间。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 14. The mobile terminal of claim 13, further comprising:a traffic information unit configured to obtain traffic information indicative of traffic in an area between the position of the mobile terminal and the destination point;wherein the controller is further configured to generate the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point.(String), 14.如权利要求13所述的移动终端,还包括:交通信息单元,被配置为获取指示移动终端的位置和目的地点之间的区域中的交通的交通信息;其中,控制器还被配置为响应于移动终端的位置和目的地点之间的区域中的交通来生成估计时间。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 15. The mobile terminal of claim 13, wherein the controller is further configured to calculate a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and a rate of motion of the mobile terminal.(String), 15.如权利要求13所述的移动终端,其中控制器还被配置为响应于移动终端的位置、目的地点的位置和移动终端的运动速率来计算目的地点周围的时空边界。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 16. The mobile terminal of claim 13, further comprising a map database, wherein the controller is further configured to generate a route between the position of the mobile terminal and the destination point in response to map information stored in the map database.(String), 16.如权利要求13所述的移动终端,还包括地图数据库,其中,控制器还被配置为响应于存储在地图数据库中的地图信息生成移动终端的位置和目的地点之间的路线。(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185952(Integer), 17. A method of managing a location of a mobile terminal, comprising:obtaining a position of the mobile terminal;measuring a current speed of the mobile terminal;estimating a distance from the mobile terminal to a destination point;generating an estimated time for the mobile terminal to reach the destination point;generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time;calculating a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and the current speed of motion of the mobile terminal, wherein the geo-temporal boundary indicates a farthest distance that the mobile terminal can be from the destination point while still being less than the threshold time away from reaching the destination point; anddisplaying the geo-temporal boundary on a display screen of the mobile terminal.(String), 17.一种管理移动终端位置的方法,包括:获取移动终端的位置;测量移动终端的当前速度;估计从移动终端到目的地点的距离;生成移动终端到达目的地点的预计时间;如果移动终端到达目的地点的估计时间达到阈值时间,则产生警报;响应于移动终端的位置、目的地点的位置和移动终端的当前运动速度计算目的地点周围的时空边界,其中,时空边界表示距离移动终端最远的距离。移动终端可以在距离到达目的地点的距离小于阈值时间的情况下离开目的地点;和在移动终端的显示屏上显示时空边界。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185952(Integer), FIELD OF THE INVENTION [0001]The present invention relates to wireless communication terminals, and more particularly, to wireless communication terminals including functionality for determining the location of the terminal. BACKGROUND [0002]Wireless communication terminals are typically purchased by a user for the purpose of obtaining access to wireless telephone services through a cellular telephone network. However, as the capabilities of communication mobile terminals increase, an additional level of user functionality is being included in the hardware and/or software of such mobile terminals. For example, a communication terminal may be provided with a still and/or video camera, allowing pictures and/or videos to be taken by a user and transmitted from the mobile terminal to others. Likewise, many communication terminals include personal digital assistant (PDA) type applications suitable for tracking scheduling, tasks and the like. Many communication terminals also include messaging capability, such as electronic mail (e-mail), short message service (SMS) and multimedia message service (MMS) capabilities. Communication terminals may also be capable of connecting to the internet by using internet protocol (IP) over wireless and/or wired networks. [0003]Communication terminals are also increasingly being provided with the capability of determining the physical location of the terminal. For example, many communication terminals include global positioning system (GPS) receivers that permit the terminals to determine their location with a high degree of precision. Other systems for determining the location of a communication terminal have been implemented, including systems that obtain location information from a cellular communications network, and systems that obtain location information through inertial guidance techniques. SUMMARY [0004]Some embodiments of the invention provide methods of managing a location of a mobile terminal. The methods include obtaining a position of the mobile terminal, estimating a distance from the mobile terminal to a destination point, generating an estimated time for the mobile terminal to reach the destination point, and generating an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. [0005]Estimating a distance from the mobile terminal to a destination point may include generating a route between the position of the mobile terminal and the destination point based on a movement constraint of the mobile terminal. Generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time based on the generated route. [0006]Generating the route may be performed in response to an operational mode of the mobile terminal. The operational mode may include a pedestrian operational mode, and the movement constraint may include at least one of a building, a bridge, a gate, or a fence. In some embodiments, the operational mode may include a vehicular operational mode, and the movement constraint may include a road. [0007]The methods may further include measuring a current speed of the mobile terminal, and generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time in response to the current speed. In some embodiments, generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time assuming the mobile terminal travels the route at an average speed and/or a maximum speed. [0008]The methods may further include obtaining traffic information indicative of traffic in an area between the mobile terminal and the destination point. Generating the estimated time for the mobile terminal to reach the destination point may include generating the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point. [0009]Generating the route may include generating a quickest route between the position of the mobile terminal and the destination point in response to the traffic in the area between the mobile terminal and the destination point. [0010]Generating the alert may include generating the alert if the estimated time for the mobile terminal to reach the destination point exceeds the threshold time. In some embodiments, generating the alert may include generating the alert if the estimated time for the mobile terminal to reach the destination point is less than the threshold time. [0011]The methods may further include calculating a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and a rate of motion of the mobile terminal. The methods may further include displaying the geo-temporal boundary on a display screen of the mobile terminal. [0012]The methods may further include receiving a user input designating the destination point, and generating a route between the position of the mobile terminal and the destination point. [0013]The methods may further include displaying an information box associated with the mobile terminal, the information box including an estimated time for the mobile terminal to reach the destination point. The methods may further include dynamically updating the geo-temporal boundary in response to a passage of time. [0014]Methods of managing locations of a plurality of mobile terminals according to some embodiments of the invention include obtaining positions of the plurality of mobile terminals, estimating distances from the plurality of mobile terminals to a destination point, generating estimated times for the mobile terminals to reach the destination point, and generating an alert if the estimated time for at least one of the mobile terminals to reach the destination point reaches a threshold time. [0015]A mobile terminal according to some embodiments of the invention includes a location management unit configured to obtain a position of a mobile terminal, and a controller. The controller is configured to estimate a distance from the position of the mobile terminal to a destination point, configured to generate an estimated time for the mobile terminal to reach the destination point, and configured to generate an alert if the estimated time for the mobile terminal to reach the destination point reaches a threshold time. [0016]The mobile terminal may further include a traffic information unit configured to obtain traffic information indicative of traffic in an area between the position of the mobile terminal and the destination point. The controller may be further configured to generate the estimated time in response to the traffic in the area between the position of the mobile terminal and the destination point. [0017]The controller may be further configured to calculate a geo-temporal boundary around the destination point in response to the position of the mobile terminal, the location of the destination point, and a rate of motion of the mobile terminal. [0018]The mobile terminal may further include a map database, and the controller may be further configured to generate a route between the position of the mobile terminal and the destination point in response to map information stored in the map database. BRIEF DESCRIPTION OF THE DRAWINGS [0019]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate certain embodiment(s) of the invention. In the drawings: [0020]FIG. 1 is a schematic block diagram illustrating wireless communication terminals and a cellular communication system in accordance with some embodiments of the present invention. [0021]FIG. 2 is a schematic block diagram illustrating some aspects of a wireless communication terminal in accordance with some embodiments of the present invention. [0022]FIG. 3 is a schematic block diagram illustrating some aspects of a wireless communication terminal in accordance with some embodiments of the present invention. [0023]FIGS. 4-8 are exemplary illustrations of display screens configured according to some embodiments of the invention. [0024]FIGS. 9-11 are flow diagrams illustrating operations of communication terminals according to some embodiments of the invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION [0025]The present invention now will be described more fully with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein the term “comprising” or “comprises” is open-ended, and includes one or more stated elements, steps and/or functions without precluding one or more unstated elements, steps and/or functions. As used herein the term “and/or” includes any and all combinations of one or more of the associated listed items. [0026]Embodiments according to the present invention are described with reference to block diagrams and/or operational illustrations of methods and communication terminals. It is to be understood that each block of the block diagrams and/or operational illustrations, and combinations of blocks in the block diagrams and/or operational illustrations, can be implemented by radio frequency, analog and/or digital hardware, and/or program instructions. These program instructions may be provided to a controller, which may include one or more general purpose processors, special purpose processors, ASICs, and/or other programmable data processing apparatus, such that the instructions, which execute via the controller and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or operational block or blocks. In some implementations, the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. [0027]As used herein, a “communication terminal” (or simply a “terminal”) includes, but is not limited to, a device that is configured to receive/transmit communication signals via a wireline connection, such as via a public-switched telephone network (PSTN), digital subscriber line (DSL), digital cable, a direct cable connection, and/or another data connection/network, and/or via a wireless interface with, for example, a cellular network, a wireless local area network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM/FM broadcast transmitter, and/or another communication terminal. A communication terminal that is configured to communicate over a wireless interface may be referred to as a “wireless communication terminal,” a “wireless terminal” and/or a “mobile terminal.” Examples of mobile terminals include, but are not limited to, a satellite or cellular radiotelephone; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and a conventional laptop and/or palmtop receiver or other appliance that includes a radiotelephone transceiver. [0028]Wireless communication between electronic devices may be accomplished using a wide variety of communication media, communication systems and communication standards. For example, portable electronic devices such as mobile telephones are typically configured to communicate via analog and/or digital wireless radio frequency (RF) telephone systems. Such devices may additionally be configured to communicate using wired and/or wireless local area networks (LANs), short range communication channels, such as Bluetooth RF communication channels and/or infrared communication channels, and/or long range communication systems, such as satellite communication systems. [0029]FIG. 1 is a schematic block diagram of a wireless communication system 100 that includes two communication terminals 102, 104 that are configured to communicate data with one another over a direct wireless communication interface 106, over another wireless communication interface 108 through one or more cellular base stations 110a-b, and/or over another wireless communication interface 112 through a wireless local area network (WLAN) access point 114. The direct wireless communication interface 106 may include an RF wireless communication interface such as a Bluetooth interface or an infrared communication interface, such as, for example, the infrared communication interface defined by the Infrared Data Association (IRDA) protocols. The IRDA defines a number of standards for infrared wireless data communication, including standards for infrared wireless communication at data rates up to 16 Mb/s. It will be appreciated that one or more of the communication terminals 102, 104 may be handheld wireless communication terminals, such as mobile telephones, PDAs, and the like. [0030]As further illustrated in FIG. 1, the terminals 102, 104 may include a user interface 122, a controller 126, a communication module 128, and a memory 125. [0031]The communication module 128 is configured to communicate data over one or more of the wireless interfaces 106, 108, and/or 112 to another remote terminal or other communication device. The memory 125 is configured to store programs and or data for use by the controller 126. The memory 125 may include a nonvolatile memory that is capable of storing digital information even when power to the terminal 102, 104 is switched off. [0032]The communication module 128 can include, for example, a cellular communication module, a Bluetooth module, an infrared communication module, and/or a WLAN module. With a cellular communication module, the terminals 102, 104 can communicate via the base stations 110a-b using one or more cellular communication protocols such as, for example, Advanced Mobile Phone Service (AMPS), ANSI-136, Global Standard for Mobile (GSM) communication, General Packet Radio Service (GPRS), enhanced data rates for GSM evolution (EDGE), code division multiple access (CDMA), wideband-CDMA, CDMA2000, and Universal Mobile Telecommunications System (UMTS). The cellular base stations 110a-b may be connected to a Mobile Telephone Switching Office (MTSO) 116, which, in turn, may be connected to one or more other networks 118 (e.g. the Internet, a public switched telephone network, and/or another network). With a Bluetooth or infrared module, the terminal 102, 104 can communicate via an ad-hoc network using the direct interface 106. With a WLAN module, the terminal 102, 104 can communicate through the WLAN router 114 using a communication protocol that may include, but is not limited to, 802.11a, 802.11b, 802.11e, 802.11g, and/or 802.11i. One or more of the terminals 102, 104 may also be configured to communicate directly over the networks 118 as shown in FIG. 1. [0033]The terminals 102, 104 may be configured to transmit and/or receive a digital data signal between one another and/or with another communication terminal that may be communicatively coupled thereto through, for example the MTSO 116, and/or another network 118, such as a public switched telephone network (PSTN). However, it will be appreciated that data communication between terminals 102, 104 may be accomplished without using the MTSO 116 or the other networks 118. [0034]The terminals 102, 104 my additionally include an AM/FM radio tuner, a UHF/VHF tuner, a satellite radio tuner, a DVB-H receiver, and/or another receiver configured to receive a broadcast audio/video signal. [0035]Some further aspects of a terminal 102 according to some embodiments of the invention are illustrated in FIG. 2. As shown therein, a terminal 102 may further include a position/velocity determination unit 146 and a traffic information unit 148. The position/velocity determination unit 146 and the traffic information unit 148 may communicate with the communication module 128 through the controller 126 as shown in FIG. 2. Alternatively or additionally, the position/velocity determination unit 146 and/or the traffic information unit 148 may communicate directly with the communication module 128, for example through a system bus. [0036]According to some embodiments, the position/velocity determination unit 146 may be configured to determine a current position and/or velocity of the terminal 102. For example, the position/velocity determination unit 146 may include a global positioning system (GPS) receiver that permits the position/velocity determination unit 146 to determine the location of the terminal 102 with a high degree of precision. The position/velocity determination unit 146 may include other systems and/or functionality for determining the location of the terminal 102. For example, the position/velocity determination unit 146 may be configured to obtain location information for the terminal 102 from a cellular communications network with which the terminal 102 may communicate. The position/velocity determination unit 146 may further include an inertial guidance system that permits the position/velocity determination unit 146 to determine a position/velocity of the terminal 102 through inertial movement from a known position. [0037]The traffic information unit 148 is configured to obtain information about current automobile and/or pedestrian traffic in or near a location at which the terminal 102 is located and/or near a destination point, or along a route from a current location of the terminal 102 to a destination point. For example, traffic information may be broadcast in one or more data subchannels of a public and/or private communication network that may be received by the terminal 102. For example, Traffic Message Channel (TMC) data is available in a number of cities throughout North America and Europe. TMC data is broadcast continuously on FM radio channels, and may provide notification of accidents, road construction, police, or emergency action, etc. [0038]Traffic information obtained by the traffic information unit 148 may be used by the controller 126 to determine estimated travel times and/or route information for a user of the terminal 102, as will be described in greater detail below. [0039]The terminal 102 may further include a map database 150 that contains map information concerning a geographic location in which the terminal 102 is located, or in which a destination point is located. For example, the map database 150 may contain street/road information and/or may contain map information for other areas, such as pedestrian walking areas. The map information may further include information regarding features, such as buildings, fences, rivers, etc., that may constrain the motion of a user of the terminal 102. [0040]Although the map database 150 is shown as a component of the terminal 102, it will be appreciated that the map database 150, and/or a portion of the map database 150, may be located remotely from the terminal 102. For example, the map database 150 may be stored remotely and accessed through the communication module 128. A portion of the map database 150 may be retrieved and stored locally at the terminal 102. [0041]Referring to FIG. 3, the user interface 122 can include an input device 134, such as a keypad, keyboard, touchpad, jog dial and/or other user input device. The user interface 122 may further include a display screen 132, such as an LCD display that is capable of displaying video signals in a video format, such as Quarter VGA (QVGA, 320×240 pixels), Common Intermediate Format (CIF, 360×288 pixels) and/or Quarter Common Intermediate Format (QCIF, 180×144 pixels). The terminal 102 may include appropriate CODECs to permit the terminal 102 to decode and display video signals in various formats. The user interface 122 can also include an audio interface unit 136 including a microphone coupled to an audio processor that is configured to generate an audio data stream responsive to sound incident on the microphone, and a speaker that generates sound responsive to an input audio signal. [0042]Accordingly, a navigational aid, such as a map, may be displayed on the display screen 132. Furthermore, alerts and or navigational information may be communicated to a user or the terminal 102 through the audio interface 136. [0043]According to some embodiments, a position of a terminal 102 is determined by the position/velocity determination unit 146. The controller 126 may then estimate the distance of the terminal 102 from a destination point, and may determine an estimated time for the terminal 102 to reach the destination point, assuming a given course and velocity. The controller 126 may generate an alert if the estimated time for the communication terminal to reach the destination point reaches a threshold time. [0044]In particular, the controller 126 may determine a route between a current position of the terminal 102 and the destination point. The route may be determined based on an operational mode of the controller 126. For example, in a first mode (i.e. an unconstrained mode), the route may be determined without movement constraints on the user. Thus, the route may be a straight line from the current position of the terminal 102 to the destination point. [0045]In some embodiments, the controller 126 may operate in a second mode (“constrained mode”), in which the route may be determined based on movement constraints. For example, the movement of the terminal 102 may be limited to movement over streets/roads. [0046]In a third mode (“partially constrained mode”), the route may be determined based on partial movement constraints, such as the presence of buildings, fences, gates, and/or other features that may partially restrict the movement of the user and/or vehicle in which the terminal 102 is located. The partially constrained mode of operation may be suitable for locations in which the terminal 102 is carried by a user, but in which the user's movement is at least partially limited. For example, the partially constrained mode may be suitable in urban locations, where the movement of the user in certain directions may be blocked by buildings, rivers, walls and/or other geographic features, or in locations, such as theme parks, where the movement of a user of the terminal 102 is generally unconstrained but may be limited, for example, by fences, gates, etc. [0047]The terminal102 may also operate in a vehicular mode or a pedestrian mode of operation. In a vehicular mode of operation, the terminal 102 may be limited to movement along streets/roads (i.e. constrained mode) for purposes of route/distance/time calculation, but may be assumed to be able to move at prevailing traffic speeds. In a pedestrian mode, the terminal 102 may be assumed to be in an unconstrained mode or a partially constrained mode, but may be assumed to have a maximum speed that corresponds to an average, predicted or maximum walking speed for purposes of route/distance/time calculation. [0048]The current speed of the terminal 102 may be determined, and the estimated time for the terminal 102 to reach the destination point may be determined based on the current speed of the user and/or the operational mode of the terminal 102. In some embodiments, an average speed may be used to determine the estimated time for the terminal 102 to reach the destination point. In other embodiments, a maximum historic speed may be used to determine the estimated time for the communication terminal to reach the destination point. In some embodiments, the velocity (speed and direction) of the terminal 102 may be determined, and the estimated time for the terminal 102 to reach the destination point may be determined based on the current velocity of the user. [0049]In some embodiments, an alert may be generated if the estimated time for the terminal 102 to reach the destination point (assuming movement along a designated route) exceeds the threshold time. This might be the case, for example, if the terminal 102 moves too far away from a designated destination point. Thus, for example, in some embodiments, a user may wish to be notified if they move too far away from a destination point to be able to return to the destination point within a given amount of time. As an example, a user may have an appointment at a destination point at a given time. The user may wish to temporarily walk away from the destination point, but may not want to be more than, for example, 15 minutes away from the destination point. Accordingly, an alert may be generated, and the user may be notified, if it is determined that the estimated time for the user of the terminal 102 to return to the destination point is greater than 15 minutes. [0050]In some embodiments, the alert may be generated if the estimated time for the user of the terminal 102 to reach the destination point is less than the threshold time. For example, a user may wish to be notified when they are less than 15 minutes away from a destination point that the user is traveling toward. [0051]Some embodiments of the invention are illustrated in FIG. 4, which shows a map displayed on a display screen 132 of the terminal 102. The map displayed on the display screen 132 includes icons showing a destination point 138 (indicated by a star) and a first location 140a of a user of the terminal 102. The destination point 138 may be entered by a user of the terminal 102 and displayed by the communication terminal on the display screen 132. The user may also enter a temporal limit indicating an amount of time from the destination point 138 based on speed and/or directional constraints of the user. In the embodiments shown in FIG. 4, the terminal 102 is operating in an unconstrained mode, such that it is assumed that the user of the communication terminal may move in any direction. [0052]In some embodiments, the terminal 102 may generate a geo-temporal boundary 142, which indicates the farthest location that the user can be from the destination point while still being less than the temporal limit away from reaching the destination point. That is, assuming the temporal limit entered by the user is 15 minutes, when the communication terminal is located just on the geo-temporal boundary 142, it is estimated that it would take the user approximately 15 minutes to reach the destination point along a chosen path. In some embodiments, the communication terminal may determine a shortest path from the current location of the terminal 102 and the geo-temporal boundary 142 may be determined based on the shortest path to the destination point. [0053]In some embodiments, the geo-temporal boundary 142 may be explicitly calculated or estimated by the terminal 102 and displayed on the display screen 132, for example, as a shaded and/or highlighted area around a destination point 138. However, in some embodiments, the geo-temporal boundary may not be explicitly determined. Rather, the terminal 102 may periodically update an expected travel time from a current location 140 to a destination point 138, and an alert may be generated when the expected travel time equals the temporal limit established by the user. [0054]In the embodiments shown in FIG. 4, as the movement of the user is assumed to be unconstrained, the geo-temporal boundary 142 has the shape of a circle with the destination point at the center of the circle. [0055]The time that it is estimated to take the user to move from the current location of the terminal 102 to the destination point may be estimated with reference to an assumed movement rate (speed) of the user. The assumed speed of the user may be equal to a current speed of the user, an average speed of the user, and/or an arbitrarily chosen speed. [0056]Accordingly, assuming unconstrained movement, the radius R of the geo-temporal boundary 142 may be given by the following equation: R=S*T  (1) where S is the assumed speed of the user and T is the temporal limit entered by the user. [0057]In some embodiments, the location of the geo-temporal boundary may be updated at regular and/or irregular time intervals. For example, the user may specify a certain time that he or she needs to be at a destination point. In that case, the radius of the geo-temporal boundary 142 may be given by the equation: R′=S*(T−t)  (2) where S and T are as given above, and t represents the elapsed time since the temporal limit was established. Thus, as shown in FIG. 4, after an amount of time t has elapsed, the geo-temporal boundary 142 will shrink to a new boundary 142′ in proportion to the amount of time elapsed. [0058]As an example, a visitor to a theme park may have a reservation to ride a particular ride located at a destination point 138 in the park. The user may enter the destination point into the terminal 102 and may designate a temporal limit that is less than or equal to the time remaining before the reservation time. The communication terminal may then determine a geo-temporal boundary 142 around the destination point based on the temporal limit. A map showing the geo-temporal boundary 142, the location of the destination point 138 and the current location 140 of the terminal 102 may be displayed on the display screen 132. The geo-temporal boundary 142 may be continually updated according to changes in elapsed time. Provided the user stays within the geo-temporal boundary 142, the user can have confidence that he or she will be able to reach the ride by the appointed time. [0059]The geo-temporal boundary 142 may also be updated based on changes in the average speed of movement of the user and/or on traffic and/or congestion information obtained by the traffic information unit 148. [0060]FIG. 4 also illustrates a user located at a location 140b outside the geo-temporal boundary 142. In some embodiments, a user may wish to be notified when he or she comes within a certain travel time of a destination point so that a predetermined action can be performed. For example, a user may wish to be notified when he or she is within ten minutes of a destination, so that the user can contact someone at the destination. [0061]FIG. 5 illustrates a map on a display 132 of a communication terminal where the motion of the user is partially constrained. In particular, the user and the destination point 138 may be in an urban environment including streets 146 and buildings 144 that restrict movement to generally orthogonal directions (e.g. north/south and east/west). Accordingly, the geo-temporal boundary 142 may have a shape that is non-circular. In particular, since the motion of the user in the area shown in FIG. 5 is generally limited to north/south and east/west movement, the geo-temporal boundary 142 may have a generally diamond shaped periphery. [0062]In the embodiments shown in FIG. 5, the location of the user terminal 102 is indicated by a symbol 140 that indicates position and direction of the user. [0063]In some embodiments, traffic information may be provided to the terminal 102 by a public and/or private traffic information system, as described above. In some embodiments, one or more traffic cameras 143 or other sensors may be positioned in an area and may be used to provide an indication of vehicular and/or pedestrian traffic. The amount of traffic present in a location may be used to determine an expected and/or maximum speed of the user, which in turn may be used to determine the estimated travel time of the user to the destination point 138 and/or the location of the geo-temporal boundary 142. For example, more traffic congestion may result in slower expected speeds, which may reduce the footprint of the geo-temporal boundary 142. Traffic information and/or information concerning average or expected rates of speed may also be obtained from other location-enabled mobile terminals 102, and may be communicated to the terminal 102, for example, through a communication link 106, 108, 112 as shown in FIG. 1. [0064]Anot(String), 发明领域 [0001] 本发明涉及无线通信终端,更具体地,涉及包括用于确定终端位置的功能的无线通信终端。 背景 [0002] 无线通信终端通常由用户购买,目的是通过蜂窝电话网络获得对无线电话服务的访问。 然而,随着通信移动终端的能力增加,附加级别的用户功能被包括在这样的移动终端的硬件和/或软件中。 例如,通信终端可以配备静态和/或摄像机,允许用户拍摄照片和/或视频并从移动终端传输给其他人。 同样,许多通信终端包括适用于跟踪日程安排、任务等的个人数字助理(PDA)类型的应用程序。 许多通信终端还包括消息传递能力,例如电子邮件(e-mail)、短消息服务(SMS)和多媒体消息服务(MMS)能力。 通信终端也能够通过使用互联网协议(IP)在无线和/或有线网络上连接到互联网。 [0003] 通信终端也越来越多地具有确定终端物理位置的能力。 例如,许多通信终端包括允许终端以高精度确定它们的位置的全球定位系统(GPS)接收器。 已经实现了用于确定通信终端位置的其他系统,包括从蜂窝通信网络获取位置信息的系统,以及通过惯性引导技术获取位置信息的系统。 概括 [0004] 本发明的一些实施例提供了管理移动终端的位置的方法。 该方法包括获取移动终端的位置,估计移动终端到目的地点的距离,生成移动终端到达目的地点的估计时间,以及如果移动终端到达目的地的估计时间则生成警报。 到达目的地点达到阈值时间。 [0005] 估计从移动终端到目的地点的距离可以包括基于移动终端的移动约束生成移动终端的位置和目的地点之间的路线。 生成移动终端到达目的地点的估计时间可以包括基于生成的路线生成估计时间。 [0006] 可以响应于移动终端的操作模式来执行生成路线。 操作模式可包括行人操作模式,并且移动约束可包括建筑物、桥梁、大门或栅栏中的至少一者。 在一些实施例中,操作模式可以包括车辆操作模式,并且移动约束可以包括道路。 [0007] 该方法还可以包括测量移动终端的当前速度,并且生成移动终端到达目的地点的估计时间可以包括响应于当前速度生成估计时间。 在一些实施例中,生成移动终端到达目的地点的估计时间可以包括假设移动终端以平均速度和/或最大速度行进路线来生成估计时间。 [0008] 该方法还可以包括获得指示移动终端和目的地点之间的区域中的交通的交通信息。 生成移动终端到达目的地点的估计时间可以包括响应于移动终端的位置和目的地点之间的区域中的交通生成估计时间。 [0009] 生成路线可以包括响应于移动终端和目的地点之间的区域中的交通生成移动终端的位置和目的地点之间的最快路线。 [0010]生成警报可以包括如果移动终端到达目的地点的估计时间超过阈值时间则生成警报。 在一些实施例中,生成警报可以包括如果移动终端到达目的地点的估计时间小于阈值时间则生成警报。 [0011] 该方法还可以包括响应于移动终端的位置、目的地点的位置和移动终端的运动速率来计算目的地点周围的地理-时间边界。 该方法还可以包括在移动终端的显示屏上显示地理时间边界。 [0012] 该方法还可以包括接收指定目的地点的用户输入,以及生成移动终端的位置和目的地点之间的路线。 [0013] 该方法还可以包括显示与移动终端相关联的信息框,该信息框包括移动终端到达目的地点的估计时间。 该方法还可以包括响应于时间的流逝动态地更新地理时间边界。 [0014] 根据本发明的一些实施例的管理多个移动终端的位置的方法包括获取多个移动终端的位置、估计多个移动终端到目的地点的距离、生成移动终端到达目的地的估计时间。 目的地点,并且如果移动终端中的至少一个移动终端到达目的地点的估计时间达到阈值时间则生成警报。 [0015] 根据本发明一些实施例的移动终端包括被配置为获得移动终端的位置的位置管理单元和控制器。 控制器被配置为估计从移动终端的位置到目的地点的距离,被配置为生成移动终端到达目的地点的估计时间,并且被配置为如果移动终端的估计时间生成警报 到达目的地点达到阈值时间。 [0016] 移动终端还可以包括交通信息单元,配置为获得指示移动终端的位置和目的地点之间的区域中的交通的交通信息。 控制器还可以被配置为响应于移动终端的位置和目的地点之间的区域中的交通产生估计时间。 [0017] 控制器还可以被配置为响应于移动终端的位置、目的地点的位置和移动终端的运动速率来计算目的地点周围的地理-时间边界。 [0018] 移动终端还可以包括地图数据库,并且控制器还可以被配置为响应于存储在地图数据库中的地图信息生成移动终端的位置和目的地点之间的路线。 附图的简要说明 [0019] 包括的附图是为了提供对本发明的进一步理解并且并入本申请并构成本申请的一部分,图示了本发明的某些实施例。 在图纸中: [0020] 图1是说明根据本发明一些实施例的无线通信终端和蜂窝通信系统的示意框图。 [0021] 图2是说明根据本发明一些实施例的无线通信终端的一些方面的示意框图。 [0022] 图3是说明根据本发明一些实施例的无线通信终端的一些方面的示意框图。 [0023] 图4-8是根据本发明的一些实施例配置的显示屏的示例性图示。 [0024] 图9-11是图示根据本发明的一些实施例的通信终端的操作的流程图。 具体实施方式的详细说明 [0025] 现在将参考附图更全面地描述本发明,在附图中示出了本发明的实施例。 然而,本发明不应被解释为限于在此阐述的实施例。 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明的范围充分地传达给本领域的技术人员。 相同的数字始终指代相同的元素。 如本文所用,术语“包括”或“包括”是开放式的,并且包括一个或多个规定的要素、步骤和/或功能而不排除一个或多个未规定的要素、步骤和/或功能。 如本文所用,术语“和/或”包括一个或多个关联列出的项目的任何和所有组合。 [0026] 参照方框图和/或方法和通信终端的操作说明来描述根据本发明的实施例。 应当理解,方框图和/或操作说明的每个方框,以及方框图和/或操作说明中方框的组合,可以通过射频、模拟和/或数字硬件、和/或程序来实现 指示。 这些程序指令可以提供给控制器,该控制器可以包括一个或多个通用处理器、专用处理器、ASIC和/或其他可编程数据处理装置,使得经由控制器和/或其他可编程数据处理装置执行的指令 数据处理设备,创建用于实现框图和/或操作块中指定的功能/动作的装置。 在一些实施方式中,块中标注的功能/动作可能不按操作说明中标注的顺序发生。 例如,连续显示的两个块实际上可以基本上同时执行,或者这些块有时可以以相反的顺序执行,这取决于所涉及的功能/动作。 [0027] 如本文所用,“通信终端”(或简称为“终端”)包括但不限于配置为通过有线连接(例如通过公共交换电话网络)接收/发送通信信号的设备 (PSTN)、数字用户线 (DSL)、数字电缆、直接电缆连接和/或另一个数据连接/网络,和/或通过无线接口与例如蜂窝网络、无线局域网( WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM/FM广播发射机和/或另一个通信终端。 被配置为通过无线接口进行通信的通信终端可以称为“无线通信终端”、“无线终端”和/或“移动终端”。 移动终端的示例包括但不限于卫星或蜂窝无线电话; 个人通信系统 (PCS) 终端,可将蜂窝无线电话与数据处理、传真和数据通信功能相结合; 可包括无线电话、寻呼机、互联网/内联网访问、Web 浏览器、管理器、日历和/或全球定位系统 (GPS) 接收器的 PDA; 以及包括无线电话收发器的常规膝上型和/或掌上型接收器或其他器具。 [0028] 电子设备之间的无线通信可以使用各种各样的通信媒体、通信系统和通信标准来实现。 例如,诸如移动电话的便携式电子设备通常被配置为通过模拟和/或数字无线射频(RF)电话系统进行通信。 此类设备还可配置为使用有线和/或无线局域网 (LAN)、短程通信信道(例如蓝牙 RF 通信信道和/或红外通信信道)和/或远程通信系统(例如卫星)进行通信 通信系统。 [0029] 图1是无线通信系统的示意框图 100 其中包括两个通信终端 102 , 104 配置为通过直接无线通信接口相互通信数据 106, 通过另一个无线通信接口 108 通过一个或多个蜂窝基站 110 a - b ,和/或通过另一个无线通信接口 112 通过无线局域网 (WLAN) 接入点 114 . 直接无线通讯接口 106 可以包括RF无线通信接口,例如蓝牙接口或红外通信接口,例如由红外数据协会(IRDA)协议定义的红外通信接口。 IRDA 定义了许多红外无线数据通信标准,包括数据速率高达 16 Mb/s 的红外无线通信标准。 应当理解,一个或多个通信终端 102 , 104 可以是手持无线通信终端,例如手机、PDA等。 [0030] 如图 1 中进一步所示,终端 102 , 104 可能包括用户界面 122 , 一个控制器 126 , 通信模块 128 , 和记忆 125 . [0031] 通信模块 128 被配置为通过一个或多个无线接口传送数据 106 , 108 , 和/或 112 到另一个远程终端或其他通信设备。 记忆 125 被配置为存储供控制器使用的程序和/或数据 126 . 记忆 125 可能包括一个非易失性存储器,即使在为终端供电时也能够存储数字信息 102 , 104 已关闭。 [0032] 通信模块 128 可以包括例如蜂窝通信模块、蓝牙模块、红外通信模块和/或WLAN模块。 使用蜂窝通信模块,终端 102 , 104 可以通过基站进行通信 110 a - b 使用一种或多种蜂窝通信协议,例如高级移动电话服务 (AMPS)、ANSI-136、全球移动标准 (GSM) 通信、通用分组无线服务 (GPRS)、增强数据速率的 GSM 演进 (EDGE) )、码分多址 (CDMA)、宽带 CDMA、CDMA2000 和通用移动电信系统 (UMTS)。 蜂窝基站 110 a - b 可以连接到移动电话交换局 (MTSO) 116 ,这反过来又可以连接到一个或多个其他网络 118 (例如互联网、公共交换电话网络和/或其他网络)。 带有蓝牙或红外模块,终端 102 , 104 可以使用直接接口通过临时网络进行通信 106 . 带有WLAN模块,终端 102 , 104 可以通过WLAN路由器进行通信 114 使用的通信协议可能包括但不限于 802.11a、802.11b、802.11e、802.11g 和/或 802.11i。 一个或多个终端 102 , 104 也可以配置为直接通过网络通信 118 如图1所示。 [0033] 终端机 102 , 104 可以被配置为在彼此之间和/或与可以通过例如MTSO与其通信耦合的另一通信终端之间传送和/或接收数字数据信号 116 , 和/或另一个网络 118 ,例如公共交换电话网 (PSTN)。 然而,应当理解,终端之间的数据通信 102 , 104 可以在不使用 MTSO 的情况下完成 116 或其他网络 118 . [0034] 终端机 102 , 104 我还包括 AM/FM 无线电调谐器、UHF/VHF 调谐器、卫星无线电调谐器、DVB-H 接收器和/或配置为接收广播音频/视频信号的另一个接收器。 [0035] 终端的一些其他方面 102 根据本发明的一些实施例在图2中示出。如图中所示,终端 102 可以进一步包括位置/速度确定单元 146 和一个交通信息单元 148 . 位置/速度确定单元146 和交通信息单元 148 可与通讯模块通讯 128 通过控制器 126 如图 2 所示。可替代地或附加地,位置/速度确定单元 146 和/或交通信息单元 148 可直接与通讯模块通讯 128 ,例如通过系统总线。 [0036] 根据一些实施例,位置/速度确定单元 146 可以被配置为确定终端的当前位置和/或速度 102 . 例如,位置/速度确定单元 146 可能包括允许位置/速度确定单元的全球定位系统 (GPS) 接收器 146 确定终端的位置 102 具有高精度。 位置/速度确定单元 146 可能包括用于确定终端位置的其他系统和/或功能 102 . 例如,位置/速度确定单元 146 可以配置为获取终端的位置信息 102 从与终端的蜂窝通信网络 102 可以交流。 位置/速度确定单元 146 可以进一步包括惯性制导系统,允许位置/速度确定单元 146 确定终端的位置/速度 102 通过已知位置的惯性运动。 [0037] 交通信息单元 148 被配置为获取有关当前汽车和/或行人在终端所在位置或附近的信息 102 位于和/或靠近目的地点,或沿着终端当前位置的路线 102 到一个目的地点。 例如,可以在终端可以接收的公共和/或专用通信网络的一个或多个数据子信道中广播交通信息 102 . 例如,交通信息频道 (TMC) 数据在北美和欧洲的许多城市都可用。 TMC 数据在 FM 无线电频道上连续广播,并可能提供事故、道路施工、警察或紧急行动等通知。 [0038] 交通信息单元获取的交通信息 148 可以被控制器使用 126 为终端用户确定估计的旅行时间和/或路线信息 102 , 下文将更详细地描述。 [0039] 终点站 102 可能还包括地图数据库 150 包含有关终端所在地理位置的地图信息 102 位于,或目标点位于其中。 比如地图数据库 150 可能包含街道/道路信息和/或可能包含其他区域的地图信息,例如步行区。 地图信息还可以包括关于可能限制终端用户的运动的特征的信息,例如建筑物、栅栏、河流等 102 . [0040] 虽然地图数据库 150 显示为终端的一个组件 102 , 将会理解地图数据库 150 和/或地图数据库的一部分 150 , 可能远离终端 102 . 比如地图数据库 150 可远程存储并通过通信模块访问 128 . 地图数据库的一部分 150 可以在终端本地检索和存储 102 . [0041] 参考图3,用户界面 122 可以包括一个输入设备 134 ,例如小键盘、键盘、触摸板、滚轮和/或其他用户输入设备。 用户界面 122 还可以包括显示屏 132 ,例如能够以视频格式显示视频信号的 LCD 显示器,例如四分之一 VGA(QVGA,320×240 像素)、通用中间格式(CIF,360×288 像素)和/或四分之一通用中间格式( QCIF,180×144 像素)。 终点站 102 可能包括适当的编解码器以允许终端 102解码和显示各种格式的视频信号。 用户界面 122 还可以包括一个音频接口单元 136 包括耦合到音频处理器的麦克风,音频处理器被配置为响应于入射到麦克风上的声音而生成音频数据流,以及扬声器,其响应于输入音频信号而生成声音。 [0042] 因此,可以在显示屏上显示诸如地图之类的导航帮助 132 . 此外,可以将警报和/或导航信息传送给用户或终端 102 通过音频接口 136 . [0043] 根据一些实施例,终端的位置 102 由位置/速度确定单元确定 146 . 控制器 126 然后可以估计终端的距离 102 从目的地点,并且可以确定终端的估计时间 102 假设给定的路线和速度到达目的地点。 控制器 126 如果通信终端到达目的地点的估计时间达到阈值时间,则可以生成警报。 [0044] 特别地,控制器 126 可以确定终端的当前位置之间的路线 102 和目的地点。 路线可基于控制器的操作模式来确定 126 . 例如,在第一模式(即无约束模式)中,可以在没有对用户的移动约束的情况下确定路线。 因此,该路线可以是从终端的当前位置开始的直线 102 到目的地点。 [0045] 在一些实施例中,控制器 126 可以在第二模式(“受限模式”)下操作,其中可以基于移动约束来确定路线。 例如终端的移动 102 可能仅限于在街道/道路上移动。 [0046] 在第三种模式(“部分受限模式”)中,可以基于部分移动限制来确定路线,例如建筑物、栅栏、大门和/或其他可能部分限制用户移动的特征和/ 或终端所在的车辆 102 位于。 部分约束的操作模式可能适用于终端所在的位置 102 由用户携带,但用户的移动至少部分受到限制。 例如,部分约束模式可能适用于城市位置,其中用户在某些方向上的移动可能被建筑物、河流、墙壁和/或其他地理特征阻挡,或者适用于诸如主题公园之类的位置,其中 终端用户的移动 102 通常不受约束,但也可能受到限制,例如,受到栅栏、大门等的限制。 [0047] 终点站 102 也可以以车辆模式或行人模式运行。 在车辆操作模式下,终端 102 出于路线/距离/时间计算的目的,可能仅限于沿街道/道路移动(即约束模式),但可以假定能够以现行交通速度移动。 在行人模式下,航站楼 102 可以假定处于无约束模式或部分约束模式,但可以假定最大速度对应于用于路线/距离/时间计算的平均、预测或最大步行速度。 [0048] 终端当前速度 102 可以确定,和终端的估计时间 102 到达目的地点可以基于用户当前的速度和/或终端的操作模式来确定 102 . 在一些实施例中,可以使用平均速度来确定终端的估计时间 102 到达目的地。 在其他实施例中,可以使用最大历史速度来确定通信终端到达目的地点的估计时间。 在一些实施例中,终端的速度(速度和方向) 102 可以确定,和终端的估计时间 102 可以基于用户的当前速度来确定到达目的地点的时间。 [0049]在一些实施例中,如果终端的估计时间 102 到达目的地点(假设沿指定路线移动)超过阈值时间。 这可能是这种情况,例如,如果终端 102 距离指定的目的地点太远。 因此,例如,在一些实施例中,如果用户移动距离目的地点太远而不能在给定的时间内返回目的地点,则用户可能希望得到通知。 作为示例,用户可能在给定时间在目的地点有约会。 用户可能希望暂时离开目的地点,但可能不想离开目的地点超过例如15分钟。 因此,如果确定终端的用户的估计时间,则可以生成警报,并且可以通知用户 102 返回目的地点的时间大于 15 分钟。 [0050] 在一些实施例中,如果终端用户的估计时间 102 到达目的地点的时间小于阈值时间。 例如,用户可能希望在距离用户行进的目的地点不到 15 分钟时收到通知。 [0051] 本发明的一些实施例在图4中示出,其示出显示在显示屏上的地图 132 终端的 102 . 显示屏上显示的地图 132 包括显示目的地点的图标 138 (用星号表示)和第一个位置 140 a 终端用户的 102 . 目的地点 138 可以由终端用户输入 102 并由通讯终端显示在显示屏上 132 . 用户还可以输入时间限制,指示距离目的地点的时间量 138 基于用户的速度和/或方向限制。 在图4所示的实施例中,终端 102 正在以不受约束的模式操作,从而假设通信终端的用户可以在任何方向上移动。 [0052] 在一些实施例中,终端 102 可能会产生地理时间边界 142 ,它表示用户可以到达目的地点的最远位置,同时仍然小于距离到达目的地点的时间限制。 即,假设用户输入的时限为15分钟,当通信终端刚好位于时空边界上时 142 ,估计用户需要大约 15 分钟才能沿着所选路径到达目的地点。 在一些实施例中,通信终端可以确定距终端当前位置的最短路径 102 和地理时间边界 142 可以基于到目的地点的最短路径来确定。 [0053] 在一些实施例中,地理时间边界 142 可以由终端显式计算或估计 102 并显示在显示屏上 132 ,例如,作为目的地点周围的阴影和/或突出显示区域 138 . 然而,在一些实施例中,地理时间边界可能未被明确确定。 而是终端 102 可能会定期更新从当前位置出发的预期旅行时间 140 到目的地 138 ,并且当预期旅行时间等于用户建立的时间限制时可以生成警报。 [0054] 在图 4 所示的实施例中,由于假设用户的移动不受约束,因此地理时间边界 142 具有圆的形状,目标点位于圆的中心。 [0055] 估计用户从终端当前位置移动所需的时间 102 可以参考假定的用户移动速率(速度)来估计到目的地点的距离。 假定的用户速度可以等于用户的当前速度、用户的平均速度和/或任意选择的速度。 [0056]因此,假设不受约束的运动,地理时间边界的半径 R 142 可由以下等式给出: R=S*T (1) 其中 S 是用户的假定速度,T 是用户输入的时间限制。 [0057] 在一些实施例中,地理时间边界的位置可以以规律和/或不规律的时间间隔更新。 例如,用户可以指定他或她需要到达目的地点的特定时间。 在那种情况下,地理时间边界的半径 142 可以由以下等式给出: R′=S* ( T−t ) (2) 其中 S 和 T 如上所述,t 表示自时间限制建立以来经过的时间。 因此,如图 4 所示,经过一定时间量 t 后,地理-时间边界 142 将缩小到一个新的边界 142 ' 与经过的时间成正比。 [0058] 例如,主题公园的游客可能预订了位于目的地的特定游乐设施 138 在公园里。 用户可以将目的地点输入终端 102 并且可以指定一个时间限制,该时间限制小于或等于保留时间之前的剩余时间。 然后通信终端可以确定地理时间边界 142 基于时间限制在目的地点周围。 显示时空边界的地图 142 , 目标点的位置 138 和当前位置 140 终端的 102 可能会显示在显示屏上 132 . 时空边界 142 可以根据经过的时间的变化不断更新。 如果用户停留在地理时间边界内 142 ,用户可以确信他或她将能够在指定时间到达乘车点。 [0059] 时空边界 142 也可以基于用户移动的平均速度的变化和/或交通信息单元获得的交通和/或拥塞信息来更新 148 . [0060] 图 4 还说明了位于某个位置的用户 140 b 在地理时间边界之外 142 . 在一些实施例中,用户可能希望在他或她在目的地点的特定旅行时间内到达时得到通知,以便可以执行预定动作。 例如,用户可能希望在他或她距离目的地不到十分钟时收到通知,以便用户可以联系目的地的某人。 [0061] 图5图示了显示器上的地图 132 用户的运动被部分约束的通信终端的例子。 特别是,用户和目的地点 138 可能在城市环境中,包括街道 146 和建筑物 144 将运动限制在大致正交的方向(例如北/南和东/西)。 因此,地理时间边界 142 可能具有非圆形的形状。 具体而言,由于用户在图 5 所示区域中的运动通常限于北/南和东/西运动,因此地理时间边界 142 可以具有大致菱形的外围。 [0062] 在图5所示的实施例中,用户终端的位置 102 由符号表示 140 指示用户的位置和方向。 [0063] 在一些实施例中,可以向终端提供交通信息 102 通过公共和/或私人交通信息系统,如上所述。 在一些实施例中,一个或多个交通摄像头 143 或其他传感器可以放置在一个区域中,并可以用来提供车辆和/或行人交通的指示。 位置中存在的交通量可用于确定用户的预期和/或最大速度,这又可用于确定用户到目的地点的估计行进时间 138 和/或地理时间边界的位置 142 . 例如,更多的交通拥堵可能会导致预期速度变慢,这可能会减少地理时间边界的足迹 142. 还可以从其他支持定位的移动终端获得交通信息和/或关于平均或预期速度的信息 102 , 并且可以传达给终端 102 ,例如,通过通信链路 106 , 108 , 112 如图1所示。 [0064] 图 6 中显示了部分受限运动的另一个示例。在图 6 中所示的实施例中,用户(其位置由图标指示 140 ) 和目的地点 138 位于包括围栏的城市或准城市环境中 148 包括一个门 147 . 时空边界 142 包括一部分 142 a 在围栏的同一侧 148 作为目的地 138 和一部分 142 b 在篱笆的另一边 148 从目的地点 138 . 如图 6 所示,围栏的存在 148 和大门 147 导致时空边界的形状 142 被扭曲。 例如,假设时间限制 T L 已由用户建立,一部分 142 a 时空边界 142 在围栏的同一侧 148 作为目的地 138 大致呈圆形,半径为 R a 等于 S*T L ,其中 S 是用户的估计移动速度。 假设用户需要花费 T 的时间 1 分钟到达目的地 138 从门口 147 ,然后是部分 142 b 时空边界 142 在栅栏的另一边是一个半圆,其半径 Rb 等于 S*(T L −(T 1 +T G )), 其中 T G 代表,例如,在门口的等待时间 147 . [0065] 时空边界的扭曲 142 可以以与上述类似的方式来确定基于其他运动约束的。 目标点周围区域中的建筑物、围栏、大门、桥梁等移动约束越多,时空边界扭曲的越多 142 可能会变成。 时空边界 142 也可能基于用户在不同位置的预期移动速度的变化而失真。 [0066] 约束模式的示例如图 7 所示,其中显示 132 显示包含道路的路线图 156 . 目的地点 138 由星号表示,用户位置由图标表示 140 指示终端的位置和移动方向 102 . 用户位置 140 在路上 156 . 地理时间边界 142 显示为包括部分 156 的道路 156 在用户建立的时间限制内。 在一些实施例中,如图7所示,部分 156 的道路 156 在地理时间边界内 142 可以突出显示、加阴影和/或以其他方式标记以指示地理时间区域内的道路范围 142 . [0067] 终端时可以使用图7所示的显示格式 102 被放置在车辆操作模式下,其中终端的运动 102 仅限于街道/道路 156 . 终端的时间距离 102 从目的地 138 可以通过建立终端当前位置之间的路线来确定 102 和目的地点 138 . 使用地图信息计算路线是本领域已知的,并且不需要进一步描述。 [0068] 图8说明本发明的进一步实施例,其中多于一个终端的位置 102 a - c 可能会显示在显示屏上 132 . 一个或多个终端的当前位置/速度 102 b , 102 c 可以传送到终端 102 a ,例如,通过通信链路 106 , 108 , 112 如图 1. 终端所示 102 a 可能会在显示屏上显示图标 132 终端的 102 a 指示通信终端的位置和/或移动方向 102 b , 102 c ,以及它自己的位置/方向。 此外,如图 8 所示,信息框 141 a - 141 c 可以显示在相应用户图标附近 140 a - 140 c 例如,可以指示从所选目的地点和/或终端的当前操作模式的估计行程时间 102 a - 102 c 与用户图标关联 140 a - 1 . 40 c. [0069] 在图 8 所示的示例中,假设目的地点 138 a 是指定的目的地点,终点站位于location 140 a 以车辆模式运行,预计到达指定目的地点的时间为 12 分 31 秒。 航站楼位于 location 140 b 也以车辆模式运行,预计到达指定目的地点的时间为 18 分 45 秒。 航站楼位于 location 140 c 以行人模式运行,预计到达指定目的地点的时间为 5 分 23 秒。 [0070] 如图 8 中进一步所示,多个目的地点 138 a , 138 b 可能会显示在显示屏上 132 . 选择特定目的地点后 138 a , 138 b , 终点站 102 a 可以显示地理时间边界 142 与所选目的地点相关联和/或信息框可以更新以显示信息,例如相对于所选目的地点的估计旅行时间 138 a , 138 b. [0071] 图8中所示的实施例对于希望提供期望水平的服务和/或对特定位置的响应的服务提供商可能特别有用。 例如,服务级别协议可能指定服务提供商有义务向给定的客户位置提供少于 15 分钟的响应时间。 因此,一些实施例可用于显示服务提供商是否在距客户位置的指定旅行时间内。 [0072] 应当理解,正在跟踪和显示终端位置的终端 102 a - 102 c 和目的地点 138 a , 138 b 不一定是移动或无线通信终端,但可以是例如与终端通信的工作站 102 a - 102 c 通过一个或多个通信链接 106 , 108 , 112 如图1所示。 [0073] 根据本发明的一些实施例的操作在图9至11中示出,其是可以由终端执行的操作的流程图 102 如上所述配置。 参考图9,用户可以设置目的地点 138 在终端 102 (堵塞 205 ). 用户还可以在目的地点周围设置时间限制(块 210 ). [0074] 用户可以设置终端的操作模式 102 用于确定距目的地点的距离和/或时间(块 215 ). 例如,用户可以将操作模式设置为行人模式或车辆模式。 在行人模式下,航站楼 102 可以设置为在无约束模式或部分约束模式下操作,如上所述。 [0075] 终点站 102 可以选择生成和/或显示地理时间边界 142 响应目的地点、时间限制和操作模式(块 220 ). 如上所述,地理时间边界 142 可以参考终端的预期、估计、平均和/或最大速度来确定 102 . [0076] 参见图10,在操作中,终端 102 可以确定终端的位置(块 225 ) 使用位置确定单元 146 (图 2)。 终点站 102 可以进一步获取目的地点周围地理区域的交通/拥堵信息 138 ,例如,使用交通信息单元 148 (堵塞 230 ). 接下来是终端 102 可以计算终端当前位置之间的路线 102 和目的地点 138 使用地图信息、终端位置、目的地点位置和/或交通信息(块 235 ). 在一些实施例中,终端 102 可以确定终端位置和目的地点之间的最快路线。 [0077] 参考图11,终端 102 可以使用位置/速度确定单元确定其位置 146 (堵塞 305 ). 终点站 102 然后可以检查终端的用户是否 102 已经跨越了地理时间边界(块 310 ). 在一些实施例中,终端 102 可确定到达目的地点的预期行程时间 138 已达到指定的时间限制。 [0078] 如果确定终端 102 没有跨越地理时间边界 142 (或者到目的地的预计行程时间 138 没有达到指定的时间限制)(块 310 ),操作可能会循环返回以再次确定终端的位置(块 305 ). [0079] 但是,如果终端 102 确定它已经跨越了地理时间边界 142 (堵塞 310 ), 并且可能会生成警报并且可能会通知用户越界 (bock 315 ). [0080] 已经参考图9-11部分地描述了本发明,图9-11是说明根据本发明的方面的示例性操作的流程图图示。 应当理解,图 9-11 的流程图的方框以及流程图中方框的组合可以使用包括在终端中的电子电路来实现,例如终端 102 . 还应理解,图 9-11 的流程图的块以及流程图中的块的组合可以使用不同于图 1 中所示的组件来实现, 2 和 2 A,一般来说,图 9-11 的流程图的方框和流程图中方框的组合,可以在专用硬件中实现,例如分立的模拟和/或数字电路,例如集成的组合 电路或一个或多个专用集成电路 (ASIC),以及通过可以加载到计算机或其他可编程数据处理设备上以产生机器的计算机程序指令,使得在计算机上执行的指令或其他可编程数据 处理装置创建用于实现流程图块或块中指定的功能的装置。 计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,以导致在计算机或其他可编程设备上执行一系列操作步骤,以产生计算机实现的过程,使得在计算机或其他可编程数据处理设备上执行的指令 其他可编程装置提供用于实现流程图块或块中指定的功能的步骤。 [0081] 因此,图9-11的流程图图示的块支持用于执行指定功能/动作的电子电路和其他装置,以及用于执行指定功能/动作的步骤的组合。 应当理解,图 9-11 的流程图的每个块所支持的电路和其他装置以及其中的块的组合可以通过在专用或通用数据处理器上运行的专用硬件、软件或固件来实现, 或其组合。 [0082]在附图和说明书中,已经公开了本发明的实施例,尽管使用了特定的术语,但它们仅用于一般和描述性的意义,而不是为了限制的目的,本发明的范围如下所述 索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AT483316T(String), BRPI0721418A2(String), CN101627610A(String), CN101627610B(String), DE602007009573D1(String), DE602007009573T2(String), EP2116013A2(String), EP2116013B1(String), IN4590CHENP2009A(String), JP2010522867A(String), MX2009008667A(String), MX293111B(String), RU2009136561A(String), RU2460042C2(String), US20080218405A1(String), US7561063B2(String), WO2008108827A2(String), WO2008108827A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AT483316T(String), BRPI0721418A2(String), CN101627610A(String), CN101627610B(String), DE602007009573D1(String), DE602007009573T2(String), EP2116013A2(String), EP2116013B1(String), IN4590CHENP2009A(String), JP2010522867A(String), MX2009008667A(String), MX293111B(String), RU2009136561A(String), RU2460042C2(String), US20080218405A1(String), US7561063B2(String), WO2008108827A2(String), WO2008108827A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7561063B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AT483316T(String), BRPI0721418A2(String), CN101627610A(String), CN101627610B(String), DE602007009573D1(String), DE602007009573T2(String), EP2116013A2(String), EP2116013B1(String), IN4590CHENP2009A(String), JP2010522867A(String), MX2009008667A(String), MX293111B(String), RU2009136561A(String), RU2460042C2(String), US20080218405A1(String), US7561063B2(String), WO2008108827A2(String), WO2008108827A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), AT483316T(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), BRPI0721418A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), CN101627610A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), CN101627610B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:09.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), DE602007009573D1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), DE602007009573T2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), EP2116013A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), EP2116013B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), IN4590CHENP2009A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), JP2010522867A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), MX2009008667A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), MX293111B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), RU2009136561A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), RU2460042C2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), US20080218405A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), US7561063B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), WO2008108827A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271650(Integer), WO2008108827A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7561063B2(String), US7561063B2(String), 1247500800(Integer), 271650(Integer), 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185952(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 185952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1660818391(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185952(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 23104(Integer), 2(Integer), 185952(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:10.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权 | 权利转移(String), 3(Integer), 185952(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US11209555B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Positioning method and apparatus for mobile terminal, and mobile terminal(String), 移动终端的定位方法、装置及移动终端(String), US11209555B2(String), A positioning method and apparatus for a mobile terminal, and a mobile terminal. After a first time period elapses, a main processor obtains M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal, and obtains K pieces of buffered position change data of the mobile terminal. The main processor combines the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. The N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period. The K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period.(String), 一种移动终端的定位方法、装置及移动终端。 在经过第一时间段后,主处理器从缓存的N条移动终端导航数据中获取M条可靠的导航数据,并获取缓存的K条移动终端位置变化数据。 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 N个导航数据是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 K个位置变化数据是利用移动终端的传感器在第一时间段内监测得到的数据计算得到的。(String), US15/764263(String), 1447084800(Integer), US11209555B2(String), 1640620800(Integer), 1640620800(Integer), 美国(String), 4(Integer), WO(String), 5(Integer), 37(Integer), CN101035386A | CN101769747A | CN102243315A | CN102645667A | CN102901975A | CN103312902A | CN103454659A | CN104598253A | CN104749592A | CN104793223A | CN105223595A | JP2011209057A | JP2012083323A | JP2014190827A | US10514468B2 | US20050049787A1 | US20070010936A1 | US20080266174A1 | US20090278738A1 | US20110106450A1 | US20110175772A1 | US20110237275A1 | US20110291886A1 | US20120062414A1 | US20120176270A1 | US20150304985A1 | US7171303B1 | US7460064B1 | US8054220B1 | US8362949B2 | US8391888B2 | US8560218B1 | US8655578B2 | US8692709B2 | US9291704B2 | US9451580B2 | US9880286B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.468 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.612 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.613 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.613 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\5bca85bc978245d89acce83f1ce75abc.png(String), 185953(Integer), 5bca85bc978245d89acce83f1ce75abc.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.666 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.666 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.666 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Positioning method and apparatus for mobile terminal, and mobile terminal(String), 移动终端的定位方法、装置及移动终端(String), US11209555B2(String), A positioning method and apparatus for a mobile terminal, and a mobile terminal. After a first time period elapses, a main processor obtains M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal, and obtains K pieces of buffered position change data of the mobile terminal. The main processor combines the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. The N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period. The K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period.(String), 一种移动终端的定位方法、装置及移动终端。 在经过第一时间段后,主处理器从缓存的N条移动终端导航数据中获取M条可靠的导航数据,并获取缓存的K条移动终端位置变化数据。 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 N个导航数据是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 K个位置变化数据是利用移动终端的传感器在第一时间段内监测得到的数据计算得到的。(String), US15/764263(String), 1447084800(Integer), US11209555B2(String), 1640620800(Integer), 1640620800(Integer), 美国(String), 3(Integer), 4(Integer), WO(String), 5(Integer), 37(Integer), CN101035386A | CN101769747A | CN102243315A | CN102645667A | CN102901975A | CN103312902A | CN103454659A | CN104598253A | CN104749592A | CN104793223A | CN105223595A | JP2011209057A | JP2012083323A | JP2014190827A | US10514468B2 | US20050049787A1 | US20070010936A1 | US20080266174A1 | US20090278738A1 | US20110106450A1 | US20110175772A1 | US20110237275A1 | US20110291886A1 | US20120062414A1 | US20120176270A1 | US20150304985A1 | US7171303B1 | US7460064B1 | US8054220B1 | US8362949B2 | US8391888B2 | US8560218B1 | US8655578B2 | US8692709B2 | US9291704B2 | US9451580B2 | US9880286B2(String), \20230420\5bca85bc978245d89acce83f1ce75abc.png(String), 20(Integer), 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 1. A positioning method for a mobile terminal, wherein the mobile terminal comprises at least one processor, a sensor, and a global navigation satellite system (GNSS) receiver, and the method comprises:receiving, by the GNSS receiver and from one or more GNSS navigation satellites, a satellite navigation signal during a first time period;storing N pieces of navigation data of the mobile terminal in a first buffer, wherein N is an integer, and wherein the N pieces of navigation data are obtained through calculation by using the satellite navigation signal received during the first time period;monitoring, by the sensor, movement data of the mobile terminal during the first time period;storing K pieces of position change data of the mobile terminal in a second buffer, wherein K≥1, K is an integer, and the K pieces of position change data are obtained through calculation by using the movement data of the mobile terminal during the first time period;obtaining, by the at least one processor after the first time period elapses, M pieces of navigation data from the N pieces of navigation data of the mobile terminal in the first buffer, wherein N≥M, M≥1, and M;obtaining, by the at least one processor after the first time period elapses, the K pieces of position change data of the mobile terminal in the second buffer; andcombining, by the at least one processor, the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period.(String), 1.根据权利要求10所述的方法,其中至少一处理器从N个导航数据中取得M个导航数据包含:其中,N个导航数据分别对应一个时刻和一个信号强度,N个导航数据对应时刻t1,吨2,...,和TN分别按照时刻的先后顺序;至少一处理器根据时刻的先后顺序遍历N条导航数据的信号强度;至少一处理器判断第一导航数据的状态为高,其中第一导航数据为N个导航数据中信号强度大于或等于a的第一导航数据。第一预设阈值;至少一个处理器通过以下方式确定另一导航数据的状态,其中,另一导航数据为N个导航数据中的第一导航数据之后的导航数据,其中:如果导航数据在时刻t的状态i高,当时刻t的导航数据信号强度i+1小于第二预设阈值,确定t时刻导航数据的状态i+1低;或者如果导航数据在时刻t的状态i低,当时刻t的导航数据信号强度i+1大于或等于第三预设阈值,确定t时刻导航数据的状态i+1为高,其中1≥i≥n,i为整数,第二预设阈值大于第三预设阈值;和至少一处理器将所有状态为高的导航数据确定为M条导航数据。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 2. The method according to claim 1, wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and wherein the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data of the mobile terminal comprises:traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;determining, by the at least one processor, a status of first navigation data to be high, wherein the first navigation data is the first piece of navigation data of the N pieces of navigation data, with a signal strength greater than or equal to a first preset threshold;determining, by the at least one processor, a status of another piece of navigation data in the following manner, wherein the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data, wherein:if a status of navigation data at a moment ti is high, when a signal strength of navigation data at a moment ti+1 is less than a second preset threshold, determining a status of the navigation data at the moment ti+1 to be low; orif a status of navigation data at a moment ti is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti+1 to be high, wherein 1≤i≤n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is as high as the M pieces of navigation data.(String), 12.根据权利要求10所述的方法,其中至少一处理器从N个导航数据中取得M个导航数据包含:其中,N个导航数据分别对应一个时刻和一个信号强度,N个导航数据对应时刻t1,吨2,...,和TN分别按照时刻的先后顺序;至少一处理器根据时刻的先后顺序遍历N条导航数据的信号强度;至少一处理器取得N个导航数据中第一个导航数据之前的先前导航数据的状态,其中先前导航数据对应的时刻t0先于时刻t1对应第一条导航数据,时刻to与时刻t相邻1;至少一个处理器通过以下方式确定N条导航数据的状态:如果导航数据在时刻t的状态i−1高,当时刻t的导航数据信号强度i小于第二预设阈值,确定t时刻导航数据的状态i低;或者若某时刻导航数据状态低,当某时刻导航数据信号强度ti大于或等于第三预设阈值,确定t时刻导航数据的状态i为高,其中1≤i≤n,i为整数,第二预设阈值大于第三预设阈值;和至少一处理器将所有状态为高的导航数据确定为M条导航数据。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 3. The method according to claim 1, wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data of the mobile terminal comprises:wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and wherein the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;obtaining, by the at least one processor, a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, wherein a moment to corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment t0 is adjacent to the moment t1;determining, by the at least one processor, statuses of the N pieces of navigation data in the following manner:if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment ti is less than a second preset threshold, determining a status of the navigation data at the moment ti to be low; orif a status of navigation data at a moment ti−1 is low, when a signal strength of navigation data at a moment ti is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti to be high, wherein 1≤i≤n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is high as the M pieces of navigation data.(String), 13.根据权利要求10所述的方法,其中每个导航数据对应一个时刻,每个位置变化数据对应一个时刻,其中当m个时刻th一条导航数据与n的时刻相同th一段位置变化数据,mth一条导航数据被设置为匹配nth位置变化数据;和其中,所述至少一个处理器对M条导航数据和K条位置变化数据进行融合处理,得到移动终端在第一时间段内的位置信息,包括:至少一处理器从M个导航数据和K个位置变化数据中获取相互匹配的导航数据和位置变化数据;和所述至少一个处理器将匹配的导航数据和位置变化数据进行合并,并结合未合并的位置变化数据,获取移动终端在第一时间段内的位置信息。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 4. The method according to claim 1, wherein each of the navigation data corresponds to one moment, and each of the position change data corresponds to one moment;and when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; andwherein the combining, by the at least one processor, the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor, navigation data and position change data that match each other from the M pieces of navigation data and the K pieces of position change data; andcombining, by the at least one processor, the navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtaining the position information of the mobile terminal in the first time period.(String), 14.根据权利要求10所述的方法,其中导航数据为利用卫星导航信号计算得到的待计算位置坐标的数据,其中,所述至少一个处理器对所述M个导航数据和所述K个导航数据进行融合处理位置变化数据,获取移动终端在第一时间段内的位置信息,包括:至少一处理器根据M个导航数据计算得到M个位置坐标;和至少一个处理器将M个位置坐标与K个位置变化数据结合,得到移动终端在第一时间段内的位置信息。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 5. The method according to claim 1, wherein the navigation data is data obtained through calculation by using the satellite navigation signal and from which position coordinates are to be calculated, and the combining, by the at least one processor, the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor through calculation, M position coordinates according to the M pieces of navigation data; andcombining, by the at least one processor, the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period.(String), 15.根据权利要求10所述的方法,其中导航数据是位置坐标。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 6. The method according to claim 1, wherein the navigation data is position coordinates.(String), 16.根据权利要求10所述的方法,其中至少一个处理器在第一时间段内保持睡眠状态;和至少一个处理器在第一时间段过去后被唤醒。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 7. The method according to claim 1, whereinthe at least one processor remains in a sleep state during the first time period; andthe at least one processor is woken up after the first time period elapses.(String), 17.根据权利要求10所述的方法,其中该方法还包括:至少一个处理器在第一时间段内获取到移动终端的位置信息后进入休眠状态。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 8. The method according to claim 1, wherein the method further comprises:entering, by the at least one processor, a sleep state after obtaining the position information of the mobile terminal in the first time period.(String), 18.根据权利要求10所述的方法,其中移动终端在第一时间段的位置信息包括至少两个位置坐标,其中每个位置坐标对应于第一时间段的一个时刻。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 9. The method according to claim 1, wherein the position information of the mobile terminal in the first time period comprises at least two position coordinates, and wherein each of the position coordinates corresponds to one moment of the first time period.(String), 19.移动终端,包括至少一个处理器、一个全球导航卫星系统(GNSS)接收器和一个传感器,其中GNSS接收器配置为:在第一时间段期间从一个或多个GNSS导航卫星接收卫星导航信号;将移动终端的N条导航数据存储在第一缓存中,N为整数,N条导航数据是利用第一时间段接收到的卫星导航信号计算得到的;和从卫星导航信号计算导航数据,其中导航数据是要计算位置坐标的数据或者导航数据是位置坐标;传感器配置为:监测第一时间段移动终端的运动数据;将移动终端的K个位置变化数据存储在第二缓冲区中,其中K≤l,K为整数,K个位置变化数据是利用第一阶段移动终端的运动数据计算得到的时间段;和至少一个处理器被配置为:在经过第一时间段后,从第一缓存中的移动终端的N条导航数据中获取M条导航数据,其中N≤M,M≤1,M为整数;在经过第一时间段后,获取第二缓冲区中移动终端的K条位置变化数据;和结合M条导航数据和K条位置变化数据,得到移动终端在第一时间段内的位置信息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 10. A positioning method for a mobile terminal, wherein the mobile terminal comprises at least one processor and a global navigation satellite system (GNSS) receiver, and the method comprises:receiving, by the GNSS receiver and from one or more GNSS navigation satellites, a satellite navigation signal during a first time period;obtaining through calculation N pieces of navigation data according to the satellite navigation signal, and buffering the N pieces of navigation data in a first buffer, wherein N≥1, and N is an integer;monitoring, during the first time period, movement data of the mobile terminal by using a sensor of the mobile terminal;obtaining through calculation K pieces of position change data of the mobile terminal according to the data obtained by the sensor through monitoring, and buffering the K pieces of position change data in a second buffer, wherein K≥1, and K is an integer;obtaining, by the at least one processor after the first time period elapses, M pieces of navigation data from the N pieces of navigation data in the first buffer, wherein N≥M, M≥1, and M is an integer; andperforming, by the at least one processor, fusion processing on the M pieces of navigation data and the K pieces of position change data in the second buffer, to obtain position information of the mobile terminal in the first time period.(String), 20.根据权利要求19所述的移动终端,其中第一时间段包括第二时间段,GNSS接收器在第二时间段处于休眠状态;和传感器在第一时间段处于工作状态。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 11. The method according to claim 10, wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data comprises:wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;determining, by the at least one processor, a status of first navigation data to be high, wherein the first navigation data is the first piece of navigation data, of the N pieces of navigation data, with a signal strength greater than or equal to a first preset threshold;determining, by the at least one processor, a status of another piece of navigation data in the following manner, wherein the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data, wherein:if a status of navigation data at a moment ti is high, when a signal strength of navigation data at a moment ti+1 is less than a second preset threshold, determining a status of the navigation data at the moment ti+1 to be low; orif a status of navigation data at a moment ti is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti+1 to be high, wherein 1≥i≥n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is high as the M pieces of navigation data.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 12. The method according to claim 10, wherein the obtaining, by the at least one processor, M pieces of navigation data from the N pieces of navigation data comprises:wherein each of the N pieces of navigation data corresponds to one moment and one signal strength, and the N pieces of navigation data correspond to moments t1, t2, . . . , and tN respectively according to an order of the moments;traversing, by the at least one processor according to the order of the moments, signal strengths of the N pieces of navigation data;obtaining, by the at least one processor, a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, wherein a moment to corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment to is adjacent to the moment t1;determining, by the at least one processor, statuses of the N pieces of navigation data in the following manner:if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment ti is less than a second preset threshold, determining a status of the navigation data at the moment ti to be low; orif a status of navigation data at a moment is low, when a signal strength of navigation data at a moment ti is greater than or equal to a third preset threshold, determining a status of the navigation data at the moment ti to be high, wherein 1≤i≤n, i is an integer, and the second preset threshold is greater than the third preset threshold; anddetermining, by the at least one processor, all navigation data whose status is high as the M pieces of navigation data.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 13. The method according to claim 10, wherein each of the navigation data corresponds to one moment, and each of the position change data corresponds to one moment, and wherein when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; andwherein the performing, by the at least one processor, fusion processing on the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor, navigation data and position change data that match each other from the M pieces of navigation data and the K pieces of position change data; andcombining, by the at least one processor, the navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtaining the position information of the mobile terminal in the first time period.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 14. The method according to claim 10, wherein the navigation data is data obtained through calculation by using the satellite navigation signal and from which position coordinates are to be calculated, and wherein the performing, by the at least one processor, fusion processing on the M pieces of navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period comprises:obtaining, by the at least one processor through calculation, M position coordinates according to the M pieces of navigation data; andcombining, by the at least one processor, the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 15. The method according to claim 10, wherein the navigation data is position coordinates.(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 16. The method according to claim 10, whereinthe at least one processor remains in a sleep state during the first time period; andthe at least one processor is woken up after the first time period elapses.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 17. The method according to claim 10, wherein the method further comprises:entering, by the at least one processor, a sleep state after obtaining the position information of the mobile terminal in the first time period.(String), 1(Integer), 16(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 18. The method according to claim 10, wherein the position information of the mobile terminal in the first time period comprises at least two position coordinates, and wherein each of the position coordinates corresponds to one moment of the first time period.(String), 1(Integer), 17(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 19. A mobile terminal, comprising at least one processor, a global navigation satellite system (GNSS) receiver, and a sensor, whereinthe GNSS receiver is configured to:receive, from one or more GNSS navigation satellites, a satellite navigation signal during a first time period;store N pieces of navigation data of the mobile terminal in a first buffer, wherein N is an integer, and wherein the N pieces of navigation data are obtained through calculation by using the satellite navigation signal received during the first time period; andcalculate navigation data from the satellite navigation signal, wherein the navigation data is data from which position coordinates are to be calculated or the navigation data is position coordinates;the sensor is configured to:monitor movement data of the mobile terminal during the first time period;store K pieces of position change data of the mobile terminal in a second buffer, wherein K≤l, K is an integer, and the K pieces of position change data are obtained through calculation by using the movement data of the mobile terminal during the first time period; andthe at least one processor is configured to:obtain, after the first time period elapses, M pieces of navigation data from the N pieces of navigation data of the mobile terminal in the first buffer, wherein N≤M, M≤1, and M is an integer;obtain, after the first time period elapses, the K pieces of position change data of the mobile terminal in the second buffer; andcombine the M pieces of navigation data and the K pieces of position change data to obtain position information of the mobile terminal in the first time period.(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:11.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185953(Integer), 20. The mobile terminal according to claim 19, whereinthe first time period comprises a second time period,the GNSS receiver is in a sleep state during the second time period; andthe sensor is in a working state during the first time period.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185953(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a national stage of International Application No. PCT/CN2015/094224, filed on Nov. 10, 2015, which claims priority to International Application No. PCT/CN2015/091138, filed on Sep. 29, 2015. Both of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present invention relate to communications technologies, and in particular, to a positioning method and apparatus for a mobile terminal, and a mobile terminal. BACKGROUND [0003]A global navigation satellite system (Global Navigation Satellite System, GNSS) is a generic term for a type of system that uses a navigation satellite to implement positioning. The GNSS can obtain user coordinates over the globe, and is a widely used positioning technology. However, in urban areas, due to reflection and blockage of a navigation signal, drifting usually exists in a positioning result or even positioning cannot be implemented. Dead reckoning (Dead Reckoning, DR) is a technology that uses a sensor module (such as an accelerometer, a gyroscope, and a magnetic field sensor) of a mobile terminal to calculate a relative position of a moving user. The dead reckoning does not rely on an external wireless signal, and can implement positioning when a navigation signal is blocked. However, accuracy of the DR deteriorates because errors are accumulated over time. [0004]In the prior art, two sets of positioning systems: the GNSS and the DR may be operated simultaneously to separately output positioning results, and a central processing unit (CPU) performs real-time fusion processing on the positioning results of the two sets of positioning systems to implement accurate positioning. However, real-time fusion processing performed by the CPU causes relatively high power consumption of a terminal. SUMMARY [0005]Embodiments of the present invention provide a positioning method and apparatus for a mobile terminal, and a mobile terminal, to resolve a prior-art problem of high power consumption of positioning services. [0006]According to a first aspect, an embodiment of the present invention provides a positioning method for a mobile terminal, where the mobile terminal includes a main processor, and the method includes: [0007]obtaining, by the main processor after a first time period elapses, M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal, where N≥M, M≥1, M and N are integers, and the N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period; [0008]obtaining, by the main processor after the first time period elapses, K pieces of buffered position change data of the mobile terminal, where K≥1, K is an integer, and the K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period; and [0009]combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. [0010]Optionally, the obtaining, by the main processor, M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal includes: [0011]where each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; [0012]traversing, by the main processor according to the order of the moments, signal strengths of the N pieces of navigation data; [0013]determining, by the main processor, a status of first navigation data to be high, where the first navigation data is the first piece of navigation data, of the N pieces of navigation data, with a signal strength greater than or equal to a first threshold; [0014]determining, by the main processor, a status of another piece of navigation data in the following manner, where the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data: if a status of navigation data at a moment t1 is high, when a signal strength of navigation data at a moment ti+1 is less than a second threshold, determining a status of the navigation data at the moment ti+1 to be low; or if a status of navigation data at a moment t1 is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third threshold, determining a status of the navigation data at the moment ti+1 to be high, where 1≤i≤n, i is an integer, and the second threshold is greater than the third threshold; and [0015]determining, by the main processor, all navigation data whose status is high as the M pieces of reliable navigation data. [0016]Optionally, the obtaining, by the main processor, M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal includes: [0017]where each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; [0018]traversing, by the main processor according to the order of the moments, signal strengths of the N pieces of navigation data; [0019]obtaining, by the main processor, a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, where a moment t0 corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment t0 is adjacent to the moment t1; [0020]determining, by the main processor, statuses of the N pieces of navigation data in the following manner: if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment ti is less than a second threshold, determining a status of the navigation data at the moment ti to be low; or if a status of navigation data at a moment ti−1 is low, when a signal strength of navigation data at a moment ti is greater than or equal to a third threshold, determining a status of the navigation data at the moment ti to be high, where 1≤i≤n, i is an integer, and the second threshold is greater than the third threshold; and determining, by the processor, all navigation data whose status is high as the M pieces of reliable navigation data. [0021]Optionally, each of the navigation data is corresponding to one moment, and each of the position change data is corresponding to one moment; and when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; and [0022]the combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period includes: [0023]obtaining, by the main processor, reliable navigation data and position change data that match each other from the M pieces of reliable navigation data and the K pieces of position change data; and [0024]combining, by the main processor, the reliable navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtaining the position information of the mobile terminal in the first time period. [0025]Optionally, the navigation data is data that is obtained through calculation by using the satellite navigation signal of the mobile terminal and from which position coordinates are to be calculated, and the combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period includes: [0026]obtaining, by the main processor through calculation, M position coordinates according to the M pieces of reliable navigation data; and [0027]combining, by the main processor, the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period. [0028]Optionally, the navigation data is position coordinates. [0029]Optionally, the method further includes: [0030]remaining, by the main processor, in a sleep state during the first time period; and [0031]being woken up, by the main processor, after the first time period elapses. [0032]Optionally, the method further includes: [0033]entering, by the main processor, a sleep state after obtaining the position information of the mobile terminal in the first time period. [0034]Optionally, the position information of the mobile terminal in the first time period includes at least two position coordinates, and each of the position coordinates is corresponding to one moment of the first time period. [0035]According to a second aspect, an embodiment of the present invention further provides a positioning method for a mobile terminal, where the mobile terminal includes a main processor, and the method includes: [0036]receiving a satellite navigation signal of the mobile terminal during a first time period; [0037]obtaining through calculation N pieces of navigation data according to the satellite navigation signal, and buffering the N pieces of navigation data, where N≥1, and N is an integer; [0038]monitoring, during the first time period, movement data of the mobile terminal by using a sensor of the mobile terminal; [0039]obtaining through calculation K pieces of position change data of the mobile terminal according to the movement data that is obtained by the sensor through monitoring, and buffering the K pieces of position change data, where K≥1, and K is an integer; [0040]obtaining, by the main processor after the first time period elapses, M pieces of reliable navigation data from the N pieces of navigation data, where N≥M, M≥1, and M is an integer; and [0041]combining, by the main processor, the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. [0042]Optionally, the method according to the second aspect may further include all the optional solutions in the first aspect. [0043]According to a third aspect, an embodiment of the present invention provides a positioning apparatus for a mobile terminal, including: [0044]an obtaining module, configured to obtain M pieces of reliable navigation data from N pieces of buffered navigation data of the mobile terminal after a first time period elapses, where N≥M, M≥1, M and N are integers, and the N pieces of navigation data are obtained through calculation by using a satellite navigation signal of the mobile terminal that is received during the first time period; where [0045]the obtaining module is further configured to obtain K pieces of buffered position change data of the mobile terminal after the first time period elapses, where K≥1, K is an integer, and the K pieces of position change data are obtained through calculation by using data that is obtained through monitoring by a sensor of the mobile terminal during the first time period; and [0046]a data processing module, configured to combine the M pieces of reliable navigation data and the K pieces of position change data, to obtain position information of the mobile terminal in the first time period. [0047]Optionally, each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; and [0048]the obtaining module is specifically configured to: [0049]traverse signal strengths of the N pieces of navigation data according to the order of the moments; [0050]determine a status of first navigation data to be high, where the first navigation data is the first piece of navigation data, of the N pieces of navigation data, with a signal strength greater than or equal to a first threshold; [0051]determine a status of another piece of navigation data in the following manner, where the another piece of navigation data is navigation data, following the first navigation data, of the N pieces of navigation data: if a status of navigation data at a moment ti is high, when a signal strength of navigation data at a moment ti+1 is less than a second threshold, determine a status of the navigation data at the moment ti+1 to be low; or if a status of navigation data at a moment ti is low, when a signal strength of navigation data at a moment ti+1 is greater than or equal to a third threshold, determine a status of the navigation data at the moment ti+1 to be high, where 1≤i≤n, i is an integer, and the second threshold is greater than the third threshold; and determine all navigation data whose status is high as the M pieces of reliable navigation data. [0052]Optionally, each of the N pieces of navigation data is corresponding to one moment and one signal strength, and the N pieces of navigation data are corresponding to moments t1, t2, . . . , and tN respectively according to an order of the moments; and [0053]the obtaining module is specifically configured to: [0054]traverse signal strengths of the N pieces of navigation data according to the order of the moments; and obtain a status of previous navigation data preceding the first piece of navigation data of the N pieces of navigation data, where a moment t0 corresponding to the previous navigation data is prior to the moment t1 corresponding to the first piece of navigation data, and the moment t0 is adjacent to the moment t1; [0055]determine statuses of the N pieces of navigation data in the following manner: if a status of navigation data at a moment ti−1 is high, when a signal strength of navigation data at a moment t1 is less than a second threshold, determine a status of the navigation data at the moment ti to be low; or if a status of navigation data at a moment ti−1 is low, when a signal strength of navigation data at a moment t1 is greater than or equal to a third threshold, determine a status of the navigation data at the moment ti to be high, where 1≤i≤n, and the second threshold is greater than the third threshold; and [0056]determine all navigation data whose status is high as the M pieces of reliable navigation data. [0057]Optionally, each of the navigation data is corresponding to one moment, and each of the position change data is corresponding to one moment; and when a moment of the mth piece of navigation data is the same as a moment of the nth piece of position change data, the mth piece of navigation data is set to match the nth piece of position change data; and [0058]the data processing module is specifically configured to: [0059]obtain reliable navigation data and position change data that match each other from the M pieces of reliable navigation data and the K pieces of position change data; and [0060]combine the reliable navigation data and the position change data that match each other, and in combination with position change data that is not combined, obtain the position information of the mobile terminal in the first time period. [0061]Optionally, the navigation data is data that is obtained through calculation by using the satellite navigation signal of the mobile terminal and from which position coordinates are to be calculated; and the data processing module is specifically configured to: [0062]obtain through calculation M position coordinates according to the M pieces of reliable navigation data; and [0063]combine the M position coordinates and the K pieces of position change data, to obtain the position information of the mobile terminal in the first time period. [0064]Optionally, the apparatus further includes: [0065]a wake-up module, configured to wake up the positioning apparatus after the first time period elapses; where [0066]the positioning apparatus is in a sleep state during the first time period. [0067]Optionally, the apparatus further includes: [0068]a sleep module, configured to enable the positioning apparatus to enter a sleep state after the position information of the mobile terminal in the first time period is obtained. [0069]According to a fourth aspect, an embodiment of the present invention provides a mobile terminal, including a main processor, a global navigation satellite system GNSS receiver, a sensor, and a coprocessor, where [0070]the main processor is configured to execute any one of the foregoing methods; [0071]the GNSS receiver is configured to: receive a satellite navigation signal of the mobile terminal during a first time period, and calculate navigation data from the satellite navigation signal, where the navigation data is data from which position coordinates are to be calculated or the navigation data is position coordinates; [0072]the sensor is configured to monitor movement data of the mobile terminal during the first time period; and [0073]the coprocessor is configured to obtain through calculation K pieces of position change data according to the movement data that is obtained by the sensor through monitoring; or the coprocessor is configured to: obtain through calculation K pieces of position change data according to the movement data that is obtained by the sensor through monitoring, and calculate the position coordinates from the navigation data. [0074]Optionally, the first time period includes a second time period, and the global navigation satellite system GNSS receiver is in a sleep state during the second time period; and the sensor is in a working state during the first time period. [0075]In the embodiments of the present invention, N pieces of navigation data and K pieces of position change data that are obtained during a first time period are separately buffered. A main processor may obtain the K pieces of position change data after the first time period elapses, obtain M pieces of reliable navigation data from the N pieces of buffered navigation data, and combine the reliable navigation data and the position change data, to obtain position information of a mobile terminal. During a process of obtaining the N pieces of navigation data and the K pieces of position change data, the main processor does not need to be turned on in real time, thereby reducing positioning power consumption of a system. BRIEF DESCRIPTION OF DRAWINGS [0076]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0077]FIG. 1 is a schematic diagram of a frame structure of a mobile terminal according to an embodiment of the present invention; [0078]FIG. 2 is a schematic diagram of a frame structure of another mobile terminal according to an embodiment of the present invention; [0079]FIG. 3 is a schematic flowchart of a positioning method for a mobile terminal according to an embodiment of the present invention; [0080]FIG. 4 is a schematic diagram of an operating manner of a GNSS receiver and a DR module according to an embodiment of the present invention; [0081]FIG. 5 is a schematic flowchart of a method for obtaining reliable navigation data according to an embodiment of the present invention; [0082]FIG. 6 is a schematic flowchart of a specific implementation manner of the method for obtaining reliable navigation data in FIG. 5; [0083]FIG. 7 is a schematic flowchart of another method for obtaining reliable navigation data according to an embodiment of the present invention; and [0084]FIG. 8 is a schematic structural diagram of a positioning apparatus for a mobile terminal according to an embodiment of the present invention. DESCRIPTION OF EMBODIMENTS [0085]To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0086]In the embodiments of the present invention, a GNSS positioning technology and a DR positioning technology are combined to improve positioning performance, and a main processor combines a GNSS positioning result and a DR positioning result in a non-real-time manner to reduce positioning power consumption. [0087]Specifically, GNSS is a generic term for a type of system that uses a navigation satellite to implement positioning, and may include America's Global Positioning System (Global Positioning System, GPS), Russia's GLONASS (GLONASS), Europe's Galileo (Galileo), China's BeiDou System, Japan's Quasi-Zenith Satellite System (Quasi-Zenith Satellite System, QZSS), and so on. The GNSS can be used to obtain user coordinates over the globe, and is a widely used positioning technology. However, in urban areas, a navigation signal is likely to be reflected or blocked by buildings, drifting exists in a positioning result or even positioning cannot be implemented by using the GNSS positioning technology. [0088]The DR positioning technology uses a sensor module (such as an accelerometer, a gyroscope, and a magnetic field sensor) of a mobile terminal to calculate a relative position of a moving user. The DR positioning technology does not rely on an external wireless signal, and can implement positioning when a navigation signal is blocked. However, accuracy of DR positioning deteriorates as errors are accumulated over time. [0089]FIG. 1 is a schematic diagram of a frame structure of a mobile terminal according to an embodiment of the present invention. Referring to FIG. 1, the mobile terminal includes components such as a GNSS receiver 10, a sensor 20, a main processor 30, a coprocessor 40, a first storage unit 50, and a second storage unit 43. The components communicate with each other by using one or more buses. It can be understood by a person skilled in the art that the structure of the mobile terminal shown in the figure does not constitute any limitation on the present invention. The structure may be either a bus structure or a star structure, and may include more or less components than those shown in the figure, or may combine some parts, or may have a component layout different from that in the figure. The mobile terminal may be any mobile or portable electronic device, and includes but is not limited to a mobile phone, a mobile computer, a tablet computer, a personal digital assistant (Personal Digital Assistant, PDA), a navigation apparatus, a mobile internet device (Mobile Internet Device, MID), or a wearable device (Wearable Device). [0090]The GNSS receiver 10 is configured to: receive a navigation signal transmitted by a GNSS navigation satellite, and calculate data such as a pseudorange, a navigation message, and a signal strength from the navigation signal. The GNSS receiver 10 may be a GNSS receiver, a GNSS positioning chip, and the like. A satellite of one of the GPS, the GLONASS, the Galileo, the BeiDou System, the QZSS, or another system may be used for navigation (a single-mode receiver), or more than one system may be simultaneously used to implement positioning (a multi-mode receiver). The main processor 30 obtains through calculation position coordinates of a user according to the data such as the pseudorange, the navigation message, and the signal strength. The GNSS receiver may include an integrated circuit, such as a GNSS chip. The GNSS receiver includes a first buffer 11, configured to buffer data such as a measurement and a navigation message. The first buffer 11 is a storage area integrated in the GNSS receiver and may include an integrated circuit. [0091]The sensor 20 may include an accelerometer, a gyroscope, a magnetic field sensor, and the like. The sensor 20 is connected to the coprocessor 40 by using a transmission circuit, such as an I2C bus, and transmits physical data obtained through measurement by the sensor 20 to the coprocessor 40 for processing. [0092]The main processor 30 and the coprocessor 40 are control centers of the mobile terminal; are connected to various parts of the entire electronic device by using various interfaces and lines; and run or execute a software program and/or a module stored in the storage unit and invoke data stored in the storage unit, to implement various functions of the electronic device and/or process data. The main processor 30 and the coprocessor 40 may include an integrated circuit (Integrated Circuit, IC for short), for example, may include a single packaged IC, or may include multiple packaged ICs with a same function or different functions. For example, the main processor 30 and coprocessor 40 may include only a central processing unit (Central Processing Unit, CPU), or may include a combination of a graphics processing unit (Graphics Processing Unit, GPU), a digital signal processor (Digital Signal Processor, DSP for short), and a control chip (for example, a baseband chip) of a communications unit. In this embodiment of the present invention, the CPU may be a single-core processor or a multi-core processor. [0093]The main processor 30 has higher power consumption due to its greater processing capability and more complex circuit structure. The coprocessor has lower power consumption due to its weaker processing capability and simpler circuit structure. For example, the coprocessor may include a microcontroller unit (Microcontroller Unit, MCU), or may be implemented by using a sensor hub (Sensor Hub) technology. The first storage unit 50 is configured to provide the main processor 30 with a storage capacity required for code storage and processing. [0094]The coprocessor 40 includes a second buffer 41, configured to buffer user position change information that is obtained by processing the physical data output by the sensor module. The second storage unit 43 is configured to provide the coprocessor 40 with a storage capacity required in a code storage and processing process. The first storage unit 50 and the second storage unit 43 may be configured to store a software program and a module. The main processor 30 and the coprocessor 40 run the software program and the module stored in the first storage unit 50 and the second storage unit 43, to implement various functions and applications of the mobile terminal and implement data processing. The first storage unit 50 and the second storage unit 43 include a program storage area and a data storage area. The program storage area may store an operating system, and an application program required for at least one function, such as an audio playback program and an image playback program. The data storage area may store data created during the use of the mobile terminal (such as audio data and a phone book), and so on. In this embodiment of the present invention, the first storage unit 50 and the second storage unit 43 may include a volatile memory, such as a nonvolatile dynamic random access memory (Nonvolatile Random Access Memory, NVRAM), a phase-change random access memory (Phase Change RAM, PRAM), and a magnetoresistive random access memory (Magetoresistive RAM, MRAM); and may include a nonvolatile memory, such as at least one disk storage device, an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), and a flash memory device, such as a NOR flash memory (NOR flash memory) or a NAND flash memory (NAND flash memory). The nonvolatile memory stores the operating system and the application program executed by the main processor 30 and the coprocessor 40. The main processor 30 and the coprocessor 40 load a running program and data from the nonvolatile memory into a memory and store digital content in a large-capacity storage apparatus. The operating system includes various components and/or drivers that are used to control and manage a conventional system task, such as memory management, storage device control, and power management, and that facilitate communication between various hardware and software. In this embodiment of the present invention, the operating system may be the Android system of Google, the iOS system developed by Apple, the Windows operating system developed by the Microsoft Corporation, or the like, or an embedded operating system such as Vxworks. [0095]A buffer is a type of storage unit, can be quickly read and written, and is generally implemented by using a register circuit. The first buffer 11 is configured to buffer data that the GNSS receiver 10 needs to transmit to the main processor 30. The second buffer 41 is configured to buffer data that the coprocessor 40 needs to transmit to the main processor 40. [0096]FIG. 2 is a schematic diagram of a frame structure of another mobile terminal according to an embodiment of the present invention. Referring to FIG. 2, on the basis of the mobile terminal provided in the embodiment shown in FIG. 1, a GNSS receiver 10 is not connected to a main processor 30 by using a bus, but is directly connected to a coprocessor 40 by using a transmission circuit. For example, the transmission circuit may be a universal asynchronous receiver/transmitter (Universal Asynchronous Receiver/Transmitter, UART). [0097]The mobile terminal shown in FIG. 1 receives, by using a GNSS receiver 10, a navigation signal sent by a GNSS navigation satellite, calculates data such as a pseudorange, a navigation message, and a signal strength according to the navigation signal, and buffers the data into a first buffer 11 of the GNSS receiver 10. During processing, a main processor 30 reads the data such as the pseudorange, the navigation message, and the signal strength from the first buffer 11 and calculates corresponding position coordinates of a user. [0098]Compared with the mobile terminal shown in FIG. 1, no first buffer is provided in the GNSS receiver 10 of the mobile terminal shown in FIG. 2. After receiving a navigation signal transmitted from a GNSS navigation satellite and calculating data such as a pseudorange, a navigation message, and a signal strength according to the navigation signal, the GNSS receiver 10 does not buffer the data, but directly transmits the data to a coprocessor 40 by using a transmission circuit. The coprocessor 40 calculates position coordinates of a user in real time according to the data such as the pseudorange, the navigation message, and the signal strength, and buffers the position coordinates of the user into a second buffer 41 of the coprocessor 40. [0099]The embodiments of the present invention may be applied to a non-real-time positioning scenario. For example, when a user is running, a mobile phone may be used to record a running track. During a process of recording, the mobile phone may be in a screen-off (screen-turnoff) state, that is, a main processor is in a sleep state. In this case, the phone does not calculate a current position in real time but buffers GNSS and DR data, and after the main processor is woken up, calculates coordinates of a running track of the user according to the buffered data. [0100]The technical solutions of the present invention are described in detail with reference to specific embodiments below. The following specific embodiments may be combined with each other, and a same or similar concept or process may not be repeated in some embodiments. [0101]FIG. 3 is a schematic flowchart of a positioning method for a mobile terminal according to an embodiment of the present invention. The positioning method shown in FIG. 3 can be implemented by the mobile terminal shown in FIG. 1 or FIG. 2. Referring (String), 交叉引用相关申请 [0001] 本申请为 2015 年 11 月 10 日提交的国际申请号 PCT/CN2015/094224 的国家阶段,其要求于 2015 年 9 月 29 日提交的国际申请号 PCT/CN2015/091138 的优先权。 上述申请通过引用整体并入本文。 技术领域 [0002] 本发明实施例涉及通信技术,尤其涉及一种移动终端的定位方法、装置及移动终端。 背景 [0003] 全球导航卫星系统(Global Navigation Satellite System,GNSS)是利用导航卫星实现定位的一类系统的总称。 GNSS可以获取全球用户坐标,是一种应用广泛的定位技术。 但是在市区,由于导航信号的反射和遮挡,定位结果通常会出现漂移,甚至无法定位。 航位推算(Dead Reckoning,DR)是一种利用移动终端的传感器模块(如加速度计、陀螺仪、磁场传感器等)计算移动用户的相对位置的技术。 航位推算不依赖外部无线信号,可以在导航信号受阻时进行定位。 然而,由于误差随着时间的推移而累积,DR 的准确性会下降。 [0004] 现有技术中,GNSS和DR两套定位系统可以同时运行,分别输出定位结果,中央处理器(CPU)对两组定位的定位结果进行实时融合处理 系统实现精准定位。 但是,CPU进行实时融合处理会导致终端的功耗较高。 概括 [0005] 本发明实施例提供一种移动终端的定位方法、装置及移动终端,以解决现有技术中定位业务的高功耗问题。 [0006] 根据第一方面,本发明实施例提供一种移动终端的定位方法,所述移动终端包括主处理器,所述方法包括: [0007] 主处理器经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠的导航数据,其中N≥M,M≥1,M和N为整数,N条 导航数据的个数是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的; [0008] 主处理器在经过第一时间段后得到移动终端缓存的K条位置变化数据,其中K≥1,K为整数,K条位置变化数据是利用数据计算得到的 由移动终端的传感器在第一时间段内监测得到; 和 [0009] 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0010] 可选的,主处理器从移动终端缓存的N个导航数据中获取M个可靠导航数据包括: [0011] 其中N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; [0012] 主处理器按照矩的顺序遍历N个导航数据的信号强度; [0013] 主处理器确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据 ; [0014]主处理器通过如下方式确定另一条导航数据的状态,其中该另一条导航数据是N条导航数据中在第一条导航数据之后的导航数据: 如果是导航状态 t时刻的数据 1 为高,当导航数据的信号强度在时刻 t i+1 小于第二阈值,确定时刻t的导航数据状态 i+1 低; 或者如果在时刻 t 的导航数据状态 1 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,确定导航数据在时刻t的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 和 [0015] 主处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0016] 可选的,主处理器从移动终端缓存的N个导航数据中获取M个可靠导航数据包括: [0017] 其中N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; [0018] 主处理器按照矩的顺序遍历N个导航数据的信号强度; [0019] 主处理器获取N个导航数据中第一个导航数据之前的前一个导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 ; [0020] 主处理器通过以下方式确定N条导航数据的状态:如果导航数据在时刻t的状态 i−1 为高,当导航数据的信号强度在时刻 t i 小于第二阈值,确定时刻t的导航数据状态 i 低; 或者如果在时刻 t 的导航数据状态 i−1 低,当导航数据的信号强度在时刻 t i 大于或等于第三阈值,确定导航数据在时刻t的状态 i 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0021] 可选的,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻; 当 m 的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一条位置变化数据; 和 [0022] 主处理器将M个可靠导航数据和K个位置变化数据组合,得到第一时间段内移动终端的位置信息包括: [0023] 主处理器从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据; 和 [0024] 主处理器结合可靠的导航数据和匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0025]可选地,所述导航数据为利用所述移动终端的卫星导航信号计算得到的待计算位置坐标的数据,主处理器将所述M个可靠导航数据与所述M个可靠导航数据相结合。 K条位置变化数据,获取移动终端在第一时间段的位置信息包括: [0026] 主处理器根据M个可靠导航数据计算得到M个位置坐标; 和 [0027] 主处理器结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0028] 可选地,导航数据是位置坐标。 [0029] 可选的,该方法还包括: [0030] 在第一时间段内由主处理器保持在睡眠状态; 和 [0031] 在第一个时间段过去后,被主处理器唤醒。 [0032] 可选的,该方法还包括: [0033] 主处理器在第一时间段内获得移动终端的位置信息后进入休眠状态。 [0034] 可选的,第一时间段内移动终端的位置信息包括至少两个位置坐标,每个位置坐标对应第一时间段的一个时刻。 [0035] 根据第二方面,本发明实施例还提供一种移动终端的定位方法,所述移动终端包括主处理器,所述方法包括: [0036] 在第一时间段接收移动终端的卫星导航信号; [0037] 根据卫星导航信号计算得到N个导航数据,并缓存N个导航数据,其中N≥1,N为整数。 [0038] 通过移动终端的传感器在第一时间段内监测移动终端的运动数据; [0039] 根据传感器监测得到的运动数据,计算得到移动终端的K条位置变化数据,并缓存K条位置变化数据,其中K≥1,K为整数。 [0040] 在经过第一时间段后,主处理器从N个导航数据中获取M个可靠导航数据,其中N≥M,M≥1,M为整数; 和 [0041] 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0042] 可选的,第二方面的方法还可以包括第一方面的所有可选方案。 [0043] 第三方面,本发明实施例提供一种移动终端的定位装置,包括: [0044] 获取模块,用于在经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠导航数据,其中N≥M,M≥1,M和N为整数,N条 导航数据的个数是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的; 在哪里 [0045] 获取模块,还用于在经过第一时间段后,获取移动终端缓存的K条位置变化数据,其中K≥1,K为整数,K条位置变化数据通过计算得到 移动终端的传感器在第一时间段内监测得到的数据; 和 [0046] 数据处理模块,用于将M个可靠导航数据和K个位置变化数据结合起来,得到第一时间段内移动终端的位置信息。 [0047]可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; 和 [0048] 获取模块具体用于: [0049] 按照矩的顺序遍历N个导航数据的信号强度; [0050] 确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据; [0051] 判断另一条导航数据状态的方式如下,其中该另一条导航数据是N条导航数据中在第一个导航数据之后的导航数据: 如果某时刻t的导航数据的状态 i 为高,当导航数据的信号强度在时刻 t i+1 小于第二个阈值,判断t时刻导航数据的状态 i+1 低; 或者如果在时刻 t 的导航数据状态 i 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,判断t时刻导航数据的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 将所有状态为高的导航数据确定为M个可靠导航数据。 [0052] 可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序; 和 [0053] 获取模块具体用于: [0054] 按照矩的顺序遍历N个导航数据的信号强度; 获取N个导航数据中第一个导航数据之前的前一个导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 ; [0055] N个导航数据的状态判断方法如下:如果某时刻t的导航数据的状态 i−1 为高,当导航数据的信号强度在时刻 t 1 小于第二个阈值,判断t时刻导航数据的状态 i 低; 或者如果在时刻 t 的导航数据状态 i−1 低,当导航数据的信号强度在时刻 t 1 大于或等于第三阈值,判断t时刻导航数据的状态 i 为高,其中1≤i≤n,第二阈值大于第三阈值; 和 [0056] 将所有状态为高的导航数据确定为M个可靠导航数据。 [0057] 可选的,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻; 当 m 的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一条位置变化数据; 和 [0058] 数据处理模块具体用于: [0059] 从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据; 和 [0060] 结合可靠的导航数据和相互匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0061]可选地,所述导航数据为利用所述移动终端的卫星导航信号计算得到的、用于计算位置坐标的数据; 数据处理模块具体用于: [0062] 根据M个可靠导航数据计算得到M个位置坐标; 和 [0063] 结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0064] 可选的,该装置还包括: [0065] 唤醒模块,用于在经过第一时间段后唤醒定位装置; 在哪里 [0066] 定位装置在第一时间段内处于休眠状态。 [0067] 可选的,该装置还包括: [0068] 休眠模块,用于在获取到移动终端在第一时间段内的位置信息后,使定位装置进入休眠状态。 [0069] 根据第四方面,本发明实施例提供一种移动终端,包括主处理器、全球导航卫星系统GNSS接收器、传感器和协处理器,其中 [0070] 主处理器,用于执行上述任一方法; [0071] GNSS接收器,用于在第一时间段内接收移动终端的卫星导航信号,并根据卫星导航信号计算导航数据,导航数据为计算位置坐标的数据或导航数据。 是位置坐标; [0072] 传感器用于监测第一时间段内移动终端的运动数据; 和 [0073] 协处理器,用于根据传感器监测得到的运动数据,计算得到K个位置变化数据。 或者,协处理器,用于根据传感器监测得到的运动数据,计算得到K个位置变化数据,并根据导航数据计算出位置坐标。 [0074] 可选地,所述第一时间段包括第二时间段,所述全球导航卫星系统GNSS接收机在第二时间段内处于休眠状态; 第一时间段内传感器处于工作状态。 [0075] 在本发明实施例中,分别缓存第一时间段获取的N个导航数据和K个位置变化数据。 主处理器可以在经过第一时间段后获取K个位置变化数据,从缓存的N个导航数据中获取M个可靠导航数据,将可靠导航数据和位置变化数据结合,得到位置 移动终端的信息。 在获取N个导航数据和K个位置变化数据的过程中,不需要实时开启主处理器,从而降低了系统的定位功耗。 附图说明 [0076] 为了更清楚地描述本发明实施例中的技术方案,下面对描述实施例所需的附图进行简要说明。 显然,以下描述中的附图示出了本发明的一些实施例,本领域普通技术人员在没有做出创造性劳动的情况下仍可以从这些附图中导出其他附图。 [0077] 图1是根据本发明实施例的移动终端的帧结构示意图; [0078] 图2为本发明实施例提供的另一种移动终端的帧结构示意图; [0079] 图3为本发明实施例提供的移动终端定位方法的流程示意图; [0080]图4是根据本发明实施例的GNSS接收器和DR模块的工作方式示意图; [0081] 图5为本发明实施例提供的可靠导航数据获取方法的流程示意图。 [0082] 图6是图5中获取可靠导航数据的方法的具体实施方式的流程示意图; [0083] 图7为本发明实施例提供的另一种可靠导航数据获取方法的流程示意图; 和 [0084] 图8为本发明实施例提供的移动终端定位装置的结构示意图。 具体实施方式 [0085] 为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。 显然,所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0086] 本发明实施例将GNSS定位技术和DR定位技术结合起来提高定位性能,主处理器将GNSS定位结果和DR定位结果以非实时方式结合起来,降低定位功率 消耗。 [0087] 具体来说,GNSS是利用导航卫星实现定位的一类系统的总称,可能包括美国的全球定位系统(Global Positioning System,GPS)、俄罗斯的格洛纳斯(GLONASS)、欧洲的伽利略(Galileo)、中国的北斗 系统,日本的准天顶卫星系统(Quasi-Zenith Satellite System,QZSS)等。 GNSS 可用于获取全球用户坐标,是一种应用广泛的定位技术。 然而,在市区,导航信号容易被建筑物反射或遮挡,定位结果存在漂移,甚至无法利用GNSS定位技术进行定位。 [0088] DR定位技术利用移动终端的传感器模块(如加速度计、陀螺仪、磁场传感器等)计算移动用户的相对位置。 DR定位技术不依赖外部无线信号,可以在导航信号受阻时进行定位。 然而,DR 定位的准确性会随着时间的推移累积误差而恶化。 [0089] 图1为本发明实施例提供的移动终端的帧结构示意图。 参考图1,移动终端包括诸如GNSS接收器等组件 10 , 一个传感器 20 , 主处理器 30 , 协处理器 40 ,第一存储单元 50 ,以及第二个存储单元 43 . 组件通过使用一条或多条总线相互通信。 本领域技术人员可以理解,图中所示的移动终端的结构并不构成对本发明的任何限制。 该结构可以是总线结构,也可以是星形结构,可以包括比图中所示更多或更少的元件,也可以组合一些部件,也可以有与图中不同的元件布局。 移动终端可以是任何移动或便携式电子设备,包括但不限于手机、移动电脑、平板电脑、个人数字助理(Personal Digital Assistant,PDA)、导航仪、移动互联网 设备(Mobile Internet Device,MID)或可穿戴设备(Wearable Device)。 [0090] GNSS 接收机 10 用于接收GNSS导航卫星发射的导航信号,并根据导航信号计算伪距、导航电文、信号强度等数据。 GNSS 接收机10 可以是GNSS接收器、GNSS定位芯片等。 GPS、GLONASS、Galileo、北斗系统、QZSS或其他系统之一的卫星可用于导航(单模接收机),也可同时使用多个系统实现定位( 多模式接收器)。 主处理器 30 根据伪距、导航电文、信号强度等数据计算出用户的位置坐标。 GNSS接收器可以包括集成电路,例如GNSS芯片。 GNSS接收器包括第一缓冲器 11 ,配置为缓冲数据,例如测量和导航消息。 第一个缓冲区 11 是集成在GNSS接收器中的存储区域并且可以包括集成电路。 [0091] 传感器 20 可以包括加速度计、陀螺仪、磁场传感器等。 传感器 20 连接到协处理器 40 使用I2C总线等传输电路,传输传感器测量得到的物理数据 20 到协处理器 40 用于处理。 [0092] 主处理器 30 和协处理器 40 是移动终端的控制中心; 通过各种接口和线路连接到整个电子设备的各个部分; 运行或执行存储单元中存储的软件程序和/或模块,并调用存储单元中存储的数据,以实现电子设备的各种功能和/或处理数据。 主处理器 30 和协处理器 40 可以包括集成电路(Integrated Circuit,简称IC),例如可以包括单个封装好的IC,也可以包括多个功能相同或不同的封装好的IC。 例如,主处理器 30 和协处理器 40 可以只包括中央处理单元(Central Processing Unit,CPU),也可以包括图形处理单元(Graphics Processing Unit,GPU)、数字信号处理器(Digital Signal Processor,简称DSP)和控制器的组合 通信单元的芯片(例如基带芯片)。 在本发明实施例中,CPU可以是单核处理器,也可以是多核处理器。 [0093] 主处理器 30 由于处理能力更强,电路结构更复杂,功耗也更高。 协处理器由于处理能力较弱,电路结构较简单,功耗较低。 例如,协处理器可以包括微控制器单元(Microcontroller Unit,MCU),也可以通过传感器集线器(Sensor Hub)技术实现。 第一存储单元 50 配置为提供主处理器 30 具有代码存储和处理所需的存储容量。 [0094] 协处理器 40 包括第二个缓冲区 41 ,用于缓存对传感器模块输出的物理数据进行处理得到的用户位置变化信息。 第二存储单元 43 配置为提供协处理器 40 具有代码存储和处理过程所需的存储容量。 第一存储单元 50 第二存储单元 43 可以被配置为存储软件程序和模块。 主处理器 30 和协处理器 40 运行存储在第一存储单元中的软件程序和模块 50 第二存储单元 43 ,实现移动终端的各种功能和应用,实现数据处理。 第一存储单元 50 第二存储单元 43 包括程序存储区和数据存储区。 程序存储区可以存储操作系统,以及至少一种功能所需的应用程序,例如音频播放程序和图像播放程序。 数据存储区可以存储移动终端使用过程中产生的数据(如音频数据和电话簿)等。 在本发明实施例中,第一存储单元 50 第二存储单元 43可以包括易失性存储器,例如非易失性动态随机存取存储器(Nonvolatile Random Access Memory,NVRAM)、相变随机存取存储器(Phase Change RAM,PRAM)和磁阻随机存取存储器(Magetoresistive RAM,MRAM) ; 并且可以包括非易失性存储器,例如至少一个磁盘存储设备、电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory,EEPROM)和闪存设备,例如NOR闪存(NOR 闪存)或 NAND 闪存(NAND 闪存)。 非易失性存储器存储操作系统和主处理器执行的应用程序 30 和协处理器 40 . 主处理器 30 和协处理器 40 将非易失性存储器中的运行程序和数据加载到存储器中,并将数字内容存储在大容量存储装置中。 操作系统包括各种组件和/或驱动程序,用于控制和管理常规系统任务,例如内存管理、存储设备控制和电源管理,并促进各种硬件和软件之间的通信。 在本发明实施例中,操作系统可以是谷歌的Android系统、苹果公司开发的iOS系统、微软公司开发的Windows操作系统等,也可以是Vxworks等嵌入式操作系统。 [0095] 缓冲器是一种存储单元,可以快速读写,一般采用寄存器电路实现。 第一个缓冲区 11 配置为缓冲 GNSS 接收器的数据 10 需要传输到主处理器 30 . 第二个缓冲区 41 配置为缓冲协处理器的数据 40 需要传输到主处理器 40 . [0096] 图2为本发明实施例提供的另一种移动终端的帧结构示意图。 参见图2,基于图1所示实施例提供的移动终端,一种GNSS接收机 10 未连接到主处理器 30 通过使用总线,但直接连接到协处理器 40 通过使用传输电路。 例如,传输电路可以是通用异步接收器/发送器(Universal Asynchronous Receiver/Transmitter,UART)。 [0097] 图1所示的移动终端通过使用GNSS接收器接收 10 ,GNSS导航卫星发送的导航信号,根据导航信号计算伪距、导航电文、信号强度等数据,并将数据缓存到第一缓冲区 11 GNSS 接收机 10 . 在处理过程中,主处理器 30 从第一个缓冲区中读取伪距、导航信息、信号强度等数据 11 计算用户对应的位置坐标。 [0098] 与图1所示的移动终端相比,在GNSS接收器中没有设置第一缓冲器 10 GNSS接收机接收到GNSS导航卫星发射的导航信号,根据导航信号计算伪距、导航电文、信号强度等数据后, 10 不缓存数据,而是直接将数据传输到协处理器 40 通过使用传输电路。 协处理器 40 根据伪距、导航电文、信号强度等数据实时计算出用户的位置坐标,并将用户的位置坐标缓存到第二缓冲区 41 协处理器 40 . [0099]本发明实施例可以应用于非实时定位场景。 例如,当用户在跑步时,可以使用手机记录跑步轨迹。 在录制过程中,手机可能处于熄屏(screen-turnoff)状态,即主处理器处于休眠状态。 在这种情况下,手机不会实时计算当前位置,而是缓存GNSS和DR数据,在主处理器唤醒后,根据缓存的数据计算用户的跑步轨迹坐标。 [0100] 下面结合具体实施例对本发明的技术方案进行详细说明。 以下具体实施例可以相互结合,相同或相似的概念或过程在某些实施例中不再赘述。 [0101] 图3为本发明实施例提供的移动终端定位方法的流程示意图。 图3所示的定位方法可以由图1或图2所示的移动终端实现。 参见图3,在本发明实施例中,移动终端包括主处理器,该方法包括以下步骤 . [0102] 小号 301 . 主处理器在经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠的导航数据,其中N≥M,M≥1,M和N为整数,N条导航数据 是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 [0103] 具体地,导航数据可以是根据卫星信号计算得到的中间数据,例如伪距、导航电文、信号强度等数据。 中间数据用于计算最终位置坐标。 或者,导航数据可以是根据卫星信号计算得到的位置坐标。 位置坐标可以是经纬度坐标,也可以是其他可以表示移动终端位置的坐标形式。 [0104] 当导航数据为伪距、导航消息、信号强度等中间数据时,图3所示的定位方法可以通过图1所示的移动终端来实现。 具体地,GNSS接收机 10 在第一时间段接收移动终端的卫星导航信号,根据卫星导航信号计算伪距、导航电文、信号强度等数据,并缓存伪距、导航电文等数据, 和信号强度进入第一个缓冲区 11 . 主处理器 30 可以根据伪距、导航信息、信号强度等数据计算出移动终端对应的位置坐标。 [0105] 当导航数据为位置坐标时,图3所示的定位方法可以由图2所示的移动终端来实现。 具体地,GNSS接收机 10 在第一时间段内接收移动终端的卫星导航信号,并根据卫星导航信号计算出伪距、导航电文、信号强度等中间数据。 协处理器 40 根据伪距、导航信息、信号强度等数据计算移动终端对应的位置坐标,并将位置坐标缓存到第二缓存中 41 . [0106] 具体来说,在第一个时间段内,GNSS 接收机 10 可以间歇性地计算伪距、导航电文、信号强度等数据,例如每隔1s或5s计算一次。 因此,在第一时间段内对应得到多个时间点的导航数据。 当获取导航数据对应的时刻时,可以根据卫星导航信号获取该时刻的信息,也可以通过时钟信号(例如协处理器的时钟)来标记导航数据对应的时刻 40),即系统的时间戳。 [0107] 缓存第一时间段的N条导航数据。 在经过第一时间段之后的第一时刻后,主处理器可以从缓存的N个导航数据中获取M个可靠导航数据。 第一时刻可以是第一时间段的最后时刻。 也就是说,在第一个时间段过去后,主处理器 30 可以读取缓冲的导航数据。 GNSS 接收机接收到的卫星信号的信号强度 10 可能不稳定。 当卫星信号的信号强度比较强时,根据卫星信号计算得到的导航数据是准确的,即可靠的。 当卫星信号的信号强度较弱时,根据卫星信号计算得到的导航数据可能不准确,即不可靠。 因此,主处理器 30 在读取缓存的导航数据时,获取M个可靠的导航数据。 [0108] 在缓存导航数据的过程中,主处理器 30 可能处于休眠状态以降低功耗。 然后是主处理器 30 唤醒后可以处理缓存的导航数据。 具体来说,主处理器可能有多种状态 30 . 例如,主处理器 30 第一时刻前处于休眠状态,主处理器 30 在第一时间被唤醒。 被唤醒后,主处理器 30 获取缓冲的导航数据。 如果第一时刻是第一时间段的最后时刻,主处理器 30 第一时间段处于休眠状态,主处理器 30 在第一个时间段过去后被唤醒。 被唤醒后,主处理器 30 获取缓冲的导航数据。 [0109] 具体来说,主处理器 30 可以定期唤醒,也可以通过设置的触发条件唤醒。 例如,当移动终端的屏幕打开时,主处理器被唤醒,或者在定位过程结束后,主处理器被唤醒。 [0110] 小号 302 . 主处理器在经过第一时间段后,获取移动终端缓存的K条位置变化数据,其中K≥1,K为整数,利用得到的数据计算得到K条位置变化数据 通过移动终端的传感器在第一时间段内进行监测。 [0111] 具体来说,在第一时间段内,传感器 20 监控移动设备的运动数据(例如,加速度计、陀螺仪或磁场传感器的观测数据),并将监控得到的运动数据传送给协处理器 40 . DR 模块在协处理单元中运行。 DR模块根据传感器监测得到的数据,计算出移动终端的K条位置变化数据(包括移动方向变化和相邻时刻之间的距离),即进行航位推算DR; 并将K条位置变化数据缓存到第二个缓冲区中 41 . 航位推算DR也可以间歇进行,例如每隔1s或5s一次,从而可以得到移动终端在相邻两个计算时刻之间的位置变化数据。 协处理器可以通过时钟电路记录每个计算时刻,并在保存K条位置变化数据时记录对应的计算时刻,即时间戳。 时间戳和K条位置变化数据一起缓存到第二个缓存中 41 . [0112] 在缓存K个位置变化数据的过程中,主处理器 30 可能处于休眠状态以降低功耗。 被唤醒时,主处理器 30 可以对缓存的K个位置变化数据进行处理。 [0113]可选地,在航位推算DR过程中,可以以固定的时间间隔计算位置变化数据,也可以在满足设定条件时计算。 例如,当检测到移动终端的移动距离超过设定的阈值时,计算移动终端的位置变化数据。 或者,可以根据时间间隔和空间移动距离确定是否需要计算移动终端的位置变化数据。 例如,设置时间间隔阈值和空间移动距离阈值,当满足任一阈值条件时,可以计算位置变化数据。 [0114] 可选地,GNSS接收器的时钟电路可以与协处理器的时钟电路异步。 N条导航数据和对应的时间戳保存在第一个缓冲区中 11 GNSS 接收机 10 . K个位置变化数据和对应的时间戳存储在第二个缓冲区中 41 协处理器 40 . [0115] 可选地,GNSS 接收器之间的时钟同步 10 和协处理器 40 可以使用同步时钟电路来实现。 在这种情况下,不需要保存N个导航数据对应的时间戳和K个位置变化数据对应的时间戳。 [0116] 需要说明的是,在本发明实施例中,步骤S的执行顺序 301 和步骤 S 302 不受限制。 脚步 301 可以先执行,或者步骤 S 302 可以先执行,也可以两步同时执行。 此外,在第一时间段内,GNSS接收器获取卫星导航信号和传感器监测移动终端移动数据的执行顺序不设限制。 [0117] 小号 303 . 主处理器结合M个可靠导航数据和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0118] 为了在保证移动终端能够正常定位的同时提高移动终端的定位精度,主处理器将M个可靠导航数据和K个位置变化数据进行合并。 [0119] 具体地,主处理器从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据。 主处理器结合可靠的导航数据和相互匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0120] 可靠导航数据的数​​量可以等于或小于位置变化数据的数量。 当可靠导航数据的数​​量与位置变化数据的数量相等且每个导航数据与一个位置变化数据匹配时,未合并的位置变化数据的数量为零。 即对所有位置变化数据和匹配的导航数据进行融合处理。 当可靠导航数据的数​​量小于位置变化数据的数量时,只对匹配的可靠导航数据和位置变化数据进行融合处理。 [0121] 具体地,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻。 当m的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一块位置变化数据。 那一刻的m th 一条导航数据与n的时刻相同 th 一条位置变化数据表示两个时刻的时间差在允许的误差范围内(即两个时刻的差小于或等于预设阈值)。 如果至少两个GNSS导航数据对应的坐标点与一个位置变化数据对应的同一个DR坐标点匹配,则只保留一个GNSS导航数据对应的坐标点。 为了降低功耗,GNSS导航数据的计算时间间隔可以长于位置变化数据的计算时间间隔,或者GNSS导航数据的计算时间间隔可以是位置变化数据的计算时间间隔的倍数 . [0122] 在主处理器将M个可靠导航数据与K个位置变化数据进行匹配的过程中,可选地,当GNSS接收机的时钟电路与协处理器的时钟电路异步时,主处理器进行匹配 根据第一缓存中M个可靠导航数据对应的时间戳和第二缓存中K个位置变化数据对应的时间戳,将时间戳相等或相同的导航数据和位置变化数据合并 最接近。 [0123] 可选地,当GNSS接收机的时钟电路与协处理器的时钟电路同步时,主处理器可以直接将同一时刻的导航数据和位置变化数据进行合并,而不需要通过时间戳进行匹配。 具体地,当导航数据为根据移动终端的卫星导航信号计算得到的位置坐标时,主处理器将相互匹配的可靠导航数据和位置变化数据进行组合,可以但不限于: 以下实施方式。 [0124] 主处理器得到匹配的导航数据和位置变化数据后,根据位置变化数据对应的时间点建立卡尔曼滤波过程。 根据卡尔曼滤波对匹配的可靠导航数据和位置变化数据进行融合处理的具体过程如下。 [0125] 在DR过程中可以得到用户在两个时刻的位置坐标的变化,据此可以得到卡尔曼滤波的状态方程: X k+1 =F k ·X k [0126] 其中,X为卡尔曼滤波中的待估计向量,具体可以包括用户坐标、用户运动方向等。 k表示待估计向量对应的矩; 和 F k 反映了向量 X 在两个相邻时刻的变化关系(即 k th 时刻和 (k+1) th 时刻,其中 k th 时刻在 (k+1) 之前 th 时刻),和 F k 是矩阵,可以根据DR模块的输出结果得到。 [0127] 此外,如果在 k th 时刻,有可靠的导航数据与位置变化数据相匹配,可靠的导航数据在 k th 时刻被标记为观察向量 Z k , 可以建立一个观测方程: Z k =H k ·X k [0128] 其中 H k 表示观测方程在 k 处的系数矩阵 th 片刻。 [0129] 本发明实施例中,可靠导航数据与位置变化数据相互匹配的卡尔曼滤波过程可以建立如下: [0130] (1)初始化卡尔曼滤波参数:X 0 和 P 0 . X 0 表示待估计向量的初始值,P 0 表示 X 的均方误差矩阵 0 初始化时。 [0131] (2) 进行一步预测:X k+1/k =F x ·X k , 其中 X k+1/k 表示一个预测向量,在 (k+1) th 时刻,根据k处的待估计向量得到 th 片刻。 [0132] (3) 对一个均方误差矩阵进行一步预测:P k+1/k =F k ·P k ·F k T +Q k , 其中 P k 表示 X 的均方误差矩阵 k 在 k th 片刻; 磷 k+1/k 表示预测的均方误差矩阵,在 (k+1) th 时刻,根据 k 处的均方误差矩阵得到 th 片刻; F k T 表示 F 的转置矩阵 k ; 和问 k 表示卡尔曼滤波系统的噪声协方差矩阵,用于表示状态方程的可靠程度。 [0133] (4) 计算一个滤波器增益:K k+1 =P k+1/k ·H k+1 T ·(H k+1 ·P k+1/k ·H k+1 T +R k+1 ) −1 [0134] 其中K k+1 表示卡尔曼滤波系统在 (k+1) 处的滤波增益 th 片刻; H k+1 T 表示 H 的转置矩阵 k+1 ; 和 R k+1 表示在 (k+1) 处观察到的噪声协方差 th 矩,用来表示观测方程的可靠程度。 [0135] (5) 计算可靠的导航数据和相互匹配的位置变化数据合并后的结果: X k+1 =X k+1/k +K k+1 ·(Z k+1 -H k+1 ·X k+1/k )。 [0136] (6) 更新均方误差矩阵:P k+1 =(I−K k+1 ·H k+1 )·P k+1/k ,其中 I 是单位矩阵。 [0137] 如果在 (k+1) th 此时,不存在与位置变化数据相匹配的可靠导航数据,本发明实施例根据卡尔曼滤波状态方程对未合并的位置变化数据建立卡尔曼滤波过程如下 : [0138] (1) 进行一步预测:X k+1/k =F k ·X k , 其中 X k+1/k 表示一个预测向量,在 (k+1) th 时刻,根据k处的待估计向量得到 th 片刻。 [0139] (2) 对一个均方误差矩阵进行一步预测:P k+1/k =F k ·P k ·F k T +Q k 其中P k 表示 X 的均方误差矩阵 k 在 k th 片刻; 磷 k+1/k 表示预测的均方误差矩阵,在 (k+1) th 时刻,根据 k 处的均方误差矩阵得到 th 片刻; F k T 表示 F 的转置矩阵 k ; 和问 k 表示卡尔曼滤波系统的噪声协方差矩阵,用于表示状态方程的可靠程度。 [0140] (3)更新待估计向量的结果:X k+1 =X k+1/k . [0141] (4) 更新均方误差矩阵:P k+1 =P k+1/k . [0142] GNSS接收机和DR模块在将可靠的导航数据和相互匹配的位置变化数据进行组合的过程中,可以具有但不限于以下几种操作方式。 [0143] GNSS接收机的一种工作方式是:GNSS接收机和DR模块全程开启,计算相应的导航数据和位置变化数据。 [0144]GNSS接收机的另一种工作方式是:DR模块全程开启,GNSS接收机间歇性开启(如图4所示)。 图4为本发明实施例提供的GNSS接收机和DR模块的工作方式示意图。 参见图4,在主处理器结合可靠导航数据和位置变化数据相互匹配的过程中,DR模块在整个过程中处于开启状态,而GNSS接收器则进入休眠状态或低电平状态。 开机一段时间后的耗电状态。 此外,还增加了在每个时间段开始时打开 GNSS 接收器的步骤。 当DR模块持续开启时,GNSS接收器的工作状态相对灵活,GNSS接收器可以根据预设规则交替处于工作状态和休眠状态。 例如,当DR模块和GNSS接收器在一段时间内都开启时,主处理器可以将相互匹配的导航数据和位置变化数据进行组合。 当DR模块开启而GNSS接收机休眠一段时间后,主处理器仅通过位置变化数据获取移动终端的位置信息。 [0145] 还有一种工作方式是:GNSS接收机和DR模块交替开启,即交替计算导航数据和位置变化数据。 在这种情况下,无需将导航数据与位置变化数据进行匹配或进行卡尔曼滤波。 只有导航数据时,根据导航数据获取位置坐标点。 当只有位置变化数据时,根据上一时刻的位置坐标点,递归得到位置坐标点。 [0146] 具体来说,在步骤 303 ,当导航数据是利用移动终端的卫星导航信号计算得到的数据,需要计算位置坐标时,主处理器将M个可靠导航数据与K 获取移动终端在第一时间段内的位置信息的位置变化数据包括: [0147] 主处理器根据M个可靠导航数据计算得到M个位置坐标; 和 [0148] 主处理器结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0149] 当导航数据为利用移动终端的卫星导航信号计算得到的用于计算位置坐标的中间数据(如伪码、导航电文、信号强度等)时, 主处理器不能直接结合中间数据和位置变化数据。 主处理器在进行融合处理前,首先从可靠的导航数据中计算出对应的位置坐标,然后通过卡尔曼滤波将M个位置坐标和K个位置变化数据结合起来,首先得到移动终端的位置信息。 时间段。 具体融合过程与上述方法相同,此处不再赘述。 [0150] 具体地,第一时间段内移动终端的位置信息包括至少两个位置坐标,每个位置坐标对应第一时间段的一个时刻。 [0151] 步骤 S 之后 303 ,本实施例还可以包括以下步骤。 [0152] 小号 304 . 主处理器在第一时间段内获得移动终端的位置信息后进入休眠状态。 [0153] 在获得移动终端的位置信息后,如果不需要处理其他任务,则主处理器可以进入休眠状态以降低功耗。 [0154]在本发明实施例中,分别缓存第一时间段内获取的N个导航数据和K个位置变化数据。 主处理器可以在经过第一时间段后获取K个位置变化数据,从缓存的N个导航数据中获取M个可靠导航数据,将可靠导航数据和位置变化数据结合,得到位置 移动终端的信息。 在获取N个导航数据和K个位置变化数据的过程中,不需要实时开启主处理器,从而降低了系统的定位功耗。 [0155] 具体地,步骤S中主处理器从移动终端缓存的N条导航数据中获取M条可靠的导航数据 101 可以通过但不限于以下两种可能的实现方式来实现。 [0156] 图5为本发明实施例提供的可靠导航数据获取方法的流程示意图。 图6是图5中获取可靠导航数据的方法的具体实施方式的流程示意图。 参见图5和图6,在一种可能的实施方式中,第一时间段之前的导航数据的状态不是 在第一个时间段之前确定或没有缓冲的导航数据。 如图5和图6所述,主处理器从移动终端缓存的N个导航数据中获取M个可靠的导航数据包括以下步骤。 [0157] 小号 501 . 主处理器按照矩的顺序遍历N个导航数据的信号强度。 [0158] N个导航数据中的每一个都对应一个时刻和一个信号强度。 N条导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照时刻的顺序。 [0159] 具体地,时刻的顺序是指按照时刻的时间顺序,在先的时刻为前时刻,后的时刻为后时刻。 [0160] 小号 502 . 主处理器确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据。 [0161] 第一时间段之前的导航数据的状态未确定或者第一时间段之前没有缓存的导航数据。 主处理器 30 根据第一阈值确定第一导航数据,以根据第一导航数据确定导航数据跟随第一导航数据的状态。 第一阈值可以预先设置。 具体来说,主处理器 30 根据时刻的顺序确定N条导航数据的信号强度(如图6所示)。 在判断过程中,判断信号强度大于或等于第一阈值的第一导航数据的导航数据的状态为高,并将导航数据判断为第一导航数据。 [0162] 具体来说,在 GNSS 导航期间,GNSS 接收机 10 接收来自多颗卫星的信号,每个卫星信号对应一个信号强度,信号强度一般用信噪比或载噪比来表示。 当某一时刻接收到的导航数据的信号强度(例如,时刻 T a ) 计算,卫星信号强度在时刻 T 分辨率的平均值 a 可以计算; 或在时刻 T 分辨率的卫星信号强度的最小值 a 可以计算; 或者可以计算A卫星信号强度的平均值,也可以计算A卫星信号强度最小值。 A卫星是所有可见卫星中按信号强度降序排列的第一个A卫星,A不大于B,B是T时刻所有可见卫星的数量 a . 可见卫星是 GNSS 接收器所在的卫星 10 可以接收导航信号。 [0163] 小号 503 . 处理器通过如下方式确定另一条导航数据的状态,其中,另一条导航数据是N条导航数据中在第一条导航数据之后的导航数据: 如果是当前导航数据的状态 吨 i 为高,当导航数据的信号强度在时刻 t i+1 小于第二阈值,确定导航数据在时刻t的状态 i+1 低; 或者如果在时刻 t 的导航数据状态 i 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,确定导航数据在时刻t的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值。 [0164] 具体地,处理器在确定第一导航数据之后的导航数据的状态时,可以根据第一导航数据的状态、第二阈值和第三阈值确定下一时刻导航数据的状态。 可以根据当前时刻的导航数据的状态确定每个导航数据在下一时刻的状态。 例如,假设某时刻导航数据的状态为 t 2 判断为高,导航数据在时刻t的信号强度是否 3 确定小于第二阈值。 如果此时导航数据的信号强度为 t 3 小于第二阈值,导航数据在t时刻的状态 3 确定为低。 如果此时导航数据的信号强度为 t 3 不小于第二阈值,t时刻导航数据的状态 3 确定为高。 假设某一时刻导航数据的状态为 t 2 判断为低,导航数据是否在t时刻的信号强度 3 大于第三阈值被确定。 如果此时导航数据的信号强度为 t 3 大于第三阈值,导航数据在t时刻的状态 3 确定为高。 如果此时导航数据的信号强度为 t 3 不大于第三阈值,t时刻导航数据的状态 3 确定为低。 [0165] 具体地,当移动终端进入建筑物时,导航信号容易被遮挡。 因此,需要设置较高的第二阈值,以便尽快丢弃导航信号强度不够强的GNSS导航数据,使用DR得到的移动终端位置变化数据。 这样就保证了移动终端可以正常定位。 同理,当移动终端离开建筑物时,由于使用DR得到的移动终端位置变化数据的累积误差较大,因此需要设置较低的第三阈值。 即需要将第三阈值设置为小于第二阈值,以便尽快合并GNSS导航数据,保证移动终端的定位精度。 可选的,第二阈值可以与第一阈值相同,也可以与第一阈值不同。 [0166] 小号 504 . 处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0167]图7为本发明实施例提供的另一种可靠导航数据获取方法的流程示意图。 在另一种可能的实施方式中,第一时间段内的第一导航数据之前存在导航数据,并确定第一时间段内第一导航数据之前的导航数据的状态。 主处理器从移动终端缓存的N条导航数据中获取M条可靠的导航数据包括以下步骤。 [0168] 小号 701 . 主处理器按照矩的顺序遍历N个导航数据的信号强度。 [0169] N个导航数据中的每一个都对应一个时刻和一个信号强度。 N条导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照时刻的顺序。 [0170] 小号 702 . 主处理器获取N个导航数据中的第一个导航数据之前的先前导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 . [0171] 小号 703 . 主处理器通过以下方式确定N条导航数据的状态:如果在时刻t的导航数据的状态 i−1 为高,当导航数据的信号强度在时刻 t i 小于第二阈值,确定导航数据在时刻t的状态 i 低; 或者如果某一时刻导航数据的状态为低,当某一时刻导航数据的信号强度为 t i 大于或等于第三阈值,确定导航数据在时刻t的状态 i 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值。 [0172] 确定第一时间段内第一条导航数据之前的先前导航数据的状态。 因此,主处理器可以根据之前的导航数据的状态确定第一时间段内的第一导航数据的状态,并根据第一时间段的状态确定下一时刻的导航数据的状态。 第一时间段内的导航数据,以此类推。 具体地,在另一种实施方式中,主处理器根据前一导航数据的状态判断第一导航数据的状态,以及根据前一导航数据的状态判断下一时刻导航数据状态的方式。 第一条导航数据与S中描述的方法相同 503 ,此处不再赘述。 [0173] 小号 704 . 处理器将所有状态为高的导航数据确定为M个可靠导航数据。 [0174] 本发明实施例还提供一种移动终端的定位装置。 图8为本发明实施例提供的移动终端定位装置的结构示意图。 参见图8,定位装置至少包括获取模块 810 和数据处理模块 820 . [0175] 具体来说,获取模块 810 用于在经过第一时间段后,从移动终端缓存的N条导航数据中获取M条可靠的导航数据,其中N≥M,M≥1,M和N为整数,N条导航数据 是利用第一时间段内接收到的移动终端的卫星导航信号计算得到的。 [0176] 获取模块 810还用于在经过第一时间段后,获取缓存的移动终端的K条位置变化数据,其中,K≥1,K为整数,K条位置变化数据由以下数据计算得到: 通过移动终端的传感器在第一时间段内监测得到。 [0177] 数据处理模块 820 用于将M个可靠导航数据和K个位置变化数据结合起来,得到移动终端在第一时间段内的位置信息。 [0178] 可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序。 [0179] 获取模块 810 专门配置为: [0180] 按照矩的顺序遍历N个导航数据的信号强度; [0181] 确定N个导航数据中信号强度大于或等于第一阈值的第一导航数据的状态为高,第一导航数据为第一导航数据; [0182] 判断另一条导航数据状态的方式如下,其中该另一条导航数据是N条导航数据中在第一个导航数据之后的导航数据: 如果某时刻t的导航数据的状态 i 为高,当导航数据的信号强度在时刻 t i+1 小于第二个阈值,判断t时刻导航数据的状态 i+1 低; 或者如果在时刻 t 的导航数据状态 1 低,当导航数据的信号强度在时刻 t i+1 大于或等于第三阈值,判断t时刻导航数据的状态 i+1 为高,其中1≤i≤n,i为整数,第二阈值大于第三阈值; 和 [0183] 将所有状态为高的导航数据确定为M个可靠导航数据。 [0184] 可选的,N个导航数据中的每一个对应一个时刻和一个信号强度,N个导航数据对应时刻t 1 , t 2 , . . . , 和T N 分别按照矩的顺序。 [0185] 获取模块 810 专门配置为: [0186] 按照矩的顺序遍历N个导航数据的信号强度; 获取N个导航数据中第一个导航数据之前的前一个导航数据的状态,其中时刻t 0 对应于先前的导航数据在时刻 t 之前 1 对应第一条导航数据,时刻t 0 与时刻 t 相邻 1 ; [0187] N个导航数据的状态判断方法如下:如果某时刻t的导航数据的状态 i−1 为高,当导航数据的信号强度在时刻 t i 小于第二个阈值,判断t时刻导航数据的状态 i 低; 或者如果在时刻 t 的导航数据状态 i−1 低,当导航数据的信号强度在时刻 t i 大于或等于第三阈值,判断t时刻导航数据的状态 i 为高,其中1≤i≤n,第二阈值大于第三阈值; 和 [0188] 将所有状态为高的导航数据确定为M个可靠导航数据。 [0189] 可选的,每个导航数据对应一个时刻,每个位置变化数据对应一个时刻; 当 m 的一瞬间 th 一条导航数据与n的时刻相同 th 一条位置变化数据,m th 一条导航数据设置为匹配 n th 一块位置变化数据。 [0190]数据处理模块 820 专门配置为: [0191] 从M个可靠导航数据和K个位置变化数据中获取相互匹配的可靠导航数据和位置变化数据; 和 [0192] 结合可靠的导航数据和相互匹配的位置变化数据,结合未结合的位置变化数据,得到第一时间段内移动终端的位置信息。 [0193] 可选地,所述导航数据为利用所述移动终端的卫星导航信号计算得到的、用于计算位置坐标的数据。 数据处理模块 820 专门配置为: [0194] 根据M个可靠导航数据计算得到M个位置坐标; 和 [0195] 结合M个位置坐标和K个位置变化数据,得到移动终端在第一时间段的位置信息。 [0196] 可选的,该装置还包括: [0197] 唤醒模块 830 ,用于在经过第一时间段后唤醒定位装置; 其中,定位装置在第一时间段内处于休眠状态。 [0198] 可选的,该装置还包括: [0199] 睡眠模块 840 ,用于在获取到移动终端在第一时间段内的位置信息后,使定位装置进入休眠状态。 [0200] 本发明实施例提供的移动终端定位装置,具体用于执行方法实施例提供的技术方案。 其实现原理和效果与方法实施例类似,在此不再赘述。 [0201] 本发明实施例还提供一种移动终端。 参考图1和图2,移动终端至少包括主处理器 30 , 全球导航卫星系统 GNSS 接收机 10 , 一个传感器 20 , 和协处理器 40 . [0202] 主处理器 30 用于执行方法实施例中描述的方法。 [0203] GNSS 接收机 10 用于在第一时间段接收移动终端的卫星导航信号,并根据卫星导航信号计算导航数据,导航数据为计算位置坐标的数据或导航数据为位置坐标 . [0204] 传感器 20 用于监测第一时间段内移动终端的运动数据。 [0205] 协处理器 40 用于根据传感器获取的运动数据计算得到K个位置变化数据 20 通过监控。 或者,协处理器 40 用于根据传感器监测得到的运动数据计算得到K个位置变化数据,并根据导航数据计算出位置坐标。 [0206] 可选地,第一时间段包括第二时间段,GNSS接收机 10 在第二时间段内处于休眠状态。 传感器 20 在第一时间段处于工作状态。 [0207] 本发明实施例提供的移动终端可以执行方法实施例提供的技术方案。 其实现原理和效果与方法实施例类似,在此不再赘述。 [0208]本领域普通技术人员可以理解,上述方法实施例的全部或者部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机、手机或其他便携设备可以读取的存储介质中。 当程序运行时,执行方法实施例的步骤。 上述存储介质包括:ROM、RAM、磁盘、光盘等任何可以存储程序代码的介质。 [0209] 最后需要说明的是,上述实施例仅仅用以说明本发明的技术方案,并不用于限制本发明。 尽管结合上述实施例对本发明进行了详细描述,但本领域普通技术人员应当理解,他们仍然可以对上述实施例中描述的技术方案进行修改或者对部分或全部技术特征进行等同替换 在不脱离本发明实施例技术方案的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN108029092A(String), CN108029092B(String), IN201827013200A(String), JP2019502895A(String), JP6646741B2(String), US11209555B2(String), US20180239027A1(String), WO2017054298A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN108029092A(String), CN108029092B(String), IN201827013200A(String), JP2019502895A(String), JP6646741B2(String), US11209555B2(String), US20180239027A1(String), WO2017054298A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN108029092A(String), CN108029092B(String), IN201827013200A(String), JP2019502895A(String), JP6646741B2(String), US11209555B2(String), US20180239027A1(String), WO2017054298A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), CN108029092A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271279(Integer), CN108029092B(String), 1048459(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), IN201827013200A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.504 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.504 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), JP2019502895A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.537 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), JP6646741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), US11209555B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), US20180239027A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271279(Integer), WO2017054298A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN108029092B(String), CN108029092B(String), 1599494400(Integer), 271279(Integer), 185563(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185953(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.834 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.834 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.834 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185953(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185953(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:12.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.008 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9899854B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, master data communication device and mobile terminal charging system and method(String), 移动终端、主数据通信设备和移动终端计费系统和方法(String), US9899854B2(String), A mobile terminal, a master data communication device and a mobile terminal charging system and method are provided. The method includes that: a mobile terminal determines whether or not a power supply device is a master data communication device and, if so, determines an appropriate charging mode for charging the mobile terminal. The disclosure not only enables a mobile terminal to select a plurality of adjustable charging modes to charge the mobile terminal but also enables the terminal to select a most appropriate charging mode to charging the mobile terminal, thus improving the charging efficiency.(String), 提供了一种移动终端、主数据通信设备以及移动终端计费系统和方法。 该方法包括:移动终端判断供电设备是否为主数据通信设备,如果是,则确定为移动终端充电的合适充电模式。 本发明不仅使移动终端能够选择多种可调节的充电模式对移动终端进行充电,而且使终端能够选择最合适的充电模式对移动终端进行充电,从而提高充电效率。(String), US14/428826(String), 1375286400(Integer), US9899854B2(String), 1519056000(Integer), 1519056000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 31(Integer), CN101162403A | CN101383627A | CN101853966A | CN102301305A | CN102377221A | CN102868820A | CN1617620A | CN1797894A | CN2569461Y | JP2011041394A | JP2012176786A | US20040189251A1 | US20070024239A1 | US20080084189A1 | US20080238358A1 | US20080278119A1 | US20100007310A1 | US20100026236A1 | US20110018503A1 | US20110103004A1 | US20110144823A1 | US20120181983A1 | US20130076299A1 | US20130110340A1 | US20130254580A1 | US20140035530A1 | US20140139176A1 | US20140347003A1 | US20150278038A1 | US7884571B2 | WO2005013456A1(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.834 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7ab5a322869c40a5aba4d14d0ec08436.png(String), 185954(Integer), 7ab5a322869c40a5aba4d14d0ec08436.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, master data communication device and mobile terminal charging system and method(String), 移动终端、主数据通信设备和移动终端计费系统和方法(String), US9899854B2(String), A mobile terminal, a master data communication device and a mobile terminal charging system and method are provided. The method includes that: a mobile terminal determines whether or not a power supply device is a master data communication device and, if so, determines an appropriate charging mode for charging the mobile terminal. The disclosure not only enables a mobile terminal to select a plurality of adjustable charging modes to charge the mobile terminal but also enables the terminal to select a most appropriate charging mode to charging the mobile terminal, thus improving the charging efficiency.(String), 提供了一种移动终端、主数据通信设备以及移动终端计费系统和方法。 该方法包括:移动终端判断供电设备是否为主数据通信设备,如果是,则确定为移动终端充电的合适充电模式。 本发明不仅使移动终端能够选择多种可调节的充电模式对移动终端进行充电,而且使终端能够选择最合适的充电模式对移动终端进行充电,从而提高充电效率。(String), US14/428826(String), 1375286400(Integer), US9899854B2(String), 1519056000(Integer), 1519056000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 31(Integer), CN101162403A | CN101383627A | CN101853966A | CN102301305A | CN102377221A | CN102868820A | CN1617620A | CN1797894A | CN2569461Y | JP2011041394A | JP2012176786A | US20040189251A1 | US20070024239A1 | US20080084189A1 | US20080238358A1 | US20080278119A1 | US20100007310A1 | US20100026236A1 | US20110018503A1 | US20110103004A1 | US20110144823A1 | US20120181983A1 | US20130076299A1 | US20130110340A1 | US20130254580A1 | US20140035530A1 | US20140139176A1 | US20140347003A1 | US20150278038A1 | US7884571B2 | WO2005013456A1(String), \20230420\7ab5a322869c40a5aba4d14d0ec08436.png(String), 11(Integer), 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 1. A master data communication device comprising an interface unit and a command generation unit, whereinthe interface unit is configured to be connected with a mobile terminal to transfer interaction information between the master data communication device and the mobile terminal; andthe command generation unit is configured to generate a charging command and send the generated charging command to the mobile terminal via the interface unit,wherein the device further comprises a mode selection unit configured to select an adjustable charging mode needed by the mobile terminal, and accordingly, the command generation unit is configured to generate a corresponding charging command according to the adjustable charging mode selected by the mode selection unit; or the command generation unit is configured to generate a corresponding charging command based on a charging command request received from the mobile terminal;wherein the adjustable charging mode is one of a standard charging mode, a first charging mode and a second charging mode, and a working current in the standard charging mode is a first working current commonly used by the master data communication device, a working current in the first charging mode is a second working current higher than the first working current, a working current in the second charging mode is a third working current higher than the second working current, and the third working current is the maximum working current that the master data communication can supply.(String), 1.主控数据通讯设备包括接口单元和命令生成单元,其中接口单元,用于与移动终端连接,传递数据通信主设备与移动终端之间的交互信息;和命令生成单元,用于生成充电命令,并将生成的充电命令通过接口单元发送给移动终端,其中,所述装置还包括模式选择单元,用于选择移动终端需要的可调充电模式,相应地,命令生成单元用于根据模式选择单元选择的可调充电模式生成相应的充电命令。或者,命令生成单元,用于根据从移动终端接收到的充电命令请求,生成相应的充电命令;其中,可调充电模式为标准充电模式、第一充电模式和第二充电模式中的一种,标准充电模式下的工作电流为数据通信主设备常用的第一工作电流,工作电流为第一充电模式为高于第一工作电流的第二工作电流,第二充电模式下的工作电流为高于第二工作电流的第三工作电流,第三工作电流为主数据的最大工作电流。通讯可以供应。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 2. The master data communication device according to claim 1, further comprising an identification unit configured to identify whether or not the mobile terminal supports adjustable charging modes.(String), 2.根据权利要求1所述的主数据通信装置,还包括识别单元,用于识别移动终端是否支持可调充电模式。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 3. The master data communication device according to claim 1, wherein the command generation unit is configured to automatically generate a charging command corresponding to a maximum working current available in adjustable charging modes supported by the mobile terminal.(String), 3.根据权利要求1所述的主数据通信装置,其中命令生成单元,用于自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令。4、移动终端充电系统包括一种数据通信主设备和移动终端,其中主数据通信设备与移动终端连接;数据通信主设备,用于向移动终端发送充电命令;和移动终端,用于接收来自数据通信主设备的充电指令,选择与充电指令对应的可调充电模式进行充电,其中,主数据通信设备根据移动终端选择的可调充电模式对应的充电命令请求发送相应的充电命令,或者根据主数据通信设备选择的可调充电模式为移动终端发送相应的充电命令。移动终端,或者自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令,并发送生成的充电命令;其中,可调充电模式为标准充电模式、第一充电模式和第二充电模式中的一种,标准充电模式下的工作电流为数据通信主设备常用的第一工作电流,工作电流为第一充电模式为高于第一工作电流的第二工作电流,第二充电模式下的工作电流为高于第二工作电流的第三工作电流,第三工作电流为主数据的最大工作电流。通讯可以供应。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 4. A mobile terminal charging system comprising a master data communication device and a mobile terminal, whereinthe master data communication device is connected with the mobile terminal;the master data communication device is configured to send a charging command to the mobile terminal; andthe mobile terminal is configured to receive the charging command from the master data communication device and select an adjustable charging mode corresponding to the charging command so as to be charged,wherein the master data communication device sends a corresponding charging command according to a charging command request corresponding to the adjustable charging mode selected by the mobile terminal, or sends a corresponding charging command according to the adjustable charging mode selected by the master data communication device for the mobile terminal, or automatically generates a charging command corresponding to a maximum working current available in adjustable charging modes supported by the mobile terminal and sends the generated charging command;wherein the adjustable charging mode is one of a standard charging mode, a first charging mode and a second charging mode, and a working current in the standard charging mode is a first working current commonly used by the master data communication device, a working current in the first charging mode is a second working current higher than the first working current, a working current in the second charging mode is a third working current higher than the second working current, and the third working current is the maximum working current that the master data communication can supply.(String), 5.根据权利要求4所述的移动终端充电系统,其中数据通信主设备还用于判断移动终端是否支持可调充电模式。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 5. The mobile terminal charging system according to claim 4, wherein the master data communication device is further configured to determine whether or not the mobile terminal supports adjustable charging modes.(String), 6.根据权利要求4所述的移动终端充电系统,其中主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一个,其中标准充电模式、第一充电模式和第二充电模式对应于标准充电命令,分别为第一充电指令与第二充电指令。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 6. The mobile terminal charging system according to claim 4, wherein the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command wherein the standard charging mode, the first charging mode and the second charging mode are corresponding to the standard charging command, the first charging command and the second charging command, respectively.(String), 7.根据权利要求6所述的移动终端充电系统,其中标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。8、一种移动端充电方法,包括:移动终端与主数据通信设备连接;数据通信主设备向移动终端发送相应的充电指令;和移动终端根据相应的充电指令选择相应的充电模式为移动终端充电,其中,在主数据通信设备向移动终端发送相应的充电命令之前,该方法还包括:主数据通信设备判断移动终端是否支持可调充电模式;数据通信主设备在确定移动终端支持可调充电模式后,向移动终端发送相应的充电命令,其中,数据通信主设备向移动终端发送相应的充电命令包括:移动终端选择需要的可调充电模式,并向数据通信主设备发送与选择的可调充电模式对应的充电命令请求;数据通信主设备根据充电命令请求向移动终端发送相应的充电命令;或者数据通信主设备为移动终端选择可调充电模式,数据通信主设备根据选择的可调充电模式生成相应的充电命令,数据通信主设备发送向移动终端生成充电命令;或者数据通信主设备自动生成移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令,并将生成的充电命令发送给移动终端;其中,可调充电模式为标准充电模式、第一充电模式和第二充电模式中的一种,标准充电模式下的工作电流为数据通信主设备常用的第一工作电流,工作电流为第一充电模式为高于第一工作电流的第二工作电流,第二充电模式下的工作电流为高于第二工作电流的第三工作电流,第三工作电流为主数据的最大工作电流。通讯可以供应。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 7. The mobile terminal charging system according to claim 6, wherein a working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA.(String), 9.根据权利要求8所述的移动终端充电方法,其中主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一个,其中标准充电模式、第一充电模式和第二充电模式对应于标准充电命令,第一充电命令和第二充电命令,分别。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 8. A mobile terminal charging method, comprising:connecting a mobile terminal with a master data communication device;sending, by the master data communication device, a corresponding charging command to the mobile terminal; andselecting, by the mobile terminal, a corresponding charging mode according to the corresponding charging command to charge the mobile terminal,wherein before the master data communication device sends the corresponding charging command to the mobile terminal, the method further comprising: determining, by the master data communication device, whether or not the mobile terminal supports adjustable charging modes; and sending, by the master data communication device, the corresponding charging command to the mobile terminal after the master data communication device determines that the mobile terminal supports adjustable charging modes,wherein the sending, by the master data communication device, a corresponding charging command to the mobile terminal comprises:selecting, by the mobile terminal, an adjustable charging mode needed and sending, by the mobile terminal, a charging command request corresponding to the selected adjustable charging mode to the master data communication device; and sending, by the master data communication device, the corresponding charging command to the mobile terminal according to the charging command request; orselecting, by the master data communication device, an adjustable charging mode for the mobile terminal, generating, by the master data communication device, the corresponding charging command according to the selected adjustable charging mode, and sending, by the master data communication device, the generated charging command to the mobile terminal; orautomatically generating, by the master data communication device, a charging command corresponding to a maximum working current available in adjustable charging modes supported by the mobile terminal and sending, by the master data communication device, the generated charging command to the mobile terminal;wherein the adjustable charging mode is one of a standard charging mode, a first charging mode and a second charging mode, and a working current in the standard charging mode is a first working current commonly used by the master data communication device, a working current in the first charging mode is a second working current higher than the first working current, a working current in the second charging mode is a third working current higher than the second working current, and the third working current is the maximum working current that the master data communication can supply.(String), 10.根据权利要求9所述的移动终端充电方法,其中标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 9. The mobile terminal charging method according to claim 8, wherein the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command, wherein the standard charging mode, the first charging mode and the second charging mode are corresponding to the standard charging command, the first charging command and the second charging command, respectively.(String), 11.根据权利要求1所述的主数据通信装置,其中指令产生单元所产生的充电指令为标准充电指令、第一充电指令及第二充电指令其中之一,其中标准充电模式、第一充电模式及第二充电模式对应于标准充电指令,分别为第一充电指令与第二充电指令。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 10. The mobile terminal charging method according to claim 9, wherein a working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:13.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185954(Integer), 11. The master data communication device according to claim 1, wherein the charging command generated by the command generation unit is one of a standard charging command, a first charging command and a second charging command, wherein the standard charging mode, the first charging mode and the second charging mode are corresponding to the standard charging command, the first charging command and the second charging command, respectively.(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185954(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of electronic communications, and in particular to a mobile terminal, a master data communication device and a mobile terminal charging system and method. BACKGROUND [0002]At present, it is very convenient to use mobile terminal devices because of the employment of a USB interface as a power interface by chargers for most of mobile terminal devices such as mobile phones, cameras and PAD and due to the easiness of getting a standard USB master device which is capable of charging these mobile terminal devices. However, as the current provided by a standard USB master device is small, for example, the current provided by a standard USB master device with a USB2.0 interface is 500 mA, and that provided by a standard USB master device with a USB1.1 interface is 250 mA, it takes a long time to charge a mobile terminal using a standard USB master device, resulting in poor user experience. Some existing portable power sources with a USB interface are capable of supplying a larger charging current, for example, a current of 800 mA, 1 A or even 1.5 A, than a standard USB master device. For existing USB master devices having a large-current charging capacity, as a USB slave device, that is, a mobile terminal, is incapable of automatically changing the magnitude of a charging current according to the power supply capacity of such a USB master device, the charging efficiency is low. For customers, it is desirable that a mobile terminal is capable of selecting a charging current as needed while providing a data communication service and that a plurality of charging modes are selectable for the convenient and rapid charging of a mobile terminal. SUMMARY [0003]The main technical problem the disclosure is intended to solve is to provide a mobile terminal, a master data communication device and a mobile terminal charging system and method to avoid a low charging efficiency caused because of the incapability of a mobile terminal to select in real time a charging mode matching with a master device to charge itself. [0004]To address the technical problem above, the technical solution of the disclosure is as follows: [0005]a mobile terminal includes a first interface unit, a first identification unit, a command receiving unit and a charging management unit, wherein [0006]the first interface unit is configured to be connected with a power supply device to transfer interaction information between the mobile terminal and the power supply device; [0007]the first identification unit is configured to identify whether or not the power supply device is a master data communication device; [0008]the command receiving unit is configured to receive a charging command sent by the power supply device when an identification result is that the power supply device is a master data communication device; and [0009]the charging management unit is configured to select an adjustable charging mode for charging according to the charging command. [0010]In an embodiment, the charging command received by the control unit may be one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the charging management unit may be one of: a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the standard charging command, the first charging command and the second charging command, respectively. A working current of the standard charging mode may be 500 mA, a working current in the first charging mode may be 800 mA, and a working current in the second charging mode may be 1000 mA or 1500 mA. [0011]In an embodiment, the mobile terminal further may include a first mode selection unit configured to select a corresponding adjustable charging mode needed by the mobile terminal and send a corresponding charging command request to the power supply device. [0012]In an embodiment, the first interface unit may be a USB interface unit. [0013]A master data communication device is also provided in an embodiment of the disclosure, which includes a second interface unit and a command generation unit, wherein [0014]the second interface unit is configured to be connected with a mobile terminal to transfer interaction information between the master data communication device and the mobile terminal; and [0015]the command generation unit is configured to generate a charging command and send the generated charging command to the mobile terminal via the second interface unit. [0016]In an embodiment, the master data communication device further may include a second identification unit configured to identify whether or not the mobile terminal supports adjustable charging modes. [0017]In an embodiment, the command generation unit may be configured to automatically generate a charging command corresponding to a maximum working current available in the adjustable charging modes supported by the mobile terminal. [0018]In an embodiment, the master data communication device further may include a second mode selection unit configured to select an adjustable charging mode needed by the mobile terminal, and correspondingly, the command generation unit is configured to generate a corresponding charging command according to the adjustable charging mode selected by the second mode selection unit; or the command generation unit generates a corresponding charging command based on a charging command request received from the mobile terminal. [0019]A mobile terminal charging system is also provided in an embodiment of the disclosure, which includes a master data communication device and a mobile terminal, wherein [0020]the master data communication device is connected with the mobile terminal; [0021]the master data communication device is configured to send a charging command to the mobile terminal; and [0022]the mobile terminal is configured to receive the charging command sent by the master data communication device and select an adjustable charging mode corresponding to the charging command so as to be charged. [0023]In an embodiment, the master data communication device may be also configured to determine whether or not the mobile terminal supports adjustable charging modes. [0024]In an embodiment, the charging command sent by the master data communication device may be one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal may be one of a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the standard charging command, the first charging command and the second charging command, respectively. A working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA. [0025]In an embodiment, the master data communication device may send a corresponding charging command according to a charging command request corresponding to the adjustable charging mode selected by the mobile terminal, or may send a corresponding charging command according to an adjustable charging mode selected by the master data communication device for the mobile terminal, or may automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and sends the generated charging command. [0026]A mobile terminal charging method is also provided in an embodiment of the disclosure, which includes that: [0027]a mobile terminal is connected with a master data communication device; [0028]the master data communication device sends a corresponding charging command to the mobile terminal; and [0029]the mobile terminal selects a corresponding charging mode according to the charging command so as to be charged. [0030]In an embodiment, before the master data communication device sends a corresponding charging command to the mobile terminal, the method further may include that: [0031]the master data communication device determines whether or not the mobile terminal supports adjustable charging modes and, after determining that the mobile terminal supports adjustable charging modes, sends the corresponding charging command to the mobile terminal. [0032]In an embodiment, the process that the master data communication device sends a corresponding charging command to the mobile terminal may include that: [0033]the mobile terminal selects a needed adjustable charging mode and sends a charging command request corresponding to the selected adjustable charging mode to the master data communication device; and [0034]the master data communication device sends a corresponding charging command to the mobile terminal according to the charging command request. [0035]In an embodiment, the process that the master data communication device sends a corresponding charging command to the mobile terminal may include that: the master data communication device selects an adjustable charging mode for the mobile terminal, generates a corresponding charging command according to the adjustable charging mode selected and sends the corresponding charging command generated to the mobile terminal; or the master data communication device automatically generates a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and sends the generated charging command. [0036]In an embodiment, the charging command sent by the master data communication device may be one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal may be one of a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the standard charging command, the first charging command and the second charging command, respectively. A working current in the standard charging mode is 500 mA, a working current in the first charging mode is 800 mA, and a working current in the second charging mode is 1000 mA or 1500 mA. [0037]Embodiments of the disclosure achieve the following beneficial effect: by means of the mobile terminal, the master data communication device and the mobile terminal charging system and method provided herein, a mobile data terminal can determine whether or not a power supply device is a master data communication device and if so, determine an appropriate charging mode for charging itself. In this way, the mobile terminal can not only select a corresponding charging mode for charging itself from a plurality of adjustable charging modes but also select the most appropriate charging mode for charging itself, thus improving the charging efficiency BRIEF DESCRIPTION OF THE DRAWINGS [0038]FIG. 1 is a schematic diagram illustrating the structure of a mobile terminal according to an embodiment of the disclosure; [0039]FIG. 2 is a schematic diagram illustrating the structure of a master data communication device according to an embodiment of the disclosure; [0040]FIG. 3 is a schematic diagram illustrating the structure of a mobile terminal charging system according to an embodiment of the disclosure; and [0041]FIG. 4 is a flowchart illustrating of a mobile terminal charging method according to an embodiment of the disclosure. DETAILED DESCRIPTION [0042]In embodiments of the disclosure, a mobile terminal can make a selection from a plurality of charging modes supported by a master device to achieve a user-desired or optimal charging mode, and a user-desired or optimal charging efficiency. Technical solution and the advantages of the disclosure will become clearer from the detailed description of the disclosure when taken in conjunction with accompanying drawings. [0043]A mobile terminal is provided in an embodiment of the disclosure, which, as shown in FIG. 1, includes: a first interface unit 101, a first identification unit 102, a command receiving unit 104 and a charging management unit 105, wherein [0044]the first interface unit 101 is connected with a power supply device to transfer the interaction information between the mobile terminal and the power supply device; [0045]the mobile terminal, which may be connected with the power supply device via a plurality of interfaces, is preferably connected with the power supply device via a USB interface. [0046]The first identification unit 102 is configured to identify whether or not the power supply device is a master data communication device; [0047]Although there are a variety of kinds of power supply devices, such as AC/DC adaptors, standard master devices, portable power sources and master data communication devices, the power supply device here is preferably a master data communication device as the master data communication device is capable of providing a plurality of charging modes for a mobile terminal while performing data communication with the mobile terminal, and also capable of providing both a standard current charging mode and a large current (e.g. 1000 mA) charging mode for the mobile terminal. [0048]The command receiving unit 104 is configured to start a master device charging mode when the identification result is that the power supply device is a master data communication device and to receive a charging command sent by the power supply device; [0049]when the first identification unit 102 identifies that the power supply device is a master data communication device, the command receiving unit 104 controls the mobile terminal to enter a charging mode and receives charging commands sent by a plurality of power supply devices. [0050]The charging management unit 105 is configured to select a corresponding adjustable charging mode for charging according to the charging command received by the command receiving unit 104. [0051]In the embodiment, a variety of kinds of charging commands may be sent by the power supply device, including one of a standard charging command, a first charging command and a second charging command; and there are also a plurality of adjustable charging modes corresponding to the mobile terminal, including a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. Specifically, the standard charging command is corresponding to the standard charging mode, the first charging command is corresponding to the first charging mode, and the second charging command is corresponding to the second charging mode. In an embodiment, the working current in the standard charging mode, which is the working current commonly used by the power supply device, is preferably 500 mA; the working current in the first charging mode, which is a relatively large working current that the power supply device can supply, is usually 800 mA; the working current in the second charging mode, which is the maximum working current that the power supply device can supply, is preferably 1000 mA or 1500 mA; and the working currents mentioned herein cover any working current that can be provided by the power supply device and supported by the mobile terminal, but not limited to a specific working current limited in the disclosure. [0052]In the embodiment, the mobile terminal further includes a first mode selection unit which is mainly configured to select an adjustable charging mode needed by the mobile terminal and send a corresponding charging command request to the power supply device; after the first identification unit 102 identifies that the power supply device is a master data communication device, the user may select a needed adjustable charging mode through the first mode selection unit, generates a corresponding charging command request and sends the generated charging command to the power supply device, the power supply device generates, according to the charging command request, a charging command corresponding to the charging mode and sends the generated charging command to the command receiving unit 104, and the charging management unit 105 starts a corresponding charging mode. [0053]In the embodiment, as the first interface unit 101 is a USB interface unit, the identification of the power supply device as a master data communication device by the first identification unit 104 mainly includes the following identification steps of: [0054]determining whether or not the power supply device is an AC/DC adaptor with a USB interface or a USB master device by detecting whether or not the D+ signal pin and the D− signal pin of the USB are short-circuited; if the D+ signal pin and the D− signal pin of the USB are short-circuited, determining that the power supply device is an AC/DC adaptor with a USB interface, otherwise, determining that the power supply device is a USB master device; and [0055]sequentially determining whether or not the power supply device is a portable power source with a USB interface or a master data communication device by detecting whether or not there are signals at the D+ signal pin and the D− signal pin of the USB, determining that the power supply device is a master data communication device if there are signals at the D+ signal pin and the D− signal pin of the USB, otherwise, determining that the power supply device is a portable power source with a USB interface. [0056]A master data communication device is also provided in an embodiment of the disclosure, which, as shown in FIG. 2, includes: a second interface unit 201, a second identification unit 202 and a command generation unit 204, wherein [0057]the second interface unit 201 is connected with a mobile terminal to transfer the interaction information between the master data communication device and the mobile terminal; [0058]the second identification unit 202 is configured to identify whether or not the mobile terminal supports adjustable charging modes; after being connected with the mobile terminal, the second identification unit needs to identify the mobile terminal so as to determine whether or not the mobile terminal supports adjustable charging modes; [0059]the specific determination process is as follows: the second identification unit sends a test command and analyzes the result information fed back to determine whether or not the mobile terminal supports adjustable charging modes; or the second identification unit 202 directly sends a charging command generation request to the command generation unit 204, and the command generation unit 204 sends a first or second charging command to the mobile terminal; if the result information fed back is an acknowledgement, which indicates that the mobile terminal supports adjustable charging modes, then the mobile terminal starts a charging mode corresponding to the charging command so as to be charged; and if the result information fed back is a fault, which indicates that the mobile terminal supports no adjustable charging mode, then the command generation unit 204 sends a standard charging command to the mobile terminal; and [0060]the command generation unit 204 is configured to generate a charging command and send the generated charging command to the mobile terminal via the second interface unit 201; [0061]the command generation unit 204 is mainly configured to generate a corresponding charging command and send the generated charging command to the mobile terminal to start a corresponding charging mode to charge the mobile terminal. [0062]In the embodiment, the master data communication device further may include a second mode selection unit 203 configured to select an adjustable charging mode needed by the mobile terminal; in consideration of the situation that a mobile terminal is out of power and cannot be launched, which happens sometimes, and the situation that a user is used to performing a charging operation at the side of the master data communication device, the user may select an adjustable charging mode supported by the terminal on the interface of the master data communication device through the second mode selection unit 203, and the command generation unit 204 generates a corresponding charging command according to the adjustable charging mode selected by the second mode selection unit 203. In the embodiment, the command generation unit 204 may further generate a corresponding charging command based on a charging command request sent by the mobile terminal. If no adjustable charging mode is selected by the user from the mobile terminal or from the master data communication device, then the command generation unit 204 may automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and send the generated charging command to the mobile terminal. [0063]A mobile terminal charging system is also provided in an embodiment of the disclosure, which, as shown in FIG. 3, includes a master data communication device and a mobile terminal, wherein [0064]the master data communication device is connected with the mobile terminal and configured to determine whether or not the mobile terminal supports adjustable charging modes and send a charging command to the mobile terminal; and the mobile terminal is configured to receive the charging command sent by the master data communication device and select an adjustable charging mode corresponding to the charging command so as to be charged. [0065]In the embodiment, the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal includes a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. Specifically, the standard charging command is corresponding to the standard charging mode, the first charging command is corresponding to the first charging mode, and the second charging command is corresponding to the second charging mode. In an embodiment, the working current in the standard charging mode, which is the working current commonly used by the power supply device, is preferably 500 mA; the working current in the first charging mode, which is a relatively large working current the power supply device can supply, is usually 800 mA; the working current in the second charging mode, which is the maximum working current the power supply device can supply, is preferably 1000 mA or 1500 mA; and the working currents mentioned herein cover any working current that can be provided by the power supply device and supported by the mobile terminal, but not limited to a specific working current limited in the disclosure. [0066]In the embodiment, the master data communication device may send a charging command according to a charging command request corresponding to the adjustable charging mode selected by the mobile terminal, or send a corresponding charging command according to an adjustable charging mode selected by the master data communication device for the mobile terminal, or automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and send the generated charging command. [0067]A mobile terminal charging method is also provided in an embodiment of the disclosure, which specifically includes the following steps that: [0068]a mobile terminal is connected with a master data communication device; [0069]the master data communication device sends a corresponding charging command to the mobile terminal; and [0070]the mobile terminal selects a corresponding charging mode according to the charging command so as to be charged. [0071]In the embodiment, the process that the master data communication device sends a corresponding charging command to the mobile terminal specifically includes that: [0072]the mobile terminal selects a needed adjustable charging mode and sends a charging command request corresponding to the selected adjustable charging mode to the master data communication device; and [0073]the master data communication device sends a corresponding charging command to the mobile terminal according to the charging command request. [0074]In the embodiment, the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal includes a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. [0075]In the embodiment, the master data communication device may directly generate a first or second charging command and send the generated first or second charging command to the mobile terminal; if the result information fed back is acknowledgement, which indicates that the mobile terminal supports adjustable charging modes, then the mobile terminal starts a charging mode corresponding to the charging command so as to be charged; and if the result information fed back is fault, which indicates that the mobile terminal supports no adjustable charging mode, then the master data communication device sends a standard charging command to the mobile terminal. [0076]Alternatively, in the embodiment, before the master data communication device sends a corresponding charging command to the mobile terminal, the method further may include that: the master data communication device determines whether or not the mobile terminal supports adjustable charging modes. As in the embodiment, besides by directly sending a charging command to the mobile terminal, the master data communication device may also determine whether or not the mobile terminal supports adjustable charging modes by sending a test command to the mobile terminal and analyzing the result information fed back. [0077]Alternatively, in the embodiment, the process that the master data communication device sends a charging command to the mobile terminal may be as follows: the master data communication device selects an adjustable charging mode for the mobile terminal, generates a corresponding charging command according to the adjustable charging mode selected and sends the charging command generated to the mobile terminal; or the master data communication device automatically generates a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and sends the generated charging command. [0078]Refer to FIG. 4, the mobile terminal charging method disclosed herein is described in detail below based on a specific embodiment: [0079]Step 402: a mobile terminal is connected with a master data communication device, and then Step 404 is executed; [0080]Step 404: the master data communication device determines whether or not the mobile terminal supports adjustable charging modes, if so, Step 410 is executed, otherwise, Step 406 is executed; [0081]in this step, the master data communication device sends a test command to determine whether or not the mobile terminal supports adjustable charging modes; [0082]Step 406: the master data communication device sends a standard charging command, and then Step 408 is executed; [0083]Step 408: the mobile terminal starts a standard charging mode for charging itself; [0084]Step 410: the mobile terminal selects an adjustable charging mode and then Step 412 is executed; [0085]in this step, in consideration of the situation that a mobile terminal may go out of power and cannot be launched, which happens sometimes, and the situation that a user is used to performing a charging operation at the side of the master data communication device, the user may select an adjustable charging mode supported by the terminal on the interface of the master data communication device through the second mode selection unit of the master data communication device, and the command generation unit of the master data communication device generates a corresponding charging command according to the adjustable charging mode selected by the second mode selection unit. In the embodiment, the command generation unit may further generate a corresponding charging command based on a charging command request received from the mobile terminal. If no adjustable charging mode is selected by the user from the mobile terminal or from the master data communication device, then the command generation unit may automatically generate a charging command corresponding to the maximum working current available in the adjustable charging modes supported by the mobile terminal and send the generated charging command to the mobile terminal; [0086]Step 412: a corresponding charging command request is generated according to the selected adjustable charging mode and sent to the master data communication device, and then Step 414 is executed; [0087]Step 414: the master data communication device generates a corresponding charging command according to the charging command request and sends the generated charging command to the mobile terminal, and then Step 416 is executed; and [0088]Step 416: the mobile terminal selects and starts a corresponding adjustable charging mode according to the received charging command so as to be charged. [0089]In Step 414 and Step 416, the charging command sent by the master data communication device is one of a standard charging command, a first charging command and a second charging command; and the adjustable charging mode selected by the mobile terminal includes a standard charging mode, a first charging mode and a second charging mode, which are corresponding to the foregoing charging commands, respectively. In an embodiment, the working current in the standard charging mode, which is the working current commonly used by the power supply device, is preferably 500 mA; the working current in the first charging mode, which is a relatively large working current the power supply device can supply, is usually 800 mA; the working current in the second charging mode, which is the maximum working current the power supply device can supply, is preferably 1000 mA or 1500 mA; and the working currents mentioned herein cover any working current that can be provided by the power supply device and supported by the mobile terminal, but not limited to a specific working current limited in the disclosure. [0090]The mentioned above is merely detailed description of specific implementation mode of the disclosure but is not to be construed as limiting the specific implementation of the disclosure. It should be appreciated by those ordinary skills in the art that a variety of simple derivations and substitutes can be devised without departing from the spirit and scope of the disclosure, and all the derivations and substitutes should fall within the scope of the disclosure.(String), 技术领域 [0001] 本发明涉及电子通信领域,尤其涉及一种移动终端、数据通信主设备及移动终端计费系统及方法。 背景 [0002] 目前,手机、相机、PAD等移动终端设备大多采用USB接口作为充电器的电源接口,而且标准USB接口随手可得,使用起来非常方便。 能够为这些移动终端设备充电的主控设备。 但由于标准USB主控设备提供的电流较小,例如USB2.0接口的标准USB主控设备提供的电流为500mA,USB1.0接口的标准USB主控设备提供的电流为500mA。 1接口为250毫安,使用标准USB主控设备给移动终端充电时间较长,导致用户体验不佳。 现有的一些带有USB接口的便携式电源能够提供比标准USB主设备更大的充电电流,例如800mA、1A甚至1.5A的电流。 对于现有的具有大电流充电能力的USB主控设备,作为USB从属设备,即移动终端,无法根据此类USB主控设备的供电能力自动改变充电电流的大小, 充电效率低。 对于消费者而言,希望移动终端在提供数据通信服务的同时,能够根据需要选择充电电流,并且能够选择多种充电模式,以方便、快速地为移动终端充电。 概括 [0003] 本发明所要解决的主要技术问题是提供一种移动终端、数据通信主设备及移动终端充电系统及方法,避免因移动终端无法实时选择而导致的充电效率低下 与主控设备匹配的充电方式,为自身充电。 [0004] 为解决上述技术问题,本发明的技术方案如下: [0005] 一种移动终端,包括第一接口单元、第一识别单元、命令接收单元和充电管理单元,其中 [0006] 第一接口单元,用于与供电设备连接,以传递移动终端与供电设备之间的交互信息; [0007] 第一识别单元用于识别供电设备是否为主数据通信设备; [0008] 命令接收单元,用于当识别结果为供电设备为主数据通信设备时,接收供电设备发送的充电命令; 和 [0009] 充电管理单元用于根据充电命令选择可调的充电模式进行充电。 [0010] 在一个实施例中,控制单元接收到的充电命令可以是标准充电命令、第一充电命令和第二充电命令中的一种; 充电管理单元选择的可调充电模式可以为以下之一:标准充电模式、第一充电模式和第二充电模式,分别对应于标准充电命令、第一充电命令和第二充电命令, 分别。 标准充电模式的工作电流可以为500mA,第一充电模式的工作电流可以为800mA,第二充电模式的工作电流可以为1000mA或1500mA。 [0011] 在一个实施例中,移动终端还可以包括第一模式选择单元,用于选择移动终端需要的对应的可调充电模式,并向供电设备发送对应的充电命令请求。 [0012] 在一个实施例中,第一接口单元可以是USB接口单元。 [0013] 本发明实施例还提供一种主控数据通信装置,包括第二接口单元和命令生成单元,其中, [0014]第二接口单元,用于与移动终端连接,传递数据通信主设备与移动终端之间的交互信息; 和 [0015] 命令生成单元,用于生成充电命令,并将生成的充电命令通过第二接口单元发送给移动终端。 [0016] 在一个实施例中,数据通信主设备还可以包括第二识别单元,用于识别移动终端是否支持可调充电模式。 [0017] 在一个实施例中,命令生成单元可以用于自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令。 [0018] 在一个实施例中,数据通信主设备还可以包括:第二模式选择单元,用于选择移动终端需要的可调充电模式;相应的,命令生成单元,用于根据可调充电模式生成相应的充电命令。 第二模式选择单元选择的模式; 或者,命令生成单元根据从移动终端接收到的充电命令请求生成相应的充电命令。 [0019] 本发明实施例还提供了一种移动终端计费系统,包括数据通信主设备和移动终端,其中, [0020] 主数据通信设备与移动终端连接; [0021] 数据通信主设备,用于向移动终端发送充电命令; 和 [0022] 移动终端,用于接收数据通信主设备发送的充电命令,选择与充电命令对应的可调充电模式进行充电。 [0023] 在一个实施例中,主数据通信设备还可以用于判断移动终端是否支持可调充电模式。 [0024] 在一个实施例中,主数据通信设备发送的充电命令可以是标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式可以为标准充电模式、第一充电模式和第二充电模式中的一种,分别对应于标准充电命令、第一充电命令和第二充电命令。 标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。 [0025] 在一个实施例中,主数据通信设备可以根据移动终端选择的可调充电模式对应的充电命令请求发送相应的充电命令,也可以根据主数据通信设备选择的可调充电模式发送相应的充电命令。 用于移动终端的数据通信装置,或者可以在移动终端支持的可调充电模式中自动生成与可用的最大工作电流对应的充电命令并发送生成的充电命令。 [0026] 本发明实施例还提供了一种移动终端的充电方法,包括: [0027] 移动终端连接主数​​据通信设备; [0028] 数据通信主设备向移动终端发送相应的充电命令; 和 [0029] 移动终端根据充电指令选择相应的充电模式进行充电。 [0030] 在一个实施例中,在主数据通信设备向移动终端发送相应的充电命令之前,该方法还可以包括: [0031]数据通信主设备判断移动终端是否支持可调充电模式,在判断移动终端支持可调充电模式后,向移动终端发送相应的充电命令。 [0032] 在一个实施例中,主数据通信设备向移动终端发送相应的充电命令的过程可以包括: [0033] 移动终端选择需要的可调充电模式,并向数据通信主设备发送与选择的可调充电模式对应的充电命令请求; 和 [0034] 数据通信主设备根据充电命令请求向移动终端发送相应的充电命令。 [0035] 在一个实施例中,数据通信主设备向移动终端发送相应的充电命令的过程可以包括:数据通信主设备为移动终端选择可调充电模式,根据可调充电生成相应的充电命令。 选择模式并将生成的相应充电命令发送给移动终端; 或者,主数据通信设备在移动终端支持的可调充电模式下自动生成最大可用工作电流对应的充电指令,并发送生成的充电指令。 [0036] 在一个实施例中,主数据通信设备发送的充电命令可以是标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式可以为标准充电模式、第一充电模式和第二充电模式中的一种,分别对应于标准充电命令、第一充电命令和第二充电命令。 标准充电模式下的工作电流为500mA,第一充电模式下的工作电流为800mA,第二充电模式下的工作电流为1000mA或1500mA。 [0037] 本发明实施例的有益效果是:通过本发明提供的移动终端、数据通信主设备及移动终端充电系统及方法,移动数据终端可以判断供电设备是否为数据主设备。 通信设备,如果是,则确定适当的充电模式来为自身充电。 这样,移动终端不仅可以从多种可调节的充电模式中选择相应的充电模式为自己充电,还可以选择最合适的充电模式为自己充电,提高了充电效率。 附图的简要说明 [0038] 图1是根据本发明一个实施例的移动终端的结构示意图; [0039] 图2为根据本发明一实施例的主数据通信装置的结构示意图。 [0040] 图3是根据本发明实施例的移动终端计费系统的结构示意图。 和 [0041] 图4为根据本发明一实施例的移动终端充电方法的流程图。 详细说明 [0042] 在本发明实施例中,移动终端可以从主设备支持的多种充电模式中进行选择,以实现用户期望或最优的充电模式,以及用户期望或最优的充电效率。 通过结合附图对本发明的详细描述,本发明的技术方案和优点将会更加清楚。 [0043] 本发明实施例提供一种移动终端,如图1所示,包括: 第一接口单元 101 , 第一识别单元 102 , 一个指令接收单元 104 和充电管理单元 105 , 其中 [0044] 第一接口单元 101与供电设备连接,传递移动终端与供电设备的交互信息; [0045] 移动终端与供电设备可以通过多种接口连接,优选地通过USB接口与供电设备连接。 [0046] 第一标识单元 102 用于识别供电设备是否为主数据通信设备; [0047] 虽然供电装置种类繁多,例如AC/DC适配器、标准主控装置、可携式电源及主控数据通讯装置,但此处的供电装置较佳为主控数据通讯装置,作为主控数据通讯装置 能够在与移动终端进行数据通信的同时为移动终端提供多种充电模式,也能够为移动终端提供标准电流充电模式和大电流(如1000mA)充电模式。 [0048] 指令接收单元 104 用于当识别结果为供电设备为主数据通信设备时,启动主设备充电模式,并接收供电设备发送的充电命令; [0049] 当第一个标识单元 102 识别供电设备为主数据通信设备,命令接收单元 104 控制移动终端进入充电模式,并接收多个供电设备发送的充电指令。 [0050] 充电管理单元 105 用于根据命令接收单元接收到的充电命令选择相应的可调充电模式进行充电 104 . [0051] 在本实施例中,供电设备可以发送多种充电指令,包括标准充电指令、第一充电指令和第二充电指令中的一种; 移动终端对应的充电模式也有多种可调,包括标准充电模式、第一充电模式和第二充电模式,分别对应上述充电指令。 具体地,标准充电指令对应标准充电模式,第一充电指令对应第一充电模式,第二充电指令对应第二充电模式。 在一个实施例中,标准充电模式下的工作电流,即供电设备常用的工作电流,优选为500mA; 第一充电模式下的工作电流,是供电设备能够提供的较大的工作电流,通常为800mA。 第二充电模式下的工作电流,即供电装置所能提供的最大工作电流,优选为1000mA或1500mA。 此处所说的工作电流涵盖了供电装置能够提供的、移动终端支持的任何工作电流,而不限于本发明所限定的具体工作电流。 [0052] 在本实施例中,移动终端还包括第一模式选择单元,主要用于选择移动终端需要的可调充电模式,并向供电设备发送相应的充电命令请求。 在第一个识别单元之后 102 识别供电设备为主数据通信设备,用户可以通过第一模式选择单元选择需要的可调充电模式,生成相应的充电命令请求,并将生成的充电命令发送给供电设备,供电设备 设备根据充电命令请求生成与充电模式对应的充电命令,并将生成的充电命令发送给命令接收单元 104 , 以及充电管理单元 105 启动相应的充电模式。 [0053] 本实施例中,作为第一接口单元 101为USB接口单元,第一识别单元识别供电设备为主数据通信设备 104 主要包括以下识别步骤: [0054] 通过检测USB的D+信号脚和D-信号脚是否短路来判断供电设备是否为USB接口的AC/DC适配器或USB主控设备; 若USB的D+信号脚与D-信号脚短路,则判断供电设备为USB接口的AC/DC适配器,否则判断供电设备为USB主控设备; 和 [0055] 通过检测USB的D+信号管脚和D-信号管脚是否有信号,依次判断供电设备是否为USB接口的便携式电源或数据通信主设备,确定 若USB的D+信号脚和D-信号脚均有信号,则供电设备为主数据通信设备,否则,确定供电设备为USB接口的便携式电源。 [0056] 本发明实施例还提供一种主数据通信装置,如图2所示,包括: 第二接口单元 201 , 第二识别单元 202 和一个命令生成单元 204 , 其中 [0057] 第二接口单元 201 与移动终端连接,传递数据通信主设备与移动终端之间的交互信息; [0058] 第二识别单元 202 用于识别移动终端是否支持可调充电模式; 第二识别单元在与移动终端连接后,需要对移动终端进行识别,以判断移动终端是否支持可调充电模式。 [0059] 具体判断过程为:第二识别单元发送测试命令,分析反馈的结果信息,判断移动终端是否支持可调充电模式。 或第二识别单元 202 直接向命令生成单元发送充电命令生成请求 204 , 和命令生成单元 204 向移动终端发送第一或第二充电命令; 若反馈的结果信息为确认,表明移动终端支持可调充电模式,则移动终端启动与充电命令对应的充电模式进行充电。 如果反馈的结果信息为错误,表明移动终端不支持可调充电模式,则命令生成单元 204 向移动终端发送标准充电命令; 和 [0060] 命令生成单元 204 用于生成充电命令,并将生成的充电命令通过第二接口单元发送给移动终端 201 ; [0061] 命令生成单元 204 主要用于生成相应的充电命令,并将生成的充电命令发送给移动终端,以启动相应的充电模式对移动终端进行充电。 [0062] 在本实施例中,主数据通信装置还可以包括:第二模式选择单元 203 用于选择移动终端需要的可调充电模式; 考虑到移动终端有时会出现没电无法启动的情况,以及用户习惯在主数据通信设备侧进行充电操作的情况,用户可以选择 终端通过第二模式选择单元在主数据通信设备接口上支持的充电模式可调 203 , 和命令生成单元 204 根据第二模式选择单元选择的可调充电模式产生相应的充电命令 203 . 本实施例中,命令生成单元 204还可以根据移动终端发送的充电命令请求生成相应的充电命令。 如果用户没有从移动终端或主数据通信设备选择可调充电模式,则命令生成单元 204 可以在移动终端支持的可调充电模式中自动生成最大可用工作电流对应的充电指令,并将生成的充电指令发送给移动终端。 [0063] 本发明实施例还提供了一种移动终端计费系统,如图3所示,包括数据通信主设备和移动终端,其中, [0064] 数据通信主设备与移动终端连接,用于判断移动终端是否支持可调充电模式,并向移动终端发送充电命令; 移动终端用于接收数据通信主设备发送的充电指令,选择与充电指令对应的可调充电模式进行充电。 [0065] 在本实施例中,主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式包括标准充电模式、第一充电模式和第二充电模式,分别对应于上述充电指令。 具体地,标准充电指令对应标准充电模式,第一充电指令对应第一充电模式,第二充电指令对应第二充电模式。 在一个实施例中,标准充电模式下的工作电流,即供电设备常用的工作电流,优选为500mA; 第一充电模式下的工作电流,是供电设备能够提供的较大工作电流,通常为800mA。 第二充电模式下的工作电流,即供电设备能够提供的最大工作电流,优选为1000mA或1500mA。 此处所说的工作电流涵盖了供电装置能够提供的、移动终端支持的任何工作电流,而不限于本发明所限定的具体工作电流。 [0066] 本实施例中,主数据通信设备可以根据移动终端选择的可调充电模式对应的充电命令请求发送充电命令,或者根据主数据通信选择的可调充电模式发送相应的充电命令。 设备为移动终端,或者在移动终端支持的可调充电模式中自动生成对应于最大可用工作电流的充电命令并发送生成的充电命令。 [0067] 本发明实施例还提供了一种移动终端的充电方法,具体包括以下步骤: [0068] 移动终端连接主数​​据通信设备; [0069] 数据通信主设备向移动终端发送相应的充电命令; 和 [0070] 移动终端根据充电指令选择相应的充电模式进行充电。 [0071] 在本实施例中,主数据通信设备向移动终端发送相应的充电命令的过程具体包括: [0072] 移动终端选择需要的可调充电模式,并向数据通信主设备发送与选择的可调充电模式对应的充电命令请求; 和 [0073] 数据通信主设备根据充电命令请求向移动终端发送相应的充电命令。 [0074]在本实施例中,主数据通信设备发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一种; 移动终端选择的可调充电模式包括标准充电模式、第一充电模式和第二充电模式,分别对应于上述充电指令。 [0075] 本实施例中,主数据通信设备可以直接生成第一或第二充电命令,并将生成的第一或第二充电命令发送给移动终端。 若反馈的结果信息为确认,表明移动终端支持可调充电模式,则移动终端启动与充电命令对应的充电模式进行充电。 如果反馈的结果信息为fault,表明移动终端不支持可调充电模式,则数据通信主设备向移动终端发送标准充电命令。 [0076] 可选地,在本实施例中,在主数据通信设备向移动终端发送相应的充电命令之前,该方法还可以包括: 主数据通信设备判断移动终端是否支持可调充电模式。 如本实施例,数据通信主设备除了直接向移动终端发送充电指令外,还可以通过向移动终端发送测试指令,分析反馈的结果信息,判断移动终端是否支持可调充电模式。 背部。 [0077] 可选地,在本实施例中,主数据通信设备向移动终端发送充电命令的过程可以为: 主数据通信设备为移动终端选择可调节的充电模式,根据充电模式生成相应的充电命令。 选择可调充电模式并将生成的充电命令发送给移动终端; 或者,主数据通信设备在移动终端支持的可调充电模式下自动生成最大可用工作电流对应的充电指令,并发送生成的充电指令。 [0078] 参见图4,下面结合一个具体实施例对本发明公开的移动终端充电方法进行详细说明: [0079] 步 402 :移动终端与主数据通信设备连接,然后步骤 404 被执行; [0080] 步 404 :主数据通信设备判断移动终端是否支持可调充电模式,若支持,步骤 410 被执行,否则,Step 406 被执行; [0081] 本步骤中,数据通信主设备发送测试命令,判断移动终端是否支持可调充电模式。 [0082] 步 406 :主数据通信设备发送标准充电命令,然后Step 408 被执行; [0083] 步 408 :移动终端启动标准充电模式为自身充电; [0084] 步 410 :移动端选择一种可调节的充电方式,然后Step 412 被执行; [0085]本步骤中,考虑到移动终端有时会出现没电无法启动的情况,以及用户习惯在主数据通信设备侧进行充电操作的情况, 用户可以通过主数据通信设备的第二模式选择单元在主数据通信设备的界面上选择终端支持的可调充电模式,主数据通信设备的命令生成单元生成相应的充电命令 根据第二模式选择单元选择的可调充电模式。 在本实施例中,命令生成单元还可以根据从移动终端接收到的充电命令请求生成相应的充电命令。 如果用户未从移动终端或数据通信主设备选择可调充电模式,则命令生成单元可自动生成与移动终端支持的可调充电模式下可用的最大工作电流对应的充电命令 将生成的充电命令发送给移动终端; [0086] 步 412 :根据选择的可调充电模式生成相应的充电命令请求发送给主数据通信设备,然后步骤 414 被执行; [0087] 步 414 :主数据通信设备根据计费命令请求生成相应的计费命令,并将生成的计费命令发送给移动终端,然后步骤 416 被执行; 和 [0088] 步 416 :移动终端根据接收到的充电指令选择并启动相应的可调充电模式进行充电。 [0089] 在步骤 414 和步骤 416 ,主数据通信装置发送的充电命令为标准充电命令、第一充电命令和第二充电命令中的一个; 移动终端选择的可调充电模式包括标准充电模式、第一充电模式和第二充电模式,分别对应于上述充电命令。 在一个实施例中,标准充电模式下的工作电流,即供电设备常用的工作电流,优选为500mA; 第一充电模式下的工作电流,是供电设备能够提供的较大工作电流,通常为800mA。 第二充电模式下的工作电流,即供电设备能够提供的最大工作电流,优选为1000mA或1500mA。 此处所说的工作电流涵盖了供电装置能够提供的、移动终端支持的任何工作电流,而不限于本发明所限定的具体工作电流。 [0090] 以上所述仅为本发明的具体实施方式的详细说明,并不构成对本发明具体实施方式的限定。 本领域的普通技术人员应当理解,在不脱离本公开的精神和范围的情况下,可以设计出各种简单的推导和替代,并且所有的推导和替代都应落入本公开的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102868820A(String), EP2892214A2(String), EP2892214A4(String), EP2892214B1(String), US20150256018A1(String), US9899854B2(String), WO2013178191A2(String), WO2013178191A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102868820A(String), EP2892214A2(String), EP2892214A4(String), EP2892214B1(String), US20150256018A1(String), US9899854B2(String), WO2013178191A2(String), WO2013178191A3(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102868820A(String), EP2892214A2(String), EP2892214A4(String), EP2892214B1(String), US20150256018A1(String), US9899854B2(String), WO2013178191A2(String), WO2013178191A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271549(Integer), CN102868820A(String), 1049188(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.478 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), EP2892214A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.513 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.514 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), EP2892214A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), EP2892214B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), US20150256018A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), US9899854B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), WO2013178191A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271549(Integer), WO2013178191A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN102868820A(String), CN102868820A(String), 1357660800(Integer), 271549(Integer), 185833(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185954(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185954(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:14.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185954(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185954(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.320 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7668136B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: System, network, mobile terminal, computer program product and method for cross-paging a mobile terminal via a data burst message(String), 用于通过数据突发消息对移动终端进行跨页寻呼的系统、网络、移动终端、计算机程序产品和方法(String), US7668136B2(String), Systems and methods are provided to permit a network, such as a data only network, with which a mobile terminal is not currently communicating to notify the mobile terminal that the network desires to establish communication with the mobile terminal, even in instances in which the mobile terminal is actively communicating via another network, such as a voice and data network and has stopped monitoring for paging messages. The mobile terminal can then end communications with the network with which it has been previously communicating and commence communications with the other network that has transmitted the paging message. For example, a mobile terminal may terminate voice communications via a voice and data network in order to receive a Multimedia Message Service message via a data only network upon receiving notification that the data only network desires to establish a communications session with the mobile terminal.(String), 提供系统和方法以允许移动终端当前未与之通信的网络(例如纯数据网络)通知移动终端该网络希望与移动终端建立通信,即使在移动终端未与之通信的情况下也是如此。 终端正在通过另一个网络(例如语音和数据网络)进行主动通信,并且已停止监听寻呼消息。 移动终端然后可以结束与其先前已经与之通信的网络的通信并且开始与已经发送寻呼消息的其他网络的通信。 例如,移动终端可以终止经由语音和数据网络的语音通信以便在接收到仅数据网络期望与移动终端建立通信会话的通知时经由仅数据网络接收多媒体消息服务消息。(String), US11/353542(String), 1139846400(Integer), US7668136B2(String), 1266854400(Integer), 1266854400(Integer), 美国(String), 4(Integer), US(String), 15(Integer), 12(Integer), US20020082029A1 | US20020154627A1 | US20020187804A1 | US20040037222A1 | US20040120283A1 | US20040185879A1 | US20040218575A1 | US20050276273A1 | US20060176870A1 | US6047071A | WO2004005236A1 | WO2004045236A1(String), 31(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\9244ff0e982e41ee99a7e8a2e6fbf214.png(String), 185955(Integer), 9244ff0e982e41ee99a7e8a2e6fbf214.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System, network, mobile terminal, computer program product and method for cross-paging a mobile terminal via a data burst message(String), 用于通过数据突发消息对移动终端进行跨页寻呼的系统、网络、移动终端、计算机程序产品和方法(String), US7668136B2(String), Systems and methods are provided to permit a network, such as a data only network, with which a mobile terminal is not currently communicating to notify the mobile terminal that the network desires to establish communication with the mobile terminal, even in instances in which the mobile terminal is actively communicating via another network, such as a voice and data network and has stopped monitoring for paging messages. The mobile terminal can then end communications with the network with which it has been previously communicating and commence communications with the other network that has transmitted the paging message. For example, a mobile terminal may terminate voice communications via a voice and data network in order to receive a Multimedia Message Service message via a data only network upon receiving notification that the data only network desires to establish a communications session with the mobile terminal.(String), 提供系统和方法以允许移动终端当前未与之通信的网络(例如纯数据网络)通知移动终端该网络希望与移动终端建立通信,即使在移动终端未与之通信的情况下也是如此。 终端正在通过另一个网络(例如语音和数据网络)进行主动通信,并且已停止监听寻呼消息。 移动终端然后可以结束与其先前已经与之通信的网络的通信并且开始与已经发送寻呼消息的其他网络的通信。 例如,移动终端可以终止经由语音和数据网络的语音通信以便在接收到仅数据网络期望与移动终端建立通信会话的通知时经由仅数据网络接收多媒体消息服务消息。(String), US11/353542(String), 1139846400(Integer), US7668136B2(String), 1266854400(Integer), 1266854400(Integer), 美国(String), 2(Integer), 4(Integer), US(String), 15(Integer), 12(Integer), US20020082029A1 | US20020154627A1 | US20020187804A1 | US20040037222A1 | US20040120283A1 | US20040185879A1 | US20040218575A1 | US20050276273A1 | US20060176870A1 | US6047071A | WO2004005236A1 | WO2004045236A1(String), \20230420\9244ff0e982e41ee99a7e8a2e6fbf214.png(String), 31(Integer), 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 1. A network comprising an agent configured to enable communication with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot, the agent including a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the agent to perform at least:receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal, andissuing a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the series of messages including:a first message for directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 1.一个网络包括一种代理,被配置为能够与插槽中的至少一个混合移动终端和至少一个非混合移动终端进行通信,该代理包括处理器和包含计算机程序代码的存储器,该存储器和计算机程序代码被配置为,处理器,使代理至少执行:从目标网络接收寻呼指示,寻呼指示指示目标网络期望与选定的混合移动终端通信,以及向至少一个混合移动终端和至少一个非混合移动终端发布一系列消息,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示至少一个非混合移动终端停止监视时隙;和第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 2. A network according to claim 1, wherein the series of messages further comprises a third message for directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 2.根据权利要求1的网络,其中该系列消息还包括第三消息,用于指示剩余的混合移动终端停止监视时隙。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 3. A network according to claim 1, wherein the data burst message includes a predefined code indicative of the page indication.(String), 3.根据权利要求1的网络,其中数据突发消息包括指示寻呼指示的预定义代码。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 4. A network according to claim 1, wherein the selected hybrid mobile terminal is configured to switch from the network to the target network in response to the data burst message.(String), 4.根据权利要求1的网络,其中所选择的混合移动终端被配置为响应于数据突发消息从网络切换到目标网络。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 5. A network according to claim 1, wherein the processor, memory and the computer program code further cause the agent to perform receiving network and service availability information from the target network.(String), 5.根据权利要求1的网络,其中处理器、存储器和计算机程序代码进一步使代理执行从目标网络接收网络和服务可用性信息。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.972 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 6. A network according to claim 1, wherein the at least one hybrid mobile terminal ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 6.根据权利要求1所述的网络,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则至少一个混合移动终端停止监视时隙。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 7. An apparatus comprising a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus to perform at least:receiving a series of messages from an anchor network in communication with the apparatus while the apparatus is monitoring a slot, the apparatus being enabled to communicate with a target network, the series of messages including:a first message for directing any non-hybrid mobile terminal in communication with the anchor network to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of a page indication to the apparatus, the page indication indicating that the target network desires to communicate with the apparatus.(String), 7.仪器包括处理器和存储器,包括计算机程序代码,存储器和计算机程序代码被配置为与处理器一起使装置至少执行:当该装置正在监视时隙时,从与该装置通信的锚网络接收一系列消息,该装置能够与目标网络通信,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示与锚定网络通信的任何非混合移动终端停止监视时隙;和第二消息包括指示对装置的寻呼指示的数据突发消息,寻呼指示指示目标网络期望与装置通信。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 8. An apparatus according to claim 7, wherein the data burst message includes a predefined code indicative of the page indication.(String), 8.根据权利要求7所述的装置,其中数据突发消息包括指示寻呼指示的预定义代码。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 9. An apparatus according to claim 7, wherein the apparatus is configured to switch from the anchor network to the target network in response to the data burst message.(String), 9.根据权利要求7所述的装置,其中该装置被配置为响应于数据突发消息从锚定网络切换到目标网络。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 10. An apparatus according to claim 7, wherein the apparatus ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 10.根据权利要求7所述的装置,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则装置停止监视时隙。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 11. A method comprising:receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal in a communication network enabled to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal monitoring a slot;sending a first message of a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the first message directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; andsending a second message of the series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 11.一种方法包括:从目标网络接收寻呼指示,该寻呼指示指示目标网络希望与通信网络中的选定混合移动终端通信,该通信网络能够与至少一个混合移动终端和至少一个非混合移动终端监控进行通信插槽;向至少一个混合移动终端和至少一个非混合移动终端发送一系列消息中的第一消息,第一消息指示至少一个非混合移动终端停止监视时隙,如果预定义字段第一消息的设置为预定值;和向至少一个混合移动终端和至少一个非混合移动终端发送一系列消息中的第二消息,第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 12. A method according to claim 11, further comprising sending a third message of the series of messages, the third message directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 12.根据权利要求11所述的方法,还包括发送一系列消息中的第三条消息,第三条消息指示剩余的混合移动终端停止监视时隙。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 13. A method according to claim 11, further comprising receiving network and service availability information from the target network.(String), 13.根据权利要求11所述的方法,还包括从目标网络接收网络和服务可用性信息。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.973 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 14. A method according to claim 11, wherein sending the first message further comprises directing the at least one hybrid mobile terminal to cease to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 14.根据权利要求11所述的方法,其中发送第一消息还包括如果消息系列的第一消息的预定义字段被设置为不同于预定值的值,则指示至少一个混合移动终端停止监视时隙。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 15. A computer program product comprising at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:a first executable portion for receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal in a communication network enabled to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal monitoring a slot;a second executable portion for sending a first message of a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the first message directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda third executable portion for sending a second message of the series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 15.计算机程序产品包括至少一个计算机可读存储介质,其中存储有计算机可读程序代码部分,计算机可读程序代码部分包括:第一可执行部分,用于从目标网络接收寻呼指示,该寻呼指示指示目标网络希望与通信网络中的选定混合移动终端通信,该通信网络能够与至少一个混合移动终端和至少一个非-混合移动终端监控槽;第二可执行部分,用于向至少一个混合移动终端和至少一个非混合移动终端发送一系列消息中的第一消息,第一消息指示至少一个非混合移动终端停止监视如果第一消息的预定义字段被设置为预定值,则时隙;和第三可执行部分,用于向至少一个混合移动终端和至少一个非混合移动终端发送消息系列中的第二消息,第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息移动终端。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 16. A computer program product according to claim 15, further comprising a fourth executable portion for sending a third message of the series of messages, the third message directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 16.根据权利要求15所述的计算机程序产品,还包括第四可执行部分,用于发送消息系列中的第三消息,第三消息指示混合移动终端中的其余混合移动终端停止监视时隙。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 17. A computer program product according to claim 15, further comprising a fourth executable portion for receiving network and service availability information from the target network.(String), 17.根据权利要求15所述的计算机程序产品,还包括第四可执行部分,用于从目标网络接收网络和服务可用性信息。(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 18. A computer program product according to claim 15, wherein the second executable portion includes further instructions for directing the at least one hybrid mobile terminal to cease to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 18.根据权利要求15所述的计算机程序产品,其中第二可执行部分包括进一步的指令,用于在消息系列的第一消息的预定义字段被设置为不同于预定值的值的情况下指示至少一个混合移动终端停止监视时隙。(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 19. A system comprising:an anchor network configured to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot; anda target network configured to issue a page indication to the anchor network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal,wherein the anchor network issues a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the series of messages including:a first message for directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 19.一个系统包括:锚定网络,用于在时隙中与至少一个混合移动终端和至少一个非混合移动终端进行通信;和目标网络被配置为向锚网络发出寻呼指示,该寻呼指示指示目标网络希望与选定的混合移动终端通信,其中,锚定网络向至少一个混合移动终端和至少一个非混合移动终端下发一系列消息,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示至少一个非混合移动终端停止监视时隙;和第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 20. A system according to claim 19, wherein the series of messages further comprises a third message for directing remaining ones of the at least one hybrid mobile terminals to cease monitoring the slot.(String), 20.根据权利要求19所述的系统,其中该系列消息还包括第三消息,用于指示至少一个混合移动终端中的其余混合移动终端停止监视时隙。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 21. A system according to claim 19, wherein the at least one hybrid mobile terminal ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 21.根据权利要求19所述的系统,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则至少一个混合移动终端停止监视时隙。(String), 1(Integer), 20(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 22. A network comprising:means for receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal, the network being enabled to communicate with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot; andmeans for issuing a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal, the series of messages including:a first message for directing the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value; anda second message including a data burst message indicative of the page indication to the selected hybrid mobile terminal.(String), 22.一个网络包括:用于从目标网络接收寻呼指示的装置,该寻呼指示指示目标网络希望与选定的混合移动终端通信,该网络能够与至少一个混合移动终端和至少一个非混合移动终端通信插槽中的端子;和用于向至少一个混合移动终端和至少一个非混合移动终端发布一系列消息的装置,该系列消息包括:如果第一消息的预定义字段被设置为预定值,则第一消息用于指示至少一个非混合移动终端停止监视时隙;和第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。(String), 0(Integer), 21(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 23. A network according to claim 22, further comprising a means for issuing a third message for directing remaining ones of the hybrid mobile terminals to cease monitoring the slot.(String), 23.根据权利要求22所述的网络,还包括用于发出第三消息以指示混合移动终端中的其余移动终端停止监视时隙的装置。(String), 1(Integer), 22(Integer), 21(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 24. A network according to claim 22, wherein the data burst message includes a predefined code indicative of the page indication.(String), 24.根据权利要求22所述的网络,其中数据突发消息包括指示寻呼指示的预定义代码。(String), 1(Integer), 23(Integer), 21(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 25. A network according to claim 22, wherein the at least one hybrid mobile terminal ceases to monitor the slot if the predefined field of the first message of the series of messages is set to a value other than the predetermined value.(String), 25.根据权利要求22所述的网络,其中如果消息系列的第一条消息的预定义字段被设置为不同于预定值的值,则至少一个混合移动终端停止监视时隙。(String), 1(Integer), 24(Integer), 21(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 26. A network comprising an agent configured to enable communication with at least one hybrid mobile terminal in a slot, the agent including a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the agent to perform at least:receiving a page indication from a target network, the page indication indicating that the target network desires to communicate with a selected hybrid mobile terminal, andissuing a data burst message having a predefined code indicative of the page indication to the selected hybrid mobile terminal, wherein the data burst message is issued in sequence following a general page message, and wherein the selected hybrid mobile terminal ceases to monitor the slot if the predefined field of the general page message is set to a value other than the predetermined value.(String), 26.一个网络包括代理被配置为能够与插槽中的至少一个混合移动终端进行通信,代理包括处理器和存储器,存储器包括计算机程序代码,存储器和计算机程序代码被配置为与处理器一起使代理执行至少:从目标网络接收寻呼指示,寻呼指示指示目标网络期望与选定的混合移动终端通信,以及向所选混合移动终端发布具有指示寻呼指示的预定义代码的数据突发消息,其中数据突发消息在通用寻呼消息之后按顺序发布,并且其中所选混合移动终端停止监视时隙,如果通用寻呼消息的预定义字段被设置为不同于预定值的值。(String), 0(Integer), 25(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 27. A network according to claim 26, wherein the data burst message is issued in sequence prior to a general page message.(String), 27.根据权利要求26所述的网络,其中数据突发消息在一般寻呼消息之前按顺序发出。(String), 1(Integer), 26(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 28. A network according to claim 26, wherein in response to a predefined field of the general page message having a predetermined value, the selected hybrid mobile terminal is directed to monitor the slot for subsequent transmission of the data burst message.(String), 28.根据权利要求26所述的网络,其中响应于具有预定值的通用寻呼消息的预定义字段,选择的混合移动终端被指示监视用于数据突发消息的后续传输的时隙。(String), 1(Integer), 27(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 29. An apparatus comprising a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus to perform at least:receiving a data burst message from an anchor network, the data burst message having a predefined code indicative of a page indication to the apparatus monitoring a slot while in communication with an anchor network and configured to communicate with a target network,wherein the page indication is received by the anchor network from the target network, the page indication indicating that the target network desires to communicate with the apparatus,wherein the data burst message is issued in sequence following a general page message, andwherein the apparatus ceases to monitor the slot if the predefined field of the general page message is set to a value other than the predetermined value.(String), 29.仪器包括处理器和存储器,包括计算机程序代码,存储器和计算机程序代码被配置为与处理器一起使装置至少执行:从锚定网络接收数据突发消息,该数据突发消息具有指示寻呼指示的预定义代码,该寻呼指示在与锚定网络通信时监控时隙并被配置为与目标网络通信,其中寻呼指示由锚网络从目标网络接收,寻呼指示指示目标网络期望与装置通信,其中,数据突发消息是在一般寻呼消息之后按顺序发出的,并且其中,如果通用寻呼消息的预定义字段被设置为不同于预定值的值,则该装置停止监视时隙。(String), 0(Integer), 28(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 30. An apparatus according to claim 29, wherein the data burst message is issued in sequence prior to a general page message.(String), 30.根据权利要求29所述的装置,其中数据突发消息在一般寻呼消息之前按顺序发出。(String), 1(Integer), 29(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:15.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185955(Integer), 31. An apparatus according to claim 29, wherein in response to a predefined field of the general page message having a predetermined value, the apparatus is directed to monitor the slot for subsequent transmission of the data burst message.(String), 31.根据权利要求29所述的装置,其中响应于具有预定值的通用寻呼消息的预定义字段,该装置被指示监视用于数据突发消息的后续传输的时隙。(String), 1(Integer), 30(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185955(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application claims the benefit of U.S. Provisional Application No. 60/652,674, filed Feb. 14, 2005, the contents of which are incorporated herein in their entirety. FIELD OF THE INVENTION [0002]The present invention generally relates to systems and methods of cross-paging a mobile terminal from one network while the mobile terminal operates in another network and, more particularly, relates to systems and methods of cross-paging a mobile terminal from a network via a data burst message (DBM) in another network within which the mobile terminal is operating. BACKGROUND OF THE INVENTION [0003]A communication network operates to communicate data between two, or more, communication stations. A communication network is formed, at a minimum, of a first communication station, forming a sending station, and a second communication station, forming a receiving station. The communication stations are interconnected by way of a communication channel. And data that is to be communicated by the first communication station to the second communication station is sent to the second communication station by way of the communication channel. The data that is to be communicated is converted by the first communication station into a form to permit its communication upon the communication channel. And the second communication station operates to detect the data communicated thereto and to recover the informational content thereof. [0004]Many different types of communication networks have been developed and implemented to effectuate the communication of the data between the communication stations. And with continued advancements in communication technologies, new types of communication networks, as well as improvements to existing communication networks, have been, and continue to be, made. [0005]A radio communication network is an exemplary type of communication network. A radio communication network utilizes radio communication channels upon which to transmit the data that is to be communicated between the communication stations operable therein. Radio communication channels are defined upon radio links forming part of the electromagnetic spectrum. As a radio link is utilized upon which to define the communication channels, the need otherwise to utilize wireline connections upon which to define communication channels is obviated. Implementation of a radio communication network is generally less costly than the corresponding costs that would be required to construct a conventional, wireline communication network. And a radio communication network can be implemented to form a mobile communication network. [0006]A cellular communication network, exemplary of a radio communication network, has been widely implemented and has achieved wide levels of usage. A cellular communication network provides for radio communications with mobile terminals. The mobile terminals permit telephonic communication to be effectuated therethrough. A cellular communication network includes a network part that is installed throughout a geographical area and with which the mobile terminals communicate by way of radio channels. Base transceiver stations, forming portions of the network part of the communication network, are installed at spaced apart locations throughout the geographical area that is to be covered by the communication network. Each of the base transceiver stations defines a cell encompassing a portion of the geographical area. When a mobile terminal is within the cell defined by a base transceiver station, communications are generally effectuable with the base transceiver station that defines the cell. [0007]As a mobile terminal travels between cells defined by different ones of the base transceiver stations, communication handoffs are effectuated to permit continued communications by, and with, the mobile terminal. Through appropriate positioning of the base transceiver stations, only relatively low-powered signals need to be generated to effectuate communications between a mobile terminal and a base transceiver station. Hand-offs of communications between successive base transceiver stations, as the mobile terminal moves between cells permit the continued communications without necessitating increases in the power levels at which the communication signals are transmitted. And, because only relatively low-powered signals need to be generated to effectuate communications, the same radio channels can be reused at different locations of the same cellular communication network. Efficient utilization of the frequency-spectrum allocation to the cellular communication network is thereby possible. [0008]Various operating specifications have been promulgated that define operational parameters by which cellular, as well as other, communication networks are to be operable. Successive generations of cellular communication networks, incorporating technological advancements, as such advancements become available, have been defined by successive generations, or updates to, operational specifications. First-generation (1G) and second-generation (2G) networks have been widely implemented and have achieved significant levels of usage. In this regard, the goal of second generation (2G) networks (e.g., IS-95) was to enable pre-defined mobile telephony services that were spectrum efficient and economically viable. The result was a network that provided mobile low rate circuit switched voice communications and low rate data communications. The success of 2G is evidenced by its consumer acceptance and popularity that exceeded expectations. As more consumers used mobile terminal services, certain increasing numbers of them manifested a desire for more capacity in both voice and data. The cellular industry responded with third-generation (3G) (e.g., cdma2000) networks, the next generation that introduced packet switched data networks. [0009]Code Division Multiple Access (CDMA) was introduced into cellular based, mobile communication systems in the early 1990s with the introduction of the IS-95 standard. Since then, CDMA technology has been well accepted in the wireless industry and has been widely disseminated reaching literally hundreds of millions of subscribers throughout the world. More recently, 3G backward-compatible evolutions of the IS-95 standard, such as the cdma2000 1X standard, have been developed to further improve the voice service capacity of CDMA while providing higher data rates for data services. As part of this evolution, the cdma2000 1X-EVDO network was developed to optimize wireless, high speed packet data services, such as may be facilitated by the Internet Protocol (IP). However, as networks such as cdma2000 1X-EVDO only support packet data services, mobile terminals, sometimes referred to as hybrid terminals, have been developed that are capable of accessing networks, such as cdma2000 1X, that provide both voice and data services, as well as networks such as cdma2000 1X-EVDO that provide higher-speed packet data services. Thus, a hybrid terminal could utilize a cdma2000-1X network for voice communications and for short message service (SMS), and a cdma2000-1X-EVDO network for multimedia message service (MMS) and for other data communications. [0010]In a network such as cdma2000 1X or 1X-EVDO, when a message (i.e., a “call”) is to be terminated at a mobile terminal, the network infrastructure broadcasts a paging message to alert the mobile terminal of the message. Monitoring channels of the respective network, the mobile terminal detects the paging message and, in response, performs various operations to receive the terminating message. With respect to the detection of a paging message, slotted mode operation was introduced in cdma2000 1X systems to conserve the life of a mobile terminal's battery. In this regard, the channel via which paging messages are transmitted, e.g., the forward common signaling logical channel (f-csch), is divided into 2048 slots. A mobile terminal operating in slotted mode is therefore assigned one of the slots and only needs to monitor its assigned slot and subsequent slot. See, for example, FIG. 1. Other than its assigned slot and the subsequent slot, the mobile terminal can opt to turn off its receiver/transmitter and to defer other non-vital processing. Each paging slot in a cdma2000 1X system is 80 ms in length and the slot assigned to a mobile terminal is determined through a hash algorithm defined in the cdma2000 1X standard. By way of example, the hash algorithm takes the phone number (MIN) of the mobile terminal and determines which slot of the 2048 possible slots (denoted slots 0˜2047) is the slot assigned to the mobile terminal. Since the cdma200 1X network also uses the same hash algorithm, the network is also aware which is the slot assigned to the mobile terminal. [0011]Also defined in a cdma2000 1X system is the concept of a slot cycle. In this regard, once a mobile terminal determines its assigned slot, the mobile terminal will wake up every slot cycle to check if there is page indication or other message addressed to it in its assigned slot or in the subsequent slot. As shown in FIG. 1, the mobile terminals may have different slot cycles with the cycle of MN 0 being 1.28 seconds and the cycle of MN 7 being 2.56 seconds, for example. Moreover, by permitting messages to be transmitted to the mobile terminal both in its assigned slot and in the subsequent slot, the network has improved flexibility in regards to the scheduling of the messages to the mobile terminal which is particularly useful in instances in which the paging channel is crowded. [0012]Since there are only 2048 possible slot positions, different mobile terminals can be assigned the same slot. See FIG. 1 in which MN 0, MN 3 and MN 4 are all assigned to one slot, and MN 1 and MN 7 are all assigned to another slot. Before monitoring its assigned slot, a mobile terminal does not know whether there will be pages/messages for the mobile terminal in its next assigned slot. If the network does not need to page or transmit any other message to any of the mobile terminals in that assigned slot, the network advantageously advises the mobile terminals assigned to the slot as soon as possible within the slot so that mobile terminals can go to sleep as early as possible, thereby further conserving battery power. As shown in FIG. 2, the mechanism in a cdma2000 1X network is to set the CLASS—0_DONE field to ‘1’ in the General Page Message (GPM) to indicate that there are no pages/messages for the mobile terminals of the respective slot. Upon receiving this GPM in the assigned slot, the mobile terminals can go to sleep immediately, i.e., prior to the end of the slot as shown in FIG. 2. In the common instance in which many mobile terminals utilize the same slot, the network cannot transmit the GPM with the CLASS—0_DONE field set to 1 until any messages have been transmitted to the mobile terminals assigned to the slot. For those mobile terminals that are not receiving a message, the mobile terminals must stay awake, during the transmission of messages to other mobile terminals, thereby unnecessarily consuming battery power. [0013]As will be appreciated by those skilled in the art, however, in various instances of operating in a network such as cdma2000 1X, a mobile terminal may not otherwise monitor for paging messages from a cdma2000 1X-EVDO network, thereby conserving battery power. For example, a mobile terminal may initially be operating in a cdma2000 1X-EVDO network in conjunction with a data application, e.g., the download of an ftp file. At some point in time, the data application may go dormant, such as upon completion of the ftp file download, and the mobile terminal may be placed in an idle state by the cdma2000 1X-EVDO network. The mobile terminal may thereafter switch to a cdma2000 1X network. The mobile terminal may switch to the cdma2000 1X network for many reasons including the loss of network services by the cdma2000 1X-EVDO network coupled with the discovery of network services by the cdma2000 1X network or the placing of a voice call by the mobile terminal. Since the mobile terminal is now monitoring a different frequency for signals from the cdma2000 1X network than from the cdma2000 1X-EVDO network, the mobile terminal will no longer be monitoring for paging messages from the cdma2000 1X-EVDO network. In addition to frequency differences, differences in the over-the-air technology between two networks would also prevent the mobile terminal active in one network from monitoring for paging messages in another network. In such instances, although the cdma2000 1X-EVDO network may have a message to be terminated at the mobile terminal operating in the cdma2000 1X network, such as an advertisement or the download of a new movie, the cdma2000 1X-EVDO network may be unable to reach the mobile terminal via a paging message. SUMMARY OF THE INVENTION [0014]In light of the foregoing background, embodiments of the present invention provide a system, a network, a mobile terminal and a method for cross-paging a mobile terminal even in instances in which the mobile terminal has stopped monitoring for paging messages. In this regard, a target network, such as a data only network (e.g., cdma2000 1X-EVDO), with which the mobile terminal is not currently communicating may notify the mobile terminal that the target network desires to establish communication with the mobile terminal, even in instances in which the mobile terminal is actively communicating via an anchor network, such as a voice and data network (e.g., cdma2000 1X) and has stopped monitoring for paging messages from other networks. As such, the mobile terminal can end communications with the anchor network and can then commence communications with the target network. For example, a user of a mobile terminal may terminate voice communications via a voice and data network in order to receive a MMS message or download a movie via a data only network upon receiving notification that the data only network desires to establish a communications session with the mobile terminal. [0015]The target network may notify the mobile terminal of its desire to communicate with the mobile terminal by means of a message, such as a page message, transmitted to the anchor network. The anchor network of this embodiment can then issue a Data Burst Message (DBM) including a predefined code to the mobile terminal notifying the mobile terminal of the inquiry from the target network. In response to the DBM, the mobile terminal may determine if a switch should be made from the anchor network to the target network and, if so, may end the anchor traffic channel assignment and issue a connection request to the target network to initiate target network traffic and service setup. Along with a page notification, the target network can provide the anchor network with network and service availability information. This network and service availability information can assist the user in determining whether to switch to the target network and, if so, can assist in rapidly and efficiently performing the target network traffic and service setup. [0016]According to one embodiment, the signaling sequence is altered for those mobile terminals that are in an idle state. In the slot to which the mobile terminals are assigned, a general page message (GPM) may be transmitted with a predefined field set to a predetermined value which notifies all non-hybrid mobile terminals, i.e., those mobile terminals that would be incapable of communicating with the target network, assigned to the slot to cease monitoring the slot and to go back to sleep. The hybrid mobile terminals continue monitoring the slot so as to receive the DBM which is directed to one or more hybrid mobile terminals. A conventional GPM can then be issued to direct the remaining hybrid mobile terminals, i.e., those hybrid mobile terminals that have not switched to a target network, to cease monitoring the slot and to go back to sleep. By employing the signaling sequence of this embodiment of the present invention, the battery life of the non-hybrid mobile terminals is therefore further conserved. [0017]According to exemplary embodiments, a method and computer program product is provided for cross-paging a selected hybrid mobile terminal which includes receiving a page indication from a target network. The page indication indicates that the target network desires to communicate with the selected hybrid mobile terminal. A first message of a series of messages is then sent to the selected hybrid mobile terminal which is one of a group of hybrid mobile terminals and non-hybrid mobile terminals. The first message directs the at least one non-hybrid mobile terminal to cease monitoring a slot if a predefined field of the first message is set to a predetermined value. A second message of the series of messages is then sent. The second message includes a data burst message indicative of the page indication to the selected hybrid mobile terminal. A third message of the general page message may then be sent. The third message directs any remaining hybrid mobile terminals to cease monitoring the slot. [0018]According to another exemplary embodiment, a system and networks for cross-paging a selected hybrid mobile terminal are provided. The system includes an anchor network and a target network. The anchor network is capable of communication with at least one hybrid mobile terminal and at least one non-hybrid mobile terminal in a slot. The target network is capable of issuing a page indication to the anchor network. The page indication indicates that the target network desires to communicate with the selected hybrid mobile terminal, which is one of the hybrid mobile terminals. The anchor network issues a series of messages to the at least one hybrid mobile terminal and the at least one non-hybrid mobile terminal. The series of messages includes a first message and a second message. The first message directs the at least one non-hybrid mobile terminal to cease monitoring the slot if a predefined field of the first message is set to a predetermined value. The second message includes a data burst message indicative of the page indication to the selected hybrid mobile terminal. [0019]According to another exemplary embodiment, a mobile terminal capable of being cross-paged is provided. The mobile terminal monitors a slot while in communication with an anchor network and is capable of communication with a target network. The mobile terminal includes a controller capable of receiving a series of messages from the anchor network. The series of messages includes a first message and a second message. The first message directs any non-hybrid mobile terminal in communication with the anchor network to cease monitoring the slot if a predefined field of the first message is set to a predetermined value. The second message includes a data burst message indicative of a page indication to the mobile terminal, with the page indication indicating that the target network desires to communicate with the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0020]Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein: [0021]FIG. 1 is a schematic representation of the slotted mode operation provided by a conventional cdma2000 system; [0022]FIG. 2 is a schematic representation of the use of GPM in a conventional manner to halt the monitoring of a slot as soon as practical; [0023]FIG. 3 is a block diagram of one type of mobile node and system that would benefit from embodiments of the present invention; [0024]FIG. 4 is a schematic block diagram of an entity capable of operating as a mobile node, home agent, foreign agent and/or correspondent node, in accordance with embodiments of the present invention; [0025]FIG. 5 is a schematic block diagram of a mobile node, in accordance with one embodiment of the present invention; [0026]FIG. 6 is a control flow diagram illustrating communication between various entities performing a method of cross-paging a mobile terminal, in accordance with one embodiment of the present invention; [0027]FIG. 7 is a schematic representation of a DBM transmitted in a slot in accordance with one embodiment of the present invention; [0028]FIG. 8 is a schematic representation of a modified GPM and a DBM transmitted in a slot in accordance with another embodiment of the present invention; and [0029]FIG. 9 is a block diagram of an exemplary method for cross-paging a mobile terminal via a data burst message in accordance with an exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION [0030]The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. [0031]Referring to FIG. 3, an illustration of one type of system that would benefit from the present invention is provided. The system, method and computer program product of embodiments of the present invention will be primarily described in conjunction with mobile communications applications. It should be understood, however, that the system, method and computer program product of embodiments of the present invention can be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries. For example, the system, method and computer program product of embodiments of the present invention can be utilized in conjunction with wireline and/or wireless network (e.g., Internet) applications. [0032]As shown, the system can include a mobile terminal, hereinafter a mobile node (MN), 10 capable of transmitting signals to and for receiving signals from base sites or base stations (BS) 14, two of which are shown in FIG. 3 (shown and described below as including an anchor BS 14a and a target BS 14b). The base station is a part of one or more cellular or mobile networks that include elements required to operate the network, such as a mobile switching center (MSC) (not shown). As well known to those skilled in the art, the mobile network may also be referred to as a Base Station/MSC/Interworking function (BMI). In operation, the MSC is capable of routing calls to and from the terminal when the terminal is making and receiving calls. The MSC can also provide a connection to landline trunks when the terminal is involved in a call. In addition, the MSC can be capable of controlling the forwarding of messages to and from the terminal, and can also control the forwarding of messages for the terminal to and from a messaging center. [0033]The MN 10 can also be coupled to a data network. For example, the BS 14 can be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN). In one typical embodiment, the BS is coupled to a gateway, which is coupled to the data network, such as an Internet Protocol (IP) network 16. The gateway can comprise any of a number of different entities capable of providing network connectivity between the MN and other nodes directly or indirectly coupled to the data network. As will be appreciated, the gateway can be described in any of a number of different manners, such as a home agent (HA) 18, foreign agent (FA) 20 (shown and described below as including an anchor FA 20a and a target FA 20b), packet data serving node (PDSN), access router or the like. In this regard, a HA can comprise a router within a home network 22 of the MN. The HA is capable of tunneling data for delivery to the MN when the MN is away from home, and can maintain current location information for the MN. A FA, on the other hand, can comprise router within a visited network 24 of the MN (shown and described below as including an anchor visited network 24a and a target visited network 24b). The FA provides routing services to the MN while the MN is registered with the visited network. In operation, the FA detunnels data from the HA, and delivers the data to the MN. Then, for data sent from a MN registered with the visited network, the FA can serve as a default router. [0034]The other nodes coupled to the MN 10 via the IP network 16 can comprise any of a number of different devices, systems or the like capable of communicating with the MN in accordance with embodiments of the present invention. As described herein, a node capable of communicating with the MN via the IP network is referred to as a correspondent node (CN) 26, one of which is shown in FIG. 3. The other CNs can comprise, for example, personal computers, server computers or the like. Additionally or alternatively, for example, one or more CNs can comprise, other MNs, such as mobile telephones, portable digital assistants (PDAs), pagers, laptop computers, or the like. [0035]Although not every element of every possible network is shown and described herein, it should be appreciated that the MN 10 can be coupled to one or more of any of a number of different networks. As shown and described herein, the anchor visited network 24a is capable of supporting communication in accordance with third-generation (3G) mobile communication protocol cdma2000 1X (TIA/EIA/IS-2000), while the target visited network 24b is capable of supporting communication in accordance with 3G mobile communication protocol cdma2000 1XEV-DO (TIA/EIA/IS-856). It should be appreciated, however, that the mobile network(s) may be equally capable of operating in accordance with embodiments of the present invention while supporting communication in accordance with any one or more of a number of other first-generation (1G), second-generation (2G), 2.5G, 3G or other mobile communication protocols. For example, one or more networks capable of supporting communication in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, IS-95 (CDMA) or the like; 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE) or the like; and/or 3G wireless communication protocols Universal Mobile Telephone System (UMTS) network employing Wideband Code Division Multiple Access (WCDMA) radio access technology, cdma2000 1XEV-DV or the like. [0036]Referring now to FIG. 4, a block diagram of an entity capable of operating as a MN 10, HA 18, FA 20 and/or CN 26 is shown in accordance with one embodiment of the present invention. Although shown as separate entities, in some embodiments, one or more entities may support one or more of a MN, HA, FA and/or CN, logically separated but co-located within the entit(ies). For example, a single entity may support a logically separate, but co-located, HA and CN. Also, for example, a single entity may support a logically separate, but co-located FA and CN. [0037]As shown, the entity capable of operating as a MN 10, HA 18, FA 20 and/or CN 26 can generally include a processor 30 connected to a memory 32. The memory can comprise volatile and/or non-volatile memory, and typically stores content, data or the like. For example, the memory typically stores content transmitted from, and/or received by, the entity. Also for example, the memory typically stores software applications, instructions or the like for the processor to perform steps associated with operation of the entity in accordance with embodiments of the present invention. [0038]In addition to the memory 32, the processor 30 can also be connected to at least one interface or other means for displaying, transmitting and/or receiving data, content or the like. In this regard, the interface(s) can include at least one communication interface 34 or other means for transmitting and/or receiving data, content or the like, as well as at least one user interface that can include a display 36 and/or a user input interface 38. The user input interface, in turn, can comprise any of a number of devices allowing the entity to receive data from a user, such as a keypad, a touch display, a joystick or other input device. [0039]Reference is now made to FIG. 5, which illustrates one type of MN 10 that would benefit from embodiments of the present invention. It should be understood, however, that the MN illustrated and hereinafter described is merely illustrative of one type of MN that would benefit from the present invention and, therefore, should not be taken to limit the scope of the present invention. While several embodiments of the MN are illustrated and will be hereinafter described for purposes of example, other types of MNs, such as portable digital assistants (PDAs), pagers, laptop computers and other types of electronic systems, can readily employ the present invention. [0040]As shown, in addition to an antenna 40, the MN 10 includes a transmitter 42, a receiver 44, and a controller 46 that provides signals to and receives signals from the transmitter and receiver, respectively. These signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data. In this regard, the MN can be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. As explained herein, the MN is capable of operating in accordance with the cdma2000 1X and cdma2000 1XEV-DO communication protocols. It should be understood, however, that the MN may more generally be capable of operating in accordance with any of a number of 1G, 2G, 2.5G, 3G or other communication protocols. [0041]It is understood that the controller 46 includes the circuitry required for implementing the audio and logic functions of the MN 10. For example, the controller may be comprised of a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits. The control and signal processing functions of the MN are allocated between these devices according to their respective capabilities. The controller can additionally include an internal voice coder (VC) 46A, and may include an internal data modem (DM) 46B. Further, the controller may include the functionality to operate one or more software programs, which may be stored in memory (described below). For example, the controller may be capable of operating a connectivity program, such as a conventional Web browser. The connectivity program may then allow the MN to transmit and receive Web content, such as according to HTTP and/or the Wireless Application Protocol (WAP), for example. [0042]The MN 10 also comprises a user interface including a conventional earphone or speaker 48, a ringer 50, a microphone 52, a display 54, and a user input interface, all of which are coupled to the controller 46. The user input interface, which allows the MN to receive data, can comprise any of a number of devices allowing the MN to receive data, such as a keypad 56, a touch display (not shown) or other input device. In embodiments including a keypad, the keypad includes the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the MN. Although not shown, the MN can include a battery, such as a vibrating battery pack, for powering the various circuits that are required to operate the MN, as well as optionally providing mechanical vibration as a detectable output. [0043]The MN 10 can also include memory, such as a subscriber identity module (SIM) 58, a removable user identity module (R-UIM) or the like, which typically stores information elements related to a mobile subscriber. In addition to the SIM, the MN can include other removable and/or fixed memory. In this regard, the MN can include volatile memory 60, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The MN can also include other non-volatile memory 62, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively comprise an EEPROM, flash memory or the like. The memories can store any of a number of pieces of information,(String), 相关申请的交叉引用 [0001] 本申请要求 2005 年 2 月 14 日提交的美国临时申请第 60/652,674 号的权益,其内容全部并入本文。 发明领域 [0002] [0001] 本发明一般涉及当移动终端在另一网络中操作时从一个网络交叉寻呼移动终端的系统和方法,更具体地,涉及通过数据从网络交叉寻呼移动终端的系统和方法。 移动终端在其中运行的另一个网络中的突发消息 (DBM)。 发明背景 [0003] 通信网络用于在两个或多个通信站之间传送数据。 通信网络至少由构成发送站的第一通信站和构成接收站的第二通信站构成。 通信站通过通信信道相互连接。 并且要由第一通信站传送到第二通信站的数据通过通信信道被发送到第二通信站。 要传送的数据由第一通信站转换成允许其在通信信道上传送的形式。 并且第二通信站操作以检测向其传送的数据并恢复其信息内容。 [0004] 已经开发和实施了许多不同类型的通信网络以实现通信站之间的数据通信。 随着通信技术的不断进步,新型通信网络以及对现有通信网络的改进已经并将继续进行。 [0005] 无线电通信网络是通信网络的示例类型。 无线电通信网络利用无线电通信信道来传输要在其中运行的通信站之间通信的数据。 无线通信信道是根据构成电磁频谱一部分的无线链路定义的。 由于使用无线电链路来定义通信信道,因此避免了使用有线连接来定义通信信道的需要。 无线通信网络的实现通常比构建传统的有线通信网络所需的相应成本要低。 并且可以实现无线电通信网络以形成移动通信网络。 [0006] 作为无线电通信网络的示例的蜂窝通信网络已经被广泛实施并且已经达到了广泛的使用水平。 蜂窝通信网络提供与移动终端的无线电通信。 移动终端允许通过其实现电话通信。 蜂窝通信网络包括遍及地理区域安装的网络部分并且移动终端通过无线电信道与其通信。 构成通信网络的网络部分的部分的基站收发信机安装在整个地理区域中的间隔开的位置,该地理区域将被通信网络覆盖。 每个基站收发器定义了一个包含一部分地理区域的小区。 当移动终端位于基站收发信台定义的小区内时,通常可以与定义该小区的基站收发信台进行通信。 [0007]当移动终端在由不同的基站收发信台定义的小区之间移动时,实现通信切换以允许移动终端继续进行通信并与移动终端进行通信。 通过基站收发器的适当定位,仅需要生成相对低功率的信号来实现移动终端和基站收发器之间的通信。 当移动终端在小区之间移动时,连续基站收发信台之间的通信切换允许继续通信,而无需增加通信信号传输的功率电平。 并且,因为只需要产生相对低功率的信号来实现通信,所以可以在同一蜂窝通信网络的不同位置重复使用相同的无线电信道。 从而可以有效地利用分配给蜂窝通信网络的频谱。 [0008] 已经颁布了各种操作规范,这些规范定义了蜂窝以及其他通信网络可操作的操作参数。 结合技术进步的连续几代蜂窝通信网络,随着此类进步变得可用,已由连续几代或更新操作规范定义。 第一代 (1G) 和第二代 (2G) 网络已得到广泛实施,并取得了显着的使用水平。 在这方面,第二代 (2G) 网络(例如 IS-95)的目标是实现频谱高效且经济可行的预定义移动电话服务。 结果是一个提供移动低速率电路交换语音通信和低速率数据通信的网络。 2G 的成功体现在其消费者接受度和受欢迎程度超出预期。 随着越来越多的消费者使用移动终端服务,越来越多的消费者表现出对更多语音和数据容量的需求。 蜂窝行业以第三代 (3G)(例如 cdma2000)网络作为回应,下一代网络引入了分组交换数据网络。 [0009] 随着 IS-95 标准的推出,码分多址 (CDMA) 在 1990 年代初被引入基于蜂窝的移动通信系统。 从那时起,CDMA 技术在无线行业得到了广泛接受,并得到了广泛传播,几乎覆盖了全世界数亿用户。 最近,已经开发了 IS-95 标准的 3G 向后兼容演进,例如 cdma2000 1X 标准,以进一步提高 CDMA 的语音服务容量,同时为数据服务提供更高的数据速率。 作为这一演进的一部分,开发了 cdma2000 1X-EVDO 网络以优化无线、高速分组数据服务,例如因特网协议 (IP) 可能促进的服务。 然而,由于cdma2000 1X-EVDO等网络仅支持分组数据业务,因此开发了移动终端,有时也称为混合终端,能够接入提供语音和数据业务的网络,如cdma2000 1X,如 以及提供更高速分组数据服务的网络,例如 cdma2000 1X-EVDO。 因此,混合终端可以利用 cdma2000-1X 网络进行语音通信和短消息服务 (SMS),并利用 cdma2000-1X-EVDO 网络进行多媒体消息服务 (MMS) 和其他数据通信。 [0010]在 cdma2000 1X 或 1X-EVDO 等网络中,当消息(即“呼叫”)要在移动终端终止时,网络基础设施会广播寻呼消息以提醒移动终端该消息。 监视相应网络的信道,移动终端检测寻呼消息并作为响应执行各种操作以接收终止消息。 关于寻呼消息的检测,在 cdma2000 1X 系统中引入时隙模式操作以节省移动终端电池的寿命。 在这点上,传送寻呼消息的信道,例如前向公共信令逻辑信道(f-csch),被分成2048个时隙。 因此,以时隙模式运行的移动终端被分配了一个时隙,并且只需要监视其分配的时隙和后续时隙。 参见例如图1。除了分配给它的时隙和随后的时隙之外,移动终端可以选择关闭它的接收器/发射器并推迟其他非重要的处理。 cdma2000 1X 系统中的每个寻呼时隙长度为 80 ms,分配给移动终端的时隙是通过 cdma2000 1X 标准中定义的散列算法确定的。 举例来说,散列算法采用移动终端的电话号码(MIN)并确定2048个可能的时隙(表示为时隙0~2047)中的哪个时隙是分配给移动终端的时隙。 由于 cdma200 1X 网络也使用相同的散列算法,网络也知道分配给移动终端的时隙。 [0011] 在 cdma2000 1X 系统中还定义了时隙周期的概念。 就此而言,一旦移动终端确定了其分配的时隙,移动终端将在每个时隙周期唤​​醒以检查在其分配的时隙或后续时隙中是否存在寻呼指示或寻址到它的其他消息。 如图1所示,移动终端的时隙周期可以与MN的周期不同 0 为 1.28 秒和 MN 的周期 7 例如,为 2.56 秒。 此外,通过允许在分配给移动终端的时隙和随后的时隙中向移动终端发送消息,网络在向移动终端调度消息方面提高了灵活性,这在寻呼的情况下特别有用 通道拥挤。 [0012] 由于只有 2048 个可能的时隙位置,不同的移动终端可以分配相同的时隙。 见图1,其中MN 0 , 明尼苏达州 3 和锰 4 都分配到一个时隙,MN 1 和锰 7 都分配给另一个插槽。 在监视其分配的时隙之前,移动终端不知道在其下一个分配的时隙中是否有针对该移动终端的寻呼/消息。 如果网络不需要寻呼或发送任何其他消息到指定时隙中的任何移动终端,则网络有利地在该时隙内尽快通知指定给该时隙的移动终端,以便移动终端可以进入休眠状态 尽早,从而进一步节省电池电量。 如图 2 所示,cdma2000 1X 网络中的机制是设置 CLASS — 通用寻呼消息 (GPM) 中的 0_DONE 字段为“1”,指示相应时隙的移动终端没有寻呼/消息。 在分配的时隙中收到此 GPM 后,移动终端可以立即进入休眠状态,即在时隙结束之前,如图 2 所示。在许多移动终端使用同一时隙的常见情况下,网络无法 用 CLASS 传输 GPM — 0_DONE 字段设置为 1,直到任何消息都已传输到分配给该时隙的移动终端。 对于那些没有接收到消息的移动终端,在向其他移动终端发送消息期间,移动终端必须保持清醒,从而不必要地消耗电池电量。 [0013]然而,如本领域技术人员将理解的那样,在诸如cdma2000 1X的网络中操作的各种实例中,移动终端可能不以其他方式监视来自cdma2000 1X-EVDO网络的寻呼消息,从而节省电池电量。 例如,移动终端最初可能在 cdma2000 1X-EVDO 网络中结合数据应用程序运行,例如,下载 ftp 文件。 在某个时间点,数据应用程序可能会进入休眠状态,例如在完成 ftp 文件下载时,并且移动终端可能会被 cdma2000 1X-EVDO 网络置于空闲状态。 此后移动终端可以切换到cdma2000 1X网络。 移动终端切换到cdma2000 1X网络的原因有很多,包括cdma2000 1X-EVDO网络的网络服务丢失以及cdma2000 1X网络发现网络服务或者移动终端发起语音呼叫。 由于移动终端现在正在监视来自 cdma2000 1X 网络和来自 cdma2000 1X-EVDO 网络的不同频率的信号,因此移动终端将不再监视来自 cdma2000 1X-EVDO 网络的寻呼消息。 除了频率差异之外,两个网络之间无线技术的差异也会阻止在一个网络中活动的移动终端监听另一个网络中的寻呼消息。 在这种情况下,尽管 cdma2000 1X-EVDO 网络可能有一条消息要在 cdma2000 1X 网络中运行的移动终端终止,例如广告或下载新电影,但 cdma2000 1X-EVDO 网络可能无法 通过寻呼消息到达移动终端。 发明内容 [0014] 鉴于上述背景,本发明实施例提供了一种即使在移动终端停止监听寻呼消息的情况下,也能对移动终端进行交叉寻呼的系统、网络、移动终端及方法。 就此而言,移动终端当前未与之通信的诸如纯数据网络(例如,cdma2000 1X-EVDO)的目标网络可以通知移动终端目标网络期望与移动终端建立通信, 即使在移动终端通过诸如语音和数据网络(例如,cdma2000 1X)之类的锚定网络主动通信并且已经停止监视来自其他网络的寻呼消息的情况下。 这样,移动终端可以结束与锚定网络的通信,然后可以开始与目标网络的通信。 例如,移动终端的用户可以在接收到仅数据网络希望与 移动终端。 [0015] 目标网络可以通过发送给锚定网络的消息,例如寻呼消息,通知移动终端其希望与移动终端进行通信。 然后,该实施例的锚定网络可以向移动终端发出包括预定义代码的数据突发消息(DBM),通知移动终端来自目标网络的查询。 响应于DBM,移动终端可以确定是否应该从锚定网络切换到目标网络,并且如果是,则可以结束锚定业务信道分配并且向目标网络发出连接请求以启动目标网络 流量和服务设置。 连同页面通知,目标网络可以向锚定网络提供网络和服务可用性信息。 该网络和服务可用性信息可以帮助用户确定是否切换到目标网络,如果是,则可以帮助快速有效地执行目标网络流量和服务设置。 [0016]根据一个实施例,对于处于空闲状态的那些移动终端改变信令序列。 在分配给移动终端的时隙中,可以发送通用寻呼消息(GPM),其中预定义字段设置为预定值,通知所有非混合移动终端,即那些不能通信的移动终端 与目标网络,分配给插槽以停止监视插槽并返回睡眠状态。 混合移动终端继续监视时隙以便接收指向一个或多个混合移动终端的DBM。 然后可以发布传统的 GPM 以指示剩余的混合移动终端,即,那些还没有切换到目标网络的混合移动终端,停止监视时隙并返回睡眠。 通过采用本发明该实施例的信令序列,因此进一步节省了非混合移动终端的电池寿命。 [0017] 根据示例性实施例,提供了一种用于交叉寻呼所选择的混合移动终端的方法和计算机程序产品,其包括从目标网络接收寻呼指示。 寻呼指示表明目标网络希望与选定的混合移动终端进行通信。 然后将一系列消息中的第一条消息发送到所选择的混合移动终端,该混合移动终端是一组混合移动终端和非混合移动终端中的一个。 如果第一消息的预定义字段被设置为预定值,则第一消息指示至少一个非混合移动终端停止监视时隙。 然后发送该系列消息中的第二条消息。 第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。 然后可以发送通用寻呼消息的第三消息。 第三条消息指示任何剩余的混合移动终端停止监视时隙。 [0018] 根据另一个示例性实施例,提供了一种用于交叉寻呼所选择的混合移动终端的系统和网络。 该系统包括锚网络和目标网络。 锚定网络能够在时隙中与至少一个混合移动终端和至少一个非混合移动终端进行通信。 目标网络能够向锚网络发出寻呼指示。 寻呼指示指示目标网络期望与选择的混合移动终端通信,该混合移动终端是混合移动终端之一。 锚定网络向至少一个混合移动终端和至少一个非混合移动终端发布一系列消息。 该系列消息包括第一消息和第二消息。 如果第一消息的预定义字段被设置为预定值,则第一消息指示至少一个非混合移动终端停止监视时隙。 第二消息包括指示对所选混合移动终端的寻呼指示的数据突发消息。 [0019] 根据另一示例性实施例,提供了一种能够跨页的移动终端。 移动终端在与锚定网络通信的同时监听时隙,能够与目标网络进行通信。 移动终端包括能够从锚定网络接收一系列消息的控制器。 该系列消息包括第一消息和第二消息。 如果第一消息的预定义字段被设置为预定值,则第一消息指示与锚定网络通信的任何非混合移动终端停止监视时隙。 第二消息包括指示对移动终端的寻呼指示的数据突发消息,寻呼指示指示目标网络期望与移动终端通信。 附图的简要说明 [0020] [0032] 已经以一般术语描述了本发明,现在将参考附图,这些附图不一定按比例绘制,并且其中: [0021] 图1是传统cdma2000系统提供的时隙模式操作的示意图; [0022]图2是以常规方式使用GPM来尽快停止对时隙的监视的示意图; [0023] 图3是受益于本发明实施例的一种类型的移动节点和系统的框图; [0024] 图4是根据本发明实施例的能够作为移动节点、归属代理、外地代理和/或通信节点操作的实体的示意框图; [0025] 图5是根据本发明的一个实施例的移动节点的示意框图; [0026] 图6是说明根据本发明的一个实施例的执行跨寻呼移动终端的方法的各种实体之间的通信的控制流程图; [0027] 图7是根据本发明的一个实施例在时隙中传输的DBM的示意图; [0028] 图8是根据本发明的另一个实施例的在时隙中传输的修改的GPM和DBM的示意图; 和 [0029] 图9是根据本发明示例性实施例的用于经由数据突发消息交叉寻呼移动终端的示例性方法的框图。 发明详述 [0030] 现在将在下文中参考附图更全面地描述本发明,其中示出了本发明的优选实施例。 然而,本发明可以以许多不同的形式来体现,并且不应被解释为限于在此阐述的实施例; 相反,提供这些实施例是为了使本公开透彻和完整,并将本发明的范围充分地传达给本领域的技术人员。 相同的数字始终指代相同的元素。 [0031] 参考图3,提供了将受益于本发明的一种类型的系统的图示。 将主要结合移动通信应用来描述本发明实施例的系统、方法和计算机程序产品。 然而,应当理解,本发明的实施例的系统、方法和计算机程序产品可以结合移动通信行业中和移动通信行业之外的各种其他应用来使用。 例如,本发明实施例的系统、方法和计算机程序产品可以结合有线和/或无线网络(例如因特网)应用程序使用。 [0032] 如图所示,该系统可以包括移动终端,以下称为移动节点(MN), 10 能够向基站或基站 (BS) 发送信号并从中接收信号 14 ,其中两个显示在图 3 中(在下面显示和描述为包括锚点 BS 14 a 和一个目标 BS 14 b ). 基站是一个或多个蜂窝或移动网络的一部分,包括操作网络所需的元件,例如移动交换中心(MSC)(未示出)。 如本领域技术人员所熟知的,移动网络也可以称为基站/MSC/互通功能(BMI)。 在操作中,当终端正在拨打和接收呼叫时,MSC 能够将呼叫路由到终端和从终端路由呼叫。 当终端参与通话时,MSC 还可以提供与陆线干线的连接。 另外,MSC可以控制与终端的消息转发,也可以控制终端与消息中心的消息转发。 [0033] 明尼苏达州 10 也可以耦合到数据网络。 例如,英国学士学位 14 可以耦合到数据网络,例如局域网(LAN)、城域网(MAN)和/或广域网(WAN)。 在一个典型的实施例中,BS耦合到网关,网关耦合到数据网络,例如互联网协议(IP)网络 16. 网关可以包括能够提供MN与直接或间接耦合到数据网络的其他节点之间的网络连接的多个不同实体中的任何一个。 应当理解,网关可以用多种不同方式中的任何一种来描述,例如归属代理(HA) 18 , 外国代理人 (FA) 20 (在下面显示和描述为包括锚点 FA 20 a 和一个目标 FA 20 b )、分组数据服务节点(PDSN)、接入路由器等。 在这方面,HA 可以包括家庭网络中的路由器 22 明尼苏达州的。 HA能够在MN不在家时通过隧道传输数据以传递给MN,并且可以维护MN的当前位置信息。 另一方面,FA 可以包含访问网络中的路由器 24 MN 的(如下所示和描述为包括锚访问网络 24 a 和目标访问网络 24 b ). FA在MN注册到拜访网络的同时向MN提供路由服务。 在操作中,FA 从 HA 解除数据隧道,并将数据传递给 MN。 然后,对于从注册到访问网络的MN发送的数据,FA可以作为默认路由器。 [0034] 其他节点耦合到 MN 10 通过IP网络 16 根据本发明的实施例,MN可以包括能够与MN通信的多个不同设备、系统等中的任何一个。 如本文所述,能够经由IP网络与MN通信的节点被称为对应节点(CN) 26 ,其中一个在图3中示出。其他CN可以包括例如个人计算机、服务器计算机等。 此外或备选地,例如,一个或多个CN可以包括其他MN,例如移动电话、便携式数字助理(PDA)、寻呼机、膝上型计算机等。 [0035] 虽然这里没有显示和描述每个可能网络的每个元素,但是应该理解,MN 10 可以耦合到许多不同网络中的任何一个或多个。 如本文所示和所述,锚访问网络 24 a 能够支持符合第三代 (3G) 移动通信协议 cdma2000 1X (TIA/EIA/IS-2000) 的通信,而目标访问网络 24 b 能够支持符合 3G 移动通信协议 cdma2000 1XEV-DO (TIA/EIA/IS-856) 的通信。 然而,应当理解,移动网络可以同样能够根据本发明的实施例操作,同时支持根据多个其他第一代(1G)中的任何一个或多个的通信, 第二代 (2G)、2.5G、3G 或其他移动通信协议。 例如,能够支持根据2G无线通信协议IS-136(TDMA)、GSM、IS-95(CDMA)等通信的一个或多个网络; 2.5G无线通信协议GPRS、增强型数据GSM环境(EDGE)等; 和/或 3G 无线通信协议 采用宽带码分多址 (WCDMA) 无线电接入技术的通用移动电话系统 (UMTS) 网络、cdma2000 1XEV-DV 等。 [0036] 现在参考图4,能够作为MN操作的实体的框图 10 , 哈 18 , F A 20 和/或中国 26 根据本发明的一个实施例示出。 尽管被示为单独的实体,但在一些实施例中,一个或多个实体可支持逻辑上分离但共同位于实体内的MN、HA、FA和/或CN中的一者或一者以上。 例如,单个实体可能支持逻辑上分离但位于同一位置的 HA 和 CN。 此外,例如,单个实体可以支持逻辑上分离但位于同一位置的 FA 和 CN。 [0037] 如图所示,能够作为 MN 运行的实体 10 , 哈 18 , F A 20 和/或中国 26 通常可以包括一个处理器 30 连接到内存 32. 存储器可以包括易失性和/或非易失性存储器,并且通常存储内容、数据等。 例如,存储器通常存储从实体发送和/或由实体接收的内容。 又例如,根据本发明的实施例,存储器通常存储软件应用程序、指令等以供处理器执行与实体的操作相关联的步骤。 [0038] 除了记忆 32 , 处理器 30 还可以连接到至少一个接口或其他装置,用于显示、传输和/或接收数据、内容等。 在这方面,接口可以包括至少一个通信接口 34 或用于传输和/或接收数据、内容等的其他装置,以及至少一个可以包括显示器的用户界面 36 和/或用户输入界面 38 . 用户输入接口又可以包括允许实体从用户接收数据的许多设备中的任何设备,例如小键盘、触摸显示器、操纵杆或其他输入设备。 [0039] 现在参考图5,其图示了一种类型的MN 10 这将受益于本发明的实施例。 然而,应当理解,所示出和下文描述的MN仅是将受益于本发明的一种类型的MN的说明,因此不应被视为限制本发明的范围。 虽然出于示例的目的示出并在下文中描述了MN的几个实施例,但是其他类型的MN,例如便携式数字助理(PDA)、寻呼机、膝上型计算机和其他类型的电子系统,可以容易地采用本发明。 [0040] 如图所示,除了一根天线 40 , 锰 10 包括一个发射器 42 , 一个接收器 44 , 和一个控制器 46 分别向发射器和接收器提供信号和从发射器和接收器接收信号。 这些信号包括符合适用蜂窝系统的空中接口标准的信令信息,以及用户语音和/或用户生成的数据。 就这一点而言,MN能够以一种或多种空中接口标准、通信协议、调制类型和接入类型进行操作。 如本文所解释的,MN能够根据cdma2000 1X和cdma2000 1XEV-DO通信协议进行操作。 然而,应当理解,MN可以更一般地能够根据多个1G、2G、2.5G、3G或其他通信协议中的任何一个来操作。 [0041] 据了解,控制器 46 包括实现 MN 的音频和逻辑功能所需的电路 10 . 例如,控制器可以包括数字信号处理器装置、微处理器装置以及各种模数转换器、数模转换器和其他支持电路。 MN的控制和信号处理功能根据各自的能力在这些设备之间进行分配。 控制器还可以包括一个内部语音编码器 (VC) 46 A,并且可能包括一个内部数据调制解调器(DM) 46 B.此外,控制器可以包括操作一个或多个软件程序的功能,这些软件程序可以存储在存储器中(如下所述)。 例如,控制器可能能够运行连接程序,例如传统的网络浏览器。 连接性程序然后可以允许 MN 发送和接收 Web 内容,例如根据 HTTP 和/或无线应用协议(WAP)。 [0042] 明尼苏达州 10 还包括一个用户界面,包括一个传统的耳机或扬声器 48 , 铃声 50 , 麦克风 52 , 一个显示器 54 和用户输入接口,所有这些都耦合到控制器 46 . 允许 MN 接收数据的用户输入接口可以包括任何允许 MN 接收数据的设备,例如键盘 56、触摸显示器(未显示)或其他输入设备。 在包括小键盘的实施例中,小键盘包括常规数字(0-9)和相关键(#、*),以及用于操作MN的其他键。 虽然未示出,但 MN 可以包括电池,例如振动电池组,用于为操作 MN 所需的各种电路供电,以及可选地提供机械振动作为可检测输出。 [0043] 明尼苏达州 10 还可以包括存储器,例如用户识别模块 (SIM) 58 、可移除用户身份模块(R-UIM)等,其通常存储与移动订户相关的信息元素。 除了 SIM 之外,MN 还可以包括其他可移动和/或固定存储器。 在这方面,MN 可以包括易失性存储器 60 ,例如易失性随机存取存储器(RAM),包括用于临时存储数据的高速缓存区域。 MN 还可以包括其他非易失性存储器 62 ,可以嵌入和/或可以移动。 非易失性存储器可以附加地或替代地包括EEPROM、闪存等。 存储器可以存储由 MN 用来实现 MN 功能的多条信息和数据中的任何一条。 例如,存储器可以存储标识符,例如国际移动设备识别码(IMEI)码、国际移动用户识别码(IMSI)码、移动台综合业务数字网络(MSISDN)码(移动电话号码)、会话发起协议(Session Initiation Protocol) (SIP)地址等,能够唯一识别移动站,例如移动网络 22 , 24 . [0044] 如背景部分中所解释的,网络,例如纯数据网络(例如,cdma2000 1X-EVDO),可能希望与 MN 建立通信 10 在另一个网络中运行,例如语音和数据网络(例如,cdma2000 1X)。 例如,cdma2000 1X-EVDO网络可能希望通过cdma2000 1X网络向当前支持语音通信的MN发送MMS消息或下载文件,例如电影或广告。 然而,在一个网络中运行的 MN 可能已停止监视其他网络的寻呼消息,这是 MN 当前未与之通信的网络通知 MN 它希望建立的传统技术 与 MN 的通信。 就这一点而言,如上所述,MN可能已经停止监视符合管理标准的寻呼消息以减少电池消耗。 [0045] 如下面更详细地解释的,本发明的实施例因此能够允许网络,诸如纯数据网络(例如,cdma2000 1X-EVDO),MN通过该网络 10 当前未通信以通知 MN 网络希望与 MN 建立通信,即使在 MN 正在通过另一个网络(例如语音和数据网络(例如,cdma2000 1X))主动通信并已停止监视的情况下 用于来自其他网络的寻呼消息。 因此,MN 可以结束与其先前一直与之通信的网络的通信,通常是在从 MN 或 MN 的用户接收到授权后,然后可以开始与已通知 MN 其期望的其他网络通信 与 MN 通信。 例如,MN 的用户可以在接收到仅数据网络希望与 锰。 [0046] 现在参考图6,其图示了交叉寻呼MN的方法的控制流程图 10 在当前的锚点 FA 中运行 20 a 在第一网络中,例如在 MN 和 CN 之间的通信会话期间 26 , MN 被新的目标 FA 通知 20 b 在目标 FA 希望与 MN 通信的不同网络中。 如本文所解释的,MN正在与锚点FA通信。 然而,应当理解,MN可以与锚点HA同等地通信 18, 在不脱离本发明的精神和范围的情况下。 此外,如下文所解释的,图6的方法适用于当MN在cdma2000 1X网络中操作时通过cdma2000 1X-EVDO网络交叉寻呼MN,或者将来可能通过信令的适当扩展反之亦然 由 cdma2000 1X-EVDO 网络提供。 就此而言,图6的方法将结合在cdma2000 1X-EVDO网络中从目标PDSN(即,目标FA)交叉寻呼MN来解释,同时MN处于与锚定PDSN的通信会话中( 即,在 cdma2000 1X 网络中锚定 FA)。 然而,应当理解,图6的方法可以同样适用于在MN在相同或不同类型的网络中操作时从多个其他网络中的任何网络交叉寻呼MN,而不背离 本发明的精神和范围。 [0047] 如图6所示,一种MN交叉寻呼的方法 10 根据本发明的一个实施例,包括一个 MN 10 最初与锚定网络中的锚定 PDSN 通信 20 a ,即 cdma 2000 1X 网络。 例如,MN 和锚点 PDSN 可能参与语音通信或 SMS 消息的交换。 在这个与锚定 PDSN 的通信会话期间,MN 可以停止监视来自其他网络的寻呼消息,否则这些寻呼消息会提醒 MN 另一个网络希望与 MN 通信。 MN 对寻呼消息的监视的停止通常由适用的标准管理并且可以出于各种原因来完成,包括例如为了节省电池消耗。 [0048] 在图6的方法中,目标网络 20 b ,例如 cdma2000 1X-EVDO 网络,可能希望与 MN 建立通信 10 , 但可以确定 MN 当前在锚网络中处于活动状态 20 a . 在这种情况下,目标网络向锚定网络发送目标页面。 该目标页面不仅包括页面通知,还有利地包括与目标网络相关的网络信息和服务可用性信息。 在其他信息中,网络信息例如可以包括目标网络的频率信息、开销信息和/或目标网络的业务信道分配。 锚定网络然后构造数据突发消息(DBM)以传送到MN以警告MN目标网络期望与MN通信。 尽管 MN 可能没有监视来自目标网络的寻呼消息,但是 MN 将接收并响应 DBM,从而即使在 MN 已经停止监视寻呼消息之后也允许 MN 被警告来自目标网络的寻呼通知。 [0049] DBM通常在预定字段中包括预定义代码以告知MN该DBM和其中包括的信息有效地构成来自另一个网络的页面通知。 尽管可以在不同领域使用各种代码,但是一个实施例的 DBM 的结构使得锚网络 20 a 将突发类型字段设置为 000111 以提醒 MN 10 另一个网络已发出寻呼通知。 除了在突发类型字段中包含预定义代码外,目标网络提供的其他信息 20 b ,例如网络信息和服务可用性信息也可以被封装并包含在DBM中。 当MN处于空闲状态或业务状态时,锚网络可以将DBM发送给MN。 如果处于空闲状态,则锚定网络通常在分配给 MN 的时隙中或在分配的时隙之后的时隙中传输 DBM。 或者,如果处于业务状态,则锚定网络仅以传统方式将DBM传输到MN。 [0050] 在接收到在预定字段中具有预定义代码的 DBM 后,例如突发类型字段设置为 000111,MN 10 可以确定是否希望从锚网络切换 20 a 到目标网络 20 b. 就此而言,如果MN处于空闲状态,则MN可以自动切换到目标网络,通常是在尽可能快的机会。 或者,如果MN处于业务状态,则MN可以被配置为在最早的实际机会自动从锚定网络切换到目标网络。 然而,典型地,处于业务状态的MN被配置为首先征求用户授权,例如经由呈现在MN的显示器上的图标建议用户另一网络期望与MN通信。 由于目标网络连同寻呼通知一起提供了各种服务和其他网络信息,因此 MN 可以但不一定向用户呈现至少一些这种附加信息,或者至少允许用户访问这种附加信息中的一些 根据请求提供信息,从而允许用户做出关于用户是否希望从锚定网络切换到目标网络的更明智的决定。 例如,用户可以在接收到另一网络期望与MN通信的通知时与朋友进行语音呼叫。 在查看与通知关联的附加信息时,在附加信息指示用户希望观看的新电影现在可供下载的情况下,用户可以选择终止语音呼叫并切换到另一个网络。 或者,在附加信息指示其他网络仅希望将广告下载到MN的情况下,用户可以选择继续语音呼叫并延迟到其他网络的任何切换。 [0051] 如果用户不希望切换到目标网络或者如果 MN 10 否则无法切换到目标网络,MN 向锚定网络发送预定义信号,例如移动站拒绝命令 20 a 反过来,它建议目标网络 20 b . 然而,如果 MN 要切换到目标网络,无论是由于 MN 处于空闲状态还是由于从处于业务状态的 MN 的用户接收到授权而自动切换,MN 发出 到目标网络的连接请求。 在 MN 已处于与锚定网络的业务状态的情况下,MN 必须首先结束当前业务信道分配,通常是在第一个实际机会时,然后发出连接请求。 为了进一步加速到目标网络的转换,MN可以放弃典型响应,例如通常为响应​​寻呼而发出的寻呼响应或通常为响应​​而发出的移动站确认命令(MS Ack) 到 DBM。 对于本领域的技术人员来说显而易见的是,目标网络先前提供的网络信息和服务可用性信息有助于MN构造连接请求。 例如,网络信息可以包括关于目标网络的频率信息,其帮助MN确定MN可以期望来自目标网络的服务的频率,从而避免MN必须基于基于目标网络来搜索来自目标网络的服务。 运营商提供的频率列表。 作为另一示例,网络信息还可以包括关于目标网络的开销信息。 由于MN在发送连接请求之前需要从目标网络获取最新的开销信息,因此MN不需要等待目标网络周期性发送开销信息,而是可以在获取到目标网络后立即发起连接请求,因为 MN已经收到DBM中的开销信息。 最后,网络信息可以包括目标网络中的业务分配,其允许MN直接切换到目标网络中的特定业务信道,甚至无需发送连接请求。 [0052] 收到连接请求后,目标网络 20 b 和锰 10 可以执行常规的流量和服务设置程序。 此后,MN经由目标网络与目标PDSN通信,例如交换MMS消息或其他纯数据服务。 [0053] 作为采用本发明实施例的交叉寻呼技术的结果,目标网络 20 b 可以向MN提供寻呼通知 10 为了从锚定网络发起切换 20 a 即使 MN 已停止监视来自其他网络的寻呼消息,也可以发送到目标网络。 此外,通过连同寻呼通知一起提供网络信息和/或业务信道分配,MN可以更快速和有效地连接到目标网络。 此外,通过连同寻呼通知一起提供服务可用性信息,处于与锚定网络的流量状态的MN的用户可以就用户是否期望切换到目标网络做出更有根据的决定。 本发明实施例的交叉寻呼技术还提供了无论MN处于空闲状态还是业务状态,目标网络和锚定网络都以相同的方式将来自目标网络的寻呼通知告知MN,从而简化了 网络侧的信令过程。 [0054] 如背景部分所述,cdma2000 1X 网络使用时隙操作模式,而 MN 10 处于空闲状态以节省 MN 电池的寿命。 也如上所述,cdma2000 1X 网络采用具有 CLASS 的 GPM — 0_DONE 字段设置为“1”以指示没有分配给相应时隙的 MN 的页面/消息,以便 MN 可以立即进入休眠状态,即,在时隙结束之前,并进一步节省电池电量。 为了确保 MN 收到指示目标网络的 DBM 20 b 希望与 MN 通信,DBM 必须在 GPM 与 CLASS 之前传输 — 0_DONE字段设置为1。如图7所示,MN 0 , 明尼苏达州 3 , 明尼苏达州 4 和锰 8 都分配到同一个插槽。 在发送 GPM 之前,如上所述传输 DBM,这表明目标网络希望与 MN 通信 4 . 收到 DBM 后,MN 4 切换到目标网络,而 MN 0 , 明尼苏达州 3 和锰 8 继续监控插槽。 GPM 与 CLASS — 然后发送设置为 1 的 0_DONE 字段,使得 MN 0 , 明尼苏达州 3 和锰 8 可以去睡觉了。 显而易见,所有 MN 都需要监视时隙,直到收到具有 CLASS 的 GPM — 0_DONE 字段设置为 1 会不利地消耗 DBM 未指向的 MN 的电池电量。 事实上,一些 MN 可能是非混合 MN,它们只能在语音和数据网络中进行通信,而不能在纯数据网络中进行通信。 尽管如此,所有 MN,包括不能在纯数据网络中通信的非混合 MN,都保持通电以接收 DBM,即使在这种情况下 DBM 与非混合 MN 无关。 [0055] 因此,本发明的一个实施例利用 GPM 中的预定义字段(例如 RESERVED 字段)来更改 MN 重新进入睡眠状态的过程,以便进一步节省电池电量,尤其是对于非混合 MN . 如图8所示,例如,其中MN 0 , 明尼苏达州 3 , 明尼苏达州 4 和锰 8 再次被分配到同一个时隙,考虑 MN 的情况 0 和锰 8 是非混合 MN 和 MN 3 和锰 4 是混合 MN。 一流的 GPM — 设置为 1 的 0_DONE 字段可能最初由锚网络传输 20 a. 与传统的 GPM 相比,预定义字段(例如 RESERVED 字段)被设置为预定值,例如 1。在任何情况下都无法访问目标网络的非混合 MN 不会检查 RESERVED 字段,并且 ,而是停止监视寻呼信道并返回休眠状态。 混合 MN 查看预定义字段以获取进一步说明。 在预定义字段被设置为预定值的情况下,例如,RESERVED字段被设置为1,混合MN继续监视DBM的寻呼信道。 或者,如果预定义字段未设置为预定值,例如,RESERVED字段设置为0,则混合MN也可以停止监视寻呼信道并返回休眠。 [0056] 在预定义字段设置为预定值的情况下,锚网络 20 a 接下来可以如上所述发送DBM。 如图8所示,DBM表示目标网络 20 b 希望与 MN 沟通 4 . 在 DBM 之后,MN 4 可以如上所述切换到目标网络,而MN 3 继续监视寻呼信道。 具有 CLASS 的传统 GPM — 可以发送设置为 1 的 0_DONE 字段和设置为不同于预定值的值的预定义字段,例如设置为 0 的 RESERVED 字段。 该 GPM 由尚未切换到另一个网络的所有混合 MN 接收,使得这些其他混合 MN(MN 3 在此示例中),也可以停止监视寻呼信道并返回休眠状态。 通过允许所有非混合 MN 返回休眠而不等待 DBM,根据该实施例进一步节省了非混合 MN 的电池电量,同时仍然允许一个或多个混合 MN 在另一个网络出现时得到通知 希望建立通信。 [0057] 根据本发明的一个方面,本发明的系统的全部或部分,例如MN的全部或部分 10 , 锚FA 20 a 目标 FA 20 b ,通常在计算机程序产品的控制下运行。 用于执行本发明实施例的方法的计算机程序产品包括计算机可读存储介质,例如非易失性存储介质,以及计算机可读程序代码部分,例如一系列计算机指令,体现在 计算机可读存储介质。 [0058] 在这方面,图9是根据本发明的方法、系统和计算机程序产品的框图。 应当理解,控制流程图的每个块或步骤以及控制流程图中的块的组合可以由计算机程序指令来实现。 这些计算机程序指令可以加载到计算机或其他可编程设备上以产生机器,使得在计算机或其他可编程设备上执行的指令创建用于实现控制流程图块或步骤中指定的功能的手段 (s). 这些计算机程序指令也可以存储在计算机可读存储器中,该存储器可以指示计算机或其他可编程装置以特定方式运行,使得存储在计算机可读存储器中的指令产生包括指令装置的制品 实现控制流程图块或步骤中指定的功能。 计算机程序指令也可以加载到计算机或其他可编程设备上,以导致在计算机或其他可编程设备上执行一系列操作步骤,以产生计算机实现的过程,使得在计算机或其他可编程设备上执行的指令 装置提供用于实现控制流程图块或步骤中指定的功能的步骤。 [0059]因此,框图的块或步骤支持用于执行指定功能的装置的组合、用于执行指定功能的步骤的组合以及用于执行指定功能的程序指令装置。 还应当理解,控制流程图的每个块或步骤,以及控制流程图中的块或步骤的组合,可以由执行指定功能或步骤的专用基于硬件的计算机系统来实现,或者 专用硬件和计算机指令。 [0060] 就此而言,在能够与至少一个混合移动终端和至少一个监视时隙的非混合移动终端通信的通信网络中,一种用于交叉寻呼至少一个混合移动终端中的所选一个的方法包括接收 操作中来自目标网络的寻呼指示 100 . 寻呼指示指示目标网络希望与至少一个混合移动终端中选择的一个进行通信。 运行中 110 ,将一系列消息中的第一消息发送到至少一个混合移动终端和至少一个非混合移动终端。 如果第一消息的预定义字段被设置为预定值,则第一消息指示至少一个非混合移动终端停止监视时隙。 运行中 120 ,可以将一系列消息中的第二消息发送到至少一个混合移动终端和至少一个非混合移动终端。 第二消息包括指示对至少一个混合移动终端中选择的一个的寻呼指示的数据突发消息。 运行中 130 ,可以发送该系列消息中的第三条消息。 第三消息指示至少一个混合移动终端中的任何其余混合移动终端停止监视时隙。 [0061] 本发明所属领域的技术人员受益于前述描述和相关附图中呈现的教导,将想到本发明的许多修改和其他实施例。 因此,应当理解,本发明不限于所公开的具体实施例,修改和其他实施例旨在包括在所附权利要求的范围内。 尽管本文使用了特定术语,但它们仅在一般和描述性意义上使用,并非出于限制目的。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: BRPI0608532A2(String), CN101164362A(String), EP1849328A1(String), IN6352DELNP2007A(String), JP2008532352A(String), KR1020080002760A(String), MX2007009823A(String), MYPI2006000588A0(String), SG134706A1(String), SG134706B(String), TW200642334A(String), US20060182069A1(String), US60652674P0(String), US7668136B2(String), VN16596A(String), WO2006085218A1(String), ZA200707790B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: BRPI0608532A2(String), CN101164362A(String), EP1849328A1(String), IN6352DELNP2007A(String), JP2008532352A(String), KR1020080002760A(String), MX2007009823A(String), MYPI2006000588A0(String), SG134706A1(String), SG134706B(String), TW200642334A(String), US20060182069A1(String), US60652674P0(String), US7668136B2(String), VN16596A(String), WO2006085218A1(String), ZA200707790B(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7668136B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), BRPI0608532A2(String), CN101164362A(String), EP1849328A1(String), IN6352DELNP2007A(String), JP2008532352A(String), KR1020080002760A(String), MX2007009823A(String), MYPI2006000588A0(String), SG134706A1(String), SG134706B(String), TW200642334A(String), US20060182069A1(String), US60652674P0(String), US7668136B2(String), VN16596A(String), WO2006085218A1(String), ZA200707790B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), BRPI0608532A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), CN101164362A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), EP1849328A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), IN6352DELNP2007A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:16.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), JP2008532352A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), KR1020080002760A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), MX2007009823A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), MYPI2006000588A0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), SG134706A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), SG134706B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), TW200642334A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), US20060182069A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), US60652674P0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), US7668136B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), VN16596A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), WO2006085218A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271651(Integer), ZA200707790B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7668136B2(String), US7668136B2(String), 1266854400(Integer), 271651(Integer), 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: NOKIA CORPORATION(String), NOKIA CORPORATION(String), 诺基亚公司(String), 诺基亚公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: NOKIA CORPORATION(String), 诺基亚公司(String), 255(String), 0(Integer), 1660814384(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185955(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20942(Integer), 1(Integer), 185955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: NOKIA CORPORATION(String), 诺基亚公司(String), 255(String), 0(Integer), 1660814384(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185955(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20942(Integer), 2(Integer), 185955(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:17.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 185955(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120072902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Self-Starting Method and Apparatus for Mobile Terminal, and Mobile Terminal(String), 一种移动终端的自启动方法、装置及移动终端(String), US20120072902A1(String), The present invention discloses a self-starting method and apparatus for a mobile terminal and a mobile terminal, which method comprises: when the mobile terminal is installed in a computer, installing the mobile terminal as a virtual compact disc (CD) of the computer; automatically running an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; and driving the mobile terminal using the driver. The present invention can achieve the self-starting of the mobile terminal, thus achieving the technical effect of facilitating use of user.(String), 本发明公开了一种移动终端自启动方法、装置及移动终端,方法包括:当移动终端安装在电脑中时,将移动终端安装为电脑的虚拟光盘; 自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 使用驱动程序驱动移动终端。 本发明能够实现移动终端的自启动,从而达到方便用户使用的技术效果。(String), US13/259777(String), 1274716800(Integer), US20120072902A1(String), 1332345600(Integer), 美国(String), 2(Integer), CN(String), 6(Integer), 10(Integer), US20030046447A1 | US20030099147A1 | US20040210897A1 | US20050015540A1 | US20090119445A1 | US20090193152A1 | US20100082843A1 | US20110060877A1 | US20130127749A1 | US8296757B2(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\342cf9605c55491ab0eea4071aa30e2f.png(String), 185956(Integer), 342cf9605c55491ab0eea4071aa30e2f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Self-Starting Method and Apparatus for Mobile Terminal, and Mobile Terminal(String), 一种移动终端的自启动方法、装置及移动终端(String), US20120072902A1(String), The present invention discloses a self-starting method and apparatus for a mobile terminal and a mobile terminal, which method comprises: when the mobile terminal is installed in a computer, installing the mobile terminal as a virtual compact disc (CD) of the computer; automatically running an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; and driving the mobile terminal using the driver. The present invention can achieve the self-starting of the mobile terminal, thus achieving the technical effect of facilitating use of user.(String), 本发明公开了一种移动终端自启动方法、装置及移动终端,方法包括:当移动终端安装在电脑中时,将移动终端安装为电脑的虚拟光盘; 自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 使用驱动程序驱动移动终端。 本发明能够实现移动终端的自启动,从而达到方便用户使用的技术效果。(String), US13/259777(String), 1274716800(Integer), US20120072902A1(String), 1332345600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 6(Integer), 10(Integer), US20030046447A1 | US20030099147A1 | US20040210897A1 | US20050015540A1 | US20090119445A1 | US20090193152A1 | US20100082843A1 | US20110060877A1 | US20130127749A1 | US8296757B2(String), \20230420\342cf9605c55491ab0eea4071aa30e2f.png(String), 11(Integer), 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 1. A self-starting method for a mobile terminal, comprising:installing the mobile terminal as a virtual CD of a computer when the mobile terminal is installed in the computer;automatically running an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; anddriving the mobile terminal using the driver.(String), 1.根据权利要求9所述的移动终端,其中开关模块为通用串行总线单刀双掷开关。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 2. The self-starting method according to claim 1, wherein installing the mobile terminal as a virtual CD of the computer comprises:the mobile terminal reporting itself as the virtual CD to the computer; andthe computer identifying and installing the mobile terminal as the virtual CD.(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 3. The self-starting method according to claim 1, wherein after the installation of the driver and before driving the mobile terminal using the driver, the method further comprises:sending a switch command to the mobile terminal; andthe mobile terminal switching a data path connected to the computer from a first path to a second path in response to the switch command and triggering the computer to re-enumerate a device,wherein, the first path is a default path and is connected to a driver installation module of the mobile terminal, and the second path is connected to a main module of the mobile terminal.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 4. A self-starting apparatus for a mobile terminal, comprising:a driver installation module, configured to, when the mobile terminal is installed in a computer, install the mobile terminal as a virtual CD of the computer and automatically run an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; anda driving module, configured to drive the mobile terminal using the driver.(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 5. The self-starting apparatus according to claim 4, wherein the apparatus further comprises:a switch command sending module, configured to send a switch command to a switching module according to the driver installation result of the driver installation module; andthe switching module, configured to switch a data path connecting the mobile terminal to the computer from a first path to a second path in response to the switch command and trigger the computer to re-enumerate a device,wherein, the first path is a default path and is connected to an automatic installation program of the mobile terminal, and the second path is connected to a main module of the mobile terminal.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 6. The self-starting apparatus according to claim 5, wherein the driver installation module and the switching module are located in the mobile terminal, and the switch command sending module and the driving module are installed in the computer while installing the driver.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 7. The self-starting apparatus according to claim 5, wherein the switching module is a universal serial bus single-pole double-throw switch.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 8. A mobile terminal comprises a self-starting apparatus, wherein the self-starting apparatus comprises:a driver installation module, configured to install the mobile terminal as a virtual CD of a computer when the mobile terminal is installed in the computer, and automatically run an automatic installation program in the virtual CD so as to install a driver of the mobile terminal in the computer; anda driving module, configured to drive the mobile terminal using the driver.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 9. The mobile terminal according to claim 8, wherein the self-starting apparatus further comprises:a switch command sending module, configured to send a switch command to a switching module according to the driver installation result of the driver installation module; andthe switching module, configured to switch a data path connecting the mobile terminal to the computer from a first path to a second path in response to the switch command and trigger the computer to re-enumerate a device,wherein the first path is a default path and is connected to an automatic installation program of the mobile terminal, and the second path is connected to a main module of the mobile terminal.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 10. The mobile terminal according to claim 9, wherein the driver installation module and the switching module are located in the mobile terminal, and the switch command sending module and the driving module are installed in the computer while installing the driver.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185956(Integer), 11. The mobile terminal according to claim 9, wherein the switching module is a universal serial bus single-pole double-throw switch.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185956(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, and in particular to a self-starting method and apparatus for a mobile terminal as well as a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the popularization of mobile terminal devices, there is an increasing demand for interconnecting a mobile terminal to a computer. Especially those mobile communication card type devices with various standards must cooperate with the computers to finish various functions. [0003]Currently, the self-starting method generally used when a mobile terminal is connected to a computer is: a user installs the driver software of a mobile terminal adapted to the type of the mobile terminal in a computer, and the object of starting the mobile terminal by using the driver software to drive the mobile terminal is achieved when the mobile terminal of this type is connected to the computer. [0004]During the implementation of the present invention, the inventors find that, when a mobile terminal is connected to a computer in relevant art, the self-starting method requires a user to manually install the driver software of the mobile terminal of its type in the computer, which causes the operation to be inconvenient. SUMMARY OF THE INVENTION [0005]An aspect of the present invention is to provide a self-starting method and apparatus for a mobile terminal as well as a mobile terminal, which is capable of solving the technical problem in relevant art that it needs a user to manually install the driver of a mobile terminal in a computer and thus causes the operation to be inconvenient. [0006]A self-starting method for a mobile terminal is provided according to one aspect of the present invention, which method comprises: when a mobile terminal is installed in a computer, installing the mobile terminal as a virtual compact disc (CD) of the computer; automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and driving the mobile terminal using the driver. [0007]A self-starting apparatus for a mobile terminal is further provided according to another aspect of the present invention, which apparatus comprises: a driver installation module for, when a mobile terminal is installed in a computer, installing the mobile terminal as a virtual CD of the computer and automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and a driving module for driving the mobile terminal using the driver. [0008]A mobile terminal comprising a self-starting apparatus is further provided according to still another aspect of the present invention, which self-starting apparatus comprises: a driver installation module for, when a mobile terminal is installed in a computer, installing the mobile terminal as a virtual CD of the computer and automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and a driving module for driving the mobile terminal using the driver. [0009]By virtue of at least one of the above technical solutions of the present invention, the object of self-starting of the mobile terminal is achieved by installing the mobile terminal as the virtual CD of the computer when the mobile terminal is connected to the computer so as to automatically running an automatic installation program in the mobile terminal, thus achieving the technical effect of facilitating the user. BRIEF DESCRIPTION OF THE DRAWINGS [0010]The drawings, provided for further understanding of the present invention and forming a part of the specification, are used to explain the present invention together with embodiments of the present invention rather than to limit the present invention, wherein [0011]FIG. 1 is a flow chart of a self-starting method for a mobile terminal according to a first embodiment of the present invention; [0012]FIG. 2 is a block diagram of a self-starting apparatus for a mobile terminal according to a second embodiment of the present invention; [0013]FIG. 3 is a schematic diagram of the connection of a switching module of a self-starting apparatus for a mobile terminal according to the second embodiment of the present invention; [0014]FIG. 4 is a block diagram of a mobile terminal according to a third embodiment of the present invention; [0015]FIG. 5 is a flowchart of a self-starting method for a mobile terminal according to a fourth embodiment of the present invention; and [0016]FIG. 6 is a block diagram of a self-starting apparatus for a mobile terminal according to the second embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS [0017]A detailed description of the preferred embodiments of the present invention is provided hereinafter with reference to attached drawings. It should be understood that the preferred embodiments described herein are used for illustrating and explaining the present invention only and shall not be used for limiting the protection scope of the present invention. [0018]For the purpose of illustration, certain details are described in the description below, in order to offer a better understanding of the present invention. However, it is apparent, that the present invention can be achieved even without these certain details, and moreover, the following embodiments and the technical features of these embodiments can be combined if there is no conflict, i.e. without departing from the spirit and scope interpreted by the appended claims. First Embodiment [0019]FIG. 1 is a flow chart of a self-starting method for a mobile terminal according to a first embodiment of the present invention. As shown in FIG. 1, when a mobile terminal is connected to a computer, the self-starting method for the mobile terminal according to the first embodiment of the present invention comprises the following steps: [0020]Step S102: installing a mobile terminal as a virtual CD of a computer when the mobile terminal is installed in (also referred to as “connected to”) the computer; [0021]Step S104: automatically running an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and [0022]Step S106: driving the mobile terminal using the driver. [0023]The self-starting method for a mobile terminal according to the first embodiment of the present invention achieves the self-starting object of the mobile terminal by installing the mobile terminal as the virtual CD of the computer when the mobile terminal is connected to the computer so as to automatically run an automatic installation program in the mobile terminal, thus avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. [0024]Preferably, installing the mobile terminal as a virtual CD of the computer comprises: the mobile terminal reporting itself as the virtual CD to the computer; and the computer identifying and installing the mobile terminal as the virtual CD. Thus, it can make the operation of the user more convenient. Optionally, the user can manually set the mobile terminal as the virtual CD to enable the computer to identify and install the mobile terminal as the virtual CD. [0025]Preferably, after the installation of the driver and before driving the mobile terminal using the driver, it further comprises: sending a switch command to the mobile terminal; and the mobile terminal switching a data path connected to the computer from a first path to a second path in response to the switch command and triggering the computer to re-enumerate a device, wherein the first path is a default path and is connected to a driver installation module of the mobile terminal, and the second path is connected to a main module of the mobile terminal. [0026]While installing the driver, a switch command sending module is also installed in the computer so as to send to the mobile terminal a switch command of switching between the first path and the second path after the installation of the driver has been finished; and after the installation of the driver has been finished, the computer re-enumerates the mobile terminal as a mobile terminal instead of a virtual CD by the switch between the first path and the second path, thus achieving normal data communication. [0027]The self-starting method for a mobile terminal according to this embodiment enables the mobile terminal to automatically switch to the main module after the installation of the driver has been finished by switching from the first path to the second path after the installation of the driver has been finished, thus achieving the self-starting of the mobile terminal. Since the self-starting method for a mobile terminal according to the embodiments of the present invention achieves the self-starting of a mobile terminal by switching from a first path which is connected to the driver installation module to a second path which is connected to the main module of the mobile terminal after the installation of the driver has been finished, the achievement of the self-starting function of the self-starting method for a mobile terminal according to the embodiments of the present invention is irrelevant to whether the main module of the mobile terminal supports the function of reporting it as a virtual CD, and therefore it solves the technical problem in relevant art that the self-starting function of a mobile terminal depends on the support of the main module for self-starting function, thus reducing the dependence of the self-starting function upon the main module of the mobile terminal. [0028]Additionally, if it is not the first time that the mobile terminal is connected to the computer, i.e. the driver of this mobile terminal or a mobile terminal of this type is already installed in the computer, and since the first path is a default path, the command sending module directly sends to the mobile terminal a switch command of switching between the first path and the second path so as to enable the computer to re-enumerate the mobile terminal as a mobile terminal instead of a virtual CD, thus achieving normal data communication. [0029]Preferably, sending a switch command to the mobile terminal comprises: enabling a command-sending flag; and sending a switch command according to the command-sending flag. After the command sending module has been installed, it actively detects the command-sending flag which marks whether the installation of the driver is finished or not, if the command-sending flag is in the enabled state, then it indicates that the installation of the driver is finished and the command sending module sends a switch command to the mobile terminal, and if the command-sending flag is not enabled, then it indicates that the installation of the driver is not yet finished and the command sending module continues the detection. Thus, the self-starting function of the mobile terminal is achieved. [0030]The self-starting method for a mobile terminal according to the first embodiment of the present invention achieves the self-starting object of a mobile terminal by installing the mobile terminal as a virtual CD of a computer when the mobile terminal is connected to the computer so as to automatically run an automatic installation program in the mobile terminal and to install the driver of the mobile terminal in the computer, thereby avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. Second Embodiment [0031]FIG. 2 is a block diagram of a self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention. As shown in FIG. 2, the self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention comprises: a driver installation module 202, configured to install the mobile terminal as a virtual CD of a computer when installing the mobile terminal in the computer, and automatically run an automatic installation program in the virtual CD so as to install the driver of the mobile terminal in the computer; and a driving module 204, configured to drive the mobile terminal using the driver. [0032]The self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention achieves the self-starting object of the mobile terminal by using a driver installation module 202 to install the mobile terminal as the virtual CD of a computer when the mobile terminal is connected to the computer and automatically running the automatic installation program in the mobile terminal, thereby avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. [0033]In this embodiment, the driver installation module can be a mass storage device with self-starting function, or can be other devices with self-starting function. [0034]Preferably, as shown in FIG. 6, the self-starting apparatus 200 further comprises: a switch command sending module 206, configured to send a switch command according to the driver installation result of the driver installation module 202; and a switching module 208, configured to switch a data path connected to the computer from a first path to a second path in response to the switch command and trigger the computer to re-enumerate a device, wherein the first path is a default path and is connected to the driver installation module of the mobile terminal, while the second path is connected to a main module of the mobile terminal. [0035]The self-starting apparatus 200 for a mobile terminal according to this embodiment enables the mobile terminal to automatically switch to the main module by using the switching module 208 to switch from the first path to the second path after the installation of the driver has been finished, thus achieving the self-starting of the mobile terminal. Since the self-starting apparatus 200 of this embodiment reports the mobile terminal as a virtual CD and automatically runs the driver installation program by the driver installation module 202 to which the first path is connected and then switches the data path to the second path which is connected to the main module of the mobile terminal only after the installation of the driver has been finished, the achievement of the self-starting function of the self-starting apparatus 200 of this embodiment is irrelevant to whether the main module of the mobile terminal supports the function of reporting it as a virtual CD, and therefore it solves the technical problem in relevant art that the self-starting function of a mobile terminal depends on the support of the main module for self-starting function, thus reducing the dependence of the self-starting function upon the main module of the mobile terminal. [0036]While installing the driver, a switch command sending module 206 is also installed in the computer to send a switch command of switching between the first path and the second path to the mobile terminal after the installation of the driver has been finished; and the computer re-enumerates the mobile terminal as a mobile terminal instead of a virtual CD after the installation of the driver has been finished by switching between the first path and the second path, thus achieving normal data communication. [0037]Additionally, if it is not the first time that the mobile terminal is connected to the computer, i.e. the driver of the mobile terminal or a mobile terminal of this type is already installed in the computer, since the first path is a default path, the switch command sending module 206 directly sends a switch command of switching between the first path and the second path to the mobile terminal so as to enable the computer to re-enumerate the mobile terminal as a mobile terminal instead of a virtual CD, thus achieving normal data communication. [0038]Preferably, the switch command sending module 206 includes: a command-sending flag enabling unit, configured to enable a command-sending flag; and a command sending unit, configured to send a switch command to the switching module 208 according to the command-sending flag. The command sending flag enabling unit enables the command-sending flag after the installation of the driver has been finished, and after the installation of the switch command sending module 206 has been finished, the command sending module actively detects the command-sending flag, if the command-sending flag is enabled, then it indicates that the installation of the driver is finished and the command sending module sends a switch command to the mobile terminal, and if the command sending flag is not enabled, then it indicates that the installation of the driver is not yet finished and the command sending module continues the detection. Thus, the self-starting function of the mobile terminal is achieved. [0039]Preferably, the driver installation module 202 and the switching module 208 are located in the mobile terminal, while the switch command sending module 206 and the driving module 204 are installed in the computer while installing the driver. They cooperate with each other to finish the self-starting of the mobile terminal. [0040]Preferably, the switching module 208 is a USB single-pole double-throw switch, as shown in FIG. 3. The single-pole double-throw switch can decide whether to switch the data path to the first path which is connected to the driver installation module 202 or to the second path which is connected to the main module of the mobile terminal by judging the level of its selected pin. Thus, the switch between data paths can be achieved, thus achieving normal data communication. [0041]The self-starting apparatus 200 for a mobile terminal according to the second embodiment of the present invention uses the driver installation module 202 to install a mobile terminal as a virtual CD of a computer when the mobile terminal is connected to the computer and automatically runs an automatic installation program in the mobile terminal so as to install the driver in the computer and then achieves the self-starting of the mobile terminal by switching the data path from the driver installation module 202 to the main module, thus avoiding the inconvenience caused requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. Third Embodiment [0042]FIG. 4 is a block diagram of a mobile terminal according to a third embodiment of the present invention. As shown in FIG. 4, a mobile terminal 400 according to the third embodiment of the present invention comprises a self-starting apparatus 200 for a mobile terminal and a main module 404 shown in FIG. 2 or FIG. 6. [0043]Preferably, the mobile terminal is a WiMax terminal. As to the WiMax terminal, since its built-in WiMax main chip does not support to report it as a virtual CD, the self-starting function of the terminal is finished with the assistance of arranging a self-starting apparatus according to the embodiments of the present invention in this mobile terminal. [0044]The mobile terminal according to this embodiment enables the mobile terminal to automatically switch to the main module 404 after the installation of the driver has been finished by using the switching module 208 to switch from the first path to the second path after the installation of the driver has been finished, thus achieving the self-starting of the mobile terminal. Since the mobile terminal according to the embodiment of the present invention reports a mobile terminal as a virtual CD by the driver installation module 202 connected to the first path, automatically runs the driver installation program, and switches the data path to the second path which is connected to the main module 404 of the mobile terminal after the installation of the driver has been finished, the achievement of the self-starting function of the mobile terminal according to the embodiment of the present invention is irrelevant to whether the main module 404 of the mobile terminal supports the function of reporting it as a virtual CD, and therefore it solves the technical problem in relevant art that the self-starting function of a mobile terminal depends on the support of the main module 404 for self-starting function, thus reducing the dependence of the self-starting function upon the main module 404 of the mobile terminal. [0045]The mobile terminal according to the third embodiment of the present invention performs self-starting using a self-starting apparatus, thus avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. Fourth Embodiment [0046]FIG. 5 is a flowchart of a self-starting method for a mobile terminal according to a fourth embodiment of the present invention. As shown in FIG. 5, the self-starting method for a mobile terminal when it is connected to a computer according to the fourth embodiment of the present invention comprises the following steps, [0047]Step S502: when a mobile terminal is installed in a computer, it is judged whether it is the first time that the mobile terminal is connected to the computer, if it is, then step S504 is performed, otherwise step S508 is performed. [0048]Step S504: the driver installation module reports the mobile terminal as a CDROM (Compact Disk Read Only Memory), and the system automatically performs the installation of an installation package according to autorun.inf and enables a command-sending flag by using a command-sending flag enabling unit installed simultaneously during the installation of the driver. [0049]Step S506: a command sending module which has already been installed at the computer side detects the enabling flag, if it is enabled, then proceed to step S508, and if it is not enabled, then continue the detection. [0050]Step S508: the command sending module sends a switch command. [0051]Step S510: after having received the switch command, the driver installation module at the mobile terminal side resolves the command and sends a switch signal to a USB-switch according to the resolution result. [0052]Step S512: after having received the switch signal, the USB-switch performs the switch of USB data paths and switches the data path from the driver installation module to the main module of the mobile terminal. [0053]Step S514: the computer removes the command sending module installed therein, and re-enumerates device information to obtain the report of the main module of the mobile terminal so as to identify it as a mobile terminal. [0054]The self-starting method for a mobile terminal according to the fourth embodiment of the present invention uses a driver installation module to install a mobile terminal as a virtual CD of a computer and automatically runs the automatic installation program in the mobile terminal so as to install the mobile terminal in the computer and then achieves the self-starting of the mobile terminal by switching the data path from the driver installation module to the main module, thus avoiding the inconvenience caused by requiring a user to install the driver manually when the mobile terminal is connected to the computer, and achieving the technical effect of facilitating the user. [0055]As described above, the technical solutions of the present invention can achieve the self-starting of a mobile terminal by using a driver installation module to install the mobile terminal in a computer when it is the first time that the mobile terminal is connected to the computer, thus achieving the technical effect of facilitating the user. [0056]Above description is only to illustrate the preferred embodiments but not to limit the present invention. Any amendments, equivalent substitutions, improvements and etc. within the spirit and principle of the present invention are all included in the scope of the present invention.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的自启动方法、装置及移动终端。 发明背景 [0002] 随着移动终端设备的普及,移动终端与计算机互联的需求越来越大。 尤其是各种制式的移动通讯卡类设备,必须配合电脑才能完成各种功能。 [0003] 目前,移动终端与电脑连接时一般采用的自启动方法是:用户在电脑中安装适配移动终端类型的移动终端驱动软件,启动移动终端的对象 该类移动终端与电脑连接时,通过驱动软件驱动移动终端即可实现。 [0004] 发明人在实施本发明的过程中发现,相关技术中移动终端与计算机连接时,自启动方法需要用户在计算机中手动安装该类型移动终端的驱动软件。 ,导致操作不便。 发明内容 [0005] 本发明的一方面在于提供一种移动终端的自启动方法、装置及移动终端,能够解决相关技术中需要用户手动安装驱动程序的技术问题。 移动终端在电脑上,造成操作不便。 [0006] 根据本发明的一个方面,提供了一种移动终端的自启动方法,该方法包括: 当移动终端安装在计算机中时,将移动终端安装为计算机的虚拟光盘(CD); 自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 使用驱动程序驱动移动终端。 [0007] 根据本发明的另一方面,还提供了一种移动终端的自启动装置,该装置包括: 驱动安装模块,用于在计算机安装移动终端时,将移动终端安装为计算机的虚拟光盘。 电脑自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 以及驱动模块,用于使用驱动程序驱动移动终端。 [0008] 根据本发明的再一方面,还提供了一种包括自启动装置的移动终端,该自启动装置包括: 驱动安装模块,用于在计算机中安装移动终端时,将移动终端安装为 计算机的虚拟光盘,自动运行虚拟光盘中的自动安装程序,在计算机中安装移动终端的驱动程序; 以及驱动模块,用于使用驱动程序驱动移动终端。 [0009] 通过本发明的上述至少一种技术方案,实现了移动终端在连接电脑时将移动终端安装为电脑的虚拟光盘,从而实现了移动终端自启动的目的。 在移动终端中自动运行自动安装程序,达到方便用户的技术效果。 附图的简要说明 [0010] 附图为使本发明进一步理解而构成说明书的一部分,与本发明的实施例一起用于解释本发明,并不用于限制本发明,其中 [0011] 图1为本发明第一实施例的移动终端自启动方法的流程图; [0012] 图2为本发明第二实施例的移动终端自启动装置框图; [0013]图3为本发明实施例二的移动终端自启动装置的切换模块的连接示意图; [0014] 图4是本发明第三实施例的移动终端的框图; [0015] 图5为本发明第四实施例的移动终端自启动方法的流程图; 和 [0016] 图6为本发明第二实施例的移动终端自启动装置的框图。 具体实施方式 [0017] 下面结合附图对本发明的优选实施例进行详细说明。 应当理解,此处所描述的优选实施例仅用于说明和解释本发明,并不用于限定本发明的保护范围。 [0018] 为了说明的目的,在下面的描述中描述了一些细节,以便提供对本发明更好的理解。 然而,显而易见的是,即使没有这些特定细节也可以实现本发明,而且,在不冲突的情况下,即在不脱离所解释的精神和范围的情况下,可以组合以下实施例和这些实施例的技术特征 通过所附权利要求。 第一实施例 [0019] 图1为本发明第一实施例的移动终端自启动方法的流程图。 如图1所示,当移动终端与计算机连接时,本发明第一实施例的移动终端自启动方法包括以下步骤: [0020] 脚步 102 :当移动终端安装在(也称为“连接到”)计算机中时,将移动终端安装为计算机的虚拟CD; [0021] 脚步 104 :自动运行虚拟光盘中的自动安装程序,在电脑中安装移动终端的驱动程序; 和 [0022] 脚步 106 :使用驱动驱动移动端。 [0023] 本发明第一实施例的移动终端自启动方法,通过在移动终端与计算机连接时,将移动终端安装为计算机的虚拟光盘,实现了移动终端自启动的目的,因此 在移动终端中自动运行自动安装程序,避免了移动终端与电脑连接时需要用户手动安装驱动带来的不便,达到了方便用户的技术效果。 [0024] 优选地,将移动终端安装为计算机的虚拟光盘包括: 移动终端向计算机报告自身为虚拟光盘; 计算机将移动终端识别为虚拟光盘安装。 从而可以使用户的操作更加方便。 可选的,用户可以手动将移动终端设置为虚拟光盘,使计算机能够识别并安装移动终端为虚拟光盘。 [0025] 优选地,在安装驱动之后,在使用驱动驱动移动终端之前,还包括: 向移动终端发送切换命令; 移动终端响应于切换命令将与计算机连接的数据路径从第一路径切换到第二路径,并触发计算机重新枚举设备,其中,第一路径为默认路径,连接到 移动终端驱动安装模块,第二路径连接移动终端主模块。 [0026]在安装驱动的同时,计算机中还安装有切换命令发送模块,用于在驱动安装完成后向移动终端发送切换第一路径和第二路径的切换命令; 驱动安装完成后,计算机通过第一路径和第二路径的切换,将移动终端重新枚举为移动终端,而不是虚拟光盘,从而实现正常的数据通信。 [0027] 本实施例的移动终端自启动方法通过在驱动安装完成后从第一路径切换到第二路径,使得移动终端在驱动安装完成后自动切换到主模块。 完成,从而实现移动终端的自启动。 由于本发明实施例的移动终端自启动方法是通过从连接驱动安装模块的第一路径切换到连接驱动安装模块的第二路径实现移动终端自启动的。 驱动安装完成后的移动终端主模块,本发明实施例的移动终端自启动方法的自启动功能的实现与主模块是否安装无关。 移动终端支持虚拟光盘上报功能,解决了相关技术中移动终端的自启动功能依赖于主模块对自启动功能的支持的技术问题,减少了 自启动功能对移动终端主模块的依赖。 [0028] 另外,如果移动终端不是第一次连接电脑,即电脑中已经安装了该移动终端或该类型移动终端的驱动,由于第一路径为默认路径, 命令发送模块直接向移动终端发送切换第一路径和第二路径的切换命令,使得计算机将移动终端重新枚举为移动终端而不是虚拟CD,从而实现正常数据 沟通。 [0029] 优选地,向移动终端发送切换命令包括:​​ 使能命令发送标志; 根据命令发送标志发送切换命令。 命令发送模块安装完成后,会主动检测标记驱动安装是否完成的命令发送标志,如果命令发送标志为使能状态,则表示驱动安装完成。 驱动完成,指令发送模块向移动终端发送切换指令,若指令发送标志位未开启,则表示驱动尚未安装完成,指令发送模块继续检测。 从而实现了移动终端的自启动功能。 [0030] 本发明第一实施例的移动终端自启动方法通过在移动终端与计算机连接时将移动终端安装为计算机的虚拟光盘来实现移动终端自启动的目的,因此 在移动终端中自动运行自动安装程序,在电脑中安装移动终端的驱动程序,避免了移动终端与电脑连接时需要用户手动安装驱动程序带来的不便, 达到方便用户的技术效果。 第二实施例 [0031] 图2是自启动装置的框图 200 用于根据本发明第二实施例的移动终端。 如图2所示,自启动装置 200 本发明实施例二提供的一种移动终端,包括:驱动安装模块 202、用于在电脑中安装移动终端时将移动终端作为电脑的虚拟光盘安装,并自动运行虚拟光盘中的自动安装程序,以在电脑中安装移动终端的驱动程序; 和一个驱动模块 204 ,配置为使用驱动程序驱动移动终端。 [0032] 自启动装置 200 本发明实施例二的移动终端通过驱动安装模块实现移动终端自启动的目的 202 当移动终端与电脑连接时,将移动终端作为电脑的虚拟光盘进行安装,自动运行移动终端中的自动安装程序,避免了移动终端需要用户手动安装驱动带来的不便。 终端与电脑连接,达到方便用户使用的技术效果。 [0033] 在本实施例中,驱动安装模块可以是具有自启动功能的大容量存储设备,也可以是其他具有自启动功能的设备。 [0034] 优选地,如图6所示,自启动装置 200 还包括:开关命令发送模块 206 ,配置为根据驱动安装模块的驱动安装结果发送切换命令 202 ; 和一个开关模块 208 ,用于响应于切换命令将连接计算机的数据路径从第一路径切换到第二路径,并触发计算机重新枚举设备,其中,第一路径为默认路径,连接驱动程序 移动终端的安装模块,而第二路径连接移动终端的主模块。 [0035] 自启动装置 200 本实施例的移动终端通过切换模块实现移动终端自动切换到主模块 208 驱动安装完成后从第一路径切换到第二路径,从而实现移动终端的自启动。 自启动装置 200 本实施例将移动终端上报为虚拟光盘,驱动安装模块自动运行驱动安装程序 202 连接第一条路径,然后在驱动安装完成后,将数据路径切换到连接移动终端主模块的第二条路径,实现自身的自启动功能 -启动装置 200 本实施例与移动终端主模块是否支持虚拟光盘上报功能无关,解决了相关技术中移动终端自启动功能依赖于上报虚拟光盘功能的技术问题。 自启动功能的主模块,减少了自启动功能对移动终端主模块的依赖。 [0036] 安装驱动时,开关命令发送模块 206 还安装在电脑中,用于在驱动安装完成后向移动终端发送切换第一路径和第二路径的切换命令; 计算机通过在第一路径和第二路径之间切换,驱动安装完成后,将移动终端重新枚举为移动终端,而不是虚拟光盘,从而实现正常的数据通信。 [0037] 另外,如果移动终端不是第一次连接电脑,即电脑中已经安装了移动终端的驱动程序或此类移动终端,由于第一条路径为默认路径,则 开关命令发送模块 206 直接向移动终端发送切换第一路径和第二路径的切换命令,使得计算机将移动终端重新枚举为移动终端,而不是虚拟CD,从而实现正常的数据通信。 [0038] 优选地,所述开关命令发送模块 206包括: 命令发送标志使能单元,用于使能命令发送标志; 命令发送单元,用于向切换模块发送切换命令 208 根据命令发送标志。 命令发送标志使能单元在驱动安装完成后,开关命令发送模块安装完成后,使能命令发送标志。 206 完成后,命令发送模块主动检测命令发送标志位,若命令发送标志位开启,则表示驱动安装完成,命令发送模块向移动终端发送切换命令, 如果命令发送标志位没有开启,则说明驱动尚未安装完成,命令发送模块继续检测。 从而实现了移动终端的自启动功能。 [0039] 优选的,驱动安装模块 202 和开关模块 208 位于移动端,而开关命令发送模块 206 和驱动模块 204 在安装驱动程序的同时安装在计算机中。 它们相互配合完成移动终端的自启动。 [0040] 优选地,切换模块 208 是一个USB单刀双掷开关,如图3所示。单刀双掷开关可以决定是否将数据路径切换到连接驱动安装模块的第一条路径 202 或者通过判断其选择引脚的电平,连接到移动终端主模块的第二条路径。 从而实现数据路径之间的切换,从而实现正常的数据通信。 [0041] 自启动装置 200 本发明第二实施例的移动终端使用驱动安装模块 202 将移动终端作为电脑的虚拟光盘进行安装,当移动终端与电脑连接时,自动运行移动终端中的自动安装程序,安装电脑中的驱动程序,实现自启动。 移动端通过驱动安装模块切换数据路径 202 避免了移动终端与电脑连接时需要用户手动安装驱动带来的不便,达到了方便用户的技术效果。 第三实施例 [0042] 图4是根据本发明第三实施例的移动终端的框图。 如图4所示,移动终端 400 根据本发明的第三实施例包括自启动装置 200 用于移动终端和主模块 404 如图2或图6所示。 [0043] 优选地,移动终端为WiMax终端。 对于WiMax终端,由于其内置的WiMax主芯片不支持上报为虚拟光盘,根据本发明实施例设置自启动装置辅助完成终端的自启动功能。 本发明在该移动终端中。 [0044] 本实施例的移动终端能够使移动终端自动切换到主模块 404 使用交换模块完成驱动安装后 208 驱动安装完成后从第一路径切换到第二路径,从而实现移动终端的自启动。 由于本发明实施例的移动终端通过驱动安装模块将移动终端上报为虚拟光盘 202 连接到第一条路径,自动运行驱动安装程序,并将数据路径切换到连接到主模块的第二条路径 404 移动终端在驱动安装完成后,本发明实施例的移动终端自启动功能的实现与主模块是否完成无关。 404移动终端支持虚拟光盘上报功能,解决了相关技术中移动终端自启动功能依赖于主模块支持的技术问题 404 用于自启动功能,从而减少自启动功能对主模块的依赖 404 的移动终端。 [0045] 本发明实施例三的移动终端通过自启动装置进行自启动,避免了移动终端连接电脑时需要用户手动安装驱动带来的不便,实现了 方便用户的技术效果。 第四实施例 [0046] 图5为本发明第四实施例的移动终端自启动方法的流程图。 如图5所示,本发明第四实施例的移动终端连接电脑自启动的方法包括以下步骤, [0047] 脚步 502 :当移动终端安装在电脑上时,判断移动终端是否是第一次连接电脑,如果是,则步骤S 504 执行,否则执行步骤S 508 被执行。 [0048] 脚步 504 :驱动安装模块将移动端上报为CDROM(Compact Disk Read Only Memory),系统根据autorun.inf自动进行安装包的安装,并通过命令发送标志启用命令发送标志 在安装驱动程序的过程中同时安装启用单元。 [0049] 脚步 506 :计算机端已经安装的命令发送模块检测启用标志,如果启用,则进行步骤S 508 ,如果没有启用,则继续检测。 [0050] 脚步 508 :命令发送模块发送切换命令。 [0051] 脚步 510 :移动终端侧的驱动安装模块接收到开关命令后,对该命令进行解析,并根据解析结果向USB-switch发送开关信号。 [0052] 脚步 512 :USB-switch接收到切换信号后,进行USB数据路径的切换,将数据路径从驱动安装模块切换到移动终端主模块。 [0053] 脚步 514 :计算机移除安装在其中的命令发送模块,重新枚举设备信息得到移动终端主模块的上报,从而识别为移动终端。 [0054] 本发明第四实施例的移动终端自启动方法采用驱动安装模块安装移动终端作为计算机的虚拟光盘,自动运行移动终端中的自动安装程序进行安装 移动终端在电脑中,然后通过将数据路径从驱动安装模块切换到主模块,实现移动终端的自启动,避免了移动终端需要用户手动安装驱动带来的不便。 与电脑连接,达到方便使用者的技术效果。 [0055] 综上所述,本发明技术方案在移动终端首次连接电脑时,通过驱动安装模块将移动终端安装到电脑中,实现了移动终端的自启动。 ,从而达到方便用户的技术效果。 [0056] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明保护的范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:18.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101576863A(String), CN101576863B(String), DE202010017805U1(String), DK201200117U1(String), DK201200117U4(String), DK201200117W(String), EP2439649A1(String), EP2439649A4(String), US20120072902A1(String), WO2010139246A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101576863A(String), CN101576863B(String), DE202010017805U1(String), DK201200117U1(String), DK201200117U4(String), DK201200117W(String), EP2439649A1(String), EP2439649A4(String), US20120072902A1(String), WO2010139246A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101576863A(String), CN101576863B(String), DE202010017805U1(String), DK201200117U1(String), DK201200117U4(String), DK201200117W(String), EP2439649A1(String), EP2439649A4(String), US20120072902A1(String), WO2010139246A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), CN101576863A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271112(Integer), CN101576863B(String), 1048007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), DE202010017805U1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), DK201200117U1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), DK201200117U4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), DK201200117W(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), EP2439649A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), EP2439649A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), US20120072902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271112(Integer), WO2010139246A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101576863B(String), CN101576863B(String), 1305043200(Integer), 271112(Integer), 185396(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185956(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185956(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185956(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:19.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130246051A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for reducing call consumption of mobile terminal(String), 减少移动终端通话消耗的方法及移动终端(String), US20130246051A1(String), A method for reducing call power consumption of a mobile terminal and mobile terminal are disclosed in the present invention, wherein, the method includes: in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of the user; if not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal. With the present invention, voice call power consumption of the mobile terminal is reduced, battery usage time of the mobile terminal is extended, and user experience is enhanced.(String), 本发明公开了一种降低移动终端通话功耗的方法及移动终端,其中,该方法包括:在语音通话过程中,移动终端对移动终端自身采集的音频信号进行声纹建模, 获取声纹模型,判断获取的声纹模型与存储的用户声纹模型是否匹配; 如果不匹配,则放弃对采集的音频信号进行无线传输或放弃对采集的音频信号进行基带和射频处理和无线传输,如果匹配,则对音频信号进行基带和射频处理和无线传输 . 通过本发明,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。(String), US13/641808(String), 1307980800(Integer), US20130246051A1(String), 1379520000(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 15(Integer), US20030061036A1 | US20040138890A1 | US20050102134A1 | US20060074658A1 | US20080211641A1 | US20080255842A1 | US20080312924A1 | US20090094029A1 | US20090119106A1 | US6453285B1 | US7016834B1 | US7231019B2 | US7260724B1 | US7567827B2 | US7664636B1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\a74add85fa0d494aa68b3d9a0f7407c4.png(String), 185957(Integer), a74add85fa0d494aa68b3d9a0f7407c4.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for reducing call consumption of mobile terminal(String), 减少移动终端通话消耗的方法及移动终端(String), US20130246051A1(String), A method for reducing call power consumption of a mobile terminal and mobile terminal are disclosed in the present invention, wherein, the method includes: in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of the user; if not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal. With the present invention, voice call power consumption of the mobile terminal is reduced, battery usage time of the mobile terminal is extended, and user experience is enhanced.(String), 本发明公开了一种降低移动终端通话功耗的方法及移动终端,其中,该方法包括:在语音通话过程中,移动终端对移动终端自身采集的音频信号进行声纹建模, 获取声纹模型,判断获取的声纹模型与存储的用户声纹模型是否匹配; 如果不匹配,则放弃对采集的音频信号进行无线传输或放弃对采集的音频信号进行基带和射频处理和无线传输,如果匹配,则对音频信号进行基带和射频处理和无线传输 . 通过本发明,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。(String), US13/641808(String), 1307980800(Integer), US20130246051A1(String), 1379520000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 15(Integer), US20030061036A1 | US20040138890A1 | US20050102134A1 | US20060074658A1 | US20080211641A1 | US20080255842A1 | US20080312924A1 | US20090094029A1 | US20090119106A1 | US6453285B1 | US7016834B1 | US7231019B2 | US7260724B1 | US7567827B2 | US7664636B1(String), \20230420\a74add85fa0d494aa68b3d9a0f7407c4.png(String), 14(Integer), 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 1. A method for reducing call power consumption of a mobile terminal, comprising:in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user; andif not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 1.根据权利要求2所述的方法,其中:当存储有多个用户声纹模型时,如果移动终端判断移动终端采集到的音频信号与多个用户声纹模型中的任何一个都不匹配,则移动终端放弃对采集到的语音信号进行无线传输音频信号或者放弃对采集到的音频信号进行基带和射频处理以及无线传输,如果移动终端判断移动终端采集到的音频信号与用户的多种声纹模型中的至少一种相匹配,则移动终端对音频信号进行基带和射频处理及无线传输。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 2. The method according to claim 1, wherein:an establishment way of the stored voiceprint model of the user is any one or two of the following ways:before the voice call starts, recording a voice segment of a user, and establishing and storing the voiceprint model of the user according to the voice segment;when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, establishing and storing the voiceprint model of the user.(String), 12.根据权利要求2所述的方法,其中:存储的用户声纹模型包括:普通用户声纹模型和临时用户声纹模型;该方法还包括:将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中;或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 3. The method according to claim 1, wherein:when there are multiple stored voiceprint models of users, if the mobile terminal judges that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, the mobile terminal gives up performing the wireless transmission on the collected audio signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, and if the mobile terminal judges that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of users, the mobile terminal performs the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 13.根据权利要求7所述的移动终端,其中:声纹处理子模块,还用于当存储的用户声纹模型有多个时,当判断移动终端采集的音频信号与多个用户声纹模型中的任意一个不匹配时,确定获取的声纹模型与用户预存的声纹模型不匹配,当判断移动终端采集的音频信号与用户的多个声纹模型中的至少一个匹配时,确定获取的声纹模型与预存的声纹模型匹配-存储用户的声纹模型。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 4. The method according to claim 1, wherein:the stored voiceprint model of the user comprises: a voiceprint model of a common user and a voiceprint model of a temporary user;the method further comprises: storing the voiceprint model of the common user and the voiceprint model of the temporary user in a non-volatile memory of the mobile terminal; or, storing the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and storing the voiceprint model of the temporary user in a volatile memory of the mobile terminal.(String), 14.根据权利要求7所述的移动终端,其中:存储的用户声纹模型具体包括普通用户声纹模型和临时用户声纹模型,移动终端的存储器包括非易失性存储器和易失性存储器。声纹处理子模块还用于将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中。或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 5. The method according to claim 1, wherein:the step of the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user comprises: when the voice call starts, after receiving a voiceprint model establishment indication sent by the user, the mobile terminal firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process, and judging whether the obtained voiceprint model matches with any of all the stored voiceprint models of users;in the step of giving up performing the wireless transmission on the collected audio signal or giving up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, performing the wireless transmission on the audio signal collected in the subsequent voice call process is given up or performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process is given up.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 6. A mobile terminal for reducing call power consumption, comprising: a memory module and an antenna module, and further comprising: a baseband and radio frequency processing module, wherein, the baseband and radio frequency processing module comprises a voiceprint processing submodule and an audio signal control processing submodule;the memory module is configured to: store a voiceprint model of a user;the voiceprint processing submodule is configured to: in a voice call process, perform voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, judge whether the obtained voiceprint model matches with a stored voiceprint model of the user, and send a judgment result to the audio signal control processing submodule; andthe audio signal control processing submodule is configured to: when the judgment result is not matching, give up performing wireless transmission on the collected audio signal or give up performing baseband and radio frequency processing and wireless transmission on the collected audio signal; and when the judgment result is matching, perform the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 7. The mobile terminal according to claim 6, wherein:the voiceprint processing submodule is further configured to establish the stored voiceprint model of the user in any one or two of the following ways:before a voice call of the mobile terminal starts, according to a voice segment of a user recorded by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal;after the voice call of the mobile terminal starts, and when a voiceprint model establishment indication sent by the user is received, according to the audio signal collected by the mobile terminal, establishing the voiceprint model of the user and storing in the memory of the mobile terminal.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 8. The mobile terminal according to claim 6, wherein:the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 9. The mobile terminal according to claim 6, wherein:the stored voiceprint model of the user specifically comprises a voiceprint model of a common user and a voiceprint model of a temporary user, and the memory of the mobile terminal comprises a non-volatile memory and a volatile memory;the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 10. The mobile terminal according to claim 6, wherein:the voiceprint processing submodule is configured to perform the voiceprint modeling on the audio signal collected by the mobile terminal to obtain the voiceprint model during the voice call process in the following way: when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process to obtain the voiceprint model;the audio signal control processing submodule is configured to give up performing the wireless transmission on the collected audio signal or give up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal in the following way: giving up performing the wireless transmission on the audio signal collected in the subsequent voice call process or giving up performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 11. The method according to claim 2, wherein:when there are multiple stored voiceprint models of users, if the mobile terminal judges that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, the mobile terminal gives up performing the wireless transmission on the collected audio signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, and if the mobile terminal judges that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of users, the mobile terminal performs the baseband and radio frequency processing and wireless transmission on the audio signal.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 12. The method according to claim 2, wherein:the stored voiceprint model of the user comprises: a voiceprint model of a common user and a voiceprint model of a temporary user;the method further comprises: storing the voiceprint model of the common user and the voiceprint model of the temporary user in a non-volatile memory of the mobile terminal; or, storing the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and storing the voiceprint model of the temporary user in a volatile memory of the mobile terminal.(String), 1(Integer), 11(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 13. The mobile terminal according to claim 7, wherein:the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user.(String), 1(Integer), 12(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:20.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185957(Integer), 14. The mobile terminal according to claim 7, wherein:the stored voiceprint model of the user specifically comprises a voiceprint model of a common user and a voiceprint model of a temporary user, and the memory of the mobile terminal comprises a non-volatile memory and a volatile memory;the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185957(Integer), TECHNICAL FIELD [0001]The present invention relates to the field of mobile communication technology, and specifically, the invention relates to a method for reducing call power consumption of a mobile terminal and a mobile terminal. BACKGROUND OF THE RELATED ART [0002]With the rapid development of the communication and microelectronic technology, functions of a mobile phone become richer. Besides a traditional voice call function, various functions such as video call, photograph, camera shooting, recording, music play, video play, mobile TV, net play and JAVA games and so on are integrated, and the power consumption is comparatively high when these functions are used. Currently, lithium ion battery is used to power most mobile phones. Capacity of the lithium ion battery is usually small, but mobile phone users often expect that the battery can be used for a long time after one time of charging, so a contradiction between fast electricity consumption of mobile phone and limited battery capacity is caused. How to reduce the power consumption of the mobile phone to extend the usage time of the battery after one-time charging becomes an important task. In the study of reducing the power consumption of the mobile phone, the voice call service becomes the most important aspect in the task of reducing the power consumption of the mobile phone as the voice call service is used frequently and has high power consumption. [0003]As shown in FIG. 1, the existing uplink data transmission flow of mobile phone voice calls is: an audio signal collected through an MIC of a mobile terminal going through the analog amplification processing (such as three-level analog amplification processing), then being converted through an Analog-to-Digital Converter, which is also called as an AD converter, into a Pulse-code modulation (PCM) numerical code stream, being processed through an audio frequency algorithm, then being filtered through an equalizer, then audio frequency Adaptive Multi-Rat (AMR) coding being performed after a digital gain, and finally being transmitted out through a radio frequency after going through processing such as channel coding and modulation and so on. SUMMARY OF THE INVENTION [0004]In a normal condition, making a call is an interaction process between the two parties, wherein one party always speaks in a certain time and listens to the other party in a certain time, therefore, voices required to be transmitted through mobile phones and networks are discontinuous. However, the environment of voice calls is relatively complicated, as besides the voice of a caller himself, voices of other people and other environmental noises around always exist. Although the existing audio algorithm has echo suppression and noise suppression, it can only perform the noise suppression processing on the voices when the caller is speaking. When the caller is not speaking, other voices in the ambient environment are still taken as valid data to be processed and transmitted, so no matter whether the caller is speaking or not, the voices processed and transmitted by the audio frequency algorithm are always continuous. It causes that a great quantity of unwanted voice data are collected, processed and transmitted by the mobile phones and the system needs to process a great quantity of additional data, which brings large power consumption of the baseband and radio frequency. [0005]The object of the present invention is to provide a method and mobile terminal for reducing call power consumption of the mobile terminal, to solve the problem of how to reduce the power consumption of voice calls, save the battery electricity consumption of the mobile terminal, and reduce the transmission of invalid data. [0006]In order to solve the above technical problem, the present invention provides a method for reducing call power consumption of a mobile terminal, which comprises: [0007]in a voice call process, the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal itself to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user; and [0008]if not matching, giving up performing wireless transmission on the collected audio signal or giving up performing baseband and radio frequency processing and wireless transmission on the collected audio signal, and if matching, performing the baseband and radio frequency processing and wireless transmission on the audio signal. [0009]In the method of the present invention, an establishment way of the stored voiceprint model of the user is any one or two of the following ways: [0010]before the voice call starts, recording a voice segment of a user, and establishing and storing the voiceprint model of the user according to the voice segment; [0011]when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, establishing and storing the voiceprint model of the user. [0012]In the method of the present invention, when there are multiple stored voiceprint models of users, if the mobile terminal judges that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, the mobile terminal gives up performing the wireless transmission on the collected audio signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, and if the mobile terminal judges that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of users, the mobile terminal performs the baseband and radio frequency processing and wireless transmission on the audio signal. [0013]In the method of the present invention, the stored voiceprint model of the user comprises: a voiceprint model of a common user and a voiceprint model of a temporary user; [0014]the method further comprises: storing the voiceprint model of the common user and the voiceprint model of the temporary user in a non-volatile memory of the mobile terminal; or, [0015]storing the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and storing the voiceprint model of the temporary user in a volatile memory of the mobile terminal. [0016]In the method of the present invention, the step of the mobile terminal performing voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, and judging whether the obtained voiceprint model matches with a stored voiceprint model of a user comprises: when the voice call starts, after receiving a voiceprint model establishment indication sent by the user, the mobile terminal firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process, and judging whether the obtained voiceprint model matches with any of all the stored voiceprint models of users; [0017]in the step of giving up performing the wireless transmission on the collected audio signal or giving up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal, performing the wireless transmission on the audio signal collected in the subsequent voice call process is given up or performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process is given up. [0018]In order to solve the above technical problem, the present invention further provides a mobile terminal for reducing call power consumption, which comprises: a memory module and an antenna module, and further comprises: a baseband and radio frequency processing module, wherein, the baseband and radio frequency processing module comprises a voiceprint processing submodule and an audio signal control processing submodule; [0019]the memory module is configured to: store a voiceprint model of a user; [0020]the voiceprint processing submodule is configured to: in a voice call process, perform voiceprint modeling on an audio signal collected by the mobile terminal to obtain a voiceprint model, judge whether the obtained voiceprint model matches with a stored voiceprint model of the user, and send a judgment result to the audio signal control processing submodule; and [0021]the audio signal control processing submodule is configured to: when the judgment result is not matching, give up performing wireless transmission on the collected audio signal or give up performing baseband and radio frequency processing and wireless transmission on the collected audio signal; and when the judgment result is matching, perform the baseband and radio frequency processing and wireless transmission on the audio signal. [0022]In the mobile terminal of the present invention, the voiceprint processing submodule is further configured to establish the stored voiceprint model of the user in any one or two of the following ways: [0023]before a voice call of the mobile terminal starts, according to a voice segment of a user recorded by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal; [0024]after the voice call of the mobile terminal starts, and when a voiceprint model establishment indication sent by the user is received, according to the audio signal collected by the mobile terminal, establishing the voiceprint model of the user and storing in the memory of the mobile terminal. [0025]In the mobile terminal of the present invention, the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user. [0026]In the mobile terminal of the present invention, the stored voiceprint model of the user specifically comprises a voiceprint model of a common user and a voiceprint model of a temporary user, and the memory of the mobile terminal comprises a non-volatile memory and a volatile memory; [0027]the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal. [0028]In the mobile terminal of the present invention, the voiceprint processing submodule is configured to perform the voiceprint modeling on the audio signal collected by the mobile terminal to obtain the voiceprint model during the voice call process in the following way: when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, firstly establishing and storing the voiceprint model of the user according to the collected audio signal, and then performing the voiceprint modeling on an audio signal collected in a subsequent voice call process to obtain the voiceprint model; [0029]the audio signal control processing submodule is configured to give up performing the wireless transmission on the collected audio signal or give up performing the baseband and radio frequency processing and wireless transmission on the collected audio signal in the following way: giving up performing the wireless transmission on the audio signal collected in the subsequent voice call process or giving up performing the baseband and radio frequency processing and wireless transmission on the audio signal collected in the subsequent voice call process. [0030]Compared with the related art, with the technical scheme of the present invention, voice call power consumption of the mobile terminal is reduced, battery usage time of the mobile terminal is extended, and user experience is enhanced. Moreover, since transmission of invalid data is reduced, system load is alleviated, effective utilization rate of system resources is improved, and power consumption of the baseband and radio frequency is reduced. BRIEF DESCRIPTION OF DRAWINGS [0031]FIG. 1 is a traditional flow diagram of uplink voice processing of a mobile terminal voice call. [0032]FIG. 2 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in the example of the present invention. [0033]FIG. 3 is a structure diagram of a mobile terminal for reducing call power consumption in the example of the present invention. [0034]FIG. 4 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in one application example. [0035]FIG. 5 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in another application example. [0036]FIG. 6 is a flow diagram of uplink voice processing of a mobile phone voice call for reducing call power consumption in another application example. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0037]In order to make the object, technical scheme and advantages of the present invention more clear, the examples of the present invention will be described in detail in combination with the accompanying drawings below. It should be noted that the examples in the present invention and the characteristics in the examples can be optionally combined with each other in the condition of no conflict. [0038]As shown in FIG. 2, the example of the present invention provides a method for reducing call power consumption of a mobile terminal, a mobile phone is taken as an example, and the method includes following steps. [0039]In S201, when a caller is on the phone, in a voice call process, the mobile phone performs voiceprint modeling on an audio signal collected by the mobile phone itself. [0040]Wherein, the audio signal collected by the mobile phone itself refers to an audio signal collected by the mobile phone through an internal MIC, but not an audio signal received from an opposite terminal through the radio communication. The mobile phone uses the in-built MIC to collect audio signals, and no additional hardware device is required to be added, therefore, the system complexity is not increased, which is simple and practical. [0041]Wherein, in the call process, the operation of performing voiceprint modeling is generally real-time, which is performed in a certain time interval, the time interval can be manually set by a user according to the use demand, and also can be defaulted in the mobile terminal. [0042]The process of performing voiceprint modeling on the voice signal includes: after performing analog amplification, AD conversion and denoising operation on the collected audio signal, extracting voiceprint feature data from the denoised audio data, and then establishing the voiceprint model according to the extracted voiceprint feature data. Extracting the voiceprint feature data refers to extracting acoustic feature data or language feature data such as a cepstrum and so on with strong divisibility and high stability from the denoised audio data. [0043]At the point, the established voiceprint model may be the voiceprint model of the caller, and also may be voiceprint models formed from voices of other speakers in the environment. [0044]In S202, whether the obtained voiceprint model matches with a stored voiceprint model of the user is judged. [0045]The speaker of the current voices can be confirmed through the model matching, and it can be determined whether the extracted voices are the voices of the caller, that is, whether the caller is speaking, and whether the voice data are valid data of the call. [0046]Wherein, an establishment way of the stored voiceprint model of the user is any one or two of the following ways: [0047]before a voice call starts, recording a voice segment of the user, and according to the voice segment, establishing and storing the voiceprint model of the user; [0048]when the voice call starts, and after a voiceprint model establishment indication sent by the user is received, establishing and storing the voiceprint model of the user according to the collected audio signal. [0049]The stored voiceprint model of the user comprises: a voiceprint model of the common user and a voiceprint model of the temporary user, the voiceprint model of the common user and voiceprint model of the temporary user are stored in a non-volatile memory of the mobile terminal; or, the voiceprint model of the common user is stored in the non-volatile memory of the mobile terminal, and the voiceprint model of the temporary user is stored in a one-time memory of the mobile terminal. Generally speaking, the voiceprint model stored in the non-volatile memory of the mobile phone will be saved permanently, and the voiceprint model stored in the one-time memory of the mobile phone or in one data structure will be automatically deleted by the mobile phone after a time and will not be saved permanently. In the above storage modes, the first storage mode is beneficial to guaranteeing the data security, and the second mode is beneficial to saving the storage space of the mobile phone and processing capacity. [0050]In a general application situation, the user using the mobile phone only includes the owner of the mobile phone. When the mobile phone is in a non-call state, the owner of the mobile phone can record the voice segment of the user through the mobile phone, and the voiceprint model of the user can be established and stored according to the voice segment. [0051]In other application situations, the user using the mobile phone not only includes the owner of the mobile phone, but also includes other users. A common user can be the owner of the mobile phone, and a temporary user can be a temporary borrower of the mobile phone. If what the caller is using is not his own mobile phone, or if a situation that the mobile phone needs to be transferred to another person who will talk to the other party of the conversation in the call process occurs, the voiceprint model establishment indication can be sent to the mobile phone in the way of key selection through a menu on the mobile phone during the conversation, and its own voiceprint model is established within a period of time when the conversation just starts and stored in the mobile phone, and is taken as a reference voiceprint model for the subsequent model matching. For example, a certain keypad used to establish and store the voiceprint model of the current caller is set, and then after the current caller presses the keypad, the mobile phone receives the voiceprint model establishment indication sent by the user. The user sends a segment of voice used for modeling after pressing the keypad, and the mobile phone automatically intercepts the voice from the beginning of receiving the voiceprint model establishment indication to a later preset time length (e.g. 10 seconds) so as to establish and store the voiceprint model of the user, or, the user also can control the end time of the voice. For example, after the user sends the segment of voice, the mobile phone is indicated by keypad selection though the menu on the mobile phone during the conversation that the voice for modeling ends, and then the mobile phone establishes and stores the voiceprint model of the user according to the voice from the time of receiving the voiceprint model establishment indication to the time of receiving a voiceprint model establishment end indication. [0052]Certainly, in the specific implementation, other methods also can be used to confirm the common user. For example, a public terminal can determine one or multiple common users and one or multiple temporary users voluntarily. [0053]In the example, the model matching refers to performing similarity matching on the voiceprint model established according to the extracted voiceprint feature data and the voiceprint model stored in the mobile phone. A common method includes: a probability statistics method, a dynamic time warping method and a neural network method and so on. In the specific implementation, whether a matching degree between the voiceprint model established according to the extracted voiceprint feature data and the reference voiceprint model stored in the mobile phone reaches a certain preset threshold can be judged through a distance measurement algorithm. If the matching degree between the voiceprint model established according to the extracted voiceprint feature data and the reference voiceprint model stored in the mobile phone reaches the certain preset threshold, it is matching, and if the matching degree between the voiceprint model established according to the extracted voiceprint feature data and the reference voiceprint model stored in the mobile phone does not reach the certain preset threshold, it is not matching. Generally, the threshold can be adjusted according to the practical situation. [0054]In S203, if not matching, performing wireless transmission on the collected voice signal is given up or performing baseband and radio frequency processing and wireless transmission on the collected voice signal is given up, and if matching, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. [0055]Specifically, in the example, if the matching is determined, it is considered that the extracted voices are the voices of the existing valid user, and the voice data thereof are valid data of the call and required to be processed and transmitted. If the matching is not determined, it is considered that the extracted voices are not the voices of the existing valid user, such as environmental sounds (including mute, or the voices of other people in the environment), and the voice data thereof are not valid data of the call and not required to be processed and transmitted. At the point, the CPU load of a baseband chip of the mobile phone is decreased, a radio frequency is also in a state of no data transmission, and the system power consumption can be reduced. [0056]In practical applications, the mobile phone also may have stored voiceprint models of multiple users. If the mobile terminal judges that the voice signal collected by the mobile terminal itself does not match with any one of the multiple voiceprint models of the users, the mobile terminal gives up performing the wireless transmission on the collected voice signal or gives up performing the baseband and radio frequency processing and wireless transmission on the collected voice signal, and if the mobile terminal judges that the voice signal collected by the mobile terminal itself matches with at least one of the multiple voiceprint model of the users, performs the baseband and radio frequency processing and wireless transmission on the voice signal. [0057]In the above example, performing the baseband and radio frequency processing on the voice signal refers to performing processing such as audio algorithm processing, digital equalization processing, digital gain processing, AMR coding processing, channel coding processing, modulation processing and radio frequency processing, etc. on the audio signal. [0058]Correspondingly, as shown in FIG. 3, the example also provides a mobile terminal for reducing call power consumption, and the mobile terminal includes: a memory module, a baseband and radio frequency processing module and an antenna module, wherein, [0059]the memory module includes a volatile memory and a non-volatile memory, and is configured to: store a voiceprint model of the user, wherein, the stored voiceprint model of the user specifically includes a voiceprint model of the common user and a voiceprint model of the temporary user; [0060]the baseband and radio frequency processing module includes a voiceprint processing submodule and an audio signal control processing submodule, wherein, [0061]the voiceprint processing submodule is configured to: in a voice call process, perform voiceprint modeling on an audio signal collected by the mobile terminal, judge whether the obtained voiceprint model matches with the stored voiceprint model of the user, and send a judgment result to the audio signal control processing submodule; [0062]the voiceprint processing submodule is further configured to establish the stored voiceprint model of the user in any one or two of the following ways: before a voice call of the mobile terminal starts, according to a voice segment of a user recorded by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal; after the voice call of the mobile terminal starts, and when a voiceprint model establishment indication sent by the user is received, according to the audio signal collected by the mobile terminal, establishing the voiceprint model of the user and storing in a memory of the mobile terminal; [0063]the voiceprint processing submodule is further configured to: when there are multiple stored voiceprint models of users, when judging that the audio signal collected by the mobile terminal does not match with any one of the multiple voiceprint models of users, determine that the obtained voiceprint model does not match with the pre-stored voiceprint model of the user, and when judging that the audio signal collected by the mobile terminal matches with at least one of the multiple voiceprint models of the users, determine that the obtained voiceprint model matches with the pre-stored voiceprint model of the user; and [0064]the voiceprint processing submodule is further configured to: store the voiceprint model of the common user and the voiceprint model of the temporary user in the non-volatile memory of the mobile terminal; or, store the voiceprint model of the common user in the non-volatile memory of the mobile terminal, and store the voiceprint model of the temporary user in the volatile memory of the mobile terminal. [0065]The audio signal control processing submodule is configured to: when the judgment result is not matching, give up performing wireless transmission on the collected audio signal or give up performing baseband and radio frequency processing and wireless transmission on the collected audio signal; and when the judgment result is matching, perform the baseband and radio frequency processing and wireless transmission on the audio signal. [0066]The audio signal control processing submodule performing the baseband and radio frequency processing on the audio signal refers to: performing audio algorithm processing, digital equalization processing, digital gain processing, AMR coding processing, channel coding processing, modulation processing and radio frequency processing on the audio signal. [0067]The antenna module is configured to: perform wireless transmission on the voice signal which has gone through the baseband and radio frequency processing. Specific Example 1 [0068]In the specific example 1, an execution mode of establishing and storing a voiceprint model of the user before a call starts is mainly described. As shown in FIG. 4, the specific example includes following steps. [0069]In S301, before the voice call starts, a mobile terminal records a voice segment of a common user A, and according to the voice segment, establishes and stores a voiceprint model of the user A. [0070]In S302, during the voice call, the mobile terminal performs voiceprint modeling on an audio signal collected by the mobile terminal itself. [0071]In S303, whether the obtained voiceprint model matches with the stored voiceprint model of the user A is judged. [0072]In S304, if not matching, step S305 is executed, and if matching, S306 is executed. [0073]In S305, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process is given up, and the flow ends. [0074]In S306, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. Specific Example 2 [0075]In the specific example 2, an execution mode of establishing and storing a voiceprint model of the user after a call starts is mainly described. As shown in FIG. 5, the specific example includes following steps. [0076]In S401, after the voice call starts, a mobile terminal receives a voiceprint model establishment indication sent by a user A, and according to the collected voice signal (i.e. a voice sent after the user presses the voiceprint model establishment indication), establishes and stores a voiceprint model of the user A. [0077]In S402, during the subsequent voice call, the mobile terminal performs voiceprint modeling on a voice signal collected in subsequence. [0078]In S403, whether the obtained voiceprint model matches with the stored voiceprint model of the user is judged. [0079]In S404, if not matching, step S405 is executed, and if matching, S406 is executed. [0080]In S405, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process is given up, and the flow ends. [0081]In S406, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. Specific Example 3 [0082]In the specific example 3, an execution mode that a voiceprint model of the user is required to be established and stored before and after a call starts is mainly described. As shown in FIG. 6, the specific example includes following steps. [0083]In S501, before the voice call starts, a mobile terminal records a voice segment of a common user A, and according to the voice segment, establishes and stores a voiceprint model of the user A. [0084]In S502, during the process of the user A using the mobile phone to make the voice call, the mobile terminal performs voiceprint modeling on an audio signal collected by the mobile terminal itself. [0085]In S503, whether the obtained voiceprint model matches with the stored voiceprint model of the user A is judged. [0086]In S504, if not matching, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process is given up, and if matching, the baseband and radio frequency processing and wireless transmission are performed on the voice signal. [0087]In S505, a temporary user B replaces the user A to make the call with the opposite end in the call process, and sends a voiceprint model establishment indication to the mobile phone by performing key selection through a menu on the mobile phone while talking, the mobile phone establishes and stores a voiceprint model of the user B according to the voice signal collected in subsequence (i.e. a voice sent after the user B presses the voiceprint model establishment indication). Within the time range of the mobile phone establishing the voiceprint model for the user B, the baseband and radio frequency processing and wireless transmission are performed on all the collected audio signals. [0088]In S506, after establishing and storing the voiceprint model of the user B, the mobile phone continues to perform voiceprint modeling on voice signals collected in subsequence. [0089]In S507, whether the obtained voiceprint model matches with the stored voiceprint models of the user A and user B is judged. [0090]In S508, if no one of the stored voiceprint models of the user A and user B is matched, performing wireless transmission on the voice signal collected in the subsequent voice call process is given up or performing baseband and radio frequency processing and wireless transmission on the voice signal collected in the subsequent voice call process(String), 技术领域 [0001] 本发明涉及移动通信技术领域,具体涉及一种降低移动终端通话功耗的方法及移动终端。 相关技术背景 [0002] 随着通信技术和微电子技术的飞速发展,手机的功能越来越丰富。 除了传统的语音通话功能外,还集成了视频通话、拍照、拍照、录音、音乐播放、视频播放、手机电视、网络播放、JAVA游戏等多种功能,这些功能耗电较高 使用函数。 目前,锂离子电池用于为大多数手机供电。 锂离子电池的容量通常较小,而手机用户往往希望电池充一次电就可以使用很长时间,这就造成了手机用电快和电池容量有限的矛盾。 如何降低手机的功耗,延长电池一次充电后的使用时间成为一项重要课题。 在降低手机功耗的研究中,由于语音通话业务使用频率高、功耗大,因此语音通话业务成为降低手机功耗任务中最重要的方面。 [0003] 如图1所示,现有的手机语音通话的上行数据传输流程是:通过移动终端MIC采集的音频信号,经过模拟放大处理(如三级模拟放大处理),然后进行转换 通过Analog-to-Digital Converter,也叫AD转换器,转换成Pulse-code modulation(PCM)数字码流,经过音频算法处理,再经过均衡器滤波,然后音频自适应 Multi-Rat(AMR)编码是经过数字增益后进行的,经过信道编码、调制等处理后,最终通过射频发射出去。 发明内容 [0004] 在正常情况下,通话是双方的一个交互过程,一方总是在一定的时间内说话,而另一方总是在一定的时间内听对方说话,因此,需要通过手机和网络传输的语音是 不连续的。 然而,语音通话的环境比较复杂,除了通话者自己的声音外,周围的其他人的声音和其他环境噪声也始终存在。 现有的音频算法虽然具有回声抑制和噪声抑制功能,但只能对来电者说话时的声音进行噪声抑制处理。 当来电者不说话时,周围环境中的其他声音仍然作为有效数据进行处理和传输,所以无论来电者是否在说话,经过音频算法处理和传输的语音始终是连续的。 这导致手机采集、处理和传输大量不需要的语音数据,系统需要处理大量的附加数据,带来基带和射频的大量功耗。 [0005] 本发明的目的在于提供一种降低移动终端通话功耗的方法及移动终端,解决如何降低语音通话功耗,节省移动终端电池电量,以及 减少无效数据的传输。 [0006] 为了解决上述技术问题,本发明提供了一种降低移动终端通话功耗的方法,包括: [0007] 在语音通话过程中,移动终端对自身采集的音频信号进行声纹建模,得到声纹模型,判断得到的声纹模型与存储的用户声纹模型是否匹配。 和 [0008]不匹配则放弃对采集到的音频信号进行无线传输或放弃对采集到的音频信号进行基带和射频处理无线传输,匹配则对音频信号进行基带和射频处理无线传输 . [0009] 在本发明的方法中,所述用户存储声纹模型的建立方式为以下方式中的任意一种或两种: [0010] 在语音通话开始前,记录用户的语音片段,并根据语音片段建立并存储用户的声纹模型; [0011] 当语音通话开始时,接收到用户发送的声纹模型建立指示后,建立并存储用户的声纹模型。 [0012] 在本发明的方法中,当存储有多个用户声纹模型时,如果移动终端判断出移动终端采集的音频信号与多个用户声纹模型中的任何一个都不匹配,则移动终端给出 停止对采集到的音频信号进行无线传输或者放弃对采集到的音频信号进行基带和射频处理以及无线传输,如果移动终端判断出移动终端采集到的音频信号与以下至少一种匹配 用户的多种声纹模型,移动终端对音频信号进行基带和射频处理及无线传输。 [0013] 在本发明的方法中,所述存储的用户声纹模型包括:普通用户声纹模型和临时用户声纹模型; [0014] 该方法还包括:将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中; 或者, [0015] 将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。 [0016] 在本发明的方法中,所述移动终端对其采集的音频信号进行声纹建模得到声纹模型,并判断得到的声纹模型与存储的用户声纹模型是否匹配包括: 当语音通话开始时,移动终端接收到用户发送的声纹模型建立指示后,首先根据采集到的音频信号建立并存储用户的声纹模型,然后对采集到的音频信号进行声纹建模。 后续的语音通话流程,判断获取的声纹模型是否与所有存储的用户声纹模型匹配; [0017] 所述放弃对采集到的音频信号进行无线传输或者放弃对采集到的音频信号进行基带和射频处理无线传输的步骤中,对后续语音通话过程中采集到的音频信号进行无线传输为 放弃或放弃对后续语音通话过程中采集到的音频信号进行基带和射频处理和无线传输。 [0018] 为了解决上述技术问题,本发明还提供了一种降低通话功耗的移动终端,包括:存储模块和天线模块,还包括:基带和射频处理模块,其中,基带 射频处理模块包括声纹处理子模块和音频信号控制处理子模块; [0019] 存储模块用于存储用户的声纹模型; [0020]声纹处理子模块用于在语音通话过程中,对移动终端采集的音频信号进行声纹建模,得到声纹模型,判断得到的声纹模型与存储的用户声纹模型是否匹配,发送 判断结果给音频信号控制处理子模块; 和 [0021] 音频信号控制处理子模块,用于当判断结果不匹配时,放弃对采集到的音频信号进行无线传输或放弃对采集到的音频信号进行基带和射频处理及无线传输。 当判断结果匹配时,对音频信号进行基带和射频处理及无线传输。 [0022] 在本发明的移动终端中,所述声纹处理子模块还用于通过以下任意一种或两种方式建立所述用户的存储声纹模型: [0023] 在移动终端语音通话开始前,根据移动终端记录的用户的语音片段,建立用户的声纹模型并存储在移动终端的内存中; [0024] 移动终端语音通话开始后,当接收到用户发送的声纹模型建立指示时,根据移动终端采集的音频信号,建立用户的声纹模型并存储在手机内存中 终端。 [0025] 在本发明的移动终端中,所述声纹处理子模块还用于:当存储的用户声纹模型有多个时,当判断移动终端采集的音频信号与所述多个声纹模型中的任意一个不匹配时 的用户,确定获取的声纹模型与预先存储的用户的声纹模型不匹配,当判断移动终端采集的音频信号与用户的多个声纹模型中的至少一个匹配时,确定 获取的声纹模型与预先存储的用户声纹模型匹配。 [0026] 在本发明的移动终端中,存储的用户声纹模型具体包括普通用户声纹模型和临时用户声纹模型,移动终端的存储器包括非易失性存储器和易失性存储器。 记忆; [0027] 声纹处理子模块还用于将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中。 或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。 [0028] 在本发明的移动终端中,声纹处理子模块用于在语音通话过程中对移动终端采集的音频信号进行声纹建模,得到声纹模型:当语音通话开始时, 接收到用户发送的声纹模型建立指示后,首先根据采集到的音频信号建立并存储用户的声纹模型,再对后续语音通话过程中采集到的音频信号进行声纹建模得到 声纹模型; [0029] 音频信号控制处理子模块,用于放弃对采集到的音频信号进行无线传输或者放弃对采集到的音频信号进行基带和射频处理无线传输,具体方式为:放弃对采集到的音频信号进行无线传输。 后续语音通话过程中采集的音频信号或者放弃对后续语音通话过程中采集的音频信号进行基带和射频处理以及无线传输。 [0030]与相关技术相比,采用本发明的技术方案,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。 并且,由于减少了无效数据的传输,减轻了系统负载,提高了系统资源的有效利用率,降低了基带和射频的功耗。 附图说明 [0031] 图1是传统的移动终端语音通话的上行语音处理流程图。 [0032] 图2为本发明实施例中用于降低通话功耗的手机语音通话的上行语音处理流程图。 [0033] 图3为本发明实施例中降低通话功耗的移动终端的结构示意图。 [0034] 图4为一种应用示例中为降低通话功耗而对手机语音通话进行上行语音处理的流程图。 [0035] 图5为另一应用示例中降低通话功耗的手机语音通话的上行语音处理流程图。 [0036] 图6为另一应用示例中降低通话功耗的手机语音通话的上行语音处理流程图。 本发明的优选实施例 [0037] 为使本发明的目的、技术方案及优点更加清楚明白,以下结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本发明中的实施例及实施例中的特征可以相互任意组合。 [0038] 如图2所示,本发明实施例提供了一种降低移动终端通话功耗的方法,以手机为例,该方法包括以下步骤。 [0039] 在 S 201 ,当来电者在通话时,在语音通话过程中,手机对手机自身采集的音频信号进行声纹建模。 [0040] 其中,手机自身采集的音频信号是指手机通过内置MIC采集的音频信号,而不是通过无线通信从对端接收到的音频信号。 该手机采用内置MIC采集音频信号,无需增加额外的硬件设备,不增加系统复杂度,简单实用。 [0041] 其中,在通话过程中,进行声纹建模的操作一般是实时的,以一定的时间间隔进行,该时间间隔可以由用户根据使用需求手动设置,也可以默认为 移动终端。 [0042] 对语音信号进行声纹建模的过程包括:对采集到的音频信号进行模拟放大、AD转换和去噪操作后,从去噪后的音频数据中提取声纹特征数据,然后根据提取的声纹特征建立声纹模型 数据。 提取声纹特征数据是指从降噪后的音频数据中提取可分性强、稳定性高的声学特征数据或语言特征数据,如倒谱等。 [0043] 此时,建立的声纹模型可以是通话方的声纹模型,也可以是环境中其他说话人的声音形成的声纹模型。 [0044] 在 S 202 ,判断获取的声纹模型与存储的用户声纹模型是否匹配。 [0045] 通过模型匹配可以确定当前语音的说话人,判断提取的语音是否为来电方的语音,即来电方是否在说话,语音数据是否为通话的有效数据 . [0046] 其中,用户存储的声纹模型的建立方式为以下方式中的任意一种或两种: [0047] 在语音通话开始前,记录用户的语音片段,并根据语音片段建立并存储用户的声纹模型; [0048] 当语音通话开始时,接收到用户发送的声纹模型建立指示后,根据采集到的音频信号建立并存储用户的声纹模型。 [0049] 存储的用户声纹模型包括:普通用户声纹模型和临时用户声纹模型,普通用户声纹模型和临时用户声纹模型存储在手机的非易失性存储器中 终端; 或者,普通用户的声纹模型存储在移动终端的非易失性存储器中,临时用户的声纹模型存储在移动终端的一次性存储器中。 一般来说,保存在手机非易失性存储器中的声纹模型会永久保存,而保存在手机一次性内存或某种数据结构中的声纹模型会被手机自动删除 一段时间后,将不会永久保存。 在上述存储方式中,第一种存储方式有利于保证数据安全,第二种存储方式有利于节省手机的存储空间和处理能力。 [0050] 在一般的应用情况下,使用手机的用户只包括手机的所有者。 当手机处于非通话状态时,手机主人可以通过手机记录用户的语音片段,根据语音片段建立并存储用户的声纹模型。 [0051] 在其他应用场合,使用手机的用户不仅包括手机的所有者,还包括其他用户。 普通用户可以是手机的主人,临时用户可以是手机的临时借用者。 如果主叫方使用的不是自己的手机,或者在通话过程中出现需要将手机转移给其他人与通话对方通话的情况,声纹模型建立指示可以 在通话过程中通过手机上的菜单以按键选择的方式发送至手机,并在通话刚开始的一段时间内建立自己的声纹模型并存储在手机中,并被提取 作为后续模型匹配的参考声纹模型。 例如,设置用于建立和存储当前主叫方声纹模型的某个键盘,则当前主叫方按下该键盘后,手机接收到用户发送的声纹模型建立指示。 用户按下键盘后发送一段用于建模的语音,手机从收到声纹模型建立指示开始到后面的预设时长(如10秒)自动截取语音,建立并存储 用户的声纹型号,或者,用户还可以控制语音的结束时间。 例如,用户发送一段语音后,在通话过程中通过手机菜单通过键盘选择提示手机建模语音结束,然后手机建立并存储该语音段的声纹模型。 用户根据语音从接收到声纹模型建立指示到接收到声纹模型建立结束指示为止。 [0052] 当然,在具体实现中,也可以采用其他方式对普通用户进行确认。 例如,公共终端可以自行确定一个或多个普通用户和一个或多个临时用户。 [0053]在本实施例中,模型匹配是指将根据提取的声纹特征数据建立的声纹模型与手机中存储的声纹模型进行相似度匹配。 常用的方法有:概率统计法、动态时间规整法和神经网络法等。 具体实施中,可以通过测距算法判断根据提取的声纹特征数据建立的声纹模型与手机中存储的参考声纹模型的匹配度是否达到某个预设阈值。 如果根据提取的声纹特征数据建立的声纹模型与手机中存储的参考声纹模型的匹配度达到一定的预设阈值,则匹配,如果根据提取的声纹特征数据建立的声纹模型之间的匹配度 声纹特征数据与手机中存储的参考声纹模型没有达到一定的预设阈值,不匹配。 一般来说,阈值可以根据实际情况进行调整。 [0054] 在 S 203 ,如果不匹配,则放弃对采集到的语音信号进行无线传输或者放弃对采集到的语音信号进行基带和射频处理,无线传输,如果匹配,则进行基带和射频处理,无线传输 在语音信号上。 [0055] 具体地,在该示例中,如果确定匹配,则认为提取的语音是现有有效用户的语音,其语音数据是呼叫的有效数据,需要处理和传输。 如果不匹配,则认为提取的语音不是现有有效用户的语音,如环境音(包括静音,或环境中其他人的语音),其语音数据不是 呼叫的有效数据,不需要处理和传输。 此时手机基带芯片的CPU负荷降低,射频也处于无数据传输状态,可以降低系统功耗。 [0056] 在实际应用中,手机中还可能存储有多个用户的声纹模型。 若移动终端判断自身采集的语音信号与用户的多个声纹模型中的任一个都不匹配,则移动终端放弃对采集到的语音信号进行无线传输或者放弃进行基带传输。 对采集到的语音信号进行射频处理和无线传输,如果移动终端判断自身采集到的语音信号与用户的多种声纹模型中的至少一种匹配,则进行基带和射频处理 以及语音信号的无线传输。 [0057] 在上面的例子中,对语音信号进行基带和射频处理是指进行音频算法处理、数字均衡处理、数字增益处理、AMR编码处理、信道编码处理、调制处理和射频处理等处理。 .关于音频信号。 [0058] 相应地,如图3所示,本实施例还提供了一种降低通话功耗的移动终端,该移动终端包括:存储模块、基带及射频处理模块和天线模块,其中, [0059] 存储模块包括易失性存储器和非易失性存储器,用于存储用户的声纹模型,其中,存储的用户声纹模型具体包括普通用户的声纹模型和普通用户的声纹模型。 临时用户; [0060] 基带及射频处理模块包括声纹处理子模块和音频信号控制处理子模块,其中, [0061]声纹处理子模块用于在语音通话过程中,对移动终端采集的音频信号进行声纹建模,判断获取的声纹模型与存储的用户声纹模型是否匹配,并将判断结果发送给 音频信号控制处理子模块; [0062] 声纹处理子模块还用于通过以下任意一种或两种方式建立存储的用户声纹模型: 在移动终端语音通话开始前,根据移动终端记录的用户语音片段, 建立用户的声纹模型并存储在移动终端的内存中; 移动终端语音通话开始后,当接收到用户发送的声纹模型建立指示时,根据移动终端采集到的音频信号,建立用户的声纹模型并存储在手机的内存中 终端; [0063] 声纹处理子模块,还用于当存储的用户声纹模型有多个时,当判断移动终端采集的音频信号与多个用户声纹模型中的任意一个不匹配时,确定获取的声纹模型 与用户预存的声纹模型不匹配,当判断移动终端采集的音频信号与用户的多个声纹模型中的至少一个匹配时,确定获取的声纹模型与预存的声纹模型匹配 -存储的用户声纹模型; 和 [0064] 声纹处理子模块还用于将普通用户的声纹模型和临时用户的声纹模型存储在移动终端的非易失性存储器中。 或者,将普通用户的声纹模型存储在移动终端的非易失性存储器中,将临时用户的声纹模型存储在移动终端的易失性存储器中。 [0065] 音频信号控制处理子模块,用于当判断结果不匹配时,放弃对采集到的音频信号进行无线传输或放弃对采集到的音频信号进行基带和射频处理及无线传输。 当判断结果匹配时,对音频信号进行基带和射频处理及无线传输。 [0066] 音频信号控制处理子模块对音频信号进行基带和射频处理是指:对音频进行音频算法处理、数字均衡处理、数字增益处理、AMR编码处理、信道编码处理、调制处理和射频处理。 信号。 [0067] 天线模块用于对经过基带和射频处理后的语音信号进行无线传输。 具体实例一 [0068] 在具体实施例一中,主要描述在通话开始前建立并存储用户的声纹模型的执行方式。 如图4所示,具体示例包括以下步骤。 [0069] 在 S 301 ,在语音通话开始前,移动终端记录普通用户A的语音片段,并根据语音片段建立并存储用户A的声纹模型。 [0070] 在 S 302 ,在语音通话过程中,移动终端对移动终端自身采集的音频信号进行声纹建模。 [0071] 在 S 303 ,判断获取的声纹模型与存储的用户A的声纹模型是否匹配。 [0072] 在 S 304 , 如果不匹配, 步骤S 305 被执行,如果匹配,S 306 被执行。 [0073] 在 S 305 、放弃对后续语音通话过程中采集的语音信号进行无线传输,或者放弃对后续语音通话过程中采集的语音信号进行基带和射频处理,无线传输,流程结束。 [0074] 在 S 306,对语音信号进行基带和射频处理及无线传输。 具体例子2 [0075] 在具体实施例二中,主要描述通话开始后建立并存储用户的声纹模型的执行方式。 如图5所示,具体示例包括以下步骤。 [0076] 在 S 401 ,语音通话开始后,移动终端接收用户A发送的声纹模型建立指示,根据采集到的语音信号(即用户按下声纹模型建立指示后发出的语音),建立并存储声纹 用户A的模型 [0077] 在 S 402 ,在后续的语音通话中,移动终端对后续采集的语音信号进行声纹建模。 [0078] 在 S 403 ,判断获取的声纹模型与存储的用户声纹模型是否匹配。 [0079] 在 S 404 , 如果不匹配, 步骤S 405 被执行,如果匹配,S 406 被执行。 [0080] 在 S 405 、放弃对后续语音通话过程中采集的语音信号进行无线传输,或者放弃对后续语音通话过程中采集的语音信号进行基带和射频处理,无线传输,流程结束。 [0081] 在 S 406 ,对语音信号进行基带和射频处理及无线传输。 具体实例3 [0082] 在具体实施例三中,主要描述了通话开始前后需要建立并存储用户的声纹模型的执行方式。 如图6所示,具体示例包括以下步骤。 [0083] 在 S 501 ,在语音通话开始前,移动终端记录普通用户A的语音片段,并根据语音片段建立并存储用户A的声纹模型。 [0084] 在 S 502 ,在用户A使用手机进行语音通话的过程中,移动终端对自身采集的音频信号进行声纹建模。 [0085] 在 S 503 ,判断获取的声纹模型与存储的用户A的声纹模型是否匹配。 [0086] 在 S 504 ,如果不匹配,则放弃对后续语音通话过程中采集的语音信号进行无线传输或者放弃对后续语音通话过程中采集的语音信号进行基带和射频处理,无线传输,如果匹配 ,对语音信号进行基带和射频处理及无线传输。 [0087] 在 S 505 ,临时用户B在通话过程中代替用户A与对端通话,并在通话过程中通过手机上的菜单进行按键选择,向手机发送声纹模型建立指示,手机 根据后续采集到的语音信号(即用户B按下声纹模型建立指示后发出的语音),建立并存储用户B的声纹模型。 在手机为用户B建立声纹模型的时间范围内,对采集到的所有音频信号进行基带和射频处理及无线传输。 [0088] 在 S 506 ,手机B建立并存储用户B的声纹模型后,继续对后续采集的语音信号进行声纹建模。 [0089] 在 S 507 ,判断获取的声纹模型与存储的用户A和用户B的声纹模型是否匹配。 [0090] 在 S 508,如果存储的用户A和用户B的声纹模型均不匹配,则放弃对后续语音通话过程中采集的语音信号进行无线传输或对语音信号进行基带和射频处理无线传输 放弃在后续语音通话过程中收集到的,如果其中至少有一个匹配,则对语音信号进行基带和射频处理和无线传输。 [0091] 从以上示例可以看出,本发明提供的降低移动终端通话功耗的方法及移动终端,通过在现有语音通话上行流程中增加一个基带处理模块,对声纹建模进行声纹建模。 移动终端采集的语音信号,非主叫方的语音数据通过模型匹配被丢弃,后续的基带和射频处理和/或无线传输不再进行,减少了处理和传输 对于无效数据,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,提升了用户体验。 同时,如果通话对方手机的上行也采用声纹处理,则相应地带来当前方接收数据量的减少,下行流量处理的任务量也减少 从而减轻系统负载,提高系统资源的有效利用率,降低基带和射频的功耗。 [0092] 本发明不需要在手机的硬件系统中增加额外的部件,也不需要对硬件布局进行改动。 只需要在软件上已有的语音通话上行流程中增加一个基带处理模块,利用手机内置的音频系统即可实现。 [0093] 本领域普通技术人员可以理解,上述方法中的全部或部分步骤可以通过程序指令相关硬件来完成,该程序可以存储在计算机可读取存储介质中,例如只读存储器 、磁盘或光盘等。 或者,上述实施例的全部或部分步骤也可以采用一个或多个集成电路来实现。 相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。 本发明不限于任何特定形式的硬件和软件的组合。 [0094] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。 根据本发明的内容,还可以有其他各种实施例,本领域的技术人员可以在不脱离本发明的精神和实质的情况下,根据本发明作出各种相应的变化和变换,所有 所作的修改、等同替换、改进等,均属于本发明的保护范围。 工业实用性 [0095] 采用本发明的技术方案,降低了移动终端的语音通话功耗,延长了移动终端的电池使用时间,增强了用户体验。 并且,由于减少了无效数据的传输,减轻了系统负载,提高了系统资源的有效利用率,降低了基带和射频的功耗。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102781075A(String), CN102781075B(String), DK2551847T3(String), EP2551847A1(String), EP2551847A4(String), EP2551847B1(String), US20130246051A1(String), WO2012151771A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.293 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102781075A(String), CN102781075B(String), DK2551847T3(String), EP2551847A1(String), EP2551847A4(String), EP2551847B1(String), US20130246051A1(String), WO2012151771A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102781075A(String), CN102781075B(String), DK2551847T3(String), EP2551847A1(String), EP2551847A4(String), EP2551847B1(String), US20130246051A1(String), WO2012151771A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), CN102781075A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271317(Integer), CN102781075B(String), 1048560(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), DK2551847T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), EP2551847A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), EP2551847A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.504 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), EP2551847B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), US20130246051A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271317(Integer), WO2012151771A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN102781075B(String), CN102781075B(String), 1471968000(Integer), 271317(Integer), 185601(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), CAI, XIAOGUANG(String), ZHAN, MING(String), 中兴通讯股份有限公司(String), CAI XIAOGUANG(String), ZHAN MING(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185957(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: CAI, XIAOGUANG(String), CAI XIAOGUANG(String), 0(Integer), 1681976061(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHAN, MING(String), ZHAN MING(String), 0(Integer), 1681976061(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185957(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75834(Integer), 2(Integer), 185957(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75835(Integer), 2(Integer), 185957(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:21.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75834(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185957(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8811949B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Anti-theft mobile terminal and anti-theft method for mobile terminal(String), 移动终端防盗及移动终端防盗方法(String), US8811949B2(String), An anti-theft mobile terminal is disclosed, including: a setting module (10); an encryption module (11), configured to set a screen-lock password and an information return verification password of the mobile terminal; a password verification module (12), configured to verify a screen-unlock password input by a user; a detection module (18), configured to trigger a power management module (13) when detecting that an SIM card or battery has been pulled out, or the battery has run down longer than a preset duration; the power management module (13), configured to stop power supply from the battery of the mobile terminal and start a standby power supply to supply power to an information return module (14), an information deleting module (15), a positioning module (16), and an IMSI; the information return module (14), configured to verify a received information return verification password and return information saved in a set storage area after successful verification; the information deleting module (15), configured to delete the returned information; the positioning module (16), configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. An anti-theft method for mobile terminals is also disclosed.(String), 公开了一种防盗移动终端,包括:设置模块( 10 ); 加密模块( 11 ),用于设置移动终端的锁屏密码和信息返回验证密码; 密码验证模块( 12 ),用于验证用户输入的屏幕解锁密码; 检测模块( 18 ),配置为触发电源管理模块( 13 ) 当检测到 SIM 卡或电池已被拔出,或电池电量耗尽超过预设持续时间时; 电源管理模块( 13 ),用于停止移动终端电池供电,启动备用电源为信息回传模块( 14 ),信息删除模块( 15 )、定位模块( 16 ) 和 IMSI; 信息返回模块( 14 ),用于验证接收到的信息返回验证密码,验证成功后返回保存在设定存储区的信息; 信息删除模块( 15 ),配置删除返回的信息; 定位模块( 16 ),用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 还公开了一种移动终端的防盗方法。(String), US13/258287(String), 1276185600(Integer), US8811949B2(String), 1408377600(Integer), 1408377600(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 12(Integer), CN100473194C | CN101026422A | CN101039479A | CN101459721A | CN101568119A | CN101610500A | CN1859670A | US20090093235A1 | US20090270126A1 | US20100009697A1 | US7137003B2 | US8265695B2(String), 8(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.658 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185958(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d41923e087b84179af992fc681d81c14.png(String), 185958(Integer), d41923e087b84179af992fc681d81c14.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Anti-theft mobile terminal and anti-theft method for mobile terminal(String), 移动终端防盗及移动终端防盗方法(String), US8811949B2(String), An anti-theft mobile terminal is disclosed, including: a setting module (10); an encryption module (11), configured to set a screen-lock password and an information return verification password of the mobile terminal; a password verification module (12), configured to verify a screen-unlock password input by a user; a detection module (18), configured to trigger a power management module (13) when detecting that an SIM card or battery has been pulled out, or the battery has run down longer than a preset duration; the power management module (13), configured to stop power supply from the battery of the mobile terminal and start a standby power supply to supply power to an information return module (14), an information deleting module (15), a positioning module (16), and an IMSI; the information return module (14), configured to verify a received information return verification password and return information saved in a set storage area after successful verification; the information deleting module (15), configured to delete the returned information; the positioning module (16), configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. An anti-theft method for mobile terminals is also disclosed.(String), 公开了一种防盗移动终端,包括:设置模块( 10 ); 加密模块( 11 ),用于设置移动终端的锁屏密码和信息返回验证密码; 密码验证模块( 12 ),用于验证用户输入的屏幕解锁密码; 检测模块( 18 ),配置为触发电源管理模块( 13 ) 当检测到 SIM 卡或电池已被拔出,或电池电量耗尽超过预设持续时间时; 电源管理模块( 13 ),用于停止移动终端电池供电,启动备用电源为信息回传模块( 14 ),信息删除模块( 15 )、定位模块( 16 ) 和 IMSI; 信息返回模块( 14 ),用于验证接收到的信息返回验证密码,验证成功后返回保存在设定存储区的信息; 信息删除模块( 15 ),配置删除返回的信息; 定位模块( 16 ),用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 还公开了一种移动终端的防盗方法。(String), US13/258287(String), 1276185600(Integer), US8811949B2(String), 1408377600(Integer), 1408377600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 12(Integer), CN100473194C | CN101026422A | CN101039479A | CN101459721A | CN101568119A | CN101610500A | CN1859670A | US20090093235A1 | US20090270126A1 | US20100009697A1 | US7137003B2 | US8265695B2(String), \20230420\d41923e087b84179af992fc681d81c14.png(String), 8(Integer), 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 1. An anti-theft mobile terminal, comprising: a battery, a setting unit, an encryption module, a password verification module, a detection module, a power management module, an information return module, an information deleting module and a positioning module; whereinthe setting unit is configured to set an International Mobile Subscriber Identity (IMSI) for the mobile terminal;the encryption module is configured to set a screen-lock password and an information return verification password of the mobile terminal;the password verification module is configured to verify a screen-unlock password input by a user, and unlock a screen after successful verification;the detection module is configured to detect a battery or a Subscriber Identity Module (SIM) card of the mobile terminal, and trigger the power management module to manage a power supply when detecting that the SIM card has been pulled out, the battery has been pulled out, or the battery has run down longer than a preset duration;the power management module is configured to stop a power supply function of the battery of the mobile terminal and start a standby power supply to supply power to the information return module, the information deleting module, the positioning module, and the IMSI;the information return module is configured to receive an information return verification password from another mobile terminal, verify the information return verification password, and return information saved in a set storage area in the mobile terminal to the another terminal after successful verification;the information deleting module is configured to delete information having been returned by the information return module from the set storage area; andthe positioning module is configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal;wherein the password verification module is configured to trigger the power management module to manage the power supply when the number of verification attempts exceeds a preset threshold, and is started after the mobile terminal is restarted or powered on again.(String), 1.防盗移动终端,包括:电池、设置单元、加密模块、密码验证模块、检测模块、电源管理模块、信息返回模块、信息删除模块和定位模块;其中设置单元,用于为移动终端设置IMSI;加密模块,用于设置移动终端的锁屏密码和信息返回验证密码;密码验证模块,用于验证用户输入的解锁密码,验证成功后解锁屏幕;检测模块,用于检测移动终端的电池或SIM卡,当检测到SIM卡已拔出、电池已拔出时,触发电源管理模块进行电源管理out,或者电池耗尽的时间超过预设时间;电源管理模块,用于停止移动终端电池的供电功能,启动备用电源为信息返回模块、信息删除模块、定位模块和IMSI供电。信息返回模块,用于接收来自其他移动终端的信息返回验证密码,对信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给其他终端。信息删除模块,用于从设置的存储区中删除信息返回模块返回的信息;和定位模块,用于对移动终端进行定位,并周期性向网络侧或指定的移动终端发送定位信息;其中,密码验证模块用于在验证尝试次数超过预设阈值时触发电源管理模块管理电源,并在移动终端重启或再次上电后启动。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 2. The mobile terminal according to claim 1, further comprising:an SIM card binding module, configured to bind a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refuse to provide a network access service to the non-set SIM card.(String), 2.根据权利要求1所述的移动终端,还包括:SIM卡绑定模块,用于为移动终端绑定设置的SIM卡,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 3. The mobile terminal according to claim 2, wherein the SIM card binding module is further configured to bind the IMSI of the mobile terminal to the set SIM card.(String), 3.根据权利要求2所述的移动终端,其中SIM卡绑定模块还用于将移动终端的IMSI与设置的SIM卡进行绑定。四、一种移动终端防盗方法包括:设置移动终端的锁屏密码和信息返回验证密码;为移动终端设置国际移动用户识别码(IMSI);还包括:接收并验证用户输入的解锁密码,验证成功后解锁移动终端的屏幕;当检测到移动终端SIM卡被拔出、移动终端电池被拔出或电池电量耗尽超过预设时间时,停止移动终端电池供电,启动备用电源,使移动终端进入自动运行状态,以移动终端的IMSI作为通信标识;其中,所述自动运行状态包括:接收来自另一移动终端的信息返回验证密码,并对所述信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给另一终端,并从中删除返回的信息。设定的存储区域;启动移动终端的自动定位功能,周期性地向网络侧或指定的移动终端发送移动终端的当前定位信息;和当移动终端输入验证密码错误且尝试验证次数超过预设阈值时,停止移动终端电池供电,启动备用电源,使移动终端进入自动运行状态;并在移动终端重启或再次上电时自动锁定移动终端的屏幕。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 4. An anti-theft method for a mobile terminal comprising: setting a screen-lock password and an information return verification password of the mobile terminal; and setting an International Mobile Subscriber Identity (IMSI) for the mobile terminal; and further comprising:receiving and verifying a screen-unlock password input by a user, and unlocking a screen of the mobile terminal after successful verification; when detecting that an SIM card of the mobile terminal has been pulled out, a battery of the mobile terminal has been pulled out, or the battery has run down longer than a preset duration, stopping supply of power from the battery of the mobile terminal, starting a standby power supply, enabling the mobile terminal to enter an automatic running state, and using the IMSI of the mobile terminal as a communication identity; wherein the automatic running state comprises: receiving an information return verification password from another mobile terminal and verifying the information return verification password, returning information saved in a set storage area in the mobile terminal to the another terminal after successful verification, and deleting returned information from the set storage area; and starting an automatic positioning function of the mobile terminal and periodically transmitting current positioning information of the mobile terminal to a network side or a specified mobile terminal; andwhen an input verification password is incorrect to the mobile terminal and the number of verification attempts exceeds a preset threshold, stopping supply of power from the battery of the mobile terminal, starting the standby power supply, and enabling the mobile terminal to enter the automatic running state; and automatically locking the screen of the mobile terminal when the mobile terminal is restarted or powered on again.(String), 5.根据权利要求4所述的方法,还包括:将设置的SIM卡与移动终端绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 5. The method according to claim 4, further comprising:binding a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card.(String), 6.根据权利要求4所述的方法,还包括:将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 6. The method according to claim 4, further comprising:binding the IMSI of the mobile terminal to a set SIM card, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card.(String), 7.根据权利要求4所述的方法,还包括:当移动终端中的SIM卡或电池拔出时间超过预设时间时,由移动终端启动备用电源,使移动终端自身进入自动运行状态。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 7. The method according to claim 4, further comprising:starting the standby power supply by the mobile terminal and enabling the mobile terminal itself to enter the automatic running state when the SIM card or the battery in the mobile terminal has been pulled out longer than the preset duration.(String), 8.根据权利要求5所述的方法,还包括:将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。(String), 1(Integer), 6(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:22.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185958(Integer), 8. The method according to claim 5, further comprising:binding the IMSI of the mobile terminal to the set SIM card, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card.(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185958(Integer), TECHNICAL FIELD [0001]The present disclosure relates to anti-theft technologies for mobile terminals, and in particular to an anti-theft mobile terminal and an anti-theft method for a mobile terminal. BACKGROUND [0002]Due to system complexity and application diversity, mobile terminals become like personal computers (PCs) when they are used. Users have become accustomed to storing their important personal information and files in mobile terminals because of portability. This is especially the case for business mobile terminals, which store large amounts of important user information. However, such portability also produces a high risk of losing mobile terminals. A large number of mobile terminal users have experienced such loss. Once a mobile terminal is lost, a user may suffer great economic loss. Therefore, if a mobile terminal is lost, a user would always want to ensure that personal information stored in the mobile terminal is well protected when recovering the lost mobile terminal. However, current mobile terminals obviously do not have this function. [0003]At present, anti-theft methods commonly used for mobile terminals are as follows: [0004]1. using a physical a case is for a mobile terminal: specifically, using a case for a mobile terminal, attaching a chain-like link on the case, and tying the mobile terminal to the user's clothes through the chain-like link to prevent anti-theft; this method can reduce the probability of loss of a terminal, however, once a mobile terminal is lost, a user cannot prevent loss of the user's personal information; [0005]2. arranging a mechanical locking apparatus inside a mobile terminal: a mechanical locking apparatus is placed inside a mobile terminal, wherein, generally, the locking apparatus includes a lock latch, a lock body, a spring, an electromagnetic coil, an iron core, and a locking tongue panel connected to a cell panel; in this method, the locking apparatus is complex in structure and is difficult to implement within the small space of a mobile terminal, meanwhile, the mechanical lock can be easily unlocked by persons skilled in lock-picking, thereby being an ineffective anti-theft mechanism; [0006]3. setting a startup password for a mobile terminal, generally, setting a four-digit PIN code for encryption: such anti-theft method is simple but passwords can be easily cracked, system can be easily reset by using professional cracking software or by refreshing the mobile terminal, therefore, great security risks still exist; and [0007]4. returning related information stored in a mobile terminal through a short message after the mobile terminal is stolen, specifically, returning important information of a user stored in a set storage area, such as an address book, to a new mobile terminal of the user: this method is very effective in returning personal contact information, but has certain limitations, for example, a user cannot implement information return if the mobile terminal is powered off or if a Subscriber Identity Module (SIM) card is replaced. SUMMARY [0008]In view of the above mentioned, the main objective of the present disclosure is to provide an anti-theft mobile terminal and an anti-theft method for a mobile terminal, so that related information in a mobile terminal can be retrieved when the mobile terminal is stolen and the mobile terminal can be accurately positioned. [0009]In order to the above objective, the technical solution of the present disclosure is implemented as follows. [0010]An anti-theft mobile terminal includes a setting unit, an encryption module, a password verification module, a detection module, a power management module, an information return module, an information deleting module, and a positioning module; wherein [0011]the setting unit is configured to set an International Mobile Subscriber Identity (IMSI) for the mobile terminal; [0012]the encryption module is configured to set a screen-lock password and an information return verification password of the mobile terminal; [0013]the password verification module is configured to verify a screen-unlock password input by a user, and unlock a screen after successful verification; [0014]the detection module is configured to detect a battery or an SIM card of the mobile terminal, and trigger the power management module to manage a power supply when detecting that the SIM card has been pulled out, the battery has been pulled out, or the battery has run down longer than a preset duration; [0015]the power management module is configured to stop a power supply function of the battery of the mobile terminal and start a standby power supply to supply power to the information return module, the information deleting module, the positioning module, and the IMSI; [0016]the information return module is configured to receive an information return verification password from another mobile terminal, verify the information return verification password, and return information saved in a set storage area in the mobile terminal to the another terminal after successful verification; [0017]the information deleting module is configured to delete information having been returned by the information return module from the set storage area; and [0018]the positioning module is configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. [0019]Preferably, the mobile terminal may further include: [0020]an SIM card binding module, configured to bind a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refuse to provide a network access service to the non-set SIM card. [0021]Preferably, the SIM card binding module may be further configured to bind the IMSI of the mobile terminal to the set SIM card. [0022]Preferably, the password verification module may be configured to trigger the power management module to manage the power supply when the number of verification attempts exceeds a preset threshold, and is started after the mobile terminal is restarted or powered on again. [0023]Preferably, the power management module may not supply power to the information return module, the information deleting module, the positioning module, and the IMSI when the mobile terminal is powered by the battery normally. [0024]An anti-theft method for a mobile terminal includes: setting a screen-lock password and an information return verification password of a mobile terminal; and setting an IMSI for the mobile terminal; the method further includes:[0025]receiving and verifying a screen-unlock password input by a user, and unlocking a screen of the mobile terminal alter successful verification; when detecting that an SIM card of the mobile terminal has been pulled out, or a battery of the mobile terminal has been pulled out, or the battery has run down longer than a preset duration, stopping supply of power from the battery of the mobile terminal, starting a standby power supply, enabling the mobile terminal to enter an automatic running state, and using the IMSI of the mobile terminal as a communication identity; [0026]wherein the automatic running state comprises: receiving an information return verification password from another mobile terminal and verifying the information return verification password, returning information saved in a set storage area in the mobile terminal to the another terminal after successful verification, and deleting returned information from the set storage area; and starting an automatic positioning function of the mobile terminal and periodically transmitting current positioning information of the mobile terminal to a network side or a specified mobile terminal. [0027]Preferably, the method may further include: [0028]binding a set SIM card to the mobile terminal, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card. [0029]Preferably, the method may further include: [0030]binding the IMSI of the mobile terminal to the set SIM card, and when the mobile terminal uses a non-set SIM card, refusing to provide a network access service to the non-set SIM card. [0031]Preferably, the method may further include: [0032]when an input verification password is incorrect to the mobile terminal and the number of verification attempts exceeds a preset threshold, stopping supply of power from the battery of the mobile terminal, and starting the standby power supply, and enabling the mobile terminal to enter the automatic running state; and automatically locking the screen of the mobile terminal when the mobile terminal is restarted or powered on again. [0033]Preferably, the method may further include: [0034]starting the standby power supply by the mobile terminal and enabling the mobile terminal itself to enter the automatic running state when the SIM card or the battery in the mobile terminal has been pulled out longer than the preset duration. [0035]In the present disclosure, by means of additional arrangement of the IMSI, the password encryption module, the positioning module and the standby power supply in a mobile terminal, when the mobile terminal is stolen or a screen-lock password has been input for many times, the mobile terminal stops its battery from supplying power, starts the standby power supply, and enters the automatic running state, i.e., an anti-theft state. In this case, the standby power supply only supplies power to a module related to the anti-theft state. In this way, the mobile terminal verifies a password requested to be input upon receiving a request for information return from a user who sends this request through another mobile terminal, and sends related information stored in a set storage area to the another mobile terminal after successful verification. Meanwhile, the positioning module of the stolen mobile terminal is started, automatically positions the mobile terminal, and sends positioning information to a network side or a specified mobile terminal. In this way, when a mobile terminal is lost, the lost mobile terminal can be accurately positioned, and can send related information stored in its set storage area to another terminal through which a request for information return is sent, after a user sends a password for information return through the another mobile terminal to the lost mobile terminal. The loss due to loss of a mobile terminal can be greatly reduced by means of the technical solution disclosed in the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure; [0037]FIG. 2 is another structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure; and [0038]FIG. 3 is a flowchart of an anti-theft method for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0039]The basic idea of the present disclosure is that: an IMSI, a password setting module, a positioning module, a standby power supply and the like are arranged in a mobile terminal, so that when the mobile terminal is stolen or a screen-lock password has been input for many times, the mobile terminal stops a mobile terminal battery from supplying power, starts the standby power supply, and enters an automatic running state, i.e., an anti-theft state, in this case, the standby power supply only supplies power to a module related to the anti-theft state. The mobile terminal verifies a password requested to be input after receiving a request for information return which is sent by the user through another mobile terminal, and sends related information stored in a set storage area after successful verification to the mobile terminal which sent the request. Meanwhile, the positioning module of the stolen mobile terminal is started, automatically positions the mobile terminal, and sends positioning information to a network side or a specified mobile terminal. [0040]FIG. 1 is a structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 1, the anti-theft mobile terminal in this embodiment includes: a setting unit 10, an encryption module 11, a password verification module 12, a detection module 18, a power management module 13, an information return module 14, an information deleting module 15, and a positioning module 16. [0041]The setting unit 10 is configured to set an IMSI for the mobile terminal. After the mobile terminal is lost and enters an anti-theft state, the IMSI is started to act as the identity of the lost mobile terminal so as to implement relevant communication with the lost mobile terminal. [0042]The encryption module 11 is configured to set a screen-lock password and an information return verification password of the mobile terminal, wherein the screen-lock password and the information return verification password can be a password whose number of digits is not limited, which may be numeral or character combination, and is set by a user after the mobile terminal is started. The screen-lock password is a password which is required to be input to unlock the screen of the mobile terminal when the user wants to use the mobile terminal. The information return verification password is a password for verifying whether a requester is an authorized user upon a request for information return is received. When the verification password is input correctly, the request for information return is considered valid. [0043]The password verification module 12 is configured to verify a screen-unlock password input by a user, unlock the screen after successful verification, and trigger the power management module to manage a power supply when the number of verification attempts exceeds a preset threshold. Here, the threshold of the number of verification attempts for a screen-unlock password may be set to 6, that is, when a user inputs incorrect screen-unlock password six times consecutively, the mobile terminal enters an automatic running state, i.e., an anti-theft state. When detecting that a battery or an SIM card of the mobile terminal has been pulled out longer than a preset duration, the mobile terminal enters the automatic running state. The preset duration can be one hour, two hours, 24 hours, or a week, and is set by a mobile terminal user. [0044]In the present disclosure, the password verification module 12 is started after the mobile terminal is restarted or powered on again, i.e., after the mobile terminal is restarted or powered on again, the password verification module 12 considers it a normal start and prompts a user to input the screen-unlock password. [0045]The detection module 18 is configured to detect the battery or the SIM card of the mobile terminal, and trigger the power management module 13 to manage the power supply when detecting that the SIM card has been pulled out, the battery has been pulled out, or the battery has run down longer than a preset duration. The detection module 18 is configured to prevent the user from being unable to communicate with and find the lost mobile terminal in the case where a thief pulls out the SIM card or battery, or powers off the stolen mobile terminal. To overcome this defect of existing mobile terminals, the detection module 18 is arranged for the mobile terminal in the present disclosure to start a standby power supply automatically to enable the mobile terminal enter the anti-theft state when detecting that the battery of the mobile terminal has run down longer than the preset duration or the SIM card has been pulled out longer than the preset duration. The preset duration can be set as 30 minutes, 20 minutes, or one day. [0046]The power management module 13 is configured to stop power supply from the battery and start a standby power supply to supply power to the information return module 14, the information deleting module 15, the positioning module 16, and the IMSI; that is to say, when determining that the number of verification attempts for a screen-unlock password input by a user exceeds the preset threshold, the battery of the mobile terminal is automatically cut off and no power is supplied to corresponding processing units, then, the mobile terminal enters a power-off state like existing mobile terminals does. In the present disclosure, the standby power supply is connected to the battery of the mobile terminal, charged by the battery of the mobile terminal when the mobile terminal is working normally, and supplies power to relevant modules in the anti-theft state in the mobile terminal once the battery of the mobile terminal stops working, so that the anti-theft function of the mobile terminal can be implemented. Detailed description is given below on how the mobile terminal implements the anti-theft function according to the present disclosure. [0047]The power management module 13 does not supply power to the information return module 14, information deleting module 15, positioning module 16 and the IMSI when the mobile terminal is powered by the battery normally. [0048]The information return module 14 is configured to receive and verify the information return verification password, and return information saved in a set storage area in the mobile terminal to another terminal when verification succeeds. When a user confirms that his/her mobile terminal is lost, the user can send a request for information return to the lost mobile terminal using any other mobile terminal; specifically, the request is sent to the lost mobile terminal through a short message, the content of which is the information return verification password set by the user before the mobile terminal is lost. After the lost mobile terminal starts an automatic running mode, the lost mobile terminal, once upon receiving the short message, takes the message as the information return verification password by default, extracts the content from the short message and compares the content with the information return verification password stored in the lost mobile terminal; if they are consistent, the lost mobile terminal automatically sends related information stored in the set storage area in the lost mobile terminal to the terminal who sent the request. Specifically, the above set storage area may be an address book storage area, a short message storage area, or a user personal information storage area, etc. [0049]Since the lost mobile terminal has entered the anti-theft state, the SIM card in the mobile terminal does not work any longer. Therefore, in order to enable the request for information return to be responded by the lost mobile terminal, an IMSI set for the lost mobile terminal is required to be used as an identity, that is, the mobile terminal is located in a network environment supporting the IMSI and can receive a short message and the like from any other mobile terminal. [0050]The information deleting module 15 is configured to delete information having been returned by the information return module 14 from the set storage area. When the information return module 14 returns related information stored in the set storage area to another mobile terminal, the information deleting module 15 deletes the information. In this way, even though the screen-lock password set for the lost mobile terminal is cracked, the information cannot be obtained, which effectively protects privacy of the mobile terminal user. [0051]The positioning module 16 is configured to position the mobile terminal, and periodically transmit positioning information to a network side or a specified mobile terminal. In the present disclosure, the positioning module 16 can be implemented by a Global Positioning System (GPS) or an equivalent processor. The GPS positioning function can be simply implemented on a mobile terminal. In the present disclosure, the positioning module 16 can be also a Geographic Information System (GIS) positioning instrument, and specifically, determines location information of the mobile terminal according to base station location information reported by the mobile terminal to a network side, an angle at which a signal is transmitted from the mobile terminal to the base station and power of the signal. In the present disclosure, when the positioning module 16 is started, it automatically positions the mobile terminal and reports positioning information to a network side or a specified mobile terminal. In this way, once the mobile terminal is lost, current positioning information of the lost mobile terminal can be provided to a relevant person, thus giving the person a clue to finding of the lost mobile terminal. [0052]FIG. 2 is another structure schematic diagram of an anti-theft mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 2, based on the terminal illustrated in FIG. 1, the anti-theft mobile terminal further includes: [0053]an SIM card binding module 17, configured to bind a set SIM card to the mobile terminal, and refuse to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card; wherein the function of the SIM card binding module 17 can be set by a user, for example, when the user selects the function of binding the current mobile terminal to the current inserted SIM card, the mobile terminal enables the binding function. With this function enabled, the mobile terminal does not support any other SIM card except its bound SIM card unless a binding relationship is set between the mobile terminal and other SIM card. [0054]Or the SIM card binding module is further configured to bind the IMSI to the set SIM card, and refuse to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card. The principle of binding the IMSI to the SIM card is the same as that of binding the SIM card to the mobile terminal. [0055]FIG. 3 is a flowchart of an anti-theft method for a mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 3, the method includes the following steps: [0056]step 301: a screen-lock password and an information return verification password of the mobile terminal are set; and an IMSI is set for the mobile terminal; [0057]in this step, after the mobile terminal enters a normal running state, the screen-lock password and the information return verification password are set through corresponding setting functions, wherein these passwords are set by a user, and can be numeral or/and character combination. Setting the IMSI is equivalent to setting another network access mode for the mobile terminal; this mode is not started when the mobile terminal is working normally but started when the mobile terminal enters the anti-theft state. That is to say, the mobile terminal according to the present disclosure supports a multi-mode function, however, during actual working, only a single mode, either a network function supported by the IMSI (in the anti-theft state) or a network function supported by the SIM card (in normal working), can be enabled; [0058]step 302: after the screen of the mobile terminal is locked, a screen-unlock password input by the user is received and verified, and the screen is unlocked when the password verification is successful; if the input password is incorrect and the number of verification attempts exceeds a preset threshold, a battery of the mobile terminal stops supplying power, a standby power supply is started and the mobile terminal enters an automatic running state, further, the IMSI of the mobile terminal is used as a communication identity; here, the mobile terminal enters the automatic running state, i.e. it enters the anti-theft state; [0059]when the number of times of inputting an incorrect screen-lock password exceeds the preset threshold, the mobile terminal automatically enters the anti-theft state, at this moment, the mobile terminal appears to be powered off, disables the network function supported by the SIM card but enables the network function supported by the IMSI set in the mobile terminal. In fact, at this moment, the mobile terminal, with the help of the standby power supply, still supports a network communication function, which is, however, not controlled by a user. [0060]It should be noted that when the SIM card or battery of the mobile terminal has been pulled out or the battery has been unable to supply power because of shutdown or battery faults or other reasons longer than a preset duration, the mobile terminal also enters the automatic running state, i.e., the anti-theft state. The preset duration can be set as 30 minutes, 20 minutes, or one day. [0061]The automatic running state here includes: receiving an information return verification password from another mobile terminal and verifying the password, returning information saved in a set storage area in the mobile terminal to the another terminal after successful verification, and deleting information, which has been returned by the information return module, from the set storage area; and starting an automatic positioning function of the mobile terminal and periodically transmitting current positioning information of the mobile terminal to a network side or a specified mobile terminal. [0062]In the present disclosure, besides the above-mentioned step 301 and step 302, the anti-theft method further includes: binding the SIM card to the mobile terminal, and refusing to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card. The above function can be set by a user, for example, when the user selects the function of binding the current mobile terminal to the current inserted SIM card, the mobile terminal enables the binding function, thus, the mobile terminal does not support any other SIM card any longer except this SIM card inserted in the mobile terminal unless a binding relationship is additionally set between the mobile terminal and other SIM card. [0063]Or the anti-theft method further includes: binding the IMSI of the mobile terminal to the set SIM card, and refusing to provide a network access service to a non-set SIM card when the mobile terminal uses the non-set SIM card. Binding of the IMSI to the set SIM card and binding of the mobile terminal to the set SIM card are the same, which is not detailed here again. [0064]To prevent the mobile terminal from entering the anti-theft state in stead of the normal state due to an operation mistake or a failure in memorizing a password, the mobile terminal according to the present disclosure automatically locks its screen after being restarted and powered-on again, i.e., it automatically enters a screen-lock state after being started or powered on again, and can enter a normal working state after the user inputs a correct screen-unlock password. [0065]The above are only preferred embodiments of the present disclosure, and not intended to limit the protection scope of the present disclosure.(String), 技术领域 [0001] 本发明涉及移动终端防盗技术,尤其涉及一种移动终端防盗及移动终端防盗方法。 背景 [0002] 由于系统的复杂性和应用的多样性,移动终端在使用时变得像个人电脑(Personal Computer,PC)。 由于便携性的原因,用户已经习惯于将重要的个人信息和文件存储在移动终端中。 尤其是商务移动终端,存储了大量重要的用户信息。 然而,这种便携性也产生了丢失移动终端的高风险。 大量的移动终端用户都曾经历过这样的流失。 一旦移动终端丢失,用户可能会遭受很大的经济损失。 因此,如果移动终端丢失,用户在找回丢失的移动终端时,总是希望能够保证移动终端中存储的个人信息得到很好的保护。 但是,目前的移动终端显然没有这个功能。 [0003] 目前,移动终端常用的防盗方法有以下几种: [0004] 1、移动终端使用实体外壳:具体为移动终端使用外壳,在外壳上附上链条,通过链条将移动终端系在用户的衣服上,以防 防小偷; 这种方法可以降低终端丢失的概率,但是一旦移动终端丢失,用户就无法避免用户个人信息的丢失。 [0005] 2、在移动终端内部设置机械锁紧装置:在移动终端内部设置机械锁紧装置,通常,锁紧装置包括锁舌、锁体、弹簧、电磁线圈、铁芯, 与电池板连接的锁舌板; 该方法中,锁定装置结构复杂,难以在移动终端的狭小空间内实现,同时机械锁很容易被开锁技术人员解锁,防盗效果不佳。 ; [0006] 3、为移动终端设置开机密码,一般设置一个四位PIN码进行加密:这种防盗方法简单,但密码容易被破解,使用专业破解软件或刷新即可轻松重置系统 因此,移动终端仍然存在很大的安全隐患; 和 [0007] 4、移动终端被盗后通过短信返回移动终端中存储的相关信息,具体为将存储在设定存储区域中的用户重要信息,如通讯录返回给用户的新移动终端。 :这种方法在返回个人联系信息方面非常有效,但是有一定的局限性,例如,如果移动终端关机或更换SIM卡,用户将无法实现信息返回。 概括 [0008] 鉴于以上所述,本发明的主要目的在于提供一种移动终端防盗及移动终端防盗方法,使得移动终端在被盗时能够检索到移动终端中的相关信息。 被盗,移动终端可以准确定位。 [0009] 为实现上述目的,本发明的技术方案是通过以下方式实现的。 [0010] 一种移动防盗终端,包括设置单元、加密模块、密码验证模块、检测模块、电源管理模块、信息返回模块、信息删除模块和定位模块; 其中 [0011] 设置单元,用于为移动终端设置IMSI; [0012] 加密模块,用于设置移动终端的锁屏密码和信息返回验证密码; [0013] 密码验证模块,用于验证用户输入的解锁密码,验证成功后解锁屏幕; [0014]检测模块用于检测移动终端的电池或SIM卡,当检测到SIM卡已拔出、电池已拔出或电池已拔出时,触发电源管理模块进行电源管理。 耗尽时间超过预设持续时间; [0015] 电源管理模块,用于停止移动终端电池的供电功能,启动备用电源为信息返回模块、信息删除模块、定位模块和IMSI供电。 [0016] 信息返回模块,用于接收来自其他移动终端的信息返回验证密码,对信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给其他终端。 [0017] 信息删除模块,用于从设置的存储区中删除信息返回模块返回的信息; 和 [0018] 定位模块,用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 [0019] 优选地,所述移动终端还可以包括: [0020] SIM卡绑定模块,用于为移动终端绑定设置的SIM卡,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 [0021] 优选地,SIM卡绑定模块还用于将移动终端的IMSI与设置的SIM卡进行绑定。 [0022] 优选地,密码验证模块可以用于在验证尝试次数超过预设阈值时触发电源管理模块管理电源,并在移动终端重启或重新上电后启动。 [0023] 优选地,当移动终端由电池正常供电时,电源管理模块可以不向信息返回模块、信息删除模块、定位模块和IMSI供电。 [0024] 一种移动终端防盗方法,包括:设置移动终端的锁屏密码和信息返回验证密码; 为移动终端设置IMSI; 该方法还包括: [0025]接收并验证用户输入的锁屏密码,验证成功后解锁移动终端屏幕; 当检测到移动终端SIM卡被拔出,或移动终端电池被拔出,或电池电量耗尽超过预设时间时,停止移动终端电池供电 、启动备用电源,使移动终端进入自动运行状态,以移动终端的IMSI作为通信标识; [0026] 其中,所述自动运行状态包括:接收来自另一移动终端的信息返回验证密码,并对所述信息返回验证密码进行验证,验证成功后将移动终端中设置的存储区域中保存的信息返回给另一终端,并从中删除返回的信息。 设定的存储区域; 启动移动终端的自动定位功能,周期性地向网络侧或指定移动终端发送移动终端当前的定位信息。 [0027] 优选地,该方法还可以包括: [0028] 将设置的SIM卡与移动终端绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 [0029] 优选地,该方法还可以包括: [0030] 将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 [0031] 优选地,该方法还可以包括: [0032] 当移动终端输入验证密码错误且尝试验证次数超过预设阈值时,停止移动终端电池供电,启动备用电源,使移动终端进入自动模式 运行状态; 并在移动终端重启或再次上电时自动锁定移动终端的屏幕。 [0033] 优选地,该方法还可以包括: [0034]当移动终端中的SIM卡或电池拔出时间超过预设时间时,由移动终端启动备用电源,使移动终端自身进入自动运行状态。 [0035] 本发明通过在移动终端中增设IMSI、密码加密模块、定位模块和备用电源,当移动终端被盗或多次输入锁屏密码时 ,移动终端停止电池供电,启动备用电源,进入自动运行状态,即防盗状态。 此时,备用电源只为与防盗状态相关的模块供电。 这样,移动终端在接收到用户通过其他移动终端发送信息返回请求后,对要求输入的密码进行验证,成功后将存储在设置的存储区中的相关信息发送给其他移动终端。 确认。 同时启动被盗移动终端的定位模块,自动对移动终端进行定位,并向网络侧或指定移动终端发送定位信息。 这样,当移动终端丢失时,可以准确定位丢失的移动终端,并在用户发送密码后,将其设置的存储区域中存储的相关信息发送给另一个终端,通过该终端发送信息返回请求。 用于通过另一移动终端向丢失的移动终端返回信息。 通过本发明公开的技术方案,可以大大减少因移动终端丢失而造成的损失。 附图的简要说明 [0036] 图1为本发明实施例提供的一种移动防盗终端的结构示意图; [0037] 图2为本发明实施例提供的一种移动防盗终端的另一种结构示意图; 和 [0038] 图3为本发明实施例提供的一种移动终端防盗方法的流程图。 详细说明 [0039] 本发明的基本思想是:在移动终端中设置IMSI、密码设置模块、定位模块、备用电源等,以便在移动终端被盗或锁屏密码时 多次输入后,移动终端停止移动终端电池供电,启动备用电源,进入自动运行状态,即防盗状态,此时备用电源只供电 给与防盗状态相关的模块供电。 移动终端在接收到用户通过其他移动终端发送的信息返回请求后,对请求输入的密码进行验证,将验证成功后存储在设置的存储区中的相关信息发送给发送请求的移动终端。 同时启动被盗移动终端的定位模块,自动对移动终端进行定位,并向网络侧或指定移动终端发送定位信息。 [0040] 图1为本发明实施例提供的一种移动防盗终端的结构示意图。 如图1所示,本实施例的移动防盗终端,包括: 设置单元 10 , 一个加密模块 11 , 密码验证模块 12 , 检测模块 18 , 电源管理模块 13 , 信息返回模块 14 ,信息删除模块 15 , 和一个定位模块 16 . [0041] 设定单位 10 用于为移动终端设置IMSI。 当移动终端丢失进入防盗状态后,启动IMSI作为丢失移动终端的标识,与丢失移动终端进行相关通信。 [0042] 加密模块 11用于设置移动终端的锁屏密码和信息返回验证密码,其中,屏幕锁定密码和信息返回验证密码可以是不限位数的密码,可以是数字或字符。 组合,由用户在移动终端启动后设置。 锁屏密码是用户在使用移动终端时解锁移动终端屏幕所需要输入的密码。 信息返回验证密码是在接收到信息返回请求时验证请求者是否为授权用户的密码。 当验证密码输入正确时,信息返回请求被视为有效。 [0043] 密码验证模块 12 用于验证用户输入的屏幕解锁密码,验证成功后解锁屏幕,当验证次数超过预设阈值时,触发电源管理模块对电源进行管理。 这里,可以将锁屏密码的验证尝试次数阈值设置为6,即当用户连续6次输入错误的锁屏密码时,移动终端进入自动运行状态,即 防盗状态。 当检测到移动终端的电池或SIM卡被拔出时间超过预设时间时,移动终端进入自动运行状态。 预设时长可以为1小时、2小时、24小时或一周,由移动终端用户设置。 [0044] 在本发明中,密码验证模块 12 密码验证模块在移动终端重启或重新上电后启动,即移动终端重新启动或重新上电后,密码验证模块 12 认为是正常启动,提示用户输入锁屏密码。 [0045] 检测模块 18 用于检测移动终端的电池或SIM卡,并触发电源管理模块 13 当检测到SIM卡被拔出、电池被拔出或电池电量耗尽超过预设时间时,进行电源管理。 检测模块 18 用于防止在小偷拔出SIM卡或电池,或将被盗移动终端关机等情况下,用户无法与丢失的移动终端通信,无法找到丢失的移动终端。 为了克服现有移动终端的这一缺陷,检测模块 18 本发明的移动终端设置为当检测到移动终端电池电量耗尽超过预设时长或SIM卡失灵时,自动启动待机电源使移动终端进入防盗状态。 被拔出的时间超过预设时间。 预设持续时间可以设置为 30 分钟、20 分钟或一天。 [0046] 电源管理模块 13 设置为停止电池供电,启动备用电源给信息返回模块供电 14 ,信息删除模块 15 , 定位模块 16 , 和 IMSI; 也就是说,当判断用户输入的锁屏密码验证次数超过预设阈值时,移动终端的电池自动断电,不给相应的处理单元供电,则, 移动终端与现有移动终端一样进入关机状态。 本发明中,备用电源连接移动终端的电池,在移动终端正常工作时由移动终端的电池充电,并在防盗状态下为手机中的相关模块供电。 一旦移动终端的电池停止工作,终端可以实现移动终端的防盗功能。 下面详细说明移动终端如何实现本发明的防盗功能。 [0047] 电源管理模块 13 不给信息返回模块供电 14一、信息删除模块 15 , 定位模块 16 以及移动终端正常由电池供电时的IMSI。 [0048] 信息反馈模块 14 用于接收并验证信息返回验证密码,验证成功时,将移动终端中设置的存储区域中保存的信息返回给其他终端。 当用户确认自己的移动终端丢失后,用户可以使用其他任何移动终端向丢失的移动终端发送信息找回请求; 具体地,通过短信向丢失的移动终端发送请求,短信内容为用户在移动终端丢失前设置的信息返还验证密码。 丢失的移动终端启动自动运行模式后,丢失的移动终端一旦收到短信,默认将该短信作为信息返回验证密码,提取短信内容,与信息返回进行比对 遗失移动终端中保存的验证密码; 如果一致,则丢失的移动终端自动将丢失移动终端中设置的存储区域中存储的相关信息发送给发送请求的终端。 具体的,上述设置的存储区可以为通讯录存储区、短信存储区或用户个人信息存储区等。 [0049] 由于丢失的移动终端已经进入防盗状态,移动终端中的SIM卡不再工作。 因此,为了使丢失的移动终端响应信息返回请求,需要使用为丢失的移动终端设置的IMSI作为标识,即移动终端所处的网络环境支持 IMSI,可以接收来自任何其他移动终端的短消息等。 [0050] 信息删除模块 15 用于删除信息返回模块返回的信息 14 从设定的存储区。 当信息返回模块 14 将设置的存储区中存储的相关信息返回给另一移动终端,信息删除模块 15 删除信息。 这样即使为丢失的移动终端设置的锁屏密码被破解,也无法获取信息,有效保护了移动终端用户的隐私。 [0051] 定位模块 16 用于对移动终端进行定位,并周期性地向网络侧或指定的移动终端发送定位信息。 在本发明中,定位模块 16 可以通过全球定位系统 (GPS) 或等效处理器来实现。 GPS定位功能可以简单地在移动终端上实现。 在本发明中,定位模块 16 也可以是地理信息系统(GIS)定位仪,具体地,根据移动终端向网络侧上报的基站位置信息、移动终端发射信号的角度等,确定移动终端的位置信息 终端到基站和信号功率。 在本发明中,当定位模块 16 启动后,自动对移动终端进行定位,并将定位信息上报给网络侧或指定的移动终端。 这样,一旦移动终端丢失,就可以将丢失的移动终端当前的定位信息提供给相关人员,从而为相关人员寻找丢失的移动终端提供线索。 [0052] 图2为本发明实施例提供的一种移动防盗终端的另一种结构示意图。 如图2所示,该移动防盗终端在图1所示终端的基础上,还包括: [0053] SIM卡绑定模块 17 ,用于将设置的SIM卡绑定到移动终端,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供网络接入服务; 其中SIM卡绑定模块的功能 17可以由用户设置,例如,当用户选择绑定当前移动终端和当前插入的SIM卡的功能时,移动终端开启绑定功能。 启用该功能后,除非移动终端与其他SIM卡建立绑定关系,否则移动终端不支持除自身绑定的SIM卡外的其他任何SIM卡。 [0054] 或者,SIM卡绑定模块,还用于将IMSI绑定到设置的SIM卡上,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供网络接入服务。 IMSI与SIM卡的绑定原理与SIM卡与移动终端的绑定原理相同。 [0055] 图3为本发明实施例提供的一种移动终端防盗方法的流程图。 如图3所示,该方法包括以下步骤: [0056] 步 301 :设置移动终端的锁屏密码和信息返回验证密码; 为移动终端设置IMSI; [0057] 本步骤中,移动终端进入正常运行状态后,通过相应的设置功能设置锁屏密码和信息返回验证密码,这些密码由用户设置,可以是数字或/和字符的组合 . 设置IMSI相当于为移动终端设置了另一种网络接入方式; 该模式在移动终端正常工作时不启动,在移动终端进入防盗状态时启动。 也就是说,本发明的移动终端支持多模功能,但在实际工作中,只有一种模式,要么是IMSI支持的网络功能(防盗状态下),要么是网络 SIM卡支持的功能(正常工作时),可以启用; [0058] 步 302 :移动终端锁屏后,接收并验证用户输入的解锁密码,验证成功后解锁屏幕; 如果输入的密码错误,且尝试验证的次数超过预设阈值,则移动终端的电池停止供电,启动备用电源,移动终端进入自动运行状态,进一步,移动终端的IMSI 终端作为通信标识; 此时,移动终端进入自动运行状态,即进入防盗状态; [0059] 当锁屏密码输入错误次数超过预设阈值时,移动终端自动进入防盗状态,此时移动终端呈现关机状态,禁用SIM支持的网络功能 卡,但启用移动终端设置的IMSI支持的网络功能。 实际上,此时移动终端借助于备用电源,仍然支持网络通信功能,但不受用户控制。 [0060] 需要注意的是,当移动终端的SIM卡或电池被拔出或电池因关机或电池故障等原因超过预设时间无法供电时,移动终端也会进入自动关机状态。 运行状态,即防盗状态。 预设持续时间可以设置为 30 分钟、20 分钟或一天。 [0061] 这里的自动运行状态包括:接收到另一移动终端的信息返回验证密码并验证密码,验证成功后将保存在移动终端中设置的存储区域中的信息返回给另一终端,并删除已返回的信息 由信息返回模块,从设定的存储区中获取; 启动移动终端的自动定位功能,周期性地向网络侧或指定移动终端发送移动终端当前的定位信息。 [0062] 在本发明中,除了上述步骤外 301 和步骤 302,该防盗方法还包括:将SIM卡与移动终端绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 上述功能可以由用户设置,例如当用户选择绑定当前移动终端与当前插入的SIM卡的功能时,移动终端开启绑定功能,则移动终端不支持任何其他功能 除非移动终端与其他SIM卡另外设置绑定关系,否则移动终端中不再插入此SIM卡以外的SIM卡。 [0063] 或者,该防盗方法还包括:将移动终端的IMSI与设置的SIM卡绑定,当移动终端使用非设置的SIM卡时,拒绝为非设置的SIM卡提供入网服务。 IMSI与设置的SIM卡的绑定与移动终端与设置的SIM卡的绑定相同,此处不再赘述。 [0064] 为防止移动终端因操作失误或密码记忆失败而进入防盗状态而不是正常状态,本发明的移动终端在重启开机后自动锁屏。 再次,即开机或再次上电后自动进入锁屏状态,用户输入正确的锁屏密码后即可进入正常工作状态。 [0065] 以上所述仅为本发明的优选实施例而已,并不用于限定本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101772018A(String), CN101772018B(String), EP2503806A1(String), EP2503806A4(String), EP2503806B1(String), US20120244839A1(String), US8811949B2(String), WO2011088652A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101772018A(String), CN101772018B(String), EP2503806A1(String), EP2503806A4(String), EP2503806B1(String), US20120244839A1(String), US8811949B2(String), WO2011088652A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101772018A(String), CN101772018B(String), EP2503806A1(String), EP2503806A4(String), EP2503806B1(String), US20120244839A1(String), US8811949B2(String), WO2011088652A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), CN101772018A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271089(Integer), CN101772018B(String), 1047934(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), EP2503806A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), EP2503806A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), EP2503806B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), US20120244839A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), US8811949B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271089(Integer), WO2011088652A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101772018B(String), CN101772018B(String), 1459267200(Integer), 271089(Integer), 185373(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185958(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185958(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185958(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185958(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:23.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185958(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.240 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9621802B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US9621802B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US14/735625(String), 1433865600(Integer), US9621802B2(String), 1491840000(Integer), 1491840000(Integer), 美国(String), 4(Integer), 8(Integer), 36(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130229529A1 | US20140168356A1 | US20140210940A1 | US20140375760A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185959(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c035982275854df09fc3ec625e291340.png(String), 185959(Integer), c035982275854df09fc3ec625e291340.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US9621802B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US14/735625(String), 1433865600(Integer), US9621802B2(String), 1491840000(Integer), 1491840000(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 36(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130229529A1 | US20140168356A1 | US20140210940A1 | US20140375760A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2(String), \20230420\c035982275854df09fc3ec625e291340.png(String), 20(Integer), 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 1. A method for presenting a panoramic photo in a mobile terminal, comprising:detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, wherein the immersive browsing mode is a browsing mode in which the panoramic photo moves as the mobile terminal rotates;detecting and determining a rotation angle of the mobile terminal when the trigger instruction is detected;calculating a minimum displacement of the panoramic photo according to a preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; andmoving and presenting, according to the rotation angle and the minimum displacement, the panoramic photo that is displayed in a normal mode in the mobile terminal, andwherein the panoramic photo is moved for the minimum displacement along a direction opposite to a rotation direction of the mobile terminal.(String), 1.移动终端,包括:输入设备;传感器;处理器耦合到输入装置和传感器;和显示屏耦合到处理器,其中,输入设备用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,其中,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,其中,传感器用于检测移动终端的旋转角度,其中,处理器用于根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、全景照片沿旋转方向的照片宽度,确定全景照片的最小位移。移动端拍摄全景照片时,其中,处理器用于在检测到输入设备输入触发指令时,根据旋转角度和最小位移移动移动终端中以正常模式呈现的全景照片,其中,处理器用于将全景照片沿与移动终端的旋转方向相反的方向移动最小位移,以及其中,显示屏用于呈现全景照片。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 2. The method according to claim 1, wherein determining the rotation angle of the mobile terminal comprises:determining a placement direction in which the mobile terminal is located in a rotation process; anddetermining the rotation angle of the mobile terminal according to the placement direction.(String), 12.根据权利要求11所述的移动终端,其中传感器配置为:确定移动终端在旋转过程中所处的放置方向;和根据放置方向确定移动终端的旋转角度。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 3. The method according to claim 2, wherein determining the placement direction in which the mobile terminal is located in the rotation process comprises:detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, wherein the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and wherein a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located; anddetermining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process.(String), 13.根据权利要求12所述的移动终端,其中传感器用于通过以下方式确定移动终端在旋转过程中所处的放置方向:检测移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,其中参考三维坐标系的X-Y平面平行于屏幕所在的平面移动终端的屏幕所在平面,其中参考三维坐标系的Z轴垂直于移动终端屏幕所在的平面。和根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端在旋转过程中所处的放置方向。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 4. The method according to claim 3, wherein determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process comprises:determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees; anddetermining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees.(String), 14.根据权利要求12所述的移动终端,其中传感器,用于根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角,确定如下方式,其中,所述放置方向为:移动端位于轮换过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角为时,确定移动终端在旋转过程中所处的放置方向为竖直放置方向不大于45度;和当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角为时,确定移动终端在旋转过程中所处的放置方向为水平放置方向大于45度。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 5. The method according to claim 3, wherein determining the rotation angle of the mobile terminal according to the placement direction comprises:using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 15.根据权利要求13所述的移动终端,其中传感器用于根据放置方向,通过以下方式确定移动终端的旋转角度:当确定移动终端在旋转过程中所处的放置方向为a时,将参考三维坐标系中Z轴的方向作为移动终端在旋转过程中对应的轴向水平放置方向;和将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 6. The method according to claim 3, wherein determining the rotation angle of the mobile terminal according to the placement direction comprises:using one of a direction of an X-axis and a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 16.根据权利要求13所述的移动终端,其中传感器用于根据放置方向,通过以下方式确定移动终端的旋转角度:当确定放置方向为旋转过程时,将参考三维坐标系中的X轴方向和Y轴方向之一作为移动终端对应的轴向方向。移动端在旋转过程中定位为竖直放置方向;和将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。(String), 1(Integer), 5(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 7. The method according to claim 1, wherein before moving, according to the rotation angle, the panoramic photo that is displayed in the normal mode in the mobile terminal, further comprises determining that the rotation angle of the mobile terminal reaches the preset rotation angle threshold.(String), 17.根据权利要求11所述的移动终端,其中处理器,还用于确定移动终端的旋转角度达到预设的旋转角度阈值后,根据旋转角度移动终端中正常模式下呈现的全景照片。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 8. The method according to claim 1, wherein before detecting and determining the rotation angle of the mobile terminal, the method further comprises providing prompt information that is used to instruct to rotate the mobile terminal.(String), 18.根据权利要求11所述的移动终端,其中处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 9. The method according to claim 8, wherein before providing the prompt information that is used to instruct to rotate the mobile terminal, the method further comprises acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and wherein providing the prompt information that is used to instruct to rotate the mobile terminal comprises providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction.(String), 19.根据权利要求18所述的移动终端,其中处理器还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,其中,处理器具体用于提供,以下方式,根据获取的旋转方向,提供用于指示旋转移动终端的提示信息,用于指示旋转移动终端的提示信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 10. The method according to claim 1, wherein the minimum displacement is calculated according to an equation:s=d⁢φ1φ2,wherein s is the minimum displacement, d is the width of the panoramic photo, φ1 is the preset rotation angle threshold, and wherein φ2 is the rotation angle of the mobile terminal when the panoramic photo is photographed.(String), 20.根据权利要求11所述的移动终端,其中最小位移根据以下公式计算:s=d⁢φ1φ2,其中s为最小位移,d为全景照片的宽度,φ1为预设旋转角度阈值,其中φ2为拍摄全景照片时移动端的旋转角度。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 11. A mobile terminal, comprising:an input device;a sensor;a processor coupled to the input device and the sensor; anda display screen coupled to the processor,wherein the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode,wherein the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates,wherein the sensor is configured to detect a rotation angle of the mobile terminal,wherein the processor is configured to determine a minimum displacement of the panoramic photo according to a preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed,wherein the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle and the minimum displacement, the panoramic photo that is presented in a normal mode in the mobile terminal,wherein the processor is configured to move the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal, andwherein the display screen is configured to present the panoramic photo.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 12. The mobile terminal according to claim 11, wherein the sensor is configured to:determine a placement direction in which the mobile terminal is located in a rotation process; anddetermine the rotation angle of the mobile terminal according to the placement direction.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 13. The mobile terminal according to claim 12, wherein the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process:detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, wherein the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and wherein a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located; anddetermining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 14. The mobile terminal according to claim 12, wherein the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, and wherein the placement direction in which the mobile terminal is located in the rotation process:determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees; anddetermining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees.(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 15. The mobile terminal according to claim 13, wherein the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction:using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 16. The mobile terminal according to claim 13, wherein the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction:using one of a direction of an X-axis and a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process when it is determined that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; andusing an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal.(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 17. The mobile terminal according to claim 11, wherein the processor is further configured to determine that the rotation angle of the mobile terminal reaches the preset rotation angle threshold before moving, according to the rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal.(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 18. The mobile terminal according to claim 11, wherein the processor is further configured to provide prompt information that is used to instruct to rotate the mobile terminal when it is detected that the trigger instruction is input by the input device.(String), 1(Integer), 17(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 19. The mobile terminal according to claim 18, wherein the processor is further configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed before providing the prompt information that is used to instruct to rotate the mobile terminal, and wherein the processor is specifically configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal by providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction.(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:24.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185959(Integer), 20. The mobile terminal according to claim 11, wherein the minimum displacement is calculated according to an equation:s=d⁢φ1φ2,wherein s is the minimum displacement, d is the width of the panoramic photo, φ1 is the preset rotation angle threshold, and wherein φ2 is the rotation angle of the mobile terminal when the panoramic photo is photographed.(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.295 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.295 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185959(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a continuation of International Application No. PCT/CN2014/079950, filed on Jun. 16, 2014, which is incorporated herein by reference in its entirety. TECHNICAL FIELD [0002]The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present invention provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is specifically configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is specifically configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is specifically configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is specifically configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is specifically configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is specifically configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is specifically configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is specifically configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is specifically configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is specifically configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is specifically configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present invention, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present invention. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present invention. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present invention. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present invention. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present invention. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present invention. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present invention. [0046]FIG. 10A to FIG. 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. The described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present invention, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present invention, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. The method may be performed by a mobile terminal, or specifically by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps: [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present invention, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present invention, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. By using the present invention, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present invention, there may be multiple implementation manners for specifically implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present invention in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present invention. The method may be performed by a mobile terminal, or specifically by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps: [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present invention, a user may input, by using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present invention, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present invention, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present invention, in order to implement immersive mode browsing, the user needs to rotate the mobile terminal, so that the panoramic photo can move as the mobile terminal rotates. Generally, for better browsing of the panoramic photo, the prompt information t(String), 相关申请的交叉引用 [0001] 本申请是 2014 年 6 月 16 日提交的国际申请号 PCT/CN2014/079950 的延续,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及通信技术领域,尤其涉及一种全景照片在移动终端中的呈现方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,移动终端的使用范围和环境也越来越多样化。 例如,目前很多移动终端,如手机、个人数字助理、个人电脑等都具有全景拍摄的功能。 [0004] 当移动终端进行全景拍摄时,用户旋转移动终端拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 然后可以将多张拍摄的照片按照上述的拼接原理拼接成一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,会在全景照片上浏览到比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端中呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作较为复杂。 概括 [0006] 本发明实施例提供一种全景照片在移动终端中的呈现方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 第一方面,提供了一种全景照片在移动终端中的呈现方法,包括:检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为浏览模式。 其中全景照片随着移动终端的旋转而移动,若检测到触发指令,则检测并确定移动终端的旋转角度,根据确定的旋转角度移动呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实现方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009] 结合第一方面的第一种实现方式,在第二种实现方式中,所述确定移动终端在旋转过程中所处的放置方向包括检测移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考的Z轴 三维坐标系垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于参考三维X-Y平面方向的夹角确定- 维度坐标系,移动终端在旋转过程中所处的放置方向。 [0010]结合第一方面的第二种实现方式,在第三种实现方式中,所述根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为竖直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0011] 结合第一方面的第二种实现方式或第一方面的第三种实现方式,在第四种实现方式中,所述根据放置方向确定移动终端的旋转角度包括: 其中,旋转过程中移动终端所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为旋转过程中移动终端对应的轴向。 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者判断旋转过程中移动终端所处的放置方向为竖直放置方向 ,将参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 分别以轴向为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实现方式,在第五种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013] 结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括确定: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动终端中以正常模式呈现的全景照片移动包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实现方式中,所述检测确定移动终端的旋转角度之前,还包括提供用于指示旋转移动终端的提示信息。 [0015] 结合第一方面的第七种实现方式,在第八种实现方式中,所述提供用于指示旋转移动终端的提示信息之前,所述方法还包括: 获取旋转时保存的移动终端的旋转方向。 拍摄全景照片,提供用于指示旋转移动终端的提示信息包括:根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0016]第二方面,提供了一种全景照片在移动终端中的呈现装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,所述触发指令用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元,所述沉浸式浏览模式为全景照片随着移动终端移动的浏览模式。 旋转,所述判断单元,用于接收检测单元发送的检测结果,若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送给呈现单元,呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0017] 结合第二方面,在第一种实现方式中,所述确定单元具体用于通过以下方式确定所述移动终端的旋转角度,确定所述移动终端在旋转过程中所处的放置方向,以及 根据放置方向确定移动终端的旋转角度。 [0018] 结合第二方面的第一种实现方式,在第二种实现方式中,所述确定单元具体用于通过以下方式确定所述移动终端在检测角度的旋转过程中所处的放置方向 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 位于,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端所在的放置方向 d 在旋转过程中。 [0019] 结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元具体用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,通过如下方式确定: 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向相对于参考的X-Y平面方向的夹角 三维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面方向大于45度,确定 其中,旋转过程中移动终端所处的放置方向为水平放置方向。 [0020]结合第二方面的第二种实现方式或第二方面的第三种实现方式,在第四种实现方式中,所述确定单元具体用于通过如下方式确定所述移动终端的旋转角度: 放置方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴向 旋转过程中的移动终端,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向 旋转过程为垂直放置方向,使用X轴方向或Y轴方向 参考三​​维坐标系中的s作为移动终端在旋转过程中对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实现方式,在第五种实现方式中,所述装置还包括判断单元,所述判断单元根据所述确定的旋转角度,在所述呈现单元移动前,确定所述全景图 在移动终端中以正常模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元还用于在所述呈现单元根据确定的旋转角度移动之前,以正常模式呈现的全景照片处于 移动终端,根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 呈现单元,具体用于如下移动移动终端中正常模式呈现的全景照片,使全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0023] 结合第二方面,在第七种实现方式中,所述装置还包括提示单元,所述提示单元用于接收所述检测单元发送的检测结果; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示旋转移动终端的提示信息。 [0024] 结合第二方面的第七种实现方式,在第八种实现方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄所述全景照片时保存的所述移动终端的旋转方向 , 向提示单元发送获取的拍摄照片时保存的移动终端的旋转方向, 提示单元具体用于通过以下方式提供提示信息, 用于指示 旋转移动终端,根据获取单元获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0025]第三方面,提供了一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于在检测到输入设备输入触发指令时,根据检测确定的旋转角度移动移动终端中以正常模式呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实现方式,在第二种实现方式中,所述传感器具体用于通过以下方式,在检测角度的旋转过程中,确定所述移动终端所处的放置方向 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 定位,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端在ro中的放置方向 化过程。 [0028] 结合第三方面的第二种实现方式,在第三种实现方式中,所述传感器具体用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,采用如下方式确定: 参考三​​维坐标系的X-Y平面,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角时,移动终端在旋转过程中所处的放置方向- 维度坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于方向的夹角为 参考三​​维坐标系的X-Y平面大于45度,确定t 移动终端在旋转过程中所处的放置方向为水平放置方向。 [0029]结合第三方面的第二种实现方式或第三方面的第三种实现方式,在第四种实现方式中,所述传感器具体用于通过以下方式,根据所述移动终端的旋转角度确定所述移动终端的旋转角度。 放置方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴向 旋转过程中的移动终端,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向 旋转过程为垂直放置方向,在旋转过程中使用X轴方向或Y轴方向 在旋转过程中参考三维坐标系作为移动终端对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,移动所述移动设备中以正常模式呈现的全景照片。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于,在移动终端中以正常模式呈现的全景照片根据确定的旋转角度移动之前,确定 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 所述处理器,具体用于移动终端中正常模式下呈现的全景照片的移动方式, 使全景照片沿与移动终端的旋转方向相反的方向移动最小位移 . [0032] 结合第三方面,在第七种实现方式中,处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示所述移动终端旋转的提示信息之前,获取所述移动终端的旋转方向,即 拍摄全景照片时保存, 处理器具体用于按照以下方式提供用于指示旋转移动终端的提示信息, 提供用于指示旋转移动终端的提示信息 到获得的旋转方向。 [0034] 本发明实施例提供的一种移动终端全景照片呈现方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测到,检测并确定移动终端的旋转角度; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 通过本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,简单方便。 操作。 附图说明 [0035]为了更加清楚地描述本发明实施例中的技术方案,下面对实施例描述中所需要的附图进行简单介绍。 [0036] 图1为本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一种实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端的旋转角度的过程的示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所处放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实现示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实现示意图。 [0043] 图8为本发明实施例的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例的全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例的全景照片浏览过程的实现示意图。 [0046] 图10A至图10D为本发明实施例的移动终端中全景照片呈现装置的结构示意图。 [0047] 图11为本发明实施例的移动终端的结构示意图。 具体实施方式 [0048] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 本发明实施例提供的移动终端中全景照片的呈现方法,全景照片随着移动终端的旋转而移动。 本发明实施例中为了描述方便,将全景照片随着移动终端的旋转而移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为 以下简称正常模式,当然不限于此; 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览以普通模式显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 该方法可以由移动终端执行,或者具体可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤: [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 本发明实施例中,若检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :根据S中确定的旋转角度移动并呈现 102 ,移动终端正常显示的全景照片。 [0055] 本发明实施例提供的移动终端中全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 通过本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,简单方便。 操作。 [0056] 在本发明实施例中,具体实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在用户触发移动终端进入沉浸式浏览模式后立即以预定方式旋转移动终端,该预定方式可以例如通过用户手册预先学习得到。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示旋转移动终端的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供用于指示旋转移动终端的提示信息的实现方式为例,对全景照片在移动终端中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的全景照片在移动终端中的呈现方法的另一种实现流程图。 该方法可以由移动终端执行,或者具体可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤: [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,本发明实施例可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 启用控件的启用状态用于确定是否启用沉浸式浏览模式,当检测到启用控件被启用时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面设置沉浸式浏览按钮。 When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选地,本发明实施例还可以在检测到用户正在浏览全景照片时,提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片随着移动终端的旋转而移动。 通常,为了更好的浏览全景照片,可以提供用于指示旋转移动终端的提示信息,以告知用户移动终端需要按照预设方向进行旋转,该预设方向可以为 例如,从左向右旋转,当然,也可以从右向左旋转。 [0064] 在本发明实施例中,所提供的提示信息可以是在显示界面上显示的文本信息,当然,也可以是通过语音输出的方式通知的语音信息,本发明实施例对此不作具体限定。 . [0065] 可选地,本发明实施例还可以获取拍摄全景照片时保存的移动终端的旋转方向,并以提示信息的形式通知获取的旋转方向。 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,提示用户根据获取的拍摄全景照片时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,从而及时控制全景照片移动。 [0068] 用户在拍摄全景照片时,一般会将移动终端定位在确定的放置方向上。 但是,用户在浏览全景照片时,很可能会使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了更准确地浏览全景照片,可以根据移动终端在旋转过程中所处的放置方向来确定移动终端的旋转角度。 [0069] S中移动终端旋转角度的确定过程 203 本发明实施例可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 在本发明实施例中,可以利用设置在移动终端中的重力传感器指示的移动终端的重力方向来确定移动终端所在的放置方向,移动终端的旋转角度为 通过使用布置在移动终端中的陀螺仪传感器的角度来确定。 可选地,在本发明实施例中,用于确定移动终端的放置方向的重力传感器和用于确定移动终端的旋转角度的陀螺仪传感器可以在用于指示移动终端的触发指令时被启用。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选地,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤: [0074] 小号 2031 a :以移动终端屏幕所在平面为基准,建立参考三维坐标系。 [0075]本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面平行于该平面 移动终端屏幕所在平面,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也根据移动终端的不同放置方向进行旋转。 例如,参考三维坐标系的示意图分别对应图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的夹角 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过在S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选地,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于基准三的X-Y平面方向的夹角时- 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为竖直放置方向。 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所处的放置方向 旋转过程中为水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为竖直放置方向,或者为水平放置方向,本发明实施例具体可以设置为竖直放置方向。 [0081] 本发明实施例中,如果通过移动终端的重力方向相对于参考三的X-Y平面方向的夹角确定旋转过程中移动终端所处的放置方向 S中的维坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 : [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 本发明实施例在确定移动终端在旋转过程中所处的放置方向为水平放置方向时,采用参考三维坐标系中Z轴的方向 作为移动终端在旋转过程中对应的轴向; 或者,当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 用作移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,本发明实施例中,上述移动终端在旋转过程中对应的轴向仅仅是为了简化确定移动终端旋转角度的过程,具体的确定方式不作限定。 至此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺仪传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于对应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度移动移动终端正常显示的全景照片。 [0088] 本发明实施例中,在浏览全景照片时,一般先以普通浏览方式显示全景照片; 例如,可以是分辨率较低的全景照片,或者只有全景照片的最左部分或全景照片的最右部分等部分全景照片显示在手机的显示屏中 终端。 本发明实施例在确定移动终端的旋转角度后,可以移动终端中正常模式显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实现方式来移动移动终端中正常模式下显示的全景照片。 例如,移动终端在正常模式下显示的全景照片可以沿与移动终端的旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,本发明实施例中,为了实现全景照片的平滑移动,可以预先设置一个旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现了全景照片的平滑移动。 如果没有达到预设的旋转角度阈值,全景照片可能不会被移动。 [0091] 本发明实施例中,根据确定的移动终端的旋转角度,移动终端中正常模式下显示的全景照片在S中沿与移动终端旋转方向相反的方向移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端的旋转方向相同的方向移动时,也可以采用类似的方式): [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,则执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常模式显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,在本发明实施例中,为了进一步增强平滑移动的效果,还可以确定最小位移,当控制全景图像沿与移动终端的旋转方向相反的方向移动时, 照片每次移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,可以根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度以及全景照片沿a的照片宽度,确定全景照片的最小位移量。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录并保存,可以是 直接从本发明实施例拍摄全景照片时保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选地,在本发明实施例中,确定全景照片的最小位移可以采用以下方式。 全景照片的最小位移根据公式确定 [0097] s = d ⁢ φ 1 φ 2 , 其中s是全景照片的最小位移; d为全景照片的照片宽度; φ 1 为预设旋转角度阈值; φ2为拍摄全景照片时移动终端的旋转角度。 [0098] 本发明实施例中,对于浏览的全景照片,在确定为全景照片时,全景照片的照片宽度d和拍摄全景照片时移动终端的旋转角度φ2为固定值(如果 在拍摄全景照片的过程中记录了旋转角度φ2,使用记录的值;如果在拍摄过程中没有记录旋转角度φ2,则可以参考一些参考值,例如180度或360度作为旋转角度。 角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,适当的旋转角度阈值φ 1 可能是预设的。 若预设旋转角度阈值φ 1 固定后,确定全景照片在旋转过程中移动的最小位移量。 在浏览全景照片的过程中,实时检测并判断移动终端的旋转角度,如果判断移动终端的旋转角度达到预设的旋转角度阈值φ 1 ,全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0099] 本发明实施例中,移动终端的旋转角度可以为移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,可以认为上一次移动全景照片时移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为持续执行并重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值φ 1,可以将移动终端的初始旋转角度设置为0,检测并确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值来移动全景照片。 例如,移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 −1度,全景照片不动; 当移动端旋转到φ 1 度,全景照片移动最小位移,重新设置旋转角度,继续检测移动端的旋转角度; 当移动端旋转到φ 1 度,全景照片再次移动最小位移,如此循环直到移动终端停止转动。 [0100] 进一步地,本发明实施例中移动全景照片的过程可以为立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,则移动全景照片 ; 例如,预设的旋转角度阈值φ 1 为5度,当旋转角度达到5度时,全景照片移动到最小位移。 移动全景照片的过程也可以是延时执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后,在一段时间内将全景照片移动最小位移量 临界点。 [0101] 移动终端的旋转角度还可以为移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以为a 随着用户移动移动终端不断积累价值。 此时,可以设置全景照片移动的位移与旋转角度成正比关系。 即,移动终端旋转角度越大,全景照片移动的位移越大,移动终端旋转角度越小,全景照片移动的位移越小。 [0102] 上述移动全景照片的方式和最小位移的确定方式还可以有其他实施方式,本发明不对其具体实施方式进行限定。 [0103] 小号 205 :以沉浸式浏览方式呈现全景照片。 [0104] 本发明实施例在沉浸式浏览方式下实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种全景照片的呈现方式可以采用现有的实施方案,例如,在呈现全景照片时,在将全景照片适配显示屏尺寸的过程中可以采用现有的实施方式。 [0105]本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移并呈现。 通过本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,而不需要手动在移动终端的屏幕上滑动浏览全景照片,简单易行。 操作方便。 [0106] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,当然本发明不限于此。 [0107] 本发明实施例提供的控制全景照片在移动终端中呈现的方法的实现基于拍摄全景照片时保存的照片参数,该照片参数例如为: 拍摄全景照片时移动终端旋转,移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的移动终端中全景照片的呈现方法,在拍摄全景照片时,该方法也可以区别于现有的全景照片拍摄。 本发明以下实施例将结合实际案例举例说明全景照片的拍摄过程和浏览过程。 [0108] 图9A示出了根据本发明实施例的拍摄全景照片的过程的实现示意图。 如图9A所示,实现过程包括以下步骤: [0109] 小号 301 :启用全景拍摄模式。 [0110] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0111] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0112] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0113] 本发明实施例中,可以通过陀螺仪传感器在S中启动的角度来确定移动终端的旋转角度。 302 旋转。 [0114] 小号 305 :保存拍摄的全景照片的属性信息。 [0115] 本发明实施例中,保存的全景照片的属性信息至少包括照片类型、拍摄角度和照片尺寸,其中,照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0116] 可选地,本发明实施例中,保存的全景照片的属性信息还可以包括拍摄全景照片时移动终端的旋转方向,该旋转方向例如可以为从右向左, 当然,也可能是从左到右。 [0117] 图9B示出了根据本发明实施例的全景照片浏览过程的实现示意图。 如图9B所示,实现过程包括以下步骤: [0118] 小号 401 :检测用户浏览的照片类型。 [0119] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行S 403 ; 否则,以正常的照片浏览方式浏览照片。 [0120] 小号 403 :当检测到用户触发了用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0121] 小号 404 :用户通过旋转移动端浏览全景照片。 [0122] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 具体的确定过程可以参见前述实施例的相关描述。 [0123] 小号 406 :根据S中确定的放置方向,确定移动终端在相应轴向的旋转角度 405 以及陀螺仪传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端在Z方向上旋转的角度 -轴,当移动终端的放置方向为竖直放置方向时,确定移动终端在X轴或Y轴方向上旋转的角度。 [0124] 小号 407 :判断旋转角度是否在S中确定 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0125] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移量。 [0126] 小号 409 :检测移动终端的放置方向和旋转角度; 当移动端的放置方向改变时,执行S 405 ,当旋转角度发生变化时,执行S 407 . [0127] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,从而及时调整全景照片的移动。 [0128] 本发明实施例提供的移动终端中全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 通过本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动滑动。 在移动终端屏幕上浏览全景照片。 [0129] 基于上述实施例提供的移动终端中全景照片的呈现方法,本发明实施例还提供一种装置 900 用于在移动终端呈现全景照片。 如图 10A 所示,该装置 900 包括一个检测单元 901 , 决定单位 902 , 和一个呈现单元 903 . [0130] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元 902 ,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动的浏览模式。 [0131] 决定单位 902用于接收检测单元发送的检测结果 901 ; 若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的移动终端的旋转角度发送给呈现单元 903 . [0132] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0133] 在第一种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端的旋转角度,确定移动终端在旋转过程中所处的放置方向,并根据放置方向确定移动终端的旋转角度。 [0134] 在第二种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端在旋转过程中所处的放置方向: 检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角 -维坐标系,其中参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于 移动终端屏幕所在的平面; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0135] 在第三种实施方式中,确定单元 902 具体用于,通过如下方式,根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端的放置方向 定位旋转过程:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 端子位于旋转过程中是垂直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0136] 在第四种实施方式中,所述确定单元 902 具体用于通过以下方式根据放置方向确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向 维坐标系作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 l以相对于轴向为移动终端的旋转角度旋转。 [0137] 在第五种实施方式中,所述装置还包括判断单元 904, 如图 10B 所示, 在呈现单元之前 903 判断单元根据确定的旋转角度移动移动终端中正常模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0138] 在第六种实施方式中,所述确定单元 902 还配置在呈现单元之前 903 移动,根据确定的旋转角度移动终端中正常模式下呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,全景时移动终端的旋转角度 拍摄全景照片时,全景照片沿移动终端旋转方向的照片宽度,以及呈现单元 903 具体用于如下所述移动移动终端中正常模式下呈现的全景照片,将全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量。 [0139] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供用于指示旋转移动终端的提示信息。 [0140] 在第八种实施方式中,所述装置还包括获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,并发送给提示单元 905 ,获取拍照时保存的移动终端的旋转方向,以及提示单元 905 具体用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取单元获取的旋转方向提供用于指示旋转移动终端的提示信息 906 . [0141] 需要说明的是,对于本发明实施例图10A至图10D提供的全景照片在移动终端中的呈现装置,如果具体实现全景照片在移动终端中的呈现过程不是 描述的不够详细,可以参见方法实施例的相关描述,在此不再赘述。 [0142] 本发明实施例提供的移动终端中全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 通过本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动滑动。 在移动终端屏幕上浏览全景照片。 [0143] 基于上述实施例提供的全景照片在移动终端中的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动端 1000 包括一个输入设备 1001 , 一个传感器 1002 , 处理器 1003 , 和一个显示屏 1004 ,其中输入设备 1001 用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,所述传感器 1002 用于检测移动终端的旋转角度,处理器1003 用于当检测到输入设备输入触发指令时 1001 ,根据检测确定的旋转角度移动移动终端中正常模式呈现的全景照片,显示屏幕 1004 用于呈现全景照片。 [0144] 本发明实施例中,输入设备可以是一个或多个 1001 ,例如,输入设备 1001 可能是显示屏或按钮,可能与处理器集成在一起 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可能连接到处理器 1003 使用有线连接(例如电缆/端口)或无线连接(例如蓝牙)。 [0145] 处理器 1003 可以在单芯片、多芯片或多个电子元件上实现,可以采用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0146] 可能有一个或多个传感器 1002 ,其中传感器 1002 可能有也可能没有运算处理功能。 例如,传感器 1002 本发明实施例中可以为重力传感器和陀螺仪传感器中的至少一种。 [0147] 在本发明的这个实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0148] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0149] 第二种实现方式,传感器 1002 具体用于通过以下方式确定移动终端在旋转过程中所处的放置方向: 检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角 -维坐标系,其中参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于 移动终端屏幕所在的平面; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0150] 第三种实现方式,传感器 1002 具体用于,通过如下方式,根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端的放置方向 定位旋转过程:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 终端在旋转过程中所处位置为竖直放置方向,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,确定: 移动终端在旋转过程中所处的放置方向为水平放置方向 节。 [0151] 在第四种实现方式中,传感器 1002 具体用于通过以下方式根据放置方向确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向 维坐标系作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 l以相对于轴向为移动终端的旋转角度旋转。 [0152] 在第五种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,将在移动终端中以正常模式呈现的全景照片确定移动终端的旋转角度达到预设的旋转角度阈值。 [0153] 在第六种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移, 拍摄全景照片时的移动终端,以及拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度,以及处理器 1003 具体用于移动终端中正常模式下呈现的全景照片的移动方式: 将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0154] 在第七种实现方式中,处理器 1003 还用于当检测到输入设备输入触发指令时 1001 ,提供用于指示旋转移动终端的提示信息。 [0155] 在第八种实现方式中,处理器 1003 还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,处理器 1003 用于指示旋转移动终端的提示信息,具体用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0156] 需要说明的是,对于本发明实施例图11提供的移动终端,具体实现控制全景照片在移动终端中显示的过程如果描述的不够详细,可以参考 方法实施例的相关描述,此处不再赘述。 [0157] 本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片随着移动终端的旋转而移动。 通过本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动滑动。 在移动终端屏幕上浏览全景照片。 [0158]本领域的技术人员应该理解,本发明的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本发明可以采用纯硬件实施例、纯软件实施例或结合软件和硬件的实施例的形式。 此外,本发明可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0159] 参考根据本发明实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图描述了本发明。 应当理解,可以使用计算机程序指令来实现流程图和/或框图中的每个过程和/或每个框以及流程图和/或框图中的过程和/或框的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器生成机器,使得任何计算机或处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0160] 这些计算机程序指令也可以存储在计算机可读存储器中,该计算机可读存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,使得存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程中和/或在框图中的一个或多个块中实现特定功能。 [0161] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程数据处理设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供了用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0162] 以上虽然描述了本发明的一些优选实施例,但是本领域的技术人员在了解了基本的发明构思后,可以对这些实施例进行更改和变型。 因此,所附权利要求旨在被解释为涵盖优选实施例以及落入本发明范围内的所有改变和修改。 [0163] 显然,本领域的技术人员可以对本发明实施例进行各种更改和变型而不脱离本发明实施例的范围。 本发明旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), CA2966400A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), CA2966400C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), CN104471519A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519B(String), 1048800(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), CN110650241A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241B(String), 1048801(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US10222877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.808 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US10649546B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US11126275B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.878 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.878 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US20150363915A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US20170212609A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US20190171300A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:25.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US20200241657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), US9621802B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271404(Integer), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104471519B(String), CN104471519B(String), 1600963200(Integer), 271404(Integer), 185688(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 271405(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 271405(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.275 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185959(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185959(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.378 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.378 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185959(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185959(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.520 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.520 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185959(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:26.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10222877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10222877B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US15/483724(String), 1491753600(Integer), US10222877B2(String), 1551715200(Integer), 1551715200(Integer), 美国(String), 4(Integer), 8(Integer), 47(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20070263995A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9729788B2 | US9894272B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185960(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e9cd0892d58940f6b10bd032b33b52a5.png(String), 185960(Integer), e9cd0892d58940f6b10bd032b33b52a5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.322 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.322 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10222877B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US15/483724(String), 1491753600(Integer), US10222877B2(String), 1551715200(Integer), 1551715200(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 47(Integer), CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | US20050237383A1 | US20070109398A1 | US20070263995A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9729788B2 | US9894272B2(String), \20230420\e9cd0892d58940f6b10bd032b33b52a5.png(String), 20(Integer), 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.409 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 1. A method of presenting a panoramic photo in a mobile terminal, comprising:photographing a panoramic photo with the mobile terminal moving along one direction;receiving an instruction of entering an immersive browsing mode; andunder the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating along an axis of a plane with a first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating along the axis of the plane with the first direction, the plane being a plane of a screen of the mobile terminal;detecting the mobile terminal rotating along the axis with a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating along the axis with the second direction, the first direction being the same as the direction of the mobile terminal when the panoramic photo is photographed, the second direction being opposite to the first direction, the second part of the panoramic photo being different from the first part of the panoramic photo, and the third part of the panoramic photo being different from the first part of the panoramic photo.(String), 1.如权利要求10所述的移动终端,其中移动终端从左向右移动,或从右向左移动拍摄全景照片。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 2. The method of claim 1, wherein the panoramic photo is photographed with the mobile terminal moving from left to right, or moving from right to left.(String), 12.如权利要求11所述的移动终端,其中全景照片的第一部分是全景照片的最左侧部分或全景照片的最右侧部分。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 3. The method of claim 2, wherein the first part of the panoramic photo is the leftmost part of the panoramic photo or the rightmost part of the panoramic photo.(String), 13.如权利要求10所述的移动终端,其中在移动终端从左向右移动拍摄全景照片的情况下,第二部分在第一部分的右侧,第三部分在第一部分的左侧。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 4. The method of claim 1, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from left to right, the second part is to the right of the first part, and the third part is to the left of the first part.(String), 14.如权利要求10所述的移动终端,其中在移动终端从右向左移动拍摄全景照片的情况下,第二部分在第一部分的左侧,第三部分在第一部分的右侧。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 5. The method of claim 4, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from right to left, the second part is to the left of the first part, and the third part is to the right of the first part.(String), 15.如权利要求10所述的移动终端,其中指令使移动终端进一步执行:以正常模式显示全景照片;在正常模式下显示图标;检测图标上的输入;和响应于检测到图标上的输入而进入沉浸式浏览模式。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 6. The method of claim 1, further comprising:displaying the panoramic photo in a normal mode;displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 16.如权利要求10所述的移动终端,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 7. The method of claim 1, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 17.如权利要求10所述的移动终端,其中移动终端沿轴的旋转由移动终端的陀螺仪传感器检测。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 8. The method of claim 1, wherein rotation of the mobile terminal along the axis is detected by a gyro sensor of the mobile terminal.(String), 18.如权利要求10所述的移动终端,其中该轴线平行于移动终端屏幕的一侧,并横跨移动终端的中心。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 9. The method of claim 1, wherein the axis is parallel to a side of the screen of the mobile terminal and is across a center of the mobile terminal.(String), 19.一种非暂时性计算机可读存储介质包括当由移动终端执行时,使移动终端执行以下步骤的指令:移动终端沿一个方向移动拍摄全景照片;接收进入沉浸式浏览模式的指令;和沉浸式浏览模式下:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向的平面轴旋转;响应于检测到移动终端沿第一方向的平面的轴旋转显示全景照片的第二部分,该平面为移动终端的屏幕平面;检测移动终端沿第二方向的轴旋转;和响应于检测到移动终端以第二方向沿轴旋转显示全景照片的第三部分,第一方向与拍摄全景照片时移动终端的方向相同,第二方向与第一方向,第二部分全景照片不同于第一部分全景照片,第三部分全景照片不同于第一部分全景照片。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 10. A mobile terminal, comprising:one or more processors;a screen coupled to the one or more processors;a camera coupled to the one or more processors;a sensor coupled to the one or more processors; anda memory coupled to the one or more processors and comprising instructions that when executed by the one or more processors, cause the mobile terminal to perform:photographing a panoramic photo with the mobile terminal moving along one direction;receiving an instruction of entering an immersive browsing mode; andunder the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating along an axis of a plane with a first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating along the axis of the plane with the first direction, the plane being a plane of a screen of the mobile terminal;detecting the mobile terminal rotating along the axis with a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating along the axis with the second direction, the first direction being the same as the direction of the mobile terminal when the panoramic photo is photographed, the second direction being opposite to the first direction, the second part of the panoramic photo being different from the first part of the panoramic photo, and the third part of the panoramic photo being different from the first part of the panoramic photo.(String), 20.如权利要求19所述的非暂时性计算机可读存储介质,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 11. The mobile terminal of claim 10, wherein the panoramic photo is photographed with the mobile terminal moving from left to right, or moving from right to left.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 12. The mobile terminal of claim 11, wherein the first part of the panoramic photo is the leftmost part of the panoramic photo or the rightmost part of the panoramic photo.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 13. The mobile terminal of claim 10, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from left to right, the second part is to the right of the first part, and the third part is to the left of the first part.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 14. The mobile terminal of claim 10, wherein in a case that the panoramic photo is photographed with the mobile terminal moving from right to left, the second part is to the left of the first part, and the third part is to the right of the first part.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 15. The mobile terminal of claim 10, wherein the instructions cause the mobile terminal to further perform:displaying the panoramic photo in a normal mode;displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 16. The mobile terminal of claim 10, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 17. The mobile terminal of claim 10, wherein rotation of the mobile terminal along the axis is detected by a gyro sensor of the mobile terminal.(String), 1(Integer), 16(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 18. The mobile terminal of claim 10, wherein the axis is parallel to a side of the screen of the mobile terminal and is across a center of the mobile terminal.(String), 1(Integer), 17(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 19. A non-transitory computer-readable storage medium comprising instructions which, when executed by a mobile terminal, cause the mobile terminal to carry out the following steps:photographing a panoramic photo with the mobile terminal moving along one direction;receiving an instruction of entering an immersive browsing mode; andunder the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating along an axis of a plane with a first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating along the axis of the plane with the first direction, the plane being a plane of a screen of the mobile terminal;detecting the mobile terminal rotating along the axis with a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating along the axis with the second direction, the first direction being the same as the direction of the mobile terminal when the panoramic photo is photographed, the second direction being opposite to the first direction, the second part of the panoramic photo being different from the first part of the panoramic photo, and the third part of the panoramic photo being different from the first part of the panoramic photo.(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185960(Integer), 20. The non-transitory computer-readable storage medium of claim 19, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185960(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 14/735,625 filed Jun. 10, 2015, now U.S. Pat. No. 9,621,802, which is a continuation of International Patent Application No. PCT/CN2014/079950, filed on Jun. 16, 2014. All of the afore-mentioned patent applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present disclosure. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present disclosure. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present disclosure. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present disclosure. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present disclosure. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present disclosure. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present disclosure. [0046]FIGS. 10A, 10B, 10C, and 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present disclosure, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present disclosure, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps. [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present disclosure, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present disclosure, there may be multiple implementation manners for implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present disclosure in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps. [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present disclosure, a user may input, using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present disclosure, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present disclosure, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present disclosure, in order to implement immersive mode browsing, the user needs to rotate the mobile terminal, so that the panoramic photo can move as the mobile terminal rotates. Generally, for better browsing of the panoramic phot(String), 相关申请的交叉引用 [0001] 本申请是美国专利申请系列的延续。 2015 年 6 月 10 日提交的第 14/735,625 号,现为美国专利。 美国专利第 9,621,802 号是 2014 年 6 月 16 日提交的国际专利申请第 PCT/CN2014/079950 号的延续。所有上述专利申请均以引用方式全文并入本文。 技术领域 [0002] 本发明涉及通信技术领域,尤其涉及一种在移动终端中呈现全景照片的方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,使用移动终端的范围和环境也越来越多样化。 例如,目前手机、个人数字助理、个人电脑等很多移动终端都具备全景拍照功能。 [0004] 当移动终端进行全景拍摄时,用户转动移动终端来拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 再根据上述拼接原理,可以将多张拍摄的照片拼接为一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,可以浏览全景照片上比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作相对复杂。 概括 [0006] 本发明实施例提供一种在移动终端中呈现全景照片的方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 根据第一方面,提供了一种在移动终端中呈现全景照片的方法,包括检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为 全景照片随着移动终端旋转移动,若检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实施方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009] 结合第一方面的第一种实现方式,在第二种实现方式中,确定移动终端在旋转过程中所处的放置方向包括:检测移动终端的重力方向相对于移动终端的角度。 参考三​​维坐标系的X-Y平面方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考坐标系的Z轴 三维坐标系垂直于移动终端屏幕所在的平面,根据移动终端重力方向相对于参考三坐标X-Y平面方向的夹角确定 三维坐标系,移动终端在旋转过程中所处的放置方向。 [0010] 结合第一方面的第二种实现方式,在第三种实现方式中,根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为垂直放置方向; 当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,确定移动终端所在的放置方向为旋转 工艺是水平放置方向。 [0011] 结合第一方面的第二种实施方式或第一方面的第三种实施方式,在第四种实施方式中,根据放置方向确定移动终端的旋转角度包括:如果确定放置方向 其中移动终端在旋转过程中所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向; 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端在旋转过程中所处的放置方向为垂直放置方向 ,以参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并以移动终端旋转的角度为 相对于轴向作为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实施方式,在第五种实施方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013] 结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动在移动终端中以正常模式呈现的全景照片,包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实施方式中,在检测确定移动终端的旋转角度之前,还包括:提供用于指示移动终端旋转的提示信息。 [0015] 结合第一方面的第七种实施方式,在第八种实施方式中,在提供用于指示移动终端旋转的提示信息之前,该方法还包括:获取移动终端的旋转方向。 拍摄全景照片, 提供用于指示移动终端旋转的提示信息包括: 提供用于指示根据获取的旋转方向旋转移动终端的提示信息。 [0016] 第二方面,提供了一种在移动终端中呈现全景照片的装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送至确定单元,沉浸式浏览模式为全景照片随着移动终端移动的浏览模式 旋转时,确定单元,用于接收检测单元发送的检测结果,如果检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送到呈现单元, 呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度,移动并呈现移动终端中正常呈现的全景照片。 [0017] 结合第二方面,在第一种实施方式中,确定单元用于确定移动终端的旋转角度如下:确定移动终端在旋转过程中所处的放置方向,确定 移动终端根据放置方向的旋转角度。 [0018] 结合第二方面的第一种实施方式,在第二种实施方式中,所述确定单元,用于通过以下方式确定所述移动终端在检测角度的旋转过程中所处的放置方向。 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,其中,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面。 参考三​​维坐标系的Z轴垂直于移动终端屏幕所在的平面,根据移动终端的重力方向相对于该移动终端的角度确定 参考三​​维坐标系的X-Y平面方向,移动终端在轮播中所处的放置方向 化过程。 [0019] 结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元,用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,采用如下方式确定。 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向与参考三坐标的X-Y平面方向的夹角时 -维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为垂直放置方向,当移动终端的重力方向相对于该方向的夹角时 参考三​​维坐标系的 X-Y 平面的夹角大于 45 度,确定 th 移动终端在旋转过程中所处的放置方向为水平放置方向。 [0020]结合第二方面的第二种实施方式或第二方面的第三种实施方式,在第四种实施方式中,所述确定单元,用于根据以下方式确定所述移动终端的旋转角度: 放置方向如果确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所在的放置方向在 旋转过程是垂直放置方向,使用参考中的X轴方向或Y轴方向 以三维坐标系作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实施方式,在第五种实施方式中,所述装置还包括判断单元,所述判断单元在所述呈现单元移动之前,根据所述确定的旋转角度,确定所述全景图。 在移动终端中以普通模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元,还用于在所述呈现单元移动之前,根据所述确定的旋转角度,将正常模式下呈现的全景照片在 移动终端,根据预设的旋转角度阈值、全景照片拍摄时移动终端的旋转角度、全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 所述呈现单元,用于将所述移动终端以正常模式呈现的所述全景照片沿与所述移动终端的旋转方向相反的方向移动所述全景照片最小位移。 [0023] 结合第二方面,在第七种实施方式中,所述装置还包括提示单元,所述提示单元,用于接收所述检测单元发送的检测结果。 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0024] 结合第二方面的第七种实施方式,在第八种实施方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄全景照片时保存的所述移动终端的旋转方向。 ,并将获取的拍摄照片时保存的移动终端的旋转方向发送给提示单元, 提示单元用于以如下方式提供用于指示旋转的提示信息 移动终端提供提示信息,用于指示移动终端根据获取单元获取的旋转方向进行旋转。 [0025]第三方面,提供一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,所述沉浸式浏览模式为全景照片随着移动终端旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于当检测到输入设备输入触发指令时,根据检测确定的旋转角度,移动移动终端中正常呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实施方式,在第二种实施方式中,所述传感器用于通过如下方式确定所述移动终端在检测重力角的旋转过程中所处的放置方向 移动终端的方向相对于参考三维坐标系的X-Y平面的方向,其中,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 ,参考三维坐标系的Z轴与移动终端屏幕所在的平面垂直,根据移动终端的重力方向相对于该方向的夹角确定 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向 s。 [0028] 结合第三方面的第二种实施方式,在第三种实施方式中,所述传感器,用于根据所述移动终端的重力方向相对于X-Y方向的夹角,如下确定: 参考三​​维坐标系平面,移动终端在旋转过程中所处的放置方向,移动终端的重力方向相对于参考三维坐标系X-Y平面方向的夹角 坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为垂直放置方向,当移动终端的重力方向相对于移动终端的方向的夹角时 参考三​​维坐标系的X-Y平面大于45度,确定放置 移动终端在旋转过程中所处的方向为水平放置方向。 [0029]结合第三方面的第二种实施方式或第三方面的第三种实施方式,在第四种实施方式中,所述传感器用于根据所述摆放位置通过如下方式确定所述移动终端的旋转角度 方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所在的放置方向在 旋转过程是垂直放置方向,在参考三中使用一个X轴的方向或者一个Y轴的方向 -维坐标系作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,将正常模式下呈现的全景照片在手机中移动。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,确定在移动终端中以正常模式呈现的全景照片 全景照片根据预设旋转角度阈值的最小位移、全景照片拍摄时移动终端的旋转角度、全景照片拍摄时全景照片沿移动终端旋转方向的照片宽度 所述处理器用于将所述移动终端以正常模式呈现的全景照片沿与所述移动终端的旋转方向相反的方向移动所述全景照片最小位移。 [0032] 结合第三方面,在第七种实施方式中,所述处理器还用于在检测到所述输入设备输入触发指令时,提供用于指示移动终端旋转的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示旋转所述移动终端的提示信息之前,获取所述移动终端的旋转方向为: 在拍摄全景照片时保存, 处理器用于按照如下方式提供用于指示移动终端旋转的提示信息,提供用于指示移动终端旋转的提示信息 获取的旋转方向。 [0034] 根据本发明实施例提供的一种在移动终端中呈现全景照片的方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测,检测确定移动终端的旋转角度; 根据确定的旋转角度,移动并呈现移动终端中正常显示的全景照片。 通过本发明,可以实现全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便 . 附图说明 [0035]为了更清楚地描述本发明实施例中的技术方案,下面简要介绍描述实施例所需的附图。 [0036] 图1是根据本发明实施例的在移动终端中呈现全景照片的方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端旋转角度的过程示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所在放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实施示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实施示意图。 [0043] 图8为本发明实施例提供的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例提供的全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例提供的全景照片浏览过程的实现示意图。 [0046] 图10A、图10B、图10C和图10D是根据本发明实施例的移动终端中全景照片的呈现装置的结构示意图。 [0047] 图11为本发明实施例提供的一种移动终端的结构示意图。 具体实施方式 [0048] 下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚的说明。 以上所述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 根据本发明实施例提供的一种移动终端中全景照片的呈现方法,全景照片随着移动终端的转动而移动。 本发明实施例为了描述方便,将全景照片随移动终端旋转移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为 以下称为正常模式,当然不限于此。 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览正常模式下显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的在移动终端中呈现全景照片的方法的实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤。 [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 在本发明实施例中,如果检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :根据 S 中确定的旋转角度移动并呈现 102 ,在移动端以普通模式显示的全景照片。 [0055] 根据本发明实施例提供的移动终端全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 根据确定的旋转角度,移动并呈现移动终端中正常显示的全景照片。 通过本发明,可以实现全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便 . [0056] 在本发明实施例中,实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在触发移动终端进入沉浸式浏览模式后,立即以预定义的方式旋转移动终端,该预定义的方式例如可以通过预先学习用户手册获得。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示移动终端旋转的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供提示信息用于指示移动终端旋转的实现方式为例,对全景照片在手机中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的在移动终端中呈现全景照片的方法的另一个实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤。 [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 在本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,在本发明实施例中,可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 使能控件的使能状态用于确定是否使能沉浸式浏览模式,当检测到使能控件被使能时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面上设置沉浸式浏览按钮。 在选择进入沉浸式浏览模式浏览全景照片时,用户可以触发按钮,指示移动终端进入沉浸式浏览模式; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选的,在本发明实施例中,还可以在检测到用户正在浏览全景照片时,进一步提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片可以随着移动终端的旋转而移动。 通常,为了更好地浏览全景照片,可以提供用于指示移动终端旋转的提示信息,通知用户移动终端需要按照预设方向进行旋转,其中预设方向可以是 ,例如从左到右旋转,当然,也可能是从右到左旋转。 [0064] 在本发明实施例中,提供的提示信息可以是显示界面上显示的文字信息,当然也可以是通过语音输出通知的语音信息,本发明实施例对此不做限定。 [0065] 可选的,本发明实施例还可以进一步获取拍摄全景照片时保存的移动终端的旋转方向,并将获取的旋转方向以提示信息的形式通知; 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,以提示用户根据获取的全景照片拍摄时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,及时控制全景照片移动。 [0068] 在拍摄全景照片时,用户一般将移动终端定位在确定的放置方向。 然而,在浏览全景照片时,用户很可能使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了比较精确地浏览全景照片,可以根据移动终端在旋转过程中所处的放置方向来确定移动终端的旋转角度。 [0069] S中确定移动终端旋转角度的过程 203 在本发明实施例中,可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 在本发明实施例中,可以通过设置在移动终端中的重力传感器所指示的移动终端的重力方向来确定移动终端所处的放置方向,并确定移动终端的旋转角度。 使用设置在移动终端中的陀螺传感器的角度。 可选地,在本发明实施例中,用于确定移动终端放置方向的重力传感器和用于确定移动终端旋转角度的陀螺传感器可以在用于指示移动终端的触发指令时开启。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选的,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤。 [0074] 小号 2031 a :基于移动终端屏幕所在的平面,建立参考三维坐标系。 [0075]在本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面与该平面平行 移动终端屏幕所在的位置,参考三维坐标系的Z轴垂直于移动终端屏幕所在的平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也会根据移动终端的不同放置方向旋转。 例如,参考三维坐标系的示意图分别对应于图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的角度 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选的,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角时, 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为垂直放置方向; 当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所在的放置方向 在旋转过程中是水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为垂直放置方向,或者为水平放置方向,本发明实施例可以设置为垂直放置方向。 [0081] 在本发明实施例中,如果移动终端在旋转过程中所处的放置方向是通过移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角来确定的, S中的维度坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 . [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 在本发明实施例中,当确定移动终端在旋转过程中所处的放置方向为水平放置方向时,使用参考三维坐标系中的Z轴方向 作为移动终端在旋转过程中对应的轴向; 或者当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 作为移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,在本发明实施例中,上述移动终端在旋转过程中对应的轴向只是为了简化确定移动终端旋转角度的过程,并不限定具体的确定方式 对此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 在本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于相应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度,移动移动终端中正常显示的全景照片。 [0088] 在本发明实施例中,在浏览全景照片时,一般先以普通浏览模式显示全景照片; 例如,可以是分辨率比较低的全景照片,或者只有全景照片的最左边或最右边的部分全景照片显示在手机的显示屏上。 终端。 本发明实施例中,在确定移动终端的旋转角度后,可以移动移动终端中正常模式下显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实现方式来移动移动终端中正常模式下显示的全景照片。 例如,移动终端中以正常模式显示的全景照片可以沿与移动终端旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,在本发明实施例中,为了实现全景照片的平滑移动,可以预先设置旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动终端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现全景照片的平滑移动。 如果未达到预设的旋转角度阈值,则全景照片可能无法移动。 [0091] 在本发明实施例中,根据确定的移动终端的旋转角度,将移动终端中正常模式显示的全景照片沿与移动终端在S中的旋转方向相反的方向移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端旋转方向相同的方向移动时,也可以采用类似方式)。 [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,在本发明实施例中,为了进一步增强平滑移动的效果,还可以进一步确定最小位移,当被控制沿与移动终端旋转方向相反的方向移动时,全景 每次将照片移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,全景照片的最小位移可以根据预设的旋转角度阈值、全景照片拍摄时移动终端的旋转角度、全景照片沿一方向的照片宽度确定。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时沿移动终端旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录保存,可以是 本发明实施例在拍摄全景照片时直接从保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选的,在本发明实施例中,确定全景照片的最小位移可以采用以下方式。 全景照片的最小位移根据公式s=dφ确定 1 /φ 2 ,其中 s 是全景照片的最小位移; d 为全景照片的照片宽度; φ 1 是预设的旋转角度阈值; 和 2 是拍摄全景照片时移动终端的旋转角度。 [0097] 本发明实施例中,对于浏览的全景照片,在确定全景照片时,全景照片的照片宽度d和旋转角度φ 2 全景照片拍摄时移动端的固定值(如果旋转角度φ 2 在拍摄全景照片的过程中记录,使用记录值; 如果旋转角 φ 2 拍摄时不记录,可以使用一些参考值,如180度或360度作为旋转角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,需要设置一个合适的旋转角度阈值φ 1 可以预设。 如果预设的旋转角度阈值 φ 1 固定,则确定全景照片在旋转过程中移动的最小位移。 在浏览全景照片的过程中,实时检测确定移动终端的旋转角度,如果确定移动终端的旋转角度达到预设的旋转角度阈值φ 1 ,全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0098] 在本发明实施例中,移动终端的旋转角度可以是移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,则可以认为上一次移动全景照片时,移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为一个不断执行和重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值 φ 1,可以将移动终端的初始旋转角度设置为0,检测确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值移动全景照片。 例如,将移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 -1度,全景照片不动; 当移动终端旋转到 φ 1 度,全景照片移动到最小位移,重置旋转角度,继续检测移动终端的旋转角度; 当移动终端旋转到 φ 1 度,全景照片再次移动最小位移,如此重复直到移动终端停止旋转。 [0099] 进一步地,在本发明实施例中,移动全景照片的过程可以是立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,就移动全景照片。 ; 例如,预设的旋转角度阈值 φ 1 为 5 度,一旦旋转角度达到 5 度,全景照片将移动最小位移。 移动全景照片的过程也可以是延迟执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后的一段时间内,将全景照片移动最小位移。 临界点。 [0100] 移动终端的旋转角度还可以是移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以是 随着用户移动移动终端而不断累积的值。 在这种情况下,可以在全景照片移动的位移和旋转角度之间设置成正比关系。 即,移动终端的旋转角度越大,表示全景照片移动的位移越大,移动终端的旋转角度越小,表示全景照片移动的位移越小。 [0101] 上述全景照片的移动方式和最小位移的确定方式还可以有其他实施例,本发明对其具体实施方式不作限定。 [0102] 小号 205 :以沉浸式浏览模式呈现全景照片。 [0103] 本发明实施例在以沉浸式浏览方式实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种呈现全景照片的方式可以使用现有的实施方案,例如在呈现全景照片时,在使全景照片适应显示屏尺寸的过程中可以使用现有的实施方式。 [0104]根据本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端旋转方向相反的方向移动最小位移并呈现。 使用本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,无需在移动终端的屏幕上手动滑动来浏览全景照片,方便快捷。 在操作上很方便。 [0105] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,本发明当然不限于此。 [0106] 本发明实施例提供的全景照片在移动终端呈现的控制方法的实现,是基于拍摄全景照片时保存的照片参数,例如,照片参数为拍摄的角度。 移动终端旋转和拍摄全景照片时移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的在移动终端中呈现全景照片的方法,该方法在全景照片拍摄时也可以与现有的全景照片拍摄不同。 本发明以下实施例结合实际案例,以举例的方式描述全景照片的拍摄过程和浏览过程。 [0107] 图9A示出了根据本发明实施例的全景照片拍摄过程的实现示意图。 如图9A所示,实施过程包括以下步骤。 [0108] 小号 301 :启用全景拍摄模式。 [0109] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0110] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0111] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0112] 在本发明实施例中,移动终端的旋转角度可以通过陀螺传感器在S开始的角度来确定。 302 旋转。 [0113] 小号 305 :保存拍摄的全景照片的属性信息。 [0114] 在本发明实施例中,保存的全景照片属性信息至少包括照片类型、拍摄角度和照片尺寸,其中照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0115] 可选的,在本发明实施例中,保存的全景照片的属性信息还可以包括移动终端在拍摄全景照片时的旋转方向,该旋转方向例如可以是从右到左, 当然,也可能是从左到右。 [0116] 图9B示出了根据本发明实施例的浏览全景照片的过程的实现示意图。 如图9B所示,实现过程包括以下步骤: [0117] 小号 401 :检测用户浏览的照片类型。 [0118] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行 S 403 ; 否则,以普通照片浏览模式浏览照片。 [0119] 小号 403 :当检测到用户触发用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0120] 小号 404 :用户通过旋转移动终端浏览全景照片。 [0121] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 确定的具体过程可以参见上述实施例的相关描述。 [0122] 小号 406 :根据S中确定的放置方向确定移动终端在相应轴向上的旋转角度 405 陀螺传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端沿Z方向旋转的角度 轴,当移动终端的放置方向为垂直放置方向时,确定移动终端沿X轴或Y轴方向旋转的角度。 [0123] 小号 407 :判断是否在S中确定的旋转角度 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0124] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移。 [0125] 小号 409 :检测移动端的放置方向和旋转角度; 当移动终端的放置方向发生变化时,执行S 405 ,当旋转角度发生变化时,执行 S 407 . [0126] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,及时调整全景照片的移动。 [0127] 本发明实施例提供的移动终端全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动滑动。 移动终端屏幕浏览全景照片。 [0128] 在上述实施例提供的移动终端中全景照片的呈现方法的基础上,本发明实施例还提供了一种装置 900 用于在移动终端中呈现全景照片。 如图 10A 所示,该装置 900 包括检测单元 901 , 确定单元 902 , 和一个呈现单元 903 . [0129] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给确定单元 902 其中,沉浸式浏览模式是全景照片随着移动终端旋转而移动的浏览模式。 [0130] 确定单元 902用于接收检测单元发送的检测结果 901 ; 如果检测结果为检测到触发指令,则检测确定移动终端的旋转角度,并将确定的移动终端旋转角度发送给呈现单元 903 . [0131] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度,移动并呈现移动终端中正常呈现的全景照片。 [0132] 在第一种实施方式中,确定单元 902 用于确定移动终端的旋转角度如下,确定移动终端在旋转过程中所处的放置方向,根据放置方向确定移动终端的旋转角度。 [0133] 在第二种实施方式中,确定单元 902 用于通过如下方式确定移动终端在旋转过程中所处的放置方向:检测移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角。 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端的屏幕所在的位置; 根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角,确定移动终端在旋转过程中所处的放置方向。 [0134] 在第三种实施方式中,确定单元 902 用于通过如下方式,根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定移动终端所在的放置方向 旋转过程中:当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端所处的放置方向 位于旋转过程中的是垂直放置方向; 当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,确定移动终端所在的放置方向为旋转 工艺是水平放置方向。 [0135] 在第四种实施方式中,确定单元 902 用于根据放置方向通过如下方式确定移动终端的旋转角度: 如果确定旋转过程中移动终端所处的放置方向为水平放置方向,则使用 以参考三维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向的旋转角度作为移动终端的旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为垂直放置方向,则使用参考三轴中的X轴方向或Y轴方向 将一维坐标系作为移动终端在旋转过程中对应的轴向,使用移动终端旋转的角度 h相对于轴向方向作为移动终端的旋转角度。 [0136] 在第五种实施方式中,所述装置还包括判断单元 904 ,如图10B所示,其中在呈现单元之前 903判断单元根据确定的旋转角度移动在移动终端中以普通模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0137] 在第六种实施方式中,所述确定单元 902 还用于呈现单元之前 903 根据确定的旋转角度移动在移动终端中以普通模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,移动终端在全景拍摄时的旋转角度 拍摄照片, 以及全景照片拍摄时沿移动终端旋转方向的照片宽度, 呈现单元 903 用于将在移动终端中以正常模式呈现的全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量的移动终端以如下方式移动。 [0138] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供提示信息,用于指示移动终端旋转。 [0139] 在第八种实施方式中,所述装置还包括:获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,发送给提示单元 905 、获取的拍摄照片时保存的移动终端的旋转方向,以及提示单元 905 用于通过以下方式提供用于指示移动终端旋转的提示信息: 根据获取单元获取的旋转方向,提供用于指示移动终端旋转的提示信息 906 . [0140] 需要说明的是,对于本发明实施例中图10A至图10D提供的移动终端中全景照片的呈现装置,如果不对移动终端中全景照片的呈现过程进行描述, 足够详细的可以参见方法实施例的相关描述,在此不再赘述。 [0141] 根据本发明实施例提供的移动终端全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动滑动。 移动终端屏幕浏览全景照片。 [0142] 基于上述实施例提供的移动终端中全景照片的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动终端 1000 包括输入设备 1001 , 一个传感器 1002 , 一个处理器 1003 , 和显示屏 1004 , 其中输入设备 1001 用于输入触发指令,用于指示移动终端进入沉浸式浏览模式,所述沉浸式浏览模式为全景照片随着移动终端旋转而移动的浏览模式,所述传感器 1002 所述处理器,用于检测所述移动终端的旋转角度, 1003 用于当检测到输入设备输入触发指令时1001 ,根据检测确定的旋转角度,移动在移动终端中以正常模式呈现的全景照片,以及显示屏幕 1004 配置为呈现全景照片。 [0143] 在本发明实施例中,输入设备可以是一个或多个 1001 ,例如输入设备 1001 可以是显示屏或按钮,可以与处理器集成 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可以连接到处理器 1003 使用有线连接(例如,电缆/端口)或无线连接(例如,蓝牙)。 [0144] 处理器 1003 可以在单个芯片、多个芯片或多个电子元件上实现,并且可以使用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0145] 可能有一个或多个传感器 1002 , 其中传感器 1002 可能有也可能没有操作处理功能。 例如,传感器 1002 在本发明实施例中,可以是重力传感器和陀螺仪传感器中的至少一种。 [0146] 在本发明实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0147] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0148] 在第二种实施方式中,传感器 1002 用于通过如下方式确定移动终端在旋转过程中所处的放置方向:检测移动终端的重力方向相对于参考三坐标的X-Y平面方向的夹角。 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端的屏幕所在的位置; 根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角,确定移动终端在旋转过程中所处的放置方向。 [0149] 在第三种实施方式中,传感器 1002 用于通过如下方式,根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定移动终端所在的放置方向 旋转过程中:当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端所处的放置方向 位于旋转过程中为垂直放置方向,当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角大于45度时,判断为 移动终端在旋转过程中所处的放置方向为水平放置方向。 [0150] 在第四种实施方式中,传感器 1002用于根据放置方向通过如下方式确定移动终端的旋转角度: 如果确定旋转过程中移动终端所处的放置方向为水平放置方向,则使用 以参考三维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,以移动终端相对于轴向的旋转角度作为移动终端的旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为垂直放置方向,则使用参考三轴中的X轴方向或Y轴方向 将一维坐标系作为移动终端在旋转过程中对应的轴向,使用移动终端旋转的角度 h相对于轴向方向作为移动终端的旋转角度。 [0151] 在第五种实施方式中,处理器 1003 还用于根据确定的旋转角度,在移动终端中以正常模式呈现的全景照片在移动之前,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0152] 在第六种实施方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,在移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值,确定全景照片的最小位移,所述全景照片的旋转角度。 拍摄全景照片时的移动终端,以及拍摄全景照片时沿移动终端旋转方向的全景照片的照片宽度,以及处理器 1003 用于以如下方式移动移动终端中正常模式呈现的全景照片:将全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0153] 在第七种实施方式中,处理器 1003 还用于当检测到所述触发指令由所述输入设备输入时 1001 ,提供提示信息,用于指示移动终端旋转。 [0154] 在第八种实施方式中,处理器 1003 还用于在提供用于指示移动终端旋转的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向, 处理器 1003 用于通过以下方式提供用于指示移动终端旋转的提示信息: 提供用于指示根据获取的旋转方向旋转移动终端的提示信息。 [0155] 需要说明的是,对于本发明实施例中图11提供的移动终端,其实现控制全景照片在移动终端中显示的过程如描述不充分,可参见相关 以上为方法实施例的描述,在此不再赘述。 [0156] 根据本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片会随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,无需手动滑动 移动终端屏幕浏览全景照片。 [0157]本领域技术人员应当理解,本发明实施例可以作为方法、系统或者计算机程序产品来提供。 因此,本发明可以采用纯硬件实施例、纯软件实施例或软件和硬件结合的实施例的形式。 此外,本公开可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0158] 参考根据本公开实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述本公开。 应当理解,计算机程序指令可以用于实现流程图和/或框图中的每个过程和/或每个块以及流程图和/或框图中的过程和/或块的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器以生成机器,以便由计算机或任何处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0159] 这些计算机程序指令还可以存储在计算机可读存储器中,该存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,以便存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能。 [0160] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0161] 尽管已经描述了本公开的一些优选实施例,但是本领域技术人员一旦了解了基本的发明概念,就可以对这些实施例进行改变和修改。 因此,以下权利要求旨在解释为覆盖优选实施例以及落入本公开范围内的所有变化和修改。 [0162] 显然,本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的范围。 本公开旨在覆盖这些修改和变化,只要它们落入由以下权利要求及其等效技术限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:27.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CA2966400A1(String), 1049694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CA2966400C(String), 1049695(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519A(String), 1049696(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519B(String), 1048800(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241A(String), 1049697(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241B(String), 1048801(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US10222877B2(String), 1049698(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US10649546B2(String), 1049699(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US11126275B2(String), 1049700(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20150363915A1(String), 1049701(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20170212609A1(String), 1049702(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20190171300A1(String), 1049703(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20200241657A1(String), 1049704(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US9621802B2(String), 1049705(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), WO2016004554A1(String), 1049706(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104471519B(String), CN104471519B(String), 1600963200(Integer), 271404(Integer), 185688(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185960(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185960(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185960(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185960(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:28.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185960(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10649546B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.513 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.514 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.514 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10649546B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US16/266498(String), 1549209600(Integer), US10649546B2(String), 1589212800(Integer), 1589212800(Integer), 美国(String), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | JP2006129329A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185961(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d23f8b7c6f13428badb55064deaf659a.png(String), 185961(Integer), d23f8b7c6f13428badb55064deaf659a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.750 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.750 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.750 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US10649546B2(String), A method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. A trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, complexity of panoramic photo browsing can be reduced, which makes it convenient for a user to browse a panoramic photo.(String), 一种全景照片在移动终端中的呈现方法、装置及移动终端。 检测用于指示移动终端进入沉浸式浏览模式的触发指令,沉浸式浏览模式为全景照片随移动终端旋转移动的浏览模式。 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。 通过本发明,可以降低全景照片浏览的复杂度,方便用户浏览全景照片。(String), US16/266498(String), 1549209600(Integer), US10649546B2(String), 1589212800(Integer), 1589212800(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | JP2006129329A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), \20230420\d23f8b7c6f13428badb55064deaf659a.png(String), 20(Integer), 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 1. A method for presenting a panoramic photo using a mobile terminal, the method comprising:photographing the panoramic photo while the mobile terminal is moving in a first direction;receiving an instruction for entering an immersive browsing mode; andperforming the following operations in the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 1.一种使用移动终端呈现全景照片的方法,该方法包括:移动终端在第一方向移动时拍摄全景照片;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下进行以下操作:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 2. The method of claim 1, wherein the first direction is either from left to right or from right to left.(String), 2.如权利要求1所述的方法,其中第一个方向是从左到右或从右到左。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 3. The method of claim 2, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 3.如权利要求2所述的方法,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 4. The method of claim 1, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 4.如权利要求1所述的方法,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 5. The method of claim 1, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 5.如权利要求1所述的方法,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 6. The method of claim 1, further comprising:displaying the panoramic photo in a normal mode that is different than the immersive browsing mode;displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 6.如权利要求1所述的方法,还包括:以不同于沉浸式浏览模式的正常模式显示全景照片;在正常模式下显示图标;检测图标上的输入;和响应于检测到图标上的输入而进入沉浸式浏览模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 7. The method of claim 1, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 7.如权利要求1所述的方法,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 8. The method of claim 1, wherein rotation of the mobile terminal in either the first direction or the second direction is detected by a gyro sensor of the mobile terminal.(String), 8.如权利要求1所述的方法,其中移动终端沿第一方向或第二方向的旋转由移动终端的陀螺仪传感器检测。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 9. A mobile terminal, comprising:one or more processors; anda memory coupled to the one or more processors and comprising instructions that, when executed by the one or more processors, cause the mobile terminal to:photograph a panoramic photo while the mobile terminal is moving in a first direction;receive an instruction for entering an immersive browsing mode; andperform the following operations in the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 9.移动终端,包括:一个或多个处理器;和存储器耦合到一个或多个处理器并包括指令,当由一个或多个处理器执行时,使移动终端:移动终端在第一方向移动时拍摄全景照片;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下进行以下操作:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 10. The mobile terminal of claim 9, wherein the first direction is either from left to right or from right to left.(String), 10.如权利要求9所述的移动终端,其中第一个方向是从左到右或从右到左。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 11. The mobile terminal of claim 10, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 11.如权利要求10所述的移动终端,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 12. The mobile terminal of claim 9, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 12.如权利要求9所述的移动终端,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 13. The mobile terminal of claim 9, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 13.如权利要求9所述的移动终端,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 14. The mobile terminal of claim 9, wherein the instructions further cause the mobile terminal to:display the panoramic photo in a normal mode that is different than the immersive browsing mode;display an icon in the normal mode;detect an input on the icon; andenter the immersive browsing mode in response to detecting the input on the icon.(String), 14.如权利要求9所述的移动终端,其中该指令进一步使移动终端:以不同于沉浸式浏览模式的正常模式显示全景照片;在正常模式下显示一个图标;检测图标上的输入;和响应于检测到图标上的输入进入沉浸式浏览模式。(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 15. The mobile terminal of claim 9, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 15.如权利要求9所述的移动终端,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 16. The mobile terminal of claim 9, further comprising a gyro sensor coupled to the one or more processors and configured to detect rotation of the mobile terminal in either the first direction or the second direction.(String), 16.如权利要求9所述的移动终端,还包括陀螺仪传感器耦合到一个或多个处理器并被配置为检测移动终端在第一方向或第二方向上的旋转。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 17. A non-transitory computer-readable storage medium comprising instructions that, when executed by a mobile terminal, cause the mobile terminal to:photograph a panoramic photo while the mobile terminal is moving in a first direction;receive an instruction for entering an immersive browsing mode; andperform the following operations in the immersive browsing mode:displaying only a first part of the panoramic photo;displaying an indication to prompt a user to rotate the mobile terminal;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 17.一种非暂时性计算机可读存储介质包括指令,当由移动终端执行时,使移动终端:移动终端在第一方向移动时拍摄全景照片;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下进行以下操作:仅显示全景照片的第一部分;显示提示用户旋转移动终端的提示;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 18. The non-transitory computer-readable storage medium of claim 17, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 18.如权利要求17所述的非暂时性计算机可读存储介质,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 19. The non-transitory computer-readable storage medium of claim 17, wherein the first direction is either from left to right or from right to left.(String), 19.如权利要求17所述的非暂时性计算机可读存储介质,其中第一个方向是从左到右或从右到左。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:29.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185961(Integer), 20. The non-transitory computer-readable storage medium of claim 19, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 20.如权利要求19所述的非暂时性计算机可读存储介质,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185961(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 15/483,724 filed on Apr. 10, 2017, the U.S. patent application Ser. No. 15/483,724 is a continuation of U.S. patent application Ser. No. 14/735,625 filed on Jun. 10, 2015, now U.S. Pat. No. 9,621,802, which is a continuation of International Patent Application No. PCT/CN2014/079950 filed on Jun. 16, 2014. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present disclosure. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present disclosure. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present disclosure. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present disclosure. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present disclosure. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present disclosure. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present disclosure. [0046]FIGS. 10A, 10B, 10C, and 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present disclosure, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present disclosure, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps. [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present disclosure, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present disclosure, there may be multiple implementation manners for implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present disclosure in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps. [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present disclosure, a user may input, using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present disclosure, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present disclosure, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present disclosure, in order to implement immersive mode browsing, the user needs to rotate the mobile (String), 相关申请的交叉引用 [0001] 该申请是美国专利申请序列号的延续。 2017 年 4 月 10 日提交的第 15/483,724 号美国专利申请序列号。 第 15/483,724 号是美国专利申请序列号的延续。 2015 年 6 月 10 日提交的第 14/735,625 号,现为美国专利。 美国专利第 9,621,802 号,是 2014 年 6 月 16 日提交的国际专利申请号 PCT/CN2014/079950 的继续申请。所有上述申请的全部内容通过引用并入本文。 技术领域 [0002] 本 发明涉及通信技术领域,尤其涉及一种移动终端中全景照片的呈现方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,移动终端的使用范围和环境也越来越多样化。 例如,目前很多移动终端,如手机、个人数字助理、个人电脑等都具有全景拍摄的功能。 [0004] 当移动终端进行全景拍摄时,用户旋转移动终端拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 然后可以将多张拍摄的照片按照上述的拼接原理拼接成一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,会在全景照片上浏览到比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端中呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作较为复杂。 概括 [0006] 本发明实施例提供一种全景照片在移动终端中的呈现方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 第一方面,提供了一种全景照片在移动终端中的呈现方法,包括:检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为浏览模式。 其中全景照片随着移动终端的旋转而移动,若检测到触发指令,则检测并确定移动终端的旋转角度,根据确定的旋转角度移动呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实现方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009]结合第一方面的第一种实现方式,在第二种实现方式中,所述确定移动终端在旋转过程中所处的放置方向包括检测移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考的Z轴 三维坐标系垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于参考三维X-Y平面方向的夹角确定- 维度坐标系,移动终端在旋转过程中所处的放置方向。 [0010] 结合第一方面的第二种实现方式,在第三种实现方式中,所述根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为竖直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0011] 结合第一方面的第二种实现方式或第一方面的第三种实现方式,在第四种实现方式中,所述根据放置方向确定移动终端的旋转角度包括: 其中,旋转过程中移动终端所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为旋转过程中移动终端对应的轴向。 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者判断旋转过程中移动终端所处的放置方向为竖直放置方向 ,将参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 分别以轴向为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实现方式,在第五种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013]结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括确定: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动终端中以正常模式呈现的全景照片移动包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实现方式中,所述检测确定移动终端的旋转角度之前,还包括提供用于指示旋转移动终端的提示信息。 [0015] 结合第一方面的第七种实现方式,在第八种实现方式中,所述提供用于指示旋转移动终端的提示信息之前,所述方法还包括: 获取旋转时保存的移动终端的旋转方向。 拍摄全景照片,提供用于指示旋转移动终端的提示信息包括:根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0016] 第二方面,提供了一种全景照片在移动终端中的呈现装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,所述触发指令用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元,所述沉浸式浏览模式为全景照片随着移动终端移动的浏览模式。 旋转,所述判断单元,用于接收检测单元发送的检测结果,若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送给呈现单元,呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0017] 结合第二方面,在第一种实现方式中,所述确定单元用于通过以下方式确定所述移动终端的旋转角度,确定所述移动终端在旋转过程中所处的放置方向,并确定 移动终端根据放置方向的旋转角度。 [0018] 结合第二方面的第一种实现方式,在第二种实现方式中,所述确定单元具体用于通过如下方式确定移动终端在旋转过程中检测角度的放置方向。 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 定位,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端在rota中的放置方向 化过程。 [0019]结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元,用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,通过如下方式确定: 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向相对于参考三维的X-Y平面方向的夹角 -维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于该方向的夹角 参考三​​维坐标系的X-Y平面的夹角大于45度,确定th e 旋转过程中移动终端所处的放置方向为水平放置方向。 [0020] 结合第二方面的第二种实现方式或第二方面的第三种实现方式,在第四种实现方式中,所述确定单元,用于通过以下方式,根据所述移动终端的旋转角度确定所述移动终端的旋转角度。 放置方向若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 rotation process为垂直放置方向,参考中使用X轴方向或Y轴方向 以三维坐标系作为移动终端在旋转过程中对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实现方式,在第五种实现方式中,所述装置还包括判断单元,所述判断单元根据所述确定的旋转角度,在所述呈现单元移动前,确定所述全景图 在移动终端中以正常模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元还用于在所述呈现单元根据确定的旋转角度移动之前,以正常模式呈现的全景照片处于 移动终端,根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 呈现单元,用于将移动终端中正常模式呈现的全景照片按如下方式移动,使全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0023] 结合第二方面,在第七种实现方式中,所述装置还包括提示单元,所述提示单元用于接收所述检测单元发送的检测结果; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示旋转移动终端的提示信息。 [0024]结合第二方面的第七种实现方式,在第八种实现方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄所述全景照片时保存的所述移动终端的旋转方向 , 向提示单元发送获取的拍摄照片时保存的移动终端的旋转方向, 提示单元用于通过以下方式提供用于指示旋转的提示信息 移动终端根据获取单元获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0025] 第三方面,提供了一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于在检测到输入设备输入触发指令时,根据检测确定的旋转角度移动移动终端中以正常模式呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实现方式,在第二种实现方式中,所述传感器用于在检测重力角度的旋转过程中,通过如下方式确定所述移动终端所处的放置方向 移动终端的方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 ,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端的重力方向与相对方向的夹角确定 参考三​​维坐标系的X-Y平面,旋转过程中移动终端所处的放置方向 秒。 [0028] 结合第三方面的第二种实现方式,在第三种实现方式中,所述传感器用于根据所述移动终端的重力方向相对于X-Y方向的夹角,通过如下方式进行判断 参考三​​维坐标系的平面,移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角时移动终端在旋转过程中所处的放置方向 坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面大于45度,确定放置 旋转过程中移动终端所处的方向为水平放置方向。 [0029]结合第三方面的第二种实现方式或第三方面的第三种实现方式,在第四种实现方式中,所述传感器,用于通过如下方式确定所述移动终端根据放置的旋转角度 方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向作为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 旋转过程为垂直放置方向,参考三中X轴方向或Y轴方向 移动终端在旋转过程中对应的轴向为维坐标系,移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,移动所述移动设备中以正常模式呈现的全景照片。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于,在移动终端中以正常模式呈现的全景照片根据确定的旋转角度移动之前,确定 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 拍摄后,处理器用于移动终端中正常模式下呈现的全景照片,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0032] 结合第三方面,在第七种实现方式中,处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示所述移动终端旋转的提示信息之前,获取所述移动终端的旋转方向,即 拍摄全景照片时保存, 处理器用于按照以下方式提供用于指示旋转移动终端的提示信息, 提供用于指示旋转移动终端的提示信息 获取的旋转方向。 [0034] 本发明实施例提供的一种移动终端全景照片呈现方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测到,检测并确定移动终端的旋转角度; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . 附图说明 [0035]为更加清楚地描述本发明实施例的技术方案,下面对实施例描述所需的附图进行简单介绍。 [0036] 图1为本发明实施例提供的全景照片在移动终端中的呈现方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一种实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端的旋转角度的过程的示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所处放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实现示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实现示意图。 [0043] 图8是根据本发明实施例的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例的全景照片浏览过程的实现示意图。 [0046] 图10A、10B、10C和10D是根据本发明实施例的移动终端中全景照片呈现装置的结构示意图。 [0047] 图11为本发明实施例提供的移动终端的结构示意图。 具体实施方式 [0048] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 本发明实施例提供的移动终端中全景照片的呈现方法,全景照片随着移动终端的旋转而移动。 本发明实施例中为了描述方便,将全景照片随着移动终端旋转而移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为“沉浸式浏览模式”。 以下简称正常模式,当然不限于此; 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览以普通模式显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤。 [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 本发明实施例中,若检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :移动呈现,根据S中确定的旋转角度 102 ,移动终端正常显示的全景照片。 [0055] 本发明实施例提供的移动终端中全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . [0056] 在本发明实施例中,实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在用户触发移动终端进入沉浸式浏览模式后立即以预定方式旋转移动终端,该预定方式可以例如通过用户手册预先学习得到。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示旋转移动终端的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供用于指示旋转移动终端的提示信息的实现方式为例,对全景照片在移动终端中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的全景照片在移动终端中的呈现方法的另一种实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤。 [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 在本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,本发明实施例可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 启用控件的启用状态用于确定是否启用沉浸式浏览模式,当检测到启用控件被启用时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面设置沉浸式浏览按钮。 When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选地,本发明实施例还可以在检测到用户正在浏览全景照片时,提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片随着移动终端的旋转而移动。 通常,为了更好的浏览全景照片,可以提供用于指示旋转移动终端的提示信息,以告知用户移动终端需要按照预设方向进行旋转,该预设方向可以为 例如,从左向右旋转,当然,也可以从右向左旋转。 [0064] 在本发明实施例中,提供的提示信息可以是在显示界面上显示的文字信息,当然,也可以是通过语音输出的方式通知的语音信息,本发明实施例对此不做限定。 [0065] 可选的,本发明实施例还可以获取拍摄全景照片时保存的移动终端的旋转方向,并以提示信息的形式通知获取的旋转方向。 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,提示用户根据获取的拍摄全景照片时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,从而及时控制全景照片移动。 [0068] 用户在拍摄全景照片时,一般会将移动终端定位在确定的放置方向上。 但是,用户在浏览全景照片时,很可能会使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了更加准确地浏览全景照片,在旋转过程中,可以根据移动终端所处的放置方向来确定移动终端的旋转角度。 [0069] S中移动终端旋转角度的确定过程 203 本发明实施例可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 本发明实施例中,可以利用设置在移动终端中的重力传感器指示的移动终端的重力方向,确定移动终端所在的放置方向,确定移动终端的旋转角度。 使用设置在移动终端中的陀螺仪传感器的角度。 可选地,在本发明实施例中,用于确定移动终端的放置方向的重力传感器和用于确定移动终端的旋转角度的陀螺仪传感器可以在用于指示移动终端的触发指令时被启用。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选地,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤。 [0074] 小号 2031 a :以移动终端屏幕所在平面为基准,建立参考三维坐标系。 [0075]本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面平行于该平面 移动终端屏幕所在平面,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也根据移动终端的不同放置方向进行旋转。 例如,参考三维坐标系的示意图分别对应图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的夹角 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过在S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选地,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于基准三的X-Y平面方向的夹角- 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为竖直放置方向。 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所处的放置方向 旋转过程中为水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为竖直放置方向,或者为水平放置方向,本发明实施例可以设置为竖直放置方向。 [0081] 本发明实施例中,如果利用移动终端的重力方向相对于基准三的X-Y平面方向的夹角来确定移动终端在旋转过程中所处的放置方向—— S 中的维度坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 . [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 本发明实施例在确定移动终端在旋转过程中所处的放置方向为水平放置方向时,采用参考三维坐标系中Z轴的方向 作为移动终端在旋转过程中对应的轴向; 或者,当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 用作移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,本发明实施例中,上述移动终端在旋转过程中对应的轴向只是为了简化确定移动终端旋转角度的过程,具体的确定方式不作限定。 至此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺仪传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于对应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度移动移动终端正常显示的全景照片。 [0088] 在本发明实施例中,在浏览全景照片时,一般先以普通浏览方式显示全景照片; 例如,可以是分辨率较低的全景照片,或者只有全景照片的最左部分或全景照片的最右部分等部分全景照片显示在手机的显示屏中 终端。 本发明实施例在确定移动终端的旋转角度后,可以移动终端中正常模式显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实施方式对移动终端中正常模式显示的全景照片进行移动。 例如,移动终端在正常模式下显示的全景照片可以沿与移动终端的旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,本发明实施例中,为了实现全景照片的平滑移动,可以预先设置旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现了全景照片的平滑移动。 如果没有达到预设的旋转角度阈值,全景照片可能不会被移动。 [0091] 本发明实施例中,根据确定的移动终端的旋转角度,将移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向在S中移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端的旋转方向相同的方向移动时,也可以采用类似的方式)。 [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,则执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常模式显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,本发明实施例中,为了进一步增强平滑移动的效果,还可以确定最小位移,当控制全景图像沿与移动终端的旋转方向相反的方向移动时, 照片每次移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,可以根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度以及全景照片沿a的照片宽度,确定全景照片的最小位移量。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录并保存,可以是 直接从本发明实施例拍摄全景照片时保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选地,在本发明实施例中,确定全景照片的最小位移可以采用如下方式。 全景照片的最小位移根据公式确定 [0097] s = d ⁢ ⁢ φ 1 φ 2 , 其中s是全景照片的最小位移; d为全景照片的照片宽度; φ 1 为预设旋转角度阈值; φ2为拍摄全景照片时移动终端的旋转角度。 [0098] 本发明实施例中,对于浏览的全景照片,在确定全景照片时,全景照片的照片宽度d和拍摄全景照片时移动终端的旋转角度φ2为固定值(如果 在拍摄全景照片的过程中记录了旋转角度φ2,使用记录的值;如果在拍摄过程中没有记录旋转角度φ2,则可以参考一些参考值,例如180度或360度作为旋转角度。 角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,适当的旋转角度阈值φ 1 可能是预设的。 若预设旋转角度阈值φ 1 固定后,确定全景照片在旋转过程中移动的最小位移量。 在浏览全景照片的过程中,实时检测并判断移动终端的旋转角度,如果判断移动终端的旋转角度达到预设的旋转角度阈值φ 1 ,全景照片沿与移动终端旋转方向相反的方向移动最小位移。 [0099] 本发明实施例中,移动终端的旋转角度可以为移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,可以认为上一次移动全景照片时移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为一个持续执行并重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值φ 1,可以将移动终端的初始旋转角度设置为0,检测并确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值来移动全景照片。 例如,移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 −1度,全景照片不动; 当移动端旋转到φ 1 度,全景照片移动最小位移,重新设置旋转角度,继续检测移动端的旋转角度; 当移动端旋转到φ 1 度,全景照片再次移动最小位移,如此循环直到移动终端停止转动。 [0100] 进一步地,在本发明实施例中,移动全景照片的过程可以是立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,则移动全景照片。 ; 例如,预设的旋转角度阈值φ 1 为5度,当旋转角度达到5度时,全景照片移动到最小位移。 移动全景照片的过程也可以是延时执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后,在一段时间内将全景照片移动最小位移量 临界点。 [0101] 移动终端的旋转角度还可以为移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以为a 随着用户移动移动终端不断积累价值。 此时,可以设置全景照片移动的位移与旋转角度成正比关系。 即,移动终端旋转角度越大,全景照片移动的位移越大,移动终端旋转角度越小,全景照片移动的位移越小。 [0102] 上述移动全景照片的方式和最小位移的确定方式还可以有其他实施方式,本发明不对其具体实施方式进行限定。 [0103] 小号 205 :以沉浸式浏览方式呈现全景照片。 [0104] 本发明实施例在沉浸式浏览模式下实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种全景照片的呈现方式可以采用现有的实施方案,例如,在呈现全景照片时,在将全景照片适配显示屏尺寸的过程中可以采用现有的实施方式。 [0105]本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移并呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,而不需要手动在移动终端的屏幕上滑动来浏览全景照片,简单易行。 在操作方面方便。 [0106] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,当然不限于此。 [0107] 本发明实施例提供的控制全景照片在移动终端中呈现的方法的实现基于拍摄全景照片时保存的照片参数,该照片参数例如为: 拍摄全景照片时移动终端旋转,移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的移动终端中全景照片的呈现方法,在拍摄全景照片时,该方法也可以区别于现有的全景照片拍摄。 本发明以下实施例结合实际案例,举例说明全景照片的拍摄过程和浏览过程。 [0108] 图9A示出了根据本发明实施例的全景照片拍摄过程的实现示意图。 如图9A所示,实施过程包括以下步骤。 [0109] 小号 301 :启用全景拍摄模式。 [0110] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0111] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0112] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0113] 本发明实施例中,可以通过陀螺仪传感器在S中启动的角度来确定移动终端的旋转角度。 302 旋转。 [0114] 小号 305 :保存拍摄的全景照片的属性信息。 [0115] 本发明实施例中,保存的全景照片的属性信息至少包括照片类型、拍摄角度和照片尺寸,其中,照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0116] 可选地,本发明实施例中,保存的全景照片的属性信息还可以包括拍摄全景照片时移动终端的旋转方向,该旋转方向例如可以为从右向左, 当然,也可能是从左到右。 [0117] 图9B示出了根据本发明实施例的全景照片浏览过程的实现示意图。 如图9B所示,实施过程包括以下步骤。 [0118] 小号 401 :检测用户浏览的照片类型。 [0119] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行S 403 ; 否则,以正常的照片浏览方式浏览照片。 [0120] 小号 403 :当检测到用户触发了用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0121] 小号 404 :用户通过旋转移动端浏览全景照片。 [0122] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 具体的确定过程可以参见前述实施例的相关描述。 [0123] 小号 406 :根据S中确定的放置方向,确定移动终端在相应轴向的旋转角度 405 以及陀螺仪传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端在Z方向上旋转的角度 -轴,当移动终端的放置方向为竖直放置方向时,确定移动终端在X轴或Y轴方向上旋转的角度。 [0124] 小号 407 :判断旋转角度是否在S中确定 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0125] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移量。 [0126] 小号 409 :检测移动终端的放置方向和旋转角度; 当移动端的放置方向改变时,执行S 405 ,当旋转角度发生变化时,执行S 407 . [0127] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,从而及时调整全景照片的移动。 [0128] 本发明实施例提供的移动终端中全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0129] 基于上述实施例提供的移动终端中全景照片的呈现方法,本发明实施例还提供了一种装置 900 用于在移动终端呈现全景照片。 如图 10A 所示,该装置 900 包括一个检测单元 901 , 决定单位 902 , 和一个呈现单元 903 . [0130] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元 902 ,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动的浏览模式。 [0131] 决定单位 902用于接收检测单元发送的检测结果 901 ; 若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的移动终端的旋转角度发送给呈现单元 903 . [0132] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0133] 在第一种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端的旋转角度,确定移动终端在旋转过程中所处的放置方向,根据放置方向确定移动终端的旋转角度。 [0134] 在第二种实施方式中,所述确定单元 902 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0135] 在第三种实施方式中,确定单元 902 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 位于旋转过程中的是垂直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 工艺是水平放置方向。 [0136] 在第四种实施方式中,所述确定单元 902 用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0137] 在第五种实施方式中,所述装置还包括判断单元 904 , 如图 10B 所示, 在呈现单元之前 903判断单元根据确定的旋转角度移动移动终端中正常模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0138] 在第六种实施方式中,所述确定单元 902 还配置在呈现单元之前 903 移动,根据确定的旋转角度移动终端中正常模式下呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,全景时移动终端的旋转角度 拍摄全景照片时,全景照片沿移动终端旋转方向的照片宽度,以及呈现单元 903 用于将移动终端中正常模式下呈现的全景照片按照如下方式移动,将全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量。 [0139] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供用于指示旋转移动终端的提示信息。 [0140] 在第八种实施方式中,所述装置还包括获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,并发送给提示单元 905 ,获取拍照时保存的移动终端的旋转方向,以及提示单元 905 用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取单元获取的旋转方向提供用于指示旋转移动终端的提示信息 906 . [0141] 需要说明的是,对于本发明实施例图10A至图10D提供的全景照片在移动终端中的呈现装置,如果不描述在移动终端中实现全景照片的呈现过程 不够详细,可以参见方法实施例的相关描述,在此不再赘述。 [0142] 本发明实施例提供的移动终端中全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0143] 基于上述实施例提供的全景照片在移动终端中的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动端 1000 包括一个输入设备 1001 , 一个传感器 1002 , 处理器 1003 , 和一个显示屏 1004 ,其中输入设备 1001 用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,所述传感器 1002 用于检测移动终端的旋转角度,处理器 1003 用于当检测到输入设备输入触发指令时1001 ,根据检测确定的旋转角度移动移动终端中正常模式呈现的全景照片,显示屏幕 1004 用于呈现全景照片。 [0144] 本发明实施例中,输入设备可以是一个或多个 1001 ,例如,输入设备 1001 可能是显示屏或按钮,可能与处理器集成在一起 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可能连接到处理器 1003 使用有线连接(例如电缆/端口)或无线连接(例如蓝牙)。 [0145] 处理器 1003 可以在单芯片、多芯片或多个电子元件上实现,可以采用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0146] 可能有一个或多个传感器 1002 ,其中传感器 1002 可能有也可能没有运算处理功能。 例如,传感器 1002 在本发明实施例中,可以为重力传感器和陀螺仪传感器中的至少一种。 [0147] 在本公开的该实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0148] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0149] 第二种实现方式,传感器 1002 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0150] 第三种实现方式,传感器 1002 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 旋转过程中位于垂直放置方向,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定 旋转过程中移动终端所处的放置方向为水平放置方向。 [0151] 在第四种实现方式中,传感器 1002用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0152] 在第五种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,将在移动终端中以正常模式呈现的全景照片确定移动终端的旋转角度达到预设的旋转角度阈值。 [0153] 在第六种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移, 拍摄全景照片时的移动终端,以及拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度,以及处理器 1003 用于移动终端中正常模式下呈现的全景照片的移动方式: 将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0154] 在第七种实现方式中,处理器 1003 还用于当检测到输入设备输入触发指令时 1001 ,提供用于指示旋转移动终端的提示信息。 [0155] 在第八种实现方式中,处理器 1003 还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,处理器 1003 用于提供指示旋转移动终端的提示信息的方式如下: 根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0156] 需要说明的是,对于本发明实施例图11提供的移动终端,在移动终端中实现控制全景照片显示的过程如描述不够详细,可以参考相关文献 方法实施例的描述,此处不再赘述。 [0157] 本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0158]本领域的技术人员应该理解,本公开的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本公开可以采用纯硬件实施例、纯软件实施例或结合软件和硬件的实施例的形式。 此外,本公开可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0159] 参考根据本公开的实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述本公开。 应当理解,可以使用计算机程序指令来实现流程图和/或框图中的每个过程和/或每个框以及流程图和/或框图中的过程和/或框的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器生成机器,使得任何计算机或处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0160] 这些计算机程序指令也可以存储在计算机可读存储器中,该计算机可读存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,使得存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程中和/或在框图中的一个或多个块中实现特定功能。 [0161] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程数据处理设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供了用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0162] 尽管已经描述了本公开的一些优选实施例,但是本领域的技术人员在了解基本发明构思后可以对这些实施例进行更改和修改。 因此,所附权利要求旨在被解释为涵盖优选实施例以及落入本公开范围内的所有变化和修改。 [0163] 显然,本领域的技术人员可以对本发明实施例进行各种更改和变型而不脱离本发明实施例的范围。 本公开旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.431 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CA2966400A1(String), 1049694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.502 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CA2966400C(String), 1049695(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519A(String), 1049696(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519B(String), 1048800(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241A(String), 1049697(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241B(String), 1048801(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US10222877B2(String), 1049698(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US10649546B2(String), 1049699(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US11126275B2(String), 1049700(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20150363915A1(String), 1049701(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20170212609A1(String), 1049702(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20190171300A1(String), 1049703(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20200241657A1(String), 1049704(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US9621802B2(String), 1049705(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.936 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), WO2016004554A1(String), 1049706(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:30.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104471519B(String), CN104471519B(String), 1600963200(Integer), 271404(Integer), 185688(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.083 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.083 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.083 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185961(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185961(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185961(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185961(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185961(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10182389B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for restricting usage region of mobile terminal, and mobile terminal(String), 移动终端使用区域限制方法、装置及移动终端(String), US10182389B2(String), A method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal are provided. Cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information, otherwise, the mobile terminal skips accessing a wireless communications network. Hence, the cell identification information of the cell network at the current location is compared with the locked identification information to control cell network access of the mobile terminal.(String), 提供了一种限制移动终端使用区域的方法、装置和移动终端。 可以获得覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络,否则,移动终端跳过接入无线通信网络。 因此,将当前位置的小区网络的小区标识信息与锁定的标识信息进行比较,以控制移动终端的小区网络接入。(String), US15/551131(String), 1423929600(Integer), US10182389B2(String), 1547481600(Integer), 1547481600(Integer), 美国(String), 4(Integer), 5(Integer), 11(Integer), CN101137173A | CN101137214A | CN102984778A | GB2369004A | JP1992373330A | JP1995107550A | JP2012526407A | US20070275717A1 | US20140045505A1 | US20150057003A1 | US5966668A(String), 13(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:31.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185962(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.093 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\597c7c5becbf4051878d8793492658c0.png(String), 185962(Integer), 597c7c5becbf4051878d8793492658c0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for restricting usage region of mobile terminal, and mobile terminal(String), 移动终端使用区域限制方法、装置及移动终端(String), US10182389B2(String), A method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal are provided. Cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information, otherwise, the mobile terminal skips accessing a wireless communications network. Hence, the cell identification information of the cell network at the current location is compared with the locked identification information to control cell network access of the mobile terminal.(String), 提供了一种限制移动终端使用区域的方法、装置和移动终端。 可以获得覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络,否则,移动终端跳过接入无线通信网络。 因此,将当前位置的小区网络的小区标识信息与锁定的标识信息进行比较,以控制移动终端的小区网络接入。(String), US15/551131(String), 1423929600(Integer), US10182389B2(String), 1547481600(Integer), 1547481600(Integer), 美国(String), 3(Integer), 4(Integer), 5(Integer), 11(Integer), CN101137173A | CN101137214A | CN102984778A | GB2369004A | JP1992373330A | JP1995107550A | JP2012526407A | US20070275717A1 | US20140045505A1 | US20150057003A1 | US5966668A(String), \20230420\597c7c5becbf4051878d8793492658c0.png(String), 13(Integer), 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.223 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.223 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 1. A method for restricting a usage region of a mobile terminal, applied to a mobile terminal, comprising:obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, the at least one cell network corresponding to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information comprising at least one of frequency channel number information, and the frequency channel number information and auxiliary cell identification information;determining a cell network having maximum signal strength in the at least one cell network covering the current location of the mobile terminal;sending cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile terminal;determining, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, the region lock instruction comprising the cell identification information corresponding to the cell network having maximum signal strength;determining the cell identification information corresponding to the cell network having maximum signal strength as locked identification information;determining whether the cell identification information comprises cell identification information matching the locked identification information, a parameter of the locked identification information being in a one-to-one correspondence with a parameter of the cell identification information;accessing, by the mobile terminal, a cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information; andskipping access, by the mobile terminal, of a wireless communication network when the cell identification information does not comprise the cell identification information matching the locked identification information.(String), 1.根据权利要求9所述的非暂时性计算机可读存储介质,其中接入锁定的标识信息对应的小区网络包括当小区标识信息中包含与锁定的标识信息匹配的小区标识信息时,移动终端接入锁定的标识信息对应的小区网络,当小区的信号强度为与锁定的标识信息匹配的标识信息不小于预设强度阈值。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.223 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 2. The method according to claim 1, wherein when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information comprises the frequency channel number information and the locked identification information comprises a locked frequency channel number, and wherein when the network standard supported by the mobile terminal is not GSM, the cell identification information comprises the frequency channel number information and the auxiliary cell identification information, and the locked identification information comprises the locked frequency channel number and locked auxiliary identification information.(String), 12.根据权利要求9所述的非暂时性计算机可读存储介质,其中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息包括:移动终端进行频率扫描;和从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.223 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 3. The method according to claim 1, wherein accessing the cell network corresponding to the locked identification information comprises accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information, and when signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold.(String), 13.根据权利要求9所述的非暂时性计算机可读存储介质,其中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息包括:移动终端接收小区广播消息;和从小区广播消息中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 4. The method according to claim 1, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:performing, by the mobile terminal, frequency scanning; andobtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 5. The method according to claim 1, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:receiving, by the mobile terminal, a cell broadcast message; andobtaining, from the cell broadcast message, the cell identification information of the at least one cell network covering the current location of the mobile terminal.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 6. A mobile terminal, comprising:a processor;a memory;a communications interface; anda bus,wherein the processor, the memory, and the communications interface are coupled and communicate with each other using the bus,wherein the memory is configured to store an executable program code, andwherein when executed, the executable program code causes the processor to be configured to:obtain cell identification information of at least one cell network that covers a current location of the mobile terminal, the at least one cell network corresponding to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information comprising at least one of frequency channel number information and the frequency channel number information and auxiliary cell identification information;determine a cell network having maximum signal strength in the at least one cell network covering the current location of the mobile terminal;send the cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile terminal;determine, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, the region lock instruction comprising the cell identification information corresponding to the cell network having maximum signal strength;determine the cell identification information corresponding to the cell network having maximum signal strength as locked identification information;determine whether the cell identification information comprises cell identification information matching the locked identification information, a parameter of the locked identification information being in a one-to-one correspondence with a parameter of the cell identification information;access a cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information; andskipping access of a wireless communication network when the cell identification information does not comprise the cell identification information matching the locked identification information.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 7. The mobile terminal according to claim 6, wherein when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information comprises the frequency channel number information and the locked identification information comprises a locked frequency channel number, and wherein when the network standard supported by the mobile terminal is not the GSM, the cell identification information comprises the frequency channel number information and the auxiliary cell identification information, and the locked identification information comprises the locked frequency channel number and locked auxiliary identification information.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 8. The mobile terminal according to claim 6, wherein the executable program code further causes the processor to be configured to access the cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 9. A non-transitory computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to carry out a method comprising:obtaining cell identification information of at least one cell network that covers a current location of a mobile terminal, the at least one cell network corresponding to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information comprising frequency channel number information, or the frequency channel number information and auxiliary cell identification information;determining a cell network having maximum signal strength in the at least one cell network covering the current location of the mobile terminal;sending cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile terminal;determining, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, the region lock instruction comprising the cell identification information corresponding to the cell network having maximum signal strength;determining the cell identification information corresponding to the cell network having maximum signal strength as locked identification information;determining whether the cell identification information comprises cell identification information matching the locked identification information, a parameter of the locked identification information being in a one-to-one correspondence with a parameter of the cell identification information;accessing, by the mobile terminal, a cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information; andskip access, by the mobile terminal, of a wireless communication network when the cell identification information does not comprise the cell identification information matching the locked identification information.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 10. The non-transitory computer-readable storage medium according to claim 9, wherein when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information comprises the frequency channel number information and the locked identification information comprises a locked frequency channel number, and wherein when the network standard supported by the mobile terminal is not GSM, the cell identification information comprises the frequency channel number information and the auxiliary cell identification information, and the locked identification information comprises the locked frequency channel number and locked auxiliary identification information.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 11. The non-transitory computer-readable storage medium according to claim 9, wherein accessing the cell network corresponding to the locked identification information comprises accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the cell identification information comprises the cell identification information matching the locked identification information, and when signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 12. The non-transitory computer-readable storage medium according to claim 9, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:performing, by the mobile terminal, frequency scanning; andobtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185962(Integer), 13. The non-transitory computer-readable storage medium according to claim 9, wherein obtaining the cell identification information of the at least one cell network covering the current location of the mobile terminal comprises:receiving, by the mobile terminal, a cell broadcast message; andobtaining, from the cell broadcast message, the cell identification information of the at least one cell network covering the current location of the mobile terminal.(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185962(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a U.S. National Stage of International Patent Application No. PCT/CN2015/073113 filed on Feb. 15, 2015, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present disclosure relates to the field of mobile communications, and in particular, to a method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal. BACKGROUND [0003]For a particular purpose, usage ranges of some mobile terminals (for example, mobile phones, point of sale (POS) machines, and a portable wireless broadband apparatus (MIFI)) often need to be restricted. Within only a specified usage range, these mobile terminals can normally use a wireless communication service such as a voice communication service, a short message service, or a data communication service provided by a communications operator. For example, MIFI can be used only in a specified region. When MIFI is in the specified region, MIFI can work normally to provide a wireless network for another device. When MIFI is outside the specified region, MIFI cannot work normally and cannot provide a wireless network for another device. [0004]In other approaches, a usage range of a mobile terminal is restricted by locking a location area code. When a mobile terminal is in a region identified by a locked location area code, the mobile terminal can normally use a wireless communication service. Otherwise, the mobile terminal cannot normally use a wireless communication service. [0005]However, a region identified by a location area code is excessively large, and even a district or a county is in a region identified by a location area code. Therefore, in the other approaches, a usage range of a mobile terminal cannot be restricted precisely. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for restricting a usage region of a mobile terminal, and a mobile terminal to restrict a usage range of a mobile terminal more precisely. Solutions are as follows. [0007]According to a first aspect, a method for restricting a usage region of a mobile terminal is provided. The method is applied to a mobile terminal, and the method includes obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skipping accessing, by the mobile terminal, a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0008]With reference to the first aspect, in a first possible implementation manner, when the network standard supported by the mobile terminal is Global System for Mobile Communications (GSM), the cell identification information is frequency channel number information and the locked identification information includes a locked frequency channel number, and when the network standard supported by the mobile terminal is not GSM, the cell identification information includes frequency channel number information and auxiliary cell identification information, and the locked identification information includes a locked frequency channel number and locked auxiliary identification information. [0009]With reference to the first aspect, in a second possible implementation manner, before determining whether the cell identification information includes cell identification information matching locked identification information, the method further includes determining a cell network having maximum signal strength in the at least one cell network that covers the current location of the mobile terminal, and sending cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile device, determining, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, where the region lock instruction includes the cell identification information corresponding to the cell network having maximum signal strength, and determining the cell identification information corresponding to the cell network having maximum signal strength as the locked identification information. [0010]With reference to the first aspect, in a third possible implementation manner, accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information includes accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the obtained cell identification information includes the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold. [0011]With reference to the first to the third possible implementation manners of the first aspect, in a fourth possible implementation manner, obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal includes performing, by the mobile terminal, frequency scanning, and obtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result, or receiving, by the mobile terminal, a cell broadcast message, and obtaining, from the broadcast message, the cell identification information of the at least one cell network that covers the current location of the mobile terminal. [0012]According to a second aspect, an apparatus for restricting a usage region of a mobile terminal is provided. The apparatus is applied to a mobile terminal, and the apparatus includes a cell identification information obtaining unit, a match determining unit, a network access unit, and a network discarding unit, where the cell identification information obtaining unit is configured to obtain cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information. The match determining unit is configured to determine whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information. The network access unit is configured to access a cell network corresponding to the locked identification information, when the cell identification information obtained by the cell identification information obtaining unit includes the cell identification information matching the locked identification information, and the network discarding unit is configured to skip accessing a wireless communication network when the cell identification information obtained by the cell identification information obtaining unit does not include the cell identification information matching the locked identification information. [0013]With reference to the second aspect, in a first possible implementation manner, when the network standard supported by the mobile terminal is GSM, the cell identification information is frequency channel number information and the locked identification information includes a locked frequency channel number, and when the network standard supported by the mobile terminal is not GSM, the cell identification information includes frequency channel number information and auxiliary cell identification information, and the locked identification information includes a locked frequency channel number and locked auxiliary identification information. [0014]With reference to the second aspect, in a second possible implementation manner, the apparatus further includes a strongest network determining unit, an identification information determining unit, and an identification information locking unit, where before determining, by the match determining unit, whether the cell identification information includes the cell identification information matching the locked identification information, the strongest network determining unit is configured to determine a cell network having maximum signal strength in the at least one cell network that covers the current location of the mobile terminal, and send cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile device. The identification information determining unit is configured to determine, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, where the region lock instruction includes the cell identification information corresponding to the cell network having maximum signal strength, and the identification information locking unit is configured to determine the cell identification information corresponding to the cell network having maximum signal strength as the locked identification information. [0015]With reference to the second aspect, in a third possible implementation manner, the network access unit is further configured to access, by the mobile terminal, the cell network corresponding to the locked identification information when the obtained cell identification information includes the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold. [0016]With reference to the first to the third possible implementation manners of the second aspect, in a fourth possible implementation manner, the cell identification information obtaining unit includes a frequency scanning subunit and/or a broadcast receiving subunit, where the frequency scanning subunit is configured to perform frequency scanning, and obtain the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result, and the broadcast receiving subunit is configured to receive a cell broadcast message, and obtain, from the broadcast message, the cell identification information of the at least one cell network that covers the current location of the mobile terminal. [0017]According to a third aspect, a storage medium is provided. The storage medium is configured to store an application program. When the application program runs, the method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is executed. The method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is applied to a mobile terminal, and the method may include obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skip accessing, by the mobile terminal, a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0018]According to a fourth aspect, an application program is provided. When the application program runs, the method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is executed. The method for restricting a usage region of a mobile terminal in the embodiments of the present disclosure is applied to a mobile terminal, and the method may include obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing, by the mobile terminal, a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skip accessing, by the mobile terminal, a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0019]According to a fifth aspect, a mobile terminal is provided, including a processor, a memory, a communications interface, and a bus, where the processor, the memory, and the communications interface are connected and communicate with each other using the bus. The memory stores executable program code. The processor reads the executable program code stored in the memory to run a program corresponding to the executable program code to perform the following steps of obtaining cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information, determining whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information, and accessing a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information, or skip accessing a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0020]As can be known from the foregoing technical solutions, according to the method and the apparatus for restricting a usage region of a mobile terminal, and the mobile terminal in the embodiments of the present disclosure, cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information. Otherwise, the mobile terminal skips accessing a wireless communications network. In the present disclosure, the cell identification information of the cell network at the current location is compared with the locked identification information, to control cell network access of the mobile terminal. In the present disclosure, because a region corresponding to a cell is smaller than that corresponding to a location area code, a usage range of the mobile terminal can be more precisely restricted. BRIEF DESCRIPTION OF DRAWINGS [0021]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required in the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0022]FIG. 1 is a flowchart of a method for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; [0023]FIG. 2 is a schematic diagram of coverage of a wireless communications network according to an embodiment of the present disclosure; [0024]FIG. 3 is a flowchart of another method for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; [0025]FIG. 4 is a schematic diagram of communication between a control device and a mobile terminal according to an embodiment of the present disclosure; [0026]FIG. 5 is a schematic structural diagram of an apparatus for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; [0027]FIG. 6 is a schematic structural diagram of another apparatus for restricting a usage region of a mobile terminal according to an embodiment of the present disclosure; and [0028]FIG. 7 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0029]To make the objectives, technical solutions, and advantages of the present disclosure clearer and more comprehensible, the following further describes the present disclosure in detail with reference to the accompanying drawings and embodiments. The described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0030]As shown in FIG. 1, an embodiment of the present disclosure provides a method for restricting a usage region of a mobile terminal. The method is applied to a mobile terminal, and the method may include the following steps. [0031]Step S100: Obtain cell identification information of at least one cell network that covers a current location of the mobile terminal, where the cell network corresponds to a wireless communications network corresponding to a network standard supported by the mobile terminal, and the cell identification information is frequency channel number information, or the cell identification information includes frequency channel number information and auxiliary cell identification information. [0032]The mobile terminal may be a mobile phone, a POS machine, an MIFI, or the like. [0033]A cell (also referred to as a cellular cell) is a minimum unit on a wireless communications network, and multiple cells may form a region corresponding to a location area code. A cell is smaller than a region corresponding to a location area code. [0034]The frequency channel number information is a number of a fixed frequency. To avoid interference caused by same frequency channel number information, frequency channel number information of cells in a region is different from each other. Frequency channel number information of cells is different from each other in a wide area of a communications apparatus that uses a standard of GSM. Therefore, frequency channel number information, obtained by the mobile terminal, of cells of the wireless communications network that covers the current location is different from each other. [0035]A frequency multiplexing technology is used in a network standard such as Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), or Long Term Evolution (LTE). Therefore, frequency channel number information, obtained by the mobile terminal, of the cell network that covers the current location may be the same. Therefore, to reduce misoperations, auxiliary cell identification information of a cell may also be obtained to identify the cell. In WCDMA, auxiliary cell identification information is a primary scrambling code. In TD-SCDMA, auxiliary cell identification information is a scrambling code. In LTE, auxiliary cell identification information is a physical layer cell number. Cells can be more precisely distinguished using frequency channel number information of the cells and auxiliary cell identification information of the cells, to reduce misoperations. The cell identification information may consist of the frequency channel number information and the auxiliary cell identification information. [0036]It may be understood that, different frequency bands are used in different network standards. For example, frequency channel numbers of a frequency band 900 megahertz (MHz) and a frequency band 1800 MHz are used in the GSM standard. When the mobile terminal supports only the GSM standard, frequency channel number information of the frequency band 900 MHz and the frequency band 1800 MHz may be obtained. [0037]Further, alternatively, only cell identification information of at least one cell network of a first communications operator that covers the current location of the mobile terminal may be obtained. The first communications operator is a communications operator that provides a subscriber identity module card/universal subscriber identity module card of the mobile terminal. [0038]For example, for the frequency band 900 MHz in the GSM standard, a downlink frequency band of CHINA MOBILE is 935-954 MHz, and a downlink frequency band of CHINA UNICOM is 954-960 MHz. When the subscriber identity module card/universal subscriber identity module card of the mobile terminal is provided by CHINA MOBILE, only frequency channel number information of 935-954 MHz may be obtained. [0039]A wireless communication signal of a cell network is provided by a base station, and one base station may provide a wireless communication signal for one or more cell networks. When multiple cell networks cover the current location of the mobile terminal, the mobile terminal may obtain wireless communication signals of the multiple cell networks provided by a base station. As shown in FIG. 2, it is assumed that a base station 201 provides a wireless communication signal for a cell network A, a base station 202 provides a wireless communication signal for a cell network B, and a base station 203 provides a wireless communication signal for a cell network C, and the wireless communication signals of the three cell networks A, B, and C cover a current location of the mobile terminal 200. In this case, the mobile terminal 200 may obtain cell identification information of the three cell networks A, B, and C at the current location. [0040]The mobile terminal 200 may obtain the cell identification information by performing frequency scanning or receiving a cell broadcast message. Further, step S100 may include performing, by the mobile terminal, frequency scanning, and obtaining the cell identification information of the at least one cell network that covers the current location of the mobile terminal from a frequency scanning result, or receiving, by the mobile terminal, a cell broadcast message, and obtaining, from the broadcast message, the cell identification information of the at least one cell network that covers the current location of the mobile terminal. [0041]Step S200: Determine whether the cell identification information includes cell identification information matching locked identification information, where a parameter of the locked identification information is in a one-to-one correspondence with a parameter of the cell identification information. [0042]When the network standard supported by the mobile terminal is GSM, the cell identification information is frequency channel number information and the locked identification information includes a locked frequency channel number, and when the network standard supported by the mobile terminal is not GSM, the cell identification information includes frequency channel number information and auxiliary cell identification information, and the locked identification information includes a locked frequency channel number and locked auxiliary identification information. [0043]Step S300: The mobile terminal accesses a cell network corresponding to the locked identification information, when the obtained cell identification information includes the cell identification information matching the locked identification information. [0044]Step S400: The mobile terminal skips accessing a wireless communication network when the obtained cell identification information does not include the cell identification information matching the locked identification information. [0045]Further, a network access function of the mobile terminal may be locked in a particular period to not access a wireless communications network in order to discard the network. For example, cell handover and cell reselection functions of the mobile terminal are locked. After a period during which the network access function of the mobile terminal is locked is beyond the particular period, go back to step S100. [0046]The locked identification information may be cell identification information of a cell covered in a restricted region. The restricted region is a usage region, such as a factory, to which the mobile terminal needs to be restricted. There may be one or at least two pieces of locked identification information. [0047]Optionally, when the obtained cell identification information includes only the cell identification information matching the locked identification information, the cell network corresponding to the locked identification information may be accessed. When the obtained cell identification information includes at least two pieces of cell identification information matching the locked identification information, a cell network corresponding to one piece of the locked identification information may be accessed. Preferably, a cell network that corresponds to the locked identification information and has maximum signal strength may be accessed. [0048]Optionally, step S300 may include accessing, by the mobile terminal, the cell network corresponding to the locked identification information when the obtained cell identification information includes the cell identification information matching the locked identification information, and signal strength of the cell identification information matching the locked identification information is not less than a preset strength threshold. [0049]In some cases, although the mobile terminal can access the cell network corresponding to the locked identification information, the cell network has relatively poor signal strength and cannot provide a desirable communication service for a user. Therefore, to ensure that a desirable communication service is provided for a user, the cell network corresponding to the locked identification information may be accessed when signal strength is relatively high. [0050]According to the method for restricting a usage region of a mobile terminal provided in this embodiment of the present disclosure, cell identification information of a cell network that covers a current location of a mobile terminal may be obtained. When the obtained cell identification information includes cell identification information matching locked identification information, the mobile terminal accesses a cell network corresponding to the locked identification information. Otherwise, the mobile terminal skips accessing a wireless communications network. In the present disclosure, the cell identification information of the cell network at the current location is compared with the locked identification information to control cell network access of the mobile terminal. In the present disclosure, because a region corresponding to a cell is smaller than that corresponding to a location area code, a usage range of the mobile terminal can be more precisely restricted. [0051]Based on the embodiment shown in FIG. 1, as shown in FIG. 3, an embodiment of the present disclosure provides another method for restricting a usage region of a mobile terminal. Before step S200, the method may further include the following steps. [0052]Step S101: Determine a cell network having maximum signal strength in the at least one cell network that covers the current location of the mobile terminal, and send cell identification information corresponding to the cell network having maximum signal strength to a control device connected to the mobile device. [0053]In another embodiment of the present disclosure, alternatively, cell identification information corresponding to another cell network that covers the current location of the mobile terminal may also be sent to a control device. When multiple pieces of cell identification information are sent to the control device, signal strength information may be simultaneously sent to the control device. [0054]Step S102: Determine, according to a region lock instruction delivered by the control device, the cell identification information corresponding to the cell network having maximum signal strength, where the region lock instruction includes the cell identification information corresponding to the cell network having maximum signal strength. [0055]The region lock instruction may be delivered by the control device after a user performs a region locking operation on the control device, or may be automatically delivered by the control device. [0056]Step S103: Determine the cell identification information corresponding to the cell network having maximum signal strength as the locked identification information. [0057]It may be understood that, when the mobile terminal is located in the restricted region, steps S101 to S103 may be performed. The cell network having maximum signal strength is one of cell networks that provide wireless communication services for the mobile terminal at the current location of the restricted region. The cell network has maximum signal strength and therefore provides highest wireless communication service quality. When the cell identification information corresponding to the cell network having maximum signal strength is set as the locked identification information, the mobile terminal can access the cell network having better service quality. (String), 相关申请的交叉引用 [0001] 本申请为2015年2月15日提交的美国国家阶段国际专利申请PCT/CN2015/073113,其全部内容通过引用并入本文。 技术领域 [0002] 本 发明涉及移动通信领域,尤其涉及一种限制移动终端使用区域的方法、装置及移动终端。 背景 [0003] 为了特定的目的,一些移动终端(例如手机、POS机、MIFI)的使用范围往往需要进行限制。 只有在特定的使用范围内,这些移动终端才能正常使用通信运营商提供的语音通信服务、短信服务或数据通信服务等无线通信服务。 例如,MIFI 只能在指定区域使用。 当 MIFI 在指定区域时,MIFI 可以正常工作,为其他设备提供无线网络。 当MIFI在指定区域之外时,MIFI无法正常工作,无法为其他设备提供无线网络。 [0004] 在其他方式中,通过锁定位置区码来限制移动终端的使用范围。 当移动终端处于锁定位置区码标识的区域时,移动终端可以正常使用无线通信服务。 否则,移动终端将无法正常使用无线通信服务。 [0005] 但是,位置区码标识的区域太大,甚至区县都在位置区码标识的区域内。 因此,其他方式无法精确限制移动终端的使用范围。 概括 [0006] 本发明实施例提供一种限制移动终端使用区域的方法、装置及移动终端,以更加精确地限制移动终端的使用范围。 解决方法如下。 [0007] 第一方面,提供了一种限制移动终端使用区域的方法。 该方法应用于移动终端,该方法包括获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,该小区网络对应于无线通信网络所支持的网络制式。 移动终端,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断小区标识信息是否包括与锁定标识信息匹配的小区标识信息,参数为 锁定标识信息与小区标识信息的参数一一对应,当获取到小区标识信息时,移动终端接入锁定标识信息对应的小区网络 包括与锁定的标识信息匹配的小区标识信息,或者当获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,移动终端跳过接入无线通信网络。 [0008] 结合第一方面,在第一种可能的实现方式中,当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定的标识信息包括锁定的 频道号,当移动终端支持的网络制式不是GSM时,小区标识信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0009]结合第一方面,在第二种可能的实现方式中,在判断所述小区标识信息是否包括与锁定标识信息匹配的小区标识信息之前,所述方法还包括:确定所述至少一个小区网络中信号强度最大的小区网络。 覆盖移动终端的当前位置,向与移动设备连接的控制设备发送信号强度最大的小区网络对应的小区标识信息,根据控制设备下发的区域锁定指令确定小区标识 信号强度最大的小区网络对应的信息, 区域锁定指令包括信号强度最大的小区网络对应的小区标识信息, 确定si最大的小区网络对应的小区标识信息 gnal强度作为锁定的标识信息。 [0010] 结合第一方面,在第三种可能的实现方式中,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,移动终端接入锁定的标识信息对应的小区网络包括接入, 移动终端在获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息,且与锁定标识信息匹配的小区标识信息的信号强度不小于预设值时,获取锁定标识信息对应的小区网络 强度阈值。 [0011] 结合第一方面的第一种至第三种可能的实现方式,在第四种可能的实现方式中,获取覆盖所述移动终端当前位置的至少一个小区网络的小区标识信息,包括: 所述移动终端执行: 频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,或者移动终端接收小区广播消息,从广播中获取 消息,覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0012] 第二方面,提供了一种限制移动终端使用区域的装置。 该装置应用于移动终端,该装置包括小区标识信息获取单元、匹配判断单元、网络接入单元和网络丢弃单元,小区标识信息获取单元用于获取小区标识信息 覆盖移动终端当前位置的至少一个小区网络的标识,该小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者, 小区标识信息包括频道号信息和辅助小区标识信息。 匹配判断单元,用于判断小区标识信息中是否包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应。 网络接入单元,用于当小区标识信息获取单元获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,接入锁定标识信息对应的小区网络; 网络丢弃单元,用于 当小区标识信息获取单元获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0013]结合第二方面,在第一种可能的实现方式中,当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定标识信息包括锁定频道号,当 移动终端支持的网络制式不是GSM,小区标识信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0014] 结合第二方面,在第二种可能的实现方式中,所述装置还包括最强网络确定单元、标识信息确定单元和标识信息锁定单元,其中,所述匹配确定单元在确定所述小区是否为所述小区之前 标识信息包括与锁定的标识信息匹配的小区标识信息, 最强网络确定单元用于确定覆盖移动终端当前位置的至少一个小区网络中信号强度最大的小区网络,并发送小区标识 将与具有最大信号强度的小区网络对应的信息发送给连接到移动设备的控制设备。 标识信息确定单元,用于根据控制设备下发的区域锁定指令,确定信号强度最大的小区网络对应的小区标识信息,该区域锁定指令包括该小区对应的小区标识信息 所述信号强度最大的小区网络,所述标识信息锁定单元用于将所述信号强度最大的小区网络对应的小区标识信息确定为锁定的标识信息。 [0015] 结合第二方面,在第三种可能的实现方式中,所述网络接入单元,还用于当获取的小区标识信息中包括匹配的小区标识信息时,移动终端接入锁定的标识信息对应的小区网络。 锁定标识信息,与锁定标识信息匹配的小区标识信息的信号强度不小于预设强度门限。 [0016] 结合第二方面的第一种至第三种可能的实现方式,在第四种可能的实现方式中,所述小区标识信息获取单元包括频率扫描子单元和/或广播接收子单元,所述频率扫描子单元用于 进行频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,广播接收子单元用于接收小区广播消息,从中获取 广播消息、覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0017]第三方面,提供了一种存储介质。 存储介质用于存储应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0018] 第四方面,提供了一种应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0019]第五方面,提供了一种移动终端,包括处理器、存储器、通信接口和总线,处理器、存储器和通信接口通过总线连接并通信。 存储器存储可执行程序代码。 处理器读取存储在存储器中的可执行程序代码,以运行与可执行程序代码对应的程序,以执行以下步骤:获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,其中小区 网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断小区标识是否为 信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,接入锁定标识对应的小区网络 当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,则跳过无线通信网络的接入;或者当获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0020] 由上述技术方案可知,根据本发明实施例的移动终端使用区域限制方法、装置及移动终端,覆盖当前小区网络的小区标识信息 可以获得移动终端的位置。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 否则,移动终端跳过接入无线通信网络。 本发明通过将当前位置的小区网络的小区标识信息与锁定的标识信息进行比对,来控制移动终端的小区网络接入。 在本发明中,由于小区对应的区域小于位置区码对应的区域,因此可以更精确地限制移动终端的使用范围。 附图说明 [0021] 为更加清楚地描述本发明实施例中的技术方案,下面对实施例中所需要的附图进行简要说明。 下面描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0022] 图1为本发明实施例限制移动终端使用区域的方法流程图; [0023] 图2是根据本发明实施例的无线通信网络的覆盖示意图; [0024] 图3为本发明实施例提供的另一种限制移动终端使用区域的方法流程图; [0025] 图4为本发明实施例控制设备与移动终端通信的示意图; [0026] 图5为本发明实施例限制移动终端使用区域的装置的结构示意图; [0027] 图6为本发明实施例提供的另一种限制移动终端使用区域的装置的结构示意图; 和 [0028] 图7为本发明实施例提供的移动终端的结构示意图。 具体实施方式 [0029] 为使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本发明进行进一步详细说明。 所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0030] 如图1所示,本发明实施例提供了一种限制移动终端使用区域的方法。 该方法应用于移动终端,该方法可以包括以下步骤。 [0031] 脚步 100 :获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,该小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道 号信息,或者小区标识信息包括频道号信息和辅助小区标识信息。 [0032] 移动终端可以是手机、POS机、MIFI等。 [0033] 小区(cell,也称为蜂窝小区)是无线通信网络上的最小单位,多个小区可以组成一个位置区码对应的区域。 小区小于位置区域码对应的区域。 [0034] 频道号信息为固定频率的编号。 为了避免相同频道号信息造成的干扰,一个区域内的小区的频道号信息是不同的。 在使用GSM标准的通信设备的广泛区域中,小区的频道号信息彼此不同。 因此,移动终端获取到的覆盖当前位置的无线通信网络的小区的频道号信息是不同的。 [0035] 频率复用技术用于诸如宽带码分多址(WCDMA)、时分同步码分多址(TD-SCDMA)或长期演进(LTE)的网络标准中。 因此,移动终端获取的覆盖当前位置的小区网络的频道号信息可能是相同的。 因此,为了减少误操作,还可以获取小区的辅助小区标识信息来识别小区。 在WCDMA中,辅助小区标识信息是主要的扰码。 在TD-SCDMA中,辅助小区标识信息是扰码。 在LTE中,辅助小区标识信息是物理层小区号。 利用小区的频道号信息和小区的辅助小区标识信息,可以更准确的区分小区,减少误操作。 小区标识信息可以由频道号信息和辅助小区标识信息组成。 [0036] 可以理解的是,不同的网络标准使用不同的频段。 例如,GSM标准中使用900兆赫兹(MHz)频段和1800MHz频段的频道号。 当移动终端仅支持GSM制式时,可以获取900MHz频段和1800MHz频段的频道号信息。 [0037] 进一步地,可选地,可以仅获取覆盖移动终端当前位置的第一通信运营商的至少一个小区网络的小区标识信息。 第一通信运营商为提供移动终端的用户识别卡/通用用户识别卡的通信运营商。 [0038]例如,对于GSM标准中的900MHz频段,中国移动的下行频段为935-954MHz,中国联通的下行频段为954-960MHz。 当移动终端的用户识别卡/通用用户识别卡为中国移动提供时,只能获取935-954MHz的频道号信息。 [0039] 小区网络的无线通信信号由基站提供,一个基站可以为一个或多个小区网络提供无线通信信号。 当多个小区网络覆盖移动终端的当前位置时,移动终端可以获得基站提供的多个小区网络的无线通信信号。 如图2所示,假设基站 201 为小区网络A提供无线通信信号,基站 202 为小区网络B提供无线通信信号,基站 203 为小区网络C提供无线通信信号,三个小区网络A、B、C的无线通信信号覆盖移动终端的当前位置 200 . 在这种情况下,移动端 200 可以获得当前位置的三个小区网络A、B、C的小区标识信息。 [0040] 移动端 200 可以通过频率扫描或者接收小区广播消息来获取小区标识信息。 进一步地,步骤S 100 可以包括移动终端进行频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,或者移动终端接收小区 广播消息,从广播消息中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0041] 脚步 200 :判断小区标识信息是否包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应。 [0042] 当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定标识信息包括锁定频道号,当移动终端支持的网络制式为非GSM时,小区标识信息为锁定频道号。 信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0043] 脚步 300 :当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 [0044] 脚步 400 :移动终端在获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0045] 进一步地,移动终端的网络接入功能可以在特定时间段内被锁定以不接入无线通信网络以丢弃网络。 例如,移动终端的小区切换和小区重选功能被锁定。 移动终端的网络接入功能被锁定的时间超过特定时间后,返回步骤S 100 . [0046] 锁定的标识信息可以是受限区域覆盖的小区的小区标识信息。 受限区域为移动终端需要限制的使用区域,例如工厂。 锁定的标识信息可以是一条或至少两条。 [0047]可选的,当获取的小区标识信息仅包括与锁定的标识信息匹配的小区标识信息时,可以接入锁定的标识信息对应的小区网络。 当获取的小区标识信息包括至少两条与锁定标识信息匹配的小区标识信息时,可以接入其中一条锁定标识信息对应的小区网络。 优选地,可以接入锁定的标识信息对应的信号强度最大的小区网络。 [0048] 可选地,步骤S 300 可以包括:当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息,且与锁定标识信息匹配的小区标识信息的信号强度不存在时,移动终端接入锁定标识信息对应的小区网络。 低于预设的强度阈值。 [0049] 在某些情况下,移动终端虽然可以接入锁定的标识信息对应的小区网络,但是该小区网络信号强度较差,无法为用户提供满意的通信服务。 因此,为了保证为用户提供满意的通信服务,可以在信号强度较大时接入锁定的标识信息对应的小区网络。 [0050] 本发明实施例提供的限制移动终端使用区域的方法,可以获取覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 否则,移动终端跳过接入无线通信网络。 本发明通过将当前位置的小区网络的小区标识信息与锁定的标识信息进行比对来控制移动终端的小区网络接入。 在本发明中,由于小区对应的区域小于位置区码对应的区域,因此可以更精确地限制移动终端的使用范围。 [0051] 基于图1所示实施例,如图3所示,本发明实施例提供了另一种限制移动终端使用区域的方法。 在步骤 S 之前 200 ,该方法还可以包括以下步骤。 [0052] 脚步 101 :确定覆盖移动终端当前位置的至少一个小区网络中信号强度最大的小区网络,将信号强度最大的小区网络对应的小区标识信息发送给与移动设备连接的控制设备。 [0053] 在本发明的另一个实施例中,可选地,也可以向控制设备发送覆盖移动终端当前所在位置的其他小区网络对应的小区标识信息。 当向控制设备发送多个小区标识信息时,可以同时向控制设备发送信号强度信息。 [0054] 脚步 102 :根据控制设备下发的区域锁定指令确定信号强度最大的小区网络对应的小区标识信息,区域锁定指令包括信号强度最大的小区网络对应的小区标识信息。 [0055] 区域锁定指令可以是用户对控制设备进行区域锁定操作后控制设备下发的,也可以是控制设备自动下发的。 [0056] 脚步 103 :确定信号强度最大的小区网络对应的小区标识信息作为锁定标识信息。 [0057]可以理解的是,当移动终端位于限制区域时,步骤S 101 到小号 103 可能被执行。 信号强度最大的小区网络是为受限区域当前位置的移动终端提供无线通信服务的小区网络之一。 小区网络具有最大信号强度,因此提供最高的无线通信服务质量。 当将信号强度最大的小区网络对应的小区标识信息设置为锁定标识信息时,移动终端可以接入服务质量较好的小区网络。 [0058] 步骤 101 到小号 103 是设置锁定标识信息的过程。 可以理解的是,不需要每次都在步骤S之前进行设置过程 200 被执行。 或者,步骤 S 101 到小号 103 可以在步骤S之前执行 100 , 以及一系列执行步骤 S 101 到小号 103 和步骤S 100 不限于本公开。 [0059] 控制设备可以是与移动终端通信连接的服务器、个人电脑、移动设备等。 在本发明中,移动终端可以通过WI-FI、通用串行总线(USB)路径等方式与控制设备进行通信连接。 步骤 S 之后 103 进行,步骤S 200 可以开始执行图1所示的步骤。 执行步骤 S 后 300 或步骤S 400 之后,移动终端还可以向控制设备返回小区网络接入结果,例如是否接入小区网络,或者接入小区网络的信息。 [0060] 当控制设备通过USB路径与移动终端通信连接时,参见图4,移动终端的流程 502 与控制设备通信 501 设置锁定标识信息并尝试访问小区可以包括以下内容。 [0061] 第1步:通过控制装置传送 501 通过USB路径,向移动终端获取小区标识信息的第一控制指令 502 ; [0062] 第二步:移动端后 502 通过USB口接收第一控制指令,通过USB口将第一控制指令转发给非接入层; [0063] 步骤3、非接入层解析第一控制指令,并将解析后的消息发送给接入层; [0064] 步骤4:接入层进行频率扫描,或者接收广播消息,获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息 502 ,确定覆盖移动终端当前位置的至少一个小区网络中信号强度最大的小区网络 502 ,向非接入层发送信号强度最大的小区网络对应的小区标识信息; [0065] 第五步:非接入层发送给控制设备 501 使用USB路径,接入层发送的小区标识信息; [0066] 第六步:发送,由控制设备 501 , 向移动端的区域锁定指令 502 采用USB路径,区域锁定指令包括信号强度最大的小区网络对应的小区标识信息; [0067] 第七步:转发,通过移动端USB口转发 502 , 非接入层的区域锁定指令; [0068] 步骤8、非接入层解析区域锁定指令,并将解析后的消息发送给接入层,解析后的消息中包含信号强度最大的小区网络对应的小区标识信息; [0069]步骤9:接入层将信号强度最大的小区网络对应的小区标识信息设置为锁定标识信息,在步骤4得到的小区标识信息中查找与锁定标识信息匹配的小区标识信息,如果是 查找到与锁定标识信息匹配的小区标识信息,接入锁定标识信息对应的小区网络,否则跳过接入无线通信网络,进行网络丢弃处理; 和 [0070] 第十步:返回,通过移动端 502 , 将步骤9的处理结果发送给控制设备 501 使用 USB 路径。 [0071] 接入层和非接入层是移动终端通信技术的另一种方式,本领域技术人员可以理解接入层和非接入层的上述工作过程。 [0072] 与上述方法实施例对应,本发明还提供了一种限制移动终端使用区域的装置。 [0073] 如图5所示,本发明实施例提供了一种限制移动终端使用区域的装置。 该装置应用于移动终端,该装置可以包括小区标识信息获取单元 100 , 匹配判定单元 200 , 一个网络访问单元 300 , 和一个网络丢弃单元 400 . [0074] 小区标识信息获取单元 100 用于获取覆盖所述移动终端当前位置的至少一个小区网络的小区标识信息,所述小区网络对应于所述移动终端支持的网络制式对应的无线通信网络,所述小区标识信息为 频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息。 [0075] 移动终端可以是手机、POS机、MIFI等。 [0076] 小区标识信息获取单元 100 可以包括频率扫描子单元(未示出)和/或广播接收子单元(未示出)。 [0077] 频率扫描子单元,用于进行频率扫描,从频率扫描结果中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0078] 广播接收子单元,用于接收小区广播消息,从广播消息中获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息。 [0079] 匹配判定单元 200 用于判断小区标识信息是否包括与锁定标识信息匹配的小区标识信息,其中锁定标识信息的参数与小区标识信息的参数一一对应。 [0080] 当移动终端支持的网络制式为GSM时,小区标识信息为频道号信息,锁定标识信息包括锁定频道号,当移动终端支持的网络制式为非GSM时,小区标识信息为锁定频道号。 信息包括频道号信息和辅助小区标识信息,锁定标识信息包括锁定频道号和锁定辅助标识信息。 [0081] 网络接入单元 300 用于当小区标识信息获取单元获取到小区标识信息时,接入锁定的标识信息对应的小区网络 100 包括与锁定标识信息匹配的小区标识信息。 [0082] 网络丢弃单元 400用于当小区标识信息获取单元获取到小区标识信息时,跳过接入无线通信网络 100 不包括与锁定标识信息匹配的小区标识信息。 [0083] 进一步地,移动终端的网络接入功能可以在特定时间段内被锁定以不接入无线通信网络以丢弃网络。 例如,移动终端的小区切换和小区重选功能被锁定。 在移动终端的网络接入功能被锁定的时间超过特定时间后,小区标识信息获取单元 100 可能会再次触发。 [0084] 网络接入单元 300 可以用于当获取的小区标识信息包括与锁定标识信息匹配的小区标识信息以及与锁定标识信息匹配的小区标识信息的信号强度时,移动终端接入锁定标识信息对应的小区网络 不低于预设的强度阈值。 [0085] 在某些情况下,移动终端虽然可以接入锁定的标识信息对应的小区网络,但是该小区网络信号强度较差,无法为用户提供满意的通信服务。 因此,为了保证为用户提供满意的通信服务,可以在信号强度较大时接入锁定的标识信息对应的小区网络。 [0086] 本发明实施例提供的限制移动终端使用区域的装置,可以获取覆盖移动终端当前位置的小区网络的小区标识信息。 当获取的小区标识信息中包括与锁定标识信息匹配的小区标识信息时,移动终端接入锁定标识信息对应的小区网络。 否则,移动终端跳过接入无线通信网络。 本发明通过将当前位置的小区网络的小区标识信息与锁定的标识信息进行比对来控制移动终端的小区网络接入。 在本发明中,由于小区对应的区域小于位置区码对应的区域,因此可以更精确地限制移动终端的使用范围。 [0087] 基于图5所示实施例,如图6所示,本发明实施例提供了另一种限制移动终端使用区域的装置。 该装置还可以包括最强网络确定单元 101 , 识别信息确定单元 102 , 以及识别信息锁定单元 103 . [0088] 最强网络决定单位 101 用于确定覆盖移动终端当前所在位置的至少一个小区网络中信号强度最大的小区网络,将信号强度最大的小区网络对应的小区标识信息发送给与移动终端连接的控制设备 确定前的设备,由匹配确定单元 200 ,小区标识信息中是否包括与锁定的标识信息相匹配的小区标识信息。 [0089] 身份信息确定单元 102 用于根据控制设备下发的区域锁定指令确定信号强度最大的小区网络对应的小区标识信息, 区域锁定指令包括信号强度最大的小区网络对应的小区标识信息 . [0090] 区域锁定指令可以是用户对控制设备进行区域锁定操作后控制设备下发的,也可以是控制设备自动下发的。 [0091]识别信息锁定单元 103 用于将信号强度最大的小区网络对应的小区标识信息确定为锁定标识信息。 [0092] 信号强度最大的小区网络是为受限区域当前位置的移动终端提供无线通信服务的小区网络之一。 小区网络具有最大信号强度,因此提供最高的无线通信服务质量。 当将信号强度最大的小区网络对应的小区标识信息设置为锁定标识信息时,移动终端可以接入服务质量较好的小区网络。 [0093] 控制设备可以是与移动终端通信连接的服务器、个人电脑、移动设备等。 在本发明中,移动终端可以通过WI-FI、USB路径等方式与控制设备通信连接。 [0094] 相应地,本发明实施例还提供了一种存储介质。 存储介质用于存储应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0095]本发明实施例还提供了一种应用程序。 当应用程序运行时,执行本发明实施例的限制移动终端使用区域的方法。 本发明实施例限制移动终端使用区域的方法,应用于一种移动终端,该方法可以包括获取覆盖该移动终端当前位置的至少一个小区网络的小区标识信息, 其中,小区网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断是否 小区标识信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,移动终端接入小区网络 对应 针对锁定的标识信息,当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,或者当获取的小区标识信息不包括小区标识信息时,移动终端跳过接入无线通信网络 匹配锁定的标识信息。 [0096] 本发明还提供了一种与上述方法实施例对应的移动终端。 [0097] 本发明实施例提供的移动终端可以包括处理器、存储器、通信接口和总线。 [0098] 处理器、存储器和通信接口使用总线相互连接和通信。 [0099] 存储器存储可执行程序代码。 [0100] 处理器读取存储在存储器中的可执行程序代码,以运行与可执行程序代码对应的程序,以执行以下步骤获取覆盖移动终端当前位置的至少一个小区网络的小区标识信息,其中小区 网络对应移动终端支持的网络制式对应的无线通信网络,小区标识信息为频道号信息,或者小区标识信息包括频道号信息和辅助小区标识信息,判断小区标识是否为 信息包括与锁定标识信息匹配的小区标识信息,锁定标识信息的参数与小区标识信息的参数一一对应,接入锁定标识对应的小区网络 当获取的小区标识信息中包括与锁定的标识信息匹配的小区标识信息时,则跳过无线通信网络的接入;或者当获取的小区标识信息中不包括与锁定的标识信息匹配的小区标识信息时,跳过接入无线通信网络。 [0101] 本发明实施例提供的移动终端中的处理器可以为基带芯片。 存储器可以是多芯片封装。 通信接口可以包括USB端口、射频器件和WI-FI芯片。 此外,本发明实施例提供的移动终端还可以包括用户识别模块卡。 [0102] 进一步的,如图7所示,本发明实施例提供的移动终端可以包括:基带芯片 701 , 一个射频分量 702 , 多芯片封装 703 , 订户识别模块卡(SIM卡) 704 , WI-FI芯片 705 , 和一个 USB 端口 706 . 射频成分 702 , 多芯片封装 703 , 用户识别模块卡 704, WI-FI芯片 705 , 和 USB 端口 706 都与基带芯片电连接 701 . [0103] 基带芯片 701 用于进行数据处理、完成与网络侧的信令交互、处理控制设备的控制命令和数据请求、使用SIM卡进行鉴权等操作 704 ,以及读/写多芯片封装 703 . [0104] 射频成分 702 被配置为提供移动WI-FI的第三代(3G)上行链路路径。 [0105] 多芯片封装 703 集成了闪存和双倍数据率同步动态随机存取存储器(DRAM)。 闪存用于存储处理器的图像和数据。 DRAM 被配置为存储运行的程序。 [0106] WI-FI芯片 705 用于承载移动终端的无线局域网连接。 [0107] USB端口 706 作为移动终端与控制设备的物理连接路径,承载控制设备与移动终端之间的数据交互。 [0108] 本发明实施例提供了另一种移动终端。 移动终端还可以包括电源管理单元。 电源管理单元为基带芯片、射频器件、多芯片封装、SIM卡、WI-FI芯片和USB接口供电。 [0109] 以上所述仅为本发明的实施例而已,并不用于限制本发明。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.560 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN107113765A(String), CN107113765B(String), EP3249983A1(String), EP3249983A4(String), EP3249983B1(String), JP2018505627A(String), JP6514350B2(String), US10182389B2(String), US20180035355A1(String), WO2016127432A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN107113765A(String), CN107113765B(String), EP3249983A1(String), EP3249983A4(String), EP3249983B1(String), JP2018505627A(String), JP6514350B2(String), US10182389B2(String), US20180035355A1(String), WO2016127432A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.736 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN107113765A(String), CN107113765B(String), EP3249983A1(String), EP3249983A4(String), EP3249983B1(String), JP2018505627A(String), JP6514350B2(String), US10182389B2(String), US20180035355A1(String), WO2016127432A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), CN107113765A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271239(Integer), CN107113765B(String), 1048353(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), EP3249983A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), EP3249983A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), EP3249983B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), JP2018505627A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), JP6514350B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:32.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), US10182389B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), US20180035355A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271239(Integer), WO2016127432A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN107113765B(String), CN107113765B(String), 1608566400(Integer), 271239(Integer), 185523(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.183 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185962(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185962(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.320 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185962(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185962(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.389 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.442 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.442 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185962(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:33.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20140245234A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.042 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.042 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.042 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 用于根据与移动终端的操作相关的输入来控制多个对象的显示的方法及其移动终端(String), US20140245234A1(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US14/105735(String), 1386864000(Integer), US20140245234A1(String), 1409155200(Integer), 美国(String), 2(Integer), KR(String), 17(Integer), 22(Integer), US20080250312A1 | US20080282202A1 | US20090197635A1 | US20100070926A1 | US20100125816A1 | US20100217685A1 | US20100248788A1 | US20110041101A1 | US20110281633A1 | US20120030569A1 | US20120162261A1 | US20120166997A1 | US20120192121A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130278484A1 | US20140059472A1 | US20140139637A1 | US20140143737A1 | US20140181751A1 | US20150077333A1(String), 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185963(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e3a65ce8dc974c8099bd635c439cb8b5.png(String), 185963(Integer), e3a65ce8dc974c8099bd635c439cb8b5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 用于根据与移动终端的操作相关的输入来控制多个对象的显示的方法及其移动终端(String), US20140245234A1(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US14/105735(String), 1386864000(Integer), US20140245234A1(String), 1409155200(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 17(Integer), 22(Integer), US20080250312A1 | US20080282202A1 | US20090197635A1 | US20100070926A1 | US20100125816A1 | US20100217685A1 | US20100248788A1 | US20110041101A1 | US20110281633A1 | US20120030569A1 | US20120162261A1 | US20120166997A1 | US20120192121A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130278484A1 | US20140059472A1 | US20140139637A1 | US20140143737A1 | US20140181751A1 | US20150077333A1(String), \20230420\e3a65ce8dc974c8099bd635c439cb8b5.png(String), 25(Integer), 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 1. A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal, the method comprising:displaying a layout including a plurality of areas in which a plurality of objects are respectively displayed;receiving the input related to the operation of the mobile terminal;changing one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal; anddisplaying a layout including the changed areas.(String), 1.一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法,该方法包括:显示包括分别显示多个对象的多个区域的布局;接收与移动终端操作相关的输入;改变与移动终端的操作相关的输入对应的多个区域中的一个或多个区域;和显示包含更改区域的布局。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 2. The method of claim 1, wherein the input related to the operation of the mobile terminal is at least one of a motion of the mobile terminal, a user's breath, and a gesture.(String), 2.如权利要求1所述的方法,其中与移动终端的操作相关的输入为移动终端的动作、用户的呼吸、手势中的至少一种。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 3. The method of claim 2, further comprising:detecting a reciprocating motion direction corresponding to at least one of an up-down direction, a left-right direction, and a diagonal direction of the mobile terminal if the input related to the operation of the mobile terminal is a motion of the mobile terminal4. The method of claim 3, wherein the changing of the areas corresponding to the input related to the operation of the mobile terminal comprises changing one or more areas of the plurality of areas corresponding to the reciprocating motion direction.(String), 3.如权利要求2所述的方法,还包括:如果与移动终端的操作相关的输入是移动终端的运动,则检测对应于移动终端的上下方向、左右方向和对角线方向中的至少一个的往复运动方向4.如权利要求3所述的方法,其中改变与移动终端的操作相关的输入对应的区域包括改变多个区域中对应往复运动方向的一个或多个区域。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 5. The method of claim 1, further comprising:determining whether one of the plurality of areas is touched;determining whether the input related to the operation of the mobile terminal is received while the touch is maintained; andrearranging the remaining areas except for the touched area if the input related to the operation of the mobile terminal is received while the touch is maintained.(String), 5.如权利要求1所述的方法,还包括:确定多个区域之一是否被触摸;判断在保持触摸的情况下是否接收到与移动终端操作相关的输入;和如果在保持触摸的同时接收到与移动终端的操作相关的输入,则重新排列除触摸区域之外的其余区域。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 6. The method of claim 5, further comprising:searching for one or more objects associated with an object belonging to the touched area based on a property of the object if the input related to the operation of the mobile terminal is received while the touch is maintained; anddisplaying a layout in which the found objects are respectively displayed in the remaining areas.(String), 6.如权利要求5所述的方法,还包括:如果在保持触摸的同时接收到与移动终端的操作相关的输入,则基于对象的属性搜索与属于触摸区域的对象关联的一个或多个对象;和显示在剩余区域中分别显示找到的对象的布局。(String), 1(Integer), 4(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 7. The method of claim 6, further comprising:if the object belonging to the touch area is a portrait, searching for pictures associated with a person appearing on the portrait are, and respectively displaying the found pictures in the remaining areas.(String), 7.如权利要求6所述的方法,还包括:如果属于触摸区域的对象为人像,则在人像区域中查找与人像区域相关联的图片,并在其余区域分别显示查找到的图片。(String), 1(Integer), 5(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 8. The method of claim 1, wherein the displaying of the layout including the changed areas comprises arranging the plurality of objects on the changed areas in consideration of the properties of the objects, the properties regarding the horizontal and vertical formats of the objects.(String), 8.如权利要求1所述的方法,其中包括改变区域的布局的显示包括考虑到对象的属性,关于对象的水平和垂直格式的属性,将多个对象布置在改变区域上。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 9. The method of claim 1, wherein the displaying of the layout including the changed areas comprises moving an object displayed on a largest area among the plurality of objects to a smallest area and moving an object displayed on the smallest area to the largest area.(String), 9.如权利要求1所述的方法,其中包括改变区域的布局的显示包括将多个对象中显示在最大区域上的对象移动到最小区域,并将显示在最小区域上的对象移动到最大区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 10. The method of claim 3, further comprising:determining whether a number of one or more reciprocating motions of the mobile terminal is equal to or greater than a predetermined number if the direction of the reciprocating motions of the mobile terminal is determined; andadding a predetermined number of areas to areas constituting a layout of a current page if the number of the reciprocating motions is equal to or greater than the predetermined number.(String), 10.如权利要求3所述的方法,还包括:如果确定了移动终端的往复运动的方向,则判断移动终端的一次或多次往复运动的次数是否等于或大于预定次数;和如果往复运动的次数等于或大于预定数目,则将预定数目的区域添加到构成当前页面的布局的区域。(String), 1(Integer), 8(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 11. The method of claim 10, wherein the predetermined number of areas is a predetermined number of areas constituting a layout of a next page.(String), 11.如权利要求10所述的方法,其中预定数量的区域是构成下一页布局的预定数量的区域。(String), 1(Integer), 9(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 12. The method of claim 1, further comprising:displaying an icon for adjusting a number of the plurality of areas if a request for adjusting the number of the areas is received; andadding/removing one or more areas to/from the plurality of areas if an input related to operation of the mobile terminal is received while the icon for adjusting the number of the areas is touched.(String), 12.如权利要求1所述的方法,还包括:如果接收到调整区域数量的请求,则显示用于调整多个区域数量的图标;和如果在触摸用于调整区域数量的图标的同时接收到与移动终端的操作相关的输入,则向/从多个区域添加/删除一个或多个区域。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 13. A mobile terminal for controlling a display of a plurality of objects according to an input related to operation of the mobile terminal, the mobile terminal comprising:a display unit configured to display a layout including a plurality of areas in which the plurality of objects are respectively displayed;a sensor module configured to detect the input related to the operation of the mobile terminal; anda controller configured to change one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and to control the display unit to display a layout including the changed areas.(String), 13.一种用于根据与移动终端的操作相关的输入来控制多个对象的显示的移动终端,该移动终端包括:显示单元被配置为显示包括分别显示多个对象的多个区域的布局;传感器模块,用于检测与移动终端的操作相关的输入;和控制器被配置为对应于与移动终端的操作相关的输入来改变多个区域中的一个或多个区域,并且控制显示单元显示包括改变的区域的布局。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 14. The mobile terminal of claim 13, wherein the input related to the operation of the mobile terminal is at least one of a motion of the mobile terminal, a user's breath, and a gesture.(String), 14.如权利要求13所述的移动终端,其中与移动终端的操作相关的输入为移动终端的动作、用户的呼吸、手势中的至少一种。(String), 1(Integer), 12(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 15. The mobile terminal of claim 14, wherein the sensor module comprises at least one of a motion sensor for detecting the motion of the mobile terminal, a breath detection sensor for detecting the user's breath, and a camera sensor for sensing the gesture.(String), 15.如权利要求14所述的移动终端,其中传感器模块包括用于检测移动终端运动的运动传感器、用于检测用户呼吸的呼吸检测传感器和用于感应手势的摄像头传感器中的至少一种。(String), 1(Integer), 13(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 16. The mobile terminal of claim 14, wherein the sensor module detects a reciprocating motion direction corresponding to at least one of an up-down direction, a left-right direction, and a diagonal direction of the mobile terminal.(String), 16.如权利要求14所述的移动终端,其中传感器模块检测对应于移动终端的上下方向、左右方向和对角线方向中的至少一个的往复运动方向。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 17. The mobile terminal of claim 16, wherein the controller changes one or more areas of the plurality of areas corresponding to a reciprocating motion direction detected through the sensor module.(String), 17.如权利要求16所述的移动终端,其中控制器对应于通过传感器模块检测到的往复运动方向改变多个区域中的一个或多个区域。(String), 1(Integer), 15(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 18. The mobile terminal of claim 13, wherein the controller determines whether any one of the plurality of areas is selected, and rearranges the remaining areas except for the selected area if an input related to the mobile terminal is detected through the sensor module while the selection is maintained.(String), 18.如权利要求13所述的移动终端,其中控制器确定是否选择了多个区域中的任何一个,并且如果在保持选择的同时通过传感器模块检测到与移动终端相关的输入,则重新排列除了所选区域之外的剩余区域。(String), 1(Integer), 16(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 19. The mobile terminal of claim 18, wherein if the input related to the operation of the mobile terminal is detected through the sensor module while the selection is maintained, the controller searches for objects associated with an object belonging to the selected area based on a property of the selected area, and controls the display unit to display a layout in which the found objects are respectively displayed in the remaining areas.(String), 19.如权利要求18所述的移动终端,其中如果在保持选择的同时通过传感器模块检测到与移动终端的操作相关的输入,则控制器基于所选区域的属性搜索与属于所选区域的对象相关联的对象,并控制显示显示布局的单元,其中找到的对象分别显示在其余区域中。(String), 1(Integer), 17(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 20. The mobile terminal of claim 19, wherein if the object belonging to the selected area is a portrait, the controller searches for pictures associated with a person appearing on the portrait, and then controls the display unit to display the found pictures in the remaining areas, respectively.(String), 20.如权利要求19所述的移动终端,其中如果属于所选区域的对象是肖像,则控制器搜索与出现在肖像上的人相关联的图片,然后控制显示单元分别在其余区域中显示找到的图片。(String), 1(Integer), 18(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 21. The mobile terminal of claim 13, wherein the controller arranges the plurality of objects on the changed areas in consideration of the properties of the objects, the properties regarding the horizontal and vertical formats of the objects.(String), 21.如权利要求13所述的移动终端,其中控制器考虑到对象的属性,关于对象的水平和垂直格式的属性,将多个对象布置在改变的区域上。(String), 1(Integer), 19(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 22. The mobile terminal of claim 13, wherein the controller moves an object displayed on a largest area among the plurality of objects to a smallest area and moves an object displayed on the smallest area to the largest area.(String), 22.如权利要求13所述的移动终端,其中控制器将多个对象中显示在最大区域上的对象移动到最小区域,并将显示在最小区域上的对象移动到最大区域。(String), 1(Integer), 20(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 23. The mobile terminal of claim 14, wherein the controller determines whether the number of one or more reciprocating motions of the mobile terminal detected through the sensor module is equal to or greater than a predetermined number, and adds a predetermined number of areas to areas constituting a layout of a current page if the number of the reciprocating motions is equal to or greater than the predetermined number.(String), 23.如权利要求14所述的移动终端,其中控制器判断通过传感器模块检测到的移动终端的一个或多个往复运动的次数是否等于或大于预定数目,如果数目为,则将预定数目的区域添加到构成当前页面布局的区域往复运动的次数等于或大于预定次数。(String), 1(Integer), 21(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 24. The mobile terminal of claim 23, wherein the predetermined number of areas is a predetermined number of areas constituting a layout of a next page.(String), 24.如权利要求23所述的移动终端,其中预定数量的区域是构成下一页布局的预定数量的区域。(String), 1(Integer), 22(Integer), 22(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185963(Integer), 25. The mobile terminal of claim 13, wherein the controller displays an icon for adjusting the number of the plurality of areas if a request for adjusting the number of the areas is received, and adds/removes one or more areas to/from the plurality of areas if an input related to operation of the mobile terminal is detected while the icon for adjusting the number of the areas is selected.(String), 25.如权利要求13所述的移动终端,其中如果接收到调整区域数量的请求,则控制器显示用于调整多个区域的数量的图标,并且如果与操作相关的输入,控制器向/从多个区域添加/删除一个或多个区域mobileterminalisdetectedwhiletheiconforadjustingthenumberoftheareasisselected.(String), 1(Integer), 23(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185963(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Feb. 22, 2013 in the Korean Intellectual Property Office and assigned Serial No. 10-2013-0019508, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an apparatus and method for managing a plurality of objects that are displayed on a touch screen. More particularly, the present invention relates to an apparatus and method for allowing a user of a mobile terminal to easily change a display of a plurality of objects on a touch screen according to a motion of the mobile terminal [0004]2. Description of the Related Art [0005]A touch screen with a touch panel mounted on a display device displays images and allows a user to easily input commands without using a keyboard or a mouse. The touch screen has been widely used in various electronic devices, such as a mobile terminal, a navigation system, a TV, Automated Teller Machines (ATMs), a Point-Of-Sale (POS) system, and the like. [0006]For example, with the variety of services and additional functions that can be provided by mobile terminals, many recent mobile terminals provide a Graphic User Interface (GUI) based on a touch screen. [0007]In order to raise the effective value of such mobile terminals and meet users' needs, various applications executable in mobile terminals are being developed. [0008]A mobile terminal can store basic applications developed by the mobile terminal's manufacturing company, as well as additional applications downloaded from application sales web sites through the Internet, and execute the applications. [0009]Accordingly, a mobile terminal, such as the latest smart phone, tablet PC, and the like, stores at least hundreds of applications, and shortcut keys for executing the applications individually are displayed in the form of icons on the touch screen of the mobile terminal. A user can touch one of the icons displayed on the touch screen of a mobile terminal to thus execute a desired application on the mobile terminal. Various visual objects, such as widgets, pictures, document, etc., other than the shortcut keys, may also be displayed on the touch screen of the mobile terminal. [0010]However, as the number of such various visual objects increases, another issue arises. The number of objects that can be displayed on the small screen of a mobile terminal is limited although the mobile terminal stores many visual objects. [0011]Accordingly, due to the spatial limitation of a display screen, there is a need for classifying and arranging visual objects that can be displayed on the screen. However, arranging the components of a layout at regular intervals is insufficient, and it is necessary for a user to be able to conveniently manage visual objects displayed on the screen of a mobile terminal, such as editing, moving, or deleting the visual objects. According to the related art, when a user wants to change a display of objects, the user should convert the screen of his/her mobile terminal into an Edit environment, and input commands for deleting or correcting objects, which causes onerousness and inconvenience and requires a long time for editing. [0012]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. [0013]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY OF THE INVENTION [0014]Aspects of the present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide an apparatus and method for allowing a user to conveniently change the components of a layout in which a plurality of objects are arranged according to his/her desired pattern. [0015]Another aspect of the present invention is to provide an apparatus and method for easily controlling an arrangement of a plurality of objects and a display of a layout in which the objects are arranged according to a motion of a mobile terminal. [0016]In accordance with an aspect of the present invention, a method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes displaying a layout including a plurality of areas in which a plurality of objects are respectively displayed, receiving the input related to the operation of the mobile terminal, changing one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. [0017]In accordance with another aspect of the present invention, a mobile terminal for controlling a display of a plurality of objects according to an input related to operation of the mobile terminal is provided. The mobile terminal includes a display unit configured to display a layout including a plurality of areas in which the plurality of objects are respectively displayed, a sensor module configured to detect the input related to the operation of the mobile terminal, and a controller configured to change one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and to control the display unit to display a layout including the changed areas. [0018]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0019]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0020]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention; [0021]FIG. 2 is a front perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0022]FIG. 3 is a rear perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0023]FIG. 4 is a flowchart of a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0024]FIGS. 5A through 8B show examples for explaining a process in which areas constituting a layout change according to directions of reciprocating motions of a mobile terminal according to an exemplary embodiment of the present invention; [0025]FIGS. 9A to 9D show examples for explaining a process in which areas constituting a layout change according to a breath according to an exemplary embodiment of the present invention; [0026]FIGS. 10A to 11D are views for explaining an arrangement rule of a layout according to an exemplary embodiment of the present invention; [0027]FIG. 12 is a flowchart for explaining a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0028]FIGS. 13A and 13B show examples for explaining a process in which different objects are respectively displayed on areas constituting a layout according to the property of a touched object according to an exemplary embodiment of the present invention; [0029]FIGS. 14A and 14B are flowcharts for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0030]FIGS. 15A to 15I show examples for explaining a process of adjusting a number of areas constituting a layout in the mobile terminal, according to an exemplary embodiment of the present invention; [0031]FIG. 16 is a flowchart for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; and [0032]FIGS. 17A to 17C show examples for explaining a process of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention. [0033]Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0034]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. [0035]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0036]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0037]It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. [0038]The exemplary embodiments that will be described below relate to a hand-held terminal, however, an apparatus and method for managing a plurality of objects displayed on a touch screen, according to exemplary embodiments of the present invention, may be applied to various electronic devices with touch screens, such as a navigation system, a television (TV), an Automated Teller Machine (ATM), a Point-Of-Sale (POS) system, and the like, as well as a mobile terminal, such as a mobile phone, a smart phone, a tablet PC, and the like. [0039]Also, in the following description, a mobile terminal may be a flexible device or a flexible display device. As a representative mobile terminal, a mobile phone is assumed, and some components of such a mobile terminal may be omitted or changed as necessary. [0040]Exemplary embodiments of the present invention provide a method of controlling a display of a plurality of objects according to an input related to a motion of a mobile terminal Exemplary embodiments of the present invention includes an operation of changing, if an input related to a motion of the mobile terminal is received when a layout including areas in which the plurality of objects are displayed is displayed, one or more areas corresponding to the input related to the motion of the mobile terminal among the areas constituting the layout; and an operation of displaying a layout comprised of the changed areas. The input related to the motion of the mobile terminal may correspond to a motion of the mobile terminal, a user's breath, a gesture, and the like. According to exemplary embodiments of the present invention, if an input related to a motion of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged. In this case, objects that are respectively displayed in the remaining areas may be objects searched in correspondence to the property of an object displayed on the touched area. Thereby, a user can easily change components corresponding to the areas of a layout, as well as changing the areas of the layout. [0041]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention. [0042]Referring to FIG. 1, the mobile terminal 100 may be connected to an external electronic device (not shown) using at least one of a communication module 120, a connector 165, and an earphone connecting jack 167. The external electronic device may include an earphone, an external speaker, a Universal Serial Bus (USB) memory, a battery charger, a Cradle/Dock, a Digital Multimedia Broadcasting (DMB) antenna, a mobile payment system, healthcare equipment (a blood glucose meter, etc.), a game, a vehicle navigation system, and the like, which can be removably connected to the mobile terminal 100 through a line. The external electronic device may include a Bluetooth communication apparatus, a Near Field Communication (NFC) apparatus, a WiFi Direct communication apparatus, a Wireless Access Point (WAP), and the like, which can be connected to the mobile terminal 100 in a wireless fashion. The mobile terminal 100 may be connected to one of other mobile terminals or electronic devices (for example, a mobile phone, a smart phone, a tablet PC, a desktop PC, and a server) in a wired/wireless fashion. [0043]The mobile terminal 100 includes a touch screen 190 and at least one touch screen controller 195. The mobile terminal 100 may further include a controller 110, the communication module 120, a multimedia module 140, a camera module 150, an input/output module 160, a sensor module 170, a storage unit 175, and a power supply unit 180. [0044]The communication module 120 includes a mobile communication module 121, a sub communication module 130, and a broadcasting communication module 141. [0045]The sub communication module 130 includes at least one of a Wireless LAN (WLAN) module 131 and a short-range communication module 132. The multimedia module 140 includes at least one of an audio play module 142 and a video play module 143. The camera module 150 may include at least one of a first camera 151 and a second camera 152. The camera module 150 may also include at least one of a body tube 155 for zooming in/out the first and/or second camera 151 or 152, a motor unit 154 for controlling the movement of the body tube 155, and a flash 153 for providing a light source for photographing, according to the main purpose of the mobile terminal 100. The input/output module 160 may includes at least one of a button 161, a microphone 162, a speaker 163, a vibration device 164, the connector 165, and a keypad 166. [0046]The controller 110 may include a CPU 111, a Read Only Memory (ROM) 112 that stores control programs for controlling the mobile terminal 100, and a Random Access Memory (RAM) 113 that stores signals or data received from the outside or is used as a memory area for tasks being performed by the mobile terminal 100. The CPU 111 may include one or more cores, such as a single core, a dual core, a triple core, or a quad core. The CPU 111, ROM 112, and RAM 113 may be connected to each other through internal buses. [0047]Also, the controller 110 may control the communication module 120, the multimedia module 140, the camera module 150, the input/output module 160, the sensor module 170, the storage unit 175, the power supply unit 180, the touch screen 190, and the touch screen controller 195. [0048]When a user input device, such as an input unit 168 or a user's finger, touches, approaches, or is located in proximity to at least one of a plurality of objects or items displayed on the touch screen 190, the controller 110 senses a user input, and identifies an object corresponding to a location at which the user input has been sensed on the touch screen 190. The user input through the touch screen 190 may be one of a direct touch input of directly touching an object, and a hovering input which is an indirect touch input of approaching an object within a predetermined identification distance without directly touching the object. For example, when a user brings the input unit 168 close to the touch screen 190, an object located straightly below the input unit 168 may be selected. The user input may be a gesture input through the camera module 150, a switch/button input through the button 161 or the keypad 166, or a voice input through the microphone 16, other than a user input through the touch screen 190. [0049]The object or item (such as a function item) may be at least one of an application, a menu, document, a widget, a picture, video, E-mail, a Short Message Service (SMS) message, a Multimedia Message Service (MMS) message, and the like, which have been or can be displayed on the touch screen 190 of the mobile terminal 100. The object or item can be selected, executed, deleted, canceled, stored, or changed by the user input device. The item may be a button, an icon (such as a shortcut icon), a thumbnail image, or a folder that stores at least one object in a mobile terminal. The item may be displayed in the form of an image, text, and the like. [0050]A shortcut item is an image that is displayed on the touch screen 190 to quickly execute a call, a contact list, a menu, etc., which are provided by each application or by the mobile terminal 100. If a command or selection for executing a shortcut item is received, the corresponding application is executed. [0051]When the input unit 168 approaches the touch screen 190 or is placed in proximity to the touch screen 190, the controller 110 may sense a user input event such as a hovering event. If a user input event is generated with respect to a predetermined item or according to a predetermined method, the controller 110 performs predetermined program operation corresponding to the user input event. [0052]The controller 110 may output a control signal to the input unit 168 or the vibration device 164. The control signal may include information regarding a vibration pattern, and the input unit 168 or the vibration device 164 may generate vibration according to the vibration pattern. The information regarding the vibration pattern may represent a vibration pattern, an identifier of a vibration pattern, or the like. Alternatively, the control signal may include only a request for generation of vibration. [0053]The mobile terminal 100 may include at least one of the mobile communication module 121, the WLAN module 131, and the short-range communication module 132, according to the function of the mobile terminal 100. [0054]The mobile communication module 121 may connect the mobile terminal 100 to an external electronic device through mobile communication using one or more antennas (not shown) under the control of the controller 110. The mobile communication module 121 may transmit/receive radio signals for a voice call, a video call, a SMS message, or a MMS message to/from a mobile phone (not shown), a smart phone (not shown), a tablet PC (not shown), or another electronic device (not shown) when the corresponding phone number is input to the mobile terminal 100. [0055]The sub communication module 130 may include at least one of the WLAN module 131 and the short-range communication module 132 as described above. For example, the sub communication module 130 may include one of the WLAN module 131 and the short-range communication module 132, or both the WLAN module 131 and the short-range communication module 132. [0056]The WLAN module 131 may be connected to the Internet at a place in which a WAP has been installed, under the control of the controller 110. The WLAN module 131 supports the IEEE802.11x standard. The short-range communication module 132 performs short-range communication between the mobile terminal 100 and an external electronic device in a wireless fashion under the control of the controller 110. The short-range communication may include Bluetooth, Infrared Data Association (IrDA), WiFi-Direct communication, NFC, and the like. [0057]The controller 110 may transmit a control signal according to a haptic pattern to the input unit 168 through the sub communication module 130. [0058]The broadcasting communication module 141 may receive broadcasting signals (for example, TV broadcasting signals, radio broadcasting signals, or data broadcasting signals) and broadcasting additional information (for example, an Electric Program Guide (EPS) or an Electric Service Guide (ESG)) transmitted from a broadcast station through a broadcasting communication antenna (not shown), under the control of the controller 110. [0059]The multimedia module 140 may include the audio play module 142 and the video play module 143 as described above. The audio play module 142 may reproduce a digital audio file (for example, a file with the extension “.mp3”, “.wma”, “.ogg” or “.wav”) that is stored in the storage unit 175 or received from an external device, under the control of the controller 110. The video play module 143 may reproduce a digital video file (for example, a file with the extension “.mpeg”, “.mpg”, “.mp4”, “.avi”, “.mov”, or “.mkv”) that is stored or received, under the control of the controller 110. The multimedia module 140 may be integrated with the controller 110. [0060]The camera module 150 may include at least one of the first and second cameras 151 and 152 for photographing still images or moving images under the control of the controller 110. The camera module 150 may also include at least one among the body tube 155 for zooming in/out to photograph a subject, the motor unit 154, and the flash 153 for providing a secondary light source required for photographing the subject. The first camera 151 may be disposed in the front side of the mobile terminal 100, and the second camera 152 may be disposed in the rear side of the mobile terminal 100. [0061]Each of the first and second cameras 151 and 152 may include a lens system, an image sensor, and the like. Each of the first and second cameras 151 and 152 converts an optical signal received (or photographed) through the lens system into an electrical image signal, and outputs the electrical image signal to the controller 110. Accordingly, a user can photograph a moving image or a still image through the first and second cameras 151 and 152. [0062]The input/output module 160 may include at least one among at least one button 161, at least one microphone 162, at least one speaker 163, at least one vibration device 164, the connector 165, the keypad 166, the earphone connecting jack 167, and the input unit 168. However, the input/output module 160 is not limited to the above-mentioned devices, and a cursor control, such as a mouse, a trackball, a joystick, or cursor direction keys, may also be provided to control the movement of a cursor on the touch screen 190. [0063]The button 161 may be formed on the front, side, or rear surface of the housing (or case) of the mobile terminal 100, and may include at least one among a power/lock button, a volume button, a menu button, a home button, a back button, and a search button. [0064]The microphone 162 may receive a voice or sound under the control of the controller 110 to generate an electrical signal. [0065]The speaker 163 may output sound corresponding to various signals or data (for example, radio data, broadcasting data, digital audio data, digital video data, etc.) out of the mobile terminal 100 under the control of the controller 110. The speaker 163 may output sound (for example, button manipulation sound corresponding to a call, currency connection sound, the other party's voice, etc.) corresponding to a function that is performed by the mobile terminal 100. One or more speakers 163 may be provided at one or more appropriate locations on the housing of the mobile terminal 100. [0066]The vibration device 164 may convert an electrical signal into mechanical vibration under the control of the controller 110. For example, if a voice or video call is made by another device (not shown) when the mobile terminal 100 is in a vibration mode, the vibration device 164 operates. One or more vibration devices 164 may be provided in the housing of the mobile terminal 100. The vibration device 164 may operate in correspondence to a user input through the touch screen 190. [0067]The connector 165 may be used as an interface for connecting the mobile terminal 100 to an external electronic device or a power source (not shown). The controller 110 may transmit data stored in the storage unit 175 to an external electronic device or receive data from the external electronic device through a wired cable connected to the connector 165. The mobile terminal 100 may receive power from a power source or charge a battery using the power source through the wired cable connected to the connector 165. [0068]The keypad 166 may receive a key input from a user to control the mobile terminal 100. The keypad 166 includes a physical keypad (not shown) formed on the mobile terminal 100 or a virtual keypad (not shown) displayed on the touch screen 190. The physical keypad formed on the mobile terminal 100 may be excluded according to the performance or structure of the mobile terminal 100. [0069]The earphone (not shown) may be inserted into the earphone connecting jack 167 to connect to the mobile terminal 100. [0070]The input unit 168 may be inserted into and held in the mobile terminal 100, and when in use, the input unit 168 may be drawn or separated from the mobile terminal 100. A detachment/attachment recognition switch 169 that operates in correspondence to attachment and detachment of the input unit 168 may be provided in an area of the mobile terminal 100 into which the input unit 168 is inserted. The detachment/attachment recognition switch 169 may output a signal corresponding to attachment/separation of the input unit 168 to the controller 110. The detachment/attachment recognition switch 169 may be configured to directly or indirectly contact the input unit 168 when the input unit 169 is attached in the mobile terminal 100. Accordingly, the detachment/attachment recognition switch 169 generates a signal (i.e., a signal for notifying attachment or separation of the input unit 168) corresponding to attachment or separation of the input unit 168 based on whether the detachment/attachment recognition switch 169 contacts the input unit 168, and outputs the signal to the controller 110. [0071]The sensor module 170 may include at least one sensor for detecting the state of the mobile terminal 100. For example, the sensor module may include at least one sensor among a proximity sensor (not shown) for detecting an approach to the mobile terminal 100, an ambient light sensor (not shown) for detecting the ambient light intensity around the mobile terminal 100, a motion sensor (not shown) for detecting a motion (for example, rotation, acceleration, vibration) of the mobile terminal 100, a geo-magnetic sensor (not shown) for detecting a point of the compass of the mobile terminal 100 using the earth's magnetic field, a gravity sensor (not shown) for detecting a direction in which gravity is applied, an altimeter (not shown) for measuring atmospheric pressure to detect an altitude, and a GPS module 157. A camera sensor for sensing a user's gesture may also be included in the sensor module 170. [0072]The motion sensor among the above-mentioned sensors senses the location, movement, and the like of the mobile terminal 100 using an acceleration sensor, a gyro sensor, a tilt sensor, or their combinations. However, the sensors are not limited to the above-mentioned sensors, and may include other types of a sensor capable of sensing the reciprocating motions, movement directions, and the like of the mobile terminal 100. [0073]Sensing data (that is, motion information) output through the motion sensors may have a direction and a magnitude. For example, an acceleration sensor for sensing the acceleration of the mobile terminal 100 can sense acceleration with respect to at least one reference-axis direction of x, y, and z axes, and output the acceleration information. The reference-axis may be an axis (for example, the up-down (z-axis), left-right (x-axis), and front-rear (y-axis) directions of the mobile terminal 100) according to the direction of the mobile terminal 100, or may be an axis according to the direction of gravity (the direction (z-axis) of gravity and directions (z and y axes) perpendicular to the direction of gravity). [0074]The sensor module 170 may further include a calculator (not shown) for integrating sensed angular velocity, velocity, etc. over time to calculate a rotation angle, a direction, velocity, a travel distance, a location, a trajectory, and the like according to a motion of the mobile terminal 100, and output the calculated information. The calculator may be included in the controller 110. The calculator may also include a frequency filter for blocking or passing a specific band of a signal such as sensed acceleration in order to calculate a trajectory, etc. or effectively analyze the direction of a motion. [0075]When the sensor module 170 includes the calculator, the calculator may calculate a direction or angle in or at which the mobile terminal 100 moves, and transfer the result of the calculation to the controller 100. However, the direction or angle in or at which the mobile terminal 100 moves may be calculated by the controller 110. The direction in which the mobile terminal 100 moves may be basically an up-down direction or a left-right direction. The direction in which the mobile terminal 100 moves may be a front direction in which the mobile terminal 100 is pulled horizontally toward a user or a back direction in which the mobile terminal 100 is pushed horizontally against the user. A tilting direction in which the mobile terminal 100 is tilted with respect to a reference axis is included in the direction of a motion. When the angle at which the mobile terminal 100 moves is calculated in a direction which the mobile terminal 100 is tilted under an assumption that the current position of the mobile terminal 100 is at 0 degree, a direction diagonal to the direction in which the mobile terminal 100 moves also may be included in the direction of a motion. [0076]According to an exemplary embodiment of the present invention, the sensor module 170 may also include a breath detection sensor for using a user's breath as a control command to change the configuration of a layout according to the user's breath. The breath detection sensor is attached on the outer surface of the mobile terminal 100, and detects a user's breath or wind brown through an inlet. The breath detection sensor may be a wind velocity sensor that outputs an electrical signal according to a user's breath. The wind velocity sensor transfers an output value that increases at a constant rate according to a user's breath intensity to the controller 110. Alternatively, the breath detection sensor may be a temperature sensor or a humidity sensor capable of sensing a user's breath, in which case the temperature sensor or the humidity sensor can transfer various levels of output values to the controller 110 according to a user's breath intensity. [0077]The GPS module 157 can receive radio waves from a plurality of GPS satellites (not shown) on the orbit around the earth, and calculate the location of the mobile terminal 100 based on a time of arrival of the radio waves from the GPS satellites to the mobile terminal 100. [0078]The storage unit 175 may store signals or data that is input/output according (String), 优先 [0001] 此申请根据 35 U.S.C. 2013 年 2 月 22 日向韩国知识产权局提交的韩国专利申请的第 119(a) 条,并转让了序列号 10-2013-0019508,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及一种用于管理在触摸屏上显示的多个对象的设备和方法。 更具体地,本发明涉及一种用于允许移动终端的用户根据移动终端的动作容易地改变触摸屏上的多个对象的显示的设备和方法 [0004] 2.相关技术的描述 [0005] 具有安装在显示设备上的触摸面板的触摸屏显示图像并允许用户在不使用键盘或鼠标的情况下轻松输入命令。 触摸屏已广泛应用于各种电子设备,例如移动终端、导航系统、电视、自动柜员机(ATM)、销售点(POS)系统等。 [0006] 例如,随着移动终端可以提供的各种服务和附加功能,最近的许多移动终端都提供了基于触摸屏的图形用户界面(GUI)。 [0007] 为了提高此类移动终端的有效价值并满足用户的需求,正在开发可在移动终端中执行的各种应用程序。 [0008] 移动终端可以存储移动终端制造公司开发的基本应用程序,以及通过互联网从应用程序销售网站下载的附加应用程序,并执行这些应用程序。 [0009] 相应地,移动终端,例如最新的智能手机、平板电脑等,存储了至少数百个应用程序,并且用于单独执行应用程序的快捷键以图标的形式显示在移动终端的触摸屏上 . 用户可以触摸显示在移动终端的触摸屏上的图标之一,从而在移动终端上执行期望的应用。 移动终端的触摸屏上还可以显示除快捷键之外的各种可视对象,如小部件、图片、文档等。 [0010] 然而,随着这种各种视觉对象的数量增加,出现了另一个问题。 移动终端虽然存储了很多可视对象,但在移动终端的小屏幕上可以显示的对象的数量是有限的。 [0011] 因此,由于显示屏幕的空间限制,需要对可显示在屏幕上的视觉对象进行分类和排列。 然而,将布局的组成部分等间隔排列是不够的,需要用户能够方便地管理移动终端屏幕上显示的可视对象,例如对可视对象进行编辑、移动或删除等。 现有技术中,当用户想要改变对象的显示时,需要将自己的移动终端屏幕转换为Edit环境,并输入删除或更正对象的命令,造成繁重不便,需要 很长一段时间的编辑。 [0012] 上述信息仅作为背景信息提供以帮助理解本公开。 没有做出任何决定,也没有做出断言,关于上述任何内容是否可以用作关于本发明的现有技术。 [0013] 上述信息仅作为背景信息提供以帮助理解本公开。 没有做出任何决定,也没有做出断言,关于上述任何内容是否可以用作关于本发明的现有技术。 发明内容 [0014]本发明的方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面是提供一种允许用户方便地改变布局的组件的设备和方法,其中多个对象根据他/她的期望图案排列。 [0015] 本发明的另一方面在于提供一种用于容易地控制多个对象的布置以及其中根据移动终端的运动布置对象的布局的显示的设备和方法。 [0016] 根据本发明的一方面,提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括显示包括多个区域的布局,其中分别显示多个对象,接收与移动终端的操作相关的输入,改变与与移动终端相关的输入对应的多个区域中的一个或多个区域。 移动终端的操作,以及显示包括改变区域的布局。 [0017] 根据本发明的另一方面,提供了一种用于根据与移动终端的操作相关的输入来控制多个对象的显示的移动终端。 移动终端包括:显示单元,被配置为显示包括多个区域的布局,在该多个区域中分别显示多个对象;传感器模块,被配置为检测与移动终端的操作相关的输入;以及控制器,被配置为改变 对应于与移动终端的操作相关的输入的多个区域中的一个或多个,并控制显示单元显示包括改变的区域的布局。 [0018] 通过以下详细描述,本发明的其他方面、优点和显着特征对于本领域技术人员将变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0019] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0020] 如图。 附图说明图1是示出根据本发明示例性实施例的移动终端的框图; [0021] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图; [0022] 如图。 图3是根据本发明示例性实施例的移动终端的后透视图; [0023] 如图。 图4是根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图; [0024] 图 图5A至图8B示出了用于解释根据本发明示例性实施例的构成布局的区域根据移动终端的往复运动方向改变的处理的示例; [0025] 图 图9A至9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的处理的示例; [0026] 图 图10A~图11D是用于说明本发明的实施方式的布局的排列规则的图。 [0027] 如图。 图12是用于说明根据本发明示例性实施例的移动终端中改变构成布局的区域的方法的流程图; [0028] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的特性将不同对象分别显示在构成布局的区域上的处理的示例; [0029]图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; [0030] 图 图15A至图15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例; [0031] 如图。 图16是用于说明根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; 和 [0032] 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0033] 在整个附图中,相同的附图标记将被理解为指代相同的部件、组件和结构。 示例性实施例的详细描述 [0034] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,可以省略对众所周知的功能和结构的描述。 [0035] 以下描述和权利要求中使用的术语和词语不限于书目含义,而仅由发明人使用以使对本发明的理解清晰一致。 因此,本领域技术人员应当清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物定义的本发明。 [0036] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0037] 应当理解,尽管在本文中可以使用术语第一、第二等来描述各种元素,但是这些元素不应受到这些术语的限制。 这些术语仅用于区分一个元素与另一个元素。 例如,可以将第一元件称为第二元件,并且类似地,可以将第二元件称为第一元件,而不脱离本发明的范围。 如本文所用,单数形式“a”、“an”和“the”旨在也包括复数形式,除非上下文另有明确指示。 [0038] 下面将描述的示例性实施例涉及手持终端,然而,根据本发明示例性实施例的用于管理显示在触摸屏上的多个对象的设备和方法可以应用于各种电子设备 具有触摸屏,例如导航系统、电视(TV)、自动柜员机(ATM)、销售点(POS)系统等,以及移动终端,例如移动 手机、智能手机、平板电脑等。 [0039] 此外,在以下描述中,移动终端可以是柔性设备或柔性显示设备。 作为代表性的移动终端,假设是移动电话,并且可以根据需要省略或改变这种移动终端的一些组件。 [0040]本发明的示例性实施例提供了一种根据与移动终端的运动相关的输入来控制多个对象的显示的方法。 当显示包括显示多个对象的区域的布局时,接收移动终端,构成布局的区域中与移动终端的运动相关的输入对应的一个或多个区域; 以及显示由改变的区域组成的布局的操作。 与移动终端的动作相关的输入可以对应于移动终端的动作、用户的呼吸、手势等。 根据本发明的示例性实施例,如果在构成布局的区域之一被触摸时检测到与移动终端的运动相关的输入,则重新排列除了被触摸区域之外的其余区域。 在这种情况下,分别显示在剩余区域中的对象可以是与显示在触摸区域上的对象的属性相对应的搜索对象。 因此,用户可以容易地改变与布局的区域相对应的组件,以及改变布局的区域。 [0041] 如图。 图1是示出根据本发明示例性实施例的移动终端的框图。 [0042] 参考图。 1、移动端 100 可以使用通信模块中的至少一个连接到外部电子设备(未示出) 120 , 一个连接器 165 和耳机连接插孔 167 . 外部电子设备可以包括耳机、外部扬声器、通用串行总线(USB)存储器、电池充电器、底座/底座、数字多媒体广播(DMB)天线、移动支付系统、医疗保健设备(血液 血糖仪等)、游戏、车载导航系统等,可拆卸地连接到移动终端 100 通过一条线。 外部电子设备可以包括蓝牙通信装置、近场通信(NFC)装置、WiFi Direct通信装置、无线接入点(WAP)等,它们可以连接到移动终端 100 以无线方式。 移动终端 100 可以有线/无线方式连接到其他移动终端或电子设备(例如,手机、智能手机、平板电脑、台式电脑和服务器)之一。 [0043] 移动终端 100 包括一个触摸屏 190 和至少一个触摸屏控制器 195 . 移动终端 100 还可以包括控制器 110 , 通讯模块 120 , 多媒体模块 140 , 一个摄像头模块 150 , 输入/输出模块 160 , 一个传感器模块 170 , 一个存储单元 175 , 和一个电源单元 180 . [0044] 通讯模块 120 包括一个移动通信模块 121 , 一个子通信模块 130 ,以及广播通信模块 141 . [0045] 子通讯模块 130 包括至少一个无线 LAN (WLAN) 模块 131 和一个短距离通信模块 132 . 多媒体模块 140 包括至少一个音频播放模块 142 和一个视频播放模块 143 . 摄像头模组 150 可以包括第一相机中的至少一个 151 和第二台相机 152 . 摄像头模组 150 还可以包括至少一个体管 155 用于放大/缩小第一台和/或第二台摄像机 151 或者 152 , 一个电机单元 154 用于控制体管的运动 155 , 和一个闪光灯 153 根据移动终端的主要用途,为拍照提供光源 100 . 输入/输出模块 160 可以包括至少一个按钮 161 , 麦克风 162 , 扬声器 163 , 振动装置 164 , 连接器 165 , 和一个键盘 166 . [0046] 控制器110 可能包括一个 CPU 111 , 只读存储器 (ROM) 112 存储用于控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 存储从外部接收的信号或数据或用作移动终端正在执行的任务的存储区域 100 . 中央处理器 111 可以包括一个或多个核,例如单核、双核、三核或四核。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线相互连接。 [0047] 此外,控制器 110 可以控制通讯模块 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 存储单元 175 , 电源单元 180 , 触摸屏 190 , 和触摸屏控制器 195 . [0048] 当用户输入设备,例如输入单元 168 或用户的手指、触摸、接近或位于触摸屏上显示的多个对象或项目中的至少一个的附近 190 , 控制器 110 感测用户输入,并识别与在触摸屏上感测到用户输入的位置相对应的对象 190 . 用户通过触摸屏输入 190 可以是直接触摸对象的直接触摸输入和不直接触摸对象而接近预定识别距离内的对象的间接触摸输入的悬停输入之一。 例如,当用户将输入单元 168 靠近触摸屏 190 , 位于输入单元正下方的对象 168 可以选择。 用户输入可以是通过相机模块的手势输入 150 , 一个开关/按钮通过按钮输入 161 或键盘 166 ,或通过麦克风输入的语音 16 , 除了通过触摸屏的用户输入 190 . [0049] 对象或项(例如功能项)可以是应用程序、菜单、文档、小部件、图片、视频、电子邮件、短消息服务(SMS)消息、多媒体消息服务中的至少一个 (MMS)消息等,已经或可以在触摸屏上显示 190 移动终端的 100 . 对象或项目可以由用户输入设备选择、执行、删除、取消、存储或改变。 该项目可以是按钮、图标(例如快捷方式图标)、缩略图或移动终端中存储至少一个对象的文件夹。 该项目可以以图像、文本等的形式显示。 [0050] 快捷项目是显示在触摸屏上的图像 190 快速执行各个应用或移动终端提供的通话、联系人列表、菜单等 100 . 如果接收到用于执行快捷方式项的命令或选择,则执行相应的应用程序。 [0051] 当输入单元 168 接近触摸屏 190 或放置在触摸屏附近 190 , 控制器 110 可以感测用户输入事件,例如悬停事件。 如果针对预定项目或根据预定方法生成用户输入事件,则控制器 110 执行对应于用户输入事件的预定程序操作。 [0052] 控制器 110 可以向输入单元输出控制信号 168 或振动装置 164 . 控制信号可以包括关于振动模式的信息,以及输入单元 168 或振动装置 164 可以根据振动模式产生振动。 关于振动模式的信息可以表示振动模式、振动模式的标识符等。 或者,控制信号可以仅包括产生振动的请求。 [0053] 移动终端 100 可以包括至少一个移动通信模块 121 , WLAN 模块 131 , 和短距离通信模块 132,根据手机端的功能 100 . [0054] 移动通信模块 121 可以连接移动终端 100 在控制器的控制下,使用一根或多根天线(未显示)通过移动通信连接到外部电子设备 110 . 移动通信模块 121 可以向/从移动电话(未示出)、智能手机(未示出)、平板电脑(未示出)发送/接收用于语音呼叫、视频呼叫、SMS消息或MMS消息的无线电信号, 当对应的电话号码输入到移动终端时,或另一个电子设备(未示出) 100 . [0055] 子通讯模块 130 可以包括至少一个 WLAN 模块 131 和短距离通信模块 132 如上所述。 例如子通信模块 130 可能包括 WLAN 模块之一 131 和短距离通信模块 132 , 或两者 WLAN 模块 131 和短距离通信模块 132 . [0056] 无线局域网模块 131 在控制器的控制下,可以在安装了 WAP 的地方连接到 Internet 110 . 无线局域网模块 131 支持 IEEE802.11x 标准。 短距离通信模块 132 在移动终端之间进行短距离通信 100 以及在控制器控制下以无线方式的外部电子设备 110 . 短距离通信可以包括蓝牙、红外数据协会(IrDA)、WiFi-Direct通信、NFC等。 [0057] 控制器 110 可以根据触觉模式向输入单元发送控制信号 168 通过子通讯模块 130 . [0058] 广播通信模块 141 可以接收广播信号(例如,电视广播信号、无线电广播信号或数据广播信号)和广播从广播站发送的附加信息(例如,电子节目指南(EPS)或电子服务指南(ESG)) 通过广播通信天线(未显示),在控制器的控制下 110 . [0059] 多媒体模块 140 可能包括音频播放模块 142 和视频播放模块 143 如上所述。 音频播放模块 142 可以再现存储在存储单元中的数字音频文件(例如,扩展名为“.mp3”、“.wma”、“.ogg”或“.wav”的文件) 175 或从外部设备接收,在控制器的控制下 110 . 视频播放模块 143 可以复制存储或 收到,在控制器的控制下 110 . 多媒体模块 140 可与控制器集成 110 . [0060] 摄像头模组 150 可以包括第一和第二相机中的至少一个 151 和 152 在控制器的控制下拍摄静止图像或运动图像 110 . 摄像头模组 150 还可以包括至少一种管体 155 用于放大/缩小拍摄对象,电机单元 154 , 和闪光灯 153 用于提供拍摄对象所需的辅助光源。 第一台相机 151 可以设置在移动终端的正面 100 , 和第二台相机 152 可以设置在移动终端的背面 100 . [0061] 第一和第二相机中的每一个 151 和 152 可以包括透镜系统、图像传感器等。 第一和第二相机中的每一个 151 和 152 将通过镜头系统接收(或拍摄)的光信号转换为电图像信号,并将电图像信号输出到控制器 110 . 因此,用户可以通过第一和第二相机拍摄运动图像或静止图像 151 和 152 . [0062] 输入/输出模块 160 可以包括至少一个按钮中的至少一个 161 , 至少一个麦克风 162 , 至少一位发言者 163 , 至少一个振动装置 164 , 连接器 165 , 键盘 166 , 耳机连接插孔 167 , 和输入单元 168 . 然而,输入/输出模块 160 不限于上述设备,还可以提供鼠标、轨迹球、操纵杆或光标方向键等光标控件来控制光标在触摸屏上的移动 190 . [0063] 按钮 161 可以形成在移动终端的外壳(或外壳)的正面、侧面或背面 100 ,并且可以包括电源/锁定按钮、音量按钮、菜单按钮、主页按钮、返回按钮和搜索按钮中的至少一个。 [0064] 麦克风 162 可以在控制器的控制下接收语音或声音 110 产生电信号。 [0065] 演讲者 163 可以将与各种信号或数据(例如,无线电数据、广播数据、数字音频数据、数字视频数据等)对应的声音输出到移动终端之外 100 在控制器的控制下 110 . 演讲者 163 可以输出与移动终端执行的功能对应的声音(例如,与呼叫对应的按钮操作声音、货币连接声音、对方的语音等) 100 . 一位或多位演讲者 163 可以在移动终端的外壳上的一个或多个适当位置提供 100 . [0066] 振动装置 164 可在控制器的控制下将电信号转换为机械振动 110 . 例如,如果在移动终端时由另一个设备(未示出)进行语音或视频通话 100 处于振动模式时,振动装置 164 运作。 一个或多个振动装置 164 可以设置在移动终端的外壳中 100 . 振动装置 164 可以对应于通过触摸屏的用户输入进行操作 190 . [0067] 连接器 165 可作为连接移动终端的接口 100 连接到外部电子设备或电源(未显示)。 控制器 110 可以传输存储在存储单元中的数据 175 到外部电子设备或通过连接到连接器的有线电缆从外部电子设备接收数据 165 . 移动终端 100 可以通过连接到连接器的有线电缆从电源接收电力或使用电源为电池充电 165 . [0068] 键盘 166 可以接收来自用户的按键输入以控制移动终端 100 . 键盘 166 包括在移动终端上形成的物理键盘(未显示) 100 或触摸屏上显示的虚拟键盘(未显示) 190 . 在移动终端上形成的物理键盘 100 可根据移动终端的性能或结构排除 100 . [0069] 耳机(未显示)可以插入耳机连接插孔 167 连接到移动终端 100 . [0070] 输入单元 168 可插入并保持在移动终端中 100 ,而在使用时,输入单元 168 可从移动终端抽出或分离 100 . 脱离/附着识别开关 169 对应于输入单元的安装和拆卸进行操作 168 可以设置在移动终端的区域内 100 输入单元 168 被插入。 分离/附着识别开关 169 可以输出与输入单元的连接/分离相对应的信号 168 到控制器 110 . 分离/附着识别开关 169 可配置为直接或间接接触输入单元 168 当输入单元169 附在手机端 100 . 因此,分离/附着识别开关 169 产生一个信号(即,用于通知输入单元的连接或分离的信号 168 ) 对应于输入单元的连接或分离 168 基于是否分离/附着识别开关 169 接触输入单元 168 , 并将信号输出到控制器 110 . [0071] 传感器模块 170 可以包括至少一个传感器,用于检测移动终端的状态 100 . 例如,传感器模块可以包括用于检测接近移动终端的接近传感器(未示出)中的至少一个传感器 100 ,环境光传感器(未示出),用于检测移动终端周围的环境光强度 100 ,用于检测移动终端的运动(例如,旋转、加速度、振动)的运动传感器(未示出) 100 ,地磁传感器(未示出),用于检测移动终端的罗盘点 100 使用地球磁场,用于检测施加重力的方向的重力传感器(未示出),用于测量大气压力以检测高度的高度计(未示出),以及GPS模块 157 . 用于感测用户手势的相机传感器也可以包括在传感器模块中 170 . [0072] 上述传感器中的运动传感器感知移动终端的位置、运动等 100 使用加速度传感器、陀螺仪传感器、倾斜传感器或它们的组合。 然而,传感器不限于上述传感器,还可以包括能够感测移动终端的往复运动、移动方向等的其他类型的传感器。 100 . [0073] 通过运动传感器输出的感测数据(即运动信息)可以具有方向和幅度。 例如,用于感应移动终端加速度的加速度传感器 100 可以感应相对于x、y和z轴中至少一个参考轴方向的加速度,并输出加速度信息。 参考轴可以是移动终端的轴(例如,上下(z轴)、左右(x轴)和前后(y轴)方向) 100 ) 根据移动端的方向 100 ,或者可以是根据重力方向的轴(重力方向(z轴)和垂直于重力方向的方向(z和y轴))。 [0074] 传感器模块 170 还可以包括计算器(未示出),用于将感测到的角速度、速度等随时间积分以根据物体的运动计算旋转角度、方向、速度、行进距离、位置、轨迹等。 移动终端 100 ,并输出计算得到的信息。 计算器可能包含在控制器中 110 . 计算器还可以包括频率滤波器,用于阻止或通过特定频带的信号,例如检测到的加速度,以便计算轨迹等或有效地分析运动的方向。 [0075] 当传感器模块 170 包括计算器,计算器可以计算移动终端所处的方向或角度 100 移动,并将计算结果传送给控制器 100 . 但是,移动终端所处的方向或角度 100 移动可由控制器计算 110 . 移动终端的方向 100 移动基本上可以是上下方向或左右方向。 移动终端的方向 100 移动可以是移动终端所处的正面方向 100 被水平拉向用户或移动终端所在的后退方向 100 被水平推向用户。 移动终端的倾斜方向 100 相对于参考轴倾斜 包含在运动方向中。 当移动终端的角度 100 移动是在移动终端的方向上计算的 100在假设移动终端的当前位置是倾斜的 100 为0度,与移动终端所在方向的对角线方向 100 运动也可以包含在运动的方向中。 [0076] 根据本发明的示例性实施例,传感器模块 170 还可以包括呼吸检测传感器,用于使用用户的呼吸作为控制命令来根据用户的呼吸改变布局的配置。 呼吸检测传感器贴附在移动终端的外表面上 100 ,并通过入口检测用户的呼吸或风棕色。 呼吸检测传感器可以是根据用户的呼吸输出电信号的风速传感器。 风速传感器将根据用户的呼吸强度以恒定速率增加的输出值传输到控制器 110 . 或者,呼吸检测传感器可以是能够感测用户呼吸的温度传感器或湿度传感器,在这种情况下,温度传感器或湿度传感器可以将各种级别的输出值传递给控制器 110 根据用户的呼吸强度。 [0077] GPS模块 157 可以接收来自环绕地球轨道上的多个GPS卫星(未图示)的无线电波,并计算移动终端的位置 100 基于从 GPS 卫星到移动终端的无线电波的到达时间 100 . [0078] 存储单元 175 可以存储根据通信模块的操作输入/输出的信号或数据 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 或触摸屏 190 , 在控制器的控制下 110 . 存储单元 175 可以存储用于控制移动终端的应用程序和控制程序 100 或控制器 110 . [0079] 术语“存储单元”表示任意数据存储设备,例如存储单元 175 , 只读存储器 112 和内存 113 在控制器中 110 ,安装在移动终端中的存储卡(例如,SD卡或记忆棒) 100 ,等等。 存储单元 175 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)和固态驱动器(SSD)。 [0080] 存储单元 175 可以存储具有各种功能的应用程序,例如导航、视频通话、游戏、基于时间的警报应用程序等、用于为用户提供与应用程序相关联的图形用户界面 (GUI) 的图像、用户信息、文档、数据库 或与处理触摸输入的方法、背景图像(菜单屏幕、锁定屏幕等)或驱动移动终端所需的操作程序有关的数据 100 , 摄像头模块拍摄的图像 150 等存储单元 175 还可以存储与合成图像提供方法相关的数据。 [0081] 存储单元 175 是机器(例如,计算机)可读介质,术语“机器可读介质”可以定义为向机器提供数据以使机器能够执行特定功能的介质。 存储单元 175 可能包括非易失性介质和易失性介质。 这样的介质需要是有形的,以便传送到介质的命令可以被使用机器读取命令的物理工具检测到。 [0082] 机器可读介质包括软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、穿孔卡、纸带中的至少一种。 、RAM、可编程只读存储器(PROM)、可擦除PROM(EPROM)和FLASH-EPROM,然而,机器可读介质不限于上述设备。 [0083] 电源单元 180 可以为安装在移动终端外壳中的一个或多个电池供电 100 在控制器的控制下 110 . 一节或多节电池为移动终端供电 100. 电源单元 180 可以将从外部电源接收的电力提供给移动终端 100 通过连接到连接器的有线电缆 165 . 电源单元 180 可以将从外部电源无线接收的电力提供给移动终端 100 通过无线充电技术。 [0084] 移动终端 100 可能包括至少一个触摸屏 190 为用户提供与各种服务(例如,通话、数据传输、拍照)相对应的GUI。 [0085] 触摸屏 190 可以将与输入到用户图形界面的至少一个用户输入相对应的模拟信号输出到触摸屏控制器 195 . 触摸屏 190 可以通过用户的身体部位(例如,包括拇指的手指)或输入单元接收至少一个用户输入 168 (例如,手写笔或电子笔)。 触摸屏 190 可以接收触摸的连续移动(例如,拖动输入)。 触摸屏 190 可以将与触摸的连续移动对应的模拟信号输出到触摸屏控制器 195 . [0086] 在本说明书中,术语“触摸”不限于手指或输入单元的接触 168 到触摸屏 190 ,并且可以包括非接触式识别(例如,当用户输入设备位于识别距离(例如,1 cm)内时,用户输入设备可以在不直接接触触摸屏的情况下被检测到) 190 )。 触摸屏的识别距离 190 能否识别用户输入设备可能取决于移动终端的性能或结构 100 . 为了触摸屏 190 为了区分与用户输入设备直接接触产生的直接触摸事件和间接触摸事件(即悬停事件),触摸屏 190 可以被配置为根据直接触摸事件和悬停事件输出不同的值(例如,包括电压值和电流值的模拟值)。 [0087] 触摸屏 190 可以是电阻式触摸屏、电容式触摸屏、红外触摸屏、声波触摸屏或它们的组合。 [0088] 触摸屏 190 还可以包括至少两个触摸面板,分别用于感应手指和输入单元的触摸或接近 168 分别接收手指和输入单元的输入 168 . 至少两个触摸面板针对手指和输入单元的输入提供不同的输出值 168 到触摸屏控制器 195 , 和触摸屏控制器 195 识别从至少两个触摸面板接收到的不同输出值,以确定触摸屏是否有输入 190 是手指输入还是输入单元输入 168 . [0089] 触摸屏控制器 195 转换从触摸屏接收到的模拟信号 190 转换成数字信号,并将数字信号传输给控制器 110 . 控制器 110 可以控制触摸屏 190 使用从触摸屏控制器接收到的数字信号 195 . 例如,控制器 110 可以选择或执行显示在触摸屏上的快捷方式图标或对象 190 响应直接触摸事件或悬停事件。 触摸屏控制器 195 可以集成到控制器中 110 . [0090] 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值) 190 确定悬停间隔或距离以及用户的输入位置,将确定的距离值转换为数字信号(例如z坐标),然后将数字信号提供给控制器 110 . 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值) 190估计用户输入设备按压触摸屏的压力 190 ,将估计的压力值转换为数字信号,然后将数字信号提供给控制器 110 . [0091] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图,以及图2是根据本发明示例性实施例的移动终端的前透视图。 图3是根据本发明示例性实施例的移动终端的后透视图。 [0092] 参考图。 1-3、触摸屏 190 放置在正面的中央 101 移动终端的触摸屏 190 可以形成占据正面主要部分的大面积 101 移动终端的图。 图2示出了在触摸屏上显示主主屏幕的示例 190 . 主主屏幕是最初出现在触摸屏上的屏幕 190 当移动端 100 通电。 如果移动端 100 具有多个页面的不同主屏幕,主主屏幕可以是主屏幕中的第一个主屏幕。 主屏幕可能会显示快捷方式图标 191 - 1 , 191 - 2 , 和 191 - 3 用于执行常用应用程序,主菜单转换键 191 - 4 、当前时间、天气信息等。如果用户选择主菜单转换键 191 - 4 , 触摸屏上显示菜单画面 190 . 状态栏 192 代表移动终端的状态 100 可在触摸屏上方显示电池充电状态、接收信号强度、当前时间等 190 . [0093] 一个主页按钮 161 a, 一个菜单按钮 161 b, 和一个后退按钮 161 c 可能会显示在触摸屏的下部 190 . 主页按钮 161 a 用于在触摸屏上显示主主屏幕 190 . 例如,如果主页按钮 161 a 当触摸屏上显示除主主屏幕或菜单屏幕之外的另一个主屏幕时选择 190 , 主屏幕可能会显示在触摸屏上 190 . 如果主页按钮 161 a 在触摸屏上执行应用程序时选择 190 ,主屏幕如图所示。 2 可在触摸屏上显示 190 . 主页按钮 161 a 可用于在触摸屏上显示最近使用的应用程序 190 或在触摸屏上显示任务管理器 190 . [0094] 菜单按钮 161 b 提供可在触摸屏上显示的链接菜单 190 . 链接菜单可以包括小部件添加菜单、锁屏改变菜单、搜索菜单、编辑菜单、设置菜单等。 [0095] 后退按钮 161 c 可用于显示恰好在当前正在执行的屏幕之前执行的屏幕或终止最近使用的应用程序。 [0096] 第一台相机 151 , 环境光传感器 170 a, 和接近传感器 170 b 可以设置在移动终端正面的一个边缘部分 100 . 第二台相机 152 , 闪光 153 , 和扬声器 163 可以设置在背面 103 移动终端的 100 . [0097] 在移动终端的侧面 102 ,例如,电源/锁定按钮 161 d, 音量按钮 161 e 包括一个音量增大按钮 161 f 和一个音量减小按钮 161 g, 地面DMB天线 141 a 用于接收广播,一个或多个麦克风 162 等。 DMB 天线 141 a 可以固定或可拆卸地附在移动终端上 100 . [0098] 连接器 165 形成在移动终端下端的侧面 10 . 连接器 165包括多个电极,并且可以通过线路连接到外部设备。 耳机连接插孔 167 可以形成在移动终端上端的侧面 100 . 耳机可插入耳机连接插孔 167 . [0099] 输入单元 168 可安装在移动终端下端的侧面 100 . 输入单元 168 可插入移动终端内部 100 并存储在移动终端中 100 ,而在使用时,输入单元 168 与移动端分离 100 . [0100] 随着用户在移动终端上以各种形式显示多个视觉对象的愿望的增加 100 通过上述结构,例如,在相册应用的情况下,用户可以通过轻弹或拖拽手势在将图片排列在布局的预定区域上的屏幕上翻页的同时查看许多图片。 触摸屏 190 . [0101] 然而,为了让用户改变图片的排列和显示图片的区域,用户必须在编辑屏幕上编辑层,这可能需要很长时间。 此外,用户倾向于将关联图片收集到特定文件夹中,以便轻松快速地找到想要的图片或关联图片。 [0102] 因此,根据本发明的示例性实施例,提供了一种用于在触摸屏上容易且快速地改变由显示视觉对象的区域组成的布局的方法和设备 190 ,根据移动终端的动作 100 当用户选择特定对象时,提供一种布局,在该布局中,考虑到所选对象的属性,显示与所选对象相关联的对象。 [0103] 如图。 图4是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 [0104] 参考图。 参照图4,将参照图1和图4所示的示例来描述改变构成布局的区域的方法。 然而,在图5A至8B中,该方法不限于图5A至图8B中所示的示例。 5A到8B。 此外,根据本发明的示例性实施例,例如,当执行故事专辑应用程序时,将作为示例描述显示划分为预定数量的区域的布局并改变布局的组件的方法。 然而,对于本领域普通技术人员来说显而易见的是,根据移动终端的运动改变布局的组件的方法可以应用于各种显示屏幕。 [0105] 在步骤 400 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 . 在本说明书中,配置布局的“区域”也可以称为“网格”、“部分”等。 [0106] 图 图5A到8B示出了根据本发明示例性实施例的用于解释构成布局的区域根据移动终端的往复运动的方向改变的处理的示例。 [0107] 参考图。 参见图 5A-8B, 图5A示出了在触摸屏上显示对象的显示屏的示例 190 布局由区域 A、B、C 和 D 组成。可在各个区域上显示的对象可能包括图片、插图、字母(字体、类型)、字符等组件,还包括各种 视觉对象,例如各种内容(例如,文本)、用于执行应用程序的快捷图标、小部件、表示具有各种文件格式的文档的图标、文件夹等。对象还可以包括从视觉对象中选择的一些视觉对象。 [0108] 当显示画面如图所示。 如图5A所示,用户可以通过摇动移动终端来改变布局区域的排列 100 与移动终端 100 在用户手中。 在步骤 405 , 控制器110 判断移动终端是否往复运动 100 通过传感器模块检测到 170 . 如果移动终端的往复运动 100 检测到,然后在步骤中确定检测到的往复运动的方向 410 . 控制器 110 判断移动终端往复运动的方向是否 100 基于通过传感器模块收集的传感器信号对应于上下方向、左右方向和对角方向中的哪个方向 170 . 在步骤 415 , 控制器 110 根据确定的往复运动方向改变构成布局的区域,并在步 420 , 控制器 110 显示使用更改区域重新配置的布局。 [0109] 如图。 图5B示出了当用户摇动移动终端时的示例 100 在左右方向 500 , 左右方向对齐的区域排列 500 根据本发明的示例性实施例改变。 [0110] 参考图。 5B,如果用户摇动移动终端 100 在左右方向上预定次数(例如一次或两次) 500 与移动终端 100 在用户手中时,屏幕如图所示。 显示图5A,在左右方向上对齐的区域排列 500 在布局更改的区域之间。 在图。 在图5A中,区域A、B、C和D中的区域B和C对应于可以根据左右方向上的往复运动而改变的区域 500 ,因此,在左右方向的往复运动之后 500 执行后,区域B和C的布置改变如图6所示。 5B。 显示在图1的区域B中的对象。 图5A移动到并显示在图5的区域B中。 图5B的区域C中显示的对象。 图5A移动到并显示在图5的区域C中。 5B。 [0111] 图 图6A到6B示出了当用户摇动移动终端时的示例 100 在上下方向 600 ,根据本发明的示例性实施例,沿上下方向排列的区域的排列发生变化。 [0112] 参考图。 如图 6A 和 6B 所示,如果在上下方向上往复运动 600 当显示配置有区域 A、B、C 和 D 的布局屏幕时,执行如图 10 所示。 图6A,上下方向排列的区域排列 600 如图所示的变化。 6B。 如果上下方向往复运动 600 执行,图的区域B和C。 图6A移动到图6的上部区域。 在图6B中,区域D对应于图6的下部区域。 图6A移动到图6的中心区域。 图6B的区域A,图6B的区域A。 图6A移动到图6的下部区域。 6B(即,到图6B的区域A)。 下面参照图1至图3描述区域的排列规则。 10 和 11。 [0113] 图 图7A和7B示出了当用户摇动移动终端时的示例 100 在对角线方向 700 ,根据本发明的示例性实施例,沿对角线方向排列的区域的排列发生变化。 [0114] 参考图。 如图 7A 和 7B 所示,如果沿对角线方向往复运动 700 当屏幕如图 3 所示时执行。 显示图7A的区域A,显示图7A的区域A。 图7A移动到图7的区域A。 图7B的区域D和图7B的区域D。 图7A移动到图7的区域D。 7B。 [0115] 图 图8A和8B示出了当用户摇动移动终端时的示例 100 ,除触摸区域外的其余区域的排列发生变化。 如图。 图8A示出了用于说明用户摇动移动终端的情况的画面示例 100 在对角线方向 805 在保持在区域A上的触摸的同时。在这种情况下,除了图1的区域A之外的其余区域B、C和D的布置可以保持在区域A上。 保持触摸的图8A的变化如图8A所示。 8B。 [0116] 如果用户晃动移动终端 100 同时保持对用户所需区域的触摸 800,只有触摸的区域是固定的。 类似地,如果用户在两个或多个区域上保持触摸,则对应的区域也是固定的。 例如,如果用户手持移动终端 100 用双手晃动移动终端可能会让用户感到困难或不舒服 100 在一个特定的方向。 在这种情况下,可以使用用户拉/推移动终端的动作来改变布局的配置 100 朝向/反对用户、倾斜运动等。 [0117] 上述示例性实施例如图1和2所示。 图5A到7B涉及布局的配置根据用户摇动移动终端的往复运动而改变的情况 100 左右方向、上下方向、对角线方向。 然而,也可以根据其他各种动作来改变布局的配置,例如拉/推移动终端的动作 100 水平,倾斜运动,旋转运动等。 图5A到8B涉及根据预定动作改变布局配置的方法。 然而,改变布局的配置的方法不限于以上参照图1至图3描述的方法。 5A到8B。 例如,可以使用呼吸来改变布局的配置。 [0118] 图 图9A至9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的过程的示例。 [0119] 参考图。 9A-9D,如果用户在一个方向吹他/她的呼吸 900 朝向显示由区域A、B、C和D组成的布局的屏幕,如图1所示。 在图9A中,如图9A所示,显示区域A、B、C和D响应用户的呼吸而吹散的屏幕,好像这些区域是从屏幕上吹出的纸一样。 9B。 依次如图所示。 如图9C所示,显示区域A、B、C和D的布置响应于用户的呼吸而改变的屏幕,并且如图9C所示。 参照图9D,显示具有改变了区域A、B、C和D的布置的布局的屏幕。 如上所述,图。 图9A至9D涉及考虑“吹纸”的应用示例,“吹纸”是各种呼吸行为中的一种简单、直接的行为。 图9A到9D示出了显示交互图像的情况,其中响应于用户的呼吸,区域被吹散,就好像纸吹掉了一样。因此,用户可以具有控制屏幕区域的体验,就好像用户实际上是在吹掉纸一样。 . 根据本发明的示例性实施例,屏幕的内容可以根据用户呼吸的强度而变化。 [0120] 根据本发明的另一示例性实施例,构成布局的区域可以通过检测预定手势(例如,好像翻页的手势)来改变。 这种姿势可以由相机传感器、环境光传感器等检测。 图 1 和 3 中所示的示例。 如上所述,图5A到9D涉及使用动作或呼吸重新配置布局的情况,然而,当相机传感器、环境光传感器等接收到与各种行为有关的输入时,也可以重新配置布局。 [0121] 如上所述,当用户摇动移动终端时 100 或者对着移动终端的屏幕呼吸 100 ,屏幕上显示的图像会根据移动终端的动作而变化 100 或用户的呼吸,使用户无需操作按钮即可轻松快速地排列对象,感受图像的生动变化。 [0122] 可以使用如下所述的排列规则重新排列布局的组件。 [0123] 图 图10A至图10D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0124]参考图。 参照图10A-10D,根据区域大小的排列规则是将显示在较大区域上的对象移动到较小区域并且将显示在较小区域上的对象移动到较大区域的方法。 如图。 图10A示出了其中区域A具有最大尺寸并且区域B和C具有小于区域A的尺寸的屏幕。如果移动终端的往复运动 100 例如,当画面如图1所示时,检测到上下方向的往复运动。 在显示图10A时,显示在具有大尺寸的区域A中的对象移动到具有小尺寸的区域A,如图10所示。 10B 步中 1000 ,并且显示在具有小尺寸的区域C中的对象移动到具有大尺寸的区域C,如图5所示。 10B 步中 1005 . 根据排列规则,每当移动终端有动作 100 当检测到如图 3 所示的屏幕时。 在显示图10A的情况下,布局的配置按照图10的顺序改变。 参照图10B至图10。 10D。 [0125] 图 图11A至11D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0126] 参考图。 如图11A-11D所示,在水平拍摄图像和垂直拍摄图像的情况下,优选水平拍摄图像位于水平区域,而垂直拍摄图像位于垂直区域。 如图。 图11A示出了区域A是水平区域并且区域B和C是垂直区域的示例。 在这种情况下,最好是水平物体 1100 分配到区域 A 并显示在区域 A 中,垂直对象 1102 和 1105 被分配到区域B和C并显示在区域B和C中。根据本发明的示例性实施例,关于对象具有水平格式或垂直格式的每个对象的属性是对象的唯一属性并且可以被识别 提前。 因此,控制器 110 考虑到对象的属性,将每个对象定位在与对象对应的区域。 当执行智能相册应用程序时,控制器 110 可以确定必须显示的对象的数量,从页面具有不同区域排列的多个布局中选择与对象的数量和对象的属性相对应的布局,并提供选择的布局。 [0127] 如果检测到运动时出现如图所示的画面。 在显示图11A的情况下,可以显示具有改变的区域布置的布局,如图11所示。 11B。 如果一个对象显示在图 C 的区域中。 11A是垂直物体 1105 , 垂直物体 1105 可以显示虽然垂直对象 1105 移动到图1的区域C。 11B。 垂直物体 1105 可以显示在图3的区域C中。 11B虽然零件 1110 垂直物体的 1105 被截断且未显示。 [0128] 随后,如果再次检测到运动,则如图3所示的布局。 图11B改变为具有如图11所示布置的布局。 11C。 即,由于显示在图2的区域B中的对象。 11B对应垂直物体 1105 显示在图 2 的区域 B 中。 如图11A所示,对象可以移动到图11的区域B并显示在区域B上。 11C。 然而,由于对象显示在图1的区域A中。 11B对应于水平物体 1100 显示在图 1 的区域 A 中。 如图11A所示,对象不能移动到图11的区域A并显示在区域A上。 11D。 当水平物体 1100 位于图A的区域A中。 11D,零件 1115 水平物体的 1100 被切断,同时在区域A中出现空白。这种具有比预定允许的比例失配程度更大的比例失配程度的区域优选在搬迁对象时排除。 因此,图1中所示的布局。 11D 不包括在可选择以更改布局的布局中。 因此,通过考虑每个对象的属性来改变布局,可以在屏幕的区域上适当地布置诸如肖像、风景等的组件,同时保持每个组件的比例。 [0129]如图。 图12是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 在下文中,将参考图10描述根据触摸对象的属性改变在构成布局的区域中显示的对象的方法。 然而,如图12所示,该方法不限于图12所示的示例。 12. [0130] 参考图。 1和12,在步骤 1200 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 移动终端的 100 . 在步骤 1205 , 控制器 110 确定至少一个区域是否已被输入设备触摸。 如果至少触摸了一个区域,则在步骤 1210 控制器 110 判断移动终端是否往复运动 100 被检测到。 如果移动终端的往复运动 100 被检测到,然后在步骤 1215 控制器 110 搜索与属于触摸区域的对象的属性相对应的对象。 如果在步骤中确定 1205 没有接触过任何区域,或者是否在步骤中确定 1210 没有检测到往复运动,则过程返回步骤 1200 并保持布局。 [0131] 在步骤 1220 , 控制器 110 将找到的对象排列在除显示触摸对象的区域之外的其余区域中,并在步骤 1225 , 控制器 110 显示重新配置的布局,其中包含排列找到的对象的区域。 如果没有检测到往复运动,则过程返回操作 1200 ,并且布局保持不变。 [0132] 在上述本发明的示例性实施例中,步骤 1215 搜索关联对象的步骤在步骤之后执行 1210 在保持触摸的同时检测往复运动; 然而,当至少一个区域被触摸时,也可能搜索与属于该区域的对象相关联的对象。 [0133] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的属性将不同对象分别显示在构成布局的区域上的处理的示例。 [0134] 参考图。 参照图13A和13B,除了基于位置布置对象的方法之外,还可以采用根据对象的属性布置关联对象的各种方法。 这样的方法包括基于人来布置对象的方法、基于社交网络来布置对象的方法等。 [0135] 在基于人的布置对象的方法的情况下,如果用户摇动移动终端 100 同时保持对移动终端屏幕上显示的图片上特定人的触摸 100 ,则与被触摸的人相关联的图片可以被重新排列以配置当前页面的布局。 显示多人图片时,允许用户在人群中只选择一个人,如果用户摇晃移动终端 100 在保持触摸特定人的同时,可以搜索与特定人相关联的图片并在各个重新排列的区域上显示。 在基于社交网络的排列对象的方法的情况下,例如,如果选择了facebook feed功能,则可以重新排列相应的Facebook feed以适合相应页面的布局区域。 [0136] 如图。 图13A示出了由地图区域和区域A、B和C组成的布局。如果用户触摸地图区域并摇动移动终端 100 同时保持对地图区域的触摸 1300 ,可以根据对象的属性搜索与属于地图区域的对象相关联的对象,并且可以将找到的对象排列并显示在各个区域上,如图3所示。 13B。 例如,如果用户摇动移动终端 100在地图区域按住“纽约时代广场”的同时,与“纽约时代广场”相关联的对象,例如在该地点拍摄的照片、该地点的相关新闻、该地点推荐的应用项目, 等可以布置在各个区域上,如图1所示。 13B。 [0137] 图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图。 图 图15A到15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例 [0138] 参考图。 参见图14A和14B以及图14A和14B。 参照图15A-15I,图15的过程。 图14B跟随图14的过程。 14A。 为了便于理解,将参照图1至图3描述调整区域数量的方法。 图15A至15I; 然而,该方法不限于图1和图2所示的示例。 15A至15I。 [0139] 在步骤 1400 , 控制器 110 显示由触摸屏上显示对象的区域组成的布局 190 . 在步骤 1405 , 控制器 110 判断是否接收到改变区域数量的请求。 用户可以通过按下诸如音量键之类的特定键或通过位于屏幕上部的操作栏上显示的选项功能来发送改变区域数量的请求。 如果收到更改区域数量的请求,则在步骤 1410 , 控制器 110 显示用于调整区域数量的图标。 如果没有收到更改区域数量的请求,则返回步骤 1400 . 在步骤 1415 , 控制器 110 确定是否触摸了任何一个图标。 [0140] 如果在操作中确定 1415 如果没有检测到触摸输入,则过程返回操作 1410 . 如果选择了用于添加区域的图标,则在步骤 1420 图。 14B、控制器 110 确定在触摸用于添加区域的图标时是否检测到往复运动。 如果检测到往复运动,则在运行中 1425 , 控制器 110 将构成下一页布局的区域添加到构成当前页面布局的区域中,并且在步骤 1440 , 控制器 110 显示重新配置的布局以包括添加的区域。 如果在触摸区域添加图标时重复检测到往复运动,控制器 110 每当检测到往复运动时,逐步添加区域。 [0141] 图 图15A至图15I示出了用于说明根据移动终端的动作调整构成布局的区域的数量以及改变区域的布置的过程的示例 100 ,根据本发明的示例性实施例。 如果接收到调整区域数量的请求,则在如图 10 所示的屏幕。 显示图15A,区域添加图标 1510 和一个区域移除图标 1510 如图所示显示。 15B。 如果用户晃动移动终端 100 同时保持触摸区域添加图标 1510 ,添加区域D,如图3所示。 在图15C中,A、B和C区域被重新排列。 如果用户晃动移动终端 100 再次,添加区域E,如图4所示。 15D,其余区域重新排列。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 保持15D。 因此,如果构成在页面上显示的布局的区域的数量增加,则将减少总页面数量,因为要显示的对象的数量已经设置。 [0142] 如果在步骤中未触摸区域添加图标 1430 , 控制器 110 确定在区域移除图标被触摸时是否检测到往复运动。 如果在触摸区域移除图标时检测到往复运动,则在操作中 1435 控制器 110从构成当前页面布局的区域中删除一个区域,并在操作中 1440 , 控制器 110 显示用剩余区域重新配置的布局。 如果在区域移除图标时反复检测到往复运动 1500 被触摸时,每当检测到往复运动时,区域就会逐步移除。 [0143] 如果用户晃动移动终端 100 同时保持触摸区域移除图标 1500 如图所示。 在图15F中,去除了D区域,如图15F所示。 15G,A、B、C区域重新排列。 当用户摇动移动终端时 100 同时保持触摸区域移除图标 1500 ,由于已经设置了最小区域数,因此区域数可能不会改变,如图3所示。 15H。 在这种情况下,区域的排列会发生变化。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 15I 保持不变。 因此,如果减少在页面上显示的构成布局的区域的数量,则页面的总数将增加以显示预定数量的对象。 [0144] 运行中 1430 ,如果在没有触摸区域添加/删除图标时检测到往复运动,则在操作中 1445 控制器 110 根据往复运动方向的方向改变构成布局的区域,如图1和2所示。 5至7,并在运行 1450 , 控制器 110 显示使用更改区域重新配置的布局。 [0145] 上述示例是使用图标增加或减少页面上显示的区域数量的情况; 然而,也可以采用其他方法,例如使用音量增大/减小键添加或删除区域的方法。 例如,一个区域可能是如果用户摇动移动终端 100 如果用户摇动移动终端,同时按住音量增大键并移除区域 100 按住音量减小键的同时。 [0146] 如图。 图16是用于说明在移动终端中调整构成布局的区域数的方法的流程图 100 ,根据本发明的示例性实施例。 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0147] 参考图。 16 和 17 一个- 17 C、自步骤 1600 和 1605 步骤相同 400 和 405 图。 在图4中,将省略其详细描述。 运行中 1610 ,确定往复运动的次数是否等于或大于预定次数。 如果往复运动的次数等于或大于预定次数,则在步骤 1615 包括在下一页的布局中的预定数量的区域被添加到构成当前页面的布局的区域中。 运行中 1620 , 控制器 110 显示重新配置的布局以包括添加的区域。 可以根据往复运动的次数确定添加的区域的数量。 [0148] 如图。 图17A示出了当前页面的布局由区域A、B、C和D构成的情况,而图17A示出了当前页面的布局配置有区域A、B、C和D的情况。 图17B示出了下一页面的布局由区域E、F、G、H和I配置的情况。当前页面是显示在触摸屏上的页面 190 , 下一页是轻弹或拖动触摸屏手势时将显示的页面 190从用户接收。 因此,如果在当前页面如图1所示时检测到一个或多个往复运动。 如图17A所示,下一页的区域E和F如图17所示。 如图17B所示,根据往复运动的次数将图17B的区域添加到当前页面的区域。 如图17C所示,同时,区域A、B和C根据往复运动的方向重新排列。 这些区域可以一个一个地添加,也可以以预定数量为单位添加。 当区域被添加到当前页面时,在下一页的区域E和F上显示的对象如图4所示。 如图17B所示,图17B移动到区域E和F并显示在区域E和F上。 17C。 [0149] 如上所述,根据本发明的示例性实施例,用户可以使用移动终端的动作以他/她的期望模式直观地布置布局的组件(即,区域/对象) 100 . 因此,根据本发明的示例性实施例,用户可以根据移动终端的动作容易且快速地将显示在移动终端的屏幕上的多个对象的排列改变为用户期望的图案。 此外,由于可以通过移动终端的简单动作的输入来改变布置对象的布局的配置,所以可以最大化用户的便利性。 [0150] 此外,由于可以通过考虑对象的属性来配置布局来提供由期望的对象组成的布局,因此可以提供具有统一顺序的个性化布局。 [0151] 本发明的示例性实施例可以以硬件、软件或硬件和软件的组合的形式来实现。 软件可以存储在易失性或非易失性存储设备中,例如 ROM,不管它是可擦除的还是可重写的,存储在诸如 RAM、存储芯片、 和集成电路 (IC),或在光/磁可记录和机器可读的存储介质中,例如压缩盘 (CD)、数字多功能盘 (DVD)、磁盘和磁带 . 可以包括在移动终端中的存储器是适用于存储一个或多个程序的非暂时性机器可读存储介质的示例,包括实现本发明示例性实施例的指令。 因此,本发明的示例性实施例包括包括用于实现如说明书的所附权利要求中所述的设备和方法的代码的程序,以及存储这些程序的机器可读存储介质。 [0152] 此外,移动终端可以从以有线/无线方式连接的程序提供装置接收和存储程序。 程序提供装置可以包括:存储器,用于存储程序,该程序包括用于执行根据移动终端的动作控制多个对象的显示的方法的指令;通信单元,用于与移动终端进行有线/无线通信; 控制器,用于根据移动终端的请求或自动向移动终端发送程序。 [0153] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:34.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20140245234A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), AU2014219558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), AU2014219558B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), BR112015020243A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), BR112015020243B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), CN104007892A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), CN104007892B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), CN110333758A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), EP2770424A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), EP2770424A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), EP2770424B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.468 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.469 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), EP3696653A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), EP3696653B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), IN2703MUMNP2015A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), IN407024B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), JP2016511471A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), JP2019083048A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), JP6816858B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), KR1020140105344A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.750 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.750 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.750 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), KR102146244B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), MX2015010598A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), MX353242B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.856 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), RU2015140072A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), RU2667496C2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), US10775896B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.961 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.961 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.961 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), US20140245234A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:35.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), US20190121443A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.032 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.032 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), VN10030622B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), VN44787A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), WO2014129862A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), ZA201505799A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271652(Integer), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20140245234A1(String), US20140245234A1(String), 1409155200(Integer), 271652(Integer), 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185963(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185963(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185963(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185963(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:36.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8898492B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: System, method and mobile terminal for sharing battery between mobile terminals(String), 移动终端间共享电池的系统、方法及移动终端(String), US8898492B2(String), A system, a method, and a mobile terminal for sharing a battery between mobile terminals are disclosed, which can solve a problem that the battery can not be shared between mobile terminals in the prior art. In accordance with the present invention, a mobile terminal having power supplying ability is able to supply power to a mobile terminal lacking power by an external power supply line, power control circuits of the power supply end and the power utilization end are controlled, the power utilization end is able to detect an electricity quantity of the power supply end, and the sharing of a battery between two mobile terminals can be achieved, thereby greatly increasing utilization modes of the battery without external charging power supply so as to facilitate the using of a user.(String), 本发明公开了一种移动终端间共享电池的系统、方法及移动终端,能够解决现有技术中移动终端间无法共享电池的问题。 根据本发明,具有供电能力的移动终端能够通过外接电源线向缺电的移动终端供电,控制供电端和用电端的电源控制电路,电源 利用端能够检测供电端的电量,可以实现两个移动终端共享电池,大大增加了电池在无需外接充电电源的情况下的使用方式,方便使用 用户。(String), US13/517866(String), 1339603200(Integer), US8898492B2(String), 1416844800(Integer), 1416844800(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 12(Integer), US20030030412A1 | US20050174710A1 | US20060017839A1 | US20080054855A1 | US20080074077A1 | US20080116854A1 | US20090167245A1 | US20090200989A1 | US20090267571A1 | US20100045243A1 | US20100109602A1 | US7508162B2(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185964(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\110ab9cb2a2442b99bc3b3ae321c4845.png(String), 185964(Integer), 110ab9cb2a2442b99bc3b3ae321c4845.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.374 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.374 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: System, method and mobile terminal for sharing battery between mobile terminals(String), 移动终端间共享电池的系统、方法及移动终端(String), US8898492B2(String), A system, a method, and a mobile terminal for sharing a battery between mobile terminals are disclosed, which can solve a problem that the battery can not be shared between mobile terminals in the prior art. In accordance with the present invention, a mobile terminal having power supplying ability is able to supply power to a mobile terminal lacking power by an external power supply line, power control circuits of the power supply end and the power utilization end are controlled, the power utilization end is able to detect an electricity quantity of the power supply end, and the sharing of a battery between two mobile terminals can be achieved, thereby greatly increasing utilization modes of the battery without external charging power supply so as to facilitate the using of a user.(String), 本发明公开了一种移动终端间共享电池的系统、方法及移动终端,能够解决现有技术中移动终端间无法共享电池的问题。 根据本发明,具有供电能力的移动终端能够通过外接电源线向缺电的移动终端供电,控制供电端和用电端的电源控制电路,电源 利用端能够检测供电端的电量,可以实现两个移动终端共享电池,大大增加了电池在无需外接充电电源的情况下的使用方式,方便使用 用户。(String), US13/517866(String), 1339603200(Integer), US8898492B2(String), 1416844800(Integer), 1416844800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 12(Integer), US20030030412A1 | US20050174710A1 | US20060017839A1 | US20080054855A1 | US20080074077A1 | US20080116854A1 | US20090167245A1 | US20090200989A1 | US20090267571A1 | US20100045243A1 | US20100109602A1 | US7508162B2(String), \20230420\110ab9cb2a2442b99bc3b3ae321c4845.png(String), 6(Integer), 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185964(Integer), 1. A system for sharing a battery between mobile terminals, comprising a mobile terminal of a power supply end and a mobile terminal of a power utilization end, wherein,the mobile terminal of the power supply end comprises a battery of the power supply end, a circuit interface of the power supply end and a power supply control unit of the power supply end, wherein the power supply control unit of the power supply end is coupled with the battery of the power supply end and the circuit interface of the power supply end respectively;the mobile terminal of the power utilization end comprises a battery of the power utilization end, a circuit interface of the power utilization end, a power supply control unit of the power utilization end and a power management unit, wherein the power management unit is coupled with the battery of the power utilization end and comprises a power supply switch subunit;wherein the circuit interface of the power utilization end is coupled with the circuit interface of the power supply end; the power supply control unit of the power supply end is configured to control the battery of the power supply end to supply power to the mobile terminal of the power utilization end through the circuit interface of the power supply end;the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; and the power supply control unit of the power utilization end is configured to supply power to the mobile terminal of the power utilization end;wherein the power management unit further comprises: a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series, and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal of the power utilization end further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein,the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end;the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the mobile terminal of the power supply end charges the battery of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; andthe electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of the battery of the power supply end.(String), 1、一种移动终端共享电池的系统,包括一种供电端移动终端和用电端移动终端,其中,供电端移动终端包括供电端电池、供电端电路接口和供电端供电控制单元,供电端供电控制单元耦接分别带有供电端的电池和供电端的电路接口;用电端移动终端包括用电端电池、用电端电路接口、用电端供电控制单元和电源管理单元,其中,电源管理单元耦接于电源利用端的电池,包括电源切换子单元;其中,用电端的电路接口与供电端的电路接口耦合;供电端供电控制单元用于控制供电端电池通过供电端电路接口为用电端移动终端供电。电源开关子单元,分别与用电端电路接口、用电端电池和用电端电源控制单元耦合,用于控制用电端电路接口或用电端电池与用电端电源控制单元耦合;用电端供电控制单元,用于为用电端移动终端供电;其中,电源管理单元还包括:依次串联耦合在用电端的电路接口与供电开关子单元之间的充电供电模式控制子单元和电量检测开关子单元,以及耦合的电量检测子单元。带电量检测开关子单元;用电端移动终端还包括与用电端电池耦合的用电端充电控制单元。其中,用电端充电控制单元,用于对用电端电池进行充电控制;充电供电模式控制子单元,与用电端充电控制单元耦合,用于控制供电端移动终端在供电端移动终端充电时是否对用电端电池进行充电。端为用电端的移动终端供电;和电量检测开关子单元,用于控制电量检测子单元检测用电端电池电量或供电端电池电量。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185964(Integer), 2. The system for sharing a battery between mobile terminals according to claim 1, wherein the mobile terminal of the power supply end further comprises:a charging control unit of the power supply end, coupled with the battery of the power supply end, configured to perform charging control to the battery of the power supply end; anda power supply interface control unit, coupled between the circuit interface of the power supply end and the power supply control unit of the power supply end in series and coupled with the charging control unit of the power supply end, configured to control the circuit interface of the power supply end to couple with the charging control unit of the power supply end or the power supply control unit of the power supply end.(String), 2.根据权利要求1所述的移动终端电池共享系统,其中供电端移动终端还包括:供电端充电控制单元,与供电端电池耦合,用于对供电端电池进行充电控制;和供电接口控制单元,串联耦合在供电端的电路接口与供电端的供电控制单元之间,并与供电端的充电控制单元耦合,用于控制供电端的电路接口供电端耦接供电端的充电控制单元或供电端的供电控制单元。3、一种移动终端共享电池的方法,包括步骤:供电端移动终端通过用电端电路接口向用电端移动终端供电;和用电端移动终端在用电端移动终端中开启用电端电池的供电电路,同时关闭用电端电路接口的供电电路,从而实现供电端移动终端向用电端移动终端供电;其中,用电端充电控制单元对用电端电池进行充电控制;充电及供电方式控制子单元,控制供电端移动终端向用电端移动终端供电时,供电端移动终端是否对用电端电池进行充电;和电量检测开关子单元控制电量检测子单元检测供电端电池的电量。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185964(Integer), 3. A method for sharing a battery between mobile terminals, comprising the steps of:a mobile terminal of a power supply end supplying power to a mobile terminal of a power utilization end through a circuit interface of the power utilization end; andthe mobile terminal of the power utilization end opening a power supply circuit of the battery of the power utilization end in the mobile terminal of the power utilization end and closing a power supply circuit of the circuit interface of the power utilization end at the same time, thus enabling the mobile terminal of the power supply end to supply power to the mobile terminal of the power utilization end;wherein a charging control unit of the power utilization end performing charging control to the battery of the power utilization end;a charging and power supply mode control subunit controlling whether the mobile terminal of the power supply end charges the battery of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; andan electricity quantity detection switch subunit controlling an electricity quantity detection subunit to detect an electricity quantity of the battery of the power supply end.(String), 4.根据权利要求3所述的移动终端电池共享方法,其中在供电端移动终端向用电端移动终端供电之前,该方法还包括以下步骤:用电端移动终端判断是否对用电端移动终端中的用电端电池进行充电,如果是,将用电端电路接口与充电电路耦合;如果否,断开用电端电路接口与充电电路的耦合。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185964(Integer), 4. The method for sharing a battery between mobile terminals according to claim 3, wherein before the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of:the mobile terminal of the power utilization end determining whether to charge the battery of the power utilization end in the mobile terminal of the power utilization end, if yes, coupling the circuit interface of the power utilization end with a charging circuit; if no, breaking a coupling between the circuit interface of the power utilization end and the charging circuit.(String), 5.根据权利要求3所述的移动终端共享电池的方法,其中在供电端移动终端向用电端移动终端供电过程中,该方法还包括以下步骤:用电端移动终端检测并显示供电端移动终端的供电端电池电量。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185964(Integer), 5. The method for sharing a battery between mobile terminals according to claim 3, wherein during the procedure that the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of:the mobile terminal of the power utilization end detecting and displaying an electricity quantity of the battery of the power supply end of the mobile terminal of the power supply end.(String), 6.移动终端,包括用电端电池、与用电端电池耦合的电源管理单元,其中电源管理单元包括电源开关子单元,移动终端还包括用电端电路接口和用电端供电控制单元;其中,电源利用端的电路接口,用于连接外部供电设备;电源开关子单元,分别与用电端电路接口、用电端电池和用电端电源控制单元耦合,用于控制用电端电路接口或用电端电池与用电端电源控制单元耦合;和用电端供电控制单元,用于为移动终端供电;其中,所述电源管理单元还包括依次串联耦合在用电端电路接口与供电开关子单元之间的充电供电模式控制子单元和电量检测开关子单元,以及与所述电源耦合的电量检测子单元。电量检测开关子单元;移动终端还包括与用电端电池耦合的用电端充电控制单元。其中,用电端充电控制单元,用于对用电端电池进行充电控制;充电供电方式控制子单元,与用电端充电控制单元耦合,用于在外部供电设备为移动设备供电时,控制外部供电设备是否对用电端电池进行充电。用电端终端;和电量检测开关子单元,用于控制电量检测子单元检测用电端电池电量或外部供电设备电池电量。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185964(Integer), 6. A mobile terminal, comprising a battery of a power utilization end, a power management unit coupled with the battery of the power utilization end, wherein the power management unit comprises a power supply switch subunit, and the mobile terminal further comprises a circuit interface of the power utilization end and a power supply control unit of the power utilization end; wherein,the circuit interface of the power utilization end is configured to couple with an external power supply device;the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; andthe power supply control unit of the power utilization end is configured to supply power to the mobile terminal;wherein the power management unit further comprises a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein,the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end;the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the external power supply device charges the battery of the power utilization end when the external power supply device supplies power to the mobile terminal of the power utilization end; andthe electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of a battery of the external power supply device.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185964(Integer), [0001]This is a continuation of International Application PCT/CN2010/073703, with an International Filing Date of Jun. 9, 2010, which claims priority to Chinese Application No. 200910260372.7, filed Dec. 17, 2009, each of which is incorporated by reference. FIELD OF THE INVENTION [0002]The present invention relates to the technical field of mobile terminal devices, and in particular to a system, a method and a mobile terminal for sharing a battery between mobile terminals. BACKGROUND OF THE INVENTION [0003]As a portable device, a mobile terminal is more frequently used than other portable devices and has become the most frequently used portable device of a user and a main carrier for the communication, information management and entertainment of the user. Due to the characteristics of a portable device, the mobile terminal, whose power supply is realized by means of a built-in battery, usually does not use an external power supply to supply power after being charged. Therefore, the continuous using time of the mobile terminal is completely determined by the electricity quantity of the battery in the device. With respect to a portable device, the using time of the battery is an important technical reference index. [0004]Currently, the power supply of the mobile terminal is basically based on the built-in rechargeable battery in the mobile terminal. Even for mobile terminals of the same type, their batteries are used independently. When one mobile terminal runs out of power, it is only possible to take out the battery of another mobile terminal and then replace the battery of the mobile terminal, which runs out of power, with the battery of the another mobile terminal, however, the another mobile terminal can not be used at the same time, causing inconvenience to the users. Therefore, in a working environment without charging fittings and with special requirements, the user desires to use the mobile terminals simultaneously when a mobile terminal runs out of power. SUMMARY OF THE INVENTION [0005]The present invention provides a system, a method and a mobile terminal for sharing a battery between mobile terminals, so as to address the problem that the battery can not be shared between mobile terminals in the prior art. [0006]To solve the technical problem above, in one aspect, a system for sharing a battery between mobile terminals is provided, which comprises a mobile terminal of a power supply end and a mobile terminal of a power utilization end; wherein, [0007]the mobile terminal of the power supply end comprises a battery of the power supply end, a circuit interface of the power supply end and a power supply control unit of the power supply end, wherein the power supply control unit of the power supply end is coupled with the battery of the power supply end and the circuit interface of the power supply end respectively; [0008]the mobile terminal of the power utilization end comprises a battery of the power utilization end, a circuit interface of the power utilization end, a power supply control unit of the power utilization end and a power management unit of the power utilization end, wherein the power management unit is coupled with the battery of the power utilization end and comprises a power supply switch subunit; [0009]wherein the circuit interface of the power utilization end is coupled with the circuit interface of the power supply end; the power supply control unit of the power supply end is configured to control the battery of the power supply end to supply power to the mobile terminal of the power utilization end through the circuit interface of the power supply end; [0010]the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; and the power supply control unit of the power utilization end is configured to supply power to the mobile terminal of the power utilization end. [0011]Preferably, the mobile terminal of the power supply end further comprises: [0012]a charging control unit of the power supply end, coupled with the battery of the power supply end, configured to perform charging control to the battery of the power supply end; and [0013]a power supply interface control unit, coupled between the circuit interface of the power supply end and the power supply control unit of the power supply end in series and coupled with the charging control unit of the power supply end, configured to control the circuit interface of the power supply end to couple with the charging control unit of the power supply end or the power supply control unit of the power supply end. [0014]Preferably, the power management unit further comprises: a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series, and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal of the power utilization end further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein, [0015]the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end; [0016]the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the mobile terminal of the power supply end charges the battery of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; and [0017]the electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of the battery of the power supply end. [0018]In another aspect, a method for sharing a battery between mobile terminals is provided, comprising: [0019]a mobile terminal of a power supply end supplying power to a mobile terminal of a power utilization end through a circuit interface of the power utilization end; and [0020]the mobile terminal of the power utilization end opening a power supply circuit of the battery of the power utilization end and closing a power supply circuit of the circuit interface of the power utilization end at the same time, thus enabling the mobile terminal of the power supply end to supply power to the mobile terminal of the power utilization end. [0021]Preferably, before the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of: [0022]the mobile terminal of the power utilization end determining whether to charge the battery of the power utilization end in the mobile terminal of the power utilization end, if yes, coupling the circuit interface of the power utilization end with a charging circuit; if no, breaking a coupling between the circuit interface of the power utilization end and the charging circuit. [0023]Preferably, during the procedure that the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the method further comprises the steps of: [0024]the mobile terminal of the power utilization end detecting and displaying an electricity quantity of the battery of the power supply end of the mobile terminal of the power supply end. [0025]In another aspect, a mobile terminal is provided, the mobile terminal comprises a battery of a power supply end, and the mobile terminal further comprises: [0026]a circuit interface of the power supply end; and [0027]a power supply control unit of the power supply end, coupled with the battery of the power supply end and the circuit interface of the power supply end respectively, configured to control the battery of the power supply end to supply power externally through the circuit interface of the power supply end. [0028]Preferably, the mobile terminal further comprises: [0029]a charging control unit of the power supply end, coupled with the battery of the power supply end, configured to perform charging control to the battery of the power supply end; and [0030]a power supply interface control unit, coupled between the circuit interface of the power supply end and the power supply control unit of the power supply end in series, and coupled with the charging control unit of the power supply end, configured to control the circuit interface of the power supply end to couple with the charging control unit of the power supply end or the power supply control unit of the power supply end. [0031]In another aspect, a mobile terminal is provided, comprising a battery of a power utilization end and a power management unit which is coupled with the battery of the power utilization end and comprises a power supply switch subunit, the mobile terminal further comprises a circuit interface of the power utilization end and a power supply control unit of the power utilization end; wherein, [0032]the circuit interface of the power utilization end is configured to couple with an external power supply device; [0033]the power supply switch subunit, coupled with the circuit interface of the power utilization end, the battery of the power utilization end and the power supply control unit of the power utilization end respectively, is configured to control the circuit interface of the power utilization end or the battery of the power utilization end to couple with the power supply control unit of the power utilization end; and [0034]the power supply control unit of the power utilization end is configured to supply power to the mobile terminal. [0035]Preferably, the power management unit further comprises a charging and power supply mode control subunit and an electricity quantity detection switch subunit sequentially coupled between the circuit interface of the power utilization end and the power supply switch subunit in series, and an electricity quantity detection subunit coupled with the electricity quantity detection switch subunit; the mobile terminal further comprises a charging control unit of the power utilization end coupled with the battery of the power utilization end; wherein, [0036]the charging control unit of the power utilization end is configured to perform charging control to the battery of the power utilization end; [0037]the charging and power supply mode control subunit, coupled with the charging control unit of the power utilization end, is configured to control whether the external power supply device charges the battery of the power utilization end when the external power supply device supplies power to the mobile terminal of the power utilization end; and [0038]the electricity quantity detection switch subunit is configured to control the electricity quantity detection subunit to detect an electricity quantity of the battery of the power utilization end or an electricity quantity of a battery of the external power supply device. [0039]In accordance with the present invention, a mobile terminal having power supplying ability is able to supply power to a mobile terminal lacking power by an external power supply line, power control circuits of the power supply end and the power utilization end are controlled, the power utilization end is able to detect an electricity quantity of the power supply end, and the sharing of a battery between two mobile terminals can be achieved, thereby greatly increasing utilization modes of the battery without external charging power supply so as to facilitate the utilization of a user. BRIEF DESCRIPTION OF THE DRAWINGS [0040]FIG. 1 is a schematic diagram of the structure of a mobile terminal of a power supply end in accordance with an embodiment of the present invention; [0041]FIG. 2 is a schematic diagram of the structure of a mobile terminal of a power utilization end in accordance with an embodiment of the present invention; [0042]FIG. 3 is a schematic diagram of the structure of another mobile terminal of a power supply end in accordance with an embodiment of the present invention; [0043]FIG. 4 is a schematic diagram of the structure of another mobile terminal of power utilization end in accordance with an embodiment of the present invention; [0044]FIG. 5 is a flowchart of a method for sharing a battery between mobile terminals in accordance with an embodiment of the present invention; [0045]FIG. 6 is a flowchart when a mobile terminal of a power supply end supplies power externally in accordance with an embodiment of the present invention; and [0046]FIG. 7 is a flowchart when a mobile terminal of a power utilization end receives power from external in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0047]To solve the problem that the battery can not be shared between mobile terminals in the prior art, a system, a method and a mobile terminal for sharing a battery between mobile terminals are provided in the present invention, which will be detailed hereinafter in conjunction with the accompanying figures and the embodiments. It shall be understood that the embodiments described herein are only to illustrate the present invention, rather than limit it. [0048]As shown in FIGS. 1 and 2, Embodiment 1 of the present invention relates to a system for sharing a battery between mobile terminals, comprising a mobile terminal of a power supply end and a mobile terminal of a power utilization end. The structure of the mobile terminal of the power supply end is as shown in FIG. 1, comprising a battery 103 of the power supply end, a circuit interface 101 of the power supply end and a power supply control unit 102 of the power supply end, wherein the power supply control unit 102 of the power supply end is coupled with the battery 103 of the power supply end and the circuit interface 101 of the power supply end respectively. The structure of the mobile terminal of the power utilization end is as shown in FIG. 2, comprising a battery 204 of the power utilization end, a circuit interface 201 of the power utilization end, a power supply control unit 203 of the power utilization end and a power management unit 202, wherein the power management unit 202 is coupled with the battery 204 of the power utilization end and comprises a power supply switch subunit 2021. [0049]The circuit interface 201 of the power utilization end is coupled with the circuit interface 101 of the power supply end; the power supply control unit 102 of the power supply end is configured to control the battery 103 of the power supply end to supply power to the mobile terminal of the power utilization end through the circuit interface 101 of the power supply end; [0050]the power supply switch subunit 2021, coupled with the circuit interface 201 of the power utilization end, the battery 204 of the power utilization end and the power supply control unit 203 of the power utilization end respectively, is configured to control the circuit interface 201 of the power utilization end or the battery 204 of the power utilization end to couple with the power supply control unit 203 of the power utilization end; and the power supply control unit 203 of the power utilization end is configured to supply power to the mobile terminal of the power utilization end. [0051]When the mobile terminal of the power supply end supplies power locally, namely when the mobile terminal of the power supply end does not enable its battery sharing function thereby not supplying power to the mobile terminal of the power utilization end, the battery 103 of the power supply end in the mobile terminal of the power supply end is coupled with the power supply control unit 102 of the power supply end, and supplies power locally through the power supply control unit 102 of the power supply end. When the mobile terminal of the power supply end enables its battery sharing function thereby supplying power to the mobile terminal of the power utilization end, the battery 103 of the power supply end, the power supply control unit 102 of the power supply end and the circuit interface 101 of the power supply end are coupled serially in sequence, at this time, the power supply control unit 102 of the power supply end realizes, on the premise of ensuring the local power supply to the mobile terminal of the power supply end, the function of supplying power to the mobile terminal of the power utilization end through the circuit interface 101 of the power supply end connected with the mobile terminal of the power utilization end. [0052]When the mobile terminal of the power utilization end supplies power through the battery 204 of the power utilization end, the power supply switch subunit 2021 of the power management unit 202 is coupled with the battery 204 of the power utilization end, thus enabling the power of the battery 204 of the power utilization end to supply power to the mobile terminal of the power utilization end locally through the power supply switch subunit 2021 and the power supply control unit 203 of the power utilization end coupled with the power supply switch subunit 2021. When the battery 204 of the power utilization end runs low or down, the circuit interface 101 of the power supply end is coupled with the circuit interface 201 of the power utilization end through a power supply line, so that the battery 103 of the power supply end in the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end. A power supply voltage no higher than a local voltage of the mobile terminal of the power supply end can be provided by controlling the output voltage of the circuit interface 101 of the power supply end through the power supply control unit 102 of the power supply end, thus supplying power to the mobile terminal of the power utilization end with a power supply voltage no higher than the above local voltage. At this time, the power supply switch subunit 2021 breaks its coupling with the battery 204 of the power utilization end and couples with the circuit interface 201 of the power utilization end, thus the power provided by the battery 103 of the power supply end is supplied to the power supply control unit 203 of the power utilization end through the circuit interface 101 of the power supply end, the circuit interface 201 of the power utilization end and the power supply switch subunit 2021. The power supply control unit 203 of the power utilization end adjusts the voltage and the electricity quantity according to parameters (such as voltage, current and electricity quantity) used by the mobile terminal of the power utilization end and finally supplies power to the mobile terminal of the power utilization end. The sharing of the battery 103 of the power supply end between the mobile terminals of the power supply end and the power utilization end is realized, and the purpose of using the two mobile terminals of the power supply end and the power utilization end simultaneously is reached. [0053]In addition, since most of the mobile terminals use rechargeable battery or require data transfer, a mobile terminal is usually provided with a charging interface or a data interface. Due to the requirements for the portability of a mobile terminal, they are limited in size and interface quantity. Moreover, considering that the charging interface or some data interfaces can be used as power supply interface, the additional use of the charging interface or data interfaces on the mobile terminal of the power supply end as the circuit interface 101 of the power supply end is designed in the embodiment. [0054]As shown in FIG. 3, on the basis of the embodiment above, the mobile terminal of the power supply end further comprises: a charging control unit 105 of the power supply end and a power supply interface control unit 104, wherein the charging control unit 105 of the power supply end is coupled with the battery 103 of the power supply end; the power supply interface control unit 104 is coupled serially between the circuit interface 101 of the power supply end and the power supply control unit 102 of the power supply end and is coupled with the charging control unit 105 of the power supply end. The charging control unit 105 of the power supply end is configured to perform charging control to the battery 103 of the power supply end; and the power supply interface control unit 104 is configured to control the circuit interface 101 of the power supply end to couple with the charging control unit 105 of the power supply end or the power supply control unit 102 of the power supply end. Namely, when the circuit interface 101 of the power supply end is used as a charging interface, the power supply interface control unit 104 controls the circuit interface 101 of the power supply end to couple with the charging control unit 105 of the power supply end, and breaks the coupling between the circuit interface 101 of the power supply end and the power supply control unit 102 of the power supply end. In this way, the battery 103 of the power supply end can be charged and can supply power locally through the power supply control unit 102 of the power supply end. [0055]When the circuit interface 101 of the power supply end is coupled with the power supply line, the user configures to enable the battery sharing function of the mobile terminal of the power supply end to supply power to the mobile terminal of the power utilization end. Namely, when the circuit interface 101 of the power supply end is used as the power supply interface, the power supply interface control unit 104 breaks the coupling between the circuit interface 101 of the power supply end and the charging control unit 105 of the power supply end, couples the circuit interface 101 of the power supply end with the power supply control unit 102 of the power supply end, reads configuration parameters such as voltage, and configures the power supply control unit 102 of the power supply end. Thus the battery 103 of the power supply end can supply power externally through the circuit interface 101 of the power supply end when simultaneously supplying power locally through the power supply control unit 102 of the power supply end. [0056]Moreover, when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, there may exist a case that the mobile terminal of the power utilization end cannot be coupled with the mobile terminal of the power supply end through the power supply line for a long period of time, so the user has the requirement of charging the mobile terminal of the power utilization end by the mobile terminal of the power supply end. In addition, when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the residual electricity quantity of the battery 103 of the power supply end is critical to the mobile terminal of the power supply end and the mobile terminal of the power utilization end, so it is necessary to detect the residual electricity quantity of the battery 103 of the power supply end, so as to remind the user to conduct corresponding operation. In view of the above, the mobile terminal of the power utilization end is further designed in the embodiment of the present invention. [0057]As shown in FIG. 4, on the basis of the embodiment above, the mobile terminal of the power utilization end also comprises a charging control unit 205 of the power utilization end coupled with the battery 204 of the power utilization end; the power management unit 202 also comprises a charging and power supply mode control subunit 2022, an electricity quantity detection switch subunit 2023 and an electricity quantity detection subunit 2024, wherein the charging and power supply mode control subunit 2022 and the electricity quantity detection switch subunit 2023 are coupled serially between the circuit interface 201 of the power utilization end and the power supply switch subunit 2021 in sequence, and the electricity quantity detection subunit 2024 is coupled with the electricity quantity detection switch subunit 2023. The charging control unit 205 of the power utilization end is configured to perform charging control to the battery 204 of the power utilization end; the charging and power supply mode control subunit 2022 is coupled with the charging control unit 204 of the power utilization end and is configured to control whether the mobile terminal of the power supply end charges the battery 204 of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end; and the electricity quantity detection switch subunit 2023 is configured to control the electricity quantity detection subunit 2024 to detect the electricity quantity of the battery 103 of the power supply end or the electricity quantity of the battery 204 of the power utilization end. [0058]After the circuit interface 201 of the power utilization end in the mobile terminal of the power utilization end is coupled with the power supply line, firstly, the mobile terminal of the power utilization end determines whether to charge the battery 204 of the power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, if the answer is yes, the charging and power supply mode control subunit 2022 controls the circuit interface 201 of the power utilization end to couple with the charging control unit 205 of the power utilization end so as to charge the battery 204 of the power utilization end through the charging control unit 205 of the power utilization end, and simultaneously keeps the coupling between the circuit interface 201 of the power utilization end and the power supply switch subunit 2021 so as to supply power to the mobile terminal of the power utilization end; if the answer is no, the charging and power supply mode control subunit 2022 breaks the coupling between the circuit interface 201 of the power utilization end and the charging control unit 205 of the power utilization end, and only keeps the coupling between the circuit interface 201 of the power utilization end and the power supply switch subunit 2021 so as to supply power to the mobile terminal of the power utilization end. [0059]When the mobile terminal of the power utilization end is supplied with power through the battery 204 of the power utilization end, the electricity quantity detection switch subunit 2023 controls the electricity quantity detection subunit 2024 to detect an end voltage of the battery 204 of the power utilization end and a voltage attenuation, estimate a capacity of the battery 103 of the power supply end, write the estimated capacity in a PMU status register for the access of an UI (User Interface), and display the current electricity quantity. During the procedure that the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, the electricity quantity detection switch subunit 2023 controls the electricity quantity detection subunit 2024 to detect the end voltage of the battery 103 of the power supply end and the voltage attenuation, estimate the capacity of the battery 103 of the power supply end, write the estimated capacity in the PMU status register for the access of the UI, and display the current electricity quantity. [0060]It can be seen from the embodiment above that, through supplying power to the mobile terminal of the power utilization end by the mobile terminal of the power supply end, the embodiment of the present invention achieves sharing the battery of the power supply end between the mobile terminals of the power supply end and the power utilization end, reduces the hardware added by the additional use of the interfaces, simplifies the structure and realizes the function of charging to the battery of the power utilization end, thus facilitating using of a user. [0061]As shown in FIG. 5, Embodiment 2 of the present invention relates to a method for sharing a battery between mobile terminals, comprising the steps as follows. [0062]S301, a mobile terminal of a power supply end supplies power to a mobile terminal of a power utilization end through a circuit interface of the power utilization end. [0063]As shown in FIG. 6, if a charging interface of the mobile terminal of the power supply end is additionally used as the circuit interface of the power supply end in the mobile terminal of the power supply end, the step above comprises the steps as follows. [0064]S3011, after the mobile terminal of the power supply end is coupled with the mobile terminal of the power utilization end through a power supply line, a power supply mode is enabled. [0065]S3012, since the circuit interface of the power supply end is used as a charging interface when the mobile terminal of the power supply end does not supply power externally, the circuit interface of the power supply end is coupled with a charging circuit, namely the circuit interface of the power supply end is coupled with the charging control unit of the power supply end so as to charge the battery of the power supply end through the charging control unit of the power supply end. When the mobile terminal of the power supply end supplies power externally, the circuit interface of the power supply end is not used as a charging interface any more, thus it is required to break the coupling between the circuit interface of the power supply end and the charging circuit. [0066]S3013, since a rated operational voltage in normal operation may vary with different mobile terminals, it is required to determine whether to configure a voltage reduction parameter before supplying power to the mobile terminal of the power utilization end, if the answer is yes, turn to S3014, otherwise, turn to S3015. [0067]S3014, the voltage reduction parameter is configured according to parameters such as rated operational voltage and rated operational current of the mobile terminal of the power utilization end, and then turn to S3016. [0068]S3015, the current voltage parameter of the battery of the power supply end is used, and turn to S3016. [0069]S3016, the circuit interface of the power supply end is coupled with a discharge circuit of the battery of the power supply end, namely the circuit interface of the power supply end is coupled with the battery of the power supply end through the power supply control unit of the power supply end. [0070]S3017, the power supply control unit of the power supply end supplies power, through the circuit interface of the power supply end, to the mobile terminal of the power utilization end connected with it when locally supplying power to the mobile terminal of the power supply end at the same time. [0071]S302, the mobile terminal of the power utilization end opens a power supply circuit of the battery of the power utilization end and closes a power supply circuit of the circuit interface of the power utilization end. [0072]As shown in FIG. 7, in the case that the mobile terminal of the power supply end is also required to charge the battery of the power utilization end when supplying power to the mobile terminal of the power utilization end, S302 specifically comprises the steps as follows. [0073]S3021, power supply of the mobile terminal of the power supply end enters to supply power to the mobile terminal of the power utilization end. [0074]S3022, firstly, it is determined whether it is required to charge the battery of the power utilization end in the mobile terminal of power utilization end when the mobile terminal of the power supply end supplies power to the mobile terminal of the power utilization end, if it is required to do so, keep the coupling between the circuit interface of the power utilization end and the charging circuit, namely keep the coupling between the circuit interface of the power utilization end and the charging control unit of the power utilization end, then turn to S3024; if it is not required to do so, turn to (String), [0001] 这是国际申请 PCT/CN2010/073703 的延续,国际申请日为 2010 年 6 月 9 日,该申请要求于 2009 年 12 月 17 日提交的中国申请号 200910260372.7 的优先权,该申请均通过引用并入本文。 发明领域 [0002] 本发明涉及移动终端设备技术领域,尤其涉及一种移动终端间共享电池的系统、方法及移动终端。 背景技术 [0003] 移动终端作为便携设备,使用频率高于其他便携设备,已成为用户最频繁使用的便携设备,也是用户进行通信、信息管理和娱乐的主要载体。 由于便携设备的特性,通过内置电池实现供电的移动终端在充电后通常不使用外接电源供电。 因此,移动终端的持续使用时间完全取决于设备中电池的电量。 对于便携设备而言,电池的使用时间是一项重要的技术参考指标。 [0004] 目前,移动终端的供电基本都是基于移动终端内置的可充电电池。 即使是同类型的移动终端,其电池也是独立使用的。 当一个移动终端没电时,只能取出另一个移动终端的电池,然后用另一个移动终端的电池更换没电的移动终端的电池。 不能同时使用其他移动终端,给用户带来不便。 因此,在没有充电配件且有特殊要求的工作环境中,用户希望在移动终端没电的情况下同时使用移动终端。 发明内容 [0005] 本发明提供一种移动终端间共享电池的系统、方法及移动终端,以解决现有技术中移动终端间无法共享电池的问题。 [0006] 为解决上述技术问题,一方面,提供了一种移动终端间共享电池的系统,包括供电端移动终端和用电端移动终端。 其中, [0007] 供电端的移动终端包括供电端的电池、供电端的电路接口和供电端的供电控制单元,其中供电端的供电控制单元耦接 分别与供电端的电池和供电端的电路接口; [0008] 用电端的移动终端包括用电端的电池、用电端的电路接口、用电端的供电控制单元和用电端的电源管理单元,其中电源 管理单元与用电端的电池耦合,包括电源开关子单元; [0009] 其中,用电端的电路接口与供电端的电路接口耦接。 供电端的供电控制单元,用于控制供电端的电池通过供电端的电路接口向用电端的移动终端供电。 [0010] 电源开关子单元,分别与用电端的电路接口、用电端的电池和用电端的电源控制单元耦合,用于控制用电端的电路接口或 用电端的电池与用电端的供电控制单元耦合; 所述用电端的供电控制单元,用于为所述用电端的移动终端供电。 [0011]优选地,所述供电端的移动终端还包括: [0012] 所述供电端的充电控制单元,与所述供电端的电池相连,用于对所述供电端的电池进行充电控制; 和 [0013] 电源接口控制单元,串联在电源端的电路接口和电源端的电源控制单元之间,并与电源端的充电控制单元耦合,用于控制电源端的电路接口。 供电端耦接供电端的充电控制单元或供电端的供电控制单元。 [0014] 优选地,所述电源管理单元还包括:充电供电模式控制子单元和电量检测开关子单元,依次串联在所述用电端的电路接口和所述电源开关子单元之间,以及电量检测子单元。 与电量检测开关子单元连接; 所述用电端的移动终端还包括:所述用电端的充电控制单元,与所述用电端的电池相连。 其中, [0015] 用电端的充电控制单元,用于对用电端的电池进行充电控制。 [0016] 充电和供电模式控制子单元,与用电端的充电控制单元耦合,用于控制供电端的移动终端在供电端的移动终端是否对用电端的电池进行充电。 端向用电端的移动终端供电; 和 [0017] 电量检测开关子单元,用于控制电量检测子单元检测用电端电池电量或供电端电池电量。 [0018] 另一方面,提供了一种移动终端之间共享电池的方法,包括: [0019] 供电端的移动终端通过用电端的电路接口向用电端的移动终端供电; 和 [0020] 用电端的移动终端打开用电端电池的供电电路,同时关闭用电端电路接口的供电电路,从而使供电的移动终端 端向用电端的移动终端供电。 [0021] 优选地,在供电端的移动终端向用电端的移动终端供电之前,该方法还包括以下步骤: [0022] 用电端的移动终端在用电端的移动终端中判断是否对用电端的电池进行充电,如果是,则将用电端的电路接口与充电电路耦合。 如果否,则断开用电端的电路接口与充电电路之间的耦合。 [0023] 优选地,在供电端的移动终端向用电端的移动终端供电的过程中,该方法还包括以下步骤: [0024] 用电端的移动终端检测并显示供电端的移动终端的供电端的电池电量。 [0025] 另一方面,提供了一种移动终端,所述移动终端包括供电端的电池,所述移动终端还包括: [0026] 电源端电路接口; 和 [0027]供电端的供电控制单元,分别与供电端的电池和供电端的电路接口耦接,用于通过电路接口控制供电端的电池对外供电。 电源端。 [0028] 优选地,所述移动终端还包括: [0029] 所述供电端的充电控制单元,与所述供电端的电池相连,用于对所述供电端的电池进行充电控制; 和 [0030] 电源接口控制单元,串联在电源端的电路接口和电源端的电源控制单元之间,并与电源端的充电控制单元耦合,用于控制电路接口 供电端与供电端的充电控制单元或供电端的供电控制单元耦接。 [0031] 另一方面,提供了一种移动终端,包括用电端的电池和与用电端的电池耦合的电源管理单元,所述电源管理单元包括电源开关子单元,所述移动终端还包括电路接口。 用电端的结构和用电端的供电控制单元; 其中, [0032] 用电端的电路接口,用于与外部供电装置耦合; [0033] 电源开关子单元,分别与用电端的电路接口、用电端的电池和用电端的电源控制单元耦合,用于控制用电端的电路接口或 用电端的电池与用电端的供电控制单元耦合; 和 [0034] 用电端的供电控制单元,用于为移动终端供电。 [0035] 优选地,电源管理单元还包括依次串联在用电端的电路接口和供电开关子单元之间的充电供电模式控制子单元和电量检测开关子单元,以及电量检测子单元。 带有电量检测开关子单元; 所述移动终端还包括所述用电端的充电控制单元,与所述用电端的电池相连。 其中, [0036] 用电端的充电控制单元,用于对用电端的电池进行充电控制。 [0037] 充电和供电模式控制子单元,与用电端的充电控制单元耦合,用于控制外部供电设备在给移动设备供电时,是否对用电端的电池进行充电。 用电端终端; 和 [0038] 电量检测开关子单元,用于控制电量检测子单元检测用电端的电池电量或外部供电设备的电池电量。 [0039] 根据本发明,具有供电能力的移动终端能够通过外接电源线向缺电的移动终端供电,控制供电端和用电端的电源控制电路,电源 利用端能够检测供电端的电量,可以实现两个移动终端共享一个电池,大大增加了电池在无需外接充电电源的情况下的利用方式,方便用户利用 用户。 附图的简要说明 [0040] 图1是根据本发明实施例的供电端移动终端的结构示意图; [0041]图2是根据本发明实施例的用电端的移动终端的结构示意图; [0042] 图3为本发明实施例提供的另一种供电端移动终端的结构示意图。 [0043] 图4为本发明实施例提供的另一种用电端移动终端的结构示意图。 [0044] 图5为本发明实施例提供的移动终端间共享电池的方法流程图。 [0045] 图6为本发明实施例供电端移动终端对外供电时的流程图。 和 [0046] 图7是根据本发明实施例的用电端的移动终端从外部接收电力时的流程图。 具体实施方式 [0047] 为解决现有技术中无法在移动终端间共享电池的问题,本发明提供了一种移动终端间共享电池的系统、方法及移动终端,下面将结合以下内容进行详细说明。 附图和实施例。 应当理解,此处所描述的实施例仅用于说明本发明,并不用于限制本发明。 [0048] 如图1和图2所示,本发明实施例一涉及一种移动终端间共享电池的系统,包括供电端移动终端和用电端移动终端。 供电端移动终端结构如图1所示,包括电池 103 电源端,电路接口 101 供电端和供电控制单元 102 所述的供电端,其中所述供电控制单元 102 电源端与电池耦合 103 电源端与电路接口 101 电源端分别。 用电端的移动终端结构如图2所示,包括电池 204 用电端,电路接口 201 用电端,电源控制单元 203 用电端和电源管理单元 202 ,其中电源管理单元 202 与电池耦合 204 用电端,包括电源开关子单元 2021 . [0049] 电路接口 201 用电端与电路接口耦合 101 电源端; 电源控制单元 102 电源端用于控制电池 103 供电端通过电路接口向用电端的移动终端供电 101 电源端; [0050] 电源开关子单元 2021 ,加上电路接口 201 用电端,电池 204 用电端和供电控制单元 203 用电端分别用于控制电路接口 201 用电端或电池 204 用电端与电源控制单元耦合 203 用电端; 和电源控制单元 203 用电端的移动终端,用于向用电端的移动终端供电。 [0051] 当供电端的移动终端在本地供电时,即供电端的移动终端没有开启电池共享功能从而不给用电端的移动终端供电时,电池 103 供电端在移动终端中的供电端与供电控制单元耦合 102供电端,通过供电控制单元就地供电 102 的电源端。 当供电端的移动终端开启电池共享功能从而为用电端的移动终端供电时,电池 103 电源端,电源控制单元 102 电源端与电路接口 101 电源端依次串联耦合,此时电源控制单元 102 供电端在保证供电端移动终端本地供电的前提下,通过电路接口实现向用电端移动终端供电的功能 101 供电端与用电端的移动终端相连。 [0052] 当用电端的移动终端通过电池供电时 204 用电端,供电开关子单元 2021 电源管理单元 202 与电池耦合 204 用电端,从而使电池的电源 204 用电端通过供电开关子单元对用电端的移动终端本地供电 2021 和电源控制单元 203 与电源开关子单元耦合的用电端的 2021 . 当电池 204 用电端低电平或停机,电路接口 101 电源端与电路接口耦合 201 用电端通过供电线,使电池 103 供电端移动终端中的供电端向用电端移动终端供电。 通过控制电路接口的输出电压,可以提供不高于供电端移动终端本地电压的供电电压 101 电源端通过电源控制单元 102 ,从而以不高于上述本地电压的电源电压向用电端的移动终端供电。 此时,电源开关子单元 2021 断开与电池的耦合 204 用电端与电路接口耦合 201 用电端,即电池提供的电量 103 供电端向供电控制单元供电 203 用电端通过电路接口 101 电源端,电路接口 201 用电端和供电开关子单元 2021 . 电源控制单元 203 用电端的移动终端根据用电端移动终端使用的电压、电流、电量等参数调整电压和电量,最终向用电端移动终端供电。 电池共享 103 实现了供电端和用电端的移动终端之间的供电端的连接,达到同时使用供电端和用电端两个移动终端的目的。 [0053] 另外,由于大多数移动终端使用充电电池或需要数据传输,因此移动终端通常设置有充电接口或数据接口。 由于移动终端便携性的要求,它们在尺寸和接口数量上受到限制。 另外,考虑到充电接口或者部分数据接口可以作为供电接口,额外使用供电端移动终端上的充电接口或者数据接口作为电路接口 101 本实施例中设计了电源端。 [0054] 如图3所示,在上述实施例的基础上,供电端的移动终端还包括:充电控制单元 105供电端和供电接口控制单元 104 ,其中充电控制单元 105 电源端与电池耦合 103 电源端; 电源接口控制单元 104 在电路接口之间串联耦合 101 电源端和电源控制单元的 102 电源端,与充电控制单元耦合 105 的电源端。 充电控制单元 105 供电端,用于对电池进行充电控制 103 电源端; 和电源接口控制单元 104 被配置为控制电路接口 101 电源端与充电控制单元耦合 105 供电端或供电控制单元 102 的电源端。 即当电路接口 101 供电端作为充电接口,供电接口控制单元 104 控制电路接口 101 电源端与充电控制单元耦合 105 电源端,并断开电路接口之间的耦合 101 电源端和电源控制单元的 102 的电源端。 这样,电池 103 供电端可充电,可通过供电控制单元就地供电 102 的电源端。 [0055] 当电路接口 101 供电端与供电线耦合,用户配置开启供电端移动终端的电池共享功能,为用电端移动终端供电。 即当电路接口 101 供电端作为供电接口,供电接口控制单元 104 打破了电路接口之间的耦合 101 供电端与充电控制单元 105 电源端,耦合电路接口 101 带电源控制单元的电源端 102 电源端,读取电压等配置参数,配置电源控制单元 102 的电源端。 因此电池 103 电源端可通过电路接口对外供电 101 通过供电控制单元本地同时供电时供电端的 102 的电源端。 [0056] 并且,供电端的移动终端在向用电端的移动终端供电时,可能存在用电端的移动终端无法通过以下方式与供电端的移动终端耦合的情况。 供电线路较长时间,因此用户有通过供电端的移动终端给用电端的移动终端充电的需求。 另外,供电端的移动终端向用电端的移动终端供电时,电池的剩余电量 103 供电端的移动端对供电端的移动终端和用电端的移动终端来说都是至关重要的,所以需要检测电池的剩余电量 103 以提醒用户进行相应的操作。 综上所述,本发明实施例进一步设计了用电端的移动终端。 [0057] 如图4所示,在上述实施例的基础上,用电端的移动终端还包括充电控制单元 205 用电端与电池耦合 204 用电端; 电源管理单元 202 还包括充电和供电模式控制子单元 2022 、电量检测开关子单元 2023 电量检测子单元 2024,其中充电和供电模式控制子单元 2022 电量检测开关子单元 2023 在电路接口之间串联耦合 201 用电端和供电开关子单元 2021 依次,电量检测子单元 2024 与电量检测开关子单元耦合 2023 . 充电控制单元 205 用电端,用于对电池进行充电控制 204 用电端; 充电和供电方式控制子单元 2022 与充电控制单元耦合 204 供电端的移动终端,用于控制供电端的移动终端是否对电池进行充电 204 供电端的移动终端向用电端的移动终端供电时,用电端的供电; 电量检测开关子单元 2023 用于控制电量检测子单元 2024 检测电池电量 103 电源端或电池电量 204 用电端。 [0058] 后电路接口 201 用电端的移动终端中的用电端与供电线耦合,首先,用电端的移动终端判断是否给电池充电 204 供电端的移动终端向用电端的移动终端供电时,供电端的移动终端向供电端的移动终端供电时,若为是,则充电及供电模式控制子单元 2022 控制电路接口 201 用电端与充电控制单元耦合 205 用电端对电池充电 204 用电端通过充电控制单元 205 用电端,同时保持电路接口之间的耦合 201 用电端和供电开关子单元 2021 为用电端的移动终端供电; 否,充电和供电模式控制子单元 2022 打破了电路接口之间的耦合 201 用电端和充电控制单元 205 用电端,只保持电路接口之间的耦合 201 用电端和供电开关子单元 2021 为用电端的移动终端供电。 [0059] 当用电端的移动终端通过电池供电时 204 用电端,电量检测开关子单元 2023 控制电量检测子单元 2024 检测电池的端电压 204 用电端和电压衰减,估算电池容量 103 供电端,将预估容量写入PMU状态寄存器,供UI(User Interface)访问,并显示当前电量。 在供电端移动终端向用电端移动终端供电过程中,电量检测切换子单元 2023 控制电量检测子单元 2024 检测电池的端电压 103 电源端和电压衰减,估算电池容量 103 供电端,将预估容量写入PMU状态寄存器供UI访问,显示当前电量。 [0060]由上述实施例可知,本发明实施例通过供电端的移动终端向用电端的移动终端供电,实现了移动端之间共享供电端的电池。 供电端和用电端的端子,减少了额外使用接口所增加的硬件,简化了结构,实现了对用电端电池充电的功能,方便用户使用。 [0061] 如图5所示,本发明实施例二涉及一种移动终端间共享电池的方法,包括以下步骤。 [0062] 小号 301 供电端的移动终端通过用电端的电路接口向用电端的移动终端供电。 [0063] 如图6所示,如果供电端移动终端的充电接口额外作为供电端移动终端中的供电端电路接口,则上述步骤包括如下步骤。 [0064] 小号 3011 ,供电端的移动终端通过供电线与用电端的移动终端耦合后,开启供电模式。 [0065] 小号 3012 ,由于供电端的电路接口在供电端的移动终端不对外供电时作为充电接口,所以供电端的电路接口与充电电路耦合,即电路接口 供电端的充电控制单元耦接供电端的充电控制单元,以通过供电端的充电控制单元对供电端的电池进行充电。 供电端的移动终端对外供电时,供电端的电路接口不再作为充电接口,因此需要断开供电端的电路接口与充电端之间的耦合。 充电电路。 [0066] 小号 3013 ,由于正常工作时的额定工作电压可能因不同的移动终端而异,需要在给用电端的移动终端供电前确定是否配置降压参数,如果是,则转S 3014 , 否则转 S 3015 . [0067] 小号 3014 ,根据用电端移动终端的额定工作电压、额定工作电流等参数配置降压参数,然后转S 3016 . [0068] 小号 3015 ,使用供电端电池的当前电压参数,转S 3016 . [0069] 小号 3016 ,电源端的电路接口与电源端电池的放电电路耦合,即电源端的电路接口通过电源控制单元与电源端的电池耦合。 电源端。 [0070] 小号 3017 ,供电端的供电控制单元在本地向供电端的移动终端供电时,通过供电端的电路接口向与其连接的用电端的移动终端供电。 同时。 [0071] 小号 302 ,用电端的移动终端打开用电端电池的供电电路,关闭用电端电路接口的供电电路。 [0072] 如图7所示,在供电端的移动终端在给用电端的移动终端供电时,还需要给用电端的电池充电的情况下,S 302 具体包括如下步骤。 [0073] 小号 3021 ,供电端的移动终端的电源进入为用电端的移动终端供电。 [0074] 小号 3022,首先判断供电端的移动终端向用电端的移动终端供电时,是否需要在用电端的移动终端对用电端的电池进行充电,如果是 需要这样做,保持用电端的电路接口和充电电路的耦合,即保持用电端的电路接口和用电端的充电控制单元的耦合,然后转向 小号 3024 ; 如果不需要,请转到 S 3023 . [0075] 小号 3023 ,用电端的电路接口与用电端的电池的耦合断开,即用电端的电路接口与用电端的充电控制单元的耦合断开,然后 转向S 3024 . [0076] 小号 3024 ,判断用电端的移动终端是否开启电池共享功能,即判断用电端的移动终端是否有外接电源输入,如果用电端的移动终端有外接电源 电源输入,表示开启电池共享功能,转S 3025 ; 如果用电端的移动终端没有外接电源输入,则表示电池共享功能关闭,转S 3026 . [0077] 小号 3025 ,用电端移动终端在供电端移动终端检测供电端电池端电压及电压衰减,估计供电端电池容量,写入估计 在 PMU 状态寄存器的容量为 U 的访问 1 ,最后显示当前电量。 [0078] 小号 3026 ,用电端电池的供电电路断开(即用电端电池与PMU供电开关子单元的耦合断开),同时, 用电端的电路接口闭合(即将用电端的电路接口与供电开关子单元耦合)。 [0079] 小号 3027 ,结束,即完成供电端的移动终端向用电端的移动终端供电的电路。 [0080] 小号 303 ,供电端的移动终端向用电端的移动终端供电。 [0081] 以USB(Universal Serial Bus)作为供电端和用电端的电路接口为例,详细说明本实施例的方案。 [0082] 目前,移动终端一般都带有USB接口,用于数据传输和充电。 标准USB接口提供5V电压和0.5A输出电流,具有4根数据线和2根电源线的有效引线,其中电源线分别耦合到PMU管脚上,用于充电和供电。 供电端移动终端的USB接口作为供电电路接口。 该移动终端之间共享电池的方法包括以下步骤。 [0083] 1、USB接口附加作为供电端移动终端的供电电路接口。 [0084]增加USB接口控制开关,控制与USB接口耦合的供电端电池的充电电路(电源管理单元,PMU)和放电电路。 用户可以配置控制开关来控制USB接口与充电电路或放电电路耦合。 如果移动终端的电池提供4.2V的输出电压,USB接口在与放电电路耦合的情况下,可以提供4.2V的输出电压。 如果电源IC串联耦合,通过控制电源IC可以控制接口提供不高于4.2V的输出电压。 或者可以串联一个二极管以提供降低到固定值的电压输出。 [0085] 2、用电端移动终端的USB接口与用电端移动终端的PMU耦合。 PMU可以通过编程控制用电端电池的充电电路和供电电路的闭合或断开,切换供电和充电模式。 PMU还可以控制输入电压的范围,将输入电压降低到用电端移动终端的允许电压范围内,从而为用电端移动终端提供一致的电流供电。 例如,如果用电端的移动终端的供电电压为3.9V,则供电电路将通过降压提供3.9V的电压输出。 充电电路是指对用电端电池充电所涉及的电路; 供电端是指为用电端的移动终端供电所涉及的电路。 [0086] 3、通过将用电端的移动终端配置为电池共享模式,PMU将电量检测切换到进入的供电线路,以检测供电端电池的电压衰减情况,估算出供电端的容量。 电源端的电池,并将估计容量写入PMU的状态寄存器,用于UI的访问和当前电量的显示。 [0087] 由以上描述可知,通过该方法,可以在增加少量硬件的情况下,额外使用现有接口,降低成本,实现电池共享,特别是在没有可用充电配件的情况下,可以丰富使用 移动终端之间的电池模式。 并且,通过对用电端移动终端的控制,可以灵活配置供电电压,保证用电端移动终端的安全使用。 用电端移动终端可以通过检测输入电压来模拟供电端移动终端的电池容量,以方便用户使用。 用电端移动终端可以通过配置在供电模式和充电/供电模式之间切换,可以有效利用供电端移动终端的电池容量,方便用户使用。 [0088] 尽管出于示例性目的公开了本发明的优选实施例,但是本领域技术人员应当意识到各种改进、添加和替换是可能的。 因此,本发明的范围不应限于上述实施例。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101728859A(String), CN101728859B(String), EP2515416A1(String), EP2515416A4(String), EP2515416B1(String), US20120266001A1(String), US8898492B2(String), WO2010148950A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101728859A(String), CN101728859B(String), EP2515416A1(String), EP2515416A4(String), EP2515416B1(String), US20120266001A1(String), US8898492B2(String), WO2010148950A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101728859A(String), CN101728859B(String), EP2515416A1(String), EP2515416A4(String), EP2515416B1(String), US20120266001A1(String), US8898492B2(String), WO2010148950A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), CN101728859A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271271(Integer), CN101728859B(String), 1048429(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), EP2515416A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.961 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), EP2515416A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:37.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), EP2515416B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), US20120266001A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), US8898492B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271271(Integer), WO2010148950A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.135 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101728859B(String), CN101728859B(String), 1355846400(Integer), 271271(Integer), 185555(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), SHA, JINCHUAN(String), ZHONG, SHENG(String), 中兴通讯股份有限公司(String), SHA JINCHUAN(String), ZHONG SHENG(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185964(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185964(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHA, JINCHUAN(String), SHA JINCHUAN(String), 0(Integer), 1681976078(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: ZHONG, SHENG(String), ZHONG SHENG(String), 0(Integer), 1681976078(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185964(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75836(Integer), 2(Integer), 185964(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75837(Integer), 2(Integer), 185964(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75836(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:38.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8099108B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminals including display screens capable of displaying maps and map display methods for mobile terminals(String), 包括能够显示地图的显示屏的移动终端和用于移动终端的地图显示方法(String), US8099108B2(String), A mobile terminal includes a communication module, a display screen, and control circuitry. The circuitry is configured to estimate a current geographic position of the mobile terminal, and to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. The circuitry is further configured to retrieve additional geographic map information including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information.(String), 一种移动终端,包括通信模块、显示屏和控制电路。 该电路被配置为估计移动终端的当前地理位置,并确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内。 该电路还被配置为如果移动终端的当前位置不在所存储的地理地图信息的边界内,则使用通信模块检索包括移动终端的当前位置的附加地理地图信息。(String), US11/776805(String), 1184169600(Integer), US8099108B2(String), 1326729600(Integer), 1326729600(Integer), 美国(String), 4(Integer), 6(Integer), 17(Integer), DE19537255A1 | JP1996145699A | JP1996286602A | JP1998013961A | JP1998105053A | JP2001117554A | JP2002213990A | JP2002312801A | US20020087263A1 | US20020116121A1 | US20030201912A1 | US20040193371A1 | US20050195221A1 | US20060122768A1 | US20070124065A1 | US20080243375A1 | US20080288166A1(String), 19(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185965(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\cef196f6a75a4f56a189d9640f92ffa9.png(String), 185965(Integer), cef196f6a75a4f56a189d9640f92ffa9.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminals including display screens capable of displaying maps and map display methods for mobile terminals(String), 包括能够显示地图的显示屏的移动终端和用于移动终端的地图显示方法(String), US8099108B2(String), A mobile terminal includes a communication module, a display screen, and control circuitry. The circuitry is configured to estimate a current geographic position of the mobile terminal, and to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. The circuitry is further configured to retrieve additional geographic map information including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information.(String), 一种移动终端,包括通信模块、显示屏和控制电路。 该电路被配置为估计移动终端的当前地理位置,并确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内。 该电路还被配置为如果移动终端的当前位置不在所存储的地理地图信息的边界内,则使用通信模块检索包括移动终端的当前位置的附加地理地图信息。(String), US11/776805(String), 1184169600(Integer), US8099108B2(String), 1326729600(Integer), 1326729600(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 17(Integer), DE19537255A1 | JP1996145699A | JP1996286602A | JP1998013961A | JP1998105053A | JP2001117554A | JP2002213990A | JP2002312801A | US20020087263A1 | US20020116121A1 | US20030201912A1 | US20040193371A1 | US20050195221A1 | US20060122768A1 | US20070124065A1 | US20080243375A1 | US20080288166A1(String), \20230420\cef196f6a75a4f56a189d9640f92ffa9.png(String), 19(Integer), 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 1. A method comprising:estimating a current geographic position of a mobile terminal including a communication module and a display screen;determining if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, the geographic map information defining geographic features within a first geographic area;in response to determining that the estimated current position of the mobile terminal is within the boundary of the stored geographic map information, displaying the map including the current position of the mobile terminal on the display;in response to determining that the estimated current position of the mobile terminal is not within the boundary of the stored geographic map information, providing additional geographic map information to the mobile terminal using the communication module, the additional geographic map information defining geographic features within a second geographic area that includes the estimated current position of the mobile terminal; anddetermining a current scale for the display screen to display a map by estimating a current speed of the mobile terminal and automatically selecting a display scale in response to the current speed of the mobile terminal, wherein selecting the display scale comprises selecting a relatively larger scale if the speed of the mobile terminal is higher and selecting a smaller scale if the speed of the mobile terminal is smaller.(String), 1.一种方法包括:估计包括通信模块和显示屏的移动终端的当前地理位置;确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内,该地理地图信息定义第一地理区域内的地理特征;响应于确定移动终端的估计当前位置在存储的地理地图信息的边界内,将包括移动终端当前位置的地图显示在显示器上;响应于确定移动终端的估计当前位置不在所存储的地理地图信息的边界内,使用通信模块向移动终端提供额外的地理地图信息,该额外的地理地图信息定义第二内的地理特征包括移动终端的估计当前位置的地理区域;和通过估计移动终端的当前速度确定显示屏显示地图的当前比例尺,并根据移动终端的当前速度自动选择显示比例尺,其中,选择显示比例尺包括选择相对较大的比例尺,如果移动端的速度越小,移动端的速度越高,选择越小的尺度。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 2. The method of claim 1, further comprising:determining a current scale for the map;determining if the stored map information contains enough map information to fill the display screen at the current scale;in response to determining that the stored map information does not contain enough map information to fill the display screen at the current scale, reducing the scale of the display screen until the stored map information is sufficient to fill the display screen at the reduced scale.(String), 2.如权利要求1所述的方法,还包括:确定地图的当前比例;确定存储的地图信息是否包含足够的地图信息以填满当前比例尺的显示屏幕;响应于确定存储的地图信息不包含足够的地图信息来以当前比例填充显示屏幕,减小显示屏幕的比例直到存储的地图信息足以以缩小的比例填充显示屏幕。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 3. The method of claim 2, further comprising retrieving additional map information using the communication module sufficient to fill the display screen at the current scale, and after the additional map information has been retrieved, increasing the scale to the current scale.(String), 3.如权利要求2所述的方法,还包括使用足以以当前比例填满显示屏幕的通信模块检索额外的地图信息,并且在已经检索到额外的地图信息之后,将比例增加到当前比例。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 4. The method of claim 1, further comprising estimating a current speed and direction of travel of the mobile terminal and estimating, in response to the current speed and direction of travel of the mobile terminal, when the mobile terminal will leave an area described by the stored map information.(String), 4.如权利要求1所述的方法,还包括估计移动终端当前的行进速度和方向,并根据移动终端当前的行进速度和方向,估计移动终端将离开存储的地图信息描述的区域的时间。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 5. The method of claim 4, further comprising:estimating an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and downloading the additional map information before the mobile terminal leaves the area described by the stored map information.(String), 5.如权利要求4所述的方法,还包括:估计为移动终端正前往的地理区域下载附加地图信息所需的时间量,并且在移动终端离开存储的地图信息所描述的区域之前下载附加地图信息。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 6. The method of claim 1, wherein estimating the current position of the mobile terminal is performed by a remote server in response to network-generated location information.(String), 6.如权利要求1所述的方法,其中估计移动终端的当前位置由远程服务器响应于网络生成的位置信息来执行。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 7. The method of claim 6, further comprising transmitting additional map information to the mobile terminal from the remote server if the current position of the mobile terminal is not within the boundary of the stored geographic map information.(String), 7.如权利要求6所述的方法,还包括如果移动终端的当前位置不在存储的地理地图信息的边界内,则从远程服务器向移动终端发送附加地图信息。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 8. The method of claim 1, wherein displaying the map including the current position of the mobile terminal on the display comprises displaying the map including the current position of the mobile terminal on the display after a predetermined period of nonuse of the mobile terminal.(String), 8.如权利要求1所述的方法,其中在显示器上显示包括移动终端的当前位置的地图包括在移动终端未使用预定时间段之后在显示器上显示包括移动终端的当前位置的地图。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 9. The method of claim 8, wherein the mobile terminal further comprises a secondary display screen on a flip portion that is movable between an open position and a closed position so that the secondary display screen is visible when the flip portion is in the closed position, the method comprising displaying the map including the current position of the mobile terminal on the secondary display when the flip portion is in the closed position.(String), 9.如权利要求8所述的方法,其中移动终端还包括在翻盖部分上的副显示屏,该副显示屏可在打开位置和闭合位置之间移动,使得副显示屏在翻盖部分处于闭合位置时可见,该方法包括显示地图,该地图包括当翻盖部分处于关闭位置时移动终端在辅助显示器上的当前位置。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 10. The method of claim 1, further comprising:determining that the mobile terminal has entered an idle mode; andreducing a brightness of the display and/or turning the display off;wherein estimating the current geographic position of the mobile terminal and determining if the estimated current position of the mobile terminal is within the boundary of geographic map information stored in the mobile terminal are performed while the mobile terminal is in the idle mode.(String), 10.如权利要求1所述的方法,还包括:确定移动终端进入空闲模式;和降低显示器的亮度和/或关闭显示器;其中,估计移动终端的当前地理位置以及判断估计的移动终端的当前位置是否在移动终端存储的地理地图信息的边界内是在移动终端处于空闲模式时执行的。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 11. The method of claim 10, wherein providing additional geographic map information to the mobile terminal using the communication module is performed while the mobile terminal is in the idle mode.(String), 11.如权利要求10所述的方法,其中当移动终端处于空闲模式时执行使用通信模块向移动终端提供附加地理地图信息。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 12. A mobile terminal, comprising:a communication module;a display screen; andcircuitry configured to estimate a current geographic position of the mobile terminal; to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, the geographic map information defining geographic features within a first geographic area; to display the map including the current position of the mobile terminal on the display in response to determining that the estimated current position of the mobile terminal is within the boundary of the stored geographic map information; and to retrieve additional geographic map information using the communication module in response to determining that the estimated current position of the mobile terminal is not within the boundary of the stored geographic map information, the additional geographic map information defining geographic features within a second geographic area that includes the estimated current position of the mobile terminal;wherein the circuitry is further configured to determine a current scale for the map on the display screen by estimating a current speed of the mobile terminal and to automatically select a display scale in response to the current speed of the mobile terminal.(String), 12.移动终端,包括:通信模块;显示屏;和被配置为估计移动终端的当前地理位置的电路​​;确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内,该地理地图信息定义第一地理区域内的地理特征;响应于确定移动终端的估计当前位置在存储的地理地图信息的边界内,在显示器上显示包括移动终端当前位置的地图;响应于确定移动终端的估计当前位置不在存储的地理地图信息的边界内,使用通信模块检索附加地理地图信息,附加地理地图信息定义第二地理区域内的地理特征包括移动终端的估计当前位置;其中,该电路还被配置为通过估计移动终端的当前速度来确定显示屏上地图的当前比例尺,并响应于移动终端的当前速度自动选择显示比例尺。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 13. The mobile terminal of claim 12, wherein the circuitry is further configured to determine a current scale for the map; to determine if the stored map information contains enough map information to fill the display screen at the current scale; and to reduce the scale of the display screen until the stored map information is sufficient to fill the display screen at the reduced scale in response to determining that the stored map information does not contain enough map information to fill the display screen at the current scale.(String), 13.如权利要求12所述的移动终端,其中该电路还被配置为确定地图的当前比例;判断存储的地图信息是否包含足够的地图信息以填满当前比例尺的显示屏幕;响应于确定存储的地图信息不包含足够的地图信息来以当前比例填满显示屏幕,减小显示屏幕的比例直到存储的地图信息足以以缩小的比例填满显示屏幕。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 14. The mobile terminal of claim 13, wherein the circuitry is further configured to retrieve additional map information using the communication module, and to increase the scale to an increased scale that is larger than the reduced scale after the additional map information has been retrieved.(String), 14.如权利要求13所述的移动终端,其中该电路还被配置为使用通信模块检索附加地图信息,并且在检索到附加地图信息之后将比例尺增加到大于缩小比例尺的增加比例尺。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 15. The mobile terminal of claim 12, wherein the circuitry is further configured to estimate a current speed and direction of travel of the mobile terminal, and, in response to the current speed and direction of travel of the mobile terminal, to estimate when the mobile terminal will leave an area described by the stored map information.(String), 15.如权利要求12所述的移动终端,其中该电路还被配置为估计移动终端的当前行进速度和方向,并且响应于移动终端的当前行进速度和方向,估计移动终端何时将离开存储的描述的区域地图信息。(String), 1(Integer), 14(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 16. The mobile terminal of claim 15, wherein the circuitry is further configured toestimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to download the additional map information before the mobile terminal leaves the area described by the stored map information.(String), 16.如权利要求15所述的移动终端,其中该电路还被配置为估计为移动终端正前往的地理区域下载附加地图信息以及在移动终端离开由存储的地图信息描述的区域之前下载附加地图信息所需的时间量。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 17. A map server, comprising:a communication module configured to communicate with a remotely located mobile terminal;a position/velocity determination unit configured to estimate position/velocity information for the mobile terminal;a database storing map information; andcircuitry configured to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, the geographic map information defining geographic features within a first geographic area; and to send additional geographic map information from the database using the communication module in response to determining that the estimated current position of the mobile terminal is not within the boundary of the stored geographic map information, the additional geographic map information defining geographic features within a second geographic area that includes the estimated current position of the mobile terminal;wherein the circuitry is further configured to determine a current scale for a map on a display screen of the mobile terminal by estimating a current speed of the mobile terminal and to automatically select a display scale for the map in response to the current speed of the mobile terminal.(String), 17.地图服务器,包括:通信模块,用于与远程移动终端进行通信;位置/速度确定单元,用于估计移动终端的位置/速度信息;储存地图信息的数据库;和被配置为确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内的电路,该地理地图信息定义第一地理区域内的地理特征;响应于确定移动终端的估计的当前位置不在存储的地理地图信息的边界内,使用通信模块从数据库发送附加的地理地图信息,附加的地理地图信息定义了第二个内的地理特征包括移动终端的估计当前位置的地理区域;其中,该电路还被配置为通过估计移动终端的当前速度来确定移动终端显示屏上地图的当前比例尺,并响应于移动终端的当前速度自动选择地图的显示比例尺终端。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 18. The map server of claim 17, wherein the position/velocity determination unit is configured to estimate the current position of the mobile terminal using location information provided by a communication network in which the mobile terminal is registered.(String), 18.如权利要求17所述的地图服务器,其中位置/速度确定单元被配置为使用由移动终端在其中注册的通信网络提供的位置信息来估计移动终端的当前位置。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185965(Integer), 19. The map server of claim 17, wherein the circuitry is further configured to estimate when the mobile terminal will leave an area described by the map information stored at the mobile terminal using the position/velocity of the mobile terminal, to estimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to transmit the additional map information to the mobile terminal before the mobile terminal leaves the area described by the map information stored at the mobile terminal.(String), 19.如权利要求17所述的地图服务器,其中电路还被配置为使用移动终端的位置/速度来估计移动终端何时将离开存储在移动终端处的地图信息所描述的区域,以估计下载地理的附加地图信息所需的时间量移动终端正前往的区域,并且在移动终端离开存储在移动终端处的地图信息所描述的区域之前将附加地图信息发送到移动终端。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185965(Integer), FIELD OF THE INVENTION [0001]The present invention relates to wireless communication terminals, and more particularly, to wireless communication terminals including display screens capable of displaying map information. BACKGROUND [0002]Wireless communication terminals are primarily used for obtaining access to wireless telephone services through a cellular telephone network. However, as the capabilities of wireless communication terminals increase, an additional level of user functionality is being included in the hardware and/or software of such terminals. For example, a communication terminal may be provided with a still and/or video camera, allowing pictures and/or videos to be taken by a user and transmitted from the mobile terminal to others. Likewise, many communication terminals include personal digital assistant (PDA) type applications suitable for tracking and managing schedules, tasks and the like. Many communication terminals also include messaging capability, such as electronic mail (e-mail), short message service (SMS) and multimedia message service (MMS) capabilities. Communication terminals may also be capable of connecting to the internet by using internet protocol (IP) over wireless and/or wired networks. [0003]Communication terminals are also increasingly being provided with the capability of determining the physical location of the terminal. For example, many communication terminals include global positioning system (GPS) receivers that permit the terminals to determine their location with a high degree of precision. Other systems for determining the location of a communication terminal have been implemented, including systems that obtain location information from a cellular communications network, and systems that obtain location information through inertial guidance techniques. [0004]In addition, some wireless networks have the ability to determine an approximate location of a terminal that is registered to the system. Such location information can be used, for example, to provide location information to emergency operators when a terminal is used to call for emergency help. SUMMARY [0005]Methods according to some embodiments of the invention include estimating a current geographic position of a mobile terminal including a communication module and a display screen, and determining if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. If the current position of the mobile terminal is within the boundary of the stored geographic map information, the map including the current position of the mobile terminal is displayed on the display. If the current position of the mobile terminal is not within the boundary of the stored geographic map information, additional geographic map information including the current position of the mobile terminal is provided to the mobile terminal using the communication module. [0006]The methods may further include determining a current scale for the map, and determining if the stored map information contains enough map information to fill the display screen at the current scale. If the stored map information does not contain enough map information to fill the display screen at the current scale, the scale of the display screen can be reduced until the stored map information is sufficient to fill the display screen at the reduced scale. [0007]The methods may further include retrieving additional map information using the communication module sufficient to fill the display screen at the current scale, and after the additional map information has been retrieved, increasing the scale to the current scale. [0008]The methods may further include determining a current scale for the display screen by estimating a current speed of the mobile terminal and selecting a display scale in response to the current speed of the mobile terminal. Determining the current scale may include selecting a relatively larger scale if the speed of the mobile terminal is higher and selecting a smaller scale if the speed of the mobile terminal is smaller. [0009]The methods may further include estimating a current speed and direction of travel of the mobile terminal and estimating, in response to the current speed and direction of travel of the mobile terminal, when the mobile terminal will leave an area described by the stored map information. [0010]The methods may further include estimating an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and downloading the additional map information before the mobile terminal leaves the area described by the stored map information. [0011]Estimating the current position of the mobile terminal may be performed by a remote server in response to network-generated location information. The methods may further include transmitting additional map information to the mobile terminal from the remote server if the current position of the mobile terminal is not within the boundary of the stored geographic map information. [0012]Displaying the map including the current position of the mobile terminal on the display may include displaying the map on the display after a predetermined period of nonuse of the mobile terminal. [0013]The mobile terminal may further include a secondary display screen on a flip portion of the device that is movable between an open position and a closed position so that the secondary display screen is visible when the flip portion is in the closed position. The methods may include displaying the map including the current position of the mobile terminal on the secondary display when the flip portion is in the closed position. [0014]The methods may further include determining that the mobile terminal has entered an idle mode, and reducing a brightness of the display and/or turning the display off. Estimating the current geographic position of the mobile terminal and determining if the estimated current position of the mobile terminal is within the boundary of geographic map information stored in the mobile terminal may be performed while the mobile terminal is in the idle mode. Furthermore, providing additional geographic map information to the mobile terminal using the communication module may be performed while the mobile terminal is in the idle mode. [0015]A mobile terminal according to some embodiments of the invention includes a communication module, a display screen, and control circuitry. The circuitry is configured to estimate a current geographic position of the mobile terminal, and to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal. The circuitry is further configured to display the map including the current position of the mobile terminal on the display if the current position of the mobile terminal is within the boundary of the stored geographic map information, and to retrieve additional geographic map information including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information. [0016]The circuitry may be further configured to determine a current scale for the map, to determine if the stored map information contains enough map information to fill the display screen at the current scale, and to reduce the scale of the display screen until the stored map information is sufficient to fill the display screen at the reduced scale if the stored map information does not contain enough map information to fill the display screen at the current scale. [0017]The circuitry may be further configured to retrieve additional map information using the communication module, and to increase the scale to an increased scale that is larger than the reduced scale after the additional map information has been retrieved. [0018]The circuitry may be further configured to determine a current scale for the display screen by estimating a current speed of the mobile terminal and to select a display scale in response to the current speed of the mobile terminal. [0019]The circuitry may be further configured to estimate a current speed and direction of travel of the mobile terminal, and, in response to the current speed and direction of travel of the mobile terminal, to estimate when the mobile terminal will leave an area described by the stored map information. The circuitry may be further configured to estimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to download the additional map information before the mobile terminal leaves the area described by the stored map information. [0020]A map server according to some embodiments of the invention includes a communication module configured to communicate with a remotely located mobile terminal, a position/velocity determination unit configured to estimate position/velocity information for the mobile terminal, a database storing map information, and a circuitry configured to determine if the estimated current position of the mobile terminal is within a boundary of geographic map information stored in the mobile terminal, and to send additional geographic map information from the database including the current position of the mobile terminal using the communication module if the current position of the mobile terminal is not within the boundary of the stored geographic map information. [0021]The position/velocity determination unit may be configured to estimate the current position of the mobile terminal using location information provided by a communication network in which the mobile terminal is registered. [0022]The circuitry may be further configured to estimate when the mobile terminal will leave an area described by the map information stored at the mobile terminal using the position/velocity of the mobile terminal, to estimate an amount of time needed to download additional map information for a geographic area that the mobile terminal is heading toward, and to transmit the additional map information to the mobile terminal before the mobile terminal leaves the area described by the map information stored at the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0023]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate certain embodiment(s) of the invention. In the drawings: [0024]FIG. 1 illustrates an electronic device according to some embodiments of the invention. [0025]FIGS. 2A-2B illustrate a flip-type mobile telephone according to some embodiments of the invention. [0026]FIG. 3 is a schematic block diagram illustrating an electronic device and a cellular communication system in accordance with some embodiments of the present invention. [0027]FIGS. 4A and 4B are a schematic block diagrams illustrating some aspects of an electronic device in accordance with some embodiments of the present invention. [0028]FIG. 5 is a schematic block diagram illustrating a map server in accordance with some embodiments of the present invention. [0029]FIGS. 6A, 6B, 7A, 7B and 7C are exemplary illustrations of display screens configured according to some embodiments of the invention. [0030]FIGS. 8-11 are flow diagrams illustrating operations of electronic devices according to some embodiments of the invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION [0031]The present invention now will be described more fully with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein the term “comprising” or “comprises” is open-ended, and includes one or more stated elements, steps and/or functions without precluding one or more unstated elements, steps and/or functions. As used herein the term “and/or” includes any and all combinations of one or more of the associated listed items. [0032]Embodiments according to the present invention are described with reference to block diagrams and/or operational illustrations of methods and communication terminals. It is to be understood that each block of the block diagrams and/or operational illustrations, and combinations of blocks in the block diagrams and/or operational illustrations, can be implemented by radio frequency, analog and/or digital hardware, and/or program instructions. These program instructions may be provided to a controller, which may include one or more general purpose processors, special purpose processors, ASICs, and/or other programmable data processing apparatus, such that the instructions, which execute via the controller and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or operational block or blocks. In some implementations, the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. [0033]As used herein, a “communication terminal” (or simply a “terminal”) includes, but is not limited to, a device that is configured to receive/transmit communication signals via a wireline connection, such as via a public-switched telephone network (PSTN), digital subscriber line (DSL), digital cable, a direct cable connection, and/or another data connection/network, and/or via a wireless interface with, for example, a cellular network, a wireless local area network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM/FM broadcast transmitter, and/or another communication terminal. A communication terminal that is configured to communicate over a wireless interface may be referred to as a “wireless communication terminal,” a “wireless terminal” and/or a “mobile terminal.” Examples of mobile terminals include, but are not limited to, a satellite or cellular radiotelephone; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and a conventional laptop and/or palmtop receiver or other appliance that includes a radiotelephone transceiver. [0034]Wireless communication between electronic devices may be accomplished using a wide variety of communication media, communication systems and communication standards. For example, mobile terminals such as wireless mobile telephones are typically configured to communicate via analog and/or digital wireless radio frequency (RF) telephone systems. Such devices may additionally be configured to communicate using wired and/or wireless local area networks (LANs), short range communication channels, such as Bluetooth RF communication channels and/or infrared communication channels, and/or long range communication systems, such as satellite communication systems. [0035]Mobile terminals, such as wireless mobile telephones, according to embodiments of the invention can have a variety of shapes, sizes and housing types. Examples of several types of mobile telephone housings are shown in FIGS. 1 to 2B. For example, a mobile terminal 100A according to some embodiments is illustrated in FIG. 1. The mobile terminal 100A includes a housing 15 that houses and protects the electronics of the mobile terminal 100A. The mobile terminal 100A includes an LCD display 18 and a keypad 16. The mobile terminal 100A further includes a multifunction control/input button 22 that can be used to select menu items and/or to input commands to the mobile terminal 100A. [0036]The mobile terminal 100A includes a microphone port 14 and an earphone/speaker 20. The housing 15 may be designed to form an acoustic seal to the user's ear when the earphone/speaker 20 is placed against the user's head. The mobile terminal 100A may be configured to play video files and or audio files, such as song files, which may be stereophonic signals. [0037]A flip-style mobile terminal 100B is illustrated in FIGS. 2A and 2B. The flip-style mobile terminal 100B is shown in the open position in FIG. 2A and the closed position in FIG. 2B. The mobile terminal 100B includes a housing 15 that includes a lower housing 15A and an upper housing, or “flip” portion 15B that are rotatably connected by means of a hinge 24. The mobile terminal 100B includes a primary LCD display 18 on the inside of the flip 15B and a keypad 16 on the inside of the lower housing 15A. The mobile terminal 100B further includes a multifunction control/input button 22. [0038]The mobile terminal 100A includes a microphone port 14 on the lower housing 15A and an earphone/speaker 20 on the inside of the flip 15B. As shown in FIG. 2B, a secondary display 28 and a camera lens 30 may be located on the outside of the flip 15B. [0039]FIG. 3 is a schematic block diagram of a wireless communication system 10 that includes a mobile terminal 100 that is configured to communicate with a map server 200A, 200B. For example, the mobile terminal 100 can communicate with the map server 200A over a direct wireless communication interface 106, over another wireless communication interface 108 through one or more cellular base stations 110a-b, and/or over another wireless communication interface 112 through a wireless local area network (WLAN) access point 114. The direct wireless communication interface 106 may include an RF wireless communication interface such as a Bluetooth interface or an infrared communication interface, such as, for example, the infrared communication interface defined by the Infrared Data Association (IRDA) protocols. The IRDA defines a number of standards for infrared wireless data communication, including standards for infrared wireless communication at data rates up to 16 Mb/s. It will be appreciated that the mobile terminal 100 may be a handheld wireless communication terminal, such as a mobile telephone, PDA, or the like. [0040]As further illustrated in FIG. 3, the mobile terminal 100 can include a user interface 122, a controller 126, a communication module 128, and a memory 125. [0041]The communication module 128 is configured to communicate data over one or more of the wireless interfaces 106, 108, and/or 112 to another remote terminal or other communication device, such as the map server 200A, 200B. The memory 125 is configured to store programs and or data for use by the controller 126. The memory 125 may include a nonvolatile memory that is capable of storing digital information even when power to the mobile terminal 100 is switched off. [0042]The communication module 128 can include, for example, a cellular communication module, a Bluetooth module, an infrared communication module, and/or a WLAN module. With a cellular communication module, the mobile terminal 100 can communicate via the base stations 110a-b using one or more cellular communication protocols such as, for example, Advanced Mobile Phone Service (AMPS), ANSI-136, Global Standard for Mobile (GSM) communication, General Packet Radio Service (GPRS), enhanced data rates for GSM evolution (EDGE), code division multiple access (CDMA), wideband-CDMA, CDMA2000, and Universal Mobile Telecommunications System (UMTS). The cellular base stations 110a-b may be connected to a Mobile Telephone Switching Office (MTSO) 116, which, in turn, may be connected to one or more other networks 118 (e.g. the Internet, a public switched telephone network, and/or another network). With a Bluetooth or infrared module, the mobile terminal 100 can communicate via an ad-hoc network using the direct interface 106. With a WLAN module, the mobile terminal 100 can communicate through the WLAN router 114 using a communication protocol that may include, but is not limited to, 802.11a, 802.11b, 802.11e, 802.11g, and/or 802.11i. A mobile telephone may also be configured to communicate directly over the networks 118. [0043]The mobile terminal 100 may be configured to transmit and/or receive a digital data signal to/from another communication terminal that may be communicatively coupled thereto through, for example the MTSO 116, and/or another network 118, such as a public switched telephone network (PSTN). However, it will be appreciated from the foregoing description that data communication between the mobile terminal 100 and another terminal may be accomplished without using the MTSO 116 or the other networks 118. [0044]The mobile terminal 100 my additionally include an AM/FM radio tuner, a UHF/VHF tuner, a satellite radio tuner, a DVB-H receiver, and/or another receiver configured to receive a broadcast audio/video signal and/or data signal. [0045]The map server 200A can be a standalone server that is configured to communicate with the mobile terminal 100 over wireless communication links, such as the WLAN communication link 112, a direct wireless communication link 106, and/or another wireless communication interface 108 through one or more cellular base stations 110a-b. For example, the map server 200A could be configured to broadcast a data signal including map information over the wireless communication link 106 to mobile terminals, such as mobile terminal 100, within a geographic service area. That is, the map server 200A could broadcast maps of a particular geographic area to mobile terminals, such as mobile terminal 100, within the geographic area. In some embodiments, the wireless communication link 106 could be a one-way communication link, and maps could be broadcast over the one-way wireless communication link 106 blindly, i.e. without knowledge of any mobile terminals 100 within the geographic area. In other embodiments, the wireless communication link 106 could be a one-way communication link, and map information could be broadcast or otherwise transmitted on demand to a requesting mobile terminal 100 in response to a request received over a separate communication link, such as the WLAN communication link 112 and/or a cellular communication link 108. [0046]The map server 200B can be located within or otherwise controlled by a mobile telephone switching office (MTSO) 116, in which case the map server 200B may communicate with the wireless telephone 100 primarily using the wireless communication interface 108. [0047]Some further aspects of a mobile terminal 100 according to some embodiments of the invention are illustrated in FIGS. 4A and 4B. As shown therein, a mobile terminal 100 may further include a position/velocity determination unit 146 and a traffic information unit 148. The position/velocity determination unit 146 and the traffic information unit 148 may communicate with the communication module 128 through the controller 126 as shown in FIG. 3. Alternatively or additionally, the position/velocity determination unit 146 and/or the traffic information unit 148 may communicate directly with the communication module 128, for example through a system bus. [0048]According to some embodiments, the position/velocity determination unit 146 may be configured to determine a current position and/or velocity of the mobile terminal 100. For example, the position/velocity determination unit 146 may include a global positioning system (GPS) receiver that permits the position/velocity determination unit 146 to determine the location of the mobile terminal 100 with a high degree of precision. The position/velocity determination unit 146 may include other systems and/or functionality for determining the location of the mobile terminal 100. For example, the position/velocity determination unit 146 may be configured to obtain location information for the mobile terminal 100 from a cellular communications network with which the mobile terminal 100 communicates. The position/velocity determination unit 146 may additionally or alternatively include an inertial guidance system that permits the position/velocity determination unit 146 to determine a position/velocity of the mobile terminal 100 through inertial movement from a known position. [0049]The traffic information unit 148 is configured to obtain information about current automobile and/or pedestrian traffic in or near a location at which the mobile terminal 100 is located and/or near a destination point, or along a route from a current location of the mobile terminal 100 to a destination point. For example, traffic information may be broadcast in one or more data subchannels of a public and/or private communication network that may be received by the mobile terminal 100. For example, Traffic Message Channel (TMC) data is available in a number of cities throughout North America and Europe. TMC data is broadcast continuously on FM radio channels, and may provide notification of accidents, road construction, police, or emergency action, etc. [0050]Traffic information obtained by the traffic information unit 148 may be used by the controller 126 to determine estimated travel times and/or route information for a user of the mobile terminal 100. [0051]The mobile terminal 100 may further include a map database 150 that contains map information concerning a geographic area in which the mobile terminal 100 is located, and/or in which a destination point is located. For example, the map database 150 may contain street/road information and/or may contain map information for other areas, such as pedestrian walking areas. The map information may further include information regarding features, such as buildings, fences, rivers, etc., that may constrain the motion of a user of the mobile terminal 100. [0052]Although the map database 150 is shown as a component of the terminal 102, it will be appreciated that the map database 150, and/or a portion of the map database 150, may be located remotely from the mobile terminal 100. For example, the map database 150 may be stored remotely and accessed through the communication module 128. A portion of the map database 150 may be retrieved and stored locally at the mobile terminal 100. Remote storage of the map database 150 may be desirable, since memory storage space in the mobile terminal 100 may be limited, and a map database may consume a significant amount of memory. In some embodiments, the map database 150 may be stored at a map server 200A, 200B. [0053]Referring to FIG. 4B, the user interface 122 can include an input device 134, such as a keypad 16, multifunction key 22, keyboard, touchpad, jog dial and/or other user input device. The user interface 122 may further include a primary display screen 18, such as an LCD display that is capable of displaying video signals in a video format, such as Quarter VGA (QVGA, 320×240 pixels), Common Intermediate Format (CIF, 360×288 pixels) and/or Quarter Common Intermediate Format (QCIF, 180×144 pixels). The mobile terminal 100 may include appropriate CODECs to permit the mobile terminal 100 to decode and display video signals in various formats. A secondary display screen 28 may also be provided. [0054]The user interface 122 can also include an audio interface unit including a microphone 14 coupled to an audio processor that is configured to generate an audio signal responsive to sound incident on the microphone, and a speaker 20 that generates sound responsive to an output audio signal. [0055]According to some embodiments, a navigational aid, such as a map, may be displayed on the primary display screen 18 and/or the secondary display screen 28. Furthermore, alerts and or navigational information may be communicated to a user of the mobile terminal 100 through the audio interface. [0056]Some aspects of a map server 200A according to some embodiments of the invention are illustrated in FIG. 5. As shown therein, a map server 200A may include a position/velocity determination unit 246 and a traffic information unit 248. The position/velocity determination unit 246 and the traffic information unit 248 may communicate with the communication module 228 through the controller 226 as shown in FIG. 5. Alternatively or additionally, the position/velocity determination unit 246 and/or the traffic information unit 248 may communicate directly with the communication module 228, for example through a system bus. [0057]According to some embodiments, the position/velocity determination unit 246 may be configured to determine a current position and/or velocity of a remotely located mobile terminal 100. For example, the position/velocity determination unit 246 may receive global positioning system (GPS) information from the mobile terminal 100 that permits the position/velocity determination unit 246 to determine the location of the mobile terminal 100 with a high degree of precision. The position/velocity determination unit 246 may include other systems and/or functionality for determining the location of the mobile terminal 100. For example, the position/velocity determination unit 246 may be configured to obtain location information for the mobile terminal 100 from a cellular communications network on which the mobile terminal 100 is registered. [0058]The traffic information unit 248 is configured to obtain information about current automobile and/or pedestrian traffic in or near a location at which the mobile terminal 100 is located and/or near a destination point, or along a route from a current location of the mobile terminal 100 to a destination point. [0059]Traffic information obtained by the traffic information unit 248 may be used by the controller 226 to determine estimated travel times and/or route information for a user of the mobile terminal 100. [0060]The map server 200 may further include a map database 250 that contains map information concerning a wide geographic area in which the mobile terminal 100 may be located. For example, the map database 250 may contain street/road information and/or may contain map information for other areas, such as pedestrian walking areas. The map information may further include information regarding features, such as buildings, fences, rivers, etc., that may constrain the motion of a user of the mobile terminal 100. [0061]According to some embodiments, a position of a mobile terminal 100 is determined. In some embodiments, the position of the mobile telephone may be determined by the position/velocity determination unit 146. In other embodiments, the position of the mobile terminal 100 may be determined by an element in the network 10 (FIG. 3). For example, the position of the mobile telephone may be determined by map server 200A or 200B. [0062]The mobile terminal 100 and/or the map server 200A, 200B may then determine if the estimated current position of the mobile terminal 100 is within a boundary of geographic map information stored in the mobile terminal 100, e.g. within a boundary of a map stored in short term memory, such as within the memory 125 (e.g. a RAM cache) and/or stored in the map database 150. If the current position of the mobile terminal 100 is within the boundary of the stored geographic map information, the mobile terminal 100 may display a map including the current position of the mobile terminal 100 on its primary display 18 and/or secondary display 28. [0063]If the current position of the mobile terminal 100 is not within the boundary of the geographic map information stored in the mobile terminal 100, geographic map information including the current position of the mobile terminal 100 may be retrieved by the mobile terminal 100 and/or pushed to the mobile terminal 100 from the map server 200A, 200B using the communication module 128. Thus, in some embodiments, it may not be necessary for the mobile terminal 100 to store large amounts of map information locally in the map database 150. Instead, the mobile terminal 100 may be able to download only the map information needed to be displayed at a given time. Old and/or unused map information may be stored locally, e.g. wit(String), 发明领域 [0001] 无线 通信终端技术领域本发明涉及无线通信终端,更具体地,涉及包括能够显示地图信息的显示屏的无线通信终端。 背景 [0002] 无线通信终端主要用于通过蜂窝电话网络获得对无线电话服务的访问。 然而,随着无线通信终端的能力增加,附加级别的用户功能被包括在这样的终端的硬件和/或软件中。 例如,通信终端可以配备静态和/或摄像机,允许用户拍摄照片和/或视频并从移动终端传输给其他人。 同样,许多通信终端包括适用于跟踪和管理日程、任务等的个人数字助理(PDA)类型的应用程序。 许多通信终端还包括消息传递能力,例如电子邮件(e-mail)、短消息服务(SMS)和多媒体消息服务(MMS)能力。 通信终端也能够通过使用互联网协议(IP)在无线和/或有线网络上连接到互联网。 [0003] 通信终端也越来越多地具有确定终端物理位置的能力。 例如,许多通信终端包括允许终端以高精度确定它们的位置的全球定位系统(GPS)接收器。 已经实现了用于确定通信终端位置的其他系统,包括从蜂窝通信网络获取位置信息的系统,以及通过惯性引导技术获取位置信息的系统。 [0004] 此外,一些无线网络能够确定注册到系统的终端的大致位置。 这样的位置信息可以用于例如在使用终端呼叫紧急帮助时向紧急操作员提供位置信息。 概括 [0005] 根据本发明的一些实施例的方法包括估计包括通信模块和显示屏的移动终端的当前地理位置,以及确定估计的移动终端的当前位置是否在移动终端中存储的地理地图信息的边界内。 终端。 如果移动终端的当前位置在存储的地理地图信息的边界内,则在显示器上显示包括移动终端的当前位置的地图。 如果移动终端的当前位置不在存储的地理地图信息的边界内,则使用通信模块向移动终端提供包括移动终端的当前位置的附加地理地图信息。 [0006] 该方法还可以包括确定地图的当前比例,以及确定存储的地图信息是否包含足够的地图信息来以当前比例填充显示屏。 如果存储的地图信息没有包含足够的地图信息来以当前比例填充显示屏幕,则可以缩小显示屏幕的比例直到存储的地图信息足以以缩小的比例填充显示屏幕。 [0007] 该方法还可以包括使用足以以当前比例填满显示屏幕的通信模块来检索附加地图信息,并且在已经检索到附加地图信息之后,将比例增加到当前比例。 [0008] 该方法还可以包括通过估计移动终端的当前速度并响应于移动终端的当前速度选择显示比例来确定显示屏幕的当前比例。 确定当前比例可以包括如果移动终端的速度较高则选择相对较大的比例并且如果移动终端的速度较小则选择较小的比例。 [0009]该方法还可以包括估计移动终端的当前行进速度和方向,并且响应于移动终端的当前行进速度和方向来估计移动终端将何时离开存储的地图信息所描述的区域。 [0010] 该方法还可以包括估计为移动终端正前往的地理区域下载附加地图信息所需的时间量,以及在移动终端离开存储的地图信息所描述的区域之前下载附加地图信息。 [0011] 估计移动终端的当前位置可以由远程服务器响应于网络生成的位置信息来执行。 该方法还可以包括如果移动终端的当前位置不在存储的地理地图信息的边界内则从远程服务器向移动终端发送附加地图信息。 [0012] 在显示器上显示包括移动终端的当前位置的地图可以包括在移动终端未使用预定时间段之后在显示器上显示地图。 [0013] 移动终端还可以包括在设备的翻盖部分上的副显示屏,该副显示屏可在打开位置和闭合位置之间移动,使得副显示屏在翻盖部分处于闭合位置时可见。 该方法可以包括当翻盖部分处于关闭位置时在辅助显示器上显示包括移动终端的当前位置的地图。 [0014] 该方法还可以包括确定移动终端已经进入空闲模式,并且降低显示器的亮度和/或关闭显示器。 估计移动终端的当前地理位置并判断估计的移动终端的当前位置是否在移动终端存储的地理地图信息的边界内可以在移动终端处于空闲模式时执行。 此外,可以在移动终端处于空闲模式时执行使用通信模块向移动终端提供附加地理地图信息。 [0015] 根据本发明一些实施例的移动终端包括通信模块、显示屏和控制电路。 该电路被配置为估计移动终端的当前地理位置,并确定估计的移动终端的当前位置是否在存储在移动终端中的地理地图信息的边界内。 该电路还被配置为如果移动终端的当前位置在所存储的地理地图信息的边界内则在显示器上显示包括移动终端的当前位置的地图,并且检索包括当前位置的附加地理地图信息 如果移动终端的当前位置不在存储的地理地图信息的边界内,则移动终端使用通信模块。 [0016] 该电路还可以被配置为确定地图的当前比例,以确定存储的地图信息是否包含足够的地图信息以在当前比例下填充显示屏,以及减小显示屏的比例直到存储的地图信息 如果存储的地图信息不包含足够的地图信息来以当前比例填充显示屏幕,则足以以缩小的比例填充显示屏幕。 [0017] 该电路还可以被配置为使用通信模块检索附加地图信息,并且在已经检索到附加地图信息之后将比例尺增加到大于缩小比例尺的增加比例尺。 [0018] 该电路还可以被配置为通过估计移动终端的当前速度来确定显示屏幕的当前比例,并且响应于移动终端的当前速度来选择显示比例。 [0019]该电路还可以被配置为估计移动终端的当前行进速度和方向,并且响应于移动终端的当前行进速度和方向,估计移动终端何时将离开由 存储的地图信息。 该电路还可以被配置为估计下载移动终端正前往的地理区域的附加地图信息以及在移动终端离开所存储的地图信息所描述的区域之前下载附加地图信息所需的时间量 . [0020] 根据本发明一些实施例的地图服务器包括被配置为与位于远程的移动终端通信的通信模块、被配置为为移动终端估计位置/速度信息的位置/速度确定单元、存储地图信息的数据库、以及 电路被配置为确定移动终端的估计当前位置是否在存储在移动终端中的地理地图信息的边界内,并且如果是则使用通信模块从数据库发送包括移动终端的当前位置的附加地理地图信息 移动终端当前位置不在存储的地图信息范围内。 [0021] 位置/速度确定单元可以被配置为使用由移动终端在其中注册的通信网络提供的位置信息来估计移动终端的当前位置。 [0022] 该电路还可以被配置为使用移动终端的位置/速度来估计移动终端何时将离开存储在移动终端处的地图信息所描述的区域,以估计下载附加地图信息所需的时间量 移动终端正前往的地理区域,并且在移动终端离开存储在移动终端处的地图信息所描述的区域之前将附加地图信息发送到移动终端。 附图的简要说明 [0023] 包括的附图是为了提供对本发明的进一步理解并且并入本申请并构成本申请的一部分,图示了本发明的某些实施例。 在图纸中: [0024] 图1图示了根据本发明一些实施例的电子设备。 [0025] 图2A-2B示出了根据本发明一些实施例的翻盖式移动电话。 [0026] 图3是图示根据本发明的一些实施例的电子设备和蜂窝通信系统的示意性框图。 [0027] 图4A和4B是图示根据本发明一些实施例的电子设备的一些方面的示意性框图。 [0028] 图5是示出根据本发明一些实施例的地图服务器的示意性框图。 [0029] 图6A, 6 乙, 7 一种, 7 乐队 7 C是根据本发明的一些实施例配置的显示屏的示例性图示。 [0030] 图8-11是说明根据本发明一些实施例的电子设备的操作的流程图。 具体实施方式的详细说明 [0031] 现在将参考附图更全面地描述本发明,在附图中示出了本发明的实施例。 然而,本发明不应被解释为限于在此阐述的实施例。 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明的范围充分地传达给本领域的技术人员。 相同的数字始终指代相同的元素。 如本文所用,术语“包括”或“包括”是开放式的,并且包括一个或多个规定的要素、步骤和/或功能而不排除一个或多个未规定的要素、步骤和/或功能。 如本文所用,术语“和/或”包括一个或多个关联列出的项目的任何和所有组合。 [0032] 参照方框图和/或方法和通信终端的操作说明来描述根据本发明的实施例。 应当理解,方框图和/或操作说明的每个方框,以及方框图和/或操作说明中方框的组合,可以通过射频、模拟和/或数字硬件、和/或程序来实现 指示。 这些程序指令可以提供给控制器,该控制器可以包括一个或多个通用处理器、专用处理器、ASIC和/或其他可编程数据处理装置,使得经由控制器和/或其他可编程数据处理装置执行的指令 数据处理设备,创建用于实现框图和/或操作块中指定的功能/动作的装置。 在一些实施方式中,块中标注的功能/动作可能不按操作说明中标注的顺序发生。 例如,连续显示的两个块实际上可以基本上同时执行,或者这些块有时可以以相反的顺序执行,这取决于所涉及的功能/动作。 [0033] 如本文所用,“通信终端”(或简称为“终端”)包括但不限于配置为通过有线连接(例如通过公共交换电话网络)接收/发送通信信号的设备 (PSTN)、数字用户线 (DSL)、数字电缆、直接电缆连接和/或另一个数据连接/网络,和/或通过无线接口与例如蜂窝网络、无线局域网( WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM/FM广播发射机和/或另一个通信终端。 被配置为通过无线接口进行通信的通信终端可以称为“无线通信终端”、“无线终端”和/或“移动终端”。 移动终端的示例包括但不限于卫星或蜂窝无线电话; 个人通信系统 (PCS) 终端,可将蜂窝无线电话与数据处理、传真和数据通信功能相结合; 可包括无线电话、寻呼机、互联网/内联网访问、Web 浏览器、管理器、日历和/或全球定位系统 (GPS) 接收器的 PDA; 以及包括无线电话收发器的常规膝上型和/或掌上型接收器或其他器具。 [0034] 电子设备之间的无线通信可以使用各种各样的通信媒体、通信系统和通信标准来实现。 例如,诸如无线移动电话的移动终端通常被配置为通过模拟和/或数字无线射频(RF)电话系统进行通信。 此类设备还可配置为使用有线和/或无线局域网 (LAN)、短程通信信道(例如蓝牙 RF 通信信道和/或红外通信信道)和/或远程通信系统(例如卫星)进行通信 通信系统。 [0035] 根据本发明实施例的诸如无线移动电话的移动终端可以具有多种形状、尺寸和外壳类型。 几种类型的移动电话外壳的示例在图1至2B中示出。 比如移动端 100 图 1 中图示了根据一些实施例的移动终端 100 A包括外壳 15 容纳和保护移动终端的电子设备 100 A.移动端 100 A包括一个LCD显示器 18 和一个键盘 16 . 移动端 100 A还包括一个多功能控制/输入按钮 22 可用于选择菜单项和/或向移动终端输入命令 100 一种。 [0036] 移动端 100 A包括一个麦克风端口 14 和耳机/扬声器 20 . 住房 15 可以设计成当耳机/扬声器与用户的耳朵形成声学密封 20 被放置在用户的头部。 移动端 100A可以被配置为播放视频文件和/或音频文件,例如歌曲文件,它们可以是立体声信号。 [0037] 翻盖式移动终端 100 B如图2A和2B所示。 翻盖式移动终端 100 B在图2A中显示为打开位置,在图2B中显示为关闭位置。 移动端 100 B包括外壳 15 包括一个较低的住房 15 A 和上部外壳,或“翻盖”部分 15 B 通过铰链可旋转地连接 24 . 移动端 100 B 包括一个主 LCD 显示屏 18 在翻盖内侧 15 B 和键盘 16 在下部外壳的内侧 15 A.移动端 100 B还包括一个多功能控制/输入按钮 22 . [0038] 移动端 100 A包括一个麦克风端口 14 在较低的外壳上 15 A和耳机/扬声器 20 在翻盖内侧 15 B. 如图 2B 所示,辅助显示 28 和一个相机镜头 30 可能位于翻盖的外侧 15 B. [0039] 图3是无线通信系统的示意框图 10 其中包括一个移动终端 100 配置为与地图服务器通信 200 一种, 200 B. 例如移动端 100 可以与地图服务器通信 200 A 通过直接无线通信接口 106 , 通过另一个无线通信接口 108 通过一个或多个蜂窝基站 110 a - b ,和/或通过另一个无线通信接口 112 通过无线局域网 (WLAN) 接入点 114 . 直接无线通讯接口 106 可以包括RF无线通信接口,例如蓝牙接口或红外通信接口,例如由红外数据协会(IRDA)协议定义的红外通信接口。 IRDA 定义了许多红外无线数据通信标准,包括数据速率高达 16 Mb/s 的红外无线通信标准。 可以理解,移动终端 100 可以是手持无线通信终端,例如手机、PDA等。 [0040] 如图 3 进一步所示,移动终端 100 可以包括用户界面 122 , 一个控制器 126 , 通信模块 128 , 和记忆 125 . [0041] 通信模块 128 被配置为通过一个或多个无线接口传送数据 106 , 108 , 和/或 112 到另一个远程终端或其他通信设备,例如地图服务器 200 一种, 200 B、记忆 125 被配置为存储供控制器使用的程序和/或数据 126 . 记忆 125 可能包括一个非易失性存储器,即使在移动终端通电时也能存储数字信息 100 已关闭。 [0042] 通信模块 128 可以包括例如蜂窝通信模块、蓝牙模块、红外通信模块和/或WLAN模块。 带有蜂窝通信模块的移动终端 100 可以通过基站进行通信 110 a - b 使用一种或多种蜂窝通信协议,例如高级移动电话服务 (AMPS)、ANSI-136、全球移动标准 (GSM) 通信、通用分组无线服务 (GPRS)、增强数据速率的 GSM 演进 (EDGE) )、码分多址 (CDMA)、宽带 CDMA、CDMA2000 和通用移动电信系统 (UMTS)。 蜂窝基站 110 a - b 可以连接到移动电话交换局 (MTSO) 116 ,这反过来又可以连接到一个或多个其他网络 118 (例如互联网、公共交换电话网络和/或其他网络)。 带有蓝牙或红外模块,移动终端 100可以使用直接接口通过临时网络进行通信 106 . 带有WLAN模块,移动终端 100 可以通过WLAN路由器进行通信 114 使用的通信协议可能包括但不限于 802.11a、802.11b、802.11e、802.11g 和/或 802.11i。 移动电话也可以配置为直接通过网络通信 118 . [0043] 移动端 100 可以被配置为向/从另一个通信终端发送和/或接收数字数据信号,该另一个通信终端可以通过例如MTSO与其通信耦合 116 , 和/或另一个网络 118 ,例如公共交换电话网 (PSTN)。 然而,从前面的描述中可以理解,移动终端之间的数据通信 100 无需使用 MTSO 即可完成另一个终端 116 或其他网络 118 . [0044] 移动端 100 我还包括 AM/FM 无线电调谐器、UHF/VHF 调谐器、卫星无线电调谐器、DVB-H 接收器和/或配置为接收广播音频/视频信号和/或数据信号的另一个接收器。 [0045] 地图服务器 200 A可以是独立的服务器,配置为与移动终端通信 100 通过无线通信链路,例如 WLAN 通信链路 112 ,一个直接的无线通信链路 106 ,和/或另一个无线通信接口 108 通过一个或多个蜂窝基站 110 a - b . 例如,地图服务器 200 A 可以配置为通过无线通信链路广播包括地图信息的数据信号 106 到移动终端,比如移动终端 100 , 在一个地理服务区内。 即地图服务器 200 A可以向移动终端广播特定地理区域的地图,例如移动终端 100 , 在地理区域内。 在一些实施例中,无线通信链路 106 可以是单向通信链路,地图可以通过单向无线通信链路广播 106 盲目地,即不了解任何移动终端 100 地理区域内。 在其他实施例中,无线通信链路 106 可以是单向通信链路,地图信息可以按需广播或以其他方式传输到请求移动终端 100 响应通过单独的通信链路(例如 WLAN 通信链路)收到的请求 112 和/或蜂窝通信链路 108 . [0046] 地图服务器 200 B 可以位于移动电话交换局 (MTSO) 内或由其控制 116 ,在这种情况下,地图服务器 200 B可与无线电话通话 100 主要使用无线通信接口 108 . [0047] 移动终端的一些进一步方面 100 根据本发明的一些实施例,在图4A和4B中示出。 如图所示,移动终端 100 可以进一步包括位置/速度确定单元 146 和一个交通信息单元 148 . 位置/速度确定单元 146 和交通信息单元 148 可与通讯模块通讯 128 通过控制器 126 如图 3 所示。可替代地或附加地,位置/速度确定单元 146 和/或交通信息单元 148 可直接与通讯模块通讯 128 ,例如通过系统总线。 [0048] 根据一些实施例,位置/速度确定单元 146 可以被配置为确定移动终端的当前位置和/或速度 100 . 例如,位置/速度确定单元 146 可能包括允许位置/速度确定单元的全球定位系统 (GPS) 接收器 146 确定移动终端的位置 100 具有高精度。 位置/速度确定单元146 可以包括用于确定移动终端位置的其他系统和/或功能 100 . 例如,位置/速度确定单元 146 可以配置为获取移动终端的位置信息 100 来自移动终端所使用的蜂窝通信网络 100 沟通。 位置/速度确定单元 146 可以额外地或替代地包括允许位置/速度确定单元的惯性制导系统 146 确定移动终端的位置/速度 100 通过已知位置的惯性运动。 [0049] 交通信息单元 148 被配置为获取关于移动终端所在位置或其附近的当前汽车和/或行人交通的信息 100 位于和/或靠近目的地点,或沿着移动终端当前位置的路线 100 到一个目的地点。 例如,可以在移动终端可以接收的公共和/或专用通信网络的一个或多个数据子信道中广播交通信息 100 . 例如,交通信息频道 (TMC) 数据在北美和欧洲的许多城市都可用。 TMC 数据在 FM 无线电频道上连续广播,并可能提供事故、道路施工、警察或紧急行动等通知。 [0050] 交通信息单元获取的交通信息 148 可以被控制器使用 126 为移动终端的用户确定估计的旅行时间和/或路线信息 100 . [0051] 移动端 100 可能还包括地图数据库 150 包含有关移动终端所在地理区域的地图信息 100 位于,和/或目标点位于其中。 比如地图数据库 150 可能包含街道/道路信息和/或可能包含其他区域的地图信息,例如步行区。 地图信息还可以包括关于可能限制移动终端的用户的运动的特征的信息,例如建筑物、栅栏、河流等 100 . [0052] 虽然地图数据库 150 显示为终端的一个组件 102 , 将会理解地图数据库 150 和/或地图数据库的一部分 150 , 可能位于远离移动终端的地方 100 . 比如地图数据库 150 可远程存储并通过通信模块访问 128 . 地图数据库的一部分 150 可以在移动终端本地检索和存储 100 . 地图数据库远程存储 150 可能是可取的,因为移动终端中的内存存储空间 100 可能是有限的,并且地图数据库可能会消耗大量内存。 在一些实施例中,地图数据库 150 可以存储在地图服务器上 200 一种, 200 B. [0053] 参考图 4B,用户界面 122 可以包括一个输入设备 134 , 比如键盘 16 , 多功能键 22 、键盘、触摸板、滚轮和/或其他用户输入设备。 用户界面 122 还可以包括主显示屏 18 ,例如能够以视频格式显示视频信号的 LCD 显示器,例如四分之一 VGA(QVGA,320×240 像素)、通用中间格式(CIF,360×288 像素)和/或四分之一通用中间格式( QCIF,180×144 像素)。 移动端 100 可能包括适当的编解码器以允许移动终端 100 解码和显示各种格式的视频信号。 副显示屏 28 也可以提供。 [0054] 用户界面 122 还可以包括一个音频接口单元,包括一个麦克风 14 耦合到音频处理器和扬声器,音频处理器被配置为响应于入射在麦克风上的声音而生成音频信号 20 产生响应于输出音频信号的声音。 [0055]根据一些实施例,可以在主显示屏上显示诸如地图的导航帮助 18 和/或辅助显示屏 28 . 此外,可以将警报和/或导航信息传送给移动终端的用户 100 通过音频接口。 [0056] 地图服务器的某些方面 200 图 5 中说明了根据本发明的一些实施例。如其中所示,地图服务器 200 A可以包括位置/速度确定单元 246 和一个交通信息单元 248 . 位置/速度确定单元 246 和交通信息单元 248 可与通讯模块通讯 228 通过控制器 226 如图5所示。可替代地或附加地,位置/速度确定单元 246 和/或交通信息单元 248 可直接与通讯模块通讯 228 ,例如通过系统总线。 [0057] 根据一些实施例,位置/速度确定单元 246 可以被配置为确定远程移动终端的当前位置和/或速度 100 . 例如,位置/速度确定单元 246 可以从移动终端接收全球定位系统(GPS)信息 100 允许位置/速度确定单元 246 确定移动终端的位置 100 具有高精度。 位置/速度确定单元 246 可以包括用于确定移动终端位置的其他系统和/或功能 100 . 例如,位置/速度确定单元 246 可以配置为获取移动终端的位置信息 100 来自移动终端所在的蜂窝通信网络 100 已登记。 [0058] 交通信息单元 248 被配置为获取关于移动终端所在位置或其附近的当前汽车和/或行人交通的信息 100 位于和/或靠近目的地点,或沿着移动终端当前位置的路线 100 到一个目的地点。 [0059] 交通信息单元获取的交通信息 248 可以被控制器使用 226 为移动终端的用户确定估计的旅行时间和/或路线信息 100 . [0060] 地图服务器 200 可能还包括地图数据库 250 包含有关移动终端所在广阔地理区域的地图信息 100 可能位于。 比如地图数据库 250 可能包含街道/道路信息和/或可能包含其他区域的地图信息,例如步行区。 地图信息还可以包括关于可能限制移动终端的用户的运动的特征的信息,例如建筑物、栅栏、河流等 100 . [0061] 根据一些实施例,移动终端的位置 100 决心,决意,决定。 在一些实施例中,移动电话的位置可以由位置/速度确定单元确定 146 . 在其他实施例中,移动终端的位置 100 可能由网络中的元素决定 10 (图 3)。 例如,移动电话的位置可以由地图服务器确定 200 一个或 200 B. [0062] 移动端 100 和/或地图服务器 200 一种, 200 B然后可以确定移动终端的估计的当前位置是否 100 在移动终端存储的地理地图信息的边界内 100 ,例如 在存储在短期记忆中的地图的边界内,例如在内存中 125 (例如 RAM 缓存)和/或存储在地图数据库中 150 . 如果移动端当前位置 100 在存储的地理地图信息的边界内,移动终端 100 可以显示包含移动终端当前位置的地图 100在其主显示屏上 18 和/或辅助显示器 28 . [0063] 如果移动端当前位置 100 不在移动终端存储的地理地图信息范围内 100 ,包括移动终端当前位置的地理地图信息 100 可通过移动端检索 100 和/或推送到移动端 100 从地图服务器 200 一种, 200 B 使用通信模块 128 . 因此,在一些实施例中,移动终端可能不需要 100 在本地地图数据库中存储大量地图信息 150 . 取而代之的是移动端 100 可以只下载给定时间需要显示的地图信息。 旧的和/或未使用的地图信息可以存储在本地,例如 在记忆中 125 和/或地图数据库 150 , 但可能会根据需要删除,以便为更新的地图信息提供空间。 [0064] 此外,移动终端当前位置的地图 100 可以在主显示器上连续显示,例如作为屏幕保护程序或背景 18 或辅助显示 28 ,这样用户就可以很容易地获得地图信息,而不必选择菜单项、按键或以其他方式发出显示当前地图的命令。 [0065] 移动端 100 当移动终端没有连接到外部电源时,可以配置为在一段时间不活动之后进入空闲模式或电池节省模式以保存电池电量。 进入闲置或省电模式后,主显示屏 18 和/或辅助显示器 28 可以调暗和/或可以关闭背光,但移动终端 100 可能会继续跟踪和更新其位置/速度。 在一些实施例中,主显示器 18 和/或辅助显示器 28 可以关闭,但是移动端的位置/速度 100 仍然可以计算,并且可以根据需要下载新的地图信息。 当移动终端“醒来”时(例如,当用户按下按钮时),新位置可以在显示屏上轻松快速地更新,而无需用户等待位置更新和/或新地图信息的下载。 [0066] 根据本发明的实施例的样本显示图像如图 6A-6B 所示, 7 一种- 7 B.例如,图6A图示了地图图像 120 可能会显示在主显示器上 18 和/或辅助显示器 28 移动终端的 100 . 移动终端的位置 100 由图标指示 140 可以指示移动终端的位置和行进方向 100 . 在图 6A 所示的显示中,图标 140 位于显示屏中央,其中还包括一个图标 142 指示北方方向,以及比例指示器 144 显示每单位显示屏的距离。 在所示示例中,比例尺为每单位 1 公里。 可以使用其他比例指示器。 例如,可以在显示器上叠加一个网格图案,每个网格分区代表一个特定的距离(例如 1 公里、100 米等)。 [0067] 显示地图图像 120 , 地图数据库 150 移动端 100 包括地图图像中显示的整个区域的地图信息 120 . 另外,地图数据库 150 可能包含其他区域的地图信息,例如地图图像中显示的区域周围的区域 120 . 地图数据库中存储的附加地图信息 150 移动端 100 但当前未显示在图 6A 中显示为区域 132 以虚线显示。 作为移动端 100 移动,地图图像 120 也可以移动保持图标 140 对应移动端 100 以地图图像为中心 120 . [0068] 当移动端 100靠近地图数据库中存储的地图信息的边缘或边界 150 , 移动端 100 可以从地图服务器下载额外的地图信息 200 一种, 200 B、例如,如图6B所示,移动终端 100 100 , 如图标所示 140 , 已经移动到显示图像的边缘 120 已到达地图信息的边缘 132 存储在地图数据库中 150 移动端 100 . 参考图 7A,附加地图信息 134 可以从地图服务器下载 200 一种, 200 B 为移动终端进入的区域 100 正在移动。 [0069] 在一些实施例中,附加的地图信息可以被下载到移动终端 100 在移动端之前 100 移动到如此靠近地图信息的边缘或边界 132 存储在地图数据库中 150 即移动端 100 将用完地图信息以显示在显示屏上 18 , 28 在目前的规模。 但是,如果由于某些原因,例如网络拥塞和/或地图服务器不可用 200 一种, 200 B、移动端 100 无法检索到足够的地图信息 132 以当前比例显示全屏,移动端 100 可以更改地图的显示比例,以便存储的地图信息继续显示在屏幕上。 例如,如图7B所示,作为移动终端 100 移动到存储的地图信息的边缘 132 , 尺度缩小为每单位 500 m。 或者,如果移动终端 100 无法检索到足够的附加地图信息 134 以当前比例显示全屏,移动端 100 可以保持当前比例并移动图标 140 代表移动端 100 偏离显示图像的中心 120 如图7C所示直到附加地图信息 134 已下载。 [0070] 因此,本发明的一些实施例可以包括确定地图的当前比例,以及确定存储的地图信息是否包含足够的地图信息来以当前比例填充显示屏。 如果存储的地图信息没有包含足够的地图信息以填充当前比例尺的显示屏幕,则可以缩小显示屏幕的比例尺直到存储的地图信息足以以缩小的比例尺填充显示屏幕,并且地图 可能会显示在显示屏上 18 , 28 缩小比例,或图标 140 代表移动端 100 可能会远离显示器的中心 120 . [0071] 从地图服务器下载附加地图信息后 200 一种, 200 B,比例可能会增加(例如,显示的比例可能会增加到以前的比例)和/或图标 140 可以移回显示的中心。 [0072] 一些实施例可以估计移动终端的当前行进速度和方向 100 并估计,响应于移动终端当前的行进速度和方向 100 , 当移动端 100 将离开存储的地图信息描述的区域 132 . 移动终端所在的位置 100 将离开存储的地图信息所描述的区域 132 可根据道路位置、移动终端当前速度和方向进行预测 100 、拥堵/交通状况和/或其他因素。 为移动终端下载某个地理区域的附加地图信息所需的时间量 100 可以预估正在前往的方向,可以在移动终端之前下载附加地图信息 100 离开存储的地图信息所描述的区域。 这样,移动终端所在区域的地图 100 位置可以在移动端无缝显示 100 移动到以前没有地图信息的区域。 [0073] 在一些实施例中,可以响应于移动终端的速度来设置显示的比例 100 . 例如,在低速时,可以使用较低的刻度,而在高速时,可以使用较高的刻度。 例如,在高速下,可以使用诸如每单位1公里或更高的比例,而在较低速度下,可以使用小于每单位1公里的比例。 [0074] 估计移动终端的当前位置 100 可由移动终端执行 100 和/或可以由远程服务器执行,例如地图服务器 200 一种, 200 B、响应网络生成的位置信息。 [0075] 在一些实施例中,地图包括移动终端的当前位置 100 可能会显示在主显示屏上 18 和/或辅助显示器 28 在预定的不使用移动终端的时间之后 100 ,例如 作为屏幕保护程序或默认图像。 [0076] 在一些实施例中,移动终端 100 可能包括一个辅助显示屏 28 在可在打开位置和关闭位置之间移动的翻盖部分上,以便副显示屏 28 当翻盖部分处于关闭位置时,如图 2A 和 2B 所示,可见。 在那种情况下,地图包括移动终端的当前位置 100 当翻盖部分处于关闭位置时,可以在副显示器上显示。 [0077] 图8-10是说明根据本发明一些实施例的电子设备的操作的流程图。 例如,如图8的流程图所示,根据一些实施例,诸如移动终端的设备的位置 100 ,估计(块 205 ). 如上所述,设备的位置 100 可以由设备本身使用 GPS 定位、惯性导航或任何其他合适的技术来估计。 设备的位置 100 也可以由例如远程服务器确定,例如地图服务器 200 一种, 200 B 使用基于网络的定位技术和/或使用移动终端提供的信息 100 . [0078] 在座 210 ,确定移动终端是否 100 位于移动终端本地存储的地图信息所描述的区域内 100 , 比如在地图数据库中 150 移动端 100 . [0079] 如果设备 100 位于移动终端本地存储的地图信息所描述的区域 100 ,地图显示在移动终端的屏幕上 100 , 如主显示器 18 和/或辅助显示器 28 (堵塞 220 ). [0080] 但是,如果设备不在本地存储的地图信息所描述的区域(即设备 100 没有其当前位置的地图),则可以获得额外的地图信息(块 215 ). 附加地图信息可以从远程服务器下载,例如地图服务器 200 一种, 200 B、和/或附加地图信息可以从远程服务器推送,例如地图服务器 200 一种, 200 B、到移动端 100 , 没有先接收到来自移动端的请求 100 . 一旦移动终端接收到附加地图数据 100 ,地图可以显示在移动终端的屏幕上 100 , 如主屏幕 18 和/或辅助屏幕 28 . [0081] 图 9 的流程图中说明了本发明的进一步实施例。如其中所示,在方框 305 移动终端屏幕显示地图信息的默认比例尺 100 决心,决意,决定。 接下来检查移动终端本地存储的地图信息是否 100 , 比如在地图数据库中 150 移动端 100 , 足以以默认比例显示全屏信息(块 310 ). 如果是,则地图显示在屏幕上(块 320 ). [0082]但是,如果本地存储的地图信息不足以显示全屏,则可能会缩小显示比例和/或图标 140 代表移动端 100 可以从显示图像的中心移开 120 (堵塞 315 ) 直到本地存储了足够数量的地图信息以允许全屏显示(块 310 ). 然后地图可以修改后的(缩小的)比例尺(方块)显示在显示屏上 320 ). [0083] 在 Block 进行支票 325 查看比例是否缩小或图标是否 140 被转移到街区 315 . 如果是这样,可以将额外的地图数据下载到移动终端 100 (根据要求或推送到移动端 100 ) (堵塞 330 ). 然后可以增加显示的比例,例如增加到默认比例,和/或图标 140 可以移回显示图像的中心 120 (堵塞 335 ). [0084] 本发明的进一步实施例在图10的流程图中示出。如图所示,在一些实施例中,移动终端 100 可以显示一个地图,显示移动终端的位置 100 在当前规模(块 405 ). 移动终端何时产生估计 100 将留下移动终端本地存储的地图信息覆盖的区域 100 ,例如在地图数据库中 150 (堵塞 415 ). 该估计可以基于诸如移动终端的速度和方向等因素 100 、道路、桥梁、路口等位置,可影响移动终端用户当前路线的出行时间、交通/拥堵 100 , ETC。 [0085] 还可以估计用于下载额外地图数据的时间量(块 420 ). 可将附加地图数据传输至移动终端 100 就在移动终端之前 100 离开存储的地图数据的区域(块 425 ). 因此,可以延迟附加地图数据的下载,直到实际需要该数据为止。 这可以潜在地避免下载不需要的地图信息。 [0086] 图 11 中说明了本发明的其他实施例。如其中所示,在方框 510 , 移动终端的位置 100 使用例如图8所示的操作更新并显示在显示屏上。检查移动终端是否 100 已进入空闲或节电模式(块 520 ). 如果没有,移动端 100 继续更新并显示其所描述的位置。 [0087] 如果移动端 100 已进入空闲或省电模式,移动终端的显示屏幕 100 可以调暗(例如,通过降低背光亮度或完全关闭背光)或完全关闭(阻止 530 ). 但是,移动端 100 可能会继续估计其位置(块 540 ) 并确定其位置是否在存储的地图信息覆盖的区域内(块 550 ). 如果没有,则移动终端可以获得额外的地图信息(Block 560 ) 覆盖移动终端所在的地理区域 100 位于。 [0088] 移动端 100 然后确定它是否已经退出空闲或电池节能模式(块 570 ), 如果是,则显示包含移动终端当前位置的地图 100 在显示屏上(块 580 ). 否则,操作返回阻塞 540 ,并且移动终端继续估计它的位置。 [0089] 已经参考图8-11部分地描述了本发明,图8-11是说明根据本发明的方面的示例性操作的流程图图示。 将理解,图8-11的流程图的块以及流程图中块的组合可以使用包括在诸如移动终端的终端中的电子电路来实现 100. 还应当理解,图 8-11 的流程图的块以及流程图中的块的组合可以使用不同于图 1 到 5 中所示的组件来实现,并且通常, 图8-11的流程图图示和流程图图示中的块的组合,可以在诸如分立模拟和/或数字电路的专用硬件中实现,诸如集成电路的组合或一个或多个专用集成电路(ASIC) ), 以及通过可以加载到计算机或其他可编程数据处理设备上的计算机程序指令来生产机器, 使得在计算机或其他可编程数据处理设备上执行的指令创建用于实现在 流程图块或块。 计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,以导致在计算机或其他可编程设备上执行一系列操作步骤,以产生计算机实现的过程,使得在计算机或其他可编程数据处理设备上执行的指令 其他可编程装置提供用于实现流程图块或块中指定的功能的步骤。 [0090] 因此,图8-11的流程图图示的块支持用于执行指定功能/动作的电子电路和其他装置,以及用于执行指定功能/动作的步骤的组合。 应当理解,图 8-11 的流程图的每个块所支持的电路和其他装置,以及其中的块的组合,可以通过在专用或通用数据处理器上运行的专用硬件、软件或固件来实现, 或其组合。 [0091] 在附图和说明书中,已经公开了本发明的实施例,尽管使用了特定的术语,但它们仅用于一般和描述性的意义,而不是为了限制的目的,本发明的范围如下所述 索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:39.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101688786A(String), CN101688786B(String), EP2167919A1(String), EP2167919B1(String), JP2010534858A(String), JP4951707B2(String), KR101491195B1(String), KR1020100041814A(String), US20090017840A1(String), US8099108B2(String), WO2009008909A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.042 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.043 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.043 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101688786A(String), CN101688786B(String), EP2167919A1(String), EP2167919B1(String), JP2010534858A(String), JP4951707B2(String), KR101491195B1(String), KR1020100041814A(String), US20090017840A1(String), US8099108B2(String), WO2009008909A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8099108B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101688786A(String), CN101688786B(String), EP2167919A1(String), EP2167919B1(String), JP2010534858A(String), JP4951707B2(String), KR101491195B1(String), KR1020100041814A(String), US20090017840A1(String), US8099108B2(String), WO2009008909A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), CN101688786A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), CN101688786B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), EP2167919A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), EP2167919B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), JP2010534858A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), JP4951707B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), KR101491195B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), KR1020100041814A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), US20090017840A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), US8099108B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271653(Integer), WO2009008909A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.501 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8099108B2(String), US8099108B2(String), 1326729600(Integer), 271653(Integer), 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185965(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 185965(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1660818391(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185965(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 23104(Integer), 2(Integer), 185965(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:40.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权 | 权利转移(String), 3(Integer), 185965(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130346212A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US20130346212A1(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in a macrocell of the macro base station set in a downlink broadcast channel of the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station among the at least one femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations of the mobile terminal and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list of the neighboring femto base stations and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别设置在宏小区的下行链路广播信道中的宏基站的宏小区中的毫微微小区。 当移动终端在广播信道部分中的至少一个毫微微基站中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成移动终端的相邻毫微微基站列表和相邻毫微微基站信息,并发送相邻毫微微基站列表和相邻毫微微基站信息。 移动终端的相邻毫微微基站。(String), US14/014938(String), 1377792000(Integer), US20130346212A1(String), 1387987200(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 2(Integer), US20090307091A1 | US7489768B1(String), 4(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185966(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\46e8b34b9fc045249d19830e14ed71f0.png(String), 185966(Integer), 46e8b34b9fc045249d19830e14ed71f0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US20130346212A1(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in a macrocell of the macro base station set in a downlink broadcast channel of the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station among the at least one femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations of the mobile terminal and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list of the neighboring femto base stations and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别设置在宏小区的下行链路广播信道中的宏基站的宏小区中的毫微微小区。 当移动终端在广播信道部分中的至少一个毫微微基站中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成移动终端的相邻毫微微基站列表和相邻毫微微基站信息,并发送相邻毫微微基站列表和相邻毫微微基站信息。 移动终端的相邻毫微微基站。(String), US14/014938(String), 1377792000(Integer), US20130346212A1(String), 1387987200(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 2(Integer), US20090307091A1 | US7489768B1(String), \20230420\46e8b34b9fc045249d19830e14ed71f0.png(String), 4(Integer), 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185966(Integer), 1. A method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising:identifying a voice call transmitting signal transmitted from the mobile terminal;postponing transmission of the voice call transmitting signal, in response to the identification of the voice call transmitting signal; andoffering a unique voice advertisement service of the femto base station, in response to the identification of the voice call transmitting signal.(String), 1.一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括:识别移动终端发送的语音呼叫发送信号;延迟发送语音呼叫发送信号,以响应语音呼叫发送信号的识别;和响应语音呼叫发射信号的识别,提供毫微微基站的独特语音广告服务。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185966(Integer), 2. The method of claim 1, further comprising:identifying a ringback tone signal transmitted from a receiving side; andstopping the unique voice advertisement service of the femto base station in response to the identification of the ringback tone signal.(String), 2.如权利要求1所述的方法,还包括:识别接收端发送的回铃音信号;和响应回铃音信号的识别,停止毫微微基站的唯一语音广告服务。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185966(Integer), 3. A method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising:identifying a data communication connection signal transmitted from the mobile terminal;postponing transmission of the data communication connection signal, in response to the identification of the data communication connection signal; andoffering a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal.(String), 3.一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括:识别移动终端发送的数据通信连接信号;响应于数据通信连接信号的识别,推迟数据通信连接信号的传输;和响应于数据通信连接信号的识别,向移动终端提供毫微微基站的唯一广告服务。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.754 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185966(Integer), 4. The method of claim 3, further comprising:identifying a data reception signal about a uniform resource locator (URL) address that the mobile terminal desires to access; andstopping the unique advertisement service of the femto base station, in response to the identification of the data reception signal.(String), 4.如权利要求3所述的方法,还包括:识别关于移动终端希望访问的统一资源定位符(URL)地址的数据接收信号;和响应于数据接收信号的识别,停止毫微微基站的唯一广告服务。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.843 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185966(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a division of Application No. 13/013,617, filed on Jan. 25, 2011, which claims the benefit of Korean Patent Application No. 10-2010-0055844, filed on Jun. 14, 2010, in the Korean Intellectual Property Office, the entire disclosures of which are incorporated herein by reference for all purposes. BACKGROUND [0002]1. Field [0003]The following description relates to a method of advertising to a mobile terminal connected to a femto base station, and a communication method of a mobile terminal, a femto base station, and a macro base station. [0004]2. Description of Related Art [0005]Femtocells may be classified into various types of femtocells, for example, a personal femtocell that may be used to provide an ultrahigh speed transmission service within a predetermined area, a commercial femtocell to provide an advertisement service for sales promotion of a shop, and an authorized femtocell to provide a location service. Most femtocell applications focus on a user's convenience but do not sufficiently consider benefits to various installers and administrators. [0006]In a personal femtocell, a femtocell installer and an administrator may be substantially the same as a service beneficiary, and therefore, various administrative rights need not be distinguished. However, in the commercial femtocell, there is a need to further distinguish the rights of a femtocell installer with that of a femtocell administrator in order to protect commercial rights. SUMMARY [0007]In one general aspect, there is provided a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in a macrocell set in a downlink broadcast channel of the macrocell, receiving position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal from the mobile terminal, when the mobile terminal identifies an accessible femto base station from among the at least one femto base station in the broadcast channel section, generating a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal. [0008]The method may further comprise transmitting connection information to enable the mobile terminal to access a femto base station selected by the mobile terminal from among the femto base stations in the list to the mobile terminal. [0009]The broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0010]The information about the neighbor femto base stations of the mobile terminal may comprise information about a shop in which each of the femto base stations is located or information about a discount policy of a connection service offered by each of the femto base stations. [0011]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a voice call transmitting signal transmitted from the mobile terminal, postponing transmission of the voice call transmitting signal, in response to the identification of the voice call transmitting signal, and offering a unique voice advertisement service of the femto base station, in response to the identification of the voice call transmitting signal. [0012]The method may further comprise identifying a ringback tone signal transmitted from a receiving side, and stopping the unique voice advertisement service of the femto base station in response to the identification of the ringback tone signal. [0013]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a data communication connection signal transmitted from the mobile terminal, postponing transmission of the data communication connection signal, in response to the identification of the data communication connection signal, and offering a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal. [0014]The method may further comprise identifying a data reception signal about a uniform resource locator (URL) address that the mobile terminal desires to access, and stopping the unique advertisement service of the femto base station, in response to the identification of the data reception signal. [0015]In another aspect, there is provided a communication method of a mobile terminal, the method comprising detecting a broadcast channel section used to identify a femtocell in a macrocell set in a downlink broadcast channel of the macrocell, identifying a femto base station which is accessible to the mobile terminal from among at least one femto base station in the macrocell based on a measurement of an intensity of a signal of the broadcast channel section, transmitting, to a macro base station, position information of the mobile terminal and a request for information about the accessible femto base station, receiving a list of neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal from the macro base station, and selecting a femto base station from among the neighbor femto base stations of the mobile terminal based on the list of the neighbor femto base stations and the information about the neighbor femto base stations. [0016]The detecting of the broadcast channel section to identify the femtocell in the macrocell may detect a broadcast channel section based on whether a femtocell exploration mode of the mobile terminal in the macrocell is set. [0017]The indentifying of the accessible femto base station may identify a femto base station which is accessible to the mobile terminal from among the at least one femto base station in the macrocell by comparing a preset threshold value with the measured intensity of the signal of the broadcast channel section. [0018]The selected femto base station may be selected based on preferences of a user of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal. [0019]The method may further comprise receiving connection information to enable access to the selected femto base station from among the femto base stations in the list from the macro base station. [0020]The broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0021]The information about the neighbor femto base stations of the mobile terminal may comprise information about a shop in which the femto base stations are located, respectively, or comprises information about a discount policy of a connection service offered by each respective femto base station. [0022]In another aspect, there is provided a communication method of a femto base station, the method comprising receiving, from a macro base station, a report about a broadcast channel section used to identify a femtocell in a macrocell of the macro base station set in a downlink broadcast channel in the macrocell, and setting a signal in the broadcast channel section to report that the existence of a femtocell of the femto base station is within the macrocell of the macro base station. [0023]In another aspect, there is provided a computer-readable storage medium having stored therein program instructions to cause a processor to execute a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in a macrocell set in a downlink broadcast channel of the macrocell, receiving position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal from the mobile terminal, when the mobile terminal identifies an accessible femto base station from among the at least one femto base station in the broadcast channel section, generating a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal. [0024]Other features and aspects may apparent from the following description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0025]FIG. 1 is a diagram illustrating an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0026]FIG. 2 is a diagram illustrating an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0027]FIG. 3 is a flowchart illustrating an example of a communication method of a macro base station. [0028]FIG. 4 is a flowchart illustrating an example of a communication method of a mobile terminal. [0029]FIG. 5 is a flowchart illustrating an example of a method of offering an advertisement to a mobile terminal connected to a femto base station. [0030]Throughout the drawings and the description, unless otherwise described, the same drawing reference numerals should be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience. DESCRIPTION [0031]The following description is provided to assist the reader in gaining a comprehensive understanding of the methods, apparatuses, and/or systems described herein. Accordingly, various changes, modifications, and equivalents of the methods, apparatuses, and/or systems described herein may be suggested to those of ordinary skill in the art. Also, description of well-known functions and constructions may be omitted for increased clarity and conciseness. [0032]As described herein, a macrocell refers to a coverage area of a macro base station, and a femtocell refers to a coverage area of a femto base station. [0033]FIG. 1 illustrates an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0034]Referring to FIG. 1, the network in which the mobile terminal identifies and connects to the neighbor femtocell includes a macro base station 101, two femto base stations 103, and a mobile terminal 105. It should be appreciated that the number of macro base stations, femto base stations, and mobile terminals are not limited to the example shown in FIG. 1. For example, the network may include one or more macro base stations, one or more femto base stations, and one or more mobile terminals. [0035]The macro base station coverage area includes a macrocell. The macro base station 101 sets up a broadcast channel section 109 to identify a femtocell within a downlink broadcast channel 107 of the macrocell of the macro base station 105. The macro base station 101 reports the broadcast channel section 109 to at least one femto base station 103 in the macrocell of the macro base station 105. [0036]For example, the macro base station 101 may be linked with the femto base station 103 positioned in the macrocell of the macro base station 105, and maintain and renew a database including connection information. The connection information may include, for example, information about linked femto base stations 103, information about shops in which the linked femto base stations 103 are located, information about the linked femto base stations 103 with the macro base station 101, and the like. [0037]For example, the macro base station 101 may renew the database at a time when a femto base station 103 is added to the macrocell of the macro base station 105, at a preset time, or at any other desired time. [0038]The femto base stations 103 may offer various services, for example, real-time advertisements and event announcements of shops to the mobile terminal 105 as the user of the mobile terminal is within the coverage area of the femto base stations or passing by the shops in which the femto base stations 103 are located. [0039]For example, the femto base stations 103 may be linked with the macro base station 101 to attract customers passing by the shops in which the femto base stations 103 are located. The femto base stations 103 may be synchronized with the macro base station 101 to be linked with the macro base station 101. [0040]The mobile terminal 105 may set a femtocell exploration mode of the mobile terminal 105 to automatically identify a femtocell. For example, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 in order to identify a femtocell in the macrocell and identify whether there is a neighbor femtocell. During femtocell exploration mode, the mobile terminal 105 may detect one or more femtocells corresponding to one or more femto base stations 103, which are within the macrocell of the macro base station 101 and which are available for the mobile terminal 105 to connect with. [0041]The mobile terminal 105 may select a femto base station 103 from among the one or more detected femto base stations 103 based on a user preference of the mobile terminal 105 and/or information about neighbor femto base stations 103 of the mobile terminal 105 received from the macro base station 101. Accordingly, the mobile terminal 105 may be provided with a unique advertisement service of the femto base station 103 while located within a femtocell of the femto base station 103. [0042]For example, the unique advertisement service of the femto base station 103 may include products sold by a shop in which the femto base station 103 is located, an advertisement for the shop, an advertisement service for an event held by the shop, and the like. [0043]As an example, when the shop in which the femto base station 103 is located is an ice cream shop, an advertisement service for the shop may include an advertisement for a new flavor of ice cream that may be purchased in the shop, discount information about products “on sale”, discount coupons, and the like. [0044]As described herein, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 to identify a femtocell of a femto base station 103 that is located within the macrocell of the macro base station 101, and be provided with the a unique advertisement service of the femto base station 103 from the femto base station 103. The mobile terminal 105 may be positioned in the same macrocell as the macro base station 101 and the femto base station 103. The downlink broadcast channel 107 of the macrocell may be used to identify a femtocell in the macrocell. [0045]The broadcast channel section 109 used to identify the femtocell in the macrocell set in the downlink broadcast channel 107 of the macrocell may be set at a preset cycle, for example, a cycle of a hundred milliseconds, two hundred milliseconds, five hundred milliseconds, or other desired amount of time. [0046]Hereinafter, a method including the macro base station 101, the femto base station 103, and the mobile terminal 105 in which the mobile terminal 105 identifies a neighbor femto base station 103 of the mobile terminal 105 and connect to the femto base station 103, is described. [0047]The macro base station 101 reports information about the broadcast channel section 109 to the femtocell corresponding to at least one femto cell 103 in the macrocell set in the downlink broadcast channel 107 of the macrocell, in 110. For example, the macro base station may report to one or more femto base stations 103 during 110. [0048]The femto base station 103 receiving a report about the broadcast channel section 109 from the macro base station 101 may set a signal in the broadcast channel section 109 in order to report the existence of the femtocell corresponding to the femto base station 103, in 120. [0049]For example, the broadcast channel section 109 of the downlink broadcast channel 107 may be set to a single bit or multiple bits. [0050]In 120, the femto base station 103 may set various types of signals in the broadcast channel section 109 to report the existence of the femtocell of the femto base station 103, for example, the femto base station 103 may set a particular bit of the broadcast channel section 109 to ‘1’ or set the broadcast channel section 109 to a dummy signal. [0051]When the femtocell exploration mode of the mobile terminal 105 is set to ON in 130, the mobile terminal 105 may detect the broadcast channel section 109 to that identify the femtocell corresponding to the a femto base station 103 is within the macrocell corresponding to the macro base station 101. [0052]The mobile terminal 105 may identify a femto base station 103 that is accessible to the mobile terminal 105 from among the at least one femto base station 103 that is within the macrocell of the macro base station, based on a measurement result of an intensity of the signal of the broadcast channel section 109, in 140. [0053]For example, when the measurement result of the intensity of the signal in the broadcast channel section 109 is higher than a preset threshold value, the mobile terminal 105 may identify that there is at least one femto base station 103 neighboring the mobile terminal 105 and which is accessible to the mobile terminal 105. As another example, based on the intensity of the signal the mobile terminal 105 may determine that a plurality of femto base stations are neighboring and available, for example, two femto base stations, three femto base stations, four femto base stations, or more femto base stations. [0054]For example, the femto base station 103 may set a signal in the broadcast channel section 109 in order to report the existence of the femtocell that corresponds to the femto base station 103 when receiving the report about the broadcast channel section 109 to identify the femtocell in the macrocell from the macro base station 101. [0055]The mobile terminal 105 may measure an intensity of the signal in the broadcast channel section 109 received from each neighbor femto base station 103 of the mobile terminal 105. The mobile terminal 105 may identify a femto base station 103 that is accessible to the mobile terminal 105 from among the at least one femto base station 103 in the macrocell based on the measured intensity. [0056]The mobile terminal 105 may transmit position information of the mobile terminal 105 to the macro base station 101, and may transmit a request for information about the femto base station 103 which is accessible to the mobile terminal 105 to the macro base station 101, in 150. [0057]For example, the macro base station 101 may generate a list of neighbor femto base stations 103 and information about the neighbor femto base stations 103 based on the position information of the mobile terminal 105 received from the mobile terminal 105, and may transmit the generated information to the mobile terminal 105, in 160. [0058]As an example, the information about the neighbor femto base stations 103 of the mobile terminal 105 may include information about a shop in which each of the respective femto base stations 103 is located or information about a discount policy of a connection service offered by each of the femto base stations 103. [0059]The mobile terminal 105 may select one femto base station 103 from among the neighbor femto base stations 103 of the mobile terminal 105 based on the list of the neighbor femto base stations 103 and the information about the neighbor femto base stations 103 received from the macro base station 101, in 170. [0060]In 170, the mobile terminal 105 may select the femto base station 103 in the list of the neighbor femto base stations 103 based on a user preference of the mobile terminal 105 and/or the information about the neighbor femto base stations 103 of the mobile terminal 105. [0061]An example of the list of the neighbor femto base stations 103 of the mobile terminal 105 received by the mobile terminal 105 from the macro base station 101 may include the following contents as shown in Table 1. TABLE 1Locationof BaseFemto baseBusinessTransmissionstationstation IDcategoryPolicy for usespeedaACosmeticsfreeLowaBClothing10 cents/minHighaCEntertainmentfreeMediumaDFast food5 cent/minHigh(free whenreceivingadvertisements) [0062]In this example, the mobile terminal 105 receives information about four femto base stations A, B, C, and D 103 neighboring the mobile terminal 105 from the macro base station 101. Accordingly, if a user of the mobile terminal 105 prefers a femto base station that provides a high transmittance speed and a free communication channel, the user of the mobile terminal 105 may select femto base station D to receive communication from. [0063]That is, the mobile terminal 105 may automatically select or a user of the mobile terminal 105 may select the femto base station D which satisfies all user preferences from among the femto base stations B and D that provide a high transmittance speed and a free communication channel from among the femto base stations A, B, C, and D in the list. [0064]For example, the mobile terminal 105 may use the communication channel provided by the selected femto base station D. Further, the mobile terminal 105 may be provided with information about a shop in which the femto base station D is located or information about a discount policy of a connection service offered by the femto base station D from the femto base station D. [0065]In this example, the femto base station D corresponds to a femto base station of a fast food restaurant. Accordingly, the mobile terminal 105 may be provided with information about a fast food restaurant in which the femto base station D is located, information about a sales event offered by the fast food restaurant, coupons for discounts offered by the fast food restaurant, and an advertisement for the sales event. [0066]As another example, the mobile terminal 105 may select a femto base station 103 based on the information about the neighbor femto base stations 103 of the mobile terminal 105. [0067]For example, the mobile terminal 105 may select a femto base station 103 corresponding to information in which a user of the mobile terminal 105 is interested in from among information about shops in which the respective femto base stations 103 in the list of the neighbor the femto base stations 103 of the mobile terminal 105 are located. [0068]As an example, the mobile terminal 105 may select a femto base station 103 located in a shop in the list of the neighbor femto base stations 103 of the mobile terminal 105, the shop offering a sales event, a shop providing a coupon of a product for a discount when receiving an advertisement service, and the like. [0069]As described above, the mobile terminal 105 may automatically select a femto base station 103 from the list of the neighbor femto base stations 103 of the mobile terminal 105 by various methods. Depending on the femto base station 103 selected, the user of the mobile terminal 105 may be provided with an advertisement service from the femto base station 103. [0070]Further, the mobile terminal 105 itself may provide the list of the neighbor femto base stations 103 of the mobile terminal 105 and information about events thereof to a user of the mobile terminal 105 when selecting a femto base station 103, thereby allowing the users to select a femto base station 103 themselves. [0071]As another example, a femto base station 103 may be automatically selected by the macro base station 101. In yet other embodiments, the femto base station 103 may be automatically selected by the mobile terminal 105 based on predetermined settings or dynamically adjusted settings that may be dynamically set by a user. As yet another example, the femto base station 103 may be selected by a user of the mobile terminal 105. [0072]As another example, the macro base station 101 may store a user preference of the mobile terminal 105 and the information about the neighbor femto base stations 103 of the mobile terminal 105 in advance, and selectively provide a femto base station 103 that satisfies the user preference based on stored information. [0073]For example, the macro base station 101 may include a database of information about the user preference of the mobile terminal 105 shown in the following Table 2. TABLE 2MobileterminalAgePolicy forTransmissionInterestedIDgroupsusespeedbusiness categoryOthersA20sFreeMediumCommunicationSelecting free ofterminals, gamescharge whenreceivingadvertisementsB30sFree/chargedHighRestaurantsHigh transmissionspeedC40sFreeMediumSports, bookReceiving sports-storesrelatedadvertisements [0074]The macro base station 101 may select a femto base station 103 which corresponds to the user preferences of the mobile terminal 105 shown in Table 2 from among the information about the neighbor femto base stations 103 of the mobile terminal 105 and provide the femto base station 103 to the mobile terminal 105. [0075]The macro base station 101 may transmit connection information to the mobile terminal 105 to enable an access to the selected femto base station 103 in the list of the femto base stations 103, in 180. [0076]The mobile terminal 105 may connect to the selected femto base station 103 using the connection information received from the macro base station 101, in 190. [0077]Accordingly, the mobile terminal 105 connected to the femto base station 103 may be provided with various communication services and advertisement services offered by the femto base station 103. [0078]For example, the advertisement services may include a unique voice advertisement service of the femto base station 103 and a unique display advertisement service of the femto base station 103. For example, the unique voice advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 inputs a telephone number and waits for a call to connect. [0079]As described herein, the unique advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 waits for data reception about a uniform resource locator (URL) address which the mobile terminal 105 desires to access. [0080]FIG. 2 illustrates an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0081]Referring to FIG. 2, the network for providing the advertisement to the mobile terminal includes a counterpart exchange station 201, a femto base station 203, a mobile terminal 205, and a receiving side mobile terminal 207. [0082]For example, a user in control of the mobile terminal 205 passing by a shop in which the femto base station 203 is located may attempt to call a friend by entering the phone number of a friend that corresponds to the receiving side mobile terminal 207, to try a call, in 210. [0083]In response to the call being placed by the user of the mobile terminal 205, the femto base station 203 identifies a voice call transmitting signal transmitted from the mobile terminal 205 based on the call being placed. Accordingly, the femto base station 203 may provide an advertisement to the mobile terminal 205 connected to the femto base station 203, and postpone transmission of the voice call transmitting signal in response to the identification of the voice call transmitting signal, in 220. [0084]For example, the femto base station 203 may include a voice call transmitting signal identification module that may identify the voice call transmitting signal transmitted from the mobile terminal 205. The femto base station 203 may offer a unique voice advertisement service of the femto base station 203 to the mobile terminal 205 in response to the identification of the voice call transmitting signal, in 230. [0085]The femto base station 203 forwards the postponed voice call transmitting signal to the counterpart exchange station 201, in 240. For example, the femto base station 203 may forward the postponed voice call transmitting signal after a predetermined amount of time elapses. [0086]For example, the femto base station 203 may identify a ringback tone signal transmitted from the receiving side mobile terminal 207, and accordingly, the femto base station 203 stops the unique voice advertisement service of the femto base station 203 in response to the identification of the ringback tone signal, in 250. [0087]After stopping the unique voice advertisement service of the femto base station 203, the femto base station 203 may forward the ringback tone signal to the mobile terminal 205 to connect a voice call, in 260. [0088]FIG. 3 illustrates an example of a communication method of a macro base station. [0089]Referring to FIG. 3, the macro base station reports information about a broadcast channel section to at least one femto base station to identify a femtocell corresponding to a femto base station in the macrocell corresponding to the macro base station set in a downlink broadcast channel of the macrocell, in 310. For example, the broadcast channel may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0090]The macro base station receives position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, in 320. For example, the position information and the request for information may be transmitted from the mobile terminal. For example, when the mobile terminal identifies an accessible femto base station from among the at least one femto base station in the broadcast channel section, the mobile terminal may transmit the information to the macro base station. [0091]For example, the information about the neighbor femto base stations of the mobile terminal may include information about a shop in which each of the femto base stations is located. As another example, the information may include information about a discount policy of a connection service offered by each of the femto base stations. [0092]The macro base station generates a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, in 330. [0093]The macro base station transmits the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal, in 340. [0094]In 350, the macro base station may transmit connection information to enable the mobile terminal access to a femto base station. [0095]The connection information to enable the mobile terminal access to the femto base station may be information about a femto base station selected by the mobile terminal from among the neighbor femto base stations of the mobile terminal in the list. [0096]FIG. 4 illustrates an example of a communication method of a mobile terminal. [0097]Referring to FIG. 4, the mobile terminal may determine whether a femtocell exploration mode of the mobile terminal in a macrocell is set to ‘ON’, in 410. [0098]When the femtocell exploration mode is set to ‘ON,’ the mobile terminal detects a broadcast channel section to identify a femtocell that the macrocell set in a downlink broadcast channel of the macrocell, in 420. For example, the broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0099]As a result of the determination in 410, if the femtocell exploration mode is not set to ‘ON,’ or the mobile terminal does not have a femtocell exploration function, the mobile terminal may finish the process without performing subsequent operations to 410. [0100]The mobile terminal identifies a f(String), 相关申请的交叉引用 [0001] 本申请是 2011 年 1 月 25 日提交的申请号 13/013,617 的分案,该申请要求韩国知识产权局于 2010 年 6 月 14 日提交的韩国专利申请号 10-2010-0055844 的权益 Office,其全部公开内容出于所有目的通过引用并入本文。 背景 [0002] 1. 领域 [0003] 以下描述涉及向连接到毫微微基站的移动终端进行广告的方法,以及移动终端、毫微微基站和宏基站的通信方法。 [0004] 2.相关技术说明 [0005] Femtocell可以分为各种类型的femtocell,例如,可以用于在预定区域内提供超高速传输服务的个人femtocell,用于为商店的促销提供广告服务的商业femtocell,以及授权的femtocell。 femtocell 提供定位服务。 大多数毫微微蜂窝应用关注用户的便利性,但没有充分考虑对各种安装人员和管理员的好处。 [0006] 在个人femtocell中,femtocell安装者和管理员可以作为服务受益人基本相同,因此不需要区分各种管理权限。 然而,在商用毫微微基站中,需要进一步区分毫微微基站安装者和毫微微基站管理员的权利,以保护商业权利。 概括 [0007] 在一个一般方面,提供了一种宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告关于用于识别毫微微小区中的毫微微小区的广播信道部分的信息。 宏小区设置在宏小区的下行广播信道中,当移动终端识别出可接入的毫微微基站时,从移动终端接收移动终端的位置信息和对移动终端的相邻毫微微基站的信息的请求 广播信道部分中的至少一个毫微微基站,基于移动终端的位置信息生成移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息,并发送 移动终端的相邻femto基站列表和有关相邻femt的信息 o 移动终端的基站到移动终端。 [0008] 该方法还可以包括向移动终端发送连接信息以使移动终端能够接入由移动终端从列表中的毫微微基站中选择的毫微微基站。 [0009] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0010] 关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于每个毫微微基站提供的连接服务的折扣政策的信息。 [0011] 在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的语音呼叫发送信号,作为响应推迟语音呼叫发送信号的发送 对语音呼叫发送信号的识别,并响应语音呼叫发送信号的识别,提供毫微微基站的独特语音广告服务。 [0012] 该方法还可以包括识别从接收侧发送的回铃音信号,并且响应于回铃音信号的识别停止毫微微基站的唯一语音广告服务。 [0013]在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的数据通信连接信号,作为响应推迟数据通信连接信号的发送 对数据通信连接信号的识别进行响应,并响应于数据通信连接信号的识别,向移动终端提供毫微微基站的唯一广告服务。 [0014] 该方法还可以包括识别关于移动终端期望访问的统一资源定位符(URL)地址的数据接收信号,并且响应于数据接收信号的识别停止毫微微基站的唯一广告服务。 [0015] 在另一方面,提供了一种移动终端的通信方法,该方法包括:检测用于在宏小区的下行链路广播信道中设置的宏小区中识别毫微微小区的广播信道部分,识别可接入的毫微微基站。 来自宏小区中的至少一个毫微微基站中的移动终端基于对广播信道部分的信号强度的测量,向宏基站发送移动终端的位置信息和对有关信息的请求 可接入的毫微微基站,从宏基站接收移动终端的相邻毫微微基站列表和关于移动终端的相邻毫微微基站的信息,并从相邻毫微微基站中选择毫微微基站 移动终端基于相邻毫微微基站列表和有关相邻毫微微基站的信息 车站。 [0016] 检测广播信道区间以识别宏小区中的毫微微小区可以基于是否设置了移动终端在宏小区中的毫微微小区探索模式来检测广播信道区间。 [0017] 可接入毫微微基站的识别可以通过将预设阈值与所测量的广播信道的信号强度进行比较,从宏小区中的至少一个毫微微基站中识别出移动终端可接入的毫微微基站。 部分。 [0018] 可以基于移动终端的用户的偏好和关于移动终端的相邻毫微微基站的信息来选择所选择的毫微微基站。 [0019] 该方法还可以包括从宏基站接收连接信息以使得能够从列表中的毫微微基站中接入所选择的毫微微基站。 [0020] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0021] 移动终端的相邻毫微微基站的信息可以包括毫微微基站所在店铺的信息,或者包括各个毫微微基站提供的连接服务的折扣政策的信息。 [0022] 在另一方面,提供了一种毫微微基站的通信方法,该方法包括从宏基站接收关于用于识别设置在宏基站的宏小区中的毫微微小区的广播信道部分的报告。 宏小区中的下行广播信道,并在广播信道部分设置信号以报告在宏基站的宏小区内存在毫微微基站的毫微微小区。 [0023]在另一方面,提供了一种其中存储有程序指令的计算机可读存储介质,以使处理器执行宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告。 宏基站,关于用于识别宏小区下行广播信道中设置的宏小区中的毫微微小区的广播信道部分的信息,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求。 移动终端,当移动终端从广播信道部分的至少一个毫微微基站中识别出可接入的毫微微基站时,生成移动终端的相邻毫微微基站的列表和关于相邻毫微微基站的信息 移动终端根据移动终端的位置信息,发送l 移动终端的相邻毫微微基站的列表以及移动终端的相邻毫微微基站的信息给移动终端。 [0024] 从以下描述、附图和权利要求中,其他特征和方面可能是显而易见的。 附图的简要说明 [0025] 图1是图示允许移动终端识别并连接到相邻毫微微小区的网络的示例的图。 [0026] 图2是图示允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例的图。 [0027] 图3是图示宏基站的通信方法的示例的流程图。 [0028] 图4是图示移动终端的通信方法的示例的流程图。 [0029] 图5是图示向连接到毫微微基站的移动终端提供广告的方法的示例的流程图。 [0030] 在整个附图和描述中,除非另有说明,相同的附图标记应被理解为指代相同的元件、特征和结构。 为了清楚、说明和方便起见,这些元素的相对大小和描述可能会被夸大。 描述 [0031] 提供以下描述以帮助读者获得对本文描述的方法、装置和/或系统的全面理解。 因此,可以向本领域普通技术人员建议本文描述的方法、装置和/或系统的各种改变、修改和等效物。 此外,为了更清楚和简明,可以省略对众所周知的功能和结构的描述。 [0032] 如本文所述,宏小区是指宏基站的覆盖区域,毫微微小区是指毫微微基站的覆盖区域。 [0033] 图1图示了允许移动终端识别并连接到相邻毫微微小区的网络的示例。 [0034] 参考图1,移动终端识别并连接到相邻毫微微小区的网络包括宏基站 101 , 两个毫微微基站 103 , 和一个移动终端 105 . 应当理解,宏基站、毫微微基站和移动终端的数量不限于图1所示的示例。例如,网络可以包括一个或多个宏基站、一个或多个毫微微基站 ,以及一个或多个移动终端。 [0035] 宏基站覆盖区域包括宏小区。 宏基站 101 设置广播频道部分 109 识别下行广播信道内的毫微微小区 107 宏基站的宏小区 105 . 宏基站 101 报告广播频道部分 109 到至少一个毫微微基站 103 在宏基站的宏小区中 105 . [0036] 例如宏基站 101 可与毫微微基站链接 103 位于宏基站的宏小区 105,并维护和更新包括连接信息的数据库。 连接信息可以包括例如关于链接的毫微微基站的信息 103 ,有关链接的毫微微基站的商店的信息 103 定位,有关链接的毫微微基站的信息 103 与宏基站 101 ,等等。 [0037] 例如宏基站 101 可以在毫微微基站更新数据库时 103 加入宏基站的宏小区 105 ,在预设时间,或在任何其他所需时间。 [0038] 毫微微基站 103 可以向移动终端提供各种服务,例如商店的实时广告和活动公告 105 当移动终端的用户在毫微微基站的覆盖范围内或经过毫微微基站所在的商店时 103 位于。 [0039] 例如,毫微微基站 103 可与宏基站联动 101 吸引经过femto基站所在商店的顾客 103 位于。 毫微微基站 103 可与宏基站同步 101 与宏基站联动 101 . [0040] 移动终端 105 可以设置移动终端的femtocell探索模式 105 自动识别毫微微蜂窝基站。 例如,当移动终端的femtocell探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 以识别宏小区中的毫微微小区,并识别是否有相邻毫微微小区。 在femtocell探索模式下,移动终端 105 可以检测对应于一个或多个毫微微基站的一个或多个毫微微小区 103 ,在宏基站的宏小区内 101 哪些可用于移动端 105 连接。 [0041] 移动终端 105 可以选择一个毫微微基站 103 从一个或多个检测到的毫微微基站中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 移动终端的 105 从宏基站接收 101 . 因此,移动终端 105 可以提供femto基站的独特广告服务 103 当位于毫微微基站的毫微微小区内时 103 . [0042] 例如,femto 基站的独特广告服务 103 可能包括由 Femto 基站所在的商店销售的产品 103 定位,商店的广告,商店举办的活动的广告服务等。 [0043] 例如,当 femto 基站所在的商店 103 如果位于冰淇淋店,则该店的广告服务可以包括可在该店购买的新口味冰淇淋的广告、“特价”产品的折扣信息、折扣券等。 [0044] 如本文所述,当移动终端的毫微微小区探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 识别毫微微基站的毫微微小区 103 位于宏基站的宏小区内 101 ,并获得femto基站独有的广告服务 103 从毫微微基站 103 . 移动终端 105 可以与宏基站位于同一宏小区中 101 和毫微微基站 103 . 下行广播信道 107 宏小区的名称可以用于识别宏小区中的毫微微小区。 [0045] 广播频道部分 109 用于识别下行广播信道中宏小区集合中的毫微微小区 107宏小区的时间周期可以设置为预设的周期,例如一百毫秒、两百毫秒、五百毫秒的周期,或者其他期望的时间量。 [0046] 在下文中,一种包括宏基站的方法 101 , 毫微微基站 103 , 和移动终端 105 其中移动端 105 识别相邻的毫微微基站 103 移动终端的 105 并连接到 femto 基站 103 , 被描述。 [0047] 宏基站 101 报告有关广播频道部分的信息 109 到对应于至少一个毫微微小区的毫微微小区 103 在下行广播信道中设置的宏小区中 107 宏蜂窝,在 110 . 例如,宏基站可以向一个或多个毫微微基站报告 103 期间 110 . [0048] 毫微微基站 103 接收有关广播频道部分的报告 109 从宏基站 101 可以在广播频道部分设置信号 109 为了上报femto基站对应的femtocell的存在 103 , 在 120 . [0049] 例如,广播频道部分 109 下行广播信道 107 可以设置为单个位或多个位。 [0050] 在 120 , 毫微微基站 103 可以在广播频道部分设置各种类型的信号 109 报告femto基站的femtocell存在 103 ,例如,毫微微基站 103 可以设置广播频道部分的特定位 109 为“1”或设置广播频道部分 109 到一个虚拟信号。 [0051] 当移动终端的femtocell探索模式 105 在设置为 ON 130 , 移动端 105 可以检测广播频道部分 109 以识别对应于一个毫微微基站的毫微微小区 103 在宏基站对应的宏小区内 101 . [0052] 移动终端 105 可以识别毫微微基站 103 移动终端可以访问的 105 从至少一个毫微微基站中 103 在宏基站的宏小区内,基于广播信道部分的信号强度的测量结果 109 , 在 140 . [0053] 例如,当广播频道部分的信号强度测量结果 109 高于预设阈值,移动终端 105 可以识别存在至少一个毫微微基站 103 靠近移动终端 105 移动终端可以访问的 105 . 作为另一个示例,基于信号的强度,移动终端 105 可以确定多个毫微微基站相邻且可用,例如,两个毫微微基站、三个毫微微基站、四个毫微微基站或更多毫微微基站。 [0054] 例如,毫微微基站 103 可以在广播频道部分设置信号 109 为了上报femto基站对应的femtocell的存在 103 收到有关广播频道部分的报告时 109 从宏基站识别宏小区中的毫微微小区 101 . [0055] 移动终端 105 可以测量广播频道部分的信号强度 109 从每个相邻毫微微基站接收 103 移动终端的 105 . 移动终端 105 可以识别毫微微基站 103 移动终端可以访问的 105 从至少一个毫微微基站中 103 在基于测量强度的宏单元中。 [0056] 移动终端 105 可以发送移动终端的位置信息 105 到宏基站101 ,并且可以发送对关于毫微微基站的信息的请求 103 移动终端可以访问的 105 到宏基站 101 , 在 150 . [0057] 例如宏基站 101 可以生成相邻毫微微基站的列表 103 以及有关相邻毫微微基站的信息 103 基于移动终端的位置信息 105 从移动终端接收 105 ,并且可以将生成的信息发送到移动终端 105 , 在 160 . [0058] 例如,有关相邻毫微微基站的信息 103 移动终端的 105 可以包括关于商店的信息,其中每个相应的毫微微基站 103 位置或有关每个毫微微基站提供的连接服务的折扣政策的信息 103 . [0059] 移动终端 105 可选择一个毫微微基站 103 从相邻的毫微微基站中 103 移动终端的 105 基于相邻毫微微基站列表 103 以及有关相邻毫微微基站的信息 103 从宏基站接收 101 , 在 170 . [0060] 在 170 , 移动端 105 可选择femto基站 103 在相邻毫微微基站列表中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 移动终端的 105 . [0061] 相邻毫微微基站列表的示例 103 移动终端的 105 由移动终端接收 105 从宏基站 101 可包括以下内容,如表 1 所示。 表格1 地点 基地 毫微微基站 商业 传播 车站 站号 类别 使用政策 速度 a A 化妆品 自由的 低的 a B 衣服 10 美分/分钟 高的 a C 娱乐 自由的 中等的 a D 快餐 5 分/分钟 高的 (免费时 接收 广告) [0062] 在这个例子中,移动终端 105 接收有关四个毫微微基站 A、B、C 和 D 的信息 103 靠近移动终端 105 从宏基站 101 . 因此,如果移动终端的用户 105 移动终端的用户更喜欢提供高传输速度和免费通信信道的毫微微基站 105 可以选择毫微微基站D来接收通信。 [0063] 也就是移动终端 105 可自动选择或移动终端的用户 105 可以从列表中的毫微微基站A、B、C和D中提供高传输速度和空闲通信信道的毫微微基站B和D中选择满足所有用户偏好的毫微微基站D。 [0064] 例如,移动终端 105 可以使用由选择的毫微微基站D提供的通信信道。此外,移动终端 105 可以提供关于毫微微基站D所在的商店的信息或者关于毫微微基站D从毫微微基站D提供的连接服务的折扣政策的信息。 [0065] 在该示例中,毫微微基站D对应于快餐店的毫微微基站。 因此,移动终端 105 可以提供关于毫微微基站D所在的快餐店的信息、关于快餐店提供的销售活动的信息、快餐店提供的折扣券以及销售活动的广告。 [0066] 再举一个例子,移动终端 105 可以选择一个毫微微基站 103 基于有关相邻毫微微基站的信息 103 移动终端的 105 . [0067] 例如,移动终端 105 可以选择一个毫微微基站 103 对应于移动终端用户的信息 105 从有关各个femto基站所在商店的信息中感兴趣 103在邻居列表中的毫微微基站 103 移动终端的 105 位于。 [0068] 以移动终端为例 105 可以选择一个毫微微基站 103 位于相邻毫微微基站列表中的商店中 103 移动终端的 105 、提供销售活动的商店、在接收广告服务时提供产品优惠券以获得折扣的商店等。 [0069] 如上所述,移动终端 105 可以自动选择一个毫微微基站 103 从相邻毫微微基站列表中 103 移动终端的 105 通过各种方法。 取决于毫微微基站 103 选中,移动端的用户 105 可以从毫微微基站提供广告服务 103 . [0070] 此外,移动终端 105 本身可以提供相邻毫微微基站的列表 103 移动终端的 105 以及关于其事件的信息给移动终端的用户 105 选择毫微微基站时 103 ,从而允许用户选择一个毫微微基站 103 他们自己。 [0071] 作为另一个示例,毫微微基站 103 可由宏基站自动选择 101 . 在又一些实施例中,毫微微基站 103 可由移动端自动选择 105 基于可以由用户动态设置的预定设置或动态调整的设置。 作为又一示例,毫微微基站 103 可由移动终端的用户选择 105 . [0072] 再举一个例子,宏基站 101 可以存储移动终端的用户偏好 105 以及有关相邻毫微微基站的信息 103 移动终端的 105 提前,并有选择地提供一个毫微微基站 103 根据存储的信息满足用户偏好。 [0073] 例如宏基站 101 可以包括关于移动终端的用户偏好的信息数据库 105 如下表2所示。 表 2 移动的 终端 年龄 政策 传播 感兴趣的 ID 团体 利用 速度 业务类别 其他 A 20s 自由的 中等的 沟通 选择免费的 终端、游戏 什么时候收费 接收 广告 B 30s 免费/收费 高的 餐厅 高传输 速度 C 40s 自由的 中等的 运动、书籍 接受运动—— 商店 有关的 广告 [0074] 宏基站 101 可以选择一个毫微微基站 103 对应移动终端的用户偏好 105 从有关相邻毫微微基站的信息中显示在表2中 103 移动终端的 105 并提供femto基站 103 到移动终端 105 . [0075] 宏基站 101 可以向移动终端发送连接信息 105 启用对所选毫微微基站的访问 103 在 femto 基站列表中 103 , 在 180 . [0076] 移动终端 105 可以连接到选定的毫微微基站 103 使用从宏基站接收到的连接信息 101 , 在 190 . [0077] 因此,移动终端 105 连接到毫微微基站 103 可以提供由毫微微基站提供的各种通信服务和广告服务 103 . [0078] 例如,广告服务可以包括毫微微基站的独特语音广告服务 103 以及femto基站独有的展示广告服务 103 . 例如,femto基站独有的语音广告服务 103 可提供给移动终端 105 而移动端 105 输入电话号码并等待呼叫接通。 [0079] 如本文所述,毫微微基站的独特广告服务 103 可提供给移动终端 105 而移动端 105 等待关于移动终端的统一资源定位符(URL)地址的数据接收 105 渴望访问。 [0080] 图2图示了允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例。 [0081] 参考图2,用于向移动终端提供广告的网络包括对方交换站 201 , 一个毫微微基站 203 , 移动终端 205 ,以及接收方移动终端 207 . [0082] 例如,控制移动终端的用户 205 路过一家有femto基站的商店 203 定位到可以尝试通过输入与接收方移动终端对应的朋友的电话号码来呼叫朋友 207 , 尝试通话,在 210 . [0083] 响应移动终端用户的呼叫 205 , 毫微微基站 203 识别移动终端发送的语音呼叫发送信号 205 根据正在拨打的电话。 因此,毫微微基站 203 可以向移动终端提供广告 205 连接到毫微微基站 203 ,并且响应于语音呼叫发射信号的识别延迟语音呼叫发射信号的传输,在 220 . [0084] 例如,毫微微基站 203 可以包括语音呼叫发送信号识别模块,其可以识别从移动终端发送的语音呼叫发送信号 205 . 毫微微基站 203 可以提供femto基站独特的语音广告服务 203 到移动终端 205 响应语音呼叫发射信号的识别,在 230 . [0085] 毫微微基站 203 将延迟的语音呼叫发射信号转发给对方交换台 201 , 在 240 . 例如,毫微微基站 203 可以在经过预定时间量之后转发延迟的语音呼叫发送信号。 [0086] 例如,毫微微基站 203 可以识别从接收侧移动终端发送的回铃音信号 207 ,因此,毫微微基站 203 停止femto基站独有的语音广告服务 203 响应回铃音信号的识别,在 250 . [0087] 停止femto基站的独特语音广告服务后 203 , 毫微微基站 203 可以将回铃音信号转发给移动终端 205 连接语音通话,在 260 . [0088] 图3图示了宏基站的通信方法的示例。 [0089] 参考图3,宏基站向至少一个毫微微基站报告关于广播信道部分的信息,以识别与在该宏基站的下行链路广播信道中设置的宏基站对应的宏小区中的毫微微基站对应的毫微微小区。 宏单元,在 310 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道。 [0090] 宏基站接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,在 320 . 例如,可以从移动终端发送位置信息和信息请求。 例如,当移动终端从广播信道部分中的至少一个毫微微基站中识别出可访问的毫微微基站时,移动终端可以将该信息发送到宏基站。 [0091] 例如,关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息。 作为另一示例,该信息可以包括关于由每个毫微微基站提供的连接服务的折扣策略的信息。 [0092]宏基站根据移动终端的位置信息生成移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息,在 330 . [0093] 宏基站将移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息发送给移动终端,在 340 . [0094] 在 350 ,宏基站可以发送连接信息以使移动终端能够接入毫微微基站。 [0095] 使移动终端能够接入毫微微基站的连接信息可以是关于移动终端从列表中的移动终端的相邻毫微微基站中选择的毫微微基站的信息。 [0096] 图4图示了移动终端的通信方法的示例。 [0097] 参考图4,移动终端可以确定移动终端在宏小区中的毫微微小区探索模式是否设置为“ON”,在 410 . [0098] 当毫微微小区探索模式设置为“开启”时,移动终端检测广播信道部分以识别宏小区在宏小区的下行链路广播信道中设置的毫微微小区,在 420 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道段。 [0099] 作为确定的结果 410 ,如果femtocell探索模式未设置为“ON”,或者移动终端不具备femtocell探索功能,则移动终端可以不执行后续操作就完成该过程 410 . [0100] 移动终端基于广播信道部分的信号强度的测量从宏小区中的至少一个毫微微基站中识别移动终端可接入的毫微微基站,以便识别宏小区中的毫微微小区 . [0101] 也就是说,移动终端可以测量广播信道部分的信号强度以识别毫微微小区,并将测量结果与预设阈值进行比较,在 440 . [0102] 当测量的广播频道部分的信号强度 440 高于预设阈值时,移动终端可以从宏小区中的至少一个毫微微基站中识别出该毫微微基站是移动终端可接入的,在 450 . [0103] 移动终端向宏基站发送移动终端的位置信息和对关于可接入毫微微基站的信息的请求,在 460 . 移动终端接收来自宏基站的请求信息,在 470 . [0104] 例如,从宏基站接收的信息可以包括移动终端的相邻毫微微基站的列表和关于移动终端的相邻毫微微基站的信息。 例如,可以基于移动终端的位置信息来生成列表和信息。 [0105] 作为示例,关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于由每个毫微微基站提供的连接服务的折扣政策的信息。 车站。 [0106] 移动终端可以基于相邻毫微微基站的列表和关于相邻毫微微基站的信息,从移动终端的相邻毫微微基站中选择毫微微基站,在 480 . [0107] 例如,移动终端可以使用移动终端的用户的偏好和关于移动终端的相邻毫微微基站的信息来选择毫微微基站。 [0108] 图5图示了向连接到毫微微基站的移动终端提供广告的方法的示例。 [0109]参考图5,当移动终端输入诸如移动终端希望访问的URL地址的数据通信连接信号时,毫微微基站识别从移动终端发送的数据通信连接信号,在 510 . [0110] 毫微微基站响应于数据通信连接信号的识别延迟数据通信连接信号的传输,在 520 . [0111] 毫微微基站响应数据通信连接信号的识别,向移动终端提供独特的毫微微基站广告服务,在 530 . 例如,在经过预定量的时间之后,毫微微基站可以将延迟的数据通信连接信号转发到运行中的互联网服务器。 [0112] 在 540 ,毫微微基站识别关于移动终端希望访问的URL地址的数据接收信号。 例如,毫微微基站可以包括识别数据接收信号的功能模块,例如移动终端期望的主页或URL地址,以便识别数据接收信号。 [0113] 毫微微基站可以响应关于移动终端希望访问的URL地址的数据接收信号的识别,停止毫微微基站的唯一广告服务,在 550 . 毫微微基站可以将关于移动终端期望访问的URL地址的数据接收信号转发给移动终端以连接语音呼叫。 [0114] 如本文所述,移动终端可以包括各种模式,例如毫微微小区探索模式。 然而,应该理解,移动终端可能只有一种模式,其中移动终端不断地搜索可用的毫微微小区。 [0115] 仅作为非穷举说明,此处描述的终端设备可以指移动设备,例如蜂窝电话、个人数字助理(PDA)、数码相机、便携式游戏机、MP3播放器、便携式/个人多媒体 播放器 (PMP)、手持电子书、便携式实验室个人计算机 (PC)、全球定位系统 (GPS) 导航,以及台式 PC、高清电视 (HDTV)、光盘等设备 播放器、设置盒等,能够进行与本文所公开的一致的无线通信或网络通信。 [0116] 计算系统或计算机可以包括与总线、用户接口和存储器控制器电连接的微处理器。 它还可以包括闪存设备。 闪存设备可以通过存储控制器存储N位数据。 N位数据由微处理器处理或将由微处理器处理,N可以为1或大于1的整数。当计算系统或计算机为移动设备时,可额外提供电池以提供计算的工作电压 系统或计算机。 [0117] 对于本领域的普通技术人员来说,计算系统或计算机还可以包括应用芯片组、相机图像处理器(CIS)、移动动态随机存取存储器(DRAM)等应该是显而易见的。 存储器控制器和闪存设备可以构成使用非易失性存储器来存储数据的固态驱动器/磁盘(SSD)。 [0118]上述过程、功能、方法和/或软件可以被记录、存储或固定在一个或多个计算机可读存储介质中,该存储介质包括要由计算机实现以使处理器执行或执行程序的程序指令 指示。 媒体还可以单独或与程序指令、数据文件、数据结构等组合地包括。 计算机可读存储介质的示例包括诸如硬盘、软盘和磁带之类的磁介质; 光媒体,如 CD ROM 盘和 DVD; 磁光介质,例如光盘; 以及专门用于存储和执行程序指令的硬件设备,例如只读存储器(ROM)、随机存取存储器(RAM)、闪存等。 程序指令的示例包括机器代码(例如由编译器生成)和包含可由计算机使用解释器执行的更高级别代码的文件。 所描述的硬件设备可以被配置为充当一个或多个软件模块以执行上述操作和方法,反之亦然。 此外,计算机可读存储介质可以分布在通过网络连接的计算机系统之间,并且可以以分散方式存储和执行非暂时性计算机可读代码或程序指令。 [0119] 上面已经描述了许多示例。 然而,应该理解可以进行各种修改。 例如,如果以不同的顺序执行所描述的技术和/或如果所描述的系统、架构、设备或电路中的组件以不同的方式组合和/或由其他组件替换或补充或 他们的等价物。 因此,其他实施方式在所附权利要求的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:41.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.065 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20130346212A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271654(Integer), KR101622169B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271654(Integer), KR1020110136068A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271654(Integer), US20110306324A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271654(Integer), US20130346212A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271654(Integer), US8548504B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271654(Integer), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20130346212A1(String), US20130346212A1(String), 1387987200(Integer), 271654(Integer), 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), JANG, KYUNG HUN(String), KWON, TAE SOO(String), CHOI, HYUN HO(String), LIM, JONG BU(String), SHIN, WON JAE(String), 三星电子株式会社(String), JANG KYUNG HUN(String), KWON TAE SOO(String), CHOI HYUN HO(String), LIM JONG BU(String), SHIN WON JAE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185966(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.496 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185966(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: JANG, KYUNG HUN(String), JANG KYUNG HUN(String), 0(Integer), 1681976082(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: KWON, TAE SOO(String), KWON TAE SOO(String), 0(Integer), 1681976082(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: CHOI, HYUN HO(String), CHOI HYUN HO(String), 0(Integer), 1681976082(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIM, JONG BU(String), LIM JONG BU(String), 0(Integer), 1681976082(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHIN, WON JAE(String), SHIN WON JAE(String), 0(Integer), 1681976082(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185966(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75838(Integer), 2(Integer), 185966(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75839(Integer), 2(Integer), 185966(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75840(Integer), 2(Integer), 185966(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75841(Integer), 2(Integer), 185966(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75842(Integer), 2(Integer), 185966(Integer), 4(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.917 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.918 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.918 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.953 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75838(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:42.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185966(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10775896B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 根据与移动终端操作相关的输入来控制多个对象显示的方法及其移动终端(String), US10775896B2(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US16/227823(String), 1545235200(Integer), US10775896B2(String), 1600099200(Integer), 1600099200(Integer), 美国(String), 4(Integer), KR(String), 17(Integer), 113(Integer), CN102736849A | JP1456713S | JP1976007453A | JP2003345492A | JP2004240757A | JP2004254281A | JP2006055398A | JP2006513487A | JP2007094378A | JP2007511851A | JP2007538203A | JP2008247873A | JP2008268689A | JP2009122093A | JP2011007701A | JP2011028677A | JP2012038292A | JP2012118652A | JP2012138892A | JP2012150205A | JP2012217677A | JP2012230572A | JP2012243091A | JP2012509544A | JP2012521595A | JP2012533751A | JP2013174279A | JP2013245447A | JP2014003854A | JP2014069285A | JP2014082404A | JP2014215737A | JP2015061605A | JP5107453B1 | JPWO2005112336A1 | JPWO2011125790A1 | KR1020050086960A | KR1020050086963A | KR1020110016194A | KR1020120071468A | KR1020120129697A | RU2011110239A | RU2455679C2 | US20050108655A1 | US20060053385A1 | US20060101352A1 | US20080250312A1 | US20080282202A1 | US20090046075A1 | US20090051648A1 | US20090106694A1 | US20090197635A1 | US20090327272A1 | US20100060599A1 | US20100070926A1 | US20100125811A1 | US20100125816A1 | US20100134312A1 | US20100164992A1 | US20100217685A1 | US20100248788A1 | US20100281374A1 | US20110016423A1 | US20110041101A1 | US20110175930A1 | US20110281633A1 | US20110312349A1 | US20120030569A1 | US20120032901A1 | US20120154294A1 | US20120162261A1 | US20120166997A1 | US20120190407A1 | US20120192121A1 | US20120200513A1 | US20120246586A1 | US20120264512A1 | US20120274541A1 | US20120299847A1 | US20130120295A1 | US20130120447A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130191784A1 | US20130219277A1 | US20130278484A1 | US20140035946A1 | US20140059472A1 | US20140101610A1 | US20140115493A1 | US20140139637A1 | US20140143737A1 | US20140149903A1 | US20140152597A1 | US20140181751A1 | US20140189601A1 | US20140215310A1 | US20150077333A1 | US8191011B2 | WO2008117827A1 | WO2010117827A2 | WO2012061917A1 | WO2012066591A1 | WO2012083277A2 | WO2012108620A2 | WO2012159268A1 | WO2012169190A1(String), 21(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.612 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185967(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c612d573547d44be86f06686cdfafb2d.png(String), 185967(Integer), c612d573547d44be86f06686cdfafb2d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for controlling display of multiple objects depending on input related to operation of mobile terminal, and mobile terminal therefor(String), 根据与移动终端操作相关的输入来控制多个对象显示的方法及其移动终端(String), US10775896B2(String), A method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes changing, if an input related to operation of the mobile terminal is received when a layout including a plurality of areas in which a plurality of objects are respectively displayed is displayed, one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. The input related to the operation of the mobile terminal may be a motion of the mobile terminal, a user's breath, or a gesture. If an input related to operation of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged.(String), 提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括:如果在显示包括分别显示多个对象的多个区域的布局时接收到与移动终端的操作相关的输入,则改变与输入相关的多个区域中的一个或多个区域。 对移动终端的操作进行操作,并显示包括改变区域的布局。 与移动终端的操作相关的输入可以是移动终端的动作、用户的呼吸或手势。 如果在构成布局的区域之一被触摸时检测到与移动终端的操作相关的输入,则重新排列除了被触摸区域之外的其余区域。(String), US16/227823(String), 1545235200(Integer), US10775896B2(String), 1600099200(Integer), 1600099200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 17(Integer), 113(Integer), CN102736849A | JP1456713S | JP1976007453A | JP2003345492A | JP2004240757A | JP2004254281A | JP2006055398A | JP2006513487A | JP2007094378A | JP2007511851A | JP2007538203A | JP2008247873A | JP2008268689A | JP2009122093A | JP2011007701A | JP2011028677A | JP2012038292A | JP2012118652A | JP2012138892A | JP2012150205A | JP2012217677A | JP2012230572A | JP2012243091A | JP2012509544A | JP2012521595A | JP2012533751A | JP2013174279A | JP2013245447A | JP2014003854A | JP2014069285A | JP2014082404A | JP2014215737A | JP2015061605A | JP5107453B1 | JPWO2005112336A1 | JPWO2011125790A1 | KR1020050086960A | KR1020050086963A | KR1020110016194A | KR1020120071468A | KR1020120129697A | RU2011110239A | RU2455679C2 | US20050108655A1 | US20060053385A1 | US20060101352A1 | US20080250312A1 | US20080282202A1 | US20090046075A1 | US20090051648A1 | US20090106694A1 | US20090197635A1 | US20090327272A1 | US20100060599A1 | US20100070926A1 | US20100125811A1 | US20100125816A1 | US20100134312A1 | US20100164992A1 | US20100217685A1 | US20100248788A1 | US20100281374A1 | US20110016423A1 | US20110041101A1 | US20110175930A1 | US20110281633A1 | US20110312349A1 | US20120030569A1 | US20120032901A1 | US20120154294A1 | US20120162261A1 | US20120166997A1 | US20120190407A1 | US20120192121A1 | US20120200513A1 | US20120246586A1 | US20120264512A1 | US20120274541A1 | US20120299847A1 | US20130120295A1 | US20130120447A1 | US20130125069A1 | US20130154951A1 | US20130167055A1 | US20130191784A1 | US20130219277A1 | US20130278484A1 | US20140035946A1 | US20140059472A1 | US20140101610A1 | US20140115493A1 | US20140139637A1 | US20140143737A1 | US20140149903A1 | US20140152597A1 | US20140181751A1 | US20140189601A1 | US20140215310A1 | US20150077333A1 | US8191011B2 | WO2008117827A1 | WO2010117827A2 | WO2012061917A1 | WO2012066591A1 | WO2012083277A2 | WO2012108620A2 | WO2012159268A1 | WO2012169190A1(String), \20230420\c612d573547d44be86f06686cdfafb2d.png(String), 21(Integer), 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.847 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.848 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.848 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 1. A method of controlling a display of a plurality of areas according to a motion of a mobile terminal, the method comprising:dividing a display screen into the plurality of areas according to a predefined layout;identifying a shaking motion of the mobile terminal while the plurality of areas are displayed, wherein the shaking motion comprises a first movement associated with a first direction and a second movement associated with a second direction opposite to the first direction;determining whether the first and second direction of the shaking motion corresponds to a reconfiguration direction in which the layout changes; andin response to the shaking motion being performed a predetermined number of times:identifying at least one area of the plurality of areas to be moved according to the reconfiguration direction,maintaining remaining areas of the plurality of areas that are not to be moved in same area in which the remaining areas are displayed before the shaking motion, wherein the at least one area to be moved and the remaining areas to be maintained in the same area are identified according to a preset arrangement rule,moving all of the identified at least one area of the plurality of areas to at least one different location within the layout in which the identified at least one area of the plurality of areas was not displayed before the shaking motion, such that the plurality of areas are arranged according to the preset arrangement rule and remain being displayed on the display screen after the shaking motion; anddisplaying at least one icon for adjusting a number of the plurality of areas in the layout andrearranging the plurality of areas when adding or removing one or more areas in response to the shaking motion of the mobile terminal being performed number of times while a touch on the at least one icon for adjusting is maintained.(String), 1.一种根据移动终端的运动控制多个区域显示的方法,该方法包括:根据预定布局将显示屏幕划分为多个区域;识别显示多个区域时移动终端的摇动动作,其中摇动动作包括与第一方向相关联的第一运动和与第一方向相反的第二方向相关联的第二运动;判断摇动的第一方向和第二方向是否对应于布局变化的重构方向;和响应于执行预定次数的摇动动作:根据重构方向识别要移动的多个区域中的至少一个区域,将多个待移动区域中的剩余区域保持在同一区域中,所述剩余区域在摇动动作之前显示在同一区域中,其中,所述至少一个待移动区域与所述剩余待移动区域保持在同一区域中根据预设排列规则识别,将多个区域中的所有已识别的至少一个区域移动到布局内的至少一个不同位置,其中在摇动动作之前未显示多个区域中的已识别的至少一个区域,使得多个区域按照预设排列规则排列,并在摇动后保持显示在显示屏上;和显示至少一个图标,用于调整布局中多个区域的数量,以及当响应于移动终端被执行多次摇动动作而增加或移除一个或多个区域时,重新排列多个区域,同时保持对至少一个用于调整的图标的触摸。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 2. The method of claim 1, further comprising:determining whether one of the plurality of areas is applied to the preset arrangement rule in response to the shaking motion of the mobile terminal.(String), 2.如权利要求1所述的方法,还包括:响应于移动终端的摇动动作,确定多个区域之一是否适用于预设排列规则。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 3. The method of claim 1, wherein the preset arrangement rule is in consideration of the properties of the plurality of areas, the properties regarding the horizontal and vertical formats of the plurality of areas.(String), 3.如权利要求1所述的方法,其中预设排列规则是考虑了多个区域的属性,即多个区域的横向和纵向格式的属性。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 4. The method of claim 1, wherein the plurality of areas include shortcut icons for executing applications.(String), 4.如权利要求1所述的方法,其中多个区域包括用于执行应用程序的快捷方式图标。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 5. The method of claim 4, further comprising:detecting a direction of the shaking motion corresponding to at least one of an up-down direction, a left-right direction, or a diagonal direction of the mobile terminal.(String), 5.如权利要求4所述的方法,还包括:检测与移动终端的上下方向、左右方向或对角方向中的至少一个方向对应的摇动运动的方向。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 6. The method of claim 1, further comprising:determining whether a number of shaking motions of the mobile terminal is equal to or greater than a predetermined number in response to the shaking motion of the mobile terminal; andadding a predetermined number of areas to a current page in response to the number of the shaking motions being equal to or greater than the predetermined number.(String), 6.如权利要求1所述的方法,还包括:响应于移动终端的摇动动作,判断移动终端的摇动动作次数是否等于或大于预定次数;和响应于摇动动作的数量等于或大于预定数量,将预定数量的区域添加到当前页面。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 7. The method of claim 6, wherein the added areas include areas of a next page.(String), 7.如权利要求6所述的方法,其中添加的区域包括下一页的区域。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 8. The method of claim 1, further comprising:determining whether one of the plurality of areas is touched; determining whether the shaking motion of the mobile terminal is received while the touch is maintained; andin response to identifying the shaking motion of the mobile terminal while the touch is maintained, rearranging remaining areas except for the touched areas in response to the shaking motion of the mobile terminal.(String), 8.如权利要求1所述的方法,还包括:确定多个区域之一是否被触摸;判断在保持触摸的同时是否接收到移动终端的摇动动作;和响应于在保持触摸的同时识别移动终端的摇动动作,响应于移动终端的摇动动作重新排列除了被触摸区域之外的剩余区域。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 9. The method of claim 8, further comprising:searching for areas associated with an area belonging to the touched area corresponding to a property of the area in response to the shaking motion of the mobile terminal;adding the searched areas to position where the area is not displayed; anddisplaying the searched areas.(String), 9.如权利要求8所述的方法,还包括:响应于移动终端的摇动运动,搜索与区域的属性对应的属于触摸区域的区域相关联的区域;将搜索到的区域添加到未显示区域的位置;和显示搜索到的区域。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 10. The method of claim 9, further comprising: searching for pictures associated with a person appearing on a portrait in response to the area belonging to the touch area being the portrait; andrespectively displaying the searched pictures.(String), 10.如权利要求9所述的方法,还包括:响应于属于触摸区域的区域是人像,搜索与出现在人像上的人物相关联的图片;和分别显示搜索到的图片。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 11. A mobile terminal for controlling a display of a plurality of areas according to a shaking motion of the mobile terminal, the mobile terminal comprising:a display screen divided into the plurality of areas according to a predefined layout;a sensor device configured to detect the shaking motion of the mobile terminal; andat least one processor configured to:identify, by using the sensor device, the shaking motion of the mobile terminal while the plurality of areas are displayed, wherein the shaking motion comprises a first movement associated with a first direction and a second movement associated with a second direction opposite to the first direction,determine whether the first and second direction of the shaking motion corresponds to a reconfiguration direction in which the layout changes; andin response to the shaking motion being performed a predetermined number of times:identify at least one area of the plurality of areas to be moved according to the reconfiguration direction, maintain all remaining areas of the plurality of areas that are not to be moved in same area in which the remaining areas are displayed before the shaking motion, wherein the at least one area to be moved and the remaining areas to be maintained in the same area are identified according to a preset arrangement rule,move all of the identified at least one area of the plurality of areas to at least one different location within the layout in which the identified at least one area of the plurality of areas was not displayed before the shaking motion, such that the plurality of areas are arranged according to the preset arrangement rule and remain being displayed on the display screen after the shaking motion, anddisplay at least one icon for adjusting a number of the plurality of areas in the layout and rearranging the plurality of areas when adding or removing one or more areas in response to the shaking motion of the mobile terminal being performed number of times while a touch on the at least one icon for adjusting is maintained.(String), 11.一种根据移动终端的摇动动作控制多个区域显示的移动终端,该移动终端包括:显示屏按照预定布局划分为多个区域;传感器装置,用于检测移动终端的晃动动作;和至少一个处理器配置为:通过传感器装置识别显示多个区域时移动终端的摇动动作,其中摇动动作包括与第一方向相关联的第一运动和与第一方向相反的第二方向相关联的第二运动,判断摇动的第一方向和第二方向是否对应于布局变化的重构方向;和响应于执行预定次数的摇动动作:根据重构方向识别多个待移动区域中的至少一个区域,将多个待移动区域中的所有剩余区域保持在摇动动作之前显示剩余区域的同一区域中,其中根据预设排列规则识别出至少一个待移动区域和同一区域中的其余待维护区域,将多个区域中的所有已识别的至少一个区域移动到布局内的至少一个不同位置,其中在摇动动作之前未显示多个区域中的已识别的至少一个区域,使得多个区域按照预设排列规则排列,并在摇动后保持显示在显示屏上;显示至少一个图标,用于在添加或删除一个或多个区域时响应于在触摸保留至少一个调整图标。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 12. The mobile terminal of claim 11, wherein the at least one processor is further configured to determine whether one of the plurality of areas is applied to the preset arrangement rule in response to the shaking motion of the mobile terminal.(String), 12.如权利要求11所述的移动终端,其中至少一个处理器还用于响应于移动终端的摇动动作,判断多个区域之一是否适用于预设排列规则。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 13. The mobile terminal of claim 11, wherein the preset arrangement rule is in consideration of the properties of the plurality of areas, the properties regarding the horizontal and vertical formats of the plurality of areas.(String), 13.如权利要求11所述的移动终端,其中预设排列规则是考虑了多个区域的属性,即多个区域的横向和纵向格式的属性。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 14. The mobile terminal of claim 11, wherein the at least one processor is further configured to:determine whether a number of shaking motions of the mobile terminal detected through the sensor device is equal to or greater than a predetermined number, andadd a predetermined number of areas to position of a current page in response to the number of the shaking motions being equal to or greater than the predetermined number.(String), 14.如权利要求11所述的移动终端,其中至少一个处理器还被配置为:确定通过传感器装置检测到的移动终端的摇动动作的次数是否等于或大于预定次数,以及响应于大于或等于预定数量的摇动动作,在当前页面的位置添加预定数量的区域。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 15. The mobile terminal of claim 14, wherein the added areas include areas of a next page.(String), 15.如权利要求14所述的移动终端,其中添加的区域包括下一页的区域。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 16. The mobile terminal of claim 11, wherein the at leas t one processor is further configured to:determine whether any one of the plurality of areas is selected, andin response to identifying the shaking motion of the mobile terminal while the selection is maintained, switch positions of remaining areas except for the selected area in response to detecting the shaking motion of the mobile terminal through the sensor device while the selection is maintained.(String), 16.如权利要求11所述的移动终端,其中至少一个处理器还被配置为:确定是否选择了多个区域中的任何一个,并且响应于在保持选择的同时识别移动终端的摇动动作,响应于在保持选择的同时通过传感器装置检测到移动终端的摇动动作,切换除所选区域之外的其余区域的位置。(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 17. The mobile terminal of claim 16, wherein, in response to detecting the shaking motion of the mobile terminal through the sensor device while the selection is maintained, the at least one processor is further configured to:search for areas associated with an area belonging to the selected area based on a property of the selected area,add the searched areas to position where the area is not displayed, and control the display to display the searched areas.(String), 17.如权利要求16所述的移动终端,其中,响应于在保持选择的同时通过传感器设备检测到移动终端的摇动动作,至少一个处理器还被配置为:基于所选区域的属性搜索与属于所选区域的区域关联的区域,将搜索到的区域添加到不显示该区域的位置,控制显示器显示搜索到的区域。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 18. The mobile terminal of claim 17, wherein, in response to the selected area being a portrait, the at least one processor is further configured to:search for pictures associated with a person appearing on the portrait, and control the display to display the searched pictures.(String), 18.如权利要求17所述的移动终端,其中,响应于所选区域为人像,所述至少一个处理器还用于:查找人像中出现的人物相关联的图片,并控制显示器显示查找到的图片。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 19. The mobile terminal of claim 11, wherein the plurality of areas include shortcut icons for executing applications.(String), 19.如权利要求11所述的移动终端,其中多个区域包括用于执行应用程序的快捷方式图标。(String), 1(Integer), 18(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 20. The mobile terminal of claim 19, wherein the sensor device comprises a motion sensor for detecting the shaking motion of the mobile terminal.(String), 20.如权利要求19所述的移动终端,其中传感器装置包括用于检测移动终端的晃动运动的运动传感器。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:43.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185967(Integer), 21. The mobile terminal of claim 19, wherein the sensor device is further configured to detect a direction of the shaking motion corresponding to at least one of an up-down direction, a left-right direction, or a diagonal direction of the mobile terminal.(String), 21.如权利要求19所述的移动终端,其中传感器装置还被配置为检测对应于移动终端的上下方向、左右方向或对角线方向中的至少一个的摇动运动的方向。(String), 1(Integer), 20(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.283 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185967(Integer), PRIORITY [0001]This application is a continuation application of prior application Ser. No. 14/105,735, filed on Dec. 13, 2013, which was based on and claimed priority under 35 U.S.C § 119(a) of a Korean patent application number 10-2013-0019508, filed on Feb. 22, 2013, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein in its entirety. BACKGROUND OF THE INVENTION 1. Field of the Invention [0002]The present invention relates generally to an apparatus and method for managing a plurality of objects that are displayed on a touch screen. More particularly, the present invention relates to an apparatus and method for allowing a user of a mobile terminal to easily change a display of a plurality of objects on a touch screen according to a motion of the mobile terminal. 2. Description of the Related Art [0003]A touch screen with a touch panel mounted on a display device displays images and allows a user to easily input commands without using a keyboard or a mouse. The touch screen has been widely used in various electronic devices, such as a mobile terminal, a navigation system, a TV, Automated Teller Machines (ATMs), a Point-Of-Sale (POS) system, and the like. [0004]For example, with the variety of services and additional functions that can be provided by mobile terminals, many recent mobile terminals provide a Graphic User Interface (GUI) based on a touch screen. [0005]In order to raise the effective value of such mobile terminals and meet users' needs, various applications executable in mobile terminals are being developed. [0006]A mobile terminal can store basic applications developed by the mobile terminal's manufacturing company, as well as additional applications downloaded from application sales web sites through the Internet, and execute the applications. [0007]Accordingly, a mobile terminal, such as the latest smart phone, tablet PC, and the like, stores at least hundreds of applications, and shortcut keys for executing the applications individually are displayed in the form of icons on the touch screen of the mobile terminal. A user can touch one of the icons displayed on the touch screen of a mobile terminal to thus execute a desired application on the mobile terminal. Various visual objects, such as widgets, pictures, document, etc., other than the shortcut keys, may also be displayed on the touch screen of the mobile terminal. [0008]However, as the number of such various visual objects increases, another issue arises. The number of objects that can be displayed on the small screen of a mobile terminal is limited although the mobile terminal stores many visual objects. [0009]Accordingly, due to the spatial limitation of a display screen, there is a need for classifying and arranging visual objects that can be displayed on the screen. However, arranging the components of a layout at regular intervals is insufficient, and it is necessary for a user to be able to conveniently manage visual objects displayed on the screen of a mobile terminal, such as editing, moving, or deleting the visual objects. According to the related art, when a user wants to change a display of objects, the user should convert the screen of his/her mobile terminal into an Edit environment, and input commands for deleting or correcting objects, which causes onerousness and inconvenience and requires a long time for editing. [0010]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. [0011]The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY OF THE INVENTION [0012]Aspects of the present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide an apparatus and method for allowing a user to conveniently change the components of a layout in which a plurality of objects are arranged according to his/her desired pattern. [0013]Another aspect of the present invention is to provide an apparatus and method for easily controlling an arrangement of a plurality of objects and a display of a layout in which the objects are arranged according to a motion of a mobile terminal. [0014]In accordance with an aspect of the present invention, a method of controlling a display of a plurality of objects according to an input related to operation of a mobile terminal is provided. The method includes displaying a layout including a plurality of areas in which a plurality of objects are respectively displayed, receiving the input related to the operation of the mobile terminal, changing one or more areas of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and displaying a layout including the changed areas. [0015]In accordance with another aspect of the present invention, a mobile terminal for controlling a display of a plurality of objects according to an input related to operation of the mobile terminal is provided. The mobile terminal includes a display unit configured to display a layout including a plurality of areas in which the plurality of objects are respectively displayed, a sensor module configured to detect the input related to the operation of the mobile terminal, and a controller configured to change one or more of the plurality of areas corresponding to the input related to the operation of the mobile terminal, and to control the display unit to display a layout including the changed areas. [0016]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention; [0019]FIG. 2 is a front perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0020]FIG. 3 is a rear perspective view of a mobile terminal according to an exemplary embodiment of the present invention; [0021]FIG. 4 is a flowchart of a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0022]FIGS. 5A through 8B show examples for explaining a process in which areas constituting a layout change according to directions of reciprocating motions of a mobile terminal according to an exemplary embodiment of the present invention; [0023]FIGS. 9A to 9D show examples for explaining a process in which areas constituting a layout change according to a breath according to an exemplary embodiment of the present invention; [0024]FIGS. 10A to 11D are views for explaining an arrangement rule of a layout according to an exemplary embodiment of the present invention; [0025]FIG. 12 is a flowchart for explaining a method of changing areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0026]FIGS. 13A and 13B show examples for explaining a process in which different objects are respectively displayed on areas constituting a layout according to the property of a touched object according to an exemplary embodiment of the present invention; [0027]FIGS. 14A and 14B are flowcharts for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; [0028]FIGS. 15A to 15I show examples for explaining a process of adjusting a number of areas constituting a layout in the mobile terminal, according to an exemplary embodiment of the present invention; [0029]FIG. 16 is a flowchart for explaining a method of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention; and [0030]FIGS. 17A to 17C show examples for explaining a process of adjusting a number of areas constituting a layout in a mobile terminal according to an exemplary embodiment of the present invention. [0031]Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0032]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. [0033]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0034]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0035]It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. [0036]The exemplary embodiments that will be described below relate to a hand-held terminal, however, an apparatus and method for managing a plurality of objects displayed on a touch screen, according to exemplary embodiments of the present invention, may be applied to various electronic devices with touch screens, such as a navigation system, a television (TV), an Automated Teller Machine (ATM), a Point-Of-Sale (POS) system, and the like, as well as a mobile terminal, such as a mobile phone, a smart phone, a tablet PC, and the like. [0037]Also, in the following description, a mobile terminal may be a flexible device or a flexible display device. As a representative mobile terminal, a mobile phone is assumed, and some components of such a mobile terminal may be omitted or changed as necessary. [0038]Exemplary embodiments of the present invention provide a method of controlling a display of a plurality of objects according to an input related to a motion of a mobile terminal. Exemplary embodiments of the present invention includes an operation of changing, if an input related to a motion of the mobile terminal is received when a layout including areas in which the plurality of objects are displayed is displayed, one or more areas corresponding to the input related to the motion of the mobile terminal among the areas constituting the layout; and an operation of displaying a layout comprised of the changed areas. The input related to the motion of the mobile terminal may correspond to a motion of the mobile terminal, a user's breath, a gesture, and the like. According to exemplary embodiments of the present invention, if an input related to a motion of the mobile terminal is detected while one of the areas constituting the layout is being touched, the remaining areas except for the touched area are rearranged. In this case, objects that are respectively displayed in the remaining areas may be objects searched in correspondence to the property of an object displayed on the touched area. Thereby, a user can easily change components corresponding to the areas of a layout, as well as changing the areas of the layout. [0039]FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention. [0040]Referring to FIG. 1, the mobile terminal 100 may be connected to an external electronic device (not shown) using at least one of a communication module 120, a connector 165, and an earphone connecting jack 167. The external electronic device may include an earphone, an external speaker, a Universal Serial Bus (USB) memory, a battery charger, a Cradle/Dock, a Digital Multimedia Broadcasting (DMB) antenna, a mobile payment system, healthcare equipment (a blood glucose meter, etc.), a game, a vehicle navigation system, and the like, which can be removably connected to the mobile terminal 100 through a line. The external electronic device may include a Bluetooth communication apparatus, a Near Field Communication (NFC) apparatus, a WiFi Direct communication apparatus, a Wireless Access Point (WAP), and the like, which can be connected to the mobile terminal 100 in a wireless fashion. The mobile terminal 100 may be connected to one of other mobile terminals or electronic devices (for example, a mobile phone, a smart phone, a tablet PC, a desktop PC, and a server) in a wired/wireless fashion. [0041]The mobile terminal 100 includes a touch screen 190 and at least one touch screen controller 195. The mobile terminal 100 may further include a controller 110, the communication module 120, a multimedia module 140, a camera module 150, an input/output module 160, a sensor module 170, a storage unit 175, and a power supply unit 180. [0042]The communication module 120 includes a mobile communication module 121, a sub communication module 130, and a broadcasting communication module 141. [0043]The sub communication module 130 includes at least one of a Wireless LAN (WLAN) module 131 and a short-range communication module 132. The multimedia module 140 includes at least one of an audio play module 142 and a video play module 143. The camera module 150 may include at least one of a first camera 151 and a second camera 152. The camera module 150 may also include at least one of a body tube 155 for zooming in/out the first and/or second camera 151 or 152, a motor unit 154 for controlling the movement of the body tube 155, and a flash 153 for providing a light source for photographing, according to the main purpose of the mobile terminal 100. The input/output module 160 may includes at least one of a button 161, a microphone 162, a speaker 163, a vibration device 164, the connector 165, and a keypad 166. [0044]The controller 110 may include a CPU 111, a Read Only Memory (ROM) 112 that stores control programs for controlling the mobile terminal 100, and a Random Access Memory (RAM) 113 that stores signals or data received from the outside or is used as a memory area for tasks being performed by the mobile terminal 100. The CPU 111 may include one or more cores, such as a single core, a dual core, a triple core, or a quad core. The CPU 111, ROM 112, and RAM 113 may be connected to each other through internal buses. [0045]Also, the controller 110 may control the communication module 120, the multimedia module 140, the camera module 150, the input/output module 160, the sensor module 170, the storage unit 175, the power supply unit 180, the touch screen 190, and the touch screen controller 195. [0046]When a user input device, such as an input unit 168 or a user's finger, touches, approaches, or is located in proximity to at least one of a plurality of objects or items displayed on the touch screen 190, the controller 110 senses a user input, and identifies an object corresponding to a location at which the user input has been sensed on the touch screen 190. The user input through the touch screen 190 may be one of a direct touch input of directly touching an object, and a hovering input which is an indirect touch input of approaching an object within a predetermined identification distance without directly touching the object. For example, when a user brings the input unit 168 close to the touch screen 190, an object located straightly below the input unit 168 may be selected. The user input may be a gesture input through the camera module 150, a switch/button input through the button 161 or the keypad 166, or a voice input through the microphone 16, other than a user input through the touch screen 190. [0047]The object or item (such as a function item) may be at least one of an application, a menu, document, a widget, a picture, video, E-mail, a Short Message Service (SMS) message, a Multimedia Message Service (MMS) message, and the like, which have been or can be displayed on the touch screen 190 of the mobile terminal 100. The object or item can be selected, executed, deleted, canceled, stored, or changed by the user input device. The item may be a button, an icon (such as a shortcut icon), a thumbnail image, or a folder that stores at least one object in a mobile terminal. The item may be displayed in the form of an image, text, and the like. [0048]A shortcut item is an image that is displayed on the touch screen 190 to quickly execute a call, a contact list, a menu, etc., which are provided by each application or by the mobile terminal 100. If a command or selection for executing a shortcut item is received, the corresponding application is executed. [0049]When the input unit 168 approaches the touch screen 190 or is placed in proximity to the touch screen 190, the controller 110 may sense a user input event such as a hovering event. If a user input event is generated with respect to a predetermined item or according to a predetermined method, the controller 110 performs predetermined program operation corresponding to the user input event. [0050]The controller 110 may output a control signal to the input unit 168 or the vibration device 164. The control signal may include information regarding a vibration pattern, and the input unit 168 or the vibration device 164 may generate vibration according to the vibration pattern. The information regarding the vibration pattern may represent a vibration pattern, an identifier of a vibration pattern, or the like. Alternatively, the control signal may include only a request for generation of vibration. [0051]The mobile terminal 100 may include at least one of the mobile communication module 121, the WLAN module 131, and the short-range communication module 132, according to the function of the mobile terminal 100. [0052]The mobile communication module 121 may connect the mobile terminal 100 to an external electronic device through mobile communication using one or more antennas (not shown) under the control of the controller 110. The mobile communication module 121 may transmit/receive radio signals for a voice call, a video call, a SMS message, or a MMS message to/from a mobile phone (not shown), a smart phone (not shown), a tablet PC (not shown), or another electronic device (not shown) when the corresponding phone number is input to the mobile terminal 100. [0053]The sub communication module 130 may include at least one of the WLAN module 131 and the short-range communication module 132 as described above. For example, the sub communication module 130 may include one of the WLAN module 131 and the short-range communication module 132, or both the WLAN module 131 and the short-range communication module 132. [0054]The WLAN module 131 may be connected to the Internet at a place in which a WAP has been installed, under the control of the controller 110. The WLAN module 131 supports the IEEE802.11x standard. The short-range communication module 132 performs short-range communication between the mobile terminal 100 and an external electronic device in a wireless fashion under the control of the controller 110. The short-range communication may include Bluetooth, Infrared Data Association (IrDA), WiFi-Direct communication, NFC, and the like. [0055]The controller 110 may transmit a control signal according to a haptic pattern to the input unit 168 through the sub communication module 130. [0056]The broadcasting communication module 141 may receive broadcasting signals (for example, TV broadcasting signals, radio broadcasting signals, or data broadcasting signals) and broadcasting additional information (for example, an Electric Program Guide (EPS) or an Electric Service Guide (ESG)) transmitted from a broadcast station through a broadcasting communication antenna (not shown), under the control of the controller 110. [0057]The multimedia module 140 may include the audio play module 142 and the video play module 143 as described above. The audio play module 142 may reproduce a digital audio file (for example, a file with the extension “.mp3”, “. wma”, “.ogg” or “.wav”) that is stored in the storage unit 175 or received from an external device, under the control of the controller 110. The video play module 143 may reproduce a digital video file (for example, a file with the extension “.mpeg”, “. mpg”, “.mp4”, “.avi”, “.mov”, or “.mkv”) that is stored or received, under the control of the controller 110. The multimedia module 140 may be integrated with the controller 110. [0058]The camera module 150 may include at least one of the first and second cameras 151 and 152 for photographing still images or moving images under the control of the controller 110. The camera module 150 may also include at least one among the body tube 155 for zooming in/out to photograph a subject, the motor unit 154, and the flash 153 for providing a secondary light source required for photographing the subject. The first camera 151 may be disposed in the front side of the mobile terminal 100, and the second camera 152 may be disposed in the rear side of the mobile terminal 100. [0059]Each of the first and second cameras 151 and 152 may include a lens system, an image sensor, and the like. Each of the first and second cameras 151 and 152 converts an optical signal received (or photographed) through the lens system into an electrical image signal, and outputs the electrical image signal to the controller 110. Accordingly, a user can photograph a moving image or a still image through the first and second cameras 151 and 152. [0060]The input/output module 160 may include at least one among at least one button 161, at least one microphone 162, at least one speaker 163, at least one vibration device 164, the connector 165, the keypad 166, the earphone connecting jack 167, and the input unit 168. However, the input/output module 160 is not limited to the above-mentioned devices, and a cursor control, such as a mouse, a trackball, a joystick, or cursor direction keys, may also be provided to control the movement of a cursor on the touch screen 190. [0061]The button 161 may be formed on the front, side, or rear surface of the housing (or case) of the mobile terminal 100, and may include at least one among a power/lock button, a volume button, a menu button, a home button, a back button, and a search button. [0062]The microphone 162 may receive a voice or sound under the control of the controller 110 to generate an electrical signal. [0063]The speaker 163 may output sound corresponding to various signals or data (for example, radio data, broadcasting data, digital audio data, digital video data, etc.) out of the mobile terminal 100 under the control of the controller 110. The speaker 163 may output sound (for example, button manipulation sound corresponding to a call, currency connection sound, the other party's voice, etc.) corresponding to a function that is performed by the mobile terminal 100. One or more speakers 163 may be provided at one or more appropriate locations on the housing of the mobile terminal 100. [0064]The vibration device 164 may convert an electrical signal into mechanical vibration under the control of the controller 110. For example, if a voice or video call is made by another device (not shown) when the mobile terminal 100 is in a vibration mode, the vibration device 164 operates. One or more vibration devices 164 may be provided in the housing of the mobile terminal 100. The vibration device 164 may operate in correspondence to a user input through the touch screen 190. [0065]The connector 165 may be used as an interface for connecting the mobile terminal 100 to an external electronic device or a power source (not shown). The controller 110 may transmit data stored in the storage unit 175 to an external electronic device or receive data from the external electronic device through a wired cable connected to the connector 165. The mobile terminal 100 may receive power from a power source or charge a battery using the power source through the wired cable connected to the connector 165. [0066]The keypad 166 may receive a key input from a user to control the mobile terminal 100. The keypad 166 includes a physical keypad (not shown) formed on the mobile terminal 100 or a virtual keypad (not shown) displayed on the touch screen 190. The physical keypad formed on the mobile terminal 100 may be excluded according to the performance or structure of the mobile terminal 100. [0067]The earphone (not shown) may be inserted into the earphone connecting jack 167 to connect to the mobile terminal 100. [0068]The input unit 168 may be inserted into and held in the mobile terminal 100, and when in use, the input unit 168 may be drawn or separated from the mobile terminal 100. A detachment/attachment recognition switch 169 that operates in correspondence to attachment and detachment of the input unit 168 may be provided in an area of the mobile terminal 100 into which the input unit 168 is inserted. The detachment/attachment recognition switch 169 may output a signal corresponding to attachment/separation of the input unit 168 to the controller 110. The detachment/attachment recognition switch 169 may be configured to directly or indirectly contact the input unit 168 when the input unit 169 is attached in the mobile terminal 100. Accordingly, the detachment/attachment recognition switch 169 generates a signal (i.e., a signal for notifying attachment or separation of the input unit 168) corresponding to attachment or separation of the input unit 168 based on whether the detachment/attachment recognition switch 169 contacts the input unit 168, and outputs the signal to the controller 110. [0069]The sensor module 170 may include at least one sensor for detecting the state of the mobile terminal 100. For example, the sensor module may include at least one sensor among a proximity sensor (not shown) for detecting an approach to the mobile terminal 100, an ambient light sensor (not shown) for detecting the ambient light intensity around the mobile terminal 100, a motion sensor (not shown) for detecting a motion (for example, rotation, acceleration, vibration) of the mobile terminal 100, a geo-magnetic sensor (not shown) for detecting a point of the compass of the mobile terminal 100 using the earth's magnetic field, a gravity sensor (not shown) for detecting a direction in which gravity is applied, an altimeter (not shown) for measuring atmospheric pressure to detect an altitude, and a GPS module 157. A camera sensor for sensing a user's gesture may also be included in the sensor module 170. [0070]The motion sensor among the above-mentioned sensors senses the location, movement, and the like of the mobile terminal 100 using an acceleration sensor, a gyro sensor, a tilt sensor, or their combinations. However, the sensors are not limited to the above-mentioned sensors, and may include other types of a sensor capable of sensing the reciprocating motions, movement directions, and the like of the mobile terminal 100. [0071]Sensing data (that is, motion information) output through the motion sensors may have a direction and a magnitude. For example, an acceleration sensor for sensing the acceleration of the mobile terminal 100 can sense acceleration with respect to at least one reference-axis direction of x, y, and z axes, and output the acceleration information. The reference-axis may be an axis (for example, the up-down (z-axis), left-right (x-axis), and front-rear (y-axis) directions of the mobile terminal 100) according to the direction of the mobile terminal 100, or may be an axis according to the direction of gravity (the direction (z-axis) of gravity and directions (z and y axes) perpendicular to the direction of gravity). [0072]The sensor module 170 may further include a calculator (not shown) for integrating sensed angular velocity, velocity, etc. over time to calculate a rotation angle, a direction, velocity, a travel distance, a location, a trajectory, and the like according to a motion of the mobile terminal 100, and output the calculated information. The calculator may be included in the controller 110. The calculator may also include a frequency filter for blocking or passing a specific band of a signal such as sensed acceleration in order to calculate a trajectory, etc. or effectively analyze the direction of a motion. [0073]When the sensor module 170 includes the calculator, the calculator may calculate a direction or angle in or at which the mobile terminal 100 moves, and transfer the result of the calculation to the controller 100. However, the direction or angle in or at which the mobile terminal 100 moves may be calculated by the controller 110. The direction in which the mobile terminal 100 moves may be basically an up-down direction or a left-right direction. The direction in which the mobile terminal 100 moves may be a front direction in which the mobile terminal 100 is pulled horizontally toward a user or a back direction in which the mobile terminal 100 is pushed horizontally against the user. A tilting direction in which the mobile terminal 100 is tilted with respect to a reference axis is included in the direction of a motion. When the angle at which the mobile terminal 100 moves is calculated in a direction which the mobile terminal 100 is tilted under an assumption that the current position of the mobile terminal 100 is at 0 degree, a direction diagonal to the direction in which the mobile terminal 100 moves also may be included in the direction of a motion. [0074]According to an exemplary embodiment of the present invention, the sensor module 170 may also include a breath detection sensor for using a user's breath as a control command to change the configuration of a layout according to the user's breath. The breath detection sensor is attached on the outer surface of the mobile terminal 100, and detects a user's breath or wind brown through an inlet. The breath detection sensor may be a wind velocity sensor that outputs an electrical signal according to a user's breath. The wind velocity sensor transfers an output value that increases at a constant rate according to a user's breath intensity to the controller 110. Alternatively, the breath detection sensor may be a temperature sensor or a humidity sensor capable of sensing a user's breath, in which case the temperature sensor or the humidity sensor can transfer various levels of output values to the controller 110 according to a user's breath intensity. [0075]The GPS module 157 can receive radio waves from a plurality of GPS satellites (not shown) on the orbit around the earth, and calculate the location of the mobile terminal 100 based on a time of arrival of the radio waves from the GPS satellites to the mob(String), 优先 [0001] 本申请是在先申请系列的延续申请。 2013 年 12 月 13 日提交的第 14/105,735 号,该专利基于 2013 年 2 月 22 日提交的韩国专利申请号 10-2013-0019508 并根据 35 U.S.C § 119(a) 要求优先权 韩国知识产权局,其公开的全部内容通过引用并入本文。 背景技术 1. 发明领域 [0002] 本发明总体上涉及一种用于管理在触摸屏上显示的多个对象的设备和方法。 更具体地,本发明涉及一种用于允许移动终端的用户根据移动终端的动作容易地改变触摸屏上的多个对象的显示的设备和方法。 2.相关技术的描述 [0003] 具有安装在显示设备上的触摸面板的触摸屏显示图像并允许用户在不使用键盘或鼠标的情况下轻松输入命令。 触摸屏已广泛应用于各种电子设备,例如移动终端、导航系统、电视、自动柜员机(ATM)、销售点(POS)系统等。 [0004] 例如,随着移动终端可以提供的各种服务和附加功能,最近的许多移动终端都提供了基于触摸屏的图形用户界面(GUI)。 [0005] 为了提高这种移动终端的有效价值并满足用户的需求,正在开发可在移动终端中执行的各种应用程序。 [0006] 移动终端可以存储移动终端制造公司开发的基本应用程序,以及通过互联网从应用程序销售网站下载的附加应用程序,并执行这些应用程序。 [0007] 相应地,移动终端,例如最新的智能手机、平板电脑等,存储了至少数百个应用程序,并且用于单独执行应用程序的快捷键以图标的形式显示在移动终端的触摸屏上 . 用户可以触摸显示在移动终端的触摸屏上的图标之一,从而在移动终端上执行期望的应用。 移动终端的触摸屏上还可以显示除快捷键之外的各种可视对象,如小部件、图片、文档等。 [0008] 然而,随着这种各种视觉对象的数量增加,另一个问题出现了。 移动终端虽然存储了很多视觉对象,但是在移动终端的小屏幕上可以显示的对象的数量是有限的。 [0009] 因此,由于显示屏幕的空间限制,需要对可显示在屏幕上的视觉对象进行分类和排列。 然而,将布局的组成部分等间隔排列是不够的,需要用户能够方便地管理移动终端屏幕上显示的可视对象,例如对可视对象进行编辑、移动或删除等。 现有技术中,当用户想要改变对象的显示时,需要将自己的移动终端屏幕转换为Edit环境,并输入删除或更正对象的命令,造成繁重不便,需要 很长一段时间的编辑。 [0010] 上述信息仅作为背景信息提供以帮助理解本公开。 没有作出任何决定,也没有作出任何断言,关于上述任何内容是否可以用作关于本发明的现有技术。 [0011] 上述信息仅作为背景信息提供以帮助理解本公开。 没有作出任何决定,也没有作出任何断言,关于上述任何内容是否可以用作关于本发明的现有技术。 发明内容 [0012]本发明的方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面是提供一种允许用户方便地改变布局的组件的设备和方法,其中多个对象根据他/她的期望图案排列。 [0013] 本发明的另一方面在于提供一种用于容易地控制多个对象的布置以及其中根据移动终端的运动布置对象的布局的显示的设备和方法。 [0014] 根据本发明的一方面,提供了一种根据与移动终端的操作相关的输入来控制多个对象的显示的方法。 该方法包括显示包括多个区域的布局,其中分别显示多个对象,接收与移动终端的操作相关的输入,改变与与移动终端相关的输入对应的多个区域中的一个或多个区域。 移动终端的操作,以及显示包括改变区域的布局。 [0015] 根据本发明的另一方面,提供了一种用于根据与移动终端的操作相关的输入来控制多个对象的显示的移动终端。 移动终端包括:显示单元,被配置为显示包括多个区域的布局,在该多个区域中分别显示多个对象;传感器模块,被配置为检测与移动终端的操作相关的输入;以及控制器,被配置为改变 对应于与移动终端的操作相关的输入的多个区域中的一个或多个,并控制显示单元显示包括改变的区域的布局。 [0016] 通过以下详细描述,本发明的其他方面、优点和显着特征对于本领域技术人员将变得显而易见,其结合附图公开了本发明的示例性实施例。 附图的简要说明 [0017] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0018] 如图。 附图说明图1是示出根据本发明示例性实施例的移动终端的框图; [0019] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图; [0020] 如图。 图3是根据本发明示例性实施例的移动终端的后透视图; [0021] 如图。 图4是根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图; [0022] 图 图5A至图8B示出了用于解释根据本发明示例性实施例的构成布局的区域根据移动终端的往复运动方向改变的处理的示例; [0023] 图 图9A至9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的处理的示例; [0024] 图 图10A~图11D是用于说明本发明的实施方式的布局的排列规则的图。 [0025] 如图。 图12是用于说明根据本发明示例性实施例的移动终端中改变构成布局的区域的方法的流程图; [0026] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的特性将不同对象分别显示在构成布局的区域上的处理的示例; [0027]图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; [0028] 图 图15A至图15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例; [0029] 如图。 图16是用于说明根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图; 和 [0030] 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0031] 在整个附图中,相似的附图标记将被理解为指代相似的部件、组件和结构。 示例性实施例的详细描述 [0032] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物定义的本发明的示例性实施例。 它包括各种具体细节以帮助理解,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对这里描述的实施例进行各种改变和修改。 此外,为了清楚和简明,可以省略对众所周知的功能和结构的描述。 [0033] 以下描述和权利要求中使用的术语和词语不限于书目含义,而仅由发明人使用以使对本发明的理解清晰一致。 因此,本领域技术人员应当清楚,提供本发明示例性实施例的以下描述仅用于说明目的,而不是为了限制由所附权利要求及其等同物限定的本发明。 [0034] 应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0035] 应当理解,尽管在本文中可以使用术语第一、第二等来描述各种元素,但是这些元素不应受到这些术语的限制。 这些术语仅用于区分一个元素与另一个元素。 例如,可以将第一元件称为第二元件,并且类似地,可以将第二元件称为第一元件,而不脱离本发明的范围。 如本文所用,单数形式“a”、“an”和“the”旨在也包括复数形式,除非上下文另有明确指示。 [0036] 下面将描述的示例性实施例涉及手持终端,然而,根据本发明示例性实施例的用于管理显示在触摸屏上的多个对象的设备和方法可以应用于各种电子设备 具有触摸屏,例如导航系统、电视(TV)、自动柜员机(ATM)、销售点(POS)系统等,以及移动终端,例如移动 手机、智能手机、平板电脑等。 [0037] 此外,在以下描述中,移动终端可以是柔性设备或柔性显示设备。 作为代表性的移动终端,假设是移动电话,并且可以根据需要省略或改变这种移动终端的一些组件。 [0038]本发明的示例性实施例提供了一种根据与移动终端的运动相关的输入来控制多个对象的显示的方法。 本发明的示例性实施例包括如下操作:如果在显示包括显示多个对象的区域的布局时接收到与移动终端的运动相关的输入,则改变与该输入相关的一个或多个区域的操作。 移动终端在构成布局的区域之间的运动; 以及显示由改变的区域组成的布局的操作。 与移动终端的动作相关的输入可以对应于移动终端的动作、用户的呼吸、手势等。 根据本发明的示例性实施例,如果在构成布局的区域之一被触摸时检测到与移动终端的运动相关的输入,则重新排列除了被触摸区域之外的其余区域。 在这种情况下,分别显示在剩余区域中的对象可以是与显示在触摸区域上的对象的属性相对应的搜索对象。 因此,用户可以容易地改变与布局的区域相对应的组件,以及改变布局的区域。 [0039] 如图。 图1是示出根据本发明示例性实施例的移动终端的框图。 [0040] 参考图。 1、移动端 100 可以使用通信模块中的至少一个连接到外部电子设备(未示出) 120 , 一个连接器 165 和耳机连接插孔 167 . 外部电子设备可以包括耳机、外部扬声器、通用串行总线(USB)存储器、电池充电器、底座/底座、数字多媒体广播(DMB)天线、移动支付系统、医疗保健设备(血液 血糖仪等)、游戏、车载导航系统等,可拆卸地连接到移动终端 100 通过一条线。 外部电子设备可以包括蓝牙通信装置、近场通信(NFC)装置、WiFi Direct通信装置、无线接入点(WAP)等,它们可以连接到移动终端 100 以无线方式。 移动终端 100 可以有线/无线方式连接到其他移动终端或电子设备(例如,手机、智能手机、平板电脑、台式电脑和服务器)之一。 [0041] 移动终端 100 包括一个触摸屏 190 和至少一个触摸屏控制器 195 . 移动终端 100 还可以包括控制器 110 , 通讯模块 120 , 多媒体模块 140 , 一个摄像头模块 150 , 输入/输出模块 160 , 一个传感器模块 170 , 一个存储单元 175 , 和一个电源单元 180 . [0042] 通讯模块 120 包括一个移动通信模块 121 , 一个子通信模块 130 ,以及广播通信模块 141 . [0043] 子通讯模块 130 包括至少一个无线 LAN (WLAN) 模块 131 和一个短距离通信模块 132 . 多媒体模块 140 包括至少一个音频播放模块 142 和一个视频播放模块 143 . 摄像头模组 150 可以包括第一相机中的至少一个 151 和第二台相机 152 . 摄像头模组 150 还可以包括至少一个体管 155 用于放大/缩小第一台和/或第二台摄像机 151 或者 152 , 一个电机单元 154 用于控制体管的运动 155 , 和一个闪光灯 153 根据移动终端的主要用途,为拍照提供光源 100 . 输入/输出模块 160 可以包括至少一个按钮 161 , 麦克风 162 , 扬声器 163 , 振动装置 164 , 连接器 165 , 和一个键盘 166 . [0044]控制器 110 可能包括一个 CPU 111 , 只读存储器 (ROM) 112 存储用于控制移动终端的控制程序 100 , 和一个随机存取存储器 (RAM) 113 存储从外部接收的信号或数据或用作移动终端正在执行的任务的存储区域 100 . 中央处理器 111 可以包括一个或多个核,例如单核、双核、三核或四核。 中央处理器 111 , 只读存储器 112 , 和内存 113 可以通过内部总线相互连接。 [0045] 此外,控制器 110 可以控制通讯模块 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 存储单元 175 , 电源单元 180 , 触摸屏 190 , 和触摸屏控制器 195 . [0046] 当用户输入设备,例如输入单元 168 或用户的手指、触摸、接近或位于触摸屏上显示的多个对象或项目中的至少一个的附近 190 , 控制器 110 感测用户输入,并识别与在触摸屏上感测到用户输入的位置相对应的对象 190 . 用户通过触摸屏输入 190 可以是直接触摸对象的直接触摸输入和不直接触摸对象而接近预定识别距离内的对象的间接触摸输入的悬停输入之一。 例如,当用户将输入单元 168 靠近触摸屏 190 , 位于输入单元正下方的对象 168 可以选择。 用户输入可以是通过相机模块的手势输入 150 , 一个开关/按钮通过按钮输入 161 或键盘 166 ,或通过麦克风输入的语音 16 , 除了通过触摸屏的用户输入 190 . [0047] 对象或项(例如功能项)可以是应用程序、菜单、文档、小部件、图片、视频、电子邮件、短消息服务(SMS)消息、多媒体消息服务中的至少一个 (MMS)消息等,已经或可以在触摸屏上显示 190 移动终端的 100 . 对象或项目可以由用户输入设备选择、执行、删除、取消、存储或改变。 该项目可以是按钮、图标(例如快捷方式图标)、缩略图或移动终端中存储至少一个对象的文件夹。 该项目可以以图像、文本等的形式显示。 [0048] 快捷项目是显示在触摸屏上的图像 190 快速执行各个应用或移动终端提供的通话、联系人列表、菜单等 100 . 如果接收到用于执行快捷方式项的命令或选择,则执行相应的应用程序。 [0049] 当输入单元 168 接近触摸屏 190 或放置在触摸屏附近 190 , 控制器 110 可以感测用户输入事件,例如悬停事件。 如果针对预定项目或根据预定方法生成用户输入事件,则控制器 110 执行对应于用户输入事件的预定程序操作。 [0050] 控制器 110 可以向输入单元输出控制信号 168 或振动装置 164 . 控制信号可以包括关于振动模式的信息,以及输入单元 168 或振动装置 164 可以根据振动模式产生振动。 关于振动模式的信息可以表示振动模式、振动模式的标识符等。 或者,控制信号可以仅包括产生振动的请求。 [0051] 移动终端 100 可以包括至少一个移动通信模块 121 , WLAN 模块 131 , 和短距离通信模块132 ,根据手机端的功能 100 . [0052] 移动通信模块 121 可以连接移动终端 100 在控制器的控制下,使用一根或多根天线(未显示)通过移动通信连接到外部电子设备 110 . 移动通信模块 121 可以向/从移动电话(未示出)、智能手机(未示出)、平板电脑(未示出)发送/接收用于语音呼叫、视频呼叫、SMS消息或MMS消息的无线电信号, 当对应的电话号码被输入到移动终端时,或另一个电子设备(未示出) 100 . [0053] 子通讯模块 130 可以包括至少一个 WLAN 模块 131 和短距离通信模块 132 如上所述。 例如子通信模块 130 可能包括 WLAN 模块之一 131 和短距离通信模块 132 , 或两者 WLAN 模块 131 和短距离通信模块 132 . [0054] 无线局域网模块 131 在控制器的控制下,可以在安装了 WAP 的地方连接到 Internet 110 . 无线局域网模块 131 支持 IEEE802.11x 标准。 短距离通信模块 132 在移动终端之间进行短距离通信 100 以及在控制器控制下以无线方式的外部电子设备 110 . 短距离通信可以包括蓝牙、红外数据协会(IrDA)、WiFi-Direct通信、NFC等。 [0055] 控制器 110 可以根据触觉模式向输入单元发送控制信号 168 通过子通讯模块 130 . [0056] 广播通信模块 141 可以接收广播信号(例如,电视广播信号、无线电广播信号或数据广播信号)和广播从广播站发送的附加信息(例如,电子节目指南(EPS)或电子服务指南(ESG)) 通过广播通信天线(未显示),在控制器的控制下 110 . [0057] 多媒体模块 140 可能包括音频播放模块 142 和视频播放模块 143 如上所述。 音频播放模块 142 可以再现存储在存储单元中的数字音频文件(例如,扩展名为“.mp3”、“.wma”、“.ogg”或“.wav”的文件) 175 或从外部设备接收,在控制器的控制下 110 . 视频播放模块 143 可以复制存储或 收到,在控制器的控制下 110 . 多媒体模块 140 可与控制器集成 110 . [0058] 摄像头模组 150 可以包括第一和第二相机中的至少一个 151 和 152 在控制器的控制下拍摄静止图像或运动图像 110 . 摄像头模组 150 还可以包括至少一种管体 155 为了放大/缩小拍摄对象,电机单元 154 , 和闪光灯 153 用于提供拍摄对象所需的辅助光源。 第一台相机 151 可以设置在移动终端的正面 100 , 和第二个摄像头 152 可以设置在移动终端的背面 100 . [0059] 第一和第二相机中的每一个 151 和 152 可以包括镜头系统、图像传感器等。 第一和第二相机中的每一个 151 和 152 将通过镜头系统接收(或拍摄)的光信号转换为电图像信号,并将电图像信号输出到控制器 110 . 因此,用户可以通过第一和第二相机拍摄运动图像或静止图像 151 和152 . [0060] 输入/输出模块 160 可以包括至少一个按钮中的至少一个 161 , 至少一个麦克风 162 , 至少一位发言者 163 , 至少一个振动装置 164 , 连接器 165 , 键盘 166 , 耳机连接插孔 167 , 和输入单元 168 . 然而,输入/输出模块 160 不限于上述设备,还可以提供鼠标、轨迹球、操纵杆或光标方向键等光标控件来控制光标在触摸屏上的移动 190 . [0061] 按钮 161 可以形成在移动终端的外壳(或外壳)的正面、侧面或背面 100 ,并且可以包括电源/锁定按钮、音量按钮、菜单按钮、主页按钮、返回按钮和搜索按钮中的至少一个。 [0062] 麦克风 162 可以在控制器的控制下接收语音或声音 110 产生电信号。 [0063] 演讲者 163 可以将与各种信号或数据(例如,无线电数据、广播数据、数字音频数据、数字视频数据等)对应的声音输出到移动终端之外 100 在控制器的控制下 110 . 演讲者 163 可以输出与移动终端执行的功能对应的声音(例如,与呼叫对应的按钮操作声音、货币连接声音、对方的语音等) 100 . 一位或多位演讲者 163 可以在移动终端的外壳上的一个或多个适当位置提供 100 . [0064] 振动装置 164 可在控制器的控制下将电信号转换为机械振动 110 . 例如,如果在移动终端时由另一个设备(未示出)进行语音或视频通话 100 处于振动模式时,振动装置 164 运作。 一个或多个振动装置 164 可以设置在移动终端的外壳中 100 . 振动装置 164 可以对应于通过触摸屏的用户输入进行操作 190 . [0065] 连接器 165 可作为连接移动终端的接口 100 连接到外部电子设备或电源(未显示)。 控制器 110 可以传输存储在存储单元中的数据 175 到外部电子设备或通过连接到连接器的有线电缆从外部电子设备接收数据 165 . 移动终端 100 可以通过连接到连接器的有线电缆从电源接收电力或使用电源为电池充电 165 . [0066] 键盘 166 可以接收来自用户的按键输入以控制移动终端 100 . 键盘 166 包括在移动终端上形成的物理键盘(未显示) 100 或触摸屏上显示的虚拟键盘(未显示) 190 . 在移动终端上形成的物理键盘 100 可根据移动终端的性能或结构排除 100 . [0067] 耳机(未显示)可以插入耳机连接插孔 167 连接到移动终端 100 . [0068] 输入单元 168 可插入并保持在移动终端中 100 ,而在使用时,输入单元 168 可从移动终端抽出或分离 100 . 脱离/附着识别开关 169 对应于输入单元的安装和拆卸进行操作 168 可以设置在移动终端的区域内 100 输入单元 168 被插入。 分离/附着识别开关 169 可以输出与输入单元的连接/分离相对应的信号 168 到控制器 110 . 分离/附着识别开关 169 可配置为直接或间接接触输入单元 168当输入单元 169 附在手机端 100 . 因此,分离/附着识别开关 169 产生一个信号(即,用于通知输入单元的连接或分离的信号 168 ) 对应于输入单元的连接或分离 168 基于是否分离/附着识别开关 169 接触输入单元 168 , 并将信号输出到控制器 110 . [0069] 传感器模块 170 可以包括至少一个传感器,用于检测移动终端的状态 100 . 例如,传感器模块可以包括用于检测接近移动终端的接近传感器(未示出)中的至少一个传感器 100 ,环境光传感器(未示出),用于检测移动终端周围的环境光强度 100 ,用于检测移动终端的运动(例如,旋转、加速度、振动)的运动传感器(未示出) 100 ,地磁传感器(未示出),用于检测移动终端的罗盘点 100 使用地球磁场,用于检测施加重力的方向的重力传感器(未示出),用于测量大气压力以检测高度的高度计(未示出),以及GPS模块 157 . 用于感测用户手势的相机传感器也可以包括在传感器模块中 170 . [0070] 上述传感器中的运动传感器感知移动终端的位置、运动等 100 使用加速度传感器、陀螺仪传感器、倾斜传感器或它们的组合。 然而,传感器不限于上述传感器,还可以包括能够感测移动终端的往复运动、移动方向等的其他类型的传感器。 100 . [0071] 通过运动传感器输出的感测数据(即运动信息)可以具有方向和幅度。 例如,用于感应移动终端加速度的加速度传感器 100 可以感应相对于x、y和z轴中至少一个参考轴方向的加速度,并输出加速度信息。 参考轴可以是移动终端的轴(例如,上下(z轴)、左右(x轴)和前后(y轴)方向) 100 ) 根据移动端的方向 100 ,或者可以是根据重力方向的轴(重力方向(z轴)和垂直于重力方向的方向(z和y轴))。 [0072] 传感器模块 170 还可以包括计算器(未示出),用于将感测到的角速度、速度等随时间积分以根据物体的运动计算旋转角度、方向、速度、行进距离、位置、轨迹等。 移动终端 100 ,并输出计算得到的信息。 计算器可能包含在控制器中 110 . 计算器还可以包括频率滤波器,用于阻止或通过特定频带的信号,例如检测到的加速度,以便计算轨迹等或有效地分析运动的方向。 [0073] 当传感器模块 170 包括计算器,计算器可以计算移动终端所处的方向或角度 100 移动,并将计算结果传送给控制器 100 . 但是,移动终端所处的方向或角度 100 移动可由控制器计算 110 . 移动终端的方向 100 移动基本上可以是上下方向或左右方向。 移动终端的方向 100 移动可以是移动终端所处的正面方向 100 被水平拉向用户或移动终端所在的后退方向 100 被水平推向用户。 移动终端的倾斜方向 100 相对于参考轴倾斜 包含在运动方向中。 当移动终端的角度 100移动是在移动终端的方向上计算的 100 在假设移动终端的当前位置是倾斜的 100 为0度,与移动终端所在方向的对角线方向 100 运动也可以包含在运动的方向中。 [0074] 根据本发明的示例性实施例,传感器模块 170 还可以包括呼吸检测传感器,用于使用用户的呼吸作为控制命令来根据用户的呼吸改变布局的配置。 呼吸检测传感器贴附在移动终端的外表面上 100 ,并通过入口检测用户的呼吸或风棕色。 呼吸检测传感器可以是根据用户的呼吸输出电信号的风速传感器。 风速传感器将根据用户的呼吸强度以恒定速率增加的输出值传输到控制器 110 . 或者,呼吸检测传感器可以是能够感测用户呼吸的温度传感器或湿度传感器,在这种情况下,温度传感器或湿度传感器可以将各种级别的输出值传递给控制器 110 根据用户的呼吸强度。 [0075] GPS模块 157 可以接收来自环绕地球轨道上的多个GPS卫星(未示出)的无线电波,并计算移动终端的位置 100 基于从 GPS 卫星到移动终端的无线电波的到达时间 100 . [0076] 存储单元 175 可以存储根据通信模块的操作输入/输出的信号或数据 120 , 多媒体模块 140 , 摄像头模块 150 , 输入/输出模块 160 , 传感器模块 170 , 或触摸屏 190 , 在控制器的控制下 110 . 存储单元 175 可以存储用于控制移动终端的应用程序和控制程序 100 或控制器 110 . [0077] 术语“存储单元”表示任意数据存储设备,例如存储单元 175 , 只读存储器 112 和内存 113 在控制器中 110 ,安装在移动终端中的存储卡(例如,SD卡或记忆棒) 100 ,等等。 存储单元 175 可以包括非易失性存储器、易失性存储器、硬盘驱动器(HDD)和固态驱动器(SSD)。 [0078] 存储单元 175 可以存储具有各种功能的应用程序,例如导航、视频通话、游戏、基于时间的警报应用程序等、用于为用户提供与应用程序相关联的图形用户界面 (GUI) 的图像、用户信息、文档、数据库 或与处理触摸输入的方法、背景图像(菜单屏幕、锁定屏幕等)或驱动移动终端所需的操作程序有关的数据 100 , 摄像头模块拍摄的图像 150 等存储单元 175 还可以存储与合成图像提供方法相关的数据。 [0079] 存储单元 175 是机器(例如,计算机)可读介质,术语“机器可读介质”可以定义为向机器提供数据以使机器能够执行特定功能的介质。 存储单元 175 可能包括非易失性介质和易失性介质。 这样的介质需要是有形的,以便传送到介质的命令可以被使用机器读取命令的物理工具检测到。 [0080] 机器可读介质包括软盘、软盘、硬盘、磁带、光盘只读存储器(CD-ROM)、光盘、穿孔卡、纸带中的至少一种。 、RAM、可编程只读存储器(PROM)、可擦除PROM(EPROM)和FLASH-EPROM,然而,机器可读介质不限于上述设备。 [0081] 电源单元 180 可以为安装在移动终端外壳中的一个或多个电池供电 100 在控制器的控制下 110. 一节或多节电池为移动终端供电 100 . 电源单元 180 可以将从外部电源接收的电力提供给移动终端 100 通过连接到连接器的有线电缆 165 . 电源单元 180 可以将从外部电源无线接收的电力提供给移动终端 100 通过无线充电技术。 [0082] 移动终端 100 可能包括至少一个触摸屏 190 为用户提供与各种服务(例如,通话、数据传输、拍照)相对应的GUI。 [0083] 触摸屏 190 可以将与输入到用户图形界面的至少一个用户输入相对应的模拟信号输出到触摸屏控制器 195 . 触摸屏 190 可以通过用户的身体部位(例如,包括拇指的手指)或输入单元接收至少一个用户输入 168 (例如,手写笔或电子笔)。 触摸屏 190 可以接收触摸的连续移动(例如,拖动输入)。 触摸屏 190 可以将与触摸的连续移动对应的模拟信号输出到触摸屏控制器 195 . [0084] 在本说明书中,术语“触摸”不限于手指或输入单元的接触 168 到触摸屏 190 ,并且可以包括非接触式识别(例如,当用户输入设备位于识别距离(例如,1 cm)内时,用户输入设备可以在不直接接触触摸屏的情况下被检测到) 190 )。 触摸屏的识别距离 190 能否识别用户输入设备可能取决于移动终端的性能或结构 100 . 为了触摸屏 190 为了区分与用户输入设备直接接触产生的直接触摸事件和间接触摸事件(即悬停事件),触摸屏 190 可以被配置为根据直接触摸事件和悬停事件输出不同的值(例如,包括电压值和电流值的模拟值)。 [0085] 触摸屏 190 可以是电阻式触摸屏、电容式触摸屏、红外触摸屏、声波触摸屏或它们的组合。 [0086] 触摸屏 190 还可以包括至少两个触摸面板,分别用于感应手指和输入单元的触摸或接近 168 分别接收手指和输入单元的输入 168 . 至少两个触摸面板针对手指和输入单元的输入提供不同的输出值 168 到触摸屏控制器 195 , 和触摸屏控制器 195 识别从至少两个触摸面板接收到的不同输出值,以确定触摸屏是否有输入 190 是手指输入还是输入单元输入 168 . [0087] 触摸屏控制器 195 转换从触摸屏接收到的模拟信号 190 转换成数字信号,并将数字信号传输给控制器 110 . 控制器 110 可以控制触摸屏 190 使用从触摸屏控制器接收到的数字信号 195 . 例如,控制器 110 可以选择或执行显示在触摸屏上的快捷方式图标或对象 190 响应直接触摸事件或悬停事件。 触摸屏控制器 195 可以集成到控制器中 110 . [0088] 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值) 190 确定悬停间隔或距离以及用户的输入位置,将确定的距离值转换为数字信号(例如z坐标),然后将数字信号提供给控制器 110 . 触摸屏控制器 195 可以检测通过触摸屏输出的值(例如,当前值)190 估计用户输入设备按压触摸屏的压力 190 ,将估计的压力值转换成数字信号,然后将数字信号提供给控制器 110 . [0089] 如图。 图2是根据本发明示例性实施例的移动终端的前透视图,以及图2是根据本发明示例性实施例的移动终端的前透视图。 图3是根据本发明示例性实施例的移动终端的后透视图。 [0090] 参考图。 1-3、触摸屏 190 放置在正面的中央 101 的移动终端。 触摸屏 190 可以形成占据正面主要部分的大面积 101 的移动终端。 如图。 图2示出了在触摸屏上显示主主屏幕的示例 190 . 主主屏幕是最初出现在触摸屏上的屏幕 190 当移动端 100 通电。 如果移动端 100 具有多个页面的不同主屏幕,主主屏幕可以是主屏幕中的第一个主屏幕。 主屏幕可能会显示快捷方式图标 191 - 1 , 191 - 2 , 和 191 - 3 用于执行常用应用程序,主菜单转换键 191 - 4 、当前时间、天气信息等。如果用户选择主菜单转换键 191 - 4 , 触摸屏上显示菜单画面 190 . 状态栏 192 代表移动终端的状态 100 可在触摸屏上方显示电池充电状态、接收信号强度、当前时间等 190 . [0091] 一个主页按钮 161 a , 一个菜单按钮 161 b , 和一个后退按钮 161 c 可能会显示在触摸屏的下部 190 . 主页按钮 161 a 用于在触摸屏上显示主主屏幕 190 . 例如,如果主页按钮 161 a 当触摸屏上显示除主主屏幕或菜单屏幕之外的另一个主屏幕时选择 190 , 主屏幕可能会显示在触摸屏上 190 . 如果主页按钮 161 a 在触摸屏上执行应用程序时选择 190 ,主屏幕如图所示。 2 可在触摸屏上显示 190 . 主页按钮 161 a 可用于在触摸屏上显示最近使用的应用程序 190 或在触摸屏上显示任务管理器 190 . [0092] 菜单按钮 161 b 提供可在触摸屏上显示的链接菜单 190 . 链接菜单可以包括小部件添加菜单、锁屏改变菜单、搜索菜单、编辑菜单、设置菜单等。 [0093] 后退按钮 161 c 可用于显示恰好在当前正在执行的屏幕之前执行的屏幕或终止最近使用的应用程序。 [0094] 第一台相机 151 , 环境光传感器 170 a , 和一个接近传感器 170 b 可以设置在移动终端正面的一个边缘部分 100 . 第二台相机 152 , 闪光 153 , 和扬声器 163 可以设置在背面 103 移动终端的 100 . [0095] 在移动终端的侧面 102 ,例如,电源/锁定按钮 161 d , 音量按钮 161 e 包括一个音量增大按钮 161 f 和一个音量减小按钮 161 g ,地面DMB天线 141 a 用于接收广播,一个或多个麦克风 162 等。 DMB 天线 141 a 可以固定或可拆卸地附在移动终端上 100 . [0096] 连接器 165 形成在移动终端下端的侧面 10 . 连接器 165包括多个电极,并且可以通过线路连接到外部设备。 耳机连接插孔 167 可以形成在移动终端上端的侧面 100 . 耳机可插入耳机连接插孔 167 . [0097] 输入单元 168 可安装在移动终端下端的侧面 100 . 输入单元 168 可插入移动终端内部 100 并存储在移动终端中 100 ,而在使用时,输入单元 168 与移动端分离 100 . [0098] 随着用户在移动终端上以各种形式显示多个视觉对象的愿望的增加 100 通过上述结构,例如,在相册应用的情况下,用户可以通过轻弹或拖拽手势在将图片排列在布局的预定区域的屏幕上翻页的同时查看许多图片。 触摸屏 190 . [0099] 然而,为了让用户改变图片的排列和显示图片的区域,用户必须在编辑屏幕上编辑层,这可能需要很长时间。 此外,用户倾向于将关联图片收集到特定文件夹中,以便轻松快速地找到想要的图片或关联图片。 [0100] 因此,根据本发明的示例性实施例,提供了一种用于在触摸屏上容易且快速地改变由显示视觉对象的区域组成的布局的方法和设备 190 ,根据移动终端的动作 100 当用户选择特定对象时,提供一种布局,在该布局中,考虑到所选对象的属性,显示与所选对象相关联的对象。 [0101] 如图。 图4是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 [0102] 参考图。 参照图4,将参照图1和图4所示的示例来描述改变构成布局的区域的方法。 然而,在图5A至8B中,该方法不限于图5A至图8B中所示的示例。 5A到8B。 此外,根据本发明的示例性实施例,例如,当执行故事专辑应用程序时,将作为示例描述显示被划分为预定数量的区域的布局并改变布局的组件的方法。 然而,对于本领域普通技术人员来说显而易见的是,可以将根据移动终端的运动改变布局的组件的方法应用于各种显示屏幕。 [0103] 在步骤 400 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 . 在本说明书中,配置布局的“区域”也可以称为“网格”、“部分”等。 [0104] 图 图5A到8B示出了根据本发明示例性实施例的用于解释构成布局的区域根据移动终端的往复运动的方向改变的处理的示例。 [0105] 参考图。 参见图 5A-8B, 图5A示出了在触摸屏上显示对象的显示屏的示例 190 布局由区域 A、B、C 和 D 组成。可在各个区域上显示的对象可能包括图片、插图、字母(字体、类型)、字符等组件,还包括各种 视觉对象,例如各种内容(例如,文本)、用于执行应用程序的快捷图标、小部件、表示具有各种文件格式的文档的图标、文件夹等。对象还可以包括从视觉对象中选择的一些视觉对象。 [0106] 当显示画面如图所示。 如图5A所示,用户可以通过摇动移动终端来改变布局区域的排列 100 与移动终端 100 在用户手中。 在步骤 405 , 控制器110 判断移动终端是否往复运动 100 通过传感器模块检测到 170 . 如果移动终端的往复运动 100 检测到,然后在步骤中确定检测到的往复运动的方向 410 . 控制器 110 判断移动终端往复运动的方向是否 100 基于通过传感器模块收集的传感器信号对应于上下方向、左右方向和对角方向中的哪个方向 170 . 在步骤 415 , 控制器 110 根据确定的往复运动方向改变构成布局的区域,并在步 420 , 控制器 110 显示使用更改区域重新配置的布局。 [0107] 如图。 图5B示出了当用户摇动移动终端时的示例 100 在左右方向 500 , 左右方向对齐的区域排列 500 根据本发明的示例性实施例改变。 [0108] 参考图。 5B,如果用户摇动移动终端 100 在左右方向上预定次数(例如一次或两次) 500 与移动终端 100 在用户手中时,屏幕如图所示。 显示图5A,在左右方向上对齐的区域排列 500 在布局更改的区域之间。 在图。 在图5A中,区域A、B、C和D中的区域B和C对应于可以根据左右方向上的往复运动而改变的区域 500 ,因此,在左右方向的往复运动之后 500 执行后,区域B和C的布置改变如图6所示。 5B。 显示在图1的区域B中的对象。 图5A移动到并显示在图5的区域B中。 图5B的区域C中显示的对象。 图5A移动到并显示在图5的区域C中。 5B。 [0109] 图 图6A到6B示出了当用户摇动移动终端时的示例 100 在上下方向 600 ,根据本发明的示例性实施例,沿上下方向排列的区域的排列发生变化。 [0110] 参考图。 如图 6A 和 6B 所示,如果在上下方向上往复运动 600 当显示配置有区域 A、B、C 和 D 的布局屏幕时,执行如图 10 所示。 图6A,上下方向排列的区域排列 600 如图所示的变化。 6B。 如果上下方向往复运动 600 执行,图的区域B和C。 图6A移动到图6的上部区域。 在图6B中,区域D对应于图6的下部区域。 图6A移动到图6的中心区域。 图6B的区域A,图6B的区域A。 图6A移动到图6的下部区域。 6B(即,到图6B的区域A)。 下面参照图1至图3描述区域的排列规则。 10 和 11。 [0111] 图 图7A和7B示出了当用户摇动移动终端时的示例 100 在对角线方向 700 ,根据本发明的示例性实施例,沿对角线方向排列的区域的排列发生变化。 [0112] 参考图。 如图 7A 和 7B 所示,如果沿对角线方向往复运动 700 当屏幕如图 3 所示时执行。 显示图7A的区域A,显示图7A的区域A。 图7A移动到图7的区域A。 图7B的区域D和图7B的区域D。 图7A移动到图7的区域D。 7B。 [0113] 图 图8A和8B示出了当用户摇动移动终端时的示例 100 ,除触摸区域外的其余区域的排列发生变化。 如图。 图8A示出了用于说明用户摇动移动终端的情况的画面示例 100 在对角线方向 805 在保持对区域A的触摸的同时。在这种情况下,除了图1中的区域A之外的其余区域B、C和D的布置可以保持在区域A上。 保持触摸的图8A的变化如图8A所示。 8B。 [0114] 如果用户晃动移动终端 100 同时保持对用户所需区域的触摸 800,只有触摸的区域是固定的。 类似地,如果用户在两个或多个区域上保持触摸,则对应的区域也是固定的。 例如,如果用户手持移动终端 100 用双手晃动移动终端可能会让用户感到困难或不舒服 100 在一个特定的方向。 在这种情况下,可以使用用户拉/推移动终端的动作来改变布局的配置 100 朝向/反对用户、倾斜运动等。 [0115] 上述示例性实施例如图1和2所示。 图5A到7B涉及布局的配置根据用户摇动移动终端的往复运动而改变的情况 100 左右方向、上下方向、对角线方向。 然而,也可以根据其他各种动作来改变布局的配置,例如拉/推移动终端的动作 100 水平,倾斜运动,旋转运动等。 图5A到8B涉及根据预定动作改变布局配置的方法。 然而,改变布局的配置的方法不限于以上参照图1至图3描述的方法。 5A到8B。 例如,可以使用呼吸来改变布局的配置。 [0116] 图 图9A到9D示出了用于解释根据本发明示例性实施例的构成布局的区域根据呼吸改变的处理的示例。 [0117] 参考图。 9A-9D,如果用户在一个方向吹他/她的呼吸 900 朝向显示由区域A、B、C和D组成的布局的屏幕,如图1所示。 在图9A中,如图9A所示,显示区域A、B、C和D响应用户的呼吸而吹散的屏幕,好像这些区域是从屏幕上吹出的纸一样。 9B。 依次如图所示。 如图9C所示,显示区域A、B、C和D的布置响应于用户的呼吸而改变的屏幕,并且如图9C所示。 参照图9D,显示具有改变了区域A、B、C和D的布置的布局的屏幕。 如上所述,图。 图9A至9D涉及考虑“吹纸”的应用示例,“吹纸”是各种呼吸行为中的一种简单、直接的行为。 图9A至9D示出了显示交互图像的情况,其中区域响应于用户的呼吸而吹散,就好像纸张吹散一样。 因此,用户可以具有控制屏幕区域的体验,就好像用户实际上是在吹纸一样。 根据本发明的示例性实施例,屏幕的内容可以根据用户呼吸的强度而变化。 [0118] 根据本发明的另一示例性实施例,构成布局的区域可以通过检测预定手势(例如,好像翻页的手势)来改变。 这种姿势可以由相机传感器、环境光传感器等检测。 图 1 和 3 中所示的示例。 如上所述,图5A到9D涉及使用动作或呼吸重新配置布局的情况,然而,当相机传感器、环境光传感器等接收到与各种行为有关的输入时,也可以重新配置布局。 [0119] 如上所述,当用户摇动移动终端时 100 或者对着移动终端的屏幕呼吸 100 ,屏幕上显示的图像会根据移动终端的动作而变化 100 或用户的呼吸,使用户无需操作按钮即可轻松快速地排列对象,感受图像的生动变化。 [0120] 可以使用如下所述的排列规则重新排列布局的组件。 [0121] 图 图10A至图10D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0122]参考图。 参照图10A-10D,根据区域大小的排列规则是将显示在较大区域上的对象移动到较小区域并且将显示在较小区域上的对象移动到较大区域的方法。 如图。 图10A示出了其中区域A具有最大尺寸并且区域B和C具有小于区域A的尺寸的屏幕。如果移动终端的往复运动 100 例如,当屏幕如图1所示时,检测到上下方向的往复运动。 在显示图10A时,显示在具有大尺寸的区域A中的对象移动到具有小尺寸的区域A,如图10A所示。 10B 步中 1000 ,并且显示在具有小尺寸的区域C中的对象移动到具有大尺寸的区域C,如图5所示。 10B 步中 1005 . 根据排列规则,每当移动终端有动作 100 当检测到如图 3 所示的屏幕时。 在显示图10A的情况下,布局的配置按照图10的顺序改变。 参照图10B至图10。 10D。 [0123] 图 图11A至11D是用于解释根据本发明示例性实施例的布局的布置规则的视图。 [0124] 参考图。 如图11A-11D所示,在水平拍摄图像和垂直拍摄图像的情况下,优选水平拍摄图像位于水平区域,而垂直拍摄图像位于垂直区域。 如图。 图11A示出了区域A是水平区域并且区域B和C是垂直区域的示例。 在这种情况下,最好是水平物体 1100 分配到区域 A 并显示在区域 A 中,垂直对象 1102 和 1105 被分配到区域B和C并显示在区域B和C中。根据本发明的示例性实施例,关于对象具有水平格式或垂直格式的每个对象的属性是对象的唯一属性并且可以被识别 提前。 因此,控制器 110 考虑到对象的属性,将每个对象定位在与对象对应的区域。 当执行智能相册应用程序时,控制器 110 可以确定必须显示的对象的数量,从页面具有不同区域排列的多个布局中选择与对象的数量和对象的属性相对应的布局,并提供选择的布局。 [0125] 如果检测到运动时出现如图所示的画面。 在显示图11A的情况下,可以显示具有改变的区域布置的布局,如图11A所示。 11B。 如果一个对象显示在图 C 的区域中。 11A是垂直物体 1105 , 垂直物体 1105 可以显示虽然垂直对象 1105 移动到图1的区域C。 11B。 垂直物体 1105 可以显示在图3的区域C中。 11B 虽然零件 1110 垂直物体的 1105 被截断且未显示。 [0126] 随后,如果再次检测到运动,则如图3所示的布局。 图11B改变为具有如图11所示布置的布局。 11C。 即,由于显示在图2的区域B中的对象。 11B对应垂直物体 1105 显示在图 2 的区域 B 中。 如图11A所示,对象可以移动到图11的区域B并显示在区域B上。 11C。 然而,由于对象显示在图1的区域A中。 11B对应于水平物体 1100 显示在图 1 的区域 A 中。 如图11A所示,对象不能移动到图11的区域A并显示在区域A上。 11D。 当水平物体 1100 位于图A的区域A中。 11D,零件 1115 水平物体的 1100 被切断,同时在区域A中出现空白。这种具有比预定允许的比例失配程度更大的比例失配程度的区域优选在搬迁对象时排除。 因此,图1中所示的布局。 11D 不包括在可选择以更改布局的布局中。 因此,通过考虑每个对象的属性来改变布局,可以在屏幕的区域上适当地布置诸如肖像、风景等的组件,同时保持每个组件的比例。 [0127]如图。 图12是用于解释根据本发明示例性实施例的在移动终端中改变构成布局的区域的方法的流程图。 在下文中,将参考图10描述根据触摸对象的属性改变在构成布局的区域中显示的对象的方法。 然而,如图12所示,该方法不限于图12所示的示例。 12. [0128] 参考图。 1和12,在步骤 1200 , 控制器 110 在触摸屏上显示由显示对象的区域组成的布局 190 移动终端的 100 . 在步骤 1205 , 控制器 110 确定至少一个区域是否已被输入设备触摸。 如果至少触摸了一个区域,则在步骤 1210 控制器 110 判断移动终端是否往复运动 100 被检测到。 如果移动终端的往复运动 100 被检测到,然后在步骤 1215 控制器 110 搜索与属于触摸区域的对象的属性相对应的对象。 如果在步骤中确定 1205 没有接触过任何区域,或者是否在步骤中确定 1210 没有检测到往复运动,则过程返回步骤 1200 并保持布局。 [0129] 在步骤 1220 , 控制器 110 将找到的对象排列在除显示触摸对象的区域之外的其余区域中,并在步骤 1225 , 控制器 110 显示重新配置的布局,其中包含排列找到的对象的区域。 如果没有检测到往复运动,则过程返回操作 1200 ,并且布局保持不变。 [0130] 在上述本发明的示例性实施例中,步骤 1215 搜索关联对象的步骤在步骤之后执行 1210 在保持触摸的同时检测往复运动; 然而,当至少一个区域被触摸时,也可能搜索与属于该区域的对象相关联的对象。 [0131] 图 图13A和13B示出了用于解释根据本发明示例性实施例的根据被触摸对象的属性将不同对象分别显示在构成布局的区域上的处理的示例。 [0132] 参考图。 参照图13A和13B,除了基于位置布置对象的方法之外,还可以采用根据对象的属性布置关联对象的各种方法。 这样的方法包括基于人来布置对象的方法、基于社交网络来布置对象的方法等。 [0133] 在基于人的布置对象的方法的情况下,如果用户摇动移动终端 100 同时保持对移动终端屏幕上显示的图片上特定人的触摸 100 ,则与被触摸的人相关联的图片可以被重新排列以配置当前页面的布局。 显示多人图片时,允许用户在人群中只选择一个人,如果用户摇晃移动终端 100 在保持触摸特定人的同时,可以搜索与特定人相关联的图片并在各个重新排列的区域上显示。 在基于社交网络的排列对象的方法的情况下,例如,如果选择了facebook feed功能,则可以重新排列相应的Facebook feed以适合相应页面的布局区域。 [0134] 如图。 图13A示出了由地图区域和区域A、B和C组成的布局。如果用户触摸地图区域并摇动移动终端 100 同时保持对地图区域的触摸 1300 ,可以根据对象的属性搜索与属于地图区域的对象相关联的对象,并且可以将找到的对象排列并显示在各个区域上,如图3所示。 13B。 例如,如果用户摇动移动终端 100在地图区域按住“纽约时代广场”的同时,与“纽约时代广场”相关联的对象,例如在该地点拍摄的照片、该地点的相关新闻、该地点推荐的应用项目, 等可以布置在各个区域上,如图1所示。 13B。 [0135] 图 图14A和14B是用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的方法的流程图。 图 图15A到15I示出了根据本发明示例性实施例的用于解释在移动终端中调整构成布局的区域数量的处理的示例 [0136] 参考图。 参见图14A和14B以及图14A和14B。 参照图15A-15I,图15的过程。 图14B跟随图14的过程。 14A。 为了便于理解,将参考图1至图3描述调整区域数量的方法。 图15A至15I; 然而,该方法不限于图1和图2所示的示例。 15A至15I。 [0137] 在步骤 1400 , 控制器 110 显示由触摸屏上显示对象的区域组成的布局 190 . 在步骤 1405 , 控制器 110 判断是否接收到改变区域数量的请求。 用户可以通过按下诸如音量键之类的特定键或通过位于屏幕上部的操作栏上显示的选项功能来发送改变区域数量的请求。 如果收到更改区域数量的请求,则在步骤 1410 , 控制器 110 显示用于调整区域数量的图标。 如果没有收到更改区域数量的请求,则返回步骤 1400 . 在步骤 1415 , 控制器 110 确定是否触摸了任何一个图标。 [0138] 如果在操作中确定 1415 如果没有检测到触摸输入,则过程返回操作 1410 . 如果选择了用于添加区域的图标,则在步骤 1420 图。 14B、控制器 110 确定在触摸用于添加区域的图标时是否检测到往复运动。 如果检测到往复运动,则在运行中 1425 , 控制器 110 将构成下一页布局的区域添加到构成当前页面布局的区域中,并且在步骤 1440 , 控制器 110 显示重新配置的布局以包括添加的区域。 如果在触摸区域添加图标时重复检测到往复运动,则控制器 110 每当检测到往复运动时,逐步添加区域。 [0139] 图 图15A至图15I示出了用于说明根据移动终端的动作调整构成布局的区域的数量以及改变区域的布置的过程的示例 100 ,根据本发明的示例性实施例。 如果接收到调整区域数量的请求,则在如图 10 所示的屏幕。 显示图15A,区域添加图标 1510 和一个区域移除图标 1510 如图所示显示。 15B。 如果用户晃动移动终端 100 同时保持触摸区域添加图标 1510 ,添加区域D,如图3所示。 在图15C中,A、B和C区域被重新排列。 如果用户晃动移动终端 100 再次,添加区域E,如图4所示。 15D,其余区域重新排列。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 保持15D。 因此,如果构成在页面上显示的布局的区域的数量增加,则将减少总页面数量,因为要显示的对象的数量已经设置。 [0140] 如果在步骤中未触摸区域添加图标 1430 , 控制器 110 确定在区域移除图标被触摸时是否检测到往复运动。 如果在触摸区域移除图标时检测到往复运动,则在操作中 1435 控制器 110从构成当前页面布局的区域中删除一个区域,并在操作中 1440 , 控制器 110 显示用剩余区域重新配置的布局。 如果在区域移除图标时反复检测到往复运动 1500 被触摸时,每当检测到往复运动时,区域就会逐步移除。 [0141] 如果用户晃动移动终端 100 同时保持触摸区域移除图标 1500 如图所示。 在图15F中,去除了D区域,如图15F所示。 15G,A、B、C区域重新排列。 当用户摇动移动终端时 100 同时保持触摸区域移除图标 1500 ,由于已经设置了最小区域数,因此区域数可能不会改变,如图3所示。 15H。 在这种情况下,区域的排列会发生变化。 此后,如果在预定时间段内没有检测到运动,则如图3所示的布局。 15I 保持不变。 因此,如果减少在页面上显示的构成布局的区域的数量,则页面的总数将增加以显示预定数量的对象。 [0142] 运行中 1430 ,如果在没有触摸区域添加/删除图标时检测到往复运动,则在操作中 1445 控制器 110 根据往复运动方向的方向改变构成布局的区域,如图1和2所示。 5至7,并在运行 1450 , 控制器 110 显示使用更改区域重新配置的布局。 [0143] 上述示例是使用图标增加或减少页面上显示的区域数量的情况; 然而,也可以采用其他方法,例如使用音量增大/减小键添加或删除区域的方法。 例如,一个区域可能是如果用户摇动移动终端 100 如果用户摇动移动终端,同时按住音量增大键并移除区域 100 按住音量减小键的同时。 [0144] 如图。 图16是用于说明在移动终端中调整构成布局的区域数的方法的流程图 100 ,根据本发明的示例性实施例。 图 图17A到17C示出了用于解释根据本发明示例性实施例的在移动终端中调整构成布局的区域数量的处理的示例。 [0145] 参考图。 参见图 16 和 17A-17C,因为步骤 1600 和 1605 步骤相同 400 和 405 图。 在图4中,将省略其详细描述。 运行中 1610 ,确定往复运动的次数是否等于或大于预定次数。 如果往复运动的次数等于或大于预定次数,则在步骤 1615 包括在下一页的布局中的预定数量的区域被添加到构成当前页面的布局的区域中。 运行中 1620 , 控制器 110 显示重新配置的布局以包括添加的区域。 可以根据往复运动的次数确定添加的区域的数量。 [0146] 如图。 图17A示出了当前页面的布局由区域A、B、C和D构成的情况,而图17A示出了当前页面的布局配置有区域A、B、C和D的情况。 图17B示出了下一页面的布局由区域E、F、G、H和I配置的情况。当前页面是显示在触摸屏上的页面 190 , 下一页是轻弹或拖动触摸屏手势时将显示的页面 190从用户接收。 因此,如果在当前页面如图1所示时检测到一个或多个往复运动。 如图17A所示,下一页的区域E和F如图17所示。 如图17B所示,根据往复运动的次数将图17B的区域添加到当前页面的区域。 如图17C所示,同时,区域A、B和C根据往复运动的方向重新排列。 这些区域可以一个一个地添加,也可以以预定数量为单位添加。 当区域被添加到当前页面时,在下一页的区域E和F上显示的对象如图4所示。 如图17B所示,图17B移动到区域E和F并显示在区域E和F上。 17C。 [0147] 如上所述,根据本发明的示例性实施例,用户可以使用移动终端的动作以他/她的期望模式直观地布置布局的组件(即,区域/对象) 100 . 因此,根据本发明的示例性实施例,用户可以根据移动终端的动作容易且快速地将显示在移动终端的屏幕上的多个对象的排列改变为用户期望的图案。 此外,由于可以通过移动终端的简单动作的输入来改变布置对象的布局的配置,所以可以最大化用户的便利性。 [0148] 此外,由于可以通过考虑对象的属性来配置布局来提供由期望的对象组成的布局,因此可以提供具有统一顺序的个性化布局。 [0149] 本发明的示例性实施例可以以硬件、软件或硬件和软件的组合的形式来实现。 软件可以存储在易失性或非易失性存储设备中,例如 ROM,不管它是可擦除的还是可重写的,存储在诸如 RAM、存储芯片、 和集成电路 (IC),或在光/磁可记录和机器可读的存储介质中,例如压缩盘 (CD)、数字多功能盘 (DVD)、磁盘和磁带 . 可以包括在移动终端中的存储器是适用于存储一个或多个程序的非暂时性机器可读存储介质的示例,包括实现本发明示例性实施例的指令。 因此,本发明的示例性实施例包括包括用于实现如说明书的所附权利要求中所述的设备和方法的代码的程序,以及存储这些程序的机器可读存储介质。 [0150] 此外,移动终端可以从以有线/无线方式连接的程序提供装置接收和存储程序。 程序提供设备可以包括:存储器,用于存储程序,该程序包括用于执行根据移动终端的动作控制多个对象的显示的方法的指令;通信单元,用于与移动终端进行有线/无线通信; 控制器,用于根据移动终端的请求或自动向移动终端发送程序。 [0151] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2014219558A1(String), AU2014219558B2(String), BR112015020243A2(String), BR112015020243B1(String), CN104007892A(String), CN104007892B(String), CN110333758A(String), EP2770424A2(String), EP2770424A3(String), EP2770424B1(String), EP3696653A1(String), EP3696653B1(String), IN2703MUMNP2015A(String), IN407024B(String), JP2016511471A(String), JP2019083048A(String), JP6816858B2(String), KR1020140105344A(String), KR102146244B1(String), MX2015010598A(String), MX353242B(String), RU2015140072A(String), RU2667496C2(String), US10775896B2(String), US20140245234A1(String), US20190121443A1(String), VN10030622B(String), VN44787A(String), WO2014129862A1(String), ZA201505799A(String), ZA201505799B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 31 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), AU2014219558A1(String), 1049716(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), AU2014219558B2(String), 1049717(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), BR112015020243A2(String), 1049718(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), BR112015020243B1(String), 1049719(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), CN104007892A(String), 1049720(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), CN104007892B(String), 1049721(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), CN110333758A(String), 1049722(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), EP2770424A2(String), 1049723(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), EP2770424A3(String), 1049724(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.852 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.852 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.852 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), EP2770424B1(String), 1049725(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), EP3696653A1(String), 1049726(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), EP3696653B1(String), 1049727(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.953 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.953 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), IN2703MUMNP2015A(String), 1049728(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:44.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), IN407024B(String), 1049729(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), JP2016511471A(String), 1049730(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), JP2019083048A(String), 1049731(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), JP6816858B2(String), 1049732(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), KR1020140105344A(String), 1049733(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), KR102146244B1(String), 1049734(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), MX2015010598A(String), 1049735(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), MX353242B(String), 1049736(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), RU2015140072A(String), 1049737(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), RU2667496C2(String), 1049738(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), US10775896B2(String), 1049739(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), US20140245234A1(String), 1049740(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), US20190121443A1(String), 1049741(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), VN10030622B(String), 1049742(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), VN44787A(String), 1049743(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), WO2014129862A1(String), 1049744(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.521 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.522 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), ZA201505799A(String), 1049745(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271652(Integer), ZA201505799B(String), 1049746(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20140245234A1(String), US20140245234A1(String), 1409155200(Integer), 271652(Integer), 185963(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185967(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185967(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185967(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185967(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.874 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.874 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.874 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.996 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:45.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9565293B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and device for operating mobile terminal based on sensor, and mobile terminal(String), 基于传感器的移动终端操作方法、装置及移动终端(String), US9565293B2(String), A method for operating a mobile terminal based on a sensor is disclosed. The method includes: a sensor is triggered according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, ab operation type, which is corresponding to the digital signal, of the mobile terminal is determined; and a corresponding operation process is performed on the mobile terminal according to the operation type. The disclosure also provides a corresponding device and a mobile terminal including the device. The method for operating the mobile terminal based on the sensor provided in the disclosure completes power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler.(String), 公开了一种基于传感器操作移动终端的方法。 该方法包括:根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; 接收到传感器输出的与触发规则对应的数字信号后,确定该数字信号对应的移动终端的操作类型ab; 根据操作类型对移动终端进行相应的操作过程。 本发明还提供了相应的装置和包括该装置的移动终端。 本发明提供的基于传感器的移动终端操作方法通过传感器完成对移动终端的开机/关机、唤醒、休眠等操作,从而在制作结构的同时给用户带来更好的使用体验。 移动端的更简单。(String), US14/399993(String), 1342368000(Integer), US9565293B2(String), 1486396800(Integer), 1486396800(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 18(Integer), CN101002175A | CN101101523A | CN101847055A | CN101937316A | CN102265253A | US20020173299A1 | US20060005156A1 | US20070161400A1 | US20090143103A1 | US20100123664A1 | US20100245282A1 | US20110183601A1 | US20110238191A1 | US20110244844A1 | US20120019390A1 | US20120306770A1 | US20130063611A1 | WO2012054005A1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185968(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.713 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.713 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0b2303da79fa4570a0a6f7f35cdce657.png(String), 185968(Integer), 0b2303da79fa4570a0a6f7f35cdce657.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and device for operating mobile terminal based on sensor, and mobile terminal(String), 基于传感器的移动终端操作方法、装置及移动终端(String), US9565293B2(String), A method for operating a mobile terminal based on a sensor is disclosed. The method includes: a sensor is triggered according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, ab operation type, which is corresponding to the digital signal, of the mobile terminal is determined; and a corresponding operation process is performed on the mobile terminal according to the operation type. The disclosure also provides a corresponding device and a mobile terminal including the device. The method for operating the mobile terminal based on the sensor provided in the disclosure completes power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler.(String), 公开了一种基于传感器操作移动终端的方法。 该方法包括:根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; 接收到传感器输出的与触发规则对应的数字信号后,确定该数字信号对应的移动终端的操作类型ab; 根据操作类型对移动终端进行相应的操作过程。 本发明还提供了相应的装置和包括该装置的移动终端。 本发明提供的基于传感器的移动终端操作方法通过传感器完成对移动终端的开机/关机、唤醒、休眠等操作,从而在制作结构的同时给用户带来更好的使用体验。 移动端的更简单。(String), US14/399993(String), 1342368000(Integer), US9565293B2(String), 1486396800(Integer), 1486396800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 18(Integer), CN101002175A | CN101101523A | CN101847055A | CN101937316A | CN102265253A | US20020173299A1 | US20060005156A1 | US20070161400A1 | US20090143103A1 | US20100123664A1 | US20100245282A1 | US20110183601A1 | US20110238191A1 | US20110244844A1 | US20120019390A1 | US20120306770A1 | US20130063611A1 | WO2012054005A1(String), \20230420\0b2303da79fa4570a0a6f7f35cdce657.png(String), 12(Integer), 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 1. A method for operating a mobile terminal based on a sensor, comprising:presetting a plurality of trigger rules for triggering the sensor according to a plurality of operation types of the mobile terminal;triggering the sensor according to one of the plurality of trigger rules to make the sensor output a digital signal corresponding to the trigger rule;determining an operation type, which is corresponding to the digital signal, of the mobile terminal, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor; andperforming a corresponding operation process on the mobile terminal according to the operation type,wherein after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal comprises:determining that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;determining that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anddetermining that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1.移动终端,包括8.根据权利要求7所述的基于传感器操作移动终端的装置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 2. The method according to claim 1, wherein the plurality of operation types of the mobile terminal comprises at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system.(String), 12.移动终端,包括9.根据权利要求8所述的基于传感器操作移动终端的装置。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 3. The method according to claim 2, wherein the plurality of trigger rules comprises a long press, a click and a double-click; wherein,an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off;an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; andan operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep.(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 4. The method according to claim 3, wherein after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal comprises:determining that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;determining that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anddetermining that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 5. The method according to claim 2, wherein after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal comprises:determining that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;determining that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anddetermining that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 6. A device for operating a mobile terminal based on a sensor, comprising:a presetting component to preset a plurality of trigger rules for triggering the sensor according to a plurality of operation types of the mobile terminal;a triggering component to trigger a sensor according a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule;a determining component to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine an operation type, which is corresponding to the digital signal, of the mobile terminal; andan operating component to perform a corresponding operation process on the mobile terminal according to the operation type,wherein the determining component comprises:a first determining unit to-determine that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;a second determining unit to determine that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anda third determining unit determine that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 7. The device according to claim 6, wherein the operation types of the mobile terminal comprise at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 8. The device according to claim 7, wherein the plurality of trigger rules comprises: a long press, a click and a double-click; wherein,an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off;an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; andan operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 9. The device according to claim 7, wherein the determining component comprises:a first determining unit to-determine that the operation type of the mobile terminal is power-on or power-off when the trigger rule corresponding to the digital signal is the long press, after receiving the digital signal;a second determining unit to determine that the operation type of the mobile terminal is going to the main menu of system, when the trigger rule corresponding to the digital signal is the click; anda third determining unit to determine that the operation type of the mobile terminal is wakeup or sleep, when the trigger rule corresponding to the digital signal is the double-click.(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 10. A mobile terminal, comprising the device for operating the mobile terminal based on the sensor according to claim 6.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 11. A mobile terminal, comprising the device for operating the mobile terminal based on the sensor according to claim 7.(String), 1(Integer), 10(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:46.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185968(Integer), 12. A mobile terminal, comprising the device for operating the mobile terminal based on the sensor according to claim 8.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185968(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of communications, and more particularly to a method and device for operating a mobile terminal based on a sensor, and a mobile terminal. BACKGROUND [0002]With higher and higher requirement of people on function and appearance of a mobile terminal, the appearance and production of a mobile terminal become more and more exquisite. At present, the most obvious change of a mobile terminal is that the past keypad is gradually replaced by a touch screen. However, despite this, the increasing aesthetic demand of a user is not satisfied; therefore, the current manufactured mobile terminal is equipped with as few keys as possible or not equipped with key at all. [0003]Currently, most mobile terminals with touch screen mainly include a home key, a power-on key, several function keys at side of the mobile terminals, and so on. However, these mobile terminals usually start a system through an entity power button; the specific method is that: an entity power button is connected with a Power Management Unit (PMU); the PMU will be triggered after long press of the entity power button, and a Main Control Unit (MCU) is powered through the PMU, so as to maintain normal running of the MCU, thus, to complete start-up of a terminal system; when powering off, it is implemented by long press of the entity power button. But, using an entity power button to power on or off a mobile terminal makes the structure of the mobile terminal not simple enough, and can not bring better use experience to a user. SUMMARY [0004]The disclosure provides a method and device for operating a mobile terminal based on a sensor, and a mobile terminal, so as to complete power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor, and bring better use experience to a user while making the structure of the mobile terminal simpler. [0005]The disclosure provides a method for operating a mobile terminal based on a sensor, and the method includes: [0006]the sensor is triggered according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0007]after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, an operation type, which is corresponding to the digital signal, of the mobile terminal is determined; and [0008]a corresponding operation process is performed on the mobile terminal according to the operation type. [0009]Before triggering the sensor according to the preset trigger rule, the method may further include that: [0010]according to a plurality of operation types of the mobile terminal, a plurality of trigger rules for triggering a sensor are preset. [0011]The plurality of operation types of the mobile terminal may include at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system. [0012]The trigger rule may include long press, click or double-click, wherein, an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off; [0013]an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; and [0014]an operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep. [0015]After receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determining the operation type, which is corresponding to the digital signal, of the mobile terminal may include: [0016]after receiving the digital signal, it is determined that the operation type of the mobile terminal is power-on or power-off if the trigger rule corresponding to the digital signal is long press; [0017]if the trigger rule corresponding to the digital signal is click, it is determined that the operation type of the mobile terminal is going to the main menu of system; and [0018]if the trigger rule corresponding to the digital signal is double-click, it is determined that the operation type of the mobile terminal is wakeup or sleep. [0019]The disclosure also provides a device for operating a mobile terminal based on a sensor, and the device includes: [0020]a triggering component configured to trigger the sensor according a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0021]a determining component configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine the operation type, which is corresponding to the digital signal, of the mobile terminal; and [0022]an operating component configured to perform a corresponding operation process on the mobile terminal according to the operation type. [0023]The device for operating the mobile terminal based on the sensor may further include: [0024]a presetting component configured to preset, according to a plurality of operation types of the mobile terminal, a plurality of trigger rules for triggering a sensor. [0025]The operation types of the mobile terminal may include at least one of the followings: power-on, power-off, wakeup, sleep and going to the main menu of system. [0026]The plurality of trigger rules may include long press, click and double-click; wherein, [0027]an operation type, which is corresponding to the long press, of the mobile terminal is power-on or power-off; [0028]an operation type, which is corresponding to the click, of the mobile terminal is going to the main menu of system; and [0029]an operation type, which is corresponding to the double-click, of the mobile terminal is wakeup and/or sleep. [0030]The determining component may include: [0031]a first determining unit configured to, after receiving the digital signal, determine that the operation type of the mobile terminal is power-on or power-off if the trigger rule corresponding to the digital signal is long press; [0032]a second determining unit configured to, if the trigger rule corresponding to the digital signal is click, determine that the operation type of the mobile terminal is going to the main menu of system; and [0033]a third determining unit configured to, if the trigger rule corresponding to the digital signal is double-click, determine that the operation type of a mobile terminal is wakeup or sleep. [0034]The disclosure further provides a mobile terminal, including the device for operating the mobile terminal based on the sensor; the device includes: [0035]a triggering component configured to trigger the sensor according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0036]a determining component configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine the operation type, which is corresponding to the digital signal, of the mobile terminal; and [0037]an operating component configured to perform a corresponding operation process on the mobile terminal according to the operation type. [0038]The disclosure adopts the sensor to replace a power-on/off button of a mobile terminal or a button for wakeup or sleep of the mobile terminal. Firstly, the sensor is triggered according to the preset trigger rule, and the sensor outputs the digital signal corresponding to the trigger rule; after the digital signal is received, the digital signal is detected to obtain the operation type of the mobile terminal corresponding to the determined digital signal, and a corresponding operation process is performed on a mobile terminal according to the obtained operation type. By adopting such solution, power-on/off, wakeup, sleep and other operations on the mobile terminal are completed through a sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler. BRIEF DESCRIPTION OF THE DRAWINGS [0039]FIG. 1 is a flowchart of a method for operating a mobile terminal based on a sensor in an embodiment of the disclosure; [0040]FIG. 2 is a flowchart of determining an operation type of a mobile terminal in a method for operating the mobile terminal based on a sensor according to an embodiment of the disclosure; [0041]FIG. 3 is a flowchart of a method for operating a mobile terminal based on a sensor according to another embodiment of the disclosure; [0042]FIG. 4 is a structure diagram of a device for operating a mobile terminal based on a sensor according to an embodiment of the disclosure; [0043]FIG. 5 is a structure diagram of a determining component of a device for operating a mobile terminal based on a sensor according to an embodiment of the disclosure; and [0044]FIG. 6 is a structure diagram of a device for operating a mobile terminal based on a sensor according to another embodiment of the disclosure. [0045]The implementation of the aim, the function features and the advantages of the disclosure will be further illustrated in combination with the accompanying drawings and embodiments. DETAILED DESCRIPTION OF THE EMBODIMENTS [0046]It should be understood that specific embodiments described here are only used for illustrating the disclosure and not intended to limit the disclosure. [0047]A method for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 1, the method includes the following steps. [0048]S10: the sensor is triggered according to a preset trigger rule, in order to make the sensor output a digital signal corresponding to the trigger rule. [0049]The method for operating the mobile terminal based on the sensor provided by the embodiment of the disclosure adopts a sensor to replace a power-on/off button in a mobile terminal or a button for wakeup or sleep of the mobile terminal, so as to implement a function of performing corresponding operation on a mobile terminal without any button. In this way, a system of mobile terminal, to which the method for operating the mobile terminal based on a sensor provided by the disclosure may be applied, may include a sensor, a battery, a Power Management Unit (PMU) and a Main Control Unit (MCU), wherein the battery is used for power supply of the PMU and the sensor; the sensor may be provided at any position on the screen of the mobile terminal; the sensor is connected to a pin of the PMU; after the PMU is triggered, it can supply power for the MCU, so as to maintain normal running of the MCU. At the same time, in the present embodiment, it is also needed to integrate in the system of mobile terminal a software processing module which is used for processing digital information output to the MCU by the sensor. [0050]In the present embodiment, when the mobile terminal is operated according to the actual requirement of a user, firstly, the sensor is triggered according to the trigger rule preset in the system of mobile terminal. The trigger rule includes long press, click or double-click, and different trigger rules correspond to different operation types of the mobile terminal. After the sensor is triggered according to different trigger rules, a processing chip in the sensor converts analogue data corresponding to an trigger action into a digital signal corresponding to the trigger rule, and then outputs the digital signal. In the present embodiment, a pressure sensor may be adopted as the provided sensor. Because the sensor is connected to a pin of the PMU, the PMU may be triggered after the sensor is triggered, thus making a battery work for the PMU; at this point, the PMU powers the MCU on to maintain normal running of the MCU. [0051]S20: after the digital signal, which is corresponding to the trigger rule and is output from the sensor is received, an operation type, which is corresponding to the digital signal, of the mobile terminal is determined. [0052]After the digital signal, which is output from the sensor and obtained from conversion performed by a processing chip of the sensor according to the current trigger rule for triggering the sensor, is received, the digital signal is determined, so as to determine the operation type, which is corresponding to the digital signal, of the mobile terminal, and then to get which operation is needed to perform by a user on the mobile terminal now. In the present embodiment, the operation types of the mobile terminal may include: power-on, power-off, wakeup, sleep, going to the main menu of system, and so on; besides, the preset trigger rules for triggering the sensor corresponds to these operation types; that is, an operation type of the mobile terminal corresponding to the long press is power-on or power-off; an operation type of the mobile terminal corresponding to the click is going to the main menu of system; and an operation type of the mobile terminal corresponding to the double-click is wakeup and/or sleep. [0053]S30: a corresponding operation process is performed on a mobile terminal according to the operation type. [0054]After the operation type of the mobile terminal is determined according to the digital signal output from the sensor, it is needed to perform the corresponding operation process which is corresponding to the current operation type. That is, the mobile terminal is powered on or off; and after powering on, wakeup, sleep, going to the main menu and other operations are performed. [0055]The method for operating the mobile terminal based on the sensor provided by the present embodiment adopts a sensor to replace a power-on/off button in a mobile terminal or a button for wakeup or sleep of the mobile terminal. Firstly, the sensor is triggered according to the preset trigger rule, and the sensor outputs the digital signal corresponding to the trigger rule; after the digital signal is received, the digital signal is detected to obtain the operation type, which is corresponding to the digital signal, of the mobile terminal, and the corresponding operation process is performed on the mobile terminal according to the operation type of the mobile terminal corresponding to the digital signal. By adopting this method, power-on/off, wakeup, sleep and other operations on the mobile terminal are completed through a sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler. [0056]A method for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 2, the step S20 includes the following steps: [0057]S21: after a digital signal is received, a trigger rule corresponding to the digital signal is determined according to the digital signal; if the trigger rule corresponding to the digital signal is long press, turn to the step S22; if the trigger rule corresponding to the digital signal is click, turn to the step S23; if the trigger rule corresponding to the digital signal is double-click, turn to the step S24; [0058]S22: the operation type of the mobile terminal is determined to be power-on or power-off; [0059]S23: the operation type of the mobile terminal is determined to be going to the main menu of system; and [0060]S24: the operation type of the mobile terminal is determined to be wakeup or sleep. [0061]In the above embodiment, after the digital signal, which is corresponding to the trigger rule and is output from the sensor, is received, firstly, the trigger rule corresponding to the digital signal is determined according to the digital signal, and then the operation type of the mobile terminal is determined according to the trigger rule. If the trigger rule corresponding to the digital signal is long press, the operation type of the mobile terminal may be determined to be power-on or power-off. In this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically power-on or power-off; if it is power-on, a software processing module which is integrated in the system and used for processing digital information is loaded, so as to enter a normal power-on process to start the mobile terminal; if it is power-off, the software processing module is released, so as to enter a normal power-off process to power the mobile terminal off. [0062]After entering a power-on process by triggering the sensor and starting the mobile terminal, that is, the mobile terminal is in the power on state, a process for making the mobile terminal sleep or wakeup may also be performed on the mobile terminal. Therefore, if a digital signal is received at this point and the trigger rule corresponding to the digital signal is double-click, it may be determined that the operation type of the mobile terminal corresponding to the digital signal at this point is wakeup or sleep. Likewise, in this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically wakeup or sleep; if it is wakeup, a wakeup process is performed to wake the mobile terminal up. [0063]After the mobile terminal is woken up, if the sensor is triggered again, and a digital signal corresponding to a trigger signal is received, a software processing module used for processing the digital signal is needed to process the digital signal, that is, the operation type of the mobile terminal corresponding to the digital signal at this point is determined. If the trigger rule is click, the operation type of the mobile terminal corresponding to the digital signal at this point is going to the main menu, and the software processing module responses the operation type to return the main menu; if the trigger rule is double-click, the software processing module responses the operation type to make the mobile terminal enter a sleep state. [0064]Of course, after the mobile terminal is woken up, the sensor may also be pressed long to make the mobile terminal power off. That is, at this point, the sensor may also output a digital signal corresponding to long press. Then, if the operation type of the mobile terminal corresponding to the digital signal is determined to be power-off through a software processing module, a normal power-off process is performed directly to power the mobile terminal off. [0065]After the digital signal output from the sensor is received, the operation type corresponding to the digital signal is determined. The operation type of the mobile terminal corresponding to the trigger rule is determined according to different trigger rules for triggering the sensor, and a corresponding operation is performed on the mobile terminal according to the determined operation type. In this way, the process of completing power-on/off, wakeup, sleep and other operations on a mobile terminal through a sensor is further perfected, and better use experience is further brought to a user while further ensuring to make the structure of the mobile terminal simpler. [0066]As shown in FIG. 3, a method for operating a mobile terminal based on a sensor is provided according to another embodiment of the disclosure. [0067]Before performing the step S10, the method further includes the following steps. [0068]Step S40: trigger rules for triggering the sensor are preset according to operation types of the mobile terminal. [0069]Because there are many different operation types of the mobile terminal, it is required the sensor to detect different operation types of the mobile terminal when the sensor is adopted to replace a button of the mobile terminal. In this way, before triggering the sensor, it is needed to preset in the system of mobile terminal the trigger rules, which are corresponding to the operation types, for triggering the sensor according to different operation types, wherein the trigger rules includes long press, click and double-click. After the sensor is triggered by using corresponding trigger rule according to the actual requirement of a user, the system of mobile terminal may identify the trigger rule, so as to determine the operation type corresponding to the trigger rule and complete the corresponding operation process. [0070]The trigger rules for triggering the sensor are preset according to several different operation types of the mobile terminal, so that the trigger rule may be identified after triggering the sensor by using the corresponding trigger rule, and the corresponding operation type may be determined. In this way, a more powerful guarantee is provided for using the sensor to implement power-on/off, wakeup, sleep and other operations on the mobile terminal. [0071]As shown in FIG. 4, a device for operating a mobile terminal based on a sensor is provided according to an embodiment of the disclosure and the device includes: [0072]a triggering component 10 configured to trigger the sensor according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0073]a determining component 20 configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine an operation type, which is corresponding to the digital signal, for the mobile terminal; and [0074]an operating component 30 configured to perform a corresponding operation process on the mobile terminal according to the operation type. [0075]The device for operating the mobile terminal based on the sensor provided by the present embodiment adopts the sensor to replace a power-on/off button of the mobile terminal or a button for wakeup or sleep of the mobile terminal, so as to implement a function of performing corresponding operation on the mobile terminal without any button. In this way, a system of mobile terminal to which the method for operating the mobile terminal based on the sensor provided by the disclosure can be applied may include a sensor, a battery, a PMU and an MCU. The battery is used for power supply of the PMU and the sensor. The sensor may be provided at any position on the screen of the mobile terminal. The sensor is connected to a pin of the PMU. After the PMU is triggered, the PMU may supply power for the MCU, so as to maintain normal running of the MCU. At the same time, in the present embodiment, it is also needed to integrate in the system of mobile terminal a software processing module which is used for processing digital information output to the MCU by the sensor. [0076]In the present embodiment, when the mobile terminal is operated according to the actual requirement of the user, firstly, the sensor is triggered by the triggering component 10 according to the trigger rules preset in the system of mobile terminal. The trigger rules include long press, click and double-click; different trigger rules correspond to different operation types of the mobile terminal. After the sensor is triggered according to different trigger rules, a processing chip in the sensor converts corresponding analogue data of a trigger action into a digital signal corresponding to the trigger rule, and then outputs the digital signal. In the present embodiment, a pressure sensor may be adopted as the provided sensor. Because the sensor is connected to a pin of the PMU, the PMU may be triggered after the sensor is triggered, so as to make a battery supply power to the PMU. At this point, the PMU supply power to the MCU to maintain normal running of the MCU. [0077]After the digital signal which is output from the sensor and obtained from conversion performed by a processing chip of the sensor according to the current trigger rule for triggering the sensor, the digital signal is detected by the determining component 20, so as to determine the operation type of the mobile terminal corresponding to the digital signal, and then to get which operation is needed to perform by the user on the mobile terminal now. In the present embodiment, the operation types of the mobile terminal may include: power-on, power-off, wakeup, sleep, going to the main menu of system, and so on; besides, the preset trigger rules for triggering the sensor corresponds to these operation types; that is, the operation type of the mobile terminal corresponding to the long press is power-on or power-off; the operation type of the mobile terminal corresponding to the click is going to the main menu of system; and the operation type of the mobile terminal corresponding to the double-click is wakeup and/or sleep. [0078]After the operation type of the mobile terminal is determined according to the digital signal output from the sensor, the operating component 30 needs to perform a corresponding operation process according to the current operation type. That is, the mobile terminal is powered on or off; and after powering on, wakeup, sleep, going to the main menu and other operations may be performed. [0079]The device for operating the mobile terminal based on the sensor provided by the present embodiment adopts the sensor to replace a power-on/off button of a mobile terminal or a button for wakeup or sleep of the mobile terminal. Firstly, the sensor is triggered according to the preset trigger rule, and the sensor outputs the digital signal corresponding to the trigger rule; after the digital signal is received, the digital signal is detected to obtain the operation type of the mobile terminal corresponding to the determined digital signal, and a corresponding operation process is performed on a mobile terminal according to the obtained the operation type. By adopting this method, power-on/off, wakeup, sleep and other operations on the mobile terminal are completed through the sensor, so as to bring better use experience to a user while making the structure of the mobile terminal simpler. [0080]A device for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 5, the determining component 20 specifically includes: [0081]a first determining unit 21 configured to, if the trigger rule corresponding to the digital signal is long press, determine that the operation type of the mobile terminal is power-on or power-off; [0082]a second determining unit 22 configured to, if the trigger rule corresponding to the digital signal is click, determine that the operation type of the mobile terminal is going to the main menu of system; and [0083]a third determining unit 23 configured to, if the trigger rule corresponding to the digital signal is double-click, determine that the operation type of the mobile terminal is wakeup or sleep. [0084]In the above embodiment, after the digital signal which is corresponding to the trigger rule and is output from the sensor is received, firstly, the trigger rule corresponding to the digital signal is determined according to the digital signal, and then the operation type of the mobile terminal is determined according to the trigger rule. If the trigger rule corresponding to the digital signal is long press, the first determining unit 21 may determine that the operation type of the mobile terminal is power-on or power-off. In this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically power-on or power-off; if it is power-on, a software processing module which is integrated in the system and used for processing digital information is loaded, so as to enter a normal power-on process to power on the mobile terminal; if it is power-off, the software processing module is released, so as to enter a normal power-off process to power the mobile terminal off. [0085]After the mobile terminal enters a power-on process when the sensor is trigged and the mobile terminal is powered on, a process for making the mobile terminal sleep or wakeup may also be performed in a case that the mobile terminal is in a power-on state. Therefore, if the digital signal is received at this point and the trigger rule corresponding to the digital signal is double-click, the third determining unit 23 may determine that the operation type of the mobile terminal corresponding to the digital signal at this point is wakeup or sleep. Likewise, in this case, the MCU needs to further detect the digital signal to get whether the operation type corresponding to the digital signal is specifically wakeup or sleep; if it is wakeup, a wakeup process is performed to wake the mobile terminal up. [0086]After the mobile terminal is woken up, if the sensor is triggered again, and a digital signal corresponding to a trigger signal is received, a software processing module used for processing the digital signal is needed to process the digital signal, that is, the operation type of the mobile terminal corresponding to the digital signal at this point is determined. If the trigger rule is click, the second determining unit 22 may determine that the operation type of the mobile terminal corresponding to the digital signal at this point is going to the main menu, and the software processing module responds by returning the main the menu; if the trigger rule is double-click, the software processing module responds by making the mobile terminal enter a sleep state. [0087]Of course, after the mobile terminal is woken up, the sensor may also be pressed long to power the mobile terminal off. That is, at this point, the sensor may also output a digital signal corresponding to long press. Then, if an operation type of the mobile terminal corresponding to the digital signal is determined to be power-off through the software processing module, a normal power-off process to power the mobile terminal off is performed directly. [0088]After the digital signal output from the sensor is received, the operation type corresponding to the digital signal is determined. The operation type of the mobile terminal corresponding to the trigger rule is determined according to different trigger rules for triggering the sensor, and a corresponding operation is performed on the mobile terminal according to the determined operation type. In this way, the process of completing power-on/off, wakeup, sleep and other operations on the mobile terminal through the sensor is further perfected, and better use experience is further brought to a user while further ensuring to make the structure of the mobile terminal simpler. [0089]A device for operating a mobile terminal based on a sensor is provided in an embodiment of the disclosure. As shown in FIG. 6, the device further includes: [0090]a presetting component 40 configured to preset, according to a plurality of operation types of the mobile terminal, trigger rules for triggering the sensor. [0091]When the sensor is adopted to replace a button of the mobile terminal, because the mobile terminal includes several different operation types, it is required to adopt a sensor to detect different operation types of the mobile terminal. In this way, before triggering the sensor, the presetting component 40 needs to preset in the system of mobile terminal the trigger rules for triggering the sensor corresponding to the plurality of operation types according to different operation types, wherein the trigger rules includes long press, click and double-click. After the sensor is triggered by using corresponding trigger rule according to the actual requirement of a user, the system of mobile terminal may identify the trigger rule, so as to determine the operation type corresponding to the trigger rule and complete corresponding operation process. [0092]The trigger rules for triggering the sensor is preset according to several different operation types of the mobile terminal, so that a trigger rule may be identified after the sensor is trigged by using corresponding trigger rule, and the corresponding operation type may be determined. In this way, a more powerful guarantee is provided for using the sensor to implement power-on/off, wakeup, sleep and other operations on the mobile terminal. [0093]The embodiment of the disclosure further provides a mobile terminal, including a device for operating a mobile terminal based on a sensor; and the device includes: [0094]a triggering component 10 configured to trigger a sensor according to a preset trigger rule to make the sensor output a digital signal corresponding to the trigger rule; [0095]a determining component 20 configured to, after receiving the digital signal which is corresponding to the trigger rule and is output from the sensor, determine an operation type, which is corresponding to the digital signal, of the mobile terminal; and [0096]an operating component 30 configured to per(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种基于传感器的移动终端操作方法、装置及移动终端。 背景 [0002] 随着人们对移动终端的功能和外观的要求越来越高,移动终端的外观和制作也越来越讲究。 目前,移动终端最明显的变化就是过去的键盘逐渐被触摸屏所取代。 然而,尽管如此,仍不能满足用户日益增长的审美需求; 因此,目前制造的移动终端都尽可能少配备按键或根本不配备按键。 [0003] 目前,大多数触摸屏移动终端主要包括主页键、开机键、移动终端侧边的几个功能键等。 然而,这些移动终端通常通过实体电源按钮来启动系统; 具体方法是:实体电源按钮连接电源管理单元(PMU)。 长按实体电源键触发PMU,通过PMU给主控单元(Main Control Unit,MCU)供电,维持MCU正常运行,从而完成终端系统的启动。 关机时,通过长按实体电源键实现。 但是,使用实体电源键来开启或关闭移动终端使得移动终端的结构不够简单,不能给用户带来更好的使用体验。 概括 [0004] 本发明提供了一种基于传感器操作移动终端的方法、装置及移动终端,以通过传感器完成对移动终端的开关机、唤醒、休眠等操作,带来更好的使用体验。 在使移动终端的结构更简单的同时,给用户带来更好的体验。 [0005] 本发明提供了一种基于传感器的移动终端操作方法,该方法包括: [0006] 根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0007] 在接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型。 和 [0008] 根据操作类型对移动终端进行相应的操作处理。 [0009] 在根据预设触发规则触发传感器之前,该方法还可以包括: [0010] 根据移动终端的多种操作类型,预先设置多种触发传感器的触发规则。 [0011] 移动终端的多种操作类型可以包括以下至少一种:开机、关机、唤醒、休眠和进入系统主菜单。 [0012] 触发规则可以包括长按、点击或双击,其中,长按对应的移动终端的操作类型为开机或关机; [0013] 移动终端点击对应的操作类型为进入系统主菜单; 和 [0014] 移动终端双击对应的操作类型为唤醒和/或休眠。 [0015] 在接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型可以包括: [0016] 接收到数字信号后,若数字信号对应的触发规则为长按,则判断移动终端的操作类型为开机或关机。 [0017] 若数字信号对应的触发规则为点击,则判断移动终端的操作类型为进入系统主菜单。 和 [0018] 若数字信号对应的触发规则为双击,则确定移动终端的操作类型为唤醒或睡眠。 [0019] 本发明还提供了一种基于传感器操作移动终端的装置,该装置包括: [0020] 触发组件,用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0021] 判断模块,用于在接收到传感器输出的与触发规则对应的数字信号后,判断移动终端与该数字信号对应的操作类型; 和 [0022] 操作模块,用于根据操作类型对移动终端执行相应的操作过程。 [0023] 基于传感器操作移动终端的装置还可以包括: [0024] 预设模块,用于根据移动终端的多种操作类型,预设多种触发传感器的触发规则。 [0025] 移动终端的操作类型可以包括以下至少一种:开机、关机、唤醒、休眠和进入系统主菜单。 [0026] 多个触发规则可以包括长按、点击和双击; 其中, [0027] 移动终端长按对应的操作类型为开机或关机; [0028] 移动终端点击对应的操作类型为进入系统主菜单; 和 [0029] 移动终端双击对应的操作类型为唤醒和/或休眠。 [0030] 决定性成分可能包括: [0031] 第一判断单元,用于在接收到数字信号后,若数字信号对应的触发规则为长按,则判断移动终端的操作类型为开机或关机; [0032] 第二判断单元,用于若数字信号对应的触发规则为点击,则判断移动终端的操作类型为进入系统主菜单; 和 [0033] 第三判断单元,用于若数字信号对应的触发规则为双击,则判断移动终端的操作类型为唤醒或睡眠。 [0034] 本发明还提供了一种移动终端,包括上述基于传感器的移动终端操作装置; 该设备包括: [0035] 触发组件,用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0036] 判断模块,用于在接收到传感器输出的与触发规则对应的数字信号后,判断移动终端与该数字信号对应的操作类型; 和 [0037] 操作模块,用于根据操作类型对移动终端执行相应的操作过程。 [0038] 本发明采用传感器替代移动终端的开机/关机按钮或移动终端的唤醒或睡眠按钮。 首先,传感器根据预设的触发规则进行触发,传感器输出与触发规则对应的数字信号; 接收到数字信号后,对数字信号进行检测,获取确定的数字信号对应的移动终端的操作类型,并根据获取的操作类型对移动终端进行相应的操作处理。 采用该方案,通过传感器完成对移动终端的开关机、唤醒、睡眠等操作,在简化移动终端结构的同时,给用户带来更好的使用体验。 附图的简要说明 [0039] 图1为本发明实施例中基于传感器的移动终端操作方法的流程图; [0040]图2是根据本发明实施例的基于传感器的移动终端操作方法中确定移动终端操作类型的流程图。 [0041] 图3是根据本发明另一实施例的基于传感器的移动终端操作方法的流程图。 [0042] 图4是根据本发明实施例的基于传感器操作移动终端的装置的结构图; [0043] 图5是根据本发明实施例的基于传感器操作移动终端的装置的判断模块的结构图。 和 [0044] 图6是根据本发明另一实施例的基于传感器操作移动终端的装置的结构图。 [0045] 本发明目的的实现、功能特点及优点将结合附图及实施例作进一步说明。 具体实施方式 [0046] 应当理解,此处所描述的具体实施例仅仅用于说明本发明,并不用于限制本发明。 [0047] 本发明实施例提供了一种基于传感器的移动终端操作方法。 如图1所示,该方法包括以下步骤。 [0048] 小号 10 :传感器按照预设的触发规则触发,使传感器输出符合触发规则的数字信号。 [0049] 本发明实施例提供的基于传感器的移动终端操作方法,采用传感器代替移动终端中的开机/关机按键或移动终端的唤醒或休眠按键,以实现 无需按键即可在移动终端上进行相应操作的功能。 这样,应用本发明提供的基于传感器的移动终端操作方法的移动终端系统可以包括传感器、电池、电源管理单元(PMU)和主控。 单元(MCU),其中电池用于PMU和传感器的供电; 传感器可以设置在移动终端屏幕的任意位置。 传感器连接到PMU的引脚; PMU被触发后,可以为MCU供电,维持MCU的正常运行。 同时,本实施例还需要在移动终端的系统中集成一个软件处理模块,用于处理传感器输出给MCU的数字信息。 [0050] 在本实施例中,当根据用户的实际需求对移动终端进行操作时,首先根据移动终端系统中预设的触发规则触发传感器。 触发规则包括长按、点击或双击,不同的触发规则对应移动终端的不同操作类型。 传感器根据不同的触发规则被触发后,传感器中的处理芯片将触发动作对应的模拟数据转换为触发规则对应的数字信号,然后输出数字信号。 在本实施例中,可以采用压力传感器作为所提供的传感器。 由于传感器连接到PMU的一个管脚上,所以PMU可以在传感器被触发后被触发,从而使电池为PMU工作; 此时PMU给MCU上电,维持MCU正常运行。 [0051] 小号 20 :接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型。 [0052]接收到传感器输出的数字信号,该数字信号由传感器的处理芯片根据当前触发传感器的触发规则进行转换得到,判断该数字信号,从而确定操作类型 ,对应移动终端的数字信号,则可以得到用户现在需要在移动终端上进行哪些操作。 在本实施例中,移动终端的操作类型可以包括:开机、关机、唤醒、睡眠、进入系统主菜单等; 另外,预先设置的触发传感器的触发规则对应这些操作类型; 即长按对应的移动终端的操作类型为开机或关机。 点击对应的移动终端操作类型为进入系统主菜单; 双击对应的移动终端的操作类型为唤醒和/或睡眠。 [0053] 小号 30 :根据操作类型在移动终端上进行相应的操作处理。 [0054] 根据传感器输出的数字信号确定移动终端的操作类型后,需要执行与当前操作类型对应的相应操作处理。 即移动终端处于开机或关机状态; 开机后进行唤醒、休眠、进入主菜单等操作。 [0055] 本实施例提供的基于传感器的移动终端的操作方法,采用传感器代替移动终端中的开机/关机按钮或移动终端的唤醒或休眠按钮。 首先,传感器根据预设的触发规则进行触发,传感器输出与触发规则对应的数字信号; 接收到数字信号后,检测数字信号得到数字信号对应的移动终端的操作类型,并根据移动终端的操作类型对移动终端进行相应的操作处理 终端对应的数字信号。 采用该方法,通过传感器完成对移动终端的开关机、唤醒、睡眠等操作,在简化移动终端结构的同时,给用户带来更好的使用体验。 [0056] 本发明实施例提供了一种基于传感器的移动终端操作方法。 如图2所示,步骤S 20 包括以下步骤: [0057] 小号 21 :接收到数字信号后,根据数字信号确定数字信号对应的触发规则; 若数字信号对应的触发规则为长按,转步骤S 22 ; 若数字信号对应的触发规则为点击,转步骤S 23 ; 若数字信号对应的触发规则为双击,转步骤S 24 ; [0058] 小号 22 :确定移动终端的操作类型为开机或关机; [0059] 小号 23 :确定移动终端的操作类型为进入系统主菜单; 和 [0060] 小号 24 :确定移动终端的操作类型是唤醒还是睡眠。 [0061]在上述实施例中,在接收到传感器输出的与触发规则对应的数字信号后,首先根据数字信号确定与数字信号对应的触发规则,然后确定操作类型。 根据触发规则确定移动终端的号码。 若数字信号对应的触发规则为长按,则可判断移动终端的操作类型为开机或关机。 这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是开机还是关机; 若开机,则加载系统中集成的用于处理数字信息的软件处理模块,进入正常开机流程,启动移动终端。 若为关机,则释放软件处理模块,进入正常关机流程,将移动终端关机。 [0062] 在通过触发传感器启动移动终端进入开机过程后,即移动终端处于开机状态后,还可以在移动终端上进行使移动终端休眠或唤醒的过程。 因此,若此时接收到数字信号,且该数字信号对应的触发规则为双击,则可以确定此时该数字信号对应的移动终端的操作类型为唤醒或睡眠。 同样,这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是唤醒还是睡眠; 如果是唤醒,则执行唤醒过程,将移动终端唤醒。 [0063] 移动终端被唤醒后,如果再次触发传感器,接收到触发信号对应的数字信号,则需要用于处理数字信号的软件处理模块对数字信号进行处理,即操作 确定此时数字信号对应的移动终端的类型。 若触发规则为点击,则此时数字信号对应的移动终端操作类型为进入主菜单,软件处理模块响应该操作类型返回主菜单; 若触发规则为双击,则软件处理模块响应操作类型,使移动终端进入休眠状态。 [0064] 当然,在移动终端被唤醒后,也可以长按感应器使移动终端关机。 也就是说,此时,传感器还可以输出长按对应的数字信号。 然后,如果通过软件处理模块判断出数字信号对应的移动终端的操作类型为关机,则直接执行正常的关机流程,将移动终端关机。 [0065] 在接收到传感器输出的数字信号后,判断该数字信号对应的操作类型。 根据触发传感器的不同触发规则,确定触发规则对应的移动终端的操作类型,并根据确定的操作类型对移动终端进行相应的操作。 这样,进一步完善了通过传感器完成移动终端的开关机、唤醒、休眠等操作的过程,进一步为用户带来更好的使用体验,同时进一步保证了移动终端的架构。 移动端更简单。 [0066] 如图3所示,根据本发明的另一个实施例,提供了一种基于传感器的移动终端的操作方法。 [0067] 在执行步骤S之前 10 ,该方法还包括以下步骤。 [0068] 脚步 40 :根据移动终端的操作类型预先设置触发传感器的触发规则。 [0069]由于移动终端的操作类型多种多样,因此在采用传感器代替移动终端的按键时,需要传感器检测移动终端的不同操作类型。 这样,在触发传感器之前,需要在移动终端的系统中预先设置与操作类型对应的触发规则,用于根据不同的操作类型触发传感器,其中,触发规则包括长按、 单击并双击。 在根据用户的实际需求使用相应的触发规则触发传感器后,移动终端的系统可以识别触发规则,从而确定触发规则对应的操作类型,并完成相应的操作过程。 [0070] 触发传感器的触发规则是根据移动终端的几种不同的操作类型预先设置的,从而可以在使用相应的触发规则触发传感器后识别触发规则,从而确定相应的操作类型。 这样,为利用传感器实现移动终端的开关机、唤醒、睡眠等操作提供了更有力的保障。 [0071] 如图4所示,本发明实施例提供了一种基于传感器操作移动终端的装置,该装置包括: [0072] 触发组件 10 用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0073] 决定因素 20 用于在接收到传感器输出的触发规则对应的数字信号后,为移动终端确定该数字信号对应的操作类型; 和 [0074] 一个操作组件 30 用于根据操作类型对移动终端进行相应的操作处理。 [0075] 本实施例提供的基于传感器的移动终端操作装置,采用传感器替代移动终端的开机/关机按键或移动终端的唤醒或睡眠按键,实现功能 无需任何按钮即可在移动终端上进行相应的操作。 这样,本发明提供的基于传感器的移动终端操作方法可应用的移动终端系统可以包括传感器、电池、PMU和MCU。 电池用于PMU和传感器的供电。 传感器可以设置在移动终端屏幕的任意位置。 传感器连接到 PMU 的一个引脚。 PMU被触发后,PMU可以为MCU供电,以维持MCU的正常运行。 同时,本实施例还需要在移动终端的系统中集成一个软件处理模块,用于处理传感器输出给MCU的数字信息。 [0076] 在本实施例中,当根据用户的实际需求对移动终端进行操作时,首先,传感器被触发组件触发。 10 根据移动端系统预设的触发规则。 触发规则包括长按、单击、双击; 不同的触发规则对应移动终端的不同操作类型。 传感器根据不同的触发规则被触发后,传感器中的处理芯片将触发动作对应的模拟数据转换成与触发规则对应的数字信号,然后输出数字信号。 在本实施例中,可以采用压力传感器作为所提供的传感器。 由于传感器连接到PMU的一个管脚,因此可以在传感器被触发后触发PMU,从而使电池为PMU供电。 此时PMU为MCU供电,维持MCU正常运行。 [0077]传感器输出的数字信号由传感器的处理芯片根据当前触发传感器的触发规则转换得到后,由判断部件检测数字信号。 20 ,从而确定该数字信号对应的移动终端的操作类型,进而得到用户现在需要在移动终端上进行哪些操作。 在本实施例中,移动终端的操作类型可以包括:开机、关机、唤醒、睡眠、进入系统主菜单等; 另外,预先设置的触发传感器的触发规则对应这些操作类型; 即长按对应的移动终端的操作类型为开机或关机。 点击对应的移动端操作类型为进入系统主菜单; 双击对应的移动终端的操作类型为唤醒和/或睡眠。 [0078] 根据传感器输出的数字信号确定移动终端的操作类型后,操作组件 30 需要根据当前的操作类型进行相应的操作流程。 即移动终端处于开机或关机状态; 开机后可以进行唤醒、休眠、进入主菜单等操作。 [0079] 本实施例提供的基于传感器的移动终端操作装置,采用传感器代替移动终端的开机/关机按钮或移动终端的唤醒或休眠按钮。 首先,传感器根据预设的触发规则进行触发,传感器输出与触发规则对应的数字信号; 接收到数字信号后,检测数字信号,获取确定的数字信号对应的移动终端的操作类型,并根据获取的操作类型对移动终端进行相应的操作处理。 采用该方法,通过传感器完成对移动终端的开关机、唤醒、睡眠等操作,在简化移动终端结构的同时,给用户带来更好的使用体验。 [0080] 本发明实施例提供了一种基于传感器的移动终端操作装置。 如图5所示,判断组件 20 具体包括: [0081] 第一确定单位 21 用于若数字信号对应的触发规则为长按,则判断移动终端的操作类型为开机或关机; [0082] 第二决定单位 22 用于若数字信号对应的触发规则为点击,则判断移动终端的操作类型为进入系统主菜单; 和 [0083] 第三决定单位 23 配置为若数字信号对应的触发规则为双击,则判断移动终端的操作类型为唤醒或休眠。 [0084] 在上述实施例中,接收到传感器输出的与触发规则对应的数字信号后,首先根据该数字信号确定与该数字信号对应的触发规则,然后确定该数字信号对应的触发规则的操作类型。 移动终端根据触发规则确定。 若数字信号对应的触发规则为长按,则第一判断单元 21 可以判断移动终端的操作类型是开机还是关机。 这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是开机还是关机; 若开机,则加载系统中集成的用于处理数字信息的软件处理模块,进入正常开机流程,为移动终端开机。 若为关机,则释放软件处理模块,进入正常关机流程,将移动终端关机。 [0085]当传感器被触发移动终端进入开机流程后,移动终端开机,在移动终端处于开机状态的情况下,还可以进行使移动终端休眠或唤醒的流程 状态。 因此,若此时接收到数字信号,且该数字信号对应的触发规则为双击,则第三判断单元 23 可以判断此时数字信号对应的移动终端的操作类型是唤醒还是睡眠。 同样,这种情况下,MCU需要进一步检测数字信号,得到数字信号对应的操作类型具体是唤醒还是睡眠; 如果是唤醒,则执行唤醒过程,将移动终端唤醒。 [0086] 移动终端被唤醒后,如果再次触发传感器,接收到触发信号对应的数字信号,则需要用于处理数字信号的软件处理模块对数字信号进行处理,即操作 确定此时数字信号对应的移动终端的类型。 若触发规则为点击,则第二判断单元 22 可以判断此时数字信号对应的移动终端的操作类型为进入主菜单,软件处理模块响应返回主菜单。 若触发规则为双击,则软件处理模块响应使移动终端进入休眠状态。 [0087] 当然,在移动终端被唤醒后,也可以通过长按感应器来关闭移动终端。 也就是说,此时,传感器还可以输出长按对应的数字信号。 然后,如果通过软件处理模块判断出数字信号对应的移动终端的操作类型为关机,则直接执行正常关机流程,将移动终端关机。 [0088] 在接收到传感器输出的数字信号后,判断该数字信号对应的操作类型。 根据触发传感器的不同触发规则,确定触发规则对应的移动终端的操作类型,并根据确定的操作类型对移动终端进行相应的操作。 这样,进一步完善了通过传感器完成移动终端的开关机、唤醒、休眠等操作的流程,进一步为用户带来更好的使用体验,同时进一步保证了移动终端的架构。 移动端更简单。 [0089] 本发明实施例提供了一种基于传感器的移动终端操作装置。 如图6所示,该装置还包括: [0090] 预设组件 40 用于根据移动终端的多种操作类型预设触发传感器的触发规则。 [0091] 当采用传感器代替移动终端的按键时,由于移动终端包括多种不同的操作类型,因此需要采用传感器来检测移动终端的不同操作类型。 这样,在触发传感器之前,预置元件 40 需要根据不同的操作类型,在移动终端的系统中预设触发多个操作类型对应的传感器的触发规则,其中,触发规则包括长按、点击和双击。 在根据用户的实际需求使用相应的触发规则触发传感器后,移动终端的系统可以识别触发规则,从而确定触发规则对应的操作类型,完成相应的操作过程。 [0092]触发传感器的触发规则是根据移动终端的几种不同的操作类型预先设置的,从而可以在传感器被触发后使用相应的触发规则来识别触发规则,并确定相应的操作类型。 这样,为利用传感器实现移动终端的开关机、唤醒、睡眠等操作提供了更有力的保障。 [0093] 本发明实施例还提供了一种移动终端,包括基于传感器的移动终端操作装置; 该设备包括: [0094] 触发组件 10 用于根据预设的触发规则触发传感器,使传感器输出与触发规则对应的数字信号; [0095] 决定因素 20 用于在接收到传感器输出的与触发规则对应的数字信号后,确定移动终端与该数字信号对应的操作类型; 和 [0096] 一个操作组件 30 用于根据操作类型对移动终端进行相应的操作处理。 [0097] 该移动终端实施例包括图4至图6所示的基于传感器的移动终端操作装置实施例的全部技术方案; 实现的技术效果是一样的,这里不再赘述。 [0098] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明的保护范围; 任何基于本发明的说明书和附图的内容所进行的结构或流程的等同替换,或者等同替换在其他相关技术领域的直接或间接应用,均属于本发明权利要求的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102681784A(String), EP2849415A1(String), EP2849415A4(String), US20150215441A1(String), US9565293B2(String), WO2013166778A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102681784A(String), EP2849415A1(String), EP2849415A4(String), US20150215441A1(String), US9565293B2(String), WO2013166778A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102681784A(String), EP2849415A1(String), EP2849415A4(String), US20150215441A1(String), US9565293B2(String), WO2013166778A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271253(Integer), CN102681784A(String), 1048391(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271253(Integer), EP2849415A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271253(Integer), EP2849415A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.444 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.444 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271253(Integer), US20150215441A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271253(Integer), US9565293B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271253(Integer), WO2013166778A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN102681784A(String), CN102681784A(String), 1347984000(Integer), 271253(Integer), 185537(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), SHEN, CHUANGYE(String), LIU, LITIAN(String), SUN, XIAOMIN(String), 中兴通讯股份有限公司(String), SHEN CHUANGYE(String), LIU LITIAN(String), SUN XIAOMIN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185968(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185968(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHEN, CHUANGYE(String), SHEN CHUANGYE(String), 0(Integer), 1681976087(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIU, LITIAN(String), LIU LITIAN(String), 0(Integer), 1681976087(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SUN, XIAOMIN(String), SUN XIAOMIN(String), 0(Integer), 1681976087(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185968(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75843(Integer), 2(Integer), 185968(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75844(Integer), 2(Integer), 185968(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75845(Integer), 2(Integer), 185968(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:47.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75843(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.100 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.100 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185968(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.288 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7245911B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.632 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.632 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal for automatically managing country code and method for storing/finding phone number using the same(String), 自动管理国家代码的移动终端及使用该移动终端存储/查找电话号码的方法(String), US7245911B2(String), A mobile terminal for providing a mobile service and a method for storing and finding a phone number using the mobile terminal. The mobile terminal stores and manages country code information, a mobile service subscriber's registration information, and mobile service usage history information; automatically generates a country code of a country where the mobile terminal is located using the mobile service subscriber's registration information and mobile service usage history information; and executes a phone number storage command or a phone number search command using the country code. Where an international roaming service is executed by a user's moving from one country to another country, the mobile terminal can automatically generate a country code or store an arbitrary phone number. Thus, there is no need for mobile service users to manually enter a country code in their mobile terminal when roaming service is executed.(String), 一种用于提供移动服务的移动终端以及使用该移动终端存储和查找电话号码的方法。 移动终端存储和管理国家代码信息、移动业务用户注册信息、移动业务使用历史信息; 利用移动业务用户的注册信息和移动业务使用历史信息,自动生成移动终端所在国家的国家代码; 使用国家代码执行电话号码存储命令或电话号码搜索命令。 在用户从一个国家移动到另一个国家执行国际漫游业务的情况下,移动终端可以自动生成国家代码或存储任意电话号码。 因此,移动服务用户在执行漫游服务时无需手动在其移动终端中输入国家代码。(String), US10/760907(String), 1074528000(Integer), US7245911B2(String), 1184601600(Integer), 1184601600(Integer), 美国(String), 4(Integer), KR(String), 5(Integer), 6(Integer), DE19711096A1 | EP0526832A2 | US20040204117A1 | US20050101323A1 | US5305372A | WO2000041422A1(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185969(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2b75bc18a0704356a16e43e06c262db5.png(String), 185969(Integer), 2b75bc18a0704356a16e43e06c262db5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.867 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.867 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.867 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal for automatically managing country code and method for storing/finding phone number using the same(String), 自动管理国家代码的移动终端及使用该移动终端存储/查找电话号码的方法(String), US7245911B2(String), A mobile terminal for providing a mobile service and a method for storing and finding a phone number using the mobile terminal. The mobile terminal stores and manages country code information, a mobile service subscriber's registration information, and mobile service usage history information; automatically generates a country code of a country where the mobile terminal is located using the mobile service subscriber's registration information and mobile service usage history information; and executes a phone number storage command or a phone number search command using the country code. Where an international roaming service is executed by a user's moving from one country to another country, the mobile terminal can automatically generate a country code or store an arbitrary phone number. Thus, there is no need for mobile service users to manually enter a country code in their mobile terminal when roaming service is executed.(String), 一种用于提供移动服务的移动终端以及使用该移动终端存储和查找电话号码的方法。 移动终端存储和管理国家代码信息、移动业务用户注册信息、移动业务使用历史信息; 利用移动业务用户的注册信息和移动业务使用历史信息,自动生成移动终端所在国家的国家代码; 使用国家代码执行电话号码存储命令或电话号码搜索命令。 在用户从一个国家移动到另一个国家执行国际漫游业务的情况下,移动终端可以自动生成国家代码或存储任意电话号码。 因此,移动服务用户在执行漫游服务时无需手动在其移动终端中输入国家代码。(String), US10/760907(String), 1074528000(Integer), US7245911B2(String), 1184601600(Integer), 1184601600(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 5(Integer), 6(Integer), DE19711096A1 | EP0526832A2 | US20040204117A1 | US20050101323A1 | US5305372A | WO2000041422A1(String), \20230420\2b75bc18a0704356a16e43e06c262db5.png(String), 6(Integer), 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185969(Integer), 1. A mobile terminal for providing mobile service subscribers with a mobile service, comprising:a country code storage unit for coupling each mobile communication network ID received from each of a plurality of mobile communication network MSCs (Mobile Switching Centers) providing a mobile communication network service for every service area with a country code of a prescribed country in which the mobile communication network is located, and for storing and managing the coupling result of the mobile communication network ID and the country code;a subscriber information storage unit for storing and managing mobile service registration information and mobile service usage history information of the mobile service subscriber;a phone number storage unit for storing and managing phone number information; anda controller for detecting a mobile communication network ID of a current PLMN (Public Land Mobile Network) service, retrieving mobile service usage history information from the subscriber information storage unit upon receiving either a phone number storage command or a phone number search command, determining whether a roaming operation of the mobile terminal is executed on the basis of the mobile communication network ID of the current PLMN service and the mobile service usage history information, and executing a phone number storage command or a phone number search command using both a received entry phone number and a detected country code.(String), 1.为移动服务用户提供移动服务的移动终端,包括:国家代码存储单元,用于耦合从多个移动通信网络MSC(移动交换中心)中的每一个接收的每个移动通信网络ID,为每个服务区域提供移动通信网络服务与移动设备所在的规定国家的国家代码通信网络定位,用于存储和管理移动通信网络ID与国家代码的耦合结果;用户信息存储单元,用于存储和管理移动业务用户的移动业务注册信息和移动业务使用历史信息;电话号码存储单元,用于存储和管理电话号码信息;和控制器,用于检测当前PLMN(公共陆地移动网络)服务的移动通信网络ID,在接收到电话号码存储命令或电话号码搜索命令时,从用户信息存储单元中检索移动服务使用历史信息,确定是否移动终端根据当前PLMN业务的移动通信网络ID和移动业务使用历史信息执行漫游操作,并使用接收到的登录电话执行电话号码存储命令或电话号码搜索命令号码和检测到的国家代码。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185969(Integer), 2. The mobile terminal as set forth in claim 1, wherein the phone number storage unit includes a phone number storage field, a phone number storage field excluding country code, and a reception information storage field of the phone number excluding country code.(String), 2.如权利要求1所述的移动终端,其中电话号码存储单元包括电话号码存储字段、不包括国家代码的电话号码存储字段和不包括国家代码的电话号码的接收信息存储字段。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185969(Integer), 3. The mobile terminal as set forth in claim 1, wherein the controller analyzes an entry phone number received for a phone number storage service, determines whether the entry phone number has a country code, retrieves a country code of a country where the mobile terminal is located from the country code storage unit in the case where the entry phone number has no country code, and stores the country code and the entry phone number in the phone number storage unit.(String), 3.如权利要求1所述的移动终端,其中控制器分析接收到的用于电话号码存储服务的入口电话号码,判断入口电话号码是否具有国家代码,如果是,则从国家代码存储单元中检索移动终端所在国家的国家代码。入口电话号码没有国家代码,将国家代码和入口电话号码存储在电话号码存储单元中。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185969(Integer), 4. The mobile terminal as set forth in claim 1, wherein the controller reads a requested phone number from the phone number storage unit, detects a country code of a country where the mobile terminal is located according to the phone number search command, compares the detected country code with an other country code associated with a phone number read from the phone number storage unit, and then displays a phone number having the other country code inserted into the phone number on a display in a predetermined display format when the detected country code is different from the other country code.(String), 4.如权利要求1所述的移动终端,其中控制器从电话号码存储单元中读取请求的电话号码,根据电话号码搜索命令检测移动终端所在国家的国家代码,将检测到的国家代码与与电话号码关联的其他国家代码进行比较从电话号码存储单元中读取,然后当检测到的国家代码不同于其他国家代码时,以预定显示格式在显示器上显示具有插入电话号码中的其他国家代码的电话号码。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185969(Integer), 5. The mobile terminal as set forth in claim 4, wherein the controller, if the detected country code is identical to the other country code read from the phone number storage unit, displays on the display a phone number created by removing the country code from the phone number read from the phone number storage unit in a predetermined display format.(String), 5.如权利要求4所述的移动终端,其中控制器,如果检测到的国家代码与从电话号码存储单元读取的其他国家代码相同,则在显示器上显示通过以预定的时间从从电话号码存储单元读取的电话号码中去除国家代码而创建的电话号码显示格式。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:48.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185969(Integer), 6. A method for finding a phone number in a mobile terminal adapted to store and manage country code information of various countries to allow a mutual roaming process among countries, mobile service registration information and mobile service usage history information of the mobile service subscriber comprising the steps of:a) reading a search-requested phone number from a memory contained in the mobile terminal upon receiving a phone number search command;b) detecting a country code of a current country wherein the mobile terminal is located;c) comparing a country code contained in the phone number read at step (a) with the country code detected at step (b); andd) displaying the phone number read at step (a) in the form of a prescribed display format on the basis of the result of step (c),wherein if it is determined at step (c) that the country code detected at step (b) is different from the country code contained in the phone number read at step (a), displaying in step (d) a phone number having the country code contained in the phone number read at step (a), and if it is determined at step (c) that the country code detected at step (b) is the same as the country code contained in the phone number read at step (a), displaying in step (d) a phone number created by removing the country code from the read phone number of step (a).(String), 6.一种在移动终端中查找电话号码的方法,适用于存储和管理各个国家的国家代码信息以允许在国家之间进行相互漫游的过程,移动服务注册信息和移动服务订户的移动服务使用历史信息包括步骤:a)在接收到电话号码搜索命令时,从移动终端包含的存储器中读取搜索请求的电话号码;b)检测移动终端当前所在国家的国家代码;c)将步骤(a)读取的电话号码中包含的国家代码与步骤(b)检测到的国家代码进行比较;和d)在步骤(c)的结果的基础上,以规定的显示格式显示步骤(a)读取的电话号码,其中,如果在步骤(c)确定在步骤(b)检测到的国家代码与在步骤(a)读取的电话号码中包含的国家代码不同,则在步骤(d)显示具有该国家的电话号码在步骤(a)中读取的电话号码中包含的代码,并且如果在步骤(c)中确定在步骤(b)中检测到的国家代码与在步骤(a)中读取的电话号码中包含的国家代码相同),在步骤(d)中显示通过从步骤(a)中读取的电话号码中删除国家代码而创建的电话号码。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185969(Integer), PRIORITY [0001]This application claims priority to an application entitled “WIRELESS TERMINAL FOR AUTO-MANAGING NATIONAL CODE AND METHOD FOR STORING AND SEARCHING PHONE NUMBER USING THE WIRELESS-TERMINAL” filed in the Korean Intellectual Property Office on Jan. 22, 2003 and assigned Serial No. 2003-04307, the contents of which are hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal, also called a wireless terminal, and more particularly to a mobile terminal for automatically managing a country code during roaming, and a method for storing and finding a phone number using the mobile terminal [0004]2. Description of the Related Art [0005]Typically, a GSM (Global System for Mobile communication) is a digital mobile phone system widely used in Europe and other countries in recent times. The GSM is a variant of TDMA (Time Division Multiple Access), and is one of the three most widely used wireless telephony systems: the TDMA system, the CDMA (Code Division Multiple Access) system, and the GSM system. A GSM enables a user who travels abroad to continuously use his or her mobile phone anywhere he or she wishes because many international GSM network enterprisers have entered into roaming agreements with each other. [0006]Conventionally, in the case where a user of a GSM-based mobile service moves from one country to another country and thus a roaming process between such countries is performed, in order to select a phone number previously registered in a mobile terminal and to use the selected phone number to make a phone call to a receiving party, the user must append a corresponding country code to the registered phone number prior to roaming. Also, the user who is roaming from one country to another country must append a country code of an original country to the phone number registered on a PLMN (Public Land Mobile Network) of the original country, in order for the user's phone number as registered on the PLMN to be stored in his or her mobile terminal. [0007]FIG. 1 is an exemplary view illustrating a conceptual diagram wherein an international roaming process occurs on a PLMN service network. Referring to FIG. 1, in the case where a mobile terminal 10 of a subscriber registered in a MSC (Mobile Switching Center) 30 of a PLMN B service having a country code of ‘0033’ roams within a MSC's 20 area of a PLMN A service having a country code of ‘0044’, a user of the mobile terminal 10 must append a country code of ‘0033′’ to a prestored phone number to make a phone call to the prestored phone number. Unless the user appends the country code of ‘0033’ to the prestored phone number, there may-occur an erroneous phone call to another party registered to the PLMN A service having the country code of ‘0044’. For example, in the case where the mobile terminal 10 previously stores a phone number of ‘123-4567’ therein, and a user of the mobile terminal 10 selects only the phone number of 123-4567 without appending an appropriate country code to the phone number of ‘123-4567’, the PLMN A service MSC 20 makes a phone, call to a wrong phone number of ‘0044-123-4567’ instead of a correct phone number of ‘0033-123-4567’. [0008]Conversely, in the case where the PLMN B service subscriber attempts to store in the mobile terminal 10 a phone number of a user registered to the PLMN A service in an area of the PLMN A service MSC 20, the subscriber must append a country code of ‘0044’ corresponding to the PLMN A service to the user's phone number. Otherwise, the mobile terminal 10 recognizes the user's phone number as a phone number of a subscriber registered to the PLMN B service. [0009]In this manner, conventionally, in the case where a user of such a PLMN service moves from one country to another country and thus there occurs a roaming process between countries, he or she must append an additional country code to his or her phone number in order to make a phone call to a called: party or store any phone number in the mobile terminal, resulting in a user's inconvenience. SUMMARY OF THE INVENTION [0010]Therefore, the present invention has been made in view of the above problems, and it is an object of the present invention to provide a mobile terminal for storing any phone number in the mobile terminal, and for automatically generating a country code, when a user is roaming internationally by moving from one country to another country, to make a phone call to a called party without appending a country code to the mobile terminal. [0011]It is another object of the present invention to provide a method for storing a phone number which automatically generates a country code upon receiving a phone number storage command. [0012]It is yet another object of the present invention to provide a method for finding a phone number which automatically generates a country code upon receiving a phone number search command. [0013]In accordance with one aspect of the present invention, the above and other objects can be accomplished by the provision of a mobile terminal for providing mobile service subscribers with a mobile service, comprising: a country code storage unit for coupling each mobile communication network ID with a country code of a prescribed country having the mobile communication network, and storing and managing the coupling result of the mobile communication network ID and the country code, wherein the mobile communication network ID is received from each of a plurality of mobile communication network MSCs (Mobile Switching Centers) providing a mobile communication network service for every service area; a subscriber information storage unit for storing and managing mobile service subscriber's registration information and mobile service usage history information; a phone number storage unit for storing and managing phone number information; and a controller for detecting a mobile communication network ID of a current PLMN service and retrieving mobile service usage history information from the subscriber information storage unit upon receiving a phone number storage command or a phone number search command, for determining whether a roaming operation of the mobile terminal is executed on the basis of the mobile communication network ID of the current PLMN service and the mobile service usage history information, and for executing either one of the phone number storage command or the phone number search command using an entry phone number and the detected country code. [0014]In accordance with another aspect of the present invention, there is provided a method for storing a phone number in a mobile terminal adapted to store and manage country code information of various countries, mobile service subscriber's registration information, and mobile service usage history information, comprising the steps of: a) reading an external entry phone number according to a phone number storage command; b) analyzing the phone number read at step (a) to determine whether the phone number has a country code; c) if the phone number has no country code at step (b), retrieving a country code of a country where the mobile terminal is located using a mobile communication network ID of a current PLMN service; and d) storing the phone number read at step (a) and the country code retrieved at step (c) in the mobile terminal. [0015]In accordance with yet another aspect of the present invention, there is provided a method for finding a phone number in a mobile terminal adapted to store and manage country code information of many countries, mobile service subscriber's registration information, and mobile service usage history information, comprising the steps of: a) reading a search-requested phone number from a memory contained in the mobile terminal upon receiving a phone number search command; b) detecting a country code of a country where the mobile terminal is located; c) comparing a country code contained in the phone number read at step (a) with the country code detected at step (b); and d) displaying the phone number read at step (a) in the form of a prescribed display format on the basis of the result of step (c). BRIEF DESCRIPTION OF THE DRAWINGS [0016]The above and other objects, features and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which: [0017]FIG. 1 is an exemplary view illustrating a conceptual diagram wherein the roaming between countries occurs on a PLMN service network; [0018]FIG. 2 is a view illustrating a schematic diagram of a mobile terminal in accordance with a preferred embodiment of the present invention; [0019]FIG. 3 is a view illustrating an exemplary configuration for storing a country code therein using a country code table in accordance with a preferred embodiment of the present invention; [0020]FIG. 4 is a view illustrating an exemplary configuration for storing/managing a phone number in a phone number storage unit in accordance with a preferred embodiment of the present invention; [0021]FIG. 5 is a flow chart illustrating a procedure for storing a phone number in accordance with a preferred embodiment of the present invention; [0022]FIG. 6 is a flow chart illustrating a procedure for automatically generating a country code in accordance with a preferred embodiment of the present invention; and [0023]FIG. 7 is a flow chart illustrating a procedure for finding a phone number in accordance with a preferred embodiment of the present invention DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0024]Preferred embodiments of the present invention will be described in detail with reference to the attached drawings. In the drawings, the same or similar elements are denoted by the same reference numerals even though they are depicted in different drawings. In the following description, a detailed description of known functions and configurations incorporated herein will be omitted when they might make the subject matter of the present invention unclear. [0025]FIG. 2 is a view illustrating a schematic diagram of a mobile terminal in accordance with a preferred embodiment of the present invention. Referring to FIG. 2, the mobile terminal according to the present invention includes an input unit 110, a controller 120, a subscriber information storage unit 130, a country code table 140, a phone number storage unit 150, and a display 160. [0026]The input unit 110 is adapted to execute an interface between a user and his or her mobile terminal. For example, a representative example of such an input unit 110 is a keypad. The display 160 displays operation status and an external entry item thereon. The input unit 110 and the display 160 are adapted to execute an interface between the mobile terminal and the user, and are typically contained in a general mobile terminal along with a speaker and a microphone (not shown), so their detailed description will hereinafter be omitted. [0027]The country code table 140 stores and manages country code information of various countries for allowing a mutual international roaming process. An exemplary structure for storing a country code in the country code table 140 is depicted in FIG. 3. Referring to FIG. 3, the country code table 140 couples each mobile communication network ID with a country code of a prescribed country where the mobile communication network is located, and individually stores and manages a plurality of couples of the network IDs and the country code, in which the mobile communication network IDs are received from a plurality of MSCs for providing a mobile communication network service for every service area. [0028]The mobile communication network ID is specific information transmitted to a mobile terminal from a MSC providing a mobile communication network service for every service area. Such a mobile communication network ID includes an MCC (Mobile Country Code), an MNC (Mobile Network Code), an LAI (Location Area Identity), and a PLMN enterpriser ID. [0029]The subscriber information storage unit 130 stores and manages a mobile service subscriber's registration information and mobile service usage history information. The mobile service subscriber's registration information is information stored in a mobile terminal when the mobile service subscriber joins a prescribed mobile communication service as a member. A representative example of such mobile communication service subscriber's registration information is a MCC (hereinafter referred to as an H_MCC) of a PLMN (i.e., Home PLMN). The mobile service usage history information is a subscriber's usage record information, stored from the time of a subscriber's mobile service registration up to the time of the subscriber's most recent usage, and is typically stored in a mobile terminal. A representative example of mobile service usage history information is a MCC (hereinafter referred to as an R_MCC) of a PLMN (i.e., registered PLMN) indicating the most recent usage record of a mobile terminal. [0030]The phone number storage unit 150 stores and manages phone number information entered by a user. An exemplary structure for storing/managing phone numbers in the phone number storage unit 150 is shown in FIG. 4. Referring to FIG. 4, the phone number storage unit 150 includes a reception information storage field (e.g., a receiver name), a country code storage field, and a phone number storage field. The phone number storage unit 150 divides a phone number into a country code and a common phone number excluding country code, and stores the phone number divided into the country code and the common phone number, as shown in FIG. 4. [0031]The controller 120 controls an operation of the mobile terminal according to an external control command. Particularly, the controller 120 automatically generates a country code of a country in which the mobile terminal is located using the mobile service subscriber's registration information and the mobile service usage history information stored in the subscriber information storage unit 130. The controller 120 adapts the country code to execute a new phone number storage command or a prestored phone number search command. [0032]A method for automatically generating a country code, a method for storing a phone number using the country code, and a method for finding a phone number using the country code are shown in FIGS. 5–7, respectively. [0033]FIG. 5 is a flow chart illustrating a procedure for storing a phone number in accordance with a preferred embodiment of the present invention. Referring to FIGS. 2 and 5, if a user selects a command for storing a phone number on the input unit 110 and enters a desired phone number at step S110, the controller 120 reads the entry phone number and determines at step S120 whether the entry phone number has a country code. The controller 120 determines whether a specific code or specific number arrangement is contained in the entry phone number at step S120. For example, the controller determines whether specific information of ‘00’ or ‘+’ is contained in the phone number entered by the input unit 110, because a general country code begins with the specific information of ‘00’ or ‘+’ as shown in ‘0044’ or ‘+44’. [0034]The controller 120 determines at step S130 whether a country code of a country in which the mobile terminal is located is automatically generated on the basis of the result of step S120. If it is determined at step S120 that the entry phone number has no country code, the controller 120 automatically generates a country code using a mobile communication network ID of a current PLMN service at step S150, and stores the automatically generated country code and the entry phone number in the phone number storage unit 150 at step S160. If it is determined at step S120 that the entry phone number has a country code, the controller 120 stores the entry phone number in the phone number storage unit 150 at step S140. The controller 120 separately stores in the phone number storage unit 150 the country code received from the input unit 110 or automatically generated at step S150, and a phone number excluding the country code. The controller 120 stores the country code in a country code field of the phone number storage unit 150, and the phone number excluding the country code in a phone number field of the phone number storage unit 150. [0035]Herein, please note that FIG. 6 illustrates the procedure of step S150 of FIG. 5 in detail. FIG. 6 is a flow chart illustrating a procedure for automatically generating a country code in accordance with a preferred embodiment of the present invention. Referring to FIGS. 2 and 6, if the controller 120 decides to automatically generate a country code, it checks a mobile communication network ID (i.e., MCC) of a current PLMN service at step S151, and checks another ID (i.e., R_MCC) of the most recent use of the mobile communication network by the mobile terminal, using a mobile service usage history information previously stored in the subscriber information storage unit 130 at step S153, to determine whether a roaming service is executed. The controller 120 determines at step S155 whether the mobile communication network ID (MCC) of step S151 is identical to the other ID (R_MCC) of step S153. Based on the determination result, the controller 120 retrieves a country code corresponding to either the MCC or the R_MCC from the prestored country code table, and generates a correct country code at step S157 or S159. If it is determined at step S155 that the mobile communication network ID (MCC) is identical to the other ID (R_MCC), the controller 120 determines that a roaming service is not executed and retrieves a country code corresponding to the ID (R_MCC) confirmed at step S153 from the country code table 140. If it is determined at step S155 that mobile communication network ID (MCC) is not identical to the other, ID (R_MCC), the controller 120 determines that a roaming service is executed and retrieves a country code corresponding to the ID (MCC) confirmed at step S151 from the country code table 140. The controller 120 then automatically allocates the retrieved country code as a country code of a country in which the mobile terminal is located. [0036]For instance, in the case where any mobile service subscriber enters a phone number shown in the following Table 1 in an area using a country code of ‘0044’, and attempts to store the entry phone number in a mobile terminal carried with the subscriber, the result of storing the entry phone number in the mobile terminal on the basis of the methods shown in FIGS. 5–6 is shown in the following Table 2: [0037]TABLE 1NamePhone NumberFather0208775331Mother0208786998Boss07787816714 American_uncle001-778835991 [0038]TABLE 2NameCountry CodePhone NumberFather00440208775331Mother00440208786998Boss004407787816714American_uncle 0010778835991 [0039]With reference to the above Tables 1˜2, in the case of ‘American_uncle’, wherein a user manually enters a country code, the mobile terminal stores a country code and phone number entered by the user. In the cases of ‘Father’, ‘Mother’, and ‘Boss’, wherein a user does not enter a country code, it can be seen that a country code of ‘0044’ of a country (or area) where the user is located is automatically appended on the front of each phone number. [0040]FIG. 7 is a flow chart illustrating a procedure for finding a phone number in accordance with a preferred embodiment of the present invention. Referring to FIGS. 2 and 7, if a user selects a command for finding a phone number on the input unit 110 and enters desired search information at step S210, the controller 120 searches through the phone number storage unit 150, and retrieves a corresponding phone number from the phone number storage unit 150 at step S220. The controller 120 determines a country code of a country where a mobile terminal is located at step S230, being a country where the user of the mobile terminal is located. The controller 120 determines at step S240 whether the country code determined at step S230 is identical to the other country code contained in the phone number found at step S220. Based on the result of comparing the two country codes at step S240, the controller 120 controls the display 150 to display a found phone number in a prescribed display format at steps S250–270. If it is determined at step S240 that the country code determined at step S230 is identical to the other country code contained in the phone number found at step S220, the controller 120 removes the country code from the found phone number at step S250, and controls the display 160 to display a phone number excluding country code at step S260. On the other hand, if it is determined at step S240 that the country code determined at step S230 is not identical to the other country code contained in the phone number found at step S220, the controller 120 controls the display 160 to display the found phone number at step S270. In this case, the result may be displayed in a display format preset by the user. For example, in the case where the found phone number is composed of a country code, a regional number, and a common phone number excluding both the country code and the regional number, the country code, the regional number, and the common phone number excluding both the country code and the regional number are distinguishably displayed according to a user-defined display format. For example, a specific sign such as ‘-’ may be inserted between the country code, the regional number, and the common phone number according to the user-defined display format, or may be added only to the rear of the country code. Such a display format may be applicable in various ways according to the type of user-defined information. [0041]For example, in the case where a phone number is stored in the phone number storage unit 150 in the form of the above Table 2 and a user enters a command for finding a phone number of ‘Father’ in a certain area having a country code of ‘0044’, the result of finding the phone number of ‘Father’ in the phone number storage unit 150 on the basis of the methods shown in FIGS. 5–7 is displayed in a format (i.e., 0208775331) excluding the country code of ‘0044’. Such a display format may be applicable in various ways according to the type of user-defined information. [0042]In another example, in the case where a phone number is stored in the phone number storage unit 150 in the form of the above Table 2 and a user enters a command for finding a phone number of ‘Father’ in a place other than the area having the country code of ‘0044’, the result of finding the phone number of ‘Father’ in the phone number storage unit 150 on the basis of the method shown in FIG. 7 is displayed in the a format (i.e., 0044-0208775331) including the country code of ‘0044’. Such a display format may be applicable in various ways according to the type of user-defined information. [0043]As apparent from the above description, in the case where an international roaming service is executed by a user's moving from one country to another country, a mobile terminal automatically generates a country code without appending a country code to the mobile terminal to make a phone call to a called party, or stores an arbitrary phone number in the mobile terminal. Thus, the present invention automatically processes a country code in a mobile terminal when executing an international roaming service between countries, such that there is no need for mobile service users to manually enter a country code in their mobile terminal when they move from one country to another country, thereby increasing users' convenience. [0044]Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims. The present invention has been disclosed on a GSM system, however, it can also be applicable, for example, to a wideband CDMA system which uses a chipset for supporting GSM and CDMA schemes as well as a protocol for supporting the same.(String), 优先 [0001] 本申请要求于 2003 年 1 月 22 日向韩国知识产权局提交并转让序列号为 2003 的题为“用于自动管理国家代码的无线终端和使用无线终端存储和搜索电话号码的方法”的申请的优先权 -04307,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明涉及一种移动终端,也称为无线终端,尤其涉及一种在漫游时自动管理国家代码的移动终端,以及使用该移动终端存储和查找电话号码的方法 [0004] 2.相关技术的描述 [0005] 通常,GSM(全球移动通信系统)是近年来在欧洲和其他国家广泛使用的数字移动电话系统。 GSM 是 TDMA(时分多址)的变体,是三种最广泛使用的无线电话系统之一:TDMA 系统、CDMA(码分多址)系统和 GSM 系统。 GSM 使出国旅行的用户能够在任何他或她希望的地方持续使用他或她的移动电话,因为许多国际 GSM 网络企业已经相互签订了漫游协议。 [0006] 传统上,在基于GSM的移动服务的用户从一个国家移动到另一个国家并因此执行这些国家之间的漫游过程的情况下,为了选择预先在移动终端中注册的电话号码并使用 选择电话号码向接收方拨打电话,用户必须在漫游前将相应的国家代码附加到注册的电话号码。 另外,从一个国家漫游到另一个国家的用户,必须在原国家PLMN(公共陆地移动网络)上注册的电话号码上附加原国家的国家代码,才能使用户的电话号码注册 在PLMN上存储在他或她的移动终端中。 [0007] 如图。 附图说明图1是图示其中国际漫游过程发生在PLMN服务网络上的概念图的示例性视图。 参考图。 1、在有移动终端的情况下 10 在 MSC(移动交换中心)注册的用户 30 国家代码为“0033”的 PLMN B 服务在 MSC 内漫游 20 PLMN 区域 国家代码为“0044”的服务,移动终端的用户 10 必须将国家代码“0033”附加到预存的电话号码才能拨打预存的电话号码。 除非用户将国家代码“0033”附加到预存的电话号码,否则可能会出现错误的电话呼叫注册到国家代码为“0044”的PLMN A服务的另一方。 例如,在移动终端 10 之前存储了一个电话号码“123-4567”,移动终端的用户 10 仅选择电话号码 123-4567 而不将适当的国家代码附加到电话号码“123-4567”,PLMN A 服务 MSC 20 拨打电话,拨打错误的电话号码“0044-123-4567”而不是正确的电话号码“0033-123-4567”。 [0008] 相反,在PLMN B服务用户尝试在移动终端中存储的情况下 10 PLMN A业务MSC区域内注册PLMN A业务的用户电话号码 20 ,用户必须在用户电话号码后附加一个与PLMN A业务对应的国家代码‘0044’。 否则,移动端 10 将用户的电话号码识别为注册到 PLMN B 服务的用户的电话号码。 [0009] 以这种方式,传统上,在这种PLMN服务的用户从一个国家移动到另一个国家并因此在国家之间发生漫游过程的情况下,他或她必须在他或她的电话号码中附加一个额外的国家代码。 为了给被叫打电话:一方或在移动终端中存储任何电话号码,给用户带来不便。 发明内容 [0010]因此,鉴于上述问题做出了本发明,并且本发明的目的是提供一种移动终端,用于在移动终端中存储任何电话号码,并在用户使用时自动生成国家代码。 正在通过从一个国家移动到另一个国家来进行国际漫游,以便在移动终端上不附加国家代码的情况下向被叫方拨打电话。 [0011] 本发明的另一个目的是提供一种存储电话号码的方法,该方法在接收到电话号码存储命令时自动生成国家代码。 [0012] 本发明的又一个目的是提供一种查找电话号码的方法,该方法在接收到电话号码搜索命令时自动生成国家代码。 [0013] 根据本发明的一个方面,上述和其他目的可以通过提供一种用于向移动服务订户提供移动服务的移动终端来实现,包括:国家代码存储单元,用于将每个移动通信网络ID与 具有移动通信网络的规定国家的国家代码,并存储和管理移动通信网络ID和国家代码的耦合结果,其中移动通信网络ID是从多个移动通信网络MSC中的每一个接收的( 移动交换中心)为每个服务区提供移动通信网络服务; 用户信息存储单元,用于存储和管理移动服务用户的注册信息和移动服务使用历史信息; 电话号码存储单元,用于存储和管理电话号码信息; 控制器,用于检测当前PLMN服务的移动通信网络ID,并在接收到电话号码存储命令或电话号码搜索命令时,从用户信息存储单元中检索移动服务使用历史信息,用于确定是否有漫游操作。 移动终端基于当前PLMN服务的移动通信网络ID和移动服务使用历史信息执行,用于使用条目电话号码执行电话号码存储命令或电话号码搜索命令之一,并且 检测到的国家代码。 [0014] 根据本发明的另一方面,提供了一种在移动终端中存储电话号码的方法,用于存储和管理各个国家的国家代码信息、移动服务用户的注册信息和移动服务使用历史信息,包括 步骤:a)根据电话号码存储命令读取外部入口电话号码; b)分析在步骤(a)中读取的电话号码以确定该电话号码是否具有国家代码; c)如果步骤(b)的电话号码没有国家代码,则使用当前PLMN业务的移动通信网络ID,获取移动终端所在国家的国家代码; d)将在步骤(a)中读取的电话号码和在步骤(c)中检索到的国家代码存储在移动终端中。 [0015] 根据本发明的又一方面,提供了一种在移动终端中查找电话号码的方法,该方法适用于存储和管理多个国家的国家代码信息、移动服务用户的注册信息和移动服务使用历史信息, 包括以下步骤: a)在接收到电话号码搜索命令时,从包含在移动终端中的存储器中读取请求搜索的电话号码; b) 检测移动终端所在国家的国家代码; c) 将在步骤 (a) 读取的电话号码中包含的国家代码与在步骤 (b) 检测到的国家代码进行比较; d)根据步骤(c)的结果,以规定的显示格式显示在步骤(a)中读取的电话号码。 附图的简要说明 [0016] 本发明的上述和其他目的、特征和其他优点将从以下结合附图的详细描述中得到更清楚的理解,其中: [0017]如图。 附图说明图1是表示国家间漫游发生在PLMN服务网络上的概念图的示例图。 [0018] 如图。 图2为本发明较佳实施例的移动终端示意图。 [0019] 如图。 图3是示出根据本发明的优选实施例的使用国家代码表在其中存储国家代码的示例性配置的视图; [0020] 如图。 图4是表示本发明的优选实施方式的电话号码存储部中的电话号码的存储/管理的结构例的图。 [0021] 如图。 图5是说明根据本发明优选实施例的用于存储电话号码的过程的流程图; [0022] 如图。 图6是说明根据本发明优选实施例的自动生成国家代码的过程的流程图; 和 [0023] 如图。 图7是说明根据本发明优选实施例的查找电话号码的过程的流程图 优选实施例的详细说明 [0024] 将参照附图详细描述本发明的优选实施例。 在附图中,相同或相似的元件由相同的附图标记表示,即使它们在不同的附图中被描绘。 在以下描述中,当包含在本文中的已知功能和配置可能使本发明的主题不清楚时,将省略它们的详细描述。 [0025] 如图。 图2是示出了根据本发明优选实施例的移动终端的示意图。 参考图。 2、根据本发明的移动终端包括输入单元 110 , 一个控制器 120 ,订户信息存储单元 130 , 国家代码表 140 ,电话号码存储单元 150 , 和一个显示器 160 . [0026] 输入单元 110 用于执行用户与其移动终端之间的接口。 例如,这种输入单元的一个代表例子 110 是键盘。 显示器 160 显示运行状态和外部输入项。 输入单元 110 和显示器 160 用于执行移动终端和用户之间的接口,通常与扬声器和麦克风(未示出)一起包含在普通移动终端中,因此在下文中将省略对其的详细描述。 [0027] 国家代码表 140 存储和管理各个国家的国家代码信息,以实现相互国际漫游。 用于在国家代码表中存储国家代码的示例性结构 140 在图 1 中描绘。 3.参考图。 3、国家代码表 140 将每个移动通信网络ID与该移动通信网络所在的规定国家的国家代码进行耦合,并单独存储和管理多个网络ID和国家代码对,其中接收移动通信网络ID 多个MSC,用于为每个服务区域提供移动通信网络服务。 [0028] 移动通信网络ID是从为每个服务区域提供移动通信网络服务的MSC发送到移动终端的特定信息。 这种移动通信网络ID包括MCC(移动国家代码)、MNC(移动网络代码)、LAI(位置区域标识)和PLMN企业ID。 [0029] 订户信息存储单元 130存储和管理移动服务用户的注册信息和移动服务使用历史信息。 移动服务用户注册信息是当移动服务用户作为会员加入规定的移动通信服务时存储在移动终端中的信息。 这种移动通信服务订户的注册信息的代表性示例是PLMN(即,归属PLMN)的MCC(以下称为H_MCC)。 移动服务使用历史信息是订户的使用记录信息,从订户的移动服务注册时间到订户最近一次使用的时间存储,并且通常存储在移动终端中。 移动服务使用历史信息的代表性示例是指示移动终端的最近使用记录的PLMN(即,注册的PLMN)的MCC(以下称为R_MCC)。 [0030] 电话号码存储单元 150 存储和管理用户输入的电话号码信息。 用于在电话号码存储单元中存储/管理电话号码的示例性结构 150 如图所示。 4.参考图。 4、电话号码存储单元 150 包括接收信息存储字段(例如,接收者姓名)、国家代码存储字段和电话号码存储字段。 电话号码存储单元 150 将电话号码分为国家码和不包括国家码的普通电话号码,并存储分为国家码和普通电话号码的电话号码,如图2所示。 4. [0031] 控制器 120 根据外部控制命令控制移动终端的操作。 特别是控制器 120 使用移动服务用户的注册信息和存储在用户信息存储单元中的移动服务使用历史信息自动生成移动终端所在国家的国家代码 130 . 控制器 120 调整国家代码以执行新的电话号码存储命令或预先存储的电话号码搜索命令。 [0032] 一种自动生成国家代码的方法、一种使用国家代码存储电话号码的方法、以及一种使用国家代码查找电话号码的方法如图1和图2所示。 5-7,分别。 [0033] 如图。 图5是说明根据本发明优选实施例的用于存储电话号码的过程的流程图。 参考图。 参照图2和图5,如果用户在输入单元上选择用于存储电话号码的命令 110 并在步骤 S 输入所需的电话号码 110 , 控制器 120 读取入口电话号码并在步骤 S 确定 120 入口电话号码是否有国家代码。 控制器 120 在步骤 S 确定输入电话号码中是否包含特定代码或特定号码排列 120 . 例如,控制器确定输入单元输入的电话号码中是否包含“00”或“+”的特定信息 110 ,因为一般国家代码以“00”或“+”的特定信息开头,如“0044”或“+44”所示。 [0034] 控制器 120 在步骤 S 确定 130 是否根据步骤S的结果自动生成移动终端所在国家的国家代码 120 . 如果在步骤 S 确定 120 输入电话号码没有国家代码,控制器 120 在步骤 S,使用当前 PLMN 服务的移动通信网络 ID 自动生成国家代码 150 ,并将自动生成的国家代码和输入的电话号码存储在电话号码存储单元中 150 在步骤 S 160 . 如果在步骤 S 确定 120 输入电话号码有国家代码,控制器 120 将输入电话号码存储在电话号码存储单元中 150 在步骤 S 140 . 控制器 120 分别存储在电话号码存储单元中 150 从输入单元接收到的国家代码 110 或在步骤 S 自动生成 150,以及不包括国家/地区代码的电话号码。 控制器 120 将国家代码存储在电话号码存储单元的国家代码字段中 150 ,以及电话号码存储单元的电话号码字段中不包括国家代码的电话号码 150 . [0035] 在此,请注意图。 图6说明步骤S的过程 150 图。 5 详细。 如图。 图6是说明根据本发明优选实施例的用于自动生成国家代码的过程的流程图。 参考图。 2和6,如果控制器 120 决定自动生成国家代码,它在步骤 S 检查当前 PLMN 服务的移动通信网络 ID(即 MCC) 151 ,并使用先前存储在订户信息存储单元中的移动服务使用历史信息,检查移动终端最近使用移动通信网络的另一个ID(即,R_MCC) 130 在步骤 S 153 ,判断是否执行漫游服务。 控制器 120 在步骤 S 确定 155 步骤S的移动通信网络ID(MCC)是否 151 与步骤 S 的另一个 ID (R_MCC) 相同 153 . 根据判断结果,控制器 120 从预存的国家代码表中检索对应于MCC或R_MCC的国家代码,并在步骤S生成正确的国家代码 157 或小号 159 . 如果在步骤 S 确定 155 如果移动通信网络 ID (MCC) 与另一个 ID (R_MCC) 相同,则控制器 120 确定未执行漫游服务并检索与在步骤S确认的ID(R_MCC)对应的国家代码 153 从国家代码表 140 . 如果在步骤 S 确定 155 即移动通信网络 ID (MCC) 与其他 ID (R_MCC) 不同,控制器 120 确定执行漫游服务并检索与在步骤 S 确认的 ID (MCC) 对应的国家代码 151 从国家代码表 140 . 控制器 120 然后将检索到的国家代码自动分配为移动终端所在国家的国家代码。 [0036] 例如,如果任何移动服务用户在使用国家代码“0044”的地区输入下表1中所示的电话号码,并试图将输入的电话号码存储在用户所携带的移动终端中, 基于图1和2所示方法在移动终端中存储入口电话号码的结果。 5-6如下表2所示: [0037] 表格1 姓名 电话号码 父亲 0208775331 母亲 0208786998 老板 07787816714  American_uncle 001-778835991 [0038] 表 2 姓名 国家代码 电话号码 父亲 0044 0208775331 母亲 0044 0208786998 老板 0044 07787816714 American_uncle  001 0778835991 [0039] 参照上述表1~表2,在用户手动输入国家代码的“American_uncle”的情况下,移动终端存储用户输入的国家代码和电话号码。 在“父亲”、“母亲”和“老板”的情况下,用户没有输入国家代码,可以看出用户所在国家(或地区)的国家代码“0044” 位于每个电话号码的前面会自动附加。 [0040] 如图。 图7是说明根据本发明优选实施例的查找电话号码的过程的流程图。 参考图。 参照图2和图7,如果用户在输入单元上选择用于查找电话号码的命令 110 并在步骤 S 输入所需的搜索信息 210 , 控制器 120 搜索电话号码存储单元 150 ,并从电话号码存储单元中检索对应的电话号码 150 在步骤 S 220 . 控制器 120 在步骤S确定移动终端所在国家的国家代码 230 ,为移动终端用户所在的国家。 控制器 120 在步骤 S 确定 240 是否在步骤 S 确定的国家代码 230 与步骤 S 中找到的电话号码中包含的其他国家/地区代码相同 220 . 基于在步骤 S 比较两个国家代码的结果 240 , 控制器 120控制显示 150 在步骤 S 以规定的显示格式显示找到的电话号码 250 – 270 . 如果在步骤 S 确定 240 在步骤 S 确定的国家代码 230 与步骤 S 中找到的电话号码中包含的其他国家/地区代码相同 220 , 控制器 120 在步骤 S 从找到的电话号码中删除国家代码 250 , 并控制显示 160 在步骤 S 显示不包括国家代码的电话号码 260 . 另一方面,如果在步骤 S 确定 240 在步骤 S 确定的国家代码 230 与步骤 S 中找到的电话号码中包含的其他国家/地区代码不同 220 , 控制器 120 控制显示 160 在步骤 S 显示找到的电话号码 270 . 在这种情况下,可以以用户预设的显示格式来显示结果。 例如,在查找到的电话号码由国家代码、地区号码和不包括国家代码和地区号码的公共电话号码组成的情况下,国家代码、地区号码和公共电话号码 除国家代码和地区号码外,按照用户自定义的显示格式进行区分显示。 例如,可以根据用户自定义的显示格式,在国家代码、地区号码和常用电话号码之间插入“-”等特定符号,也可以只在国家代码后面添加“-”。 这种显示格式可以根据用户定义信息的类型以各种方式应用。 [0041] 例如,在电话号码存储单元中存储电话号码的情况下 150 如上表2的形式,用户在国家代码为“0044”的某个地区输入查找“父亲”电话号码的命令,在手机中查找“父亲”电话号码的结果 号码存储单元 150 基于图1和2所示的方法。 5-7 以不包括国家代码“0044”的格式(即 0208775331)显示。 这种显示格式可以根据用户定义信息的类型以各种方式应用。 [0042] 在另一示例中,在电话号码存储在电话号码存储单元中的情况下 150 如上表2的形式,用户在国家代码为“0044”的地区以外的地方输入查找“父亲”电话号码的命令,得到“父亲”电话号码的结果 在电话号码存储单元中 150 基于图1所示的方法。 7以a格式(即0044-0208775331)显示,包括国家代码“0044”。 这种显示格式可以根据用户定义信息的类型以各种方式应用。 [0043] 从上面的描述可以看出,在用户从一个国家移动到另一个国家来执行国际漫游业务的情况下,移动终端自动生成国家代码,而不需要在移动终端上附加国家代码来拨打电话。 发送给被叫方,或在移动终端中存储任意电话号码。 因此,本发明在执行国家间国际漫游业务时,自动处理移动终端中的国家代码,使得移动服务用户在从一个国家移动到另一个国家时,无需在其移动终端中手动输入国家代码。 另一个国家,从而增加了用户的便利性。 [0044] 尽管为了说明的目的已经公开了本发明的优选实施例,但是本领域技术人员将理解,在不背离所附权利要求中公开的本发明的范围和精神的情况下,各种修改、添加和替换是可能的。 本发明已经在GSM系统上公开,然而,它也可以应用于例如使用支持GSM和CDMA方案的芯片组以及支持它们的协议的宽带CDMA系统。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.125 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN100527870C(String), CN1518387A(String), EP1441557A2(String), EP1441557A3(String), EP1441557B1(String), KR100929090B1(String), KR1020040067277A(String), US20040147260A1(String), US20070178896A1(String), US7245911B2(String), US7418262B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN100527870C(String), CN1518387A(String), EP1441557A2(String), EP1441557A3(String), EP1441557B1(String), KR100929090B1(String), KR1020040067277A(String), US20040147260A1(String), US20070178896A1(String), US7245911B2(String), US7418262B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7245911B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN100527870C(String), CN1518387A(String), EP1441557A2(String), EP1441557A3(String), EP1441557B1(String), KR100929090B1(String), KR1020040067277A(String), US20040147260A1(String), US20070178896A1(String), US7245911B2(String), US7418262B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), CN100527870C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), CN1518387A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), EP1441557A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), EP1441557A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), EP1441557B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), KR100929090B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), KR1020040067277A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.605 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.605 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), US20040147260A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), US20070178896A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), US7245911B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271655(Integer), US7418262B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.748 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7245911B2(String), US7245911B2(String), 1184601600(Integer), 271655(Integer), 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185969(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185969(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185969(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:49.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185969(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185969(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20110319037A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Implementing method for matching frequency bands of mobile terminals, and mobile terminal and mainboard thereof(String), 移动终端频段匹配的实现方法、移动终端和主板(String), US20110319037A1(String), An implementing method for matching the frequency bands of the mobile terminals, a mobile terminal, and a mainboard thereof are disclosed. The mobile terminal involves a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module. The mobile terminal further involves a first connection selection module and a second connection selection module. The implementing method for matching the frequency bands of the mobile terminals comprises the following steps. The multi frequency bands bonding pad compatibility is achieved respectively on the circuit board by the radio-frequency transmitting module, the radio-frequency receiving module and the radio-frequency front-end module. When the mobile terminal has to work within a certain frequency band, one end of the first connection selection module is connected with the transmitting pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency transmitting module. One end of the second connection selection module is connected with the receiving pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency receiving module. The radio-frequency front-end module is connected with the radio-frequency transmitting module and the radio-frequency receiving module.(String), 本发明公开了一种移动终端频段匹配的实现方法、移动终端及其主板。 移动终端包括具有至少两个频段的信号发射/接收模块、射频发射模块、射频接收模块和射频前端模块。 移动终端还包括第一连接选择模块和第二连接选择模块。 该移动终端频段匹配的实现方法包括以下步骤。 射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容。 当移动终端必须工作在某个频段时,第一连接选择模块的一端与信号收发模块中该频段的发射管脚相连,另一端与射频相连。 发射模块。 第二连接选择模块的一端与信号发射/接收模块中频段的接收引脚相连,另一端与射频接收模块相连。 射频前端模块与射频发射模块和射频接收模块连接。(String), US13/225687(String), 1315238400(Integer), US20110319037A1(String), 1325088000(Integer), 美国(String), 2(Integer), CN(String), 5(Integer), 3(Integer), US20080100374A1 | US5915212A | US6845126B2(String), 21(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185970(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f27bccb47a32427a91a5dada4cafcf34.png(String), 185970(Integer), f27bccb47a32427a91a5dada4cafcf34.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Implementing method for matching frequency bands of mobile terminals, and mobile terminal and mainboard thereof(String), 移动终端频段匹配的实现方法、移动终端和主板(String), US20110319037A1(String), An implementing method for matching the frequency bands of the mobile terminals, a mobile terminal, and a mainboard thereof are disclosed. The mobile terminal involves a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module. The mobile terminal further involves a first connection selection module and a second connection selection module. The implementing method for matching the frequency bands of the mobile terminals comprises the following steps. The multi frequency bands bonding pad compatibility is achieved respectively on the circuit board by the radio-frequency transmitting module, the radio-frequency receiving module and the radio-frequency front-end module. When the mobile terminal has to work within a certain frequency band, one end of the first connection selection module is connected with the transmitting pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency transmitting module. One end of the second connection selection module is connected with the receiving pin of the frequency band in the signal transmitting/receiving module, and the other end is connected with the radio-frequency receiving module. The radio-frequency front-end module is connected with the radio-frequency transmitting module and the radio-frequency receiving module.(String), 本发明公开了一种移动终端频段匹配的实现方法、移动终端及其主板。 移动终端包括具有至少两个频段的信号发射/接收模块、射频发射模块、射频接收模块和射频前端模块。 移动终端还包括第一连接选择模块和第二连接选择模块。 该移动终端频段匹配的实现方法包括以下步骤。 射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容。 当移动终端必须工作在某个频段时,第一连接选择模块的一端与信号收发模块中该频段的发射管脚相连,另一端与射频相连。 发射模块。 第二连接选择模块的一端与信号发射/接收模块中频段的接收引脚相连,另一端与射频接收模块相连。 射频前端模块与射频发射模块和射频接收模块连接。(String), US13/225687(String), 1315238400(Integer), US20110319037A1(String), 1325088000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 5(Integer), 3(Integer), US20080100374A1 | US5915212A | US6845126B2(String), \20230420\f27bccb47a32427a91a5dada4cafcf34.png(String), 21(Integer), 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:50.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 1. An implementing method for matching frequency bands of a mobile terminal, which comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module, wherein said mobile terminal further comprises a first connection selection module and a second connection selection module, the method comprising:achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module; andwhen said mobile terminal needs to work within a certain frequency band, connecting one end of said first connection selection module to a transmitting pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency transmitting module; connecting one end of said second connection selection module to a receiving pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency receiving module; and connecting said radio-frequency front-end module to said radio-frequency transmitting module and said radio-frequency receiving module.(String), 1.如权利要求8所述的移动终端,其中所述射频发射模块包括射频功率放大器、耦合器和匹配网络。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 2. The implementing method as claimed in claim 1, wherein said first connection selection module or said second connection selection module comprises at least two of resistors, capacitor(s) or inductor(s).(String), 12.如权利要求8所述的移动终端,其中所述射频接收模块包括匹配网络。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 3. The implementing method as claimed in claim 1, wherein achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module includes that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module.(String), 13.如权利要求8所述的移动终端,其中所述射频前端模块包括双工器和匹配网络。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 4. The implementing method as claimed in claim 1, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 14.如权利要求8所述的移动终端,其中所述移动终端为手机或网卡。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 5. The implementing method as claimed in claim 1, wherein said radio-frequency receiving module comprises a matching network.(String), 15.一种移动终端主板,主板包括信号发射/接收模块接口、射频发射模块接口、射频接收模块接口和射频前端模块接口,其中所述主板还包括第一连接选择模块接口和第二连接选择模块接口。模块接口,其中,所述第一连接选择模块接口的一端用于选择性地连接所述信号发射/接收模块接口中的管脚,其另一端用于连接所述射频发射模块接口。所述第二连接选择模块的一端用于选择性地连接所述信号发射/接收模块接口中的管脚,其另一端用于连接所述射频接收模块接口。所述射频前端模块接口连接所述射频发射模块接口和所述射频接收模块接口。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 6. The implementing method as claimed in claim 1, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 16.如权利要求3所述的实施方法,其中所述射频发射模块包括射频功率放大器、耦合器和匹配网络。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 7. The implementing method as claimed in claim 1, wherein said mobile terminal is a cell phone or a network card.(String), 17.如权利要求3所述的实施方法,其中所述射频接收模块包括匹配网络。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 8. A mobile terminal, which comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module, a radio-frequency front-end module and an antenna module, wherein said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieve the multi frequency bands bonding pad compatibility respectively on a circuit board; andsaid mobile terminal further comprises a first connection selection module and a second connection selection module, wherein one end of said first connection selection module is connected to a transmitting pin of a certain frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency transmitting module; one end of said second connection selection module is connected to a receiving pin of the frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency receiving module; and said radio-frequency front-end module is connected to said radio-frequency transmitting module and said radio-frequency receiving module.(String), 18.如权利要求3所述的实施方法,其中所述射频前端模块包括双工器和匹配网络。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 9. The mobile terminal as claimed in claim 8, wherein said first connection selection module or said second connection selection module comprises at least two of resistors, capacitor(s) or inductor(s).(String), 19.如权利要求10所述的移动终端,其中所述射频发射模块包括射频功率放大器、耦合器和匹配网络。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 10. The mobile terminal as claimed in claim 8, wherein said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieving the multi frequency bands bonding pad compatibility respectively on a circuit board specifically refers to that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module.(String), 20.如权利要求10所述的移动终端,其中所述射频接收模块包括匹配网络。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 11. The mobile terminal as claimed in claim 8, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 21.如权利要求10所述的移动终端,其中所述射频前端模块包括双工器和匹配网络。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 12. The mobile terminal as claimed in claim 8, wherein said radio-frequency receiving module comprises a matching network.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 13. The mobile terminal as claimed in claim 8, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 1(Integer), 12(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 14. The mobile terminal as claimed in claim 8, wherein said mobile terminal is a cell phone or a network card.(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 15. A mainboard for a mobile terminal, the mainboard comprising a signal transmitting/receiving module interface, a radio-frequency transmitting module interface, a radio-frequency receiving module interface and a radio-frequency front-end module interface, wherein said mainboard further comprises a first connection selection module interface and a second connection selection module interface, wherein one end of said first connection selection module interface is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency transmitting module interface; one end of said second connection selection module is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency receiving module interface; and said radio-frequency front-end module interface connects said radio-frequency transmitting module interface and said radio-frequency receiving module interface.(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 16. The implementing method as claimed in claim 3, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 1(Integer), 15(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 17. The implementing method as claimed in claim 3, wherein said radio-frequency receiving module comprises a matching network.(String), 1(Integer), 16(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 18. The implementing method as claimed in claim 3, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 1(Integer), 17(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 19. The mobile terminal as claimed in claim 10, wherein said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network.(String), 1(Integer), 18(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 20. The mobile terminal as claimed in claim 10, wherein said radio-frequency receiving module comprises a matching network.(String), 1(Integer), 19(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185970(Integer), 21. The mobile terminal as claimed in claim 10, wherein said radio-frequency front-end module comprises a duplexer and a matching network.(String), 1(Integer), 20(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185970(Integer), [0001]This is a continuation of International Application PCT/CN2009/075636, with an International Filing Date of Dec. 16, 2009, which claims priority to Chinese Application No. 200910108393.7, filed Jun. 24, 2009, each of which is incorporated by reference. TECHNICAL FIELD [0002]The present invention relates to the field of communication technology and, particularly, to an implementing method for matching the frequency bands of the mobile terminals, and a mobile terminal and a mainboard thereof. BACKGROUND ART [0003]The development of the modern communication technology is extremely rapid. Not only there are a variety of systems, such as Global System for Mobile Communication (GSM for short), Code Division Multiple Access (CDMA for short), Wideband Code Division Multiple Access (WCDMA for short), etc., but also there are a variety of frequency bands which a same system needs to support, for example, CDMA needs to support 800M, 1.9 G, 450M, etc. In order to support multi frequency bands, radio-frequency transmitting/receiving circuit(s) corresponding to each of the frequency bands has to be added into the mobile terminal of a certain system when the circuit thereof is designed. However, for a specific market and a specific operator, normally only a specific frequency band is used. Taking CDMA as an example, CDMA 800M is used in China, while CDMA 1.9 G is used in Indonesia. [0004]FIG. 1 is a schematic diagram of a module in which a mobile terminal with double frequency bands is supported by two radio-frequency transmitting/receiving circuits according to the related art. As shown in FIG. 1, it illustrates the existing method in which two radio-frequency transmitting/receiving circuits are used to support a mobile terminal with double frequency bands. The function of a band 1 is achieved by means of one radio-frequency transmitting/receiving circuit supporting the band 1, and the function of a band 2 is achieved by means of the other radio-frequency transmitting/receiving circuit supporting the band 2. Such method of employing a plurality of radio-frequency transmitting/receiving circuits to make multi frequency bands compatible cannot be realized in many mobile terminals since it occupies a relatively larger area of the circuit board. At present, this is addressed by a method of designing a plurality of circuit boards. Taking CDMA as an example, in a common method, as for the CDMA 800M market, one circuit board is design on which only the radio-frequency transmitting/receiving devices related to CDMA 800M are bonded and the radio-frequency transmitting/receiving devices related to CDMA 1.9 G are not bonded; while as for the CDMA 1.9 G market, one circuit board is designed on which only the radio-frequency transmitting/receiving devices related to CDMA 1.9 G are bonded and the radio-frequency transmitting/receiving devices related to CDMA 800M are not bonded. The circuit devices of the corresponding frequency band are bonded according to the specific market demand. Such solution causes that the number of the circuit boards to be designed in the mobile terminal is increased, and thus the cost is improved, the design period is prolonged, and more developers are needed. SUMMARY OF THE INVENTION [0005]The technical problem to be addressed by the present invention is to provide an implementing method for matching the frequency bands of the mobile terminals, a mobile terminal, and a mainboard thereof, so as to overcome the defects that the number of the designed circuit boards in the mobile terminal is increased, the cost is improved, the design period is prolonged, and more developers are needed. [0006]In order to solve the abovementioned technical problem, the present invention provides an implementing method for matching frequency bands of a mobile terminal, the mobile terminal comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module and a radio-frequency front-end module, said mobile terminal further comprises a first connection selection module and a second connection selection module, and the implementing method for matching the frequency bands of the mobile terminal comprises:[0007]achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module;[0008]when said mobile terminal needs to work within a certain frequency band, connecting one end of said first connection selection module to the transmitting pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency transmitting module; connecting one end of said second connection selection module to a receiving pin of the frequency band in said signal transmitting/receiving module, and connecting the other end thereof to said radio-frequency receiving module; and connecting said radio-frequency front-end module to said radio-frequency transmitting module and said radio-frequency receiving module. [0009]Further, in the abovementioned method, said first selection module or said second selection module comprises at least two of resistors, capacitor(s) or inductor(s). [0010]Further, in the abovementioned method, achieving the multi frequency bands bonding pad compatibility on a circuit board respectively by said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module specifically refers to that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module. [0011]Further, in the abovementioned method, said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network. [0012]Further, in the abovementioned method, said radio-frequency receiving module comprises a matching network. [0013]Further, in the abovementioned method, said radio-frequency front-end module comprises a duplexer and a matching network. [0014]In order to solve the abovementioned technical problem, the present invention also provides a mobile terminal, and the mobile terminal comprises a signal transmitting/receiving module with at least two frequency bands, a radio-frequency transmitting module, a radio-frequency receiving module, a radio-frequency front-end module and an antenna module, in which said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieve the multi frequency bands bonding pad compatibility respectively on a circuit board; and[0015]said mobile terminal further comprises a first connection selection module and a second connection selection module, in which one end of said first connection selection module is connected to a transmitting pin of a certain frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency transmitting module; one end of said second connection selection module is connected to a receiving pin of the frequency band in said signal transmitting/receiving module, and the other end thereof is connected to said radio-frequency receiving module; and said radio-frequency front-end module is connected to said radio-frequency transmitting module and said radio-frequency receiving module. [0016]Further, said first selection module or said second selection module comprises at least two of resistors, capacitor(s) or inductor(s). [0017]Further, said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module achieving the multi frequency bands bonding pad compatibility respectively on a circuit board specifically refers to that said radio-frequency transmitting module, said radio-frequency receiving module and said radio-frequency front-end module can be compatible on the circuit board with the various frequency bands in said signal transmitting/receiving module. [0018]Further, said radio-frequency transmitting module comprises a radio-frequency power amplifier, a coupler and a matching network. [0019]Further, said radio-frequency receiving module comprises a matching network. [0020]Further, said radio-frequency front-end module comprises a duplexer and a matching network. [0021]In order to solve the abovementioned technical problem, the present invention also provides a mainboard for a mobile terminal, the mainboard comprises a signal transmitting/receiving module interface, a radio-frequency transmitting module interface, a radio-frequency receiving module interface and a radio-frequency front-end module interface, and said mainboard further comprises a first connection selection module interface and a second connection selection module interface, in which one end of said first connection selection module interface is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency transmitting module interface; one end of said second connection selection module is used for selectively connecting a pin in said signal transmitting/receiving module interface, and the other end thereof for connecting said radio-frequency receiving module interface; and said radio-frequency front-end module interface connects said radio-frequency transmitting module interface and said radio-frequency receiving module interface. [0022]In this case, in the abovementioned method or mobile terminal, said mobile terminal may be a cell phone or a network card, etc. [0023]Since the technical solution disclosed by the present invention achieves the compatibility of multi frequency bands by using a single radio-frequency transmitting/receiving circuit, it can realize that one circuit board implements multi frequency bands in the miniaturization design of mobile terminals, which replaces the current multi circuit boards, so as to reduce the research and development costs and decrease the period of research and development and research personnel. BRIEF DESCRIPTION OF THE DRAWINGS [0024]FIG. 1 is a module schematic diagram in which a mobile terminal with double frequency bands is supported by two radio-frequency transmitting/receiving circuits according to the related art; [0025]FIG. 2 is a module schematic diagram of a mobile terminal with double frequency bands in an embodiment of the present invention; [0026]FIG. 3 is a module schematic diagram of a mobile terminal of CDMA 800M and CDMA 1900M in an embodiment of the present invention; [0027]FIG. 4 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N frequency bands in an embodiment of the present invention; [0028]FIG. 5 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N-M frequency bands in an embodiment of the present invention; and [0029]FIG. 6 is a module schematic diagram of a mobile terminal in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0030]In order to further describe the technical means adopted by the present invention to achieve the predetermined target and the effects thereof, the implementing method for matching the frequency bands of mobile terminals, the mobile terminal, and the mainboard thereof will be described in detail hereinbelow in conjunction with the accompanying drawings and the embodiments. [0031]FIG. 2 is a module schematic diagram of a mobile terminal with double frequency bands in an embodiment of the present invention, and as shown in FIG. 2, a double frequency bands signal transmitting/receiving module 101 fulfills the transmission and reception of the radio-frequency signals of the frequency band 1 and the frequency band 2, and a first connection selection module 102 and a second connection selection module 103 select the frequency band 1 or the frequency band 2 to be connected to a single radio-frequency transmitting/receiving circuit according to the requirement, and at the same time disconnect the signal with unnecessary frequency band from the single radio-frequency transmitting/receiving circuit. A radio-frequency transmitting module 104, a radio-frequency receiving module 105 and a radio-frequency front-end module 106 are compatible with the frequency band 1 and the frequency band 2 on the circuit board, therefore the modules with the corresponding frequency band can be bonded according to the practical requirement, and an antenna module 107 is selected to support the modules with the corresponding frequency band, so as to achieve that the single radio-frequency transmitting/receiving circuit supports the double frequency bands. In this embodiment, the single radio-frequency transmitting/receiving circuit specifically refers to the circuit composed of the radio-frequency transmitting module 104, the radio-frequency receiving module 105, the radio-frequency front-end module 106 and the antenna module 107. [0032]Specifically speaking, if the mobile terminal supporting the frequency band 1 is needed, the first connection selection module 102 connects the transmitting signal of the frequency band 1 in the double frequency bands signal transmitting/receiving module 101 to the single radio-frequency transmitting/receiving circuit, and disconnects the transmitting signal of the frequency band 2 in the double frequency bands signal transmitting/receiving module 101 from the single radio-frequency transmitting/receiving circuit; and the second connection selection module 103 connects the receiving signal of the frequency band 1 in the double frequency bands signal transmitting/receiving module 101 to the single radio-frequency transmitting/receiving circuit, and disconnects the receiving signal of the frequency band 2 in the double frequency bands signal transmitting/receiving module 101 from the single radio-frequency transmitting/receiving circuit. The radio-frequency transmitting module 104, the radio-frequency receiving module 105 and the radio-frequency front-end module 106 are all bonded with the modules corresponding to the frequency band 1, and are connected to the antenna module 107 supporting the frequency band 1, so as to fulfill the radio-frequency support for the frequency band 1. [0033]FIG. 3 is a module schematic diagram of a mobile terminal of CDMA 800M and CDMA 1900M in an embodiment of the present invention, and as shown in FIG. 3, the master chip 201 can fulfill the transmission and reception of the radio-frequency signals of CDMA 800M and CDMA 1900M. [0034]The first connection selection module 202 is composed of two capacitors, wherein one end of a capacitor A is connected to the transmitting pin of CDMA 800M of the master chip 201, one end of a capacitor B is connected to the transmitting pin of CDMA 1900M of the master chip 201, and the other ends of the capacitors A and B are connected with each other to join a radio-frequency transmitting path. [0035]The second connection selection module 203 is composed of four capacitors, and in this embodiment, since the receiving signals of CDMA 800M and CDMA 1900M are both differential signals, there are two signal lines for each receiving signal, wherein capacitors M and N respectively have one end which is respectively connected to one of the two differential receiving pins of CDMA 800M of the master chip 201, capacitors X and Y respectively have one end which is respectively connected to one of the two differential receiving pins of CDMA 1900M of the master chip 201, the other ends of the capacitors M and X are connected with each other to join the radio-frequency receiving path, and the other ends of the capacitors N and Y are connected with each other to join the radio-frequency receiving path. [0036]The radio-frequency transmitting module 204 comprises a radio-frequency power amplifier, a coupler and a matching network, etc., and appropriate devices are selected to make the bonding pad compatibility of the radio-frequency power amplifiers, the couplers and the matching networks of CDMA 800M and CDMA 1900M on the circuit board. [0037]The radio-frequency receiving module 205 comprises a matching network, etc., and appropriate devices are selected to make the bonding pad compatibility of the matching networks of CDMA 800M and CDMA 1900M on the circuit board;[0038]the radio-frequency front-end module 206 comprises a duplexer and a matching network, etc., and appropriate devices are selected to make the bonding pad compatibility of the duplexers and the matching networks of CDMA 800M and CDMA 1900M on the circuit board; and[0039]the antenna module 207 achieves the compatibility of the feed point on the circuit board. [0040]In this embodiment, if CDMA 800M needs to be supported, then the capacitor A is bonded in the first connection selection module 202, and the capacitor B is not bonded; the capacitors M and N are bonded in the second connection selection module 203, and the capacitors X and Y are not bonded; a radio-frequency power amplifier, coupler and matching network corresponding to CDMA 800M are bonded in the radio-frequency transmitting module 204; a matching network corresponding to CDMA 800M is bonded in the radio-frequency receiving module 205; a duplexer and matching network corresponding to CDMA 800M are bonded in the radio-frequency front-end module, and the antenna module 207 supporting CDMA 800M is further installed, so as to fulfill the support for CDMA 800M. The matching network refers to a circuit composed of capacitor(s), inductor(s) or resistor(s). [0041]If CDMA 1900M needs to be supported, then the capacitor B is bonded in the first connection selection module 202, and the capacitor A is not bonded; the capacitors X and Y are bonded in the second connection selection module 203, and the capacitors M and N are not bonded; a radio-frequency power amplifier, coupler and matching network corresponding to CDMA 1900M are bonded in the radio-frequency transmitting module 204; a matching network corresponding to CDMA 1900M is bonded in the radio-frequency receiving module 205; a duplexer and matching network corresponding to CDMA 1900M are bonded in the radio-frequency front-end module, and the antenna module 207 supporting CDMA 1900M is further installed, so as to fulfill the support for CDMA 1900M. [0042]FIG. 2 and FIG. 3 are mainly directed to the mobile terminal with double frequency bands. If it is a mobile terminal with multi frequency bands, there are many ways to use this method. FIG. 4 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N frequency bands in an embodiment of the present invention. In FIG. 4, a single radio-frequency transmitting/receiving circuit is used to be compatible with the N frequency bands. [0043]FIG. 5 is a module schematic diagram in which a single radio-frequency transmitting/receiving circuit of a mobile terminal with multi frequency bands is compatible with N-M frequency bands in an embodiment of the present invention. As shown in FIG. 5, among N frequency bands, there are the N-M frequency bands which a single radio-frequency transmitting/receiving circuit is compatible with, and each of the rest M frequency bands is supported by using one radio-frequency transmitting/receiving circuit. [0044]FIG. 6 is a module schematic diagram of a mobile terminal in an embodiment of the present invention. As shown in FIG. 6, the mobile terminal comprises a signal transmitting/receiving module 501, a first connection selection module 502, a second connection selection module 503, a radio-frequency transmitting module 504, a radio-frequency receiving module 505, a radio-frequency front-end module 506, and an antenna module 507 which are connected in sequence. [0045]In the embodiment of the present invention, the radio-frequency transmitting module 504, the radio-frequency receiving module 505 and the radio-frequency front-end module 506 respectively achieve the multi frequency bands bonding pad compatibility on the circuit board. Herein, the multi frequency bands bonding pad compatibility specifically refers to that the radio-frequency transmitting module 504, the radio-frequency receiving module 505 and the radio-frequency front-end module 506 can be compatible with the various frequency bands in the signal transmitting/receiving module 501 on the circuit board. One end of the first connection selection module 502 is connected to the transmitting pin of a certain frequency band in said signal transmitting/receiving module, and the other end thereof is connected to the radio-frequency transmitting module 504; one end of the second connection selection module 503 is connected to the receiving pin of the frequency band in said signal transmitting/receiving module, and the other end thereof is connected to the radio-frequency receiving module 505; and the radio-frequency front-end module 506 is connected to the radio-frequency transmitting module 504 and the radio-frequency receiving module 505. [0046]What are mentioned above are merely the preferred exemplary embodiments of the present invention, which are not intended to limit the present invention; and any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be covered in the protective scope of the present invention.(String), [0001] 本申请是国际申请 PCT/CN2009/075636 的延续,国际申请日期为 2009 年 12 月 16 日,该申请要求 2009 年 6 月 24 日提交的中国申请号 200910108393.7 的优先权,每份申请均通过引用并入。 技术领域 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端频段匹配的实现方法、移动终端及其主板。 背景技术 [0003] 现代通信技术的发展非常迅速。 不仅有全球移动通信系统(简称GSM)、码分多址(简称CDMA)、宽带码分多址(简称WCDMA)等多种制式,而且还有 同一个系统需要支持的多种频段,例如CDMA需要支持800M、1.9G、450M等,为了支持多频段,射频发射/接收电路需要对应每个频段 某些系统的移动终端在设计其电路时,必须增加频段的数量。 但是,对于特定的市场和特定的运营商,通常只使用特定的频段。 以CDMA为例,中国使用CDMA 800M,而印度尼西亚使用CDMA 1.9G。 [0004] 图1为现有技术中两个射频发射/接收电路支持双频段移动终端的模块示意图。 如图1所示,说明了现有的利用两个射频发射/接收电路来支持双频段移动终端的方法。 乐队的作用 1 通过一个支持频段的射频发射/接收电路实现 1 , 和乐队的功能 2 是通过其他支持该频段的射频发射/接收电路实现的 2 . 这种采用多个射频发射/接收电路实现多频段兼容的方法由于占用的电路板面积较大,在很多移动终端中无法实现。 目前,这是通过设计多个电路板的方法来解决的。 以CDMA为例,通常的做法是,针对CDMA 800M市场,设计一块电路板,上面只绑定CDMA 800M相关的射频发射/接收器件,相关的射频发射/接收器件 CDMA 1.9 G 未绑定; 而对于CDMA 1.9G市场,设计了一块电路板,只绑定了CDMA 1.9G相关的射频发射/接收器件,没有绑定CDMA 800M相关的射频发射/接收器件。 相应频段的电路器件根据具体的市场需求进行绑定。 这种方案导致移动终端中需要设计的电路板数量增加,从而提高了成本,延长了设计周期,需要更多的开发人员。 发明内容 [0005] 本发明所要解决的技术问题是提供一种移动终端频段匹配的实现方法、移动终端及其主板,以克服设计电路板数量多的不足。 移动端增加,成本提高,设计周期延长,需要更多的开发人员。 [0006] 为了解决上述技术问题,本发明提供了一种移动终端频段匹配的实现方法,该移动终端包括至少两个频段的信号发射/接收模块、射频发射模块、 射频接收模块和射频前端模块,所述移动终端还包括第一连接选择模块和第二连接选择模块,匹配移动终端频段的实现方法包括: [0007]射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容;[0008] 当所述移动终端需要工作在某个频段时,将所述第一连接选择模块的一端连接到所述信号发射/接收模块中该频段的发射引脚,将其另一端连接到所述射频发射 模块; 所述第二连接选择模块的一端与所述信号发射/接收模块中的频段接收引脚相连,另一端与所述射频接收模块相连; 将所述射频前端模块连接至所述射频发射模块和所述射频接收模块。 [0009]进一步地,在上述方法中,所述第一选择模块或所述第二选择模块包括电阻、电容或电感中的至少两者。 [0010] 进一步地,上述方法中,所述射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容,具体是指所述射频- 频率发射模块、射频接收模块和射频前端模块可以在电路板上兼容信号发射/接收模块中的各个频段。 [0011] 进一步地,在上述方法中,所述射频发射模块包括射频功率放大器、耦合器和匹配网络。 [0012] 进一步地,在上述方法中,所述射频接收模块包括匹配网络。 [0013] 进一步地,在上述方法中,所述射频前端模块包括双工器和匹配网络。 [0014] 为了解决上述技术问题,本发明还提供了一种移动终端,该移动终端包括具有至少两个频段的信号发射/接收模块、射频发射模块、射频接收模块, 射频前端模块和天线模块,其中所述射频发射模块、所述射频接收模块和所述射频前端模块分别在电路板上实现多频段焊盘兼容 ; 和 [0015] 所述移动终端还包括第一连接选择模块和第二连接选择模块,所述第一连接选择模块的一端连接所述信号发射/接收模块中某一频段的发射引脚,另一端 其连接至所述射频发射模块; 所述第二连接选择模块的一端连接所述信号发射/接收模块中频段的接收引脚,另一端连接所述射频接收模块。 射频前端模块连接射频发射模块和射频接收模块。 [0016] 进一步地,所述第一选择模块或所述第二选择模块包括电阻、电容或电感中的至少两者。 [0017] 进一步地,所述射频发射模块、射频接收模块和射频前端模块分别在电路板上实现多频段焊盘兼容,具体是指所述射频发射模块、所述无线电 -频率接收模块和所述射频前端模块可以在电路板上兼容所述信号发射/接收模块中的各个频段。 [0018] 进一步地,所述射频发射模块包括射频功率放大器、耦合器和匹配网络。 [0019] 进一步地,所述射频接收模块包括匹配网络。 [0020] 进一步地,所述射频前端模块包括双工器和匹配网络。 [0021] 为了解决上述技术问题,本发明还提供了一种移动终端主板,该主板包括信号发射/接收模块接口、射频发射模块接口、射频接收模块接口和无线电 -频率前端模块接口,所述主板还包括第一连接选择模块接口和第二连接选择模块接口,所述第一连接选择模块接口的一端用于选择性地连接所述信号传输中的管脚/ 接收模块接口,其另一端连接所述射频发射模块接口; 所述第二连接选择模块的一端用于选择性地连接所述信号发射/接收模块接口中的管脚,其另一端用于连接所述射频接收模块接口。 所述射频前端模块接口连接所述射频发射模块接口和所述射频接收模块接口。 [0022] 此时,上述方法或移动终端中,所述移动终端可以为手机或网卡等。 [0023]由于本发明所公开的技术方案通过单一的射频发射/接收电路实现了多频段的兼容,在移动终端的小型化设计中可以实现一块电路板实现多频段,取代 电流多电路板,从而降低研发成本,减少研发和研究人员的周期。 附图的简要说明 [0024] 图1为现有技术中两个射频发射/接收电路支持双频段移动终端的模块示意图; [0025] 图2为本发明实施例中双频段移动终端的模块示意图; [0026] 图3为本发明实施例中CDMA 800M和CDMA 1900M移动终端的模块示意图; [0027] 图4为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N个频段的模块示意图; [0028] 图5为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N-M频段的模块示意图; 和 [0029] 图6为本发明实施例移动终端的模块示意图。 具体实施方式 [0030] 为了进一步说明本发明为达到预定目标所采用的技术手段及其效果,下面对移动终端频段匹配的实现方法、移动终端及其主板进行详细说明。 结合附图和实施例。 [0031] 图2为本发明实施例中双频段移动终端的模块示意图,如图2所示,双频段信号发射/接收模块 101 完成该频段射频信号的发射和接收 1 和频段 2 ,以及第一连接选择模块 102 和第二连接选择模块 103 选择频段 1 或频段 2 根据需要连接到单个射频发射/接收电路,同时断开不需要频段的信号与单个射频发射/接收电路的连接。 一种射频发射模块 104 ,射频接收模块 105 和射频前端模块 106 兼容频段 1 和频段 2 在电路板上,因此可以根据实际需要粘合相应频段的模块,以及天线模块 107 选择支持相应频段的模块,从而实现单个射频发射/接收电路支持双频段。 在本实施例中,单个射频发射/接收电路具体是指由射频发射模块组成的电路。 104 ,射频接收模块 105 , 射频前端模块 106 和天线模块 107 . [0032] 具体来说,如果移动终端支持该频段 1 需要,第一个连接选择模块 102 连接频段的发射信号 1 双频段信号发射/接收模块 101 到单射频发射/接收电路,断开该频段的发射信号 2 双频段信号发射/接收模块 101来自单个射频发射/接收电路; 和第二个连接选择模块 103 连接频段的接收信号 1 双频段信号发射/接收模块 101 到单射频发射/接收电路,断开该频段的接收信号 2 双频段信号发射/接收模块 101 来自单个射频发射/接收电路。 射频发射模块 104 ,射频接收模块 105 和射频前端模块 106 均与频段对应的模块绑定 1 ,并连接到天线模块 107 支持频段 1 ,从而实现对频段的射频支持 1 . [0033] 图3为本发明实施例中CDMA 800M和CDMA 1900M移动终端的模块示意图,如图3所示 3 , 主控芯片 201 可以完成CDMA 800M和CDMA 1900M射频信号的发射和接收。 [0034] 第一连接选择模块 202 由两个电容组成,电容A的一端接主控芯片CDMA 800M的发射脚 201 ,电容B的一端接主控芯片CDMA 1900M的发射脚 201 ,电容A、B的另一端相互连接,加入射频发射通路。 [0035] 第二连接选择模块 203 由四个电容组成,在本实施例中,由于CDMA 800M和CDMA 1900M的接收信号都是差分信号,所以每个接收信号有两条信号线,其中电容M和N的一端分别连接到 主控芯片CDMA 800M的两个差分接收引脚之一 201 ,电容X和Y各有一端分别接主控芯片CDMA 1900M的两个差分接收管脚之一 201 ,电容M和X的另一端相互连接加入射频接收通路,电容N和Y的另一端相互连接加入射频接收通路。 [0036] 射频发射模块 204 包括射频功率放大器、耦合器和匹配网络等,选择合适的器件使CDMA 800M和CDMA 1900M射频功率放大器、耦合器和匹配网络的焊盘兼容 电路板。 [0037] 射频接收模块 205 包括匹配网络等,选择合适的器件使电路板上CDMA 800M和CDMA 1900M匹配网络的焊盘兼容; [0038]射频前端模块 206 包括双工器和匹配网络等,选择合适的器件使电路板上双工器和CDMA 800M、CDMA 1900M匹配网络的焊盘兼容。 和[0039]天线模块 207 实现电路板上馈电点的兼容性。 [0040] 本实施例中,如果需要支持CDMA 800M,则在第一连接选择模块中绑定电容A 202 ,且电容器 B 未绑定; 电容器M和N在第二连接选择模块中被绑定 203 ,并且电容器 X 和 Y 未绑定; 射频发射模块中绑定了CDMA 800M对应的射频功率放大器、耦合器和匹配网络 204 ; 射频接收模块绑定了CDMA 800M对应的匹配网络 205 ; 射频前端模块中绑定了CDMA 800M对应的双工器和匹配网络,天线模块 207 进一步安装支持CDMA 800M,完成对CDMA 800M的支持。 匹配网络是指由电容器、电感器或电阻器组成的电路。 [0041] 如果需要支持CDMA 1900M,则在第一连接选择模块中键合电容B 202 , 且电容器 A 未绑定; 电容器X和Y在第二个连接选择模块中被绑定 203, 电容 M 和 N 未绑定; 射频发射模块中绑定了CDMA 1900M对应的射频功率放大器、耦合器和匹配网络 204 ; 射频接收模块绑定了CDMA 1900M对应的匹配网络 205 ; 射频前端模块中绑定了CDMA 1900M对应的双工器和匹配网络,天线模块 207 进一步安装支持CDMA 1900M,完成对CDMA 1900M的支持。 [0042] 图2和图3主要针对双频段移动终端。 如果是多频段的移动终端,使用这种方法的方式有很多种。 图4为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N个频段的模块示意图。 在图4中,采用单个射频发射/接收电路来兼容N个频段。 [0043] 图5为本发明实施例多频段移动终端的单个射频发射/接收电路兼容N-M频段的模块示意图。 如图5所示,在N个频段中,有N-M个频段是单个射频发射/接收电路兼容的,其余M个频段各由一个射频发射/接收电路支持 电路。 [0044] 图6为本发明实施例移动终端的模块示意图。 如图6所示,移动终端包括信号发射/接收模块 501 , 第一连接选择模块 502 , 第二连接选择模块 503 , 射频发射模块 504 ,射频接收模块 505 , 射频前端模块 506 , 和一个天线模块 507 它们是按顺序连接的。 [0045] 在本发明实施例中,射频发射模块 504 ,射频接收模块 505 和射频前端模块 506 分别实现电路板上的多频段焊盘兼容。 在此,多频段焊盘兼容性具体是指射频发射模块 504 ,射频接收模块 505 和射频前端模块 506 可兼容信号发射/接收模块中的各种频段 501 在电路板上。 第一连接选择模块一端 502 与所述信号发射/接收模块中某一频段的发射引脚相连,另一端与射频发射模块相连 504 ; 第二连接选择模块的一端 503 连接到所述信号发射/接收模块中的频段的接收引脚,其另一端连接到射频接收模块 505 ; 和射频前端模块 506 连接射频发射模块 504 射频接收模块 505 . [0046] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明; 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101604980A(String), CN101604980B(String), EP2448128A1(String), EP2448128A4(String), IN1865MUMNP2011A(String), US20110319037A1(String), WO2010148615A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101604980A(String), CN101604980B(String), EP2448128A1(String), EP2448128A4(String), IN1865MUMNP2011A(String), US20110319037A1(String), WO2010148615A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20110319037A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101604980A(String), CN101604980B(String), EP2448128A1(String), EP2448128A4(String), IN1865MUMNP2011A(String), US20110319037A1(String), WO2010148615A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), CN101604980A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), CN101604980B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), EP2448128A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), EP2448128A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), IN1865MUMNP2011A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), US20110319037A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271656(Integer), WO2010148615A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20110319037A1(String), US20110319037A1(String), 1325088000(Integer), 271656(Integer), 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:51.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), SHAO, YONGPING(String), WU, YAN(String), LIANG, PANFENG(String), GUO, SHUAI(String), WEI, HONGPO(String), LUO, YIBAO(String), 中兴通讯股份有限公司(String), SHAO YONGPING(String), WU YAN(String), LIANG PANFENG(String), GUO SHUAI(String), WEI HONGPO(String), LUO YIBAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185970(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185970(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SHAO, YONGPING(String), SHAO YONGPING(String), 0(Integer), 1681976092(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: WU, YAN(String), WU YAN(String), 0(Integer), 1681976092(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIANG, PANFENG(String), LIANG PANFENG(String), 0(Integer), 1681976092(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUO, SHUAI(String), GUO SHUAI(String), 0(Integer), 1681976092(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: WEI, HONGPO(String), WEI HONGPO(String), 0(Integer), 1681976092(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LUO, YIBAO(String), LUO YIBAO(String), 0(Integer), 1681976092(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185970(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75846(Integer), 2(Integer), 185970(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75847(Integer), 2(Integer), 185970(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75848(Integer), 2(Integer), 185970(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75849(Integer), 2(Integer), 185970(Integer), 3(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75850(Integer), 2(Integer), 185970(Integer), 4(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75851(Integer), 2(Integer), 185970(Integer), 5(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.604 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.605 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75846(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.658 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185970(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:52.901 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.245 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal for information security and information security method of mobile terminal(String), 用于信息安全的移动终端及移动终端的信息安全方法(String), US20100299757A1(String), A mobile terminal to secure information stored therein is provided. The mobile terminal may perform an algorithm to perform information security without remote control. The mobile terminal may detect a characteristic behavior pattern of a user of the mobile terminal, compare the characteristic behavior pattern with a behavior pattern of a current user, and thereby may determine whether a current user is an authorized user. Also, the mobile terminal may perform processing to protect data stored in the mobile terminal based on a result of the determination.(String), 提供了一种用于保护其中存储的信息的移动终端。 移动终端可以在没有远程控制的情况下执行算法来执行信息安全。 移动终端可以检测移动终端用户的特征行为模式,将特征行为模式与当前用户的行为模式进行比较,从而可以确定当前用户是否为授权用户。 此外,移动终端可以基于确定的结果来执行处理以保护存储在移动终端中的数据。(String), US12/706023(String), 1266249600(Integer), US20100299757A1(String), 1290614400(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030129964A1 | US20030185361A1 | US20040085909A1 | US20050262563A1 | US20060094401A1 | US20070236330A1 | US20080172715A1 | US20080189776A1 | US20090247122A1 | US20110016534A1 | US20110107421A1 | US7924989B1 | US8145561B1 | US8351408B2 | US8423785B2(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185971(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.431 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\47fb9950e4164621994ad383dcb1e732.png(String), 185971(Integer), 47fb9950e4164621994ad383dcb1e732.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal for information security and information security method of mobile terminal(String), 用于信息安全的移动终端及移动终端的信息安全方法(String), US20100299757A1(String), A mobile terminal to secure information stored therein is provided. The mobile terminal may perform an algorithm to perform information security without remote control. The mobile terminal may detect a characteristic behavior pattern of a user of the mobile terminal, compare the characteristic behavior pattern with a behavior pattern of a current user, and thereby may determine whether a current user is an authorized user. Also, the mobile terminal may perform processing to protect data stored in the mobile terminal based on a result of the determination.(String), 提供了一种用于保护其中存储的信息的移动终端。 移动终端可以在没有远程控制的情况下执行算法来执行信息安全。 移动终端可以检测移动终端用户的特征行为模式,将特征行为模式与当前用户的行为模式进行比较,从而可以确定当前用户是否为授权用户。 此外,移动终端可以基于确定的结果来执行处理以保护存储在移动终端中的数据。(String), US12/706023(String), 1266249600(Integer), US20100299757A1(String), 1290614400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030129964A1 | US20030185361A1 | US20040085909A1 | US20050262563A1 | US20060094401A1 | US20070236330A1 | US20080172715A1 | US20080189776A1 | US20090247122A1 | US20110016534A1 | US20110107421A1 | US7924989B1 | US8145561B1 | US8351408B2 | US8423785B2(String), \20230420\47fb9950e4164621994ad383dcb1e732.png(String), 15(Integer), 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.519 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 1. An information security method in a mobile terminal, the information security method comprising:collecting data associated with a characteristic behavior pattern of a user of the mobile terminal;comparing the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period; andperforming processing to protect data stored in the mobile terminal based on a result of the comparison.(String), 1.一种移动终端中的信息安全方法,信息安全方法包括:收集与移动终端用户的特征行为模式相关联的数据;将特征行为模式与用户针对移动终端的行为模式进行比较,该行为模式是在特定时间段内被监控的;和基于比较的结果执行保护存储在移动终端中的数据的处理。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 2. The information security method of claim 1, wherein the performing comprises:hiding or deleting the data stored in the mobile terminal.(String), 2.如权利要求1所述的信息安全方法,其中表演包括:隐藏或删除移动终端中存储的数据。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 3. The information security method of claim 1, wherein the performing comprises:transmitting a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal.(String), 3.如权利要求1所述的信息安全方法,其中表演包括:向移动终端外部发送与移动终端的当前状态或当前位置相关联的通知消息。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 4. The information security method of claim 1, wherein the collecting collects the data associated with the characteristic behavior pattern of the user to update the characteristic behavior pattern.(String), 4.如权利要求1所述的信息安全方法,其中收集收集与用户的特征行为模式相关联的数据,以更新特征行为模式。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 5. The information security method of claim 1, further comprising:detecting the characteristic behavior pattern of the user based on the collected data.(String), 5.如权利要求1所述的信息安全方法,还包括:根据收集到的数据检测用户的特征行为模式。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 6. The information security method of claim 1, further comprising:monitoring the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period.(String), 6.如权利要求1所述的信息安全方法,还包括:实时监控移动终端,检测用户在特定时间段内针对移动终端的行为模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 7. The information security method of claim 1, wherein the comparing compares a value corresponding to the characteristic behavior pattern of the user with a value corresponding to the behavior pattern of the user to compare the characteristic behavior pattern with the behavior pattern of the user.(String), 7.如权利要求1所述的信息安全方法,其中比较是将用户的特征行为模式对应的值与用户的行为模式对应的值进行比较,以将特征行为模式与用户的行为模式进行比较。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 8. The information security method of claim 1, wherein the performing performs processing to protect data, which is requested to be protected in advance, from among the data stored in the mobile terminal.(String), 8.如权利要求1所述的信息安全方法,其中执行部执行处理以保护移动终端中存储的数据中预先请求保护的数据。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 9. The information security method of claim 1, wherein the characteristic behavior pattern of the user includes a characteristic usage pattern of the user with respect to the mobile terminal or a characteristic change pattern of an environment of the mobile terminal.(String), 9.如权利要求1所述的信息安全方法,其中用户的特征行为模式包括用户对移动终端的特征使用模式或移动终端环境的特征变化模式。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 10. The information security method of claim 1, wherein the characteristic behavior pattern of the user includes a characteristic usage pattern of the user with respect to the mobile terminal, and the characteristic usage pattern is detected based on at least one of details of calls of the user, a history of access to the Internet, a history of sending and/or receiving a text message, keystroke information, and a history of application uses.(String), 10.如权利要求1所述的信息安全方法,其中用户特征行为模式包括用户对移动终端的特征使用模式,特征使用模式是基于用户通话详情、上网历史中的至少一项检测的,发送和/或接收文本消息的历史记录、击键信息以及应用程序使用的历史记录。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 11. The information security method of claim 1, wherein the characteristic behavior pattern of the user includes a characteristic change pattern of an environment of the mobile terminal, and the characteristic change pattern is detected based on at least one of a moving route of the mobile terminal, information about the environment of the mobile terminal, and biological information of the user.(String), 11.如权利要求1所述的信息安全方法,其中用户的特征行为模式包括移动终端环境的特征变化模式,该特征变化模式是基于移动终端的移动路线、移动终端的环境信息中的至少一种检测的,和用户的生物信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 12. A computer-readable storage medium to store a program to implement an information security method in a mobile terminal, comprising instructions causing a computer to:collect data associated with a characteristic behavior pattern of a user of the mobile terminal;compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period; andperform processing to protect data stored in the mobile terminal based on a result of the comparison.(String), 12.一种计算机可读存储介质,用于存储在移动终端中实现信息安全方法的程序,包括导致计算机执行以下操作的指令:收集与移动终端用户的特征行为模式相关联的数据;将特征行为模式与用户针对移动终端的行为模式进行比较,该行为模式是在特定时间段内被监控的;和基于比较的结果执行保护存储在移动终端中的数据的处理。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 13. A mobile terminal to secure information stored therein, the mobile terminal comprising:a database to collect data associated with a characteristic behavior pattern of a user of the mobile terminal;a monitoring unit to detect the characteristic behavior pattern of the user using the database;a pattern comparison/reasoning unit to compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period; anda post-processing unit to perform processing to protect data stored in the mobile terminal based on a result of the comparison.(String), 13.一种用于保护存储在其中的信息的移动终端,该移动终端包括:数据库,用于收集与移动终端用户的特征行为模式相关联的数据;监测单元使用数据库检测用户的特征行为模式;模式比较/推理单元,将特征行为模式与用户针对移动终端的行为模式进行比较,该行为模式在特定时间段内被监控;和后处理单元基于比较的结果执行处理以保护存储在移动终端中的数据。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.557 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 14. The mobile terminal of claim 13, wherein the post-processing unit comprises at least one of a data management unit to hide or delete the data stored in the mobile terminal, and an urgent communication unit to transmit a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal.(String), 14.如权利要求13所述的移动终端,其中后处理单元包括隐藏或删除存储在移动终端中的数据的数据管理单元和发送与移动终端的当前状态或当前位置相关联的通知消息的紧急通信单元中的至少一个,到移动终端的外部。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.557 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185971(Integer), 15. The mobile terminal of claim 13, wherein the monitoring unit monitors the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period.(String), 15.如权利要求13所述的移动终端,其中监控单元实时监控移动终端,检测用户在特定时间段内针对移动终端的行为模式。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.843 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.844 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185971(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean Patent Application No. 10-2009-0044372, filed on May 21, 2009, in the Korean Intellectual Property Office, the entire disclosure of which is incorporated herein by reference for all purposes. BACKGROUND [0002]1. Field [0003]The following description relates to a technology to protect information stored in a terminal, and more particularly, to a technology to protect information stored in a mobile terminal in the event of an emergency such as loss or theft of the mobile terminal. [0004]2. Description of the Related Art [0005]Currently, various mobile terminals such as a cellular phone, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), and the like are widely used. A user may store various types of data or information in a mobile terminal. For example, a user may store photos, music files, data of a telephone book, text messages, etc., in a cellular phone. [0006]When a user loses the mobile terminal or has it stolen, the user's privacy may be compromised if confidential information was stored thereon. Furthermore, where information stored in a mobile terminal is used by a company or a government employee, a significant amount of damage may be caused if the otherwise secure information is available to an unauthorized user. [0007]In response to this issue, a variety of methods to protect information stored in a mobile terminal have been attempted. For example, security technologies include functions to activate a mobile terminal only when a password is input, technologies to remotely control a lost or stolen mobile terminal to protect information stored in the mobile terminal, etc. However, a mobile terminal having the above technologies may be operated manually and by an unauthorized user if the unauthorized user has access to the true mobile terminal owner's password. Accordingly, such technologies may not effectively protect information stored in a mobile terminal where a user does not know that the mobile terminal has been lost or stolen. SUMMARY [0008]In one general aspect, there is provided an information security method in a mobile terminal, the information security method includes collecting data associated with a characteristic behavior pattern of a user of the mobile terminal, comparing the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period, and performing processing to protect data stored in the mobile terminal based on a result of the comparison. [0009]The performing may include hiding or deleting the data stored in the mobile terminal, or transmitting a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal. [0010]The collecting may collect the data associated with the characteristic behavior pattern of the user to update the characteristic behavior pattern. [0011]The information security method may further include detecting the characteristic behavior pattern of the user based on the collected data. [0012]The information security method may further include monitoring the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period. [0013]The comparing may compare a value corresponding to the characteristic behavior pattern of the user with a value corresponding to the behavior pattern of the user to compare the characteristic behavior pattern with the behavior pattern of the user. [0014]The performing may perform processing to protect data, which is requested to be protected in advance, from among the data stored in the mobile terminal. [0015]The characteristic behavior pattern of the user may include a characteristic usage pattern of the user with respect to the mobile terminal or a characteristic environmental change pattern around the mobile terminal. [0016]The characteristic behavior pattern of the user may include a characteristic usage pattern of the user with respect to the mobile terminal, and the characteristic usage pattern may be detected based on details of calls of the user, a history of access to the Internet, a history of sending/receiving a text message, keystroke information, and a history of application uses. [0017]The characteristic behavior pattern of the user includes a characteristic environmental pattern of the user with respect to the mobile terminal, and the characteristic environmental change pattern may be detected based on at least one of a moving route of the mobile terminal, information about the environment of the mobile terminal, and biological information of the user. [0018]In another general aspect, there is provided a computer-readable storage medium to store a program to implement an information security method in a mobile terminal, comprising instructions causing a computer to collect data associated with a characteristic behavior pattern of a user of the mobile terminal, compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period, and perform processing to protect data stored in the mobile terminal based on a result of the comparison. [0019]In another general aspect, there is provided a mobile terminal to secure information stored therein, the mobile terminal includes a database to collect data associated with a characteristic behavior pattern of a user of the mobile terminal, a monitoring unit to detect the characteristic behavior pattern of the user using the database, a pattern comparison/reasoning unit to compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal, the behavior pattern being monitored in a particular time period, and a post-processing unit to perform processing to protect data stored in the mobile terminal based on a result of the comparison. [0020]The post-processing unit may include at least one of a data management unit to hide or delete the data stored in the mobile terminal, and an urgent communication unit to transmit a notification message, associated with a current state or a current location of the mobile terminal, to an outside of the mobile terminal. [0021]The monitoring unit may monitor the mobile terminal in real time to detect the behavior pattern of the user with respect to the mobile terminal, the behavior pattern of the user being monitored in the particular time period. [0022]Other features and aspects will be apparent from the following detailed description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0023]FIG. 1 is a diagram illustrating examples of a mobile terminal and various types of data stored in the mobile terminal. [0024]FIG. 2 is a diagram illustrating an example of a mobile terminal to detect a characteristic behavior pattern of a user and to check whether a current user is an authorized user using the detected characteristic behavior pattern in real time. [0025]FIG. 3 is a flowchart illustrating an example of an information security method. [0026]FIG. 4 is a diagram illustrating an example of data used during detection of a characteristic behavior pattern. [0027]FIG. 5 is a block diagram illustrating a configuration of an example of a mobile terminal. [0028]Throughout the drawings and the detailed description, unless otherwise described, the same drawing reference numerals will be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience. DETAILED DESCRIPTION [0029]The following detailed description is provided to assist the reader in gaining a comprehensive understanding of the media, apparatuses, methods and/or systems described herein. Accordingly, various changes, modifications, and equivalents of the systems, methods, apparatuses and/or media described herein will be suggested to those of ordinary skill in the art. Also, descriptions of well-known functions and constructions may be omitted for increased clarity and conciseness. [0030]FIG. 1 illustrates examples of a mobile terminal and various types of data stored in the mobile terminal. [0031]Referring to FIG. 1, various types of data may be stored in the mobile terminal, which may include various types of devices such as a cellular phone, a notebook computer (i.e. laptop), and the like. For example, as illustrated in FIG. 1, private information such as text messages, photo and video files, phone book, and the like, may be stored in the cellular phone. Also, emails, various documents, photos, and the like may be stored in the notebook computer. [0032]If the information stored in the mobile terminal is easily revealed and unsecure, a user's private information may be compromised thereby resulting in potentially substantial financial damage. In particular, if the user's mobile terminal is stolen, the user loses control the mobile terminal and all of the information stored thereupon. Furthermore, conventional methods of password-protecting mobile terminals may be difficult, inconvenient, and cumbersome. [0033]A user's mobile terminal usage behavior such as calling, sending and/or receiving text messages, movement, and application uses, may have a particular pattern. For example, the user of the mobile terminal generally moves along a particular moving route, talks on the mobile terminal with a particular caller and a particular receiver, and uses particular applications from among a plurality of applications installed in the mobile terminal. A characteristic behavior pattern of the user may be detected from the above-described behavior patterns of the user. [0034]Accordingly, the mobile terminal may actively ascertain a loss or theft of the mobile terminal using the detected user's characteristic behavior pattern, without remote control. For example, where a behavior of a current user is significantly different from the characteristic behavior pattern of the user, the mobile terminal may determine that the current user is an unauthorized user, and recognize that the mobile terminal is lost or stolen. An operation of actively and intelligently recognizing the loss or theft is described in detail below. [0035]FIG. 2 illustrates an example of a mobile terminal 210 to detect a characteristic behavior pattern of a user 220 and to check whether a current user is an authorized user using the detected characteristic behavior pattern in real time. [0036]Referring to FIG. 2, the mobile terminal 210 may recognize the characteristic behavior pattern of the user 220 from among various behaviors of the user 220. Accordingly, the characteristic behavior pattern of the user 220 may be classified into a characteristic usage pattern of the user 220 and a characteristic change pattern of an environment of the mobile terminal 210. [0037]The characteristic behavior pattern of the user 220 may be detected based on details regarding calls the user 220 has made and/or received, a history of access to the Internet, a history of sending and/or receiving text messages, keystroke information, and a history of application uses. The details of the calls of the user 220 may include information about a caller, information about a receiver, a time of making the calls, a time of receiving the calls, and a call duration. The history of sending and/or receiving the text messages may include information about a caller, information about a receiver, a size of the text message, a time of sending, a time of receiving, and the like. Also, the keystroke information of the user 220 may include information about a strength and/or speed of the manner in which keys were input. The history of application uses may include information about a type and/or time of use of a particular application which is installed in the mobile terminal 210. [0038]Also, the characteristic change pattern of the environment of the mobile terminal 210 may be influenced by external factors. That is, the characteristic change pattern of the environment of the mobile terminal 210 may be detected based on at least one of a moving route of the mobile terminal 210, information about the environment of the mobile terminal 210, and biological information of the user 220. More specifically, the information about the environment may include a brightness of a location of the mobile terminal 210, a humidity level of the location of the mobile terminal 210, a noise level of the location of the mobile terminal 210, etc., and the biological information may include a body temperature of the user, etc. [0039]The mobile terminal 210 may check whether the current user is the authorized user 220 in real time, after detecting the characteristic behavior pattern of the user 220 from the behaviors of the user 220. That is, the mobile terminal 210 may determine whether a behavior pattern, detected from the behavior of the current user, is similar to the characteristic behavior pattern of the user 220, and thereby may check whether the current user is the authorized user 220. As a similarity between the detected behavior pattern of the current user and the characteristic behavior pattern of the user 220 decreases, a probability that the current user may be an unauthorized user increases. [0040]Where the current user is an unauthorized user, the mobile terminal 210 may actively hide or delete data in order to protect the mobile terminal 210's true owner (i.e., the user 220 as illustrated in FIG. 2). In this instance, the data actively hidden or deleted may be set by the user 220 in advance. [0041]Also, the mobile terminal 210 may report the loss or theft of the mobile terminal 210 and transmit a notification message to a location outside of the mobile terminal 210, such as a serving base station. The notification message may include a current location of the mobile terminal 210. [0042]FIG. 3 illustrates an example of an information security method. [0043]The information security method may be actively and intelligently performed. [0044]Referring to FIG. 3, at 310, the information security method may identify data, which is requested to be protected by a user, from among data stored in a mobile terminal. In this instance, the user may request data associated with privacy, valuable data, and the like, to be protected in advance. [0045]At 320, the information security method may set an operation mode corresponding to a loss or theft of the mobile terminal according to a user setting. For example, if the mobile terminal is lost or stolen, the user may desire a mode of hiding or deleting the data to be protected, and select a mode of transmitting a notification message. [0046]At 330, the information security method may collect data associated with a characteristic behavior pattern of the user of the mobile terminal. In this instance, the mobile terminal may continuously collect details of calls of the user, a history of access to the Internet, a history of sending and/or receiving text messages, keystroke information, and a history of application uses. Accordingly, the application may be installed in the mobile terminal. Also, the mobile terminal may collect at least one of information about a moving route of the mobile terminal, information about an environment of the mobile terminal, and biological information of the user. The information about the environment may include a brightness of a location of the mobile terminal, a humidity level of the location of the mobile terminal, a noise level of the location of the mobile terminal, and, and the biological information may include a body temperature of the user, etc. [0047]At 340, the information security method may detect the characteristic behavior pattern of the user based on the collected data. In this instance, a variety of well-known data analysis schemes may be applied, and the characteristic behavior pattern may be expressed numerically or in a table or a graph. [0048]At 350, the information security method may collect data to detect a current behavior pattern of a user of the mobile terminal in real time. [0049]At 360, the information security method may compare the characteristic behavior pattern, detected at 340, with the behavior pattern, detected at 350. [0050]At 370, the information security method may determine whether the current user is an authorized user or whether the mobile terminal is lost or stolen, based on a result of the comparison at 360. [0051]That is, where the behavior pattern, detected at 350, is significantly different from the characteristic behavior pattern, detected at 340, the information security method may determine that the current user is an unauthorized user. Conversely, where the behavior pattern, detected at 350, is significantly similar to the characteristic behavior pattern, detected at 340, the information security method may determine that the current user is an authorized user. [0052]Where the current user is in fact the authorized user, the information security method may return to 330. However, where the current user is the unauthorized user, the information security method may perform at least one of transmitting data (at 382) and deleting or hiding data (at 381). [0053]At 381, the information security method may hide or delete the data to be protected. At 382, the information security method may transmit the notification message to an outside location of the mobile terminal. [0054]FIG. 4 illustrates an example of data used during detection of a characteristic behavior pattern. [0055]The examples of data to be protected and an operation mode are illustrated in FIG. 4. That is, a user may determine an image file, received from a girlfriend (for example), as the data to be protected. Also, the data to be protected may be set by the user, and the user may set a mode of hiding the data to be protected and a mode of transmitting a notification message in an event of loss or theft of the mobile terminal, as the operation mode. [0056]The user may behave according to the characteristic behavior pattern as illustrated in FIG. 4. That is, the user may send and/or receive an image file from and/or to the girlfriend between 12:00 and 13:00, and perform a video call with the girlfriend between 23:00 and 01:00. Also, the user usually moves along a route of home—school—home on weekdays, and along a route of home—training center—girlfriend's house—home on weekends. The above-described behaviors may be automatically monitored by the mobile terminal, and the mobile terminal may detect the characteristic behavior pattern using data associated with the collected behaviors of the user. Accordingly, the characteristic behavior pattern may be expressed in various ways such as a table, a numerical value, a graph, and the like. [0057]For example, it may be assumed that the user lost the mobile terminal in a bus while going to school on Wednesday morning, and the user does not realize it. Accordingly, the mobile terminal lost on the bus may continuously monitor a behavior pattern of a user of the mobile terminal. [0058]Hence, the mobile terminal moves along a route of the bus, and the user does not send and/or receive an image file between 12:00 and 13:00, and a monitored noise around the mobile terminal may be higher than usual. [0059]In this instance, the mobile terminal may determine that the current situation around the mobile terminal is different from typical patterns by means of the characteristic behavior pattern based on the collected data. In particular, the mobile terminal may compare a value corresponding to the characteristic behavior pattern with a value corresponding to the current situation around the mobile terminal, and apply a result of the comparison to a particular rule, and thereby may determine that the current situation around the mobile terminal is different from the characteristic behavior pattern. [0060]As a result, the mobile terminal may hide the image file received from the girlfriend, which is the data to be protected, and transmit the notification message. Accordingly, although the user may not recognize the loss or theft of the mobile terminal, the data will be protected. Also, the data may be efficiently protected even when a communication of the mobile terminal is unavailable, since remote control is not required. [0061]FIG. 5 illustrates a configuration of an example of a mobile terminal. [0062]Referring to FIG. 5, the mobile terminal includes a user setting management unit 510, a database 520, a pattern comparison/reasoning unit 530, a monitoring unit 540, an internal sensor 550, an external sensor 560, and a post-processing unit 570. [0063]The user setting management unit 510 may manage a user setting with respect to data to be protected, and an operation mode if the mobile terminal is lost or stolen. The data to be protected may be requested by a user. [0064]The database 520 may store the characteristic behavior pattern of the user based on the collected data associated with a characteristic behavior pattern of a user of the mobile terminal. This behavior pattern is provided from the monitoring unit 540. In this instance, the database 520 may update the characteristic behavior pattern. [0065]Also, the pattern comparison/reasoning unit 530 may compare the characteristic behavior pattern with a behavior pattern of the user with respect to the mobile terminal. The behavior pattern may be monitored in a particular time period. Also, the pattern comparison/reasoning unit 530 may apply a result of the comparison to a particular rule, and thereby may identify a current state of the mobile terminal. [0066]Also, the monitoring unit 540 may monitor data, provided from the internal sensor 550 and the external sensor 560, in real time and detect the behavior pattern of the user with respect to the mobile terminal based on the data. Also, the monitoring unit 540 may provide the detected behavior pattern to the database 520 and the pattern comparison/reasoning unit 530. Accordingly, the internal sensor 550 may provide, to the monitoring unit 540, details of calls of the user, a history of access to the Internet, a history of sending/receiving text messages, keystroke information, and a history of application uses in real time. Also, the external sensor 560 may provide, to the monitoring unit 540, a moving route of the mobile terminal, information about an environment of the mobile terminal, and biological information of the user. [0067]The post-processing unit 570 includes a data management unit 571 and an urgent communication unit 572. In this instance, the data management unit 571 may hide or delete the data stored in the mobile terminal based on the user setting, and the urgent communication unit 572 may transmit a notification message, associated with a current state or a current location of the mobile terminal, to a location outside of the mobile terminal. [0068]Since the descriptions described with reference to FIGS. 1 through 4 may be applied to the above-described units illustrated in FIG. 5, further detailed descriptions will be omitted herein. [0069]The processes, functions, methods and/or software described above may be recorded, stored, or fixed in one or more computer-readable storage media that includes program instructions to be implemented by a computer to cause a processor to execute or perform the program instructions. The media may also include, alone or in combination with the program instructions, data files, data structures, and the like. The media and program instructions may be those specially designed and constructed, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable media include magnetic media, such as hard disks, floppy disks, and magnetic tape; optical media such as CD ROM disks and DVDs; magneto-optical media, such as optical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory (ROM), random access memory (RAM), flash memory, and the like. Examples of program instructions include machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter. The described hardware devices may be configured to act as one or more software modules in order to perform the operations and methods described above, or vice versa. In addition, a computer-readable storage medium may be distributed among computer systems connected through a network and computer-readable codes or program instructions may be stored and executed in a decentralized manner. [0070]As described above with reference to the figures, a mobile terminal may actively or intelligently determine whether the mobile terminal is lost or stolen, or whether a current user is an authorized user, and thereby may efficiently protect information, stored in the mobile terminal, even when the user does not recognize the loss or theft. [0071]Also as described above with reference to the figures, a mobile terminal may compare a characteristic behavior pattern of a user with a current behavior pattern, and thereby may accurately determine whether the mobile terminal is lost or stolen or whether a current user is an authorized user. [0072]Further as described above with reference to the figures, a mobile terminal may actively or intelligently determine whether the mobile terminal is lost or stolen, or whether a current user is an authorized user, and thereby may economically protect information, stored in the mobile terminal, without a separate hardware for remote control. [0073]A number of examples have been described above. Nevertheless, it will be understood that various modifications may be made. For example, suitable results may be achieved if the described techniques are performed in a different order and/or if components in a described system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components or their equivalents. Accordingly, other implementations are within the scope of the following claims.(String), 相关申请的交叉引用 [0001] 此申请根据 35 U.S.C. 2009 年 5 月 21 日向韩国知识产权局提交的第 10-2009-0044372 号韩国专利申请的§119(a),其全部公开内容通过引用并入本文用于所有目的。 背景 [0002] 1. 领域 [0003] 以下描述涉及保护存储在终端中的信息的技术,更具体地,涉及在紧急情况例如移动终端丢失或被盗的情况下保护存储在移动终端中的信息的技术。 [0004] 2.相关技术的描述 [0005] 目前,各种移动终端如蜂窝电话、个人数字助理(PDA)、便携式多媒体播放器(PMP)等被广泛使用。 用户可以在移动终端中存储各种类型的数据或信息。 例如,用户可以将照片、音乐文件、电话簿数据、文本消息等存储在蜂窝电话中。 [0006] 当用户丢失或被盗移动终端时,如果在其上存储机密信息,用户的隐私可能会受到损害。 此外,在存储在移动终端中的信息被公司或政府雇员使用的情况下,如果未经授权的用户可以使用原本安全的信息,则可能造成大量损害。 [0007] 针对这个问题,已经尝试了多种方法来保护存储在移动终端中的信息。 例如,安全技术包括仅在输入密码时激活移动终端的功能,远程控制丢失或被盗的移动终端以保护移动终端中存储的信息的技术等。但是,具有上述技术的移动终端可以 如果未经授权的用户可以访问真正的移动终端所有者的密码,则由未经授权的用户手动操作。 因此,在用户不知道移动终端丢失或被盗的情况下,这样的技术可能无法有效地保护存储在移动终端中的信息。 概括 [0008] 在一个一般方面,提供了一种移动终端中的信息安全方法,该信息安全方法包括收集与移动终端的用户的特征行为模式相关联的数据,将特征行为模式与用户的行为模式进行比较 对于移动终端,在特定时间段内监测行为模式,并根据比较结果进行处理以保护移动终端中存储的数据。 [0009] 该执行可以包括隐藏或删除存储在移动终端中的数据,或者将与移动终端的当前状态或当前位置相关联的通知消息发送到移动终端的外部。 [0010] 收集可以收集与用户的特征行为模式相关联的数据以更新特征行为模式。 [0011] 信息安全方法还可以包括基于收集的数据检测用户的特征行为模式。 [0012] 所述信息安全方法还可以包括对所述移动终端进行实时监控,以检测用户对所述移动终端的行为模式,所述用户的行为模式在特定时间段内被监测。 [0013] 比较可以将与用户的特征行为模式对应的值与与用户的行为模式对应的值进行比较,以将特征行为模式与用户的行为模式进行比较。 [0014] 执行可以执行处理以保护存储在移动终端中的数据之中的被预先请求保护的数据。 [0015] 用户的特征行为模式可以包括用户对移动终端的特征使用模式或移动终端周围的特征环境变化模式。 [0016]用户的特征行为模式可以包括用户对移动终端的特征使用模式,该特征使用模式可以基于用户的通话细节、上网历史、上网历史等来检测。 发送/接收文本消息、击键信息和应用程序使用历史。 [0017] 用户的特征行为模式包括用户相对于移动终端的特征环境模式,可以基于移动终端的移动路线、环境信息中的至少一种来检测特征环境变化模式。 移动终端,以及用户的生物信息。 [0018] 在另一个一般方面,提供了一种计算机可读存储介质,用于存储在移动终端中实现信息安全方法的程序,包括使计算机收集与移动终端用户的特征行为模式相关联的数据的指令 ,将特征行为模式与用户对移动终端的行为模式进行比较,该行为模式在特定时间段内被监控,并根据比较结果进行处理以保护移动终端中存储的数据。 [0019] 在另一个一般方面,提供了一种用于保护其中存储的信息的移动终端,该移动终端包括用于收集与该移动终端的用户的特征行为模式相关联的数据的数据库、用于检测用户的特征行为模式的监控单元。 用户使用数据库,模式比较/推理单元将特征行为模式与用户相对于移动终端的行为模式进行比较,在特定时间段内被监控的行为模式,以及后处理单元,用于 根据比较结果,进行处理以保护移动终端中存储的数据。 [0020] 后处理单元可以包括至少一个数据管理单元,用于隐藏或删除存储在移动终端中的数据,以及紧急通信单元,用于发送与移动设备的当前状态或当前位置相关联的通知消息。 终端,到移动终端的外部。 [0021] 监控单元可以对移动终端进行实时监控,以检测用户对移动终端的行为模式,该用户的行为模式在特定时间段内被监控。 [0022] 从以下详细描述、附图和权利要求中,其他特征和方面将是显而易见的。 附图的简要说明 [0023] 如图。 附图说明图1是图示移动终端和存储在移动终端中的各种类型的数据的示例的图。 [0024] 如图。 图2是示出移动终端检测用户的特征行为模式并使用检测到的特征行为模式实时检查当前用户是否是授权用户的示例的图。 [0025] 如图。 图3是表示信息安全方法的一个例子的流程图。 [0026] 如图。 图4是表示特征行为模式的检测时使用的数据的一例的图。 [0027] 如图。 图5是图示移动终端的示例的配置的框图。 [0028] 在整个附图和详细描述中,除非另有说明,否则相同的附图标记将被理解为指代相同的元件、特征和结构。 为了清楚、说明和方便起见,这些元素的相对大小和描述可能会被夸大。 详细说明 [0029]提供以下详细描述以帮助读者获得对本文描述的媒体、装置、方法和/或系统的全面理解。 因此,本文所述的系统、方法、装置和/或媒体的各种改变、修改和等效物将被建议给本领域普通技术人员。 此外,为了更清楚和简明,可以省略对众所周知的功能和结构的描述。 [0030] 如图。 图1图示了移动终端和存储在移动终端中的各种类型的数据的示例。 [0031] 参考图。 参照图1,移动终端中可以存储各种类型的数据,移动终端可以包括各种类型的设备,例如蜂窝电话、笔记本电脑(即膝上型电脑)等。 例如,如图所示。 如图1所示,诸如文本消息、照片和视频文件、电话簿等的私人信息可以存储在蜂窝电话中。 此外,电子邮件、各种文档、照片等可以存储在笔记本计算机中。 [0032] 如果存储在移动终端中的信息容易泄露且不安全,则用户的私人信息可能会受到损害,从而导致潜在的重大经济损失。 特别是,如果用户的移动终端被盗,用户将失去对移动终端的控制以及其上存储的所有信息。 此外,传统的密码保护移动终端的方法可能是困难的、不方便的和麻烦的。 [0033] 用户的移动终端使用行为,例如呼叫、发送和/或接收文本消息、移动和应用程序使用,可能具有特定的模式。 例如,移动终端的用户通常沿着特定的移动路线移动,在移动终端上与特定的呼叫者和特定的接收者通话,并使用安装在移动终端中的多个应用程序中的特定应用程序。 可以从上述用户的行为模式中检测出用户的特征行为模式。 [0034] 因此,移动终端可以使用检测到的用户的特征行为模式来主动确定移动终端的丢失或被盗,而无需远程控制。 例如,在当前用户的行为与用户的特征行为模式显着不同的情况下,移动终端可以确定当前用户是未经授权的用户,并识别出移动终端丢失或被盗。 下面详细介绍主动智能识别丢失或被盗的操作。 [0035] 如图。 图2图示了移动终端的示例 210 检测用户的特征行为模式 220 使用检测到的特征行为模式实时检查当前用户是否为授权用户。 [0036] 参考图。 2、移动端 210 可以识别用户的特征行为模式 220 从用户的各种行为中 220 . 相应地,用户的特征行为模式 220 可以分类为用户的特征使用模式 220 以及移动终端环境的特征变化模式 210 . [0037] 用户的特征行为模式 220 可以根据有关用户呼叫的详细信息进行检测 220 已制作和/或接收到互联网访问历史、发送和/或接收文本消息的历史、击键信息和应用程序使用历史。 用户通话详情 220 可以包括关于呼叫者的信息、关于接收者的信息、进行呼叫的时间、接收呼叫的时间和呼叫时长。 发送和/或接收文本消息的历史可以包括关于呼叫者的信息、关于接收者的信息、文本消息的大小、发送时间、接收时间等。 还有用户的按键信息 220“输入键”可以包括关于输入键的方式的强度和/或速度的信息。 应用程序使用历史可以包括关于安装在移动终端中的特定应用程序的类型和/或使用时间的信息 210 . [0038] 此外,移动终端环境的特征变化模式 210 可能会受到外部因素的影响。 即移动终端环境的特征变化模式 210 可以基于移动终端的移动路线中的至少一个来检测 210 , 移动终端的环境信息 210 ,以及用户的生物信息 220 . 更具体地,关于环境的信息可以包括移动终端的位置的亮度 210 , 移动终端所在位置的湿度等级 210 , 移动终端位置的噪声级 210 等,并且生物信息可以包括用户的体温等。 [0039] 移动终端 210 可以检查当前用户是否是授权用户 220 实时检测用户的特征行为模式后 220 从用户的行为 220 . 也就是移动终端 210 可以确定从当前用户的行为中检测到的行为模式是否与用户的特征行为模式相似 220 ,从而可以检查当前用户是否是授权用户 220 . 作为检测到的当前用户的行为模式与用户的特征行为模式之间的相似度 220 减少,当前用户可能是未授权用户的概率增加。 [0040] 当前用户为非法用户时,移动终端 210 可能会主动隐藏或删除数据以保护移动终端 210 的真正所有者(即用户 220 如图所示。 2)。 在这种情况下,主动隐藏或删除的数据可能由用户设置 220 提前。 [0041] 此外,移动终端 210 可报移动终端丢失或被盗 210 向移动终端外的位置发送通知消息 210 ,例如服务基站。 通知消息可以包括移动终端的当前位置 210 . [0042] 如图。 图3图示了信息安全方法的示例。 [0043] 可以主动智能地执行信息安全方法。 [0044] 参考图。 3、在 310 所述信息安全方法可以从存储在移动终端中的数据中识别出用户请求保护的数据。 在这种情况下,用户可以请求提前保护与隐私、有价值的数据等相关的数据。 [0045] 在 320 ,该信息安全方法可以根据用户设置设置与移动终端丢失或被盗对应的操作模式。 例如,如果移动终端丢失或被盗,用户可能希望隐藏或删除要保护的数据的模式,并选择发送通知消息的模式。 [0046] 在 330,该信息安全方法可以收集与移动终端用户的特征行为模式相关联的数据。 在这种情况下,移动终端可以不断地收集用户的通话细节、访问互联网的历史、发送和/或接收文本消息的历史、击键信息和应用程序使用的历史。 因此,应用程序可以安装在移动终端中。 此外,移动终端可以收集关于移动终端的移动路线的信息、关于移动终端的环境的信息和用户的生物信息中的至少一种。 关于环境的信息可以包括移动终端所在位置的亮度、移动终端所在位置的湿度水平、移动终端所在位置的噪声水平,并且,生物信息可以包括体温 用户等 [0047] 在 340 ,信息安全方法可以基于收集的数据检测用户的特征行为模式。 在这种情况下,可以应用各种众所周知的数据分析方案,并且可以用数字或表格或图形来表示特征行为模式。 [0048] 在 350 ,该信息安全方法可以收集数据以实时检测移动终端用户的当前行为模式。 [0049] 在 360 ,信息安全方法可以比较特征行为模式,在 340 ,与行为模式,检测到 350 . [0050] 在 370 ,信息安全方法可以根据在 360 . [0051] 也就是说,在哪里检测到行为模式 350 ,与特征行为模式显着不同,在 340 ,信息安全方法可以确定当前用户为非授权用户。 相反,在行为模式中,检测到 350 ,与特征行为模式显着相似,在 340 ,信息安全方法可以确定当前用户为授权用户。 [0052] 在当前用户实际上是授权用户的情况下,信息安全方法可能会返回到 330 . 然而,在当前用户是未授权用户的情况下,信息安全方法可以执行至少一种传输数据(在 382 )和删除或隐藏数据(在 381 )。 [0053] 在 381 ,信息安全方法可能会隐藏或删除要保护的数据。 在 382 ,信息安全方法可以将通知消息发送到移动终端的外部位置。 [0054] 如图。 图4图示了在检测特征行为模式期间使用的数据的示例。 [0055] 要保护的数据的示例和操作模式在图1中示出。 4、即用户可以将例如从女朋友处接收到的图像文件确定为要保护的数据。 另外,需要保护的数据可以由用户设置,用户可以设置隐藏需要保护的数据的方式和移动终端丢失或被盗时发送通知消息的方式,作为 操作模式。 [0056] 用户可以根据如图1所示的特征行为模式来行动。 4、即用户可以在12:00到13:00之间向女朋友发送和/或接收图像文件,并在23:00到01:00之间与女朋友进行视频通话。 此外,用户通常在工作日沿着家-学校-家的路线移动,而在周末沿着家-培训中心-女朋友家-家的路线移动。 上述行为可以由移动终端自动监测,并且移动终端可以使用与收集的用户行为相关联的数据来检测特征行为模式。 因此,可以以诸如表格、数值、图表等的各种方式来表达特征行为模式。 [0057]例如,可以假设用户在周三早上去上学时在公交车上丢失了移动终端,而用户没有意识到这一点。 因此,在公共汽车上丢失的移动终端可以持续监控移动终端用户的行为模式。 [0058] 因此,移动终端沿着公交车的路线移动,并且用户在12:00和13:00之间没有发送和/或接收图像文件,并且移动终端周围的监测到的噪声可能比平时高。 [0059] 在这种情况下,移动终端可以通过基于收集到的数据的特征行为模式来确定移动终端周围的当前情况不同于典型模式。 具体地,移动终端可以将对应于特征行为模式的值与对应于移动终端周围的当前情况的值进行比较,并将比较的结果应用于特定规则,从而可以确定周围的当前情况 移动终端不同于特征行为模式。 [0060] 结果,移动终端可以隐藏从女朋友接收到的图像文件,这是要保护的数据,并发送通知消息。 因此,虽然用户可能无法识别移动终端的丢失或被盗,但数据将受到保护。 此外,即使在移动终端的通信不可用时,也可以有效地保护数据,因为不需要远程控制。 [0061] 如图。 图5图示了移动终端的示例的配置。 [0062] 参考图。 5、移动终端包括用户设置管理单元 510 , 一个数据库 520 , 一个模式比较/推理单元 530 , 一个监控单元 540 , 一个内部传感器 550 , 一个外部传感器 560 , 和一个后处理单元 570 . [0063] 用户设置管理单元 510 可以管理关于要保护的数据的用户设置,以及移动终端丢失或被盗时的操作模式。 要保护的数据可以由用户请求。 [0064] 数据库 520 可以基于收集到的与移动终端的用户的特征行为模式相关联的数据来存储用户的特征行为模式。 此行为模式由监控单元提供 540 . 在这种情况下,数据库 520 可以更新特征行为模式。 [0065] 此外,模式比较/推理单元 530 可以将特征行为模式与用户对移动终端的行为模式进行比较。 可以在特定时间段内监控行为模式。 此外,模式比较/推理单元 530 可以将比较的结果应用到特定规则,从而可以识别移动终端的当前状态。 [0066] 此外,监控单元 540 可以监控从内部传感器提供的数据 550 和外部传感器 560 ,基于数据实时检测用户对移动终端的行为模式。 此外,监控单元 540 可以将检测到的行为模式提供给数据库 520 和模式比较/推理单元 530 . 因此,内部传感器 550 可以提供给监控单元 540 、用户通话详情、上网历史、收发短信历史、按键信息、应用程序使用历史实时。 此外,外部传感器 560 可以提供给监控单元 540 、移动终端的移动路线、移动终端的环境信息、用户的生物信息。 [0067] 后处理单元 570 包括一个数据管理单元 571 和一个紧急通信单元 572 . 在这种情况下,数据管理单元 571 可根据用户设置隐藏或删除移动终端中存储的数据,紧急通信单元 572可以将与移动终端的当前状态或当前位置相关联的通知消息发送到移动终端之外的位置。 [0068] 由于参照图1至图5描述的描述。 图1至图4的实施例可以应用于图1所示的上述单元。 参照图5,这里将省略进一步的详细描述。 [0069] 上述过程、功能、方法和/或软件可以被记录、存储或固定在一个或多个计算机可读存储介质中,该存储介质包括将由计算机实现以使处理器执行或执行程序指令的程序指令 . 媒体还可以单独或与程序指令、数据文件、数据结构等组合地包括。 媒体和程序指令可以是那些专门设计和构造的,或者它们可以是计算机软件领域的技术人员熟知和可用的那种。 计算机可读介质的示例包括磁介质,例如硬盘、软盘和磁带; 光媒体,如 CD ROM 盘和 DVD; 磁光介质,例如光盘; 以及专门用于存储和执行程序指令的硬件设备,例如只读存储器(ROM)、随机存取存储器(RAM)、闪存等。 程序指令的示例包括诸如由编译器产生的机器代码,以及包含可由计算机使用解释器执行的更高级别代码的文件。 所描述的硬件设备可以被配置为充当一个或多个软件模块以执行上述操作和方法,反之亦然。 此外,计算机可读存储介质可以分布在通过网络连接的计算机系统之间,并且计算机可读代码或程序指令可以以分散方式存储和执行。 [0070] 如上文结合附图所描述的,移动终端可以主动或智能地确定移动终端是否丢失或被盗,或者当前用户是否为授权用户,从而可以有效地保护存储在移动终端中的信息,甚至 当用户不承认丢失或被盗时。 [0071] 同样如上面参考附图所描述的,移动终端可以将用户的特征行为模式与当前行为模式进行比较,从而可以准确地确定移动终端是否丢失或被盗或者当前用户是否是授权用户 . [0072] 进一步如以上参考附图所述,移动终端可以主动或智能地确定移动终端是否丢失或被盗,或者当前用户是否为授权用户,从而可以经济地保护存储在移动终端中的信息, 无需单独的硬件进行远程控制。 [0073] 上面已经描述了许多示例。 然而,应当理解,可以进行各种修改。 例如,如果以不同的顺序执行所描述的技术和/或如果所描述的系统、架构、设备或电路中的组件以不同的方式组合和/或由其他组件替换或补充或 他们的等价物。 因此,其他实施方式在所附权利要求的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:53.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101541305B1(String), KR1020100125588A(String), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101541305B1(String), KR1020100125588A(String), US20100299757A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.070 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101541305B1(String), KR1020100125588A(String), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271657(Integer), KR101541305B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271657(Integer), KR1020100125588A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271657(Integer), US20100299757A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20100299757A1(String), US20100299757A1(String), 1290614400(Integer), 271657(Integer), 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), LEE, HO SUB(String), 三星电子株式会社(String), LEE HO SUB(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185971(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185971(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LEE, HO SUB(String), LEE HO SUB(String), 0(Integer), 1681976094(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185971(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75852(Integer), 2(Integer), 185971(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75852(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.641 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185971(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.833 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:54.834 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120231798A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and cell reselection method of mobile terminal(String), 移动终端及移动终端的小区重选方法(String), US20120231798A1(String), The present invention provides a cell reselection method of a mobile terminal. The method comprises the following steps: setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. The present invention further provides a mobile terminal. The present invention solves the problem that the mobile terminal, which is in the WCDMA/GSM dual mode and resides in the GSM cell, cannot reside in the WCDMA cell while the WCDMA network can be used actually, improves the capability and success rate of the reselection toward the WCDMA network of the mobile terminal, and enables the user to have more opportunities to enjoy rich and colourful 3G services.(String), 本发明提供一种移动终端的小区重选方法。 该方法包括以下步骤:设置移动终端从GSM小区到WCDMA小区的重选参数; 根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 本发明还提供一种移动终端。 本发明解决了WCDMA/GSM双模驻留在GSM小区中的移动终端不能驻留在WCDMA小区而WCDMA网络可以实际使用的问题,提高了移动终端的能力和成功率。 重新选择移动终端的WCDMA网络,让用户有更多机会享受丰富多彩的3G服务。(String), US13/510346(String), 1282579200(Integer), US20120231798A1(String), 1347465600(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 3(Integer), US20040082328A1 | US20080102847A1 | US20100056178A1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185972(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d0d26725698f4ba2b1cadb8736b6bbcd.png(String), 185972(Integer), d0d26725698f4ba2b1cadb8736b6bbcd.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and cell reselection method of mobile terminal(String), 移动终端及移动终端的小区重选方法(String), US20120231798A1(String), The present invention provides a cell reselection method of a mobile terminal. The method comprises the following steps: setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. The present invention further provides a mobile terminal. The present invention solves the problem that the mobile terminal, which is in the WCDMA/GSM dual mode and resides in the GSM cell, cannot reside in the WCDMA cell while the WCDMA network can be used actually, improves the capability and success rate of the reselection toward the WCDMA network of the mobile terminal, and enables the user to have more opportunities to enjoy rich and colourful 3G services.(String), 本发明提供一种移动终端的小区重选方法。 该方法包括以下步骤:设置移动终端从GSM小区到WCDMA小区的重选参数; 根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 本发明还提供一种移动终端。 本发明解决了WCDMA/GSM双模驻留在GSM小区中的移动终端不能驻留在WCDMA小区而WCDMA网络可以实际使用的问题,提高了移动终端的能力和成功率。 重新选择移动终端的WCDMA网络,让用户有更多机会享受丰富多彩的3G服务。(String), US13/510346(String), 1282579200(Integer), US20120231798A1(String), 1347465600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 3(Integer), US20040082328A1 | US20080102847A1 | US20100056178A1(String), \20230420\d0d26725698f4ba2b1cadb8736b6bbcd.png(String), 14(Integer), 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 1. A mobile terminal, comprising a setting module and a detecting module, whereinthe setting module is configured to set a reselection parameter of a mobile terminal from a Global System for Mobile Communications (GSM) cell to a Wideband Code Division Multiple Access (WCDMA) cell; andthe detecting module is configured to judge whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter.(String), 1.移动终端,包括设置模块和检测模块,其中设置模块,用于设置移动终端从GSM小区到WCDMA小区的重选参数;和检测模块,用于根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 2. The mobile terminal according to claim 1, wherein, the step that the setting module sets a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: the setting module sets a first threshold of Received Energy per Chip Divided by the Noise Spectral Density (Ec/No) of the mobile terminal on each code channel of a transmitter after spreading spectrum, and sets a second threshold of Received Signal Code Power (RSCP).(String), 2.根据权利要求1所述的移动终端,其中,设置模块设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:设置模块设置第一门限值为每个码片的接收能量除以移动终端的噪声频谱密度(Ec/No)终端在扩频后的发射机的每个码道上,并设置接收信号码功率(RSCP)的第二门限。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 3. The mobile terminal according to claim 2, wherein, the step that the detecting module judges whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter comprises:the detecting module measures the value of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum of the WCDMA cell, and the value of the RSCP of the mobile terminal, and initiates a reselection toward the WCDMA cell when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP is greater than or equal to the second threshold which situation lasts for a second preset time.(String), 3.根据权利要求2所述的移动终端,其中,检测模块根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选包括:检测模块测量WCDMA小区扩频后发射机各码道上移动终端的Ec/No值和移动终端的RSCP值,当满足时向WCDMA小区发起重选发射机扩频后各码道上的Ec/No测量值大于或等于第一门限,这种情况持续第一预设时间,RSCP测量值大于或等于第二阈值,该情况持续第二预设时间。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 4. The mobile terminal according to claim 2, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module sets the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and sets the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 4.根据权利要求2所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和RSCP的第二门限包括:设置模块设置第一门限大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,并将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 5. The mobile terminal according to claim 2, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module presets the first threshold and the second threshold during factory manufacture of the mobile terminal, and sets the first threshold and the second threshold as being modifiable.(String), 5.根据权利要求2所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和设置RSCP的第二门限包括:设置模块预先设置第一门限和第二门限在移动终端出厂时,将第一阈值和第二阈值设置为可修改。6、一种移动终端的小区重选方法,包括:设置移动终端从GSM小区到WCDMA小区的重选参数;和根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 6. A cell reselection method of a mobile terminal, comprising:setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; andjudging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter.(String), 7.根据权利要求6所述的移动终端的小区重选方法,其中,设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:设置移动终端在WCDMA小区扩频后的发射机各码道上的第一门限Ec/No,设置RSCP的第二个阈值。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 7. The cell reselection method of a mobile terminal according to claim 6, wherein,the step of setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: setting a first threshold of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum of the WCDMA cell, and setting a second threshold of RSCP.(String), 8.根据权利要求7所述的移动终端的小区重选方法,其中,基于WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选包括:移动终端测量WCDMA小区扩频后的发射机信道大于或等于第一门限,该情况持续第一预设时间,并且WCDMA小区的RSCP测量值大于或者等于第二阈值,该情况持续第二预设时间。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 8. The cell reselection method of a mobile terminal according to claim 7, wherein, the step of judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter comprises: initiating a reselection toward the WCDMA cell when the measured value of Ec/No on each code channel of the transmitter after spreading spectrum of the WCDMA cell, measured by the mobile terminal, is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP of the WCDMA cell is greater than or equal to the second threshold which situation lasts for a second preset time.(String), 9.根据权利要求7所述的移动终端的小区重选方法,其中,设置第一阈值和第二阈值的步骤包括:将第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 9. The cell reselection method of a mobile terminal according to claim 7, wherein, the step of setting the first threshold and the second threshold comprises: setting the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and setting the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 10.根据权利要求7所述的移动终端的小区重选方法,其中,第一阈值和第二阈值在移动终端出厂时预先设置,可以修改。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 10. The cell reselection method of a mobile terminal according to claim 7, wherein, the first threshold and the second threshold are preset during factory manufacture of the mobile terminal, and are modifiable.(String), 11.根据权利要求3所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和RSCP的第二门限包括:设置模块设置第一门限大于或等于−18dB且小于FDD_Qmin−FDD_Qmin13Offset,将第二阈值设置为大于等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 11. The mobile terminal according to claim 3, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module sets the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin13Offset, and sets the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 12.根据权利要求3所述的移动终端,其中,设置模块设置移动终端扩频后发射机各码道上的Ec/No的第一门限和设置RSCP的第二门限包括:设置模块预先设置第一门限和第二门限在移动终端出厂时,将第一阈值和第二阈值设置为可修改。(String), 1(Integer), 10(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 12. The mobile terminal according to claim 3, wherein, the step that the setting module sets the first threshold of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum and sets the second threshold of the RSCP comprises: the setting module presets the first threshold and the second threshold during factory manufacture of the mobile terminal, and sets the first threshold and the second threshold as being modifiable.(String), 13.根据权利要求8所述的移动终端的小区重选方法,其中,设置第一阈值和第二阈值的步骤包括:将第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 13. The cell reselection method of a mobile terminal according to claim 8, wherein, the step of setting the first threshold and the second threshold comprises: setting the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and setting the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold.(String), 14.根据权利要求8所述的移动终端的小区重选方法,其中,第一阈值和第二阈值在移动终端出厂时预先设置,可以修改。(String), 1(Integer), 12(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185972(Integer), 14. The cell reselection method of a mobile terminal according to claim 8, wherein, the first threshold and the second threshold are preset during factory manufacture of the mobile terminal, and are modifiable.(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185972(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the technical field of mobile communication, and in particular to a mobile terminal and a cell reselection method of a mobile terminal. BACKGROUND OF THE INVENTION [0002]With the development of mobile communication technology, at present, a same one operator usually operates a Wideband Code Division Multiple Access (WCDMA) network and a Global System for Mobile Communication (GSM) network at the same time, mainly for the reason: as the WCDMA in the mainstream standards of 3G is evolved from the GSM, in order to protect the investment on the GSM network at the earlier stage, the operator generally modifies and utilize the original GSM network; the operator needs to retain the old users of GSM network; and the WCDMA network construction cannot achieve complete coverage in short time. When the WCDMA network and the GSM network coexist, all the operators hope the users to switch from the GSM network to the WCDMA network, thus the users may use the rich 3G services, thereby increasing income of operators. [0003]In 3GPP protocol, there are requirements for reselection from the GSM cell to the WCDMA cell, relating to many parameters and algorithms, mainly comprising the following two adopted. [0004]First, control parameters of reselection from the GSM cell to the WCDMA cell are sent to the mobile terminal in the system information SYSTEM_INFORMATION—2QUATER; the mobile terminal stores these parameters after receiving them. The key parameters are as follows: [0005]3G Measurement Parameters Description[0006]Qsearch_I=7 (0×7)[0007]Qsearch_C_Initial=0 (0×0)[0008]fdd_qoffset_present=1 (0×1)[0009]FDD_Qoffset=0 (0×0)[0010]FDD_REP_QUANT=1 (0×1)[0011]FDD_MULTIRAT_REPORTING=0 (0×0)[0012]FDD_Qmin=7 (0×7)[0013]tdd_qoffset_present=0 (0×0) [0014]The description of value thereof can be obtained by referring to the 3GPP protocol 45.008, wherein the value of Qsearch_I is usually 7, which means to select the WCDMA cell unconditionally as long as the measurement of the WCDMA cell meets requirements, and the operator makes such configuration usually for the purpose of facilitating users to switch to the WCDMA network as much as possible; [0015]Second, after residing in the GSM cell, the mobile terminal constantly measures the surrounding WCDMA cells, calculates and judges the measured value according to the requirement of 6.6.5 in the 3GPP 45.008. Since the Qsearch_I is usually set as 7 (which means it is unconditional), finally it is judged whether the measured values of Received Energy per Chip Divided by the Noise Spectral Density (Ec/No) on each code channel of a transmitter after spreading spectrum and Received Signal Code Power (RSCP) meet the judging condition with the meeting lasts for more than 5 seconds, and if yes, a selection toward the WCDMA cell is initiated. The judging condition is that: whether the measured value of the Ec/No is greater than or equal to FDD_Qmin−FDD_Qmin_Offset; whether the measured value of the RSCP is greater than or equal to FDD_RSCP_threshold. [0016]The system information SYSTEM_INFORMATION—2QUATER sent by the network side decides the values of FDD_Qmin, FDD_Qmin_Offset and FDD_RSCP_threshold. The specific calculating and value setting methods can be know by referring to the 3GPP 45.008. [0017]In practical field test, it is often found that the mobile terminal can register to the WCDMA network when being set only in the WCDMA mode, but under the situation that the mobile terminal is set in WCDMA/GSM dual mode, if the mobile terminal firstly resides in the GSM cell, the measured values of the Ec/No and RSCP always do not meet the requirements, which causes the reselection toward the WCDMA cell cannot be initiated. Thus, the mobile terminal cannot reside in the WCDMA cell while the WCDMA network can be used actually. SUMMARY OF THE INVENTION [0018]The technical problem to be solved by the present invention is to provide a mobile terminal and a cell selection method thereof, which can improve the reselection capability of the mobile terminal from the GSM cell to the WCDMA cell. [0019]For solving the above technical problem, the present invention provides a cell selection method of a mobile terminal, which comprises the following steps: [0020]setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; and [0021]judging whether to initiate a reselection toward the WCDMA cell based on the s comparison between a signal measurement value of the WCDMA cell and the parameter. [0022]The step of setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: setting a first threshold of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum of the WCDMA cell, and setting a second threshold of RSCP. [0023]The step of judging based on comparison comprises: when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum of the WCDMA cell measured by the mobile terminal is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP of the WCDMA cell is greater than or equal to the second threshold which situation lasts for a second preset time, initiating a reselection toward the WCDMA cell. [0024]The first threshold is set as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, the second threshold is set as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0025]The first threshold and the second threshold can be preset during factory manufacture of the mobile terminal, and are modifiable. [0026]A mobile terminal, which comprises a setting module and a detecting module; the setting module is configured to set a reselection parameter of the mobile terminal from a GSM cell to a WCDMA cell, and the detecting module is configured to judge whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. [0027]The step of setting a reselection parameter of the mobile terminal from a GSM cell to a WCDMA cell comprises: the setting module sets a first threshold of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum, and sets a second threshold of RSCP. [0028]The detecting module is further configured to measure the value of the Ec/No of the mobile terminal on each code channel of the transmitter after spreading spectrum of the WCDMA cell and the value of the RSCP of the mobile terminal, and initiate a reselection toward the WCDMA cell when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum is greater than or equal to the first threshold which situation lasts for a first preset time, and the measured value of the RSCP is greater than or equal to the second threshold which situation lasts for a second preset time. [0029]The setting module is further configured to set the first threshold as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and set the second threshold as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0030]The setting module is further configured to preset the first threshold and the second threshold during factory manufacture of the mobile terminal, and set the first threshold and the second threshold as being modifiable. [0031]The beneficial effects of the present invention are as follows: [0032](1) in the present invention, setting a reselection parameter of a mobile terminal is from a GSM cell to a WCDMA cell, and judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter solve the problem that the mobile terminal, which is set in WCDMA/GSM dual mode, cannot reside in the WCDMA cell while the WCDMA network can be actually used, if the mobile terminal firstly resides in the GSM cell, and improve the capability and success rate of the reselection toward the WCDMA network of the mobile terminal, such that the user can have more opportunities to enjoy rich and colourful 3G services; [0033](2) in the present invention, when the measured value of Ec/No on each code channel of a transmitter after spreading spectrum of a WCDMA cell measured by the mobile terminal is greater than or equal to a first threshold which situation lasts for a first preset time, and the measured value of RSCP of the WCDMA cell is greater than or equal to a second threshold which situation lasts for a second preset time, a reselection toward the WCDMA cell is initiated, which is simple and easy to perform; [0034](3) in the present invention, the first threshold and the second threshold can be determined according to empirical values, which ensures that the mobile terminal can initiate a reselection from a GSM cell to a WCDMA cell when the condition is met; and [0035](4) in the present invention, the first threshold and the second threshold can be preset during factory manufacture of the mobile terminal and are modifiable, which enable the operator and user to set and modify based on actual need. Compared with the traditional art in which only the parameters sent by the network side are accepted, the first threshold and the second threshold can be adjusted according to actual situation, so it is more flexible and convenient to use. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a schematic diagram of a structure of a specific embodiment of a mobile terminal of the present invention; [0037]FIG. 2 is a flowchart of a cell reselection method of the present invention; and [0038]FIG. 3 is a flowchart of a specific embodiment of a cell reselection method of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0039]The present invention is described in detail hereinafter with reference to the accompanying drawings and in conjunction with embodiments. [0040]FIG. 1 is a schematic diagram of a structural of a specific embodiment of a mobile terminal of the present invention. As shown in FIG. 1, in an embodiment of the mobile terminal of the present invention, the mobile terminal comprises a setting module and a detecting module, wherein [0041]the setting module is configured to set a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; [0042]the detecting module is configured to judge whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter. [0043]The step that the setting module sets a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell comprises: the setting module sets a first threshold Ec/No min of Ec/No of the mobile terminal on each code channel of a transmitter after spreading spectrum of the WCDMA cell and sets a second threshold RSCP_min of RSCP. [0044]The step that the detecting module judges whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the set parameter comprises: the detecting module measures the value of the Ec/No on each code channel of the transmitter after spreading spectrum of the WCDMA cell and the value of the RSCP of the mobile terminal, and initiates a reselection toward the WCDMA cell when the measured value of the Ec/No on each code channel of the transmitter after spreading spectrum is greater than or equal to the first threshold Ec/No_min which situation lasts for a first preset time, and the measured value of the RSCP is greater than or equal to the second threshold RSCP_min, lasting for a second preset time. [0045]The first preset time can be set according to specific need, and in this specific embodiment, it can be set as 5 seconds or other suitable time. The second preset time can also be set according to specific need, and in this specific embodiment, it can be set as 5 seconds or other suitable time. [0046]Preferably, the first threshold Ec/No_min can be set as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset, and the second threshold RSCP_min can be set as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0047]The setting module is further configured to set the first threshold Ec/No_min and the second threshold RSCP_min according to empirical value. [0048]The setting module can preset the first threshold Ec/No_min and the second threshold RSCP_min during factory manufacture of the mobile terminal, and set them as being modifiable. [0049]FIG. 2 is a flowchart of a cell reselection method of the present invention. As shown in FIG. 2, the cell reselection method of the present invention comprises the following steps: [0050]Step 201: setting a reselection parameter of a mobile terminal from a GSM cell to a WCDMA cell; [0051]Step 202: judging whether to initiate a reselection toward the WCDMA cell based on the comparison between a signal measurement value of the WCDMA cell and the parameter. [0052]In this case, the parameter compared with the signal measurement value of the WCDMA cell is the reselection parameter from the GSM cell to the WCDMA cell in Step 201. [0053]The cell reselection method of a mobile terminal of the present invention is described hereinafter in detail. FIG. 3 is a flowchart of a specific embodiment of a cell reselection method of the present invention. As shown in FIG. 3, the method comprises the following steps: [0054]Step 301: setting the threshold Ec/No_min of the Ec/No and the threshold RSCP_min of the RSCP. [0055]In this specific embodiment, the threshold of the Ec/No is the first threshold, and specifically the first threshold Ec/No_min can be set as being greater than or equal to −18 dB and less than FDD_Qmin−FDD_Qmin_Offset. The threshold of the RSCP is the second threshold, and specifically the second threshold RSCP_min can be set as being greater than or equal to −105 dB and less than FDD_RSCP_threshold. [0056]The first threshold Ec/No_min and the second threshold RSCP min can be set according to empirical value. [0057]In practical application, the first threshold Ec/No_min and the second threshold RSCP_min can be preset during factory manufacture of the mobile terminal, and are set as being modifiable, thus they can be adjusted flexibly for different networks; [0058]Step 302: the mobile terminal detects a WCDMA cell. [0059]The mobile terminal measures the surrounding WCDMA cells and measures the signals thereof. In this specific embodiment, it is needed to measure the Ec/No and its lasting period, the RSCP and its lasting period and so on. [0060]Step 303: it is judged whether the measured value of the Ec/No is greater than or equal to the Ec/No_min which situation lasts for a first preset time, and whether the measured value of the RSCP is greater than or equal to the RSCP_min which situation lasts for a second preset time, and if yes, turning to Step 304, otherwise, turning to Step 302. [0061]The mobile terminal judges whether the measured value of the Ec/No is greater than or equal to the Ec/No_min which situation lasts for the first preset time, wherein the first preset time can be set according to specific requirement, and in this specific embodiment, it can be set as 5 seconds or other suitable time; the mobile terminal judges whether the measured value of the RSCP is greater than or equal to the RSCP_min which situation lasts for the second preset time, wherein the second preset time can also be set according to specific requirement, and in this specific embodiment, it can be set as 5 seconds or other suitable time. If simultaneously meeting the conditions that the measured value of the Ec/No is greater than or equal to the Ec/No_min which situation lasts for the first preset time, and the measured value of the RSCP is greater than or equal to the RSCP_min which situation lasts for the second preset time, it turns to Step 304, otherwise, it turns to Step 302. [0062]Step 304: initiating a reselection toward the WCDMA cell. [0063]In this case, the mobile terminal initiates the reselection toward the WCDMA cell. [0064]In the present invention, except setting the first threshold Ec/No_min and its first preset time, and the second threshold RSCP_min and its preset time, other parameters can be set according to the requirements of 6.6.5 in the 3GPP 45.008. [0065]The above content is further detailed descriptions of the present invention in conjunction with the specific embodiments, and the specific embodiments of the present invention should not limit only to these descriptions. Those skilled in the art can perform some simple deductions or equivalent substitutions without departing from the spirit of the present invention, and these deductions or substitutions are within the scope of the claims of the present invention.(String), 发明领域 [0001] 本发明涉及移动通信技术领域,尤其涉及一种移动终端及移动终端的小区重选方法。 发明背景 [0002] 随着移动通信技术的发展,目前同一个运营商通常同时运营一个宽带码分多址(WCDMA)网络和一个全球移动通信系统(GSM)网络,主要是因为:作为 3G主流标准中的WCDMA是从GSM演进而来的,为了保护前期对GSM网络的投资,运营商一般会对原有的GSM网络进行改造利用; 运营商需要留住GSM网络的老用户; 而WCDMA网络建设无法在短时间内实现全覆盖。 当WCDMA网络和GSM网络并存时,所有运营商都希望用户从GSM网络切换到WCDMA网络,这样用户就可以享受到丰富的3G业务,从而增加运营商的收入。 [0003] 在3GPP协议中,对从GSM小区重选到WCDMA小区有要求,涉及到很多参数和算法,主要采用的有以下两种。 [0004] 首先在系统信息SYSTEM_INFORMATION中向移动终端发送GSM小区重选到WCDMA小区的控制参数 — 2季度; 移动终端接收到这些参数后进行存储。 关键参数如下: [0005] 3G测量参数说明 [0006]Qsearch_I=7 (0×7)[0007] Qsearch_C_Initial=0 (0×0)[0008] fdd_qoffset_present=1 (0×1)[0009] FDD_Qoffset=0 (0×0)[0010] FDD_REP_QUANT=1 (0×1)[0011] FDD_MULTIRAT_REPORTING=0 (0×0)[0012] FDD_Qmin=7 (0×7)[0013] tdd_qoffset_present=0 (0×0) [0014] 其取值的描述可参考3GPP协议45.008,其中Qsearch_I的取值通常为7,表示只要WCDMA小区的测量满足要求,就无条件选择WCDMA小区,运营商做出这样的选择 配置通常是为了方便用户尽可能切换到WCDMA网络; [0015] 第二,移动终端驻留在GSM小区后,不断测量周围的WCDMA小区,根据3GPP 45.008中6.6.5的要求计算判断测量值。 由于Qsearch_I通常设置为7(表示无条件),最后判断扩频后发射机各码道上的每码片接收能量除以噪声谱密度(Ec/No)的测量值是否 和接收信号码功率(RSCP)满足判断条件且满足持续5秒以上,如果满足,则发起对WCDMA小区的选择。 判断条件为:Ec/No的测量值是否大于等于FDD_Qmin-FDD_Qmin_Offset; RSCP的测量值是否大于等于FDD_RSCP_threshold。 [0016] 系统信息SYSTEM_INFORMATION — 网络侧发送的2QUATER决定了FDD_Qmin、FDD_Qmin_Offset和FDD_RSCP_threshold的值。 具体的计算和取值方法可以参考3GPP 45.008。 [0017] 在实际外场测试中,经常发现移动终端只设置为WCDMA模式时可以注册到WCDMA网络,但是在移动终端设置为WCDMA/GSM双模式的情况下,如果移动终端先 驻留在GSM小区,Ec/No和RSCP的测量值总是不符合要求,导致无法发起向WCDMA小区的重选。 这样,移动终端不能驻留在WCDMA小区中,而WCDMA网络可以实际使用。 发明内容 [0018] 本发明所要解决的技术问题是提供一种移动终端及其小区选择方法,能够提高移动终端从GSM小区到WCDMA小区的重选能力。 [0019] 为解决上述技术问题,本发明提供了一种移动终端的小区选择方法,包括以下步骤: [0020] 设置移动终端从GSM小区到WCDMA小区的重选参数; 和 [0021]根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 [0022] 设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:在WCDMA小区扩频后,在发射机的每个码道上设置移动终端的第一门限Ec/No,设置 RSCP 的第二个阈值。 [0023] 所述基于比较判断的步骤包括:当移动终端测量的WCDMA小区扩频后的发射机各码道上的Ec/No测量值大于或等于第一门限时,该情况持续为 第一预设时间,WCDMA小区的RSCP测量值大于或等于第二阈值,该情况持续第二预设时间,发起向WCDMA小区的重选。 [0024] 第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。 [0025] 第一阈值和第二阈值可以在移动终端出厂时预先设置,可以修改。 [0026] 一种移动终端,包括设置模块和检测模块; 设置模块用于设置移动终端从GSM小区到WCDMA小区的重选参数,检测模块用于根据信号测量值与WCDMA小区的比较判断是否发起向WCDMA小区的重选 WCDMA 小区和参数。 [0027] 设置移动终端从GSM小区到WCDMA小区的重选参数的步骤包括:设置模块在发射机扩频后的每个码道上设置移动终端的第一门限Ec/No,并设置 RSCP 的第二个阈值。 [0028] 检测模块,还用于测量WCDMA小区扩频后发射机各码道上移动终端的Ec/No值和移动终端的RSCP值,并发起重选。 WCDMA小区,当发射机扩频后各码道上的Ec/No测量值大于或等于第一门限,且该情况持续第一预设时间,且RSCP测量值大于或等于 等于第二阈值,该情况持续第二预设时间。 [0029] 设置模块还用于将第一阈值设置为大于或等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,将第二阈值设置为大于或等于-105dB且小于FDD_RSCP_threshold。 [0030] 设置模块还用于在移动终端出厂时预先设置第一阈值和第二阈值,并设置第一阈值和第二阈值可修改。 [0031] 本发明的有益效果如下: [0032] (1)本发明中,设置移动终端的重选参数为从GSM小区到WCDMA小区,根据WCDMA小区信号测量值的比较判断是否发起向WCDMA小区的重选 该参数解决了设置为WCDMA/GSM双模式的移动终端无法驻留在WCDMA小区的问题,而如果移动终端先驻留在GSM小区,则可以实际使用WCDMA网络,提高了 移动终端重选WCDMA网络的能力和成功率,使用户有更多机会享受丰富多彩的3G业务; [0033](2)本发明中,当移动终端测量的WCDMA小区扩频后发射机各码道上的Ec/No测量值大于或等于第一门限时,该情况持续第一时间 预设时间,且WCDMA小区的RSCP测量值大于或等于第二阈值,且该情况持续第二预设时间,则发起向WCDMA小区的重选,简单易行。 [0034] (3)本发明中,第一门限和第二门限可以根据经验值确定,保证了移动终端在满足条件时能够发起从GSM小区到WCDMA小区的重选; 和 [0035] (4)在本发明中,第一阈值和第二阈值可以在移动终端出厂时预先设置,并且可以修改,使得运营商和用户可以根据实际需要进行设置和修改。 与传统技术只接受网络侧发送的参数相比,第一门限和第二门限可以根据实际情况进行调整,使用起来更加灵活方便。 附图的简要说明 [0036] 图1为本发明移动终端一个具体实施例的结构示意图; [0037] 图2是本发明小区重选方法的流程图; 和 [0038] 图3为本发明小区重选方法的一个具体实施例的流程图。 具体实施方式 [0039] 下面将参照附图并结合实施例对本发明进行详细说明。 [0040] 图1为本发明移动终端一个具体实施例的结构示意图。 如图1所示,在本发明移动终端的一个实施例中,移动终端包括设置模块和检测模块,其中 [0041] 设置模块,用于设置移动终端从GSM小区到WCDMA小区的重选参数; [0042] 检测模块,用于根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选。 [0043] 设置模块设置移动终端从GSM小区到WCDMA小区的重选参数包括:设置模块在发射机的每个码道上设置移动终端的Ec/No的第一阈值Ec/No min 在WCDMA小区扩频之后,设置RSCP的第二阈值RSCP_min。 [0044] 检测模块根据WCDMA小区的信号测量值与设置参数的比较,判断是否向WCDMA小区发起重选包括: 检测模块测量各码道上的Ec/No值 WCDMA小区扩频后发射机的RSCP值与移动终端RSCP的值,当发射机扩频后各码道上的Ec/No测量值较大时,向WCDMA小区发起重选 大于等于第一阈值Ec/No_min,持续第一预设时间,RSCP的测量值大于等于第二阈值RSCP_min,持续第二预设时间。 [0045] 第一预设时间可以根据具体需要进行设置,在本具体实施例中,可以设置为5秒或者其他合适的时间。 第二预设时间也可以根据具体需要进行设置,在本具体实施例中,可以设置为5秒或者其他合适的时间。 [0046] 优选地,第一门限Ec/No_min可设置为大于等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset,第二门限RSCP_min可设置为大于等于-105dB且小于FDD_RSCP_threshold . [0047]设置模块还用于根据经验值设置第一阈值Ec/No_min和第二阈值RSCP_min。 [0048] 设置模块可以在移动终端出厂时预先设置第一阈值Ec/No_min和第二阈值RSCP_min,并设置为可修改。 [0049] 图2是本发明小区重选方法的流程图。 如图2所示,本发明的小区重选方法包括以下步骤: [0050] 步 201 :设置移动终端从GSM小区到WCDMA小区的重选参数; [0051] 步 202 :根据WCDMA小区的信号测量值与参数的比较,判断是否向WCDMA小区发起重选。 [0052] 此时,与WCDMA小区的信号测量值比较的参数为步骤中GSM小区到WCDMA小区的重选参数 201 . [0053] 下面对本发明的移动终端的小区重选方法进行详细说明。 图3为本发明小区重选方法的一个具体实施例的流程图。 如图3所示,该方法包括以下步骤: [0054] 步 301 :设置Ec/No的阈值Ec/No_min和RSCP的阈值RSCP_min。 [0055] 本具体实施例中,Ec/No的门限为第一门限,具体可以将第一门限Ec/No_min设置为大于等于-18dB且小于FDD_Qmin-FDD_Qmin_Offset。 RSCP的阈值为第二阈值,具体可以将第二阈值RSCP_min设置为大于等于-105dB且小于FDD_RSCP_threshold。 [0056] 第一阈值Ec/No_min和第二阈值RSCP min可根据经验值设定。 [0057] 在实际应用中,第一门限Ec/No_min和第二门限RSCP_min可以在移动终端出厂时预先设置,设置为可修改的,从而可以针对不同的网络灵活调整。 [0058] 步 302 :移动终端检测到WCDMA小区。 [0059] 移动终端测量周围的WCDMA小区并测量其信号。 在本具体实施例中,需要测量Ec/No及其持续时间、RSCP及其持续时间等。 [0060] 步 303 :判断Ec/No的测量值是否大于或等于Ec/No_min哪种情况持续第一预设时间,以及RSCP的测量值是否大于或等于RSCP_min哪种情况 持续第二个预设时间,如果是,则转到步骤 304 , 否则转向 Step 302 . [0061] 移动终端判断Ec/No的测量值是否大于或等于Ec/No_min哪种情况持续第一预设时间,其中第一预设时间可以根据具体需要设置,在本具体实施例中 ,可设置为5秒或其他合适的时间; 移动终端判断RSCP的测量值是否大于或等于RSCP_min,这种情况持续第二预设时间,其中,第二预设时间也可以根据具体需要进行设置,在本具体实施例中,可以 设置为 5 秒或其他合适的时间。 如果同时满足Ec/No测量值大于或等于Ec/No_min这种情况持续第一个预设时间,并且RSCP测量值大于或等于RSCP_min这种情况 持续第二个预设时间,转为Step 304 , 否则转为 Step 302 . [0062] 步 304 :向WCDMA小区发起重选。 [0063] 在这种情况下,移动终端发起向WCDMA小区的重选。 [0064]本发明中,除了设置第一阈值Ec/No_min及其第一预设时间、第二阈值RSCP_min及其预设时间外,其他参数可按照3GPP 45.008中6.6.5的要求进行设置。 [0065] 以上内容是结合具体实施例对本发明所做的进一步详细说明,本发明的具体实施不应只局限于这些说明。 本领域的技术人员可以在不脱离本发明的精神的情况下进行一些简单的推演或等同替换,这些推演或替换都在本发明的权利要求的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101707791A(String), EP2503821A1(String), EP2503821A4(String), US20120231798A1(String), WO2011060657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:55.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101707791A(String), EP2503821A1(String), EP2503821A4(String), US20120231798A1(String), WO2011060657A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120231798A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101707791A(String), EP2503821A1(String), EP2503821A4(String), US20120231798A1(String), WO2011060657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271658(Integer), CN101707791A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271658(Integer), EP2503821A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271658(Integer), EP2503821A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271658(Integer), US20120231798A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271658(Integer), WO2011060657A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120231798A1(String), US20120231798A1(String), 1347465600(Integer), 271658(Integer), 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185972(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185972(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185972(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185972(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185972(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:56.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20170131793A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Controlling Mobile Terminal Screen Display and Mobile Terminal(String), 一种控制移动终端屏幕显示的方法及移动终端(String), US20170131793A1(String), A method for controlling mobile terminal screen display, and a mobile terminal is presented. The method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 提出了一种控制移动终端屏幕显示的方法及移动终端。 该方法包括获取移动终端的当前倾斜角度; 当确定当前倾斜角度在第二或第三预设角度范围内时,根据该倾斜角度调整移动终端屏幕的界面内容布局。 或者,在确定移动终端的当前倾斜角度在第一预设角度范围内时,保持移动终端屏幕现有的界面内容布局,其中第二、第一和第三预设角度范围依次形成连续的角度范围。(String), US15/414869(String), 1485273600(Integer), US20170131793A1(String), 1494432000(Integer), 美国(String), 2(Integer), 5(Integer), 0(Integer), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.209 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185973(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c409672caa284507bce83ce0aebbd676.png(String), 185973(Integer), c409672caa284507bce83ce0aebbd676.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Controlling Mobile Terminal Screen Display and Mobile Terminal(String), 一种控制移动终端屏幕显示的方法及移动终端(String), US20170131793A1(String), A method for controlling mobile terminal screen display, and a mobile terminal is presented. The method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 提出了一种控制移动终端屏幕显示的方法及移动终端。 该方法包括获取移动终端的当前倾斜角度; 当确定当前倾斜角度在第二或第三预设角度范围内时,根据该倾斜角度调整移动终端屏幕的界面内容布局。 或者,在确定移动终端的当前倾斜角度在第一预设角度范围内时,保持移动终端屏幕现有的界面内容布局,其中第二、第一和第三预设角度范围依次形成连续的角度范围。(String), US15/414869(String), 1485273600(Integer), US20170131793A1(String), 1494432000(Integer), 美国(String), 2(Integer), 2(Integer), 5(Integer), 0(Integer), \20230420\c409672caa284507bce83ce0aebbd676.png(String), 20(Integer), 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 1. A mobile terminal, comprising:a sensor configured to acquire a current tilt angle of the mobile terminal;a screen configured to display interface content on the mobile terminal; anda processor configured to:adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a second or third preset angle range; andkeep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 1.移动终端,包括:传感器,用于获取移动终端的当前倾斜角度;屏幕,用于在移动终端上显示界面内容;和处理器配置为:在确定当前倾斜角度处于第二或第三预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 2. The mobile terminal according to claim 1, wherein the processor being configured to adjust the interface content layout of the mobile terminal screen according to the tilt angle comprises the processor being configured to:determine an adjustment magnitude according to the tilt angle; andadjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude.(String), 2.根据权利要求1所述的移动终端,其中处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,包括:根据倾斜角度确定调整幅度;和根据调整幅度调整移动终端屏幕的全部或部分界面内容。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 3. The mobile terminal according to claim 2, wherein the processor being configured to determine the adjustment magnitude according to the tilt angle, and adjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude comprises the processor being configured to implement one of the following:determine an adjustment distance according to the tilt angle, and pan or float all or a part of the interface content of the mobile terminal screen, wherein a distance of the panning or floating is the adjustment distance; anddetermine an adjustment angle according to the tilt angle, and rotate all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, wherein an angle of the rotating is the adjustment angle.(String), 3.根据权利要求2所述的移动终端,其中处理器,用于根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容,包括:处理器,用于实现以下之一:根据倾斜角度确定调整距离,对移动终端屏幕的全部或部分界面内容进行平移或浮动,平移或浮动的距离即为调整距离。和根据倾斜角度确定调整角度,以移动终端屏幕为中心旋转移动终端屏幕的全部或部分界面内容,旋转的角度即为调整角度。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 4. The mobile terminal according to claim 3, wherein the processor being configured to adjust the interface content layout of the mobile terminal screen according to the tilt angle further comprises the processor being configured to:determine an adjustment direction according to the tilt angle; andadjust the interface content layout of the mobile terminal screen in the determined adjustment direction.(String), 4.根据权利要求3所述的移动终端,其中处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,还包括:处理器,用于:根据倾斜角度确定调整方向;和沿确定的调整方向调整移动终端屏幕的界面内容布局。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 5. The mobile terminal according to claim 4, wherein the processor being configured to determine the adjustment direction according to the tilt angle comprises the processor being configured to:determine that the adjustment direction is a first direction when the current tilt angle is in the second preset angle range; anddetermine that the adjustment direction is a second direction when the current tilt angle is in the third preset angle range.(String), 5.根据权利要求4所述的移动终端,其中处理器,用于根据倾斜角度确定调整方向,包括:处理器,用于:当前倾斜角度在第二预设角度范围内时,确定调整方向为第一方向;和当前倾斜角度在第三预设角度范围内时,确定调整方向为第二方向。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 6. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 6.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向上,当移动终端当前的倾斜角度小于第一阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮;和确定调整方向为向下,当移动终端当前倾斜角度大于第二阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 7. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 7.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向下,当移动终端当前倾斜角度小于第一阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容;和确定调整方向为向上,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或浮动。(String), 1(Integer), 6(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 8. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 8.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向右,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动;和确定调整方向为向左,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。(String), 1(Integer), 7(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 9. The mobile terminal according to claim 4, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 9.根据权利要求4所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向左,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动;和确定调整方向为向右,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。(String), 1(Integer), 8(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 10. The mobile terminal according to claim 2, wherein the sensor is further configured to acquire ambient light intensity information of the mobile terminal, and wherein the processor being configured to determine an adjustment magnitude according to the tilt angle comprises the processor being configured to determine, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle.(String), 10.根据权利要求2所述的移动终端,其中所述传感器,还用于获取所述移动终端的环境光强度信息,其中,所述处理器用于根据所述倾斜角度确定调整幅度,包括所述处理器用于根据所述环境光强度信息确定调整量对应于倾斜角的大小。(String), 1(Integer), 9(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 11. The mobile terminal according to claim 1, wherein the processor is further configured to:receive angle range adjustment information; andadjust at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information.(String), 11.根据权利要求1所述的移动终端,其中处理器还被配置为:接收角度范围调整信息;和根据角度范围调整信息调整第一、第二或第三预设角度范围中的至少一个预设角度范围。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 12. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 12.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向上,当移动终端当前的倾斜角度小于第一阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮;和确定调整方向为向下,当移动终端当前倾斜角度大于第二阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容。(String), 1(Integer), 11(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 13. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a length direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 13.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的长度方向与水平面之间的夹角,其中,处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器被配置为:确定调整方向为向下,当移动终端当前倾斜角度小于第一阈值时,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容;和确定调整方向为向上,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的界面内容全部或部分在屏幕上平移或浮动。(String), 1(Integer), 12(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 14. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 14.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向右,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动;和确定调整方向为向左,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。(String), 1(Integer), 13(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 15. The mobile terminal according to claim 5, wherein the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, wherein the first threshold is less than the second threshold, wherein the tilt angle of the mobile terminal is an angle comprised between a width direction of the mobile terminal screen and a horizontal plane, and wherein the processor being configured to determine the adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction comprises the processor being configured to:determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen when the current tilt angle of the mobile terminal is less than the first threshold; anddetermine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen when the current tilt angle of the mobile terminal is greater than the second threshold.(String), 15.根据权利要求5所述的移动终端,其中第一预设角度范围为大于或等于第一阈值且小于或等于第二阈值的角度范围,其中第一阈值小于第二阈值,其中移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面之间的夹角,其中处理器用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括处理器被配置为:确定调整方向为向左,当移动终端当前倾斜角度小于第一阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动;和确定调整方向为向右,当移动终端当前倾斜角度大于第二阈值时,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。16、一种控制移动终端屏幕显示的方法,包括:获取移动终端的当前倾斜角度;当确定当前倾斜角度在第二或第三预设角度范围内时,根据倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。(String), 1(Integer), 14(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 16. A method for controlling mobile terminal screen display, comprising:acquiring a current tilt angle of a mobile terminal;adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; andkeeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 17.根据权利要求16所述的方法,其中根据倾斜角度调整移动终端屏幕的界面内容布局包括:根据倾斜角度确定调整幅度;和根据调整幅度调整移动终端屏幕的全部或部分界面内容。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 17. The method according to claim 16, wherein adjusting the interface content layout of the mobile terminal screen according to the tilt angle comprises:determining an adjustment magnitude according to the tilt angle; andadjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude.(String), 18.根据权利要求17所述的方法,其中根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容,包括以下之一:根据倾斜角度确定调整距离,对移动终端屏幕的全部或部分界面内容进行平移或浮动,平移或浮动的距离即为调整距离。和根据倾斜角度确定调整角度,以移动终端屏幕为中心旋转移动终端屏幕的全部或部分界面内容,旋转的角度即为调整角度。19、一种控制移动终端屏幕显示的方法,包括:获取移动终端的当前倾斜角度;在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 18. The method according to claim 17, wherein determining the adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude comprises one of the following:determining an adjustment distance according to the tilt angle, and panning or floating all or a part of the interface content of the mobile terminal screen, wherein a distance of the panning or floating is the adjustment distance; anddetermining an adjustment angle according to the tilt angle, and rotating all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, wherein an angle of the rotating is the adjustment angle.(String), 20.移动终端,包括:传感器,用于获取移动终端的当前倾斜角度;屏幕,用于在移动终端上显示界面内容;和处理器配置为:在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局;和在确定移动终端当前倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 19. A method for controlling mobile terminal screen display, comprising:acquiring a current tilt angle of a mobile terminal;adjusting an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; andkeeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.485 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185973(Integer), 20. A mobile terminal, comprising:a sensor configured to acquire a current tilt angle of the mobile terminal;a screen configured to display interface content on the mobile terminal; anda processor configured to:adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; andkeep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, wherein the second, first, and third preset angle ranges sequentially form a continuous angle range.(String), 0(Integer), 19(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185973(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Patent Application No. PCT/CN2014/083097 filed on Jul. 26, 2014, the disclosure of which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present disclosure relates to the technical field of mobile terminals, and in particular, to a method for controlling mobile terminal screen display and a mobile terminal. BACKGROUND [0003]Currently, functions of mobile terminals such as a mobile phone and a tablet keep increasing. Nowadays, most smart mobile terminals can switch between a landscape orientation and a portrait orientation of an interface (which is equivalent to rotating the interface by 90 degrees) on a mobile terminal screen so long as a tilt angle of the mobile terminal is greater than a specific angle, which, however, tends to cause unwanted switching. That is, although the mobile terminal tilts at a specific angle, a user does not expect switching of interface display. Consequently, control of screen display does not exactly meet a use requirement of the user, thereby lowering user experience. SUMMARY [0004]Embodiments of the present disclosure provide a method for controlling mobile terminal screen display and a mobile terminal to better meet a use requirement of a user and improve user experience. [0005]According to a first aspect, an embodiment of the present disclosure provides a method for controlling mobile terminal screen display, where the method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0006]With reference to the first aspect, in a first possible implementation manner of the first aspect, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle includes determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude. [0007]With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude includes determining an adjustment distance according to the tilt angle, and panning or floating all or a part of the interface content of the mobile terminal screen, where a distance of the panning or floating is the adjustment distance; or determining an adjustment angle according to the tilt angle, and rotating all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, where an angle of the rotating is the adjustment angle. [0008]With reference to the first or second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle further includes determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction. [0009]With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the determining an adjustment direction according to the tilt angle includes, when the current tilt angle is in the second preset angle range, determining that the adjustment direction is a first direction; or when the current tilt angle is in the third preset angle range, determining that the adjustment direction is a second direction. [0010]With reference to the third or fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen. [0011]With reference to the third or fourth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen. [0012]With reference to the third or fourth possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen. [0013]With reference to the third or fourth possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen. [0014]With reference to any one of the first possible implementation manner of the first aspect to the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner of the first aspect, the method further includes acquiring ambient light intensity information of the mobile terminal; and the determining an adjustment magnitude according to the tilt angle includes determining, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle. [0015]With reference to the first aspect or any one of the first possible implementation manner of the first aspect to the ninth possible implementation manner of the first aspect, in a tenth possible implementation manner of the first aspect, the method further includes receiving angle range adjustment information; and adjusting at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information. [0016]According to a second aspect, an embodiment of the present disclosure provides a method for controlling mobile terminal screen display, where the method includes acquiring a current tilt angle of a mobile terminal; and adjusting an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; or keeping an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0017]According to a third aspect, an embodiment of the present disclosure provides a mobile terminal, where the mobile terminal includes a sensor configured to acquire a current tilt angle of the mobile terminal; a screen configured to display interface content on the mobile terminal; and a processor configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a second or third preset angle range; or keep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0018]With reference to the third aspect, in a first possible implementation manner of the third aspect, the processor being configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle includes the processor being configured to determine an adjustment magnitude according to the tilt angle, and adjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude. [0019]With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the processor being configured to determine an adjustment magnitude according to the tilt angle, and adjust all or a part of interface content of the mobile terminal screen according to the adjustment magnitude includes the processor being configured to determine an adjustment distance according to the tilt angle, and pan or float all or a part of the interface content of the mobile terminal screen, where a distance of the panning or floating is the adjustment distance; or the processor being configured to determine an adjustment angle according to the tilt angle, and rotate all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, where an angle of the rotating is the adjustment angle. [0020]With reference to the first or second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the processor being configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle further includes the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction. [0021]With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the processor being configured to determine an adjustment direction according to the tilt angle is the processor being configured to, when the current tilt angle is in the second preset angle range, determine that the adjustment direction is a first direction; or when the current tilt angle is in the third preset angle range, determine that the adjustment direction is a second direction. [0022]With reference to the third or fourth possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen. [0023]With reference to the third or fourth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is downward, and pan or float all or a part of the interface content of the mobile terminal screen downward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is upward, and pan or float all or a part of the interface content of the mobile terminal screen upward on the screen. [0024]With reference to the third or fourth possible implementation manner of the third aspect, in a seventh possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen. [0025]With reference to the third or fourth possible implementation manner of the third aspect, in an eighth possible implementation manner of the third aspect, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold; the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane; and the processor being configured to determine an adjustment direction according to the tilt angle, and adjust the interface content layout of the mobile terminal screen in the determined adjustment direction includes the processor being configured to, if the current tilt angle of the mobile terminal is less than the first threshold, determine that the adjustment direction is leftward, and pan or float all or a part of the interface content of the mobile terminal screen leftward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determine that the adjustment direction is rightward, and pan or float all or a part of the interface content of the mobile terminal screen rightward on the screen. [0026]With reference to any one of the first possible implementation manner of the third aspect to the eighth possible implementation manner of the third aspect, in a ninth possible implementation manner of the third aspect, the sensor is further configured to acquire ambient light intensity information of the mobile terminal; and the processor being configured to determine an adjustment magnitude according to the tilt angle includes the processor being configured to determine, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle. [0027]With reference to the third aspect or any one of the first possible implementation manner of the third aspect to the ninth possible implementation manner of the third aspect, in a tenth possible implementation manner of the third aspect, the processor is further configured to receive angle range adjustment information; and adjust at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information. [0028]According to a fourth aspect, an embodiment of the present disclosure provides a mobile terminal, where the mobile terminal includes a sensor configured to acquire a current tilt angle of the mobile terminal; a screen configured to display interface content on the mobile terminal; and a processor configured to adjust an interface content layout of a mobile terminal screen according to the tilt angle of the mobile terminal when determining that the current tilt angle is in a first preset angle range; or keep an interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a second or third preset angle range, where the second, first, and third preset angle ranges sequentially form a continuous angle range. [0029]According to the method and the mobile terminal that are provided in the embodiments of the present disclosure, a current tilt angle of the mobile terminal may be detected; and an interface content layout of a mobile terminal screen is adjusted according to the tilt angle only in a case in which the current tilt angle of the mobile terminal meets a specific range condition, for example, when the current tilt angle of the mobile terminal is in a second or third preset angle range; or an existing interface content layout of a mobile terminal screen is kept when the current tilt angle of the mobile terminal is in a first preset angle range. In this way, screen display adjustment is avoided in a case in which a user does not expect the screen display adjustment although the mobile terminal tilts at a specific angle, so that the method for controlling mobile terminal screen display better meets a use requirement of the user and improves user experience. BRIEF DESCRIPTION OF DRAWINGS [0030]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0031]FIG. 1 is a flowchart of a method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0032]FIG. 2 is a flowchart of another method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0033]FIG. 3A, FIG. 3B, FIG. 4A, FIG. 4B, FIG. 5A, and FIG. 5B, are schematic diagrams of a tilt angle of a mobile terminal according to an embodiment of the present disclosure; [0034]FIG. 6, FIG. 7, FIG. 8, FIG. 9, and FIG. 10 are schematic effect diagrams of a method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0035]FIG. 11, FIG. 12, and FIG. 13 are schematic effect diagrams of another method for controlling mobile terminal screen display according to an embodiment of the present disclosure; [0036]FIG. 14 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure; [0037]FIG. 15 is a schematic diagram of a tilt angle of a mobile terminal according to an embodiment of the present disclosure; and [0038]FIG. 16A, FIG. 16B, FIG. 16C, FIG. 16D, FIG. 16E, FIG. 16F, and FIG. 16G are schematic effect diagrams of another method for controlling mobile terminal screen display according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0039]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0040]The term “and/or” in this specification describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, the character “/” in this specification generally indicates an “or” relationship between associated objects. Embodiment 1 [0041]As shown in FIG. 1, in an embodiment of a method for controlling mobile terminal screen display according to the present disclosure, the method may include the following steps. [0042]Step 101. Acquire a current tilt angle of a mobile terminal. [0043]The current tilt angle of the mobile terminal may be detected and acquired using a sensor such as a gravity sensor or a gyro sensor. [0044]The mobile terminal in the present disclosure may be a mobile terminal device with a screen, such as a mobile phone, a tablet, or a personal digital assistant (PDA), where the screen may be a touchscreen. [0045]Step 102. Adjust an interface content layout of a mobile terminal screen according to the tilt angle when determining that the current tilt angle is in a second or third preset angle range. [0046]Step 103. Keep an existing interface content layout of a mobile terminal screen when determining that the current tilt angle of the mobile terminal is in a first preset angle range, that is, skip adjusting the interface content layout currently displayed on the mobile terminal screen. [0047]The second, first, and third preset angle ranges sequentially form a continuous angle range. [0048]Further, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle includes determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude. [0049]Further, the determining an adjustment magnitude according to the tilt angle, and adjusting all or a part of interface content of the mobile terminal screen according to the adjustment magnitude includes determining an adjustment distance according to the tilt angle, and panning or floating all or a part of the interface content of the mobile terminal screen, where a distance of the panning or floating is the adjustment distance; or determining an adjustment angle according to the tilt angle, and rotating all or a part of the interface content of the mobile terminal screen around a center of the mobile terminal screen, where an angle of the rotating is the adjustment angle. [0050]Further, the adjusting an interface content layout of a mobile terminal screen according to the tilt angle further includes determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction. [0051]Further, the determining an adjustment direction according to the tilt angle includes, when the current tilt angle is in the second preset angle range, determining that the adjustment direction is a first direction; or when the current tilt angle is in the third preset angle range, determining that the adjustment direction is a second direction. [0052]The first direction may be the same as or different from the second direction, which may be determined according to a specific condition. [0053]Further, the first preset angle range is a range of an angle greater than or equal to a first threshold and less than or equal to a second threshold, where the first threshold is less than the second threshold. [0054]The current tilt angle of the mobile terminal may be an acute angle or a right angle, the first threshold is greater than 0 degrees, and the second threshold is less than or equal to 90 degrees. [0055]For example, the first threshold may be 30 degrees, and the second threshold may be 60 degrees. [0056]In a specific embodiment, the tilt angle of the mobile terminal is an angle included between a length direction of the mobile terminal screen and a horizontal plane. [0057]In an implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen. [0058]Alternatively, in another implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is downward, and panning or floating all or a part of the interface content of the mobile terminal screen downward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is upward, and panning or floating all or a part of the interface content of the mobile terminal screen upward on the screen. [0059]In another specific embodiment, the tilt angle of the mobile terminal is an angle included between a width direction of the mobile terminal screen and a horizontal plane. [0060]In an implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen. [0061]Alternatively, in another implementation manner, the determining an adjustment direction according to the tilt angle, and adjusting the interface content layout of the mobile terminal screen in the determined adjustment direction includes, if the current tilt angle of the mobile terminal is less than the first threshold, determining that the adjustment direction is leftward, and panning or floating all or a part of the interface content of the mobile terminal screen leftward on the screen; or if the current tilt angle of the mobile terminal is greater than the second threshold, determining that the adjustment direction is rightward, and panning or floating all or a part of the interface content of the mobile terminal screen rightward on the screen. [0062]Further, the method may further include acquiring ambient light intensity information of the mobile terminal, where the ambient light intensity information of the mobile terminal may be acquired using a light sensor. [0063]The determining an adjustment magnitude according to the tilt angle includes determining, according to the ambient light intensity information, an adjustment magnitude corresponding to the tilt angle. [0064]Further, the method may further include receiving angle range adjustment information; and adjusting at least one preset angle range of the first, second, or third preset angle range according to the angle range adjustment information. [0065]Information about adjustment of an angle range may be received from a user. In this way, for a different user, a proper angle range may be configured for the different user according to an actual use habit or requirement of the different user, and the interface content layout of the mobile terminal screen may be adjusted according to the proper angle range. Such an adjustment can better meet the actual use habit or requirement of the user, and reduce an unnecessary adjustment of the interface content layout of the mobile terminal screen. [0066]Further, optionally, the method may further include recei(String), 相关申请的交叉引用 [0001] 本申请是2014年7月26日提交的国际专利申请号PCT/CN2014/083097的继续申请,其公开内容通过引用全部并入本文。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端屏幕显示的控制方法及移动终端。 背景 [0003] 目前,手机、平板等移动终端的功能不断丰富。 现在大部分智能移动终端只要移动终端的倾斜角度大于 特定的角度,然而,这往往会导致不必要的切换。 也就是说,虽然移动终端倾斜了特定的角度,但用户并不期望界面显示的切换。 因此,对屏幕显示的控制并不能完全满足用户的使用需求,从而降低了用户体验。 概括 [0004] 本发明实施例提供一种移动终端屏幕显示的控制方法及移动终端,以更好地满足用户的使用需求,提高用户体验。 [0005] 第一方面,本发明实施例提供了一种控制移动终端屏幕显示的方法,该方法包括获取移动终端当前的倾斜角度; 当确定当前倾斜角度处于第二或第三预设角度范围内时,根据倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。 [0006] 结合第一方面,在第一方面的第一种可能的实现方式中,所述根据倾斜角度调整移动终端屏幕的界面内容布局,包括根据倾斜角度确定调整幅度,调整全部或部分内容。 移动端屏幕部分界面内容根据调整幅度。 [0007] 结合第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,所述根据倾斜角度确定调整幅度,根据所述调整移动终端屏幕的全部或部分界面内容。 调整幅度包括根据倾斜角度确定调整距离,平移或浮动移动终端屏幕的全部或部分界面内容,平移或浮动的距离为调整距离。 或者,根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容以移动终端屏幕为中心旋转,旋转的角度即为调整角度。 [0008] 结合第一方面的第一种或第二种可能的实现方式,在第一方面的第三种可能的实现方式中,所述根据倾斜角度调整移动终端屏幕的界面内容布局,还包括根据倾斜角度确定调整方向。 倾斜角度,按照确定的调整方向调整移动终端屏幕的界面内容布局。 [0009] 结合第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中,所述根据倾斜角度确定调整方向包括:当当前倾斜角度在第二预设角度范围内时,确定 调整方向为第一方向; 或者,当当前倾斜角度处于第三预设角度范围内时,确定调整方向为第二方向。 [0010]结合第一方面的第三种或第四种可能的实现方式,在第一方面的第五种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或悬浮; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0011] 结合第一方面的第三种或第四种可能的实现方式,在第一方面的第六种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向为向下,在屏幕上向下平移或浮动移动终端屏幕的全部或部分界面内容; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或悬浮。 [0012] 结合第一方面的第三种或第四种可能的实现方式,在第一方面的第七种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0013]结合第一方面的第三种或第四种可能的实现方式,在第一方面的第八种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值,则确定调整 方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动; 或者,如果移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0014] 结合第一方面的第一种可能的实现方式至第一方面的第八种可能的实现方式中的任一种,在第一方面的第九种可能的实现方式中,所述方法还包括获取移动终端的环境光强度信息。 ; 其中,根据倾斜角度确定调整幅度包括:根据环境光强度信息确定倾斜角度对应的调整幅度。 [0015] 结合第一方面或第一方面的第一种可能的实现方式至第一方面的第九种可能的实现方式中的任一种,在第一方面的第十种可能的实现方式中,所述方法还包括:接收角度范围调整信息 ; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0016] 第二方面,本发明实施例提供了一种控制移动终端屏幕显示的方法,该方法包括获取移动终端当前的倾斜角度; 当确定当前倾斜角度在第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕已有的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围 . [0017] 第三方面,本发明实施例提供了一种移动终端,该移动终端包括传感器,用于获取移动终端当前的倾斜角度; 屏幕,用于在移动终端上显示界面内容; 处理器,用于在确定当前倾斜角度处于第二或第三预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。 [0018] 结合第三方面,在第三方面的第一种可能的实现方式中,所述处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,包括: 所述处理器,用于根据以下参数确定调整幅度: 倾斜角度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0019]结合第三方面的第一种可能的实现方式,在第三方面的第二种可能的实现方式中,所述处理器,用于根据倾斜角度确定调整幅度,调整所述界面的全部或部分内容。 根据调整幅度移动终端屏幕包括处理器,用于根据倾斜角度确定调整距离,平移或浮动移动终端屏幕的全部或部分界面内容,其中,平移或浮动的距离 为调整距离; 或者,处理器,用于根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容围绕移动终端屏幕的中心旋转,旋转的角度为调整角度 . [0020] 结合第三方面的第一种或第二种可能的实现方式,在第三方面的第三种可能的实现方式中,所述处理器,用于根据倾斜角度调整移动终端屏幕的界面内容布局,还包括: 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0021] 结合第三方面的第三种可能的实现方式,在第三方面的第四种可能的实现方式中,所述处理器,用于根据所述倾斜角度确定调整方向,所述处理器用于,当当前倾斜角度为 处于第二预设角度范围内,确定调整方向为第一方向; 或者,当前倾斜角度在第三预设角度范围内时,确定调整方向为第二方向。 [0022] 结合第三方面的第三种或第四种可能的实现方式,在第三方面的第五种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0023]结合第三方面的第三种或第四种可能的实现方式,在第三方面的第六种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮。 [0024] 结合第三方面的第三种或第四种可能的实现方式,在第三方面的第七种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0025] 结合第三方面的第三种或第四种可能的实现方式,在第三方面的第八种可能的实现方式中,所述第一预设角度范围为大于等于第一阈值且小于等于第一阈值的角度范围 到第二阈值,其中第一阈值小于第二阈值; 移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角; 处理器,用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器,用于若移动终端的当前倾斜角度小于 比第一阈值确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0026] 结合第三方面的第一种可能的实现方式至第三方面的第八种可能的实现方式中的任一种,在第三方面的第九种可能的实现方式中,所述传感器,还用于获取所述传感器的环境光强度信息。 移动终端; 处理器,用于根据倾斜角度确定调整幅度,包括处理器,用于根据环境光强度信息,确定倾斜角度对应的调整幅度。 [0027]结合第三方面或第三方面的第一种可能的实现方式至第三方面的第九种可能的实现方式中的任一种,在第三方面的第十种可能的实现方式中,所述处理器还用于接收角度范围 调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0028] 第四方面,本发明实施例提供了一种移动终端,该移动终端包括传感器,用于获取移动终端当前的倾斜角度; 屏幕,用于在移动终端上显示界面内容; 处理器,用于在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。 [0029] 本发明实施例提供的方法及移动终端,可以检测移动终端当前的倾斜角度; 仅在移动终端当前倾斜角度满足特定范围条件的情况下,例如当移动终端当前倾斜角度为 在第二或第三预设角度范围内; 或者,当移动终端的当前倾斜角度在第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局。 这样,避免了在移动终端倾斜特定角度但用户不希望进行屏幕显示调整的情况下进行屏幕显示调整,使得本控制移动终端屏幕显示的方法更好地满足了用户的使用需求。 用户并改善用户体验。 附图说明 [0030] 为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简要说明。 下面描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0031] 图1为本发明实施例的移动终端屏幕显示控制方法的流程图; [0032] 图2为本发明实施例提供的另一种移动终端屏幕显示控制方法的流程图; [0033] 图3A、图3B、图4A、图4B、图5A、图5B为本发明实施例的移动终端的倾斜角度示意图。 [0034] 图6、图7、图8、图9和图10为本发明实施例的移动终端屏幕显示控制方法的效果示意图; [0035] 图11、图12和图13为本发明实施例提供的另一种控制移动终端屏幕显示的方法的效果示意图; [0036] 图14为本发明实施例提供的移动终端的结构示意图; [0037] 图15为本发明实施例的移动终端的倾斜角度示意图; 和 [0038] 图16A、图16B、图16C、图16D、图16E、图16F和图16G为本发明实施例提供的另一种移动终端屏幕显示控制方法的效果示意图。 具体实施方式 [0039]下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0040] 本说明书中的术语“和/或”仅描述了描述关联对象的关联关系,表示可以存在三种关系。 例如,A和/或B可以表示以下三种情况:只有A存在,A和B都存在,只有B存在。 另外,本说明书中字符“/”一般表示关联对象之间的“或”关系。 实施例一 [0041] 如图1所示,在本发明移动终端屏幕显示控制方法的一个实施例中,该方法可以包括以下步骤。 [0042] 步 101 . 获取移动终端当前的倾斜角度。 [0043] 移动终端当前的倾斜角度可以通过重力传感器、陀螺仪等传感器检测获取。 [0044] 本发明中的移动终端可以是手机、平板电脑、个人数字助理(Personal Digital Assistant,PDA)等带有屏幕的移动终端设备,其中屏幕可以是触摸屏。 [0045] 步 102 . 当确定当前倾斜角度处于第二或第三预设角度范围内时,根据倾斜角度调整移动终端屏幕的界面内容布局。 [0046] 步 103 . 当确定移动终端当前的倾斜角度在第一预设角度范围内时,保持移动终端屏幕已有的界面内容布局,即跳过调整移动终端屏幕当前显示的界面内容布局。 [0047] 第二、第一和第三预设角度范围依次形成连续的角度范围。 [0048] 进一步地,所述根据倾斜角度调整移动终端屏幕的界面内容布局包括根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0049] 进一步地,所述根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容包括:根据倾斜角度确定调整距离,平移或浮动全部或部分界面内容。 移动端屏幕的部分界面内容,其中平移或悬浮的距离为调整距离; 或者,根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容以移动终端屏幕为中心旋转,旋转的角度即为调整角度。 [0050] 进一步的,根据倾斜角度调整移动终端屏幕的界面内容布局还包括根据倾斜角度确定调整方向,在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0051] 进一步地,所述根据倾斜角度确定调整方向包括:当当前倾斜角度在第二预设角度范围内时,确定调整方向为第一方向; 或者,当当前倾斜角度处于第三预设角度范围内时,确定调整方向为第二方向。 [0052] 第一方向可以与第二方向相同,也可以不同,具体可以根据具体情况确定。 [0053] 进一步地,第一预设角度范围为大于等于第一阈值且小于等于第二阈值的角度范围,第一阈值小于第二阈值。 [0054]移动终端当前的倾斜角度可以为锐角或直角,第一阈值大于0度,第二阈值小于或等于90度。 [0055] 例如,第一阈值可以是30度,第二阈值可以是60度。 [0056] 在一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角。 [0057] 在一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值, 确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0058] 可选地,在另一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端的当前倾斜角度小于第一倾斜角度 阈值,确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动; 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上向上平移或悬浮。 [0059] 在另一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角。 [0060] 在一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端当前的倾斜角度小于第一阈值, 确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0061] 可选地,在另一种实施方式中,所述根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局包括:若移动终端的当前倾斜角度小于第一倾斜角度 阈值,确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动; 或者,如果移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0062] 进一步地,该方法还可以包括获取移动终端的环境光强度信息,该移动终端的环境光强度信息可以通过光传感器获取。 [0063] 其中,根据倾斜角度确定调整幅度包括:根据环境光强度信息确定倾斜角度对应的调整幅度。 [0064]进一步地,该方法还可以包括:接收角度范围调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0065] 可以从用户接收关于角度范围调整的信息。 这样,对于不同的用户,可以根据不同用户的实际使用习惯或需求,为不同的用户配置合适的角度范围,并根据合适的角度调整移动终端屏幕的界面内容布局。 角度范围。 这样的调整可以更好地满足用户的实际使用习惯或需求,减少对移动终端屏幕界面内容布局的不必要的调整。 [0066] 进一步可选的,该方法还可以包括接收用户的反馈信息; 其中,根据倾斜角度确定调整幅度可以包括:根据反馈信息确定倾斜角度对应的调整幅度。 [0067] 例如,在调整移动终端屏幕的界面内容布局后,可以接收用户对本次调整的反馈。 例如,用户可以反馈调整大小是否过大或过小,以便根据用户的反馈信息配置调整大小。 [0068] 在本发明中,第一阈值和/或第二阈值可以是移动终端预先设置的,或者是用户设置的,或者是根据用户使用移动终端的情况统计得到的。 对于不同的用户,可以根据不同用户的使用习惯来确定第一阈值和/或第二阈值。 通常,当用户正常手持手机等移动终端时,手机不一定是完全水平或垂直的,而是倾斜一定的角度,手机与水平面和/或 一个垂直平面。 现有技术中,在重力传感器检测到手机不是水平或垂直的所有情况下,确定手机处于倾斜状态,以及当前显示在手机屏幕上的界面内容布局 被调整。 因此,虽然有时手机会倾斜特定角度,但用户是在正常使用手机,调整手机屏幕当前显示的界面内容会影响用户正常使用手机。 本发明通过重力传感器或陀螺仪检测手机当前的倾斜角度。 当手机当前倾斜角度处于用户手持手机的正常角度范围(本实施例中为第一预设角度范围)时,不调整手机屏幕当前显示的界面内容布局,即 更好的满足了用户使用手机的习惯,避免了对手机屏幕当前显示的界面内容布局进行不必要的调整,降低了手机的功耗,提升了手机的用户体验。 当手机当前的倾斜角度超出用户手持手机的正常角度范围(本实施例中为第二或第三预设角度范围)时,根据手机屏幕的界面内容布局进行调整 倾斜角度。 由于第一阈值和第二阈值与用户使用手机的习惯相关,本实施例能够为用户提供更加智能的调整手机屏幕界面内容布局的方法,提供更好的体验。 本公开基于用户使用手机的习惯。 [0069]在本实施例中,以手机为例,手机当前的倾斜角度在用户手持手机的正常角度范围之外,可以是手机当前的倾斜角度小于第一倾斜角度。 阈值或大于第二阈值。 即,手机当前的倾斜角度在用户手持手机的正常角度范围内可以是手机当前的倾斜角度大于或等于第一阈值且小于或等于 到第二个门槛。 [0070] 调整移动终端屏幕的界面内容布局可以包括:将移动终端屏幕的部分或全部界面内容在确定的方向上进行平移或浮动或旋转; 或者将特定区域的界面内容部分从隐藏状态变为显示状态,从显示状态变为隐藏状态等。 浮动可以是指将移动终端屏幕的界面内容中的一个或多个元素从界面上的原位置移动到新的位置,以方便用户操作。 进一步可选的,在用户操作完成后,或者在用户将手机的倾斜角度改变一定程度后,可以将一个或多个元素重新定位回原来的位置。 例如,浮动是指将移动终端屏幕的界面内容中的图标从原来的位置移动到界面上的新位置,以方便用户操作。 可选的,在用户操作完成后,可以将图标重新定位回原来的位置。 在用户看来,该图标似乎漂浮在界面上。 [0071] 本发明实施例将第一预设角度范围作为重力感应的基本水平面(相当于正常使用手机的场合),根据倾斜角度调整手机屏幕的界面内容布局 当手机当前的倾斜角度(例如图3A中手机与水平面的夹角γ)在第一预设角度范围之外时。 如图3A、图4A和图5A所示,图中灰色区域为第一预设角度范围。 [0072] α为第一预设角度范围内的最小角度,即用户正常使用手机时的最小角度,本实施例中的a为第一阈值。 在一个实施例中,a大于0度。 [0073] β为第一预设角度范围内的最大角度,即用户正常使用手机时的最大角度,本实施例中的β为第二阈值。 [0074] γ为手机右视图中手机与水平面的夹角(也可以理解为手机屏幕长度方向与水平面的夹角),本实施例中为 手机当前的倾斜角度。 本发明实施例仅以γ为锐角(或直角)为例进行说明。 也就是说,在本发明实施例中,γ值可以在大于0度且小于等于90度的范围内。 实际上,γ可以是钝角。 当γ为钝角时,参照γ为锐角(或直角)的情况,可作相同或相似的理解。 本发明实施例中,第一预设角度范围可以设置为大于0度且小于等于90度的范围(例如图3A中灰色区域所示的范围为第一预设角度 范围)。 [0075] μ是用户在使用手机的过程中手机可以承受的最小倾斜角度,μ可以大于等于0度,即如果手机倾斜角度小于这个 倾斜角度,用户无法正常查看手机屏幕的界面内容。 [0076] μ2为用户在使用手机的过程中手机最大可承受的倾斜角度,μ2可以小于或等于90度,即如果手机倾斜角度大于此 倾斜角度,用户无法正常查看手机屏幕的界面内容。 [0077] μ和μ2是可选的,以下与μ和μ2相关的内容也是可选的。 μ< a<β<μ 2. [0078] 在本发明实施例中,当手机当前倾斜角度γ在α和β之间时(如图3A所示)或者当手机当前倾斜角度等于α或β时,可以是 本发明实施例考虑到手机的倾斜角度在用户正常使用手机的范围内,手机屏幕的界面内容布局没有发生变化。 当手机的倾斜角度处于用户正常使用手机的范围内时,本发明实施例可以对手机的倾斜角度进行角度转换。 角度转换后(例如,当手机当前倾斜角度γ在α和β之间时,可以将当前倾斜角度γ转换为0度),则可以认为手机的重力感应状态为 平行于水平面(例如本发明实施例中手机倾斜角度在正常范围内时,进行角度转换后的重力感应状态,如图3B所示),而不会产生 重力感应组件,因此不调整手机屏幕的界面内容布局。 [0079] 当手机当前的倾斜角度γ小于α时(如图4A所示),本发明实施例可以认为手机的倾斜角度超出正常使用手机的范围 由用户使用,可能会影响用户正常使用手机。 这种情况下,需要调整手机屏幕的界面内容布局。 调整幅度可以通过以下方式获得。 可以根据手机当前的倾斜角度对倾斜角度进行角度转换处理,得到角度α-γ,并确定角度α-γ对应的调整幅度。 例如,调整幅度可以等于预设的调整系数×(α-γ)。 如图4B所示,虽然手机当前的倾斜角度实际为γ,但是本发明实施例中可以对当前的倾斜角度进行角度转换处理,根据角度α确定调整幅度。 -γ是经过角度转换处理后得到的,避免出现以下情况:当手机倾斜角度γ为α时不进行调整,而当γ略小于α时进行较大幅度的调整。 [0080] 当手机当前的倾斜角度γ大于β且小于μ2时(如图5A所示),本发明实施例可以认为手机的倾斜角度超出正常范围。 用户使用手机但在用户使用手机过程中不超过手机最大可承受倾斜角度。 在这种情况下,由于手机倾斜角度过大,可能会影响用户观看手机屏幕的视线,影响用户正常使用手机,影响用户使用体验。 手机受影响。 需要调整手机屏幕的界面内容布局。 调整幅度可以通过以下方式获得。 可以根据手机当前的倾斜角度对倾斜角度进行角度转换处理,得到角度γ-β,并确定角度γ-β对应的调整幅度。 如图5B所示,虽然手机当前的倾斜角度实际为γ,但是本发明实施例中可以对当前的倾斜角度进行角度转换处理,根据角度γ确定调整幅度。 -β是经过角度转换处理后得到的,以避免出现以下情况:当手机倾斜角度γ为β时不进行调整,而当γ略大于β时进行较大幅度的调整。 [0081]本发明各实施例均以仅以一个预设角度范围(本实施例中为第一预设角度范围)作为重力感应的基本水平面(相当于正常使用手机的场合)为例进行说明。 ,灰色区域为预设角度范围。 在多个预设角度范围作为重力感应的基本水平面的情况下(相当于正常使用手机的场合),如图15所示(显示两个预设角度范围:α1至β1,α2 至β2),可以参照以一个预设角度范围作为重力感应的基本水平面的情况的相关或相似内容来理解。 此时,可以理解为包括本发明实施例中的第一、第二、第三预设角度范围,第二、第一、第三预设角度范围依次形成一个连续的角度范围(例如, 一个连续的角度范围 0 到 α2); 角度范围α2至β2所指示的灰色区域可以理解为本发明实施例在本发明实施例的基础上进一步新增的第四预设角度范围。 [0082] 移动终端屏幕的界面内容部分可以是界面上的至少一个图标、按钮和/或图片等。 [0083] 根据反重力感应原理确定的方向与根据重力感应原理确定的调整方向相反。 反重力感应显示是将移动终端屏幕的全部或部分界面内容向与重力感应相反的方向平移或浮动(例如,根据重力感应原理,当手机向左倾斜时,界面内容 向左平移或悬浮;但根据反重力感应原理,当手机向左倾斜时,界面内容会向右平移或悬浮)。 [0084] 本发明实施例以第一预设角度范围作为重力感应的基本水平面。 当手机当前倾斜角度在第一预设角度范围内时,不启动重力/反重力感应显示,不调整手机屏幕的界面内容布局; 当手机当前倾斜角度大于第一预设角度范围的第二阈值时,若启动重力感应显示,则将手机屏幕的界面内容布局调整为向下/向右。 当手机当前的倾斜角度小于第一预设角度范围的第一阈值时,将手机屏幕的界面内容布局调整为向上/向左方向。 [0085] 如果开启反重力感应显示,则将手机屏幕的界面内容布局调整到与重力感应相反的方向。 [0086] 下面举例说明根据重力感应或反重力感应原理向上或向下平移手机屏幕的整个界面内容的情况。 图6至图10为同一界面内容在手机屏幕上的不同布局。 手机屏幕的界面内容布局可以参考以下方法进行调整。 [0087] (1)首先,利用重力传感器或陀螺仪检测手机在空间中的位置和角度,其中手机与水平面的夹角记为γ。 当然,也可以测量并记录手机与垂直面的夹角(大小可以为90-γ)。 [0088] (2)当γ在预设角度α和β之间时,手机屏幕界面内容布局显示不变,如图6所示。若手机与垂直面夹角90-γ为 测量并记录,可以理解当90-γ在预设角度90-β和90-α之间时,手机屏幕界面内容布局的显示没有变化,下面的描述也可以自适应理解 . [0089](3)当γ在α和β之间的范围之外时,可以启动反重力感应显示或重力感应显示。 即根据基本水平面,将移动终端屏幕的全部或部分界面内容的布局显示调整到与反重力感应或重力感应相同的方向。 [0090] (4)反重力感应显示规则至少包括以下步骤之一。 [0091] (a) 当γ小于a且大于μ时,反重力感应方向向下,手机屏幕界面内容在屏幕上向下偏移。 如图7所示,在屏幕上将手机屏幕的整个界面内容向下移动的过程中,将区域A中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户进行操作。 用户操作A区原本不方便触摸的界面内容。 [0092] (b)可选的,当γ小于或等于μ时,将手机屏幕的界面内容在屏幕上向下移动,直到到达极限位置。 如图8所示,区域A中的界面内容被完全移动到可触摸区域,使得用户更方便地操作区域A中原本不方便触摸的界面内容。当γ小于 或等于μ时,手机屏幕界面内容在屏幕上向下移动,直到到达极限位置,可以避免手机屏幕界面内容因连续减小而无限制移动而影响用户体验 的倾斜角度,进一步提高手机的智能性和易用性。 [0093] (c) 当γ小于μ2且大于β时,反重力感应方向向上,手机屏幕界面内容在屏幕上向上偏移。 如图9所示,将区域C中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户对区域C中原本不方便触摸的界面内容进行操作。 [0094] (d)可选的,当γ大于或等于μ2时,将手机屏幕的界面内容在屏幕上向上移动,直到到达极限位置。 如图10所示,区域C中的界面内容被完全移动到可触摸区域,使得用户更方便地操作区域C中原本不方便触摸的界面内容。当γ大于 或等于μ2时,手机屏幕界面内容在屏幕上向上移动,直到到达极限位置,可以避免手机屏幕界面内容连续增加导致的无限移动影响用户体验 的倾斜角度,进一步提高手机的智能性和易用性。 [0095] (五)重力感应展示规则至少包括以下一项: [0096] (a) 当γ小于a且大于μ时,重力感应方向向上,手机屏幕界面内容在屏幕上向上平移(或平移或浮动)。 如图9所示,将区域C中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户对区域C中原本不方便触摸的界面内容进行操作。 [0097] (b)可选的,当γ小于或等于μ时,将手机屏幕的界面内容在屏幕上向上移动,直到到达极限位置。 如图10所示,将C区的界面内容完全移至可触摸区,使得用户对C区原本不方便触摸的界面内容进行操作更加方便。 [0098](c) 当γ小于μ2且大于β时,重力感应方向向下,手机屏幕界面内容在屏幕上向下偏移。 如图7所示,在屏幕上将手机屏幕的整个界面内容向下移动的过程中,将区域A中的界面内容部分移动到手机屏幕的可触摸区域,可以方便用户的操作。 用户操作A区原本不方便触摸的界面内容。 [0099] (d)可选的,当γ大于或等于μ2时,将手机屏幕的界面内容在屏幕上向下移动,直到到达极限位置。 如图8所示,将A区的界面内容完全移至可触摸区,使得用户对A区原本不方便触摸的界面内容进行操作更加方便。 [0100] 用户在实际使用手机时,可以利用上述规则,根据需要操作的对象所在的区域倾斜手机,从而相应地调整手机屏幕的界面内容,满足操作需求。 用户的。 特别是当用户单手使用手机时,有些区域的物体有时单手难以触摸,可以利用上述规则将手机倾斜,从而相应地调整手机的界面内容 屏幕。 这样,将原本不能单手触摸的物体调整到可以触摸的位置,使得用户可以方便地单手操作该物体,更好地满足了用户的操作需求。 [0101] 上述规则同样适用于手机向左或向右倾斜时对手机屏幕的界面内容进行的调整处理。 手机向上或向下倾斜时所涉及的角度可以是手机屏幕的长度方向与水平面(或竖直面)之间的夹角,手机向左或向右倾斜时所涉及的角度可以是 手机屏幕的宽度方向与水平面(或垂直面)的夹角。 [0102] 在实施例一的基础上,可以根据倾斜角度确定调整角度,可以使移动终端屏幕的界面内容全部或部分以移动终端屏幕为中心旋转,旋转的角度为 调整角度。 进一步的,旋转方向可以根据倾斜角度确定,可以是顺时针方向,也可以是逆时针方向。 [0103]图11为手机屏幕正常显示的界面内容。 当用户在使用手机的过程中将手机倾斜到特定的角度,且手机当前的倾斜角度在预设的角度范围内时,不调整手机屏幕的界面内容布局, 如图12所示,当手机当前倾斜角度超出预设角度范围时,根据重力感应检测到的当前倾斜角度旋转手机屏幕的全部或部分界面内容。 手机(如图13旋转效果示意图)。 旋转的程度或角度与倾斜角度有关。 例如,可以通过预设的算法或公式得到倾斜角度对应的调整幅度(此处为旋转的角度)。 在本发明实施例中,根据手机的倾斜角度,对手机屏幕的界面内容进行全部或部分的旋转。 旋转的角度与倾斜角度相关,并不是每次都以固定的角度在横向和纵向之间切换屏幕(可以理解为固定旋转90度)。 因此,可以更好地满足用户的不同需求。 例如,用户可以更方便地以不同的视角观看手机屏幕的界面内容。 另外,还可以对旋转后的界面内容进行进一步调整,例如将旋转后的界面内容放大或缩小,使人眼看到的界面内容区域为矩形,提供更好的观看效果。 [0104] 下面举例说明如何根据倾斜角度旋转移动终端屏幕的全部或部分界面内容。 [0105] 当手机正常使用时(例如手机当前的倾斜角度在预设范围内时),手机屏幕的界面内容如图16A所示,为横向显示。 当手机当前的倾斜角度如图5A所示时,手机屏幕的界面内容可以逆时针旋转(如图16B和图16C所示,箭头表示旋转方向)。 随着倾斜角度的不断增大,当倾斜角度达到最大倾斜角度(例如μ2)时,手机屏幕的界面内容在旋转后变为垂直显示(如图16D所示)。 当手机当前的倾斜角度如图4A所示时,手机屏幕的界面内容可以顺时针旋转(如图16E和图16F所示)。 随着倾斜角度的不断减小,当倾斜角度达到最小倾斜角度(例如μ)时,手机屏幕的界面内容在旋转后变成倒置显示(如图16G所示)。 实施例二 [0106] 如图2所示,在本发明移动终端屏幕显示控制方法的另一实施例中,该方法包括以下步骤。 [0107] 步 101 . 获取移动终端当前的倾斜角度。 [0108] 步 202 . 在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局。 [0109] 步 203 . 在确定移动终端当前倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕已有的界面内容布局。 第二、第一和第三预设角度范围依次形成连续的角度范围。 [0110] 进一步地,所述根据倾斜角度调整移动终端屏幕的界面内容布局包括根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0111]进一步地,所述根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容包括:根据倾斜角度确定调整距离,平移或浮动全部或部分界面内容。 移动端屏幕的部分界面内容,其中平移或悬浮的距离为调整距离; 或者,根据倾斜角度确定调整角度,将移动终端屏幕的全部或部分界面内容以移动终端屏幕为中心旋转,旋转的角度即为调整角度。 [0112] 进一步的,根据倾斜角度调整移动终端屏幕的界面内容布局还包括根据倾斜角度确定调整方向,在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0113] 进一步地,第一预设角度范围为大于等于第一阈值且小于等于第二阈值的角度范围,第一阈值小于第二阈值。 [0114] 移动终端当前的倾斜角度可以为锐角或直角,第一阈值大于0度,第二阈值小于或等于90度。 [0115] 例如,第一阈值可以是30度,第二阈值可以是60度。 [0116] 在本实施例中,手机当前的倾斜角度在用户手持手机的正常角度范围之外可以是手机当前的倾斜角度在第一阈值和第二阈值之间。 即,手机当前倾斜角度处于用户手持手机的正常角度范围内,可以是手机当前倾斜角度小于第一阈值或大于第二阈值。 [0117] 进一步地,该方法还可以包括获取移动终端的环境光强度信息,该移动终端的环境光强度信息可以通过光传感器获取。 [0118] 其中,根据倾斜角度确定调整幅度包括:根据环境光强度信息确定倾斜角度对应的调整幅度。 [0119] 进一步地,该方法还可以包括:接收角度范围调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0120] 可以从用户接收关于角度范围调整的信息。 这样,对于不同的用户,可以根据不同用户的实际使用习惯或需求,为不同的用户配置合适的角度范围,并根据合适的角度调整移动终端屏幕的界面内容布局。 角度范围。 这样的调整可以更好地满足用户的实际使用习惯或需求,减少对移动终端屏幕界面内容布局的不必要的调整。 [0121] 进一步可选的,该方法还可以包括接收用户的反馈信息; 其中,根据倾斜角度确定调整幅度可以包括:根据反馈信息确定倾斜角度对应的调整幅度。 [0122] 例如,在调整移动终端屏幕的界面内容布局后,可以接收用户对本次调整的反馈。 例如,用户可以反馈调整大小是否过大或过小,以便根据用户的反馈信息配置调整大小。 [0123]在本发明中,第一阈值和/或第二阈值可以是移动终端预先设置的,或者是用户设置的,或者是根据用户使用移动终端的情况统计得到的。 对于不同的用户,可以根据不同用户的使用习惯来确定第一阈值和/或第二阈值。 通常,当用户正常手持手机等移动终端时,手机不一定是完全水平或垂直的,而是倾斜一定的角度,手机与水平面和/或 一个垂直平面。 现有技术中,在重力传感器检测到手机不是水平或垂直的所有情况下,确定手机处于倾斜状态,以及当前显示在手机屏幕上的界面内容布局 被调整。 因此,虽然有时手机会倾斜特定角度,但用户是在正常使用手机,调整手机屏幕当前显示的界面内容会影响用户正常使用手机。 本发明通过重力传感器或陀螺仪检测手机当前的倾斜角度。 当手机当前倾斜角度处于用户手持手机的正常角度范围(本实施例中为第二或第三预设角度范围)时,不调整手机屏幕当前显示的界面内容布局 ,更符合用户使用手机的习惯,避免了对手机屏幕当前显示的界面内容布局进行不必要的调整,降低了手机的功耗,提升了手机的用户体验。 当手机当前的倾斜角度超出用户手持手机的正常角度范围(本实施例中为第一预设角度范围)时,根据倾斜度调整手机屏幕的界面内容布局 角度。 由于第一阈值和第二阈值与用户使用手机的习惯相关,本实施例能够为用户提供更加智能的调整手机屏幕界面内容布局的方法,提供更好的体验。 本公开基于用户使用手机的习惯。 [0124] 本发明实施例中的第一、第二或第三预设角度范围可以与实施例一中的第一、第二或第三预设角度范围相同或不同。 [0125] 本发明实施例中的部分内容可以参见实施例一中的相关部分,这些内容可以有相同或相近的理解,在此不再赘述。 实施例3 [0126] 本发明实施例还提供了一种移动终端。 图14示出了本发明提供的移动终端的一个实施例。 本实施例中,移动终端包括传感器 1401 用于获取移动终端当前的倾斜角度,其中传感器 1401 可以是一个或多个具有相同功能或不同功能的传感器,可以包括重力传感器或陀螺仪传感器,进一步可选地,可以包括光传感器等; 屏幕 1402 用于在移动终端上显示界面内容; 和一个处理器 1403 用于在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第一预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一、第三预设角度范围依次形成连续的角度范围。 [0127] 或者,在另一个实施例-实施例4中,处理器 1403用于在确定当前倾斜角度处于第一预设角度范围内时,根据移动终端的倾斜角度调整移动终端屏幕的界面内容布局; 或者,在确定移动终端当前的倾斜角度处于第二或第三预设角度范围内时,保持移动终端屏幕的界面内容布局,其中,第二、第一和第三预设角度范围依次形成连续的角度范围。 [0128] 可能有一个或多个处理器 1403 例如,可以包括图像处理器。 [0129] 进一步地,移动终端还可以包括存储器 1407 用于存储各种数据或指令,还可以包括接收器 1405 和一个发射器 1406 分别用于接收和发送信号。 [0130] 基于实施例三或四,进一步地,处理器 1403 用于根据倾斜角度调整移动终端屏幕的界面内容布局,包括处理器 1403 具体用于根据倾斜角度确定调整幅度,根据调整幅度调整移动终端屏幕的全部或部分界面内容。 [0131] 基于实施例三或四,进一步地,处理器 1403 用于根据倾斜角度确定调整幅度,并根据调整幅度调整移动终端屏幕的全部或部分界面内容,包括处理器 1403 用于根据倾斜角度确定调整距离,平移或浮动移动终端屏幕的全部或部分界面内容,平移或浮动的距离为调整距离。 或处理器 1403 用于根据倾斜角度确定调整角度,将移动终端屏幕的界面内容全部或部分以移动终端屏幕为中心旋转,旋转的角度为调整角度。 [0132] 基于实施例三或四,进一步地,处理器 1403 用于根据倾斜角度调整移动终端屏幕的界面内容布局还包括处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局。 [0133] 基于实施例三或四,进一步的,所述第一预设角度范围为大于等于第一阈值且小于等于第二阈值的角度范围,所述第一阈值小于第二阈值。 [0134] 移动终端当前的倾斜角度可以为锐角或直角,第一阈值大于0度,第二阈值小于或等于90度。 [0135] 例如,第一阈值可以是30度,第二阈值可以是60度。 [0136] 在实施例三的基础上,进一步地,处理器 1403 处理器用于根据倾斜角度确定调整方向,当当前倾斜角度处于第二预设角度范围内时,确定调整方向为第一方向。 或者,当前倾斜角度在第三预设角度范围内时,确定调整方向为第二方向。 [0137] 基于实施例三,在一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的长度方向与水平面的夹角。 [0138] 在一种实现方式中,处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403用于若移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上平移或向上浮动。 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动。 [0139] 或者, 在另一种实现方式中, 处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403 用于如果移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向下,将移动终端屏幕的界面内容全部或部分在屏幕上向下平移或浮动; 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向上,将移动终端屏幕的界面内容全部或部分在屏幕上平移或悬浮。 [0140] 基于实施例三,在另一个具体实施例中,移动终端的倾斜角度为移动终端屏幕的宽度方向与水平面的夹角。 [0141] 在一种实现方式中,处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403 用于如果移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 或者,若移动终端当前的倾斜角度大于第二阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 [0142] 或者, 在另一种实现方式中, 处理器 1403 用于根据倾斜角度确定调整方向,并在确定的调整方向上调整移动终端屏幕的界面内容布局,包括处理器 1403 用于若移动终端当前的倾斜角度小于第一阈值,则确定调整方向为向左,将移动终端屏幕的全部或部分界面内容在屏幕上向左平移或浮动。 或者,若移动终端当前倾斜角度大于第二阈值,则确定调整方向为向右,将移动终端屏幕的全部或部分界面内容在屏幕上向右平移或浮动。 [0143] 在实施例3或4的基础上,进一步地,传感器 1401 还用于获取移动终端的环境光强度信息; 和处理器 1401 被配置为根据倾斜角度确定调整幅度包括处理器 1401 用于根据环境光强度信息确定倾斜角度对应的调整幅度。 [0144] 基于实施例三或四,进一步地,处理器 1403 还用于接收角度范围调整信息; 根据角度范围调整信息调整第一预设角度范围、第二预设角度范围或第三预设角度范围中的至少一个预设角度范围。 [0145] 需要说明的是,各个装置实施例可以参见对应的方法实施例中的内容,在此不再赘述,方法实施例之间相同或相似的内容互相参见即可 此处不再详述。 [0146]需要说明的是,在本说明书中,第一、第二等关系术语仅用于区分一个实体或操作与另一个实体或操作,并不一定要求或暗示这些实体或操作之间存在任何实际关系或顺序 . 此外,术语“包括”、“包含”或它们的任何其他变体旨在涵盖非排他性的包含,因此包括元素列表的过程、方法、物品或装置不仅包括 这些元素,但也包括未明确列出的其他元素,或进一步包括此类过程、方法、物品或设备固有的元素。 前面带有“的元素包括一个 . . . ” 在没有更多限制的情况下,不排除在包含该元素的过程、方法、物品或设备中存在其他相同元素。 [0147] 本领域普通技术人员可以理解,上述任一实施例所规定的方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在移动终端的闪存或电可擦除可编程只读存储器(EEPROM)等可读取存储介质中。 当程序运行时,程序执行上述全部或部分步骤。 [0148] 在上述具体实施方式中,进一步详细说明了本发明的目的、技术方案和有益效果。 应当理解,可以组合不同的实施例。 以上所述仅为本发明的具体实施方式,并非用于限定本发明的保护范围。 凡在不脱离本发明的精神和原则的情况下,所作的任何组合、修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:57.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104756059A(String), EP3166289A1(String), EP3166289A4(String), KR1020170023198A(String), US20170131793A1(String), WO2016015183A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104756059A(String), EP3166289A1(String), EP3166289A4(String), KR1020170023198A(String), US20170131793A1(String), WO2016015183A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104756059A(String), EP3166289A1(String), EP3166289A4(String), KR1020170023198A(String), US20170131793A1(String), WO2016015183A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271431(Integer), CN104756059A(String), 1048869(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271431(Integer), EP3166289A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271431(Integer), EP3166289A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271431(Integer), KR1020170023198A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271431(Integer), US20170131793A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271431(Integer), WO2016015183A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104756059A(String), CN104756059A(String), 1435680000(Integer), 271431(Integer), 185715(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.385 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185973(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185973(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.567 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185973(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185973(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.671 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.706 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.706 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.706 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185973(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:58.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160192162A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.293 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.293 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Transferring Call on Mobile Terminal, and Mobile Terminal(String), 移动终端呼叫转移的方法及移动终端(String), US20160192162A1(String), A method for transferring a call in a mobile terminal and a mobile terminal thereof, wherein the method includes: a mobile terminal controlling its two communication cards to respectively establish a first call connection and a second call connection; when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection; the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink call connection of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 一种移动终端中呼叫转移的方法及移动终端,该方法包括:移动终端控制其两张通信卡分别建立第一呼叫连接和第二呼叫连接; 移动终端在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行呼叫连接,并屏蔽音频 移动终端中的数据输入/输出单元。(String), US14/910685(String), 1396540800(Integer), US20160192162A1(String), 1467216000(Integer), 美国(String), 2(Integer), CN(String), 3(Integer), 2(Integer), US6606305B1 | US9002364B2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185974(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.478 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d706dd51b4164b9cbc0cee064574f657.png(String), 185974(Integer), d706dd51b4164b9cbc0cee064574f657.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.513 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.514 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.514 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Transferring Call on Mobile Terminal, and Mobile Terminal(String), 移动终端呼叫转移的方法及移动终端(String), US20160192162A1(String), A method for transferring a call in a mobile terminal and a mobile terminal thereof, wherein the method includes: a mobile terminal controlling its two communication cards to respectively establish a first call connection and a second call connection; when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection; the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink call connection of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 一种移动终端中呼叫转移的方法及移动终端,该方法包括:移动终端控制其两张通信卡分别建立第一呼叫连接和第二呼叫连接; 移动终端在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行呼叫连接,并屏蔽音频 移动终端中的数据输入/输出单元。(String), US14/910685(String), 1396540800(Integer), US20160192162A1(String), 1467216000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 3(Integer), 2(Integer), US6606305B1 | US9002364B2(String), \20230420\d706dd51b4164b9cbc0cee064574f657.png(String), 12(Integer), 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 1. A method for transferring a call in a mobile terminal, comprising:a mobile terminal controlling two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection;when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection;the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 1.如权利要求2所述的方法,其中,在移动终端控制移动终端的两个通信卡分别建立第一呼叫连接和第二呼叫连接之后,该方法还包括:移动终端接收到用户通过本终端发送的终止通话指令后,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接;或者当第一呼叫连接终止时,移动终端控制第二呼叫连接断开,或者当第二呼叫连接终止时,移动终端控制第一呼叫连接断开。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 2. The method of claim 1, wherein, before obtaining the downlink channel data of the first call connection and the second call connection, a call state corresponding to the first call connection is a call hold state, a call state corresponding to the second call connection is a call activated state.(String), 12.如权利要求5所述的方法,其中,在控制移动终端的第二通信卡建立第二呼叫连接之后,该方法还包括:移动终端接收到用户通过本终端发送的终止通话指令后,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接;或者移动终端在第一呼叫连接终止时控制断开第二呼叫连接,或者在第二呼叫连接断开时控制第一呼叫连接断开。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 3. The method of claim 1 or 2, wherein, after the mobile terminal controls two communication cards of the mobile terminal to respectively establish the first call connection and the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orwhen the first call connection is terminated, the mobile terminal controlling the second call connection to be disconnected, or when the second call connection is terminated, the mobile terminal controlling the first call connection to be disconnected.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 4. A method for transferring a call in a mobile terminal, comprising:a mobile terminal controlling a first communication card of the mobile terminal to establish a first call connection;when receiving a call transferring instruction, the mobile terminal controlling a second communication card of the mobile terminal to establish a second call connection and obtaining downlink channel data of the first call connection and the second call connection;the mobile terminal taking the obtained downlink channel data of the first call connection as uplink data channel of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal.(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 5. The method of claim 4, wherein, before obtaining the downlink channel data of the first call connection and the second call connection, a call state corresponding to the first call connection and a call state corresponding to the second call connection are call activated states.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 6. The method of claim 4, wherein, after controlling the second communication card of the mobile terminal to establish the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orthe mobile terminal controlling the second call connection to be disconnected when the first call connection is terminated, or controlling the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 7. A mobile terminal for transferring a call in the mobile terminal, comprising:a controlling module, configured to: control two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection;an obtaining module, configured to: upon receiving a call transferring instruction, obtain downlink channel data of the first call connection and the second call connection;a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield an audio data input/output unit in the mobile terminal.(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 8. The mobile terminal of claim 7, wherein, the controlling module is further configured to:upon receiving a call termination instruction sent by a user through a present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orcontrol the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 9. A mobile terminal for transferring a call in the mobile terminal, comprising:a controlling module, configured to: control a first communication card of the mobile terminal to establish a first call connection; and further configured to: control a second communication card of the mobile terminal to establish a second call connection upon receiving a call transferring instruction;an obtaining module, configured to: obtain downlink channel data of the first call connection and the second call connection;a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield an audio data input/output unit in the mobile terminal.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 10. The mobile terminal of claim 9, wherein, the controlling module is further configured to:upon receiving a call termination instruction sent by a user through a present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orcontrol the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 11. The method of claim 2, wherein, after the mobile terminal controls two communication cards of the mobile terminal to respectively establish the first call connection and the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orwhen the first call connection is terminated, the mobile terminal controlling the second call connection to be disconnected, or when the second call connection is terminated, the mobile terminal controlling the first call connection to be disconnected.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185974(Integer), 12. The method of claim 5, wherein, after controlling the second communication card of the mobile terminal to establish the second call connection, the method further comprises:upon receiving a call termination instruction sent by a user through a present terminal, the mobile terminal controlling two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; orthe mobile terminal controlling the second call connection to be disconnected when the first call connection is terminated, or controlling the first call connection to be disconnected when the second call connection is terminated.(String), 1(Integer), 11(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.852 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185974(Integer), TECHNICAL FIELD [0001]The present document relates to the field of communication technologies, and more particularly, to a method for transferring a call on a mobile terminal and a mobile terminal thereof. BACKGROUND OF THE RELATED ART [0002]Although a related dual-card dual-standby dual-pass mobile terminal can achieve a three-party call under two communication cards, when two parties want to talk directly during the call, they must hang up and then call each other directly to talk with each other directly. For example, Xiao Wang establishes a call connection with Xiao Hong via a first communication card, and also establishes a call connection with Xiao Ming via a second communication card, and if Xiao Hong and Xiao Ming want to chat with each other, they can only do so by respectively hanging up the call connections with Xiao Wang and redial each other's phone number to chat, and when the Xiao Hong and Xiao Ming don't hang up the call connections with Xiao Wang respectively, the call of the Xiao Hong and Xiao Ming cannot be directly transferred by Xiao Wang to implement the direct call between the Xiao Hong and Xiao Ming. Also, if Xiao Hong is looking for Xiao Ming through the first card, the terminal may directly dial Xiao Ming's phone number through the second card and directly transfer the call to Xiao Hong without disclosing the Xiao Ming's phone number or hanging up the call. With the increasing number of dual-card dual-standby dual-pass terminals, this call transferring function will become the urgent needs of the users. SUMMARY OF THE INVENTION [0003]The embodiment of the present document is to provide a method for transferring a call on a mobile terminal and the mobile terminal thereof to address the defects that the call transferring function cannot be achieved in an existing mobile terminal. [0004]The embodiment of the present document provides a method for transferring a call in a mobile terminal, comprising: a mobile terminal controlling its two communication cards to respectively establish a first call connection and a second call connection; when receiving a call transferring instruction, the mobile terminal obtaining downlink channel data of the first call connection and the second call connection; [0005]the mobile terminal taking the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and taking the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal. [0006]Preferably, before obtaining the downlink channel data of the first call connection and the second call connection, a call state corresponding to the first call connection is a call hold state, a call state corresponding to the second call connection is a call activated state. [0007]Preferably, after the mobile terminal controls its two communication cards to respectively establish the first call connection and the second call connection, the method further comprises: upon receiving a call termination instruction sent by a user through the present terminal, the mobile terminal controlling its two communication cards to disconnect the established first call connection and second call connection; or when the first call connection is terminated, the mobile terminal controlling the second call connection to be disconnected, or when the second call connection is terminated, the mobile terminal controlling the first call connection to be disconnected. [0008]A method for transferring a call in a mobile terminal, comprising: a mobile terminal controlling its first communication card to establish a first call connection; when receiving a call transferring instruction, the mobile terminal controlling its second communication card to establish a second call connection and obtaining downlink channel data of the first call connection and the second call connection; the mobile terminal taking the obtained downlink channel data of the first call connection as uplink data channel of the second call connection, and taking the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shielding an audio data input/output unit in the mobile terminal. [0009]Preferably, before obtaining the downlink channel data of the first call connection and the second call connection, the call state corresponding to the first call connection and the call state corresponding to the second call connection are the call activated state. [0010]Preferably, after controlling its second communication card to establish the second call connection, the method further comprises: upon receiving a call termination instruction sent by the user through the present terminal, the mobile terminal controlling its two communication cards to disconnect the established first call connection and second call connection; or the mobile terminal controlling the second call connection to be disconnected when the first call connection is terminated, or controlling the first call connection to be disconnected when the second call connection is terminated. [0011]The embodiment of the present document further provides a mobile terminal for transferring a call in the mobile terminal, comprising: [0012]a controlling module, configured to: control two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection; an obtaining module, configured to: upon receiving a call transferring instruction, obtain downlink channel data of the first call connection and the second call connection; a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield an audio data input/output unit in the mobile terminal. [0013]Preferably, the controlling module is further configured to: upon receiving a call termination instruction sent by the user through the present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; or control the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated. [0014]A mobile terminal for transferring a call in the mobile terminal, comprising: a controlling module, configured to: control first communication card of the mobile terminal to establish a first call connection, and further configured to: control second communication card of the mobile terminal to establish a second call connection upon receiving a call transferring instruction; an obtaining module, configured to: obtain downlink channel data of the first call connection and the second call connection; a processing module, configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as uplink data channel of the first call connection, and shield the audio data input/output unit in the mobile terminal. [0015]Preferably, the controlling module is further configured to: upon receiving a call termination instruction sent by a user through the present terminal, control two communication cards of the mobile terminal to disconnect the established first call connection and second call connection; or [0016]control the second call connection to be disconnected when the first call connection is terminated, or control the first call connection to be disconnected when the second call connection is terminated. [0017]The embodiment of the present document can directly perform a call connection on the opposite-end calls through a call transferring method without hanging up the current call connections when two communication cards respectively establish call connections according to user demands, so as to easily, simply and quickly implement the call transferring function in a mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0018]FIG. 1 is a flow chart of an embodiment of a method for transferring a call in a mobile terminal in accordance with an embodiment of the present document; [0019]FIG. 2 is a flow chart of another embodiment of the method for transferring a call in a mobile terminal in accordance with an embodiment of the present document; [0020]FIG. 3 is a functional block diagram of an embodiment of a mobile terminal for transferring a call in a mobile terminal in accordance with an embodiment of the present document; [0021]FIG. 4 is a functional block diagram of another embodiment of the mobile terminal for transferring a call in a mobile terminal in accordance with an embodiment of the present document. PREFERRED EMBODIMENTS OF THE INVENTION [0022]Hereinafter, in conjunction with the accompanying drawings and embodiments, the technical solution of the present document will be further described. It should be understood that the specific embodiments described herein are only intended to explain rather than limit the present document. [0023]FIG. 1 shows a flow chart of an embodiment of the method for transferring a call in a mobile terminal in accordance with an embodiment of the present document. [0024]It should be emphasized that: the flow chart shown in FIG. 1 is only a preferred embodiment, and those skilled in the art should know that any embodiments constructed within the thoughts of the present document should not be departed from the scope covered in the following technical solution: [0025]the method for transferring a call in a mobile terminal provided in the present embodiment comprises: [0026]in step S10, the mobile terminal controls its two communication cards to respectively establish a first call connection and a second call connection; [0027]In the present embodiment, the two communication cards may belong to the same network standard, which can be any one of GSM (Global System Of Mobile Communication), WCDMA (Wideband Code Division Multiple Access), CDMA (Code division Multiple Access), TD-SCDMA (Time division-synchronous Code division Multiple Access) and LTE (long Term Evolution), or may respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the mobile terminal establishes a first call connection through the GSM network standard of the first communication card and establishes a second call connection through the CDMA network standard of the second communication card, or the mobile terminal establishes a first call connection through the GSM network standard of the first communication card, and establishes a second call connection through the GSM network standard of the second communication card. [0028]In step S20, upon receiving a call transferring instruction, the mobile terminal obtains downlink channel data of the first call connection and the second call connection; [0029]upon receiving the call transferring instruction, the mobile terminal has already established two call connections through the two communication cards. The call state corresponding to the first call connection is the call hold state, that is, call waiting state, the call state corresponding to the second call connection is the call activated state, that is, normal call state. According to the user needs, it may also switch between these two states. For example, when the user wants to switch from the call of the second call connection to the first call connection, it transmits a Retrieve instruction to the network side of the first communication card and transmits a Hold instruction to the network side of the second communication card, to retrieve the first call connection of the first communication card; of course, the user can also switch the call of the first call connection to the second call connection, the processing procedure is the same and is not repeated here. [0030]After receiving the call transferring instruction, it sends a Retrieve instruction to the corresponding first communication card or second communication card to enable the first communication card or the second communication card to stay in the call activated state, that is, the normal call state. The mobile terminal obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card. [0031]In step S30, the mobile terminal takes the obtained downlink channel data of the first call connection as the uplink channel data of the second call connection, and takes the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shields the audio data input/output unit in the mobile terminal. [0032]In the GSM and CDMA network standards, for example, the mobile terminal controls its two communication cards to establish the first call connection and the second call connection respectively through the GSM and CDMA networks, upon receiving a call transferring instruction, the mobile terminal takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0033]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0034]Preferably, in the call transferring process, when the mobile terminal receives a call termination instruction sent by the user through the present terminal, the mobile terminal controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the mobile terminal controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the mobile terminal controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0035]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0036]The present embodiment can directly perform a call connection on the opposite-end calls through a call transferring method without hanging up the current call connections when two communication cards respectively establish call connections according to user demands, so as to easily, simply and quickly implement the call transferring function in a mobile terminal. [0037]FIG. 2 shows a flow chart of another embodiment of the method for transferring a call in a mobile terminal in accordance with an embodiment of the present document. [0038]It should be emphasized that: the flow chart shown in FIG. 2 is only a preferred embodiment, and those skilled in the art should know that any embodiments constructed within the thoughts of the present document should not be departed from the scope covered in the following technical solution: [0039]The method for transferring a call in a mobile terminal provided in the present embodiment comprises: [0040]in step S110, the mobile terminal controls its first communication card to establish a first call connection; [0041]in step S120, the mobile terminal controls its second communication card to establish a second call connection when receiving a call transferring instruction, and obtains the downlink channel data of the first call connection and the second call connection; [0042]in the present embodiment, the first communication card and the second communication card may belong to the same network standard, which can be any one of GSM (Global System Of Mobile Communication), WCDMA (Wideband Code Division Multiple Access), CDMA (Code division Multiple Access), TD-SCDMA (Time division-synchronous Code division Multiple Access) and LTE (long Term Evolution), or respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the mobile terminal establishes a first call connection through the GSM network standard of the first communication card and the mobile terminal establishes a second call connection through the CDMA network standard of the second communication card when receiving a call transferring instruction, or the mobile terminal establishes a first call connection through the GSM network standard of the first communication card, and the mobile terminal establishes a second call connection through the GSM network standard of the second communication card when receiving a call transferring instruction. [0043]The mobile terminal controls its first communication card to establish a first call connection; upon receiving the call transferring instruction, the mobile terminal controls its second communication card to establish a second call connection. In this case the mobile terminal has already established two call connections through the first communication card and the second communication card respectively. The call state corresponding to the first call connection and the call state corresponding to the second call connection are the call activated state, that is, the normal call state. [0044]When the mobile terminal controls its second communication card to establish the second call connection, the mobile terminal obtains the downlink channel data of the first call connection established through the first communication card as well as the downlink channel data of the second call connection established through the second communication card. [0045]In step S130, the mobile terminal takes the obtained downlink channel data of the first call connection as the uplink channel data of the second call connection and the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shields the audio data input/output unit in the mobile terminal. [0046]In the GSM and CDMA network standards, for example, the mobile terminal controls its first communication card to establish the first call connection through the GSM network, and controls its second communication card to establish the second call connection through the CDMA network when receiving a call transferring instruction, and it obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card; the mobile terminal takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0047]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0048]Furthermore, in the call transferring process, when the mobile terminal receives a call termination instruction sent by the user through the present terminal, the mobile terminal controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the mobile terminal controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the mobile terminal controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0049]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0050]FIG. 3 shows a functional block diagram of an embodiment of the mobile terminal for transferring a call in a mobile terminal in accordance with the present document. The mobile terminal 1 provided in the present embodiment comprises: [0051]a controlling module 10, used to control two communication cards of the mobile terminal to respectively establish a first call connection and a second call connection; [0052]In the present embodiment, the two communication cards may belong to the same network standard, which can be any one of GSM, WCDMA, CDMA, TD-SCDMA and LTE, or respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the controlling module 10 establishes a first call connection through the GSM network standard of the first communication card and establishes a second call connection through the CDMA network standard of the second communication card, or the controlling module 10 establishes the first call connection through the GSM network standard of the first communication card, and establishes the second call connection through the GSM network standard of the second communication card. [0053]An obtaining module 20 is configured to, upon receiving a call transferring instruction, obtain downlink channel data of the first call connection and the second call connection; [0054]upon receiving the call transferring instruction, the controlling module 10 has already established two call connections through the two communication cards. The call state corresponding to the first call connection is the call hold state, that is, the call waiting state, and the call state corresponding to the second call connection is the call activated state, that is, the normal call state. According to the user needs, it can also switch between these two states. For example, when the user wants to switch from the call of the second call connection to the first call connection, it transmits a Retrieve instruction to the network side of the first communication card and transmits a Hold instruction to the network side of the second communication card to retrieve the first call connection of the first communication card; of course, the user can also switch the call of the first call connection to the second call connection, the processing procedure is same and is not repeated here. [0055]After receiving the call transferring instruction, it is to send a Retrieve instruction to the corresponding first communication card or second communication card to enable the first communication card or second communication card to stay in the call activated state, that is the normal call state. The obtaining module 20 obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card. [0056]A processing module 30 is configured to: take the obtained downlink channel data of the first call connection as uplink channel data of the second call connection and the obtained downlink channel data of the second call connection as uplink channel data of the first call connection, and shield the audio data input/output unit in the mobile terminal. [0057]In the GSM and CDMA network standards, for example, the controlling module 10 controls two communication cards of the mobile terminal to respectively establish the first call connection and the second call connection through the GSM and CDMA networks, and upon receiving a call transferring instruction, the processing module 30 takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0058]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0059]Preferably, in the call transferring process, when the controlling module 10 receives a call termination instruction sent by the user through the present terminal, the controlling module 10 controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the controlling module 10 controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the controlling module 10 controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0060]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0061]The embodiment of the present document can directly perform a call connection on the opposite-end calls through a call transferring method without hanging up the current call connections when two communication cards respectively establish call connections according to user demands, so as to easily, simply and quickly implement the call transferring function in a mobile terminal. [0062]FIG. 4 shows a functional block diagram of another embodiment of the mobile terminal for transferring a call in a mobile terminal in accordance with an embodiment of the present document. The mobile terminal 2 provided in the present embodiment comprises: [0063]a controlling module 110, configured to: control a first communication card of the mobile terminal to establish a first call connection; and also used to control a second communication card of the mobile terminal to establish a second call connection when receiving a call transferring instruction, [0064]an obtaining module 120, configured to: obtain downlink channel data of the first call connection and the second call connection;[0065]in the present embodiment, the first communication card and the second communication card may belong to the same network standard, which can be any one of GSM, WCDMA, CDMA, TD-SCDMA and LTE, or respectively belong to any two of the GSM, the CDMA, the WCDMA, the TD-SCDMA and the LTE. For example, the controlling module 110 establishes a first call connection through the GSM network standard of the first communication card, and the controlling module 110 establishes a second call connection through the CDMA network standard of the second communication card when receiving a call transferring instruction, or the controlling module 110 establishes the first call connection through the GSM network standard of the first communication card, and the controlling module 110 establishes the second call connection through the GSM network standard of the second communication card when receiving a call transferring instruction. [0066]The controlling module 110 controls the first communication card of the mobile terminal to establish a first call connection; upon receiving a call transferring instruction, the controlling module 110 controls the second communication card of the mobile terminal to establish a second call connection. In this case the controlling module 110 has already established two call connections through the first communication card and the second communication card respectively. The call state corresponding to the first call connection and the call state corresponding to the second call connection are the call activated state, that is, the normal call state. [0067]When the controlling module 110 controls the second communication card of the mobile terminal to establish the second call connection, the obtaining module 120 obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card. [0068]A processing module 130 is configured to: take the obtained downlink channel data of the first call connection as the uplink channel data of the second call connection, and take the obtained downlink channel data of the second call connection as the uplink channel data of the first call connection, and shield the audio data input/output unit in the mobile terminal. [0069]In the GSM and CDMA network standards, for example, the controlling module 110 controls its first communication card to establish the first call connection through the GSM network, and the controlling module 110 controls its second communication card to establish the second call connection through the CDMA network, and the obtaining module 120 obtains the downlink channel data of the first call connection established through the first communication card and the downlink channel data of the second call connection established through the second communication card; the processing module 130 takes the downlink channel data received from the GSM network side as uplink channel data of the CDMA network side to transmit, and takes the downlink channel data received from the CDMA network side as uplink channel data of the GSM network side to transmit. [0070]The audio data input/output unit is in the shielded state, that is, it does not perform any data processing, which well protects the privacy of the opposite-end of call transferring. The audio data input/output unit comprises: Mic (Microphone), Receiver, Speaker and other audio data input/output units with the same function. [0071]Preferably, in the call transferring process, when the controlling module 110 receives a call termination instruction sent by the user through the present terminal, the controlling module 110 controls the first communication card and the second communication card to disconnect the established first call connection and second call connection; or the controlling module 10 controls the second call connection of the second communication card to be disconnected when the first call connection of the first communication card is terminated, or the controlling module 10 controls the first call connection of the first communication card to be disconnected when the second call connection is terminated. [0072]In order to facilitate the implementation of the call transferring in the dual-card single-network mode or the dual-card dual-network mode, two sets of baseband radio frequency provided in the embodiment of the present document can process the uplink channel data of the calls respectively established through two communication cards without performing any changes to the network side. [0073]The above description is preferred embodiments of the present document and is not intended to limit the patent scope of the embodiments of the present document, any equivalent structure transformations made by using the contents of the specification and the accompanying drawings of the present document, or directly or indirectly used in other related technical fields, should similarly be included in the patent protection scope of the embodiments of the present document. INDUSTRIAL APPLICABILITY [0074]The embodiment of the present document can directly perform(String), 技术领域 [0001] 本 发明涉及通信技术领域,尤其涉及一种移动终端呼叫转移的方法及移动终端。 相关技术背景 [0002] 虽然相关的双卡双待双通移动终端可以实现两张通讯卡下的三方通话,但是当通话中双方想直接通话时,必须先挂机再直接呼叫对方通话。 直接互相 例如,小王通过第一通讯卡与小红建立通话连接,也通过第二通讯卡与小明建立通话连接,如果小红和小明要聊天,只能 分别挂断与小王的通话连接并重拨对方的电话号码进行聊天,当小红和小明分别没有挂断与小王的通话连接时,小红和小明的通话 小王不能直接调用小明实现小红和小明之间的直接通话。 另外,如果小红通过第一张卡寻找小明,则终端可以通过第二张卡直接拨打小明的电话号码,直接将电话转给小红,而不会泄露小明的电话号码,也不会挂断电话。 随着双卡双待双通终端越来越多,这种呼叫转移功能将成为用户的迫切需求。 发明内容 [0003] 本发明实施例旨在提供一种移动终端来电转接的方法及其移动终端,以解决现有移动终端无法实现来电转接功能的缺陷。 [0004] 本发明实施例提供了一种移动终端中呼叫转移的方法,包括: 移动终端控制其两块通信卡分别建立第一呼叫连接和第二呼叫连接; 当接收到呼叫转移指令时,移动终端获取第一呼叫连接和第二呼叫连接的下行信道数据; [0005] 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,并将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,并屏蔽音频 移动终端中的数据输入/输出单元。 [0006] 优选地,在获取第一呼叫连接和第二呼叫连接的下行信道数据之前,第一呼叫连接对应的呼叫状态为呼叫保持状态,第二呼叫连接对应的呼叫状态为呼叫激活状态。 [0007] 优选地,所述移动终端控制其两块通信卡分别建立第一呼叫连接和第二呼叫连接之后,所述方法还包括: 移动终端接收到用户通过本终端发送的终止呼叫指令后,控制其两块通信卡。 通信卡断开已建立的第一呼叫连接和第二呼叫连接; 或者,当第一呼叫连接终止时,移动终端控制断开第二呼叫连接,或者当第二呼叫连接终止时,移动终端控制第一呼叫连接断开。 [0008]一种移动终端呼叫转移的方法,包括: 移动终端控制其第一通信卡建立第一呼叫连接; 当移动终端接收到呼叫转移指令时,移动终端控制其第二通信卡建立第二呼叫连接,并获取第一呼叫连接和第二呼叫连接的下行信道数据; 移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行数据信道,并将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,屏蔽 移动终端中的音频数据输入/输出单元。 [0009] 优选地,在获取第一呼叫连接和第二呼叫连接的下行信道数据之前,第一呼叫连接对应的呼叫状态和第二呼叫连接对应的呼叫状态为呼叫激活状态。 [0010] 优选地,在控制自身的第二通信卡建立第二呼叫连接之后,所述方法还包括: 移动终端接收到用户通过本终端发送的终止呼叫指令后,控制自身的两个通信卡断开建立的第一呼叫连接。 和第二呼叫连接; 或者,移动终端在第一呼叫连接终止时控制断开第二呼叫连接,或者在第二呼叫连接断开时控制第一呼叫连接断开。 [0011] 本发明实施例还提供了一种移动终端,用于移动终端中的呼叫转移,包括: [0012] 控制模块,用于控制移动终端的两个通信卡分别建立第一呼叫连接和第二呼叫连接; 获取模块,用于在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; 处理模块,用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行数据信道, 屏蔽移动终端中的音频数据输入/输出单元。 [0013] 优选地,所述控制模块,还用于在接收到用户通过本终端发送的终止通话指令时,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接。 或者在第一呼叫连接终止时控制第二呼叫连接断开,或者在第二呼叫连接终止时控制第一呼叫连接断开。 [0014] 一种移动终端,用于在移动终端中转移呼叫,包括: 控制模块,用于控制移动终端的第一通信卡建立第一呼叫连接,还用于控制移动终端的第二通信卡建立第一呼叫连接。 接收到呼叫转移指令后建立第二呼叫连接; 获取模块,用于获取第一呼叫连接和第二呼叫连接的下行信道数据; 处理模块,用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行数据信道, 屏蔽移动终端中的音频数据输入/输出单元。 [0015] 优选地,所述控制模块,还用于在接收到用户通过本终端发送的通话结束指令时,控制移动终端的两个通信卡断开已建立的第一通话连接和第二通话连接。 或者 [0016] 在第一呼叫连接终止时控制第二呼叫连接断开,或者在第二呼叫连接终止时控制第一呼叫连接断开。 [0017] 本发明实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接与对端呼叫进行呼叫连接,而无需挂断当前的呼叫连接,实现了简单、方便、快捷的目的。 快速实现移动终端的呼叫转移功能。 附图的简要说明 [0018] 图1为本发明实施例提供的移动终端来电转移方法实施例的流程图; [0019] 图2为本发明实施例提供的移动终端来电转移方法另一实施例的流程图。 [0020] 图3是本发明实施例的移动终端中呼叫转移的实施例的功能框图; [0021] 图4是根据本发明实施例的移动终端中用于转移呼叫的移动终端的另一个实施例的功能框图。 本发明的优选实施例 [0022] 下面结合附图及实施例,对本发明的技术方案作进一步说明。 应当理解,此处所描述的具体实施例仅仅用于解释,并不用于限制本发明。 [0023] 图1示出了根据本发明实施例的移动终端中呼叫转移方法的一个实施例的流程图。 [0024] 需要强调的是:图1所示的流程图仅为一个优选实施例,本领域的技术人员应当知晓,任何在本文档思想构思内所构筑的实施例都不应该脱离以下技术所涵盖的范围 解决方案: [0025] 本实施例提供的移动终端中的呼叫转移方法包括: [0026] 在步骤S 10 ,移动终端控制其两块通信卡分别建立第一通话连接和第二通话连接; [0027] 在本实施例中,两块通信卡可以属于同一网络制式,可以是GSM(全球移动通信系统)、WCDMA(宽带码分多址)、CDMA(码分多址)、TD中的任意一种。 -SCDMA(时分同步码分多址)和LTE(长期演进),或者可以分别属于GSM、CDMA、WCDMA、TD-SCDMA和LTE中的任意两个。 例如,移动终端通过第一通信卡的GSM网络制式建立第一呼叫连接,通过第二通信卡的CDMA网络制式建立第二呼叫连接,或者移动终端通过GSM建立第一呼叫连接 第一通信卡的网络制式,通过第二通信卡的GSM网络制式建立第二通话连接。 [0028] 在步骤S 20 、移动终端接收到呼叫转移指令后,获取第一呼叫连接和第二呼叫连接的下行信道数据; [0029]移动终端在接收到呼叫转移指令后,已经通过两张通信卡建立了两条呼叫连接。 第一呼叫连接对应的呼叫状态为呼叫保持状态,即呼叫等待状态,第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 根据用户需要,还可以在这两种状态之间切换。 例如,当用户想从第二呼叫连接的呼叫切换到第一呼叫连接时,向第一通信卡的网络侧发送Retrieve指令,向第二通信的网络侧发送Hold指令 card,获取第一通信卡的第一通话连接; 当然,用户也可以将第一呼叫连接的呼叫切换到第二呼叫连接,处理过程相同,此处不再赘述。 [0030] 接收到呼叫转移指令后,向对应的第一通信卡或第二通信卡发送Retrieve指令,使第一通信卡或第二通信卡保持呼叫激活状态,即正常呼叫状态。 移动终端获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据。 [0031] 在步骤S 30 ,移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,以及 屏蔽移动终端中的音频数据输入/输出单元。 [0032] 例如,在GSM和CDMA网络制式中,移动终端通过GSM和CDMA网络控制自己的两块通信卡分别建立第一呼叫连接和第二呼叫连接,当移动终端收到呼叫转移指令时,移动终端接 将从GSM网络侧接收的下行信道数据作为CDMA网络侧的上行信道数据进行传输,将从CDMA网络侧接收的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0033] 音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0034] 优选地,在呼叫转移过程中,当移动终端接收到用户通过本终端发送的终止呼叫指令时,移动终端控制第一通信卡和第二通信卡断开已建立的第一呼叫连接和第二呼叫连接。 ; 或者移动终端在第一通信卡的第一呼叫连接终止时控制第二通信卡的第二呼叫连接断开,或者移动终端在第二通信卡的第一呼叫连接断开时控制第一通信卡的第一呼叫连接断开。 呼叫连接终止。 [0035] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0036] 本实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接对对端呼叫进行呼叫连接,而无需挂断当前呼叫连接,从而方便、简单、快速地实现。 移动终端中的呼叫转移功能。 [0037]图2示出了根据本发明实施例的移动终端中呼叫转移方法的另一个实施例的流程图。 [0038] 需要强调的是:图2所示的流程图仅为一个较佳实施例,本领域的技术人员应该知晓,任何在本文档思想构思下所构筑的实施例都不应脱离以下技术所涵盖的范围 解决方案: [0039] 本实施例提供的移动终端中的呼叫转移方法包括: [0040] 在步骤S 110 ,移动终端控制其第一通信卡建立第一呼叫连接; [0041] 在步骤S 120 、移动终端在接收到呼叫转移指令时控制其第二通信卡建立第二呼叫连接,并获取第一呼叫连接和第二呼叫连接的下行信道数据; [0042] 在本实施例中,第一通信卡和第二通信卡可以属于同一网络制式,可以是GSM(全球移动通信系统)、WCDMA(宽带码分多址)、CDMA(码分 Multiple Access)、TD-SCDMA(Time Division-Synchronous Code Division Multiple Access)和LTE(Long Term Evolution),或者分别属于GSM、CDMA、WCDMA、TD-SCDMA和LTE中的任意两个。 例如,移动终端在接收到呼叫转移指令时,通过第一通信卡的GSM网络制式建立第一呼叫连接,移动终端通过第二通信卡的CDMA网络制式建立第二呼叫连接,或者移动终端 终端通过第一通信卡的GSM网络制式建立第一呼叫连接,移动终端在接收到呼叫转移指令时通过第二通信卡的GSM网络制式建立第二呼叫连接。 [0043] 移动终端控制其第一通信卡建立第一呼叫连接; 移动终端接收到呼叫转移指令后,控制其第二通信卡建立第二呼叫连接。 此时移动终端已经分别通过第一通信卡和第二通信卡建立了两个通话连接。 第一呼叫连接对应的呼叫状态和第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 [0044] 当移动终端控制其第二通信卡建立第二呼叫连接时,移动终端获取通过第一通信卡建立的第一呼叫连接的下行信道数据以及通过第二通信卡建立的第二呼叫连接的下行信道数据。 第二张通讯卡。 [0045] 在步骤S 130 ,移动终端将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,屏蔽 移动终端中的音频数据输入/输出单元。 [0046] 例如,在GSM和CDMA网络制式中,移动终端在接到电话时控制自己的第一通信卡通过GSM网络建立第一呼叫连接,控制第二通信卡通过CDMA网络建立第二呼叫连接 传递指令,获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据; 移动终端将从GSM网络侧接收到的下行信道数据作为CDMA网络侧的上行信道数据进行传输,并将从CDMA网络侧接收到的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0047]音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0048] 进一步地,在呼叫转移过程中,当移动终端接收到用户通过本终端发送的终止呼叫指令时,移动终端控制第一通信卡和第二通信卡断开已建立的第一呼叫连接和第二呼叫连接。 ; 或者移动终端在第一通信卡的第一呼叫连接终止时控制第二通信卡的第二呼叫连接断开,或者移动终端在第二通信卡的第一呼叫连接断开时控制第一通信卡的第一呼叫连接断开。 呼叫连接终止。 [0049] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0050] 图3示出了根据本文档的用于在移动终端中转移呼叫的移动终端的实施例的功能框图。 移动端 1 本实施例提供的包括: [0051] 一个控制模块 10 ,用于控制移动终端的两个通信卡分别建立第一呼叫连接和第二呼叫连接; [0052] 在本实施例中,两块通信卡可以属于同一网络制式,可以是GSM、WCDMA、CDMA、TD-SCDMA和LTE中的任意一种,也可以分别属于GSM、CDMA、WCDMA中的任意两种。 、TD-SCDMA 和 LTE。 例如,控制模块 10 通过第一通信卡的GSM网络制式建立第一呼叫连接,通过第二通信卡的CDMA网络制式建立第二呼叫连接,或控制模块 10 通过第一通信卡的GSM网络制式建立第一呼叫连接,通过第二通信卡的GSM网络制式建立第二呼叫连接。 [0053] 获取模块 20 用于在接收到呼叫转移指令时,获取第一呼叫连接和第二呼叫连接的下行信道数据; [0054] 控制模块收到呼叫转移指令后, 10 已经通过两张通讯卡建立了两条通话连接。 第一呼叫连接对应的呼叫状态为呼叫保持状态,即呼叫等待状态,第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 根据用户需要,还可以在这两种状态之间切换。 例如,当用户想从第二呼叫连接的呼叫切换到第一呼叫连接时,向第一通信卡的网络侧发送Retrieve指令,向第二通信的网络侧发送Hold指令 卡取回第一通信卡的第一通话连接; 当然,用户也可以将第一呼叫连接的呼叫切换到第二呼叫连接,处理过程相同,此处不再赘述。 [0055] 接收到呼叫转移指令后,向对应的第一通信卡或第二通信卡发送Retrieve指令,使第一通信卡或第二通信卡保持呼叫激活状态,即正常呼叫状态。 获取模块 20获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据。 [0056] 一个处理模块 30 用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据,并对音频数据进行屏蔽 移动终端中的输入/输出单元。 [0057] 在GSM和CDMA网络标准中,例如,控制模块 10 控制移动终端的两个通信卡分别通过GSM和CDMA网络建立第一呼叫连接和第二呼叫连接,处理模块接收到呼叫转移指令后, 30 将从GSM网络侧接收到的下行信道数据作为CDMA网络侧的上行信道数据进行传输,将从CDMA网络侧接收到的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0058] 音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0059] 优选地,在呼叫转移过程中,当控制模块 10 控制模块接收用户通过本终端发送的通话结束指令, 10 控制第一通信卡和第二通信卡断开已建立的第一通话连接和第二通话连接; 或控制模块 10 当第一通信卡的第一呼叫连接终止时,控制第二通信卡的第二呼叫连接断开,或者控制模块 10 当第二通话连接终止时,控制第一通信卡的第一通话连接断开。 [0060] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0061] 本发明实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接与对端呼叫进行呼叫连接,而无需挂断当前的呼叫连接,实现了简单、方便、快捷的目的。 快速实现移动终端的呼叫转移功能。 [0062] 图4示出了根据本发明实施例的移动终端中用于转移呼叫的移动终端的另一个实施例的功能框图。 移动端 2 本实施例提供的包括: [0063] 一个控制模块 110 , 用于控制移动终端的第一通信卡建立第一呼叫连接; 还用于在接收到呼叫转移指令时,控制移动终端的第二通信卡建立第二呼叫连接, [0064] 获取模块 120 ,用于获取第一呼叫连接和第二呼叫连接的下行信道数据; [0065]本实施例中,第一通信卡和第二通信卡可以属于同一网络制式,可以是GSM、WCDMA、CDMA、TD-SCDMA和LTE中的任意一种,也可以分别属于GSM中的任意两种, CDMA、WCDMA、TD-SCDMA和LTE。 例如,控制模块 110 通过第一通信卡的GSM网络制式建立第一通话连接,控制模块 110 接收到呼叫转移指令时,通过第二通信卡的CDMA网络制式建立第二呼叫连接,或者控制模块 110 通过第一通信卡的GSM网络标准建立第一通话连接,控制模块 110 接收到呼叫转移指令时,通过第二通信卡的GSM网络制式建立第二呼叫连接。 [0066] 控制模块 110 控制移动终端的第一通信卡建立第一呼叫连接; 控制模块收到呼叫转移指令后, 110 控制移动终端的第二通信卡建立第二呼叫连接。 在这种情况下,控制模块 110已经分别通过第一通讯卡和第二通讯卡建立了两个通话连接。 第一呼叫连接对应的呼叫状态和第二呼叫连接对应的呼叫状态为呼叫激活状态,即正常呼叫状态。 [0067] 当控制模块 110 控制移动终端的第二通信卡建立第二呼叫连接,获取模块 120 获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据。 [0068] 一个处理模块 130 用于将获取的第一呼叫连接的下行信道数据作为第二呼叫连接的上行信道数据,将获取的第二呼叫连接的下行信道数据作为第一呼叫连接的上行信道数据, 屏蔽移动终端中的音频数据输入/输出单元。 [0069] 在GSM和CDMA网络标准中,例如,控制模块 110 控制其第一通信卡通过GSM网络建立第一通话连接,控制模块 110 控制其第二通信卡通过CDMA网络建立第二呼叫连接,获取模块 120 获取通过第一通信卡建立的第一呼叫连接的下行信道数据和通过第二通信卡建立的第二呼叫连接的下行信道数据; 处理模块 130 将从GSM网络侧接收到的下行信道数据作为CDMA网络侧的上行信道数据进行传输,将从CDMA网络侧接收到的下行信道数据作为GSM网络侧的上行信道数据进行传输。 [0070] 音频数据输入/输出单元处于屏蔽状态,即不进行任何数据处理,很好地保护了呼叫转移对端的隐私。 音频数据输入/输出单元包括:Mic(麦克风)、Receiver、Speaker和其他具有相同功能的音频数据输入/输出单元。 [0071] 优选地,在呼叫转移过程中,当控制模块 110 控制模块接收用户通过本终端发送的通话结束指令, 110 控制第一通信卡和第二通信卡断开已建立的第一通话连接和第二通话连接; 或控制模块 10 当第一通信卡的第一呼叫连接终止时,控制第二通信卡的第二呼叫连接断开,或者控制模块 10 当第二通话连接终止时,控制第一通信卡的第一通话连接断开。 [0072] 为了便于实现双卡单网或双卡双网模式下的呼叫转移,本发明实施例提供的两组基带射频可以处理上行信道数据。 在不对网络侧做任何改变的情况下,分别通过两块通信卡建立呼叫。 [0073] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明实施例的专利范围,任何利用本发明说明书内容及附图所作的等同结构变换,或者直接 或者间接用于其他相关技术领域,同样应当包含在本发明实施例的专利保护范围内。 工业实用性 [0074]本发明实施例可以在两块通信卡根据用户需求分别建立呼叫连接时,通过呼叫转移的方法直接与对端呼叫进行呼叫连接,而无需挂断当前的呼叫连接,实现了简单、方便、快捷的目的。 快速实现移动终端的呼叫转移功能。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:34:59.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104378748A(String), US20160192162A1(String), WO2014169764A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104378748A(String), US20160192162A1(String), WO2014169764A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104378748A(String), US20160192162A1(String), WO2014169764A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271177(Integer), CN104378748A(String), 1048179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.135 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.135 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.135 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271177(Integer), US20160192162A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271177(Integer), WO2014169764A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104378748A(String), CN104378748A(String), 1424793600(Integer), 271177(Integer), 185461(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185974(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185974(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185974(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185974(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.507 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.507 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:00.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10827055B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for obtaining event information on mobile terminal and mobile terminal(String), 移动终端获取事件信息的方法及移动终端(String), US10827055B2(String), This application provides a mobile terminal and a method for obtaining event information on a mobile terminal, so as to automatically add a plurality of pieces of classifiable information in an event notification message to an application, thereby improving addition efficiency. The method includes: receiving, by a mobile terminal, an event notification message of a first application; obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template; determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule; and adding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to the m class attributes in the second application.(String), 本申请提供一种移动终端及获取移动终端事件信息的方法,以自动将事件通知消息中的多条可分类信息添加到应用程序中,提高添加效率。 该方法包括:移动终端接收第一应用的事件通知消息; 移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息; 移动终端根据预设规则,根据n个类属性确定第二应用程序; 移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m个类属性中。(String), US16/456951(String), 1561651200(Integer), US10827055B2(String), 1604332800(Integer), 1604332800(Integer), 美国(String), 4(Integer), CN(String), 3(Integer), 20(Integer), CN103221948A | CN103325031A | CN104750357A | CN104980549A | CN105227572A | CN105657158A | CN105898721A | CN106686240A | EP1965594A1 | JP2007317190A | JP2009137193A | US20040196866A1 | US20070271293A1 | US20090068990A1 | US20120226753A1 | US20120289206A1 | US20130145024A1 | US20150304425A1 | US20170126609A1 | WO2009030769A2(String), 5(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185975(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e6efab3f8a15433c976bcc612d369f8b.png(String), 185975(Integer), e6efab3f8a15433c976bcc612d369f8b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for obtaining event information on mobile terminal and mobile terminal(String), 移动终端获取事件信息的方法及移动终端(String), US10827055B2(String), This application provides a mobile terminal and a method for obtaining event information on a mobile terminal, so as to automatically add a plurality of pieces of classifiable information in an event notification message to an application, thereby improving addition efficiency. The method includes: receiving, by a mobile terminal, an event notification message of a first application; obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template; determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule; and adding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to the m class attributes in the second application.(String), 本申请提供一种移动终端及获取移动终端事件信息的方法,以自动将事件通知消息中的多条可分类信息添加到应用程序中,提高添加效率。 该方法包括:移动终端接收第一应用的事件通知消息; 移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息; 移动终端根据预设规则,根据n个类属性确定第二应用程序; 移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m个类属性中。(String), US16/456951(String), 1561651200(Integer), US10827055B2(String), 1604332800(Integer), 1604332800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 3(Integer), 20(Integer), CN103221948A | CN103325031A | CN104750357A | CN104980549A | CN105227572A | CN105657158A | CN105898721A | CN106686240A | EP1965594A1 | JP2007317190A | JP2009137193A | US20040196866A1 | US20070271293A1 | US20090068990A1 | US20120226753A1 | US20120289206A1 | US20130145024A1 | US20150304425A1 | US20170126609A1 | WO2009030769A2(String), \20230420\e6efab3f8a15433c976bcc612d369f8b.png(String), 5(Integer), 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185975(Integer), 1. A method, comprising:receiving, by a mobile terminal, an event notification message of a first application;obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template, wherein the n pieces of classifiable information correspond to n class attributes, the predefined class template comprises a classification relationship between classifiable information and a particular class attribute, and n is an integer greater than 2;determining a plurality of target applications of the mobile terminal based on then class attributes, wherein each target application of the plurality of target applications comprises at least one class attribute in then class attributes;determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule, wherein the second application comprises m class attributes, a set that comprises them class attributes is a subset of a set that comprises then class attributes, and m is an integer greater than or equal to 2 and less than n; andadding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to them class attributes in the second application, wherein them pieces of classifiable information correspond to them class attributes in the second applicationwherein the determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule comprises:determining, by the mobile terminal from the plurality of target applications, a particular application that comprises the greatest number of attributes in then class attributes, to serve as the second application.(String), 1.一种方法,包括:移动终端接收第一应用的事件通知消息;移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息,其中,n条可分类信息对应n个类属性,预定义的类模板包括可分类信息与类属性之间的分类关系。特定类属性,n为大于2的整数;基于类别属性确定移动终端的多个目标应用,其中,多个目标应用中的每个目标应用包括类别属性中的至少一个类别属性;移动终端根据预设规则从多个目标应用中确定第二应用,其中,第二应用包括m个类别属性,包括m个类别属性的集合是包括m个类别属性的集合的子集,m为大于或等于2且小于n的整数;和移动终端将事件通知消息中的m条可分类信息添加到第二应用中的类属性中,其中,所述可分类信息对应于第二应用中的类属性其中,移动终端根据预设规则从多个目标应用中确定第二应用包括:移动终端从多个目标应用中确定在该类属性中包含最多属性的特定应用作为第二应用。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185975(Integer), 2. The method according to claim 1, wherein before the adding, by the mobile terminal, m pieces of classifiable information in the event notification message to the m class attributes in the second application, the method further comprises:searching, by the mobile terminal, existing content in the second application for similar content that includes the m pieces of classifiable information; andperforming, by the mobile terminal, first processing on the similar content based on an operation performed by the user on the similar content, wherein the first processing comprises deletion processing.(String), 2.根据权利要求1所述的方法,其中在移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m类属性之前,还包括:移动终端在第二应用中已有的内容中查找包含m条可分类信息的相似内容;和移动终端根据用户对相似内容的操作,对相似内容进行第一处理,其中,第一处理包括删除处理。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185975(Integer), 3. A mobile terminal, comprising a transceiver, a processor, and a memory, wherein the memory is configured to store at least one instruction, and the processor is configured to invoke the at least one instruction to perform the following processing:receiving, from the transceiver, an event notification message of a first application;obtaining n pieces of classifiable information in the event notification message based on a predefined class template, wherein the n pieces of classifiable information correspond to n class attributes, the predefined class template comprises a classification relationship between classifiable information and a class attribute, and n is an integer greater than 2;determining a plurality of target applications of the mobile terminal based on then class attributes, wherein each target application of the plurality of target applications comprises at least one class attribute in then class attributes;determining a second application from the plurality of target applications according to a preset rule, wherein the second application comprises m class attributes, a set that comprises them class attributes is a subset of a set that comprises then class attributes, and m is an integer greater than or equal to 2 and less than n; andadding m pieces of classifiable information that are in the event notification message to them class attributes in the second application, wherein them pieces of classifiable information correspond to them class attributes in the second applicationwherein the determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule comprises:determining, by the mobile terminal from the plurality of target applications, a particular application that comprises the greatest number of attributes in then class attributes, to serve as the second application.(String), 3.移动终端,包括收发器、处理器和存储器,其中,所述存储器用于存储至少一条指令,所述处理器用于调用所述至少一条指令进行以下处理:从收发器接收第一应用程序的事件通知消息;基于预定义的类模板获取事件通知消息中的n条可分类信息,其中,n条可分类信息对应n个类属性,预定义类模板包括可分类信息与类属性之间的分类关系,n为大于2的整数;基于类别属性确定移动终端的多个目标应用,其中,多个目标应用中的每个目标应用包括类别属性中的至少一个类别属性;根据预设规则从多个目标应用中确定第二应用,其中,第二应用包括m个类别属性,包括其类别属性的集合为包括该类别属性的集合的子集,m为大于的整数小于或等于2且小于n;和将事件通知消息中的m条可分类信息添加到第二应用中的类属性中,其中每条可分类信息对应第二应用中的类属性其中,移动终端根据预设规则从多个目标应用中确定第二应用包括:移动终端从多个目标应用中确定在该类属性中包含最多属性的特定应用作为第二应用。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185975(Integer), 4. The mobile terminal according to claim 3, wherein the processor is further configured to search existing content in the second application for similar content that includes the m pieces of classifiable information; andperform first processing on the similar content based on an operation performed by the user on the similar content, wherein the first processing comprises deletion processing.(String), 4.根据权利要求3所述的移动终端,其中处理器还用于在第二应用程序中的现有内容中查找包含m条可分类信息的相似内容。和基于用户对相似内容的操作对相似内容进行第一处理,其中,第一处理包括删除处理。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185975(Integer), 5. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to carry out the following operations:receiving, by a mobile terminal, an event notification message of a first application;obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template, wherein the n pieces of classifiable information correspond to n class attributes, the predefined class template comprises a classification relationship between classifiable information and a particular class attribute, and n is an integer greater than 2;determining a plurality of target applications of the mobile terminal based on then class attributes, wherein each target application of the plurality of target applications comprises at least one class attribute in then class attributes;determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule, wherein the second application comprises m class attributes, a set that comprises them class attributes is a subset of a set that comprises then class attributes, and m is an integer greater than or equal to 2 and less than n; andadding, by the mobile terminal, m pieces of classifiable information that are in the event notification message to them class attributes in the second application, wherein them pieces of classifiable information correspond to them class attributes in the second applicationwherein the determining, by the mobile terminal, a second application from the plurality of target applications according to a preset rule comprises:determining, by the mobile terminal from the plurality of target applications, a particular application that comprises the greatest number of attributes in then class attributes, to serve as the second application.(String), 5.一种非暂时性计算机可读存储介质包括当被处理器执行时,使处理器执行以下操作的指令:移动终端接收第一应用的事件通知消息;移动终端根据预定义的类模板获取事件通知消息中的n条可分类信息,其中,n条可分类信息对应n个类属性,预定义的类模板包括可分类信息与类属性之间的分类关系。特定类属性,n为大于2的整数;基于类别属性确定移动终端的多个目标应用,其中,多个目标应用中的每个目标应用包括类别属性中的至少一个类别属性;移动终端根据预设规则从多个目标应用中确定第二应用,其中,第二应用包括m个类别属性,包括m个类别属性的集合是包括m个类别属性的集合的子集,m为大于或等于2且小于n的整数;和移动终端将事件通知消息中的m条可分类信息添加到第二应用中的类属性中,其中,所述可分类信息对应于第二应用中的类属性其中,移动终端根据预设规则从多个目标应用中确定第二应用包括:移动终端从多个目标应用中确定在该类属性中包含最多属性的特定应用作为第二应用。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185975(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2017/099424, filed on Aug. 29, 2017, which claims priority to Chinese Patent Application No. 201611260769.2, filed on Dec. 30, 2016. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of this application relate to the field of information processing on a mobile terminal, and more specifically, to a method for obtaining event information on a mobile terminal and a mobile terminal. BACKGROUND [0003]Content recognition by a mobile terminal mainly includes automatic matching and feature capturing performed by the mobile terminal on information such as a character, a picture, and a geographic location. Character recognition may be applied to a plurality of fields such as reading, translation, document retrieval, letter and parcel sorting, manuscript editing and proofreading, summarization and analysis of massive statistical statements and cards, bank check processing, commodity invoice summarization, commodity code recognition, commodity warehouse management, automatic processing of massive credit cards in services of charging fees for water, electricity, gas, house rent, and personal insurance, and partial work automation for office typists. Character information recognition in a mobile terminal system can support the mobile terminal system in performing a further intelligent scenario function after obtaining and recognizing character information. For example, after obtaining and recognizing address content, the mobile terminal system may invoke a related map application in the system based on a shortcut operation performed by a user on the address content, to recommend content related to the address text content to the user, so that the user can check and select the content recommended by the mobile terminal and the like. [0004]In the prior art, an event notification message received by a mobile terminal may include a plurality of pieces of information, and if a user needs to add the plurality of pieces of information to an application, the user needs to respectively perform operations such as manual addition or system recognition addition. For example, after an SMS application module receives a notification message that includes content such as a position, a contact, an email address, and a phone number, when the user needs to add the contact, the email address, and the phone number to an address book, the user first performs a shortcut operation on the phone number to add the phone number to the address book, and then successively manually enters or copies the contact and the email address in the SMS message to a contact and email address column in the address book. It can be learned that such a method for adding a plurality of pieces of classifiable information in one event notification message to an application one by one causes relatively low efficiency. SUMMARY [0005]This application provides a method for obtaining event information on a mobile terminal and a mobile terminal, so as to automatically add a plurality of pieces of classifiable information in an event notification message to an application, thereby improving addition efficiency. [0006]According to a first aspect, a method for obtaining event information on a mobile terminal is provided, and includes: receiving, by a mobile terminal, an event notification message of a first application; [0007]obtaining, by the mobile terminal, n pieces of classifiable information in the event notification message based on a predefined class template, where the n pieces of classifiable information are respectively corresponding to n class attributes, the class template includes a classification relationship between classifiable information and a class attribute, and n is an integer greater than or equal to 2; [0008]determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule, where the second application includes m class attributes, a set that includes the m class attributes is a subset of a set that includes the n class attributes, and m is an integer greater than or equal to 2 and not greater than n; and [0009]adding, by the mobile terminal, m pieces of classifiable information that are in the event notification message and that are respectively corresponding to the m class attributes to the m class attributes in the second application. [0010]According to the method for obtaining event information on a mobile terminal in this application, the mobile terminal may obtain the plurality of pieces of classifiable information included in the event notification message by using the predefined class template. In addition, the mobile terminal may obtain, according to the preset rule, an application (namely, the second application) that includes class attributes corresponding to at least two pieces of classifiable information in the plurality of pieces of classifiable information. Further, the mobile terminal may automatically add the at least two pieces of classifiable information in the plurality of pieces of classifiable information to the corresponding class attributes in the second application. Therefore, operation complexity of adding all pieces of classifiable information by a user one by one can be reduced, information addition efficiency can be improved, and user experience can be improved. [0011]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0012]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0013]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application that includes most attributes in the n class attributes, to serve as the second application. [0014]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0015]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0016]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application that has highest relevance to the first application, to serve as the second application. [0017]In the foregoing manner, the mobile terminal may automatically add the classifiable information in the event notification message to the application having highest relevance to the first application. [0018]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0019]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0020]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application used by a user at a time that is proximate to a time at which the first application is used, to serve as the second application. [0021]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0022]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0023]if there are a plurality of target applications, determining, by the mobile terminal from the target applications, an application that is most frequently used by a user, to serve as the second application. [0024]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0025]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0026]if there are a plurality of target applications, determining, by the mobile terminal, an application that is randomly selected from the target applications, to serve as the second application. [0027]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0028]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0029]if there is one target application, determining, by the mobile terminal, the target application as the second application. [0030]In a possible implementation, the determining, by the mobile terminal, a second application based on the n class attributes according to a preset rule includes: [0031]determining, by the mobile terminal, a target application based on the n class attributes, where the target application includes at least one class attribute in the n class attributes; and [0032]if there are a plurality of target applications, determining, by the mobile terminal, any one of the target applications as the second application. [0033]Optionally, the mobile terminal may determine some or all of the target applications as second applications. [0034]If there are a plurality of second applications, the mobile terminal may sequentially present application names of the determined second applications to the user based on a quantity of included class attributes in the n class attributes. In addition, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on relevance to the first application. Moreover, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on an interval between a use time of the user and a current time, or a use frequency of the user in a recent period of time. Certainly, the mobile terminal may randomly sort the second applications to present application names of the second applications to the user. [0035]The user may select any one of the foregoing second applications, and add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in the selected application. The user may select no application from the presented second applications, but add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in each second application together. [0036]It should be understood that for the foregoing plurality of manners of determining the second application by the mobile terminal, the mobile terminal may select one thereof or perform combination, and a specific manner that is to be used may be defined or selected by the user, so as to meet different user requirements. [0037]In a possible implementation, before the adding, by the mobile terminal, m pieces of classifiable information in the event notification message to the m class attributes in the second application, the method further includes: [0038]searching, by the mobile terminal, existing content corresponding to the m class attributes in the second application for content that is the same as the m pieces of classifiable information; and [0039]performing, by the mobile terminal, first processing on the same content based on an operation performed by the user on the same information content, where the first processing includes deletion processing. [0040]The deletion processing is performed on the content, in the second application, that is the same as the m pieces of classifiable information, so as to avoid repeated information storage, and release storage space of the mobile terminal. In addition, it is convenient for the user to read and search for related content, so as to improve user experience. [0041]According to a second aspect, a mobile terminal is provided, and is configured to perform the method in the first aspect or any possible implementation of the first aspect. Specifically, the mobile terminal includes units configured to perform the method in the first aspect or any possible implementation of the first aspect. [0042]According to a third aspect, a mobile terminal is provided, and includes a processor, a memory, and a transceiver, where the processor, the memory, and the transceiver are connected by using a bus system. The memory is configured to store an instruction, and the processor is configured to invoke the instruction stored in the memory, so that the terminal device performs the method in the first aspect or any possible implementation of the first aspect. [0043]According to a fourth aspect, a computer readable medium is provided, and is configured to store a computer program, where the computer program includes an instruction used to perform the method in the first aspect or any possible implementation of the first aspect. BRIEF DESCRIPTION OF DRAWINGS [0044]FIG. 1 is a schematic diagram of an application scenario according to this application; [0045]FIG. 2 is a schematic flowchart of a method for obtaining event information on a mobile terminal according to an embodiment of this application; [0046]FIG. 3 is a schematic diagram of a method for obtaining event information on a mobile terminal according to a specific embodiment of this application; [0047]FIG. 4 is a schematic diagram of a method for obtaining event information on a mobile terminal according to a specific embodiment of this application; [0048]FIG. 5 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0049]FIG. 6 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0050]FIG. 7 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0051]FIG. 8 is a schematic diagram of a method for obtaining event information on a mobile terminal according to still another specific embodiment of this application; [0052]FIG. 9 is a schematic diagram of a method for obtaining event information on a mobile terminal according to still another specific embodiment of this application; [0053]FIG. 10 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0054]FIG. 11 is a schematic diagram of a method for obtaining event information on a mobile terminal according to another specific embodiment of this application; [0055]FIG. 12 is a schematic block diagram of a mobile terminal according to an embodiment of this application; and [0056]FIG. 13 is a schematic block diagram of a mobile terminal according to another embodiment of this application. DESCRIPTION OF EMBODIMENTS [0057]The following describes the embodiments of this application with reference to accompanying drawings. [0058]In this application, the term such as “for example” is used to indicate an example, instance, or illustration. Any embodiment or design scheme described by using the term “for example” in the embodiments of this application should not be construed as having more advantages than another embodiment or design scheme. Exactly, using the term such as “for example” is intended to present a related concept in a specific manner. [0059]A terminal device in this application includes an electronic product that can perform human-computer interaction with a user by using a keyboard, a touchpad, or a sound control device. For example, the terminal device may be a computer, a smartphone, a wearable device, a tablet computer (Portable Android Device (PAD)), or the like. An operating system running on the terminal device may be a Linux kernel-based operating system such as Android in a mobile version, Ubuntu in a mobile version, or Tizen, and a desktop operating system such as Windows, Mac OS, or Linux. This is not limited in this application. [0060]In the embodiments of this application, an application may be referred to as an application program (e.g., Application or APP), and an application may be an application built into the operating system of the terminal device, or may be a third-party application installed in the operating system of the terminal device. This is not limited in this application. [0061]FIG. 1 shows an application scenario according to embodiments of this application. As shown in FIG. 1, when an application of the terminal device, such as an SMS message or the WeChat® APP, receives an event notification message, and the event notification message includes two or more pieces of classifiable information such as a conference theme, a time, a position, staff, and a phone number, the terminal device may process the classifiable information by identifying an operation performed by a user on the classifiable information, for example, may enable an application related to the classifiable information. [0062]In an existing related technology, a mobile system end usually performs tappable single recognition on key text content through tapping or touching and holding. The tapping triggers a most frequently-used operation action, and the touching and holding adds more operations on the text information. For example, when a current prompt is that digits may be tapped, the tapping is triggering a user to perform a call operation, and the touching and holding is triggering more operation options that include making a call, sending an SMS message, adding to an address book, copying, and the like. When the user needs to add the conference theme, the time, the position, the staff, and the phone number shown in FIG. 1 to an application such as a calendar, the user needs to perform operations on the conference theme, the time, the position, the staff, and the phone number one by one, to respectively add the conference theme, the time, the position, the staff, and the phone number to corresponding class attributes of the calendar. Such a method for adding a plurality of pieces of classifiable information to corresponding class attributes of an application one by one causes relatively low efficiency and relatively complex operations. [0063]Based on the foregoing prior-art problems, this application provides a method for obtaining event information on a mobile terminal. When an event notification message includes a plurality of pieces of classifiable information, at least two pieces of classifiable information in the plurality of pieces of classifiable information can be automatically added to a corresponding application, and do not need to be manually added by a user, so as to improve addition efficiency, reduce addition operation complexity, and improve user experience. [0064]FIG. 2 is a schematic flowchart of a method for obtaining event information on a mobile terminal according to an embodiment of this application. [0065]S210. A mobile terminal receives an event notification message. [0066]The event notification message is a message of a first application. For example, the first application may be an SMS message APP, WeChat® APP, or QQ® APP, and correspondingly, the event notification message may be an SMS message, a WeChat message, or a QQ message. For example, the event notification message may be a conference notification message, and the conference notification message may include a time, a position, staff, and a phone number (a contact may be included). For another example, the event notification message may be a flight notification message, and the flight notification message may include information such as a time (including a departure time and a landing time), a flight number, a position (including a departure position and a destination). [0067]S220. The mobile terminal obtains n pieces of classifiable information in the event notification message based on a predefined class template according to a preset rule. [0068]For example, a user usually needs to add a plurality of pieces of information such as a contact or a phone number to an address book, and the mobile terminal may define a class template based on class attributes such as a contact, a phone number, an address, and an email address presented in the address book. For example, the mobile terminal may define that the class template includes three class attributes: the contact, the address, and the email address. For another example, the mobile terminal may define that the class template includes four class attributes: the contact, the address, the phone number, and the email address. Then, the mobile terminal obtains the n pieces of classifiable information in the event notification message based on the predefined class template according to the preset rule. The n pieces of classifiable information are respectively corresponding to n class attributes, and n is an integer greater than or equal to 2. For example, when the event notification message is the conference notification message described in S210, then class attributes included in the event notification message include a time, a position, staff, and a phone number. When the class template includes the four class attributes, the mobile terminal may obtain information about the time, the position, the staff, and the phone number information in the event notification message. [0069]It should be understood that in this embodiment of this application, a system may define a class template based on one or more applications. For example, the system may define the class template based on only one application such as an address book or a calendar, or define the class template with reference to a plurality of applications such as an address book and a calendar. This is not limited in this embodiment of this application. [0070]In this embodiment of this application, after obtaining the n pieces of classifiable information in the event notification message, the mobile terminal may present a first operation page to the user, and the first operation page includes at least two of the n pieces of classifiable information. Based on information presented on the first operation page, the user can learn of the classifiable information obtained by the terminal device in S220. In addition, to improve intelligibility, the first operation page may further present identification information used to identify each piece of classifiable information. The identification information may be predefined by the system based on a class template. For example, the identification information may be a text or an image for identifying a class attribute defined in the class template. For example, time information may be identified by using a text “time” or an image with an icon of an alarm clock, and position information may be identified by using a text “position” or an image with an icon of a map. A specific form of the identification information is not limited in this application. [0071]S230. The mobile terminal determines a second application based on the n class attributes according to the preset rule. [0072]The second application includes m class attributes, a set that includes the m class attributes is a subset of a set that includes the n class attributes, and m is an integer greater than or equal to 2 and not greater than n. For example, when the n class attributes include the time, the position, the staff, and the phone number, the m class attributes may include the time, the position, and the staff, or may include the position, the staff, and the phone number. [0073]When determining the second application based on the n class attributes according to the preset rule, the mobile terminal may first determine a target application based on the n class attributes, and the target application includes at least one class attribute in the n class attributes. In other words, the mobile terminal may determine an application as the target application, provided that the application includes one of the n class attributes. If there is only one target application, the mobile terminal determines the target application as the second application. If there are a plurality of target applications, the mobile terminal may determine the second application in the following manners. [0074]Manner 1 [0075]The mobile terminal determines, from the target applications, an application that has most attributes in the n class attributes, to serve as the second application. [0076]Specifically, after the mobile terminal determines the target applications, the mobile terminal selects, from the target applications, the application that has most attributes in the n class attributes, and determines the application as the second application. For example, the n class attributes include the time, the position, the staff, and the phone number; the address book includes two class attributes: the staff and the phone number; a note includes four class attributes: the time, the position, the staff, and the phone number; and the calendar includes one attribute: the time. Therefore, the target applications determined by the mobile terminal include the address book, the note, and the calendar. The note includes most class attributes in the target applications, and therefore the mobile terminal may determine the note that includes the foregoing four class attributes, to serve as the second application. [0077]Manner 2 [0078]The mobile terminal determines, from the target applications, an application that has highest relevance to the first application, to serve as the second application. [0079]For example, the first application may be an SMS application, and applications related to the first application may be the WeChat® APP, the QQ® APP, an address book, and the like. The mobile terminal may predefine the applications related to the first application, and define relevance of each application to the first application. When defining an application related to the first application, the mobile terminal may define an application that is frequently used by the user recently or an application that is invoked together with the first application by using a shortcut, to serve as the application related to the first application. This is not specifically limited in this embodiment of this application. In this embodiment of this application, the mobile terminal may first obtain the target applications that include the at least one class attribute in the n class attributes, and then find, based on relevance of these applications to the first application, the application that has highest relevance to the first application, to serve as the second application. [0080]Manner 3 [0081]The mobile terminal determines, from the target applications, an application used by a user at a time that is proximate to a time at which the first application is used, to serve as the second application. [0082]Specifically, in this embodiment, the mobile terminal first determines a target application that includes at least one class attribute in the n class attributes. If there are a plurality of target applications, the mobile terminal may determine, based on times at which a user uses these applications, an application used at a most recent time that is proximate to a current time, and determine the application as the second application. [0083]For example, the target applications determined by the mobile terminal include the address book, the calendar, and the note, and if most recent times at which the user uses the three applications are respectively one day ago, two days ago, and five days ago, the mobile terminal determines the address book as the second application. [0084]Manner 4 [0085]The mobile terminal determines, from the target applications, an application that is most frequently used by a user, to serve as the second application. [0086]After determining the target applications, the mobile terminal obtains, based on a frequency of recently using each of the target applications by the user, the application that is most frequently used by the user, and determines the application as the second application. [0087]For example, the target applications determined by the mobile terminal include the address book, the calendar, and the note, and if frequencies of recently using the three applications by the user, for example, in the last six months or the last three months are respectively 200, 20, and 10, respectively, the mobile terminal determines the address book as the second application. [0088]Manner 5 [0089]The mobile terminal determines an application that is randomly selected from the target applications, to serve as the second application. [0090]Herein, the mobile terminal may determine the second application by using a random algorithm. An algorithm or a method used by the mobile terminal for random selection is not limited in this embodiment of this application. [0091]Manner 6 [0092]The mobile terminal determines any one of the target applications as the second application. [0093]In other words, the mobile terminal may determine one or more applications that include the at least one class attribute in the n class attributes, to serve as the second application. [0094]If determining a plurality of applications in the target applications as second applications, the mobile terminal may sequentially present application names of the determined second applications to the user based on a quantity of included class attributes in the n class attributes. For example, from top to bottom of a display screen, the mobile terminal may present, in the first row, a name of an application that includes the most class attributes in the n class attributes, present, in the second row, a name of an application that includes the second most class attributes in the n class attributes, and by analogy, present, in the last row, a name of an application that includes the fewest class attributes in the n class attributes. In addition, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on relevance to the first application. For example, from top to bottom of a display screen, the mobile terminal may present, in the first row, a name of an application that has the highest relevance to the first application, present, in the second row, a name of an application that has the second highest relevance to the first application, and by analogy, present, in the last row, a name of an application that has the lowest relevance to the first application. Moreover, the mobile terminal may alternatively sequentially present application names of the determined second applications to the user based on an interval between a use time of the user and a current time, or a use frequency of the user in a recent period of time. Certainly, the mobile terminal may randomly sort the second applications to present application names of the second applications to the user. [0095]The user may select any one of the foregoing second applications, and add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in the selected application. The user may select no application from the presented second applications, but add one or more pieces of classifiable information in the n pieces of classifiable information to a corresponding class attribute in each second application together. [0096]It should be understood that for the foregoing plurality of manners of determining the second application by the mobile terminal, the mobile terminal may select one thereof or perform combination, and a specific manner that is to be used may be defined or selected by the user, so as to meet different user requirements. [0097]It should be understood that the mobile terminal determines the second application based on selection from a plurality of applications. For ease of description, the plurality of applications are referred to as third applic(String), 相关申请的交叉引用 [0001] 本申请是2017年8月29日提交的国际申请号PCT/CN2017/099424的继续申请,该国际申请要求2016年12月30日提交的中国专利申请号201611260769.2的优先权。上述申请的公开内容是 特此通过引用整体并入。 技术领域 [0002] 本申请实施例涉及移动终端信息处理领域,更具体地,涉及一种移动终端事件信息的获取方法及移动终端。 背景 [0003] 移动终端的内容识别主要包括移动终端对字符、图片、地理位置等信息进行的自动匹配和特征捕获。 字符识别可应用于阅读、翻译、文献检索、信件包裹分拣、稿件编辑校对、海量统计报表、卡片汇总分析、银行支票处理、商品发票汇总、商品代码识别等多个领域 、商品仓库管理、水、电、气、房租、人身保险等收费服务的海量信用卡自动处理,办公打字员部分工作自动化。 移动终端系统中的字符信息识别,可以支持移动终端系统在获取并识别字符信息后,进一步执行智能化的场景功能。 例如,移动终端系统获取并识别地址内容后,可以根据用户对地址内容的快捷操作,调用系统中相关的地图应用,向用户推荐与地址文本内容相关的内容, 方便用户查看和选择移动端推荐的内容等。 [0004] 现有技术中,移动终端接收到的事件通知消息中可能包含多条信息,如果用户需要将多条信息添加到应用程序中,则需要用户分别进行手动操作等操作。 添加或系统识别添加。 例如,短信应用模块收到包含位置、联系人、邮箱、电话号码等内容的通知消息后,当用户需要将联系人、邮箱、电话添加到 通讯录,用户首先对电话号码进行快捷操作,将电话号码添加到通讯录中,然后依次手动输入或复制短信中的联系人和邮箱到通讯录中的联系人和邮箱栏中 地址簿。 可以看出,这种将一条事件通知消息中的多条可分类信息逐一添加到应用程序中的方法效率较低。 概括 [0005] 本申请提供了一种获取移动终端事件信息的方法及移动终端,能够自动为应用程序添加事件通知消息中的多条可分类信息,提高添加效率。 [0006] 第一方面,提供了一种获取移动终端事件信息的方法,包括: 移动终端接收第一应用的事件通知消息; [0007] 移动终端根据预先定义的类模板获取事件通知消息中的n条可分类信息,该n条可分类信息分别对应n个类属性,类模板包括可分类信息与类模板之间的分类关系 类属性,n为大于等于2的整数; [0008] 移动终端根据预设规则根据n类属性确定第二应用,其中,第二应用包括m类属性,包括m类属性的集合是包括n类的集合的子集 属性,m为大于等于2且不大于n的整数; 和 [0009] 移动终端将事件通知消息中的m类属性分别对应的m条可分类信息添加到第二应用中的m类属性中。 [0010] 根据本申请的移动终端事件信息的获取方法,移动终端可以通过预先定义的类模板获取事件通知消息中包含的多个可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包括至少两个分类信息对应的类别属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个分类信息中的至少两个分类信息添加到第二应用中对应的类属性中。 从而可以降低用户将所有可分类信息逐条添加的操作复杂度,提高信息添加效率,提高用户体验。 [0011] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0012] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0013] 若目标应用为多个,则移动终端从目标应用中确定n类属性中属性最多的应用作为第二应用。 [0014] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0015] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0016] 若目标应用为多个,则移动终端从目标应用中确定与第一应用相关性最高的应用作为第二应用。 [0017] 通过上述方式,移动终端可以自动将事件通知消息中的可分类信息添加到与第一应用相关度最高的应用中。 [0018] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0019] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0020] 若目标应用为多个,则移动终端从目标应用中确定用户在与第一应用的使用时间相近的时间使用的应用作为第二应用。 [0021] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0022] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0023] 若目标应用为多个,则移动终端从目标应用中确定用户使用频率最高的应用作为第二应用。 [0024] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0025] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0026]若目标应用为多个,则移动终端从目标应用中随机选择一个应用作为第二应用。 [0027] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0028] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0029] 若目标应用为一个,则移动终端将该目标应用确定为第二应用。 [0030] 在一种可能的实现方式中,移动终端根据预设规则基于n类属性确定第二应用包括: [0031] 移动终端根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性; 和 [0032] 若目标应用为多个,则移动终端将目标应用中的任一个确定为第二应用。 [0033] 可选的,移动终端可以将部分或全部目标应用确定为第二应用。 [0034] 如果存在多个第二应用,则移动终端可以根据n个类别属性中包含的类别属性的数量,依次将确定的第二应用的应用名称呈现给用户。 另外,移动终端还可以根据与第一应用的相关性,将确定的第二应用的应用名称依次呈现给用户。 并且,移动终端还可以根据用户使用时间与当前时间的间隔,或者用户最近一段时间的使用频率,依次将确定的第二应用的应用名称依次呈现给用户。 当然,移动终端可以对第二应用程序进行随机排序,以将第二应用程序的应用程序名称呈现给用户。 [0035] 用户可以选择上述任一第二应用,将n条可分类信息中的一条或多条可分类信息添加到所选应用中对应的类属性中。 用户可以在所呈现的第二应用中不选择任何应用,而是将n条可分类信息中的一条或多条可分类信息一起添加到每个第二应用中对应的类别属性中。 [0036] 可以理解的是,对于上述多种移动终端确定第二应用的方式,移动终端可以选择其中的一种或者进行组合,具体采用何种方式可以由用户自行定义或选择, 以满足不同的用户需求。 [0037] 在一种可能的实现方式中,移动终端在将事件通知消息中的m条可分类信息添加到第二应用中的m类属性之前,还包括: [0038] 移动终端在第二应用中的m类属性对应的已有内容中查找与m条可分类信息相同的内容; 和 [0039] 移动终端根据用户对同一信息内容的操作,对同一内容进行第一处理,第一处理包括删除处理。 [0040] 对第二应用中与m条可分类信息相同的内容进行删除处理,避免重复信息存储,释放移动终端的存储空间。 另外,方便用户阅读和搜索相关内容,提高用户体验。 [0041]第二方面,提供了一种移动终端,用于执行第一方面或第一方面的任何可能实现方式中的方法。 具体地,该移动终端包括用于执行第一方面的方法或第一方面的任何可能实现方式的单元。 [0042] 第三方面,提供了一种移动终端,包括处理器、存储器和收发器,所述处理器、存储器和收发器通过总线系统连接。 存储器,用于存储指令,处理器,用于调用存储在存储器中的指令,使得终端设备执行第一方面的方法或第一方面的任何可能实现方式。 [0043] 第四方面,提供一种计算机可读介质,用于存储计算机程序,所述计算机程序包括用于执行第一方面的方法或第一方面的任何可能实现方式的指令。 附图说明 [0044] 图1为本申请的应用场景示意图; [0045] 图2为本申请实施例提供的一种获取移动终端事件信息的方法流程示意图; [0046] 图3为本申请具体实施例提供的移动终端事件信息的获取方法示意图; [0047] 图4为本申请具体实施例提供的移动终端事件信息的获取方法示意图; [0048] 图5为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0049] 图6为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0050] 图7为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0051] 图8为本申请又一具体实施例提供的移动终端事件信息的获取方法示意图; [0052] 图9为本申请再一具体实施例提供的移动终端事件信息的获取方法示意图; [0053] 图10为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0054] 图11为本申请另一具体实施例提供的移动终端事件信息的获取方法示意图; [0055] 图12是本申请一个实施例的移动终端的示意性框图; 和 [0056] 图13是根据本申请另一实施例的移动终端的示意性框图。 具体实施方式 [0057] 下面将结合附图对本申请的实施例进行描述。 [0058] 在本申请中,诸如“例如”之类的术语用于表示示例、实例或说明。 凡在本申请实施例中以“举例”一词描述的实施例或设计方案,不应理解为比其他实施例或设计方案具有更多的优点。 确切地说,使用诸如“例如”之类的术语是为了以特定方式呈现相关概念。 [0059]本申请中的终端设备包括能够通过键盘、触摸板或声控设备与用户进行人机交互的电子产品。 例如,终端设备可以是计算机、智能手机、可穿戴设备、平板电脑(Portable Android Device(PAD))等。 终端设备上运行的操作系统可以是基于Linux内核的操作系统,例如移动版的Android、移动版的Ubuntu、Tizen,以及桌面操作系统,例如Windows、Mac OS、Linux。 本申请不限于此。 [0060] 在本申请实施例中,应用程序可以称为应用程序(例如Application或APP),应用程序可以是终端设备操作系统内置的应用程序,也可以是第三方应用程序 安装在终端设备的操作系统中。 本申请不限于此。 [0061] 图1示出了根据本申请实施例的应用场景。 如图1所示,当终端设备的应用程序如短信或微信®APP接收到事件通知消息时,事件通知消息中包含两条或多条可分类信息,如会议主题, 终端设备可以通过识别用户对分类信息的操作来对分类信息进行处理,例如,可以开启与分类信息相关的应用。 [0062] 在现有的相关技术中,移动系统端通常通过点击或长按的方式对关键文本内容进行可点击的单一识别。 点击触发最常用的操作动作,长按增加对文本信息的更多操作。 例如,当当前提示为可以点击数字时,点击触发用户进行通话操作,长按触发更多的操作选项,包括拨打电话、发送短信、添加 地址簿、复印等。 当用户需要将图1所示的会议主题、时间、地点、人员、电话号码添加到日历等应用中时,用户需要对会议主题、时间、地点等进行操作。 职位、人员、电话一一对应,将会议主题、时间、职位、人员、电话一一添加到日历对应的类属性中。 这种将多条可分类信息逐条添加到应用程序对应的类属性中的方法效率较低,操作也比较复杂。 [0063] 基于上述现有技术问题,本申请提供了一种获取移动终端事件信息的方法。 当事件通知消息包括多个分类信息时,可以将多个分类信息中的至少两个分类信息自动添加到对应的应用中,不需要用户手动添加, 从而提高加法效率,降低加法操作复杂度,提升用户体验。 [0064] 图2为本申请实施例提供的一种获取移动终端事件信息的方法流程示意图。 [0065] 小号 210 . 移动终端接收事件通知消息。 [0066]事件通知消息为第一应用程序的消息。 例如,第一应用可以是短信APP、微信APP或QQAPP,相应的,事件通知消息可以是短信、微信或QQ消息。 例如,事件通知消息可以是会议通知消息,会议通知消息可以包括时间、地点、工作人员、电话号码(可以包括联系人)。 又例如,事件通知消息可以是航班通知消息,航班通知消息可以包括时间(包括起飞时间和降落时间)、航班号、位置(包括起飞位置和降落时间)等信息。 目的地)。 [0067] 小号 220 . 移动终端根据预设规则,基于预定义的类模板获取事件通知消息中的n条可分类信息。 [0068] 例如,用户通常需要在通讯录中添加联系人或电话号码等多条信息,移动终端可以根据联系人、电话号码等类属性定义类模板, 地址簿中显示的地址和电子邮件地址。 例如,移动终端可以定义类模板包括三个类属性:联系人、地址和电子邮件地址。 又例如,移动终端可以定义类模板包括四个类属性:联系人、地址、电话号码和电子邮件地址。 然后,移动终端根据预设规则基于预定义的类模板获取事件通知消息中的n条可分类信息。 n条可分类信息分别对应n个类别属性,n为大于等于2的整数。例如,当事件通知消息为S中描述的会议通知消息时 210 ,则事件通知消息中包含的类属性包括时间、职位、人员、电话号码。 当类模板包括四种类属性时,移动终端可以获取事件通知消息中的时间、位置、人员、电话号码信息。 [0069] 应理解,在本申请实施例中,系统可以基于一个或多个应用定义类模板。 例如,系统可以仅基于通讯录或日历等一个应用程序来定义类模板,也可以参考通讯录和日历等多个应用程序来定义类模板。 本申请实施例对此不作限定。 [0070] 本申请实施例中,移动终端在获取事件通知消息中的n条可分类信息后,可以向用户呈现第一操作页面,第一操作页面包括n条可分类信息中的至少两条。 . 用户可以根据第一个操作页面呈现的信息,了解到终端设备在S中获取的分类信息 220 . 另外,为了提高易懂性,第一操作页面还可以呈现用于标识每条可分类信息的标识信息。 标识信息可以是系统基于类模板预先定义的。 例如,标识信息可以是用于标识类模板中定义的类属性的文本或图像。 例如,时间信息可以通过文本“时间”或带有闹钟图标的图像来标识,位置信息可以通过文本“位置”或带有地图图标的图像来标识。 本申请不对标识信息的具体形式进行限定。 [0071] 小号 230 . 移动终端根据预设规则,基于n个类属性确定第二应用。 [0072]第二应用包括m类属性,包括m类属性的集合是包括n类属性的集合的子集,m为大于等于2且不大于n的整数。 例如,当n类属性包括时间、职位、人员、电话号码时,m类属性可以包括时间、职位、人员,也可以包括职位、人员、电话号码。 电话号码。 [0073] 在根据预设规则基于n个类属性确定第二应用时,移动终端可以首先根据n个类属性确定目标应用,目标应用包括n个类属性中的至少一个类属性。 也就是说,移动终端可以确定一个应用程序为目标应用程序,前提是该应用程序包括n个类属性之一。 如果目标应用只有一个,则移动终端将目标应用确定为第二应用。 如果目标应用有多个,则移动终端可以通过以下方式确定第二应用。 [0074] 方式一 [0075] 移动终端从目标应用中确定n类属性中属性最多的应用作为第二应用。 [0076] 具体地,移动终端确定目标应用后,移动终端从目标应用中选择n类属性中属性最多的应用,确定该应用为第二应用。 例如,n个类属性包括时间、职位、人员、电话号码; 通讯录包括两个类属性:工作人员和电话号码; 一张便条包括四个类属性:时间、职位、人员、电话号码; 日历包含一个属性:时间。 因此,移动终端确定的目标应用包括通讯录、便签和日历。 笔记包含了目标应用中的大部分类属性,因此移动终端可以确定包含上述四种类属性的笔记作为第二应用。 [0077] 方式二 [0078] 移动终端从目标应用中确定与第一应用相关性最高的应用作为第二应用。 [0079] 例如,第一应用可以是短信应用,与第一应用相关的应用可以是微信APP、QQAPP、通讯录等。 移动终端可以预先定义与第一应用相关的应用,并定义每个应用与第一应用的相关性。 移动终端在定义与第一应用相关的应用时,可以定义用户最近使用频率较高的应用或者通过快捷方式与第一应用一起调用的应用,作为与第一应用相关的应用 应用。 本申请实施例对此不作具体限定。 在本申请实施例中,移动终端可以先获取n个类属性中包含至少一个类属性的目标应用,然后根据这些应用与第一应用的相关性,查找具有最高的应用。 与第一个应用程序相关,作为第二个应用程序。 [0080] 方式三 [0081] 移动终端从目标应用中确定用户在与第一应用的使用时间最接近的时间使用的应用作为第二应用。 [0082] 具体地,在本实施例中,移动终端首先确定n个类别属性中包括至少一个类别属性的目标应用。 如果目标应用有多个,则移动终端可以根据用户使用这些应用的时间,确定与当前时间最近一次使用的应用,确定该应用为第二应用 . [0083]例如,移动终端确定的目标应用包括通讯录、日历和便签,如果用户最近使用这三个应用的时间分别为一天前、两天前和五天前 ,移动终端确定通讯录为第二应用。 [0084] 方式四 [0085] 移动终端从目标应用中确定用户使用频率最高的应用作为第二应用。 [0086] 在确定目标应用程序后,移动终端根据用户最近使用各个目标应用程序的频率,获取用户使用频率最高的应用程序,确定该应用程序为第二应用程序。 [0087] 例如,移动终端确定的目标应用包括通讯录、日历和便签,如果用户最近使用这三个应用的频率,例如最近六个月或最近三个月, 分别为200、20、10,移动终端确定通讯录为第二应用。 [0088] 方式五 [0089] 移动终端从目标应用中随机选择一个应用作为第二应用。 [0090] 这里,移动终端可以通过随机算法确定第二应用。 本申请实施例不对移动终端随机选择的算法或方法进行限定。 [0091] 方式6 [0092] 移动终端将目标应用中的任意一个确定为第二应用。 [0093] 也就是说,移动终端可以确定n个类别属性中包括至少一个类别属性的一个或多个应用作为第二应用。 [0094] 如果将目标应用中的多个应用确定为第二应用,则移动终端可以根据n个类别属性中包含的类别属性的数量,依次向用户呈现确定的第二应用的应用名称。 例如,移动终端从显示屏的上到下,可以在第一行呈现n个类别属性中类别属性最多的应用程序的名称,在第二行呈现以下应用程序的名称: n个类属性中包含第二多类属性的应用程序,以此类推,在最后一行给出n个类属性中包含最少类属性的应用程序的名称。 另外,移动终端还可以根据与第一应用的相关性,将确定的第二应用的应用名称依次呈现给用户。 例如,移动终端从显示屏幕的顶部到底部,可以在第一行呈现与第一应用相关度最高的应用的名称,在第二行呈现应用的名称 与第一应用的相关性第二高的应用名称,以此类推,在最后一行给出与第一应用的相关性最低的应用名称。 并且,移动终端还可以根据用户使用时间与当前时间的间隔,或者用户最近一段时间的使用频率,依次将确定的第二应用的应用名称依次呈现给用户。 当然,移动终端可以对第二应用程序进行随机排序,以将第二应用程序的应用程序名称呈现给用户。 [0095] 用户可以选择上述任一第二应用,将n条可分类信息中的一条或多条可分类信息添加到所选应用中对应的类属性中。 用户可以在所呈现的第二应用中不选择任何应用,而是将n条可分类信息中的一条或多条可分类信息一起添加到每个第二应用中对应的类别属性中。 [0096]可以理解的是,对于上述多种移动终端确定第二应用的方式,移动终端可以选择其中的一种或者进行组合,具体采用何种方式可以由用户自行定义或选择, 以满足不同的用户需求。 [0097] 应理解,移动终端基于从多个应用中的选择来确定第二应用。 为了便于描述,以下将多个应用称为第三应用。 具体的,移动终端根据n个类别属性从第三应用程序中确定n个类别属性中的至少一个类别属性的应用程序作为第二应用程序。 第三应用可由用户自行定义。 例如,用户可以定义移动终端系统内置的部分或全部应用程序为第三应用程序。 又例如,用户可以定义移动终端上安装的部分或全部第三方应用程序为第三方应用程序。 再例如,用户可以定义移动终端系统中内置的所有应用程序和移动终端上安装的所有第三方应用程序都是第三方应用程序。 本申请不限制第三应用的数量和第三应用的来源。 第三应用程序可以由系统定义。 换句话说,用户不能改变第三应用程序的定义。 [0098] 还应理解,上述类模板也可以是基于第三应用定义的。 当第三应用由用户定义时,类模板也可能随着用户改变第三应用而改变。 当系统定义第三个应用时,类模板对用户来说是固定的,只随系统变化。 需要说明的是,移动终端通常是在接收到事件通知消息后,对事件通知消息进行识别。 当识别成功时,移动终端通过对内容进行特殊标记,例如下划线等,提示用户对事件通知消息中的某些内容进行快捷操作。 但是,在本申请实施例中,S中获取的分类信息 220 基于预定义的类模板可以只包括上述特别标注的内容,也可以只包括不特别标注的内容,还可以包括前述特别标注的内容和不特别标注的内容。 [0099] 小号 240 . 移动终端将事件通知消息中的m个类别属性分别对应的m条可分类信息添加到第二应用中的m个类别属性中。 具体地,移动终端在获取事件通知消息和第二应用中的n条可分类信息后,可以自动将n条可分类信息中的m条可分类信息添加到第二应用中的m类属性中。 例如,用户可以通过对第一操作页面进行操作,例如长按第一操作页面,将m条可分类信息添加到第二应用中的m类属性中。 [0100]因此,本申请的获取移动终端事件信息的方法,移动终端可以通过预定义的类模板获取事件通知消息中包含的多个可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包括至少两个分类信息对应的类别属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个分类信息中的至少两个分类信息添加到第二应用中对应的类属性中。 从而可以降低用户将所有可分类信息逐一添加的操作复杂度,提高信息添加效率,提高用户体验。 [0101] 下面以类模板包括四个类属性:联系人、电话号码、时间和位置为例,对本申请实施例的获取移动终端事件信息的方法进行说明。 会议通知消息如图1所示。 [0102] 移动终端接收到图1所示的会议通知消息后,通过类模板和会议通知消息,移动终端可以获取到会议通知消息中的四项信息:联系人:叶敏,电话号码: 13800000000,事件:明早10点,位置:A路18号。此时,移动终端呈现给用户的第一操作页面如图3所示。 或者,移动终端可以在S中通过任意方式确定第二应用。 230 同时将第一个操作页面呈现给用户。 例如,移动终端可以通过方式三确定通讯录为第二应用。则在用户操作图3所示的第一操作页面后,例如,用户长按图3所示的第一操作页面。 3、移动终端可以将第一操作页面上的联系人:叶敏和电话号码分别添加到通讯录的联系人栏和电话号码栏中。 添加完成后,通讯录生成的快捷操作页面如图4所示,用户可以在该页面上进行快捷操作,例如拨打电话、发送短信等。 [0103] 可选的,移动终端接收到事件通知消息后,可以向用户呈现第二操作页面。 第二操作页面包括事件通知消息和用于提示用户操作事件通知消息的第二页面元素。 移动终端可以根据预先定义的类模板和用户对第二页面元素的操作,获取事件通知消息中的n条可分类信息。 [0104] 具体地,以移动终端接收到主题为部门年中活动主题策划讨论的通知消息为例,移动终端接收到该通知消息后,呈现如图5所示的第二操作页面。当用户需要时 为了获取通知消息中的n条可分类信息,用户可以通过操作第二页面元素,例如点击第二页面元素,获取图3或图6所示的第一操作页面。 用户在获取到第一操作页面后,对移动终端呈现的第一操作页面进行操作,使得移动终端可以将n条分类信息中的至少两条分类信息添加到第二应用中。 [0105]第一操作页面还可以包括第一页面元素。 移动终端可以根据用户对第一页面元素的操作,将n条分类信息中的至少两条分类信息添加到第二应用中。 第一页元素可以是图形标记。 例如,第一页面元素可以是图6所示的图形标记,用户可以通过点击图形标记将n条分类信息中的至少两条分类信息添加到第二应用中。 第一页面元素可以是用于提示用户对第一操作页面进行添加操作的文本等标识。 本申请不对第一页面元素的具体形式进行限定。 [0106] 进一步地,若移动终端确定的第二应用为多个,则当移动终端根据用户对第二应用的操作,将n条可分类信息中的至少两条可分类信息添加到第二应用中。 第一操作页面,移动终端可以首先根据用户在第一操作页面上的操作呈现第一操作提示项。 第一操作提示项可以表示添加了n条可分类信息中的至少两条可分类信息的目标应用。 也就是说,第一操作提示项用于向用户提示可以添加n条分类信息中的至少两条分类信息的应用。 如果用户需要将第一操作页面呈现的分类信息添加到所有呈现的应用中,则用户可以长按第一操作页面,为这些应用中对应的类属性添加对应的分类信息。 另外,用户可以对呈现的应用进行选择,移动终端可以根据用户的选择,将n条分类信息中的至少两条分类信息添加到选择的第二应用中对应的类属性中。 第一个用户。 [0107] 例如,在用户对第一操作页面进行操作后,例如,用户在图6所示的第一操作页面上点击第一页面元素后,移动终端可以对第一操作页面呈现的可分类信息进行添加处理 当第一操作页面呈现的分类信息可以添加到多个应用时,可以呈现图7所示的第一操作提示项。 如图7所示,第一操作提示项包括提示项“添加事件到待办事项”和提示项“添加事件到通讯录”。 在用户触发第一操作提示项后,移动终端可以将第一操作页面呈现的分类信息添加到相应应用中的相应类属性中。 例如,在用户触发提示项“添加事件到通讯录”后,移动终端可以将图6所示的联系人和电话号码添加到通讯录中。 或者,在用户触发提示项“添加事件到待办事项”后,移动终端可以将图6所示的四种信息添加到待办事项中。 [0108] 在本申请的另一个实施例中,在移动终端将事件通知消息中的m条可分类信息添加到第二应用中的m类属性之前,该方法还可以包括: [0109] 移动终端在第二应用中的m类属性对应的已有内容中查找与m条可分类信息相同的内容; 和 [0110] 移动终端根据用户对同一信息内容的操作,对同一内容进行第一处理,第一处理包括删除处理。 [0111]对第二应用中与m条可分类信息相同的内容进行删除处理,避免重复信息存储,释放移动终端的存储空间。 另外,方便用户阅读和搜索相关内容,提高用户体验。 [0112] 具体的,第二应用可以包括与n条可分类信息相关的内容,移动终端可以在第二应用中对应m类属性的m条内容中查找与n条可分类信息相同的内容。 . 例如,当第二应用包括待办事项应用和通讯录时,移动终端可以分别将n条可分类信息与时间、地址、姓名、地址等关键词的信息内容进行匹配。 待办事项应用中用户记录的个人姓名,以及通讯录中的联系人、电话号码、邮箱地址等关键词的信息内容。 通过上述匹配操作,可以得到第二应用中与n条可分类信息相关的内容。 例如,事件通知消息为短信,当短信中包含两个或两个以上与待办事项或通讯录中的内容相同的文本字符时,匹配成功。 移动终端得到的匹配结果为待办事项或通讯录中的内容包括两个或两个以上与每条可分类信息相同的文本字符。 移动终端在获取到与n条可分类信息相同的内容后,可以在第一操作页面上以第二操作提示项的形式向用户提示第二应用包括的内容为: 与n条可分类信息相同。 用户通过操作第二操作提示项,可以对第二应用中与n条可分类信息相关的内容进行相应的处理,例如删除处理。 [0113] 另外,在上述匹配过程中,移动终端还可以触发相应的互联网资源和服务,以及系统的其他传感器模块,如加速度模块、湿度模块、脉搏模块等进行匹配。 例如,当事件通知消息中包含地址时,移动终端可以触发相应的互联网资源和服务选项,如地图打开、路线规划、现状状态识别等。 例如,通过获取传感器速度,如果检测到用户当前处于驾驶模式,则默认推送路线导航驾驶模式,或者如果检测到用户当前处于禁止状态,则打车应用 服务被推送。 [0114] 因此,根据本申请中获取移动终端事件信息的方法,移动终端在获取并识别分类信息时,在第二应用中查找与分类信息相同的内容,使得 用户在向第二应用添加事件通知消息中的可分类信息之前,可以对第二应用中与可分类信息相同的内容进行删除处理,从而提高第二应用中内容的可理解性, 并改善用户体验。 [0115] 本申请实施例中,当移动终端查找到与n条可分类信息相同的内容时,移动终端可以呈现提示项“检查已有内容”(即第二操作提示项的示例) ) 在第一个操作页面上。 [0116]例如,参考图1,移动终端接收到关于部门年中活动主题策划讨论主题的通知消息后,根据预定义的类模板获取n条可分类信息,例如,关于部门年中活动主题策划讨论的内容。 如图3或图6所示的第一操作页面,移动终端在确定第二应用后,在待办事项或通讯录等第二应用中查找与至少一条可分类信息相同的内容 在 n 条可分类信息中。 当移动终端查找到与至少一条可分类信息相同的内容时,移动终端向用户呈现如图8所示的第一操作页面。 [0117] 在移动终端呈现包括第二操作提示项的第一操作页面后,用户可以对第二操作提示项进行操作,例如可以通过点击第二操作提示项查看m条内容中的内容 ,即与n条分类信息中的至少一条分类信息相同。 若第二应用包括与n条分类信息中的至少一条分类信息相同的内容,则在用户触发第二操作提示项后,移动系统呈现第二子操作提示项。 第二子操作提示项表示与n条分类信息中的至少一条分类信息相同的内容所在的第二应用。 通过操作第二子操作提示项,用户可以在期望的应用中查看n条分类信息中与至少一条分类信息相同的内容。 [0118] 例如,结合图8所示的第一操作页面,在用户触发提示项“查看已有内容”后,移动终端呈现图9所示的第二子操作提示项。第二子操作提示项包括: 提示项“在通讯录中查看匹配的内容”和提示项“在待办事项列表中查看匹配的内容”。 在用户触发第二子操作提示项后,例如,在用户触发“查看通讯录中匹配的内容”提示项后,移动系统开启通讯录应用,用户可以在通讯录中进行查看 ,与n条分类信息中的至少一条分类信息相同的内容。 [0119] 可选的,在用户操作第一操作页面后,移动终端可以根据用户在第一操作页面上的操作,呈现第三操作提示项。 第三操作提示项提示用户对第二应用中与n条分类信息中的至少一条分类信息相同的内容进行第一处理。 用户操作第三操作提示项,使得移动终端可以对第二应用中与n条分类信息中的至少一条分类信息相同的内容进行第一处理。 [0120] 可选的,第一处理操作包括取消事件提醒操作和删除操作,或者取消事件提醒操作或删除操作。 [0121] 例如,如图10所示,用户在第一操作页面对第一页面元素进行操作后,移动终端可以向用户呈现如图11所示的第三操作提示项。 如图11所示,第三操作提示项包括提示项“是否取消同一待办事项提醒”和提示项“删除原待办事项记录”。 在用户触发图11所示的提示项后,移动终端进行与用户触发的提示项对应的处理。 例如,在用户触发提示项“是否取消同一待办事件提醒”后,移动终端系统取消明天上午10点A路18号相关事件的提醒,或者 叶敏。 [0122]对第二应用中与m条可分类信息相同的内容进行删除处理,避免重复信息存储,释放移动终端的存储空间。 另外,方便用户阅读和搜索相关内容,提高用户体验。 [0123] 以上结合图2至图11详细描述了根据本申请实施例的候选项呈现方法,下面结合图12详细描述根据本申请实施例的移动终端。 [0124] 图12是移动终端的示意框图 20 根据本申请的一个实施例。 如图12所示,移动终端 20 包括一个接收单元 21 , 一个获取单元 22 , 决定单位 23 , 和一个加法单元 24 . [0125] 接收单位 21 用于接收第一应用的事件通知消息。 [0126] 获取单位 22 用于根据预定义的类模板获取事件通知消息中的n条可分类信息。 n条可分类信息分别对应n个类属性,类模板包括可分类信息与类属性的分类关系,n为大于等于2的整数。 [0127] 决定单位 23 用于根据预设规则根据n类属性确定第二应用。 第二应用包括m类属性,包括m类属性的集合是包括n类属性的集合的子集,m为大于等于2且不大于n的整数。 [0128] 添加单元 24 用于将事件通知消息中的m类属性分别对应的m条可分类信息添加到第二应用中的m类属性中。 [0129] 在本申请实施例中,移动终端可以通过预先定义的类模板获取事件通知消息中包含的多条可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包括至少两个分类信息对应的类别属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个分类信息中的至少两个分类信息添加到第二应用中对应的类属性中。 从而可以降低用户将所有可分类信息逐条添加的操作复杂度,提高信息添加效率,提高用户体验。 [0130] 应该理解为移动端 20 可以用于执行图2所示方法中的流程和/或步骤,为避免重复,此处不再赘述。 [0131] 还应当理解,移动终端 20 这里以功能模块的形式实现。 此处的术语“单元”可以是专用集成电路(ASIC)、电子电路、被配置为执行一个或多个软件或固件的处理器(例如,共享处理器、专用处理器或分组处理器) 程序、存储器、组合逻辑电路和/或用于支持所描述的功能的另一个合适的组件。 [0132] 如图13所示,本申请实施例还提供了一种移动终端 40 . 如图13所示,移动终端 40 可能具体包括射频 (RF) 电路等组件 41 , 一段记忆 42 , 一个输入单元 43 , 显示单元 44 , 一个音频单元 45 , 处理器 46 , 电源 47 , 和一个接口 48. 本领域技术人员可以理解,图13所示移动终端的结构并不构成对移动终端的限制。 移动终端具体可以包括比图13所示更多或更少的组件,或者组合一些组件,或者具有不同的组件排列。 [0133] 射频电路 41 用于接收第一应用的事件通知消息。 处理器 46 用于根据预先定义的类模板获取事件通知消息中的n条可分类信息,所述n条可分类信息分别对应n个类属性,所述类模板包括可分类信息与类的分类关系 属性,n为大于等于2的整数; 根据预设规则,根据n类属性确定第二应用,第二应用包括m类属性,包括m类属性的集合是包括n类属性的集合的子集,m为 大于或等于2且不大于n的整数; 将事件通知消息中的m个类别属性分别对应的m条可分类信息添加到第二应用中的m个类别属性中。 [0134] 因此,在本申请中,移动终端可以通过预定义的类模板获取事件通知消息中包含的多个可分类信息。 另外,移动终端可以根据预设规则获取多个分类信息中包含一个或多个分类信息对应的类属性的应用程序(即第二应用程序)。 进一步地,移动终端可以自动将多个可分类信息中的一个或多个信息添加到第二应用中对应的类别属性中。 从而可以降低用户将所有可分类信息逐条添加的操作复杂度,提高信息添加效率,提高用户体验。 [0135] 应当理解,在本申请实施例中,射频电路 41 可以用于在信息收发过程或通话过程中接收和发送信号。 特别地,在接收到下行链路信号后,RF电路 41 发送下行信号给处理器 46 进行处理,并发送上行信号。 射频电路通常包括但不限于天线、至少一个放大器、收发器、耦合器、低噪声放大器(LNA)、双工器等。 此外,射频电路 41 还可以通过无线通信与网络和另一设备进行通信。 无线通信可以使用任何通信标准或协议,包括但不限于全球移动通信系统(GSM)、通用分组无线电服务(GPRS)、码分多址(CDMA)、宽带码分多址( WCDMA)、长期演进(LTE)、电子邮件、短消息服务(SMS)等。 [0136] 记忆 42 可以被配置为存储软件程序和模块。 处理器 46 通过运行存储在内存中的软件程序和模块进行移动终端的各种功能应用和信号处理 42 . 记忆 42 可以主要包括程序存储区和数据存储区。 程序存储区可以存储智能手机的操作系统、至少一种功能所需的应用程序(例如信息输入功能所需的应用程序,即输入法应用程序、声音播放功能或图像播放功能) 功能)等。 数据存储区可以存储在使用智能手机时创建的数据(例如,当用户使用输入法时创建的词典、音频数据、图像数据或电话簿)等。 此外,内存 42可以包括高速随机存取存储器,或者可以包括非易失性存储器,例如至少一个磁盘存储设备、闪存或另一易失性固态存储设备。 [0137] 输入单元 43 可以用于:接收输入的数字或字符信息,产生与移动终端的用户设置和功能控制相关的按键信号输入。 具体来说,输入单元 43 可能包括触摸屏 431 和另一个输入设备 432 . 触摸屏 431 也称为触摸屏,可以采集触摸操作(例如用户在触摸屏上或触摸屏附近的操作 431 通过使用任何适当的物体或配件,如手指或手写笔)由用户在触摸屏上或触摸屏附近执行 431 ,并通过预设程序驱动相应的连接设备。 可选地,触摸屏 431 可以包括两部分:触摸检测装置和触摸控制器。 触摸检测装置检测用户的触摸位置,检测触摸操作带来的信号,并将该信号传送给触摸控制器。 触摸控制器接收来自触摸检测装置的触摸信息,将触摸信息转换为接触坐标,将接触坐标发送给处理器 46 ,并接收并执行处理器发送的命令 46 . 此外,触摸屏 431 可以采用电阻式、电容式、红外线式、表面声波式等多种方式实现。 另一个输入设备 432 可以包括但不限于物理键盘、功能键(如音量控制键或电源键)、轨迹球、鼠标、摇杆等中的一种或多种。 [0138] 显示器 44 可以用于显示移动终端的各种菜单,以及用户输入的信息或为用户提供的信息。 显示单元 44 可能包括一个显示面板 441 . 可选地,显示面板 441 可以以诸如液晶显示器(LCD)或有机发光二极管(OLED)的形式来配置。 此外,触摸屏 431 可能会覆盖显示面板 441 . 检测到触摸屏上或触摸屏附近的触摸操作后 431 , 触摸屏 431 将触摸操作传送给处理器 46 以确定触摸事件的类型。 然后,处理器 46 在显示面板上提供相应的视觉输出 441 基于触摸事件的类型。 虽然触摸屏 431 和显示面板 441 图13中的智能手机作为两个独立的组件实现输入输出功能,在一些实施例中,触摸屏 431 和显示面板 441 可以集成实现移动终端的输入输出功能。 [0139] 音频单元 45 包括一个音频电路 451 , 一个扬声器 452 , 和一个麦克风 453 . 音频单元 45 可以在用户和移动终端之间提供音频接口。 音频电路 451 可以将接收到的音频数据转换成电信号并将电信号传输到扬声器 452 , 和扬声器 452 将电信号转换为声音信号并输出​​声音信号。 此外,麦克风 453 将采集到的声音信号转换成电信号,音频电路 451 接收电信号,将电信号转换成音频数据,输出音频数据给射频电路 41 将音频数据发送到例如另一个移动终端,或者将音频数据输出到存储器 42 进行进一步处理。 [0140] 处理器 46 是移动终端的控制中心,通过各种接口和线路连接到整个移动终端的各个部分,通过运行或执行存储在内存中的软件程序和模块实现移动终端的各种功能和数据处理 42并通过调用存储在内存中的数据 42 ,实现移动终端的相应功能。 可选地,处理器 46 可能包括一个或多个处理单元。 可选地,应用处理器和调制解调器处理器可以集成到处理器中 46 其中,应用处理器主要处理操作系统、用户界面、应用程序等,调制解调器处理器主要处理无线通信。 可以理解,上述调制解调器处理器可以不集成到处理器中 46 . [0141] 移动终端还包括电源 47 (如电池)为组件供电。 优选地,电源可以逻辑地连接到处理器 46 通过电源管理系统实现充放电管理、用电管理等功能。 [0142] 界面 48 可以用于:连接其他设备,在移动终端与其他设备之间传输数据。 [0143] 可选的,移动终端还可以包括图13中未示出的无线保真(Wi-Fi)模块、蓝牙模块等,本申请实施例不再赘述。 [0144] 应该理解为移动端 40 本申请实施例中可以对应移动终端 20 在本申请实施例中,可以与本申请方法实施例中的移动终端相对应。 为简洁起见,在此不再赘述。 [0145] 应当理解,整个说明书中所提及的“一个实施例”或“一个实施例”是指与该实施例相关的特定特征、结构或特性包含在本申请的至少一个实施例中。 因此,贯穿说明书出现的“在一个实施例中”或“在一个实施例中”并不指代相同的实施例。 此外,这些特定的特征、结构或特性可以通过任何适当的方式组合在一个或多个实施例中。 [0146] 本说明书中的术语“和/或”仅描述了描述关联对象的关联关系,表示可以存在三种关系。 例如,A和/或B可能代表以下三种情况:只有A存在,A和B都存在,只有B存在。 另外,本说明书中的字符“/”一般表示关联对象之间是一种“或”的关系。 [0147] 应当理解,上述过程的序号并不代表本申请各实施例中的执行顺序。 进程的执行顺序应当根据进程的功能和内部逻辑来确定,不应理解为对本申请实施例的实现过程的限制。 [0148] 本领域普通技术人员可以知悉,结合本说明书所公开的实施例中所描述的示例,方法步骤和单元可以通过电子硬件、计算机软件或其组合来实现。 为了清楚地描述硬件和软件之间的互换性,以上根据功能概括地描述了各个实施例的步骤和组成。 这些功能是通过硬件还是软件来实现,取决于技术方案的特定应用和设计约束条件。 对于每个特定的应用,本领域的普通技术人员可以采用不同的方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。 [0149]本说明书所公开的实施例所描述的方法或步骤可以通过硬件、处理器执行的软件程序或其组合来实现。 软件程序可以设置在随机存取存储器(RAM)、存储器、只读存储器(ROM)、电可编程只读存储器(EPROM)、电可擦除可编程只读存储器(EEPROM)、 寄存器、硬盘、可移动磁盘、光盘只读存储器(CD-ROM)或本领域已知的任何其他形式的存储介质。 [0150] 在本申请提供的几个实施例中,应当理解,所公开的系统、装置和方法可以有其他的实现方式。 例如,所描述的装置实施例仅仅是一个示例。 例如,单元划分仅仅是逻辑功能划分,在实际实现中可以是其他划分。 例如,可以将多个单元或组件组合或集成到另一个系统中,或者可以忽略或不执行某些特征。 [0151] 描述为独立组件的单元可以是物理上独立的也可以不是物理上独立的,作为单元显示的组件可以是物理单元也可以不是物理单元,可以位于一个位置,也可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。 [0152] 另外,本申请实施例中的各功能单元可以集成为一个处理单元,也可以各单元在物理上单独存在,或者两个或多个单元集成为一个单元。 [0153] 参照附图并结合优选实施例对本申请进行了详细说明,但并不限于此。 在不脱离本申请的精神和实质的情况下,本领域的普通技术人员可以对本申请中的实施例进行各种等同修改或替换,这些修改或替换均属于本申请保护的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106686240A(String), CN106686240B(String), US10827055B2(String), US20190327356A1(String), WO2018120882A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106686240A(String), CN106686240B(String), US10827055B2(String), US20190327356A1(String), WO2018120882A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10827055B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106686240A(String), CN106686240B(String), US10827055B2(String), US20190327356A1(String), WO2018120882A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271659(Integer), CN106686240A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271659(Integer), CN106686240B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271659(Integer), US10827055B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271659(Integer), US20190327356A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:01.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271659(Integer), WO2018120882A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10827055B2(String), US10827055B2(String), 1604332800(Integer), 271659(Integer), 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185975(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185975(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185975(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185975(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9814022B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.968 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.968 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:02.968 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US9814022B2(String), The present invention discloses a network accessing method for a mobile terminal, and a mobile terminal. In some implementations of the present invention, a mobile terminal reads a help request for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 本发明公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一移动终端接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US14/801612(String), 1436976000(Integer), US9814022B2(String), 1509984000(Integer), 1509984000(Integer), 美国(String), 4(Integer), 6(Integer), 17(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185976(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\0d3ddaf3c1c34839b2913e0b19d78513.png(String), 185976(Integer), 0d3ddaf3c1c34839b2913e0b19d78513.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.205 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US9814022B2(String), The present invention discloses a network accessing method for a mobile terminal, and a mobile terminal. In some implementations of the present invention, a mobile terminal reads a help request for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 本发明公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一移动终端接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US14/801612(String), 1436976000(Integer), US9814022B2(String), 1509984000(Integer), 1509984000(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 17(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2(String), \20230420\0d3ddaf3c1c34839b2913e0b19d78513.png(String), 12(Integer), 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 1. A network accessing method for a mobile terminal, comprising:reading a help request for accessing a network by the mobile terminal;establishing a radio resource control (RRC) connection to a base station of the network;applying to the base station to become a base-station mobile terminal;receiving a beacon channel resource, a broadcast channel resource, and an access resource that are allocated by the base station;sending a beacon channel on the beacon channel resource allocated by the base station;sending a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises the access resource; andreceiving an access request of the mobile terminal on the access resource.(String), 1.根据权利要求9所述的非暂时性计算机存储介质,其中接收网络基站分配的信标信道资源、广播信道资源和接入资源的步骤还包括:接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 2. The network accessing method for a mobile terminal according to claim 1, further comprising:connecting the mobile terminal to the network.(String), 12.根据权利要求9所述的非暂时性计算机存储介质,还包括:成为基站移动终端;和向网络发送分配请求。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 3. The network accessing method for a mobile terminal according to claim 1, wherein the steps of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 4. The network accessing method for a mobile terminal according to claim 1, further comprising:becoming a base-station mobile terminal; andsending an allocation request to the network.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 5. A mobile terminal, comprising an input apparatus, an output apparatus, a memory, and a processor, wherein the processor performs the following steps:reading a help request for accessing a network by another mobile terminal;establishing a radio resource control (RRC) connection to a base station of the network;sending a request for becoming a base-station mobile terminal to the network;receiving a beacon channel resource, a broadcast channel resource, and an access resource that are allocated by the base station of the network;sending a beacon channel on the beacon channel resource allocated by the base station of the network;sending a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises the access resource; andreceiving an access request of the another mobile terminal on the access resource after the another mobile terminal synchronizes with the mobile terminal according to the beacon channel, and, after synchronizing with the mobile terminal, reads the broadcast signal to obtain the access resource.(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 6. The mobile terminal according to claim 5, further comprising:connecting the another mobile terminal to the network.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 7. The mobile terminal according to claim 5, wherein the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 8. The mobile terminal according to claim 5, further comprising:becoming a base-station mobile terminal; andsending an allocation request to the network.(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 9. A non-transitory computer storage medium, wherein the computer storage medium stores a program, and the program is configured to perform a network accessing method for a mobile terminal, wherein the method comprises:reading a help request for accessing a network by the mobile terminal;establishing a radio resource control (RRC) connection to a base station of the network;applying to the base station of the network to become a base-station mobile terminal;receiving a beacon channel resource, a broadcast channel resource, and an access resource that are allocated by the base station of the network;sending a beacon channel on the beacon channel resource allocated by the base station;sending a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises the access resource; andreceiving an access request of the mobile terminal on the access resource.(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 10. The non-transitory computer storage medium according to claim 9, further comprising:connecting the mobile terminal to the network.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 11. The non-transitory computer storage medium according to claim 9, wherein the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185976(Integer), 12. The non-transitory computer storage medium according to claim 9, further comprising:becoming a base-station mobile terminal; andsending an allocation request to the network.(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.548 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185976(Integer), [0001]This application is a continuation of International Application No. PCT/CN2013/070522, filed on Jan. 16, 2013, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present invention relates to the field of communications technologies, and specifically, to a network accessing method for a mobile terminal, and a mobile terminal. BACKGROUND [0003]In a current cellular system, a base station includes a macro base station and a micro base station. Because distances from different mobile terminals to the base station are different, interference to different mobile terminals is different, which causes channel quality of different mobile terminals to be different. In addition, in some cases, some mobile terminals may not be covered by a base station, for example, a mobile terminal falls in a coverage hole area, or a base station is damaged for some special reasons, such as an earthquake. Such a mobile terminal that is not covered needs another mobile terminal to help access a network. A mobile terminal that is not covered or weakly covered is defined as an access mobile terminal, and a mobile terminal that can connect to a base station to access a network and can help the access mobile terminal access the network is defined as a base-station mobile terminal. [0004]Because the access mobile terminal needs the base-station mobile terminal to help access a network, the access mobile terminal needs to discover the base-station mobile terminal and also needs to establish a connection to the base-station mobile terminal, and in this way, a final aim of accessing the network by the access mobile terminal can be implemented. Currently, an existing discovering manner for mobile terminals is mainly a manner in which mobile terminals autonomously discover each other. Each mobile terminal sends a beacon channel on a specific resource, so as to discover each other by checking beacon channels of each other. [0005]Because a beacon channel resource is limited, it is necessary to check, before a mobile terminal sends a beacon channel, whether there is a beacon channel resource, and if there is a beacon channel resource, the mobile terminal sends the beacon channel. In this way, a disadvantage of a distributed manner for autonomously using a beacon channel by a mobile terminal is that a mobile terminal may use a beacon channel but does not establish a connection to another mobile terminal, thereby wasting the beacon channel. SUMMARY [0006]Embodiments of the present invention provide a network accessing method for a mobile terminal, and a mobile terminal, which can more effectively use a beacon channel resource. [0007]According to a first aspect, the present invention provides a network accessing method for a mobile terminal, including reading a help request used for accessing a network by the mobile terminal; sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network. [0008]In a first possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0009]In a second possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0010]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes receiving the access request of the mobile terminal on the access resource, and assisting the mobile terminal in completing access to the network. [0011]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0012]In a fifth possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0013]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes receiving the access request of the mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the mobile terminal in completing access to the network. [0014]According to a second aspect, the present invention provides a mobile terminal, including a reading module, configured to read a help request used for accessing a network by another mobile terminal; a broadcasting module, configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and a receiving module, configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0015]In a first possible implementation manner, the broadcasting module includes: a network connecting submodule, configured to establish a RRC connection to the base station of the network, send a request for becoming a base-station mobile terminal to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0016]In a second possible implementation manner, the mobile terminal further includes a base-station module, configured to make the mobile terminal become a base-station mobile terminal; and the broadcasting module includes: a network connecting submodule, configured to send an allocation request to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0017]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the network connecting submodule receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0018]In a fourth possible implementation manner, the broadcasting module includes a network connecting submodule, configured to camp on the base station of the network, acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and a broadcasting submodule, configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0019]With reference to the fourth possible implementation manner, in a fifth possible implementation manner, the network connecting submodule is further configured to, after the receiving module receives the access request, access the base station and request to become a base-station mobile terminal, so as to assist the another mobile terminal in accessing the network. [0020]According to a third aspect, the present invention provides a computer storage medium, where the computer storage medium may store a program, and the program is used to perform the steps according to the first aspect of the present invention or any one of the first to the sixth possible implementation manners of the first aspect. [0021]According to a fourth aspect, the present invention provides a mobile terminal, including an input apparatus, an output apparatus, a memory, and a processor, where the processor performs the following steps: reading a help request used for accessing a network by another mobile terminal; sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network. [0022]In a first possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes establishing a RRC connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0023]In a second possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0024]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes: receiving the access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in completing access to the network. [0025]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step, which is performed by the processor, of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes: receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0026]In a fifth possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0027]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes receiving the access request of the another mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the another mobile terminal in completing access to the network. [0028]According to the network accessing method for a mobile terminal, and the mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that another mobile terminal connects to the mobile terminal on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. BRIEF DESCRIPTION OF DRAWINGS [0029]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0030]FIG. 1 is a schematic diagram of an application environment according to an embodiment of the present invention; [0031]FIG. 2 to FIG. 4 are schematic flowcharts of a network accessing method for a mobile terminal according to embodiments of the present invention; and [0032]FIG. 5 to FIG. 8 are schematic diagrams of a mobile terminal according to embodiments of the present invention. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0033]The following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0034]Referring to FIG. 1, FIG. 1 is a schematic diagram of an application environment of a network accessing method for a mobile terminal according to an embodiment of the present invention. In an implementation manner of the present invention, the network accessing method for a mobile terminal is used in a mobile communications system, for example, a Long Term Evolution (LTE) network, and a network under the 3rd Generation Partnership Project (3GPP). In some implementation manners of the present invention, the network accessing method for a mobile terminal may also be used in a wireless system. A network shown in FIG. 1 is a mobile communications system network, including a base station 30, where the base station 30 includes a macro base station (only one macro base station is used as an example in FIG. 1) and a micro base station (only one micro base station is used as an example in FIG. 1). A mobile terminal 10 is in coverage of the base station 30 and can access a network; and a mobile terminal 20 is not in the coverage of the base station 30, and cannot access the network, and therefore, the mobile terminal 10 is needed to assist the mobile terminal 20 in accessing the network. The mobile terminal 20 that is not covered or weakly covered is defined as an access mobile terminal, and the mobile terminal 10 that can connect to the base station 30 to access the network and can help the access mobile terminal 20 access the network is defined as a base-station mobile terminal. [0035]It should be noted that, in specific implementation, a function of a beacon channel is to make a terminal be discovered by another terminal. Therefore, in specific implementation, a resource allocated by the base station in the present invention is not merely limited to a beacon channel, and code that can be used to discover a terminal can be allocated by the base station in the present invention. That is, in this embodiment of the present invention, a beacon channel is merely used to indicate code used to discover a terminal, but is not used to limit use of other code having a terminal discovering function in this embodiment of the present invention. [0036]It may be understood that, because a base-station mobile terminal and an access mobile terminal move, the base-station mobile terminal may also become an access mobile terminal, and the access mobile terminal may also become a base-station mobile terminal. [0037]With reference to FIG. 1 and referring to FIG. 2, a network accessing method for a mobile terminal according to a first embodiment of the present invention includes: [0038]S201. Read a help request used for accessing a network by the mobile terminal 20. [0039]In this embodiment, the mobile terminal 20 is an access mobile terminal 20 that cannot access a network, and therefore, sends, on an agreed resource, the help request used for accessing a network, where the agreed resource may be, for example, a first timeslot of a frequency. By means of scanning, the mobile terminal 10 reads, on the agreed resource, the help request used for accessing a network by the mobile terminal 20. [0040]S202. Send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. [0041]In some implementation manners of the present invention, the mobile terminal 10 sends the beacon channel on the beacon channel resource allocated by the base station of the network. For example, there are resources of eight subframes from 0 to 7, and a second subframe is idle. In this case, the base station may allocate the second subframe to the mobile terminal 10, and the mobile terminal 10 may send a beacon channel in the second subframe and send a broadcast signal on a broadcast channel resource corresponding to the second subframe, for example, a third subframe, where the broadcast signal includes an access resource, for example, a fifth subframe. [0042]S203. Receive an access request of the mobile terminal 20 on the access resource, and assist the mobile terminal 20 in accessing the network. [0043]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0044]With reference to FIG. 1 and referring to FIG. 3, a network accessing method for a mobile terminal according to a second embodiment of the present invention includes: [0045]S301. The access mobile terminal 20 sends a request for requesting the mobile terminal 10 to help access a network. [0046]S302. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0047]S303. The mobile terminal 10 establishes a radio resource control (RRC) protocol connection to the base station 30 of the network, and sends a request for becoming a base-station mobile terminal to the base station 30. [0048]In this embodiment of the present invention, if the mobile terminal 10 intends to become a base-station mobile terminal after reading the help request of the access mobile terminal 20, the mobile terminal 10 sends the request for becoming a base-station mobile terminal to the base station 30. [0049]In some embodiments of the present invention, the mobile terminal 10 may also have become a base-station mobile terminal; in this case, the mobile terminal 10 sends only an allocation request to the base station 30. [0050]S304. The base station 30 allocates a beacon channel resource, a broadcast channel resource, and an access resource to the mobile terminal 10. [0051]In this embodiment of the present invention, the base station 30 allocates the beacon channel resource, the broadcast channel resource, and the access resource to the mobile terminal 10 by using radio resource control protocol signaling. [0052]In some implementation manners of the present invention, the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station 30 include a timeslot resource, a frequency resource, a code channel resource, and the like. [0053]In this case, the mobile terminal 10 becomes a base-station mobile terminal. [0054]S305. The mobile terminal 10 sends a beacon channel on the beacon channel resource allocated by the base station 30, and sends a broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0055]Step S303 to S305 are specific implementation steps of step S202 in FIG. 2. [0056]S306. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0057]S307. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0058]After receiving the access request of the access mobile terminal 20, the base-station mobile terminal 10 may help the access mobile terminal 20 complete access to the network, that is, the base station 30. [0059]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station 30, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0060]With reference to FIG. 1 and referring to FIG. 4, a network accessing method for a mobile terminal according to a third embodiment of the present invention includes: [0061]S401. The access mobile terminal 20 sends a request for requesting the base-station mobile terminal 10 to help access a network. [0062]S402. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0063]S403. The mobile terminal 10 camps on the base station 30, and acquires a beacon channel resource set and an access resource set by means of broadcast of the base station 30. [0064]S404. The mobile terminal 10 sends a beacon channel on an idle beacon channel resource in the beacon channel resource set, and sends a broadcast signal on a broadcast channel resource, where the broadcast signal includes an access resource. [0065]The mobile terminal 10 checks whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, and if there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the mobile terminal 10 sends the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sends the broadcast signal on a corresponding broadcast channel resource, where the broadcast signal includes the access resource. [0066]Step S403 to step S404 are specific implementation manners of step S202 in FIG. 2. [0067]S405. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0068]S406. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0069]S407. The mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, so as to assist the access mobile terminal in completing access to the network. [0070]According to the network accessing method for a mobile terminal, it is checked whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the beacon channel is sent on the idle beacon channel resource in the beacon channel resource set, and the broadcast signal is sent on a broadcast channel resource corresponding to the idle beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses a network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. In addition, only after receiving the access request of the access mobile terminal 20, the mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, thereby avoiding a waste of a resource. [0071]To better implement the foregoing solutions in the embodiments of the present invention, a related apparatus configured to cooperate to implement the foregoing solutions is provided in the following. [0072]Referring to FIG. 5, a mobile terminal 50 according to an embodiment of the present invention includes a reading module 500, a broadcasting module 510, and a receiving module 520. The reading module 500 is configured to read a help request used for accessing a network by another mobile terminal. The another mobile terminal is not covered by a network or weakly covered by a network, and therefore the another mobile terminal requests the mobile terminal 50 to help access the network. [0073]The broadcasting module 510 is configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The receiving module 520 is configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0074]Referring to FIG. 6, the broadcasting module 510 includes a network connecting submodule 511 and a broadcasting submodule 512. [0075]In some implementation manners of the present invention, the network connecting submodule 511 is configured to send a request for becoming a base-station mobile terminal to the network and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network. The broadcasting submodule 512 is configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0076]In some implementation manners of the present invention, the network connecting submodule 511 receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0077]In some implementation manners of the present invention, the network connecting submodule 511 is configured to camp on the base station of the network, and acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes the idle beacon channel resource, and the access resource set includes the access resource. The broadcasting submodule 512 is configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes the access resource. [0078]In some implementation manners of the present invention, the network connecting submodule 511 is further configured to, after the receiving module receives the access request, access the base station and request to become a base-station mobile terminal, so as to assist the another mobile terminal in accessing the network. [0079]It may be understood that the mobile terminal 50 in this embodiment may be, for example, a computer, a mobile phone, or a tablet computer. [0080]It may be understood that, functions of all function modules of the mobile terminal 50 in this embodiment may be specifically implemented according to the methods in the foregoing first(String), [0001] 本申请是 2013 年 1 月 16 日提交的国际申请号 PCT/CN2013/070522 的延续,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及通信技术领域,具体涉及一种移动终端的网络接入方法及移动终端。 背景 [0003] 在目前的蜂窝系统中,基站包括宏基站和微基站。 由于不同移动终端到基站的距离不同,对不同移动终端的干扰不同,从而导致不同移动终端的信道质量不同。 另外,在某些情况下,一些移动终端可能不在基站的覆盖范围内,例如移动终端落入覆盖盲区,或者由于地震等特殊原因导致基站损坏等。 这种未被覆盖的移动终端需要另外的移动终端帮助接入网络。 将未覆盖或弱覆盖的移动终端定义为接入移动终端,能够连接基站接入网络并帮助接入移动终端接入网络的移动终端定义为基站 移动终端。 [0004] 由于接入移动终端需要基站移动终端帮助接入网络,因此接入移动终端需要发现基站移动终端,同时也需要与基站移动终端建立连接,这种方式 ,可以实现接入移动终端接入网络的最终目的。 目前,现有的移动终端发现方式主要是移动终端自主发现对方的方式。 每个移动终端在特定资源上发送信标信道,以便通过检查彼此的信标信道来相互发现。 [0005] 由于信标信道资源有限,移动终端在发送信标信道之前,需要检查是否有信标信道资源,如果有信标信道资源,则移动终端发送信标信道。 这样,移动终端自主使用信标信道的分布式方式的缺点是移动终端可以使用信标信道但不与其他移动终端建立连接,从而浪费信标信道。 概括 [0006] 本发明实施例提供一种移动终端的网络接入方法及移动终端,能够更有效地利用信标信道资源。 [0007] 第一方面,本发明提供一种移动终端的网络接入方法,包括读取移动终端接入网络的帮助请求; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收移动终端对接入资源的接入请求,协助移动终端接入网络。 [0008] 在第一种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源还包括与网络基站建立无线资源控制(Radio Resource Control,无线资源控制)连接,向网络发送成为基站移动终端的请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0009]在第二种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源进一步包括成为基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0010] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,接收所述移动终端对所述接入资源的接入请求,并协助所述移动终端接入网络的步骤还包括接收所述接入请求 接入资源上的移动终端,辅助移动终端完成接入网络。 [0011] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述接收网络基站分配的信标信道资源、广播信道资源和接入资源的步骤还包括接收 网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0012] 在第五种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源进一步包括驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲的信标信道资源,所述 访问资源集包括访问资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0013] 结合第五种可能的实现方式,在第六种可能的实现方式中,所述接收移动终端对接入资源的接入请求,并协助移动终端接入网络的步骤还包括接收移动终端的接入请求。 访问资源上的终端; 接入基站并请求成为基站移动终端,以辅助移动终端完成入网。 [0014] 第二方面,本发明提供了一种移动终端,包括:读取模块,用于读取其他移动终端接入网络的帮助请求; 广播模块,用于在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源; 接收模块,用于接收所述另一移动终端对所述接入资源的接入请求,协助所述另一移动终端接入网络。 [0015]在第一种可能的实现方式中,所述广播模块包括: 网络连接子模块,用于与网络基站建立RRC连接,向网络发送成为基站移动终端的请求,并接收beacon 网络基站分配的信道资源、广播信道资源和接入资源; 广播子模块,用于在网络基站分配的信标信道资源上发送信标信道,并在广播信道资源上发送广播信号,广播信号包括接入资源。 [0016] 在第二种可能的实现方式中,所述移动终端还包括基站模块,用于使所述移动终端成为基站移动终端; 广播模块包括:网络连接子模块,用于向网络发送分配请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块,用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号中包括接入资源。 [0017] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,网络连接子模块接收网络基站通过使用 无线电资源控制协议信令。 [0018] 在第四种可能的实现方式中,广播模块包括网络连接子模块,用于驻留在网络的基站上,通过基站的广播获取信标信道资源集和接入资源集,其中,所述beacon 信道资源集包括空闲信标信道资源,接入资源集包括接入资源; 广播子模块,用于在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号包括接入资源 . [0019] 结合第四种可能的实现方式,在第五种可能的实现方式中,网络连接子模块还用于接收模块接收到接入请求后,接入基站,请求成为基站移动终端,因此 以协助其他移动终端接入网络。 [0020] 第三方面,本发明提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行本发明第一方面或第一至至任意一项所述的步骤。 第一方面的第六种可能的实现方式。 [0021] 第四方面,本发明提供一种移动终端,包括输入装置、输出装置、存储器和处理器,所述处理器执行以下步骤: 读取另一移动设备接入网络的帮助请求 终端; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0022]在第一种可能的实现方式中,所述处理器执行在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号的步骤 信道资源,其中广播信号包括接入资源还包括与网络基站建立RRC连接,向网络发送成为基站移动终端的请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0023] 在第二种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括成为基站的移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0024] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述处理器接收所述另一移动终端对所述接入资源的接入请求,并协助所述另一移动终端执行的步骤 接入网络还包括:接收另一移动终端对接入资源的接入请求,协助另一移动终端完成接入网络。 [0025] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述处理器接收所述处理器分配的信标信道资源、广播信道资源和接入资源的步骤。 网络基站还包括:接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0026] 在第五种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括 空闲信标信道资源,接入资源集合包括接入资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0027] 结合第五种可能的实现方式,在第六种可能的实现方式中,所述处理器接收所述其他移动终端对所述访问资源的访问请求,协助所述其他移动终端访问所述访问资源。 网络还包括接收另一移动终端对接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0028]一种移动终端入网方法及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在信标对应的广播信道资源上发送 channel resource,指示接入资源,以便其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入资源。 附图说明 [0029] 为更加清楚地描述本发明实施例中的技术方案,下面对实施例描述中所需要的附图进行简单介绍。 显然,以下描述中的附图仅仅是本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0030] 图1为本发明实施例的应用环境示意图; [0031] 图2至图4是根据本发明实施例的移动终端的网络接入方法的流程示意图; 和 [0032] 图5至图8是根据本发明实施例的移动终端的示意图。 说明性实施例的详细说明 [0033] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 显然,所描述的实施例仅仅是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0034] 请参阅图1,图1为本发明实施例提供的移动终端的网络接入方法的应用环境示意图。 在本发明的一个实施方式中,所述移动终端的入网方法用于移动通信系统,例如长期演进(LTE)网络、第三代合作伙伴计划(3GPP)下的网络。 在本发明的一些实施方式中,该移动终端的网络接入方法还可以用于无线系统中。 图1所示网络为移动通信系统网络,包括基站 30 ,其中基站 30 包括宏基站(图1中仅以一个宏基站为例)和微基站(图1中仅以一个微基站为例)。 移动终端 10 在基站覆盖范围内 30 并且可以访问网络; 和移动终端 20 不在基站覆盖范围内 30 , 无法上网, 因此, 移动终端 10 需要移动端辅助 20 在访问网络时。 手机端 20 未覆盖或弱覆盖定义为接入移动终端,移动终端 10 可以连接到基站 30 接入网络,可以帮助接入移动终端 20 接入网络的移动终端被定义为基站。 [0035] 需要说明的是,在具体实现中,信标信道的作用是使一个终端被另一个终端发现。 因此,在具体实施中,本发明基站分配的资源并不仅限于信标信道,本发明基站可以分配可用于发现终端的代码。 即本发明实施例中,信标信道仅用于指示用于发现终端的代码,并不用于限制本发明实施例中使用其他具有终端发现功能的代码。 [0036]可以理解的是,由于基站移动终端和接入移动终端移动,因此基站移动终端也可能成为接入移动终端,接入移动终端也可能成为基站移动终端。 [0037] 结合图1并参考图2,本发明实施例一提供的一种移动终端的网络接入方法包括: [0038] 小号 201 . 读取移动终端接入网络的帮助请求 20 . [0039] 本实施例中,移动终端 20 是接入移动终端 20 无法接入网络,因此在约定的资源上发送用于接入网络的帮助请求,该约定的资源例如可以是频率的第一时隙。 手机端扫一扫 10 在约定的资源上读取移动终端接入网络的帮助请求 20 . [0040] 小号 202 . 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0041] 在本发明的一些实施方式中,移动终端 10 在网络基站分配的信标信道资源上发送信标信道。 例如,0到7有8个子帧的资源,第二个子帧空闲。 在这种情况下,基站可以将第二子帧分配给移动终端 10 , 和移动端 10 可以在第二子帧发送信标信道,在第二子帧对应的广播信道资源,例如第三子帧上发送广播信号,该广播信号包括接入资源,例如第五子帧。 [0042] 小号 203 . 接收移动终端的访问请求 20 在接入资源上,协助移动终端 20 在访问网络时。 [0043] 该移动终端的入网方法,在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,以指示 访问资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0044] 结合图1并参考图3,本发明实施例二提供的一种移动终端的网络接入方法包括: [0045] 小号 301 . 接入移动终端 20 发送请求移动端的请求 10 帮助访问网络。 [0046] 小号 302 . 移动端 10 读取接入移动端的帮助请求 20 . [0047] 小号 303 . 移动端 10 建立到基站的无线资源控制 (RRC) 协议连接 30 向基站发送成为基站移动终端的请求 30 . [0048] 本发明实施例中,如果移动终端 10 读取接入移动终端的帮助请求后,打算成为基站移动终端 20 , 移动端 10 向基站发送成为基站移动终端的请求 30 . [0049] 在本发明的一些实施例中,移动终端 10 也可能成为基站移动终端; 在这种情况下,移动端 10 只向基站发送分配请求 30 . [0050] 小号 304 . 基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源10 . [0051] 本发明实施例中,基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源 10 通过使用无线电资源控制协议信令。 [0052] 在本发明的一些实施方式中,基站分配的信标信道资源、广播信道资源和接入资源 30 包括时隙资源、频率资源、码道资源等。 [0053] 在这种情况下,移动端 10 成为基站移动终端。 [0054] 小号 305 . 手机端 10 在基站分配的信标信道资源上发送信标信道 30 ,在广播信道资源上发送广播信号,广播信号中包含接入资源。 [0055] 脚步 303 到小号 305 是步骤S的具体实现步骤 202 在图 2 中。 [0056] 小号 306 . 接入移动终端 20 搜索信标信道,与移动终端同步 10 ,从而读取广播信号,并从广播信号中读取接入资源。 [0057] 小号 307 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0058] 收到接入移动终端的接入请求后 20 , 基站移动终端 10 可以帮助接入移动终端 20 完全接入网络,即基站 30 . [0059] 一种移动终端入网方法,所述信标信道在基站分配的信标信道资源上发送 30 ,在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0060] 结合图1并参考图4,本发明实施例三提供的一种移动终端的网络接入方法包括: [0061] 小号 401 . 接入移动终端 20 发送请求基站移动终端的请求 10 帮助访问网络。 [0062] 小号 402 . 手机端 10 读取接入移动端的帮助请求 20 . [0063] 小号 403 . 手机端 10 基站上的营地 30 , 通过基站的广播获取信标信道资源集和接入资源集 30 . [0064] 小号 404 . 手机端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,在广播信道资源上发送广播信号,该广播信号包括接入资源。 [0065] 手机端 10 检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30 , 如果基站广播的信标信道资源集合中有空闲的信标信道资源 30 , 移动端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在相应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0066] 脚步 403 到步骤 S 404 是步骤S的具体实现方式 202 在图 2 中。 [0067] 小号 405 . 接入移动终端 20 搜索信标信道,与移动终端同步 10,从而读取广播信号,并从广播信号中读取接入资源。 [0068] 小号 406 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0069] 小号 407 . 手机端 10 接入基站 30 请求成为基站移动终端,以协助接入移动终端完成入网。 [0070] 一种移动终端入网方法,检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30 ,信标信道在信标信道资源集合中的空闲信标信道资源上发送,广播信号在空闲信标信道资源对应的广播信道资源上发送,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 另外,只有在接收到接入移动终端的接入请求后 20 , 移动端 10 接入基站 30 请求成为基站移动终端,避免资源浪费。 [0071] 为了更好的实施本发明实施例的上述方案,下面提供一种用于配合实施上述方案的相关装置。 [0072] 参见图5,移动终端 50 根据本发明的实施例包括读取模块 500 , 广播模块 510 , 和一个接收模块 520 . 阅读模块 500 用于读取其他移动终端接入网络的帮助请求。 另一移动终端未被网络覆盖或弱网络覆盖,因此另一移动终端请求该移动终端 50 以帮助访问网络。 [0073] 广播模块 510 用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 接收模块 520 用于接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0074] 参见图6,广播模块 510 包括一个网络连接子模块 511 和一个广播子模块 512 . [0075] 在本发明的一些实施方式中,网络连接子模块 511 用于向网络发送成为基站移动终端的请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0076] 在本发明的一些实施方式中,网络连接子模块 511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0077] 在本发明的一些实施方式中,网络连接子模块 511 用于驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲信标信道资源和接入资源 set 包括访问资源。 广播子模块 512用于在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0078] 在本发明的一些实施方式中,网络连接子模块 511 还用于接收模块接收到接入请求后,接入基站并请求成为基站移动终端,以辅助其他移动终端接入网络。 [0079] 可以理解为移动端 50 本实施例中例如可以为电脑、手机或平板电脑。 [0080] 可以理解为,移动终端的所有功能模块的功能 50 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0081] 上述移动终端 50 在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 50 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0082] 参考图7,移动终端之间的区别 70 根据本发明实施例的移动终端 50 图5所示为基站模块 700 除了阅读模块外,还包括 500 , 广播模块 510 , 和一个接收模块 520 , 其中阅读模块 500 ,广播模块 510 , 接收模块 520 与图5所示的相应模块基本相同,在此不再赘述。 基站模块 700 配置为使移动端 70 成为基站移动终端。 [0083] 广播模块 510 还包括网络连接子模块 511 和广播子模块 512 如图6所示,其中网络连接子模块 511 用于向网络端发送分配请求,接收网络端基站分配的信标信道资源、广播信道资源和接入资源; 和广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0084] 在本发明的一些实施方式中,网络连接子模块 511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0085] 可以理解为移动端 70 本实施例中例如可以为电脑、手机或平板电脑。 [0086] 可以理解为,移动终端的所有功能模块的功能 70 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0087] 上述移动终端 70在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 70 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0088] 本发明实施例还提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行上述方法中描述的移动终端上网方法的部分或全部步骤。 实施例。 [0089] 参见图8,本发明实施例还提供了一种移动终端 80 ,包括一个处理器 810 , 一段记忆 800 , 输入设备 820 , 和一个输出设备 830 (可能有一个或多个处理器 810 在移动端 80 ,图8中以一个处理器为例)。 在本发明的一些实施例中,输入装置 820 , 输出设备 830 , 记忆 800 , 和处理器 810 可以通过使用总线或以其他方式相互连接。 图8中以它们通过总线连接为例。 [0090] 处理器 810 执行以下步骤: 读取另一移动终端用于接入网络的帮助请求; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0091] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:发送 请求成为网络的基站移动终端; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0092] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:成为一个 基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0093] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络还包括:接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络。 完成对网络的访问。 [0094] 在本发明的一些实施方式中,所述步骤由处理器执行 810接收网络基站分配的信标信道资源、广播信道资源和接入资源还包括:接收网络基站分配的信标信道资源、广播信道资源和接入资源。 网络的基站通过使用无线资源控制协议信令。 [0095] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,还包括:驻留在 网络的基站,通过基站广播获取信标信道资源集和接入资源集,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源 ; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0096] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收所述另一移动终端对所述接入资源的接入请求,协助所述另一移动终端接入网络还包括:接收所述另一移动终端对所述接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0097] 可以理解为,移动终端的所有功能模块的功能 80 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0098] 需要说明的是,为便于描述,上述方法实施例均以一系列动作进行描述。 然而,本领域的技术人员应该理解,本发明不限于所描述的动作顺序,因为根据本发明,一些步骤可以以不同的顺序或同时执行。 其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本发明所必须的。 [0099] 在上述实施例中,对各个实施例的描述都各有侧重。 一个实施例中没有详述的部分,可以参见其他实施例的相关描述。 [0100] 综上所述,根据移动终端的入网方法,以及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在相应的广播信道资源上发送 到信标信道资源,指示接入资源,使得其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入 资源。 [0101] 本领域普通技术人员可以理解,上述实施例中方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 存储介质可以包括:只读存储器、随机存取存储器、磁盘或光盘。 [0102]以上对本发明实施例提供的移动终端的网络接入方法及移动终端进行了详细描述。 本说明书中采用具体的例子来说明本发明的原理和实施方式。 上述实施例只是为了帮助理解本发明的方法和核心思想。 此外,对于实施方式和适用范围,本领域的普通技术人员可以根据本发明的思想进行修改。 总之,说明书不应理解为对本发明的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.595 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 13 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.788 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), CN104303526A(String), 192720(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), CN104303526B(String), 192721(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP2947901A1(String), 192722(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP2947901A4(String), 192723(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP2947901B1(String), 192724(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP3624471A1(String), 192725(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:03.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP3624471B1(String), 192726(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US10200973B2(String), 192727(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US20150327216A1(String), 192728(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US20180054802A1(String), 192729(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US9814022B2(String), 192730(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), WO2014110726A1(String), 192731(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104303526B(String), CN104303526B(String), 1548345600(Integer), 270789(Integer), 185073(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 68351(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 68351(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), 华为技术有限公司(String), 255(String), 0(Integer), 1661144373(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25166(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185976(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25166(Integer), 1(Integer), 185976(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185976(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185976(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25166(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:04.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10200973B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US10200973B2(String), Embodiments disclose a network accessing method for a mobile terminal, and a mobile terminal. In some implementation manners of the present invention, a mobile terminal reads a help request used for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 实施例公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一个移动终端用于接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US15/796502(String), 1509033600(Integer), US10200973B2(String), 1549296000(Integer), 1549296000(Integer), 美国(String), 4(Integer), 6(Integer), 19(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | CN102844993A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2 | US9814022B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.259 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.259 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185977(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.407 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\5570f6c83a9f438c8bce7fe2d7ca21b6.png(String), 185977(Integer), 5570f6c83a9f438c8bce7fe2d7ca21b6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.442 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Network accessing method for mobile terminal and mobile terminal(String), 一种移动终端的网络接入方法及移动终端(String), US10200973B2(String), Embodiments disclose a network accessing method for a mobile terminal, and a mobile terminal. In some implementation manners of the present invention, a mobile terminal reads a help request used for accessing a network by another mobile terminal; sends a beacon channel on a beacon channel resource allocated by a base station of the network, and sends a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receives an access request of the another mobile terminal on the access resource, and assists the another mobile terminal in accessing the network.(String), 实施例公开了一种移动终端的网络接入方法及移动终端。 在本发明的一些实施方式中,移动终端读取另一个移动终端用于接入网络的帮助请求; 在网络的基站分配的信标信道资源上发送信标信道,并在与信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。(String), US15/796502(String), 1509033600(Integer), US10200973B2(String), 1549296000(Integer), 1549296000(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 19(Integer), CN101296172A | CN101771720A | CN101841920A | CN101854728A | CN102469410A | CN102790950A | CN102811497A | CN102844993A | US20010036810A1 | US20070183360A1 | US20100167743A1 | US20110300892A1 | US20120315841A1 | US20130016630A1 | US20140078935A1 | US20140171062A1 | US8767705B2 | US9125105B2 | US9814022B2(String), \20230420\5570f6c83a9f438c8bce7fe2d7ca21b6.png(String), 20(Integer), 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 1. A method, comprising:reading, by a first mobile terminal, a help request for accessing a network, wherein the help request is sent by a second mobile terminal;in response to reading the help request, and in response to a determination that the first mobile terminal will allow the second mobile terminal to communicate with the network using a network connection of the first mobile terminal, sending, by the first mobile terminal, a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises an access resource; andreceiving, by the first mobile terminal, an access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 1.一种方法,包括:第一移动终端读取第二移动终端发送的入网帮助请求;响应于读取帮助请求,并且响应于确定第一移动终端将允许第二移动终端使用第一移动终端的网络连接与网络通信,由第一移动终端发送信标在网络基站分配的信标信道资源上信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源;和第一移动终端接收第二移动终端对接入资源的接入请求,允许第二移动终端利用第一移动终端的网络连接与网络进行通信。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 2. The method according to claim 1, wherein sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises:establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, wherein the broadcast signal comprises the access resource.(String), 2.根据权利要求1所述的方法,其中在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,包括:与网络基站建立无线资源控制(RRC)连接,向网络发送成为基站移动终端的请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,以及在广播信道资源上发送广播信号,其中广播信号包括接入资源。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 3. The method according to claim 2, wherein receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises:receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 3.根据权利要求2所述的方法,其中接收第二移动终端对接入资源的接入请求,允许第二移动终端利用第一移动终端的网络连接与网络进行通信,包括:接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 4. The method according to claim 2, wherein receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network comprises:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network using radio resource control protocol signaling.(String), 4.根据权利要求2所述的方法,其中接收网络基站分配的信标信道资源、广播信道资源和接入资源包括:接收网络基站使用无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 5. The method according to claim 1, wherein sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises:becoming a base-station mobile terminal;sending an allocation request to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, wherein the broadcast signal comprises the access resource.(String), 5.根据权利要求1所述的方法,其中在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,包括:成为基站移动终端;向网络发送分配请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,以及在广播信道资源上发送广播信号,其中广播信号包括接入资源。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 6. The method according to claim 1, wherein sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, further comprises:camping on the base station the network, and acquiring a beacon channel resource set and an access resource set from a broadcast of the base station, wherein the beacon channel resource set comprises an idle beacon channel resource, and the access resource set comprises the access resource; andsending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, wherein the broadcast signal comprises the access resource.(String), 6.根据权利要求1所述的方法,其中在网络基站分配的信标信道资源上发送信标信道,在该信标信道资源对应的广播信道资源上发送广播信号,还包括:基站驻留网络,从基站的广播中获取信标信道资源集和接入资源集,其中,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源;和在信标信道资源集合中的空闲信标信道资源上发送信标信道,以及在空闲信标信道资源对应的广播信道资源上发送广播信号,其中广播信号包括接入资源。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 7. The network accessing method for a mobile terminal according to claim 6, wherein receiving the access request of the mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises:receiving the access request of the mobile terminal on the access resource; andaccessing the base station and requesting to become a base-station mobile terminal, to allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 7.根据权利要求6所述的移动终端的网络接入方法,其中接收移动终端对接入资源的接入请求,允许第二移动终端利用第一移动终端的网络连接与网络进行通信,包括:接收移动终端对接入资源的接入请求;和接入基站并请求成为基站移动终端,以允许第二移动终端使用第一移动终端的网络连接与网络进行通信。8、一种移动终端,用于作为第一移动终端,该移动终端包括:输入装置;输出装置;非暂时性记忆;和一个处理器,配置为:读取入网帮助请求,该帮助请求由第二移动终端发送;响应于读取帮助请求,并且响应于第一移动终端将允许第二移动终端使用第一移动终端的网络连接与网络通信的确定,在分配的信标信道资源上发送信标信道通过网络的基站,在与信标信道资源对应的广播信道资源上发送广播信号,其中广播信号包括接入资源;和接收第二移动终端对接入资源的接入请求,并允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 8. A mobile terminal, configured to act as a first mobile terminal, the mobile terminal comprising:an input apparatus;an output apparatus;a non-transitory memory; anda processor, configured to:read a help request for accessing a network, wherein the help request is sent by a second mobile terminal;in response to reading the help request, and is response to a determination that the first mobile terminal will allow the second mobile terminal to communicate with the network using a network connection of the first mobile terminal, send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises an access resource; andreceive an access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 9.根据权利要求8所述的移动终端,其中所述处理器,用于在所述网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,包括所述处理器,用于:与网络基站建立无线资源控制(RRC)连接,向网络发送成为基站移动终端的请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 9. The mobile terminal according to claim 8, wherein the processor being configured to send a beacon channel on the beacon channel resource allocated by the base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, comprises the processor being configured to:establish a radio resource control (RRC) connection to the base station of the network, and send a request for becoming a base-station mobile terminal to the network;receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsend the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource.(String), 10.根据权利要求9所述的移动终端,其中处理器,用于接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信,包括处理器,用于:接收第二移动终端对接入资源的接入请求,并允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 10. The mobile terminal according to claim 9, wherein the processor being configured to receive an access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises the processor being configured to:receive the access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 11.根据权利要求9所述的移动终端,其中处理器,用于接收网络基站分配的信标信道资源、广播信道资源和接入资源,包括处理器,用于:接收网络基站使用无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 11. The mobile terminal according to claim 9, wherein the processor being configured to receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network, comprises the processor being configured to:receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network using radio resource control protocol signaling.(String), 12.根据权利要求8所述的移动终端,其中处理器,用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,包括处理器,用于:成为基站移动终端;向网络发送分配请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 12. The mobile terminal according to claim 8, wherein the processor being configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send a broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the processor being configured to:become a base-station mobile terminal;send an allocation request to the network;receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsend the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource.(String), 13.根据权利要求8所述的移动终端,其中处理器,用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,包括处理器,用于:驻留在网络的基站,从基站的广播中获取信标信道资源集和接入资源集,其中,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源;和在信标信道资源集合中的空闲信标信道资源上发送信标信道,在空闲信标信道资源对应的广播信道资源上发送广播信号。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 13. The mobile terminal according to claim 8, wherein the processor being configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the processor being configured to:camp on the base station of the network, and acquire a beacon channel resource set and an access resource set from a broadcast of the base station, wherein the beacon channel resource set comprises an idle beacon channel resource, and the access resource set comprises the access resource; andsend the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource.(String), 14.根据权利要求13所述的移动终端,其中处理器,用于接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信,包括处理器,用于:接收第二移动终端对接入资源的接入请求;和接入基站并请求成为基站移动终端,以允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 12(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 14. The mobile terminal according to claim 13, wherein the processor being configured to receive an access request of the second mobile terminal on the access resource, and allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises the processor being configured to:receive the access request of the second mobile terminal on the access resource; andaccess the base station and request to become a base-station mobile terminal, to allow the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 15.非暂时性计算机存储介质,其中非暂时性计算机存储介质存储程序,该程序包括用于:读取第二移动终端发送的入网帮助请求;响应于读取帮助请求,并且响应于确定第一移动终端将允许第二移动终端使用第一移动终端的网络连接与网络通信,在分配的信标信道资源上发送信标信道通过网络的基站,在与信标信道资源对应的广播信道资源上发送广播信号,其中广播信号包括接入资源;和接收第二移动终端对接入资源的接入请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 15. A non-transitory computer storage medium, wherein the non-transitory computer storage medium stores a program, and the program comprises instructions for:reading a help request for accessing a network, wherein the help request is sent-by a second mobile terminal;in response to reading the help request, and in response to a determination that a first mobile terminal will allow the second mobile terminal to communicate with the network using a network connection of the first mobile terminal, sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, wherein the broadcast signal comprises an access resource; andreceiving an access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 16.根据权利要求15所述的非暂时性计算机存储介质,其中包括用于在网络的基站分配的信标信道资源上发送信标信道以及在与信标信道资源对应的广播信道资源上发送广播信号的指令的程序包括用于以下指令的程序:与网络基站建立无线资源控制(RRC)连接,向网络发送成为基站移动终端的请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 16. The non-transitory computer storage medium according to claim 15, wherein the program including instructions for sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the program including instructions for:establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource.(String), 17.根据权利要求16所述的非暂时性计算机存储介质,其中包括用于接收第二移动终端对访问资源的访问请求并允许第二移动终端使用第一移动终端的网络连接与网络通信的指令的程序包括用于:接收第二移动终端对访问资源的访问请求,允许第二移动终端使用第一移动终端的网络连接与网络进行通信。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 17. The non-transitory computer storage medium according to claim 16, wherein the program including instructions for receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal, comprises the program including instructions for:receiving the access request of the second mobile terminal on the access resource, and allowing the second mobile terminal to communicate with the network using the network connection of the first mobile terminal.(String), 18.根据权利要求16所述的非暂时性计算机存储介质,其中包括用于接收由网络的基站分配的信标信道资源、广播信道资源和接入资源的指令的程序包括用于以下指令的程序:接收网络基站使用无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 18. The non-transitory computer storage medium according to claim 16, wherein the program including instructions for receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network, comprises the program including instructions for:receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network using radio resource control protocol signaling.(String), 19.根据权利要求15所述的非暂时性计算机存储介质,其中包括用于在网络的基站分配的信标信道资源上发送信标信道以及在与信标信道资源对应的广播信道资源上发送广播信号的指令的程序包括用于以下指令的程序:成为基站移动终端;向网络发送分配请求;接收网络基站分配的信标信道资源、广播信道资源和接入资源;和在信标信道资源上发送信标信道,在广播信道资源上发送广播信号。(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 19. The non-transitory computer storage medium according to claim 15, wherein the program including instructions for sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the program including instructions for:becoming a base-station mobile terminal;sending an allocation request to the network;receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; andsending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource.(String), 20.根据权利要求15所述的非暂时性计算机存储介质,其中包括用于在网络的基站分配的信标信道资源上发送信标信道以及在与信标信道资源对应的广播信道资源上发送广播信号的指令的程序包括用于以下指令的程序:基站驻留网络,通过基站的广播获取信标信道资源集和接入资源集,其中,所述信标信道资源集包括空闲信标信道资源,所述接入资源集包括接入资源;和在信标信道资源集合中的空闲信标信道资源上发送信标信道,在空闲信标信道资源对应的广播信道资源上发送广播信号。(String), 1(Integer), 18(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185977(Integer), 20. The non-transitory computer storage medium according to claim 15, wherein the program including instructions for sending the beacon channel on the beacon channel resource allocated by the base station of the network, and sending the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, comprises the program including instructions for:camping on the base station the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, wherein the beacon channel resource set comprises an idle beacon channel resource, and the access resource set comprises the access resource; andsending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource.(String), 1(Integer), 19(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.939 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.939 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:05.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185977(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 14/801,612, filed on Jul. 16, 2015, now U.S. Pat. No. 9,814,022, which is a continuation of International Application No. PCT/CN2013/070522, filed on Jan. 16, 2013. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present invention relates to the field of communications technologies, and specifically, to a network accessing method for a mobile terminal, and a mobile terminal. BACKGROUND [0003]In a current cellular system, a base station includes a macro base station and a micro base station. Because distances from different mobile terminals to the base station are different, interference to different mobile terminals is different, which causes that channel quality of different mobile terminals is different. In addition, in some cases, some mobile terminals may not be covered by a base station, for example, a mobile terminal falls in a coverage hole area, or a base station is damaged for some special reasons, such as an earthquake. Such a mobile terminal that is not covered needs another mobile terminal to help access a network. A mobile terminal that is not covered or weakly covered is defined as an access mobile terminal, and a mobile terminal that can connect to a base station to access a network and can help the access mobile terminal access the network is defined as a base-station mobile terminal. [0004]Because the access mobile terminal needs the base-station mobile terminal to help access a network, the access mobile terminal needs to discover the base-station mobile terminal and also needs to establish a connection to the base-station mobile terminal, and in this way, a final aim of accessing the network by the access mobile terminal can be implemented. Currently, an existing discovering manner for mobile terminals is mainly a manner in which mobile terminals autonomously discover each other. Each mobile terminal sends a beacon channel on a specific resource, so as to discover each other by checking beacon channels of each other. [0005]Because a beacon channel resource is limited, it is necessary to check, before a mobile terminal sends a beacon channel, whether there is a beacon channel resource, and if there is a beacon channel resource, the mobile terminal sends the beacon channel. In this way, a disadvantage of a distributed manner for autonomously using a beacon channel by a mobile terminal is that a mobile terminal may use a beacon channel but does not establish a connection to another mobile terminal, thereby wasting the beacon channel. SUMMARY [0006]Embodiments of the present invention provide a network accessing method for a mobile terminal, and a mobile terminal, which can more effectively use a beacon channel resource. [0007]According to a first aspect, embodiments of the present invention provide a network accessing method for a mobile terminal. The method includes reading a help request used for accessing a network by the mobile terminal. The method also includes sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The method also includes receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network. [0008]In a first possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: establishing a radio resource control (RRC) connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0009]In a second possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0010]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes: receiving the access request of the mobile terminal on the access resource, and assisting the mobile terminal in completing access to the network. [0011]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes: receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0012]In a fifth possible implementation manner, the step of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0013]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step of receiving an access request of the mobile terminal on the access resource, and assisting the mobile terminal in accessing the network further includes: receiving the access request of the mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the mobile terminal in completing access to the network. [0014]According to a second aspect, embodiments of the present invention provide a mobile terminal. The mobile terminal includes a reading module, configured to read a help request used for accessing a network by another mobile terminal. The mobile terminal also includes a broadcasting module, configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The mobile terminal also includes a receiving module, configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0015]In a first possible implementation manner, the broadcasting module includes: a network connecting submodule, configured to establish a RRC connection to the base station of the network, send a request for becoming a base-station mobile terminal to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource allocated by the base station of the network, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0016]In a second possible implementation manner, the mobile terminal further includes a base-station module, configured to make the mobile terminal become a base-station mobile terminal; and the broadcasting module includes: a network connecting submodule, configured to send an allocation request to the network, and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and a broadcasting submodule, configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0017]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the network connecting submodule receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0018]In a fourth possible implementation manner, the broadcasting module includes: a network connecting submodule, configured to camp on the base station of the network, acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and a broadcasting submodule, configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0019]With reference to the fourth possible implementation manner, in a fifth possible implementation manner, the network connecting submodule is further configured to, after the receiving module receives the access request, access the base station and request to become a base-station mobile terminal, so as to assist the another mobile terminal in accessing the network. [0020]According to a third aspect, embodiments of the present invention provide a computer storage medium, where the computer storage medium may store a program, and the program is used to perform the steps according to the first aspect of the present invention or any one of the first to the sixth possible implementation manners of the first aspect. [0021]According to a fourth aspect, embodiments of the present invention provide a mobile terminal, including an input apparatus, an output apparatus, a memory, and a processor, where the processor performs the following steps: reading a help request used for accessing a network by another mobile terminal; sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource; and receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network. [0022]In a first possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: establishing a RRC connection to the base station of the network, and sending a request for becoming a base-station mobile terminal to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0023]In a second possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: becoming a base-station mobile terminal; sending an allocation request to the network; receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network; and sending the beacon channel on the beacon channel resource, and sending the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0024]With reference to the first or the second possible implementation manner, in a third possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes: receiving the access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in completing access to the network. [0025]With reference to the first or the second possible implementation manner, in a fourth possible implementation manner, the step, which is performed by the processor, of receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network further includes: receiving the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0026]In a fifth possible implementation manner, the step, which is performed by the processor, of sending a beacon channel on a beacon channel resource allocated by a base station of the network, and sending a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource further includes: camping on the base station of the network, and acquiring a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes an idle beacon channel resource, and the access resource set includes the access resource; and sending the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sending the broadcast signal on a broadcast channel resource corresponding to the idle beacon channel resource, where the broadcast signal includes the access resource. [0027]With reference to the fifth possible implementation manner, in a sixth possible implementation manner, the step, which is performed by the processor, of receiving an access request of the another mobile terminal on the access resource, and assisting the another mobile terminal in accessing the network further includes: receiving the access request of the another mobile terminal on the access resource; and accessing the base station and requesting to become a base-station mobile terminal, so as to assist the another mobile terminal in completing access to the network. [0028]According to the network accessing method for a mobile terminal, and the mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that another mobile terminal connects to the mobile terminal on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. BRIEF DESCRIPTION OF THE DRAWINGS [0029]To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0030]FIG. 1 is a schematic diagram of an application environment according to an embodiment of the present invention; [0031]FIG. 2 to FIG. 4 are schematic flowcharts of a network accessing method for a mobile terminal according to embodiments of the present invention; and [0032]FIG. 5 to FIG. 8 are schematic diagrams of a mobile terminal according to embodiments of the present invention. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0033]The following describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0034]Referring to FIG. 1, FIG. 1 is a schematic diagram of an application environment of a network accessing method for a mobile terminal according to an embodiment of the present invention. In an implementation manner of the present invention, the network accessing method for a mobile terminal is used in a mobile communications system, for example, a Long Term Evolution (LTE for short) network, and a network under the 3rd Generation Partnership Project (3GPP for short). In some implementation manners of the present invention, the network accessing method for a mobile terminal may also be used in a wireless system. A network shown in FIG. 1 is a mobile communications system network, including a base station 30, where the base station 30 includes a macro base station (only one macro base station is used as an example in FIG. 1) and a micro base station (only one micro base station is used as an example in FIG. 1). A mobile terminal 10 is in coverage of the base station 30 and can access a network; and a mobile terminal 20 is not in the coverage of the base station 30, and cannot access the network, and therefore, the mobile terminal 10 is needed to assist the mobile terminal 20 in accessing the network. The mobile terminal 20 that is not covered or weakly covered is defined as an access mobile terminal, and the mobile terminal 10 that can connect to the base station 30 to access the network and can help the access mobile terminal 20 access the network is defined as a base-station mobile terminal. [0035]It should be noted that, in specific implementation, a function of a beacon channel is to make a terminal be discovered by another terminal. Therefore, in specific implementation, a resource allocated by the base station in the present invention is not merely limited to a beacon channel, and code that can be used to discover a terminal can be allocated by the base station in the present invention. That is, in this embodiment of the present invention, a beacon channel is merely used to indicate code used to discover a terminal, but is not used to limit use of other code having a terminal discovering function in this embodiment of the present invention. [0036]It may be understood that, because a base-station mobile terminal and an access mobile terminal move, the base-station mobile terminal may also become an access mobile terminal, and the access mobile terminal may also become a base-station mobile terminal. [0037]With reference to FIG. 1 and referring to FIG. 2, a network accessing method for a mobile terminal according to a first embodiment of the present invention includes the following steps. [0038]S201. Read a help request used for accessing a network by the mobile terminal 20. [0039]In this embodiment, the mobile terminal 20 is an access mobile terminal 20 that cannot access a network, and therefore, sends, on an agreed resource, the help request used for accessing a network, where the agreed resource may be, for example, a first timeslot of a frequency. By means of scanning, the mobile terminal 10 reads, on the agreed resource, the help request used for accessing a network by the mobile terminal 20. [0040]S202. Send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. [0041]In some implementation manners of the present invention, the mobile terminal 10 sends the beacon channel on the beacon channel resource allocated by the base station of the network. For example, there are resources of eight subframes from 0 to 7, and a second subframe is idle. In this case, the base station may allocate the second subframe to the mobile terminal 10, and the mobile terminal 10 may send a beacon channel in the second subframe and send a broadcast signal on a broadcast channel resource corresponding to the second subframe, for example, a third subframe, where the broadcast signal includes an access resource, for example, a fifth subframe. [0042]S203. Receive an access request of the mobile terminal 20 on the access resource, and assist the mobile terminal 20 in accessing the network. [0043]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station of the network, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0044]With reference to FIG. 1 and referring to FIG. 3, a network accessing method for a mobile terminal according to a second embodiment of the present invention includes: [0045]S301. The access mobile terminal 20 sends a request for requesting the mobile terminal 10 to help access a network. [0046]S302. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0047]S303. The mobile terminal 10 establishes a radio resource control (RRC) protocol connection to the base station 30 of the network, and sends a request for becoming a base-station mobile terminal to the base station 30. [0048]In this embodiment of the present invention, if the mobile terminal 10 intends to become a base-station mobile terminal after reading the help request of the access mobile terminal 20, the mobile terminal 10 sends the request for becoming a base-station mobile terminal to the base station 30. [0049]In some embodiments of the present invention, the mobile terminal 10 may also have become a base-station mobile terminal; in this case, the mobile terminal 10 sends only an allocation request to the base station 30. [0050]S304. The base station 30 allocates a beacon channel resource, a broadcast channel resource, and an access resource to the mobile terminal 10. [0051]In this embodiment of the present invention, the base station 30 allocates the beacon channel resource, the broadcast channel resource, and the access resource to the mobile terminal 10 by using radio resource control protocol signaling. [0052]In some implementation manners of the present invention, the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station 30 include a timeslot resource, a frequency resource, a code channel resource, and the like. [0053]In this case, the mobile terminal 10 becomes a base-station mobile terminal. [0054]S305. The mobile terminal 10 sends a beacon channel on the beacon channel resource allocated by the base station 30, and sends a broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0055]Step S303 to S305 are specific implementation steps of step S202 in FIG. 2. [0056]S306. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0057]S307. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0058]After receiving the access request of the access mobile terminal 20, the base-station mobile terminal 10 may help the access mobile terminal 20 complete access to the network, that is, the base station 30. [0059]According to the network accessing method for a mobile terminal, the beacon channel is sent on the beacon channel resource allocated by the base station 30, and the broadcast signal is sent on the broadcast channel resource corresponding to the beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses the network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. [0060]With reference to FIG. 1 and referring to FIG. 4, a network accessing method for a mobile terminal according to a third embodiment of the present invention includes the following steps. [0061]S401. The access mobile terminal 20 sends a request for requesting the base-station mobile terminal 10 to help access a network. [0062]S402. The mobile terminal 10 reads the help request of the access mobile terminal 20. [0063]S403. The mobile terminal 10 camps on the base station 30, and acquires a beacon channel resource set and an access resource set by means of broadcast of the base station 30. [0064]S404. The mobile terminal 10 sends a beacon channel on an idle beacon channel resource in the beacon channel resource set, and sends a broadcast signal on a broadcast channel resource, where the broadcast signal includes an access resource. [0065]The mobile terminal 10 checks whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, and if there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the mobile terminal 10 sends the beacon channel on the idle beacon channel resource in the beacon channel resource set, and sends the broadcast signal on a corresponding broadcast channel resource, where the broadcast signal includes the access resource. [0066]Step S403 to step S404 are specific implementation manners of step S202 in FIG. 2. [0067]S405. The access mobile terminal 20 searches for the beacon channel, and synchronizes with the mobile terminal 10, so as to read the broadcast signal and read the access resource from the broadcast signal. [0068]S406. The access mobile terminal 20 initiates an access process on the read access resource, that is, sends an access request to the mobile terminal 10. [0069]S407. The mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, so as to assist the access mobile terminal in completing access to the network. [0070]According to the network accessing method for a mobile terminal, it is checked whether there is an idle beacon channel resource in the beacon channel resource set broadcasted by the base station 30, the beacon channel is sent on the idle beacon channel resource in the beacon channel resource set, and the broadcast signal is sent on a broadcast channel resource corresponding to the idle beacon channel resource, to indicate the access resource, so that the mobile terminal 20 connects to the mobile terminal 10 on the access resource and then accesses a network, which avoids a waste of the beacon channel and more properly uses the beacon channel and the access resource. In addition, only after receiving the access request of the access mobile terminal 20, the mobile terminal 10 accesses the base station 30 and requests to become a base-station mobile terminal, thereby avoiding a waste of a resource. [0071]To better implement the foregoing solutions in the embodiments of the present invention, a related apparatus configured to cooperate to implement the foregoing solutions is provided in the following. [0072]Referring to FIG. 5, a mobile terminal 50 according to an embodiment of the present invention includes a reading module 500, a broadcasting module 510, and a receiving module 520. The reading module 500 is configured to read a help request used for accessing a network by another mobile terminal. The another mobile terminal is not covered by a network or weakly covered by a network, and therefore the another mobile terminal requests the mobile terminal 50 to help access the network. [0073]The broadcasting module 510 is configured to send a beacon channel on a beacon channel resource allocated by a base station of the network, and send a broadcast signal on a broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes an access resource. The receiving module 520 is configured to receive an access request of the another mobile terminal on the access resource, and assist the another mobile terminal in accessing the network. [0074]Referring to FIG. 6, the broadcasting module 510 includes a network connecting submodule 511 and a broadcasting submodule 512. [0075]In some implementation manners of the present invention, the network connecting submodule 511 is configured to send a request for becoming a base-station mobile terminal to the network and receive the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network. The broadcasting submodule 512 is configured to send the beacon channel on the beacon channel resource, and send the broadcast signal on the broadcast channel resource, where the broadcast signal includes the access resource. [0076]In some implementation manners of the present invention, the network connecting submodule 511 receives the beacon channel resource, the broadcast channel resource, and the access resource that are allocated by the base station of the network by using radio resource control protocol signaling. [0077]In some implementation manners of the present invention, the network connecting submodule 511 is configured to camp on the base station of the network, and acquire a beacon channel resource set and an access resource set by means of broadcast of the base station, where the beacon channel resource set includes the idle beacon channel resource, and the access resource set includes the access resource. The broadcasting submodule 512 is configured to send the beacon channel on the idle beacon channel resource in the beacon channel resource set, and send the broadcast signal on the broadcast channel resource corresponding to the beacon channel resource, where the broadcast signal includes the access resource. [0078]In some implementation manners of the present invention, the network connecting submodule 511 is further configured to, after the receiving module receives the access request, access the base st(String), 相关申请的交叉引用 [0001] 该申请是美国专利申请序列号的延续。 第 14/801,612 号,2015 年 7 月 16 日提交,现为美国专利。 美国第 9,814,022 号是 2013 年 1 月 16 日提交的国际申请第 PCT/CN2013/070522 号的继续申请。所有上述申请均通过引用整体并入本文。 技术领域 [0002] 本发明涉及通信技术领域,具体涉及一种移动终端的网络接入方法及移动终端。 背景 [0003] 在目前的蜂窝系统中,基站包括宏基站和微基站。 由于不同移动终端到基站的距离不同,对不同移动终端的干扰不同,导致不同移动终端的信道质量不同。 另外,在某些情况下,一些移动终端可能不在基站的覆盖范围内,例如移动终端落入覆盖盲区,或者由于地震等特殊原因导致基站损坏等。 这种未被覆盖的移动终端需要另外的移动终端帮助接入网络。 将未覆盖或弱覆盖的移动终端定义为接入移动终端,能够连接基站接入网络并帮助接入移动终端接入网络的移动终端定义为基站 移动终端。 [0004] 由于接入移动终端需要基站移动终端帮助接入网络,因此接入移动终端需要发现基站移动终端,同时也需要与基站移动终端建立连接,这种方式 ,可以实现接入移动终端接入网络的最终目的。 目前,现有的移动终端发现方式主要是移动终端自主发现对方的方式。 每个移动终端在特定资源上发送信标信道,以便通过检查彼此的信标信道来相互发现。 [0005] 由于信标信道资源有限,移动终端在发送信标信道之前,需要检查是否有信标信道资源,如果有信标信道资源,则移动终端发送信标信道。 这样,移动终端自主使用信标信道的分布式方式的缺点是移动终端可以使用信标信道但不与其他移动终端建立连接,从而浪费信标信道。 概括 [0006] 本发明实施例提供一种移动终端的网络接入方法及移动终端,能够更有效地利用信标信道资源。 [0007] 第一方面,本发明实施例提供了一种移动终端的网络接入方法。 该方法包括读取移动终端用于接入网络的帮助请求。 该方法还包括在由网络的基站分配的信标信道资源上发送信标信道,以及在对应于该信标信道资源的广播信道资源上发送广播信号,其中该广播信号包括接入资源。 该方法还包括接收移动终端对接入资源的接入请求,协助移动终端接入网络。 [0008]在第一种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源还包括:与网络基站建立无线资源控制(Radio Resource Control,无线资源控制)连接,向网络发送成为基站移动终端的请求。 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0009] 在第二种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 接入资源还包括:成为基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0010] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,接收所述移动终端对所述接入资源的接入请求,并协助所述移动终端接入网络的步骤还包括:接收所述接入 移动终端对接入资源的请求,协助移动终端完成对网络的接入。 [0011] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述接收网络基站分配的信标信道资源、广播信道资源和接入资源的步骤还包括: 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0012] 在第五种可能的实现方式中,所述步骤在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括: 一种接入资源,进一步包括:驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲的信标信道资源,以及 访问资源集合包括访问资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0013] 结合第五种可能的实现方式,在第六种可能的实现方式中,接收所述移动终端对所述接入资源的接入请求,并协助所述移动终端接入网络的步骤还包括:接收所述移动终端的接入请求。 接入资源上的移动终端; 接入基站并请求成为基站移动终端,以辅助移动终端完成入网。 [0014]第二方面,本发明实施例提供了一种移动终端。 该移动终端包括读取模块,用于读取其他移动终端接入网络的帮助请求。 移动终端还包括广播模块,用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,其中,广播信号 包括访问资源。 移动终端还包括接收模块,用于接收其他移动终端对访问资源的访问请求,协助其他移动终端访问网络。 [0015] 在第一种可能的实现方式中,所述广播模块包括: 网络连接子模块,用于与网络基站建立RRC连接,向网络发送成为基站移动终端的请求,并接收beacon 网络基站分配的信道资源、广播信道资源和接入资源; 广播子模块,用于在网络基站分配的信标信道资源上发送信标信道,并在广播信道资源上发送广播信号,广播信号包括接入资源。 [0016] 在第二种可能的实现方式中,所述移动终端还包括基站模块,用于使所述移动终端成为基站移动终端; 广播模块包括:网络连接子模块,用于向网络发送分配请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块,用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号中包括接入资源。 [0017] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,网络连接子模块接收网络基站通过使用 无线电资源控制协议信令。 [0018] 在第四种可能的实现方式中,广播模块包括:网络连接子模块,用于驻留在网络的基站上,通过基站的广播获取信标信道资源集和接入资源集,其中, 信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源; 广播子模块,用于在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号包括接入资源 . [0019] 结合第四种可能的实现方式,在第五种可能的实现方式中,网络连接子模块还用于接收模块接收到接入请求后,接入基站,请求成为基站移动终端,因此 以协助其他移动终端接入网络。 [0020] 第三方面,本发明实施例提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行本发明第一方面或以下任一项所述的步骤 第一方面的第一种至第六种可能的实现方式。 [0021]第四方面,本发明实施例提供一种移动终端,包括输入装置、输出装置、存储器和处理器,所述处理器执行以下步骤:读取用于访问网络的帮助请求。 另一个移动终端; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0022] 在第一种可能的实现方式中,所述处理器执行在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号的步骤 信道资源,其中广播信号包括接入资源还包括:与网络基站建立RRC连接,向网络发送成为基站移动终端的请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0023] 在第二种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括:成为基站的移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0024] 结合第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述处理器接收所述另一移动终端对所述接入资源的接入请求,并协助所述另一移动终端执行的步骤 接入网络还包括:接收另一移动终端对接入资源的接入请求,协助另一移动终端完成接入网络。 [0025] 结合第一种或第二种可能的实现方式,在第四种可能的实现方式中,所述处理器接收所述处理器分配的信标信道资源、广播信道资源和接入资源的步骤。 网络基站还包括:接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0026] 在第五种可能的实现方式中,所述处理器在网络基站分配的信标信道资源上发送信标信道,并在所述信标对应的广播信道资源上发送广播信号。 信道资源,其中广播信号包括接入资源还包括:驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,其中,所述信标信道资源集 包括空闲信标信道资源,接入资源集合包括接入资源; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在空闲信标信道资源对应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0027] 结合第五种可能的实现方式,在第六种可能的实现方式中,所述处理器接收所述其他移动终端对所述访问资源的访问请求,协助所述其他移动终端访问所述访问资源。 网络还包括:接收另一移动终端对接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0028] 一种移动终端入网方法及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在信标对应的广播信道资源上发送 channel resource,指示接入资源,以便其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入资源。 附图的简要说明 [0029] 为了更加清楚地描述本发明实施例中的技术方案,下面对实施例描述中所需要的附图进行简单介绍。 显然,以下描述中的附图仅仅是本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0030] 图1为本发明实施例的应用环境示意图; [0031] 图2至图4是根据本发明实施例的移动终端的网络接入方法的流程示意图; 和 [0032] 图5至图8是根据本发明实施例的移动终端的示意图。 说明性实施例的详细说明 [0033] 下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行说明。 显然,所描述的实施例仅仅是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0034] 请参阅图1,图1为本发明实施例提供的移动终端的网络接入方法的应用环境示意图。 在本发明的一个实施方式中,所述移动终端的入网方法用于移动通信系统,例如长期演进(Long Term Evolution,简称LTE)网络、第三代合作伙伴计划(3GPP)下的网络。 简称)。 在本发明的一些实施方式中,该移动终端的网络接入方法还可以用于无线系统中。 图1所示网络为移动通信系统网络,包括基站 30 ,其中基站 30 包括宏基站(图1中仅以一个宏基站为例)和微基站(图1中仅以一个微基站为例)。 移动终端 10 在基站覆盖范围内 30 并且可以访问网络; 和移动终端 20 不在基站覆盖范围内 30 , 无法上网, 因此, 移动终端 10 需要移动端辅助 20 在访问网络时。 移动端 20 未覆盖或弱覆盖定义为接入移动终端,移动终端 10 可以连接到基站 30 接入网络,可以帮助接入移动终端 20 接入网络的移动终端被定义为基站。 [0035]需要说明的是,在具体实现中,信标信道的作用是使一个终端被另一个终端发现。 因此,在具体实施中,本发明基站分配的资源并不仅限于信标信道,本发明基站可以分配可用于发现终端的代码。 即本发明实施例中,信标信道仅用于指示用于发现终端的代码,并不用于限制本发明实施例中使用其他具有终端发现功能的代码。 [0036] 可以理解的是,由于基站移动终端和接入移动终端移动,因此基站移动终端也可能成为接入移动终端,接入移动终端也可能成为基站移动终端。 [0037] 参考图1并参考图2,根据本发明第一实施例的移动终端的网络接入方法包括以下步骤。 [0038] 小号 201 . 读取移动终端接入网络的帮助请求 20 . [0039] 本实施例中,移动终端 20 是接入移动终端 20 无法接入网络,因此在约定的资源上发送用于接入网络的帮助请求,该约定的资源例如可以是频率的第一时隙。 手机端扫一扫 10 在约定的资源上读取移动终端接入网络的帮助请求 20 . [0040] 小号 202 . 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0041] 在本发明的一些实施方式中,移动终端 10 在网络基站分配的信标信道资源上发送信标信道。 例如,0到7有8个子帧的资源,第二个子帧空闲。 在这种情况下,基站可以将第二子帧分配给移动终端 10 , 和移动端 10 可以在第二子帧发送信标信道,在第二子帧对应的广播信道资源,例如第三子帧上发送广播信号,该广播信号包括接入资源,例如第五子帧。 [0042] 小号 203 . 接收移动终端的访问请求 20 在接入资源上,协助移动终端 20 在访问网络时。 [0043] 一种移动终端的入网方法,所述信标信道在网络基站分配的信标信道资源上发送,广播信号在所述信标信道资源对应的广播信道资源上发送,以指示 访问资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理地利用了信标信道和接入资源。 [0044] 结合图1并参考图3,本发明实施例二提供的一种移动终端的网络接入方法包括: [0045] 小号 301 . 接入移动终端 20 发送请求移动端的请求 10 帮助访问网络。 [0046] 小号 302 . 移动端 10 读取接入移动端的帮助请求 20 . [0047] 小号 303 . 移动端 10 建立到基站的无线资源控制 (RRC) 协议连接 30 向基站发送成为基站移动终端的请求 30 . [0048] 本发明实施例中,若移动终端 10读取接入移动终端的帮助请求后,打算成为基站移动终端 20 , 移动端 10 向基站发送成为基站移动终端的请求 30 . [0049] 在本发明的一些实施例中,移动终端 10 也可能成为基站移动终端; 在这种情况下,移动端 10 仅向基站发送分配请求 30 . [0050] 小号 304 . 基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源 10 . [0051] 本发明实施例中,基站 30 为移动终端分配信标信道资源、广播信道资源和接入资源 10 通过使用无线电资源控制协议信令。 [0052] 在本发明的一些实施方式中,基站分配的信标信道资源、广播信道资源和接入资源 30 包括时隙资源、频率资源、码道资源等。 [0053] 在这种情况下,移动端 10 成为基站移动终端。 [0054] 小号 305 . 移动端 10 在基站分配的信标信道资源上发送信标信道 30 ,在广播信道资源上发送广播信号,广播信号中包含接入资源。 [0055] 脚步 303 到小号 305 是步骤S的具体实现步骤 202 在图 2 中。 [0056] 小号 306 . 接入移动终端 20 搜索信标信道,与移动终端同步 10 ,从而读取广播信号,并从广播信号中读取接入资源。 [0057] 小号 307 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0058] 收到接入移动终端的接入请求后 20 , 基站移动终端 10 可以帮助接入移动终端 20 完全接入网络,即基站 30 . [0059] 一种移动终端入网方法,所述信标信道在基站分配的信标信道资源上发送 30 ,在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0060] 参考图1并参考图4,根据本发明实施例三的移动终端的网络接入方法包括以下步骤。 [0061] 小号 401 . 接入移动终端 20 发送请求基站移动终端的请求 10 帮助访问网络。 [0062] 小号 402 . 移动端 10 读取接入移动端的帮助请求 20 . [0063] 小号 403 . 移动端 10 基站上的营地 30 , 通过基站的广播获取信标信道资源集和接入资源集 30 . [0064] 小号 404 . 移动端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,在广播信道资源上发送广播信号,该广播信号包括接入资源。 [0065] 移动端 10 检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30, 如果基站广播的信标信道资源集合中有空闲的信标信道资源 30 , 移动端 10 在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在相应的广播信道资源上发送广播信号,广播信号中包括接入资源。 [0066] 脚步 403 到步骤 S 404 是步骤S的具体实现方式 202 在图 2 中。 [0067] 小号 405 . 接入移动终端 20 搜索信标信道,与移动终端同步 10 ,从而读取广播信号,并从广播信号中读取接入资源。 [0068] 小号 406 . 接入移动终端 20 对读取的访问资源发起访问过程,即向移动终端发送访问请求 10 . [0069] 小号 407 . 移动端 10 接入基站 30 请求成为基站移动终端,以协助接入移动终端完成入网。 [0070] 一种移动终端入网方法,检查基站广播的信标信道资源集合中是否有空闲的信标信道资源 30 ,信标信道在信标信道资源集合中的空闲信标信道资源上发送,广播信号在空闲信标信道资源对应的广播信道资源上发送,指示接入资源,使得移动终端 20 连接到移动端 10 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 另外,只有在接收到接入移动终端的接入请求后 20 , 移动端 10 接入基站 30 请求成为基站移动终端,避免资源浪费。 [0071] 为了更好的实施本发明实施例的上述方案,下面提供一种用于配合实施上述方案的相关装置。 [0072] 参见图5,移动终端 50 根据本发明的实施例包括读取模块 500 , 广播模块 510 , 和一个接收模块 520 . 阅读模块 500 用于读取其他移动终端接入网络的帮助请求。 另一移动终端未被网络覆盖或弱网络覆盖,因此另一移动终端请求该移动终端 50 以帮助访问网络。 [0073] 广播模块 510 用于在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 接收模块 520 用于接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0074] 参见图6,广播模块 510 包括一个网络连接子模块 511 和一个广播子模块 512 . [0075] 在本发明的一些实施方式中,网络连接子模块 511 用于向网络发送成为基站移动终端的请求,接收网络基站分配的信标信道资源、广播信道资源和接入资源。 广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0076] 在本发明的一些实施方式中,网络连接子模块511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0077] 在本发明的一些实施方式中,网络连接子模块 511 用于驻留在网络的基站,通过基站的广播获取信标信道资源集和接入资源集,所述信标信道资源集包括空闲信标信道资源和接入资源 set 包括访问资源。 广播子模块 512 用于在信标信道资源集合中空闲的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0078] 在本发明的一些实施方式中,网络连接子模块 511 还用于接收模块接收到接入请求后,接入基站并请求成为基站移动终端,以辅助其他移动终端接入网络。 [0079] 可以理解为移动端 50 本实施例中例如可以为电脑、手机或平板电脑。 [0080] 可以理解为,移动终端的所有功能模块的功能 50 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0081] 上述移动终端 50 在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 50 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0082] 参考图7,移动终端之间的区别 70 根据本发明实施例的移动终端 50 图5所示为基站模块 700 除了阅读模块外,还包括 500 , 广播模块 510 , 和一个接收模块 520 , 其中阅读模块 500 ,广播模块 510 , 接收模块 520 与图5所示的相应模块基本相同,在此不再赘述。 基站模块 700 配置为使移动端 70 成为基站移动终端。 [0083] 广播模块 510 还包括网络连接子模块 511 和广播子模块 512 如图6所示,其中网络连接子模块 511 用于向网络端发送分配请求,接收网络端基站分配的信标信道资源、广播信道资源和接入资源; 和广播子模块 512 用于在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0084] 在本发明的一些实施方式中,网络连接子模块 511 接收网络基站通过无线资源控制协议信令分配的信标信道资源、广播信道资源和接入资源。 [0085] 可以理解为移动端 70 本实施例中例如可以为电脑、手机或平板电脑。 [0086]可以理解为,移动终端的所有功能模块的功能 70 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0087] 上述移动终端 70 在网络基站分配的信标信道资源上发送信标信道,并在信标信道资源对应的广播信道资源上发送广播信号,指示接入资源,以便其他移动终端连接到移动台 终端 70 在接入资源上接入网络,避免了信标信道的浪费,更合理的使用了信标信道和接入资源。 [0088] 本发明实施例还提供了一种计算机存储介质,该计算机存储介质中可以存储有程序,该程序用于执行上述方法中描述的移动终端上网方法的部分或全部步骤。 实施例。 [0089] 参见图8,本发明实施例还提供了一种移动终端 80 ,包括一个处理器 810 , 一段记忆 800 , 输入设备 820 , 和一个输出设备 830 (可能有一个或多个处理器 810 在移动端 80 ,图8中以一个处理器为例)。 在本发明的一些实施例中,输入装置 820 , 输出设备 830 , 记忆 800 , 和处理器 810 可以通过使用总线或以其他方式相互连接。 图8中以它们通过总线连接为例。 [0090] 处理器 810 执行以下步骤: 读取另一移动终端用于接入网络的帮助请求; 在网络基站分配的信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源; 接收另一移动终端对接入资源的接入请求,协助另一移动终端接入网络。 [0091] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:发送 请求成为网络的基站移动终端; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0092] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,进一步包括:成为一个 基站移动终端; 向网络发送分配请求; 接收网络基站分配的信标信道资源、广播信道资源和接入资源; 在信标信道资源上发送信标信道,在广播信道资源上发送广播信号,广播信号包括接入资源。 [0093] 在本发明的一些实施方式中,所述步骤由处理器执行 810接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络还包括:接收其他移动终端对接入资源的接入请求,协助其他移动终端接入网络。 完成对网络的访问。 [0094] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收网络基站分配的信标信道资源、广播信道资源和接入资源还包括:接收网络基站分配的信标信道资源、广播信道资源和接入资源。 网络的基站通过使用无线资源控制协议信令。 [0095] 在本发明的一些实施方式中,所述步骤由处理器执行 810 ,在网络基站分配的信标信道资源上发送信标信道,并在所述信标信道资源对应的广播信道资源上发送广播信号,所述广播信号包括接入资源,还包括:驻留在 网络的基站,通过基站广播获取信标信道资源集和接入资源集,信标信道资源集包括空闲信标信道资源,接入资源集包括接入资源 ; 在信标信道资源集合中的空闲信标信道资源上发送信标信道,并在该信标信道资源对应的广播信道资源上发送广播信号,该广播信号包括接入资源。 [0096] 在本发明的一些实施方式中,所述步骤由处理器执行 810 接收所述另一移动终端对所述接入资源的接入请求,协助所述另一移动终端接入网络还包括:接收所述另一移动终端对所述接入资源的接入请求; 接入基站并请求成为基站移动终端,以辅助另一移动终端完成入网。 [0097] 可以理解为,移动终端的所有功能模块的功能 80 本实施例中的具体可以按照上述实施例一至实施例三中的方法实现。 具体实现过程可以参见上述实施例一至实施例三方法中的相关描述,在此不再赘述。 [0098] 需要说明的是,为便于描述,上述方法实施例均以一系列动作进行描述。 然而,本领域的技术人员应该理解,本发明不限于所描述的动作顺序,因为根据本发明,一些步骤可以以不同的顺序或同时执行。 其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本发明所必须的。 [0099] 在上述实施例中,对各个实施例的描述都各有侧重。 一个实施例中没有详述的部分,可以参见其他实施例的相关描述。 [0100] 综上所述,根据移动终端的入网方法,以及移动终端,信标信道在网络基站分配的信标信道资源上发送,广播信号在相应的广播信道资源上发送 到信标信道资源,指示接入资源,使得其他移动终端在接入资源上连接到该移动终端,然后接入网络,避免了信标信道的浪费,更合理地使用信标信道和接入 资源。 [0101]本领域普通技术人员可以理解,上述实施例中方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 存储介质可以包括:只读存储器、随机存取存储器、磁盘或光盘。 [0102] 以上对本发明实施例提供的移动终端的网络接入方法及移动终端进行了详细描述。 本说明书中采用具体的例子来说明本发明的原理和实施方式。 上述实施例只是为了帮助理解本发明的方法和核心思想。 此外,对于实施方式和适用范围,本领域的普通技术人员可以根据本发明的思想进行修改。 总之,说明书不应理解为对本发明的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104303526A(String), CN104303526B(String), EP2947901A1(String), EP2947901A4(String), EP2947901B1(String), EP3624471A1(String), EP3624471B1(String), US10200973B2(String), US20150327216A1(String), US20180054802A1(String), US9814022B2(String), WO2014110726A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 13 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), CN104303526A(String), 192720(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), CN104303526B(String), 192721(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP2947901A1(String), 192722(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP2947901A4(String), 192723(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP2947901B1(String), 192724(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP3624471A1(String), 192725(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), EP3624471B1(String), 192726(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US10200973B2(String), 192727(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US20150327216A1(String), 192728(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US20180054802A1(String), 192729(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), US9814022B2(String), 192730(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 270789(Integer), WO2014110726A1(String), 192731(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104303526B(String), CN104303526B(String), 1548345600(Integer), 270789(Integer), 185073(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD(String), 华为技术有限公司(String), 255(String), 0(Integer), 1661144373(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25166(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.713 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185977(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25166(Integer), 1(Integer), 185977(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185977(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185977(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25166(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.919 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.989 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:06.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.006 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.006 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.006 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10310566B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Foldable mechanism of mobile terminal and mobile terminal(String), 移动终端折叠机构及移动终端(String), US10310566B2(String), The present disclosure provides a foldable mechanism of a mobile terminal and the mobile terminal. The foldable mechanism includes a soft support structure and a hard support structure embedded in the soft support structure. The foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting a first housing and a second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward. Therefore, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved.(String), 本发明提供一种移动终端的折叠机构及移动终端。 折叠机构包括软支撑结构和嵌入软支撑结构的硬支撑结构。 由软支撑结构和嵌入软支撑结构中的硬支撑结构形成的可折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软支撑结构和硬支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 当移动终端折叠时,软支撑结构远离硬支撑结构的一侧向内收缩。 因此,避免了移动终端具有突兀的外观结构,提高了移动终端的外观效果。(String), US16/119102(String), 1535644800(Integer), US10310566B2(String), 1559577600(Integer), 1559577600(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 34(Integer), CN102710823A | CN104900149A | CN105096756A | CN105549690A | CN204069046U | CN205446377U | KR101467857B1 | US20020067339A1 | US20070117600A1 | US20100164837A1 | US20120147542A1 | US20120307423A1 | US20120307472A1 | US20130216740A1 | US20140196254A1 | US20140217875A1 | US20150055287A1 | US20150077917A1 | US20150176317A1 | US20150257290A1 | US20150330614A1 | US20160062412A1 | US20160139634A1 | US20160187935A1 | US20160224072A1 | US20180077810A1 | US6421235B2 | US6577496B1 | US9506279B2 | US9811119B2 | US9818961B2 | US9898051B2 | US9927841B2 | WO2012167204A2(String), 18(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.577 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.577 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185978(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.724 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\821b589054d5495287227f89bee9d528.png(String), 185978(Integer), 821b589054d5495287227f89bee9d528.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Foldable mechanism of mobile terminal and mobile terminal(String), 移动终端折叠机构及移动终端(String), US10310566B2(String), The present disclosure provides a foldable mechanism of a mobile terminal and the mobile terminal. The foldable mechanism includes a soft support structure and a hard support structure embedded in the soft support structure. The foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting a first housing and a second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward. Therefore, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved.(String), 本发明提供一种移动终端的折叠机构及移动终端。 折叠机构包括软支撑结构和嵌入软支撑结构的硬支撑结构。 由软支撑结构和嵌入软支撑结构中的硬支撑结构形成的可折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软支撑结构和硬支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 当移动终端折叠时,软支撑结构远离硬支撑结构的一侧向内收缩。 因此,避免了移动终端具有突兀的外观结构,提高了移动终端的外观效果。(String), US16/119102(String), 1535644800(Integer), US10310566B2(String), 1559577600(Integer), 1559577600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 34(Integer), CN102710823A | CN104900149A | CN105096756A | CN105549690A | CN204069046U | CN205446377U | KR101467857B1 | US20020067339A1 | US20070117600A1 | US20100164837A1 | US20120147542A1 | US20120307423A1 | US20120307472A1 | US20130216740A1 | US20140196254A1 | US20140217875A1 | US20150055287A1 | US20150077917A1 | US20150176317A1 | US20150257290A1 | US20150330614A1 | US20160062412A1 | US20160139634A1 | US20160187935A1 | US20160224072A1 | US20180077810A1 | US6421235B2 | US6577496B1 | US9506279B2 | US9811119B2 | US9818961B2 | US9898051B2 | US9927841B2 | WO2012167204A2(String), \20230420\821b589054d5495287227f89bee9d528.png(String), 18(Integer), 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.848 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 1. A foldable mechanism of a mobile terminal, comprising:a soft support structure to connect a first housing and a second housing of the mobile terminal, the soft support structure comprising a plurality of V-shaped supports arranged in a single row, open ends of adjacent V-shaped supports are connected, and an opening of each V-shaped support faces a flexible display screen of the mobile terminal; anda hard support structure included in each V-shaped support and configured to support the flexible display screen, wherein each hard support structure blocks two ends of a V-shaped support corresponding to the hard support structure; and further comprising a blocking layer included between bending tip portions of any two adjacent V-shaped supports;when the foldable mechanism of the mobile terminal is bent, bending tip portions of the plurality of V-shaped supports converge, and each blocking layer is compressed into a gap between two V-shaped supports connected by the blocking layer; andwhen the foldable mechanism of the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports move away from each other, and each blocking layer is unfolded to block the gap between the two V-shaped supports connected by the blocking layer.(String), 1.根据权利要求10所述的移动终端,其中多个阻挡层为一体结构的折弯板,折弯板上包括多个折痕,多个V形支架的折弯尖端部分等间距固定连接于折弯板上的折痕,并且相邻的V形支撑之间存在奇数个折痕。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 2. The foldable mechanism of the mobile terminal according to claim 1, wherein a plurality of blocking layers are a bending plate of an integrated structure, a plurality of creases are included on the bending plate, the bending tip portions of the plurality of V-shaped supports are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports.(String), 12.根据权利要求10所述的移动终端,其中多个阻挡层中的至少一个阻挡层为弯折件,弯折件上存在奇数条折痕,弯折件的两端分别与两侧的V型支架的弯折尖端部连接。一对一的基础上的阻挡层。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 3. The foldable mechanism of the mobile terminal according to claim 1, wherein at least one blocking layer in a plurality of blocking layers is a bending piece, an odd number of creases exist on the bending piece, and two ends of the bending piece are respectively connected to bending tip portions of V-shaped supports on two sides of the blocking layer on a one-to-one basis.(String), 13.根据权利要求12所述的移动终端,其中每个弯曲件上都有一个折痕。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 4. The foldable mechanism of the mobile terminal according to claim 3, wherein one crease exists on each bending piece.(String), 14.根据权利要求10所述的移动终端,其中多个阻挡层中的至少一个阻挡层包括夹在相邻V形支撑件之间的弹性材料层。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 5. The foldable mechanism of the mobile terminal according to claim 1, wherein at least one blocking layer in the plurality of blocking layers comprises an elastic material layer included between adjacent V-shaped supports.(String), 15.根据权利要求14所述的移动终端,其中各弹性材料层和与弹性材料层相邻的V型支架为一体结构。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 6. The foldable mechanism of the mobile terminal according to claim 5, wherein each elastic material layer and a V-shaped support adjacent to the elastic material layer are an integrated structure.(String), 16.根据权利要求10所述的移动终端,其中每个硬质支撑结构包括挡住硬质支撑结构对应的V型支架的开口的第一支撑层,第一支撑层的两端具有挡住V型支架一端的折叠机构。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 7. The foldable mechanism of the mobile terminal according to claim 1, wherein each hard support structure comprises a first support layer blocking an opening of a V-shaped support corresponding to the hard support structure, and a foldable mechanism blocking one end of the V-shaped support exists at either end of the first support layer.(String), 17.根据权利要求16所述的移动终端,还包括外层包括在可折叠机构的外侧壁上。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 8. The foldable mechanism of the mobile terminal according to claim 7, further comprising an exterior layer included on an external sidewall of the foldable mechanism.(String), 18.根据权利要求16所述的移动终端,其中硬质支撑结构还包括包裹第一支撑层的第二支撑层,第二支撑层的强度高于第一支撑层的强度。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 9. The foldable mechanism of the mobile terminal according to claim 7, wherein the hard support structure further comprises a second support layer wrapping the first support layer, and strength of the second support layer is higher than strength of the first support layer.(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 10. A mobile terminal, comprising,a housing; anda flexible display screen included in the housing, the housing comprising:a first housing,a second housing, anda foldable mechanism to fold the first housing and the second housing, the foldable mechanism comprising:a soft support structure to connect the first housing and the second housing of the mobile terminal, the soft support structure comprising a plurality of V-shaped supports arranged in a single row, open ends of adjacent V-shaped supports are connected, and an opening of each V-shaped support faces a flexible display screen of the mobile terminal; anda hard support structure included in each V-shaped support and configured to support the flexible display screen, wherein each hard support structure blocks two ends of a V-shaped support corresponding to the hard support structure; and further comprising a blocking layer included between bending tip portions of any two adjacent V-shaped supports;when the foldable mechanism of the mobile terminal is bent, bending tip portions of the plurality of V-shaped supports converge, and each blocking layer is compressed into a gap between two V-shaped supports connected by the blocking layer; andwhen the foldable mechanism of the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports move away from each other, and each blocking layer is unfolded to block the gap between the two V-shaped supports connected by the blocking layer.(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 11. The mobile terminal according to claim 10, wherein a plurality of blocking layers are a bending plate of an integrated structure, a plurality of creases are included on the bending plate, the bending tip portions of the plurality of V-shaped supports are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 12. The mobile terminal according to claim 10, wherein at least one blocking layer in a plurality of blocking layers is a bending piece, an odd number of creases exist on the bending piece, and two ends of the bending piece are respectively connected to bending tip portions of V-shaped supports on two sides of the blocking layer on a one-to-one basis.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 13. The mobile terminal according to claim 12, wherein one crease exists on each bending piece.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 14. The mobile terminal according to claim 10, wherein at least one blocking layer in the plurality of blocking layers comprises an elastic material layer included between adjacent V-shaped supports.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 15. The mobile terminal according to claim 14, wherein each elastic material layer and a V-shaped support adjacent to the elastic material layer are an integrated structure.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 16. The mobile terminal according to claim 10, wherein each hard support structure comprises a first support layer blocking an opening of a V-shaped support corresponding to the hard support structure, and a foldable mechanism blocking one end of the V-shaped support exists at either end of the first support layer.(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 17. The mobile terminal according to claim 16, further comprising an exterior layer included on an external sidewall of the foldable mechanism.(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:07.851 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185978(Integer), 18. The mobile terminal according to claim 16, wherein the hard support structure further comprises a second support layer wrapping the first support layer, and strength of the second support layer is higher than strength of the first support layer.(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185978(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2017/102310, filed on Sep. 19, 2017, which claims priority to Chinese Patent Application No. 201610836223.0, filed on Sep. 20, 2016. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of mobile terminal technologies, and in particular, to a foldable mechanism of a mobile terminal and the mobile terminal. BACKGROUND [0003]As flexible foldable screen technologies are increasingly mature, foldable terminal products will also be a main trend in the future. A foldable terminal product (for example, an electronic device such as a foldable mobile phone, a foldable tablet, or a foldable computer) needs to have a relatively good ID exterior, so that the product can be accepted by consumers. Using a foldable mobile phone as an example, different from a conventional flip phone, a flexible foldable mobile phone has a screen that can be continuously folded. To ensure that the foldable screen is not pulled or squeezed, a middle hinge folding part of an entire exterior of the product is largely deformed, but a general structure cannot implement such large deformation. Therefore, all foldable mechanisms in the prior art are foldable mechanisms implemented by using a mechanical linkage mechanism, and complexity is relatively high. In addition, when a component of the mechanical linkage mechanism moves, an exterior effect of a mobile terminal is impaired unavoidably. SUMMARY [0004]Embodiments of the present invention provide a foldable mechanism of a mobile terminal and the mobile terminal to improve an effect of the mobile terminal when the mobile terminal is bent. [0005]Embodiments of the present invention provide a foldable mechanism of a mobile terminal. The foldable mechanism includes a soft support structure that connects a first housing and a second housing of the mobile terminal, where the soft support structure includes a plurality of V-shaped supports arranged in a single row, open ends of adjacent V-shaped supports are connected, and an opening of each V-shaped support faces a flexible display screen of the mobile terminal; the foldable mechanism further includes a hard support structure that is disposed in each V-shaped support and configured to support the flexible display screen, where each hard support structure blocks two ends of a V-shaped support corresponding to the hard support structure; and the foldable mechanism further includes a blocking layer disposed between bending tip portions of any two adjacent V-shaped supports; [0006]when the foldable mechanism of the mobile terminal is bent, bending tip portions of the plurality of V-shaped supports converge, and each blocking layer is compressed into a gap between two V-shaped supports connected by the blocking layer; and [0007]when the foldable mechanism of the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports move away from each other, and each blocking layer is unfolded to block the gap between the two V-shaped supports connected by the blocking layer. [0008]In the foregoing technical solution, the foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting the first housing and the second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward, and one side of the soft support structure located on the hard support structure is also extended and bent, so that the entire foldable mechanism forms a C-shaped structure to implement bending of the first housing and the second housing. In the foregoing bending process, the flexible screen is supported by the hard support structure, and the shape of the foldable mechanism is changed according to a change of the soft support structure. Therefore, continuity of connections between the foldable mechanism and the first housing and the second housing is improved, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved. [0009]In a specific implementation solution, a plurality of blocking layers are a bending plate of an integrated structure, a plurality of creases are disposed on the bending plate, the bending tip portions of the plurality of V-shaped supports are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports. That is, the blocking layers use the bending plate to block a gap formed by tip ends of the plurality of V-shaped supports. This improves the exterior effect of the entire mobile terminal. In addition, when being bent, the bending plate occupies less space. Therefore, the exterior effect after the entire structure is bent can be ensured. [0010]In another implementation solution, at least one blocking layer in a plurality of blocking layers is a bending piece, an odd number of creases exist on the bending piece, and two ends of the bending piece are respectively connected to bending tip portions of V-shaped supports on two sides of the blocking layer on a one-to-one basis. That is, the blocking layer may use a structure of a bending piece. There is no great structural difference between the bending piece and the foregoing bending plate. The only difference is that the bending piece in this solution is located between two V-shaped supports. In addition, in this solution, when all blocking layers use bending pieces as described above, after the bending pieces are connected, there is no great structural difference from the bending plate. However, the blocking layer in this solution not only uses the structure of the bending piece, but also may use another foldable mechanism. Therefore, the V-shaped support may be blocked by using different structures. In a specific solution, one crease exists on each bending piece. That is, when being bent, the bending piece needs to be bent only once to fit into the gap between the V-shaped supports. This improves convenience during deformation, reduces a thickness of the bending piece after the bending piece is folded, and improves an effect after the bending piece is bent. [0011]In addition, in a third implementation solution, at least one blocking layer in the plurality of blocking layers includes an elastic material layer disposed between adjacent V-shaped supports. That is, the gap between the V-shaped supports is filled with the elastic material layer. After the foldable mechanism is bent, the elastic material layer is compressed and deformed, so that the foldable mechanism can be bent. When being unfolded, the elastic material recovers to an initial state, and can effectively block the gap between the V-shaped supports. In a specific implementation, each blocking layer may use an elastic material layer. Alternatively, only some blocking layers use elastic material layers. [0012]In a fourth implementation solution, some blocking layers may use bending pieces, and other blocking layers may use elastic material layers, that is, the elastic material layers and the bending pieces are mixed to form the blocking layers, thereby achieving an effect of blocking the gap between the V-shaped supports in the soft support structure. In addition, when being bent, the blocking layers can implement good deformation, and do not affect bending of the foldable mechanism. [0013]In the foregoing solution, when an elastic material layer is used as a blocking layer, each elastic material layer and a V-shaped support adjacent to the elastic material layer are an integrated structure. That is, the elastic material layer and a soft support layer are disposed by using a same material. In this case, the soft support structure may be considered as a sheet-like elastic layer in which a plurality of V-shaped slots are provided and a hard support structure is embedded in each V-shaped slot. [0014]In specific disposition, hard support structure may use different structures. In a manner, each hard support structure includes a first support layer blocking an opening of a V-shaped support corresponding to the hard support frame, and a foldable mechanism blocking one end of the V-shaped support exists at either end of the first support layer. That is, the flexible display screen is supported by the first support layer, and openings at two ends of the V-shaped support are blocked by using foldable mechanisms. Therefore, the mobile terminal is prevented from having an exterior gap or hole. This improves the exterior effect of the mobile terminal. [0015]In a solution, the hard support structure further includes an exterior layer disposed on an external sidewall of the foldable mechanism. The exterior layer is disposed to block the gap when the first support layer is connected to the V-shaped support. This further improves the exterior effect of the mobile terminal. [0016]In addition, to enhance support strength of the hard support structure, connection strength between the hard support structure and the soft support structure is improved. In an improved solution, the hard support structure further includes a second support layer wrapping the first support layer, and strength of the second support layer is higher than strength of the first support layer. That is, the first support layer of the hard support structure is made of a material that has a relatively good adhesive effect with the soft support structure and relatively small hardness, but the second support layer may be made of a material that has relatively high support strength. This improves an effect of supporting the flexible display screen by the hard support structure. [0017]Embodiments of the present invention further provide a mobile terminal. The mobile terminal includes a housing and a flexible display screen disposed in the housing, where the housing includes a first housing, a second housing, and the foldable mechanism for implementing folding of the first housing and the second housing according to any one of the foregoing. [0018]In the foregoing technical solution, the foldable mechanism formed by the soft support structure and the hard support structure embedded in the soft support structure is used as a component for connecting the first housing and the second housing. When the mobile terminal is unfolded, the foldable mechanism formed by the soft support structure and the hard support structure is unfolded and turns into a flat structure connected to the first housing and the second housing. When the mobile terminal is folded, one side of the soft support structure away from the hard support structure shrinks inward, and one side of the soft support structure located on the hard support structure is also extended and bent, so that the entire foldable mechanism forms a C-shaped structure to implement bending of the first housing and the second housing. In the foregoing bending process, the flexible screen is supported by the hard support structure, and the shape of the foldable mechanism is changed according to a change of the soft support structure. Therefore, continuity of connections between the foldable mechanism and the first housing and the second housing is improved, the mobile terminal is prevented from having an abrupt exterior structure, and an exterior effect of the mobile terminal is improved. BRIEF DESCRIPTION OF DRAWINGS [0019]FIG. 1 is a schematic view of a mobile terminal in a folded state according to an embodiment of the present invention; [0020]FIG. 2 is a schematic exploded view of a mobile terminal in a folded state according to an embodiment of the present invention; [0021]FIG. 3 is a schematic view of a mobile terminal in an unfolded state according to an embodiment of the present invention; [0022]FIG. 4 is a schematic exploded view of a mobile terminal in an unfolded state according to an embodiment of the present invention; [0023]FIG. 5 is a schematic view of a foldable mechanism in a bent state according to an embodiment of the present invention; [0024]FIG. 6 is a schematic exploded view of a foldable mechanism in a bent state according to an embodiment of the present invention; [0025]FIG. 7 is a schematic view of a foldable mechanism in an unfolded state according to an embodiment of the present invention; [0026]FIG. 8 is a schematic status diagram of a foldable mechanism in a bending process according to an embodiment of the present invention; [0027]FIG. 9 is a schematic exploded view of another foldable mechanism according to an embodiment of the present invention; [0028]FIG. 10 is a schematic view of a third foldable mechanism according to an embodiment of the present invention; [0029]FIG. 11 is a sectional view of a hard support structure according to an embodiment of the present invention; and [0030]FIG. 12 is a schematic exploded view of a foldable mechanism when the hard support structure shown in FIG. 11 is used according to an embodiment of the present invention. REFERENCE SIGNS IN THE DRAWINGS [0031]10: flexible display screen; 20: first housing; 30: second housing[0032]40: foldable mechanism; 41: soft support structure; 411: V-shaped support[0033]42: hard support structure; 421: first support layer; 422: foldable mechanism[0034]423: exterior layer; 43: blocking layer; 431: bending piece; 4311: first bending piece[0035]4312: second bending piece; 432: elastic material layer DESCRIPTION OF EMBODIMENTS [0036]To make the objectives, technical solutions, and advantages of the present invention clearer, the following further describes the present invention in detail with reference to the accompanying drawings. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. [0037]As shown in FIG. 1 and FIG. 3, FIG. 1 and FIG. 3 are schematic views of a mobile terminal in different states according to an embodiment of the present invention. [0038]An embodiment of the present invention provides a foldable mechanism of a mobile terminal. The foldable mechanism is applied to the mobile terminal. The mobile terminal includes a housing and a flexible display screen 10 disposed in the housing. The housing includes a first housing 20, a second housing 30, and the foldable mechanism 40 for implementing folding of the first housing 20 and the second housing 30 according to any one of the foregoing. The first housing 20 and the second housing 30 are connected by the foldable mechanism 40 to form an entirety. The flexible display screen 10 is installed in the housing formed by the first housing 20 and the second housing 30. [0039]As shown in FIG. 5, FIG. 6, and FIG. 7, FIG. 5 and FIG. 7 are schematic views of the foldable mechanism 40 in different states, and FIG. 6 is a schematic exploded view of the foldable mechanism 40. The foldable mechanism 40 provided by this embodiment has a bending function. The foldable mechanism 40 may be used to implement bending and unfolding of the first housing 20 and the second housing 30, that is, implement folding and unfolding of the mobile terminal. Specifically, the foldable mechanism 40 includes a soft support structure 41 that connects the first housing 20 and the second housing 30. The soft support structure 41 includes a plurality of V-shaped supports 411 arranged in a single row, and open ends of adjacent V-shaped supports 411 are connected. Specifically, as shown in FIG. 5 and FIG. 6, top positions of sidewalls between two adjacent V-shaped supports 411 are connected, and the plurality of V-shaped supports 411 are connected in sequence, so that the plurality of V-shaped supports 411 are connected to form an entirety. In addition, in specific disposition, a length direction of each V-shaped support 411 is parallel to a direction of rotation of the first housing 20 relative to the second housing 30, that is, in the V-shaped supports 411 arranged in the single row, V-shaped supports 411 located at two ends are connected to the first housing 20 and the second housing 30 respectively. Therefore, when the first housing 20 and the second housing 30 rotate relatively, the V-shaped supports 411 can be deformed, and tip portions of the V-shaped supports 411 move in a direction of convergence. Therefore, the soft support frame forms a structure, with its interior (one side away from the flexible display screen 10) converging and its exterior (facing the flexible display screen 10) being extended. [0040]In addition, in disposition, an opening of each V-shaped support 411 faces the flexible display screen 10, and a hard support structure 42 configured to support the flexible display screen 10 is disposed in each V-shaped support 411. The hard support structure 42 is fixed in a groove part in the V-shaped support 411, and faces the flexible display screen 10. The hard support structure 42, the first housing 20, and the second housing 30 together form a support structure for the flexible display screen 10. In the foregoing description, it should be understood that, “soft” and “hard” in the soft support structure 41 and the hard support structure 42 provided by this embodiment are relative concepts, and are relative features of materials in two parts of structures in the foldable mechanism 40. [0041]In specific disposition, the hard support structure 42 is located in a dented area of the V-shaped support 411, and each hard support structure 42 blocks two ends of a V-shaped support 411 corresponding to the hard support structure 42. The hard support structure 42 is disposed to block openings at the two ends of the V-shaped support 411. Therefore, adverse impact caused by a gap or the like on an exterior surface of the foldable mechanism 40 to an exterior structure of the mobile terminal is avoided, and exterior consistency of the mobile terminal is improved. [0042]In specific disposition, the hard support structure 42 may use different structures. As shown in FIG. 5 and FIG. 6, each hard support structure 42 includes a first support layer 421 blocking an opening of a V-shaped support 411 corresponding to the hard support frame, and a foldable mechanism 422 blocking one end of the V-shaped support 411 exists at either end of the first support layer 421. Specifically, each hard support structure 42 includes one first support layer 421 and one foldable mechanism 422 located at either end of the first support layer 421. The first support layer 421 blocks a top opening position of the V-shaped support 411, and the foldable mechanisms 422 located at the two ends of the first support layer 421 block V-shaped openings at the two ends of the V-shaped support 411 respectively. The first support layer 421 is disposed to support the flexible display screen 10, and the foldable mechanisms 422 are disposed to block the openings at the two ends of the V-shaped support 411, thereby ensuring exterior consistency of the foldable mechanisms 422. An assembled structure is shown in FIG. 5. [0043]In addition, to improve structure strength and an exterior effect of the hard support structure 42, preferably, the hard support structure 42 further includes an exterior layer 423 disposed on an external sidewall of the foldable mechanism 422. As shown in FIG. 11 and FIG. 12, the foldable mechanism 422 at either end of the first support layer 421 of each hard support structure 42 is fixedly sleeved with an exterior layer 423. The exterior layer 423 is configured to block a gap at a joint of the foldable mechanism 422 and the V-shaped support 411, thereby improving an exterior effect of the entire foldable mechanism 422. In addition, support strength of the exterior layer 423 is higher than strength of the first support layer 421. This further enhances support strength of the entire foldable mechanism 422. That is, the exterior layer 423 is disposed to block the gap when the first support layer 421 is connected to the V-shaped support 411. This further improves an exterior effect of the mobile terminal. [0044]As a variation of the hard support structure 42 shown in FIG. 11 and FIG. 12, the hard support structure 42 may not only use the foregoing exterior layer 423, but also use a second support layer disposed on the first support layer 421 to improve a support effect and the exterior effect. Specifically, the hard support structure 42 further includes a second support layer wrapping the first support layer 421, and strength of the second support layer is higher than strength of the first support layer 421. Structurally, a structure of the second support layer is the same as a structure of the first support layer 421, that is, both include a support layer and a foldable mechanism 422 disposed at either end of the support layer. In addition, in specific disposition, the second support layer is located on one side of the first support layer 421 away from the V-shaped support 411, and the first support layer 421 and the first support layer 421 are disposed in an overlapping manner, so that the second support layer wraps the first support layer 421, that is, it may be considered that the first support layer 421 and the second support layer are disposed in a sleeving manner. In addition, in specific disposition, strength of the first support layer 421 is lower than strength of the second support layer, that is, the first support layer 421 is made of a low-strength material that cooperates more easily with the V-shaped support 411 made of a soft material, but the second support layer is made of a material of relatively high strength. Use of the foregoing materials and structures ensures a combination of the soft support structure 41 and the hard support structure 42, and also enhances a support effect of the hard support structure 42 for the flexible display screen 10. [0045]Referring to FIG. 8, FIG. 9, and FIG. 10, FIG. 8 is a status diagram in a bending process, and is a simplified schematic diagram. The mobile terminal further includes a blocking layer 431 disposed between bending tip portions of any two adjacent V-shaped supports 411. The blocking layer 431 is configured to block a gap between tip portions of the plurality of V-shaped supports 411. As shown in FIG. 1 and FIG. 2, when the mobile terminal is folded, bending tip portions of the plurality of V-shaped supports 411 converge, and each blocking layer 431 is compressed into a gap between two V-shaped supports 411 connected by the blocking layer 431, so that the foldable mechanism 40 forms a C-shaped structure, and that the first housing 20 overlaps the second housing 30 to implement folding of the mobile terminal. As shown in FIG. 3 and FIG. 4, when the mobile terminal is unfolded, the bending tip portions of the plurality of V-shaped supports 411 move away from each other, and each blocking layer 431 is unfolded to block the gap between the two V-shaped supports 411 connected by the blocking layer 431. In this case, the blocking layer 431 is unfolded to block the gap between the tip portions of the V-shaped supports. [0046]In specific disposition, the blocking layer 431 may use different structures to block the gap between the tip portions of the V-shaped supports 411. As shown in FIG. 8, the blocking layer 431 uses a bending piece 431. As shown in FIG. 9, the blocking layer 431 uses an elastic material layer 432. Alternatively, as shown in FIG. 10, some blocking layers 431 use bending pieces 431, and other blocking layers 431 use different structures such as elastic material layers 432 to block the tip portions of the V-shaped supports 411. For ease of understanding, the following describes the structures by using examples separately. [0047]As shown in FIG. 8, in a plurality of blocking layers 431, at least one blocking layer 431 is a bending piece 431. In the structure shown in FIG. 8, a structure in which all blocking layers 431 are bending pieces 431 is shown. However, it should be understood that, the blocking layer 431 may also use a structure different from the bending piece 431. For the bending piece 431, an odd number of creases exist on the bending piece 431, and two ends of the bending piece 431 are respectively connected to bending tip portions of V-shaped supports 411 on two sides of the blocking layer 431 on a one-to-one basis. In addition, the bending piece 431 is disposed in a gap between tip portions of adjacent V-shaped supports 411. Still referring to FIG. 8, FIG. 8 shows a bending status of the bending piece 431 in a bending process. As can be seen from FIG. 8, the crease of the bending piece 431 causes the bending piece 431 to be bent into a gap between tip portions of the adjacent V-shaped supports 411, so that the folded bending piece 431 can shrink in the gap. Therefore, when being bent, the bending piece 431 is prevented from protruding, which otherwise affects an exterior of the foldable mechanism 40. In specific disposition, the number of creases on the bending piece 431 is an odd number, for example, 1, 3, or 5. In use of the odd number of creases, it is ensured that when the bending piece 431 is bent, an outermost end of the bending piece 431 can be flush to the tip portions of the V-shaped supports 411 or shrink in the gap between the V-shaped supports 411, and further, it is ensured that the bending piece 431 does not interfere with the foldable mechanism 40 when the foldable mechanism 40 is bent. In addition, when the mobile terminal is unfolded, the bending piece 431 can be flush to the tip portions of the V-shaped supports 411 as far as possible. This ensures exterior consistency of the mobile terminal, and improves the exterior effect of the mobile terminal. In a specific implementation solution, as shown in FIG. 8, one crease exists on each bending piece 431, that is, the bending piece 431 includes a first bending piece 4311 and a second bending piece 4312. That is, when being bent, the bending piece 431 needs to be bent only once to fit into the gap between the V-shaped supports 411. This improves convenience during deformation, reduces a thickness of the bending piece 431 after the bending piece 431 is folded, and improves an effect after the bending piece 431 is bent. [0048]As a variation of the foldable mechanism 40 shown in FIG. 8, in another solution, a plurality of blocking layers 431 are a bending plate of an integrated structure, a plurality of creases are disposed on the bending plate, the bending tip portions of the plurality of V-shaped supports 411 are fixedly connected to the creases on the bending plate at equal intervals, and an odd number of creases exist between adjacent V-shaped supports 411. In the foregoing structure, it may be considered that when each blocking layer 431 uses a bending piece 431, a plurality of bending piece 431 are connected in sequence to form an integrated structure. When the blocking layers 431 use the bending plate to block the gap formed by tip ends of the plurality of V-shaped supports, a tip portion of a V-shaped support 411 corresponds to a crease on the bending plate, and a bending plate part located on two sides of the tip portion of the V-shaped support 411, when being bent, is attached to a sidewall of the V-shaped support 411. When being bent, a bending plate part located between two V-shaped supports 411 is located in the gap between the V-shaped supports 411. A specific operating principle thereof is similar to that of the bending piece 431 shown in FIG. 8. Details are not further described herein. [0049]In another structure of the blocking layer 431, at least one blocking layer 431 in the plurality of blocking layers 431 includes an elastic material layer 432 disposed between adjacent V-shaped supports 411. As shown in FIG. 9, FIG. 9 is a schematic view of a structure that uses the elastic material layer 432 as the blocking layer 431. In this embodiment, the gap between the adjacent V-shaped supports 411 is filled with the elastic material layer 432. In specific disposition, the elastic material layer 432 may be made of different materials, for example, a material such as rubber or plastic, provided that the material can have good elasticity. After the foldable mechanism 40 is bent, the elastic material layer 432 is compressed and deformed, so that the foldable mechanism 40 can be bent. When being unfolded, the elastic material recovers to an initial state, and can effectively block the gap between the V-shaped supports 411. In a specific implementation, each blocking layer 431 may use an elastic material layer 432. Alternatively, only some blocking layers use elastic material layers 432. Specific disposition may be determined according to an actual situation. In a specific solution, each elastic material layer 432 and a V-shaped support 411 adjacent to the elastic material layer 432 are an integrated structure. That is, the elastic material layer 432 and a soft support layer are disposed by using a same material, and form an integrated structure. In this case, the soft support structure 41 may be considered as a sheet-like elastic material layer in which a plurality of V-shaped slots are provided and a hard support structure 42 is embedded in each V-shaped slot. When the foregoing structure is used, it can be seen that, when the entire soft support structure 41 is disposed, a lateral side is blocked by the elastic material layer 432, and the elastic material layer 432 and the V-shaped support 411 are disposed in an integrated structure, so that when the mobile terminal is unfolded, a lateral side away from the hard support structure 42 may be a smooth side. This further improves the exterior effect of the entire mobile terminal. [0050]In the foregoing description, the blocking layer 431 may use different structures. As shown in FIG. 10, FIG. 10 shows a form of the blocking layer 431 that uses a combination of a bending piece 431 and an elastic material. As can be seen from FIG. 10, some blocking layers 431 use bending pieces 431, and other blocking layers 431 use elastic material layers 432. That is, the elastic material layers 432 and the bending pieces 431 are mixed to form the blocking layers 431, thereby achieving an effect of blocking the gap between the V-shaped supports 411 in the soft support structure. In addition, when being bent, the blocking layers 431 can implement good deformation, and do not affect bending of the foldable mechanism 40. [0051]When the foregoing formed foldable mechanism 40 is used, the foldable mechanism 40 formed by the soft support structure 41 and the hard support structure 42 embedded in the soft support structure 41 is used as a component for connecting the first housing 20 and the second housing 30. As shown in FIG. 3 and FIG. 4, when the mobile terminal is unfolded, the foldable mechanism 40 formed by the soft support structure 41 and the hard support structure 42 is unfolded and turns into a flat structure connected to the first housing 20 and the second housing 30. As shown in FIG. 1 and FIG. 2, when the mobile terminal is folded, one side of the soft support structure 41 away from the hard support structure 42 shrinks inward, and one side of the soft support structure 41 located on the hard support structure 42 is also extended and bent, so that the entire foldable mechanism 40 forms a C-shaped structure to implement bending of the first housing 20 and the second housing 30. In the foregoing bending process, the flexible screen is supported by the hard support structure, and the shape of the foldable mechanism 40 is changed according to a change of the soft support structure 41. Therefore, continuity of connections between the foldable mechanism 40 and the first housing 20 and the second housing 30 is improved, the mobile terminal is prevented from having an abrupt exterior structure, and the exterior effect of the mobile terminal is improved. [0052]Obviously, a person skilled in the art can make various modifications and variations to the present invention without departing from the spi(String), 相关申请的交叉引用 [0001] 本申请是2017年9月19日提交的国际申请PCT/CN2017/102310的继续申请,该国际申请要求2016年9月20日提交的中国专利申请201610836223.0的优先权。上述申请的公开内容是 特此通过引用整体并入。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端的折叠机构及移动终端。 背景 [0003] 随着柔性折叠屏技术的日益成熟,可折叠终端产品也将是未来的主流趋势。 可折叠终端产品(例如可折叠手机、可折叠平板电脑、可折叠电脑等电子设备)需要有一个比较好的ID外观,这样产品才能被消费者接受。 以可折叠手机为例,与传统的翻盖手机不同,柔性可折叠手机的屏幕可以连续折叠。 为了保证折叠屏不被拉扯和挤压,产品整个外观的中间铰链折叠部分变形较大,而一般的结构无法实现如此大的变形。 因此,现有技术中的折叠机构都是采用机械联动机构实现的折叠机构,复杂度较高。 另外,当机械联动机构的部件移动时,不可避免地会影响移动终端的外观效果。 概括 [0004] 本发明实施例提供一种移动终端的折叠机构及移动终端,以提高移动终端弯曲时的效果。 [0005] 本发明实施例提供了一种移动终端的折叠机构。 折叠机构包括连接移动终端的第一壳体和第二壳体的软质支撑结构,软质支撑结构包括多个排成一排的V型支架,相邻V型支架的开口端为 连接,每个V型支架的开口面向移动终端的柔性显示屏; 折叠机构还包括硬质支撑结构,硬质支撑结构设置于各V型支架内,用于支撑柔性显示屏,各硬质支撑结构挡住与硬质支撑结构对应的V型支架的两端。 折叠机构还包括阻挡层,设置在任意两个相邻的V型支撑件的弯曲尖端部之间。 [0006] 当移动终端的折叠机构弯曲时,多个V型支撑件的弯曲尖端部分会合,每个阻挡层被压入阻挡层连接的两个V型支撑件之间的间隙中。 和 [0007] 当移动终端的折叠机构展开时,多个V型支撑件的弯曲尖端部分相互远离,各阻挡层展开以阻挡阻挡件连接的两个V型支撑件之间的缝隙。 层。 [0008]上述技术方案中,采用软质支撑结构和嵌入软质支撑结构中的硬质支撑结构形成的折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软质支撑结构和硬质支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 折叠移动终端时,软支撑结构远离硬支撑结构的一侧向内收缩,软支撑结构位于硬支撑结构上的一侧也伸展弯曲,从而形成整个折叠机构。 C型结构,实现第一壳体和第二壳体的弯折。 在上述弯折过程中,柔性屏由硬质支撑结构支撑,折叠机构的形状随着软质支撑结构的变化而变化。 从而提高了折叠机构与第一壳体和第二壳体连接的连续性,避免了移动终端的外观结构突兀,提高了移动终端的外观效果。 [0009] 在一种具体实施方案中,所述多个阻挡层为一体结构的折弯板,所述折弯板上设置有多个折痕,所述多个V型支架的折弯尖端部固定连接在折痕上。 折弯板等间距排列,相邻V型支撑之间存在奇数条折痕。 即,挡层利用弯板挡住多个V型支架的末端形成的间隙。 提高了整个移动终端的外观效果。 此外,弯曲板在弯曲时占用的空间更小。 因此,可以保证整个结构弯曲后的外观效果。 [0010] 在另一种实施方案中,多个阻挡层中的至少一个阻挡层为弯折件,弯折件上存在奇数条折痕,弯折件的两端分别连接V形的弯折尖端部。 一对一支撑在阻挡层的两侧。 即,阻挡层可以采用弯折件的结构。 该折弯件与上述折弯板在结构上没有太大区别。 唯一不同的是,该方案中的弯曲件位于两个V型支架之间。 另外,在该方案中,当所有阻挡层都采用如上所述的折弯件时,折弯件连接后,与折弯板在结构上没有太大的区别。 但是,该方案中的阻挡层不仅采用弯折件的结构,还可以采用另一种折叠机构。 因此,可以采用不同的结构来阻挡V型支架。 具体方案中,每个折弯件上存在一条折痕。 也就是说,在弯曲时,弯曲件只需弯曲一次即可嵌入到V型支架之间的缝隙中。 提高了变形时的便利性,减小了弯折件折叠后的厚度,提高了弯折件弯折后的效果。 [0011] 另外,在第三种实施方案中,所述多个阻挡层中的至少一个阻挡层包括设置在相邻V型支撑件之间的弹性材料层。 即,V型支撑件之间的间隙被弹性材料层填充。 折叠机构弯折后,弹性材料层受压变形,使得折叠机构可弯折。 弹性材料在展开时恢复到初始状态,可以有效地堵住V型支架之间的缝隙。 在具体实施中,各阻挡层可以采用弹性材料层。 或者,只有部分阻挡层使用弹性材料层。 [0012]在第四种实施方案中,部分阻挡层可以使用弯折件,其他阻挡层可以使用弹性材料层,即弹性材料层和弯折件混合形成阻挡层,从而达到阻挡的效果。 软支撑结构中 V 形支撑之间的间隙。 另外,在弯曲时,阻挡层可以实现良好的形变,不影响折叠机构的弯曲。 [0013] 上述方案中,当采用弹性材料层作为阻挡层时,各弹性材料层和与弹性材料层相邻的V型支架为一体结构。 即,弹性材料层和软质支撑层采用相同的材​​料设置。 在这种情况下,软支撑结构可以被认为是片状弹性层,其中设置有多个V形槽,并且在每个V形槽中嵌入硬支撑结构。 [0014] 在具体配置中,硬支撑结构可以采用不同的结构。 在一种方式中,每个硬质支撑结构包括第一支撑层,第一支撑层挡住与硬质支撑架对应的V型支架的开口,第一支架的两端分别设有挡住V型支架一端的折叠机构。 层。 即,柔性显示屏由第一支撑层支撑,V型支撑体两端开口采用折叠机构封闭。 因此,防止移动终端具有外部间隙或孔。 这提高了移动终端的外观效果。 [0015] 在一个方案中,硬质支撑结构还包括设置在可折叠机构的外侧壁上的外层。 当第一支撑层连接至V型支撑件时,设置外层以阻挡间隙。 这进一步提高了移动终端的外观效果。 [0016] 此外,为了增强硬质支撑结构的支撑强度,硬质支撑结构与软质支撑结构之间的连接强度得到提高。 在一种改进方案中,所述硬质支撑结构还包括包裹所述第一支撑层的第二支撑层,所述第二支撑层的强度高于所述第一支撑层的强度。 即,硬质支撑结构的第一支撑层采用与软质支撑结构的粘合效果较好且硬度较小的材料,而第二支撑层可以采用与软质支撑结构具有较高支撑力的材料制成 力量。 提高了硬质支撑结构对柔性显示屏的支撑效果。 [0017] 本发明实施例还提供了一种移动终端。 该移动终端包括壳体和设置在壳体内的柔性显示屏,壳体包括第一壳体、第二壳体以及根据前述任一项所述的用于实现第一壳体和第二壳体折叠的折叠机构。 . [0018]上述技术方案中,采用软质支撑结构和嵌入软质支撑结构中的硬质支撑结构形成的折叠机构作为连接第一壳体和第二壳体的部件。 当移动终端展开时,由软质支撑结构和硬质支撑结构形成的折叠机构展开,变成连接第一壳体和第二壳体的平面结构。 折叠移动终端时,软支撑结构远离硬支撑结构的一侧向内收缩,软支撑结构位于硬支撑结构上的一侧也伸展弯曲,从而形成整个折叠机构。 C型结构,实现第一壳体和第二壳体的弯折。 在上述弯折过程中,柔性屏由硬质支撑结构支撑,折叠机构的形状随着软质支撑结构的变化而变化。 从而提高了折叠机构与第一壳体和第二壳体连接的连续性,避免了移动终端的外观结构突兀,提高了移动终端的外观效果。 附图说明 [0019] 图1是本发明一个实施例的移动终端处于折叠状态的示意图; [0020] 图2是本发明一个实施例的移动终端处于折叠状态的分解示意图; [0021] 图3是本发明一个实施例的移动终端处于展开状态的示意图; [0022] 图4是本发明一个实施例的移动终端处于展开状态的分解示意图; [0023] 图5为本发明一实施例的折叠机构处于弯曲状态的示意图。 [0024] 图6为本发明一实施例的折叠机构处于弯曲状态的分解示意图。 [0025] 图7为本发明一实施例的折叠机构处于展开状态的示意图。 [0026] 图8为本发明实施例的折叠机构在折弯过程中的状态示意图; [0027] 图9为本实用新型一实施例的另一种折叠机构的分解示意图。 [0028] 图10为本发明实施例的第三种折叠机构的示意图。 [0029] 图11为本发明一实施例的硬质支撑结构的剖面图。 和 [0030] 图12为本发明一实施例的使用图11所示的硬质支撑结构时的折叠机构的分解示意图。 附图中的参考标记 [0031]10 :柔性显示屏; 20 : 第一住房; 30 : 第二套住房[0032]40 :可折叠机制; 41 :软支撑结构; 411 :V型支撑[0033]42 :硬支撑结构; 421 :第一支撑层; 422 :折叠机制[0034]423 : 外层; 43 : 阻挡层; 431 : 弯曲件; 4311 :第一个弯曲件[0035]4312 : 第二弯曲件; 432 : 弹性材料层 具体实施方式 [0036] 为使本发明的目的、技术方案和优点更加清楚,下面将结合附图对本发明作进一步地详细描述。 显然,所描述的实施例仅仅是本发明的一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0037] 如图1和图3所示,图1和图3是根据本发明实施例的移动终端在不同状态下的示意图。 [0038] 本发明实施例提供了一种移动终端的折叠机构。 折叠机构应用于移动终端。 移动终端包括外壳和柔性显示屏 10 布置在外壳中。 外壳包括第一外壳 20 , 第二个住房 30 , 和可折叠机制 40 用于实现第一外壳的折叠 20 和第二个住房30 根据上述任何一项。 第一住房 20 和第二个住房 30 由可折叠机构连接 40 形成一个整体。 柔性显示屏 10 安装在由第一壳体形成的壳体中 20 和第二个住房 30 . [0039] 如图5、图6、图7所示,图5、图7为折叠机构示意图 40 不同状态下,图6为折叠机构的分解示意图 40 . 可折叠机构 40 本实施例提供的弯折功能。 可折叠机构 40 可用于实现第一外壳的弯曲和展开 20 和第二个住房 30 ,即实现移动终端的折叠和展开。 具体来说,折叠机构 40 包括软支撑结构 41 连接第一个外壳 20 和第二个住房 30 . 软支撑结构 41 包括多个V形支架 411 单排排列,相邻V型支架两端开口 411 连接。 具体地,如图5和图6所示,两个相邻V型支架之间的侧壁顶部位置 411 连接起来,并且多个V形支撑 411 依次连接,使得多个V形支架 411 连接起来形成一个整体。 另外,在具体配置中,每个V型支架的长度方向 411 平行于第一壳体的旋转方向 20 相对于第二个住房 30 ,也就是说,在 V 形支撑 411 单排排列,V型支撑 411 位于两端连接第一壳体 20 和第二个住房 30 分别。 因此,当第一个住房 20 和第二个住房 30 相对旋转,V形支撑 411 可以变形,并且 V 形支撑的尖端部分 411 向趋同的方向发展。 因此,软支撑架形成一个结构,其内部(远离柔性显示屏的一侧 10 ) 会聚及其外部(面向柔性显示屏 10 ) 被扩展。 [0040] 此外,在配置中,每个V形支架的开口 411 面向柔性显示屏 10 和硬支撑结构 42 配置为支持柔性显示屏 10 设置在每个V型支架中 411 . 硬支撑结构 42 固定在V型支架的凹槽部分 411 ,面向柔性显示屏 10 . 硬支撑结构 42 , 第一个住房 20 , 和第二个住房 30 共同构成柔性显示屏的支撑结构 10 . 在上述描述中,应当理解,软支撑结构中的“软”和“硬” 41 和硬支撑结构 42 本实施例提供的是相对概念,是折叠机构中两部分结构的材料的相对特征。 40 . [0041] 具体配置中,硬支撑结构 42 位于 V 形支架的凹陷区域 411 , 和每个硬支撑结构 42 挡住V型支架的两端 411 对应硬支撑结构 42 . 硬支撑结构 42 设置成堵住V型支架两端的开口 411 . 因此,可折叠机构的外表面上的间隙等造成的不利影响 40 避免了移动终端的外观结构,提高了移动终端的外观一致性。 [0042] 具体配置中,硬支撑结构 42 可以使用不同的结构。 如图5和图6所示,各硬支撑结构 42 包括第一支撑层 421 堵住V型支架的开口 411对应硬质支撑架,折叠机构 422 挡住V型支架的一端 411 存在于第一支撑层的两端 421 . 具体来说,每个硬支撑结构 42 包括一个第一支撑层 421 和一个可折叠机构 422 位于第一支撑层的两端 421 . 第一支撑层 421 挡住V型支架的顶部开口位置 411 , 以及可折叠机制 422 位于第一支撑层的两端 421 V型支架两端挡V型开口 411 分别。 第一支撑层 421 用以支撑柔性显示屏 10 , 以及可折叠机制 422 设置成堵住V型支架两端的开口 411 ,从而确保可折叠机制的外部一致性 422 . 组装后的结构如图5所示。 [0043] 此外,提高硬支撑结构的结构强度和外部效果 42 , 最好是硬支撑结构 42 还包括外层 423 设置在折叠机构的外侧壁上 422 . 如图11和图12所示,折叠机构 422 在第一支撑层的两端 421 每个硬支撑结构 42 固定套有外层 423 . 外层 423 用于堵住折叠机构的连接处的缝隙 422 和V形支撑 411 ,从而提升整个折叠机构的外观效果 422 . 此外,外层的支撑强度 423 高于第一支撑层的强度 421 . 这进一步增强了整个折叠机构的支撑强度 422 . 即外层 423 被布置成在第一支撑层时阻挡间隙 421 连接到V型支架 411 . 这进一步改善了移动终端的外观效果。 [0044] 作为硬支撑结构的变体 42 如图11和图12所示,硬支撑结构 42 可能不仅使用前述外层 423 , 但也使用设置在第一支撑层上的第二支撑层 421 提高支撑效果和外在效果。 具体来说,硬支撑结构 42 还包括包裹第一支撑层的第二支撑层 421 ,且第二支撑层的强度高于第一支撑层的强度 421 . 在结构上,第二支撑层的结构与第一支撑层的结构相同 421 ,也就是说,两者都包括支撑层和可折叠机构 422 设置在支撑层的两端。 另外,在具体设置中,第二支撑层位于第一支撑层的一侧 421 远离V型支撑 411 , 和第一支撑层 421 和第一支撑层 421 以重叠方式设置,使得第二支撑层包裹第一支撑层 421 ,也就是说,可以认为第一支撑层 421 第二支撑层套设设置。 另外,在具体配置中,第一支撑层的强度 421 低于第二支撑层即第一支撑层的强度 421 由低强度材料制成,更容易与V型支架配合 411 由柔软的材料制成,而第二支撑层由强度较高的材料制成。 上述材料和结构的使用确保了软支撑结构的组合 41 和硬支撑结构 42 ,也增强了硬支撑结构的支撑作用 42 用于柔性显示屏 10 . [0045]请参阅图8、图9、图10,图8为折弯过程中的状态图,为简化示意图。 移动终端还包括阻挡层 431 设置在任意两个相邻V型支架的弯曲尖端部分之间 411 . 阻挡层 431 被配置为阻塞多个V形支撑件的尖端部分之间的间隙 411 . 如图1和图2所示,当移动终端折叠时,多个V型支架的尖端部分弯曲 411 收敛,每个阻塞层 431 被压缩到两个 V 形支撑之间的间隙中 411 由阻塞层连接 431 ,这样折叠机构 40 形成一个C形结构,并且第一个外壳 20 与第二个外壳重叠 30 实现移动终端的折叠。 如图3和图4所示,当移动终端展开时,多个V形支架的弯曲尖端部分 411 彼此远离,每个阻挡层 431 展开挡住两个V型支架之间的缝隙 411 由阻塞层连接 431 . 在这种情况下,阻挡层 431 展开以堵住V形支架尖端部分之间的间隙。 [0046] 具体配置中,阻挡层 431 可以使用不同的结构来堵住V形支架尖端部分之间的间隙 411 . 如图8所示,阻挡层 431 使用弯曲件 431 . 如图9所示,阻挡层 431 使用弹性材料层 432 . 或者,如图10所示,一些阻挡层 431 使用弯曲件 431 和其他阻挡层 431 使用不同的结构,例如弹性材料层 432 挡住 V 形支架的尖端部分 411 . 为了便于理解,下面分别举例说明结构。 [0047] 如图8所示,在多个阻挡层中 431 , 至少一层阻挡层 431 是弯曲件 431 . 在图8所示的结构中,所有阻挡层的结构 431 是弯曲件 431 显示。 但是,应该理解的是,阻挡层 431 也可采用与弯管件不同的结构 431 . 对于弯曲件 431 , 折弯件上存在奇数条折痕 431 , 弯曲件的两端 431 分别连接到V形支架的弯曲尖端部分 411 在阻挡层的两侧 431 在一对一的基础上。 另外,弯曲件 431 设置在相邻V型支架的尖端部分之间的间隙中 411 . 仍然参见图8,图8显示了弯曲件的弯曲状态 431 在弯曲过程中。 从图8可以看出,折弯件的折痕 431 导致弯曲件 431 弯入相邻V型支架尖端部分之间的缝隙 411 , 使折叠的弯曲件 431 可以缩小在差距。 因此,弯曲时,弯曲件 431 防止突出,否则会影响可折叠机构的外部 40 . 具体配置中,折弯件的折痕数量 431 为奇数,例如1、3、5。在使用奇数折痕时,保证折弯件时 431 弯曲,弯曲件的最外端 431 可以齐平到 V 形支架的尖端部分 411 或缩小V形支架之间的间隙 411 , 进一步保证弯曲件 431 不干扰折叠机制 40 当折叠机制 40 是弯曲的。 另外,当移动终端展开时,弯折件 431 可以齐平到 V 形支架的尖端部分 411越远越好。 保证了移动终端外观的一致性,提高了移动终端的外观效果。 在一种具体实施方案中,如图8所示,每个折弯件上存在一条折痕 431 , 即弯曲件 431 包括第一弯曲件 4311 和第二个弯曲件 4312 . 即弯曲时,弯曲件 431 只需弯曲一次即可装入 V 形支架之间的间隙 411 . 这提高了变形过程中的便利性,减少了弯曲件的厚度 431 弯曲件后 431 折叠,提高了折弯件后的效果 431 是弯曲的。 [0048] 作为可折叠机制的变体 40 如图8所示,在另一种方案中,多个阻挡层 431 为一体结构的折弯板,折弯板上设置有多个折痕,多个V形支架的折弯尖端部分 411 等间距固定连接在弯板上的折痕上,相邻V型支撑之间存在奇数个折痕 411 . 在上述结构中,可以认为当每个阻挡层 431 使用弯曲件 431 , 多个折弯件 431 依次连接形成一个整体结构。 当阻挡层 431 利用弯板堵住多个V型支架的尖端形成的缝隙,V型支架的尖端部分 411 对应折弯板上的折痕,折弯板部分位于V型支架尖端部分的两侧 411 , 弯曲时, 附在 V 形支架的侧壁上 411 . 弯曲时,位于两个V型支架之间的弯曲板部分 411 位于V型支架之间的空隙中 411 . 其具体工作原理与弯管件类似 431 如图8所示,在此不再赘述。 [0049] 在阻挡层的另一种结构中 431 , 至少一层阻挡层 431 在多个阻挡层中 431 包括弹性材料层 432 布置在相邻的V形支架之间 411 . 如图9所示,图9为采用弹性材料层的结构示意图 432 作为阻挡层 431 . 在本实施例中,相邻V型支架之间的间隙 411 填充有弹性材料层 432 . 具体配置中,弹性材料层 432 可以由不同的材料制成,例如橡胶或塑料等材料,只要该材料能够具有良好的弹性。 后折叠机构 40 被弯曲时,弹性材料层 432 被压缩变形,使折叠机构 40 可以弯曲。 展开时,弹性材料恢复初始状态,可有效堵住V型支架之间的缝隙 411 . 在具体实现中,每个阻塞层 431 可以使用弹性材料层 432 . 或者,只有一些阻挡层使用弹性材料层 432 . 具体配置可根据实际情况确定。 在具体方案中,各弹性材料层 432 和一个V形支架 411 紧邻弹性材料层 432 是一个集成的结构。 即弹性材料层 432 软质支撑层采用同种材料设置,形成一体结构。 在这种情况下,软支撑结构 41 可以认为是片状弹性材料层,其中设置有多个V形槽和硬质支撑结构 42 嵌在每个 V 形槽中。 当采用上述结构时,可以看出,当整个软支撑结构 41 设置时,侧面被弹性材料层挡住 432 , 和弹性材料层 432 和V形支撑 411一体式结构设置,使得移动终端展开时,远离硬质支撑结构的侧面 42 可能是光滑的一面。 这进一步提高了整个移动终端的外观效果。 [0050] 在前面的描述中,阻挡层 431 可以使用不同的结构。 如图10所示,图10为阻挡层的一种形式 431 使用弯曲件的组合 431 和弹性材料。 从图10可以看出,一些阻挡层 431 使用弯曲件 431 和其他阻挡层 431 使用弹性材料层 432 . 即弹性材料层 432 和弯曲件 431 混合形成阻挡层 431 ,从而达到堵住V型支架之间缝隙的效果 411 在软支撑结构中。 此外,当被弯曲时,阻挡层 431 可以实现良好的变形,不影响折叠机构的弯曲 40 . [0051] 当上述形成折叠机构时 40 使用,可折叠机制 40 由软支撑结构形成 41 和硬支撑结构 42 嵌入软支撑结构 41 用作连接第一壳体的组件 20 和第二个住房 30 . 如图3和图4所示,当移动终端展开时,折叠机构 40 由软支撑结构形成 41 和硬支撑结构 42 展开后变成平面结构连接到第一壳体 20 和第二个住房 30 . 如图1和图2所示,当移动终端折叠时,软支撑结构的一侧 41 远离硬支撑结构 42 向内收缩,软支撑结构的一侧 41 位于硬支撑结构上 42 也延伸和弯曲,使整个折叠机构 40 形成C型结构实现第一壳体的弯折 20 和第二个住房 30 . 在上述弯曲过程中,柔性屏由硬质支撑结构支撑,折叠机构的形状 40 根据软支撑结构的变化而变化 41 . 因此,可折叠机构之间连接的连续性 40 和第一个住房 20 和第二个住房 30 通过改进,避免了移动终端的外观结构突兀,提高了移动终端的外观效果。 [0052] 显然,本领域的技术人员可以对本发明进行各种更改和变型而不脱离本发明的精神和范围。 本发明旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN107846484A(String), CN107846484B(String), EP3352044A1(String), EP3352044A4(String), EP3352044B1(String), EP3690598A1(String), KR1020180064472A(String), KR102063283B1(String), US10310566B2(String), US20180373297A1(String), WO2018054291A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.434 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.434 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN107846484A(String), CN107846484B(String), EP3352044A1(String), EP3352044A4(String), EP3352044B1(String), EP3690598A1(String), KR1020180064472A(String), KR102063283B1(String), US10310566B2(String), US20180373297A1(String), WO2018054291A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10310566B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN107846484A(String), CN107846484B(String), EP3352044A1(String), EP3352044A4(String), EP3352044B1(String), EP3690598A1(String), KR1020180064472A(String), KR102063283B1(String), US10310566B2(String), US20180373297A1(String), WO2018054291A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.511 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), CN107846484A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), CN107846484B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), EP3352044A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), EP3352044A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), EP3352044B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), EP3690598A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), KR1020180064472A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), KR102063283B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), US10310566B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), US20180373297A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271660(Integer), WO2018054291A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10310566B2(String), US10310566B2(String), 1559577600(Integer), 271660(Integer), 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.933 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:08.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185978(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185978(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185978(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185978(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9292680B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal detection method and mobile terminal(String), 移动终端检测方法及移动终端(String), US9292680B2(String), A mobile terminal detection method and a mobile terminal. The method includes: reading a first international mobile equipment identity (IMEI) stored in a flash; comparing the first IMEI with a backup IMEI stored in a one-time programmable data (OTP) region which is prohibited from being modified; and disabling the mobile terminal when the first IMEI and the backup IMEI are inconsistent. In the present invention, the IMEI plaintext is directly backed up to the OTP region of the mobile terminal, and the value of the IMEI stored in the flash and the value of the backup IMEI are dynamically compared, so as to conveniently detect the legitimacy of the IMEI of the mobile terminal, effectively protect the IMEI number of the mobile terminal from being arbitrarily modified, and ensure the legitimate interests of users and operators.(String), 一种移动终端检测方法及移动终端。 该方法包括:读取闪存中存储的第一国际移动设备标识(IMEI); 将第一IMEI与存储在禁止修改的一次性可编程数据(OTP)区域中的备份IMEI进行比较; 当第一IMEI和备份IMEI不一致时,禁用移动终端。 本发明直接将IMEI明文备份到移动终端的OTP区域,并动态比较存储在flash中的IMEI值与备份IMEI值,方便检测合法性。 移动终端IMEI,有效保护移动终端IMEI号不被任意修改,保障用户和运营商的合法权益。(String), US14/396174(String), 1372176000(Integer), US9292680B2(String), 1458576000(Integer), 1458576000(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 26(Integer), CN100401822C | CN101719959A | CN102083055A | CN102625281A | CN102831079A | CN1722878A | KR1020090059346A | US20020120873A1 | US20020147918A1 | US20040204021A1 | US20050079868A1 | US20060236111A1 | US20070050622A1 | US20070077912A1 | US20070259683A1 | US20110003581A1 | US20110070866A1 | US20110117881A1 | US20120021805A1 | US20120157055A1 | US20130157715A1 | US20130279689A1 | US6223290B1 | US6707915B1 | US8660529B2(String), 5(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:09.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185979(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e972f3c5408d4a27afb0767e1d364fcf.png(String), 185979(Integer), e972f3c5408d4a27afb0767e1d364fcf.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.061 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal detection method and mobile terminal(String), 移动终端检测方法及移动终端(String), US9292680B2(String), A mobile terminal detection method and a mobile terminal. The method includes: reading a first international mobile equipment identity (IMEI) stored in a flash; comparing the first IMEI with a backup IMEI stored in a one-time programmable data (OTP) region which is prohibited from being modified; and disabling the mobile terminal when the first IMEI and the backup IMEI are inconsistent. In the present invention, the IMEI plaintext is directly backed up to the OTP region of the mobile terminal, and the value of the IMEI stored in the flash and the value of the backup IMEI are dynamically compared, so as to conveniently detect the legitimacy of the IMEI of the mobile terminal, effectively protect the IMEI number of the mobile terminal from being arbitrarily modified, and ensure the legitimate interests of users and operators.(String), 一种移动终端检测方法及移动终端。 该方法包括:读取闪存中存储的第一国际移动设备标识(IMEI); 将第一IMEI与存储在禁止修改的一次性可编程数据(OTP)区域中的备份IMEI进行比较; 当第一IMEI和备份IMEI不一致时,禁用移动终端。 本发明直接将IMEI明文备份到移动终端的OTP区域,并动态比较存储在flash中的IMEI值与备份IMEI值,方便检测合法性。 移动终端IMEI,有效保护移动终端IMEI号不被任意修改,保障用户和运营商的合法权益。(String), US14/396174(String), 1372176000(Integer), US9292680B2(String), 1458576000(Integer), 1458576000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 26(Integer), CN100401822C | CN101719959A | CN102083055A | CN102625281A | CN102831079A | CN1722878A | KR1020090059346A | US20020120873A1 | US20020147918A1 | US20040204021A1 | US20050079868A1 | US20060236111A1 | US20070050622A1 | US20070077912A1 | US20070259683A1 | US20110003581A1 | US20110070866A1 | US20110117881A1 | US20120021805A1 | US20120157055A1 | US20130157715A1 | US20130279689A1 | US6223290B1 | US6707915B1 | US8660529B2(String), \20230420\e972f3c5408d4a27afb0767e1d364fcf.png(String), 5(Integer), 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185979(Integer), 1. A mobile terminal detection method, comprising:powering up said mobile terminal, and reading a flag file stored in a flash;when said flag file exists, if detecting that there is an initial international mobile terminal equipment identity (IMEI) in said flag file, writing said initial IMEI into a one-time programmable data region of said mobile terminal as a backup IMEI, and deleting said flag file;when said flag file exists, if the initial IMEI is not detected in said flag file, determining that said mobile terminal is in a production phase, and normally starting up the mobile terminal;when said flag file does not exist, determining that said initial IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, giving a prompt, and performing IMEI validation by:reading a first IMEI stored in said flash;comparing said first IMEI with said backup IMEI stored in said one-time programmable data region which is prohibited from being modified, to determine whether said initial IMEI is modified;wherein if said first IMEI and said backup IMEI are inconsistent as a result of said comparing, disabling said mobile terminal, andif said first IMEI and said backup IMEI are consistent as a result of said comparing, allowing said mobile terminal to access a network.(String), 1、一种移动端检测方法,包括:为所述移动终端上电,读取存储在flash中的flag文件;当所述标志文件存在时,若检测到所述标志文件中存在初始国际移动终端设备标识(IMEI),则将所述初始IMEI写入所述移动终端的一次性可编程数据区作为备份IMEI,并删除所述初始IMEI标志文件;当所述flag文件存在时,若未在所述flag文件中检测到初始IMEI,则确定所述移动终端处于生产阶段,正常开机。当所述标志文件不存在时,确定所述初始IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并进行提示,并通过以下方式进行IMEI验证:读取存储在所述闪存中的第一IMEI;将所述第一IMEI与存储在所述不可修改的一次性可编程数据区中的所述备份IMEI进行比较,判断所述初始IMEI是否被修改;其中,如果作为所述比较的结果,所述第一IMEI和所述备份IMEI不一致,则禁用所述移动终端,以及如果所述第一IMEI和所述备份IMEI比较结果一致,则允许所述移动终端接入网络。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185979(Integer), 2. The method of claim 1,further comprises:when said flag file does not exist, determining that said IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, giving a prompt.(String), 2.如权利要求1所述的方法,还包括:当所述标志文件不存在时,确定所述IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并给出提示。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185979(Integer), 3. The method of claim 1, wherein,after said mobile terminal accesses to said network, further comprising:when said first IMEI is modified, automatically comparing said first IMEI with said backup IMEI, if they are inconsistent, disabling said mobile terminal.(String), 3.如权利要求1所述的方法,其中,所述移动终端接入所述网络后,还包括:当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185979(Integer), 4. A mobile terminal, comprising:circuitry including memory with program instructions stored therein;a writing unit stored in the memory and configured to, when powering up the mobile terminal, read a flag file stored in a flash; when said flag file exists, if an initial international mobile terminal equipment identity (IMEI) is detected in said flag file, write said initial IMEI into a one-time programmable data region of said mobile terminal as a backup IMEI, and delete said flag file; when said flag file exists, if no initial IMEI is detected in said flag file, determine that said mobile terminal is in a production phase and normally starting of the mobile terminal;a prompting module stored in the memory and configured to, when said flag file does not exist, determine that said initial IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, giving a prompt; and the mobile terminal performs IMEI validation when said flag file does not exist by:reading, by a reading unit stored in the memory, a first IMEI stored in said flash;comparing, by a checking unit stored in the memory, said first IMEI with said backup IMEI stored in said one-time programmable data region which is prevented from being modified to determine whether said initial IMEI is modified; anddisabling said mobile terminal, by a disabling unit stored in the memory, if said first IMEI and said backup IMEI are inconsistent as a result of said comparing; andallowing said mobile terminal to access a network, by an enabling unit stored in the memory, if said first IMEI and said backup IMEI are consistent as a result of said comparing.(String), 4.移动终端,包括:包括存储有程序指令的存储器的电路;写入单元,存储在存储器中,用于在移动终端上电时,读取闪存中存储的标志文件;当所述标志文件存在时,如果在所述标志文件中检测到初始国际移动终端设备标识(IMEI),则将所述初始IMEI写入所述移动终端的一次性可编程数据区作为备份IMEI,并删除所述标志文件;当存在所述flag文件时,若未在所述flag文件中检测到初始IMEI,则确定所述移动终端处于生产阶段,正常开机;提示模块,存储在存储器中,用于当所述标志文件不存在时,确定所述初始IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并进行提示。当所述标志文件不存在时,移动终端通过以下方式进行IMEI验证:存储在存储器中的读取单元读取存储在所述闪存中的第一IMEI;通过存储在存储器中的校验单元将所述第一IMEI与存储在所述一次性可编程数据区中的防止修改的所述备份IMEI进行比较,以确定所述初始IMEI是否被修改;和如果所述第一IMEI与所述备份IMEI不一致,则通过存储在内存中的禁用单元禁用所述移动终端;和如果所述第一IMEI与所述备份IMEI的比较结果一致,则通过存储在存储器中的使能单元允许所述移动终端接入网络。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185979(Integer), 5. The mobile terminal of claim 4, further comprising a flash detecting unit stored in the memory, wherein:said flash detecting unit is configured to, when said first IMEI is modified, automatically compare said first IMEI with said backup IMEI, and if they are inconsistent, disable said mobile terminal.(String), 5.如权利要求4所述的移动终端,还包括存储在存储器中的闪光检测单元,其中:所述flash检测单元用于当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.259 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.259 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185979(Integer), CROSS-REFERENCE TO RELATED APPLICATION(S) [0001]This application is the US National Phase application of PCT application number PCT/CN2013/077970 having a PCT filing date of Jun. 26, 2013, which claims priority of Chinese patent application 201210295759.8 filed on Aug. 20, 2012, the disclosures of which are hereby incorporated by reference. TECHNICAL FIELD [0002]The present document relates to the mobile terminal technology, and more particularly, to a mobile terminal detection method and a mobile terminal. BACKGROUND [0003]International Mobile Equipment Identity (IMEI) consists of 15 digits, and is commonly known as serial number and stored in an EEPROM. Each mobile terminal corresponds to a unique IMEI, and will be written with a unique IMEI when assembled and delivered from the factory. From production to delivery, the IMEI will be recorded by manufacturing vendors, and it is also the archive number and ID number of said mobile terminal at the manufacturer side. [0004]IMEI consists of TAO+FAC+SNR+SP. [0005]1, the first six digits (TAO) are the type approval number, generally representing the model, [0006]2, the following two digits (FAC) are the final assembling number, usually representing the origin, [0007]3, the following 6 digits (SNR) is a string number, generally representing the production serial number, [0008]4, the last digit (SP) is usually 0, representing the check code. [0009]In the standby screen, inputting *#06# can check the IMEI. Only a mobile terminal having an IMEI can be used in the GSM/UMTS/LTE network, and the operators can identify the device type according to the IMEI, and then provide related services, users can also make use of the IMEI to determine whether the purchased mobile terminal is an original production or not. [0010]Since the IMEI of said mobile terminal is written in a Flash that can be repeatedly read and written, it will be relatively easy to be modified by computer programs to deceive the network to obtain illegal status or function, thus the IMEI protection would be included within the requirements of the operator. [0011]The related design idea proposed aiming to the IMEI protection is to use the IMEI and the device parameters to generate the checked value with the relevant algorithm and store it in an one-time programmable (OTP) region, at each time of starting up the host, said checked value will be compared, and the usage is limited if they are different; or use an external device, and said external device encrypts the IMEI with a certain encryption algorithm to form into the ciphertext which is stored together with the decryption key in said OTP region, and accesses to the plaintext data after decrypting the ciphertext with the decryption key, and then connects with the communication terminal to verify. [0012]The abovementioned technique has the following problem: the way of protecting the IMEI is too complicated, increasing the difficulty of implementation, or it needs to use an external device to protect the IMEI, so that the mobile terminal is not convenient to use. SUMMARY [0013]To solve the technical problem, the embodiment of the present document provides a mobile terminal detection method and a mobile terminal, used to solve the shortcoming that the method for protecting the IMEI is too complex in the related art. [0014]To solve the abovementioned technical problem, the embodiment of the present document provides a mobile terminal detection method, and said method comprising: [0015]reading a first international mobile terminal equipment identity (IMEI) stored in a flash; [0016]comparing said first IMEI with a backup IMEI stored in a one-time programmable data region which is prevented from being modified; [0017]if said first IMEI and said backup IMEI are inconsistent, disabling said mobile terminal. [0018]Preferably, before reading said first IMEI stored in said flash, the method further comprises: [0019]powering up, and reading a flag file stored in said flash; [0020]when said flag file exists, if detecting there is an initial IMEI in said flag file, writing said initial IMEI into said one-time programmable data region as a backup IMEI, and deleting said flag file. [0021]Preferably, when said flag file exists, if the initial IMEI is not detected in said flag file, it is determined that said mobile terminal is in the production phase. [0022]Preferably, after reading said flag file stored in said flash, the following is further comprised: [0023]when said flag file does not exist, determining that said IMEI has been written into said one-time programmable data region of said mobile terminal as said backup IMEI, and giving a prompt. [0024]Preferably, after comparing said first IMEI with said backup IMEI stored in said one time programmable data region, the following is further comprised: [0025]if said first IMEI and said backup IMEI are consistent, allowing said mobile terminal to access to a network. [0026]Preferably, after said mobile terminal accesses to said network, the following is further comprised: [0027]when said first IMEI is modified, automatically comparing said first IMEI with said backup IMEI, if they are inconsistent, disabling said mobile terminal. [0028]To solve the abovementioned technical problem, the embodiment of the present document further provides a mobile terminal, comprising: [0029]a reading unit, which is set to read a first international mobile terminal equipment identity (IMEI) stored in a flash; [0030]a checking unit, which is set to compare said first IMEI with a backup IMEI stored in an one-time programmable data region, and said one-time programmable data region is prevented from being modified; and [0031]a disabling unit, which is set to, if said first IMEI and said backup IMEI are inconsistent, disable said mobile terminal. [0032]Preferably, said mobile terminal further comprises a writing unit, wherein: [0033]said writing unit is set to, when powering up, read a flag file stored in said flash; when said flag file exists, if an initial IMEI is detected in said flag file, write said initial IMEI into said one-time programmable data region as said backup IMEI, and delete said flag file. [0034]Preferably, said writing unit is further set to, when said flag file exists, if no initial IMEI is detected in said flag file, determine that said mobile terminal is in the production phase. [0035]Preferably, said mobile terminal further comprises a prompting module, wherein: [0036]said prompting module is set to, when said flag file does not exist, determine that said IMEI has been written into said mobile terminal, and give a prompt. [0037]Preferably, said mobile terminal further comprises an enabling unit, wherein: [0038]the checking unit comprises: [0039]a one-time programmable data region reading module for reading said backup IMEI in said one-time programmable data region; [0040]a comparing module for comparing said first IMEI with said backup IMEI; [0041]said enabling unit is set to: if said first IMEI and said backup IMEI are consistent, allow said mobile terminal to access to the network. [0042]Preferably, the abovementioned mobile terminal further comprises a flash detecting unit, wherein: [0043]said flash detecting unit is set to, when said first IMEI is modified, automatically compare said first IMEI with said backup IMEI, if they are inconsistent, disable said mobile terminal. [0044]The beneficial effects of the abovementioned technical scheme of the present document are as follows: the OTP region is prohibited from modifying the data within it, and then the backup IMEI therein may not be modified, effectively protecting the IMEI of said mobile from being modified arbitrarily, and ensuring the legitimate interests of the users and operators. BRIEF DESCRIPTION OF THE DRAWINGS [0045]FIG. 1 is a schematic diagram of a mobile terminal detection method in accordance with an embodiment of the present document; [0046]FIG. 2 a structural diagram of a mobile terminal in accordance with an embodiment of the present document. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0047]Hereinafter with reference to the accompanying drawings, the embodiments of the present document will be described in detail. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments of the present application may be arbitrarily combined with each other. [0048]The embodiments of the present document directly back up the IMEI plaintext into a one-time programmable data (OTP) region of a mobile terminal, and dynamically compare the value of the IMEI standardly stored in the flash with the value of said backup IMEI. [0049]A mobile terminal detection method according to an embodiment of the present document, as shown in FIG. 1, comprises the following steps. [0050]In step 101, read the first international mobile equipment identity (IMEI) stored in the flash; [0051]In step 102, compare said first IMEI with the backup IMEI stored in the one-time programmable (OTP) data region, and said one-time programmable data region is prohibited from being modified; [0052]In step 103, if said first IMEI and said backup IMEI are inconsistent, disable said mobile terminal. [0053]Applying the provided technical scheme, the OTP region is prohibited to modify the data within it, and then it is impossible to modify the backup IMEI therein, effectively protecting the IMEI of said mobile terminal from being arbitrarily modified, and ensuring the legitimate interests of the users and operators. [0054]Only after said mobile terminal accesses to the network can it enjoy the network services provided by the operators. [0055]In a preferred embodiment, before reading the first IMEI stored in the flash, the following is further comprised: [0056]powering up, and reading the flag file stored in the flash; [0057]when said flag file exists, reading the initial IMEI in said flag file, if detecting the initial IMEI, writing said initial IMEI into said one-time programmable data region as said backup IMEI, and deleting said flag file. [0058]If the original IMEI is not detected in said flag file, it is determined that said mobile terminal is in the production phase. [0059]In one application scenario, before reading the first IMEI stored in the flash, it further comprises the process of initializing the OTP region, comprising: [0060]step 1, power up, and read the flag file in the flash; [0061]step 2, if there is a flag file, read the IMEI in said flag file, if no IMEI is detected, consider the device in the production phase, and normally start up the mobile terminal; If the IMEI is detected, write it into the OTP region, and delete said flag file; [0062]step 3, if said flag file does not exist, enter into the normal IMEI validation phase of said mobile terminal. [0063]In said step one, said flag file exist in the Flash before writing said IMEI into said mobile terminal. [0064]In said step 2, the normal startup state is exclusively used in the research & development and production testing phases. [0065]In a preferred embodiment, reading the flag file stored in the flash further comprises: [0066]when said flag file does not exist, determining that said IMEI has been written into said mobile terminal, and giving a prompt. [0067]Whether said flag file exist or not is the unique condition to judge whether said mobile terminal is in the production phase or not, if said flag file does not exist, it represents that said IMEI has been written into said mobile terminal and backed up, thus completing the production process, and being in the user using phase. [0068]In a preferred embodiment, comparing said first IMEI with the backup IMEI stored in the one time programmable data region comprises: [0069]reading said backup IMEI in said one-time programmable data region; [0070]comparing said first IMEI with said backup IMEI. [0071]In a preferred embodiment, if said first IMEI and said backup IMEI are consistent, allow said mobile terminal to access to the network. [0072]In a preferred embodiment, after said mobile terminal accesses to the network, [0073]when said first IMEI is modified, automatically compare said first IMEI with the backup IMEI, if they are inconsistent, disable said mobile terminal. [0074]The embodiment of the present invention provides a mobile terminal, as shown in FIG. 2, comprising: [0075]reading unit 201, which is set to read the first international mobile equipment identity (IMEI) stored in the flash; [0076]detecting unit 202, which is set to compare said first IMEI with the backup IMEI stored in the one-time programmable data region, and said one-time programmable data area is prohibited from being modified; and [0077]disabling unit 203, which is set to, if said first IMEI and said backup IMEI are inconsistent, disable said mobile terminal. [0078]After using the abovementioned technical solution, directly back up said IMEI plaintext to the OTP region, protect the IMEI by dynamically comparing the value of the IMEI standardly stored in the flash with the value of the backup IMEI, so that the IMEI will not be arbitrarily rewritten, meanwhile, this function is integrated into the terminal, to achieve the dynamic self-protection of the terminal. [0079]In a preferred embodiment, said mobile terminal further comprises a writing unit, wherein: [0080]said writing unit is configured to, when powering up, read the flag file stored in the flash; if the initial IMEI is detected in said flag file, write said initial IMEI into said one-time programmable data region as said backup IMEI, delete said flag file; if the initial IMEI is not detected, determine that said mobile terminal is in the production phase. [0081]In a preferred embodiment, said mobile terminal further comprises a prompting module, wherein: [0082]said prompting module is set to, when the flag file does not exist, determine that said IMEI has been written to said mobile terminal, and give a prompt. [0083]In a preferred embodiment, said detecting unit 202 comprises: [0084]a one-time programmable read data region module, which is set to read the backup IMEI in said one-time programmable data region; and [0085]a comparing module, which is set to compare said first IMEI with said backup IMEI. [0086]In a preferred embodiment, said mobile terminal further comprises an enabling unit, wherein: [0087]said enabling unit is set to, if said first IMEI and said backup IMEI are consistent, allow said mobile terminal to access to the network. [0088]In a preferred embodiment, said mobile terminal further comprises a flash detecting unit, wherein: [0089]said flash detecting unit is set to, when said first IMEI is modified, automatically compare said first IMEI with said backup IMEI, if they are inconsistent, disable said mobile terminal. [0090]After using this scheme, the advantages are: backing up the IMEI to the OTP region, when modifying said IMEI or powering up said mobile terminal, automatically detecting whether the first IMEI currently stored in the flash and the backup IMEI are consistent or not, if they are consistent, booting the host normally, if they are inconsistent, disabling the host, so as to dynamically detect the legitimacy of the IMEI of said mobile terminal; integrating this function into the terminal can effectively protect the IMEI number of said mobile terminal from being arbitrarily modified, so as to ensure the legitimate interests of the users and operators. [0091]The above description is the preferred embodiments of the present document, and it should be noted that for a person of ordinary skill in the art, any method for protecting the IMEI backed up in the non-erasable region can also make a number of improvements and modifications without departing from the principles of the present document, and these improvements and modifications should be considered within the protection scope of the present document. [0092]Those ordinarily skilled in the art can understand that all or some of steps of the abovementioned method may be completed by the programs instructing the relevant hardware, and said programs may be stored in a computer-readable storage medium, such as read only memory, magnetic or optical disk. Alternatively, all or some of the steps of the abovementioned embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/unit in the abovementioned embodiments can be realized in the form of hardware or software function module. The present document is not limited to any specific form of hardware and software combinations. [0093]The above description is only preferred embodiments of the present document, and is not intended to limit the protection scope of the present document. According to the inventive content of the present document, there may be also a variety of other embodiments, and without departing from the spirit and essence of the document, those skilled in the field can make all kinds of corresponding changes and modifications in accordance with the present document, while within the spirit and principles of the present document, all changes, equivalent replacements and improvements should be included within the protection scope of the present document. INDUSTRIAL APPLICABILITY [0094]Compared with the relevant technology, the embodiment of the present document directly backs up the IMEI plaintext to the OTP region of the mobile terminal, and dynamically compares the value of the IMEI stored in the flash with the value of the backup IMEI, so as to conveniently detect the legitimacy of the IMEI of the mobile terminal, effectively protect the IMEI number of the mobile terminal from being modified arbitrarily, and ensure the legitimate interests of the users and operators.(String), 相关申请的交叉引用 [0001] 本申请为PCT申请号PCT/CN2013/077970的美国国家阶段申请,PCT申请日为2013年6月26日,要求2012年8月20日提交的中国专利申请201210295759.8的优先权,其公开内容为 特此通过引用并入。 技术领域 [0002] 本发明涉及移动终端技术,尤其涉及一种移动终端检测方法及移动终端。 背景 [0003] 国际移动设备识别码 (IMEI) 由 15 位数字组成,通常称为序列号,存储在 EEPROM 中。 每个移动终端对应一个唯一的 IMEI,在出厂组装和交付时都会写入一个唯一的 IMEI。 从生产到发货,IMEI都会被制造商记录下来,也是该移动终端在制造商端的存档号和ID号。 [0004] IMEI由TAO+FAC+SNR+SP组成。 [0005] 1、前六位数字(TAO)为型式批准号,一般代表型号, [0006] 2、后面的两位数(FAC)是最终的组装编号,通常代表产地, [0007] 3、后面6位数字(SNR)是一个字符串数字,一般代表生产序列号, [0008] 4、最后一位(SP)通常为0,代表校验码。 [0009] 在待机界面输入*#06#可以查看IMEI。 在GSM/UMTS/LTE网络中只能使用具有IMEI的移动终端,运营商可以根据IMEI识别设备类型,然后提供相关服务,用户也可以利用IMEI判断是否 购买的移动终端是否为原装产品。 [0010] 由于所述移动终端的IMEI是写在可反复读写的Flash中的,因此比较容易被计算机程序修改以欺骗网络获得非法状态或功能,因此IMEI保护将包含在 运营商的要求。 [0011] 针对IMEI保护提出的相关设计思路是,在主机每次开机时,利用IMEI和设备参数,通过相关算法生成校验值,并存储在一次性可编程(OTP)区域中 ,该校验值将进行比较,如果不同则限制使用; 或者使用外部设备,所述外部设备通过一定的加密算法将IMEI加密形成密文,与解密密钥一起存储在所述OTP区域中,通过解密密钥对密文进行解密后访问明文数据 ,然后连接通讯终端进行验证。 [0012] 上述技术存在以下问题:保护IMEI的方式过于复杂,增加了实施难度,或者需要使用外部设备保护IMEI,导致移动终端使用不方便。 概括 [0013] 为解决上述技术问题,本发明实施例提供了一种移动终端检测方法及移动终端,用以解决现有技术中保护IMEI的方法过于复杂的缺点。 [0014] 为解决上述技术问题,本发明实施例提供了一种移动终端检测方法,该方法包括: [0015] 读取存储在闪存中的第一国际移动终端设备标识(IMEI); [0016] 将所述第一IMEI与存储在防止被修改的一次性可编程数据区域中的备份IMEI进行比较; [0017] 如果所述第一IMEI和所述备份IMEI不一致,则禁用所述移动终端。 [0018] 优选地,在读取所述闪存中存储的所述第一IMEI之前,该方法还包括: [0019] 上电,并读取存储在所述闪存中的标志文件; [0020]当所述标志文件存在时,若检测到所述标志文件中存在初始IMEI,则将所述初始IMEI写入所述一次性可编程数据区作为备份IMEI,并删除所述标志文件。 [0021] 优选地,当所述标志文件存在时,如果在所述标志文件中未检测到初始IMEI,则确定所述移动终端处于生产阶段。 [0022] 优选地,在读取存储在所述flash中的所述标志文件之后,还包括: [0023] 当所述标志文件不存在时,确定所述IMEI已作为所述备份IMEI写入所述移动终端的所述一次性可编程数据区,并进行提示。 [0024] 优选地,在将所述第一IMEI与所述一次性可编程数据区域中存储的所述备份IMEI进行比较之后,还包括: [0025] 如果所述第一IMEI和所述备份IMEI一致,则允许所述移动终端接入网络。 [0026] 优选地,所述移动终端接入所述网络后,还包括: [0027] 当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0028] 为解决上述技术问题,本发明实施例还提供了一种移动终端,包括: [0029] 读取单元,用于读取闪存中存储的第一国际移动终端设备识别码(IMEI); [0030] 检查单元,用于将所述第一IMEI与存储在一次性可编程数据区域中的备份IMEI进行比较,防止所述一次性可编程数据区域被修改。 和 [0031] 禁用单元,用于当所述第一IMEI和所述备用IMEI不一致时,禁用所述移动终端。 [0032] 优选地,所述移动终端还包括写入单元,其中: [0033] 所述写入单元设置为在上电时读取存储在所述flash中的标志文件。 当所述标志文件存在时,若在所述标志文件中检测到初始IMEI,则将所述初始IMEI写入所述一次性可编程数据区作为所述备份IMEI,并删除所述标志文件。 [0034] 优选地,所述写入单元还设置为,当所述标志文件存在时,如果在所述标志文件中没有检测到初始IMEI,则确定所述移动终端处于生产阶段。 [0035] 优选地,所述移动终端还包括提示模块,其中: [0036] 所述提示模块,用于当所述标志文件不存在时,确定所述IMEI已写入所述移动终端,并进行提示。 [0037] 优选地,所述移动终端还包括使能单元,其中: [0038] 检查单元包括: [0039] 一次性可编程数据区读取模块,用于读取所述一次性可编程数据区中的备份IMEI; [0040] 比较模块,用于将所述第一IMEI与所述备用IMEI进行比较; [0041] 所述启用单元设置为:若所述第一IMEI和所述备用IMEI一致,则允许所述移动终端接入网络。 [0042] 优选地,上述移动终端还包括闪光检测单元,其中: [0043] 所述闪现检测单元设置为,当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0044] 本发明上述技术方案的有益效果是:禁止OTP区域修改其中的数据,从而不修改其中的备份IMEI,有效保护了所述手机的IMEI不被任意修改。 ,并确保用户和经营者的合法利益。 附图的简要说明 [0045] 图1为本发明实施例提供的一种移动终端检测方法示意图; [0046]图2为本发明实施例提供的一种移动终端的结构示意图。 本发明的优选实施方案 [0047] 下面结合附图对本发明实施例进行详细说明。 需要说明的是,在不冲突的情况下,本申请实施例中的实施例和特征可以任意组合。 [0048] 本发明实施例直接将IMEI明文备份到移动终端的一次性可编程数据(OTP)区域,并动态比较标准存储在flash中的IMEI值与备份IMEI值。 [0049] 本发明实施例提供的一种移动终端检测方法,如图1所示,包括以下步骤。 [0050] 在步骤 101 ,读取存储在闪存中的第一个国际移动设备标识(IMEI); [0051] 在步骤 102 ,将所述第一IMEI与所述一次性可编程(OTP)数据区中存储的备份IMEI进行比较,禁止修改所述一次性可编程数据区; [0052] 在步骤 103 ,如果所述第一IMEI和所述备份IMEI不一致,则禁用所述移动终端。 [0053] 应用所提供的技术方案,OTP区域内的数据被禁止修改,从而无法修改其中的备份IMEI,有效保护了移动终端的IMEI不被任意修改,保障了用户的合法权益。 用户和运营商。 [0054] 该移动终端只有接入网络后才能享受运营商提供的网络服务。 [0055] 在一个优选实施例中,在读取闪存中存储的第一IMEI之前,还包括: [0056] 上电,读取存储在flash中的flag文件; [0057] 当所述标志文件存在时,读取所述标志文件中的初始IMEI,若检测到所述初始IMEI,将所述初始IMEI写入所述一次性可编程数据区作为所述备份IMEI,并删除所述标志文件。 [0058] 如果在所述标志文件中未检测到原始IMEI,则确定所述移动终端处于生产阶段。 [0059] 在一种应用场景中,在读取存储在flash中的第一个IMEI之前,还包括初始化OTP区域的过程,包括: [0060] step 1,上电,读取flash中的flag文件; [0061] 步骤2,如果有标志文件,则读取该标志文件中的IMEI,如果没有检测到IMEI,则认为设备处于生产阶段,正常启动移动终端。 如果检测到IMEI,则将其写入OTP区域,并删除该标志文件; [0062] 步骤3,如果所述标志文件不存在,则进入所述移动终端的正常IMEI验证阶段。 [0063] 所述步骤一中,在将所述IMEI写入所述移动终端之前,所述标志文件存在于Flash中。 [0064] 所述步骤2中,正常启动状态专门用于研发和生产测试阶段。 [0065] 在一个优选实施例中,读取闪存中存储的标志文件还包括: [0066] 当所述标志文件不存在时,确定所述IMEI已写入所述移动终端,并进行提示。 [0067] 所述标志文件是否存在是判断所述移动终端是否处于生产阶段的唯一条件,如果所述标志文件不存在,则表示所述IMEI已写入所述移动终端并备份,因此 完成生产过程,进入用户使用阶段。 [0068] 在优选实施例中,将所述第一IMEI与存储在一次性可编程数据区域中的备份IMEI进行比较包括: [0069] 读取所述一次性可编程数据区域中的所述备份IMEI; [0070] 将所述第一IMEI与所述备用IMEI进行比较。 [0071]在一个优选实施例中,如果所述第一IMEI和所述备用IMEI一致,则允许所述移动终端接入网络。 [0072] 在一个优选实施例中,所述移动终端接入网络后, [0073] 当所述第一IMEI被修改时,自动将所述第一IMEI与备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0074] 本发明实施例提供一种移动终端,如图2所示,包括: [0075] 阅读单元 201 ,设置为读取存储在闪存中的第一个国际移动设备标识(IMEI); [0076] 检测单元 202 ,设置为将所述第一IMEI与存储在所述一次性可编程数据区中的备份IMEI进行比较,并禁止修改所述一次性可编程数据区; 和 [0077] 禁用单元 203 ,设置为如果所述第一IMEI和所述备用IMEI不一致,则禁用所述移动终端。 [0078] 使用上述技术方案后,直接将所述IMEI明文备份到OTP区域,通过动态比较标准存储在flash中的IMEI值与备份IMEI值来保护IMEI,使IMEI不会被任意篡改 重写,同时将该功能集成到终端中,实现终端的动态自我保护。 [0079] 在一个优选实施例中,所述移动终端还包括写入单元,其中: [0080] 所述写入单元,用于在上电时读取闪存中存储的标志文件; 如果在所述标志文件中检测到初始IMEI,将所述初始IMEI写入所述一次性可编程数据区作为所述备份IMEI,删除所述标志文件; 如果未检测到初始IMEI,则确定所述移动终端处于生产阶段。 [0081] 在一个优选实施例中,所述移动终端还包括提示模块,其中: [0082] 所述提示模块设置为当标志文件不存在时,确定所述IMEI已写入所述移动终端,并进行提示。 [0083] 在一个优选实施例中,所述检测单元 202 包含: [0084] 一次性可编程读取数据区模块,用于读取所述一次性可编程数据区中的备份IMEI; 和 [0085] 比较模块,用于将所述第一IMEI与所述备用IMEI进行比较。 [0086] 在一个优选实施例中,所述移动终端还包括使能单元,其中: [0087] 所述启动单元设置为,如果所述第一IMEI和所述备用IMEI一致,则允许所述移动终端接入网络。 [0088] 在一个优选实施例中,所述移动终端还包括闪光检测单元,其中: [0089] 所述闪现检测单元设置为,当所述第一IMEI被修改时,自动将所述第一IMEI与所述备份IMEI进行比较,如果不一致,则禁用所述移动终端。 [0090] 使用该方案后的优点是:将IMEI备份到OTP区域,在修改IMEI或给移动终端上电时,自动检测当前存储在flash中的第一个IMEI与备份的IMEI是否一致,如果 一致,正常启动主机,如果不一致,关闭主机,动态检测所述移动终端IMEI的合法性。 将该功能集成到终端中,可以有效保护该移动终端的IMEI号不被任意修改,保障用户和运营商的合法权益。 [0091] 以上所述为本文档的较佳实施例,需要说明的是,对于本领域的普通技术人员来说,任何保护不可擦除区域备份的IMEI的方法都可以做很多改进和改进。 在不脱离本文件原则的情况下进行修改,这些改进和修改应视为在本文件的保护范围之内。 [0092]本领域普通技术人员可以理解,上述方法的全部或部分步骤可以通过程序指令相关硬件来完成,所述程序可以存储在计算机可读存储介质中,例如只读存储器、磁 或光盘。 或者,上述实施例的全部或部分步骤也可以通过一个或多个集成电路来实现。 因此,上述实施例中的各个模块/单元可以采用硬件或软件功能模块的形式来实现。 本文档不限于任何特定形式的硬件和软件组合。 [0093] 以上所述,仅为本发明的较佳实施例而已,并不用于限定本发明的保护范围。 根据本发明的发明内容,还可以有多种其他的实施例,在不脱离本发明的精神和实质的前提下,本领域技术人员可以根据本发明进行各种相应的改动和变型。 本文件,在本文件的精神和原则之内,一切改动、等同替换、改进等,均应包含在本文件的保护范围之内。 工业适用性 [0094] 与相关技术相比,本文档实施例直接将IMEI明文备份到移动终端的OTP区域,并动态比较存储在flash中的IMEI值与备份IMEI值,从而 方便检测移动终端IMEI的合法性,有效保护移动终端IMEI号不被任意修改,保障用户和运营商的合法权益。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2013270195A1(String), AU2013270195B2(String), CN102831079A(String), CN102831079B(String), EP2829978A1(String), EP2829978A4(String), EP2829978B1(String), RU2014141581A(String), RU2601841C2(String), US20150067780A1(String), US9292680B2(String), WO2013178117A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.476 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2013270195A1(String), AU2013270195B2(String), CN102831079A(String), CN102831079B(String), EP2829978A1(String), EP2829978A4(String), EP2829978B1(String), RU2014141581A(String), RU2601841C2(String), US20150067780A1(String), US9292680B2(String), WO2013178117A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9292680B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2013270195A1(String), AU2013270195B2(String), CN102831079A(String), CN102831079B(String), EP2829978A1(String), EP2829978A4(String), EP2829978B1(String), RU2014141581A(String), RU2601841C2(String), US20150067780A1(String), US9292680B2(String), WO2013178117A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.548 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), AU2013270195A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), AU2013270195B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), CN102831079A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), CN102831079B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), EP2829978A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), EP2829978A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), EP2829978B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), RU2014141581A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), RU2601841C2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), US20150067780A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), US9292680B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271661(Integer), WO2013178117A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:10.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9292680B2(String), US9292680B2(String), 1458576000(Integer), 271661(Integer), 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.002 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185979(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185979(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.183 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185979(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185979(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.308 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7720717B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal device, mobile terminal method, mobile terminal program, and electronic money server(String), 移动终端装置、移动终端方法、移动终端程序以及电子货币服务器(String), US7720717B2(String), A mobile terminal device has an information processing unit that processes electronic money information and a storage unit that stores the electronic money information. A receiving unit receives from an electronic money server an electronic money identification (ID), a mobile terminal identification (ID) identifying the mobile terminal device, and a money information processing program for enabling the information processing unit to execute processing of the money information stored in the storage unit. An installation unit installs into the storage unit the money information processing program and the IDs received by the receiving unit. A sending unit sends to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information being sent to the electronic server before the receiving unit receives the money information processing and the IDs.(String), 移动终端设备具有处理电子货币信息的信息处理单元和存储电子货币信息的存储单元。 接收部从电子货币服务器接收电子货币识别码(ID)、识别移动终端装置的移动终端识别码(ID)、以及用于使信息处理部执行所存储的货币信息的处理的货币信息处理程序。 在存储单元中。 安装单元将货币信息处理程序和接收单元接收到的ID安装到存储单元中。 发送单元向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息,该必要信息在接收单元接收货币信息处理和ID之前被发送至电子服务器。(String), US10/547977(String), 1078416000(Integer), US7720717B2(String), 1274112000(Integer), 1274112000(Integer), 美国(String), 4(Integer), JP(String), 13(Integer), 27(Integer), EP0950968A1 | EP1221669A1 | JP2000112719A | JP2000259148A | JP2001291032A | JP2002004886A | JP2002042216A | JP2002073973A | JP2002135424A | JP2002329053A | JP2002352173A | JP2003016041A | JP2003022483A | JP2004102698A | US20010034725A1 | US20020049662A1 | US20020052838A1 | US20020064074A1 | US20060136548A1 | US5796832A | US6198915B1 | US6282656B1 | US6321078B1 | US6434403B1 | WO1996025828A1 | WO1997045814A1 | WO2002048869A1(String), 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:11.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185980(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\55c65817c35d4cf8800822dfbe046c52.png(String), 185980(Integer), 55c65817c35d4cf8800822dfbe046c52.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.125 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal device, mobile terminal method, mobile terminal program, and electronic money server(String), 移动终端装置、移动终端方法、移动终端程序以及电子货币服务器(String), US7720717B2(String), A mobile terminal device has an information processing unit that processes electronic money information and a storage unit that stores the electronic money information. A receiving unit receives from an electronic money server an electronic money identification (ID), a mobile terminal identification (ID) identifying the mobile terminal device, and a money information processing program for enabling the information processing unit to execute processing of the money information stored in the storage unit. An installation unit installs into the storage unit the money information processing program and the IDs received by the receiving unit. A sending unit sends to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information being sent to the electronic server before the receiving unit receives the money information processing and the IDs.(String), 移动终端设备具有处理电子货币信息的信息处理单元和存储电子货币信息的存储单元。 接收部从电子货币服务器接收电子货币识别码(ID)、识别移动终端装置的移动终端识别码(ID)、以及用于使信息处理部执行所存储的货币信息的处理的货币信息处理程序。 在存储单元中。 安装单元将货币信息处理程序和接收单元接收到的ID安装到存储单元中。 发送单元向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息,该必要信息在接收单元接收货币信息处理和ID之前被发送至电子服务器。(String), US10/547977(String), 1078416000(Integer), US7720717B2(String), 1274112000(Integer), 1274112000(Integer), 美国(String), 2(Integer), 4(Integer), JP(String), 13(Integer), 27(Integer), EP0950968A1 | EP1221669A1 | JP2000112719A | JP2000259148A | JP2001291032A | JP2002004886A | JP2002042216A | JP2002073973A | JP2002135424A | JP2002329053A | JP2002352173A | JP2003016041A | JP2003022483A | JP2004102698A | US20010034725A1 | US20020049662A1 | US20020052838A1 | US20020064074A1 | US20060136548A1 | US5796832A | US6198915B1 | US6282656B1 | US6321078B1 | US6434403B1 | WO1996025828A1 | WO1997045814A1 | WO2002048869A1(String), \20230420\55c65817c35d4cf8800822dfbe046c52.png(String), 25(Integer), 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 1. A mobile terminal device having an Internet access function for access to the Internet to communicate the mobile terminal device with an electronic money server providing electronic money service, the mobile terminal device comprising:information processing means for processing electronic information including money information;storing means for storing the electronic information including the money information;receiving means for receiving from the electronic money server secret information and an electronic money identification (ID);means for downloading from the electronic money server a money information processing program using the received secret information and electronic money ID for enabling the information processing means to execute processing of the money information stored in the storing means;installing means for installing into the storing means the money information processing program downloaded from the electronic money server and the electronic money ID and the secret information received by the receiving means while the mobile terminal device communicates only with the electronic money server;sending means for sending to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information corresponding to the electronic money ID and being sent to the electronic server by the sending means before the money information processing program is downloaded from the electronic money server and the receiving means receives the electronic money ID and the secret information from the electronic money server; anda log data storing unit for storing a history of electronic information processed by the information processing means;wherein while the mobile terminal device communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing means to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stared by the storing means by using the secret information installed in the storing means, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing means and stored in the log data storing unit;wherein the installing means generates the log data storing unit in the storing means when the installing means installs into the storing means the money information processing program, the electronic money ID, and the secret information;wherein the information processing means and the storing means comprise at least one IC chip;wherein the necessary information sent by the sending means to the electronic money server comprises information identifying the IC chip; andwherein the receiving means receives the electronic money ID from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 1.移动终端设备有互联网访问功能,用于访问互联网以将移动终端设备与提供电子货币服务的电子货币服务器进行通信,该移动终端设备包括:用于处理包括货币信息在内的电子信息的信息处理装置;用于存储包括货币信息的电子信息的存储装置;用于从电子货币服务器接收秘密信息和电子货币标识(ID)的接收装置;用于从电子货币服务器下载货币信息处理程序的装置,该货币信息处理程序使用接收到的秘密信息和电子货币ID,使得信息处理装置能够执行存储在存储装置中的货币信息的处理;在移动终端装置仅与电子货币服务器进行通信的状态下,将从电子货币服务器下载的货币信息处理程序和接收装置接收到的电子货币ID及秘密信息安装到存储装置的安装单元。发送装置,用于向电子货币服务器发送使电子货币服务器能够提供电子货币服务所必需的信息,该必要信息对应于电子货币ID并且在货币信息处理程序被执行之前由发送装置发送至电子服务器。从电子货币服务器下载,接收装置从电子货币服务器接收电子货币ID和秘密信息;和日志数据存储单元,用于存储由信息处理装置处理的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理装置执行用于接收来自电子货币服务器或电子终端设备的信息的金额信息接收功能。通过使用安装在存储装置中的秘密信息,对应于与由存储装置启动的货币信息相对应的货币量的变化,执行货币信息处理功能,用于根据接收到的相应信息改变货币量对于金额的变化,执行历史信息记录功能,用于记录由信息处理装置处理并存储在日志数据存储单元中的电子信息的历史;其中,当安装装置将货币信息处理程序、电子货币ID和秘密信息安装到存储装置中时,安装装置在存储装置中生成日志数据存储单元;其中,信息处理装置和存储装置包括至少一个IC芯片;其中,发送装置向电子货币服务器发送的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,接收装置从电子货币服务器接收电子货币ID。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 2. A mobile terminal device according to claim 1; wherein the secret information comprises identification information that enables the mobile terminal device to be identified by the electronic terminal device or the electronic money server.(String), 2.如权利要求1所述的移动终端设备;其中秘密信息包括使移动终端设备能够被电子终端设备或电子货币服务器识别的标识信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 3. A mobile terminal device according to claim 1; further comprising display means for displaying the electronic money ID received by the receiving means and installed by the installing means.(String), 3.根据权利要求1所述的移动终端设备;还包括显示装置,用于显示由接收装置接收并由安装装置安装的电子货币ID。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 4. A mobile terminal device according to claim 2; further comprising display means for displaying the electronic money ID received by the receiving means and installed by the installing means.(String), 4.如权利要求2所述的移动终端设备;还包括显示装置,用于显示由接收装置接收并由安装装置安装的电子货币ID。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 5. A mobile terminal device according to claim 3; wherein the money information processing program enables the information processing means to send to the electronic terminal device the electronic money ID in response to receipt of the information corresponding to a change in the amount of money from the electronic terminal device when the information processing means performs the money-amount information receiving function.(String), 5.根据权利要求3所述的移动终端设备;其中货币信息处理程序使信息处理装置能够响应于在信息处理装置执行货币时从电子终端设备接收到对应于货币量的变化的信息而向电子终端设备发送电子货币ID-金额信息接收功能。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 6. A mobile terminal device according to claim 4; wherein the money information processing program enables the information processing means to send to the electronic terminal device the electronic money ID in response to receipt of the information corresponding to a change in the amount of money from the electronic terminal device when the information processing means performs the money-amount information receiving function.(String), 6.如权利要求4所述的移动终端设备;其中货币信息处理程序使信息处理装置能够响应于在信息处理装置执行货币时从电子终端设备接收到对应于货币量的变化的信息而向电子终端设备发送电子货币ID-金额信息接收功能。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 7. An electronic money server for providing electronic money service using the mobile terminal device according to claim 1, the electronic money server comprising:connecting means for enabling Internet connection of the electronic money server to the mobile terminal device via the Internet access function of the mobile terminal device; andsending means for sending the secret information, the money information processing program, and the electronic money ID to the receiving means of the mobile terminal device when the electronic money server and the mobile terminal device are connected via the Internet.(String), 7.一种电子货币服务器,使用权利要求1所述的移动终端装置提供电子货币服务,该电子货币服务器包括:用于通过移动终端设备的互联网访问功能实现电子货币服务器与移动终端设备的互联网连接的连接装置;和发送装置,当电子货币服务器和移动终端设备通过因特网连接时,将秘密信息、货币信息处理程序和电子货币ID发送到移动终端设备的接收装置。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 8. A method executed by a computer for performing communication between a mobile terminal device according to claim 1 and an electronic money server for providing electronic money service using the mobile terminal device, comprising:enabling Internet connection of the electronic money server to the mobile terminal device via the Internet access function of the mobile terminal device; andsending the secret information, the money information processing program, and the electronic money ID to the receiving means of the mobile terminal device when the electronic money server and the mobile terminal device are connected via the Internet.(String), 8.一种由计算机执行的方法,用于在根据权利要求1所述的移动终端设备和使用该移动终端设备提供电子货币服务的电子货币服务器之间进行通信,包括:通过移动终端设备的互联网接入功能,使电子货币服务器能够与移动终端设备进行互联网连接;和当电子货币服务器和移动终端设备通过因特网连接时,将秘密信息、货币信息处理程序和电子货币ID发送到移动终端设备的接收装置。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 9. A mobile terminal device according to claim 1; wherein the mobile terminal device comprises a cellular mobile telephone having mobile phone functions.(String), 9.根据权利要求1所述的移动终端设备;其中移动终端设备包括具有手机功能的蜂窝移动电话。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 10. A mobile terminal device according to claim 1; wherein the mobile terminal device comprises one of a wireless communications device, a wirelessly-equipped personal digital assistant (PDA), and a portable computer.(String), 10.根据权利要求1所述的移动终端设备;其中移动终端设备包括无线通信设备、配备无线的个人数字助理(PDA)和便携式计算机之一。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 11. A mobile terminal device according to claim 1; wherein the sending means includes means for sending to the electronic money server user identification information for identifying a user of the mobile terminal device.(String), 11.根据权利要求1所述的移动终端设备;其中发送装置包括用于向电子货币服务器发送用于识别移动终端设备的用户的用户识别信息的装置。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 12. A mobile terminal device according to claim 11; wherein the user identification information comprises the information identifying the IC chip.(String), 12.根据权利要求11所述的移动终端设备;其中用户识别信息包括识别IC芯片的信息。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 13. A mobile terminal device according to claim 11; wherein the user identification information comprises the electronic money ID.(String), 13.根据权利要求11所述的移动终端设备;其中用户识别信息包括电子货币ID。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 14. A mobile terminal device according to claim 1; wherein the installing means installs the secret information, money information processing program, and electronic money ID using the secret information.(String), 14.根据权利要求1所述的移动终端设备;其中安装装置安装秘密信息、货币信息处理程序和使用秘密信息的电子货币ID。15、一种电脑执行的移动端方法有用于处理电子信息的信息处理设备,用于存储电子信息的存储设备,以及用于访问因特网以将移动终端设备与提供电子货币服务的电子货币服务器进行通信的因特网访问功能,该移动终端方法包括:向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息;在向电子货币服务器发送必要信息后,从电子货币服务器接收保密信息和与必要信息对应的电子货币标识(ID);使用接收到的秘密信息和电子货币ID,从电子货币服务器下载货币信息处理程序,以使信息处理装置能够执行存储在存储装置中的货币信息的处理;在移动终端设备与电子货币服务器通信的同时将从电子货币服务器下载的货币信息处理程序和从电子货币服务器接收的电子货币ID和秘密信息安装到存储装置中;和在存储装置中生成日志数据存储单元,用于存储信息处理处理过的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理设备执行用于接收来自电子货币服务器或电子终端设备的信息的金额信息接收功能。通过使用存储设备中安装的秘密信息,对应于存储设备存储的与货币信息相对应的货币数量的变化,执行货币信息处理功能,用于根据接收到的相应信息改变货币数量对于金额的变化,执行历史信息记录功能,用于记录由信息处理设备处理并存储在日志数据存储单元中的电子信息的历史;其中,当货币信息处理程序、电子货币ID和秘密信息被安装到存储设备中时,在存储设备中生成日志数据存储单元;其中,信息处理装置和存储装置包括至少一个IC芯片;其中,发送给电子货币服务器的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,从电子货币服务器接收电子货币ID。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 15. A mobile terminal method executed by a computer having an information processing device for processing electronic information, a storage device for storing the electronic information, and an Internet access function for access to the Internet to communicate a mobile terminal device with an electronic money server providing electronic money service, the mobile terminal method comprising:sending to the electronic money server information necessary for enabling the electronic money server to provide electronic money service;receiving from the electronic money server, after the necessary information is sent to the electronic money server, secret information and an electronic money identification (ID) corresponding to the necessary information;downloading from the electronic money server a money information processing program using the received secret information and electronic money ID for enabling the information processing device to execute processing of money information stored in the storing device;installing into the storage device the money information processing program downloaded from the electronic money server and the electronic money ID and the secret information received from the electronic money server while the mobile terminal device communicates with the electronic money server; andgenerating a log data storing unit in the storage device for storing a history of electronic information processed by the information processing;wherein while the mobile terminal device communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing device to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stored by the storage device by using the secret information installed in the storage device, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing device and stored in the log data storing unit;wherein the log data storing unit is generated in the storage device when the money information processing program, the electronic money ID, and the secret information are installed into the storage device;wherein the information processing device and the storage device comprise at least one IC chip;wherein the necessary information sent to the electronic money server comprises information identifying the IC chip; andwherein the electronic money ID is received from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 16.计算机程序产品包含一种计算机可读介质,具有用于使用计算机执行移动终端方法的指令,所述计算机具有用于处理电子信息的信息处理装置、用于存储电子信息的存储装置和用于访问因特网以通信的因特网访问功能具有提供电子货币服务的电子货币服务器的移动终端设备,指令使计算机:向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息;在向电子货币服务器发送必要信息后,从电子货币服务器接收保密信息和与必要信息对应的电子货币标识(ID);使用接收到的秘密信息和电子货币(ID)从电子货币服务器下载货币信息处理程序,以使信息处理装置能够执行存储在存储装置中的货币信息的处理;在移动终端装置仅与电子货币服务器通信的状态下,将从电子货币服务器下载的货币信息处理程序和从电子货币服务器接收的电子货币ID和秘密信息安装到存储装置中。和在存储装置中生成日志数据存储单元,用于存储信息处理装置处理过的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理设备执行用于接收来自电子货币服务器或电子终端设备的信息的金额信息接收功能。通过使用存储设备中安装的秘密信息,对应于存储设备存储的与货币信息相对应的货币数量的变化,执行货币信息处理功能,用于根据接收到的相应信息改变货币数量对于金额的变化,执行历史信息记录功能,用于记录由信息处理设备处理并存储在日志数据存储单元中的电子信息的历史;其中,当货币信息处理程序、电子货币ID和秘密信息被安装到存储设备中时,在存储设备中生成日志数据存储单元;其中,信息处理装置和存储装置包括至少一个IC芯片;其中,发送给电子货币服务器的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,从电子货币服务器接收电子货币ID。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 16. A computer program product including a computer readable medium having instructions for causing the execution of a mobile terminal method using a computer having an information processing device for processing electronic information, a storage device for storing the electronic information, and an Internet access function for access to the Internet to communicate a mobile terminal device with an electronic money server providing electronic money service, the instructions causing the computer to:send to the electronic money server information necessary for enabling the electronic money server to provide electronic money service;receive from the electronic money server, after the necessary information is sent to the electronic money server, secret information and an electronic money identification (ID) corresponding to the necessary information;download from the electronic money server a money information processing program using the received secret information and electronic money (ID) for enabling the information processing device to execute processing of money information stored in the storing device;install into the storage device the money information processing program downloaded from the electronic money server and the electronic money ID and the secret information received from the electronic money server while the mobile terminal device communicates only with the electronic money server; andgenerate a log data storing unit in the storage device for storing a history of electronic information processed by the information processing device;wherein while the mobile terminal device communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing device to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stored by the storage device by using the secret information installed in the storage device, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing device and stored in the log data storing unit;wherein the log data storing unit is generated in the storage device when the money information processing program, the electronic money ID, and the secret information are installed into the storage device;wherein the information processing device and the storage device comprise at least one IC chip;wherein the necessary information sent to the electronic money server comprises information identifying the IC chip; andwherein the electronic money ID is received from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 17.一种通过因特网连接与提供电子货币服务的电子货币服务器进行通信的移动终端设备,该移动终端设备包括:处理电子货币信息的信息处理单元;存储电子货币信息的存储单元;接收单元从电子货币服务器接收电子货币标识(ID)和标识移动终端设备的移动终端标识(ID);下载单元使用电子货币ID和移动终端ID从电子货币服务器下载货币信息处理程序,使得信息处理单元能够执行存储在存储单元中的货币信息的处理;安装部,在便携终端装置仅与电子货币服务器进行通信的状态下,将下载部下载的货币信息处理程序和接收部接收到的电子货币ID以及便携终端ID安装到存储部。发送单元向电子货币服务器发送使电子货币服务器能够提供电子货币服务所需的信息,该必要信息在下载单元下载货币信息处理程序之前被发送至电子服务器并且接收单元接收电子货币ID和移动终端ID;和日志数据存储单元,用于存储由信息处理单元处理的电子信息的历史;其中,当移动终端设备与电子货币服务器或电子终端设备通信时,货币信息处理程序使信息处理单元执行用于从电子货币服务器或电子终端设备接收信息的金额信息接收功能通过使用安装在存储单元中的移动终端ID,对应于存储单元存储的货币信息对应的货币数量的变化,以执行用于根据接收到的信息改变货币数量的货币信息处理功能对应于金额的变化,执行历史信息记录功能,用于记录信息处理单元处理并存储在日志数据存储单元中的电子信息的历史;其中,当安装单元将货币信息处理程序、电子货币ID和移动终端ID安装到存储单元时,安装单元在存储单元中生成日志数据存储单元;其中,信息单元和存储单元包括至少一IC芯片。其中,发送单元向电子货币服务器发送的必要信息包括识别IC芯片的信息;和其中,在电子货币服务器接收到识别IC芯片的信息之后,接收单元从电子货币服务器接收电子货币ID。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 17. A mobile terminal device for communication via an Internet connection to an electronic money server providing electronic money service, the mobile terminal device comprising:an information processing unit that processes electronic money information;a storage unit that stores the electronic money information;a receiving unit that receives from the electronic money server an electronic money identification (ID) and a mobile terminal identification (ID) identifying the mobile terminal device;a downloading unit that downloads from the electronic money server a money information processing program using the electronic money ID and the mobile terminal ID for enabling the information processing unit to execute processing of the money information stored in the storage unit;an installation unit that installs into the storage unit the money information processing program downloaded by the downloading unit and the electronic money ID and the mobile terminal ID received by the receiving unit while the mobile terminal device communicates only with the electronic money server;a sending unit that sends to the electronic money server information necessary for enabling the electronic money server to provide electronic money service, the necessary information being sent to the electronic server before the downloading unit downloads the money information processing program and the receiving unit receives electronic money ID and the mobile terminal ID; anda log data storing unit for storing a history of electronic information processed by the information processing unit;wherein while the mobile terminal device Communicates with the electronic money server or an electronic terminal device, the money information processing program enables the information processing unit to perform a money-amount information receiving function for receiving from the electronic money server or the electronic terminal device information corresponding to a change in an amount of money corresponding to the money information stored by the storage unit by using the mobile terminal ID installed in the storage unit, to perform a money information processing function for changing the amount of money in accordance with the received information corresponding to the change in the amount of money, and to perform a history information recording function for recording the history of electronic information processed by the information processing unit and stored in the log data storing unit;wherein the installation unit generates the log data storing unit in the storage unit when the installation unit installs into the storage unit the money information processing program, the electronic money ID, and the mobile terminal ID;wherein the information unit and the storage unit comprise at least one IC chip;wherein the necessary information sent by the sending unit to the electronic money server comprises information identifying the IC chip; andwherein the receiving unit receives the electronic money ID from the electronic money server after the electronic money server receives the information identifying the IC chip.(String), 18.根据权利要求17所述的移动终端设备;其中移动终端设备包括具有手机功能的蜂窝移动电话。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 18. A mobile terminal device according to claim 17; wherein the mobile terminal device comprises a cellular mobile telephone having mobile phone functions.(String), 19.根据权利要求17所述的移动终端设备;其中移动终端设备包括无线通信设备、配备无线的个人数字助理(PDA)和便携式计算机之一。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 19. A mobile terminal device according to claim 17; wherein the mobile terminal device comprises one of a wireless communications device, a wirelessly-equipped personal digital assistant (PDA), and a portable computer.(String), 20.根据权利要求17所述的移动终端设备;其中信息处理单元与储存单元包括至少一IC芯片。其中,移动终端ID包括识别IC芯片的信息。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 20. A mobile terminal device according to claim 17; wherein the information processing unit and the storage unit comprise at least one IC chip; and wherein the mobile terminal ID comprises information identifying the IC chip.(String), 21.根据权利要求20所述的移动终端设备;其中发送单元向电子货币服务器发送用于识别移动终端设备的用户的用户识别信息。(String), 1(Integer), 19(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 21. A mobile terminal device according to claim 20; wherein the sending unit sends to the electronic money server user identification information for identifying a user of the mobile terminal device.(String), 22.根据权利要求21所述的移动终端设备;其中用户识别信息包括识别IC芯片的信息。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 22. A mobile terminal device according to claim 21; wherein the user identification information comprises the information identifying the IC chip.(String), 23.根据权利要求21所述的移动终端设备;其中用户识别信息包括电子货币ID。(String), 1(Integer), 21(Integer), 20(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 23. A mobile terminal device according to claim 21; wherein the user identification information comprises the electronic money ID.(String), 24.根据权利要求17所述的移动终端设备;其中安装单元使用移动终端ID安装货币信息处理程序和电子货币ID。(String), 1(Integer), 22(Integer), 20(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 24. A mobile terminal device according to claim 17; wherein the installing unit installs the money information processing program and the electronic money ID using the mobile terminal ID.(String), 25.一种电子货币服务器,用于使用根据权利要求17所述的移动终端设备提供电子货币服务,该电子货币服务器包括:使电子货币服务器能够与移动终端设备进行因特网连接的连接装置;和发送单元,在电子货币服务器与移动终端装置经由因特网连接时,将移动终端ID、货币信息处理程序、电子货币ID发送到移动终端装置的接收部。(String), 1(Integer), 23(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185980(Integer), 25. An electronic money server for providing electronic money service using the mobile terminal device according to claim 17, the electronic money server comprising:connecting means for enabling Internet connection of the electronic money server to the mobile terminal device; andsending means for sending the mobile terminal ID, the money information processing program, and the electronic money ID to the receiving unit of the mobile terminal device when the electronic money server and the mobile terminal device are connected via the Internet.(String), 1(Integer), 24(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185980(Integer), CROSS REFERENCE TO RELATED APPLICATIONS [0001]This application is a U.S. national stage application of copending International Application No. PCT/JP2004/002862, filed Mar. 5, 2004, claiming a priority date of Mar. 7, 2003, and published in a non-English language. TECHNICAL FIELD [0002]The present invention relates to a mobile phone device, and more particularly, to a mobile phone using electronic-money service. BACKGROUND ART [0003]In recent years, a demonstration test of a settlement system using electronic money has been successful and the electronic money is put into practical use. [0004]Currently, a retail shop uses the electronic money for settlement. Further, in order to widespread the electronic money to general users, efforts are made to develop a technology of elements and structure a business model. [0005]In addition to the retail shop, a system using the electronic money is put into practical use to adjust the fare of a train or bus. [0006]With the electronic money, an electronic-money card stores the same exchange value, that is, so-called value, as the money, and is used as an electronic wallet. [0007]The value is written to the electronic-money card by a specific terminal device (hereinafter, referred to as an electronic-money terminal). The processing for writing the value is called charge. Upon charging the value, the money corresponding to the value is collected from a user. Thus, the actual money corresponds to the value, thereby keeping the exchange value of the value for security. [0008]The settlement using the value is executed by subtracting the amount of money corresponding to the settlement from the value stored in the electronic-money card on the electronic-money terminal. [0009]The electronic-money card comprises a non-contact IC (Integrated Circuit) card or a contact IC card. [0010]The electronic-money card comprising the non-contact IC card comprises: an IC chip having a value processing function and a value storing function; and an antenna for communication with the electronic-money terminal. The antenna has a function for wireless communication with the electronic-money terminal and further has a function for generating the power for receiving the electronic waves from the electronic-money terminal and driving the IC chip. [0011]The electronic-money terminal communicates by radio waves with the IC chip via the antenna, and accesses the IC chip in the electronic-money card, thereby performing various processing for value (writing processing, subtraction, and reference to the balance, hereinafter, referred to as value processing). Mainly, using forms of the electronic-money card are as follows. (1) Charge Value [0012]First, in a shop in which an electronic-money terminal is installed, an electronic-money card is set to the electronic-money terminal, and the writing operation of a value is requested to a person in charge. In this case, the money corresponding to the value is paid. [0013]Next, the person in charge operates the electronic-money terminal to write the value of charge to the electronic-money terminal. [0014]Then, the electronic-money terminal sends a write command for adding the money corresponding to the value to the IC chip in the electronic-money card. [0015]The IC chip receives the write command and executes the command, thereby adding the money of value stored in the IC chip. [0016]As mentioned above, the value is charged to the electronic-money card. [0017]Incidentally, in an unmanned electronic-money terminal, the electronic money card is set and the money is set to the electronic-money card, thereby automatically charging the value. (2) Settle by Value [0018]First, a product or service, serving as a target of settlement, is presented to a person in charge of an electronic-money terminal. An electronic-money card is set to the electronic-money terminal installed to a shop, and a message indicating the settlement using the value is sent to the person in charge. [0019]On the contrary, the person in charge operates the electronic-money terminal to subtract the money for settlement from the value stored in the electronic-money card. [0020]Then, the electronic-money terminal sends a subtract command for subtracting the value corresponding to the money to the IC chip in the electronic-money card. [0021]The IC chip receives the subtract command and executes the command, thereby subtracting the value corresponding to the value stored in the IC chip. [0022]As mentioned above, the settlement is performed by using the value in the electronic-money card. [0023]Incidentally, in an electronic-money terminal installed to a vending machine, a user purchases a product, and the value is automatically settled. (3) Use Electronic Money on Internet [0024]With a terminal device having an Internet access function and a reader/writer for reading/writing data to/from an electronic-money card, a value is charged to the electronic-money card or a settlement is performed by a value stored in the electronic-money card. [0025]When a value is to be charged, the electronic-money card is set to the reader/writer and is accessed to a Web site for charge on the terminal device. Then, the communication is established between a server device and the electronic-money card, and the server device writes the value to the electronic-money card. The money corresponding to the written value is withdrawn from a bank account of a user, or is processed by a credit card. [0026]In the settlement using the value, similarly, the communication is established between the server device and the electronic-money card, and the value is subtracted. [0027]As mentioned above, the electronic-money card is used as a pre-paid electronic wallet and, in particular, it is advantageous for a user in the settlement of a small amount of money because the small change does not burden the user. [0028]Recently, the mobile phone is excessively spread and it is tried that the mobile phone has the same function as that of the electronic-money card. [0029]If the mobile phone has the same function as that of the electronic-money card, a user charges the value to the mobile phone or settles the money by the value stored in the mobile phone. [0030]As mentioned above, the following technology allows the mobile phone to have the function of the electronic-money card. [0031](Patent Document 1) [0032]Japanese Unexamined Patent Application Publication-No. 2002-352173 [0033]According to the invention disclosed in Patent Document 1, a specific memory for storing the value to the mobile phone is provided, and the value is charged or the money is settled by the stored value. [0034]Upon installing the same value processing function as that of the electronic-money card to the mobile phone, the install timing is a problem. [0035]Upon installing the value processing function to the mobile phone, various information on the security must be installed. [0036]If the install processing is commissioned to an external operator, then, information on the security is transferred to the commission site, and the information is not managed in the company itself. SUMMARY OF THE INVENTION [0037]Then, it is an object of the present invention to provide a mobile terminal device in which information is easily managed upon installing the value processing function. [0038]In order to solve the object, according to a first aspect of the invention, there is provided a mobile terminal device comprising: information processing means for processing electronic information; storing means for storing the electronic information; generating means for generating money information storing means for storing money information to the storing means; secret information receiving means for being connected to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device; and installing means for installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0039]According to the invention, in the mobile terminal device the secret information is identification information for identifying the mobile terminal device by the predetermined terminal device or the predetermined server device. [0040]According to the invention the mobile terminal device further comprises: ID information receiving means for receiving registering ID information from the providing server device; and display means for displaying information, wherein the installing means installs the received registering ID information to the storing means so as to display the received registering ID information on the display means. [0041]According to the invention, in the mobile terminal device the money information processing program enables the information processing means to realize an ID sending function for sending, to the predetermined terminal, the registering ID information installed upon receiving the changing information of the amount of money from the predetermined terminal by the money-amount information receiving function. [0042]According to a second aspect of the invention, a mobile terminal method executed by a computer comprises information processing means for processing electronic information, storing means for storing the electronic information, generating means, secret information receiving means, and installing means, the mobile terminal method comprising: a generating step of generating money information storing means for storing money information to the storing means; a secret information receiving step of enabling the connection to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device by the secret information receiving means; and an installing step of installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0043]According to a third aspect of the invention, a mobile terminal program for a computer comprises information processing means for processing electronic information and storing means for storing the electronic information to execute: a generating function for generating money information storing means for storing money information to the storing means; a secret information receiving function for enabling the connection to a providing server device for providing predetermined secret information and receiving the secret information from the providing server device; and an installing function for installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0044]According to a fourth aspect of the invention, a providing server device for providing secret information to a mobile terminal device according to the first aspect comprises: connecting means for enabling the connection to the mobile terminal device; and sending means for sending the secret information to the connected mobile terminal device. [0045]According to a fifth aspect of the invention a providing server method executed by a computer comprising connecting means and sending means, for providing secret information to a mobile terminal device according to the first aspect comprises: a connecting step of enabling the connection to the mobile terminal device by the connecting means; and a sending step of sending the secret information to the connected mobile terminal device by the sending means. [0046]According to a sixth aspect of the invention, a providing server program for providing secret information to a mobile terminal device for enabling a computer to realize: a connecting function for enabling the connection to the mobile terminal device; and a sending function for sending the secret information to the connected mobile terminal device. [0047]According to another embodiment of the invention, a mobile terminal device comprises: connecting means for enabling the connection to an information processing device comprising information processing means for processing electronic information and storing means for storing the electronic information; generating means for generating money information storing means for storing money information to the storing means for the connected information processing device; secret information receiving means for enabling the connection to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device; and installing means for installing, into the storing means of the connecter information processing device, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0048]According to another embodiment of the first aspect of the invention, a mobile terminal device comprises: connecting means for enabling the connection to storing means for storing electronic information; information processing means for processing electronic information; generating means for generating money information storing means for storing money information to the connected storing means; secret information receiving means for enabling the connection to a providing server device for providing predetermined secret information and for receiving the secret information from the providing server device; and installing means for installing, into the storing means, a money information processing program for enabling the information processing means to execute money information processing and the received secret information, wherein the money information processing program enables the information processing means to realize a money-amount information receiving function for receiving changing information of the amount of money from a predetermined terminal device or a predetermined server device by using the installed secret information and a money information processing function for changing the amount of money of the money information stored in the money information storing means by using the received changing information of the amount of money. [0049]According to the present invention, secret information to install the value processing function to the mobile terminal device is easily managed. BRIEF DESCRIPTION OF THE DRAWINGS [0050]FIG. 1 is a diagram showing one example of the structure of an electronic-money system; [0051]FIG. 2 is a diagram showing one example of the appearance of a mobile phone; [0052]FIG. 3 is a diagram for explaining a function of the mobile phone before installing the value processing function; [0053]FIG. 4 is a diagram for explaining the function of the mobile phone after installing the value processing function; [0054]FIG. 5 is a diagram for explaining one example of the hardware structure of the mobile phone; [0055]FIG. 6 is a diagram for explaining one example of the functional structure of an electronic-money server; [0056]FIG. 7 is a diagram showing one example of the logical structure of user information; [0057]FIG. 8 is a diagram showing one example of the logical structure of transaction information; [0058]FIG. 9 is a diagram showing one example of the hardware structure of the electronic-money server; [0059]FIG. 10 is a diagram showing one example of the hardware structure of an electronic-money card; [0060]FIG. 11(a) is a diagram for explaining the operation of the mobile phone upon installing the value processing function, and FIG. 11(b) is a diagram for explaining the operation of the mobile phone after installing the value processing function; [0061]FIG. 12 is a diagram showing one example of a screen displayed on the mobile phone upon installing the value processing function; [0062]FIG. 13 is a diagram for explaining the case of charging the value from an electronic-money terminal to the mobile phone; and [0063]FIG. 14 is a flowchart for explaining the installing sequence of the value processing function. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0064]Hereinbelow, a preferred embodiment of the present invention will be described. (1) Outline of Embodiments [0065]A mobile phone having an Internet access function comprises an IC chip having the same function as that used for a non-contact electronic-money card; and an auxiliary program (hereinafter, referred to as an installing program for installing the value processing function to the IC chip by a server device. At the time that the mobile phone is sold, the value processing function is not installed to the IC chip of the mobile phone. A user purchases the mobile phone, then, the mobile phone communicates with the server device for communication, and the value processing function is installed to the IC chip. [0066]At the installing time, the mobile phone sends, to an electronic-money server, information necessary for a carrier of electronic money, such as an IC chip ID (ID information uniquely assigned to the IC chip), and receives information necessary for using electronic-money service from the electronic-money server and installs the received information. The received and installed information includes secret information for security, such as key information, which will be described later. [0067]After installing the value processing function, the function operates. Then, similarly to the electronic-money card, the IC chip charges the value or performs the value processing such as the settlement using the value. [0068]The IC chip comprises an antenna for wireless communication with the electronic-money terminal, similarly to the electronic-money card. With the IC chip, the mobile phone is set to the electronic-money terminal to charge the value to the mobile phone, or the money is settled by the value stored in the mobile phone. [0069]Further, the mobile phone comprises an Internet access function. Therefore, the value on the IC chip is charged from the server device on the Internet, or the money is settled by the value stored in the IC chip. [0070]According to the embodiment, the mobile phone includes the IC chip (information processing device). Further, the IC chip may be detachable to the mobile phone, and may be attached to the mobile phone for use purpose. Alternatively, the mobile phone may include a function unit corresponding to a CPU (information processing means) of the IC chip, and a function unit corresponding to a memory (memory means) of the IC ship may be detachable. [0071]In the case of using a detachable IC chip or memory, a connector (connecting means) is arranged on the mobile phone side. (2) Details of the Embodiment [0072]FIG. 1 is a diagram showing an example of an electronic-money operating system 1 according to the embodiment. [0073]The electronic-money operating system 1 comprises: a mobile phone 7; an electronic-money server 2; an Internet 4; a base station 5; a phone line network 6; an electronic-money card 15; and electronic-money terminals 8, 8, 8 . . . . [0074]Hereinbelow, the components will be described later. [0075]The mobile phone 7 (mobile terminal device) comprises: a phone function unit 10; an electronic-money function unit 12; and a relay unit 27 which connects the phone function unit 10 to the electronic-money function unit 12. [0076]The phone function unit 10 is a function unit having a function as a digital phone having an Internet access function. The electronic-money function unit 12 is a function unit for storing the value and processing the value, similarly to the electronic-money card 15 (which will be described later). [0077]The communication is established between the phone function unit 10 and the electronic-money function unit 12 via the relay unit 27. [0078]Here the value means money information indicating the amount of money having the money price as electronic information, and has the identical exchange value to the money. The money information is operated by increase/reduction, thereby moving the value. Thus, the value is used for settlement (e.g. of a consumer transaction. [0079]The phone function unit 10 has two modes of a call mode and an application mode. A user uses communication service in the call mode. In the application mode, the user receives the service provided by the application. [0080]The phone function unit 10 communicates with the base station 5 by radio waves, and accesses the phone line network 6 or Internet 4 via the base station 5. [0081]Upon using the mobile phone 7 in the call mode, a communication line is established between the mobile phone 7 and a partner's phone via the phone line network 6. [0082]Upon using the mobile phone 7 in the application mode, the mobile phone 7 is accessed to the Internet 4, thereby using services provided by server devices. In addition, service of a game is used off-line (without being accessed to the Internet 4). [0083]FIG. 2 is a diagram showing an example of the appearance of the mobile phone 7. The mobile phone 7 comprises: a phone antenna 19; speaker 20; a display 21; a keyboard 22; and a microphone 23. [0084]The phone antenna 19 is an antenna for radio communication with the base station 5. [0085]The speaker 20 is a device for converting an electrical signal and generating sound. In the call mode, sound generated by a call partner is outputted. In the application mode, sound data-sent from the server device is reproduced. [0086]The display 21 is a display device for displaying characters and an image, such as a liquid crystal display or a plasma display. [0087]In the call mode, the display 21 displays call information on the call including a receiving state of radio waves, a phone number inputted by the user, or a phone number of the call partner. [0088]In the application mode, the display 21 displays a screen provided by the application. [0089]In the access to the Internet, a screen using screen data sent by the server device is displayed. [0090]In the off-line, various screens, such as a game screen, provided by the application are displayed. For example, the balance or history of value stored in the electronic-money function unit 12 is displayed. [0091]The keyboard 22 comprises a character key for inputting character information of numerals and characters and a function key. The function key is a key having assigned specific functions for turning on/off the mobile phone 7, switching the call mode and the application mode, or moving a cursor displayed on the exposing device 21, and clicking a button displayed on the display 21. [0092]The user presses the key of the display 21 to perform various operations, thereby inputting a URL (Uniform Resource Locators) on a desired Web site, inputting information in an input column displayed on the screen, and selecting an item displayed on the screen. [0093]With the above function, the URL of a service site (Web site for providing the service on the electronic money) of the electronic-money server 2 is inputted or the install operation of the value processing function is selected on the screen provided by the service site, thereby installing the value processing function to the mobile phone 7. [0094]The microphone 23 is a device for obtaining sound and converting the sound into an electronic signal. The user inputs the sound from the microphone 23. [0095]Next, a description is given of the value processing of the various functions provided for the mobile phone 7. [0096]The functions of the mobile phone 7 are different from the state before installing the value processing function and the state after the install operation. First, a description is given of the functional structure before installing the value processing function with reference to FIG. 3. [0097]FIG. 3 is a diagram showing the functional structure of the mobile phone 7 before installing the value processing function. [0098]Referring to FIG. 3, before installing the value processing function, the electronic-money function unit 12 shown in FIG. 1 is referred to as an IC function unit 12a. [0099]As will be described later, the phone function unit 10 and the IC function unit 12a comprise CPUs (Central Processing Units). The CPUs execute predetermined programs, thereby enabling the function units to operate like software. [0100]Referring to FIG. 3, the IC function unit 12a comprises a central processing unit 28a (information processing means) and a storing unit 29a (storing means). [0101]Although not shown, the IC function unit 12a has the identical function as that of an antenna (hereinafter, referred to as a terminal antenna) for communication between a non-contact IC card and the electronic-money terminal 8, and accesses a terminal for the non-contact IC card, such as the electronic-money terminal 8. [0102]The storing unit 29a is writable and readable and stores a plurality of pieces of programs data. [0103]At the time of sale of the mobile phone 7 to the users, a basic program for operating the IC function unit 28a is installed to the storing unit 29a. [0104]The above-mentioned basic program includes an OS (Operating System) for input/output processing of a file, and control of the IC function unit 12a, or a communication program for radio communication of the IC function unit 12a with a terminal for non-contact IC card. [0105]The central processing unit 28a is a function unit for executing a predetermined program, performing the calculation, controlling the entire IC function unit 12a, and executing information processing such as input/output of data. [0106]The central processing unit 28a reads a program or data from the storing unit 29a or the application unit 26. Further, the central processing unit 28a receives, by wireless manner, a program or data from a terminal for non-contact IC card via a terminal antenna, and reads the received program or data. [0107]An install program is read to the central processing unit 28a, and is executed, thereby installing application programs to the storing unit 29a. The install program is provided for each application program. [0108]The central processing unit 28a executes the install program and then ensures an area for installing the application program in the storing unit 29a (when the application program for install is known in advance, the area for the program is ensured in advance). [0109]After formatting the ensured area to match the data format of the application program, the application program is written to the area. [0110]After installing the application program to the storing unit 29a, the application program is read to the central processing unit 28a, and is executed. [0111]According to the embodiment, the application program (hereinafter, value processing program) is installed to the storing unit 29a, and the central processing unit 28a realizes the value processing function. [0112]The relay unit 27 is a function unit (interface) for relaying the communication between the phone function unit 10 and the IC function unit 12a. In the relay of communication between the phone function unit 10 and the IC function unit 12a, the relay unit 27 encrypts the data to be sent to the phone function unit 10, or decrypts the encrypted data to be sent to the IC function unit 12a by the phone function unit 10. [0113]This is because the data the phone function unit 10 receives and transmits to/from the electronic-money server 2 are encrypted/decrypted, thereby improving the security. [0114]The electronic-money server 2 comprises: means for combining the data received from the phone function unit 19; and means for encrypting the data sent to the mobile phone 7. [0115]When the communication format of the phone function unit 10 is different from that of the IC function unit 12a, the communication format can be converted. [0116]This is because, for example, there could be a case in which the IC function unit 12a communicates data in the same communication format of the non-contact IC card, while the phone function unit 10 uses the communication format on the Internet 4 and the communication format needs to be con converted to access the IC function unit 12a from the phone function unit 10. [0117]The application unit 26 is a function unit for providing various applications by the mobile phone 7. [0118]The application unit 26 provides an Internet access function for connecting the mobile phone 7 to the Internet 4, a using function of the IC function unit for using application programs installed in the IC function unit 12a, and a service providing function for providing various services such as a game or calendar. [0119]In the case of providing the Internet access function, the application unit 26 receives the input of URL and accesses the mobile phone 7 to a Web site specified by the URL. Further, the application unit 26 reproduces information (image information, character information, and sound information) sent by the site in the access destination and sends the information from the mobile phone 7 to a site in the access destination and thus functions as a browser. [0120]The application unit 26 has an installing unit 26a (installing means and generating means) for supporting the install operation of the value processing program (money information processing program) to the IC function unit 12a by the electronic-money server 2. [0121]The installing unit 26 communicates with the central processing unit 28a and the electronic-money server 2 and simultaneously installs (incorporates) the value processing program to the storing unit 29a. [0122]Specifically, the installing unit 26 operates cooperatively with the electronic-money server 2, and sends, to the central processing unit 28a, a program for installing the value processing program. The central processing unit 28a executes the sent program, thereby installing the value processing program to the storing-unit 29a. [0123]The program to be installed may be downloaded from the electronic-money server 2 at the install time, or may be provided for the installing unit 26a in advance. [0124]In the case of installing the value processing program, the installing unit 26a receives information necessary for executing the value processing program including key information (identification information used (String), 相关申请的交叉引用 [0001] 本申请是共同未决国际申请号 PCT/JP2004/002862 的美国国家阶段申请,于 2004 年 3 月 5 日提交,要求优先权日期为 2003 年 3 月 7 日,并以非英语公布。 技术领域 [0002] [0001] 本发明涉及一种移动电话装置,更具体地,涉及一种使用电子货币服务的移动电话。 背景技术 [0003] 近年来,电子货币结算系统的实证试验取得成功,电子货币已投入实际使用。 [0004] 目前,零售商店使用电子货币进行结算。 此外,为了向普通用户普及电子货币,努力开发元件技术和构建商业模型。 [0005] 除了零售店之外,使用电子货币的系统也被投入实际使用以调整火车或公共汽车的票价。 [0006] 对于电子货币,电子货币卡存储与货币相同的交换价值,即所谓的价值,并用作电子钱包。 [0007] 通过特定的终端设备(以下称为电子货币终端)将价值写入电子货币卡。 写入值的处理称为充电。 在收取该价值后,从用户处收取对应于该价值的钱。 这样,实际的货币就对应了价值,从而保持了交换价值的安全性。 [0008] 使用价值的结算是通过从电子货币终端上存储在电子货币卡中的价值减去与结算对应的金额来执行的。 [0009] 电子货币卡包括非接触式IC(集成电路)卡或接触式IC卡。 [0010] 包括非接触IC卡的电子货币卡包括:具有价值处理功能和价值存储功能的IC芯片; 以及用于与电子货币终端通信的天线。 天线具有与电子货币终端进行无线通信的功能,还具有产生电力以接收来自电子货币终端的电子波并驱动IC芯片的功能。 [0011] 电子货币终端通过天线与IC芯片进行电波通信,访问电子货币卡内的IC芯片,进行各种价值处理(写入处理、减法、余额参照,以下称为 作为价值处理)。 电子货币卡的使用方式主要有以下几种。 (1) 收费金额 [0012] 首先,在设置有电子货币终端的店铺中,将电子货币卡设置于电子货币终端,向负责人请求价值的写入操作。 在这种情况下,支付与价值对应的钱。 [0013] 接下来,负责人操作电子货币终端以将充值金额写入电子货币终端。 [0014] 然后,电子货币终端向电子货币卡内的IC芯片发送追加与价值对应的货币的写入命令。 [0015] IC芯片接收写入命令并执行命令,从而增加存储在IC芯片中的有价货币。 [0016] 如上所述,价值被记入电子货币卡。 [0017] 顺便提及,在无人电子货币终端中,设置电子货币卡并将货币设置到电子货币卡,从而自动充值。 (2) 按价值结算 [0018] 首先,将作为结算对象的商品或服务出示给电子货币终端的负责人。 电子货币卡被设置到安装到商店的电子货币终端,并且指示使用价值的结算的消息被发送到负责人。 [0019]相反,负责人操作电子货币终端以从存储在电子货币卡中的价值中减去用于结算的货币。 [0020] 然后,电子货币终端向电子货币卡中的IC芯片发送用于减去对应于货币的价值的减法命令。 [0021] IC芯片接收减法命令并执行该命令,从而减去与IC芯片中存储的值对应的值。 [0022] 如上所述,使用电子货币卡内的价值进行结算。 [0023] 附带地,在安装到自动售货机的电子货币终端中,用户购买商品,并且自动结算价值。 (3) 在互联网上使用电子货币 [0024] 通过具有因特网访问功能的终端装置和用于向/从电子货币卡读取/写入数据的读取器/写入器,向电子货币卡充值或使用存储在电子货币卡中的值进行结算 -钱卡。 [0025] 当要充值时,电子货币卡被设置到读取器/写入器并在终端设备上访问用于充值的网站。 然后,在服务器装置和电子货币卡之间建立通信,并且服务器装置将值写入电子货币卡。 对应于书面价值的钱从用户的银行账户中提取,或者通过信用卡处理。 [0026] 在使用价值的结算中,类似地,在服务器设备和电子货币卡之间建立通信,并且减去价值。 [0027] 如上所述,电子货币卡被用作预付电子钱包,特别是对于用户来说小额货币的结算是有利的,因为小额零钱不会给用户造成负担。 [0028] 最近,手机过度普及,尝试手机具有与电子货币卡相同的功能。 [0029] 如果手机具有与电子货币卡相同的功能,用户可以通过手机充值或使用手机中存储的金额进行结算。 [0030] 如上所述,以下技术可以让手机具备电子货币卡的功能。 [0031] (专利文献1) [0032] 日本未审查专利申请公开号 2002-352173 [0033] 根据专利文献1所公开的发明,在移动电话中设置用于存储价值的特定存储器,根据该价值进行充值或结算。 [0034] 在将与电子货币卡相同的价值处理功能安装到移动电话时,安装时机是个问题。 [0035] 在手机上安装值处理功能后,必须安装各种安全信息。 [0036] 如果将安装处理委托给外部运营商,则与安全有关的信息被传送到委托站点,并且该信息不在公司本身进行管理。 发明内容 [0037] 因此,本发明的目的在于提供一种在安装了价值处理功能时能够容易地管理信息的便携终端装置。 [0038]为了解决该目的,根据本发明的第一方面,提供了一种移动终端设备,包括: 用于处理电子信息的信息处理装置; 用于存储电子信息的存储装置; 用于生成货币信息的生成装置,用于将货币信息存储到存储装置的存储装置; 秘密信息接收装置,用于连接到提供预定秘密信息的提供服务器设备,并用于从提供服务器设备接收秘密信息; 安装装置,用于在存储装置中安装使信息处理装置能够执行货币信息处理的货币信息处理程序和接收到的秘密信息,其中货币信息处理程序使信息处理装置能够实现货币量 信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收货币数量的变化信息,以及货币信息处理功能,用于改变存储在货币信息存储中的货币信息的货币数量 是指利用接收到的金额变化信息。 [0039] 根据本发明,在移动终端设备中,秘密信息是用于由预定终端设备或预定服务器设备识别移动终端设备的识别信息。 [0040] 根据本发明,移动终端设备还包括: ID信息接收装置,用于从提供服务器设备接收注册ID信息; 以及用于显示信息的显示装置,其中,安装装置将接收到的注册ID信息安装到存储装置中,以便在显示装置上显示接收到的注册ID信息。 [0041] 根据本发明,在移动终端设备中,货币信息处理程序使信息处理装置能够实现ID发送功能,用于向预定终端发送在从 通过金额信息接收功能向规定的终端发送信息。 [0042] 根据本发明的第二方面,一种由计算机执行的移动终端方法包括用于处理电子信息的信息处理装置、用于存储电子信息的存储装置、生成装置、秘密信息接收装置和安装装置,该移动终端方法 包括:生成货币信息存储装置的生成步骤,用于将货币信息存储到存储装置; 秘密信息接收步骤,使与提供预定秘密信息的提供服务器设备的连接成为可能,并通过秘密信息接收装置从提供服务器设备接收秘密信息; 以及安装步骤,将用于使信息处理装置执行货币信息处理的货币信息处理程序和接收到的秘密信息安装到存储装置中,其中货币信息处理程序使信息处理装置能够实现货币- 金额信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收金额的变化信息,以及货币信息处理功能,用于改变存储在货币信息中的货币信息的金额 存储装置利用接收到的金额变化信息。 [0043]根据本发明的第三方面,用于计算机的移动终端程序包括用于处理电子信息的信息处理装置和用于存储电子信息以执行的存储装置:用于生成货币信息的生成功能存储装置用于将货币信息存储到 储存装置; 秘密信息接收功能,用于与提供预定的秘密信息的提供服务器装置连接,并从提供服务器装置接收秘密信息; 以及安装功能,用于将用于使信息处理装置执行货币信息处理的货币信息处理程序和接收到的秘密信息安装到存储装置中,其中货币信息处理程序使信息处理装置能够实现货币- 金额信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收金额的变化信息,以及货币信息处理功能,用于改变存储在货币信息中的货币信息的金额 存储装置利用接收到的金额变化信息。 [0044] 根据本发明的第四方面,一种用于向根据第一方面的移动终端设备提供秘密信息的提供服务器设备包括: 连接装置,用于实现与移动终端设备的连接; 发送装置,用于向连接的移动终端设备发送秘密信息。 [0045] 根据本发明的第五方面,一种由计算机执行的提供服务器方法,包括连接装置和发送装置,用于向根据第一方面的移动终端设备提供秘密信息,包括:连接步骤,启用与移动终端的连接 通过连接装置的装置; 发送步骤,通过发送装置将保密信息发送给连接的移动终端设备。 [0046] 根据本发明的第六方面,一种提供服务器程序,用于向移动终端设备提供秘密信息,以使得计算机能够实现: 连接功能,用于实现与移动终端设备的连接; 以及发送功能,用于将秘密信息发送到连接的移动终端设备。 [0047] 根据本发明的另一个实施例,移动终端设备包括:连接装置,用于实现与信息处理设备的连接,该信息处理设备包括用于处理电子信息的信息处理装置和用于存储电子信息的存储装置; 用于生成货币信息的生成装置,用于将货币信息存储到连接的信息处理设备的存储装置中的存储装置; 秘密信息接收装置,用于实现与提供预定秘密信息的提供服务器设备的连接,并用于从提供服务器设备接收秘密信息; 安装装置,用于将用于使信息处理装置执行货币信息处理的货币信息处理程序和接收到的秘密信息安装到连接器信息处理设备的存储装置中,其中货币信息处理程序使信息处理装置能够执行 实现用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收金额变化信息的金额信息接收功能和用于改变货币信息的金额的货币信息处理功能 利用接收到的金额变化信息,将货币金额存储在货币信息存储装置中。 [0048]根据本发明第一方面的另一个实施例,一种移动终端设备包括:连接装置,用于实现与用于存储电子信息的存储装置的连接; 用于处理电子信息的信息处理装置; 用于生成货币信息存储装置的生成装置,用于将货币信息存储到连接的存储装置; 秘密信息接收装置,用于实现与提供预定秘密信息的提供服务器设备的连接,并用于从提供服务器设备接收秘密信息; 安装装置,用于在存储装置中安装使信息处理装置能够执行货币信息处理的货币信息处理程序和接收到的秘密信息,其中货币信息处理程序使信息处理装置能够实现货币量 信息接收功能,用于通过使用安装的秘密信息从预定终端设备或预定服务器设备接收货币数量的变化信息,以及货币信息处理功能,用于改变存储在货币信息存储中的货币信息的货币数量 是指利用接收到的金额变化信息。 [0049] 根据本发明,容易管理用于将价值处理功能安装到移动终端设备的秘密信息。 附图的简要说明 [0050] 图1是表示电子货币系统的构成例的图。 [0051] 图2是表示移动电话的外观例的图。 [0052] 图3是用于说明安装数值处理功能之前的移动电话的功能的图。 [0053] 图4是手机安装数值处理功能后的功能说明图。 [0054] 图5是用于说明移动电话的硬件结构的一例的图。 [0055] 图6是用于说明电子货币服务器的功能结构的一例的图。 [0056] 图7是表示用户信息的逻辑结构的一例的图。 [0057] 图8是表示交易信息的逻辑结构的一个例子的图。 [0058] 图9是表示电子货币服务器的硬件结构的一例的图。 [0059] 图10是表示电子货币卡的硬件结构的一例的图。 [0060] 图 11( a )是用于说明移动电话在安装值处理功能时的操作的图,图11( b )为手机安装数值处理功能后的操作说明图; [0061] 图12是表示安装了数值处理功能时移动电话显示的画面的一例的图。 [0062] 图13是用于说明从电子货币终端向移动电话充值的情况的图。 和 [0063] 图14是用于说明值处理功能的安装顺序的流程图。 优选实施例的详细说明 [0064] 以下,对本发明的优选实施方式进行说明。 (1)实施方式概要 [0065] 一种具有上网功能的手机,包括与非接触式电子货币卡功能相同的IC芯片; 以及辅助程序(以下称为安装程序,用于通过服务器设备将价值处理功能安装到IC芯片。在移动电话销售时,价值处理功能未安装到IC芯片 手机,用户购买手机后,手机与服务器设备进行通信,并在IC芯片上安装价值处理功能。 [0066]在安装时,移动电话向电子货币服务器发送电子货币的载体所需的信息,例如IC芯片ID(唯一分配给IC芯片的ID信息),并接收使用电子货币所需的信息 -来自电子货币服务器的货币服务并安装接收到的信息。 接收和安装的信息包括用于安全的秘密信息,例如稍后将描述的密钥信息。 [0067] 安装值处理函数后,函数运行。 然后,类似于电子货币卡,IC芯片对价值进行充值或使用该价值执行诸如结算的价值处理。 [0068] IC芯片包括用于与电子货币终端进行无线通信的天线,类似于电子货币卡。 通过IC芯片,将手机设置为电子货币终端,向手机充值,或通过手机中存储的金额进行结算。 [0069] 进一步的,所述手机具有上网功能。 因此,IC芯片上的价值是从互联网上的服务器设备收取的,或者是用IC芯片中存储的价值来结算的。 [0070] 根据该实施例,移动电话包括IC芯片(信息处理装置)。 此外,IC芯片可以是可拆卸到手机上的,并且可以附加到手机上使用。 或者,移动电话可以包括对应于IC芯片的CPU(信息处理装置)的功能单元,并且对应于IC芯片的存储器(存储装置)的功能单元可以是可拆卸的。 [0071] 在使用可拆卸的IC芯片或存储器的情况下,连接器(连接装置)布置在移动电话侧。 (2)实施方式的详细内容 [0072] 图1是表示电子货币操作系统的例子的图 1 根据实施例。 [0073] 电子货币操作系统 1 包括:一部手机 7 ; 电子货币服务器 2 ; 互联网 4 ; 基站 5 ; 电话线网络 6 ; 电子货币卡 15 ; 和电子货币终端 8 , 8 , 8 . . . . [0074] 在下文中,稍后将描述这些组件。 [0075] 手机 7 (移动终端设备)包括:电话功能单元 10 ; 电子货币功能单元 12 ; 和一个中继单元 27 连接电话功能单元 10 到电子货币功能单元 12 . [0076] 电话功能单元 10 是具有作为具有因特网访问功能的数字电话的功能的功能单元。 电子货币功能单元 12 是存储价值和处理价值的功能单元,类似于电子货币卡 15 (这将在后面描述)。 [0077] 电话功能单元之间建立通信 10 和电子货币功能单元 12 通过中继单元 27 . [0078] 在此,价值是指表示具有作为电子信息的货币价格的金额的货币信息,并且具有与货币相同的交换价值。 通过增加/减少操作货币信息,从而移动价值。 因此,该值用于结算(例如消费者交易。 [0079] 电话功能单元 10 具有调用模式和应用模式两种模式。 用户在呼叫模式下使用通信服务。 在应用模式下,用户接收应用提供的服务。 [0080] 电话功能单元 10 与基站通信 5 通过无线电波,并接入电话线网络 6 或互联网 4 通过基站 5 . [0081] 使用手机时 7 在通话模式下,手机与手机之间建立了一条通讯线路 7 和合作伙伴的电话通过电话线网络6 . [0082] 使用手机时 7 在应用程序模式下,手机 7 访问互联网 4 ,从而使用服务器设备提供的服务。 此外,游戏服务是离线使用的(无需访问互联网 4 ). [0083] 图2是移动电话的外观示例图 7 . 手机 7 包括:电话天线 19 ; 扬声器 20 ; 显示器 21 ; 键盘 22 ; 和麦克风 23 . [0084] 手机天线 19 是与基站进行无线电通信的天线 5 . [0085] 演讲者 20 是一种转换电信号并产生声音的装置。 在通话模式中,输出通话伙伴发出的声音。 在应用模式中,再现从服务器设备发送的声音数据。 [0086] 显示器 21 是用于显示字符和图像的显示设备,例如液晶显示器或等离子显示器。 [0087] 在通话模式下,显示 21 显示呼叫的呼叫信息,包括无线电波的接收状态、用户输入的电话号码或呼叫伙伴的电话号码。 [0088] 在应用模式下,显示 21 显示应用程序提供的屏幕。 [0089] 在访问因特网时,显示使用服务器设备发送的屏幕数据的屏幕。 [0090] 在离线状态下,显示应用提供的游戏画面等各种画面。 例如,存储在电子货币功能单元中的余额或历史价值 12 被陈列。 [0091] 键盘 22 包括用于输入数字和字符的字符信息的字符键和功能键。 功能键是分配了特定功能的按键,用于打开/关闭手机 7 ,切换调用模式和应用模式,或移动显示在显示设备上的光标 21 ,然后单击显示屏上显示的按钮 21 . [0092] 用户按下显示器的键 21 执行各种操作,从而在所需网站上输入 URL(统一资源定位器),在屏幕上显示的输入栏中输入信息,并选择屏幕上显示的项目。 [0093] 通过上述功能,电子货币服务器的服务站点(提供电子货币服务的网站)的 URL 2 在服务站点提供的屏幕上输入或选择值处理功能的安装操作,从而将值处理功能安装到手机上 7 . [0094] 麦克风 23 是一种获取声音并将声音转换成电子信号的装置。 用户从麦克风输入声音 23 . [0095] 下面对手机提供的各种功能的取值处理进行说明 7 . [0096] 手机的功能 7 不同于安装值处理函数之前的状态和安装操作之后的状态。 首先,参照图3说明安装值处理功能之前的功能结构。 [0097] 图3为手机功能结构示意图 7 在安装值处理功能之前。 [0098] 参考图3,在安装价值处理功能之前,电子货币功能单元 12 如图1所示称为IC功能单元 12 a. [0099] 正如后面将要描述的,电话功能单元 10 和 IC 功能单元 12 a 包括 CPU(中央处理单元)。 CPU执行预定程序,从而使功能单元能够像软件一样操作。 [0100] 参考图3,IC功能单元 12 a 包括一个中央处理单元 28 a (信息处理装置)和存储单元 29 a (存储方式)。 [0101] 虽然没有显示, IC功能单元 12 a 具有与用于非接触式IC卡和电子货币终端之间的通信的天线(以下称为终端天线)相同的功能 8 ,接入非接触式IC卡终端,如电子货币终端 8 . [0102] 收纳单元 29 a 可写入可读取,并储存多个程序数据。 [0103] 手机销售时 7 给用户,用于操作 IC 功能单元的基本程序 28 a 安装到存储单元 29 a. [0104] 上述基本程序包括用于文件的输入/输出处理的OS(操作系统)和IC功能单元的控制 12 a ,或用于IC功能单元无线电通信的通信程序 12 a 带有非接触式IC卡终端。 [0105] 中央处理器 28 a 是一个功能单元,用于执行预定的程序,进行计算,控制整个IC功能单元 12 a ,并执行信息处理,例如数据的输入/输出。 [0106] 中央处理器 28 a 从存储单元中读取程序或数据 29 a 或申请单位 26 . 此外,中央处理器 28 a 通过终端天线以无线方式接收来自非接触式IC卡终端的程序或数据,并读取接收到的程序或数据。 [0107] 安装程序被读取到中央处理器 28 a ,并被执行,从而将应用程序安装到存储单元 29 a . 为每个应用程序提供安装程序。 [0108] 中央处理器 28 a 执行安装程序,然后在存储单元中确保用于安装应用程序的区域 29 a (当预先知道要安装的应用程序时,预先确定程序的区域)。 [0109] 在对保证区域进行格式化以匹配应用程序的数据格式后,将应用程序写入该区域。 [0110] 将应用程序安装到存储单元后 29 a , 应用程序被读入中央处理器 28 a , 并被执行。 [0111] 根据该实施例,应用程序(以下称为值处理程序)被安装到存储单元 29 a , 和中央处理单元 28 a 实现值处理功能。 [0112] 中继单元 27 是一个功能单元(接口),用于中继电话功能单元之间的通信 10 和 IC 功能单元 12 a . 在电话功能单元之间的中继通信 10 和 IC 功能单元 12 a , 中继单元 27 加密要发送到电话功能单元的数据 10 , 或解密加密数据发送给IC功能单元 12 a 通过电话功能单元 10 . [0113] 这是因为电话功能单元的数据 10 从电子货币服务器接收和传输 2 加密/解密,从而提高安全性。 [0114] 电子货币服务器 2 包括:用于组合从电话功能单元接收的数据的装置 19 ; 以及对发送到手机的数据进行加密的方法 7 . [0115] 当电话功能单元的通信格式 10 不同于IC功能单元 12 a , 可以转换通讯格式。 [0116]这是因为,例如,可能存在 IC 功能单元 12 a 以与非接触式IC卡相同的通信格式进行数据通信,而电话功能单元 10 使用互联网上的通信格式 4 需要con转换通讯格式才能访问IC功能单元 12 a 从电话功能单元 10 . [0117] 申请单位 26 是手机提供各种应用的功能单元 7 . [0118] 申请单位 26 提供连接手机上网功能 7 上网 4 , IC功能单元的使用函数,用于使用安装在IC功能单元中的应用程序 12 a ,以及提供游戏或日历等各种服务的服务提供功能。 [0119] 在提供上网功能的情况下,申请单位 26 接收URL输入并访问手机 7 到 URL 指定的网站。 此外,申请单位 26 再现访问目的地站点发送的信息(图像信息、字符信息和声音信息),并从手机发送信息 7 到访问目的地的站点,从而起到浏览器的作用。 [0120] 申请单位 26 有一个安装单元 26 a (安装装置和生成装置)用于支持价值处理程序(货币信息处理程序)到IC功能单元的安装操作 12 a 通过电子货币服务器 2 . [0121] 安装单位 26 与中央处理器通信 28 a 和电子货币服务器 2 同时安装(合并)价值处理程序到存储单元 29 a. [0122] 具体安装单位 26 与电子货币服务器协同操作 2 , 并发送到中央处理单元 28 a ,用于安装值处理程序的程序。 中央处理器 28 a 执行发送的程序,从而将值处理程序安装到存储单元 29 a. [0123] 要安装的程序可以从电子货币服务器上下载 2 在安装时,或者可以为安装单元提供 26 a 提前。 [0124] 在安装值处理程序的情况下,安装单元 26 a 接收执行价值处理程序所需的信息,包括密钥信息(用于识别移动电话的识别信息 7 通过电子货币终端 8 )、后述的电子货币ID(注册ID信息)以及来自电子货币服务器的电子货币ID 2 , 并将信息存入存储单元 29 a . 此外,安装单位 26 a 发送到电子货币服务器 2 , 电子货币服务器提供电子货币服务所需的信息 2 ,例如构成IC功能单元的IC芯片的IC芯片ID 12 a. [0125] 下面结合图4对手机的功能结构进行说明 7 将值处理函数安装到IC功能单元后 12 a. [0126] 参考图4,IC功能单元 12 a 执行值处理程序,从而生成,给IC功能单元 12 a , 电子货币功能单元 12 包括值处理单元 28 和日志数据存储单元 29 (货币信息存储装置)。 [0127] 顺便提及,值处理程序可以总是被执行。 或者,在将另一个程序安装到 IC 功能单元时 12a , 相应的应用程序可能会根据需要启动。 [0128] 日志数据存储单元 29 是一个功能单元,用于存储值上的日志数据。 在执行值的写入、减法、余额的参照等值处理时,日志数据是记录处理内容的履历信息。 通过查阅日志数据,当前手机中存储的余额 7 或者可以知道价值处理的历史。 [0129] 作为日志数据记录的内容是处理的日期和时间、处理的类型、变化的值(例如,写入值时的值对应的金额或金额)等信息 减去价值时对应于减去的价值)如果对应于价值的金额通过处理改变,则电子货币终端的终端ID 8 用于访问和处理价值,以及当前价值余额。 [0130] 顺便说一句,申请单位 26 可以访问信息并可以在显示器上显示信息 21 . [0131] 值处理单元 28 与电子货币终端通信 8 或申请单位 26 (金额信息接收功能),执行存储在日志数据存储部中的价值处理(金额信息处理功能) 29 . [0132] 如后所述,电子货币终端 8 有读/写单元 8 a 具有用于与电子货币卡进行无线电通信的天线 15 . 手机 7 靠近电子货币终端 8 通过设置和值处理单元 28 从而与读写器单元通信 8 a 通过无线电波。 [0133] 通过申请单位 26 和中继单元 27 , 电子货币服务器 2 与值处理单元通信 28 以及价值处理单元 28 执行值处理。 [0134] 如上所述,值处理单元 28 与电子货币终端通信 8 , 申请单位 26 , 和电子货币服务器 2 . [0135] 值处理单元 28 接收命令的输入,并执行命令指定的信息处理。 [0136] 提供了各种类型的命令,例如,包括用于增加值的写入命令、用于减去值的减法命令以及用于参考值余额的余额参考命令。 [0137] 命令从电子货币终端输入 8 , 申请单位 26 , 和电子货币服务器 2 . [0138] 但是,仅由应用单元输入的命令 26 例如,是不改变与该值对应的金额的余额参考命令。 [0139] 在执行改变与价值相对应的金额的处理时,需要与实际货币对应。 因此,可以防止与电子货币载体无关地仅增加/减少价值。 [0140] 改变金额的命令形成金额改变信息。 [0141] 写入命令包括作为附件的关于值写入处理的信息,例如写入的金额、终端ID、处理日期和时间、以及用于指定组店的组店ID作为参数。 写入命令输入到值处理单元 28 然后是值处理单元 28 更新日志数据存储单元的日志数据 29 . 此外,值处理单元 28 执行加法,将参数指定的金额值加到当前余额上。 执行加法,从而收取价值。 [0142]减去命令具有作为附件的关于结算的信息,包括作为参数的减去值的金额、终端ID、处理日期和时间以及组店ID。 减法命令被输入到值处理单元 28 和值处理单元 28 从而更新日志数据存储单元的日志数据 29 . 此外,值处理单元 28 执行从当前余额中减去参数指定的金额值的减法。 通过执行减法,执行使用该值的结算(支付)。 [0143] 余额参考命令是获取当前余额值的命令。 平衡参考指令输入数值处理单元 28 和值处理单元 28 从而在日志数据存储单元中查找日志数据 29 ,从而返回值的当前余额。 [0144] 显示器 21 显示值处理单元返回的当前余额 28 ,从而向用户发送指示当前余额的通知。 [0145] 此外,用于操作值处理单元的各种命令 28 提供。 例如,操作值处理单元的命令 28 包括用于读取形成电子货币功能单元的IC芯片的IC芯片ID的读取命令 12 、电子货币ID的读取指令、向电子货币终端发送用于识别的密钥信息的指令 8 . [0146] 中继单元 27 中继应用程序单元之间的通信 26 和电子货币功能单元 12 . [0147] 申请单位 26 向值处理单元输入各种命令 28 通过中继单元 27 ,类似于电子货币终端 8 . 在这种情况下,继电器单元 27 具有与读写器相同的功能 8 a. [0148] 电子货币终端之间的通信 8 和电子货币功能单元 12 已加密。 [0149] 申请单位 26 访问值处理单元 28 通过中继单元 27 . 申请单位 26 向值处理单元输入各种命令 28 ,从而操作值处理单元 28 不改变价值余额(余额参考)并进一步连接到电子货币服务器 2 ,从而中介与电子货币服务器的通信 2 和值处理单元 28 连同继电器单元 27 . [0150] 上面提到了与值处理单元通信的方法 28 包括来自电子货币终端的无线电通信的情况 8 以及通过中继单元进行通信的情况 27 . [0151] 因此,写入命令或减法命令被输入到值处理单元 28 从电子货币终端 8 , 并通过充值或使用该值进行结算来进行结算。 命令输入到值处理单元 28 来自电子货币服务器 2 通过申请单位 26 . 然后,在互联网上收取价值 4 或者使用该值进行结算。 [0152] 下面以手机的硬件结构为例进行说明 7 参考图5,图5为安装值处理函数后的结构。 [0153] 电话功能单元 10 形成具有上网功能的数字手机 4 ,并且包括:电话天线 40 ; 基站通信单元 41 ; 电话控制单元 200 ; 一个存储单元 45 ; 显示单元 46 ; 一个操作单元 47 ; 数字信号处理单元 48 ; 和一个声音输入/输出单元 49 . [0154] 手机天线 40 向基站辐射电波 5 或吸收基站天线辐射的电波 5 . 于是,手机 7 通过无线电波与基站通信 5 , 并通过基站拨打电话 5 并上网 4 . [0155] 基站通信单元 41 (秘密信息接收装置和ID信息接收装置)驱动电话天线 40 ,并放大从电话天线发送的信号 40 或放大从基站接收到的信号 5 ,从而向电话控制单元提供信号 200 . [0156] 电话控制单元 200 包括:CPU 42 ; ROM(只读存储器) 43 和 RAM(随机存取存储器) 44 . [0157] 中央处理器 42 是中央处理单元,用于执行预定程序和进行各种信息处理,并表现出功能,如具有电话功能单元的互联网访问功能的移动电话 10 . [0158] 中央处理器 42 执行存储在ROM中的程序 43 , 内存 44 , 或存储单元 45 ,从而起到手机或互联网终端的作用 4 . 此外,中央处理器 42 访问电子货币功能单元 12 通过中继单元 27 . [0159] 只读存储器 43 是一个只读存储器,安排为可由 CPU 读取 42 , 存放CPU执行的程序或参数 42 . [0160] 只读存储器 43 例如,存储操作系统作为基本程序,用于 CPU 的操作 42 . [0161] 内存 44 是一个可读/可写的内存,为CPU提供一个工作区 42 在操作 CPU 时 42 . [0162] 收纳单元 45 存储 CPU 使用的程序或数据 42 . 收纳单元 45 是CPU的可读/可写内存 42 . 例如,存储单元 45 是闪存或 EEPROM(电可擦除可编程 ROM)。 [0163] 根据实施例,存储单元 45 包括:应用程序 45 a 用于启用 CPU 42 实现应用功能; 和一个安装程序 45 c 用于辅助电子货币服务器价值处理功能的安装操作 2 . [0164] 中央处理器 42 执行应用程序 45 a 和安装程序 45 c , 从而构建应用单元的软件 26 (参考图3)和安装单元 26 a. [0165] 此外,存储单元 45 存储用户注册的电话号码和电子邮件地址、假名和汉字转换程序以及其他信息(未显示)。 [0166] 显示单元 46 是在显示器上显示字符信息和图像的功能单元 21 (参考图2)。 [0167] 显示单元 46 在通话模式下选择性地显示用户注册的电话号码列表,并进一步显示通话信息,如基站发出的电波强度 5 , 用户输入的电话号码, 或呼叫伙伴电话号码的电话号码。 [0168] 在应用程序模式下,应用程序提供的应用程序屏幕 45 a 显示URL的输入栏、服务器装置发送的画面、邮件。 此外,显示价值的余额。 [0169] 经营单位 47 包括键盘 22 用于将用户的按键操作转换为电信号,并将转换后的信号输入CPU 42 . [0170] 声音输入输出单元 49 包括:麦克风 23 和演讲者 20, 转换通过麦克风接收到的声音 23 转换成模拟信号或将模拟信号转换为声音,并从扬声器输出声音 20 . [0171] 来自麦克风的用户语音转换为电信号,并将语音输入到电话功能单元 10 . 此外,从电话功能单元输出的声音信号 10 转换为声音并通过扬声器收听。 [0172] 数字信号处理单元 48 是将声音数据的模拟信号转换为数字信号或将数字信号快速转换为模拟信号的功能单元,并且包括例如DSP(数字信号处理器)。 此外,数字信号处理单元 48 压缩或解压缩声音数据。 [0173] 麦克风和扬声器使用模拟信号。 另一方面,电话功能单元的其他功能单元 10 使用数字信号。 然后,在输入声音信号后,数字信号处理单元 48 转换从麦克风输出的模拟信号,并进一步压缩转换后的信号。 在输出声音信号时,数字信号处理单元 48 解压缩电话功能单元输出的数字信号 10 并通过扬声器输出转换后的模拟信号。 [0174] 电子货币功能单元 12 包括:终端天线 35 ; 终端通信单元 31 ; IC控制单元 300 ; 和一个存储单元 36 . 元器件中,不含终端天线的元器件 35 被容纳在一个IC芯片上。 [0175] IC控制单元 300 和电话控制单元 200 通过中继单元连接 27 . [0176] 根据实施例,手机 7 包括电子货币功能单元 12 . 然而,本发明不限于此,电子货币功能单元 12 可以与手机分离 7 . [0177] 终端天线 35 与布置在读取器/写入器单元上的天线通信 8 a 电子货币终端 8 通过电波。 [0178] 终端通信单元 31 驱动终端天线 35 ,并进一步放大用于接收和传输的信号。 [0179] IC控制单元 300 包括:CPU 32 ; 只读存储器 33 ; 和一个内存 34 . [0180] 中央处理器 32 是中央处理单元,通过执行存储在ROM中的程序来执行数值处理 33 , 内存 34 , 和存储单元 36 . [0181] 只读存储器 33 是只读存储器,安排为可由 CPU 读取 32 . 只读存储器 33 存储,例如,操作系统,作为操作 CPU 的基本程序 32 . [0182] 在 IC 芯片的制造步骤中,特定的 IC 芯片 ID 被分配给 IC 芯片,并存储在 ROM 中 33 . [0183] IC 芯片 ID 在出厂后不会更改,一般情况下用户不会读取。 [0184] 内存 34 是一个可读/可写的内存,用于为CPU提供一个工作区 32 在操作 CPU 时 32 . [0185] 收纳单元 36 包括,例如,闪存或EEPROM,并且是布置成可由CPU读取/写入的存储介质 32 . 收纳单元 36 存储应用程序或其他数据。 [0186] 收纳单元 36 确保电子货币区 36 a 用于价值管理。 电子货币领域 36 a 形成这样的申请单位 26 a 将价值处理功能安装到电子货币功能单元 12 . [0187] 电子货币领域 36 a 包括一个程序区域 36 b 用于存储程序和日志数据区 36 c 用于存储日志数据。 [0188] 使能CPU的值处理程序 32 实现值处理函数安装到程序区 36 b . 中央处理器 32 执行值处理程序,从而构建值处理单元的软件 28 和日志数据存储单元 29 (参考图4)。 [0189] 节目区 36 b 存储从电子货币服务器发送的密钥信息和电子货币ID 2 , 在安装单元安装值处理函数时 26 a. [0190] 日志数据区 36 c 存储值处理的日志数据,形成日志数据存储单元 29 (参考图4)。 [0191] 存储单元中的应用程序 36 包括价值处理程序和作为通勤季票的季票程序(通过手机设置进站) 7 在检票口),并且有选择地驱动应用程序。 [0192] 如上所述,手机 7 具有值处理功能,因此用户不仅设置了手机 7 到电子货币终端 8 , 从而充值或使用该值进行结算, 还使用了电子货币服务器 2 ,从而收取价值或使用价值结算货币。 [0193] 接下来,对因特网进行说明 4 , 基站 5 , 和电话线网络 6 (参见图 1)。 [0194] 互联网 4 连接各种服务器设备和终端,并使用 TCP/IP(传输控制协议/互联网协议)或其他协议进行数据通信。 [0195] 互联网 4 一般采用分组通讯。 在分组通信中,数据以分组为单位被分割并被发送。 作为附件,包具有用于指定发送目的地的发送目的地指定信息和用于从发送目的地上的包恢复原始数据的恢复信息作为报头。 [0196] 数据接收端构造数据包并恢复原始数据。 [0197] 虽然未显示,但各种服务器设备已连接到互联网 4 . 用于提供各种服务的网站向服务器设备开放。 网站由 URL 指定。 [0198] 通过互联网接收或发送电子邮件 4 . 电子邮件帐户,作为电子邮件的发送目的地由电子邮件地址指定。 [0199] 电子邮件不仅发送和接收字符数据,还发送和接收图像数据、程序和作为附件的其他数据。 [0200] 基站 5 与手机通信 7 通过无线电波,为手机用户提供通话服务或上网服务 7 . [0201] 当用户接入基站时 5 从手机 7 在通话模式下,基站 5 将线路设置为电话线网络 6 用于呼叫操作。 当用户接入基站时 5 在应用模式中,基站 5 设置访问因特网使用Web服务器提供的服务的操作 4 . [0202] 参考图1,网上 4 和电话线网络 6 是独立安排的。 功能视图中使用独立排列,互联网 4 和电话线网络 6 包括物理上通用的传输介质。 [0203] 作为传输媒介,使用了各种电缆、光纤和经由人造卫星的线路。 [0204] 接着,对电子货币服务器进行说明 2 (参见图 1)。 [0205] 图6是表示电子货币服务器的功能结构的一例的概念图 2(提供服务器设备)。 电子货币服务器 2 上网 4 通过互联网线路,并进一步连接到电子货币终端 8 , 8 , 8 . . . . [0206] 电子货币服务器 2 包括:一个服务站点单元 56 ; 安装注册单元 57 ; 识别单元 58 ; 事务处理单元 59 ; 各种功能单元; 用户信息数据库 54 ; 交易信息数据库 55 ; 和其他各种数据库。 [0207] 根据该实施例,电子货币服务器 2 使用电子货币提供服务。 然而,本发明不限于此并且可以使用通过组合多个服务器设备获得的系统。 [0208] 例如,电子货币服务器的服务 2 可以通过将打开电子货币服务站点的Web服务器、用于识别用户的识别服务器、用于交易处理的交易处理服务器以及用于安装价值处理功能的安装服务器的服务器设备来提供。 [0209] 服务站点单位 56 是在因特网上以电子货币服务运营网站的功能单元 4 . [0210] 用户通过手机输入服务站点的URL 7 或者其他终端,从而访问服务站点,从而使用服务站点提供的各种服务。 [0211] 用户访问服务站点和电子货币服务器 2 在手机上显示主菜单屏幕时发送屏幕数据 7 . 主菜单屏幕可选择地显示由服务站点提供的服务的项目,并且用户选择期望的项目。 [0212] 提供各种服务项目,例如,不仅包括关于电子货币的使用,例如用户注册、用户注册信息的更改、价值的收取和使用价值的结算,还包括活动的新呈现、客户的接收 查询等 [0213] 用户注册后,同时安装数值处理功能。 [0214] 安装注册单元 57 是一个功能单元,进行用户注册信息的处理和值处理功能的安装操作,例如用户注册,值处理功能到手机的安装操作 7 、删除注册、注册内容的变更等。 [0215] 此外,安装注册单元 57 当用户选择用户注册信息上的项目时启动,例如主菜单屏幕上的用户注册或用户注册信息的更改。 [0216] 这里,对新用户登记的情况进行说明。 用户在主菜单屏幕上选择用户注册,然后选择安装注册单元 57 发送用于显示注册屏幕的屏幕数据到手机 7 . [0217] 注册屏幕有一栏用于输入注册信息,例如用户名、密码和发行者。 用户将信息输入到栏中,并将信息发送到电子货币服务器 2 . [0218] 安装注册单元 57 将信息存储到用户信息数据库 54 , 并转移到值处理函数的安装处理。 顺便提及,在价值处理功能的安装处理之前将使用条款呈现给用户,用户接受该条款,然后可以执行安装处理。 当不接受安装处理时,可以稍后执行。 [0219] 安装注册单元 57 与安装单元一起执行安装处理 26 a (参考图3)。 一、安装注册单元 57 从手机接收IC芯片ID 7 ,并将IC芯片ID存入用户信息数据库 54. IC芯片ID由申请单位读取 26 a 来自 IC 功能单元 12 a. [0220] 电子货币ID被使用并发送到手机 7 . 此外,电子货币ID存储在用户信息数据库中 54 . [0221] 安装注册单元 57 具有确保安全所必需的关键信息或其他秘密信息,并将秘密信息和必要的数据发送到手机 7 . [0222] 当用于安装值处理程序的程序被发送到手机时 7 来自电子货币服务器 2 ,程序发送到手机 7 . 手机的时候 7 提前有节目,节目不发。 [0223] 图7是表示存储在用户信息数据库中的用户信息的逻辑结构的例子的图。 54 . [0224] 用户信息包括电子货币ID 61 , 一个用户名 62 , 密码 63 , 发行人 64 , 一个 IC 芯片 ID 65 , 状态 66 , ETC。 [0225] 电子货币ID 61 是安装登记单位发行的电子货币ID 57 手机安装值处理功能后 7 . [0226] 尽管未显示,但电子货币服务器 2 具有用于对电子货币ID进行编号的编号表,以及电子货币ID 61 由安装注册单元从表中编号 57 . [0227] 用户名 62 是用户在注册屏幕上输入的名称。 [0228] 密码 63 是用于确认使用服务的用户是否为真实用户的信息,由用户在用户注册时设定。 [0229] 发行人 64 是用于指定在从电子货币服务器收取价值时由哪个发行者发行价值的信息 2 通过互联网 4 , 由用户在用户注册时从多个发行人中选择。 [0230] 尽管未显示,但电子货币服务器 2 有一个issuer master用于注册issuer,用户从issuer master中选择issuer。 [0231] 顺便提及,发行者表示发行价值的发行者,并且出于业务操作的原因存在多个发行者。 此外,发行的价值被任何电子货币终端使用 8 ,与发行人无关。 [0232] IC芯片ID 65 设置为电子货币服务器 2 从手机 7 安装价值处理功能后。 [0233] 根据该实施例,如上所述,IC芯片ID被注册,因此用户从移动电话被注册 7 . 未注册IC芯片ID时,用户从手机以外的其他终端注册 7 . [0234] 现状 66 为用户设置状态“未安装”和“已安装”。 [0235] 直到安装注册单元 57 接收用户注册并结束安装处理,安装注册单元 57 将状态设置为“未安装”。 安装过程结束后,安装注册单元 57 将状态更新为“已安装”。 [0236] 返回参考图6,识别单元 58 是注册用户使用服务站点时识别用户的功能单元。 [0237] 服务站点单位提供的服务 56 包括不需要识别的服务和需要识别的服务。 用户接收到标识,然后接收需要标识的服务。 [0238] 识别单位 58 发送,到手机 7,输入密码的画面数据(显示如图2所示的密码输入画面),接收用户从手机输入的密码、IC芯片ID、电子货币号码 7 . [0239] 信息核对到用户信息库中存储的信息 54 . 当信息与用户信息数据库中存储的信息相匹配时 54 ,用户被识别为普通用户。 [0240] 上述标识指定用户,从而提供针对该用户的服务。 [0241] 用户识别不需要所有的密码、IC芯片ID和电子货币ID。 密码、IC芯片ID和电子货币ID中的至少一种用于识别。 [0242] 事务处理单元 59 是将用户的交易记录记录到交易信息数据库中的功能单元 55 . [0243] 事务处理单元 59 记录,到交易信息数据库 55 、收费处理、结算等由手机进行的处理 7 或电子货币卡 15 . [0244] 图8是表示存储在交易信息数据库中的交易信息的逻辑结构的一个例子的图 55 . [0245] 交易信息包括电子货币ID 67 , 充电记录 68 , 结算记录 69 . [0246] 充电记录 68 记录进行充值操作的终端ID信息、充值日期、充值金额。 [0247] 电子货币ID 67 从手机读取 7 (或电子货币卡 15 ) 通过电子货币终端 8 . 在与电子货币服务器的通信中 2 通过互联网 4 , 电子货币 ID 67 从手机读取 7 通过电子货币服务器 2 . [0248] 例如,录音 71 记录图7中第一行的IC芯片ID,作为终端ID。 如上所述,在从电子货币服务器收取价值的情况下 2 通过互联网 4 , 手机的IC芯片ID 7 其中收费的价值被记录下来。 [0249] 记录 72 表示电子货币终端 8 由终端ID“347895”指定的终端收取相当于3,000日元的价值。 [0250] 结算记录 69 包括:结算终端; 结算日期和时间; 结算金额和价值。 例如录音 73 表示电子货币终端 8 终端 ID“2547657”指定的 2000 日元对应的金额结算。 [0251] 在使用电子货币服务器的价值结算中 2 通过互联网 4 , 手机的IC芯片ID 7 被记录为终端ID。 [0252] 交易信息中存储的交易信息 55 分析,从而将从发行者收取的现金按价值分配给结算货币的商店,以及非法电子货币卡 15 受到监控以收集用于业务的信息。 另外,同时记录用户购买的产品,从而进行市场调查等数据挖掘。 [0253] 顺便说一下,事务处理单元 59 不一定实时进行信息处理。 电子货币终端 8 存储交易信息并更新交易信息数据库 55 通过稍后接收交易信息。 因此,电子货币操作系统 1 无需访问电子货币服务器即可快速执行处理 2 在商店的收费操作或结算中。 [0254]根据该实施例,在电子货币操作系统中 1 ,用于结算的值存储在手机中 7 或电子货币卡 15 . 电子货币服务器 2 管理其交易信息。 [0255] 因此,电子货币服务器 2 在使用价值的结算中不实时访问,并在现场快速处理价值。 另外,交易信息暂时存储在电子货币终端的存储装置中 8 , 并被传送到电子货币服务器 2 在预定时间后,或者用于存储交易信息的存储介质被负责人收集。 [0256] 接着,对电子货币服务器的硬件结构的一例进行说明 2 (参见图 1)。 [0257] 如图9所示,电子货币服务器 2 包括:CPU 75 , 只读存储器 76 , 内存 77 , 通讯控制单元 78 ; 和存储单元 79 它们由总线连接 82 . [0258] 中央处理器 75 根据预定程序进行信息处理并控制整个电子货币服务器 2 . [0259] 只读存储器 76 是只读存储器,存储操作电子货币服务器的基本程序或参数 2 . [0260] 内存 77 是可读/可写内存,提供CPU的工作内存 75 或者加载并存储存储单元中存储的程序或数据 79 . [0261] 通信控制单元 78 (接收装置和发送装置)是与手机通信的功能单元 7 通过互联网 4 或基站 5 ,或与电子货币终端通信 8 通过通信线路。 [0262] 中央处理器 75 使用电子货币卡接收交易信息 15 或手机 7 从电子货币终端 8 通过通信控制单元 78 , 并与手机通信 7 并向手机充值 7 或使用手机中的金额进行结算 7 . [0263] 收纳单元 79 为硬盘或非易失性存储器,包括程序存储单元 80 用于存储各种程序和数据存储单元 81 用于存储数据。 [0264] 程序存储单元 80 存储操作系统,作为电子货币服务器运行的基本程序 2 ,用于操作服务站点的服务站点程序,用于注册用户或安装价值处理功能的注册程序,用于识别用户的识别程序,用于执行交易的交易程序等。 [0265] 中央处理器 75 执行程序,因此,服务站点单元 56 , 安装注册单元 57 , 识别单位 58 , 和事务处理单元 59 (参考图5)由软件配置。 [0266] 数据存储单元 81 存放用户信息的数据库 54 、交易信息数据库 55 、编号表、发行人主数据库和另一个数据库。 [0267] 接着,对电子货币终端进行说明 8 (参见图 1)。 [0268] 电子货币终端 8 是与电子货币功能单元通信的终端设备 12 手机的 7 通过无线电波,并操作值处理单元 28 (图 4)。 [0269] 电子货币终端 8 安装在便利店收银台,用户设置手机 7 到电子货币终端的预定部分 8 (读写器单元 8 a ), 从而对价值进行计费和结算。 [0270] 以下,对电子货币终端之间的通信进行说明 8 和手机 7 . 电子货币终端 8 执行与电子货币卡相同的处理 15 . [0271] 读写器单元 8 a 通过使用其中的天线进行近距离无线电通信,并通过无线电波从/向终端天线接收/发送数据 35 在电子货币功能单元 12 . [0272] 开始与手机通信时 7 , 电子货币终端 8 从电子货币功能单元读取关键信息 12 (向值处理单元发送读取关键信息的命令 28 并接收值处理单元发送的密钥信息 28 ). 将密钥信息与电子货币终端的密钥信息进行比对 8 然后检查电子货币功能单元是否 12 是有规律的。 [0273] 电子货币终端 8 确定电子货币功能单元 12 是有规律的,然后向值处理单元输入写入命令或减法命令 28 ,从而启用值处理单元 28 执行值处理。 [0274] 电子货币终端 8 在网络上连接到电子货币服务器 2 通过数字电话线等通信线路发送至电子货币服务器 2 , 对手机的计费结算信息 7 . [0275] 发送到电子货币服务器的信息 2 通过电子货币终端 8 是指定电子货币终端之间的处理内容的信息 8 和电子货币功能单元 12 ,例如,终端ID(用于识别电子货币终端的ID 8 )、会员店ID、电子货币编号、充值金额、结算金额、充值或结算日期时间。 [0276] 基于该信息,电子货币服务器 2 确认与存储在电子货币功能单元中的价值相对应的货币数量 12 以及哪个电子货币终端 8 以及哪个电子货币功能单元 12 收取或结算多少价值。 [0277] 电子货币终端 8 对电子货币卡进行充值和结算 15 ,这将在后面描述,类似于电子货币功能单元 12 . [0278] 根据该实施例,电子货币终端 8 安装在零售商店并执行计费和价值结算。 [0279] 此外,电子货币终端 8 安装在自动售货机、车站检票口、阶梯井、出租车、剧院入口等用户的收费处。 在这种情况下,电子货币终端 8 仅供结算即可安装。 [0280] 此外,在公共场所或公园等人多的地方,电子货币终端 8 for charge only 可以安装充电值。 [0281] 电子货币终端之间的网络连接 8 和电子货币服务器 2 一般是数字电话线。 此外,电子货币终端之间的网络连接 8 和电子货币服务器 2 由特定线路实现。 [0282] 可以在电子货币终端附近安装无线终端 8 并且可以通过电子货币终端之间的无线电线路实现连接 8 和一个无线终端。 由于一个无线终端与多个电子货币终端通信 8通过无线电波,与为个人电子货币终端安装线路相比,成本可能会降低 8 . 通过这种结构,有利的是,多个电子货币终端 8 安装在自动售货机上的设备被统一管理。 [0283] 此外,可以将存储介质布置到电子货币终端 8 , 存储电子货币终端之间通信处理内容的数据 8 和手机 7 ,负责人可以收集存储介质。 [0284] 该结构在安装电子货币终端的情况下是有利的 8 到移动成员,例如公共汽车、出租车、飞机或轮船。 [0285] 接着,对电子货币卡进行说明 15 (参见图 1)。 [0286] 电子货币卡 15 由塑料外壳中的终端天线和 IC 芯片组成。 [0287] 图10是表示电子货币卡的硬件构成例的图 15 . [0288] 电子货币卡 15 包括:IC芯片 112 ; 和一个中央处理器 132 , 只读存储器 133 , 一个内存 134 , 一个存储单元 136 , 和一个终端通信单元 131 安装在IC芯片上 112 . 电子货币卡 15 为IC芯片供电 112 ,还包括终端天线 135 用于接收和发送信号。 [0289] 电子货币卡 15 设置在电子货币终端的预定位置 8 , 类似于电子货币功能单元 12 ,从而在非接触状态下充电和稳定值。 [0290] 在这种情况下,电子货币终端发出的无线电波 8 被接收,并且终端天线 135 电子货币卡 15 产生电力,从而提供驱动IC芯片的电力 112 . 如上所述,终端天线 135 产生电力并从/向电子货币终端接收和发送数据 8 . [0291] 自电子货币功能单元 12 手机的 7 从手机的电源接收电力 7 , 电子货币功能单元的IC芯片 12 从电子货币终端获取电源 8 或手机电源 7 . [0292] 一般来说,当手机 7 开机时,电源取自手机电池 7 . 手机的时候 7 关闭时,从电子货币终端获取电源 8 . [0293] 中央处理器 132 , 只读存储器 133 , 内存 134 , 存储单元 136 , 和终端通信单元 131 安装在IC芯片上 112 具有与CPU相同的功能 32 , 只读存储器 33 , 内存 34 , 存储单元 34 , 和终端通信单元 31 安装在电子货币功能单元上 12 . [0294] 即存储单元 136 存储值处理程序和CPU 132 执行值处理程序,从而通过软件配置值处理单元。 收纳单元 136 有一个日志数据存储单元。 [0295] 值处理单元的操作设置了电子货币卡 15 到电子货币终端的读取器/写入器单元 8 ,从而收取价值并使用价值进行结算。 [0296] 接下来,说明在电子货币操作系统中安装价值处理功能的情况下的组件的操作 1 参考图11所示的参考数字具有上述结构( a ). [0297] (1) 用户购买手机后启动应用模式 7 , 从而使用应用程序单元 26. 然后,电子货币服务器的服务站点的URL 2 被输入到申请单元 26 , 和服务站点单元 56 电子货币服务器 2 从手机访问 7 . [0298] 相反,服务站点单元 56 发送,到手机 7 , 用于显示主菜单屏幕的屏幕数据。 [0299] 图 12( a )是表示显示在显示器上的主菜单画面的例子的图 21 (参考图2)的手机 7 . [0300] 参考图 12( a ), 电子货币服务器提供的服务 2 显示主菜单屏幕上的每个项目,用户通过操作键盘选择项目 22 . 在这里,“1。 注册用户”被选中。 [0301] (2) 用户选择项目“1. 注册用户”,然后安装注册单元 57 在电子货币服务器中启动 2 (图 11( a )). 一、电子货币服务器 2 将显示注册画面的画面数据发送至手机 7 . [0302] 图 12( b )是表示显示在显示器上的登记画面的例子的图 21 . [0303] 注册屏幕具有用于输入名称的栏、用于输入设置密码的栏、用于选择发行者的栏(未示出)和另一个输入栏。 通过操作键盘在注册屏幕上输入必要的项目 22 . [0304] 输入必要的项目后,用户点击显示在显示器上的发送按钮(未示出) 21 . 因此,输入项目被发送到电子货币服务器 2 从手机 7 . [0305] 关于发行者的选择,在显示器上显示发行者选择屏幕 21 , 用户任意选择显示屏上显示的发行人 21 . [0306] 在电子货币服务器中 2 , 安装注册单元 57 存储从手机接收到的注册信息 7 到用户信息数据库 54 , 并注册用户。 [0307] 注册用户后,安装注册单元 57 发送用于显示 use 子句的屏幕数据。 use子句中有install选择项供用户选择手机是否安装值处理功能 7 . 当用户同意使用条款时,即安装值处理功能。 当用户不同意使用条款时,不安装数值处理功能。 [0308] 图 12( c )是显示在显示器上显示的安装选择项目的一个例子的图 21 . [0309] 用户选择“是”和“否”中的任何一个。 选择“是”时,将注册用户,然后开始值处理功能的安装操作。 选择“NO”时,安装操作不会开始。 选择“否”时,电子货币服务器 2 稍后访问并执行安装操作。 [0310] (3) 当用户选择“YES”时,安装注册单元 57 开始安装过程。 [0311] 之后,安装注册单元 57 与安装单元通信 26 a 并同时进行安装处理。 [0312] 一、在手机中 7 , 安装单位 26 a (参考图3)确保电子货币区 36 a 在存储单元 36 (参考图5),并形成程序区 36 b 和日志数据区 36 c . 当电子货币区 36 a 事先保证,此步骤省略。 [0313] 然后,安装单元 26 a 将值处理程序安装到程序区 36 b. [0314] 此外,安装单元 26 a 读取IC芯片ID并将IC芯片ID发送至电子货币服务器 2 . [0315] 在电子货币服务器中 2 , 安装注册单元 57 从手机接收IC芯片ID 7 ,并将IC芯片ID存入用户信息数据库 54 . 此外,电子货币服务器 2 发行电子货币ID并将电子货币ID存储到用户信息数据库中 54 . [0316] 随后,安装注册单元 57 将编号的电子货币ID和密钥信息等秘密信息发送到手机 7 . [0317] 在手机里 7 , 安装单位 26 a 写,到程序区 36 b , 从电子货币服务器接收到的电子货币ID 2 以及秘密信息,例如关键信息。 [0318] 如上所述,电子货币服务器 2 和安装单元 26 a 协同安装值处理功能到IC功能单元 12 a. [0319] 安装过程中,安装单位 26 a 显示如图12所示的画面( d ) 在显示屏上 21 . [0320] 安装处理结束后,参见图12( e ), 电子货币 ID 显示在显示器上 21 . [0321] 电子货币ID用于用户服务。 此外,在充值或使用该价值进行结算的情况下,其信息和电子货币ID被记录并用于价值管理。 [0322] 图 11( b )是表示电子货币功能单元之间关系的图 12 , 电子货币终端 8 , 和电子货币服务器 2 安装值处理功能后。 [0323] 参考图 11( b ), 值处理单元 28 直接接收来自电子货币终端的访问 8 . 此外,值处理单元 28 接收来自电子货币服务器的访问 2 通过申请单位 26 和中继单元 27 . [0324] 值处理单元 28 从电子货币终端接收各种命令 8 和电子货币服务器 2 并执行命令,并处理日志数据存储单元中存储的值 29 . [0325] 说明从电子货币终端充值的操作 8 到电子货币功能单元 12 如上参照图13中的参考数字形成的。 [0326] (1) 一、手机 7 设置为读写器单元 8 a 电子货币终端 8 . 然后,电子货币功能单元之间开始通信 12 和电子货币终端 8 . [0327] 电子货币终端 8 请求将密钥信息传输到值处理单元 28 . 作为响应,值处理单元 28 从程序区读取关键信息 36 b (参考图5)并将密钥信息发送到电子货币终端 8 . [0328] 电子货币终端 8 通过使用从值处理单元接收到的密钥信息来识别 28 , 是否为电子货币功能单元 12 是有规律的。 此外,电子货币终端 8 从价值处理单元读取并记录电子货币ID 28 . [0329] (2) 电子货币终端 8 接收指定充值金额的写入信息的输入。 例如,负责人从设置到电子货币终端的输入设备输入写入信息 8 . [0330] (3) 电子货币终端 8生成对输入的货币对应的价值进行充值的写入指令,并将写入指令发送给价值处理单元 28 . [0331] (4) 值处理单元 28 从电子货币终端接收写入命令 8 并执行命令。 然后,值处理单元 28 将与输入的金额对应的金额添加到日志数据存储单元中存储的当前余额值中 29 ,并更新日志数据。 [0332] 作为上述处理的结果,价值被充入电子货币功能单元 12 从电子货币终端 8 . [0333] 类似地执行使用该值的结算。 即电子货币终端 8 从电子货币功能单元接收密钥信息 12 , 标识电子货币功能单元 12 ,生成结算对应金额的减法命令,并将该命令发送给值处理单元 28 . 值处理单元 28 执行命令并减去 value 的余额。 [0334] 写命令和减命令被输入到值处理单元 28 来自电子货币服务器 2 通过申请单位 26 和中继单元 27 ,价值被收取或结算。 在这种情况下,申请单位 26 读取密钥信息并将密钥信息发送给电子货币服务器 2 . 然后,电子货币服务器 2 识别关键信息。 [0335] 下面说明数值处理功能在手机上的安装顺序 7 参考图14所示的流程图。 [0336] 一、在手机中 7 ,电话功能单元 10 设置为应用模式,电子货币服务器的服务站点 2 被访问(在步骤 3 ). [0337] 相反,在电子货币服务器中 2 、服务现场单位 56 发送,到手机 7 ,用于显示主菜单屏幕的屏幕数据(在步骤 50 ). [0338] 手机 7 接收屏幕数据,应用单元 26 在显示屏上显示主菜单屏幕 21 通过使用屏幕数据。 [0339] 用户在主菜单屏幕上选择各种项目。 在这里,用户选择用户注册(步骤 5 ). [0340] 相反,在电子货币服务器中 2 , 安装注册单元 57 启动并发送到电子货币服务器 2 ,用于显示注册屏幕的屏幕数据(在步骤 55 ). [0341] 手机 7 接收屏幕数据,应用单元 26 在显示器上显示注册屏幕 21 通过使用屏幕数据。 [0342] 用户从注册屏幕输入注册所需的信息,例如姓名、密码和选择的发行者,并点击显示在注册屏幕上的发送按钮。 那么,申请单位 26 发送到电子货币服务器 2 ,输入的注册信息(步骤 10 ). [0343] 电子货币服务器 2 接收手机发送的注册信息 7 . 安装注册单元 57 搜索用户信息数据库 54 通过使用接收到的注册信息,并检查用户是否注册(步骤 60 ). 当用户的item存在且状态为“正在安装”时(Y;步骤中 60 ), 向手机发送用户注册信息 7 然后处理返回到步骤 50 . [0344] 当用户信息数据库 54 不包含该用户或当用户信息数据库的项目 54包括用户的item但现有状态为“未安装”(默认是在安装操作时造成的,然后再次执行安装操作)(N;在步骤 60 ), 用户注册到用户信息数据库 54 (在步骤 65 ). 然后,将用户项的状态设置为“未安装”。 [0345] 接下来,安装注册单元 57 发送使用条款数据,用于显示使用条款至手机 7 (在步骤 70 ). [0346] 手机 7 接收有关使用条款和申请单位的数据 26 在显示器上显示 use 子句 21 通过使用 use 子句上的数据。 [0347] 用户阅读使用条款,选择用户是同意使用条款并安装价值处理功能还是用户不同意使用条款不安装价值处理功能,并将选择结果发送给电子货币 服务器 2 (在步骤 15 ). [0348] 电子货币服务器 2 收到选择结果。 当用户不同意使用条款时(N;在步骤 75 ), 安装注册单元 57 不进行安装处理和电子货币服务器的状态 2 返回步骤 50 . [0349] 当用户同意使用条款时(Y;在步骤 75 ), 安装注册单元 57 开始安装过程,与安装单元通信 26 a 手机的 7 , 与安装单元一起进行值处理函数的安装处理 26 a (按步骤 80 和 20 ). [0350] 即安装注册单元 57 发行电子货币ID并将密钥信息和电子货币ID发送到手机 7 . 安装单位 26 a 读取IC芯片ID并将IC芯片ID发送至电子货币服务器 2 . [0351] 手机的时候 7 从电子货币服务器下载 2 ,值处理程序,安装注册单元 57 将价值处理程序发送到电子货币服务器 2 . [0352] 安装注册单元 57 存储从手机接收到的IC芯片ID 7 和手机的电子货币ID号 7 到用户信息数据库中用户的项目 54 . [0353] 安装单位 26 a 使用密钥信息和电子货币ID安装价值处理程序。 [0354] 手机 7 结束值处理程序,然后是应用程序单元 26 在显示屏上显示安装结束消息 21 并且用户检查消息。 用户查看消息,然后是应用单元 26 向电子货币服务器发送指示安装操作结束的通知 2 (在步骤 25 ). [0355] 电子货币服务器 2 收到结束通知,安装注册单元 57 更新用户信息数据库中用户项目的状态 54 并确定值处理函数的安装操作(在步骤 85 ). [0356] 当在安装值处理功能期间导致默认时,执行以下处理。 [0357] 在开始安装过程之前(步骤之前 20 和 80 ),不进行恢复处理,电子货币服务器 2 再次发送,到手机 7 , 用于显示主菜单屏幕的屏幕数据。 [0358] 在开始安装处理后发生默认时,执行恢复处理并且安装处理从处理中断开始。 [0359] 上述电子货币操作系统具有以下优点 1根据本发明。 [0360] (1)由于关键信息和另一个信息被发送到手机 7 直接从电子货币服务器 2 安装价值处理功能后,安全的秘密信息和其他秘密信息不会发送给外包合作伙伴,信息易于管理。 [0361] (2) 手机 7 不给IC功能单元安装价值处理功能就卖给用户 12 a (参考图3)。 因此,降低了安装操作的成本。 [0362] (3) 与电子货币卡相同 15 , 手机 7 安装价值处理功能后,对价值进行充值或使用价值进行结算。 此外,从电子货币服务器中充值并使用该价值进行结算 2 . [0363] 上面已经描述了根据本发明的实施例。 然而,本发明不限于所描述的实施例并且可以根据权利要求的范围进行修改。 [0364] 例如,具有电子货币功能单元的移动终端设备 12 不限于手机 7 并且可以是可以访问电子货币服务器的移动电子设备,例如PDA(个人数字助理)或袖珍铃 2 通过网络。 [0365] 根据该实施例,IC芯片具有与电子货币卡中的IC芯片相同的功能 15 安装在手机中 7 . 硬件结构不限于此。 例如,值处理程序安装在存储单元中 45 (参考图5)在电话功能单元 10 , 并且可以被 CPU 执行 42 . 在这种情况下,电话功能单元 10 具有电子货币功能单元的功能 12 因此无需在手机中安装IC芯片 7 .(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: BRPI0408141A(String), BRPI0408141A2(String), CA2518209A1(String), CN1759414A(String), EP1610245A1(String), EP1610245A4(String), HK1090455A(String), IN2161CHENP2005A(String), JP2004272561A(String), JP2004272561A5(String), JP2006018847A5(String), KR1020050111340A(String), RU2005131017A(String), TW200423691A(String), US20060100933A1(String), US7720717B2(String), WO2004079616A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: BRPI0408141A(String), BRPI0408141A2(String), CA2518209A1(String), CN1759414A(String), EP1610245A1(String), EP1610245A4(String), HK1090455A(String), IN2161CHENP2005A(String), JP2004272561A(String), JP2004272561A5(String), JP2006018847A5(String), KR1020050111340A(String), RU2005131017A(String), TW200423691A(String), US20060100933A1(String), US7720717B2(String), WO2004079616A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.960 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7720717B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.994 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:12.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), BRPI0408141A(String), BRPI0408141A2(String), CA2518209A1(String), CN1759414A(String), EP1610245A1(String), EP1610245A4(String), HK1090455A(String), IN2161CHENP2005A(String), JP2004272561A(String), JP2004272561A5(String), JP2006018847A5(String), KR1020050111340A(String), RU2005131017A(String), TW200423691A(String), US20060100933A1(String), US7720717B2(String), WO2004079616A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), BRPI0408141A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), BRPI0408141A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.086 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.086 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.086 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), CA2518209A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), CN1759414A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), EP1610245A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.191 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.191 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), EP1610245A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.226 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), HK1090455A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.261 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.261 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.261 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), IN2161CHENP2005A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), JP2004272561A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), JP2004272561A5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), JP2006018847A5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), KR1020050111340A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), RU2005131017A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), TW200423691A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), US20060100933A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), US7720717B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271662(Integer), WO2004079616A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7720717B2(String), US7720717B2(String), 1274112000(Integer), 271662(Integer), 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.646 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY CORPORATION(String), 索尼公司(String), 索尼公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185980(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 185980(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.831 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185980(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 2(Integer), 185980(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.918 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.918 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.918 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.953 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:13.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费 | 权利转移(String), 2(Integer), 185980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20170111495A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Control method for mobile terminal antenna, and mobile terminal(String), 一种移动终端天线的控制方法及移动终端(String), US20170111495A1(String), Embodiments provide a control method for a mobile terminal antenna, and a mobile terminal. By means of the control method for a mobile terminal antenna, and the mobile terminal, the mobile terminal can determine, according to a specific application scenario, for example, information such as a service that needs to be executed and an environment sensed, a quantity of antennas that should be enabled.(String), 实施例提供了一种移动终端天线的控制方法及移动终端。 本发明的移动终端天线的控制方法及移动终端,移动终端可以根据具体的应用场景,例如需要执行的业务、感知的环境等信息,确定数量。 应启用的天线数量。(String), US15/395022(String), 1483027200(Integer), US20170111495A1(String), 1492617600(Integer), 美国(String), 2(Integer), CN(String), 8(Integer), 0(Integer), 24(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185981(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ef9b7e9b1cfa449fb39e598cf3386d01.png(String), 185981(Integer), ef9b7e9b1cfa449fb39e598cf3386d01.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Control method for mobile terminal antenna, and mobile terminal(String), 一种移动终端天线的控制方法及移动终端(String), US20170111495A1(String), Embodiments provide a control method for a mobile terminal antenna, and a mobile terminal. By means of the control method for a mobile terminal antenna, and the mobile terminal, the mobile terminal can determine, according to a specific application scenario, for example, information such as a service that needs to be executed and an environment sensed, a quantity of antennas that should be enabled.(String), 实施例提供了一种移动终端天线的控制方法及移动终端。 本发明的移动终端天线的控制方法及移动终端,移动终端可以根据具体的应用场景,例如需要执行的业务、感知的环境等信息,确定数量。 应启用的天线数量。(String), US15/395022(String), 1483027200(Integer), US20170111495A1(String), 1492617600(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 8(Integer), 0(Integer), \20230420\ef9b7e9b1cfa449fb39e598cf3386d01.png(String), 24(Integer), 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.856 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 1. A method comprising:acquiring, by a mobile terminal, a start command of a service;determining, by the mobile terminal according to the start command, a quantity of antennas to be enabled for the service; andcontrolling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal, wherein the quantity of enabled antennas of the mobile terminal equals the quantity of antennas to be enabled for the service.(String), 1.一种方法包括:移动终端获取业务启动命令;移动终端根据启动命令确定该业务需要启用的天线数量;和移动终端控制移动终端启用的天线数量,其中,移动终端启用的天线数量等于业务要启用的天线数量。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 2. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, a service signal of the service, wherein the service signal is the start command;prompting, by the mobile terminal, a user whether to start the service; andcontrolling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the service signal has been received, in response to the mobile terminal not receiving, within a preset time, an operation instruction entered by the user, or determining that the operation instruction entered by the user and received within a preset time is not an instruction to start the service.(String), 2.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收业务的业务信号,业务信号为启动命令;移动终端提示用户是否开启服务;和响应于移动终端在预设时间内没有接收到用户输入的操作指令,移动终端控制移动终端启用的天线数量恢复到接收到业务信号之前的天线数量用户,或者确定在预设时间内接收到的用户输入的操作指令不是启动服务的指令。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 3. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, a service signal of the service;prompting, by the mobile terminal, a user whether to start the service;receiving, by the mobile terminal, an operation instruction entered by the user; andsing the operation instruction as the start command in response to the mobile terminal determining that the operation instruction is an instruction to start the service.(String), 3.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收业务的业务信号;移动终端提示用户是否开启服务;移动终端接收用户输入的操作指令;和响应于移动终端确定操作指令为启动业务的指令,将操作指令作为启动命令发出。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 4. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, an operation instruction relevant to the service, wherein the operation instruction has been entered by a user, wherein the operation instruction relevant to the service is the start command.(String), 4.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收与该业务相关的操作指令,该操作指令是用户输入的,该与该业务相关的操作指令为启动命令。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 5. The method according to claim 4, further comprising:prompting, by the mobile terminal, the user to enter a subsequent operation instruction; andcontrolling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the operation instruction relevant to the service is received, in response to the mobile terminal not receiving, within a preset time, the subsequent operation instruction entered by the user, or determining that the subsequent operation instruction received within the preset time is not an instruction to start the service.(String), 5.根据权利要求4所述的方法,还包括:移动终端提示用户输入后续操作指令;和响应于移动终端在预设时间内没有接收到后续的业务相关操作指令,移动终端控制移动终端启用的天线数量恢复到接收到业务相关操作指令之前的天线数量用户输入的操作指令,或者确定后续在预设时间内收到的操作指令不是启动服务的指令。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 6. The method according to claim 1, wherein acquiring, by the mobile terminal, the start command of the service comprises:receiving, by the mobile terminal, an operation instruction relevant to the service, wherein the operation instruction has been entered by a user;prompting, by the mobile terminal according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction;receiving, by the mobile terminal, a subsequent operation instruction to start the service; andusing the subsequent operation instruction to start the service as the start command after receiving the subsequent operation instruction to start the service.(String), 6.根据权利要求1所述的方法,其中移动终端获取服务的启动命令包括:移动终端接收用户输入的与业务相关的操作指令;移动终端根据与业务相关的操作指令提示用户输入后续操作指令;移动终端接收后续启动服务的操作指令;和接收到启动服务的后续操作指令后,将启动服务的后续操作指令作为启动命令。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 7. A method comprising:acquiring, by a mobile terminal, relevant information, wherein the relevant information comprises information selected from the group consisting of: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal;determining, by the mobile terminal according to the relevant information, a quantity of antennas to remain enabled; andcontrolling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal, wherein the quantity of enabled antennas corresponds to the relevant information.(String), 7.一种方法包括:移动终端获取相关信息,其中,相关信息包括选自以下信息:与移动终端相关的环境信息、移动终端的相关参数、移动终端当前的工作模式;移动终端根据相关信息确定保持开启的天线数量;和移动终端控制移动终端启用的天线数量,启用的天线数量与相关信息对应。8、如权利要求7所述的方法,所述移动终端根据相关信息确定保持开启的天线数量之前,还包括:移动终端将相关信息与预设条件进行比对;和判断相关信息是否满足预设条件;其中,所述预设条件为响应于所述相关信息为与所述移动终端相关的环境信息,且所述环境信息为所述移动终端辐射范围内的用户而预设的生物信息;其中,预设条件为响应于环境信息为移动终端所在场景而预设的限制场景;其中,预设条件大于预设辐射阈值响应于相关信息为移动终端的相关参数,相关参数为移动终端的辐射强度;其中,预设条件小于预设信号阈值响应于相关参数为移动终端的信号强度;和其中,预设条件为响应于相关参数为移动终端的当前工作模式而预设的工作模式。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 8. The method according to claim 7, before determining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled, further comprising:comparing, by the mobile terminal, the relevant information with a preset condition; anddetermining whether the relevant information meets the preset condition;wherein the preset condition is preset biological information in response to the relevant information being the environment information relevant to the mobile terminal, and the environment information being a user within radiation of the mobile terminal;wherein the preset condition is a preset limitation scenario in response to the environment information being a scenario in which the mobile terminal is located;wherein the preset condition is greater than a preset radiation threshold in response to the relevant information being the relevant parameter of the mobile terminal, and the relevant parameter being a radiant intensity of the mobile terminal;wherein the preset condition is less than a preset signal threshold in response to the relevant parameter being a signal strength of the mobile terminal; andwherein the preset condition is a preset work mode in response to the relevant parameter being the current work mode of the mobile terminal.(String), 9.根据权利要求8所述的方法,其中响应于环境信息为移动终端辐射范围内的用户,该方法还包括:移动终端将第三方设备发送的用户特征与预设的生物信息进行比对,或移动终端解析用户输入的操作指令或获取的用户信息,获取用户特征,移动终端将用户特征与预设的生物信息进行比对,其中,用户信息由用户或由第三方设备发送;判断用户特征是否符合预设生物信息;和移动终端根据相关信息确定用户特征满足预设生物信息后保持开启的天线数量。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 9. The method according to claim 8, wherein in response to the environment information being the user within the radiation of the mobile terminal, the method further comprises:comparing, by the mobile terminal, a user feature sent by a third-party device with the preset biological information, orparsing, by the mobile terminal, an operation instruction entered by the user or acquired user information, to acquire a user feature, and comparing, by the mobile terminal, the user feature with the preset biological information, wherein the user information is entered by the user or sent by a third-party device;determining whether the user feature meets the preset biological information; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the user feature meeting the preset biological information.(String), 10.根据权利要求8所述的方法,其中响应于环境信息为移动终端所在的场景,该方法还包括:移动终端将场景信息与预设的限制场景进行比较,判断场景信息是否满足预设的限制场景,其中,场景信息是通过移动终端上的传感器或摄像头获取的;和移动终端根据相关信息确定满足预设限制场景的场景信息响应的保持启用的天线数量。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 10. The method according to claim 8, wherein in response to the environment information being the scenario in which the mobile terminal is located, the method further comprises:comparing, by the mobile terminal, scenario information with the preset limitation scenario, and determining whether the scenario information meets the preset limitation scenario, wherein the scenario information is acquired using a sensor or a camera on the mobile terminal; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the scenario information meeting the preset limitation scenario.(String), 11.根据权利要求8所述的方法:其中响应于相关参数为移动终端的辐射强度,该方法还包括:移动终端将检测到的移动终端的辐射强度与预设的辐射阈值进行比较,判断移动终端的辐射强度是否大于预设的辐射阈值;和响应于移动终端的辐射强度大于预设辐射阈值,移动终端根据相关信息确定保持开启的天线数量;或者其中,响应于相关参数为移动终端的信号强度,该方法还包括:移动终端将检测到的移动终端信号强度与预设信号门限值进行比较,判断移动终端信号强度是否小于预设信号门限值;和移动终端根据相关信息确定响应于移动终端的辐射强度大于预设辐射阈值而保持开启的天线数量。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 11. The method according to claim 8:wherein in response to the relevant parameter being the radiant intensity of the mobile terminal, the method further comprises:comparing, by the mobile terminal, a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determining whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled, in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold; orwherein, in response to the relevant parameter being the signal strength of the mobile terminal, the method further comprises:comparing, by the mobile terminal, a detected signal strength of the mobile terminal with the preset signal threshold, and determining whether the signal strength of the mobile terminal is less than the preset signal threshold; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold.(String), 12.根据权利要求8所述的方法,其中响应于相关参数为移动终端当前的工作模式,该方法还包括:移动终端将移动终端当前的工作模式与预设的工作模式进行比较,判断当前的工作模式是否满足预设的工作模式,其中当前的工作模式是用户设置的,或者当前的工作模式为移动终端响应于移动终端检测到移动终端剩余电量低于预设电量阈值而设置;和移动终端根据相关信息,确定移动终端当前工作模式满足预设工作模式时,保持开启的天线数量。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 12. The method according to claim 8, wherein in response to the relevant parameter being the current work mode of the mobile terminal, and the method further comprises:comparing, by the mobile terminal, the current work mode of the mobile terminal with a preset operation mode, and determining whether the current work mode meets the preset work mode, wherein the current work mode is set by the user, or the current work mode is set by the mobile terminal in response to the mobile terminal detecting that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; anddetermining, by the mobile terminal according to the relevant information, the quantity of antennas to remain enabled in response to the current work mode of the mobile terminal meeting the preset work mode.(String), 13.移动终端,包括:处理器;和一种非暂时性计算机可读存储介质,存储由处理器执行的程序,该程序包括以下指令:获取服务的启动命令;根据启动命令确定该业务需要启用的天线数量;和控制移动终端启用的天线数量为业务确定启用的天线数量。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 13. A mobile terminal, comprising:a processor; anda non-transitory computer readable storage medium storing a program for execution by the processor, the program including instructions to:acquire a start command of a service;determine, according to the start command, a quantity of antennas to be enabled for the service; andcontrol a quantity of enabled antennas of the mobile terminal to be the quantity of antennas determined to be enabled for the service.(String), 14.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收服务的服务信号,服务信号为启动命令;提示用户是否启动服务;和响应于确定移动终端在预设时间内没有接收到用户输入的操作指令,控制移动终端使能的天线数量恢复到接收到业务信号之前的天线数量,或者移动终端在预设时间内接收到的用户输入的操作指令不是启动服务的指令。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 14. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive a service signal of the service, wherein the service signal is the start command;prompt a user whether to start the service; andcontrol the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the service signal is received, in response to determining that the mobile terminal does not receive, within a preset time, an operation instruction entered by the user, or that an operation instruction entered by the user and received by the mobile terminal within the preset time is not an instruction to start the service.(String), 15.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收服务的服务信号;提示用户是否启动服务;接收用户输入的操作指令;确定该操作指令为启动服务的指令;和在确定操作指令为启动服务的指令后,将该操作指令作为启动命令。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 15. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive a service signal of the service;prompt a user whether to start the service;receive an operation instruction entered by the user;determine that the operation instruction is an instruction to start the service; anduse the operation instruction as the start command after determining that the operation instructions is an instruction to start the service.(String), 16.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收用户输入的与业务相关的操作指令,其中,与业务相关的操作指令为启动命令。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 16. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive an operation instruction relevant to the service and entered by a user, wherein the operation instruction relevant to the service is the start command.(String), 17.根据权利要求16所述的移动终端,其中该说明还包括以下说明:提示用户输入后续操作指令;和响应于确定移动终端在预设时间内没有接收到后续输入的操作指令,控制移动终端使能的天线数量恢复到接收到与业务相关的操作指令之前的天线数量用户输入的移动终端在预设时间内接收到的后续操作指令不属于业务启动指令。(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 17. The mobile terminal according to claim 16, wherein the instructions further comprise instructions to:prompt the user to enter a subsequent operation instruction; andcontrol the quantity of enabled antennas of the mobile terminal to revert to a quantity of antennas before the operation instruction relevant to the service is received, in response to determining that the mobile terminal does not receive, within a preset time, a subsequent operation instruction entered by the user, or that a subsequent operation instruction entered by the user and received by the mobile terminal within the preset time is not an instruction to start the service.(String), 18.根据权利要求13所述的移动终端,其中该说明还包括以下说明:接收用户输入的与服务相关的操作指令;根据与服务相关的操作指令,提示用户输入后续操作指令;确定移动终端接收到后续启动服务的操作指令;和在确定移动终端接收到后续操作指令后,将后续操作指令启动服务作为启动命令。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 18. The mobile terminal according to claim 13, wherein the instructions further comprise instructions to:receive an operation instruction relevant to the service and entered by a user;prompt, according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction;determine that the mobile terminal receives a subsequent operation instruction to start the service; anduse the subsequent operation instruction to start the service as the start command after determining that the mobile terminal receives the subsequent operation instruction.(String), 19.移动终端,包括:处理器;和一种非暂时性计算机可读存储介质,存储由处理器执行的程序,该程序包括以下指令:获取相关信息,其中,所述相关信息包括从以下组中选择的信息:与移动终端相关的环境信息、移动终端的相关参数和移动终端当前的工作模式;根据相关信息确定保持启用的天线数量;和控制移动终端启用的天线数量为确定保持启用的天线数量。(String), 1(Integer), 17(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 19. A mobile terminal, comprising:a processor; anda non-transitory computer readable storage medium storing a program for execution by the processor, the program including instructions to:acquire relevant information, wherein the relevant information comprises information selecting from the group consisting of: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal;determine, according to the relevant information, a quantity of antennas to remain enabled; andcontrol a quantity of enabled antennas of the mobile terminal to be the quantity of antennas determined to remain enabled.(String), 20.根据权利要求19所述的移动终端,其中该说明还包括以下说明:将相关信息与预设条件进行比较,判断相关信息是否满足预设条件;其中,所述预设条件为响应于所述相关信息为与所述移动终端相关的环境信息,且所述环境信息为所述移动终端辐射范围内的用户而预设的生物信息;其中,预设条件为响应于环境信息为移动终端所在场景而预设的限制场景;其中,预设条件大于预设辐射阈值响应于相关信息为移动终端的相关参数,相关参数为移动终端的辐射强度;其中,预设条件小于预设信号阈值响应于相关参数为移动终端的信号强度;和其中,预设条件为响应于相关参数为移动终端的当前工作模式而预设的工作模式。(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 20. The mobile terminal according to claim 19, wherein the instructions further comprise instructions to:compare the relevant information with a preset condition, and determine whether the relevant information meets the preset condition;wherein the preset condition is preset biological information in response to the relevant information being the environment information relevant to the mobile terminal, and the environment information being a user within radiation of the mobile terminal;wherein the preset condition is a preset limitation scenario in response to the environment information being a scenario in which the mobile terminal is located;wherein the preset condition is greater than a preset radiation threshold in response to the relevant information being the relevant parameter of the mobile terminal, and the relevant parameter being a radiant intensity of the mobile terminal;wherein the preset condition is less than a preset signal threshold in response to the relevant parameter being a signal strength of the mobile terminal; andwherein the preset condition is a preset work mode in response to the relevant parameter being the current work mode of the mobile terminal.(String), 21.根据权利要求20所述的移动终端,其中响应于环境信息为移动终端辐射范围内的用户,所述指令还包括:将第三方设备发送的用户特征与预设生物信息进行比对,或解析用户输入的操作指令或获取的用户信息,获取用户特征,并将用户特征与预设的生物信息进行比对,其中,用户信息由用户输入或由第三方设备发送;判断用户特征是否符合预设生物信息;和根据相关信息,确定用户特征满足预设生物信息后保持开启的天线数量。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 21. The mobile terminal according to claim 20, wherein in response to the environment information being a user within radiation of the mobile terminal, the instructions further comprise instructions to:compare a user feature sent by a third-party device with the preset biological information, orparse an operation instruction entered by the user or acquired user information, to acquire a user feature, and compare the user feature with the preset biological information, wherein the user information is entered by the user or sent by a third-party device;determine whether the user feature meets the preset biological information; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the user feature meeting the preset biological information.(String), 22.根据权利要求20所述的移动终端,其中响应于环境信息为移动终端所在的场景,所述指令还包括:将场景信息与预设限制场景进行比较,判断场景信息是否满足预设限制场景,其中,场景信息由移动终端上的传感器或摄像头获取;和根据相关信息,确定满足预设限制场景的场景信息中保持启用的天线数量。(String), 1(Integer), 20(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 22. The mobile terminal according to claim 20, wherein in response to the environment information being the scenario in which the mobile terminal is located, the instructions further comprise instructions to:compare scenario information with the preset limitation scenario, and determine whether the scenario information meets the preset limitation scenario, wherein the scenario information is acquired by a sensor or a camera on the mobile terminal; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the scenario information meeting the preset limitation scenario.(String), 23.根据权利要求20所述的移动终端:其中响应于相关参数为移动终端的辐射强度,所述指令还包括:将检测到的移动终端的辐射强度与预设辐射阈值进行比较,判断移动终端的辐射强度是否大于预设辐射阈值;和根据相关信息,确定响应于移动终端的辐射强度大于预设辐射阈值而保持开启的天线数量;和其中,响应于相关参数为移动终端的信号强度,所述指令还包括:将检测到的移动终端信号强度与预设信号门限值进行比较,判断移动终端信号强度是否小于预设信号门限值;和根据相关信息,确定响应于移动终端的辐射强度大于预设辐射阈值而保持开启的天线数量。(String), 1(Integer), 21(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.866 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 23. The mobile terminal according to claim 20:wherein in response to the relevant parameter being the radiant intensity of the mobile terminal, the instructions further comprise instructions to:compare a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determine whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold; andwherein in response to the relevant parameter being the signal strength of the mobile terminal, the instructions further comprise instructions to:compare a detected signal strength of the mobile terminal with the preset signal threshold, and determine whether the signal strength of the mobile terminal is less than the preset signal threshold; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the radiant intensity of the mobile terminal being greater than the preset radiation threshold.(String), 24.根据权利要求20所述的移动终端,其中响应于相关参数为移动终端当前的工作模式,所述指令还包括:将移动终端当前工作模式与当前工作模式进行比较,判断当前工作模式是否满足预设工作模式,其中当前工作模式由用户设置,或者当前工作模式由移动终端设置响应于移动终端检测到移动终端的剩余电量低于预设电量阈值;和根据相关信息,确定移动终端当前工作模式满足预设工作模式时保持开启的天线数量。(String), 1(Integer), 22(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.867 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:14.867 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185981(Integer), 24. The mobile terminal according to claim 20, wherein in response to the relevant parameter being the current work mode of the mobile terminal, the instructions further comprise instructions to:compare the current work mode of the mobile terminal with the current work mode, and determine whether the current work mode meets the preset work mode, wherein the current work mode is set by the user, or the current work mode is set by the mobile terminal in response to the mobile terminal detecting that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; anddetermine, according to the relevant information, the quantity of antennas to remain enabled in response to the current work mode of the mobile terminal meeting the preset work mode.(String), 1(Integer), 23(Integer), 19(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185981(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2015/073496, filed on Mar. 2, 2015, which claims priority to Chinese Patent Application No. 201410307645.X, filed on Jun. 30, 2014. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present embodiments relate to the field of communications technologies, and in particular, to a control method for a mobile terminal antenna, and a mobile terminal. BACKGROUND [0003]In second generation (2G) and third generation (3G) technologies, one antenna is configured for a mobile terminal, while in fourth generation (4G) LTE (Long Term Evolution), two antennas are configured for a mobile terminal. Further, in LTE-Advanced, as many as four antennas may be configured for a mobile terminal. With development and evolution of communications technologies, eight or even more antennas, for example, 12 antennas or 16 antennas, may be configured for a mobile terminal in the future. In an MIMO (Multiple Input Multiple Output) technology, an increase in a quantity of antennas of a mobile terminal may improve a transmission capacity and a transmission rate. However, more antennas also increase calculation complexity of communication between the terminal and a communications network element, further leading to higher power consumption. [0004]Specifically, some tasks, services, or the like that are executed on the mobile terminal do not need participation of many antennas, for example, only two antennas need to be enabled to normally execute a session service. In this case, if four antennas on the mobile terminal are enabled, it causes excessively high power consumption of the mobile terminal. Especially, in the case of the mobile terminal, which is an electronic device that relies on a battery for power supply, enabling an unnecessary antenna wastes electricity of the battery, and affects use by a user. SUMMARY [0005]Embodiments provide a control method for a mobile terminal antenna, and a mobile terminal, which are used to properly control a quantity of disabled or enabled antennas of the mobile terminal. [0006]According to a first aspect, an embodiment provides a control method for a mobile terminal antenna, including acquiring, by a mobile terminal, a start command of a service and determining, by the mobile terminal according to the start command, a quantity of antennas that need to be enabled for the service. The control method also includes controlling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0007]With reference to the first aspect, in a first implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, a service signal of the service, where the service signal is the start command. [0008]With reference to the first implementation manner of the first aspect, in a second implementation manner, the method further includes: prompting, by the mobile terminal, a user whether to start the service; and if the mobile terminal does not receive, within a preset time, an operation instruction entered by the user, or the mobile terminal determines that an operation instruction entered by the user and received within the preset time is not an instruction to start the service, controlling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0009]With reference to the first aspect, in a third implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, a service signal of the service; prompting, by the mobile terminal, a user whether to start the service; receiving, by the mobile terminal, an operation instruction entered by the user; and if the mobile terminal determines that the operation instruction is an instruction to start the service, using the operation instruction as the start command. [0010]With reference to the first aspect, in a fourth implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, an operation instruction relevant to the service and entered by the user, where the operation instruction relevant to the service is the start command. [0011]With reference to the fourth implementation manner of the first aspect, in a fifth implementation manner, the method further includes: prompting, by the mobile terminal, the user to enter a subsequent operation instruction; and if the mobile terminal does not receive, within a preset time, the subsequent operation instruction entered by the user, or the mobile terminal determines that a subsequent operation instruction received within the preset time is not an instruction to start the service, controlling, by the mobile terminal, the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0012]With reference to the first aspect, in a sixth implementation manner, the acquiring, by a mobile terminal, a start command of a service includes: receiving, by the mobile terminal, an operation instruction relevant to the service and entered by a user; prompting, by the mobile terminal according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction; and receiving, by the mobile terminal, a subsequent operation instruction to start the service, and then using the subsequent operation instruction to start the service as the start command. [0013]With reference to any implementation manner of the first aspect to the sixth implementation manner of the first aspect, in a seventh implementation manner, the control method further includes: receiving, by the mobile terminal, information for terminating the service; and terminating, by the mobile terminal, the service, and controlling the quantity of enabled antennas of the mobile terminal to revert to a quantity before the start command is received. [0014]According to a second aspect, an embodiment provides a control method for a mobile terminal antenna, including acquiring, by a mobile terminal, relevant information, where the relevant information is at least any of the following information: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal. The control method also includes determining, by the mobile terminal according to the relevant information, a quantity of antennas that should remain enabled and controlling, by the mobile terminal, a quantity of enabled antennas of the mobile terminal to be the quantity of antennas corresponding to the relevant information. [0015]With reference to the second aspect, in a first implementation manner, before the determining, by the mobile terminal according to the relevant information, a quantity of antennas that should remain enabled, the control method further includes: comparing, by the mobile terminal, the relevant information with a preset condition, and determining whether the relevant information meets the preset condition, where when the relevant information is the environment information relevant to the terminal, and the environment information is a user within radiation of the mobile terminal, the preset condition is preset biological information; when the environment information is a scenario in which the mobile terminal is located, the preset condition is a preset limitation scenario; when the relevant information is the relevant parameter of the terminal, and the relevant parameter is a radiant intensity of the mobile terminal, the preset condition is being greater than a preset radiation threshold; when the relevant parameter is a signal strength of the mobile terminal, the preset condition is being less than a preset signal threshold; and when the relevant parameter is the current work mode of the mobile terminal, the preset condition is a preset work mode. [0016]With reference to the first implementation manner of the second aspect, in a second implementation manner, when the environment information is the user within the radiation of the mobile terminal, the control method further includes: comparing, by the mobile terminal, a user feature sent by a third-party device with the preset biological information, and determining whether the user feature sent by the third-party device meets the preset biological information; or, parsing, by the mobile terminal, an operation instruction entered by the user or acquired user information, to acquire a user feature; and comparing, by the mobile terminal, the user feature with the preset biological information, and determining whether the user feature meets the preset biological information, where the user information is entered by the user or sent by a third-party device; and if the user feature meets the preset biological information, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. [0017]With reference to the first implementation manner of the second aspect, in a third implementation manner, when the environment information is the scenario in which the mobile terminal is located, the control method includes: comparing, by the mobile terminal, scenario information with the preset limitation scenario, and determining whether the scenario information meets the preset limitation scenario, where the scenario information is acquired by using a sensor or a camera on the mobile terminal; and if the scenario information meets the preset limitation scenario, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. [0018]With reference to the first implementation manner of the second aspect, in a fourth implementation manner, when the relevant parameter is the radiant intensity of the mobile terminal, the control method further includes: comparing, by the mobile terminal, a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determining whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled; and when the relevant parameter is the signal strength of the mobile terminal, the control method further includes: comparing, by the mobile terminal, a detected signal strength of the mobile terminal with the preset signal threshold, and determining whether the signal strength of the mobile terminal is less than the preset signal threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. With reference to the first implementation manner of the second aspect, in a fifth implementation manner, the relevant parameter is the current work mode of the mobile terminal, and the control method further includes: comparing, by the mobile terminal, the current work mode of the mobile terminal with the work mode, and determining whether the current work mode meets the preset work mode, where the current work mode is set by the user, or is set by the mobile terminal when the mobile terminal detects that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; and if the current work mode of the mobile terminal meets the preset work mode, determining, by the mobile terminal according to the relevant information, the quantity of antennas that should remain enabled. [0019]According to a third aspect, an embodiment provides a mobile terminal, including: an acquiring module, configured to acquire a start command of a service; a determining module, configured to determine, according to the start command, a quantity of antennas that need to be enabled for the service; and a processing module, configured to control a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0020]With reference to the third aspect, in a first implementation manner, the acquiring module is specifically configured to receive a service signal of the service, where the service signal is the start command. [0021]With reference to the first implementation manner of the third aspect, in a second implementation manner, the mobile terminal further includes a prompting module and a judging module, where the prompting module is configured to prompting a user whether to start the service; and if the judging module determines that the acquiring module does not receive, within a preset time, an operation instruction entered by the user, or the judging module determines that an operation instruction entered by the user and received by the acquiring module within the preset time is not an instruction to start the service, the processing module controls the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0022]With reference to the third aspect, in a third implementation manner, the mobile terminal further includes a prompting module and a judging module, where the acquiring module is further configured to receive a service signal of the service; the prompting module is configured to prompting a user whether to start the service; and the acquiring module is configured to receive an operation instruction entered by the user; and the judging module is configured to determine that the operation instruction is an instruction to start the service, and then the acquiring module is specifically configured to use the operation instruction as the start command. [0023]With reference to the third aspect, in a fourth implementation manner, the acquiring module is specifically configured to receive an operation instruction relevant to the service and entered by the user, where the operation instruction relevant to the service is the start command. [0024]With reference to the fourth implementation manner of the third aspect, in a fifth implementation manner, the mobile terminal further includes a prompting module and a judging module, where the prompting module is configured to prompt the user to enter a subsequent operation instruction; and if the judging module determines that the acquiring module does not receive, within a preset time, a subsequent operation instruction entered by the user, or the judging module determines that a subsequent operation instruction entered by the user and received by the acquiring module within the preset time is not an instruction to start the service, the processing module is configured to control the quantity of enabled antennas of the mobile terminal to revert to a quantity before the service signal is received. [0025]With reference to the third aspect, in a sixth implementation manner, the mobile terminal further includes a prompting module and a judging module, where the acquiring module receives an operation instruction relevant to the service and entered by a user; the prompting module prompts, according to the operation instruction relevant to the service, the user to enter a subsequent operation instruction; and the judging module determines that the acquiring module receives a subsequent operation instruction to start the service, and then the acquiring module uses the subsequent operation instruction to start the service as the start command. [0026]With reference to any implementation manner of the third aspect to the sixth implementation manner of the third aspect, in a seventh implementation manner, the acquiring module is further configured to receive information for terminating the service; and the processing module terminates the service, and controls the quantity of enabled antennas of the mobile terminal to revert to a quantity before the start command is received. [0027]According to a fourth aspect, an embodiment provides a mobile terminal, including: an acquiring module, configured to acquire relevant information, where the relevant information is at least any of the following information: environment information relevant to the mobile terminal, a relevant parameter of the mobile terminal, and a current work mode of the mobile terminal; a determining module, configured to determine, according to the relevant information, a quantity of antennas that should remain enabled; and a processing module, configured to control a quantity of enabled antennas of the mobile terminal to be the quantity of antennas corresponding to the relevant information. [0028]With reference to the fourth aspect, in a first implementation manner, the determining module is further configured to compare the relevant information with a preset condition, and determine whether the relevant information meets the preset condition, where when the relevant information is the environment information relevant to the terminal, and the environment information is a user within radiation of the mobile terminal, the preset condition is preset biological information; when the environment information is a scenario in which the mobile terminal is located, the preset condition is a preset limitation scenario; when the relevant information is the relevant parameter of the terminal, and the relevant parameter is a radiant intensity of the mobile terminal, the preset condition is being greater than a preset radiation threshold; when the relevant parameter is a signal strength of the mobile terminal, the preset condition is being less than a preset signal threshold; and when the relevant parameter is the current work mode of the mobile terminal, the preset condition is a preset work mode. [0029]With reference to the first implementation manner of the fourth aspect, in a second implementation manner, the environment information is a user within radiation of the mobile terminal, and then the determining module is specifically configured to compare a user feature sent by a third-party device with the preset biological information, and determine whether the user feature sent by the third-party device meets the preset biological information; or, the acquiring module is further configured to parse an operation instruction entered by the user or acquired user information, to acquire a user feature; and the determining module is further configured to compare the user feature with the preset biological information, and determine whether the user feature meets the preset biological information, where the user information is entered by the user or sent by a third-party device; and if the user feature meets the preset biological information, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0030]With reference to the first implementation manner of the fourth aspect, in a third implementation manner, when the environment information is the scenario in which the mobile terminal is located, and the determining module is specifically configured to compare scenario information with the preset limitation scenario, and determine whether the scenario information meets the preset limitation scenario, where the scenario information is acquired by using a sensor or a camera on the mobile terminal; and if the scenario information meets the preset limitation scenario, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0031]With reference to the first implementation manner of the fourth aspect, in a fourth implementation manner, when the relevant parameter is the radiant intensity of the mobile terminal, the determining module is specifically configured to compare a detected radiant intensity of the mobile terminal with the preset radiation threshold, and determine whether the radiant intensity of the mobile terminal is greater than the preset radiation threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled; when the relevant parameter is the signal strength of the mobile terminal, the determining module is specifically configured to compare a detected signal strength of the mobile terminal with the preset signal threshold, and determine whether the signal strength of the mobile terminal is less than the preset signal threshold; and if the radiant intensity of the mobile terminal is greater than the preset radiation threshold, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0032]With reference to the first implementation manner of the fourth aspect, in a fifth implementation manner, when the relevant parameter is the current work mode of the mobile terminal, the determining module compares the current work mode of the mobile terminal with the work mode, and determines whether the current work mode meets the preset work mode, where the current work mode is set by the user, or is set by the mobile terminal when the mobile terminal detects that a remaining electric quantity of the mobile terminal is lower than a preset electric quantity threshold; and if the current work mode of the mobile terminal meets the preset work mode, the processing module is configured to determine, according to the relevant information, the quantity of antennas that should remain enabled. [0033]By means of the control method for a mobile terminal antenna and the mobile terminal that are provided in the embodiments, when a start command or relevant information of a service is received, a quantity of antennas that the mobile terminal should enable is determined, and a quantity of enabled antennas on the mobile terminal is flexibly changed, thereby preventing that the quantity of enabled antennas on the mobile terminal cannot meet a requirement for executing the service, and also preventing that the quantity of enabled antennas on the mobile terminal is excessive, which causes unnecessary energy loss; moreover, it can further prevent the quantity of enabled antennas on the mobile terminal from causing harmful impact on surroundings, or consuming electricity of the mobile terminal excessively fast and affecting performance of the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0034]FIG. 1 is a schematic diagram of an application scenario according to an embodiment; [0035]FIG. 2 is a flowchart of Embodiment 1 of a control method for a mobile terminal antenna according to the embodiments; [0036]FIG. 3 is a flowchart of Embodiment 2 of a control method for a mobile terminal antenna according to the present embodiments; [0037]FIG. 4 is a flowchart of Embodiment 3 of a control method for a mobile terminal antenna according to the present embodiments; [0038]FIG. 5 is a flowchart of Embodiment 4 of a control method for a mobile terminal antenna according to the present embodiments; [0039]FIG. 6 is a flowchart of Embodiment 5 of a control method for a mobile terminal antenna according to the present embodiments; [0040]FIG. 7 is a flowchart of Embodiment 6 of a control method for a mobile terminal antenna according to the present embodiments; [0041]FIG. 8 is a flowchart of Embodiment 7 of a control method for a mobile terminal antenna according to the present embodiments; [0042]FIG. 9 is a structural diagram of Embodiment 1 of a mobile terminal according to the present embodiments; [0043]FIG. 10 is a structural diagram of Embodiment 2 of a mobile terminal according to the present embodiments; [0044]FIG. 11 is a structural diagram of Embodiment 3 of a mobile terminal according to the present embodiments; and [0045]FIG. 12 is a structural diagram of Embodiment 4 of a mobile terminal according to the present embodiments. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0046]To make the objectives, technical solutions, and advantages of the embodiments clearer, the following clearly describes the technical solutions in the embodiments with reference to the accompanying drawings in the embodiments. Apparently, the described embodiments are some but not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments without creative efforts shall fall within the protection scope of the present embodiments. [0047]FIG. 1 is a schematic diagram of an application scenario according to an embodiment. As shown in FIG. 1, this embodiment is applied to a communications network on which technologies such as fourth generation long term evolution (4G LTE), LTE-Advanced, and multiple-input multiple-output (MIMO) are used, and a quantity of antennas that are generally disposed on a mobile terminal (such as a mobile phone or a tablet) is at least 2. Accordingly, multiple antennas are set on a network element (such as a base station) that provides a communications service for the mobile terminal. For example, N antennas are disposed on the mobile terminal, where N is a positive integer not less than 2, and M antennas are disposed on the base station, where M is a positive integer not less than 2, and in this case, the mobile terminal on the communications network can communicate, by using the N antennas, with the M antennas of the base station, to transmit a data stream. It may be understood that, when the mobile terminal executes some services, service requirements can be met by enabling only one antenna; although to use multiple antennas can improve communications performance by some degree, multiple antennas participating in communication increases complexity of the communication, causes high power consumption of the mobile terminal, and brings inconvenience to a user when the user uses the mobile terminal, or in some cases, the mobile terminal enables multiple antennas, and therefore causes excessive radiation to people or devices near the mobile terminal. Therefore, the mobile terminal needs to properly control a quantity of enabled antennas on the mobile terminal, and a specific control manner is as follows: [0048]FIG. 2 is a flowchart of Embodiment 1 of a control method for a mobile terminal antenna according to the present embodiments. As shown in FIG. 2, reference may be made to FIG. 1, and this embodiment is executed by a mobile terminal, where the mobile terminal is specifically a mobile phone, a tablet, or the like. The control method specifically includes. [0049]S101: A mobile terminal acquires a start command of a service. [0050]The start command may be a service signal of the service, for example, if a user using a mobile terminal has subscribed to a video push service, a video server periodically sends video content to the mobile terminal; and in this case, when the mobile terminal receives a video stream signal, the video stream signal is a service signal used as the start command. [0051]Alternatively, the start command may be an operation instruction entered by a user, where the operation instruction is used to instruct the mobile terminal to execute the service, for example, if the user taps a “Radio” icon on a display of the mobile terminal, the start command of the service received by the mobile terminal is an operation instruction “start a radio service”. [0052]S102: The mobile terminal determines, according to the start command, a quantity of antennas that need to be enabled for the service. [0053]The mobile terminal learns about, according to the start command, a specific service to be executed at present, and thereby can determine a quantity of antennas that are needed by the service to be started. For example, the mobile terminal enables 4 antennas at a current moment, but at this time, an incoming call paging message is received, and in this case, the mobile terminal determines that the service to be executed is a session service; the mobile terminal determines, according to settings of a network or a capability of the mobile terminal, that 1 (when the mobile terminal is on a 2G network) or 2 (when the mobile terminal is on an LTE network) antennas need to be enabled to meet a requirement of the session service; and then unnecessary enabled antennas may be disabled, that is, the following S103 is further performed. [0054]S103: The mobile terminal controls a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0055]It should be additionally noted that, when or after S103 is performed, the mobile terminal begins to execute the service, and subsequently, when the mobile terminal receives information for terminating the service, the mobile terminal terminates the service, and controls the quantity of enabled antennas of the mobile terminal to revert to a quantity before the start command is received. [0056]In this embodiment, a mobile terminal determines, according to a received start command of a service, a quantity of antennas that need to be enabled for the service, and flexibly changes a quantity of enabled antennas on the mobile terminal, thereby preventing that the quantity of enabled antennas on the mobile terminal cannot meet a requirement for executing the service, and also preventing that the quantity of enabled antennas on the mobile terminal is excessive, which causes unnecessary energy loss and affects performance of the mobile terminal. [0057]FIG. 3 is a flowchart of Embodiment 2 of a control method for a mobile terminal antenna according to the present embodiments. As shown in FIG. 3, in this embodiment, a start command of a service is a service signal of the service, and in this case, a specific process is as follows: [0058]S201: A mobile terminal receives a service signal of a service. [0059]S202: The mobile terminal determines, according to the service signal of the service, a quantity of antennas that need to be enabled for the service. [0060]Description is made by using an example in which an incoming call paging message in a session service is used as the service signal. When the mobile terminal receives the incoming call paging message, the mobile terminal learns that the session service is about to be executed, and currently the mobile terminal camps on a second generation (2G) network; in this case, the mobile terminal can meet a requirement of the session service by enabling only 1 antenna, and therefore, the mobile terminal determines, by using S202, to enable 1 antenna; and if the mobile terminal camps on an LTE network, and corresponding to the LTE network, the mobile terminal can meet the requirement of the session service by enabling only 2 antennas, and therefore, the mobile terminal determines, by using S202, to enable 2 antennas. [0061]S203: The mobile terminal controls a quantity of enabled antennas of the mobile terminal to be the quantity of antennas that need to be enabled for the service. [0062]For example, the mobile terminal enables 4 antennas at a current moment, but determines, by using S202, that the quantity of antennas that need to be enabled is 2, and then in S203, the mobile terminal disables 2 antennas, to retain 2 enabled antennas. [0063]It may be understood that, if the service signal is a video stream signal sent by a video server to the mobile terminal according to a push service that the mobile terminal subscribes to, the mobile terminal enables, by using S201 to S203, antennas needed by a video service, and then the mobile terminal directly receives and plays a video stream, that is, directly executes the service; and the following S204 to S209 may not be performed. However, to improve user experience, the mobile terminal prompts a user whether to start the service; for example, if the service signal is an incoming call paging message, the mobile terminal displays options such as “Answer” and “Reject” on a display, to prompting the user whether to start the session service, that is, in this embodiment, the following S204 to S209 still need to be performed: [0064]S20(String), 相关申请的交叉引用 [0001] 本申请是2015年3月2日提交的国际申请No.PCT / CN2015 / 073496的延续,其要求2014年6月30日提交的中国专利申请No.201410307645.X的优先权。 这些申请在此全文引入作为参考。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种移动终端天线的控制方法及移动终端。 背景 [0003] 在第二代(2G)和第三代(3G)技术中,一个天线被配置用于移动终端,而在第四代(4G)LTE(长期演进)中,两个天线被配置用于移动终端。 此外,在高级LTE中,可以为移动终端配置多达四个天线。 随着通信技术的发展和演进,将来可以为移动终端配置八个或更多个天线,例如12个天线或16个天线。 在MIMO(多输入多输出)技术中,移动终端的天线数量的增加可以提高传输容量和传输速率。 然而,更多的天线也增加了终端与通信网络元件之间的通信的计算复杂度,进一步导致更高的功耗。 [0004] 具体地,在移动终端上执行的某些任务,服务等不需要很多天线的参与,例如,仅需要启用两个天线即可正常执行会话服务。 在这种情况下,如果在移动终端上启用了四个天线,则会导致移动终端的功耗过高。 特别地,在移动终端是依靠电池供电的电子设备的情况下,启用不必要的天线会浪费电池的电,并影响用户的使用。 概要 [0005] 实施例提供了用于移动终端天线的控制方法和移动终端,其用于适当地控制移动终端的禁用或启用的天线的数量。 [0006] 根据第一方面,实施例提供了一种用于移动终端天线的控制方法,包括:由移动终端获取服务的开始命令,以及由移动终端根据该开始命令确定天线的数量。 需要启用该服务。 该控制方法还包括由移动终端将移动终端的启用的天线的数量控制为该服务需要启用的天线的数量。 [0007] 结合第一方面,在第一种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收所述服务的服务信号,所述服务信号为启动 命令。 [0008] 结合第一方面的第一种实现方式,在第二种实现方式中,该方法还包括:移动终端提示用户是否启动服务; 如果移动终端在预设时间内没有接收到用户输入的操作指令,或者移动终端确定用户输入并在预设时间内接收到的操作指令不是启动服务的指令, 由移动终端控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0009] 结合第一方面,在第三种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收所述服务的服务信号; 所述移动终端提示用户是否启动所述服务; 所述移动终端接收用户输入的操作指令; 如果移动终端确定该操作指令为启动服务的指令,则将该操作指令作为启动指令。 [0010] 结合第一方面,在第四种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收用户输入的与所述服务相关的操作指令, 与服务相关的操作指令是启动命令。 [0011] 结合第一方面的第四种实施方式,在第五种实施方式中,所述方法还包括:移动终端提示用户输入后续的操作指令; 如果移动终端在预设时间内没有接收到用户输入的后续操作指令,或者移动终端确定在预设时间内接收到的后续操作指令不是启动服务的指令, 在移动终端中,移动终端的启用天线的数量恢复为在接收服务信号之前的数量。 [0012] 结合第一方面,在第六种实现方式中,所述移动终端获取服务的启动命令,包括:所述移动终端接收用户输入的与所述服务相关的操作指令; 所述移动终端根据所述业务相关的操作指令提示用户输入后续的操作指令; 所述移动终端接收后续的操作指令以启动所述服务,然后使用所述后续的操作指令以启动所述服务作为所述启动命令。 [0013] 结合第一方面的第一实施方式至第一方面的第六实施方式中的任意一种,在第七实施方式中,所述控制方法还包括:所述移动终端接收用于终止服务的信息; 所述移动终端终止所述服务,并控制所述移动终端的使能天线数量恢复为接收到所述启动命令之前的数量。 [0014] 根据第二方面,实施例提供了一种用于移动终端天线的控制方法,包括:由移动终端获取相关信息,其中,所述相关信息是以下信息中的至少任何一种:与所述移动终端相关的环境信息; 移动终端的相关参数以及移动终端的当前工作模式。 该控制方法还包括:由移动终端根据相关信息确定应保持启用的天线的数量;以及由移动终端将移动终端的启用的天线的数量控制为与之对应的天线的数量。 相关信息。 [0015] 结合第二方面,在第一种实现方式中,在所述移动终端根据所述相关信息确定需要保持启用的天线数量之前,所述控制方法还包括:所述移动终端比较所述 具有预设条件的相关信息,并确定所述相关信息是否满足所述预设条件,当所述相关信息为与所述终端相关的环境信息,所述环境信息为所述移动终端辐射范围内的用户时,所述预设条件为 预设生物学信息; 当环境信息为移动终端所处的场景时,预设条件为预设限制场景; 当相关信息为终端的相关参数,且相关参数为移动终端的辐射强度时,预设条件大于预设辐射阈值; 当相关参数为移动终端的信号强度时,所述预设条件小于预设信号阈值; 当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0016] 结合第二方面的第一种实现方式,在第二种实现方式中,当所述环境信息为所述移动终端辐射范围内的用户时,所述控制方法还包括:所述移动终端比较发送的用户特征 第三方设备获取预设的生物信息,并确定第三方设备发送的用户特征是否满足预设的生物信息; 或者,移动终端解析用户输入的操作指令或获取的用户信息,获取用户特征; 所述移动终端将所述用户特征与所述预设生物信息进行比较,确定所述用户特征是否满足所述预设生物信息,所述用户信息由用户输入或由第三方设备发送; 如果用户特征满足预设的生物信息,则移动终端根据相关信息确定应保持启用的天线数量。 [0017] 结合第二方面的第一种实现方式,在第三种实现方式中,当所述环境信息为所述移动终端所在的场景时,所述控制方法包括:所述移动终端将所述场景信息与所述预设信息进行比较。 限制场景,并确定所述场景信息是否满足预设的限制场景,所述场景信息是通过移动终端上的传感器或摄像头获取的; 如果所述场景信息满足所述预设的限制场景,则所述移动终端根据所述相关信息确定应保持启用的天线数量。 [0018] 结合第二方面的第一种实现方式,在第四种实现方式中,当所述相关参数为所述移动终端的辐射强度时,所述控制方法还包括:所述移动终端比较检测到的所述移动终端的辐射强度。 具有预设的辐射阈值的移动终端,并确定所述移动终端的辐射强度是否大于预设的辐射阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则移动终端根据相关信息确定应保持启用的天线数量; 当所述相关参数为所述移动终端的信号强度时,所述控制方法还包括:所述移动终端将检测到的所述移动终端的信号强度与所述预设信号阈值进行比较,并确定所述移动终端的信号强度 终端小于预设信号阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则由移动终端根据相关信息确定应保持启用的天线数量。 结合第二方面的第一种实现方式,在第五种实现方式中,所述相关参数为所述移动终端的当前工作模式,所述控制方法还包括:所述移动终端比较所述移动终端当前的工作模式。 具有工作模式的移动终端,并确定当前工作模式是否满足预设工作模式,即当前工作模式由用户设置,还是当移动终端检测到剩余电量时由移动终端设置 所述移动终端低于预设电量阈值; 如果移动终端当前的工作模式满足预设的工作模式,则移动终端根据相关信息确定应保持启用的天线数量。 [0019] 根据第三方面,实施例提供了一种移动终端,包括:获取模块,用于获取服务的启动命令; 确定模块,用于根据启动命令,确定需要为该业务启用的天线数量; 处理模块,用于将所述移动终端的已启用天线的数量控制为所述业务需要启用的天线的数量。 [0020] 结合第三方面,在第一种实现方式中,所述获取模块,具体用于接收所述服务的服务信号,所述服务信号为所述启动命令。 [0021] 结合第三方面的第一种实现方式,在第二种实现方式中,所述移动终端还包括提示模块和判断模块,所述提示模块,用于提示用户是否启动所述服务; 判断模块确定获取模块在预设时间内没有收到用户输入的操作指令,或者判断模块确定用户输入并获取模块在预设时间内接收到的操作指令 如果不是开始服务的指令,则处理模块控制移动终端的已启用天线的数量以恢复到接收到服务信号之前的数量。 [0022] 结合第三方面,在第三种实施方式中,所述移动终端还包括提示模块和判断模块,所述获取模块,还用于接收所述服务的服务信号; 提示模块,用于提示用户是否启动服务; 获取模块,用于接收用户输入的操作指令; 所述判断模块,用于确定所述操作指令为启动服务的指令,所述获取模块,具体用于,将所述操作指令作为所述启动命令。 [0023] 结合第三方面,在第四种实现方式中,所述获取模块,用于接收用户输入的与所述服务有关的操作指令,其中,与所述服务有关的操作指令为启动命令。 [0024] 结合第三方面的第四种实施方式,在第五种实施方式中,所述移动终端还包括提示模块和判断模块,所述提示模块用于提示用户输入后续的操作指令; 判断模块确定获取模块在预设时间内没有接收到用户输入的后续操作指令,或者判断模块确定用户输入并由获取模块接收到的后续操作指令 预设时间不是开始服务的指令,处理模块被配置为控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0025] 结合第三方面,在第六种实现方式中,所述移动终端还包括提示模块和判断模块,所述获取模块接收与所述服务相关的用户输入的操作指令; 提示模块根据与服务有关的操作指令提示用户输入后续的操作指令; 判断模块确定获取模块接收到后续的操作指令以启动服务,然后获取模块使用后续的操作指令以启动服务作为启动命令。 [0026] 结合第三方面的任何实现方式至第三方面的第六种实现方式,在第七种实现方式中,所述获取模块,还用于接收用于终止服务的信息; 处理模块终止服务,控制移动终端的使能天线数量恢复到接收到启动命令之前的数量。 [0027] 根据第四方面,实施例提供了一种移动终端,包括:获取模块,用于获取相关信息,所述相关信息为以下至少信息:与所述移动终端相关的环境信息, 该移动终端,以及该移动终端的当前工作模式; 确定模块,用于根据相关信息,确定应保持启用状态的天线数量; 处理模块,用于将所述移动终端的启用天线的数量控制为与所述相关信息对应的天线的数量。 [0028] 结合第四方面,在第一实施方式中,所述确定模块,还用于将所述相关信息与预设条件进行比较,并确定所述相关信息是否满足所述预设条件; 所述环境信息为所述移动终端辐射范围内的用户,所述预设条件为预设生物信息; 当环境信息为移动终端所处的场景时,预设条件为预设限制场景; 当相关信息为终端的相关参数,且相关参数为移动终端的辐射强度时,预设条件大于预设辐射阈值; 当相关参数为移动终端的信号强度时,所述预设条件小于预设信号阈值; 当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0029] 结合第四方面的第一种实现方式,在第二种实现方式中,环境信息为移动终端辐射范围内的用户,则确定模块具体用于比较第三方发送的用户特征 具有所述预设生物信息的设备,并确定所述第三方设备发送的用户特征是否满足所述预设生物信息; 所述获取模块,还用于解析所述用户输入的操作指令或获取的用户信息,以获取用户特征; 所述确定模块,还用于将所述用户特征与所述预设生物信息进行比较,确定所述用户特征是否满足所述预设生物信息,所述用户信息由用户输入或由第三方设备发送; 如果所述用户特征满足所述预设的生物信息,则所述处理模块,用于根据所述相关信息,确定应保持启用的天线数量。 [0030] 结合第四方面的第一种实现方式,在第三种实现方式中,当所述环境信息为所述移动终端所处的场景时,所述确定模块具体用于将所述场景信息与所述预设的限制场景进行比较, 确定场景信息是否满足预设的限制场景,该场景信息是通过移动终端上的传感器或摄像头获取的; 如果所述场景信息满足所述预设的限制场景,则所述处理模块,用于根据所述相关信息,确定应保持启用的天线数量。 [0031] 结合第四方面的第一种实现方式,在第四种实现方式中,当所述相关参数为所述移动终端的辐射强度时,所述确定模块具体用于将检测到的所述移动终端的辐射强度与所述预设值进行比较 辐射阈值,并确定移动终端的辐射强度是否大于预设的辐射阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则处理模块,用于根据相关信息,确定应保持启用的天线数量; 当相关参数为移动终端的信号强度时,确定模块具体用于将检测到的移动终端的信号强度与预设的信号阈值进行比较,判断移动终端的信号强度是否小于预设的 信号阈值 如果所述移动终端的辐射强度大于所述预设的辐射阈值,则所述处理模块,用于根据所述相关信息,确定应保持启用的天线数量。 [0032] 结合第四方面的第一种实现方式,在第五种实现方式中,当所述相关参数为所述移动终端的当前工作模式时,所述确定模块将所述移动终端的当前工作模式与所述工作模式进行比较, 确定当前工作模式是否满足用户设置的当前工作模式或当前工作模式是否满足预设工作模式,或者当移动终端检测到剩余电量低于预设电量时,由移动终端设置 数量阈值 如果移动终端当前的工作模式满足预设的工作模式,则处理模块,用于根据相关信息,确定应保持启用的天线数量。 [0033] 通过实施例中提供的移动终端天线的控制方法和移动终端,当接收到启动命令或服务的相关信息时,确定移动终端应启用的天线数量, 可以灵活地改变移动终端上启用天线的数量,从而防止移动终端上启用天线的数量不能满足执行业务的需求,还可以防止移动终端上启用天线的数量过多, 造成不必要的能量损失; 此外,它还可以防止移动终端上启用的天线数量对周围环境造成有害影响,或者过快地消耗移动终端的电力并影响移动终端的性能。 附图的简要说明 [0034] 图。 图1是根据一个实施例的应用场景的示意图; [0035] 图。 图2是根据实施例的用于移动终端天线的控制方法的实施例1的流程图; [0036] 图。 图3是本实施方式的移动终端天线的控制方法的实施方式2的流程图。 [0037] 图。 图4是本实施方式的移动终端天线的控制方法的实施方式3的流程图。 [0038] 图。 图5是本实施方式的移动终端天线的控制方法的实施方式4的流程图。 [0039] 图。 图6是本实施方式的移动终端天线的控制方法的实施方式5的流程图。 [0040] 图。 图7是本实施方式的移动终端天线的控制方法的实施方式6的流程图。 [0041] 图。 图8是本实施方式的移动终端天线的控制方法的实施方式7的流程图。 [0042] 图。 图9是本实施方式的移动终端的实施方式1的结构图。 [0043] 图。 图10是本实施方式的移动终端的实施方式2的结构图。 [0044] 图。 图11是本实施方式的移动终端的实施方式3的结构图。 和 [0045] 图。 图12是根据本实施例的移动终端的实施例四的结构图。 具体实施方式 [0046] 为了使实施例的目的,技术方案和优点更加清楚,下面结合实施例中的附图,对实施例中的技术方案进行清楚地描述。 显然,所描述的实施例是一些但不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0047] 图。 图1是根据一个实施例的应用场景的示意图。 如图1所示。 参照图1,该实施例被应用于使用诸如第四代长期演进(4G LTE),LTE-Advanced和多输入多输出(MIMO)的技术以及通常使用的天线数量的通信网络。 设置在移动终端(例如,移动电话或平板电脑)上的至少2个。因此,在为移动终端提供通信服务的网络元件(例如,基站)上设置了多个天线。 例如,在移动终端上设置N个天线,其中N为不小于2的正整数,在基站上设置M个天线,其中M为不小于2的正整数,在这种情况下, 通信网络上的移动终端可以通过使用N个天线与基站的M个天线进行通信,以传输数据流。 可以理解的是,当移动终端执行某些服务时,仅启用一根天线就可以满足服务需求。 尽管使用多个天线可以在某种程度上改善通信性能,但是参与通信的多个天线增加了通信的复杂性,导致移动终端的功耗高,并且在用户使用移动终端时或在某些情况下给用户带来不便 在这种情况下,移动终端启用多个天线,因此对移动终端附近的人或设备造成过多的辐射。 因此,移动终端需要适当控制移动终端上启用的天线数量,具体控制方式如下: [0048] 图。 图2是根据本实施例的用于移动终端天线的控制方法的实施例1的流程图。 如图1所示。 参考图2,可以参考图1。 如图1所示,本实施例由移动终端执行,其中,移动终端具体为手机,平板电脑等。 该控制方法具体包括。 [0049] 小号 101 :移动终端获取服务的启动命令。 [0050] 该开始命令可以是该服务的服务信号,例如,如果使用移动终端的用户已经订阅了视频推送服务,则视频服务器周期性地向移动终端发送视频内容; 在这种情况下,当移动终端接收到视频流信号时,该视频流信号是用作开始命令的服务信号。 [0051] 替代地,开始命令可以是用户输入的操作指令,其中该操作指令用于指示移动终端执行服务,例如,如果用户点击了移动终端的显示器上的“无线电”图标。 移动终端接收到的服务的启动命令为操作指令“启动无线服务”。 [0052] 小号 102 :移动终端根据启动命令确定需要为该服务启用的天线数量。 [0053] 移动终端根据启动命令了解当前要执行的特定服务,从而可以确定要启动的服务所需的天线数量。 例如,移动终端在当前时刻启用了四个天线,但是此时,接收到呼入寻呼消息,在这种情况下,移动终端确定要执行的服务是会话服务; 移动终端根据网络的设置或移动终端的能力确定需要启用1根(当移动终端在2G网络上时)或2根(当移动终端在LTE网络上时)天线。 满足会话服务的要求; 然后可能会禁用不必要的启用天线,即以下S 103 进一步执行。 [0054] 小号 103 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0055] 还应注意,在S时或之后 103 执行该操作时,移动终端开始执行服务,随后,当移动终端接收到终止服务的信息时,移动终端终止服务,并控制移动终端的启用天线的数量恢复到之前的数量。 收到启动命令。 [0056] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0057] 图。 图3是根据本实施例的用于移动终端天线的控制方法的实施例2的流程图。 如图1所示。 如图3所示,在本实施例中,服务的启动命令是该服务的服务信号,在这种情况下,具体过程如下: [0058] 小号 201 :移动终端接收服务的服务信号。 [0059] 小号 202 :移动终端根据该服务的服务信号,确定该服务需要启用的天线数量。 [0060] 通过使用将会话服务中的呼入寻呼消息用作服务信号的示例进行描述。 当移动终端接收到呼入寻呼消息时,得知该会话服务即将被执行,当前该移动终端预占第二代(2G)网络。 在这种情况下,移动终端仅启用1个天线就可以满足会话服务的要求,因此,移动终端通过使用S来确定 202 ,启用1根天线; 如果移动终端驻留在LTE网络上并且对应于LTE网络,则移动终端仅启用2个天线就可以满足会话服务的需求,因此,移动终端通过使用S确定 202 ,以启用2根天线。 [0061] 小号 203 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0062] 例如,移动终端在当前时刻启用4个天线,但通过使用S来确定 202 ,则需要启用的天线数量为2,然后为S 203 ,移动终端禁用2根天线,以保留2根启用的天线。 [0063] 可以理解,如果服务信号是视频服务器根据移动终端订阅的推送服务发送给移动终端的视频流信号,则移动终端通过使用S 201 到S 203 视频服务所需的天线,然后移动终端直接接收并播放视频流,即直接执行该服务; 和以下的S 204 到S 209 可能无法执行。 然而,为了改善用户体验,移动终端提示用户是否启动服务。 例如,如果业务信号为呼入寻呼消息,则移动终端在显示屏上显示诸如“应答”和“拒绝”的选项,以提示用户是否开始会话服务,即,在本实施例中, 以下的S 204 到S 209 仍然需要执行: [0064] 小号 204 :移动终端提示用户是否启动该服务。 [0065] 小号 205 :移动终端确定是否在预设时间内接收到用户输入的操作指令,如果是,则执行S 206 ; 否则,执行S 209 。 [0066] 用户将手机放在手提包中,不知道有通话,或者用户不在移动终端附近,无法及时输入操作指令,但是移动终端无法一直等到用户进入 操作说明; 因此,移动终端需要确定是否在预设时间内接收到操作指令。 [0067] 小号 206 :移动终端确定接收到的操作指令是否为服务启动指令,如果是,则执行S 207 ; 否则,执行S 209 。 [0068] 在移动终端的显示器上显示诸如“回答”和“拒绝”之类的选项。 如果用户点击“答案”,则移动终端确定用户输入了操作指令以启动服务; 或者,如果用户点击“拒绝”,则移动终端确定用户输入了不用于启动该服务的操作指令,即会话服务在启动前已经结束,因此,S 209 被执行。 [0069] 小号 207 :移动终端执行服务。 [0070] 小号 208 :移动终端接收用于终止服务的信息。 [0071] 例如,移动终端接收视频流中的最后一条视频数据,则视频业务结束; 或者在终止呼叫时用户点击“举手”选项,则会话服务结束。 [0072] 小号 209 :移动终端控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0073] 在S 205 当移动终端确定在预设时间内没有收到用户输入的操作指令时,可以认为该服务在执行之前已经结束; 在S中 206 ,当移动终端确定接收到的操作指令为不用于启动服务的指令时,也可以认为该服务在执行之前结束; 和在S 208 ,移动终端接收用于终止服务的信息。 因此,当移动终端确定在预设时间内没有接收到用户输入的操作指令时,或者当移动终端确定接收到的操作指令是不用于启动服务的指令时,或者在移动终端之后。 终端开始执行服务,移动终端在S接收到用于终止服务的信息 209 因此,可以认为移动终端终止了服务,并且控制了移动终端的启用天线的数量以恢复到接收到服务信号之前的数量。 [0074] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0075] 图。 图4是根据本实施例的用于移动终端天线的控制方法的实施例3的流程图。 如图1所示。 如图4所示,在本实施例中,服务的启动命令为操作指令,在这种情况下,具体过程如下: [0076] 小号 301 :移动终端接收与服务有关并由用户输入的操作指令。 [0077] 小号 302 :移动终端根据与该服务相关的操作指令,确定该服务需要启用的天线数量。 [0078] 例如,在S中 301 ,如果用户点击“广播”图标,则移动终端接收用户输入的与收听广播业务有关的操作指令; 或者,如果用户点击“电话”应用(应用)图标和“联系人”应用图标,则移动终端接收与会话服务相关的操作指令,然后移动终端开始执行该服务。 因此,在本实施方式中,与服务相关的操作指令是开始指令。 然后在S 302 然后,移动终端根据与该服务相关的操作指令,确定要执行的服务以及该服务需要启用的天线数量。 [0079] 小号 303 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0080] 通过使用用户点击“联系人”应用程序的示例,移动终端通过使用S确定 302 ,要执行的服务是会话服务,但通过使用S确定 302 ,则需要为会话服务启用的天线数量为2,然后为S 303 ,移动终端禁用2根天线,并保留2根启用的天线。 [0081] 可以理解的是,如果与服务相关的操作指令正在点击“无线电”应用,并且移动终端通过使用S来启用 301 到S 303 ,是收听广播服务并直接执行该服务所需的天线,以下S 304 到S 309 可能无法执行。 对于某些服务,为了改善用户体验,或者避免用户输入的操作指令是用户误按的结果,在执行该服务之前,移动终端还需要接收后续的操作指令,以确定 用户决定启动服务。 例如,在用户点击“联系人”应用图标后,移动终端向用户显示多个联系人选项和“返回”选项; 移动终端直到用户进一步点击联系人之后并与该联系人的选项相对应的拨号选项之前,才确认用户决定开始会话服务; 或者,如果用户选择“返回”选项,则表明用户决定不启动会话服务。 详细信息如S所示 304 到S 309 : [0082] 小号 304 :移动终端提示用户输入后续的操作指令。 [0083] 小号 305 :移动终端确定是否在预设时间内接收到用户输入的后续操作指令,如果是,则执行S 306 ; 否则,执行S 309 。 [0084] 在用户不知不觉地误按图标的情况下,用户不能及时输入后续的操作指令,但是移动终端不能一直等到用户输入后续的操作指令。 因此,移动终端需要确定在预定时间内是否接收到后续的操作指令。 [0085] 小号 306 :移动终端确定接收到的后续操作指令是否为启动服务的指令,如果是,则执行S 307 ; 否则,执行S 309 。 [0086] 多个联系人选项和与该联系人选项相对应的拨号选项显示在移动终端的显示屏上,同时还有诸如“返回”和“放入黑名单”之类的选项。 如果用户点击“拨号”选项,则移动终端确定用户输入了后续的操作指令以启动服务。 或者,如果用户点击“返回”或“放入黑名单”之类的选项,则移动终端确定用户输入了不用于启动该服务的后续操作指令,即会话服务在启动前已结束 ,因此S 309 被执行。 [0087] 小号 307 :移动终端执行服务。 [0088] 小号 308 :移动终端接收用于终止服务的信息。 [0089] 具体而言,请参阅S 208 。 [0090] 小号 309 :移动终端控制移动终端的启用天线的数量,使其恢复到接收到操作指令之前的数量。 [0091] 在S 305 ,当移动终端确定在预设时间内没有收到用户输入的后续操作指令时,可以认为该服务在执行之前已经结束; 在S中 306 ,当移动终端确定接收到的后续操作指令为不用于启动服务的指令时,还可以认为该服务在执行之前结束; 和在S 308 ,移动终端接收用于终止服务的信息。 因此,当移动终端确定在预设时间内没有接收到用户输入的操作指令时,或者当移动终端确定接收到的操作指令是不用于启动服务的指令时,或者在移动终端之后。 终端开始执行服务,移动终端在S接收到用于终止服务的信息 309 因此,可以认为移动终端终止了服务,并且控制了移动终端的启用天线的数量以恢复到接收到服务信号之前的数量。 [0092] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 在移动终端上启用天线的数量不能满足执行服务的要求,并且还防止了在移动终端上启用天线的数量过多,这导致不必要的功耗并影响移动终端的性能。 [0093] 在前述实施例中,接收到的服务信号或与服务有关的操作指令被用作开始命令。 在某些情况下,当移动终端接收到服务信号或与该服务有关的操作指令时,该移动终端仅准备执行该服务,而没有立即执行该服务,然而,为了有效地向用户提供该服务, 移动终端仍立即将移动终端的启用天线的数量控制为为要执行服务而需要启用的天线的数量。 然而,在某些情况下,与服务有关的操作指令是用户错​​误按压的结果,或者接收到服务信号,但是用户不能立即给出指令,即,移动终端没有接收到操作。 在预设时间内发出指令,在这种情况下,需要控制移动终端将启用天线的数量恢复为接收到启动命令之前的数量。 在该过程中,在移动终端上发生不必要的启用/关闭控制。 移动终端对天线的开/关控制也需要开销,而不必要的开/关控制会浪费开销。 因此,优选地,通过使用图2所示的实施例,可以进一步执行天线的开/关控制。 5或图。 6: [0094] 图。 图5是根据本实施例的移动终端天线的控制方法的实施例四的流程图。 如图1所示。 参照图5,该实施例包括。 [0095] 小号 401 :移动终端接收服务的服务信号。 [0096] 小号 402 :移动终端提示用户是否启动该服务。 [0097] 小号 403 :移动终端确定是否在预设时间内接收到用户输入的操作指令,如果是,则执行S 404 ; 否则,结束该过程。 [0098] 通过使用呼入呼呼消息作为服务信号的示例,用户将移动电话放在手提包中并且不知道有呼叫,或者用户不在移动终端附近并且不能在其中输入操作指令。 时间,但是移动终端不能一直等到用户输入操作指令。 因此,移动终端需要确定是否在预设时间内接收到操作指令。 [0099] 小号 404 :移动终端确定接收到的操作指令是否为服务启动指令,如果是,则执行S 405 ; 否则,结束该过程。 [0100] 在移动终端的显示器上显示诸如“回答”和“拒绝”之类的选项。 如果用户点击“答案”,则移动终端确定用户输入了操作指令以启动服务; 或者,如果用户点击“拒绝”,则移动终端确定用户输入了不用于启动服务的操作指令,即会话服务在启动前已经结束,本实施例结束。 [0101] 小号 405 :移动终端将该操作指令作为启动命令,并根据该启动命令确定需要为该服务启用的天线数量。 [0102] 即,移动终端确定在预设时间内接收到的操作指令是启动服务的指令,然后将该操作指令用作启动命令。 [0103] 小号 406 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0104] 执行S时 406 ,移动终端同时执行服务。 [0105] 小号 407 :移动终端接收用于终止服务的信息。 [0106] 小号 408 :移动终端控制移动终端的启用天线的数量,使其恢复到接收到启动命令之前的数量。 [0107] 同时,移动终端终止服务。 [0108] 在该实施例中,当接收到服务信号时,启用天线的数量不会立即改变。 当接收到用户输入的用于启动服务的操作指令时,将用于启动服务的操作指令用作启动命令。 其他步骤与图1所示实施例中的相应步骤相似。 具体可以参见图3所示实施例中的相应步骤。 3.在本实施例中,将启动服务的操作指令用作启动命令,可以避免不必要的天线开/关开销。 [0109] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 在移动终端上启用天线的数量不能满足执行服务的要求,并且还防止了在移动终端上启用天线的数量过多,这导致不必要的功耗并影响移动终端的性能。 [0110] 图。 图6是根据本实施例的移动终端天线的控制方法的实施例五的流程图。 如图1所示。 参照图6,该实施例包括。 [0111] 小号 501 :移动终端接收与服务有关并由用户输入的操作指令。 [0112] 小号 502 :移动终端根据与业务有关的操作指令提示用户输入后续的操作指令。 [0113] 小号 503 :移动终端确定是否在预设时间内接收到用户输入的后续操作指令,如果是,则执行S 504 ; 否则,结束该过程。 [0114] 在用户不知不觉地误按图标的情况下,用户不能及时输入后续的操作指令,但是移动终端不能一直等到用户输入后续的操作指令。 因此,移动终端需要确定是否在预设时间内接收到后续的操作指令,如果是,则S 504 被执行; 否则,过程结束。 [0115] 小号 504 :移动终端确定接收到的后续操作指令是否为启动服务的指令,如果是,则执行S 505 ; 否则,结束该过程。 [0116] 多个联系人选项和与该联系人选项相对应的拨号选项显示在移动终端的显示屏上,同时还有诸如“返回”和“放入黑名单”之类的选项。 如果用户点击“拨号”选项,则移动终端确定用户输入了后续的操作指令以启动服务。 或者,如果用户点击“返回”或“添加至黑名单”等选项,则移动终端确定用户输入了不用于启动服务的后续操作指令,然后结束本实施例。 [0117] 小号 505 :移动终端使用后续的操作指令作为启动命令启动服务,并根据该启动命令确定需要为该服务启用的天线数量。 [0118] 移动终端接收到随后的用于启动服务的操作指令,因此,随后的用于启动服务的操作指令被用作启动命令。 [0119] 小号 506 :移动终端将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0120] 同时,服务被执行。 [0121] 小号 507 :移动终端接收用于终止服务的信息。 [0122] 小号 508 :移动终端控制移动终端的启用天线的数量,使其恢复到接收到启动命令之前的数量。 [0123] 同时,移动终端终止服务。 [0124] 与图1所示的实施例相比, 参照图4,在该实施例中,当接收到与服务有关的操作指令时,启用天线的数量不立即改变。 当接收到用户输入的用于启动服务的后续操作指令时,将用于启动服务的操作指令用作启动命令。 其他步骤与图1所示实施例中的相应步骤相似。 具体可以参见图4所示实施例中的相应步骤。 4.在本实施例中,将随后的启动服务的操作指令作为启动命令,可以避免不必要的天线开/关开销。 [0125] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0126] 图。 图7是根据本实施例的移动终端天线的控制方法的实施例六的流程图。 如图1所示。 参照图7,该实施例包括。 [0127] 小号 601 :移动终端获取相关信息。 [0128] 相关信息是以下信息中的至少任何一个:与移动终端相关的环境信息,移动终端的相关参数以及移动终端的当前工作模式。 [0129] 小号 602 :移动终端根据相关信息确定应保持启用状态的天线数量。 [0130] 具体地,移动终端获取的相关信息为相关参数,该相关参数表示移动终端的辐射过多,容易对用户造成有害影响。 因此,需要通过禁用某些天线来减少辐射。 例如,如果移动终端当前启用4个天线,导致移动终端过度辐射,则通过使用S来确定 602 ,应保持启用的天线数量为2,因此,使用S禁用2根天线 603 。 [0131] 小号 603 :移动终端控制移动终端的启用天线的数量为与相关信息相对应的天线的数量。 [0132] 在本实施例中,移动终端根据获取到的相关信息,确定该移动终端上应保持启用的天线数量,并灵活地改变该移动终端上的启用天线数量,从而防止移动终端上启用天线数量的增加。 移动终端对周围环境造成有害影响,或者移动终端耗电等电能消耗过快,影响移动终端性能。 [0133] 图。 图8是根据本实施例的移动终端天线的控制方法的实施例七的流程图。 如图1所示。 在图8所示的实施例的基础上,图8示出了该实施例。 参照图7,该实施例提供了进一步的详细描述,并且具体包括。 [0134] 小号 701 :移动终端获取相关信息。 [0135] 小号 702 :移动终端将相关信息与预设条件进行比较,确定相关信息是否满足预设条件,如果是,则执行S 703 ; 否则,结束该过程。 [0136] 具体地,如果相关信息具体为由相关参数反映的辐射强度,则预设条件大于预设辐射阈值。 确定后,使用S 702 ,表明辐射强度大于预设的辐射阈值S 703 否则,表明当前移动终端启用的天线数量不影响附近的用户,在这种情况下,不需要禁用天线,本实施例结束。 备选地,可以认为移动终端执行S。 703 即,当移动终端当前启用的天线数量不影响附近的用户时,根据相关信息,确定应保持启用的天线数量与相关之前保持相同。 信息被获取。 如果相关信息具体是由相关参数反映的信号强度,则预设条件小于预设信号阈值。 确定后,使用S 702 ,表明信号强度小于预设信号阈值S 703 执行该操作,使更多的天线能够确保移动终端正常地为用户提供服务,否则,表明移动终端当前启用的天线数量满足移动终端正常运行的要求, 在这种情况下,不需要执行启用天线的控制,并且该实施例结束。 备选地,可以认为移动终端执行S。 703 即,当移动终端的当前信号强度大于预设信号阈值时,通过使用S确定 703 其中,不需要增加使能的天线数量,即根据相关信息确定应保持使能的天线数量保持与获取相关信息之前的数量相同。 [0137] 如果相关信息不满足预设条件,则表明不需要改变移动终端上的启用天线数量,本实施例结束。 换句话说,S 703 和S 704 仍然执行,即通过使用S确定 703 根据不满足预设条件的相关信息,保持启用天线的数量与获取相关信息之前的数量相同。 然后在S 704 ,控制移动终端以保持启用天线的数量与S之前的数量相同 701 。 [0138] 小号 703 :移动终端根据相关信息确定应保持启用状态的天线数量。 [0139] 小号 704 :移动终端控制移动终端的启用天线的数量为与相关信息相对应的天线的数量。 [0140] 此外,相关信息是以下信息中的至少任何一个:与移动终端相关的环境信息,移动终端的相关参数以及移动终端的当前工作模式。 对应地,可能的相关信息有以下五种情况:第一种情况:当相关信息是与终端相关的环境信息,并且该环境信息是移动终端辐射范围内的用户时,预设条件为预设生物 信息; 第二种情况:当环境信息是移动终端所处的场景时,预设条件为预设限制场景; 第三种情况:当相关信息是终端的相关参数,并且相关参数是移动终端的辐射强度时,预设条件大于预设辐射阈值; 第四种:当相关参数为移动终端的信号强度时,预设条件小于预设信号阈值; 第五种:当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0141] 对于第一种情况,以下步骤用于表示S的特定执行过程 701 到S 702 , 那是。 [0142] 小号 11 a :移动终端接收第三方设备发送的用户功能。 [0143] 第三方设备是智能可穿戴设备,其中,第三方设备可以获取移动终端用户或附近人的用户特征,该人具体为成年人,老人,孕妇,儿童。 等等。 [0144] 或者,S 11 a 可以用S代替 11 b. [0145] 小号 11 b :移动终端解析用户输入的操作指令或获取的用户信息,以获取用户特征。 [0146] 例如,操作指令是“访问孕妇网页”,或打开一个名为“老人保健”的应用程序; 然后,在解析该操作指令后,获取关键字“孕妇”或“老人”,表示使用该移动终端的用户是孕妇还是老人。 然后使用S确定 12 ,这些用作用户功能的关键字是否符合预设的生物学信息。 [0147] 用户信息由用户输入或由第三方设备发送; 例如,用户通过使用照相机或移动终端的温度传感器来获得诸如使用该移动终端的用户的面部图像和体温或该移动终端附近的人的面部图像和体温之类的用户信息。 ,或智能穿戴设备之类的第三方设备收集用户信息,例如体温,用户的皮肤湿度和弹性; 然后,在解析用户信息之后,移动终端获取用户特征,即根据用户信息确定的用户特征具体为生物特征,例如老人,儿童,孕妇或成年人。 [0148] 小号 12 :移动终端将用户特征与预设的生物信息进行比较,确定用户特征是否符合预设的生物信息,如果是,则执行S 703 ; 否则,结束该过程。 [0149] 例如,预设的生物学信息具体包括老年人,儿童和孕妇。 如果使用S获得用户功能 11 是老年人,通过使用S确定 12 需要注意的是,用户功能符合预设的生物学信息,因此需要禁用某些天线以减少对老年人的辐射。 如果用户特征是成年人,则无需禁用天线,即本实施例结束,换句话说,移动终端仍然继续执行S操作。 703 到S 704 :在这种情况下,通过使用S确定 703 ,则无需为成年人更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0150] 对于第二种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0151] 小号 21 :移动终端获取场景信息。 [0152] 通过在移动终端上使用传感器或照相机来获取场景信息。 [0153] 小号 22 :移动终端将场景信息与预设的限制场景进行比较,确定场景信息是否满足预设的限制场景,如果是,则执行S 703 ; 否则,结束该过程。 [0154] 预设限制场景是诸如医院和机场之类的场景,其中需要限制来自移动终端的辐射干扰。 例如,如果在照相机拍摄的图像上出现医院的标识符,机场的标识符,儿童,孕妇,老人的标识符等,则通过移动终端的图像分析获悉: 因此,通信设备位于诸如医院或机场之类的环境中,或者周围有儿童,孕妇,老人等,并且移动终端继续执行S 703 。 可替代地,如果场景信息不是预设的限制场景所规定的任何场景,则不需要执行天线开启/关闭的控制,即该实施例结束,或者说,移动终端仍然继续 施行 703 到S 704 :在这种情况下,通过使用S确定 703 ,对于预设限制场景未规定的任何场景,无需更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0155] 对于第三种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0156] 小号 31 :移动终端自身检测辐射强度,以获取移动终端当前的辐射强度。 [0157] 小号 32 :移动终端将检测到的移动终端的辐射强度与预设的辐射阈值进行比较,确定移动终端的辐射强度是否大于预设的辐射阈值,如果是,则执行S 703 ; 否则,结束该过程。 该过程的结束也可以被解释为继续执行S。 703 到S 704 即辐射强度不大于预设的辐射阈值; 并通过使用S来确定 703 ,则无需为成年人更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0158] 对于第四种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0159] 小号 41 :移动终端自身检测信号强度,以获取移动终端的当前信号强度。 [0160] 小号 42 :移动终端将检测到的移动终端的信号强度与预设信号阈值进行比较,确定移动终端的信号强度是否小于预设信号阈值,如果是,则执行S 703 ; 否则,结束该过程。 该过程的结束也可以被解释为执行S。 703 到S 704 即,当辐射强度大于预设的辐射阈值时,通过S确定 703 ,则无需更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0161] 对于第五种情况,以下步骤用于表示S的特定执行过程 701 到S 702 。 [0162] 小号 51 :移动终端获取当前的工作模式。 [0163] 当前的工作模式是由用户设置的,例如,飞行模式,省电模式,正常模式或增强模式,并且在这种情况下,预设工作模式包括以下模式: 需要控制启用状态,例如飞行模式,省电模式,正常模式或增强模式。 例如,正常模式通常是移动终端的默认模式,并且保持启用了4根天线; 在飞行模式下需要禁用所有天线,在省电模式下只需要启用一根天线,在增强模式下需要启用超过4根天线; 另外,可以由移动终端设置省电模式,例如,当移动终端检测到移动终端的剩余电量低于预设的电量阈值时,可以由移动终端设置省电模式。 移动终端。 [0164] 小号 52 :移动终端将移动终端的当前工作模式与预设工作模式进行比较,确定当前工作模式是否满足预设工作模式,如果是,则执行S 703 ; 否则,结束该过程。 该过程的结束也可以被解释为执行S。 703 到S 704 即当前工作模式不是预设工作模式下的任何模式,例如,如果当前工作模式为普通模式,则通过S来确定 703 ,对于正常模式,仅需要保留默认数量的启用天线,并且不需要更改启用天线的数量,然后在S中 704 ,启用天线的数量保持与获取相关信息之前的数量相同。 [0165] 在本实施例中,移动终端根据获取到的相关信息,确定该移动终端上应保持启用的天线数量,并灵活地改变该移动终端上的启用天线数量,从而防止移动终端上启用天线数量的增加。 移动终端对周围环境造成有害影响,或者移动终端耗电等电能消耗过快,影响移动终端性能。 [0166] 图。 图9是根据本实施例的移动终端的实施例1的结构图。 如图1所示。 9,移动终端 600 包括:获取模块 61 ,配置为获取服务的启动命令; 确定模块 62 ,用于根据启动命令确定需要为该服务启用的天线数量; 和一个处理模块 63 配置为将移动终端的启用天线的数量控制为该服务需要启用的天线的数量。 [0167] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0168] 图。 图10是根据本实施例的移动终端的实施例二的结构图。 如图1所示。 在图10所示的实施例的基础上, 9 ,本实施例提供了进一步的详细描述,具体地,获取模块 61 具体用于接收业务的业务信号,业务信号为启动命令。 [0169] 进一步地,所述移动终端还包括提示模块 64 和一个判断模块 65 ,其中提示模块 64 配置为提示用户是否启动服务; 以及判断模块 65 确定获取模块 61 在预设时间内未收到用户或判断模块输入的操作指令 65 确定所述用户输入并由所述获取模块接收到的操作指令 61 在预设时间内未启动服务指令,处理模块 63 控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0170] 进一步的,获取模块 61 还被配置为接收该服务的服务信号; 提示模块 64 配置为提示用户是否启动服务; 获取模块 61 用于接收用户输入的操作指令; 和评审模块 65 配置为确定该操作指令为启动服务的指令,然后获取模块 61 专门配置为使用操作指令作为启动命令。 [0171] 进一步的,获取模块 61 具体用于接收用户输入的与服务有关的操作指令,其中,与服务有关的操作指令为启动命令。 [0172] (可选)提示模块 64 用于提示用户输入后续的操作指令; 以及判断模块 65 确定获取模块 61 在预设时间内没有收到用户或判断模块输入的后续操作指令 65 确定所述用户输入并由所述获取模块接收到的后续操作指令 61 在预设时间内未启动服务指令,处理模块 63 配置为控制移动终端的启用天线的数量以恢复到接收服务信号之前的数量。 [0173] 可选地,获取模块 61 接收用户输入的与服务相关的操作指令; 提示模块 64 根据与服务有关的操作指令提示用户输入后续的操作指令; 和评审模块 65 确定获取模块 61 接收后续的操作指令启动服务,然后获取模块 61 使用后续的操作指令将服务作为启动命令来启动。 [0174] 进一步的,获取模块 61 还被配置为接收用于终止服务的信息; 和处理模块 63 终止服务,并控制移动终端的启用天线数量,使其恢复到接收到启动命令之前的数量。 [0175] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行服务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失,影响移动终端的性能。 [0176] 图。 图11是根据本实施例的移动终端的实施例三的结构图。 如图1所示。 11,移动终端 700 本实施例中包括:获取模块 71 ,用于获取相关信息,所述相关信息至少为以下信息中的任意一种:与所述移动终端相关的环境信息,所述移动终端的相关参数以及所述移动终端的当前工作模式; 确定模块 72 ,配置为根据相关信息确定应保持启用状态的天线数量; 和一个处理模块 73 ,被配置为控制移动终端的启用天线的数量为与相关信息相对应的天线的数量。 [0177] 进一步地,确定模块 72 还用于将所述相关信息与预设条件进行比较,并确定所述相关信息是否满足所述预设条件,其中,当所述相关信息为与所述终端相关的环境信息,所述环境信息为所述移动终端辐射范围内的用户时 终端,预设条件为预设生物信息; 当环境信息为移动终端所处的场景时,预设条件为预设限制场景; 当相关信息为终端的相关参数,且相关参数为移动终端的辐射强度时,预设条件大于预设辐射阈值; 当相关参数为移动终端的信号强度时,所述预设条件小于预设信号阈值; 当相关参数为移动终端的当前工作模式时,预设条件为预设工作模式。 [0178] 进一步地,当环境信息是移动终端辐射范围内的用户时,确定模块 72 具体用于将第三方设备发送的用户特征与预设的生物信息进行比较,确定第三方设备发送的用户特征是否满足预设的生物信息; 或者,获取模块 71 进一步用于解析用户输入的操作指令或获取的用户信息,获取用户特征; 和确定模块 72 进一步用于将所述用户特征与所述预设生物信息进行比较,并确定所述用户特征是否满足所述预设生物信息,所述用户信息由用户输入或由第三方设备发送; 如果用户特征满足预设的生物学信息,则处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0179] 当环境信息为移动终端所在的场景时,确定模块 72 具体用于将场景信息与预设的限制场景进行比较,确定场景信息是否满足预设的限制场景,该场景信息是通过移动终端上的传感器或摄像机获取的。 如果所述场景信息满足预设的限制场景,则所述处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0180] 当相关参数为移动终端的辐射强度时,确定模块 72 具体用于将检测到的移动终端的辐射强度与预设的辐射阈值进行比较,判断移动终端的辐射强度是否大于预设的辐射阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则处理模块 73 用于根据相关信息确定应保持启用状态的天线数量; 或者,当相关参数为移动终端的信号强度时,确定模块 72 具体用于将检测到的所述移动终端的信号强度与所述预设信号阈值进行比较,判断所述移动终端的信号强度是否小于所述预设信号阈值; 如果移动终端的辐射强度大于预设的辐射阈值,则处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0181] 当相关参数为移动终端当前的工作模式时,确定模块 72 将移动终端的当前工作模式与工作模式进行比较,确定当前工作模式是否满足预设工作模式,其中当前工作模式由用户设置,或由移动终端在检测到工作模式时设置 移动终端的剩余电量低于预设电量阈值; 如果移动终端当前的工作模式满足预设的工作模式,则处理模块 73 配置为根据相关信息确定应保持启用状态的天线数量。 [0182] 在本实施例中,移动终端根据获取到的相关信息,确定该移动终端上应保持启用的天线数量,并灵活地改变该移动终端上的启用天线数量,从而防止移动终端上启用天线数量的增加。 移动终端对周围环境造成有害影响,或者移动终端耗电等电能消耗过快,影响移动终端性能。 [0183] 需要另外说明的是,移动终端实施例中的模块分别执行图3所示方法实施例中的步骤。 参照图2至图3。 如图8所示,具体执行过程和有益效果可以参考方法实施例。 [0184] 图。 图12是根据本实施例的移动终端的实施例四的结构图。 如图1所示。 参照图12,该实施例中的移动终端仅是示例。 可以理解,在实际应用中,移动终端可以是智能手机,iPad等。 不同移动终端内部的模块和部件不相同; 因此,在实践中,移动终端可以具有比图2所示的更多或更少的部件。 如图12所示,可以组合两个或更多个部分,或者可以具有不同的部分构造。 图2中所示的部件包括: 可以用包括一个或多个信号处理和/或专用集成电路的硬件,软件或硬件和软件的组合来实现图12所示的处理。 [0185] 移动终端 800 至少包含2根天线 81 ,至少一个处理器 82 记忆 83 传感器 84 ,输入/输出(I / O)接口 85 ,一个通讯模块 86 ,以及至少一条通讯总线 87 。 进一步地,移动终端还包括另一功能组件,例如,用于电池管理的电池模块,用户设置管理模块或参数检测模块; 和通讯总线 87 配置为实现模块和组件之间的连接通信。 记忆 83 存储器可以包括非易失性固态存储器和/或动态非易失性存储设备,例如闪存或可旋转磁盘驱动器。 传感器 84 包括各种传感器,例如温度传感器和湿度传感器,并且被配置为测量诸如使用移动终端的用户的体温和皮肤湿度的信息; 通讯模块 86 3G技术可以用于GSM(全球移动通信系统),CDMA(码分多址),GPRS(通用分组无线业务)或EDGE(GSM演进的增强数据速率)等长距离通信。 作为WCDMA(宽带码分多址)或TD-SCDMA(时分同步码分多址),LTE(长期演进)等4G技术等; 和通讯模块 86 可以进一步用于短距离通信,并且可以与第三方执行短距离无线电通信,例如ZigBee,超宽带(UWB),Wi-Fi,蓝牙,近场通信(NFC)和红外通信 短距离内的设备(例如智能穿戴设备)以及天线 81 与通讯模块配合 86 配置为接收和发送信号。 [0186] 具体而言,I / O接口 85 包括触摸屏 851 用于显示和输入的I / O键盘 852 (可选)用于输入,麦克风 853 , 相机 854 等等。 [0187] 具体来说,内存 83 包括一个操作系统 4021 和一个应用程序 4022 ,其中的操作系统 4021 包括各种操作系统程序,用于实现基于硬件的各种操作; 和应用程序 4022 包括各种应用程序,用于实现各种应用程序功能,例如,用于启用/关闭天线的控制程序,服务识别程序,用户特征识别程序以及相关的信息识别程序,其中,服务识别程序 可以根据用户输入的操作或移动终端接收到的服务信号,标识移动终端将要执行的服务,用户特征识别程序可以分析获取到的图像,得到关键词, 用户特征等,或者可以根据用户输入的声纹信息执行分析,以获取用户特征,或者可以分析由第三方设备(例如智能可穿戴设备)发送并由第三方设备接收的用户信息。 通信模块,以获得用户功能。 [0188] 此外,内存 83 可以进一步存储预设条件,该预设条件可以是预设生物信息,预设限制场景,预设辐射阈值,预设信号阈值,预设工作模式等。 [0189] 处理器 82 使用通讯总线与模块和组件进行通讯 87 。 在控制禁用或启用移动终端上的天线期间,当通信模块 86 通过使用天线接收服务的服务信号 81 ; 基于存储器中的服务识别程序,处理器识别服务并确定需要为该服务启用的天线数量,然后基于用于启用/关闭天线的控制程序控制启用的天线数量 移动终端的数量等于需要为该服务启用的天线数量。 [0190] 可选地,当用户通过触摸屏输入操作指令时,所述处理器基于所述服务标识程序,识别所述服务并确定需要为该服务启用的天线数量,然后基于所述控制程序启用 断开/断开天线,将移动终端的已启用天线的数量控制为该服务需要启用的天线的数量。 [0191] 另外,处理器 82 可以进一步控制触摸屏 851 通过使用通讯总线 87 ,并提示用户是否启动服务,并提示用户输入操作指令。 [0192] 进一步,当处理器获得相关信息时 82 是在移动终端辐射范围内的用户,处理器 82 根据用户特征识别程序解析用户信息,获得用户特征,将用户特征与存储在存储器中的预设生物信息进行比较,然后基于控制程序使能/关闭天线,控制天线的数量。 使移动终端的天线成为与用户特征相对应的天线数量,其中,用户信息可以是用户通过使用麦克风输入的声纹信息,用户通过使用摄像头捕获的面部图像或者用户的身体 温度,皮肤湿度等由温度传感器或湿度传感器感测到,或者可以是智能可穿戴设备感测并由通信模块接收的用户信息,或者是来自用户并由触摸屏接收的操作指令 。 [0193] 或者,处理器 82 可以基于相关信息识别程序进一步分析一些相关信息,将相关信息与存储在存储器中的预设条件进行比较,然后基于用于启用/禁用天线的控制程序,控制移动台的启用天线数量 终端是与相关信息相对应的天线数量,其中相关信息可以是移动终端所在的场景,所述场景是从摄像机拍摄的图片中获取的,相关信息标识程序可以标识 场景图片中的内容,例如医院或机场等关键字; 或者,所述相关信息为参数检测模块获取的移动终端的信号强度,辐射强度等; 或相关信息为用户设置管理模块中设置的工作模式,该工作模式可以由用户通过触摸屏输入的操作指令设置 851 或键盘 852 。 用户设置管理模块还通过使用通信总线与电池模块进行通信 87 并且,当电池模块检测到剩余电量小于预设阈值时,可以指示用户设置管理模块将工作模式设置为省电模式。 [0194] 在本实施例中,移动终端根据接收到的服务的启动命令,确定需要为该服务启用的天线数量,并灵活地改变移动终端上已启用的天线数量,从而避免了该数量 移动终端上启用天线的数量不能满足执行业务的要求,还可以防止移动终端上启用天线的数量过多,从而造成不必要的能量损失; 另外,移动终端还可以根据获取的相关信息,确定移动终端上应保持启用的天线数量,并灵活地改变移动终端上的启用天线数量,从而避免启用天线数量 会导致移动终端上的信息对周围环境造成有害影响,或者消耗过多的能量,例如移动终端的电能,从而影响移动终端的性能。 [0195] 本领域普通技术人员可以理解,方法实施例的全部或部分步骤可以通过指令相关硬件的程序来实现。 程序可以存储在计算机可读存储介质中。 当程序运行时,执行方法实施例的步骤。 前述存储介质包括:可以存储程序代码的任何介质,例如只读存储器(ROM),随机存取存储器(RAM),磁盘或光盘。 [0196] 最后,需要说明的是,上述实施例仅用于描述本实施例的技术方案,并不用于限制本发明。 尽管参考前述实施例详细描述了本实施例,但是本领域普通技术人员应该理解,他们仍然可以对前述实施例中描述的技术方案进行修改,或者对其部分或全部技术特征进行等同替换。 在不脱离实施例技术方案范围的情况下。 (String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104219377A(String), CN104219377B(String), CN107734615A(String), EP3151525A1(String), EP3151525A4(String), EP3151525B1(String), EP4020955A1(String), IN201627044485A(String), JP2017529808A(String), US20170111495A1(String), WO2016000460A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.559 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.560 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.560 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104219377A(String), CN104219377B(String), CN107734615A(String), EP3151525A1(String), EP3151525A4(String), EP3151525B1(String), EP4020955A1(String), IN201627044485A(String), JP2017529808A(String), US20170111495A1(String), WO2016000460A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.577 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104219377A(String), CN104219377B(String), CN107734615A(String), EP3151525A1(String), EP3151525A4(String), EP3151525B1(String), EP4020955A1(String), IN201627044485A(String), JP2017529808A(String), US20170111495A1(String), WO2016000460A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), CN104219377A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271093(Integer), CN104219377B(String), 1047953(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271093(Integer), CN107734615A(String), 1047964(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), EP3151525A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), EP3151525A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), EP3151525B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), EP4020955A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), IN201627044485A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), JP2017529808A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), US20170111495A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271093(Integer), WO2016000460A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:15.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104219377B(String), CN104219377B(String), 1511193600(Integer), 271093(Integer), 185377(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 271100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 271100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.129 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.130 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185981(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.197 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.197 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185981(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185981(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185981(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.443 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.613 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.613 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.613 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10666789B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:16.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Control method and device for sensors of mobile terminal, storage medium and mobile terminal(String), 移动终端传感器的控制方法及装置、存储介质及移动终端(String), US10666789B2(String), A control method for sensors of a mobile terminal is provided, which includes: a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; when determining that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, when there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and when the state resetting is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported.(String), 一种移动终端传感器的控制方法,包括:根据传感器使能指令确定移动终端传感器中的待使能传感器; 当确定触发移动终端的传感器开机事件时,获取移动终端的目标传感器的开机延迟,其中目标传感器至少包括待使能传感器,当有 为一个目标传感器,目标传感器的开机延迟小于移动终端传感器的最大开机延迟; 响应确定当前时刻达到目标传感器对应的开机延迟,对目标传感器执行状态复位; 当状态复位完成后,使能待使能传感器成为使能传感器,并上报使能传感器的获取数据。(String), US16/483693(String), 1508169600(Integer), US10666789B2(String), 1590422400(Integer), 1590422400(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 14(Integer), CN104503565A | CN105843365A | CN106850985A | CN108249874A | CN108255937A | US10111175B2 | US20090184849A1 | US20090259865A1 | US20100235667A1 | US20100302028A1 | US20130039230A1 | US20150005039A1 | US9167527B2 | US9693310B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185982(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.176 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8072daa739f04cdca955ae987f16fbc7.png(String), 185982(Integer), 8072daa739f04cdca955ae987f16fbc7.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Control method and device for sensors of mobile terminal, storage medium and mobile terminal(String), 移动终端传感器的控制方法及装置、存储介质及移动终端(String), US10666789B2(String), A control method for sensors of a mobile terminal is provided, which includes: a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; when determining that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, when there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and when the state resetting is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported.(String), 一种移动终端传感器的控制方法,包括:根据传感器使能指令确定移动终端传感器中的待使能传感器; 当确定触发移动终端的传感器开机事件时,获取移动终端的目标传感器的开机延迟,其中目标传感器至少包括待使能传感器,当有 为一个目标传感器,目标传感器的开机延迟小于移动终端传感器的最大开机延迟; 响应确定当前时刻达到目标传感器对应的开机延迟,对目标传感器执行状态复位; 当状态复位完成后,使能待使能传感器成为使能传感器,并上报使能传感器的获取数据。(String), US16/483693(String), 1508169600(Integer), US10666789B2(String), 1590422400(Integer), 1590422400(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 14(Integer), CN104503565A | CN105843365A | CN106850985A | CN108249874A | CN108255937A | US10111175B2 | US20090184849A1 | US20090259865A1 | US20100235667A1 | US20100302028A1 | US20130039230A1 | US20150005039A1 | US9167527B2 | US9693310B2(String), \20230420\8072daa739f04cdca955ae987f16fbc7.png(String), 14(Integer), 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 1. A control method for sensors of a mobile terminal, comprising:determining a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction;a determining that a sensor power-on event of the mobile terminal is triggered and acquiring a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least comprises the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal;executing, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; anddetermining that the state resetting on the to-be-enabled sensor is completed, enabling the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and reporting acquired data of the enabled sensor.(String), 1.如权利要求9所述的移动终端,还包括:响应于确定当前时刻达到移动终端的传感器的最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 2. The method as claimed in claim 1, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a first power-on delay of the to-be-enabled sensor; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor.(String), 12.如权利要求8所述的移动终端,其中获取移动终端的目标传感器的开机延时包括:获取移动终端各传感器的开机延时;和执行,响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器进行状态重置包括:响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 3. The method as claimed in claim 2, after reporting the acquired data of the enabled sensor, further comprising:executing state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 13.如权利要求12所述的移动终端,还包括:在确定移动终端的传感器开机事件被触发的同时启动调谐器,其中执行时,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器进行状态复位包括:响应于确定定时,定时器的值达到每个传感器中对应传感器的上电延迟,执行对应传感器上的状态重置。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 4. The method as claimed in claim 2, further comprising:executing, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 14.如权利要求12所述的移动终端,其中获取移动终端各传感器的开机延时包括:按照开机延时由短到长的顺序获取移动终端各传感器的开机延时。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 5. The method as claimed in claim 1, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a power-on delay of each sensor of the mobile terminal; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that a power-on delay of a corresponding sensor in each sensor is reached at the present moment, state resetting on the corresponding sensor.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 6. The method as claimed in claim 5, further comprising:starting a timer at the same time of determining that the sensor power-on event of the mobile terminal is triggered, whereinexecuting, in response to determining that a power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor comprises:executing, in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting on the corresponding sensor.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 7. The method as claimed in claim 5, wherein acquiring the power-on delay of each sensor of the mobile terminal comprises:acquiring the power-on delay of each sensor of the mobile terminal according to a sequence from short to long power-on delays.(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 8. A mobile terminal, comprising a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to implement the following operations:determining a to-be-enabled sensor in sensors of the mobile terminal according to a sensor enabling instruction;determining that a sensor power-on event of the mobile terminal is triggered, and acquiring a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least comprises the to-be-enabled sensor and, in a ease where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal;executing, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; anddetermining that the state resetting on the to-be-enabled sensor is completed, enabling the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and reporting acquired data of the enabled sensor.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 9. The mobile terminal as claimed in claim 8, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a first power-on delay of the to-be-enabled sensor; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 10. The mobile terminal as claimed in claim 9, after reporting the acquired data of the enabled sensor, further comprising:executing the state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 11. The mobile terminal as claimed in claim 9, further comprising:executing, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, the state resetting on sensors, except the enabled sensor, in the mobile terminal.(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 12. The mobile terminal as claimed in claim 8, wherein acquiring the power-on delay of the target sensor of the mobile terminal comprises:acquiring a power-on delay of each sensor of the mobile terminal; andexecuting, in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting on the target sensor comprises:executing, in response to determining that a power-on delay of a corresponding sensor in each sensor is reached at the present moment, state resetting on the corresponding sensor.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 13. The mobile terminal as claimed in claim 12, further comprising:starting a tuner at the same time of determining that the sensor power-on event of the mobile terminal is triggered, whereinexecuting, in response to determining the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor comprises:executing, in response to determining that a timing, value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting on the corresponding sensor.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185982(Integer), 14. The mobile terminal as claimed in claim 12, wherein acquiring the power-on delay of each sensor of the mobile terminal comprises:acquiring the power-on delay of each sensor of the mobile terminal according to a sequence from short to long power-on delays.(String), 1(Integer), 13(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.606 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185982(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The present application is a national stage application of International Patent Application No. PCT/CN2017/106612, which is filed on Oct. 17, 2017 and claims benefit to Chinese Patent Application No. 201710065209.X, filed on Feb. 4, 2017 and entitled “Control Method and Device for Sensors of Mobile Terminal, and Mobile Terminal”, the contents of which are hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]Embodiments of the application relate to the technical field of data processing, and particularly to a control method and device for sensors of a mobile terminal, a storage medium and a mobile terminal. BACKGROUND [0003]A mobile terminal such as a mobile phone is integrated with various types of sensors configured to assist in realization of various functions of the mobile phone. For example, an ambient light sensor may be configured to regulate brightness of automatic backlight of a screen of the mobile phone, a proximity sensor may be configured to assist in controlling the screen to be turned on and turned off, an acceleration sensor may be configured for step counting, a gravity sensor may be applied to a gravity sensing type game, a magnetic field sensor may be applied to map navigation and a compass, and a gyroscope may be configured to control a viewing angle in a game and implement inertial navigation and the like according to a motion state of an object when there is no signal of a Global Positioning System (GPS). SUMMARY [0004]The embodiments of the application provide a control method and device for sensors of a mobile terminal, a storage medium and a mobile terminal, which may increase a reporting speed of sensor data of the mobile terminal. [0005]The embodiments of the application provide a control method for sensors of a mobile terminal, which may include that: [0006]a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; [0007]in response to detecting that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0008]in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and [0009]in response to detecting that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0010]The embodiments of the application provide a control device for sensors of a mobile terminal, which may include: [0011]a to-be-enabled sensor determination module, configured to determine a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction; [0012]a power-on delay acquisition module, configured to acquire, in response to detecting that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0013]a target sensor state resetting module, configured to execute, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; and [0014]a sensor data reporting module, configured to, in response to detecting that state resetting of the to-be-enabled sensor is completed, enable the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and report acquired data of the enabled sensor. [0015]The embodiments of the application provide a storage medium, in which multiple instructions may be stored, the instructions being suitable to be loaded by a processor to execute the control method for the sensors of the mobile terminal in the embodiments of the application. [0016]The embodiments of the application provide a mobile terminal, which may include a memory, a processor and a computer program stored in the memory and capable of running on a processor, the processor executing the computer program to implement the following operations: [0017]a to-be-enabled sensor in sensors of the mobile terminal is determined according to a sensor enabling instruction; [0018]in response to detecting that a sensor power-on event of the mobile terminal is triggered, a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0019]in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and [0020]in response to detecting that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0021]According to the control method and device for the sensors of the mobile terminal, storage medium and mobile terminal provided in the embodiments of the application, a reporting speed of sensor data of the mobile terminal may be increased. BRIEF DESCRIPTION OF THE DRAWINGS [0022]FIG. 1 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application; [0023]FIG. 2 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application; [0024]FIG. 3 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application; [0025]FIG. 4 is a structure diagram of a control device for sensors of a mobile terminal according to an embodiment of the application; and [0026]FIG. 5 is a structure diagram of a mobile terminal according to an embodiment of the application. DETAILED DESCRIPTION OF THE EMBODIMENTS [0027]In order to make the purpose, technical solutions and advantages of the application clearer, exemplary embodiments of the application will further be described below in combination with the drawings in detail. It can be understood that the exemplary embodiments described herein are adopted only to explain the application and not intended to limit the application. It is also to be noted that, for convenient description, not all contents but only parts related to the application are illustrated in the drawings. It is to be mentioned before more detailed discussions about exemplary embodiments that some exemplary embodiments are described as processing or methods described in the flowcharts. Although each operation (or step) is described into sequential processing in the flowcharts, many operations therein may be implemented in parallel, concurrently or simultaneously. In addition, a sequence of each operation may be rearranged. When the operations are completed, processing may be terminated, but there may also be additional operations not included in the drawings. Processing may correspond to a method, a function, a procedure, a subroutine, a subprogram and the like. [0028]When a mobile terminal is woken from a dormant state, sensors may usually be controlled through the following process: powering-on each sensor, waiting for a power-on delay for each sensor, performing state resetting for each sensor, enabling one or more sensors, and reporting data of the one or more enabled sensors. A control method for sensors of a mobile terminal in a related art has defects and therefore needs to be improved. [0029]An embodiment of the application provides a control method for sensors of a mobile terminal, which includes that: [0030]a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction; [0031]it is determined that a sensor power-on event of the mobile terminal is triggered, and a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0032]in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting is executed on the target sensor; and [0033]it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0034]In an implementation mode, the operation that the power-on delay of the target sensor of the mobile terminal is acquired includes that: [0035]a first power-on delay of the to-be-enabled sensor is acquired; and [0036]the operation that the state resetting is executed on the target sensor in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment includes that: [0037]in response to determining that the first power-on delay is reached at the present moment, the state resetting is executed on the to-be-enabled sensor. [0038]In an implementation mode, the operation that the power-on delay of the target sensor of the mobile terminal is acquired includes that: [0039]a power-on delay of each sensor of the mobile terminal is acquired; and [0040]the operation that the state resetting is executed on the target sensor in response to determining that the power-on delay corresponding to the target sensor is reached at the present moment includes that: [0041]in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting is executed on the corresponding sensor. [0042]In an implementation mode, after the operation that the acquired data of the enabled sensor is reported, the method further includes that: [0043]the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0044]In an implementation mode, the control method for the sensors of the mobile terminal further includes that: [0045]in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0046]In an implementation mode, the control method for the sensors of the mobile terminal further includes that: [0047]a timer is started at the same time of determining that the sensor power-on event of the mobile terminal is triggered; and [0048]the operation that the state resetting is executed on the corresponding sensor in response to determining that the power-on delay of the corresponding sensor in each sensor is reached at the present moment includes that: [0049]in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting is executed on the corresponding sensor. [0050]FIG. 1 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application. The method of the embodiment may be executed by a control device for sensors of a mobile terminal. The device may be implemented by hardware and/or software. The device may be arranged in the mobile terminal as a part of the mobile terminal. [0051]As shown in FIG. 1, the control method for the sensors of the mobile terminal in the embodiment includes the following operations. [0052]In operation 101, a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction. [0053]In the embodiment, the mobile terminal includes, but is not limited to, a device such as a mobile phone, a notebook computer and a tablet computer, and the sensors of the mobile terminal include, but are not limited to, an ambient light sensor, a proximity sensor, an acceleration sensor, a gravity sensor, a magnetic field sensor, a gyroscope, a fingerprint sensor, a hall sensor, an air pressure sensor, a heartbeat sensor, an ultraviolet sensor and the like. [0054]An application of the mobile terminal, when needing to acquire data by use of a sensor, may send a sensor enabling instruction to a hardware abstract layer of the mobile terminal through an application layer of the mobile terminal. For example, when the mobile terminal changes from a screen-off state to a screen-on state, some applications (for example, a false triggering prevention application) may send enabling instructions of enabling the proximity sensor to the hardware abstract layer to acquire data of the proximity sensor, and some applications (for example, an automatic backlight regulation application) may send enabling instructions of enabling the ambient light sensor to the hardware abstract layer to acquire data of the ambient light sensor. There are many sensors in the mobile terminal, only one or more sensors may be to be enabled, and the one or more sensors of this type are called one or more to-be-enabled sensors. Then, the one or more to-be-enabled sensors in the sensors of the mobile terminal may be determined according to the sensor enabling instructions. After a sensor is enabled, data may be acquired by use of the sensor. For example, an ambient light parameter is acquired by use of the ambient light sensor, and a distance parameter between a user or another target object and the mobile terminal is acquired by use of the proximity sensor. Herein, there may be one or more to-be-enabled sensors. [0055]In operation 102, it is determined that that a sensor power-on event of the mobile terminal is triggered, and a power-on delay of a target sensor of the mobile terminal is acquired, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal. [0056]That the sensor power-on event of the mobile terminal is triggered includes that the mobile terminal is woken from a dormant state (for example, changing from the screen-off state to the screen-on state), or that the sensors are woken from the dormant state or that the sensor enabling instruction is detected. [0057]The power-on delay refers to a minimum time duration started from a power-on moment to ensure stable and normal power-on of the sensor. The power-on delay of each sensor may be different. For example, the power-on delay of the ambient light sensor is 20 ms, the power-on delay of the proximity sensor is 30 ms, while the power-on delay of the gyroscope is 150 ms. [0058]The target sensor may be the to-be-enabled sensor, and may alternatively include the to-be-enabled sensor and the other sensors. [0059]In operation 103, whether power-on delay corresponding to the target sensor is reached at a present moment or not is judged, if the power-on delay corresponding to the target sensor is reached at the present moment, operation 104 is executed, otherwise operation 103 is continued to be executed until the power-on delay is reached at the present moment. [0060]The inventor finds that many sensors in the mobile terminal share an Inter-Integrated Circuit (I2C) and a power supply and thus all of the sensors may be simultaneously powered on during power-on of the sensors. A maximum power-on delay in the power-on delays of all the sensors may be selected as the power-on delay to ensure normal power-on of each sensor. For example, the gyroscope usually requires a relatively long power-on delay as long as 150 ms, but the power-on delay of the ambient light sensor or the proximity sensor is short or even not required. Even if the ambient light sensor only needs to be enabled for an application, state resetting and enabling of the ambient light sensor can be executed only after the delay of 150 ms, which greatly delays data reporting of the ambient light sensor and reduces a reporting speed of sensor data. [0061]In a first example, if the target sensor includes the ambient light sensor and the proximity sensor, both of which are to-be-enabled sensors, state resetting is executed on the ambient light sensor 20 ms after power-on is started, and the state resetting is executed on the proximity sensor 30 ms after power-on is started. [0062]In a second example, if the target sensor includes the ambient light sensor which is a to-be-enabled sensor and another sensor, i.e., the gyroscope, the state resetting is executed on the ambient light sensor 20 ms after power-on is started, and the state resetting is executed on the gyroscope 150 ms after power-on is started. [0063]Herein, initial states of some sensors may be abnormal and thus state resetting is executed to ensure that the powered-on sensors are in normal states. [0064]In operation 104, state resetting is executed on the target sensor. [0065]In response to determining that the power-on delay corresponding to the target sensor is reached at the present moment, the state resetting is executed on the target sensor. [0066]If there are multiple target sensors, in response to determining that the power-on delay of a certain sensor is reached, the state resetting is executed on this sensor. [0067]In operation 105, it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0068]In a process of executing the resetting operation on the target sensor, if state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor. [0069]In the first example, the state resetting is executed on the ambient light sensor 20 ms after power-on is started, and in response to determining that state resetting of the ambient light sensor is completed, the ambient light sensor is enabled, and acquired data of the ambient light sensor is reported. Also in the first example, the state resetting is executed on the proximity sensor 30 ms after power-on is started, and in response to determining that state resetting of the proximity sensor is completed, the proximity sensor is enabled, and acquired data of the proximity sensor is reported. Compared with executing state resetting on the proximity sensor and the ambient light sensor and enabling the proximity sensor and the ambient light sensor 150 ms after power-on, this manner has the advantage that the reporting speed of the sensor data is greatly increased. [0070]In the second example, the state resetting is executed on the ambient light sensor 20 ms after power-on is started, and in response to determining that state resetting of the ambient light sensor is completed, the ambient light sensor is enabled, and the acquired data of the ambient light sensor is reported. Also in the second example, the state resetting is executed on the gyroscope 150 ms after power-on is started. [0071]It is to be noted that operation 105 may be executed in a process of executing operation 104 and may alternatively be executed after operation 104 is executed. FIG. 1 exemplarily illustrates an execution sequence of operations 104 and 105. Exemplarily, if the target sensor is the ambient light sensor which is a to-be-enabled sensor, after operation 104 is executed to execute the state resetting on the ambient light sensor, operation 105 is executed to determine that state resetting of the ambient light sensor is completed and enable the ambient light sensor. In the second example, after operation 104 is executed to execute the state resetting on the ambient light sensor 20 ms after power-on is started, operation 105 is executed to determine that state resetting of the ambient light sensor is completed and enable the ambient light sensor, and then operation 104 is re-executed to execute the state resetting on the gyroscope. [0072]FIG. 2 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application. As shown in FIG. 2, the method provided in the embodiment includes the following operations. [0073]In operation 201, a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction. [0074]In operation 202, it is determined that a sensor power-on event of the mobile terminal is triggered, and a first power-on delay of the to-be-enabled sensor is acquired. [0075]When there are multiple to-be-enabled sensors, there are correspondingly multiple first power-on delays. [0076]In operation 203, whether the first power-on delay is reached at a present moment or not is judged, if the first power-on delay is reached at the present moment, operation 204 is executed, otherwise operation 203 is continued to be executed until the first power-on delay is reached at the present moment. [0077]In operation 204, state resetting is executed on the to-be-enabled sensor. [0078]When there are multiple first power-on delays, in response to determining that the first power-on delay of a certain sensor is reached at the present moment, the state resetting may be executed on this sensor. [0079]In operation 205, it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0080]When there are multiple to-be-enabled sensors, in response to determining that state resetting of a certain sensor therein is completed, the sensor is immediately enabled. [0081]After the operation that the acquired data of the enabled sensor is reported, the method may further include that: the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0082]In response to determining that a maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, the state resetting is executed on sensors, except the enabled sensor, in the mobile terminal. [0083]FIG. 3 is a flowchart of a control method for sensors of a mobile terminal according to an embodiment of the application. As shown in FIG. 3, the control method for the sensors of the mobile terminal in the embodiment includes the following operations. [0084]In operation 301, a to-be-enabled sensor in the sensors of the mobile terminal is determined according to a sensor enabling instruction. [0085]In operation 302, it is determined that a sensor power-on event of the mobile terminal is triggered, and a power-on delay of each sensor of the mobile terminal is acquired. [0086]In operation 303, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at a present moment, state resetting is executed on the corresponding sensor. [0087]The operation 303 may include that: each power-on delay corresponding to each sensor is determined according to a sequence from short to long power-on delays; each power-on delay is determined as a present power-on delay respectively; and in response to determining that the present power-on delay is reached at the present moment, the state resetting is executed on the sensor corresponding to the present power-on delay. [0088]Exemplarily, the power-on delays of each sensor of the mobile terminal are 20 ms, 30 ms, 50 ms and 150 ms respectively. Then, the state resetting is executed on the sensor with the 20 ms power-on delay 20 ms after power-on is started, the state resetting is executed on the sensor with the 30 ms power-on delay 30 ms after power-on is started, the state resetting is executed on the sensor with the 50 ms power-on delay 50 ms after power-on is started, and finally the state resetting is executed on the sensor with the 150 ms power-on delay 150 ms after power-on is started. [0089]In operation 304, it is determined that state resetting of the to-be-enabled sensor is completed, the to-be-enabled sensor is enabled to become an enabled sensor, and acquired data of the enabled sensor is reported. [0090]A timer is started at the same time of determining that the sensor power-on event of the mobile terminal is triggered. Correspondingly, operation 303 may include that: in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting is executed on the corresponding sensor. Herein, the operation that the state resetting is executed on the corresponding sensor in response to determining that the power-on delay of the corresponding sensor in each sensor is reached at the timing value of the timer may include that: each power-on delay corresponding to each sensor is determined; each power-on delay is determined as a present power-on delay; and in response to determining that the present power-on delay is reached at the timing value of the timer, the state resetting is executed on the sensor corresponding to the present power-on delay. [0091]An embodiment of the application provides a control device for sensors of a mobile terminal, which includes: [0092]a to-be-enabled sensor determination module, configured to determine a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction; [0093]a power-on delay acquisition module, configured to determine that a sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal; [0094]a target sensor state resetting module, configured to execute, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor; and [0095]a sensor data reporting module, configured to determine that state resetting of the to-be-enabled sensor is completed, enable the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and report acquired data of the enabled sensor. [0096]In an implementation mode, the power-on delay acquisition module is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a first power-on delay of the to-be-enabled sensor; and [0097]the target sensor state resetting module is configured to execute, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor. [0098]In an implementation mode, the power-on delay acquisition module is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of each sensor of the mobile terminal; and [0099]the target sensor state resetting module is configured to execute, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor. [0100]In an implementation mode, the device further includes: [0101]a first other sensor state resetting module, configured to, after the acquired data of the enabled sensor is reported, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0102]In an implementation mode, device further includes: [0103]a second other sensor state resetting module, configured to, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0104]In an implementation mode, the device further includes: [0105]a timer starting module, configured to start a timer at the same time of determining that the sensor power-on event of the mobile terminal is triggered; and [0106]the operation that the target sensor state resetting module executes, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor includes that: [0107]in response to determining that a timing value of the timer reaches the power-on delay of the corresponding sensor in each sensor, the state resetting is executed on the corresponding sensor. [0108]FIG. 4 is a structure block diagram of a control device for sensors of a mobile terminal according to an embodiment of the application. The device may be implemented by software and/or hardware, and is integrated into a mobile terminal. As shown in FIG. 4, the device includes a to-be-enabled sensor determination module 41, a power-on delay acquisition module 42, a target sensor state resetting module 43 and a sensor data reporting module 44. [0109]The to-be-enabled sensor determination module 41 is configured to determine a to-be-enabled sensor in the sensors of the mobile terminal according to a sensor enabling instruction. [0110]The power-on delay acquisition module 42 is configured to determine that a sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of a target sensor of the mobile terminal, wherein the target sensor at least includes the to-be-enabled sensor and, in a case where there is one target sensor, the power-on delay of the target sensor is shorter than a maximum power-on delay of the sensors of the mobile terminal. [0111]The target sensor state resetting module 43 is configured to execute, in response to determining that the power-on delay corresponding to the target sensor is reached at a present moment, state resetting on the target sensor. [0112]The sensor data reporting module 44 is configured to determine that state resetting of the to-be-enabled sensor is completed, enable the to-be-enabled sensor so that the to-be-enabled sensor becomes an enabled sensor, and report acquired data of the enabled sensor. [0113]The power-on delay acquisition module 42 is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a first power-on delay of the to-be-enabled sensor; and [0114]the target sensor state resetting module 43 is configured to execute, in response to determining that the first power-on delay is reached at the present moment, the state resetting on the to-be-enabled sensor. [0115]The power-on delay acquisition module 42 is configured to determine that the sensor power-on event of the mobile terminal is triggered and acquire a power-on delay of each sensor of the mobile terminal; and [0116]the target sensor state resetting module 43 is configured to execute, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor. [0117]The device may further include a first other sensor state resetting module, configured to, after the acquired data of the enabled sensor is reported, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0118]The device may further include a second other sensor state resetting module, configured to, in response to determining that the maximum power-on delay of the sensors of the mobile terminal is reached at the present moment, execute the state resetting on sensors, except the enabled sensor, in the mobile terminal. [0119]The device may further include a timer starting module, configured to start a timer at the same time of determining that the sensor power-on event of the mobile terminal is triggered; and [0120]the operation that the target sensor state resetting module 43 executes, in response to determining that the power-on delay of a corresponding sensor in each sensor is reached at the present moment, the state resetting on the corresponding sensor includes that: [0121]in response to dete(String), 相关申请的交叉引用 [0001] 本申请是2017年10月17日提交的国际专利申请PCT/CN2017/106612的国家阶段申请,要求2017年2月4日提交的中国专利申请201710065209.X的权益, 标题为“用于移动终端的传感器的控制方法和装置以及移动终端”的专利,其内容通过引用整体并入本文。 技术领域 [0002] 本发明实施例涉及数据处理技术领域,尤其涉及一种移动终端传感器的控制方法、装置、存储介质和移动终端。 背景 [0003] 手机等移动终端中集成了各种传感器,用于辅助实现手机的各种功能。 例如,可以配置环境光传感器来调节手机屏幕自动背光的亮度,可以配置接近传感器来辅助控制屏幕的开启和关闭,可以配置加速度传感器 对于计步,重力传感器可以应用于重力感应类游戏,磁场传感器可以应用于地图导航和指南针,陀螺仪可以用于控制游戏中的视角,实现惯性导航; 当没有全球定位系统(GPS)的信号时,根据物体的运动状态等。 概括 [0004] 本发明实施例提供一种移动终端传感器的控制方法、装置、存储介质和移动终端,能够提高移动终端传感器数据的上报速度。 [0005] 本申请实施例提供了一种移动终端传感器的控制方法,包括: [0006] 根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0007] 响应于检测到移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0008] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0009] 响应于检测到待使能传感器状态复位完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0010] 本申请实施例提供了一种移动终端传感器的控制装置,包括: [0011] 待启用传感器确定模块,用于根据传感器启用指令确定移动终端的传感器中的待启用传感器; [0012] 开机延时获取模块,用于响应于检测到移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,所述目标传感器至少 包括待使能的传感器,在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时; [0013] 目标传感器状态重置模块,用于响应于判断当前时刻达到目标传感器对应的开机延时,对目标传感器执行状态重置; 和 [0014] 传感器数据上报模块,用于响应于检测到待使能传感器状态复位完成,使待使能传感器变为使能传感器, 报告已启用传感器的采集数据。 [0015]本发明实施例提供了一种存储介质,该存储介质中可以存储多条指令,该指令适合处理器加载以执行本发明实施例的移动终端的传感器的控制方法。 [0016] 本发明实施例提供了一种移动终端,包括存储器、处理器以及存储在存储器中并能够在处理器上运行的计算机程序,处理器执行计算机程序以实现以下操作: [0017] 根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0018] 响应于检测到移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0019] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0020] 响应于检测到待使能传感器状态复位完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0021] 本发明实施例提供的移动终端传感器的控制方法及装置、存储介质及移动终端,可以提高移动终端传感器数据的上报速度。 附图的简要说明 [0022] 图1是根据本发明一个实施例的移动终端的传感器的控制方法的流程图; [0023] 图2是根据本发明一个实施例的移动终端的传感器的控制方法的流程图; [0024] 图3是根据本发明一个实施例的移动终端的传感器的控制方法的流程图; [0025] 图4是根据本发明一个实施例的移动终端的传感器控制装置的结构图; 和 [0026] 图5是根据本发明实施例的移动终端的结构图。 具体实施方式 [0027] 为使本申请的目的、技术方案及优点更加清楚,下面将结合附图对本申请的优选实施例作进一步地详细描述。 可以理解,此处所描述的示例性实施例仅仅用于解释本申请,并不用于限制本申请。 还需要说明的是,为便于描述,附图中并未示出全部内容,仅示出了与本申请相关的部分。 在对示例性实施例进行更详细的讨论之前需要提及的是,一些示例性实施例被描述为流程图中描述的处理或方法。 虽然在流程图中每个操作(或步骤)被描述为顺序处理,但是其中的许多操作可以并行、并发或同时执行。 此外,可以重新安排每个操作的顺序。 当操作完成时,可以终止处理,但也可能存在未包括在附图中的额外操作。 处理可以对应于方法、函数、过程、子例程、子程序等。 [0028] 当移动终端从休眠状态唤醒时,通常可以通过以下流程控制传感器:为每个传感器上电,为每个传感器等待上电延时,为每个传感器进行状态复位,使能一个或多个传感器 ,以及报告一个或多个启用的传感器的数据。 相关技术中移动终端传感器的控制方法存在缺陷,需要改进。 [0029] 本申请实施例提供了一种移动终端传感器的控制方法,包括: [0030]根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0031] 确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0032] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0033] 确定待使能传感器的状态重置完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0034] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0035] 获取待使能传感器的首次上电延时; 和 [0036] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0037] 响应于确定当前时刻达到第一上电延时,对待使能传感器执行状态重置。 [0038] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0039] 获取移动终端各传感器的开机延时; 和 [0040] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0041] 响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。 [0042] 在一种实施方式中,在上报使能传感器的获取数据的操作之后,所述方法还包括: [0043] 对移动终端中除启用的传感器外的传感器进行状态重置。 [0044] 在一个实施方式中,所述移动终端的传感器的控制方法还包括: [0045] 响应于确定当前时刻达到移动终端的传感器的最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。 [0046] 在一个实施方式中,所述移动终端的传感器的控制方法还包括: [0047] 在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0048] 响应于确定当前时刻达到各传感器中对应传感器的上电延时,对对应传感器执行状态复位的操作包括: [0049] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0050] 图1是根据本发明一个实施例的移动终端的传感器的控制方法的流程图。 本实施例的方法可以由移动终端的传感器控制装置执行。 该设备可以通过硬件和/或软件来实现。 该设备可以作为移动终端的一部分设置在移动终端中。 [0051] 如图1所示,本实施例的移动终端的传感器的控制方法包括以下操作。 [0052] 运作中 101 、根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0053]在本实施例中,移动终端包括但不限于手机、笔记本电脑、平板电脑等设备,移动终端的传感器包括但不限于环境光传感器。 、接近传感器、加速度传感器、重力传感器、磁场传感器、陀螺仪、指纹传感器、霍尔传感器、气压传感器、心跳传感器、紫外线传感器等。 [0054] 移动终端的应用程序在需要通过传感器获取数据时,可以通过移动终端的应用层向移动终端的硬件抽象层发送传感器使能指令。 例如,当移动终端从熄屏状态变为亮屏状态时,一些应用程序(例如防误触发应用程序)可以向硬件抽象层发送开启接近传感器的开启指令,以获取数据 接近传感器的实现,一些应用程序(例如背光自动调节应用程序)可以向硬件抽象层发送使能环境光传感器的使能指令,以获取环境光传感器的数据。 移动终端中的传感器有很多,可以只启用一个或多个传感器,这种类型的一个或多个传感器称为一个或多个待启用传感器。 然后,可以根据传感器启用指令确定移动终端的传感器中的一个或多个待启用传感器。 启用传感器后,可以使用传感器获取数据。 例如,通过环境光传感器获取环境光参数,通过接近传感器获取用户或其他目标物体与移动终端之间的距离参数。 其中,待启用的传感器可以是一个或多个。 [0055] 运作中 102 ,确定触发移动终端的传感器开机事件,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待使能的传感器 并且,在目标传感器为一个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0056] 触发移动终端的传感器开机事件包括移动终端从休眠状态被唤醒(例如,从熄屏状态变为亮屏状态),或者传感器被唤醒。 休眠状态或检测到传感器使能指令。 [0057] 上电延时是指从上电时刻开始,保证传感器稳定正常上电的最短时间。 每个传感器的上电延迟可能不同。 例如,环境光传感器的上电延迟为20ms,接近传感器的上电延迟为30ms,而陀螺仪的上电延迟为150ms。 [0058] 目标传感器可以是待使能传感器,也可以包括待使能传感器和其他传感器。 [0059] 运作中 103 ,判断当前时刻是否达到目标传感器对应的开机延时,如果当前时刻达到目标传感器对应的开机延时,则运行 104 被执行,否则运行 103 继续执行,直到当前时刻达到开机延时。 [0060]发明人发现移动终端中的多个传感器共用一个I2C(Inter-Integrated Circuit,I2C)和一个电源,因此在传感器上电的过程中,所有的传感器都可以同时上电。 可以选择所有传感器的开机延时中的最大开机延时作为开机延时,以保证各传感器正常开机。 例如,陀螺仪通常需要比较长的上电延时,长达150ms,而环境光传感器或接近传感器的上电延时很短,甚至不需要。 即使应用只需要使能环境光传感器,也需要延迟150ms后才能进行环境光传感器的状态复位和使能,大大延迟了环境光传感器的数据上报,降低了上报速度 的传感器数据。 [0061] 在第一个例子中,如果目标传感器包括环境光传感器和接近传感器,两者都是待使能传感器,则在开始上电20ms后对环境光传感器执行状态重置,并且 上电30ms后对接近传感器执行状态复位。 [0062] 在第二个例子中,如果目标传感器包括作为待使能传感器的环境光传感器和另一个传感器,即陀螺仪,则在开始上电20ms后对环境光传感器执行状态重置 , 陀螺仪在上电 150 ms 后进行状态清零。 [0063] 在此,部分传感器的初始状态可能会出现异常,因此需要进行状态重置,以确保已上电的传感器处于正常状态。 [0064] 运作中 104 ,在目标传感器上执行状态重置。 [0065] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态重置。 [0066] 如果目标传感器有多个,则响应于确定达到某个传感器的上电延时,对该传感器执行状态复位。 [0067] 运作中 105 ,确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0068] 在对目标传感器执行复位操作的过程中,若待使能传感器的状态复位完成,则使能待使能传感器成为使能传感器。 [0069] 在第一个例子中,在开始上电20ms后,对环境光传感器进行状态重置,响应于确定环境光传感器状态重置完成,启用环境光传感器,并获取数据 环境光传感器的报告。 同样在实施例一中,在开始上电30ms后对接近传感器执行状态复位,响应于确定接近传感器状态复位完成,使接近传感器使能,并获取接近传感器的数据。 报告接近传感器。 与在上电150ms后对接近传感器和环境光传感器进行状态重置,并使能接近传感器和环境光传感器相比,这种方式的优点是大大提高了传感器数据的上报速度。 [0070] 实施例二中,在开始上电20ms后对环境光传感器进行状态复位,响应于确定环境光传感器状态复位完成,使能环境光传感器,并获取到 报告环境光传感器的数据。 同样在第二个例子中,在开始上电150ms后对陀螺仪执行状态重置。 [0071] 需要注意的是,操作 105 可以在执行操作的过程中执行 104 也可以在操作后执行 104 被执行。 图1示例性地说明了操作的执行顺序 104 和 105 . 示例性的,若目标传感器为环境光传感器,为待使能传感器,运行后 104被执行以对环境光传感器执行状态重置,操作 105 执行判断环境光传感器的状态重置完成并启用环境光传感器。 在第二个例子中,运行后 104 执行上电后20ms对环境光传感器执行状态复位,操作 105 执行判断环境光传感器状态复位完成并启用环境光传感器,然后操作 104 重新执行,对陀螺仪进行状态清零。 [0072] 图2是根据本发明一个实施例的移动终端的传感器的控制方法的流程图。 如图2所示,本实施例提供的方法包括以下操作。 [0073] 运作中 201 、根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0074] 运作中 202 ,确定移动终端的传感器开机事件被触发,获取待使能传感器的第一次开机延时。 [0075] 当有多个待使能的传感器时,对应有多个首次上电延时。 [0076] 运作中 203 , 判断当前时刻是否到达第一个上电延时, 如果当前时刻到达第一个上电延时, 则运行 204 被执行,否则运行 203 继续执行,直到当前时刻到达第一个上电延时。 [0077] 运作中 204 , 对待使能的传感器执行状态复位。 [0078] 当存在多个首次上电延时时,响应于判断当前时刻达到某个传感器的首次上电延时,可以对该传感器执行状态复位。 [0079] 运作中 205 ,确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0080] 当有多个待启用的传感器时,响应于确定其中某个传感器的状态重置完成,立即启用该传感器。 [0081] 在上报使能传感器的获取数据的操作之后,该方法还可以包括:对移动终端中除使能传感器之外的传感器执行状态重置。 [0082] 响应于确定当前时刻移动终端的传感器达到最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。 [0083] 图3是根据本发明一个实施例的移动终端的传感器的控制方法的流程图。 如图3所示,本实施例的移动终端的传感器的控制方法包括以下操作。 [0084] 运作中 301 、根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0085] 运作中 302 ,确定触发了移动终端的传感器开机事件,获取移动终端各传感器的开机延时。 [0086] 运作中 303 ,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。 [0087] 操作 303 可以包括:每个传感器对应的每个上电延时按照上电延时由短到长的顺序确定; 将每个开机延时分别确定为当前开机延时; 响应于判断当前时刻达到当前上电延时,对当前上电延时对应的传感器进行状态复位。 [0088]示例的,移动终端的每个传感器的开机延时分别为20ms、30ms、50ms和150ms。 然后,在开始上电20ms后,对传感器执行状态复位,延时20ms,上电30ms后,对传感器执行状态复位,延时30ms。 started, sensor 执行状态复位 50 ms power-on delay 开机后 50 ms,最后 sensor 执行状态复位 150 ms power-on delay 开机后 150 ms on 开始了。 [0089] 运作中 304 ,确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0090] 在确定移动终端的传感器开机事件被触发的同时启动定时器。 相应地,操作 303 可以包括:各传感器中响应于确定定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 其中,响应于在定时器的定时值确定各传感器中对应传感器的上电延时到达,对对应传感器执行状态复位的操作可以包括: 对应的各上电延时 对每个传感器进行确定; 每次开机延时确定为当前开机延时; 响应于在定时器的定时值判断为达到当前上电延时,对当前上电延时对应的传感器进行状态复位。 [0091] 本申请实施例提供了一种移动终端传感器的控制装置,包括: [0092] 待启用传感器确定模块,用于根据传感器启用指令确定移动终端的传感器中的待启用传感器; [0093] 开机延时获取模块,用于确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,所述目标传感器至少包括: 启用传感器,在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端传感器的最大开机延时; [0094] 目标传感器状态重置模块,用于响应于判断当前时刻达到目标传感器对应的开机延时,对目标传感器执行状态重置; 和 [0095] 传感器数据上报模块,用于确定待使能传感器状态复位完成,使能待使能传感器,使待使能传感器变为使能传感器,并上报获取的数据。 启用的传感器。 [0096] 在一种实施方式中,所述开机延时获取模块,用于确定所述移动终端的传感器开机事件被触发,获取所述待使能传感器的第一开机延时; 和 [0097] 目标传感器状态重置模块,用于响应于判断当前时刻达到第一上电延时,对待使能传感器执行状态重置。 [0098] 在一种实施方式中,所述开机延时获取模块,用于确定所述移动终端的传感器开机事件被触发,获取所述移动终端各传感器的开机延时; 和 [0099] 目标传感器状态重置模块,用于响应于确定当前时刻达到各传感器中对应传感器的上电延时,执行对应传感器的状态重置。 [0100] 在一种实施方式中,该装置还包括: [0101] 第一其他传感器状态重置模块,用于在上报启用传感器的获取数据后,对移动终端中除启用传感器之外的传感器执行状态重置。 [0102]在一种实施方式中,装置还包括: [0103] 第二其他传感器状态重置模块,用于响应于确定当前时刻移动终端的传感器达到最大开机延时,对除使能的传感器之外的传感器执行状态重置。 移动终端。 [0104] 在一种实施方式中,该装置还包括: [0105] 定时器启动模块,用于在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0106] 目标传感器状态重置模块执行的操作,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器进行状态重置包括: [0107] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0108] 图4是根据本发明一个实施例的移动终端的传感器控制装置的结构框图。 该装置可以通过软件和/或硬件实现,集成在移动终端中。 如图4所示,该装置包括待使能传感器判断模块 41 , 上电延时采集模块 42 , 目标传感器状态复位模块 43 和传感器数据报告模块 44 . [0109] 待使能传感器判断模块 41 用于根据传感器启用指令确定移动终端的传感器中待启用的传感器。 [0110] 上电延时采集模块 42 用于确定移动终端的传感器开机事件被触发,并获取移动终端的目标传感器的开机延时,其中,所述目标传感器至少包括待使能的传感器,在 在目标传感器为一个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0111] 目标传感器状态复位模块 43 用于响应于确定当前时刻达到目标传感器对应的开机延时,对目标传感器执行状态复位。 [0112] 传感器数据上报模块 44 用于判断待使能传感器状态复位完成,使能待使能传感器,使待使能传感器变为使能传感器,并上报获取使能传感器的数据。 [0113] 上电延时采集模块 42 用于确定移动终端的传感器开机事件被触发,获取待启用传感器的第一开机延时; 和 [0114] 目标传感器状态复位模块 43 用于响应于判断当前时刻达到第一上电延时,对待使能传感器执行状态复位。 [0115] 上电延时采集模块 42 用于确定移动终端的传感器开机事件被触发,获取移动终端各传感器的开机延时; 和 [0116] 目标传感器状态复位模块 43 用于响应于确定当前时刻达到各传感器中对应传感器的开机延时,执行对应传感器的状态复位。 [0117] 该装置还可以包括:第一其他传感器状态重置模块,用于在上报所述使能传感器的获取数据后,对所述移动终端中除所述使能传感器之外的传感器执行状态重置。 [0118]该装置还可以包括第二其他传感器状态重置模块,用于响应于确定当前时刻达到移动终端的传感器的最大开机延时,对除传感器之外的传感器执行状态重置。 启用传感器,在移动终端。 [0119] 该装置还可以包括:定时器启动模块,用于在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0120] 目标传感器状态复位模块的操作 43 执行时,响应于确定当前时刻达到每个传感器中对应传感器的上电延时,所述对应传感器的状态复位包括: [0121] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0122] 本发明实施例提供了一种存储介质,该存储介质中存储有多条指令,该指令适合处理器加载以执行本发明实施例的移动终端的传感器的控制方法。 本申请实施例提供了一种移动终端,包括存储器、处理器以及存储在存储器中并能够在处理器上运行的计算机程序,处理器执行计算机程序以实现以下操作: [0123] 根据传感器启用指令确定移动终端的传感器中待启用的传感器; [0124] 确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 [0125] 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 和 [0126] 确定待使能传感器的状态重置完成,使待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0127] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0128] 获取待使能传感器的首次上电延时; 和 [0129] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0130] 响应于确定当前时刻达到第一上电延时,对待使能传感器执行状态重置。 [0131] 在一种实施方式中,获取移动终端的目标传感器的开机延时的操作包括: [0132] 获取移动终端各传感器的开机延时; 和 [0133] 响应于判断当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位操作包括: [0134] 响应于确定当前时刻达到每个传感器中对应传感器的上电延时,对对应传感器执行状态复位。 [0135] 在一种实施方式中,在上报使能传感器的采集数据的操作之后,还包括以下操作: [0136] 对移动终端中除启用的传感器外的传感器进行状态重置。 [0137] 在一种实施方式中,所述移动终端还包括: [0138]响应于确定当前时刻达到移动终端的传感器的最大开机延时,对移动终端中除使能的传感器之外的传感器执行状态重置。 [0139] 在一种实施方式中,所述移动终端还包括: [0140] 在确定移动终端的传感器开机事件被触发的同时启动定时器; 和 [0141] 响应于确定当前时刻达到各传感器中对应传感器的上电延时,对对应传感器执行状态复位的操作包括: [0142] 响应于确定各传感器中定时器的计时值达到对应传感器的上电延时,对对应传感器执行状态复位。 [0143] 图5是根据本发明实施例的移动终端的结构图。 在本申请任一实施例中,移动终端可以包括移动终端传感器的控制装置。 如图5所示,该移动终端可以包括:存储器 501 和中央处理器 (CPU) 502 (也称为处理器)。 记忆 501 被配置为存储可执行程序代码。 处理器 502 读取存储在内存中的可执行程序代码 501 运行该可执行程序代码对应的程序执行以下操作: 根据传感器开启指令确定移动终端的传感器中待开启的传感器; 确定移动终端的传感器开机事件被触发,获取移动终端的目标传感器的开机延时,其中,目标传感器至少包括待启用的传感器, 在目标传感器为1个的情况下,目标传感器的开机延时小于移动终端的传感器的最大开机延时。 响应于确定当前时刻达到目标传感器对应的上电延时,对目标传感器执行状态复位; 确定待使能传感器状态复位完成,待使能传感器变为使能传感器,并上报获取的使能传感器数据。 [0144] 移动终端还包括:外设接口 503 , 射频 (RF) 电路 505 , 音频电路 506 , 扬声器 511 , 电源管理芯片 508 , 输入/输出 (I/O) 子系统 509 , 触摸屏 512 , 另一个输入/控制设备 510 和一个外部端口 504 ,这些组件通过一条或多条通信总线或信号线进行通信 507 . [0145] 可以理解的是,移动端 500 图中所示仅为移动端的示例,移动端 500 可以具有比图中所示的部件更多或更少的部件,可以组合两个或更多部件或者可以制作不同的部件配置。 图中所示的每个组件可以以包括一个或多个信号处理和/或专用集成电路的硬件、软件或硬件和软件的组合来实现。 [0146] 下面详细描述本实施例提供的移动终端,用于控制移动终端的传感器。 例如,移动终端为手机。 [0147] 记忆 501 : 记忆 501 可以被CPU访问 502 , 外设接口 503 之类的,还有内存 501 可以包括高速随机存取存储器(RAM),还可以包括非易失性存储器,例如,一个或多个磁盘存储设备、闪存或其他非易失性固态存储设备。 [0148] 外设接口 503 :外设接口 503 可以将设备的 I/O 外围设备连接到 CPU 502 和记忆 501 . [0149] 输入输出子系统 509 : I/O 子系统 509可以连接设备的I/O外设,例如触摸屏 512 和另一个输入/控制设备 510 到外设接口 503 . 输入输出子系统 509 可能包括一个显示控制器 5091 以及一个或多个输入控制器 5092 配置为控制其他输入/控制设备 510 . 在此,一个或多个输入控制器 5092 从其他输入/控制设备接收电信号 510 或将电信号发送到其他输入/控制设备 510 , 和另一个输入/控制设备 510 可以包括物理按钮(按压按钮和摇臂按钮)、拨盘、滑动开关、操纵杆和点击滚轮。 值得注意的是,输入控制器 5092 可以与键盘、红外端口、通用串行总线(USB)接口、鼠标等指示设备中的任意一种连接。 [0150] 触摸屏 512 : 触摸屏 512 为用户终端与用户之间的输入接口和输出接口,向用户显示视觉输出,视觉输出可以包括图形、文字、图标、视频等。 [0151] 显示控制器 5091 在 I/O 子系统中 509 从触摸屏接收电信号 512 或向触摸屏发送电信号 512 . 触摸屏 512 检测触摸屏上的接触,显示控制器 5091 将检测到的接触转换为与触摸屏上显示的用户界面对象的交互 512 实现人机交互,将用户界面对象显示在触摸屏上 512 可以是正在运行的游戏图标、连接到相应网络的图标等。 需要说明的是,该设备还可以包括光电鼠标,该光电鼠标是不显示视觉输出的触敏面,或者是触摸屏形成的触敏面的延伸。 [0152] 射频电路 505 主要用于建立手机与无线网络(即网络侧)之间的通信,以实现手机与无线网络之间的数据收发,例如短信、电子邮件的收发 . 在某些示例性实施例中,RF电路 505 接收和发送射频信号,射频信号也称为电磁信号。 射频电路 505 将电信号转换为电磁信号或将电磁信号转换为电信号,并通过电磁信号与通信网络和其他设备进行通信。 射频电路 505 可以包括被配置为执行这些功能的已知电路,并且包括但不限于天线系统、RF收发器、一个或多个放大器、调谐器、一个或多个振荡器、数字信号处理器、编码器-解码器( CODEC)芯片组、用户识别模块(SIM)等。 [0153] 音频电路 506 主要用于接收外设接口的音频数据 503 ,将音频数据转换成电信号,并将电信号发送给扬声器 511 . [0154] 演讲者 511 用于还原手机通过射频电路从无线网络接收到的语音信号 505 变成声音并向用户播放声音。 [0155] 电源管理芯片 508 配置为对CPU进行供电和电源管理 502 , I/O 子系统和与外设接口连接的硬件 503 . [0156]需要说明的是,对于本申请实施例中的移动终端传感器的控制方法,本领域普通技术人员可以理解实现该移动终端传感器控制方法的全部或部分流程。 本申请实施例中的终端,可以通过计算机程序控制相关硬件来完成。 该计算机程序可以存储在一个计算机可读取存储介质中,例如存储在内存中,由至少一个处理器执行,执行过程可以包括上述传感器的控制方法实施例的流程。 移动终端。 这里,存储介质可以是磁盘、光盘、只读存储器(Read Only Memory,ROM)、RAM等。 [0157] 以上所述仅为本申请的较佳实施例及所应用的技术原理。 本申请不限于这里描述的示例性实施例。 在不脱离本申请保护范围的情况下,本领域的技术人员可以做出各种显而易见的变更、规定和替换。 因此,本申请虽然通过上述实施例进行了详细描述,但并不限于上述实施例,在不脱离本申请的构思的前提下,还可以包括更多其他等同的实施例,本申请的范围由其所公开的范围确定。 的索赔。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106850985A(String), CN106850985B(String), EP3579531A1(String), EP3579531A4(String), US10666789B2(String), US20200028957A1(String), WO2018141167A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106850985A(String), CN106850985B(String), EP3579531A1(String), EP3579531A4(String), US10666789B2(String), US20200028957A1(String), WO2018141167A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106850985A(String), CN106850985B(String), EP3579531A1(String), EP3579531A4(String), US10666789B2(String), US20200028957A1(String), WO2018141167A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271104(Integer), CN106850985A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271104(Integer), CN106850985B(String), 1047978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271104(Integer), EP3579531A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271104(Integer), EP3579531A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:17.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271104(Integer), US10666789B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271104(Integer), US20200028957A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271104(Integer), WO2018141167A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN106850985B(String), CN106850985B(String), 1562256000(Integer), 271104(Integer), 185388(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185982(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.246 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 1(Integer), 185982(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.315 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185982(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 2(Integer), 185982(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:18.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20180139553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Operating Mobile Terminal Based on Blowing Action and Mobile Terminal(String), 基于吹气动作的移动终端操作方法及移动终端(String), US20180139553A1(String), A method for operating a mobile terminal based on a blowing action and a mobile terminal, where the mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained, an operation type is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation instruction is generated according to the operation type, and an operation corresponding to the operation instruction is performed such that a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency.(String), 一种基于吹气动作操作移动终端的方法及移动终端,所述移动终端上设置有至少两个麦克风。 当用户对至少两个麦克风吹气时,分别获取至少两个麦克风接收的声音信号的特征参数,根据获得的至少两个麦克风接收的声音信号的特征参数确定操作类型 ,根据操作类型生成操作指令,并执行与操作指令对应的操作,从而可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率 .(String), US15/570201(String), 1430150400(Integer), US20180139553A1(String), 1526486400(Integer), 美国(String), 2(Integer), 4(Integer), 3(Integer), CN103680501A | CN103955278A | US20140119568A1(String), 44(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185983(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8e32b0c904134edbba26e4294df53648.png(String), 185983(Integer), 8e32b0c904134edbba26e4294df53648.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.257 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.257 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.257 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.275 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.275 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Operating Mobile Terminal Based on Blowing Action and Mobile Terminal(String), 基于吹气动作的移动终端操作方法及移动终端(String), US20180139553A1(String), A method for operating a mobile terminal based on a blowing action and a mobile terminal, where the mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained, an operation type is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation instruction is generated according to the operation type, and an operation corresponding to the operation instruction is performed such that a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency.(String), 一种基于吹气动作操作移动终端的方法及移动终端,所述移动终端上设置有至少两个麦克风。 当用户对至少两个麦克风吹气时,分别获取至少两个麦克风接收的声音信号的特征参数,根据获得的至少两个麦克风接收的声音信号的特征参数确定操作类型 ,根据操作类型生成操作指令,并执行与操作指令对应的操作,从而可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率 .(String), US15/570201(String), 1430150400(Integer), US20180139553A1(String), 1526486400(Integer), 美国(String), 2(Integer), 2(Integer), 4(Integer), 3(Integer), CN103680501A | CN103955278A | US20140119568A1(String), \20230420\8e32b0c904134edbba26e4294df53648.png(String), 44(Integer), 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 1.-24. (canceled)25. A method for operating a mobile terminal based on a blowing action, wherein the mobile terminal comprises at least two microphones, and wherein the method comprises:separately obtaining characteristic parameters of sound signals received by the at least two microphones;determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones;generating an operation instruction according to the operation type; andperforming an operation corresponding to the operation instruction.(String), 1.-24.(取消)25、一种基于吹气动作操作移动终端的方法,其中所述移动终端包括至少两个麦克风,所述方法包括:分别获取至少两个麦克风接收到的声音信号的特征参数;根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型;根据操作类型生成操作指令;和执行与操作指令对应的操作。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 26. The method according to claim 25, wherein a characteristics parameter of a sound signal comprises at least one of a start moment, input duration, or sound loudness of the sound signal received by a microphone.(String), 26.根据权利要求25所述的方法,其中声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入时长、声音响度中的至少一项。(String), 1(Integer), 1(Integer), 24(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 27. The method according to claim 25, further comprising:determining, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow; anddetermining the operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of the blown airflow.(String), 27.根据权利要求25所述的方法,还包括:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断所述至少两个麦克风接收到的声音信号是否为吹入气流的声音信号;和当所述至少两个麦克风接收到的声音信号为吹出气流的声音信号时,根据获取的所述至少两个麦克风接收到的声音信号的特征参数确定操作类型。(String), 1(Integer), 2(Integer), 24(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 28. The method according to claim 26, further comprising:determining, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow; anddetermining the operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of the blown airflow.(String), 28.根据权利要求26所述的方法,还包括:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断所述至少两个麦克风接收到的声音信号是否为吹入气流的声音信号;和当所述至少两个麦克风接收到的声音信号为吹出气流的声音信号时,根据获取的所述至少两个麦克风接收到的声音信号的特征参数确定操作类型。(String), 1(Integer), 3(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 29. The method according to claim 26, wherein the at least two microphones comprise a first microphone and a second microphone, and wherein when the characteristics parameter of the sound signal comprises the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, determining a corresponding operation type comprises:determining that the corresponding operation type is a first operation when a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal; anddetermining that the corresponding operation type is a second operation when the start moment of the second sound signal received by the second microphone is earlier than the start moment of the first sound signal received by the first microphone, and the sound loudness of the second sound signal is greater than the sound loudness of the first sound signal.(String), 29.根据权利要求26所述的方法,其中至少两个麦克风包括第一麦克风和第二麦克风,其中当声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入持续时间和声音响度时,确定相应的操作类型包括:当第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻时,确定对应的操作类型为第一操作,且第一声音信号的声音响度为大于第二声音信号的声音响度;和当第二麦克风接收到第二声音信号的开始时刻早于第一麦克风接收到第一声音信号的开始时刻时,确定对应的操作类型为第二操作,以及第二声音信号的声音响度大于第一声音信号的声音响度。(String), 1(Integer), 4(Integer), 25(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 30. The method according to claim 25, further comprising determining, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance corresponding to the operation type, and wherein generating the operation instruction comprises generating the operation instruction according to the operation type and the operation distance.(String), 30.根据权利要求25所述的方法,还包括根据获取的所述至少两个麦克风接收到的声音信号的特征参数,确定所述操作类型对应的操作距离;其中,生成操作指令包括根据操作类型和操作距离生成操作指令。(String), 1(Integer), 5(Integer), 24(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 31. The method according to claim 29, wherein when the first microphone is disposed on a top of the mobile terminal and the second microphone is disposed at a bottom of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from top to bottom, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from bottom to top.(String), 31.根据权利要求29所述的方法,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作包括移动终端的显示内容从上到下的移动,其中,第二操作包括移动终端的显示内容由下往上的移动。(String), 1(Integer), 6(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 32. The method according to claim 29, wherein when the first microphone is disposed on a left of the mobile terminal and the second microphone is disposed on a right of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from left to right, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from right to left.(String), 32.根据权利要求29所述的方法,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作包括移动终端的显示内容从左向右移动,其中,第二操作包括移动终端的显示内容从右到左的移动。(String), 1(Integer), 7(Integer), 28(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 33. The method according to claim 31, wherein when the first microphone is disposed on the top of the mobile terminal and the second microphone is disposed at the bottom of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and wherein an operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top.(String), 33.根据权利要求31所述的方法,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作对应的操作距离为移动终端的显示内容从顶部移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从下往上移动的距离。(String), 1(Integer), 8(Integer), 30(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 34. The method according to claim 32, wherein when the first microphone is disposed on the left of the mobile terminal and the second microphone is disposed on the right of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and wherein operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left.(String), 34.根据权利要求32所述的方法,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作对应的操作距离为移动终端的显示内容从左侧移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从右向左移动的距离。(String), 1(Integer), 9(Integer), 31(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 35. The method according to claim 31, wherein when the first microphone is disposed on the top of the mobile terminal and the second microphone is disposed at the bottom of the mobile terminal, the first operation comprises one of a page up operation, an operation of sliding from top to bottom to unblock, and a back operation, and wherein the second operation comprises one of a page down operation, an operation of sliding from bottom to top to unblock, and a forward operation.(String), 35.根据权利要求31所述的方法,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作包括向上翻页操作、从上向下滑动解锁操作,以及返回操作,其中,第二操作包括向下翻页操作、从下向上滑动解锁操作和前进操作中的一种。(String), 1(Integer), 10(Integer), 30(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 36. A mobile terminal, comprising:at least two microphones;a processor; anda memory,wherein the at least two microphones, the processor, and the memory are coupled to each other using a bus,wherein the memory is configured to store a computer program, andwherein the computer program causes the processor to be configured to:separately obtain characteristic parameters of sound signals received by the at least two microphones;determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones;generate an operation instruction according to the operation type; andperform an operation corresponding to the operation instruction.(String), 36.移动终端,包括:至少两个麦克风;处理器;和一段回忆,其中至少两个麦克风、处理器和存储器使用总线彼此耦合,其中存储器被配置为存储计算机程序,并且其中计算机程序使处理器被配置为:分别获取至少两个麦克风接收到的声音信号的特征参数;根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型;根据操作类型生成操作指令;和执行与操作指令对应的操作。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 37. The mobile terminal according to claim 36, wherein a characteristics parameter of a sound signal comprises at least one of a start moment, input duration, or sound loudness of the sound signal received by a microphone.(String), 37.根据权利要求36所述的移动终端,其中声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入时长、声音响度中的至少一项。(String), 1(Integer), 12(Integer), 35(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 38. The mobile terminal according to claim 36, wherein the computer program further causes the processor to be configured to:determine, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow; anddetermine the operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of the blown airflow.(String), 38.根据权利要求36所述的移动终端,其中计算机程序还使处理器被配置为:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断所述至少两个麦克风接收到的声音信号是否为吹入气流的声音信号;和当至少两个麦克风接收到的声音信号为吹出气流的声音信号时,根据获取的至少两个麦克风接收到的声音信号的特征参数确定操作类型。(String), 1(Integer), 13(Integer), 35(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 39. The mobile terminal according to claim 37, wherein the at least two microphones comprise a first microphone and a second microphone, and wherein when the characteristics parameter of the sound signal comprises the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, the computer program further causes the processor to be configured to:determine that the operation type is a first operation when a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal; anddetermine that the operation type is a second operation when the start moment of the second sound signal received by the second microphone is earlier than the start moment of the first sound signal received by the first microphone, and the sound loudness of the second sound signal is greater than the sound loudness of the first sound signal.(String), 39.根据权利要求37所述的移动终端,其中至少两个麦克风包括第一麦克风和第二麦克风,其中当声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入持续时间和声音响度时,计算机程序进一步使处理器配置为:当第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻,且第一声音信号的声音响度较大时,确定操作类型为第一操作比第二声音信号的声音响度;和当第二麦克风接收到第二声音信号的开始时刻早于第一麦克风接收到第一声音信号的开始时刻时,确定操作类型为第二操作,且第二声音信号的声音响度为大于第一声音信号的声音响度。(String), 1(Integer), 14(Integer), 36(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 40. The mobile terminal according to a claim 36, wherein the computer program further causes the processor to be configured to determine, according to the obtained Characteristic parameters of the sound signals received by the at least two microphones, an operation distance corresponding to the operation type, and wherein when generating the operation instruction, the computer program further causes the processor to be configured to generate the operation instruction according to the operation type and the operation distance.(String), 40.根据权利要求36所述的移动终端,其中计算机程序还使得处理器用于根据获取的至少两个麦克风接收的声音信号的特征参数,确定与操作类型对应的操作距离,其中,计算机在生成操作指令时,程序还使得处理器用于根据操作类型和操作距离生成操作指令。(String), 1(Integer), 15(Integer), 35(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 41. The mobile terminal according to claim 39, wherein when the first microphone is disposed on a top of the mobile terminal and the second microphone is disposed at a bottom of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from top to bottom, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from bottom to top.(String), 41.根据权利要求39所述的移动终端,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作包括移动终端的显示内容从上到下的移动,其中,第二操作包括移动终端的显示内容由下往上的移动。(String), 1(Integer), 16(Integer), 38(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 42. The mobile terminal according to claim 39, wherein when the first microphone is disposed on a left of the mobile terminal and the second microphone is disposed on a right of the mobile terminal, the first operation comprises a movement of displayed content of the mobile terminal from left to right, and wherein the second operation comprises a movement of the displayed content of the mobile terminal from right to left.(String), 42.根据权利要求39所述的移动终端,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作包括移动终端的显示内容从左向右移动,其中,第二操作包括移动终端的显示内容从右到左的移动。(String), 1(Integer), 17(Integer), 38(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 43. The mobile terminal according to claim 41, wherein when the first microphone is disposed on the top of the mobile terminal and the second microphone is disposed at the bottom of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and wherein an operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top.(String), 43.根据权利要求41所述的移动终端,其中当第一麦克风设置在移动终端的顶部,第二麦克风设置在移动终端的底部时,第一操作对应的操作距离为移动终端的显示内容从顶部移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从下往上移动的距离。(String), 1(Integer), 18(Integer), 40(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185983(Integer), 44. The mobile terminal according to claim 41, wherein when the first microphone is disposed on the left of the mobile terminal and the second microphone is disposed on the right of the mobile terminal, an operation distance corresponding to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and wherein an operation distance corresponding to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left.(String), 44.根据权利要求41所述的移动终端,其中当第一麦克风位于移动终端的左侧,第二麦克风位于移动终端的右侧时,第一操作对应的操作距离为移动终端的显示内容从左侧移动的距离其中,第二操作对应的操作距离为移动终端的显示内容从右向左移动的距离。(String), 1(Integer), 19(Integer), 40(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185983(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a U.S. National Stage of International Patent Application No. PCT/CN2015/077665 filed on Apr. 28, 2015, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]Embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method for operating a mobile terminal based on a blowing action and a mobile terminal. BACKGROUND [0003]With development of mobile terminals such as smart tablet computers and smartphones, sizes of screens of the mobile terminals become increasingly large, and some limitations are caused to a screen sliding operation performed through finger touch. Especially, during a one-handed operation, it is relatively clumsy to perform a screen sliding operation using a finger, and man-machine interaction efficiency is low. [0004]As the sizes of the screens of the mobile terminals become increasingly large, design of dual microphones and multiple microphones becomes increasingly popular in these products, and is mainly used for noise reduction processing during a voice conversation. How to use these microphones to perform a screen sliding operation, simplify an existing operation mode, and improve man-machine interaction efficiency is a problem that needs to be resolved in the present disclosure. SUMMARY [0005]Embodiments of the present disclosure provide a method for operating a mobile terminal based on a blowing action and a mobile terminal such that a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency. [0006]According to a first aspect, a method for operating a mobile terminal based on a blowing action is provided, where the mobile terminal includes at least two microphones, and the method includes separately obtaining characteristic parameters of sound signals received by the at least two microphones, determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones, generating an operation instruction according to the operation type, and performing an operation that corresponds to the operation instruction. [0007]With reference to the first aspect, in a first possible implementation manner, the characteristics parameter of the sound signal includes at least one of a start moment, input duration, or sound loudness of the sound signal received by the microphone. [0008]With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the method further includes determining, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow, and performing the operation of determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of a blown airflow. [0009]With reference to the first or the second possible implementation manner of the first aspect, in a third possible implementation manner, the at least two microphones include a first microphone and a second microphone, and if the characteristics parameter of the sound signal includes the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, determining a corresponding operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones includes determining that the operation type is a first operation if a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal, or determining that the operation type is a second operation if a start moment of a second sound signal received by the second microphone is earlier than a start moment of a first sound signal received by the first microphone, and sound loudness of the second sound signal is greater than sound loudness of the first sound signal. [0010]With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner, the method further includes determining, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance that corresponds to the operation type, and generating an operation instruction according to the operation type includes generating the operation instruction according to the operation type and the operation distance. [0011]With reference to the third or the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from top to bottom, and the second operation includes a movement of the displayed content of the mobile terminal from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from left to right, and the second operation includes a movement of the displayed content of the mobile terminal from right to left. [0012]With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left. [0013]With reference to the third or the fourth possible implementation manner of the first aspect, in a seventh possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a page up operation, an operation of sliding from top to bottom to unblock, or a back operation, and the second operation includes a page down operation, an operation of sliding from bottom to top to unblock, or a forward operation, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a page up operation, an operation of sliding from left to right to unblock, or a back operation, and the second operation includes an operation of sliding from right to left to unblock, a page down operation, or a forward operation. [0014]According to a second aspect, a mobile terminal is provided, where the mobile terminal includes at least two microphones, and the mobile terminal further includes a monitoring unit configured to separately obtain characteristic parameters of sound signals received by the at least two microphones, a determining unit configured to determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones, a generation unit configured to generate an operation instruction according to the operation type, and an execution unit configured to perform an operation that corresponds to the operation instruction. [0015]With reference to the second aspect, in a first possible implementation manner, the characteristics parameter of the sound signal includes at least one of a start moment, input duration, or sound loudness of the sound signal received by the microphone. [0016]With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the mobile terminal further includes an identification unit configured to determine, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow, and the determining unit performs the operation of determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of a blown airflow. [0017]With reference to the first or the second possible implementation manner of the second aspect, in a third possible implementation manner, the at least two microphones include a first microphone and a second microphone, and if the characteristics parameter of the sound signal includes the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, the determining unit is further configured to determine that the operation type is a first operation if a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal, or determine that the operation type is a second operation if a start moment of a second sound signal received by the second microphone is earlier than a start moment of a first sound signal received by the first microphone, and sound loudness of the second sound signal is greater than sound loudness of the first sound signal. [0018]With reference to the second aspect or any one of the foregoing possible implementation manners of the second aspect, in a fourth possible implementation manner, the determining unit is further configured to determine, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance that corresponds to the operation type, and generating an operation instruction according to the operation type includes generating the operation instruction according to the operation type and the operation distance. [0019]With reference to the third or the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from top to bottom, and the second operation includes a movement of the displayed content of the mobile terminal from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from left to right, and the second operation includes a movement of the displayed content of the mobile terminal from right to left. [0020]With reference to the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left. [0021]With reference to the third or the fourth possible implementation manner of the second aspect, in a seventh possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a page up operation, an operation of sliding from top to bottom to unblock, or a back operation, and the second operation includes a page down operation, an operation of sliding from bottom to top to unblock, or a forward operation, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a page up operation, an operation of sliding from left to right to unblock, or a back operation, and the second operation includes an operation of sliding from right to left to unblock, a page down operation, or a forward operation. [0022]According to a third aspect, a mobile terminal is provided, where the mobile terminal includes at least two microphones, and the mobile terminal further includes a processor and a memory, where the at least two microphones, the processor, and the memory are connected using a bus, the memory is configured to store a computer program, and the processor is configured to perform the computer program, where the processor performs the computer program to separately obtain characteristic parameters of sound signals received by the at least two microphones, determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones, generate an operation instruction according to the operation type, and perform an operation that corresponds to the operation instruction. [0023]With reference to the third aspect, in a first possible implementation manner, the characteristics parameter of the sound signal includes at least one of a start moment, input duration, or sound loudness of the sound signal received by the microphone. [0024]With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the processor performs the computer program to determine, according to relevancy between the characteristic parameters of the sound signals received by the at least two microphones, whether the sound signals received by the at least two microphones are sound signals of a blown airflow, and perform the operation of determining an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones when the sound signals received by the at least two microphones are sound signals of a blown airflow. [0025]With reference to the first or the second possible implementation manner of the third aspect, in a third possible implementation manner, the at least two microphones include a first microphone and a second microphone, and if the characteristics parameter of the sound signal includes the start moment, the input duration, and the sound loudness of the sound signal received by the microphone, the processor performs the computer program to determine that the operation type is a first operation if a start moment of a first sound signal received by the first microphone is earlier than a start moment of a second sound signal received by the second microphone, and sound loudness of the first sound signal is greater than sound loudness of the second sound signal, or determine that the operation type is a second operation if a start moment of a second sound signal received by the second microphone is earlier than a start moment of a first sound signal received by the first microphone, and sound loudness of the second sound signal is greater than sound loudness of the first sound signal. [0026]With reference to the third aspect or any one of the foregoing possible implementation manners of the third aspect, in a fourth possible implementation manner, the processor performs the computer program to determine, according to the obtained characteristic parameters of the sound signals received by the at least two microphones, an operation distance that corresponds to the operation type, and generating an operation instruction according to the operation type includes generating the operation instruction according to the operation type and the operation distance. [0027]With reference to the third or the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from top to bottom, and the second operation includes a movement of the displayed content of the mobile terminal from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a movement of displayed content of the mobile terminal from left to right, and the second operation includes a movement of the displayed content of the mobile terminal from right to left. [0028]With reference to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from top to bottom, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from bottom to top, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, an operation distance that corresponds to the first operation is a distance by which the displayed content of the mobile terminal moves from left to right, and an operation distance that corresponds to the second operation is a distance by which the displayed content of the mobile terminal moves from right to left. [0029]With reference to the third or the fourth possible implementation manner of the third aspect, in a seventh possible implementation manner, if the first microphone is a microphone disposed on the top of the mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal, the first operation includes a page up operation, an operation of sliding from top to bottom to unblock, or a back operation, and the second operation includes a page down operation, an operation of sliding from bottom to top to unblock, or a forward operation, or if the first microphone is a microphone disposed on the left of the mobile terminal and the second microphone is a microphone disposed on the right of the mobile terminal, the first operation includes a page up operation, an operation of sliding from left to right to unblock, or a back operation, and the second operation includes an operation of sliding from right to left to unblock, a page down operation, or a forward operation. [0030]The embodiments of the present disclosure provide a method for operating a mobile terminal based on a blowing action and a mobile terminal. The mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained, where the characteristics parameter includes a start moment, input duration, or sound loudness of the sound signal. An operation type (and an operation distance) is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones. An operation instruction is generated according to the operation type (and the operation distance). An operation that corresponds to the operation instruction is performed. Therefore, a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency. BRIEF DESCRIPTION OF DRAWINGS [0031]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show some embodiments of the present disclosure, and persons of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0032]FIG. 1 is a schematic flowchart of a method for operating a mobile terminal based on a blowing action according to the present disclosure, [0033]FIG. 2 is a schematic flowchart of another method for operating a mobile terminal based on a blowing action according to the present disclosure, [0034]FIG. 3A and FIG. 3B are diagrams of sound signals that correspond to different blowing directions according to an embodiment of the present disclosure, [0035]FIG. 4 is a schematic diagram of an operation effect according to an embodiment of the present disclosure, [0036]FIG. 5 is a schematic diagram of another operation effect according to an embodiment of the present disclosure. [0037]FIG. 6 is a schematic diagram of another operation effect according to an embodiment of the present disclosure, [0038]FIG. 7 is a schematic diagram of another operation effect according to an embodiment of the present disclosure, [0039]FIG. 8 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure, [0040]FIG. 9 is a schematic structural diagram of another mobile terminal according to an embodiment of the present disclosure, and [0041]FIG. 10 is a schematic structural diagram of still another mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0042]To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the following clearly and completely describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0043]An embodiment of the present disclosure provides a method for operating a mobile terminal based on a blowing action. As shown in FIG. 1, the method includes the following steps. [0044]Step 101: Separately obtain characteristic parameters of sound signals received by at least two microphones. [0045]Step 102: Determine an operation type according to the obtained characteristic parameters of the sound signals received by the at least two microphones. [0046]The characteristic parameters of the sound signals received by the at least two microphones are parameters that can represent physical characteristics of the sound signals received by the at least two microphones. The characteristic parameters can be used to distinguish and identify different sound signals. The characteristic parameters may be start moments, input duration, and sound loudness of the sound signals received by the at least two microphones. [0047]Step 103: Generate an operation instruction according to the operation type. [0048]Step 104: Perform an operation that corresponds to the operation instruction. [0049]This embodiment of the present disclosure provides a method for operating a mobile terminal based on a blowing action. The mobile terminal is provided with at least two microphones. When a user blows air to the at least two microphones, characteristic parameters of sound signals received by the at least two microphones are separately obtained. An operation type is determined according to the obtained characteristic parameters of the sound signals received by the at least two microphones. An operation instruction is generated according to the operation type. An operation that corresponds to the operation instruction is performed. Therefore, a mobile terminal can be operated using microphones on the mobile terminal, thereby simplifying an existing operation mode and improving man-machine interaction efficiency. [0050]To make persons skilled in the art understand the technical solutions provided in the embodiments of the present disclosure more clearly, the method for operating a mobile terminal based on a blowing action provided in this embodiment of the present disclosure is described below in detail using a specific embodiment. For ease of description, that a first microphone is a microphone disposed on the top of a mobile terminal and the second microphone is a microphone disposed at the bottom of the mobile terminal is used as an example. As shown in FIG. 2, the method includes the following steps. [0051]Step 201: The mobile terminal identifies whether the mobile terminal is in an automatic-screen-sliding scenario. [0052]In this embodiment of the present disclosure, “screen sliding” may be construed as a movement of content displayed on a screen of the mobile terminal. The movement includes, but is not limited to touch unblock, sliding unblock, an up/down movement or a left/right movement of the displayed content, page up, and page down. The automatic-screen-sliding scenario may be construed as a scenario in which the foregoing “screen sliding” operation can be performed without needing a touch operation by a user. [0053]For example, in an implementation manner, an on-off key may be set on a drop-down (or may be another direction) notification bar of the terminal to make it convenient for the user to turn off or on the on-off key. When the user enables an automatic-screen-sliding function using the on-off key, the mobile terminal determines that the mobile terminal is currently in the automatic-screen-sliding scenario. Otherwise, the mobile terminal determines that the mobile terminal is not in the automatic-screen-sliding scenario. [0054]Alternatively, in another implementation manner, an automatic-screen-sliding function may be set in advance to be associated with some application programs. These application programs may be application programs, such as a browser, a reading application, and a video application, that the user wants to operate without any hand blocking the screen. In this way, when the user runs the foregoing application programs on the mobile terminal, the mobile terminal determines that the mobile terminal is currently in the automatic-screen-sliding scenario, and after these application programs are exited, the mobile terminal determines that the mobile terminal is not currently in the automatic-screen-sliding scenario. [0055]Alternatively, in another implementation manner, a preset enabling gesture and a preset disabling gesture may be associated with an automatic-screen-sliding function. When a user gesture received by the mobile terminal is consistent with the enabling gesture, it is determined that the mobile terminal is currently in the automatic-screen-sliding scenario, and when a user gesture received by the mobile terminal in the automatic-screen-sliding scenario is consistent with the disabling gesture, the mobile terminal determines that the mobile terminal is not currently in the automatic-screen-sliding scenario. [0056]The foregoing several manners are only examples, and the present disclosure includes, but is not limited to the foregoing several manners. In addition, another possible manner may be used to identify whether the mobile terminal is in the automatic-screen-sliding scenario, and examples are not separately provided herein. [0057]If it is identified that the mobile terminal is in the automatic-screen-sliding scenario, step 202 is performed, otherwise, step 201 continues to be performed. [0058]Step 202: The mobile terminal turns on the first microphone and the second microphone. [0059]Step 203: The mobile terminal detects whether the first microphone and the second microphone both receive sound signals, and if the first microphone and the second microphone both receive sound signals, step 204 is performed, otherwise, step 203 continues to be performed. [0060]Step 204: The mobile terminal separately obtains a characteristics parameter of a first sound signal received by the first microphone and a characteristics parameter of a second sound signal received by the second microphone. [0061]The characteristic parameters of the first sound signal and the second sound signal include at least one of start moments, input duration, and sound loudness of the first sound signal and the second sound signal. When the user blows air to the first microphone and the second microphone, an airflow signal should have a particular strength (for example, loudness of a sound signal reaches a particular decibel (dB) value) and stability (for example, the sound signal needs to exist for a period of time). In addition, the first sound signal and the second sound signal should be relevant, but a difference lies in that the first sound signal and the second sound signal have different start moments and different sound loudness when air is blown in different directions. Therefore, the following steps may be used to determine whether the first sound signal and the second sound signal are sound signals that are generated by the user by blowing air. [0062]Step 205: The mobile terminal determines, according to relevancy between the characteristic parameters of the first sound signal and the second sound signal, whether the first sound signal and the second sound signal are sound signals of a blown airflow. [0063]For example, the characteristics parameter of the sound signal may include the start moment, the input duration, and the sound loudness of the sound signal. Before it is determined, using the relevancy between the characteristic parameters of the first sound signal and the second sound signal, whether the first sound signal and the second sound signal are sound signals of a blown airflow, screening may be first performed using the input duration of the first sound signal and the input duration of the second sound signal in order to reduce processing complexity. A specific method is as follows. [0064]After the first microphone and the second microphone respectively receive the first sound signal and the second sound signal, the input duration of the first sound signal and the input duration of the second sound signal may be f(String), 相关申请的交叉引用 [0001] 本申请为2015年4月28日提交的美国国家阶段国际专利申请PCT/CN2015/077665,其全部内容通过引用并入本文。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种基于吹气动作的移动终端操作方法及移动终端。 背景 [0003] 随着智能平板电脑、智能手机等移动终端的发展,移动终端的屏幕尺寸越来越大,对通过手指触摸进行的屏幕滑动操作造成了一定的限制。 尤其是单手操作时,用手指进行屏幕滑动操作比较笨拙,人机交互效率低。 [0004] 随着移动终端的屏幕尺寸越来越大,双麦克风和多麦克风的设计在这些产品中越来越流行,主要用于语音通话时的降噪处理。 如何利用这些麦克风进行屏幕滑动操作,简化现有的操作方式,提高人机交互效率,是本发明需要解决的问题。 概括 [0005] 本发明实施例提供一种基于吹气动作的移动终端操作方法及移动终端,可以通过移动终端上的麦克风对移动终端进行操作,简化现有操作方式,提高人机交互效率。 . [0006] 根据第一方面,提供一种基于吹气动作操作移动终端的方法,所述移动终端包括至少两个麦克风,所述方法包括分别获取所述至少两个麦克风接收的声音信号的特征参数, 根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型,根据操作类型生成操作指令,执行与操作指令对应的操作。 [0007] 结合第一方面,在第一种可能的实现方式中,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一个。 [0008] 结合第一方面或第一方面的第一种可能的实现方式,在第二种可能的实现方式中,所述方法还包括:根据所述至少两个麦克风接收到的声音信号的特征参数之间的相关性,判断是否 所述至少两个麦克风接收到的声音信号为吹出气流的声音信号,当所述至少两个麦克风接收到的声音信号时,根据获得的所述至少两个麦克风接收到的声音信号的特征参数,执行确定操作类型的操作。 至少两个麦克风为吹出气流的声音信号。 [0009]结合第一方面的第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述至少两个麦克风包括第一麦克风和第二麦克风,如果所述声音信号的特征参数包括所述起始时刻 、输入时长和麦克风接收的声音信号的声音响度,根据获得的至少两个麦克风接收的声音信号的特征参数确定对应的操作类型包括确定操作类型为第一操作 如果第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度, 或者如果接收到第二声音信号的开始时刻,则确定操作类型为第二操作b y 第二麦克风早于第一麦克风接收第一声音信号的开始时刻,第二声音信号的声音响度大于第一声音信号的声音响度。 [0010] 结合第一方面或第一方面的上述任一种可能的实现方式,在第四种可能的实现方式中,所述方法还包括:根据获取的所述至少两个麦克风接收的声音信号的特征参数确定 ,对应于操作类型的操作距离,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0011] 结合第一方面的第三种或第四种可能的实现方式,在第五种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 移动终端,第一操作包括移动终端显示内容从上到下移动,第二操作包括移动终端显示内容从下到上移动,或者如果第一麦克风为麦克风 设置在移动终端左侧,第二麦克风为设置在移动终端右侧的麦克风,第一操作包括移动终端的显示内容从左向右移动,第二操作包括移动终端的移动。 移动终端的显示内容从右到左。 [0012] 结合第一方面的第五种可能的实现方式,在第六种可能的实现方式中,如果第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风 ,第一操作对应的操作距离为移动终端的显示内容从上到下移动的距离,第二操作对应的操作距离为移动终端的显示内容的移动距离 从下向上移动,或者如果第一麦克风为设置在移动终端左侧的麦克风,第二麦克风为设置在移动终端右侧的麦克风,则第一操作对应的操作距离为距离 移动终端的显示内容从左向右移动的距离,以及对应第二个的操作距离 操作是移动终端的显示内容从右向左移动的距离。 [0013]结合第一方面的第三种或第四种可能的实现方式,在第七种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 所述移动终端,所述第一操作包括上翻页操作、从上往下滑动解锁操作或返回操作,所述第二操作包括下翻页操作、从下往上滑动解锁操作, 或者前向操作,或者如果第一麦克风是设置在移动终端左侧的麦克风,第二麦克风是设置在移动终端右侧的麦克风,则第一操作包括向上翻页操作、滑动操作 从左到右解除阻塞或返回操作,第二操作包括从右向左滑动解除阻塞操作、向下翻页操作或前进操作 操作。 [0014] 第二方面,提供一种移动终端,所述移动终端包括至少两个麦克风,所述移动终端还包括监测单元,用于分别获取所述至少两个麦克风接收的声音信号的特征参数,确定 单元,用于根据获取的所述至少两个麦克风接收的声音信号的特征参数确定操作类型; 生成单元,用于根据所述操作类型生成操作指令; 执行单元,用于执行以下操作: 对应操作说明。 [0015] 结合第二方面,在第一种可能的实现方式中,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一个。 [0016] 结合第二方面或第二方面的第一种可能的实现方式,在第二种可能的实现方式中,所述移动终端还包括识别单元,用于根据所述接收到的声音信号的特征参数之间的相关性确定 至少两个麦克风, 所述至少两个麦克风接收的声音信号是否为吹出气流的声音信号, 判断单元根据获取的所述麦克风接收的声音信号的特征参数执行判断操作类型的操作。 当至少两个麦克风接收到的声音信号为吹出气流的声音信号时,至少两个麦克风。 [0017] 结合第二方面的第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述至少两个麦克风包括第一麦克风和第二麦克风,如果所述声音信号的特征参数包括起始时刻 、输入时长、麦克风接收到的声音信号的声音响度,判断单元还用于如果第一麦克风接收到的第一声音信号的开始时刻较早,则判断操作类型为第一操作。 大于第二麦克风接收的第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度,或者如果 第二麦克风接收到的第二声音信号早于第一麦克风接收到的第一声音信号的开始时刻,并且声音 第二声音信号的响度大于第一声音信号的响度。 [0018] 结合第二方面或第二方面的上述任一种可能的实现方式,在第四种可能的实现方式中,所述确定单元,还用于根据获取的所述终端接收到的声音信号的特征参数,确定 至少两个麦克风,操作距离对应操作类型,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0019] 结合第二方面的第三种或第四种可能的实现方式,在第五种可能的实现方式中,如果第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 移动终端,第一操作包括移动终端显示内容从上到下移动,第二操作包括移动终端显示内容从下到上移动,或者如果第一麦克风为麦克风 设置在移动终端左侧,第二麦克风为设置在移动终端右侧的麦克风,第一操作包括移动终端的显示内容从左向右移动,第二操作包括移动终端的移动。 移动终端显示的内容从右到左。 [0020] 结合第二方面的第五种可能的实现方式,在第六种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风 ,第一操作对应的操作距离为移动终端的显示内容从上到下移动的距离,第二操作对应的操作距离为移动终端的显示内容的移动距离 从下向上移动,或者如果第一麦克风为设置在移动终端左侧的麦克风,第二麦克风为设置在移动终端右侧的麦克风,则第一操作对应的操作距离为距离 移动终端的显示内容从左到右移动的距离,以及对应第二个的操作距离 操作是移动终端的显示内容从右向左移动的距离。 [0021] 结合第二方面的第三种或第四种可能的实现方式,在第七种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 所述移动终端,所述第一操作包括上翻页操作、从上往下滑动解锁操作或返回操作,所述第二操作包括下翻页操作、从下往上滑动解锁操作, 或者前向操作,或者如果第一麦克风是设置在移动终端左侧的麦克风,第二麦克风是设置在移动终端右侧的麦克风,则第一操作包括向上翻页操作、滑动操作 从左到右解锁或返回操作,第二操作包括从右到左滑动解锁操作、向下翻页操作或向前 手术。 [0022] 第三方面,提供了一种移动终端,所述移动终端包括至少两个麦克风,所述移动终端还包括处理器和存储器,所述至少两个麦克风、所述处理器和所述存储器通过以下方式连接。 总线,存储器用于存储计算机程序,处理器用于执行计算机程序,处理器执行计算机程序分别获取至少两个麦克风接收的声音信号的特征参数,确定操作 根据获取的至少两个麦克风接收的声音信号的特征参数进行类型,根据操作类型生成操作指令,执行与操作指令对应的操作。 [0023] 结合第三方面,在第一种可能的实现方式中,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一个。 [0024]结合第三方面或第三方面的第一种可能的实现方式,在第二种可能的实现方式中,处理器执行计算机程序,根据至少两个接收到的声音信号的特征参数之间的相关性确定 麦克风,所述至少两个麦克风接收到的声音信号是否为吹出气流的声音信号,并根据获得的所述至少两个麦克风接收到的声音信号的特征参数,在发出声音时,执行确定操作类型的操作。 至少两个麦克风接收到的信号为吹出气流的声音信号。 [0025] 结合第三方面的第一种或第二种可能的实现方式,在第三种可能的实现方式中,所述至少两个麦克风包括第一麦克风和第二麦克风,如果所述声音信号的特征参数包括所述起始时刻 、输入持续时间以及麦克风接收到的声音信号的声音响度,处理器执行计算机程序,如果第一麦克风接收到的第一声音信号的开始时刻较早,则确定操作类型为第一操作。 大于第二麦克风接收的第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度,或者如果 第二麦克风接收到的第二声音信号早于第一麦克风接收到的第一声音信号的开始时刻,并且声音 第二声音信号的响度大于第一声音信号的响度。 [0026] 结合第三方面或第三方面的上述任一种可能的实现方式,在第四种可能的实现方式中,处理器执行计算机程序,根据获取的终端接收的声音信号的特征参数确定 至少两个麦克风,操作距离对应操作类型,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0027] 结合第三方面的第三种或第四种可能的实现方式,在第五种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 移动终端,第一操作包括移动终端显示内容从上到下移动,第二操作包括移动终端显示内容从下到上移动,或者如果第一麦克风为麦克风 设置在移动终端左侧,第二麦克风为设置在移动终端右侧的麦克风,第一操作包括移动终端的显示内容从左向右移动,第二操作包括移动终端的移动。 移动终端的显示内容从右到左。 [0028] 结合第三方面的第五种可能的实现方式,在第六种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风 ,第一操作对应的操作距离为移动终端的显示内容从上到下移动的距离,第二操作对应的操作距离为移动终端的显示内容的移动距离 从下向上移动,或者如果第一麦克风为设置在移动终端左侧的麦克风,第二麦克风为设置在移动终端右侧的麦克风,则第一操作对应的操作距离为距离 移动终端的显示内容从左向右移动的距离,以及对应第二个的操作距离 操作是移动终端的显示内容从右向左移动的距离。 [0029] 结合第三方面的第三种或第四种可能的实现方式,在第七种可能的实现方式中,若第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风。 所述移动终端,所述第一操作包括上翻页操作、从上往下滑动解锁操作或返回操作,所述第二操作包括下翻页操作、从下往上滑动解锁操作, 或者前向操作,或者如果第一麦克风是设置在移动终端左侧的麦克风,第二麦克风是设置在移动终端右侧的麦克风,则第一操作包括向上翻页操作、滑动操作 从左到右解除阻塞或返回操作,第二操作包括从右向左滑动解除阻塞操作、向下翻页操作或前进操作 操作。 [0030] 本发明实施例提供一种基于吹气动作的移动终端操作方法及移动终端。 移动终端设置有至少两个麦克风。 当用户对至少两个麦克风吹气时,分别获取至少两个麦克风接收到的声音信号的特征参数,该特征参数包括声音信号的起始时刻、输入时长或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离)。 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率。 附图说明 [0031] 为了更清楚地描述本发明实施例中的技术方案,下面对描述实施例所需的附图进行简单说明。 以下描述中的附图示出了本发明的一些实施例,本领域普通技术人员在没有做出创造性劳动的情况下仍可以从这些附图中导出其他附图。 [0032] 图1为本发明基于吹气动作操作移动终端的方法流程示意图, [0033] 图2为本发明另一种基于吹气动作操作移动终端的方法流程示意图; [0034] 图3A和图3B是根据本发明实施例的不同吹气方向对应的声音信号示意图, [0035] 图4为本发明实施例的操作效果示意图, [0036] 图5为本发明实施例提供的另一种操作效果示意图。 [0037] 图6为本发明实施例提供的另一种操作效果示意图, [0038] 图7为本发明实施例提供的另一种操作效果示意图, [0039] 图8为本发明实施例提供的一种移动终端的结构示意图, [0040] 图9为本发明实施例提供的另一种移动终端的结构示意图, [0041] 图10为本发明实施例提供的又一种移动终端的结构示意图。 具体实施方式 [0042]为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。 以上所述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0043] 本发明实施例提供一种基于吹气动作的移动终端操作方法。 如图1所示,该方法包括以下步骤。 [0044] 步 101 :分别获取至少两个麦克风接收到的声音信号的特征参数。 [0045] 步 102 :根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型。 [0046] 至少两个麦克风接收到的声音信号的特征参数是能够代表至少两个麦克风接收到的声音信号的物理特性的参数。 特征参数可用于区分和识别不同的声音信号。 特征参数可以是至少两个麦克风接收到的声音信号的起始时刻、输入时长和声音响度。 [0047] 步 103 :根据操作类型生成操作指令。 [0048] 步 104 :执行与操作指令对应的操作。 [0049] 本发明实施例提供一种基于吹气动作的移动终端操作方法。 移动终端设置有至少两个麦克风。 当用户向至少两个麦克风吹气时,分别获得至少两个麦克风接收到的声音信号的特征参数。 根据获得的至少两个麦克风接收的声音信号的特征参数确定操作类型。 根据操作类型生成操作指令。 执行对应于操作指令的操作。 因此,可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率。 [0050] 为使本领域技术人员更加清楚地理解本发明实施例提供的技术方案,下面以具体的方式对本发明实施例提供的基于吹气动作的移动终端操作方法进行详细说明。 体现。 为了便于描述,以第一麦克风为设置在移动终端顶部的麦克风,第二麦克风为设置在移动终端底部的麦克风为例进行说明。 如图2所示,该方法包括以下步骤。 [0051] 步 201 :移动终端识别移动终端是否处于自动滑屏场景。 [0052] 在本发明实施例中,“屏幕滑动”可以理解为移动终端屏幕上显示的内容的移动。 移动包括但不限于触摸解锁、滑动解锁、显示内容的上下移动或左右移动、上翻页和下翻页。 自动滑屏场景可以理解为无需用户进行触摸操作即可进行上述“滑屏”操作的场景。 [0053]例如,在一种实施方式中,可以在终端的下拉(或者可以是其他方向)通知栏上设置开关键,以方便用户对开关键进行关闭或打开。 . 当用户通过开关键开启自动滑屏功能时,移动终端确定移动终端当前处于自动滑屏场景。 否则,移动终端确定移动终端不处于自动滑屏场景。 [0054] 或者,在另一种实施方式中,可以预先设置自动滑屏功能与一些应用程序相关联。 这些应用程序可以是用户想要在没有任何手遮挡屏幕的情况下操作的应用程序,例如浏览器、阅读应用、视频应用等。 这样,当用户在移动终端上运行上述应用程序时,移动终端确定移动终端当前处于自动滑屏场景,退出这些应用程序后,移动终端确定 移动端目前不在自动滑屏场景。 [0055] 或者,在另一种实施方式中,可以将预设的启用手势和预设的禁用手势与自动滑屏功能相关联。 当移动终端接收到的用户手势与启用手势一致时,确定移动终端当前处于自动滑屏场景,当移动终端接收到的用户手势处于自动滑屏场景时 滑动场景与禁用手势一致,移动终端判断移动终端当前不在自动滑屏场景。 [0056] 上述几种方式仅为示例,本发明包括但不限于上述几种方式。 此外,还可以采用其他可能的方式来识别移动终端是否处于自动滑屏场景,在此不再一一举例。 [0057] 如果识别出移动终端处于自动滑屏场景,则步骤 202 执行,否则,步骤 201 继续执行。 [0058] 步 202 :移动终端开启第一麦克风和第二麦克风。 [0059] 步 203 :移动终端检测第一麦克风和第二麦克风是否都接收到声音信号,如果第一麦克风和第二麦克风都接收到声音信号,则步骤 204 执行,否则,步骤 203 继续执行。 [0060] 步 204 :移动终端分别获取第一麦克风接收的第一声音信号的特征参数和第二麦克风接收的第二声音信号的特征参数。 [0061] 第一声​​音信号和第二声音信号的特征参数包括第一声音信号和第二声音信号的起始时刻、输入时长和声音响度中的至少一个。 当用户向第一麦克风和第二麦克风吹气时,气流信号应该具有特定的强度(例如,声音信号的响度达到特定的分贝(dB)值)和稳定性(例如,声音信号需要 存在一段时间)。 另外,第一声音信号和第二声音信号应该是相关的,但区别在于第一声音信号和第二声音信号在不同方向吹气时的起始时刻不同,声音响度也不同。 因此,可以通过以下步骤来判断第一声音信号和第二声音信号是否为用户通过吹气产生的声音信号。 [0062] 步 205 :移动终端根据第一声音信号和第二声音信号的特征参数的相关性判断第一声音信号和第二声音信号是否为吹出气流的声音信号。 [0063]例如,声音信号的特征参数可以包括声音信号的开始时刻、输入时长、声音响度。 在确定第一声音信号和第二声音信号的特征参数之间的相关性,第一声音信号和第二声音信号是否为吹出气流的声音信号之前,可以先使用输入的时长进行筛选 第一声​​音信号的输入时间和第二声音信号的输入时长,以降低处理复杂度。 具体方法如下。 [0064] 在第一麦克风和第二麦克风分别接收到第一声音信号和第二声音信号后,可以先将第一声音信号的输入时长和第二声音信号的输入时长与预设时长进行比较。 [0065] 如果第一声音信号的输入持续时间和第二声音信号的输入持续时间小于预设持续时间,则确定第一声音信号和第二声音信号不是吹出气流的声音信号。 [0066] 第一声​​音信号和第二声音信号可以是吹出气流的声音信号,为了保证第一声音信号和第二声音信号的输入时长和输入时长为 第二声音信号大于或等于预设时长。 [0067] 相关性是指两个对象之间的相关程度,一般可以用百分比来表示。 因此,第一声音信号和第二声音信号之间的相关性可以被解释为第一声音信号和第二声音信号之间的相关程度。 [0068] 例如,第一声音信号和第二声音信号的特征参数还可以包括第一声音信号和第二声音信号的频率。 因此,可以得到第一声音信号的频率和第二声音信号的频率,并根据第一声音信号的频率和第二声音信号的频率计算第一声音信号和第二声音信号的相关度。 第二个声音信号。 当用户向第一麦克风和第二麦克风吹气时,只有一个声源。 因此,如果第一声音信号和第二声音信号是吹出气流的声音,则第一声音信号和第二声音信号的频率应该相同或者误差很小。 因此,获得的相关性应该等于 1 或大约为 1。 [0069] 或者,可以根据第一声音信号的声音响度在一段时间内的变化趋势和第二声音信号的声音响度在一段时间内的变化趋势计算第一声音信号与第二声音信号的相关度。 同时。 可以通过获得第一声音信号的声音响度值和 采样时间内多个采样点的第二个声音信号。 当变化趋势越接近时,相关度也越接近1。或者,可以通过比较第一声音信号在一段时间内的声音响度波形得到第一声音信号与第二声音信号的相关度。 具有第二声音信号的声音响度的波形。 波形越接近,相关度也越接近1。采样时间和时间段可以是第一声音信号和第二声音信号的输入时长,也可以是小于输入时长的一段时间。 [0070] 当然,为了更准确的识别,上述两种方法可以结合使用。 此外,上述以频率和声音响度计算相关度的方法仅为示例,还可以使用其他可用于评估两个声音信号之间的相关度的参数。 [0071]在获得第一声音信号和第二声音信号的相关度后,可以将获得的相关度与预设的相关度阈值进行比较。 [0072] 当获得的相关度大于或等于相关度阈值时,确定第一声音信号和第二声音信号为被吹出的气流产生的声音信号,否则确定第一声音信号和第二声音 信号不是由吹出的气流产生的声音信号。 这样可以排除其他原因产生的声音信号,避免误操作。 [0073] 在确定第一声音信号和第二声音信号是由吹出的气流产生的声音信号后,步骤 206 执行,否则返回步骤 203 . [0074] 步 206 :移动终端根据获取的第一声音信号和第二声音信号的特征参数确定操作类型,第一声音信号和第二声音信号的特征参数包括开始时刻、输入时长和声音响度。 第一声​​音信号和第二声音信号。 [0075] 进一步地,当空气吹向不同方向时,第一声音信号和第二声音信号具有不同的开始时刻和不同的声音响度。 例如,当移动终端从下向上吹空气时,第二麦克风首先接收到声音信号,由于用户的嘴巴距离第二麦克风较近,因此第二麦克风接收到的第二声音信号的响度较大。 第二麦克风大于第一麦克风接收的第一声音信号的响度。 反之,当移动终端从上往下吹气时,第一麦克风首先接收到声音信号,由于用户的嘴巴距离第一麦克风较近,因此第一麦克风接收到的第一声音信号的响度较大。 第一麦克风大于第二麦克风接收到的第二声音信号的响度。 [0076] 因此,可以根据获得的第一声音信号和第二声音信号的起始时刻和声音响度来确定吹气方向。 图3A和图3B为本发明实施例的不同吹气方向对应的声音信号示意图。 [0077] 首先,如图3B所示,如果第一声音信号的开始时刻早于第二声音信号的开始时刻,并且第一声音信号的声音响度大于第二声音信号的声音响度, 确定用户从移动终端的上向下吹气,从而可以确定操作类型为第一操作。 [0078] 如图3A所示,若第二声音信号的起始时刻早于第一声音信号的起始时刻,且第二声音信号的声音响度大于第一声音信号的声音响度,则为 确定用户从移动终端的底部向顶部吹气,从而可以确定操作类型为第二操作。 [0079] 需要说明的是,由于第一声音信号和第二声音信号的声音响度可能在第一声音信号和第二声音信号的整个输入时长内发生波动,因此可以采用以下方法来比较第一声音信号和第二声音信号的声音响度 声音信号和第二声音信号。 [0080] 如果第一个声音信号在时刻 t 的声音响度 1 大于第二个声音信号在t时刻的声音响度 2 ,则确定第一声音信号的声音响度大于第二声音信号的声音响度。 时刻 t 1 是第一个声音信号的输入持续时间内的任何时刻,时刻 t 之间的差 2 和时刻 t 1 为Δt,Δt为第二声音信号的起始时刻与第一声音信号的起始时刻之差。 [0081] 同样,如果第二个声音信号在时刻 t 的声音响度 2大于第一个声音信号在时刻 t 的声音响度 1 ,第二声音信号的声音响度大于第一声音信号的声音响度。 时刻 t 2 是第二声音信号输入持续时间内第二声音信号的任何时刻,时刻t之间的差 1 和时刻 t 2 为Δt,Δt为第一声音信号的起始时刻与第二声音信号的起始时刻之差。 [0082] 或者,可以从第一声音信号和第二声音的整个输入持续时间中选择第一声音信号和第二声音信号都稳定的时间段,例如图3A和图3B中的时间段T。 信号。 如果在T内任意时刻第一声音信号的声音响度大于第二声音信号的声音响度,则确定第一声音信号的声音响度大于第二声音信号的声音响度。 如果在T内任意时刻第二声音信号的声音响度大于第一声音信号的声音响度,则确定第二声音信号的声音响度大于第一声音信号的声音响度。 [0083] 例如,可以根据需要预先配置第一操作和第二操作的具体内容。 第一操作对应于从移动终端的顶部到底部的吹气,第二操作对应于从移动终端的底部到顶部的吹气。 例如,第一操作可以是移动终端的显示内容从上到下的移动,或者是翻页操作,或者是从上到下滑动解锁的操作(可以理解为移动的操作) 在锁定屏幕界面中从上到下的滑块解锁)。 例如,如图4所示,第一操作是显示内容从上到下的移动,或者第一操作可以是浏览器或类似应用程序运行过程中的后退操作(图4未示出)。 [0084] 第二操作可以是移动终端的显示内容从下往上移动,也可以是向下翻页操作,或者是从下往上滑动解锁的操作(可以理解为滑块从下往上移动的操作)。 在锁屏界面从下到上解锁)。 例如,如图5所示,第二操作是显示内容从下向上移动,或者第二操作可以是浏览器或类似应用程序运行过程中的前进操作(图5未示出)。 [0085] 该方法还可以包括以下步骤。 [0086] 步 207 :移动终端根据获取的第一声音信号和第二声音信号的特征参数,确定操作类型对应的操作距离。 操作距离可以称为操作路径。 [0087] 例如,当第一操作是移动终端的显示内容从上到下移动或者从上到下滑动解锁操作,第二操作是移动终端的显示内容从上往下移动时 从下到上或从下到上滑动解锁的操作,还需要获取操作距离。 [0088] 以第一操作为移动终端的显示内容自上而下移动为例,第一操作对应的操作距离为移动终端的显示内容自下而上移动的距离 . 同样,当第二操作为移动终端的显示内容从下向上移动时,第二操作对应的操作距离为移动终端的显示内容从下向上移动的距离。 [0089]由于显示内容移动的距离可以用像素值来衡量,因此第一操作对应的操作距离可以是移动终端的显示内容从下到上需要移动的像素值, 第二操作对应的操作距离可以是移动终端的显示内容从下向上移动所需的像素值。 [0090] 同理,当第一操作为上下滑动解锁操作时,第一操作对应的操作距离为解锁界面中的滑块需要上下移动的像素值。 当第二操作为从下向上滑动解锁操作时,第二操作对应的操作距离为解锁界面中的滑块需要从下向上移动的像素值。 [0091] 另外,可以根据第一声音信号的输入时长或第二声音信号的输入时长中的至少一个来确定第一操作或第二操作对应的操作距离。 以像素值为例,可以直接根据第一声音信号的输入时长和第二声音信号的输入时长确定需要移动的像素值的大小。 例如,可以预设不同输入时长对应的待移动像素值,也可以预设每单位时长对应的单位像素值。 在得到第一声音信号的输入时长和第二声音信号的输入时长后,可以根据输入时长得到对应的待移动像素值。 如果声音信号是用户通过吹气产生的,则第一声音信号的输入持续时间和第二声音信号的输入持续时间应该相等或有很小的误差。 因此,在计算时,需要使用第一声音信号或第二声音信号中的至少一个的输入时长。 [0092] 步 208 :移动终端根据操作类型生成操作指令。 [0093] 当然,如果存在与确定的操作类型对应的操作距离,则需要根据操作类型和操作距离生成操作指令。 [0094] 步 209 :移动终端执行与操作指令对应的操作。 [0095] 可选地,作为另一种实施方式,在本实施例中,第一麦克风可以是设置在移动终端左侧的麦克风,第二麦克风可以是设置在移动终端右侧的麦克风。 [0096] 在这种情况下,相应地,第一操作对应于移动终端从左到右的吹气,第二操作对应于移动终端的从右到左的吹气。 例如,第一操作可以是移动终端的显示内容从左向右移动,或者是向上翻页操作,或者是从左向右滑动解锁的操作(可以理解为移动的操作)。 在锁定屏幕界面中从左到右的滑块解锁)。 例如,如图6所示,第一操作是显示内容从左向右移动,或者第一操作可以是浏览器或类似应用程序运行过程中的后退操作(图6中未示出)。 [0097] 第二操作可以是移动终端的显示内容从右向左移动,也可以是向下翻页操作,或者是从右向左滑动解除阻塞的操作(可以理解为从 在锁屏界面从右到左解锁)。 例如,如图7所示,第二操作是移动终端的显示内容从右向左移动,或者第二操作可以是浏览器运行过程中的前进操作(图7中未示出),或者 类似的应用程序。 [0098]另外,当第一麦克风和第二麦克风设置在移动终端的左右两侧时,基于吹气动作操作移动终端的方法与上述第一麦克风和第二麦克风的方法相同。 第二麦克风设置在移动终端的顶部和底部。 [0099] 此外,需要注意的是,步骤 204 其中,移动终端分别获取第一麦克风接收到的第一声音信号的特征参数和第二麦克风接收到的第二声音信号的特征参数可以周期性地执行。 即每隔一段预设时间,获取第一声音信号的特征参数和第二声音信号的特征参数,剩下的步骤 205 迈出一步 209 执行。 [0100] 预设时间可以设置得很短,例如200毫秒(ms)。 也就是步 203 迈出一步 209 每 200 ms 执行一次。 这样,移动终端可以在用户吹气的同时进行操作。 在显示内容从下到上移动的例子中,移动终端的显示内容可以在用户吹气的同时从下到上移动,当用户停止吹气时,移动终端的显示内容可以从下到上移动。 移动终端也停止移动。 这更便于用户控制操作过程。 [0101] 本发明实施例提供一种基于吹气动作的移动终端操作方法。 移动终端设置有至少两个麦克风。 当用户向至少两个麦克风吹气时,分别获得至少两个麦克风接收到的声音信号的特征参数。 特征参数包括声音信号的开始时刻、输入持续时间或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离)。 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,可以通过移动终端上的麦克风对移动终端进行操作,从而简化现有的操作方式,提高人机交互效率。 [0102] 本发明实施例提供一种移动终端 01 . 移动终端 01 包括至少两个麦克风 010 . 如图8所示,移动终端 01 还包括一个监控单元 011 用于分别获取至少两个麦克风接收到的声音信号的特征参数 010 , 确定单元 012 用于根据获取的至少两个麦克风接收的声音信号的特征参数确定操作类型 010 , 一个生成单元 013 用于根据操作类型生成操作指令,以及执行单元 014 用于执行与所述操作指令对应的操作。 [0103] 可选地,所述声音信号的特征参数包括麦克风接收到的声音信号的起始时刻、输入时长或声音响度中的至少一种。 [0104] 可选的,如图9所示,移动终端 01 还包括识别单元 015 用于根据至少两个麦克风接收到的声音信号的特征参数之间的相关性确定 010 , 至少两个麦克风是否接收到声音信号 010 为吹出气流的声音信号,判断单元 012 根据获得的至少两个麦克风接收的声音信号的特征参数,执行确定操作类型的操作 010 当至少两个麦克风接收到声音信号时 010 是吹出气流的声音信号。 [0105]可选地,至少两个麦克风 010 包括第一麦克风和第二麦克风,如果声音信号的特征参数包括麦克风接收到的声音信号的开始时刻、输入时长和声音响度,则在根据获得的特征确定操作类型时 至少两个麦克风接收到的声音信号的参数 010 , 确定单元 012 还用于如果所述第一麦克风接收到的第一声音信号的开始时刻早于所述第二麦克风接收到的第二声音信号的开始时刻,则确定所述操作类型为第一操作,并且所述第一麦克风的声音响度 声音信号大于第二声音信号的声音响度,或者如果第二麦克风接收到的第二声音信号的开始时刻早于第二麦克风接收到的第一声音信号的开始时刻,则确定操作类型为第二操作 第一麦克风,第二声音信号的声音响度大于第一声音信号的声音响度。 [0106] 可选的,确定单元 012 还用于根据获取的所述至少两个麦克风接收的声音信号的特征参数确定 010 , 操作类型对应的操作距离, 对应的, 生成单元 013 还用于根据操作类型和操作距离生成操作指令。 [0107] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 01 第二麦克风为设置在移动终端底部的麦克风 01 ,第一操作包括移动终端显示内容的移动 01 从上到下,第二操作包括移动终端显示内容的移动 01 从下到上,或者如果第一麦克风是设置在移动终端左侧的麦克风 01 第二麦克风为设置在移动终端右侧的麦克风 01 ,第一操作包括移动终端显示内容的移动 01 从左到右,第二操作包括移动终端显示内容的移动 01 从右到左。 [0108] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 01 第二麦克风为设置在移动终端底部的麦克风 01 ,第一操作对应的操作距离为移动终端显示内容的距离 01 从上到下移动,第二操作对应的操作距离为移动终端显示内容的距离 01 从下向上移动,或者如果第一麦克风是设置在移动终端左侧的麦克风 01 第二麦克风为设置在移动终端右侧的麦克风 01 ,第一操作对应的操作距离为移动终端显示内容的距离 01 从左向右移动,第二操作对应的操作距离为移动终端显示内容的距离 01 从右向左移动。 [0109] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 01 第二麦克风为设置在移动终端底部的麦克风 01 ,第一操作包括上翻页操作、从上往下滑动解锁或后退操作,第二操作包括下翻页操作、从下往上滑动解锁或前进 操作,或者如果第一麦克风是设置在移动终端左侧的麦克风 01 第二麦克风为设置在移动终端右侧的麦克风 01,第一操作包括向上翻页操作、从左向右滑动解除阻塞或返回操作,第二操作包括从右向左滑动解除阻塞、向下翻页操作或向前 手术。 [0110] 本实施例用于实现上述方法实施例。 本实施例中各单元的工作流程和工作原理参见上述方法实施例中的描述。 此处不再赘述。 [0111] 本发明实施例提供的移动终端 01 . 移动终端 01 配备至少两个麦克风 010 . 当用户向至少两个麦克风吹气时 010 , 至少两个麦克风接收到的声音信号的特征参数 010 分别获得。 特征参数包括声音信号的开始时刻、输入持续时间或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离) 010 . 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,移动端 01 可以使用至少两个麦克风进行操作 010 在移动端 01 ,从而简化现有的操作模式,提高人机交互效率。 [0112] 本发明实施例还提供了另一种移动终端 02 . 移动终端 02 包括至少两个麦克风 020 . 如图 10 所示,移动终端 02 还包括一个处理器 021 和一段记忆 022 . 处理器 021 , 至少两个麦克风 020 , 和内存 022 使用总线连接 023 . 记忆 022 被配置为存储计算机程序 0221 . 处理器 021 被配置为执行计算机程序 0221 . 处理器 021 执行计算机程序 0221 分别获取至少两个麦克风接收到的声音信号的特征参数 020 ,根据得到的至少两个麦克风接收到的声音信号的特征参数确定操作类型 020 ,根据操作类型生成操作指令,执行与操作指令对应的操作。 [0113] 可选地,所述声音信号的特征参数包括所述至少两个麦克风接收到的声音信号的开始时刻、输入时长或声音响度中的至少一种。 020 . [0114] 可选地,处理器 021 执行计算机程序 0221 根据至少两个麦克风接收到的声音信号的特征参数之间的相关性来确定 020 , 至少两个麦克风是否接收到声音信号 020 为吹出气流的声音信号,根据得到的至少两个麦克风接收到的声音信号的特征参数进行判断操作类型的操作 020 当至少两个麦克风接收到声音信号时 020 是吹出气流的声音信号。 [0115] 可选地,至少两个麦克风 020 包括第一麦克风和第二麦克风,如果声音信号的特征参数包括至少两个麦克风接收到的声音信号的开始时刻、输入时长和声音响度 020 , 处理器 021 执行计算机程序 0221如果第一麦克风接收到的第一声音信号的开始时刻早于第二麦克风接收到的第二声音信号的开始时刻,则判断操作类型为第一操作,并且第一声音信号的声音响度为 大于第二声音信号的声音响度,或者如果第二麦克风接收到的第二声音信号的开始时刻早于第一麦克风接收到的第一声音信号的开始时刻,则确定操作类型为第二操作 ,且第二声音信号的声音响度大于第一声音信号的声音响度。 [0116] 可选地,处理器 021 执行计算机程序 0221 根据得到的至少两个麦克风接收到的声音信号的特征参数来确定 020 ,对应于操作类型的操作距离,根据操作类型生成操作指令包括根据操作类型和操作距离生成操作指令。 [0117] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 02 第二麦克风为设置在移动终端底部的麦克风 02 ,第一操作包括移动终端显示内容的移动 02 从上到下,第二操作包括移动终端显示内容的移动 02 从下到上,或者如果第一麦克风是设置在移动终端左侧的麦克风 02 第二麦克风为设置在移动终端右侧的麦克风 02 ,第一操作包括移动终端显示内容的移动 02 从左到右,第二操作包括移动终端显示内容的移动 02 从右到左。 [0118] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 02 第二麦克风为设置在移动终端底部的麦克风 02 ,第一操作对应的操作距离为移动终端显示内容的距离 02 从上到下移动,第二操作对应的操作距离为移动终端显示内容的距离 02 从下向上移动,或者如果第一麦克风是设置在移动终端左侧的麦克风 02 第二麦克风为设置在移动终端右侧的麦克风 02 ,第一操作对应的操作距离为移动终端显示内容的距离 02 从左向右移动,第二操作对应的操作距离为移动终端显示内容的距离 02 从右向左移动。 [0119] 可选的,如果第一麦克风为设置在移动终端顶部的麦克风 02 第二麦克风为设置在移动终端底部的麦克风 02 ,第一操作包括上翻页操作,或从上到下滑动解除阻塞的操作,或返回操作,第二操作包括向下翻页操作,或从下到上滑动解除阻塞的操作,或 向前操作,或者如果第一麦克风是设置在移动终端左侧的麦克风 02 第二麦克风为设置在移动终端右侧的麦克风 02 ,第一操作包括向上翻页操作,或从左向右滑动解锁操作,或返回操作,第二操作包括从右向左滑动解锁操作,或向下翻页操作,或 前向操作。 [0120] 本实施例用于实现上述方法实施例。 本实施例中各单元的工作流程和工作原理参见上述方法实施例中的描述。 此处不再赘述。 [0121]本发明实施例提供的移动终端 02 . 移动终端 02 配备至少两个麦克风 020 . 当用户向至少两个麦克风吹气时 020 , 至少两个麦克风接收到的声音信号的特征参数 020 分别获得。 特征参数包括声音信号的开始时刻、输入持续时间或声音响度。 根据获得的至少两个麦克风接收到的声音信号的特征参数确定操作类型(和操作距离) 020 . 根据操作类型(和操作距离)生成操作指令。 执行对应于操作指令的操作。 因此,移动端 02 可以在移动终端上使用麦克风进行操作,简化了现有的操作方式,提高了人机交互效率。 [0122] 在本发明提供的几个实施例中,应当理解,所公开的装置和方法可以通过其他方式实现。 例如,所描述的设备实施例仅仅是示例。 例如,单元划分仅仅是逻辑上的功能划分,实际实现中还可以是其他的划分。 例如,可以将多个单元或组件组合或集成到另一个系统中,或者可以忽略或不执行某些特征。 此外,显示或讨论的相互耦合或直接耦合或通信连接可以使用一些接口来实现。 装置或单元之间的间接耦合或通信连接可以以电子、机械或其他形式实现。 [0123] 被描述为独立部分的单元可以是物理上独立的,也可以不是物理上的,作为单元显示的部分可以是物理单元,也可以不是物理单元,可以位于一个位置,或者可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部单元来实现本实施例方案的目的。 [0124] 另外,本发明实施例中的功能单元可以集成在一个处理单元中,也可以是各个单元在物理上单独存在,或者两个或多个单元集成在一个单元中。 集成单元可以以硬件的形式实现,也可以在软件功能单元的基础上以硬件的形式实现。 [0125] 当上述集成单元以软件功能单元的形式实现时,该集成单元可以存储在计算机可读存储介质中。 软件功能单元存储在存储介质中,包括若干指令,用于指示计算机设备(可以是个人计算机、服务器或网络设备)或处理器执行上述方法的部分步骤。 本发明的实施例。 上述存储介质包括任何可以存储程序代码的介质,如通用串行总线(USB)闪存盘、移动硬盘、只读存储器(ROM)、随机存取存储器(RAM)、磁盘等。 ,或光盘。 [0126] 本领域技术人员可以清楚地理解,为了描述的方便和简洁,以上述功能模块的划分为例进行说明。 在实际应用中,上述功能可以根据需要分配到不同的功能模块中实现,即将装置的内部结构划分为不同的功能模块来实现上述全部或部分功能。 上述装置的详细工作过程可以参见上述方法实施例中的对应过程,在此不再赘述。 [0127]最后需要说明的是,上述实施例仅用于说明本发明的技术方案,并不用于限制本发明。 尽管结合前述实施例对本发明进行了详细描述,但本领域普通技术人员应当理解,对于前述实施例中描述的技术方案,仍然可以进行修改或者对其部分或全部技术特征进行等同替换。 ,而不脱离本发明实施例技术方案的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN107005609A(String), CN107005609B(String), EP3282680A1(String), EP3282680A4(String), EP3282680B1(String), US20180139553A1(String), WO2016172846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN107005609A(String), CN107005609B(String), EP3282680A1(String), EP3282680A4(String), EP3282680B1(String), US20180139553A1(String), WO2016172846A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN107005609A(String), CN107005609B(String), EP3282680A1(String), EP3282680A4(String), EP3282680B1(String), US20180139553A1(String), WO2016172846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:19.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271631(Integer), CN107005609A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271631(Integer), CN107005609B(String), 1049420(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271631(Integer), EP3282680A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271631(Integer), EP3282680A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271631(Integer), EP3282680B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271631(Integer), US20180139553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271631(Integer), WO2016172846A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN107005609B(String), CN107005609B(String), 1596729600(Integer), 271631(Integer), 185916(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.311 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185983(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185983(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185983(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185983(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.534 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.640 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:20.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20210075461A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Signal processing method and circuit of mobile terminal and mobile terminal(String), 移动终端的信号处理方法及电路及移动终端(String), US20210075461A1(String), A signal processing method and circuit of a mobile terminal and a mobile terminal are provided, by sending a signal detected by operating an antenna body as a sensing pad of a sensor to a microprocessor, the microprocessor determines a usage state of the mobile terminal according to the signal, generates a control signal according to the usage state of the mobile terminal, and controls a tuning circuit to switch tuning paths through the control signal so as to perform a tuning process on a signal from a mobile terminal signal source or the antenna body.(String), 一种移动终端的信号处理方法和电路及移动终端,通过将作为传感器的感应垫的天线体操作检测到的信号发送给微处理器,微处理器根据以下情况判断移动终端的使用状态。 信号,根据移动终端的使用状态产生控制信号,通过控制信号控制调谐电路切换调谐路径,从而对来自移动终端信号源或天线本体的信号进行调谐处理 .(String), US16/644804(String), 1527091200(Integer), US20210075461A1(String), 1615392000(Integer), 美国(String), 2(Integer), CN(String), 3(Integer), 0(Integer), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185984(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\bc8110aaeca34fb59b3f0437ebe7c4ec.png(String), 185984(Integer), bc8110aaeca34fb59b3f0437ebe7c4ec.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.409 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.409 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Signal processing method and circuit of mobile terminal and mobile terminal(String), 移动终端的信号处理方法及电路及移动终端(String), US20210075461A1(String), A signal processing method and circuit of a mobile terminal and a mobile terminal are provided, by sending a signal detected by operating an antenna body as a sensing pad of a sensor to a microprocessor, the microprocessor determines a usage state of the mobile terminal according to the signal, generates a control signal according to the usage state of the mobile terminal, and controls a tuning circuit to switch tuning paths through the control signal so as to perform a tuning process on a signal from a mobile terminal signal source or the antenna body.(String), 一种移动终端的信号处理方法和电路及移动终端,通过将作为传感器的感应垫的天线体操作检测到的信号发送给微处理器,微处理器根据以下情况判断移动终端的使用状态。 信号,根据移动终端的使用状态产生控制信号,通过控制信号控制调谐电路切换调谐路径,从而对来自移动终端信号源或天线本体的信号进行调谐处理 .(String), US16/644804(String), 1527091200(Integer), US20210075461A1(String), 1615392000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 3(Integer), 0(Integer), \20230420\bc8110aaeca34fb59b3f0437ebe7c4ec.png(String), 12(Integer), 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.444 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.444 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.444 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.478 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.478 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 1. A signal processing circuit of a mobile terminal, comprising: an antenna body, a sensor connected with the antenna body, a microprocessor and a tuning circuit having a plurality of tuning paths,wherein the tuning circuit is connected between a mobile terminal signal source and the antenna body, and the microprocessor is connected with the sensor and the tuning circuit, respectively,the sensor is configured to send a signal detected by operating the antenna body as a sensing pad of the sensor to the microprocessor,the microprocessor is configured to receive the signal, determine a usage state of the mobile terminal according to the signal, generate a control signal according to the usage state of the mobile terminal, and control the tuning circuit to switch the tuning paths through the control signal to perform a tuning process on a signal from the mobile terminal signal source or the antenna body.(String), 1.存储介质,其中所述存储介质包括存储的程序,所述程序在被处理器执行时使处理器执行根据权利要求8所述的信号处理方法。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 2. The signal processing circuit of claim 1, wherein the signal processing circuit further comprises an isolation device which is a lumped inductive element, the sensor is connected with the antenna body through the isolation device, andwherein the isolation device is configured to isolate interference of a communication signal on the signal detected by the sensor.(String), 12.处理器,其中所述处理器,用于运行程序,所述处理器执行所述程序时,执行如权利要求8所述的信号处理方法。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 3. The signal processing circuit of claim 1, wherein the sensor is a capacitive proximity sensor.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 4. The signal processing circuit of claim 1, wherein,the tuning circuit comprises a tuning path T1 and a tuning path T2, the tuning path T1 comprises inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected with one stationary contact of a first switch element, and one end of the capacitor C3 is connected with a signal feed point of the antenna body,the tuning path T2 comprises inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to the other one stationary contact of the first switch element, and one end of the capacitor C5 is connected with the signal feed point of the antenna body.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 5. The signal processing circuit of claim 4, wherein the signal processing circuit comprises a second switch element, the mobile terminal signal source comprises a radio frequency circuit and a baseband processing circuit, andwherein a grounding point GND1 and a grounding point GND2 of the antenna body are respectively connected with two stationary contacts of the second switch element;control ends of the first switch element and the second switch element are both connected with one end of the microprocessor, and the other end of the microprocessor is connected with the sensor;a moving contact of the first switch element is connected with one end of the radio frequency circuit, the other end of the radio frequency circuit is connected with the baseband processing circuit, and a moving contact of the second switch element is grounded.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 6. The signal processing circuit of claim 4 or 5, wherein the tuning paths have a well-type circuit structure, a T-type circuit structure, or a it-type circuit structure.(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 7. A mobile terminal comprising the signal processing circuit of claim 1.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 8. A signal processing method of a mobile terminal, comprising:detecting a signal by operating an antenna body of the mobile terminal as a sensing pad of a sensor;determining a usage state of the mobile terminal according to the signal; andperforming a tuning process on a signal from a mobile terminal signal source or the antenna body according to the usage state of the mobile terminal.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 9. The signal processing method of claim 8, wherein determining the usage state of the mobile terminal according to the signal comprises:detecting a change condition of a capacitance as a human body approaches through the sensor and the antenna body of the mobile terminal; anddetermining the usage state of the mobile terminal according to the change condition.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 10. The signal processing method according to claim 8, wherein performing the tuning process on the signal from the mobile terminal signal source or the antenna body according to the usage state of the mobile terminal comprises:performing the tuning process on the signal from the mobile terminal signal source or the antenna body by switching a tuning circuit of the mobile terminal to a corresponding tuning path,wherein the mobile terminal is provided with the tuning circuit having a plurality of tuning paths, and each tuning path corresponds to one usage state of the mobile terminal.(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 11. A storage medium, wherein the storage medium comprises a stored program which cause, when executed by a processor, the processor to perform the signal processing method according to claim 8.(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185984(Integer), 12. A processor, wherein the processor is configured to run a program, the signal processing method according to claim 8 is performed when the program is executed by the processor.(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185984(Integer), TECHNICAL FIELD [0001]The present disclosure relates to the field of communication, and in particular, to a signal processing method and circuit of a mobile terminal, and a mobile terminal. BACKGROUND [0002]With continuous development of communication technology, portable mobile terminals such as mobile phones and notebooks have become essential personal belongings for almost everyone. In a process of designing a mobile terminal, various parameters required for design are obtained usually based on performance designed in a free space mode (that is, the mobile terminal is placed in the free space), and antenna performance of the mobile terminal is designed based on the parameters. Thus, after the design of the mobile terminal is completed, the antenna performance of the mobile terminal is determined. However, in a process of using the mobile terminal, a using environment of the mobile terminal is significantly different from a free space environment, for example, when the mobile terminal is used, external factors such as holding the mobile terminal by a hand of a user and approaching the mobile terminal to a head of the user may cause deterioration of the antenna performance, and finally, user experience is affected. SUMMARY [0003]The following is a summary of a subject matter described in detail herein. This summary is not intended to limit the scope of the claims. [0004]Embodiments of the present disclosure provide a signal processing method and circuit of a mobile terminal and a mobile terminal. [0005]According to an embodiment of the present disclosure, there is provided a signal processing circuit of a mobile terminal including an antenna body, a sensor connected with the antenna body, a microprocessor and a tuning circuit having a plurality of tuning paths. The tuning circuit is connected between a mobile terminal signal source and the antenna body, and the microprocessor is connected with the sensor and the tuning circuit, respectively. The sensor is configured to send a signal detected by operating the antenna body as a sensing pad of the sensor to the microprocessor. The microprocessor is configured to receive the signal, determine a usage state of the mobile terminal according to the signal, generate a control signal according to the usage state of the mobile terminal, and control the tuning circuit to switch the tuning paths through the control signal to perform a tuning process on a signal from the mobile terminal signal source or the antenna body. [0006]In an exemplary embodiment, the signal processing circuit further includes an isolation device which is a lumped inductive element, and the sensor is connected with the antenna body through the isolation device. The isolation device is configured to isolate interference of a communication signal on the signal detected by the sensor. [0007]In an exemplary embodiment, the sensor is a capacitive proximity sensor. [0008]In an exemplary embodiment, the tuning circuit includes a tuning path T1 and a tuning path T2, the tuning path T1 includes inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected with one stationary contact of a first switch element, and one end of the capacitor C3 is connected with a signal feed point of the antenna body. The tuning path T2 includes inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to one stationary contact of the first switch element, and one end of the capacitor C5 is connected with the signal feed point of the antenna body. [0009]In an exemplary embodiment, the signal processing circuit includes a second switch element, the mobile terminal signal source includes a radio frequency circuit and a baseband processing circuit. A grounding point GND1 and a grounding point GND2 of the antenna body are respectively connected with two stationary contacts of the second switch element. Control ends of the first switch element and the second switch element are both connected with one end of the microprocessor, and the other end of the microprocessor is connected with the sensor. A moving contact of the first switch element is connected with one end of the radio frequency circuit, the other end of the radio frequency circuit is connected with the baseband processing circuit, and a moving contact of the second switch element is grounded. [0010]In an exemplary embodiment, the tuning paths have a well-type circuit structure, a T-type circuit structure, or a n-type circuit structure. [0011]According to another embodiment of the present disclosure, a mobile terminal including any of above signal processing circuits is provided. [0012]According to another embodiment of the present disclosure, a signal processing method of a mobile terminal is provided. [0013]The signal processing method includes: detecting a signal by operating an antenna body of the mobile terminal as a sensing pad of a sensor; determining a usage state of the mobile terminal according to the signal; and performing a tuning process on a signal from a mobile terminal signal source or the antenna body according to the usage state of the mobile terminal. [0014]In an exemplary embodiment, determining the usage state of the mobile terminal according to the signal includes: detecting a change condition of a capacitance as a human body approaches through the sensor and the antenna body of the mobile terminal; and determining the usage state of the mobile terminal according to the change condition. [0015]In an exemplary embodiment, performing the tuning process on the signal from the mobile terminal signal source or the antenna body according to the usage state of the mobile terminal includes: performing the tuning process on the signal from the mobile terminal signal source or the antenna body by switching a tuning circuit of the mobile terminal to a corresponding tuning path, in which the mobile terminal is provided with the tuning circuit having a plurality of tuning paths, and each tuning path corresponds to one usage state of the mobile terminal. [0016]According to another embodiment of the present disclosure, a storage medium is further provided, the storage medium includes a stored program, any of above signal processing methods is performed when the program is executed. [0017]According to another embodiment of the present disclosure, a processor is further provided, the processor is configured to run a program, any of above signal processing methods is performed when the program is executed. [0018]According to the present disclosure, by sending the signal detected by operating the antenna body as a sensing pad of the sensor to the microprocessor, the microprocessor determines the usage state of the mobile terminal according to the signal, generates the control signal according to the usage state of the mobile terminal, and controls the tuning circuit to switch tuning paths according to the control signal to perform the tuning process on the signal from the mobile terminal signal source or the antenna body. A problem is solved that a current antenna signal processing circuit occupies more space due to a fact that a sensing pad connected with the sensor needs to be independently arranged in order to ensure that an antenna system is automatically switched to an optimal state to improve quality of antenna signals, an occupied internal space of the mobile terminal is reduced, interference to a communication antenna is avoided and user experience is improved. [0019]Other aspects will be apparent after reading and understanding the accompanying drawings and the detailed description. BRIEF DESCRIPTION OF THE DRAWINGS [0020]FIG. 1 is a block diagram of a hardware structure of a mobile terminal performing a signal processing method according to an embodiment of the present disclosure; [0021]FIG. 2 is a structural block diagram of a signal processing circuit according to an embodiment of the present disclosure; [0022]FIG. 3 is a structural block diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure; [0023]FIG. 4 is a schematic diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure; [0024]FIG. 5 is a flowchart of a signal processing method of a mobile terminal according to an embodiment of the present disclosure; [0025]FIG. 6 is a flowchart of a signal processing method according to an embodiment of the present disclosure; and [0026]FIG. 7 is a structural block diagram of a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0027]At present, a smart watch and an antenna signal processing circuit thereof are disclosed, the antenna signal processing circuit includes a sensor module, a microprocessor, an antenna body and an antenna tuning circuit having a plurality of tuning paths, in which a wearing state of the smart watch is determined by using a proximity sensing signal detected by the sensor module, and then the antenna tuning circuit is switched to a tuning path corresponding to the wearing state, so that an antenna system is suitable for the current wearing state, the antenna system is guaranteed to be automatically switched to an optimal state, and quality of antenna signals is improved. The sensor module is one or more of a distance sensor, a temperature sensor and an acceleration sensor, and requires additional supporting elements and supporting circuits. [0028]There is no solution provided for a problem that the antenna signal processing circuit occupies more space due to a fact that a sensing pad connected with the sensor needs to be independently arranged in order to ensure that the antenna system is automatically switched to an optimal state to improve the quality of the antenna signals. [0029]The present disclosure will be described in detail below with reference to accompanying drawings in conjunction with embodiments. [0030]The terms “first,”“second,” and the like in the description and claims of the present disclosure and in the foregoing accompanying drawings are used to distinguish between similar elements and not necessarily for describing a particular sequence or chronological order. Example 1 [0031]A method embodiment provided in example 1 of the present disclosure may be performed in a mobile terminal, a computer terminal or a similar computing device. Taking the mobile terminal as an example, FIG. 1 is a block diagram of a hardware structure of a mobile terminal performing a signal processing method according to an embodiment of the present disclosure. As shown in FIG. 1, a mobile terminal 10 may include one or two processors 102 (only one processor 102 is shown in FIG. 1) which may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, a memory 104 for storing data, and a transmission device 106 for performing communication functions. It will be understood by those skilled in the art that the structure shown in FIG. 1 is only an illustration and is not intended to limit the structure of the mobile terminal. For example, the mobile terminal 10 may include more or fewer components than those shown in FIG. 1, or have a configuration different from that shown in FIG. 1. [0032]The memory 104 may be used to store software programs and modules of an application, such as program instructions/modules corresponding to a signal processing method according to an embodiment of the present disclosure, and the processor 102 executes various functional applications and data processes by running the software programs and the modules stored in the memory 104, so as to implement the method described above. The memory 104 may include a high speed random memory, and may also include a non-volatile memory, such as one or two magnetic memory devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory located remotely from the processor 102 which may be connected to the mobile terminal 10 via a network. Examples of the network include, but are not limited to, an internet, an intranet, a local area network, a mobile communication network, and a combination thereof. [0033]The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal 10. In one example, the transmission device 106 includes a network interface controller (NIC) which can be connected to other network apparatuses through a base station so as to communicate with the internet. In one example, the transmission device 106 may be a radio frequency (RF) module which is used to communicate with the internet in a wireless manner. [0034]According to an embodiment of the present disclosure, there is provided a signal processing circuit of a mobile terminal which is applied to the mobile terminal described above. FIG. 2 is a structural block diagram of a signal processing circuit according to an embodiment of the present disclosure. As shown in FIG. 2, the signal processing circuit includes an antenna body 201, a sensor 203 connected with the antenna body 201, a microprocessor 205, a tuning circuit 204 having a plurality of tuning paths. [0035]The tuning circuit 204 is connected between a mobile terminal signal source 206 and the antenna body 201, and the microprocessor 205 is connected with the sensor 203 and the tuning circuit 204, respectively. [0036]The sensor 203 is configured to send a signal detected by operating the antenna body 201 as a sensing pad of the sensor 203 to the microprocessor 205. [0037]The microprocessor 205 is configured to receive the signal, determine a usage state of the mobile terminal according to the signal, generate a control signal according to the usage state of the mobile terminal, and control the tuning circuit 204 to switch the tuning paths through the control signal to perform a tuning process on a signal from the mobile terminal signal source 206 or the antenna body 201. [0038]FIG. 3 is a structural block diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure. As shown in FIG. 3, the circuit further includes an isolation device 202 which is a lumped inductive element. The sensor 203 is connected to the antenna body 201 through the isolation device 202, and the isolation device 202 is configured to isolate interference of a communication signal to the signal detected by the sensor 203. [0039]In an exemplary embodiment, the sensor 203 may be a capacitive proximity sensor. [0040]FIG. 4 is a schematic diagram of a signal processing circuit according to an exemplary embodiment of the present disclosure. As shown in FIG. 4, the tuning circuit 204 includes a tuning path T1 and a tuning path T2, the tuning path T1 includes inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected to one stationary contact of a first switch element 208, and one end of the capacitor C3 is connected to a signal feed point of the antenna body 201. [0041]The tuning path T2 includes inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to the other one stationary contact of the first switch element 208, and one end of the capacitor C5 is connected to the signal feed point of the antenna body 201. [0042]In an exemplary embodiment, the circuit may include a second switch element, the mobile terminal signal source 206 includes a radio frequency circuit 209 and a baseband processing circuit 210. [0043]A grounding point GND1 and a grounding point GND2 of the antenna body 201 are respectively connected with two stationary contacts of the second switch element. [0044]Control ends of the first switch element 208 and the second switch element are both connected with one end of the microprocessor 205, and the other end of the microprocessor 205 is connected with the sensor 203. [0045]A moving contact of the first switch element 208 is connected with one end of the radio frequency circuit 209, the other end of the radio frequency circuit 209 is connected with the baseband processing circuit 210, and a moving contact of the second switch element is grounded. [0046]In an exemplary embodiment, the tuning paths may have a well-type circuit structure, a T-type circuit structure, or a IL-type circuit structure. [0047]As shown in FIG. 4, the signal processing circuit includes the antenna body 201, the isolation device 202, the sensor 203, the tuning circuit 204 having a plurality of tuning paths, the microprocessor 205, and the mobile terminal signal source 206. The antenna body 201 is connected with the sensor 203 through the isolation device 202, the tuning circuit 204 is connected between the mobile terminal signal source 206 and the antenna body 201, and the microprocessor 205 is connected with the sensor 203 and the tuning circuit 204, respectively. The sensor 203 detects an approach signal of an external human body through the antenna body 201 and sends the detected signal to the microprocessor 205, the microprocessor 205 receives the signal and generates a control signal according to the signal, and controls the tuning circuit 204 to switch the tuning paths through the control signal to perform the tuning process on the signal from the mobile terminal signal source 206 or the antenna body 201. [0048]The sensor 203 adopts a capacitive proximity sensor 203, when a human body is close to/contacts the antenna body 201, since the human body is equivalent to a grounded capacity, a capacity may be formed between the antenna body 201 and the ground, and induced capacitance usually has several pF to tens pF. A circuit of the sensor 203 outputs a pulse signal to charge and discharge the capacity formed between the antenna body 201 and the ground, and whether or not the human body approaches or touches the antenna body 201 is detected based on a change in the capacitance. [0049]The isolation device 202 adopts a lumped inductive element with an inductance value greater than 100 nH. By isolation of the lumped inductance element, the interference of the communication signal to the detected signal of the sensor 203 is isolated. [0050]In the embodiment, one tuning path of the tuning circuit 204 corresponds to one usage state of the mobile terminal. In an implement, possible usage states of the mobile terminal should be determined firstly (which may be determined statistically through experiments), and then matching impedances of the tuning paths of the tuning circuit 204 are determined, so that one tuning path of the tuning circuit 204 corresponds to one usage state of the mobile terminal. [0051]In the embodiment, by arranging the sensor 203, the usage state of the mobile terminal is determined by using the signal detected by the antenna body 201, and then the tuning circuit 204 is switched to a corresponding tuning path, so that a system of the mobile terminal is suitable for the current usage state. In the embodiment, the antenna body 201 is connected with the sensor 203 through the isolation device 202 to detect the change in the capacitance between the antenna body 201 and the ground caused when human body is close to/contacts the antenna body 201, thereby avoiding independently arranging a sensing pad to be connected with the sensor 203, thus, a space occupied by arranging the sensing pad is reduced. Meanwhile, interference of the sensing pad to communication is avoided and communication quality is improved. As shown in FIG. 4, the signal processing circuit includes the antenna body 201, the isolation device 202, the sensor 203, the tuning circuit 204 having a plurality of tuning paths, the microprocessor 205, the radio frequency circuit 209, the baseband processing circuit 210, and the first switch element 208. The first switch element 208 includes the control end, the moving contact, and the stationary contacts. [0052]Based on the above assumption of the embodiment, accordingly, the tuning circuit 204 includes two tuning paths, i.e., the tuning path T1 and the tuning path T2. Exemplarily, as shown in FIG. 4, the tuning path T1 includes inductors L1 and L2, and capacitors C3 and C4, one end of the inductor L2 is connected to one of the stationary contacts of the first switch element 208, and one end of the capacitor C3 is connected to the signal feed point of the antenna body 201; the tuning path T2 includes inductors L3 and L4, and capacitors C5 and C6, one end of the inductor L4 is connected to the other one of the stationary contacts of the first switch element 208, and one end of the capacitor C5 is connected to the signal feed point of the antenna body 201. [0053]FIG. 4 only exemplarily illustrates the tuning paths with a well-type circuit structure, the circuit structure of the tuning paths is not limited in the embodiment, and the tuning paths may be designed to have a T-type circuit structure, a n-type circuit structure, or the like. The embodiment further includes a second switch element (not shown in FIG. 4) which also includes the control end, the moving contact and the stationary contacts. Correspondingly, the antenna body 201 includes one signal feed point and two grounding points which are the grounding point GND1 and the grounding point GND2, respectively. [0054]In the embodiment, one end of the tuning path T1 and one end of the tuning path T2 are connected to the signal feed point of the antenna body 201, respectively, the other end of the tuning path T1 and the other end of the tuning path T2 are connected to the two stationary contacts of the first switch element 208, respectively, and the grounding point GND1 and the grounding point GND2 of the antenna body 201 are connected to the two stationary contacts of the second switch element, respectively; the control ends of the first switch element 208 and the second switch element are both connected with one end of the microprocessor 205, and the other end of the microprocessor 205 is connected with the sensor 203; the moving contact of the first switch element 208 is connected to one end of the radio frequency circuit 209, the other end of the radio frequency circuit 209 is connected to the baseband processing circuit 210, and the moving contact of the second switch element is grounded. [0055]The microprocessor 205 of the embodiment adjusts system performance of the mobile terminal based on the control signal as follows: the sensor 203 sends a detected change signal of a system capacitance to the microprocessor 205, and the microprocessor 205 determines the current usage state of the mobile terminal according to the signal and generates a corresponding control signal according to the current usage state of the mobile terminal. [0056]As previously assumed, the usage state in the embodiment includes a state of using, a state of free space, a state of holding by a hand of a user, and a state of approaching by the head of a user, so that the microprocessor 205 can generate a high level or a low level to control the switching of the first switch element 208 and the switching of the second switch element by using the high level or the low level. In this case, the first switch element 208 and the second switch element may be single-pole double-throw switches controlled by high and low levels inputted through the control end. [0057]Exemplarily, it is assumed that the microprocessor 205 determines that the mobile terminal is currently in the state of holding by a hand of a user, accordingly, the microprocessor 205 generates the high level to control the control ends of the first switch element 208 and the second switch element, to control the moving contact of the first switch element 208 to contact with the stationary contact connecting with the tuning path T2, and to control the moving contact of the second switch element to contact with the stationary contact connecting with the grounding point GND1, so that to perform the tuning process on the signal from the antenna body 201 or a transmission signal from the baseband processing circuit 210 by using a matching impedance of the tuning path T1 and to adjust and improve radiation performance of the antenna body 201 in the state of holding by a hand of a user by using the grounding point GND2. Example 2 [0058]In an embodiment of the present disclosure, a signal processing method of a mobile terminal is provided. FIG. 5 is a flowchart of a signal processing method of a mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 5, the flowchart includes the following steps S502 to S506. [0059]In step S502, a signal is detected by operating the antenna body 201 of the mobile terminal as a sensing pad of the sensor 203. [0060]In step S504, a usage state of the mobile terminal is determined according to the signal. [0061]In step S506, a tuning process is performed on a signal from the mobile terminal signal source 206 or the antenna body 201 according to the usage state of the mobile terminal. [0062]Through the above steps, the antenna body 201 of the mobile terminal is operated as the sensing pad of the sensor 203 to detect a signal, and the usage state of the mobile terminal is determined according to the signal, and the tuning process is performed on the signal from the mobile terminal signal source 206 or the antenna body 201 according to the usage state of the mobile terminal, so that the problem is solved that a current antenna signal processing circuit occupies more space due to a fact that a sensing pad connected with the sensor 203 needs to be independently arranged in order to ensure that an antenna system is automatically switched to an optimal state to improve quality of antenna signals, an occupied internal space of the mobile terminal is reduced, interference to a communication antenna is avoided and user experience is improved. [0063]In an exemplary embodiment, determining the usage state of the mobile terminal according to the signal may include: a change condition of a capacitance as a human body approaches is detected through the sensor 203 and the antenna body 201 of the mobile terminal, and the usage state of the mobile terminal is determined according to the change condition. [0064]In an exemplary embodiment, performing the tuning process on the signal from the mobile terminal signal source 206 or the antenna body 201 according to the usage state of the mobile terminal may include: the tuning process is performed on the signal from the mobile terminal signal source 206 or the antenna body 201 by switching the tuning circuit 204 of the mobile terminal to a corresponding tuning path, the mobile terminal is provided with the tuning circuit 204 having a plurality of tuning paths, and each tuning path corresponds to one usage state of the mobile terminal. The mobile terminal is internally provided with the antenna body 201, the sensor 203 connected with the antenna body 201, the microprocessor 205 and the tuning circuit 204 having a plurality of tuning paths, and the method includes the following steps: the sensor 203 detects a signal by operating the antenna body 201 as the sensing pad and determines the usage state of the mobile terminal according to the signal; arranging the tuning circuit 204 having a plurality of tuning paths such that one tuning path corresponds to one usage state of the mobile terminal; and switching the tuning circuit 204 to a corresponding tuning path according to the usage state of the mobile terminal, and performing the tuning process on the signal from the mobile terminal signal source or the antenna body. In the method, since a communication antenna on a module is reused as the sensing pad of the sensor 203, so that the problem of more occupied space caused by independently arranging the sensing pad connected with the sensor 203 is avoided, and interference of the sensing pad on communication is also avoided. [0065]FIG. 6 is a flowchart of a signal processing method according to an embodiment of the present disclosure. As shown in FIG. 6, the method including steps S602 to S606. [0066]In step S602, the tuning circuit 204 having a plurality of tuning paths is arranged to enable one tuning path to correspond to one usage state of the mobile terminal. [0067]In step S604, a change of a capacitance as a human body approaches is detected by using the sensor 203 and the antenna body 201, and the usage state of the mobile terminal is determined according to the change. [0068]In step S606, the microprocessor 205 switches the tuning circuit 204 and the grounding point of the antenna to a corresponding path according to the usage state of the mobile terminal, and performs a tuning processing on a signal from the mobile terminal signal source 206 or the antenna body 201. [0069]In the embodiment, the change of the capacitance as a human body approaches is detected by using the sensor 203 and the antenna body 201, the usage state of the mobile terminal is determined according to the change, and then the tuning circuit 204 is switched to the tuning path corresponding to the usage state, so that the system of the mobile terminal is suitable for the current usage state, the system of the mobile terminal can be automatically switched to an optimal state, quality of signals is ensured, and user experience is improved. [0070]In order to further improve performance of the mobile terminal in different usage states, the method in FIG. 6 further includes: arranging one signal feed point and a plurality of grounding points for the antenna body 201, and when or after performing the tuning process on the signal from the mobile terminal signal source or the antenna body 201, the method further includes: the grounding points of the antenna body 201 are switched to adjust performance of the antenna body 201. [0071]In one implementation of the embodiment, the grounding points of the antenna body may be switched by arranging a switch element for the antenna body, the switch element includes a control end, a moving contact and a plurality of stationary contacts, the moving contact is grounded, one stationary contact is connected with one grounding point, each stationary contact corresponds to one usage state of the mobile terminal, and the moving contact of the switch element is switched by controlling the control end. Example 3 [0072]According to another embodiment of the present disclosure, there is also provided a mobile terminal including the antenna body 201, the sensor 203 connecting with the antenna body 201, the microprocessor 205, and the tuning circuit 204 having a plurality of tuning paths. The interference of the communication signal to the signal of the sensor 203 is isolated through the isolation device 202 between the antenna body 201 and the sensor 203. The microprocessor 205 detects the usage state of the mobile terminal and adjusts system parameters of the mobile terminal. [0073]FIG. 7 is a structural block diagram of a mobile terminal according to an embodiment of the present disclosure. As shown in FIG. 7, the mobile terminal of the embodiment includes an antenna signal processing circuit, an internal structure of the antenna signal processing circuit is as shown in FIG. 3, the antenna body 201 in the antenna signal processing circuit is connected to the sensor 203 through the isolation device 202, and when a human body approaches the antenna body 201, a change of a capacitance between the antenna body 201 and the ground may be detected, and the microprocessor 205 in the antenna signal processing circuit senses whether a human body approaches, so as to adjust the system parameters of the mobile terminal. [0074]In a design process of the embodiment, in order to save space of the mobile terminal and save components, the microprocessor 205 in the embodiment is a central controller CPU of the mobile terminal, that is, the actions such as determining, calculating, controlling or the like performed by the microprocessor 205 in the antenna signal processing circuit are performed by the central controller CPU of the mobile terminal. [0075]Since the baseband processing circuit in the antenna signal processing circuit is also substantially one microcontroller, the baseband processing circuit in the antenna signal processing circuit may be a central processing unit CPU of the mobile terminal either. Example 4 [0076]Embodiments of the present disclosure also provide a storage medium including stored programs, any one of the methods describe(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端的信号处理方法、电路及移动终端。 背景 [0002] 随着通信技术的不断发展,手机、笔记本等便携式移动终端已经成为几乎每个人必不可少的个人随身物品。 在移动终端的设计过程中,通常根据自由空间模式(即移动终端放置在自由空间中)设计的性能,获取设计所需的各种参数,设计移动终端的天线性能 基于参数。 这样,移动终端的设计完成后,移动终端的天线性能就确定了。 然而,在使用移动终端的过程中,移动终端的使用环境与自由空间环境有很大的不同,例如,在使用移动终端时,人的手拿着移动终端等外部因素。 用户将移动终端靠近用户头部可能会导致天线性能下降,最终影响用户体验。 概括 [0003] 以下是本文详细描述的主题的概要。 该概述不旨在限制权利要求的范围。 [0004] 本发明实施例提供一种移动终端的信号处理方法、电路及移动终端。 [0005] 根据本公开的实施例,提供了一种移动终端的信号处理电路,包括天线本体、与天线本体连接的传感器、微处理器和具有多个调谐路径的调谐电路。 调谐电路连接在移动终端信号源和天线本体之间,微处理器分别连接传感器和调谐电路。 传感器被配置为将通过将天线体作为传感器的感测垫操作而检测到的信号发送到微处理器。 微处理器用于接收信号,根据信号判断移动终端的使用状态,根据移动终端的使用状态产生控制信号,通过控制信号控制调谐电路切换调谐路径 对来自移动终端信号源或天线体的信号进行调谐处理。 [0006] 在一个示例性实施例中,信号处理电路还包括隔离装置,隔离装置为集总电感元件,传感器通过隔离装置与天线本体连接。 隔离装置用于隔离通信信号对传感器检测信号的干扰。 [0007] 在示例性实施例中,传感器是电容式接近传感器。 [0008] 在示例性实施例中,调谐电路包括调谐路径T 1 和调整路径 T 2 , 调整路径 T 1 包括电感器 L 1 和我 2 和电容器 C 3 和C 4 , 电感 L 的一端 2 与第一开关元件的一个固定触点连接,电容器C的一端 3 与天线本体的信号馈入点连接。 调整路径 T 2 包括电感器 L 3 和我 4 和电容器 C 5 和C 6 , 电感 L 的一端 4 连接到第一开关元件的一个固定触点,和电容器C的一端 5 与天线本体的信号馈入点相连。 [0009] 在一个示例性实施例中,信号处理电路包括第二开关元件,移动终端信号源包括射频电路和基带处理电路。 接地点GND 1 和接地点GND 2天线本体的两个固定触点分别与第二开关元件的两个固定触点连接。 第一开关元件和第二开关元件的控制端均连接微处理器的一端,微处理器的另一端连接传感器。 第一开关元件的动触点连接射频电路的一端,射频电路的另一端连接基带处理电路,第二开关元件的动触点接地。 [0010] 在示例性实施例中,调谐路径具有阱型电路结构、T型电路结构或n型电路结构。 [0011] 根据本公开的另一个实施例,提供了一种包括上述任一种信号处理电路的移动终端。 [0012] 根据本公开的另一个实施例,提供了一种移动终端的信号处理方法。 [0013] 该信号处理方法包括:通过将移动终端的天线体作为传感器的感应垫操作来检测信号; 根据信号判断移动终端的使用状态; 根据移动终端的使用状态,对来自移动终端信号源或天线本体的信号进行调谐处理。 [0014] 在一个示例性实施例中,根据所述信号确定移动终端的使用状态包括: 通过传感器和移动终端的天线体检测人体接近时电容的变化情况; 根据变化情况判断移动终端的使用状态。 [0015] 在一个优选实施例中,根据移动终端的使用状态对来自移动终端信号源或天线本体的信号进行调谐处理包括:对来自移动终端信号源或天线本体的信号进行调谐处理。 通过将移动终端的调谐电路切换到对应的调谐路径,移动终端设置有具有多条调谐路径的调谐电路,每条调谐路径对应移动终端的一种使用状态。 [0016] 根据本发明的另一个实施例,还提供了一种存储介质,该存储介质包括存储的程序,在执行该程序时执行上述任一种信号处理方法。 [0017] 根据本发明的另一个实施例,还提供了一种处理器,该处理器用于运行程序,在程序运行时执行上述任一种信号处理方法。 [0018] 本发明通过将天线体作为传感器的感应垫工作时检测到的信号发送给微处理器,微处理器根据该信号判断移动终端的使用状态,并根据使用情况产生控制信号。 移动终端的状态,根据控制信号控制调谐电路切换调谐路径,对来自移动终端信号源或天线本体的信号进行调谐处理。 解决了现有的天线信号处理电路由于需要单独设置与传感器连接的感应垫而占用较多空间的问题,以保证天线系统自动切换到最佳状态,提高信号质量。 天线信号,减少了移动终端内部空间的占用,避免了对通信天线的干扰,提高了用户体验。 [0019] 在阅读和理解附图和详细描述之后,其他方面将是显而易见的。 附图的简要说明 [0020] 图1是执行根据本发明实施例的信号处理方法的移动终端的硬件结构框图; [0021] 图2是根据本发明实施例的信号处理电路的结构框图; [0022]图3是根据本发明一个示例性实施例的信号处理电路的结构框图。 [0023] 图4是根据本公开示例性实施例的信号处理电路的示意图; [0024] 图5是本发明一个实施例的移动终端的信号处理方法的流程图。 [0025] 图6是根据本发明实施例的信号处理方法的流程图; 和 [0026] 图7是根据本发明实施例的移动终端的结构框图。 详细说明 [0027] 目前,公开了一种智能手表及其天线信号处理电路,该天线信号处理电路包括传感器模块、微处理器、天线本体和具有多个调谐路径的天线调谐电路,其中佩戴状态 智能手表利用传感器模块检测到的接近感应信号进行判断,然后将天线调谐电路切换到与佩戴状态对应的调谐路径,使天线系统适合当前佩戴状态,天线 保证系统自动切换到最佳状态,提高天线信号质量。 传感器模块为距离传感器、温度传感器和加速度传感器中的一种或多种,​​需要额外的支持元件和支持电路。 [0028] 为保证天线系统自动切换到最佳状态,需要单独设置与传感器连接的感应垫,导致天线信号处理电路占用较多空间,目前未提供解决方案。 提高天线信号的质量。 [0029] 下面结合附图并结合实施例对本发明进行详细说明。 [0030] 本公开的说明书和权利要求以及前述附图中的术语“第一”、“第二”等用于区分相似的元素,并不一定用于描述特定的顺序或时间顺序。 示例 1 [0031] 本发明实施例一提供的方法实施例可以在移动终端、计算机终端或类似的计算设备中执行。 以移动终端为例,图1是执行根据本发明实施例的信号处理方法的移动终端的硬件结构框图。 如图1所示,一个移动终端 10 可能包括一个或两个处理器 102 (只有一个处理器 102 如图1所示)可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等处理设备、存储器 104 用于存储数据,以及传输设备 106 用于执行通信功能。 本领域的技术人员可以理解,图1所示的结构只是一种示例,并不对移动终端的结构构成限制。 比如移动端 10 可以包括比图 1 中所示的组件更多或更少的组件,或者具有与图 1 中所示的不同的配置。 [0032] 记忆 104 可以用于存储应用程序的软件程序和模块,例如与根据本公开实施例的信号处理方法对应的程序指令/模块,以及处理器 102 通过运行存储在内存中的软件程序和模块来执行各种功能应用和数据处理 104 ,从而实现上述方法。 记忆 104 可以包括高速随机存储器,也可以包括非易失性存储器,例如一个或两个磁存储设备、闪存或其他非易失性固态存储器。 在某些情况下,内存 104 还可以包括远离处理器的存储器 102 可连接移动终端 10通过网络。 网络的示例包括但不限于因特网、内联网、局域网、移动通信网络及其组合。 [0033] 传动装置 106 用于通过网络接收或传输数据。 上述网络的具体示例可以包括移动终端的通信提供商提供的无线网络 10 . 在一个例子中,传输设备 106 包括网络接口控制器(NIC),其可以通过基站连接到其他网络设备以与互联网通信。 在一个例子中,传输设备 106 可以是用于以无线方式与因特网通信的射频(RF)模块。 [0034] 根据本发明实施例,提供了一种移动终端信号处理电路,应用于上述移动终端。 图2是根据本发明实施例的信号处理电路的结构框图。 如图2所示,信号处理电路包括天线本体 201 , 一个传感器 203 与天线体相连 201 , 一个微处理器 205 , 调谐电路 204 具有多个调谐路径。 [0035] 调谐电路 204 连接在移动终端信号源之间 206 和天线体 201 , 和微处理器 205 与传感器相连 203 和调谐电路 204 , 分别。 [0036] 传感器 203 被配置为发送通过操作天线体检测到的信号 201 作为传感器的感应垫 203 到微处理器 205 . [0037] 微处理器 205 用于接收信号,根据信号判断移动终端的使用状态,根据移动终端的使用状态产生控制信号,控制调谐电路 204 通过控制信号切换调谐路径,对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 . [0038] 图3是根据本公开示例性实施例的信号处理电路的结构框图。 如图3所示,该电路还包括隔离器件 202 这是一个集总电感元件。 传感器 203 连接到天线体 201 通过隔离装置 202 和隔离装置 202 被配置为隔离通信信号对传感器检测到的信号的干扰 203 . [0039] 在示例性实施例中,传感器 203 可能是电容式接近传感器。 [0040] 图4是根据本公开示例性实施例的信号处理电路的示意图。 如图4所示,调谐电路 204 包括调谐路径 T 1 和调整路径 T 2 , 调整路径 T 1 包括电感器 L 1 和我 2 和电容器 C 3 和C 4 , 电感 L 的一端 2 连接到第一开关元件的一个固定触点 208 ,电容C的一端 3 连接到天线本体的信号馈入点 201 . [0041] 调整路径 T 2 包括电感器 L 3 和我 4 和电容器 C 5 和C 6 , 电感 L 的一端 4 连接到第一开关元件的另一个固定触点 208 ,电容C的一端 5 连接到天线本体的信号馈入点 201 . [0042] 在一个示例性实施例中,该电路可以包括第二开关元件,移动终端信号源 206 包括射频电路 209 和基带处理电路 210 . [0043] 接地点GND 1 和接地点GND 2 天线本体 201分别与第二开关元件的两个固定触点相连。 [0044] 第一开关元件的控制端 208 第二开关元件均与微处理器的一端连接 205 ,微处理器的另一端 205 与传感器相连 203 . [0045] 第一开关元件的动触点 208 与射频电路的一端相连 209 ,射频电路的另一端 209 与基带处理电路相连 210 ,第二开关元件的动触点接地。 [0046] 在示例性实施例中,调谐路径可以具有阱型电路结构、T型电路结构或IL型电路结构。 [0047] 如图4所示,信号处理电路包括天线本体 201 , 隔离装置 202 , 传感器 203 , 调谐电路 204 具有多个调谐路径,微处理器 205 , 和移动端信号源 206 . 天线本体 201 与传感器相连 203 通过隔离装置 202 , 调谐电路 204 连接在移动终端信号源之间 206 和天线体 201 , 和微处理器 205 与传感器相连 203 和调谐电路 204 , 分别。 传感器 203 通过天线体检测外界人体接近信号 201 并将检测到的信号发送给微处理器 205 , 微处理器 205 接收信号并根据信号产生控制信号,控制调谐电路 204 通过控制信号切换调谐路径,对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 . [0048] 传感器 203 采用电容式接近传感器 203 ,当人体靠近/接触天线体时 201 ,由于人体相当于一个接地电容,天线本体之间可能形成电容 201 与地、感应电容一般有几pF到几十pF。 传感器电路 203 输出脉冲信号对天线体间形成的电容进行充放电 201 和地面,以及人体是否接近或接触天线体 201 基于电容的变化来检测。 [0049] 隔离装置 202 采用电感值大于100nH的集总电感元件。 通过集总电感元件的隔离,通信信号对传感器检测信号的干扰 203 是孤立的。 [0050] 在本实施例中,调谐电路的一个调谐路径 204 对应移动终端的一种使用状态。 在实现中,首先要确定移动终端可能的使用状态(可以通过实验统计确定),然后匹配调谐电路的调谐路径的阻抗。 204 被确定,使得调谐电路的一个调谐路径 204 对应移动终端的一种使用状态。 [0051] 在本实施例中,通过设置传感器 203 ,利用天线体检测到的信号判断移动终端的使用状态 201 ,然后是调谐电路 204 切换到相应的调谐路径,使得移动终端的系统适合当前的使用状态。 本实施例中,天线本体 201 与传感器相连 203 通过隔离装置 202 检测天线体之间的电容变化 201 以及人体靠近/接触天线体时产生的接地 201 ,从而避免单独设置感应垫与传感器连接 203,从而减少了设置感应垫所占用的空间。 同时,避免了感应垫对通信的干扰,提高了通信质量。 如图4所示,信号处理电路包括天线本体 201 , 隔离装置 202 , 传感器 203 , 调谐电路 204 具有多个调谐路径,微处理器 205 , 射频电路 209 ,基带处理电路 210 , 和第一个开关元件 208 . 第一个开关元件 208 包括控制端、动触点和静触点。 [0052] 基于本实施例的上述假设,相应地,调谐电路 204 包括两条调谐路径,即调谐路径 T 1 和调整路径 T 2 . 示例性地,如图4所示,调谐路径T 1 包括电感器 L 1 和我 2 和电容器 C 3 和C 4 , 电感 L 的一端 2 连接到第一开关元件的固定触点之一 208 ,电容C的一端 3 连接到天线本体的信号馈入点 201 ; 调整路径 T 2 包括电感器 L 3 和我 4 和电容器 C 5 和C 6 , 电感 L 的一端 4 连接到第一开关元件的另一个固定触点 208 ,电容C的一端 5 连接到天线本体的信号馈入点 201 . [0053] 图4只是示例性地示出了具有阱型电路结构的调谐路径,本实施例不对调谐路径的电路结构进行限定,调谐路径可以设计为T型电路结构、n型电路结构。 电路结构等。 该实施例还包括第二开关元件(图4中未示出),第二开关元件也包括控制端、动触点和静触点。 相应地,天线体 201 包括一个信号馈入点和两个接地点,接地点为GND 1 和接地点GND 2 , 分别。 [0054] 在本实施例中,调谐路径T的一端 1 和调谐路径 T 的一端 2 连接到天线本体的信号馈入点 201 , 分别为调谐路径 T 的另一端 1 和调谐路径T的另一端 2 连接到第一个开关元件的两个固定触点 208 ,分别与接地点GND 1 和接地点GND 2 天线本体 201 分别连接至第二开关元件的两个固定触点; 第一开关元件的控制端 208 第二开关元件均与微处理器的一端连接 205 ,微处理器的另一端 205 与传感器相连 203 ; 第一开关元件的动触点 208 连接到射频电路的一端 209 ,射频电路的另一端 209 接基带处理电路 210 ,第二开关元件的动触点接地。 [0055] 微处理器 205 本实施例基于控制信号调整移动终端的系统性能如下:传感器 203 向微处理器发送检测到的系统电容变化信号 205 , 和微处理器 205 根据该信号确定移动终端的当前使用状态,并根据移动终端的当前使用状态生成相应的控制信号。 [0056] 如前所述,本实施例中的使用状态包括使用状态、空闲空间状态、用户手持状态、用户头部接近状态,使得微处理器 205 可以产生高电平或低电平来控制第一开关元件的开关 208第二开关元件以高电平或低电平切换。 在这种情况下,第一个开关元件 208 第二开关元件可以为由控制端输入的高低电平控制的单刀双掷开关。 [0057] 示例性地,假设微处理器 205 确定移动终端当前处于用户手持状态,相应地,微处理器 205 产生高电平控制第一开关元件的控制端 208 以及第二开关元件,以控制第一开关元件的动触点 208 接触与调谐路径T连接的固定触点 2 ,并控制第二开关元件的动触点与接地点GND相连的静触点接触 1 , 从而对来自天线体的信号进行调谐处理 201 或来自基带处理电路的传输信号 210 通过使用调谐路径 T 的匹配阻抗 1 调整和改善天线体的辐射性能 201 使用接地点GND在用户手持状态下 2 . 示例 2 [0058] 在本发明实施例中,提供了一种移动终端的信号处理方法。 图5是根据本公开实施例的移动终端的信号处理方法的流程图。 如图5所示,该流程图包括以下步骤S 502 到小号 506 . [0059] 在步骤S 502 ,通过操作天线体来检测信号 201 移动终端作为传感器的感应板 203 . [0060] 在步骤S 504 ,根据该信号确定移动终端的使用状态。 [0061] 在步骤S 506 , 对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 根据移动终端的使用状态。 [0062] 通过以上步骤,天线体 201 移动终端的作为传感器的感应垫操作 203 检测信号,根据信号判断移动终端的使用状态,并对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 根据移动终端的使用状态,解决了现有的天线信号处理电路由于与传感器连接的感应垫占用较多空间的问题 203 需要独立设置,以保证天线系统自动切换到最佳状态,提高天线信号质量,减少移动终端内部占用空间,避免对通信天线的干扰,提高用户体验 . [0063] 在一个示例性实施例中,根据所述信号确定移动终端的使用状态可以包括:通过传感器检测电容随着人体接近的变化情况。 203 和天线体 201 移动终端的使用状态,根据变化情况确定移动终端的使用状态。 [0064] 在一个示例性实施例中,对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 根据移动终端的使用状态可以包括:对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 通过切换调谐电路 204 移动终端到相应的调谐路径,移动终端设置有调谐电路 204 具有多个调谐路径,每个调谐路径对应移动终端的一种使用状态。 移动终端内置有天线体 201 , 传感器 203 与天线体相连 201 , 微处理器 205 和调谐电路 204具有多个调谐路径,并且该方法包括以下步骤:传感器 203 通过操作天线体来检测信号 201 作为感应垫,根据信号判断移动终端的使用状态; 布置调谐电路 204 具有多个调谐路径,一个调谐路径对应移动终端的一种使用状态; 并切换调谐电路 204 根据移动终端的使用状态到相应的调谐路径,对来自移动终端信号源或天线本体的信号进行调谐处理。 在该方法中,由于模块上的通信天线被重新用作传感器的感应垫 203 , 从而解决单独设置与传感器相连的感应垫占用空间较多的问题 203 避免了感应垫对通信的干扰。 [0065] 图6是根据本公开实施例的信号处理方法的流程图。 如图6所示,该方法包括步骤S 602 到小号 606 . [0066] 在步骤S 602 , 调谐电路 204 具有多条调谐路径,用于使一条调谐路径对应移动终端的一种使用状态。 [0067] 在步骤S 604 ,当人体接近时电容的变化是通过使用传感器检测到的 203 和天线体 201 ,根据变化判断移动终端的使用状态。 [0068] 在步骤S 606 , 微处理器 205 切换调谐电路 204 以及天线的接地点根据移动终端的使用状态到相应的路径,并对来自移动终端信号源的信号进行调谐处理 206 或天线体 201 . [0069] 在本实施例中,利用传感器检测电容随着人体靠近的变化 203 和天线体 201 ,根据变化判断移动终端的使用状态,然后调谐电路 204 切换到与使用状态对应的调谐路径,使得移动终端的系统适合当前的使用状态,能够自动将移动终端的系统切换到最佳状态,保证信号质量, 用户体验得到改善。 [0070] 为了进一步提高移动终端在不同使用状态下的性能,图6的方法还包括:天线体设置一个信号馈入点和多个接地点。 201 ,以及在对来自移动终端信号源或天线体的信号进行调谐处理时或之后 201 ,该方法还包括:天线本体的接地点 201 被切换以调整天线体的性能 201 . [0071] 在本实施例的一种实施方式中,可以通过为天线本体设置开关元件来切换天线本体的接地点,开关元件包括控制端、动触点和多个静触点,动触点接地。 一个静触点连接一个接地点,每个静触点对应移动终端的一种使用状态,通过控制端控制开关元件的动触点进行切换。 示例 3 [0072] 根据本发明的另一个实施例,还提供了一种移动终端,包括所述天线本体 201 , 传感器 203 与天线本体连接 201 , 微处理器 205 和调谐电路 204 具有多个调谐路径。 通信信号对传感器信号的干扰 203 通过隔离装置隔离 202 天线体之间 201 和传感器 203 . 微处理器 205 检测移动终端的使用状态,调整移动终端的系统参数。 [0073]图7是根据本发明实施例的移动终端的结构框图。 如图7所示,本实施例的移动终端包括天线信号处理电路,天线信号处理电路的内部结构如图3所示,天线本体 201 在天线信号处理电路中连接到传感器 203 通过隔离装置 202 ,当人体接近天线体时 201 ,天线体之间电容的变化 201 并且可以检测到地面,并且微处理器 205 天线信号处理电路中感应是否有人体靠近,从而调整移动终端的系统参数。 [0074] 在本实施例的设计过程中,为了节省移动终端的空间和元器件,微处理器 205 本实施例中为移动终端的中控CPU,即微处理器进行的判断、计算、控制等动作 205 天线信号处理电路中的处理由移动终端的中央控制器CPU完成。 [0075] 由于天线信号处理电路中的基带处理电路实质上也是一个微控制器,因此天线信号处理电路中的基带处理电路也可以是移动终端的中央处理器CPU。 例 4 [0076] 本发明实施例还提供了一种存储介质,包括存储的程序,在执行程序时执行上述任一方法。 [0077] 可选地,在本实施例中,存储介质可以用于存储用于执行以下步骤S的程序代码 11 到小号 13 . [0078] 在步骤S 11 ,通过将移动终端的天线体作为传感器的感测垫操作来检测信号。 [0079] 在步骤S 12 ,根据该信号确定移动终端的使用状态。 [0080] 在步骤S 13 ,根据移动终端的使用状态,对来自移动终端信号源或天线体的信号进行调谐处理。 [0081] 可选地,在本实施例中,存储介质可以包括但不限于U盘、只读存储器(ROM)、随机存取存储器(RAM)、可移动存储器等各种能够存储程序代码的介质。 硬盘、磁盘或光盘。 例 5 [0082] 本发明实施例还提供一种处理器,用于运行程序,该处理器在执行程序时执行上述任一种方法中的步骤。 [0083] 可选地,在本实施例中,程序用于执行以下步骤S 21 到小号 23 . [0084] 在步骤S 21 ,通过将移动终端的天线体作为传感器的感测垫操作来检测信号。 [0085] 在步骤S 22 ,根据该信号确定移动终端的使用状态。 [0086] 在步骤S 23 ,根据移动终端的使用状态,对来自移动终端信号源或天线体的信号进行调谐处理。 [0087] 可选的,本实施例中的具体示例可以参见上述实施例及可选实施方式中描述的示例,在此不再赘述。 [0088]本领域普通技术人员可以理解,上述公开的方法、装置中的功能模块/单元、系统的全部或部分步骤可以通过软件、固件、硬件或其适当组合来实现。 在硬件实现中,上述描述中的功能模块/单元的划分并不一定对应于物理部件的划分; 例如,一个物理组件可以具有多种功能,或者一个功能或一个步骤可以由多个物理组件共同完成。 一些或所有组件可以实现为由诸如数字信号处理器或微处理器的处理器执行的软件,或者实现为硬件,或者实现为诸如专用集成电路的集成电路。 这样的软件可以分布在可以包括计算机存储介质(或非暂时性介质)的计算机可读介质上。 术语“计算机存储介质”包括以任何方法或技术实现的易失性和非易失性介质、可移动和不可移动介质,用于存储诸如计算机可读指令、数据结构、程序模块或其他数据等信息,正如那些众所周知的 本领域的普通技术人员。 计算机存储介质包括但不限于 RAM、ROM、EEPROM、闪存或其他存储技术、CD-ROM、数字通用磁盘 (DVD) 或其他光盘存储、磁带、磁带、磁盘存储 或其他磁存储设备,或任何其他可用于存储所需信息并可由计算机访问的介质。 [0089] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明,对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。 工业实用性 [0090] 根据本公开,通过将天线体作为传感器的感应垫操作检测到的信号发送给微处理器,微处理器根据该信号确定移动终端的使用状态,并根据使用情况产生控制信号。 移动终端状态,根据控制信号控制调谐电路切换调谐路径,对来自移动终端信号源或天线本体的信号进行调谐处理,解决了现有天线信号处理电路存在的问题 由于与传感器连接的感应垫占用更多空间 203 需要独立设置,以保证天线系统自动切换到最佳状态,提高天线信号质量,减少移动终端内部占用空间,避免对通信天线的干扰,提高用户体验 .(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN109474290A(String), US20210075461A1(String), WO2019047562A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN109474290A(String), US20210075461A1(String), WO2019047562A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.961 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN109474290A(String), US20210075461A1(String), WO2019047562A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:21.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271385(Integer), CN109474290A(String), 1048725(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271385(Integer), US20210075461A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271385(Integer), WO2019047562A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN109474290A(String), CN109474290A(String), 1552579200(Integer), 271385(Integer), 185669(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185984(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185984(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185984(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185984(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 放弃(String), 2(Integer), 185984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:22.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Controlling the radiation pattern of a mobile terminal according to a posture of the mobile terminal(String), 根据移动终端的姿态控制移动终端的辐射方向图(String), US9144032B2(String), A transmission method and apparatus of a mobile terminal including an antenna are provided. The transmission method includes determining a posture of the mobile terminal in an active state, updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, and transmitting a transmit signal amplified according to the updated reference power. Accordingly, the reference power is adjusted according to the posture of the mobile terminal, whereby it is possible to control the radiation pattern of antenna of the mobile terminal.(String), 提供了一种包括天线的移动终端的传输方法和装置。 传输方法包括确定移动终端处于激活状态的姿势,通过添加根据移动终端的姿势确定的功率增益来更新预设的参考功率,以及发送根据更新的参考功率放大的发射信号。 因此,根据移动终端的姿势调整参考功率,从而可以控制移动终端的天线的辐射方向图。(String), US13/397031(String), 1329235200(Integer), US9144032B2(String), 1442851200(Integer), 1442851200(Integer), 美国(String), 4(Integer), KR(String), 2(Integer), 13(Integer), US20040176125A1 | US20070216584A1 | US20070259689A1 | US20080317175A1 | US20090253459A1 | US20090305742A1 | US20100279751A1 | US20110021139A1 | US20110237306A1 | US6512917B1 | US7212164B2 | US7330705B2 | US8436784B2(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185985(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ec58afc01c754de5a80f0b6766e4963b.png(String), 185985(Integer), ec58afc01c754de5a80f0b6766e4963b.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.240 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.240 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.260 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.261 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Controlling the radiation pattern of a mobile terminal according to a posture of the mobile terminal(String), 根据移动终端的姿态控制移动终端的辐射方向图(String), US9144032B2(String), A transmission method and apparatus of a mobile terminal including an antenna are provided. The transmission method includes determining a posture of the mobile terminal in an active state, updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, and transmitting a transmit signal amplified according to the updated reference power. Accordingly, the reference power is adjusted according to the posture of the mobile terminal, whereby it is possible to control the radiation pattern of antenna of the mobile terminal.(String), 提供了一种包括天线的移动终端的传输方法和装置。 传输方法包括确定移动终端处于激活状态的姿势,通过添加根据移动终端的姿势确定的功率增益来更新预设的参考功率,以及发送根据更新的参考功率放大的发射信号。 因此,根据移动终端的姿势调整参考功率,从而可以控制移动终端的天线的辐射方向图。(String), US13/397031(String), 1329235200(Integer), US9144032B2(String), 1442851200(Integer), 1442851200(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 2(Integer), 13(Integer), US20040176125A1 | US20070216584A1 | US20070259689A1 | US20080317175A1 | US20090253459A1 | US20090305742A1 | US20100279751A1 | US20110021139A1 | US20110237306A1 | US6512917B1 | US7212164B2 | US7330705B2 | US8436784B2(String), \20230420\ec58afc01c754de5a80f0b6766e4963b.png(String), 11(Integer), 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.296 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 1. A transmission method of a mobile terminal including an antenna, the method comprising:determining a posture of the mobile terminal in an active state;updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, the posture determined according to one of an angle or a position of the mobile terminal in relation to the ground; andtransmitting a transmit signal amplified according to the updated preset reference power in a radiation pattern according to the posture of the mobile terminal,wherein the mobile terminal stores a mapping of a plurality of power gains corresponding to a plurality of different postures, andwherein the radiation pattern is at least one of symmetric and asymmetric.(String), 1.如权利要求10所述的传输装置,其中根据预设参考功率与发射功率的差值确定新的功率增益。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 2. The transmission method of claim 1, wherein the determining of the posture comprises configuring the preset reference power based on analysis of a received signal.(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 3. The transmission method of claim 2, wherein the preset reference power is determined according to strength of the received signal.(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 4. The transmission method of claim 1, wherein the transmitting of the transmit signal comprises updating, when the transmit power is less than the preset reference power, the reference power by adding a new power gain.(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 5. The transmission method of claim 4, wherein the new power gain is determined according to a difference value between the preset reference power and the transmit power.(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 6. A transmission apparatus of the mobile terminal, the apparatus comprising:a posture detection unit configured to detect a posture of the mobile terminal in an active state, the posture determined according to one of an angle or a position of the mobile terminal in relation to the ground;a memory unit configured to store a mapping of a plurality of power gains to a plurality of different postures;a control unit configured to control the posture detection unit to update a preset reference power by adding a power gain determined according to the posture of the mobile terminal;a Radio Frequency (RF) unit configured to amplify a transmit signal according to the updated preset reference power under the control of the control unit; andan antenna configured to radiate the transmit signal in a radiation pattern according to the posture of the mobile terminal,wherein the radiation pattern is at least one of symmetric and asymmetric.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 7. The transmission apparatus of claim 6, wherein the control unit configures the preset reference power based on analysis of a received signal.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 8. The transmission apparatus of claim 7, wherein the preset reference power is determined according to strength of the received signal.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 9. The transmission apparatus of claim 6, wherein the RF unit comprises:a power amplifier configured to amplify a transmit power of the transmit signal according to the preset reference power; anda power detector configured to determine whether the transmit power is less than the preset reference power.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 10. The transmission apparatus of claim 9, wherein the control unit updates, when the transmit power is less than the preset reference power, the reference power by adding a new power gain.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185985(Integer), 11. The transmission apparatus of claim 10, wherein the new power gain is determined according to a difference value between the preset reference power and the transmit power.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185985(Integer), PRIORITY [0001]This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Feb. 16, 2011 in the Korean Intellectual Property Office and assigned Serial No. 10-2011-0013563, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal. More particularly, the present invention relates to a transmission method and apparatus of a mobile terminal having an antenna in a wireless communication system. [0004]2. Description of the Related Art [0005]Recently, wireless communication systems have been designed to support various multimedia services based on an integrated supplementary functionality such as a Global Positioning System (GPS), Bluetooth, and the Internet. In order to facilitate providing various multimedia services, a high data rate must be secured for transmitting high volume multimedia data. An antenna is one factor that determines transmission performance. Thus research has been conducted to acquire high quality antenna features because the antenna of a mobile terminal is substantially responsible for transmitting signals carrying multimedia services. In a mobile communication terminal, it is preferred to implement the antenna to have an optimal radiation pattern. The optimal radiation pattern can be acquired through several times of tuning processes in a manufacturing state. [0006]Meanwhile, mobile communication terminals are manufactured with a slim and compact design to secure portability. Conventional antennas such as a rod antenna and a helical antenna are exposed partially out of a terminal casing, which compromises portability and causes physical damage of the antenna. In order to address these problems, recent mobile terminals have been equipped with an internal antenna, which is also referred to as an intenna. [0007]However, the conventional mobile terminals are designed to transmit signals in a fixed radiation pattern determined as being optimal, resulting in antenna utilization efficiency problems because the optimal radiation pattern of the antenna is determined without consideration of a user's assumption factor of Electro-Magnetic Interference (EMI), i.e., Specific Absorption Rate (SAR). The signal transmitted according to the radiation pattern of the antenna can be absorbed as noise by the terminal user's body. Such EMI noise can result in a bad influence to the human body, more particularly, to the brain. SUMMARY OF THE INVENTION [0008]An aspect of the present invention is to address at least the above-mentioned problems and or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a transmission method and apparatus of a mobile terminal that is capable of adjusting an antenna's radiation pattern, resulting in improvement of transmission performance. [0009]Another aspect of the present invention is to provide a transmission method and apparatus of a mobile terminal that is capable of reducing Specific Absorption Rate (SAR) by adjusting an antenna's radiation pattern. [0010]In accordance with an aspect of the present invention, a transmission method of a mobile terminal including an antenna is provided. The method includes determining a posture of the mobile terminal in an active state, updating a preset reference power by adding a power gain determined according to the posture of the mobile terminal, and transmitting a transmit signal amplified according to the updated reference power. [0011]The transmission method may include amplifying the transmit power of the transmit signal according to the reference power and updating, when the transmit power is less than the reference power, the reference power by adding a new power gain. [0012]In accordance with another aspect of the present invention, a transmission apparatus of the mobile terminal is provided. The apparatus includes a posture detection unit for detecting a posture of the mobile terminal in an active state, a control unit for controlling the posture detection unit to update a preset reference power by adding a power gain determined according to the posture of the mobile terminal, a Radio Frequency (RF) unit which amplifies a transmit signal according to the reference power under the control of the control unit, and an antenna for radiating the transmit signal. [0013]The RF unit may include a power amplifier for amplifying a transmit power of the transmit signal according to the reference power, and a power detector for determining whether the transmit power is less than the reference power. [0014]The control unit may update, when the transmit power is less than the reference power, the reference power by adding a new power gain. [0015]Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS [0016]The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee. [0017]The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 is a schematic diagram illustrating a configuration of a wireless communication system to which a transmission method is applied according to an exemplary embodiment of the present invention; [0019]FIG. 2 is a block diagram illustrating a configuration of the mobile terminal of FIG. 1 according to an exemplary embodiment of the present invention; [0020]FIG. 3 is a circuit diagram illustrating a configuration of the Radio Frequency (RF) transmitter of the RF unit of FIG. 2 according to an exemplary embodiment of the present invention; [0021]FIG. 4 is a flowchart illustrating a transmission method of a mobile terminal according to an exemplary embodiment of the present invention; and [0022]FIG. 5 is a diagram illustrating exemplary radiation patterns of an antenna of a mobile terminal according to an exemplary embodiment of the present invention. [0023]Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0024]The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, description of well-known functions and constructions may be omitted for clarity and conciseness. [0025]The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0026]It is to be understood that the singular forms “a,”“an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. [0027]FIG. 1 is a schematic diagram illustrating a configuration of a wireless communication system to which a transmission method is applied according to an exemplary embodiment of the present invention. [0028]Referring to FIG. 1, the wireless communication system includes a base station 100 and a mobile terminal 200. [0029]In the wireless communication system, the base station 100 and the mobile terminal 200 can perform radio communication with each other. Once the mobile terminal 200 has entered a service area of the base station 100, it can receive signals from the base station 100. Within the service area of the base station 100, the mobile terminal 200 connects to the base station 100. At this time, the mobile terminal 200 receives signals from the base station 100. The mobile terminal 200 can transmit and receive signals to and from the base station 100 in an active state. For example, the mobile terminal 200 in an active state can perform a call establishment process with the base station 100 and request or wait for an incoming call in a standby mode. [0030]FIG. 2 is a block diagram illustrating a configuration of the mobile terminal of FIG. 1 according to an exemplary embodiment of the present invention. In an exemplary implementation, descriptions are directed to a mobile phone as a representative mobile terminal. [0031]Referring to FIG. 2, the mobile terminal 200 includes a posture detection unit 210, an antenna 220, a Radio Frequency (RF) unit 230, a control unit 240, a memory unit 250, an audio processing unit 260, a display unit 270, and a key input unit 280. [0032]The posture detection unit 210 detects a posture of the mobile terminal 200. That is, the posture detection unit 210 can determine at least one of an angle and location in relation to the ground. The posture detection unit 210 can be implemented by at least one of an acceleration sensor, a gyro sensor, and a terrestrial magnetic sensor. [0033]The antenna 220 receives and transmits radio signals. That is, the antenna 220 radiates and receives radio signals. At this time, Total Radiate Power (TRP) of the transmit signal is determined based on a unique antenna gain of the antenna 220. Here, the antenna gain is determined based on the shape and electric features of the antenna 220. That is, when the transmit signal is input to the antenna with conduction power, the antenna gain is added to the conduction power such that the radiation power is determined based on the conduction power. Accordingly, the transmit signal is radiated with the radiation power at the antenna 220. For example, if the conduction power is 30 dBm and the antenna gain is −3 dBm, the antenna radiates the transmit signal at the radiation power of 27 dBm. [0034]The antenna 220 transmits the transmit signal and receives the receive signal in a preset radiation pattern. Here, the radiation pattern is formed according to the radiation power of the transmit signal to be radiated by the antenna 220. That is, the radiation pattern can vary according to the radiation power of the transmit signal. The antenna 220 can radiate the transmit signal in an asymmetrically-formed radiation pattern in all directions. The antenna 220 also can radiate the transmit signal in a symmetrically-formed radiation pattern in all directions. [0035]The RF unit 230 processes radio frequency signals. The RF unit 210 includes a RF transmitter and a RF receiver. The RF transmitter process the transmit signal to be radiated by means of the antenna 220. The RF receiver processes the radio signal received by means of the antenna 220. [0036]FIG. 3 is a circuit diagram illustrating a configuration of the RF transmitter of the RF unit of FIG. 2 according to an exemplary embodiment of the present invention. [0037]Referring to FIG. 3, the RF transmitter of the RF unit 230 includes a mixer 231, a transceiver 233, a power amplifier 235, a duplexer 237, and a power detector 239. [0038]The mixer 231 transforms the transmit signal frequency. That is, the mixer 231 up-converts the transmit signal frequency from a baseband signal to an intermediate band signal. The transceiver 233 adjusts the frequency of the transmit signal. That is, the transceiver 233 performs filtering to the transmit signal to acquire the necessary frequency bandwidth. That power amplifier 235 amplifies the transmit power according to the reference power. That is, the power amplifier 235 amplifies the transmit power of the transmit signal in correspondence with the reference power. The duplexer 237 outputs the transmit signal to the antenna 220. At this time, the duplexer 237 blocks the received signal to the RF transmitter and guides the received signal from the antenna 220 to the RF receiver. That is, the duplexer 237 separates the transmit and receive signals from each other. When the receive signal is input by means of the antenna 220, the duplexer 237 delivers the receive signal to the RF receiver. The power detector 220 detects the transmit power of the transmit signal. That is, the power detector 239 measures the transmit power of the transmit signal at the input end of the antenna 220. [0039]The control unit 240 controls entire operations of the mobile terminal 200. The control unit 240 includes a data processing unit having a transmitter for encoding and modulating the transmit signal and a receiver for demodulating and decoding the receive signal. The data processing unit can include a modem and a codec pack. Here, the codec pack includes a data codec for processing packet data and an audio codec for processing an audio signal including voice. More particularly in an exemplary implementation, the control unit 240 controls the reference power to be applied to the transmit signal in an active state. The control unit 240 controls the RF unit 230 to amplify the transmit power of the transmit signal according to the reference power. [0040]That is, the control unit 240 configures the reference power by analyzing the receive signal in an active state. Here, the control unit 240 can configure the reference power according to the received signal strength. The control unit 240 also can configure the reference power such that the radiation power becomes greater than a preset threshold value. For example, the control unit 240 can configure the reference power such that the sum of the reference power and the antenna gain is greater than the preset threshold value. The control unit 240 also can configure the reference power periodically. When signal reception is detected, the control unit can configure the reference power. Also, the control unit 240 can configure the reference power such that the radiation power is greater than the preset threshold value. [0041]The control unit 240 also determines the posture of the mobile terminal 200 in an active state. Here, the control unit 240 determines the posture of the mobile terminal 200 based on at least one of an angle or position of the mobile terminal in relation to the ground. The control unit 240 also determines a power gain based on the posture of the mobile terminal 200. The control unit 240 updates the reference power by adding the power gain to the reference power. [0042]The control unit 240 also compares the transmit power of the transmit signal with the reference power. That is, the control unit 240 determines whether the transmit power is less than the reference power. If the transmit power is less than the reference power, the control unit determines the power gain. Here, the control unit 240 can determine the power gain according to the difference between the transmit power and the reference power. The control unit 240 updates the reference power by adding the power gain to the reference power. [0043]The memory unit 250 can include a program memory and a data memory. The program memory stores the programs necessary for controlling general operations of the mobile terminal 200. The program memory can store the programs necessary for adjusting the reference power to be applied to the transmit power according to an exemplary embodiment of the present invention. The data memory stores the data generated while the programs are running. At this time, the data memory can store the power gains corresponding to the postures available for the mobile terminal 200 according to an exemplary embodiment of the present invention. The memory unit 250 also can store the power gains corresponding to the values comparable to the difference value between the transmit power and the reference power according to an exemplary embodiment of the present invention. [0044]The audio processing unit 260 processes the audio signal output by the audio codec of the data processing unit to be played out through a Speaker (SPK) and transfers the transmit audio signal collected through a Microphone (MIC) to the audio codec of the data processing unit. [0045]The display unit 270 displays user data output by the control unit 240. The display unit may be implemented with a Liquid Crystal Display (LCD) and, in this case, the display unit 270 can include an LCD controller, a video memory for storing video data, and LCD devices. In a case where a touchscreen is enabled, the display unit 270 can function as an input device. [0046]The key input unit 280 is provided with a plurality of alphanumeric keys for data input and function keys for setting various functions. [0047]FIG. 4 is a flowchart illustrating a transmission method of a mobile terminal according to an exemplary embodiment of the present invention. FIG. 5 is a diagram illustrating exemplary radiation patterns of an antenna of a mobile terminal according to an exemplary embodiment of the present invention. [0048]Referring to FIG. 4, in the transmission method, the mobile terminal 200 first operates in an active state at step 411. In the active state, the control unit 240 can receive radio signals. In the active state, the control unit configures the reference power at step 413. Here, the control unit 240 can configure the reference power by analyzing the received signal. For example, the control unit 240 can configure the reference power in accordance with the strength of the received signal. The control unit 240 can configure the reference power periodically and can configure the reference power when signal reception is detected. The control unit 240 also can configure the reference power such that the radiation power is greater than a preset threshold power. For example, the control unit 240 can configure the reference power such that the sum of the reference power and the antenna gain is greater than the preset threshold value. For example, if the threshold value is 27 dBm and the antenna gain is −3 dBm, the control unit 240 can set the reference power to 30 dBm. [0049]The control unit 240 then determines the posture of the mobile terminal 200 at step 415. At this time, the control unit 240 determines the posture of the mobile terminal 200 based on at least one of an angle and position of the mobile terminal 200 in relation to the ground. The control unit 240 then determines the power gain according to the posture of the mobile terminal 200 at step 417. At this time, the memory unit 250 can store the power gains corresponding to the angles available in relation with the group as shown in Table 1. That is, the control unit 240 can select the power gain corresponding to the current posture of the mobile terminal 200. For example, when the mobile terminal 200 makes an angle of 90° in relation to the ground, the control unit 240 can select the power gain of +1 dBm. [0050]TABLE 1PosturePower gain (dBm) 76° to 105°+1106° to 165°  0166° to 195°−1—————— [0051]The control unit 240 updates the reference power at step 419. That is, the control unit 240 adds the power gain to the reference power. For example, if the reference power is 30 dBm and the power gain is +1 dBm, the control unit updates the reference power to 31 dBm. The control unit 240 processes the transmit signal at step 421. That is the control unit 240 generates the transmit signal. Sequentially, the control unit 240 controls the RF unit 230 to transmit the transmit signal through the antenna 220. [0052]At this time, the control unit 240 controls the RF transmitter to amplify the transmit power according to the reference power. Here, the power amplifier 235 amplifies the transmit power of the transmit signal with reference to the reference power. In this manner, the radiation power of the antenna 220 is determined based on the transmit power and antenna gain, and the radiation power is determined to be greater than the threshold value. Here, the antenna 220 radiates the transmit signal in the radiation pattern corresponding to the radiation power. For example, the radiation power is 28 dBm, the antenna 220 can radiate the transmit signal in the radiation pattern formed asymmetrically at the center of the antenna 220 as illustrated in part (a) of FIG. 5. If the radiation power 27 dBm, the antenna 220 can radiate the transmit signal in the radiation pattern formed symmetrically at the center of the antenna 220 as illustrated in part (b) of FIG. 5. [0053]Finally, the control unit 240 compares the transmit power of the transmit signal with the reference power at step 423. That is, the transmit power is detected by means of the power detector 239, the control unit 240 determines whether the transmit power is less than the reference power. In this manner, the control unit 240 can determine whether there is power loss in the transmit power as compared to the reference power. If it is determined that the transmit power is equal to or greater than the reference power at step 423, the control unit 240 ends the transmit procedure. [0054]Otherwise, if it is determined that the transmit power is less than the reference power at step 423, the control unit 240 determines the power gain at step 417. That is, if the transmit power is less than the reference power, the control unit 24 determines an occurrence of power loss and thus decides the power gain. For this purpose, the memory unit 250 can store the power gains corresponding to the individual comparison values that can be compared with the difference values between the transmit power and the reference power as shown in Table 2. That is, the control unit 240 can select the power gain corresponding to the difference value between the transmit power and the reference power. For example, if the difference value between the transmit power and the reference power is 2 dBm, the control unit 240 can select the power gain of +1 dBm. Thereafter, the control unit 240 repeats steps 419 to 423. [0055]TABLE 2PosturePower gain (dBm)Greater than 1+2Less than 1 and greater than 0+1Less than 0 and greater than −1  0—————— [0056]Although the description has been directed to the exemplary embodiments where the mobile terminal transmits or receives radio signals through the antenna, the present invention is not limited thereto. For example, exemplary embodiments of the present invention can be applied to the case where the mobile terminal having a transmit antenna and a receive antenna separated from each other. In this case, the function blocks of the mobile terminal operate in a similar manner as described above. However, the duplexer is disabled in the mobile terminal. The power amplifier of the mobile terminal amplifies the transmit signal according to the reference power and transfers the amplified signal to the antenna. In this manner, the mobile terminal adjusts the reference power to be applied to the transmitted signal in an active state and amplifies the transmit power of the transmit signal according to the reference power. [0057]According to exemplary embodiments of the present invention, the mobile terminal can control the radiation pattern of the antenna. That is, the mobile terminal can adjust the reference power to control the radiation pattern of the antenna without changing the shape of the antenna. By adjusting the reference power according to the posture of the mobile terminal, it is possible for the mobile terminal to transmit a signal in a radiation pattern corresponding to the terminal's posture. Also, since the reference power is adjusted based on a comparison result with the transmit power, the mobile terminal can perform fine adjustment of the radiation power. [0058]When the mobile terminal transmits the signal in the radiation pattern formed symmetrically in all directions and centered on the antenna, the Specific Absorption Rate (SAR) can be relatively high. In this case, the reference power is adjusted according to the posture of the mobile terminal such that the mobile terminal can transmit the signal in the radiation pattern formed asymmetrically in all directions and centered on the antenna. In this manner, the mobile terminal can reduce the SAR to the user. For example, when the mobile terminal is in the middle of the communication mode, the posture of the mobile terminal is likely to have the rectangular angle in relation to the ground. In this case, the mobile terminal transmits the signal in the radiation pattern formed asymmetrically in all directions and centered on the antenna, to reduce the SAR. [0059]As described above, the transmission method and apparatus of the mobile terminal having an antenna according to an exemplary embodiment of the present invention can control the radiation pattern of the antenna of the mobile terminal. That is, it is possible to control the radiation pattern of the antenna by adjusting the reference power of the mobile terminal. At this time, the reference power is adjusted according to the posture of the mobile terminal, and thus the mobile terminal can transmit the signal in the radiation pattern corresponding to the posture of the mobile terminal. Also, since the reference power is adjusted according to the comparison result with the transmit power, it is possible to apply fine adjustment of radiation power to the mobile terminal. [0060]When transmitting a signal in the radiation pattern formed symmetrically in all directions and centered on the antenna, the SAR to the user can be relatively high. By adjusting the reference power according to the posture of the mobile terminal, the mobile terminal can transmit the signal in the radiation pattern formed asymmetrically in all direction centering the antenna. In this manner, it is possible to reduce the SAR to the mobile terminal user. For example, in the wireless communication system, the mobile terminal is likely to be postured to have the vertical angle to the ground. At this time, the mobile terminal transmits the signal in the radiation pattern formed asymmetrically in all directions and centered on the antenna, resulting in reduction of SAR of the mobile terminal to the human body. [0061]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims and their equivalents.(String), 优先 [0001] 此申请根据 35 U.S.C. 2011 年 2 月 16 日向韩国知识产权局提交并转让序列号为 10-2011-0013563 的韩国专利申请的第 119(a) 条,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动终端。 更具体地,本发明涉及在无线通信系统中具有天线的移动终端的传输方法和装置。 [0004] 2.相关技术的描述 [0005] 近来,无线通信系统已被设计为支持基于诸如全球定位系统(GPS)、蓝牙和互联网等综合补充功能的各种多媒体服务。 为了便于提供各种多媒体服务,必须确保高数据速率以传输大量多媒体数据。 天线是决定传输性能的一个因素。 由于移动终端的天线主要负责传输承载多媒体服务的信号,因此进行了研究以获得高质量的天线特征。 在移动通信终端中,优选将天线实现为具有最佳辐射方向图。 在制造状态下,通过多次调谐过程可以获得最佳的辐射方向图。 [0006] 同时,移动通信终端采用纤薄紧凑的设计制造,以确保便携性。 传统的天线,如杆状天线和螺旋天线,部分暴露在终端外壳之外,这会损害便携性并导致天线的物理损坏。 为了解决这些问题,最近的移动终端已经配备了内置天线,也称为天线。 [0007] 然而,传统的移动终端被设计成以被确定为最优的固定辐射方向图发送信号,导致天线利用效率问题,因为天线的最佳辐射方向图是在没有考虑用户的电磁干扰假设因素的情况下确定的( EMI),即比吸收率(SAR)。 根据天线的辐射图发射的信号可以被终端用户的身体吸收为噪声。 这种EMI噪声会对人体产生不良影响,尤其是对大脑。 发明内容 [0008] 本发明的一个方面是至少解决上述问题和/或缺点并提供至少下述优点。 因此,本发明的一个方面是提供一种移动终端的传输方法和装置,其能够调整天线的辐射方向图,从而提高传输性能。 [0009] 本发明的另一方面在于提供一种能够通过调整天线的辐射图来降低比吸收率(SAR)的移动终端的传输方法和装置。 [0010] 根据本发明的一个方面,提供了一种包括天线的移动终端的传输方法。 该方法包括确定处于活动状态的移动终端的姿势,通过添加根据移动终端的姿势确定的功率增益来更新预设的参考功率,以及发送根据更新的参考功率放大的发射信号。 [0011] 发送方法可以包括根据参考功率放大发送信号的发送功率,并且当发送功率小于参考功率时,通过增加新的功率增益来更新参考功率。 [0012]根据本发明的另一方面,提供了一种移动终端的传输装置。 该装置包括:姿态检测单元,用于检测移动终端处于活动状态的姿态;控制单元,用于控制姿态检测单元通过添加根据移动终端的姿态确定的功率增益来更新预设参考功率, 射频(RF)单元在控制单元的控制下根据参考功率放大发射信号,以及用于辐射发射信号的天线。 [0013] RF单元可包括用于根据参考功率放大发射信号的发射功率的功率放大器,以及用于确定发射功率是否小于参考功率的功率检测器。 [0014] 当发射功率小于参考功率时,控制单元可以通过增加新的功率增益来更新参考功率。 [0015] 根据以下结合附图公开本发明示例性实施例的详细描述,本领域技术人员将清楚本发明的其他方面、优点和显着特征。 附图的简要说明 [0016] 专利或申请文件包含至少一幅彩色绘图。 专利局将根据请求和支付必要的费用提供本专利或专利申请出版物的彩色附图副本。 [0017] 本发明的某些示例性实施例的上述和其他方面、特征和优点将从以下结合附图的描述中变得更加明显,其中: [0018] 图1是图示应用根据本发明示例性实施例的传输方法的无线通信系统的配置的示意图; [0019] 图2是示出根据本发明示例性实施例的图1的移动终端的配置的框图; [0020] 图3是示出根据本发明示例性实施例的图2的RF单元的射频(RF)发送器的配置的电路图; [0021] 图4是示出根据本发明示例性实施例的移动终端的传输方法的流程图; 和 [0022] 图5是图示根据本发明示例性实施例的移动终端的天线的示例性辐射图案的图。 [0023] 在整个附图中,应当注意,相似的附图标记用于描绘相同或相似的元件、特征和结构。 示例性实施例的详细描述 [0024] 提供参考附图的以下描述以帮助全面理解由权利要求及其等同物限定的本发明的示例性实施例。 它包括有助于理解的各种具体细节,但这些仅被视为示例性的。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对本文描述的实施例进行各种改变和修改。 此外,为了清楚和简明起见,可以省略对公知功能和构造的描述。 [0025] 以下描述和权利要求中使用的术语和词语不限于参考文献的含义,而只是由发明人使用以使得能够清楚和一致地理解本发明。 因此,对于本领域的技术人员来说显而易见的是,本发明的示例性实施例的以下描述仅出于说明的目的而提供,而不是为了限制如所附权利要求及其等同物所定义的本发明的目的。 [0026]应当理解,单数形式“a”、“an”和“the”包括复数指示物,除非上下文另有明确规定。 因此,例如,对“部件表面”的引用包括对一个或多个这样的表面的引用。 [0027] 图1是示出应用根据本发明示例性实施例的传输方法的无线通信系统的配置的示意图。 [0028] 参考图1,无线通信系统包括基站 100 和一个移动终端 200 . [0029] 在无线通信系统中,基站 100 和移动终端 200 可以相互进行无线电通信。 一旦移动端 200 已进入基站服务区 100 ,它可以接收来自基站的信号 100 . 基站服务区内 100 , 移动端 200 连接到基站 100 . 这时,移动端 200 从基站接收信号 100 . 移动终端 200 可以向基站发送和接收信号 100 处于活动状态。 例如,移动终端 200 在激活状态下可以与基站进行呼叫建立过程 100 并在待机状态下请求或等待来电。 [0030] 图2是示出根据本发明示例性实施例的图1的移动终端的配置的框图。 在示例性实施方式中,描述针对作为代表性移动终端的移动电话。 [0031] 参见图2,移动终端 200 包括姿势检测单元 210 , 天线 220 , 一个射频 (RF) 单元 230 , 一个控制单元 240 , 一个记忆单元 250 , 一个音频处理单元 260 , 一个显示单元 270 , 和一个按键输入单元 280 . [0032] 姿态检测单元 210 检测移动终端的姿态 200 . 即姿态检测单元 210 可以确定相对于地面的角度和位置中的至少一个。 姿态检测单元 210 可以通过加速度传感器、陀螺仪传感器和地磁传感器中的至少一种来实现。 [0033] 天线 220 接收和发送无线电信号。 也就是天线 220 发射和接收无线电信号。 此时,发射信号的总辐射功率(TRP)是根据天线的唯一天线增益确定的 220 . 这里,天线增益是根据天线的形状和电特性确定的 220 . 即,当发射信号以传导功率输入到天线时,天线增益被添加到传导功率,使得基于传导功率确定辐射功率。 因此,发射信号在天线处以辐射功率辐射 220 . 例如,如果传导功率为 30 dBm,天线增益为 -3 dBm,则天线以 27 dBm 的辐射功率辐射发射信号。 [0034] 天线 220 以预设的辐射方向图发射发射信号并接收接收信号。 这里,辐射图是根据天线要辐射的发射信号的辐射功率形成的 220 . 也就是说,辐射图可以根据发射信号的辐射功率而变化。 天线 220 可以在所有方向以不对称形成的辐射模式辐射发射信号。 天线 220 也可以在所有方向以对称形成的辐射模式辐射发射信号。 [0035] 射频单元 230 处理射频信号。 射频单元 210 包括射频发射器和射频接收器。 RF发射器处理要通过天线辐射的发射信号 220 . RF接收器处理通过天线接收到的无线电信号 220 . [0036]图3是示出根据本发明示例性实施例的图2的RF单元的RF发射器的配置的电路图。 [0037] 参考图3,射频单元的射频发射器 230 包括一个混合器 231 , 收发器 233 , 功率放大器 235 , 双工器 237 , 和一个功率检测器 239 . [0038] 搅拌机 231 变换发射信号频率。 也就是搅拌机 231 将发射信号频率从基带信号上变频到中带信号。 收发器 233 调整发射信号的频率。 也就是收发器 233 对发射信号进行滤波以获得必要的频率带宽。 那个功放 235 根据参考功率放大发射功率。 也就是功放 235 对应于参考功率放大发射信号的发射功率。 双工器 237 将发射信号输出到天线 220 . 这时,双工器 237 阻止接收到的信号到射频发射器并引导从天线接收到的信号 220 到射频接收器。 也就是双工器 237 将发送和接收信号相互分离。 通过天线输入接收信号时 220 , 双工器 237 将接收信号传送到射频接收器。 功率检测器 220 检测发射信号的发射功率。 也就是说,功率检测器 239 测量天线输入端发射信号的发射功率 220 . [0039] 控制单元 240 控制移动终端的整个操作 200 . 控制单元 240 包括数据处理单元,其具有用于编码和调制发射信号的发射器和用于解调和解码接收信号的接收器。 数据处理单元可以包括调制解调器和编解码器包。 这里,编解码器包包括用于处理分组数据的数据编解码器和用于处理包括语音的音频信号的音频编解码器。 更具体地,在示例性实施方式中,控制单元 240 控制在激活状态下施加到发射信号的参考功率。 控制单元 240 控制射频单元 230 根据参考功率放大发射信号的发射功率。 [0040] 也就是说,控制单元 240 通过分析处于活动状态的接收信号来配置参考功率。 这里,控制单元 240 可以根据接收到的信号强度配置参考功率。 控制单元 240 还可以配置参考功率,使得辐射功率变得大于预设阈值。 例如,控制单元 240 可以配置参考功率,使得参考功率与天线增益之和大于预设阈值。 控制单元 240 也可以定期配置参考功率。 当检测到信号接收时,控制单元可以配置参考功率。 此外,控制单元 240 可以配置参考功率,使得辐射功率大于预设阈值。 [0041] 控制单元 240 也决定了移动端的姿势 200 处于活动状态。 这里,控制单元 240 确定移动终端的姿势 200 基于移动终端相对于地面的角度或位置中的至少一个。 控制单元 240 还根据移动终端的姿势确定功率增益 200 . 控制单元 240 通过将功率增益添加到参考功率来更新参考功率。 [0042] 控制单元 240 还将发射信号的发射功率与参考功率进行比较。 也就是说,控制单元 240 判断发射功率是否小于参考功率。 如果发射功率小于参考功率,则控制单元确定功率增益。 这里,控制单元 240可以根据发射功率和参考功率的差值来确定功率增益。 控制单元 240 通过将功率增益添加到参考功率来更新参考功率。 [0043] 记忆单元 250 可以包括程序存储器和数据存储器。 程序存储器存储控制移动终端的一般操作所需的程序 200 . 根据本发明的示例性实施例,程序存储器可以存储调整要应用于发射功率的参考功率所需的程序。 数据存储器存储程序运行时生成的数据。 此时,数据存储器可以存储移动终端可用姿势对应的功率增益 200 根据本发明的示例性实施例。 记忆单元 250 根据本发明的示例性实施例,还可以存储与与发射功率和参考功率之间的差值相当的值相对应的功率增益。 [0044] 音频处理单元 260 将数据处理单元的音频编解码器输出的音频信号处理后通过扬声器(SPK)进行播放,并将通过麦克风(MIC)采集的发射音频信号传送到数据处理单元的音频编解码器。 [0045] 显示单元 270 显示控制单元输出的用户数据 240 . 显示单元可以用液晶显示器 (LCD) 来实现,在这种情况下,显示单元 270 可以包括 LCD 控制器、用于存储视频数据的视频存储器和 LCD 设备。 在启用触摸屏的情况下,显示单元 270 可以作为输入设备使用。 [0046] 按键输入单元 280 具有多个用于数据输入的字母数字键和用于设置各种功能的功能键。 [0047] 图4是示出根据本发明示例性实施例的移动终端的传输方法的流程图。 图5是示出根据本发明示例性实施例的移动终端的天线的示例性辐射方向图的图。 [0048] 参见图4,在传输方法中,移动终端 200 首先在步骤中以活动状态运行 411 . 在激活状态下,控制单元 240 可以接收无线电信号。 在激活状态下,控制单元在步骤配置参考功率 413 . 这里,控制单元 240 可以通过分析接收到的信号来配置参考功率。 例如,控制单元 240 可以根据接收信号的强弱配置参考功率。 控制单元 240 可以周期性地配置参考功率,并且可以在检测到信号接收时配置参考功率。 控制单元 240 还可以配置参考功率,使得辐射功率大于预设的阈值功率。 例如,控制单元 240 可以配置参考功率,使得参考功率与天线增益之和大于预设阈值。 例如,如果阈值为 27 dBm,天线增益为 -3 dBm,则控制单元 240 可以将参考功率设置为 30 dBm。 [0049] 控制单元 240 然后确定移动终端的姿势 200 在步骤 415 . 这时,控制单元 240 确定移动终端的姿势 200 基于移动终端的角度和位置中的至少一个 200 相对于地面。 控制单元 240 然后根据移动终端的姿态确定功率增益 200 在步骤 417 . 这时,内存单元 250 可以存储与组相关的可用角度对应的功率增益,如表 1 所示。即,控制单元 240 可选择移动终端当前姿势对应的功率增益 200 . 例如,当移动终端 200 与地面成 90° 角,控制单元240 可选择+1 dBm的功率增益。 [0050] 表格1 姿势 功率增益 (dBm) 76° 至 105° +1 106° 至 165°   0 166° 至 195° −1 — — — — — — [0051] 控制单元 240 在步骤更新参考功率 419 . 也就是说,控制单元 240 将功率增益添加到参考功率。 例如,如果参考功率为 30 dBm,功率增益为 +1 dBm,则控制单元将参考功率更新为 31 dBm。 控制单元 240 在步骤处理发送信号 421 . 那是控制单元 240 产生发射信号。 依次,控制单元 240 控制射频单元 230 通过天线发射发射信号 220 . [0052] 这时,控制单元 240 控制射频发射器根据参考功率放大发射功率。 这里的功放 235 参考参考功率放大发射信号的发射功率。 这样,天线的辐射功率 220 是基于发射功率和天线增益确定的,辐射功率被确定为大于阈值。 在这里,天线 220 以对应于辐射功率的辐射方向图来辐射发射信号。 例如,辐射功率为 28 dBm,天线 220 可以在天线中心不对称形成的辐射方向图中辐射发射信号 220 如图5(a)部分所示。如果辐射功率为27 dBm,则天线 220 可以在天线中心对称形成的辐射方向图中辐射发射信号 220 如图 5 的 (b) 部分所示。 [0053] 最后,控制单元 240 将发射信号的发射功率与参考功率进行比较 423 . 即通过功率检测器检测发射功率 239 , 控制单元 240 判断发射功率是否小于参考功率。 这样,控制单元 240 可以确定发射功率与参考功率相比是否存在功率损耗。 如果在步骤确定发射功率等于或大于参考功率 423 , 控制单元 240 结束发送过程。 [0054] 否则,如果在步骤确定发射功率小于参考功率 423 , 控制单元 240 确定步长的功率增益 417 . 也就是说,如果发射功率小于参考功率,则控制单元 24 确定功率损耗的发生,从而决定功率增益。 为此,存储单元 250 可以存储对应于各个比较值的功率增益,该比较值可以与发射功率和参考功率之间的差值进行比较,如表2所示。即,控制单元 240 可以选择与发射功率和参考功率之间的差值相对应的功率增益。 例如,如果发射功率和参考功率之间的差值为 2 dBm,则控制单元 240 可选择+1 dBm的功率增益。 此后,控制单元 240 重复步骤 419 至 423 . [0055] 表 2 姿势 功率增益 (dBm) 大于 1 +2 小于 1 且大于 0 +1 小于 0 且大于 -1   0 — — — — — — [0056] 尽管描述已经针对移动终端通过天线发送或接收无线电信号的示例性实施例,但是本发明不限于此。 例如,本发明的示例性实施例可以应用于移动终端具有彼此分离的发射天线和接收天线的情况。 在这种情况下,移动终端的功能块以与上述类似的方式操作。 然而,双工器在移动终端中被禁用。 移动终端的功率放大器根据参考功率对发射信号进行放大,并将放大后的信号传输到天线。 以这种方式,移动终端在激活状态下调整要应用于发射信号的参考功率,并根据参考功率放大发射信号的发射功率。 [0057] 根据本发明的示例性实施例,移动终端可以控制天线的辐射方向图。 也就是说,移动终端可以在不改变天线形状的情况下调整参考功率来控制天线的辐射方向图。 通过根据移动终端的姿势调整参考功率,移动终端可以以与终端的姿势对应的辐射图发射信号。 此外,由于参考功率是基于与发射功率的比较结果来调整的,因此移动终端可以对辐射功率进行微调。 [0058] 当移动终端以天线为中心在各个方向对称形成的辐射图发射信号时,比吸收率(SAR)可以相对较高。 在这种情况下,参考功率根据移动终端的姿态进行调整,使得移动终端可以以天线为中心在所有方向上不对称形成的辐射图发射信号。 以这种方式,移动终端可以降低对用户的SAR。 例如,当移动终端处于通信模式的中间时,移动终端的姿态很可能与地面呈直角。 在这种情况下,移动终端以天线为中心在所有方向不对称形成的辐射方向图发送信号,以降低SAR。 [0059] 如上所述,根据本发明示例性实施例的具有天线的移动终端的传输方法和装置可以控制移动终端的天线的辐射方向图。 也就是说,可以通过调整移动终端的参考功率来控制天线的辐射方向图。 此时,根据移动终端的姿态调整参考功率,从而使移动终端能够以与移动终端的姿态对应的辐射图发射信号。 此外,由于根据与发射功率的比较结果来调整参考功率,因此可以对移动终端应用辐射功率的微调。 [0060] 当以天线为中心在所有方向上对称形成的辐射方向图传输信号时,对用户的 SAR 可能相对较高。 通过根据移动终端的姿势调整参考功率,移动终端可以在以天线为中心的所有方向上不对称形成的辐射图发射信号。 以这种方式,可以降低对移动终端用户的SAR。 例如,在无线通信系统中,移动终端很可能被摆成与地面具有垂直角的姿势。 此时,移动终端以天线为中心,向各个方向不对称形成的辐射方向图发射信号,导致移动终端对人体的SAR降低。 [0061] 尽管本发明已经参照其某些示例性实施例进行了展示和描述,但是本领域技术人员可以在不背离本发明的精神和范围的情况下对其中的形式和细节进行各种改变。 附加的权利要求及其等价物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101778528B1(String), KR1020120094213A(String), US20120208554A1(String), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101778528B1(String), KR1020120094213A(String), US20120208554A1(String), US9144032B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101778528B1(String), KR1020120094213A(String), US20120208554A1(String), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271663(Integer), KR101778528B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271663(Integer), KR1020120094213A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271663(Integer), US20120208554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271663(Integer), US9144032B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:23.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9144032B2(String), US9144032B2(String), 1442851200(Integer), 271663(Integer), 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.100 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185985(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185985(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO. LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1662111618(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25448(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.202 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185985(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25448(Integer), 2(Integer), 185985(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25448(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US11126275B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US11126275B2(String), An apparatus for presenting a panoramic photo in a mobile terminal receives a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle.(String), 一种在移动终端中呈现全景照片的装置,接收触发指令,用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式 ; 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。(String), US16/841961(String), 1586188800(Integer), US11126275B2(String), 1632153600(Integer), 1632153600(Integer), 美国(String), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9342998B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:24.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185986(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.111 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ac9de6d67f4b4563bc94daebb2c69223.png(String), 185986(Integer), ac9de6d67f4b4563bc94daebb2c69223.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.164 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.165 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and apparatus for presenting panoramic photo in mobile terminal, and mobile terminal(String), 移动终端中全景照片的呈现方法、装置及移动终端(String), US11126275B2(String), An apparatus for presenting a panoramic photo in a mobile terminal receives a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates; and if the trigger instruction is detected, a rotation angle of the mobile terminal is detected and determined, and a panoramic photo that is presented in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle.(String), 一种在移动终端中呈现全景照片的装置,接收触发指令,用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式 ; 如果检测到触发指令,则检测并确定移动终端的旋转角度,并根据确定的旋转角度移动并呈现移动终端中正常模式呈现的全景照片。(String), US16/841961(String), 1586188800(Integer), US11126275B2(String), 1632153600(Integer), 1632153600(Integer), 美国(String), 3(Integer), 4(Integer), 8(Integer), 56(Integer), CN101872243A | CN102023790A | CN102104641A | CN102272690A | CN102314179A | CN102420898A | CN102572258A | CN102591014A | CN103106335A | CN103176347A | CN103530799A | CN103543831A | CN103561209A | CN103841332A | CN104243805A | CN1589050A | JP2004317548A | US10222877B2 | US20050237383A1 | US20070071361A1 | US20070109398A1 | US20070263995A1 | US20090325607A1 | US20100123737A1 | US20100174421A1 | US20110110605A1 | US20110149015A1 | US20110173565A1 | US20120075410A1 | US20120293610A1 | US20120294549A1 | US20130176384A1 | US20130229529A1 | US20140152562A1 | US20140168356A1 | US20140194164A1 | US20140210940A1 | US20140267441A1 | US20140375760A1 | US20150178257A1 | US20150189175A1 | US20160014921A1 | US5594845A | US6118595A | US6677981B1 | US6717608B1 | US6885392B1 | US7733368B2 | US8711174B2 | US9342998B2 | US9582168B2 | US9621802B2 | US9635254B2 | US9729788B2 | US9865033B1 | US9894272B2(String), \20230420\ac9de6d67f4b4563bc94daebb2c69223.png(String), 20(Integer), 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.200 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 1. A method for presenting a panoramic photo using a mobile terminal, the method comprising:photographing the panoramic photo while the mobile terminal is moving in a first direction;storing attribute information of the panoramic photo, wherein the attribute information includes a photo type indicating that the panoramic photo is panoramic;displaying only a part of the panoramic photo in a normal mode;receiving a slide operation on the panoramic photo in the normal mode;displaying another part of the panoramic photo in response to the slide operation in the normal mode;receiving an instruction for entering an immersive browsing mode; andperforming the following when in the immersive browsing mode:displaying only a first part of the panoramic photo;detecting the mobile terminal rotating in the first direction;displaying a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detecting the mobile terminal rotating in a second direction; anddisplaying a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 1.一种使用移动终端呈现全景照片的方法,该方法包括:移动终端在第一方向移动时拍摄全景照片;存储全景照片的属性信息,其中,属性信息包括表示全景照片为全景的照片类型;在正常模式下仅显示全景照片的一部分;在正常模式下接收对全景照片的滑动操作;在正常模式下响应滑动操作显示全景照片的另一部分;接收进入沉浸式浏览模式的指令;和在沉浸式浏览模式下执行以下操作:仅显示全景照片的第一部分;检测移动终端沿第一方向旋转;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 2. The method of claim 1, wherein the first direction is either from left to right or from right to left, and wherein the first direction is stored in the attribute information.(String), 2.如权利要求1所述的方法,其中第一方向是从左到右或从右到左,其中第一方向存储在属性信息中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 3. The method of claim 2, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 3.如权利要求2所述的方法,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 4. The method of claim 1, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 4.如权利要求1所述的方法,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 5. The method of claim 1, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 5.如权利要求1所述的方法,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 6. The method of claim 1, further comprising:displaying an icon in the normal mode;detecting an input on the icon; andentering the immersive browsing mode in response to detecting the input on the icon.(String), 6.如权利要求1所述的方法,还包括:在正常模式下显示图标;检测图标上的输入;和响应于检测到图标上的输入而进入沉浸式浏览模式。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 7. The method of claim 1, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 7.如权利要求1所述的方法,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 8. The method of claim 7, further comprising:detecting a rotation angle of the mobile terminal in real time; anddisplaying the panoramic photo in the movable way when the rotation angle is greater than a preset rotation angle threshold.(String), 8.如权利要求7所述的方法,还包括:实时检测移动终端的旋转角度;和当旋转角度大于预设的旋转角度阈值时,以可移动的方式显示全景照片。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 9. The method of claim 8, further comprising determining a minimum movement value of the movable way using the following equation:s=d⁢φ1φ2,wherein s is the minimum movement value, wherein d is a width of the panoramic photo, wherein φ1 is the preset rotation angle threshold, and wherein φ2 is a rotation angle of the mobile terminal photographing the panoramic photo in the first direction.(String), 9.如权利要求8所述的方法,还包括使用以下等式确定可移动方式的最小移动值:s=d⁢φ1φ2,其中s为最小移动值,d为全景照片的宽度,其中φ1为预设旋转角度阈值,其中φ2为移动终端拍摄全景照片在第一方向的旋转角度。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 10. The method of claim 1, wherein rotation of the mobile terminal in either the first direction or the second direction is detected by a gyro sensor of the mobile terminal.(String), 10.如权利要求1所述的方法,其中移动终端沿第一方向或第二方向的旋转由移动终端的陀螺仪传感器检测。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 11. A mobile terminal, comprising:a processor; anda memory coupled to the processor and comprising instructions that, when executed by the processor, cause the mobile terminal to:photograph a panoramic photo while the mobile terminal is moving in a first direction;store attribute information of the panoramic photo, wherein the attribute information includes a photo type indicating that the panoramic photo is panoramic;display only a part of the panoramic photo in a normal mode;receive a slide operation on the panoramic photo in the normal mode;display another part of the panoramic photo in response to the slide operation in the normal mode; andreceive an instruction for entering an immersive browsing mode;perform the following when in the immersive mode:display only a first part of the panoramic photo;detect the mobile terminal rotating in the first direction;display a second part of the panoramic photo in response to detecting the mobile terminal rotating in the first direction;detect the mobile terminal rotating in a second direction; anddisplay a third part of the panoramic photo in response to detecting the mobile terminal rotating in the second direction, wherein the second direction is opposite the first direction, wherein the second part of the panoramic photo is different than the first part of the panoramic photo, and wherein the third part of the panoramic photo is different than the first part of the panoramic photo.(String), 11.移动终端,包括:处理器;和存储器耦合到处理器并且包括当由处理器执行时使移动终端:移动终端在第一方向移动时拍摄全景照片;存储全景照片的属性信息,其中,属性信息包括表示全景照片为全景的照片类型;在正常模式下只显示全景照片的一部分;在普通模式下接收对全景照片的滑动操作;在正常模式下响应滑动操作显示全景照片的另一部分;和接收进入沉浸式浏览模式的指令;在沉浸式模式下执行以下操作:仅显示全景照片的第一部分;检测第一方向旋转的移动终端;响应于检测到移动终端沿第一方向旋转,显示全景照片的第二部分;检测移动终端向第二方向的旋转;和响应于检测到移动终端沿第二方向旋转显示全景照片的第三部分,其中第二方向与第一方向相反,其中全景照片的第二部分不同于全景照片的第一部分,其中,全景照片的第三部分不同于全景照片的第一部分。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 12. The mobile terminal of claim 11, wherein the first direction is either from left to right or from right to left, and wherein the first direction is stored in the attribute information.(String), 12.如权利要求11所述的移动终端,其中第一方向是从左到右或从右到左,其中第一方向存储在属性信息中。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 13. The mobile terminal of claim 12, wherein the first part of the panoramic photo is either a leftmost part of the panoramic photo or a rightmost part of the panoramic photo.(String), 13.如权利要求12所述的移动终端,其中全景照片的第一部分是全景照片的最左部分或全景照片的最右部分。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 14. The mobile terminal of claim 11, wherein the first direction is from left to right, wherein the second part is to the right of the first part, and wherein the third part is to the left of the first part.(String), 14.如权利要求11所述的移动终端,其中第一方向是从左到右,其中第二部分在第一部分的右侧,并且其中第三部分在第一部分的左侧。(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 15. The mobile terminal of claim 11, wherein the first direction is from right to left, wherein the second part is to the left of the first part, and wherein the third part is to the right of the first part.(String), 15.如权利要求11所述的移动终端,其中第一方向是从右到左,其中第二部分在第一部分的左侧,并且其中第三部分在第一部分的右侧。(String), 1(Integer), 14(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 16. The mobile terminal of claim 11, wherein the instructions further cause the mobile terminal to:display an icon in the normal mode;detect an input on the icon; andenter the immersive browsing mode in response to detecting the input on the icon.(String), 16.如权利要求11所述的移动终端,其中该指令进一步使移动终端:在正常模式下显示一个图标;检测图标上的输入;和响应于检测到图标上的输入进入沉浸式浏览模式。(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 17. The mobile terminal of claim 11, wherein the immersive browsing mode is a mode in which the panoramic photo is displayed in a movable way in response to rotation of the mobile terminal.(String), 17.如权利要求11所述的移动终端,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动显示的模式。(String), 1(Integer), 16(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 18. The mobile terminal of claim 17, wherein the instructions further cause the mobile terminal to:detect a rotation angle of the mobile terminal in real time; anddisplay the panoramic photo in the movable way when the rotation angle is greater than a preset rotation angle threshold.(String), 18.如权利要求17所述的移动终端,其中该指令进一步使移动终端:实时检测移动终端的旋转角度;和当旋转角度大于预设的旋转角度阈值时,以可移动的方式显示全景照片。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 19. The mobile terminal of claim 18, wherein the instructions further cause the mobile terminal to determine a minimum movement value of the movable way using the following equation:s=d⁢φ1φ2,wherein s is the minimum movement value, wherein d is a width of the panoramic photo, wherein φ1 is the preset rotation angle threshold, and wherein φ2 is a rotation angle of the mobile terminal photographing the panoramic photo in the first direction.(String), 19.如权利要求18所述的移动终端,其中指令还使移动终端使用以下等式确定可移动方式的最小移动值:s=d⁢φ1φ2,其中s为最小移动值,d为全景照片的宽度,其中φ1为预设旋转角度阈值,其中φ2为移动终端拍摄全景照片在第一方向的旋转角度。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185986(Integer), 20. The mobile terminal of claim 11, further comprising a gyro sensor coupled to the processor and configured to detect rotation of the mobile terminal in either the first direction or the second direction.(String), 20.如权利要求11所述的移动终端,还包括陀螺仪传感器耦合到处理器并被配置为检测移动终端在第一方向或第二方向上的旋转。(String), 1(Integer), 19(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185986(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 16/266,498 filed on Feb. 4, 2019, which is a continuation of U.S. patent application Ser. No. 15/483,724 filed on Apr. 10, 2017, now U.S. Pat. No. 10,222,877, which is a continuation of U.S. patent application Ser. No. 14/735,625 filed on Jun. 10, 2015, now U.S. Pat. No. 9,621,802, which is a continuation of International Patent Application No. PCT/CN2014/079950 filed on Jun. 16, 2014. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal. BACKGROUND [0003]With the rapid development of communications technologies, functions of a mobile terminal become increasingly powerful, and a range and an environment in which a mobile terminal is used become increasingly diverse. For example, currently, many mobile terminals such as mobile phones, personal digital assistants, and personal computers all have a function of panoramic photographing. [0004]When a mobile terminal performs panoramic photographing, a user rotates the mobile terminal to photograph a scene that needs to be photographed. A basic principle of “panoramic photographing” is that edge parts of two photos are searched for, and registration is performed on areas that have closest imaging effects, so as to complete automatic stitching of the photos. Multiple photographed photos may be then stitched as one panoramic photo according to the foregoing stitching principle, and a vision of a scene recorded in the panoramic photo is relatively broad. When browsing a photo, a user may browse relatively rich image content on a panoramic photo, which features a relatively strong visual impact. [0005]However, although currently, relatively rich photo content can be recorded in a panoramic photo, the photo is relatively large when the panoramic photo is presented in a mobile terminal. When browsing the panoramic photo, a user needs to manually slide the photo to browse the photo content, which is relatively complex in terms of operations. SUMMARY [0006]Embodiments of the present disclosure provide a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal, so as to reduce complexity of panoramic photo browsing, and make it convenient for a user to browse a panoramic photo. [0007]According to a first aspect, a method for presenting a panoramic photo in a mobile terminal is provided, including detecting a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, if the trigger instruction is detected, detecting and determining a rotation angle of the mobile terminal, and moving and presenting, according to the determined rotation angle, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0008]With reference to the first aspect, in a first implementation manner, the determining a rotation angle of the mobile terminal includes determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0009]With reference to the first implementation manner of the first aspect, in a second implementation manner, the determining a placement direction in which the mobile terminal is located in a rotation process includes detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0010]With reference to the second implementation manner of the first aspect, in a third implementation manner, the determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process includes when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction; and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0011]With reference to the second implementation manner of the first aspect or the third implementation manner of the first aspect, in a fourth implementation manner, the determining the rotation angle of the mobile terminal according to the placement direction includes if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process; and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0012]With reference to any one of the foregoing implementation manners of the first aspect, in a fifth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0013]With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner, before the moving, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal, the method further includes determining a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the moving a panoramic photo that is presented in a normal mode in the mobile terminal includes moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0014]With reference to the first aspect, in a seventh implementation manner, before the detecting and determining a rotation angle of the mobile terminal, the method further includes providing prompt information that is used to instruct to rotate the mobile terminal. [0015]With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner, before the providing prompt information that is used to instruct to rotate the mobile terminal, the method further includes acquiring a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the providing prompt information that is used to instruct to rotate the mobile terminal includes providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0016]According to a second aspect, an apparatus for presenting a panoramic photo in a mobile terminal is provided, including a detecting unit, a determining unit, and a presenting unit, where the detecting unit is configured to detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode; and when the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, transmit a detection result to the determining unit, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the determining unit is configured to receive the detection result transmitted by the detecting unit, and if the detection result is that the trigger instruction is detected, detect and determine a rotation angle of the mobile terminal, and transmit the determined rotation angle of the mobile terminal to the presenting unit, and the presenting unit is configured to receive the rotation angle of the mobile terminal determined by the determining unit; and move and present, according to the determined rotation angle, a panoramic photo that is presented in a normal mode in the mobile terminal. [0017]With reference to the second aspect, in a first implementation manner, the determining unit is configured to determine the rotation angle of the mobile terminal in the following manner, determining a placement direction in which the mobile terminal is located in a rotation process, and determining the rotation angle of the mobile terminal according to the placement direction. [0018]With reference to the first implementation manner of the second aspect, in a second implementation manner, the determining unit is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0019]With reference to the second implementation manner of the second aspect, in a third implementation manner, the determining unit is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process, when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0020]With reference to the second implementation manner of the second aspect or the third implementation manner of the second aspect, in a fourth implementation manner, the determining unit is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0021]With reference to any one of the foregoing implementation manners of the second aspect, in a fifth implementation manner, the apparatus further includes a judging unit, where the judging unit determines, before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0022]With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner, the determining unit is further configured to before the presenting unit moves, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed; and the presenting unit is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0023]With reference to the second aspect, in a seventh implementation manner, the apparatus further includes a prompting unit, where the prompting unit is configured to receive the detection result transmitted by the detecting unit; and when the detection result is that the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected by the detecting unit, provide prompt information that is used to instruct to rotate the mobile terminal. [0024]With reference to the seventh implementation manner of the second aspect, in an eighth implementation manner, the apparatus further includes an acquiring unit, where the acquiring unit is configured to acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and transmit, to the prompting unit, the acquired rotation direction of the mobile terminal that is saved when the photo is photographed, and the prompting unit is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the rotation direction acquired by the acquiring unit. [0025]According to a third aspect, a mobile terminal is provided, including an input device, a sensor, a processor, and a display screen, where the display screen is configured to present a panoramic photo, the input device is configured to input a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode, where the immersive browsing mode is a browsing mode in which a panoramic photo moves as the mobile terminal rotates, the sensor is configured to detect a rotation angle of the mobile terminal, and the processor is configured to, when it is detected that the trigger instruction is input by the input device, move, according to the rotation angle determined by means of detection, a panoramic photo that is presented in a normal mode in the mobile terminal. [0026]With reference to the third aspect, in a first implementation manner, the sensor is configured to determine a placement direction in which the mobile terminal is located in a rotation process, and determine the rotation angle of the mobile terminal according to the placement direction. [0027]With reference to the first implementation manner of the third aspect, in a second implementation manner, the sensor is configured to determine, in the following manner, the placement direction in which the mobile terminal is located in the rotation process detecting an angle of a gravity direction of the mobile terminal with respective to a direction of an X-Y plane of a reference three-dimensional coordinate system, where the X-Y plane of the reference three-dimensional coordinate system is parallel to a plane in which a screen of the mobile terminal is located, and a Z-axis of the reference three-dimensional coordinate system is perpendicular to the plane in which the screen of the mobile terminal is located, and determining, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process. [0028]With reference to the second implementation manner of the third aspect, in a third implementation manner, the sensor is configured to determine, in the following manner, according to the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system, the placement direction in which the mobile terminal is located in the rotation process when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is not greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a vertical placement direction, and when the angle of the gravity direction of the mobile terminal with respective to the direction of the X-Y plane of the reference three-dimensional coordinate system is greater than 45 degrees, determining that the placement direction in which the mobile terminal is located in the rotation process is a horizontal placement direction. [0029]With reference to the second implementation manner of the third aspect or the third implementation manner of the third aspect, in a fourth implementation manner, the sensor is configured to determine, in the following manner, the rotation angle of the mobile terminal according to the placement direction, if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the horizontal placement direction, using a direction of the Z-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal, or if it is determined that the placement direction in which the mobile terminal is located in the rotation process is the vertical placement direction, using a direction of an X-axis or a direction of a Y-axis in the reference three-dimensional coordinate system as a corresponding axial direction of the mobile terminal in the rotation process, and using an angle by which the mobile terminal rotates with respective to the axial direction as the rotation angle of the mobile terminal. [0030]With reference to any one of the foregoing implementation manners of the third aspect, in a fifth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine that the rotation angle of the mobile terminal reaches a preset rotation angle threshold. [0031]With reference to the fifth implementation manner of the third aspect, in a sixth implementation manner, the processor is further configured to before moving, according to the determined rotation angle, the panoramic photo that is presented in the normal mode in the mobile terminal, determine a minimum displacement of the panoramic photo according to the preset rotation angle threshold, a rotation angle of the mobile terminal when the panoramic photo is photographed, and a photo width of the panoramic photo along a rotation direction of the mobile terminal when the panoramic photo is photographed, and the processor is configured to move, in the following manner, the panoramic photo that is presented in the normal mode in the mobile terminal moving the panoramic photo for the minimum displacement along a direction opposite to the rotation direction of the mobile terminal. [0032]With reference to the third aspect, in a seventh implementation manner, the processor is further configured to when it is detected that the trigger instruction is input by the input device, provide prompt information that is used to instruct to rotate the mobile terminal. [0033]With reference to the seventh implementation manner of the third aspect, in an eighth implementation manner, the processor is further configured to before providing the prompt information that is used to instruct to rotate the mobile terminal, acquire a rotation direction of the mobile terminal that is saved when the panoramic photo is photographed, and the processor is configured to provide, in the following manner, the prompt information that is used to instruct to rotate the mobile terminal providing the prompt information that is used to instruct to rotate the mobile terminal according to the acquired rotation direction. [0034]According to a method and an apparatus for presenting a panoramic photo in a mobile terminal, and a mobile terminal that are provided in the embodiments of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. BRIEF DESCRIPTION OF DRAWINGS [0035]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. [0036]FIG. 1 is a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0037]FIG. 2 is another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0038]FIG. 3 is a schematic diagram of a process of determining a rotation angle of a mobile terminal according to an embodiment of the present disclosure. [0039]FIG. 4 is a schematic diagram of implementation of determining a placement direction in which a mobile terminal is located in a rotation process according to an embodiment of the present disclosure. [0040]FIG. 5A and FIG. 5B are schematic diagrams of placement directions of a mobile terminal involved in an embodiment of the present disclosure. [0041]FIG. 6 is a schematic diagram of implementation of determining a rotation angle of a mobile terminal according to a placement direction according to an embodiment of the present disclosure. [0042]FIG. 7 is a schematic diagram of implementation of controlling, according to a determined rotation angle of a mobile terminal, a panoramic photo to move along a direction opposite to a rotation direction of the mobile terminal according to an embodiment of the present disclosure. [0043]FIG. 8 is a schematic diagram of implementation of a program for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0044]FIG. 9A is a schematic diagram of implementation of a process of photographing a panoramic photo according to an embodiment of the present disclosure. [0045]FIG. 9B is a schematic diagram of implementation of a process of browsing a panoramic photo according to an embodiment of the present disclosure. [0046]FIGS. 10A, 10B, 10C, and 10D are schematic structural diagrams of an apparatus for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. [0047]FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. DESCRIPTION OF EMBODIMENTS [0048]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0049]According to a method for presenting a panoramic photo in a mobile terminal provided in the embodiments of the present disclosure, a panoramic photo moves as the mobile terminal rotates. For ease of description in the embodiments of the present disclosure, a browsing mode in which a panoramic photo moves as the mobile terminal rotates is referred to as an “immersive browsing mode”, and a browsing mode of a panoramic photo in the prior art is referred to as a normal mode in the following, which is certainly not limited thereto; for example, the “immersive browsing mode” may also be referred to as “panorama browsing mode”. When browsing a panoramic photo that is displayed in a normal mode in the mobile terminal, a user may choose to enter the immersive browsing mode. In the immersive browsing mode, the panoramic photo may be browsed by rotating the mobile terminal, and it is not required to manually slide on a screen of the mobile terminal to browse the panoramic photo. [0050]FIG. 1 shows a flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 1, the method includes the following steps. [0051]S101: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0052]In this embodiment of the present disclosure, if the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, S102 is performed. [0053]S102: Detect and determine a rotation angle of the mobile terminal. [0054]S103: Move and present, according to the rotation angle determined in S102, a panoramic photo that is displayed in a normal mode in the mobile terminal. [0055]According to the method for presenting a panoramic photo in a mobile terminal provided in this embodiment of the present disclosure, when a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode is detected, a rotation angle of the mobile terminal is detected and determined; and a panoramic photo that is displayed in a normal mode in the mobile terminal is moved and presented according to the determined rotation angle. Using the present disclosure, a panoramic photo may be enabled to move as a mobile terminal rotates, so that browsing of the panoramic photo may be implemented without requiring manual sliding on a screen of the mobile terminal, which is easy and convenient in terms of operations. [0056]In this embodiment of the present disclosure, there may be multiple implementation manners for implementing a rotation process of the mobile terminal. For example, a user may rotate the mobile terminal in a predefined manner immediately after the user triggers the mobile terminal to enter the immersive browsing mode, where the predefined manner may be obtained, for example, by pre-learning from a user manual. For example, after the user triggers the mobile terminal to enter the immersive browsing mode, the mobile terminal may further provide prompt information that is used to instruct to rotate the mobile terminal, so as to prompt the user to perform rotation. [0057]An implementation manner in which a mobile terminal provides prompt information that is used to instruct to rotate the mobile terminal is used as an example in an embodiment of the present disclosure in the following to describe in detail the method for presenting a panoramic photo in a mobile terminal involved in the foregoing embodiment. [0058]FIG. 2 shows another flowchart of implementation of a method for presenting a panoramic photo in a mobile terminal according to an embodiment of the present disclosure. The method may be performed by a mobile terminal, or by components in the mobile terminal. As shown in FIG. 2, the method includes the following steps. [0059]S201: Detect a trigger instruction that is used to instruct the mobile terminal to enter an immersive browsing mode. [0060]In this embodiment of the present disclosure, a user may input, using a display screen or a key of the mobile terminal, the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode. For example, in this embodiment of the present disclosure, an enabling control used to enable the immersive browsing mode may be set on a display interface of the mobile terminal. An enabling status of the enabling control is used to determine whether to enable the immersive browsing mode, and when it is detected that the enabling control is enabled, it can be determined that the mobile terminal needs to enter the immersive browsing mode. For example, an immersive browsing button is set on the display interface of the mobile terminal. When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; and if the mobile terminal receives the trigger instruction, it may be considered that the user needs to browse the panoramic photo in the immersive browsing mode. [0061]Optionally, in this embodiment of the present disclosure, the user may be further prompted, when it is detected that the user is browsing a panoramic photo, to trigger the enabling control that is used to instruct to enable the immersive browsing mode. [0062]S202: When the trigger instruction that is used to instruct the mobile terminal to enter the immersive browsing mode is detected, provide prompt information that is used to instruct to rotate the mobile terminal. [0063]In this embodiment of the present disclosure, i(String), 相关申请的交叉引用 [0001] 该申请是美国专利申请序列号的延续。 2019 年 2 月 4 日提交的第 16/266,498 号美国专利申请的延续。 2017 年 4 月 10 日提交的第 15/483,724 号,现为美国专利。 第 10,222,877 号,是美国专利申请序列号的延续。 2015 年 6 月 10 日提交的第 14/735,625 号,现为美国专利。 美国专利第 9,621,802 号,是 2014 年 6 月 16 日提交的国际专利申请号 PCT/CN2014/079950 的继续申请。所有上述申请的全部内容通过引用并入本文。 技术领域 [0002] 本 发明涉及通信技术领域,尤其涉及一种移动终端中全景照片的呈现方法、装置及移动终端。 背景 [0003] 随着通信技术的飞速发展,移动终端的功能越来越强大,移动终端的使用范围和环境也越来越多样化。 例如,目前很多移动终端,如手机、个人数字助理、个人电脑等都具有全景拍摄的功能。 [0004] 当移动终端进行全景拍摄时,用户旋转移动终端拍摄需要拍摄的场景。 “全景拍摄”的一个基本原理是搜索两张照片的边缘部分,对成像效果最接近的区域进行配准,从而完成照片的自动拼接。 然后可以将多张拍摄的照片按照上述的拼接原理拼接成一张全景照片,全景照片中记录的场景视野较为开阔。 用户在浏览照片时,会在全景照片上浏览到比较丰富的图像内容,具有比较强的视觉冲击力。 [0005] 然而,虽然目前全景照片可以记录比较丰富的照片内容,但是全景照片在移动终端中呈现时,照片比较大。 在浏览全景照片时,用户需要手动滑动照片来浏览照片内容,操作较为复杂。 概括 [0006] 本发明实施例提供一种全景照片在移动终端中的呈现方法、装置及移动终端,以降低全景照片浏览的复杂度,方便用户浏览全景照片。 [0007] 第一方面,提供了一种全景照片在移动终端中的呈现方法,包括:检测用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为浏览模式。 其中全景照片随着移动终端的旋转而移动,若检测到触发指令,则检测并确定移动终端的旋转角度,根据确定的旋转角度移动呈现正常显示的全景照片 移动端模式。 [0008] 结合第一方面,在第一种实现方式中,所述确定移动终端的旋转角度包括:确定移动终端在旋转过程中所处的放置方向,根据所述确定移动终端的旋转角度。 放置方向。 [0009]结合第一方面的第一种实现方式,在第二种实现方式中,所述确定移动终端在旋转过程中所处的放置方向包括检测移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考的Z轴 三维坐标系垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于参考三维X-Y平面方向的夹角确定- 维度坐标系,移动终端在旋转过程中所处的放置方向。 [0010] 结合第一方面的第二种实现方式,在第三种实现方式中,所述根据移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角确定 ,移动终端在旋转过程中所处的放置方向包括当移动终端的重力方向相对于参考三维坐标系的X-Y平面方向的夹角不大于45度时 ,确定移动终端在旋转过程中所处的放置方向为竖直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0011] 结合第一方面的第二种实现方式或第一方面的第三种实现方式,在第四种实现方式中,所述根据放置方向确定移动终端的旋转角度包括: 其中,旋转过程中移动终端所处的位置为水平放置方向,以参考三维坐标系中的Z轴方向作为旋转过程中移动终端对应的轴向。 将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者判断旋转过程中移动终端所处的放置方向为竖直放置方向 ,将参考三维坐标系中的X轴方向或Y轴方向作为移动终端在旋转过程中对应的轴向,并使用移动终端旋转的角度 分别以轴向为移动终端的旋转角度。 [0012] 结合第一方面的上述任一种实现方式,在第五种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还 包括确定移动终端的旋转角度达到预设的旋转角度阈值。 [0013]结合第一方面的第五种实现方式,在第六种实现方式中,在根据确定的旋转角度移动移动终端中以正常模式呈现的全景照片之前,该方法还包括确定: 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 ,移动终端中以正常模式呈现的全景照片移动包括将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0014] 结合第一方面,在第七种实现方式中,所述检测确定移动终端的旋转角度之前,还包括提供用于指示旋转移动终端的提示信息。 [0015] 结合第一方面的第七种实现方式,在第八种实现方式中,所述提供用于指示旋转移动终端的提示信息之前,所述方法还包括: 获取旋转时保存的移动终端的旋转方向。 拍摄全景照片,提供用于指示旋转移动终端的提示信息包括:根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0016] 第二方面,提供了一种全景照片在移动终端中的呈现装置,包括检测单元、确定单元和呈现单元,所述检测单元用于检测触发指令,所述触发指令用于指示 移动终端进入沉浸式浏览模式; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元,所述沉浸式浏览模式为全景照片随着移动终端移动的浏览模式。 旋转,所述判断单元,用于接收检测单元发送的检测结果,若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的旋转角度发送给移动终端。 移动终端发送给呈现单元,呈现单元用于接收确定单元确定的移动终端的旋转角度; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0017] 结合第二方面,在第一种实现方式中,所述确定单元用于通过以下方式确定所述移动终端的旋转角度,确定所述移动终端在旋转过程中所处的放置方向,并确定 移动终端根据放置方向的旋转角度。 [0018] 结合第二方面的第一种实现方式,在第二种实现方式中,所述确定单元具体用于通过如下方式确定移动终端在旋转过程中检测角度的放置方向。 移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 定位,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端重力方向相对于 参考三​​维坐标系的X-Y平面方向,移动终端在rota中的放置方向 化过程。 [0019]结合第二方面的第二种实现方式,在第三种实现方式中,所述确定单元,用于根据所述移动终端的重力方向相对于所述移动终端的方向的夹角,通过如下方式确定: 参考三​​维坐标系的X-Y平面,移动终端在旋转过程中所处的放置方向,当移动终端的重力方向相对于参考三维的X-Y平面方向的夹角 -维坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于该方向的夹角 参考三​​维坐标系的X-Y平面的夹角大于45度,确定th e 旋转过程中移动终端所处的放置方向为水平放置方向。 [0020] 结合第二方面的第二种实现方式或第二方面的第三种实现方式,在第四种实现方式中,所述确定单元,用于通过以下方式,根据所述移动终端的旋转角度确定所述移动终端的旋转角度。 放置方向若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 rotation process为垂直放置方向,在refe中使用X轴方向或Y轴方向 以三维坐标系作为移动终端在旋转过程中对应的轴向,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0021] 结合第二方面的上述任一种实现方式,在第五种实现方式中,所述装置还包括判断单元,所述判断单元根据所述确定的旋转角度,在所述呈现单元移动前,确定所述全景图 在移动终端中以正常模式呈现的照片,移动终端的旋转角度达到预设的旋转角度阈值。 [0022] 结合第二方面的第五种实现方式,在第六种实现方式中,所述确定单元还用于在所述呈现单元根据确定的旋转角度移动之前,以正常模式呈现的全景照片处于 移动终端,根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度,确定全景照片的最小位移。 拍摄全景照片; 呈现单元,用于将移动终端中正常模式呈现的全景照片按如下方式移动,使全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0023] 结合第二方面,在第七种实现方式中,所述装置还包括提示单元,所述提示单元用于接收所述检测单元发送的检测结果; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示旋转移动终端的提示信息。 [0024]结合第二方面的第七种实现方式,在第八种实现方式中,所述装置还包括获取单元,所述获取单元用于获取拍摄所述全景照片时保存的所述移动终端的旋转方向 , 向提示单元发送获取的拍摄照片时保存的移动终端的旋转方向, 提示单元用于通过以下方式提供用于指示旋转的提示信息 移动终端根据获取单元获取的旋转方向,提供用于指示旋转移动终端的提示信息。 [0025] 第三方面,提供了一种移动终端,包括输入设备、传感器、处理器和显示屏,所述显示屏用于呈现全景照片,所述输入设备用于输入触发指令 用于指示移动终端进入沉浸式浏览模式,沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,传感器用于检测移动终端的旋转角度, 处理器,用于在检测到输入设备输入触发指令时,根据检测确定的旋转角度移动移动终端中以正常模式呈现的全景照片。 [0026] 结合第三方面,在第一种实施方式中,所述传感器用于确定所述移动终端在旋转过程中所处的放置方向,并根据所述放置方向确定所述移动终端的旋转角度。 [0027] 结合第三方面的第一种实现方式,在第二种实现方式中,所述传感器用于在检测重力角度的旋转过程中,通过如下方式确定所述移动终端所处的放置方向 移动终端的方向相对于参考三维坐标系的X-Y平面的方向,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面 ,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面,根据移动终端的重力方向与相对方向的夹角确定 参考三​​维坐标系的X-Y平面,旋转过程中移动终端所在的放置方向 秒。 [0028] 结合第三方面的第二种实现方式,在第三种实现方式中,所述传感器用于根据所述移动终端的重力方向相对于X-Y方向的夹角,通过如下方式进行判断 参考三​​维坐标系的平面,移动终端的重力方向相对于参考三维的X-Y平面方向的夹角时移动终端在旋转过程中所处的放置方向 坐标系不大于45度,确定移动终端在旋转过程中所处的放置方向为竖直放置方向,当移动终端的重力方向相对于 参考三​​维坐标系的X-Y平面大于45度,确定放置 旋转过程中移动终端所处的方向为水平放置方向。 [0029]结合第三方面的第二种实现方式或第三方面的第三种实现方式,在第四种实现方式中,所述传感器,用于通过如下方式确定所述移动终端根据放置的旋转角度 方向,若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则以参考三维坐标系中的Z轴方向作为对应的轴方向 移动终端在旋转过程中,将移动终端相对于轴向旋转的角度作为移动终端的旋转角度,或者如果确定移动终端所处的放置方向在 旋转过程为垂直放置方向,参考三中X轴方向或Y轴方向 移动终端在旋转过程中对应的轴向为维坐标系,移动终端相对于轴向旋转的角度作为移动终端的旋转角度。 [0030] 结合第三方面的上述任一种实现方式,在第五种实现方式中,所述处理器还用于在移动之前,根据确定的旋转角度,移动所述移动设备中以正常模式呈现的全景照片。 终端,确定移动终端的旋转角度达到预设的旋转角度阈值。 [0031] 结合第三方面的第五种实现方式,在第六种实现方式中,所述处理器还用于,在移动终端中以正常模式呈现的全景照片根据确定的旋转角度移动之前,确定 全景照片根据预设旋转角度阈值的最小位移、拍摄全景照片时移动终端的旋转角度、拍摄全景照片时全景照片沿移动终端旋转方向的照片宽度 拍摄后,处理器用于移动终端中正常模式下呈现的全景照片,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0032] 结合第三方面,在第七种实现方式中,处理器还用于在检测到输入设备输入触发指令时,提供用于指示旋转移动终端的提示信息。 [0033] 结合第三方面的第七种实现方式,在第八种实现方式中,所述处理器还用于在提供所述用于指示所述移动终端旋转的提示信息之前,获取所述移动终端的旋转方向,即 拍摄全景照片时保存, 处理器用于按照以下方式提供用于指示旋转移动终端的提示信息, 提供用于指示旋转移动终端的提示信息 获取的旋转方向。 [0034] 本发明实施例提供的一种移动终端全景照片呈现方法、装置及移动终端,当用于指示移动终端进入沉浸式浏览模式的触发指令时 检测到,检测并确定移动终端的旋转角度; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . 附图说明 [0035]为更加清楚地描述本发明实施例的技术方案,下面对实施例描述所需的附图进行简单介绍。 [0036] 图1为本发明实施例提供的全景照片在移动终端中的呈现方法的实现流程图。 [0037] 图2为本发明实施例提供的全景照片在移动终端中的呈现方法的另一种实现流程图。 [0038] 图3是根据本发明实施例的确定移动终端的旋转角度的过程的示意图。 [0039] 图4为本发明实施例在旋转过程中确定移动终端所处放置方向的实现示意图。 [0040] 图5A和图5B为本发明实施例涉及的移动终端的放置方向示意图。 [0041] 图6为本发明实施例根据放置方向确定移动终端旋转角度的实现示意图。 [0042] 图7为本发明实施例根据确定的移动终端旋转角度控制全景照片沿与移动终端旋转方向相反的方向移动的实现示意图。 [0043] 图8是根据本发明实施例的全景照片展示程序在移动终端中的实现示意图。 [0044] 图9A为本发明实施例全景照片拍摄过程的实现示意图。 [0045] 图9B为本发明实施例的全景照片浏览过程的实现示意图。 [0046] 图10A、10B、10C和10D是根据本发明实施例的移动终端中全景照片呈现装置的结构示意图。 [0047] 图11为本发明实施例提供的移动终端的结构示意图。 具体实施方式 [0048] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0049] 本发明实施例提供的移动终端中全景照片的呈现方法,全景照片随着移动终端的旋转而移动。 本发明实施例中为了描述方便,将全景照片随着移动终端旋转而移动的浏览模式称为“沉浸式浏览模式”,现有技术中的全景照片浏览模式为“沉浸式浏览模式”。 以下简称正常模式,当然不限于此; 例如,“沉浸式浏览模式”也可以称为“全景浏览模式”。 用户在移动终端浏览以普通模式显示的全景照片时,可以选择进入沉浸式浏览模式。 在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在移动终端的屏幕上滑动来浏览全景照片。 [0050] 图1示出了根据本发明实施例的全景照片在移动终端中的呈现方法的实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图1所示,该方法包括以下步骤。 [0051] 小号 101:检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0052] 本发明实施例中,若检测到用于指示移动终端进入沉浸式浏览模式的触发指令,S 102 被执行。 [0053] 小号 102 :检测并确定移动终端的旋转角度。 [0054] 小号 103 :移动呈现,根据S中确定的旋转角度 102 ,移动终端正常显示的全景照片。 [0055] 本发明实施例提供的移动终端中全景照片的呈现方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,移动终端的旋转角度 被检测和确定; 移动终端中正常显示的全景照片根据确定的旋转角度移动呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而实现全景照片的浏览,无需在移动终端的屏幕上手动滑动,操作简单方便。 . [0056] 在本发明实施例中,实现移动终端的旋转过程可以有多种实现方式。 例如,用户可以在用户触发移动终端进入沉浸式浏览模式后立即以预定方式旋转移动终端,该预定方式可以例如通过用户手册预先学习得到。 例如,在用户触发移动终端进入沉浸式浏览模式后,移动终端还可以提供用于指示旋转移动终端的提示信息,以提示用户进行旋转。 [0057] 下面以本发明实施例中移动终端提供用于指示旋转移动终端的提示信息的实现方式为例,对全景照片在移动终端中的呈现方法进行详细说明。 上述实施例涉及的终端。 [0058] 图2示出了根据本发明实施例的全景照片在移动终端中的呈现方法的另一种实现流程图。 该方法可以由移动终端执行,也可以由移动终端中的组件执行。 如图2所示,该方法包括以下步骤。 [0059] 小号 201 :检测用于指示移动终端进入沉浸式浏览模式的触发指令。 [0060] 在本发明实施例中,用户可以通过移动终端的显示屏或按键输入用于指示移动终端进入沉浸式浏览模式的触发指令。 例如,本发明实施例可以在移动终端的显示界面上设置用于开启沉浸式浏览模式的开启控件。 启用控件的启用状态用于确定是否启用沉浸式浏览模式,当检测到启用控件被启用时,可以确定移动终端需要进入沉浸式浏览模式。 例如,在移动终端的显示界面设置沉浸式浏览按钮。 When choosing to enter the immersive browsing mode to browse a panoramic photo, the user can trigger the button, to instruct the mobile terminal to enter the immersive browsing mode; 如果移动终端接收到触发指令,则可以认为用户需要在沉浸式浏览模式下浏览全景照片。 [0061] 可选地,本发明实施例还可以在检测到用户正在浏览全景照片时,提示用户触发用于指示开启沉浸式浏览模式的开启控件。 [0062] 小号 202:当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提供用于指示移动终端旋转的提示信息。 [0063] 在本发明实施例中,为了实现沉浸式浏览,用户需要旋转移动终端,使得全景照片随着移动终端的旋转而移动。 通常,为了更好的浏览全景照片,可以提供用于指示旋转移动终端的提示信息,以告知用户移动终端需要按照预设方向进行旋转,该预设方向可以为 例如,从左向右旋转,当然,也可以从右向左旋转。 [0064] 在本发明实施例中,提供的提示信息可以是在显示界面上显示的文字信息,当然,也可以是通过语音输出的方式通知的语音信息,本发明实施例对此不做限定。 [0065] 可选的,本发明实施例还可以获取拍摄全景照片时保存的移动终端的旋转方向,并以提示信息的形式通知获取的旋转方向。 提供用于指示根据通知的旋转方向旋转移动终端的提示信息,提示用户根据获取的拍摄全景照片时保存的移动终端的旋转方向旋转移动终端。 [0066] 小号 203 :检测并确定移动终端的旋转角度。 [0067] 本发明实施例通过实时检测移动终端的旋转角度,从而及时控制全景照片移动。 [0068] 用户在拍摄全景照片时,一般会将移动终端定位在确定的放置方向上。 但是,用户在浏览全景照片时,很可能会使用与拍摄全景照片时确定的放置方向不同的放置方向来浏览全景照片。 因此,在本发明实施例中,为了更加准确地浏览全景照片,在旋转过程中,可以根据移动终端所处的放置方向来确定移动终端的旋转角度。 [0069] S中移动终端旋转角度的确定过程 203 本发明实施例可以采用如下方式进行判断,如图3所示。 [0070] 小号 2031 :确定移动终端在旋转过程中所处的放置方向。 [0071] 小号 2032 :根据S中确定的放置方向确定移动终端的旋转角度 2031 . [0072] 本发明实施例中,可以利用设置在移动终端中的重力传感器指示的移动终端的重力方向,确定移动终端所在的放置方向,确定移动终端的旋转角度。 使用设置在移动终端中的陀螺仪传感器的角度。 可选地,在本发明实施例中,用于确定移动终端的放置方向的重力传感器和用于确定移动终端的旋转角度的陀螺仪传感器可以在用于指示移动终端的触发指令时被启用。 检测到移动终端进入沉浸式浏览模式。 [0073] 可选地,在S中的旋转过程中确定移动终端所处的放置方向 2031 本发明实施例可以采用图4所示的方法进行判断。 如图4所示,该方法包括以下步骤。 [0074] 小号 2031 a :以移动终端屏幕所在平面为基准,建立参考三维坐标系。 [0075]本发明实施例中,参考三维坐标系可以基于移动终端屏幕所在的平面建立,参考三维坐标系的X-Y平面平行于该平面 移动终端屏幕所在平面,参考三维坐标系的Z轴垂直于移动终端屏幕所在平面。 [0076] 移动终端在旋转过程中位于不同的放置方向,相应的参考三维坐标系也根据移动终端的不同放置方向进行旋转。 例如,参考三维坐标系的示意图分别对应图5A中的垂直放置方向和图5B中的水平放置方向。 [0077] 小号 2031 b :检测移动终端的重力方向相对于S中建立的参考三维坐标系的X-Y平面方向的夹角 2031 a. [0078] 小号 2031 c :根据角度确定移动终端在旋转过程中所处的放置方向,通过在S中检测得到 2031 b ,移动终端的重力方向相对于参考三维坐标系的X-Y平面的方向。 [0079] 可选地,在本发明实施例中,为了简化控制全景照片呈现的控制过程,当移动终端的重力方向相对于基准三的X-Y平面方向的夹角- 维度坐标系不大于45度,则可以确定移动终端在旋转过程中所处的放置方向为竖直放置方向。 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,可以确定移动终端所处的放置方向 旋转过程中为水平放置方向。 [0080] 需要说明的是,在本发明实施例中,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角等于45度时,可以是 确定移动终端所在的放置方向为竖直放置方向,或者为水平放置方向,本发明实施例可以设置为竖直放置方向。 [0081] 本发明实施例中,如果利用移动终端的重力方向相对于基准三的X-Y平面方向的夹角来确定移动终端在旋转过程中所处的放置方向—— S 中的维度坐标系 2031 ,在S中确定移动终端的旋转角度时,可以采用图6所示的确定方式 2032 . [0082] 小号 2032 a :确定移动终端在旋转过程中对应的轴向。 [0083] 本发明实施例在确定移动终端在旋转过程中所处的放置方向为水平放置方向时,采用参考三维坐标系中Z轴的方向 作为移动终端在旋转过程中对应的轴向; 或者,当确定移动终端在旋转过程中所处的放置方向为垂直放置方向时,参考三维坐标系中的X轴方向或Y轴方向为 用作移动终端在旋转过程中对应的轴向。 [0084]需要说明的是,本发明实施例中,上述移动终端在旋转过程中对应的轴向只是为了简化确定移动终端旋转角度的过程,具体的确定方式不作限定。 至此。 [0085] 小号 2032 b :使用移动终端相对于S中确定的轴向旋转的角度 2032 a 作为移动终端的旋转角度。 [0086] 本发明实施例中,可以在检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,启用用于确定移动终端旋转角度的陀螺仪传感器。 检测设置在移动终端上的陀螺传感器相对于轴向旋转的角度,根据陀螺传感器旋转的角度确定移动终端相对于对应轴向的旋转角度。 [0087] 小号 204 :根据确定的移动终端旋转角度移动移动终端正常显示的全景照片。 [0088] 在本发明实施例中,在浏览全景照片时,一般先以普通浏览方式显示全景照片; 例如,可以是分辨率较低的全景照片,或者只有全景照片的最左部分或全景照片的最右部分等部分全景照片显示在手机的显示屏中 终端。 本发明实施例在确定移动终端的旋转角度后,可以移动终端中正常模式显示的全景照片,实现全景照片的沉浸式浏览。 [0089] 可选地,在本发明实施例中,可以采用多种实施方式对移动终端中正常模式显示的全景照片进行移动。 例如,移动终端在正常模式下显示的全景照片可以沿与移动终端的旋转方向相同的方向移动,也可以沿与旋转方向相反的方向移动。 的移动终端。 在本发明实施例中,为了实现更好的显示效果,优选地,移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0090] 可选的,本发明实施例中,为了实现全景照片的平滑移动,可以预先设置旋转角度阈值,在S之前 204 执行后,确定移动终端的旋转角度达到预设的旋转角度阈值。 在沉浸式浏览模式下浏览全景照片时,实时检测移动端的旋转角度; 当移动终端的旋转角度达到预设的旋转角度阈值时,控制全景照片移动,实现了全景照片的平滑移动。 如果没有达到预设的旋转角度阈值,全景照片可能不会被移动。 [0091] 本发明实施例中,根据确定的移动终端的旋转角度,将移动终端中正常模式下显示的全景照片沿与移动终端旋转方向相反的方向在S中移动。 204 可以采用图7所示的实现方式(当全景照片沿与移动终端的旋转方向相同的方向移动时,也可以采用类似的方式)。 [0092] 小号 2041 :判断移动终端的旋转角度是否达到预设的旋转角度阈值; 如果移动终端的旋转角度达到预设的旋转角度阈值,则执行S 2042 ; 否则,执行 S 202 检测移动终端的旋转角度。 [0093] 小号 2042:当旋转角度达到预设的旋转角度阈值时,将移动终端中正常模式显示的全景照片沿与移动终端旋转方向相反的方向移动。 [0094] 可选地,本发明实施例中,为了进一步增强平滑移动的效果,还可以确定最小位移,当控制全景图像沿与移动终端的旋转方向相反的方向移动时, 照片每次移动确定的最小位移。 最小位移的单位是像素。 [0095] 本发明实施例中,可以根据预设的旋转角度阈值、拍摄全景照片时移动终端的旋转角度以及全景照片沿a的照片宽度,确定全景照片的最小位移量。 拍摄全景照片时移动终端的旋转方向。 拍摄全景照片时移动终端的旋转角度和拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度一般在拍摄全景照片时记录并保存,可以是 直接从本发明实施例拍摄全景照片时保存的全景照片的相关属性中获取。 需要说明的是,在本发明实施例中,全景照片的照片宽度的单位也是像素。 [0096] 可选地,在本发明实施例中,确定全景照片的最小位移可以采用如下方式。 全景照片的最小位移根据公式确定 [0097] s = d ⁢ φ 1 φ2 , 其中s是全景照片的最小位移; d为全景照片的照片宽度; φ 1 为预设旋转角度阈值; φ2为拍摄全景照片时移动终端的旋转角度。 [0098] 本发明实施例中,对于浏览的全景照片,在确定全景照片时,全景照片的照片宽度d和拍摄全景照片时移动终端的旋转角度φ2为固定值(如果 在拍摄全景照片的过程中记录了旋转角度φ2,使用记录的值;如果在拍摄过程中没有记录旋转角度φ2,则可以参考一些参考值,例如180度或360度作为旋转角度。 角度); 因此,在本发明实施例中,为了实现全景照片的平滑移动,适当的旋转角度阈值φ 1 可能是预设的。 若预设旋转角度阈值φ 1 固定后,确定全景照片在旋转过程中移动的最小位移量。 在浏览全景照片的过程中,实时检测并确定移动终端的旋转角度,如果确定移动终端的旋转角度达到预设的旋转角度阈值CI,则移动全景照片 为与移动终端旋转方向相反方向的最小位移。 [0099] 本发明实施例中,移动终端的旋转角度可以为移动终端当前位置对应的角度与全景照片移动时移动终端位置对应的角度的角度差。 上一次(如果是第一次确定移动终端的旋转角度,可以认为上一次移动全景照片时移动终端对应的角度为0)。 在本发明实施例中,判断移动终端的旋转角度是否达到预设的旋转角度阈值的过程可以理解为持续执行并重置的过程,即每次移动终端的旋转角度达到 预设旋转角度阈值φ 1,可以将移动终端的初始旋转角度设置为0,检测并确定旋转角度,根据确定的旋转角度是否达到预设的旋转角度阈值来移动全景照片。 例如,移动终端的初始旋转角度设置为0,在移动终端从0度旋转到φ的过程中 1 −1度,全景照片不动; 当移动端旋转到φ 1 度,全景照片移动最小位移,重新设置旋转角度,继续检测移动端的旋转角度; 当移动端旋转到φ 1 度,全景照片再次移动最小位移,如此循环直到移动终端停止转动。 [0100] 进一步地,在本发明实施例中,移动全景照片的过程可以是立即执行的过程,即一旦确定移动终端的旋转角度达到预设的旋转角度阈值,则移动全景照片。 ; 例如,预设的旋转角度阈值φ 1 为5度,当旋转角度达到5度时,全景照片移动到最小位移。 移动全景照片的过程也可以是延时执行的过程,即在确定移动终端的旋转角度达到预设旋转角度后,在一段时间内将全景照片移动最小位移量 临界点。 [0101] 移动终端的旋转角度还可以为移动终端当前位置对应的角度与移动终端初始位置对应的角度的差值,即移动终端的旋转角度可以为a 随着用户移动移动终端不断积累价值。 此时,可以设置全景照片移动的位移与旋转角度成正比关系。 即,移动终端旋转角度越大,全景照片移动的位移越大,移动终端旋转角度越小,全景照片移动的位移越小。 [0102] 上述移动全景照片的方式和最小位移的确定方式还可以有其他实施方式,本发明不对其具体实施方式进行限定。 [0103] 小号 205 :以沉浸式浏览方式呈现全景照片。 [0104] 本发明实施例在沉浸式浏览模式下实现全景照片浏览时,不是通过手指滑动全景照片来实现全景照片的移动,而是通过旋转移动终端来实现全景照片的移动。 另一种全景照片的呈现方式可以采用现有的实施方案,例如,在呈现全景照片时,在将全景照片适配显示屏尺寸的过程中可以采用现有的实施方式。 [0105]本发明实施例提供的控制全景照片呈现的方法,当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,提示用户旋转移动终端 根据设定的方向,确定移动终端在旋转过程中所处的放置方向,进一步根据放置方向确定移动终端在相应方向上的旋转角度。 根据预设的旋转角度阈值确定全景照片移动的最小位移,将全景照片沿与移动终端的旋转方向相反的方向移动最小位移并呈现。 利用本发明,可以使全景照片随着移动终端的转动而移动,从而进一步实现全景照片的浏览,而不需要手动在移动终端的屏幕上滑动来浏览全景照片,简单易行。 操作方便。 [0106] 在本发明实施例中,在移动终端中呈现全景照片的实现过程可以采用图8所示的程序的实现过程,当然不限于此。 [0107] 本发明实施例提供的控制全景照片在移动终端中呈现的方法的实现基于拍摄全景照片时保存的照片参数,该照片参数例如为: 拍摄全景照片时移动终端旋转,移动终端的旋转方向,拍摄的全景照片的照片宽度。 因此,为了实现本发明实施例提供的移动终端中全景照片的呈现方法,在拍摄全景照片时,该方法也可以区别于现有的全景照片拍摄。 本发明以下实施例结合实际案例,举例说明全景照片的拍摄过程和浏览过程。 [0108] 图9A示出了根据本发明实施例的全景照片拍摄过程的实现示意图。 如图9A所示,实施过程包括以下步骤。 [0109] 小号 301 :启用全景拍摄模式。 [0110] 小号 302 :启动设置在移动终端上的陀螺仪传感器。 [0111] 小号 303 :用户通过旋转移动终端进行全景拍摄。 [0112] 小号 304 :确定全景拍摄时移动终端旋转的角度。 [0113] 本发明实施例中,可以通过陀螺仪传感器在S中启动的角度来确定移动终端的旋转角度。 302 旋转。 [0114] 小号 305 :保存拍摄的全景照片的属性信息。 [0115] 本发明实施例中,保存的全景照片的属性信息至少包括照片类型、拍摄角度和照片尺寸,其中,照片类型表示当前照片为全景照片,拍摄角度表示 拍摄全景照片时移动终端旋转的角度,照片尺寸表示全景照片的照片宽度。 [0116] 可选地,本发明实施例中,保存的全景照片的属性信息还可以包括拍摄全景照片时移动终端的旋转方向,该旋转方向例如可以为从右向左, 当然,也可能是从左到右。 [0117] 图9B示出了根据本发明实施例的全景照片浏览过程的实现示意图。 如图9B所示,实施过程包括以下步骤。 [0118] 小号 401 :检测用户浏览的照片类型。 [0119] 小号 402 :当检测到用户浏览的照片类型为全景照片时,向用户发送提示信息,该提示信息用于提示用户是否选择进入沉浸式浏览模式。 如果用户选择进入沉浸式浏览模式,执行S 403 ; 否则,以正常的照片浏览方式浏览照片。 [0120] 小号 403 :当检测到用户触发了用于指示移动终端进入沉浸式浏览模式的触发指令时,启动设置在移动终端上的重力传感器和陀螺仪传感器。 [0121] 小号 404 :用户通过旋转移动端浏览全景照片。 [0122] 小号 405 :根据重力传感器指示的重力方向确定移动终端所在的放置方向,确定的放置方向可以是水平放置方向,也可以是垂直放置方向。 具体的确定过程可以参见前述实施例的相关描述。 [0123] 小号 406 :根据S中确定的放置方向,确定移动终端在相应轴向的旋转角度 405 以及陀螺仪传感器在放置方向对应的轴向上的角度值,即当移动终端的放置方向为水平放置方向时,确定移动终端在Z方向上旋转的角度 -轴,当移动终端的放置方向为竖直放置方向时,确定移动终端在X轴或Y轴方向上旋转的角度。 [0124] 小号 407 :判断旋转角度是否在S中确定 406 达到预设的旋转角度阈值; 如果是,执行 S 408 ; 否则,执行 S 409 . [0125] 小号 408 :控制全景照片沿与移动终端的旋转方向相反的方向移动至少确定的最小位移量。 [0126] 小号 409 :检测移动终端的放置方向和旋转角度; 当移动端的放置方向改变时,执行S 405 ,当旋转角度发生变化时,执行S 407 . [0127] 本发明实施例在浏览全景照片时,实时检测移动终端的放置方向和旋转角度的变化,从而及时调整全景照片的移动。 [0128] 本发明实施例提供的移动终端中全景照片的呈现方法,在沉浸式浏览模式下,全景照片随着移动终端的转动而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0129] 基于上述实施例提供的移动终端中全景照片的呈现方法,本发明实施例还提供了一种装置 900 用于在移动终端呈现全景照片。 如图 10A 所示,该装置 900 包括一个检测单元 901 , 决定单位 902 , 和一个呈现单元 903 . [0130] 检测单元 901 用于检测用于指示移动终端进入沉浸式浏览模式的触发指令; 当检测到用于指示移动终端进入沉浸式浏览模式的触发指令时,将检测结果发送给判断单元 902 ,其中沉浸式浏览模式是全景照片随着移动终端的旋转而移动的浏览模式。 [0131] 决定单位 902用于接收检测单元发送的检测结果 901 ; 若检测结果为检测到触发指令,则检测并确定移动终端的旋转角度,并将确定的移动终端的旋转角度发送给呈现单元 903 . [0132] 呈现单位 903 用于接收确定单元确定的移动终端的旋转角度 902 ; 根据确定的旋转角度移动呈现移动终端中正常模式呈现的全景照片。 [0133] 在第一种实施方式中,所述确定单元 902 具体用于通过以下方式确定移动终端的旋转角度,确定移动终端在旋转过程中所处的放置方向,根据放置方向确定移动终端的旋转角度。 [0134] 在第二种实施方式中,所述确定单元 902 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0135] 在第三种实施方式中,确定单元 902 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 位于旋转过程中的是垂直放置方向; 当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定旋转中移动终端所在的放置方向 process是水平放置方向。 [0136] 在第四种实施方式中,所述确定单元 902 用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0137] 在第五种实施方式中,所述装置还包括判断单元 904 , 如图 10B 所示, 在呈现单元之前 903判断单元根据确定的旋转角度移动移动终端中正常模式呈现的全景照片 904 确定移动终端的旋转角度达到预设的旋转角度阈值。 [0138] 在第六种实施方式中,所述确定单元 902 还配置在呈现单元之前 903 移动,根据确定的旋转角度移动终端中正常模式下呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移,全景时移动终端的旋转角度 拍摄全景照片时,全景照片沿移动终端旋转方向的照片宽度,以及呈现单元 903 用于将移动终端中正常模式下呈现的全景照片按照如下方式移动,将全景照片沿与移动终端的旋转方向相反的方向移动上述确定的最小位移量。 [0139] 在第七种实施方式中,所述装置还包括提示单元 905 . 如图10C所示,其中提示单元 905 用于接收检测单元发送的检测结果 901 ; 当检测结果为检测单元检测到用于指示移动终端进入沉浸式浏览模式的触发指令时 901 ,提供用于指示旋转移动终端的提示信息。 [0140] 在第八种实施方式中,所述装置还包括获取单元 906 ,如图10D所示,其中获取单元 906 用于获取拍摄全景照片时保存的移动终端的旋转方向,并发送给提示单元 905 ,获取拍照时保存的移动终端的旋转方向,以及提示单元 905 用于通过以下方式提供用于指示旋转移动终端的提示信息: 根据获取单元获取的旋转方向提供用于指示旋转移动终端的提示信息 906 . [0141] 需要说明的是,对于本发明实施例图10A至图10D提供的全景照片在移动终端中的呈现装置,如果不描述在移动终端中实现全景照片的呈现过程 不够详细,可以参见方法实施例的相关描述,在此不再赘述。 [0142] 本发明实施例提供的移动终端中全景照片的呈现装置,在沉浸式浏览模式下,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0143] 基于上述实施例提供的全景照片在移动终端中的呈现方法及装置,本发明实施例还提供了一种移动终端 1000 . 如图11所示,移动端 1000 包括一个输入设备 1001 , 一个传感器 1002 , 处理器 1003 , 和一个显示屏 1004 ,其中输入设备 1001 用于输入用于指示移动终端进入沉浸式浏览模式的触发指令,所述沉浸式浏览模式为全景照片随着移动终端的旋转而移动的浏览模式,所述传感器 1002 用于检测移动终端的旋转角度,处理器 1003 用于当检测到输入设备输入触发指令时1001 ,根据检测确定的旋转角度移动移动终端中正常模式呈现的全景照片,显示屏幕 1004 用于呈现全景照片。 [0144] 本发明实施例中,输入设备可以是一个或多个 1001 ,例如,输入设备 1001 可能是显示屏或按钮,可能与处理器集成在一起 1003 ,或者可以是独立的外围设备(例如,扫描仪、相机或扬声器)。 如果输入设备 1001 是外围设备,输入设备 1001 可能连接到处理器 1003 使用有线连接(例如电缆/端口)或无线连接(例如蓝牙)。 [0145] 处理器 1003 可以在单芯片、多芯片或多个电子元件上实现,可以采用多种类型的架构,包括嵌入式处理器、专用处理器、控制器等。 [0146] 可能有一个或多个传感器 1002 ,其中传感器 1002 可能有也可能没有运算处理功能。 例如,传感器 1002 在本发明实施例中,可以为重力传感器和陀螺仪传感器中的至少一种。 [0147] 在本公开的该实施例中,如果传感器 1002 具有运算处理功能,传感器 1002 可以确定移动终端的旋转角度; 如果传感器 1002 不具备运算处理功能,传感器 1002 可以检测移动终端的旋转角度,并将检测得到的移动终端的旋转角度发送给处理器 1003 . 处理器 1003 确定移动终端的旋转角度。 [0148] 在第一种实施方式中,传感器 1002 可以用于确定移动终端在旋转过程中所处的放置方向,并根据确定的放置方向确定移动终端的旋转角度。 [0149] 第二种实现方式,传感器 1002 用于在旋转过程中通过以下方式确定移动终端所处的放置方向:检测移动终端的重力方向相对于参考三的X-Y平面方向的夹角- 三维坐标系,参考三维坐标系的X-Y平面平行于移动终端屏幕所在的平面,参考三维坐标系的Z轴垂直于该平面 移动终端屏幕所在的位置; 根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定旋转过程中移动终端所处的放置方向。 [0150] 第三种实现方式,传感器 1002 用于根据移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角,确定移动终端所在的放置方向: 旋转过程中:当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角不大于45度时,确定移动终端的放置方向 旋转过程中位于垂直放置方向,当移动终端的重力方向与参考三维坐标系的X-Y平面方向的夹角大于45度时,确定 旋转过程中移动终端所处的放置方向为水平放置方向。 [0151] 在第四种实现方式中,传感器 1002用于根据放置方向,通过以下方式确定移动终端的旋转角度:若确定移动终端在旋转过程中所处的放置方向为水平放置方向,则使用 参考三​​维坐标系中的Z轴方向作为移动终端在旋转过程中对应的轴向,移动终端相对于该轴向旋转的角度作为旋转角度。 移动终端,或者如果确定移动终端在旋转过程中所处的放置方向为竖直放置方向,则使用参考三中的X轴方向或Y轴方向。 将移动终端在旋转过程中对应的坐标系作为移动终端的轴向,并使用移动终端旋转的角度 h分别以轴向为移动终端的旋转角度。 [0152] 在第五种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,将在移动终端中以正常模式呈现的全景照片确定移动终端的旋转角度达到预设的旋转角度阈值。 [0153] 在第六种实现方式中,处理器 1003 还用于在移动之前,根据确定的旋转角度,移动终端中以正常模式呈现的全景照片,根据预设的旋转角度阈值确定全景照片的最小位移, 拍摄全景照片时的移动终端,以及拍摄全景照片时移动终端沿旋转方向的全景照片的照片宽度,以及处理器 1003 用于移动终端中正常模式下呈现的全景照片的移动方式: 将全景照片沿与移动终端的旋转方向相反的方向移动最小位移。 [0154] 在第七种实现方式中,处理器 1003 还用于当检测到输入设备输入触发指令时 1001 ,提供用于指示旋转移动终端的提示信息。 [0155] 在第八种实现方式中,处理器 1003 还用于在提供用于指示旋转移动终端的提示信息之前,获取拍摄全景照片时保存的移动终端的旋转方向,处理器 1003 用于提供指示旋转移动终端的提示信息的方式如下: 根据获取的旋转方向提供用于指示旋转移动终端的提示信息。 [0156] 需要说明的是,对于本发明实施例图11提供的移动终端,在移动终端中实现控制全景照片显示的过程如描述不够详细,可以参考相关文献 方法实施例的描述,此处不再赘述。 [0157] 本发明实施例提供的移动终端,当用户选择沉浸式浏览模式浏览全景照片时,全景照片随着移动终端的旋转而移动。 使用本发明,用户在浏览全景照片时,可以选择进入沉浸式浏览模式,在沉浸式浏览模式下,可以通过旋转移动终端来浏览全景照片,不需要手动在上面滑动。 移动终端屏幕浏览全景照片。 [0158]本领域的技术人员应该理解,本公开的实施例可以作为方法、系统或计算机程序产品来提供。 因此,本公开可以采用纯硬件实施例、纯软件实施例或结合软件和硬件的实施例的形式。 此外,本公开可以使用在一个或多个计算机可用存储介质(包括但不限于磁盘存储器、光盘只读存储器(CD-ROM)、 光存储器等),包括计算机可用的程序代码。 [0159] 参考根据本公开的实施例的方法、设备(系统)和计算机程序产品的流程图和/或框图来描述本公开。 应当理解,可以使用计算机程序指令来实现流程图和/或框图中的每个过程和/或每个框以及流程图和/或框图中的过程和/或框的组合。 这些计算机程序指令可以提供给通用计算机、专用计算机、嵌入式处理器或任何其他可编程数据处理设备的处理器生成机器,使得任何计算机或处理器执行的指令 其他可编程数据处理设备生成用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的装置。 [0160] 这些计算机程序指令也可以存储在计算机可读存储器中,该计算机可读存储器可以指示计算机或任何其他可编程数据处理设备以特定方式工作,使得存储在计算机可读存储器中的指令生成包括指令装置的工件 . 指令装置在流程图中的一个或多个过程中和/或在框图中的一个或多个块中实现特定功能。 [0161] 这些计算机程序指令也可以加载到计算机或其他可编程数据处理设备上,从而在计算机或其他可编程数据处理设备上执行一系列操作和步骤,从而产生计算机执行的处理。 因此,在计算机或另一可编程设备上执行的指令提供了用于在流程图中的一个或多个过程和/或框图中的一个或多个块中实现特定功能的步骤。 [0162] 尽管已经描述了本公开的一些优选实施例,但是本领域的技术人员在了解基本发明构思后可以对这些实施例进行更改和修改。 因此,所附权利要求旨在被解释为涵盖优选实施例以及落入本公开范围内的所有变化和修改。 [0163] 显然,本领域的技术人员可以对本发明实施例进行各种更改和变型而不脱离本发明实施例的范围。 本公开旨在涵盖这些修改和变化,只要它们落入所附权利要求及其等同技术所限定的保护范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CA2966400A1(String), CA2966400C(String), CN104471519A(String), CN104471519B(String), CN110650241A(String), CN110650241B(String), US10222877B2(String), US10649546B2(String), US11126275B2(String), US20150363915A1(String), US20170212609A1(String), US20190171300A1(String), US20200241657A1(String), US9621802B2(String), WO2016004554A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 15 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CA2966400A1(String), 1049694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CA2966400C(String), 1049695(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519A(String), 1049696(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:25.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN104471519B(String), 1048800(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241A(String), 1049697(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.043 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), CN110650241B(String), 1048801(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US10222877B2(String), 1049698(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US10649546B2(String), 1049699(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US11126275B2(String), 1049700(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20150363915A1(String), 1049701(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20170212609A1(String), 1049702(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.247 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20190171300A1(String), 1049703(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US20200241657A1(String), 1049704(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.314 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), US9621802B2(String), 1049705(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271404(Integer), WO2016004554A1(String), 1049706(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104471519B(String), CN104471519B(String), 1600963200(Integer), 271404(Integer), 185688(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185986(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185986(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185986(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.630 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.631 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185986(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.718 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.787 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:26.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8705554B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for reducing power consumption of WAPI mobile terminal and WAPI mobile terminal(String), WAPI移动终端降低功耗的方法及WAPI移动终端(String), US8705554B2(String), A method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal and a WAPI mobile terminal are provided. Said method includes: caching received WAPI service data into a dynamic cache module, and in a process of caching WAPI service data, when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data. Said WAPI mobile terminal includes: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively.(String), 提供了一种降低无线局域网认证和隐私基础设施(WAPI)移动终端的功耗的方法和WAPI移动终端。 所述方法包括:将接收到的WAPI业务数据缓存到动态缓存模块中,在缓存WAPI业务数据的过程中,当缓存的WAPI业务数据的数据量累积到所述WAPI移动终端设置的数据量阈值时,处理器模块 所述WAPI移动终端处理缓存的WAPI服务数据。 所述WAPI移动终端包括:WAPI通信模块和处理器模块相互连接,存储模块与所述处理器模块连接,动态缓存模块分别与所述WAPI通信模块和处理器模块连接。(String), US13/260080(String), 1271347200(Integer), US8705554B2(String), 1398096000(Integer), 1398096000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 9(Integer), CN100407696C | CN101588602A | CN1578516A | US20040267983A1 | US20050138238A1 | US20070238437A1 | US20120106415A1 | US6219728B1 | US6292492B1(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185987(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\50063a650eeb49d29459f1bbcdfee11a.png(String), 185987(Integer), 50063a650eeb49d29459f1bbcdfee11a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for reducing power consumption of WAPI mobile terminal and WAPI mobile terminal(String), WAPI移动终端降低功耗的方法及WAPI移动终端(String), US8705554B2(String), A method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal and a WAPI mobile terminal are provided. Said method includes: caching received WAPI service data into a dynamic cache module, and in a process of caching WAPI service data, when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data. Said WAPI mobile terminal includes: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively.(String), 提供了一种降低无线局域网认证和隐私基础设施(WAPI)移动终端的功耗的方法和WAPI移动终端。 所述方法包括:将接收到的WAPI业务数据缓存到动态缓存模块中,在缓存WAPI业务数据的过程中,当缓存的WAPI业务数据的数据量累积到所述WAPI移动终端设置的数据量阈值时,处理器模块 所述WAPI移动终端处理缓存的WAPI服务数据。 所述WAPI移动终端包括:WAPI通信模块和处理器模块相互连接,存储模块与所述处理器模块连接,动态缓存模块分别与所述WAPI通信模块和处理器模块连接。(String), US13/260080(String), 1271347200(Integer), US8705554B2(String), 1398096000(Integer), 1398096000(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 9(Integer), CN100407696C | CN101588602A | CN1578516A | US20040267983A1 | US20050138238A1 | US20070238437A1 | US20120106415A1 | US6219728B1 | US6292492B1(String), \20230420\50063a650eeb49d29459f1bbcdfee11a.png(String), 6(Integer), 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185987(Integer), 1. A Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal of which power consumption is reduced, comprising: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively; whereinsaid dynamic cache module is configured to: receive and cache WAPI service data sent by said WAPI communication module; and after data quantity of cached WAPI service data accumulates to a data quantity threshold set by said processor module, send a triggering message to said processor module to notify said processor module to carry out processing, and said processor module is configured to: set the data quantity threshold of cache storage; before data quantity of cached WAPI service data accumulates to the data quantity threshold, not monitor and not process the WAPI service data; after receiving the triggering message of said dynamic cache module, process the WAPI service data cached by said dynamic cache module; set the data quantity threshold of the cache storage according to a real-time requirement of the WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is.(String), 1.一种降低功耗的无线局域网认证和隐私基础设施(WAPI)移动终端,包括:相互连接的WAPI通信模块和处理器模块,以及与所述处理器模块连接的存储模块,以及分别与所述WAPI通信模块和处理器模块连接的动态缓存模块;其中所述动态缓存模块,用于接收并缓存所述WAPI通信模块发送的WAPI服务数据;在缓存的WAPI业务数据的数据量达到所述处理器模块设置的数据量阈值后,向所述处理器模块发送触发消息,通知所述处理器模块进行处理,所述处理器模块用于:设置数据缓存存储数量阈值;在缓存的WAPI业务数据的数据量达到数据量阈值之前,不对WAPI业务数据进行监控和处理;接收到所述动态缓存模块的触发消息后,对所述动态缓存模块缓存的WAPI服务数据进行处理;根据WAPI服务的实时性要求设置缓存存储的数据量阈值,WAPI服务的实时性要求越高,设置的数据量阈值越低。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185987(Integer), 2. The WAPI mobile terminal as claimed in claim 1, whereinsaid processor module is configured to: keep in a sleeping state or process a task of which a priority is higher than that of said WAPI service in a process of caching WAPI data.(String), 2.如权利要求1所述的WAPI移动终端,其中所述处理器模块用于在缓存WAPI数据的过程中保持休眠状态或处理优先级高于所述WAPI服务的任务。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185987(Integer), 3. The WAPI mobile terminal as claimed in claim 2, whereinsaid processor module is further configured to: move the cached WAPI service data to said storage module after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, and enter into the sleeping state over again or continue to process the task of which the priority is higher than that of said WAPI service.(String), 3.如权利要求2所述的WAPI移动终端,其中所述处理器模块,还用于在缓存的WAPI业务数据的数据量累积到所述数据量阈值后,将缓存的WAPI业务数据移至所述存储模块,重新进入休眠状态或继续处理任务。其优先级高于上述WAPI服务。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185987(Integer), 4. The WAPI mobile terminal as claimed in claim 1, whereinsaid dynamic cache module is a Field Programmable Gate Array.(String), 4.如权利要求1所述的WAPI移动终端,其中所述动态缓存模块为现场可编程门阵列。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185987(Integer), 5. A method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal, comprising:caching received WAPI service data into a dynamic cache module, and when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data, and in a process of caching WAPI data, before data quantity of cached WAPI service data accumulates to the data quantity threshold, said processor module not monitoring and processing the WAPI service data, and said processor module being in a sleeping state or processing a task of which a priority is higher than that of said WAPI service, wherein said data quantity threshold is set by the WAPI mobile terminal according to a real-time requirement of a WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is.(String), 5.一种降低无线局域网认证和隐私基础设施(WAPI)移动终端功耗的方法,包括:将接收到的WAPI业务数据缓存到动态缓存模块中,当缓存的WAPI业务数据的数据量累积到WAPI移动终端设置的数据量阈值时,WAPI移动终端的处理器模块处理缓存的WAPI业务数据,并在缓存WAPI数据的过程,在缓存的WAPI业务数据的数据量达到数据量阈值之前,所述处理器模块不对WAPI业务数据进行监控和处理,所述处理器模块处于休眠状态或处理任务优先级高于所述WAPI服务,其中,所述数据量阈值由WAPI移动终端根据WAPI服务的实时性要求设置,WAPI服务的实时性要求越高,则越低设置的数据量阈值是。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185987(Integer), 6. The method as claimed in claim 5, said method further comprising:after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, said processor module moving the cached WAPI service data to a storage module of said WAPI mobile terminal, and entering into the sleeping state over again or continuing to process the task of which the priority is higher than that of said WAPI service.(String), 6.如权利要求5所述的方法,所述方法还包括:当缓存的WAPI业务数据的数据量累积到所述数据量阈值后,所述处理器模块将缓存的WAPI业务数据移至所述WAPI移动终端的存储模块,重新进入休眠状态或继续处理任务其中优先级高于上述WAPI服务。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185987(Integer), TECHNICAL FIELD [0001]The present invention relates to the communication terminal field, and particularly, to a method for reducing power consumption of a mobile terminal and a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal. BACKGROUND OF THE RELATED ART [0002]After the Time Division-Synchronous Code Division Multiple Access (TD-SDCMA) technology of the 3rd Generation (3G) standards is commercialized, the China wireless network standard WAPI also emerges to the forefront along with the wireless city upsurge rising from various cities in China, and the mobile terminal supporting the WAPI function (namely the WAPI mobile terminal) becomes more and more popular. [0003]In the mobile communication system, the continuous working time length of the mobile terminal is an important index reflecting the quality and performance of products. The mobile terminal downloading data through the WAPI technique during a long time will run out of the power of the battery quickly, and for the purpose of extending the continuous working time of the mobile terminal, it is necessary to reduce the power consumption of the mobile terminal. [0004]As shown in FIG. 1, in the prior art, the WAPI mobile terminal comprises a processor module 101, a user interface module 102, a WAPI communication module 103 and a storage module 104. When the WAPI mobile terminal downloads the large flow and long time data, the processor module 101 of the mobile terminal is required to monitor the data sent by the WAPI communication module 103 all the time, and stores the data to the storage module 104 in real-time, and carries out related processing on the received data, and the above large quantity of data processing operations of the processor module 101 makes the working current of the mobile terminal keep in a higher constant value all the time, which causes the mobile terminal to severely consume the power. SUMMARY OF THE INVENTION [0005]The technical problem to be solved in the present invention is to provide a method for reducing power consumption of a WAPI mobile terminal and a WAPI mobile terminal, which saves the power consumption of the mobile terminal and extends the working time. [0006]In order to solve the above problem, the present invention provides a WAPI mobile terminal for reducing power consumption, comprising: a WAPI communication module and a processor module connected with each other, and a storage module connected with said processor module, and a dynamic cache module connected with said WAPI communication module and said processor module respectively; [0007]said dynamic cache module being configured to: receive and cache WAPI service data sent by said WAPI communication module; and after data quantity of cached WAPI service data accumulates to a data quantity threshold set by said processor module, send a triggering message to said processor module to notify said processor module to carry out processing. [0008]In the above WAPI mobile terminal, the following characteristics are further included: [0009]said processor module is configured to: set the data quantity threshold of cache storage; in a process of caching WAPI service data, not monitor and process the WAPI service data; and after receiving the triggering message of said dynamic cache module, process the WAPI service data cached by said dynamic cache module. [0010]In the above WAPI mobile terminal, the following characteristics are further included: [0011]said processor module is configured to: keep in a sleeping state or process a task of which a processing priority is higher than the processing priority of said WAPI service in a process of caching WAPI data. [0012]In the above WAPI mobile terminal, the following characteristics are further included: [0013]said processor module is configured to: set the data quantity threshold of the cache storage according to a real-time requirement of the WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is. [0014]In the above WAPI mobile terminal, the following characteristics are further included: [0015]said processor module is further configured to: move the cached WAPI service data to said storage module after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, and enter into the sleeping state over again or continue to process a task of which the processing priority is higher than the processing priority of said WAPI service. [0016]In the above WAPI mobile terminal, the following characteristics are further included: [0017]said dynamic cache module is a Field Programmable Gate Array. [0018]In order to solve the above problem, the present invention also provides a method for reducing power consumption of a Wireless Local Area Networks Authentication and Privacy Infrastructure (WAPI) mobile terminal, comprising: [0019]caching received WAPI service data into a dynamic cache module, and when data quantity of cached WAPI service data accumulates to a data quantity threshold set by said WAPI mobile terminal, a processor module of said WAPI mobile terminal processing the cached WAPI service data. [0020]The above method further comprises: [0021]in a process of caching WAPI data, said processor module not monitoring and processing the WAPI service data, and said processor module being in a sleeping state or processing a task of which a processing priority is higher than the processing priority of said WAPI service. [0022]In the above method, the following characteristics are further included: [0023]said data quantity threshold is set by the WAPI mobile terminal according to a real-time requirement of a WAPI service, and the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is. [0024]The above method further comprises: [0025]after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, said processor module moving the cached WAPI service data to a storage module of said WAPI mobile terminal, and entering into the sleeping state over again or continuing to process a task of which the processing priority is higher than the processing priority of said WAPI service. [0026]In the method of the present invention, the WAPI mobile terminal adds a dynamic cache module, and when the mobile terminal carries out WAPI data downloading operations of lower real-time requirement and large data quantity, in the time consuming process of caching the data to the dynamic cache module, the processor of the mobile terminal doesn't need to monitor and process the data in the dynamic cache module, and further uniformly processes the data until the data accumulated in the dynamic cache module reaches to the quantity set by system, and thus the whole power consumption of the mobile terminal can be effectively reduced, and the working quantity of the processor is reduced, and further the power of the mobile terminal is saved, and the continuous using time of the mobile terminal is extended. BRIEF DESCRIPTION OF DRAWINGS [0027]FIG. 1 is a function structure diagram of the WAPI mobile terminal in the prior art; [0028]FIG. 2 is a function structure diagram of the WAPI mobile terminal of which the power consumption can be reduced according to the example; [0029]FIG. 3 is a flow chart of the method for reducing the power consumption of the WAPI mobile terminal according to the example; [0030]FIG. 4 is a flow chart of the method for reducing the power consumption of the WAPI mobile terminal according to the specific example. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0031]As shown in FIG. 2, comparing with the WAPI mobile terminal shown in FIG. 1, the WAPI mobile terminal of which the power consumption is reduced adds a dynamic cache module 105 respectively connected with the processor module 101 and the WAPI communication module 103; [0032]the user interface module 102 is used for data interaction between the man-machine interacting device and the processor module 101; wherein the man-machine interacting device of the mobile terminal is a terminal screen and a keyboard; [0033]the WAPI communication module 103 is used for carrying out data interaction with a wireless access node of a WAPI network by the WAPI protocol, and sending the WAPI data received from the wireless access node to the processor module 101 or the dynamic cache module 105; [0034]the storage module 104 is used for storing WAPI data under the control of the processor module 101; [0035]the processor module 101 is used for controlling the normal operation of the whole system, receiving the input of the external control signal, and processing the WAPI transmission data; is further used for setting the data quantity threshold of the cache storage according to the real-time requirement of the WAPI service, wherein the higher the real-time requirement of the WAPI service is, the lower the set data quantity threshold is; is further used for in the process of caching the WAPI service data, enter into a sleeping state or process the task of which the priority is higher than that of said WAPI service, not monitoring or processing WAPI service data; and is further used for moving cached WAPI service data to said storage module after receiving the triggering message of said dynamic cache module, namely after the data quantity of the cached WAPI service data accumulates to said data quantity threshold, and entering into the sleeping state over again or continuing to process the task of which the priority is higher than that of said WAPI service; [0036]the dynamic cache module 105 is used for receiving and caching the WAPI service data sent by said WAPI communication module; and is further used for sending a triggering message to said processor module 101 after the data quantity of the cached WAPI service data accumulates to the data quantity threshold set by said processor module; [0037]this dynamic cache module 105 can be a Field Programmable Gate Array (FPGA) chip with low power consumption, and the Random Access Memory (RAM) inside the FPGA chip stores the cached WAPI data. [0038]According to the real-time requirement of the WAPI service, the WAPI mobile terminal sets the data quantity threshold of the cache storage (namely the dynamic cache module), and the higher the real-time requirement of the WAPI service is, the lower the data quantity threshold of the cache storage is. For example, for the WAPI service which is required to be played in streaming media, the real-time requirement of the data transmission is very high, and the user can set a very low data quantity threshold of the cache storage, or directly set to 0, namely not caching this WAPI service data, and directly caching data by the small capacity RAM inside the processor. For the WAPI service which requires downloading file packets in a large quantity and not paying attention to the downloading content, the user can set a very high data quantity threshold of the cache storage. [0039]As shown in FIG. 3, the method for reducing power consumption of the WAPI mobile terminal comprises: [0040]step 310, the mobile terminal and the wireless access node of the WAPI network establish a communication connection between them to download data; [0041]step 302, the WAPI mobile terminal caches the received WAPI service data into the dynamic cache module; in the process of caching the WAPI data, the processor module of the WAPI mobile terminal does not process the cached WAPI data; [0042]in the process of caching the WAPI data, the processor judges that except the WAPI service, there is no other task of which the priority is higher than that of the WAPI service running, and the processor enters into the sleeping or low power consumption state; the processor judges that besides wireless communication of the WAPI, there is currently another task of which the priority is higher than that of the WAPI service running, and the processor processes this task of which the priority is higher than that of the WAPI service. [0043]Step 303, when the cached WAPI data accumulates to the data quantity threshold set by the WAPI mobile terminal, the processor of the WAPI mobile terminal processes the cached WAPI service data; [0044]when the cached WAPI data accumulates to the data quantity threshold set by the WAPI mobile terminal, and when the dynamic cache module sends the triggering message to the processor, and if the processor is in the sleeping state, then the processor quits the sleeping state, and moves the WAPI data in the dynamic cache module to the storage module; if the processor is processing another task of which the priority is higher than that of the WAPI service, then after finishing this task, the processor further moves the WAPI data inside the dynamic cache module to the storage module, or after receiving the triggering message, the processor suspends processing of this task, and moves the WAPI data in the dynamic cache module to the storage module. [0045]Step 304, the processor judges whether the WAP service data are all received, and if yes, the flow ends, otherwise the step 302 is carried out to continue to receive the WAPI service data. [0046]According to the above method, if the user downloads the WAPI service with the large flow quantity data and not high real-time requirement through the WAPI, the processor doesn't need to monitor and carry out the downloading operation of the data all the time, but caches the WAPI service data in the dynamic cache module, and when the stored data in the cache area reach to a certain value, the processor further moves the data to the storage space, and in the process of caching the WAPI service data, the processor does not monitor and process cached data, and thus in the time consuming process of caching the WAPI data, the processor doesn't need to consume the processing capability on the WAPI service, thereby saving the power; especially for the case of the larger downloaded WAPI service data quantity and consuming longer downloading time, the effect is obvious. [0047]It will further describe the specific example of the present invention in detail in combination with the figures below. [0048]As shown in FIG. 4, combining with FIG. 2, the dynamic cache module 105 of the mobile terminal is a FPGA chip, and the method of the WAPI mobile terminal processing WAPI service data comprises: [0049]step 401, according to their own application requirements, the user sets the data capacity of the cache storage area in the FPGA according to the real-time requirement of the WAPI service through the Man-Machine Interacting (MMI) devices, the set value is input into the register of the processor module 101 through the user interface module 102 of the mobile terminal; [0050]for example, when the real-time requirement of the WAPI service is very high, the data capacity of the FPGA can be set to 0, and when the real-time requirement of the WAPI service is low, for the purpose of saving power of the mobile terminal to the maximum, the user can set the data capacity of the FPGA to the maximum capacity of the cache storage. [0051]Step 402, according to the set value in the register of the processor module 101, the FGPA sets the capacity of the cache storage area of the FPGA; [0052]step 403, the WAPI communication module 103 and the wireless access node of the WAPI network establish the communication connection between them, and the user downloads data by the mobile terminal; [0053]step 404, the processor module 101 judges whether there is another task of which the priority is higher than that of the WAPI service running besides the WAPI communication module 103 being carrying out the wireless data transmission, and if yes, step 406 is carried out, otherwise step 405 is carried out; [0054]step 405, the processor module 101 enters into the sleeping or low power consumption mode, and waits for the execution of the higher priority service and the wake-up of the external interruption; [0055]step 406, the WAPI communication module 103 of the mobile terminal caches the received download data into the RAM of the dynamic cache module 105; [0056]step 407, when the data capacity stored in the RAM of the FPGA reaches to the capacity threshold set by the user, an interruption is generated to be input into the processor module 101; [0057]step 408, if the processor module 101 is in the sleeping or low power consumption mode, the processor module 101 will quit the sleeping or low power consumption mode, and move the cached data in the FPGA to the storage module 104; [0058]step 409, the processor module 101 judges whether the data transmission between the WAPI communication module 103 and the wireless access node of the WAPI network ends, and if yes, step 410 is carried out, otherwise step 404 is carried out; [0059]step 410, the mobile terminal ends this data downloading service. [0060]In the above implementation way, due to the setup of the dynamic cache module between the processing module and the WAPI communication module, the processor module doesn't need to process the WAPI service data sent by the WAPI communication module in real-time. The above method also sets the data quantity threshold, and before the WAPI service data cached by the dynamic cache module reaches to the data quantity threshold, the processor module is able to not process the WAPI service data cached in the dynamic cache module, thereby saving the power of the terminal and reducing the power consumption of the terminal. But the present invention is not limited to the above one way, and in other examples, the processor doesn't need to wait for the WAPI service data cached in the dynamic cache module reaching to the data quantity threshold in order to process data, and before reaching to the data quantity threshold, the processor can also carry out one or more times, regular or irregular discontinuous processing on the cached data as long as the processor doesn't need to process cached data in real-time, and the present invention does not limit the specific implementation method. [0061]Certainly, the present invention can also have other various examples, and without departing from the spirit or essence of the present invention, the person skilled in the art can make various corresponding modifications and transformations according to the present invention. And all the modifications and transformations shall all fall into the protection scope of the appended claims of the present invention. INDUSTRIAL APPLICABILITY [0062]In the method of the present invention, the WAPI mobile terminal adds a dynamic cache module, and when the mobile terminal carries out WAPI data downloading operations of lower real-time requirement and large data quantity, and in the time consuming process of caching the data into the dynamic cache module, the processor of the mobile terminal doesn't need to monitor and process the data in the dynamic cache module, and further uniformly processes the data until the data accumulated in the dynamic cache module reaches to the quantity set by system, and thus the whole power consumption of the mobile terminal can be effectively reduced, and the working quantity of the processor is reduced, and further the power of the mobile terminal is saved, and the continuous using time of the mobile terminal is extended.(String), 技术领域 [0001] 本发明涉及通信终端领域,尤其涉及一种降低移动终端功耗的方法及WAPI移动终端。 相关技术背景 [0002] 第三代(3G)标准的时分-同步码分多址(TD-SDCMA)技术商用后,随着中国各城市掀起的无线城市热潮,中国无线网络标准WAPI也崭露头角 ,支持WAPI功能的移动终端(即WAPI移动终端)越来越普及。 [0003] 在移动通信系统中,移动终端的连续工作时长是反映产品质量和性能的重要指标。 移动终端长时间通过WAPI技术下载数据会很快耗尽电池的电量,为了延长移动终端的连续工作时间,有必要降低手机的功耗 终端。 [0004] 如图1所示,现有技术中,WAPI移动终端包括处理器模块 101 , 一个用户界面模块 102 ,一个WAPI通信模块 103 和一个存储模块 104 . 当WAPI移动终端下载大流量、长时间数据时,处理器模块 101 需要手机端监听WAPI通讯模块发送的数据 103 一直,并将数据存储到存储模块 104 实时,并对接收到的数据进行相关处理,以及处理器模块的上述大量数据处理操作 101 使得移动终端的工作电流始终保持在一个较高的恒定值,导致移动终端严重耗电。 发明内容 [0005] 本发明所要解决的技术问题是提供一种降低WAPI移动终端功耗的方法及WAPI移动终端,节省移动终端的功耗,延长工作时间。 [0006] 为了解决上述问题,本发明提供了一种降低功耗的WAPI移动终端,包括:WAPI通信模块和处理器模块,与所述处理器模块连接的存储模块,动态缓存 分别与所述WAPI通信模块和所述处理器模块连接的模块; [0007] 所述动态缓存模块,用于接收并缓存所述WAPI通信模块发送的WAPI服务数据; 当缓存的WAPI业务数据的数据量累积到所述处理器模块设置的数据量阈值后,向所述处理器模块发送触发消息,通知所述处理器模块进行处理。 [0008] 在上述WAPI移动终端中,还包括以下特点: [0009] 所述处理器模块,用于设置缓存存储的数据量阈值; 在缓存WAPI服务数据的过程中,不对WAPI服务数据进行监控和处理; 接收到所述动态缓存模块的触发消息后,对所述动态缓存模块缓存的WAPI服务数据进行处理。 [0010] 在上述WAPI移动终端中,还包括以下特点: [0011] 所述处理器模块,用于在缓存WAPI数据的过程中,保持休眠状态或处理处理优先级高于所述WAPI服务的处理优先级的任务。 [0012] 在上述WAPI移动终端中,还包括以下特点: [0013] 所述处理器模块用于根据WAPI服务的实时性要求设置缓存存储的数据量阈值,WAPI服务的实时性要求越高,设置的数据量阈值越低。 . [0014]在上述WAPI移动终端中,还包括以下特点: [0015] 所述处理器模块,还用于在缓存的WAPI业务数据的数据量累计到所述数据量阈值后,将缓存的WAPI业务数据移至所述存储模块,重新进入休眠状态或继续处理任务。 其处理优先级高于所述WAPI服务的处理优先级。 [0016] 在上述WAPI移动终端中,还包括以下特点: [0017] 所述动态缓存模块为现场可编程门阵列。 [0018] 为了解决上述问题,本发明还提供了一种降低无线局域网认证和隐私基础设施(WAPI)移动终端功耗的方法,包括: [0019] 将接收到的WAPI业务数据缓存到动态缓存模块中,当缓存的WAPI业务数据的数据量累积到WAPI移动终端设置的数据量阈值时,WAPI移动终端的处理器模块对缓存的WAPI业务数据进行处理。 [0020] 上述方法还包括: [0021] 在缓存WAPI数据的过程中,所述处理器模块不对WAPI服务数据进行监控和处理,并且所述处理器模块处于休眠状态或者正在处理优先级高于所述WAPI服务的处理优先级的任务。 [0022] 在上述方法中,还包括以下特征: [0023] 所述数据量阈值由WAPI移动终端根据WAPI业务的实时性要求设置,WAPI业务的实时性要求越高,设置的数据量阈值越低。 [0024] 上述方法还包括: [0025] 当缓存的WAPI业务数据的数据量累积到所述数据量阈值后,所述处理器模块将缓存的WAPI业务数据移至所述WAPI移动终端的存储模块,重新进入休眠状态或继续处理任务 其中处理优先级高于该WAPI服务的处理优先级。 [0026] 在本发明的方法中,WAPI移动终端增加了动态缓存模块,当移动终端进行实时性要求较低、数据量较大的WAPI数据下载操作时,在缓存数据的耗时过程中, 动态缓存模块,移动终端的处理器不需要监视和处理动态缓存模块中的数据,进一步统一处理数据,直到动态缓存模块中累积的数据达到系统设置的数量, 从而可以有效降低移动终端的整体功耗,减少处理器的工作量,进一步节省移动终端的电量,延长移动终端的连续使用时间。 附图说明 [0027] 图1为现有技术中WAPI移动终端的功能结构图; [0028] 图2为实施例的可降低功耗的WAPI移动终端的功能结构图。 [0029] 图3为本实施例的降低WAPI移动终端功耗的方法流程图; [0030] 图4是根据具体示例的降低WAPI移动终端功耗的方法的流程图。 本发明的优选实施例 [0031] 如图2所示,与图1所示的WAPI移动终端相比,本发明降低功耗的WAPI移动终端增加了动态缓存模块。 105 分别与处理器模块相连 101 和WAPI通信模块 103 ; [0032] 用户界面模块 102 用于人机交互装置与处理器模块之间的数据交互 101; 其中,所述移动终端的人机交互装置为终端屏幕和键盘; [0033] WAPI通讯模块 103 用于通过WAPI协议与WAPI网络的无线接入节点进行数据交互,将从无线接入节点接收到的WAPI数据发送给处理器模块 101 或动态缓存模块 105 ; [0034] 存储模块 104 用于在处理器模块的控制下存储WAPI数据 101 ; [0035] 处理器模块 101 用于控制整个系统的正常运行,接收外部控制信号的输入,处理WAPI传输数据; 还用于根据WAPI服务的实时性要求设置缓存存储的数据量阈值,WAPI服务的实时性要求越高,设置的数据量阈值越低。 进一步用于在缓存WAPI服务数据的过程中,进入休眠状态或处理优先级高于该WAPI服务的任务,而不是监听或处理WAPI服务数据; 进一步用于在接收到所述动态缓存模块的触发消息后,即缓存的WAPI业务数据的数据量累积到所述数据量阈值后,将缓存的WAPI业务数据移至所述存储模块,并进入休眠状态。 再次或继续处理优先级高于该WAPI服务的任务; [0036] 动态缓存模块 105 用于接收并缓存所述WAPI通信模块发送的WAPI服务数据; 进一步用于向所述处理器模块发送触发消息 101 缓存的WAPI业务数据的数据量累积到所述处理器模块设置的数据量阈值后; [0037] 这个动态缓存模块 105 可以是低功耗的现场可编程门阵列(FPGA)芯片,FPGA芯片内部的随机存取存储器(RAM)存储缓存的WAPI数据。 [0038] WAPI移动终端根据WAPI服务的实时性要求,设置缓存存储(即动态缓存模块)的数据量阈值,WAPI服务的实时性要求越高,则越低 缓存存储的数据量阈值是。 例如,对于需要在流媒体中播放的WAPI服务,数据传输的实时性要求很高,用户可以将缓存存储的数据量阈值设置的很低,或者直接设置为 0,即不缓存此WAPI服务数据,直接由处理器内部的小容量RAM缓存数据。 对于需要大量下载文件包且不关注下载内容的WAPI业务,用户可以设置很高的缓存存储数据量阈值。 [0039] 如图3所示,降低WAPI移动终端功耗的方法包括: [0040] 步 310 、移动终端与WAPI网络的无线接入节点之间建立通信连接,进行数据下载; [0041] 步 302 、WAPI移动终端将接收到的WAPI业务数据缓存到动态缓存模块中; 在缓存WAPI数据的过程中,WAPI移动终端的处理器模块不对缓存的WAPI数据进行处理。 [0042] 在缓存WAPI数据的过程中,处理器判断除WAPI服务外,没有其他任务的优先级高于正在运行的WAPI服务,处理器进入休眠或低功耗状态。 处理器判断当前除了WAPI无线通信外,还有一个优先级高于WAPI服务运行的任务,处理器处理该优先级高于WAPI服务的任务。 [0043] 步 303、当缓存的WAPI数据累积到WAPI移动终端设置的数据量阈值时,WAPI移动终端的处理器对缓存的WAPI业务数据进行处理; [0044] 当缓存的WAPI数据累积到WAPI移动终端设置的数据量阈值时,动态缓存模块向处理器发送触发消息,若处理器处于休眠状态,则处理器退出休眠状态, 将动态缓存模块中的WAPI数据移动到存储模块中; 如果处理器正在处理另一个优先级高于WAPI服务的任务,则在完成该任务后,处理器进一步将动态缓存模块内的WAPI数据移动到存储模块,或者在接收到触发消息后, 处理器暂停处理该任务,将动态缓存模块中的WAPI数据移动到存储模块中。 [0045] 步 304 ,处理器判断是否接收到所有WAP业务数据,如果是,则流程结束,否则执行该步骤 302 进行继续接收WAPI服务数据。 [0046] 根据上述方法,如果用户通过WAPI下载数据流量大、实时性要求不高的WAPI服务,则处理器不需要一直监听并执行数据的下载操作。 ,而是将WAPI服务数据缓存在动态缓存模块中,当缓存区中存储的数据达到一定值时,处理器进一步将数据移动到存储空间中,在缓存WAPI服务数据的过程中, 处理器不对缓存的数据进行监控和处理,因此在缓存WAPI数据的耗时过程中,处理器不需要消耗对WAPI服务的处理能力,从而节省了电能。 特别是对于下载的WAPI服务数据量较大,下载时间较长的情况,效果更为明显。 [0047] 下面结合附图对本发明的具体实施例作进一步详细说明。 [0048] 如图4所示,结合图2,动态缓存模块 105 移动终端的为FPGA芯片,WAPI移动终端处理WAPI业务数据的方法包括: [0049] 步 401 ,用户根据自己的应用需求,通过人机交互(MMI)设备,根据WAPI服务的实时要求,设置FPGA中缓存存储区的数据容量,将设置值输入到 处理器模块的寄存器 101 通过用户界面模块 102 移动终端; [0050] 例如,当WAPI服务的实时性要求很高时,可以将FPGA的数据容量设置为0,而当WAPI服务的实时性要求不高时,达到节省功耗的目的。 移动端设置为最大,用户可以将FPGA的数据容量设置为缓存存储的最大容量。 [0051] 步 402 , 根据处理器模块寄存器中的设定值 101 ,FGPA设置FPGA的缓存存储区的容量; [0052] 步 403 , WAPI通信模块 103 与WAPI网络的无线接入节点之间建立通信连接,用户通过移动终端下载数据; [0053] 步 404 , 处理器模块 101 判断除WAPI通信模块外是否还有优先级高于WAPI服务运行的任务 103 正在进行无线数据传输,如果是,步骤 406 执行,否则步骤 405 完成了; [0054] 步 405 , 处理器模块 101 进入休眠或低功耗模式,等待更高优先级服务的执行和外部中断的唤醒; [0055] 步 406 , WAPI通信模块 103移动终端将接收到的下载数据缓存到动态缓存模块的RAM中 105 ; [0056] 步 407 ,当FPGA的RAM中存储的数据容量达到用户设定的容量阈值时,产生一个中断输入到处理器模块 101 ; [0057] 步 408 , 如果处理器模块 101 处于睡眠或低功耗模式时,处理器模块 101 会退出休眠或低功耗模式,将FPGA中的缓存数据移动到存储模块中 104 ; [0058] 步 409 , 处理器模块 101 判断WAPI通讯模块之间是否有数据传输 103 WAPI网络的无线接入节点结束,如果是,步骤 410 执行,否则步骤 404 完成了; [0059] 步 410 ,移动终端结束本次数据下载业务。 [0060] 在上述实现方式中,由于在处理模块和WAPI通信模块之间设置了动态缓存模块,处理器模块不需要实时处理WAPI通信模块发送的WAPI服务数据。 上述方法还设置了数据量阈值,在动态缓存模块缓存的WAPI业务数据达到数据量阈值之前,处理器模块可以不对动态缓存模块缓存的WAPI业务数据进行处理,从而节省了时间。 终端的功率,降低终端的功耗。 但本发明不限于上述一种方式,在其他示例中,处理器不需要等待动态缓存模块中缓存的WAPI服务数据达到数据量阈值来处理数据,并且 在达到数据量阈值之前,只要处理器不需要对缓存数据进行实时处理,处理器还可以对缓存数据进行一次或多次、定期或不定期的不连续处理,本发明 不限定具体的实现方式。 [0061] 当然,本发明还可以有其他各种实施例,在不脱离本发明的精神或实质的情况下,本领域的技术人员可以根据本发明做出各种相应的修改和变换。 并且所有的修改和变换均落入本发明所附权利要求的保护范围之内。 工业实用性 [0062] 在本发明的方法中,WAPI移动终端增加了动态缓存模块,当移动终端进行实时性要求较低、数据量较大的WAPI数据下载操作时,在缓存数据的过程中比较耗时。 进入动态缓存模块,移动终端的处理器不需要对动态缓存模块中的数据进行监听和处理,进一步对数据进行统一处理,直到动态缓存模块中累积的数据达到系统设定的数量 ,从而可以有效降低移动终端的整体功耗,减少处理器的工作量,进一步节省移动终端的电量,延长移动终端的连续使用时间。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.808 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101588602A(String), CN101588602B(String), EP2434802A1(String), EP2434802A4(String), EP2434802B1(String), US20120106415A1(String), US8705554B2(String), WO2010133115A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101588602A(String), CN101588602B(String), EP2434802A1(String), EP2434802A4(String), EP2434802B1(String), US20120106415A1(String), US8705554B2(String), WO2010133115A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101588602A(String), CN101588602B(String), EP2434802A1(String), EP2434802A4(String), EP2434802B1(String), US20120106415A1(String), US8705554B2(String), WO2010133115A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:27.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), CN101588602A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271223(Integer), CN101588602B(String), 1048298(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), EP2434802A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), EP2434802A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), EP2434802B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), US20120106415A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), US8705554B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.244 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271223(Integer), WO2010133115A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101588602B(String), CN101588602B(String), 1310486400(Integer), 271223(Integer), 185507(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.391 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185987(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185987(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185987(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185987(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.632 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.632 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.874 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:28.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8548504B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US8548504B2(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别宏小区中的毫微微小区。 当移动终端在广播信道部分中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息,并且将列表和关于相邻毫微微基站的信息发送给移动终端。(String), US13/013617(String), 1295884800(Integer), US8548504B2(String), 1380556800(Integer), 1380556800(Integer), 美国(String), 4(Integer), KR(String), 4(Integer), 25(Integer), KR100858282B1 | KR1020090110103A | KR1020100011271A | US20090021287A1 | US20090135758A1 | US20090168727A1 | US20090239511A1 | US20090252073A1 | US20090299788A1 | US20090310561A1 | US20100035622A1 | US20100190496A1 | US20100240397A1 | US20100260068A1 | US20100278141A1 | US20110110520A1 | US20110111754A1 | US7107055B2 | US8144725B2 | US8180368B2 | US8345633B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185988(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\eea7d408950d47d994e30e860a3eb433.png(String), 185988(Integer), eea7d408950d47d994e30e860a3eb433.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.453 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Communication method of a mobile terminal and method of advertising to a mobile terminal(String), 移动终端的通信方法和向移动终端做广告的方法(String), US8548504B2(String), A communication method of a macro base station including reporting information about a broadcast channel section in order to identify a femtocell in the macrocell, is provided. The macro base station receives position information of a mobile terminal and a request for information about neighboring femto base stations from the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section. The macro base station generates a list of the neighboring femto base stations and information about the neighboring femto base stations based on the position information of the mobile terminal, and transmits the list and the information about the neighboring femto base stations to the mobile terminal.(String), 提供了一种宏基站的通信方法,包括报告关于广播信道部分的信息以便识别宏小区中的毫微微小区。 当移动终端在广播信道部分中识别出可访问的毫微微基站时,宏基站从移动终端接收移动终端的位置信息和对关于相邻毫微微基站的信息的请求。 宏基站基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息,并且将列表和关于相邻毫微微基站的信息发送给移动终端。(String), US13/013617(String), 1295884800(Integer), US8548504B2(String), 1380556800(Integer), 1380556800(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 4(Integer), 25(Integer), KR100858282B1 | KR1020090110103A | KR1020100011271A | US20090021287A1 | US20090135758A1 | US20090168727A1 | US20090239511A1 | US20090252073A1 | US20090299788A1 | US20090310561A1 | US20100035622A1 | US20100190496A1 | US20100240397A1 | US20100260068A1 | US20100278141A1 | US20110110520A1 | US20110111754A1 | US7107055B2 | US8144725B2 | US8180368B2 | US8345633B2(String), \20230420\eea7d408950d47d994e30e860a3eb433.png(String), 14(Integer), 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.522 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 1. A communication method of a macro base station, the method comprising:reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell;receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section;generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal; andtransmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal.(String), 1.一种宏基站的通信方法,该方法包括:向宏基站的宏小区中的至少一个毫微微基站上报宏小区中用于标识毫微微小区的广播信道段信息;当移动终端在广播信道部分识别出可访问的毫微微基站时,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求;基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息;和将相邻毫微微基站的列表和相邻毫微微基站的信息发送给移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 2. The method of claim 1, further comprising transmitting connection information to enable the mobile terminal to access a femto base station selected by the mobile terminal.(String), 2.如权利要求1所述的方法,还包括发送连接信息以使移动终端能够接入由移动终端选择的毫微微基站。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 3. The method of claim 1, wherein the broadcast channel section is set in a downlink broadcast channel of the macrocell at a preset cycle.(String), 3.如权利要求1所述的方法,其中广播信道段以预设周期设置在宏小区的下行广播信道中。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 4. The method of claim 1, wherein the information about the neighbor femto base stations comprises information about a shop in which each of the femto base stations is located or information about a discount policy of a connection service offered by each of the femto base stations.(String), 4.如权利要求1所述的方法,其中所述相邻毫微微基站的信息包括各毫微微基站所在店铺的信息或各毫微微基站提供的连接服务的优惠政策信息。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 5. A communication method of a mobile terminal, the method comprising:detecting a broadcast channel section used to identify a femtocell in a macrocell;identifying a femto base station accessible to the mobile terminal based on a measurement of an intensity of a signal of the broadcast channel section;transmitting, to a macro base station, position information of the mobile terminal and a request for information about the accessible femto base station;receiving a list of neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations from the macro base station; andselecting a femto base station based on the list and the information about the neighbor femto base stations.(String), 5.一种移动终端的通信方法、方法包括:检测宏小区中用于识别毫微微小区的广播信道段;基于对广播信道部分的信号强度的测量来识别移动终端可访问的毫微微基站;向宏基站发送移动终端的位置信息和可访问的毫微微基站的信息请求;从宏基站接收移动终端的相邻毫微微基站列表和相邻毫微微基站的信息;和基于列表和关于相邻毫微微基站的信息选择毫微微基站。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 6. The method of claim 5, wherein the detecting of the broadcast channel section is performed when a femtocell exploration mode of the mobile terminal is set to on.(String), 6.如权利要求5所述的方法,其中广播信道段的检测在移动终端的毫微微基站探索模式设置为开启时进行。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 7. The method of claim 5, wherein the identifying of the accessible femto base station is performed by comparing a preset threshold value with the measured intensity of the signal of the broadcast channel section.(String), 7.如权利要求5所述的方法,其中可接入的毫微微基站的识别是通过将预设的阈值与广播信道段的信号的测量强度进行比较来执行的。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 8. The method of claim 5, wherein the selected femto base station is selected based on preferences of a user of the mobile terminal.(String), 8.如权利要求5所述的方法,其中所选择的毫微微基站是基于移动终端的用户的偏好来选择的。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 9. The method of claim 5, further comprising receiving connection information to enable access to the selected femto base station from the macro base station.(String), 9.如权利要求5所述的方法,还包括接收连接信息以使得能够从宏基站接入所选择的毫微微基站。(String), 1(Integer), 8(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 10. The method of claim 5, wherein the broadcast channel section is set in a downlink broadcast channel of the macrocell at a preset cycle.(String), 10.如权利要求5所述的方法,其中广播信道段以预设周期设置在宏小区的下行广播信道中。(String), 1(Integer), 9(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 11. The method of claim 5, wherein the information about the neighbor femto base stations comprises information about a shop in which the femto base stations are located, respectively, or comprises information about a discount policy of a connection service offered by each respective femto base station.(String), 11.如权利要求5所述的方法,其中所述相邻毫微微基站的信息包括各毫微微基站所在店铺的信息,或者包括各毫微微基站所提供的连接服务的优惠政策信息。(String), 1(Integer), 10(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 12. A communication method of a femto base station, the method comprising: receiving, by the femto base station from a macro base station, a report about a broadcast channel section used to identify a femtocell in a macrocell of the macro base station; setting, by the femto base station, a signal in the broadcast channel section to report existence of a femtocell of the femto base station within the macrocell; and connecting, by the femto base station, to a mobile terminal that detects the broadcast channel section to identify the femtocell of the femto base station within the macrocell.(String), 12.一种毫微微基站的通信方法,该方法包括:毫微微基站从宏基站接收宏基站宏小区中用于标识毫微微小区的广播信道段的报告;毫微微基站在广播信道段设置信号,报告宏小区内存在毫微微基站的毫微微小区;毫微微基站连接到检测广播信道段的移动终端,以在宏小区内识别毫微微基站的毫微微小区。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 13. The method of claim 12, further comprising setting, by the femto base station, the signal in the broadcast channel section to report existence of the femtocell of the femto base station within the macrocell upon receipt of the report about the broadcast channel section.(String), 13.如权利要求12所述的方法,还包括毫微微基站设置广播信道段中的信号,在收到广播信道段的报告后,报告宏小区内存在毫微微基站的毫微微小区。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185988(Integer), 14. A non-transitory computer-readable storage medium having stored therein program instructions to cause a processor to execute a communication method of a macro base station, the method comprising:reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell;receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section;generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal; andtransmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal.(String), 14.一种非暂时性计算机可读存储介质有存储在其中的程序指令使处理器执行宏基站的通信方法,该方法包括:向宏基站的宏小区中的至少一个毫微微基站上报宏小区中用于标识毫微微小区的广播信道段信息;当移动终端在广播信道部分识别出可访问的毫微微基站时,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求;基于移动终端的位置信息生成相邻毫微微基站的列表和关于相邻毫微微基站的信息;和将相邻毫微微基站的列表和相邻毫微微基站的信息发送给移动终端。(String), 0(Integer), 13(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185988(Integer), CROSS-REFERENCE TO RELATED APPLICATION(S) [0001]This application claims the benefit under 35 U.S.C. §119(a) of Korean Patent Application No. 10-2010-0055844, filed on Jun. 14, 2010, in the Korean Intellectual Property Office, the entire disclosure of which is incorporated herein by reference for all purposes. BACKGROUND [0002]1. Field [0003]The following description relates to a method of advertising to a mobile terminal connected to a femto base station, and a communication method of a mobile terminal, a femto base station, and a macro base station. [0004]2. Description of Related Art [0005]Femtocells may be classified into various types, for example, a personal femtocell that may be used to provide an ultrahigh speed transmission service within a predetermined area, a commercial femtocell to provide an advertisement service for sales promotion of a shop, and an authorized femtocell to provide a location service. Most femtocell applications focus on a user's convenience but do not sufficiently consider benefits to various installers and administrators. [0006]In a personal femtocell, a femtocell installer and an administrator may be substantially the same as a service beneficiary, and therefore, various administrative rights need not be distinguished. However, in a commercial femtocell, there is a need to distinguish the rights of a femtocell installer with those of a femtocell administrator in order to protect commercial rights. SUMMARY [0007]In one general aspect, there is provided a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell, receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section, generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal. [0008]The method may further comprise transmitting connection information to enable the mobile terminal to access a femto base station selected by the mobile terminal. [0009]The broadcast channel section may be set in a downlink broadcast channel of the macrocell at a preset cycle. [0010]The information about the neighbor femto base stations may comprise information about a shop in which each of the femto base stations is located or information about a discount policy of a connection service offered by each of the femto base stations. [0011]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a voice call transmitting signal transmitted from the mobile terminal, postponing transmission of the voice call transmitting signal, in response to the identification of the voice call transmitting signal, and offering a unique voice advertisement service of the femto base station, in response to the identification of the voice call transmitting signal. [0012]The method may further comprise identifying a ringback tone signal transmitted from a receiving side, and stopping the unique voice advertisement service of the femto base station in response to the identification of the ringback tone signal. [0013]In another aspect, there is provided a method of offering an advertisement to a mobile terminal connected to a femto base station, the method comprising identifying a data communication connection signal transmitted from the mobile terminal, postponing transmission of the data communication connection signal, in response to the identification of the data communication connection signal, and offering a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal. [0014]The method may further comprise identifying a data reception signal about a uniform resource locator (URL) address that the mobile terminal desires to access, and stopping the unique advertisement service of the femto base station, in response to the identification of the data reception signal. [0015]In another aspect, there is provided a communication method of a mobile terminal, the method comprising detecting a broadcast channel section used to identify a femtocell in a macrocell, identifying a femto base station accessible to the mobile terminal based on a measurement of an intensity of a signal of the broadcast channel section, transmitting, to a macro base station, position information of the mobile terminal and a request for information about the accessible femto base station, receiving a list of neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations from the macro base station, and selecting a femto base station based on the list and the information about the neighbor femto base stations. [0016]The detecting of the broadcast channel section is performed when a femtocell exploration mode of the mobile terminal is set to on. [0017]The indentifying of the accessible femto base station may perform by comparing a preset threshold value with the measured intensity of the signal of the broadcast channel section. [0018]The selected femto base station may be selected based on preferences of a user of the mobile terminal. [0019]The method may further comprise receiving connection information to enable access to the selected femto base station from the macro base station. [0020]The broadcast channel section may be set in a downlink broadcast channel of the macrocell at a preset cycle. [0021]The information about the neighbor femto base stations may comprise information about a shop in which the femto base stations are located, respectively, or comprises information about a discount policy of a connection service offered by each respective femto base station. [0022]In another aspect, there is provided a communication method of a femto base station, the method comprising receiving, from a macro base station, a report about a broadcast channel section used to identify a femtocell in a macrocell of the macro base station, and setting a signal in the broadcast channel section to report existence of a femtocell of the femto base station within the macrocell. [0023]In another aspect, there is provided a computer-readable storage medium having stored therein program instructions to cause a processor to execute a communication method of a macro base station, the method comprising reporting, to at least one femto base station in a macrocell of the macro base station, information about a broadcast channel section used to identify a femtocell in the macrocell, receiving from a mobile terminal position information of the mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, when the mobile terminal identifies an accessible femto base station in the broadcast channel section, generating a list of the neighbor femto base stations and information about the neighbor femto base stations based on the position information of the mobile terminal, and transmitting the list of the neighbor femto base stations and the information about the neighbor femto base stations to the mobile terminal. [0024]Other features and aspects may apparent from the following description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS [0025]FIG. 1 is a diagram illustrating an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0026]FIG. 2 is a diagram illustrating an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0027]FIG. 3 is a flowchart illustrating an example of a communication method of a macro base station. [0028]FIG. 4 is a flowchart illustrating an example of a communication method of a mobile terminal. [0029]FIG. 5 is a flowchart illustrating an example of a method of offering an advertisement to a mobile terminal connected to a femto base station. [0030]Throughout the drawings and the description, unless otherwise described, the same drawing reference numerals should be understood to refer to the same elements, features, and structures. The relative size and depiction of these elements may be exaggerated for clarity, illustration, and convenience. DESCRIPTION [0031]The following description is provided to assist the reader in gaining a comprehensive understanding of the methods, apparatuses, and/or systems described herein. Accordingly, various changes, modifications, and equivalents of the methods, apparatuses, and/or systems described herein may be suggested to those of ordinary skill in the art. Also, description of well-known functions and constructions may be omitted for increased clarity and conciseness. [0032]As described herein, a macrocell refers to a coverage area of a macro base station, and a femtocell refers to a coverage area of a femto base station. [0033]FIG. 1 illustrates an example of a network that allows a mobile terminal to identify and connect to a neighbor femtocell. [0034]Referring to FIG. 1, the network in which the mobile terminal identifies and connects to the neighbor femtocell includes a macro base station 101, two femto base stations 103, and a mobile terminal 105. It should be appreciated that the number of macro base stations, femto base stations, and mobile terminals are not limited to the example shown in FIG. 1. For example, the network may include one or more macro base stations, one or more femto base stations, and one or more mobile terminals. [0035]The macro base station coverage area includes a macrocell. The macro base station 101 sets up a broadcast channel section 109 within a downlink broadcast channel to identify a femtocell. The macro base station 101 reports the broadcast channel section 109 to at least one femto base station 103 in the macrocell. [0036]For example, the macro base station 101 may be linked with the femto base station 103 positioned in the macrocell, and maintain and renew a database including connection information. The connection information may include, for example, information about linked femto base stations 103, information about shops in which the linked femto base stations 103 are located, and the like. [0037]For example, the macro base station 101 may renew the database at a time when a femto base station 103 is added to the macrocell, at a preset time, or at any other desired time. [0038]The femto base stations 103 may offer various services, for example, real-time advertisements and event announcements of shops to the mobile terminal 105 as the user of the mobile terminal is within the coverage area of the femto base stations or passing by the shops in which the femto base stations 103 are located. [0039]For example, the femto base stations 103 may be linked with the macro base station 101 to attract customers passing by the shops in which the femto base stations 103 are located. The femto base stations 103 may be synchronized and linked with the macro base station 101. [0040]The mobile terminal 105 may set itself in a femtocell exploration mode to automatically identify a femtocell. For example, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 in order to identify a femtocell in the macrocell and identify whether there is a neighbor femtocell. During the femtocell exploration mode, the mobile terminal 105 may detect one or more femtocells corresponding to one or more femto base stations 103, which are within the macrocell of the macro base station 101 and are available for the mobile terminal 105 to connect with. [0041]The mobile terminal 105 may select a femto base station 103 from among the one or more detected femto base stations 103 based on a user preference of the mobile terminal 105 and/or information about neighbor femto base stations 103 received from the macro base station 101. Accordingly, the mobile terminal 105 may be provided with a unique advertisement service of the femto base station 103 while located within a femtocell of the femto base station 103. [0042]For example, the unique advertisement service of the femto base station 103 may include products sold by a shop in which the femto base station 103 is located, an advertisement for the shop, an advertisement service for an event held by the shop, and the like. [0043]As an example, when the shop in which the femto base station 103 is located is an ice cream shop, an advertisement service for the shop may include an advertisement for a new flavor of ice cream that may be purchased in the shop, discount information about products “on sale”, discount coupons, and the like. [0044]As described herein, when the femtocell exploration mode of the mobile terminal 105 is set to ‘ON,’ the mobile terminal 105 may detect the broadcast channel section 109 to identify a femtocell of a femto base station 103 located within the macrocell of the macro base station 101, and be provided with the a unique advertisement service of the femto base station 103. [0045]The broadcast channel section 109 used to identify the femtocell in the macrocell may be set at a preset cycle, for example, a cycle of a hundred milliseconds, two hundred milliseconds, five hundred milliseconds, or other desired amount of time. [0046]Hereinafter, a method including the macro base station 101, the femto base station 103, and the mobile terminal 105 in which the mobile terminal 105 identifies a neighbor femto base station 103 of the mobile terminal 105 and connect to the femto base station 103, is described. [0047]As indicated by reference numeral 110, the macro base station 101 reports information about the broadcast channel section 109 to the femtocell corresponding to at least one femto base station 103 in the macrocell. For example, the macro base station may report to one or more femto base stations 103. [0048]The femto base station 103 receiving a report about the broadcast channel section 109 from the macro base station 101 may set a signal in the broadcast channel section 109 in order to report the existence of the femtocell corresponding to the femto base station 103, as indicated by reference numeral 120. For example, the broadcast channel section 109 of the downlink broadcast channel may be set to a single bit or multiple bits. [0049]In 120, the femto base station 103 may set various types of signals in the broadcast channel section 109 to report the existence of the femtocell of the femto base station 103, for example, the femto base station 103 may set a particular bit of the broadcast channel section 109 to ‘1’ or set the broadcast channel section 109 to a dummy signal. [0050]When the femtocell exploration mode of the mobile terminal 105 is set to ON as indicated by reference numeral 130, the mobile terminal 105 may detect the broadcast channel section 109 to identify that the femtocell corresponding to the a femto base station 103 is within the macrocell corresponding to the macro base station 101. [0051]The mobile terminal 105 may identify a femto base station 103 accessible to the mobile terminal 105 from among the at least one femto base station 103 that is within the macrocell of the macro base station, based on a measurement result of an intensity of the signal of the broadcast channel section 109, in 140. [0052]For example, when the measurement result of the intensity of the signal in the broadcast channel section 109 is higher than a preset threshold value, the mobile terminal 105 may identify that there is at least one femto base station 103 neighboring the mobile terminal 105 and accessible to the mobile terminal 105. As another example, based on the intensity of the signal, the mobile terminal 105 may determine that a plurality of femto base stations are neighboring and available, for example, two femto base stations, three femto base stations, four femto base stations, or more femto base stations. The femto base station 103 may set a signal in the broadcast channel section 109 upon receiving the report about the broadcast channel section 109 from the macro base station 101. [0053]The mobile terminal 105 may transmit its position information to the macro base station 101, and may transmit a request to the macro base station 101 for information about the femto base station 103 which is accessible to the mobile terminal 105, in 150. [0054]For example, the macro base station 101 may generate a list of neighbor femto base stations 103 and information about the neighbor femto base stations 103 based on the position information of the mobile terminal 105 received from the mobile terminal 105, and may transmit the generated information to the mobile terminal 105, in 160. [0055]As an example, the information about the neighbor femto base stations 103 of the mobile terminal 105 may include information about a shop in which each of the respective femto base stations 103 is located or information about a discount policy of a connection service offered by each of the femto base stations 103. [0056]The mobile terminal 105 may select one femto base station 103 based on the list of the neighbor femto base stations 103 and the information about the neighbor femto base stations 103 received from the macro base station 101, in 170. [0057]In 170, the mobile terminal 105 may select the femto base station 103 in the list of the neighbor femto base stations 103 based on a user preference of the mobile terminal 105 and/or the information about the neighbor femto base stations 103 of the mobile terminal 105. [0058]An example of the list of the neighbor femto base stations 103 received from the macro base station 101 may include the following contents as shown in Table 1. [0059]TABLE 1Trans-Location ofFemto baseBusinessmissionBase stationstation IDcategoryPolicy for usespeedaACosmeticsfreeLowaBClothing10 cents/minHighaCEntertainmentfreeMediumaDFast food5 cent/minHigh(free whenreceivingadvertisements) [0060]In this example, the mobile terminal 105 receives information about four femto base stations A, B, C, and D neighboring the mobile terminal 105 from the macro base station 101. Accordingly, if a user of the mobile terminal 105 prefers a femto base station that provides a high transmittance speed and a free communication channel, the user of the mobile terminal 105 may select femto base station D to receive communication from. In other words, among the femto base stations B and D that provide a high transmittance speed and the femto base stations A, C, and D that provide a free communication channel, the mobile terminal 105 may automatically select or a user of the mobile terminal 105 may select the femto base station D which satisfies all user preferences. [0061]For example, the mobile terminal 105 may use the communication channel provided by the selected femto base station D. Further, the mobile terminal 105 may be provided with information about a shop in which the femto base station D is located or information about a discount policy of a connection service offered by the femto base station D from the femto base station D. [0062]In this example, the femto base station D corresponds to a femto base station of a fast food restaurant. Accordingly, the mobile terminal 105 may be provided with information about the fast food restaurant in which the femto base station D is located, information about a sales event offered by the fast food restaurant, coupons for discounts offered by the fast food restaurant, and an advertisement for the sales event. [0063]As another example, the mobile terminal 105 may select a femto base station 103 based on the interest of the user of the mobile terminal 105. For example, the mobile terminal 105 may select a femto base station 103 located in a shop of interest a shop offering a sales event, a shop providing a coupon of a product for a discount when receiving an advertisement service, and the like. [0064]As described above, the mobile terminal 105 may automatically select a femto base station 103 from the list by various methods. Depending on the femto base station 103 selected, the user of the mobile terminal 105 may be provided with an advertisement service from the femto base station 103. [0065]Further, the mobile terminal 105 itself may provide the list of the neighbor femto base stations 103 and information about their events to allow a user to select a femto base station 103. [0066]As another example, a femto base station 103 may be automatically selected by the macro base station 101. In yet other embodiments, the femto base station 103 may be automatically selected by the mobile terminal 105 based on predetermined settings or dynamically adjusted settings that may be dynamically set by a user. As yet another example, the femto base station 103 may be selected by a user of the mobile terminal 105. [0067]As another example, the macro base station 101 may store a user preference of the mobile terminal 105 and the information about the femto base stations 103 in advance, and selectively provide a femto base station 103 that satisfies the user preference based on stored information. [0068]For example, the macro base station 101 may include a database of information about the user preference of the mobile terminal 105 shown in the following Table 2. [0069]TABLE 2MobileTrans-InterestedterminalAgePolicy formissionbusinessIDgroupsusespeedcategoryOthersA20sFreeMediumCommunica-Selecting freetionof charge whenterminals,receivinggamesadvertisementsB30sFree/HighRestaurantsHigh trans-chargedmission speedC40sFreeMediumSports,Receivingbooksports-relatedstoresadvertisements [0070]The macro base station 101 may select the femto base stations that satisfy the user preferences of the mobile terminal 105 shown in Table 2 and provide them to the mobile terminal 105. [0071]After receiving the selection from the mobile terminal 105, the macro base station 101 may transmit connection information to the mobile terminal 105 to enable an access to the selected femto base station 103, in 180. [0072]The mobile terminal 105 may connect to the selected femto base station 103 using the connection information received from the macro base station 101, in 190. [0073]Accordingly, the mobile terminal 105 connected to the femto base station 103 may be provided with various communication services and advertisement services offered by the femto base station 103. [0074]For example, the advertisement services may include a unique voice advertisement service of the femto base station 103 and a unique display advertisement service of the femto base station 103. For example, the unique voice advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 inputs a telephone number and waits for a call to connect. [0075]As described herein, the unique advertisement service of the femto base station 103 may be provided to the mobile terminal 105 while the mobile terminal 105 waits for data reception about a uniform resource locator (URL) address which the mobile terminal 105 desires to access. [0076]FIG. 2 illustrates an example of a network that allows a femto base station to offer an advertisement to a mobile terminal connected to the femto base station. [0077]Referring to FIG. 2, the network for providing the advertisement to the mobile terminal includes a counterpart exchange station 201, a femto base station 203, a mobile terminal 205, and a receiving side mobile terminal 207. [0078]For example, a user in control of the mobile terminal 205 passing by a shop in which the femto base station 203 is located may attempt to call a friend by entering the phone number of a friend that corresponds to the receiving side mobile terminal 207, to try a call, in 210. [0079]In response to the call being placed by the user of the mobile terminal 205, the femto base station 203 identifies a voice call transmitting signal transmitted from the mobile terminal 205 based on the call being placed. Accordingly, the femto base station 203 may provide an advertisement to the mobile terminal 205 connected to the femto base station 203, and postpone transmission of the voice call transmitting signal in response to the identification of the voice call transmitting signal, in 220. [0080]For example, the femto base station 203 may include a voice call transmitting signal identification module that may identify the voice call transmitting signal transmitted from the mobile terminal 205. The femto base station 203 may offer a unique voice advertisement service of the femto base station 203 to the mobile terminal 205 in response to the identification of the voice call transmitting signal, in 230. [0081]The femto base station 203 forwards the postponed voice call transmitting signal to the counterpart exchange station 201, in 240. For example, the femto base station 203 may forward the postponed voice call transmitting signal after a predetermined amount of time elapses. [0082]For example, the femto base station 203 may identify a ringback tone signal transmitted from the receiving side mobile terminal 207, and accordingly, the femto base station 203 stops the unique voice advertisement service of the femto base station 203 in response to the identification of the ringback tone signal, in 250. [0083]After stopping the unique voice advertisement service of the femto base station 203, the femto base station 203 may forward the ringback tone signal to the mobile terminal 205 to connect a voice call, in 260. [0084]FIG. 3 illustrates an example of a communication method of a macro base station. [0085]Referring to FIG. 3, the macro base station reports information about a broadcast channel section to at least one femto base station in the macrocell, in 310. For example, the broadcast channel may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0086]The macro base station receives position information of a mobile terminal and a request for information about neighbor femto base stations of the mobile terminal, in 320. For example, the position information and the request for information may be transmitted from the mobile terminal when the mobile terminal identifies an accessible femto base station. [0087]The information about the neighbor femto base stations of the mobile terminal may include information about a shop in which each of the femto base stations is located. As another example, the information may include a discount policy of a connection service offered by each of the femto base stations. [0088]The macro base station generates a list of the neighbor femto base stations of the mobile terminal and information about the neighbor femto base stations of the mobile terminal based on the position information of the mobile terminal, in 330. [0089]The macro base station transmits the list of the neighbor femto base stations of the mobile terminal and the information about the neighbor femto base stations of the mobile terminal to the mobile terminal, in 340. [0090]In 350, the macro base station may transmit connection information to enable the mobile terminal access to a femto base station. [0091]The connection information to enable the mobile terminal access to the femto base station may be information about a femto base station selected by the mobile terminal from among the neighbor femto base stations of the mobile terminal in the list. [0092]FIG. 4 illustrates an example of a communication method of a mobile terminal [0093]Referring to FIG. 4, the mobile terminal may determine whether a femtocell exploration mode is set to ‘ON’, in 410. [0094]When the femtocell exploration mode is set to ‘ON,’ the mobile terminal detects a broadcast channel section to identify a femtocell, in 420. For example, the broadcast channel section may be set in the downlink broadcast channel of the macrocell at a preset cycle. [0095]As a result of the determination in 410, if the femtocell exploration mode is not set to ‘ON,’ or the mobile terminal does not have a femtocell exploration function, the mobile terminal may finish the process without performing subsequent operations. [0096]The mobile terminal identifies a femto base station accessible to the mobile terminal based on a measurement of an intensity of a signal of the broadcast channel section in order to identify the femtocell in the macrocell. For example, the mobile terminal may measure the intensity of the signal of the broadcast channel section to identify the femtocell and compare the measurement result with a preset threshold value, in 440. [0097]When the intensity of the signal of the broadcast channel section measured in 440 is higher than the preset threshold value, the mobile terminal may identify that the femto base station is accessible to the mobile terminal, in 450. [0098]The mobile terminal transmits, to a macro base station, its position information and a request for information about the accessible femto base station, in 460. The mobile terminal receives the requested information from the macro base station, in 470. For example, the information received from the macro base station may include a list of neighbor femto base stations of the mobile terminal and information about them. For example, the list and the information may be generated based on the position information of the mobile terminal. As an example, the information about the neighbor femto base stations may include information about a shop in which each of the femto base stations is located or include information about a discount policy of a connection service offered by each of the femto base stations. [0099]The mobile terminal may select a femto base station based on the list of the neighbor femto base stations and the information about them, in 480. For example, the mobile terminal may use a preference of a user of the mobile terminal and the information about the neighbor femto base stations in selecting a femto base station. [0100]FIG. 5 illustrates an example of a method of offering an advertisement to a mobile terminal connected to a femto base station. [0101]Referring to FIG. 5, when the mobile terminal inputs a data communication connection signal such as a URL address which the mobile terminal desires to access, the femto base station identifies the data communication connection signal transmitted from the mobile terminal, in 510. [0102]The femto base station postpones transmission of the data communication connection signal in response to the identification of the data communication connection signal, in 520. [0103]The femto base station offers a unique advertisement service of the femto base station to the mobile terminal, in response to the identification of the data communication connection signal, in 530. And, after a lapse of a predetermined amount of time, For example, the femto base station may forward the postponed data communication connection signal to an internet server in operation. [0104]In 540, the femto base station identifies a data reception signal about the URL address which the mobile terminal desires to access. For example, the femto base station may include a functional module to identify a data reception signal such as a homepage or a URL address which the mobile terminal desires in order to identify the data reception signal. [0105]The femto base station may stop a unique advertisement service in response to the identification of the data reception signal about the URL address which the mobile terminal desires to access, in 550. The femto base station may forward the data reception signal about the URL address to the mobile terminal for connection. [0106]As described herein, the mobile terminal may include various modes such as a femtocell exploration mode. However, it should be appreciated that the mobile terminal may only have one mode in which the mobile terminal constantly searches for an available femtocell. [0107]As a non-exhaustive illustration only, the terminal device described herein may refer to mobile devices such as a cellular phone, a(String), 相关申请的交叉引用 [0001] 此申请根据 35 U.S.C. 2010 年 6 月 14 日向韩国知识产权局提交的韩国专利申请号 10-2010-0055844 的§119(a),其全部公开内容通过引用并入本文用于所有目的。 背景 [0002] 1. 领域 [0003] 以下描述涉及向连接到毫微微基站的移动终端进行广告的方法,以及移动终端、毫微微基站和宏基站的通信方法。 [0004] 2.相关技术说明 [0005] 毫微微蜂窝可以分为多种类型,例如,可用于在预定区域内提供超高速传输服务的个人毫微微蜂窝、用于为商店促销提供广告服务的商业毫微微蜂窝以及授权毫微微蜂窝以 提供定位服务。 大多数毫微微蜂窝应用关注用户的便利性,但没有充分考虑对各种安装人员和管理员的好处。 [0006] 在个人毫微微小区中,毫微微小区安装者和管理员可以作为服务受益人实质上相同,因此不需要区分各种管理权限。 然而,在商业毫微微小区中,需要区分毫微微小区安装者和毫微微小区管理员的权利,以保护商业权利。 概括 [0007] 在一个一般方面,提供了一种宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告关于用于识别毫微微小区中的毫微微小区的广播信道部分的信息。 宏小区,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,当移动终端在广播信道部分中识别出可接入的毫微微基站时,生成该移动终端的列表 相邻毫微微基站和相邻毫微微基站的信息基于移动终端的位置信息,将相邻毫微微基站列表和相邻毫微微基站信息发送给移动终端。 [0008] 该方法还可以包括发送连接信息以使移动终端能够接入由移动终端选择的毫微微基站。 [0009] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0010] 关于相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于每个毫微微基站提供的连接服务的折扣政策的信息。 [0011] 在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的语音呼叫发送信号,延迟语音呼叫发送信号的发送,作为响应 对语音呼叫发射信号的识别,并响应语音呼叫发射信号的识别,提供毫微微基站的独特的语音广告服务。 [0012] 该方法还可以包括识别从接收侧发送的回铃音信号,并且响应于回铃音信号的识别停止毫微微基站的唯一语音广告服务。 [0013] 在另一方面,提供了一种向连接到毫微微基站的移动终端提供广告的方法,该方法包括识别从移动终端发送的数据通信连接信号,作为响应推迟数据通信连接信号的发送 对数据通信连接信号的识别进行响应,并响应于数据通信连接信号的识别,向移动终端提供毫微微基站的唯一广告服务。 [0014] 该方法还可以包括识别关于移动终端期望访问的统一资源定位符(URL)地址的数据接收信号,并且响应于数据接收信号的识别停止毫微微基站的唯一广告服务。 [0015] 在另一方面,提供了一种移动终端的通信方法,该方法包括检测用于识别宏小区中的毫微微小区的广播信道部分,基于对移动终端的强度的测量来识别移动终端可接入的毫微微基站。 广播信道部分的信号,向宏基站发送移动终端的位置信息和对关于可访问的毫微微基站的信息的请求,接收移动终端的相邻毫微微基站的列表和关于移动终端的信息 从宏基站中选择相邻毫微微基站,并基于列表和关于相邻毫微微基站的信息来选择毫微微基站。 [0016] 当移动终端的毫微微小区探索模式设置为开启时,执行广播信道部分的检测。 [0017] 可接入毫微微基站的识别可以通过将预设阈值与广播信道部分的信号的测量强度进行比较来执行。 [0018] 可以基于移动终端的用户的偏好来选择所选择的毫微微基站。 [0019] 该方法还可以包括接收连接信息以使得能够从宏基站接入所选择的毫微微基站。 [0020] 广播信道段可以按预设周期设置在宏小区的下行广播信道中。 [0021] 关于相邻毫微微基站的信息可以包括关于毫微微基站分别位于的商店的信息,或者包括关于各个毫微微基站提供的连接服务的折扣政策的信息。 [0022] 在另一方面,提供了一种毫微微基站的通信方法,该方法包括从宏基站接收关于用于识别宏基站的宏小区中的毫微微小区的广播信道部分的报告,以及设置 广播信道部分中的信号,用于报告宏小区内的毫微微基站的毫微微小区的存在。 [0023] 在另一方面,提供了一种其中存储有程序指令的计算机可读存储介质,以使处理器执行宏基站的通信方法,该方法包括向宏基站的宏小区中的至少一个毫微微基站报告。 宏基站,关于用于识别宏小区中的毫微微小区的广播信道部分的信息,从移动终端接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,当移动终端识别 广播信道部分中可接入的毫微微基站,基于移动终端的位置信息生成相邻毫微微基站列表和相邻毫微微基站的信息,并发送相邻毫微微基站列表和 向移动终端发送有关相邻毫微微基站的信息。 [0024] 从以下描述、附图和权利要求中,其他特征和方面可能是显而易见的。 附图的简要说明 [0025] 如图。 附图说明图1是图示允许移动终端识别并连接到相邻毫微微小区的网络的示例的图。 [0026] 如图。 图2是图示允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例的图。 [0027] 如图。 图3是图示宏基站的通信方法的示例的流程图。 [0028] 如图。 图4是图示移动终端的通信方法的示例的流程图。 [0029]如图。 图5是示出向连接到毫微微基站的移动终端提供广告的方法的示例的流程图。 [0030] 在整个附图和描述中,除非另有说明,相同的附图标记应被理解为指代相同的元件、特征和结构。 为了清楚、说明和方便起见,这些元素的相对大小和描述可能会被夸大。 描述 [0031] 提供以下描述以帮助读者获得对本文描述的方法、装置和/或系统的全面理解。 因此,可以向本领域普通技术人员建议本文描述的方法、装置和/或系统的各种改变、修改和等效物。 此外,为了更清楚和简明,可以省略对众所周知的功能和结构的描述。 [0032] 如本文所述,宏小区是指宏基站的覆盖区域,毫微微小区是指毫微微基站的覆盖区域。 [0033] 如图。 图1图示了允许移动终端识别并连接到相邻毫微微小区的网络的示例。 [0034] 参考图。 参照图1,移动终端识别并连接到相邻毫微微小区的网络包括宏基站 101 , 两个毫微微基站 103 , 和一个移动终端 105 . 应当理解,宏基站、毫微微基站和移动终端的数量不限于图1所示的示例。 1、例如,网络可以包括一个或多个宏基站、一个或多个毫微微基站、以及一个或多个移动终端。 [0035] 宏基站覆盖区域包括宏小区。 宏基站 101 设置广播频道部分 109 在下行链路广播信道内识别毫微微小区。 宏基站 101 报告广播频道部分 109 到至少一个毫微微基站 103 在宏单元中。 [0036] 例如宏基站 101 可与毫微微基站链接 103 定位在宏单元中,并维护和更新包括连接信息的数据库。 连接信息可以包括例如关于链接的毫微微基站的信息 103 ,有关链接的毫微微基站的商店的信息 103 位于,等等。 [0037] 例如宏基站 101 可以在毫微微基站更新数据库时 103 在预设时间,或在任何其他所需时间,将其添加到宏小区。 [0038] 毫微微基站 103 可以向移动终端提供各种服务,例如商店的实时广告和活动公告 105 当移动终端的用户在毫微微基站的覆盖范围内或经过毫微微基站所在的商店时 103 位于。 [0039] 例如,毫微微基站 103 可与宏基站联动 101 吸引经过femto基站所在商店的顾客 103 位于。 毫微微基站 103 可与宏基站同步链接 101 . [0040] 移动终端 105 可以将自身设置为femtocell探索模式以自动识别femtocell。 例如,当移动终端的femtocell探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 以识别宏小区中的毫微微小区,并识别是否有相邻毫微微小区。 在femtocell探索模式下,移动终端 105 可以检测对应于一个或多个毫微微基站的一个或多个毫微微小区 103 ,在宏基站的宏小区内 101 并且可用于移动端 105 连接。 [0041] 移动终端 105 可以选择一个毫微微基站 103从一个或多个检测到的毫微微基站中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 从宏基站接收 101 . 因此,移动终端 105 可以提供femto基站的独特广告服务 103 当位于毫微微基站的毫微微小区内时 103 . [0042] 例如,femto 基站的独特广告服务 103 可能包括由 Femto 基站所在的商店销售的产品 103 定位,商店的广告,商店举办的活动的广告服务等。 [0043] 例如,当 femto 基站所在的商店 103 如果位于冰淇淋店,则该店的广告服务可以包括可在该店购买的新口味冰淇淋的广告、“特价”产品的折扣信息、折扣券等。 [0044] 如本文所述,当移动终端的毫微微小区探索模式 105 设置为“ON”,移动终端 105 可以检测广播频道部分 109 识别毫微微基站的毫微微小区 103 位于宏基站的宏小区内 101 ,并获得femto基站独有的广告服务 103 . [0045] 广播频道部分 109 用于识别宏小区中的毫微微小区可以设置为预设周期,例如一百毫秒、两百毫秒、五百毫秒或其他所需时间量的周期。 [0046] 在下文中,一种包括宏基站的方法 101 , 毫微微基站 103 , 和移动终端 105 其中移动端 105 识别相邻的毫微微基站 103 移动终端的 105 并连接到 femto 基站 103 , 被描述。 [0047] 如参考数字所示 110 , 宏基站 101 报告有关广播频道部分的信息 109 至对应于至少一毫微微基站的毫微微小区 103 在宏单元中。 例如,宏基站可以向一个或多个毫微微基站报告 103 . [0048] 毫微微基站 103 接收有关广播频道部分的报告 109 从宏基站 101 可以在广播频道部分设置信号 109 为了上报femto基站对应的femtocell的存在 103 ,如参考数字所示 120 . 例如,广播频道部分 109 下行广播信道可以设置为单个比特或多个比特。 [0049] 在 120 , 毫微微基站 103 可以在广播频道部分设置各种类型的信号 109 报告femto基站的femtocell存在 103 ,例如,毫微微基站 103 可以设置广播频道部分的特定位 109 为“1”或设置广播频道部分 109 到一个虚拟信号。 [0050] 当移动终端的femtocell探索模式 105 如附图标记所示,设置为 ON 130 , 移动端 105 可以检测广播频道部分 109 识别该毫微微基站对应的毫微微小区 103 在宏基站对应的宏小区内 101 . [0051] 移动终端 105 可以识别毫微微基站 103 移动端可访问 105 从至少一个毫微微基站中 103 在宏基站的宏小区内,基于广播信道部分的信号强度的测量结果 109 , 在 140 . [0052]例如,当广播频道部分的信号强度测量结果 109 高于预设阈值,移动终端 105 可以识别存在至少一个毫微微基站 103 靠近移动终端 105 移动端可访问 105 . 又例如,基于信号的强度,移动终端 105 可以确定多个毫微微基站相邻且可用,例如,两个毫微微基站、三个毫微微基站、四个毫微微基站或更多毫微微基站。 毫微微基站 103 可以在广播频道部分设置信号 109 在收到有关广播频道部分的报告后 109 从宏基站 101 . [0053] 移动终端 105 可以将其位置信息发送到宏基站 101 ,并且可以向宏基站发送请求 101 有关 femto 基站的信息 103 移动终端可以访问的 105 , 在 150 . [0054] 例如宏基站 101 可以生成相邻毫微微基站的列表 103 以及有关相邻毫微微基站的信息 103 基于移动终端的位置信息 105 从移动终端接收 105 ,并且可以将生成的信息发送到移动终端 105 , 在 160 . [0055] 例如,有关相邻毫微微基站的信息 103 移动终端的 105 可以包括关于商店的信息,其中每个相应的毫微微基站 103 位置或有关每个毫微微基站提供的连接服务的折扣政策的信息 103 . [0056] 移动终端 105 可选择一个毫微微基站 103 基于相邻毫微微基站列表 103 以及有关相邻毫微微基站的信息 103 从宏基站接收 101 , 在 170 . [0057] 在 170 , 移动端 105 可选择femto基站 103 在相邻毫微微基站列表中 103 基于移动终端的用户偏好 105 和/或有关相邻毫微微基站的信息 103 移动终端的 105 . [0058] 相邻毫微微基站列表的示例 103 从宏基站接收 101 可包括以下内容,如表 1 所示。 [0059] 表格1 反式 位置 毫微微基站 商业 使命 基站 站号 类别 使用政策 速度 a A 化妆品 自由的 低的 a B 衣服 10 美分/分钟 高的 a C 娱乐 自由的 中等的 a D 快餐 5 分/分钟 高的 (免费时 接收 广告) [0060] 在这个例子中,移动终端 105 接收与移动终端相邻的四个毫微微基站 A、B、C 和 D 的信息 105 从宏基站 101 . 因此,如果移动终端的用户 105 移动终端的用户更喜欢提供高传输速度和免费通信信道的毫微微基站 105 可以选择毫微微基站D来接收通信。 换言之,在提供高传输速度的毫微微基站B和D以及提供自由通信信道的毫微微基站A、C和D中,移动终端 105 可自动选择或移动终端的用户 105 可以选择满足所有用户偏好的毫微微基站D。 [0061] 例如,移动终端 105 可以使用由选择的毫微微基站D提供的通信信道。此外,移动终端 105 可以提供关于毫微微基站D所在的商店的信息或者关于毫微微基站D从毫微微基站D提供的连接服务的折扣政策的信息。 [0062] 在该示例中,毫微微基站D对应于快餐店的毫微微基站。 因此,移动终端 105可以提供关于毫微微基站D所在的快餐店的信息、关于快餐店提供的销售活动的信息、快餐店提供的折扣券以及销售活动的广告。 [0063] 再举一个例子,移动终端 105 可以选择一个毫微微基站 103 基于移动终端用户的兴趣 105 . 例如,移动终端 105 可以选择一个毫微微基站 103 位于感兴趣的商店中、提供销售活动的商店、在接收广告服务时提供产品优惠券以获得折扣的商店等。 [0064] 如上所述,移动终端 105 可以自动选择一个毫微微基站 103 通过各种方法从列表中。 取决于毫微微基站 103 选中,移动端的用户 105 可以从毫微微基站提供广告服务 103 . [0065] 此外,移动终端 105 本身可以提供相邻毫微微基站的列表 103 以及有关其事件的信息,以允许用户选择毫微微基站 103 . [0066] 作为另一个示例,毫微微基站 103 可由宏基站自动选择 101 . 在又一些实施例中,毫微微基站 103 可由移动端自动选择 105 基于可以由用户动态设置的预定设置或动态调整的设置。 作为又一示例,毫微微基站 103 可由移动终端的用户选择 105 . [0067] 再举一个例子,宏基站 101 可以存储移动终端的用户偏好 105 以及有关femto基站的信息 103 提前,并有选择地提供一个毫微微基站 103 根据存储的信息满足用户偏好。 [0068] 例如宏基站 101 可以包括关于移动终端的用户偏好的信息数据库 105 如下表2所示。 [0069] 表 2 移动的 反式 感兴趣的 终端 年龄 政策 使命 商业 ID 团体 利用 速度 类别 其他 A 20s 自由的 中等的 通讯—— 自由选择 化 收费时 终端, 接收 游戏 广告 B 30s 自由的/ 高的 餐厅 高反式 带电 任务速度 C 40s 自由的 中等的 运动的, 接收 书 运动相关 商店 广告 [0070] 宏基站 101 可选择满足移动终端用户偏好的毫微微基站 105 如表 2 所示,并提供给移动终端 105 . [0071] 收到手机端的选择后 105 , 宏基站 101 可以向移动终端发送连接信息 105 启用对所选毫微微基站的访问 103 , 在 180 . [0072] 移动终端 105 可以连接到选定的毫微微基站 103 使用从宏基站接收到的连接信息 101 , 在 190 . [0073] 因此,移动终端 105 连接到毫微微基站 103 可以提供由毫微微基站提供的各种通信服务和广告服务 103 . [0074] 例如,广告服务可以包括毫微微基站的独特语音广告服务 103 以及femto基站独有的展示广告服务 103 . 例如,femto 基站独有的语音广告服务 103 可提供给移动终端 105 而移动端 105 输入电话号码并等待呼叫接通。 [0075] 如本文所述,毫微微基站的独特广告服务 103 可提供给移动终端 105 而移动端 105 等待关于移动终端的统一资源定位符(URL)地址的数据接收 105 渴望访问。 [0076] 如图。 图2图示了允许毫微微基站向连接到毫微微基站的移动终端提供广告的网络的示例。 [0077] 参考图。 参照图2,用于向移动终端提供广告的网络包括对方交换站 201 , 一个毫微微基站 203 , 移动终端 205 ,以及接收方移动终端 207 . [0078] 例如,控制移动终端的用户 205 路过一家有femto基站的商店 203 定位到可以尝试通过输入与接收方移动终端对应的朋友的电话号码来呼叫朋友 207 , 尝试通话,在 210 . [0079] 响应移动终端用户的呼叫 205 , 毫微微基站 203 识别移动终端发送的语音呼叫发送信号 205 根据正在拨打的电话。 因此,毫微微基站 203 可以向移动终端提供广告 205 连接到毫微微基站 203 ,并且响应于语音呼叫发射信号的识别延迟语音呼叫发射信号的传输,在 220 . [0080] 例如,毫微微基站 203 可以包括语音呼叫发送信号识别模块,其可以识别从移动终端发送的语音呼叫发送信号 205 . 毫微微基站 203 可以提供femto基站独特的语音广告服务 203 到移动终端 205 响应语音呼叫发射信号的识别,在 230 . [0081] 毫微微基站 203 将延迟的语音呼叫发射信号转发给对方交换台 201 , 在 240 . 例如,毫微微基站 203 可以在经过预定时间量之后转发延迟的语音呼叫发送信号。 [0082] 例如,毫微微基站 203 可以识别从接收侧移动终端发送的回铃音信号 207 ,因此,毫微微基站 203 停止femto基站独有的语音广告服务 203 响应回铃音信号的识别,在 250 . [0083] 停止femto基站的独特语音广告服务后 203 , 毫微微基站 203 可以将回铃音信号转发给移动终端 205 连接语音通话,在 260 . [0084] 如图。 图3图示了宏基站的通信方法的示例。 [0085] 参考图。 参照图3,宏基站向宏小区中的至少一个毫微微基站报告关于广播信道部分的信息,在 310 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道。 [0086] 宏基站接收移动终端的位置信息和关于移动终端的相邻毫微微基站的信息的请求,在 320 . 例如,当移动终端识别出可接入的毫微微基站时,可以从移动终端发送位置信息和信息请求。 [0087] 关于移动终端的相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息。 作为另一示例,该信息可以包括由每个毫微微基站提供的连接服务的折扣政策。 [0088] 宏基站根据移动终端的位置信息生成移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息,在 330 . [0089] 宏基站将移动终端的相邻毫微微基站列表和移动终端的相邻毫微微基站的信息发送给移动终端,在 340 . [0090] 在 350,宏基站可以发送连接信息以使移动终端能够接入毫微微基站。 [0091] 使移动终端能够接入毫微微基站的连接信息可以是关于移动终端从列表中的移动终端的相邻毫微微基站中选择的毫微微基站的信息。 [0092] 如图。 图4图示了移动终端的通信方法的示例 [0093] 参考图。 4、移动终端可以判断毫微微小区探索模式是否设置为“开启”,在 410 . [0094] 当毫微微小区探索模式设置为“开启”时,移动终端检测广播信道部分以识别毫微微小区,在 420 . 例如,可以在宏小区的下行广播信道中以预设的周期设置广播信道段。 [0095] 作为确定的结果 410 ,如果femtocell探索模式未设置为“ON”,或者移动终端不具备femtocell探索功能,则移动终端可以不执行后续操作而完成该过程。 [0096] 移动终端基于广播信道部分的信号强度的测量来识别移动终端可接入的毫微微基站,以便识别宏小区中的毫微微小区。 例如,移动终端可以测量广播信道部分的信号强度以识别毫微微小区并将测量结果与预设阈值进行比较,在 440 . [0097] 当测量的广播频道部分的信号强度 440 高于预设阈值,移动终端可以识别出该毫微微基站可接入移动终端,在 450 . [0098] 移动终端向宏基站发送其位置信息和对关于可接入毫微微基站的信息的请求,在 460 . 移动终端从宏基站接收请求的信息,在 470 . 例如,从宏基站接收的信息可以包括移动终端的相邻毫微微基站的列表以及关于它们的信息。 例如,可以基于移动终端的位置信息来生成列表和信息。 作为示例,关于相邻毫微微基站的信息可以包括关于每个毫微微基站所在的商店的信息或者关于由每个毫微微基站提供的连接服务的折扣策略的信息。 [0099] 移动终端可以基于相邻毫微微基站的列表和关于它们的信息来选择毫微微基站,在 480 . 例如,移动终端可以在选择毫微微基站时使用移动终端用户的偏好和关于相邻毫微微基站的信息。 [0100] 如图。 图5图示了向连接到毫微微基站的移动终端提供广告的方法的示例。 [0101] 参考图。 参照图5,当移动终端输入移动终端希望访问的URL地址等数据通信连接信号时,毫微微基站识别从移动终端发送的数据通信连接信号,在 510 . [0102] 毫微微基站响应于数据通信连接信号的识别延迟数据通信连接信号的传输,在 520 . [0103] 毫微微基站响应数据通信连接信号的识别,向移动终端提供独特的毫微微基站广告服务,在 530 . 并且,在预定量的时间过去之后,例如,毫微微基站可以将延迟的数据通信连接信号转发到运行中的互联网服务器。 [0104] 在 540,毫微微基站识别关于移动终端希望访问的URL地址的数据接收信号。 例如,毫微微基站可以包括功能模块,以识别移动终端期望的诸如主页或URL地址的数据接收信号以便识别数据接收信号。 [0105] 毫微微基站可以响应于识别关于移动终端期望访问的URL地址的数据接收信号来停止唯一的广告服务,在 550 . 毫微微基站可以将关于URL地址的数据接收信号转发给移动终端进行连接。 [0106] 如本文所述,移动终端可以包括各种模式,例如毫微微小区探索模式。 然而,应当理解,移动终端可能只有一种模式,其中移动终端不断地搜索可用的毫微微小区。 [0107] 仅作为非穷举说明,此处描述的终端设备可以指移动设备,例如蜂窝电话、个人数字助理(PDA)、数码相机、便携式游戏机、MP3播放器、便携式/个人多媒体 播放器 (PMP)、手持电子书、便携式实验室个人计算机 (PC)、全球定位系统 (GPS) 导航,以及台式 PC、高清电视 (HDTV)、光盘等设备 播放器、设置盒等,能够进行与本文所公开的一致的无线通信或网络通信。 [0108] 计算系统或计算机可以包括与总线电连接的微处理器、用户接口和存储器控制器。 它还可以包括闪存设备。 闪存设备可以通过存储控制器存储N位数据。 N位数据由微处理器处理或将由微处理器处理,N可以为1或大于1的整数。当计算系统或计算机为移动设备时,可额外提供电池以提供计算的工作电压 系统或计算机。 [0109] 对于本领域的普通技术人员来说,计算系统或计算机还可以包括应用芯片组、相机图像传感器(CIS)、移动动态随机存取存储器(DRAM)等应该是显而易见的。 存储器控制器和闪存设备可以构成使用非易失性存储器来存储数据的固态驱动器/磁盘(SSD)。 [0110] 上述过程、功能、方法和/或软件可以被记录、存储或固定在一个或多个计算机可读存储介质中,该存储介质包括要由计算机实现以使处理器执行或执行程序的程序指令 指示。 媒体还可以单独或与程序指令、数据文件、数据结构等组合地包括。 计算机可读存储介质的示例包括诸如硬盘、软盘和磁带之类的磁介质; 光媒体,如 CD ROM 盘和 DVD; 磁光介质,例如光盘; 以及专门用于存储和执行程序指令的硬件设备,例如只读存储器(ROM)、随机存取存储器(RAM)、闪存等。 程序指令的示例包括机器代码(例如由编译器生成)和包含可以由计算机使用解释器执行的更高级别代码的文件。 所描述的硬件设备可以被配置为充当一个或多个软件模块以执行上述操作和方法,反之亦然。 此外,计算机可读存储介质可以分布在通过网络连接的计算机系统之间,并且可以以分散方式存储和执行非暂时性计算机可读代码或程序指令。 [0111]上面已经描述了许多示例。 然而,应该理解可以进行各种修改。 例如,如果以不同的顺序执行所描述的技术和/或如果所描述的系统、架构、设备或电路中的组件以不同的方式组合和/或由其他组件替换或补充或 他们的等价物。 因此,其他实施方式在所附权利要求的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:29.856 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8548504B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101622169B1(String), KR1020110136068A(String), US20110306324A1(String), US20130346212A1(String), US8548504B2(String), WO2011159010A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 6 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271664(Integer), KR101622169B1(String), 1049765(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271664(Integer), KR1020110136068A(String), 1049766(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271664(Integer), US20110306324A1(String), 1049767(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271664(Integer), US20130346212A1(String), 1049768(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271664(Integer), US8548504B2(String), 1049769(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271664(Integer), WO2011159010A1(String), 1049770(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8548504B2(String), US8548504B2(String), 1380556800(Integer), 271664(Integer), 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 271654(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 271654(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.441 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.442 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.442 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185988(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.508 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185988(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185988(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185988(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.646 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.647 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.682 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185988(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:30.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.303 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.303 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.303 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Integrated content file search method for mobile terminal and mobile terminal implementing the same(String), 移动终端集成内容文件搜索方法及实现该方法的移动终端(String), US20080010261A1(String), An integrated content file search method for a mobile terminal and a mobile terminal implementing the same are provide, in which content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and selection of one of the found content files causes immediate execution of the selected content file. A search mode for a content file search is set, a search string from a user is input, the input search string is displayed on a display unit of the mobile terminal, the text entry of content files stored in the mobile terminal are accessed, the text entry is verified to determine whether the text entry contains the input search string, a textual excerpt from the text entry containing the input search string is displayed on the display unit, and a content file that contains the displayed textual excerpt is executed.(String), 提供了一种移动终端集成内容文件搜索方法及实现该方法的移动终端,以集成的方式搜索移动终端中分层或非分层结构存储的内容文件,并选择其中一个。 找到的内容文件会立即执行选定的内容文件。 设置内容文件搜索的搜索模式,输入来自用户的搜索字符串,输入的搜索字符串显示在移动终端的显示单元上,访问存储在移动终端中的内容文件的文本条目, 验证文本条目以确定该文本条目是否包含输入搜索字符串,将包含输入搜索字符串的文本条目的文本摘录显示在显示单元上,并执行包含显示的文本摘录的内容文件。(String), US11/812880(String), 1182441600(Integer), US20080010261A1(String), 1199894400(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 5(Integer), US20050037816A1 | US20060047644A1 | US20070255785A1 | US6405060B1 | US6990180B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185989(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\eacb06a3d8984e4493127516aa0ebae3.png(String), 185989(Integer), eacb06a3d8984e4493127516aa0ebae3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.522 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.522 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.522 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Integrated content file search method for mobile terminal and mobile terminal implementing the same(String), 移动终端集成内容文件搜索方法及实现该方法的移动终端(String), US20080010261A1(String), An integrated content file search method for a mobile terminal and a mobile terminal implementing the same are provide, in which content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and selection of one of the found content files causes immediate execution of the selected content file. A search mode for a content file search is set, a search string from a user is input, the input search string is displayed on a display unit of the mobile terminal, the text entry of content files stored in the mobile terminal are accessed, the text entry is verified to determine whether the text entry contains the input search string, a textual excerpt from the text entry containing the input search string is displayed on the display unit, and a content file that contains the displayed textual excerpt is executed.(String), 提供了一种移动终端集成内容文件搜索方法及实现该方法的移动终端,以集成的方式搜索移动终端中分层或非分层结构存储的内容文件,并选择其中一个。 找到的内容文件会立即执行选定的内容文件。 设置内容文件搜索的搜索模式,输入来自用户的搜索字符串,输入的搜索字符串显示在移动终端的显示单元上,访问存储在移动终端中的内容文件的文本条目, 验证文本条目以确定该文本条目是否包含输入搜索字符串,将包含输入搜索字符串的文本条目的文本摘录显示在显示单元上,并执行包含显示的文本摘录的内容文件。(String), US11/812880(String), 1182441600(Integer), US20080010261A1(String), 1199894400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 5(Integer), US20050037816A1 | US20060047644A1 | US20070255785A1 | US6405060B1 | US6990180B2(String), \20230420\eacb06a3d8984e4493127516aa0ebae3.png(String), 14(Integer), 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 1. An integrated content file search method for a mobile terminal, the method comprising:setting a search mode for a content file search;inputting a search string;displaying the input search string on a display unit;accessing a text entry of stored content files;verifying the text entry to determine whether the text entry contains the input search string;displaying a textual excerpt from the text entry containing the input search string on the display unit; andexecuting a content file that contains the displayed textual excerpt.(String), 1.一种移动终端综合内容文件搜索方法,该方法包括:设置内容文件搜索的搜索模式;输入搜索字符串;在显示单元上显示输入的搜索字符串;访问存储的内容文件的文本条目;验证文本条目以确定文本条目是否包含输入的搜索字符串;在显示单元上显示来自包含输入搜索字符串的文本条目的文本摘录;和执行包含显示的文本摘录的内容文件。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 2. The integrated content file search method of claim 1, wherein the text entry of the stored content files includes a list of file subjects on the content files.(String), 2.如权利要求1所述的综合内容文件搜索方法,其中存储的内容文件的文本条目包括内容文件的文件主题列表。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 3. The integrated content file search method of claim 1, wherein the text entry of the stored content files includes textual contents of the content files.(String), 3.如权利要求1所述的综合内容文件搜索方法,其中存储的内容文件的文本条目包括内容文件的文本内容。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 4. The integrated content file search method of claim 1, wherein the displaying of the textual excerpt comprising displaying a textual excerpt of the corresponding content file is displayed together with an icon indicating the content file.(String), 4.如权利要求1所述的综合内容文件搜索方法,其中文本摘录的显示包括显示相应内容文件的文本摘录,连同指示内容文件的图标一起显示。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 5. The integrated content file search method of claim 4, further comprising selecting an icon to execute the content file associated with the icon.(String), 5.如权利要求4所述的综合内容文件搜索方法,还包括选择图标以执行与该图标关联的内容文件。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 6. The integrated content file search method of claim 4, wherein the icon comprises an avatar.(String), 6.如权利要求4所述的综合内容文件搜索方法,其中该图标包括一个化身。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 7. The integrated content file search method of claim 1, wherein the content files comprises at least one of phone book files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files and game program files.(String), 7.如权利要求1所述的综合内容文件搜索方法,其中内容文件包括电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静态图片文件、运动图片文件和游戏程序文件中的至少一种。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 8. A mobile terminal comprising:a key input unit for setting a search mode for a content file search and inputting a search string;a display unit for displaying the input search string;a controller for accessing a text entry of content files, verifying the text entry to determine whether the text entry contains the input search string, displaying a textual excerpt from the text entry containing the input search string, and executing a content file that contains the textual excerpt.(String), 8.移动终端包括:键输入单元,用于设置内容文件搜索的搜索模式并输入搜索字符串;显示单元,用于显示输入的搜索字符串;控制器,用于访问内容文件的文本条目,验证文本条目以确定文本条目是否包含输入搜索字符串,显示来自包含输入搜索字符串的文本条目的文本摘录,以及执行包含文本的内容文件摘抄。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 9. The mobile terminal of claim 8, wherein the text entry of content files comprises a list of file subjects on the content files.(String), 9.如权利要求8所述的移动终端,其中内容文件的文本条目包括内容文件上的文件主题列表。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 10. The mobile terminal of claim 8, wherein the text entry of content files comprises textual contents of the content files.(String), 10.如权利要求8所述的移动终端,其中内容文件的文本条目包括内容文件的文本内容。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 11. The mobile terminal of claim 8, wherein the textual excerpt is displayed together with an icon indicating the content file.(String), 11.如权利要求8所述的移动终端,其中文本摘录与指示内容文件的图标一起显示。(String), 1(Integer), 10(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.612 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 12. The mobile terminal of claim 11, wherein selection of the icon executes the content file associated with the icon.(String), 12.如权利要求11所述的移动终端,其中选择图标会执行与该图标相关联的内容文件。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.612 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 13. The mobile terminal of claim 11, wherein the icon comprises an avatar.(String), 13.如权利要求11所述的移动终端,其中该图标包括一个化身。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.612 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185989(Integer), 14. The mobile terminal of claim 8, wherein the content files comprises at least one of phone book files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files and game program files.(String), 14.如权利要求8所述的移动终端,其中内容文件包括电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静态图片文件、运动图片文件和游戏程序文件中的至少一种。(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.898 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.898 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.898 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185989(Integer), CROSS-REFERENCE TO RELATED PATENT APPLICATION [0001]This application claims the benefit under 35 U.S.C. §119(a) of Korean Patent Application filed in the Korean Intellectual Property Office on Jul. 6, 2006 and assigned Serial No. 2006-0063428, the entire disclosure of which is hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an integrated method and mobile terminal for searching a desired content file in the mobile terminal. More particularly, the present invention relates to an integrated content file search method for a mobile terminal wherein content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and searched content files can be selected for immediate execution. [0004]2. Description of the Related Art [0005]In recent years, mass-storage devices have been installed in mobile terminals to increase storage capacity. Some mobile terminals include a hard disk drive (HDD) or a high-capacity non-volatile memory device. [0006]With increased storage capacity, various content files (for example, phonebook files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files, and game program files) are classified according to their categories and stored in a hierarchical structure in a mobile terminal. In a hierarchical structure such as a tree-like structure, a parent-child relation exists between an element (parent) and a next-lower-level element (child). Namely, a parent element can have zero, one or multiple child elements, and a child element can have only one parent element. [0007]Because a large number of content files are stored in a hierarchical structure, it is difficult to know the location of a particular content file in a mobile terminal. Further, in a conventional search approach, content file search is limited to a particular folder or category. [0008]Accordingly, there is a need for an improved method for locating a content file in a mobile terminal and a mobile terminal implementing the same. SUMMARY OF THE INVENTION [0009]An aspect of exemplary embodiments of the present invention is to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of exemplary embodiments of the present invention is to provide an integrated content file search method for a mobile terminal wherein contents files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner and selection of one of the found content files causes immediate execution of the selected content file. [0010]In order to achieve the aspects, an exemplary embodiment of the present invention provides an integrated content file search method for a mobile terminal, in which a search mode is set for content file search, a search string from a user is input; the input search string is displayed on a display unit of the mobile terminal, a text entry of content files stored in the mobile terminal is accessed, the text entry is verified to determine whether the text entry contains the input search string, a textual excerpt from the text entry containing the input search string is displayed on the display unit, and a content file that contains the displayed textual excerpt is executed. [0011]In an exemplary implementation, the text entry of content files may include a list of file subjects on the content files. Alternatively, the text entry of content files may include textual contents of the content files. [0012]In another exemplary implementation, a textual excerpt of the corresponding content file is displayed together with an icon indicating the content file. [0013]In still another exemplary implementation, selection of a displayed icon causes execution of the content file associated with the icon. [0014]In a further exemplary implementation, the icon is represented in the form of an avatar. [0015]In order to achieve the aspects, an exemplary embodiment of the present invention provides a mobile terminal which includes: a key input unit for setting a search mode for a content file search and inputting a search string; a display unit for displaying the input search string; a controller for accessing a text entry of content files, verifying the text entry to determine whether the text entry contains the input search string, displaying a textual excerpt from the text entry containing the input search string, and executing a content file that contains the textual excerpt. BRIEF DESCRIPTION OF THE DRAWINGS [0016]The above and other objects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following detailed description in conjunction with the accompanying drawings, in which: [0017]FIG. 1 illustrates a configuration of a mobile terminal according to an exemplary embodiment of the present invention; [0018]FIG. 2 is a flow chart illustrating steps of an integrated content file search method for a mobile terminal according to an exemplary embodiment of the present invention; and [0019]FIG. 3 illustrates a display screen representation resulting from execution of the search method of FIG. 2. [0020]Throughout the drawings, the same drawing reference numerals will be understood to refer to the same elements, features and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS [0021]The matters defined in the description such as a detailed construction and elements are provided to assist in comprehensive understanding of exemplary embodiments of the invention. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. [0022]FIG. 1 illustrates a configuration of a mobile terminal according to an exemplary embodiment of the present invention. [0023]Referring to FIG. 1, the mobile terminal includes a camera module 111, a video processor 112, a display unit 113, a memory unit 114, a key input unit 115, an audio processor 116, a radio frequency (RF) unit 117, a data processor 118, and a controller 119. [0024]The camera module 111 includes a camera lens for forming an image of a target object, a camera sensor for converting an optical signal corresponding to the formed image into an electrical signal, and a signal processor for converting the analog electrical signal from the camera sensor into digital data. The camera sensor may be a charge-coupled device (CCD) sensor, and the signal processor may be a digital signal processor (DSP). The camera sensor and signal processor may be implemented as a single body or as separate bodies. [0025]The video processor 112 generates screen data to display an image signal from the camera module 111. The video processor 112 processes the image signal from the camera module 111 on a frame-by-frame basis to output frame image data corresponding to display characteristics and the size of the display unit 113. The video processor 112 includes a video coder/decoder (codec) to compress frame image data to be displayed on the display unit 113 in a predetermined format and to decompress compressed frame image data into frame image data. The video codec may be a Joint Photographic Experts Group (JPEG) codec, Moving Picture Experts Group-4 (MPEG-4) codec or wavelet codec. The video processor 112 may also perform an on screen display (OSD) function, and output OSD data corresponding to the picture size under the control of the controller 119. [0026]The display unit 113 displays an image signal from the video processor 112, and data from the controller 119 on a screen. The display unit 113 may include a panel that is composed of display devices such as liquid crystal display (LCD) devices or organic light emitting diodes (OLED). In an exemplary implementation, the panel has a touch screen capability. [0027]The memory unit 114 includes a program memory section and a data memory section. The program memory section stores executable programs of the mobile terminal, and the data memory section temporarily stores data resulting from execution of the programs. In an exemplary implementation, the memory unit 114 includes a hard disk drive for a mobile terminal or a non-volatile memory device such as a flash memory. [0028]The key input unit 115 includes a plurality of keys for inputting numeric data, text data and phone numbers, and a plurality of function keys for setting functions of the mobile terminal. The key input unit 115 may further include shortcut keys such as keys labeled by ‘#’ and ‘*’. [0029]The audio processor 116 reproduces an audio signal from an audio codec of the data processor 18, and transmits an audio signal from a microphone (MIC) to the audio codec of the data processor 18. [0030]The RF unit 117 performs wireless communication operations for the mobile terminal. The RF unit 117 includes a RF transmitter for upconverting the frequency of a signal to be transmitted and amplifying the signal, and an RF receiver for low-noise amplifying a received signal and downconverting the frequency of the signal. [0031]The data processor 118 includes a transmitter for encoding and modulating a signal to be transmitted, and a receiver for demodulating and decoding a received signal. The data processor 118 may include a modem and a codec. The codec includes a data codec for processing packet data, and an audio codec for processing an audio signal such as a voice signal. [0032]The controller 119 controls the overall operation of the mobile terminal. The controller 119 may include the data processor 118. The controller 119 is connected to the video processor 112, display unit 113, memory unit 114, key input unit 115, audio processor 116 and data processor 18, and controls these components to exchange and process data, and to establish a call. [0033]FIG. 2 is a flow chart illustrating steps of an integrated content file search method for a mobile terminal according to an exemplary embodiment of the present invention; and FIG. 3 illustrates a display screen representation resulting from execution of the search method of FIG. 2. [0034]Referring to FIG. 2, the mobile terminal is initially in an idle mode after power-on (S201). [0035]The user inputs a predetermined key to set a search mode for finding a desired content file (S203). [0036]Content files include various data files such as phonebook files, short message files, multimedia message files, electronic mail files, text document files, still picture files, moving picture files, and game program files. [0037]In setting a search mode, a search range may be reduced by limiting categories of content files to be searched. For example, a search range may be set to include phonebook files in the mobile terminal, or set to include short message files, multimedia message files and electronic mail files. [0038]If a search range is set to include file contents in addition to file subjects, a content file containing a particular search string in textual contents thereof can be found. [0039]The user inputs a search string using a keypad of the key input unit 115 or a touch screen of the display unit 113 (S205). [0040]The controller 119 displays the input search string on a screen of the display unit 113 (S207). [0041]The controller 119 accesses a text entry of content files (S209). The text entry of content files stored in the mobile terminal may include a list of file subjects on the content files. [0042]In an exemplary implementation, each content file to be stored in the mobile terminal has at least one file subject. Thereby a content file whose file subject contains an input search string can be found. [0043]The text entry of content files may also include textual contents of the content files. If the search range is set to include file contents in addition to file subjects, a content file containing the input search string in the textual contents can be found. For example, if the contents of a document file contain an input search string, the file name of the document file is output. [0044]The controller 119 checks the text entry to determine whether at least one content file containing the input search string exists (S211). [0045]If no content file containing the input search string is found, the controller 119 returns to step S205 to input a search string for a new search. [0046]If a content file that contains the input search string is found, a textual excerpt and/or a file subject containing the input search string from the text entry, and a category of the found content file is displayed on the display unit 113 (S213). [0047]FIG. 3 illustrates a search result when a search string ‘James’ is input in a search field 320 of the display unit 113. Every content file whose file subject or textual contents contains the search string ‘James’ is found. In FIG. 3, content files, such as a phone book file 330, a text message file 340, an electronic mail file 350, a still picture file 360, and a document file 370 are found, and textual excerpts and/or file subjects of the found content files are displayed in a list of search results. [0048]In addition, an icon indicating a file category is displayed in the list of search results for easy identification of the category of a corresponding content file. The icon can be represented in the form of an avatar. [0049]The user selects a displayed item in a list of search results for execution of a content file associated with the selected item (S215). The user can select a file sequence number or an icon in the list of search results using a key of the key input unit 115 or a touch screen of the display unit 113. [0050]A content file associated with the selected item is entered into an execution mode and executed (S217). [0051]The controller 119 asks the user whether to execute another content file in the list of search results (S219). [0052]If the user decides to execute another content file in the list of search results at step S219, the controller 119 returns to step S213 and repeats step S213 and subsequent steps to execute another content file. [0053]If the user decides not to execute another content file at step S219, the controller 119 asks the user whether to perform a new search (S223). [0054]If the user inputs a command key for setting a search mode, the controller 119 returns to step S205 and repeats step S205 and subsequent steps to perform a new search. [0055]As apparent from the above description, exemplary embodiments of the present invention provide an integrated content file search method for a mobile terminal. Content files stored in the mobile terminal in a hierarchical or non-hierarchical structure are searched in an integrated manner, and selection of one of the found content files causes immediate execution of the selected content file. Thereby a desired content file can be easily found and executed. [0056]While the present invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.(String), 相关专利申请的交叉引用 [0001] 本申请根据 35 U.S.C. §119(a) 于 2006 年 7 月 6 日在韩国知识产权局提交并分配序列号为 2006-0063428 的韩国专利申请,其全部公开内容通过引用并入本文。 发明背景 [0002] 一、发明领域 [0003] 本发明总体上涉及一种用于在移动终端中搜索所需内容文件的集成方法和移动终端。 更具体地,本发明涉及一种用于移动终端的集成内容文件搜索方法,其中以集成方式搜索以分层或非分层结构存储在移动终端中的内容文件,并且可以选择搜索到的内容文件以用于即时 执行。 [0004] 二、相关技术说明 [0005] 近年来,大容量存储设备已经安装在移动终端中以增加存储容量。 一些移动终端包括硬盘驱动器(HDD)或大容量非易失性存储设备。 [0006] 随着存储容量的增加,各种内容文件(例如,电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静态图片文件、运动图片文件和游戏程序文件)根据其类别进行分类 并以分层结构存储在移动终端中。 在树状结构等层级结构中,元素(父)与下一级元素(子)之间存在父子关系。 即,一个父元素可以有零个、一个或多个子元素,而一个子元素只能有一个父元素。 [0007] 由于大量的内容文件以分层结构存储,因此很难知道特定内容文件在移动终端中的位置。 此外,在传统的搜索方法中,内容文件搜索限于特定文件夹或类别。 [0008] 因此,需要一种用于在移动终端中定位内容文件的改进方法和实现该方法的移动终端。 发明内容 [0009] 本发明示例性实施例的一个方面是至少解决上述问题和/或缺点并且至少提供下述优点。 因此,本发明示例性实施例的一个方面是提供一种用于移动终端的综合内容文件搜索方法,其中以综合方式搜索以分层或非分层结构存储在移动终端中的内容文件,并选择一个 找到的内容文件导致立即执行所选内容文件。 [0010] 为了实现这些方面,本发明的示例性实施例提供了一种用于移动终端的集成内容文件搜索方法,其中为内容文件搜索设置搜索模式,输入来自用户的搜索字符串; 输入的搜索字符串显示在移动终端的显示单元上,访问存储在移动终端中的内容文件的文本条目,验证文本条目以确定文本条目是否包含输入的搜索字符串,文本摘自 包含输入的搜索字符串的文本条目显示在显示单元上,并且执行包含显示的文本摘录的内容文件。 [0011] 在示例性实施方式中,内容文件的文本条目可以包括关于内容文件的文件主题的列表。 或者,内容文件的文本条目可以包括内容文件的文本内容。 [0012] 在另一示例性实施方式中,相应内容文件的文本摘录与指示内容文件的图标一起显示。 [0013] 在又一示例性实施方式中,显示图标的选择引起与该图标相关联的内容文件的执行。 [0014] 在进一步的示例性实施方式中,图标以化身的形式表示。 [0015]为了实现这些方面,本发明的示例性实施例提供了一种移动终端,包括:键输入单元,用于设置内容文件搜索的搜索模式并输入搜索字符串; 显示单元,用于显示输入的搜索字符串; 控制器,用于访问内容文件的文本条目,验证文本条目以确定文本条目是否包含输入搜索字符串,显示来自包含输入搜索字符串的文本条目的文本摘录,以及执行包含文本的内容文件 摘抄。 附图的简要说明 [0016] [0010] 通过以下结合附图的详细描述,本发明的某些示例性实施例的上述和其他目的、特征和优点将更加明显,其中: [0017] 图1图示了根据本发明示例性实施例的移动终端的配置; [0018] 图2是示出根据本发明示例性实施例的用于移动终端的综合内容文件搜索方法的步骤的流程图; 和 [0019] 图3图示了由执行图2的搜索方法产生的显示屏表示。 [0020] 在整个附图中,相同的附图标记将被理解为指代相同的元件、特征和结构。 示例性实施方案的详细描述 [0021] 提供描述中定义的事项,例如详细构造和元件,以帮助全面理解本发明的示例性实施例。 因此,本领域的普通技术人员将认识到,在不脱离本发明的范围和精神的情况下,可以对本文描述的实施例进行各种改变和修改。 此外,为了清楚和简明起见,省略了对众所周知的功能和结构的描述。 [0022] 图1图示了根据本发明示例性实施例的移动终端的配置。 [0023] 参见图1,移动终端包括摄像头模块 111 , 视频处理器 112 , 显示单元 113 , 一个记忆单元 114 , 一个按键输入单元 115 , 音频处理器 116 , 射频 (RF) 单元 117 , 数据处理器 118 , 和一个控制器 119 . [0024] 相机模组 111 包括用于形成目标物体的图像的相机镜头、用于将与形成的图像相对应的光信号转换为电信号的相机传感器以及用于将来自相机传感器的模拟电信号转换为数字数据的信号处理器。 相机传感器可以是电荷耦合器件(CCD)传感器,信号处理器可以是数字信号处理器(DSP)。 相机传感器和信号处理器可以实现为单个主体或单独的主体。 [0025] 视频处理器 112 生成屏幕数据以显示来自相机模块的图像信号 111 . 视频处理器 112 处理来自相机模块的图像信号 111 逐帧输出对应显示特性和显示单元尺寸的帧图像数据 113 . 视频处理器 112 包括一个视频编码器/解码器(编解码器)来压缩要在显示单元上显示的帧图像数据 113 以预定格式将压缩的帧图像数据解压缩为帧图像数据。 视频编解码器可以是联合图像专家组(JPEG)编解码器、运动图像专家组-4(MPEG-4)编解码器或小波编解码器。 视频处理器 112 还可以执行屏幕显示(OSD)功能,并在控制器的控制下输出与画面尺寸对应的OSD数据 119 . [0026] 显示单元 113 显示来自视频处理器的图像信号 112 , 以及来自控制器的数据 119 在屏幕上。 显示单元 113可包括由诸如液晶显示(LCD)装置或有机发光二极管(OLED)之类的显示装置构成的面板。 在示例性实施方式中,面板具有触摸屏能力。 [0027] 记忆单元 114 包括一个程序存储部分和一个数据存储部分。 程序存储部分存储移动终端的可执行程序,数据存储部分临时存储程序执行产生的数据。 在示例性实现中,存储单元 114 包括用于移动终端的硬盘驱动器或诸如闪存的非易失性存储设备。 [0028] 按键输入单元 115 包括用于输入数字数据、文本数据和电话号码的多个键,以及用于设置移动终端功能的多个功能键。 按键输入单元 115 还可以包括快捷键,例如标有“#”和“*”的键。 [0029] 音频处理器 116 从数据处理器的音频编解码器再现音频信号 18 , 并将来自麦克风 (MIC) 的音频信号传输到数据处理器的音频编解码器 18 . [0030] 射频单元 117 为移动终端执行无线通信操作。 射频单元 117 包括用于对要发送的信号进行上变频和放大信号的RF发射器,以及用于对接收到的信号进行低噪声放大和对信号的频率进行下变频的RF接收器。 [0031] 数据处理器 118 包括用于对要发送的信号进行编码和调制的发送器,以及用于对接收到的信号进行解调和解码的接收器。 数据处理器 118 可能包括调制解调器和编解码器。 编解码器包括用于处理分组数据的数据编解码器和用于处理诸如语音信号的音频信号的音频编解码器。 [0032] 控制器 119 控制移动终端的整体操作。 控制器 119 可能包括数据处理器 118 . 控制器 119 连接到视频处理器 112 , 显示单元 113 , 记忆单元 114 , 按键输入单元 115 , 音频处理器 116 和数据处理器 18 ,并控制这些组件交换和处理数据,并建立呼叫。 [0033] 图2是示出根据本发明示例性实施例的用于移动终端的综合内容文件搜索方法的步骤的流程图; 图3示出了执行图2的搜索方法所产生的显示屏幕表示。 [0034] 参考图2,移动终端在开机后最初处于空闲模式(S 201 ). [0035] 用户输入预定键以设置用于查找所需内容文件的搜索模式(S 203 ). [0036] 内容文件包括各种数据文件,例如电话簿文件、短信文件、彩信文件、电子邮件文件、文本文档文件、静止图片文件、运动图片文件和游戏程序文件。 [0037] 在设置搜索模式时,可以通过限制要搜索的内容文件的类别来缩小搜索范围。 例如,可以将搜索范围设置为包括移动终端中的电话本文件,或者设置为包括短信文件、彩信文件和电子邮件文件。 [0038] 如果将搜索范围设置为包括文件内容以及文件主题,则可以找到在其文本内容中包含特定搜索字符串的内容文件。 [0039] 用户使用键输入单元的小键盘输入搜索字符串 115 或显示单元的触摸屏 113 (小号 205 ). [0040] 控制器 119 在显示单元的屏幕上显示输入的搜索字符串 113 (小号 207 ). [0041] 控制器 119 访问内容文件的文本条目(S 209 ). 存储在移动终端中的内容文件的文本条目可以包括内容文件上的文件主题列表。 [0042]在一个示例性实施方式中,移动终端中存储的每个内容文件具有至少一个文件主题。 从而可以找到其文件主题包含输入的搜索字符串的内容文件。 [0043] 内容文件的文本条目还可以包括内容文件的文本内容。 如果搜索范围设置为包括文件内容和文件主题,则可以找到文本内容中包含输入搜索字符串的内容文件。 例如,如果文档文件的内容包含输入搜索字符串,则输出文档文件的文件名。 [0044] 控制器 119 检查文本条目以确定是否存在至少一个包含输入搜索字符串的内容文件(S 211 ). [0045] 如果没有找到包含输入搜索字符串的内容文件,控制器 119 回到步骤S 205 为新搜索输入搜索字符串。 [0046] 如果找到包含输入搜索字符串的内容文件,则在显示单元上显示包含来自文本条目的输入搜索字符串的文本摘录和/或文件主题,以及找到的内容文件的类别 113 (小号 213 ). [0047] 图 3 说明了在搜索字段中输入搜索字符串“James”时的搜索结果 320 显示单元 113 . 找到文件主题或文本内容包含搜索字符串“James”的每个内容文件。 在图3中,内容文件,例如电话簿文件 330 , 一个短信文件 340 , 一个电子邮件文件 350 , 静态图片文件 360 , 和文档文件 370 找到,并且找到的内容文件的文本摘录和/或文件主题显示在搜索结果列表中。 [0048] 此外,在搜索结果列表中显示指示文件类别的图标,以便于识别相应内容文件的类别。 图标可以以化身的形式表示。 [0049] 用户选择搜索结果列表中显示的项目以执行与所选项目相关联的内容文件(S 215 ). 用户可以使用键输入单元的键在搜索结果列表中选择文件序号或图标 115 或显示单元的触摸屏 113 . [0050] 与所选项目关联的内容文件进入执行模式并执行(S 217 ). [0051] 控制器 119 询问用户是否执行搜索结果列表中的另一个内容文件(S 219 ). [0052] 如果用户在步骤S决定执行搜索结果列表中的另一个内容文件 219 , 控制器 119 回到步骤S 213 并重复步骤 S 213 以及执行另一个内容文件的后续步骤。 [0053] 如果用户在步骤 S 决定不执行另一个内容文件 219 , 控制器 119 询问用户是否执行新的搜索(S 223 ). [0054] 如果用户输入用于设置搜索模式的命令键,则控制器 119 回到步骤S 205 并重复步骤 S 205 以及执行新搜索的后续步骤。 [0055] 从以上描述显而易见,本发明的示例性实施例提供了一种用于移动终端的综合内容文件搜索方法。 以集成的方式搜索存储在移动终端中的分层或非分层结构的内容文件,并且选择找到的内容文件之一导致立即执行所选内容文件。 从而可以容易地找到并执行所需的内容文件。 [0056] 虽然本发明已经参照其某些示例性实施例被示出和描述,但是本领域的技术人员将理解,在不脱离所定义的本发明的精神和范围的情况下,可以在其中进行形式和细节的各种改变 通过所附权利要求及其等同物。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.937 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:31.938 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100745040B1(String), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.090 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100745040B1(String), US20080010261A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100745040B1(String), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271665(Integer), KR100745040B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.196 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271665(Integer), US20080010261A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.230 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.231 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20080010261A1(String), US20080010261A1(String), 1199894400(Integer), 271665(Integer), 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.265 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.266 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.266 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), NAM, HAN SOEK(String), KIM, BONG KYUN(String), KIM, HWAN(String), 三星电子株式会社(String), NAM HAN SOEK(String), KIM BONG KYUN(String), KIM HWAN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185989(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185989(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: NAM, HAN SOEK(String), NAM HAN SOEK(String), 0(Integer), 1681976132(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.451 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: KIM, BONG KYUN(String), KIM BONG KYUN(String), 0(Integer), 1681976132(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.485 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.486 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: KIM, HWAN(String), KIM HWAN(String), 0(Integer), 1681976132(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.520 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.521 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.521 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185989(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75853(Integer), 2(Integer), 185989(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75854(Integer), 2(Integer), 185989(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75855(Integer), 2(Integer), 185989(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75853(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.934 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185989(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:32.971 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9560486B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for identifying motion status of mobile terminal, and mobile terminal(String), 一种识别移动终端运动状态的方法及移动终端(String), US9560486B2(String), A method for identifying a motion status of a mobile terminal, and a mobile terminal are provided. The method includes collecting information about multiple wireless local area network (WLAN) access points during each time of scanning, where the information includes a basic service set identifier and signal strength; calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points; and presetting a belief decision threshold and a list orthogonality decision threshold, and comparing the decision thresholds with calculated values to acquire the motion status of the mobile terminal. Therefore, the motion status of the mobile terminal may be acquired without making a change in any hardware on an existing mobile terminal. In addition, the present disclosure is applicable to an area covered by multiple wireless local area network access points.(String), 提供了一种移动终端运动状态的识别方法及移动终端。 该方法包括在每次扫描时收集多个无线局域网(WLAN)接入点的信息,该信息包括基本服务集标识和信号强度; 根据多个WLAN接入点的信息计算置信度值和列表正交度值; 预设置信度判定阈值和列表正交性判定阈值,将判定阈值与计算值进行比较,获取移动终端的运动状态。 因此,无需对现有移动终端的硬件做任何改动,即可获取移动终端的运动状态。 另外,本发明适用于多个无线局域网接入点覆盖的区域。(String), US14/923094(String), 1445788800(Integer), US9560486B2(String), 1485792000(Integer), 1485792000(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 13(Integer), CN101627561A | CN101822094A | CN102111434A | CN102355530A | CN1501610A | CN201978444U | US20070018890A1 | US20070183344A1 | US20080207278A1 | US20100248668A1 | US20100255781A1 | US20120004881A1 | US20140141796A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185990(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\77024a6a88454561a74bf41a2a8b52c9.png(String), 185990(Integer), 77024a6a88454561a74bf41a2a8b52c9.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.548 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for identifying motion status of mobile terminal, and mobile terminal(String), 一种识别移动终端运动状态的方法及移动终端(String), US9560486B2(String), A method for identifying a motion status of a mobile terminal, and a mobile terminal are provided. The method includes collecting information about multiple wireless local area network (WLAN) access points during each time of scanning, where the information includes a basic service set identifier and signal strength; calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points; and presetting a belief decision threshold and a list orthogonality decision threshold, and comparing the decision thresholds with calculated values to acquire the motion status of the mobile terminal. Therefore, the motion status of the mobile terminal may be acquired without making a change in any hardware on an existing mobile terminal. In addition, the present disclosure is applicable to an area covered by multiple wireless local area network access points.(String), 提供了一种移动终端运动状态的识别方法及移动终端。 该方法包括在每次扫描时收集多个无线局域网(WLAN)接入点的信息,该信息包括基本服务集标识和信号强度; 根据多个WLAN接入点的信息计算置信度值和列表正交度值; 预设置信度判定阈值和列表正交性判定阈值,将判定阈值与计算值进行比较,获取移动终端的运动状态。 因此,无需对现有移动终端的硬件做任何改动,即可获取移动终端的运动状态。 另外,本发明适用于多个无线局域网接入点覆盖的区域。(String), US14/923094(String), 1445788800(Integer), US9560486B2(String), 1485792000(Integer), 1485792000(Integer), 美国(String), 2(Integer), 4(Integer), CN(String), 4(Integer), 13(Integer), CN101627561A | CN101822094A | CN102111434A | CN102355530A | CN1501610A | CN201978444U | US20070018890A1 | US20070183344A1 | US20080207278A1 | US20100248668A1 | US20100255781A1 | US20120004881A1 | US20140141796A1(String), \20230420\77024a6a88454561a74bf41a2a8b52c9.png(String), 16(Integer), 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 1. A method for identifying a motion status of a mobile terminal, the method comprising:scanning for wireless local area network (WLAN) access points of the mobile terminal once every specified sampling period;collecting information about multiple WLAN access points that are acquired during each time of scanning, wherein the information comprises a basic service set identifier and signal strength;calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length, wherein the set time window length is n sampling period, wherein n is an integral multiple, wherein the belief value is an average length of WLAN access point lists within the set time window length, and wherein the list orthogonality value is a weighted average of (n−1) orthogonalities that are acquired by separately calculating orthogonality between the last list and previous (n−1) lists within the time window;comparing the calculated belief value with a preset belief decision threshold;comparing the calculated list orthogonality value with a preset list orthogonality decision threshold when the calculated belief value is greater than the preset belief decision threshold;determining that the motion status of the mobile terminal is still when the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold; anddetermining that the motion status of the mobile terminal is driving when the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold.(String), 1.一种移动终端运动状态的识别方法,该方法包括:每隔指定的采样周期扫描一次移动终端的无线局域网(WLAN)接入点;收集每次扫描获取的多个WLAN接入点的信息,该信息包括基本服务集标识和信号强度;根据在设定的时间窗长度内获取的多个WLAN接入点的信息,计算置信值和列表正交值,其中,设定的时间窗长度为n个采样周期,n为整数倍,置信度value为设定时间窗长度内WLAN接入点列表的平均长度,其中列表正交度值为(n-1)个正交度的加权平均,分别计算上一个列表与前(n-)个列表的正交度得到1)在时间窗口内列出;将计算出的置信度值与预设的置信度决策阈值进行比较;当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较;当计算出的列表正交性值小于预设列表正交性判定阈值的最小值时,确定移动终端的运动状态为静止;和当计算出的列表正交性值大于预设列表正交性判定阈值的最大值时,确定移动终端的运动状态为驾驶。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 2. The method according to claim 1, wherein calculating the belief value comprises:multiplying a quantity of multiple WLAN access points acquired during the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; andadding all the average quantities of WLAN access points to acquire the belief value, wherein the average quantities are calculated within the set time window length.(String), 2.根据权利要求1所述的方法,其中计算置信值包括:将每隔指定采样周期扫描获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子,计算出每次扫描后的平均WLAN接入点数量;和将所有WLAN接入点的平均数量相加得到置信值,其中平均数量是在设定的时间窗长度内计算得到的。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 3. The method according to claim 1, wherein calculating the list orthogonality value comprises:comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning;acquiring, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value;adding degrees of contribution of all of the non-duplicate WLAN access points;multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution;adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a quantity of WLAN access points;dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, wherein a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; andadding the list orthogonality values of the first time of scanning, the second time of scanning, and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length.(String), 3.根据权利要求1所述的方法,其中计算列表正交值包括:在设置的时间窗长度内,将第一次扫描获取的多个WLAN接入点信息与第二次扫描获取的多个WLAN接入点信息进行比较,得到非重复的WLAN接入点信息在两次扫描中获得的;根据预设的贡献度函数获取每个非重复WLAN接入点的信号强度对列表正交值的贡献度;添加所有非重复WLAN接入点的贡献度;将相加得到的值乘以预设的第二时间维度权重因子,得到平均贡献度;将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到WLAN接入点数量;将平均贡献度除以WLAN接入点数量得到第一次扫描的列表正交度值,其中第二次扫描的列表正交度值是通过比较多个WLAN接入点的信息得到的。将第二次扫描获取的多个WLAN接入点的信息与第三次扫描获取的多个WLAN接入点的信息进行比较,将获取的多个WLAN接入点的信息进行比较,得到第三次扫描的列表正交值在第三次扫描时,使用第四次扫描时获取的多个WLAN接入点的信息,以及(N-1)的列表正交值th获取扫描次数,假设在设定的时间窗长度内,在指定的采样周期内共进行了N次扫描;和将第一次扫描、第二次扫描的列表正交值相加,第(N-1)次th扫描次数获取设定时间窗长度内N次扫描的列表正交值。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 4. The method according to claim 1, further comprising determining that the motion status of the mobile terminal cannot be identified when the calculated belief value is less than the preset belief decision threshold.(String), 4.根据权利要求1所述的方法,还包括当计算出的置信度值小于预设的置信度判定阈值时,确定无法识别移动终端的运动状态。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 5. The method according to claim 1, further comprising:calculating a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length; andcomparing the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold when the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the preset list orthogonality decision threshold value.(String), 5.根据权利要求1所述的方法,还包括:根据在设定时间窗长度内获取的多个WLAN接入点的信息,计算信号波动率;和当计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于预设列表正交性判定阈值的最大值时,将计算出的信号波动率与预设信号波动率判定阈值进行比较。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 6. The method according to claim 5, further comprising:determining that the motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold; anddetermining that the motion status of the mobile terminal is still when the calculated signal fluctuation rate is less than the preset signal fluctuation rate decision threshold.(String), 6.根据权利要求5所述的方法,还包括:当计算出的信号波动率大于预设的信号波动率判定阈值时,确定移动终端的运动状态为步行;和当计算出的信号波动率小于预设的信号波动率判定阈值时,确定移动终端的运动状态为静止。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 7. The method according to claim 5, further comprising:determining that the motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold; anddetermining that the motion status of the mobile terminal is still when the calculated signal fluctuation rate is equal to the preset signal fluctuation rate decision threshold.(String), 7.根据权利要求5所述的方法,还包括:当计算出的信号波动率大于预设的信号波动率判定阈值时,确定移动终端的运动状态为步行;和当计算出的信号波动率等于预设的信号波动率判定阈值时,确定移动终端的运动状态为静止。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 8. The method according to claim 1, further comprising setting a motion status, which occurs for most times in motion statuses of the mobile terminal within several successive time windows, of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows.(String), 8.根据权利要求1所述的方法,还包括将移动终端在连续几个时间窗内的移动终端的运动状态中出现次数最多的运动状态设置为移动终端在连续几个时间窗内的最终运动状态。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 9. A mobile terminal, comprising:a processor;a communication interface;a memory; anda bus,wherein the processor, the communication interface and the memory accomplish mutual communication using the bus,wherein the communication interface is configured to communicate with another device,wherein the memory is configured to store an application, andwherein the processor is configured to execute the application stored in the memory to:scan for wireless local area network (WLAN) access points of the mobile terminal once every specified sampling period, and collect information about multiple WLAN access points that are acquired during each time of scanning, wherein the information comprises a basic service set identifier and signal strength;calculate a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length, wherein the set time window length is n sampling period, wherein n is an integral multiple, wherein the belief value is an average length of WLAN access point lists within the set time window length, and wherein the list orthogonality value is a weighted average of (n−1) orthogonalities that are acquired by separately calculating orthogonality between the last list and previous (n−1) lists within the time window;compare the calculated belief value with a preset belief decision threshold;compare the calculated list orthogonality value with a preset list orthogonality decision threshold when the calculated belief value is greater than the preset belief decision threshold;determine that motion status of the mobile terminal is still when the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold; anddetermine that motion status of the mobile terminal is driving when the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold.(String), 9.移动终端,包括:处理器;通信接口;记忆;和一辆巴士,其中,处理器、通信接口和存储器通过总线实现相互通信,其中,通信接口被配置为与另一设备通信,其中存储器被配置为存储应用程序,并且其中,处理器被配置为执行存储在存储器中的应用程序以:每隔指定的采样周期扫描一次移动终端的无线局域网(WLAN)接入点,并收集每次扫描获取的多个WLAN接入点的信息,该信息包括基本服务集标识和信号强度;根据在设定的时间窗长度内获取的多个WLAN接入点的信息计算置信值和列表正交值,其中,设定的时间窗长度为n个采样周期,n为整数倍,置信度value为设定时间窗长度内WLAN接入点列表的平均长度,其中列表正交度值为(n-1)个正交度的加权平均,分别计算上一个列表与前(n-)个列表的正交度得到1)在时间窗口内列出;将计算出的置信度值与预设的置信度决策阈值进行比较;当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较;当计算出的列表正交性值小于预设列表正交性判定阈值的最小值时,确定移动终端的运动状态为静止;和当计算出的列表正交性值大于预设列表正交性判定阈值的最大值时,确定移动终端的运动状态为正在驾驶。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 10. The mobile terminal according to claim 9, wherein the processor being configured to execute the application to calculate the belief value includes being configured to execute the application to:multiply a quantity of multiple WLAN access points acquired during the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; andadd all the average quantities of WLAN access points to acquire the belief value, wherein the average quantities are calculated within the set time window length.(String), 10.根据权利要求9所述的移动终端,其中处理器被配置为执行应用程序以计算置信度值包括被配置为执行应用程序以:将每指定采样周期扫描获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子,计算出每次扫描后的平均WLAN接入点数量;和将所有WLAN接入点的平均数量相加得到置信值,其中平均数量是在设定的时间窗长度内计算得到的。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 11. The mobile terminal according to claim 9, wherein the processor being configured to execute the application to calculate the list orthogonality value includes being configured to execute the application to:compare, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning;acquire, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value;add degrees of contribution of all of the non-duplicate WLAN access points;multiply a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution;add a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a value of a quantity of WLAN access points;divide the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, wherein a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and a list orthogonality value of the (N−1)th of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; andadd the list orthogonality values of the first time of scanning, the second time of scanning, and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length.(String), 11.根据权利要求9所述的移动终端,其中处理器被配置为执行应用程序以计算列表正交性值包括被配置为执行应用程序以:在设置的时间窗长度内,将第一次扫描获取的多个WLAN接入点信息与第二次扫描获取的多个WLAN接入点信息进行比较,得到非重复的WLAN接入点信息在两次扫描中获得的;根据预设的贡献度函数获取每个非重复WLAN接入点的信号强度对列表正交值的贡献度;添加所有非重复WLAN接入点的贡献度;相加得到的值乘以预设的第二时间维度权重因子,得到平均贡献度;将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到WLAN接入点数量值;将平均贡献度除以WLAN接入点数量得到第一次扫描的列表正交度值,其中第二次扫描的列表正交度值是通过比较多个WLAN接入点的信息得到的。将第二次扫描获取的多个WLAN接入点的信息与第三次扫描获取的多个WLAN接入点的信息进行比较,将获取的多个WLAN接入点的信息进行比较,得到第三次扫描的列表正交值在第三次扫描时,使用第四次扫描时获取的多个WLAN接入点的信息,以及(N-1)的列表正交值th获取扫描次数,假设在设定的时间窗长度内,在指定的采样周期内总共进行了N次扫描;和将第一次扫描、第二次扫描的列表正交值相加,第(N−1)th扫描次数获取设定时间窗长度内N次扫描的列表正交值。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 12. The mobile terminal according to claim 9, wherein the processor is further configured to execute the application to determine that motion status of the mobile terminal cannot be identified when the calculated belief value is less than the preset belief decision threshold.(String), 12.根据权利要求9所述的移动终端,其中处理器,还用于当计算出的置信度值小于预设置信度判定阈值时,执行应用程序判断为无法识别移动终端的运动状态。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 13. The mobile terminal according to claim 9, wherein the processor is further configured to execute the application to calculate a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length, and compare the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold when the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the list orthogonality decision threshold.(String), 13.根据权利要求9所述的移动终端,其中处理器,还用于执行应用,根据设定的时间窗长度内获取的多个WLAN接入点的信息,计算信号波动率,并将计算出的信号波动率与预设的信号波动率判定阈值进行比较当计算出的列表正交性值大于预设的列表正交性判定阈值的最小值且小于列表正交性判定阈值的最大值时。(String), 1(Integer), 12(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.635 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 14. The mobile terminal according to claim 13, wherein the processor is further configured to execute the application to determine that motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, and determine that motion status of the mobile terminal is still when the calculated signal fluctuation rate is less than the preset signal fluctuation rate decision threshold.(String), 14.根据权利要求13所述的移动终端,其中处理器还用于执行应用,当计算出的信号波动率大于预设的信号波动率判定阈值时,判断移动终端的运动状态为行走,当计算出的信号波动率大于预设信号波动率阈值时,判断移动终端的运动状态为静止。计算出的信号波动率小于预设的信号波动率判定阈值。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 15. The mobile terminal according to claim 13, wherein the processor is further configured to execute the application to determine that motion status of the mobile terminal is walking when the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, and determine that motion status of the mobile terminal is still when the calculated signal fluctuation rate is equal to the preset signal fluctuation rate decision threshold.(String), 15.根据权利要求13所述的移动终端,其中处理器还用于执行应用,当计算出的信号波动率大于预设的信号波动率判定阈值时,判断移动终端的运动状态为行走,当计算出的信号波动率大于预设信号波动率阈值时,判断移动终端的运动状态为静止。计算出的信号波动率等于预设的信号波动率判定阈值。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185990(Integer), 16. The mobile terminal according to claim 9, wherein the processor is further configured to execute the application to set a motion status, which occurs for most times in motion statuses of the mobile terminal within several successive time windows of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows.(String), 16.根据权利要求9所述的移动终端,其中处理器还用于执行应用程序,将移动终端的连续几个时间窗口内的移动终端的运动状态中出现次数最多的运动状态设置为移动终端在连续的几个时间窗口内的最终运动状态视窗。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:33.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185990(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2013/087024, filed on Nov. 13, 2013, which claims priority to Chinese Patent Application No. 201310157676.7, filed on Apr. 28, 2013, both of which are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present disclosure relates to the communications field, and in particular, to a method for identifying a motion status of a mobile terminal, and a mobile terminal. BACKGROUND [0003]Motion status identification is one of important content of context awareness. With popularization of mobile terminals, intelligent services with better experience may be provided for a user by inferring, using a mobile terminal, a motion status of the user, triggering, according to the motion status of the user, a change in a status or a function of the mobile terminal, and providing for the user an intelligent mobile application, such as personalized recommendation or accurate advertisement push according to an inferred higher-class user situation. In a mobile terminal application scenario, difficulties and challenges of motion status identification are how prepared identification is performed on motion of different users in a complex and changeable environment using sensors built in most mobile terminals and without the help of a function of another additional hardware. In consideration of limited computing, storage and energy resources of a terminal, an algorithm involved in motion status identification is as simple as possible, and a dependent function module cannot generate a large number of extra function overheads. [0004]A user is positioned by means of satellite positioning (for example, a global positioning system (GPS)), and a difference between longitudes and a difference between latitudes within a time interval are converted into a motion speed for indirectly inferring a motion status of the user. This manner requires a satellite positioning function be additionally enabled. Generally, power consumption of a GPS on a mobile terminal is higher; time to first fix is longer; and this manner often cannot be used in a shaded area (for example, indoors or in an underground passage). [0005]A motion status of a user is inferred by means of feature extraction, classification, and other means and according to data collected by an inertial sensor, such as an acceleration sensor or a gyroscope. Accuracy of identification using this method is more greatly affected by a placement position of a mobile phone and is more closely related to a posture and a motion habit of the user; algorithm complexity is generally higher; and a large number of training samples need to be collected in advance. [0006]Standard deviation analysis is performed on wireless signal strength data of a base station on a traditional wireless cellular network, still and motion states are distinguished according to a standard deviation, and then, feature matching is performed on a signal sequence and a waveform in a sample library to distinguish two motion types: “walking” and “driving”. When the two motion types “walking” and “driving” are distinguished, similarity analysis needs to be performed on the waveform in real time. On one hand, calculation complexity is higher, and a challenge is brought to a processing capacity of a mobile terminal. On the other hand, signal samples need to be collected and stored in advance, and when there is a large amount of data in the sample library, a burden is brought to limited storage space of the mobile terminal. SUMMARY [0007]Objectives of embodiments of the present disclosure are to provide a method for identifying a motion status of a mobile terminal, and a mobile terminal, so as to resolve a problem about how a motion status of a mobile terminal is determined. [0008]According to a first aspect, a method for identifying a motion status of a mobile terminal is provided, where the method includes scanning for wireless local area network (WLAN) access points of the mobile terminal once every specified sampling period, and collecting information about multiple WLAN access points that are acquired during each time of scanning, where the information includes a basic service set identifier and signal strength; calculating a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length; comparing the calculated belief value with a preset belief decision threshold; when the calculated belief value is greater than the preset belief decision threshold, comparing the calculated list orthogonality value with a preset list orthogonality decision threshold; if the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold, determining that the motion status of the mobile terminal is still; and if the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold, determining that the motion status of the mobile terminal is driving. [0009]With reference to the first aspect, in a first possible implementation manner of the first aspect, the calculating a belief value includes multiplying a quantity of multiple WLAN access points acquired in the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; and adding all the average quantities of WLAN access points to acquire the belief value, where the average quantities are calculated within the set time window length. [0010]With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the calculating a list orthogonality value includes comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning; acquiring, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value; adding degrees of contribution of all of the non-duplicate WLAN access points; multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution; adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a quantity of WLAN access points; and dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, where a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is obtained by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and so on, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; and adding the list orthogonality values of the first time of scanning, the second time of scanning, . . . , and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length. [0011]With reference to the first aspect, the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the method further includes, if the calculated belief value is less than the preset belief decision threshold, determining that the motion status of the mobile terminal cannot be identified. [0012]With reference to the first aspect, the first possible implementation manner of the first aspect, the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes calculating a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length, where if the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the list orthogonality decision threshold, comparing the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold. [0013]With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes, if the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, determining that the motion status of the mobile terminal is walking; and if the calculated signal fluctuation rate is less than or equal to the preset signal fluctuation rate decision threshold, determining that the motion status of the mobile terminal is still. [0014]With reference to the first aspect or the first possible implementation manner of the first aspect, or with reference to the second possible implementation manner of the first aspect, the third possible implementation manner of the first aspect, the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the method further includes performing determining according to motion statuses of the mobile terminal within several successive time windows, and setting a determined motion status, which occurs for most times in the motion statuses of the mobile terminal, of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows. [0015]According to a second aspect, a mobile terminal is provided, where the mobile terminal provides a collecting unit configured to scan for WLAN access points of the mobile terminal once every specified sampling period, and collect information about multiple WLAN access points that are acquired during each time of scanning, where the information includes a basic service set identifier and signal strength; a calculation unit configured to calculate a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length; a first comparison unit configured to compare the calculated belief value with a preset belief decision threshold; a second comparison unit configured to, when the calculated belief value is greater than the preset belief decision threshold, compare the calculated list orthogonality value with a preset list orthogonality decision threshold; a first determining unit configured to, if the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold, determine that motion status of the mobile terminal is still; and a second determining unit configured to, if the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold, determine that motion status of the mobile terminal is driving. [0016]With reference to the second aspect, in a first possible implementation manner of the second aspect, the step of calculating the belief value by the calculation unit is multiplying a quantity of multiple WLAN access points acquired in the scanning performed every specified sampling period by a preset first time dimension weight factor to calculate an average quantity of WLAN access points after each time of scanning; and adding all the average quantities of WLAN access points to acquire the belief value, where the average quantities are calculated within the set time window length. [0017]With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the step of calculating the list orthogonality value by the calculation unit is comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning; obtaining, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value; adding degrees of contribution of all of the non-duplicate WLAN access points; multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to obtain an average degree of contribution, adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to obtain a quantity of WLAN access points; and dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning; where a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired the third time of scanning, a list orthogonality value of the third time of scanning is obtained by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and so on, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; and adding the list orthogonality values of the first time of scanning, the second time of scanning, . . . , and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length. [0018]With reference to the second aspect, the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the mobile terminal further includes a third determining unit, where the third determining unit is configured to, if the calculated belief value is less than the preset belief decision threshold, determine that motion status of the mobile terminal cannot be identified. [0019]With reference to the second aspect, the first possible implementation manner of the second aspect, the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, the mobile terminal further includes a calculation subunit, where the calculation subunit is configured to calculate a signal fluctuation rate according to the information about the multiple WLAN access points that are acquired within the set time window length; and the mobile terminal further includes a third comparison unit, where the third comparison unit is configured to, if the calculated list orthogonality value is greater than the minimum value of the preset list orthogonality decision threshold and less than the maximum value of the list orthogonality decision threshold, compare the calculated signal fluctuation rate with a preset signal fluctuation rate decision threshold. [0020]With reference to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner of the second aspect, the method further includes a fourth determining unit and a fifth determining unit; the fourth determining unit is configured to, if the calculated signal fluctuation rate is greater than the preset signal fluctuation rate decision threshold, determine that motion status of the mobile terminal is walking; and the fifth determining unit is configured to, if the calculated signal fluctuation rate is less than or equal to the preset signal fluctuation rate decision threshold, determine that motion status of the mobile terminal is still. [0021]With reference to the second aspect, the first possible implementation manner of the second aspect, the second possible implementation manner of the second aspect, the third possible implementation manner of the second aspect, the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner of the second aspect, the mobile terminal further includes a processing unit, where the processing unit is configured to perform determining according to motion statuses of the mobile terminal within several successive time windows, and set a determined motion status, which occurs for most times in the motion statuses of the mobile terminal, of the mobile terminal as a final motion status of the mobile terminal within the several successive time windows. [0022]Compared with the prior art, the embodiments of the present disclosure provide a method for identifying a motion status of a mobile terminal using a WLAN signal to perform determining and the mobile terminal. A time window length is set, and multiple WLAN access points acquired within the set time window length are collected, such that an application scope of the method is wide, that is, the method is applicable to an area covered by multiple WLAN access points and is not limited by an indoor or outdoor site. According to the method, a calculation process is simple, that is, the motion status of the mobile terminal may be determined simply by calculating a belief value and a list orthogonality value of the multiple WLAN access points, comparing the calculated belief value with a preset belief value, and comparing the calculated list orthogonality value with a preset list orthogonality value. Therefore, implementability of the method is high and the method may be directly applied to a mobile terminal having a WLAN function in the market without making a change in hardware. Because the method has no special requirement on a placement location of the mobile terminal during measurement and is irrelevant to a posture or a motion habit of a user, the method is universal. Because a quantity of feature parameters required in the method is small and a determining method is simple, complexity of the method is lower. In addition, no additional power overhead is required in measurement and operation processes in the method, that is, power consumption of the method is low. BRIEF DESCRIPTION OF DRAWINGS [0023]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0024]FIG. 1 is a flowchart of a method for identifying a motion status of a mobile terminal according to Embodiment 1 of the present disclosure; [0025]FIG. 2 is a schematic diagram of a method for identifying a motion status of a mobile terminal according to Embodiment 1 of the present disclosure; [0026]FIG. 3 is a schematic diagram of a method for identifying a motion status of a mobile terminal within multiple time windows in a combined way according to Embodiment 1 of the present disclosure; [0027]FIG. 4 is a flowchart of another method for identifying a motion status of a mobile terminal according to Embodiment 2 of the present disclosure; [0028]FIG. 5 is a structural diagram of an apparatus of a mobile terminal according to Embodiment 3 of the present disclosure; and [0029]FIG. 6 is a structural diagram of an apparatus of a mobile terminal according to Embodiment 4 of the present disclosure. DESCRIPTION OF EMBODIMENTS [0030]To make the objectives, technical solutions, and advantages of the present disclosure clearer and more comprehensible, the following further describes the present disclosure in detail with reference to the accompanying drawings and embodiments. It should be understood that the embodiments described herein are merely used to explain the present disclosure but are not intended to limit the present disclosure. [0031]The foregoing descriptions are merely exemplary embodiments of the present disclosure, but are not intended to limit the present disclosure. Any modification, equivalent replacement, and improvement made without departing from the spirit and principle of the present disclosure shall fall within the protection scope of the present disclosure. Embodiment 1 [0032]FIG. 1 is a flowchart of a method for identifying a motion status of a mobile terminal according to Embodiment 1 of the present disclosure. As shown in FIG. 1, the method includes the following steps. [0033]Step 101: Scan for WLAN access points of the mobile terminal once every specified sampling period, and collect information about multiple WLAN access points that are acquired during each time of scanning, where the information includes a basic service set identifier and signal strength. [0034]In this step, on the premise that a WLAN function of the mobile terminal is enabled, access points (AP) are scanned for once every specified sampling period Δt, and basic service set identifiers (BSSID) and signal strength of multiple WLAN access points that are measured each time are recorded. To facilitate automatic processing of software, a result of each time of scanning may be recorded in the form of a list. For example, a form of one WLAN access point list is L={, , . . . }, and multiple WLAN access point lists, L1, . . . , Lk, Lk+1, . . . , are acquired during multiple times of scanning. [0035]One time window length T is selected, where the length T is an integral multiple of the sampling period Δt, that is, T=nΔt. Combined analysis is performed on n WLAN access point lists, Li0, Li0+1, . . . , and Li0+n-1, acquired in successive times of scanning within one time window, where a smaller subscript of a list is corresponding to a list older in a time dimension. For example, Li0+n-1 is a result of the latest time of scanning within the set time window length, and Li0 is a result of the earliest historical scanning within the set time window length. [0036]Step 102: Calculate a belief value and a list orthogonality value according to the information about the multiple WLAN access points that are acquired within a set time window length. [0037]In this step, analysis on a WLAN access point list is separately calculating a belief value (recorded as Belief) and a list orthogonality value (recorded as Orth) that are corresponding to a current time window. [0038](1) Belief value: The belief value indicates an average length of WLAN access point lists within a set time window length and expressed in a formula as: [0039]Belief=∑i=0n-1⁢ki⁢Li0+i,⁢s.t.⁢∑i=0n-1⁢ki=1,0<ki<1 [0040]|Li0+i| represents a length of the list Li0+i (that is, a quantity of included access points), and k1 is a weight factor. Preferably, 0⁢∑i=0n-2⁢wi=1,0<wi<1 [0045]|Li0+n-1 ∪ Li0+l| represents a quantity of all access points in Li0n-1 and Li0+l, and a unique BSSID may be used to ensure that duplicate access points are not repeatedly counted. Preferably, 0⁢∑i=0n-2⁢wi=1 [0048]|Li0+n-1 ∩ Li0+i represents a quantity of duplicate access points between Li0+n-1 and Li0+i. [0049]The calculating a list orthogonality value includes comparing, within the set time window length, information about multiple WLAN access points that are acquired during the first time of scanning with information about multiple WLAN access points that are acquired during the second time of scanning to acquire information about non-duplicate WLAN access points that are acquired during the two times of scanning; acquiring, according to a preset degree-of-contribution function, a degree of contribution of signal strength of each of the non-duplicate WLAN access points to the list orthogonality value; adding degrees of contribution of all of the non-duplicate WLAN access points; multiplying a value, which is acquired by the adding, by a preset second time dimension weight factor to acquire an average degree of contribution, adding a quantity of non-duplicate WLAN access points and a quantity of duplicate WLAN access points that are acquired during the two times of scanning to acquire a quantity of WLAN access points; and dividing the average degree of contribution by the quantity of WLAN access points to acquire a list orthogonality value of the first time of scanning, where a list orthogonality value of the second time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the second time of scanning with information about multiple WLAN access points that are acquired during the third time of scanning, a list orthogonality value of the third time of scanning is acquired by comparing the information about the multiple WLAN access points that are acquired during the third time of scanning with information about multiple WLAN access points that are acquired during the fourth time of scanning, and so on, and a list orthogonality value of the (N−1)th time of scanning is acquired, assuming that in total N times of scanning are performed in the specified sampling periods within the set time window length; and adding the list orthogonality values of the first time of scanning, the second time of scanning, . . . , and the (N−1)th time of scanning to acquire a list orthogonality value of the N times of scanning within the set time window length. [0050]The list orthogonality value reflects an update speed of a list of WLAN signals acquired by several adjacent times of scanning, and higher orthogonality indicates that a user may move at a higher speed. The list orthogonality value is related to a quantity of orthogonal APs in results of several successive times of scanning and related to signal strength. A larger quantity of orthogonal APs indicates a larger list orthogonality value, and higher signal strength of the orthogonal APs also indicates a larger list orthogonality value. The quantity of orthogonal APs refers to a quantity of APs that do not occur at the same time in results of two times of scanning. [0051]Optionally, the method further includes calculating a signal fluctuation rate (recorded as Ed). [0052](3) Signal fluctuation rate: The signal fluctuation rate indicates a status of a change in signal strength of related access points in two adjacent lists within a set time window length, and is measured using an average Euclidean distance: [0053]Ed=∑i=0n-2⁢αi⁢∑APm∈Li0+n-1⋂Li0+i⁢(PLi0+n-1APm-PLi0+iAPm)2Li0+n-1⋂Li0+i,⁢s.t.⁢∑i=0n-2⁢αi=1,0<αi<1 where [0054](PLi0+n-1APm-PLi0+iAPm) represents a difference between strength of related signals from a same access point. Preferably, 0<α1≦α2≦ . . . ≦αn-2<1 may be set, such that an item fresher in a time dimension indicates a larger weight. [0055]A change in signal strength of an AP is determined using a value of a signal fluctuation rate. If the signal fluctuation rate is large, it may be determined that a motion status of a mobile terminal is walking or driving, and if the signal fluctuation rate is small, it may be determined that a motion status of a mobile terminal is still. [0056]Step 103: Compare the calculated belief value with a preset belief decision threshold. [0057]In this step, the comparing the calculated belief value with a preset belief decision threshold includes, if the calculated belief value is less than the belief decision threshold, determining that the motion status of the mobile terminal cannot be identified. [0058]Step 104: When the calculated belief value is greater than the preset belief decision threshold, compare the calculated list orthogonality value with a preset list orthogonality decision threshold. [0059]Step 105: If the calculated list orthogonality value is less than a minimum value of the preset list orthogonality decision threshold, determine that motion status of the mobile terminal is still. [0060]Step 106: If the calculated list orthogonality value is greater than a maximum value of the preset list orthogonality decision threshold, determine that the motion status of the mobile terminal is driving. [0061]Further, when the calculated belief value is grea(String), 相关申请的交叉引用 [0001] 本申请是2013年11月13日提交的国际申请No.PCT / CN2013 / 087024的延续,其要求2013年4月28日提交的中国专利申请No.201310157676.7的优先权,其全部内容通过引用合并于此。 全文参考。 技术领域 [0002] 本发明涉及通信领域,尤其涉及一种识别移动终端运动状态的方法及移动终端。 背景 [0003] 运动状态识别是情境感知的重要内容之一。 随着移动终端的普及,通过使用移动终端推断用户的运动状态,并根据用户的运动状态触发状态或动作的变化,可以为用户提供具有更好体验的智能服务。 移动终端的功能,并根据推断出的更高级别的用户情况为用户提供智能移动应用程序,例如个性化推荐或准确的广告推送。 在移动终端应用场景中,运动状态识别的困难和挑战是如何使用大多数移动终端中内置的传感器在复杂而多变的环境中对不同用户的运动进行准备好的识别,而无需借助其他硬件的功能。 考虑到终端的有限的计算,存储和能量资源,运动状态识别中涉及的算法尽可能简单,并且从属功能模块不能产生大量的额外功能开销。 [0004] 通过卫星定位(例如,全球定位系统(GPS))来对用户进行定位,并且将时间间隔内的经度之间的差和纬度之间的差转换为运动速度,以间接地推断出用户的运动状态。 用户。 这种方式需要额外启用卫星定位功能。 通常,移动终端上GPS的功耗较高; 首次修复的时间更长; 并且这种方式通常不能在阴影区域(例如,室内或地下通道)中使用。 [0005] 借助于特征提取,分类和其他手段并且根据由诸如加速度传感器或陀螺仪的惯性传感器收集的数据来推断用户的运动状态。 使用该方法进行识别的准确性受手机放置位置的影响更大,并且与用户的姿势和运动习惯密切相关。 算法复杂度通常更高; 并且需要提前收集大量的训练样本。 [0006] 对传统无线蜂窝网络中基站的无线信号强度数据进行标准差分析,根据标准差区分静止和运动状态,然后对样本中的信号序列和波形进行特征匹配。 该库可以区分两种运动类型:“行走”和“驾驶”。 当区分“行走”和“行驶”两种运动类型时,需要实时对波形执行相似性分析。 一方面,计算复杂度较高,给移动终端的处理能力带来了挑战。 另一方面,需要预先收集并存储信号样本,并且当样本库中有大量数据时,负担增加了移动终端的有限存储空间。 概要 [0007] 本公开的实施例的目的是提供一种用于识别移动终端的运动状态的方法和一种移动终端,以解决关于如何确定移动终端的运动状态的问题。 [0008] 根据第一方面,提供了一种用于识别移动终端的运动状态的方法,其中,该方法包括:每隔指定的采样时间扫描一次移动终端的无线局域网(WLAN)接入点;以及收集关于多个终端的信息。 在每次扫描期间获取的WLAN接入点,其中的信息包括基本服务集标识符和信号强度; 根据在设置的时间窗口长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交性值; 将计算出的置信度值与预设的置信度决策阈值进行比较; 当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较; 如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止; 如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0009] 结合第一方面,在第一方面的第一种可能的实现方式中,所述计算置信度值包括:将在每个指定采样周期进行的扫描中获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子, 每次扫描后计算平均WLAN接入点数量; 将所有无线局域网接入点的平均数量相加得到置信度值,在设定的时间窗口长度内计算出平均数量。 [0010] 结合第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,所述计算列表正交性值包括:在所述设置的时间窗长度内,比较在所述时间间隔内获取的多个WLAN接入点的信息。 第一次扫描使用第二次扫描期间获取的有关多个WLAN接入点的信息来获取两次扫描期间获取的有关非重复的WLAN接入点的信息; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获得第三次扫描的列表正交性值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0011] 结合第一方面,第一方面的第一种可能的实现方式,或第一方面的第二种可能的实现方式,在第一方面的第三种可能的实现方式中,所述方法还包括:如果计算出的置信度为 小于预设的信念判定阈值,确定不能识别出移动终端的运动状态。 [0012] 结合第一方面,第一方面的第一种可能的实现方式,第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中, 该方法还包括根据在设置的时间窗口长度内获取的关于多个WLAN接入点的信息来计算信号波动率,如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于 在列表正交性判定阈值的最大值之外,将计算出的信号波动率与预设信号波动率判定阈值进行比较。 [0013] 结合第一方面的第四种可能的实现方式,在第一方面的第五种可能的实现方式中,所述方法还包括:如果计算出的信号波动率大于预设信号波动率决策阈值,则确定运动 移动终端的状态为步行; 如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定移动终端的运动状态为静止。 [0014] 结合第一方面或第一方面的第一种可能的实现方式,或结合第一方面的第二种可能的实现方式,第一方面的第三种可能的实现方式,第一方面的第四种可能的实现方式 或第一方面的第五种可能的实现方式,在第一方面的第六种可能的实现方式中,所述方法还包括:根据所述移动终端在多个连续的时间窗内的运动状态进行确定,并设置确定的运动状态; 在移动终端的运动状态中大多数时间出现在移动终端的运动状态中,作为移动终端在几个连续时间窗口内的最终运动状态。 [0015] 根据第二方面,提供了一种移动终端,其中,该移动终端提供收集单元,该收集单元被配置为每隔指定的采样时间扫描一次该移动终端的WLAN接入点,并收集关于在每个接入点期间获取的多个WLAN接入点的信息。 扫描时间,其中信息包括基本服务集标识符和信号强度; 计算单元,用于根据在设定的时间窗口长度内获取的与多个WLAN接入点的信息,计算置信度值和列表正交度值; 第一比较单元,用于将计算出的置信度值与预设的置信度决策阈值进行比较; 第二比较单元,用于当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较; 第一确定单元,用于如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止; 第二确定单元,用于如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0016] 结合第二方面,在第二方面的第一种可能的实现方式中,所述计算单元计算所述置信度值的步骤是将在每个指定采样周期进行的扫描中获取的多个WLAN接入点的数量乘以预设值 第一时间维度权重因子,用于计算每次扫描后WLAN接入点的平均数量; 将所有无线局域网接入点的平均数量相加得到置信度值,在设定的时间窗口长度内计算出平均数量。 [0017] 结合第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,所述计算单元计算列表正交性值的步骤是在设定的时间窗长度内比较多个WLAN的信息。 第一次扫描时获取的接入点,以及第二次扫描时获取的多个WLAN接入点的信息,以获取两次扫描时获取的非重复的WLAN接入点的信息; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加而获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度,然后将非重复的WLAN接入点的数量与在该过程中获取的重复的WLAN接入点的数量相加。 进行两次扫描以获得一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值; 其中,通过将第二次扫描获取的多个WLAN接入点的信息与第三次扫描获取的多个WLAN接入点的信息进行比较,得到第二次扫描的列表正交值。 通过将在第三次扫描期间获取的有关多个WLAN接入点的信息与在第四次扫描期间获取的有关多个WLAN接入点的信息进行比较,等等,获得第三次扫描的正交性值,依此类推, 和(N-1)的列表正交性值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0018] 结合第二方面,第二方面的第一种可能的实现方式,或第二方面的第二种可能的实现方式,在第二方面的第三种可能的实现方式中,所述移动终端还包括第三确定单元, 第三确定单元,如果计算出的置信度值小于预设的置信度判定阈值,则确定无法识别出移动终端的运动状态。 [0019] 结合第二方面,第二方面的第一种可能的实现方式,第二方面的第二种可能的实现方式或第二方面的第三种可能的实现方式,在第二方面的第四种可能的实现方式中, 所述移动终端还包括计算子单元,计算子单元,用于根据所述设定的时间窗长度内获取的所述多个WLAN接入点的信息,计算信号波动率; 所述移动终端还包括第三比较单元,所述第三比较单元,用于如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于列表正交性判定的最大值, 阈值,将计算出的信号波动率与预设信号波动率决策阈值进行比较。 [0020] 结合第二方面的第四种可能的实现方式,在第二方面的第五种可能的实现方式中,所述方法还包括:第四确定单元和第五确定单元; 第四确定单元,用于如果计算出的信号波动率大于预设信号波动率决策阈值,则确定移动终端的运动状态为步行; 第五确定单元,用于如果计算出的信号波动率小于或等于预设信号波动率判定阈值,则确定移动终端的运动状态为静止。 [0021] 结合第二方面,第二方面的第一种可能的实现方式,第二方面的第二种可能的实现方式,第二方面的第三种可能的实现方式,第二方面的第四种可能的实现方式,或第五种 第二方面的可能的实现方式,在第二方面的第六的可能的实现方式中,所述移动终端还包括处理单元,所述处理单元,用于在多个连续的时间窗内根据所述移动终端的运动状态进行确定。 ,并将在移动终端的运动状态中最多出现的确定的运动状态设置为移动终端在几个连续时间窗口内的最终运动状态。 [0022] 相较于现有技术,本发明实施例提供了一种利用无线局域网络信号进行移动终端识别移动终端运动状态的方法。 设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此该方法的应用范围较广,即该方法适用于多个WLAN接入点覆盖的区域,并且 不受室内或室外场所的限制。 根据该方法,计算过程很简单,也就是说,可以通过将多个WLAN接入点的置信度值和列表正交性值与预设值进行比较来简单地确定移动终端的运动状态。 置信度值,并将计算出的列表正交性值与预设列表正交性值进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 附图说明 [0023] 为了更清楚地描述本发明实施例中的技术方案,以下简要介绍用于描述实施例所需的附图。 以下描述中的附图仅示出了本公开的一些实施例,并且本领域普通技术人员仍可以在不付出创造性劳动的情况下从这些附图中得出其他附图。 [0024] 图。 附图说明图1是根据本发明实施例一的识别移动终端运动状态的方法的流程图。 [0025] 图。 图2是根据本发明实施例一的识别移动终端运动状态的方法的示意图; [0026] 图。 图3是根据本发明实施例一的在多个时间窗口内以组合方式识别移动终端的运动状态的方法的示意图; [0027] 图。 图4是根据本发明实施例二的另一种识别移动终端运动状态的方法的流程图; [0028] 图。 图5是根据本发明实施例三的移动终端的装置的结构图; 和 [0029] 图。 图6是根据本发明实施例四的移动终端的装置的结构图。 具体实施方式 [0030] 为了使本发明的目的,技术方案和优点更加清楚和理解,以下结合附图和实施例,对本发明进行进一步详细描述。 应当理解,本文所述实施例仅用于解释本发明,并不用于限制本发明。 [0031] 前述描述仅是本公开的示例性实施例,而无意于限制本公开。 凡在本发明的精神和原则之内,所作的任何修改,等同替换,改进等,均应包含在本发明的保护范围之内。 实施例1 [0032] 图。 图1是根据本公开的实施例1的识别移动终端的运动状态的方法的流程图。 如图1所示。 参照图1,该方法包括以下步骤。 [0033] 步 101 :每个指定的采样周期扫描一次移动终端的WLAN接入点,并收集每次扫描期间获取的多个WLAN接入点的信息,其中包括基本服务集标识符和信号强度。 [0034] 在该步骤中,在使能移动终端的WLAN功能的前提下,每隔规定的采样周期Δt对接入点(AP)进行一次扫描,并对多个WLAN接入点的基本业务集标识(BSSID)和信号强度进行扫描。 每次记录都测量。 为了促进软件的自动处理,可以以列表的形式记录每次扫描的结果。 例如,一个WLAN接入点列表的形式为L = { , ,。 。 。 },以及多个WLAN接入点列表L 1 ,。 。 。 ,L k ,L k+1 ,。 。 。 ,是在多次扫描中获取的。 [0035] 选择一个时间窗长度T,其中长度T是采样周期Δt的整数倍,即,T =nΔt。 对n个WLAN接入点列表Li进行组合分析 0 ,李 0+1 ,。 。 。 和李 0+n-1 在一个时间窗口内连续扫描获得的,其中列表的较小下标对应于在时间维度上较旧的列表。 例如李 0+n-1 是在设定的时间范围内扫描的最新时间的结果, 0 是在设置的时间窗口长度内最早进行历史扫描的结果。 [0036] 步 102 :根据在设置的时间窗长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交性值。 [0037] 在此步骤中,对WLAN接入点列表的分析分别计算与当前时间窗口相对应的置信度值(记录为Belief)和列表正交性值(记录为Orth)。 [0038] (1)置信度:置信度值表示设置的时间范围内的WLAN接入点列表的平均长度,用以下公式表示: [0039] 信仰 = ∑ i = 0 n - 1 ⁢ k i ⁢ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 1 ⁢ k i = 1 , 0 < k i < 1 [0040] | L i 0 +i | 代表列表的长度L i 0 +i (即,所包含的接入点的数量),以及k 1 是一个重量因素。 最好是0 Orth = ∑ i = 0 n - 2 ⁢ w i ⁢ ∑ 美联社 t ∉ ( L i 0 + n - 1 ⋂ L i 0 + i ) ⁢ C ⁡ ( P 美联社 t ) L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 , 0 < w i < 1 [0045] | L i 0 +n-1 ∪ i 0 +l | 表示L中所有接入点的数量 i 0 n-1 和我 i 0 +l ,并且可以使用唯一的BSSID来确保不会重复计算重复的访问点。 最好是0 Orth = 1 - 柯尔 = 1 - ∑ i = 0 n - 2 ⁢ w i ⁢ L i 0 + n - 1 ⋂ L i 0 + i L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 [0048] | L i 0 +n-1 ∩ i 0 +i 表示L之间的重复访问点数量 i 0 +n-1 和我 i 0 +i 。 [0049] 计算列表正交性值包括在设置的时间窗口长度内,将关于在第一次扫描期间获取的多个WLAN接入点的信息与关于在第二次扫描期间获取的多个WLAN接入点的信息进行比较以获取信息。 关于两次扫描中获取的非重复的WLAN接入点; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加而获得的值乘以预设的第二时间维度权重因子以获取平均贡献度,然后将非重复的WLAN接入点的数量和在此期间获取的重复的WLAN接入点的数量相加 进行两次扫描以获取一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获取第三次扫描的列表正交值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0050] 列表正交性值反映通过几次相邻扫描而获取的WLAN信号的列表的更新速度,并且更高的正交性表示用户可以以更高的速度移动。 列表正交值与几次连续扫描的结果中的正交AP的数量有关,并且与信号强度有关。 正交AP的数量越大,列表正交性值越大,正交AP的信号强度越高,列表正交性值越大。 正交AP的数量是指两次扫描的结果中不同时出现的AP的数量。 [0051] 可选地,该方法还包括计算信号波动率(记录为Ed)。 [0052] (3)信号波动率:信号波动率表示在设定的时间窗口长度内两个相邻列表中相关接入点的信号强度变化的状态,并使用平均欧几里德距离来测量: [0053] 埃德 = ∑ i = 0 n - 2 ⁢ α i ⁢ ∑ 美联社 m ∈ L i 0 + n - 1 ⋂ L i 0 + i ⁢ ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 2 L i 0 + n - 1 ⋂ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ α i = 1 , 0 < α i < 1 哪里 [0054] ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 代表来自同一接入点的相关信号强度之间的差异。 最好是0 <α 1 ≦α 2 ≦。 。 。 ≦α n-2 可以设置<1,以便在时间维度上较新的商品表示重量更大。 [0055] 使用信号波动率的值来确定AP的信号强度的变化。 如果信号波动率大,则可以确定移动终端的运动状态为步行或驾驶,并且如果信号波动率小,则可以确定移动终端的运动状态为静止。 [0056] 步 103 :将计算出的置信度值与预设的置信度决策阈值进行比较。 [0057] 在该步骤中,将计算出的置信度值与预设置信度决策阈值进行比较包括:如果计算出的置信度值小于置信度决策阈值,则确定不能识别出移动终端的运动状态。 [0058] 步 104 :当计算出的置信度值大于预设置信度决策阈值时,将计算出的列表正交性值与预设列表正交性决策阈值进行比较。 [0059] 步 105 :如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止。 [0060] 步 106 :如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0061] 此外,当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较。 [0062] 将计算出的列表正交性值与预设列表正交性判定阈值进行比较包括:如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止。 [0063] 此外,如果计算出的列表正交性值大于列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0064] 此外,如果计算出的列表正交性值大于列表正交性判定阈值的最小值并且小于列表正交性判定阈值的最大值,则将计算出的信号波动率与预设信号波动率判定阈值进行比较。 [0065] 该方法还包括:如果计算出的信号波动率大于预设信号波动率决策阈值,则确定移动终端的运动状态为行走; 如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定移动终端的运动状态为静止。 [0066] 如图1所示。 如图2所示。 图2是根据本公开的实施例的识别移动终端的运动状态的示意图。 如图1所示。 参照图2,在信念值大于阈值的前提下,首先使用列表正交性值的第一阈值Orth_th_low和第二阈值Orth_th_high来区分运动状态中的两个极端状态(行驶和静止)。 例如,当计算出的移动终端的列表正交度值小于第一阈值时,确定移动终端的运动状态为静止; 当计算出的所述移动终端的列表正交性值大于所述第二阈值时,确定所述移动终端的运动状态为驾驶中。 对于其余情况,使用信号波动率的阈值区分两个较平缓的运动状态(静止和行走)。 [0067] 需要说明的是,在实际应用中,在上述确定当前时间窗口内的运动状态的过程中,可以同时进行三个特征参数的计算,从而避免了不必要的计算开销,提高了确定速度。 首先,计算置信度值。 假设置信度值小于阈值,则输出直接无效,无需计算列表正交性值和信号波动率两个参数。 如果置信度值大于阈值,则计算列表正交性值。 假设列表正交性值小于第一阈值或大于第二阈值,则对应的输出为“静止”或“驱动”,并且不需要计算信号波动率。 仅当置信度值大于阈值并且列表正交性值在第一阈值和第二阈值之间时才需要计算信号波动率,并且根据信号波动率和阈值之间的关系进行确定。 [0068] 优选地,根据所述移动终端在几个连续的时间窗内的运动状态进行判断,并将确定的运动状态设置为最终运动状态,所述确定的运动状态在所述移动终端的运动状态中最多出现。 在几个连续的时间窗口内移动终端的时间间隔。 [0069] 如图1所示。 如图3所示。 图3是根据本公开实施例的用于以组合方式识别多个时间窗内的移动终端的运动状态的方法的示意图。 为了减少由信号抖动引起的错误确定,可以根据几个连续的时间窗口进一步执行组合确定,以选择在大多数情况下出现的运动状态作为最终结果。 图。 图3是在三个时间窗口内进行组合确定的示意图。 如果在三个连续的时间窗口中出现的运动状态数量大于或等于两次,则认为运动状态是确定的最终结果。 从图2可以看出。 3结合多个时间窗口进行确定可以有效避免频繁跳频。 [0070] 附表1 阈 阈 参数 值 信仰 日 3 Orth 日 — 低 0.2 Orth 日 — 高 0.7 埃德 日 2 [0071] 作为实施例,请参考附表1。首先,每Δt= 16秒(s)扫描一次有关WLAN接入点的信息。 假设在前三次连续扫描中获取的WLAN接入点列表分别为: 大号 1 = { , , , } L2={ , , } L3={ , , } [0072] 然后,分析在扫描期间获取的WLAN接入点列表。 如果使用时间窗口长度T = 48s,则在一个时间窗口内包括三次扫描,即n = 3。 设置三个功能的阈值,如附表1所示。 [0073] 对应于第一时间窗口(包括三个列表,L)的三个参数的计算,即置信度值(记录为Belief),列表正交性值(记录为Orth)和信号波动率(记录为Ed)。 1 ,L 2 , 和我 3 )用作下面的示例。 [0074] (1)信念值:如果加权值k 0 =⅙,k 1 =⅓和k 2 使用= 1/2,置信度值表示为: [0075] 信仰 = ⁢ k 1 · L 1 + k 2 · L 2 + k 3 · L 3 = ⁢ 4 / 6 + 3 / 3 + 3 / 2 = ⁢ 3.2 > 信仰 日 [0076] (2)列表正交值:如果加权值w 0 =⅓和w 1 使用=⅔,贡献度函数C(P 美联社 t )定义为: [0077] C ⁡ ( P 美联社 t ) = { 1 , P ≥ - 60 0.9 , - 80 ≤ P < - 60 0.8 , P < - 80 [0078] 因为L的正交接入点集 3 和我 1 是{ , , },以及L的正交接入点集 3 和我 2 是{ , },列表正交性值为: [0079] Orth = ⁢ w 1 ⁢ ∑ 美联社 t ∉ L 1 ⋂ L 3 ⁢ C ⁡ ( P 美联社 t ) L 1 ⋃ L 3 + w 2 ⁢ ∑ 美联社 l ∉ L 2 ⋂ L 3 ⁢ C ⁡ ( P 美联社 l ) L 2 ⋃ L 3 = ⁢ 1 3 · C ⁡ ( - 55 ) + C ⁡ ( - 71 ) + C ⁡ ( - 70 ) 5 + 2 3 · C ⁡ ( - 60 ) + C ⁡ ( - 70 ) 4 = ⁢ 1 3 · 1 + 0.9 + 0.9 5 + 2 3 · 1 + 0.9 4 = ⁢ 0.33 ∈ ( Orth 低 , Orth 高 ) [0080] (3)信号波动率:加权值α 0 =⅓和α 1 使用=⅔,信号波动率是: [0081] 埃德 = ⁢ 1 3 · ( 77 - 73 ) 2 + ( 92 - 80 ) 2 2 + 2 3 · ( 80 - 77 ) 2 + ( 86 - 80 ) 2 2 = ⁢ 4.345 > 埃德 日 [0082] 根据预设的阈值和上述三个草图值,可以推断出当前时间窗内的运动状态为“行走”。 [0083] 作为另一实施例,首先每Δt= 16s扫描关于WLAN接入点的信息。 假设在前三次连续扫描中获取的WLAN接入点列表分别为: 大号 1 = { , , , } L2={ , } L3={ , , , } [0084] 以相同的方式,使用时间窗口长度T = 48s,即n = 3。 下面显示了特征计算和确定过程。 随附表1中的值仍用作阈值。 [0085] (1)信念值:如果加权值k 0 =⅙,k 1 =⅓和k 2 使用= 1/2,置信度值表示为: [0086] 信仰 = ⁢ k 1 · L 1 + k 2 · L 2 + k 3 · L 3 = ⁢ 4 / 6 + 2 / 3 + 4 / 2 = ⁢ 3.33 > 信仰 日 [0087] (2)列表正交值:如果加权值w 0 =⅓和w 1 =⅔,使用贡献度函数C(P 美联社 t )= 1,列表正交性值为: [0088] Orth = ⁢ 1 - 柯尔 = ⁢ 1 - ( w 0 ⁢ L 1 ⋂ L 3 L 1 ⋃ L 3 + w 1 ⁢ L 2 ⋂ L 3 L 2 ⋃ L 3 ) = ⁢ 1 - ( 1 3 · 1 7 + 2 3 · 1 5 ) = ⁢ 0.822 > Orth 高 [0089] 因此,当前时间窗口内的运动状态为“行驶中”。 [0090] 本公开的实施例提供一种用于使用WLAN信号来执行确定的识别移动终端的运动状态的方法。 设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此该方法的应用范围较广,即该方法适用于多个WLAN接入点覆盖的区域 并且不受室内或室外场所的限制。 根据该方法,计算过程很简单,也就是说,可以通过将多个WLAN接入点的置信度值和列表正交性值与预设值进行比较来简单地确定移动终端的运动状态。 置信度值,并将计算出的列表正交性值与预设列表正交性值进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 实施例2 [0091] 图。 图4为本发明实施例二提供的另一种识别移动终端运动状态的方法的流程图。 如图1所示。 参照图4,该方法包括以下步骤。 [0092] 步 401 :每个指定的采样周期扫描一次移动终端的WLAN接入点,并收集每次扫描期间获取的多个WLAN接入点的信息,其中包括基本服务集标识符和信号强度。 [0093] 在该步骤中,在使能移动终端的WLAN功能的前提下,每隔规定的采样周期Δt对AP进行一次扫描,并记录每次测量的多个WLAN接入点的BSSID和信号强度。 为了促进软件的自动处理,可以以列表的形式记录每次扫描的结果。 例如,一个WLAN接入点列表的形式为L = { , ,。 。 。 },以及多个WLAN接入点列表L 1 ,。 。 。 ,L k ,L k+1 ,。 。 。 ,是在多次扫描中获取的。 [0094] 选择一个时间窗长度T,其中长度T是采样周期Δt的整数倍,即,T =nΔt。 对n个WLAN接入点列表Li进行组合分析 0 ,李 0+1 ,。 。 。 和李 0+n-1 在一个时间窗口内连续扫描获得的,其中列表的较小下标对应于在时间维度上较旧的列表。 例如李 0+n-1 是在设定的时间范围内扫描的最新时间的结果, 0 是在设置的时间窗口长度内最早进行历史扫描的结果。 [0095] 步 402 :根据在预设时间窗口长度内获取的与多个WLAN接入点有关的信息,计算置信度值,列表正交性值和信号波动率。 [0096] 在这一步骤中,对WLAN接入点列表的分析分别计算出三个参数,分别为置信度值(记录为Belief),列表正交性值(记录为Orth)和信号波动率(记录为Ed)。 到当前时间窗口。 [0097] (1)置信度:置信度值表示设置的时间范围内的WLAN接入点列表的平均长度,用以下公式表示: [0098] 信仰 = ∑ i = 0 n - 1 ⁢ k i ⁢ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 1 ⁢ k i = 1 , 0 < k i < 1 [0099] | L i 0 +i |表示列表的长度L i 0 +i (即,所包含的接入点的数量),以及k i 是一个重量因素。 最好是0 Orth = ∑ i = 0 n - 2 ⁢ w i ⁢ ∑ 美联社 t ∉ ( L i 0 + n - 1 ⋂ L i 0 + i ) ⁢ C ⁡ ( P 美联社 t ) L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 , 0 < w i < 1 [0103] | L i 0 +n-1 ∪ i 0 +i | 表示L中所有接入点的数量 i 0 +n-1 , 和我 i 高清+ i ,并且可以使用唯一的BSSID来确保不会重复计算重复的访问点。 最好是0 Orth = 1 - 柯尔 = 1 - ∑ i = 0 n - 2 ⁢ w i ⁢ L i 0 + n - 1 ⋂ L i 0 + i L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 [0106] | L i 0 +n-1 ∩ i 0 +i | 表示L之间的重复访问点数量 i 0 +n-1 和我 i 0 +i 。 [0107] 计算列表正交性值包括预先设置贡献度函数,其中,所述贡献度函数是信号强度的非递减函数,并且指示具有较高信号强度的WLAN接入点的贡献度为: 列表正交性值较高; 在设置的时间窗口长度内,将有关在第一次扫描期间获取的多个WLAN接入点的信息与有关在第二次扫描期间获取的多个WLAN接入点的信息进行比较,以获取有关非重复的WLAN接入点的信息 在两次扫描中获取的; 根据贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值。 通过将关于在第二次扫描期间获取的多个WLAN接入点的信息与关于在第三次扫描期间获取的多个WLAN接入点的信息进行比较,来获取第二次扫描的列表正交值。 通过将在第三次扫描期间获取的有关多个WLAN接入点的信息与在第四次扫描期间获取的有关多个WLAN接入点的信息进行比较,来获取第三次扫描的正交性值,依此类推, 和(N-1)的列表正交性值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0108] (3)信号波动率:信号波动率表示在设定的时间窗口长度内两个相邻列表中相关接入点的信号强度变化的状态,并使用平均欧几里德距离来测量: [0109] 埃德 = ∑ i = 0 n - 2 ⁢ α i ⁢ ∑ 美联社 m ∈ L i 0 + n - 1 ⋂ L i 0 + i ⁢ ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 2 L i 0 + n - 1 ⋂ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ α i = 1 , 0 < α i < 1 哪里 [0110] ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 代表来自同一接入点的相关信号强度之间的差异。 最好是0 <α 1 ≦α 2 ≦。 。 。 ≦α n-2 可以设置<1,以便在时间维度上较新的商品表示重量更大。 [0111] 步 403 :预设置信度判定阈值,列表正交性判定阈值和信号波动率判定阈值。 [0112] 步 404 :确定置信度值是否小于置信度决策阈值。 如果置信度值小于置信度决策阈值,请继续执行步骤 405 。 如果置信度值不小于置信度判定阈值,则执行步骤 406 。 [0113] 步 405 :如果置信度值小于预设的置信度决策阈值,则认为AP太稀疏,因此输出结果无效。 [0114] 步 406 :确定列表正交性值是否小于第一列表正交性判定阈值。 如果列表正交性值小于第一列表正交性判定阈值,则继续执行步骤 407 ,如果列表正交性值不小于第一列表正交性判定阈值,则执行步骤 408 。 [0115] 步 407 :如果列表正交性值小于第一列表正交性判定阈值,则确定移动终端的当前运动状态为静止。 [0116] 步 408 :确定列表正交性值是否大于第二列表正交性判定阈值。 如果列表正交性值大于第二列表正交性判定阈值,则继续执行步骤 409 ,如果列表正交性值不大于第二列表正交性判定阈值,则执行步骤 410 。 [0117] 步 409 :如果列表正交性值大于第二列表正交性判定阈值,则确定移动终端的当前运动状态为驾驶中。 [0118] 步 410 :确定信号波动率是否大于信号波动率值阈值。 如果信号波动率大于信号波动率值阈值,请继续执行步骤 411 ,如果信号波动率不大于信号波动率阈值,执行步骤 412 。 [0119] 步 411 :如果信号波动率大于信号波动率值阈值,请确定移动终端当前的运动状态为步行。 [0120] 步 412 :如果信号波动率小于或等于信号波动率值阈值,请确定移动终端当前的运动状态为静止。 [0121] 本公开的实施例提供一种用于使用WLAN信号来执行确定的识别移动终端的运动状态的方法。 设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此该方法的应用范围较广,即该方法适用于多个WLAN接入点覆盖的区域 并且不受室内或室外场所的限制。 根据该方法,计算过程是简单的,即,可以通过计算多个WLAN接入点的置信度值,列表正交性值和信号波动率来简单地确定移动终端的运动状态。 将计算出的置信度值与预设置信度值进行比较,将计算出的列表正交度值与预设列表正交度值进行比较,并将计算出的信号波动率与预设信号波动率进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 实施例3 [0122] 图。 图5是根据本发明实施例三的移动终端的装置的结构图。 如图1所示。 参照图5,移动终端包括以下单元。 [0123] 收集单元 501 配置为每个指定的采样周期扫描一次移动终端的WLAN接入点,并收集每次扫描期间获取的多个WLAN接入点的信息,所述信息包括基本服务集标识和信号强度。 [0124] 根据该单元,在启用移动终端的WLAN功能的前提下,每隔指定的采样周期Δt扫描AP一次,并且记录每次测量的多个WLAN接入点的BSSID和信号强度。 为了促进软件的自动处理,可以以列表的形式记录每次扫描的结果。 例如,一个WLAN接入点列表的形式为L = { , ,。 。 。 },以及多个WLAN接入点列表L 1 ,。 。 。 ,L k ,L k+1 ,。 。 。 ,是在多次扫描中获取的。 [0125] 选择一个时间窗长度T,其中长度T是采样周期Δt的整数倍,即,T =nΔt。 对n个WLAN接入点列表Li进行组合分析 0 ,李 +1 ,。 。 。 和李 0+n-1 在一个时间窗口内连续扫描获得的,其中列表的较小下标对应于在时间维度上较旧的列表。 例如李 0+n-1 是在设定的时间范围内扫描的最新时间的结果, 0 是在设置的时间窗口长度内最早进行历史扫描的结果。 [0126] 计算单位 502 配置为根据在设置的时间窗长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交度值。 [0127] 根据该单元,对WLAN接入点列表的分析分别计算与当前时间窗口相对应的置信度值(记录为信度)和列表正交性值(记录为Orth)。 [0128] (1)置信度:置信度值表示设置的时间范围内的WLAN接入点列表的平均长度,用以下公式表示: [0129] 信仰 = ∑ i = 0 n - 1 ⁢ k i ⁢ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 1 ⁢ k i = 1 , 0 < k i < 1 [0130] | L i 0 +i | 代表列表的长度L i 0 +i (即,所包含的接入点的数量),以及k i 是一个重量因素。 最好是0 Orth = ∑ i = 0 n - 2 ⁢ w i ⁢ ∑ 美联社 t ∉ ( L i 0 + n - 1 ⋂ L i 0 + i ) ⁢ C ⁡ ( P 美联社 t ) L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 , 0 < w i < 1 [0134] | L i 0 +n-1 ∪ i 0 +i | 表示L中所有接入点的数量 i 0 +n-1 和我 i 0 +i ,并且可以使用唯一的BSSID来确保不会重复计算重复的访问点。 最好是0 Orth = 1 - 柯尔 = 1 - ∑ i = 0 n - 2 ⁢ w i ⁢ L i 0 + n - 1 ⋂ L i 0 + i L i 0 + n - 1 ⋃ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ w i = 1 [0137] | L i 0 +n-1 ∩ i 0 +i | 表示L之间的重复访问点数量 i 0 +n-1 和我 i 0 +i 。 [0138] 计算单元计算列表正交性值的步骤包括:预先设置贡献度函数,其中,贡献度函数是信号强度的非递减函数,表示WLAN接入的贡献度 信号强度较高的点到列表正交值较高; 在设置的时间窗口长度内,将有关在第一次扫描期间获取的多个WLAN接入点的信息与有关在第二次扫描期间获取的多个WLAN接入点的信息进行比较,以获取有关非重复的WLAN接入点的信息 在两次扫描中获取的; 根据贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获取第三次扫描的列表正交值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0139] 可选地,计算单元还包括计算子单元,计算子单元用于计算信号波动率。 [0140] (3)信号波动率:信号波动率表示在设定的时间窗口长度内两个相邻列表中相关接入点的信号强度变化的情况,并使用平均欧几里德距离来测量: [0141] 埃德 = ∑ i = 0 n - 2 ⁢ α i ⁢ ∑ 美联社 m ∈ L i 0 + n - 1 ⋂ L i 0 + i ⁢ ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 2 L i 0 + n - 1 ⋂ L i 0 + i , ⁢ s . t . ⁢ ∑ i = 0 n - 2 ⁢ α i = 1 , 0 < α i < 1 哪里 [0142] ( P L i 0 + n - 1 美联社 m - P L i 0 + i 美联社 m ) 代表来自同一接入点的相关信号强度之间的差异。 最好是0 <α 1 ≦α 2 ≦。 。 。 ≦α n-2 可以设置<1,以便在时间维度上较新的商品表示重量更大。 [0143] 第一比较单元 503 配置为将计算出的置信度值与预设置信度决策阈值进行比较。 [0144] 该移动终端还包括第三确定单元 507 ,其中第三确定单元 507 配置为,如果计算出的置信度值小于预设的置信度判定阈值,则确定无法识别出所述移动终端的运动状态。 [0145] 第二比较单元 504 配置为,当计算出的置信度值大于预设置信度决策阈值时,将计算出的列表正交度值与预设列表正交度决策阈值进行比较。 [0146] 第一确定单元 505 设置为,如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止。 [0147] 第二确定单元 506 配置为,如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0148] 该移动终端还包括计算子单元,该计算子单元被配置为根据在设置的时间窗口长度内获取的与多个WLAN接入点有关的信息,计算信号波动率。 [0149] 该移动终端还包括第三比较单元 508 ,其中第三个比较单元 508 配置为,如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值且小于列表正交性判定阈值的最大值,则将计算出的信号波动率与预设信号波动率判定阈值进行比较 。 [0150] 该移动终端还包括第四确定单元 509 第五确定单元 510 。 [0151] 第四确定单元 509 设置为,如果计算出的信号波动率大于预设信号波动率决策阈值,则确定所述移动终端的运动状态为步行。 [0152] 第五确定单元 510 设置为,如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定所述移动终端的运动状态为静止。 [0153] 该移动终端还包括处理单元,该处理单元用于在多个连续的时间窗内根据移动终端的运动状态进行确定,并设置确定的运动状态,该运动状态在移动终端的运动状态中最多发生。 移动终端中的移动终端作为移动终端在几个连续时间窗口内的最终运动状态。 [0154] 本公开的实施例提供了一种移动终端。 移动终端设置时间窗口长度,并收集在设置的时间窗口长度内获取的多个WLAN接入点,因此移动终端的应用范围较广,即该方法适用于多个WLAN接入所覆盖的区域 点数,不受室内或室外站点的限制。 根据该方法,计算过程很简单,也就是说,可以通过将多个WLAN接入点的置信度值和列表正交性值与预设值进行比较来简单地确定移动终端的运动状态。 置信度值,并将计算出的列表正交性值与预设列表正交性值进行比较。 因此,该方法的可实现性高,并且该方法可以直接应用于市场上具有WLAN功能的移动终端,而无需改变硬件。 由于该方法在测量过程中对移动终端的放置位置没有特殊要求,并且与用户的姿势或运动习惯无关,因此该方法是通用的。 由于该方法所需的特征参数数量少且确定方法简单,因此该方法的复杂度较低。 另外,在该方法的测量和操作过程中不需要额外的功率开销,也就是说,该方法的功耗很低。 实施例4 [0155] 图。 图6是根据本发明实施例四的移动终端的装置的结构图。 参考图。 参见图6。 6是移动终端 600 根据本公开的实施例,并且不限制本公开的实施例中的移动终端的实现。 移动终端 600 包括一个处理器 601 ,一个通讯接口 602 记忆 603 和一辆公共汽车 604 。 [0156] 处理器 601 ,通讯接口 602 以及记忆 603 使用总线完成相互通信 604 。 [0157] 通讯接口 602 配置为与另一个设备通信。 [0158] 处理器 601 配置为执行应用程序。 [0159] 该应用程序可以包括程序代码,其中该程序代码包括计算机操作指令。 [0160] 处理器 601 可以是中央处理单元(CPU),专用集成电路(ASIC)或配置为实现本公开的该实施例的一个或多个集成电路。 [0161] 记忆 603 配置为存储应用程序。 记忆 603 存储器可以包括高速随机存取存储器(RAM),或者可以包括非易失性存储器,例如,至少一个磁盘存储器。 所述应用可以包括:每隔指定的采样周期扫描一次所述移动终端的WLAN接入点;收集每次扫描所获取的多个WLAN接入点的信息,所述信息包括基本服务集标识和信号强度; 根据在设置的时间窗口长度内获取的多个WLAN接入点的信息,计算置信度值和列表正交性值; 将计算出的置信度值与预设的置信度决策阈值进行比较; 当计算出的置信度值大于预设置信度判定阈值时,将计算出的列表正交度值与预设列表正交度判定阈值进行比较; 如果计算出的列表正交性值小于预设列表正交性判定阈值的最小值,则确定移动终端的运动状态为静止; 如果计算出的列表正交性值大于预设列表正交性判定阈值的最大值,则确定移动终端的运动状态为驾驶中。 [0162] 计算置信度值包括:将在每个指定采样周期内进行的扫描中获取的多个WLAN接入点的数量乘以预设的第一时间维度权重因子,以计算每次扫描后的WLAN接入点的平均数量; 然后,将所有平均数量和WLAN接入点的总和相加,以获取置信度值,其中在设置的时间窗口长度内计算平均数量。 [0163] 计算列表正交性值包括在设置的时间窗口长度内,将关于在第一次扫描期间获取的多个WLAN接入点的信息与关于在第二次扫描期间获取的多个WLAN接入点的信息进行比较以获取信息。 关于两次扫描中获取的非重复的WLAN接入点; 根据预设的贡献度函数,获取每个非重复WLAN接入点的信号强度对列表正交度的贡献度; 增加所有非重复WLAN接入点的贡献度; 将通过相加获得的值乘以预设的第二时间维度权重因子,以获得平均贡献度; 将两次扫描获取的非重复WLAN接入点数量和重复WLAN接入点数量相加,得到一定数量的WLAN接入点; 将平均贡献度除以WLAN接入点的数量,得到第一次扫描的列表正交性值,其中通过比较多个WLAN接入点的信息获取第二次扫描的列表正交性值 在第二次扫描期间获取的信息与在第三次扫描期间获取的关于多个WLAN接入点的信息时,通过比较关于多个WLAN接入点的信息来获取第三次扫描的列表正交值 使用在第四次扫描期间获取的有关多个WLAN接入点的信息等进行第三次扫描时获取的信息,以及(N-1)的列表正交值 日 假设在设定的时间窗口长度内,在指定的采样周期内总共进行了N次扫描,则获取扫描时间。 并添加第一次扫描,第二次扫描的列表正交性值。 。 。 和(N-1) 日 在设定的时间窗口长度内,获取N次扫描的列表正交值。 [0164] 该应用还包括:如果计算出的置信度值小于预设的置信度判定阈值,则确定不能识别出移动终端的运动状态。 [0165] 该应用程序还包括:根据在设置的时间窗口长度内获取的关于多个WLAN接入点的信息,以及如果计算出的列表正交性值大于预设列表正交性判定阈值的最小值,则计算信号波动率。 小于列表正交性判定阈值的最大值,将计算出的信号波动率与预设信号波动率判定阈值进行比较。 [0166] 该应用程序还包括:如果计算出的信号波动率大于预设信号波动率决策阈值,则确定移动终端的运动状态为行走; 如果计算出的信号波动率小于或等于预设信号波动率决策阈值,则确定移动终端的运动状态为静止。 [0167] 该应用程序还包括根据移动终端的运动状态在几个连续的时间窗口内进行确定,并将确定的运动状态设置为最终运动状态,该确定的运动状态在移动终端的运动状态中最多出现一次。 在几个连续的时间窗口内移动终端的时间间隔。 [0168] 本领域普通技术人员可以理解,实施例中方法的全部或部分处理可以通过指令相关硬件的计算机程序(例如处理器)来实现。 程序可以存储在计算机可读存储介质中。 当程序运行时,执行实施例中的方法的处理。 前述存储介质可以包括磁盘,光盘,只读存储器(ROM)或RAM。 [0169] 以上所述仅为本发明的优选实施方式,并不用于限制本发明的保护范围。 凡在本发明的精神和原则之内,所作的任何修改,等同替换,改进等,均应包含在本发明的保护范围之内。 (String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104125021A(String), CN104125021B(String), EP2993947A1(String), EP2993947A4(String), US20160044462A1(String), US9560486B2(String), WO2014176887A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104125021A(String), CN104125021B(String), EP2993947A1(String), EP2993947A4(String), US20160044462A1(String), US9560486B2(String), WO2014176887A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.197 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.197 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.197 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9560486B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104125021A(String), CN104125021B(String), EP2993947A1(String), EP2993947A4(String), US20160044462A1(String), US9560486B2(String), WO2014176887A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), CN104125021A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), CN104125021B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.320 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.320 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), EP2993947A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.355 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), EP2993947A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), US20160044462A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), US9560486B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271666(Integer), WO2014176887A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9560486B2(String), US9560486B2(String), 1485792000(Integer), 271666(Integer), 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185990(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185990(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.732 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185990(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185990(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.923 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:34.923 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 185990(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.459 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for printing document of mobile terminal through printer, and mobile terminal therefor(String), 一种通过打印机打印移动终端文档的方法及其移动终端(String), US20110063663A1(String), A method for printing a document of a mobile terminal without a separate printer setup is provided. The method includes performing a wireless auto-connection between a mobile terminal and a printer located near the mobile terminal, and when the mobile terminal transmits a document to be printed to the printer, the printer finds a computer capable of outputting the document, transmits the document to the computer, and prints the document in response to a print instruction received from the computer. Accordingly, a user can print various documents stored in the mobile terminal wherever a printer is located, even without information of the printer.(String), 提供了一种在没有单独的打印机设置的情况下打印移动终端的文档的方法。 该方法包括在移动终端与位于移动终端附近的打印机之间进行无线自动连接,当移动终端向打印机发送待打印文档时,打印机找到能够输出该文档的计算机,发送 文档到计算机,并响应从计算机接收到的打印指令打印文档。 因此,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档,即使没有打印机的信息。(String), US12/869984(String), 1282838400(Integer), US20110063663A1(String), 1300291200(Integer), 美国(String), 2(Integer), KR(String), 4(Integer), 20(Integer), US20020051200A1 | US20020087622A1 | US20020097433A1 | US20030002072A1 | US20060105714A1 | US20060208088A1 | US20070130296A1 | US20080309961A1 | US20100201996A1 | US20130222618A1 | US6369909B1 | US6587835B1 | US6690918B2 | US6798530B1 | US7016062B2 | US7272788B2 | US7460261B2 | US7609402B2 | US7991778B2 | US8050709B2(String), 17(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.496 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185991(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.644 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\632f12ad2040459fa8925a55560ccfd7.png(String), 185991(Integer), 632f12ad2040459fa8925a55560ccfd7.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for printing document of mobile terminal through printer, and mobile terminal therefor(String), 一种通过打印机打印移动终端文档的方法及其移动终端(String), US20110063663A1(String), A method for printing a document of a mobile terminal without a separate printer setup is provided. The method includes performing a wireless auto-connection between a mobile terminal and a printer located near the mobile terminal, and when the mobile terminal transmits a document to be printed to the printer, the printer finds a computer capable of outputting the document, transmits the document to the computer, and prints the document in response to a print instruction received from the computer. Accordingly, a user can print various documents stored in the mobile terminal wherever a printer is located, even without information of the printer.(String), 提供了一种在没有单独的打印机设置的情况下打印移动终端的文档的方法。 该方法包括在移动终端与位于移动终端附近的打印机之间进行无线自动连接,当移动终端向打印机发送待打印文档时,打印机找到能够输出该文档的计算机,发送 文档到计算机,并响应从计算机接收到的打印指令打印文档。 因此,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档,即使没有打印机的信息。(String), US12/869984(String), 1282838400(Integer), US20110063663A1(String), 1300291200(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 4(Integer), 20(Integer), US20020051200A1 | US20020087622A1 | US20020097433A1 | US20030002072A1 | US20060105714A1 | US20060208088A1 | US20070130296A1 | US20080309961A1 | US20100201996A1 | US20130222618A1 | US6369909B1 | US6587835B1 | US6690918B2 | US6798530B1 | US7016062B2 | US7272788B2 | US7460261B2 | US7609402B2 | US7991778B2 | US8050709B2(String), \20230420\632f12ad2040459fa8925a55560ccfd7.png(String), 17(Integer), 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 1. A method for printing, by a printer connected to at least one computer, a document of a mobile terminal, the method comprising the steps ofacquiring document support information from at least one computer connected with the printer;performing a wireless auto-connection procedure with the mobile terminal;receiving a print request including an output target document from the connected mobile terminal;upon receiving the print request, selecting a computer to output the output target document by referring to the acquired document support information; andprinting the output target document in response to a print instruction issued by the selected computer.(String), 1.一种通过连接至少一台计算机的打印机打印移动终端文档的方法,该方法包括的步骤从至少一台与打印机连接的计算机获取文档支持信息;执行与移动终端的无线自动连接程序;从连接的移动终端接收包括输出目标文档的打印请求;接收到打印请求后,参照获取的文档支持信息,选择计算机输出输出目标文档;和响应于所选计算机发出的打印指令打印输出目标文档。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 2. The method as claimed in claim 1, further comprising, when acquiring the document support information from the at least one computer, mapping the at least one computer according to types of documents and storing a result of the mapping in a table.(String), 2.如权利要求1所述的方法,还包括,当从至少一台计算机获取文档支持信息时,根据文档类型对至少一台计算机进行映射,并将映射结果存储在表中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 3. The method as claimed in claim 2, wherein the document support information includes at least one selected from a group consisting of a document type, a network address of the computer, a version of document software installed in the computer, information indicating whether output of the document is available, and a document storage area allocated to the computer.(String), 3.如权利要求2所述的方法,其中文档支持信息包括选自文档类型、计算机的网络地址、计算机中安装的文档软件的版本、文档是否可用的信息、文档存储区中的至少一项分配给电脑。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 4. The method as claimed in claim 1, wherein performing the wireless auto-connection procedure with the mobile terminal comprises:when a request for starting an automatic wireless Local Area Network (LAN) connection procedure is issued, generating and displaying random information used in common with the mobile terminal for the wireless auto-connection; andgenerating and configuring information required for the wireless auto-connection using the random information.(String), 4.如权利要求1所述的方法,其中与移动终端执行无线自动连接过程包括:当发出启动自动无线局域网(LAN)连接过程的请求时,生成并显示与移动终端共同用于无线自动连接的随机信息;和使用随机信息生成和配置无线自动连接所需的信息。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 5. The method as claimed in claim 1, further comprising, when the printer is powered on before the document support information is acquired, multicasting a request for the document support information to the at least one computer connected on a Local Area Network (LAN), according to a discovery protocol.(String), 5.如权利要求1所述的方法,还包括,当在获取文档支持信息之前打印机开机时,根据发现协议向连接在局域网(LAN)上的至少一台计算机组播对文档支持信息的请求。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 6. The method as claimed in claim 1, further comprising, after performing the wireless auto-connection procedure:receiving a printer information request according to a discovery protocol from the mobile terminal;providing the mobile terminal with a response message, the response message including a name of the printer, an Internet Protocol (IP) address of the printer, and port information of the printer;receiving, from the mobile terminal, a request for attribute information of the printer; andtransmitting a response to the request, wherein the response includes the attribute information of the printer.(String), 6.如权利要求1所述的方法,还包括,执行无线自动连接程序后:根据发现协议从移动终端接收打印机信息请求;向移动终端提供响应消息,该响应消息包括打印机的名称、打印机的IP地址和打印机的端口信息;接收移动终端对打印机属性信息的请求;和传送对请求的响应,其中响应包括打印机的属性信息。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 7. The method as claimed in claim 6, wherein the printer attribute information corresponds to information required for constructing a print menu in the mobile terminal, and includes at least one selected from a group consisting of state information of the printer, a type of a document that can be output, and an output-related option.(String), 7.如权利要求6所述的方法,其中打印机属性信息对应移动终端中构建打印菜单所需的信息,包括打印机状态信息、可输出文档类型、输出相关信息中的至少一项。选项。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 8. A method for printing, by a mobile terminal, a document of the mobile terminal through a printer connected with at least one computer, the method comprising the steps of:performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped; andtransmitting, when the wireless auto-connection procedure is completed a print request including an output target document to the printer, in order for the printer to select a target computer by referring to the document information.(String), 8.一种移动终端通过与至少一台计算机连接的打印机打印移动终端文档的方法,该方法包括步骤:执行与打印机的无线自动连接程序,其中打印机管理文档信息,其中映射了根据每个文档类型可用于输出的计算机;和当无线自动连接程序完成时,传送包含输出目标文档的打印请求至打印机,以供打印机参考文档信息选择目标计算机。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 9. The method as claimed in claim 8, wherein performing the wireless auto-connection procedure with the printer comprises:acquiring random information used in common with the printer for the wireless auto-connection when a request for starting an automatic wireless Local Area Network (LAN) connection procedure is issued; andgenerating and configuring information required for the wireless auto-connection using the random information.(String), 9.如权利要求8所述的方法,其中执行与打印机的无线自动连接程序包括:当发出启动无线局域网(LAN)自动连接程序的请求时,获取与打印机共同使用的无线自动连接的随机信息;和使用随机信息生成和配置无线自动连接所需的信息。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 10. The method as claimed in claim 8 further comprising, after performing the wireless auto-connection procedure:transmitting a request for printer information to the printer according to a discovery protocol; andreceiving a response message, wherein the response message includes a name of the printer, an Internet Protocol (IP) address of the printer, and port information of the printer.(String), 10.如权利要求8所述的方法还包括,执行无线自动连接程序后:根据发现协议向打印机发送对打印机信息的请求;和接收响应消息,其中响应消息包括打印机的名称、打印机的互联网协议(IP)地址和打印机的端口信息。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 11. The method as claimed in claim 10, further comprising, after receiving the response message:requesting the printer to send attribute information of the printer; andreceiving a response to the request, wherein the response includes attribute information of the printer.(String), 11.如权利要求10所述的方法,还包括,收到响应消息后:请求打印机发送打印机的属性信息;和接收对请求的响应,其中响应包括打印机的属性信息。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 12. The method as claimed in claim 11, wherein the printer attribute information corresponds to information required for constructing a print menu in the mobile terminal, and includes at least one selected from a group consisting of state information of the printer, a type of a document that can be output, and an output-related option.(String), 12.如权利要求11所述的方法,其中打印机属性信息对应移动终端中构建打印菜单所需的信息,包括打印机状态信息、可输出文档类型、输出相关信息中的至少一项。选项。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 13. The method as claimed in claim 12, wherein the print request including the output target document includes a print option set through the print menu.(String), 13.如权利要求12所述的方法,其中包括输出目标文档的打印请求包括通过打印菜单设置的打印选项。14、一种移动终端,通过与至少一台计算机连接的打印机输出移动终端的文档,该移动终端包括:无线自动设置模块,用于执行与打印机的无线自动连接程序,其中打印机管理文档信息,其中映射了根据每个文档类型可用于输出的计算机;发现模块,用于对连接的打印机执行发现操作;图形用户界面(GUI),用于提供打印菜单,打印菜单用于选择待输出的目标文档和选择打印选项;和打印代理模块,用于当通过打印菜单指定输出目标文档和打印选项时,向打印机发送包括输出目标文档的打印请求,以使打印机参考文档信息选择目标计算机。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 14. A mobile terminal for outputting a document of the mobile terminal through a printer connected with at least one computer, the mobile terminal comprising:a wireless auto-setup module for performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped;a discovery module for performing a discovery operation with the connected printer;a Graphical User Interface (GUI) for providing a print menu, the print menu being used for selecting a target document to be output and selecting a print option; anda printing agent module for, when the output target document and print option are appointed through the print menu, transmitting a print request including the output target document to the printer for enabling the printer to select a target computer by referring to the document information.(String), 15.如权利要求14所述的移动终端,其中发现模块通过发现协议获取打印机信息,包括打印机的名称、打印机的网际协议(IP)地址和打印机的端口信息,以及其中,发现模块将获取的打印机信息发送给打印代理模块。(String), 0(Integer), 13(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 15. The mobile terminal as claimed in claim 14, wherein the discovery module acquires printer information including a name of the printer, an Internet Protocol (IP) address of the printer, and port information of the printer, by a discovery protocol, andwherein the discovery module transmits the acquired printer information to the printing agent module.(String), 16.如权利要求14所述的移动终端,其中,打印代理模块获取打印机信息后,向打印机请求发送打印机的属性信息,根据请求接收包含打印机属性信息的响应,并将该响应传递给GUI。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 16. The mobile terminal as claimed in claim 14, wherein, after acquiring the printer information, the printing agent module requests the printer to send attribute information of the printer, receives a response comprising attribute information of the printer according to the request, and transfers the response to the GUI.(String), 17.如权利要求16所述的移动终端,其中,GUI基于接收到的打印机属性信息构造打印菜单,打印菜单包括从由打印机的状态信息、可输出的文档的类型、彩色/黑白组成的组中选择的至少一个打印选项设置和水平/垂直设置。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:35.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185991(Integer), 17. The mobile terminal as claimed in claim 16, wherein, the GUI constructs the print menu based on the received printer attribute information, the print menu including at least one print option selected from a group consisting of state information of the printer, a type of a document that can be output, color/black & white setup, and horizontal/vertical setup.(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.133 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.134 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185991(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to an application filed in the Korean Industrial Property Office on Sep. 15, 2009 and assigned Serial No. 10-2009-0087112, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an apparatus and method for printing a document of a mobile terminal, and more particularly to an apparatus and method for enabling a user to print the document through a printer, via wireless communication of the mobile terminal, and without requiring a separate printer setup procedure. [0004]2. Description of the Related Art [0005]Generally, in order for a desktop personal computer (hereinafter, referred to as a computer) to print a document via a printer, a document file, application software capable of reading the document, and driver software suitable for the particular printer model and the operating system are requested. Therefore, when the user issues a document output request, a computer reads and analyzes a document file through application software and generates, through a Graphical Device Interface (GDI) a document image that has a form suitable for a printer to which the document image is to be output. After reading and analyzing the document, the computer transmits data of the document image to the printer through a printer driver, thereby printing the document. [0006]Unlike desktop personal computer environments such as described above, a mobile terminal such as a cellular phone cannot use the same application software as that used in the computer. Since mobile terminals are designed to be carried by users, the performance of mobile terminals is lower than the performance of desktop personal computers, and mobile terminal operating systems are different from desktop computer operating systems in most cases. More specifically, mobile terminals are more limited than desktop personal computers, with respect to implementing application software. Therefore, such mobile environments, dedicated viewer software capable of only viewing documents is used to check various documents. [0007]In order to output a document stored in a mobile terminal, the mobile terminal connects to a computer. To this end, indirect and direct connection schemes are used. The indirect connection scheme includes directly inserting an external storage device into the mobile terminal, copying a desired document into the external storage device, bringing the copied document of the external storage device into the computer, and then outputting the copied document. The direct connection scheme includes outputting the document using a separate data cable or a wireless local area connection scheme. However, using an external storage device or a data cable is inconvenient for a user because the user must perform a connection task, and using a wireless local area connection scheme requires the user to be aware of the way of using software for wireless connection. [0008]As described above, a conventional mobile terminal uses dedicated viewer software in order to read a computer document. However, when using dedicated viewer software, since the number of formats for documents has already been determined, a user of the mobile terminal cannot view a corresponding document if the mobile terminal does not have the same viewer software for supporting a document format of document software, as that in the computer. Document formats may frequently change due to version upgrades according to enhancement of functions of document software. Therefore, if dedicated viewer software is not rapidly updated, the dedicated viewer software may not be used with updated document formats. Although dedicated viewer software is used to address the above-described absence of mobile versions of document-related software, such dedicated viewer software cannot support all document formats used by computers. It is also necessary to install a printer driver in order to print a document. However, since mobile terminals have no fixed printer for usage, unlike computers, a mobile terminal must find and install a suitable printer driver every time a document is to be printed. Even in the above-described method of connecting a mobile terminal and a computer, a user passes through a setup procedure of inputting, step-by-step, information for a wireless communication connection in order to establish a wireless local area communication, which is inconvenient. It is inefficient for a user to input pieces of information items, one-by-one, which is very inconvenient for users who must frequently change setup due to frequent movement. [0009]Therefore, a need exists for a method for enabling a mobile terminal to simply establish a wireless connection with a printer when the mobile terminal is located near the printer, and to print a desired document, even without installing a printer driver for document printing. SUMMARY OF THE INVENTION [0010]Accordingly, the present invention has been made to solve at least the above-mentioned problems occurring in the prior art, and the present invention provides an apparatus and method for printing documents of a mobile terminal, even without application software corresponding to each document and a separate printer setup procedure, such as installing a printer driver or other similar procedures. [0011]In addition, the present invention provides an apparatus and method for enabling the user to easily connect a mobile terminal to a printer using a wireless communication function of the mobile terminal, and to print documents of the mobile terminal using the printer. [0012]In accordance with an aspect of the present invention, there is provided a method for printing, by a printer, a document of a mobile terminal, the printer being connected with at least one computer. The method includes acquiring document support information from at least one computer connected with the printer; performing a wireless auto-connection procedure with the mobile terminal; receiving a print request including an output target document from the connected mobile terminal; selecting a computer to output the output target document by referring to the acquired document support information when receiving the print request; and printing the output target document in response to a print instruction issued by the selected computer. [0013]In accordance with another aspect of the present invention, there is provided a method for printing, by a mobile terminal, a document of the mobile terminal through a printer connected with at least one computer. The method includes performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped; and transmitting a print request including an output target document to the printer in order for the printer to select a target computer by making reference to the document information when a connection with the printer is completed. [0014]In accordance with another aspect of the present invention, there is provided a mobile terminal for outputting a document of the mobile terminal through a printer connected with at least one computer. The mobile terminal includes a wireless auto-setup module for performing a wireless auto-connection procedure with the printer, wherein the printer manages document information in which a computer available for output according to each document type is mapped; a discovery module for performing a discovery operation with the connected printer; a Graphical User Interface (GUI) for providing a print menu, the print menu being used for selecting a target document to be output and selecting a print option; and a printing agent module for, when the output target document and print option are appointed through the print menu, transmitting a print request including the output target document to the printer for enabling the printer to select a target computer by referring to the document information. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0016]FIG. 1 is a block diagram illustrating a system for network printing according to an embodiment of the present invention; [0017]FIG. 2 is a flowchart illustrating a printing procedure according to an embodiment of the present invention; [0018]FIG. 3 is an operational flowchart further illustrating a discovery and printable document registration procedure illustrated in FIG. 2, according to an embodiment of the present invention; [0019]FIGS. 4 and 5 are operational flowcharts further illustrating a wireless auto-connection procedure illustrated in FIG. 2 according to an embodiment of the present invention; and [0020]FIG. 6 is an operational flowchart further illustrating a discovery and document output procedure between a mobile terminal and a printer illustrated in FIG. 2, according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS [0021]Hereinafter, various embodiments of the present invention are described with reference to the accompanying drawings. In the following description, the same elements are designated by the same reference numerals although they are shown in different drawings. In addition, in the following description of the present invention, a detailed description of known functions and configurations incorporated herein are omitted where a detailed description thereof may make the subject matter of the present invention unclear. [0022]The present invention provides a method for printing a document of a mobile terminal, even without a separate printer setup procedure. To this end, an embodiment of the present invention includes performing a wireless auto-connection between a mobile terminal and a printer located near the mobile terminal, and when the mobile terminal transmits a document to be printed to the printer, allowing the printer to find a computer capable of outputting the document and to transmit the document to the computer. Thereafter the printer prints the document in response to a print instruction received from the computer. Accordingly, the user can print various documents stored in the mobile terminal wherever a printer is located, even without information of the printer. [0023]FIG. 1 is a block diagram illustrating a system for network printing according to an embodiment of the present invention. As illustrated in FIG. 1, a system for printing a document of a mobile terminal includes a mobile terminal 10, a printer 20 for printing documents, and at least one computer 30, 40, and 50 connected with the printer 20 by a local area network (LAN). [0024]The mobile terminal 10, which may be a cellular phone or another similar device, performs a wireless connection operation with the adjacent printer 20 using a wireless local area communication scheme, and transmits a document to be printed to the printer 20 while sending a print request when the mobile terminal 10 is connected with the printer 20. The mobile terminal 10 includes a wireless auto-setup module 102, a discovery module 104, a printing agent module 106, and a Graphical User Interface (GUI) 108. [0025]The wireless auto-setup module 102 functions configure a wireless auto-connection between the mobile terminal 10 and the printer 20. [0026]The discovery module 104 finds a printer located near the mobile terminal 10. The discovery module 104 multicasts a printer discovery request, and then obtains a name, an Internet Protocol (IP) address, port information, etc. of a printer targeted for connection from a response to the discovery request when receiving the response. In the present example, the mobile terminal 10 obtains information form the printer 20. The information of the printer 20, obtained as described above, is used to transmit a document to be printed to the printer 20. [0027]The printing agent module 106 communicates with a printing manager module 114 of the printer 20, and transmits/receives and manages various state information of the printer 20. More specifically, the printing agent module 106 manages state information of the wirelessly-connected printer 20, such as an online state, an offline state, a power on/off state, a paper feed state, etc. The printing agent module 106 also issues a document print request to the printer 20, and checks whether a document to be printed can be printed by inquiring the printer 20 for information about whether the printer 20 can print the document and receiving a response to the inquiry. The printing agent module 106 requests and acquires information on various attributes, e.g., the number of copies, a paper type, a page, color/black & white, etc., that are used in printing. The printing agent module 106 transmits acquired attribute information to the GUI 108. When print option information and a print target document is selected by the user through the GUI 108, the printing agent module 106 transmits the print option information together with the print target document to the printer 20. [0028]Based on attribute information received from the printing agent module 106, the GUI 108 provides a user with information on the state of a wirelessly-connected printer, a selected number of copies, a selected paper, whether the printer can print a document, and other configurable print options. The user can also select a print-target document through the GUI 108. [0029]The printer 20 includes a wireless auto-setup module 110, a discovery module 112, and the printing manager module 114. [0030]The wireless auto-setup module 110 configures a wireless auto-connection with the mobile terminal 10, similarly to the wireless auto-setup module 102 of the mobile terminal 10. Such a wireless auto-connection procedure will be described in detail hereinbelow. [0031]Similarly to the discovery module 104 of the mobile terminal 10, the discovery module 112 provides a response including information on its own name. IP address, port, etc. upon receiving the discovery request from the mobile terminal 10. [0032]The printing manager module 114 manages target computers 30, 40, and 50 capable of outputting documents through the current printer 20 in the form of a table by mapping the computers 30, 40, and 50 according to types of documents. Such a table may have a structure as illustrated in Table 1 below, but the present invention is not limited thereto. TABLE 1TargetOutputType ofcomputerSoftwareavailable/AllocatedNo.documentaddressversionunavailablearea (Free)1doc192.168.0.107.0Output115 GBavailable2doc192.168.0.155.0Output 50 MBunavailable3xls192.168.0.1107.0Output663 MBavailable4ppt192.168.0.107.0Output115 GBavailable5gul192.168.0.2012  Output800 MBavailable............... [0033]As shown in Table 1, contents of the table include document support information, such as a type of each document (i.e., a file extension), a network address of each computer connected with the printer 20 in a local area network, a version of each document software installed in each computer, information regarding whether document output is available, and information regarding a document storage area allocated to each computer, etc. [0034]The printing manager module 114 also receives a document requested for printing by the user, from the printing agent module 106 of the mobile terminal 10, finds a computer capable of outputting the received document by referring to a table such as Table 1, and then transmitting the received document to the found computer. [0035]As described above, a printer auto-connected with a mobile terminal prints a document to be printed through a computer corresponding to the document among computers connected with the printer by a network, so that the mobile terminal can print a desired document, without installing a printer driver and application software corresponding to each document. [0036]The first computer 30 includes a discovery module 120, a print control module 122, a document control module 124, and a storage 126. The following description of the configuration of the first computer 30 is provided as an example; the configuration and operation of the second and third computers 40 and 50 are the same as those of the first computer 30. [0037]The discovery module 120 performs a discovery operation of the first computer 30 to find the printer 20. The discovery module 120 also registers information regarding types of documents that the first computer 30 can output, a network address, an area allocated to accommodate documents, etc., which are collected by the document control module 124 of the first computer 30 that is a local computer, with the printing manager module 114 of the printer 20. [0038]The document control module 124 searches for document software installed in the first computer 30, and manages types of documents that can be output by the first computer 30. In the present example, information managed by the document control module 124 includes a type of each document (i.e., a file extension), a name of each software, a version of each software, an installation position of each software, etc. Such management information may have a table structure as illustrated in Table 2 below, but the present invention is not limited thereto. TABLE 2Type ofNo.documentNameVersionPosition of software1docMS Word7.0C:\Program Files\Word.exe2xlsMS Excel7.0C:\Program Files\Excel.exe3pptMS PowerPoint7.0C:\Program Files\Powerpoint.exe4gulHunMinJeongEum12  C:\Program Files\Hun.exe5hwpHangul20072007   C:\Program Files\Hwp.exe............... [0039]The document control module 124 also receives an output target document and an output option set by the user from the printing manager module 114 of the printer 20, and stores the received output target document and output option in the storage 126. In addition, the document control module 124 performs document security-related operations, such as deletion, copy protection, modulation protection, etc., or a document [0040]The print control module 122 applies the received output option through an output function of document software, and controls the printer 20 to print the document. [0041]FIG. 2 is a diagram schematically illustrating a printing procedure according to an embodiment of the present invention. More specifically. FIG. 2 illustrates a procedure in which, when the mobile terminal 10 wirelessly auto-connects with the printer 20 and transmits a document to be printed to the printer 20, the printer 20 finds a computer corresponding to the document and requests the found computer to print the document. [0042]Referring to FIG. 2, when the printer 20 is powered on, the printer 20 performs a discovery operation of searching for one or more computers 30 and 40 connected by a LAN using a predetermined discovery protocol, identifies documents that can be output from the searched computers 30 and 40, and registers documents that can be output from each computer 30 and 40 in steps 200 and 205. The procedure of performing a discovery operation between the printer and the computer and registering documents that can be output in steps 200 and 205 is described detail hereinbelow with reference to FIG. 3. [0043]In step 210, a wireless auto-connection procedure is performed between the mobile terminal 10 and the printer 20. According to an embodiment of the present invention, a method for easily achieving a wireless connection is provided for improving convenience for a user. Such a wireless auto-connection procedure is described hereinbelow with reference to FIGS. 4 and 5. FIGS. 4 and 5 are flow diagrams explaining a wireless auto-connection procedure in FIG. 2 according to an embodiment of the present invention. [0044]When the mobile terminal 10 and the printer 20 have been connected with each other through step 210, a discovery operation is performed in step 215. Through the discover operation, the mobile terminal 10 can obtain attribute information of the printer 20, and can report a state of the printer 20 based on the obtained attribute information. When the user of the mobile terminal 10 has selected a print option and a document to be printed, the mobile terminal 10 transmits the document to be printed to the printer 20 in step 220. In the present example, a print option selected by the user is transmitted, together with the document, and the printer 20 finds a computer capable of outputting the document by referring to a table such as Table 1. If the printer 20 has found the second computer 40 as a computer corresponding to the document (i.e., capable of outputting the document), the printer 20 transmits the document to the second computer 40 in step 225. The second computer 40 transmits an output instruction to the printer 20 in step 230, so that the printer 20 prints the document. [0045]As described above, according to an embodiment of the present invention, the printer 20 directly finds a target computer suitable for document output among computers connected with the printer 20 by a LAN, and requests the found computer to output a document. Accordingly, the mobile terminal 10 is not required to install a separate printer driver to use the printer 20, and can print various types of documents stored in the mobile terminal 10 because a print request is sent to a computer having application software corresponding to a document to be printed, among computers connected with the printer 20 by a LAN. [0046]In order to print various types of documents, as described above, the printer 20 should be aware of information regarding documents supported by each computer 30, 40, and 50. For this reason, according to an embodiment of the present invention, a procedure of performing a discovery operation between a printer and a computer and registering documents that can be output is provided, as described in steps 200 and 205. Such a procedure is described as follows with reference to FIG. 3, wherein an operation performed between the printer 20 and the first and second computers 30 and 40 is explained as an example. [0047]In step 300, the discovery module 112 of the printer 20 multicasts a request signal for requesting each computer 30 and 40 to provide information regarding documents that can be output by the first and second computers 30 or 40, to the computers 30 and 40 connected by a LAN using a discovery protocol. The printer 20 transmits such a request in order to identity document output support information for each of the first and second computers 30 and 40. The request is transmitted to the discovery modules 120 and 130 of the first and second computers 30 and 40, respectively. Each discovery module 120 and 130 inquires each document control module 124 and 134, respectively, about a list of printable documents in steps 305 and 310, so that each of document control modules 124 and 134 acquires application information in steps 315 and 320, respectively. The application information represents document information, including types of documents supported by each computer, the version of document software installed in each computer, whether output is available or unavailable, and a document allocation area that can be accommodated. Thereafter, when each document control module 124 and 134 transmits the document information to each discovery module 120 and 130 in steps 335 and 340, each discovery module 120 and 130 generates and transmits a response message including the document information to the printer 20 in steps 345 and 350. In the present example, the response message includes a network address, in addition to the document information. [0048]As described above, each computer 30 and 40 provides the printer 20 with document support information, including types and versions of documents supported by the computer, a document allocation area that can be accommodated, whether output is available or unavailable, a network address, etc., using a discovery protocol, in advance in response to a printable document information request. If a third computer 50 is powered on after the discovery operation has been completed, the discovery module of the third computer 50 may directly register information regarding documents supported by the third computer 50 with a previously registered printer 20. [0049]When the printer 20 receives response messages including each piece of document information from each of first and second computers 30 and 40 through the aforementioned steps, the printer 20 generates a table such as Table 1 based on each piece of received document information. The table is used to find a computer that can output a document received from the mobile terminal 10. [0050]According to an embodiment of the present invention, a method for enabling the user to easily connect the mobile terminal 10 and the printer 20 using a Wireless Auto Setup procedure, i.e. a wireless auto-connection setup procedure is provided. Such a wireless auto-connection procedure corresponding to step 210 in FIG. 2 is described in detail as follows with reference to FIGS. 4 and 5. [0051]FIG. 4 is a diagram illustrating a wireless auto-connection procedure using a Wireless Fidelity (WiFi) scheme among wireless local area communication schemes, wherein a Service Set IDentifier (SSID) is required for WiFi communication between the mobile terminal 10 and the printer 20, a security key is required for authentication and encryption, an IP address must be set for IP communication, and a Wired Equivalent Privacy (WEP) key value is required, since authentication and encryption are performed in a WEP scheme. According to an embodiment of the present invention, a scheme of automatically generating and setting up all the information required for wireless connection is used. Specifically, an SSID, a security key, an IP address are automatically generated using the same information input by a user between the mobile terminal 10 and the printer 20. According to alternative embodiments of the present invention, random information may be used instead of the same information. In this case, the random information may be a random number that is randomly generated in the mobile terminal 10 and the printer 20. Through this procedure, it is possible to conveniently and automatically connect the mobile terminal 10 to the printer 20 without requiring a user to input each piece of information for wireless LAN connection every time. Due to the characteristics of random information that changes for every connection attempt, it is possible to obtain a more enhanced security characteristic. [0052]Referring to FIG. 4, the mobile terminal 10 and the printer 20 execute the same wireless connection software, in which a WiFi connection setup begins in the mobile terminal 10 and the printer 20, respectively, according to a user input. When initiation of such a wireless LAN auto-connection procedure is requested, the printer 20 generates and displays random information that is used in common with the mobile terminal 10, on a display unit of the printer 20 for the wireless auto-connection, in step 400. The mobile terminal 10 displays a random number on the display unit of the printer 20, and receives user input of the random number of the printer 20 in step 405. Such a random number is used to generate and set up information required for a wireless auto-connection. Specifically, as shown in steps 410 and 415, an SSID, a WEP, etc. is automatically generated and set up with the respective random numbers using the same hash function, thereby completing a WiFi connection. [0053]FIG. 5 is a diagram illustrating a wireless auto-connection procedure using a BLUETOOTH® (BT) scheme among wireless local area communication schemes, wherein each of the mobile terminal 10 and printer 20 generates a device name and a Personal Identification Number (PIN) code with a random number, such as in FIG. 4, using the same hash function. When a Bluetooth connection setup begins in the mobile terminal 10 and the printer 20, the printer 20 generates and outputs a random number in step 500, and then the user sees and inputs the random number through the mobile terminal 10 in step 505. Then, the printer 20 performs a device name setup procedure and a PIN code auto-generation/setup procedure using the random number in steps 510 and 515, respectively, while the mobile terminal 10 performs a printer discovery operation and a PIN code auto-generation/setup procedure using the random number in steps 520 and 525, respectively. Accordingly, the user is only required to input a random number in order to automatically achieve a wireless connection between the mobile terminal 10 and the printer 20. [0054]Hereinafter, a discovery and document output procedure between the mobile terminal and the printer, which corresponds to steps 215 to 230 in FIG. 2, is described in detail as follows with reference to FIG. 6. [0055]Referring to FIG. 6, a user may begin a network printing function through a “print” menu provided by the GUI 108. When such a beginning request is input to the mobile terminal 10, the discovery module 104 of the mobile terminal 10 executes a discovery protocol in step 600, thereby requesting a printer discovery from the discovery module 112 of the printer 20. For such a request, the discovery module 104 of the mobile terminal 10 multicasts a DISCOVERY_PRINTER message. Upon receiving such a DISCOVERY_PRINTER message, the printer 20 transmits a RESPONSE_PRINTER message, which is a response message including printer information, such as its own printer name, IP address, port information, etc., to the discovery module 104 of the mobile terminal 10 in step 605. The discovery module 104 transmits the printer information, which has been acquired through such a discovery procedure, to the printing agent module 106 in step 610. [0056]The GUI 108 transmits a PRINTING_CAPABILITY_REQUEST message for requesting attribute information of the printer 20 from the printing agent module 106 in step 615. Such an attribute information request is used to prepare a “print” menu, which enables the user to check the state of a printer, and then to configure a desired option. [0057]Accordingly, the printing agent module 106 transmits the PRINTING_CAPABILITY_REQUEST message to the printing manager module 114 of the printer 20 in step 620 in order to request attribute information. The printing manager module 114 responds by transmitting a PRINTING_CAPABILITY_RESPONSE message corresponding to the attribute information request in step 625. Such a response message includes attribute information requested by the mobile terminal 10. Here, the attribute information represents various information related to printing, and includes types of printable documents, the state of the printer 20, and information on various options which can be set. [0058]Upon receiving the PRINTING_CAPABILITY_RESPONSE message, the printing agent module 106 transfers the PRINTING_CAPABILITY_RESPONSE message to the GUI 108, in step 630. The GUI 108 provides a “print” menu based on received attribute information. Such a “print” menu includes various option functions, including state information of the printer, types of printable documents, color/black & white setup options, horizontal/vertical setup options, etc. When a print target document and various print options have been appointed through the use of the “print” menu, the GUI 108 transmits the print target document to the printing agent module 106 using a SELECT_DOCUMENT message in step 635. The printing agent module 106 combines and transmits the document and the appointed print options through the use of a PRINT_REQUEST message in step 640. [0059]Through such a PRINT_REQUEST message, the print target document, which has been combined together with the appointed print options, is transmitted to the printing manager module 114 of the printer 20. The printing manager module 114 selects a computer capable of outputting the document by referring to a table such as Table 1 in step 642. More specifically, the printer 20 compares a type of a received document, a capacity of the received document, a right of use, etc. with corresponding information in a document-computer mapping table such as Table 1, and selects a computer capable of outputting the received document. When the printer 20 selects the first computer 30, the printing manager module 114 transmits a PRINT_REQUEST message to th(String), 优先 [0001] 本申请根据 35 U.S.C. §119(a) 于 2009 年 9 月 15 日在韩国工业产权局提交并指定序列号为 10-2009-0087112 的申请,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明总体上涉及一种用于打印移动终端文档的装置和方法,更具体地涉及一种使用户能够通过移动终端的无线通信通过打印机打印文档而无需请求的装置和方法。 单独的打印机设置程序。 [0004] 2.相关技术的描述 [0005] 通常,为了使台式个人计算机(以下简称计算机)通过打印机打印文档,文档文件、能够读取该文档的应用软件以及适合特定打印机型号和操作的驱动软件。 系统被要求。 因此,当用户发出文档输出请求时,计算机通过应用软件读取并分析文档文件,并通过图形设备接口(GDI)生成适合打印机格式的文档图像。 被输出。 计算机读取并分析文档后,通过打印机驱动程序将文档图像的数据传输至打印机,从而打印文档。 [0006] 与如上所述的台式个人计算机环境不同,诸如蜂窝电话的移动终端不能使用与在计算机中使用的应用软件相同的应用软件。 由于移动终端是为用户携带而设计的,因此移动终端的性能低于台式个人电脑的性能,并且移动终端操作系统在大多数情况下与台式电脑操作系统不同。 更具体地,移动终端在实现应用软件方面比台式个人计算机更受限制。 因此,在这种移动环境下,只能查看文档的专用查看器软件被用来检查各种文档。 [0007] 为了输出存储在移动终端中的文档,移动终端连接到计算机。 为此,使用了间接和直接连接方案。 间接连接方案包括直接将外部存储设备插入移动终端,将需要的文件复制到外部存储设备中,将复制的外部存储设备的文件带入计算机,然后将复制的文件输出。 直接连接方案包括使用单独的数据线或无线局域网连接方案输出文档。 然而,使用外部存储设备或数据线对于用户来说是不方便的,因为用户必须执行连接任务,并且使用无线局域网连接方案需要用户了解使用软件进行无线连接的方式。 [0008]如上所述,传统的移动终端使用专用的浏览器软件来阅读计算机文档。 但是,在使用专用的查看器软件时,由于文档的格式数量已经确定,如果移动终端没有相同的支持文档软件的文档格式的查看器软件,则移动终端的用户将无法查看对应的文档。 ,就像电脑里的一样。 随着文档软件功能的增强,文档格式可能会因版本升级而频繁变化。 因此,如果不快速更新专用查看器软件,则专用查看器软件可能无法与更新的文档格式一起使用。 尽管使用专用查看器软件来解决上述缺少移动版本的文档相关软件的问题,但是这样的专用查看器软件不能支持计算机使用的所有文档格式。 还需要安装打印机驱动程序才能打印文档。 但是,由于移动终端没有固定的打印机可供使用,与电脑不同,移动终端每次要打印文档时都必须寻找并安装合适的打印机驱动程序。 即使在上述连接移动终端和计算机的方法中,用户通过逐步输入用于无线通信连接的信息的设置过程以建立无线局域网通信,这是 不方便。 一条一条的信息输入对于用户来说效率低下,对于因频繁移动而必须频繁更改设置的用户来说非常不方便。 [0009] 因此,需要一种方法使移动终端能够在移动终端位于打印机附近时简单地与打印机建立无线连接,并打印所需的文档,甚至无需安装用于文档打印的打印机驱动程序。 发明内容 [0010] 相应地,本发明是为了至少解决现有技术中存在的上述问题而提出的,本发明提供了一种移动终端的文档打印装置和方法,即使没有与每个文档对应的应用软件和 单独的打印机设置程序,例如安装打印机驱动程序或其他类似程序。 [0011] 此外,本发明提供了一种设备和方法,用于使用户能够使用移动终端的无线通信功能轻松地将移动终端连接到打印机,并使用打印机打印移动终端的文档。 [0012] 根据本发明的一个方面,提供了一种通过打印机打印移动终端文档的方法,该打印机与至少一台计算机连接。 该方法包括从至少一台与打印机连接的计算机获取文档支持信息; 执行与移动终端的无线自动连接程序; 从连接的移动终端接收包括输出目标文档的打印请求; 在接收到打印请求时,参照获取的文档支持信息,选择计算机输出输出目标文档; 响应于被选择的计算机发出的打印指令打印输出目标文档。 [0013] 根据本发明的另一方面,提供了一种移动终端通过与至少一个计算机连接的打印机打印移动终端的文档的方法。 该方法包括与打印机执行无线自动连接程序,其中打印机管理文档信息,其中映射了根据每个文档类型可用于输出的计算机; 当与打印机的连接完成时,向打印机发送包括输出目标文档的打印请求,以便打印机通过参考文档信息来选择目标计算机。 [0014]根据本发明的另一方面,提供了一种移动终端,用于通过与至少一台计算机连接的打印机输出移动终端的文档。 移动终端包括无线自动设置模块,用于执行与打印机的无线自动连接过程,其中打印机管理文档信息,其中根据每个文档类型映射了可用于输出的计算机; 发现模块,用于对连接的打印机执行发现操作; 图形用户界面(GUI),用于提供打印菜单,打印菜单用于选择待输出的目标文档和选择打印选项; 打印代理模块,用于当通过打印菜单指定输出目标文档和打印选项时,向打印机发送包括输出目标文档的打印请求,以使打印机参考文档信息选择目标计算机。 附图的简要说明 [0015] [0015] 通过以下结合附图的详细描述,本发明的上述及其他方面、特征和优点将更加明显,其中: [0016] 图1为本发明一实施例的网络打印系统的方块图。 [0017] 图2是表示本发明的一个实施方式的打印步骤的流程图。 [0018] 图3是进一步说明根据本发明实施例的图2中说明的发现和可打印文档注册过程的操作流程图; [0019] 图4和图5是进一步说明根据本发明实施例的图2中所示的无线自动连接过程的操作流程图; 和 [0020] 图6是进一步图示根据本发明实施例的图2所示的移动终端和打印机之间的发现和文档输出过程的操作流程图。 具体实施方式 [0021] 在下文中,将参考附图描述本发明的各种实施例。 在下面的描述中,尽管相同的元件在不同的附图中示出,但它们由相同的附图标记表示。 此外,在本发明的以下描述中,省略了对并入本文的已知功能和配置的详细描述,其中对其的详细描述可能使本发明的主题不清楚。 [0022] 本发明提供了一种打印移动终端文档的方法,甚至不需要单独的打印机设置过程。 为此,本发明实施例包括在移动终端和位于移动终端附近的打印机之间进行无线自动连接,并且当移动终端将待打印的文档发送到打印机时,允许打印机发现 能够输出文档并将文档传输到计算机的计算机。 此后打印机响应从计算机接收到的打印指令打印文档。 因此,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档,即使没有打印机的信息。 [0023] 图1是示出根据本发明实施例的用于网络打印的系统的框图。 如图1所示,一种移动终端文档打印系统,包括移动终端 10 , 打印机 20 用于打印文档,以及至少一台计算机 30 , 40 , 和 50 与打印机连接 20 通过局域网 (LAN)。 [0024] 移动端 10 ,可以是手机或其他类似设备,与相邻的打印机进行无线连接操作 20 使用无线局域网通信方案,并将要打印的文档传输到打印机 20 当移动端发送打印请求时 10 与打印机相连 20. 移动端 10 包括一个无线自动设置模块 102 , 发现模块 104 , 打印代理模块 106 和图形用户界面 (GUI) 108 . [0025] 无线自动设置模块 102 功能配置移动终端之间的无线自动连接 10 和打印机 20 . [0026] 发现模块 104 找到位于移动终端附近的打印机 10 . 发现模块 104 多播打印机发现请求,然后在接收到响应时从对发现请求的响应中获取作为连接目标的打印机的名称、互联网协议(IP)地址、端口信息等。 在本示例中,移动终端 10 从打印机获取信息 20 . 打印机信息 20 ,如上所述获得,用于将要打印的文档传输到打印机 20 . [0027] 打印代理模块 106 与打印管理器模块通信 114 打印机的 20 , 发送/接收和管理打印机的各种状态信息 20 . 更具体地说,打印代理模块 106 管理无线连接打印机的状态信息 20 ,例如在线状态、离线状态、电源开关状态、进纸状态等。 打印代理模块 106 还向打印机发出文档打印请求 20 , 并通过查询打印机来检查是否可以打印要打印的文档 20 有关打印机是否 20 可以打印文档和接收查询的响应。 打印代理模块 106 请求并获取有关打印中使用的各种属性的信息,例如份数、纸张类型、页面、彩色/黑白等。 打印代理模块 106 将获取的属性信息传输到 GUI 108 . 当用户通过 GUI 选择打印选项信息和打印目标文档时 108 ,打印代理模块 106 将打印选项信息与打印目标文档一起传输到打印机 20 . [0028] 基于从打印代理模块接收到的属性信息 106 , 图形用户界面 108 为用户提供有关无线连接打印机状态、选定份数、选定纸张、打印机是否可以打印文档以及其他可配置打印选项的信息。 用户还可以通过 GUI 选择打印目标文档 108 . [0029] 打印机 20 包括一个无线自动设置模块 110 , 发现模块 112 和打印管理器模块 114 . [0030] 无线自动设置模块 110 配置与移动终端的无线自动连接 10 ,类似于无线自动设置模块 102 移动端 10 . 下面将详细描述这种无线自动连接过程。 [0031] 类似于发现模块 104 移动端 10 , 发现模块 112 提供一个响应,包括关于它自己名字的信息。 接收到移动终端发现请求后的IP地址、端口等 10 . [0032] 打印管理器模块 114 管理目标计算机 30 , 40 , 和 50 能够通过当前打印机输出文件 20 通过映射计算机以表格的形式 30 , 40 , 和 50 根据文件类型。 这样的表可以具有如下表1所示的结构,但本发明不限于此。 表格1 目标 输出 类型 计算机 软件 可用的/ 已分配 不。 文档 地址 版本 不可用 区域(免费) 1 文件 192.168.0.10 7.0 输出 115GB 可用的 2 文件 192.168.0.15 5.0 输出 50MB 不可用 3 xls 192.168.0.110 7.0 输出 663兆字节 可用的 4 ppt 192.168.0.10 7.0 输出 115GB 可用的 5 古尔 192.168.0.20 12   输出 800 兆字节 可用的 . . . . . . . . . . . . . . . [0033] 如表1所示,该表的内容包括文档支持信息,例如每个文档的类型(即文件扩展名)、与打印机连接的每台计算机的网络地址 20在局域网中,每台计算机安装的各文档软件的版本、文档输出是否可用的信息、分配给每台计算机的文档存储区域的信息等。 [0034] 打印管理器模块 114 还从打印代理模块接收用户请求打印的文档 106 移动终端的 10 ,参照表1等表格,找到能够输出接收到的文件的计算机,然后将接收到的文件传送到找到的计算机。 [0035] 如上所述,自动连接移动终端的打印机通过网络连接打印机的计算机中与文档对应的计算机打印待打印文档,使得移动终端无需安装 每个文档对应的打印机驱动程序和应用软件。 [0036] 第一台电脑 30 包括一个发现模块 120 ,打印控制模块 122 , 文档控制模块 124 , 和一个存储 126 . 下面介绍第一台电脑的配置 30 作为示例提供; 第二台和第三台电脑的配置和操作 40 和 50 与第一台计算机相同 30 . [0037] 发现模块 120 执行第一台计算机的发现操作 30 找到打印机 20 . 发现模块 120 还注册有关第一台计算机的文档类型的信息 30 可以输出,网络地址,分配容纳文档的区域等,由文档控制模块收集 124 第一台电脑的 30 那是一台本地计算机,带有打印管理器模块 114 打印机的 20 . [0038] 文档控制模块 124 搜索安装在第一台计算机上的文档软件 30 , 并管理第一台计算机可以输出的文档类型 30 . 在本示例中,由文档控制模块管理的信息 124 包括每个文档的类型(即文件扩展名)、每个软件的名称、每个软件的版本、每个软件的安装位置等。这些管理信息可以具有如下表2所示的表格结构, 但本发明不限于此。 表 2 类型 不。 文档 姓名 版本 软件位置 1 文件 微软Word 7.0 C:\Program Files\Word.exe 2 xls 微软Excel 7.0 C:\Program Files\Excel.exe 3 ppt 微软幻灯片 7.0 C:\Program Files\Powerpoint.exe 4 古尔 训民正音 12   C:\Program Files\Hun.exe 5 hwp 韩文2007 2007    C:\Program Files\Hwp.exe . . . . . . . . . . . . . . . [0039] 文档控制模块 124 还从打印管理器模块接收输出目标文档和用户设置的输出选项 114 打印机的 20 , 并将接收到的输出目标文档和输出选项存储在存储中 126 . 另外,文档控制模块 124 执行文档安全相关的操作,如删除、复制保护、调制保护等,或者文档 [0040] 打印控制模块 122 通过文档软件的输出功能应用接收到的输出选项,并控制打印机 20 打印文档。 [0041] 图2是示意性图示根据本发明实施例的打印过程的图。 进一步来说。 图 2 说明了一个过程,其中,当移动终端 10 无线自动连接打印机 20 并将要打印的文档传输到打印机 20 , 打印机 20 查找该文档对应的计算机,并请求查找到的计算机打印该文档。 [0042] 参考图 2,当打印机 20 电源打开时,打印机 20 执行搜索一台或多台计算机的发现操作 30 和 40 使用预定的发现协议通过 LAN 连接,识别可以从搜索到的计算机输出的文档 30 和 40 , 并注册可以从每台计算机输出的文档 30 和 40 逐步 200 和 205. 在打印机和计算机之间执行发现操作并注册可分步输出的文档的过程 200 和 205 下面参照图3详细描述。 [0043] 在步 210 ,移动终端之间执行无线自动连接过程 10 和打印机 20 . 根据本发明的实施例,提供了一种容易实现无线连接的方法,以提高用户的便利性。 下面参考图4和图5描述这样的无线自动连接过程。图4和图5是解释根据本发明实施例的图2中的无线自动连接过程的流程图。 [0044] 当移动端 10 和打印机 20 已通过步骤相互连接 210 , 在步骤中执行发现操作 215 . 通过discover操作,移动端 10 可以获得打印机的属性信息 20 , 并且可以报告打印机的状态 20 基于获得的属性信息。 当移动端用户 10 选择了打印选项和需要打印的文档,移动终端 10 将要打印的文档传输到打印机 20 在步骤 220 . 在本示例中,用户选择的打印选项与文档和打印机一起被传输 20 参照表 1 等表格查找能够输出文档的计算机。如果打印机 20 找到了第二台电脑 40 作为文档对应的计算机(即能够输出文档),打印机 20 将文档传输到第二台计算机 40 在步骤 225 . 第二台电脑 40 向打印机发送输出指令 20 在步骤 230 , 这样打印机 20 打印文档。 [0045] 如上所述,根据本发明的一个实施例,打印机 20 直接在连接打印机的电脑中寻找适合文档输出的目标电脑 20 通过局域网,请求搜索到的计算机输出文件。 据此,移动终端 10 无需安装单独的打印机驱动程序即可使用打印机 20 ,并可打印存储在移动端的各类文档 10 因为打印请求被发送到与打印机连接的计算机中具有与待打印文档对应的应用软件的计算机 20 通过局域网。 [0046] 如上所述,为了打印各种类型的文档,打印机 20 应了解有关每台计算机支持的文档的信息 30 , 40 , 和 50 . 为此,根据本发明的一个实施例,提供了一种在打印机和计算机之间执行发现操作并注册可以输出的文档的过程,如步骤中所述 200 和 205 . 这种过程参考图3描述如下,其中在打印机之间执行的操作 20 以及第一台和第二台计算机 30 和 40 举例说明。 [0047] 在步 300 , 发现模块 112 打印机的 20 多播请求信号以请求每台计算机 30 和 40 提供有关第一台和第二台计算机可以输出的文档的信息 30 或者 40 , 到计算机 30 和 40 使用发现协议通过 LAN 连接。 打印机 20 传输这样的请求,以便为第一台和第二台计算机中的每台计算机提供身份证明文件输出支持信息 30 和 40 . 请求被传输到发现模块 120 和 130 第一台和第二台电脑 30 和 40 , 分别。 每个发现模块 120 和 130 查询各文件控制模块 124 和 134,分别是关于步骤的可打印文档列表 305 和 310 , 这样每个文档控制模块 124 和 134 分步获取申请信息 315 和 320 , 分别。 应用信息表示文档信息,包括每台计算机支持的文档类型、每台计算机安装的文档软件的版本、是否可以输出、可容纳的文档分配区域。 此后,当每个文档控制模块 124 和 134 将文档信息传送给各个发现模块 120 和 130 逐步 335 和 340 , 每个发现模块 120 和 130 生成并向打印机发送包含文档信息的响应消息 20 逐步 345 和 350 . 在本示例中,除了文档信息之外,响应消息还包括网络地址。 [0048] 如上所述,每台计算机 30 和 40 提供打印机 20 具有文档支持信息,包括计算机支持的文档类型和版本、可容纳的文档分配区域、是否可以输出、网络地址等,使用发现协议,预先响应一个 可打印文档信息请求。 如果第三台电脑 50 发现操作完成后上电,第三台计算机的发现模块 50 可以直接注册有关第三台计算机支持的文档的信息 50 使用先前注册的打印机 20 . [0049] 当打印机 20 从第一台计算机和第二台计算机中的每台计算机接收包括每条文档信息的响应消息 30 和 40 通过上述步骤,打印机 20 根据接收到的每条文档信息生成表格如表1。 该表用于查找可以输出从移动端接收到的文档的计算机 10 . [0050] 根据本发明的实施例,一种使用户能够轻松连接移动终端的方法 10 和打印机 20 使用无线自动设置程序,即提供无线自动连接设置程序。 这样一个无线自动连接过程对应的步骤 210 下面结合图4和图5详细描述图2中的。 [0051] 图4是图示在无线局域网通信方案中使用无线保真(WiFi)方案的无线自动连接过程的图,其中移动终端之间的WiFi通信需要服务集标识符(SSID) 10 和打印机 20 ,认证和加密需要安全密钥,IP通信必须设置IP地址,并且需要有线等效保密(WEP)密钥值,因为认证和加密是在WEP方案中执行的。 根据本发明的实施例,使用自动生成和设置无线连接所需的所有信息的方案。 具体地,SSID、安全密钥、IP地址是使用用户在移动终端之间输入的相同信息自动生成的。 10 和打印机 20 . 根据本发明的备选实施例,可以使用随机信息来代替相同的信息。 在这种情况下,随机信息可以是在移动终端中随机生成的随机数 10 和打印机 20 . 通过该流程,可以方便的自动连接移动终端 10 到打印机 20 无需用户每次都输入无线局域网连接的每条信息。 由于每次连接尝试都会发生变化的随机信息的特性,可以获得更高的安全特性。 [0052] 参见图4,移动终端 10 和打印机 20执行同样的无线连接软件,在移动端开始建立WiFi连接 10 和打印机 20 ,分别根据用户输入。 当请求启动此类无线 LAN 自动连接过程时,打印机 20 生成并显示与移动端通用的随机信息 10 , 在打印机的显示单元上 20 对于无线自动连接,步骤 400 . 移动终端 10 在打印机的显示单元上显示一个随机数 20 , 并接收用户输入的打印机随机数 20 在一步 405 . 这样的随机数用于生成和设置无线自动连接所需的信息。 具体如步骤所示 410 和 415 、SSID、WEP等自动生成,并使用相同的哈希函数设置各自的随机数,从而完成WiFi连接。 [0053] 图5是图示在无线局域通信方案中使用蓝牙(BT)方案的无线自动连接过程的图,其中每个移动终端 10 和打印机 20 使用相同的散列函数生成设备名称和带有随机数的个人识别码 (PIN) 代码,如图 4 所示。 当移动终端开始建立蓝牙连接时 10 和打印机 20 , 打印机 20 步骤中生成并输出一个随机数 500 ,然后用户通过移动端看到并输入随机数 10 在一步 505 . 然后,打印机 20 使用随机数分步执行设备名称设置程序和 PIN 码自动生成/设置程序 510 和 515 ,分别是移动端 10 使用随机数逐步执行打印机发现操作和 PIN 码自动生成/设置过程 520 和 525 , 分别。 相应地,用户只需输入一个随机数,即可自动实现移动终端之间的无线连接。 10 和打印机 20 . [0054] 以下为移动终端与打印机之间的发现及文档输出流程,对应步骤 215 至 230 在图2中,结合图6详细描述如下。 [0055] 参考图6,用户可以通过GUI提供的“打印”菜单开始网络打印功能 108 . 当这样的开始请求被输入到移动终端时 10 , 发现模块 104 移动终端的 10 在步骤中执行发现协议 600 ,从而从发现模块请求打印机发现 112 打印机的 20 . 对于这样的请求,发现模块 104 移动终端的 10 多播 DISCOVERY_PRINTER 消息。 在收到这样的 DISCOVERY_PRINTER 消息后,打印机 20 向discovery模块发送RESPONSE_PRINTER消息,该消息是包含打印机信息的响应消息,例如自己的打印机名称、IP地址、端口信息等 104 移动终端的 10 在一步 605 . 发现模块 104 将通过这种发现过程获取的打印机信息传输到打印代理模块 106 在一步 610 . [0056] 图形用户界面 108 发送 PRINTING_CAPABILITY_REQUEST 消息请求打印机的属性信息 20 来自打印代理模块 106 在一步 615 . 这种属性信息请求用于准备“打印”菜单,使用户能够检查打印机的状态,然后配置所需的选项。 [0057] 据此,印刷剂模块 106 将 PRINTING_CAPABILITY_REQUEST 消息传输到打印管理器模块 114 打印机的 20 在一步 620 为了请求属性信息。 打印管理器模块 114通过发送与步骤中的属性信息请求对应的 PRINTING_CAPABILITY_RESPONSE 消息进行响应 625 . 这种响应消息包括移动终端请求的属性信息 10 . 这里的属性信息表示与打印相关的各种信息,包括可打印文档的类型、打印机的状态 20 ,以及有关可以设置的各种选项的信息。 [0058] 在收到 PRINTING_CAPABILITY_RESPONSE 消息后,打印代理模块 106 将 PRINTING_CAPABILITY_RESPONSE 消息传输到 GUI 108 , 在步骤 630 . 图形用户界面 108 根据收到的属性信息提供“打印”菜单。 这种“打印”菜单包括各种选项功能,包括打印机的状态信息、可打印文档的类型、彩色/黑白设置选项、水平/垂直设置选项等。当打印目标文档和各种打印选项已经 通过使用“打印”菜单指定,GUI 108 将打印目标文件传送给打印代理模块 106 在步骤中使用 SELECT_DOCUMENT 消息 635 . 打印代理模块 106 在步骤中通过使用 PRINT_REQUEST 消息组合并传输文档和指定的打印选项 640 . [0059] 通过这样一个PRINT_REQUEST消息,将与指定的打印选项组合在一起的打印目标文档传送给打印管理模块 114 打印机的 20 . 打印管理器模块 114 参考步骤中的表1等表格选择能够输出文档的计算机 642 . 更具体地说,打印机 20 将接收文件的类型、接收文件的容量、使用权限等与文件-计算机映射表如表1中的相应信息进行比较,选择能够输出接收文件的计算机。 当打印机 20 选择第一台计算机 30 ,打印管理器模块 114 向文档控制模块发送 PRINT_REQUEST 消息 124 第一台电脑的 30 在步骤 650 ,从而将文档和打印选项传输到文档控制模块 124 . [0060] 收到 PRINT_REQUEST 消息后,文档控制模块 124 将文档存储在存储的本地存储区域中 126 在步骤 655 ,然后通知打印控制模块 122 通过使用 PRINT_REQUEST 消息确定存储文档的位置和打印选项,步骤 660 . 打印控制模块 122 通过参考如表2的文档-应用表,将应用程序或输出API应用到打印选项,执行与文档或应用程序的输出API对应的应用程序,使得打印管理器模块 114 打印机的 20 可以打印文档。 据此,打印控制模块 122 向打印管理器模块发送包含打印图像的 PRINT 消息 114 在步骤 665 , 以便通过打印机驱动程序执行实际打印。 [0061] 根据本发明的实施例,无论打印机位于何处,用户都可以打印存储在移动终端中的各种文档。 另外,由于文档打印指令是在移动终端位于打印机附近的状态下发出的,因此用户可以在没有打印机信息的情况下打印移动终端的文档,并且可以立即获得打印的文档。 因此,用户无需在每次打印文档时都寻找文档应用程序并安装适用于相应打印机的打印机驱动程序,从而提高了用户的便利性。 另外,根据本发明实施例,还提供了一种简单实现移动终端与打印机无线连接的方法,使得用户能够方便地连接移动终端与打印机。 [0062]虽然本发明已参照其某些实施例进行了展示和描述; 本领域的技术人员将理解,在不脱离由所附权利要求限定的本发明的精神和范围的情况下,可以在其中进行形式和细节的各种改变。 因此,本发明的范围不受上述实施例的限制,而是由权利要求及其等同物限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102023829A(String), EP2302504A2(String), EP2302504A3(String), KR1020110029435A(String), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102023829A(String), EP2302504A2(String), EP2302504A3(String), KR1020110029435A(String), US20110063663A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.350 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102023829A(String), EP2302504A2(String), EP2302504A3(String), KR1020110029435A(String), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271667(Integer), CN102023829A(String), 1049300(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271667(Integer), EP2302504A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271667(Integer), EP2302504A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271667(Integer), KR1020110029435A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271667(Integer), US20110063663A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20110063663A1(String), US20110063663A1(String), 1300291200(Integer), 271667(Integer), 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 271587(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.653 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 271587(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.768 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185991(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185991(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185991(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.904 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185991(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.939 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.994 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:36.995 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.068 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185991(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10425523B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for controlling mobile terminal, and mobile terminal(String), 控制移动终端的方法及移动终端(String), US10425523B2(String), The present disclosure discloses a method of controlling a mobile terminal, and a mobile terminal. The method of controlling a mobile terminal includes obtaining a motion status of a user of the mobile terminal, and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status.(String), 本公开公开了一种控制移动终端的方法和移动终端。 控制移动终端的方法包括获得移动终端的用户的运动状态,以及基于获得的运动状态执行与预定事件对应的移动终端的功能。(String), US15/570543(String), 1463932800(Integer), US10425523B2(String), 1569254400(Integer), 1569254400(Integer), 美国(String), 4(Integer), CN | CN | KR(String), 5(Integer), 42(Integer), CN101150542A | CN101179533A | CN101754462A | CN102655541A | CN103179535A | CN103476985A | CN103500047A | CN103747140A | CN103763675A | CN103873342A | CN1812380A | CN1941707A | EP2608501A1 | JP2005115557A | JP2006294970A | JP2013032932A | JP2013089238A | JP2014161930A | JP2014211850A | KR101117424B1 | KR1020100021859A | KR1020100073743A | KR1020110046909A | KR1020140073232A | US20070260730A1 | US20110106530A1 | US20130104089A1 | US20130104090A1 | US20130203393A1 | US20130237204A1 | US20150112796A1 | US7039676B1 | US7512407B2 | US8213914B2 | US9032337B2 | WO2009023701A2 | WO2013029258A1(String), 13(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.636 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185992(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.782 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\b8c4c861985e43e4a81db266eade4d3f.png(String), 185992(Integer), b8c4c861985e43e4a81db266eade4d3f.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.818 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for controlling mobile terminal, and mobile terminal(String), 控制移动终端的方法及移动终端(String), US10425523B2(String), The present disclosure discloses a method of controlling a mobile terminal, and a mobile terminal. The method of controlling a mobile terminal includes obtaining a motion status of a user of the mobile terminal, and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status.(String), 本公开公开了一种控制移动终端的方法和移动终端。 控制移动终端的方法包括获得移动终端的用户的运动状态,以及基于获得的运动状态执行与预定事件对应的移动终端的功能。(String), US15/570543(String), 1463932800(Integer), US10425523B2(String), 1569254400(Integer), 1569254400(Integer), 美国(String), 3(Integer), 4(Integer), CN | CN | KR(String), 5(Integer), 42(Integer), CN101150542A | CN101179533A | CN101754462A | CN102655541A | CN103179535A | CN103476985A | CN103500047A | CN103747140A | CN103763675A | CN103873342A | CN1812380A | CN1941707A | EP2608501A1 | JP2005115557A | JP2006294970A | JP2013032932A | JP2013089238A | JP2014161930A | JP2014211850A | KR101117424B1 | KR1020100021859A | KR1020100073743A | KR1020110046909A | KR1020140073232A | US20070260730A1 | US20110106530A1 | US20130104089A1 | US20130104090A1 | US20130203393A1 | US20130237204A1 | US20150112796A1 | US7039676B1 | US7512407B2 | US8213914B2 | US9032337B2 | WO2009023701A2 | WO2013029258A1(String), \20230420\b8c4c861985e43e4a81db266eade4d3f.png(String), 13(Integer), 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 1. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises transmitting the information representing the motion status of the user to a counterpart device which is in communication with the mobile terminal, andwherein a GUI object representing the motion status of the user is displayed, based on the transmitted information representing the motion status, in an interface of a contact application which is executed in the counterpart device.(String), 1.一种移动终端的控制方法、方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,执行移动终端的功能包括将表示用户的运动状态的信息发送到与移动终端通信的对方设备,以及其中,基于所发送的代表动作状态的信息,在对方设备中执行的联系人应用的界面中显示代表用户的动作状态的GUI对象。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 2. The method of claim 1, wherein the obtaining of the information representing the motion status comprises:periodically receiving output data from an inertia sensor of the mobile terminal;reading a feature value from the received output data; anddetermining the motion status corresponding to the read feature value from a table of mapping relationships between motion statuses and feature values.(String), 2.如权利要求1所述的方法,其中获取表示运动状态的信息包括:周期性地接收移动终端的惯性传感器输出的数据;从接收到的输出数据中读取特征值;和从运动状态与特征值的映射关系表中确定读取的特征值对应的运动状态。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 3. The method of claim 1, wherein the obtaining of the information representing the motion status comprises:obtaining, by a global positioning system (GPS), starting location information and ending location information corresponding to a predetermined time interval;calculating a movement velocity corresponding to the predetermined time interval, based on the starting location information and the ending location information; anddetermining the motion status corresponding to the calculated movement velocity from a table of mapping relationships between motion statuses and movement velocities.(String), 3.如权利要求1所述的方法,其中获取表示运动状态的信息包括:通过全球定位系统(GPS)获取预定时间间隔对应的起始位置信息和结束位置信息;基于起始位置信息和结束位置信息计算对应于预定时间间隔的运动速度;和根据运动状态与运动速度的映射关系表,确定计算出的运动速度对应的运动状态。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 4. The method of claim 1, wherein the contact application is an instant message application,wherein the performing of the function of the mobile terminal further comprises transmitting the information representing the motion status of the user to the counterpart device in response to execution of the instant message application, andwherein a GUI object representing the motion status of the user displayed on an instant messaging interface of the instant messaging application of the counterpart device is updated, based on the transmitted information representing the motion status.(String), 4.如权利要求1所述的方法,其中联系人应用程序是即时消息应用程序,其中,移动终端的功能的执行进一步包括响应于即时消息应用的执行将表示用户的运动状态的信息发送到对方设备,以及其中,基于所发送的代表动作状态的信息,更新对方设备的即时通讯应用的即时通讯界面上显示的代表用户的动作状态的GUI对象。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 5. The method of claim 1, wherein the contact application is a call application,wherein the performing of the function of the mobile terminal further comprises transmitting the information representing the motion status of the user to the counterpart device in response to execution of the call application, andwherein a GUI object representing the motion status of the user displayed on a call interface of the call application of the counterpart device, based on the transmitted information representing the motion status.(String), 5.如权利要求1所述的方法,其中联系人应用程序是呼叫应用程序,其中,移动终端的功能的执行还包括响应于呼叫应用的执行将表示用户的运动状态的信息发送到对方设备,以及其中,基于所传输的表示用户动作状态的信息,在对端设备的通话应用的调用界面上显示表示用户动作状态的GUI对象。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 6. The method of claim 1, wherein the contact application is an address list application,wherein the performing of the function of the mobile terminal further comprises transmitting the information representing the motion status of the user to the counterpart device in response to execution of the address list application, andwherein a GUI object representing the motion status of the user displayed on an address list of the address list application of the counterpart device, based on the transmitted information representing the motion status.(String), 6.如权利要求1所述的方法,其中联系人应用程序是地址列表应用程序,其中,移动终端的功能的执行进一步包括响应于地址列表应用的执行将表示用户的运动状态的信息发送到对方设备,以及其中,基于所发送的代表动作状态的信息,代表用户的动作状态的GUI对象被显示在对方设备的地址列表应用的地址列表上。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 7. The method of claim 1, wherein the contact application is an address list, andwherein the performing of the function of the mobile terminal further comprises displaying, in real time, a motion status of a contact in the address list and a time period required by the contact from a current location to a destination on a user interface in response to execution of a real-time timing function for the contact, based on the obtained information representing the motion status.(String), 7.如权利要求1所述的方法,其中联系人应用程序是一个地址列表,并且其中,所述移动终端的功能的执行还包括:实时显示通讯录中联系人的运动状态,以及该联系人从当前位置到目的地所需的时间,以响应用户界面。基于获得的表示运动状态的信息,为接触执行实时计时功能。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 8. The method of claim 1, the method further comprising:receiving information representing a motion status of another user of the counterpart device which is in communication with the mobile terminal, andwherein the performing of the function of the mobile terminal further comprises displaying a GUI object representing the motion status of the another user, based on the received information representing the motion status of the another user, in an interface of a contact application which is executed in the mobile terminal.(String), 8.如权利要求1所述的方法,该方法还包括:接收表示与移动终端通信的对方设备的另一用户的运动状态的信息,以及其中,移动终端的功能的执行还包括基于接收到的表示另一个用户的运动状态的信息,在联系人应用的界面中显示表示另一个用户的运动状态的GUI对象,该联系人应用在以下步骤中执行:移动终端。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 9. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises automatically switching a home screen layout of the mobile terminal in response to execution of the mobile terminal, based on the obtained information representing the motion status.(String), 9.一种移动终端的控制方法,该方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,执行移动终端的功能包括基于获得的表示运动状态的信息,响应于移动终端的执行自动切换移动终端的主屏幕布局。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 10. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises automatically adjusting a ringtone or a call volume of the mobile terminal when receiving a call, based on the obtained information representing the motion status.(String), 10.一种移动终端的控制方法,该方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,移动终端功能的执行包括:基于获取的表示运动状态的信息,在来电时自动调整移动终端的铃声或通话音量。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 11. A method of controlling a mobile terminal, the method comprising:obtaining information representing a motion status of a user of the mobile terminal; andperforming a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the mobile terminal comprises, when an incoming call or a received short message is not answered within a predetermined unanswered time period, sending a status reply including the obtained motion status to an opposite party of the incoming call or the received short message, based on the obtained information representing the motion status.(String), 11.一种移动终端的控制方法,该方法包括:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,所述移动终端的功能的执行包括:当来电或收到的短信在预定无人应答时间内无人应答时,向来电或对方发送包括获取的动作状态在内的状态回复。接收到的短消息,根据获取到的代表运动状态的信息。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 12. A mobile terminal comprising:a communication interface;at least one sensor configured to detect a motion of the mobile terminal;a memory storing one or more instructions; andat least one processor configured to execute the one or more instructions at least to:obtain information representing a motion status of a user of the mobile terminal; andperform a function of the mobile terminal corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the at least one processor executes the one or more instructions to transmit the information representing the motion status of the user to a counterpart device which is in communication with the mobile terminal, andwherein a GUI object representing the motion status of the user is displayed, based on the transmitted information representing the motion status, in an interface of a contact application which is executed in the counterpart device.(String), 12.移动终端包括:通信接口;至少一个传感器,用于检测移动终端的运动;存储一条或多条指令的存储器;和至少一个处理器被配置为执行一个或多个指令至少以:获取表示移动终端用户运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件对应的移动终端的功能,其中,至少一个处理器执行一个或多个指令以将表示用户的运动状态的信息发送到与移动终端通信的对应设备,并且其中,基于所发送的代表动作状态的信息,在对方设备中执行的联系人应用的界面中显示代表用户的动作状态的GUI对象。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:37.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185992(Integer), 13. A computer program product comprising a non-transitory computer readable storage medium comprising a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, causes the computing device to perform operations of:obtaining information representing a motion status of a user of the computing device; andperforming a function of the computing device corresponding to a predetermined event, based on the obtained information representing the motion status,wherein the performing of the function of the computing device comprises transmitting the information representing the motion status of the user to a counterpart device which is in communication with the computing device, andwherein a GUI object representing the motion status of the user is displayed, based on the transmitted information representing the motion status, in an interface of a contact application which is executed in the counterpart device.(String), 13.计算机程序产品包括一种非暂时性计算机可读存储介质,包括存储在其中的计算机可读程序,其中计算机可读程序当在计算设备上执行时使计算设备执行以下操作:获取表示计算设备用户的运动状态的信息;和基于获得的表示运动状态的信息,执行与预定事件相对应的计算设备的功能,其中计算设备的功能的执行包括将表示用户的运动状态的信息发送到与计算设备通信的对应设备,并且其中,基于所发送的代表动作状态的信息,在对方设备中执行的联系人应用的界面中显示代表用户的动作状态的GUI对象。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.162 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185992(Integer), TECHNICAL FIELD [0001]The present disclosure relates to a method of controlling a mobile terminal, and a mobile terminal. BACKGROUND ART [0002]To more effectively utilize functions of a mobile terminal, information about a status of a user of the mobile terminal may be reflected. However, if the user directly selects and sets the information about the status of the user, an actual status of the user cannot be accurately reflected. DETAILED DESCRIPTION OF THE INVENTION Technical Problem [0003]The present disclosure provides a method of controlling a mobile terminal, and a mobile terminal, whereby functions of the mobile terminal are more effectively utilized by using information about an actual motion status of a user of the mobile terminal. Technical Solution [0004]According to a first aspect of the present invention, there is provided a method of controlling a mobile terminal, the method including obtaining a motion status of a user of the mobile terminal; and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status. [0005]The obtaining of the motion status may include periodically receiving output data from an inertia sensor of the mobile terminal; reading a feature value from the received output data; and determining a motion status corresponding to the read feature value from a table of mapping relationships between motion statuses and feature values. [0006]The obtaining of the motion status may include obtaining, by a global positioning system (GPS), starting location information and ending location information corresponding to a predetermined time interval; calculating a movement velocity corresponding to the predetermined time interval, based on the starting location information and the ending location information; and determining a motion status corresponding to the calculated movement velocity from a table of mapping relationships between motion statuses and movement velocities. [0007]The performing of the function of the mobile terminal may include updating a motion status of an instant messaging user displayed on an instant messaging interface in response to execution of an instant message application, based on the obtained motion status. [0008]The performing of the function of the mobile terminal may include updating a motion status of an opposite party displayed on a call interface in response to execution of a call application, based on the obtained motion status. [0009]The performing of the function of the mobile terminal may include updating a motion status of a contact displayed on an address list in response to execution of an address list application, based on the obtained motion status. [0010]The performing of the function of the mobile terminal may include displaying, in real time, a motion status of a contact in an address list and a time period required by the contact from a current location to a destination on a user interface in response to execution of a real-time timing function for the contact, based on the obtained motion status. [0011]The performing of the function of the mobile terminal may include automatically switching a device mode in response to execution of the mobile terminal, based on the obtained motion status. [0012]The performing of the function of the mobile terminal may include adjusting a ringtone or a call volume of the mobile terminal when receiving a call, based on the obtained motion status. [0013]The performing of the function of the mobile terminal may include, when an incoming call or a received short message is not answered for a long time, sending a status reply including the obtained motion status to an opposite party of the incoming call or the received short message, based on the obtained motion status. [0014]According to a second aspect of the present invention, there is provided a mobile terminal including a memory configured to store computer executable instructions; and at least one processor configured to obtain a motion state of a user of the mobile terminal and perform a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion state, by executing the computer executable instructions. [0015]According to a third aspect of the present invention, there is provided a method for communication of a mobile terminal, the method including selecting a setting item for resetting communication setting; detecting a motion status of the mobile terminal in real time; obtaining a current motion status of the mobile terminal; and resetting the selected setting item according to the obtained motion status. [0016]According to a fourth aspect of the present invention, there is provided a mobile terminal including a system setting module configured to select a setting item for resetting communication setting; a motion status determining module configured to detect a motion status of the mobile terminal in real time, obtain a current motion status of the mobile terminal, and send the obtained motion status to the communication resetting module; and a communication resetting module configured to reset the selected setting item according to the obtained motion status. [0017]As shown in the above technical solutions of the present disclosure, the motion status of the mobile terminal may be detected in real time, and the current motion status of the mobile terminal may be obtained. The selected setting item may be reset according to the obtained motion status. Accordingly, the communication setting may be performed automatically according to an actual motion status of the mobile terminal, thereby making the communication setting more accurate and intelligent. DESCRIPTION OF THE DRAWINGS [0018]FIG. 1 is a schematic flowchart illustrating a communication method of a mobile terminal, according to an embodiment of the present disclosure. [0019]FIG. 2 is a flowchart of a method, performed by an inertia sensor, of determining a motion status, according to an embodiment of the present disclosure. [0020]FIG. 3 is a flowchart of a method, performed by a global positioning system (GPS), of determining a motion status, according to an embodiment of the present disclosure. [0021]FIG. 4 is a flowchart of a process of outputting motion statuses S0 and S1 when they are determined by a combination of an inertia sensor and a GPS. [0022]FIG. 5 is a flowchart of a process of outputting a final motion status, based on the motion statuses S0 and S1, according to an embodiment of the present disclosure. [0023]FIG. 6 shows interfaces for updating a motion status displayed on an instant messaging interface according to an embodiment of the present disclosure. [0024]FIG. 7 is a flowchart of a method of determining a motion track, according to an embodiment of the present disclosure. [0025]FIG. 8 shows interfaces for updating a motion status displayed in a call process according to an embodiment of the present disclosure. [0026]FIG. 9 shows interfaces for updating a motion status of a contact in an address list, according to an embodiment of the present disclosure. [0027]FIG. 10 shows interfaces prompted to the user when the motion status of a contact displayed in the address list changes according to a predefined mode or when the motion status of the contact is a predefined motion status, according to an embodiment of the present disclosure. [0028]FIG. 11 shows interfaces that display the motion track and the location information of each party member in real time according to a party assistant function in instant messaging, according to an embodiment of the present disclosure. [0029]FIG. 12 shows a process of performing a real-time timing function for a contact in an address list, according to an embodiment of the present disclosure. [0030]FIG. 13 illustrates a process of automatically recommending participating in a group according to a motion status of a user, according to an embodiment of the present disclosure. [0031]FIG. 14 illustrates interfaces on which a device mode is automatically switched according to a motion status of a user, according to an embodiment of the present disclosure. [0032]FIG. 15 illustrates a process of automatically adjusting a call ringtone or a call volume according to a motion status of a user, according to an embodiment of the present disclosure. [0033]FIG. 16 illustrates a process of automatically performing status replies to an incoming call and a received short message according to a current motion status of a user, according to an embodiment of the present disclosure. [0034]FIGS. 17A-17C are block diagrams illustrating a structure of a mobile terminal, according to an embodiment of the present disclosure. [0035]FIG. 18 is a flowchart illustrating a method of controlling a mobile terminal, according to an embodiment of the present disclosure. BEST MODE [0036]A method of controlling a mobile terminal includes obtaining a motion status of a user of the mobile terminal; and performing a function of the mobile terminal corresponding to a predetermined event, based on the obtained motion status. Mode of the Invention [0037]Exemplary embodiments of the present disclosure will now be described more fully with reference to the accompanying drawings. The various embodiments below are only to specify the inventive concept and are not to restrict or limit the right scope of the inventive concept. It is analyzed that those which could be readily inferred by one of ordinary skill in the art to which the inventive concept belongs from the detailed description and the various embodiments belong to the right scope of the inventive concept. [0038]Terms “configured” or “include” used herein should not be construed as necessary including all of several components or several steps written in the specification, but as not including some of the components or steps or as further including additional components or steps. [0039]While such terms as “first,”“second,” etc., may be used to describe various components, such components must not be limited to the above terms. The above terms are used only to distinguish one component from another. [0040]The below embodiments relate to a mobile terminal and a method of controlling a mobile terminal, and a detailed description of matters well known to one of ordinary skill in the art to which the below embodiments pertain will be omitted. [0041]The present disclosure is described in detail with reference to the attached drawings and the embodiments. [0042]FIG. 1 is a schematic flowchart illustrating a method for communication of a mobile terminal according to an embodiment of the present disclosure. The method includes the following operations. [0043]In operation 101, a setting item for resetting communication settings is selected. [0044]When the setting item for resetting communication settings is determined based on a motion status, at least one setting item may be selected. For example, at least one of fourteen items may be selected, which include an item for updating a motion status of an instant messaging user in real time, an item for updating a motion track of an instant messaging user in real time, an item for updating a motion status of a user in a call process in real time, an item for updating a motion status of a contact in an address list in real time, an item for a prompt of a motion status of a contact in an address list, an item for enabling a party assistant function in instant messaging, an item for enabling a real-time timing function for a contact in an address list, an item for automatically recommending participating in a group according to a motion status of a user, an item for automatically performing a prompt according to a motion status of a user, an item for automatically switching a device mode according to a motion status of a user, an item for automatically switching a topic mode according to a motion status of a user, an item for automatically switching a do-not-disturb mode according to a motion status of a user, an item for call control, and an item for status reply. [0045]In operation 102, the motion status of the mobile terminal is detected in real time. [0046]Multiple methods for detecting the motion status of the mobile terminal may be used. For example, a motion status of the mobile terminal may be detected by an inertia sensor, by a global positioning system (GPS), or by a combination of the inertia sensor and the GPS. [0047]In operation 103, a current motion status of the mobile terminal is obtained. [0048]A currently-detected motion status of the mobile terminal is obtained. [0049]In operation 104, the selected setting item is reset according to the obtained motion status. [0050]After obtaining the current motion status, the selected setting item may be reset. Because setting items are different, methods for resetting the setting items are different. [0051]In an example of the present disclosure, the motion status of the mobile terminal is detected in real time, the current motion status of the mobile terminal is obtained, and the selected setting item is reset according to the obtained motion status. Accordingly, the communication setting may be performed automatically according to an actual motion status of the mobile terminal, thereby making the communication setting more accurate and intelligent. [0052]Methods for detecting a motion status will now be described according to some examples. [0053]In a first example, the motion status may be detected by an inertia sensor. [0054]The mobile terminal may include an inertia sensor. For example, the inertia sensor may be an acceleration sensor or a gyroscope. [0055]A method of detecting the motion status by the inertia sensor includes: periodically receiving output data of the inertia sensor and adding the output data to a storage queue; when the length of the storage queue is larger than a predefined value, processing data in the storage queue to extract a feature value; and finding the motion status from a table of mapping relationships between motion statuses and feature values according to the extracted feature value. [0056]Further, the accuracy of motion status determination may be improved through the following methods. [0057]The process of detecting the motion status by the inertia sensor may be repeated for N0 times, and the determined motion status may be recorded every time the process of detecting the motion status by the inertia sensor is performed. [0058]The number of times each motion status is detected is counted and represented as N. [0059]If a motion status S meets a condition of N>N0*m, the motion status S is determined as a final motion status, wherein 0N 的条件 0 *m,运动状态S被确定为最终运动状态,其中0 Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104821991A(String), CN105657188A(String), CN105657188B(String), EP3300342A1(String), EP3300342A4(String), EP3300342B1(String), KR1020160137446A(String), KR102321363B1(String), US10425523B2(String), US20180176363A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.385 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104821991A(String), CN105657188A(String), CN105657188B(String), EP3300342A1(String), EP3300342A4(String), EP3300342B1(String), KR1020160137446A(String), KR102321363B1(String), US10425523B2(String), US20180176363A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104821991A(String), CN105657188A(String), CN105657188B(String), EP3300342A1(String), EP3300342A4(String), EP3300342B1(String), KR1020160137446A(String), KR102321363B1(String), US10425523B2(String), US20180176363A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.421 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.422 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.422 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271585(Integer), CN104821991A(String), 1049293(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), CN105657188A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271585(Integer), CN105657188B(String), 1049310(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.524 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), EP3300342A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.558 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), EP3300342A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.594 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), EP3300342B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), KR1020160137446A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), KR102321363B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), US10425523B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271585(Integer), US20180176363A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN104821991A(String), CN104821991A(String), 1438704000(Integer), 271585(Integer), 185869(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.883 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185992(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.917 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.917 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185992(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.952 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:38.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185992(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185992(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.072 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.160 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185992(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120309450A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for Controlling Communication States of Mobile Terminal and Mobile Terminal(String), 控制移动终端通信状态的方法及移动终端(String), US20120309450A1(String), The invention provides a method for controlling communication states of a mobile terminal and the mobile terminal. The method comprises: the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; and the mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are inconsistent, adjusting the current communication state to the communication state corresponding to the planned time period. The invention allows the user to set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time.(String), 本发明提供了一种控制移动终端通信状态的方法及移动终端。 该方法包括:移动终端通过特定的设置界面接收并存储用户输入的计划时间段和与计划时间段对应的通信状态; 移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态 到计划时间段对应的通信状态。 本发明允许用户根据自己的工作或学习需要在移动终端中设置时间规划和相应的通信状态,从而在闲暇时保持正常通信的同时,避免来电和短信带来的不必要的打扰。(String), US13/575703(String), 1277827200(Integer), US20120309450A1(String), 1354723200(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 3(Integer), US20100042827A1 | US6317593B1 | US7302272B2(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185993(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7380909e2cff405b806c4b845095f7a3.png(String), 185993(Integer), 7380909e2cff405b806c4b845095f7a3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.933 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.933 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for Controlling Communication States of Mobile Terminal and Mobile Terminal(String), 控制移动终端通信状态的方法及移动终端(String), US20120309450A1(String), The invention provides a method for controlling communication states of a mobile terminal and the mobile terminal. The method comprises: the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; and the mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are inconsistent, adjusting the current communication state to the communication state corresponding to the planned time period. The invention allows the user to set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time.(String), 本发明提供了一种控制移动终端通信状态的方法及移动终端。 该方法包括:移动终端通过特定的设置界面接收并存储用户输入的计划时间段和与计划时间段对应的通信状态; 移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态 到计划时间段对应的通信状态。 本发明允许用户根据自己的工作或学习需要在移动终端中设置时间规划和相应的通信状态,从而在闲暇时保持正常通信的同时,避免来电和短信带来的不必要的打扰。(String), US13/575703(String), 1277827200(Integer), US20120309450A1(String), 1354723200(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 3(Integer), US20100042827A1 | US6317593B1 | US7302272B2(String), \20230420\7380909e2cff405b806c4b845095f7a3.png(String), 6(Integer), 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:39.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185993(Integer), 1. A method for controlling communication states of a mobile terminal comprising:the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; andthe mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are not consistent, adjusting the current communication state to the communication state corresponding to the planned time period.(String), 1.一种移动终端通信状态控制方法包括:移动终端通过特定的设置界面接收并存储用户输入的计划时间段以及与计划时间段对应的通信状态;和移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态到计划时间段对应的通信状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185993(Integer), 2. The method according to claim 1, further comprising:the mobile terminal receiving authentication information input by the user, and detecting whether the authentication information is legal, and if yes, entering the specific setup interface.(String), 2.根据权利要求1所述的方法,还包括:移动终端接收用户输入的认证信息,检测认证信息是否合法,若合法则进入具体设置界面。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185993(Integer), 3. The method according to claim 1, further comprising:if the mobile terminal detects that the current time is in the planned time period, calculating duration from the current time to the end time of the planned time period; andmaintaining the communication state corresponding to the planned time period in the duration.(String), 3.根据权利要求1所述的方法,还包括:若移动终端检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长;和在duration中保持计划时间段对应的通信状态。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185993(Integer), 4. A mobile terminal comprising:a setting module configured to receive and store a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface;a processing module configured to detect whether the current time is in the planned time period, if yes, detect whether the current communication state is consistent with the communication state corresponding to the planned time period stored in the setting module, and if they are not consistent, output a signal to a communication module; andthe communication module configured to receive the signal from the processing module, and then adjust the current communication state to the communication state corresponding to the planned time period and stored in the setting module.(String), 4.移动端包括:设置模块,用于接收并存储用户通过特定设置界面输入的计划时间段和与计划时间段对应的通信状态;处理模块,用于检测当前时间是否在计划时间段内,如果是,则检测当前通信状态与设置模块中存储的计划时间段对应的通信状态是否一致,如果不一致,输出信号给通信模块;和通讯模块,用于接收来自处理模块的信号,将当前的通讯状态调整为设置模块中存储的计划时间段对应的通讯状态。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185993(Integer), 5. The mobile terminal according to claim 4, further comprising an authentication module, whereinthe authentication module is configured to receive authentication information input by the user, and detecting whether the authentication information is legal, and if yes, output a signal to the setting module; andthe setting module is further configured to receive the signal of the authentication module and then enter the specific setup interface.(String), 5.根据权利要求4所述的移动终端,还包括认证模块,其中鉴权模块,用于接收用户输入的鉴权信息,检测鉴权信息是否合法,若合法,则向设置模块输出信号。和设置模块还用于接收鉴权模块的信号,进入特定的设置界面。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185993(Integer), 6. The mobile terminal according to claim 4, whereinthe processing module is further configured to calculate duration from the current time to the end time of the planned time period if detecting that the current time is in the planned time period, and output the calculated duration to the communication module; andthe communication module is further configured to receive the duration and maintain the communication state corresponding to the planned time period in the duration.(String), 6.根据权利要求4所述的移动终端,其中处理模块,还用于若检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长,并将计算出的时长输出给通信模块。和通信模块还用于接收时长,并在该时长内保持计划时间段对应的通信状态。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185993(Integer), TECHNICAL FIELD [0001]The present invention relates to mobile communications, and more particularly, to a method for controlling communication states of a mobile terminal and the mobile terminal. BACKGROUND OF THE RELATED ART [0002]In the current information society, roles of information and communication are more and more important. Different users have different demands on functions of mobile terminals (such as, mobile phones, Personal Handy-phone Systems (PHS)). When services are busy or some transactions are required to be processed tranquilly, incoming calls or text messages will certainly affect users' attention. In a classroom where tens of students flock together, for example, incoming and outgoing short messages and MMS (Multimedia Messaging Service) notification messages of mobile communication terminals in class time will seriously affect students' class attention and teachers' teaching process. Moreover, cross-radiation due to the mobile terminals inside the classroom will seriously affect the students' health. SUMMARY OF THE INVENTION [0003]A object of the present invention is to provide a method for controlling communication states of a mobile terminal and the mobile terminal such that a user can set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time. [0004]In order to achieve the aforementioned object, the present invention provides a method for controlling communication states of a mobile terminal comprising:[0005]the mobile terminal receiving and storing a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface; and[0006]the mobile terminal detecting whether the current time is in the planned time period, if yes, detecting whether the current communication state is consistent with the communication state corresponding to the stored planned time period, and if they are not consistent, adjusting the current communication state to the communication state corresponding to the planned time period. [0007]Preferably, the method also comprises:[0008]the mobile terminal receiving authentication information input by the user, and detecting whether the authentication information is legal, and if yes, entering the specific setup interface. [0009]Preferably, the method also comprises:[0010]if the mobile terminal detects that the current time is in the planned time period, calculating duration from the current time to the end time of the planned time period; and[0011]maintaining the communication state corresponding to the planned time period in the duration. [0012]The present invention also provides a mobile terminal comprising:[0013]a setting module configured to receive and store a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface;[0014]a processing module configured to detect whether the current time is in the planned time period, if yes, detect whether the current communication state is consistent with the communication state corresponding to the planned time period stored in the setting module, and if they are not consistent, output a signal to a communication module; and[0015]the communication module configured to receive the signal from the processing module, and then adjust the current communication state to the communication state corresponding to the planned time period and stored in the setting module. [0016]Preferably, the mobile terminal also comprises an authentication module. [0017]The authentication module is configured to receive authentication information input by the user, and detecting whether the authentication information is legal, and if yes, output a signal to the setting module. [0018]The setting module is further configured to receive the signal of the authentication module and then enter the specific setup interface. [0019]Preferably, the mobile terminal also has the following features:[0020]the processing module is further configured to calculate duration from the current time to the end time of the planned time period if detecting that the current time is in the planned time period, and output the calculated duration to the communication module; and[0021]the communication module is further configured to receive the duration and maintain the communication state corresponding to the planned time period in the duration. [0022]Compared with the prior art, the present invention has the following advantages. [0023]The user can set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time. [0024]In the present invention, the communication states of the mobile terminal in different time periods are set by planning of the user's work and rest time, to reduce harm of radiation of the mobile communication terminal to the user on the basis of meeting basic communication functions. Moreover, due to reduction of network communications, standby time of the mobile communication terminal will certainly be prolonged greatly. [0025]The present invention, which is designed specifically for students, has broad market prospects and is particularly suitable to people in universities, high schools, junior middle schools, and elementary schools. BRIEF DESCRIPTION OF DRAWINGS [0026]FIG. 1 is a block diagram of a mobile terminal in accordance with an embodiment of the present invention; [0027]FIG. 2 is a flow chart of a method for controlling communication states of a mobile terminal in accordance with an embodiment of the present invention; and [0028]FIG. 3 is a flow chart of an application example of a method for controlling communication states of a mobile terminal in accordance with the present invention. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0029]Preferred embodiments of the technical scheme of the present invention will be further described below in detail in conjunction with the accompanying drawings. [0030]FIG. 1 is a block diagram of a mobile terminal in accordance with an embodiment of the present invention. As shown in FIG. 1, the mobile terminal 100 in accordance with the embodiment comprises a setting module 110, a processing module 120 and a communication module 130. [0031]The setting module 110 is configured to receive and store a planned time period input by a user and a communication state corresponding to the planned time period through a specific setup interface. [0032]Specifically, the setup interface for time planning and communication states is added to the mobile terminal such that the user can set the time planning and the corresponding communication states in the setup interface. The setting module 110 receives the time planning and the corresponding communication state information input by the user, and stores the setting result into a file system. [0033]The processing module 120 is configured to detect whether the current time is in the planned time period stored by the setting module 110, if yes, detect whether the current communication state is consistent with the communication state corresponding to the planned time period stored in the setting module 110, and if they are not consistent, output a signal to the communication module 130. [0034]The communication module 130 is configured to receive the signal from the processing module 120, and then adjust the current communication state to the communication state corresponding to the planned time period and stored in the setting module 110. [0035]For example, assuming that the mobile terminal is currently in a normal communication state, that is, the communication module 130 is in an on state. If the user sets a planned time period, and sets a communication state corresponding to the planned time period to be an off state, when the processing module 120 detects that the current time is in the time period set by the user, the communication module 130 is turned off. [0036]Thus, for the mobile terminal in accordance with this embodiment, the user can set time planning and corresponding communication states in his mobile terminal according to his own work or learning needs, in order to avoid unnecessary disturbance from incoming calls and short messages while keeping normal communication in his leisure time. [0037]Preferably, the mobile terminal in accordance with this embodiment might also comprise an authentication module 140, which is configured to receive authentication information input by the user, detect whether the authentication information is legal, and if it is legal, output a signal to the setting module 110. After receiving the signal from the authentication module 140, the setting module 110 enters the specific setup interface. That is, a user (such as, parents) who has passed the authentication (for example, by entering a user name, password, etc.) can access to the planed setup page, otherwise the user is refused to access to the planed setup interface. [0038]Preferably, the processing module 120 is further configured to calculate duration from the current time to the end time of the planned time period if detecting that the current time is in the planned time period, and then output the calculated duration to the communication module 130. After the communication module 130 receives the duration information, it maintains the communication state corresponding to the planned time period in the duration. [0039]For example, if the user sets to close communication from 9:00 am to 10:00 am and the processing module 120 detects that the current time is in the planned time period at 9 o'clock in the morning and calculates the duration of one hour from the current time to the end time of the planned time period, then the communication module 130 will maintain the closed state for one hour and return to the normal communication after one hour. [0040]FIG. 2 is a flow chart of a method for controlling communication states of a mobile terminal in accordance with an embodiment of the present invention. As shown in FIG. 2, the method in accordance with the embodiment comprises the following steps. [0041]In S11, the mobile terminal receives authentication information input by a user. [0042]For example, the user inputs a user name, password, etc. [0043]In S12, whether the authentication information is legal is detected, if it is legal, a planed setup interface is entered, and step S13 is performed, otherwise, the planed setup interface is refused to be entered. [0044]In S13, the mobile terminal receives the planned time period input by the user and planning information of a communication state corresponding to the planned time period through the planned setup interface, and then stores the planning information. [0045]Assuming that the planning information input by the user contains a planned time period such as from 9:00 am to 10:00 am, and a communication state, such as closed communication. [0046]In S14, the mobile terminal detects whether the current time is in the planned time period, and if yes, step S15 is performed; otherwise, step S17 is performed. [0047]In S15, whether the current communication state is consistent with the stored communication state corresponding to the planned time period is detected, if they are not consistent, step S16 is performed; otherwise, step S17 is performed. [0048]In S16, the current communication state is adjusted to the communication state corresponding to the planned time period. [0049]In S17, the current communication state is maintained. [0050]If the current time is 8:00 am, the normal communication state is maintained; and if the current time is 9:00 am, the communication is closed. [0051]Preferably, after the mobile terminal detects that the current time is in the planned time period, the method further comprises the following steps. [0052]In S18, the duration from the current time to the end time of the planned time period is calculated. [0053]For example, the duration is from 9:00 am to 10:00 am, i.e., one hour. [0054]In S19, the communication state corresponding to the planned time period in the duration is maintained. [0055]For example, the communication closed state is maintained for one hour, and then the normal communication state is restored after one hour. [0056]An application example of a method for controlling communication states of a mobile terminal according to the present invention will be described below. [0057]In this application example, according to features of students, students' class time and non-class time are divided by semester, daily class time and the like. For example, the following items are set through interfaces of the mobile terminal. [0058]1. The following several time periods are set. [0059]a) Semester time periods are set. [0060]The students' school time periods are set. For example, school time of a student is set as follows: NameStartEndFirst semester2009 Mar. 12009 Jul. 1Second semester2009 Sep. 12010 Jan. 20. . .. . .. . . [0061]Saturdays and Sundays are rest days and can be marked individually. [0062]b) Class time is set. [0063]For example, the class time in a school is set as follows: Class timeStartEndFirst class in the morning 8:00 8:45Second class in the morning 9:00 9:45Third class in the morning10:0010:45Fourth class in the morning11:0011:45First class in the afternoon14:0014:45Second class in the afternoon15:0015:45Third class in the afternoon16:0016:45. . .. . . [0064]c) Sleep time periods are set. [0065]The sleep time periods in the afternoon and at night are set as follows: Sleep time periodStartEndAfternoon13:0014:00Night22:0006:30 [0066]d) Special time periods are set. [0067]For example, when there is emergency at home, kids are required to be connected at any time. For example: Special time periodStartEndEmergency at home2009 Jan. 018:002009 Jan. 0120:00Grandpa is coming2009 Dec. 058:002009 Dec. 0520:00. . .. . .. . . [0068](2) Communication states, mainly communication states of the mobile communication terminal in different time periods, are set. [0069]The above time periods mainly include class time, sleep time, special time, and other time. Setting items of the communication states include normal communication and closed communication. The closed communication means that a communication module (a RF module) in the mobile terminal is turned off, and the mobile terminal can neither receive nor send messages. [0070]For example, a student's communication states are set as follows: Time periodSetting of communication statesSpecial timeNormal communicationClass timeClosed communicationSleep timeClosed communicationOther timeNormal communication [0071]FIG. 3 illustrates a flow chart of a method for controlling communication states of a mobile terminal in accordance with the application example, which comprises the following steps. [0072]In S201, the mobile terminal is turned on. [0073]In S202, it is detected that the current time is in which planned time period set above, such as, the semester time period, the daily class time period, special time period, or sleep time period. [0074]In S203, it is determined whether the current communication state is consistent with the set planned communication state, if they are inconsistent, the current communication state is adjusted to the set planned communication state; otherwise, the current communication state is maintained unchanged. [0075]For example, the communication module at the current time is turned on or off. [0076]In S204, the duration from the current time to a time point at which the recent communication state needs to be changed is calculated. [0077]In S205, the current communication state is maintained in the duration; after the duration, step S202 is performed. [0078]In S206, if the user turns the mobile terminal off, the operation ends. [0079]In this application example, the time planning function is added to the common mobile communication terminal, that is, one day of students can be divided into different time periods, such as class time periods, sleep time periods, special time periods and other time periods. In the class time periods and sleep time periods, by turning off the communication module in the mobile terminal, the students in the class will not be disturbed by ring tones of incoming calls, SMS, MMS, and the like, thus ensuring the normal teaching order in the classroom; meanwhile, due to turning off of the communication module, radiation of the mobile communication terminal is reduced to zero. In the other time periods, the communication module of the mobile terminal is turned on to meet people's communication requirements. In the special time periods, for example, when there is an emergency at home, the communication module can be set to be in an on state all the time to ensure convenient communication with outside in the special time periods. [0080]As described above, by planning the students' time, communication states of mobile communication terminals in different time periods can be set to greatly reduce radiation of the mobile communication terminals to users. Due to the reduction of network traffic, the electricity consumption will certainly be decreased such that standby time of the mobile communication terminals can be increased greatly. [0081]Because the mobile terminal in accordance with the present invention can greatly reduce the radiation to students, teachers and students in the class, teachers and students will not be disturbed in class by incoming calls, text messages, and the like, and normal communication can be maintained after class, it will certainly especially liked by the majority of students, teachers and communities. [0082]The present invention can be applied to not only students, but also all users who need to set the corresponding communication states according to different time periods. [0083]The above embodiments are only examples of illustrating a method for controlling communication states of a mobile terminal in accordance with the present invention and should not be construed as limitation of the present invention. Various equivalent variations or substitutions may be made according to description of the technical scheme of the present invention and its preferred embodiments, and all these equivalent variations and substitutions should be covered within the protection scope of the claims of the present invention. INDUSTRIAL APPLICABILITY [0084]The technical solution of the present invention can let the users set time planning and the corresponding communication states in the mobile terminal according to their work or learning needs, in order to avoid disturbance of incoming calls and the SMS when they are unavailable, while to be able to communicate properly in their leisure time, thus it is particularly applicable to student crowds.(String), 技术领域 [0001] 控制 移动终端通信状态的方法及移动终端技术领域本发明涉及移动通信领域,尤其涉及一种控制移动终端通信状态的方法及移动终端。 相关技术背景 [0002] 在当今信息社会,信息和通信的作用越来越重要。 不同的用户对移动终端(如手机、小灵通(Personal Handy-phone System,PHS))的功能需求不同。 当业务繁忙或需要安静处理一些事务时,来电或短信肯定会影响用户的注意力。 例如,在数十名学生聚集在一起的教室中,上课时间移动通信终端的短信和MMS(Multimedia Messaging Service)通知消息会严重影响学生的课堂注意力和教师的教学过程。 此外,课堂内移动终端的交叉辐射会严重影响学生的身体健康。 发明内容 [0003] 本发明的目的在于提供一种控制移动终端通信状态的方法及移动终端,使得用户可以根据自己的工作或学习需要,在移动终端中设置时间规划和相应的通信状态,以便 避免来电、短信等不必要的打扰,同时保持闲暇时间的正常沟通。 [0004] 为实现上述目的,本发明提供了一种移动终端通信状态控制方法,包括: [0005]移动终端通过特定的设置界面接收并存储用户输入的计划时间段以及与计划时间段对应的通信状态; 和[0006] 移动终端检测当前时间是否在计划时间段内,若是,则检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,则调整当前通信状态 到计划时间段对应的通信状态。 [0007] 优选地,该方法还包括: [0008] 移动终端接收用户输入的认证信息,检测认证信息是否合法,若合法则进入具体设置界面。 [0009] 优选地,该方法还包括: [0010] 若移动终端检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长; 和[0011] 在duration中保持计划时间段对应的通信状态。 [0012] 本发明还提供了一种移动终端,包括: [0013] 设置模块,用于接收并存储用户通过特定设置界面输入的计划时间段和与计划时间段对应的通信状态;[0014] 处理模块,用于检测当前时间是否在计划时间段内,如果是,则检测当前通信状态与设置模块中存储的计划时间段对应的通信状态是否一致,如果不一致 ,输出信号给通信模块; 和[0015] 通讯模块,用于接收来自处理模块的信号,将当前的通讯状态调整为设置模块中存储的计划时间段对应的通讯状态。 [0016] 优选地,移动终端还包括鉴权模块。 [0017] 鉴权模块用于接收用户输入的鉴权信息,检测鉴权信息是否合法,若合法,则向设置模块输出信号。 [0018] 设置模块还用于接收鉴权模块的信号,进入特定的设置界面。 [0019] 优选地,所述移动终端还具有以下特征: [0020] 处理模块,还用于若检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长,并将计算出的时长输出给通信模块。 和[0021] 通信模块还用于接收时长,并在该时长内保持计划时间段对应的通信状态。 [0022] 与现有技术相比,本发明具有以下优点。 [0023] 用户可以根据自己的工作或学习需要,在自己的移动终端中设置时间规划和相应的通讯状态,从而在闲暇时间保持正常通讯的同时,避免来电和短信的不必要的打扰。 [0024] 本发明通过规划用户的作息时间,设置移动终端在不同时段的通信状态,在满足基本通信功能的基础上,降低移动通信终端的辐射对用户的危害。 而且,由于网络通信的减少,移动通信终端的待机时间势必会大大延长。 [0025] 本发明专为学生设计,具有广阔的市场前景,特别适合大中小学生使用。 附图说明 [0026] 图1是根据本发明一个实施例的移动终端的框图; [0027] 图2为本发明实施例的移动终端通信状态控制方法的流程图; 和 [0028] 图3为本发明移动终端通信状态控制方法的应用实例流程图。 本发明的优选实施例 [0029]下面结合附图对本发明技术方案的优选实施方式作进一步详细说明。 [0030] 图1是根据本发明实施例的移动终端的框图。 如图1所示,移动端 100 根据该实施例包括设置模块 110 , 处理模块 120 和通信模块 130 . [0031] 设置模块 110 用于通过特定的设置界面接收并存储用户输入的计划时间段以及与计划时间段对应的通信状态。 [0032] 具体地,在移动终端中增加时间计划和通信状态的设置界面,使得用户可以在设置界面中设置时间计划和相应的通信状态。 设置模块 110 接收用户输入的时间规划和相应的通信状态信息,并将设置结果存储到文件系统中。 [0033] 处理模块 120 用于检测当前时间是否在设置模块存储的计划时间段内 110 ,若是,则检测当前通信状态是否与设置模块中存储的计划时间段对应的通信状态一致 110 , 不一致则输出信号给通讯模块 130 . [0034] 通信模块 130 用于接收来自处理模块的信号 120 ,然后将当前的通信状态调整为设置模块中存储的计划时间段对应的通信状态 110 . [0035] 例如,假设移动终端当前处于正常通信状态,即通信模块 130 处于开启状态。 若用户设置了一个计划时间段,并将该计划时间段对应的通信状态设置为关闭状态,则当处理模块 120 通信模块检测到当前时间在用户设置的时间段内, 130 被关闭。 [0036] 因此,对于本实施例的移动终端,用户可以根据自己的工作或学习需要,在自己的移动终端中设置时间规划和相应的通讯状态,从而在保持正常工作的同时,避免来电和短信的不必要的打扰。 闲暇时的交流。 [0037] 优选地,本实施例的移动终端还可以包括鉴权模块 140 ,用于接收用户输入的认证信息,检测认证信息是否合法,如果合法则输出信号给设置模块 110 . 收到认证模块的信号后 140 , 设置模块 110 进入具体设置界面。 即通过认证(如输入用户名、密码等)的用户(如家长)可以访问规划设置页面,否则拒绝访问规划设置页面 界面。 [0038] 优选地,处理模块 120 还用于若检测到当前时间在计划时间段内,则计算当前时间到计划时间段结束时间的时长,将计算出的时长输出给通信模块 130 . 通信模块后 130 接收到时长信息,在时长内保持计划时间段对应的通信状态。 [0039] 例如,用户设置上午9:00-10:00关闭通讯,处理模块 120 早上9点检测到当前时间在计划时间段内,计算当前时间到计划时间段结束时间一小时的时长,然后通信模块 130 将保持关闭状态一小时,一小时后恢复正常通讯。 [0040] 图2是根据本发明实施例的控制移动终端通信状态的方法的流程图。 如图2所示,根据本实施例的方法包括以下步骤。 [0041] 在 S 11 ,移动终端接收用户输入的认证信息。 [0042] 例如,用户输入用户名、密码等。 [0043] 在 S 12 ,检测认证信息是否合法,如果合法,则进入规划的设置界面,步骤S 13 执行,否则拒绝进入规划的设置界面。 [0044] 在 S 13 移动终端通过计划设置界面接收用户输入的计划时间段和计划时间段对应的通信状态的计划信息,然后存储计划信息。 [0045] 假设用户输入的计划信息包含计划时间段,例如上午9:00至10:00,以及通信状态,例如封闭通信。 [0046] 在 S 14 ,移动终端检测当前时间是否在计划时间段内,若是,则执行步骤S 15 执行; 否则,步骤S 17 被执行。 [0047] 在 S 15 ,检测当前通信状态与存储的计划时间段对应的通信状态是否一致,若不一致,步骤S 16 执行; 否则,步骤S 17 被执行。 [0048] 在 S 16 ,将当前通信状态调整为规划时间段对应的通信状态。 [0049] 在 S 17 , 保持当前的通信状态。 [0050] 若当前时间为上午8:00,则保持正常通信状态; 如果当前时间是上午9:00,则关闭通信。 [0051] 优选地,在移动终端检测到当前时间在计划时间段内之后,该方法还包括以下步骤。 [0052] 在 S 18 ,计算当前时间到计划时间段结束时间的时长。 [0053] 例如,持续时间为上午9:00至上午10:00,即一小时。 [0054] 在 S 19 ,维持duration中计划时间段对应的通信状态。 [0055] 例如保持通信关闭状态一小时,一小时后恢复正常通信状态。 [0056] 下面描述根据本发明的控制移动终端通信状态的方法的应用示例。 [0057] 在本应用实例中,根据学生的特点,按学期、每天的上课时间等划分学生的上课时间和非上课时间。 例如,通过移动终端的界面设置以下项目。 [0058] 1、设置以下几个时间段。 [0059] a) 设置学期时间段。 [0060] 设置学生的上课时间段。 例如,某学生的上课时间设置如下: 姓名 开始 结尾 第一学期 2009年3月1日 2009年7月1日 第二学期 2009年9月1日 2010年1月20日 . . . . . . . . . [0061] 周六和周日为休息日,可单独标注。 [0062] b) 上课时间已定。 [0063] 比如某学校的上课时间是这样设置的: 上课时间 开始 结尾 早上第一节课  8:00  8:45 上午第二节课  9:00  9:45 上午第三节课 10:00 10:45 上午第四节课 11:00 11:45 下午第一节课 14:00 14:45 下午第二节课 15:00 15:45 下午第三节课 16:00 16:45 . . . . . . [0064] c) 设置休眠时间段。 [0065] 下午和晚上的睡眠时间段设置如下: 休眠时间段 开始 结尾 下午 13:00 14:00 夜晚 22:00 06:30 [0066] d) 设置特殊时间段。 [0067] 比如家里有急事,要求孩子随时接通。 例如: 特殊时期 开始 结尾 家里有急事 2009年1月1日 8:00 2009年1月1日 20:00 爷爷来了 2009年12月05日 8:00 2009年12月05日 20:00 . . . . . . . . . [0068] (2)设置通信状态,主要是设置移动通信终端在不同时间段的通信状态。 [0069]以上时间段主要包括上课时间、睡眠时间、特殊时间、其他时间。 通信状态的设置项包括正常通信和封闭通信。 关闭通信是指移动终端中的通信模块(射频模块)被关闭,移动终端既不能接收也不能发送消息。 [0070] 例如,学生的通信状态设置如下: 时间段 通讯状态设定 特殊时期 正常沟通 上课时间 封闭式沟通 睡觉时间 封闭式沟通 其他时间 正常沟通 [0071] 图3示出了根据本应用示例的控制移动终端通信状态的方法的流程图,包括以下步骤。 [0072] 在 S 201 ,移动终端开启。 [0073] 在 S 202 ,检测到当前时间处于上述设定的哪个计划时间段,例如学期时间段、每日上课时间段、特殊时间段或睡眠时间段。 [0074] 在 S 203 、判断当前通信状态与设定的计划通信状态是否一致,若不一致,则将当前通信状态调整为设定的计划通信状态; 否则,保持当前通信状态不变。 [0075] 例如,当前时间的通信模块处于打开或关闭状态。 [0076] 在 S 204 ,计算从当前时间到需要改变最近通信状态的时间点的时长。 [0077] 在 S 205 , 持续时间内保持当前通信状态; 持续时间后,步骤 S 202 被执行。 [0078] 在 S 206 ,如果用户关闭移动终端,则操作结束。 [0079] 本应用实例为普通移动通信终端增加了时间规划功能,即可以将学生的一天划分为不同的时间段,如上课时间段、睡眠时间段、特殊时间段等。 . 在上课时间段和睡眠时间段,通过关闭移动终端中的通讯模块,上课的学生不会受到来电、短信、彩信等铃声的打扰,保证了正常的教学 课堂秩序; 同时,由于通信模块的关闭,移动通信终端的辐射降为零。 在其他时间段,移动终端的通讯模块处于开启状态,以满足人们的通讯需求。 在特殊时间段,例如家中有紧急情况时,可以将通讯模块设置为一直处于开启状态,以保证特殊时间段与外界的方便通讯。 [0080] 如上所述,通过规划学生的时间,可以设置移动通信终端在不同时间段的通信状态,可以大大降低移动通信终端对用户的辐射。 由于网络流量的减少,必然会降低用电量,从而大大增加移动通信终端的待机时间。 [0081] 由于根据本发明的移动终端可以大大降低对学生、老师和学生在课堂上的辐射,老师和学生在课堂上不会受到来电、短信等的干扰,可以正常交流。 课后维护,一定会特别受到广大学生、老师和社区的喜爱。 [0082] 本发明不仅适用于学生,也适用于所有需要根据不同时间段设置相应通信状态的用户。 [0083]以上实施例仅是举例说明根据本发明的控制移动终端的通信状态的方法,不应理解为对本发明的限制。 根据本发明的技术方案及其优选实施例的说明,可以做出各种等同变化或替换,这些等同变化和替换均应包含在本发明的权利要求的保护范围之内。 工业实用性 [0084] 本发明的技术方案可以让用户根据自己的工作或学习需要在移动终端中设置时间计划和相应的通讯状态,从而避免在无法接听电话和短信时受到打扰,同时 能够在闲暇时间进行适当的交流,因此特别适用于学生人群。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.206 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.207 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101778171A(String), EP2519072A1(String), EP2519072A4(String), US20120309450A1(String), WO2011094996A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101778171A(String), EP2519072A1(String), EP2519072A4(String), US20120309450A1(String), WO2011094996A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101778171A(String), EP2519072A1(String), EP2519072A4(String), US20120309450A1(String), WO2011094996A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271641(Integer), CN101778171A(String), 1049457(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271641(Integer), EP2519072A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271641(Integer), EP2519072A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271641(Integer), US20120309450A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.541 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271641(Integer), WO2011094996A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.576 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.577 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101778171A(String), CN101778171A(String), 1279036800(Integer), 271641(Integer), 185926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.689 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185993(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 185993(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185993(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 185993(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.878 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.878 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:40.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185993(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10114522B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.517 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method of controlling display of display device by mobile terminal and mobile terminal for the same(String), 移动终端控制显示设备显示的方法及移动终端(String), US10114522B2(String), Disclosed is a method of controlling a screen display of an external display device by a mobile terminal, including when a connection between the mobile terminal and the external display device is performed, transmitting image data to the external display device and displaying an image displayed in the mobile terminal in the external display device, and when a selection command for one of objects included in the image data is input in the mobile terminal, moving a position of the image displayed in the external display device and then controlling such that the image is displayed together with an image of the object for the selection command.(String), 公开了一种通过移动终端控制外部显示设备的屏幕显示的方法,包括在移动终端与外部显示设备之间进行连接时,将图像数据发送到外部显示设备,并显示在外部显示设备中显示的图像。 移动终端在外部显示设备中,并且当在移动终端中输入图像数据中包括的对象之一的选择命令时,移动外部显示设备中显示的图像的位置,然后进行控制以显示图像 连同用于选择命令的对象的图像。(String), US13/872783(String), 1367164800(Integer), US10114522B2(String), 1540828800(Integer), 1540828800(Integer), 美国(String), 4(Integer), KR(String), 5(Integer), 30(Integer), CN101917673A | CN102238280A | CN102301738A | CN102447969A | EP2385689A1 | KR1020120015931A | US20030069923A1 | US20070211734A1 | US20090092185A1 | US20100299436A1 | US20100313143A1 | US20110075031A1 | US20110099512A1 | US20110216064A1 | US20110268218A1 | US20110283334A1 | US20120017236A1 | US20120019674A1 | US20120038541A1 | US20120042102A1 | US20120088447A1 | US20120088548A1 | US20120131458A1 | US20130040623A1 | US20130094423A1 | US20130103446A1 | US20130125018A1 | WO2010143843A2 | WO2012026750A2(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185994(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.700 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\18182216527f46c8b82b811173ccdcd5.png(String), 185994(Integer), 18182216527f46c8b82b811173ccdcd5.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.735 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of controlling display of display device by mobile terminal and mobile terminal for the same(String), 移动终端控制显示设备显示的方法及移动终端(String), US10114522B2(String), Disclosed is a method of controlling a screen display of an external display device by a mobile terminal, including when a connection between the mobile terminal and the external display device is performed, transmitting image data to the external display device and displaying an image displayed in the mobile terminal in the external display device, and when a selection command for one of objects included in the image data is input in the mobile terminal, moving a position of the image displayed in the external display device and then controlling such that the image is displayed together with an image of the object for the selection command.(String), 公开了一种通过移动终端控制外部显示设备的屏幕显示的方法,包括在移动终端与外部显示设备之间进行连接时,将图像数据发送到外部显示设备,并显示在外部显示设备中显示的图像。 移动终端在外部显示设备中,并且当在移动终端中输入图像数据中包括的对象之一的选择命令时,移动外部显示设备中显示的图像的位置,然后进行控制以显示图像 连同用于选择命令的对象的图像。(String), US13/872783(String), 1367164800(Integer), US10114522B2(String), 1540828800(Integer), 1540828800(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 5(Integer), 30(Integer), CN101917673A | CN102238280A | CN102301738A | CN102447969A | EP2385689A1 | KR1020120015931A | US20030069923A1 | US20070211734A1 | US20090092185A1 | US20100299436A1 | US20100313143A1 | US20110075031A1 | US20110099512A1 | US20110216064A1 | US20110268218A1 | US20110283334A1 | US20120017236A1 | US20120019674A1 | US20120038541A1 | US20120042102A1 | US20120088447A1 | US20120088548A1 | US20120131458A1 | US20130040623A1 | US20130094423A1 | US20130103446A1 | US20130125018A1 | WO2010143843A2 | WO2012026750A2(String), \20230420\18182216527f46c8b82b811173ccdcd5.png(String), 16(Integer), 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 1. A method of controlling a display of an external display device by a mobile terminal, the method comprising:transmitting, by the mobile terminal, when a connection with the external display device is performed, second content that is identical to first content displayed on the mobile terminal to the external display device, wherein the second content is displayed on the external display device, and wherein the second content occupies a portion of the external display such that the second content is mirrored based on a screen direction of the mobile terminal;receiving, by the mobile terminal, a touch input, through a touch screen of the mobile terminal, for selecting one object of a plurality of objects included in the first content displayed on the mobile terminal; anddetermining, by the mobile terminal, a screen direction of the mobile terminal;transmitting, by the mobile terminal, based on the determined screen direction being a vertical direction, information on third content corresponding to the selected object to be displayed in an empty space in order to fill the empty screen space not occupied by the second content on the external display device, to the external display device; andcontrolling, by the mobile terminal, the external display device to display the second content on a first area of the external display device and the third content corresponding to the selected object on a second area of the external display device.(String), 1.一种移动终端控制外接显示设备显示的方法,该方法包括:移动终端在与外部显示设备进行连接时,向外部显示设备发送与移动终端上显示的第一内容相同的第二内容,其中,第二内容显示在外部显示设备上,以及其中,第二内容占据外部显示器的一部分,使得第二内容基于移动终端的屏幕方向被镜像;移动终端通过移动终端的触摸屏接收触摸输入,用于选择移动终端显示的第一内容包括的多个对象中的一个对象;和移动终端确定移动终端的屏幕方向;移动终端基于确定的屏幕方向为竖直方向,发送选择的对象对应的第三内容的信息,在空白处显示,以填充第二内容未占用的空白屏幕空间外接显示设备,到外接显示设备;和移动终端控制外接显示设备在外接显示设备的第一区域显示第二内容,在外接显示设备的第二区域显示与选择的对象对应的第三内容。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 2. The method of claim 1, wherein receiving, by the mobile terminal, the selection of the one object comprises receiving an input for designating a display position of the third content on the external display device.(String), 2.如权利要求1所述的方法,其中由移动终端接收对一个对象的选择包括接收用于指定第三内容在外部显示设备上的显示位置的输入。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 3. The method of claim 2, wherein the input for designating the display position of the third content indicates a direction in which drag and drop according to a touch input is generated.(String), 3.如权利要求2所述的方法,其中用于指定第三内容的显示位置的输入指示产生根据触摸输入的拖放的方向。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 4. The method of claim 3, further comprising, when the input for designating the display position of the third content is made, transmitting a command for designating the display position of the third content to the external display device and displaying the third content together with the second content by moving a display position of the second content in the external display device.(String), 4.如权利要求3所述的方法,还包括,当进行了用于指定第三内容的显示位置的输入时,将用于指定第三内容的显示位置的命令发送到外部显示设备并且通过移动第二内容的显示位置来与第二内容一起显示第三内容外部显示设备中的内容。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 5. The method of claim 4, wherein the second content is moved to and displayed in a part of a screen in an opposite direction of the direction in which the drag and drop is generated, and the third content is displayed in a part of the screen in the direction in which the drag and drop is generated.(String), 5.如权利要求4所述的方法,其中将第二内容移动到与产生拖放方向相反的部分屏幕显示,将第三内容显示在产生拖放方向的部分屏幕。滴产生。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 6. The method of claim 1, wherein the information on the third content includes at least one of a content type of the third content and an address to receive the third content.(String), 6.如权利要求1所述的方法,其中第三内容的信息包括第三内容的内容类型和接收第三内容的地址中的至少一种。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 7. The method of claim 6, wherein the content type indicates one of web content, media content, and advertisement content according to a type of the third content.(String), 7.如权利要求6所述的方法,其中内容类型根据第三内容的类型指示网页内容、媒体内容和广告内容中的一种。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 8. The method of claim 1, further comprising performing a connection with the external display device based on a Wi-Fi Direct technique.(String), 8.如权利要求1所述的方法,还包括基于Wi-FiDirect技术与外部显示设备进行连接。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 9. The method of claim 1, wherein the second content is transmitted based on a Real Time Streaming Protocol (RTSP).(String), 9.如权利要求1所述的方法,其中第二内容基于实时流协议(RTSP)传输。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 10. The method of claim 1, wherein transmitting, by the mobile terminal, the information on the third content to the external display device comprises:configuring, when the one object is selected, a combined screen to display the second content and the third content together on the external display device; andtransmitting information on the combined screen to the external display device.(String), 10.如权利要求1所述的方法,其中移动终端向外接显示设备发送第三内容信息包括:在选择一个对象时,配置一个组合的屏幕以在外部显示设备上显示第二个内容和第三个内容;和将组合屏幕上的信息传输到外部显示设备。11、一种控制外接显示设备显示的移动终端包括:通信电路;触摸屏;和处理器配置为:在触摸屏上显示第一内容;通过通讯电路传送与第一内容相同的第二内容至外部显示装置,其中第二内容显示在外部显示装置上,且其中第二内容占据外部显示器的一部分,使得第二内容基于镜像在移动终端的屏幕方向上;通过触摸屏接收用于选择移动终端上显示的第一内容中包括的多个对象中的一个对象的触摸输入确定移动终端的屏幕方向;基于确定的屏幕方向为垂直方向,使用通信电路发送关于与选择的对象对应的第三内容的信息,以在空白空间中显示以填充未被第二内容占据的空白屏幕空间外部显示设备,到外部显示设备,以及控制外部设备在外部显示设备的第一区域上显示第二内容并且在外部显示设备的第二区域上显示与选择的对象对应的第三内容。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 11. A mobile terminal for controlling a display of an external display device comprising:a communication circuit;a touch screen; anda processor configured to:display first content on the touch screen;transmit second content identical to the first content to the external display device through the communication circuit, wherein the second content is displayed on the external display device, and wherein the second content occupies a portion of the external display such that the second content is mirrored based on a screen direction of the mobile terminal;receive, through the touch screen, a touch input for selecting one object of a plurality of objects included in the first content displayed on the mobile terminaldetermine a screen direction of the mobile terminal;transmit, using the communication circuit, based on the determined screen direction being a vertical direction, information on a third content corresponding to the selected object to be displayed in an empty space in order to fill the empty screen space not occupied by the second content on the external display device, to the external display device, andcontrol the external device to display the second content on a first area of the external display device and third content corresponding to the selected object on a second area of the external display device.(String), 12.如权利要求11所述的移动终端,其中通信电路提供显示网页的网页内容,并且提供媒体内容的数字生活网络联盟(DLNA)模块。(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 12. The mobile terminal of claim 11,wherein the communication circuit provides web content showing a web page, anda Digital Living Network Alliance (DLNA) module which provides media content.(String), 13.如权利要求11所述的移动终端,其中处理器还被配置为当通过触摸屏在外部显示设备上存在用于指定第三内容的显示位置的输入时,将用于指定第三内容的显示位置的命令发送到外部显示设备。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 13. The mobile terminal of claim 11, wherein the processor is further configured such that a command for designating a display position of the third content is transmitted to the external display device when there is an input for designating the display position of the third content on the external display device through the touch screen.(String), 14.如权利要求13所述的移动终端,其中用于指定第三内容的显示位置的输入指示通过触摸屏产生根据触摸输入的拖放的方向。(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 14. The mobile terminal of claim 13, wherein the input for designating the display position of the third content indicates a direction in which a drag and drop according to a touch input is generated through the touch screen.(String), 15.如权利要求13所述的移动终端,其中将第二内容移动到与产生拖放方向相反的部分屏幕显示,将第三内容显示在产生拖放方向的部分屏幕。滴产生。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 15. The mobile terminal of claim 13, wherein the second content is moved to and displayed in a part of a screen in an opposite direction of the direction in which the drag and drop is generated, and the third content is displayed in a part of the screen in the direction in which the drag and drop is generated.(String), 16.如权利要求11所述的移动终端,其中第三内容的信息包括第三内容的内容类型和接收第三内容的地址中的至少一种。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:41.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185994(Integer), 16. The mobile terminal of claim 11, wherein the information on the third content includes at least one of a content type of the third content and an address to receive the third content.(String), 1(Integer), 15(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185994(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to Korean Application Serial No. 10-2012-0079367, which was filed in the Korean Intellectual Property Office on Jul. 20, 2012, the contents of which are incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to an apparatus and a method for controlling a display in a mobile terminal, and more particularly, to an apparatus and a method for controlling a display in an external display device in a mobile terminal having a function of outputting an image to the external display device. [0004]2. Description of the Related Art [0005]Interest in a digital broadcasting service for allowing a user to watch a digital broadcast while moving has increased as digital broadcasting and mobile communication technologies have evolved. Concurrently, a paradigm of the broadcasting service has been changed from the broadcasting service having a passive concept in which the user only passively watches the broadcast to the broadcasting service having an active concept in which the user identifies information on a cost of a product shown in the broadcast and purchases the product while directly watching the broadcast. [0006]Interest in a Digital Multimedia Broadcasting (DMB) service using a mobile terminal has also increased. The DMB service overcomes spatial and temporal limitations in watching the broadcast, but is not suitable for the broadcast simultaneously watched by several people due to screen size limitations. Accordingly, there have been increased releases of mobile terminals having a function of outputting a signal to a large sized display device, such as a TV. [0007]A current mobile terminal having a Television (TV) out function can output a video such as a broadcast displayed through a screen of the mobile terminal to an external display device. Accordingly, the user can watch the broadcast through a larger sized screen by outputting image data downloaded from a web server or photographed by a camera to the external display device. Examples of advanced mobile terminals having the TV out function include a Wi-Fi Display (WFD) and an airplay mirroring. [0008]For example, WFD refers to a technology in which a small sized screen of a mobile terminal 100 interworks with an external display device such as a TV 110 and then the same screen as that of the mobile terminal 100 is wirelessly displayed in the TV as illustrated in FIG. 1. When a user input is performed through the mobile terminal screen 100, a current screen is switched to a screen corresponding to the user input. The screen of the TV 110 is switched to the same screen as that of the mobile terminal 100. [0009]However, the same image as the image on the mobile terminal screen is located in the center of the TV screen. Accordingly, while the same image as the image on the mobile terminal screen is displayed on an entire TV screen when a screen direction of the mobile terminal is horizontal, the remaining parts except for the center of the TV screen remain as empty spaces, as illustrated in FIG. 1, when the screen direction is vertical. That is, due to a difference between a screen size of the mobile terminal and a screen size of the TV, the empty spaces are generated on the TV screen as illustrated in FIG. 1. [0010]Accordingly, there is a need in the art for the user to be able to control a screen display of the external display device in displaying an image on the mobile terminal screen on the external display device, to enable the user to receive a more vivid and efficient image in comparison with using the mobile terminal. SUMMARY OF THE INVENTION [0011]Accordingly, the present invention provides an apparatus and a method for controlling the screen display of the external display device by the mobile terminal. [0012]The present invention also provides an apparatus and a method for providing an efficient screen display of the external display device. [0013]In accordance with an aspect of the present invention, a method of controlling a display of a display device by a mobile terminal includes, when a connection with the display device is performed, transmitting second content equal to first content displayed on the mobile terminal to the display device, receiving a selection of one object of objects included in the first content displayed on the mobile terminal, and transmitting information on third content corresponding to a selected object to the display device so that the second content and the third content corresponding to the selected object are displayed together in the display device. [0014]In accordance with another aspect of the present invention, a mobile terminal for controlling a display of a display device includes a connector for performing a connection with the display device, a touch screen for displaying a first content and outputting a selection signal according to a selection of one object from objects included in the first content, and a controller for controlling such that second content equal to the first content is transmitted to the display device through the connector, and controlling such that when the selection signal according to the selection of the one object is transferred from the touch screen, information on a third content corresponding to the selected object is transmitted to the display device so that the second content and third content corresponding to the selected object are displayed together on the display device. BRIEF DESCRIPTION OF THE DRAWINGS [0015]The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0016]FIG. 1 illustrates a TV screen when a screen of a conventional mobile terminal is mirrored; [0017]FIG. 2 illustrates an internal block diagram of a first device and a second device according to an embodiment of the present invention; [0018]FIG. 3 illustrates an operation between the first device and the second device to control a screen display of the second device according to a first embodiment of the present invention; [0019]FIG. 4 illustrates an example for describing a method of the operation of FIG. 3; [0020]FIG. 5 illustrates an operation between the first device and the second device to control the screen display of the second device according to a second embodiment of the present invention; [0021]FIG. 6 illustrates the operation between the first device and the second device to control the screen display of the second device according to a third embodiment of the present invention; [0022]FIG. 7 illustrates an example for describing a method of the operation of FIG. 6; [0023]FIG. 8 illustrates an operation between the first device and the second device to control the screen display of the second device according to a fourth embodiment of the present invention; and [0024]FIG. 9 illustrates an example for describing a method of the operation of FIG. 8. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0025]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, the same elements will be designated by the same reference numerals although they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted for the sake of clarity and conciseness. [0026]The present invention provides a method of controlling a screen display of an external display device in a mobile terminal. To this end, the present invention includes a process of controlling such that a mobile terminal is connected with a neighboring external display device, image data is transmitted to the external display device to display an image displayed on a screen of the mobile terminal on the external display device, and a position of the image displayed on the external display device is moved and the image is displayed with an object image for the selection command when a selection command for one of objects included in the image data is input on the mobile terminal. Accordingly, it is possible to efficiently control an output screen of the external display device. [0027]FIG. 2 illustrates an internal block diagram of a first device and a second device according to an embodiment of the present invention. In FIG. 2, a first device 200 is the mobile terminal supporting an image viewing function such as a smart phone, a mobile phone, or a tablet PC, and a second device 230 is the external display device, such as a TV, having a larger sized screen than a screen of the first device 200. [0028]The first device 200 includes a display unit 205, a web browser module 210, a Digital Living Network Alliance (DLNA) module 215, a Wi-Fi Display (WFD) connector 220, and a controller 225. [0029]The display unit 205 may be implemented by a Liquid Crystal Display (LCD) panel, and operates as an input means when the LCD panel is implemented in a touch screen type. The display unit 205 serves to display information input by or provided to the user, as well as various types of menus of the mobile terminal. When the display unit 205 is implemented in the touch screen type, an input signal is output to the controller 225 if there is a touch input from the user. The controller 225 identifies an input type by means of the signal input through the touch screen, and determines, for example, a hold, a drag, and a drop. [0030]When an Internet browser is operated according to a request of the user, the web browser module 210 accesses Uniform Resource Locator (URL) information input to an Internet address window through a web server to generate a web page according to a received packet. The web browser module 210 provides web content showing the web page to the controller 225. [0031]The DLNA module 215 provides media content to the controller 225 in order to transmit the media content, such as a video, to the second device 230 in a streaming type. The DLNA module 215 shares the media content with the second device 230, to allow the user to continuously watch the media content stored in the first device 200 in the second device 230. [0032]The WFD connector 220 searches for the neighboring second device 230 which is available for a Wi-Fi Direct service. When the second device 230 is found, the WFD connector 220 serves to connect the first device 200 with the second device 230 through a process of exchanging a device capability with the second device 230. [0033]The controller 225 controls a general operation within the first device 200. Specifically, the controller 225 controls such that contents such as web content from the web browser module 210 or media content from the DLNA module 215 are transmitted to the second device 230 through the WFD connector 220 based on a Real Time Streaming Protocol (hereinafter RTSP). [0034]The controller 225 determines an input signal form from the user through the display unit 205 to control the first device 200 in accordance with the determination. For example, when the user inputs a selection command for an object included in an image displayed on the display unit 205, the controller 225 controls the web browser module 210 or the DLNA module 215 so that detailed data on the selected object is displayed. In addition, the controller 225 transmits currently displayed content to the second device 230, and a transmission type of the content follows a streaming type, so that a detailed description thereof will be omitted. Actual content may be transmitted according to the streaming type, or alternatively, only a content address to receive the content may be transmitted and then the second device 230 may access the content address to display the same content. [0035]After the same content as the currently displayed content is transmitted to be displayed on the second device 230 in the streaming type, if a selection command for one of the objects included in the content is input, detailed data on the selected object is transmitted to the second device 230. The detailed data on the selected object is inserted into a parameter based on an RTSP and then transmitted. For example, the detailed data on the selected object includes actual content data, an address to receive the content data, a display position, and a content type. [0036]When the user touches a particular content or a web page among lists found through the web browser with his/her finger and then performs a drag and drop leftwards, the first device 200 transmits to the second device 230 a signal for instructing to prepare such that the particular content or the web page is displayed in a left side of the screen of the second device 230. In response to the signal, content displayed in a center of the screen moves in order to display the particular content or the web page in the left side of the screen of the second device 230. [0037]The operation performed in the second device 230 will be described below in detail. [0038]The second device 230 includes a display unit 235, a WFD connector 240, a content type processor 245, a content position processor 250, and a controller 255. [0039]The controller 255 receives the same content as the content displayed on the first device 200 in the streaming type and controls such that the content is displayed on the display unit 235. When a command for designating a display position of the selected object based on the RTSP, that is, the selected content is received through the WFD connector 240, the controller 255 moves the content on a current screen to secure a screen space where the selected content is rendered, in response to the command. When the screen space is secured, the controller 255 controls such that selected content is displayed on the display unit 235 with the previous content. [0040]Specifically, the controller 255 divides the screen into two spaces to simultaneously display the current content and the newly selected content, and controls such that the current content and the newly selected content are disposed in the divided screen spaces, respectively. The current content which had been displayed in the center is disposed in the screen space corresponding to an opposite side of the display position of the selected content among the divided screen spaces. [0041]A size of each of the divided screen spaces can be variously set. For example, the screen may be divided to maintain a display magnification of the current content which had displayed in the center of the screen, and in this case, the newly selected content is displayed in the remaining screen space other than the screen space displaying the current content. In order to display the current content and the newly selected content with the same size, the screen may be divided into screen spaces having the same size. A method of dividing the screen for displaying the content is not limited thereto. [0042]Accordingly, the display unit 235 may display an image changed according to an object selection in the first device 200 as well as display the same image as the image displayed through the display unit 205 of the first device 200. [0043]The content type processor 245 determines a type of the content received from the first device 200 and provides the content to the controller 255. The content type refers to a type of contents such as web content and media content, and for example, the web content may be set to “web”, the media content may be set to a “video”, and an advertisement may be set to an “ads video”. [0044]When a content address is included in the detailed data on the selected object, the content position processor 250 accesses the web server corresponding to the content address, receives content corresponding to the selected object, and provides the content to the controller 255. [0045]An operation between the first device and the second device to control a screen display of the second device according to a first embodiment of the present invention will now be described with reference to FIG. 3. In FIG. 3, the first device 200 is the mobile terminal, and the second device 230 is a TV. [0046]Referring to FIG. 3, the mobile terminal 200 performs a device discovery to find a neighboring external display device supporting Wi-Fi Direct in step 300. When the TV 230 is found as an example of the external display device, the mobile terminal 200 sets a connection with the TV 230 in step 305, and exchanges a capability and performs a negotiation in step 310. The mobile terminal 200 sets an RTSP connection to transmit a command in step 315, and then directly transmits content displayed on a screen of the mobile terminal 200 to the TV 230 through an RTSP play command in step 320. [0047]When a response is received from the TV 230 in step 325, the mobile terminal 200 starts an Audio/Video (AV) streaming for a mirroring in step 330. Accordingly, the content is transmitted to the TV 230 through the streaming type. Since processes of connecting the mobile terminal 200 and the TV 230 in steps 300 to 330 are performed based on a general Wi-Fi Direct technique, a detailed description of connection processes according to the Wi-Fi Direct technique will not be made in the present invention. [0048]When the web browser is started in the mobile terminal 200 as shown in step 335, the user selects one from a search list in step 340. When the web browser is started, web content 440 is displayed in the mobile terminal 200 and the same web content 405 is displayed in the TV 230 as the web content 400 is provided to the TV 230 through the streaming type as illustrated in FIG. 4. [0049]When a command for designating a display position on the TV 230 is input when one object included in the content 400 is selected by the user, the mobile terminal 200 transmits to the TV 230 the command for designating the display position on the TV 230. For example, when the user performs a drag and drop in a right direction 410 when the user touches one object included in the content 400 with his/her finger, the mobile terminal 200 determines an input signal according to the drag and drop. Accordingly, the mobile terminal 200 transmits an RTSP setting parameter including direction information indicating the direction in which the drag and drop is performed to the TV 230 in step 345. [0050]When the RTSP setting parameter is received, the TV 230 moves a mirrored screen displayed in a center in step 350, and then transmits a response in step 355. To this end, the TV 230 analyzes direction information included in the RTSP setting parameter, and then moves the mirrored screen leftwards to display the content for the selected object in a right side when the drag and drop direction is a right direction. [0051]The mobile terminal 200 determines that the screen space is secured in the TV 230 when receiving the response, and thus transmits content information corresponding to the selected object to the TV 230 by using the RTSP setting parameter in step 360. [0052]For example, in FIG. 4, the TV 230 receives a content type set as the “web” and content information including a content address to receive the selected content such as http://xyz.com/news/20111022/headline.html. In response to the reception, the TV 230 operates the browser in step 365, and then accesses a web server 260 by using the content address to receive the content for the selected object in step 370. Accordingly, the TV 230 moves the mirrored screen 405, which had been displayed in the center, in the left direction opposite to the direction of the drag and drop of the user, and then displays the mirrored screen 405 in a left part 420 and the content for the selected object in a right part 415. Alternatively, an actual content instead of the content address may be transmitted as the content information in the streaming type. [0053]FIG. 5 illustrates an example in which the mobile terminal 200 combines screens and transmits the combined screen according to a second embodiment of the present invention. Since steps 500 to 540 of FIG. 5 are the same as steps 300 to 340 of FIG. 3, a detailed description thereof will be omitted. However, when the content for the selected object is operated in step 545, the mobile terminal 200 directly receives the content for the selected object from the web server 260 in step 550, configures the screen generated by combining the provided content and previous content in step 555, and directly transmits information on the combined screen to the TV 230 in step 560 in the second embodiment of the present invention. [0054]FIG. 6 illustrates an example of an operation between the first device and the second device to control a screen display of the second device according to a third embodiment of the present invention. Since operations performed in steps 600 to 630 of FIG. 6 are the same as the operations performed in steps 300 to 330 of FIG. 3, a detailed description thereof will be omitted. However, in FIG. 6, when a content application is executed in step 635, the mobile terminal 200 displays a content list screen 700 as illustrated in FIG. 7. When a drag and drop 710 is performed by the user when one content is selected, a content list 705 displayed on the TV 230 moves to a right part 720, and the selected content is displayed in a left part 715. [0055]An RTSP setting parameter transmitted in step 660 contains content information that includes a content type set as a “video” indicating that the content is media content and, for example, a content address set as “rtp://192.168.1.32/dlna_contents/thumnail.avi” When the RTST setting parameter is received, the TV 230 operates a player to execute the selected content in step 665, and accesses the web server 260 by using the content address to receive the content from the web server 260 in step 670. Accordingly, the content list is displayed in the right screen part 720 of the TV 230, and simultaneously, the content reproduced through the player is output in the left screen part 715. [0056]FIG. 8 illustrates an operation between the first device and the second device to control a screen display of the second device according to a fourth embodiment of the present invention. Since operations of steps 800 to 830 of FIG. 8 are the same as the operations of steps 300 to 330 of FIG. 3, a detailed description thereof will be omitted. However, in FIG. 8, the mobile terminal 200 determines a display direction of a current screen in step 835. When the screen direction is a horizontal direction, there is no empty space on the screen of the TV 230. When the screen direction is a vertical direction, there is an empty space in both sides of a center on the screen. When the current screen direction is determined as the vertical direction, the mobile terminal 200 transmits the RTSP setting parameter containing information on the content to be displayed in the empty space in order to fill the empty space in step 840. Then, the TV 230 operates the player in step 845, and receives an advertisement to be displayed in the empty space from the mobile terminal 200 in step 850. Accordingly, the TV 230 can reproduce the advertisement through the player, so that the advertisement such as a video can be output. [0057]Referring to FIG. 9, a mirrored screen of the TV 230 identical to a screen 900 of the mobile terminal 200 is located in a center part 905 of the TV 230. In this case, empty spaces are generated in left and right parts of the remaining screen except for the center part 905 of the TV 230. FIG. 9 illustrates an example where advertisement screens 910 and 915 are displayed together in both sides of the center of the mirrored screen 905. In this case, the content information contained in the RTSP setting parameter contains a content type as an “ads video” indicating that the content is an advertisement. When the mobile terminal 200 does not directly provide the advertisement, the content information may contain a content address to receive the advertisement. [0058]As described above, according to the present invention, the user can view an image on the mobile terminal screen 200 through an enlarged screen by mirroring the image on the mobile terminal screen 200 to the TV 230, and can also view an image for object selection on the mobile terminal screen 200 together with a previous image through the TV 230. [0059]According to the present invention, there is an advantage in that the user receives a more vivid and efficient image in comparison with using the mobile terminal since the user can control a screen display of an external display device. There is an advantage in that a dual screen is used according to characteristics of the device receiving a mirrored image, for example, a ratio of width to height and a web screen preview and a content preview are possible through a large sized screen of the external display device while maintaining the mobile terminal screen. [0060]Moreover, there is an advantage of using the external display device as a new business model by showing an advertisement in an empty space of the device screen. For example, it is possible to ask an advertiser for advertisement profits by counting the number of times of advertisement reproductions and maximize an advertisement effect by using the advertisement as the purpose of advertising the mobile terminal product. [0061]While the present invention has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details is made therein without departing from the spirit and scope of the present invention as defined by the appended claims. Therefore, several modifications are possible without departing from the gist of the present invention as defined by the appended claims. It should be understood that the modifications remain within the technical ideas and overviews of the invention.(String), 优先 [0001] 本申请根据 35 U.S.C. 2012 年 7 月 20 日向韩国知识产权局提交的韩国申请序列号 10-2012-0079367 的第 119(a) 条,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及用于控制移动终端中的显示的设备和方法,更具体地,涉及用于控制具有输出图像功能的移动终端中的外部显示设备中的显示的设备和方法 到外部显示设备。 [0004] 2.相关技术的描述 [0005] 随着数字广播和移动通信技术的发展,对允许用户在移动时观看数字广播的数字广播服务的兴趣增加了。 同时,广播服务的范式已经从具有被动概念的广播服务(其中用户仅被动地观看广播)改变为具有主动概念的广播服务,其中用户识别关于图1所示的产品的成本信息。 在直接观看广播的同时购买产品。 [0006] 对使用移动终端的数字多媒体广播(DMB)服务的兴趣也增加了。 DMB业务克服了收看节目的空间和时间限制,但由于屏幕尺寸的限制,不适合多人同时收看的节目。 因此,具有向TV等大型显示装置输出信号的功能的移动终端的发布增加。 [0007] 当前具有电视(TV)输出功能的移动终端可以将通过移动终端的屏幕显示的诸如广播的视频输出到外部显示设备。 因此,用户可以通过将从网络服务器下载的或由照相机拍摄的图像数据输出到外部显示设备来通过更大尺寸的屏幕观看广播。 具有电视输出功能的高级移动终端的示例包括 Wi-Fi 显示器 (WFD) 和播放镜像。 [0008] 例如,WFD 是指将移动终端的小尺寸屏幕 100 与电视等外部显示设备互通 110 然后和手机端同屏 100 如图 1 所示,在电视中无线显示。当通过移动终端屏幕进行用户输入时 100 ,将当前画面切换到与用户输入对应的画面。 电视机的屏幕 110 切换到与移动端同屏 100 . [0009] 但是,与移动终端屏幕上的图像相同的图像位于电视屏幕的中央。 因此,当移动终端的屏幕方向为水平时,虽然与移动终端屏幕上的图像相同的图像显示在整个电视屏幕上,但除了电视屏幕的中心之外的其余部分保持为空白区域,如图所示 在图1中,屏幕方向为垂直时。 也就是说,由于移动终端的屏幕尺寸和电视的屏幕尺寸不同,在电视屏幕上会产生如图1所示的空白区域。 [0010] 因此,本领域需要用户在外接显示设备上显示移动终端屏幕上的图像时能够控制外接显示设备的屏幕显示,以使用户接收到更生动、更生动的画面。 与使用移动终端相比,图像更高效。 发明内容 [0011] 因此,本发明提供了一种用于通过移动终端控制外部显示设备的屏幕显示的装置和方法。 [0012] 本发明还提供一种用于提供外部显示设备的有效屏幕显示的设备和方法。 [0013]根据本发明的一个方面,一种由移动终端控制显示装置的显示的方法包括:当执行与显示装置的连接时,将与显示在移动终端上的第一内容相同的第二内容发送到移动终端。 显示装置, 接收对移动终端上显示的第一内容中包含的对象中的一个对象的选择, 将与选择的对象对应的第三内容的信息发送到显示装置, 使得第二内容和与选择的对象对应的第三内容 对象一起显示在显示设备中。 [0014] 根据本发明的另一方面,一种用于控制显示装置的显示的移动终端包括用于执行与显示装置的连接的连接器、用于显示第一内容并根据选择输出选择信号的触摸屏 of one object from objects included in the first content, and a controller for controlling such that second content equal to the first content is transmitted to the display device through the connector, and controlling such that when the selection signal according to the selection of the one 从触摸屏传送对象,将与选择的对象对应的第三内容的信息传输到显示设备,从而将第二内容和与选择的对象对应的第三内容一起显示在显示设备上。 附图的简要说明 [0015] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0016] 图1为现有移动终端镜像时的电视画面。 [0017] 图2为本发明实施例的第一设备和第二设备的内部框图。 [0018] 图3是说明根据本发明第一实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作的示意图。 [0019] 图4是说明图3的动作方法的例子。 [0020] 图5是根据本发明第二实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作示意图。 [0021] 图6是根据本发明第三实施例的第一设备与第二设备之间控制第二设备的屏幕显示的操作示意图。 [0022] 图7是说明图6的动作方法的例子。 [0023] 图8是根据本发明第四实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作示意图。 和 [0024] 图9示出了用于描述图8的操作方法的示例。 本发明实施方案的详细说明 [0025] 在下文中,将参照附图描述本发明的实施例。 在以下描述中,相同的元件将由相同的附图标记表示,尽管它们在不同的附图中示出。 在本发明的以下描述中,为了清楚和简洁起见,将省略对包含在本文中的已知功能和配置的详细描述。 [0026]本发明提供一种在移动终端中控制外部显示设备的屏幕显示的方法。 为此,本发明包括控制使得移动终端与相邻的外部显示设备连接,图像数据被发送到外部显示设备以在外部显示在移动终端的屏幕上显示的图像的过程。 当在移动终端上输入针对图像数据中包括的对象之一的选择命令时,移动显示在外部显示设备上的图像的位置,并且将图像与用于选择命令的对象图像一起显示。 因此,可以有效地控制外部显示装置的输出画面。 [0027] 图2示出了根据本发明实施例的第一设备和第二设备的内部框图。 在图 2 中,第一个设备 200 是智能手机、手机、平板电脑等支持图像查看功能的移动终端,以及第二设备 230 是具有比第一设备的屏幕更大的屏幕的外部显示设备,例如电视 200 . [0028] 第一台设备 200 包括一个显示单元 205 , 一个网页浏览器模块 210 , 数字生活网络联盟 (DLNA) 模块 215 , 一个 Wi-Fi 显示 (WFD) 连接器 220 , 和一个控制器 225 . [0029] 显示单元 205 可以由液晶显示器(LCD)面板实现,并且当LCD面板以触摸屏类型实现时用作输入装置。 显示单元 205 用于显示用户输入或提供给用户的信息,以及移动终端的各类菜单。 当显示单元 205 在触摸屏类型中实现,输入信号输出到控制器 225 如果有来自用户的触摸输入。 控制器 225 通过触摸屏输入的信号来识别输入类型,并确定例如保持、拖动和放下。 [0030] 当根据用户的请求操作互联网浏览器时,网络浏览器模块 210 通过网络服务器访问输入到互联网地址窗口的统一资源定位符(URL)信息,以根据接收到的数据包生成网页。 网络浏览器模块 210 向控制器提供显示网页的网页内容 225 . [0031] DLNA 模块 215 向控制器提供媒体内容 225 为了将媒体内容(例如视频)传输到第二设备 230 在流式传输。 DLNA 模块 215 与第二个设备共享媒体内容 230 , 让用户可以持续观看存储在第一设备中的媒体内容 200 在第二个设备中 230 . [0032] WFD 连接器 220 搜索相邻的第二个设备 230 可用于 Wi-Fi Direct 服务。 当第二台设备 230 找到,WFD连接器 220 用于连接第一个设备 200 使用第二个设备 230 通过与第二设备交换设备能力的过程 230 . [0033] 控制器 225 控制第一设备内的一般操作 200 . 具体来说,控制器 225 控件使得来自 Web 浏览器模块的内容(例如 Web 内容) 210 或来自 DLNA 模块的媒体内容 215 被传送到第二个设备 230 通过 WFD 连接器 220 基于实时流协议(以下简称 RTSP)。 [0034] 控制器 225 通过显示单元确定来自用户的输入信号形式 205 控制第一个设备 200 按照决定。 例如,当用户输入对包括在显示单元上显示的图像中的对象的选择命令时 205 , 控制器 225 控制网络浏览器模块 210 或 DLNA 模块 215以便显示所选对象的详细数据。 此外,控制器 225 将当前显示的内容传输到第二个设备 230 ,并且内容的传输类型遵循流式传输类型,因此将省略其详细描述。 可以根据流类型传输实际内容,或者也可以只传输接收内容的内容地址,然后第二设备 230 可以访问内容地址以显示相同的内容。 [0035] 在传输与当前显示内容相同的内容后显示在第二设备上 230 在流式传输类型中,如果输入内容中包括的对象之一的选择命令,则将有关所选对象的详细数据发送到第二设备 230 . 将所选对象的详细数据插入到基于 RTSP 的参数中,然后传输。 例如,所选对象的详细数据包括实际内容数据、接收内容数据的地址、显示位置和内容类型。 [0036] 当用户用他/她的手指触摸通过网络浏览器找到的列表中的特定内容或网页然后执行向左拖放时,第一设备 200 传输到第二个设备 230 用于指示准备使得特定内容或网页显示在第二设备的屏幕左侧的信号 230 . 响应于该信号,显示在屏幕中央的内容移动以便在第二设备的屏幕左侧显示特定内容或网页 230 . [0037] 在第二个设备中执行的操作 230 下面将详细介绍。 [0038] 第二台设备 230 包括一个显示单元 235 , WFD 连接器 240 , 内容类型处理器 245 , 内容位置处理器 250 , 和一个控制器 255 . [0039] 控制器 255 接收与第一台设备上显示的内容相同的内容 200 在流类型和控制中,使得内容显示在显示单元上 235 . 当通过 WFD 连接器接收到基于 RTSP 指定所选对象的显示位置的命令时,即所选内容 240 , 控制器 255 响应命令,移动当前屏幕上的内容以确保呈现所选内容的屏幕空间。 当屏幕空间得到保证时,控制器 255 控件使得所选内容显示在显示单元上 235 与之前的内容。 [0040] 具体来说,控制器 255 将屏幕划分为两个空间同时显示当前内容和新选择的内容,并控制使得当前内容和新选择的内容分别布置在划分的屏幕空间中。 已经在中心显示的当前内容被布置在划分的屏幕空间中与选择的内容的显示位置相对的一侧对应的屏幕空间中。 [0041] 可以不同地设置每个划分的屏幕空间的大小。 例如,可以划分屏幕以保持当前显示在屏幕中央的内容的显示放大率,在这种情况下,新选择的内容显示在显示该屏幕空间之外的剩余屏幕空间中。 当前内容。 为了以相同大小显示当前内容和新选择的内容,可以将屏幕划分为具有相同大小的屏幕空间。 划分用于显示内容的屏幕的方法不限于此。 [0042] 因此,显示单元 235 可以显示根据第一设备中的对象选择而改变的图像 200 以及显示与通过显示单元显示的图像相同的图像 205 第一台设备 200 . [0043] 内容类型处理器 245 确定从第一设备接收的内容的类型 200并将内容提供给控制器 255 . 内容类型是指网页内容、媒体内容等内容的类型,例如,网页内容可以设置为“web”,媒体内容可以设置为“视频”,还可以设置广告 到“广告视频”。 [0044] 当内容地址包含在所选对象的详细数据中时,内容位置处理器 250 访问内容地址对应的web服务器,接收选择的对象对应的内容,并将内容提供给控制器 255 . [0045] 现在将参照图3描述根据本发明第一实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作。在图3中,第一设备 200 是移动终端,第二个设备 230 是电视。 [0046] 参见图3,移动终端 200 执行设备发现以查找支持 Wi-Fi Direct 的相邻外部显示设备 300 . 当电视 230 发现作为外部显示设备的示例,移动终端 200 设置与电视的连接 230 在一步 305 , 并交换能力并逐步执行协商 310 . 移动终端 200 设置 RTSP 连接以在步骤中传输命令 315 ,然后直接传输显示在移动终端屏幕上的内容 200 到电视 230 通过 RTSP 播放命令在步骤 320 . [0047] 当收到来自电视的响应时 230 在一步 325 , 移动端 200 启动音频/视频 (AV) 流以进行镜像 330 . 因此,内容被传送到电视 230 通过流式传输。 由于连接移动终端的过程 200 和电视 230 逐步 300 至 330 由于基于一般Wi-Fi Direct技术进行的连接过程,本发明将不详细描述根据Wi-Fi Direct技术的连接过程。 [0048] 在移动终端中启动网络浏览器时 200 如步骤所示 335 ,用户在步骤中从搜索列表中选择一个 340 . 当网络浏览器启动时,网页内容 440 显示在移动端 200 和相同的网页内容 405 显示在电视上 230 作为网页内容 400 提供给电视 230 通过流式传输,如图 4 所示。 [0049] 指定电视显示位置的命令时 230 当内容中包含一个对象时输入 400 由用户选择,移动端 200 传送到电视 230 指定电视显示位置的命令 230 . 例如,当用户在正确的方向上执行拖放操作时 410 当用户触摸内容中包含的一个对象时 400 用他/她的手指,移动终端 200 根据拖放确定输入信号。 因此,移动终端 200 将包括指示执行拖放方向的方向信息的RTSP设置参数发送到TV 230 在一步 345 . [0050] 当接收到 RTSP 设置参数时,电视 230 以步进方式移动显示在中心的镜像屏幕 350 ,然后在步骤中发送响应 355 . 为此,电视 230 分析RTSP设置参数中包含的方向信息,然后在拖放方向为右方向时将镜像屏幕向左移动以在右侧显示所选对象的内容。 [0051] 移动终端 200 确定电视中的屏幕空间是安全的 230 当接收到响应时,将与所选对象对应的内容信息发送到电视 230 通过使用步骤中的 RTSP 设置参数 360 . [0052] 例如,在图 4 中,电视230 接收设置为“web”的内容类型和包括接收所选内容的内容地址的内容信息,例如http://xyz.com/news/20111022/headline.html。 响应接收,电视 230 一步一步操作浏览器 365 ,然后访问 Web 服务器 260 通过使用内容地址接收步骤中所选对象的内容 370 . 因此,电视 230 移动镜像屏幕 405 ,一直显示在中间,向左方向与用户拖拽的方向相反,然后显示镜像屏幕 405 在左侧 420 以及右侧部分中所选对象的内容 415 . 备选地,可以将实际内容而不是内容地址作为流式传输类型的内容信息来发送。 [0053] 图 5 说明了一个示例,其中移动终端 200 根据本发明的第二实施例,组合屏幕并传输组合屏幕。 由于步骤 500 至 540 图5的步骤相同 300 至 340 在图3中,将省略其详细描述。 但是,当在步骤中操作所选对象的内容时 545 , 移动端 200 直接从 Web 服务器接收所选对象的内容 260 在一步 550 , 配置通过在步骤中结合提供的内容和以前的内容生成的屏幕 555 ,并直接将组合屏幕上的信息传输到电视上 230 在一步 560 在本发明的第二实施例中。 [0054] 图6示出了根据本发明第三实施例的在第一设备和第二设备之间控制第二设备的屏幕显示的操作的示例。 由于操作是分步执行的 600 至 630 图 6 的操作与步骤中执行的操作相同 300 至 330 在图3中,将省略其详细描述。 然而,在图 6 中,当在步骤 635 , 移动端 200 显示内容列表屏幕 700 如图 7 所示。当拖放 710 由用户在选择一个内容时执行,内容列表 705 显示在电视上 230 向右移动 720 , 选中的内容显示在左侧 715 . [0055] 分步传送的 RTSP 设置参数 660 包含内容信息,该内容信息包括设置为“视频”的内容类型,指示该内容是媒体内容,例如,设置为“rtp://192.168.1.32/dlna_contents/thumnail.avi”的内容地址当RTST设置时 接收到参数,电视 230 操作播放器执行步骤中选择的内容 665 , 并访问网络服务器 260 通过使用内容地址从 Web 服务器接收内容 260 在一步 670 . 因此,内容列表显示在右侧屏幕部分 720 电视的 230 ,同时通过播放器再现的内容在左画面部分输出 715 . [0056] 图8示出了根据本发明第四实施例的第一设备和第二设备之间控制第二设备的屏幕显示的操作。 由于步骤的操作 800 至 830 图8的操作与步骤的操作相同 300 至 330 在图3中,将省略其详细描述。 然而,在图 8 中,移动终端 200 在步骤中确定当前画面的显示方向 835 . 当屏幕方向为水平方向时,电视屏幕上没有空白区域 230 . 当屏幕方向为垂直方向时,屏幕中心的两侧有空白区域。 当当前屏幕方向确定为垂直方向时,移动终端 200 传送包含有关要在空白处显示的内容的信息的 RTSP 设置参数,以便在步骤中填充空白处 840. 那么,电视 230 同步操作播放器 845 ,并从移动终端接收要在空白处展示的广告 200 在一步 850 . 因此,电视 230 可以通过播放器再现广告,从而可以输出视频等广告。 [0057] 参考图9,电视的镜像屏幕 230 等同于屏幕 900 移动终端的 200 位于中心部分 905 电视的 230 . 在这种情况下,除了中心部分之外,其余屏幕的左右部分会产生空白空间 905 电视的 230 . 图 9 说明了一个示例,其中广告屏幕 910 和 915 一起显示在镜像屏幕中心的两侧 905 . 在这种情况下,包含在RTSP设置参数中的内容信息包含作为“广告视频”的内容类型,指示该内容是广告。 当移动端 200 不直接提供广告,内容信息可能包含接收广告的内容地址。 [0058] 如上所述,根据本发明,用户可以在移动终端屏幕上查看图像 200 通过将图像镜像到移动终端屏幕上的放大屏幕 200 到电视 230 ,也可以在移动端屏幕上查看图片进行对象选择 200 连同之前通过电视的图像 230 . [0059] 根据本发明,由于用户可以控制外部显示设备的屏幕显示,因此与使用移动终端相比,具有用户接收到更生动和更有效的图像的优点。 优点是根据接收镜像的设备的特点,使用双屏,例如宽高比,通过外接大屏可以进行网页预览和内容预览。 显示设备,同时保持移动终端屏幕。 [0060] 此外,通过在设备屏幕的空白空间中显示广告,具有使用外部显示设备作为新商业模式的优点。 例如,可以通过统计广告的复制次数来向广告商索取广告收益,并以广告为目的对移动终端产品进行广告宣传,从而使广告效果最大化。 [0061] 尽管本发明已经参照其某些实施例进行了展示和描述,但本领域技术人员将理解,在不背离由以下定义的本发明的精神和范围的情况下,在形式和细节上进行了各种改变。 所附权利要求。 因此,在不背离由所附权利要求限定的本发明的主旨的情况下,可以进行若干修改。 应当理解,这些修改仍然在本发明的技术思想和概述之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.208 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104471954A(String), CN104471954B(String), EP2875645A1(String), EP2875645A4(String), EP2875645B1(String), KR1020140011857A(String), US10114522B2(String), US20140026068A1(String), WO2014014185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104471954A(String), CN104471954B(String), EP2875645A1(String), EP2875645A4(String), EP2875645B1(String), KR1020140011857A(String), US10114522B2(String), US20140026068A1(String), WO2014014185A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10114522B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104471954A(String), CN104471954B(String), EP2875645A1(String), EP2875645A4(String), EP2875645B1(String), KR1020140011857A(String), US10114522B2(String), US20140026068A1(String), WO2014014185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), CN104471954A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), CN104471954B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.504 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), EP2875645A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), EP2875645A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), EP2875645B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.609 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), KR1020140011857A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.645 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), US10114522B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), US20140026068A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271668(Integer), WO2014014185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10114522B2(String), US10114522B2(String), 1540828800(Integer), 271668(Integer), 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.830 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185994(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 185994(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185994(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:42.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 185994(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.035 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.104 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.140 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.156 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.157 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.157 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185994(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.347 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10499298B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10499298B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/180651(String), 1541347200(Integer), US10499298B2(String), 1575302400(Integer), 1575302400(Integer), 美国(String), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185995(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.874 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\709a35e9657f436e84276b60cf9f6df3.png(String), 185995(Integer), 709a35e9657f436e84276b60cf9f6df3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10499298B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/180651(String), 1541347200(Integer), US10499298B2(String), 1575302400(Integer), 1575302400(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), \20230420\709a35e9657f436e84276b60cf9f6df3.png(String), 16(Integer), 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:43.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 1. A method, comprising:obtaining, by a mobile terminal, a measurement result of a target cell by measuring the target cell according to measurement configuration information, wherein the measurement configuration information is obtained by the mobile terminal, by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; anddetermining, by the mobile terminal according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and in response, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell; ordetermining, by the mobile terminal, that the mobile terminal generates a measurement report according to the measurement result and that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, and in response, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell; ordetermining, by the mobile terminal, according to the measurement result and indication information that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and that the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, and in response, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell.(String), 1.一种方法,包括:移动终端根据测量配置信息对目标小区进行测量获得目标小区的测量结果,其中,所述测量配置信息是移动终端通过与所述目标小区之间建立的无线资源控制(RRC)连接获得的。移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元;和移动终端根据测量结果和指示信息确定测量结果满足该指示信息对应的测量上报事件的进入条件,作为响应,移动终端发起接入连接建立目标小区对应的网元,其中,指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立;或者移动终端确定移动终端根据测量结果生成测量报告,该测量报告为指示信息对应的测量报告事件的测量报告,作为响应,移动终端发起,与目标小区对应的接入网元建立连接,其中,指示信息用于指示移动终端发起与目标小区对应的接入网元的连接建立;或者移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件,移动终端生成对应的测量上报事件的测量报告指示信息,作为响应,移动终端向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立目标细胞。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 2. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:skipping, by the mobile terminal, sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiating connection establishment to the access network element corresponding to the target cell.(String), 2.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 3. The method according to claim 1, wherein:when it is determined that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal determines that a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orwhen it is determined that the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information, initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal determines that a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 3.根据权利要求1所述的方法,其中:当确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端确定测量结果满足指示信息对应的测量上报事件进入条件的时长达到预定时长时,移动终端发起到目标小区对应的接入网网元的连接建立;或者当确定移动终端生成指示信息对应的测量上报事件的测量报告时,移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端确定生成指示信息对应的测量报告事件的测量报告后的时长达到预定时长时,移动终端发起到目标小区对应的接入网网元的连接建立。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 4. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:when the mobile terminal is in a discontinuous reception (DRX) state, initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell.(String), 4.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端处于非连续接收(DRX)状态时,移动终端向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 5. The method according to claim 4, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 5.根据权利要求4所述的方法,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 6. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:when a mobility state estimation of the mobile terminal is greater than or equal to a speed threshold, initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell.(String), 6.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端的移动状态估计值大于或等于速度门限时,移动终端向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 7. The method according to claim 1, further comprising:sending, by the mobile terminal, a mobility state estimation of the mobile terminal to the access network element corresponding to the serving cell; andreceiving, by the mobile terminal, the indication information after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold specified by the access network element corresponding to the serving cell.(String), 7.根据权利要求1所述的方法,还包括:移动终端向服务小区对应的接入网元发送移动终端的移动状态估计;和移动终端在服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限后,接收指示信息。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 8. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell comprises:initiating, by the mobile terminal to the target cell, at least one of: a random access process, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 8.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:移动终端向目标小区发起以下至少之一:随机接入过程、RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 9. An apparatus, comprising:a storage medium comprising processor-executable instructions; anda processor coupled to the storage medium, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:obtain a measurement result of a target cell by measuring the target cell according to measurement configuration information, wherein the measurement configuration information is obtained by a mobile terminal, by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell, anddetermine, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and in response, initiate connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell, ordetermine that a measurement report is generated according to the measurement result and that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, and in response, initiate connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell, ordetermine according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and that a measurement report of the measurement reporting event corresponding to the indication information is generated, and in response, initiate connection establishment to an access network element corresponding to the target cell, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell.(String), 9.一个仪器,包括:包括处理器可执行指令的存储介质;和耦合到存储介质的处理器,其中处理器可执行指令在由处理器执行时使装置:根据测量配置信息测量目标小区获得目标小区的测量结果,其中测量配置信息是移动终端通过移动终端与接入网之间建立的无线资源控制(RRC)连接获得的服务小区对应的网元,来自服务小区对应的接入网网元,根据测量结果和指示信息,确定测量结果满足指示信息对应的测量上报事件的进入条件,作为响应,向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示向目标小区对应的接入网元发起连接建立,或者确定根据测量结果生成测量报告,该测量报告为指示信息对应的测量报告事件的测量报告,作为响应,向目标小区对应的接入网元发起连接建立,其中指示信息用于指示向目标小区对应的接入网元发起连接建立,或者根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件,生成指示信息对应的测量上报事件的测量报告,响应、向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示向目标小区对应的接入网元发起连接建立。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 10. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:skip sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiate connection establishment to the access network element corresponding to the target cell.(String), 10.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 11. The apparatus according to claim 9, wherein:when it is determined that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:initiate connection establishment to the access network element corresponding to the target cell when a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orwhen it is determined that the measurement report is generated according to the measurement result and the measurement report is a measurement report of a measurement reporting event, the processor-executable instructions, when executed by the processor, further cause the apparatus to:initiate connection establishment to the access network element corresponding to the target cell when a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 11.根据权利要求9所述的装置,其中:当确定测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立,处理器可执行指令在处理器执行时,进一步使设备:当测量结果满足指示信息对应的测量上报事件进入条件的时长达到预定时长时,发起到目标小区对应的接入网元的连接建立;或者当确定测量报告是根据测量结果生成的并且测量报告是测量报告事件的测量报告时,处理器可执行指令在被处理器执行时还使装置:当生成指示信息对应的测量报告事件的测量报告后的时长达到预定时长时,发起到目标小区对应的接入网元的连接建立。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 12. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when the apparatus is in a discontinuous reception (DRX) state, initiate connection establishment to the access network element corresponding to the target cell.(String), 12.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当装置处于非连续接收(DRX)状态时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 13. The apparatus according to claim 12, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 13.根据权利要求12所述的装置,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 14. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when a mobility state estimation of the apparatus is greater than or equal to a speed threshold, initiate connection establishment to the access network element corresponding to the target cell.(String), 14.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当该装置的移动性状态估计大于或等于速度门限时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 15. The apparatus according to claim 9, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:send a mobility state estimation of the apparatus to the access network element corresponding to the serving cell; andreceive the indication information after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold.(String), 15.根据权利要求9所述的装置,其中处理器可执行指令在由处理器执行时使装置:向服务小区对应的接入网元发送该装置的移动性状态估计;和在服务小区对应的接入网元确定移动状态估计大于或等于速度门限后,接收指示信息。(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185995(Integer), 16. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, cause the apparatus to:initiate to the target cell, at least one of: a random access process, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 16.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时使装置:向目标小区发起以下至少之一:随机接入过程、RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185995(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. application Ser. No. 15/473,407, filed on Mar. 29, 2017, which is a continuation of International Application No. PCT/CN2014/088061, filed on Sep. 30, 2014. All of the afore-mentioned patent applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present invention relate to the field of communications technologies, and in particular, to a mobile terminal control method and a mobile terminal. BACKGROUND [0003]Currently, a mobile terminal and life of a user are closely related to each other. Usually, the user performs a communication service such as chat by using the mobile terminal while being on a vehicle such as a bus or a subway. In this case, the mobile terminal also moves at high speed as the vehicle moves. Because the mobile terminal moves at relatively high speed, in terms of a physical location, after the mobile terminal enters from a coverage area of a previous serving cell to a coverage area of a new cell, quality of a communication service provided by the serving cell is deteriorated. In addition, because the mobile terminal cannot establish a connection to the new cell in a timely manner either, mobility of the mobile terminal is affected. For example, because the quality of the communication service provided by the serving cell is deteriorated, and the mobile terminal cannot establish a connection to the new cell in a timely manner either, a communication service currently performed by the mobile terminal is interrupted. [0004]Specifically, before establishing a connection to an access network element corresponding to the new cell, the mobile terminal needs to send a measurement report about the new cell to an access network element corresponding to the serving cell. The mobile terminal may establish a connection to a new cell only when the mobile terminal receives an indication that connection establishment is allowed and that is sent by the access network element corresponding to the serving cell. It may be understood that, by using the prior art, the mobile terminal needs to wait for a relatively long time period from discovering the new cell to establishing a connection to the new cell, and cannot establish a connection to the new cell in a timely manner to obtain a communication service provided by the new cell. Particularly, when the mobile terminal is in a discontinuous reception (DRX) state, an interval at which the mobile terminal measures the serving cell and an interval at which the mobile terminal measures the new cell become longer. For example, when a DRX cycle is 320 ms, and the mobile terminal needs to spend 5 times the DRX cycle performing radio resource management (RRM) measurement on a neighboring cell, the mobile terminal needs to spend a longer time period from discovering a new cell to establishing a connection to the new cell, and mobility of the mobile terminal cannot meet a basic requirement of the user. Therefore, how the mobile terminal establishes a connection to a new cell in a timely manner is an important aspect of improving performance of the mobile terminal. SUMMARY [0005]Embodiments of the present invention provide a mobile terminal control method and a mobile terminal, so as to improve mobility of the mobile terminal. [0006]According to a first aspect, an embodiment of the present invention provides a processing method for establishing a connection to an access network element by a mobile terminal, and the method includes:[0007]measuring, by a mobile terminal, a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and[0008]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or[0009]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information; or[0010]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and when the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information, where[0011]the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. [0012]According to a second aspect, an embodiment of the present invention provides a method for controlling a DRX state of a mobile terminal, and the method includes:[0013]performing, by a mobile terminal, radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and[0014]when the mobile terminal determines, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold,[0015]starting, by the mobile terminal, a timer, and before the timer expires, transitioning the mobile terminal from a DRX state to a non-DRX state, or transitioning the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shortening a cycle of the DRX state. [0016]According to a third aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes:[0017]a measurement module, configured to measure a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and[0018]a processing module, configured to: initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or[0019]initiate connection establishment to an access network element corresponding to the target cell when generating a measurement report according to the measurement result, and determining that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the processing module generates the measurement report of the measurement reporting event corresponding to the indication information; or[0020]initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the processing module generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the processing module generates the measurement report of the measurement reporting event corresponding to the indication information, where[0021]the indication information is obtained by the processing module in advance from the access network element corresponding to the serving cell. [0022]According to a fourth aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes:[0023]an obtaining module, configured to perform radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and[0024]a processing module, configured to: when determining, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold,[0025]start a timer, and before the timer expires, transition the mobile terminal from a DRX state to a non-DRX state, or transition the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shorten a cycle of the DRX state. [0026]According to the mobile terminal control method and the mobile terminal that are provided in the embodiments of the present invention, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. BRIEF DESCRIPTION OF THE DRAWINGS [0027]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0028]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0029]FIG. 3 is a schematic diagram of an RRC connection establishment process according to Embodiment 2 of the present invention; [0030]FIG. 4 is a schematic diagram of an RRC connection re-establishment process according to Embodiment 2 of the present invention; [0031]FIG. 5 is a schematic diagram of a cell update process according to Embodiment 2 of the present invention; [0032]FIG. 6 is a schematic diagram of a contention-based random access process according to Embodiment 2 of the present invention; [0033]FIG. 7 is a schematic diagram of a non-contention-based random access channel process according to Embodiment 2 of the present invention; [0034]FIG. 8 is a schematic flowchart of Embodiment 3 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0035]FIG. 9A and FIG. 9B are a schematic flowchart of Embodiment 4 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0036]FIG. 10A and FIG. 10B are a schematic flowchart of Embodiment 5 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0037]FIG. 11A and FIG. 11B are a schematic flowchart of Embodiment 6 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0038]FIG. 12A to FIG. 12C are a schematic flowchart of Embodiment 7 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0039]FIG. 13A to FIG. 13C are a schematic flowchart of Embodiment 8 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0040]FIG. 14A to FIG. 14C are a schematic flowchart of Embodiment 9 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0041]FIG. 15A to FIG. 15C are a schematic flowchart of Embodiment 10 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0042]FIG. 16 is a schematic flowchart of Embodiment 1 of a method for controlling a DRX state of a mobile terminal according to the present invention; [0043]FIG. 17 is a schematic structural diagram of Embodiment 1 of a mobile terminal according to the present invention; [0044]FIG. 18 is a schematic structural diagram of Embodiment 2 of a mobile terminal according to the present invention; [0045]FIG. 19 is a schematic structural diagram of Embodiment 3 of a mobile terminal according to the present invention; [0046]FIG. 20 is a schematic structural diagram of Embodiment 4 of a mobile terminal according to the present invention; [0047]FIG. 21 is a schematic structural diagram of Embodiment 5 of a mobile terminal according to the present invention; and [0048]FIG. 22 is a schematic structural diagram of Embodiment 6 of a mobile terminal according to the present invention. DETAILED DESCRIPTION [0049]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 1, this embodiment is executed by a mobile terminal, and specifically includes the following steps. [0050]S101. The mobile terminal measures a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell. [0051]The mobile terminal establishes an RRC (radio resource control) connection to a serving cell, and the measurement configuration information is obtained by the mobile terminal, by using the RRC connection, from an access network element (which may be specifically a base station that manages the serving cell) corresponding to the serving cell. Specifically, the measurement configuration information includes a configuration about a measurement reporting event and the measurement reporting event may be specifically an event A3, an event A4, an event A5, or the like. [0052]Specifically, the mobile terminal performs RRM measurement on the target cell according to the measurement configuration information, so as to obtain an RRM measurement result. The target cell may be a neighboring cell of the serving cell, or may be a corresponding cell. When the target cell is a corresponding cell, the mobile terminal needs to obtain an identity of the corresponding cell from the serving cell before the mobile terminal performs measurement. [0053]S102. When the mobile terminal determines, according to the measurement result of the target cell and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0054]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0055]By performing S102, the mobile terminal skips generating a measurement report of the measurement reporting event corresponding to the indication information, skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0056]Alternatively, after performing S101, the mobile terminal chooses to perform S103 instead of S102. [0057]S103. When the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0058]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to indication information. [0059]By performing S103, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0060]Alternatively, after performing S101, the mobile terminal chooses to perform S104 instead of S102 and S103. [0061]S104. When the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0062]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information. [0063]By performing S104, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0064]In any one step of the foregoing S102, S103, or S104, the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. Optionally, the mobile terminal receives, by using the RRC connection, the indication information sent by the access network element corresponding to the serving cell. Specifically, the access network element corresponding to the serving cell may deliver the indication information while delivering the measurement configuration information to the mobile terminal, or may deliver the indication information to the mobile terminal before this embodiment is executed. In this embodiment, an example in which the measurement reporting event is the event A3 or the event A4 is used. When the measurement reporting event is specifically the event A3, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”. When the measurement reporting event is specifically the event A4, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Thresh”. Mn is the measurement result of the target cell, Ofn is a frequency specific offset of the target cell, and Ocn is a cell individual offset of the target cell. If the target cell is not configured with the cell individual offset, when the formulas are applied, a value of Ocn may be 0. Ms is a measurement result of the serving cell, Ofs is a frequency specific offset of the serving cell, Ocs is a cell individual offset of the serving cell, Hys is an event hysteresis parameter, Off is an event offset parameter, and Thresh is an event threshold parameter. Parameters such as Ofn, Ocn, Hys, Ofs, Ocs, and Off are obtained by the mobile terminal in advance. [0065]Specifically, in communication transmission, the indication information is specifically at least one piece of data. The at least one piece of data includes an identifier of the measurement reporting event. For example, if the at least one piece of data includes an identifier “A3”, it indicates that the measurement reporting event corresponding to the indication information is the event A3. Alternatively, the at least one piece of data is specifically a specific identifier. The specific identifier may be located in measurement configuration information, and is associated with the configuration about the measurement reporting event in the measurement configuration information. For example, if partial content of the measurement configuration information is a configuration about the event A3, and the specified identifier is associated with the configuration about the event A3 in the measurement configuration information, it may indicate that the measurement reporting event corresponding to the indication information is the event A3. [0066]Possibly, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0067]Optionally, the indication information may be specifically a direct re-establishment indication, a cell update indication, or a forward handover indication. [0068]In this embodiment, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0069]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 2, on the basis of the embodiment shown in FIG. 1, this embodiment is described in a implementation manner, and specifically includes the following steps. [0070]S201. A mobile terminal receives measurement configuration information and indication information that are sent by an access network element corresponding to a serving cell. [0071]The measurement configuration information and the indication information may be sent, to the mobile terminal by using same signaling, by the access network element corresponding to the serving cell, or may be sent, to the mobile terminal by using different signaling, by the access network element corresponding to the serving cell. [0072]S202. The mobile terminal measures a target cell, so as to obtain a measurement result of the target cell. [0073]The step is specifically described in S101. However, it should be noted that, in addition to being a newly discovered neighboring cell, the target cell may be a specified cell described in the S101, and may be specifically specified by the indication information. That is, if the indication information further carries a cell identity, a cell corresponding to the cell identity carried in the indication information is the target cell. [0074]S203. The mobile terminal determines whether the measurement result of the target cell meets an entering condition of a measurement reporting event corresponding to the indication information, and if yes, the mobile terminal performs S204, or if no, this embodiment ends. [0075]Optionally, in this embodiment, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0076]For example, if the mobile terminal receives two pieces of indication information in S201, one of the two pieces of indication information is corresponding to an event A3, and the other is corresponding to an event A4. When the measurement result obtained in S202 meets an entering condition of either measurement reporting event of the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S204. [0077]Alternatively, if one piece of indication information is obtained in S201, and the indication information is corresponding to an event A3 and an event A4, when the measurement result obtained in S202 meets an entering condition of either the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S204. [0078]Alternatively, if the indication information obtained in S201 is corresponding to an event A3, when the measurement result obtained in S202 meets an entering condition of the event A3, the mobile terminal performs the following S204. That is, when Mn meets “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, the mobile terminal performs S204. However, when Mn meets “Mn+Ofn+Ocn−Hys>Thresh” but does not meet “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, this embodiment ends, that is, an entering condition that is of a measurement reporting event and is met by the measurement result is not the entering condition of the measurement reporting event corresponding to the indication information. [0079]It should be additionally noted that, if the indication information is used to instruct the mobile terminal to initiate connection establishment to an access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal may directly perform S205 after determining, by performing S203, that the measurement result of the target cell meets the entering condition of the measurement reporting event corresponding to the indication information. However, to ensure that a control effect, on the mobile terminal, of a network-side device in a communications network is not affected and to give consideration to mobility of the mobile terminal as well, in this embodiment, preferably, the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. The mobile terminal performs S204 and S205 in sequence after determining, by performing S203, that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0080]S204. The mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. [0081]S205. The mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0082]The connection establishment in S205 specifically includes:[0083]initiating, by the mobile terminal, a random access process to the target cell, and/or any one of the following processing:[0084]initiating, by the mobile ter(String), 相关申请的交叉引用 [0001] 该申请是美国申请 Ser. 2017 年 3 月 29 日提交的第 15/473,407 号国际申请是 2014 年 9 月 30 日提交的国际申请第 PCT/CN2014/088061 号的继续申请。所有上述专利申请均通过引用并入本文 完整地。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种移动终端控制方法及移动终端。 背景 [0003] 目前,移动终端与用户的生活息息相关。 通常,用户在诸如公共汽车或地铁的交通工具上通过使用移动终端进行诸如聊天的通信服务。 在这种情况下,移动终端也随着车辆的移动而高速移动。 由于移动终端移动速度较高,从物理位置上来说,移动终端从上一个服务小区的覆盖范围进入到新的小区覆盖范围后,服务小区提供的通信服务质量 恶化。 另外,由于移动终端也无法及时与新小区建立连接,影响了移动终端的移动性。 例如,由于服务小区提供的通信服务质量下降,移动终端也无法及时建立到新小区的连接,导致移动终端当前进行的通信服务中断。 [0004] 具体地,移动终端在与新小区对应的接入网元建立连接之前,需要向服务小区对应的接入网元发送关于新小区的测量报告。 只有当移动终端接收到服务小区对应的接入网元发送的允许建立连接的指示时,移动终端才可以建立到新小区的连接。 可以理解的是,采用现有技术,移动终端从发现新小区到与新小区建立连接需要等待较长的时间,不能及时与新小区建立连接。 获得新小区提供的通信服务的方式。 特别地,当移动终端处于非连续接收(DRX)状态时,移动终端测量服务小区的间隔和移动终端测量新小区的间隔变长。 例如,当DRX周期为320ms时,移动终端需要花费5倍的DRX周期对邻区进行无线资源管理(Radio Resource Management,无线资源管理)测量,则移动终端需要花费更长的时间才能发现新的小区。 小区与新小区建立连接,移动终端的移动性不能满足用户的基本需求。 因此,移动终端如何及时建立与新小区的连接是提高移动终端性能的重要方面。 概括 [0005] 本发明实施例提供一种移动终端控制方法及移动终端,以提高移动终端的移动性。 [0006] 第一方面,本发明实施例提供了一种移动终端与接入网元建立连接的处理方法,该方法包括: [0007]移动终端根据测量配置信息对目标小区进行测量,以获取目标小区的测量结果,其中,移动终端获取测量配置信息,使用之间建立的无线资源控制RRC连接 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和[0008] 当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立; 或者[0009] 当移动终端根据测量结果生成测量报告时,移动终端发起到目标小区对应的接入网元的连接建立,移动终端确定该测量报告为测量报告的测量报告 指示信息对应的事件,该指示信息用于在移动终端生成该指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立; 或者[0010] 当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,当移动终端生成该指示信息对应的测量报告事件的测量报告时,该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,如果 测量结果满足指示信息对应的测量上报事件的进入条件,移动终端生成指示信息对应的测量上报事件的测量报告,其中[0011] 指示信息是移动终端预先从服务小区对应的接入网元获取的。 [0012] 第二方面,本发明实施例提供了一种移动终端的DRX状态控制方法,该方法包括: [0013] 移动终端根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,以获取服务小区的下行无线链路质量; 和[0014] 当移动终端通过估计下行无线链路质量,确定下行无线链路连续出现失步指示的次数达到预设门限时,[0015] 移动终端启动定时器,在定时器超时之前,将移动终端从DRX状态转变为非DRX状态,或者将移动终端从长周期DRX状态转变为短周期DRX状态 ,或者缩短DRX状态的周期。 [0016] 第三方面,本发明实施例提供了一种移动终端,该移动终端包括: [0017] 测量模块,用于根据测量配置信息对目标小区进行测量,以获取所述目标小区的测量结果,所述测量配置信息为所述移动终端通过与所述目标小区之间建立的无线资源控制RRC连接获得的 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和[0018]处理模块,用于在根据所述测量结果和指示信息确定所述测量结果满足所述指示信息对应的测量上报事件的进入条件时,发起到所述目标小区对应的接入网元的连接建立 , 该指示信息用于指示处理模块如果测量结果满足该指示信息对应的测量上报事件的进入条件,则向目标小区对应的接入网元发起连接建立; 或者[0019] 根据测量结果生成测量报告时,向目标小区对应的接入网元发起连接建立,确定该测量报告为指示信息对应的测量报告事件的测量报告,其中使用该指示信息 若处理模块生成指示信息对应的测量上报事件的测量报告,则指示处理模块向目标小区对应的接入网元发起连接建立; 或者[0020] 当根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,发起到目标小区对应的接入网元的连接建立,处理模块生成 指示信息对应的测量上报事件的测量报告,指示信息用于在测量结果满足测量上报进入条件时,指示处理模块向目标小区对应的接入网元发起连接建立 指示信息对应的事件,处理模块生成指示信息对应的测量报告事件的测量报告,其中[0021] 指示信息由处理模块预先从服务小区对应的接入网元获取。 [0022] 第四方面,本发明实施例提供一种移动终端,该移动终端包括: [0023] 获取模块,用于根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,获取服务小区的下行无线链路质量; 和[0024] 处理模块,用于通过对所述下行无线链路质量的估计,确定所述下行无线链路连续出现失步指示的次数达到预设门限时,[0025] 启动定时器,在定时器超时前,将移动终端从DRX状态转移到非DRX状态,或者将移动终端从长周期DRX状态转移到短周期DRX状态,或者缩短周期 DRX 状态。 [0026]本发明实施例提供的移动终端控制方法及移动终端,通过指示信息指示移动终端在测量结果满足时,向目标小区对应的接入网元发起连接建立。 指示信息对应的测量上报事件的进入条件; 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 附图的简要说明 [0027] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图; [0028] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图; [0029] 图3为本发明实施例二的RRC连接建立过程示意图; [0030] 图4为本发明实施例二的RRC连接重建过程示意图; [0031] 图5为本发明实施例二的小区更新过程示意图; [0032] 图6为本发明实施例二的基于竞争的随机接入过程的示意图; [0033] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图; [0034] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图; [0035] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图; [0036] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图; [0037] 图11A和图11B为本发明移动终端与小区建立连接的处理方法实施例六的流程示意图; [0038] 图12A至图12C为本发明移动终端与小区建立连接的处理方法实施例七的流程示意图; [0039] 图13A至图13C为本发明移动终端与小区建立连接的处理方法实施例八的流程示意图; [0040] 图14A至图14C为本发明移动终端与小区建立连接的处理方法实施例九的流程示意图; [0041]图15A至图15C为本发明移动终端与接入网元建立连接的处理方法实施例十的流程示意图; [0042] 图16为本发明移动终端的DRX状态控制方法实施例一的流程示意图; [0043] 图17为本发明移动终端实施例一的结构示意图; [0044] 图18为本发明移动终端实施例二的结构示意图; [0045] 图19为本发明移动终端实施例三的结构示意图; [0046] 图20为本发明移动终端实施例四的结构示意图; [0047] 图21为本发明移动终端实施例五的结构示意图; 和 [0048] 图22为本发明移动终端实施例六的结构示意图。 详细说明 [0049] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图。 如图1所示,本实施例的执行主体为移动终端,具体包括以下步骤。 [0050] 小号 101 . 移动终端根据测量配置信息对目标小区进行测量,以获得目标小区的测量结果。 [0051] 移动终端与服务小区建立RRC(无线资源控制)连接,移动终端通过RRC连接从接入网元(具体可以是管理基站的基站)获取测量配置信息 服务小区)对应于服务小区。 具体的,测量配置信息包括测量上报事件的配置,测量上报事件具体可以是事件A 3 , 一个事件 A 4 , 一个事件 A 5 , 等等。 [0052] 具体的,移动终端根据测量配置信息对目标小区进行RRM测量,得到RRM测量结果。 目标小区可以是服务小区的邻区,也可以是对应小区。 当目标小区为对应小区时,移动终端在进行测量前需要从服务小区获取对应小区的标识。 [0053] 小号 102 . 当移动终端根据目标小区的测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立 到目标单元格。 [0054] 该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0055] 通过执行 S 102 , 移动终端跳过生成指示信息对应的测量报告事件的测量报告, 跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告, 发起 与目标小区对应的接入网元建立连接,使得移动终端能够及时发起与目标小区对应的接入网元的连接建立,提高了移动终端的移动性。 [0056] 或者,在执行 S 之后 101 , 移动端选择执行S 103 而不是S 102 . [0057] 小号 103. 当移动终端根据测量结果生成测量报告,且移动终端确定该测量报告为指示信息对应的测量报告事件的测量报告时,移动终端向指示信息对应的接入网元发起连接建立 目标细胞。 [0058] 该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 [0059] 通过执行 S 103 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0060] 或者,在执行 S 之后 101 , 移动端选择执行S 104 而不是S 102 和小号 103 . [0061] 小号 104 . 当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端生成对应的测量上报事件的测量报告。 指示信息,移动终端向目标小区对应的接入网元发起连接建立。 [0062] 该指示信息用于指示移动终端在测量结果满足指示信息对应的测量报告事件的进入条件并生成测量报告时,向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0063] 通过执行 S 104 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0064] 在上述S的任何一个步骤中 102 , 小号 103 , 或小号 104 ,该指示信息是移动终端预先从服务小区对应的接入网元获取的。 可选的,移动终端通过RRC连接接收服务小区对应的接入网元发送的指示信息。 具体地,服务小区对应的接入网元可以在向移动终端下发测量配置信息的同时下发指示信息,也可以在本实施例执行前向移动终端下发指示信息。 本实施例以测量上报事件为事件A为例 3 或事件 A 4 用来。 当测量报告事件具体为事件A时 3 ,测量上报事件的进入条件为:“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”。 当测量报告事件具体为事件A时 4,测量上报事件的进入条件为:“Mn+Ofn+Ocn−Hys>Thresh”。 Mn是目标小区的测量结果,Ofn是目标小区的频率特定偏移,Ocn是目标小区的小区个体偏移。 如果目标小区没有配置小区个体偏移,当应用公式时,Ocn的值可以为0。Ms是服务小区的测量结果,Ofs是服务小区的频率特定偏移,Ocs是 服务小区的小区个体偏移,Hys为事件迟滞参数,Off为事件偏移参数,Thresh为事件阈值参数。 Ofn、Ocn、Hys、Ofs、Ocs、Off等参数由移动终端预先获取。 [0065] 具体地,在通信传输中,指示信息具体为至少一个数据。 至少一个数据包括测量报告事件的标识。 例如,如果至少一个数据包括标识符“A 3 ”,表示该指示信息对应的测量上报事件为事件A 3 . 或者,所述至少一个数据具体为特定标识。 特定标识可以位于测量配置信息中,与测量配置信息中关于测量上报事件的配置相关联。 例如,如果测量配置信息的部分内容是关于事件A的配置 3 , 指定的标识符与事件A的配置相关联 3 在测量配置信息中,可以指示该指示信息对应的测量上报事件为事件A 3 . [0066] 可能的,该指示信息至少有一条,该指示信息对应的测量上报事件至少有一个。 [0067] 可选的,该指示信息具体可以为直接重建指示、小区更新指示或前向切换指示。 [0068] 本实施例中,指示信息用于当测量结果满足指示信息对应的测量上报事件的进入条件时,指示移动终端向目标小区对应的接入网元发起连接建立。 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 [0069] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图。 如图2所示,在图1所示实施例的基础上,对本实施例的实施方式进行说明,具体包括以下步骤。 [0070] 小号 201 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0071] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0072] 小号 202 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0073] 该步骤在 S 中具体描述 101 . 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0074] 小号 203 . 移动终端判断目标小区的测量结果是否满足该指示信息对应的测量上报事件的进入条件,如果满足,移动终端执行S 204 ,否则,本实施例结束。 [0075] 可选的,在本实施例中,指示信息至少有一条,与指示信息对应的测量上报事件至少有一个。 [0076] 例如,如果移动终端在S中接收到两条指示信息 201 , 两条指示信息之一对应事件A 3 , 另一个对应事件A 4 . 当在 S 中获得的测量结果 202 满足事件A任一测量上报事件的进入条件 3 或事件 A 4 ,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行如下S 204 . [0077] 或者,若在S中获取到一条指示信息 201 ,指示信息对应事件A 3 和一个事件 A 4 , 当在 S 中获得的测量结果 202 满足事件A的进入条件 3 或事件 A 4 ,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行如下S 204 . [0078] 或者,若S中获取的指示信息 201 对应一个事件A 3 , 当在 S 中获得的测量结果 202 满足事件A的进入条件 3 ,移动终端执行以下S 204 . 即当Mn满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,移动终端执行S 204 . 而当Mn满足“Mn+Ofn+Ocn-Hys>Thresh”但不满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,本实施例结束,即进入条件为 测量上报事件的条件,测量结果满足的不是该指示信息对应的测量上报事件的进入条件。 [0079] 还需要说明的是,如果该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,则测量结果满足该指示信息对应的测量上报事件的进入条件 ,移动终端可以直接执行S 205 确定后,通过执行 S 203,则目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 但是,为保证通信网络中网络侧设备对移动终端的控制效果不受影响,同时兼顾移动终端的移动性,本实施例中,优选的,所述指示信息为 用于如果测量结果满足指示信息对应的测量上报事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成测量上报的测量报告 指示信息对应的事件。 移动终端执行S 204 和小号 205 确定后依次执行S 203 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0080] 小号 204 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0081] 小号 205 . 移动终端向目标小区对应的接入网元发起连接建立。 [0082] S中的连接建立 205 具体包括: [0083] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理:[0084] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 [0085] 图3为本发明实施例二的RRC连接建立过程示意图。 如图3所示,具体过程包括以下步骤: [0086] C 11 . 移动终端向目标小区对应的接入网元发送RRC连接建立请求。 [0087] C 12 . 移动终端接收目标小区对应的接入网元发送的RRC连接建立消息。 [0088] C 13 . 移动终端向目标小区对应的接入网元发送RRC连接建立完成消息。 [0089] 图4为本发明实施例二的RRC连接重建过程示意图。 如图4所示,具体过程包括以下步骤: [0090] C 21 . 移动终端向目标小区对应的接入网元发送RRC连接重建请求。 [0091] C 22 . 移动终端接收目标小区对应的接入网元发送的RRC连接重建消息。 [0092] C 23 . 移动终端向目标小区对应的接入网元发送RRC连接重建完成消息。 [0093] 图5为本发明实施例二的小区更新过程示意图。 如图5所示,具体过程包括以下步骤: [0094] C 31 . 移动终端向目标小区对应的接入网元发送小区更新请求。 [0095] C 32 . 移动终端接收目标小区对应的接入网元发送的小区更新消息。 [0096] C 33 . 移动终端向目标小区对应的接入网元发送小区更新完成消息。 [0097] C 33 为可选步骤,可以根据实际网络情况执行也可以不执行。 [0098] 图6为本发明实施例二的基于竞争的随机接入信道过程示意图。 如图6所示,具体过程包括以下步骤: [0099] C 41 . 移动端发送消息 1 到目标小区对应的接入网元。 讯息 1 特别是“随机访问前导码”。 [0100] C 42 . 移动端收到消息 2 由目标小区对应的接入网元发送。 讯息 2特别是“随机访问响应”。 [0101] C 43 . 移动端发送消息 3 到目标小区对应的接入网元。 讯息 3 特别是“预定传输”。 [0102] C 44 . 移动端收到消息 4 由目标小区对应的接入网元发送。 讯息 4 具体是“争用解决”。 [0103] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图。 如图7所示,具体过程包括以下步骤: [0104] C 51 . 移动端收到消息 0 由目标小区对应的接入网元发送。 讯息 0 具体是“RA Preamble assignment”。 [0105] C 52 . 移动端发送消息 1 到目标小区对应的接入网元。 讯息 1 特别是“随机访问前导码”。 [0106] C 53 . 移动端收到消息 2 由目标小区对应的接入网元发送。 讯息 2 特别是“随机访问响应”。 [0107] 还应该注意的是,当确定时,通过执行 S 203 , 本实施例结束, 表示移动终端不再继续执行S 204 和小号 205 ,但继续按照现有技术进行其他操作。 例如,若指示信息对应的测量上报事件为事件A 3 , 但移动端在 S 中判断 203 目标小区的测量结果不满足事件A的进入条件 3 但满足事件A的进入条件 4 , 移动终端生成事件A的测量报告 4 根据满足事件A进入条件的测量结果 4 ; 发送事件A的测量报告 4 服务小区对应的接入网元; 等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到服务小区对应的接入网元下发给移动终端的允许建立连接的指示时,移动终端才建立到目标小区的连接。 [0108] 即,现有技术中,当目标小区的测量结果满足测量上报事件的进入条件时,移动终端首先需要生成测量报告,并将测量报告上报给目标小区对应的接入网元。 服务小区,然后需要等待服务小区对应的接入网元下发允许建立连接的指示。 在这个过程中,移动终端需要花费较长的时间周期,不利于提高移动终端与目标小区对应的接入网元建立连接的效率。 但是,在本说明书中,只要目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件,移动终端生成该指示信息对应的测量上报事件的测量报告,则 移动终端能够在移动终端与目标小区之间建立连接,提高了移动终端与目标小区对应的接入网元建立连接的效率,提高了移动终端的移动性。 [0109]本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立,并且移动终端生成 指示信息对应的测量上报事件的测量报告。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,以及 直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0110] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图。 如图8所示,在图1所示实施例的基础上,对本实施例的一个优选实施方式进行说明,具体包括以下步骤。 [0111] 小号 301 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0112] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0113] 小号 302 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0114] 该步骤在 S 中具体描述 101 . 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0115] 小号 303 . 移动终端根据测量结果生成测量报告。 [0116] 小号 304 . 移动终端判断该测量报告是否为该指示信息对应的测量报告事件的测量报告,如果是,则移动终端执行S 305 ,否则,本实施例结束。 [0117] 在本实施例中,该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 前提是在 S 中获得的测量结果 302 满足测量报告事件的进入条件,在S中生成测量报告 303 . 可以理解,当S中的测量结果满足测量上报事件的进入条件时 302 不是指示信息对应的测量报告事件的进入条件,S中生成的测量报告 303 也不是该指示信息对应的测量上报事件的测量报告。 [0118] 然而,如果移动终端确定,通过执行S 304 , S 中的测量报告 303为指示信息对应的测量报告事件的测量报告,即当移动终端根据指示信息确定移动终端生成指示信息对应的测量报告事件的测量报告时,移动终端 终端可以不向服务小区对应的接入网元发送该指示信息对应的测量报告事件的测量报告,直接执行S 305 . [0119] 可选的,在本实施例中,指示信息至少有一条,与指示信息对应的测量上报事件至少有一个。 [0120] 例如,如果移动终端在S中接收到两条指示信息 301 , 两条指示信息之一对应事件A 3 , 另一个对应事件A 4 , 当在 S 中获得的测量结果 302 满足事件A任一测量上报事件的进入条件 3 或事件 A 4 , S中生成的测量报告 303 必然是指示信息对应的测量上报事件的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0121] 或者,若在S中获取到一条指示信息 301 ,指示信息对应事件A 3 和一个事件 A 4 , 当在 S 中获得的测量结果 302 满足事件A的进入条件 3 或事件 A 4 , S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0122] 或者,若S中获取的指示信息 301 对应一个事件A 3 , 当在 S 中获得的测量结果 302 满足事件A的进入条件 3 , S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . 但是,有可能,如果在S中得到的指示信息 301 对应事件A 3 , 但在 S 中获得的测量结果 302 满足事件A的进入条件 4 , S中生成的测量报告 303 不是指示信息对应的测量报告而是事件A的测量报告 4 . 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 即当Mn满足“Mn+Ofn+Ocn−Hys>Thresh”但不满足“Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”时,S中生成的测量报告 303 不是指示信息对应的测量报告。 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 [0123] 小号 305 . 移动终端向目标小区对应的接入网元发起连接建立。 [0124] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理: [0125] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 具体可以参考图3至图7所示的信令流程。 [0126]本实施例中,指示信息用于指示移动终端跳过,如果移动终端生成该指示信息对应的测量报告事件的测量报告,则向服务小区对应的接入网元发送该测量 上报指示信息对应的测量上报事件。 因此,移动终端可以直接向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0127] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图。 如图9A和图9B所示,本实施例在图1所示实施例的基础上进行进一步说明,具体包括以下步骤。 [0128] 小号 401 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0129] 移动状态估计(Mobility State Estimation,MSE)是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0130] 小号 402 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0131] 小号 403 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0132] 该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0133] 小号 404 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0134] 当服务小区对应的接入网元学习时,通过执行S 402 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 403 向移动终端下发指示信息。 [0135] 测量配置信息和指示信息可以同时下发,即S 403 和小号 404 通过使用相同的信令来实现。 可选地,S 404 可以在 S 之前执行 403 ,或者可以在 S 之前或同时执行 402 ,或者可以在 S 之前或同时执行 401 . 例如,首先,移动终端接收到测量配置信息,然后,当确定移动终端在高速移动时,服务小区对应的接入网元下发指示信息。 此外,任选地,S 401 和小号 402 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0136] 小号 405 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0137]在移动终端接收到指示信息之前,移动终端根据S-Measure发现目标小区。 即移动终端只有在获知服务小区的服务质量低于预设值时才对邻区进行RRM测量,以发现测量结果满足测量上报事件的目标小区。 但在本实施例中,移动终端接收到指示信息后,可以忽略S-Measure,即移动终端可以随时对邻区进行RRM测量,无需等到服务 服务小区的质量低于预设值,从而及时判断目标小区的测量结果是否满足测量上报事件的进入条件,从而进一步提高移动终端的移动性 改善。 [0138] 小号 406 . 移动终端确定该测量结果满足该指示信息对应的测量上报事件的进入条件。 [0139] 可以理解的是,如果移动终端与目标小区建立连接,则移动终端在任意时刻确定目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 ,弱化了网络侧设备(如基站或基站控制器)对移动终端的控制。 但是,移动终端处于短周期DRX状态或长周期DRX状态时,对移动性的影响较大。 因此,可选地,当本实施例的移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示建立到目标小区的连接,即 移动端还需要执行以下S 407 执行 S 后 406 . [0140] 小号 407 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 409 或 408 ,或者如果否,则执行 S 410 . [0141] DRX状态为短周期DRX状态或长周期DRX状态。 [0142] 现有技术中,移动终端处于休眠状态的时长也会影响移动终端的移动性。 另外,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端处于休眠状态的时间较长,对移动终端的移动性影响更为严重。 . 而本实施例中,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示及时建立到目标小区的连接,以及 移动终端的移动性不受移动终端的短周期DRX状态或长周期DRX状态的影响。 [0143] 小号 408 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 409 ,或者如果是,则执行 S 410 . [0144] 当移动终端位于服务小区和目标小区的临界区域时,如果移动终端的移动速度较低,则移动终端更容易发生目标小区和服务小区之间的“乒乓切换”。 为了避免发生乒乓切换的情况,优选地,S 408 需要执行。 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 409 . [0145]另外,移动终端指定的速度门限和服务小区对应的接入网元指定的速度门限可以相同,也可以不同。 另外,移动终端指定的速度门限可以由服务小区对应的接入网元为移动终端配置,或者在通信协议中指定,例如,移动终端的速度门限为 高机动状态的速度。 [0146] 此外,S 407 和小号 408 为可选步骤,即在实际应用中实施本实施例时,移动终端可以选择执行S 407 和/或 408 执行 S 后 406 , 以及执行 S 的序列 407 和小号 408 不受限制。 在这个实施例中,一个例子中 S 408 在 S 之后执行 407 使用确定移动终端处于DRX状态。 [0147] 小号 409 . 移动终端向目标小区对应的接入网元发起连接建立。 [0148] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 因此,当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立。 目标细胞。 即,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的进入条件后,可以不生成该指示信息对应的测量上报事件的测量报告,不发送 , 向服务小区对应的接入网元, 指示信息对应的测量报告事件的测量报告, 向目标小区对应的接入网元发起连接建立, 使得移动终端可以发起, 在 及时与目标小区对应的接入网元建立连接,提高移动终端的移动性。 [0149] 小号 410 . 移动终端生成指示信息对应的测量报告事件的测量报告,并向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 [0150] 在本实施例中,即使移动终端接收到指示信息,并且目标小区的测量结果满足该指示信息对应的测量报告事件的进入条件,移动终端也可以根据S中的判断结果进行选择。 407 和/或 408 ,应用指示信息(即,执行S 409 ). 或者,移动终端根据S中的判断结果进行选择 407 和/或 408 , 不应用指示信息; 仍然按照现有技术与目标小区对应的接入网元建立连接,即执行S 410 ; 然后,等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0151]本实施例中,移动终端根据目标小区的测量结果确定该测量结果满足指示信息对应的测量上报事件的进入条件后,根据该指示信息的指示,移动终端可以跳过生成 指示信息对应的测量上报事件的测量报告, 并跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告, 使得移动终端可以直接 向目标小区对应的接入网元发起连接建立,提高移动终端的移动性。 [0152] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图。 如图10A和图10B所示,在图1或图2所示实施例的基础上,在一个优选实施方式中,本实施例具体包括以下步骤。 [0153] 小号 501 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0154] 移动状态估计是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0155] 小号 502 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0156] 小号 503 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0157] 该指示信息用于当测量结果满足该指示信息对应的测量报告事件的进入条件并生成测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0158] 小号 504 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0159] 当服务小区对应的接入网元学习时,通过执行S 502 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 503 向移动终端下发指示信息。 [0160] 测量配置信息和指示信息可以同时下发,即S 503 和小号 504 通过使用相同的信令来实现。 可选地,S 504 可以在 S 之前执行 503 ,或者可以在 S 之前或同时执行 502 ,或者可以在 S 之前或同时执行 501 . 例如,首先,移动终端接收到测量配置信息,然后,接入网元在确定移动终端高速移动时,下发指示信息。 此外,任选地,S 501 和小号 502 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0161] 小号 505 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0162] 小号 506 . 移动终端判断测量结果是否满足指示信息对应的测量上报事件的进入条件,如果满足,则执行S 507 ,或者如果否,则执行 S 511 . [0163] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件且移动终端向目标小区对应的接入网元发起连接建立时。 生成指示信息对应的测量报告事件的测量报告。 因此,本实施例中的移动终端通过执行S来确定 506 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0164] 可能的,如果测量结果既不满足指示信息对应的测量上报事件的进入条件,也不满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件,本实施例 结束,即移动终端不再进行后续步骤。 [0165] 但是,若测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件, 在该实施例中,根据现有技术,S 511 执行和小号 512 随后执行。 图9以测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件为例 指示信息。 [0166] 小号 507 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0167] 小号 508 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 510 或 509 ,或者如果否,则执行 S 512 . [0168] DRX状态为短周期DRX状态或长周期DRX状态。 [0169] 小号 509 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 510 ,或者如果是,则执行 S 512 . [0170] 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 510 . [0171] 小号 508 和小号 509 为可选步骤,即在实际应用中实施本实施例时,移动终端可以选择执行S 508 和/或 509 执行 S 后 507 , 以及执行 S 的序列 508 和小号 509 不受限制。 本实施例以移动终端继续执行S为例 509 执行 S 后 508 使用确定移动终端处于DRX状态。 [0172] 小号 510 . 移动终端向目标小区对应的接入网元发起连接建立。 [0173] 可选的,移动终端向目标小区对应的接入网元发起连接建立后,移动终端与服务小区对应的接入网元保持连接。 [0174] 小号 511. 移动终端根据满足测量报告事件的进入条件的测量结果生成测量报告,该测量报告事件不同于指示信息对应的测量报告事件的进入条件。 [0175] 小号 512 . 移动终端将测量报告发送给服务小区对应的接入网元。 [0176] 如果 S 之前的一步 512 是小号 508 或 509 ,移动终端发送的测量报告为指示信息对应的测量报告事件的测量报告。 如果 S 之前的一步 512 是小号 511 ,移动终端发送的测量报告是移动终端根据测量报告事件的满足进入条件的测量结果生成的测量报告,不同于指示信息对应的测量报告事件的进入条件 . [0177] 当 S 前一步 512 是小号 508 或 509 ,表示即使移动终端接收到指示信息,目标小区的测量结果也满足该指示信息对应的测量上报事件的进入条件,移动终端生成对应的测量上报事件的测量报告 对于指示信息,移动终端根据S中的判断结果进行选择 508 和/或 509 ,以应用指示信息(即,执行 S 510 ). 或者,移动终端根据S中的判断结果进行选择 508 和/或 509 , 不应用指示信息; 仍然按照现有技术建立到目标小区的连接,即执行S 512 将测量报告发送给服务小区对应的接入网元; 然后,等待接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0178] 可以理解的是,现有技术中的通信过程中已经包含了关于测量报告生成的协议、配置等。 因此,在基于现有协议或配置应用本实施例时,需要调整和修改的内容较少,范围较小,有利于本实施例的实施。 [0179] 本实施例中,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的进入条件后,生成该指示信息对应的测量上报事件的测量报告,然后, 移动终端可以直接向目标小区对应的接入网元发起连接建立。 然而,现有技术中,当目标小区的测量结果满足测量上报(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.390 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.583 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), CN105659666A(String), 1049229(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), EP3193534A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), EP3193534A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.688 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), US10142904B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), US10499298B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), US10805853B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), US20170251417A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), US20190075502A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.863 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), US20200068471A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.898 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271563(Integer), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.933 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.933 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN105659666A(String), CN105659666A(String), 1465315200(Integer), 271563(Integer), 185847(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:44.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185995(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185995(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185995(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185995(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.268 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.269 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.320 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.321 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185995(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10805853B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.869 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.870 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10805853B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/669334(String), 1572364800(Integer), US10805853B2(String), 1602518400(Integer), 1602518400(Integer), 美国(String), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), 19(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:45.906 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185996(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\3bbf61620c8341efad5d2e6d1720637d.png(String), 185996(Integer), 3bbf61620c8341efad5d2e6d1720637d.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.105 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal control method and mobile terminal(String), 移动终端控制方法及移动终端(String), US10805853B2(String), Embodiments of the present invention provide a mobile terminal control method and a mobile terminal. When initiating connection establishment to an access network element corresponding to a target cell, a mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, a measurement report of a measurement reporting event corresponding to indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell.(String), 本发明实施例提供一种移动终端控制方法及移动终端。 移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告,直接 向目标小区对应的接入网元发起连接建立,以便移动终端及时向目标小区对应的接入网元发起连接建立。(String), US16/669334(String), 1572364800(Integer), US10805853B2(String), 1602518400(Integer), 1602518400(Integer), 美国(String), 3(Integer), 4(Integer), 6(Integer), 26(Integer), CN101170830A | CN101742587A | CN102300274A | CN103188734A | CN103781136A | CN103797849A | CN1859784A | US20070224992A1 | US20110105119A1 | US20110269462A1 | US20130196659A1 | US20140045494A1 | US20140086173A1 | US20140112180A1 | US20140334371A1 | US20140349694A1 | US20150079991A1 | US20150181493A1 | US20150257066A1 | US20150257111A1 | US20160112918A1 | US20160286424A1 | US20170041841A1 | WO2006089456A1 | WO2013038052A1 | WO2013177778A1(String), \20230420\3bbf61620c8341efad5d2e6d1720637d.png(String), 19(Integer), 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 1. A method, comprising:receiving, by the mobile terminal from an access network element corresponding to a target cell, measurement configuration information by using a radio resource control (RRC) connection established between the mobile terminal and the access network element corresponding to the target cell;measuring, by the mobile terminal, the target cell according to the measurement configuration information, to obtain a measurement result of the target cell; andinitiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; orinitiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell when the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information.(String), 1.一种方法,包括:移动终端通过移动终端与目标小区对应的接入网元之间建立的无线资源控制(RadioResourceControl,无线资源控制)连接从目标小区对应的接入网元接收测量配置信息;移动终端根据测量配置信息对目标小区进行测量,得到目标小区的测量结果;和当移动终端根据测量结果确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网网元的连接建立;或者当移动终端根据测量结果生成测量报告时,移动终端发起到目标小区对应的接入网网元的连接建立,移动终端确定该测量报告为测量报告的测量报告指示信息对应的事件,其中,所述指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 2. The method according to claim 1, wherein initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell comprises:skipping, by the mobile terminal, sending, to the access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiating connection establishment to the access network element corresponding to the target cell.(String), 2.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 3. The method according to claim 1, wherein:the initiating, by the mobile terminal, of the connection establishment to an access network element corresponding to the target cell further comprises:initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and the indication information, that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, and when the mobile terminal determines that a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orinitiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell when the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information and determines that a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 3.根据权利要求1所述的方法,其中:移动终端发起与目标小区对应的接入网元的连接建立还包括:当移动终端根据测量结果和指示信息确定测量结果满足对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网网元的连接建立接收到指示信息,当移动终端确定测量结果满足指示信息对应的测量上报事件进入条件的时长达到预定时长;或者移动终端在生成该指示信息对应的测量报告事件的测量报告并确定该测量的测量报告后的时长时,发起到目标小区对应的接入网网元的连接建立指示信息对应的上报事件产生达到预定时长。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 4. The method according to claim 1, wherein initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell comprises:when the mobile terminal is in a discontinuous reception (DRX) state, initiating, by the mobile terminal, connection establishment to the access network element corresponding to the target cell.(String), 4.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端处于非连续接收(DRX)状态时,移动终端向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 5. The method according to claim 4, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 5.根据权利要求4所述的方法,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 6. The method according to claim 1, wherein initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell comprises:when a mobility state estimation of the mobile terminal is greater than or equal to a speed threshold, initiating, by the mobile terminal, the connection establishment to the access network element corresponding to the target cell.(String), 6.根据权利要求1所述的方法,其中移动终端向目标小区对应的接入网元发起连接建立包括:当移动终端的移动状态估计值大于或等于速度门限时,移动终端发起到目标小区对应的接入网元的连接建立。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 7. The method according to claim 1, further comprising:sending, by the mobile terminal, the mobility state estimation of the mobile terminal to the access network element corresponding to a serving cell, whereinthe indication information is sent after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold specified by the access network element corresponding to the serving cell.(String), 7.根据权利要求1所述的方法,还包括:移动终端向服务小区对应的接入网元发送移动终端的移动状态估计,其中在服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限后发送指示信息。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 8. The method according to claim 1, the initiating of the connection establishment comprises:correspondingly initiating, by the mobile terminal, a random access process to the target cell, and/or any one of the following processing:initiating, by the mobile terminal to the target cell, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 8.根据权利要求1所述的方法,发起连接建立包含:移动终端相应地发起对目标小区的随机接入过程,和/或以下任一处理:移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。9、一种配置在移动终端中的装置,包括:包括处理器可执行指令的存储介质;和耦合到存储介质的处理器,其中处理器可执行指令在由处理器执行时使装置:通过移动终端与目标小区对应的接入网元之间建立的无线资源控制(RadioResourceControl,无线资源控制)连接获取测量配置信息;根据测量配置信息对目标小区进行测量,得到目标小区的测量结果;和当测量结果满足指示信息对应的测量上报事件进入条件时,向目标小区对应的接入网元发起连接建立;或者当测量报告为指示信息对应的测量报告事件的测量报告时,向目标小区对应的接入网元发起连接建立,其中,指示信息用于指示向目标小区对应的接入网元发起连接建立如果测量报告事件的测量报告对应于指示信息,则目标小区。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 9. An apparatus configured in a mobile terminal, comprising:a storage medium comprising processor-executable instructions; anda processor coupled to the storage medium, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:obtain measurement configuration information by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to a target cell;measure the target cell according to the measurement configuration information, to obtain a measurement result of the target cell; andinitiate connection establishment to the access network element corresponding to the target cell when the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; orinitiate connection establishment to the access network element corresponding to the target cell when a measurement report is a measurement report of a measurement reporting event corresponding to indication information, wherein the indication information is used to instruct to initiate connection establishment to the access network element corresponding to the target cell if the measurement report of the measurement reporting event is corresponding to the indication information.(String), 10.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,向目标小区对应的接入网元发起连接建立。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 10. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:skip sending, to the access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiate connection establishment to the access network element corresponding to the target cell.(String), 11.根据权利要求9所述的装置,其中:为了发起与目标小区对应的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当测量结果满足指示信息对应的测量上报事件进入条件,且测量结果满足测量上报进入条件时,发起到目标小区对应接入网元的连接建立指示信息对应的事件达到预定时长;或者在生成指示信息对应的测量报告事件的测量报告时,以及生成指示信息对应的测量报告事件的测量报告后的时长达到a时,向目标小区对应的接入网元发起连接建立预定的持续时间。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 11. The apparatus according to claim 9, wherein:to initiate the connection establishment to the access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:initiate the connection establishment to the access network element corresponding to the target cell when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, and when a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration; orinitiate the connection establishment to the access network element corresponding to the target cell when generating the measurement report of the measurement reporting event corresponding to the indication information and a duration after the measurement report of the measurement reporting event corresponding to the indication information is generated reaches a predetermined duration.(String), 12.根据权利要求9所述的装置,其中为了发起与目标小区对应的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当装置处于非连续接收(DRX)状态时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 10(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 12. The apparatus according to claim 9, wherein to initiate the connection establishment to the access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when the apparatus is in a discontinuous reception (DRX) state, initiate connection establishment to the access network element corresponding to the target cell.(String), 13.根据权利要求12所述的装置,其中DRX状态为短周期DRX状态或长周期DRX状态。(String), 1(Integer), 11(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 13. The apparatus according to claim 12, wherein the DRX state is a short-cycle DRX state or a long-cycle DRX state.(String), 14.根据权利要求9所述的装置,其中为了启动到对应于目标小区的接入网络元件的连接建立,处理器可执行指令在由处理器执行时进一步使装置:当该装置的移动性状态估计大于或等于速度门限时,向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 14. The apparatus according to claim 9, wherein to initiate connection establishment to an access network element corresponding to the target cell, the processor-executable instructions, when executed by the processor, further cause the apparatus to:when a mobility state estimation of the apparatus is greater than or equal to a speed threshold, initiate connection establishment to the access network element corresponding to the target cell.(String), 15.根据权利要求9所述的装置,其中处理器可执行指令在由处理器执行时使装置:向服务小区对应的接入网元发送所述装置的移动性状态估计,其中,所述指示信息是在服务小区对应的接入网元确定移动性状态估计大于或等于速度门限后发送的.16.根据权利要求9所述的装置,其中为了启动连接建立,处理器可执行指令在由处理器执行时使装置:相应地发起对目标小区的随机接入过程,和/或以下任一过程:向目标小区发起、RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。(String), 1(Integer), 13(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 15. The apparatus according to claim 9, wherein the processor-executable instructions, when executed by the processor, cause the apparatus to:send the mobility state estimation of the apparatus to the access network element corresponding to a serving cell, wherein the indication information is sent after the access network element corresponding to the serving cell determines that the mobility state estimation is greater than or equal to a speed threshold.(String), 17.一种存储程序代码的非暂时性计算机可读介质,供移动终端用于无线通信,其中程序代码包括以下指令:通过移动终端与目标小区对应的接入网元之间建立的无线资源控制(RadioResourceControl,无线资源控制)连接获取测量配置信息;根据测量配置信息对目标小区进行测量,得到目标小区的测量结果;和当测量结果满足指示信息对应的测量上报事件进入条件时,向目标小区对应的接入网元发起连接建立;或者当测量报告事件的测量报告对应指示信息时,向目标小区对应的接入网元发起连接建立,该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立如果移动终端生成指示信息对应的测量报告事件的测量报告,则目标小区。(String), 1(Integer), 14(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 16. The apparatus according to claim 9, wherein to initiate connection establishment, the processor-executable instructions, when executed by the processor, cause the apparatus to:correspondingly initiate a random access process to the target cell, and/or any one of the following processes:initiate to the target cell, an RRC connection re-establishment process, a cell update process, an RRC connection establishment process, or a forward handover process.(String), 18.根据权利要求17所述的非暂时性计算机可读介质,其中向目标小区对应的接入网元发起连接建立包括:跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立。(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 17. A non-transitory computer readable medium storing program codes for use by a mobile terminal for wireless communication, wherein the program codes comprise instructions for:obtaining measurement configuration information by using a radio resource control (RRC) connection established between the mobile terminal and an access network element corresponding to the target cell;measuring a target cell according to the measurement configuration information, to obtain a measurement result of the target cell; andinitiating connection establishment to the access network element corresponding to the target cell when the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; orinitiating connection establishment to the access network element corresponding to the target cell when a measurement report of a measurement reporting event is corresponding to indication information, wherein the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information.(String), 19.根据权利要求17所述的非暂时性计算机可读介质,其中:向目标小区对应的接入网元发起连接建立还包括:当测量结果满足指示信息对应的测量上报事件的进入条件,且测量结果满足测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立指示信息对应的时间达到预定时长。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 18. The non-transitory computer readable medium according to claim 17, wherein initiating the connection establishment to the access network element corresponding to the target cell comprises:skipping sending, to the access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiating connection establishment to the access network element corresponding to the target cell.(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185996(Integer), 19. The non-transitory computer readable medium according to claim 17, wherein:the initiating of the connection establishment to the access network element corresponding to the target cell further comprises:initiating the connection establishment to the access network element corresponding to the target cell when the measurement result meets the entering condition of the measurement reporting event corresponding to indication information, and when a duration in which the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information reaches a predetermined duration.(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.582 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185996(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. application Ser. No. 16/180,651, filed on Nov. 5, 2018, which is a continuation of U.S. application Ser. No. 15/473,407, filed on Mar. 29, 2017, now U.S. Pat. No. 10,142,904, which is a continuation of International Application No. PCT/CN2014/088061, filed on Sep. 30, 2014. All of the afore-mentioned patent applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]Embodiments of the present invention relate to the field of communications technologies, and in particular, to a mobile terminal control method and a mobile terminal. BACKGROUND [0003]Currently, a mobile terminal and life of a user are closely related to each other. Usually, the user performs a communication service such as chat by using the mobile terminal while being on a vehicle such as a bus or a subway. In this case, the mobile terminal also moves at high speed as the vehicle moves. Because the mobile terminal moves at relatively high speed, in terms of a physical location, after the mobile terminal enters from a coverage area of a previous serving cell to a coverage area of a new cell, quality of a communication service provided by the serving cell is deteriorated. In addition, because the mobile terminal cannot establish a connection to the new cell in a timely manner either, mobility of the mobile terminal is affected. For example, because the quality of the communication service provided by the serving cell is deteriorated, and the mobile terminal cannot establish a connection to the new cell in a timely manner either, a communication service currently performed by the mobile terminal is interrupted. [0004]Specifically, before establishing a connection to an access network element corresponding to the new cell, the mobile terminal needs to send a measurement report about the new cell to an access network element corresponding to the serving cell. The mobile terminal may establish a connection to a new cell only when the mobile terminal receives an indication that connection establishment is allowed and that is sent by the access network element corresponding to the serving cell. It may be understood that, by using the prior art, the mobile terminal needs to wait for a relatively long time period from discovering the new cell to establishing a connection to the new cell, and cannot establish a connection to the new cell in a timely manner to obtain a communication service provided by the new cell. Particularly, when the mobile terminal is in a discontinuous reception (DRX) state, an interval at which the mobile terminal measures the serving cell and an interval at which the mobile terminal measures the new cell become longer. For example, when a DRX cycle is 320 ms, and the mobile terminal needs to spend 5 times the DRX cycle performing radio resource management (RRM) measurement on a neighboring cell, the mobile terminal needs to spend a longer time period from discovering a new cell to establishing a connection to the new cell, and mobility of the mobile terminal cannot meet a basic requirement of the user. Therefore, how the mobile terminal establishes a connection to a new cell in a timely manner is an important aspect of improving performance of the mobile terminal. SUMMARY [0005]Embodiments of the present invention provide a mobile terminal control method and a mobile terminal, so as to improve mobility of the mobile terminal. [0006]According to a first aspect, an embodiment of the present invention provides a processing method for establishing a connection to an access network element by a mobile terminal, and the method includes: [0007]measuring, by a mobile terminal, a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and [0008]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or [0009]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information; or [0010]initiating, by the mobile terminal, connection establishment to an access network element corresponding to the target cell when the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and when the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information, where [0011]the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. [0012]According to a second aspect, an embodiment of the present invention provides a method for controlling a DRX state of a mobile terminal, and the method includes: [0013]performing, by a mobile terminal, radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and [0014]when the mobile terminal determines, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold, [0015]starting, by the mobile terminal, a timer, and before the timer expires, transitioning the mobile terminal from a DRX state to a non-DRX state, or transitioning the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shortening a cycle of the DRX state. [0016]According to a third aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes: [0017]a measurement module, configured to measure a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell, where the measurement configuration information is obtained by the mobile terminal, by using a radio resource control RRC connection established between the mobile terminal and an access network element corresponding to a serving cell, from the access network element corresponding to the serving cell; and [0018]a processing module, configured to: initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information; or [0019]initiate connection establishment to an access network element corresponding to the target cell when generating a measurement report according to the measurement result, and determining that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the processing module generates the measurement report of the measurement reporting event corresponding to the indication information; or [0020]initiate connection establishment to an access network element corresponding to the target cell when determining, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the processing module generates a measurement report of the measurement reporting event corresponding to the indication information, where the indication information is used to instruct the processing module to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the processing module generates the measurement report of the measurement reporting event corresponding to the indication information, where [0021]the indication information is obtained by the processing module in advance from the access network element corresponding to the serving cell. [0022]According to a fourth aspect, an embodiment of the present invention provides a mobile terminal, and the mobile terminal includes: [0023]an obtaining module, configured to perform radio link monitoring RLM on a serving cell according to a downlink reference signal of the serving cell, so as to obtain quality of a downlink radio link of the serving cell; and [0024]a processing module, configured to: when determining, by estimating the quality of the downlink radio link, that a quantity of times in which consecutive out-of-synchronization indications occur in the downlink radio link reaches a preset threshold, [0025]start a timer, and before the timer expires, transition the mobile terminal from a DRX state to a non-DRX state, or transition the mobile terminal from a long-cycle DRX state to a short-cycle DRX state, or shorten a cycle of the DRX state. [0026]According to the mobile terminal control method and the mobile terminal that are provided in the embodiments of the present invention, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. BRIEF DESCRIPTION OF THE DRAWINGS [0027]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0028]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0029]FIG. 3 is a schematic diagram of an RRC connection establishment process according to Embodiment 2 of the present invention; [0030]FIG. 4 is a schematic diagram of an RRC connection re-establishment process according to Embodiment 2 of the present invention; [0031]FIG. 5 is a schematic diagram of a cell update process according to Embodiment 2 of the present invention; [0032]FIG. 6 is a schematic diagram of a contention-based random access process according to Embodiment 2 of the present invention; [0033]FIG. 7 is a schematic diagram of a non-contention-based random access channel process according to Embodiment 2 of the present invention; [0034]FIG. 8 is a schematic flowchart of Embodiment 3 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0035]FIG. 9A and FIG. 9B are a schematic flowchart of Embodiment 4 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0036]FIG. 10A and FIG. 10B are a schematic flowchart of Embodiment 5 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0037]FIG. 11A and FIG. 11B are a schematic flowchart of Embodiment 6 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0038]FIG. 12A to FIG. 12C are a schematic flowchart of Embodiment 7 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0039]FIG. 13A to FIG. 13C are a schematic flowchart of Embodiment 8 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0040]FIG. 14A to FIG. 14C are a schematic flowchart of Embodiment 9 of a processing method for establishing a connection to a cell by a mobile terminal according to the present invention; [0041]FIG. 15A to FIG. 15C are a schematic flowchart of Embodiment 10 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention; [0042]FIG. 16 is a schematic flowchart of Embodiment 1 of a method for controlling a DRX state of a mobile terminal according to the present invention; [0043]FIG. 17 is a schematic structural diagram of Embodiment 1 of a mobile terminal according to the present invention; [0044]FIG. 18 is a schematic structural diagram of Embodiment 2 of a mobile terminal according to the present invention; [0045]FIG. 19 is a schematic structural diagram of Embodiment 3 of a mobile terminal according to the present invention; [0046]FIG. 20 is a schematic structural diagram of Embodiment 4 of a mobile terminal according to the present invention; [0047]FIG. 21 is a schematic structural diagram of Embodiment 5 of a mobile terminal according to the present invention; and [0048]FIG. 22 is a schematic structural diagram of Embodiment 6 of a mobile terminal according to the present invention. DETAILED DESCRIPTION [0049]FIG. 1 is a schematic flowchart of Embodiment 1 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 1, this embodiment is executed by a mobile terminal, and specifically includes the following operations. [0050]S101. The mobile terminal measures a target cell according to measurement configuration information, so as to obtain a measurement result of the target cell. [0051]The mobile terminal establishes an RRC (radio resource control) connection to a serving cell, and the measurement configuration information is obtained by the mobile terminal, by using the RRC connection, from an access network element (which may be specifically a base station that manages the serving cell) corresponding to the serving cell. Specifically, the measurement configuration information includes a configuration about a measurement reporting event and the measurement reporting event may be specifically an event A3, an event A4, an event A5, or the like. [0052]Specifically, the mobile terminal performs RRM measurement on the target cell according to the measurement configuration information, so as to obtain an RRM measurement result. The target cell may be a neighboring cell of the serving cell, or may be a corresponding cell. When the target cell is a corresponding cell, the mobile terminal needs to obtain an identity of the corresponding cell from the serving cell before the mobile terminal performs measurement. [0053]S102. When the mobile terminal determines, according to the measurement result of the target cell and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0054]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0055]By performing S102, the mobile terminal skips generating a measurement report of the measurement reporting event corresponding to the indication information, skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0056]Alternatively, after performing S101, the mobile terminal chooses to perform S103 instead of S102. [0057]S103. When the mobile terminal generates a measurement report according to the measurement result, and the mobile terminal determines that the measurement report is a measurement report of a measurement reporting event corresponding to indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0058]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the mobile terminal generates the measurement report of the measurement reporting event corresponding to indication information. [0059]By performing S103, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0060]Alternatively, after performing S101, the mobile terminal chooses to perform S104 instead of S102 and 103. [0061]S104. When the mobile terminal determines, according to the measurement result and indication information, that the measurement result meets an entering condition of a measurement reporting event corresponding to the indication information, and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information, the mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0062]The indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates the measurement report of the measurement reporting event corresponding to the indication information. [0063]By performing S104, the mobile terminal skips sending, to the access network element corresponding to the serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and initiates connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0064]In any one operation of the foregoing S102, S103, or S104, the indication information is obtained by the mobile terminal in advance from the access network element corresponding to the serving cell. In one embodiment, the mobile terminal receives, by using the RRC connection, the indication information sent by the access network element corresponding to the serving cell. Specifically, the access network element corresponding to the serving cell may deliver the indication information while delivering the measurement configuration information to the mobile terminal, or may deliver the indication information to the mobile terminal before this embodiment is executed. In this embodiment, an example in which the measurement reporting event is the event A3 or the event A4 is used. When the measurement reporting event is specifically the event A3, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”. When the measurement reporting event is specifically the event A4, the entering condition of the measurement reporting event is: “Mn+Ofn+Ocn−Hys>Thresh”. Mn is the measurement result of the target cell, Ofn is a frequency specific offset of the target cell, and Ocn is a cell individual offset of the target cell. If the target cell is not configured with the cell individual offset, when the formulas are applied, a value of Ocn may be 0. Ms is a measurement result of the serving cell, Ofs is a frequency specific offset of the serving cell, Ocs is a cell individual offset of the serving cell, Hys is an event hysteresis parameter, Off is an event offset parameter, and Thresh is an event threshold parameter. Parameters such as Ofn, Ocn, Hys, Ofs, Ocs, and Off are obtained by the mobile terminal in advance. [0065]Specifically, in communication transmission, the indication information is specifically at least one piece of data. The at least one piece of data includes an identifier of the measurement reporting event. For example, if the at least one piece of data includes an identifier “A3”, it indicates that the measurement reporting event corresponding to the indication information is the event A3. Alternatively, the at least one piece of data is specifically a specific identifier. The specific identifier may be located in measurement configuration information, and is associated with the configuration about the measurement reporting event in the measurement configuration information. For example, if partial content of the measurement configuration information is a configuration about the event A3, and the specified identifier is associated with the configuration about the event A3 in the measurement configuration information, it may indicate that the measurement reporting event corresponding to the indication information is the event A3. [0066]In one embodiment, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0067]In one embodiment, the indication information may be specifically a direct re-establishment indication, a cell update indication, or a forward handover indication. [0068]In this embodiment, indication information is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if the mobile terminal generates a measurement report of a measurement reporting event corresponding to the indication information; or is used to instruct a mobile terminal to initiate connection establishment to an access network element corresponding to a target cell if a measurement result meets an entering condition of a measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. Therefore, when initiating connection establishment to the access network element corresponding to the target cell, the mobile terminal can at least skip sending, to an access network element corresponding to a serving cell, the measurement report of the measurement reporting event corresponding to the indication information, and directly initiate connection establishment to the access network element corresponding to the target cell, so that the mobile terminal can initiate, in a timely manner, connection establishment to the access network element corresponding to the target cell, and mobility of the mobile terminal is improved. [0069]FIG. 2 is a schematic flowchart of Embodiment 2 of a processing method for establishing a connection to an access network element by a mobile terminal according to the present invention. As shown in FIG. 2, on the basis of the embodiment shown in FIG. 1, this embodiment is described in a implementation manner, and specifically includes the following operations. [0070]S201. A mobile terminal receives measurement configuration information and indication information that are sent by an access network element corresponding to a serving cell. [0071]The measurement configuration information and the indication information may be sent, to the mobile terminal by using same signaling, by the access network element corresponding to the serving cell, or may be sent, to the mobile terminal by using different signaling, by the access network element corresponding to the serving cell. [0072]S202. The mobile terminal measures a target cell, so as to obtain a measurement result of the target cell. [0073]The operation is specifically described in S101. However, it should be noted that, in addition to being a newly discovered neighboring cell, the target cell may be a specified cell described in the S101, and may be specifically specified by the indication information. That is, if the indication information further carries a cell identity, a cell corresponding to the cell identity carried in the indication information is the target cell. [0074]S203. The mobile terminal determines whether the measurement result of the target cell meets an entering condition of a measurement reporting event corresponding to the indication information, and if yes, the mobile terminal performs S204, or if no, this embodiment ends. [0075]In one embodiment, in this embodiment, there is at least one piece of the indication information, and there is at least one measurement reporting event corresponding to the indication information. [0076]For example, if the mobile terminal receives two pieces of indication information in S201, one of the two pieces of indication information is corresponding to an event A3, and the other is corresponding to an event A4. When the measurement result obtained in S202 meets an entering condition of either measurement reporting event of the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S 204. [0077]Alternatively, if one piece of indication information is obtained in S201, and the indication information is corresponding to an event A3 and an event A4, when the measurement result obtained in S202 meets an entering condition of either the event A3 or the event A4, that is, when the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal performs the following S204. [0078]Alternatively, if the indication information obtained in S201 is corresponding to an event A3, when the measurement result obtained in S202 meets an entering condition of the event A3, the mobile terminal performs the following S204. That is, when Mn meets “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, the mobile terminal performs S204. However, when Mn meets “Mn+Ofn+Ocn−Hys>Thresh” but does not meet “Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”, this embodiment ends, that is, an entering condition that is of a measurement reporting event and is met by the measurement result is not the entering condition of the measurement reporting event corresponding to the indication information. [0079]It should be additionally noted that, if the indication information is used to instruct the mobile terminal to initiate connection establishment to an access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information, the mobile terminal may directly perform S205 after determining, by performing S203, that the measurement result of the target cell meets the entering condition of the measurement reporting event corresponding to the indication information. However, to ensure that a control effect, on the mobile terminal, of a network-side device in a communications network is not affected and to give consideration to mobility of the mobile terminal as well, in this embodiment, preferably, the indication information is used to instruct the mobile terminal to initiate connection establishment to the access network element corresponding to the target cell if the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information and the mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. The mobile terminal performs S204 and S205 in sequence after determining, by performing S203, that the measurement result meets the entering condition of the measurement reporting event corresponding to the indication information. [0080]S204. The mobile terminal generates a measurement report of the measurement reporting event corresponding to the indication information. [0081]S205. The mobile terminal initiates connection establishment to an access network element corresponding to the target cell. [0082]The connection establis(String), 相关申请的交叉引用 [0001] 该申请是美国申请 Ser. 第 16/180,651 号,于 2018 年 11 月 5 日提交,是美国申请序列号的延续。 第 15/473,407 号,2017 年 3 月 29 日提交,现为美国专利。 美国专利第 10,142,904 号是 2014 年 9 月 30 日提交的国际申请号 PCT/CN2014/088061 的延续。所有上述专利申请均通过引用整体并入本文。 技术领域 [0002] 本发明实施例涉及通信技术领域,尤其涉及一种移动终端控制方法及移动终端。 背景 [0003] 目前,移动终端与用户的生活息息相关。 通常,用户在诸如公共汽车或地铁的交通工具上通过使用移动终端进行诸如聊天的通信服务。 在这种情况下,移动终端也随着车辆的移动而高速移动。 由于移动终端移动速度较高,从物理位置上来说,移动终端从上一个服务小区的覆盖范围进入到新的小区覆盖范围后,服务小区提供的通信服务质量 恶化。 另外,由于移动终端也无法及时与新小区建立连接,影响了移动终端的移动性。 例如,由于服务小区提供的通信服务质量下降,移动终端也无法及时建立到新小区的连接,导致移动终端当前进行的通信服务中断。 [0004] 具体地,移动终端在与新小区对应的接入网元建立连接之前,需要向服务小区对应的接入网元发送关于新小区的测量报告。 只有当移动终端接收到服务小区对应的接入网元发送的允许建立连接的指示时,移动终端才可以建立到新小区的连接。 可以理解的是,采用现有技术,移动终端从发现新小区到与新小区建立连接需要等待较长的时间,不能及时与新小区建立连接。 获得新小区提供的通信服务的方式。 特别地,当移动终端处于非连续接收(DRX)状态时,移动终端测量服务小区的间隔和移动终端测量新小区的间隔变长。 例如,当DRX周期为320ms时,移动终端需要花费5倍的DRX周期对邻区进行无线资源管理(Radio Resource Management,无线资源管理)测量,则移动终端需要花费更长的时间才能发现新的小区。 小区与新小区建立连接,移动终端的移动性不能满足用户的基本需求。 因此,移动终端如何及时建立与新小区的连接是提高移动终端性能的重要方面。 概括 [0005] 本发明实施例提供一种移动终端控制方法及移动终端,以提高移动终端的移动性。 [0006] 第一方面,本发明实施例提供了一种移动终端与接入网元建立连接的处理方法,该方法包括: [0007] 移动终端根据测量配置信息对目标小区进行测量,以获取目标小区的测量结果,其中,移动终端获取测量配置信息,使用之间建立的无线资源控制RRC连接 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和 [0008]当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立; 或者 [0009] 当移动终端根据测量结果生成测量报告时,移动终端发起到目标小区对应的接入网元的连接建立,移动终端确定该测量报告为测量报告的测量报告 指示信息对应的事件,该指示信息用于在移动终端生成该指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立; 或者 [0010] 当移动终端根据测量结果和指示信息确定测量结果满足目标小区对应的测量上报事件的进入条件时,移动终端发起到目标小区对应的接入网元的连接建立 指示信息,当移动终端生成该指示信息对应的测量报告事件的测量报告时,该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,如果 测量结果满足指示信息对应的测量上报事件的进入条件,移动终端生成指示信息对应的测量上报事件的测量报告,其中 [0011] 指示信息是移动终端预先从服务小区对应的接入网元获取的。 [0012] 第二方面,本发明实施例提供了一种移动终端的DRX状态控制方法,该方法包括: [0013] 移动终端根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,以获取服务小区的下行无线链路质量; 和 [0014] 当移动终端通过估计下行无线链路质量,确定下行无线链路连续出现失步指示的次数达到预设门限时, [0015] 移动终端启动定时器,在定时器超时之前,将移动终端从DRX状态转变为非DRX状态,或者将移动终端从长周期DRX状态转变为短周期DRX状态 ,或者缩短DRX状态的周期。 [0016] 第三方面,本发明实施例提供了一种移动终端,该移动终端包括: [0017] 测量模块,用于根据测量配置信息对目标小区进行测量,以获取所述目标小区的测量结果,所述测量配置信息为所述移动终端通过与所述目标小区之间建立的无线资源控制RRC连接获得的 移动终端和服务小区对应的接入网元,来自服务小区对应的接入网元; 和 [0018]处理模块,用于在根据所述测量结果和指示信息确定所述测量结果满足所述指示信息对应的测量上报事件的进入条件时,发起到所述目标小区对应的接入网元的连接建立 , 该指示信息用于指示处理模块如果测量结果满足该指示信息对应的测量上报事件的进入条件,则向目标小区对应的接入网元发起连接建立; 或者 [0019] 根据测量结果生成测量报告时,向目标小区对应的接入网元发起连接建立,确定该测量报告为指示信息对应的测量报告事件的测量报告,其中使用该指示信息 若处理模块生成指示信息对应的测量上报事件的测量报告,则指示处理模块向目标小区对应的接入网元发起连接建立; 或者 [0020] 当根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,发起到目标小区对应的接入网元的连接建立,处理模块生成 指示信息对应的测量上报事件的测量报告,指示信息用于在测量结果满足测量上报进入条件时,指示处理模块向目标小区对应的接入网元发起连接建立 指示信息对应的事件,处理模块生成指示信息对应的测量报告事件的测量报告,其中 [0021] 指示信息由处理模块预先从服务小区对应的接入网元获取。 [0022] 第四方面,本发明实施例提供一种移动终端,该移动终端包括: [0023] 获取模块,用于根据服务小区的下行参考信号对服务小区进行无线链路监测RLM,获取服务小区的下行无线链路质量; 和 [0024] 处理模块,用于通过对所述下行无线链路质量的估计,确定所述下行无线链路连续出现失步指示的次数达到预设门限时, [0025] 启动定时器,在定时器超时前,将移动终端从DRX状态转移到非DRX状态,或者将移动终端从长周期DRX状态转移到短周期DRX状态,或者缩短周期 DRX 状态。 [0026]本发明实施例提供的移动终端控制方法及移动终端,通过指示信息指示移动终端在测量结果满足时,向目标小区对应的接入网元发起连接建立。 指示信息对应的测量上报事件的进入条件; 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 附图的简要说明 [0027] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图; [0028] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图; [0029] 图3为本发明实施例二的RRC连接建立过程示意图; [0030] 图4为本发明实施例二的RRC连接重建过程示意图; [0031] 图5为本发明实施例二的小区更新过程示意图; [0032] 图6为本发明实施例二的基于竞争的随机接入过程的示意图; [0033] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图; [0034] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图; [0035] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图; [0036] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图; [0037] 图11A和图11B为本发明移动终端与小区建立连接的处理方法实施例六的流程示意图; [0038] 图12A至图12C为本发明移动终端与小区建立连接的处理方法实施例七的流程示意图; [0039] 图13A至图13C为本发明移动终端与小区建立连接的处理方法实施例八的流程示意图; [0040] 图14A至图14C为本发明移动终端与小区建立连接的处理方法实施例九的流程示意图; [0041]图15A至图15C为本发明移动终端与接入网元建立连接的处理方法实施例十的流程示意图; [0042] 图16为本发明移动终端的DRX状态控制方法实施例一的流程示意图; [0043] 图17为本发明移动终端实施例一的结构示意图; [0044] 图18为本发明移动终端实施例二的结构示意图; [0045] 图19为本发明移动终端实施例三的结构示意图; [0046] 图20为本发明移动终端实施例四的结构示意图; [0047] 图21为本发明移动终端实施例五的结构示意图; 和 [0048] 图22为本发明移动终端实施例六的结构示意图。 详细说明 [0049] 图1为本发明移动终端与接入网元建立连接的处理方法实施例一的流程示意图。 如图1所示,本实施例的执行主体为移动终端,具体包括以下操作。 [0050] 小号 101 . 移动终端根据测量配置信息对目标小区进行测量,以获得目标小区的测量结果。 [0051] 移动终端与服务小区建立RRC(无线资源控制)连接,移动终端通过RRC连接从接入网元(具体可以是管理基站的基站)获取测量配置信息 服务小区)对应于服务小区。 具体地,测量配置信息包括关于测量上报事件的配置,测量上报事件具体可以为事件A3、事件A4、事件A5等。 [0052] 具体的,移动终端根据测量配置信息对目标小区进行RRM测量,得到RRM测量结果。 目标小区可以是服务小区的邻区,也可以是对应小区。 当目标小区为对应小区时,移动终端在进行测量前需要从服务小区获取对应小区的标识。 [0053] 小号 102 . 当移动终端根据目标小区的测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立 到目标单元格。 [0054] 该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0055] 通过执行 S 102 , 移动终端跳过生成指示信息对应的测量报告事件的测量报告, 跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告, 发起 与目标小区对应的接入网元建立连接,使得移动终端能够及时发起与目标小区对应的接入网元的连接建立,提高了移动终端的移动性。 [0056] 或者,在执行 S 之后 101 , 移动端选择执行S 103 而不是S 102 . [0057] 小号 103. 当移动终端根据测量结果生成测量报告,且移动终端确定该测量报告为指示信息对应的测量报告事件的测量报告时,移动终端向指示信息对应的接入网元发起连接建立 目标细胞。 [0058] 该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 [0059] 通过执行 S 103 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0060] 或者,在执行 S 之后 101 , 移动端选择执行S 104 而不是S 102 和 103 . [0061] 小号 104 . 当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端生成对应的测量上报事件的测量报告。 指示信息,移动终端向目标小区对应的接入网元发起连接建立。 [0062] 该指示信息用于指示移动终端在测量结果满足指示信息对应的测量报告事件的进入条件并生成测量报告时,向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0063] 通过执行 S 104 ,移动终端跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,并向目标小区对应的接入网元发起连接建立,使得 移动终端可以及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0064] 在上述 S 的任何一个操作中 102 , 小号 103 , 或小号 104,该指示信息是移动终端预先从服务小区对应的接入网元获取的。 在一个实施例中,移动终端通过RRC连接接收服务小区对应的接入网元发送的指示信息。 具体地,服务小区对应的接入网元可以在向移动终端下发测量配置信息的同时下发指示信息,也可以在本实施例执行前向移动终端下发指示信息。 本实施例以测量上报事件为事件A3或事件A4为例。 当测量上报事件具体为事件A3时,测量上报事件的进入条件为:“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”。 当测量上报事件具体为事件A4时,测量上报事件的进入条件为:“Mn+Ofn+Ocn-Hys>Thresh”。 Mn是目标小区的测量结果,Ofn是目标小区的频率特定偏移,Ocn是目标小区的小区个体偏移。 如果目标小区没有配置小区个体偏移,当应用公式时,Ocn的值可以为0。Ms是服务小区的测量结果,Ofs是服务小区的频率特定偏移,Ocs是 服务小区的小区个体偏移,Hys为事件迟滞参数,Off为事件偏移参数,Thresh为事件阈值参数。 Ofn、Ocn、Hys、Ofs、Ocs、Off等参数由移动终端预先获取。 [0065] 具体地,在通信传输中,指示信息具体为至少一个数据。 至少一个数据包括测量报告事件的标识。 例如,若该至少一个数据中包含标识“A3”,则表明该指示信息对应的测量上报事件为事件A3。 或者,所述至少一个数据具体为特定标识。 特定标识可以位于测量配置信息中,与测量配置信息中关于测量上报事件的配置相关联。 例如,如果测量配置信息的部分内容是关于事件A3的配置,并且指定标识与测量配置信息中关于事件A3的配置相关联,则可以指示该指示对应的测量上报事件 信息是事件A3。 [0066] 在一实施例中,所述指示信息至少有一条,所述指示信息对应的测量上报事件至少有一个。 [0067] 在一个实施例中,该指示信息具体可以为直接重建指示、小区更新指示或前向切换指示。 [0068]本实施例中,指示信息用于当测量结果满足指示信息对应的测量上报事件的进入条件时,指示移动终端向目标小区对应的接入网元发起连接建立。 或者,用于如果移动终端生成指示信息对应的测量报告事件的测量报告,则指示移动终端发起到目标小区对应的接入网元的连接建立; 或者,如果测量结果满足指示信息对应的测量报告事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成该测量报告。 该指示信息对应的测量上报事件。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,至少可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 ,直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,移动终端的移动性是 改善。 [0069] 图2为本发明移动终端与接入网元建立连接的处理方法实施例二的流程示意图。 如图2所示,在图1所示实施例的基础上,对本实施例的实施方式进行描述,具体包括以下操作。 [0070] 小号 201 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0071] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0072] 小号 202 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0073] 该操作在 S 中具体描述 101 . 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0074] 小号 203 . 移动终端判断目标小区的测量结果是否满足该指示信息对应的测量上报事件的进入条件,如果满足,移动终端执行S 204 ,否则,本实施例结束。 [0075] 在一个实施例中,在本实施例中,所述指示信息至少有一条,所述指示信息对应的测量上报事件至少有一个。 [0076] 例如,如果移动终端在S中接收到两条指示信息 201 ,两条指示信息之一对应事件A3,另一条对应事件A4。 当在 S 中获得的测量结果 202 满足事件A3或事件A4中任一测量上报事件的进入条件,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行以下S 204 . [0077] 或者,若在S中获取到一条指示信息 201,指示信息对应事件A3和事件A4,当S中得到的测量结果为 202 满足A3事件或A4事件的进入条件,即当测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端执行以下S 204 . [0078] 或者,若S中获取的指示信息 201 对应一个事件A3,当S中得到的测量结果 202 满足事件A3的进入条件,移动终端执行以下S 204 . 即当Mn满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,移动终端执行S 204 . 而当Mn满足“Mn+Ofn+Ocn-Hys>Thresh”但不满足“Mn+Ofn+Ocn-Hys>Ms+Ofs+Ocs+Off”时,本实施例结束,即进入条件为 测量上报事件的条件,测量结果满足的不是该指示信息对应的测量上报事件的进入条件。 [0079] 还需要说明的是,如果该指示信息用于指示移动终端向目标小区对应的接入网元发起连接建立,则测量结果满足该指示信息对应的测量上报事件的进入条件 ,移动终端可以直接执行S 205 确定后,通过执行 S 203 ,则目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 但是,为保证通信网络中网络侧设备对移动终端的控制效果不受影响,同时兼顾移动终端的移动性,本实施例中,优选的,所述指示信息为 用于如果测量结果满足指示信息对应的测量上报事件的进入条件,则指示移动终端向目标小区对应的接入网元发起连接建立,移动终端生成测量上报的测量报告 指示信息对应的事件。 移动终端执行S 204 和小号 205 确定后依次执行S 203 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0080] 小号 204 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0081] 小号 205 . 移动终端向目标小区对应的接入网元发起连接建立。 [0082] S中的连接建立 205 具体包括: [0083] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理: [0084] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 [0085] 图3为本发明实施例二的RRC连接建立过程示意图。 如图3所示,具体流程包括以下操作: [0086] C 11 . 移动终端向目标小区对应的接入网元发送RRC连接建立请求。 [0087] C 12 . 移动终端接收目标小区对应的接入网元发送的RRC连接建立消息。 [0088] C 13 . 移动终端向目标小区对应的接入网元发送RRC连接建立完成消息。 [0089] 图4为本发明实施例二的RRC连接重建过程示意图。 如图4所示,具体过程包括以下操作: [0090] C21 . 移动终端向目标小区对应的接入网元发送RRC连接重建请求。 [0091] C 22 . 移动终端接收目标小区对应的接入网元发送的RRC连接重建消息。 [0092] C 23 . 移动终端向目标小区对应的接入网元发送RRC连接重建完成消息。 [0093] 图5为本发明实施例二的小区更新过程示意图。 如图5所示,具体过程包括以下操作: [0094] C 31 . 移动终端向目标小区对应的接入网元发送小区更新请求。 [0095] C 32 . 移动终端接收目标小区对应的接入网元发送的小区更新消息。 [0096] C 33 . 移动终端向目标小区对应的接入网元发送小区更新完成消息。 [0097] C 33 为可选操作,可以根据实际网络情况执行也可以不执行。 [0098] 图6为本发明实施例二的基于竞争的随机接入信道过程示意图。 如图6所示,具体过程包括以下操作: [0099] C 41 . 移动终端向目标小区对应的接入网元发送消息1。 消息1具体为“Random Access Preamble”。 [0100] C 42 . 移动终端接收目标小区对应的接入网元发送的消息2。 消息2具体为“Random Access Response”。 [0101] C 43 . 移动终端向目标小区对应的接入网元发送消息3。 消息3具体为“Scheduled Transmission”。 [0102] C 44 . 移动终端接收目标小区对应的接入网元发送的消息4。 消息4具体为“Contention Resolution”。 [0103] 图7为本发明实施例二的基于非竞争的随机接入信道过程的示意图。 如图7所示,具体过程包括以下操作: [0104] C 51 . 移动终端接收目标小区对应的接入网元发送的消息0。 消息 0 具体是“RA Preamble assignment”。 [0105] C 52 . 移动终端向目标小区对应的接入网元发送消息1。 消息1具体为“Random Access Preamble”。 [0106] C 53 . 移动终端接收目标小区对应的接入网元发送的消息2。 消息2具体为“Random Access Response”。 [0107] 还应该注意的是,当确定时,通过执行 S 203 , 本实施例结束, 表示移动终端不再继续执行S 204 和小号 205 ,但继续按照现有技术进行其他操作。 例如,若指示信息对应的测量上报事件为事件A3,但移动终端在S中判断 203目标小区的测量结果不满足事件A3的进入条件,但满足事件A4的进入条件,则移动终端根据满足进入条件的测量结果生成事件A4的测量报告 事件A4; 向服务小区对应的接入网元发送事件A4的测量报告; 等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到服务小区对应的接入网元下发给移动终端的允许建立连接的指示时,移动终端才建立到目标小区的连接。 [0108] 即,现有技术中,当目标小区的测量结果满足测量上报事件的进入条件时,移动终端首先需要生成测量报告,并将测量报告上报给目标小区对应的接入网元。 服务小区,然后需要等待服务小区对应的接入网元下发允许建立连接的指示。 在此过程中,移动终端需要花费较长的时间周期,不利于提高移动终端与目标小区对应的接入网元建立连接的效率。 但是,在本说明书中,假设目标小区的测量结果满足指示信息对应的测量报告事件的进入条件,移动终端生成指示信息对应的测量报告事件的测量报告,则 移动终端能够在移动终端与目标小区之间建立连接,提高了移动终端与目标小区对应的接入网元建立连接的效率,提高了移动终端的移动性。 [0109] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立,并且移动终端生成 指示信息对应的测量上报事件的测量报告。 因此,移动终端在向目标小区对应的接入网元发起连接建立时,可以跳过向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告,以及 直接向目标小区对应的接入网元发起连接建立,使得移动终端能够及时向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0110] 图8为本发明移动终端与接入网元建立连接的处理方法实施例三的流程示意图。 如图8所示,在图1所示实施例的基础上,对本实施例的一个优选实施方式进行说明,具体包括以下操作。 [0111] 小号 301 . 移动终端接收服务小区对应的接入网元发送的测量配置信息和指示信息。 [0112] 测量配置信息和指示信息可以由服务小区对应的接入网网元通过相同的信令发送给移动终端,也可以由接入网通过不同的信令发送给移动终端。 服务小区对应的元素。 [0113] 小号 302 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0114] 该操作在 S 中具体描述 101. 但需要注意的是,目标小区除了是新发现的邻区外,还可以是S中描述的指定小区。 101 , 可以由指示信息具体指定。 即,如果指示信息中还携带有小区标识,则指示信息中携带的小区标识对应的小区为目标小区。 [0115] 小号 303 . 移动终端根据测量结果生成测量报告。 [0116] 小号 304 . 移动终端判断该测量报告是否为该指示信息对应的测量报告事件的测量报告,如果是,则移动终端执行S 305 ,否则,本实施例结束。 [0117] 在本实施例中,该指示信息用于在移动终端生成指示信息对应的测量报告事件的测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立。 前提是在 S 中获得的测量结果 302 满足测量报告事件的进入条件,在S中生成测量报告 303 . 可以理解,当S中的测量结果满足测量上报事件的进入条件时 302 不是指示信息对应的测量报告事件的进入条件,S中生成的测量报告 303 也不是该指示信息对应的测量上报事件的测量报告。 [0118] 然而,如果移动终端确定,通过执行S 304 , S 中的测量报告 303 为指示信息对应的测量报告事件的测量报告,即当移动终端根据指示信息确定移动终端生成指示信息对应的测量报告事件的测量报告时,移动终端 终端可以不向服务小区对应的接入网元发送该指示信息对应的测量报告事件的测量报告,直接执行S 305 . [0119] 在一个实施例中,在本实施例中,所述指示信息至少有一条,所述指示信息对应的测量上报事件至少有一个。 [0120] 例如,如果移动终端在S中接收到两条指示信息 301 , 两条指示信息之一对应事件A3, 另一条对应事件A4, 当S中得到的测量结果 302 满足事件A3或事件A4中任一测量报告事件的进入条件,S中生成的测量报告 303 必然是指示信息对应的测量上报事件的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0121] 或者,若在S中获取到一条指示信息 301 ,指示信息对应事件A3和事件A4,当S中得到的测量结果为 302 满足事件A3或事件A4的进入条件,S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . [0122] 或者,若S中获取的指示信息 301 对应一个事件A3,当S中得到的测量结果 302满足事件A3的进入条件,S中生成的测量报告 303 必然是指示信息对应的测量报告。 确定时,通过执行 S 304 , 移动终端生成该指示信息对应的测量报告事件的测量报告, 移动终端直接执行以下S 305 . 然而,在一个实施例中,如果在S中获得的指示信息 301 对应事件A3,但是S中得到的测量结果 302 满足事件A4的进入条件,S中生成的测量报告 303 不是指示信息对应的测量报告,而是事件A4的测量报告。 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 即当Mn满足“Mn+Ofn+Ocn−Hys>Thresh”但不满足“Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off”时,S中生成的测量报告 303 不是指示信息对应的测量报告。 当移动终端确定时,通过执行S 304 ,移动终端不生成该指示信息对应的测量报告事件的测量报告,本实施例结束。 [0123] 小号 305 . 移动终端向目标小区对应的接入网元发起连接建立。 [0124] 移动终端向目标小区发起随机接入过程,和/或进行以下任一处理: [0125] 移动终端向目标小区发起RRC连接重建过程、小区更新过程、RRC连接建立过程或前向切换过程。 具体可以参考图3至图7所示的信令流程。 [0126] 本实施例中,指示信息用于指示移动终端跳过,如果移动终端生成该指示信息对应的测量报告事件的测量报告,则向服务小区对应的接入网元发送该测量 上报指示信息对应的测量上报事件。 因此,移动终端可以直接向目标小区对应的接入网元发起连接建立,提高了移动终端的移动性。 [0127] 图9A和图9B为本发明移动终端与接入网元建立连接的处理方法实施例四的流程示意图。 如图9A和图9B所示,本实施例在图1所示实施例的基础上进行进一步说明,具体包括以下操作。 [0128] 小号 401 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0129] 移动状态估计(Mobility State Estimation,MSE)是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0130] 小号 402 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0131] 小号 403 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0132]该指示信息用于指示移动终端在测量结果满足该指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 [0133] 小号 404 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0134] 当服务小区对应的接入网元学习时,通过执行S 402 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 403 向移动终端下发指示信息。 [0135] 测量配置信息和指示信息可以同时下发,即S 403 和小号 404 通过使用相同的信令来实现。 在一个实施例中,S 404 可以在 S 之前执行 403 ,或者可以在 S 之前或同时执行 402 ,或者可以在 S 之前或同时执行 401 . 例如,首先,移动终端接收到测量配置信息,然后,当确定移动终端在高速移动时,服务小区对应的接入网元下发指示信息。 此外,在一个实施例中,S 401 和小号 402 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0136] 小号 405 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0137] 在移动终端接收到指示信息之前,移动终端根据S-Measure发现目标小区。 即移动终端只有在获知服务小区的服务质量低于预设值时才对邻区进行RRM测量,以发现测量结果满足测量上报事件的目标小区。 但在本实施例中,移动终端接收到指示信息后,可以忽略S-Measure,即移动终端可以随时对邻区进行RRM测量,无需等到服务 服务小区的质量低于预设值,从而及时判断目标小区的测量结果是否满足测量上报事件的进入条件,从而进一步提高移动终端的移动性 改善。 [0138] 小号 406 . 移动终端确定该测量结果满足该指示信息对应的测量上报事件的进入条件。 [0139] 可以理解的是,如果移动终端与目标小区建立连接,则移动终端在任意时刻确定目标小区的测量结果满足该指示信息对应的测量上报事件的进入条件。 ,弱化了网络侧设备(如基站或基站控制器)对移动终端的控制。 但是,移动终端处于短周期DRX状态或长周期DRX状态时,对移动性的影响较大。 因此,在一个实施例中,当本实施例的移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示与目标小区建立连接,即 , 移动终端还需要执行以下S 407 执行 S 后 406 . [0140] 小号 407 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 409 或 408 ,或者如果否,则执行 S410 . [0141] DRX状态为短周期DRX状态或长周期DRX状态。 [0142] 现有技术中,移动终端处于休眠状态的时长也会影响移动终端的移动性。 另外,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端处于休眠状态的时间较长,对移动终端的移动性影响更为严重。 . 而本实施例中,当移动终端处于短周期DRX状态或长周期DRX状态时,移动终端根据指示信息的指示及时建立到目标小区的连接,以及 移动终端的移动性不受移动终端的短周期DRX状态或长周期DRX状态的影响。 [0143] 小号 408 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 409 ,或者如果是,则执行 S 410 . [0144] 当移动终端位于服务小区和目标小区的临界区域时,如果移动终端的移动速度较低,则移动终端更容易发生目标小区和服务小区之间的“乒乓切换”。 为了避免发生乒乓切换的情况,优选地,S 408 需要执行。 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 409 . [0145] 另外,移动终端指定的速度门限和服务小区对应的接入网元指定的速度门限可以相同,也可以不同。 另外,移动终端指定的速度门限可以由服务小区对应的接入网元为移动终端配置,或者在通信协议中指定,例如,移动终端的速度门限为 高机动状态的速度。 [0146] 此外,S 407 和小号 408 为可选操作,即本实施例在实际应用中实现时,移动终端可以选择执行S 407 和/或 408 执行 S 后 406 , 以及执行 S 的序列 407 和小号 408 不受限制。 在这个实施例中,一个例子中 S 408 在 S 之后执行 407 使用确定移动终端处于DRX状态。 [0147] 小号 409 . 移动终端向目标小区对应的接入网元发起连接建立。 [0148]本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件时,向目标小区对应的接入网元发起连接建立。 因此,当移动终端根据测量结果和指示信息确定测量结果满足指示信息对应的测量上报事件的进入条件时,移动终端向对应的接入网元发起连接建立。 目标细胞。 即,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的进入条件后,可以不生成该指示信息对应的测量上报事件的测量报告,不发送 , 向服务小区对应的接入网元, 指示信息对应的测量报告事件的测量报告, 向目标小区对应的接入网元发起连接建立, 使得移动终端可以发起, 在 及时与目标小区对应的接入网元建立连接,提高移动终端的移动性。 [0149] 小号 410 . 移动终端生成指示信息对应的测量报告事件的测量报告,并向服务小区对应的接入网元发送指示信息对应的测量报告事件的测量报告。 [0150] 在本实施例中,即使移动终端接收到指示信息,并且目标小区的测量结果满足该指示信息对应的测量报告事件的进入条件,移动终端也可以根据S中的判断结果进行选择。 407 和/或 408 ,应用指示信息(即,执行S 409 ). 或者,移动终端根据S中的判断结果进行选择 407 和/或 408 , 不应用指示信息; 仍然按照现有技术与目标小区对应的接入网元建立连接,即执行S 410 ; 然后,等待服务小区对应的接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0151] 本实施例中,移动终端根据目标小区的测量结果确定该测量结果满足指示信息对应的测量上报事件的进入条件后,根据该指示信息的指示,移动终端可以跳过生成 指示信息对应的测量上报事件的测量报告, 并跳过向服务小区对应的接入网元发送指示信息对应的测量上报事件的测量报告, 使得移动终端可以直接 向目标小区对应的接入网元发起连接建立,提高移动终端的移动性。 [0152] 图10A和图10B为本发明移动终端与小区建立连接的处理方法实施例五的流程示意图。 如图10A和图10B所示,在图1或图2所示实施例的基础上,在一个优选的实施方式中,本实施例具体包括以下操作。 [0153] 小号 501 . 移动终端向服务小区对应的接入网元发送移动终端的移动性状态估计。 [0154]移动状态估计是移动终端在当前时刻获得的移动终端的移动状态。 例如,当移动终端随着用户所在的车辆移动时,移动终端可以获知移动终端是否处于高移动状态。 当移动终端处于高移动性状态时,为了保证移动终端的移动性,移动终端需要将移动终端的移动性状态估计发送给服务小区对应的接入网元。 [0155] 小号 502 . 服务小区对应的接入网元确定移动性状态估计大于或等于服务小区对应的接入网元指定的速度门限。 [0156] 小号 503 . 移动终端接收服务小区对应的接入网元发送的指示信息。 [0157] 该指示信息用于当测量结果满足该指示信息对应的测量报告事件的进入条件并生成测量报告时,指示移动终端向目标小区对应的接入网元发起连接建立 指示信息对应的测量上报事件的名称。 [0158] 小号 504 . 移动终端接收服务小区对应的接入网元发送的测量配置信息。 [0159] 当服务小区对应的接入网元学习时,通过执行S 502 , 移动终端当前处于高速移动状态, 如果移动终端仍然使用现有技术的方法建立与目标小区对应的接入网元的连接, 则影响移动终端的移动性。 因此,为保证移动终端的移动性,服务小区对应的接入网元执行S 503 向移动终端下发指示信息。 [0160] 测量配置信息和指示信息可以同时下发,即S 503 和小号 504 通过使用相同的信令来实现。 在一个实施例中,S 504 可以在 S 之前执行 503 ,或者可以在 S 之前或同时执行 502 ,或者可以在 S 之前或同时执行 501 . 例如,首先,移动终端接收到测量配置信息,然后,接入网元在确定移动终端高速移动时,下发指示信息。 此外,在一个实施例中,S 501 和小号 502 不进行,即接入网元向移动终端下发指示信息不受移动终端移动速度的影响。 [0161] 小号 505 . 移动终端对目标小区进行测量,以获得目标小区的测量结果。 [0162] 小号 506 . 移动终端判断测量结果是否满足指示信息对应的测量上报事件的进入条件,如果满足,则执行S 507 ,或者如果否,则执行 S 511 . [0163] 本实施例中,指示信息用于指示移动终端在测量结果满足指示信息对应的测量上报事件的进入条件且移动终端向目标小区对应的接入网元发起连接建立时。 生成指示信息对应的测量报告事件的测量报告。 因此,本实施例中的移动终端通过执行S来确定 506 ,则测量结果满足指示信息对应的测量上报事件的进入条件。 [0164]在一个实施例中,若测量结果既不满足指示信息对应的测量上报事件的进入条件,也不满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件, 本实施例结束,即移动终端不再进行以下操作。 [0165] 但是,若测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件, 在该实施例中,根据现有技术,S 511 执行和小号 512 随后执行。 图9以测量结果不满足指示信息对应的测量上报事件的进入条件,但满足与指示信息对应的测量上报事件的进入条件不同的测量上报事件的进入条件为例 指示信息。 [0166] 小号 507 . 移动终端生成指示信息对应的测量报告事件的测量报告。 [0167] 小号 508 . 移动终端判断移动终端是否处于DRX状态,如果是,则执行S 510 或 509 ,或者如果否,则执行 S 512 . [0168] DRX状态为短周期DRX状态或长周期DRX状态。 [0169] 小号 509 . 移动终端判断移动终端的移动状态估计是否小于移动终端指定的速度阈值,若否,则执行S 510 ,或者如果是,则执行 S 512 . [0170] 即,当移动终端确定移动终端的移动状态估计大于或等于移动终端指定的速度阈值时,移动终端应用该指示信息,即执行如下S 510 . [0171] 小号 508 和小号 509 为可选操作,即本实施例在实际应用中实现时,移动终端可以选择执行S 508 和/或 509 执行 S 后 507 , 以及执行 S 的序列 508 和小号 509 不受限制。 本实施例以移动终端继续执行S为例 509 执行 S 后 508 使用确定移动终端处于DRX状态。 [0172] 小号 510 . 移动终端向目标小区对应的接入网元发起连接建立。 [0173] 在一个实施例中,移动终端向目标小区对应的接入网元发起连接建立后,移动终端与服务小区对应的接入网元保持连接。 [0174] 小号 511 . 移动终端根据满足测量报告事件的进入条件的测量结果生成测量报告,该测量报告事件不同于指示信息对应的测量报告事件的进入条件。 [0175] 小号 512 . 移动终端将测量报告发送给服务小区对应的接入网元。 [0176] 如果 S 之前的操作 512 是小号 508 或 509 ,移动终端发送的测量报告为指示信息对应的测量报告事件的测量报告。 如果 S 之前的操作 512 是小号 511 ,移动终端发送的测量报告是移动终端根据测量报告事件的满足进入条件的测量结果生成的测量报告,不同于指示信息对应的测量报告事件的进入条件 . [0177] 当 S 之前的操作 512 是小号 508或 509 ,表示即使移动终端接收到指示信息,目标小区的测量结果也满足该指示信息对应的测量上报事件的进入条件,移动终端生成对应的测量上报事件的测量报告 对于指示信息,移动终端根据S中的判断结果进行选择 508 和/或 509 ,以应用指示信息(即,执行 S 510 ). 或者,移动终端根据S中的判断结果进行选择 508 和/或 509 , 不应用指示信息; 仍然按照现有技术建立到目标小区的连接,即执行S 512 将测量报告发送给服务小区对应的接入网元; 然后,等待接入网元向移动终端下发允许建立连接的指示。 只有当移动终端接收到接入网元下发给移动终端的允许建立连接的指示时,移动终端才与目标小区对应的接入网元建立连接。 [0178] 可以理解的是,现有技术中的通信过程中已经包含了关于测量报告生成的协议、配置等。 因此,在基于现有协议或配置应用本实施例时,需要调整和修改的内容较少,范围较小,有利于本实施例的实施。 [0179] 本实施例中,移动终端在确定目标小区的测量结果满足指示信息对应的测量上报事件的(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.628 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.783 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.801 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN105659666A(String), EP3193534A1(String), EP3193534A4(String), US10142904B2(String), US10499298B2(String), US10805853B2(String), US20170251417A1(String), US20190075502A1(String), US20200068471A1(String), WO2016049931A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 11 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), CN105659666A(String), 1049229(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.852 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), EP3193534A1(String), 1049922(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), EP3193534A4(String), 1049923(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.920 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.920 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), US10142904B2(String), 1049924(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.953 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), US10499298B2(String), 1049925(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:46.987 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), US10805853B2(String), 1049926(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), US20170251417A1(String), 1049927(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), US20190075502A1(String), 1049928(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.087 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), US20200068471A1(String), 1049929(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271563(Integer), WO2016049931A1(String), 1049930(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.153 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN105659666A(String), CN105659666A(String), 1465315200(Integer), 271563(Integer), 185847(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.234 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185996(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.300 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185996(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.336 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.369 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.371 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185996(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185996(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.457 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.474 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.474 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.474 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.491 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.543 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.562 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.716 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185996(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:47.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20220368007A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and mobile terminal antenna production method(String), 移动终端及移动终端天线的制作方法(String), US20220368007A1(String), A mobile terminal and a mobile terminal antenna production method. The mobile terminal uses an insulation film layer on an insulation rear housing as a carrier of a radiating element of an antenna, and the radiating element is located within the entire mobile terminal. A feed and an electric-conductor are disposed on a circuit board, and the electric-conductor is electrically connected to the feed. There is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 一种移动终端及移动终端天线的制作方法。 该移动终端采用绝缘后壳上的绝缘膜层作为天线辐射元件的载体,辐射元件位于整个移动终端内。 电路板上设有馈线及导电体,导电体电性连接馈线。 辐射元件与导电体之间存在间隙,导电体以电容耦合的方式间接耦合辐射元件。(String), US17/874597(String), 1658851200(Integer), US20220368007A1(String), 1668614400(Integer), 美国(String), 2(Integer), CN(String), 7(Integer), 9(Integer), CN108242592A | US11011850B2 | US11450946B2 | US20130101149A1 | US20150207208A1 | US20180332741A1 | US20190207318A1 | US20200321688A1 | WO2011051408A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185997(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.277 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\07ed955437d74569843dfcaf1f97aeab.png(String), 185997(Integer), 07ed955437d74569843dfcaf1f97aeab.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.312 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.313 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and mobile terminal antenna production method(String), 移动终端及移动终端天线的制作方法(String), US20220368007A1(String), A mobile terminal and a mobile terminal antenna production method. The mobile terminal uses an insulation film layer on an insulation rear housing as a carrier of a radiating element of an antenna, and the radiating element is located within the entire mobile terminal. A feed and an electric-conductor are disposed on a circuit board, and the electric-conductor is electrically connected to the feed. There is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 一种移动终端及移动终端天线的制作方法。 该移动终端采用绝缘后壳上的绝缘膜层作为天线辐射元件的载体,辐射元件位于整个移动终端内。 电路板上设有馈线及导电体,导电体电性连接馈线。 辐射元件与导电体之间存在间隙,导电体以电容耦合的方式间接耦合辐射元件。(String), US17/874597(String), 1658851200(Integer), US20220368007A1(String), 1668614400(Integer), 美国(String), 1(Integer), 2(Integer), CN(String), 7(Integer), 9(Integer), CN108242592A | US11011850B2 | US11450946B2 | US20130101149A1 | US20150207208A1 | US20180332741A1 | US20190207318A1 | US20200321688A1 | WO2011051408A1(String), \20230420\07ed955437d74569843dfcaf1f97aeab.png(String), 20(Integer), 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 1. A mobile terminal, comprising:a mobile terminal body comprising a circuit board;an insulation rear housing that covers the mobile terminal body, the insulation rear housing comprising an inner side facing the mobile terminal body, wherein an insulation film layer covers the inner side of the insulation rear housing; andan antenna, comprising:a feed disposed on the circuit board;an electric-conductor disposed on the circuit board, wherein the electric-conductor is electrically connected to the feed; anda radiating element disposed on the insulation film layer, wherein there is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 1.移动终端,包括:一种移动终端本体,包括电路板;绝缘后壳覆盖移动终端本体,绝缘后壳包括面向移动终端本体的内侧,绝缘膜层覆盖绝缘后壳的内侧;和天线,包括:馈线设置于电路板上;一导电体,设置于电路板上,其中导电体电性连接至馈线。和辐射元件设置于绝缘膜层上,辐射元件与导电体之间具有间隙,导电体以电容耦合的方式间接耦合辐射元件。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 2. The mobile terminal according to claim 1, wherein the insulation rear housing is a glass rear housing.(String), 2.根据权利要求1所述的移动终端,其中绝缘后壳为玻璃后壳。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 3. The mobile terminal according to claim 1, wherein the radiating element comprises silver, aluminum, or copper.(String), 3.根据权利要求1所述的移动终端,其中辐射元件包括银、铝或铜。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 4. The mobile terminal according to claim 1, wherein a thickness of the radiating element is between 1 μm and 200 μm.(String), 4.根据权利要求1所述的移动终端,其中辐射元件的厚度介于1μm至200μm之间。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 5. The mobile terminal according to claim 4, wherein an impedance of the radiating element is less than 3 ohms.(String), 5.根据权利要求4所述的移动终端,其中辐射元件的阻抗小于3欧姆。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 6. The mobile terminal according to claim 1, wherein a square resistance of the radiating element is less than 1 ohm/□.(String), 6.根据权利要求1所述的移动终端,其中辐射元件的方块电阻小于1欧姆/□。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 7. The mobile terminal according to claim 1, wherein the insulation film layer is at least one of the following:an ink film layer, a decorative film layer, or an explosion-proof film layer.(String), 7.根据权利要求1所述的移动终端,其中绝缘膜层至少为以下之一:油墨膜层、装饰膜层或防爆膜层。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 8. The mobile terminal according to claim 1, wherein the mobile terminal body further comprises a support disposed on the circuit board, wherein the support is insulated and the electric-conductor is disposed on the support.(String), 8.根据权利要求1所述的移动终端,其中移动终端本体还包括设置在电路板上的支架,支架绝缘,导电体设置在支架上。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 9. The mobile terminal according to claim 1, wherein the antenna further comprises a ground disposed on the circuit board, the electric-conductor is electrically connected to the ground.(String), 9.根据权利要求1所述的移动终端,其中天线还包括一地线,设置于电路板上,导电体电性连接于地线。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 10. The mobile terminal according to claim 9, wherein,one end of the electric-conductor is electrically connected to the feed, and the other end of the electric-conductor is connected to the radiating element in a coupled manner; orone end of the electric-conductor is electrically connected to the ground, and the other end of the electric-conductor is connected to the radiating element in a coupled manner; orone end of the electric-conductor is electrically connected to the feed, the other end of the electric-conductor is electrically connected to the ground.(String), 10.根据权利要求9所述的移动终端,其中,导电体的一端与馈线电连接,另一端与辐射元件耦合连接。或者导电体的一端与地电性连接,另一端与辐射元件耦合连接。或者导电体的一端与馈线电连接,另一端与地电连接。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 11. The mobile terminal according to claim 1, wherein the electric-conductor is a metal spring plate.(String), 11.根据权利要求1所述的移动终端,其中导电体为金属弹片。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 12. The mobile terminal according to claim 11, wherein the metal spring plate is an inverted L-shaped metal spring plate or an inverted U-shaped metal spring plate.(String), 12.根据权利要求11所述的移动终端,其中金属弹片为倒L型金属弹片或倒U型金属弹片。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 13. The mobile terminal according to claim 1, wherein the insulation rear housing comprises a flat plate and a bent side wall, and an arc-shaped transition is used at a joint between the bent side wall and the flat plate.(String), 13.根据权利要求1所述的移动终端,其中绝缘后壳包括平板和折弯侧壁,折弯侧壁与平板的连接处采用弧形过渡。(String), 1(Integer), 12(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 14. The mobile terminal according to claim 13, wherein the radiating element is disposed on the flat plate of the insulation rear housing.(String), 14.根据权利要求13所述的移动终端,其中散热元件设置于绝缘后壳的平板上。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 15. The mobile terminal according to claim 13, wherein the radiating element is disposed with a certain distance from the edge of the insulation film layer.(String), 15.根据权利要求13所述的移动终端,其中辐射元件设置在距离绝缘膜层边缘一定距离处。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 16. The mobile terminal according to claim 13, wherein the radiating element is disposed on the bent side wall of the insulation rear housing.(String), 16.根据权利要求13所述的移动终端,其中散热元件设置于绝缘后壳的弯折侧壁上。17、一种移动终端天线制作方法包括:在绝缘膜层上设置辐射元件;将绝缘膜层设置于绝缘后壳的内侧;在移动终端本体中的电路板上制作馈电;和将导电体电性连接至馈源,其中辐射元件与导电体之间具有间隙,且导电体以电容耦合的方式间接耦合辐射元件。(String), 1(Integer), 15(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 17. A mobile terminal antenna production method comprising:disposing a radiating element on an insulation film layer;disposing the insulation film layer to an inner side of an insulation rear housing;producing a feed on a circuit board in a mobile terminal body; andelectrically connecting an electric-conductor to the feed, wherein there is a gap between the radiating element and the electric-conductor, and the electric-conductor indirectly couples the radiating element in a capacitively coupled manner.(String), 18.根据权利要求17所述的移动终端的制作方法,其中辐射元件的厚度在1μm~200μm之间,f辐射元件的阻抗小于3欧姆或者辐射元件的方块电阻小于1欧姆/□。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 18. The mobile terminal production method according to claim 17, wherein a thickness of the radiating element is between 1 μm and 200 μm, and an impedance of the f radiating element is less than 3 ohms or a square resistance of the radiating element is less than 1 ohm/□.(String), 19.根据权利要求17所述的移动终端的制作方法,还包括:在电路板上设置一支架,其中支架绝缘。和将导电体设置于支架上。(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 19. The mobile terminal production method according to claim 17, further comprising:disposing a support on the circuit board, wherein the support is insulated; anddisposing the electric-conductor on the support.(String), 20.根据权利要求17所述的移动终端的制作方法,其中绝缘后壳包括平板和折弯侧壁,折弯侧壁与平板的连接处采用弧形过渡,散热元件设置在绝缘边缘一定距离处膜层。(String), 1(Integer), 18(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185997(Integer), 20. The mobile terminal production method according to claim 17, wherein the insulation rear housing comprises a flat plate and a bent side wall, an arc-shaped transition is used at a joint between the bent side wall and the flat plate, and the radiating element is disposed with a certain distance from the edge of the insulation film layer.(String), 1(Integer), 19(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.797 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185997(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of U.S. patent application Ser. No. 16/954,591, filed on Jun. 17, 2020, which is a national stage of International Application No. PCT/CN2019/098310, filed on Jul. 30, 2019, which claims priority to Chinese Patent Application No. 201810858567.0, filed on Jul. 31, 2018. All of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The embodiments relate to the field of antenna technologies, and a mobile terminal, and a mobile terminal antenna production method. BACKGROUND [0003]Currently, functions of smart phones are increasing each passing day, and the smart phones need to cover an increasingly wide communication range. A mobile phone apparatus also has increasing requirements for both an antenna and an antenna quantity. How to place more antennas in limited space is one of urgent problems to be resolved in the antenna structure field. Currently, common antenna designs all use a support, such as a laser direct structuring (LDS) technology or a metal bezel of a mobile phone as an antenna radiator. An antenna may be an IFA, a monopole antenna, or a loop antenna. However, with increasing requirements of various components and functions on a mobile phone end, the foregoing conventional method is limited in future application, and a clearance area required during antenna radiation is reduced accordingly. In addition, an LDS antenna structured on support plastic is usually placed inside a mobile phone body and is more liable to be affected by peripheral parts and components. Besides, because the antenna is comparatively short, the antenna is liable to be limited in space freedom or in efficiency and a bandwidth. SUMMARY [0004]The embodiments provide a mobile terminal and a mobile terminal antenna production method, so as to improve communication performance of the mobile terminal. [0005]According to a first aspect, a mobile terminal is provided. The mobile terminal includes a mobile terminal body and an insulation rear housing that covers the mobile terminal body. An insulation film layer covers an inner side of the insulation rear housing. The inner side of the insulation rear housing is a surface facing the mobile terminal body when the insulation rear housing covers the mobile terminal body. In addition, the mobile terminal further includes an antenna. The antenna includes a feed and a radiating element electrically connected to the feed. The feed is disposed on a circuit board in the mobile terminal body, and the radiating element is printed on the insulation film layer. It can be understood from the foregoing description that the insulation film layer on the insulation rear housing serves as a carrier of the radiating element of the antenna, and the radiating element is located within the entire mobile terminal, thereby effectively increasing a height of the radiating element of the antenna relative to the circuit board with the antenna not affecting an appearance of the mobile terminal (compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm). This reduces an impact caused by a metal component on the circuit board on antenna radiation, and further increases a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. [0006]When being disposed, the radiating antenna uses a metallic wire. The metallic wire may be a straight metallic wire, a curved metallic wire, or a spiral metallic wire, and a shape is not limited. The metallic wire may be prepared using different materials such as aluminum, copper, and silver. In an embodiment, the metallic wire is a silver wire. [0007]For a disposing position of the radiating antenna, the radiating antenna may be disposed in any position on the inner side of the insulation rear housing as needed, for example, a position on a side wall. [0008]To improve a radiation effect of the antenna, when the metallic wire is disposed, a thickness of the metallic wire is between 1 μm and 200 μm, and an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□. [0009]The insulation rear housing may be prepared using different materials, provided that insulation can be ensured. For example, the insulation rear housing is a glass rear housing or plastic rear housing. [0010]For the insulation film layer, film layers with different functions may be used. For example, the insulation film layer is an ink film layer, a decorative film layer, or an anti-explosion film layer. [0011]For the antenna, antennas of different types may be used. For example, the antenna is one or more of a GPS antenna, a Wi-Fi antenna, an NFC antenna, a millimeter-wave antenna, a diversity antenna, or a main antenna. [0012]When the feed and the radiating element are connected electrically, the antenna further includes an electric-conductor. The electric-conductor is electrically connected to the feed and/or a ground, and the electric-conductor is connected to the radiating element in a coupled manner. In other words, an electrical connection between the electric-conductor and the radiating element is implemented in a coupled manner. Compared with a manner, in a general conventional solution, in which a signal line of the circuit board is directly connected to the antenna, feeding in a coupled manner can avoid problems caused by direct electrical-connection feeding, such as uneven contact pressure and a problem that impedance of a contact point becomes unstable after a long period of time due to factors such as oxidation. [0013]When the electric-conductor is disposed, different solutions may be used. For example, in a solution, the mobile terminal further includes a circuit board that is disposed in the mobile terminal body, and the feed and the ground are disposed on the circuit board; and a support is disposed on the circuit board, and the electric-conductor is a metallic wire disposed on the support, where one end of the metallic wire is electrically connected to the feed, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the ground, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the feed, the other end of the metallic wire is electrically connected to the ground, and the metallic wire is connected to the radiating element in a coupled manner. In other words, the metallic wire is directly disposed on the support to implement a coupling connection. [0014]In another solution, the mobile terminal further includes a circuit board that is disposed in the mobile terminal body, and the feed and the ground are disposed on the circuit board; and the electric-conductor is a metal spring plate, where one end of the metal spring plate is electrically connected to the feed, and the other end of the metal spring plate is connected to the radiating element in a coupled manner; or one end of the metal spring plate is electrically connected to the ground, and the other end of the metal spring plate is connected to the radiating element in a coupled manner; or one end of the metal spring plate is electrically connected to the feed, the other end of the metal spring plate is electrically connected to the ground, and the metal spring plate is connected to the radiating element in a coupled manner. [0015]When the metal spring plate is used, the metal spring plate may be in different shapes. For example, the metal spring plate is an inverted L-shaped metal spring plate or an inverted U-shaped metal spring plate. [0016]According to a second aspect, a mobile terminal antenna production method is provided. The production method includes the following steps. [0017]Print a radiating element on an insulation film layer. For example, spray silver paste on the film layer, and then bake the silver paste and the insulation film layer at 50 degrees to 200 degrees for 30 minutes to 60 minutes, to form a metallic wire. [0018]Stick the insulation film layer to an inner side of an insulation rear housing. [0019]The insulation film layer on the insulation rear housing serves as a carrier of the radiating element of an antenna, and the radiating element is located within an entire mobile terminal, thereby effectively increasing a height of the radiating element of the antenna relative to a circuit board with the antenna not affecting an appearance of the mobile terminal (compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm). This reduces an impact caused by a metal component on the circuit board on antenna radiation, and further increases a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. [0020]The used silver paste includes 50-99 wt % silver powder, and viscosity of the silver paste is 10-20000 cps. [0021]After the metallic wire is formed, a thickness of the metallic wire is between 1 μm and 200 μm, and an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□, to ensure that the antenna can have good communication performance. [0022]The production method further includes: producing a feed and a ground on the circuit board and connecting an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner. [0023]When the electric-conductor is in different structural forms, different production manners may be used. For example, the connecting an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner, is: disposing a support on the circuit board, and printing a metallic wire on the support, where one end of the metallic wire is electrically connected to the feed, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the ground, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the feed, the other end of the metallic wire is electrically connected to the ground, and the metallic wire is connected to the radiating element in a coupled manner. [0024]When the electric-conductor is a metal spring plate, the connecting an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner, is: connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the ground electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the ground electrically, where the metal spring plate and the radiating element are connected in a coupled manner. In other words, the electric-conductor may be formed in different structural forms. BRIEF DESCRIPTION OF THE DRAWINGS [0025]FIG. 1 is a schematic structural diagram of a mobile terminal according to an embodiment; [0026]FIG. 2 is a sectional view at A-A in FIG. 1; [0027]FIG. 3 is a schematic structural diagram of another mobile terminal according to an embodiment; [0028]FIG. 4 is a schematic structural diagram of another mobile terminal according to an embodiment; [0029]FIG. 5 is a schematic structural diagram of an antenna according to an embodiment n; [0030]FIG. 6 is a schematic structural diagram of another antenna according to an embodiment; [0031]FIG. 7 is a schematic structural diagram of another antenna according to an embodiment; [0032]FIG. 8 is a schematic structural diagram of another antenna according to an embodiment; and [0033]FIG. 9 is a flowchart of producing a mobile terminal antenna according to an embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS [0034]To make the objectives, solutions, and advantages of the embodiments clearer, the following further describes the embodiments in detail with reference to the accompanying drawings. [0035]An embodiment provides a mobile terminal. The mobile terminal includes a mobile terminal body and an insulation rear housing 10 that covers the mobile terminal body. The insulation rear housing 10 is a phone housing of the mobile terminal. FIG. 1 and FIG. 2 show a structure of the insulation rear housing 10. First, as shown in FIG. 1 and FIG. 2, the insulation rear housing 10 is a rectangular structure and includes a flat plate and four bent side walls. During bending, as shown in FIG. 2, where FIG. 2 shows a sectional view at A-A in FIG. 1, a connection manner between the side wall and the flat plate is clearly shown in FIG. 2, where an arc-shaped transition is used at a joint between the bent side wall and the flat plate. In addition, during production, the insulation rear housing 10 is formed in an integrated structuring manner. However, the structure of the insulation rear housing 10 is not limited to the structure shown in FIG. 1 and FIG. 2, and a structure shown in FIG. 4 may be alternatively used. When the structure shown in FIG. 4 is used, the insulation rear housing 10 is an arc-shaped rear housing. However, the structure of the insulation rear housing 10 may alternatively be in another structural form. For ease of description, an inner side of the insulation rear housing 10 is defined. The inner side of the insulation rear housing 10 in this embodiment is a concave side of the insulation rear housing 10. When the insulation rear housing 10 is mounted on the mobile terminal body, the inner side faces the mobile terminal body. [0036]Different materials such as glass and plastic may be selected for the insulation rear housing 10 provided in this embodiment, provided that insulation can be implemented. For example, when a glass material is used, the insulation rear housing 10 is a glass rear housing 10. [0037]Still referring to FIG. 1, an insulation film layer 20 covers the inner side of the insulation rear housing 10. As a bearing structure, the insulation film layer 20 is configured to bear a radiating element 30 of an antenna. For the insulation film layer 20, film layers with different functions may be used. For example, the insulation film layer 20 is an ink film layer, a decorative film layer, or an anti-explosion film layer. A material used by the insulation film layer 20 may be plastic. When the insulation film layer 20 covers the inner side of the insulation rear housing 10, the insulation film layer 20 is adhered to the inner side of the insulation rear housing 10 by an adhesive or fixed to the inner side of the insulation rear housing 10 through vacuum adsorption. [0038]Still referring to FIG. 1 and FIG. 2, the mobile terminal provided in this embodiment further includes an antenna. For the antenna, antennas of different types may be used. For example, the antenna is one or more of a GPS antenna, a Wi-Fi antenna, an NFC antenna, a millimeter-wave antenna, a diversity antenna, or a main antenna. It can be understood that the antenna provided includes one or more of antennas of the foregoing several types but is not limited to the antennas of the foregoing listed types, and regardless of an antenna that is used, the antenna provided in this embodiment includes the following two structures: a feed and the radiating element 30. The feed is electrically connected to the radiating element 30. When the feed is disposed, the feed is disposed on a circuit board in the mobile terminal body. The circuit board may be a PCB board. To improve performance of the antenna, when the radiating element 30 is disposed, as shown in FIG. 1 and FIG. 2, the radiating element 30 is printed on the insulation film layer 20. The radiating element 30 uses a metallic wire and may be in different shapes. As shown in FIG. 1 and FIG. 2, the metallic wire may be a straight metallic wire, or may be in another structure, for example, a curved metallic wire, or a spiral metallic wire shown in FIG. 3. It can be understood from FIG. 1 and FIG. 3 that a shape of the radiating element 30 is not limited, and a different choice may be made as needed. In addition, for a disposing position of the radiating element 30, the radiating element 30 may be disposed in any position on the insulation film layer 20. It can be understood from FIG. 1 and FIG. 2 that there is not another structure on the insulation film layer 20. Therefore, a different position may be selected as needed for disposing the radiating element 30. As shown in FIG. 1 and FIG. 2, the radiating element 30 is disposed on the side wall of the insulation rear housing 10; and, as shown in FIG. 3, the radiating element 30 is disposed on the flat plate of the insulation rear housing 10. In addition, a quantity of radiating elements 30 is not limited. For example, there is one radiating element 30 shown in FIG. 1, and there are two radiating elements 30 shown in FIG. 4. In addition, the metallic wire may be prepared using different materials, such as aluminum, copper, and silver. In an embodiment, the metallic wire is a silver wire, which has good electrical conductivity. [0039]When the radiating element 30 is produced, the radiating element 30 is structured on the insulation film layer 20 by using a metal printing process. In this embodiment, the metallic wire is prepared using silver paste. Therefore, the following uses the silver paste as an example for description. First, a component of the silver paste used includes 50-99 wt % (mass percentage) silver powder, and viscosity of the formed silver paste is 10-20000 cps (mPa·s), to ensure that the silver paste can be stably adhered to the insulation film layer 20. During printing, first, the silver paste is sprayed or printed on the insulation film layer 20 (a decorative film layer, an anti-explosion film layer, or an ink film layer may be selected), and then, the silver paste and the insulation film layer 20 are baked at 50 degrees to 200 degrees for 30 min to 60 min (minutes), to increase adhesion on the insulation film layer 20. Then, the silver paste is formed to a thickness of 1 μm to 200 μm (micrometers). Further, it is ensured that an impedance of the prepared silver paste is less than 3 ohms (including 1 ohm) (a definition for testing: a value, expressed in ohms, measured between any two points on the antenna). In other words, a thickness of a printed metallic wire is between 1 μm and 200 μm, for example, 3 μm, 5 μm, 10 μm, 15 μm, or 20 μm. In addition, an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□, where the square resistance is defined as follows. When a length is represented by l, a width is represented by w, and a height is represented by d (that is, a thickness of the film), L (length)=l, and S (cross-sectional area)=w*d; and therefore, R=ρ*l/(w*d)=(ρ/d)*(l/w). Let l=w, and then, R=(ρ/d), where ρ is resistivity of a material. In this case, R is the square resistance and is expressed in ohm/□, where “□” indicates that a cross section of the metallic wire is a square. [0040]During disposing, two different manners may be used. One manner is: first printing the radiating element 30 on the insulation film layer 20 and then sticking the insulation film layer 20 into the insulation rear housing 10. The other manner is: first sticking the insulation film layer 20 into the insulation rear housing 10 and then printing the radiating element 30 on the insulation film layer 20. As shown in FIG. 2 and FIG. 4, when a position corresponding to the radiating element 30 is arc-shaped, the manner of first printing the radiating element 30 on the insulation film layer 20 greatly facilitates disposing of the radiating element 30. [0041]It can be understood from the foregoing description that the insulation film layer 20 on the inner side of the insulation rear housing 10 is configured to support the radiating element 30 of the antenna, so that the radiating element 30 is located within the entire mobile terminal, thereby effectively increasing a height of the radiating element 30 of the antenna relative to the circuit board with the antenna not affecting an appearance of the mobile terminal. Compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm, thereby reducing an impact caused by a metal component on the circuit board on antenna radiation, and further increasing a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. [0042]When the antenna is disposed, the antenna not only includes the radiating element 30, but also includes the feed and a ground, and the feed and the ground are electrically connected to the radiating element 30. To implement electrical connections of the feed and the ground to the radiating element 30, an electric-conductor is further disposed in the antenna provided in this embodiment. The electric-conductor is electrically connected to the feed and/or the ground, and the electric-conductor is connected to the radiating element 30 in a coupled manner. It should be understood that a coupling connection is an indirect coupling connection, that is, there is a gap between the radiating element 30 and the electric-conductor, and an electrical connection is implemented in a capacitively coupled manner. When the electric-conductor is disposed, the electric-conductor may be in different structural forms. The following describes implementations of two electric-conductors with reference to FIG. 5 and FIG. 7. [0043]As shown in FIG. 5, a feed is disposed on a circuit board 60 in a mobile terminal body, and a support 50 is further disposed on the circuit board 60. The support 50 is used as a support carrier to support an electric-conductor. In the structure shown in FIG. 5, the electric-conductor is a metallic wire 40. The metallic wire 40 is fixed on the support in a printing or flexible-plate sticking manner. In addition, a quantity of electric-conductors is in a one-to-one correspondence with a quantity of radiating elements 30. When two radiating elements 30 are used in FIG. 5, there are two corresponding electric-conductors, and there are also two corresponding supports 50. The support 50 may be in different structural forms. For example, in FIG. 5, the support 50 is a support block, and the support block is fixed on the circuit board 60 in a sticking manner. It can be understood that as a carrier, the support 50 should be insulated, to avoid affecting power feeding of the electric-conductor. FIG. 5 is a schematic diagram of an electrical connection between the metallic wire 40 and the feed. As shown in FIG. 6, a placement direction of a mobile terminal shown in FIG. 6 is used as a reference direction. A metallic wire 40 located on the right side is electrically connected to the ground, and two ends of a metallic wire 40 located on the left side are electrically connected to the ground and the feed separately. When the metallic wires 40 are electrically connected to the ground, a disposing manner of the metallic wires 40 is similar to that in FIG. 5, and an only difference lies in that one metallic wire 40 is connected to the feed on the circuit board 60, and the other metallic wire 40 is connected to the ground on the circuit board 60. When the two ends of the metallic wire 40 are separately connected to the feed and the ground, one end of the metallic wire 40 is connected to a feed point, and the other end of the metallic wire 40 is connected to the ground. The metallic wire 40 is connected to the radiating element 30 in a coupled manner. A coupling portion is a portion between the two ends. [0044]FIG. 7 shows a structure of another electric-conductor. In FIG. 7, the electric-conductor is a metal spring plate 70. One end of the metal spring plate 70 is fixed (electrically connected) to the feed, and the other end of the metal spring plate 70 is a free end. The free end of the metal spring plate 70 is connected to the radiating element 30 in a coupled manner. During disposing, as shown in FIG. 7, the metal spring plate 70 is an inverted L-shaped metal spring plate 70. However, a structural form of the metal spring plate 70 is not limited to the one specified in FIG. 7. The metal spring plate 70 may alternatively be an arc-shaped metal sheet, or a wavy metal spring plate 70, and both may be applied to the embodiments. For a material of the metal spring plate 70, the material may have good electrical conductivity and strength, such as copper, aluminum, or iron. As shown in FIG. 8, a placement direction of a mobile terminal shown in FIG. 8 is used as a reference direction. A metal spring plate 70 located on the right side is electrically connected to the ground, and two ends of a metal spring plate 70 located on the left side are electrically connected to the ground and the feed separately. When the metal spring plate 70 is electrically connected to the ground, a disposing manner of the metal spring plate 70 is similar to that in FIG. 7, and an only difference lies in that one metal spring plate 70 is connected to the feed on the circuit board 60, and the other metal spring plate 70 is connected to the ground on the circuit board 60. When the two ends of the metal spring plate 70 are separately connected to the feed and the ground, one end of the metal spring plate 70 is connected to a feed point, and the other end of the metal spring plate 70 is connected to the ground. The metal spring plate 70 is connected to the radiating element 30 in a coupled manner. A coupling portion is a portion between the two ends. In this case, the metal spring plate 70 is an inverted U-shaped structure. [0045]It can be understood from FIG. 5 to FIG. 8 that in the antenna, the electrical connection between the electric-conductor and the radiating element and an electrical connection between the electric-conductor and the ground are implemented in a coupled manner. Compared with a manner, in a general conventional solution, in which a signal line of the circuit board 60 is directly connected to the antenna, feeding in a coupled manner can avoid problems caused by direct electrical-connection feeding, such as uneven contact pressure and a problem that impedance of a contact point becomes unstable after a long period of time due to factors such as oxidation. [0046]In addition, the embodiments further provide an antenna production method. The method includes: printing a radiating element 30 on an insulation film layer 20 and sticking the insulation film layer 20 to an inner side of an insulation rear housing 10. The method includes two different manners: first printing a radiating element 30 on an insulation film layer 20, and then sticking the insulation film layer 20 into an insulation rear housing 10; or first sticking an insulation film layer 20 into an insulation rear housing 10, and then printing a radiating element 30 on the insulation film layer 20. As shown in FIG. 2 and FIG. 4, it can be understood from FIG. 1 and FIG. 4 that when a position corresponding to the radiating element 30 is arc-shaped, the manner of first printing the radiating element 30 on the insulation film layer 20 greatly facilitates disposing of the radiating element 30. [0047]The following describes the method in detail with reference to FIG. 9. [0048]Step 01: Spray silver paste on the insulation film layer 20. [0049]For example, a material of the used silver paste includes 50-99 wt % (mass percentage) silver powder, and viscosity of the silver paste is 10-20000 cps (mPa·s), so that the silver paste can be firmly adhered to the insulation film layer 20. [0050]Step 02: Bake the silver paste and the insulation film layer at 50 degrees to 200 degrees for 30 min to 60 min (minutes), to form a metallic wire. [0051]When the metallic wire is formed, a thickness of the metallic wire is between 1 μm and 200 μm (micrometers), for example, 3 μm, 5 μm, 10 μm, 15 μm, or 20 μm. In addition, an impedance of the metallic wire is less than 3 ohms, or a square resistance of the metallic wire is less than 1 ohm/□, to ensure that an antenna can have good communication performance. [0052]Step 03: Stick the insulation film layer 20 to an inner side of the insulation rear housing 10. [0053]For example, the insulation film layer 20 on which the metallic wire is printed is stuck into the insulation rear housing 10 by an adhesive. [0054]Step 04: Produce a feed and a ground on a circuit board and connect an electric-conductor to the feed and/or the ground electrically, where the electric-conductor is connected to the radiating element in a coupled manner. [0055]During disposing, when the electric-conductor is in different structural forms, different production manners may be used. For example, when the electric-conductor is a metallic wire, the fixing the electric-conductor on the feed may include disposing a support on the circuit board, and printing the metallic wire on the support, where one end of the metallic wire is electrically connected to the feed, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the ground, and the other end of the metallic wire is connected to the radiating element in a coupled manner; or one end of the metallic wire is electrically connected to the feed, the other end of the metallic wire is electrically connected to the ground, and the metallic wire is connected to the radiating element in a coupled manner. [0056]When the electric-conductor is a metal spring plate, the fixing of the electric-conductor on the feed is: connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the ground electrically, and connecting the other end of the metal spring plate to the radiating element in a coupled manner; or connecting one end of the metal spring plate to the feed electrically, and connecting the other end of the metal spring plate to the ground electrically, where the metal spring plate and the radiating element are connected in a coupled manner. [0057]It can be understood from the foregoing description that the insulation film layer 20 on the insulation rear housing 10 serves as a carrier of the radiating element 30 of the antenna, and the radiating element 30 is located within an entire mobile terminal, thereby effectively increasing a height of the radiating element 30 of the antenna relative to the circuit board with the antenna not affecting an appearance of the mobile terminal. Compared with a conventional support solution, this manner can increase a height of about 0.2 mm to 0.6 mm, thereby reducing an impact caused by a metal component on the circuit board on antenna radiation, and further increasing a bandwidth and efficiency of the antenna so that the antenna can cover a frequency band used in a handheld communications system. In addition, in the antenna, an electrical connection between the electric-conductor and the radiating element is implemented in a coupled manner. Compared with a manner, in a general conventional solution, in which a signal line of the circuit board is directly connected to the antenna, feeding in a coupled manner can avoid problems caused by direct electrical-connection feeding, such as uneven contact pressure and a problem that impedance of a contact point becomes unstable after a long period of time due to factors such as oxidation. [0058]The foregoing descriptions are merely embodiments but are not intended as limiting. Any variation or replacement readily figured out by a person of ordinary skill in the art shall fall within the scope of the embodiments.(String), 交叉引用相关申请 [0001]该申请是美国专利申请Ser的延续。第16/954,591号,于2020年6月17日提交,这是国际申请号PCT/CN2019/098310的全国阶段,于2019年7月30日提交,要求中国专利申请号201810858567.0优先在2018年7月31日。所有上述申请均通过引用整体合并。 技术领域 [0002]该实施方案与天线技术和移动末端和移动末端天线生产方法有关。 背景 [0003]当前,智能手机的功能每天都在增加,智能手机需要涵盖日益广泛的沟通范围。手机设备对天线和天线数量也有越来越多的要求。如何在有限空间中放置更多天线是在天线结构场中解决的紧迫问题之一。目前,常见天线设计都使用了支持,例如激光直接结构(LDS)技术或手机的金属挡板作为天线散热器。天线可能是IFA,单极天线或环天线。但是,随着手机端各种组件和功能的需求不断增加,上述常规方法在将来的应用中受到限制,并且在天线辐射过程中所需的间隙区域相应降低。此外,在支撑塑料上结构的LDS天线通常放置在手机主体内,并且更容易受到外围部件和组件的影响。此外,由于天线相对较短,因此天线可能受到空间自由度或效率和带宽的限制。 概括 [0004]该实施例提供了移动终端和移动终端天线生产方法,以提高移动终端的通信性能。 [0005]根据第一个方面,提供了移动终端。移动终端包括一个移动终端主体和覆盖移动终端体的绝缘后壳体。绝缘膜层覆盖了绝缘后壳的内侧。当绝缘后壳覆盖移动端子体时,绝缘后壳的内侧是面向移动端子体的表面。此外,移动终端还包括天线。天线包括一个进料和一个辐射元件,并带有电馈电饲料。饲料被放置在移动端子体的电路板上,辐射元件印在绝缘膜层上。可以从上述描述中可以理解,即绝缘后壳上的绝缘膜层用作天线辐射元件的载体,并且辐射元件位于整个移动端子内,从而有效地增加了辐射的高度天线的元素相对于电路板的元素不影响移动端子的外观(与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6 mm的高度)。这减少了由金属组件对电路板对天线辐射的影响,并进一步增加了天线的带宽和效率,因此天线可以覆盖手持式通信系统中使用的频带。 [0006]处置时,辐射天线使用金属线。金属线可以是直线金属线,弯曲的金属线或螺旋金属线,并且形状不受限制。可以使用铝,铜和银等不同材料制备金属线。在实施方案中,金属线是银线。 [0007]对于辐射天线的处置位置,可以根据需要在绝缘后壳内侧的任何位置处置辐射天线,例如,侧壁上的位置。 [0008]为了改善天线的辐射效果,当将金属线处置时,金属线的厚度在1μm至200μm之间,金属线的阻抗小于3欧姆,或金属的平方电阻电线小于1欧姆/□。 [0009]只要可以确保绝缘材料,就可以使用不同的材料制备绝缘后外壳。例如,隔热后壳是玻璃后壳或塑料后壳。 [0010]对于绝缘膜层,可以使用具有不同功能的膜层。例如,绝缘膜层是墨水膜层,装饰膜层或反爆炸膜层。 [0011]对于天线,可以使用不同类型的天线。例如,天线是一个或多个GPS天线,Wi-Fi天线,NFC天线,毫米波天线,多样性天线或主天线。 [0012]当饲料和辐射元件电气连接时,天线进一步包括电导器。电导器将电动连接到饲料和/或接地,并且电导器以耦合方式连接到辐射元件。换句话说,电导器与辐射元件之间的电连接以耦合方式实现。与某种方式相比,在一般常规溶液中,电路板的信号线直接连接到天线,以耦合方式喂食可以避免由直接电 - 连接进料引起的问题,例如不均匀的接触压力和A由于氧化等因素,在长时间后,接触点的阻抗变得不稳定。 [0013]当处理电导器时,可以使用不同的溶液。例如,在解决方案中,移动终端进一步包括在移动终端机构中放置的电路板,并且将饲料和地面放在电路板上;并在电路板上丢弃支撑,电动导电器是在支撑上丢弃的金属线,其中金属线的一端是电到饲料的,并且金属线的另一端连接到以耦合方式辐射元件;或金属线的一端是电到地面的,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到饲料的,金属线的另一端是电连接到地面的,并且金属线以耦合方式连接到辐射元件。换句话说,金属线直接在支撑上处置以实现耦合连接。 [0014]在另一种解决方案中,移动终端进一步包括在移动终端机构中放置的电路板,并将饲料和地面放在电路板上;电导器是金属弹簧板,其中金属弹簧板的一端是电到饲料的,并且金属弹簧板的另一端以耦合方式连接到辐射元件。或金属弹簧板的一端电到电到地面,金属弹簧板的另一端以耦合方式连接到辐射元件。或金属弹簧板的一端是电到饲料的,金属弹簧板的另一端是电连接到地面的,金属弹簧板以耦合方式连接到辐射元件。 [0015]当使用金属弹簧板时,金属弹簧板可能​​具有不同的形状。例如,金属弹簧板是倒置的L形金属弹簧板或倒立的U形金属弹簧板。 [0016]根据第二个方面,提供了移动终端天线生产方法。生产方法包括以下步骤。 [0017]在绝缘膜层上打印一个辐射元件。例如,在膜层上喷涂银糊,然后在50度至200度的隔热膜层烘烤30分钟至60分钟,以形成金属线。 [0018]将绝缘膜层粘贴到隔热后壳的内侧。 [0019]绝缘后外壳上的绝缘膜层充当天线的辐射元件的载体,并且辐射元件位于整个移动端子内,从而有效地增加了天线相对于电路板的辐射元件的高度由于天线不影响移动端子的外观(与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6 mm的高度)。这减少了由金属组件对电路板对天线辐射的影响,并进一步增加了天线的带宽和效率,因此天线可以覆盖手持式通信系统中使用的频带。 [0020]用过的银糊剂包括50-99 wt%的银色粉末,银糊的粘度为10-20000 cps。 [0021]形成金属线后,金属线的厚度在1μm和200μm之间,金属线的阻抗小于3欧姆,或者金属线的平方电阻小于1欧姆/□,□,□,确保天线可以具有良好的沟通性能。 [0022]生产方法进一步包括:在电路板上产生进料和地面,并将电动导电器连接到饲料和/或电地面,在该电路板上电导器以耦合方式连接到辐射元件。 [0023]当电导器处于不同的结构形式时,可以使用不同的生产方式。例如,将电动导电器连接到饲料和/或电地面,在电动导电器以耦合方式连接到辐射元件的地方是:在电路板上处置支撑,并打印金属线在支撑上,金属线的一端是电到饲料的,并且金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到地面的,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到饲料的,金属线的另一端是电连接到地面的,并且金属线以耦合方式连接到辐射元件。 [0024]当电导器是金属弹簧板时,将电导器连接到进料和/或电地面,在该电板上,电导器以耦合方式连接到辐射元件的地面,是:连接一端的一端金属弹簧板用电到饲料,并以耦合方式将金属弹簧板的另一端连接到辐射元件。或将金属弹簧板的一端连接到地面,并以耦合方式将金属弹簧板的另一端连接到辐射元件;或将金属弹簧板的一端连接到电饲料,然后将金属弹簧板的另一端连接到地面,在那里金属弹簧板和辐射元件以耦合方式连接。换句话说,电导器可以以不同的结构形式形成。 附图的简要说明 [0025]如图。 1是根据实施方案的移动终端的示意图结构图; [0026]如图。 2是图2中的A-A的截面视图。 1; [0027]如图。 3是根据实施方案的另一个移动终端的示意图结构图; [0028]如图。 4是根据实施方案的另一个移动终端的示意图结构图; [0029]如图。 5是根据实施方案n的天线的示意图结构图; [0030]如图。 6是根据实施方案的另一个天线的示意图结构图; [0031]如图。 7是根据实施方案的另一个天线的示意性结构图。 [0032]如图。 8是根据实施方案的另一个天线的示意图结构图;和 [0033]如图。 9是根据实施方案生成移动末端天线的流程图。 实施例的详细说明 [0034]为了使实施方案的目标,解决方案和优势更清晰,以下内容进一步描述了有关附带图纸的详细说明。 [0035]一个实施例提供了移动终端。移动终端包括一个移动终端和绝缘后壳体10覆盖了移动终端体。绝缘后壳10是移动终端的电话外壳。如图。 1和图。 2显示绝缘后壳的结构10。首先,如图图所示。 1和图。 2,绝缘后壳10是矩形结构,包括平板和四个弯曲的侧壁。在弯曲期间,如图2所示。 2,图。 2在图中显示了A-A的截面视图。 1,侧壁和平板之间的连接方式如图2所示。 2,其中在弯曲侧壁和平板之间的关节上使用了弧形的过渡。此外,在生产过程中,隔热后壳体10以综合结构方式形成。但是,绝缘后壳的结构10不限于图2所示的结构。 1和图。 2,以及图中所示的结构。可以使用4。当图中所示的结构。使用4,隔热后壳10是弧形的后壳。但是,绝缘后壳的结构10可以或者可能是另一种结构形式。为了易于描述,隔热后壳的内侧10被定义为。绝缘后壳的内侧10在这个实施方案中,是绝缘后壳的凹面10。当绝缘后壳10内侧安装在移动终端主体上,面向移动终端主体。 [0036]可以选择不同的材料(例如玻璃和塑料)作为绝缘后壳10在此实施例中提供,只要可以实施绝缘。例如,当使用玻璃材料时,隔热材料后壳10是玻璃后壳10。 [0037]仍然指图。 1,绝缘膜层20覆盖绝缘后壳的内侧10。作为轴承结构,绝缘膜层20被配置为带有辐射元素30天线。对于绝缘膜层20,可以使用具有不同功能的膜层。例如,绝缘膜层20是墨水膜层,装饰膜层或反爆炸膜层。绝缘膜层使用的材料20可能是塑料。当绝缘膜层20覆盖绝缘后壳的内侧10,绝缘膜层20被粘附在隔热后壳的内侧10通过粘合剂或固定在绝缘后壳的内侧10通过真空吸附。 [0038]仍然指图。 1和图。 2,该实施方案中提供的移动末端进一步包括天线。对于天线,可以使用不同类型的天线。例如,天线是一个或多个GPS天线,Wi-Fi天线,NFC天线,毫米波天线,多样性天线或主天线。可以理解的是,所提供的天线包括上述几种类型的一个或多个天线,但不限于上述列出的类型的天线,无论使用的天线如何,此实施方案中提供的天线包括以下内容包括两个结构:饲料和辐射元件30。进料是电连接到辐射元件的30。饲料处置后,将饲料放在移动端子体的电路板上。电路板可以是PCB板。在辐射元件时提高天线的性能30被处置,如图2所示。 1和图。 2,辐射元件30印在隔热膜层上20。辐射元件30使用金属线,可能具有不同的形状。如图图所示。 1和图。 2,金属线可以是直线金属线,也可以是另一个结构,例如,弯曲的金属线或图2所示的螺旋金属线。 3.可以从图中理解。 1和图。 3辐射元件的形状30不限,可以根据需要做出不同的选择。另外,对于辐射元件的处置位置30,辐射元素30可以在绝缘膜层上的任何位置处置20。可以从图中理解。 1和图。 2隔热膜层没有另一个结构20。因此,可以根据需要选择不同的位置以处置辐射元件30。如图图所示。 1和图。 2,辐射元件30被处置在绝缘后壳的侧壁上10;并且,如图图所示。 3,辐射元件30被处置在隔热后壳的平板上10。另外,一定数量的辐射元素30不限。例如,有一个辐射元素30如图所示。 1,有两个辐射元素30如图所示。 4.此外,可以使用铝,铜和银等不同材料制备金属线。在实施方案中,金属线是银线,具有良好的电导率。 [0039]当辐射元素30生产,辐射元件30是在绝缘膜层上结构的20通过使用金属打印过程。在这个实施方案中,金属线是使用银糊制备的。因此,以下是使用银糊作为描述的示例。首先,所使用的银糊的组成部分包括50-99 wt%(质量百分比)银色粉末,形成的银糊的粘度为10-20000 cps(mpa·s),以确保稳定的银糊剂可以稳定到绝缘膜层20。在印刷过程中,首先将银糊喷涂或印刷在绝缘膜层上20(可以选择装饰膜层,反爆炸膜层或墨水膜层),然后是银糊和绝缘膜层20以50度至200度烘烤30分钟至60分钟(分钟),以增加隔热膜层的粘附20。然后,将银糊形成1μm至200μm的厚度(微米)。此外,确保制备的银糊的阻抗小于3欧姆(包括1欧姆)(测试的定义:以欧姆表示的值,在天线上的任何两个点之间测量)。换句话说,印刷金属线的厚度在1μm至200μm之间,例如3μm,5μm,10μm,15μm或20μm。另外,金属线的阻抗小于3欧姆,或者金属线的平方电阻小于1欧姆/□,在该方向性的定义如下所示。当长度由L表示时,宽度由W表示,并且高度由D表示(即膜的厚度),L(长度)= L和S(横截面区域)= W *d;因此,r =ρ*l/(w*d)=(ρ/d)*(l/w)。令l = w,然后r =(ρ/d),其中ρ是材料的电阻率。在这种情况下,r是平方电阻,以欧姆/□表示,其中“□”表示金属线的横截面为正方形。 [0040]在处置过程中,可以使用两种不同的举止。一种方式是:首先打印辐射元素30在绝缘膜层上20然后粘贴隔热膜层20进入隔热后外壳10。另一种方式是:首先粘贴隔热膜层20进入隔热后外壳10然后打印辐射元件30在绝缘膜层上20。如图图所示。 2和图。 4,当位置对应于辐射元件时30是弧形的,首先打印辐射元件的方式30在绝缘膜层上20大大促进处置辐射元件30。 [0041]可以从上述描述中可以理解出隔热膜层20在绝缘后壳的内侧10被配置为支持辐射元素30天线的辐射元件30位于整个移动终端内,从而有效地增加了辐射元件的高度30天线相对于电路板的天线不影响移动端子的外观。与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6毫米的高度,从而减少了由金属成分对电路板对天线辐射的影响,并进一步提高天线的带宽和效率天线可以覆盖手持通信系统中使用的频带。 [0042]当处置天线时,天线不仅包括辐射元件30,但还包括饲料和地面,饲料和地面是电到辐射元件的30。实现进料的电气连接以及地面到辐射元件30,在该实施方案中提供的天线中进一步处置了电导器。电导器将电导器电连接到饲料和/或地面,电导器连接到辐射元件30以耦合方式。应该理解,耦合连接是间接耦合连接,也就是说,辐射元素之间存在差距30电导器和电连接以电容耦合方式实现。当电导器处置电导器时,电导器可能采用不同的结构形式。以下描述了两个电导器的实现。 5和图。 7。 [0043]如图图所示。 5,将饲料放在电路板上60在移动终端机构和支持50进一步处置在电路板上60。支撑50被用作支撑电导器的支撑载体。在图中所示的结构中。 5,电导器是金属线40。金属线40以打印或灵活的板粘性方式固定在支撑上。另外,一数量的电导器在一对一的对应关系中,散发元件数量30。当两个辐射元素30在图中使用。 5,有两个相应的电导器,还有两个相应的支撑50。支撑50可能是不同的结构形式。例如,在图中。 5,支持50是一个支撑块,支撑块固定在电路板上60以一种粘性的方式。可以理解,作为载体,支持50应隔热,以避免影响电导器的功率喂养。如图。 5是金属线之间电连接的示意图40和饲料。如图图所示。 6,移动终端的位置方向。 6用作参考方向。金属线40位于右侧的电气连接到地面,金属线的两端40位于左侧的电气连接到地面和饲料。当金属电线40是电连接到地面的,是金属电线的处置方式40与图中的相似之处。 5,唯一的区别在于那一条金属线40已连接到电路板上的供稿60和另一根金属电线40连接到电路板上的地面60。当金属线的两端40分别连接到饲料和地面,金属线的一端40连接到进料点,而金属线的另一端连接40连接到地面。金属线40连接到辐射元件30以耦合方式。耦合部分是两端之间的一部分。 [0044]如图。 7显示了另一个电导器的结构。在图中。 7,电导器是金属弹簧板70。金属弹簧板的一端70固定(电连接)到饲料,而金属弹簧板的另一端70是自由的。金属弹簧板的自由端70连接到辐射元件30以耦合方式。在处置过程中,如图2所示。 7,金属弹簧板70是倒L形金属弹簧板70。但是,金属弹簧板的结构形式70不仅限于图2中指定的。 7.金属弹簧板70可以或者可能是弧形金属板或波浪状的金属弹簧板70,并且两者都可以应用于实施方案。对于金属弹簧板的材料70,该材料可能具有良好的电导率和强度,例如铜,铝或铁。如图图所示。 8,移动终端的位置方向。 8用作参考方向。金属弹簧板70位于右侧的电气连接到地面,金属弹簧板的两端70位于左侧的电气连接到地面和饲料。当金属弹簧板70是电连接到地面的,是金属弹簧板的处置方式70与图中的相似之处。 7,唯一的区别在于那个金属弹簧板70已连接到电路板上的供稿60,还有其他金属弹簧板70连接到电路板上的地面60。当金属弹簧板的两端70分别连接到饲料和地面,金属弹簧板的一端70连接到进料点,而金属弹簧板的另一端70连接到地面。金属弹簧板70连接到辐射元件30以耦合方式。耦合部分是两端之间的一部分。在这种情况下,金属弹簧板70是倒的U形结构。 [0045]可以从图中理解。 5到图。 8在天线中,电导器与辐射元件之间的电连接以及电导器与地面之间的电连接以耦合方式实现。与某种方式相比,在常规解决方案中,电路板的信号线60直接连接到天线,以耦合方式喂食可以避免直接电连接进料引起的问题,例如不均匀的接触压力和由于诸如诸如等因素(例如氧化。 [0046]此外,实施方案进一步提供了一种天线生产方法。该方法包括:打印辐射元素30在绝缘膜层上20并粘贴隔热膜层20到绝缘后壳的内侧10。该方法包括两种不同的举止:首先打印一个辐射元素30在绝缘膜层上20,然后粘贴隔热膜层20进入绝缘后壳10;或首先粘附隔热膜层20进入绝缘后壳10,然后打印一个辐射元素30在绝缘膜层上20。如图图所示。 2和图。 4,可以从图中理解。 1和图。 4当位置对应于辐射元件时30是弧形的,首先打印辐射元件的方式30在绝缘膜层上20大大促进处置辐射元件30。 [0047]以下内容详细介绍了该方法,参考图。 9。 [0048]步01:在绝缘膜层上喷涂银糊20。 [0049]例如,用过的银糊的材料包括50-99 wt%(质量百分比)银色粉末,银糊的粘度为10-20000 cps(mpa·s),以便将银糊牢固地粘附在绝缘膜层20。 [0050]步02:将银糊和绝缘膜层以50度至200度烘烤30分钟至60分钟(分钟),以形成金属线。 [0051]当形成金属线时,金属线的厚度为1μm至200μm(微米),例如3μm,5μm,10μm,15μm,或20μm。此外,金属线的阻抗小于3欧姆,或者金属线的平方电阻小于1欧姆/□,以确保天线可以具有良好的通信性能。 [0052]步03:粘贴隔热膜层20到绝缘后壳的内侧10。 [0053]例如,绝缘膜层20金属线印刷在上面10通过粘合剂。 [0054]步04:在电路板上产生一个进料和接地,并将电导器连接到饲料和/或电地面,在该电路板上电导器以耦合方式连接到辐射元件。 [0055]在处置过程中,当电导器处于不同的结构形式时,可以使用不同的生产方式。例如,当电导器是金属电线时,饲料上的电导器固定可能包括在电路板上放置支架,并在支撑板上打印金属线,其中金属线的一端是电气的连接到饲料,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到地面的,金属线的另一端以耦合方式连接到辐射元件。或金属线的一端是电到饲料的,金属线的另一端是电连接到地面的,并且金属线以耦合方式连接到辐射元件。 [0056]当电导器是金属弹簧板时,电动导体在进料上的固定是:将金属弹簧板的一端连接到电饲料,并将金属弹簧板的另一端连接到辐射元件以耦合方式;或将金属弹簧板的一端连接到地面,并以耦合方式将金属弹簧板的另一端连接到辐射元件;或将金属弹簧板的一端连接到电饲料,然后将金属弹簧板的另一端连接到地面,在那里金属弹簧板和辐射元件以耦合方式连接。 [0057]可以从上述描述中可以理解出隔热膜层20在隔热后壳体上10用作辐射元件的载体30天线和辐射元件30位于整个移动终端内,从而有效地增加了辐射元件的高度30天线相对于电路板的天线不影响移动端子的外观。与常规支撑溶液相比,这种方式可以增加约0.2 mm至0.6毫米的高度,从而减少了由金属成分对电路板对天线辐射的影响,并进一步提高天线的带宽和效率天线可以覆盖手持通信系统中使用的频带。另外,在天线中,电导器与辐射元件之间的电连接以耦合方式实现。与某种方式相比,在一般常规溶液中,电路板的信号线直接连接到天线,以耦合方式喂食可以避免由直接电 - 连接进料引起的问题,例如不均匀的接触压力和A由于氧化等因素,在长时间后,接触点的阻抗变得不稳定。 [0058]上述描述仅仅是实施方案,但并不是限制的。在艺术中有普通技能的人易于弄清楚的任何变异或替代品均应属于实施方案的范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:48.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN110784564A(String), CN110784564B(String), CN111509367A(String), CN111509367B(String), CN112534796A(String), EP3709610A1(String), EP3709610A4(String), US11450946B2(String), US20200335854A1(String), US20220368007A1(String), WO2020024925A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN110784564A(String), CN110784564B(String), CN111509367A(String), CN111509367B(String), CN112534796A(String), EP3709610A1(String), EP3709610A4(String), US11450946B2(String), US20200335854A1(String), US20220368007A1(String), WO2020024925A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.034 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20220368007A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.069 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN110784564A(String), CN110784564B(String), CN111509367A(String), CN111509367B(String), CN112534796A(String), EP3709610A1(String), EP3709610A4(String), US11450946B2(String), US20200335854A1(String), US20220368007A1(String), WO2020024925A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), CN110784564A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.125 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), CN110784564B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.159 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), CN111509367A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), CN111509367B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), CN112534796A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), EP3709610A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), EP3709610A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), US11450946B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), US20200335854A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), US20220368007A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.439 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271669(Integer), WO2020024925A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20220368007A1(String), US20220368007A1(String), 1668614400(Integer), 271669(Integer), 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.510 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.511 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.511 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.589 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185997(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 185997(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.658 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.658 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.692 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185997(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 185997(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.865 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:49.882 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.040 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 实质审查(String), 1(Integer), 185997(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10165161B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Bracket assembly for mobile terminal and mobile terminal(String), 移动终端和移动终端支架总成(String), US10165161B2(String), A bracket assembly for use in a mobile terminal includes a metal support and a multi-contact spring. The metal support is configured to support an electronic component of the mobile terminal. The multi-contact spring includes a first pressure contact part, a second pressure contact part, a first elastic part, a second elastic part, and a fixing part. The multi-contact spring is fixed to a frame of the mobile terminal by a fastener extending through the fixing part into the frame. The first elastic part is connected to the first pressure contact part and the fixing part and is configured to provide a first restoring force to the first pressure contact part such that the first pressure contact part abuts against a metal cover of the mobile terminal and is grounded.(String), 一种用于移动终端的支架组件,包括金属支架和多触点弹簧。 金属支架用于支撑移动终端的电子元件。 多触点弹簧包括第一压接部、第二压接部、第一弹性部、第二弹性部和固定部。 多触点弹簧通过延伸穿过固定部进入框架的紧固件固定到移动终端的框架。 第一弹性部连接第一压接部和固定部,用于向第一压接部提供第一回复力,使第一压接部抵靠移动终端的金属盖并接地。 .(String), US15/793588(String), 1508860800(Integer), US10165161B2(String), 1545667200(Integer), 1545667200(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 10(Integer), CN105356077A | CN201995193U | CN202750132U | CN205609765U | US20140111684A1 | US20150062419A1 | US20180176346A1 | US20180176351A1 | US9759988B2 | WO2016032561A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185998(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\bc833b2bd568446c9b0da6047a40c2ba.png(String), 185998(Integer), bc833b2bd568446c9b0da6047a40c2ba.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Bracket assembly for mobile terminal and mobile terminal(String), 移动终端和移动终端支架总成(String), US10165161B2(String), A bracket assembly for use in a mobile terminal includes a metal support and a multi-contact spring. The metal support is configured to support an electronic component of the mobile terminal. The multi-contact spring includes a first pressure contact part, a second pressure contact part, a first elastic part, a second elastic part, and a fixing part. The multi-contact spring is fixed to a frame of the mobile terminal by a fastener extending through the fixing part into the frame. The first elastic part is connected to the first pressure contact part and the fixing part and is configured to provide a first restoring force to the first pressure contact part such that the first pressure contact part abuts against a metal cover of the mobile terminal and is grounded.(String), 一种用于移动终端的支架组件,包括金属支架和多触点弹簧。 金属支架用于支撑移动终端的电子元件。 多触点弹簧包括第一压接部、第二压接部、第一弹性部、第二弹性部和固定部。 多触点弹簧通过延伸穿过固定部进入框架的紧固件固定到移动终端的框架。 第一弹性部连接第一压接部和固定部,用于向第一压接部提供第一回复力,使第一压接部抵靠移动终端的金属盖并接地。 .(String), US15/793588(String), 1508860800(Integer), US10165161B2(String), 1545667200(Integer), 1545667200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 10(Integer), CN105356077A | CN201995193U | CN202750132U | CN205609765U | US20140111684A1 | US20150062419A1 | US20180176346A1 | US20180176351A1 | US9759988B2 | WO2016032561A1(String), \20230420\bc833b2bd568446c9b0da6047a40c2ba.png(String), 20(Integer), 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.725 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.726 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 1. A bracket assembly in a mobile terminal, the mobile terminal comprising a communication element, an electronic component, a frame, and a metal cover, the bracket assembly comprising:a metal support configured to support the electronic component of the mobile terminal; anda multi-contact spring comprising at least one first pressure contact part, at least one second pressure contact part, at least one first elastic part, at least one second elastic part, and at least one fixing part, wherein the multi-contact spring is fixed to the frame of the mobile terminal by the at least one fixing part, the at least one first elastic part is connected to the at least one first pressure contact part and the at least one fixing part and is configured to provide a first restoring force to the at least one first pressure contact part such that the at least one first pressure contact part abuts against the metal cover of the mobile terminal and is grounded, and the at least one second elastic part is connected to the at least one second pressure contact part and the at least one fixing part and is configured to provide a second restoring force to the at least one second pressure contact part such that the at least one second pressure contact part abuts against the metal support so as to ground the metal support to reduce signal interference of the metal support to the communication element.(String), 1.一种移动终端中的支架组件,该移动终端包括通信元件、电子元件、框架和金属盖,支架组件包括:金属支架,用于支撑移动终端的电子部件;和一种多接点弹簧,包括至少一第一压接部、至少一第二压接部、至少一第一弹性部、至少一第二弹性部及至少一固定部,其中,多接点弹簧为至少一固定部固定于移动终端的边框,至少一第一弹性部连接至少一第一压接部及至少一固定部,用以提供第一回复力至少一第一压接部使至少一第一压接部抵接移动终端的金属盖体并接地,至少一第二弹性部连接至少一第二压接部该至少一固定部与该至少一固定部,并用以提供一第二回复力至该至少一第二压接部,以使该至少一第二压接部抵靠该固定部。l支架将金属支架接地,减少金属支架对通讯元件的信号干扰。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 2. The bracket assembly as claimed in claim 1, wherein the at least one fixing part comprises a base piece having a pair of long sides and a pair of short sides connecting the long sides, the at least one first pressure contact part is elastically connected to the short sides by the at least one first elastic part, the base piece extends along one of the long sides and is bent to form a connecting piece, and the at least one second pressure contact part is elastically connected to the connecting piece by the at least one second elastic part.(String), 2.如权利要求1所述的支架组件,其中至少一固定部包括一基片,基片具有一对长边及一对连接长边的短边,至少一第一压接部通过至少一第一弹性件弹性连接至短边。基片沿其中一长边延伸并弯折形成连接片,至少一第二压接部通过至少一第二弹性部弹性连接于连接片。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 3. The bracket assembly as claimed in claim 2, wherein a number of the at least one first pressure contact part is two, a number of the at least one first elastic part is two, and each of the first pressure contact parts is elastically connected to one of the short sides by a respective one of the first elastic parts.(String), 3.如权利要求2所述的支架组件,其中至少一第一压接部的数量为二,至少一第一弹性部的数量为二,且各第一压接部分别通过一短边弹性连接于其中一短边。首先是弹性部件。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 4. The bracket assembly as claimed in claim 3, wherein the mobile terminal comprises a fastener, and the base piece comprises a fixing hole configured to insert the fastener to fix the multi-contact spring to the frame.(String), 4.如权利要求3所述的支架组件,其中移动终端包括固定件,基片包括固定孔,固定孔用于插入固定件以将多触点弹簧固定到框架。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 5. The bracket assembly as claimed in claim 4, wherein the frame comprises a convex part, the base piece extends along another of the long sides and is bent to form a plurality of bending ends, a bending direction of the bending ends with respect to the base piece is the same as a bending direction of the connecting piece, the bending ends, the base piece, and the connecting piece are connected in order, the base piece comprises a receiving space defined by a region among the bending ends, the base piece, and the connecting piece, and the convex part of the frame configured to fix the multi-contact spring is received in the receiving space so as to restrict rotation of the multi-contact spring with respect to the fastener.(String), 5.如权利要求4所述的支架组件,其中框架包括凸部,基部沿另一长边延伸并弯折形成多个弯折端,弯折端相对于基部的弯折方向与基部的弯折方向相同。连接件、弯折端、基件和连接件依次连接,基件包括由弯折端、基件和连接件之间的区域限定的容纳空间,以及凸起部分。用于固定多触点弹簧的框架容纳在容纳空间中以限制多触点弹簧相对于紧固件的转动。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 6. The bracket assembly as claimed in claim 1, wherein the metal support comprises a plurality of side walls connected in order and an accommodating space cooperatively defined by the side walls for accommodating the electronic component, the side walls comprises a wall away from a side of the accommodating space, and the second pressure contact part elastically abuts against the wall.(String), 6.如权利要求1所述的支架组件,其中金属支架包括多个依次连接的侧壁和由侧壁共同限定的容置电子元件的容置空间,侧壁包括远离容置空间一侧的壁,第二压接部弹性地连接。靠在墙上。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 7. The bracket assembly as claimed in claim 6, wherein the frame comprises a slot, and the wall comprises a plurality of fixing blocks convexly disposed on the wall for inserting into the slot of the frame such that the metal support is mounted on the frame.(String), 7.如权利要求6所述的支架组件,其中框架包含一槽孔,壁面包含多个固定块,凸设于壁面,用以插入框架的槽孔内,使金属支架安装于框架上。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 8. The bracket assembly as claimed in claim 1, further comprising a plurality of convex contacts disposed on a top of the first pressure contact part and a top of the second pressure contact part.(String), 8.如权利要求1所述的支架组件,还包括多个凸状接点设置于第一压接部的顶部与第二压接部的顶部。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 9. The bracket assembly as claimed in claim 1, wherein the first pressure contact part, the second pressure contact part, the first elastic part, the second elastic part, and the fixing part are an integral structure integrally formed by bending at least one of a metal material and a metal alloy material.(String), 9.如权利要求1所述的支架组件,其中第一压接部、第二压接部、第一弹性部、第二弹性部和固定部为金属材料和金属合金材料中的至少一种通过弯折一体成型的一体结构。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 10. A mobile terminal, comprising:a communication element disposed in the mobile terminal;a frame;a metal cover, being attached to the frame;an electronic component; anda bracket assembly, comprising:a metal support configured to support the electronic component of the mobile terminal; anda multi-contact spring comprising at least one first pressure contact part, at least one second pressure contact part, at least one first elastic part, at least one second elastic part, and at least one fixing part, wherein the multi-contact spring is fixed to the frame of the mobile terminal by the at least one fixing part, the at least one first elastic part is connected to the at least one first pressure contact part and the at least one fixing part and is configured to provide a first restoring force to the at least one first pressure contact part such that the at least one first pressure contact part abuts against the metal cover of the mobile terminal and is grounded, and the at least one second elastic part is connected to the at least one second pressure contact part and the at least one fixing part and is configured to provide a second restoring force to the at least one second pressure contact part such that the at least one second pressure contact part abuts against the metal support so as to ground the metal support to reduce signal interference of the metal support to the communication element.(String), 10.移动终端一个,包括:设置在移动终端中的通信元件;一个框架;金属盖,附接于框架;电子元件;和支架组件,包括:金属支架,用于支撑移动终端的电子部件;和一种多接点弹簧,包括至少一第一压接部、至少一第二压接部、至少一第一弹性部、至少一第二弹性部及至少一固定部,其中,多接点弹簧为至少一固定部固定于移动终端的边框,至少一第一弹性部连接至少一第一压接部及至少一固定部,用以提供第一回复力至少一第一压接部使至少一第一压接部抵接移动终端的金属盖体并接地,至少一第二弹性部连接至少一第二压接部该至少一固定部与该至少一固定部,并用以提供一第二回复力至该至少一第二压接部,以使该至少一第二压接部抵靠该固定部。l支架将金属支架接地,减少金属支架对通讯元件的信号干扰。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 11. The mobile terminal as claimed in claim 10, wherein the electronic component is a dual camera assembly.(String), 11.如权利要求10所述的移动终端,其中电子元件是双摄像头组件。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 12. The mobile terminal as claimed in claim 10, wherein the at least one fixing part comprises a base piece having a pair of long sides and a pair of short sides connecting the long sides, the at least one first pressure contact part is elastically connected to the short sides by the at least one first elastic part, the base piece extends along one of the long sides and is bent to form a connecting piece, and the at least one second pressure contact part is elastically connected to the connecting piece by the second at least one elastic part.(String), 12.如权利要求10所述的移动终端,其中至少一固定部包括一基片,基片具有一对长边及一对连接长边的短边,至少一第一压接部通过至少一第一弹性件弹性连接至短边。基片沿其中一长边延伸并弯折形成一连接件,至少一第二压接部通过至少一第二弹性件弹性连接于连接件。(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 13. The mobile terminal as claimed in claim 12, wherein a number of the at least one first pressure contact part is two, a number of the at least one first elastic part is two, and each of the first pressure contact parts is elastically connected to one of the short sides by a respective one of the first elastic parts.(String), 13.如权利要求12所述的移动终端,其中至少一第一压接部的数量为二,至少一第一弹性部的数量为二,且各第一压接部分别通过一短边弹性连接于其中一短边。首先是弹性部件。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 14. The mobile terminal as claimed in claim 13, wherein the mobile terminal comprises a fastener, and the base piece comprises a fixing hole configured to insert the fastener to fix the multi-contact spring to the frame.(String), 14.如权利要求13所述的移动终端,其中移动终端包括固定件,基片包括固定孔,固定孔用于插入固定件以将多触点弹簧固定到框架。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 15. The mobile terminal as claimed in claim 14, wherein the frame comprises a convex part, the base piece extends along another of the long sides and is bent to form a plurality of bending ends, a bending direction of the bending ends with respect to the base piece is the same as a bending direction of the connecting piece, the bending ends, the base piece, and the connecting piece are connected in order, the base piece comprises a receiving space defined by a region among the bending ends, the base piece, and the connecting piece, and the convex part of the frame configured to fix the multi-contact spring is received in the receiving space so as to restrict rotation of the multi-contact spring with respect to the fastener.(String), 15.如权利要求14所述的移动终端,其中框架包括凸部,基部沿另一长边延伸并弯折形成多个弯折端,弯折端相对于基部的弯折方向与基部的弯折方向相同。连接件、弯折端、基件和连接件依次连接,基件包括由弯折端、基件和连接件之间的区域限定的容纳空间,以及凸起部分。用于固定多触点弹簧的框架容纳在容纳空间中以限制多触点弹簧相对于紧固件的转动。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 16. The mobile terminal as claimed in claim 10, wherein the metal support comprises a plurality of side walls connected in order and an accommodating space cooperatively defined by the side walls for accommodating the electronic component, the side walls comprises a wall away from a side of the accommodating space, and the second pressure contact part elastically abuts against the wall.(String), 16.如权利要求10所述的移动终端,其中金属支架包括多个依次连接的侧壁和由侧壁共同限定的容置电子元件的容置空间,侧壁包括远离容置空间一侧的壁,第二压接部弹性地连接。靠在墙上。(String), 1(Integer), 15(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 17. The mobile terminal as claimed in claim 16, wherein the frame comprises a plurality of slots surrounding the metal support, and the wall comprises a plurality of fixing blocks convexly disposed on the wall for inserting into the slot of the frame such that the metal support is mounted on the frame.(String), 17.如权利要求16所述的移动终端,其中框架包括围绕金属支架的多个槽,壁包括多个固定块,其凸设在壁上,用于插入框架的槽中,从而将金属支架安装在框架上。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 18. The mobile terminal as claimed in claim 10, further comprising a plurality of convex contacts disposed on a top of the first pressure contact part and a top of the second pressure contact part.(String), 18.如权利要求10所述的移动终端,还包括多个凸状接点设置于第一压接部的顶部与第二压接部的顶部。(String), 1(Integer), 17(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 19. The mobile terminal as claimed in claim 16, wherein the electronic component comprises a first camera lens and a second camera lens arranged side by side with the first camera lens, and the first camera lens and the second camera lens are disposed in the accommodating space.(String), 19.如权利要求16所述的移动终端,其中电子元件包括第一镜头以及与第一镜头并排设置的第二镜头,第一镜头以及第二镜头设置于容置空间内。(String), 1(Integer), 18(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:50.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185998(Integer), 20. The mobile terminal as claimed in claim 19, wherein the metal cover comprises two shooting windows, and the first camera lens and the second camera lens take pictures through a respective window of the two shooting windows.(String), 20.如权利要求19所述的移动终端,其中金属盖体包括两个拍摄窗,第一镜头和第二镜头分别通过两个拍摄窗中的一个窗口进行拍摄。(String), 1(Integer), 19(Integer), 18(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.118 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.136 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185998(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority to Chinese Application No. 201611185479.6 filed Dec. 20, 2016. The entire disclosure of the above application is incorporated herein by reference in its entirety. BACKGROUND [0002]Field [0003]The present disclosure relates to the field of electronic equipment, and particularly to a bracket assembly for a mobile terminal and a mobile terminal having the bracket assembly. [0004]Background [0005]Widespread and growing use of smart phones increases the need for a support to stabilize electronic components, such as a camera device, inside a mobile phone. In consideration of rigidity, size, and installation requirements of the support, a metal support is usually used to stabilize the electronic component. However, because metal is conductive, the metal support easily interferes with electromagnetic signals from communication elements inside the mobile phone, and thus reducing communication performance of the communication elements inside the mobile phone. [0006]In present technology, the metal support, used to stabilize the electronic component inside the mobile phone, reduces user experience. BRIEF DESCRIPTION OF THE DRAWINGS [0007]In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person skilled in the art can obtain other figures according to these figures without paying the premise. [0008]FIG. 1 is an assembled view of a bracket assembly according to an embodiment of the present disclosure. [0009]FIG. 2 is an exploded view of the bracket assembly according to the embodiment of the present disclosure. [0010]FIGS. 3A, 3B, and 3C are schematic views of a multi-contact spring according to the embodiment of the present disclosure. [0011]FIG. 4 is a schematic view of a board according to the embodiment of the present disclosure. [0012]FIG. 5 is a schematic view of a metal support according to the embodiment of the present disclosure. [0013]FIG. 6 is a schematic view of a frame according to the embodiment of the present disclosure. [0014]FIG. 7 is a partially assembled view of a mobile terminal according to the embodiment of the present disclosure. [0015]FIG. 8 is a partially exploded view of the mobile terminal according to the embodiment of the present disclosure. DETAILED DESCRIPTION OF ILLUSTRATED EMBODIMENTS [0016]In combination with the drawings of the embodiments of the present disclosure, the following is related to a detailed and complete description of the technology of the embodiments of the present disclosure. It is obvious that the disclosed embodiments are only a part of the embodiments available to the present disclosure, rather than the all embodiments thereof. Based on the disclosed embodiments of the present disclosure, other embodiments obtained by a person skilled in the art without endeavor of creativity belong to the protected scope of the present embodiments of the present disclosure. [0017]Referring to FIGS. 1, 2, and 3A to 3C, a bracket assembly is disposed in a mobile terminal, and the mobile terminal includes a communication element for receiving or transmitting a signal. The communication element may be a board 30 or an antenna. The bracket assembly includes a metal support 10 and a multi-contact spring 20. The metal support 10 is configured to support an electronic component of the mobile terminal. The electronic component is, for example, a dual camera assembly. The multi-contact spring 20 includes at least one first pressure contact part 201, at least one second pressure contact part 202, at least one first elastic part 203, at least one second elastic part 204, and at least one fixing part 200. The multi-contact spring 20 is fixed to a frame 40 of the mobile terminal by the at least one fixing part 200. The at least one first elastic part 203 is connected to the at least one first pressure contact part 201 and the at least one fixing part 200 and is configured to provide a first restoring force to the at least one first pressure contact part 201 such that the at least one first pressure contact part 201 firmly abuts against a metal cover 60 of the mobile terminal. The at least one second elastic part 204 is connected to the at least one second pressure contact part 202 and the at least one fixing part 200 and is configured to provide a second restoring force to the at least one second pressure contact part 202 such that the at least one second pressure contact part 202 firmly abuts against the metal support 10. The metal support 10 is connected to the metal cover 60 via the multi-contact spring 20 and is grounded. The frame 40 may be a middle frame of the mobile terminal, and the metal cover 60 may be a metal back cover of the mobile terminal. In an embodiment, the mobile terminal may be an electronic equipment such as a mobile phone, a notebook computer, a tablet computer, etc. [0018]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with a ground electrode of the metal cover 60 without changing mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced, to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0019]Further, the multi-contact spring 20 connects current of the metal support 10 to the ground electrode of the metal cover 60. The multi-contact spring 20 can, on the one hand, reduce the overall electric potential of the metal support 10 and, on the other hand, static electricity of the metal support 10 is guided to the ground electrode so as to prevent the static electricity of the metal support 10 from flowing to the electronic component, to protect the electronic component. The ground electrode may be exposed copper on the board 30. The metal cover 60 is in communication with the board 30, and the first pressure contact part 201 of the multi-contact spring 20 abuts against the metal cover 60 to communicate with the exposed copper of the board 30. [0020]In an embodiment, the at least one fixing part 200 includes a base piece 200a having a pair of long sides 2001 and a pair of short sides 2002 connecting the long sides 2001. The at least one first pressure contact part 201 is elastically connected to the short sides 2002 by the at least one first elastic part 203, the base piece 200a extends along one of the long sides 2001 and is bent to form a connecting piece 200b, and the at least one second pressure contact part 202 is elastically connected to the connecting piece 200b by the at least one second elastic part 202. In an embodiment, the base piece 200a is a long strip, the pair of long sides 2001 are parallel to each other, and the pair of short sides 2002 are parallel to each other. The first pressure contact part 201 is elastically connected to an edge of the short side 2002 by the first elastic part 203. The first elastic part 203 applies an elastic force to the first pressure contact part 201, and when the first pressure contact part 201 is subjected to pressure opposite to a direction of the elastic force provided by the first elastic part 203, the first elastic part 203 causes the first pressure contact part 201 to firmly abuts against an object, which applies pressure to the first pressure contact part 201. In the embodiment, the object for applying pressure to the first pressure contact part 201 may be the metal cover 60. One of the long sides 2001 of the base piece 200a extends and is bent to form the connecting piece 200b. The connecting piece 200b is at an angle to the base piece 200a. For example, the connecting piece 200b and the base piece 200a are perpendicular to each other. The connecting piece 200b is connected to the second pressure contact part 202 and the fixing part 200. In detail, the second pressure contact part 202 is elastically connected to the connecting piece 200b by the second elastic part 204. The second elastic part 204 applies an elastic force to the second pressure contact part 202, and when the second pressure contact part 202 is subjected to pressure opposite to a direction of the elastic force provided by the second elastic part 204, the second elastic part 204 causes the second pressure contact part 202 to firmly abuts against an object, which applies pressure to the second pressure contact part 202. In the embodiment, the object for applying pressure to the second pressure contact part 202 may be the metal support 10. [0021]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with the ground electrode of the metal cover 60 without changing the mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0022]Further, a number of the at least one first pressure contact part 201 is two, a number of the at least one first elastic part 203 is two, and each of the first pressure contact parts 201 is elastically connected to one of the short sides 2002 by a respective one of the first elastic parts. The two first pressure contact parts 201 abut against a housing of the mobile terminal such that the metal support 10 is grounded, a number of contacts is increased, the overall electric potential of the metal support 10 is reduced, and interference of electromagnetic signals from the communication elements is reduced. [0023]Referring to FIGS. 3 and 4, in the embodiment, the bracket assembly includes a fastener 70, the base piece 200a includes a fixing hole 2003, and the frame 40 includes a convex part 400 having a threaded hole 402 configured to fix the multi-contact spring 20 to the convex part 400 by the fastener 70. In an embodiment, the fastener 70 may be a screw. The base piece 200a is locked to the frame 40 by the screw such that the multi-contact spring 20 is securely fixed to the frame 40. Therefore, the first pressure contact part 201 can stably abut against the metal cover 60, the second pressure contact part 202 can stably abut against the metal support 10, and structural stability of the bracket assembly is improved. [0024]In addition, the base piece 200a extends along another of the long sides 2001 and is bent to form a plurality of bending ends, a bending direction of the bending ends with respect to the base piece 200a is the same as a bending direction of the connecting piece 200b. The bending ends, the base piece 200a, and the connecting piece 200b are connected in order, the base piece 200a includes a receiving space defined by a region among the bending ends, the base piece 200a, and the connecting piece 200b. The convex part 400 of the frame 40 is received in the receiving space to restrict rotation of the multi-contact spring 20. In another embodiment, a number of the bent ends of each of the multi-contact spring 20 is two for firmly fixing the multi-contact spring 20 and the frame 40. [0025]Referring to FIG. 5, in the embodiment, the metal support 10 includes a plurality of side walls 102 connected in order and an accommodating space 11 cooperatively defined by the side walls 102 for accommodating the electronic component. In detail, the metal support 10 accommodates the electronic component to facilitate installation and stabilization of the electronic component. The electronic component may be a camera module, a speaker, a fingerprint module, a connector, etc. [0026]Further, the metal support 10 has a rectangular block shape. The metal support 10 may be made of aluminum alloy material, silver material, or iron material, etc. The metal support 10 is formed by shaping a metal block using an automatic numerical control milling process. That is, forming dimensions of the side walls 102 are machined by the numerical control milling process such that dimensional accuracy of the side wall 102 is high, the electronic component can be effectively stabilized and precisely positioned, and the position of the electronic component can be easily calibrated. In addition, the metal support 10 can also be effectively fixed to an external member such that the fixing position of the metal support 10 is precise and the metal support 10 is conveniently positioned. Therefore, the mounting position of the electronic component can be accurately improved and performance of the electronic component can be improved. The accommodating space 11 can accommodate one electronic component, two electronic components, or a plurality of electronic components such that the metal support 10 can fix the plurality of electronic components centrally to save space. [0027]In the embodiment, the side walls 102 include a wall away from a side of the accommodating space 11, and a pressure contact part (including the first pressure contact part 201 and the second pressure contact part 202) elastically abuts against the wall. Restoring force applied to the pressure contact part by an elastic part (including the first elastic part 203 and the second elastic part 204) causes the pressure contact part to firmly abut against the wall of the side wall 102 of the metal support 10 to ensure that the pressure contact part and the metal support 10 can be brought into stable contact. Therefore, loose contact between the multi-contact spring 20 and the metal support 10 does not occur easily when using the mobile terminal, and the structural stability of the mobile terminal is improved. In addition, the pressure contact part elastically contacts the wall of the metal support 10 to facilitate installation and removal of the metal support 10. The metal support 10 is removed from the mobile terminal by simply pulling out the metal support 10 in a direction perpendicular to the pressure contact part against the side wall 102. The metal support 10 is mounted on the mobile terminal by simply pushing the pressure contact part in advance and placing the metal support 10 in the mobile terminal. The difficulty of installation and removal of the metal support 10 is reduced. [0028]Referring to FIG. 6, in the embodiment, the bracket assembly is applied to the mobile terminal, and the metal support 10 is fixed to the frame 40. In detail, the wall away from a side of the accommodating space 11 includes a plurality of fixing blocks 104 convexly disposed on the wall. The frame 40 includes a plurality of slots 404 corresponding to the fixing blocks 104 for inserting the fixing blocks 104 such that the metal support 10 is mounted on the frame 40. The fixing blocks 104 of the metal support 10 engage with the slots 404 such that the metal support 10 is securely mounted on the frame 40 to improve structural stability of the mobile terminal. [0029]In the embodiment, the bracket assembly includes a plurality of convex contacts disposed on a top of the pressure contact part, and the convex contacts increases a contact area between the pressure contact part and the metal support 10, such that the pressure contact part firmly abuts against the side wall 102 of the metal support 10. [0030]In the embodiment, the first pressure contact part 201, the second pressure contact part 202, the first elastic part 203, the second elastic part 204, and the fixing part 200 are an integral structure integrally formed by bending at least one of a metal material and a metal alloy material. Therefore, manufacturing process of the elastic device is simplified and production materials of the elastic device is saved. [0031]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with a ground electrode of the metal cover 60 without changing a mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0032]Referring to FIGS. 7 and 8, an embodiment of the disclosure includes a mobile terminal 100. The mobile terminal 100 includes the metal cover 60, the board 30, the frame 40, and the bracket assembly. The multi-contact spring 20 is fixed to the frame 40, the first pressure contact part abuts against the grounded metal cover 60. The board 30 includes a ground electrode. The metal cover 60 is connected to the board 30. The second pressure contact part abuts against the metal support 10 to ground the metal support 10. The multi-contact spring 20 is fixed to the frame 40 of the mobile terminal 100 by the at least one fixing part 200. The at least one first elastic part 203 is connected to the at least one first pressure contact part 201 and the at least one fixing part 200 and is configured to provide a first restoring force to the at least one first pressure contact part 201 such that the at least one first pressure contact part 201 firmly abuts against the metal cover 60 of the mobile terminal 100. The at least one second elastic part 204 is connected to the at least one second pressure contact part 202 and the at least one fixing part 200 and is configured to provide a second restoring force to the at least one second pressure contact part 202 such that the at least one second pressure contact part 202 firmly abuts against the metal support 10. The metal support 10 is connected to the metal cover 60 via the multi-contact spring 20 and is grounded. The overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0033]The metal support 10 is configured to support an electronic component of the mobile terminal 100. The electronic component is for example a dual camera assembly 50. The electronic component includes a first camera lens 52 and a second camera lens 54 arranged side by side with the first camera lens 52, and the first camera lens 52 and the second camera lens 54 are disposed in the accommodating space 11 of the metal support 10. In detail, an image optical axis of the first camera lens 52 and an image optical axis of the second camera lens 54 are parallel such that the first camera lens 52 and the second camera lens 54 can be operated in concert to improve picture taking performance. [0034]In the embodiment, the frame 40 is used to fix the metal support 10. In detail, the wall away from a side of the accommodating space 11 includes a plurality of fixing blocks 104 convexly disposed on the wall. The frame 40 includes a plurality of slots 404 corresponding to the fixing blocks 104 for inserting the fixing blocks 104 such that the metal support 10 is mounted on the frame 40. The fixing blocks 104 of the metal support 10 engage with the slots 404 such that the metal support 10 is securely mounted on the frame 40 to improve structural stability of the mobile terminal. [0035]In the embodiment, the metal cover 60 is attached to the frame 40, and the board 30 is fixed between the metal cover 60 and the frame 40 for covering and protecting the electronic component inside the mobile terminal 100, and thus increasing appearance of the mobile terminal 100. The metal cover 60 may be a metal plate. Further, the metal cover 60 includes two shooting windows, and the first camera lens 52 and the second camera lens 54 take pictures through a respective window of the two shooting windows 62 to realize picture taking. In the embodiment, the shooting window 62 is a camera lens. [0036]The fixing part 200 of the multi-contact spring 20 is stably fixed to the frame 40, the first pressure contact part 201 firmly abuts against the metal cover 60, and the second pressure contact part 202 firmly abuts against the metal support 10, such that the metal support 10 is electrically connected to the metal cover 60. The metal cover 60 is grounded, and the metal support 10 is in communication with a ground electrode of the metal cover 60 without changing a mounting structure of the metal support 10 so that the overall electric potential of the metal support 10 is reduced to improve interference with electromagnetic signals from the communication element and thus increase user experience. [0037]The foregoing descriptions are merely exemplary embodiments of the present disclosure, rather than limiting the present disclosure. Various modifications and alterations may be made to the present disclosure for a person skilled in the art. Any modification, equivalent substitution, improvement or the like made within the spirit and principle of the present disclosure shall fall into the protection scope of the present disclosure.(String), 相关申请的交叉引用 [0001] 本申请要求于2016年12月20日提交的中国申请第201611185479.6号的优先权。上述申请的全部公开内容以引用的方式整体并入本文。 背景 [0002] 场地 [0003] 本发明涉及电子设备领域,尤其涉及一种用于移动终端的支架组件及具有该支架组件的移动终端。 [0004] 背景 [0005] 智能手机的广泛和不断增长的使用增加了对稳定手机内部电子元件(例如相机设备)的支持的需求。 考虑到支架的刚性、尺寸和安装要求,通常采用金属支架来稳定电子元件。 然而,由于金属具有导电性,金属支架容易干扰手机内部通讯元件的电磁信号,从而降低手机内部通讯元件的通讯性能。 [0006] 在现有技术中,用于稳定手机内部电子元件的金属支架降低了用户体验。 附图的简要说明 [0007] 为了更清楚地说明本发明或相关技术的实施例,下面对实施例中描述的附图进行简单介绍。 显然,附图只是本发明的一些实施例,本领域技术人员可以在不付出任何前提下,根据这些附图获得其他附图。 [0008] 图1是根据本发明实施例的支架组件的组装图。 [0009] 图2是根据本发明实施例的支架组件的分解图。 [0010] 图3A、3B和3C是根据本发明实施例的多触点弹簧的示意图。 [0011] 图4为本发明实施例提供的单板示意图。 [0012] 图5为本发明实施例的金属支架的示意图。 [0013] 图6是根据本发明实施例的框架的示意图。 [0014] 图7是根据本发明实施例的移动终端的部分组装图。 [0015] 图8是根据本发明实施例的移动终端的部分分解图。 图示实施例的详细说明 [0016] 下面结合本发明实施例的附图,对本发明实施例的技术进行详细、完整的描述。 显然,所公开的实施例只是本发明可以使用的一部分实施例,而不是全部的实施例。 基于本发明中所公开的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明实施例保护的范围。 [0017] 参考图1、2和3A至3C,支架组件设置在移动终端中,并且移动终端包括用于接收或发送信号的通信元件。 通信元件可以是板 30 或天线。 支架组件包括金属支架 10 和一个多触点弹簧 20 . 金属支撑 10 被配置为支持移动终端的电子组件。 电子元件例如是双摄像头组件。 多触点弹簧 20 包括至少一个第一压力接触部分 201 ,至少一个第二压力接触部分 202 ,至少一个第一弹性部 203 ,至少一第二弹性部 204 ,以及至少一个固定部 200 . 多触点弹簧 20 固定在一个框架上 40 移动终端通过至少一个固定部 200. 至少一个第一弹性部 203 连接至至少一第一压接部 201 以及至少一固定部 200 并且被配置为向至少一个第一压力接触部分提供第一恢复力 201 使得至少一个第一压力接触部分 201 牢固地靠在金属盖上 60 的移动终端。 至少一第二弹性部 204 连接至至少一第二压接部 202 以及至少一固定部 200 并且被配置为向至少一个第二压力接触部分提供第二恢复力 202 使得至少一第二压接部 202 牢固地紧靠在金属支架上 10 . 金属支撑 10 连接到金属盖 60 通过多触点弹簧 20 并且接地。 框架 40 可以是移动终端的中框,金属盖板 60 可以是移动终端的金属后盖。 在一个实施例中,移动终端可以是手机、笔记本电脑、平板电脑等电子设备。 [0018] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极连通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少,以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0019] 此外,多触点弹簧 20 连接金属支架的电流 10 到金属盖的接地电极 60 . 多触点弹簧 20 一方面可以降低金属支架的整体电势 10 另一方面,金属支架的静电 10 引导至接地电极,以防止金属支架产生静电 10 不流入电子元件,保护电子元件。 接地电极可能是板上裸露的铜 30 . 金属盖 60 正在与董事会沟通 30 , 和第一压力接触部分 201 多触点弹簧 20 紧靠金属盖 60 与电路板的裸露铜进行通信 30 . [0020] 在一个实施例中,所述至少一个固定部 200 包括一个基础件 200 a 有一对长边 2001 和一对短边 2002 连接长边 2001 . 至少一个第一压接部 201 弹性连接到短边 2002 由至少一个第一弹性部 203 , 基础件 200 a 沿长边之一延伸 2001 并弯曲形成连接件 200 b ,以及至少一第二压接部 202 与连接件弹性连接 200 b 由至少一第二弹性部 202 . 在一个实施例中,基件 200 a 是一条长条,一对长边 2001 彼此平行,并且一对短边 2002 彼此平行。 第一压接部分 201 弹性连接到短边的边缘 2002 由第一弹性部分 203 . 第一弹性部分 203 对第一压接部施加弹力 201 ,而当第一个压力接触部分 201受到与第一弹性部提供的弹力方向相反的压力 203 ,第一弹性部分 203 导致第一个压力接触部分 201 牢固地抵靠在第一压力接触部分上的物体上 201 . 在本实施例中,用于对第一压接部施加压力的物体 201 可能是金属盖 60 . 长边之一 2001 基础件 200 a 延伸并弯曲形成连接件 200 b . 连接件 200 b 与底座成一定角度 200 a . 例如连接件 200 b 和基础件 200 a 是相互垂直的。 连接件 200 b 与第二压接部连接 202 和固定部分 200 . 详细地说,第二压接部分 202 与连接件弹性连接 200 b 通过第二弹性部分 204 . 第二弹性部分 204 对第二压接部施加弹力 202 ,而当第二个压力接触部分 202 受到与第二弹性部提供的弹力方向相反的压力 204 , 第二弹性部分 204 导致第二个压力接触部分 202 牢固地抵靠在物体上,从而对第二压力接触部分施加压力 202 . 在本实施例中,用于对第二压接部施加压力的物体 202 可能是金属支架 10 . [0021] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极相通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0022] 进一步地,所述至少一个第一压接部的若干个 201 为二,至少一个第一弹性部的数量 203 为二,各第一压接部 201 弹性连接到短边之一 2002 通过相应的一个第一弹性部分。 两个第一压接件 201 紧靠移动终端的外壳,使得金属支架 10 接地,触点数量增加,金属支架的整体电势 10 减少,并且减少来自通信元件的电磁信号的干扰。 [0023] 参考图3和图4,在本实施例中,支架组件包括紧固件 70 , 基础件 200 a 包括一个固定孔 2003 , 和框架 40 包括一个凸出部分 400 有螺纹孔 402 配置固定多触点弹簧 20 到凸出部分 400 由紧固件 70 . 在一个实施例中,紧固件 70 可能是螺丝。 基础件 200 a 锁定在框架上 40 通过螺钉使多触点弹簧 20 牢固地固定在框架上 40 . 因此,第一压力接触部分 201 可以稳定地抵靠在金属盖上 60 ,第二压力接触部分 202 可以稳定地抵靠在金属支架上 10 ,提高了支架总成的结构稳定性。 [0024] 此外,基础件 200 a 沿着另一个长边延伸 2001弯折形成多个弯折端,弯折端相对于基件的弯折方向 200 a 与连接件的弯曲方向相同 200 b . 弯曲端,基片 200 a , 和连接件 200 b 按顺序连接,基片 200 a 包括由弯曲端之间的区域限定的接收空间,基件 200 a , 和连接件 200 b . 凸出部分 400 框架的 40 容纳在容纳空间中以限制多触点弹簧的旋转 20 . 在另一个实施例中,每个多触点弹簧的弯曲端的数量 20 是两个用于牢固固定多触点弹簧 20 和框架 40 . [0025] 参见图5,在本实施例中,金属支架 10 包括多个侧壁 102 有序连接和容纳空间 11 由侧壁共同定义 102 用于容纳电子元件。 详细来说,金属支架 10 容置电子元件,以方便电子元件的安装和稳定。 电子元件可以是摄像头模块、扬声器、指纹模块、连接器等。 [0026] 此外,金属支撑 10 具有矩形块形状。 金属支撑 10 可由铝合金材料、银材料或铁材料等制成。金属支架 10 是通过使用自动数控铣削工艺对金属块进行成型而形成的。 即,形成侧壁的尺寸 102 采用数控铣削工艺加工,使侧壁的尺寸精度 102 高,能有效稳定电子元件并精确定位,容易校准电子元件的位置。 此外,金属支架 10 也可以有效地固定在外部构件上,使金属支架的固定位置 10 是精确的和金属支持 10 位置方便。 因此,可以准确地改进电子元件的安装位置,并且可以提高电子元件的性能。 容纳空间 11 可以容纳一个电子元件、两个电子元件或多个电子元件,使得金属支架 10 可将多个电子元件集中固定,节省空间。 [0027] 在本实施例中,侧壁 102 包括远离容纳空间一侧的墙壁 11 ,以及压接部(包括第一压接部 201 第二压接部 202 ) 弹性地靠在墙上。 由弹性部(包括第一弹性部)对压接部施加的恢复力 203 和第二弹性部分 204 ) 使压接部分牢固地抵靠在侧壁的壁上 102 金属支架的 10 确保压接部分和金属支架 10 可以稳定接触。 因此,多触点弹簧之间的接触松动 20 和金属支架 10 在使用移动终端时不易发生,提高了移动终端的结构稳定性。 此外,压接部与金属支架的壁弹性接触。 10 便于金属支架的安装和拆卸 10 . 金属支撑 10 只需拉出金属支架即可从移动终端上取下 10 在垂直于压力接触部分靠在侧壁上的方向上 102 . 金属支撑 10 只需预先推动压接部分并放置金属支架即可安装在移动终端上 10 在移动端。 金属支架安装和拆卸的难点 10 降低了。 [0028]参见图6,在本实施例中,支架组件应用于移动终端,金属支架 10 固定在框架上 40 . 详细地,远离容纳空间一侧的墙壁 11 包括多个固定块 104 凸设置在墙上。 框架 40 包括多个插槽 404 对应固定块 104 用于插入固定块 104 这样金属支撑 10 安装在框架上 40 . 固定块 104 金属支架的 10 与插槽啮合 404 这样金属支撑 10 牢固地安装在框架上 40 提高移动终端的结构稳定性。 [0029] 在本实施例中,支架组件包括多个凸接点,凸接点设置于压接部的顶部,凸接点增加压接部与金属支架的接触面积。 10 ,使压接部牢固地抵靠在侧壁上 102 金属支架的 10 . [0030] 在本实施例中,第一压接部 201 ,第二压力接触部分 202 ,第一弹性部分 203 , 第二弹性部分 204 , 和固定部分 200 是通过弯曲金属材料和金属合金材料中的至少一种而一体形成的整体结构。 因此,简化了弹性装置的制造工艺,节省了弹性装置的生产材料。 [0031] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极连通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0032] 参见图7和图8,本发明实施例包括一种移动终端 100 . 移动终端 100 包括金属盖 60 , 董事会 30 , 框架 40 , 和支架组件。 多触点弹簧 20 固定在框架上 40 ,第一压接部抵靠接地金属盖 60 . 董事会 30 包括接地电极。 金属盖 60 连接到电路板 30 . 第二压接部抵靠金属支架 10 将金属支架接地 10 . 多触点弹簧 20 固定在框架上 40 移动终端的 100 由至少一个固定部分 200 . 至少一个第一弹性部 203 连接至至少一第一压接部 201 以及至少一固定部 200 并且被配置为向至少一个第一压力接触部分提供第一恢复力 201 使得至少一个第一压力接触部分 201 紧贴金属盖 60 移动终端的 100 . 至少一第二弹性部 204 连接至至少一第二压接部 202 以及至少一固定部 200 并且被配置为向至少一个第二压力接触部分提供第二恢复力 202 使得至少一第二压接部 202 牢固地紧靠在金属支架上 10 . 金属支撑 10 连接到金属盖 60 通过多触点弹簧 20 并且接地。 金属载体的总电势 10减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0033] 金属支撑 10 用于支持移动终端的电子元件 100 . 电子元件例如是双摄像头组件 50 . 电子元件包括第一相机镜头 52 和第二个相机镜头 54 与第一个相机镜头并排排列 52 , 和第一个相机镜头 52 和第二个相机镜头 54 设置于容置空间内 11 金属支架的 10 . 具体地,第一摄像镜头的图像光轴 52 第二镜头的影像光轴 54 是平行的,使得第一个相机镜头 52 和第二个相机镜头 54 可以协同操作,提高拍照性能。 [0034] 在本实施例中,框架 40 用于固定金属支架 10 . 详细地,远离容纳空间一侧的墙壁 11 包括多个固定块 104 凸设置在墙上。 框架 40 包括多个插槽 404 对应固定块 104 用于插入固定块 104 这样金属支撑 10 安装在框架上 40 . 固定块 104 金属支架的 10 与插槽啮合 404 这样金属支撑 10 牢固地安装在框架上 40 提高移动终端的结构稳定性。 [0035] 在本实施例中,金属罩 60 附在框架上 40 , 和董事会 30 固定在金属盖之间 60 和框架 40 用于覆盖和保护移动终端内部的电子元件 100 ,从而增加移动终端的外观 100 . 金属盖 60 可能是金属板。 此外,金属盖 60 包括两个拍摄窗口和第一个相机镜头 52 和第二个相机镜头 54 通过两个拍摄窗口各自的窗口拍照 62 实现拍照。 在本实施例中,拍摄窗口 62 是相机镜头。 [0036] 固定部分 200 多触点弹簧 20 稳固地固定在框架上 40 ,第一压力接触部分 201 紧贴金属盖 60 , 和第二压力接触部分 202 牢固地紧靠在金属支架上 10 , 这样金属支撑 10 电性连接金属盖 60 . 金属盖 60 接地,金属支架 10 与金属盖的接地电极连通 60 不改变金属支架的安装结构 10 使金属支架的总电势 10 减少以改善对来自通信元件的电磁信号的干扰,从而增加用户体验。 [0037] 以上所述仅为本发明的较佳实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,可以对本公开进行各种修改和改变。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106603765A(String), CN106603765B(String), EP3340585A1(String), EP3340585B1(String), ES2729033T3(String), IN201714040209A(String), IN406229B(String), US10165161B2(String), US20180176426A1(String), WO2018113141A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106603765A(String), CN106603765B(String), EP3340585A1(String), EP3340585B1(String), ES2729033T3(String), IN201714040209A(String), IN406229B(String), US10165161B2(String), US20180176426A1(String), WO2018113141A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10165161B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106603765A(String), CN106603765B(String), EP3340585A1(String), EP3340585B1(String), ES2729033T3(String), IN201714040209A(String), IN406229B(String), US10165161B2(String), US20180176426A1(String), WO2018113141A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), CN106603765A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), CN106603765B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.483 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), EP3340585A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.518 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), EP3340585B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), ES2729033T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), IN201714040209A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.623 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), IN406229B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.657 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.658 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.658 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), US10165161B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), US20180176426A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271670(Integer), WO2018113141A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10165161B2(String), US10165161B2(String), 1545667200(Integer), 271670(Integer), 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.878 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185998(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 1(Integer), 185998(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:51.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185998(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 2(Integer), 185998(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.103 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 185998(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20070111710A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Automotive mobile terminal connection system providing mobile terminal function to enable dynamic external user interface(String), 汽车移动终端连接系统提供移动终端功能以启用动态外部用户界面(String), US20070111710A1(String), There is provided a method and device of adapting a phone functionality matrix of an automotive mobile terminal connection device to function capabilities of a mobile terminal device connected to said automotive mobile terminal connection device, comprising the steps of receiving data containing an indication about said function capabilities supported by said mobile terminal device, and rewriting said phone functionality matrix according to said received data.(String), 提供了一种使汽车移动终端连接设备的电话功能矩阵适应连接到所述汽车移动终端连接设备的移动终端设备的功能能力的方法和设备,包括接收包含关于所述功能能力的指示的数据的步骤 由所述移动终端设备支持,并根据所述接收到的数据重写所述电话功能矩阵。(String), US10/570528(String), 1062950400(Integer), US20070111710A1(String), 1179331200(Integer), 美国(String), 2(Integer), 7(Integer), 27(Integer), US20010011033A1 | US20040203636A1 | US20060094455A1 | US20070060111A1 | US20070293258A1 | US5175869A | US5410739A | US5493703A | US5535274A | US5548802A | US5694318A | US5794161A | US5895431A | US5940775A | US6122502A | US6223062B1 | US6226497B1 | US6266544B1 | US6349223B1 | US6449475B1 | US6501949B1 | US6832099B2 | US6892051B2 | US6952576B2 | US7116939B1 | US7257426B1 | US7308289B2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 185999(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.887 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\ea96e85adbf048589857b7700746ba60.png(String), 185999(Integer), ea96e85adbf048589857b7700746ba60.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.939 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Automotive mobile terminal connection system providing mobile terminal function to enable dynamic external user interface(String), 汽车移动终端连接系统提供移动终端功能以启用动态外部用户界面(String), US20070111710A1(String), There is provided a method and device of adapting a phone functionality matrix of an automotive mobile terminal connection device to function capabilities of a mobile terminal device connected to said automotive mobile terminal connection device, comprising the steps of receiving data containing an indication about said function capabilities supported by said mobile terminal device, and rewriting said phone functionality matrix according to said received data.(String), 提供了一种使汽车移动终端连接设备的电话功能矩阵适应连接到所述汽车移动终端连接设备的移动终端设备的功能能力的方法和设备,包括接收包含关于所述功能能力的指示的数据的步骤 由所述移动终端设备支持,并根据所述接收到的数据重写所述电话功能矩阵。(String), US10/570528(String), 1062950400(Integer), US20070111710A1(String), 1179331200(Integer), 美国(String), 2(Integer), 2(Integer), 7(Integer), 27(Integer), US20010011033A1 | US20040203636A1 | US20060094455A1 | US20070060111A1 | US20070293258A1 | US5175869A | US5410739A | US5493703A | US5535274A | US5548802A | US5694318A | US5794161A | US5895431A | US5940775A | US6122502A | US6223062B1 | US6226497B1 | US6266544B1 | US6349223B1 | US6449475B1 | US6501949B1 | US6832099B2 | US6892051B2 | US6952576B2 | US7116939B1 | US7257426B1 | US7308289B2(String), \20230420\ea96e85adbf048589857b7700746ba60.png(String), 20(Integer), 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:52.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 185999(Integer), 1. Method of adapting a phone functionality matrix of an automotive mobile terminal connection device to function capabilities of a mobile terminal device connected to said automotive mobile terminal connection device, comprising: receiving data containing an indication about said function capabilities supported by said mobile terminal device; rewriting said phone functionality matrix according to said received data; and sending said functionality matrix to a central car controller to enable said central car controller to build a user interface corresponding to said functionality matrix. 2. Method according to claim 1, wherein said data containing said indication of said function capabilities is received from a mobile terminal cradle. 3. Method according to claim 1, further comprising requesting said data containing said indication of said function capabilities from said mobile terminal device. 4. Method according to claim 1, wherein said data containing said indication of said function capabilities is received from said mobile terminal device by requesting type and software version thereof. 5. Method according to claim 1, wherein said data containing said indication of said function capabilities is provided to said automotive mobile terminal connection device by said mobile terminal cradle which derives type and software version from said mobile terminal device. 6. (canceled) 7. Software tool comprising program code means stored on a computer readable medium for carrying out the method of claim 1, when said software tool is run on a computer or network device. 8. Computer program product comprising program code means stored on a computer readable medium for carrying out the method of claim 1 when said program product is run on a computer or network device. 9. Computer program product comprising program code, downloadable from a server for carrying out the method of claim 1 when said program product is run on a computer or network device. 10. Computer data signal embodied in a carrier wave and representing a program that instructs a computer to perform the steps of the method of claim 1. 11. Automotive mobile terminal connection device, comprising an interface adapted to connect with a central car controller, a connector adapted to connect with a mobile terminal cradle which is adapted for physically receiving a mobile terminal device, characterized by a phone functionality matrix which comprises an indication of function capabilities of said mobile terminal device. 12. Automotive mobile terminal connection device according to claim 11, adapted to request data from said mobile terminal device, said data containing an indication of said function capabilities. 13. Automotive mobile terminal connection device according to claim 11, adapted to request said data containing said indication about said function capabilities of said mobile terminal device from said mobile terminal cradle. 14. Automotive mobile terminal connection device according to claim 11, adapted to request type and software version of said mobile terminal device. 15. Mobile terminal cradle for physically receiving a mobile terminal device, comprising a connector adapted to connect to an automotive mobile terminal connection device and an interface device adapted to request data from and send data to said mobile terminal device. 16. Mobile terminal cradle according to claim 15, adapted to request data from said mobile terminal device, said data containing an indication about function capabilities of said mobile terminal device. 17. Mobile terminal cradle according to claim 15, comprising a storage containing an indication about said function capabilities of said mobile terminal device. 18. Mobile terminal cradle according to claim 15, further comprising a processor adapted to convert a communication protocol of said mobile terminal device into a communication protocol supported by said automotive mobile terminal connection device. 19. Mobile terminal cradle according to claim 15, further comprising a charger adapted to charge the battery of said mobile terminal. 20. Mobile terminal cradle according to claim 15, adapted to provide a predetermined type of mobile terminal interface to said automotive mobile terminal connection device irrespective of the interface of the connected mobile terminal device.(String), 1.使汽车移动终端连接设备的电话功能矩阵适应与所述汽车移动终端连接设备连接的移动终端设备的功能能力的方法,包括:接收包含关于所述移动终端设备支持的所述功能能力的指示的数据;根据所述接收数据重写所述电话功能矩阵;以及将所述功能矩阵发送到中央汽车控制器,以使所述中央汽车控制器能够建立与所述功能矩阵相对应的用户界面。(String), 1(Integer), 0(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.065 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 185999(Integer), [0001] The present invention relates to an automotive connection system to integrate a mobile phone terminal into the phone control systems of a car. More specifically, it relates to an connection system that is suitable to obtain and provide information about the mobile terminal function capabilities, thereby making it possible to build a corresponding user interface matching the specific features of the mobile terminal. [0002] As mobile terminals like mobile phones and PDAs have become very popular, the desire has aroused to use such terminals in a vehicle environment. Because usually the vehicles driver is the main user of the terminal, the necessity exists to operate the terminal in a kind of handsfree mode. To minimize the risks of using a mobile terminal during driving that are mainly due to the distraction caused by operating a terminal while at the same time controlling the car, different holder devices have been constructed. These range from rather simple mechanical holders, whose only purpose is to place the mobile terminal in an optimal position to the driver, to very sophisticated devices. The latter ones utilize certain internal car systems like the audio system, displays like those belonging to a navigation system, or controls, for example buttons placed on the steering wheel. The speakers of the audio system may so be used for playback purposes, while installed controls may suit to operate the terminal instead of using the terminals own controls. [0003] These common mobile terminal car integration kits suffer from one major drawback that is interoperability. Integrating such kits into a car might be a quite expensive and complicated task. Since they have to be adapted both to the specific type of car and the type of terminal, an obvious problem arises. While the average lifespan of a car may be about 10 years or more, typical product cycles of mobile terminals are much shorter, at best about 1-3 years. Buying a new terminal from the same manufacturer or even from a different manufacturer will most certainly lead to also purchasing a new car integration kit. That is because such kits, the more sophisticated they are, the more likely, they are adapted to both the proprietary communication protocol of the corresponding terminal and the also proprietary communication protocol of the car, or in other words the central car controller. So a new mobile terminal will almost certainly not fit into an already installed integration kit, neither mechanically nor electrically. Since the costs of such a kit are considerably high, installing a new integration kit will not be easily accepted by a user. Neither he may want to accept to be forced to further use a terminal that is far off the state of the art, just to keep the already installed integration kit. [0004] To overcome this drawback, different approaches have been made. One of the easiest ways may be to include only functions in the integration kit that are common to most terminals, like taking a call or hanging up, and using a kind of simple universal holder. Obviously this would give the user only very restricted possibilities to use more sophisticated features of both the terminal and the internal systems of the car. So the logical next step was using kits containing a part specific to a certain car and comprising a universal connector to connect with a terminal specific holder. For each type of mobile terminal a specific holder or cradle has been used which possesses a corresponding universal connector fitting into that of the integration kit. This cradle may be equipped to translate between the car specific part of the kit and the mobile terminal, i.e. converting the communication protocol of one to another. [0005] Though lacking the possibility to make use of more sophisticated features, this may already seem to be a solution to the problem of interoperability. But some details are not yet solved completely satisfactory. A crucial step is to communicate with the mobile terminal by the cradle. As of today, this is done in a kind of passive manner, i.e. that the cradle waits for data sent by the terminal. This could be information about an incoming call or message, or the signal that the user has successfully entered the correct PIN number on the terminal for example. Since types of terminals exist that do not show such a behaviour, i.e. that are not sending information automatically, this method will not work in every possible combination of integration kit and mobile terminal. If the terminal does not automatically send required information to the cradle, the kit will wait forever for needed data. [0006] Also, provided that the car specific part of the kit provides all functionality that the cars control and display systems can offer, certainly not all types of terminal will support all these functions. If the user tries to use one of the functions offered by the kit but not supported by the actual terminal, unwanted reactions may occur. In the best case the kit will send back an error message informing the user that the wanted function is not available with this terminal. Second best would be to simply ignore the user request. In the worst possible case this will lead to a malfunction of the terminal. Anyone of these possibilities is unwanted. If a user tries to use a function that seems to be present to him, he expects that it can be used. He certainly will not understand why a function is offered to him that cannot be used though. With regard to easy understanding of the operation this is quite undesirable and should be avoided at all. [0007] In order to adapt the car specific part of the kit to the special features of the mobile terminal and make the mobile terminal interoperable with systems of the car, information about the function capabilities of the terminal has to be provided. [0008] So obviously, the need for a mobile terminal car connection system exists, that incorporates the advantages already achieved by state of the art devices but avoids the aforementioned drawbacks. The objects of the present invention are thus to provide a mobile terminal car connection system that is completely interoperable with both internal car systems and present or future terminals from the same or even different manufacturers. That means a system that offers all functions to the user that are actually usable in a given combination of car and mobile terminal. And also one that is easily upgradable with minimal costs that may be caused by a change of the mobile terminal used. [0009] To achieve the aforementioned objects, the present invention provides a system for integrating a mobile terminal into the systems of a car, which is adapted to provide mobile terminal capability information to ensure complete interoperability of a given combination of car and mobile terminal. [0010] According to an aspect of the present invention a method is provided to adapt a phone functionality matrix of an automotive mobile terminal connection device to function capabilities supported by a mobile terminal device connected to the automotive mobile terminal connection device. The method comprises the steps of: [0011] receiving data containing an indication about the function capabilities supported by the mobile terminal device; and [0012] rewriting the phone functionality matrix according to the received data. [0013] It is preferred that the data containing an indication about said function capabilities supported by said mobile terminal device is received from a mobile terminal cradle. Since the mobile terminal cradle has to be specifically adapted to a certain type of mobile terminal device, it may also provide the data containing an indication about said function capabilities and thus send that data. [0014] It is preferred that the automotive mobile terminal connection device requests the data from the mobile terminal device. The automotive mobile terminal connection device may easily request that data utilizing for example standard AT commands common to GSM mobile phones. [0015] It is preferred that the data containing an indication of said function capabilities is received from the mobile terminal device by requesting type and software version thereof. Though this may require occasional software upgrades for the automotive mobile terminal connection device this is a way which is easy to implement to determine the function capabilities of the mobile terminal device. [0016] It is preferred that the data containing the indication of the function capabilities is provided to the automotive mobile terminal connection device by the mobile terminal cradle. The cradle derives type and software version from the mobile terminal device. This may especially be useful if a cradle is adapted to several mobile phones belonging to the same series, i.e. having the same bottom connector and interface protocol, but different function capabilities. Thus the cradle has to derive the supported function capabilities from type and software version of the mobile phone actually connected. [0017] It is preferred that the functionality matrix is sent to a central car controller to enable the central car controller to build a user interface corresponding to the functionality matrix. Since the central car controller is aware of the features of systems of the car, like those of controls and display systems for example, it is the device which is responsible for building a user interface. And thus data need to be provided to enable it to adapt this user interface to correspond to the function capabilities of the mobile terminal. [0018] According to another aspect of the present invention, an automotive mobile terminal connection device is provided. The automotive mobile terminal connection device comprises an interface suitable to connect with a central car controller and a connector to connect with a mobile terminal cradle which is adapted for physically receiving a mobile terminal device. It is characterized by a phone functionality matrix which reflects function capabilities of said mobile terminal device. [0019] It is preferred that the automotive mobile terminal connection device is adapted to request data from the mobile terminal device containing an indication of the function capabilities. As 10 described before, utilizing for instance standard GSM AT commands, this would be a flexible way to derive the function capabilities of the mobile terminal device. [0020] It is preferred that the automotive mobile terminal connection device is adapted to request the data containing the indication about the function capabilities of the mobile terminal device from the mobile terminal cradle. As also described before, the mobile terminal cradle would be an ideal location to store or otherwise provide information about the function capabilities of the mobile terminal device. [0021] It is preferred that the automotive mobile terminal connection device is adapted to request type and software version of the mobile terminal device. As described before this is an easy way to derive the function capabilities of the mobile terminal device, even though it has considerable disadvantages. [0022] According to yet another aspect of the present invention a mobile terminal cradle for physically receiving a mobile terminal device is provided. It comprises a connector adapted to connect to an automotive mobile terminal connection device, an interface device adapted to request user data from and send user data to the mobile terminal device. That means the cradle is adapted to actively request user data that may not be automatically provided by the mobile terminal device. This might be information about incoming messages or calls for example. One might also say that the cradle actively supports the communication with the automotive mobile terminal connection device. [0023] It is preferred that the mobile terminal cradle is adapted to request data from the mobile terminal device containing an indication about function capabilities of the mobile terminal device. That means that the cradle is enabled to actively obtain information about the functions supported by the mobile terminal device. This is useful for types of mobile terminals that do not provide such information automatically. [0024] It is preferred that the mobile terminal cradle comprises a storage which contains an indication about the function capabilities of the mobile terminal device. Since the cradle has to be specifically adapted to a certain type of mobile terminal device anyway, it is only logical to store information about the functions supported by that particular mobile terminal device in here. [0025] It is preferred that the mobile terminal cradle comprises a processor adapted to convert a communication protocol of the mobile terminal device into a communication protocol supported by the automotive mobile terminal connection device. That way, different types of mobile terminals may be used with the same automotive mobile terminal connection device, each having its own cradle. The communication protocols of different mobile terminal devices can so be translated to the automotive mobile terminal connection device. [0026] It is preferred that the mobile terminal cradle comprises a charger adapted to charge the battery of the mobile terminal. It should be obvious that is it comfortable to also provide a power source to the terminal which is part of the cradle, instead of a separate charging device. [0027] It is preferred that the mobile terminal cradle is adapted to simulate a predetermined type of mobile terminal device to said automotive mobile terminal connection device. That means, for the automotive mobile terminal connection device it seems as if always the same predetermined type of mobile terminal device is connected to the cradle, regardless of the type of mobile terminal device actually connected. This may be desirable, because thus the adaptation could be made easier, while at the same time losing some level of interoperability. If the type of terminal corresponding to this unified functionality only support few features, some more sophisticated features of the terminal actually connected would be lost. While otherwise, if the terminal actually connected supports less features than the terminal corresponding to the unified functionality the problem of presenting unusable features through the cars system would come up again. In certain circumstances this may though be a useful possibility. [0028] The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the present invention and serve, together with the description, to explain the principles of the invention. In the drawings, [0029]FIG. 1 schematically illustrates an embodiment of the present invention; [0030]FIG. 2 illustrates another embodiment of the present invention; [0031]FIG. 3 illustrates another embodiment of the present invention; and [0032]FIG. 4 illustrates yet another embodiment of the present invention. [0033] In FIG. 1 a mobile terminal car connection system according to the invention is schematically illustrated. A mobile terminal P is electrically connected to a cradle 4, in a bi-directional way, through an interface 12. So the terminal P can send data to be received by the cradle 4, and vice versa. The cradle 4 is connected with an automotive mobile terminal connection device 2. Cradle 4 and automotive mobile terminal connection device 2 are interconnected also in a bi-directional way, through connector 20 being part of the automotive mobile terminal connection device 2, and connector 24 being part of the cradle 4. Those two connectors 20 and 24 are standardized connectors, meaning that every cradle 4 equipped with a connector 24 can be connected to the automotive mobile terminal connection device 2. If the terminal P is a Nokia® mobile terminal, no processing of data received from the terminal P is necessary, because the automotive mobile terminal connection device 2 supports the Nokia® propietary communication protocol. The cradle 4 may optionally contain a processor 14, in case the cradle 4 is adapted for a non-Nokia® mobile terminal. The processor 14 translates data sent by the mobile terminal device P into the Nokia® protocol. In case a Nokia® terminal is connected to the mobile terminal connection device and no processing of data received from the terminal P is necessary and cradle 4 and/or processor 14 are thus not needed, a direct cable connection from automotive terminal connection device 2 to the mobile terminal P can be used. The automotive mobile terminal connection device 2 is bi-directionally connected with a central car controller 18 through an interface 22. The central car controller 18 is connected to an internal car display system 8 and internal car controls 10. Car controls 10 could be control buttons on the steering wheel (as shown in FIG. 2), or control keys of an integrated navigation system or the like. Those are connected bi-directionally with the automotive mobile terminal connection device 2 through central car controller 18 and interface 22, in order to send control commands given through the control keys to be handled by the terminal P and to receive feedback from the terminal P, for instance in order to light an LED in a control key after a function has been switched on. The cradle 4 may optionally include a charger 16, which is adapted to charge the battery of the mobile terminal device P. [0034] In FIG. 2 a typical configuration of the present invention is illustrated. Only the parts that may be visible to the user are shown here, while connections and other parts usually hidden are not shown. A mobile terminal device P is physically received in a cradle 4 and releasably attached thereto. The cradle 4 can be mounted in a position that is suitable, dependant on wether the terminals display and control keys are to be used, and if the terminals speakers or those belonging to the cars audio system will be used. An automotive mobile terminal connection device 2 can be mounted either visibly in a radio mounting slot or the like, or hidden in the glove box for example, provided the necessary connection with the cradle 4 is ensured. The cars radio system R may be utilized to control the terminal P and serve as a replacement of the terminals own display, if the radio system R is suitably equipped. Control buttons 10, for example incorporated into the steering wheel, may suit the purpose of controlling the terminals functions, while a display device 8, being for instance part of the cars navigation system, may also serve to act as a replacement for the terminals display. [0035] In FIG. 3 a possible functionality matrix is shown. In this case said matrix is rather simple, only containing certain features and the information if a mobile terminal can support them or not. It would easily be possible to expand the matrix, for example to give information not only if, but also how or in other words in what way or to what degree certain features are supported by the mobile terminal. For example for the cell “List SMS”, possible entries could then be “in order of receiving”, “in alphabetical order”, “only from persons in the phonebook” and the like. That way, a very fine-tuned matrix could be derived, to be provided to the central car controller in order to build a sophisticated user interface taking advantage of all the advanced features of the mobile terminal. [0036] In FIG. 4 a schematic diagram about second call initiation is illustrated. The automotive mobile terminal connection device 2 and the cradle 4 are shown, also a mobile phone P. Manual dialling on the mobile phone P is possible directly with an active single call or after seperately putting the active call on hold. State changes after user operations on the mobile phone P are only detectable from cyclic checking of the call list (CLCC). [0037] There are two major kinds of data exchanged between the mobile terminal device, the cradle and the automotive mobile terminal connection device of the present invention. On the one hand there is so-called user data. This can be either the contents of an SMS message, information about an incoming call or the like, sent from the mobile terminal device. Or user data that is sent to the mobile terminal device, for example commands like establishing a mobile connection, in other words dialling, changing the ring tone or the like. User data is thus sent in both directions from and to the mobile terminal device. On the other hand there is data containing an indication about functions supported by the mobile terminal. This kind of data is only sent in the direction from the mobile terminal device to the automotive mobile terminal connection device, either automatically or requested by the mobile terminal cradle oder the automotive mobile terminal connection device. [0038] Examples for user data that is either received or has to be requested are: [0039] Indication of entering a PIN number: [0040] The automotive mobile terminal connection device needs information about if the user has already entered his PIN to begin its operation. Some phones (type A) send a message through the bottom connector that the correct PIN number has been entered. Other phone types (type B) make it necessary to request a confirmation about if the PIN has been correctly entered. In the sense of the present invention the automotive mobile terminal connection device for example waits constantly for the confirmation of having entered the PIN. If a phone of type A with a corresponding cradle is installed, the cradle will wait for such corresponding message and send this message (maybe with a correspondingly adapted command) to the automotive mobile terminal connection device. In the case that a phone of type B is installed with the corresponding cradle, the cradle will periodically send a request to the phone, to obtain information if the PIN has been entered. If the phone of type B confirms this, the cradle will send a message indicating this to the automotive mobile terminal connection device. This message is identically to that sent with a phone of type A. [0041] Displaying incoming messages (SMS, MMS, Email and the like): [0042] similar to the aforementioned examples the phone may signal incoming messages and/or output them automatically, or the cradle has to periodically request information about wether a message has come in and relay that information. [0043] Example for user data which has to be requested: [0044] Requesting the phonebook of the mobile phone: [0045] In this case it is provided that the automotive mobile terminal connection device is adapted to display the phonebook through a display system of the car. The output of the phonebook through the bottom connector is different between mobile phones from different manufacturers or even with phones from the same manufacturer belonging to different series. According to the present invention the automotive mobile terminal connection device may for example expect that the phonebook is outputted in an alphabetical order and in a certain format. If the phonebook is sent in alphabetical order by a phone of type A, the corresponding data in principle only has to be relayed to the automotive mobile terminal connection device. If a phone of type B outputs the entries of its phonebook unsorted and in another format, the cradle will have to first sort the data and convert the format, before the data can be send to the automotive mobile terminal connection device. [0046] There are different possibilities for the automotive mobile terminal connection device to obtain the needed information about a terminals function capabilities or features, in order to adapt the functional matrix. The automotive mobile terminal connection device may utilize standard GSM AT commands to request the features of the mobile terminal. This is an elegant and flexible way to obtain that information, since GSM is a widely accepted standard for mobile communication and the AT commands are supported by most of the GSM mobile terminals. Another possible, but certainly not as flexible manner to obtain the needed data could be to request type and software version of the mobile terminal. With this information at hand, the automotive mobile terminal connection device could derive which features are supported performing a kind of database lookup. The obvious disadvantage of such a method is that of necessary software updates for future terminals whose interface and other details are not yet known. Without such updates of the internal database, the automotive mobile terminal connection device would not be able to recognize terminals new to the market. If new terminals are purchased in short periods of time and/or if a larger number of terminals are to be used with the same car, of different family members for example, this can cause unacceptable costs and efforts. Using one of the aforementioned ways, the automotive mobile terminal connection device is used to obtain the features of the mobile terminal by itself. [0047] A different yet also logical approach is to use the cradle to obtain the needed information about the terminals features. Since a cradle has to be adapted specifically to a certain type of terminal, this is a rather obvious solution. The information may either be hardcoded into the cradles circuit, if only one type of terminal is to be used with the cradle. Or for example a cradle suitable for a series of terminals from the same manufacturer with the same mechanical and electrical properties but different features is utilized. In this case there are methods known in the art that can be implemented to enable the cradle to determine the actual type or software version of the terminal and thus store the right list of features. If the terminal uses a standardized connection protocol, like the bluetooth handsfree protocol (HFP) for example, the cradle can derive the needed information about supported features from the kind of connection with the terminal either. Using one of the aforementioned ways, the cradle is used to provide data conatining an indication of the features of the mobile terminal. [0048] The present invention suggests an automotive mobile terminal connection system, adaptable to different mobile terminal devices via a terminal specific cradle connectable to the automotive mobile terminal connection device via a universal connector. So when different persons are using the same car possessing also different mobile terminal devices, each of them may use the connection system by simply utilizing a cradle adapted for his or her type of terminal device. Using future mobile terminal devices is thus possible by only replacing the cradle without the cost-intensive need to replace other parts of or even the whole equipment. The cradle is able to obtain data from the mobile terminal device which is not sent by the mobile terminal by itself. This includes user data as well as data containing an indication of the function capabilities of the mobile terminal device. I.e. the cradle actively supports communication between the automotive mobile terminal connection device and the mobile terminal device. The automotive mobile terminal connection device can adapt a matrix to match the function capabilities of the mobile terminal device, in order to provide this matrix to the central car controller. The central car controller can thus build a corresponding user interface, which offers only functions to the user that are both supported by the mobile terminal device and that can be controlled and/or displayed through one of the cars control or display systems. This eliminates incorrect operation and confusion of the user, and thus increases ease of use and comfort. (String), [0001] 本发明涉及一种将移动电话终端集成到汽车的电话控制系统中的汽车连接系统。 更具体地,它涉及一种连接系统,该连接系统适合于获取和提供关于移动终端功能能力的信息,从而使得构建与移动终端的特定特征相匹配的相应用户界面成为可能。 [0002] 随着移动电话和PDA之类的移动终端变得非常流行,在车辆环境中使用这样的终端的愿望已经产生。 因为通常车辆驾驶员是终端的主要用户,所以存在以一种免提模式操作终端的必要性。 为了尽量减少在驾驶期间使用移动终端的风险(主要是由于在控制汽车的同时操作终端而造成的分心),已经构建了不同的支架设备。 这些范围从相当简单的机械支架(其唯一目的是将移动终端放置在驾驶员的最佳位置)到非常复杂的设备。 后者利用某些内部汽车系统,如音频系统、显示器(如属于导航系统的显示器)或控件,例如放置在方向盘上的按钮。 音频系统的扬声器因此可以用于播放目的,而安装的控件可能适合于操作终端而不是使用终端自己的控件。 [0003] 这些常见的移动终端汽车集成套件存在一个主要缺点,即互操作性。 将此类套件集成到汽车中可能是一项非常昂贵且复杂的任务。 由于它们必须适应特定类型的汽车和终端类型,因此出现了一个明显的问题。 汽车的平均寿命可能约为 10 年或更长,而移动终端的典型产品周期要短得多,充其量只有 1-3 年左右。 从同一制造商或什至不同制造商购买新终端肯定会导致还购买新的汽车集成套件。 这是因为此类套件越复杂,就越有可能同时适应相应终端的专有通信协议和汽车的专有通信协议,或者换句话说,汽车中央控制器。 因此,无论是机械还是电气方面,新的移动终端几乎肯定不会适合已安装的集成套件。 由于这种套件的成本相当高,安装新的集成套件将不容易被用户接受。 他也可能不想被迫进一步使用一个与最先进技术相去甚远的终端,只是为了保留已经安装的集成工具包。 [0004] 为了克服这个缺点,已经采用了不同的方法。 最简单的方法之一可能是在集成套件中只包含大多数终端通用的功能,例如接听电话或挂断电话,并使用一种简单的通用支架。 显然,这会给用户提供非常有限的可能性来使用终端和汽车内部系统的更复杂的功能。 因此,合乎逻辑的下一步是使用包含特定于特定汽车的零件的套件,并包含一个通用连接器以连接到特定于终端的支架。 对于每种类型的移动终端,都使用了特定的支架或支架,它们具有适合集成套件的相应通用连接器。 该支架可以配备成在套件的汽车特定部分和移动终端之间进行转换,即将一种通信协议转换为另一种通信协议。 [0005]尽管无法使用更复杂的功能,但这似乎已经是互操作性问题的解决方案。 但是一些细节还没有完全圆满解决。 一个关键的步骤是通过底座与移动终端通信。 截至目前,这是以一种被动方式完成的,即支架等待终端发送的数据。 例如,这可能是有关来电或消息的信息,或者用户已在终端上成功输入正确 PIN 码的信号。 由于存在不显示此类行为的终端类型,即不会自动发送信息,因此此方法不适用于集成工具包和移动终端的所有可能组合。 如果终端没有自动将所需信息发送到底座,套件将永远等待所需数据。 [0006] 此外,如果套件的汽车特定部分提供汽车控制和显示系统可以提供的所有功能,当然不是所有类型的终端都支持所有这些功能。 如果用户尝试使用套件提供但实际终端不支持的其中一项功能,则可能会出现不需要的反应。 在最好的情况下,该套件将发回一条错误消息,通知用户该终端无法使用所需的功能。 次要的是简单地忽略用户请求。 在最坏的情况下,这将导致终端发生故障。 这些可能性中的任何一种都是不需要的。 如果一个用户试图使用一个似乎存在于他面前的功能,他希望它可以被使用。 他当然不会理解为什么提供给他的功能却不能使用。 就操作的容易理解而言,这是非常不希望的,应该完全避免。 [0007] 为了使套件的汽车特定部分适应移动终端的特殊功能并使移动终端与汽车系统互操作,必须提供有关终端功能的信息。 [0008] 因此,很明显,存在对移动终端汽车连接系统的需求,它结合了现有技术设备已经实现的优点,但避免了上述缺点。 因此,本发明的目的是提供一种移动终端汽车连接系统,该系统可与内部汽车系统以及来自相同或什至不同制造商的现有或未来终端完全互操作。 这意味着一个系统可以为用户提供在给定的汽车和移动终端组合中实际可用的所有功能。 还有一个可以很容易地以最小的成本升级的,这可能是由所使用的移动终端的变化引起的。 [0009] 为实现上述目的,本发明提供了一种将移动终端集成到汽车系统中的系统,其适于提供移动终端能力信息以确保给定的汽车和移动终端组合的完全互操作性。 [0010] 根据本发明的一个方面,提供了一种使汽车移动终端连接设备的电话功能矩阵适应连接到汽车移动终端连接设备的移动终端设备所支持的功能能力的方法。 该方法包括以下步骤: [0011]接收包含关于移动终端设备支持的功能能力的指示的数据; 和[0012] 根据接收到的数据重写电话功能矩阵。 [0013] 优选地,包含关于所述移动终端设备支持的所述功能能力的指示的数据是从移动终端支架接收的。 由于移动终端支架必须专门适配某种类型的移动终端设备,它还可以提供包含关于所述功能能力的指示的数据并因此发送该数据。 [0014] 优选的是,汽车移动终端连接设备请求来自移动终端设备的数据。 汽车移动终端连接设备可以容易地使用例如GSM移动电话通用的标准AT命令来请求数据。 [0015]优选地,通过请求其类型和软件版本从移动终端设备接收包含所述功能能力的指示的数据。 虽然这可能需要偶尔对汽车移动终端连接设备进行软件升级,但这是一种易于实施以确定移动终端设备的功能能力的方式。 [0016] 优选地,包含功能能力指示的数据由移动终端支架提供给汽车移动终端连接装置。 底座从移动终端设备中获取类型和软件版本。 如果一个支架适用于属于同一系列的多个移动电话,即具有相同的底部连接器和接口协议,但具有不同的功能能力,则这可能特别有用。 因此,底座必须从实际连接的手机的类型和软件版本中推导出支持的功能能力。 [0017] 优选地,将功能矩阵发送至汽车中央控制器,以使汽车中央控制器能够建立与功能矩阵相对应的用户界面。 由于汽车中央控制器了解汽车系统的特性,例如控制和显示系统的特性,因此它是负责构建用户界面的设备。 因此需要提供数据以使其能够适配该用户界面以对应于移动终端的功能能力。 [0018] 根据本发明的另一方面,提供了一种车载移动终端连接装置。 该车载移动终端连接装置包括适于与汽车中央控制器连接的接口和用于与适于物理接收移动终端设备的移动终端支架连接的连接器。 其特征在于反映所述移动终端设备的功能能力的电话功能矩阵。 [0019] 优选地,汽车移动终端连接设备适于从移动终端设备请求包含功能能力的指示的数据。 作为 10 如前所述,利用例如标准GSM AT命令,这将是获得移动终端设备的功能能力的灵活方式。 [0020] 优选地,汽车移动终端连接设备适于从移动终端支架请求包含关于移动终端设备的功能能力的指示的数据。 同样如前所述,移动终端支架将是存储或以其他方式提供关于移动终端设备的功能能力的信息的理想位置。 [0021] 优选地,车载移动终端连接装置适合请求移动终端装置的类型和软件版本。 如前所述,这是获得移动终端设备的功能能力的简单方法,尽管它具有相当大的缺点。 [0022] 根据本发明的又一方面,提供了一种用于物理地接收移动终端设备的移动终端支架。 它包括适于连接到汽车移动终端连接设备的连接器、适于向移动终端设备请求用户数据和向移动终端设备发送用户数据的接口设备。 这意味着支架适于主动请求可能不会由移动终端设备自动提供的用户数据。 例如,这可能是有关传入消息或呼叫的信息。 也可以说,通讯座主动支持与车载移动终端连接设备的通信。 [0023] 优选地,移动终端支架适于从移动终端设备请求包含关于移动终端设备的功能能力的指示的数据。 也就是说,使通讯座能够主动获取移动终端设备支持的功能信息。 这对于不自动提供此类信息的移动终端类型很有用。 [0024]优选地,移动终端支架包括存储器,该存储器包含关于移动终端设备的功能能力的指示。 由于底座无论如何都必须专门适配某种类型的移动终端设备,因此将关于该特定移动终端设备所支持的功能的信息存储在此处是合乎逻辑的。 [0025] 优选地,移动终端支架包括适于将移动终端设备的通信协议转换成汽车移动终端连接设备支持的通信协议的处理器。 这样,不同类型的移动终端可以与相同的汽车移动终端连接设备一起使用,每个移动终端都有自己的支架。 不同移动终端设备的通信协议可以这样转换到汽车移动终端连接设备。 [0026] 优选地,移动终端支架包括适于为移动终端的电池充电的充电器。 显而易见的是,还为作为支架一部分的终端而不是单独的充电设备提供电源是舒适的。 [0027] 优选地,移动终端支架适于模拟预定类型的移动终端设备到所述汽车移动终端连接设备。 这意味着,对于汽车移动终端连接装置而言,似乎总是相同的预定类型的移动终端装置连接到托架,而不管实际连接的移动终端装置的类型如何。 这可能是可取的,因为这样可以使适应更容易,同时失去一定程度的互操作性。 如果这种统一功能对应的终端类型只支持很少的特性,那么实际连接的终端的一些更复杂的特性就会丢失。 反之,如果实际连接的终端支持的特性比统一功能对应的终端少,又会出现无法通过车载系统呈现不可用特性的问题。 在某些情况下,这可能是一种有用的可能性。 [0028] 附图被包括以提供对本发明的进一步理解并且并入并构成本说明书的一部分。 附图图示了本发明的实施例并且与描述一起用于解释本发明的原理。 在图纸中, [0029] 图1示意性地说明了本发明的一个实施例; [0030] 图2说明本发明的另一个实施例; [0031] 图3说明本发明的另一个实施例; 和 [0032] 图4示出了本发明的又一实施例。 [0033] 在图1中示意性地图示了根据本发明的移动终端汽车连接系统。 移动终端P与通讯座电连接 4 ,以双向方式,通过一个接口 12 . 所以终端P可以发送数据给cradle接收 4 ,反之亦然。 摇篮 4 与车载移动终端连接装置连接 2 . 摇篮 4 与车载移动终端连接装置 2 也通过连接器以双向方式互连 20 作为汽车移动终端连接装置的一部分 2 , 和连接器 24 成为摇篮的一部分 4 . 那两个连接器 20 和 24 是标准化的连接器,这意味着每个通讯座 4 配备连接器 24 可连接车载移动终端连接设备 2 . 如果终端 P 是诺基亚移动终端,则不需要对从终端 P 接收到的数据进行处理,因为汽车移动终端连接设备 2 支持诺基亚专有的通信协议。 摇篮 4 可以选择包含一个处理器 14 , 以防摇篮 4 适用于非 Nokia® 移动终端。 处理器 14将移动终端设备 P 发送的数据转换为 Nokia® 协议。 如果 Nokia® 终端连接到移动终端连接设备并且不需要处理从终端 P 接收到的数据并且底座 4 和/或处理器 14 因此不需要,从汽车终端连接设备的直接电缆连接 2 可以使用到移动终端P。 车载移动终端连接装置 2 与中央汽车控制器双向连接 18 通过一个界面 22 . 中央轿厢控制器 18 连接到内部汽车显示系统 8 和内部汽车控制 10 . 汽车控制 10 可以是方向盘上的控制按钮(如图2所示),也可以是集成导航系统的控制键等。 与车载移动终端连接装置双向连接 2 通过中央轿厢控制器 18 和界面 22 ,以便发送通过控制键给出的控制命令,由终端 P 处理并接收来自终端 P 的反馈,例如,为了在打开功能后点亮控制键中的 LED。 摇篮 4 可以选择包括一个充电器 16 ,适用于为移动终端设备P的电池充电。 [0034] 在图2中说明了本发明的典型配置。 此处仅显示用户可能可见的部分,而未显示连接和其他通常隐藏的部分。 移动终端设备 P 被物理地接收在支架中 4 并可释放地附在其上。 摇篮 4 可以安装在合适的位置,具体取决于是否使用终端显示器和控制键,以及是否使用终端扬声器或属于汽车音响系统的扬声器。 一种车载移动终端连接装置 2 可以明显地安装在无线电安装槽等中,或者隐藏在手套箱中,例如,提供与支架的必要连接 4 得到保证。 汽车无线电系统R可用于控制终端P并用作终端自身显示器的替代,如果无线电系统R被适当装备的话。 控制按钮 10 ,例如并入方向盘,可能适合控制终端功能的目的,而显示设备 8 ,例如作为汽车导航系统的一部分,也可以作为终端显示器的替代品。 [0035] 在图3中,示出了可能的功能矩阵。 在这种情况下,所述矩阵相当简单,仅包含某些特征以及移动终端是否支持这些特征的信息。 可以很容易地扩展矩阵,例如不仅给出信息,而且给出移动终端支持某些特征的方式或方式或程度的信息。 例如对于单元格“List SMS”,可能的条目可以是“按接收顺序”、“按字母顺序”、“仅来自电话簿中的人”等。 这样,可以导出一个非常精细的矩阵,提供给汽车中央控制器,以便利用移动终端的所有高级功能构建复杂的用户界面。 [0036] 在图4中示出了关于发起第二呼叫的示意图。 车载移动终端连接装置 2 和摇篮 4 还显示了移动电话 P。在移动电话 P 上手动拨号可以直接使用活动的单个呼叫或在单独保持活动呼叫之后。 用户在移动电话 P 上操作后的状态变化只能通过循环检查呼叫列表 (CLCC) 来检测。 [0037]本发明的移动终端装置、支架与车载移动终端连接装置之间交换的数据主要有两种。 一方面是所谓的用户数据。 这可以是从移动终端设备发送的 SMS 消息的内容、关于来电的信息等。 或者发送到移动终端设备的用户数据,例如像建立移动连接的命令,换言之拨号、改变铃声等。 用户数据因此从移动终端设备双向发送和发送到移动终端设备。 另一方面,存在包含关于移动终端支持的功能的指示的数据。 这种数据仅在从移动终端设备到汽车移动终端连接设备的方向上自动发送或由汽车移动终端连接设备上的移动终端支架请求发送。 [0038] 已接收或必须请求的用户数据示例如下: [0039] 输入 PIN 码的指示:[0040] 汽车移动终端连接设备需要有关用户是否已经输入其 PIN 以开始其操作的信息。 某些电话(A 型)通过底部连接器发送一条消息,表明已输入正确的 PIN 码。 其他电话类型(B 类)需要请求确认是否已正确输入 PIN。 在本发明的意义上,汽车移动终端连接设备例如不断地等待输入PIN的确认。 如果安装了具有相应底座的类型A电话,则底座将等待这样的相应消息并将该消息(可能带有相应适配的命令)发送到汽车移动终端连接设备。 如果B型手机安装了相应的底座,则底座会定期向手机发送请求,以获取输入PIN码后的信息。 如果 B 型电话确认了这一点,则通讯座将向汽车移动终端连接设备发送一条消息,表明这一点。 此消息与使用 A 型电话发送的消息相同。[0041] 显示传入消息(短信、彩信、电子邮件等):[0042] 与上述示例类似,电话可能会发出传入消息的信号和/或自动输出它们,或者底座必须定期请求有关消息是否已传入的信息并转发该信息。[0043] 必须请求的用户数据示例:[0044] 查询手机电话本:[0045] 在这种情况下,汽车移动终端连接设备适合于通过汽车的显示系统显示电话簿。 不同厂商的手机甚至同一厂商不同系列的手机通过底部连接器输出的电话本是不同的。 根据本发明,汽车移动终端连接设备可以例如期望电话簿以字母顺序和特定格式输出。 如果A型电话按字母顺序发送电话簿,则原则上只需要将相应的数据中继到汽车移动终端连接设备即可。 如果B型电话以另一种格式未排序地输出其电话簿条目,则通讯座必须先对数据进行排序并转换格式,然后才能将数据发送到汽车移动终端连接设备。 [0046] 汽车移动终端连接设备有不同的可能性来获得关于终端功能能力或特性的所需信息,以便适配功能矩阵。 汽车移动终端连接装置可以利用标准GSM AT命令来请求移动终端的特征。 这是获取该信息的一种优雅而灵活的方式,因为 GSM 是广泛接受的移动通信标准,并且大多数 GSM 移动终端都支持 AT 命令。 另一种可能但肯定不那么灵活的获取所需数据的方式可能是请求移动终端的类型和软件版本。 有了手头的这些信息,汽车移动终端连接设备可以推导出支持哪些特征来执行一种数据库查找。 这种方法的明显缺点是需要为未来的终端进行必要的软件更新,而这些终端的界面和其他细节尚不清楚。 如果内部数据库没有这种更新,汽车移动终端连接设备将无法识别市场上的新终端。 如果在短时间内购买新终端和/或如果大量终端要用于同一辆车,例如不同家庭成员,这可能会导致不可接受的成本和工作量。 采用上述方式之一,利用车载移动终端连接装置自行获取移动终端的特征。 [0047] 一种不同但同样合乎逻辑的方法是使用通讯座获取有关终端功能的所需信息。 由于支架必须专门适应特定类型的终端,因此这是一个相当明显的解决方案。 如果只有一种类型的终端要与支架一起使用,则该信息可以硬编码到支架电路中。 或者例如适用于来自同一制造商的具有相同机械和电气特性但具有不同特征的一系列终端的支架。 在这种情况下,存在可以实施的本领域已知的方法以使支架能够确定终端的实际类型或软件版本并因此存储正确的特征列表。 如果终端使用标准化连接协议,例如蓝牙免提协议 (HFP),则底座也可以从与终端的连接类型中获取有关支持功能的所需信息。 使用前述方式之一,支架用于提供包含移动终端的特征的指示的数据。 [0048]本发明提出了一种汽车移动终端连接系统,通过可通过通用连接器连接到汽车移动终端连接设备的终端专用支架适用于不同的移动终端设备。 因此,当不同的人使用同样拥有不同移动终端设备的同一辆车时,他们中的每个人都可以通过简单地利用适合他或她的终端设备类型的支架来使用连接系统。 因此,仅需更换支架即可使用未来的移动终端设备,而无需更换设备的其他部分甚至整个设备,成本高昂。 底座能够从移动终端设备获取非移动终端自身发送的数据。 这包括用户数据以及包含移动终端设备的功能能力的指示的数据。 IE。 通讯座主动支持车载移动终端连接设备与移动终端设备之间的通信。 汽车移动终端连接设备可以适配一个矩阵来匹配移动终端设备的功能能力,以将该矩阵提供给汽车中央控制器。 中央汽车控制器因此可以建立相应的用户界面,其仅向用户提供移动终端设备支持的并且可以通过汽车控制或显示系统之一控制和/或显示的功能。 这消除了用户的不正确操作和混淆,从而增加了易用性和舒适性。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AT471058T(String), AU2003259428A1(String), CN100481848C(String), CN1839639A(String), DE60332970D1(String), DE60332970T2(String), EP1665845A1(String), EP1665845B1(String), US20070111710A1(String), WO2005025256A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.268 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AT471058T(String), AU2003259428A1(String), CN100481848C(String), CN1839639A(String), DE60332970D1(String), DE60332970T2(String), EP1665845A1(String), EP1665845B1(String), US20070111710A1(String), WO2005025256A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20070111710A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AT471058T(String), AU2003259428A1(String), CN100481848C(String), CN1839639A(String), DE60332970D1(String), DE60332970T2(String), EP1665845A1(String), EP1665845B1(String), US20070111710A1(String), WO2005025256A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), AT471058T(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.374 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.374 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), AU2003259428A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.409 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.409 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), CN100481848C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.444 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), CN1839639A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.479 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), DE60332970D1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), DE60332970T2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), EP1665845A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.584 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), EP1665845B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), US20070111710A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271671(Integer), WO2005025256A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.691 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20070111710A1(String), US20070111710A1(String), 1179331200(Integer), 271671(Integer), 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: NOKIA CORPORATION(String), PIETRUSZKA, JORG(String), SPILKER, JOCHEN(String), HANEBRINK, THOMAS(String), 诺基亚公司(String), PIETRUSZKA JORG(String), SPILKER JOCHEN(String), HANEBRINK THOMAS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: NOKIA CORPORATION(String), 诺基亚公司(String), 255(String), 0(Integer), 1660814384(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.807 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.807 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.807 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185999(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20942(Integer), 1(Integer), 185999(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.876 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: PIETRUSZKA, JORG(String), PIETRUSZKA JORG(String), 0(Integer), 1681976153(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SPILKER, JOCHEN(String), SPILKER JOCHEN(String), 0(Integer), 1681976153(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.946 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: HANEBRINK, THOMAS(String), HANEBRINK THOMAS(String), 0(Integer), 1681976153(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:53.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 185999(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75856(Integer), 2(Integer), 185999(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75857(Integer), 2(Integer), 185999(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.085 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.086 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.086 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75858(Integer), 2(Integer), 185999(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.138 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20942(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.155 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75856(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.173 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.242 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.243 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.397 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.398 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 185999(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.432 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.434 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8145270B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.777 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Smart card and method for generating response message to be delivered to mobile terminal supporting mobile broadcast, and mobile terminal therefor(String), 用于生成响应消息以传递给支持移动广播的移动终端的智能卡和方法及其移动终端(String), US8145270B2(String), Provided is a method of efficiently processing a Short-Term Key Message (STKM) in the mobile broadcast supporting the mobile terminal. A structure of a response message according to processing the STKM in the smart card is also provided. In particular, a variety of information necessary for reproducing in the player is included in the response message and delivered to the mobile terminal, thereby the mobile terminal can easily obtain the desired information through the response message. Therefore, when the STKM is processed in the mobile terminal, there is no need to process operations except for a resending check, and the information does not need to be stored separately.(String), 提供了一种在支持移动终端的移动广播中有效处理短期密钥消息(STKM)的方法。 还提供了根据处理智能卡中的STKM的响应消息的结构。 特别地,在响应消息中包含播放器中再现所需的各种信息并传递给移动终端,从而移动终端可以通过响应消息容易地获得所需的信息。 因此,在移动终端处理STKM时,除了重发校验外,不需要其他操作,也不需要单独存储信息。(String), US12/260692(String), 1225209600(Integer), US8145270B2(String), 1332777600(Integer), 1332777600(Integer), 美国(String), 4(Integer), KR(String), 3(Integer), 7(Integer), KR100748470B1 | KR1020060031848A | KR1020070089027A | US20090316911A1 | US20100027787A1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186000(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e881ee8b8a134eeeac73f9abb5a83ec4.png(String), 186000(Integer), e881ee8b8a134eeeac73f9abb5a83ec4.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:54.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Smart card and method for generating response message to be delivered to mobile terminal supporting mobile broadcast, and mobile terminal therefor(String), 用于生成响应消息以传递给支持移动广播的移动终端的智能卡和方法及其移动终端(String), US8145270B2(String), Provided is a method of efficiently processing a Short-Term Key Message (STKM) in the mobile broadcast supporting the mobile terminal. A structure of a response message according to processing the STKM in the smart card is also provided. In particular, a variety of information necessary for reproducing in the player is included in the response message and delivered to the mobile terminal, thereby the mobile terminal can easily obtain the desired information through the response message. Therefore, when the STKM is processed in the mobile terminal, there is no need to process operations except for a resending check, and the information does not need to be stored separately.(String), 提供了一种在支持移动终端的移动广播中有效处理短期密钥消息(STKM)的方法。 还提供了根据处理智能卡中的STKM的响应消息的结构。 特别地,在响应消息中包含播放器中再现所需的各种信息并传递给移动终端,从而移动终端可以通过响应消息容易地获得所需的信息。 因此,在移动终端处理STKM时,除了重发校验外,不需要其他操作,也不需要单独存储信息。(String), US12/260692(String), 1225209600(Integer), US8145270B2(String), 1332777600(Integer), 1332777600(Integer), 美国(String), 2(Integer), 4(Integer), KR(String), 3(Integer), 7(Integer), KR100748470B1 | KR1020060031848A | KR1020070089027A | US20090316911A1 | US20100027787A1(String), \20230420\e881ee8b8a134eeeac73f9abb5a83ec4.png(String), 12(Integer), 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 1. A smart card which is inserted into a mobile terminal supporting mobile broadcast, and which generates a response message according to a short-term key message process, the smart card comprising:an information extraction unit for, when a Short-Term Key Message (STKM) is delivered from the mobile terminal, extracting information necessary for decrypting and reproducing broadcast service data from the STKM; anda response message generation unit for generating a response message including the extracted information and for delivering the response message to the mobile terminal.(String), 1.一种智能卡,插入支持移动广播的移动终端,根据短时密钥消息过程产生响应消息,该智能卡包括:信息提取单元,用于当从移动终端传送短期密钥消息(STKM)时,从STKM提取解密和再现广播服务数据所需的信息;和响应消息生成单元,用于生成包括提取的信息的响应消息,并将该响应消息传递给移动终端。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 2. The smart card as claimed in claim 1, wherein the response message comprises:a tag field for indicating a response message on a Multimedia Broadcast/Multicast Service (MBMS) operation;a field for indicating an entire length of the response message;a field for indicating that the MBMS operation is successful; anda field to be inserted with the extracted information.(String), 2.如权利要求1所述的智能卡,其中响应消息包括:用于指示关于多媒体广播/多播服务(MBMS)操作的响应消息的标签字段;用于指示响应消息的整个长度的字段;MBMS操作成功字段;和要插入提取信息的字段。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 3. The smart card as claimed in claim 2, wherein the field to be inserted with the extracted information comprises:a field for indicating a sum of length of the extracted information;a field for identifying an MBMS Traffic Key (MTK);a field for indicating an actual MTK;a field for indicating whether the Traffic Encryption Key (TEK) is decrypted with the Terminal Binding Key (TBK);a field for indicating whether a Message Authentication Code (MAC) portion is included when the broadcast service data is received; anda field for indicating a traffic key lifetime.(String), 3.如权利要求2所述的智能卡,其中要插入提取信息的字段包括:字段,表示提取信息的长度总和;用于标识MBMS流量密钥(MTK)的字段;用于指示实际MTK的字段;用于指示流量加密密钥(TEK)是否被终端绑定密钥(TBK)解密的字段;用于指示在接收到广播服务数据时是否包括消息认证码(MAC)部分的字段;和用于指示流量密钥生命周期的字段。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 4. The smart card as claimed in claim 3, wherein the field to be inserted with the extracted information further comprises a field for indicating a length of a salt key when the salt key is available, and a field for indicating an actual salt key.(String), 4.如权利要求3所述的智能卡,其中待插入提取信息的字段还包括用于指示saltkey可用时的saltkey长度的字段,以及用于指示实际saltkey的字段。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 5. The smart card as claimed in claim 1, wherein the smart card comprises a Universal Subscriber Identity Module (USIM).(String), 5.如权利要求1所述的智能卡,其中智能卡包括通用用户识别模块(USIM)。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 6. The smart card as claimed in claim 1, wherein the response message indicates a result of processing the short-term key message of the smart card in accordance with a Generic Bootstrapping Architecture (GBA)_Universal Subscriber Identity Module (USIM) (GBA_U) scheme.(String), 6.如权利要求1所述的智能卡,其中响应消息指示根据通用自举架构(GBA)_通用用户识别模块(USIM)(GBA_U)方案处理智能卡的短期密钥消息的结果。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 7. A mobile terminal into which a smart card is inserted and which processes a short-term key message, the mobile terminal comprising:a receiving unit for receiving a Short-Term Key Message (STKM) over a broadcast network;a resending check unit for determining whether the received short-term key message is a new short-term key message, and delivering the received STKM to the smart card when the received STKM is a new STKM; anda decryption unit for obtaining information necessary for decrypting and reproducing broadcast service data from the response message by parsing the delivered response message when a response message is delivered from the smart card in response to delivery of the STKM.(String), 7.一种插入智能卡并处理短期密钥消息的移动终端,该移动终端包括:用于通过广播网络接收短期密钥消息(STKM)的接收单元;重发校验单元,用于判断接收到的短期密钥消息是否为新的短期密钥消息,当接收到的STKM为新的STKM时,将接收到的STKM传递给智能卡;和解密单元,用于在响应于STKM的传递从智能卡传递响应消息时,通过解析传递的响应消息,从响应消息中获取解密和再现广播服务数据所需的信息。(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 8. The mobile terminal as claimed in claim 7, wherein the response message comprises:a tag field for indicating a response message on a Multimedia Broadcast/Multicast Service (MBMS) operation;a field for indicating an entire length of the response message;a field for indicating that the MBMS operation is successful; anda field to be inserted with information necessary for decrypting and reproducing the broadcast service data.(String), 8.如权利要求7所述的移动终端,其中响应消息包括:用于指示关于多媒体广播/多播服务(MBMS)操作的响应消息的标签字段;用于指示响应消息的整个长度的字段;MBMS操作成功字段;和将插入解密和再现广播服务数据所需的信息的字段。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 9. The mobile terminal as claimed in claim 7, wherein the information necessary for decrypting and reproducing the broadcast service data comprises at least one of:an MBMS traffic key IDentification (ID) for identifying an MBMS Traffic Key (MTK);MTK data;a terminal binding flag value for indicating whether a Traffic Encryption Key (TEK) must be decrypted with a Terminal Binding Key (TBK);a traffic authorization flag value for indicating whether a Message Authentication Code (MAC) portion is included when the broadcast service data is received; anda traffic key lifetime.(String), 9.如权利要求7所述的移动终端,其中解密和再现广播服务数据所需的信息至少包括以下之一:MBMSTrafficKeyIDentification(ID),用于识别MBMSTrafficKey(MTK);联发科数据;终端绑定标志值,用于指示流量加密密钥(TEK)是否必须用终端绑定密钥(TBK)解密;流量授权标志值,用于指示接收广播业务数据时是否包含消息认证码(MAC)部分;和交通密钥的生命周期。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 10. A method of generating a response message to be delivered to a mobile terminal supporting mobile broadcast in a smart card, the method comprising the steps of:receiving a Short-Term Key Message (STKM) from the mobile terminal;extracting information necessary for decrypting and reproducing broadcast service data from the STKM;generating a response message including the extracted information; anddelivering the response message to the mobile terminal.(String), 10.一种在智能卡中生成要传递给支持移动广播的移动终端的响应消息的方法,该方法包括步骤:从移动终端接收短期密钥消息(STKM);从STKM中提取解密和再现广播服务数据所需的信息;生成包括提取的信息的响应消息;和将响应消息传递给移动终端。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 11. The method as claimed in claim 10, wherein the response message comprises:a tag field for indicating a response message for a Multimedia Broadcast/Multicast Service (MBMS) operation;a field for indicating an entire length of the response message;a field for indicating that the MBMS operation is successful; anda field to be inserted with the extracted information.(String), 11.如权利要求10所述的方法,其中响应消息包括:用于指示多媒体广播/多播服务(MBMS)操作的响应消息的标签字段;用于指示响应消息的整个长度的字段;MBMS操作成功字段;和要插入提取信息的字段。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186000(Integer), 12. The method as claimed in claim 11, wherein the field to be inserted with the extracted information comprises:a field for indicating a sum of length of the extracted information;a field for identifying an MTK;a field for indicating an actual MTK;a field for indicating whether a TEK must be decrypted with a TBK;a field for indicating whether a Message Authentication Code (MAC) portion is included when the broadcast service data is received; anda field for indicating a traffic key lifetime.(String), 12.如权利要求11所述的方法,其中要插入提取信息的字段包括:字段,表示提取信息的长度总和;用于识别MTK的字段;用于指示实际MTK的字段;用于指示TEK是否必须用TBK解密的字段;用于指示在接收到广播服务数据时是否包括消息认证码(MAC)部分的字段;和用于指示流量密钥生命周期的字段。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.317 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.333 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.334 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186000(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. § 119(a) to an application entitled “Smart Card and Method for Generating Response Message to be Delivered to Mobile Terminal Supporting Mobile Broadcast, and Mobile Terminal therefor” filed in the Korean Industrial Property Office on Nov. 29, 2007 and assigned Serial No. 2007-122969, the contents of which are hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile broadcast system, and more particularly to a method of processing a short-term key message in a terminal supporting mobile broadcast, and a terminal therefor. [0004]2. Description of the Related Art [0005]The Open Mobile Alliance (OMA) group researches standards for interworking among individual mobile solutions, and specifies two profiles as a broadcast standard established to be used appropriately for broadcast environment. One of the profiles is a Digital Rights Management (DRM) profile, and the other is a smart card profile. In the smart card profile, a video/audio stream encrypted with specific keys is transmitted to a terminal over a broadcast network. Further, a data stream having keys necessary for decrypting the encrypted video/audio stream is also transmitted to the mobile terminal over the same broadcast network, which is referred to as a Short-Term Key Message (STKM). [0006]In the smart card profile, the received STKM is subjected to a resending check by a Multimedia Internet KEYing (MIKEY) parser in the mobile terminal. Here, a Multimedia Broadcast/Multicast Service (MBMS) Traffic Key (MTK) included in the STKM is changed once every several seconds or minutes, and the STKM is transmitted every 0.5 seconds or every several seconds, thereby causing the mobile terminal to receive the same STKM several times or several tens of times until the key is updated once. Continuously performing a parsing and a key decryption every time the STKM is received results in a waste of mobile terminal resources. Therefore, as a method of reducing this resource waste, a resending check is essential. [0007]For the resending check, the STKM to be transmitted in a MIKEY message structure is used in the smart card profile. The MIKEY message structure is described as shown in FIG. 1 and the MTK is formatted by a simple binary encoding method, such as the MIKEY, in order to be transmitted. In particular, as a decision reference for the resending check, an MTK IDentification (ID) included in an MBMS EXT (Extension) 100 field in FIG. 1 is used. [0008]A procedure of the resending check will now be described with reference to FIG. 2. FIG. 2 shows an operational flowchart of a mobile terminal for a conventional resending check. [0009]Referring to FIG. 2, the mobile terminal determines whether an STKM is received, in step 200. If the STKM is received, the mobile terminal performs the resending check in step 205, and determines whether the received STKM is a new STKM in step 210. If the received STKM is not a new STKM, the mobile terminal goes to step 215 and discards the received STKM. If the received STKM is a new message, a parsing and key decryption process is performed on the mobile terminal or the smart card according to a location of a secure function. The process is classified into a Generic Bootstrapping Architecture (GBA)-Mobile Equipment (ME) (GBA_ME) scheme or a GBA_Universal Subscriber Identity Module (USIM) (GBA_U) scheme according to whether a location for processing the STKM in the smart card profile is a mobile terminal or a USIM, i.e., a smart card. In the GBA_U scheme, the STKM is delivered to a USIM by an Application Protocol Data Unit (APDU) command, and then the parsing and key decryption process is performed within the USIM. Then, the MTK or a Traffic Encryption Key (TEK) included in the STKM is delivered again to the mobile terminal. [0010]At this time, when a separate MIKEY parser is included in the mobile terminal for analyzing the STKM, the mobile terminal analyzes the MIKEY and stores the result information according to the analysis by performing the parsing operation, in step 220. Thereafter, the mobile terminal determines whether a response message is received from the USIM, in step 225. When the response message is received, the mobile terminal obtains the TEK by parsing the response message, in step 230. Subsequently, the mobile terminal delivers the stored result information and the TEK to a player, in step 235. [0011]In the player, a variety of information is required for reproducing a video/audio stream. However, in the case of the GBA_U scheme, a variety of information is included in the STKM, but the USIM delivers the only TEK. Therefore, since the mobile terminal must perform the parsing operation by using the separate MIKEY parser and have the values in a memory, the parsing operation causes memory and resources in the mobile terminal to be wasted. Moreover, independently from the parsing and key decryption procedure within the USIM, redundant operations are unnecessarily performed in the mobile terminal by analyzing the MIKEY and by analyzing the result information, which increases the load on the mobile terminal. SUMMARY OF THE INVENTION [0012]Accordingly, the present invention has been made to solve the above-mentioned problems occurring in the prior art, and the present invention provides a smart card and a method for generating a response message to be delivered to a mobile terminal supporting mobile broadcast in order to smoothly perform memory management and resource management in the mobile terminal, and provides a mobile terminal therefor. [0013]Also, the present invention provides a smart card and a method for generating a response message to be delivered to a mobile terminal supporting mobile broadcast, avoiding redundant operations of a USIM in the mobile terminal, and provides a mobile terminal therefor. [0014]In accordance with an aspect of the present invention, there is provided a smart card which is inserted into a mobile terminal supporting mobile broadcast and which generates a response message according to short-term key message processing, the smart card including an information extraction unit for, when a Short-Term Key Message (STKM) is delivered from the mobile terminal, extracting information necessary for decrypting and reproducing broadcast service data from the STKM; and a response message generation unit for generating a response message including the extracted information and for delivering the response message to the mobile terminal. [0015]In accordance with another aspect of the present invention, there is provided a mobile terminal into which a smart card is inserted and which processes a short-term key message, the mobile terminal including a receiving unit for receiving a Short-Term Key Message (STKM) over a broadcast network; a resending check unit for determining whether the received short-term key message is a new short-term key message, and delivering the received short-term key message to the smart card when the received short-term key message is a new short-term key message; and a decryption unit for obtaining information necessary for decrypting and reproducing broadcast service data from the response message by parsing the delivered response message when a response message is delivered from the smart card in response to delivery of the short-term key message. [0016]In accordance with another aspect of the present invention, there is provided a method of generating a response message to be delivered to a mobile terminal supporting mobile broadcast in a smart card, the method including receiving a Short-Term Key Message (STKM) from the mobile terminal; extracting information necessary for decrypting and reproducing broadcast service data from the short-term key message; generating a response message including the extracted information; and delivering the response message to the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0018]FIG. 1 is a diagram illustrating a conventional Multimedia Internet KEYing (MIKEY) message structure; [0019]FIG. 2 is a operational flowchart illustrating a conventional resending check of a mobile terminal; [0020]FIG. 3 is a structure diagram illustrating a mobile terminal and a smart card according to an embodiment of the present invention; [0021]FIG. 4 is an operational flowchart between a mobile terminal and a smart card according to an embodiment of the present invention; and [0022]FIG. 5 is an exemplary diagram illustrating a Universal Subscriber Identity Module (USIM) response message structure according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT [0023]Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, the same elements will be designated by the same reference numerals although they are shown in different drawings. Further, in the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. [0024]The present invention provides a method of efficiently processing a Short-Term Key Message (STKM) in the mobile terminal supporting the mobile broadcast. For this purpose, the present invention provides an improved structure of a response message in processing the STKM in the smart card. Particularly, in the present invention, a variety of information necessary for reproducing in the player is included in the response message and delivered to the mobile terminal; thereby the mobile terminal can easily obtain the desired information through the response message. Therefore, when the STKM is processed in the mobile terminal, there is no need to process operations other than the resending check, and the information does not need to be stored separately. [0025]First, reference will now be made in brief to information related to an encryption key used for service protection and contents protection in the mobile broadcast system and usage thereof according to an embodiment of the present invention. After the mobile terminal is registered as a service subscriber to use service and contents broadcasting from a broadcast system, when the mobile terminal subscribes a corresponding service, an STKM used for decrypting an actual encrypted service and contents can be obtained. This STKM includes a Traffic Encryption Key (TEK), which is encrypted with a Service Encryption and Authentication Key (SEAK) having an integrated format of a Service Encryption Key (SEK) with a Service Authentication Key (SAK) in order to protect the TEK, and a Message Authentication Code (MAC) function can be applied. In the future, this TEK will be used to decrypt actual encrypted services and contents. [0026]Hereinafter, a smart card for generating a response message to be delivered to the mobile terminal supporting mobile broadcast and operations of the mobile terminal receiving the response message according to an embodiment of the present invention, will be described with reference to FIG. 3. [0027]Referring to FIG. 3, the mobile terminal 10 receives encrypted broadcast services from a server managing BroadCAST (BCAST) services, and these broadcast service may include a video/audio broadcast service, a file download service, etc. [0028]The mobile terminal 10 includes a Content Provider-Client (CP-C) 51, a Stream Distribution-Client (SD-C) 52, a File Distribution-Client (FD-C) 53, and a Content Provider-Decryption (CP-D) 54. [0029]First, the SD-C component 52 acts as a receiving unit for contents broadcasted in an encrypted stream format, and delivers the received contents to the CP-D component 54 to be decrypted. Further, the FD-C component 53 also acts as a receiving unit, and delivers contents broadcasted in an encrypted file format to the CP-D component 54 for decryption. The CP-C component 51 performs registration and subscription, and by this registration and subscription the CP-C component 51 serves to obtain an encryption key necessary for decrypting the encrypted contents and to deliver it the CP-D component 54. [0030]The mobile terminal 10 having the above structure can use the services by decrypting the encrypted contents with the TEK in the CP-D component 54 through the SD-C component 52 in case of the stream contents, or through the FD-C component 53 in case of the file contents. [0031]According to the embodiment of the present invention, when the STKM generated by combining information necessary for decrypting and reproducing the broadcast service data, etc., is transmitted to the FD-C component 53 of the mobile terminal 10, the transmitted STKM is delivered to a resending check unit (not shown) in order to determine whether this STKM is a new STKM. When the transmitted STKM is a new STKM as the decision result, the resending check unit delivers the STKM to the USIM 20 through an interface. [0032]The CP-D component 54, acting as a decryption unit corresponding to delivery of the STKM, serves to parse the response message from the USIM 20, and then obtains information necessary for decrypting and reproducing the broadcast service data from the response message. After obtaining the information necessary for decrypting and reproducing the broadcast service data, the CP-D component 54 uses the encryption key, such as the TEK, etc., to decrypt the broadcast service data, and uses other information to reproduce the broadcast service data in a stream format. [0033]On the other hand, the USIM 20 has a structure such that the USIM 20 is inserted into the mobile terminal 20 through an interface, including an information extraction unit 55 and a response message generation unit 56. The information extraction unit 55 serves to obtain the information necessary for decrypting and reproducing the encrypted broadcast service data from the STKM delivered from the mobile terminal 10 through an interface. This information necessary for decrypting and reproducing the broadcast service data includes an MBMS Traffic Key (MTK) IDentification (ID) for identifying the MTK, MTK data, a terminal binding flag value for indicating whether the TEK must be decrypted with a Terminal Binding Key (TBK), a traffic authorization flag value for indicating whether there is included a MAC portion when the broadcast service data is received, and a traffic key lifetime. In addition, the response message generation unit 56 serves to generate the STKM-processed result, i.e., the response message including the above information, and to deliver the result to the mobile terminal 10 through an interface. [0034]Hereinafter, operations between the mobile terminal and the smart card will now be described with reference to FIG. 4. In FIG. 4, the mobile terminal (hereinafter, Mobile Equipment (ME)) 10 is a terminal capable of receiving the BCAST service, and may be connected to a cellular network according to the mobile terminal performance. In the following description, it is assumed that the mobile terminal can connect to a cellular network. Further, in FIG. 4, as an example of a smart card that is inserted into the mobile terminal, the Universal Subscriber Identity Module (USIM) 20 will be described. [0035]First, the ME 10 determines whether the STKM is received from a broadcast network, in step 300. When the STKM is received, the ME 10 determines, in step 310, whether the received STKM is a new STKM by performing a resending check, in step 305. More specifically, if an MTK ID included in the received STKM is less than or equal to a previous received MTK ID, the mobile terminal determines that the received STKM is not a new STKM. If the MTK ID is greater than the previous received MTK ID, the mobile terminal determines that the received STKM is a new STKM, thereby performing the resending check. As the result of the resending check, when the received STKM is determined to be a new message, the ME 10 delivers the new STKM to the USIM 20, in step 315. [0036]Then, the USIM 20 parses the new STKM, in step 320. By performing parsing and decryption of this STKM, the USIM 20 extracts information necessary for decrypting and reproducing broadcast service data, in step 325. The MTK is also included in the extracted information. More specifically, because the STKM is delivered in a MIKEY message format, the USIM 20 parses the MIKEY message. Here, the MIKEY message includes the MTK, and if a salt key is available, the salt key is also included. When parsing this MIKEY message, the USIM 20 retrieves an MBMS Service Key (MSK) with a given MSK ID in an MBMS Extension field of the MIKEY message. If there is no necessary MSK, the USIM 20 determines that the MIKEY message processing is failed, and discards the MIKEY message. [0037]Unlike the above case, if there is a necessary MSK, the USIM 20 extracts the MTK protected by the MSK, as well as the salt key (if the salt key is available) and broadcast services, i.e., the information necessary for decrypting and reproducing a video/audio stream from the MIKEY message. By this extraction, the USIM 20 performs an MBMS Generation and Validation Function (MGV-F), using the MSK. When this MGV-F procedure is successful, the USIM 20 extracts the MTK from the MIKEY message. At this time, the USIM 20 stores other parameters, such as a key lifetime, an MTK ID extracted from the MIKEY message, etc. [0038]Therefore, when information necessary for decrypting and reproducing broadcast service data is extracted through the MIKEY message parsing, the USIM 20 generates a response message including the extracted information, in step 330. In other words, the response message indicates that the USIM 20 processes the STKM delivered from the ME 10 in accordance with the GBA_U (Generic Bootstrapping Architecture_USIM) scheme. [0039]When the USIM 20 delivers the generated response message to the ME 10, in step 335, the ME 10 performs decryption and reproduction of broadcast service data by using information included in the response message, in step 340, i.e., the ME 10 decrypts the broadcast service data and delivers information necessary for reproducing data to the player in order to reproduce the broadcast service in the player. [0040]In this manner, since the ME 10 can obtain the MTK as well as a variety of information from the USIM 20 without a separate MIKEY parser, there is no need to parse the MIKEY message without overlapping with the USIM 20, and no need to store the result information according to the parsing. [0041]The structure of the response message to be delivered to the mobile terminal is illustrated as shown in FIG. 5. FIG. 5 is an exemplary diagram illustrating a USIM response message structure according to an embodiment of the present invention, newly proposing the response message structure specified in 3rd Generation Partnership Project (3GPP) 31.102.v780. [0042]Referring to FIG. 5, the present invention provides a new structure of the response message in which, in addition to the TEK, broadcast service data, i.e., a variety of information necessary for decrypting and reproducing a video/audio stream (e.g., a traffic authorization flag value, a key lifetime, etc.) is included. [0043]As shown in FIG. 5, the response message schema table will be described below. The “Description” column indicates a meaning of a corresponding element or an attribute value, and the “Coding” column indicates the type of a corresponding element or an attribute value. [0044]FIG. 5 shows a field structure sequentially illustrating the response message defined according to the present invention, together with descriptions of each field of the response message. In the structure of this response message, the response message includes a one-byte tag field for indicating a response message on an MBMS operation, a field for indicating an entire length of the response message, a one-byte field for indicating that the MBMS operation is successful, and a key identifier TLV field to be inserted with a variety of actual information. A tag value of 53 is used for the tag field of the above fields in order for the ME 10 to identify the message delivered from the USIM 20 as a response message. Further, the tag field and the field for indicating the entire length are encrypted with a Basic Encoding Rules (BER)-Tag Length Value (TLV) data object. [0045]In particular, key identifier TLV field indicated by reference number 400 has the same structure as that of reference number 410, and is inserted with a variety of information, such as an MTK, a traffic authorization flag value, and a key lifetime, in a TLV format. This information is included in the STKM, and specifically, in the BCAST extension field or in other fields of the MIKEY message structure. Therefore, when the STKM delivered from the ME 10 is parsed and analyzed in the USIM 20, after extracting corresponding information from each field, the extracted information is gathered and included in the response message in an identical structure as shown in reference number 410. [0046]The schema table 410 of the key identifier TLV field 400 will be described below. The “Byte(s)” column indicates a location of corresponding element value or an attribute value; the “Length” column indicates a size of a corresponding element value or an attribute value; and the “M/O” column is used to determine whether a corresponding element value or an attribute value is an essential content. If the value is an essential content, the ‘M’ value is used, and if not, i.e., if the value is optional, the ‘O’ value is used. [0047]This response message structure includes “Length of key Identifier TLV” for indicating a sum of length of all information included in an actual key identifier TLV field 400, “MBMS Traffic Key ID” for identifying the MTK, “MBMS Traffic Key data” for indicating an actual MTK, “Terminal Binding Flag” for indicating whether the TEK is decrypted with the Terminal Binding Key (TBK), “Traffic Authentication Flag” for indicating whether a MAC portion is included when a video/audio stream is received, “Traffic Key Lifetime” for indicating the traffic key lifetime, “Salt Key Length” for indicating a length of the salt key when the salt key is available, and “Salt Key Data” for indicating an actual salt key, etc. [0048]When the response message having the above-mentioned structure is received, the mobile terminal controls decryption of a video/audio stream by using a variety of information necessary for the MTK and player as well as reproduction by a player. Therefore, in the existing mobile terminal, information necessary for decrypting and reproducing a video/audio stream is parsed and analyzed from the STKM in advance, and the STKM is then delivered to the USIM. However, in the present invention, simply the mobile terminal only processes the resending check and the response message. As described above, according to the present invention, the same processing procedures in both the mobile terminal and the USIM, that is, the procedures of key decryption after parsing and analyzing the STKM, can be prevented from being carried out repeatedly. [0049]According to the present invention, in the smart card profile GBA_U scheme, there is an advantage in that the procedures of parsing, analyzing, and key-decrypting the STKM can be prevented from being carried out repeatedly. Further, according to the present invention, since the mobile terminal only processes the response message from the USIM, a processing load on the mobile terminal can be reduced. Further, since there is no need to store the parsing and analyzing results in a separate memory, memory can be prevented from being used uselessly. [0050]While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请根据 35 U.S.C. § 119(a) 于 2007 年 11 月 29 日向韩国工业产权局提交的题为“智能卡和生成响应消息的方法,以传送到支持移动广播的移动终端及其移动终端”的申请,并分配了序列号 . 2007-122969,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及一种移动广播系统,尤其涉及一种在支持移动广播的终端中处理短期密钥消息的方法及其终端。 [0004] 2.相关技术的描述 [0005] 开放移动联盟 (OMA) 小组研究各个移动解决方案之间的互通标准,并将两个配置文件指定为广播标准,以适用于广播环境。 其中一个配置文件是数字版权管理 (DRM) 配置文件,另一个是智能卡配置文件。 在智能卡配置文件中,使用特定密钥加密的视频/音频流通过广播网络传输到终端。 此外,具有对加密的视频/音频流进行解密所需的密钥的数据流也通过相同的广播网络传输到移动终端,这被称为短期密钥消息(STKM)。 [0006] 在智能卡配置文件中,接收到的STKM由移动终端中的多媒体互联网密钥(MIKEY)解析器进行重发检查。 这里,包含在STKM中的多媒体广播/多播服务(MBMS)流量密钥(MTK)每隔几秒或几分钟改变一次,并且每隔0.5秒或每隔几秒发送一次STKM,从而使移动终端接收到 相同的 STKM 多次或数十次,直到密钥更新一次。 每次收到STKM都不断地进行解析和密钥解密,造成移动终端资源的浪费。 因此,作为减少这种资源浪费的方法,重新发送检查是必不可少的。 [0007] 对于重新发送检查,在智能卡配置文件中使用要在 MIKEY 消息结构中传输的 STKM。 MIKEY消息结构的描述如图3所示。 1和MTK被一个简单的二进制编码方法格式化,例如MIKEY,以便被传输。 特别是,作为重新发送检查的决策参考,MBMS EXT(扩展)中包含的 MTK IDentification(ID) 100 图中的字段。 1 被使用。 [0008] 现在将参考图3描述重新发送检查的过程。 2. 图。 图2示出了用于传统重发支票的移动终端的操作流程图。 [0009] 参考图。 2、移动终端判断是否收到STKM,在步骤 200 . 如果接收到 STKM,则移动终端在步骤 205 ,并判断接收到的STKM是否为新的STKM 210 . 如果接收到的STKM不是新的STKM,移动终端进入步骤 215 并丢弃接收到的 STKM。 如果接收到的STKM为新消息,则在移动终端或智能卡上根据安全功能的位置进行解析和密钥解密过程。 该过程根据在智能卡配置文件中处理STKM的位置是否为通用引导架构(GBA)-移动设备(ME)(GBA_ME)方案或GBA_通用用户识别模块(USIM)(GBA_U)方案。 移动终端或USIM,即智能卡。 在GBA_U方案中,STKM通过应用协议数据单元(APDU)命令传递给USIM,然后在USIM内部进行解析和密钥解密过程。 然后,将包含在STKM中的MTK或流量加密密钥(TEK)再次传递给移动终端。 [0010] 此时,当移动终端中包含单独的MIKEY解析器用于解析STKM时,移动终端通过执行解析操作来解析MIKEY并根据解析存储结果信息,在步骤 220. 此后,移动终端确定是否从USIM接收到响应消息,在步骤 225 . 当接收到响应消息时,移动终端通过解析响应消息获得TEK,在步骤 230 . 随后,移动终端将存储的结果信息和TEK传送给玩家,在步骤 235 . [0011] 在播放器中,再现视频/音频流需要各种信息。 然而,在 GBA_U 方案的情况下,STKM 中包含各种信息,但 USIM 提供唯一的 TEK。 因此,由于移动终端必须使用单独的MIKEY解析器进行解析操作,并将值保存在内存中,因此解析操作会浪费移动终端中的内存和资源。 此外,独立于USIM内的解析和密钥解密过程,通过分析MIKEY和分析结果信息,在移动终端中不必要地执行冗余操作,这增加了移动终端的负载。 发明内容 [0012] 因此,本发明旨在解决现有技术中出现的上述问题,并且本发明提供了一种智能卡和一种用于生成响应消息的方法,该响应消息被传送到支持移动广播的移动终端,以便 在移动终端中顺利进行内存管理和资源管理,并提供了一种移动终端。 [0013] 此外,本发明提供了一种智能卡和一种用于生成响应消息以传送到支持移动广播的移动终端的方法,避免了移动终端中USIM的冗余操作,并为此提供了一种移动终端。 [0014] 根据本发明的一个方面,提供了一种插入支持移动广播的移动终端并根据短期密钥消息处理生成响应消息的智能卡,该智能卡包括信息提取单元,用于 ,当从移动终端传送短期密钥消息(STKM)时,从STKM中提取解密和再现广播服务数据所需的信息; 响应消息生成单元,用于生成包括提取的信息的响应消息并将响应消息传送到移动终端。 [0015] 根据本发明的另一方面,提供了一种移动终端,其中插入了智能卡并且处理短期密钥消息,该移动终端包括用于接收短期密钥消息(STKM)的接收单元 )通过广播网络; 重发校验单元,用于判断接收到的短期密钥信息是否为新的短期密钥信息,当接收到的短期密钥信息为新的短期信息时,将接收到的短期密钥信息下发给智能卡 关键信息; 以及解密单元,用于在响应于短期密钥消息的传递而从智能卡传递响应消息时,通过解析传递的响应消息,从响应消息中获得解密和再现广播服务数据所需的信息。 [0016] 根据本发明的另一方面,提供了一种生成响应消息的方法,该响应消息将被传送到支持智能卡中的移动广播的移动终端,该方法包括从智能卡接收短期密钥消息(STKM)。 移动终端; 从短期密钥消息中提取解密和再现广播服务数据所需的信息; 生成包括提取信息的响应消息; 将响应消息下发给移动终端。 附图的简要说明 [0017] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0018] 如图。 附图说明图1是说明传统多媒体互联网键控(MIKEY)消息结构的示意图; [0019]如图。 图2是现有的移动终端重发检查的动作流程图。 [0020] 如图。 图3为本发明实施例的移动终端和智能卡的结构示意图。 [0021] 如图。 图4为本发明实施例移动终端与智能卡之间的操作流程图。 和 [0022] 如图。 图5是图示根据本发明实施例的通用用户识别模块(USIM)响应消息结构的示例图。 示例性实施例的详细说明 [0023] 在下文中,将参照附图描述本发明的示例性实施例。 在以下描述中,相同的元件将由相同的附图标记表示,尽管它们在不同的附图中示出。 此外,在本发明的以下描述中,当可能使本发明的主题不太清楚时,将省略对包含在本文中的已知功能和配置的详细描述。 [0024] 本发明提供了一种在支持移动广播的移动终端中有效处理短期密钥消息(STKM)的方法。 为此,本发明提供了一种改进的响应消息结构,用于处理智能卡中的STKM。 特别地,在本发明中,在播放器中再现所需的各种信息被包含在响应消息中并被传递到移动终端; 从而移动终端可以很容易地通过响应消息获得想要的信息。 因此,在移动终端处理STKM时,不需要处理重发校验以外的操作,也不需要单独存储信息。 [0025] 首先,现在将简要地参考与根据本发明实施例的在移动广播系统中用于服务保护和内容保护的加密密钥及其使用有关的信息。 在移动终端注册为服务订阅者以使用广播系统广播的服务和内容之后,当移动终端订阅相应的服务时,可以获得用于解密实际加密的服务和内容的STKM。 此 STKM 包括流量加密密钥 (TEK),该密钥使用服务加密和验证密钥 (SEAK) 加密,该密钥具有服务加密密钥 (SEK) 与服务验证密钥 (SAK) 的集成格式,以保护 TEK , 并且可以应用消息验证码 (MAC) 功能。 将来,此 TEK 将用于解密实际的加密服务和内容。 [0026] 在下文中,将参照图1描述根据本发明实施例的用于生成要传送到支持移动广播的移动终端的响应消息的智能卡以及接收响应消息的移动终端的操作。 3. [0027] 参考图。 3、移动端 10 从管理BroadCAST(BCAST)服务的服务器接收加密的广播服务,这些广播服务可以包括视频/音频广播服务、文件下载服务等。 [0028] 移动终端 10 包括一个内容提供者-客户端 (CP-C) 51 , 流分发客户端 (SD-C) 52 , 文件分发客户端 (FD-C) 53 ,以及内容提供者解密 (CP-D) 54 . [0029] 一、SD-C组件 52 充当以加密流格式广播的内容的接收单元,并将接收到的内容传递给 CP-D 组件 54 被解密。 此外,FD-C 组件 53 还充当接收单元,并将以加密文件格式广播的内容传送到 CP-D 组件 54 用于解密。 CP-C 组件 51 执行注册和订阅,并通过此注册和订阅 CP-C 组件 51 用于获取解密加密内容所需的加密密钥并将其传递给 CP-D 组件54 . [0030] 移动终端 10 具有上述结构的可以通过使用 CP-D 组件中的 TEK 对加密内容进行解密来使用服务 54 通过 SD-C 组件 52 在流内容的情况下,或通过 FD-C 组件 53 在文件内容的情况下。 [0031] 根据本发明的实施例,当通过组合解密和再现广播服务数据等所需的信息而生成的STKM被发送到FD-C组件时 53 移动终端的 10 ,发送的STKM被传递到重新发送检查单元(未示出)以确定该STKM是否是新的STKM。 当发送的STKM是新的STKM作为判定结果时,重发校验单元将STKM下发给USIM 20 通过一个界面。 [0032] CP-D 组件 54 ,作为对应于 STKM 交付的解密单元,用于解析来自 USIM 的响应消息 20 ,然后从响应消息中获得解密和再现广播服务数据所需的信息。 在获得解密和再现广播业务数据所需的信息后,CP-D组件 54 使用TEK等加密密钥对广播服务数据进行解密,并使用其他信息以流格式再现广播服务数据。 [0033] 另一方面,USIM 20 具有这样的结构,使得 USIM 20 插入移动终端 20 通过一个接口,包括一个信息提取单元 55 和响应消息生成单元 56 . 信息提取单元 55 用于从移动终端传送的 STKM 中获取解密和再现加密广播服务数据所需的信息 10 通过一个界面。 解密和再现广播服务数据所需的该信息包括用于识别 MTK、MTK 数据的 MBMS 流量密钥 (MTK) 标识 (ID)、用于指示是否必须用终端绑定密钥解密 TEK 的终端绑定标志值 ( TBK)、用于指示在接收到广播服务数据时是否包含MAC部分的流量授权标志值,以及流量密钥寿命。 此外,响应消息生成单元 56 用于生成STKM处理的结果,即包含上述信息的响应消息,并将结果传递给移动终端 10 通过一个界面。 [0034] 在下文中,现在将参照图1描述移动终端和智能卡之间的操作。 4. 在图 4、移动终端(以下简称移动设备(ME)) 10 是能够接收BCAST服务的终端,可以根据移动终端的性能连接到蜂窝网络。 在以下描述中,假设移动终端可以连接到蜂窝网络。 此外,在图 4 中。 参考图4,作为插入移动终端的智能卡的示例,通用用户识别模块(USIM) 20 将进行描述。 [0035] 首先,ME 10 确定是否从广播网络接收到 STKM,在步骤 300 . 当收到 STKM 时,ME 10 确定,在步骤 310 ,通过重发检查接收到的STKM是否为新的STKM,在步骤 305 . 更具体地,如果接收到的STKM中包括的MTK ID小于或等于先前接收到的MTK ID,则移动终端确定接收到的STKM不是新的STKM。 如果MTK ID大于之前接收到的MTK ID,则移动终端判断接收到的STKM是新的STKM,从而进行重发检查。 作为重发检查的结果,当确定收到的 STKM 是新消息时,ME 10 向 USIM 交付新的 STKM 20 , 在步 315 . [0036] 然后,USIM 20 在步骤中解析新的 STKM 320 . 通过对这个 STKM 进行解析和解密,USIM 20提取解密和再现广播服务数据所需的信息,在步骤 325 . MTK 也包含在提取的信息中。 更具体地说,因为 STKM 以 MIKEY 消息格式传递,所以 USIM 20 解析 MIKEY 消息。 这里,MIKEY 消息中包含 MTK,如果有可用的盐键,则还包含盐键。 当解析这个 MIKEY 消息时,USIM 20 在 MIKEY 消息的 MBMS 扩展字段中检索具有给定 MSK ID 的 MBMS 服务密钥 (MSK)。 如果没有必要的 MSK,USIM 20 确定MIKEY消息处理失败,丢弃MIKEY消息。 [0037] 与上述情况不同,如果有必要的 MSK,USIM 20 提取受 MSK 保护的 MTK,以及盐密钥(如果盐密钥可用)和广播服务,即从 MIKEY 消息中解密和再现视频/音频流所需的信息。 通过这种提取,USIM 20 使用 MSK 执行 MBMS 生成和验证功能 (MGV-F)。 当这个 MGV-F 程序成功时,USIM 20 从 MIKEY 消息中提取 MTK。 此时,USIM 20 存储其他参数,例如密钥生命周期、从 MIKEY 消息中提取的 MTK ID 等。 [0038] 因此,当通过 MIKEY 消息解析提取解密和再现广播服务数据所需的信息时,USIM 20 生成包含提取信息的响应消息,在步骤 330 . 换句话说,响应消息表明 USIM 20 处理从 ME 交付的 STKM 10 根据 GBA_U(通用自举体系结构_USIM)方案。 [0039] 当 USIM 20 将生成的响应消息传递给 ME 10 , 在步 335 , 主题 10 在步骤 340 ,即 ME 10 解密广播服务数据并将再现数据所需的信息传递给播放器,以便在播放器中再现广播服务。 [0040] 这样,由于 ME 10 可以从 USIM 获取 MTK 以及各种信息 20 如果没有单独的 MIKEY 解析器,则无需解析 MIKEY 消息而不与 USIM 重叠 20 ,无需根据解析存储结果信息。 [0041] 发送到移动终端的响应消息的结构如图1所示。 5. 图。 图5是说明根据本发明实施例的USIM响应消息结构的示例图,新提出3中指定的响应消息结构 rd 代合作伙伴计划 (3GPP) 31.102.v780。 [0042] 参考图。 如图5所示,本发明提供了响应消息的新结构,其中除了TEK之外,广播服务数据,即解密和再现视频/音频流所需的各种信息(例如,交通授权标志值) ,密钥寿命等)包括在内。 [0043] 如图所示。 参照图5,下面将描述响应消息模式表。 “Description”栏表示对应元素或属性值的含义,“Coding”栏表示对应元素或属性值的类型。 [0044] 如图。 图5示出了顺序说明根据本发明定义的响应消息的字段结构,以及响应消息的每个字段的描述。 在该响应消息的结构中,响应消息包括用于指示对MBMS操作的响应消息的一字节标签字段、用于指示响应消息的全长的字段、用于指示MBMS操作的一字节字段 操作成功后,一个关键标识符 TLV 字段将被插入各种实际信息。 标签值 53 用于上述字段的标签字段,以便 ME 10 识别从 USIM 传递的消息 20作为响应消息。 此外,标签字段和用于指示整个长度的字段用基本编码规则(BER)-标签长度值(TLV)数据对象加密。 [0045] 特别是,由参考号指示的密钥标识符 TLV 字段 400 具有与参考编号相同的结构 410 ,并以TLV格式插入MTK、流量授权标志值、密钥生存期等多种信息。 该信息包含在 STKM 中,特别是包含在 BCAST 扩展字段或 MIKEY 消息结构的其他字段中。 因此,当 STKM 从 ME 交付 10 在 USIM 中进行解析和分析 20 ,在从每个字段中提取相应的信息后,将提取的信息收集起来,并以与参考编号所示相同的结构包含在响应消息中 410 . [0046] 架构表 410 密钥标识符 TLV 字段 400 下面将进行描述。 “Byte(s)”列表示对应元素值或属性值的位置; “Length”列表示对应元素值或属性值的大小; “M/O”栏用于判断对应的元素值或属性值是否为必要内容。 如果该值是必要内容,则使用“M”值,如果不是,即如果该值是可选的,则使用“O”值。 [0047] 该响应消息结构包括“Length of key Identifier TLV”,用于指示包含在实际密钥标识符 TLV 字段中的所有信息的长度总和 400 , “MBMS Traffic Key ID”用于识别MTK,“MBMS Traffic Key data”用于指示实际MTK,“Terminal Binding Flag”用于指示TEK是否被终端绑定密钥(TBK)解密,“流量认证标志” 用于指示在接收到视频/音频流时是否包括MAC部分, “Traffic Key Lifetime”用于指示流量密钥寿命, “Salt Key Length”用于指示当盐密钥可用时盐密钥的长度,以及 “Salt Key Data”用于指示实际的盐键等。 [0048] 当接收到具有上述结构的响应消息时,移动终端通过使用MTK和播放器所需的各种信息以及播放器的再现来控制视频/音频流的解密。 因此,在现有的移动终端中,预先从STKM中解析和解析视频/音频流的解密和再现所需的信息,然后将STKM传递给USIM。 然而,在本发明中,简单的移动终端只处理重发检查和响应消息。 如上所述,根据本发明,可以避免重复执行移动终端和USIM中相同的处理过程,即在解析和分析STKM之后的密钥解密过程。 [0049] 根据本发明,在智能卡配置文件GBA_U方案中,具有可以防止重复执行STKM的解析、分析和密钥解密的过程的优点。 此外,根据本发明,由于移动终端仅处理来自USIM的响应消息,因此可以减轻移动终端的处理负荷。 此外,由于不需要将解析和分析结果存储在单独的存储器中,因此可以防止存储器被无用地使用。 [0050] 尽管本发明已参照其某些示例性实施例进行了展示和描述,但本领域技术人员将理解,在不背离如由 所附权利要求。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR101473488B1(String), KR1020090056026A(String), US20090143105A1(String), US8145270B2(String), WO2009069893A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.525 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR101473488B1(String), KR1020090056026A(String), US20090143105A1(String), US8145270B2(String), WO2009069893A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8145270B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.581 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR101473488B1(String), KR1020090056026A(String), US20090143105A1(String), US8145270B2(String), WO2009069893A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271672(Integer), KR101473488B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.634 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271672(Integer), KR1020090056026A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.669 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271672(Integer), US20090143105A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271672(Integer), US8145270B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271672(Integer), WO2009069893A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8145270B2(String), US8145270B2(String), 1332777600(Integer), 271672(Integer), 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.808 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186000(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186000(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:55.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186000(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.025 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 186000(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.132 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费(String), 2(Integer), 186000(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7522940B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.715 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Methods and mobile terminals for display of mobile terminal density information(String), 移动终端密度信息的显示方法及移动终端(String), US7522940B2(String), A method of providing information on a mobile terminal can include displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server.(String), 一种提供关于移动终端的信息的方法可以包括根据基于由在无线通信网络中操作的移动终端向服务器报告的参数的可选上下文,在移动终端显示器上显示移动终端密度信息。(String), US10/989652(String), 1100534400(Integer), US7522940B2(String), 1240243200(Integer), 1240243200(Integer), 美国(String), 4(Integer), 4(Integer), 23(Integer), DE10237906A1 | EP1176840A1 | EP1191802A2 | JP1999223674A | JP2002341053A | JP2003329779A | US20030100317A1 | US20030134648A1 | US20040171390A1 | US20040185839A1 | US20050086004A1 | US20060009240A1 | US6182010B1 | US6236933B1 | US6427113B1 | US6526349B2 | US6539300B2 | US6567661B2 | US6594576B2 | US6804524B1 | US6810321B1 | US7188026B2 | WO2002027691A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186001(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d8586f3a77d542aca4eca448c548c2d3.png(String), 186001(Integer), d8586f3a77d542aca4eca448c548c2d3.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Methods and mobile terminals for display of mobile terminal density information(String), 移动终端密度信息的显示方法及移动终端(String), US7522940B2(String), A method of providing information on a mobile terminal can include displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server.(String), 一种提供关于移动终端的信息的方法可以包括根据基于由在无线通信网络中操作的移动终端向服务器报告的参数的可选上下文,在移动终端显示器上显示移动终端密度信息。(String), US10/989652(String), 1100534400(Integer), US7522940B2(String), 1240243200(Integer), 1240243200(Integer), 美国(String), 2(Integer), 4(Integer), 4(Integer), 23(Integer), DE10237906A1 | EP1176840A1 | EP1191802A2 | JP1999223674A | JP2002341053A | JP2003329779A | US20030100317A1 | US20030134648A1 | US20040171390A1 | US20040185839A1 | US20050086004A1 | US20060009240A1 | US6182010B1 | US6236933B1 | US6427113B1 | US6526349B2 | US6539300B2 | US6567661B2 | US6594576B2 | US6804524B1 | US6810321B1 | US7188026B2 | WO2002027691A1(String), \20230420\d8586f3a77d542aca4eca448c548c2d3.png(String), 20(Integer), 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:56.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 1. A method of providing information on a mobile terminal comprising:displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server, the method further comprising:applying the mobile terminal density information to the selectable context to generate a geographic display associated with the contex, wherein the geographic display associated with the context comprises a map and a plurality of grid of locations overlaid thereon;wherein the density information further comprises velocity information associated with the mobile terminals; andwherein selected ones of the plurality of grid locations are rendered with color and opacity values based on mobile terminal density information associated with the selected ones of the plurality of grid locations.(String), 1.一种在移动终端上提供信息的方法包括:基于在无线通信网络中运行的移动终端向服务器报告的参数,根据可选择的上下文在移动终端显示器上显示移动终端密度信息,该方法还包括:将移动终端密度信息应用​​于可选上下文以生成与上下文相关联的地理显示,其中与上下文相关联的地理显示包括地图和覆盖在其上的多个位置网格;其中,密度信息还包括与移动终端相关联的速度信息;和其中,基于与多个网格位置中的所选位置相关联的移动终端密度信息,用颜色和不透明度值渲染多个网格位置中的所选位置。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 2. A method according to claim 1 further comprising:receiving the parameters from the mobile terminals at the server via ad-hoc reporting of the mobile terminals;compiling the parameters to provide the mobile terminal density information; andtransmitting the mobile terminal density information to the mobile terminal for display.(String), 2.根据权利要求1的方法还包括:通过移动终端的自组织上报,在服务器端接收来自移动终端的参数;编译参数以提供移动终端密度信息;和将移动终端密度信息发送给移动终端进行显示。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 3. A method according to claim 1 wherein a maximum opacity value is less than an opaque value so that the underlying map is visible through the plurality of grid locations overlaid thereon at the maximum opacity value.(String), 3.根据权利要求1的方法其中最大不透明度值小于不透明值,使得底层地图通过以最大不透明度值覆盖在其上的多个网格位置可见。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 4. A method according to claim 1 wherein the color values comprise a statistical representation of velocity of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 4.根据权利要求1的方法其中颜色值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的速度的统计表示。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 5. A method according to claim 1 wherein the opacity values comprise a statistical representation of a density of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 5.根据权利要求1的方法其中不透明度值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端密度的统计表示。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 6. A method according to claim 1 wherein the selectable context comprises a first selectable context selected from a plurality of selectable contexts, wherein some of the mobile terminal density information is suppressed according to the first selectable context and not suppressed according to a second selectable context.(String), 6.根据权利要求1所述的方法其中可选上下文包括从多个可选上下文中选择的第一可选上下文,其中一些移动终端密度信息根据第一可选上下文被抑制,并且根据第二可选上下文不被抑制。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 7. A method according to claim 1 wherein the selectable context comprises a shopping context, a commuting context, and/or an entertainment context.(String), 7.根据权利要求1的方法其中可选上下文包括购物上下文、通勤上下文和/或娱乐上下文。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 8. A method according to claim 7 wherein the selectable context comprises a sub-context.(String), 8.根据权利要求7的方法其中可选上下文包括子上下文。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 9. A method according to claim 1 carried out by a computer program product embodied in a computer readable medium executable by a processor.(String), 9.根据权利要求1所述的方法,由包含在可由处理器执行的计算机可读介质中的计算机程序产品执行。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 10. A method according to claim 1 carried out by a system comprising:a means for displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to server.(String), 10.根据权利要求1所述的方法,由系统执行包括:一种用于根据可选择的上下文在移动终端显示器上显示移动终端密度信息的装置,该上下文基于在无线通信网络中操作的移动终端向服务器报告的参数。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 11. A method according to claim 1 wherein the parameters comprise location information, velocity information, connectivity information, image information, and/or audio information.(String), 11.根据权利要求1所述的方法其中参数包括位置信息、速度信息、连通性信息、图像信息和/或音频信息。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 12. A mobile terminal comprising:a transceiver circuit configured to transmit/receive communications to/from a wireless communications network that provides service to the mobile terminal including parameters received from a server reported by mobile terminals operating in the wireless communications network to the server;a processor circuit, coupled to the transceiver, configured to provide mobile terminal density information according to a selectable context based on the parameters received from the server;a display, coupled to the processor circuit, configured to display the mobile terminal density information based on the parameters;wherein the processor circuit is further configured to provide a geographic display including the mobile terminal density information associated with the context;wherein the geographic display comprises a map and a plurality of grid of locations overlaid thereon;wherein the density information further comprises velocity information associated with the mobile terminals; andwherein selected ones of the plurality of grid locations are rendered with color and opacity values based on mobile terminal density information associated with the selected ones of the plurality of grid locations.(String), 12.移动终端包括:收发器电路,被配置为向/从无线通信网络发送/接收通信,该无线通信网络向移动终端提供服务,包括从服务器接收的参数,这些参数由在无线通信网络中操作的移动终端报告给服务器;处理器电路,耦合到收发器,被配置为基于从服务器接收的参数,根据可选择的上下文提供移动终端密度信息;显示器,与处理器电路耦合,用于根据参数显示移动终端密度信息;其中,处理器电路还被配置为提供包括与上下文关联的移动终端密度信息的地理显示;其中地理显示包括地图和覆盖在其上的多个位置网格;其中,密度信息还包括与移动终端相关联的速度信息;和其中,基于与多个网格位置中的所选位置相关联的移动终端密度信息,用颜色和不透明度值渲染多个网格位置中的所选位置。(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 13. A mobile terminal according to claim 12 wherein the parameters comprise location information, velocity information, connectivity information, and/or audio information.(String), 13.根据权利要求12所述的移动终端其中参数包括位置信息、速度信息、连通性信息和/或音频信息。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 14. A mobile terminal according to claim 13 wherein the connectivity information comprises a value associated with a number of other devices in communication with the mobile terminal over a channel other than that used to transmit the parameters.(String), 14.根据权利要求13所述的移动终端其中-连接性信息包括与通过不同于用于传输参数的信道的信道与移动终端通信的许多其他设备相关联的值。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 15. A mobile terminal according to claim 13 wherein the velocity information is used as an inversely proportional indicator of the mobile terminal density information.(String), 15.根据权利要求13所述的移动终端其中速度信息作为移动终端密度信息的反比指标。(String), 1(Integer), 14(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 16. A mobile terminal according to claim 12 wherein a maximum opacity value is less than an opaque value so that the underlying map is visible through the plurality of grid locations overlaid thereon at the maximum opacity value.(String), 16.根据权利要求12所述的移动终端其中最大不透明度值小于不透明值,使得底层地图通过以最大不透明度值覆盖在其上的多个网格位置可见。(String), 1(Integer), 15(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 17. A mobile terminal according to 12 wherein the color values comprise a statistical representation of velocity of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 17.移动终端根据12其中颜色值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的速度的统计表示。(String), 0(Integer), 16(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 18. A mobile terminal according to claim 12 wherein the opacity values comprise a statistical representation of a density of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations.(String), 18.根据权利要求12所述的移动终端其中不透明度值包括位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端密度的统计表示。(String), 1(Integer), 17(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.023 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 19. A mobile terminal according to claim 12 wherein the selectable context comprises a first selectable context selected from a plurality of selectable contexts, wherein some of the mobile terminal density information is suppressed according to the first selectable context and not suppressed according to a second selectable context.(String), 19.根据权利要求12所述的移动终端其中可选上下文包括从多个可选上下文中选择的第一可选上下文,其中一些移动终端密度信息根据第一可选上下文被抑制,并且根据第二可选上下文不被抑制。(String), 1(Integer), 18(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.024 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186001(Integer), 20. A mobile terminal according to claim 12 wherein the selectable context comprises shopping, commuting, crowding, parking, entertaining, and/or working.(String), 20.根据权利要求12所述的移动终端其中可选择的情境包括购物、通勤、拥挤、停车、娱乐和/或工作。(String), 1(Integer), 19(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.403 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186001(Integer), TECHNICAL FIELD OF THE INVENTION [0001]The invention generally relates to the field of electronics and, more particularly, to methods, mobile terminals, and computer program products for electronic communications. DESCRIPTION OF RELATED ART [0002]It is known to collect environmental parameters, such as weather-related parameters, from mobile terminals operating in a wireless communications network. For example, U.S. Pat. No. 6,567,661 to McDonnell et al. entitled “Distributed Telemetry Method and System” discusses a distributed telemetry method effected by coordinating the taking of readings or a parameter by mobile phone users. The parameter readings can be sent to a service system together with a location of the user. Collating the readings and location information may enable generation of a representation of the geographic variation of the measured parameter (see, for example, the abstract of McDonnell). [0003]It is further known to track in-vehicle cell phones within a given region to provide data for control of a traffic system. For example, U.S. Pat. No. 6,539,300 to Myr entitled “Method for Regional System Wide Optimal Signal Timing for Traffic Control Based on Wireless Phone Networks.” discusses obtaining signals from vehicular-based cellular phones to provide location information on the moving vehicles, which are input to an intelligent traffic control system to provide position information. Mathematical models may use the information and digital maps/algorithms to compute actual travel times (see, for example, the abstract of Myr). [0004]Other types of systems are discussed in the following references: EP 1191802; JP 11/223674; JP 2002/341053; JP 2003/329779; U.S. Pat. No. 6,236,933; US 2003/100317; WO 02/27691; U.S. Pat. No. 6,427,113; and DE 10237906. Notwithstanding the material discussed above, there is a need for improved usage of parameters collected from mobile terminals. SUMMARY [0005]Embodiments according to the invention can provide methods, mobile terminals, and computer program products for display of mobile terminal density information. Pursuant to these embodiments, a method of providing information on a mobile terminal can include displaying mobile terminal density information on a mobile terminal display according to a selectable context based on parameters reported by mobile terminals operating in a wireless communications network to a server. [0006]In some embodiments according to the invention, the method further includes receiving the parameters from the mobile terminals at the server via ad-hoc reporting of the mobile terminals. The parameters can be compiled to provide the mobile terminal density information and the mobile terminal density information can be transmitted to the mobile terminal for display. [0007]In some embodiments according to the invention, the mobile terminal density information can be applied to the selectable context to generate a geographic display associated with the context. In some embodiments according to the invention, the geographic display associated with the context is a map and a plurality of grid of locations overlaid thereon. [0008]In some embodiments according to the invention, the density information further includes velocity information associated with the mobile terminals. Selected ones of the plurality of grid locations can be rendered with color and opacity values based on mobile terminal density information associated with the selected ones of the plurality of grid locations. [0009]In some embodiments according to the invention, a maximum opacity value is less than an opaque value so that the underlying map is visible through the plurality of grid locations overlaid thereon at the maximum opacity value. In some embodiments according to the invention, the color values are a statistical representation of velocity of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations. In some embodiments according to the invention, the opacity values are a statistical representation of a density of mobile terminals located in a geographic area serviced by the wireless communications network corresponding to respective grid locations. [0010]In some embodiments according to the invention, the selectable context is a first selectable context selected from a plurality of selectable contexts, wherein some of the mobile terminal density information is suppressed according to the first selectable context and not suppressed according to a second selectable context. [0011]In some embodiments according to the invention, the selectable context can be a shopping context, a commuting context, and/or an entertainment context. In some embodiments according to the invention, the selectable context comprises a sub-context. In some embodiments according to the invention, the parameters can be location information, velocity information, connectivity information, image/video information and/or audio information. BRIEF DESCRIPTION OF THE DRAWINGS [0012]FIG. 1 is a schematic diagram that illustrates embodiments of a wireless communications network providing service to mobile terminals according to some embodiments of the invention. [0013]FIG. 2 is a block diagram that illustrates mobile terminals according to some embodiments of the invention. [0014]FIG. 3A is a schematic diagram that illustrates parameters collected reported by mobile terminals according to some embodiments of the invention. [0015]FIG. 3B is a schematic diagram that illustrates a mobile terminal density system according to some embodiments of the invention. [0016]FIG. 4 is a schematic diagram that illustrates a geographic display on a mobile terminal according to some embodiments of the invention. [0017]FIG. 5 is a schematic diagram that illustrates a geographic display on a mobile terminal according to some embodiments of the invention. [0018]FIG. 6A is a schematic diagram that illustrates a geographic display on a mobile terminal according to some embodiments of the invention. [0019]FIG. 6B is an enlarged view of a portion of FIG. 6A that illustrates a display of some mobile terminal density information according to a selectable context. [0020]FIG. 6C is an enlarged view of a portion of FIG. 6A that illustrates a display of some mobile terminal density information according to a selectable context. [0021]FIG. 7 is a flow chart that illustrates operations of mobile terminals according to some embodiments of the invention. DETAILED DESCRIPTION OF EMBODIMENTS ACCORDING TO THE INVENTION [0022]The invention is described more fully hereinafter with reference to the accompanying drawings, in which illustrative embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein the term “and/or” includes any and all combinations of one or more of the associated listed items. [0023]Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. [0024]It will be understood that although the terms first and second may be used herein to describe various components these components should not be limited by these terms. These terms are only used to distinguish one component from another. Thus, for example, a first component discussed below could be termed a second component without departing from the teachings of the present invention. [0025]The invention is described with reference to a flowchart and block diagrams of mobile terminals, communications networks, and operations thereof according to embodiments of the invention. It will be understood that each block of the flowchart and/or block diagrams, and combinations of blocks, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart and/or schematic block or blocks. [0026]It will be understood, that the invention may be practiced with any mobile terminal that operates in a communications network. A mobile terminal may be, for example, a single or dual mode cellular radiotelephone with or without a multi-line display; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a Personal Data Assistant (PDA) that can include a mobile terminal, pager. Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver: and a conventional laptop and/or palmtop receiver or other appliance all of which include a transceiver. [0027]It will be understood that mobile terminals according to the invention may operate in any type of wireless communications network. In some embodiments according to the invention, for example, the network may provide services broadly labeled as PCS (Personal Communications Services) including advanced digital cellular systems conforming to standards such as IS-136 and IS-95, lower-power systems such as DECT (Digital Enhanced Cordless Telephone), data communications services such as CDPD (Cellular Digital Packet Data), and other systems such as CDMA-2000, that are proposed using a format commonly referred to as Wideband Code Division Multiple Access (WCDMA). [0028]Mobile terminals according to the invention may also be used in celestial communications networks, such as satellite communications networks. The celestial wireless communications network may be employed to perform similar functions to those performed by the communications network of FIG. 1. In particular, the celestial wireless communication system typically includes one or more satellites that serve as relays or transponders between one or more earth stations and (satellite) mobile terminals. The satellites typically communicate with the satellite mobile terminals and earth stations via duplex communication links. Each earth station may, in turn, be connected to a Public Switched Telephone Network (PSTN) in a terrestrial communications networks, thereby allowing communications between the satellite mobile terminal, and other devices serviced by the network. [0029]FIG. 1 is a diagram that illustrates a wireless communications network (hereinafter “network”) 10 that supports communications in which mobile terminals 20 according to the invention can be used. Networks 10 are commonly employed to provide voice and data communications to subscribers using, for example, the standards discussed above. According to FIG. 1, a plurality of mobile terminals 20 can communicate with each other and other terminals, such as terminals 26, 28, via the network 10 and a PSTN 14. [0030]The wireless communications network 10 is organized as cells 1-2 that collectively can provide service to a geographic region. In particular, each of the cells can provide service to associated sub-regions included in the geographic region covered by the network 10. More or fewer cells can be included in the network 10, and the coverage area for the cells 1-2 may overlap. Each of the cells 1-2 may include an associated base station 30a-b. The base stations 30a-b can provide wireless communications between each other and the mobile terminals 20 in the associated geographic region to allow for communications therebetween. [0031]Each of the base stations 30a-b can transmit/receive data to/from the mobile terminals 20 over an associated control channel 22. For example, the base station 30a in cell 1 can communicate with the mobile terminal 20 over the control channel 22. The control channel 22 can be used, for example, to page the mobile terminal 20 in response to calls directed thereto or to transmit traffic channel assignments to the mobile terminal 20 over which a call associated therewith is to be conducted. The control channels 22 can be identified using control channel numbers or identifiers. For example, the mobile terminal 20 can store a channel number that identifies control channel 22 as the control channel on which it is currently camping. Although only one control channel is illustrated, it will be understood that each of the mobile terminals 20 may have a respective control channel 22 associated therewith. [0032]The mobile terminals 20 are configured to register with the network 10 when, for example, the mobile terminals are turned on. In particular, the mobile terminals use information, stored on a SIM card in the respective mobile terminal, to register with the network 10. Once the mobile terminals 20 are registered with the network 10, the mobile terminals 20 can receive service from the wireless communications network 10, such as placing and receiving calls via the wireless communications network 10 as the mobile terminals 20 move within the geographic region serviced by the network 10. [0033]The mobile terminals 20 may also be capable of sending and receiving messages over the respective control channel 22. In some embodiments according to the invention, the mobile terminals send/receive Short Message Service (SMS) or Enhanced Message Service (EMS) formatted messages, Multimedia Message Service (MMS), and/or Smartmessaging™ formatted messages. As is known to those skilled in the art, SMS and EMS messages can be transmitted on digital networks, such as GSM networks, allowing relatively small text messages (for example, 160 characters in size) to be sent and received via the network operator's message center to the mobile terminal 20, or from the Internet, using a so-called SMS (or EMS) “gateway” website. [0034]MMS is a messaging system for asynchronous mobile-to-mobile messaging, which enables communication of messages containing “rich media” content, i.e., content of types that tend to be more data-intensive than text, such as such as graphics, digital photographs, video, animation, sound files, and/or audio. MMS is standardized by the WAP Forum and the Third-Generation Partnership Project (3GPP) and is described in: “WAP MMS, Architecture Overview,” WAP-205, WAP Forum (Approved Version Apr. 25, 2001); “WAP MMS, Client Transactions Specification,” WAP-206, WAP Forum (Approved Version Jan. 15, 2002); “WAP MMS, Encapsulation Specification,” WAP-209, WAP Forum (Approved Version Jan. 5, 2002); “Requirements”, 3GPP specification 22.140; and “Architecture and Functionality,” 3GPP specification 23.140. [0035]WAP has been promulgated to enable application programs to be written to operate on a wide array of wireless communications networks by providing a standard for the presentation and delivery of wireless information and telephony services. As a result, various mobile terminals, such as mobile terminals, pagers, two-way radios, smartphones and communicators can utilize WAP to enable delivery of relevant information and services to mobile terminals. [0036]Accordingly, it will be understood that, as described further herein, the control channels 22 can be used to transmit mobile terminal density information to the mobile terminals 20 as an SMS, MMS, EMS or other type of message via a WAP client. In some embodiments according to the invention, the mobile terminal density information can be provided to the mobile terminals 20 via a “Midlet.” As is well known by those skilled in the art, a Midlet is a Java application designed to run on Java enabled devices such as cell phones and PDAs. A Midlet is based on the Java 2 Platform, Micro Edition, using the Connected Limited Device Configuration (CLDC), which defines a set of application programming interfaces and a virtual machine for resource-constrained devices, such as those discussed herein. Midlets are further discussed on the Internet at “www.sun.com.” It will be further understood that other information, such as maps and other dynamic graphical data may also be transmitted in a suitable message, including any or all of the above message types. [0037]FIG. 2 is a block diagram that illustrates a mobile terminal 20 according to some embodiments of the invention. According to some embodiments of the invention, mobile terminal density information is transmitted to the mobile terminal for display based on parameters reported by the mobile terminals. The mobile terminal density information may be a statistical representation of, for example, the number of mobile terminals estimated to be located within a geographic area at a particular time. [0038]As illustrated in FIG. 2, the mobile terminal 20 includes a transceiver circuit 242 that is operative to transmit and receive radio frequency communication signals to the network 10 via an antenna system 246. The antenna system 246 may include an antenna feed structure and one or more antennas. As is well known to those of skill in the art, a transmitter portion of the transceiver 242 converts the information which is to be transmitted by the mobile terminal 20 into electromagnetic signals suitable for radio communications. A receiver portion of the transceiver 242 demodulates electromagnetic signals which are received by the mobile terminal 20 from the network 10 to provide the information contained in the signals in a format which is understandable to the user. [0039]A user interface 244 of the mobile terminal 20 may include a variety of components, such as a display 254, a keypad 252, a speaker 256, and a microphone 250, operations of which are known to those of skill in the art. It will be understood that the functions of keypad 252 and the display 254 can be provided by a touch screen. The display may be used to provide images or graphics which the user can view, such as a map with a grid including collected parameters overlaid thereon, wherein the map represents a geographic area of interest to the user in a particular context, such as traveling to/from work, shopping, entertaining, or the like. [0040]A processor circuit 251 provides for overall operation of the mobile terminal 20 including coordination of communications via the transceiver circuit 242, the user interface 244, and other components and systems included in the mobile terminal 20. For example, the processor circuit 251 can provide communications signals to the transceiver 242 when the user speaks into the microphone 250 and receives communications signals from the transceiver 242 for the reproduction of audio through the speaker 256. The processor circuit 251 can generate characters for display on the display 254. For example, the processor circuit 251 can generate numbers for display when the user enters a telephone number on the keypad 252. The characters can also be generated by a character generator circuit which is not shown. [0041]The processor circuit 251 may be implemented using a variety of hardware and software. For example, operations of the processor circuit 251 may be implemented using special-purpose hardware, such as an Application Specific Integrated Circuit (ASIC) and programmable logic devices such as gate arrays, and/or software or firmware running on a computing device such as a microprocessor, microcontroller or digital signal processor (DSP). [0042]The mobile terminal 20 includes a SIM card 225. The SIM card 225 can be installed (or removed) from the mobile terminal 20 by inserting (or removing) the SIM card 225 into/from a SIM card holder. The SIM card 225 stores information, such as an International Mobile Subscriber Identity (IMSI) that identifies the subscriber to the network 10 and a secret key for authentication. In some embodiments according to the invention, the IMSI includes a 3-digit Mobile Country Code (MCC) which identifies the country and a 2-digit Mobile Network Code (MNC) which identifies the network within that country. It will be understood that the SIM card 225 can store data, such as maps representing geographic areas in which the mobile terminal may be used and can be displayed thereon. The SIM card 225 can also store selectable contexts that can be used to process the parameter data [0043]The SIM card 225 can also store selectable context information that can be applied to the mobile terminal density information provided to the mobile terminal 20. For example, the SIM card 225 may store selectable context such as a shopping context, an entertainment context, a traveling context, etc. It will be also understood that the selectable contexts stored by the SIM card 225 may be further subdivided into subcontexts. For example, the traveling context, discussed herein in reference to FIG. 4, may be further subdivided into a commuting to work context and a commuting from work context. In this way, the contexts may be hierarchically/logically related to one another so that each selectable context may be easier to locate and apply. [0044]In some embodiments according to the invention, the selectable context information can be stored in other types of internal or external non-volatile memory such as a Multi Media Card (MMC), a Secure Digital (SD) card, a Compact Flash (CF) card, a memory stick, and/or a Universal Serial Bus based non-volatile memory device. [0045]It will be understood that the selectable contexts can indicate which of the mobile terminal density information is to be displayed and which of the mobile terminal density information may be suppressed to, for example, simplify the display of mobile terminal density information for the user. The processor circuit 251 can apply the mobile terminal density information to the selectable context to provide a geographic display (on the display 254) that is associated with the selectable context. [0046]A memory 253 can store computer program instructions that, when executed by the processor circuit 251, carry out the operations described herein and shown in the figures. The memory 253 can be non-volatile memory, such as EEPROM (or flash memory), that retains the stored data while power is removed from the memory 253 to enable the storage of information, such as the WAP profile described above, to provide access to the network for the mobile terminal 20. [0047]The mobile terminal 20 may also include a camera 226 that is configured to generate image data corresponding to images sampled by the camera 226. For example, the camera 226 can be used to capture an image and/or video that may be reported as a parameter as discussed herein so that mobile terminal density information may be based on content of the image. [0048]The mobile terminal 20 shown in FIG. 2 also includes a geographic location circuit 260 that is configured to determine the geographic location of the mobile terminal using, for example, conventional GPS approaches (assisted or otherwise) known to those skilled in the art. It will be further understood that the geographic location circuit 260 can use other techniques to determine the mobile terminal geographic location information provided to the location server 135. As described herein, the mobile terminal geographic location information determined by the geographic location circuit 260 can be transmitted as a parameter on which the mobile terminal density information can be based. [0049]The mobile terminal 20 also includes a local wireless interface circuit 265 that can provide communication with the local wireless networks and devices associated therewith. In some embodiments according to the invention, the local wireless interface circuit 265 is a Bluetooth compliant interface. In some embodiments according to the invention, the local wireless interface circuit 265 is a WLAN compliant interface. [0050]The mobile terminal 20 can report parameters collected by the mobile terminal 20 to the network 10 via, for example, the base station 30. Some of the parameters that can be collected by the mobile terminal 20 include the geographic location of the mobile terminal, the velocity of the mobile terminal 20, an audio level sampled by the mobile terminal 20, image/video data, device type tag, and/or connectivity to other mobile terminals in the area. For example, the microphone 250 can be used to sample the ambient audio level in the local environment to provide the audio level parameter. The audio level parameter may be used to determine (at least in part) environmental parameters near the mobile terminal 20. A high audio level may indicate, for example, traffic congestion, construction, and other situations which may indicate higher or lower densities than may otherwise be evident. If the mobile terminal 20 samples an unusually high level of audio, it may be determined that there is an increased likelihood of congestion even though relatively few mobile terminals have been otherwise detected. In some embodiments according to the invention, the speaker 256 can be used to sample the ambient audio level in the local environment to provide the audio level parameter. [0051]The device type tag parameter can indicate the type of device that is reporting the parameters. The device type tag can include, for example, car (i.e., where the device is integrated into a car), personal digital assistant, laptop, cellphone, or the like. In some embodiments according to the invention, the device type tag parameter can change as the use or configuration of the device changes. For example, a cellphone device type tag may change (or be further defined) from “cellphone” to “cellphone/car” when the cellphone is connected to an auxiliary power outlet in a car. [0052]The connectivity parameter may indicate the presence of other mobile terminals in the area which may not be suitably equipped with geographic location circuits or may not participate in the same communications network. Accordingly, the presence of these otherwise undetected mobile terminals may be considered in determining mobile terminal density information. The connectivity parameter may be collected by the mobile terminal 20 using the local wireless interface circuit 265 that can detect, for example, the presence of a mobile terminal 270 within range of the local wireless interface circuit 265. It will be understood that the connectivity parameter can be further defined using the device type tag parameters described above. For example, each of the other mobile terminals in the area that are in communication with the mobile terminal 20 reporting the parameters can have an associated device type tag parameter so that when the connectivity parameter is reported, the system can further define what types of terminals are local to the mobile terminal 20 (which may be used to provide more accurate density information). [0053]In some embodiments according to the invention, the connectivity parameter may also specify a geographical location that the mobile terminal 20 retrieved from another device, such as the mobile terminal 270, if for example, the mobile terminal 20 is not itself equipped with a geographic location circuit or is temporarily unable to determine it's own position using a geographic location circuit. [0054]FIG. 3A is a schematic diagram that illustrates the collection of parameters that may be used to determine mobile terminal density information according to some embodiments of the invention. In particular, the mobile terminal 20 can collect connectivity information based on a number of other mobile terminals brought within range of the local wireless interface discussed above in reference to FIG. 2. Furthermore, the mobile terminal 20 may sample the ambient audio level to provide the audio level parameter which may also be used in determining the mobile terminal density information. [0055]It will be understood that the parameters collected by the mobile terminal 20 may be weighted based on the type of parameter which is collected or based on which other types of parameters are collected and/or how many mobile terminals are currently providing parameters within a particular geographic area. For example, the audio level parameter may be weighted comparatively less than location information reported by the mobile terminal 20 whereas the connectivity parameter may be weighted more than the audio level parameter but less than the location information reported by the mobile terminal. [0056]FIG. 3B is a schematic illustration depicting mobile terminals operating in a geographic area serviced by the network 10. According to FIG. 3B, mobile terminals 20 are shown at various positions within the geographic area including located on or at roadways, shopping areas, entertainment areas and other areas. The number of mobile terminals 20, as well as the spacings thereof, depicts the density of mobile terminals in the specific areas. For example, a first area 310 is relatively densely populated with mobile terminals 20 whereas a second area 312 is less densely populated with mobile terminals 20. A third area 313 includes an entertainment/shopping area populated by mobile terminals 20, which may be moving more slowly than those shown in the first and second areas 312 and 313 (or may even be stationary). [0057]According to some embodiments of the invention, mobile terminals 20 report parameters to a mobile terminal density information server (hereinafter the “server”) 305. It will be understood that the reporting of the parameters by the mobile terminals 20 can be done in an ad-hoc fashion wherein no request is required from the server 305 for the individual mobile terminals 20 to report parameters. It will be further understood that the reporting may be done in other ways, such as, using a synchronous type approach wherein mobile terminals 20 report at pre-assigned times or in response to a specific request from the server 305. It will be further understood that the server 305 may be directly connected to the network 10 or, alternatively, it may be indirectly coupled to the network 10 via a separate network, such as the Internet. In such embodiments where the server 305 is indirectly coupled to the network 10, the mobile terminal may report parameters via other networks, such as a WLAN, a Bluetooth network, etc. [0058]The server 305 receives the parameters from the mobile terminals 20 and compiles the parameters to provide the mobile terminal density information. As described above, the mobile terminal density information may be based upon various parameters reported by the mobile terminals such as geographic location, connectivity, velocity, image data, audio level, and other parameters. Furthermore, the parameters may be weighted differently in determining the mobile terminal density information to provide an overall more accurate indication of the density information for the user. For example, as described above, connectivity information may be used in conjunction with geographic information reported by a mobile terminal 20 to increase an estimate of the number of, for example, people at a specific geographic location even though the devices connected to the mobile terminal 20 may not be in communication with the network 10 or may not be equipped with geographic location circuitry as described above. [0059]The mobile terminal density information may be a statistical representation of, for example, the number of mobile terminals estimated to be located within a geographic area at a particular time. The statistical representation can be any type known to those skilled in the art, such as a moving average. [0060]It will be further understood that the parameters compiled by the server 305 to provide the mobile terminal density information may be treated as “context independent” so that the information may be interpreted differently depending on circumstances so that the data integrity of the server 305 may be preserved. Further, a context may be applied to the information as p(String), 发明技术领域 [0001] 本发明总体上涉及电子领域,更具体地,涉及用于电子通信的方法、移动终端和计算机程序产品。 相关技术说明 [0002] 已知从在无线通信网络中操作的移动终端收集环境参数,例如与天气相关的参数。 例如,美国专利。 麦克唐纳等人的第 6,567,661 号。 题为“分布式遥测方法和系统”讨论了一种分布式遥测方法,通过协调移动电话用户获取读数或参数来实现。 参数读数可以与用户的位置一起发送到服务系统。 整理读数和位置信息可以生成测量参数的地理变化的表示(例如,参见 McDonnell 的摘要)。 [0003] 还已知跟踪给定区域内的车载蜂窝电话以提供用于控制交通系统的数据。 例如,美国专利。 授予 Myr 的第 6,539,300 号,题为“基于无线电话网络的交通控制的区域系统范围最佳信号定时方法”。 讨论了从基于车辆的蜂窝电话获取信号以提供关于移动车辆的位置信息,这些信息被输入到智能交通控制系统以提供位置信息。 数学模型可以使用信息和数字地图/算法来计算实际旅行时间(例如,参见 Myr 的摘要)。 [0004] 以下参考文献中讨论了其他类型的系统:EP 1191802; JP 11/223674; JP 2002/341053; JP 2003/329779; 美国专利 第6,236,933号; 美国 2003/100317; WO 02/27691; 美国专利 第6,427,113号; 和 DE 10237906。尽管有上述材料,但仍需要改进对从移动终端收集的参数的使用。 概括 [0005] 根据本发明的实施例可以提供用于显示移动终端密度信息的方法、移动终端和计算机程序产品。 根据这些实施例,提供关于移动终端的信息的方法可以包括根据基于由在无线通信网络中操作的移动终端向服务器报告的参数的可选上下文,在移动终端显示器上显示移动终端密度信息。 [0006] 在根据本发明的一些实施例中,该方法还包括通过移动终端的自组织报告在服务器处从移动终端接收参数。 可以对参数进行编译,提供移动终端密度信息,并将移动终端密度信息传送到移动终端进行显示。 [0007] 在根据本发明的一些实施例中,可以将移动终端密度信息应用​​于可选上下文以生成与上下文相关联的地理显示。 在根据本发明的一些实施例中,与上下文相关联的地理显示是地图和覆盖在其上的多个位置网格。 [0008] 在根据本发明的一些实施例中,密度信息还包括与移动终端相关联的速度信息。 基于与多个网格位置中的选定位置相关联的移动终端密度信息,可以用颜色和不透明度值来渲染多个网格位置中的选定位置。 [0009] 在根据本发明的一些实施例中,最大不透明度值小于不透明值,使得通过以最大不透明度值覆盖在其上的多个网格位置可以看到底层地图。 在根据本发明的一些实施例中,颜色值是位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的速度的统计表示。 在根据本发明的一些实施例中,不透明度值是位于由对应于各个网格位置的无线通信网络服务的地理区域中的移动终端的密度的统计表示。 [0010]在根据本发明的一些实施例中,可选上下文是从多个可选上下文中选择的第一可选上下文,其中移动终端密度信息中的一些根据第一可选上下文被抑制并且根据第二可选上下文不被抑制。 [0011] 在根据本发明的一些实施例中,可选择的上下文可以是购物上下文、通勤上下文和/或娱乐上下文。 在根据本发明的一些实施例中,可选择的上下文包括子上下文。 在根据本发明的一些实施例中,参数可以是位置信息、速度信息、连接信息、图像/视频信息和/或音频信息。 附图的简要说明 [0012] 图1是图示根据本发明的一些实施例的向移动终端提供服务的无线通信网络的实施例的示意图。 [0013] 图2是说明根据本发明一些实施例的移动终端的框图。 [0014] 图3A是示出根据本发明一些实施例的由移动终端上报的参数收集的示意图。 [0015] 图3B是说明根据本发明一些实施例的移动终端密度系统的示意图。 [0016] 图4是示出根据本发明一些实施例的移动终端上的地理显示的示意图。 [0017] 图5是示出根据本发明一些实施例的移动终端上的地理显示的示意图。 [0018] 图6A是示出根据本发明一些实施例的移动终端上的地理显示的示意图。 [0019] 图6B是图6A的一部分的放大图,其示出了根据可选择的上下文显示一些移动终端密度信息。 [0020] 图6C是图6A的一部分的放大图,示出了根据可选择的上下文显示一些移动终端密度信息。 [0021] 图7是说明根据本发明一些实施例的移动终端的操作的流程图。 根据本发明的实施方案的详细说明 [0022] 下文将参照附图更全面地描述本发明,其中示出了本发明的说明性实施例。 然而,本发明可以以许多不同的形式体现,并且不应被解释为限于本文所阐述的实施例; 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明的范围充分传达给本领域技术人员。 相同的数字始终指代相同的元素。 如本文所用,术语“和/或”包括一个或多个相关列出的项目的任何和所有组合。 [0023] 除非另有定义,本文使用的所有术语(包括技术和科学术语)与本发明所属领域的普通技术人员通常理解的含义相同。 将进一步理解,术语,例如在常用字典中定义的术语,应被解释为具有与其在相关技术的上下文中的含义一致的含义,并且不会以理想化或过于正式的意义来解释,除非 在此明确如此定义。 [0024] 应当理解,尽管术语第一和第二可以在本文中用于描述各种组件,但这些组件不应受这些术语的限制。 这些术语仅用于区分一个组件与另一个组件。 因此,例如,在不背离本发明的教导的情况下,下面讨论的第一组件可以被称为第二组件。 [0025]参考根据本发明实施例的移动终端、通信网络及其操作的流程图和框图来描述本发明。 应当理解,流程图和/或框图的每个块,以及块的组合,可以由计算机程序指令来实现。 这些计算机程序指令可以被提供给通用计算机、专用计算机或其他可编程数据处理装置的处理器以生产机器,使得通过计算机或其他可编程数据处理装置的处理器执行的指令 ,创建用于实现流程图和/或示意图块或块中指定的功能的装置。 [0026] 应当理解,本发明可以用在通信网络中操作的任何移动终端来实践。 例如,移动终端可以是具有或不具有多线显示器的单模或双模蜂窝无线电话; 个人通信系统(PCS)终端,可以将蜂窝无线电话与数据处理、传真和数据通信能力相结合; 可以包括移动终端、寻呼机的个人数据助理 (PDA)。 Internet/Intranet 访问、Web 浏览器、管理器、日历和/或全球定位系统 (GPS) 接收器:以及传统的膝上型电脑和/或掌上型接收器或其他设备,所有这些都包括收发器。 [0027] 应当理解,根据本发明的移动终端可以在任何类型的无线通信网络中操作。 在根据本发明的一些实施例中,例如,网络可以提供广泛标记为PCS(个人通信服务)的服务,包括符合诸如IS-136和IS-95的标准的高级数字蜂窝系统、诸如DECT的低功率系统 (数字增强型无绳电话)、诸如 CDPD(蜂窝数字分组数据)之类的数据通信服务,以及诸如 CDMA-2000 之类的其他系统,它们被提出使用通常称为宽带码分多址 (WCDMA) 的格式。 [0028] 根据本发明的移动终端还可用于天体通信网络,例如卫星通信网络。 天体无线通信网络可用于执行与图1的通信网络执行的功能相似的功能。具体而言,天体无线通信系统通常包括一个或多个卫星,它们用作一个或多个地球站和地球站之间的中继器或转发器。 (卫星)移动终端。 卫星通常通过双工通信链路与卫星移动终端和地球站通信。 每个地球站又可以连接到陆地通信网络中的公共交换电话网络(PSTN),从而允许卫星移动终端和网络服务的其他设备之间的通信。 [0029] 图1是说明无线通信网络(以下称为“网络”)的图 10 支持移动终端的通信 20 根据本发明可以使用。 网络 10 例如,通常采用上述标准向用户提供语音和数据通信。 根据图1,多个移动终端 20 可以互相和其他终端通信,比如终端 26 , 28 , 通过网络 10 和一个 PSTN 14 . [0030] 无线通信网络 10 被组织为单元格 1 - 2 可以共同为一个地理区域提供服务。 特别地,每个小区可以为网络覆盖的地理区域中包括的相关子区域提供服务 10 . 网络中可以包含更多或更少的单元 10 ,以及小区的覆盖区域 1 - 2 可能重叠。 每个细胞 1 - 2 可能包括相关的基站 30 a - b . 基站 30 a - b 可以提供彼此与移动终端之间的无线通信 20在相关的地理区域中,以允许它们之间的通信。 [0031] 每个基站 30 a - b 可以向/从移动终端发送/接收数据 20 通过相关的控制信道 22 . 例如,基站 30 a 在单元格中 1 可与移动端通讯 20 通过控制通道 22 . 控制通道 22 可用于,例如,对移动终端进行寻呼 20 响应指向它的呼叫或向移动终端发送业务信道分配 20 将在其上进行与其相关联的呼叫。 控制通道 22 可以使用控制信道号或标识符来识别。 例如,移动终端 20 可以存储一个标识控制通道的通道号 22 作为它当前驻留的控制通道。 尽管仅图示了一个控制信道,但是应当理解,每个移动终端 20 可能有各自的控制通道 22 与之相关的。 [0032] 移动终端 20 配置为向网络注册 10 例如,当打开移动终端时。 特别地,移动终端使用存储在相应移动终端中的SIM卡上的信息向网络注册 10 . 一旦移动终端 20 在网络上注册 10 , 移动终端 20 可以接收来自无线通信网络的服务 10 ,例如通过无线通信网络拨打和接听电话 10 作为移动终端 20 在网络服务的地理区域内移动 10 . [0033] 移动终端 20 也可能能够通过相应的控制信道发送和接收消息 22 . 在根据本发明的一些实施例中,移动终端发送/接收短消息服务(SMS)或增强型消息服务(EMS)格式的消息、多媒体消息服务(MMS)和/或Smartmessaging TM 格式的消息。 如本领域技术人员所知,SMS和EMS消息可以在诸如GSM网络的数字网络上传输,允许通过网络运营商的消息发送和接收相对较小的文本消息(例如,160个字符大小) 中心到移动端 20 ,或从 Internet,使用所谓的 SMS(或 EMS)“网关”网站。 [0034] MMS 是一种用于异步移动到移动消息传递的消息传递系统,它支持包含“富媒体”内容的消息的通信,即比文本数据更密集的类型的内容,例如图形、数码照片 、视频、动画、声音文件和/或音频。 MMS 由 WAP 论坛和第三代合作伙伴项目 (3GPP) 标准化,并在以下内容中进行了描述:“WAP MMS,体系结构概述”,WAP-205,WAP 论坛(2001 年 4 月 25 日批准的版本); “WAP MMS,客户端交易规范”,WAP-206,WAP 论坛(2002 年 1 月 15 日批准的版本); “WAP MMS,封装规范”,WAP-209,WAP 论坛(2002 年 1 月 5 日批准版本); “要求”,3GPP 规范 22.140; 和“架构和功能”,3GPP 规范 23.140。 [0035] WAP 已被颁布,通过为无线信息和电话服务的呈现和传递提供标准,使编写的应用程序能够在广泛的无线通信网络上运行。 结果,各种移动终端,例如移动终端、寻呼机、双向无线电、智能手机和通信器,可以利用WAP来实现向移动终端传递相关信息和服务。 [0036] 因此,将理解,如本文进一步描述的,控制信道 22 可用于向移动终端传输移动终端密度信息 20 通过 WAP 客户端作为 SMS、MMS、EMS 或其他类型的消息。 在根据本发明的一些实施例中,可以将移动终端密度信息提供给移动终端 20通过“Midlet”。 正如本领域技术人员所熟知的,Midlet 是一种Java 应用程序,被设计为在支持Java 的设备上运行,例如手机和PDA。 Midlet 基于 Java 2 平台微型版,使用连接的有限设备配置 (CLDC),CLDC 定义了一组应用程序编程接口和用于资源受限设备的虚拟机,例如这里讨论的那些。 在 Internet 上的“www.sun.com”上进一步讨论了 Midlet。 将进一步理解,诸如地图和其他动态图形数据的其他信息也可以在合适的消息中传输,包括任何或所有上述消息类型。 [0037] 图2是说明移动终端的框图 20 根据本发明的一些实施例。 根据本发明的一些实施例,基于移动终端上报的参数将移动终端密度信息发送到移动终端进行显示。 移动终端密度信息可以是例如估计在特定时间位于地理区域内的移动终端的数量的统计表示。 [0038] 如图2所示,移动终端 20 包括收发器电路 242 用于向网络发送和接收射频通信信号 10 通过天线系统 246 . 天线系统 246 可以包括天线馈电结构和一个或多个天线。 如本领域技术人员所熟知的,收发器的发射器部分 242 转换移动终端要传输的信息 20 成适合无线电通信的电磁信号。 收发器的接收器部分 242 解调移动终端接收到的电磁信号 20 从网络 10 以用户可以理解的格式提供信号中包含的信息。 [0039] 用户界面 244 移动终端的 20 可能包括各种组件,例如显示器 254 , 键盘 252 , 扬声器 256 , 和一个麦克风 250 ,其操作是本领域技术人员已知的。 可以理解小键盘的功能 252 和显示器 254 可以通过触摸屏提供。 显示器可用于提供用户可以查看的图像或图形,例如具有网格的地图,该网格包括叠加在其上的收集的参数,其中该地图表示在特定上下文中用户感兴趣的地理区域,例如旅行到 /来自工作、购物、娱乐等。 [0040] 处理器电路 251 提供移动终端的整体操作 20 包括通过收发器电路协调通信 242 , 用户界面 244 ,以及移动终端中包含的其他组件和系统 20 . 例如处理器电路 251 可以向收发器提供通信信号 242 当用户对着麦克风说话时 250 并接收来自收发器的通信信号 242 用于通过扬声器再现音频 256 . 处理器电路 251 可以生成字符在显示器上显示 254 . 例如处理器电路 251 当用户在键盘上输入电话号码时,可以生成用于显示的数字 252 . 字符也可以由未示出的字符生成器电路生成。 [0041] 处理器电路 251 可以使用各种硬件和软件来实现。 例如,处理器电路的操作 251 可以使用专用硬件(例如专用集成电路(ASIC)和可编程逻辑设备(例如门阵列)和/或在计算设备(例如微处理器、微控制器或数字信号处理器)上运行的软件或固件)来实现。 数字信号处理器)。 [0042] 移动终端 20 包括一张 SIM 卡 225 . SIM 卡 225 可从移动终端安装(或移除)20 通过插入(或取出)SIM 卡 225 进/出 SIM 卡座。 SIM 卡 225 存储信息,例如识别网络订户的国际移动订户身份 (IMSI) 10 和一个用于身份验证的密钥。 在根据本发明的一些实施例中,IMSI包括标识国家的3位移动国家代码(MCC)和标识该国家内的网络的2位移动网络代码(MNC)。 可以理解为SIM卡 225 可以存储数据,例如表示可以使用移动终端并且可以在其上显示的地理区域的地图。 SIM 卡 225 还可以存储可用于处理参数数据的可选上下文 [0043] SIM 卡 225 还可以存储可选择的上下文信息,该上下文信息可以应用于提供给移动终端的移动终端密度信息 20 . 例如,SIM 卡 225 可以存储可选上下文,例如购物上下文、娱乐上下文、旅行上下文等。还可以理解,SIM卡存储的可选上下文 225 可以进一步细分为子上下文。 例如,本文参考图4讨论的旅行环境可以进一步细分为通勤上班环境和下班通勤环境。 以这种方式,上下文可以在层次/逻辑上彼此相关,从而可以更容易地定位和应用每个可选择的上下文。 [0044] 在根据本发明的一些实施例中,可选择的上下文信息可以存储在其他类型的内部或外部非易失性存储器中,例如多媒体卡(MMC)、安全数字(SD)卡、紧凑型闪存(CF) 卡、记忆棒和/或基于通用串行总线的非易失性存储设备。 [0045] 应当理解,可选择的上下文可以指示要显示哪个移动终端密度信息以及可以抑制哪个移动终端密度信息,例如,为用户简化移动终端密度信息的显示。 处理器电路 251 可以将移动终端密度信息应用​​到可选择的上下文中,以提供地理显示(在显示器上 254 ) 与可选择的上下文相关联。 [0046] 一段记忆 253 可以存储计算机程序指令,当由处理器电路执行时 251 ,执行此处描述和图中所示的操作。 记忆 253 可以是非易失性存储器,例如 EEPROM(或闪存),在断电时保留存储的数据 253 启用信息存储,例如上述 WAP 配置文件,为移动终端提供对网络的访问 20 . [0047] 移动终端 20 可能还包括一个相机 226 用于生成与相机采样的图像对应的图像数据 226 . 例如,相机 226 如本文所讨论的,可用于捕获可作为参数报告的图像和/或视频,使得移动终端密度信息可基于图像的内容。 [0048] 移动终端 20 图2所示还包括一个地理位置电路 260 其被配置为使用例如本领域技术人员已知的常规GPS方法(辅助或其他)来确定移动终端的地理位置。 可以进一步理解,地理位置电路 260 可以使用其他技术确定提供给定位服务器的移动终端地理位置信息 135 . 如本文所述,由地理位置电路确定的移动终端地理位置信息 260 可以作为移动终端密度信息可以基于的参数来传输。 [0049] 移动终端 20 还包括一个本地无线接口电路 265可以提供与本地无线网络和与其相关联的设备的通信。 在根据本发明的一些实施例中,本地无线接口电路 265 是蓝牙兼容接口。 在根据本发明的一些实施例中,本地无线接口电路 265 是 WLAN 兼容接口。 [0050] 移动终端 20 可上报手机端采集的参数 20 到网络 10 例如,通过基站 30 . 移动端可采集的部分参数 20 包括移动终端的地理位置、移动终端的速度 20 , 移动端采样的音频电平 20 、图像/视频数据、设备类型标签和/或与该地区其他移动终端的连接。 例如,麦克风 250 可用于对本地环境中的环境音频电平进行采样,以提供音频电平参数。 音频电平参数可用于确定(至少部分)移动终端附近的环境参数 20 . 高音频电平可以指示例如交通拥堵、施工和其他情况,这些情况可以指示比其他方式明显的更高或更低的密度。 如果移动端 20 如果对异常高水平的音频进行采样,则可以确定拥塞的可能性增加,即使以其他方式检测到相对较少的移动终端也是如此。 在根据本发明的一些实施例中,扬声器 256 可用于对本地环境中的环境音频电平进行采样,以提供音频电平参数。 [0051] 设备类型标签参数可以指示报告参数的设备类型。 设备类型标签可以包括例如汽车(即,设备被集成到汽车中的地方)、个人数字助理、膝上型电脑、手机等。 在根据本发明的一些实施例中,设备类型标签参数可以随着设备的使用或配置的改变而改变。 例如,当手机连接到汽车中的辅助电源插座时,手机设备类型标签可以从“手机”改变(或进一步定义)为“手机/汽车”。 [0052] 连接参数可以指示该区域中可能没有适当地配备有地理位置电路或者可能不参与同一通信网络的其他移动终端的存在。 因此,在确定移动终端密度信息时可以考虑这些否则未被检测到的移动终端的存在。 连接参数可以由移动终端采集 20 使用本地无线接口电路 265 例如,可以检测移动终端的存在 270 在本地无线接口电路范围内 265 . 应当理解,可以使用上述设备类型标签参数进一步定义连接参数。 例如,该区域中与该移动终端通信的其他移动终端中的每一个 20 上报参数可以有关联的设备类型标签参数,以便在上报连通性参数时,系统可以进一步定义移动终端本地的终端类型 20 (可用于提供更准确的密度信息)。 [0053] 在根据本发明的一些实施例中,连接参数还可以指定移动终端的地理位置 20 从其他设备检索,例如移动终端 270 ,例如,如果移动终端 20 本身没有配备地理位置电路或暂时无法使用地理位置电路确定自己的位置。 [0054] 图3A是图示根据本发明的一些实施例的可用于确定移动终端密度信息的参数的集合的示意图。 尤其是移动终端 20可以基于被带入以上参考图2讨论的本地无线接口范围内的多个其他移动终端来收集连接信息。此外,移动终端 20 可以对环境音频电平进行采样以提供也可以用于确定移动终端密度信息的音频电平参数。 [0055] 可以理解为移动端采集的参数 20 可以基于收集的参数的类型或基于收集哪些其他类型的参数和/或当前有多少移动终端在特定地理区域内提供参数来加权。 例如,音频电平参数的权重可能小于移动终端上报的位置信息 20 而连通性参数的权重可以大于音频电平参数,但小于移动终端上报的位置信息。 [0056] 图3B是描绘在由网络服务的地理区域中操作的移动终端的示意图 10 . 根据图 3B,移动终端 20 显示在地理区域内的不同位置,包括位于道路、购物区、娱乐区和其他区域上或处。 移动终端数量 20 ,以及它们的间距,描绘了特定区域中移动终端的密度。 例如,第一个区域 310 移动终端相对密集 20 而第二个区域 312 移动终端人口较少 20 . 第三个区域 313 包括一个由移动终端组成的娱乐/购物区 20 ,它的移动速度可能比第一个和第二个区域中显示的要慢 312 和 313 (甚至可能是静止的)。 [0057] 根据本发明的一些实施例,移动终端 20 向移动终端密度信息服务器(以下简称“服务器”)上报参数 305 . 可以理解的是,移动终端的参数上报 20 可以以 ad-hoc 方式完成,其中不需要来自服务器的请求 305 用于个人移动终端 20 报告参数。 将进一步理解,报告可以以其他方式完成,例如,使用同步类型的方法,其中移动终端 20 在预先指定的时间或响应来自服务器的特定请求进行报告 305 . 可以进一步理解,服务器 305 可以直接连接到网络 10 或者,它可以间接耦合到网络 10 通过单独的网络,例如 Internet。 在这样的实施例中,服务器 305 间接耦合到网络 10 ,移动终端可以通过其他网络上报参数,例如WLAN、蓝牙网络等。 [0058] 服务器 305 从移动终端接收参数 20 并编译参数以提供移动终端密度信息。 如上所述,移动终端密度信息可以基于移动终端报告的各种参数,例如地理位置、连接性、速度、图像数据、音频电平和其他参数。 此外,在确定移动终端密度信息时可以对参数进行不同的加权,以便为用户提供密度信息的整体更准确的指示。 例如,如上所述,连接信息可以与移动终端报告的地理信息结合使用 20 增加对特定地理位置的人数的估计,例如,即使设备连接到移动终端 20 可能无法与网络通信 10 或者可能没有配备如上所述的地理位置电路。 [0059]移动终端密度信息可以是例如估计在特定时间位于地理区域内的移动终端的数量的统计表示。 统计表示可以是本领域技术人员已知的任何类型,例如移动平均。 [0060] 进一步理解,服务器编译的参数 305 提供移动终端密度信息可能会被视为“上下文无关”,以便根据情况对信息进行不同的解释,从而保证服务器的数据完整性 305 可以保留。 此外,上下文可以作为解释的一部分由例如移动终端处的用户应用于信息。 因此,无需对服务器功能进行重大更改即可收集和报告新类型的参数 305 . 将进一步理解,在根据本发明的一些实施例中,可以基于一天中的时间应用可选择的上下文,例如在早上通勤期间或下午通勤期间,其中可以在不同时间应用不同上下文。 [0061] 服务器 305 向移动终端发送移动终端密度信息 20 (通过移动交换中心 15 )其中可选择的上下文可以应用于其上显示的移动终端密度信息。 可以理解的是,向移动终端发送的移动终端密度信息 20 只能包含移动终端的密度值。 在根据本发明的又一实施例中,向移动终端发送移动终端密度信息 20 可以包括移动终端密度值和移动终端密度值应用到的网格位置。 相应地,移动终端密度信息和网格位置可以叠加在移动终端显示的地图上 20 例如,传达与拥塞相关的信息,这些信息可能对用户在特定时间选择目的地或到特定目的地的更好路线有用。 [0062] 如上所述,移动终端密度信息可以通过移动终端在其上的控制信道发送。 20 正在露营。 或者,在根据本发明的一些实施例中,移动终端密度信息和网格位置可以使用诸如SMS或MMS格式的消息之类的消息来传输,如果移动终端如此配备的话。 或者,该信息可以通过GPRS或其他通用数据信道传输。 [0063] 在根据本发明的一些实施例中,从服务器发送到移动终端的移动终端密度信息 20 可以包括基于与特定网格位置相关联的移动终端密度信息的颜色和不透明度值。 例如,特定网格位置的颜色值可以指示位于对应于网格位置的地理区域中的移动终端的平均速度。 不透明度值可以表示位于对应于各个网格位置的地理区域中的移动终端的密度。 [0064] 可以组合颜色和不透明度值以将网格位置渲染到移动终端的显示上 20 传达有关该网格位置内的交通流量以及交通密度的信息。 例如,在根据本发明的一些实施例中,红色值可以指示该网格位置中的相对低的速度并且相对不透明的不透明度值可以指示相对高的交通密度。 相反,绿色值可以指示该网格位置中的相对较高的速度,而相对低的不透明度值可以指示相对较轻的交通。 在根据本发明的一些实施例中,可以限制不透明度值,使得最大不透明度值允许移动终端的显示器上的基础地图 20 即使不透明度相对较高,也可以通过网格位置查看。 [0065]图4是根据本发明一些实施例的移动终端密度信息的显示示意图。 具体地,在移动终端上显示图4所示的移动终端密度信息 20 由处理器电路 251 通过应用可选择的上下文,使得一些移动终端密度信息被抑制,而其他移动终端密度信息不被抑制,因此显示在移动终端上 20 . 在根据本发明的一些实施例中,图4中应用的可选择上下文可以是旅行上下文的子上下文,例如“通勤上班上下文”。 在“上班通勤”子上下文中,已知用户遵循从住宅到办公室的特定路线。 [0066] 因此,可以抑制与预定路线之外的网格位置相对应的移动终端密度信息。 例如,如图4所示,区域上网格位置对应的移动终端密度信息 313 可以抑制图3B中的。 同样,一个区域 415 对应于用户通常不从住宅到办公室行驶的高速公路也被抑制。 将进一步理解,可选择的上下文可以基于诸如周一至周五早上的工作日时间自动选择并应用于移动终端密度信息。 或者,该可选上下文可以由用户手动选择。 在根据本发明的更进一步的实施例中,可选择的上下文可以基于移动终端的地理位置自动选择 20 当用户在网络服务的区域中移动时 10 . [0067] 图5是示出根据本发明的一些实施例的可选上下文应用于移动终端密度信息的示意图。 特别地,与图4中应用的上下文相反,图5中应用的可选择上下文可以被称为“通勤回家”上下文。 在“通勤回家”上下文中,可以抑制与用户通常不经过的道路上的网格位置相对应的部分移动终端密度信息。 将进一步理解,与报告移动终端相关联的设备类型标签可以在“通勤回家”上下文中使用以确定是否应该显示或抑制密度信息。 例如,与报告移动终端相关联的“汽车”设备类型标签可能与该上下文中的显示器相关,而与“手机”设备类型标签相关联的密度信息被抑制。 [0068] 图6A是图示根据本发明的一些实施例的将可选上下文应用于移动终端密度信息的示意图。 特别地,图6A图示了可被称为“娱乐/购物”上下文的可选上下文的应用。 特别地,如图6A所示,通常与如图4和5所示的“通勤”上下文相关联的移动终端密度信息可以被抑制,而与已知与娱乐和购物相关的其他地理区域相关联的移动终端密度信息 可在移动端显示 20 . [0069] 图6B是图6A中A部分的放大图,其中移动终端上显示已知与娱乐相关的地理区域的移动终端密度信息 20 而已知与购物相关的移动终端密度信息被抑制。 相反,图6C是图6A中的部分A的放大图,其中应用了购物上下文,从而显示与购物相关联的移动终端信息并抑制与娱乐相关联的移动终端信息。 [0070]在根据本发明的又一实施例中,可以将这里称为“拥挤”的上下文应用于密度信息,从而可以抑制与与人群无关的移动终端相关的密度信息,而可以显示与人群或拥挤相关的密度信息 . 例如,在根据本发明的一些实施例中,用户可能希望找到比其他地方更受欢迎的当地海滩或娱乐区。 用户由此可以应用拥挤上下文以在移动终端上生成反映与不同地理位置相关联的拥挤程度的移动终端密度信息的显示。 还应理解,设备类型标签参数可用于基于由设备类型标签标识的设备类型来确定是否应抑制或显示与报告移动终端相关联的移动密度信息。 例如,“手机”设备类型标签可能与拥挤环境中移动终端密度信息的显示相关,而“汽车”设备类型标签可能不相关。 因此,可以抑制与汽车设备类型标签相关联的任何移动终端密度信息,而可以显示与蜂窝电话设备类型标签相关联的移动终端密度信息。 在根据本发明的进一步实施例中,设备类型标签可以应用在“停车”上下文中,其中例如与汽车相关联的设备类型标签被显示,而具有其他类型标签的移动终端报告的移动终端密度信息可以是 压制。 因此,用户可以更有效地定位停车可能更可用的区域,或者可替代地,可以避开停车不太可能可用的区域。 [0071] 根据图7,移动终端参数由移动终端报告并在服务器使用例如ad-hoc报告机制(块 705 )。 如上所述,参数可以包括地理位置信息、速度信息、连接信息、音频电平信息、设备类型标签等。服务器编译参数以提供移动终端密度信息(块 710 )。 移动终端密度信息可以通过对某些参数的权重大于或小于其他参数来编制。 例如,连接性参数信息可以指示报告移动终端附近的其他移动终端,因此可以指示增加的密度,否则这可能不明显,因为那些其他移动终端可能不在无线通信网络内操作。 [0072] 在根据本发明的一些实施例中,移动终端报告的速度信息可用于间接确定移动终端密度信息的指示。 例如,速度可以被认为与密度成反比,使得与地理位置相关联的相对高的速度值可以指示报告移动终端的相对低的密度信息。 另一方面,与地理位置相关联的相对低的速度值可以指示报告移动终端的相对高密度的信息。 [0073] 这些参数将被收集并与对应于最终将在移动终端的显示器上呈现(作为密度信息)的网格位置(i,j)的地理位置相关联。 将理解,与编译参数相关联的网格位置(i,j)对应于网络内的地理区域,该地理区域大到足以覆盖足以表示来自移动终端的足够数量的报告的区域。 将进一步理解,对应于网格位置(i,j)的地理区域也应该足够小以提供关于最终显示的移动终端密度信息的相对精细的细节。 将理解,网格位置(i,j)可以是统一的或基于例如从每个网格位置(i,j)报告多少参数而改变大小。 [0074]在根据本发明的一些实施例中,由移动终端报告的地理位置信息和速度参数与要显示的特定网格位置相关联。 例如,可以使用以下等式将特定网格位置的速度参数编译为随时间推移的移动平均值: 速度 i,j ←c·速度+(1−c)·速度 i,j n i,j ←n i,j +1 [0075] 其中 c=1/m,m 是移动平均值中包含的速度值的数量。 为了避免在特定网格位置处的速度值随时间饱和,读数计数可随时间降低,例如通过将值减小一定百分比的规则时间间隔。 尽管参考速度信息的编译描述了以上引用的方程,但是应当理解,相同或类似类型的处理可以用于编译移动终端报告的其他参数。 还应理解,如果移动终端配备有地理位置电路,例如GPS,还可以包括高度信息参数,从而可以为移动终端的二维显示呈现三维表示。 终端,其中呈现的第三维度可以表示作为高度函数的密度信息。 [0076] 将移动终端密度信息传送到移动终端(块 715 )。 如本文所讨论的,移动终端密度信息可以包括其密度的统计表示(例如移动平均值)并且还可以包括不透明度值,该不透明度值可以用于呈现网格上的位置,该网格覆盖在显示器上显示的地图上 的移动终端。 密度信息可以以可缩放矢量图形 (SVG) 格式传输。 正如本领域技术人员所熟知的,SVG是一种用于以XML描述二维图形和图形应用的语言。 SVG 1.1 是当前的 W3C 建议,构成当前 SVG 开发的核​​心,旨在用于资源有限的设备,例如 3GPP 平台第三代手机。 可选择的上下文应用于移动终端的密度信息,并以网格的形式叠加在地图上,以便在移动端显示(块 720 )。 [0077] 在不脱离本发明的精神和范围的情况下,本领域的普通技术人员在受益于本公开的情况下可以做出许多改变和修改。 因此,必须理解,所示实施例仅出于示例的目的而阐述,并且不应被视为限制由所附权利要求限定的本发明。 因此,所附权利要求应理解为不仅包括按字面阐述的元件的组合,而且包括用于以基本相同的方式执行基本相同的功能以获得基本相同的结果的所有等效元件。 因此,权利要求应理解为包括以上具体说明和描述的内容、概念上等同的内容以及包含本发明的基本思想的内容。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101099404A(String), CN101099404B(String), EP1815708A1(String), EP1815708B1(String), US20060105815A1(String), US7522940B2(String), WO2006053694A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.618 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101099404A(String), CN101099404B(String), EP1815708A1(String), EP1815708B1(String), US20060105815A1(String), US7522940B2(String), WO2006053694A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7522940B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101099404A(String), CN101099404B(String), EP1815708A1(String), EP1815708B1(String), US20060105815A1(String), US7522940B2(String), WO2006053694A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), CN101099404A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.784 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), CN101099404B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), EP1815708A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.878 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), EP1815708B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), US20060105815A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.948 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), US7522940B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:57.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271673(Integer), WO2006053694A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7522940B2(String), US7522940B2(String), 1240243200(Integer), 271673(Integer), 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.108 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.167 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186001(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.224 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 186001(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1660818391(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.297 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186001(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.331 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 23104(Integer), 2(Integer), 186001(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.367 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.384 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.401 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.420 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.473 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费 | 权利转移(String), 2(Integer), 186001(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:58.679 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9549143B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US9549143B2(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择显示在外部显示设备上的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US13/950507(String), 1374681600(Integer), US9549143B2(String), 1484582400(Integer), 1484582400(Integer), 美国(String), 4(Integer), KR(String), 9(Integer), 16(Integer), EP1853061A1 | KR1020110016571A | KR1020110070589A | KR1020110088952A | TW201219871A | TW201224993A | US20020162120A1 | US20030076344A1 | US20110154396A1 | US20120017237A1 | US20120133645A1 | US20120137329A1 | US20130177891A1 | US8112371B1 | WO2011008387A2 | WO2011084950A2(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.058 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186002(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2bd224a89f76436bb416af369f84a3a8.png(String), 186002(Integer), 2bd224a89f76436bb416af369f84a3a8.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US9549143B2(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择显示在外部显示设备上的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US13/950507(String), 1374681600(Integer), US9549143B2(String), 1484582400(Integer), 1484582400(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 9(Integer), 16(Integer), EP1853061A1 | KR1020110016571A | KR1020110070589A | KR1020110088952A | TW201219871A | TW201224993A | US20020162120A1 | US20030076344A1 | US20110154396A1 | US20120017237A1 | US20120133645A1 | US20120137329A1 | US20130177891A1 | US8112371B1 | WO2011008387A2 | WO2011084950A2(String), \20230420\2bd224a89f76436bb416af369f84a3a8.png(String), 20(Integer), 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 1. A mobile device comprising:a memory storing instructions; anda processor configured to execute the stored instructions to control the mobile device to perform:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects displayed on the external display device based on a first input of a user through the mobile device;requesting, to the external display device, additional information corresponding to the object based on a second input of the user through the mobile device;receiving, from the external display device, the additional information corresponding to the object;displaying a plurality pieces of information related to the object based on the additional information received from the external display device, the additional information including the plurality pieces of information related to the object;requesting a content corresponding to a piece of information from among the plurality pieces of information related to the object; andreceiving the content corresponding to the piece of information.(String), 1.移动设备包括:存储器存储指令;和处理器被配置为执行存储的指令以控制移动设备执行:基于用户通过移动设备的第一输入,向外部显示设备发送用于从显示在外部显示设备上的多个对象中选择对象的信号;基于用户通过移动设备的第二输入向外部显示设备请求对应于对象的附加信息;从外部显示设备接收对象对应的附加信息;基于从外部显示设备接收的附加信息显示与对象相关的多条信息,附加信息包括与对象相关的多条信息;请求与对象相关的多条信息中的一条信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 2. The mobile device of claim 1, wherein the processor is further configured to convert the signal for selecting the object according to a control protocol of the external display device.(String), 2.如权利要求1所述的移动设备,其中处理器还用于根据外部显示设备的控制协议转换用于选择对象的信号。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 3. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to transmit a signal for controlling a movement of a selection region for selecting the object displayed on the external display device.(String), 3.如权利要求1所述的移动设备,其中处理器还被配置为控制移动设备发送用于控制选择区域的移动的信号,该选择区域用于选择显示在外部显示设备上的对象。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 4. The mobile device of claim 3, wherein the processor is further configured to control the mobile device to transmit a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input.(String), 4.如权利要求3所述的移动设备,其中处理器还被配置为控制移动设备发送用于控制选择区域的移动方向、选择区域的移动速度和在外部显示器的屏幕上显示的对象的数量中的至少一项的信号基于第一个输入的设备。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 5. The mobile device of claim 3, wherein the processor is further configured to control the mobile device to display thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 5.如权利要求3所述的移动设备,其中处理器还被配置为在请求附加信息之前控制移动设备显示与其中设置有选择区域的对象对应的缩略图信息。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 6. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to receive link information of the additional information from the external display device based on the second input andreceive the content from a server based on the received link information.(String), 6.如权利要求1所述的移动设备,其中处理器还被配置为基于第二输入控制移动设备从外部显示设备接收附加信息的链接信息,并且基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 7. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to request the content based on a third input of the user through the mobile device.(String), 7.如权利要求1所述的移动设备,其中处理器还被配置为基于用户通过移动设备的第三输入来控制移动设备请求内容。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 8. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to request control authorization from the external display device and receive a control authorization acceptance message from the external display device prior to the transmitting of the signal for selecting the object.(String), 8.如权利要求1所述的移动设备,其中处理器进一步被配置为在发送用于选择对象的信号之前控制移动设备向外部显示设备请求控制授权并且从外部显示设备接收控制授权接受消息。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 9. The mobile device of claim 1, wherein the plurality of objects comprise at least one from among an icon, a link, a picture, a text, and an index item.(String), 9.如权利要求1所述的移动设备,其中多个对象包括图标、链接、图片、文本和索引项中的至少一个。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 10. The mobile device of claim 1, wherein the content comprise at least one from among a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG).(String), 10.如权利要求1所述的移动设备,其中内容包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 11. The mobile device of claim 1, wherein the additional information comprises at least one from among preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information.(String), 11.如权利要求1所述的移动设备,其中附加信息包括预览信息、试听信息、应用信息、用户评论信息、更新信息、报刊文章信息、商品信息、电影信息、游戏信息、广告图片信息、专辑信息中的至少一种。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 12. The mobile device of claim 1, wherein the processor is further configured to control the mobile device todetermine an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generate a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generate a signal for controlling the content displayed on the mobile device based on the user input.(String), 12.如权利要求1所述的移动设备,其中处理器还被配置为控制移动设备以确定移动设备的操作模式;和响应于确定操作模式是第一模式,基于用户输入产生用于控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,产生用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 13. A method in which a mobile device displays information, the method comprising:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects displayed on the external display device based on a first input of a user through the mobile device;requesting, to the external display device, additional information corresponding to the object based on a second input of the user through the mobile device;receiving, from the external display device, the additional information corresponding to the object;displaying a plurality pieces of information related to the object based on the additional information received from the external display device, the additional information including the plurality pieces of information related to the object;requesting a content corresponding to a piece of information from among the plurality pieces of information related to the object; andreceiving the content corresponding to the piece of information.(String), 13.一种方法其中移动设备显示信息,该方法包括:基于用户通过移动设备的第一输入,向外部显示设备发送用于从显示在外部显示设备上的多个对象中选择对象的信号;基于用户通过移动设备的第二输入向外部显示设备请求对应于对象的附加信息;从外部显示设备接收对象对应的附加信息;基于从外部显示设备接收的附加信息显示与对象相关的多条信息,附加信息包括与对象相关的多条信息;请求与对象相关的多条信息中的一条信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 14. The method of claim 13, wherein the transmitting the signal for selecting the object comprises transmitting a signal for controlling a movement of a selection region for selecting the object displayed on the external display device.(String), 14.如权利要求13所述的方法,其中发送用于选择对象的信号包括发送用于控制用于选择显示在外部显示设备上的对象的选择区域的移动的信号。(String), 1(Integer), 13(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 15. The method of claim 14, wherein the transmitting the signal for controlling the movement of the selection region comprises transmitting a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input.(String), 15.如权利要求14所述的方法,其中发送用于控制选择区域的移动的信号包括发送用于控制选择区域的移动方向、选择区域的移动速度和显示在选择区域的屏幕上的对象的数量中的至少一项的信号基于第一输入的外部显示设备。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 16. The method of claim 14, further comprising displaying thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 16.如权利要求14所述的方法,还包括在请求附加信息之前,显示选择区域所在的对象对应的缩略图信息。(String), 1(Integer), 15(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 17. The method of claim 13, wherein the receiving the additional information comprises receiving link information of the additional information from the external display device based on the second input and,wherein the receiving the content comprises receiving the content from a server based on the received link information.(String), 17.如权利要求13所述的方法,其中接收附加信息包括基于第二输入从外部显示设备接收附加信息的链接信息,以及,其中,接收内容包括基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 16(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 18. The method of claim 13, wherein the content comprise at least one from among a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG).(String), 18.如权利要求13所述的方法,其中内容包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。(String), 1(Integer), 17(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 19. The method of claim 13, further comprising:determining an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generating a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generating a signal for controlling the content displayed on the mobile device based on the user input.(String), 19.如权利要求13所述的方法,还包括:确定移动设备的操作模式;和响应于确定操作模式是第一模式,生成用于基于用户输入控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,生成用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 18(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186002(Integer), 20. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method of claim 13.(String), 20.一种非暂时性计算机可读记录介质有在其上记录用于执行权利要求13的方法的程序。(String), 1(Integer), 19(Integer), 12(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.727 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186002(Integer), CROSS-REFERENCE TO RELATED PATENT APPLICATION [0001]This application claims priority from Korean Patent Application No. 10-2012-0081434, filed on Jul. 25, 2012, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference. BACKGROUND [0002]1. Field [0003]Exemplary embodiments relate to a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object, a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal, and a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0004]2. Description of the Related Art [0005]A smart television (TV) is a multifunctional TV capable of utilizing various functions such as web surfing, video on demand (VOD) watching, a social networking service (SNS), a game, etc. by combining a TV and an Internet access function and installing various applications. [0006]One characteristic of the smart TV is that a user and the TV can transmit and receive information from each other. This is a difference between the smart TV and an existing TV that merely transfers information unilaterally. Thus, the smart TV is also referred to as an interactive TV. [0007]However, it is very inconvenient for the user to use the various functions of the smart TV by using a standard remote controller. In particular, when the user browses or downloads contents, the user needs to manipulate the remote controller through several steps. [0008]Therefore, a control device or system for allowing the user to easily control the smart TV is needed. SUMMARY [0009]Exemplary embodiments provide a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object. [0010]Exemplary embodiments also provide a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal. [0011]Exemplary embodiments also provide a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0012]According to an aspect of an exemplary embodiment, there is provided a method in which a mobile terminal displays information, the method including: transmitting a first signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; transmitting a second signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0013]The transmitting of the first signal for selecting the object may include: converting the signal for selecting the object according to a control protocol of the external display device. [0014]The transmitting of the first signal for selecting the object may include: transmitting a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0015]The transmitting of the signal for controlling the movement of the selection region may include: transmitting a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen of the external display device based on the first input. [0016]The transmitting of the first signal for selecting the object may include: displaying thumbnail information of contents corresponding to the object on the screen of the mobile terminal. [0017]The thumbnail information may include at least one of an image of the contents corresponding to the object, a title of the contents, and a type of the contents. [0018]The transmitting of the first signal for selecting the object may include: displaying a movement direction of the mobile terminal on the screen according to the first input. [0019]The first input and the second input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0020]The first input may include a three-dimensional (3D) motion input for moving the mobile terminal in a 3D direction, wherein the second input includes a rotational motion input for rotating the mobile terminal by more than a predetermined angle. [0021]The transmitting of the second signal for requesting additional information may include: receiving the additional information from the display device. [0022]The transmitting of the second signal for requesting additional information may include: receiving link information of the additional information from the external display device based on the second input; and receiving the additional information from a server based on the received link information. [0023]The transmitting of the first signal for selecting the object to the display device may include: requesting control authorization from the external display device; and receiving a control authorization acceptance message from the external display device. [0024]The contents may include at least one of a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG). [0025]The additional information may include at least one of preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information. [0026]The method may further include: controlling the additional information displayed on the screen of the mobile terminal based on a third input of the user through the mobile terminal. [0027]The controlling of the additional information may include: controlling at least one of displaying of the additional information, playing of the additional information, and changing to previous additional information or next additional information based on the third input of the user through the mobile terminal. [0028]The method may further include: obtaining contents corresponding to the additional information displayed on the screen of the mobile terminal. [0029]According to an aspect of another exemplary embodiment, there is provided a method in which a display device provides information to a mobile terminal, the method including: selecting an object displayed on the display device by receiving a first input of a user through the mobile terminal; and transmitting additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal. [0030]The transmitting may include: extracting the additional information from contents corresponding to the selected object. [0031]The selecting of the object may include: receiving a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal; and moving the selection region according to the control signal. [0032]The selecting of the object may include: converting the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0033]The receiving may include: receiving the control signal for controlling the movement of the selection region from each of a plurality of mobile terminals. [0034]The method may further include: sensing at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0035]The selecting of the object may include: controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0036]The selecting of the object may include: transmitting thumbnail information of contents corresponding to the object to the mobile terminal. [0037]The transmitting of the additional information to the mobile terminal may include: transmitting link information of the additional information to the mobile terminal. [0038]The terminal may further include: receiving a request for transmission of contents corresponding to the selected object from the mobile terminal; and transmitting the contents corresponding to the selected object to the mobile terminal. [0039]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a communication unit which is configured to transmit a signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; an additional information obtaining unit which is configured to transmit a signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; a display which is configured to display the additional information received from the external display device; and a controller which is configured to control the communication unit, the additional information obtaining unit, and the display unit. [0040]The controller may convert the signal for selecting the object according to a control protocol of the external display device. [0041]The communication unit may transmit a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0042]The communication unit may transmit a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input. [0043]The display may display thumbnail information of contents corresponding to the object on a screen of the mobile terminal. [0044]The additional information obtaining unit may receive the additional information from the external display device. [0045]The communication unit may receive link information of the additional information from the external display device based on the second input, and wherein the additional information obtaining unit receives the additional information from a server based on the received link information. [0046]The controller may control the additional information displayed on the mobile terminal based on a third input of the user through the mobile terminal. [0047]The mobile terminal may further include: a contents obtaining unit which is configured to obtain content corresponding to the additional information displayed on the mobile terminal. [0048]According to an aspect of an exemplary embodiment, there is provided a display device including: a selection unit which is configured to select an object displayed on the display device based on a first input of a user through a mobile terminal; a communication unit which is configured to transmit additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal, and a controller which is configured to control the selection unit and the communication unit. [0049]The controller may extract the additional information from contents corresponding to the selected object. [0050]The selection unit may receive a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal and move the selection region according to the received control signal. [0051]The controller may convert the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0052]The display device may further include: a sensor which is configured to sense at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0053]The controller may control at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0054]The communication unit may transmit link information of the additional information to the mobile terminal. [0055]The communication unit may receive a request for transmission of contents corresponding to the selected object from the mobile terminal and transmit the contents corresponding to the selected object to the mobile terminal. [0056]According to an aspect of another exemplary embodiment, there is provided a method in which a mobile terminal generates a control signal, the method including: receiving a user input; determining an operation mode of the mobile terminal; and in response to determining the operation mode is a first mode, generating a first control signal for controlling an external display device based on the user input, and, in response to determining the operation mode is a second mode, generating a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0057]The contents may include contents corresponding to an object selected from the external display device or additional information corresponding to the object based on the first control signal. [0058]The user input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0059]The determining may include: determining the operation mode of the mobile terminal as the first mode in a case where the mobile terminal is in a vertical mode, and, determining the operation mode of the mobile terminal as the second mode in a case where the mobile terminal is in a horizontal mode. [0060]The determining may include: determining the operation mode of the mobile terminal based on information displayed on a screen of the mobile terminal. [0061]The determining may include: in response to determining the information displayed on the screen of the mobile terminal is thumbnail information of contents corresponding to the object displayed on the external display device or movement direction information of the mobile terminal, determining the operation mode of the mobile terminal as the first mode, and, in response to determining the information displayed on the screen of the mobile terminal is the contents corresponding to the object displayed on the external display device or additional information corresponding to the object, determining the operation mode of the mobile terminal as the second mode. [0062]The generating of the first control signal may include: converting the first control signal according to a control protocol of the external display device. [0063]The first mode may be a mode in which the object of the external display device is selected, and the second mode is a mode in which additional information corresponding to the selected object is displayed on the mobile terminal. [0064]The first control signal may include a signal for controlling a movement of a selection region for selecting the object of the external display device, and the second control signal may include a signal for controlling at least one of playing of the contents, editing of the contents, and transmission of the contents. [0065]The method may further include: receiving a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle; converting the operation mode from the first mode to the second mode based on the first rotational motion input; receiving a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle; and converting the operation mode from the second mode to the first mode based on the second rotational motion input. [0066]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a user input which is configured to receive a user input; an operation mode determining unit which is configured to determine an operation mode of the mobile terminal; and a controller which is configured, in response to the operation mode determining unit determining that the operation mode is a first mode, generate a first control signal for controlling an external display device based on the user input, and, in response to the operation mode determining unit determining that the operation mode is a second mode, generate a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0067]The user input may receive a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle and a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle, and wherein the controller converts the operation mode from the first mode to the second mode based on the first rotational motion input and the operation mode from the second mode to the first mode based on the second rotational motion input. [0068]According to an aspect of another exemplary embodiment, a method of displaying information of an external display device on a mobile terminal displays is provided. The method includes: receiving a user input into the mobile terminal about an object displayed on the external display device; transmitting a first signal to the external display device to select the object displayed on an external display device; receiving a second user input into the mobile terminal about additional information corresponding to the object displayed on the external display device; transmitting a second signal to the external display device to request additional information corresponding to the selected object; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0069]The transmitting the first signal may include converting the first signal to a control protocol of the external display device. [0070]The transmitting the first signal may include requesting control authorization from the external display device and receiving a control authorization acceptance message from the external display device. BRIEF DESCRIPTION OF THE DRAWINGS [0071]The above and other features and advantages will become more apparent by describing in detail exemplary embodiments with reference to the attached drawings in which: [0072]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment; [0073]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment; [0074]FIGS. 3A through 3C are views of screens on which a mobile terminal selects an object of an external display device, according to an exemplary embodiment; [0075]FIGS. 4A and 4B are views of screens on which a mobile terminal obtains additional information, according to an exemplary embodiment; [0076]FIG. 5 is a view of a screen on which contents are obtained, according to an exemplary embodiment; [0077]FIG. 6 is a view of a screen on which an object is displayed or reproduced, according to an exemplary embodiment; [0078]FIG. 7 is a flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0079]FIG. 8 is a detailed flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0080]FIG. 9 is a flowchart illustrating a method in which a display device senses an input of a mobile terminal and provides additional information, according to an exemplary embodiment; [0081]FIG. 10 is a flowchart illustrating a method in which a mobile terminal obtains additional information through a server, according to an exemplary embodiment; [0082]FIG. 11 is a flowchart illustrating a method in which a mobile terminal obtains contents, according to an exemplary embodiment; [0083]FIG. 12 is a flowchart illustrating a method in which a mobile terminal obtains contents through a server, according to an exemplary embodiment; [0084]FIG. 13 is a view of a screen on which each of a plurality of mobile terminals selects an object of a display device, according to an exemplary embodiment; [0085]FIG. 14 is a block diagram of a mobile terminal, according to an exemplary embodiment; [0086]FIG. 15 is a block diagram of a display device, according to an exemplary embodiment; [0087]FIG. 16 is a flowchart illustrating a method in which a display device provides information, according to an exemplary embodiment; and [0088]FIG. 17 is a flowchart illustrating a method in which a mobile terminal generates a control signal, according to an exemplary embodiment. DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS [0089]First, the terms used herein will be briefly described, and then the exemplary embodiments will be described in detail. [0090]Although the terms used herein are general terms that are widely used at present in consideration of the functions of the exemplary embodiments, they may vary according to the intention of one of ordinary skill in the art, a precedent, the appearance of new technology, or the like. In addition, in a particular case, the applicant may select the terms arbitrarily. In this case, the meanings of the terms will be described in detail in the detailed description of the exemplary embodiments. Thus, the terms used in the detailed description should not be only names of the terms but should be defined based on their meanings and contents in relation to the exemplary embodiments. [0091]When a unit “comprises” an element in the entire specification, the unit does not exclude another element but may further comprise another element unless the context clearly indicates otherwise. In addition, terms such as “ . . . unit”, “module”, and the like used herein indicate a unit for performing at least one function or operation and may be implemented by hardware or software or a combination thereof. [0092]Throughout the specification, an “object” refers to a target that may be selected by a user from a display device. Examples of the object include, but are not limited to, an icon, a link, a picture, a text, an index item, etc. [0093]In addition, “additional information” refers to information regarding contents corresponding to an object, and may have various forms according to types of contents. Examples of the additional information may include, but are not limited to, preview information, prelistening information, application information, user review information, advertisement image information, update information, newspaper article information, goods information, movie information, game information, album information, etc. [0094]In the present specification, “contents” may be displayed, reproduced, or stored in a mobile terminal, and may include, for example, still image contents (for example, a photo, a picture, etc.), text contents (for example, an electronic book (a poem and a novel), a letter, a business file, a web page, an electronic program guide (EPG), etc.), moving image contents (for example, a personal image, a movie, music video, a YouTube video, a TV program image, etc.), music contents (for example, music, a music performance, a radio broadcast, etc.), an application (a widget, a game, etc.) [0095]The exemplary embodiments will now be described more fully with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the inventive concept to those of ordinary skill in the art. For clarity, in the drawings, irrelevant portions with respect to the description are omitted, and similar reference numbers are added to similar portions throughout the entire specification. [0096]As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list. [0097]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment. [0098]Referring to FIG. 1, the information providing system according to an exemplary embodiment may include a mobile terminal 100 and an external display device 200. [0099]The mobile terminal 100 is a device that obtains contents from the outside and displays, reproduces, or stores the obtained contents. The mobile terminal 100 may be implemented in various ways. For example, the mobile terminal 100 described in the present specification may include a cellular phone, a smart phone, a laptop computer, a tablet personal computer (PC), an e-book terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, etc. [0100]The display device 200 is a device that may be of various types including a display panel. For example, the display device 200 described in the present specification may include a smart television (TV), an Internet protocol TV (IPTV), a digital TV (DTV), a computer, a laptop computer, an e-book terminal, a tablet PC, a digital broadcasting terminal, a consumer electronics (CE) device (for example, a refrigerator or an air conditioner having the display panel), etc. [0101]The display device 200 according to an exemplary embodiment may display an object list. The object list may include identification information regarding at least one piece of contents. Examples of the identification information may include a title of contents, an image and icon indicating contents, etc. [0102]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment. [0103]Referring to FIG. 2, the information providing system according to another exemplary embodiment may include the mobile terminal 100, the display apparatus 200, and a server 300. [0104]The mobile terminal 100 and the display apparatus 200 are the same as described with reference to FIG. 1, and thus descriptions thereof are omitted. [0105]The server 300 may communicate with the mobile terminal 100 or the display apparatus 200. According to an exemplary embodiment, the server 300 may receive a contents providing request from the mobile terminal 100 or the display device 200. In this case, the server 300 may provide contents to the mobile terminal 100 or the display device 200. The contents provided by the server 300 may be contents corresponding to an object selected by the display device 200 or additional information corresponding to the object. [0106]For example, in a case where the display device 200 selects an object relating to movie contents, the server 300 may provide the movie contents or preview video of the movie contents to the mobile terminal 100 or the display device 200. [0107]An example in which the mobile terminal 100 selects an object displayed on an external display device based on a user input and obtains and displays additional information corresponding to the selected object will now be described in brief with reference to FIGS. 3 through 6. [0108]FIGS. 3A through 3C are views of screens on which the mobile terminal 100 selects an object of the external display device 200, according to an exemplary embodiment. [0109]Referring to FIG. 3A, the display device 200 may display a plurality of objects indicating a plurality of pieces of contents. In this case, a user may use the mobile terminal 100 to select at least one of the plurality of objects displayed on the display device 200. [0110]For example, the user may move the mobile terminal 100 up and down and left and right (a first input) to select at least one of the plurality of objects displayed on the display device 200. In this regard, the display device 200 may display a location of a selection region (for example, a cursor and a pointer) corresponding to a movement of the mobile terminal 100 on a screen. [0111]Although a motion input is exemplarily used as the first input for selecting an object in FIG. 3A, the first input is not limited to the motion input. The first input may be a bending input, a key input, a voice input, and a touch input in addition to the motion input. [0112]According to an exemplary embodiment, the mobile terminal 100 may turn its screen off or may blacken its screen when selecting an object displayed on a screen of the display device 200 in such a way that users eyes are not distracted. [0113]According to another exemplary embodiment, the mobile terminal 100 may display thumbnail information such as an icon, an image, a title, etc. of contents relating to an object in which the selection region is disposed or a movement direction of the mobile terminal 100 as an arrow, etc. on the display device 200. [0114]Referring to FIG. 3B, the mobile terminal 100 may display a selection window (or a graphical user interface (GUI)) for selecting a category (for example, drama, movie, sports, etc.) of contents. In this regard, the mobile terminal 100 may receive a selection of at least one category from the user. The mobile terminal 100 may transmit information regarding the selected category to the display device 200. In this case, the display device 200 may filter and display an object regarding contents corresponding to the category selected by the user. [0115]Referring to FIG. 3C, the mobile terminal 100 may output a map or a GUI indicating objects displayed on the display device 200 from among all the objects. [0116]FIGS. 4A and 4B are views of screens on which the mobile terminal 100 obtains additional information, according to an exemplary embodiment. [0117]Referring to FIG. 4A, a user may move the mobile terminal 100, select an object of the display device 200, then rotate the mobile terminal 100, and request additional information corresponding to the selected object from the display device 200. [0118]In this case, the display device 200 may transmit the additional information corresponding to the selected object or link information (for example, a uniform resource identifier (URI)) of the additional information to the mobile terminal 100. In this regard, the mobile terminal 100 may display the obtained additional information on a screen. [0119]For example, as shown in FIG. 4A, in a case where the user moves the mobile terminal 100, selects an object illustrating Shrek, and converts a vertical mode of the mobile terminal 100 into a horizontal mode, the mobile terminal 100 may obtain and display additional information (for example, Movie Title: Shrek, Review: ★★★★⋆, Representative Image, and Advertisement Moving Image) relating to Shrek. [0120]According to an exemplary embodiment, referring to FIG. 4B, if the user wishes to select a new object, the user may select the object of the display device 200 again by converting the horizontal mode of the mobile terminal 100 into the vertical mode. [0121]Although a motion input is that an object is selected and then is that the mobile terminal 100 receives and displays additional information corresponding to the object in FIGS. 3A through 4B as a rotation input, an exemplary embodiment is not limited thereto. That is, according to an exemplary embodiment, the mobile terminal 100 may receive and display additional information regarding contents relating to an object in which a selection region is disposed from the display device 200 while selecting an object of the display device 200 as the motion input. According to an exemplary embodiment, a communication network over which the mobile terminal 100 transmits a signal for sele(String), 相关专利申请的交叉引用 [0001] 本申请要求于2012年7月25日向韩国知识产权局提交的韩国专利申请第10-2012-0081434号的优先权,其公开内容通过引用的方式整体并入本文。 背景 [0002] 1. 领域 [0003] 示例性实施例涉及用于通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与所选对象相对应的附加信息来显示信息的方法和移动终端、用于提供信息的方法和显示设备 通过基于移动终端的输入选择对象并向移动终端提供关于所选对象的附加信息,以及用于通过基于操作将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端 移动终端的模式。 [0004] 2.相关技术的描述 [0005] 智能电视(TV)是一种将电视与上网功能相结合,能够利用各种功能的多功能电视,如网上冲浪、视频点播(VOD)观看、社交网络服务(SNS)、游戏等。 并安装各种应用程序。 [0006] 智能电视的一个特点是用户和电视可以相互发送和接收信息。 这是智能电视与现有的仅单方面传输信息的电视的区别。 因此,智能电视也被称为互动电视。 [0007] 但是,用户使用标准遥控器来使用智能电视的各种功能是非常不方便的。 特别地,当用户浏览或下载内容时,需要通过几个步骤来操作遥控器。 [0008] 因此,需要一种让用户容易控制智能电视的控制装置或系统。 概括 [0009] 示例性实施例提供一种用于显示信息的方法和移动终端,该方法和移动终端通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与选择的对象相对应的附加信息来进行。 [0010] 示例性实施例还提供了一种用于通过基于移动终端的输入来选择对象并将关于所选择的对象的附加信息提供给移动终端来提供信息的方法和显示设备。 [0011] 示例性实施例还提供一种用于通过基于移动终端的操作模式将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端。 [0012] 根据示例性实施例的一方面,提供了一种移动终端显示信息的方法,该方法包括:基于第一输入将用于选择在外部显示设备上显示的对象的第一信号发送到外部显示设备 用户通过移动终端; 基于用户通过移动终端的第二输入向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0013] 发送第一选择对象信号可以包括: 根据外部显示设备的控制协议对选择对象信号进行转换。 [0014] 用于选择对象的第一信号的发送可以包括:发送用于控制选择区域的移动的信号,用于选择显示在外部显示设备上的对象。 [0015] 发送用于控制选择区域的移动的信号可以包括:发送用于控制选择区域的移动方向、选择区域的移动速度和屏幕上显示的对象的数量中的至少一项的信号。 基于第一输入的外部显示设备。 [0016]发送用于选择对象的第一信号可以包括:在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0017] 缩略图信息可以包括与对象对应的内容的图像、内容的标题和内容的类型中的至少一个。 [0018] 发送用于选择对象的第一信号可以包括:根据第一输入在屏幕上显示移动终端的移动方向。 [0019] 第一输入和第二输入可以包括运动输入、键输入、触摸输入、弯曲输入和语音输入中的至少一个。 [0020] 第一输入可以包括用于在3D方向上移动移动终端的三维(3D)运动输入,其中第二输入包括用于将移动终端旋转超过预定角度的旋转运动输入。 [0021] 发送用于请求附加信息的第二信号可以包括:从显示设备接收附加信息。 [0022] 用于请求附加信息的第二信号的发送可以包括:基于第二输入从外部显示设备接收附加信息的链接信息; 以及基于接收到的链接信息从服务器接收附加信息。 [0023] 将用于选择对象的第一信号发送给显示设备可以包括: 向外部显示设备请求控制授权; 接收来自外部显示设备的控制授权接受消息。 [0024] 内容可以包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。 [0025] 附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、广告图像信息和专辑信息中的至少一种。 [0026] 该方法还可以包括:基于用户通过移动终端的第三输入来控制在移动终端的屏幕上显示的附加信息。 [0027] 对附加信息的控制可以包括:基于用户通过移动终端的第三输入,控制附加信息的显示、附加信息的播放以及改变为上一个附加信息或下一个附加信息中的至少一个。 [0028] 该方法还可以包括:获取与显示在移动终端的屏幕上的附加信息对应的内容。 [0029] 根据另一示例性实施例的一方面,提供了一种显示装置向移动终端提供信息的方法,该方法包括:通过通过移动终端接收用户的第一输入来选择显示在显示装置上的对象。 ; 通过移动终端接收用户的第二输入,将与选择的对象对应的附加信息发送到移动终端。 [0030] 发送可以包括:从对应于所选对象的内容中提取附加信息。 [0031] 对象的选择可以包括:从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号; 根据控制信号移动选择区域。 [0032] 对象的选择可以包括:将接收到的第一输入转换为用于根据显示设备的控制协议控制选择区域的移动的控制信号。 [0033] 接收可以包括:从多个移动终端中的每一个接收用于控制选择区域的移动的控制信号。 [0034]该方法还可以包括:感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0035] 对象的选择可以包括:基于用户通过移动终端的第一输入,控制选择区域的移动方向、选择区域的移动速度以及屏幕上显示的对象的数量中的至少一个。 . [0036] 对象的选择可以包括:将对象对应的内容的缩略图信息发送给移动终端。 [0037] 向移动终端发送附加信息可以包括:向移动终端发送附加信息的链接信息。 [0038] 终端还可以包括: 从移动终端接收与选择的对象对应的内容的传输请求; 将选择的对象对应的内容发送给移动终端。 [0039] 根据另一示例性实施例的一方面,提供了一种移动终端,包括: 通信单元,被配置为基于用户的第一输入向外部显示设备发送用于选择在外部显示设备上显示的对象的信号。 通过移动终端; 附加信息获取单元,被配置为基于用户通过移动终端的第二输入向外部显示设备发送请求与所选对象对应的附加信息的信号; 显示器,用于显示从外部显示设备接收到的附加信息; 控制器,用于控制通信单元、附加信息获取单元和显示单元。 [0040] 控制器可以根据外部显示设备的控制协议转换用于选择对象的信号。 [0041] 通信单元可以发送用于控制选择区域的移动的信号,该选择区域用于选择显示在外部显示装置上的对象。 [0042] 通信单元可以基于第一输入发送用于控制选择区域的移动方向、选择区域的移动速度和显示在外部显示装置的屏幕上的对象的数量中的至少一个的信号。 [0043] 显示器可以在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0044] 附加信息获取单元可以从外部显示设备接收附加信息。 [0045] 通信单元可以基于第二输入从外部显示装置接收附加信息的链接信息,并且其中附加信息获取单元基于接收到的链接信息从服务器接收附加信息。 [0046] 控制器可以基于用户通过移动终端的第三输入来控制在移动终端上显示的附加信息。 [0047] 所述移动终端还可以包括: 内容获取单元,用于获取所述移动终端显示的附加信息对应的内容。 [0048] 根据示例性实施例的一方面,提供了一种显示装置,包括: 选择单元,被配置为基于用户通过移动终端的第一输入选择显示在显示装置上的对象; 通信单元,被配置为通过接收用户通过移动终端的第二输入,将与选择的对象对应的附加信息发送到移动终端,以及控制器,被配置为控制选择单元和通信单元。 [0049] 控制器可以从对应于所选对象的内容中提取附加信息。 [0050] 选择单元可以从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号,并且根据接收到的控制信号移动选择区域。 [0051] 控制器可以根据显示设备的控制协议将接收到的第一输入转换为用于控制选择区域的移动的控制信号。 [0052] 显示装置还可以包括:传感器,用于感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0053] 控制器可以基于用户通过移动终端的第一输入来控制选择区域的移动方向、选择区域的移动速度和显示在屏幕上的对象的数量中的至少一个。 [0054] 通信单元可以将附加信息的链接信息发送到移动终端。 [0055] 通信单元可以从移动终端接收对与所选对象相对应的内容的传输请求,并将与所选对象相对应的内容发送到移动终端。 [0056] 根据另一示例性实施例的一方面,提供了一种移动终端生成控制信号的方法,该方法包括:接收用户输入; 确定移动终端的操作模式; 并且响应于确定操作模式是第一模式,基于用户输入生成用于控制外部显示设备的第一控制信号,并且响应于确定操作模式是第二模式,生成用于控制外部显示设备的第二控制信号 基于用户输入控制在移动终端上显示的内容。 [0057] 内容可以包括与从外部显示设备选择的对象相对应的内容或与基于第一控制信号的对象相对应的附加信息。 [0058] 用户输入可以包括动作输入、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0059] 所述确定可以包括:在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第一模式,以及,在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第二模式。 终端处于水平模式。 [0060] 所述确定可以包括:根据所述移动终端的屏幕上显示的信息确定所述移动终端的操作模式。 [0061] 所述确定可以包括:响应于确定所述移动终端屏幕上显示的信息为所述外接显示设备上显示的对象对应的内容的缩略图信息或所述移动终端的移动方向信息,确定所述移动终端的操作模式。 终端作为第一模式,并且,响应于确定移动终端的屏幕上显示的信息是与外部显示设备上显示的对象对应的内容或与该对象对应的附加信息,确定移动终端的操作模式 终端作为第二种模式。 [0062] 第一控制信号的产生可以包括:根据外部显示设备的控制协议转换第一控制信号。 [0063] 第一模式可以是选择外部显示设备的对象的模式,第二模式是在移动终端上显示与选择的对象对应的附加信息的模式。 [0064] 第一控制信号可以包括用于控制用于选择外部显示设备的对象的选择区域的移动的信号,并且第二控制信号可以包括用于控制内容的播放、内容的编辑中的至少一个的信号。 ,以及内容的传输。 [0065]该方法还可以包括:接收用于将移动终端在第一方向上旋转预定角度的第一旋转运动输入; 基于第一旋转运动输入将操作模式从第一模式转换为第二模式; 接收用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入; 基于第二旋转运动输入,将操作模式从第二模式转换为第一模式。 [0066] 根据另一示例性实施例的一方面,提供了一种移动终端,包括: 用户输入,被配置为接收用户输入; 操作模式确定单元,用于确定移动终端的操作模式; 控制器,被配置为响应于操作模式确定单元确定操作模式是第一模式,基于用户输入产生用于控制外部显示装置的第一控制信号,并且响应于操作模式 确定单元确定操作模式是第二模式,基于用户输入产生用于控制在移动终端上显示的内容的第二控制信号。 [0067] 用户输入可以接收用于将移动终端沿第一方向旋转预定角度的第一旋转运动输入和用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入,并且其中控制器转换操作 基于第一旋转运动输入从第一模式到第二模式的模式和基于第二旋转运动输入从第二模式到第一模式的操作模式。 [0068] 根据另一示例性实施例的一方面,提供了一种在移动终端显示器上显示外部显示设备的信息的方法。 该方法包括:接收到移动终端的关于显示在外部显示设备上的对象的用户输入; 传送第一信号至外接显示装置以选择外接显示装置上显示的对象; 接收到移动终端的关于与显示在外部显示设备上的对象对应的附加信息的第二用户输入; 向外部显示设备发送第二信号以请求对应于所选对象的附加信息; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0069] 发送第一信号可以包括将第一信号转换为外部显示设备的控制协议。 [0070] 发送第一信号可以包括从外部显示设备请求控制授权和从外部显示设备接收控制授权接受消息。 附图的简要说明 [0071] 通过参考附图详细描述示例性实施例,上述和其他特征和优点将变得更加明显,其中: [0072] 图1是用于说明根据示例性实施例的信息提供系统的视图; [0073] 图2是用于说明另一实施方式的信息提供系统的图。 [0074] 图3A至图3C是根据示例性实施例的移动终端选择外部显示设备的对象的屏幕的视图; [0075] 图4A和4B是根据示例性实施例的移动终端在其上获得附加信息的屏幕的视图; [0076] 图5是根据示例性实施例的获取内容的屏幕的视图; [0077] 图6是根据示例性实施例的显示或再现对象的屏幕的视图; [0078] 图7是示出根据示例性实施例的移动终端显示信息的方法的流程图; [0079] 图8是示出根据示例性实施例的移动终端显示信息的方法的详细流程图; [0080]图9是示出根据示例性实施例的显示设备感测移动终端的输入并提供附加信息的方法的流程图; [0081] 图10是示出根据示例性实施例的移动终端通过服务器获取附加信息的方法的流程图; [0082] 图11是示出根据示例性实施例的移动终端获取内容的方法的流程图; [0083] 图12是示出根据示例性实施例的移动终端通过服务器获取内容的方法的流程图; [0084] 图13是根据示例性实施例的多个移动终端中的每一个选择显示装置的对象的屏幕的视图; [0085] 图14是根据示例性实施例的移动终端的框图; [0086] 图15是根据示例性实施例的显示装置的框图; [0087] 图16是示出根据示例性实施例的显示设备提供信息的方法的流程图; 和 [0088] 图17是示出根据示例性实施例的移动终端生成控制信号的方法的流程图。 示例性实施例的详细说明 [0089] 首先,将简要描述这里使用的术语,然后将详细描述示例性实施例。 [0090] 尽管这里使用的术语是考虑到示例性实施例的功能而目前广泛使用的通用术语,但是它们可以根据本领域普通技术人员的意图、先例、新技术的出现或 类似。 此外,在特定情况下,申请人可以任意选择条款。 在这种情况下,术语的含义将在示例性实施例的详细描述中详细描述。 因此,在详细描述中使用的术语不应仅仅是术语的名称,而应基于与示例性实施例相关的含义和内容来定义。 [0091] 当一个单元“包括”整个说明书中的一个元素时,该单元不排除另一个元素,而是可以进一步包括另一个元素,除非上下文另有明确说明。 此外,诸如“. . . 这里使用的“单元”、“模块”等表示用于执行至少一个功能或操作的单元,可以通过硬件或软件或其组合来实现。 [0092] 在整个说明书中,“对象”指的是可以由用户从显示设备中选择的目标。 对象的示例包括但不限于图标、链接、图片、文本、索引项等。 [0093] 另外,“附加信息”是指与对象对应的内容有关的信息,可以根据内容的种类而具有各种形式。 附加信息的示例可以包括但不限于预览信息、试听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息、 等等 [0094] 在本说明书中,“内容”可以在移动终端中显示、再现或存储,并且可以包括例如静止图像内容(例如照片、图片等)、文本内容(例如 、电子书(一首诗和一部小说)、一封信、一个商业文件、一个网页、一个电子节目指南(EPG)等)、运动图像内容(例如,个人图像、电影、音乐 视频、YouTube 视频、电视节目图像等)、音乐内容(例如,音乐、音乐表演、无线电广播等)、应用程序(小部件、游戏等) [0095]现在将参照附图更全面地描述示例性实施例。 然而,示例性实施例可以以许多不同的形式体现,并且不应被解释为限于本文所阐述的实施例; 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明构思充分传达给本领域普通技术人员。 为了清楚起见,在附图中,省略了与描述无关的部分,并且在整个说明书中类似的附图标记被添加到类似的部分。 [0096] 如本文所用,术语“和/或”包括一个或多个相关列出的项目的任何和所有组合。 诸如“至少一个”之类的表达式在元素列表之前时,会修改整个元素列表,而不是修改列表中的单个元素。 [0097] 图1是用于解释根据示例性实施例的信息提供系统的视图。 [0098] 参考图1,根据示例性实施例的信息提供系统可以包括移动终端 100 和一个外部显示设备 200 . [0099] 移动终端 100 是从外部获取内容并显示、再现或存储获取的内容的设备。 移动终端 100 可以以各种方式实现。 例如,移动终端 100 本说明书中描述的可以包括蜂窝电话、智能电话、膝上型计算机、平板个人计算机(PC)、电子书终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、 导航系统等 [0100] 显示装置 200 是一种可以是各种类型的设备,包括显示面板。 例如,显示设备 200 本说明书中描述的可以包括智能电视(TV)、互联网协议电视(IPTV)、数字电视(DTV)、计算机、膝上型计算机、电子书终端、平板电脑、数字广播终端 ,消费电子(CE)设备(例如,具有显示面板的冰箱或空调)等。 [0101] 显示装置 200 根据示例性实施例,可以显示对象列表。 对象列表可以包括关于至少一个内容的标识信息。 标识信息的示例可以包括内容的标题、指示内容的图像和图标等。 [0102] 图2是用于说明根据另一示例性实施例的信息提供系统的视图。 [0103] 参考图2,根据另一示例性实施例的信息提供系统可以包括移动终端 100 , 显示装置 200 , 和一个服务器 300 . [0104] 移动终端 100 和显示装置 200 与参考图1描述的相同,因此省略其描述。 [0105] 服务器 300 可与移动终端通信 100 或显示设备 200 . 根据示例性实施例,服务器 300 可以从移动终端接收内容提供请求 100 或显示设备 200 . 在这种情况下,服务器 300 可以向移动终端提供内容 100 或显示设备 200 . 服务器提供的内容 300 可以是显示设备选择的对象对应的内容 200 或与对象对应的附加信息。 [0106] 例如,在显示设备 200 选择与电影内容相关的对象,服务器 300 可向移动终端提供电影内容或电影内容的预览视频 100 或显示设备 200 . [0107] 以移动终端为例 100 现在将参照图3至图6简要描述基于用户输入选择在外部显示设备上显示的对象并获得并显示与所选择的对象相对应的附加信息。 [0108] 图3A到3C是移动终端在其上的屏幕的视图 100 选择外部显示设备的对象 200 ,根据示例性实施例。 [0109] 参照图3A,显示装置 200 可以显示指示多条内容的多个对象。 在这种情况下,用户可以使用移动终端 100 选择显示在显示设备上的多个对象中的至少一个 200 . [0110] 例如,用户可以移动移动终端 100 上下左右(第一输入)以选择显示设备上显示的多个对象中的至少一个 200 . 对此,显示设备 200 可以显示与移动终端的移动相对应的选择区域(例如,光标和指针)的位置 100 在屏幕上。 [0111] 尽管在图3A中示例性地使用动作输入作为用于选择对象的第一输入,但是第一输入不限于动作输入。 除了动作输入之外,第一输入可以是弯曲输入、键输入、语音输入和触摸输入。 [0112] 根据示例性实施例,移动终端 100 选择显示设备屏幕上显示的对象时,可能会关闭屏幕或将屏幕变黑 200 这样用户的眼睛就不会分心。 [0113] 根据另一示例性实施例,移动终端 100 可以显示与设置选择区域的对象或移动终端的移动方向有关的内容的缩略图信息,例如图标、图像、标题等 100 显示设备上的箭头等 200 . [0114] 参考图3B,移动终端 100 可以显示用于选择内容类别(例如,戏剧、电影、体育等)的选择窗口(或图形用户界面(GUI))。 对此,移动端 100 可以接收来自用户的至少一个类别的选择。 移动终端 100 可以将关于所选类别的信息发送到显示设备 200 . 在这种情况下,显示设备 200 可以过滤和显示关于与用户选择的类别相对应的内容的对象。 [0115] 参考图3C,移动终端 100 可以输出地图或图形用户界面指示显示设备上显示的对象 200 从所有对象中。 [0116] 图4A和4B是移动终端在其上的屏幕的视图 100 根据示例性实施例,获取附加信息。 [0117] 参考图4A,用户可以移动移动终端 100 , 选择显示设备的对象 200 ,然后旋转移动端 100 , 并向显示设备请求与所选对象对应的附加信息 200 . [0118] 在这种情况下,显示设备 200 可以将与选择的对象相对应的附加信息或附加信息的链接信息(例如,统一资源标识符(URI))发送到移动终端 100 . 对此,移动端 100 可以在屏幕上显示获得的附加信息。 [0119] 例如,如图4A所示,在用户移动移动终端的情况下 100 ,选择描绘史莱克的对象,并转换移动终端的垂直模式 100 进入横屏模式,移动端 100 可能会获取和显示与史莱克有关的附加信息(例如,电影名称:史莱克、评论:★★★★⋆、代表图像和广告动态图像)。 [0120] 根据示例性实施例,参照图4B,如果用户希望选择新对象,则用户可以选择显示设备的对象 200 再次通过转换移动端的水平模式 100 进入垂直模式。 [0121] 虽然动作输入是选择了一个对象然后是移动终端 100虽然接收和显示与图3A至图4B中的对象相对应的附加信息作为旋转输入,但示例性实施例不限于此。 也就是说,根据示例性实施例,移动终端 100 可以从显示装置接收和显示关于与其中设置了选择区域的对象有关的内容的附加信息 200 在选择显示设备的对象时 200 作为运动输入。 根据示例性实施例,移动终端在其上的通信网络 100 将用于选择对象的信号发送到显示设备 200 以及移动终端所通过的通信网络 100 从显示设备接收附加信息 200 可能彼此不同。 例如,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 通过蓝牙通信,然后从显示设备接收与所选对象对应的附加信息 200 通过 Wi-Fi 通信。 [0122] 图5是根据示例性实施例的在其上获得内容的屏幕的视图。 [0123] 用户可以确认关于与从显示设备获得的对象相对应的内容的附加信息 200 然后向显示设备请求相应的内容 200 或服务器 300 . 例如,用户可以通过显示设备确认关于电影史瑞克的附加信息(用户评论等) 200 然后从显示设备请求和下载电影内容史莱克 200 或服务器 300 . [0124] 图6是根据示例性实施例的显示或再现对象的屏幕的视图。 [0125] 参考图6,根据示例性实施例,移动终端 100 可以显示或再现从显示设备下载的内容 200 或服务器 300 . [0126] 根据另一示例性实施例,移动终端 100 可以通过流式传输内容来接收和再现内容。 [0127] 一种移动终端的方法 100 现在将在下面详细描述基于用户输入检索和/或显示信息。 [0128] 根据示例性实施例的显示信息的方法可以通过预定应用来实现。 也就是移动终端 100 可以驱动用于提供根据示例性实施例的显示信息的方法的应用。 移动终端 100 可以基于用户输入或自动驱动应用程序。 [0129] 移动端驱动的应用 100 可以是仅用于执行控制显示设备的过程的应用程序 200 或提供各种服务。 例如,该应用程序可以是用于提供远程控制服务、信使服务、社交网络服务(SNS)、多媒体内容播放服务等的应用程序。 [0130] 假设移动终端使用的方法 100 可以通过预定应用程序来执行参考图7至图12描述的显示信息。 [0131] 图7是示出移动终端的方法的流程图 100 根据示例性实施例,显示信息。 参照图7,移动终端的方法 100 根据示例性实施例的显示信息包括由移动终端顺序执行的操作 100 稍后将描述的图14的。 因此,虽然以下省略,但以上关于移动终端的描述 100 图14的方法也将适用于图7的方法,其中移动终端 100 显示信息。 [0132] 在操作 S 710 , 移动端 100 可以发送用于选择外部显示设备的对象的信号 200 到显示设备 200 基于第一输入。 在接收到第一输入的情况下,移动终端 100可以产生用于选择显示设备的对象的信号 200 基于第一个输入。 [0133] 根据示例性实施例,移动终端 100 可以根据显示设备的控制协议转换用于选择对象的信号 200 . 也就是移动终端 100 可以获得显示设备的标识信息(例如设备类型、设备ID、设备序列号等) 200 并将接收到的用户的第一输入转换为显示设备可识别的控制命令 200 基于显示设备的识别信息 200 . [0134] 根据示例性实施例的用于选择对象的信号可以包括用于控制选择对象的选择区域的移动的信号。 也就是说,在移动终端 100 移动终端检测到超过阈值的移动 100 可以产生用于控制显示装置的选择区域的移动的信号 200 基于有关检测到的运动的信息。 [0135] 例如,在陀螺仪传感器值小于阈值的情况下,移动终端 100 可以确定移动终端 100 不移动,可以不产生用于控制选择区域移动的信号,并且,每次陀螺传感器值改变预定值(例如,10度)时,可以产生用于将选择区域移动一个空间的控制信号 /sec) 大于阈值。 [0136] 根据另一示例性实施例的用于选择对象的信号可以包括信息(例如,移动终端的移动位置信息) 100 ) 关于第一个输入。 也就是移动终端 100 可以直接产生控制选择区域移动的信号并将其传输到显示装置 200 或者可以发送信息(例如,移动终端的移动位置信息) 100 ) 关于显示设备的第一个输入 200 . [0137] 在信息(例如,移动终端的移动位置信息 100 ) 关于第一个输入被传输到显示设备 200 , 显示设备 200 可以根据显示设备的控制协议将第一输入转换为用于控制选择区域的移动的信号 200 . [0138] 例如,在接收到小于阈值的陀螺传感器值的情况下,移动终端 100 可以确定移动终端 100 不移动并且可能不产生用于控制选择区域移动的信号。 移动终端 100 每当接收到大于阈值的预定陀螺传感器值(例如,10度/秒)时,可以生成用于将选择区域移动一个空间的控制信号。 [0139] 在生成控制信号之前,移动终端 100 可以通过身份验证来授权显示设备 200 通过显示设备 200 . 例如,移动终端 100 可以向显示设备请求控制授权 200 . 对此,移动端 100 可以通过发送移动终端的识别信息来请求控制授权 100 到显示设备 200 . 移动终端的识别信息 100 是识别移动终端的唯一信息 100 ,并且可能包括例如设备 ID、唯一序列号、媒体访问控制 (MAC) 地址、国际移动设备身份 (IMEI) 等。 [0140] 显示装置 200 可认证移动终端的控制权限 100 基于移动终端的识别信息 100 . 在认证成功的情况下,显示设备 200 可以向移动终端发送控制授权接受消息 100. 在这种情况下,移动终端 100 可以控制显示设备 200 . [0141] 在发送控制授权接受消息时,显示设备 200 可以注册移动终端的识别信息 100 在一个存储单元中。 因此,虽然移动终端 100 未经显示设备认证 200 不再是移动端 100 可以控制显示设备 200 . [0142] 在操作 S 720 , 移动端 100 可以获得与从显示设备中选择的对象相对应的附加信息 200 基于第二个输入。 即,在接收到第二输入的情况下,移动终端 100 可以从显示设备请求与基于第一输入选择的对象相对应的附加信息 200 . 在这种情况下,移动终端 100 可以从显示设备获取附加信息 200 或通过服务器 300 . 稍后将参考图8对此进行详细描述。 [0143] 在操作 S 730 , 移动端 100 可以在屏幕上显示获得的附加信息。 移动终端 100 可以在将附加信息存储在存储单元中之后通过下载来显示附加信息,或者可以通过流式传输附加信息来显示附加信息。 [0144] 根据示例性实施例的附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息等。 [0145] 这将在稍后参考图8更详细地描述。 图8是示出移动终端的方法的详细流程图 100 根据示例性实施例,显示信息。 [0146] 在操作 S 810 , 移动端 100 可以接收第一输入。 移动端的第一个输入 100 可以是动作输入(例如3D动作输入、旋转动作输入等)、按键输入、触摸输入、弯曲输入、语音输入、多模态输入等。即用户 可以移动移动终端 100 上(+Y 轴方向)和下(-Y 轴方向)和左(-X 轴方向)和右(+X 轴方向),触摸(轻拂、拖动、轻敲、平移等)屏幕(或 GUI显示在屏幕上)的移动终端 100 上下左右,操作移动(方向)键,弯曲移动终端的预定区域(左上,右上,左下,右下) 100 ,或输入包括移动命令的语音。 在操作 S 820 , 移动端 100 可以基于第一输入生成用于选择对象的信号。 例如,在第一输入为移动终端的动作输入的情况下 100 上下左右移动,移动端 100 可以根据移动终端的移动生成用于控制选择区域的移动的信号 100 . 即,在用户移动移动终端的情况下 100 向左(-X轴方向)移动预定值以上,移动终端 100 可以产生用于将选择区域向左移动一格的控制信号。 [0147] 在第一输入为上下左右触摸触摸屏的触摸输入的情况下,移动终端 100 可以根据用户的触摸手势产生用于控制选择区域的移动的信号。 例如,在用户使用手指或电子笔从左向右轻拂触摸屏超过预定距离的情况下,移动终端 100 可以产生用于将选择信号向右移动一个空间的控制信号。 [0148] 在第一输入是操作移动(方向)键的键输入的情况下,移动终端 100可以产生用于将选择区域移动到与方向键对应的位置的控制信号。 [0149] 在第一输入是移动终端的预定区域的弯曲输入的情况下 100 , 可以由柔性显示器形成, 弯曲, 移动终端 100 可以产生用于在对应于弯曲运动的方向上移动选择区域的控制信号。 “弯曲”可以是移动终端的弯曲或变形 100 通过外力。 “弯曲运动”可以是移动终端的弯曲运动或变形 100 . [0150] 例如,在用户弯曲移动终端顶部的情况下 100 , 移动端 100 在用户弯曲移动终端的左侧区域的情况下,可以生成用于将选择区域向上移动一格的控制信号 100 , 移动端 100 可以生成用于将选择区域向左移动一个空间的控制信号,并且在用户弯曲整个移动终端的情况下 100 , 移动端 100 可以产生用于选择包括当前选择区域的对象的控制信号。 [0151] 在第一输入为语音输入的情况下,移动终端 100 可以生成用于将选择区域移动到与语音输入对应的位置的控制信号。 例如,在用户说“向左移动三个空格”的情况下,移动终端 100 可以生成用于将选择区域向左移动三个空间的控制信号。 [0152] 在操作 S 830 , 移动端 100 可以将基于第一输入生成的用于选择对象的信号发送到显示装置 200 . 移动终端 100 根据示例性实施例,可以将用于选择对象的信号发送到显示装置 200 直接或通过服务器 300 . 移动终端 100 根据示例性实施例,还可以使用各种通信方法发送用于选择对象的信号。 [0153] 例如,在移动终端 100 和显示设备 200 在预定范围(局域距离)内,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 直接通过短距离无线通信(蓝牙、Zigbee、近场通信(NFC)、Wi-Fi直连(WFD)、超宽带(UWB)、红外数据协会(IrDA)等)。 移动终端 100 也可以通过移动通信网络(例如,2G/3G/4G、Wibro等)或无线局域网(LAN)(Wi-Fi:ad-hoc模式,基础设施模式)传输用于选择对象的信号 )。 [0154] 在操作 S 840 , 显示设备 200 可以根据移动终端的第一输入移动选择区域 100 . 例如,在第一输入为移动终端的动作输入的情况下 100 向左移动(-X 轴方向),显示设备 200 将选择区域向左移动。 [0155] 根据示例性实施例,显示装置 200 可以基于第一输入控制选择区域的移动速度。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 以高于阈值速度的速度向右移动,显示设备 200 可以将选择区域向右移动几个空格(例如,每3个空格),并且,如果用户移动移动终端 100 以低于阈值速度的速度向左移动,显示设备 200 可以将选择区域向左移动一格。 [0156] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户拖动移动终端的触摸屏 100 在高于阈值速度的速度下,显示设备 200 可以将选择区域移动几个空格,并且,如果用户拖动移动终端的触摸屏 100在低于阈值速度的速度下,显示设备 200 可以将选择区域移动一个空格。 [0157] 根据示例性实施例,在第一输入是弯曲输入的情况下,显示装置 200 可以基于用户弯曲移动终端的预定区域的次数来控制选择区域的移动速度 100 . 例如,在用户弯曲移动终端顶部的情况下 100 三、显示装置 200 可以将选择区域向上移动三个空格,并且在用户弯曲移动终端的右侧区域的情况下 100 两次,显示设备 200 可以将选择区域向右移动两个空格。 此外,显示装置的例子多种多样 200 根据第一个输入移动选择区域。 [0158] 根据示例性实施例,显示装置 200 可以基于第一输入调整屏幕上显示的对象的数量。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 在正面方向(+Z轴方向)上,显示装置 200 可能会减少屏幕上显示的对象数量,并且,如果用户移动移动终端 100 在后方(-Z轴方向),显示装置 200 可能会增加屏幕上显示的对象数量。 [0159] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户多点触摸移动终端的触摸屏上的至少两个点 100 并将两个点拖离对方,显示设备 200 可能会减少屏幕上显示的对象数量,并且如果用户将两个点拖得更近,则显示设备 200 可能会增加屏幕上显示的对象数量。 [0160] 根据示例性实施例,在第一输入是弯曲输入的情况下,如果用户弯曲移动终端的中心部分 100 为凸出,显示装置 200 可以减少屏幕上显示的对象的数量,并且,如果用户弯曲移动终端的中心部分 100 是凹的,显示装置 200 可能会增加屏幕上显示的对象数量。 [0161] 此外,显示装置的例子多种多样 200 根据第一个输入调整屏幕上显示的对象数量。 [0162] 根据示例性实施例,虽然显示装置 200 根据移动终端的第一输入选择对象 100 , 移动端 100 可以从显示装置接收并显示与其中设置有选择区域的对象相对应的内容的缩略图信息 200 . 例如,移动终端 100 可以显示与设置有选择区域的对象相对应的内容的图像、图标、标题、内容类型等。 移动终端可以显示与移动终端的当前位置相对应的选择区域的位置 100 以及选择区域在显示装置的整个屏幕上的移动方向 200 . [0163] 根据另一示例性实施例,移动终端 100 可能会关闭其屏幕或使其屏幕变黑,以使用户的眼睛不会从显示设备的屏幕上分心 200 在其上选择对象。 [0164] 在操作 S 850 , 显示设备 200 选择对象。 根据示例性实施例,显示装置 200 可以基于第一输入选择其中布置了移动的选择区域的对象。 [0165] 根据示例性实施例,显示装置 200 可以识别(强调)其中设置选择区域的对象。 例如,显示设备 200可以将设置选择区域的对象的边框表示为框,也可以将设置选择区域的对象相对于其他对象增大尺寸,或者制作闪烁等动画效果。 [0166] 在操作 S 860 , 移动端 100 可以接收第二个输入。 根据示例性实施例的第二输入可以是用于获得附加信息的用户输入。 移动端二次输入 100 根据示例性实施例,可以包括动作输入、键输入、弯曲输入和语音输入中的至少一种。 例如,用户可以旋转移动终端 100 以预定角度弯曲移动终端的中心部分 100 , 按下移动端的一个选择键 100 ,在请求附加信息的屏幕上触摸(轻敲)GUI,或输入请求附加信息的语音。 第二输入不限于此,并且可以存在多种示例。 [0167] 在操作 S 870 , 移动端 100 可以向显示设备请求与所选对象对应的附加信息 200 . 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 直接或通过服务器 300 . [0168] 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 通过短距离无线通信(蓝牙、Zigbee、NFC、WFD、UWB、IrDA等)、移动通信(例如2G/3G/4G、Wibro等)或无线局域网(Wi -Fi:ad-hoc 模式,基础设施模式)。 [0169] 在操作 S 880 , 显示设备 200 可以将与选择的对象对应的附加信息发送到移动终端 100 . 例如,在选择与电影内容相关的对象的情况下,显示设备 200 可将与电影内容有关的附加信息(代表场景、预览视频、制作信息、概要信息、演员、导演信息、用户评论信息等)传输到移动终端 100 . [0170] 在选择与应用相关的对象的情况下,显示设备 200 可以向移动终端发送关于应用程序的附加信息(例如,应用程序的说明、应用程序审查信息、应用程序更新信息等) 100 . [0171] 根据示例性实施例,在选择与照片有关的对象的情况下,显示装置 200 可以将包括照片的元数据(例如,拍摄地点、拍摄时间等)、与照片中的人物相关的信息(例如,报纸文章、外观电影、代表性音乐等)等附加信息传输到 移动终端 100 . [0172] 根据示例性实施例,在选择与音乐有关的对象的情况下,显示装置 200 可以向移动终端发送关于音乐的附加信息,包括专辑信息、音乐视频、预告视频、预听信息、报纸文章、歌手信息等 100 . [0173] 根据示例性实施例,在选择与网站有关的对象的情况下,显示装置 200 可能会向移动终端发送附加信息,包括有关网站的预览信息 100 . [0174] 根据示例性实施例,在选择与EPG有关的对象的情况下,显示装置 200 可以向移动终端发送关于EPG的附加信息,包括广播节目概要、每集的预览信息等 100 . 在选择与购物项目有关的对象的情况下,显示装置 200可以向移动终端发送关于购物项目的附加信息,包括商品信息、订单信息、推荐信息等 100 . [0175] 根据示例性实施例,显示装置 200 可以将先前存储在存储单元中的附加信息发送到移动终端 100 . 如果附加信息的链接信息仅存储在存储单元中,则显示设备 200 可能会收到来自服务器的附加信息 300 并将接收到的附加信息发送给移动终端 100 . 显示装置 200 可以在搜索引擎或网站中搜索与对象相关的附加信息,并将找到的附加信息提供给移动终端 100 . [0176] 在操作 S 890 , 移动端 100 可以显示获得的附加信息。 移动终端 100 可以基于用户输入控制显示的附加信息。 现在将参考图 9 对此进行详细描述。 [0177] 如上所述,根据示例性实施例,用户可以搜索和/或选择与显示在外部显示设备上的内容有关的对象 200 通过手机端的简单输入 100 并确认与所选对象有关的附加信息,以确定是否接收相应的内容。 [0178] 图9是示出显示装置的方法的流程图 200 感应移动终端的输入 100 并且根据示例性实施例提供附加信息。 此处省略图8和图9之间的重复描述。 [0179] 参考图9,根据示例性实施例,移动终端 100 可以在操作 S 中接收第一输入 910 和显示设备 200 可感应移动终端的输入 100 . [0180] 例如,在操作 S 920 , 显示设备 200 可以感测移动终端的第一输入 100 用于选择对象。 操作 S 930 通过 S 960 图9的对应于操作S 810 通过 S 860 与图8相同,因此这里将省略对其的重复描述。 在操作 S 970 , 显示设备 200 可以感测移动终端的第二输入 100 用于获取对应于所选对象的附加信息。 操作 S 980 通过 S 995 图9的对应于操作S 870 通过 S 890 与图8相同,因此这里将省略对其的重复描述。 [0181] 移动终端的第一输入和第二输入 100 可以包括运动输入(例如,3D运动输入、旋转运动输入等)、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0182] 根据示例性实施例,在第一输入和第二输入是动作输入的情况下,显示装置 200 可以感知移动终端的动作 100 通过相机。 例如,在用户移动移动终端的情况下 100 上下左右或旋转移动终端 100 , 显示设备 200 可感应移动终端的上下左右运动 100 或者移动终端的旋转 100 . [0183] 根据示例性实施例,在第一输入和第二输入是弯曲输入的情况下,显示装置 200 可以感测移动终端的弯曲运动 100 通过相机。 例如,显示设备 200 可以感测移动终端的弯曲位置(坐标值) 100 、弯曲方向、弯曲角度、弯曲速度、弯曲频率、弯曲运动发生时间、弯曲运动持续时间段等。 [0184] 根据示例性实施例,在第一输入和第二输入是触摸输入的情况下,显示装置 200可以通过摄像头感知用户的触摸手势。 [0185] 根据示例性实施例,在第一输入和第二输入是语音输入的情况下,显示装置 200 可以通过麦克风感测用户的语音输入。 [0186] 也就是说,根据示例性实施例,显示装置 200 可以感测第一输入或第二输入以验证从移动终端接收的用于选择对象的信号 100 或用于请求对应于对象的附加信息的信号。 例如,在显示设备 200 感测移动终端的动作输入 100 向右(+X轴方向)移动并从移动终端、显示设备接收用于将选择区域向左移动一格的控制信号 200 可以向移动终端请求控制信号 100 或者可能不跟随用于将选择区域向左移动一个空间的控制信号。 [0187] 根据另一示例性实施例,显示装置 200 可以感测第一输入或第二输入以直接生成用于移动用于选择对象的选择区域的控制命令、用于选择对象的控制命令以及用于将附加信息发送到移动终端的控制命令 100 . [0188] 图10是示出移动终端的方法的流程图 100 通过服务器获取附加信息 300 ,根据示例性实施例。 操作 S 1005 通过 S 1035 图10的对应于操作S 810 通过 S 870 与图8相同(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9549143B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:35:59.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), CN103577138A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.038 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), CN103577138B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.073 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), EP2690880A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), IN1206DELNP2015A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), JP2014027659A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.179 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), JP6335448B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), KR101971624B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.249 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), KR1020140019078A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.283 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.284 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), TW201412097A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.318 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.319 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), TWI574557B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), US20140028921A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.388 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), US20170118436A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.423 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.423 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.423 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), US9549143B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.458 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271674(Integer), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9549143B2(String), US9549143B2(String), 1484582400(Integer), 271674(Integer), 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.528 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.575 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186002(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186002(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.677 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.678 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.711 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.712 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186002(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 186002(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.781 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.816 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.850 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.884 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.902 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:00.903 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.057 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.093 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.093 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8774071B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.435 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.436 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and system for intercommunication between mobile terminal and WiMAX base station, and mobile terminal(String), 移动终端与WiMAX基站互通的方法、系统及移动终端(String), US8774071B2(String), A method for intercommunication between a mobile terminal and a WiMAX base station comprises: connecting the mobile terminal with a WiMAX wireless data card via an interface (S102); obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information (S104); and using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station (S106). A system and a mobile terminal are used to implement the method.(String), 一种移动终端与WiMAX基站互通的方法,包括:通过接口(S)将移动终端与WiMAX无线数据卡连接起来。 102 ); 获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡的逻辑连接(S 104 ); 并使用WiMAX无线数据卡实现与WiMAX基站(S 106 )。 一种系统和移动终端用于实现该方法。(String), US13/060648(String), 1230220800(Integer), US8774071B2(String), 1404748800(Integer), 1404748800(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 12(Integer), CN101123577A | CN1859442A | CN1964276A | US20070038764A1 | US20070115899A1 | US20070173283A1 | US20070238448A1 | US20070253339A1 | US20080113692A1 | US20090016246A1 | US20110242964A1 | WO2007078663A2(String), 7(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.471 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.472 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186003(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.619 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.620 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\8dcaebf05fcc40579147fb963f165a9e.png(String), 186003(Integer), 8dcaebf05fcc40579147fb963f165a9e.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.656 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and system for intercommunication between mobile terminal and WiMAX base station, and mobile terminal(String), 移动终端与WiMAX基站互通的方法、系统及移动终端(String), US8774071B2(String), A method for intercommunication between a mobile terminal and a WiMAX base station comprises: connecting the mobile terminal with a WiMAX wireless data card via an interface (S102); obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information (S104); and using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station (S106). A system and a mobile terminal are used to implement the method.(String), 一种移动终端与WiMAX基站互通的方法,包括:通过接口(S)将移动终端与WiMAX无线数据卡连接起来。 102 ); 获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡的逻辑连接(S 104 ); 并使用WiMAX无线数据卡实现与WiMAX基站(S 106 )。 一种系统和移动终端用于实现该方法。(String), US13/060648(String), 1230220800(Integer), US8774071B2(String), 1404748800(Integer), 1404748800(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 12(Integer), CN101123577A | CN1859442A | CN1964276A | US20070038764A1 | US20070115899A1 | US20070173283A1 | US20070238448A1 | US20070253339A1 | US20080113692A1 | US20090016246A1 | US20110242964A1 | WO2007078663A2(String), \20230420\8dcaebf05fcc40579147fb963f165a9e.png(String), 7(Integer), 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.709 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.709 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.709 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.743 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.743 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 1. A method for intercommunication between a mobile terminal and a World Interoperability for Microwave Access (WiMAX) base station, with the mobile terminal being a dual mode terminal which supports two network systems, comprising:connecting the mobile terminal with a WiMAX wireless data card via an interface;obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information; andusing the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station, wherein using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station comprises:the mobile terminal registering with the WiMAX base station through the WiMAX wireless data card, which comprises:the mobile terminal realizing at least one of the following operations through an encapsulated application program interface: network searching, network access, and network authentication; andthe mobile terminal sending to the WiMAX base station an access request for registration; andthe mobile terminal entering the mode of intercommunication with the WiMAX base station.(String), 1.一种移动终端与全球微波接入互通(WiMAX)基站互通的方法,该移动终端为支持两种网络系统的双模终端,包括:移动终端与WiMAX无线数据卡通过接口连接;获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡之间的逻辑连接;和利用WiMAX无线数据卡实现与WiMAX基站的互通,其中,利用WiMAX无线数据卡实现与WiMAX基站的互通包括:移动终端通过WiMAX无线数据卡向WiMAX基站注册,包括:移动终端通过封装的应用程序接口实现以下至少一种操作:网络搜索、网络接入、网络认证。和移动终端向WiMAX基站发送注册接入请求;和移动终端进入与WiMAX基站互通模式。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.743 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 2. The method according to claim 1, wherein the interface is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card.(String), 2.根据权利要求1所述的方法,其中接口为通用串行总线接口,WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。3、一种互通系统,用于实现移动终端与全球微波接入互通(WiMAX)基站的互通,包括:移动终端包括:接口模块,用于连接WiMAX无线数据卡与移动终端;连接管理模块,用于选择与WiMAX基站连接的移动终端;和设备管理模块,用于获取和/或配置WiMAX无线数据卡的配置信息,通过WiMAX无线数据卡与WiMAX基站进行互通;其中,移动终端通过WiMAX无线数据卡向WiMAX基站进行注册,其间:移动终端通过封装的应用程序接口实现以下操作中的至少一种:网络搜索、网络接入、网络认证。和移动终端用于向WiMAX基站发送注册接入请求;和其中,WiMAX无线数据卡通过移动终端的接口模块与移动终端连接;和其中,WiMAX基站用于通过WiMAX无线数据卡实现与移动终端的互通。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.743 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 3. An intercommunication system, configured to realize the intercommunication between a mobile terminal and a World Interoperability for Microwave Access (WiMAX) base station, comprising:the mobile terminal comprising:an interface module, configured to connect a WiMAX wireless data card with the mobile terminal;a connection managing module, configured to select the mobile terminal to be connected with the WiMAX base station; anda device managing module, configured to obtain and/or configure configuration information of the WiMAX wireless data card, and intercommunicate with the WiMAX base station through the WiMAX wireless data card;wherein the mobile terminal is operative to register with the WiMAX base station through the WiMAX wireless data card, during which:the mobile terminal is operative to realize at least one of the following operations through an encapsulated application program interface: network searching, network access, and network authentication; andthe mobile terminal is operative to send to the WiMAX base station an access request for registration; andwherein, the WiMAX wireless data card is connected with the mobile terminal through the interface module of the mobile terminal; andwherein the WiMAX base station is configured to realize the intercommunication with the mobile terminal through the WiMAX wireless data card.(String), 4.根据权利要求3所述的对讲系统,其中移动终端还包括:电源模块,用于为WiMAX无线数据卡供电。(String), 0(Integer), 2(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 4. The intercommunication system according to claim 3, wherein the mobile terminal further comprises:a power supply module, configured to supply power for the WiMAX wireless data card.(String), 5.根据权利要求3所述的对讲系统,其中接口模块为通用串行总线接口,WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 5. The intercommunication system according to claim 3, wherein the interface module is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card.(String), 6.根据权利要求3所述的对讲系统,其中连接管理模块,用于通过调用封装的应用程序接口执行以下操作中的至少一种:网络搜索、网络接入、网络断开、网络认证、频率范围配置、连接方式选择、搜索网络步长设置,认证选项的设置,以及切换选项的设置。(String), 1(Integer), 4(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 6. The intercommunication system according to claim 3, wherein the connection managing module is configured to execute at least one of the following operations through invoking the encapsulated application program interface: network searching, network access, network disconnection, network authentication, frequency range configuration, connection mode selection, setting of search net step length, setting of authentication options, and setting of handover options.(String), 7.根据权利要求3所述的对讲系统,其中设备管理模块,用于通过调用封装后的应用程序接口实现以下操作中的至少一种:移动联盟开通、固件更新管理、设备参数配置和获取。(String), 1(Integer), 5(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.744 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186003(Integer), 7. The intercommunication system according to claim 3, wherein the device managing module is configured to realize at least one of the following operations through invoking the encapsulated application program interface: mobile alliance opening, firmware updating management, and configuration and acquisition of device parameters.(String), 1(Integer), 6(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.923 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186003(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the communication field, in particular to a method, a system and a mobile terminal for intercommunication between a mobile terminal and a world interoperability for microwave access (WiMAX) base station. BACKGROUND OF THE INVENTION [0002]WiMAX is a wideband wireless metropolitan area network (WMAN) technology based on the 802.16 series standards of Institute for Electrical and Electronic Engineers (IEEE). [0003]At present, the dual mode mobile phone of global system for mobile communications (GSM)/wireless fidelity (WiFi) based on IEEE 802.1b standard can realize seamless handover between the GSM network and wireless local area network (WLAN), and support unlicensed mobile access (UMA) technology. Users can make up the defect that the indoor signal of mobile terminal such as mobile phone is weak. When network of the mobile phone is busy or the signal is bad, the mobile phone user can perform voice communication through the WiFi network. In practical application, the handover between the two networks is realized through the voice over IP (VoIP) technology, and the expense using this technology is comparatively low and the technology can provide convenience for the mobile phone and wide frequency wireless phone. In addition, the use of the VoIP technology can also realize the functions of browsing web page, sending and receiving e-mail, short messages and multimedia messages and so on. As long as the mobile phone is moved to the areas covered by the wireless wideband, the user can make a free call worldwide by a network phone mode. [0004]In the present network, there are some areas still not covered by the GSM/WiFi networks, or some with bad signals of the GSM/WiFi networks. Aiming at the above-mentioned situations, the mobile phone terminal can realize the communication through the WiMAX network. Therefore, how to realize the intercommunication between the GSM/WiFi dual mode mobile phone and the WiMAX base station is a problem needed to be solved at present. SUMMARY OF THE PRESENT INVENTION [0005]The present invention is put forward aiming at the intercommunication problem between a GSM/WiFi dual mode mobile phone and a WiMAX base station at present. For this reason, the present invention aims to provide an improved intercommunication scheme between a mobile terminal and the WiMAX base station to solve at least one of above-mentioned problems. [0006]In order to achieve the above-mentioned aim, a method for intercommunication between a mobile terminal and a WiMAX base station is provided according to one aspect of the present invention. [0007]In the method for intercommunication between the mobile terminal and the WiMAX base station according to the present invention, the mobile terminal is a dual mode terminal which supports two network systems except the WiMAX. The method comprises: connecting the mobile terminal with a WiMAX wireless data card via an interface; obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information; and using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station. [0008]Preferably, that using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station comprises: the mobile terminal registering with the WiMAX base station through the WiMAX wireless data card; and the mobile terminal entering the mode of intercommunication with the WiMAX base station. [0009]Preferably, the step of the mobile terminal registering with the WiMAX base station through the WiMAX wireless data card comprises: the mobile terminal realizing at least one of the following operations through an encapsulated application program interface: network searching, network access, and network authentication; and the mobile terminal sending to the WiMAX base station an access request for registration. [0010]Preferably, the interface is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card. [0011]In order to achieve the above-mentioned aim, a mobile terminal is provided according to another aspect of the present invention. [0012]The mobile terminal according to the present invention comprises: an interface module, configured to connect a WiMAX wireless data card with the mobile terminal; a connection managing module, configured to select the mobile terminal to be connected with a WiMAX base station; and a device managing module, configured to obtain and/or configure configuration information of the WiMAX wireless data card, and intercommunicate with the WiMAX base station through the WiMAX wireless data card. [0013]Preferably, the mobile terminal further comprises: a power supply module, configured to supply power for the WiMAX wireless data card. [0014]Preferably, the interface module is a universal serial bus interface, and the WiMAX wireless data card is a WiMAX universal serial bus wireless data card. [0015]Preferably, the connection managing module is configured to execute at least one of the following operations through invoking encapsulated application program interface: network searching, network access, network disconnection, network authentication, frequency range configuration, connection mode selection, setting of search net step length, setting of authentication options, and setting of handover options. [0016]Preferably, the device managing module is configured to realize at least one of the following operations through invoking encapsulated application program interface: mobile alliance opening, firmware updating management, and configuration and acquisition of device parameters. [0017]In order to achieve the above-mentioned aim, an intercommunication system is further provided according to another aspect of the present invention. [0018]The intercommunication system according to the present invention, which is configured to realize the intercommunication between a mobile terminal and a WiMAX base station, comprises the mobile terminal which is mentioned above. Furthermore, the intercommunication system further comprises: the WiMAX wireless data card, connected with the mobile terminal through the interface module of the mobile terminal; and the WiMAX base station, configured to realize the intercommunication with the mobile terminal through the WiMAX wireless data card. [0019]In virtue of the technical scheme of the present invention, on the basis of small improvement to the software and/or hardware of existing mobile phone terminal (namely, mobile terminal), the present invention realizes the intercommunication between the mobile phone terminal and the WiMAX base station through the WiMAX Universal Serial Bus (USB) wireless data card, solves the problem that the GSM/WiFi dual mode mobile phone can not intercommunicate with the WiMAX base station, improves the compatibility of the mobile phone, and enable user can experience the wideband data service brought by WiMAX technology. BRIEF DESCRIPTION OF THE DRAWINGS [0020]The drawings in the specification provide a further understanding to the present invention and constitute a part of the application. The exemplary embodiments of the present invention and the explanation thereof are given thereafter by way of illustration only, and thus are not limitative of the present invention, and wherein: [0021]FIG. 1 is a flowchart of a method for intercommunication between a mobile terminal and a WiMAX base station according to the embodiment of the present invention; [0022]FIG. 2 is a flowchart of implementation of the software system of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention; [0023]FIG. 3 is a structure diagram of a mobile terminal according to the embodiment of the present invention; [0024]FIG. 4 is a schematic diagram of the hardware system structure of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention; [0025]FIG. 5 is a schematic diagram of the software system architecture of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention; and [0026]FIG. 6 is a structure diagram of the intercommunication system according to the embodiment of the present invention. DETAILED DESCRIPTION [0027]General Description of Functions [0028]In the present invention, the GSM, WiFi, WiMAX multimode terminal, voice service and data service are integrated, a group of voice call continuity (VCC) service components on the basis of IP multimedia subsystem (IMS)/Fixed-Mobile Convergence (FMC) are developed on high and middle grade intelligent mobile phones, and a uniform modularization platform is provided on multimode mobile phone terminals of various platforms and different systems, which can be beared on various wireless communication protocol stacks such as GSM/General Packet Radio Service (GPRS), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Wideband Code Division Multiple Access (WCDMA) and so on, and can also be beared on wideband wireless access modules such as the WiFi, WiMAX and so on, which can meet the development requirement of the FMC. [0029]In the technical solution of the present invention, the mobile terminal is connected with the WiMAX wireless data card via an interface; configuration information of the WiMAX wireless data card is obtained, and the logic connection between the mobile terminal and the WiMAX wireless data card is fulfilled according to the configuration information; and the WiMAX wireless data card is used to fulfill the intercommunication with the WiMAX base station. [0030]The preferable embodiments of the present invention will be detailed hereinafter in connection with the drawings. What should be understood is that the preferable embodiments detailed hereafter are only given by way of illustration and explanation, and thus are not limitative of the present invention. [0031]In the description hereafter, for the purpose of explanation, a plurality of specific details are given to provide thorough comprehension to the present invention. Nevertheless, obviously, the present invention can also be realized without the specific details. In addition, without departing from the spirit and scope defined by the claims appended, the embodiments of the present invention hereafter can be inter-combined with the details in the embodiments. [0032]Method Embodiment [0033]A method for intercommunication between a mobile terminal and WiMAX base station is provided according to the embodiment of the present invention. As mentioned above, in the present embodiment, the mobile terminal is a dual mode terminal which supports two network systems except the WiMAX, e.g. GSM/WiFi dual mode mobile phone. FIG. 1 is a flowchart of the method for intercommunication between a mobile terminal and WiMAX base station according to the embodiment of the present invention. As shown in FIG. 1, the method comprises the steps as follows (step S102-step S106): [0034]Step S102, connecting the mobile terminal with a WiMAX wireless data card via an interface; wherein preferably, in the present embodiment of the present invention, the interface used is an USB interface, and the WiMAX wireless data card is a WiMAX USB wireless data card; and, the mobile terminal provides an independent power supply to the WiMAX wireless data card; [0035]Step S104, obtaining configuration information of the WiMAX wireless data card, and fulfilling the logic connection between the mobile terminal and the WiMAX wireless data card according to the configuration information; and [0036]Step S106, using the WiMAX wireless data card to fulfill the intercommunication with the WiMAX base station; wherein concretely, the mobile terminal registers with the WiMAX base station through the WiMAX wireless data card, and the mobile terminal enters the mode of intercommunication with the WiMAX base station after the registration. [0037]In the registering operation in step S106, the mobile terminal realizes at least one of the following operations through an encapsulated API: network searching, network access, and network authentication; and the mobile terminal sends to the WiMAX base station an access request for registration. [0038]In virtue of the embodiment, the wideband data service and the intercommunication of voice and data between the GSM/WiFi dual mode mobile phone and the WiMAX base station can be realized; and voice calling, the automatic handover, manual handover, and seamless handover among the modes such as WiFi/GSM/WiMAX and so on can be guaranteed. [0039]The above-mentioned technical solution will be detailed hereafter by taking the GSM/WiFi dual mode mobile phone as an example. FIG. 2 is a flowchart of implementation of the software system of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention. As shown in FIG. 2, the method comprises the steps as follows: [0040]Step S202, connecting GSM/WiFi dual mode mobile phone with the WiMAX USB wireless data card (corresponding to the step S102 in FIG. 1); [0041]Step S204, starting the device managing (DM) software, which is configured to control the information intercommunication between the WiMAX USB wireless data card and the OMA Server (namely, WiMAX base station) through sending instructions, and fulfilling the functions concerned by operators or users; wherein preferably, the DM mainly realizes OMA DM1.2, FUMO1.0 functions, and configuration and acquisition function of the device parameters (e.g. bootstrapping, provisioning, etc) (corresponding to the step S104 in FIG. 1); [0042]Step S206, selecting whether to connect with the WiMAX base station through the Connection Management (CM) software, wherein the CM realizes the functions of network searching, network access, network disconnection, network authentication and so on through invoking an encapsulated API, and can also realize the specific functions of frequency range configuration, connection mode selection (automatic mode or manual mode), setting of search net step length, setting of authentication options, and setting of handover options, and wherein if the selection result is yes, it executes step S208; and if the selection result is no, it executes step S212; [0043]Step S208, if selecting to connect with the WiMAX base station, then using the USB wireless data card to register the WiMAX network, and executing step S210; [0044]Step S210, the mobile phone entering the intercommunication mode with the WiMAX base station (corresponding to the step S106 in FIG. 1); [0045]Step S212, if selecting to connect with the GSM or WiFi network, then registering the GSM or WiFi network, and executing step S214; [0046]Step S214, the mobile phone entering the mode of intercommunication with the GSM or WiFi network. [0047]In virtue of the embodiment, in the remote area covered by the WiMAX base station, if the mobile phone can not search the GSM and WiFi network, the GSM/WiFi dual mode mobile phone according to the embodiment of the present invention can perform the data and voice services through the way of starting the WiMAX USB wireless data card to connect with the WiMAX base station, with the result of improving the ability of network coverage effectively. [0048]Device Embodiment [0049]A mobile terminal is provided according to the embodiment of the present invention. FIG. 3 is a structure diagram of the mobile terminal according to the embodiment of present invention. As shown in FIG. 3, the device comprises: an interface module 32, a connection managing module 34, and a device managing module 36. Each module will be detailed hereafter. [0050]Concretely, the interface module 32 is configured to connect a WiMAX wireless data card with the mobile terminal; wherein the interface module is a USB interface, and the WiMAX wireless data card is a WiMAX USB wireless data card. The connection managing module 34, connected with the interface module 32, is configured to select the mobile terminal to be connected with the WiMAX base station, and is further configured to execute at least one of the following operations through invoking an encapsulated application program interface: network searching, network access, network disconnection, network authentication, frequency range configuration, connection mode selection, setting of search net step length, setting of authentication options, and setting of handover options. The device managing module 36, connected with the interface module 32 and the connection managing module 34, is configured to obtain and/or configure configuration information of the WiMAX wireless data card, and intercommunicate with the WiMAX base station through the WiMAX wireless data card. Concretely, the device managing module realizes at least one of the following operations through invoking the encapsulated application program interface: Open Mobile Alliance DM1.2, updating management of firmware, and configuration and acquisition of device parameters. [0051]Preferably, the above-mentioned device can further comprise a power supply module (which is not shown in FIG. 3). The power supply module can be configured to supply power for the WiMAX wireless data card. [0052]In virtue of the embodiment, a mobile terminal which can intercommunicate with the WiMAX base station is provided to enable the user experience the wideband data service brought by WiMAX technology. [0053]The present invention will be detailed hereinafter with reference to the drawings and in connection with the embodiment of the intercommunication between the GSM/WiFi dual mode mobile phone (namely, mobile terminal) and the WiMAX base station. FIG. 4 is a schematic diagram of the hardware system structure of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention. As shown in FIG. 4, the hardware system structure comprises: a baseband processor 404, radio frequency part (including a Radio Frequency (RF) processor 406 and a radio frequency Power Amplifier (PA) 408), an internal memory 401, a display 402, a keyboard 403, a coprocessor 407 (including a loud speaker and a microphone) and so on. Additionally, the GSM/WiFi dual mode mobile phone further comprises other parts, such as a power supply module, a chord chip, a digital camera chip, an Mp3 chip, and an MPEG chip and so on (which are not shown in FIG. 4); wherein only one set of voice input device and voice output device is set in the mobile phone. [0054]The GSM/WiFi dual mode mobile phone is connected with the WiMAX USB wireless data card 405 through various interfaces which include, but are not limited to: USB, RS-232, Cardbus, Ethernet, and SDIO. As a data access device, the WiMAX USB wireless data card 405 preferably uses the serial data bus, which meets the USB2.0 criterion, to transmit data and realize the intercommunication between the WiMAX USB wireless data card and the GSM/WiFi dual mode mobile phone. The WiMAX USB wireless data card is provided with an independent power supply module, i.e., the mobile terminal, to supply power for the WiMAX wireless data card. [0055]In the above, the WiMAX USB wireless data card can realize the functions defined in the IEEE802.16 2005 protocol, specific interface (e.g. USB) drive function, chip enable bootstrap function (chip bootstrap is realized by the Bootloader program solidified on the chip of the WiMAX USB wireless data card, is configured to initialize the hardware of the WiMAX USB wireless data card, and establish the mapping of the internal memory space), and firmware download function and so on. The WiMAX USB wireless data card is in the form of firmware, and is downloaded from the mobile phone when the device is power on and started. In the terminal system, the data card is used as a data access device, the data card is provided with a physical interface which is connected with the mobile phone via the USB interface, and adopts the serial data bus, which meets the USB 2.0 criterion, to transmit data. [0056]Through adding a USB interface of the GSM/WiFi dual mode mobile phone, the embodiment improves the hardware design of the GSM/WiFi dual mode mobile phone, and provides hardware condition for the intercommunication between the GSM/WiFi dual mode mobile phone and the WiMAX base station. [0057]The hardware system structure of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station is detailed above. Hereafter, on the basis of the dual mode mobile phone as shown in FIG. 4, the software system architecture of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station is detailed. FIG. 5 is a schematic diagram of the software system architecture of the GSM/WiFi dual mode mobile phone which supports the intercommunication with the WiMAX base station according to the embodiment of the present invention. As shown in FIG. 5, the software architecture part mainly comprises a device (WiMAX USB wireless data card) side and a host (GSM/WiFi dual mode mobile phone) side. The structure of the software system architecture will be detailed hereafter. The software system architecture comprises: a USB input output (IO) drive 501, a GSM/WiFi protocol stack 502, a hardware drive 503, a system support software 504, an operating system 505, a Man-Machine Interface (MMI) frame 506, a basic application software 507, a Connection Management (CM) 508, a Device Management (DM) 509, and an encapsulated application program interface (API) 510. [0058]Concretely, the USB IO drive 501 belongs to the device side module, is configured to realize the functions defined in the IEEE802.16 3005 protocol, specific interface (e.g. USB) drive function, and chip enable bootstrap function and so on and in form of firmware, and is stored in the storage media of Flash/EEPROM and etc. of the device. [0059]As described hereafter, the term “storage media” means one or multiple kinds of devices for storing data, which include Read Only Memory (ROM), Random Access Memory (RAM), magnetic RAM, magnetic core memory, magnetic disc storage media, optical storage media, flash memory device and/or the other machine readable media for storing information. The term “machine readable media” includes but is not limited to: portable or fixed storing device, optical storing device, wireless channel, or the other media which can store, hold or load instructions and/or data. [0060]In the GSM/WiFi dual mode mobile phone, the GSM/WiFi protocol stack 502 is configured to realize the GSM/WiFi protocol. The hardware drive 503 is configured to realize the hardware drive of the mobile phone and the drive of the WiMAX USB wireless data card. Furthermore, in the present embodiment, the system support software 504 and the operating system 505 can adopt the operating system of Windows Mobile. The MMI frame 506 is realized by using the window mechanism of Windows Mobile. The basic application software 507 comprises the original call software, short message software, web page browsing software and the other application software of the GSM/WiFi dual mode mobile phone. The CM 508 and the DM 509 belong to the software application layer, and are configured to realize the setting of connection and instruction transmission between the WiMAX connection device and the WiMAX base station. The encapsulated API 510 is configured to provide interfaces for the CM and DM of the upper layer (software application layer), take the responsibility for the realization of the CM and DM functions, and communicate with the drive of the host through invoking the kernel function of the operating system 505. The host drive forwards the message to the WiMAX USB wireless data card through the bus. And then the WiMAX USB wireless data card makes corresponding operations according to the content of the message. [0061]In the realization process of the present embodiment, the CM 508 realizes the functions of network searching, network access, network disconnection, network authentication and so on through invoking the encapsulated API 510, can also realize the specific functions of frequency range configuration, connection mode selection (automatic or manual), setting of search net step length, setting of authentication options, and setting of handover options and so on; the DM 509 realizes the Open Mobile Alliance (OMA) DM1.2 function, Firmware Update Management Object (FUMO) 1.0 function, and device parameters (e.g. bootstrapping, automation configuration and so on) configuration and acquisition through invoking the encapsulated API 510. [0062]Through setting the GSM/WiFi dual mode mobile phone on the software, the embodiment provides software conditions for the realization of the voice and data intercommunication between the GSM/WiFi dual mode mobile phone and the WiMAX base station, and further lays a foundation for realizing the wideband data service, voice call service, IMS VoIP service and so on between the GSM/WiFi dual mode mobile phone and the WiMAX base station. [0063]What needs to be explained is that in the above-mentioned embodiments, the hardware, software, firmware, middleware, microcode, hardware description language or the combinations thereof can be used to realize the embodiments. When the hardware, software, firmware, middleware or microcode are used to realize the embodiment, the program code or code segments for executing necessary tasks can be stored in the machine readable media of the storage media. (A plurality of) processors can execute necessary tasks. The code segments can express any combination of process, function, subprogram, program, routine program, subroutine program, module, object, software package, cluster, or instruction, data structure, or program language. The code segment is coupled into another code segment or a hardware circuit through transmitting and/or receiving information, data, independent variable, or the memory contents. The information, independent variables, parameters, data and so on can be transferred, transmitted or sent in any suitable mode such as memorizer sharing, message passing, token passing, network transmission and so on. [0064]System Embodiment [0065]An intercommunication system is provided according to the embodiment of the present invention. The intercommunication system is configured to realize the intercommunication between the mobile terminal and the WiMAX base station. FIG. 6 is a structure diagram of the intercommunication system according to the embodiment of the present invention. As shown in FIG. 6, the system comprises the above mobile terminal 62 (preferably, the mobile terminal 62 can be the GSM/WiFi dual mode mobile phone based on the above-mentioned structure), and further comprises the WiMAX wireless data card 64 connected with the mobile terminal 62 through the interface module of the mobile terminal, and the WiMAX base station 66. [0066]Concretely, the WiMAX base station 66, connected with the WiMAX wireless data card 64, is configured to realize the intercommunication with the mobile terminal through the WiMAX wireless data card. Preferably, the mobile terminal 62 can be connected with the WiMAX wireless data card 64 through an interface; configuration information of the WiMAX wireless data card 64 is obtained, and the logic connection between the mobile terminal 62 and the WiMAX wireless data card 64 is fulfilled according to the configuration information; and the WiMAX wireless data card 64 is used to fulfill the intercommunication with the WiMAX base station 66, i.e., the mobile terminal 62 registers with the WiMAX base station 66 through the WiMAX wireless data card 64; and then the mobile terminal 62 enters the mode of intercommunication with the WiMAX base station 66. [0067]In virtue of the present embodiment, on the basis of minor improvement to the software and/or hardware of existing GSM/WiFi dual mode mobile phone, it realizes the intercommunication between the GSM/WiFi dual mode mobile phone terminal and the WiMAX base station through the WiMAX USB wireless data card, improves the compatibility of the mobile phone, and enables the user experience the wideband data service brought by WiMAX technology. [0068]Obviously, those skilled in the art shall understand that the above-mentioned modules and steps of the present invention can be realized by using general purpose calculating device, can be integrated in one calculating device or distributed on a network which consists of a plurality of calculating devices. Alternatively, the modules and the step of the present invention can be realized by using the executable program code of the calculating device. Consequently, the modules and the steps can be stored in the storage device and executed by the calculating device, or the modules and the steps are made into integrated circuit module respectively, or a plurality of modules or steps thereof are made into one integrated circuit module. In this way, the present invention is not restricted to any particular hardware and software combination. [0069]The descriptions above are only preferable embodiments of the present invention, which are not used to restrict the present invention. For those skilled in the art, the present invention may have various changes and variations. Any amendments, equivalent substitutions, improvements etc. within the spirit and principle of the present invention are all concluded in the scope of protection of the present invention.(String), 发明领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端与全球微波接入互通(WiMAX)基站互通的方法、系统及移动终端。 发明背景 [0002] WiMAX是基于电气和电子工程师协会(IEEE)的802.16系列标准的宽带无线城域网(WMAN)技术。 [0003] 目前,基于IEEE 802.1b标准的全球移动通信系统(GSM)/无线保真(WiFi)双模手机可实现GSM网络与无线局域网(WLAN)的无缝切换,并支持免授权移动 接入(UMA)技术。 用户可以弥补手机等移动终端室内信号弱的缺陷。 当手机网络繁忙或信号不好时,手机用户可以通过WiFi网络进行语音通话。 在实际应用中,两个网络之间的切换是通过网络电话(VoIP)技术实现的,使用该技术的费用较低,可以为手机和宽频无线电话提供方便。 此外,利用VoIP技术还可以实现浏览网页、收发电子邮件、短信和彩信等功能。 只要将手机移到无线宽带覆盖的地区,用户就可以通过网络电话方式拨打全球免费电话。 [0004] 在目前的网络中,还有一些区域还没有被GSM/WiFi网络覆盖,或者GSM/WiFi网络信号不好。 针对上述情况,手机终端可以通过WiMAX网络实现通信。 因此,如何实现GSM/WiFi双模手机与WiMAX基站的互通是目前需要解决的问题。 发明内容 [0005] 本发明是针对目前GSM/WiFi双模手机与WiMAX基站的互通问题而提出的。 为此,本发明旨在提供一种改进的移动终端与WiMAX基站之间的互通方案,以解决上述问题中的至少一个。 [0006] 为实现上述目的,根据本发明的一个方面,提供了一种移动终端与WiMAX基站互通的方法。 [0007] 本发明的移动终端与WiMAX基站互通的方法中,所述移动终端为双模终端,支持除WiMAX之外的两种网络制式。 该方法包括:移动终端与WiMAX无线数据卡通过接口连接; 获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡之间的逻辑连接; 利用WiMAX无线数据卡实现与WiMAX基站的互通。 [0008] 优选地,利用WiMAX无线数据卡实现与WiMAX基站的互通包括: 移动终端通过WiMAX无线数据卡向WiMAX基站注册; 移动终端进入与WiMAX基站互通模式。 [0009] 优选地,移动终端通过WiMAX无线数据卡向WiMAX基站注册的步骤包括:移动终端通过封装的应用程序接口实现以下操作中的至少一种:网络搜索、网络接入、网络认证。 移动终端向WiMAX基站发送注册接入请求。 [0010] 优选地,所述接口为通用串行总线接口,所述WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。 [0011]为实现上述目的,根据本发明的另一方面,提供了一种移动终端。 [0012] 本发明的移动终端包括: 接口模块,用于连接WiMAX无线数据卡与移动终端; 连接管理模块,用于选择移动终端与WiMAX基站连接; 设备管理模块,用于获取和/或配置WiMAX无线数据卡的配置信息,通过WiMAX无线数据卡与WiMAX基站进行互通。 [0013] 优选地,移动终端还包括: 电源模块,用于为WiMAX无线数据卡供电。 [0014] 优选地,所述接口模块为通用串行总线接口,所述WiMAX无线数据卡为WiMAX通用串行总线无线数据卡。 [0015] 优选地,连接管理模块用于通过调用封装的应用程序接口执行以下操作中的至少一种:网络搜索、网络接入、网络断开、网络认证、频率范围配置、连接方式选择、搜索网络步长设置。 ,认证选项的设置,以及切换选项的设置。 [0016] 优选地,所述设备管理模块用于通过调用封装的应用程序接口实现以下操作中的至少一种:移动联盟开通、固件更新管理、设备参数的配置和获取。 [0017] 为实现上述目的,根据本发明的另一方面,还提供了一种对讲系统。 [0018] 本发明的对讲系统,用于实现移动终端与WiMAX基站的互通,包括上述移动终端。 进一步地,所述对讲系统还包括: WiMAX无线数据卡,通过移动终端的接口模块与移动终端连接; WiMAX基站,用于通过WiMAX无线数据卡实现与移动终端的互通。 [0019] 利用本发明的技术方案,本发明在对现有手机终端(即移动终端)的软件和/或硬件进行小幅改进的基础上,实现了手机终端与WiMAX的互通。 基站通过WiMAX通用串行总线(USB)无线数据卡,解决了GSM/WiFi双模手机无法与WiMAX基站互通的问题,提高了手机的兼容性,让用户体验到 WiMAX技术带来的宽带数据服务。 附图的简要说明 [0020] 说明书中的附图提供对本发明的进一步理解,构成本申请的一部分。 以下给出本发明的示例性实施例及其解释仅是为了说明,而不是对本发明的限制,其中: [0021] 图1为本发明实施例的移动终端与WiMAX基站互通的方法流程图; [0022] 图2为本发明实施例的支持与WiMAX基站互通的GSM/WiFi双模手机软件系统的实现流程图; [0023] 图3为本发明实施例的移动终端的结构图; [0024] 图4为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的硬件系统结构示意图; [0025]图5为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的软件系统架构示意图; 和 [0026] 图6是根据本发明实施例的对讲系统的结构图。 详细说明 [0027] 功能概述 [0028] 本发明将GSM、WiFi、WiMAX多模终端、语音业务和数据业务融为一体,是一组基于IP多媒体子系统(IMS)/固定移动融合(FMC)的语音呼叫连续性(VCC)业务组件。 )在高中档智能手机上开发,为各平台、不同制式的多模手机终端提供统一的模块化平台,可承载GSM/General Packet Radio Service等多种无线通信协议栈( GPRS)、时分-同步码分多址(TD-SCDMA)、宽带码分多址(WCDMA)等,也可承载在WiFi、WiMAX等宽带无线接入模块上, 能够满足FMC的发展需求。 [0029] 本发明技术方案中,移动终端通过接口与WiMAX无线数据卡连接; 获取WiMAX无线数据卡的配置信息,根据配置信息实现移动终端与WiMAX无线数据卡之间的逻辑连接; WiMAX无线数据卡用于实现与WiMAX基站的互通。 [0030] 下面结合附图详细说明本发明的优选实施例。 应当理解的是,以下所详述的优选实施例仅用于举例说明,并不用于限制本发明。 [0031] 在下文的描述中,为了解释的目的,给出了多个具体细节以提供对本发明的透彻理解。 尽管如此,显然,本发明也可以在没有具体细节的情况下实现。 此外,在不脱离所附权利要求所界定的精神和范围的情况下,本发明的实施例可以与实施例中的细节相互组合。 [0032] 方法实施例 [0033] 本发明实施例提供了一种移动终端与WiMAX基站互通的方法。 如前所述,在本实施例中,移动终端为双模终端,支持除WiMAX之外的两种网络制式,例如移动终端。 GSM/WiFi双模手机。 图1为本发明实施例的移动终端与WiMAX基站互通方法的流程图。 如图1所示,该方法包括以下步骤(步骤S 102 -脚步 106 ): [0034] 脚步 102 、移动终端与WiMAX无线数据卡通过接口连接; 其中,优选地,本发明实施例中,所使用的接口为USB接口,所述WiMAX无线数据卡为WiMAX USB无线数据卡。 移动终端为WiMAX无线数据卡提供独立供电。 [0035] 脚步 104 、获取WiMAX无线数据卡的配置信息,根据配置信息完成移动终端与WiMAX无线数据卡之间的逻辑连接; 和 [0036] 脚步 106 、利用WiMAX无线数据卡实现与WiMAX基站的互通; 其中,具体地,移动终端通过WiMAX无线数据卡向WiMAX基站注册,注册后移动终端进入与WiMAX基站互通的模式。 [0037] 在步骤S的注册操作中 106,移动终端通过封装的API实现以下操作中的至少一种:网络搜索、网络访问、网络认证; 移动终端向WiMAX基站发送注册接入请求。 [0038] 通过本实施例,可以实现GSM/WiFi双模手机与WiMAX基站之间的宽带数据业务和语音数据互通。 语音通话,保证WiFi/GSM/WiMAX等模式间的自动切换、手动切换、无缝切换。 [0039] 下面以GSM/WiFi双模手机为例对上述技术方案进行详细说明。 图2为本发明实施例的支持与WiMAX基站互通的GSM/WiFi双模手机软件系统的实现流程图。 如图2所示,该方法包括以下步骤: [0040] 脚步 202 ,用WiMAX USB无线数据卡连接GSM/WiFi双模手机(对应步骤S 102 在图 1 中); [0041] 脚步 204 、启动设备管理(DM)软件,用于通过发送指令控制WiMAX USB无线数据卡与OMA Server(即WiMAX基站)之间的信息互通,实现运营商或用户关心的功能; 其中优选地,DM主要实现OMA DM1.2、FUMO1.0功能,以及设备参数的配置和获取功能(如bootstrapping、provisioning等)(对应步骤S 104 在图 1 中); [0042] 脚步 206 ,通过连接管理(CM)软件选择是否与WiMAX基站连接,CM通过调用封装的API实现网络搜索、网络接入、网络断开、网络认证等功能,也可以实现 频率范围配置、连接模式选择(自动模式或手动模式)、搜索网步长设置、认证选项设置、切换选项设置的具体功能,如果选择结果为是,则执行步骤S 208 ; 如果选择结果为否,则执行步骤S 212 ; [0043] 脚步 208 ,如果选择连接WiMAX基站,则使用USB无线数据卡注册WiMAX网络,执行步骤S 210 ; [0044] 脚步 210 ,手机进入与WiMAX基站互通模式(对应步骤S 106 在图 1 中); [0045] 脚步 212 ,如果选择连接GSM或WiFi网络,则注册GSM或WiFi网络,执行步骤S 214 ; [0046] 脚步 214 ,手机进入与GSM或WiFi网络互通模式。 [0047] 通过本实施例,在WiMAX基站覆盖的偏远地区,如果手机搜索不到GSM和WiFi网络,本发明实施例的GSM/WiFi双模手机可以进行数据传输。 和语音业务通过启动WiMAX USB无线数据卡与WiMAX基站连接的方式,有效提高网络覆盖能力。 [0048] 装置实施例 [0049] 根据本发明实施例,提供了一种移动终端。 图3是根据本发明实施例的移动终端的结构图。 如图3所示,该装置包括:接口模块 32 , 一个连接管理模块 34 , 和一个设备管理模块 36 . 下面将详细介绍每个模块。 [0050] 具体来说,接口模块 32 用于与移动终端连接WiMAX无线数据卡; 其中,接口模块为USB接口,WiMAX无线数据卡为WiMAX USB无线数据卡。 连接管理模块 34 , 与接口模块相连 32,用于选择与WiMAX基站连接的移动终端,还用于通过调用封装的应用程序接口执行以下至少一种操作:网络搜索、网络接入、网络断开、网络认证、 频率范围配置、连接方式选择、搜索网步长设置、认证选项设置、切换选项设置。 设备管理模块 36 , 与接口模块相连 32 和连接管理模块 34 ,用于获取和/或配置WiMAX无线数据卡的配置信息,通过WiMAX无线数据卡与WiMAX基站互通。 具体的,设备管理模块通过调用封装后的应用程序接口实现以下操作中的至少一种:打开移动联盟DM1.2、更新固件管理、配置和获取设备参数。 [0051] 优选地,上述装置还可以包括电源模块(图3中未示出)。 供电模块可以配置为WiMAX无线数据卡供电。 [0052] 通过本实施例,提供了一种能够与WiMAX基站互通的移动终端,使用户能够体验到WiMAX技术带来的宽带数据服务。 [0053] 下面结合附图,结合GSM/WiFi双模手机(即移动终端)与WiMAX基站互通的实施例,对本发明进行详细说明。 图4为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的硬件系统结构示意图。 如图4所示,硬件系统结构包括:基带处理器 404 ,射频部分(包括射频(RF)处理器 406 和射频功率放大器 (PA) 408 ), 内部存储器 401 , 一个显示器 402 , 键盘 403 , 一个协处理器 407 (包括扬声器和麦克风)等。 此外,GSM/WiFi双模手机还包括电源模块、和弦芯片、数码相机芯片、Mp3芯片、MPEG芯片等其他部分(图4中未显示) ); 其中,手机中只设置了一套语音输入设备和语音输出设备。 [0054] GSM/WiFi双模手机连接WiMAX USB无线数据卡 405 通过各种接口,包括但不限于:USB、RS-232、Cardbus、以太网和 SDIO。 WiMAX USB无线数据卡作为数据存取设备 405 优选采用符合USB2.0标准的串行数据总线传输数据,实现WiMAX USB无线数据卡与GSM/WiFi双模手机的互通。 WiMAX USB无线数据卡设有独立的供电模块即移动终端,为WiMAX无线数据卡供电。 [0055] 以上,WiMAX USB无线数据卡可以实现IEEE802.16 2005协议定义的功能,特定接口(如USB)驱动功能,芯片使能自举功能(芯片自举是通过固化在芯片上的Bootloader程序实现的) WiMAX USB无线数据卡,用于初始化WiMAX USB无线数据卡的硬件,建立内存空间的映射),以及固件下载功能等。 WiMAX USB无线数据卡以固件形式存在,在设备上电启动时从手机下载。 在终端系统中,数据卡作为数据访问设备,数据卡带有物理接口,通过USB接口与手机连接,采用串行数据总线,符合USB 2.0规范 , 传输数据。 [0056]本实施例通过增加GSM/WiFi双模手机的USB接口,改进了GSM/WiFi双模手机的硬件设计,为GSM/WiFi双模手机与WiMAX互通提供了硬件条件。 基站。 [0057] 上面详述了支持与WiMAX基站互通的GSM/WiFi双模手机的硬件系统结构。 下面以图4所示的双模手机为基础,详细说明支持与WiMAX基站互通的GSM/WiFi双模手机的软件系统架构。 图5为本发明实施例支持与WiMAX基站互通的GSM/WiFi双模手机的软件系统架构示意图。 如图5所示,软件架构部分主要包括设备(WiMAX USB无线数据卡)端和主机(GSM/WiFi双模手机)端。 下面将详细介绍软件系统架构的结构。 软件系统架构包括:USB输入输出(IO)驱动 501 , 一个 GSM/WiFi 协议栈 502 , 一个硬件驱动器 503 , 系统支持软件 504 , 一个操作系统 505 , 人机界面 (MMI) 框架 506 , 基础应用软件 507 , 连接管理 (CM) 508 , 设备管理 (DM) 509 , 以及封装的应用程序接口 (API) 510 . [0058] 具体来说,USB IO 驱动器 501 属于设备端模块,用于以固件的形式实现IEEE802.16 3005协议定义的功能、特定接口(如USB)驱动功能、芯片使能bootstrap功能等,存放在 设备的Flash/EEPROM等存储介质。 [0059] 下文所述,“存储介质”是指一种或多种用于存储数据的设备,包括只读存储器(ROM)、随机存取存储器(RAM)、磁RAM、磁芯存储器、磁盘存储介质、光 存储介质、闪存设备和/或其他用于存储信息的机器可读介质。 术语“机器可读介质”包括但不限于:便携式或固定存储设备、光存储设备、无线信道或其他可以存储、保存或加载指令和/或数据的介质。 [0060] GSM/WiFi双模手机中,GSM/WiFi协议栈 502 配置实现GSM/WiFi协议。 硬件驱动 503 配置实现手机的硬件驱动和WiMAX USB无线数据卡的驱动。 此外,在本实施例中,系统支持软件 504 和操作系统 505 可采用Windows Mobile操作系统。 人机界面框架 506 是利用Windows Mobile的窗口机制实现的。 基础应用软件 507 包括GSM/WiFi双模手机原有的通话软件、短信软件、网页浏览软件和其他应用软件。 CM 508 和DM 509 属于软件应用层,用于实现WiMAX连接设备与WiMAX基站之间的连接设置和指令传输。 封装的API 510 用于为上层(软件应用层)的CM和DM提供接口,负责CM和DM功能的实现,通过调用操作系统的内核函数与宿主机的驱动进行通信 505 . 主机驱动通过总线将报文转发给WiMAX USB无线数据卡。 然后WiMAX USB无线数据卡根据报文内容进行相应的操作。 [0061] 在本实施例的实现过程中,CM 508 通过调用封装的API实现网络搜索、网络访问、网络断开、网络认证等功能 510,还可以实现频率范围配置、连接方式选择(自动或手动)、搜索网步长设置、认证选项设置、切换选项设置等具体功能; DM 509 通过调用封装的API实现Open Mobile Alliance (OMA) DM1.2功能、Firmware Update Management Object (FUMO) 1.0功能,以及设备参数(如bootstrapping、automation configuration等)的配置和获取 510 . [0062] 本实施例通过在软件上对GSM/WiFi双模手机进行设置,为实现GSM/WiFi双模手机与WiMAX基站之间的语音和数据互通提供了软件条件,进一步为实现 GSM/WiFi双模手机与WiMAX基站之间的宽带数据业务、语音通话业务、IMS VoIP业务等。 [0063] 需要说明的是,在上述实施例中,可以采用硬件、软件、固件、中间件、微码、硬件描述语言或其组合来实现本实施例。 当采用硬件、软件、固件、中间件或微代码来实现本实施例时,执行必要任务的程序代码或代码段可以存储在存储介质中的机器可读介质中。 (多个)处理器可以执行必要的任务。 代码段可以表示过程、函数、子程序、程序、例程、子例程、模块、对象、软件包、簇或指令、数据结构或程序语言的任意组合。 代码段通过发送和/或接收信息、数据、自变量或存储器内容耦合到另一个代码段或硬件电路。 信息、自变量、参数、数据等可以以存储器共享、消息传递、令牌传递、网络传输等任何合适的方式传输、传输或发送。 [0064] 系统实施例 [0065] 根据本发明实施例,提供了一种对讲系统。 互通系统用于实现移动终端与WiMAX基站之间的互通。 图6是根据本发明实施例的对讲系统的结构图。 如图6所示,该系统包括上述移动终端 62 (最好是移动端 62 可以是基于上述结构的GSM/WiFi双模手机),还包括WiMAX无线数据卡 64 与移动端连接 62 通过移动终端接口模块,与WiMAX基站 66 . [0066] 具体来说,WiMAX基站 66 , 连接WiMAX无线数据卡 64 ,用于通过WiMAX无线数据卡实现与移动终端的互通。 优选地,移动终端 62 可连接WiMAX无线数据卡 64 通过接口; WiMAX无线数据卡配置信息 64 得到,移动端之间的逻辑连接 62 和WiMAX无线数据卡 64 根据配置信息完成; 和WiMAX无线数据卡 64 用于实现与WiMAX基站的互通 66 ,即移动端 62 向 WiMAX 基站注册 66 通过WiMAX无线数据卡 64 ; 然后是移动端 62 进入与WiMAX基站互通模式 66 . [0067] 本实施例在对现有GSM/WiFi双模手机的软件和/或硬件进行细微改进的基础上,通过以下方式实现GSM/WiFi双模手机终端与WiMAX基站的互通。 WiMAX USB无线数据卡,提高了手机的兼容性,让用户体验到WiMAX技术带来的宽带数据服务。 [0068] 显然,本领域的技术人员应该理解,本发明的上述模块和步骤可以使用通用计算装置来实现,可以集成在一个计算装置中,也可以分布在由多个计算装置组成的网络上。 设备。 可选地,本发明的模块和步骤可以通过计算装置的可执行程序代码来实现。 因此,模块和步骤可以存储在存储装置中并由计算装置执行,或者模块和步骤分别做成集成电路模块,或者多个模块或步骤做成一个集成电路模块。 . 这样,本发明不限于任何特定的硬件和软件组合。 [0069] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,本发明可以有各种更改和变化。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.935 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.935 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.959 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:01.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101345926A(String), EP2323280A1(String), EP2323280A4(String), US20110158217A1(String), US8774071B2(String), WO2010022575A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.012 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.013 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.032 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.033 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.033 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 226(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.057 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.121 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.122 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101345926A(String), EP2323280A1(String), EP2323280A4(String), US20110158217A1(String), US8774071B2(String), WO2010022575A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.139 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8774071B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.174 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101345926A(String), EP2323280A1(String), EP2323280A4(String), US20110158217A1(String), US8774071B2(String), WO2010022575A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.193 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271675(Integer), CN101345926A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271675(Integer), EP2323280A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.267 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271675(Integer), EP2323280A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.301 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271675(Integer), US20110158217A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.312 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.313 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.336 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.336 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.336 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271675(Integer), US8774071B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.350 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.351 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 103(Integer), 1(Integer), 0(Integer), 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.356 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.371 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271675(Integer), WO2010022575A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8774071B2(String), US8774071B2(String), 1404748800(Integer), 271675(Integer), 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.492 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.526 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186003(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.560 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186003(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.596 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.629 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186003(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.664 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.665 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 186003(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.707 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.707 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.707 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.740 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.741 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.811 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.812 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.829 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:02.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186003(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.021 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20170118436A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US20170118436A1(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择在外部显示设备上显示的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US15/386556(String), 1482249600(Integer), US20170118436A1(String), 1493222400(Integer), 美国(String), 2(Integer), KR(String), 9(Integer), 5(Integer), US20120017237A1 | US20130040623A1 | US20130041938A1 | US20130103446A1 | US8112371B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186004(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\db0b70e3c1824974aaa6a12eede400a2.png(String), 186004(Integer), db0b70e3c1824974aaa6a12eede400a2.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.585 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for displaying information, method and display device for providing information, and method and mobile terminal for generating control signal(String), 显示信息的方法和移动终端、提供信息的方法和显示装置、以及产生控制信号的方法和移动终端(String), US20170118436A1(String), A method in which a mobile terminal displays information is provided. The method includes: transmitting, to an external display device, a first signal for selecting an object displayed on the external display device based on a first input of a user through the mobile terminal; transmitting, to the external display device, a second signal for requesting additional information corresponding to the selected object based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device.(String), 提供了一种移动终端显示信息的方法。 该方法包括: 向外部显示设备发送用于基于用户通过移动终端的第一输入选择在外部显示设备上显示的对象的第一信号; 基于用户通过移动终端的第二输入,向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。(String), US15/386556(String), 1482249600(Integer), US20170118436A1(String), 1493222400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 9(Integer), 5(Integer), US20120017237A1 | US20130040623A1 | US20130041938A1 | US20130103446A1 | US8112371B1(String), \20230420\db0b70e3c1824974aaa6a12eede400a2.png(String), 20(Integer), 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 1. A mobile device comprising:a display;a communication interface; anda processor configured to:control the communication interface to transmit, to an external display device, a signal for selecting an object from among a plurality of objects based on a first input of a user through the mobile device;control the communication interface to receive additional information corresponding to the object;control the display to display information related to the object based on the additional information, andcontrol the communication interface to request a content corresponding to the information related to the object; andcontrol the communication interface to receive the content corresponding to the information.(String), 1.移动设备包括:显示器;通信接口;和处理器配置为:基于用户通过移动设备的第一输入,控制通信接口向外部显示设备发送用于从多个对象中选择对象的信号;控制通信接口接收对象对应的附加信息;基于附加信息控制显示器显示与对象相关的信息,以及控制通信接口请求与对象相关的信息对应的内容;和控制通信接口接收信息对应的内容。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 2. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to request, to the external display device, the additional information corresponding to the object based on a second input of the user through the mobile device, andthe additional information including the information related to the object.(String), 2.如权利要求1所述的移动设备,其中处理器还被配置为基于用户通过移动设备的第二输入控制通信接口向外部显示设备请求与对象对应的附加信息,以及附加信息包括与对象相关的信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 3. The mobile device of claim 1, wherein the processor is further configured to control the mobile device to convert the signal for selecting the object according to a control protocol of the external display device.(String), 3.如权利要求1所述的移动设备,其中处理器还用于控制移动设备根据外部显示设备的控制协议转换用于选择对象的信号。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 4. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to transmit a signal for controlling a movement of a selection region for selecting the object from among the plurality of objects displayed on the external display device.(String), 4.如权利要求1所述的移动设备,其中处理器还被配置为控制通信接口发送用于控制选择区域的移动的信号,该选择区域用于从显示在外部显示设备上的多个对象中选择对象。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 5. The mobile device of claim 4, wherein the processor is further configured to control the communication interface to transmit a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on a input of the user.(String), 5.如权利要求4所述的移动设备,其中处理器还被配置为控制通信接口发送用于控制选择区域的移动方向、选择区域的移动速度和显示在外部显示器的屏幕上的对象的数量中的至少一个的信号设备基于用户的输入。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 6. The mobile device of claim 4, wherein the processor is further configured to control the display to display thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 6.如权利要求4所述的移动设备,其中处理器还被配置为在请求附加信息之前控制显示器显示选择区域所在的对象对应的缩略图信息。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.674 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 7. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to receive link information as the additional information from the external display device and to receive the content from a server based on the received link information.(String), 7.如权利要求1所述的移动设备,其中处理器还被配置为控制通信接口从外部显示设备接收链接信息作为附加信息,并基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 8. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to request the content based on a third input of the user through the mobile device.(String), 8.如权利要求1所述的移动设备,其中处理器还被配置为基于用户通过移动设备的第三输入来控制通信接口请求内容。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 9. The mobile device of claim 1, wherein the processor is further configured to control the communication interface to request control authorization from the external display device and receive a control authorization acceptance message from the external display device prior to the transmitting of the signal for selecting the object.(String), 9.如权利要求1所述的移动设备,其中处理器还被配置为在发送用于选择对象的信号之前,控制通信接口向外部显示设备请求控制授权并从外部显示设备接收控制授权接受消息。(String), 1(Integer), 8(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 10. The mobile device of claim 1, wherein the plurality of objects comprise at least one from among an icon, a link, a picture, a text, and an index item11. The mobile device of claim 1, wherein the content comprise at least one from among a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG).(String), 10.如权利要求1所述的移动设备,其中多个对象包括图标、链接、图片、文本和索引项中的至少一个11.如权利要求1所述的移动设备,其中内容包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。(String), 1(Integer), 9(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 12. The mobile device of claim 1, wherein the additional information comprises at least one from among preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information.(String), 12.如权利要求1所述的移动设备,其中附加信息包括预览信息、试听信息、应用信息、用户评论信息、更新信息、报刊文章信息、商品信息、电影信息、游戏信息、广告图片信息、专辑信息中的至少一种。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 13. The mobile device of claim 1, wherein the processor is further configured to control the mobile device todetermine an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generate a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generate a signal for controlling the content displayed on the mobile device based on the user input.(String), 13.如权利要求1所述的移动设备,其中处理器还被配置为控制移动设备以确定移动设备的操作模式;和响应于确定操作模式是第一模式,基于用户输入产生用于控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,产生用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 14. A method in which a mobile device displays information, the method comprising:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects based on a first input of a user through the mobile device;receiving additional information corresponding to the object;displaying information related to the object based on the additional information;requesting a content corresponding to the information related to the object; andreceiving the content corresponding to the information.(String), 14.一种方法其中移动设备显示信息,该方法包括:基于用户通过移动设备的第一输入,向外部显示设备发送用于从多个对象中选择对象的信号;接收对应于对象的附加信息;基于附加信息显示与对象相关的信息;请求与对象相关的信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 12(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 15. The method of claim 14, wherein the transmitting the signal for selecting the object comprises transmitting a signal for controlling a movement of a selection region for selecting the object from among the plurality of objects displayed on the external display device.(String), 15.如权利要求14所述的方法,其中发送用于选择对象的信号包括发送用于控制选择区域的移动的信号,该选择区域用于从显示在外部显示设备上的多个对象中选择对象。(String), 1(Integer), 13(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.675 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 16. The method of claim 15, wherein the transmitting the signal for controlling the movement of the selection region comprises transmitting a signal for controlling at least one from among a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on a input of the user.(String), 16.如权利要求15所述的方法,其中发送用于控制选择区域的移动的信号包括发送用于控制选择区域的移动方向、选择区域的移动速度和显示在选择区域的屏幕上的对象的数量中的至少一项的信号基于用户输入的外部显示设备。(String), 1(Integer), 14(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 17. The method of claim 15, further comprising displaying thumbnail information corresponding of the object in which the selection region is disposed prior to the requesting of the additional information.(String), 17.如权利要求15所述的方法,还包括在请求附加信息之前,显示选择区域所在的对象对应的缩略图信息。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 18. The method of claim 14, wherein the receiving the additional information comprises receiving link information from the external display device and,wherein the receiving the content comprises receiving the content from a server based on the received link information.(String), 18.如权利要求14所述的方法,其中接收附加信息包括从外部显示设备接收链接信息,并且,其中,接收内容包括基于接收到的链接信息从服务器接收内容。(String), 1(Integer), 16(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 19. The method of claim 14, further comprising:determining an operation mode of the mobile device; andin response to determining the operation mode is a first mode, generating a first signal for controlling the external display device based on a user input, and, in response to determining the operation mode is a second mode, generating a signal for controlling the content displayed on the mobile device based on the user input.(String), 19.如权利要求14所述的方法,还包括:确定移动设备的操作模式;和响应于确定操作模式是第一模式,基于用户输入生成用于控制外部显示设备的第一信号,并且响应于确定操作模式是第二模式,生成用于控制显示的内容的信号在基于用户输入的移动设备上。(String), 1(Integer), 17(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:03.676 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186004(Integer), 20. A non-transitory computer-readable recording medium having recorded thereon a program for executing a method in which a mobile device displays information,wherein the method comprising:transmitting, to an external display device, a signal for selecting an object from among a plurality of objects based on a first input of a user through the mobile device;receiving additional information corresponding to the object;displaying information related to the object based on the additional information;requesting a content corresponding to the information related to the object; andreceiving the content corresponding to the information.(String), 20.一种非暂时性计算机可读记录介质有在其上记录用于执行移动设备显示信息的方法的程序,其中,所述方法包括:基于用户通过移动设备的第一输入,向外部显示设备发送用于从多个对象中选择对象的信号;接收对应于对象的附加信息;基于附加信息显示与对象相关的信息;请求与对象相关的信息对应的内容;和接收信息对应的内容。(String), 0(Integer), 18(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.036 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.037 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186004(Integer), CROSS-REFERENCE TO RELATED PATENT APPLICATION [0001]This application is a continuation application of U.S. patent application Ser. No. 13/950,507, filed on Jul. 25, 2013, which claims priority from Korean Patent Application No. 10-2012-0081434, filed on Jul. 25, 2012, in the Korean Intellectual Property Office, the disclosures of which are incorporated herein in its entirety by reference. BACKGROUND [0002]1. Field [0003]Exemplary embodiments relate to a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object, a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal, and a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0004]2. Description of the Related Art [0005]A smart television (TV) is a multifunctional TV capable of utilizing various functions such as web surfing, video on demand (VOD) watching, a social networking service (SNS), a game, etc. by combining a TV and an Internet access function and installing various applications. [0006]One characteristic of the smart TV is that a user and the TV can transmit and receive information from each other. This is a difference between the smart TV and an existing TV that merely transfers information unilaterally. Thus, the smart TV is also referred to as an interactive TV. [0007]However, it is very inconvenient for the user to use the various functions of the smart TV by using a standard remote controller. In particular, when the user browses or downloads contents, the user needs to manipulate the remote controller through several steps. [0008]Therefore, a control device or system for allowing the user to easily control the smart TV is needed. SUMMARY [0009]Exemplary embodiments provide a method and mobile terminal for displaying information by selecting an object displayed on an external display device based on an input of the mobile terminal and obtaining and displaying additional information corresponding to the selected object. [0010]Exemplary embodiments also provide a method and display device for providing information by selecting an object based on an input of a mobile terminal and providing additional information regarding the selected object to the mobile terminal. [0011]Exemplary embodiments also provide a method and mobile terminal for generating a control signal by changing a received user input to the control signal based on an operating mode of the mobile terminal. [0012]According to an aspect of an exemplary embodiment, there is provided a method in which a mobile terminal displays information, the method including: transmitting a first signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; transmitting a second signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0013]The transmitting of the first signal for selecting the object may include: converting the signal for selecting the object according to a control protocol of the external display device. [0014]The transmitting of the first signal for selecting the object may include: transmitting a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0015]The transmitting of the signal for controlling the movement of the selection region may include: transmitting a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen of the external display device based on the first input. [0016]The transmitting of the first signal for selecting the object may include: displaying thumbnail information of contents corresponding to the object on the screen of the mobile terminal. [0017]The thumbnail information may include at least one of an image of the contents corresponding to the object, a title of the contents, and a type of the contents. [0018]The transmitting of the first signal for selecting the object may include: displaying a movement direction of the mobile terminal on the screen according to the first input. [0019]The first input and the second input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0020]The first input may include a three-dimensional (3D) motion input for moving the mobile terminal in a 3D direction, wherein the second input includes a rotational motion input for rotating the mobile terminal by more than a predetermined angle. [0021]The transmitting of the second signal for requesting additional information may include: receiving the additional information from the display device. [0022]The transmitting of the second signal for requesting additional information may include: receiving link information of the additional information from the external display device based on the second input; and receiving the additional information from a server based on the received link information. [0023]The transmitting of the first signal for selecting the object to the display device may include: requesting control authorization from the external display device; and receiving a control authorization acceptance message from the external display device. [0024]The contents may include at least one of a still image, a moving image, an application, music, a web page, and an electronic program guide (EPG). [0025]The additional information may include at least one of preview information, prelistening information, application information, user review information, update information, newspaper article information, goods information, movie information, game information, advertisement image information, and album information. [0026]The method may further include: controlling the additional information displayed on the screen of the mobile terminal based on a third input of the user through the mobile terminal. [0027]The controlling of the additional information may include: controlling at least one of displaying of the additional information, playing of the additional information, and changing to previous additional information or next additional information based on the third input of the user through the mobile terminal. [0028]The method may further include: obtaining contents corresponding to the additional information displayed on the screen of the mobile terminal. [0029]According to an aspect of another exemplary embodiment, there is provided a method in which a display device provides information to a mobile terminal, the method including: selecting an object displayed on the display device by receiving a first input of a user through the mobile terminal; and transmitting additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal. [0030]The transmitting may include: extracting the additional information from contents corresponding to the selected object. [0031]The selecting of the object may include: receiving a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal; and moving the selection region according to the control signal. [0032]The selecting of the object may include: converting the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0033]The receiving may include: receiving the control signal for controlling the movement of the selection region from each of a plurality of mobile terminals. [0034]The method may further include: sensing at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0035]The selecting of the object may include: controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0036]The selecting of the object may include: transmitting thumbnail information of contents corresponding to the object to the mobile terminal. [0037]The transmitting of the additional information to the mobile terminal may include: transmitting link information of the additional information to the mobile terminal. [0038]The terminal may further include: receiving a request for transmission of contents corresponding to the selected object from the mobile terminal; and transmitting the contents corresponding to the selected object to the mobile terminal. [0039]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a communication unit which is configured to transmit a signal for selecting an object displayed on an external display device to the external display device based on a first input of a user through the mobile terminal; an additional information obtaining unit which is configured to transmit a signal for requesting additional information corresponding to the selected object to the external display device based on a second input of the user through the mobile terminal; a display which is configured to display the additional information received from the external display device; and a controller which is configured to control the communication unit, the additional information obtaining unit, and the display unit. [0040]The controller may convert the signal for selecting the object according to a control protocol of the external display device. [0041]The communication unit may transmit a signal for controlling a movement of a selection region for selecting the object displayed on the external display device. [0042]The communication unit may transmit a signal for controlling at least one of a movement direction of the selection region, a movement speed of the selection region, and the number of objects displayed on a screen of the external display device based on the first input. [0043]The display may display thumbnail information of contents corresponding to the object on a screen of the mobile terminal. [0044]The additional information obtaining unit may receive the additional information from the external display device. [0045]The communication unit may receive link information of the additional information from the external display device based on the second input, and wherein the additional information obtaining unit receives the additional information from a server based on the received link information. [0046]The controller may control the additional information displayed on the mobile terminal based on a third input of the user through the mobile terminal. [0047]The mobile terminal may further include: a contents obtaining unit which is configured to obtain content corresponding to the additional information displayed on the mobile terminal. [0048]According to an aspect of an exemplary embodiment, there is provided a display device including: a selection unit which is configured to select an object displayed on the display device based on a first input of a user through a mobile terminal; a communication unit which is configured to transmit additional information corresponding to the selected object to the mobile terminal by receiving a second input of the user through the mobile terminal, and a controller which is configured to control the selection unit and the communication unit. [0049]The controller may extract the additional information from contents corresponding to the selected object. [0050]The selection unit may receive a control signal for controlling a movement of a selection region for selecting the object from the mobile terminal and move the selection region according to the received control signal. [0051]The controller may convert the received first input to a control signal for controlling a movement of a selection region according to a control protocol of the display device. [0052]The display device may further include: a sensor which is configured to sense at least one of the first input of the user through the mobile terminal and the second input of the user through the mobile terminal. [0053]The controller may control at least one of a movement direction of the selection region, a movement speed of the selection region, and a number of objects displayed on a screen based on the first input of the user through the mobile terminal. [0054]The communication unit may transmit link information of the additional information to the mobile terminal. [0055]The communication unit may receive a request for transmission of contents corresponding to the selected object from the mobile terminal and transmit the contents corresponding to the selected object to the mobile terminal. [0056]According to an aspect of another exemplary embodiment, there is provided a method in which a mobile terminal generates a control signal, the method including: receiving a user input; determining an operation mode of the mobile terminal; and in response to determining the operation mode is a first mode, generating a first control signal for controlling an external display device based on the user input, and, in response to determining the operation mode is a second mode, generating a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0057]The contents may include contents corresponding to an object selected from the external display device or additional information corresponding to the object based on the first control signal. [0058]The user input may include at least one of a motion input, a key input, a touch input, a bending input, and a voice input. [0059]The determining may include: determining the operation mode of the mobile terminal as the first mode in a case where the mobile terminal is in a vertical mode, and, determining the operation mode of the mobile terminal as the second mode in a case where the mobile terminal is in a horizontal mode. [0060]The determining may include: determining the operation mode of the mobile terminal based on information displayed on a screen of the mobile terminal. [0061]The determining may include: in response to determining the information displayed on the screen of the mobile terminal is thumbnail information of contents corresponding to the object displayed on the external display device or movement direction information of the mobile terminal, determining the operation mode of the mobile terminal as the first mode, and, in response to determining the information displayed on the screen of the mobile terminal is the contents corresponding to the object displayed on the external display device or additional information corresponding to the object, determining the operation mode of the mobile terminal as the second mode. [0062]The generating of the first control signal may include: converting the first control signal according to a control protocol of the external display device. [0063]The first mode may be a mode in which the object of the external display device is selected, and the second mode is a mode in which additional information corresponding to the selected object is displayed on the mobile terminal. [0064]The first control signal may include a signal for controlling a movement of a selection region for selecting the object of the external display device, and the second control signal may include a signal for controlling at least one of playing of the contents, editing of the contents, and transmission of the contents. [0065]The method may further include: receiving a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle; converting the operation mode from the first mode to the second mode based on the first rotational motion input; receiving a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle; and converting the operation mode from the second mode to the first mode based on the second rotational motion input. [0066]According to an aspect of another exemplary embodiment, there is provided a mobile terminal including: a user input which is configured to receive a user input; an operation mode determining unit which is configured to determine an operation mode of the mobile terminal; and a controller which is configured, in response to the operation mode determining unit determining that the operation mode is a first mode, generate a first control signal for controlling an external display device based on the user input, and, in response to the operation mode determining unit determining that the operation mode is a second mode, generate a second control signal for controlling contents displayed on the mobile terminal based on the user input. [0067]The user input may receive a first rotational motion input for rotating the mobile terminal in a first direction by a predetermined angle and a second rotational motion input for rotating the mobile terminal in a second direction by the predetermined angle, and wherein the controller converts the operation mode from the first mode to the second mode based on the first rotational motion input and the operation mode from the second mode to the first mode based on the second rotational motion input. [0068]According to an aspect of another exemplary embodiment, a method of displaying information of an external display device on a mobile terminal displays is provided. The method includes: receiving a user input into the mobile terminal about an object displayed on the external display device; transmitting a first signal to the external display device to select the object displayed on an external display device; receiving a second user input into the mobile terminal about additional information corresponding to the object displayed on the external display device; transmitting a second signal to the external display device to request additional information corresponding to the selected object; and displaying, on a screen of the mobile terminal, the additional information received from the external display device. [0069]The transmitting the first signal may include converting the first signal to a control protocol of the external display device. [0070]The transmitting the first signal may include requesting control authorization from the external display device and receiving a control authorization acceptance message from the external display device. BRIEF DESCRIPTION OF THE DRAWINGS [0071]The above and other features and advantages will become more apparent by describing in detail exemplary embodiments with reference to the attached drawings in which: [0072]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment; [0073]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment; [0074]FIGS. 3A through 3C are views of screens on which a mobile terminal selects an object of an external display device, according to an exemplary embodiment; [0075]FIGS. 4A and 4B are views of screens on which a mobile terminal obtains additional information, according to an exemplary embodiment; [0076]FIG. 5 is a view of a screen on which contents are obtained, according to an exemplary embodiment; [0077]FIG. 6 is a view of a screen on which an object is displayed or reproduced, according to an exemplary embodiment; [0078]FIG. 7 is a flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0079]FIG. 8 is a detailed flowchart illustrating a method in which a mobile terminal displays information, according to an exemplary embodiment; [0080]FIG. 9 is a flowchart illustrating a method in which a display device senses an input of a mobile terminal and provides additional information, according to an exemplary embodiment; [0081]FIG. 10 is a flowchart illustrating a method in which a mobile terminal obtains additional information through a server, according to an exemplary embodiment; [0082]FIG. 11 is a flowchart illustrating a method in which a mobile terminal obtains contents, according to an exemplary embodiment; [0083]FIG. 12 is a flowchart illustrating a method in which a mobile terminal obtains contents through a server, according to an exemplary embodiment; [0084]FIG. 13 is a view of a screen on which each of a plurality of mobile terminals selects an object of a display device, according to an exemplary embodiment; [0085]FIG. 14 is a block diagram of a mobile terminal, according to an exemplary embodiment; [0086]FIG. 15 is a block diagram of a display device, according to an exemplary embodiment; [0087]FIG. 16 is a flowchart illustrating a method in which a display device provides information, according to an exemplary embodiment; and [0088]FIG. 17 is a flowchart illustrating a method in which a mobile terminal generates a control signal, according to an exemplary embodiment. DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS [0089]First, the terms used herein will be briefly described, and then the exemplary embodiments will be described in detail. [0090]Although the terms used herein are general terms that are widely used at present in consideration of the functions of the exemplary embodiments, they may vary according to the intention of one of ordinary skill in the art, a precedent, the appearance of new technology, or the like. In addition, in a particular case, the applicant may select the terms arbitrarily. In this case, the meanings of the terms will be described in detail in the detailed description of the exemplary embodiments. Thus, the terms used in the detailed description should not be only names of the terms but should be defined based on their meanings and contents in relation to the exemplary embodiments. [0091]When a unit “comprises” an element in the entire specification, the unit does not exclude another element but may further comprise another element unless the context clearly indicates otherwise. In addition, terms such as “ . . . unit”, “module”, and the like used herein indicate a unit for performing at least one function or operation and may be implemented by hardware or software or a combination thereof. [0092]Throughout the specification, an “object” refers to a target that may be selected by a user from a display device. Examples of the object include, but are not limited to, an icon, a link, a picture, a text, an index item, etc. [0093]In addition, “additional information” refers to information regarding contents corresponding to an object, and may have various forms according to types of contents. Examples of the additional information may include, but are not limited to, preview information, prelistening information, application information, user review information, advertisement image information, update information, newspaper article information, goods information, movie information, game information, album information, etc. [0094]In the present specification, “contents” may be displayed, reproduced, or stored in a mobile terminal, and may include, for example, still image contents (for example, a photo, a picture, etc.), text contents (for example, an electronic book (a poem and a novel), a letter, a business file, a web page, an electronic program guide (EPG), etc.), moving image contents (for example, a personal image, a movie, music video, a YouTube video, a TV program image, etc.), music contents (for example, music, a music performance, a radio broadcast, etc.), an application (a widget, a game, etc.) [0095]The exemplary embodiments will now be described more fully with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the inventive concept to those of ordinary skill in the art. For clarity, in the drawings, irrelevant portions with respect to the description are omitted, and similar reference numbers are added to similar portions throughout the entire specification. [0096]As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list. [0097]FIG. 1 is a view for explaining an information providing system according to an exemplary embodiment. [0098]Referring to FIG. 1, the information providing system according to an exemplary embodiment may include a mobile terminal 100 and an external display device 200. [0099]The mobile terminal 100 is a device that obtains contents from the outside and displays, reproduces, or stores the obtained contents. The mobile terminal 100 may be implemented in various ways. For example, the mobile terminal 100 described in the present specification may include a cellular phone, a smart phone, a laptop computer, a tablet personal computer (PC), an e-book terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, etc. [0100]The display device 200 is a device that may be of various types including a display panel. For example, the display device 200 described in the present specification may include a smart television (TV), an Internet protocol TV (IPTV), a digital TV (DTV), a computer, a laptop computer, an e-book terminal, a tablet PC, a digital broadcasting terminal, a consumer electronics (CE) device (for example, a refrigerator or an air conditioner having the display panel), etc. [0101]The display device 200 according to an exemplary embodiment may display an object list. The object list may include identification information regarding at least one piece of contents. Examples of the identification information may include a title of contents, an image and icon indicating contents, etc. [0102]FIG. 2 is a view for explaining an information providing system according to another exemplary embodiment. [0103]Referring to FIG. 2, the information providing system according to another exemplary embodiment may include the mobile terminal 100, the display apparatus 200, and a server 300. [0104]The mobile terminal 100 and the display apparatus 200 are the same as described with reference to FIG. 1, and thus descriptions thereof are omitted. [0105]The server 300 may communicate with the mobile terminal 100 or the display apparatus 200. According to an exemplary embodiment, the server 300 may receive a contents providing request from the mobile terminal 100 or the display device 200. In this case, the server 300 may provide contents to the mobile terminal 100 or the display device 200. The contents provided by the server 300 may be contents corresponding to an object selected by the display device 200 or additional information corresponding to the object. [0106]For example, in a case where the display device 200 selects an object relating to movie contents, the server 300 may provide the movie contents or preview video of the movie contents to the mobile terminal 100 or the display device 200. [0107]An example in which the mobile terminal 100 selects an object displayed on an external display device based on a user input and obtains and displays additional information corresponding to the selected object will now be described in brief with reference to FIGS. 3 through 6. [0108]FIGS. 3A through 3C are views of screens on which the mobile terminal 100 selects an object of the external display device 200, according to an exemplary embodiment. [0109]Referring to FIG. 3A, the display device 200 may display a plurality of objects indicating a plurality of pieces of contents. In this case, a user may use the mobile terminal 100 to select at least one of the plurality of objects displayed on the display device 200. [0110]For example, the user may move the mobile terminal 100 up and down and left and right (a first input) to select at least one of the plurality of objects displayed on the display device 200. In this regard, the display device 200 may display a location of a selection region (for example, a cursor and a pointer) corresponding to a movement of the mobile terminal 100 on a screen. [0111]Although a motion input is exemplarily used as the first input for selecting an object in FIG. 3A, the first input is not limited to the motion input. The first input may be a bending input, a key input, a voice input, and a touch input in addition to the motion input. [0112]According to an exemplary embodiment, the mobile terminal 100 may turn its screen off or may blacken its screen when selecting an object displayed on a screen of the display device 200 in such a way that user's eyes are not distracted. [0113]According to another exemplary embodiment, the mobile terminal 100 may display thumbnail information such as an icon, an image, a title, etc. of contents relating to an object in which the selection region is disposed or a movement direction of the mobile terminal 100 as an arrow, etc. on the display device 200. [0114]Referring to FIG. 3B, the mobile terminal 100 may display a selection window (or a graphical user interface (GUI)) for selecting a category (for example, drama, movie, sports, etc.) of contents. In this regard, the mobile terminal 100 may receive a selection of at least one category from the user. The mobile terminal 100 may transmit information regarding the selected category to the display device 200. In this case, the display device 200 may filter and display an object regarding contents corresponding to the category selected by the user. [0115]Referring to FIG. 3C, the mobile terminal 100 may output a map or a GUI indicating objects displayed on the display device 200 from among all the objects. [0116]FIGS. 4A and 4B are views of screens on which the mobile terminal 100 obtains additional information, according to an exemplary embodiment. [0117]Referring to FIG. 4A, a user may move the mobile terminal 100, select an object of the display device 200, then rotate the mobile terminal 100, and request additional information corresponding to the selected object from the display device 200. [0118]In this case, the display device 200 may transmit the additional information corresponding to the selected object or link information (for example, a uniform resource identifier (URI)) of the additional information to the mobile terminal 100. In this regard, the mobile terminal 100 may display the obtained additional information on a screen. [0119]For example, as shown in FIG. 4A, in a case where the user moves the mobile terminal 100, selects an object illustrating Shrek, and converts a vertical mode of the mobile terminal 100 into a horizontal mode, the mobile terminal 100 may obtain and display additional information (for example, Movie Title: Shrek, Review: ★★★★⋆, Representative Image, and Advertisement Moving Image) relating to Shrek. [0120]According to an exemplary embodiment, referring to FIG. 4B, if the user wishes to select a new object, the user may select the object of the display device 200 again by converting the horizontal mode of the mobile terminal 100 into the vertical mode. [0121]Although a motion input is that an object is selected and then is that the mobile terminal 100 receives and displays additional information corresponding to the object in FIGS. 3A through 4B as a rotation input, an exemplary embodiment is not limited thereto. That is, according to an exemplary embodiment, the mobile terminal 100 may receive and display additional information regarding contents relating to an object in which a selection region is disposed from the display device 200 while selecting an object of the display device 200 as the motion input. According to (String), 相关专利申请的交叉引用 [0001] 本申请是美国专利申请系列的延续申请。 2013 年 7 月 25 日提交的第 13/950,507 号,要求于 2012 年 7 月 25 日在韩国知识产权局提交的韩国专利申请第 10-2012-0081434 号的优先权,其公开内容并入 在此全文引用。 背景 [0002] 1. 领域 [0003] 示例性实施例涉及用于通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与所选对象相对应的附加信息来显示信息的方法和移动终端、用于提供信息的方法和显示设备 通过基于移动终端的输入选择对象并向移动终端提供关于所选对象的附加信息,以及用于通过基于操作将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端 移动终端的模式。 [0004] 2.相关技术的描述 [0005] 智能电视(Smart TV)是一种将电视与上网功能相结合,能够利用网络冲浪、视频点播(VOD)观看、社交网络服务(SNS)、游戏等多种功能的多功能电视。 并安装各种应用程序。 [0006] 智能电视的一个特点是用户和电视可以相互发送和接收信息。 这是智能电视与现有的仅单方面传输信息的电视的区别。 因此,智能电视也被称为互动电视。 [0007] 但是,用户通过标准的遥控器来使用智能电视的各种功能是非常不方便的。 特别地,当用户浏览或下载内容时,用户需要通过几个步骤来操作遥控器。 [0008] 因此,需要一种让用户容易控制智能电视的控制装置或系统。 概括 [0009] 示例性实施例提供一种用于显示信息的方法和移动终端,该方法和移动终端通过基于移动终端的输入选择显示在外部显示设备上的对象并获得和显示与选择的对象相对应的附加信息来进行。 [0010] 示例性实施例还提供了一种用于通过基于移动终端的输入选择对象并向移动终端提供关于所选对象的附加信息来提供信息的方法和显示设备。 [0011] 示例性实施例还提供一种用于通过基于移动终端的操作模式将接收到的用户输入改变为控制信号来生成控制信号的方法和移动终端。 [0012] 根据示例性实施例的一方面,提供了一种移动终端显示信息的方法,该方法包括:基于第一输入将用于选择在外部显示设备上显示的对象的第一信号发送到外部显示设备 用户通过移动终端; 基于用户通过移动终端的第二输入向外部显示设备发送用于请求与所选对象对应的附加信息的第二信号; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0013] 发送第一选择对象信号可以包括: 根据外部显示设备的控制协议对选择对象信号进行转换。 [0014] 用于选择对象的第一信号的发送可以包括:发送用于控制选择区域的移动的信号,用于选择显示在外部显示设备上的对象。 [0015]发送用于控制选择区域的移动的信号可以包括:发送用于控制选择区域的移动方向、选择区域的移动速度和屏幕上显示的对象的数量中的至少一项的信号。 基于第一输入的外部显示设备。 [0016] 发送用于选择对象的第一信号可以包括:在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0017] 缩略图信息可以包括与对象对应的内容的图像、内容的标题和内容的类型中的至少一个。 [0018] 发送用于选择对象的第一信号可以包括:根据第一输入在屏幕上显示移动终端的移动方向。 [0019] 第一输入和第二输入可以包括运动输入、键输入、触摸输入、弯曲输入和语音输入中的至少一个。 [0020] 第一输入可以包括用于在3D方向上移动移动终端的三维(3D)运动输入,其中第二输入包括用于将移动终端旋转超过预定角度的旋转运动输入。 [0021] 发送用于请求附加信息的第二信号可以包括:从显示设备接收附加信息。 [0022] 用于请求附加信息的第二信号的发送可以包括:基于第二输入从外部显示设备接收附加信息的链接信息; 基于接收到的链接信息从服务器接收附加信息。 [0023] 将用于选择对象的第一信号发送给显示设备可以包括: 向外部显示设备请求控制授权; 接收来自外部显示设备的控制授权接受消息。 [0024] 内容可以包括静止图像、运动图像、应用程序、音乐、网页和电子节目指南(EPG)中的至少一种。 [0025] 附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、广告图像信息和专辑信息中的至少一种。 [0026] 该方法还可以包括:基于用户通过移动终端的第三输入来控制在移动终端的屏幕上显示的附加信息。 [0027] 对附加信息的控制可以包括:基于用户通过移动终端的第三输入,控制附加信息的显示、附加信息的播放以及改变为上一个附加信息或下一个附加信息中的至少一个。 [0028] 该方法还可以包括:获取与显示在移动终端的屏幕上的附加信息对应的内容。 [0029] 根据另一示例性实施例的一方面,提供了一种显示设备向移动终端提供信息的方法,该方法包括:通过通过移动终端接收用户的第一输入来选择显示在显示设备上的对象 ; 通过移动终端接收用户的第二输入,将与选择的对象对应的附加信息发送到移动终端。 [0030] 发送可以包括:从对应于所选对象的内容中提取附加信息。 [0031] 对象的选择可以包括:从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号; 根据控制信号移动选择区域。 [0032] 对象的选择可以包括:将接收到的第一输入转换为用于根据显示设备的控制协议控制选择区域的移动的控制信号。 [0033] 接收可以包括:从多个移动终端中的每一个接收用于控制选择区域的移动的控制信号。 [0034] 该方法还可以包括:感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0035] 对象的选择可以包括:基于用户通过移动终端的第一输入,控制选择区域的移动方向、选择区域的移动速度以及屏幕上显示的对象的数量中的至少一个。 . [0036] 对象的选择可以包括:将对象对应的内容的缩略图信息发送给移动终端。 [0037] 向移动终端发送附加信息可以包括:向移动终端发送附加信息的链接信息。 [0038] 终端还可以包括: 从移动终端接收与选择的对象对应的内容的传输请求; 将选择的对象对应的内容发送给移动终端。 [0039] 根据另一示例性实施例的一个方面,提供了一种移动终端,包括: 通信单元,被配置为基于用户的第一输入向外部显示设备发送用于选择在外部显示设备上显示的对象的信号。 通过移动终端; 附加信息获取单元,被配置为基于用户通过移动终端的第二输入向外部显示设备发送请求与选择的对象对应的附加信息的信号; 显示器,用于显示从外部显示设备接收到的附加信息; 控制器,用于控制通信单元、附加信息获取单元和显示单元。 [0040] 控制器可以根据外部显示设备的控制协议转换用于选择对象的信号。 [0041] 通信单元可以发送用于控制选择区域的移动的信号,该选择区域用于选择显示在外部显示装置上的对象。 [0042] 通信单元可以基于第一输入发送用于控制选择区域的移动方向、选择区域的移动速度和显示在外部显示设备的屏幕上的对象的数量中的至少一个的信号。 [0043] 显示器可以在移动终端的屏幕上显示与对象对应的内容的缩略图信息。 [0044] 附加信息获取单元可以从外部显示设备接收附加信息。 [0045] 通信单元可以基于第二输入从外部显示设备接收附加信息的链接信息,并且其中附加信息获取单元基于接收到的链接信息从服务器接收附加信息。 [0046] 控制器可以基于用户通过移动终端的第三输入来控制在移动终端上显示的附加信息。 [0047] 所述移动终端还可以包括: 内容获取单元,用于获取所述移动终端显示的附加信息对应的内容。 [0048] 根据示例性实施例的一方面,提供了一种显示装置,包括: 选择单元,被配置为基于用户通过移动终端的第一输入选择显示在显示装置上的对象; 通信单元,被配置为通过接收用户通过移动终端的第二输入来将与选择的对象对应的附加信息发送到移动终端,以及控制器,被配置为控制选择单元和通信单元。 [0049] 控制器可以从对应于所选对象的内容中提取附加信息。 [0050]选择单元可以从移动终端接收用于控制用于选择对象的选择区域的移动的控制信号,并且根据接收到的控制信号移动选择区域。 [0051] 控制器可以根据显示装置的控制协议将接收到的第一输入转换为用于控制选择区域的移动的控制信号。 [0052] 显示装置还可以包括:传感器,用于感测用户通过移动终端的第一输入和用户通过移动终端的第二输入中的至少一个。 [0053] 控制器可以基于用户通过移动终端的第一输入来控制选择区域的移动方向、选择区域的移动速度和显示在屏幕上的对象的数量中的至少一个。 [0054] 通信单元可以将附加信息的链接信息发送到移动终端。 [0055] 通信单元可以从移动终端接收对与所选对象相对应的内容的传输请求,并将与所选对象相对应的内容发送到移动终端。 [0056] 根据另一示例性实施例的一方面,提供了一种移动终端生成控制信号的方法,该方法包括:接收用户输入; 确定移动终端的操作模式; 并且响应于确定操作模式是第一模式,基于用户输入生成用于控制外部显示设备的第一控制信号,并且响应于确定操作模式是第二模式,生成用于控制外部显示设备的第二控制信号 基于用户输入控制在移动终端上显示的内容。 [0057] 内容可以包括与从外部显示设备选择的对象相对应的内容或与基于第一控制信号的对象相对应的附加信息。 [0058] 用户输入可以包括动作输入、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0059] 所述确定可以包括:在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第一模式,以及,在所述移动终端处于竖直模式的情况下,将所述移动终端的工作模式确定为所述第二模式。 终端处于水平模式。 [0060] 所述确定可以包括:根据所述移动终端的屏幕上显示的信息确定所述移动终端的操作模式。 [0061] 所述确定可以包括:响应于确定所述移动终端屏幕上显示的信息为所述外接显示设备上显示的对象对应的内容的缩略图信息或所述移动终端的移动方向信息,确定所述移动终端的操作模式。 终端作为第一模式,并且,响应于确定移动终端的屏幕上显示的信息是与外部显示设备上显示的对象对应的内容或与该对象对应的附加信息,确定移动终端的操作模式 终端作为第二种模式。 [0062] 第一控制信号的产生可以包括:根据外部显示设备的控制协议转换第一控制信号。 [0063] 第一模式可以是选择外部显示设备的对象的模式,第二模式是在移动终端上显示与选择的对象对应的附加信息的模式。 [0064] 第一控制信号可以包括用于控制用于选择外部显示设备的对象的选择区域的移动的信号,并且第二控制信号可以包括用于控制内容的播放、内容的编辑中的至少一个的信号。 ,以及内容的传输。 [0065]该方法还可以包括:接收用于将移动终端在第一方向上旋转预定角度的第一旋转运动输入; 基于第一旋转运动输入将操作模式从第一模式转换为第二模式; 接收用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入; 基于第二旋转运动输入,将操作模式从第二模式转换为第一模式。 [0066] 根据另一示例性实施例的一方面,提供了一种移动终端,包括: 用户输入,被配置为接收用户输入; 操作模式确定单元,用于确定移动终端的操作模式; 控制器,被配置为响应于操作模式确定单元确定操作模式是第一模式,基于用户输入产生用于控制外部显示装置的第一控制信号,并且响应于操作模式 确定单元确定操作模式是第二模式,基于用户输入产生用于控制在移动终端上显示的内容的第二控制信号。 [0067] 用户输入可以接收用于将移动终端沿第一方向旋转预定角度的第一旋转运动输入和用于将移动终端沿第二方向旋转预定角度的第二旋转运动输入,并且其中控制器转换操作 基于第一旋转运动输入从第一模式到第二模式的模式和基于第二旋转运动输入从第二模式到第一模式的操作模式。 [0068] 根据另一示例性实施例的一方面,提供了一种在移动终端显示器上显示外部显示设备的信息的方法。 该方法包括:接收到移动终端的关于显示在外部显示设备上的对象的用户输入; 传送第一信号至外接显示装置以选择外接显示装置上显示的对象; 接收到移动终端的关于与显示在外部显示设备上的对象对应的附加信息的第二用户输入; 向外部显示设备发送第二信号以请求对应于所选对象的附加信息; 在移动终端的屏幕上显示从外部显示设备接收到的附加信息。 [0069] 发送第一信号可以包括将第一信号转换为外部显示设备的控制协议。 [0070] 发送第一信号可以包括从外部显示设备请求控制授权和从外部显示设备接收控制授权接受消息。 附图的简要说明 [0071] 通过参考附图详细描述示例性实施例,上述和其他特征和优点将变得更加明显,其中: [0072] 如图。 附图说明图1是用于说明实施方式的信息提供系统的图。 [0073] 如图。 图2是用于说明另一实施方式的信息提供系统的图。 [0074] 图 图3A至图3C是根据示例性实施例的移动终端选择外部显示设备的对象的屏幕的视图; [0075] 图 图4A和4B是根据示例性实施例的移动终端在其上获得附加信息的屏幕的视图; [0076] 如图。 图5是根据示例性实施例的获取内容的屏幕的视图; [0077] 如图。 图6是根据示例性实施例的显示或再现对象的屏幕的视图; [0078] 如图。 图7是示出根据示例性实施例的移动终端显示信息的方法的流程图; [0079] 如图。 图8是示出根据示例性实施例的移动终端显示信息的方法的详细流程图; [0080]如图。 图9是示出根据示例性实施例的显示设备感测移动终端的输入并提供附加信息的方法的流程图; [0081] 如图。 图10是示出根据示例性实施例的移动终端通过服务器获取附加信息的方法的流程图; [0082] 如图。 图11是示出根据示例性实施例的移动终端获取内容的方法的流程图; [0083] 如图。 图12是示出根据示例性实施例的移动终端通过服务器获取内容的方法的流程图; [0084] 如图。 图13是根据示例性实施例的多个移动终端中的每一个选择显示装置的对象的屏幕的视图; [0085] 如图。 图14是根据示例性实施例的移动终端的框图; [0086] 如图。 图15是根据示例性实施例的显示装置的框图; [0087] 如图。 图16是示出根据示例性实施例的显示装置提供信息的方法的流程图; 和 [0088] 如图。 图17是示出根据示例性实施例的移动终端生成控制信号的方法的流程图。 示例性实施例的详细说明 [0089] 首先,将简要描述这里使用的术语,然后将详细描述示例性实施例。 [0090] 尽管这里使用的术语是考虑到示例性实施例的功能而目前广泛使用的通用术语,但是它们可以根据本领域普通技术人员的意图、先例、新技术的出现或 类似。 此外,在特定情况下,申请人可以任意选择术语。 在这种情况下,术语的含义将在示例性实施例的详细描述中详细描述。 因此,在详细描述中使用的术语不应仅仅是术语的名称,而应基于与示例性实施例相关的含义和内容来定义。 [0091] 当一个单元“包括”整个说明书中的一个元素时,该单元不排除另一个元素,而是可以进一步包括另一个元素,除非上下文另有明确说明。 此外,诸如“. . . 这里使用的“单元”、“模块”等表示用于执行至少一个功能或操作的单元,可以通过硬件或软件或其组合来实现。 [0092] 在整个说明书中,“对象”指的是可以由用户从显示设备中选择的目标。 对象的示例包括但不限于图标、链接、图片、文本、索引项等。 [0093] 此外,“附加信息”指的是关于与对象对应的内容的信息,并且可以根据内容的类型而具有各种形式。 附加信息的示例可以包括但不限于预览信息、试听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息、 等等 [0094] 在本说明书中,“内容”可以在移动终端中显示、再现或存储,并且可以包括例如静止图像内容(例如照片、图片等)、文本内容(例如 、电子书(一首诗、一部小说)、一封信、一份商务文件、一个网页、一个电子节目指南(EPG)等)、运动图像内容(例如,个人图像、电影、音乐 视频、YouTube 视频、电视节目图像等)、音乐内容(例如,音乐、音乐表演、无线电广播等)、应用程序(小部件、游戏等) [0095]现在将参照附图更全面地描述示例性实施例。 然而,示例性实施例可以以许多不同的形式体现,并且不应被解释为限于本文所阐述的实施例; 相反,提供这些实施例是为了使本公开彻底和完整,并将本发明构思充分传达给本领域普通技术人员。 为了清楚起见,在附图中,省略了与描述无关的部分,并且在整个说明书中类似的附图标记被添加到类似的部分。 [0096] 如本文所用,术语“和/或”包括一个或多个相关列出的项目的任何和所有组合。 诸如“至少一个”之类的表达式在元素列表之前时,会修改整个元素列表,而不是修改列表中的各个元素。 [0097] 如图。 附图说明图1是用于说明根据示例性实施例的信息提供系统的视图。 [0098] 参考图。 参照图1,根据示例性实施例的信息提供系统可以包括移动终端 100 和一个外部显示设备 200 . [0099] 移动终端 100 是从外部获取内容并显示、再现或存储获取的内容的设备。 移动终端 100 可以以各种方式实现。 例如,移动终端 100 本说明书中描述的可以包括蜂窝电话、智能电话、膝上型计算机、平板个人计算机(PC)、电子书终端、个人数字助理(PDA)、便携式多媒体播放器(PMP)、 导航系统等 [0100] 显示装置 200 是一种可以是各种类型的设备,包括显示面板。 例如,显示设备 200 本说明书中描述的可以包括智能电视(TV)、互联网协议电视(IPTV)、数字电视(DTV)、计算机、膝上型计算机、电子书终端、平板电脑、数字广播终端 ,消费电子(CE)设备(例如,具有显示面板的冰箱或空调)等。 [0101] 显示装置 200 根据示例性实施例,可以显示对象列表。 对象列表可以包括关于至少一个内容的标识信息。 标识信息的示例可以包括内容的标题、指示内容的图像和图标等。 [0102] 如图。 图2是用于说明根据另一示例性实施例的信息提供系统的视图。 [0103] 参考图。 参照图2,根据另一示例性实施例的信息提供系统可以包括移动终端 100 , 显示装置 200 , 和一个服务器 300 . [0104] 移动终端 100 和显示装置 200 与参考图1描述的相同。 与图1相同,因此省略其说明。 [0105] 服务器 300 可与移动终端通信 100 或显示设备 200 . 根据示例性实施例,服务器 300 可以从移动终端接收内容提供请求 100 或显示设备 200 . 在这种情况下,服务器 300 可以向移动终端提供内容 100 或显示设备 200 . 服务器提供的内容 300 可以是显示设备选择的对象对应的内容 200 或与对象对应的附加信息。 [0106] 例如,在显示设备 200 选择与电影内容相关的对象,服务器 300 可向移动终端提供电影内容或电影内容的预览视频 100 或显示设备 200 . [0107] 以移动终端为例 100 现在将参考图1至图3简要描述基于用户输入选择在外部显示设备上显示的对象并获得并显示与所选择的对象相对应的附加信息。 3 到 6。 [0108] 图 图3A到3C是移动终端在其上的屏幕的视图 100 选择外部显示设备的对象 200 ,根据示例性实施例。 [0109] 参考图。 3A、显示装置 200 可以显示指示多条内容的多个对象。 在这种情况下,用户可以使用移动终端 100 选择显示在显示设备上的多个对象中的至少一个 200 . [0110] 例如,用户可以移动移动终端 100 上下左右(第一输入)以选择显示设备上显示的多个对象中的至少一个 200 . 对此,显示设备 200 可以显示与移动终端的移动相对应的选择区域(例如,光标和指针)的位置 100 在屏幕上。 [0111] 尽管在图1中示例性地使用运动输入作为用于选择对象的第一输入。 如图3A所示,第一输入不限于动作输入。 除了动作输入之外,第一输入可以是弯曲输入、键输入、语音输入和触摸输入。 [0112] 根据示例性实施例,移动终端 100 选择显示设备屏幕上显示的对象时,可能会关闭屏幕或将屏幕变黑 200 这样用户的眼睛就不会分心。 [0113] 根据另一示例性实施例,移动终端 100 可以显示与设置选择区域的对象或移动终端的移动方向有关的内容的缩略图信息,例如图标、图像、标题等 100 显示设备上的箭头等 200 . [0114] 参考图。 3B、移动终端 100 可以显示用于选择内容类别(例如,戏剧、电影、体育等)的选择窗口(或图形用户界面(GUI))。 对此,移动端 100 可以接收来自用户的至少一个类别的选择。 移动终端 100 可以将关于所选类别的信息发送到显示设备 200 . 在这种情况下,显示设备 200 可以过滤和显示关于与用户选择的类别相对应的内容的对象。 [0115] 参考图。 3C、移动终端 100 可以输出地图或图形用户界面指示显示设备上显示的对象 200 从所有对象中。 [0116] 图 图4A和4B是移动终端在其上的屏幕的视图 100 根据示例性实施例,获取附加信息。 [0117] 参考图。 参照图4A,用户可以移动移动终端 100 , 选择显示设备的对象 200 ,然后旋转移动端 100 , 并向显示设备请求与所选对象对应的附加信息 200 . [0118] 在这种情况下,显示设备 200 可以将与选择的对象相对应的附加信息或附加信息的链接信息(例如,统一资源标识符(URI))发送到移动终端 100 . 对此,移动端 100 可以在屏幕上显示获得的附加信息。 [0119] 例如,如图所示。 参照图4A,在用户移动移动终端的情况下 100 ,选择描绘史莱克的对象,并转换移动终端的垂直模式 100 进入横屏模式,移动端 100 可能会获取和显示与史莱克有关的附加信息(例如,电影名称:史莱克、评论:★★★★⋆、代表图像和广告动态图像)。 [0120] 根据示例性实施例,参考图1。 参照图4B,如果用户希望选择新对象,则用户可以选择显示设备的对象 200 再次通过转换移动端的水平模式 100 进入垂直模式。 [0121] 虽然动作输入是选择了一个对象然后是移动终端 100接收并显示对应于图1和2中的对象的附加信息。 尽管将图3A到4B作为旋转输入,但示例性实施例不限于此。 也就是说,根据示例性实施例,移动终端 100 可以从显示装置接收和显示关于与其中设置了选择区域的对象有关的内容的附加信息 200 在选择显示设备的对象时 200 作为运动输入。 根据示例性实施例,移动终端在其上的通信网络 100 将用于选择对象的信号发送到显示设备 200 以及移动终端所通过的通信网络 100 从显示设备接收附加信息 200 可能彼此不同。 例如,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 通过蓝牙通信,然后从显示设备接收与所选对象对应的附加信息 200 通过 Wi-Fi 通信。 [0122] 如图。 图5是根据示例性实施例的在其上获得内容的屏幕的视图。 [0123] 用户可以确认关于与从显示设备获得的对象相对应的内容的附加信息 200 然后向显示设备请求相应的内容 200 或服务器 300 . 例如,用户可以通过显示设备确认关于电影史瑞克的附加信息(用户评论等) 200 然后从显示设备请求和下载电影内容史莱克 200 或服务器 300 . [0124] 如图。 图6是根据示例性实施例的显示或再现对象的屏幕的视图。 [0125] 参考图。 参照图6,根据示例性实施例,移动终端 100 可以显示或再现从显示设备下载的内容 200 或服务器 300 . [0126] 根据另一示例性实施例,移动终端 100 可以通过流式传输内容来接收和再现内容。 [0127] 一种移动终端的方法 100 现在将在下面详细描述基于用户输入检索和/或显示信息。 [0128] 根据示例性实施例的显示信息的方法可以通过预定应用来实现。 也就是移动终端 100 可以驱动用于提供根据示例性实施例的显示信息的方法的应用。 移动终端 100 可以基于用户输入或自动驱动应用程序。 [0129] 移动端驱动的应用 100 可以是仅用于执行控制显示设备的过程的应用程序 200 或提供各种服务。 例如,该应用程序可以是用于提供远程控制服务、信使服务、社交网络服务(SNS)、多媒体内容播放服务等的应用程序。 [0130] 假设移动终端使用的方法 100 显示参考图1和2描述的信息。 可以通过预定的应用来执行图7至图12的说明。 [0131] 如图。 图7是示出移动终端的方法的流程图 100 根据示例性实施例,显示信息。 参考图。 7、移动终端的方法 100 根据示例性实施例的显示信息包括由移动终端顺序执行的操作 100 图。 稍后将描述的图14。 因此,虽然以下省略,但以上关于移动终端的描述 100 图。 图14的方法也将适用于图14的方法。 7 其中移动终端 100 显示信息。 [0132] 在操作 S 710 , 移动端 100 可以发送用于选择外部显示设备的对象的信号 200 到显示设备 200 基于第一输入。 在接收到第一输入的情况下,移动终端100 可以产生用于选择显示设备的对象的信号 200 基于第一个输入。 [0133] 根据示例性实施例,移动终端 100 可以根据显示设备的控制协议转换用于选择对象的信号 200 . 也就是移动终端 100 可以获得显示设备的标识信息(例如设备类型、设备ID、设备序列号等) 200 并将接收到的用户的第一输入转换为显示设备可识别的控制命令 200 基于显示设备的识别信息 200 . [0134] 根据示例性实施例的用于选择对象的信号可以包括用于控制选择对象的选择区域的移动的信号。 也就是说,在移动终端 100 检测到超过阈值的移动,移动终端 100 可以产生用于控制显示装置的选择区域的移动的信号 200 基于有关检测到的运动的信息。 [0135] 例如,在陀螺仪传感器值小于阈值的情况下,移动终端 100 可以确定移动终端 100 不移动,可以不产生用于控制选择区域移动的信号,并且,每次陀螺传感器值改变预定值(例如,10度)时,可以产生用于将选择区域移动一个空间的控制信号 /sec) 大于阈值。 [0136] 根据另一示例性实施例的用于选择对象的信号可以包括信息(例如,移动终端的移动位置信息) 100 ) 关于第一个输入。 也就是移动终端 100 可以直接产生控制选择区域移动的信号并将其传输到显示装置 200 或者可以发送信息(例如,移动终端的移动位置信息) 100 ) 关于显示设备的第一个输入 200 . [0137] 在信息(例如,移动终端的移动位置信息 100 ) 关于第一个输入被传输到显示设备 200 , 显示设备 200 可以根据显示设备的控制协议将第一输入转换为用于控制选择区域的移动的信号 200 . [0138] 例如,在接收到小于阈值的陀螺传感器值的情况下,移动终端 100 可以确定移动终端 100 不移动并且可能不产生用于控制选择区域移动的信号。 移动终端 100 每当接收到大于阈值的预定陀螺传感器值(例如,10度/秒)时,可以生成用于将选择区域移动一个空间的控制信号。 [0139] 在生成控制信号之前,移动终端 100 可以通过身份验证来授权显示设备 200 通过显示设备 200 . 例如,移动终端 100 可以向显示设备请求控制授权 200 . 对此,移动端 100 可以通过发送移动终端的识别信息来请求控制授权 100 到显示设备 200 . 移动终端的识别信息 100 是识别移动终端的唯一信息 100 ,并且可能包括例如设备 ID、唯一序列号、媒体访问控制 (MAC) 地址、国际移动设备身份 (IMEI) 等。 [0140] 显示装置 200 可认证移动终端的控制权限 100 基于移动终端的识别信息 100 . 在认证成功的情况下,显示设备 200 可以向移动终端发送控制授权接受消息100 . 在这种情况下,移动终端 100 可以控制显示设备 200 . [0141] 在发送控制授权接受消息时,显示设备 200 可以注册移动终端的识别信息 100 在一个存储单元中。 因此,虽然移动终端 100 未经显示设备认证 200 不再是移动端 100 可以控制显示设备 200 . [0142] 在操作 S 720 , 移动端 100 可以获得与从显示设备中选择的对象相对应的附加信息 200 基于第二个输入。 即,在接收到第二输入的情况下,移动终端 100 可以从显示设备请求与基于第一输入选择的对象相对应的附加信息 200 . 在这种情况下,移动终端 100 可以从显示设备获取附加信息 200 或通过服务器 300 . 这将参照图3详细描述。 8 以后。 [0143] 在操作 S 730 , 移动端 100 可以在屏幕上显示获得的附加信息。 移动终端 100 可以在将附加信息存储在存储单元中之后通过下载来显示附加信息,或者可以通过流式传输附加信息来显示附加信息。 [0144] 根据示例性实施例的附加信息可以包括预览信息、预听信息、应用信息、用户评论信息、广告图像信息、更新信息、报纸文章信息、商品信息、电影信息、游戏信息、专辑信息等。 [0145] 这将参照图3更详细地描述。 8 以后。 如图。 图8是示出移动终端的方法的详细流程图 100 根据示例性实施例,显示信息。 [0146] 在操作 S 810 , 移动端 100 可以接收第一输入。 移动端的第一个输入 100 可以是动作输入(例如3D动作输入、旋转动作输入等)、按键输入、触摸输入、弯曲输入、语音输入、多模态输入等。即用户 可以移动移动终端 100 上(+Y 轴方向)和下(-Y 轴方向)和左(-X 轴方向)和右(+X 轴方向),触摸(轻拂、拖动、点击、平移等)屏幕(或 GUI显示在屏幕上)的移动终端 100 上下左右,操作移动(方向)键,弯曲移动终端预定区域(左上、右上、左下、右下) 100 ,或输入包括移动命令的语音。 在操作 S 820 , 移动端 100 可以基于第一输入生成用于选择对象的信号。 例如,在第一输入为移动终端的动作输入的情况下 100 上下左右移动,移动端 100 可以根据移动终端的移动生成用于控制选择区域的移动的信号 100 . 即,在用户移动移动终端的情况下 100 向左(-X轴方向)移动预定值以上,移动终端 100 可以产生用于将选择区域向左移动一格的控制信号。 [0147] 在第一输入为上下左右触摸触摸屏的触摸输入的情况下,移动终端 100 可以根据用户的触摸手势产生用于控制选择区域的移动的信号。 例如,在用户使用手指或电子笔从左向右轻拂触摸屏超过预定距离的情况下,移动终端 100 可以产生用于将选择信号向右移动一个空间的控制信号。 [0148] 在第一输入是操作移动(方向)键的键输入的情况下,移动终端 100可以产生用于将选择区域移动到与方向键对应的位置的控制信号。 [0149] 在第一输入是移动终端的预定区域的弯曲输入的情况下 100 , 可以由柔性显示器形成, 弯曲, 移动终端 100 可以产生用于在对应于弯曲运动的方向上移动选择区域的控制信号。 “弯曲”可以是移动终端的弯曲或变形 100 通过外力。 “弯曲运动”可以是移动终端的弯曲运动或变形 100 . [0150] 例如,在用户弯曲移动终端顶部的情况下 100 , 移动端 100 在用户弯曲移动终端的左侧区域的情况下,可以生成用于将选择区域向上移动一格的控制信号 100 , 移动端 100 可以生成用于将选择区域向左移动一个空间的控制信号,并且在用户弯曲整个移动终端的情况下 100 , 移动端 100 可以产生用于选择包括当前选择区域的对象的控制信号。 [0151] 在第一输入为语音输入的情况下,移动终端 100 可以生成用于将选择区域移动到与语音输入对应的位置的控制信号。 例如,在用户说“向左移动三个空格”的情况下,移动终端 100 可以生成用于将选择区域向左移动三个空间的控制信号。 [0152] 在操作 S 830 , 移动端 100 可以将基于第一输入生成的用于选择对象的信号发送到显示装置 200 . 移动终端 100 根据示例性实施例,可以将用于选择对象的信号发送到显示装置 200 直接或通过服务器 300 . 移动终端 100 根据示例性实施例,还可以使用各种通信方法发送用于选择对象的信号。 [0153] 例如,在移动终端 100 和显示设备 200 在预定范围(局域距离)内,移动终端 100 可以将用于选择对象的信号发送到显示设备 200 直接通过短距离无线通信(蓝牙、Zigbee、近场通信(NFC)、Wi-Fi直连(WFD)、超宽带(UWB)、红外数据协会(IrDA)等)。 移动终端 100 也可以通过移动通信网络(例如,2G/3G/4G、Wibro等)或无线局域网(LAN)(Wi-Fi:ad-hoc模式,基础设施模式)传输用于选择对象的信号 )。 [0154] 在操作 S 840 , 显示设备 200 可以根据移动终端的第一输入移动选择区域 100 . 例如,在第一输入为移动终端的动作输入的情况下 100 向左移动(-X 轴方向),显示设备 200 将选择区域向左移动。 [0155] 根据示例性实施例,显示装置 200 可以基于第一输入控制选择区域的移动速度。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 以高于阈值速度的速度向右移动,显示设备 200 可以将选择区域向右移动几个空格(例如,每3个空格),并且,如果用户移动移动终端 100 以低于阈值速度的速度向左移动,显示设备 200 可以将选择区域向左移动一格。 [0156] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户拖动移动终端的触摸屏 100 在高于阈值速度的速度下,显示设备 200 可以将选择区域移动几个空格,并且,如果用户拖动移动终端的触摸屏 100在低于阈值速度的速度下,显示设备 200 可以将选择区域移动一个空格。 [0157] 根据示例性实施例,在第一输入是弯曲输入的情况下,显示装置 200 可以基于用户弯曲移动终端的预定区域的次数来控制选择区域的移动速度 100 . 例如,在用户弯曲移动终端顶部的情况下 100 三、显示装置 200 可以将选择区域向上移动三个空格,并且在用户弯曲移动终端的右侧区域的情况下 100 两次,显示设备 200 可以将选择区域向右移动两个空格。 此外,显示装置的例子多种多样 200 根据第一个输入移动选择区域。 [0158] 根据示例性实施例,显示装置 200 可以基于第一输入调整屏幕上显示的对象的数量。 例如,在第一输入为动作输入的情况下,如果用户移动移动终端 100 在正面方向(+Z轴方向)上,显示装置 200 可能会减少屏幕上显示的对象数量,并且,如果用户移动移动终端 100 在后方(-Z轴方向),显示装置 200 可能会增加屏幕上显示的对象数量。 [0159] 根据示例性实施例,在第一输入为触摸输入的情况下,如果用户多点触摸移动终端的触摸屏上的至少两个点 100 并将两个点拖离对方,显示设备 200 可能会减少屏幕上显示的对象数量,并且如果用户将两个点拖得更近,则显示设备 200 可能会增加屏幕上显示的对象数量。 [0160] 根据示例性实施例,在第一输入是弯曲输入的情况下,如果用户弯曲移动终端的中心部分 100 为凸出,显示装置 200 可以减少屏幕上显示的对象的数量,并且,如果用户弯曲移动终端的中心部分 100 是凹的,显示装置 200 可能会增加屏幕上显示的对象数量。 [0161] 此外,显示装置的例子多种多样 200 根据第一个输入调整屏幕上显示的对象数量。 [0162] 根据示例性实施例,虽然显示装置 200 根据移动终端的第一输入选择对象 100 , 移动端 100 可以从显示装置接收并显示与其中设置有选择区域的对象相对应的内容的缩略图信息 200 . 例如,移动终端 100 可以显示与设置有选择区域的对象相对应的内容的图像、图标、标题、内容类型等。 移动终端可以显示与移动终端的当前位置相对应的选择区域的位置 100 以及选择区域在显示装置的整个屏幕上的移动方向 200 . [0163] 根据另一示例性实施例,移动终端 100 可以关闭其屏幕或使其屏幕变黑,以使用户的眼睛不会从显示设备的屏幕上分心 200 在其上选择对象。 [0164] 在操作 S 850 , 显示设备 200 选择对象。 根据示例性实施例,显示装置 200 可以基于第一输入选择其中布置了移动的选择区域的对象。 [0165] 根据示例性实施例,显示装置 200 可以识别(强调)其中设置选择区域的对象。 例如,显示设备 200可以将设置选择区域的对象的边框表示为框,也可以将设置选择区域的对象相对于其他对象增大尺寸,或者制作闪烁等动画效果。 [0166] 在操作 S 860 , 移动端 100 可以接收第二个输入。 根据示例性实施例的第二输入可以是用于获得附加信息的用户输入。 移动端二次输入 100 根据示例性实施例,可以包括动作输入、键输入、弯曲输入和语音输入中的至少一种。 例如,用户可以旋转移动终端 100 以预定角度弯曲移动终端的中心部分 100 , 按下移动端的一个选择键 100 ,在请求附加信息的屏幕上触摸(轻敲)GUI,或输入请求附加信息的语音。 第二输入不限于此,并且可以存在多种示例。 [0167] 在操作 S 870 , 移动端 100 可以向显示设备请求与所选对象对应的附加信息 200 . 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 直接或通过服务器 300 . [0168] 根据示例性实施例,移动终端 100 可以从显示设备请求附加信息 200 通过短距离无线通信(蓝牙、Zigbee、NFC、WFD、UWB、IrDA等)、移动通信(例如2G/3G/4G、Wibro等)或无线局域网(Wi -Fi:ad-hoc 模式,基础设施模式)。 [0169] 在操作 S 880 , 显示设备 200 可以将与选择的对象对应的附加信息发送到移动终端 100 . 例如,在选择与电影内容相关的对象的情况下,显示设备 200 可将与电影内容有关的附加信息(代表场景、预览视频、制作信息、概要信息、演员、导演信息、用户评论信息等)传输到移动终端 100 . [0170] 在选择与应用相关的对象的情况下,显示设备 200 可以向移动终端发送关于应用程序的附加信息(例如,应用程序的说明、应用程序审查信息、应用程序更新信息等) 100 . [0171] 根据示例性实施例,在选择与照片有关的对象的情况下,显示装置 200 可以将包括照片的元数据(例如,拍摄地点、拍摄时间等)、与照片中的人物相关的信息(例如,报纸文章、外观电影、代表性音乐等)等附加信息传输到 移动终端 100 . [0172] 根据示例性实施例,在选择与音乐有关的对象的情况下,显示装置 200 可以向移动终端发送关于音乐的附加信息,包括专辑信息、音乐视频、预告视频、预听信息、报纸文章、歌手信息等 100 . [0173] 根据示例性实施例,在选择与网站有关的对象的情况下,显示装置 200 可能会向移动终端发送附加信息,包括有关网站的预览信息 100 . [0174] 根据示例性实施例,在选择与EPG有关的对象的情况下,显示装置 200 可以向移动终端发送关于EPG的附加信息,包括广播节目概要、每集的预览信息等 100 . 在选择与购物项目有关的对象的情况下,显示装置 200可以向移动终端发送关于购物项目的附加信息,包括商品信息、订单信息、推荐信息等 100 . [0175] 根据示例性实施例,显示装置 200 可以将先前存储在存储单元中的附加信息发送到移动终端 100 . 如果附加信息的链接信息仅存储在存储单元中,则显示设备 200 可能会收到来自服务器的附加信息 300 并将接收到的附加信息发送给移动终端 100 . 显示装置 200 可以在搜索引擎或网站中搜索与对象相关的附加信息,并将找到的附加信息提供给移动终端 100 . [0176] 在操作 S 890 , 移动端 100 可以显示获得的附加信息。 移动终端 100 可以基于用户输入控制显示的附加信息。 现在将参考图3详细描述这一点。 9. [0177] 如上所述,根据示例性实施例,用户可以搜索和/或选择与显示在外部显示设备上的内容有关的对象 200 通过手机端的简单输入 100 并确认与所选对象有关的附加信息,以确定是否接收相应的内容。 [0178] 如图。 图9是示出显示装置的方法的流程图 200 感应移动终端的输入 100 并且根据示例性实施例提供附加信息。 附图之间的冗余描述。 8和9在此省略。 [0179] 参考图。 参照图9,根据示例性实施例,移动终端 100 可以在操作 S 中接收第一输入 910 和显示设备 200 可感应移动终端的输入 100 . [0180] 例如,在操作 S 920 , 显示设备 200 可以感测移动终端的第一输入 100 用于选择对象。 操作 S 930 通过 S 960 图。 9 对应于操作 S 810 通过 S 860 图。 与图8相同,因此这里将省略对其的重复描述。 在操作 S 970 , 显示设备 200 可以感测移动终端的第二输入 100 用于获取与所选对象对应的附加信息。 操作 S 980 通过 S 995 图。 9 对应于操作 S 870 通过 S 890 图。 与图8相同,因此这里将省略对其的重复描述。 [0181] 移动终端的第一输入和第二输入 100 可以包括运动输入(例如,3D运动输入、旋转运动输入等)、键输入、触摸输入、弯曲输入和语音输入中的至少一种。 [0182] 根据示例性实施例,在第一输入和第二输入是动作输入的情况下,显示装置 200 可以感知移动终端的动作 100 通过相机。 例如,在用户移动移动终端的情况下 100 上下左右或旋转移动终端 100 , 显示设备 200 可感应移动终端的上下左右运动 100 或者移动终端的旋转 100 . [0183] 根据示例性实施例,在第一输入和第二输入是弯曲输入的情况下,显示装置 200 可以感测移动终端的弯曲运动 100 通过相机。 例如,显示设备 200 可以感测移动终端的弯曲位置(坐标值) 100 、弯曲方向、弯曲角度、弯曲速度、弯曲频率、弯曲运动发生时间、弯曲运动持续时间段等。 [0184] 根据示例性实施例,在第一输入和第二输入是触摸输入的情况下,显示装置 200可以通过摄像头感知用户的触摸手势。 [0185] 根据示例性实施例,在第一输入和第二输入是语音输入的情况下,显示装置 200 可以通过麦克风感测用户的语音输入。 [0186] 也就是说,根据示例性实施例,显示装置 200 可以感测第一输入或第二输入以验证从移动终端接收的用于选择对象的信号 100 或用于请求对应于对象的附加信息的信号。 例如,在显示设备 200 感测移动终端的动作输入 100 向右(+X轴方向)移动并从移动终端、显示设备接收用于将选择区域向左移动一格的控制信号 200 可以向移动终端请求控制(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.099 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.100 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.100 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.275 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.276 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103577138A(String), CN103577138B(String), EP2690880A1(String), IN1206DELNP2015A(String), JP2014027659A(String), JP6335448B2(String), KR101971624B1(String), KR1020140019078A(String), TW201412097A(String), TWI574557B(String), US20140028921A1(String), US20170118436A1(String), US9549143B2(String), WO2014017759A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.294 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), CN103577138A(String), 1049974(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), CN103577138B(String), 1049975(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), EP2690880A1(String), 1049976(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), IN1206DELNP2015A(String), 1049977(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), JP2014027659A(String), 1049978(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.460 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), JP6335448B2(String), 1049979(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), KR101971624B1(String), 1049980(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.527 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), KR1020140019078A(String), 1049981(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.561 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), TW201412097A(String), 1049982(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.594 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.594 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.594 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), TWI574557B(String), 1049983(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.627 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), US20140028921A1(String), 1049984(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), US20170118436A1(String), 1049985(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.696 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), US9549143B2(String), 1049986(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271674(Integer), WO2014017759A1(String), 1049987(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9549143B2(String), US9549143B2(String), 1484582400(Integer), 271674(Integer), 186002(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.796 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.842 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.877 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186004(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.911 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186004(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:04.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186004(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.014 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.015 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 186004(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.049 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.066 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.067 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.101 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.102 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.154 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.172 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186004(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20150067572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method for setting virtual keyboard of mobile terminal(String), 移动终端及移动终端虚拟键盘设置方法(String), US20150067572A1(String), Disclosed are a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. The method includes: setting a virtual keyboard on a corner of a display screen of a mobile terminal and displaying same in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; and after receiving expression information input through the key display area, displaying the expression information in the symbol display area. The disclosure displays a virtual keyboard on a display screen in the form of a sector area so that a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience.(String), 本发明公开了一种移动终端及移动终端虚拟键盘的设置方法。 该方法包括:将虚拟键盘设置在移动终端显示屏的一角,并以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为 扇形区为重点展示区; 接收到通过按键显示区输入的表情信息后,在符号显示区显示表情信息。 本发明将虚拟键盘以扇形区域的形式显示在显示屏上,方便用户单手在移动终端上输入信息,大大提高了用户的操作效率,改善了用户体验。(String), US14/389046(String), 1340035200(Integer), US20150067572A1(String), 1425484800(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 5(Integer), US20100131900A1 | US20100241985A1 | US20120062465A1 | US20120075194A1 | US20130234949A1(String), 16(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.739 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186005(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.885 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.886 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\f8dcdba7aad24a98aeeae3366bcde53c.png(String), 186005(Integer), f8dcdba7aad24a98aeeae3366bcde53c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.939 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for setting virtual keyboard of mobile terminal(String), 移动终端及移动终端虚拟键盘设置方法(String), US20150067572A1(String), Disclosed are a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. The method includes: setting a virtual keyboard on a corner of a display screen of a mobile terminal and displaying same in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; and after receiving expression information input through the key display area, displaying the expression information in the symbol display area. The disclosure displays a virtual keyboard on a display screen in the form of a sector area so that a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience.(String), 本发明公开了一种移动终端及移动终端虚拟键盘的设置方法。 该方法包括:将虚拟键盘设置在移动终端显示屏的一角,并以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为 扇形区为重点展示区; 接收到通过按键显示区输入的表情信息后,在符号显示区显示表情信息。 本发明将虚拟键盘以扇形区域的形式显示在显示屏上,方便用户单手在移动终端上输入信息,大大提高了用户的操作效率,改善了用户体验。(String), US14/389046(String), 1340035200(Integer), US20150067572A1(String), 1425484800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 5(Integer), US20100131900A1 | US20100241985A1 | US20120062465A1 | US20120075194A1 | US20130234949A1(String), \20230420\f8dcdba7aad24a98aeeae3366bcde53c.png(String), 16(Integer), 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:05.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.010 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 1. A method for setting a virtual keyboard of a mobile terminal, comprising:setting a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, wherein an arc-shaped area of the sector area is a symbol display area, and a remaining area of the sector area is a key display area;after receiving expression information which is input through the key display area, displaying the expression information in the symbol display area.(String), 1.根据权利要求2所述的移动终端虚拟键盘的设置方法,还包括:在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角之后,设置虚拟键盘的扇形区域在移动终端显示屏上的显示大小。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 2. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after inputting the expression information through the key display area, hiding the virtual keyboard when it is detected that the display screen is touched by a preset first operational motion in the key display area.(String), 12.根据权利要求3所述的移动终端虚拟键盘的设置方法,还包括:在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角之后,设置虚拟键盘的扇形区域在移动终端显示屏上的显示大小。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 3. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after inputting the expression information through the key display area, changing a display position of the sector area on the display screen when it is detected that the display screen is touched by a preset second operational motion in the key display area.(String), 13.根据权利要求4所述的移动终端虚拟键盘的设置方法,还包括:在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角之后,设置虚拟键盘的扇形区域在移动终端显示屏上的显示大小。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 4. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after displaying the expression information in the symbol display area, displaying one or more operational options around the symbol display area and perform operation according to a selected operational option when it is detected that the symbol display area has been pressed for a preset period of time.(String), 14.根据权利要求7所述的移动终端,其中设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域在显示器上的显示大小移动终端屏幕。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 5. The method for setting a virtual keyboard of a mobile terminal according to claim 1, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 15.根据权利要求8所述的移动终端,其中设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域在显示器上的显示大小移动终端屏幕。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 6. A mobile terminal comprising a setting module and a processing module, whereinthe setting module is configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, and provide a symbol display area and a key display area of the sector area for the processing module, wherein an arc-shaped area of the sector area is the symbol display area, and a remaining area of the sector area is the key display area;the processing module is configured to receive the symbol display area and the key display area in the sector area provided by the setting module, and after receiving expression information which is input through the key display area, display the expression information in the symbol display area.(String), 16.根据权利要求9所述的移动终端,其中设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域在显示器上的显示大小移动终端屏幕。(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 7. The mobile terminal according to claim 6, further comprising:a virtual keyboard hiding module configured to, when it is detected that the display screen is touched by a preset first operational motion in the key display area, hide the virtual keyboard.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 8. The mobile terminal according to claim 6, further comprising:a sector area display position adjusting module configured to, when it is detected that the display screen is touched by a preset second operational motion in the key display area, change a display position of the sector area on the display screen.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 9. The mobile terminal according to claim 6, further comprising:an operational option prompt module configured to, after the expression information is displayed in the symbol display area and after it is detected that the symbol display area has been pressed for a preset period of time, display one or more operational options around the symbol display area and perform operation according to a selected operational option.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 10. The mobile terminal according to claim 6, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 11. The method for setting a virtual keyboard of a mobile terminal according to claim 2, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 12. The method for setting a virtual keyboard of a mobile terminal according to claim 3, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 13. The method for setting a virtual keyboard of a mobile terminal according to claim 4, further comprising:after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, setting a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 12(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 14. The mobile terminal according to claim 7, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 15. The mobile terminal according to claim 8, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 14(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186005(Integer), 16. The mobile terminal according to claim 9, whereinthe setting module is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal.(String), 1(Integer), 15(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.041 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.041 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.062 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.124 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_task a WHERE a.type = ? AND a.tid = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.124 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount ==> Parameters: 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.143 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.143 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Preparing: select a.id, a.type, a.uid as create_by, a.ctime as start_time, a.tid as project_id, a.mfields as field_num, a.mun as total, a.endtime as end_time, a.status, a.filename as file_name, a.filesize as file_size, a.downexcel as url, b.name as create_name, c.name as project_name, a.old_name from os_task a left join os_distribution b on a.uid = b.id left join os_thematic c on c.id = a.tid WHERE a.type = ? and a.tid = ? order by a.ctime desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.144 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.getPageList ==> Parameters: 1(Integer), 226(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.163 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.TaskMapper.getPageList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.356 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186005(Integer), FIELD [0001]The disclosure relates to the field of mobile communication, and particularly to a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. BACKGROUND [0002]With the popularization of touch screens, display screens of mobile terminals tend to become larger. Existing 3.2-inch and 3.5-inch display screens have been gradually replaced by 4.0-inch, 4.3-inch and 5.3-inch screens, and even 6-inch and 7-inch display screens have even emerged. Since all existing virtual keyboards are square and located at the bottom of mobile terminals, when a display screen of a mobile terminal becomes larger, the resulting problem is that the whole screen is hardly covered by operation with one hand, thus reducing the operating efficiency and increasing the difficulty in operation and thereby affecting the user experience. SUMMARY [0003]The disclosure is to provide a mobile terminal and a method for setting a virtual keyboard of a mobile terminal to solve the problem of inconvenient input operation by a user with one hand on a mobile terminal having a large display screen in the existing technology. [0004]To solve the problem, the disclosure provides a method for setting a virtual keyboard of a mobile terminal on one hand, including the following steps: [0005]A virtual keyboard is set on a corner of a display screen of a mobile terminal and is displayed in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; [0006]after receiving expression information which is input through the key display area, the expression information is displayed in the symbol display area. [0007]Further, after the expression information is input through the key display area, the method may further include: when it is detected that the display screen is touched by a preset first operational motion in the key display area, the virtual keyboard is hided. [0008]Further, after the expression information is input through the key display area, the method may further include: when it is detected that the display screen is touched by a preset second operational motion in the key display area, the display position of the sector area is changed on the display screen. [0009]Further, after the expression information is displayed in the symbol display area, the method may further include: [0010]when it is detected that the symbol display area has been pressed for a preset period of time, one or more operational options is displayed around the symbol display area and operation is performed according to a selected operational option. [0011]Further, after the virtual keyboard is set on the corner of the display screen of the mobile terminal and is displayed in the form of the sector area, the method may further include: [0012]a display size of the sector area of the virtual keyboard is set on the display screen of the mobile terminal. [0013]The disclosure may further provide a mobile terminal on the other hand, including a setting module and a processing module, wherein [0014]the setting module is configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, and provide a symbol display area and a key display area of the sector area for the processing module, wherein the arc-shaped area of the sector area is the symbol display area, and the remaining area of the sector area is the key display area; [0015]the processing module is configured to receive the symbol display area and the key display area in the sector area provided by the setting module, and after receiving expression information input through the key display area, display the expression information in the symbol display area. [0016]Further, the mobile terminal may further include a virtual keyboard hiding module configured to, when it is detected that the display screen is touched by a preset first operational motion in the key display area, hide the virtual keyboard. [0017]Further, the mobile terminal may further include a sector area display position adjusting module configured to, when it is detected that the display screen is touched by a preset second operational motion in the key display area, change the display position of the sector area on the display screen. [0018]Further, the mobile terminal may further include an operational option prompt module configured to, after the expression information is displayed in the symbol display area and after it is detected that the symbol display area has been pressed for a preset period of time, display one or more operational options around the symbol display area and perform operation according to a selected operational option. [0019]Further, the setting module may be further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on the corner of the display screen of the mobile terminal, set a display size of the sector area of the virtual keyboard on the display screen of the mobile terminal. [0020]The disclosure has the following beneficial effect: [0021]The disclosure displays a virtual keyboard in the form of a sector area on a display screen so that a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS [0022]FIG. 1 is a flowchart of a method for setting a virtual keyboard of a mobile terminal in an embodiment of the disclosure; [0023]FIG. 2 is a diagram of the effect of displaying a virtual keyboard on a display screen of a mobile terminal in an embodiment of the disclosure; [0024]FIG. 3 is a comparison diagram of displaying and hiding a virtual keyboard on a display screen of a mobile terminal in an embodiment of the disclosure; [0025]FIG. 4 is a comparison diagram of displaying a virtual keyboard at the left and right ends of a display screen of a mobile terminal in an embodiment of the disclosure; [0026]FIG. 5 is a diagram of the effect of operating expression information in a symbol display area in an embodiment of the disclosure; [0027]FIG. 6 is a diagram of the effect of further operating expression information in a symbol display area in an embodiment of the disclosure; [0028]FIG. 7 is a structural diagram of a mobile terminal in an embodiment of the disclosure; and [0029]FIG. 8 is a structural diagram of another mobile terminal in an embodiment of the disclosure. DETAILED DESCRIPTION [0030]To solve the problem of inconvenient input operation of a user on a mobile terminal having a large display screen with one hand, the disclosure provides a mobile terminal and a method for setting a virtual keyboard of a mobile terminal. The disclosure will be further described in details below in combination with the accompanying drawings and embodiments. It should be understood that the embodiments described herein are only used for explaining the disclosure, instead of limiting the disclosure. [0031]As shown in FIG. 1, an embodiment of the disclosure relates to a method for setting a virtual keyboard of a mobile terminal, including the following steps: [0032]Step 101: a virtual keyboard is set on a corner of a display screen of a mobile terminal and is displayed in the form of a sector area, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; [0033]here, the virtual keyboard is a keyboard displayed on the display screen of the mobile terminal, but not a physical keyboard really existing on the mobile terminal; the virtual keyboard may be a keyboard having an input mode like numbers, letters, symbols or strokes etc.; the size of the virtual keyboard is set according to a great amount of acquired data (the data of a moving range of a thumb when a user operates the mobile terminal with one hand), and the data tested at work; [0034]the physical size of the sector area, which is fixed within a range and is not related to the display screen of the mobile terminal, does not need to increase with the increase of the display screen of the mobile terminal; three display sizes including a large size, a medium sides and a small size may be set for the sector area for a user to select so as to be applicable to different thumb sizes of users; of course, more or less levels may be also provided; generally, the three sizes, i.e. the large size, the medium size, and the small size can meet the use requirement of most users; [0035]Step 102: after expression information input through the key display area is received, the expression information is displayed in the symbol display area; [0036]here, the expression information refers to information input by a user through the virtual keyboard, which may be a phone number, and may be also information including texts, numbers, letters and/or symbols etc.; [0037]since the virtual keyboard will shield a part of the display screen of the mobile terminal, a user may need to hide the virtual keyboard sometimes, i.e. not display the virtual keyboard on the display screen of the mobile terminal; in this case, the user only needs to touch the display screen of the mobile terminal with a preset first operational motion in the key display area, then the virtual keyboard will be hidden; the preset first operational motion may be any preset operational motion, e.g. a sweep with horizontal straight line, a sweep with a vertical straight line, a sweep with an arc in a specific direction, a sweep with curve of a specific shape of a number or a letter, or other similar operation; [0038]in addition, since users have different habits to operate with the left hand or the right hand, the virtual keyboard needs to be set at the lower left corner, the upper right corner, upper left corner or the lower right corner of the display screen of the mobile terminal for different users. Therefore, settings need to be provided for the left hand and the right hand to change the position of a sector-shaped dial plate on the screen; [0039]when the virtual keyboard is displayed on the mobile terminal and when a user touches the display screen with a preset second operational motion in the key display area, the display position of the sector area on the display screen is changed; the preset second operational motion may be any preset operational motion, e.g. a sweep with horizontal straight line, a sweep with a vertical straight line, a sweep with an arc in a specific direction, a sweep with curve of a specific shape of a number or a letter, or other similar operation; of course, the first operational motion cannot be the same with the second operational motion; in the embodiment, for example, when a user sweeps with a straight line from the left to the right in the key display area, the sector area of the virtual keyboard is displayed at the lower left corner of the display screen; when a user sweeps with a straight line from the right to the left in the key display area, the sector area of the virtual keyboard is displayed at the lower right corner of the display screen; when a user sweeps with a straight line from the top down in the key display area, the sector area of the virtual keyboard is displayed at the upper left corner of the display screen; when a user sweeps with a straight line from the bottom up in the key display area, the sector area of the virtual keyboard is displayed at the upper right corner of the sector area; [0040]in Step 102, after the expression information is displayed in the symbol display area, the following processing is further included: [0041]after a user presses the symbol display area for a preset period of time, one or more operational options is displayed around the symbol display area to guide the user to select an operational option to finish an operation, e.g. if a phone number is displayed in the symbol display area, after the user presses the displayed phone number for 3 s (it may be other time values, any setting), operational options, such as voice call, video call, save etc., are displayed around the phone number to guide the user to a further operation. [0042]Detailed description will be provided below by taking a virtual keyboard which is a dial plate as an example. [0043]FIG. 2 shows diagram of the effect of displaying a virtual keyboard on a display screen of a mobile terminal in the present embodiment, wherein a new dial plate is sector-shaped; the outermost sector area is a number display area and the remaining internal area is a number key area. [0044]FIG. 3 shows a comparison diagram of displaying and hiding a virtual keyboard on a display screen of a mobile terminal in the present embodiment. A dial plate can be hidden by dragging a number area within the dashed lines, specifically including: sliding in the number key area, and recognizing by the mobile terminal that the sliding direction is between 3 o'clock and 6 o'clock, then executing an operation of hiding the dial plate. [0045]FIG. 4 shows a comparison diagram of displaying a virtual keyboard at the left and right ends of a display screen of a mobile terminal in the present embodiment. A number key area is dragged to the left to switch a dial plate to a mode suitable to be used by the left hand, specifically including: sliding in the number key area, and recognizing by the mobile terminal that the sliding direction is between 6 o'clock and 9 o'clock, then executing an operation of changing a right hand-adaptive dial plate to a left hand-adaptive plate, i.e. changing the dial plate from being displayed at the lower right corner to being displayed at the lower left corner. [0046]In the present embodiment, 3 o'clock, 6 o'clock and 9 o'clock means that the middle point of the upper border line of the display screen of the mobile terminal is recorded as 12 o'clock; the middle point of the lower border line of the display screen of the mobile terminal is recorded as 6 o'clock, the middle point of the left border line of the display screen of the mobile terminal is recorded as 9 o'clock and the middle point of the right border lien of the display screen of the mobile terminal is recorded as 3 o'clock. [0047]FIG. 5 shows a diagram of the effect of operating expression information in a symbol display area in the present embodiment, wherein the dashed line oval represents a position that a user can press for a long period of time; after a number display area is pressed for a certain long period of time, an operational option which can be executed according to an entered number is displayed around the number display area of the display screen and the user is guided to perform the next gesture operation. In the present embodiment, if a finger of the user slides along the downward arrow towards the option item of Send Short Message Service (SMS), an operation of writing a text message to the number is executed; after the user is practiced, the operation of writing a text message to the number can be executed by a quick downward sliding operation after pressing the number display area. [0048]As shown in FIG. 6, if a gesture operation is performed once in FIG. 5, a subsequent operational option is required, then subsequent operational options are displayed on an interface and the user is guided to perform a secondary gesture operation. In the interface displayed in FIG. 5, if a finger of the user slides to the option item of Save Contact along the rightward arrow in the figure, then the option items of New Contact and Add to Contact are respectively displayed above and below the option item of Save Contact. At the moment, the finger of the user is located at the dashed line oval in FIG. 6, and an operation of creating a name card is executed if the finger slides upwards to the option item of New Contact. After the user is practiced, the operation of creating a name card can be executed by quickly siding rightwards and then upwards after pressing the number display area. [0049]As shown in FIG. 7, an embodiment of the disclosure further relates to a mobile terminal for realizing the method above, including a setting module 201 and a processing module 202, wherein [0050]the setting module 201 is configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, wherein the arc-shaped area of a sector area is a symbol display area, and the remaining area of the sector area is a key display area; and provide the symbol display area and key display area of the set sector area for the processing module 202, [0051]the processing module 202 is configured to receive the symbol display area and the key display area in the sector area provided by the setting module 201, and after receiving expression information which is input through the key display area, display the expression information in the symbol display area. [0052]To realize better technical effect, as shown in FIG. 8, an embodiment of the disclosure further relates to a mobile terminal for realizing the method above, including: [0053]a setting module 301, configured to set a virtual keyboard to be displayed in the form of a sector area on a corner of a display screen of a mobile terminal, wherein the arc-shaped area of the sector area is a symbol display area, and the remaining area of the sector area is a key display area; the setting module 301 is further configured to, after setting the virtual keyboard to be displayed in the form of the sector area on a corner of the display screen of the mobile terminal, set a display size of the virtual keyboard on the display screen. [0054]A processing module 302 configured to, after receiving expression information input through the key display area, display the expression information in the symbol display area. [0055]The mobile terminal further includes a virtual keyboard hiding module 303 which is configured to receive from the processing module 302 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the virtual keyboard hiding module locates, and when it is detected that the display screen is touched by a user with a preset first operational motion in the key display area, hide the virtual keyboard; accordingly, the processing module 302 is further configured to send the virtual keyboard hiding module 303 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the processing module locates. [0056]The mobile terminal further includes a sector area display position adjusting module 304 configured to receive from the processing module 302 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the sector area display position adjusting module locates, and when it is detected that the display screen is touched by a user with a preset second operational motion in the key display area, change the display position of the sector area on the display screen; accordingly, the processing module 302 is further configured to send the sector area display position adjusting module 304 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the processing module locates. [0057]The mobile terminal further includes an operational option prompt module 305 configured to, receive the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the operational option prompt module locates from the processing module 302, and after displaying the expression information in the symbol display area and after it is detected that the symbol display area is pressed by a user for a preset period of time, display one or more operational options around the symbol display area and guide the user to select an operational option to complete an operation; accordingly, the processing module 302 is further configured to send the operational option prompt module 305 the symbol display area and the key display area of the sector area of the display screen of the mobile terminal where the processing module locates. [0058]The mobile terminals in the embodiments above may be devices including mobile phones, Personal Digital Assistants (PDA) and tablet computers etc., and may be also other devices having a touch screen function and capable of processing data. [0059]It can be seen from the embodiments above that the disclosure displays a virtual keyboard in the form of a sector area in a display screen, and a user can conveniently input information on a mobile terminal by one hand, thereby greatly increasing the operating efficiency for the user, and improving the user experience. [0060]Although the preferred embodiments of the disclosure have been disclosed for the purpose of demonstration, it will be realized that various improvements, additions, and replacements are possible for those skilled in the art. Therefore, the scope of the disclosure is not intended to limited to the above embodiments.(String), 场地 [0001] 本发明涉及移动通信领域,尤其涉及一种移动终端及移动终端虚拟键盘的设置方法。 背景 [0002] 随着触摸屏的普及,移动终端的显示屏幕趋于变大。 现有的3.2英寸、3.5英寸的显示屏逐渐被4.0英寸、4.3英寸、5.3英寸的显示屏所取代,甚至出现了6英寸、7英寸的显示屏。 由于现有的虚拟键盘都是方形的,并且位于移动终端的底部,当移动终端的显示屏幕变大时,带来的问题是单手操作很难覆盖整个屏幕,降低了操作效率, 增加操作难度,影响用户体验。 概括 [0003] 本发明的目的在于提供一种移动终端及移动终端虚拟键盘的设置方法,以解决现有技术中用户在大显示屏移动终端上单手输入操作不便的问题。 [0004] 为解决上述问题,本发明一方面提供了一种移动终端虚拟键盘的设置方法,包括以下步骤: [0005] 虚拟键盘设置在移动终端显示屏的一角,以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,扇形的其余区域 area为重点显示区域; [0006] 接收到通过按键显示区输入的表情信息后,将表情信息显示在符号显示区中。 [0007] 进一步地,在通过按键显示区输入表情信息之后,该方法还可以包括: 当检测到按键显示区中预设的第一操作动作触碰显示屏时,隐藏虚拟键盘。 [0008] 进一步地,在通过按键显示区输入表情信息之后,该方法还包括:当检测到按键显示区中预设的第二操作动作触碰显示屏时,扇形区的显示位置为: 在显示屏幕上改变。 [0009] 进一步的,所述符号显示区显示所述表情信息后,所述方法还包括: [0010] 当检测到符号显示区域被按下预设时间时,在符号显示区域周围显示一个或多个操作选项,并根据选择的操作选项进行操作。 [0011] 进一步的,所述虚拟键盘设置在所述移动终端显示屏的一角,并以扇形区域的形式显示后,所述方法还包括: [0012] 在移动终端的显示屏上设置虚拟键盘扇区的显示大小。 [0013] 另一方面,本发明还可以提供一种移动终端,包括设置模块和处理模块,其中 [0014] 设置模块,用于设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角,并提供扇形区域的符号显示区域和按键显示区域供处理 模块,其中扇区的弧形区域为符号显示区,扇区的剩余区域为按键显示区; [0015] 处理模块,用于接收设置模块提供的扇区中的符号显示区和按键显示区,并在接收到通过按键显示区输入的表情信息后,在符号显示区中显示表情信息。 [0016] 进一步的,该移动终端还可以包括:虚拟键盘隐藏模块,用于在检测到所述按键显示区域中预设的第一操作动作触碰所述显示屏时,隐藏所述虚拟键盘。 [0017]进一步地,该移动终端还可以包括扇形区域显示位置调整模块,用于在检测到预设的第二操作动作在按键显示区域触碰显示屏时,改变扇形区域在按键显示区域的显示位置。 显示屏。 [0018] 进一步地,移动终端还可以包括操作选项提示模块,用于在符号显示区域显示表情信息后,检测到符号显示区域被按下预设时间后,显示一个或 更多操作选项围绕符号显示区,根据选中的操作选项进行操作。 [0019] 进一步地,设置模块还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘的扇形区域的显示大小 在移动终端的显示屏上。 [0020] 本发明具有以下有益效果: [0021] 本发明在显示屏上以扇形区域的形式显示虚拟键盘,使用户可以方便地用一只手在移动终端上输入信息,大大提高了用户的操作效率,改善了用户体验。 附图的简要说明 [0022] 图1为本发明实施例中移动终端虚拟键盘的设置方法流程图; [0023] 图2为本发明实施例中在移动终端的显示屏上显示虚拟键盘的效果图。 [0024] 图3为本发明实施例中移动终端显示屏显示和隐藏虚拟键盘的对比图。 [0025] 图4为本发明实施例中移动终端显示屏左右两端显示虚拟键盘的对比图。 [0026] 图5为本发明实施例中符号显示区操作表情信息的效果图。 [0027] 图6为本发明实施例中符号显示区进一步操作表情信息的效果图。 [0028] 图7为本发明实施例中移动终端的结构图; 和 [0029] 图8为本发明实施例的另一种移动终端的结构图。 详细说明 [0030] 为解决用户在大显示屏移动终端上单手输入操作不便的问题,本发明提供了一种移动终端及移动终端虚拟键盘的设置方法。 下面结合附图及实施例对本发明作进一步详细说明。 应当理解,此处所描述的实施例仅仅用于解释本发明,并不用于限制本发明。 [0031] 如图1所示,本发明实施例涉及一种移动终端虚拟键盘的设置方法,包括以下步骤: [0032] 步 101 :虚拟键盘设置在移动终端显示屏的一角,以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为符号显示区域。 扇区为重点显示区; [0033] 这里,虚拟键盘是显示在移动终端显示屏上的键盘,而不是移动终端上真实存在的物理键盘。 虚拟键盘可以是具有数字、字母、符号或笔画等输入方式的键盘。 虚拟键盘的大小是根据获取的大量数据(用户单手操作移动终端时拇指移动幅度的数据)和工作中测试的数据来设置的。 [0034]扇区的物理大小,固定在一个范围内,与移动终端的显示屏无关,不需要随着移动终端显示屏的增大而增大。 扇形区域可以设置大、中、小三种显示尺寸供用户选择,以适应不同拇指大小的用户。 当然,也可以提供更多或更少的层级。 一般来说,大号、中号、小号三种尺寸可以满足大部分用户的使用需求; [0035] 步 102 :接收到按键显示区输入的表情信息后,在符号显示区显示表情信息; [0036] 这里,表情信息是指用户通过虚拟键盘输入的信息,可以是电话号码,也可以是包括文字、数字、字母和/或符号等的信息。 [0037] 由于虚拟键盘会遮挡一部分移动终端的显示屏,用户有时可能需要隐藏虚拟键盘,即不在移动终端的显示屏上显示虚拟键盘。 此时,用户只需在按键显示区域以预设的第一操作动作触碰移动终端的显示屏,虚拟键盘就会被隐藏。 预设的第一操作动作可以是任何预设的操作动作,例如 水平直线扫掠、垂直直线扫掠、特定方向圆弧扫掠、数字或字母特定形状曲线扫掠等类似操作; [0038] 另外,由于用户用左手或右手操作的习惯不同,虚拟键盘需要设置在显示屏的左下角、右上角、左上角或右下角。 针对不同用户的移动终端。 因此,需要对左右手进行设置,改变扇形表盘在屏幕上的位置; [0039] 当虚拟键盘显示在移动终端上时,当用户在按键显示区域以预设的第二操作动作触碰显示屏时,改变扇形区域在显示屏上的显示位置。 预设的第二操作动作可以是任何预设的操作动作,例如 水平直线扫掠、垂直直线扫掠、特定方向圆弧扫掠、数字或字母特定形状曲线扫掠等类似操作; 当然,第一操作动作不能与第二操作动作相同; 在本实施例中,例如,当用户在按键显示区域从左向右直线扫动时,在显示屏的左下角显示虚拟键盘的扇形区域。 当用户在按键显示区由右向左直线扫动时,在显示屏右下角显示虚拟键盘的扇区。 当用户在按键显示区从上向下直线扫动时,在显示屏的左上角显示虚拟键盘的扇形区域。 当用户在按键显示区用直线自下而上扫过时,虚拟键盘的扇区显示在扇区的右上角。 [0040] 在步骤 102 ,在符号显示区显示表情信息后,还包括以下处理: [0041] 当用户按下符号显示区域预设时间后,符号显示区域周围显示一个或多个操作选项,以引导用户选择操作选项以完成操作,例如 如果符号显示区显示电话号码,用户长按显示的电话号码3s后(可以是其他时间值,任意设置),语音通话、视频通话、保存等操作选项, 在电话号码周围显示,以引导用户进行进一步的操作。 [0042]下面以虚拟键盘即拨号盘为例进行详细说明。 [0043] 图2为本实施例在移动终端的显示屏上显示虚拟键盘的效果图,其中新表盘为扇形。 最外面的扇区是数字显示区,其余的内部区是数字键区。 [0044] 图3示出了本实施例中移动终端显示屏显示和隐藏虚拟键盘的对比图。 可以通过拖动虚线内的数字区域来隐藏表盘,具体包括:在数字键区域滑动,移动端识别滑动方向为3点到6点之间,然后执行 隐藏表盘的操作。 [0045] 图4为本实施例中移动终端显示屏左右两端显示虚拟键盘的对比图。 向左拖动数字键区域,将表盘切换到适合左手使用的模式,具体包括:在数字键区域滑动,移动终端识别滑动方向在6°之间。 点钟和9点钟,然后执行将右手自适应表盘改为左手自适应表盘的操作,即将表盘由右下角显示改为左下角显示 . [0046] 在本实施例中,3点钟、6点钟和9点钟是指移动终端显示屏的上边框线的中点记为12点钟; 移动终端显示屏下边框线的中点记为6点,移动终端显示屏左边框线的中点记为9点,中间 记录移动终端显示屏右边框线的点为3点。 [0047] 图5为本实施例中符号显示区操作表情信息的效果图,其中虚线椭圆表示用户可以长时间按下的位置。 在数字显示区域被长按一定时间后,在显示屏的数字显示区域周围显示可根据输入的数字执行的操作选项,引导用户进行下一步的手势操作。 在本实施例中,如果用户的手指沿着向下的箭头向发送短信服务(SMS)选项项滑动,则执行向该号码写入短信的操作; 用户练习后,在按下号码显示区后,通过快速向下滑动操作,即可执行给号码写短信的操作。 [0048] 如图6所示,如果在图5中进行了一次手势操作,则需要进行后续的操作选项,则在界面上显示后续的操作选项,引导用户进行二次手势操作。 在图5显示的界面中,如果用户的手指沿着图中向右的箭头滑动到保存联系人选项,则在该选项的上方和下方分别显示新建联系人和添加到联系人选项。 的保存联系人。 此时,用户手指位于图6中虚线椭圆处,手指向上滑动至新建联系人选项,则执行创建名片的操作。 用户熟练后,按下数字显示区后快速向右再向上,即可执行制作名片的操作。 [0049] 如图7所示,本发明实施例还涉及一种实现上述方法的移动终端,包括设置模块 201 和一个处理模块 202 , 其中 [0050] 设置模块 201用于设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角,扇形区域的弧形区域为符号显示区域,其余区域为 扇区为重点显示区; 并为处理模块提供设置扇区的符号显示区和按键显示区 202 , [0051] 处理模块 202 用于接收设置模块提供的扇区中的符号显示区和按键显示区 201 ,接收到通过按键显示区输入的表情信息后,将表情信息显示在符号显示区。 [0052] 为实现更好的技术效果,如图8所示,本发明实施例还涉及一种实现上述方法的移动终端,包括: [0053] 设置模块 301 ,用于设置虚拟键盘在移动终端显示屏的一角以扇形区域的形式显示,扇形区域的弧形区域为符号显示区域,其余区域为 扇区为重点显示区; 设置模块 301 还用于在设置虚拟键盘以扇形区域的形式显示在移动终端显示屏的一角后,设置虚拟键盘在显示屏上的显示尺寸。 [0054] 一个处理模块 302 用于接收到按键显示区输入的表情信息后,在符号显示区显示表情信息。 [0055] 移动终端还包括虚拟键盘隐藏模块 303 它被配置为从处理模块接收 302 虚拟键盘隐藏模块所在的移动终端显示屏的扇区的符号显示区和按键显示区,当检测到用户以预设的第一操作动作触摸显示屏时 按键显示区,隐藏虚拟键盘; 相应地,处理模块 302 还用于发送虚拟键盘隐藏模块 303 所述处理模块所在的移动终端显示屏的扇区中的符号显示区和按键显示区。 [0056] 移动终端还包括扇区显示位置调整模块 304 配置为从处理模块接收 302 扇区显示位置调整模块所在的移动终端显示屏的扇区的符号显示区和按键显示区,当检测到用户以预设的第二操作触摸显示屏时 在按键显示区移动,改变扇形区在显示屏上的显示位置; 相应地,处理模块 302 还用于发送扇区显示位置调整模块 304 所述处理模块所在的移动终端显示屏的扇区中的符号显示区和按键显示区。 [0057] 移动终端还包括操作选项提示模块 305 用于从所述处理模块接收所述移动终端显示屏的所述操作选项提示模块所在扇形区域的符号显示区域和按键显示区域 302 ,在符号显示区显示表情信息,并检测到用户按下符号显示区预设时间后,在符号显示区周围显示一个或多个操作选项,引导用户进行操作。 选择一个操作选项来完成一个操作; 相应地,处理模块 302 还用于发送操作选项提示模块 305 所述处理模块所在的移动终端显示屏的扇区中的符号显示区和按键显示区。 [0058]上述实施例中的移动终端可以是手机、个人数字助理(Personal Digital Assistant,PDA)、平板电脑等设备,也可以是其他具有触摸屏功能的能够处理数据的设备。 [0059] 从以上实施例可以看出,本发明在显示屏中以扇形区域的形式显示虚拟键盘,用户可以方便地在移动终端上单手输入信息,大大提高了操作效率。 用户,提升用户体验。 [0060] 尽管出于示范的目的而公开了本公开的优选实施例,但是对于本领域的技术人员来说将认识到各种改进、添加和替换是可能的。 因此,本发明的范围并非旨在限于上述实施例。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.396 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102681670A(String), EP2824553A1(String), EP2824553A4(String), US20150067572A1(String), WO2013152558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.430 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.430 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.446 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.TaskMapper.selectList ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE (uid = ? AND type = ? AND status IN (?,?) AND tid = ?) ORDER BY ctime ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.446 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.TaskMapper.selectList ==> Parameters: 103(Integer), 1(Integer), 0(Integer), 1(Integer), 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.449 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.449 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.449 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 226(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.469 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.470 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.TaskMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102681670A(String), EP2824553A1(String), EP2824553A4(String), US20150067572A1(String), WO2013152558A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.573 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20150067572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102681670A(String), EP2824553A1(String), EP2824553A4(String), US20150067572A1(String), WO2013152558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271676(Integer), CN102681670A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.660 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271676(Integer), EP2824553A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271676(Integer), EP2824553A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271676(Integer), US20150067572A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271676(Integer), WO2013152558A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20150067572A1(String), US20150067572A1(String), 1425484800(Integer), 271676(Integer), 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.835 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), BAI, JINJIAN(String), 中兴通讯股份有限公司(String), BAI JINJIAN(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186005(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.949 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186005(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:06.984 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: BAI, JINJIAN(String), BAI JINJIAN(String), 0(Integer), 1681976166(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186005(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75859(Integer), 2(Integer), 186005(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75859(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.141 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.141 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.192 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.195 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.211 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.364 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186005(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.400 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10554877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.742 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10554877B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/240348(String), 1546531200(Integer), US10554877B2(String), 1580745600(Integer), 1580745600(Integer), 美国(String), 4(Integer), CN(String), 1(Integer), 15(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2012208876A | US20110013061A1 | US20130156345A1 | US20150109513A1 | WO2014097792A1(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.778 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186006(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\4ec9cbceb314498dae21a4e504d5d91c.png(String), 186006(Integer), 4ec9cbceb314498dae21a4e504d5d91c.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.962 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:07.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10554877B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/240348(String), 1546531200(Integer), US10554877B2(String), 1580745600(Integer), 1580745600(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 1(Integer), 15(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2012208876A | US20110013061A1 | US20130156345A1 | US20150109513A1 | WO2014097792A1(String), \20230420\4ec9cbceb314498dae21a4e504d5d91c.png(String), 14(Integer), 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.050 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 1. An image synthesis method for a mobile terminal, comprising:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel, wherein the initial location is a location of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data;wherein controlling the photosensitive element to generate the displacement at the initial location comprises:controlling, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location, comprising:controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 1.移动终端,包括:外壳、处理器、存储器、电路板和供电电路,其中,电路板设置在外壳围成的空间内,处理器和存储器设置在电路板上,供电电路用于为移动终端的电路或部件供电,存储器用于存储可执行文件程序代码,处理器用于通过读取内存中存储的可执行程序代码来运行与可执行程序代码对应的程序,执行:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦;控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素,其中,初始位置为感光元件在相位对焦时在移动终端中的位置基于移动终端中的感光元件的预设像素拍摄的物体;根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置;对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据;和根据第一感光数据与第二感光数据合成待摄对象的图像;其中,处理器还被配置为:通过微机电光学稳像系统控制感光元件在初始位置产生位移;和其中,处理器还被配置为:微机电光学稳像系统通过空间直角坐标系三轴方向的运动控制感光元件在初始位置产生位移,三轴方向的运动包括两个方向的平移运动水平面中的正交方向和绕垂直于水平面的轴的旋转运动。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 2. The image synthesis method according to claim 1, synthesizing the image of the object to be photographed according to the first photosensitive data and the second photosensitive data comprising:performing a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 12.根据权利要求11所述的移动终端,其中处理器还被配置为:将第二感光数据与第一感光数据进行补偿处理,根据补偿处理后的第二感光数据合成被摄体的图像。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 3. The image synthesis method according to claim 1, wherein the preset pixel is a masked pixel.(String), 13.根据权利要求11所述的移动终端,其中预设像素为屏蔽像素。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.051 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 4. The image synthesis method according to claim 1, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having a first module, a second module, a third module and a fourth module, andwhen performing the rotating movement, the method comprises at least one of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the method comprises at least one of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 14.根据权利要求11所述的移动终端,其中微机电光学防抖系统包括具有第一模块、第二模块、第三模块和第四模块的微机电系统,以及当执行旋转运动时,处理器被配置为执行以下至少一个动作:控制第一模块向上运动,第二模块向右运动,第三模块向左运动,第四模块向下运动,使微机电系统顺时针旋转;和控制第一模块向下运动,第二模块向左运动,第三模块向右运动,第四模块向上运动,使微机电系统逆时针旋转;和当执行平移运动时,处理器被配置为执行以下至少一个动作:控制第一模块和第四模块动作使微机电系统上下运动;和控制第二模块和第三模块采取动作使微机电系统左右移动。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 5. The image synthesis method according to claim 1, wherein the original pixel is a default pixel where a masked pixel is not reserved on the photosensitive element in the mobile terminal.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 6. An image synthesis apparatus for a mobile terminal, comprising a non-transitory computer-readable medium comprising computer-executable instructions stored thereon, and an instruction execution system which is configured by the instructions to implement acts of:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel, wherein the initial location is a location of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data;wherein the instruction execution system is further configured by the instructions to implement an act of:controlling, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location; andwherein the instruction execution system is further configured by the instructions to implement an act of:controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 0(Integer), 5(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 7. The image synthesis apparatus according to claim 6, wherein the instruction execution system is further configured by the instructions to implement an act of:perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 8. The image synthesis apparatus according to claim 6, wherein the preset pixel is a masked pixel.(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 9. The image synthesis apparatus according to claim 6, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having a first module, a second module, a third module and a fourth module, and when performing the rotating movement, the instruction execution system is further configured by the instructions to implement at least one act of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the instruction execution system is further configured by the instructions to implement at least one act of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 8(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.052 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 10. The image synthesis apparatus according to claim 6, wherein the original pixel is a default pixel where a masked pixel is not reserved on the photosensitive element in the mobile terminal.(String), 1(Integer), 9(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 11. A mobile terminal, comprising: a housing, a processor, a memory, a circuit board and a power supply circuit, wherein,the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel, wherein the initial location is a location of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data;wherein the processor is further configured to:control the photosensitive element to generate the displacement at the initial location by a micro-electromechanical optical image stabilization system; andwherein the processor is further configured to:control, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 0(Integer), 10(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 12. The mobile terminal according to claim 11, wherein the processor is further configured to:perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 13. The mobile terminal according to claim 11, wherein the preset pixel is a masked pixel.(String), 1(Integer), 12(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186006(Integer), 14. The mobile terminal according to claim 11, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having a first module, a second module, a third module and a fourth module, andwhen performing the rotating movement, the processor is configured to perform at least one act of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the processor is configured to perform at least one act of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 13(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.362 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186006(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The present application is a continuation application of a U.S. application Ser. No. 16/302,323, filed on Nov. 16, 2018, which is a national phase entry of International Application No. PCT/CN2017/087806, filed on Jun. 9, 2017, which claims priority from Chinese Patent Application No. 201610616090.6, filed on Jul. 29, 2016 by GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD., entitled “Image Synthesis Method and Device for Mobile Terminal, and Mobile Terminal”. The entire contents of the aforementioned applications are incorporated by reference herein. TECHNICAL FIELD [0002]The present disclosure relates to a field of mobile terminal technology, and in particular, to an image synthesis method and apparatus for a mobile terminal, and a mobile terminal. BACKGROUND [0003]Optical Image Stabilization (OIS) may effectively avoid image blur caused by jitter during a process of the user taking pictures with a mobile terminal. OIS uses a magnetically wrapped suspension lens to effectively overcome image blur caused by vibration of the mobile terminal. In the related art, the anti-shake is realized by a photosensitive element, of which the principles may be described as followings. The photosensitive element is fixed on a bracket that can move up, down, left, and right, and the direction and amplitude data of the shaking of the mobile terminal are sensed by a gyro sensor. After that, the gyro sensor transmits the data. Screening and amplification are performed on the data at the processor side to calculate the amount of movement of the photosensitive element that may compensate the jitter. During the process of the user taking pictures with the mobile terminal, it is also necessary to perform phase focusing on the scene to be photographed. In the related art, by hiding some masked pixels on the photosensitive element, and considering the distance between the pixels of the scene to be photographed and its changing factors, the focusing offset value may be determined to achieve the phase focusing. [0004]In this way, the masked pixels may only be used to detect the phase and cannot be used to display the image. The masked pixels may affect the quality of the image photographed. The higher the density of the masked pixels, the more accurate the phase focusing, but the worse the quality of the image photographed. SUMMARY [0005]The present disclosure aims to solve at least one of technical problems in the related art to some extent. [0006]Embodiments of the present disclosure provide an image synthesis method for the mobile terminal. The method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0007]Embodiments of the present disclosure also provide a micro-electromechanical optical image stabilization system. The system may include: a photosensitive element, configured to collect photosensitive data of an object to be photographed; and a micro-electromechanical system (MEMS), configured to control the photosensitive element to generate a displacement at an initial position. [0008]Embodiments of the present application propose a storage medium, when instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform an image synthesis method for the mobile terminal. The image synthesis method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0009]Additional aspects and advantages of embodiments of present disclosure will be given in part in the following descriptions, become apparent in part from the following descriptions, or be learned from the practice of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to make technical solutions according to embodiments of the present disclosure more apparent, drawings needed to be used in descriptions of the embodiments will be illustrated in the following. Obviously, the drawings to be illustrated in the following only represent some embodiments of the present disclosure, and other drawings can be obtained according to these drawings by those having ordinary skills in the related art without making creative labors. [0011]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a schematic diagram of preset pixels on a photosensitive element in an embodiment of the present disclosure. [0013]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0014]FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0015]FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) according to an embodiment of the present disclosure. [0016]FIG. 6 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0017]FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0018]FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0019]FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0020]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0021]The technical solutions in embodiments of the present disclosure are hereinafter described clearly and completely with reference to accompanying drawings in embodiments of the present disclosure. Apparently, embodiments described are a part of embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments in the present disclosure without creative labor shall fall in the protection scope of the present disclosure. [0022]The terms “first”, “second”, “third” and “fourth” and the like in the specification and claims of the present disclosure and the above drawings are used to distinguish different objects, and are not intended to describe a specific order. Moreover, the terms “comprise” and “have” and their variants are aim at covering non-exclusive “include”. For example, a process, a method, a system, a term or a device including a series of steps or units may be not limited to the listed steps or units, instead and alternatively, other steps or units which are not listed may be included, or other steps or units inherent for these process, method, term or device may be included in an embodiment. [0023]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. This embodiment takes an example where an image synthesis method for the mobile terminal is configured for an image synthesis apparatus for the mobile terminal. Embodiments of the present disclosure mat be applied during a process of a user paragraphing a subject to be photographed using the mobile terminal. [0024]Referring to FIG. 1, the image synthesis method of the mobile terminal may include followings. [0025]At block S11, a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0026]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0027]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0028]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0029]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0030]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, G, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0031]At block S12, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0032]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0033]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11. [0034]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0035]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0036]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0037]At block S13, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0038]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0039]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be controlled to return to the initial position to photograph the object to be photographed based on the preset pixel. [0040]At block S14, the object to be photographed is photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. [0041]In embodiments of the present disclosure, when the photosensitive element is controlled to return to the initial position, the object to be photographed is photographed based on the preset pixel, such that the photosensitive element collects the photosensitive data of the object to be photographed at the initial position as the second photosensitive data. [0042]In embodiments of the present disclosure, since the photosensitive element generates the displacement at the initial position, the original pixel is used to replace the masked pixel on the photosensitive element, and the obtained replaced pixel is the original pixel. Therefore, the mobile terminal may perform a compensation on the second photographic data based on the first photographic data so as to compensate for the masked pixel. [0043]At block S15, an image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. [0044]In embodiments of the present disclosure, the second photosensitive data are subjected to compensation processing using the first photosensitive data to synthesize an image of the object to be photographed according to the compensated second photosensitive data. [0045]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0046]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0047]Referring to FIG. 3, the micro-electromechanical optical image stabilization system may include a photosensitive element 100 and a micro-electromechanical system (MEMS) 200. The photosensitive element 100 is configured to collect photosensitive data of an object to be photographed. The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate a displacement at an initial position. [0048]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may include the photosensitive element 100. [0049]The photosensitive element 100 is configured to collect photosensitive data of the object to be photographed. [0050]In an embodiment, a masked pixel is set on the photosensitive element 100, in which the masked pixel is used to perform a phase focusing on the object to be photographed. [0051]In an embodiment, when the user uses the mobile terminal to photograph the object to be photographed, the phase focusing may be performed on the object to be photographed based on the preset pixel on the photosensitive element 100 in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0052]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may also include the MEMS 200. [0053]The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate the displacement at the initial position. [0054]In embodiments of the present disclosure, the initial position is the position of the photosensitive element in the mobile terminal when the phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal in act of block S11 in the embodiment shown in FIG. 1. [0055]In an embodiment, the photosensitive element 100 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0056]In embodiments of the present disclosure, the MEMS 200 may be used to carry the photosensitive element 100, and the photosensitive element 100 may be moved in a three-axis direction of the space rectangular coordinate system to provide an anti-shake function during the process of photographing with the mobile terminal. [0057]As an example, referring to FIG. 4, FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 41, a micro-electromechanical system (MEMS) 42, and a glue 43, in which the photosensitive element 41 and the MEMS 42 are coupled using a chip-on-board technology and a dispensing method. The photosensitive element 41 may be controlled to move by the MEMS 42. [0058]Referring to FIG. 5, FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) 200 according to an embodiment of the present disclosure. The MEMS 200 may be translated upwards and downwards, left and right, and may be rotated with an angle. For example, when the MEMS 200 needs to move upwards and downwards, module 1 and module 4 take actions to cause the MEMS 200 to move upwards and downwards; when the MEMS 200 needs to move to the left and right, module 2 or module 3 take actions to cause the MEMS 200 to move to the left or right; when the MEMS 200 needs to rotate clockwise, the module 1 moves upwards, the module 2 moves to the right, the module 4 moves downwards, and the module 3 moves to the left, such that MEMS 200 rotates clockwise; similarly, when the MEMS 200 needs to rotate counterclockwise, the module 1 moves downwards, the module 2 moves to the left, the module 4 moves upwards, and the module 3 moves to the right. [0059]According to actual needs, the movements in three-axis directions of the space rectangular coordinate system in the MEMS 200 (i.e., translating movements in two orthogonal directions in the horizontal plane, and a rotating movement around the axis perpendicular to the horizontal plane) may be realized by controlling the module 1, the module 2, the module 3, and/or the module 4, such that the MEMS 200 may pulls the photosensitive element 100 to generate the displacement at the initial position to compensate for the masked pixels during the process of photographing with the mobile terminal. [0060]In an embodiment, in some embodiments, referring to FIG. 6, the micro-electromechanical optical image stabilization system may also include: a printed circuit board (PCB) 300. [0061]In embodiments of the present disclosure, the micro-electromechanical optical image stabilization system may also include the printed circuit board (PCB) 300 coupled to the MEMS 200. [0062]In an embodiment, the PCB 300 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0063]In an embodiment, the PCB 300 is used to carry the weight of the MEMS 200 and the photosensitive element 100 and is used for routing. [0064]As an example, referring to FIG. 7, FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. The system may include: a micro-electromechanical system (MEMS) 71, a printed circuit board (PCB) 72, and a glue 73, win which the MEMS 71 is coupled to the PCB 72 using a chip-on-board technology and a dispensing method. [0065]As an example, referring to FIG. 8, FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 81, a micro-electromechanical system (MEMS) 82, a printed circuit board (PCB) 83, a glue 84, a silicon wire 85 and a gold wire 86, in which the silicon wire 85 is configured to carry the weight of the moving portion of the MEMS 82, the outer side of the silicon wire 85 is gold plated to generate electrical conductivity at the same time, and the silicon wire 85 is configured to transmit signals of the photosensitive element 81 and to supply power to the MEMS 82. The gold wire 86 is configured to transmit signals of the photosensitive element 81 and to supply power to the photosensitive element 81. [0066]As an example, referring to FIG. 9, FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 91, a micro-electromechanical system (MEMS) 92, a silicon wire 93 and a gold wire 94. [0067]In this embodiment, a printed circuit board (PCB) is coupled to the MEMS, such that the PCB may carry the weight of the MEMS and the photosensitive element, and may supply power to the micro-electromechanical optical image stabilization system to ensure a normal operation of the micro-electromechanical optical image stabilization system. [0068]In this embodiment, the photosensitive data of the object to be photographed may be collected by the photosensitive element, and the MEMS may control the photosensitive element to generate a displacement at the initial position. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0069]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. The image synthesis apparatus 100 of the mobile terminal may be implemented by software, hardware or a combination thereof. The image synthesis apparatus 100 of the mobile terminal may include: a processing module 101, a control module 102, a collecting module 103, a photographing module 104, and a synthesizing module 105. [0070]The processing module 101 is configured to perform a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0071]In an embodiment, the preset pixel is a masked pixel. [0072]The control module 102 is configured to control the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and to obtain a replaced pixel. [0073]In an embodiment, the control module 102 is also configured to: control, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial position. [0074]The collecting module 103 is configured to collect first photosensitive data of the object to be photographed based on the replaced pixel, and to control the photosensitive element to return to the initial location. [0075]The photographing module 104 is configured to photograph the object to be photographed, and to enable the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location. [0076]The synthesizing module 105 is configured to synthesize an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0077]In an embodiment, the synthesizing module 105 is also configured to: perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing. [0078]It should be noted that, the description of embodiments of the image synthesis method for the mobile terminal in the foregoing embodiments of FIGS. 1-2 is also applicable to the image synthesis apparatus for the mobile terminal. The implementation principles thereof are similar, which will not be described in detail herein. [0079]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0080]Embodiments of the disclosure also provide a mobile terminal. The mobile terminal may include a housing, a processor, a memory, a circuit board and a power supply circuit, in which the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute followings. [0081]At block S11′: a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0082]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0083]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0084]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0085]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0086]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, G, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0087]At block S12′, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0088]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0089]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11′. [0090]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0091]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0092]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0093]At block S13′, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0094]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0095]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be contro(String), 相关申请的交叉引用 [0001] 本申请是美国申请系列的延续申请。 2018 年 11 月 16 日提交的第 16/302,323 号,是 2017 年 6 月 9 日提交的国际申请 PCT/CN2017/087806 的国家阶段进入,要求中国专利申请第 201610616090.6 号的优先权, 2016年7月29日,广东​​OPPO移动通信股份有限公司提交,题为“移动终端的图像合成方法及装置,以及移动终端”。 上述申请的全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端的图像合成方法、装置及移动终端。 背景 [0003] 光学防抖(OIS)可以有效避免用户在使用移动终端拍照的过程中由于抖动而导致的图像模糊。 OIS采用磁性包裹的悬浮镜头,有效克服移动终端震动造成的图像模糊。 现有技术中,防抖是通过感光元件来实现的,其原理可以描述如下。 感光元件固定在可上下左右移动的支架上,通过陀螺仪传感器感知移动终端晃动的方向和幅度数据。 之后,陀螺仪传感器传输数据。 在处理器端对数据进行筛选和放大,计算出可以补偿抖动的感光元件的移动量。 在用户使用移动终端拍照的过程中,还需要对要拍照的场景进行相位对焦。 在相关技术中,通过在感光元件上隐藏一些被遮蔽的像素,并考虑被摄场景的像素之间的距离及其变化因素,可以确定聚焦偏移值来实现相位聚焦。 [0004] 这样,被掩蔽的像素只能用于检测相位而不能用于显示图像。 被遮盖的像素可能会影响所拍摄图像的质量。 被掩蔽的像素密度越高,相位聚焦越准确,但拍摄的图像质量越差。 概括 [0005] 本发明旨在在一定程度上解决现有技术中的至少一个技术问题。 [0006] 本发明实施例提供一种移动终端的图像合成方法。 该方法可以包括: 当用户通过移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素,采集被摄物体的第一感光数据,并控制感光元件返回初始位置; 对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成被摄物体的图像。 [0007] 本发明实施例还提供一种微机电光学防抖系统。 该系统可以包括: 感光元件,用于采集被摄物体的感光数据; 微机电系统(MEMS),用于控制光敏元件在初始位置产生位移。 [0008]本申请实施例提出一种存储介质,当存储介质中存储的指令由移动终端的处理器执行时,使移动终端执行该移动终端的图像合成方法。 该图像合成方法可以包括: 当用户通过移动终端拍摄待拍摄对象时,根据移动终端中的感光元件的预设像素对待拍摄对象进行相位对焦。 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素,采集被摄物体的第一感光数据,并控制感光元件返回初始位置; 对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成被摄物体的图像。 [0009] 本公开的实施例的另外的方面和优点将部分地在以下描述中给出,部分地从以下描述变得显而易见,或者从本公开的实施例的实践中获知。 附图的简要说明 [0010] 为使本发明实施例的技术方案更加清楚明白,以下对实施例说明中需要用到的附图进行说明。 显然,以下所绘示的附图仅代表本发明的部分实施例,本领域普通技术人员在不付出创造性劳动的情况下,可以根据这些附图获得其他附图。 [0011] 图1为本发明实施例提供的一种移动终端的图像合成方法流程示意图。 [0012] 图2为本发明实施例的感光元件上的预设像素示意图。 [0013] 图3为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 [0014] 图4为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 [0015] 图5是示出根据本公开实施例的微机电系统(MEMS)的结构的俯视图。 [0016] 图6为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0017] 图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0018] 图8为本发明实施例提供的另一种微机电光学防抖系统的结构示意图。 [0019] 图9为本发明实施例的微机电光学防抖系统的结构俯视图。 [0020] 图10为本发明实施例提供的一种移动终端的图像合成装置的结构示意图。 详细说明 [0021] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。 显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0022]本发明的说明书、权利要求书和上述附图中的“第一”、“第二”、“第三”、“第四”等术语用于区分不同的对象,并不旨在描述特定的顺序。 此外,术语“包含”和“具有”及其变体旨在涵盖非排他性的“包含”。 例如,包括一系列步骤或单元的过程、方法、系统、术语或设备可以不限于列出的步骤或单元,替代地,可以包括未列出的其他步骤或单元 或这些过程、方法、术语或设备固有的其他步骤或单元可以包括在实施例中。 [0023] 图1为本发明实施例提供的一种移动终端的图像合成方法流程示意图。 本实施例以移动终端的图像合成装置配置移动终端的图像合成方法为例。 本发明实施例可以应用于用户在移动终端对拍摄对象进行分段的过程中。 [0024] 参考图1,移动终端的图像合成方法可以包括以下内容。 [0025] 在 S 区 11 ,当用户通过移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 [0026] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0027] 在本发明实施例中,待拍摄对象可以是用户通过移动终端拍摄的场景、人物、事物等。 [0028] 在本发明实施例中,预设像素为掩蔽像素,预设像素成对设置。 [0029] 在一个实施例中,当用户使用移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 也就是说,通过在感光元件上保留一些被掩蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定聚焦偏移值,从而实现相位聚焦。 [0030] 请参阅图2,图2为本发明实施例提供的感光元件上预设像素的示意图。 例如,图2中标有字母的像素可以是预设像素,预设像素是成对设置的。 例如,可以将预设像素A、B、C、D、E、F、G、H、I、J标记为预设像素对A和B、预设像素对C和D、预设像素对E F、预设像素对G和H,以及预设像素对I和J。 [0031] 在 S 区 12 ,控制光敏元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0032] 在本发明的实施例中,可以通过微机电光学图像稳定系统控制光敏元件在初始位置产生位移。 [0033] 在本发明实施例中,所述初始位置为在移动终端中根据预先设置的感光元件的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块 S 11 . [0034] 在本发明实施例中,原始像素例如可以是在移动终端中的感光元件上没有预留掩蔽像素时的默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0035]在一个实施例中,可以通过微机电光学图像稳定系统控制光敏元件的移动,使得光敏元件在初始位置产生位移,以将被掩蔽的像素替换为原始像素以获得替换像素。 [0036] 作为示例,参见图2,图2中标有字母的像素为掩蔽像素,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到替换后的像素。 换言之,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,从而使得在彩色滤光片阵列前后对应相同滤光片位置的感光像素 移动不同,移动前的那些预设像素(保留的掩码像素)的位置被移动后的原始像素(默认像素)替换。 [0037] 在 S 区 13 ,首先根据替换的像素采集被摄物体的感光数据,并控制感光元件返回初始位置。 [0038] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据置换后的像素对被摄物体进行拍摄时采集的感光数据。 [0039] 在本发明实施例中,在采集到第一感光数据后,可以根据预设像素控制感光元件返回初始位置对被摄体进行拍摄。 [0040] 在 S 区 14 ,对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据。 [0041] 在本发明实施例中,当控制感光元件返回初始位置时,根据预设像素对被摄物体进行拍摄,从而使感光元件采集被摄物体的感光数据。 初始位置作为第二感光数据。 [0042] 在本发明实施例中,由于光敏元件在初始位置产生位移,因此使用原始像素替换光敏元件上的掩蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以基于第一拍照数据对第二拍照数据进行补偿,以补偿被掩蔽的像素。 [0043] 在 S 区 15 ,根据第一感光数据和第二感光数据合成被摄物体的图像。 [0044] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,以根据补偿后的第二感光数据合成被摄体的图像。 [0045] 在本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换的像素采集被摄体的第一感光数据,控制感光元件返回初始位置,可以对被摄体进行拍摄,使感光元件采集第二次感光 被摄物体在初始位置的数据。 根据第一感光数据和第二感光数据合成被摄物体的图像。 因此,可以有效提高相位聚焦的精度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0046]图3为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 [0047] 参考图3,微机电光学图像稳定系统可以包括感光元件 100 和微机电系统(MEMS) 200 . 感光元件 100 用于采集被摄物体的感光数据。 微机电系统 200 耦接至感光元件并用以控制感光元件 100 在初始位置产生位移。 [0048] 在本发明的实施例中,微机电光学影像稳定系统可包括感光元件 100 . [0049] 感光元件 100 用于采集被摄物体的感光数据。 [0050] 在一个实施例中,在光敏元件上设置掩蔽像素 100 ,其中被掩蔽的像素用于对被摄体进行相位对焦。 [0051] 在一个实施例中,当用户使用移动终端拍摄被摄体时,可以根据感光元件上的预设像素对被摄体进行相位对焦。 100 在移动端。 也就是说,通过在感光元件上保留一些被掩蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定聚焦偏移值,从而实现相位聚焦。 [0052] 在本公开的实施例中,微机电光学图像稳定系统还可以包括MEMS 200 . [0053] 微机电系统 200 耦接至感光元件并用以控制感光元件 100 在初始位置产生位移。 [0054] 在本发明实施例中,初始位置为移动终端中感光元件在遮挡作用下的预设像素,对被摄体进行相位对焦时移动终端中感光元件的位置。 小号 11 在图1所示的实施例中。 [0055] 在一个实施例中,光敏元件 100 和 MEMS 200 使用板上芯片技术和点胶方法进行耦合。 [0056] 在本公开的实施例中,MEMS 200 可用于承载感光元件 100 , 和感光元件 100 可以在空间直角坐标系的三轴方向上移动,以在使用移动终端拍照的过程中提供防抖功能。 [0057] 作为示例,请参阅图4,图4为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 该系统可以包括:感光元件 41 , 一种微机电系统 (MEMS) 42 , 和胶水 43 , 其中感光元件 41 和 MEMS 42 使用板上芯片技术和点胶方法进行耦合。 感光元件 41 可以由 MEMS 控制移动 42 . [0058] 请参阅图5,图5是微机电系统(MEMS)结构的俯视图 200 根据本公开的一个实施例。 微机电系统 200 可以向上和向下、向左和向右平移,并且可以旋转一个角度。 例如,当 MEMS 200 需要上下移动,模块 1 和模块 4 采取措施使 MEMS 200 上下移动; 当 MEMS 200 需要左右移动,模块 2 或模块 3 采取措施使 MEMS 200 向左或向右移动; 当 MEMS 200 需要顺时针旋转,模块 1 向上移动,模块 2向右移动,模块 4 向下移动,模块 3 向左移动,这样 MEMS 200 顺时针旋转; 同样,当 MEMS 200 需要逆时针旋转,模块 1 向下移动,模块 2 向左移动,模块 4 向上移动,模块 3 向右移动。 [0059] 根据实际需要,MEMS中空间直角坐标系三轴方向的运动 200 (即水平面两个正交方向的平移运动,以及绕垂直于水平面的轴的旋转运动)可以通过控制模块来实现 1 , 模块 2 , 模块 3 , 和/或模块 4 , 这样 MEMS 200 可拉光敏元件 100 在移动终端拍照过程中,在初始位置产生位移,以补偿被掩蔽的像素。 [0060] 在一个实施例中,在一些实施例中,参见图6,该微机电光学防抖系统还可以包括:印刷电路板(PCB) 300 . [0061] 在本公开的实施例中,微机电光学图像稳定系统还可以包括印刷电路板(PCB) 300 耦合到 MEMS 200 . [0062] 在一个实施例中,PCB 300 和 MEMS 200 使用板上芯片技术和点胶方法进行耦合。 [0063] 在一个实施例中,PCB 300 用于承载 MEMS 的重量 200 和感光元件 100 并用于路由。 [0064] 作为示例,请参阅图7,图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 该系统可以包括:微机电系统(MEMS) 71 ,印刷电路板(PCB) 72 , 和胶水 73 ,赢哪的MEMS 71 耦合到PCB 72 使用板上芯片技术和点胶方法。 [0065] 作为示例,请参阅图8,图8为本发明实施例提供的另一种微机电光学防抖系统的结构示意图。 该系统可以包括:感光元件 81 , 一种微机电系统 (MEMS) 82 ,印刷电路板(PCB) 83 , 胶水 84 , 一根硅线 85 和一根金线 86 , 其中硅线 85 被配置为承载 MEMS 的移动部分的重量 82 , 硅丝外侧 85 镀金同时产生导电性,而硅线 85 用于传输光敏元件的信号 81 并为 MEMS 供电 82 . 金线 86 用于传输光敏元件的信号 81 并为感光元件供电 81 . [0066] 作为示例,请参阅图9,图9为本发明实施例提供的一种微机电光学防抖系统的结构俯视图。 该系统可以包括:感光元件 91 , 一种微机电系统 (MEMS) 92 , 一根硅线 93 和一根金线 94 . [0067] 在本实施例中,印刷电路板(PCB)与MEMS耦合,使得PCB可以承载MEMS和感光元件的重量,并可以为微机电光学防抖系统供电,以保证正常工作。 微机电光学图像稳定系统的操作。 [0068]在本实施例中,可以通过光敏元件采集被摄体的光敏数据,MEMS可以控制光敏元件在初始位置产生位移。 因此,可以有效提高相位聚焦的精度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0069] 图10为本发明实施例提供的一种移动终端的图像合成装置的结构示意图。 图像合成装置 100 移动终端的实现可以通过软件、硬件或者两者的结合来实现。 图像合成装置 100 所述移动终端可以包括:处理模块 101 , 一个控制模块 102 , 采集模块 103 , 拍照模块 104 , 和一个合成模块 105 . [0070] 处理模块 101 用于当用户通过移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 [0071] 在一个实施例中,预设像素是掩蔽像素。 [0072] 控制模块 102 用于控制光敏元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0073] 在一个实施例中,控制模块 102 还用于通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0074] 采集模块 103 用于根据替换像素采集被摄物体的第一感光数据,并控制感光元件返回初始位置。 [0075] 拍照模块 104 用于对被摄体进行拍照,使感光元件在初始位置采集被摄体的第二感光数据。 [0076] 合成模块 105 用于根据第一感光数据和第二感光数据合成被摄物体的图像。 [0077] 在一个实施例中,合成模块 105 还用于: 将所述第二感光数据与所述第一感光数据进行补偿处理, 以根据所述补偿处理后的所述第二感光数据合成所述被摄体的图像。 [0078] 需要说明的是,上述图1-2实施例中对移动终端图像合成方法实施例的描述同样适用于移动终端图像合成装置。 其实现原理类似,在此不再赘述。 [0079] 在本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素采集被摄体的第一感光数据,控制感光元件返回初始位置,可以对被摄体进行拍摄,使感光元件采集第二次感光 被摄物体在初始位置的数据。 根据第一感光数据和第二感光数据合成被摄物体的图像。 因此,可以有效提高相位聚焦的准确度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0080]本发明实施例还提供了一种移动终端。 移动终端可以包括外壳、处理器、存储器、电路板和电源电路,其中电路板设置在外壳围成的空间内,处理器和存储器设置在电路板上, 供电电路用于为移动终端的电路或部件供电, 存储器用于存储可执行程序代码, 处理器用于通过读取存储在 执行以下操作的内存。 [0081] 在 S 区 11 ':用户在使用移动终端拍摄待摄物时,根据移动终端中感光元件的预设像素对待摄物进行相位对焦。 [0082] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0083] 在本发明实施例中,待拍摄对象可以是用户通过移动终端拍摄的场景、人物、事物等。 [0084] 在本发明实施例中,预设像素为掩蔽像素,预设像素成对设置。 [0085] 在一个实施例中,当用户使用移动终端拍摄待拍摄对象时,根据移动终端中感光元件的预设像素对待拍摄对象进行相位对焦。 也就是说,通过在感光元件上保留一些被掩蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定聚焦偏移值,从而实现相位聚焦。 [0086] 请参阅图2,图2为本发明实施例提供的感光元件上预设像素的示意图。 例如,图2中标有字母的像素可以是预设像素,预设像素是成对设置的。 例如,可以将预设像素A、B、C、D、E、F、G、H、I、J标记为预设像素对A和B、预设像素对C和D、预设像素对E F、预设像素对G和H,以及预设像素对I和J。 [0087] 在 S 区 12 ',控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0088] 在本发明的实施例中,可以通过微机电光学图像稳定系统控制光敏元件在初始位置产生位移。 [0089] 在本发明实施例中,所述初始位置为在移动终端中根据预先设置的感光元件的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块 S 11 '。 [0090] 在本发明实施例中,原始像素例如可以是在移动终端中的感光元件上没有预留掩蔽像素时的默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0091] 在一个实施例中,可以通过微机电光学图像稳定系统控制光敏元件的移动,使得光敏元件在初始位置产生位移,以将被掩蔽的像素替换为原始像素以获得替换像素。 [0092]作为示例,参见图2,图2中标有字母的像素为掩蔽像素,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到替换后的像素。 换言之,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,从而使得在彩色滤光片阵列前后对应相同滤光片位置的感光像素 移动不同,移动前的那些预设像素(保留的掩码像素)的位置被移动后的原始像素(默认像素)替换。 [0093] 在 S 区 13 ',根据置换后的像素采集被摄物体的第一感光数据,并控制感光元件返回初始位置。 [0094] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据置换后的像素对被摄物体进行拍摄时采集的感光数据。 [0095] 在本发明实施例中,在采集到第一感光数据后,可以根据预设像素控制感光元件返回初始位置对被摄体进行拍摄。 [0096] 在 S 区 14 ',对被摄体进行拍照,使感光元件在初始位置采集被摄体的第二感光数据。 [0097] 在本发明实施例中,当控制感光元件返回初始位置时,根据预设像素对被摄物体进行拍摄,从而使感光元件采集被摄物体的感光数据。 初始位置作为第二感光数据。 [0098] 在本发明实施例中,由于光敏元件在初始位置产生位移,因此使用原始像素替换光敏元件上的掩蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以基于第一拍照数据对第二拍照数据进行补偿,以补偿被掩蔽的像素。 [0099] 在 S 区 15 ',根据第一感光数据和第二感光数据合成被摄物体的图像。 [0100] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,以根据补偿后的第二感光数据合成被摄体的图像。 [0101] 在本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换的像素采集被摄体的第一感光数据,控制感光元件返回初始位置,可以对被摄体进行拍摄,使感光元件采集第二次感光 被摄物体在初始位置的数据。 根据第一感光数据和第二感光数据合成被摄物体的图像。 因此,可以有效提高相位聚焦的精度,补偿被掩蔽的像素,有效克服移动终端振动造成的图像模糊。 [0102]装置的上述实施例是示例性的。 被描述为独立组件的单元可能在物理上是分开的,也可能不是。 显示为单元的组件可以是也可以不是物理单元,换言之,可以集成在一个位置或分布到多个网络单元。 可以根据实际需要选择其中的部分或者全部模块来实现本实施例方案的目的。 本领域技术人员无需做出创造性劳动即可理解并实施本发明。 [0103] 本发明实施例方法中的步骤可以根据实际需要依次调整、合并、删除。 [0104] 本发明实施例装置中的模块或单元可以根据实际需要进行组合、划分和删除。 [0105] 本发明实施例的模块或模块可以由通用集成电路(例如中央处理器CPU)或专用集成电路(ASIC)来实现。 [0106] 通过以上实施例的描述,本领域技术人员可以清楚地了解到,各种实现方式可以通过软件加必要的通用硬件平台的方式来实现,当然也可以通过硬件来实现。 基于这样的理解,上述技术方案本质上可以体现为软件产品的形式,也可以体现为软件产品的形式,可以存储在ROM/RAM、磁盘、光驱等计算机可读存储介质中。 盘等,并且包括用于使计算机设备(其可以是个人计算机、服务器或网络设备等)执行在各个实施例或实施例的部分中描述的方法的指令。 [0107] 上述实施例不构成对技术方案范围的限制。 凡在上述实施例的精神和原则之内所作的任何修改、等同替换、改进等,均应包含在本技术方案的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.404 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.405 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10554877B2(String), US20190141257A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.554 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: US10554877B2(String), US20190141257A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.571 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10554877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), US10554877B2(String), US20190141257A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.624 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271677(Integer), US10554877B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.659 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271677(Integer), US20190141257A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.694 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.695 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10554877B2(String), US10554877B2(String), 1580745600(Integer), 271677(Integer), 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.730 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.731 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.731 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186006(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.843 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.843 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.843 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 1(Integer), 186006(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.888 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.888 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.908 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.908 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.921 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186006(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.927 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.927 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.927 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.946 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.946 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.946 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.954 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 2(Integer), 186006(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.966 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.966 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.985 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.985 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.985 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.985 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.989 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:08.990 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.005 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.005 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.005 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.007 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.007 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.007 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.025 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.025 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.025 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.044 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.044 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.044 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.063 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.063 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.063 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.083 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.083 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.098 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.102 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.102 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.102 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.102 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.122 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.122 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.122 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.141 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.142 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.213 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.213 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: QUERY_GROUP(String), ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.233 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 50 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186006(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10848678B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.447 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.448 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.467 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.654 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10848678B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/302323(String), 1496937600(Integer), US10848678B2(String), 1606147200(Integer), 1606147200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 23(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2011075677A | JP2012208876A | US10554877B2 | US20110013061A1 | US20130156345A1 | US20140354833A1 | US20150109513A1 | US20150212336A1 | US20150229843A1 | WO2014003492A1 | WO2014014222A1 | WO2014097792A1 | WO2016099128A1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.688 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.689 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.690 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186007(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.708 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.708 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id,a.product_id,a.structure_id,a.is_category, u.`name` as create_name, (select count(*) from os_thematic_file where zid = a.id and type = 1) as report_num from os_thematic a left join os_distribution u on u.id = a.creat_id order by a.`create_time` desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.708 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Parameters: 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.729 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.771 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.771 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.791 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.823 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.823 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.836 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d9106fa51dfe4579a5ad4fbffbdea6e6.png(String), 186007(Integer), d9106fa51dfe4579a5ad4fbffbdea6e6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.844 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.872 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.873 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.890 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.890 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Image synthesis method and apparatus for mobile terminal, and mobile terminal(String), 移动终端图像合成方法、装置及移动终端(String), US10848678B2(String), An image synthesis method for a mobile terminal and the mobile terminal are provided. The method includes: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first and second photosensitive data.(String), 提供了一种移动终端的图像合成方法及移动终端。 该方法包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据和第二感光数据合成待拍摄对象的图像。(String), US16/302323(String), 1496937600(Integer), US10848678B2(String), 1606147200(Integer), 1606147200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 23(Integer), CN102238329A | CN105007420A | CN105007422A | CN105008976A | CN105590939A | CN105763766A | CN105814484A | CN106101556A | CN1921571A | CN203535350U | JP2011075677A | JP2012208876A | US10554877B2 | US20110013061A1 | US20130156345A1 | US20140354833A1 | US20150109513A1 | US20150212336A1 | US20150229843A1 | WO2014003492A1 | WO2014014222A1 | WO2014097792A1 | WO2016099128A1(String), \20230420\d9106fa51dfe4579a5ad4fbffbdea6e6.png(String), 20(Integer), 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.913 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.913 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.926 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.933 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.934 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.934 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.954 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.961 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 1. An image synthesis method for a mobile terminal, comprising:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location, wherein the photosensitive element is controlled to generate the displacement at the initial location and to return to the initial location by at least two modules configured in the mobile terminal collaboratively, wherein the photosensitive element is controlled to be moved upwards and downwards by a first module and a fourth module, to be moved left and right by a second module and a third module, and to be rotated with an angle by the first module, the second module, the third module and the fourth module;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data.(String), 1.根据权利要求10所述的移动终端,其中处理器还被配置为:通过微机电光学稳像系统控制感光元件在初始位置产生位移。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 2. The image synthesis method according to claim 1, controlling the photosensitive element to generate the displacement at the initial location comprising:controlling, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location.(String), 12.根据权利要求10所述的移动终端,其中处理器还被配置为:将第二感光数据与第一感光数据进行补偿处理,根据补偿处理后的第二感光数据合成被摄体的图像。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 3. The image synthesis method according to claim 1, synthesizing the image of the object to be photographed according to the first photosensitive data and the second photosensitive data comprising:performing a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 13.根据权利要求10所述的移动终端,其中预设像素为屏蔽像素。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 4. The image synthesis method according to claim 1, wherein the preset pixel is a masked pixel.(String), 14.根据权利要求2所述的图像合成方法,其特征在于,所述微机电光学稳像系统控制所述感光元件在所述初始位置产生位移。包括:微机电光学稳像系统通过空间直角坐标系三轴方向的运动控制感光元件在初始位置产生位移,三轴方向的运动包括两个方向的平移运动水平面中的正交方向和绕垂直于水平面的轴的旋转运动。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.963 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 5. A micro-electromechanical optical image stabilization system, comprising:a photosensitive element, configured to collect photosensitive data of an object to be photographed; anda micro-electromechanical system coupled to the photosensitive element, configured to control the photosensitive element to generate a displacement at an initial position and to return to the initial location by at least two modules configured in the micro-electromechanical optical image stabilization system collaboratively, wherein the photosensitive element is controlled to be moved upwards and downwards by a first module and a fourth module, to be moved left and right by a second module and a third module, and to be rotated with an angle by the first module, the second module, the third module and the fourth module.(String), 15.根据权利要求14所述的图像合成方法,其中微机电光学防抖系统包括具有第一模块、第二模块、第三模块和第四模块的微机电系统,以及在进行旋转运动时,该方法包括以下至少之一:控制第一模块向上运动,第二模块向右运动,第三模块向左运动,第四模块向下运动,使微机电系统顺时针旋转;和控制第一模块向下运动,第二模块向左运动,第三模块向右运动,第四模块向上运动,使微机电系统逆时针旋转;和在执行平移动作时,该方法包括以下至少之一:控制第一模块和第四模块动作使微机电系统上下运动;和控制第二模块和第三模块采取动作使微机电系统左右移动。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 6. The micro-electromechanical optical image stabilization system according to claim 5, further comprising:a printed circuit board coupled to the micro-electromechanical system.(String), 16.根据权利要求1所述的图像合成方法,其中初始位置为根据移动终端中的感光元件的预设像素对被摄体进行相位对焦时移动终端中的感光元件的位置,原始像素为默认像素,其中a移动终端中的光敏元件上没有保留被遮蔽的像素。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 7. The micro-electromechanical optical image stabilization system according to claim 5, wherein the photosensitive element and the micro-electromechanical system are coupled using a chip-on-board technology and a dispensing method.(String), 17.根据权利要求5所述的微机电光学防抖系统,其中微机电系统被配置为通过执行以下动作来控制光敏元件在初始位置产生位移:通过空间直角坐标系三轴方向的运动控制感光元件在初始位置产生位移,三轴方向的运动包括水平面内两个正交方向的平移运动和围绕其旋转运动垂直于水平面的轴。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 8. The micro-electromechanical optical image stabilization system according to claim 6, wherein the printed circuit board and the micro-electromechanical system are coupled using a chip-on-board technology and a dispensing method.(String), 18.根据权利要求17所述的微机电光学防抖系统,其中微机电光学防抖系统包括具有第一模块、第二模块、第三模块和第四模块的微机电系统,以及当进行旋转运动时,微机电光学防抖系统被配置为进行以下至少之一:控制第一模块向上运动,第二模块向右运动,第三模块向左运动,第四模块向下运动,使微机电系统顺时针旋转;和控制第一模块向下运动,第二模块向左运动,第三模块向右运动,第四模块向上运动,使微机电系统逆时针旋转;和当执行平移运动时,微机电光学图像稳定系统被配置为执行以下至少之一:控制第一模块和第四模块动作使微机电系统上下运动;和控制第二模块和第三模块采取动作使微机电系统左右移动。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 9. The micro-electromechanical optical image stabilization system according to claim 7, wherein a masked pixel is set on the photosensitive element, and the masked pixel is configured to perform a phase focusing on the object to be photographed.(String), 19.根据权利要求5所述的微机电光学防抖系统,还包括:硅线,用于承载微机电系统运动部分的重量,传输光敏元件的信号,为微机电系统供电;和金线,用于传输光敏元件的信号并为光敏元件供电。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 10. A mobile terminal, comprising: a housing, a processor, a memory, a circuit board and a power supply circuit, wherein,the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute:performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal;controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel;collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location, wherein the photosensitive element is controlled to generate the displacement at the initial location and to return to the initial location by at least two modules configured in the mobile terminal collaboratively, wherein the photosensitive element is controlled to be moved upwards and downwards by a first module and a fourth module, to be moved left and right by a second module and a third module, and to be rotated with an angle by the first module, the second module, the third module and the fourth module;photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; andsynthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data.(String), 20.如权利要求6所述的微机电光学防抖系统,其特征在于,所述印刷电路板用于承载所述微机电系统和所述感光元件的重量,所述印刷电路板还用于走线。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 11. The mobile terminal according to claim 10, wherein the processor is further configured to:control the photosensitive element to generate the displacement at the initial location by a micro-electromechanical optical image stabilization system.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 12. The mobile terminal according to claim 10, wherein the processor is further configured to:perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 13. The mobile terminal according to claim 10, wherein the preset pixel is a masked pixel.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 14. The image synthesis method according to claim 2, controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location comprising:controlling, by the micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 1(Integer), 13(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 15. The image synthesis method according to claim 14, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having the first module, the second module, the third module and the fourth module, andwhen performing the rotating movement, the method comprises at least one of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the method comprises at least one of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 16. The image synthesis method according to claim 1, wherein the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal, and the original pixel is a default pixel where a masked pixel is not reserved on the photosensitive element in the mobile terminal.(String), 1(Integer), 15(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 17. The micro-electromechanical optical image stabilization system according to claim 5, wherein the micro-electromechanical system is configured to control the photosensitive element to generate the displacement at the initial position by performing an act of:controlling the photosensitive element to generate the displacement at the initial location via movements in three-axis directions of a space rectangular coordinate system, the movements in the three-axis directions comprising translating movements in two orthogonal directions in a horizontal plane and a rotating movement around an axis perpendicular to the horizontal plane.(String), 1(Integer), 16(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 18. The micro-electromechanical optical image stabilization system according to claim 17, wherein the micro-electromechanical optical image stabilization system comprises a micro-electromechanical system having the first module, the second module, the third module and the fourth module, andwhen performing the rotating movement, the micro-electromechanical optical image stabilization system is configured to perform at least one of:controlling the first module to move upwards, the second module to move to the right, the third module to move to the left, and the fourth module to move downwards, so as to cause the micro-electromechanical system to rotate clockwise; andcontrolling the first module to move downwards, the second module to move to the left, the third module to move to the right, and the fourth module to moves upwards, so as to cause the micro-electromechanical system to rotate counterclockwise; andwhen performing the translating movements, the micro-electromechanical optical image stabilization system is configured to perform at least one of:controlling the first module and the fourth module to take actions to cause the micro-electromechanical system to move upwards and downwards; andcontrolling the second module and the third module to take actions to cause the micro-electromechanical system to move to the left and right.(String), 1(Integer), 17(Integer), 16(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 19. The micro-electromechanical optical image stabilization system according to claim 5, further comprising:a silicon wire, configured to carry a weight of a moving portion of the micro-electromechanical system, and to transmit a signal of the photosensitive element and to supply power to the micro-electromechanical system; anda gold wire, configured to transmit the signal of the photosensitive element and to supply power to the photosensitive element.(String), 1(Integer), 18(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:09.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186007(Integer), 20. The micro-electromechanical optical image stabilization system according to claim 6, the printed circuit board being configured to carry weights of the micro-electromechanical system and the photosensitive element, the printed circuit board being further configured for routing.(String), 1(Integer), 19(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186007(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The present application is a U.S. national phase application of International Application No. PCT/CN2017/087806, filed on Jun. 9, 2017, which claims priority from Chinese Patent Application No. “201610616090.6” filed on Jul. 29, 2016 by GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD., entitled “Image Synthesis Method and Device for Mobile Terminal, and Mobile Terminal”. TECHNICAL FIELD [0002]The present disclosure relates to a field of mobile terminal technology, and in particular, to an image synthesis method and apparatus for a mobile terminal, and a mobile terminal. BACKGROUND [0003]Optical Image Stabilization (OIS) may effectively avoid image blur caused by jitter during a process of the user taking pictures with a mobile terminal. OIS uses a magnetically wrapped suspension lens to effectively overcome image blur caused by vibration of the mobile terminal. In the related art, the anti-shake is realized by a photosensitive element, of which the principles may be described as followings. The photosensitive element is fixed on a bracket that can move up, down, left, and right, and the direction and amplitude data of the shaking of the mobile terminal are sensed by a gyro sensor. After that, the gyro sensor transmits the data. Screening and amplification are performed on the data at the processor side to calculate the amount of movement of the photosensitive element that may compensate the jitter. During the process of the user taking pictures with the mobile terminal, it is also necessary to perform phase focusing on the scene to be photographed. In the related art, by hiding some masked pixels on the photosensitive element, and considering the distance between the pixels of the scene to be photographed and its changing factors, the focusing offset value may be determined to achieve the phase focusing. [0004]In this way, the masked pixels may only be used to detect the phase and cannot be used to display the image. The masked pixels may affect the quality of the image photographed. The higher the density of the masked pixels, the more accurate the phase focusing, but the worse the quality of the image photographed. SUMMARY [0005]The present disclosure aims to solve at least one of technical problems in the related art to some extent. [0006]Embodiments of the present disclosure provide an image synthesis method for the mobile terminal. The method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0007]Embodiments of the present disclosure also provide a micro-electromechanical optical image stabilization system. The system may include: a photosensitive element, configured to collect photosensitive data of an object to be photographed; and a micro-electromechanical system (MEMS), configured to control the photosensitive element to generate a displacement at an initial position. [0008]Embodiments of the present application propose a storage medium, when instructions stored in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is caused to perform an image synthesis method for the mobile terminal. The image synthesis method may include: performing a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal; controlling the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and obtaining a replaced pixel; collecting first photosensitive data of the object to be photographed based on the replaced pixel, and controlling the photosensitive element to return to the initial location; photographing the object to be photographed, and enabling the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location; and synthesizing an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0009]Additional aspects and advantages of embodiments of present disclosure will be given in part in the following descriptions, become apparent in part from the following descriptions, or be learned from the practice of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS [0010]In order to make technical solutions according to embodiments of the present disclosure more apparent, drawings needed to be used in descriptions of the embodiments will be illustrated in the following. Obviously, the drawings to be illustrated in the following only represent some embodiments of the present disclosure, and other drawings can be obtained according these drawings by those having ordinary skills in the related art without making creative labors. [0011]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. [0012]FIG. 2 is a schematic diagram of preset pixels on a photosensitive element in an embodiment of the present disclosure. [0013]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0014]FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0015]FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) according to an embodiment of the present disclosure. [0016]FIG. 6 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0017]FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. [0018]FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0019]FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0020]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION [0021]The technical solutions in embodiments of the present disclosure are hereinafter described clearly and completely with reference to accompanying drawings in embodiments of the present disclosure. Apparently, embodiments described are a part of embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments in the present disclosure without creative labor shall fall in the protection scope of the present disclosure. [0022]The terms “first”, “second”, “third” and “fourth” and the like in the specification and claims of the present disclosure and the above drawings are used to distinguish different objects, and are not intended to describe a specific order. Moreover, the terms “comprise” and “have” and their variants are aim at covering non-exclusive “include”. For example, a process, a method, a system, a term or a device including a series of steps or units may be not limited to the listed steps or units, instead and alternatively, other steps or units which are not listed may be included, or other steps or units inherent for these process, method, term or device may be included in an embodiment. [0023]FIG. 1 is a schematic flow chart of an image synthesis method for a mobile terminal according to an embodiment of the present disclosure. This embodiment takes an example where an image synthesis method for the mobile terminal is configured for an image synthesis apparatus for the mobile terminal. Embodiments of the present disclosure may be applied during a process of a user paragraphing a subject to be photographed using the mobile terminal. [0024]Referring to FIG. 1, the image synthesis method of the mobile terminal may include followings. [0025]At block S11, a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0026]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0027]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0028]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0029]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0030]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0031]At block S12, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0032]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0033]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11. [0034]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0035]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0036]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0037]At block S13, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0038]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0039]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be controlled to return to the initial position to photograph the object to be photographed based on the preset pixel. [0040]At block S14, the object to be photographed is photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. [0041]In embodiments of the present disclosure, when the photosensitive element is controlled to return to the initial position, the object to be photographed is photographed based on the preset pixel, such that the photosensitive element collects the photosensitive data of the object to be photographed at the initial position as the second photosensitive data. [0042]In embodiments of the present disclosure, since the photosensitive element generates the displacement at the initial position, the original pixel is used to replace the masked pixel on the photosensitive element, and the obtained replaced pixel is the original pixel. Therefore, the mobile terminal may perform a compensation on the second photographic data based on the first photographic data so as to compensate for the masked pixel. [0043]At block S15, an image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. [0044]In embodiments of the present disclosure, the second photosensitive data are subjected to compensation processing using the first photosensitive data to synthesize an image of the object to be photographed according to the compensated second photosensitive data. [0045]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0046]FIG. 3 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. [0047]Referring to FIG. 3, the micro-electromechanical optical image stabilization system may include a photosensitive element 100 and a micro-electromechanical system (MEMS) 200. The photosensitive element 100 is configured to collect photosensitive data of an object to be photographed. The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate a displacement at an initial position. [0048]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may include the photosensitive element 100. [0049]The photosensitive element 100 is configured to collect photosensitive data of the object to be photographed. [0050]In an embodiment, a masked pixel is set on the photosensitive element 100, in which the masked pixel is used to perform a phase focusing on the object to be photographed. [0051]In an embodiment, when the user uses the mobile terminal to photograph the object to be photographed, the phase focusing may be performed on the object to be photographed based on the preset pixel on the photosensitive element 100 in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0052]In embodiments of the disclosure, the micro-electromechanical optical image stabilization system may also include the MEMS 200. [0053]The MEMS 200 is coupled to the photosensitive element and configured to control the photosensitive element 100 to generate the displacement at the initial position. [0054]In embodiments of the present disclosure, the initial position is the position of the photosensitive element in the mobile terminal when the phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal in act of block S11 in the embodiment shown in FIG. 1. [0055]In an embodiment, the photosensitive element 100 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0056]In embodiments of the present disclosure, the MEMS 200 may be used to carry the photosensitive element 100, and the photosensitive element 100 may be moved in a three-axis direction of the space rectangular coordinate system to provide an anti-shake function during the process of photographing with the mobile terminal. [0057]As an example, referring to FIG. 4, FIG. 4 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 41, a micro-electromechanical system (MEMS) 42, and a glue 43, in which the photosensitive element 41 and the MEMS 42 are coupled using a chip-on-board technology and a dispensing method. The photosensitive element 42 may be controlled to move by the MEMS 42. [0058]Referring to FIG. 5, FIG. 5 is a top view showing a structure of a micro-electromechanical system (MEMS) 200 according to an embodiment of the present disclosure. The MEMS 200 may be translated upwards and downwards, left and right, and may be rotated with an angle. For example, when the MEMS 200 needs to move upwards and downwards, module 1 and module 4 take actions to cause the MEMS 200 to move upwards and downwards; when the MEMS 200 needs to move to the left and right, module 2 or module 3 take actions to cause the MEMS 200 to move to the left or right; when the MEMS 200 needs to rotate clockwise, the module 1 moves upwards, the module 2 moves to the right, the module 4 moves downwards, and the module 3 moves to the left, such that MEMS 200 rotates clockwise; similarly, when the MEMS 200 needs to rotate counterclockwise, the module 1 moves downwards, the module 2 moves to the left, the module 4 moves upwards, and the module 3 moves to the right. [0059]According to actual needs, the movements in three-axis directions of the space rectangular coordinate system in the MEMS 200 (i.e., translating movements in two orthogonal directions in the horizontal plane, and a rotating movement around the axis perpendicular to the horizontal plane) may be realized by controlling the module 1, the module 2, the module 3, and/or the module 4, such that the MEMS 200 may pulls the photosensitive element 100 to generate the displacement at the initial position to compensate for the masked pixels during the process of photographing with the mobile terminal. [0060]In an embodiment, in some embodiments, referring to FIG. 6, the micro-electromechanical optical image stabilization system may also include: a printed circuit board (PCB) 300. [0061]In embodiments of the present disclosure, the micro-electromechanical optical image stabilization system may also include the printed circuit board (PCB) 300 coupled to the MEMS 200. [0062]In an embodiment, the PCB 300 and the MEMS 200 are coupled using a chip-on-board technology and a dispensing method. [0063]In an embodiment, the PCB 300 is used to carry the weight of the MEMS 200 and the photosensitive element 100 and is used for routing. [0064]As an example, referring to FIG. 7, FIG. 7 is a schematic structural diagram of a micro-electromechanical optical image stabilization system according to another embodiment of the present disclosure. The system may include: a micro-electromechanical system (MEMS) 71, a printed circuit board (PCB) 72, and a glue 73, in which the MEMS 71 is coupled to the PCB 72 using a chip-on-board technology and a dispensing method. [0065]As an example, referring to FIG. 8, FIG. 8 is a structural diagram of another micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 81, a micro-electromechanical system (MEMS) 82, a printed circuit board (PCB) 83, a glue 84, a silicon wire 85 and a gold wire 86, in which the silicon wire 85 is configured to carry the weight of the moving portion of the MEMS 82, the outer side of the silicon wire 85 is gold plated to generate electrical conductivity at the same time, and the silicon wire 85 is configured to transmit signals of the photosensitive element 81 and to supply power to the MEMS 82. The gold wire 86 is configured to transmit signals of the photosensitive element 81 and to supply power to the photosensitive element 81. [0066]As an example, referring to FIG. 9, FIG. 9 is a top view showing a structure of a micro-electromechanical optical image stabilization system according to an embodiment of the present disclosure. The system may include: a photosensitive element 91, a micro-electromechanical system (MEMS) 92, a silicon wire 93 and a gold wire 94. [0067]In this embodiment, a printed circuit board (PCB) is coupled to the MEMS, such that the PCB may carry the weight of the MEMS and the photosensitive element, and may supply power to the micro-electromechanical optical image stabilization system to ensure a normal operation of the micro-electromechanical optical image stabilization system. [0068]In this embodiment, the photosensitive data of the object to be photographed may be collected by the photosensitive element, and the MEMS may control the photosensitive element to generate a displacement at the initial position. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0069]FIG. 10 is a schematic structural diagram of an image synthesis apparatus for a mobile terminal according to an embodiment of the present disclosure. The image synthesis apparatus 100 of the mobile terminal may be implemented by software, hardware or a combination thereof. The image synthesis apparatus 100 of the mobile terminal may include: a processing module 101, a control module 102, a collecting module 103, a photographing module 104, and a synthesizing module 105. [0070]The processing module 101 is configured to perform a phase focusing on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0071]In an embodiment, the preset pixel is a masked pixel. [0072]The control module 102 is configured to control the photosensitive element to generate a displacement at an initial location to replace the preset pixel by an original pixel, and to obtain a replaced pixel. [0073]In an embodiment, the control module 102 is also configured to: control, by a micro-electromechanical optical image stabilization system, the photosensitive element to generate the displacement at the initial position. [0074]The collecting module 103 is configured to collect first photosensitive data of the object to be photographed based on the replaced pixel, and to control the photosensitive element to return to the initial location. [0075]The photographing module 104 is configured to photograph the object to be photographed, and to enable the photosensitive element to collect second photosensitive data of the object to be photographed at the initial location. [0076]The synthesizing module 105 is configured to synthesize an image of the object to be photographed according to the first photosensitive data and the second photosensitive data. [0077]In an embodiment, the synthesizing module 105 is also configured to: perform a compensation processing on the second photosensitive data with the first photosensitive data to synthesize the image of the object to be photographed according to the second photosensitive data subjected to the compensation processing. [0078]It should be noted that, the description of embodiments of the image synthesis method for the mobile terminal in the foregoing embodiments of FIGS. 1-2 is also applicable to the image synthesis apparatus for the mobile terminal. The implementation principles thereof are similar, which will not be described in detail herein. [0079]In this embodiment, the photosensitive element is controlled to generate a displacement at an initial position to replace the preset pixel by an original pixel and a replaced pixel is obtained. First photosensitive data of the object to be photographed may be collected based on the replaced pixel and the photosensitive element is controlled to return to the initial location, and the object to be photographed may be photographed, and the photosensitive element is enabled to collect second photosensitive data of the object to be photographed at the initial location. An image of the object to be photographed is synthesized according to the first photosensitive data and the second photosensitive data. Therefore, the accuracy of phase focusing may be effectively improved, masked pixels may be compensated, and image blur caused by vibration of the mobile terminal may be effectively overcome. [0080]Embodiments of the disclosure also provide a mobile terminal. The mobile terminal may include a housing, a processor, a memory, a circuit board and a power supply circuit, in which the circuit board is disposed inside a space enclosed by the housing, the processor and the memory are disposed on the circuit board, the power supply circuit is configured to supplying power to circuits or components of the mobile terminal, the memory is configured to store executable program codes, the processor is configured to run a program corresponding to the executable program codes by reading the executable program codes stored in the memory to execute followings. [0081]At block S11′: a phase focusing is performed on an object to be photographed based on a preset pixel of a photosensitive element in the mobile terminal when a user photographs the object to be photographed with the mobile terminal. [0082]In embodiments of the present disclosure, the mobile terminal may be a hardware device having various operating systems, such as a smart phone, a tablet computer, a personal digital assistant, an e-book and the like, which is not be limited herein. [0083]In embodiments of the present disclosure, the object to be photographed may be a scene, a person, a thing and the like to be photographed by the user with the mobile terminal. [0084]In embodiments of the present disclosure, the preset pixels are masked pixels, and the preset pixels are set in pairs. [0085]In an embodiment, when the user photographs the object to be photographed with the mobile terminal, a phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal. In other words, by reserving some masked pixels on the photosensitive element, the focusing offset value may be determined according to the distance between the pixels of the scene to be photographed and its changing factors, thereby achieving the phase focusing. [0086]Referring to FIG. 2, FIG. 2 is a schematic diagram of preset pixels on a photosensitive element according to an embodiment of the present disclosure. For example, the pixels marked with letters in FIG. 2 may be preset pixels, and the preset pixels are set in pairs. For example, the preset pixels A, B, C, D, E, F, G, H, I, J may be marked as a preset pixel pair A and B, a preset pixel pair C and D, a preset pixel pair E and F, a preset pixel pair G and H, and a preset pixel pair I and J. [0087]At block S12′, the photosensitive element is controlled to generate a displacement at an initial location to replace the preset pixel by an original pixel, and a replaced pixel is obtained. [0088]In embodiments of the disclosure, the photosensitive element may be controlled to generate a displacement at the initial position by a micro-electromechanical optical image stabilization system. [0089]In embodiments of the present disclosure, the initial position is a position of the photosensitive element in the mobile terminal when the phase focusing is performed on the object to be photographed based on the preset pixel of the photosensitive element in the mobile terminal in the act of block S11′. [0090]In embodiments of the present disclosure, the original pixel may be, for example, a default pixel when a masked pixel is not reserved on the photosensitive element in the mobile terminal, and the original pixel is, for example, a default pixel adjacent to the preset pixel. [0091]In an embodiment, the movement of the photosensitive element may be controlled by the micro-electromechanical optical image stabilization system, such that the photosensitive element generates the displacement at the initial position to replace masked pixels by original pixels to obtain replaced pixels. [0092]As an example, referring to FIG. 2, the pixels marked with letters in FIG. 2 are masked pixels, and after the micro-electromechanical optical image stabilization system controls the photosensitive element to generate displacement at the initial position, the replaced pixels may be obtained. In other words, by moving the position of the photosensitive element located under the color filter array, the movement of the photosensitive element relative to the color filter array may be caused, such that the photosensitive pixels corresponding to the same filter position before and after the movement are different, and the positions of those preset pixels (reserved masked pixels) before the movement are replaced by the original pixels (default pixels) after the movement. [0093]At block S13′, first photosensitive data of the object to be photographed are collected based on the replaced pixel, and the photosensitive element is controlled to return to the initial location. [0094]In embodiments of the present disclosure, the first photosensitive data are photosensitive data collected when the mobile terminal photographs the object to be photographed based on the replaced pixels after the photosensitive element in the mobile terminal generates the displacement of at the initial position. [0095]In embodiments of the present disclosure, after the first photosensitive data is collected, the photosensitive element may be controlled to return to the initial position to photograph the object to be photographed based on the preset pixel. [0096]At block S14′, the object to be photographed is photographed, and the p(String), 相关申请的交叉引用 [0001] 本申请为国际申请号PCT/CN2017/087806于2017年6月9日提交的美国国家阶段申请,该申请要求广东OPPO于2016年7月29日提交的中国专利申请号“201610616090.6”的优先权 MOBILE TELECOMMUNICATIONS CORP., LTD., 题为“用于移动终端的图像合成方法和装置、以及移动终端”。 技术领域 [0002] 本发明涉及移动终端技术领域,尤其涉及一种移动终端图像合成方法、装置及移动终端。 背景 [0003] 光学图像稳定(OIS)可以有效避免用户在使用移动终端拍照的过程中由于抖动导致的图像模糊。 OIS采用磁悬浮悬浮镜头,有效克服移动终端震动带来的影像模糊。 在相关技术中,防抖是通过感光元件来实现的,其原理可以描述如下。 感光元件固定在可上下左右移动的支架上,通过陀螺仪传感器感知移动终端晃动的方向和幅度数据。 之后,陀螺仪传感器传输数据。 在处理器端对数据进行筛选放大,计算出可以补偿抖动的光敏元件的移动量。 用户在使用移动终端拍照的过程中,还需要对要拍摄的场景进行相位对焦。 相关技术中,可以通过在感光元件上隐藏一些被遮蔽的像素点,并考虑待拍摄场景的像素点之间的距离及其变化因素,确定对焦偏移值,从而实现相位对焦。 [0004] 这样,被遮蔽的像素点只能用于检测相位,不能用于显示图像。 被屏蔽的像素可能会影响所拍摄图像的质量。 被掩蔽像素的密度越高,相位聚焦越准确,但拍摄的图像质量越差。 概括 [0005] 本发明旨在在一定程度上解决相关技术中的至少一个技术问题。 [0006] 本发明实施例提供了一种移动终端的图像合成方法。 该方法可以包括:当用户使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据与第二感光数据合成待拍摄对象的图像。 [0007] 本发明实施例还提供一种微机电光学防抖系统。 该系统可以包括:感光元件,用于采集待拍摄物体的感光数据; 微机电系统(MEMS),用于控制感光元件在初始位置产生位移。 [0008]本发明实施例提出了一种存储介质,当移动终端的处理器执行该存储介质中存储的指令时,使移动终端执行用于移动终端的图像合成方法。 所述图像合成方法可以包括:用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦; 控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素; 根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置; 对所述被摄体进行拍摄,并使所述感光元件在所述初始位置采集所述被摄体的第二感光数据; 根据第一感光数据与第二感光数据合成待拍摄对象的图像。 [0009] 本公开的实施例的其他方面和优点将部分地在下面的描述中给出,部分地从下面的描述中变得明显,或者从本公开的实施例的实践中获知。 附图的简要说明 [0010] 为使本发明实施例的技术方案更加清楚明白,下面对实施例的描述中需要用到的附图进行举例说明。 显然,下面所要说明的附图仅代表本发明的部分实施例,相关领域的普通技术人员在不付出创造性劳动的情况下,可以根据这些附图得到其他附图。 [0011] 图1为本发明实施例提供的一种移动终端图像合成方法的流程示意图。 [0012] 图2为本发明实施例中感光元件上预设像素的示意图。 [0013] 图3为本发明实施例的微机电光学防抖系统的结构示意图。 [0014] 图4为本发明实施例的微机电光学防抖系统的结构示意图。 [0015] 图5是示出根据本公开实施例的微机电系统(MEMS)的结构的俯视图。 [0016] 图6为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0017] 图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 [0018] 图8为本发明实施例提供的另一种微机电光学防抖系统的结构图。 [0019] 图9为本发明实施例的微机电光学防抖系统的结构俯视图。 [0020] 图10为本发明实施例提供的一种移动终端图像合成装置的结构示意图。 详细说明 [0021] 下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整的描述。 显然,所描述的实施例都是本发明的部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0022]本发明的说明书和权利要求书以及上述附图中的“第一”、“第二”、“第三”和“第四”等术语用于区分不同的对象,并不用于描述特定的顺序。 此外,术语“包含”和“具有”及其变体旨在涵盖非排他性的“包括”。 例如,包括一系列步骤或单元的过程、方法、系统、术语或装置可不限于所列步骤或单元,相反和备选地,可包括未列出的其他步骤或单元 或这些过程、方法、术语或设备固有的其他步骤或单元可以包括在一个实施例中。 [0023] 图1为本发明实施例提供的一种移动终端图像合成方法的流程示意图。 本实施例以移动终端图像合成装置配置移动终端图像合成方法为例。 本发明实施例可以应用在用户使用移动终端对被摄体进行分段的过程中。 [0024] 参考图1,移动终端的图像合成方法可以包括以下内容。 [0025] 在S座 11 用户在使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 [0026] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0027] 在本发明实施例中,所述待拍摄对象可以是用户通过移动终端拍摄的景物、人物、事物等。 [0028] 在本发明实施例中,预设像素为屏蔽像素,预设像素成对设置。 [0029] 在一个实施例中,当用户使用移动终端对被摄体进行拍摄时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 也就是说,通过在感光元件上保留一些被遮蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定对焦偏移值,从而实现相位对焦。 [0030] 参见图2,图2为本发明实施例的感光元件上预设像素的示意图。 例如,图2中标有字母的像素点可以是预设像素点,预设像素点是成对设置的。 例如,预设像素A、B、C、D、E、F、H、I、J可以标记为预设像素对A和B、预设像素对C和D、预设像素对E和F ,预设像素对G和H,以及预设像素对I和J。 [0031] 在S座 12 ,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0032] 在本发明实施例中,可以通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0033] 在本发明实施例中,初始位置为移动终端中感光元件在动作时根据预设的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块S 11 . [0034] 在本发明实施例中,当移动终端中的感光元件上没有预留遮蔽像素时,原始像素例如可以是默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0035]在一个实施例中,可以通过微机电光学防抖系统控制感光元件的移动,使得感光元件在初始位置产生位移,用原始像素替换遮蔽像素,得到替换像素。 [0036] 举例来说,参见图2,图2中标有字母的像素点为被遮蔽的像素点,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到被替换的像素点。 换句话说,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,使得前后相同滤光片位置对应的感光像素。 运动不同,运动前那些预设像素(保留的屏蔽像素)的位置被运动后的原始像素(默认像素)替换。 [0037] 在S座 13 ,首先根据替换后的像素采集待摄物体的感光数据,控制感光元件返回初始位置。 [0038] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据替换后的像素对被摄体进行拍摄时采集的感光数据。 [0039] 在本发明实施例中,在采集到第一感光数据后,可以控制感光元件返回初始位置,以预设像素为基准对被摄体进行拍摄。 [0040] 在S座 14 ,对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据。 [0041] 在本发明实施例中,当控制感光元件返回初始位置时,以预设像素为基准对被摄体进行拍摄,使得感光元件在初始位置采集被摄体的感光数据。 初始位置作为第二感光数据。 [0042] 在本发明实施例中,由于感光元件在初始位置产生位移,因此使用原始像素替换感光元件上的遮蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以根据第一拍照数据对第二拍照数据进行补偿,以补偿被遮挡的像素点。 [0043] 在S座 15 之后,根据第一感光数据和第二感光数据合成被摄体的图像。 [0044] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,根据补偿后的第二感光数据合成被摄体的图像。 [0045] 本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素点采集被摄体的第一感光数据,控制感光元件回到初始位置,对被摄体进行拍摄,使感光元件采集第二感光数据。 待拍摄物体在初始位置的数据。 根据第一感光数据与第二感光数据合成待拍摄物的影像。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0046]图3为本发明实施例的微机电光学防抖系统的结构示意图。 [0047] 参见图3,微机电光学防抖系统可以包括光敏元件 100 和微机电系统(MEMS) 200 . 感光元件 100 用于采集被摄体的感光数据。 微机电系统 200 耦接感光元件,用以控制感光元件 100 在初始位置产生位移。 [0048] 在本发明的实施例中,微机电光学防抖系统可以包括光敏元件 100 . [0049] 感光元件 100 用于采集待拍摄物体的感光数据。 [0050] 在一个实施例中,所述感光元件上设置有遮蔽像素 100 ,其中被遮蔽的像素用于对被摄物体进行相位对焦。 [0051] 在一个实施例中,当用户使用移动终端对被摄体进行拍摄时,可以根据感光元件上的预设像素对被摄体进行相位对焦。 100 在移动端。 也就是说,通过在感光元件上保留一些被遮蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定对焦偏移值,从而实现相位对焦。 [0052] 在本发明实施例中,微机电光学防抖系统还可以包括MEMS 200 . [0053] 微机电系统 200 耦接感光元件,用以控制感光元件 100 在初始位置产生位移。 [0054] 在本发明实施例中,初始位置为根据移动终端中感光元件的预设像素对被摄体进行相位对焦时移动终端中感光元件的位置。 小号 11 在图1所示的实施例中。 [0055] 在一个实施例中,感光元件 100 和微机电系统 200 使用板上芯片技术和点胶方法耦合。 [0056] 在本公开的实施例中,MEMS 200 可用于承载感光元件 100 , 和感光元件 100 可以在空间直角坐标系的三轴方向上移动,以提供移动终端拍照过程中的防抖功能。 [0057] 作为示例,请参见图4,图4为本发明实施例提供的一种微机电光学防抖系统的结构示意图。 该系统可能包括:光敏元件 41 , 微机电系统 (MEMS) 42 , 和胶水 43 , 其中光敏元件 41 和微机电系统 42 使用板上芯片技术和点胶方法耦合。 感光元件 42 可由 MEMS 控制移动 42 . [0058] 参见图5,图5是微机电系统(MEMS)的结构俯视图 200 根据本公开的实施例。 微机电系统 200 可以上下左右平移,也可以旋转一个角度。 例如,当 MEMS 200 需要上下移动,模块 1 和模块 4 采取措施导致 MEMS 200 向上和向下移动; 当MEMS 200 需要左右移动,模块 2 或模块 3 采取措施导致 MEMS 200 向左或向右移动; 当MEMS 200 需要顺时针旋转,模块 1 向上移动,模块 2向右移动,模块 4 向下移动,模块 3 向左移动,这样 MEMS 200 顺时针旋转; 同样,当 MEMS 200 需要逆时针旋转,模块 1 向下移动,模块 2 向左移动,模块 4 向上移动,模块 3 向右移动。 [0059] 根据实际需要,MEMS中空间直角坐标系的三轴方向运动 200 (即在水平面内两个正交方向的平移运动,以及绕垂直于水平面的轴的旋转运动)可以通过控制模块来实现 1 , 模块 2 , 模块 3 ,和/或模块 4 , 这样 MEMS 200 可拉光敏元件 100 在初始位置产生位移,以补偿移动端拍照过程中被遮挡的像素点。 [0060] 在一个实施例中,在一些实施例中,参见图6,该微机电光学防抖系统还可以包括:印刷电路板(PCB) 300 . [0061] 在本发明实施例中,微机电光学防抖系统还可以包括印刷电路板(PCB) 300 耦合到 MEMS 200 . [0062] 在一个实施例中,PCB 300 和微机电系统 200 使用板上芯片技术和点胶方法耦合。 [0063] 在一个实施例中,PCB 300 用于承载MEMS的重量 200 和感光元件 100 并用于路由。 [0064] 作为示例,请参见图7,图7为本发明另一实施例的微机电光学防抖系统的结构示意图。 该系统可能包括:微机电系统(MEMS) 71 , 印刷电路板 (PCB) 72 , 和胶水 73 , 其中 MEMS 71 耦合到PCB 72 使用板上芯片技术和点胶方法。 [0065] 作为示例,请参见图8,图8为本发明实施例提供的另一种微机电光学防抖系统的结构图。 该系统可能包括:光敏元件 81 , 微机电系统 (MEMS) 82 , 印刷电路板 (PCB) 83 , 胶水 84 , 硅线 85 和一根金线 86 , 其中硅线 85 配置为承载 MEMS 移动部分的重量 82 , 硅线的外侧 85 镀金同时产生导电性,硅线 85 用于传输光敏元件的信号 81 并为 MEMS 供电 82 . 金线 86 用于传输光敏元件的信号 81 并给光敏元件供电 81 . [0066] 作为示例,请参阅图9,图9为本发明实施例的微机电光学防抖系统的结构俯视图。 该系统可能包括:光敏元件 91 , 微机电系统 (MEMS) 92 , 硅线 93 和一根金线 94 . [0067] 在本实施例中,印刷电路板(PCB)耦合到MEMS,使得PCB可以承载MEMS和感光元件的重量,并且可以为微机电光学防抖系统供电以保证正常的正常工作。 微机电光学图像稳定系统的操作。 [0068]本实施例中,可以通过感光元件采集被摄体的感光数据,MEMS可以控制感光元件在初始位置产生位移。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0069] 图10为本发明实施例提供的一种移动终端图像合成装置的结构示意图。 图像合成装置 100 移动终端的功能可以通过软件、硬件或其组合来实现。 图像合成装置 100 移动终端的组成部分可以包括:处理模块 101 , 一个控制模块 102 , 采集模块 103 , 拍照模块 104 , 和一个合成模块 105 . [0070] 处理模块 101 用于在用户使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 [0071] 在一个实施例中,预设像素为掩蔽像素。 [0072] 控制模块 102 用于控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0073] 在一个实施例中,控制模块 102 还用于: 通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0074] 采集模块 103 用于根据替换后的像素采集待摄对象的第一感光数据,并控制感光元件返回初始位置。 [0075] 拍照模块 104 用于对所述被摄体进行拍摄,使所述感光元件在所述初始位置采集所述被摄体的第二感光数据。 [0076] 合成模块 105 用于根据第一感光数据和第二感光数据合成被摄体的图像。 [0077] 在一个实施例中,合成模块 105 还用于: 将第二感光数据与第一感光数据进行补偿处理,根据补偿处理后的第二感光数据合成被摄体的图像。 [0078] 需要说明的是,上述图1-2实施例中对移动终端图像合成方法实施例的描述同样适用于移动终端图像合成装置。 其实现原理类似,在此不再赘述。 [0079] 本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素点采集被摄体的第一感光数据,控制感光元件回到初始位置,对被摄体进行拍摄,使感光元件采集第二感光数据。 待拍摄物体在初始位置的数据。 根据第一感光数据与第二感光数据合成待拍摄物的影像。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0080]本发明实施例还提供了一种移动终端。 该移动终端可以包括壳体、处理器、存储器、电路板和供电电路,其中,电路板设置在壳体围成的空间内,处理器和存储器设置在电路板上, 供电电路,用于为移动终端的电路或部件供电, 存储器,用于存储可执行程序代码, 处理器,用于通过读取存储在其中的可执行程序代码,运行与可执行程序代码对应的程序。 执行以下操作的内存。 [0081] 在S座 11 ':用户使用移动终端拍摄被摄体时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 [0082] 在本发明实施例中,移动终端可以是智能手机、平板电脑、个人数字助理、电子书等具有各种操作系统的硬件设备,在此不做限定。 [0083] 在本发明实施例中,所述待拍摄对象可以是用户通过移动终端拍摄的景物、人物、事物等。 [0084] 在本发明实施例中,预设像素为屏蔽像素,预设像素成对设置。 [0085] 在一个实施例中,当用户使用移动终端对被摄体进行拍摄时,基于移动终端中感光元件的预设像素对被摄体进行相位对焦。 也就是说,通过在感光元件上保留一些被遮蔽的像素点,可以根据被摄场景的像素点之间的距离及其变化因素来确定对焦偏移值,从而实现相位对焦。 [0086] 参见图2,图2为本发明实施例的感光元件上预设像素的示意图。 例如,图2中标有字母的像素点可以是预设像素点,预设像素点是成对设置的。 例如,预设像素A、B、C、D、E、F、G、H、I、J可以标记为预设像素对A和B、预设像素对C和D、预设像素对E F、预设像素对G和H以及预设像素对I和J。 [0087] 在S座 12 ',控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 [0088] 在本发明实施例中,可以通过微机电光学防抖系统控制感光元件在初始位置产生位移。 [0089] 在本发明实施例中,初始位置为移动终端中感光元件在动作时根据预设的像素点对被摄体进行相位对焦时移动终端中感光元件的位置。 块S 11 ’。 [0090] 在本发明实施例中,当移动终端中的感光元件上没有预留遮蔽像素时,原始像素例如可以是默认像素,原始像素例如是相邻的默认像素。 预设像素。 [0091] 在一个实施例中,可以通过微机电光学防抖系统控制感光元件的移动,使得感光元件在初始位置产生位移,用原始像素替换遮蔽像素,得到替换像素。 [0092]举例来说,参见图2,图2中标有字母的像素点为被遮蔽的像素点,微机电光学防抖系统控制感光元件在初始位置产生位移后,即可得到被替换的像素点。 换句话说,通过移动位于彩色滤光片阵列下方的感光元件的位置,可以引起感光元件相对于彩色滤光片阵列的移动,使得前后相同滤光片位置对应的感光像素。 运动不同,运动前那些预设像素(保留的屏蔽像素)的位置被运动后的原始像素(默认像素)替换。 [0093] 在S座 13 ',根据替换后的像素采集待摄物体的第一感光数据,控制感光元件返回初始位置。 [0094] 在本发明实施例中,第一感光数据为移动终端中的感光元件在初始位置产生位移后,移动终端根据替换后的像素对被摄体进行拍摄时采集的感光数据。 [0095] 在本发明实施例中,在采集到第一感光数据后,可以控制感光元件返回初始位置,以预设像素为基准对被摄体进行拍摄。 [0096] 在S座 14 ',对被摄体进行拍摄,使感光元件在初始位置采集被摄体的第二感光数据。 [0097] 在本发明实施例中,当控制感光元件返回初始位置时,以预设像素为基准对被摄体进行拍摄,使得感光元件在初始位置采集被摄体的感光数据。 初始位置作为第二感光数据。 [0098] 在本发明实施例中,由于感光元件在初始位置产生位移,因此使用原始像素替换感光元件上的遮蔽像素,得到的替换像素即为原始像素。 因此,移动终端可以根据第一拍照数据对第二拍照数据进行补偿,以补偿被遮挡的像素点。 [0099] 在S座 15 '、根据第一感光数据和第二感光数据合成被摄体的图像。 [0100] 在本发明实施例中,利用第一感光数据对第二感光数据进行补偿处理,根据补偿后的第二感光数据合成被摄体的图像。 [0101] 本实施例中,控制感光元件在初始位置产生位移,将预设像素替换为原始像素,得到替换像素。 可以根据替换后的像素点采集被摄体的第一感光数据,控制感光元件回到初始位置,对被摄体进行拍摄,使感光元件采集第二感光数据。 待拍摄物体在初始位置的数据。 根据第一感光数据与第二感光数据合成待拍摄物的影像。 从而可以有效提高相位对焦的精度,补偿被遮挡的像素,有效克服移动终端震动导致的图像模糊。 [0102]装置的上述实施例是示例性的。 被描述为独立组件的单元可能是物理上分离的,也可能不是。 以单元表示的部件可以是物理单元,也可以不是物理单元,即可以集成在一个位置上,也可以分布到多个网络单元中。 可以根据实际需要选择其中的部分或者全部模块来实现本实施例方案的目的。 本领域技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0103] 本发明实施例的方法中的步骤可以根据实际需要依次调整、合并、删减。 [0104] 本发明实施例的装置中的模块或单元可以根据实际需要进行合并、划分和删除。 [0105] 本发明实施例的模块或模块可以由通用集成电路(如中央处理器CPU)或专用集成电路(ASIC)来实现。 [0106] 通过以上实施例的描述,本领域的技术人员可以清楚地了解到,各种实施方式可以通过软件加必要的通用硬件平台的方式来实现,当然也可以通过硬件来实现。 基于这样的理解,上述技术方案可以本质上以软件产品的形式体现,也可以以软件产品的形式体现,该软件产品可以存储在ROM/RAM、磁盘、光盘等计算机可读取存储介质中。 盘等,并且包括用于使计算机设备(其可以是个人计算机、服务器或网络设备等)执行在各个实施例或实施例的部分中描述的方法的指令。 [0107] 上述实施例并不构成对技术方案范围的限制。 凡在上述实施例的精神和原则之内,所作的任何修改、等同替换、改进等,均属于本技术方案的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106101556A(String), CN106101556B(String), EP3474535A1(String), EP3474535A4(String), EP3474535B1(String), US10848678B2(String), US20190306429A1(String), WO2018019039A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106101556A(String), CN106101556B(String), EP3474535A1(String), EP3474535A4(String), EP3474535B1(String), US10848678B2(String), US20190306429A1(String), WO2018019039A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.598 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106101556A(String), CN106101556B(String), EP3474535A1(String), EP3474535A4(String), EP3474535B1(String), US10848678B2(String), US20190306429A1(String), WO2018019039A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.616 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), CN106101556A(String), 193434(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), CN106101556B(String), 193435(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.684 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.685 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), EP3474535A1(String), 193436(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), EP3474535A4(String), 193437(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.754 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), EP3474535B1(String), 193438(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.790 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), US10848678B2(String), 193439(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), US20190306429A1(String), 193440(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.859 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.860 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271412(Integer), WO2018019039A1(String), 193441(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.895 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN106101556B(String), CN106101556B(String), 1508428800(Integer), 271412(Integer), 185696(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 68403(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.964 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 68403(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:10.999 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141635(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25114(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186007(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25114(Integer), 1(Integer), 186007(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.151 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186007(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 2(Integer), 186007(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25114(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.287 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.377 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186007(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.544 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.544 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.566 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.739 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.740 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.759 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.760 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.760 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.784 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 100 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.880 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.881 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.900 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.907 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.908 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 225(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.908 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method and mobile terminal for controlling application in the mobile terminal(String), 一种在移动终端中控制应用程序的方法及移动终端(String), US8914010B2(String), A method of controlling applications in a mobile terminal is provided. The method includes collecting acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved; identifying a motion trace indicating that the mobile terminal has been moved from the collected acceleration values; matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds.(String), 提供了一种控制移动终端中的应用程序的方法。 该方法包括当移动终端正在移动时,使用加速度传感器连续采集加速度值; 从采集的加速度值中识别移动终端移动的运动轨迹; 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。(String), US13/398248(String), 1329321600(Integer), US8914010B2(String), 1418659200(Integer), 1418659200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 3(Integer), US20090303204A1 | US20110304534A1 | WO2005103863A2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.927 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.942 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.943 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186008(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.946 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.insert ==> Preparing: INSERT INTO os_patent_keywords_highlight ( name, project_id, user_id, enable, `default`, config ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.946 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.insert ==> Parameters: 默认模板(String), 225(Integer), 103(Integer), false(Boolean), true(Boolean), [{"color":"#5470c6","keywords":""},{"color":"#91cc75","keywords":""},{"color":"#fac858","keywords":""},{"color":"#ee6666","keywords":""},{"color":"#73c0de","keywords":""}](String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:11.986 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.089 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\88f573cdcd754743bd2db8f140f60a02.png(String), 186008(Integer), 88f573cdcd754743bd2db8f140f60a02.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.142 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method and mobile terminal for controlling application in the mobile terminal(String), 一种在移动终端中控制应用程序的方法及移动终端(String), US8914010B2(String), A method of controlling applications in a mobile terminal is provided. The method includes collecting acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved; identifying a motion trace indicating that the mobile terminal has been moved from the collected acceleration values; matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds.(String), 提供了一种控制移动终端中的应用程序的方法。 该方法包括当移动终端正在移动时,使用加速度传感器连续采集加速度值; 从采集的加速度值中识别移动终端移动的运动轨迹; 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。(String), US13/398248(String), 1329321600(Integer), US8914010B2(String), 1418659200(Integer), 1418659200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 3(Integer), US20090303204A1 | US20110304534A1 | WO2005103863A2(String), \20230420\88f573cdcd754743bd2db8f140f60a02.png(String), 14(Integer), 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.212 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.213 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 1. A method of controlling applications in a mobile terminal, the method comprising:presetting a motion trace for the mobile terminal:binding the preset motion trace to a control command of an application, prior to collecting acceleration values:collecting the acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved;identifying a motion trace of the mobile device, indicating that the mobile terminal has been move, from the collected acceleration values;matching the identified motion trace with the preset motion trace; andexecuting a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds.(String), 1.一种在移动终端中控制应用程序的方法,该方法包括:为移动端预设运动轨迹:在采集加速度值之前,将预设运动轨迹绑定到应用程序的控制命令:移动终端移动时,通过加速度传感器持续采集加速度值;从采集到的加速度值中识别出移动设备的运动轨迹,表明移动终端已经移动;将识别出的运动轨迹与预设运动轨迹进行匹配;和如果匹配成功,则执行映射到预设运动轨迹的控制命令以控制移动终端中的应用程序。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 2. The method of claim 1, wherein each of the acceleration values is a vector including a value on an X-axis, a value on an Y-axis, and a value on an Z-axis, and wherein collecting the acceleration values comprises:performing sampling at a preset time interval, by the acceleration sensor, when the mobile terminal is moved, and storing in a first storage space including M groups of subspaces, values on the X-axis obtained in the sampling, storing in a second storage space including M groups of subspaces, values on the Y-axis obtained in the sampling, and storing in a third storage space including M groups of subspaces, values on the Z-axis obtained in the sampling,wherein M is a positive integer greater than or equal to 1.(String), 2.如权利要求1所述的方法,其中每个加速度值是一个向量,包括X轴上的值、Y轴上的值和Z轴上的值,其中采集加速度值包括:当移动终端移动时,加速度传感器按照预设的时间间隔进行采样,将采样得到的X轴上的值存储在包括M组子空间的第一存储空间中,存储在第二存储空间中包括M组子空间、采样得到的Y轴上的值,以及存储在包括M组子空间、采样得到的Z轴上的值的第三存储空间中,其中M为大于或等于1的正整数。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 3. The method of claim 2, wherein identifying of the motion trace comprises:determining M respective X-axis motion identifiers based on values in the M groups of subspaces for the values in the first storage space, wherein each of the X-axis motion identifiers is 1, −1 or 0, and wherein 1 denotes motion in an X-axis positive direction, −1 denotes motion in an X-axis negative direction, and 0 denotes no motion on the X-axis;determining M respective Y-axis motion identifiers based on values in the M groups of subspaces for the values in the second storage space, wherein each of the Y-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in a Y-axis positive direction, −1 denotes motion in a Y-axis negative direction, and 0 denotes no motion on the Y-axis;determining M respective Z-axis motion identifiers based on values in the M groups of subspaces for the values in the third storage space, wherein each of the Z-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in a Z-axis positive direction, −1 denotes motion in a Z-axis negative direction, and 0 denotes no motion on the Z-axis;wherein the M X-axis motion identifiers, the M Y-axis motion identifiers and the M Z-axis motion identifiers are used to represent a motion trace of motion of the mobile terminal.(String), 3.如权利要求2所述的方法,其中运动轨迹的识别包括:根据M组子空间中的值为第一存储空间中的值分别确定M个X轴运动标识,其中每个X轴运动标识为1、-1或0,1表示运动在X轴正方向,-1表示X轴负方向运动,0表示X轴不运动;根据M组子空间中的值为第二存储空间中的值分别确定M个Y轴运动标识,其中,每个Y轴运动标识为1、-1或0,其中1表示Y轴运动-轴正方向,-1表示Y轴负方向运动,0表示Y轴不运动;针对第三存储空间中的值,根据M组子空间中的值分别确定M个Z轴运动标识,其中每个Z轴运动标识为1、-1或0,1表示Z轴运动-轴正方向,-1表示Z轴负方向运动,0表示Z轴不运动;其中,M个X轴运动标识、M个Y轴运动标识和M个Z轴运动标识用于表示移动终端运动的运动轨迹。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 4. The method of claim 3, whereinthe M groups of subspaces of the first storage space include N data units for respectively storing N values on the X-axis that have been obtained in sampling most recently,the M groups of subspaces of the second storage space include N data units for respectively storing N values on the Y-axis that have been obtained in sampling most recently,the M groups of subspaces of the third storage space include N data units for respectively storing N values on the Z-axis that have been obtained in sampling most recently, andwherein N is an integer greater than or equal to 1.(String), 4.如权利要求3所述的方法,其中第一存储空间的M组子空间包括N个数据单元,分别存储最近采样得到的X轴上的N个值,第二存储空间的M组子空间包括N个数据单元,分别存储最近采样得到的Y轴上的N个值,第三存储空间的M组子空间包括N个数据单元,分别存储最近一次采样得到的N个Z轴值,其中N为大于或等于1的整数。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 5. The method of claim 4, wherein determining the M respective X-axis motion identifiers based on values in the M groups of subspaces, determining of the M respective Y-axis motion identifiers based on values in the M groups of subspaces, and determining of the M respective Z-axis motion identifiers based on values in the M groups of subspaces comprises:selecting a first group of subspaces as the current group;subtracting a still value from the N values stored in the current group and comparing the differences between the N values and the still value with a preset threshold value to obtain N comparison results, wherein the N comparison results are obtained as follows: if a difference is larger than the preset threshold value, the corresponding comparison result is 1; if a difference is smaller than the minus preset threshold value, the corresponding comparison result is −1; and if the absolute value of a difference is smaller than the preset threshold value, the corresponding comparison result is 0;counting the N comparison results of the current group and taking one of 1, −1 and 0 whose number of the N comparison results is the maximum as a motion identifier of a corresponding axis among the X-axis motion identifier, the Y-axis motion identifier, and the Z-axis motion identifier corresponding to the current group of subspace; andselecting the next group as the current group and returns to the second step unless all of the M groups of subspaces are processed.(String), 5.如权利要求4所述的方法,其中根据M组子空间中的值分别确定M个X轴运动标识,根据M组子空间中的值分别确定M个Y轴运动标识,以及确定M个相应的Z轴运动标识基于M组子空间中的值包括:选择第一组子空间作为当前组;将当前组中存储的N个值减去一个静止值,将N个值与静止值的差值与预设阈值进行比较,得到N个比较结果,其中,得到N个比较结果:如果差值是大于预设阈值,对应的比较结果为1;若差值小于负预设阈值,则对应的比较结果为-1;如果差的绝对值小于预设阈值,则对应的比较结果为0。统计当前组的N个比较结果,取X轴运动标识、Y轴运动中N个比较结果的个数最大的1、-1、0作为对应轴的运动标识标识符,以及当前子空间组对应的Z轴运动标识符;和选择下一组作为当前组并返回第二步,除非处理完所有M组子空间。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 6. The method of claim 5, further comprising:determining whether the motion identifier of the corresponding axis corresponding to the current group is 0; andcalculating a mean of the N values of the current group and updating the still value as the calculated mean.(String), 6.如权利要求5所述的方法,还包括:判断当前组对应的对应轴的运动标识是否为0;和计算当前组的N个值的平均值,并将静止值更新为计算平均值。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.214 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 7. The method of claim 1, wherein presetting a motion trace for the mobile terminal comprises:collecting acceleration values using the acceleration sensor continuously when the mobile terminal is being moved;identifying a motion trace indicating that the mobile terminal has been moved, from the collected acceleration values; displaying the identified motion trace to a user; andsaving the identified motion trace, when a confirmation instruction is received from the user; otherwise, returning to the first step.(String), 7.如权利要求1所述的方法,其中为移动终端预设运动轨迹包括:移动终端移动时,通过加速度传感器持续采集加速度值;从采集到的加速度值中识别移动终端移动过的运动轨迹;将识别出的运动轨迹展示给用户;和当接收到用户的确认指令时,保存识别出的运动轨迹;否则,返回第一步。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 8. A mobile terminal, comprising:an acceleration sensor for detecting an acceleration when the mobile terminal is being moved; anda controller for presetting a motion trace of the mobile terminal, binding the preset motion trace to a control command of an application, prior to collecting acceleration values, collecting the acceleration values continuously using the acceleration sensor, when the mobile terminal is being moved, identifying a motion trace of the mobile terminal, indicating that the mobile terminal has been moved, from the collected acceleration values, matching the identified motion trace with the preset motion trace, and executing a control command mapped to the preset motion trace to control applications in the mobile terminal, if the matching succeeds.(String), 8.移动终端,包括:加速度传感器,用于检测移动终端移动时的加速度;和控制器,用于预设移动终端的运动轨迹,将预设运动轨迹与应用程序的控制命令绑定,在采集加速度值之前,利用加速度传感器持续采集加速度值,在移动终端移动时,识别移动终端的运动轨迹,表示移动终端已经移动,根据采集到的加速度值,将识别出的运动轨迹与预设运动轨迹匹配,执行映射到预设运动轨迹的控制命令,控制应用程序中的应用程序移动端,如果匹配成功。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 9. The mobile terminal of claim 8, further comprising:a memory for providing first, second, and third storage spaces including respective M groups of subspaces,wherein the acceleration value is a vector including a value on the X-axis, a value on the Y-axis, and a value on the Z-axis and, when collecting the acceleration values, the controller performs sampling at a time interval preset by the acceleration sensor when the mobile terminal is being moved and stores values on the X-axis obtained during the sampling in the M groups of subspaces of the first storage space, stores values on the Y-axis obtained in the sampling in the M groups of subspaces of the second storage space, and stores values on the Z-axis obtained in the sampling in the M groups of subspaces of the third storage space,wherein M is a positive greater than or equal to 1.(String), 9.如权利要求8所述的移动终端,还包括:存储器,用于提供分别包括M组子空间的第一、第二和第三存储空间,其中,加速度值是一个向量,包括X轴的值、Y轴的值和Z轴的值,控制器在采集加速度值时,按照控制器预设的时间间隔进行采样。移动终端移动时的加速度传感器,将采样得到的X轴值存储在第一存储空间的M组子空间中,将采样得到的Y轴值存储在第一存储空间的M组子空间中。第二存储空间的子空间,将采样得到的Z轴上的值存储在第三存储空间的M组子空间中,其中M是大于或等于1的正数。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 10. The mobile terminal of claim 9, wherein, the controller determines M respective X-axis motion identifiers based on values in the M groups of subspaces for the values in the first storage space, when the motion trace is identified,wherein each of the X-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in an X-axis positive direction, −1 denotes motion in an X-axis negative direction, and 0 denotes no motion on the X-axis, determines M respective Y-axis motion identifiers based on values in the M groups of subspaces for the values in the second storage space,wherein each of the Y-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in Y-axis positive direction, −1 denotes motion in a Y-axis negative direction, and 0 denotes no motion on the Y-axis and determines M respective Z-axis motion identifiers based on values in the M groups of subspaces for the values in the third storage space,wherein each of the Z-axis motion identifiers is 1, −1 or 0, wherein 1 denotes motion in a Z-axis positive direction, −1 denotes motion in a Z-axis negative direction, and 0 denotes no motion on the Z-axis, and the M X-axis motion identifiers, the M Y-axis motion identifiers and the M Z-axis motion identifiers are used to represent a motion trace of motion of the mobile terminal.(String), 10.如权利要求9所述的移动终端,其中,控制器在识别运动轨迹时,根据M组子空间中的值为第一存储空间中的值确定M个各自的X轴运动标识,其中,每个X轴运动标识为1、-1或0,其中1表示X轴正方向运动,-1表示X轴负方向运动,0表示X轴不运动axis,根据M组子空间中的值为第二存储空间中的值确定M个各自的Y轴运动标识,其中,每个Y轴运动标识为1、-1或0,其中1表示Y轴正方向运动,-1表示Y轴负方向运动,0表示Y轴不运动根据M组子空间中的值为第三存储空间中的值确定M个各自的Z轴运动标识,其中,每个Z轴运动标识为1、-1或0,其中1表示Z轴正方向运动,-1表示Z轴负方向运动,0表示Z轴不运动M个X轴运动标识、M个Y轴运动标识和M个Z轴运动标识用于表示移动终端运动的运动轨迹。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 11. The mobile terminal of claim 10, wherein the M groups of subspaces of the first storage space include N data units for respectively storing N values on the X-axis that have been obtained in sampling most recently, the M groups of subspaces of the second storage space include N data units for respectively storing N values on the Y-axis that have been obtained in sampling most recently and the M groups of subspaces of the third storage space include N data units for respectively storing N values on the Z-axis that have been obtained in sampling most recently,wherein N is an integer greater than or equal to 1.(String), 11.如权利要求10所述的移动终端,其中第一存储空间的M组子空间包括N个数据单元,分别存储最近一次采样得到的X轴上的N个值,第二存储空间的M组子空间包括N个数据单元,分别存储N个最近采样得到的Y轴上的值,第三存储空间的M组子空间包括N个数据单元,分别存储N个最近采样得到的Z轴上的值,其中N为大于或等于1的整数。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 12. The mobile terminal of claim 11, wherein, when determining the M respective X-axis motion identifiers based on values in the M groups of subspaces, determining of the M respective Y-axis motion identifiers based on values in the M groups of subspaces, and determining of the M respective Z-axis motion identifiers based on values in the M groups of subspaces, respectively, the controller subtracts a still value from the N values stored in the respective M groups and compares the differences between the N values and the still value with a preset threshold value to obtain N comparison results, and counts the N comparison results of the current group and takes one of 1, −1 and 0 whose number of the N comparison results is the maximum as a motion identifier of a corresponding axis among the X-axis motion identifier, the Y-axis motion identifier, and the Z-axis motion identifier corresponding to the current group of subspace,wherein the N comparison results are obtained as follows: if a difference is larger than the preset threshold value, the corresponding comparison result is 1; if a difference is smaller than the minus preset threshold value, the corresponding comparison result is −1; if the absolute value of a difference is smaller than the preset threshold value, the corresponding comparison result is 0.(String), 12.如权利要求11所述的移动终端,其中,当根据M组子空间中的值确定M个各自的X轴运动标识时,根据M组子空间中的值确定M个各自的Y轴运动标识,以及确定M个各自的Z轴运动控制器分别根据M组子空间中的值分别从存储的N个值中减去一个静止值,将N个值与静止值的差值与预设阈值进行比较,得到N个比较结果,统计当前组的N个比较结果,取N个比较结果中数量最多的1、-1、0作为X轴运动标识中对应轴的运动标识,Y-轴运动标识,以及当前子空间组对应的Z轴运动标识,其中,N个比较结果的获取方式为:若差值大于预设阈值,则对应的比较结果为1;若差值小于负预设阈值,则对应的比较结果为-1;如果差的绝对值小于预设的阈值,则对应的比较结果为0。(String), 1(Integer), 11(Integer), 10(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 13. The mobile terminal of claim 12, wherein the controller calculates a mean of the N values of the current group and updates the still value as the calculated mean, if the motion identifier on the corresponding axis is 0.(String), 13.如权利要求12所述的移动终端,其中控制器计算当前组的N个值的平均值,如果相应轴上的运动标识符为0,则将静止值更新为计算出的平均值。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.215 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186008(Integer), 14. The mobile terminal of claim 8, wherein, when presetting a motion trace for the mobile terminal, the controller continuously collects the acceleration values using the acceleration sensor when the mobile terminal is being moved, identifies a motion trace that the motile terminal has been moved, from the collected acceleration values, displays the identified motion trace to a user, and stores the identified motion trace, when a confirmation instruction is received from the user.(String), 14.如权利要求8所述的移动终端,其中,当为移动终端预设运动轨迹时,控制器通过加速度传感器不断采集移动终端移动时的加速度值,识别移动终端移动过的运动轨迹,根据采集到的加速度值,显示识别的当接收到用户的确认指令时,将运动轨迹发送给用户,并存储识别出的运动轨迹。(String), 1(Integer), 13(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.488 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.489 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186008(Integer), PRIORITY [0001]This application claims priority under 35 U.S.C. §119(a) to a Chinese Patent Application filed in the State Intellectual Property Office of the People's Republic of China on Feb. 16, 2011 and assigned Ser. No. 201110041328.4, the entire disclosure of which is incorporated herein by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates generally to mobile terminals and, more particularly, to a method and an apparatus for controlling applications in a mobile terminal. [0004]2. Background of the Invention [0005]Various mobile terminals such as a mobile terminal, a tablet computer, and a smart phone increasingly include more functions and, specifically, not only basic communications services, such as calling, but also various applications can be implemented. When an application is to be started or exited, a user performs the operation of start or exit by selecting the menus provided by the mobile terminal level by level. However, such operation is inconvenient. [0006]Some high-end mobile terminals also allow users to control special functions in applications in the mobile terminals. For example, a user may zoom into a picture or control a game by shaking the terminal. However, all of these controls are simple. More and more demands on control of applications have been made. Thus, it is difficult for simple shaking of the terminal to meet more complex user demands. SUMMARY OF THE INVENTION [0007]Accordingly, the present invention provides a method capable of easily controlling various applications of mobile terminals and the mobiles terminals. [0008]The present invention also provides a method for controlling applications of mobile terminal by user writing with the mobile terminal and the mobile terminal. [0009]In accordance with an aspect of the present invention, a method of controlling applications in a mobile terminal is provided. The method includes collecting acceleration values continuously using an acceleration sensor, when the mobile terminal is being moved; identifying a motion trace indicating that the mobile terminal has been moved from the collected acceleration values; matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace to control an application in the mobile terminal, if the matching succeeds. [0010]In accordance with another aspect of the present invention, a mobile terminal is provided. The terminal includes an acceleration sensor for detecting an acceleration when the mobile terminal is being moved; and a controller for collecting acceleration values using the acceleration sensor continuously when the mobile terminal is being moved, identifying a motion trace that the mobile terminal has been moved from the collected acceleration values, matching the identified motion trace with a preset motion trace, and executing a control command mapped to the preset motion trace if the matching succeeds, to control applications in the mobile terminal. [0011]Thus, according to the present invention, a user can write any types of characters and pictures, not only simple shakes with a handheld mobile terminal. Therefore, motion traces can be formed and control commands can thereby be mapped by the motion traces. Consequently, it is possible to easily control various applications in the mobile terminal by a user writing with a handheld mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS [0012]The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0013]FIG. 1 illustrates a mobile terminal according to embodiments of the present invention; [0014]FIG. 2 illustrates a flowchart according to a first embodiment of the present invention; [0015]FIG. 3 illustrates a flowchart according to a second embodiment of the present invention; [0016]FIG. 4A illustrates queue 1 for storing sampled data on X-axis according to embodiments of the present invention; [0017]FIG. 4B illustrates queue 2 for storing sampled data on Y-axis according to embodiments of the present invention; [0018]FIG. 4C illustrates queue 3 for storing sampled data on Z-axis according to embodiments of the present invention; [0019]FIG. 5A illustrates writing the character of “L” with a mobile terminal according to embodiments of the present invention; [0020]FIG. 5B illustrates executing an application after the character “L” is written with a mobile terminal according to embodiments of the present invention; [0021]FIG. 6A illustrates writing the character of “Z” with a mobile terminal according to embodiments of the present invention; and [0022]FIG. 6B illustrates executing an application after the character “Z” is written with a mobile terminal according to embodiments of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION [0023]Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, a detailed explanation of known related functions and constitutions may be omitted to avoid unnecessarily obscuring the subject matter of the present invention. [0024]Hereinafter, although embodiments of the present invention will be described with reference to a mobile terminal as an example, the embodiments of the present invention may be applied to other similar apparatuses. Further, embodiments of the present invention may be applied to other apparatuses by those skilled in the arts through some modifications without departing from the spirit and scope of the present invention. [0025]FIG. 1 is a block diagram of a mobile terminal according to embodiments of the present invention. Referring to FIG. 1, a controller 100 executes a function of a mobile terminal and also performs an application control according to embodiments of the present invention. When a user writes using the mobile terminal, the controller 100 identifies motion traces that the mobile terminal has been moved, from accelerations detected by an acceleration sensor 104. When the identified motion traces are matched with a preset motion trace, a corresponding application is controlled by executing a control command mapped to the preset motion trace. [0026]A communication unit 102 performs communication for a data communication function and a phone call executed by the controller 100. The acceleration sensor 104 detects the acceleration when the mobile terminal moves. A display 106 displays a screen according to the movement of the mobile terminal by a control of the controller 100. An input/output interface 108 provides a user interface for an input and an output by the user for the controller 100. A memory 110 stores data according to an execution by the controller 100 and stores acceleration values detected by the acceleration sensor 104. The memory 110 may further include an external memory or further include a storage device such as a Hard Disk Drive (HDD). [0027]FIG. 2 shows a flowchart according to an embodiment of the present invention. Referring to FIG. 2, the controller 100 continuously collects acceleration values using an acceleration sensor 104 when the mobile terminal is being moved in step 200. [0028]In practical applications, accelerations occur in the mobile terminal in general when a user holds a mobile terminal and writes with the handheld mobile terminal in a space. The acceleration sensor 104 detects an acceleration of the mobile terminal. A detected acceleration value is a vector including scalar quantity values on the coordinate axes of a three-dimensional space, i.e., a value on the X-axis, the Y-axis and the Z-axis. [0029]In step 202, the controller 100 identifies a motion trace indicating that the mobile terminal has been moved from the collected acceleration values. [0030]The detected acceleration values are representative of the accelerations of the mobile terminal and cannot represent a motion trace. However, a plurality of continuous accelerations can represent a certain trend of the motion of the mobile terminal. Thus, in this step, a motion trace of the mobile terminal can be identified. [0031]This method is described by taking the X-axis as an example. Assuming that an acceleration value on the X-axis of the mobile terminal is detected as 2 when the mobile terminal is moved to point A, an acceleration value on the X-axis of the mobile terminal is detected as 4 when the mobile terminal is moved to point B, and an acceleration value on the X-axis of the mobile terminal is detected as 6 when the mobile terminal is moved to point C during continuous detection, it can be derived that the mobile terminal is moved in the X-axis positive direction at all of points A, B and C and is moved in the positive direction from point A to point B, and then point C. A motion trace described in the present invention means a shape of trace formed by motion trends, rather than a trace formed by positions in the three-dimensional space where the mobile terminal is. Description is given only by taking the X-axis as the sample. Processing on the Y-axis and the Z-axis is similar to that on the X-axis and will not be described herein. [0032]The method of identifying a motion trace is described in detail below. [0033]First, it is assumed that a first storage space, a second storage space and a third storage space provided by the memory 110 are used to store respective sampled values. Among these storage spaces, the first storage space includes M groups of subspaces to store M groups of values on the X-axis, the second storage space includes M groups of subspaces to store M groups of values on the Y-axis, and the third storage space includes M groups of subspaces to store M groups of values on the Z-axis. Thus, when step 200 is carried out, the acceleration sensor 104 performs sampling at a preset time interval. In other words, at a certain sampling frequency, when the mobile terminal is being moved and stores values on the X-axis obtained in the sampling in the M groups of subspaces of the first storage space, stores values on the Y-axis obtained in the sampling in the M groups of subspaces of the second storage space, and stores values on the Z-axis obtained in the sampling in the M groups of subspaces of the third storage space. Herein, M is a positive integer greater than or equal to 1. [0034]With the sampled data stored in the above manner, the values on the X-axis, the Y-axis, and the Z-axis can be separately processed as follows to identify a motion trace. [0035]I) For values in the first storage space, i.e., collected values (scalar quantity values) on the X-axis, M respective X-axis motion identifiers are determined based on values in the M groups of subspaces. An X-axis motion identifier is 1, −1 or 0.1 denotes motion in the X-axis positive direction, −1 denotes motion in the X-axis negative direction, and 0 denotes no motion on the X-axis. [0036]II) For values in the second storage space, i.e., collected values (scalar quantity values) on the Y-axis, M respective Y-axis motion identifiers are determined based on values in the M groups of subspaces. A Y-axis motion identifier is 1, −1 or 0.1 denotes motion in the Y-axis positive direction, −1 denotes motion in the Y-axis negative direction, and 0 denotes no motion on the Y-axis. [0037]III) For values in the third storage space, i.e., collected values (scalar quantity values) on the Z-axis, M respective Z-axis motion identifiers are determined based on values in the M groups of subspaces. A Z-axis motion identifier is 1, −1 or 0.1 denotes motion in the Z-axis positive direction, −1 denotes motion in the Z-axis negative direction, and 0 denotes no motion on the Z-axis. [0038]That is, no matter whether the values on the X-axis are positive, negative or zero, they represent a motion trace formed of motion trends on the X-axis so long as they are converted into M motion identifiers. This is because, assuming that there is one piece of sampled data in each of the groups of subspaces and the groups of subspaces are stored successively in a certain order, e.g., an order of group 1 to group M, as described above, if a sampled value is positive, it is converted into a motion identifier 1, which represents motion in the X-axis positive direction; if a sampled data is negative, it is converted into a motion identifier −1, which represents motion in the X-axis negative direction; if a sampled data is 0, it is kept unchanged and represents no motion on the X-axis. Thus, M successive converted motion identifiers can represent a motion trend on the X-axis. For values on the Y-axis and Z-axis, they can be converted into motion identifiers based on the above principle to represent a motion trend on the Y-axis/Z-axis. [0039]Specifically, at least the following two methods are available to perform the above determining of M motion identifiers. [0040]A first method: directly determining M motion identifiers based on values in M groups of subspaces, respectively. This method is the same as that in the above example. As another example, supposing that there are 8 groups of subspaces in a first storage space and values in the 8 groups. [0041]of subspaces are 1, 2, 4, −2, −4, 2, 3 and 4, respectively, a motion identifier corresponding to a positive number is set as 1, a motion identifier corresponding to a negative number is set as −1, while a motion identifier corresponding to 0 is set as 0. Thus, the motion identifiers corresponding to the 8 groups of subspaces in the first storage space are 1, 1, 1, −1, −1, 1, 1, and 1, respectively. Values in the second storage space or third storage space are processed in the same manner. In sum, in the first method, motion identifiers are determined directly based on values in M groups of subspaces. Moreover, in the above example, it is assumed that M is equal to 8 and there is only one sample value in each subspace, while in practical HI applications, M and a number of sampled value in each subspace vary with sampling methods. [0042]A second method: determining M motion identifiers based on values in M groups of subspaces, a still value (i.e., representing that the terminal is not being moved), and a threshold value. In this method, an acceleration sensor 104 determines the mobile terminal's not being moved as being moved by mistake due to factors such as inaccurate operation of the user and/or an error of the sensor and thereby obtain a certain sampled value when a user writes with a handheld mobile terminal. To eliminate this error, a still value representing the terminal not being moved and a threshold value are set. A sampled value is compared with the still value. If the difference between the sampled value and the still value falls within a range of the threshold value, the mobile terminal is regarded as not having been moved. If the difference falls outside the range of the threshold value, the mobile terminal is determined as having been moved in a positive or negative direction based on the particular case. [0043]Additionally, in order to increase accuracy of the identification, a high sampling frequency is set for more samples. To make processing more convenient, N data units can be provided in each subspace to store sampled values that have been obtained. For example, each of the M groups of subspaces of a first storage space includes N data units for respectively storing N values on the X-axis that have been obtained in sampling; each of the M groups of subspaces of a second storage space includes N data units for respectively storing N values on the Y-axis that have been obtained in sampling; each of the M groups of subspaces of a third storage space includes N data units for respectively storing N values on the Z-axis that have been obtained in sampling. Herein, N is an integer greater than or equal to 1 [0044]Thus, to convert the values stored in the M groups of subspaces of each of the first, second and third storage spaces, the second method performs the following steps. [0045]For the X-axis, the method includes the following steps:[0046]x1. selecting a first group as the current group;[0047]x2. subtracting a first still value from the N values stored in the current group and comparing the differences between the N values and the first still value with a preset first threshold value to obtain N comparison results, wherein the N comparison results are obtained as follows. If a difference is larger than the preset first threshold value, the corresponding comparison result is 1; if a difference is smaller than the minus preset first threshold value (i.e., a negative preset first threshold value). the corresponding comparison result is −1; if the absolute value of a difference is smaller than the preset first threshold value, the corresponding comparison result is 0;[0048]x3. counting the N comparison results of the current group and taking one of 1, −1 and 0 whose number of the N comparison results is the maximum as the X-axis motion identifier corresponding to the current group of subspace;[0049]x4. selecting the next group as the current group and returning to x2 unless all of the M groups of subspaces are processed. [0050]Similar steps y1 to y4 and z1 to z4 occur for the Y-axis and Z-axis, respectively. [0051]As described above, the processing methods for values on the X-axis, Y-axis, and Z-axis are similar. All of these methods subtract a corresponding still value from the N data in a group of subspace, to compare the differences with a corresponding threshold value to determine whether the differences fall within or outside a range of the threshold, and to determine the motion identifier of the group of subspace based on results of the comparison. Since each storage space has M groups of subspaces, M motion identifiers are obtained in all of the these methods after the above processing is performed. The M motion identifiers can represent a motion trace on a certain axis as in the first method. Of course, a motion trace identified by the second method should be more accurate than that by the first method since factors such as inaccurate operation of a user and an error of the sensor is eliminated in the second method. [0052]Moreover, all of the first still value, the second still value and the third still value represent no motion. They are the same or different. Similarly, each of the first threshold value, the second threshold value and the third threshold value represents a certain range. [0053]Step 204, the controller 100 matches the identified motion trace with a preset motion trace, and executes a control command mapped to the preset motion trace to control an application in the mobile terminal if the matching succeeds. [0054]This step compares the X-axis motion identifier, the Y-axis motion identifier and the Z-axis motion identifier and determines whether the matching has succeeded based on the results of the comparisons. The control command mapped is automatically executed and thereby the application in the mobile terminal is controlled if the matching succeeds. [0055]In another embodiment of the present invention, it is assumed that a sampling frequency of the acceleration sensor 104 in a mobile terminal is 400 Hz, i.e., the acceleration sensor collects data once every 0.0025 seconds. That is, every second, 400 pieces of data on the X-axis, 400 pieces of data on the Y-axis and 400 pieces data on the Z-axis are collected. It is also assumed that each of a first storage space, a second storage space and a third storage space to store sampled data includes M groups of subspaces, each of which includes N data units. Herein, M=8, and N=50. In this embodiment, the first storage space, the second storage space and the third storage space are shown using queue 1, queue 2, queue 3, respectively. Each of the queues has 8 nodes and each of the nodes includes 50 data units. Moreover, the sampled data is stored in an order of queue head to queue tail when sampled data are HI stored. The data at the queue head is deleted and a node storing the new sampled data is inserted to the queue tail when data units of all of the nodes are occupied. That is, in this embodiment, each of the queues always stores the 400 sampled data that have been last obtained. Sampled data is stored in another data structure other than a queue. [0056]Moreover, it is also assumed in this embodiment that the controller 100 has an application control-setting module that operates in two modes, i.e., a motion trace-presetting mode and a motion trace-identifying mode. [0057]FIG. 3 shows a flowchart of the method of this embodiment. Referring to FIG. 3, the controller 100 allows the acceleration sensor 104 to perform sampling at an rate of 0.0025 second and to store values on the X-axis obtained in the sampling in queue 1, store values on the Y-axis obtained in the sampling in queue 2, while store values on the Z-axis obtained in the sampling in queue 3, when the mobile terminal is being moved in step 300. [0058]Queues 1, 2 and 3 in this step is shown as in FIGS. 4A to 4C, respectively. As described above, the sampled data is stored in the order of queue head to queue tail. For example, the first group of 50 data are placed at the head node of a queue when 50 pieces sampled data are obtained. After 0.125 seconds (50*0.0025 seconds), the second group of 50 sampled data is stored at the second node. After another 0.125 seconds, the third group of 50 sampled data is stored at the third node, and so on. When all of 8 nodes of a queue are full, data at the head node of the queue is deleted and the node storing the 50 sampled data that have been recently obtained is stored at the tail of the queue. In sum, each of queues 1, 2 and 3 always stores the 400 pieces of data that have been obtained lately. [0059]In step 302, the controller 100 determines whether the application control-setting module is running, and if so, step 304 is performed. Otherwise, step 306 is performed. [0060]In step 304, the controller 100 determines the current mode for the application control-setting module. If the current mode is the motion trace-presetting mode, step 312 is performed. If the current mode is the motion trace-identifying mode, step 306 is performed. [0061]In this embodiment, the application control-setting module is provided in the mobile terminal and the function of motion trace presetting or motion trace identifying is started by the application control-setting module. However, the application control-setting module is not provided in practical applications. Whether the application control-setting module is present does not affect the implementation of the solution, and steps 302 and 304 may be omitted. [0062]In step 306, 8 X-axis motion identifiers are determined from the values in queue 1, 8 Y-axis motion identifiers are determined from the values in queue 2, and 8 Z-axis motion identifiers are determined from the values in queue 3. [0063]Determining the 8 X-axis motion identifiers can be done in the method of the above steps x1 to x4, determining of the 8 Y-axis motion identifiers can be done in the method of the above steps y1 to y4, and determining of the 8 Z-axis motion identifiers can be done in the method of the above steps z1 to z4, all of which will not be described herein. [0064]All of the nodes of a queue do not store sampled data when sampling has just started. For example, only the head node of the queue stores sampled data while none of the other nodes stores data at 0.125 second. Thus, only the motion identifier corresponding to the head node of the queue can be determined. After 0.125 second, the second node of the queue also stored sampled data as described in step 300. Thus, the motion identifier corresponding to the second node can be determined. Herein, the queue and the motion identifiers are not specified and can be for the X-axis, Y-axis or Z-axis. [0065]Additionally, since an error may occur during operation, a first still value, a second still value and a third still value are be further updated in this step when the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers are determined. That is, between steps x3 and x4, the method further includes the following step to be performed when the 8 X-axis motion identifiers are determined. Determining whether the X-axis motion identifier corresponding to the current group is 0 and. if so, calculating a mean of the N values (N values on the X-axis) of the current group and updating the first still value as the calculated mean; otherwise, returning to step x4. A similar step can occur between steps y3 and y4 and z3 and z4. [0066]These steps are used to update the still values because during the operation by a user, a mobile terminal is substantially still if a motion identifier corresponding to the current group of data is 0. However, all of the N (in this embodiment, N is 50) pieces of data of the current group on each of the axes are not necessarily equal to the still value due to an error of operation or measurement. Thus, if the still value is set as a mean of the N values, the N values as a whole are closer to the still value, thereby, avoiding the case that the mobile terminal is not being moved is mistaken for being moved. [0067]In step 308, the identified motion trace is matched with a preset motion trace, and step 310 is performed if the matching succeeds. Otherwise, the process returns to step 300. [0068]Steps 300 to 308 form a large cycle, in which the acceleration sensor 104 in the mobile terminal performs sampling continuously and accesses the queues every 0.125 second. Accordingly, a motion trace is identified for the mobile terminal every 0.125 second. The identification may fail within the first one second from when sampling is started since all of the nodes in a queue do not store data and thus the determined 8 motion identifiers are inaccurate. However, all the nodes in the queue store sampled data after the one second. Thereby, effective 8 motion identifiers can be determined. As described in an embodiment above, X-axis motion identifiers, Y-axis motion identifiers and Z-axis motion identifiers represent a motion trace that a mobile terminal has been moved. In this embodiment, a preset motion trace is also represented using X-axis motion identifiers, Y-axis motion identifiers and Z-axis motion identifiers. Thus, whether the matching succeeds is determined by comparing the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers determined in step 306 with the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers of the preset motion trace, respectively. [0069]The matching does not necessarily succeed at once after the one second of sampling. However, as described in step 300, the acceleration sensor may continue with sampling, new motion identifiers may be determined from the sampled data that have been obtained lately for the mobile terminal, and matching with the preset motion trace is made in step 308 again. Once the matching succeeds, the next step 310 is performed. [0070]The matching in step 308 is performed in a manner of exact match or a manner of approximate matching in practical applications. The manner of exact matching means that the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers of an identified motion trace are the same as the 8 X-axis motion identifiers, the 8 Y-axis motion identifiers and the 8 Z-axis motion identifiers of a preset motion trace, respectively. The manner of approximate matching means that the motion identifiers on the three axes are not completely the same but a number of pairs of motion identifiers being the same is larger than a preset matching threshold value. For example, a matching threshold value is preset as 6 and 7 motion identifiers on each of the axes of an identified motion trace are the same as those of a preset motion trace, respectively. In this case, the number, 7, is larger than the matching threshold value 6. This would be a case of matching succeeding. [0071]A time threshold value also can be set. Identification is not performed anymore (i.e., no return to step 300) to avoid an infinite loop when the threshold value is exceeded. [0072]In step 310, a control command mapped to the preset motion trace is executed to control an application in the mobile terminal, and this procedure is completed. [0073]In step 312, acceleration values are continuously collecting using an acceleration sensor 104 when a mobile terminal is being moved. The same method as that for step 300 can be used for this step and will not be described herein. [0074]In step 314, a motion trace that the mobile terminal has been moved is identified from the collected acceleration values and the identified motion trace is displayed to the user through the display 106. [0075]The same method as that in step 306 is used to identify the motion trace. Moreover, after the motion trace is identified, the motion trace is visualized as a character to be displayed to the user through the display 106 for the convenience of confirmation by the user. [0076]In step 316, whether a confirmation instruction is received from the user is determined, and if the confirmation instruction is received through the input/output interface 108, step 318 is performed. Otherwise, return to step 312. [0077]In step 318, the identified motion trace is saved and this procedure is completed. [0078]A preset motion trace occurs in steps 312 to 318. If there is an application control-setting module in a mobile terminal, this module also can provide functions of displaying, searching for, associating and deleting a preset motion trace for more exact operation by a user. Steps 312 to 318 make a preset motion trace and are not necessary in an identifying process. Thus, they can be omitted in identifying a motion trace and controlling an application. [0079]It is easy to bind a control command to a preset motion trace in applications. For example, a database is provided to store corresponding relationships between preset motion traces and control commands. Thus, after matching succeeds in step 308, the motion trace whose matching succeeds is searched for in the database and a corresponding control command is executed. [0080]FIGS. 5A, 5B, 6A, and 6B each show examples illustrating controlling an application in accordance with an embodiment of the present invention. As shown in FIG. 5A, a user writes the character, “L”, with a handheld mobile terminal in the air. A motion trace is formed during motion of the mobile terminal. Supposing that this motion trace is preset in the mobile terminal and is mapped to the control command of “Opening” the application “Notepad”, “Notepad” is automatically opened once the matching succeeds. The result is shown in FIG. 5B. [0081]In another example, as shown in FIG. 6A, a user writes the character, “Z”, with a handheld mobile terminal in the air. A motion trace is formed during motion of the mobile terminal. Assuming that this motion trace is preset in the mobile terminal and is mapped to the control command of “Opening” the application “instant messenger”, “instant messenger” is automatically opened once the matching succeeds. The result is shown in FIG. 6B. [0082]By applying this embodiment, a motion trace formed during motion of the mobile terminal is identified by means of an acceleration sensor 104 when a user writes with a handheld mobile terminal. A corresponding control command is started when the identified motion trace succeeds in matching with a preset motion trace. Thus, the objective of controlling an application is achieved. The user can write any characters and pictures not only simple shakes with the handheld mobile terminal. Thus, a lot of motion traces can be formed and a lot of control commands can thereby be mapped. Consequently, it is possible to easily control various applications in the mobile terminal by a user writing with a handheld mobile terminal. [0083]Embodiments of the present invention can be implemented by hardware, software, and a combination of the hardware and the software. For example, the software can be stored, regardless of possibility of omission or rewrite, in volatile or non-volatile storage devices such as memories such as a Read Only Memory (ROM), a Random Access Mem(String), 优先 [0001] 本申请根据 35 U.S.C. §119(a) 于 2011 年 2 月 16 日向中华人民共和国国家知识产权局提交的中国专利申请,并转让了序列号。 第 201110041328.4 号,其全部公开内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明总体上涉及移动终端,更具体地,涉及用于控制移动终端中的应用的方法和装置。 [0004] 二、发明背景 [0005] 移动终端、平板电脑、智能手机等各种移动终端的功能越来越多,具体来说,不仅可以实现通话等基本的通信服务,还可以实现各种应用。 当要启动或退出应用程序时,用户通过逐级选择移动终端提供的菜单来进行启动或退出操作。 然而,这样的操作是不方便的。 [0006] 一些高端移动终端还允许用户在移动终端中控制应用中的特殊功能。 例如,用户可以通过摇动终端放大图片或控制游戏。 但是,所有这些控件都很简单。 对应用程序的控制提出了越来越多的要求。 因此,终端的简单晃动难以满足更复杂的用户需求。 发明内容 [0007] 因此,本发明提供了一种能够容易地控制移动终端的各种应用的方法和移动终端。 [0008] 本发明还提供了一种用户通过移动终端书写控制移动终端应用的方法及移动终端。 [0009] 根据本发明的一个方面,提供了一种在移动终端中控制应用的方法。 该方法包括当移动终端正在移动时,使用加速度传感器连续采集加速度值; 从采集的加速度值中识别移动终端移动的运动轨迹; 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。 [0010] 根据本发明的另一方面,提供了一种移动终端。 终端包括加速度传感器,用于检测移动终端移动时的加速度; 控制器,用于在移动终端移动过程中连续使用加速度传感器采集加速度值,从采集的加速度值中识别移动终端已经移动的运动轨迹,将识别的运动轨迹与预设的运动轨迹进行匹配,执行 如果匹配成功,则映射到预设运动轨迹的控制命令,以控制移动终端中的应用程序。 [0011] 因此,根据本发明,用户可以书写任何类型的字符和图片,而不仅仅是用手持移动终端进行简单的摇晃。 因此,可以形成运动轨迹,从而可以通过运动轨迹映射控制命令。 因此,可以通过用户用手持移动终端书写来容易地控制移动终端中的各种应用。 附图的简要说明 [0012] 本发明的上述和其他方面、特征和优点将从以下结合附图的详细描述中变得更加明显,其中: [0013] 如图。 附图说明图1示出了根据本发明实施例的移动终端; [0014] 如图。 图2为本发明第一实施例的流程图。 [0015] 如图。 图3为本发明第二实施例的流程图。 [0016] 如图。 图4A图示了队列 1 根据本发明的实施例,用于存储X轴上的采样数据; [0017]如图。 图4B图示了队列 2 根据本发明的实施例,用于在Y轴上存储采样数据; [0018] 如图。 图4C图示了队列 3 根据本发明的实施例,用于存储Z轴上的采样数据; [0019] 如图。 图5A为本发明实施例用移动终端书写“L”字的示意图。 [0020] 如图。 图5B为本发明实施例在移动终端写入字符“L”后执行应用程序的示意图。 [0021] 如图。 图6A为本发明实施例用移动终端书写“Z”字的示意图。 和 [0022] 如图。 图6B示出了根据本发明的实施例在利用移动终端写入字符“Z”之后执行应用程序。 本发明实施方案的详细说明 [0023] 在下文中,将参照附图描述本发明的实施例。 在以下描述中,可能省略对已知相关功能和构成的详细说明以避免不必要地混淆本发明的主题。 [0024] 在下文中,虽然将参考移动终端作为示例来描述本发明的实施例,但是本发明的实施例可以应用于其他类似的装置。 此外,本领域技术人员在不脱离本发明的精神和范围的情况下,可以通过一些修改将本发明的实施例应用于其他装置。 [0025] 如图。 图1是根据本发明实施例的移动终端的框图。 参考图。 1、一个控制器 100 根据本发明的实施例,执行移动终端的功能并且还执行应用控制。 当用户使用移动终端书写时,控制器 100 根据加速度传感器检测到的加速度识别移动终端已移动的运动轨迹 104 . 当识别出的运动轨迹与预设运动轨迹匹配时,通过执行映射到预设运动轨迹的控制命令来控制相应的应用程序。 [0026] 通讯单元 102 为控制器执行的数据通信功能和电话进行通信 100 . 加速度传感器 104 检测移动终端移动时的加速度。 一个显示器 106 通过控制器的控制根据移动终端的移动显示屏幕 100 . 输入/输出接口 108 为控制器提供用户输入和输出的用户界面 100 . 一段记忆 110 根据控制器的执行存储数据 100 并存储加速度传感器检测到的加速度值 104 . 记忆 110 可以进一步包括外部存储器或者进一步包括诸如硬盘驱动器(HDD)的存储设备。 [0027] 如图。 图2示出了根据本发明实施例的流程图。 参考图。 2、控制器 100 使用加速度传感器连续收集加速度值 104 当移动终端在步中移动时 200 . [0028] 在实际应用中,当用户手持移动终端在空间中书写时,移动终端一般会出现加速度。 加速度传感器 104 检测移动终端的加速度。 检测到的加速度值是包括在三维空间的坐标轴上的标量值的向量,即在X轴、Y轴和Z轴上的值。 [0029] 在步骤 202 , 控制器 100 从收集的加速度值中识别指示移动终端已经移动的运动轨迹。 [0030]检测到的加速度值代表移动终端的加速度,不能代表运动轨迹。 然而,多个连续的加速度可以代表移动终端运动的某种趋势。 因此,在本步骤中,可以识别出移动终端的运动轨迹。 [0031] 该方法以X轴为例进行说明。 假设移动终端移动到A点时检测到移动终端X轴上的加速度值为2,则移动终端移动时检测到移动终端X轴上的加速度值为4 到B点,连续检测移动终端移动到C点时,检测到移动终端X轴加速度值为6,可以推导出移动终端在X轴正方向移动 从A点到B点,再到C点的正向运动。本发明所述的运动轨迹是指运动趋势形成的轨迹形状,而不是运动轨迹。 由移动终端所在的三维空间中的位置形成的轨迹。 仅以X轴为例进行说明。 Y轴和Z轴的处理与X轴的处理类似,在此不再赘述。 [0032] 下面详细描述识别运动轨迹的方法。 [0033] 首先,假设存储器提供第一存储空间、第二存储空间和第三存储空间 110 用于存储各自的采样值。 在这些存储空间中,第一存储空间包括M组子空间,用于在X轴上存储M组值,第二存储空间包括M组子空间,用于在Y轴上存储M组值,第三存储空间包括M组子空间,用于存储M组值。 存储空间包括 M 组子空间,用于在 Z 轴上存储 M 组值。 因此,当步 200 执行时,加速度传感器 104 以预设的时间间隔进行采样。 也就是说,在某个采样频率下,当移动终端正在移动时,将采样得到的X轴值存储在第一存储空间的M组子空间中,Y轴上的值存储在第一存储空间的M组子空间中。 在第二存储空间的M组子空间中进行采样,并将采样得到的Z轴上的值存储在第三存储空间的M组子空间中。 其中,M为大于或等于1的正整数。 [0034] 通过上述方式存储的采样数据,可以分别对X轴、Y轴和Z轴上的值进行如下处理以识别运动轨迹。 [0035] i)对于第一存储空间中的值,即X轴上的采集值(标量值),根据M组子空间中的值确定M个各自的X轴运动标识。 X轴运动标识为1,-1或0.1表示X轴正方向运动,-1表示X轴负方向运动,0表示X轴无运动。 [0036] II)对于第二存储空间中的值,即Y轴上的采集值(标量值),根据M组子空间中的值确定M个各自的Y轴运动标识。 Y轴运动标识为1,-1或0.1表示Y轴正方向运动,-1表示Y轴负方向运动,0表示Y轴无运动。 [0037] III)对于第三存储空间中的值,即Z轴上的采集值(标量值),根据M组子空间中的值确定M个各自的Z轴运动标识。 Z轴运动标识为1,-1或0.1表示Z轴正方向运动,-1表示Z轴负方向运动,0表示Z轴无运动。 [0038]即无论X轴上的数值是正数、负数还是零,只要转换成M个运动标识,它们就代表了X轴上运动趋势形成的运动轨迹。 这是因为,假设每组子空间中有一个采样数据,并且子空间组按照一定的顺序依次存储,例如组的顺序 1 到组M,如上所述,如果采样值为正,则将其转换为运动标识符 1 , 表示 X 轴正方向的运动; 如果采样数据为负数,则将其转换为运动标识符-1,表示X轴负方向的运动; 如果采样数据为 0,则保持不变,表示 X 轴上没有运动。 因此,M个连续转换的运动标识符可以代表X轴上的运动趋势。 对于Y轴和Z轴上的数值,可以根据上述原理转换为运动标识,表示Y轴/Z轴上的运动趋势。 [0039] 具体地,至少可以采用以下两种方法来进行上述M个运动标识的确定。 [0040] 第一种方法:分别根据M组子空间中的值直接确定M个运动标识。 该方法与上例相同。 再如,假设第一存储空间有8组子空间,8组中的值。 [0041] 子空间的个数分别为1、2、4、-2、-4、2、3、4,正数对应的运动标识符设为1,负数对应的运动标识符设为-1, 而0对应的运动标识设置为0。因此,第一存储空间中8组子空间对应的运动标识分别为1、1、1、-1、-1、1、1、1 . 第二存储空间或第三存储空间中的值的处理方式相同。 总之,在第一种方法中,运动标识符是直接基于M组子空间中的值来确定的。 此外,在上面的例子中,假设 M 等于 8,每个子空间中只有一个样本值,而在实际的 HI 应用中,M 和每个子空间中的采样值数量会随着采样方法的不同而变化。 [0042] 第二种方法:根据M组子空间中的值、静止值(即表示终端没有被移动)和阈值确定M个运动标识。 在该方法中,加速度传感器 104 由于用户的操作不准确和/或传感器的错误等因素,将移动终端没有移动判断为误移动,从而在用户使用手持移动终端书写时获得一定的采样值。 为了消除该错误,设置了表示终端未移动的静止值和阈值。 将采样值与静止值进行比较。 如果采样值与静止值之差在阈值范围内,则认为移动终端没有移动。 如果差值落在阈值的范围之外,则根据具体情况确定移动终端已经在正方向或负方向上移动。 [0043] 另外,为了提高识别的准确性,对更多的样本设置了较高的采样频率。 为了使处理更加方便,可以在每个子空间中提供N个数据单元来存储已经获得的采样值。 例如,第一存储空间的M组子空间中的每一个包括N个数据单元,用于分别存储采样得到的X轴上的N个值。 第二存储空间的M组子空间中的每一个包括N个数据单元,用于分别存储采样得到的Y轴上的N个值。 第三存储空间的M组子空间中的每组子空间包括N个数据单元,用于分别存储采样得到的Z轴上的N个值。 这里,N为大于或等于1的整数 [0044] 因此,为了转换存储在第一、第二和第三存储空间中的每一个的M组子空间中的值,第二方法执行以下步骤。 [0045]对于X轴,该方法包括以下步骤: [0046]x1。 选择第一组作为当前组;[0047] x2。 从当前组中存储的N个值中减去第一静止值,并将N个值与第一静止值的差值与预设的第一阈值进行比较,得到N个比较结果,其中,N个比较结果的得到如下。 如果差值大于预设的第一阈值,则对应的比较结果为1; 如果差值小于负预设第一阈值(即负预设第一阈值)。 对应的比较结果为-1; 如果差值的绝对值小于预设的第一阈值,则对应的比较结果为0。[0048] x3。 统计当前组的N个比较结果,取N个比较结果个数最大的1、-1和0之一作为当前组子空间对应的X轴运动标识;[0049] x4。 选择下一组作为当前组并返回 x2,除非所有 M 组子空间都被处理。 [0050] 类似的步骤 y1 到 y4 和 z1 到 z4 分别发生在 Y 轴和 Z 轴上。 [0051] 如上所述,X轴、Y轴和Z轴上的值的处理方法是相似的。 这些方法都是从一组子空间中的N个数据中减去一个对应的静止值,将差异与对应的阈值进行比较,判断差异是在阈值范围内还是在阈值范围外,从而确定运动标识。 基于比较结果的子空间组。 由于每个存储空间有M组子空间,经过上述处理,所有这些方法都得到了M个运动标识。 M个运动标识符可以表示在某个轴上的运动轨迹,如在第一种方法中。 当然,第二种方法识别的运动轨迹应该比第一种方法更准确,因为第二种方法消除了用户操作不准确、传感器错误等因素。 [0052] 此外,第一静止值、第二静止值和第三静止值均表示没有运动。 它们相同或不同。 类似地,第一阈值、第二阈值和第三阈值分别代表一定范围。 [0053] 步 204 , 控制器 100 将识别出的运动轨迹与预设运动轨迹进行匹配,如果匹配成功,则执行映射到预设运动轨迹的控制命令来控制移动终端中的应用。 [0054] 本步骤将X轴运动标识、Y轴运动标识和Z轴运动标识进行比较,根据比较结果判断匹配是否成功。 映射的控制命令自动执行,从而在匹配成功时控制移动终端中的应用程序。 [0055] 在本发明的另一实施例中,假设加速度传感器的采样频率为 104 在移动终端中为 400 Hz,即加速度传感器每 0.0025 秒采集一次数据。 即,每秒收集400条X轴数据、400条Y轴数据和400条Z轴数据。 还假设用于存储采样数据的第一存储空间、第二存储空间和第三存储空间中的每一个包括M组子空间,每组子空间包括N个数据单元。 在此,M=8,N=50。 在本实施例中,第一存储空间、第二存储空间和第三存储空间使用队列来表示 1 , 队列 2 , 队列 3 , 分别。 每个队列有 8 个节点,每个节点包含 50 个数据单元。 此外,当采样数据被HI存储时,采样数据以队列头到队列尾的顺序存储。 当所有节点的数据单元都被占用时,删除队列头的数据,并在队列尾插入一个存储新采样数据的节点。 即,在本实施例中,每个队列总是存储最后一次获得的400个采样数据。 采样数据存储在队列以外的另一个数据结构中。 [0056] 此外,在本实施例中还假设控制器 100 具有应用控制设置模块,工作在两种模式下,即运动轨迹预设模式和运动轨迹识别模式。 [0057] 如图。 图3示出了本实施例的方法的流程图。 参考图。 3、控制器 100 允许加速度传感器 104 以 0.0025 秒的速率执行采样,并将在队列中采样中获得的值存储在 X 轴上 1 , 将采样得到的 Y 轴值存储在队列中 2 , 同时将采样得到的 Z 轴值存储在队列中 3 ,当移动终端在步中移动时 300 . [0058] 队列 1 , 2 和 3在这一步中,如图所示。 分别参照图4A至4C。 如上所述,采样数据以队列头到队列尾的顺序存储。 例如,当得到50条采样数据时,将第一组50条数据放在队列的头节点。 0.125秒(50*0.0025秒)后,第二组50个采样数据存储在第二个节点。 再过 0.125 秒,第三组 50 个采样数据存储在第三个节点,以此类推。 当一个队列的8个节点都满时,删除队列头节点的数据,将存储最近获得的50个采样数据的节点存储在队列的尾部。 总之,每个队列 1 , 2 和 3 总是存储最近获取的400条数据。 [0059] 在步骤 302 , 控制器 100 判断应用控制设置模块是否正在运行,如果是,则步骤 304 被执行。 否则,步 306 被执行。 [0060] 在步骤 304 , 控制器 100 确定应用程序控制设置模块的当前模式。 如果当前模式为运动轨迹预置模式,则步骤 312 被执行。 如果当前模式为运动轨迹识别模式,则步骤 306 被执行。 [0061] 在本实施例中,在移动终端中设置应用控制设置模块,通过应用控制设置模块启动运动轨迹预设或运动轨迹识别功能。 但实际应用中并未提供应用控制设置模块。 应用控制设置模块是否存在不影响方案的实现,步骤 302 和 304 可以省略。 [0062] 在步骤 306 , 8 个 X 轴运动标识符由队列中的值确定 1 , 8 个 Y 轴运动标识符由队列中的值确定 2 , 和 8 个 Z 轴运动标识符由队列中的值确定 3 . [0063] 确定8个X轴运动标识可以按照上述步骤x1到x4的方法,确定8个Y轴运动标识可以按照上述步骤y1到y4的方法,确定8个Y轴运动标识 Z轴运动识别可以按照上述步骤z1至z4的方法进行,在此不再赘述。 [0064] 当采样刚刚开始时,队列的所有节点都不会存储采样数据。 例如,只有队列的头节点存储采样数据,而其他节点均不存储 0.125 秒的数据。 因此,只能确定队列头节点对应的运动标识。 0.125 秒后,队列的第二个节点也存储采样数据,如步骤中所述 300 . 因此,可以确定对应于第二节点的运动标识符。 这里,队列和运动标识符没有指定,可以是X轴、Y轴或Z轴。 [0065] 另外,由于操作过程中可能会出现错误,因此在本步骤中,当8个X轴运动标识、8个Y轴运动标识和8个 Z轴运动标识符被确定。 也就是说,在步骤x3和x4之间,该方法还包括在确定8个X轴运动标识时要执行的以下步骤。 判断当前组对应的X轴运动标识是否为0和。 如果是,则计算当前组的 N 个值(X 轴上的 N 个值)的平均值,并将第一个静止值更新为计算的平均值; 否则,返回步骤 x4。 在步骤 y3 和 y4 以及 z3 和 z4 之间可以发生类似的步骤。 [0066]这些步骤用于更新静止值,因为在用户操作过程中,如果当前组数据对应的运动标识为0,则移动终端实质上是静止的。但是,所有的N(本实施例中,N为 50) 由于运算或测量误差,各轴当前组的数据不一定等于静止值。 这样,如果将静止值设置为N个值的平均值,则N个值整体上更接近于静止值,从而避免了移动终端没有被移动被误认为移动的情况。 [0067] 在步骤 308 ,识别出的运动轨迹与预设的运动轨迹相匹配,步 310 如果匹配成功则执行。 否则,过程返回步骤 300 . [0068] 脚步 300 至 308 形成一个大循环,其中加速度传感器 104 移动端连续采样,每0.125秒访问队列。 因此,每0.125秒为移动终端识别运动轨迹。 由于队列中的所有节点都不存储数据,因此确定的 8 个运动标识符不准确,因此识别可能会在采样开始后的第一秒内失败。 但是,队列中的所有节点都存储一秒钟后的采样数据。 因此,可以确定有效的8个运动标识符。 如以上实施例所述,X轴运动标识符、Y轴运动标识符和Z轴运动标识符表示移动终端已经移动的运动轨迹。 在本实施例中,还使用X轴运动标识符、Y轴运动标识符和Z轴运动标识符来表示预设的运动轨迹。 因此,通过比较步骤中确定的8个X轴运动标识符、8个Y轴运动标识符和8个Z轴运动标识符来确定匹配是否成功 306 分别与预设运动轨迹的8个X轴运动标识符、8个Y轴运动标识符和8个Z轴运动标识符。 [0069] 匹配不一定在采样一秒后立即成功。 但是,如步骤中所述 300 ,加速度传感器可以继续采样,可以从移动终端最近获取的采样数据中确定新的运动标识,并与预设的运动轨迹进行匹配。 308 再次。 一旦匹配成功,下一步 310 被执行。 [0070] 步内匹配 308 在实际应用中以精确匹配或近似匹配的方式进行。 精确匹配的方式是指识别出的运动轨迹的8个X轴运动标识符、8个Y轴运动标识符和8个Z轴运动标识符与8个X轴运动标识符、8个Y轴运动标识符相同。 轴运动标识符和预设运动轨迹的 8 个 Z 轴运动标识符。 近似匹配的方式是指三个轴上的运动标识不完全相同,但相同的运动标识对的数量大于预设的匹配阈值。 例如,预设匹配阈值,识别出的运动轨迹的每个轴上的6个和7个运动标识符分别与预设的运动轨迹相同。 在这种情况下,数字 7 大于匹配阈值 6。这将是匹配成功的情况。 [0071] 也可以设置时间阈值。 不再进行识别(即不返回步骤 300 ) 以避免在超过阈值时出现无限循环。 [0072] 在步骤 310 ,执行映射到预设运动轨迹的控制命令,控制移动终端中的应用程序,完成本流程。 [0073] 在步骤 312 , 加速度值使用加速度传感器不断收集 104 移动终端时。 与步骤相同的方法 300 可用于该步骤,此处不再赘述。 [0074] 在步骤 314,从采集的加速度值中识别出移动终端已经移动的运动轨迹,并将识别出的运动轨迹通过显示器显示给用户 106 . [0075] 方法同步骤 306 用于识别运动轨迹。 此外,在识别出运动轨迹后,将运动轨迹可视化为要通过显示器显示给用户的字符 106 为方便用户确认。 [0076] 在步骤 316 ,判断是否接收到用户的确认指令,以及是否通过输入/输出接口接收到确认指令 108 , 步 318 被执行。 否则返回步骤 312 . [0077] 在步骤 318 ,识别出的运动轨迹被保存,此过程完成。 [0078] 预设的运动轨迹分步出现 312 至 318 . 如果移动终端中有应用控制设置模块,该模块还可以提供显示、查找、关联和删除预设运动轨迹的功能,以便用户进行更准确的操作。 脚步 312 至 318 进行预设的运动轨迹,在识别过程中不是必需的。 因此,在识别运动轨迹和控制应用程序时可以省略它们。 [0079] 在应用程序中很容易将控制命令绑定到预设的运动轨迹。 例如,提供一个数据库来存储预设的运动轨迹与控制命令之间的对应关系。 因此,在匹配成功后 308 ,在数据库中查找匹配成功的运动轨迹并执行相应的控制命令。 [0080] 图 5A, 5 乙, 6 一个,和 6 B各自示出了说明根据本发明实施例控制应用的示例。 如图所示。 在图5A中,用户用手持移动终端在空中书写字符“L”。 移动终端在运动过程中形成运动轨迹。 假设该运动轨迹预设在移动终端中,并映射到“打开”应用“记事本”的控制命令,一旦匹配成功,“记事本”就会自动打开。 结果示于图3。 5B。 [0081] 在另一个示例中,如图 3 所示。 参照图6A,用户用手持移动终端在空中书写字符“Z”。 移动终端在运动过程中形成运动轨迹。 假设该动作轨迹预设在移动终端中,并映射到“打开”应用程序“即时通讯”的控制命令,一旦匹配成功,“即时通讯”就会自动打开。 结果示于图3。 6B。 [0082] 应用本实施例,通过加速度传感器识别移动终端运动过程中形成的运动轨迹 104 当用户使用手持移动终端书写时。 当识别出的运动轨迹与预设的运动轨迹匹配成功时,启动相应的控制命令。 从而达到控制应用程序的目的。 用户不仅可以用手持移动终端简单的摇一摇,还可以书写任何文字和图片。 因此,可以形成很多运动轨迹,从而可以映射很多控制命令。 因此,可以通过用户用手持移动终端书写来容易地控制移动终端中的各种应用。 [0083]本发明的实施例可以通过硬件、软件以及硬件和软件的结合来实现。 例如,软件可以存储在易失性或非易失性存储设备中,例如只读存储器(ROM)、随机存取存储器(RAM)、存储芯片、 设备或集成电路,以及光或磁可记录和机器可读的存储介质,例如压缩盘(CD)、数字多功能盘(DVD)、磁盘、磁带等。 可以包括在移动终端中的存储器是包括用于实现本发明的实施例的指令的程序或适合于存储程序的机器可读存储介质的示例。 因此,本发明包括包含代码的程序,以实现在说明书的某些权利要求中陈述的系统或方法,以及存储这种程序的机器可读存储介质。 此外,程序可以通过诸如通过有线或无线连接传输的通信信号之类的特定媒体以电子方式传输。 [0084] 根据本发明实施例的控制移动终端中应用程序的方法可以制作成程序的形式存储在存储介质中,移动终端可以通过下载程序向用户提供应用程序控制( 例如,应用程序)用于控制来自程序提供服务器的应用程序,安装下载的程序,并执行安装的程序。 即,当用于控制应用的程序安装在移动终端中时,执行该程序,然后将应用控制提供给用户。 节目提供服务器从移动终端接收对节目的传输请求,并响应传输请求将节目传输到移动终端。 节目提供服务器可以判断发出节目传输请求的移动终端是否为用户终端,进而进行用户鉴权和支付信息识别。 程序提供服务器可以包括存储程序的存储介质。 此外,存储介质可以位于程序提供服务器内部或程序提供服务器外部。 [0085] 尽管已经参照某些实施例及其附图显示和描述了本发明,但本领域技术人员将理解,在不背离本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变。 由所附权利要求及其等价物定义。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.521 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.521 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.540 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.549 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102647504A(String), CN102647504B(String), EP2490104A1(String), EP2490104B1(String), KR101892065B1(String), KR1020120094447A(String), US20120208555A1(String), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.652 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.653 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.672 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.705 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.705 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102647504A(String), CN102647504B(String), EP2490104A1(String), EP2490104B1(String), KR101892065B1(String), KR1020120094447A(String), US20120208555A1(String), US8914010B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102647504A(String), CN102647504B(String), EP2490104A1(String), EP2490104B1(String), KR101892065B1(String), KR1020120094447A(String), US20120208555A1(String), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.775 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), CN102647504A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), CN102647504B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), EP2490104A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), EP2490104B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.891 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.891 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.915 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.916 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), KR101892065B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.925 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.925 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.925 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 225(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), KR1020120094447A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.954 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.955 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.956 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 30328(Integer), 70098(Integer), 143680(Integer), 184895(Integer), 184896(Integer), 184897(Integer), 184898(Integer), 184899(Integer), 184900(Integer), 184901(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.976 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 22 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.977 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.977 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75786(Integer), 25155(Integer), 75787(Integer), 6645(Integer), 53331(Integer), 10991(Integer), 8356(Integer), 11751(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), US20120208555A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:12.997 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.004 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.004 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 30328(Integer), 70098(Integer), 143680(Integer), 184895(Integer), 184896(Integer), 184897(Integer), 184898(Integer), 184899(Integer), 184900(Integer), 184901(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.011 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.011 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.020 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271678(Integer), US8914010B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.037 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 1030 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.055 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.056 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8914010B2(String), US8914010B2(String), 1418659200(Integer), 271678(Integer), 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.091 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.092 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.137 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.162 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.163 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.163 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 61611(Integer), 57511(Integer), 193396(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.170 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.171 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186008(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.183 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.189 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.190 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 30328(Integer), 70098(Integer), 143680(Integer), 184895(Integer), 184896(Integer), 184897(Integer), 184898(Integer), 184899(Integer), 184900(Integer), 184901(Integer), 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186008(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.209 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.210 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.211 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 30328(Integer), 70098(Integer), 143680(Integer), 184895(Integer), 184896(Integer), 184897(Integer), 184898(Integer), 184899(Integer), 184900(Integer), 184901(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.230 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 11 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.238 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.239 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.243 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.243 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 30328(Integer), 70098(Integer), 143680(Integer), 184895(Integer), 184896(Integer), 184897(Integer), 184898(Integer), 184899(Integer), 184900(Integer), 184901(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.266 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.267 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.267 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 2240(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186008(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.286 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.294 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.294 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 1323(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.306 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 186008(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.313 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.315 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.316 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 64465(Integer), 271009(Integer), 215729(Integer), 270613(Integer), 270614(Integer), 270615(Integer), null, 270616(Integer), 270617(Integer), 270618(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.335 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.336 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.336 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 64466(Integer), null, null, null, null, null, null, null, null, null [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.341 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.355 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.356 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.356 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 64467(Integer), null, null, null, null, null, null, null, null, null [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.375 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.376 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.376 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.376 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.396 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.397 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.398 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 30328(Integer), 70098(Integer), 143680(Integer), 184895(Integer), 184896(Integer), 184897(Integer), 184898(Integer), 184899(Integer), 184900(Integer), 184901(Integer), 225(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.417 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.418 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.418 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 4694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.437 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.446 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Preparing: SELECT id,name AS text,cid AS fieldId FROM os_patent_field_text WHERE (cid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.446 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Parameters: 4694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.465 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.466 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.466 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.485 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.509 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid IN (?)) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.510 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4694(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.529 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.663 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186008(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.697 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.698 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:13.699 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120323902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and file browsing method implemented by mobile terminal(String), 移动终端及移动终端实现的文件浏览方法(String), US20120323902A1(String), A mobile terminal and a file browsing method implemented by the mobile terminal are disclosed, including: a scanning module scans the files in the mobile terminal and acquires related information of each file in the mobile terminal; an indexing module creates a global index list according to the related information of the files; and a browsing module classifies and displays the files according to the file types in the global index list while searching a target file. According to the technical solution, the target file can be quickly and conveniently found from the mobile terminal.(String), 本发明公开了一种移动终端及其实现的文件浏览方法,包括:扫描模块对移动终端中的文件进行扫描,获取移动终端中各个文件的相关信息。 索引模块根据文件的相关信息创建全局索引列表; 浏览模块在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 根据本发明的技术方案,可以在移动终端上快速、方便地找到目标文件。(String), US13/581140(String), 1289923200(Integer), US20120323902A1(String), 1355932800(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 1(Integer), US20090106200A1(String), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186009(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\c67067092b014cee85a2b857602febe0.png(String), 186009(Integer), c67067092b014cee85a2b857602febe0.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.274 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and file browsing method implemented by mobile terminal(String), 移动终端及移动终端实现的文件浏览方法(String), US20120323902A1(String), A mobile terminal and a file browsing method implemented by the mobile terminal are disclosed, including: a scanning module scans the files in the mobile terminal and acquires related information of each file in the mobile terminal; an indexing module creates a global index list according to the related information of the files; and a browsing module classifies and displays the files according to the file types in the global index list while searching a target file. According to the technical solution, the target file can be quickly and conveniently found from the mobile terminal.(String), 本发明公开了一种移动终端及其实现的文件浏览方法,包括:扫描模块对移动终端中的文件进行扫描,获取移动终端中各个文件的相关信息。 索引模块根据文件的相关信息创建全局索引列表; 浏览模块在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 根据本发明的技术方案,可以在移动终端上快速、方便地找到目标文件。(String), US13/581140(String), 1289923200(Integer), US20120323902A1(String), 1355932800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 1(Integer), US20090106200A1(String), \20230420\c67067092b014cee85a2b857602febe0.png(String), 10(Integer), 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 1. A mobile terminal, comprising a scanning module, an indexing module and a browsing module; wherein,the scanning module is configured to scan files in the mobile terminal and acquire related information of each file in the mobile terminal;the indexing module is configured to create a global index list according to the related information of the each file; andthe browsing module is configured to classify and display the files according to file types in the global index list while searching a target file.(String), 1.移动终端,包括扫描模块、索引模块和浏览模块;其中,扫描模块,用于扫描移动终端中的文件,获取移动终端中每个文件的相关信息;索引模块,用于根据每个文件的相关信息创建全局索引列表;和浏览模块用于在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 2. The mobile terminal according to claim 1, wherein,the browsing module is further configured to trigger the indexing module to update the global index list during manual update of the global index list.(String), 2.根据权利要求1所述的移动终端,其中,浏览模块还用于在手动更新全局索引列表时触发索引模块更新全局索引列表。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.344 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 3. The mobile terminal according to claim 1, further comprising: a file reading and writing module, and a searching module; wherein,the file reading and writing module is configured to, after file creation or deletion, create and delete an index item in the global index list through invoking an interface provided by the indexing module;the searching module is configured to search the target file in the global index list according to an input keyword of the target file; andthe browsing module is further configured to display the target file searched out.(String), 3.根据权利要求1所述的移动终端,还包括:文件读写模块和搜索模块;其中,文件读写模块用于在文件创建或删除后,通过调用索引模块提供的接口在全局索引列表中创建和删除索引项。查找模块,用于根据输入的目标文件关键字在全局索引列表中查找目标文件;和浏览模块还用于显示搜索到的目标文件。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 4. A file browsing method, comprising:scanning files in a mobile terminal and acquiring related information of each file in the mobile terminal; creating a global index list according to the acquired related information of the each file;classifying and displaying the files according to file types in the global index list while searching a target file.(String), 4.一种文件浏览方法,包括:扫描移动终端中的文件,获取移动终端中每个文件的相关信息;根据获取的每个文件的相关信息创建全局索引列表;在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 5. The method according to claim 4, wherein the acquiring related information of each file in the mobile terminal comprises:scanning every file node through a read-write interface provided by a file system, acquiring file names and file paths of all the files in a storage medium of the mobile terminal, obtaining extension names of the files based on the file names, and sending the file names, file paths and extension names of the files to an indexing module of the mobile terminal by a scanning module of the mobile terminal.(String), 5.根据权利要求4所述的方法,其中获取移动终端中每个文件的相关信息包括:通过文件系统提供的读写接口扫描每个文件节点,获取移动终端存储介质中所有文件的文件名和文件路径,根据文件名获取文件的扩展名,发送移动终端的扫描模块将文件的文件名、文件路径和扩展名传给移动终端的索引模块。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 6. The method according to claim 4, wherein the creating a global index list according to the acquired related information of the each file comprises:creating one index item for the each file by an indexing module of the mobile terminal according to the related information of the each file which is received by the index module;wherein index items of all the files constitute the global index list; each index item in the global index list includes a file name, a file path, an extension name, a file type and a file subtype of each file.(String), 6.根据权利要求4所述的方法,其中根据获取的每个文件的相关信息创建全局索引列表包括:移动终端的索引模块根据索引模块接收到的每个文件的相关信息,为每个文件创建一个索引项;其中,所有文件的索引项构成全局索引列表;全局索引列表中的每个索引项包括每个文件的文件名、文件路径、扩展名、文件类型和文件子类型。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 7. The method according to claim 6, further comprising:periodically updating the global index list by the indexing module; or after a new storage card is inserted into the mobile terminal, automatically updating the global index list by the indexing module; or after file creation or deletion, creating and deleting the index items in the global index list by a file reading and writing module of the mobile terminal through invoking an interface provided by the indexing module; or during manual update of the global index list, triggering the indexing module to update the global index list by a browsing module of the mobile terminal.(String), 7.根据权利要求6所述的方法,还包括:索引模块周期性更新全局索引列表;或者移动终端插入新的存储卡后,索引模块自动更新全局索引列表;或者,在文件创建或删除后,移动终端的文件读写模块通过调用索引模块提供的接口,在全局索引列表中创建和删除索引项。或者,在手动更新全局索引列表时,通过移动终端的浏览模块触发索引模块更新全局索引列表。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 8. The method according to claim 6, wherein the classifying and displaying the files according to file types in the global index list comprises:reading the global index list via an interface of the indexing module of the mobile terminal, classifying and displaying the files according to the file types and file sub-types of the files in the global index list by a browsing module of the mobile terminal.(String), 8.根据权利要求6所述的方法,其中将全局索引列表中的文件按文件类型分类显示包括:通过移动终端的索引模块的接口读取全局索引列表,移动终端的浏览模块根据全局索引列表中文件的文件类型和文件子类型对文件进行分类显示。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 9. The method according to claim 8, further comprising:selecting a file type of the target file from the file types displayed by the browsing module; displaying one or a plurality of file subtypes of this file type, selecting one file subtype from the plurality of file subtypes, displaying all files under this file subtype and selecting the target file from the all files under this file subtype by the browsing module.(String), 9.根据权利要求8所述的方法,还包括:从浏览模块显示的文件类型中选择目标文件的文件类型;浏览模块显示该文件类型的一个或多个文件子类型,从多个文件子类型中选择一个文件子类型,显示该文件子类型下的所有文件,并从该文件子类型下的所有文件中选择目标文件。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.346 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186009(Integer), 10. The method according to claim 9, further comprising:inputting a keyword of the target file;searching the target file in the global index list by a searching module of the mobile terminal according to the keyword, and displaying the found target file by the searching module.(String), 10.根据权利要求9所述的方法,还包括:输入目标文件的关键字;通过移动终端的搜索模块根据关键字在全局索引列表中搜索目标文件,并通过搜索模块显示搜索到的目标文件。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.563 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186009(Integer), TECHNICAL FIELD [0001]The present disclosure relates to the file browsing field of mobile terminals, particularly to a mobile terminal and a file browsing method implemented by the mobile terminal. BACKGROUND [0002]With the rapid development of mobile terminal technology, people make higher demands on both the function and convenience of mobile terminals. In the related art, the functions of mobile terminals are getting richer and the files used in mobile terminals keep increasing, including: text files such as short messages and e-books; hyper text files such as multimedia messages and mails; audio files; image files; video files; flash files; executable programs, and etc. Moreover, the storage space of mobile terminals, particularly intelligent mobile terminals, is increasing. Built-in flash, external flash storage cards and micro hard disks all become the storage media of mobile terminals. Consequently, the total storage capacity of a mobile terminal can be tens of Gigabytes (GB). [0003]In a mobile terminal, conventional file storage is organized in the form of directory tree, and different files are stored in different directories of different storage media. The thinking habit of a user who wants to browse files is that when he/she wants to browse an image, a video or a mail, firstly he/she thinks of the type of a target file. [0004]However, the form of the directory tree in the related art does not accord with user's thinking habit. When files are organized in the form of directory tree, a user can not find a target file unless he/she knows both the name and directory of the target file. Moreover, when a directory tree is adopted, a link is not established between a file type and a file position, and thus no prompt about the position of the target file is provided. Further, a mobile terminal has numerous storage media and directories, therefore it is unlikely for a user to quickly find a target file when browsing a target file, because he/she can not remember the storage path of the target file. [0005]Furthermore, mobile terminals have smaller screens and keyboards than computers do, the content displayed on a screen of a mobile terminal is limited, and it is rather inconvenient to perform scrolling, page turning and other operations, thereby increasing the difficulty of a user when he/she searches a target file from enormous files. SUMMARY [0006]In view of the above facts, the main object of the present disclosure is to provide a mobile terminal and a file browsing method implemented by the mobile terminal, which can conveniently and quickly find a target file in the mobile terminal. [0007]To achieve the foregoing object, the technical solution of the present disclosure is realized in the following way. [0008]The present disclosure provides a mobile terminal, including: a scanning module, an indexing module and a browsing module, wherein,[0009]the scanning module is configured to scan files in the mobile terminal and acquire related information of each file in the mobile terminal; [0010]the indexing module is configured to create a global index list according to the related information of the each file; and[0011]the browsing module is configured to classify and display the files according to file types in the global index list while searching a target file. [0012]In the foregoing mobile terminal,[0013]the browsing module may be further configured to trigger the indexing module to update the global index list during manual update of the global index list. [0014]The foregoing mobile terminal may further include: a file reading and writing module, and a searching module, wherein,[0015]the file reading and writing module is configured to, after file creation or deletion, create and delete an index item in the global index list through invoking an interface provided by the indexing module; [0016]the searching module is configured to search the target file in the global index list according to an input keyword of the target file; and[0017]the browsing module is further configured to display the target file searched out.[0018]The present disclosure provides a file browsing method, including:[0019]scanning files in a mobile terminal and acquiring related information of each file in the mobile terminal; creating a global index list according to the acquired related information of the each file; [0020]classifying and displaying the files according to file types in the global index list while searching a target file. [0021]In the foregoing method, the acquiring related information of each file in the mobile terminal may include: [0022]scanning every file node through a read-write interface provided by a file system, acquiring file names and file paths of all the files in a storage medium of the mobile terminal, obtaining extension names of the files based on the file names, and sending the file names, file paths and extension names of the files to an indexing module of the mobile terminal by a scanning module of the mobile terminal. [0023]In the foregoing method, the creating a global index list according to the acquired related information of the each file may include: [0024]creating one index item for the each file by an indexing module of the mobile terminal according to the related information of the each file which is received by the index module; [0025]wherein index items of all the files constitute the global index list; each index item in the global index list includes a file name, a file path, an extension name, a file type and a file subtype of each file. [0026]The foregoing method may further include: [0027]periodically updating the global index list by the indexing module; or after a new storage card is inserted into the mobile terminal, automatically updating the global index list by the indexing module; or after file creation or deletion, creating and deleting the index items in the global index list by a file reading and writing module of the mobile terminal through invoking an interface provided by the indexing module; or during manual update of the global index list, triggering the indexing module to update the global index list by a browsing module of the mobile terminal. [0028]In the foregoing method, the classifying and displaying the files according to file types in the global index list may include: [0029]reading the global index list via an interface of the indexing module of the mobile terminal, classifying and displaying the files according to the file types and file sub-types of the files in the global index list by a browsing module of the mobile terminal. [0030]The foregoing method may further include: [0031]selecting a file type of the target file from the file types displayed by the browsing module; displaying one or a plurality of file subtypes of this file type, selecting one file subtype from the plurality of file subtypes, displaying all files under this file subtype and selecting the target file from the all files under this file subtype by the browsing module. [0032]The foregoing method may further include: [0033]inputting a keyword of the target file; [0034]searching the target file in the global index list by a searching module of the mobile terminal according to the keyword, and displaying the found target file by the searching module. [0035]In the mobile terminal provided by the present disclosure and the file browsing method implemented by the mobile terminal, after the scanning module scans the files in the mobile terminal, the indexing module creates a global index list according to a scanning result. When a target file is found, the browsing module classifies and displays the files so that all video files in the mobile terminal are displayed under a video directory, and all audio files are displayed under an audio directory. The method by which enormous files in the mobile terminal are managed based on file types is more accordant with users' habits, so it increases the speed of searching a target file and can conveniently and quickly find the target file from the enormous files of the mobile terminal. The present disclosure is featured by simple operation, is particularly applicable to the mobile terminals with a small screen and a small keyboard, even without a keyboard, and significantly improves user experience and has a great market promotion value and a practical value. BRIEF DESCRIPTION OF THE DRAWINGS [0036]FIG. 1 is a structural schematic diagram of composition of a mobile terminal provided by the present disclosure; and [0037]FIG. 2 is a flow schematic diagram of realization of a file browsing method provided by the present disclosure. DETAILED DESCRIPTION [0038]The basic idea of the present disclosure is: a scanning module scans files in a mobile terminal and acquires related information of each file in the mobile terminal; an indexing module creates a global index list according to the related information of the each file; a browsing module classifies and displays the files according to file types in the global index list while searching a target file.. [0039]The present disclosure will now be described with reference to the accompanying drawings and embodiments. [0040]FIG. 1 is a structural schematic diagram of composition of a mobile terminal provided by the present disclosure. As shown in FIG. 1, the mobile terminal comprises: a scanning module 11, an indexing module 12 and a browsing module 13; wherein, the scanning module 11 is configured to scan files in the mobile terminal and acquire related information of each file in the mobile terminal; [0041]the indexing module 12 is configured to create a global index list according to the related information of the each file; [0042]the browsing module 13 is configured to classify and display the files according to file types in the global index list while searching a target file. [0043]The browsing module 13 is further configured to trigger the indexing module 12 to update the global index list during manual update of the global index list. [0044]The mobile terminal further comprises: a file reading and writing module 14 and a searching module 15; wherein, [0045]the file reading and writing module 14 is configured to, after file creation or deletion, create and delete an index item in the global index list through invoking a CreatFileIndexItem interface and a DelFileIndexItem interface provided by the indexing module; [0046]the searching module 15 is configured to search the target file in the global index list according to an input keyword of the target file. [0047]The browsing module 13 is further configured to display the target file searched out. [0048]That the scanning module 11 acquires the related information of the each file in the mobile terminal refers to that: the scanning module 11 scans each file through a read-write interface provided by an existing file system in the mobile terminal, acquires file names and file paths of all the files in a storage medium of the mobile terminal, obtains extension names of the files based on the file names, and sends the file names, file paths and extension names of the files to the indexing module 12 of the mobile terminal. [0049]That the indexing module 12 creates a global index list according to the acquired related information of the each file refers to that: the indexing module 12 creates one index item for each file according to received related information of the each file. The index items of all the files constitute the global index list. Each index item in the global index list includes the file name, file path, an extension name, file type and file sub-type of each file. [0050]That the browsing module 13 classifies and displays the files according to file types in the global index list refers to that: the browsing module 13 reads the global index list via the GetFileIndexItem interface provided by the indexing module 12, organizes the files according to the file types and file sub-types of the files in the global index list, and classifies and displays the files. [0051]Based on the mobile terminal shown in FIG. 1, the present disclosure also provides a file browsing method for the mobile terminal. FIG. 2 is a flow schematic diagram of realization of the file browsing method provided by the present disclosure. As shown in FIG. 2, the method includes the following steps: [0052]Step 201, scanning files in the mobile terminal and acquiring related information of each file in the mobile terminal; [0053]specifically, the files in the mobile terminal are organized by an existing file system and stored in a storage medium in the mobile terminal. The file system contains a plurality of file nodes. Each file node corresponds to one file. A file node stores the file name, file path, file attribute and other related information of a file. All the file nodes are organized into a tree structure. The scanning module of the mobile terminal scans every file node through a read-write interface provided by the file system, and acquires the file names, file paths and other related information of all the files in the storage medium of the mobile terminal. A file name is a string. The part behind “.” of a string is the extension name of the string. The scanning module obtains the extension name of a file from a file name. [0054]Whenever the scanning module acquires related information of a file, it sends the related information to the indexing module via the CreatFileIndexItem interface provided by the indexing module of the mobile terminal. The related information includes the file name, file path and extension name of the file. [0055]Step 202, creating a global index list according to the acquired related information of the each file. [0056]Specifically, the indexing module of the mobile terminal creates an index item for every file according to the received related information of the each file. The index items of all the files constitute the global index list. Each index item in the global index list includes the file name, file path, extension name, file type, file sub-type and other fields of the file. The file type and file sub-type are set by the indexing module according to the extension name or file path of the file during the creation of an index item. Each index item corresponds to one file type and one file sub-type. The rule for correspondence between files and file types and that between files and file sub-types can be set through the SetFileTypeRule interface and SetFileSub-typeRule interface of the indexing module, separately. The correspondence rule may be that a specific extension name corresponds to a specific file type, or a specific file path corresponds to a specific file type. The file type may be audio, video, image, or text, etc.. The file sub-types are the further division of a file type, the specific division rule of which can be set through the SetFileSub-typeRule interface of the indexing module; for example, the file sub-type of audio can be mp3, wma or ogg, etc., and alternatively, file sub-types of audio can be classified by music styles, and etc. [0057]Wherein, when the indexing module sets a file type and a file sub-type in an index item, firstly it searches a file type corresponding to a file from among the existing file types according to the rule for correspondence between files and file types; when the file type is found, it sets the file type of the file to which the index item corresponds as the found file type. Then it searches a file sub-type corresponding to the file from among the existing file sub-types according to the rule for correspondence between files and file sub-types; when the file sub-type is found, it sets the file sub-type of the file to which the index item corresponds as the found file sub-type. If the corresponding file type is not found, it creates a new file type and set the file type of the file to which the index item corresponds as “Others” type; for example, the file type to which a file with an extension name of mp3 corresponds is audio, and the file type to which a file with an extension name of jpeg corresponds is image. [0058]The indexing module can also automatically update the global index list, periodically. The period can be determined based on a file increase/decrease frequency, which can be set as one day, one week or other time. When the indexing module automatically updates the global index list, it can trigger the scanning module to scan all the files in the storage of the mobile terminal. The update strategy may be that the indexing module deletes the existing global index list before update, and then re-creates a global index list according to the related information of the files sent by the scanning module, or the scanning module reads related information of a file from file nodes, and searches the file to which the related information corresponds in the global index list according to the related information of the file; If the file can be found, it means the file exists already; otherwise, the scanning module needs to send the related information of the file to the indexing module, then the indexing module creates a new index item in the global index list. [0059]Furthermore, when a new storage card is inserted into the mobile terminal, the indexing module can also automatically update the global index list. After file creation or deletion, the file reading and writing module of the mobile terminal can create and delete the index items in the global index list through invoking the CreatFileIndexItem interface and DelFileIndexItem interface provided by the indexing module. The modules in the mobile terminal may invoke the interfaces of the indexing module by function invocation or through a command. When the global index list is manually updated, the browsing module triggers the indexing module to update the global index list. [0060]Step 203, classifying and displaying the files according to the file types in the global index list while searching a target file. [0061]Specifically, during search of a target file, the browsing module of the mobile terminal is triggered by a key of the mobile terminal. The triggered browsing module reads the global index list through the GetFileIndexItem interface of the indexing module. According to the file types and file sub-types of the files in the global index list, the browsing module classifies and displays the files. For example, audio files, video files, text files and image files are displayed by the browsing module. [0062]The type of the target file is selected from the file types displayed by the browsing module. The browsing module displays one or a plurality of file sub-types under this file type and then selects one file sub-type from the plurality of file sub-types. The browsing module displays all the files under this file sub-type and selects the target file from them. For example, an image is needed to be inserted during edition of a multimedia message, the browsing module is triggered, and displays all image files stored in the mobile terminal; if there are many files under a file type or a file sub-type, the searching module of the mobile terminal may be triggered in order to find the target file faster. The keyword of the target file is input to the searching module, and the searching module searches the target file from among the files under this file type or file sub-type in the global index list; and then the target file is displayed through the browsing module. [0063]The foregoing descriptions are preferred embodiments of the present disclosure and are not intended to limit the present disclosure. All modifications, equivalent substitutes and improvements made without departing from the spirit and principle of the present disclosure shall be within the protection scope of the present disclosure.(String), 技术领域 [0001] 本发明涉及移动终端的文件浏览领域,尤其涉及一种移动终端及其实现的文件浏览方法。 背景 [0002] 随着移动终端技术的飞速发展,人们对移动终端的功能和便利性提出了更高的要求。 相关技术中,移动终端的功能越来越丰富,移动终端使用的文件也在不断增加,包括:短信、电子书等文本文件; 彩信、邮件等超文本文件; 音频文件; 图像文件; 视频文件; 闪存文件; 可执行程序等。而且,移动终端,特别是智能移动终端的存储空间越来越大。 内置闪存、外置闪存卡和微型硬盘都成为移动终端的存储介质。 因此,移动终端的总存储容量可以达到数十千兆字节(GB)。 [0003] 在移动终端中,传统的文件存储是以目录树的形式组织的,不同的文件存储在不同存储介质的不同目录下。 想要浏览文件的用户的思维习惯是,当他/她想要浏览图片、视频或邮件时,他/她首先想到的是目标文件的类型。 [0004] 然而,相关技术中目录树的形式并不符合用户的思维习惯。 当文件以目录树的形式组织时,用户除非知道目标文件的名称和目录,否则无法找到目标文件。 而且,当采用目录树时,文件类型和文件位置之间没有建立联系,因此不提示目标文件的位置。 进一步地,移动终端的存储介质和目录众多,用户在浏览目标文件时不太可能快速找到目标文件,因为他/她记不住目标文件的存储路径。 [0005] 此外,移动终端的屏幕和键盘都比电脑小,移动终端屏幕显示的内容有限,进行滚动、翻页等操作较为不便,增加了用户使用时的难度。 /she 从大量文件中搜索目标文件。 概括 [0006] 鉴于上述情况,本发明的主要目的在于提供一种移动终端及其实现的文件浏览方法,能够方便快捷地在移动终端中找到目标文件。 [0007] 为实现上述目的,本发明的技术方案是通过以下方式实现的。 [0008] 本发明提供了一种移动终端,包括:扫描模块、索引模块和浏览模块,其中, [0009]扫描模块,用于扫描移动终端中的文件,获取移动终端中每个文件的相关信息; [0010] 索引模块,用于根据每个文件的相关信息创建全局索引列表; 和 [0011] 浏览模块,用于在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0012] 在上述移动终端中, [0013] 浏览模块还可以用于在手动更新全局索引列表时触发索引模块更新全局索引列表。 [0014] 上述移动终端还可以包括:文件读写模块和搜索模块,其中, [0015] 文件读写模块用于在文件创建或删除后,通过调用索引模块提供的接口在全局索引列表中创建和删除索引项。 [0016] 查找模块,用于根据输入的目标文件关键字在全局索引列表中查找目标文件; 和 [0017] 浏览模块还用于显示搜索到的目标文件。[0018] 本发明提供一种文件浏览方法,包括:[0019] 扫描移动终端中的文件,获取移动终端中每个文件的相关信息; 根据获取的每个文件的相关信息创建全局索引列表; [0020] 在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0021] 上述方法中,获取移动终端中各文件的相关信息可以包括: [0022] 通过文件系统提供的读写接口扫描每个文件节点,获取移动终端存储介质中所有文件的文件名和文件路径,根据文件名获取文件的扩展名,发送 移动终端的扫描模块将文件的文件名、文件路径和扩展名传给移动终端的索引模块。 [0023]上述方法中,根据获取的每个文件的相关信息创建全局索引列表可以包括: [0024] 移动终端的索引模块根据索引模块接收到的每个文件的相关信息,为每个文件创建一个索引项; [0025] 其中,所有文件的索引项构成全局索引列表; 全局索引列表中的每个索引项包括每个文件的文件名、文件路径、扩展名、文件类型和文件子类型。 [0026] 上述方法还可以包括: [0027] 索引模块周期性更新全局索引列表; 或者移动终端插入新的存储卡后,索引模块自动更新全局索引列表; 或者,在文件创建或删除后,移动终端的文件读写模块通过调用索引模块提供的接口,在全局索引列表中创建和删除索引项。 或者,在手动更新全局索引列表时,通过移动终端的浏览模块触发索引模块更新全局索引列表。 [0028] 上述方法中,所述根据文件类型对全局索引列表中的文件进行分类展示可以包括: [0029] 通过移动终端的索引模块的接口读取全局索引列表,移动终端的浏览模块根据全局索引列表中文件的文件类型和文件子类型对文件进行分类显示。 [0030] 上述方法还可以包括: [0031] 从浏览模块显示的文件类型中选择目标文件的文件类型; 浏览模块显示该文件类型的一个或多个文件子类型,从多个文件子类型中选择一个文件子类型,显示该文件子类型下的所有文件,并从该文件子类型下的所有文件中选择目标文件。 [0032] 上述方法还可以包括: [0033] 输入目标文件的关键字; [0034] 通过移动终端的搜索模块根据关键字在全局索引列表中搜索目标文件,并通过搜索模块显示搜索到的目标文件。 [0035] 本发明提供的移动终端及其实现的文件浏览方法中,扫描模块扫描移动终端中的文件后,索引模块根据扫描结果创建全局索引列表。 当找到目标文件时,浏览模块将文件分类显示,使得移动终端中的所有视频文件显示在video目录下,所有音频文件显示在audio目录下。 这种基于文件类型管理移动端海量文件的方式更符合用户的使用习惯,提高了查找目标文件的速度,可以方便快捷地从手机海量文件中找到目标文件。 终端。 本发明操作简单,特别适用于小屏幕、小键盘甚至无键盘的移动终端,显着提高了用户体验,具有很大的市场推广价值和实用价值。 附图的简要说明 [0036] 图1为本发明提供的移动终端的组成结构示意图; 和 [0037] 图2为本发明提供的文件浏览方法的实现流程示意图。 详细说明 [0038] 本发明的基本思想是:扫描模块扫描移动终端中的文件,获取移动终端中每个文件的相关信息; 索引模块根据每个文件的相关信息创建全局索引列表; 浏览模块在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0039] 现在将参考附图和实施例描述本公开。 [0040] 图1为本发明提供的移动终端的组成结构示意图。 如图1所示,该移动终端包括:扫描模块 11 , 索引模块 12 和一个浏览模块 13 ; 其中,扫描模块 11 用于扫描移动终端中的文件,获取移动终端中每个文件的相关信息; [0041] 索引模块 12 用于根据每个文件的相关信息创建全局索引列表; [0042] 浏览模块 13 用于在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0043] 浏览模块 13 进一步配置为触发索引模块 12 在手动更新全局索引列表期间更新全局索引列表。 [0044] 移动终端还包括:文件读写模块 14 和一个搜索模块 15 ; 其中, [0045] 文件读写模块 14 用于在创建或删除文件后,通过调用索引模块提供的CreatFileIndexItem接口和DelFileIndexItem接口在全局索引列表中创建和删除索引项; [0046] 搜索模块 15 用于根据输入的目标文件关键字在全局索引列表中查找目标文件。 [0047] 浏览模块 13 还用于显示搜索到的目标文件。 [0048] 即扫描模块 11 获取移动端各个文件的相关信息是指:扫描模块 11 通过移动终端中现有文件系统提供的读写接口扫描每个文件,获取移动终端存储介质中所有文件的文件名和文件路径,根据文件名获取文件的扩展名 ,并将文件的文件名、文件路径和扩展名发送给索引模块 12 的移动终端。 [0049] 索引模块 12 根据获取的各个文件的相关信息创建全局索引列表指的是:索引模块 12 根据接收到的每个文件的相关信息,为每个文件创建一个索引项。 所有文件的索引项构成全局索引列表。 全局索引列表中的每个索引项包括每个文件的文件名、文件路径、扩展名、文件类型和文件子类型。 [0050] 即浏览模块 13 全局索引列表中按文件类型分类显示文件指的是:浏览模块 13 通过索引模块提供的GetFileIndexItem接口读取全局索引列表 12 , 根据全局索引列表中文件的文件类型和文件子类型对文件进行整理,并对文件进行分类展示。 [0051] 基于图1所示的移动终端,本发明还提供了一种移动终端的文件浏览方法。 图2为本发明提供的文件浏览方法的实现流程示意图。 如图2所示,该方法包括以下步骤: [0052] 步 201 、扫描移动终端中的文件,获取移动终端中每个文件的相关信息; [0053]具体地,移动终端中的文件由现有的文件系统组织,存储在移动终端中的存储介质中。 文件系统包含多个文件节点。 每个文件节点对应一个文件。 文件节点存储文件的文件名、文件路径、文件属性等相关信息。 所有的文件节点都被组织成一个树结构。 移动终端的扫描模块通过文件系统提供的读写接口扫描每个文件节点,获取移动终端存储介质中所有文件的文件名、文件路径等相关信息。 文件名是一个字符串。 “.”后面的部分 字符串的扩展名是字符串的扩展名。 扫描模块从文件名中获取文件的扩展名。 [0054] 每当扫描模块获取到文件的相关信息时,通过移动终端索引模块提供的CreatFileIndexItem接口将相关信息发送给索引模块。 相关信息包括文件的文件名、文件路径和扩展名。 [0055] 步 202 ,根据获取的每个文件的相关信息创建全局索引列表。 [0056] 具体地,移动终端的索引模块根据接收到的每个文件的相关信息,为每个文件创建一个索引项。 所有文件的索引项构成全局索引列表。 全局索引列表中的每个索引项包括文件的文件名、文件路径、扩展名、文件类型、文件子类型等字段。 文件类型和文件子类型由索引模块在创建索引项时根据文件的扩展名或文件路径设置。 每个索引项对应一种文件类型和一种文件子类型。 文件与文件类型、文件与文件子类型的对应规则可以分别通过索引模块的SetFileTypeRule接口和SetFileSub-typeRule接口设置。 对应规则可以是特定的扩展名对应特定的文件类型,或者特定的文件路径对应特定的文件类型。 文件类型可以是音频、视频、图片、文本等。文件子类型是文件类型的进一步划分,具体划分规则可以通过索引模块的SetFileSub-typeRule接口设置 ; 例如,音频的文件子类型可以是mp3、wma或ogg等,或者,音频的文件子类型可以按音乐风格等进行分类。 [0057] 其中,索引模块在索引项中设置文件类型和文件子类型时,首先根据文件与文件类型的对应关系规则,从现有的文件类型中查找文件对应的文件类型。 当找到文件类型时,将索引项对应的文件的文件类型设置为找到的文件类型。 然后根据文件与文件子类型的对应关系规则,从现有的文件子类型中查找该文件对应的文件子类型; 当找到文件子类型时,将索引项对应的文件的文件子类型设置为找到的文件子类型。 如果没有找到对应的文件类型,则新建一个文件类型,并将索引项对应的文件的文件类型设置为“Others”类型; 例如,扩展名为mp3的文件对应的文件类型为audio,扩展名为jpeg的文件对应的文件类型为image。 [0058]索引模块还可以定期自动更新全局索引列表。 周期可以根据文件增减频率来确定,可以设置为一天、一周或其他时间。 当索引模块自动更新全局索引列表时,可以触发扫描模块扫描移动终端存储中的所有文件。 更新策略可以是索引模块在更新前删除已有的全局索引列表,然后根据扫描模块发送的文件的相关信息重新创建全局索引列表,或者扫描模块读取一个文件的相关信息 从文件节点中查找文件,根据文件的相关信息在全局索引列表中查找相关信息对应的文件; 如果能找到该文件,说明该文件已经存在; 否则,扫描模块需要将文件的相关信息发送给索引模块,然后索引模块在全局索引列表中创建新的索引项。 [0059] 此外,当移动终端插入新的存储卡时,索引模块还可以自动更新全局索引列表。 在文件创建或删除后,移动终端的文件读写模块可以通过调用索引模块提供的CreatFileIndexItem接口和DelFileIndexItem接口在全局索引列表中创建和删除索引项。 移动终端中的模块可以通过函数调用或命令调用索引模块的接口。 当手动更新全局索引列表时,浏览模块触发索引模块更新全局索引列表。 [0060] 步 203 ,在搜索目标文件时,根据全局索引列表中的文件类型对文件进行分类显示。 [0061] 具体地,在搜索目标文件时,移动终端的浏览模块由移动终端的按键触发。 触发浏览模块通过索引模块的GetFileIndexItem接口读取全局索引列表。 浏览模块根据全局索引列表中文件的文件类型和文件子类型,对文件进行分类显示。 例如,浏览模块显示音频文件、视频文件、文本文件和图像文件。 [0062] 目标文件的类型是从浏览模块显示的文件类型中选择的。 浏览模块显示该文件类型下的一个或多个文件子类型,然后从多个文件子类型中选择一个文件子类型。 浏览模块显示该文件子类型下的所有文件,并从中选择目标文件。 例如,编辑彩信时需要插入图片,触发浏览模块,显示移动终端中存储的所有图片文件; 如果一种文件类型或文件子类型下的文件较多,则可以触发移动终端的搜索模块,以便更快地找到目标文件。 将目标文件的关键字输入查找模块,查找模块从全局索引列表中该文件类型或文件子类型下的文件中查找目标文件; 然后通过浏览模块显示目标文件。 [0063] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 凡在本发明的精神和原则的范围内,所做的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101916164A(String), EP2527965A1(String), EP2527965A4(String), US20120323902A1(String), WO2012019390A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101916164A(String), EP2527965A1(String), EP2527965A4(String), US20120323902A1(String), WO2012019390A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120323902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.809 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.810 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101916164A(String), EP2527965A1(String), EP2527965A4(String), US20120323902A1(String), WO2012019390A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271679(Integer), CN101916164A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271679(Integer), EP2527965A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.896 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271679(Integer), EP2527965A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271679(Integer), US20120323902A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.965 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:14.966 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271679(Integer), WO2012019390A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120323902A1(String), US20120323902A1(String), 1355932800(Integer), 271679(Integer), 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.036 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.036 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.036 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186009(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186009(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.222 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186009(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 186009(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.394 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.411 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.412 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.566 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186009(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20130132567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, method and system for shielding mobile terminal from accessing wireless network information(String), 移动终端、屏蔽移动终端访问无线网络信息的方法及系统(String), US20130132567A1(String), The present invention relates to the technical field of information processing and provides a method for shielding a mobile terminal from accessing wireless network information, which is applied to ensure the mobile terminal to shield the information in a wireless network. The method comprises the steps of: receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command; querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; and generating a prompt according to the evaluation of the domain name. The present invention also provides a mobile terminal capable of shielding the information in the wireless network. The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information.(String), 本发明涉及信息处理技术领域,提供了一种屏蔽移动终端访问无线网络信息的方法,用于保证移动终端屏蔽无线网络中的信息。 该方法包括:接收访问命令,根据访问命令中的网页地址获取对应的域名。 查询域名的域名评价记录,获取域名评价,其中,域名评价记录包括域名和域名评价; 并根据对域名的评价产生提示。 本发明还提供了一种能够屏蔽无线网络中信息的移动终端。 本发明还提供了一种屏蔽移动终端访问无线网络信息的系统。(String), US13/697296(String), 1287590400(Integer), US20130132567A1(String), 1369238400(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080028100A1 | US20100058446A1 | US20130124304A1 | US7743405B2 | US8713188B2(String), 14(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:15.981 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186010(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.126 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.128 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\7f44d2f098d145c19157cfc126023167.png(String), 186010(Integer), 7f44d2f098d145c19157cfc126023167.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.162 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.163 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.180 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, method and system for shielding mobile terminal from accessing wireless network information(String), 移动终端、屏蔽移动终端访问无线网络信息的方法及系统(String), US20130132567A1(String), The present invention relates to the technical field of information processing and provides a method for shielding a mobile terminal from accessing wireless network information, which is applied to ensure the mobile terminal to shield the information in a wireless network. The method comprises the steps of: receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command; querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; and generating a prompt according to the evaluation of the domain name. The present invention also provides a mobile terminal capable of shielding the information in the wireless network. The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information.(String), 本发明涉及信息处理技术领域,提供了一种屏蔽移动终端访问无线网络信息的方法,用于保证移动终端屏蔽无线网络中的信息。 该方法包括:接收访问命令,根据访问命令中的网页地址获取对应的域名。 查询域名的域名评价记录,获取域名评价,其中,域名评价记录包括域名和域名评价; 并根据对域名的评价产生提示。 本发明还提供了一种能够屏蔽无线网络中信息的移动终端。 本发明还提供了一种屏蔽移动终端访问无线网络信息的系统。(String), US13/697296(String), 1287590400(Integer), US20130132567A1(String), 1369238400(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080028100A1 | US20100058446A1 | US20130124304A1 | US7743405B2 | US8713188B2(String), \20230420\7f44d2f098d145c19157cfc126023167.png(String), 14(Integer), 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.216 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.217 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 1. A method for shielding a mobile terminal from accessing wireless network information, applied for the mobile terminal shielding the information in a wireless network and comprising:receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command;querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; andgenerating a prompt according to the evaluation of the domain name.(String), 1.一种屏蔽移动终端访问无线网络信息的方法,应用于屏蔽无线网络信息的移动终端,以及包括:接收访问命令,根据访问命令中的网页地址获取对应的域名;查询域名的域名评价记录,获取域名的评价,域名评价记录包括域名和域名的评价;和根据域名评价生成提示。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 2. The method for shielding the mobile terminal from accessing the wireless network information according to claim 1, wherein after the step of querying the domain name evaluation record of the domain name is executed, the method further comprises:storing the domain name evaluation record in a cache of the mobile terminal.(String), 2.根据权利要求1所述的屏蔽移动终端访问无线网络信息的方法,其中在执行查询域名的域名评价记录的步骤之后,该方法还包括:将域名评估记录存储在移动终端的缓存中。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.251 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 3. The method for shielding the mobile terminal from accessing the wireless network information according to claim 2, wherein the domain name evaluation record is acquired in a mode that a domain name evaluation server connected with the mobile terminal accesses a website corresponding to the domain name and evaluates.(String), 3.根据权利要求2所述的屏蔽移动终端访问无线网络信息的方法,其中域名评估记录是通过与移动终端连接的域名评估服务器访问该域名对应的网站进行评估的方式获取的。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 4. The method for shielding the mobile terminal from accessing the wireless network information according to claim 1, wherein the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises:querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal;when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; andwhen the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name.(String), 4.根据权利要求1所述的屏蔽移动终端访问无线网络信息的方法,其中查询域名的域名评价记录,获取域名评价的步骤包括:查询移动终端缓存中是否存在该域名的域名评估记录;当缓存中存在域名的域名评估记录时,根据域名评估记录获取域名的评估;和当缓存中不存在该域名的域名评估记录时,从与移动终端连接的域名评估服务器查询该域名的域名评估记录,获取该域名的评估结果。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 5. The mobile terminal, comprising: a domain name resolution unit, a domain name query unit and an access prompting unit, whereinthe domain name resolution unit is configured to receive the access command and acquire the corresponding domain name according to the webpage address in the access command;the domain name query unit is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; andthe access prompting unit is configured to generate a prompt according to the evaluation of the domain name.(String), 5.移动端,包括:域名解析单元、域名查询单元和访问提示单元,其中域名解析单元用于接收访问命令,并根据访问命令中的网页地址获取对应的域名;域名查询单元,用于查询域名的域名评价记录,获取域名的评价;其中,域名评估记录包括域名和对域名的评估;和访问提示单元用于根据对域名的评估产生提示。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 6. The mobile terminal according to claim 5, further comprising:a cache unit, configured to store the domain name evaluation record after the domain name query unit queries the domain name evaluation record of the domain name.(String), 6.根据权利要求5所述的移动终端,还包括:缓存单元,用于在域名查询单元查询到域名的域名评估记录后,存储域名评估记录。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 7. The mobile terminal according to claim 5, wherein the domain name evaluation record is acquired in a mode that the domain name evaluation server connected with the mobile terminal accesses the website corresponding to the domain name and evaluates.(String), 7.根据权利要求5所述的移动终端,其中域名评估记录是通过与移动终端连接的域名评估服务器访问该域名对应的网站进行评估的方式获取的。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 8. The mobile terminal according to claim 5, wherein the domain name query unit comprises: a cache query module and a switching module, whereinthe cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; andthe switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit.(String), 8.根据权利要求5所述的移动终端,其中域名查询单元包括:缓存查询模块和切换模块,其中缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评估记录;和切换模块,用于当缓存单元中存在域名的域名评估记录时,根据域名评估记录获取域名的评估,并从域中查询域名的域名评估记录域名评估服务器与移动终端连接,当缓存单元中不存在该域名的域名评估记录时,获取该域名的评估结果。9、一种屏蔽移动终端访问无线网络信息的系统,包括:移动终端和域名评估服务器,其中域名评估服务器,用于通过访问域名对应的网站获取域名评估记录,评估并存储域名评估记录;其中,域名评估记录包括域名和对域名的评估;和移动终端包括:域名解析单元、域名查询单元和访问提示单元,其中域名解析单元,用于接收访问命令,根据访问命令中的网页地址获取对应的域名;域名查询单元,用于查询域名的域名评价记录,获取域名的评价;和访问提示单元用于根据对域名的评估产生提示。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 9. A system for shielding a mobile terminal from accessing the wireless network information, comprising: a mobile terminal and a domain name evaluation server, whereinthe domain name evaluation server is configured to acquire a domain name evaluation record by accessing a website corresponding to a domain name and evaluating and store the domain name evaluation record; wherein the domain name evaluation record comprises the domain name and the evaluation of the domain name; andthe mobile terminal comprises: a domain name resolution unit, a domain name query unit and an access prompting unit, whereinthe domain name resolution unit is configured to receive an access command and acquire a corresponding domain name according to a webpage address in the access command;the domain name query unit is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; andthe access prompting unit is configured to generate a prompt according to the evaluation of the domain name.(String), 10.根据权利要求9所述的屏蔽移动终端访问无线网络信息的系统,其中域名测评服务器包括:定时更新单元,用于定时启动访问所有网络,获取该域名对应的网站的测评记录并存储测评记录。(String), 0(Integer), 8(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 10. The system for shielding the mobile terminal from accessing the wireless network information according to claim 9, wherein the domain name evaluation server comprises: a timing updating unit, configured to be started at time intervals to access all the networks, acquire the evaluation records of the websites corresponding to the domain names and store the evaluation records.(String), 11.根据权利要求2所述的屏蔽移动终端访问无线网络信息的方法,其中查询域名的域名评价记录,获取域名评价的步骤包括:查询移动终端缓存中是否存在该域名的域名评估记录;当缓存中存在域名的域名评估记录时,根据域名评估记录获取域名的评估;和当缓存中不存在该域名的域名评估记录时,从与移动终端连接的域名评估服务器查询该域名的域名评估记录,获取该域名的评估结果。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 11. The method for shielding the mobile terminal from accessing the wireless network information according to claim 2, wherein the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises:querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal;when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; andwhen the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name.(String), 12.根据权利要求3所述的屏蔽移动终端访问无线网络信息的方法,其中查询域名的域名评价记录,获取域名评价的步骤包括:查询移动终端缓存中是否存在该域名的域名评估记录;当缓存中存在域名的域名评估记录时,根据域名评估记录获取域名的评估;和当缓存中不存在该域名的域名评估记录时,从与移动终端连接的域名评估服务器查询该域名的域名评估记录,获取该域名的评估结果。(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 12. The method for shielding the mobile terminal from accessing the wireless network information according to claim 3, wherein the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises:querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal;when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; andwhen the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name.(String), 13.根据权利要求6所述的移动终端,其中域名查询单元包括:缓存查询模块和切换模块,其中缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评估记录;和切换模块,用于当缓存单元中存在域名的域名评估记录时,根据域名评估记录获取域名的评估,并从域中查询域名的域名评估记录域名评估服务器与移动终端连接,当缓存单元中不存在该域名的域名评估记录时,获取该域名的评估结果。(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 13. The mobile terminal according to claim 6, wherein the domain name query unit comprises: a cache query module and a switching module, whereinthe cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; andthe switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit.(String), 14.根据权利要求7所述的移动终端,其中域名查询单元包括:缓存查询模块和切换模块,其中缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评估记录;和切换模块,用于当缓存单元中存在域名的域名评估记录时,根据域名评估记录获取域名的评估,并从域中查询域名的域名评估记录域名评估服务器与移动终端连接,当缓存单元中不存在该域名的域名评估记录时,获取该域名的评估结果。(String), 1(Integer), 12(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186010(Integer), 14. The mobile terminal according to claim 7, wherein the domain name query unit comprises: a cache query module and a switching module, whereinthe cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; andthe switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit.(String), 1(Integer), 13(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.559 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.559 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.559 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186010(Integer), FIELD OF THE INVENTION [0001]The present invention relates to the technical field of information processing, and in particular to a mobile terminal, a method and system for shielding a mobile terminal from accessing wireless network information. BACKGROUND OF THE INVENTION [0002]With the continuous development of the communication technology, wireless Internet access can be implemented and rapidly developed, and it takes an important effect in daily life and work of people. However, different from a conventional communication network, the wireless Internet includes a great amount of independent Wireless Application Protocol (WAP) websites (such as mobile phone websites) and World Wide Web (WWW) websites. These websites operate independently and can be directly or indirectly connected into the wireless Internet by various modes without signing the contract with telecom operators. Currently, thousands of the websites exist, contents broadcast by the websites are more and more complex, the websites are of varying quality and both bad and good websites are mixed up. The matched supervision measures and technical means are not completely provided and cannot be mentioned in the same breath with the supervision mechanism for the fixed Internet, which is formed by years of comprehensive treatment, so that loopholes are provided for criminals to spread obscene, pornographic and violent information and the social “cancer” is formed. [0003]Due to low frequency of a Central Processing Unit (CPU) and small memory space of embedded systems such as mobile terminals (e.g., a mobile phone, a Personal Digital Assistant (PDA) etc..) and the like, browsers operating on the mobile terminals generally only have a function of browsing the web and cannot be used for shielding obscene, pornographic, violent and illegal websites. However, the mobile terminals such as the mobile phone and the like are very common and most of users have a habit of spending leisure time in a mode of surfing the Internet by the mobile phones, so the user possibly contact the pornographic and violent information. Specifically, part of people (specifically, teenagers and the like) are short of awareness of preventing the violent and pornographic websites, and if the people are addicted to the violent and pornographic websites for a long time, the study and life can be seriously influenced so as to cause serious social problems. SUMMARY OF THE INVENTION [0004]The present invention provides a mobile terminal, a method and a system for shielding a mobile terminal from accessing wireless network information, thus the information in a wireless network is shielded according to the requirements of users. [0005]The present invention provides a method for shielding a mobile terminal from accessing the wireless network information, which is used for shielding the information in the wireless network for the mobile terminal. The mobile terminal is provided with a browser configured to access the wireless network. The method comprises: [0006]receiving an access command and acquiring a corresponding domain name according to a webpage address in the access command; [0007]querying a domain name evaluation record of the domain name and acquiring evaluation of the domain name, wherein the domain name evaluation record includes the domain name and the evaluation of the domain name; and [0008]generating a prompt according to the evaluation of the domain name. [0009]Preferably, after the step of querying the domain name evaluation record of the domain name is executed, the method further comprises: [0010]storing the domain name evaluation record in a cache of the mobile terminal. [0011]Preferably, the domain name evaluation record is acquired in a mode that a domain name evaluation server connected with the mobile terminal accesses a website corresponding to the domain name and evaluates. [0012]Preferably, the step of querying the domain name evaluation record of the domain name and acquiring the evaluation of the domain name comprises: [0013]querying whether the domain name evaluation record of the domain name exists in the cache of the mobile terminal; [0014]when the domain name evaluation record of the domain name exists in the cache, acquiring the evaluation of the domain name according to the domain name evaluation record; and [0015]when the domain name evaluation record of the domain name does not exist in the cache, querying the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquiring the evaluation of the domain name. [0016]The present invention also provides a mobile terminal, comprises a browser configured to access the wireless network. The mobile terminal further comprises: a domain name resolution unit, a domain name query unit and an access prompting unit, wherein [0017]the domain name resolution unit is configured to receive a access command and acquire the corresponding domain name according to the webpage address in the access command; [0018]the domain name query unit is configured to query a domain name evaluation record of the domain name and acquire the evaluation of the domain name; the domain name evaluation record comprises the domain name and the evaluation of the domain name; and [0019]the access prompting unit is configured to generate a prompt according to the evaluation of the domain name. [0020]Preferably, the mobile terminal further comprises: [0021]a cache unit configured to store the domain name evaluation record after the domain name query unit queries the domain name evaluation record of the domain name. [0022]Preferably, the domain name evaluation record is acquired in a mode that a domain name evaluation server connected with the mobile terminal accesses the website corresponding to the domain name and evaluates. [0023]Preferably, the query unit comprises a cache query module and a switching module, wherein [0024]the cache query module is configured to query whether the domain name evaluation record of the domain name exists in the cache unit of the mobile terminal; and [0025]the switching module is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record of the domain name exists in the cache unit, and query the domain name evaluation record of the domain name from the domain name evaluation server connected with the mobile terminal and acquire the evaluation of the domain name when the domain name evaluation record of the domain name does not exist in the cache unit. [0026]The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information in the wireless network, the system comprises a mobile terminal and a domain name evaluation server, wherein [0027]the domain name evaluation server is configured to acquire a domain name evaluation record by accessing a website corresponding to the domain name and evaluating and store the domain name evaluation record; the domain name evaluation record comprises the domain name and the evaluation of the domain name; and [0028]the mobile terminal is provided with a browser configured to access the wireless network, and the mobile terminal further comprises a domain name resolution unit, a domain name query unit and a access prompting unit, wherein [0029]the domain name resolution unit is configured to receive a access command and acquire the corresponding domain name according to a webpage address in the access command; [0030]the domain name query unit is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; and [0031]the access prompting unit is configured to generate the prompt according to the evaluation of the domain name. [0032]Preferably, the domain name evaluation server comprises a timing updating unit configured to be started at time intervals to access the network, acquire the evaluation record of the website corresponding to the domain name and store the evaluation record. [0033]According to the method for shielding the mobile terminal from accessing the wireless network information, the mobile terminal or the system for shielding the mobile terminal from accessing the wireless network information, which is disclosed by the present invention, the domain name is acquired by resolving the webpage address, so that when the website is accessed, the browser firstly queries the domain name evaluation record of the domain name to acquire the evaluation of the website to be accessed and the user can select to stop accessing the website according to the evaluation to shield the information; furthermore, the browser can store the domain name evaluation record into the mobile terminal, and when accessing the webpage address next time, the browser firstly queries the mobile terminal and queries the domain name evaluation record related to the domain name in the domain name evaluation server if the evaluation record of the domain name corresponding to the webpage address to be accessed does not exist in the mobile terminal so as to further shield the information in the wireless network. BRIEF DESCRIPTION OF THE DRAWINGS [0034]FIG. 1 shows a flowchart of a method for shielding a mobile terminal from accessing wireless network information according to an embodiment of the present invention; [0035]FIG. 2 shows a flowchart of a method for querying a domain name evaluation record and acquiring evaluation of a domain name according to an embodiment of the present invention; [0036]FIG. 3 shows a structural diagram of a mobile terminal according to an embodiment of the present invention; [0037]FIG. 4 shows a structural diagram of a mobile terminal according to another embodiment of the present invention; and [0038]FIG. 5 shows a structural diagram of a system for shielding the mobile terminal from accessing the wireless network information according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS [0039]The implementation of the aims, the functional characteristics and the advantages of the present invention are further illustrated with reference to the accompanying drawings by combining embodiments. [0040]In the present invention, the mobile terminal can be a mobile phone, a Personal Digital Assistant (PDA) and the like, and the network can be a Wireless Application Protocol (WAP), a World Wide Web (WWW) and the like. By taking the mobile phone as the example, a method for shielding the mobile terminal from accessing wireless network information, the mobile terminal and a system for shielding the mobile terminal from accessing the wireless network information, which are disclosed by the present invention, are described in details as below. It should be understood that the specific embodiments described herein are only used to explain the present invention and shall not be construed as improper limitations on the same. [0041]FIG. 1 shows a flowchart of a method for shielding the mobile terminal from accessing the wireless network information according to an embodiment of the present invention, which is applied for the mobile terminal shielding the information in a wireless network. The mobile terminal is provided with a browser configured to access the wireless network. The method comprises the following steps: [0042]Step 10: the browser receives an access command and acquires a corresponding domain name according to a webpage address in the access command; in one embodiment, a domain name resolution function can be implemented by devices such as a Domain Name System (DNS) and the like, for example, if the webpage address is http://www.xxx.com/news, the corresponding domain name, i.e. www.xxx.com, can be acquired by the DNS. [0043]Step 20: a domain name evaluation record of the domain name is queried and evaluation of the domain name is acquired; the domain name evaluation record comprises the domain name and the evaluation of the domain name; a format of the domain name evaluation record can make reference to the Table 1: TABLE 1Domain nameViolencePornographyIllegality. . .www.xxx.comYesNoNo. . .www.yyy.com.cnNoYesNo. . .www.sina.comNoNoNoNo. . .. . .. . .. . .. . . [0044]There are various modes of acquiring the domain name evaluation record. For example, in one embodiment, a website corresponding to the domain name can be accessed, graphics and texts are identified mutually and the domain name evaluation record with the format shown in the Table 1 is established and stored in a database. In another embodiment, contents in the website can also be acquired and compared by a graphic-text comparing technology so as to acquire the domain name evaluation record and store the domain name evaluation record in the database. The link between the mobile terminal and the database can be established by communication protocols such as a Hyper Text Transfer Protocol (HTTP), a File Transfer Protocol (FTP) and the like so as to query the domain name evaluation record. [0045]There are various options for the format of the Table 1. Preset conditions such as violence, pornography, illegality and the like in the Table 1 can be set according to the requirements of a user, which are not detailed here. [0046]Step 30: a prompt is generated according to the evaluation of the domain name. In an embodiment, if the webpage address to be accessed is http://www.xxx.com/news and the evaluation that the domain name www.xxx.com of the website has violence information exists in the domain name evaluation record, the evaluation is displayed to prompt the user that if the user accesses the website, both the body and the mind of the user are possibly damaged, so that the user can select not to access the website to shield the harmful information. If the violent, pornographic and illegal harmful information does not exist in the website to be accessed, for example, the website to be accessed is http://www.sina.com and the evaluation of the domain name www.sina.com in the domain name evaluation record is normal, the browser directly accesses the website. [0047]By the method, the user can firstly acquire the evaluation of the website to be accessed when accessing the wireless network and can select to stop accessing the website according to the evaluation so as to shield the harmful information, purify the network environment and guarantee the physical and psychological health of the user. [0048]In the embodiment, Step 20 can further comprises a step of the domain name evaluation record is stored in a cache. For example, if acquiring the domain name evaluation of the webpage address corresponding to the domain name by querying the domain name evaluation record, the browser stores the domain name evaluation in the cache for prompting when accessing next time. In the embodiment, the browser is set to firstly query the cache so as to acquire the evaluation of the website corresponding to the domain name, thereby improving the query speed of the domain name evaluation record. [0049]In the embodiment, the domain name evaluation record can be acquired in a mode that a domain name evaluation server accesses the website corresponding to the domain name and evaluates. The domain name evaluation server is a server which is provided by an operator and is configured to carry out related evaluation on the domain name. By accessing all websites, the domain name evaluation server records evaluation information of the websites corresponding to different domain names, for example, whether the pornographic, violent and illegal information exists on the website corresponding to the domain name is recorded. The domain name evaluation server can provide a function of querying the domain name and return the evaluation information of the domain name, i.e. the website with the domain name is a violent, pornographic and illegal website or not. The domain name evaluation server can be provided by the country or a telecom operation corporation. The domain name information can be updated by manually carrying out analysis evaluation and can also be updated by carrying out analysis evaluation on different website domain names according to different modes such as keywords, image identification and the like. [0050]As shown in FIG. 2, Step 20 further comprises the steps of: [0051]Step 21: the browser queries whether the domain name evaluation record of the domain name exists in the cache; for example, in the embodiment, the browser can store the evaluation record of the website corresponding to the domain name when accessing the website last time to the cache so as to query the evaluation record when accessing the website next time. The speed of acquiring the evaluation of the website can be improved by querying a local record. [0052]Step 22: when the domain name evaluation record of the domain name exists in the cache, the evaluation of the domain name is acquired according to the domain name evaluation record; and if the domain name evaluation record exists in the cache, the browser prompts or directly accesses the webpage according to the evaluation corresponding to the domain name. [0053]Step 23: when the domain name evaluation record does not exist in the cache, the domain name evaluation record of the domain name is queried from the domain name evaluation server to acquire the evaluation of the domain name. If the evaluation of the website corresponding to the domain name does not exist in the cache, the domain name evaluation record is queried from the domain name evaluation server to acquire the evaluation of the domain name and then the browser prompts or directly accesses the webpage. [0054]FIG. 3 shows the structure of a mobile terminal 100 according to another embodiment of the present invention. The mobile terminal 100 comprises a browser 10 configured to access wireless networks and shield the information in the wireless networks. The mobile terminal 100 further comprises a domain name resolution unit 11, a domain name query unit 12 and an access prompting unit 13, wherein [0055]the domain name resolution unit 11 is configured to receive the access command and acquire the corresponding domain name according to the webpage address in the access command; in one embodiment, the domain name resolution unit 11 can extract the domain name in the webpage address according to the access command input into the browser 10, for example, in the embodiment, if the webpage address input into the browser 10 is http://www.xxx.com/news, the domain name www.xxx.com can be acquired by the domain name resolution unit 11. In a specific example, in the domain name resolution unit 11, the domain name resolution function can be implemented by devices such as the DNS and the like. [0056]The domain name query unit 12 is configured to query the domain name evaluation record of the domain name and acquire the evaluation of the domain name; the domain name evaluation record comprises the domain name and the evaluation of the domain name; in one embodiment, by the domain name query unit 12, an access relation between the browser 10 and the database or the domain name evaluation server can be established and the domain name evaluation record is extracted from the database or the domain name evaluation server so as to query the evaluation of the website corresponding to the domain name. [0057]The access prompting unit 13 is configured to generate a prompt according to the evaluation of the domain name. For example, if a result that the obscene, violent or illegal information exists on the website to be accessed is obtained by carrying out query via the domain name query unit 12, the prompt of the harmful information is displayed by the access prompting unit 13 through a display screen of the mobile phone, or the harmful information is subjected to alarm prompting by voice and the like, so that the user stops continuously accessing the website to be accessed to shield the information. [0058]As shown in FIG. 4, in one embodiment, the mobile terminal 100 further comprises a cache unit 14 configured to store the domain name evaluation record. In general, for accelerating to browser, the browser of the existing mobile phone is provided with the browser cache configured to store documents requested recently into a user disk, and thus, when a visitor requests the page again, the browser can display the documents from the local disk so as to accelerate to browser the page. In the present invention, the evaluation obtained when the website was accessed last time can be stored by the cache of the browser so as to be queried when the website is accessed next time. The domain name query unit 12 further comprises a cache query module 15 and a switching module 16, wherein the cache query module 15 is configured to query the domain name evaluation record in the cache unit 14 to acquire the evaluation of the domain name before the website is accessed next time, thus the speed of querying the domain name can be improved by utilizing the cache query module 15. [0059]the switching module 16 is configured to acquire the evaluation of the domain name according to the domain name evaluation record when the domain name evaluation record exists in the cache unit 14, and query the domain name evaluation record of the domain name from the domain name evaluation server 200 and acquire the evaluation of the domain name when the domain name evaluation record does not exist in the cache unit 14. [0060]The present invention also provides a system for shielding the mobile terminal from accessing the wireless network information. The system comprises the mobile terminal 100 and the domain name evaluation server 200. As shown in FIG. 5, in one embodiment, the domain name evaluation server 200 is configured to acquire the domain name evaluation record by accessing the website corresponding to the domain name and evaluating and store the domain name evaluation record. The domain name evaluation server 200 communicates with wireless networks by the HTTP, the FTP and the like. The evaluation information of the websites corresponding to different domain names is recorded by accessing all the websites, for example, whether the pornographic, violent and illegal information exists on the website corresponding to the domain name is recorded. The domain name evaluation server can provide the function of querying the domain name and return the evaluation information of the domain name, i.e. the website with the domain name is a violent, pornographic and illegal website or not. The domain name evaluation server can be provided by the country or the telecom operation corporation. The domain name information can be updated by manually carrying out analysis evaluation and can also be updated by carrying out analysis evaluation on different website domain names according to different modes such as keywords, image identification and the like. [0061]In the network, the websites are updated frequently. For acquiring more comprehensive website health information, the website needs to be accessed according to the continuously updated webpage address to extract the domain name of the website and the website health information so as to continuously update the domain name evaluation record. On this basis, the present invention provides another embodiment. In the embodiment, the domain name evaluation server further comprises a timing updating unit 201 configured to be started at time intervals to access the network, acquire the evaluation of the website and update the domain name evaluation record. [0062]The descriptions above are only the preferable embodiment of the present invention, which are not used to restrict the present invention. For those skilled in the art, the present invention may have various changes and variations. Any amendments, equivalent substitutions, improvements, etc. within the principle of the present invention are all included in the scope of the protection of the present invention.(String), 发明领域 [0001] 本发明涉及信息处理技术领域,尤其涉及一种移动终端、屏蔽移动终端访问无线网络信息的方法及系统。 背景技术 [0002] 随着通信技术的不断发展,无线上网得以实现并迅速发展,在人们的日常生活和工作中发挥着重要作用。 然而,与传统的通信网络不同的是,无线互联网包括大量独立的无线应用协议(WAP)网站(如手机网站)和万维网(WWW)网站。 这些网站独立运营,无需与电信运营商签订合同,即可通过多种方式直接或间接接入无线互联网。 目前,网站数以千计,网站播放的内容越来越复杂,网站质量参差不齐,良莠不齐。 配套的监管措施和技术手段不完备,不能与多年综合整治形成的固网监管机制相提并论,为不法分子传播淫秽、色情、色情内容提供了漏洞。 暴力信息,形成社会“毒瘤”。 [0003] 由于中央处理器(CPU)的频率低,以及移动终端(例如,移动电话、个人数字助理(PDA)等)等嵌入式系统的存储空间小,在移动设备上运行的浏览器 终端一般只有浏览网页功能,不能用于屏蔽淫秽、色情、暴力和非法网站。 但是,手机等移动终端非常普遍,大部分用户都有通过手机上网的方式来消磨闲暇时间的习惯,因此用户可能会接触到色情和暴力信息。 具体来说,部分人群(特别是青少年等)缺乏防范暴力色情网站的意识,如果长期沉迷于暴力色情网站,会严重影响学习和生活 从而引发严重的社会问题。 发明内容 [0004] 本发明提供一种移动终端、屏蔽移动终端访问无线网络信息的方法及系统,从而根据用户的需求屏蔽无线网络中的信息。 [0005] 本发明提供一种屏蔽移动终端访问无线网络信息的方法,用于为移动终端屏蔽无线网络中的信息。 移动终端配备有用于访问无线网络的浏览器。 该方法包括: [0006] 接收访问命令,根据访问命令中的网页地址获取对应的域名; [0007] 查询域名的域名评价记录,获取域名评价,其中,域名评价记录包括域名和域名评价; 和 [0008] 根据对域名的评价产生提示。 [0009] 优选地,在执行查询域名的域名评价记录的步骤之后,该方法还包括: [0010] 将域名评价记录保存在移动终端的缓存中。 [0011] 优选地,域名评估记录是通过与移动终端连接的域名评估服务器访问该域名对应的网站并进行评估的方式获取的。 [0012] 优选地,所述查询域名的域名评价记录并获取域名评价的步骤包括: [0013] 查询移动终端缓存中是否存在该域名的域名评价记录; [0014]当缓存中存在该域名的域名评价记录时,根据该域名评价记录获取该域名的评价; 和 [0015] 当缓存中不存在该域名的域名评价记录时,从与移动终端连接的域名评价服务器中查询该域名的域名评价记录,获取该域名的评价。 [0016] 本发明还提供一种移动终端,包括用于访问无线网络的浏览器。 所述移动终端还包括:域名解析单元、域名查询单元和接入提示单元,其中 [0017] 域名解析单元,用于接收访问命令,根据访问命令中的网页地址获取对应的域名。 [0018] 域名查询单元,用于查询域名的域名评价记录,获取对域名的评价。 域名评价记录包括域名和域名评价; 和 [0019] 访问提示单元,用于根据对域名的评价产生提示。 [0020] 优选地,所述移动终端还包括: [0021] 缓存单元,用于在域名查询单元查询到域名的域名评价记录后,存储域名评价记录。 [0022] 优选地,所述域名评估记录是通过与所述移动终端连接的域名评估服务器访问所述域名对应的网站并进行评估的方式获取的。 [0023] 优选地,查询单元包括缓存查询模块和切换模块,其中 [0024] 缓存查询模块,用于查询移动终端的缓存单元中是否存在该域名的域名评价记录。 和 [0025] 切换模块,用于当缓存单元中存在域名的域名评价记录时,根据域名评价记录获取域名的评价,并从域中查询该域名的域名评价记录。 与移动终端连接的域名评价服务器,当缓存单元中不存在该域名的域名评价记录时,获取该域名的评价。 [0026] 本发明还提供一种在无线网络中屏蔽移动终端访问无线网络信息的系统,该系统包括移动终端和域名评估服务器,其中 [0027] 域名评估服务器,用于通过访问域名对应的网站获取域名评估记录,并评估并存储域名评估记录。 域名评价记录包括域名和域名评价; 和 [0028] 所述移动终端设置有用于接入无线网络的浏览器,所述移动终端还包括域名解析单元、域名查询单元和接入提示单元,其中 [0029] 域名解析单元,用于接收访问命令,根据访问命令中的网页地址获取对应的域名。 [0030] 域名查询单元,用于查询域名的域名评价记录,获取对域名的评价。 和 [0031] 访问提示单元,用于根据对域名的评估生成提示。 [0032] 优选地,所述域名评价服务器包括定时更新单元,用于定时启动访问网络,获取所述域名对应的网站的评价记录,并存储所述评价记录。 [0033]本发明公开的移动终端访问无线网络信息的屏蔽方法、移动终端或移动终端访问无线网络信息的屏蔽系统,通过解析 网页地址,以便在访问网站时,浏览器首先查询该域名的域名评价记录,获取所访问网站的评价,用户可以根据评价选择停止访问该网站以屏蔽 资料; 另外,浏览器可以将域名评价记录保存到移动终端中,下次访问网页地址时,浏览器首先查询移动终端,在域名评价服务器中查询与该域名相关的域名评价记录 如果要访问的网页地址对应的域名的评价记录在移动终端中不存在,进一步屏蔽无线网络中的信息。 附图的简要说明 [0034] 图1示出了根据本发明实施例的屏蔽移动终端访问无线网络信息的方法的流程图。 [0035] 图2示出了根据本发明实施例的查询域名评价记录和获取域名评价的方法的流程图。 [0036] 图3示出了根据本发明实施例的移动终端的结构图; [0037] 图4示出了根据本发明另一实施例的移动终端的结构图; 和 [0038] 图5示出了根据本发明实施例的移动终端访问无线网络信息的屏蔽系统的结构图。 具体实施方式 [0039] 本发明的目的、功能特点和优点的实现,结合附图,结合实施例作进一步说明。 [0040] 在本发明中,移动终端可以是手机、个人数字助理(PDA)等,网络可以是无线应用协议(WAP)、万维网(WWW)等。 以手机为例,对本发明公开的一种屏蔽移动终端访问无线网络信息的方法、移动终端及屏蔽移动终端访问无线网络信息的系统进行说明。 详情如下。 应当理解,此处所描述的具体实施例仅用于解释本发明,不应理解为对本发明的不当限制。 [0041] 图1示出了根据本发明实施例的屏蔽移动终端访问无线网络信息的方法的流程图,该方法应用于移动终端屏蔽无线网络中的信息。 移动终端配备有用于访问无线网络的浏览器。 该方法包括以下步骤: [0042] 步 10 :浏览器接收访问命令,根据访问命令中的网页地址获取对应的域名。 在一个实施例中,域名解析功能可以通过域名系统(DNS)等设备来实现,例如,如果网页地址为http://www.xxx.com/news,则对应的域 域名,即 www.xxx.com,可以被 DNS 获取。 [0043] 步 20 :查询域名的域名评价记录,获取域名评价; 域名评价记录包括域名和域名评价; 域名评估记录的格式可以参考表1: 表格1 域名 暴力 色情 违法 . . . www.xxx.com 是的 不 不 . . . www.yyy.com.cn 不 是的 不 . . . 新浪网 不 不 不 不 . . . . . . . . . . . . . . . [0044]域名评估记录的获取方式有多种。 例如,在一个实施例中,可以访问该域名对应的网站,图文相互识别,建立如表1所示格式的域名评价记录并存储在数据库中。 在另一个实施例中,还可以通过图文比对技术获取网站中的内容并进行比对,从而获取域名评价记录,并将域名评价记录存储在数据库中。 移动终端与数据库之间可以通过HTTP、FTP等通信协议建立链接,查询域名评价记录。 [0045] 表1的格式有多种选择。表1中预设的暴力、色情、违法等条件可以根据用户的需要进行设置,在此不再赘述。 [0046] 步 30 :根据对域名的评价产生提示。 在一个实施例中,如果要访问的网页地址为http://www.xxx.com/news,并且在域名评价记录中存在该网站的域名www.xxx.com存在暴力信息的评价,则 显示评价提示用户,如果用户访问该网站,用户的身心都可能受到损害,以便用户可以选择不访问该网站,以屏蔽有害信息。 如果要访问的网站不存在暴力、色情、非法有害信息,例如要访问的网站是http://www.sina.com,域名www.sina.com的评价在 域名评价记录正常,浏览器直接访问网站。 [0047] 通过该方法,用户在访问无线网络时,可以首先获取对要访问的网站的评价,并可以根据评价选择停止访问该网站,从而屏蔽有害信息,净化网络环境,保证物理安全。 和用户的心理健康。 [0048] 在本实施例中,步骤 20 还可以包括将域名评价记录存储在缓存中的步骤。 例如,如果浏览器通过查询域名评价记录获得该域名对应的网页地址的域名评价,则浏览器将该域名评价保存在缓存中,以供下次访问时进行提示。 在本实施例中,设置浏览器首先查询缓存,以获取域名对应的网站的评价,从而提高了域名评价记录的查询速度。 [0049] 在本实施例中,可以通过域名评估服务器访问该域名对应的网站并进行评估的方式获取域名评估记录。 域名评估服务器是运营商提供的用于对域名进行相关评估的服务器。 域名评价服务器通过访问所有网站,记录不同域名对应的网站的评价信息,例如记录该域名对应的网站是否存在色情、暴力、非法信息。 域名评价服务器可以提供域名查询功能,返回域名评价信息,即该域名的网站是否为暴力、色情、非法网站。 域名评估服务器可以由国家或电信运营公司提供。 域名信息可以通过人工进行分析评估来更新,也可以根据关键词、图像识别等不同方式对不同的网站域名进行分析评估来更新。 [0050] 如图2所示,步骤 20 进一步包括以下步骤: [0051] 步 21:浏览器查询缓存中是否存在该域名的域名评价记录; 例如,在本实施例中,浏览器可以将上次访问该网站时该域名对应的网站的评价记录存储到缓存中,以便下次访问该网站时查询该评价记录。 通过查询本地记录可以提高获取网站评价的速度。 [0052] 步 22 :当缓存中存在该域名的域名评价记录时,根据该域名评价记录获取该域名的评价; 如果缓存中存在域名评价记录,则浏览器根据该域名对应的评价提示或直接访问网页。 [0053] 步 23 :当缓存中不存在域名评价记录时,向域名评价服务器查询该域名的域名评价记录,获取该域名的评价。 如果缓存中不存在该域名对应的网站的评价,则向域名评价服务器查询域名评价记录,获取该域名的评价,然后浏览器提示或直接访问该网页。 [0054] 图3显示了移动终端的结构 100 根据本发明的另一个实施例。 移动终端 100 包括一个浏览器 10 配置为访问无线网络并屏蔽无线网络中的信息。 移动终端 100 还包括域名解析单元 11 , 一个域名查询单元 12 和访问提示单元 13 , 其中 [0055] 域名解析单元 11 用于接收访问命令,根据访问命令中的网页地址获取对应的域名; 在一个实施例中,域名解析单元 11 可以根据浏览器输入的访问命令提取网页地址中的域名 10 ,例如,在本实施例中,如果网页地址输入到浏览器中 10 是http://www.xxx.com/news,域名www.xxx.com可以被域名解析单位获取 11 . 在一个具体的例子中,在域名解析单元中 11 ,域名解析功能可以通过DNS等设备来实现。 [0056] 域名查询单元 12 用于查询该域名的域名评价记录,获取该域名的评价; 域名评价记录包括域名和域名评价; 在一个实施例中,由域名查询单元 12 , 浏览器之间的访问关系 10 可以建立数据库或域名评价服务器,从数据库或域名评价服务器中提取域名评价记录,以查询该域名对应的网站的评价。 [0057] 接入提示单元 13 配置为根据对域名的评价生成提示。 例如,如果通过域名查询单元查询得到待访问网站上存在淫秽、暴力或非法信息的结果 12 , 有害信息的提示由访问提示单元显示 13 通过手机显示屏,或通过语音等方式对有害信息进行报警提示,使用户停止继续访问要访问的网站,屏蔽信息。 [0058] 如图4所示,在一个实施例中,移动终端 100 还包括缓存单元 14配置为存储域名评估记录。 一般来说,为了加速到浏览器,现有手机的浏览器都会设置浏览器缓存,用于将最近请求的文档存储到用户磁盘中,这样当访问者再次请求该页面时,浏览器就可以显示来自 本地磁盘以加速浏览页面。 在本发明中,可以将上次访问网站时得到的评价保存在浏览器的缓存中,以供下次访问网站时查询。 域名查询单元 12 还包括缓存查询模块 15 和一个开关模块 16 ,其中缓存查询模块 15 用于查询缓存单元中的域名评价记录 14 在下次访问网站前获取域名的评价,利用缓存查询模块提高域名查询速度 15 . [0059] 交换模块 16 用于当域名评价记录存在于缓存单元中时,根据域名评价记录获取对域名的评价 14 ,并从域名评估服务器查询该域名的域名评估记录 200 当缓存单元中不存在域名评价记录时,获取该域名的评价 14 . [0060] 本发明还提供了一种屏蔽移动终端访问无线网络信息的系统。 该系统包括移动终端 100 和域名评估服务器 200 . 如图5所示,在一个实施例中,域名评估服务器 200 用于通过访问域名对应的网站获取域名评价记录并评价并存储域名评价记录。 域名评估服务器 200 通过HTTP、FTP等方式与无线网络进行通信。 通过访问所有网站,记录不同域名对应的网站的评价信息,例如,记录该域名对应的网站是否存在色情、暴力、非法信息。 域名评价服务器可以提供域名查询功能,返回域名评价信息,即该域名的网站是否为暴力、色情、非法网站。 域名评估服务器可以由国家或电信运营公司提供。 域名信息可以通过人工进行分析评估来更新,也可以根据关键词、图像识别等不同方式对不同的网站域名进行分析评估来更新。 [0061] 在网络中,网站更新频繁。 为了获取更全面的网站健康信息,需要根据不断更新的网页地址访问网站,提取网站域名和网站健康信息,从而不断更新域名评估记录。 在此基础上,本发明提供了另一个实施例。 在本实施例中,域名评估服务器还包括定时更新单元 201 配置为定时启动访问网络,获取网站评价,更新域名评价记录。 [0062] 以上所述仅为本发明的较佳实施例而已,并不用于限制本发明。 对于本领域的技术人员来说,本发明可以有各种变化和变化。 凡在本发明的原则之内所作的任何修改、等同替换、改进等,均包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.601 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101883180A(String), EP2571229A1(String), EP2571229A4(String), US20130132567A1(String), WO2011140784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.758 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101883180A(String), EP2571229A1(String), EP2571229A4(String), US20130132567A1(String), WO2011140784A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.776 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101883180A(String), EP2571229A1(String), EP2571229A4(String), US20130132567A1(String), WO2011140784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 271611(Integer), CN101883180A(String), 1049372(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271611(Integer), EP2571229A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271611(Integer), EP2571229A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271611(Integer), US20130132567A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.932 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271611(Integer), WO2011140784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:16.967 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: CN101883180A(String), CN101883180A(String), 1289318400(Integer), 271611(Integer), 185896(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.000 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.001 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), JIANG, MIN(String), DUAN, YONGJIAN(String), MENG, ZHAO(String), 中兴通讯股份有限公司(String), JIANG MIN(String), DUAN YONGJIAN(String), MENG ZHAO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186010(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186010(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: JIANG, MIN(String), JIANG MIN(String), 0(Integer), 1681976177(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: DUAN, YONGJIAN(String), DUAN YONGJIAN(String), 0(Integer), 1681976177(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: MENG, ZHAO(String), MENG ZHAO(String), 0(Integer), 1681976177(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186010(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.288 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.288 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.288 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75860(Integer), 2(Integer), 186010(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75861(Integer), 2(Integer), 186010(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.357 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75862(Integer), 2(Integer), 186010(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.392 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75860(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.461 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.497 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.668 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186010(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:17.704 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10702769B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method for controlling mobile terminal by using touch input device(String), 移动终端及使用触摸输入设备控制移动终端的方法(String), US10702769B2(String), A mobile terminal for providing data to another mobile terminal through a touch input device includes: a touch screen configured to receive a touch input by the touch input device; a communication module configured to transmit and receive data through a communication connection with the touch input device; and a processor configured to, when a first touch input by the touch input device is received by the touch screen, provide, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to the other mobile terminal through the touch input device.(String), 一种通过触摸输入设备向另一移动终端提供数据的移动终端,包括: 触摸屏,用于接收触摸输入设备的触摸输入; 通信模块,被配置为通过与触摸输入设备的通信连接来发送和接收数据; 处理器,被配置为当触摸屏接收到触摸输入设备的第一触摸输入时,向触摸输入设备提供与当前在移动终端中执行的第一应用相关联的预定数据,使得 预定数据通过触摸输入设备提供给其他移动终端。(String), US15/752554(String), 1470931200(Integer), US10702769B2(String), 1594051200(Integer), 1594051200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 20(Integer), KR1020150054588A | KR1020150060364A | US20050025078A1 | US20070021216A1 | US20080256471A1 | US20090054108A1 | US20130046893A1 | US20130091238A1 | US20130106803A1 | US20130136370A1 | US20130181953A1 | US20140059159A1 | US20140059169A1 | US20150091917A1 | US20150135092A1 | US20160364600A1 | US8928587B1 | US9086746B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186011(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\e1dff7a3d63d4727b5f488b825b28d9a.png(String), 186011(Integer), e1dff7a3d63d4727b5f488b825b28d9a.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.280 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method for controlling mobile terminal by using touch input device(String), 移动终端及使用触摸输入设备控制移动终端的方法(String), US10702769B2(String), A mobile terminal for providing data to another mobile terminal through a touch input device includes: a touch screen configured to receive a touch input by the touch input device; a communication module configured to transmit and receive data through a communication connection with the touch input device; and a processor configured to, when a first touch input by the touch input device is received by the touch screen, provide, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to the other mobile terminal through the touch input device.(String), 一种通过触摸输入设备向另一移动终端提供数据的移动终端,包括: 触摸屏,用于接收触摸输入设备的触摸输入; 通信模块,被配置为通过与触摸输入设备的通信连接来发送和接收数据; 处理器,被配置为当触摸屏接收到触摸输入设备的第一触摸输入时,向触摸输入设备提供与当前在移动终端中执行的第一应用相关联的预定数据,使得 预定数据通过触摸输入设备提供给其他移动终端。(String), US15/752554(String), 1470931200(Integer), US10702769B2(String), 1594051200(Integer), 1594051200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 20(Integer), KR1020150054588A | KR1020150060364A | US20050025078A1 | US20070021216A1 | US20080256471A1 | US20090054108A1 | US20130046893A1 | US20130091238A1 | US20130106803A1 | US20130136370A1 | US20130181953A1 | US20140059159A1 | US20140059169A1 | US20150091917A1 | US20150135092A1 | US20160364600A1 | US8928587B1 | US9086746B1(String), \20230420\e1dff7a3d63d4727b5f488b825b28d9a.png(String), 20(Integer), 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.316 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.349 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 1. A mobile device for providing data to another mobile device using a touch input device, the mobile device comprising:a touch screen configured to obtain a touch gesture input by the touch input device, wherein touch gesture inputs are user-defined shapes;a communication module configured to transmit and receive data through a communication connection with the touch input device; andat least one processor configured to provide, to the touch input device in response to obtaining by the touch screen a first touch gesture input from a user, predetermined data having data associated with a first application that is currently being executed in the mobile device and indicating information about an account logged into in the first application,wherein the predetermined data is provided to the other mobile device through the touch input device based on obtaining a second touch gesture input by the other mobile device, wherein the first touch gesture input and the second touch gesture input are different forms,wherein the predetermined data is provided to a second application that matches the first application, and the account is logged into in the second application based on the predetermined data provided, andwherein the predetermined data comprises data indicating information about an address of a webpage of the first application and the logged-in account.(String), 1.一种使用触摸输入设备向另一移动设备提供数据的移动设备,该移动设备包括:触摸屏,用于获取触摸输入设备输入的触摸手势,触摸手势输入为用户自定义形状;通信模块被配置为通过与触摸输入设备的通信连接来发送和接收数据;和至少一个处理器,被配置为响应于通过触摸屏获得来自用户的第一触摸手势输入,向触摸输入设备提供预定数据,该预定数据具有与当前正在移动设备中执行的第一应用相关联的数据并且指示有关在第一个应用程序中登录的帐户的信息,其中,基于获得由另一移动设备输入的第二触摸手势,通过触摸输入设备向另一移动设备提供预定数据,其中,第一触摸手势输入和第二触摸手势输入是不同形式,其中,将预定数据提供给与第一应用相匹配的第二应用,并根据提供的预定数据在第二应用中登录账号,以及其中,预定数据包括指示第一应用程序的网页地址和登录帐户的信息的数据。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.351 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 2. The mobile device of claim 1, wherein, based on the first touch gesture input being obtained by the touch screen, the at least one processor is further configured to determine a type of the first touch gesture input and to provide the predetermined data corresponding to the first application and the determined type to the touch input device.(String), 2.如权利要求1所述的移动设备,其中,基于触摸屏获得第一触摸手势输入,至少一个处理器还被配置为确定第一触摸手势输入的类型,并向触摸提供对应于第一应用的预定数据和确定的类型输入设备。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 3. The mobile device of claim 1, wherein, based on the first touch gesture input being obtained by the touch screen, the at least one processor is further configured to control display of a list of the predetermined data associated with the first application on the touch screen and to provide data selected from the displayed list by the user to the touch input device.(String), 3.如权利要求1所述的移动设备,其中,基于触摸屏获得的第一触摸手势输入,至少一个处理器还被配置为控制在触摸屏上显示与第一应用相关联的预定数据的列表,并提供从显示的列表中选择的数据由用户触摸输入设备。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 4. The mobile device of claim 1, wherein the predetermined data associated with the first application comprises at least one of an image or a text selected on an execution screen of the first application by the user, a file that is being edited in the first application, and a multimedia file that is being reproduced in the first application.(String), 4.如权利要求1所述的移动设备,其中与第一应用程序相关联的预定数据包括用户在第一应用程序的执行屏幕上选择的图像或文本、正在第一应用程序中编辑的文件和正在再现的多媒体文件中的至少一个在第一个应用程序中。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 5. The mobile device of claim 1, wherein, based on the second touch gesture input by the touch input device being obtained by a touch screen of the other mobile device, the predetermined data provided to the touch input device is transmitted from the touch input device to the other mobile device, and the transmitted predetermined data is provided to the second application executed by the other mobile device.(String), 5.如权利要求1所述的移动设备,其中,基于触摸输入设备输入的第二触摸手势被另一移动设备的触摸屏获取,将提供给触摸输入设备的预定数据从触摸输入设备传输至另一移动设备,传输的预定数据数据被提供给由另一移动设备执行的第二应用程序。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 6. The mobile device of claim 5, wherein the predetermined data comprises link information for downloading installation data for installing the second application that is the same as the first application.(String), 6.如权利要求5所述的移动设备,其中预定数据包括下载用于安装与第一应用相同的第二应用的安装数据的链接信息。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 7. The mobile device of claim 5, wherein the predetermined data comprises setting data for setting the second application that is the same as the first application.(String), 7.如权利要求5所述的移动设备,其中预定数据包括用于设置与第一应用相同的第二应用的设置数据。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 8. The mobile device of claim 5, wherein the predetermined data comprises data indicating a state of the first application based on the first touch gesture input being obtained by the touch screen, anda state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application.(String), 8.如权利要求5所述的移动设备,其中预定数据包括指示基于由触摸屏获得的第一触摸手势输入的第一应用的状态的数据,以及通过使用提供给第二应用程序的预定数据,使第二应用程序的状态与第一应用程序的状态基本相同。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 9. The mobile device of claim 5, wherein the first application is a web browsing application, and the predetermined data comprises an address of a current webpage of the first application, andthe predetermined data is provided to the second application that is the web browsing application, and a web page corresponding to the address of the current webpage is opened in the second application.(String), 9.如权利要求5所述的移动设备,其中第一应用程序为网页浏览应用程序,预定数据包括第一应用程序的当前网页地址,以及将预定数据提供给第二应用程序即网页浏览应用程序,并在第二应用程序中打开当前网页地址对应的网页。(String), 1(Integer), 8(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.352 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 10. The mobile device of claim 5, wherein, in a case where the first application has a multimedia reproduction function and multimedia is paused in the first application based on the first touch gesture input being obtained by the touch screen, the predetermined data comprises data indicating a reproduction state of the multimedia and a paused reproduction position of the multimedia, andthe predetermined data is provided to the second application having the multimedia reproduction function, and reproduction of the multimedia is started in a paused state at a reproduction position in the second application.(String), 10.如权利要求5所述的移动设备,其中,在第一应用具有多媒体播放功能,并且基于触摸屏获得第一触摸手势输入,第一应用暂停多媒体的情况下,预定数据包括指示多媒体的播放状态的数据和暂停的多媒体的再现位置,以及预定数据被提供给具有多媒体再现功能的第二应用,并且多媒体的再现在第二应用中的再现位置处以暂停状态开始。(String), 1(Integer), 9(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 11. The mobile device of claim 5, wherein, in a case where the first application is a game application and a game is paused in the first application based on the first touch gesture input being obtained by the touch screen, the predetermined data comprises data indicating a progress state of the game and a paused position of the game, andthe predetermined data is provided to the second application that is the same as the first application, and the game is started in a paused state at the paused position in the second application.(String), 11.如权利要求5所述的移动设备,其中,在第一应用程序为游戏应用程序且第一应用程序基于触摸屏获得第一触摸手势输入暂停游戏的情况下,预定数据包括指示游戏进行状态的数据和暂停的比赛的位置,和预定数据被提供给与第一应用程序相同的第二应用程序,并且游戏在第二应用程序中的暂停位置处以暂停状态开始。(String), 1(Integer), 10(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 12. The mobile device of claim 5, wherein, in a case where the first application has an account login function, the first application is a web browsing application, and the account is logged into in the first application based on the first touch gesture input being obtained by the touch screen.(String), 12.如权利要求5所述的移动设备,其中,在第一应用具有账号登录功能的情况下,第一应用为网页浏览应用,基于触摸屏获取的第一触摸手势输入在第一应用中登录账号。(String), 1(Integer), 11(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 13. The mobile device of claim 1, wherein, based on a third touch gesture input by the touch input device being obtained by the touch screen, the at least one processor is further configured to receive the predetermined data provided to the touch input device from the touch input device, and to provide the predetermined data received from the touch input device to a third application in the mobile device.(String), 13.如权利要求1所述的移动设备,其中,基于触摸屏获取触摸输入装置输入的第三触摸手势,至少一处理器还用于接收触摸输入装置提供给触摸输入装置的预定数据,并提供预定数据从触摸输入设备接收到移动设备中的第三应用程序。(String), 1(Integer), 12(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 14. A method of controlling a mobile device by using a touch input device, the method comprising:obtaining a first touch gesture input by the touch input device on a touch screen of a first mobile device, wherein touch gesture inputs are user-defined shapes;providing, by the first mobile device, to the touch input device based on obtaining by the touch screen the first touch gesture input from a user, predetermined data having data, associated with a first application that is currently being executed in the first mobile device and indicating information about an account logged into in the first application;obtaining a second touch gesture input by the touch input device on a touch screen of a second mobile device; andproviding the predetermined data stored in the touch input device from the touch input device to the second mobile device based on obtaining the second touch gesture input by the second mobile device, wherein the first touch gesture input and the second touch gesture input are different forms,wherein the predetermined data is provided to a second application that matches the first application, and the account is logged into in the second application based on the predetermined data provided; andwherein the predetermined data comprises data indicating information about an address of a webpage of the first application and the logged-in account.(String), 14.一种通过触摸输入设备控制移动设备的方法,该方法包括:获取触控输入装置在第一移动装置的触控屏幕上输入的第一触控手势,其中触控手势输入为用户自定义形状;第一移动设备基于触摸屏获得用户的第一触摸手势输入,向触摸输入设备提供预定数据,该预定数据具有与第一移动设备中当前正在执行的第一应用相关联的数据,以及指示有关在第一个应用程序中登录的帐户的信息;获取触控输入装置在第二移动装置的触控屏幕上输入的第二触控手势;和基于获得第二移动设备的第二触摸手势输入,将触摸输入设备中存储的预定数据从触摸输入设备提供给第二移动设备,其中第一触摸手势输入和第二触摸手势输入是不同形式,其中,将预定数据提供给与第一应用相匹配的第二应用,并根据提供的预定数据在第二应用中登录账号。和其中,预定数据包括指示第一应用程序的网页地址和登录帐户的信息的数据。(String), 0(Integer), 13(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 15. The method of claim 14, wherein the predetermined data transmitted from the touch input device to the second mobile device is provided to the second application executed by the second mobile device.(String), 15.如权利要求14所述的方法,其中从触摸输入设备发送到第二移动设备的预定数据被提供给由第二移动设备执行的第二应用程序。(String), 1(Integer), 14(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 16. The method of claim 15, wherein the predetermined data comprises link information for downloading installation data for installing the second application that is the same as the first application.(String), 16.如权利要求15所述的方法,其中预定数据包括下载用于安装与第一应用相同的第二应用的安装数据的链接信息。(String), 1(Integer), 15(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.353 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 17. The method of claim 15, wherein the predetermined data comprises setting data for setting the second application that is the same as the first application.(String), 17.如权利要求15所述的方法,其中预定数据包括用于设置与第一应用相同的第二应用的设置数据。(String), 1(Integer), 16(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 18. The method of claim 15, wherein the predetermined data comprises data indicating a state of the first application based on the first touch gesture input being obtained by the touch screen, anda state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application.(String), 18.如权利要求15所述的方法,其中预定数据包括指示基于由触摸屏获得的第一触摸手势输入的第一应用的状态的数据,以及通过使用提供给第二应用程序的预定数据,使第二应用程序的状态与第一应用程序的状态基本相同。(String), 1(Integer), 17(Integer), 14(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 19. The method of claim 14, wherein, based on a third touch gesture input by the touch input device being obtained by the touch screen of the first mobile device, the predetermined data transmitted from the first mobile device to the touch input device is transmitted to the first mobile device and provided to a third application in the first mobile device.(String), 19.如权利要求14所述的方法,其中,基于触摸输入设备输入的第三触摸手势被第一移动设备的触摸屏获取,将第一移动设备发送给触摸输入设备的预定数据发送给第一移动设备,并提供给第三在第一个移动设备中的应用程序。(String), 1(Integer), 18(Integer), 13(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.354 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186011(Integer), 20. A computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, causes the computing device to:obtain a first touch gesture input by a touch input device on a touch screen of a first mobile device, wherein touch gesture inputs are user-defined shapes;provide, to the touch input device in response to obtaining by the touch screen the first touch gesture input from a user, predetermined data having data, associated with a first application that is currently being executed in the first mobile device and indicating information about an account logged into in the first application;obtain a second touch gesture input by the touch input device on a touch screen of a second mobile device; andprovide the predetermined data stored in the touch input device from the touch input device to the second mobile device based on obtaining the second touch gesture input by the second mobile device, wherein the first touch gesture input and the second touch gesture input are different forms,wherein the predetermined data is provided to a second application that matches the first application, and the account is logged into in the second application based on the predetermined data provided; andwherein the predetermined data comprises data indicating information about an address of a webpage of the first application and the logged-in account.(String), 20.计算机程序产品包括一种其中存储有计算机可读程序的计算机可读存储介质,其中计算机可读程序当在计算设备上执行时使计算设备:获取触控输入装置在第一移动装置的触控屏幕上输入的第一触控手势,其中触控手势输入为用户自定义形状;响应于触摸屏获得用户的第一触摸手势输入,向触摸输入设备提供预定数据,该预定数据具有与第一移动设备中当前正在执行的第一应用相关联并指示关于账户的信息的数据登录第一个应用程序;取得触控输入装置在第二移动装置的触控屏幕上输入的第二触控手势;和基于获得第二移动设备的第二触摸手势输入,将触摸输入设备中存储的预定数据从触摸输入设备提供给第二移动设备,其中第一触摸手势输入和第二触摸手势输入是不同形式,其中,将预定数据提供给与第一应用相匹配的第二应用,并根据提供的预定数据在第二应用中登录账号。和其中,预定数据包括指示第一应用程序的网页地址和登录帐户的信息的数据。(String), 0(Integer), 19(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.738 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186011(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The application is a 371 of International Patent Application No. PCT/KR2016/008877 filed Aug. 12, 2016, which claims priority to Chinese Patent Application No. 201510497976.9 filed Aug. 13, 2015, the disclosures of which are herein incorporated by reference in their entirety. TECHNICAL FIELD [0002]The present invention relates to a mobile terminal and a method of controlling the mobile terminal by using a touch input device, and more particularly, to a mobile terminal for providing data to another mobile terminal through a touch input device and a method of controlling the mobile terminal. BACKGROUND [0003]Recently, as electronic technology continues to develop, the application of touch control technology has gained popularity, and technology for controlling terminals through touch input and the touch input devices have attracted attention. Currently, a stylus pen is one from among representative touch input devices. [0004]The stylus pen may generate a touch input by touching the tip thereof to a touch screen, and may perform a control operation on a screen through a touch on the touch screen. In particular, the stylus pen is more suitable for operations such as writing, screen capture, and the like. For example, screen capture may be performed by designating a region that needs to be captured on the touch screen of the mobile terminal by using the stylus pen, and the captured screen is stored in the mobile terminal. Further, ideas of a user may be recorded at any time by performing writing in a memo application by using the stylus pen. [0005]The control technology of the mobile terminal according to the related art is limited to controlling one terminal through the touch input by using the touch input device. However, when a plurality of terminals are present, there is a need for a control technology capable of continuously executing an application between different terminals through a touch input. SUMMARY [0006]The present disclosure provides a mobile terminal for providing data to another mobile terminal through a touch input device and continuously executing an application, and a method of controlling the mobile terminal. [0007]According to an embodiment, it is possible to transmit data between different terminals through a touch input device and to continuously execute an application. DETAILED DESCRIPTION OF THE DRAWINGS [0008]FIG. 1A is a diagram schematically illustrating data being provided to another terminal through a stylus pen, according to an embodiment. [0009]FIG. 1B is a block diagram illustrating a configuration of a mobile terminal according to an embodiment. [0010]FIG. 2 is a block diagram illustrating an internal configuration of a touch input device according to an embodiment. [0011]FIG. 3 is a diagram illustrating a configuration of a stylus pen according to an embodiment. [0012]FIG. 4 is a diagram illustrating a structure in which the stylus pen according to an embodiment is inserted into the mobile terminal. [0013]FIG. 5 is a flowchart of a method of controlling a mobile terminal by using a touch input device, according to an embodiment. [0014]FIGS. 6 to 8 illustrate transmission and invoking of an image by using the stylus pen, according to an embodiment. [0015]FIGS. 9 to 11 illustrate transmission and invoking of a document file that is being edited in a memo application by using the stylus pen, according to an embodiment. [0016]FIGS. 12 to 14 illustrate continuous execution of a game application by using the stylus pen, according to an embodiment. [0017]FIGS. 15 to 17 illustrate continuous execution of a video streaming application by using the stylus pen, according to an embodiment. [0018]FIGS. 18 to 20 illustrate continuous execution of a web browsing application by using the stylus pen, according to an embodiment. [0019]FIGS. 21 to 23 illustrate continuous execution of a game application having an account login function by using the stylus pen, according to an embodiment. DETAILED DESCRIPTION [0020]In one embodiment, a mobile terminal for providing data to another mobile terminal through a touch input device includes: a touch screen configured to receive a touch input by the touch input device; a communication module configured to transmit and receive data through a communication connection with the touch input device; and a processor configured to, when a first touch input by the touch input device is received by the touch screen, provide, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to the other mobile terminal through the touch input device. [0021]In one embodiment, when the first touch input is received by the touch screen, the processor is further configured to determine a type of the first touch input and provide predetermined data corresponding to the first application and the determined type to the touch input device. [0022]In one embodiment, when the first touch input is received by the touch screen, the processor is further configured to control display of a list of the predetermined data associated with the first application on the touch screen and provide data selected from the displayed list by the user to the touch input device. [0023]In one embodiment, wherein the predetermined data associated with the first application includes at least one of an image or a text selected on an execution screen of the first application by the user, a file that is being edited in the first application, and a multimedia file that is being reproduced in the first application. [0024]In one embodiment, as a second touch input is input to the other mobile terminal by the touch input device, the predetermined data provided to the touch input device is transmitted from the touch input device to the other mobile terminal, and the transmitted predetermined data is provided to a second application executed by the other mobile terminal. [0025]In one embodiment, the predetermined data includes link information for downloading installation data for installing the second application that is the same as the first application. [0026]In one embodiment, the predetermined data includes setting data for setting the second application that is the same as the first application. [0027]In one embodiment, the predetermined data includes data indicating a state of the first application when the first touch input is received by the touch screen, and a state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application. [0028]In one embodiment, the first application is a web browsing application, and the predetermined data includes an address of a current webpage of the first application, and the predetermined data is provided to the second application that is the web browsing application, and a web page corresponding to the address of the webpage is opened in the second application. [0029]In one embodiment, in a case where the first application has a multimedia reproduction function and multimedia is paused in the first application when the first touch input is received by the touch screen, the predetermined data includes data indicating a reproduction state of the multimedia and a paused reproduction position of the multimedia, and the predetermined data is provided to the second application having the multimedia reproduction function, and the reproduction of the multimedia is started in a paused state at the reproduction position in the second application. [0030]In one embodiment, in a case where the first application is a game application and a game is paused in the first application when the first touch input is received by the touch screen, the predetermined data includes data indicating a progress state of the game and a paused position of the game, and the predetermined data is provided to the second application that is the same as the first application, and the game is started in the paused state at the position in the second application. [0031]In one embodiment, in a case where the first application has an account login function and an account is logged into in the first application when the first touch input is received by the touch screen, the predetermined data includes data indicating information about the logged-in account, and the predetermined data is provided to the second application that is the same as the first application, and the account is logged into in the second application. [0032]In one embodiment, when a third touch input by the touch input device is received by the touch screen, the processor is further configured to receive the predetermined data provided to the touch input device from the touch input device, and provide the predetermined data received from the touch input device to a third application in the mobile terminal. [0033]In one embodiment, a method of controlling a mobile terminal by using a touch input device includes: receiving a first touch input by the touch input device on a touch screen of a first mobile terminal; transmitting predetermined data associated with a first application that is currently being executed in the first mobile terminal from the first mobile terminal to the touch input device; receiving a second touch input by the touch input device on a touch screen of a second mobile terminal; and transmitting predetermined data stored in the touch input device from the touch input device to the second mobile terminal. [0034]In one embodiment, the predetermined data transmitted from the touch input device to the second mobile terminal is provided to a second application executed by the second mobile terminal. [0035]In one embodiment, the predetermined data includes link information for downloading installation data for installing the second application that is the same as the first application. [0036]In one embodiment, the predetermined data includes setting data for setting the second application that is the same as the first application. [0037]In one embodiment, the predetermined data includes data indicating a state of the first application when the first touch input is received by the touch screen, and a state of the second application is made substantially identical to the state of the first application by using the predetermined data provided to the second application. [0038]In one embodiment, when a third touch input by the touch input device is received by the touch screen of the first mobile terminal, the predetermined data transmitted from the first mobile terminal to the touch input device is transmitted to the first mobile terminal and provided to a third application in the first mobile terminal. MODE OF THE INVENTION [0039]The advantages and features of the present invention and methods for achieving them will become more apparent from the following embodiments that are described in detail in conjunction with the accompanying drawings. However, it should be understood that the present invention is not limited to the following embodiments, and various modifications can be made without departing from the scope of the present invention. The embodiments set forth herein are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. The present invention should be defined by the appended claims. Like reference numerals are assigned to like elements throughout. [0040]It will be understood that when a region is referred to as being “connected to” or “coupled to” another region, it may be directly connected or coupled to the other region or intervening regions may be present. It will be understood that terms such as “comprise”, “include”, and “have”, when used herein, specify the presence of stated elements, but do not preclude the presence or addition of one or more other elements. In addition, the term “unit” as used herein refers to software or hardware component such as FPGA or ASIC, and “unit” performs certain functions. However, “unit” is not limited to software or hardware. A “unit” may be configured in an addressable storage medium or configured to reproduce one or more processors. Thus, for example, a “unit” includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of programs codes, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and variables. Functions provided in the components and the “units” may be combined with a smaller number of components and “units” or may be separated from additional components and “units.” [0041]Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawing so that those of ordinary skill in the art can easily carry out the embodiments of the present invention. However, an embodiment may be implemented in various different forms and is not limited thereto. In order to clearly describe the embodiment in the drawings, portions not related to the description are omitted. [0042]The terms used herein are those general terms currently widely used in the art in consideration of functions in regard to the inventive concept, but the terms may vary according to the intention of those of ordinary skill in the art, precedents, or new technology in the art. In addition, specified terms may be selected by the applicant, and in this case, the detailed meaning thereof will be described in the detailed description of the inventive concept. Thus, the terms used herein should be understood not as simple names but based on the meaning of the terms and the overall description of the inventive concept. [0043]FIG. 1A is a diagram schematically illustrating that data is provided to another terminal through a stylus pen, according to an embodiment. [0044]Referring to FIG. 1A, when an image edit application is being executed in a mobile terminal 100 and a touch gesture having a shape “C” is input on a touch screen of the mobile terminal 100 by a stylus pen 300 in a state in which a cat image is selected by an operation of the stylus pen 300, the mobile terminal 100 transmits data including the selected cat image to the stylus pen 300 through a wireless communication connection. The data including the cat image is stored in a memory of the stylus pen 300. When an image edit application is being executed in another mobile terminal 101 and a touch gesture having a shape “P” is input on a touch screen of the mobile terminal 101 by the stylus pen 300, the other mobile terminal 101 receives data including the cat image from the stylus pen 300. The received data is provided to the image edit application that is being executed in the other mobile terminal 101, and the cat image is pasted on an existing image. [0045]FIG. 1B is a block diagram illustrating the configuration of the mobile terminal according to an embodiment. [0046]Referring to FIG. 1B, the mobile terminal 100 may include a touch screen 110, a communication module 120, and a processor 130. As described below with reference to FIG. 4, the mobile terminal 100 may further include a pen insertion hole 410, a data transmission interface 420, and/or a power supply interface 430. [0047]The communication module 120 is configured to form a communication connection with a touch input device and transmit and receive data through the communication connection. The communication module 120 may include a wired communication module 121 and/or a wireless communication module 122. [0048]As described below with reference to FIG. 4, the wired communication module 121 may form a wired communication connection with the stylus pen 300 in a state in which the stylus pen 300 is inserted into the pen insertion hole 410 such that a metal contact point 321 exposed on a pen body 310 of the stylus pen 300 is connected to the data transmission interface 420 in the pen insertion hole. The wired communication module 121 may form the wired communication connection with the touch input device in a state in which the touch input device is connected to the mobile terminal through a data line. [0049]When a wireless connection condition is satisfied, the wireless communication module 122 may automatically form a wireless communication connection with the touch input device. Alternatively, the wireless communication connection with the touch input device may be formed when a specific type of a touch input is received by the touch screen. When a wireless communication function of the mobile terminal is not activated, the wireless communication module 122 may first activate the wireless communication function and then form the wireless communication connection with the touch input device. The specific type of the touch input may be basically set by a system, or the user may directly define the specific type of the touch input according to a use habit. For example, the specific type of the touch input may be set as touching the touch screen by the touch input device. That is, when the touch screen is touched by the touch input device, the wireless communication module 122 may automatically form the wireless communication connection with the touch input device. [0050]The wireless communication module 122 may activate the wireless communication function of the mobile terminal, search for a touch input device capable of performing a wireless communication function, and form the wireless communication connection with the found touch input device after a connection command input by the user is received. [0051]The touch screen 110 is configured to receive or detect the touch input by the touch input device. A touch input mode that detects only first to third touch inputs set by the system or defined by the user may be set through the operation of the mobile terminal or the touch input device. [0052]The processor 130 may perform data transmission between the touch input device and the mobile terminal and may control an execution of an application in the mobile terminal. [0053]When the first touch input by the touch input device is received by the touch screen, the processor 130 provides, to the touch input device, predetermined data associated with a first application that is currently being executed in the mobile terminal, such that the predetermined data is provided to another mobile terminal through the touch input device. Before the processor 130 transmits the predetermined data associated with the first application to the touch input device, the processor 130 may read the predetermined data from a predetermined position or a predetermined interface. [0054]The first touch input may be basically set by the system, or the user may directly define the first touch input according to the use habit. In order to effectively distinguish the first touch input from a general touch input, the first touch input may be set as a touch gesture input. For example, the first touch input may be set as a touch gesture input having a shape of “C”. Before the first touch input is input, a touch input mode for detecting the first touch input may be set. [0055]According to an embodiment, the predetermined data associated with the first application may include at least one of an image or a text selected on an execution screen of the first application by the user, a file that is being edited in the first application, and a multimedia file that is being reproduced in the first application. For example, the image or the text selected on the execution screen of the first application by the user may be an image portion corresponding to a region selected in an image edited in an image edit application by the user, an image portion corresponding to a region selected on a currently displayed screen of an application by the user, and a text portion selected in a document edit application or a web browsing application by the user. The file that is being edited in the first application may be an image file that is being edited in an image edit application, a text file that is being edited in a document edit application, and a video file that is being edited in a video edit application. The multimedia file that is being reproduced in the first application may be an audio file that is being reproduced in an audio reproduction application and a video file that is being reproduced in a video reproduction application. However, the predetermined data associated with the first application is not limited to the above-described embodiment, and may include various data. According to an embodiment, the predetermined data associated with the first application may include link information for downloading installation data for installing a second application that is the same as the first application in another mobile terminal, and may include setting data for setting the second application that is the same as the first application in the other mobile terminal. [0056]According to an embodiment, the predetermined data associated with the first application may be previously determined as consistent data according to the type of the first application. That is, predetermined data corresponding to different applications may also be different from each other. For example, when the first application that is currently being executed in the mobile terminal is a document edit application, the predetermined data associated with the first application may be determined as at least one of an image or a text selected on the execution screen of the first application by the user, a document file that is being edited in the first application, and setting data for setting a document edit environment in the same application as the first application. In addition, when the first application that is currently being executed is a web browsing application that is in a logged-in state, the predetermined data associated with the first application may be determined as data indicating information about an address of a current webpage of the first application and a logged-in account. However, the predetermined data associated with the first application is not limited to the above-described example, and may include various combinations of data. [0057]According to an embodiment, when the first touch input is received by the touch screen, the processor 130 may control display of a list of the predetermined data associated with the first application on the touch screen and provide data selected from the displayed list by the user to the touch input device. [0058]According to an embodiment, when the first touch input is received by the touch screen, the processor 130 may determine the type of the first touch input and provide the predetermined data corresponding to the first application and the determined type to the touch input device. The predetermined data corresponding to the first application may be previously determined as described above. In the predetermined data corresponding to the first application, when the first touch input is a first type, the processor 130 may transmit first data corresponding to the first type to the touch input device, and when the first touch input is a second type, the processor 130 may transmit second data corresponding to the second type to the touch input device. Therefore, the touch input device may store a plurality of data (the first data and the second data) transmitted from the mobile terminal. As an example, when the first application that is currently being executed in the mobile terminal is a document edit application, the user may select whether to transmit a document file that is being edited in the first application or whether to transmit setting data for setting a document edit environment of an application that is the same as the first application, according to the type of the touch input. That is, when the first touch input that is the first type is received by the touch screen, the processor 130 may transmit a document file that is being edited to the touch input device, and when the first touch input that is the second type is received by the touch screen, the processor 130 may transmit the setting data to the touch input device. [0059]According to an embodiment, as a second touch input is input to another mobile terminal by the touch input device, the predetermined data provided to the touch input device may be transmitted from the touch input device to the other mobile terminal, and the transmitted predetermined data may be provided to a second application executed by the other mobile terminal. The second application may be the same application as the first application among applications installed on the other mobile terminal as described below. Alternatively, the second application may be an application capable of using data received from the touch input device among the applications installed on the other mobile terminal, or may be an application that is different from the first application. [0060]According to an embodiment, when a third touch input by the touch input device is received by the touch screen, the processor 130 may receive the predetermined data provided to the touch input device from the touch input device, and provide the predetermined data received from the touch input device to a third application in the mobile terminal 100. That is, the predetermined data transmitted from the mobile terminal 100 to the touch input device may be transmitted again to not another mobile terminal but the same mobile terminal 100 and used in the third application. The third application may be the same application as the first application among applications installed on the mobile terminal 100. Alternatively, the third application may be an application capable of using data received from the touch input device among applications installed on the mobile terminal 100, or may be an application that is different from the first application. [0061]FIG. 2 is a block diagram illustrating the internal configuration of the touch input device according to an embodiment. [0062]As illustrated in FIG. 2, the touch input device 200 may include a memory 210, a communication module 220, and a battery 230. The memory 210 in the touch input device 200 is configured to store data. The touch input device 200 may further include a control button for controlling operations of the components in the outside thereof, and various functions such as a function of setting a touch input mode for detecting first to third touch inputs may be executed through the control button. [0063]The memory 210 included in the touch input device 200 may be a non-plug-type storage device or a plug-type storage device. The communication module 220 in the touch input device 200 is configured to transmit and receive data through a communication connection with the mobile terminal. The communication module 220 may include a wired communication module 221 and/or a wireless communication module 222. The wireless communication module 222 may form a wireless communication connection with another device through any wireless connection. For example, the wireless communication module 222 may form the wireless communication connection with another device through Wi-Fi connection, Bluetooth (BT) connection, near-field communication (NFC) connection, or touch screen communication (HOTKNOT) connection. The touch input device 200 may exchange data with the mobile terminal through the wired communication module 221 or the wireless communication module 222. [0064]According to an embodiment, the touch input device 200 may provide data received from a first mobile terminal to a second mobile terminal. Specifically, as a first touch input is input to the first mobile terminal by the touch input device 200, predetermined data associated with a first application that is being executed in the first mobile terminal may be received from the first mobile terminal and stored in the touch input device 200, and as a second touch input is input to the second mobile terminal by the touch input device 200, the received predetermined data may be provided to the second mobile terminal. [0065]According to an embodiment, the touch input device 200 may be a stylus pen 300 as described with reference to FIG. 3. However, the touch input device 200 is not limited thereto and may be various types of devices for generating the touch input. [0066]FIG. 3 is a schematic diagram illustrating the configuration of the stylus pen according to an embodiment. [0067]As illustrated in FIG. 3, the stylus pen 300 may include a pen body 310, a data transmission interface 320, a charge interface 330, and a control button 340. As described above, various functions of the stylus pen 300 may be executed through the control button 340. In order to smoothly perform a communication connection between the stylus pen 300 and the mobile terminal, a data line and a control line in the wired communication module 221 may be integrated in the data transmission interface 320 disposed on the pen body 310. [0068]According to an embodiment, as illustrated in FIG. 3, the data transmission interface 320 disposed on the pen body 310 may be a plurality of metal contact points 321 exposed on the pen body 310. However, the configuration of the data transmission interface 320 is not limited to the metal contact points 321 illustrated in FIG. 3, and may be another type of a metal connector. The metal contact points 321 may be formed by inserting a metal plate into the pen body 310, spraying a conductive material to the pen body 310, or attaching a conductive material to the pen body 310. [0069]The stylus pen 300 may include the battery 230 so as to supply power thereto. In order to charge the battery 230, the stylus pen 300 may further include a charge module used to charge the battery 230 with power received from the outside. The charge module may perform a charge operation through the charge interface 330 or the data transmission interface 320. The charge interface 330 may be disposed on the pen body 310. In order to facilitate a charge operation and prevent an arbitrary contact of the charge interface 330, a plurality of invaginated metal contact points 331 may be set on the pen body 310. [0070]FIG. 4 is a diagram illustrating a structure in which the stylus pen according to the embodiment is inserted into the mobile terminal. [0071]The mobile terminal 400 according to the embodiment may include a pen insertion hole 410 for insertion of the stylus pen 300. In addition, a data transmission interface 420 and a power supply interface 430 may be provided in the pen insertion hole 410. As illustrated in FIG. 4, when the stylus pen 300 is inserted into the pen insertion hole 410 of the mobile terminal 400, a position of the data transmission interface 320 of the stylus pen 300 may correspond to a position of the data transmission interface 420 in the pen insertion hole 410 of the mobile terminal 400, such that the data transmission interface 320 of the stylus pen 300 is connected to the data transmission interface 420 in the pen insertion hole 410. In the same manner, when the stylus pen 300 is inserted into the pen insertion hole 410 of the mobile terminal 400, a position of the charge interface 330 of the stylus pen 300 may correspond to a position of the power supply interface 430 in the pen insertion hole 410 of the mobile terminal 400, such that the charge interface 330 of the stylus pen 300 is connected to the power supply interface 430 in the pen insertion hole 410. The power supply interface 430 in the pen insertion hole 410 of the mobile terminal 400 may be set as a plurality of elastic contact points capable of supplying power. [0072]FIG. 5 is a flowchart of a method of controlling a mobile terminal by using a touch input device, according to an embodiment. [0073]As illustrated in FIG. 5, the method of controlling the mobile terminal by using the touch input device may include: receiving a first touch input by the touch input device on a touch screen of a first mobile terminal (510); transmitting predetermined data associated with a first application that is currently being executed in the first mobile terminal from the first mobile terminal to the touch input device (520); receiving a second touch input by the touch input device on a touch screen of a second mobile terminal (530); and transmitti(String), 相关申请的交叉引用 [0001] 本申请为2016年8月12日提交的国际专利申请PCT/KR2016/008877的第371号,要求2015年8月13日提交的中国专利申请201510497976.9的优先权,其公开内容以引用方式并入本文。 他们的全部。 技术领域 [0002] 本发明涉及一种移动终端和通过使用触摸输入设备控制移动终端的方法,更具体地,涉及通过触摸输入设备向另一个移动终端提供数据的移动终端和控制移动终端的方法 终端。 背景 [0003] 近来,随着电子技术的不断发展,触控技术的应用逐渐普及,通过触控输入控制终端的技术和触控输入设备备受关注。 目前,触控笔是代表性的触控输入装置之一。 [0004] 触控笔可以通过将其笔尖触摸到触摸屏来产生触摸输入,并且可以通过在触摸屏上的触摸来对屏幕执行控制操作。 尤其是触控笔,更适合书写、截屏等操作。 例如,可以通过触控笔在移动终端的触摸屏上指定需要截屏的区域进行截屏,并将截屏存储在移动终端中。 此外,可以通过使用触控笔在备忘录应用中执行书写来随时记录用户的想法。 [0005] 现有技术的移动终端的控制技术仅限于通过触摸输入设备通过触摸输入来控制一个终端。 然而,当存在多个终端时,需要一种能够通过触摸输入在不同终端之间连续执行应用的控制技术。 概括 [0006] 本公开提供一种用于通过触摸输入设备向另一移动终端提供数据并连续执行应用的移动终端,以及控制移动终端的方法。 [0007] 根据实施例,可以通过触摸输入设备在不同终端之间传输数据并连续执行应用程序。 附图的详细说明 [0008] 如图。 图1A是示意性地示出根据实施例的通过触控笔向另一终端提供数据的图。 [0009] 如图。 图1B是图示根据实施例的移动终端的配置的框图。 [0010] 如图。 图2是表示实施方式的触摸输入装置的内部结构的框图。 [0011] 如图。 图3是图示根据实施例的触控笔的配置的图。 [0012] 如图。 图4是示出根据实施例的触控笔插入移动终端的结构的图。 [0013] 如图。 图5是根据实施例的通过使用触摸输入设备控制移动终端的方法的流程图。 [0014] 图 图6至图8示出了根据实施例的通过使用触控笔传输和调用图像。 [0015] 图 图9至图11示出了根据实施例的通过使用触控笔在备忘录应用程序中正在编辑的文档文件的传输和调用。 [0016] 图 图12至图14示出了根据实施例的通过使用触控笔连续执行游戏应用程序。 [0017] 图 图15至图17示出了根据实施例的通过使用触控笔连续执行视频流应用。 [0018] 图 图18至图20示出了根据实施例的通过使用触控笔连续执行网页浏览应用程序。 [0019] 图 图21至图23示出了根据实施例的通过使用触控笔连续执行具有帐户登录功能的游戏应用。 详细说明 [0020]在一个实施例中,一种用于通过触摸输入设备向另一移动终端提供数据的移动终端包括: 触摸屏,用于接收触摸输入设备的触摸输入; 通信模块,被配置为通过与触摸输入设备的通信连接来发送和接收数据; 处理器,被配置为当触摸屏接收到触摸输入设备的第一触摸输入时,向触摸输入设备提供与移动终端中当前正在执行的第一应用相关联的预定数据,使得 预定数据通过触摸输入设备提供给其他移动终端。 [0021] 在一个实施例中,当触摸屏接收到第一触摸输入时,处理器还被配置为确定第一触摸输入的类型并将与第一应用和确定的类型对应的预定数据提供给触摸输入设备。 [0022] 在一个实施例中,当触摸屏接收到第一触摸输入时,处理器还被配置为控制与第一应用相关联的预定数据的列表在触摸屏上的显示,并提供由触摸屏从显示的列表中选择的数据。 用户到触摸输入设备。 [0023] 在一个实施例中,与第一应用相关联的预定数据包括用户在第一应用的执行屏幕上选择的图像或文本、在第一应用中正在编辑的文件和多媒体中的至少一个。 在第一个应用程序中复制的文件。 [0024] 在一个实施例中,当触摸输入设备向另一移动终端输入第二触摸输入时,将提供给触摸输入设备的预定数据从触摸输入设备发送到另一移动终端,发送的预定数据为 提供给由另一个移动终端执行的第二应用程序。 [0025] 在一个实施例中,预定数据包括用于下载用于安装与第一应用相同的第二应用的安装数据的链接信息。 [0026] 在一个实施例中,预定数据包括用于设置与第一应用相同的第二应用的设置数据。 [0027] 在一个实施例中,预定数据包括指示当触摸屏接收到第一触摸输入时第一应用程序的状态的数据,并且通过使用预定数据使第二应用程序的状态与第一应用程序的状态基本相同。 提供给第二个应用程序的数据。 [0028] 在一个实施例中,第一应用程序是网页浏览应用程序,预定数据包括第一应用程序的当前网页的地址,预定数据提供给作为网页浏览应用程序的第二应用程序,以及网页 在第二个应用程序中打开对应于网页地址的网页。 [0029] 在一个实施例中,在第一应用程序具有多媒体再现功能并且当触摸屏接收到第一触摸输入时第一应用程序中的多媒体暂停的情况下,预定数据包括指示多媒体再现状态的数据和 暂停多媒体的再现位置,并将预定数据提供给具有多媒体再现功能的第二应用程序,在第二应用程序的再现位置处以暂停状态开始多媒体的再现。 [0030] 在一个实施例中,当第一应用程序为游戏应用程序,并且当触摸屏接收到第一触摸输入时,第一应用程序中的游戏暂停时,预定数据包括指示游戏进行状态的数据和 游戏暂停位置,将预定数据提供给与第一应用相同的第二应用,在第二应用中的该位置以暂停状态启动游戏。 [0031]在一个实施例中,当第一应用具有账号登录功能,并且当触摸屏接收到第一触摸输入时,在第一应用中登录了账号时,所述预定数据包括表示登录信息的数据。 账号,将预定数据提供给与第一应用相同的第二应用,并在第二应用中登录该账号。 [0032] 在一个实施例中,当触摸屏接收到触摸输入设备的第三触摸输入时,处理器还用于接收从触摸输入设备提供给触摸输入设备的预定数据,并提供从触摸输入设备接收的预定数据。 将触摸输入设备连接到移动终端中的第三应用程序。 [0033] 在一个实施例中,一种通过触摸输入设备控制移动终端的方法包括: 接收触摸输入设备在第一移动终端的触摸屏上的第一触摸输入; 将与当前在第一移动终端中执行的第一应用相关联的预定数据从第一移动终端发送到触摸输入设备; 在第二移动终端的触摸屏上接收触摸输入设备的第二触摸输入; 将存储在触摸输入装置中的预定数据从触摸输入装置发送到第二移动终端。 [0034] 在一个实施例中,从触摸输入设备传输到第二移动终端的预定数据被提供给由第二移动终端执行的第二应用程序。 [0035] 在一个实施例中,预定数据包括用于下载用于安装与第一应用相同的第二应用的安装数据的链接信息。 [0036] 在一个实施例中,预定数据包括用于设置与第一应用相同的第二应用的设置数据。 [0037] 在一个实施例中,预定数据包括指示当触摸屏接收到第一触摸输入时第一应用程序的状态的数据,并且通过使用预定数据使第二应用程序的状态与第一应用程序的状态基本相同。 提供给第二个应用程序的数据。 [0038] 在一个实施例中,当第一移动终端的触摸屏接收到触摸输入设备的第三触摸输入时,第一移动终端向触摸输入设备发送的预定数据被发送给第一移动终端并提供给 第一移动终端中的第三应用程序。 发明方式 [0039] 本发明的优点和特征以及实现它们的方法将从以下结合附图详细描述的实施例中变得更加明显。 然而,应当理解,本发明不限于以下实施例,并且可以在不脱离本发明的范围的情况下进行各种修改。 提供在此阐述的实施例是为了使本公开将彻底和完整,并将本发明的概念充分传达给本领域技术人员。 本发明应由所附权利要求限定。 相同的附图标记自始至终被分配给相同的元件。 [0040]应当理解,当一个区域被称为“连接到”或“耦合到”另一个区域时,它可以直接连接到或耦合到另一个区域,或者可以存在中间区域。 应当理解,诸如“包括”、“包括”和“具有”等术语,当在本文中使用时,指定了所述元素的存在,但不排除一种或多种其他元素的存在或添加。 此外,此处使用的术语“单元”是指诸如FPGA或ASIC之类的软件或硬件组件,并且“单元”执行某些功能。 然而,“单元”不限于软件或硬件。 “单元”可以配置在可寻址存储介质中或配置为再现一个或多个处理器。 因此,例如,“单元”包括诸如软件组件、面向对象软件组件、类组件和任务组件、进程、功能、属性、过程、子例程、程序代码段、驱动程序、固件、微代码等组件。 电路、数据、数据库、数据结构、表格、数组和变量。 组件和“单元”中提供的功能可以与较少数量的组件和“单元”组合,也可以与附加的组件和“单元”分离。 [0041] 下面将结合附图对本发明实施例进行详细说明,以便本领域普通技术人员能够容易地实施本发明实施例。 然而,实施例可以以各种不同的形式实现并且不限于此。 为了清楚地描述附图中的实施例,省略了与描述无关的部分。 [0042] 此处使用的术语是本领域当前广泛使用的那些考虑到发明构思的功能的通用术语,但是这些术语可以根据本领域普通技术人员的意图、先例或本领域的新​​技术而变化。 艺术。 此外,申请人可以选择特定的术语,并且在这种情况下,其详细含义将在发明构思的详细描述中描述。 因此,此处使用的术语不应被理解为简单的名称,而应基于术语的含义和本发明概念的整体描述来理解。 [0043] 如图。 图1A是示意性地示出根据实施例的通过触控笔向另一终端提供数据的图。 [0044] 参考图。 参考图1A,当图像编辑应用程序正在移动终端中执行时 100 在移动终端的触摸屏上输入形状为“C”的触摸手势 100 用手写笔 300 在通过触控笔的操作选择猫图像的状态下 300 , 移动端 100 将包括所选猫图像在内的数据传输到触控笔 300 通过无线通信连接。 包含猫图像的数据存储在触控笔的内存中 300 . 当图像编辑应用程序正在另一个移动终端中执行时 101 在移动终端的触摸屏上输入形状为“P”的触摸手势 101 用手写笔 300 ,其他移动终端 101 从触控笔接收包括猫图像在内的数据 300 . 将接收到的数据提供给正在其他移动终端中执行的图像编辑应用程序 101 ,并且猫图像被粘贴到现有图像上。 [0045] 如图。 图1B是图示根据实施例的移动终端的配置的框图。 [0046] 参考图。 1B、移动终端 100 可能包括触摸屏 110 , 一个通讯模块 120 , 和一个处理器 130 . 如下文参考图1所描述的。 4、移动端 100 还可以包括笔插入孔 410 , 数据传输接口 420 , 和/或电源接口 430 . [0047] 通讯模块 120 被配置为与触摸输入设备形成通信连接,并通过该通信连接发送和接收数据。 通讯模块 120 可以包括有线通信模块 121和/或无线通信模块 122 . [0048] 如下文参考图1所描述的。 4、有线通讯模块 121 可与触控笔形成有线通讯连接 300 在触控笔的状态下 300 插入笔插入孔 410 这样一个金属接触点 321 暴露在笔身上 310 手写笔的 300 连接到数据传输接口 420 在笔插入孔中。 有线通讯模块 121 可以在触摸输入设备通过数据线与移动终端连接的状态下与触摸输入设备形成有线通信连接。 [0049] 当满足无线连接条件时,无线通信模块 122 可自动与触控输入装置形成无线通讯连接。 或者,可以在触摸屏接收到特定类型的触摸输入时形成与触摸输入设备的无线通信连接。 当移动终端的无线通信功能未激活时,无线通信模块 122 可先启动无线通讯功能,然后与触控输入装置形成无线通讯连接。 触摸输入的具体类型基本上可以由系统设置,或者用户可以根据使用习惯直接定义触摸输入的具体类型。 例如,可以将触摸输入的具体类型设置为触摸输入设备触摸触摸屏。 即,当触摸屏被触摸输入设备触摸时,无线通信模块 122 可自动与触控输入装置形成无线通讯连接。 [0050] 无线通讯模块 122 可以激活移动终端的无线通信功能,搜索能够执行无线通信功能的触摸输入设备,并在接收到用户输入的连接命令后与找到的触摸输入设备形成无线通信连接。 [0051] 触摸屏 110 被配置为接收或检测触摸输入设备的触摸输入。 可以通过移动终端或触摸输入设备的操作来设置仅检测系统设置或用户定义的第一至第三触摸输入的触摸输入模式。 [0052] 处理器 130 可以执行触摸输入设备和移动终端之间的数据传输,并且可以控制移动终端中应用程序的执行。 [0053] 当触摸屏接收到触摸输入设备的第一次触摸输入时,处理器 130 向触摸输入设备提供与移动终端当前正在执行的第一应用相关联的预定数据,从而通过触摸输入设备将预定数据提供给另一个移动终端。 处理器前 130 将与第一应用相关联的预定数据传输到触摸输入设备,处理器 130 可以从预定位置或预定接口读取预定数据。 [0054] 第一触摸输入基本可以由系统设置,或者用户可以根据使用习惯直接定义第一触摸输入。 为了有效区分第一触摸输入和一般触摸输入,可以将第一触摸输入设置为触摸手势输入。 例如,第一触摸输入可以被设置为具有“C”形状的触摸手势输入。 在输入第一触摸输入之前,可以设置用于检测第一触摸输入的触摸输入模式。 [0055]根据实施例,与第一应用相关联的预定数据可以包括用户在第一应用的执行屏幕上选择的图像或文本、在第一应用中正在编辑的文件、以及正在编辑的文件中的至少一个。 在第一个应用程序中再现的多媒体文件。 例如,用户在第一应用程序的执行画面上选择的图像或文本可以是与用户在图像编辑应用程序中编辑的图像中选择的区域相对应的图像部分,与区域相对应的图像部分 用户在当前显示的应用程序屏幕上选择的文本部分,以及用户在文档编辑应用程序或网络浏览应用程序中选择的文本部分。 第一应用程序中正在编辑的文件可以是图像编辑应用程序中正在编辑的图像文件、文档编辑应用程序中正在编辑的文本文件以及视频编辑中正在编辑的视频文件 应用。 正在第一应用中再现的多媒体文件可以是正在音频再现应用中再现的音频文件和正在视频再现应用中再现的视频文件。 然而,与第一应用相关联的预定数据不限于上述实施例,并且可以包括各种数据。 根据一个实施例,与第一应用程序相关联的预定数据可以包括用于下载安装数据的链接信息,该安装数据用于在另一个移动终端中安装与第一应用程序相同的第二应用程序,并且可以包括用于设置第二应用程序的设置数据: 与其他移动终端中的第一个应用程序相同。 [0056] 根据一个实施例,与第一应用相关联的预定数据可以根据第一应用的类型预先确定为一致数据。 也就是说,对应于不同应用的预定数据也可以彼此不同。 例如,当移动终端当前正在执行的第一应用程序是文档编辑应用程序时,与第一应用程序关联的预定数据可以被确定为在移动终端的执行屏幕上选择的图像或文本中的至少一个。 用户的第一应用程序,在第一应用程序中正在编辑的文档文件,以及用于在与第一应用程序相同的应用程序中设置文档编辑环境的设置数据。 另外,当当前正在执行的第一应用程序是处于登录状态的网页浏览应用程序时,与第一应用程序关联的预定数据可以被确定为指示与当前网页的地址有关的信息的数据。 第一个应用程序和登录帐户。 然而,与第一应用相关联的预定数据不限于上述示例,并且可以包括各种数据组合。 [0057] 根据一个实施例,当触摸屏接收到第一触摸输入时,处理器 130 可以控制与第一应用相关联的预定数据的列表在触摸屏上的显示,并且将用户从显示的列表中选择的数据提供给触摸输入设备。 [0058] 根据一个实施例,当触摸屏接收到第一触摸输入时,处理器 130 可以确定第一触摸输入的类型并将与第一应用和确定的类型对应的预定数据提供给触摸输入设备。 可以如上所述预先确定对应于第一应用的预定数据。 在与第一应用程序对应的预定数据中,当第一触摸输入为第一类型时,处理器 130 可以将与第一类型对应的第一数据发送给触摸输入设备,当第一触摸输入为第二类型时,处理器 130可以将对应于第二类型的第二数据发送到触摸输入设备。 因此,触摸输入装置可以存储从移动终端发送的多个数据(第一数据和第二数据)。 例如,当移动终端中当前正在执行的第一应用程序是文档编辑应用程序时,用户可以选择是否发送正在第一应用程序中编辑的文档文件,或者是否发送设置数据用于设置 根据触摸输入的类型,与第一个应用程序相同的应用程序的文档编辑环境。 即,当触摸屏接收到第一类型的第一触摸输入时,处理器 130 可以将正在编辑的文档文件发送到触摸输入设备,当触摸屏接收到第二类型的第一触摸输入时,处理器 130 可以将设置数据发送到触摸输入设备。 [0059] 根据一个实施例,当触摸输入设备向另一个移动终端输入第二触摸输入时,提供给触摸输入设备的预定数据可以从触摸输入设备发送到另一个移动终端,并且发送的预定数据 可以提供给由另一个移动终端执行的第二应用程序。 第二应用程序可以是安装在其他移动终端上的应用程序中与第一应用程序相同的应用程序,如下所述。 或者,第二应用程序可以是安装在其他移动终端上的应用程序中能够使用从触摸输入装置接收到的数据的应用程序,或者可以是与第一应用程序不同的应用程序。 [0060] 根据一个实施例,当触摸屏接收到触摸输入设备的第三触摸输入时,处理器 130 可以从触摸输入设备接收提供给触摸输入设备的预定数据,并将从触摸输入设备接收的预定数据提供给移动终端中的第三应用程序 100 . 即移动终端发送的预定数据 100 到触摸输入设备可能会再次传输到不是另一个移动终端,而是同一个移动终端 100 并在第三个应用程序中使用。 第三应用程序可以是安装在移动终端上的应用程序中与第一应用程序相同的应用程序 100 . 或者,第三应用程序可以是安装在移动终端上的应用程序中能够使用从触摸输入装置接收到的数据的应用程序。 100 ,或者可能是与第一个应用程序不同的应用程序。 [0061] 如图。 图2是表示实施方式的触摸输入装置的内部结构的框图。 [0062] 如图所示。 2、触摸输入设备 200 可能包括记忆 210 , 一个通讯模块 220 , 和一个电池 230 . 记忆 210 在触摸输入设备中 200 被配置为存储数据。 触摸输入设备 200 可以进一步包括用于控制其外部的组件的操作的控制按钮,并且可以通过控制按钮执行各种功能,例如设置用于检测第一到第三触摸输入的触摸输入模式的功能。 [0063] 记忆 210 包含在触摸输入设备中 200 可以是非插接式存储设备或插接式存储设备。 通讯模块 220 在触摸输入设备中 200 被配置为通过与移动终端的通信连接发送和接收数据。 通讯模块 220 可以包括有线通信模块 221 和/或无线通信模块 222 . 无线通讯模块 222 可以通过任何无线连接与另一设备形成无线通信连接。 例如,无线通信模块 222可以通过Wi-Fi连接、蓝牙(BT)连接、近场通信(NFC)连接或触摸屏通信(HOTKNOT)连接与另一设备形成无线通信连接。 触摸输入设备 200 可通过有线通信模块与移动终端交换数据 221 或无线通讯模块 222 . [0064] 根据一个实施例,触摸输入设备 200 可以将从第一移动终端接收到的数据提供给第二移动终端。 具体地,当触摸输入设备向第一移动终端输入第一触摸输入时 200 可以从第一移动终端接收与在第一移动终端中执行的第一应用相关联的预定数据,并将其存储在触摸输入设备中 200 ,并且作为第二次触摸输入由触摸输入设备输入到第二移动终端 200 ,可以将接收到的预定数据提供给第二移动终端。 [0065] 根据一个实施例,触摸输入设备 200 可能是手写笔 300 如参考图1所描述的。 3.然而,触摸输入设备 200 不限于此,并且可以是用于产生触摸输入的各种类型的装置。 [0066] 如图。 图3是图示根据实施例的触控笔的配置的示意图。 [0067] 如图所示。 3、触控笔 300 可能包括笔身 310 , 数据传输接口 320 , 一个充电接口 330 , 和一个控制按钮 340 . 如上所述,触控笔的各种功能 300 可以通过控制按钮执行 340 . 为了顺利进行触控笔之间的通讯连接 300 以及移动终端、有线通信模块中的数据线和控制线 221 可集成在数据传输接口中 320 设置在笔身上 310 . [0068] 根据一个实施例,如图所示。 3、数据传输接口 320 设置在笔身上 310 可以是多个金属接触点 321 暴露在笔身上 310 . 但是,数据传输接口的配置 320 不限于金属接触点 321 如图所示。 3、可能是另一种金属连接器。 金属接触点 321 可以通过将金属板插入笔身来形成 310 ,在笔身喷涂导电材料 310 ,或将导电材料连接到笔身 310 . [0069] 触控笔 300 可能包括电池 230 从而为其供电。 为了给电池充电 230 , 触控笔 300 还可以包括用于给电池充电的充电模块 230 用从外部获得的力量。 充电模块可以通过充电接口进行充电操作 330 或数据传输接口 320 . 收费接口 330 可以设置在笔身上 310 . 为了方便充电操作,防止随意接触充电接口 330 ,多个内陷金属接触点 331 可设置在笔身上 310 . [0070] 如图。 图4是示出根据实施例的触控笔插入移动终端的结构的图。 [0071] 移动终端 400 根据实施例可以包括笔插入孔 410 用于插入触控笔 300 . 另外,一个数据传输接口 420 和一个电源接口 430 可在笔插入孔中设置 410 . 如图所示。 4、当手写笔 300 插入笔插入孔 410 移动终端的 400 ,数据传输接口的位置 320 手写笔的 300 可以对应数据传输接口的位置 420 在笔插入孔中 410移动终端的 400 , 这样数据传输接口 320 手写笔的 300 连接到数据传输接口 420 在笔插入孔中 410 . 以同样的方式,当触控笔 300 插入笔插入孔 410 移动终端的 400 ,充电接口的位置 330 手写笔的 300 可以对应电源接口的位置 430 在笔插入孔中 410 移动终端的 400 , 这样充电接口 330 手写笔的 300 连接到电源接口 430 在笔插入孔中 410 . 电源接口 430 在笔插入孔中 410 移动终端的 400 可以设置为多个能够供电的弹性触点。 [0072] 如图。 图5是根据实施例的通过使用触摸输入设备控制移动终端的方法的流程图。 [0073] 如图所示。 参照图5,通过触摸输入设备控制移动终端的方法可以包括:接收触摸输入设备在第一移动终端的触摸屏上的第一触摸输入( 510 ); 将与当前在第一移动终端中执行的第一应用相关联的预定数据从第一移动终端发送到触摸输入设备( 520 ); 在第二移动终端的触摸屏上接收触摸输入设备的第二触摸输入( 530 ); 将存储在触摸输入装置中的预定数据从触摸输入装置发送到第二移动终端( 540 )。 [0074] 运行中 510 ,第一移动终端接收触摸输入设备在第一移动终端的触摸屏上的第一触摸输入。 运行中 520 ,第一移动终端响应于接收到第一触摸输入,通过与触摸输入设备的通信连接将与第一移动终端中当前正在执行的第一应用程序相关联的预定数据发送到触摸输入设备。 [0075] 根据实施例,当触摸屏接收到第一触摸输入时,第一移动终端可以确定第一触摸输入的类型并将与第一应用和确定的类型对应的预定数据提供给触摸输入设备。 如上所述,可以根据第一应用的类型预先确定对应于第一应用的预定数据。 例如,在第一应用对应的预定数据中,当第一触摸输入为第一类型时,第一移动终端可以向触摸输入设备发送第一类型对应的第一数据,当第一触摸输入为 第二类,第一移动终端可以将第二类对应的第二数据发送给触摸输入设备。 因此,触摸输入装置可以存储从第一移动终端发送的多个数据(第一数据和第二数据)。 [0076] 运营中 510 和 520 , 与移动端的操作相同 100 和触摸输入设备 200 参考图1和2描述。 可以由第一移动终端和触摸输入设备执行图1B至图4。 [0077] 运行中 530 ,第二移动终端接收触摸输入设备在第二移动终端的触摸屏上的第二触摸输入。 [0078] 第二触摸输入可以基本由系统设置,或者用户可以根据使用习惯直接定义第二触摸输入。 为了有效地区分第二触摸输入与一般触摸输入,可以将第二触摸输入设置为触摸手势输入。 例如,可以将第二触摸输入设置为具有“P”形状的触摸手势输入。 在向触摸屏输入第二触摸输入之前,可以在移动终端中设置用于检测第二触摸输入的触摸输入模式。 [0079] 运行中 540,将存储在触摸输入设备中的预定数据从触摸输入设备发送到第二移动终端。 也就是说,第二移动终端响应于第二触摸输入的接收,通过与触摸输入装置的通信连接从触摸输入装置接收存储在触摸输入装置中的预定数据。 [0080] 根据实施例,当触摸屏接收到第二触摸输入时,第二移动终端可以确定第二触摸输入的类型,并从触摸输入设备接收与确定的类型对应的预定数据。 例如,在从第一移动终端发送的多个数据(第一数据和第二数据)被存储在触摸输入设备中的情况下,第二移动终端可以从存储在触摸输入设备中的数据中接收第一数据。 当第二触摸输入为第三类型时,触摸输入设备,并且当第二触摸输入为第四类型时,可以从存储在触摸输入设备中的数据中接收第二数据。 [0081] 根据一个实施例,当触摸屏接收到第二触摸输入时,第二移动终端可以接收最新存储在触摸输入设备中并且尚未发送到移动终端的预定数据。 在这种情况下,通过多次输入第二触摸输入,第二移动终端可以在不同时刻按照存储时间的倒序接收存储在触摸输入设备中的预定数据。 可以从触摸输入装置的存储器中删除存储在触摸输入装置的存储器中的数据中已经发送到移动终端的数据。 [0082] 运行中 540 ,可以将已经从触摸输入设备发送到第二移动终端的预定数据提供给由第二移动终端执行的第二应用程序。 第二应用程序可以是安装在第二移动终端上的应用程序中与第一应用程序相同的应用程序。 或者,第二应用程序可以是安装在第二移动终端上的应用程序中能够使用从触摸输入装置接收到的数据的应用程序,或者可以是与第一应用程序不同的应用程序。 或者,第二应用程序可以是不同于第一应用程序但能够通过使用从触摸输入装置接收到的数据来执行预定处理的应用程序。 例如,当从触摸输入设备接收到的数据是包括用户选择的图像的数据时,第二应用程序可以是能够像图像编辑应用程序一样粘贴相应图像的应用程序,并且当从触摸接收到的数据时 输入设备是文档文件,第二应用程序可以是能够打开和编辑对应的文档文件的文档编辑应用程序或能够打开和查看对应的文档文件的文档查看器应用程序。 [0083] 根据实施例,通过触摸输入装置从第一移动终端发送到第二移动终端的预定数据可以包括指示当触摸屏接收到第一触摸输入时第一应用的状态的数据,以及 通过使用提供给第二应用的预定数据,可以使第二应用与第一应用的状态基本相同。 [0084] 根据实施例,通过触摸输入装置从第一移动终端发送到第二移动终端的预定数据可以包括用于下载用于安装与第一应用相同的第二应用的安装数据的链接信息,以及第二应用 可以通过安装数据安装在第二移动终端上。 [0085]根据一个实施例,通过触摸输入设备从第一移动终端发送到第二移动终端的预定数据可以包括用于设置与第一应用相同的第二应用的设置数据,并且第二应用可以设置在 通过将设置数据提供给第二应用程序,以与第一应用程序相同的方式。 [0086] 根据一个实施例,在预定数据从第一移动终端发送到触摸输入设备之后,当触摸输入设备的第三触摸输入被第一移动终端的触摸屏接收到时,从第一移动终端发送的预定数据 触摸输入设备的移动终端可以被传输到第一移动终端并提供给第一移动终端中的第三应用程序。 [0087] 根据一个实施例,第一应用可以是网页浏览应用,第一移动终端通过触摸输入设备向第二移动终端提供的预定数据可以包括第一应用的当前网页的地址。 可以将预定数据提供给作为网页浏览应用的第二应用,并且可以在第二应用中打开与当前网页的地址对应的网页。 [0088] 根据一个实施例,在第一应用具有多媒体再现功能并且当触摸屏接收到第一触摸输入时第一应用中的多媒体暂停的情况下,从第一移动终端向第二移动终端提供预定数据 通过触摸输入装置可以包括指示多媒体的再现状态和多媒体被暂停的再现位置的数据。 可以将预定数据提供给具有多媒体再现功能的第二应用程序,并且可以在处于再现位置的暂停状态的第二应用程序中开始多媒体的再现。 [0089] 根据一个实施例,在第一应用是游戏应用并且当触摸屏接收到第一触摸输入时在第一应用中暂停游戏的情况下,从第一移动终端向第二移动终端提供预定数据 通过触摸输入设备可以包括指示游戏的进展状态和游戏暂停的位置的数据。 可以将预定数据提供给与第一应用程序相同的第二应用程序,并且可以在处于上述位置的暂停状态的第二应用程序中开始游戏。 [0090] 根据一个实施例,当第一应用程序具有账号登录功能,并且当触摸屏接收到第一触摸输入时,在第一应用程序中登录了账号时,第一移动终端通过以下方式向第二移动终端提供预定数据。 触摸输入设备可以包括指示关于已登录帐户的信息的数据,并且可以通过向与第一应用相同的第二应用提供预定数据来登录第二应用中的帐户。 [0091] 根据实施例,第一应用可以具有多媒体流功能,并且从第一移动终端通过触摸输入设备提供给第二移动终端的预定数据可以包括在第一应用中流的多媒体的网络地址 . 可以将预定数据提供给与第一应用相同的第二应用,并且可以在第二应用中流式传输与网络地址对应的多媒体。 [0092] 运营中 530 和 540 , 操作与移动端相同 100 和触摸输入设备 200 参考图1和2描述。 可以由第二移动终端和触摸输入设备来执行图1B至图4的操作。 [0093]根据一个实施例,通过使用触摸输入设备控制移动终端的方法还可以包括:当触摸屏接收到第二触摸输入时,在第二移动终端中没有执行第二应用程序的情况下,执行 在将从触摸输入设备接收到的数据提供给第二应用程序之前,第二应用程序。 [0094] 将参考图1至图3描述与通过触摸输入设备在第一移动终端和第二移动终端之间传输数据并连续执行应用的方法有关的具体实施例。 6 至 23 日。 [0095] 将参照图1至图3描述通过触摸输入装置从第一移动终端向第二移动终端的第二应用提供与第一应用相关联的预定数据的情况。 参照图6至图23,但本发明不限于此。 例如,在将与第一应用相关联的预定数据提供给触摸输入设备之后,可以将与第一应用相关联的预定数据从触摸输入设备提供给安装在第一移动终端上的第三应用。 [0096] 图 图6至图8说明了使用触控笔传输和调用图像 300 ,根据一个实施例。 [0097] 参考图。 参照图6,在第一移动终端中执行图像编辑应用程序 100 ,通过手写笔的操作选择猫图像 300 ,并通过触控笔在触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将猫图像传输到触控笔 300 通过无线通信连接。 [0098] 参考图。 参照图7,在第二移动终端中执行图像编辑应用,图像编辑应用中存在现有的椅子图像。 [0099] 参考图。 如图8所示,触控笔在第二移动终端的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 300 ,第二移动终端接收到手写笔中存储的猫图片 300 来自触控笔 300 通过无线通信连接。 将接收到的数据提供给第二移动终端中正在执行的图像编辑应用程序,并将猫图像粘贴到图像编辑应用程序中的现有桌面图像上。 [0100] 参考图。 参照图6至图8,在一个实施例中,用户选择的图像可以存储在触控笔中 300 实时,图像可以在另一个移动终端或同一个移动终端中继续使用。 [0101] 图 图9至图11示出了使用触控笔在备忘录应用程序中正在编辑的文档文件的传输和调用 300 ,根据一个实施例。 [0102] 参考图。 9、在第一移动终端的备忘录应用中输入文字“TODAY'S WEATHER”后 100 ,触控笔在弹出式菜单中选择用于检测第一触摸输入的触摸输入模式 300 . [0103] 参考图。 参照图10,通过触控笔在第一移动终端的触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 ,并显示与备忘录应用程序相关联的预定数据列表,以便选择传输到触控笔的数据 300 . 该列表包括两个项目“SAVE TRACK”和“SAVE RESULT”。 在这两项中,“SAVE TRACK”表示发送用于设置备忘录应用的文档编辑环境的设置数据,“SAVE RESULT”表示发送正在备忘录应用中编辑的文档文件。 在与备忘录应用关联的预定数据列表中,用户选择“保存结果”,第一移动终端 100 将备忘录应用程序中正在编辑的文档文件传输到触控笔 300 通过无线通信连接。 [0104]参考图。 如图11所示,触控笔在第二移动终端主界面的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 300 ,以及第二个移动终端 101 接收存储在触控笔中的文档文件 300 通过无线通信连接。 由于备忘录应用不在第二移动终端中执行 101 当在第二移动终端输入第二触摸输入时 101 ,第二个移动终端 101 首先执行备忘录应用程序,然后加载从手写笔接收到的文档文件 300 在备忘录应用程序中。 [0105] 参考图。 参照图9至图11,在一个实施例中,可以将正在编辑的文档文件传送到触控笔 300 ,并且可以在另一个移动终端或同一移动终端中执行连续文档编辑。 [0106] 图 图12至图14示出了通过使用触控笔连续执行游戏应用程序 300 ,根据一个实施例。 [0107] 参考图。 12、在第一移动终端正在执行的游戏应用中暂停游戏 100 ,并通过触控笔在触摸屏上输入形状为“N”的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将游戏的进度状态和游戏的暂停位置传送到触控笔 300 通过无线通信连接。 [0108] 参考图。 参照图13,在第二移动终端的主界面中的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 接收指示游戏进度状态和游戏暂停位置的数据,存储在触控笔中 300 , 来自触控笔 300 通过无线通信连接。 [0109] 参考图。 14、游戏应用在第二移动终端中执行 101 ,从手写笔接收的数据 300 提供给游戏应用程序,在第一移动终端中游戏暂停的位置以暂停状态启动游戏。 用户可以在游戏应用的界面中选择“继续玩”以继续玩游戏。 [0110] 参考图。 参照图12至图14,在一个实施例中,用户可以通过触控笔在另一个终端或同一终端继续玩暂停的游戏 300 . [0111] 图 图15到17示出了通过使用触控笔连续执行视频流应用 300 ,根据一个实施例。 [0112] 参考图。 15、在第一移动终端的视频流应用中暂停视频流 100 ,并通过触控笔在触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 . 第一个移动终端 100 将指示视频的再现状态和视频的暂停再现位置的数据发送到触控笔 300 通过无线通信连接以及正在流式传输的视频的网络地址。 [0113] 参考图。 参照图16,在第二移动终端的主界面中的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 从触控笔接收 300 、指示正在流式传输的多媒体的网络地址、视频的再现状态和视频的暂停位置的数据,这些数据存储在触控笔中 300 ,通过无线通信连接。 [0114] 参考图。 参照图17,由于在第二移动终端中输入第二触摸输入时不执行视频流应用 101 ,首先在第二移动终端中执行视频流应用。 第二个移动终端 101 提供从触控笔接收的数据 300到视频流应用程序。 对应于网络地址的多媒体基于提供的数据在视频流应用中被流化,并且多媒体的再现在再现位置处以暂停状态开始。 为了继续继续播放视频,用户可以在视频流应用的界面中点击播放重启按钮。 [0115] 参考图。 参照图15至图17,在一个实施例中,用户可以通过使用触控笔在另一个移动终端或同一移动终端中继续流式传输视频 300 . [0116] 图 图18至图20示出了通过使用触控笔连续执行网页浏览应用程序 300 ,根据一个实施例。 [0117] 参考图。 参照图18,在第一移动终端上显示网页浏览应用的当前网页 100 ,并通过触控笔在触摸屏上输入形状为“C”的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将当前网页的地址传送到手写笔 300 通过无线通信连接。 [0118] 参考图。 参照图19,在第二移动终端的主界面中的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 接收存储在手写笔中的网页地址 300 通过无线通信连接。 [0119] 参考图。 参照图20,由于在第二移动终端中输入第二触摸输入时不执行网页浏览应用 101 ,网页浏览应用程序首先在第二移动终端中执行 101 . 第二个移动终端 101 提供从触控笔接收的数据 300 向执行的网页浏览应用程序,在网页浏览应用程序中打开与当前网页的地址对应的网页。 [0120] 参考图。 参照图18至图20,在一个实施例中,可以通过使用触控笔继续使用网络浏览应用的当前网页 300 . [0121] 图 图21至23示出了通过使用触控笔连续执行具有帐户登录功能的游戏应用程序 300 ,根据一个实施例。 [0122] 参考图。 参照图21,在第一移动终端中执行的游戏应用中暂停游戏 100 处于登录状态,触控笔在触摸屏上输入“O”字形的触摸手势输入(第一触摸输入) 300 . 因此,第一个移动终端 100 将表示登录帐户信息的数据和表示游戏进度状态和游戏暂停位置的数据传输到触控笔 300 通过无线通信连接。 [0123] 参考图。 如图22所示,在第二移动终端主界面的触摸屏上输入形状为“P”的触摸手势输入(第二触摸输入) 101 用手写笔 300 ,以及第二个移动终端 101 接收指示登录帐户信息的数据和指示游戏进度状态和游戏暂停位置的数据,这些数据存储在触控笔中 300 ,通过无线通信连接。 [0124] 参考图。 23、游戏应用在第二移动终端中执行 101 ,并将接收到的数据提供给游戏应用程序。 根据提供的数据,根据登录账户的信息执行登录,在游戏应用中以暂停状态启动反映进度状态的游戏。 [0125] 参考图。 参照图21至图23,在一个实施例中,在第一移动终端暂停游戏后 100 ,用户可以在第二移动终端继续玩暂停的游戏 101 通过使用触控笔 300 ,无需额外的操作,如账户登录和存储数据的加载。 [0126]图 图6至图23仅示出了通过使用触控笔连续执行移动终端的应用的示例 300 根据实施例。 比如手写笔之间的通讯连接 300 移动终端不限于无线通信连接,也可以是有线通信连接。 有线通信连接可以通过触控笔之间的数据线形成 300 和移动终端。 此外,第一触摸输入和第二触摸输入不限于具有“C”和“P”形状的触摸手势输入,还可以是其他类型的触摸手势输入或其他类型的触摸输入。 根据一个实施例,第一触摸输入和第二触摸输入不是触摸屏上的触摸输入,而是对应于触摸输入设备中形成的触摸按钮的触摸或触摸中形成的控制按钮的按下。 输入设备。 根据另一实施例,第一触摸输入和第二触摸输入可以对应于对显示在触摸屏上的预定图标的选择。 可以理解的是,虽然已经将应用的执行示例描述为在两个移动终端中执行,但是本发明不限于此,可以在更多的终端中通过触摸输入设备来实现应用的持续执行。 或同一个终端。 [0127] 应当理解,尽管此处可以使用术语“第一”、“第二”等来描述不同的组件,但是这些组件不应受这些术语的限制。 这些组件仅用于区分一个组件与另一个组件。 例如,第一组件可以被命名为第二组件。 类似地,在不脱离实施例的范围的情况下,可以将第二组件命名为第一组件。 [0128] 应当理解,当组件或层被称为“在”、“连接到”、“耦合到”或“接触”另一个组件或另一层时,它可以直接位于、连接到、耦合到 ,或接触其他组件或其他层,或可能存在居间的组件或层。 相反,应当理解,当组件或层被称为“直接在”、“直接连接到”、“直接耦合”或“直接接触”另一个组件或另一层时,没有中间组件或 层不存在。 [0129] 应当理解,根据实施例的通过触摸输入设备控制移动终端的方法也可以体现为计算机可读记录介质上的计算机可读代码。 计算机可读记录介质可以是能够存储可由计算机系统读取的数据的任何数据存储设备。 计算机可读记录介质可以是只读存储器(ROM)、随机存取存储器(RAM)、CD-ROM、磁带、软盘、光数据存储设备和载体(通过有线传输数据 或无线传输线)。 计算机可读记录介质还可以分布在网络连接的计算机系统上,使得计算机可读代码以分布式方式存储和执行。 此外,在本发明的范围内,具有本发明所属领域的普通技术的普通程序员可以容易地推断出用于实现本发明的功能程序、代码和代码段。 [0130] 尽管已经参照其特定实施例示出和描述了本公开,但是应当理解,本领域的技术人员可以在形式和细节上做出各种改变而不背离由所附所定义的本发明的精神和范围 索赔。 [0131] 尽管已经参照附图具体示出和描述了本发明,但是应当理解,本领域普通技术人员将认识到可以以其他特定形式实践一个实施例而不背离其精神或基本特征 . 因此,应当理解,上述实施例在所有方面都是说明性的而非限制性的。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.802 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.803 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106445199A(String), KR1020170020286A(String), US10702769B2(String), US20190083881A1(String), WO2017026835A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.956 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106445199A(String), KR1020170020286A(String), US10702769B2(String), US20190083881A1(String), WO2017026835A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:18.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10702769B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.009 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106445199A(String), KR1020170020286A(String), US10702769B2(String), US20190083881A1(String), WO2017026835A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271680(Integer), CN106445199A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.062 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271680(Integer), KR1020170020286A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.096 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.097 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271680(Integer), US10702769B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.131 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271680(Integer), US20190083881A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.166 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271680(Integer), WO2017026835A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.201 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10702769B2(String), US10702769B2(String), 1594051200(Integer), 271680(Integer), 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG TIANJIN MOBILE DEVELOPMENT CENTER(String), 三星电子株式会社(String), 天津三星通信技术研究有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.281 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.282 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.314 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.315 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.315 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186011(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.348 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186011(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SAMSUNG TIANJIN MOBILE DEVELOPMENT CENTER(String), 天津三星通信技术研究有限公司(String), 0(Integer), 1681976179(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186011(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75863(Integer), 2(Integer), 186011(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.487 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.505 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.522 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.523 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75863(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.540 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.557 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.557 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.557 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.592 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.593 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.610 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.611 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.764 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186011(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:19.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160112578A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.143 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method for automatic network search of mobile terminal and mobile terminal(String), 移动终端自动寻网方法及移动终端(String), US20160112578A1(String), Disclosed are an automatic network search method for a mobile terminal and a mobile terminal, and relates to the field of mobile communication. The method includes: it is judged whether there is a subscribed operator to which a user identification card is associated or not in network operators at a roaming destination when the mobile terminal is in a roaming state; the search network is performed automatically according to a priority of a network mode supported by the user identification card and the network of the subscribed operator if there is the subscribed operator with which the user identification card is associated; and the search network is performed automatically according to the priority of the network mode supported by the user identification card if there is no subscribed operator with the user identification card is associated. By the disclosure, a network required by a user may be automatically found simply and rapidly, and the mobile terminal may automatically roam, so that user experiences are improved.(String), 本发明公开了一种移动终端自动寻网方法及移动终端,涉及移动通信领域。 该方法包括:当移动终端处于漫游状态时,判断漫游目的地的网络运营商中是否存在用户识别卡所关联的签约运营商。 如果有用户识别卡关联的签约运营商,则根据用户身份证支持的网络模式和签约运营商的网络的优先级自动进行寻网。 如果没有与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级自动进行搜索网络。 通过本发明,可以简单快速地自动找到用户所需的网络,实现移动终端自动漫游,提高用户体验。(String), US14/783187(String), 1376236800(Integer), US20160112578A1(String), 1461168000(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080214240A1 | US20090186651A1 | US20100075711A1 | US20100099412A1 | US20110300844A1(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.177 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.178 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186012(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.325 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.326 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\30d38baa536f479e9dd051484b25e271.png(String), 186012(Integer), 30d38baa536f479e9dd051484b25e271.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.378 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method for automatic network search of mobile terminal and mobile terminal(String), 移动终端自动寻网方法及移动终端(String), US20160112578A1(String), Disclosed are an automatic network search method for a mobile terminal and a mobile terminal, and relates to the field of mobile communication. The method includes: it is judged whether there is a subscribed operator to which a user identification card is associated or not in network operators at a roaming destination when the mobile terminal is in a roaming state; the search network is performed automatically according to a priority of a network mode supported by the user identification card and the network of the subscribed operator if there is the subscribed operator with which the user identification card is associated; and the search network is performed automatically according to the priority of the network mode supported by the user identification card if there is no subscribed operator with the user identification card is associated. By the disclosure, a network required by a user may be automatically found simply and rapidly, and the mobile terminal may automatically roam, so that user experiences are improved.(String), 本发明公开了一种移动终端自动寻网方法及移动终端,涉及移动通信领域。 该方法包括:当移动终端处于漫游状态时,判断漫游目的地的网络运营商中是否存在用户识别卡所关联的签约运营商。 如果有用户识别卡关联的签约运营商,则根据用户身份证支持的网络模式和签约运营商的网络的优先级自动进行寻网。 如果没有与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级自动进行搜索网络。 通过本发明,可以简单快速地自动找到用户所需的网络,实现移动终端自动漫游,提高用户体验。(String), US14/783187(String), 1376236800(Integer), US20160112578A1(String), 1461168000(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 5(Integer), US20080214240A1 | US20090186651A1 | US20100075711A1 | US20100099412A1 | US20110300844A1(String), \20230420\30d38baa536f479e9dd051484b25e271.png(String), 15(Integer), 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.448 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 1. An automatic network search method for a mobile terminal, comprising:when the mobile terminal is in a roaming state, judging whether there is, in a plurality of network operators at a roaming destination, a subscribed operator with which a user identification card is associated;based on that there is the subscribed operator with which the user identification card is associated, automatically searching for a network according to a priority of network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator; andbased on that there is no subscribed operator with which the user identification card is associated, automatically searching for a network according to the priority of the network mode supported by the user identification card.(String), 1.根据权利要求2所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 2. The method according to claim 1, wherein before judging whether there is, in the plurality of network operators at the roaming destination, the subscribed operator with which the user identification card is associated when the mobile terminal is in the roaming state, the method further comprises:judging whether the mobile terminal is in the roaming state or not; andbased on that the mobile terminal is not in the roaming state, automatically searching for the network according to a network search manner set by the mobile terminal.(String), 12.根据权利要求3所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 3. The method according to claim 2, wherein before judging whether the mobile terminal is in the roaming state or not, the method further comprises:detecting one or more card slots of the mobile terminal in real time;reading information about an operator which issues the user identification card and information about a network mode supported by the user identification card when it is detected that the user identification card is inserted into one of the one or more card slots; andstoring the information about the operator which issues the user identification card and information about the network mode supported by the user identification card.(String), 13.根据权利要求4所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 4. The method according to claim 3, wherein judging whether the mobile terminal is in the roaming state or not comprises:searching, according to the network mode, for a network in an area where the mobile terminal is located to obtain at least one parameter of the network in the area where the mobile terminal is located; andcomparing the at least one parameter of the network in the area where the mobile terminal is located with at least one network parameter in the information about the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not.(String), 14.根据权利要求5所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 5. The method according to claim 4, wherein searching, according to the network mode, for the network in the area where the mobile terminal is located to obtain the at least one parameter of the network in the area where the mobile terminal is located comprises:when the user identification card supports multiple network modes, sequentially searching for networks corresponding to the corresponding network modes according to priorities of the multiple network modes until the at least one parameter of the network in the area where the mobile terminal is located is obtained.(String), 15.根据权利要求6所述的方法,还包括:当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。多个用户识别卡对应的多个卡槽的优先级。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 6. The method according to claim 5, wherein comparing the at least one parameter of network in the area where the mobile terminal is located with the at least one network parameter in the information of the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not comprises:based on that the at least one parameter of the network in the area where the mobile terminal is located is matched with the at least one network parameter in the information of the operator which issues the user identification card, determining that the mobile terminal is in a non-roaming state, otherwise determining that the mobile terminal is in the roaming state.(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 7. The method according to claim 1, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 8. A mobile terminal for searching for a network automatically, comprising:a subscribed operator determination component configured to, when the mobile terminal is in a roaming state, judge whether there is, in a plurality of network operators at a roaming destination, a subscribed operator to which a user identification card is associated; anda network search component configured to, when there is the subscribed operator with which the user identification card is associated, automatically search for a network according to a priority of a network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator, and automatically search for the network according to the priority of the network mode supported by the user identification card when there is no subscribed operator to which the user identification card is associated.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 9. The mobile terminal according to claim 8, further comprising:a roaming determination component configured to judge whether the mobile terminal is in the roaming state or not to enable the network search component to automatically search for the network according to a network search manner set by the mobile terminal under the condition that the mobile terminal is not in the roaming state.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 10. The mobile terminal according to claim 9, further comprising:a detection component configured to detect one or more card slots of the mobile terminal in real time;an in-card information acquisition component configured to, when it is detected that the user identification card is inserted into one of the one or more card slots, read information about an operator which issues the user identification card and information about the network mode supported by the User identification card; anda storage component configured to store the information about the operator which issues the user identification card and information about the supported network mode.(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 11. The method according to claim 2, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 10(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 12. The method according to claim 3, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 11(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 13. The method according to claim 4, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 12(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 14. The method according to claim 5, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 13(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186012(Integer), 15. The method according to claim 6, further comprising:when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards.(String), 1(Integer), 14(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.755 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.773 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.774 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186012(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of mobile communication, and in particular to an automatic network search method for a mobile terminal and a related mobile terminal. BACKGROUND [0002]Mobile technology changes life, mobile terminals spread all over the world at present, and one or more operators may operate mobile networks in many countries and areas in the world. Due to upgrading of network systems or regulation of national policies in different times, each operator may operate networks of many systems, and issued mobile telephone cards may be developed from single-mode cards to dual-mode cards and then to multimode cards in the future. In order to compete for customers and solve the problem of frequent mobile phone changing without card (number) changing of users, terminals of the operators support double card slots instead of single card slots, and may be developed to support multiple card slots in the future. [0003]Along with increasing population movement, a terminal must meet requirements of many mobile users on automatic roaming as much as possible, which promotes continuous upgrading of card slots in the terminal from support to single-mode cards to dual-mode cards and then to multimode cards. Diversity of network systems and complexity in mobile terminals cause variability of network search of the mobile terminals, and how to enable a terminal to rapidly and accurately find a network required by a user is a complicated problem. [0004]At present, there are two methods for solving the problem: [0005]1: when a mobile terminal roams to an area of another network operator, it is necessary for a user to search for and switch a network in a manual manner, such a manner has a high requirement on professional knowledge of the user and requires the user to find the network by many operating steps and then switch the network, and if the user does not perform manual searching and complete switching, the mobile terminal may fail to roam, which may cause influence on normal occurrence of a service of the user as well as poor user experiences; and [0006]2: the terminal automatically and randomly searches the whole frequency band for the network after being started, and in such a manner, intentionality is poor and the network is usually searched for a longer time, which wastes time of the user and is unfavourable for life of a battery of the terminal. SUMMARY [0007]The embodiment of the disclosure provides an automatic network search method for a mobile terminal and a mobile terminal, which may better solve a problem about automatic and rapid network search of the mobile terminal. [0008]According to one aspect of the embodiment of the disclosure, an automatic network search method for a mobile terminal is provided, which includes: [0009]when the mobile terminal is in a roaming state, judging whether there is, in a plurality of network operators at a roaming destination, a subscribed operator with which a user identification card is associated; [0010]based on that there is the subscribed operator with which the user identification card is associated, automatically searching for a network according to a priority of network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator; and [0011]based on that there is no subscribed operator with which the user identification card is associated, automatically searching for a network according to the priority of the network mode supported by the user identification card. [0012]Preferably, before judging whether there is, in the plurality of network operators at the roaming destination, the subscribed operator with which the user identification card is associated when the mobile terminal is in the roaming state, the method further comprises: judging whether the mobile terminal is in the roaming state or not; and based on that the mobile terminal is not in the roaming state, automatically searching for the network according to a network search manner set by the mobile terminal. [0013]Preferably, before judging whether the mobile terminal is in the roaming state or not, the method further comprises: detecting one or more card slots of the mobile terminal in real time; reading information about an operator which issues the user identification card and information about a network mode supported by the user identification card when it is detected that the user identification card is inserted into one of the one or more card slots; and storing the information about the operator which issues the user identification card and information about the network mode supported by the user identification card. [0014]Preferably, judging whether the mobile terminal is in the roaming state or not comprises: searching, according to the network mode, for a network in an area where the mobile terminal is located to obtain at least one parameter of the network in the area where the mobile terminal is located; and comparing the at least one parameter of the network in the area where the mobile terminal is located with at least one network parameter in the information about the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not. [0015]Preferably, searching, according to the network mode, for the network in the area where the mobile terminal is located to obtain the at least one parameter of the network in the area where the mobile terminal is located comprises: when the user identification card supports multiple network modes, sequentially searching for networks corresponding to the corresponding network modes according to priorities of the multiple network modes until the at least one parameter of the network in the area where the mobile terminal is located is obtained. [0016]Preferably, comparing the at least one parameter of network in the area where the mobile terminal is located with the at least one network parameter in the information of the operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not comprises: based on that the at least one parameter of the network in the area where the mobile terminal is located is matched with the at least one network parameter in the information of the operator which issues the user identification card, determining that the mobile terminal is in a non-roaming state, otherwise determining that the mobile terminal is in the roaming state. [0017]Preferably, the method further includes: [0018]when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enabling a user identification card inserted in a card slot with a higher priority to use the conflicting hardware resources and/or network resources according to priorities of the multiple card slots corresponding to the multiple user identification cards. [0019]According to the other aspect of the embodiment of the disclosure, a mobile terminal for searching a network automatically is provided, which includes: [0020]a subscribed operator determination component configured to, when the mobile terminal is in a roaming state, judge whether there is, in a plurality of network operators at a roaming destination, a subscribed operator to which a user identification card is associated ; and a network search component configured to, when there is the subscribed operator with which the user identification card is associated, automatically search for a network according to a priority of a network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator, and automatically search for the network according to the priority of the network mode supported by the user identification card when there is no subscribed operator to which the user identification card is associated. [0021]Preferably, the mobile terminal further includes: [0022]a roaming determination component configured to judge whether the mobile terminal is in the roaming state or not to enable the network search component to automatically search for the network according to a network search manner set by the mobile terminal under the condition that the mobile terminal is not in the roaming state. [0023]Preferably, the mobile terminal further includes: [0024]a detection component configured to detect one or more card slots of the mobile terminal in real time; [0025]an in-card information acquisition component configured to, when it is detected that the user identification card is inserted into one of the one or more card slots, read information about an operator which issues the user identification card and information about the network mode supported by the User identification card; and [0026]a storage component configured to store the information about the operator which issues the user identification card and information about the supported network mode. [0027]Compared with the related art, the embodiment of the disclosure has beneficial effects as follows: [0028]by the embodiment of the disclosure, a network required by a user may be automatically found simply and rapidly by pertinent network search, and the mobile terminal may automatically roam, so that user experiences are improved. BRIEF DESCRIPTION OF THE DRAWINGS [0029]FIG. 1 is a functional block diagram of an automatic network search method for a mobile terminal according to an embodiment of the disclosure; [0030]FIG. 2 is a structure diagram of a mobile terminal according to an embodiment of the disclosure; [0031]FIG. 3 is a working flowchart of a mobile terminal for searching a network automatically according to an embodiment of the disclosure; and [0032]FIG. 4 is a flowchart of an automatic network search method for a mobile terminal according to an embodiment of the disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS [0033]The preferred embodiment of the disclosure is described below with reference to the drawings in detail. It is should be understood that the preferred embodiment described below is only adopted to explain the disclosure and not intended to limit the disclosure. [0034]In an embodiment of the disclosure, when a terminal detects that a user identification card (for example: a Subscriber Identity Module (SIM) card and a User Identity Module (UIM) card, called card hereinafter for short) is inserted into a current card slot, information about an operator which issues the card and information about a network mode supported by the card are read and stored, the terminal determines an area where the card is currently located and judges weather the terminal is in a roaming state after being started. A network is automatically searched according to a network search manner set by the terminal if the terminal is in a non-roaming state, and if the terminal is in the roaming state, information about a network corresponding to a subscribed operator, at a roaming destination, to which the operator issuing the card has subscribed is acquired from a storage component of the terminal according to the area where the terminal is currently located, and then the network is automatically searched according to a priority of the network mode supported by the card and a network mode of the subscribed operator, so that a function of finishing automatically selecting the network without user intervention is realized. [0035]FIG. 1 is a functional block diagram of an automatic network search method for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 1, the method includes the following steps: [0036]Step 101: it is judged whether there is a subscribed operator, with which of a user identification card is associated, in a plurality of network operators at a roaming destination when a mobile terminal is in a roaming state. [0037]Before Step 101, the method further includes: one or more card slots of the mobile terminal in real time are detected. When it is detected that the user identification card is inserted into one of the one or more card slots, information about an operator which issues the user identification card and a network mode supported by the user identification card is read and stored. A network in an area where the mobile terminal is located is searched to obtain at least one parameter of the network in the area where the mobile terminal is located according to the network mode. The at least one parameter of the network in the area where the mobile terminal is located is compared with a network parameter in the information about the subscribed operator which issues the user identification card to determine whether the mobile terminal is in the roaming state or not. Preferably, when the user identification card supports multiple network modes, networks corresponding to the corresponding network modes are sequentially searched according to priorities of the multiple network modes until the at least one parameter of the network in the area where the mobile terminal is located is obtained. [0038]When the at least one parameter of the network in the area where the mobile terminal is located is matched with the at least one network parameter in the information about the subscribed operator which issues the user identification card, it is determined that the mobile terminal is in a non-roaming state, otherwise the mobile terminal is in the roaming state. When the mobile terminal is in the non-roaming state, the network is automatically searched according to a network search manner set by the mobile terminal. [0039]Step 102: if there is the subscribed operator with which the user identification card is associated, an automatic search network is performed according to a priority of the network mode supported by the user identification card and a priority of a network corresponding to the subscribed operator. [0040]Step 103: if there is no subscribed operator with which the user identification card is associated, an automatic search network is performed according to the priority of the network mode supported by the user identification card. [0041]A mobile terminal may include one or more (including two or more than two) card slots, for example, sequentially numbered as card slots 1, 2, 3 . . . , and the card slots with smaller numbers are formed in front. If the mobile terminal includes only one card slot, the card slot is a main card slot, and if the mobile terminal includes multiple card slots, card slot 1 defaults to be the main card slot, the other card slots are additional card slots, and one of the additional card slots may be set to be the main card slot by user. [0042]For a main card slot, if a terminal detects that a card has been inserted into the main card slot when being started, the terminal reads and stores information about an operator which issues the card and a network mode supported by the card. The terminal searches for a network according to a first-priority network mode supported by the card, and judges an area where the card is currently located and whether the terminal is currently in a roaming state or not. An optimal network is selected automatically according to the roaming state of the terminal, an area operated by the operator and the network mode supported by the card. A network system including, but not limited to, network systems such as Long Term Evolution (LTE), Code Division Multiple Access (CDMA) (1X, Evolution-Data Optimized (EVDO)), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) and Global System for Mobile Communications (GSM). [0043]For an additional card slot, steps of a network search manner is consistent with the steps for the main card slot. The terminal is started. The terminal reads and stores information of an operator which issues the card and a network mode supported by the card if the terminal detects that a card has been inserted into the additional card slot. and the terminal judges an area where the terminal is currently located and a roaming state of the terminal. A search network is performed according to a network search manner set by the terminal if the terminal is in a non-roaming state, and if the terminal is located in a roaming destination, it is necessary to automatically research for a network according to a priority of the network mode supported by the card and a priority of a network mode operated by a subscribed operator, at the roaming destination, with which the operator issuing the card is associated. [0044]It is necessary to additionally consider that: when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, the user identification cards inserted in high-priority card slots preferably use the conflicting hardware resources and/or network resources according to the priorities of the multiple card slots corresponding to the multiple user identification cards. That is, when the hardware resources and network resources of the terminal conflict with the card slots, for example, a network conflict of the same system occurs to the main card slot and the additional card slots, the hardware resources and the network resources are preferably used by the main card slot (or the card slots with smaller numbers), and when the main card slot or the card slots with smaller numbers are recovered into other systems, the conflict is released, and the additional card slots may be recovered into non-conflicting states. [0045]One embodiment of the disclosure further provides a mobile terminal for searching a network automatically, which includes: [0046]a subscribed operator determination component configured to judge whether there is a subscribed operator with which a user identification card is associated or not in a plurality of network operators at a roaming destination when the mobile terminal is in a roaming state; [0047]a network search component configured to automatically search for a network according to a priority of a network mode supported by the user identification card and a priority of the network of the subscribed operator if there is the subscribed operator with which the user identification card is associated, and automatically search for a network according to the priority of the network mode supported by the user identification card if there is no subscribed operator with which the user identification card is associated; [0048]a detection component configured to detect one or more card slots of the mobile terminal in real time; [0049]an in-card information acquisition component configured to read information of an operator which issues the user identification card and the network mode supported by the user identification card when it is detected that the user identification card is inserted into one of the one or more card slots; [0050]a storage component configured to store the information about the operator which issues the user identification card and the supported network mode; and [0051]a roaming determination component configured to judge whether the mobile terminal is in the roaming state or not to enable the network search component to automatically search for the network according to a network search manner set by the mobile terminal if the mobile terminal is not in the roaming state. [0052]The network search component is further configured to automatically search for a network corresponding to the network mode supported by the user identification card when the mobile terminal is in the roaming state and the operator which issues the user identification card has not subscribed to a subscribed operator in an area where the mobile terminal is located, and is configured to, when there is a conflict between hardware resources and/or network resources of multiple user identification cards of the mobile terminal, enable the user identification card in higher priority card slot to preferably use the conflicting hardware resources and/or network resources according to the priorities of multiple card slots corresponding to the multiple user identification cards. [0053]FIG. 2 is a structure diagram of a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 2, the mobile terminal includes a master control component 201, a card slot and management component 202, a network selection component 203, a receiving/sending component 204, a storage component 205, a display component 206 and a power component 207, wherein [0054]the master control component 201 mainly controls coordinated operation of the whole terminal system. [0055]The card slot and management component 202 provides card slots for the terminal system and their corresponding interfaces for card data reading and writing and the like and functions such as management, and determines that the terminal is currently in a roaming state according to read information about the operator which issues the user identification card inserted in the card slot and temporary network related information (network parameters) acquired in a searching process of the network selection component 203. That is, the card slot and management component 202 realizes functions of the abovementioned detection component, in-card information acquisition component and roaming determination component. [0056]The network selection component 203 is configured to execute network search, network authentication, network switching, a power-saving network search strategy and the like according to the roaming state of the terminal and information of subscribed operator in the storage component 205. That is, the network selection component 203 realizes functions of the abovementioned subscribed operator determination component and network search component. [0057]The receiving/sending component 204 is configured to send data to be sent by the terminal to a network side, or receive data sent to the terminal by the network side, wherein a type of the data is a service type or a data type, and the receiving/sending component is a gateway for interaction between the terminal and a network. [0058]The storage component 205 is configured to store related information such as temporary data, service data and historical data in a running process of the terminal, store information (including, but not limited to, related information such as the name of the network operator, the network parameters of the network operator (a Master Control Code (MCC), a Mobile Network Code (MNC) and the like), the network mode, priorities of networks to be selected by a user within an operating area and the subscribed operators) to which the card in the current card slot of the terminal has subscribed. The information about the operator can be updated automatically, and for example, when the operator which issues the user identification card has newly updated subscribed operator information, the user is notified for manual upgrading or the terminal is notified for automatic upgrading in background. [0059]The display component 206 is configured to display the current state of the terminal and feed back information of the terminal to the user. [0060]The power component 207 provides power for the terminal, and provides a power distribution and management function involved in the terminal system. [0061]FIG. 3 is a working flowchart of a mobile terminal for automatically searching a network according to an embodiment of the disclosure, and the flow includes the following steps: [0062]Step 301: the terminal is powered on, and configuration of a main card slot and additional card slots (if existing) of the current terminal is acquired from a card slot and management component. [0063]If the terminal includes only one card slot, Step 302 is executed, and if the terminal further has the additional card slots, Step 308 is executed. [0064]Step 302: the terminal detects whether a card is currently inserted into the main card slot or not, and if the terminal detects that the card has been inserted into the main card slot, the terminal reads and stores information about an operator which issues the card and a network mode supported by the terminal, and turns to Step 303. [0065]Step 303: the terminal searches for a network at first according to priorities of networks operated by the operator which issues the card, and judges an area where the terminal is currently located and whether the terminal is currently in a roaming state or not according to the network parameters after the network is successfully searched, Step 304 is executed if the terminal is in a non-roaming state, and Step 305 is executed if the terminal is in the roaming state. [0066]Step 304: if the terminal is currently in the non-roaming state, the search network is automatically performed according to a network search manner set by the terminal, the network search manner includes an automatic mode or a CDMA-only or other single network-only mode. [0067]Step 305: if the terminal is currently in the roaming state, an operator information table stored by a storage component is looked up according to the area, where the terminal is located, determined in Step 303, information of the network operated by a subscribed operator, at a roaming destination, to which the operator issuing the card has subscribed is acquired, Step 306 is executed if there is the subscribed operator, and Step 307 is executed if there is no subscribed operator. [0068]Step 306: if there is a subscribed operator, at the roaming destination, to which the operator issuing the card has subscribed, the search network is sequentially and automatically performed according to the network mode supported by the card and a priority of the network of the subscribed operator. [0069]Step 307: if there is not a subscribed operator, at the roaming destination, to which the operator issuing the card has subscribed, the search network is sequentially and automatically performed according to the priority of the network mode supported by the card. [0070]Step 308: if the terminal includes an additional card slot, a network search flow is the same as the network search flow for the main card slot, but it is necessary to additionally consider that when there is a conflict between hardware resources and/or network resources of the terminal and the number of the card slots, for example, a network conflict of the same system occurs to the main card slot and the additional card slot, the hardware resources and the network resources are preferably used by the main card slot (or the card slots with smaller numbers), and when the main card slot or the card slot with smaller number are recovered into other system, the conflict is released, and the additional card slot or the card slot with larger number may be recovered into the state before conflicting. [0071]FIG. 4 is a flowchart of an automatic network search method for a mobile terminal according to an embodiment of the disclosure, and as shown in FIG. 4, the method includes the following steps: [0072]Step 401: the terminal is powered on, and configuration of a main card slot and additional card slots (if existing) of the current terminal is acquired from a card slot and management component. [0073]If the terminal includes only one card slot, Step 402 is executed; and if the terminal further has an additional card slot, Step 408 is executed. [0074]Step 402: if the terminal is powered on and it is detected that a card has been inserted into the main card slot, the terminal reads and stores information about an operator which issues the card and a network mode supported by the card, and turns to Step 403. [0075]Scenario 1 4021: the terminal reads information about that a CDMA GSM dual-mode card of China Telecom is inserted into the main card slot, the operator is China Telecom, network parameters MCC and MNC are 46002 and the network modes are CDMA and GSM. [0076]Scenario 2 4022: the terminal reads information about that a CDMA GSM dual-mode card of a branch of China Telecom in Macao is inserted into the main card slot, the operator is the branch of China Telecom in Macao, the network parameters MCC and MNC are 45502 and the network modes are CDMA and GSM. [0077]Scenario 3 4023: the terminal reads information about that a CDMA GSM dual-mode card of Softbank of Japan is inserted into the main card slot, the operator is Softbank of Japan, the network parameters MCC and MNC are 44020 and the network modes are CDMA and GSM. [0078]Step 403: due to the fact that the network modes supported by the card in the card slot are CDMA and GSM, the terminal preferably searches for a CDMA network with a higher priority, finds MCC and MNC are 46002, judges that the terminal is currently in Mainland China according to country code 460, and compares and matches Mainland China with operator information read from the card to determine that the terminal is in a roaming state. [0079]For scenario 1 4021 in Step 402, the terminal is determined to be in a non-roaming state, and Step 404 is executed. [0080]For scenario 2 4022 and scenario 3 4023 in Step 402, the MCC and MNC of the terminal are determined to be mismatched with MCC and MNC contained in the information about the operator which issues the card, the terminal is determined to be in the roaming state, and Step 405 is executed. [0081]Step 404: the terminal is in the non-roaming state, and the search network is automatically performed according to a network search manner (such as an automatic mode) set by the terminal. [0082]For scenario 1 4021 in Step 402, a CDMA network of Mainland China is searched, network China Telecom 46002 is found, then it is determined that searching is successful and the terminal passes authentication, the terminal successfully resides in the network, and enters a standby state. The network search process is completed. [0083]Step 405: if the terminal is currently in the roaming state, an operator information table stored by a storage component is queried to judge whether there is a subscribed operator, at the roaming destination, to which the operator issues the card has subscribed. [0084]For scenario 2 4022, there is the subscribed operator China Telecom in Mainland China, and Step 406 is executed. [0085]For scenario 3 4023, if Softbank has not subscribed to any subscribed operator in Mainland China, Step 407 is executed. [0086]Step 406: if the operator which issues the card has the subscribed operator at the roaming destination, the search network is sequentially and automatically performed according to the network mode supported by the card and a priority of the network of the subscribed operator. [0087]For scenario 2 4022, for a card issued by the branch of China Telecom in Macao, the CDMA network of China Telecom is preferably searched, and if the terminal successfully searches for the CDMA network 46002 and passes authentication, the terminal succeeds in network search and residence. [0088]Step 407: if the operator which issues the card has not the subscribed operator at the roaming destination, the network is sequentially and automatically searched according to the priority of the network mode supported by the card. [0089]For scenario 3 4023, for a card issued by Softbank of Japan, a CDMA network is preferably searched, it is determined that the network search fails if 46002 is successfully found but the terminal cannot reside for reasons such as insufficient signal intensity, the terminal automatically searches for the next mode GSM, and for example, if a GSM network of China Mobile is successfully found and the terminal successfully resides and passes authentication, the card roams to the GSM network of China Mobile and is successfully registered. [0090]Step 408: a network search flow for the additional card slot is the same as the network search flow for the main card slot, but when there is a conflict between hardware resources and/or network resources of the terminal and the number of the card slots, for example, a network conflict of the same system occurs to the main card slot and the additional card slot, the hardware resources and the network resources are preferably used by the main card slot (or the card slot with smaller number), and when the main card slot or the card slot with smaller numbers are recovered into other system, the conflict is released, and the additional card slot or the card slot with larger numbers may be recovered into the state before conflicting. [0091]In Step 408, if a CDMA/GSM dual-mode card is in(String), 技术领域 [0001] 本发明涉及移动通信领域,尤其涉及一种移动终端自动搜网的方法及相关移动终端。 背景 [0002] 移动技术改变生活,目前移动终端遍布全球,一个或多个运营商可能在全球多个国家和地区运营移动网络。 由于不同时期网络系统的升级或国家政策的调整,每个运营商可能运营多个制式的网络,发行的手机卡未来可能会从单模卡发展到双模卡再到多模卡 . 为争夺客户,解决用户频繁换机不换卡(号)的问题,运营商终端支持双卡槽,不再支持单卡槽,未来可能会发展为支持多卡槽 . [0003] 随着人口流动的增加,终端必须尽可能满足众多移动用户对自动漫游的需求,这促使终端卡槽不断升级,从支持单模卡到双模卡再到多模卡 . 网络制式的多样性和移动终端的复杂性导致移动终端的网络搜索存在差异,如何使终端能够快速、准确地找到用户需要的网络是一个复杂的问题。 [0004] 目前解决问题的方法有两种: [0005] 1:当移动终端漫游到另一个网络运营商的区域时,需要用户手动搜索和切换网络,这种方式对用户的专业知识要求很高,需要用户 需要通过很多操作步骤找到网络,然后切换网络,如果用户不手动搜索并完成切换,移动终端可能无法漫游,也可能影响用户业务的正常进行 糟糕的用户体验; 和 [0006] 2:终端开机后自动全频段随机搜索网络,这种方式主观性差,搜索网络的时间通常较长,浪费用户时间,不利于生活 终端的电池。 概括 [0007] 本发明实施例提供了一种移动终端自动搜网的方法及移动终端,可以更好地解决移动终端自动快速搜网的问题。 [0008] 根据本发明实施例的一个方面,提供了一种移动终端的自动网络搜索方法,包括: [0009] 当移动终端处于漫游状态时,判断漫游目的地的多个网络运营商中是否存在用户识别卡关联的签约运营商; [0010] 基于存在用户识别卡关联的签约运营商,根据用户识别卡支持的网络模式优先级和签约运营商对应的网络优先级自动搜索网络; 和 [0011] 基于没有用户识别卡关联的签约运营商,根据用户识别卡支持的网络模式的优先级自动搜索网络。 [0012] 优选地,在判断所述移动终端处于漫游状态时,所述漫游目的地的多个网络运营商中是否存在所述用户识别卡关联的签约运营商之前,所述方法还包括:判断所述移动终端是否 是否处于漫游状态; 基于移动终端未处于漫游状态,根据移动终端设置的网络搜索方式自动搜索网络。 [0013]优选地,在判断移动终端是否处于漫游状态之前,该方法还包括: 实时检测移动终端的一个或多个卡槽; 当检测到用户识别卡插入一个或多个卡槽之一时,读取发行用户识别卡的运营商信息和用户识别卡支持的网络模式信息; 存储发行用户识别卡的运营商信息和用户识别卡支持的网络模式信息。 [0014] 优选地,判断移动终端是否处于漫游状态包括:根据网络模式搜索移动终端所在区域的网络,获取移动终端所在区域的网络的至少一个参数。 移动终端位于; 将移动终端所在区域的网络的至少一参数与发行用户识别卡的运营商信息中的至少一网络参数进行比较,判断移动终端是否处于漫游状态。 . [0015] 优选地,根据网络模式搜索移动终端所在区域的网络,获取移动终端所在区域的网络的至少一个参数包括: 当用户识别卡支持多个时 网络模式,根据多种网络模式的优先级依次搜索对应的网络模式对应的网络,直到获取移动终端所在区域的网络的至少一个参数。 [0016] 优选地,将所述移动终端所在区域的至少一网络参数与签发用户识别卡的运营商信息中的所述至少一网络参数进行比较,判断移动终端是否处于漫游状态或者 不包括:基于移动终端所在区域的网络的至少一参数与发行用户标识卡的运营商的信息中的至少一网络参数匹配,确定移动终端 处于非漫游状态,否则判定移动终端处于漫游状态。 [0017] 优选地,该方法还包括: [0018] 当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,使得插入卡槽中的用户识别卡根据优先级较高的硬件资源和/或网络资源使用冲突的硬件资源和/或网络资源。 多个用户识别卡对应的多个卡槽的优先级。 [0019] 根据本发明实施例的另一个方面,提供了一种自动搜索网络的移动终端,包括: [0020] 签约运营商判断模块,用于当移动终端处于漫游状态时,判断漫游目的地的多个网络运营商中是否存在与用户识别卡关联的签约运营商; 网络搜索模块,用于当存在用户识别卡关联的签约运营商时,根据用户识别卡支持的网络模式的优先级和对应的网络的优先级自动搜索网络 签约的运营商,当没有签约的运营商关联用户识别卡时,根据用户识别卡支持的网络模式的优先级自动搜索网络。 [0021] 优选地,所述移动终端还包括: [0022] 漫游判断模块,用于判断移动终端是否处于漫游状态,使网络搜索模块在移动终端未处于漫游状态的情况下,根据移动终端设置的网络搜索方式自动搜索网络。 处于漫游状态。 [0023]优选地,所述移动终端还包括: [0024] 检测模块,用于实时检测移动终端的一个或多个卡槽; [0025] 卡内信息获取模块,用于在检测到所述用户识别卡插入所述一个或多个卡槽之一时,读取所述用户识别卡的发行运营商信息和支持的网络模式信息 用户识别卡; 和 [0026] 存储模块,用于存储发行用户识别卡的运营商信息和支持的网络模式信息。 [0027] 与现有技术相比,本发明实施例具有以下有益效果: [0028] 通过本发明实施例,可以通过有针对性的网络搜索,简单快速地自动找到用户需要的网络,并实现移动终端的自动漫游,提高了用户体验。 附图的简要说明 [0029] 图1是根据本发明实施例的移动终端自动搜网方法的功能框图; [0030] 图2是根据本发明实施例的移动终端的结构图; [0031] 图3是根据本发明实施例的移动终端自动搜网的工作流程图; 和 [0032] 图4是根据本发明实施例的移动终端自动搜网方法的流程图。 具体实施方式 [0033] 下面结合附图对本发明的优选实施例进行详细说明。 应当理解,下述所描述的优选实施例仅仅用于解释本发明,并不用于限定本发明。 [0034] 在本发明的一个实施例中,当终端检测到用户识别卡(例如:SIM卡和UIM卡,以下简称卡)插入当前卡时 读取并存储卡槽、发卡运营商信息和卡支持的网络模式信息,终端启动后判断卡当前所在区域,判断终端是否处于漫游状态。 如果终端处于非漫游状态,则根据终端设置的网络搜索方式自动搜索网络,如果终端处于漫游状态,则在漫游目的地获取签约运营商对应的网络信息 根据终端当前所在区域从终端的存储组件中获取发卡运营商签约的网络,然后根据卡支持的网络模式的优先级自动搜索网络, 签约运营商的网络模式,从而实现无需用户干预即可完成自动选网的功能。 [0035] 图1是根据本发明实施例的移动终端自动搜网方法的功能框图,如图1所示,该方法包括以下步骤: [0036] 步 101 :判断移动终端处于漫游状态时,在漫游目的地的多个网络运营商中是否存在与用户识别卡关联的签约运营商。 [0037] 步骤前 101,该方法还包括:实时检测移动终端的一个或多个卡槽。 当检测到用户识别卡插入一个或多个卡槽之一时,读取并存储发行用户识别卡的运营商和用户识别卡支持的网络模式的信息。 根据网络制式搜索移动终端所在区域的网络,获取移动终端所在区域的网络的至少一个参数。 将移动终端所在区域的网络的至少一个参数与签发用户识别卡的签约运营商信息中的网络参数进行比较,判断移动终端是否处于漫游状态。 优选地,当用户识别卡支持多种网络制式时,根据多种网络制式的优先级依次搜索相应网络制式对应的网络,直至获取移动终端所在区域网络的至少一个参数。 . [0038] 当移动终端所在区域网络的至少一参数与签发用户识别卡的签约运营商信息中的至少一网络参数匹配时,确定移动终端处于 非漫游状态,否则移动终端处于漫游状态。 当移动终端处于非漫游状态时,根据移动终端设置的网络搜索方式自动搜索网络。 [0039] 步 102 :如果存在用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级和签约运营商对应的网络的优先级进行自动搜网。 [0040] 步 103 :如果没有用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级进行自动搜网。 [0041] 移动终端可以包括一个或多个(包括两个或两个以上)卡槽,例如依次编号为卡槽1、2、3。 . . , 数字较小的卡槽在前面。 如果移动终端只有一个卡槽,则该卡槽为主卡槽,如果移动终端有多个卡槽,则默认1号卡槽为主卡槽,其他卡槽为附加卡槽, 用户可以将其中一个附加卡槽设置为主卡槽。 [0042] 对于主卡槽,如果终端在启动时检测到有卡插入主卡槽,则终端读取并存储该卡的发卡运营商信息和该卡支持的网络模式。 终端根据卡支持的优先网络模式搜索网络,判断卡当前所在的区域以及终端当前是否处于漫游状态。 根据终端的漫游状态、运营商运营区域和卡片支持的网络模式,自动选择最优网络。 网络系统包括但不限于长期演进(LTE)、码分多址(CDMA)(1X,Evolution-Data Optimized(EVDO))、宽带码分多址(WCDMA)、时间等网络系统 同步码分多址 (TD-SCDMA) 和全球移动通信系统 (GSM)。 [0043]对于附加卡槽,网络搜索方式的步骤与主卡槽的步骤一致。 终端已启动。 终端在检测到有卡插入附加卡槽时,读取并存储卡的发卡运营商信息和卡支持的网络模式。 终端判断终端当前所在的区域和终端的漫游状态。 如果终端处于非漫游状态,则按照终端设置的网络搜索方式进行搜索,如果终端位于漫游目的地,则需要按照优先级自动搜索网络 卡支持的网络模式的优先级以及在漫游目的地由发行卡的运营商关联的订阅运营商运营的网络模式的优先级。 [0044] 还需要考虑:当移动终端的多个用户识别卡的硬件资源和/或网络资源发生冲突时,插入高优先级卡槽的用户识别卡优先使用冲突的硬件资源和/或 或者根据多个用户识别卡对应的多个卡槽的优先级分配网络资源。 即,当终端的硬件资源和网络资源与卡槽发生冲突时,例如主卡槽和副卡槽发生同系统网络冲突时,优选硬件资源和网络资源。 主卡槽(或编号较小的卡槽)使用,当主卡槽或编号较小的卡槽回收到其他系统时,冲突解除,附加卡槽可能回收到非 - 冲突状态。 [0045] 本发明实施例还提供了一种自动搜索网络的移动终端,包括: [0046] 签约运营商判断模块,用于当移动终端处于漫游状态时,判断漫游目的地的多个网络运营商中是否存在与用户识别卡关联的签约运营商; [0047] 网络搜索模块,用于如果存在与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级和签约运营商网络的优先级自动搜索网络, 如果没有与用户识别卡关联的签约运营商,则根据用户识别卡支持的网络模式的优先级自动搜索网络; [0048] 检测模块,用于实时检测移动终端的一个或多个卡槽; [0049] 卡内信息获取模块,用于在检测到所述用户识别卡插入所述一个或多个卡槽之一时,读取所述用户识别卡的发行运营商信息和用户识别卡支持的网络模式 ; [0050] 存储模块,用于存储发行用户识别卡的运营商信息和支持的网络模式; 和 [0051] 漫游判断模块,用于判断移动终端是否处于漫游状态,若移动终端未处于漫游状态,则网络搜索模块根据移动终端设置的网络搜索方式自动搜索网络 状态。 [0052]网络搜索模块,还用于当移动终端处于漫游状态,且发行用户识别卡的运营商未签约签约运营商时,自动搜索用户识别卡支持的网络模式对应的网络。 移动终端所在区域,用于当移动终端的多张用户识别卡的硬件资源和/或网络资源发生冲突时,优先使用优先级高的卡槽中的用户识别卡 根据多个用户识别卡对应的多个卡槽的优先级,冲突的硬件资源和/或网络资源。 [0053] 图2为本发明实施例提供的一种移动终端的结构图,如图2所示,该移动终端包括总控组件 201 、卡槽和管理组件 202 , 一个网络选择组件 203 , 接收/发送组件 204 , 一个存储组件 205 , 显示组件 206 和一个电源组件 207 , 其中 [0054] 主控组件 201 主要控制整个终端系统的协调运行。 [0055] 卡槽及管理组件 202 为终端系统提供卡槽及其对应的接口,用于卡数据读写等功能和管理等功能,根据读取到的发卡运营商信息判断终端当前处于漫游状态 插入卡槽和网络选择模块搜索过程中获取的临时网络相关信息(网络参数) 203 . 即卡槽和管理组件 202 实现了上述检测模块、卡内信息获取模块和漫游判断模块的功能。 [0056] 网络选择组件 203 用于根据终端的漫游状态和存储模块中签约运营商的信息,执行网络搜索、网络认证、网络切换、省电网络搜索策略等。 205 . 即网络选择组件 203 实现上述签约运营商确定模块和网络搜索模块的功能。 [0057] 接收/发送组件 204 用于向网络侧发送终端要发送的数据,或接收网络侧向终端发送的数据,其中,数据的类型为业务类型或数据类型,接收/发送模块为 终端与网络交互的网关。 [0058] 存储组件 205 用于存储终端运行过程中的临时数据、业务数据、历史数据等相关信息,存储信息(包括但不限于网络运营商名称、网络参数等相关信息) 卡所在的网络运营商(Master Control Code(MCC)、Mobile Network Code(MNC)等)、网络模式、用户在操作区域内选择的网络优先级以及签约的运营商) 终端当前卡槽已订阅。 运营商信息可以自动更新,例如,当发放用户识别卡的运营商有最新更新的签约运营商信息时,通知用户手动升级或通知终端后台自动升级。 [0059] 显示组件 206 用于显示终端的当前状态,并向用户反馈终端的信息。 [0060] 电源组件 207 为终端提供电源,提供终端系统涉及的电源分配和管理功能。 [0061]图3是根据本发明实施例的移动终端自动搜网的工作流程图,该流程包括以下步骤: [0062] 步 301 :终端上电,从卡槽和管理组件获取当前终端的主卡槽和附加卡槽(如果存在)的配置。 [0063] 如果终端只有一个卡槽,步骤 302 执行,若终端还具有附加卡槽,步骤 308 被执行。 [0064] 步 302 :终端检测当前主卡槽中是否插入了卡片,如果终端检测到主卡槽中插入了卡片,则终端读取并存储发卡运营商信息和 终端支持的网络模式,转步骤 303 . [0065] 步 303 :终端首先根据发卡运营商运营的网络的优先级搜索网络,根据网络参数判断终端当前所在区域以及终端当前是否处于漫游状态 搜索网络成功后,步骤 304 终端处于非漫游状态时执行,步骤 305 如果终端处于漫游状态则执行。 [0066] 步 304 :若终端当前处于非漫游状态,则根据终端设置的搜网方式自动进行搜网,搜网方式包括自动方式或CDMA-only或其他单一网络-only方式 . [0067] 步 305 :若终端当前处于漫游状态,则根据步骤中确定的终端所在区域,查找存储模块存储的运营商信息表 303 , 获取发卡运营商签约的漫游目的地签约运营商运营的网络信息, 步骤 306 如果有订阅的操作员,则执行,并且步骤 307 如果没有订阅的操作员,则执行。 [0068] 步 306 :如果漫游目的地有发卡运营商签约的签约运营商,则根据卡支持的网络模式和签约运营商的网络优先级顺序自动搜索网络 . [0069] 步 307 :如果漫游目的地没有签约的运营商,发卡运营商签约,则根据卡支持的网络模式的优先级顺序自动搜索网络。 [0070] 步 308 :如果终端包含附加卡槽,则网络搜索流程与主卡槽的网络搜索流程相同,但需要额外考虑当硬件资源和/或网络资源之间存在冲突时 终端和卡槽数量,例如主卡槽和副卡槽出现同系统网络冲突,硬件资源和网络资源优先使用主卡槽(或副卡槽) 号较小的卡槽),当主卡槽或编号较小的卡槽恢复到其他系统时,冲突解除,附加卡槽或编号较大的卡槽可以恢复到之前的状态 矛盾的。 [0071] 图4为本发明实施例提供的一种移动终端自动搜网方法的流程图,如图4所示,该方法包括以下步骤: [0072] 步 401 :终端上电,从卡槽和管理组件获取当前终端的主卡槽和附加卡槽(如果存在)的配置。 [0073] 如果终端只有一个卡槽,步骤 402 被执行; 如果终端还有额外的卡槽,步骤 408 被执行。 [0074] 步 402 :如果终端上电,检测到有卡插入主卡槽,终端读取并存储发卡运营商信息和卡支持的网络模式,转步骤 403 . [0075] 场景一4021:终端读取到主卡槽中插入了一张中国电信的CDMA GSM双模卡,运营商为中国电信,网络参数MCC和MNC为46002,网络制式为CDMA和GSM。 [0076] 场景2 4022:终端读取主卡槽插入中国电信澳门分公司的CDMA GSM双模卡信息,运营商为中国电信澳门分公司,网络参数MCC和MNC 是45502,网络模式是CDMA和GSM。 [0077] 场景3 4023:终端读取到主卡槽中插入日本软银的CDMA GSM双模卡,运营商为日本软银,网络参数MCC和MNC为44020,网络模式为CDMA 和全球移动通信系统。 [0078] 步 403 :由于卡槽中的卡支持的网络模式为CDMA和GSM,终端优先搜索优先级高的CDMA网络,发现MCC和MNC为46002,判断终端当前在大陆 中国根据国家代码460,将中国大陆与从卡中读取的运营商信息进行比对,确定终端处于漫游状态。 [0079] 对于Step中的场景1 4021 402 ,确定终端处于非漫游状态,步骤 404 被执行。 [0080] 对于Step中的场景2 4022和场景3 4023 402 ,确定终端的MCC和MNC与发卡运营商信息中的MCC和MNC不匹配,确定终端处于漫游状态, 步骤 405 被执行。 [0081] 步 404 :终端处于非漫游状态,按照终端设置的搜网方式(如自动模式)自动搜网。 [0082] 对于Step中的场景1 4021 402 ,搜索中国大陆CDMA网络,搜索到网络中国电信46002,则确定搜索成功,终端鉴权通过,终端成功入网,进入待机状态。 网络搜索过程完成。 [0083] 步 405 :若终端当前处于漫游状态,则查询存储模块存储的运营商信息表,判断漫游目的地是否有运营商签约的运营商发卡签约的运营商。 [0084] 对于场景2 4022,有中国大陆签约运营商中国电信,步骤 406 被执行。 [0085] 对于场景3 4023,如果Softbank在中国大陆没有签约任何运营商,步骤 407 被执行。 [0086] 步 406 :如果发卡运营商在漫游目的地有签约运营商,则根据卡支持的网络模式和签约运营商网络的优先级顺序自动搜索网络。 [0087] 对于场景2 4022,对于中国电信澳门分行发行的卡,优先搜索中国电信的CDMA网络,如果终端成功搜索到CDMA网络46002并认证通过,则终端搜索网络成功, 住宅。 [0088] 步 407 :如果发卡运营商在漫游目的地没有签约运营商,则按照卡支持网络模式的优先级依次自动搜索网络。 [0089]场景3 4023,对于日本软银发行的卡,优先搜索CDMA网络,如果成功搜索到46002,则判断网络搜索失败,但由于信号强度不足等原因导致终端无法驻留,终端自动 搜索下一制式GSM,如成功搜索到中国移动GSM网络,终端成功驻留并认证通过,卡漫游到中国移动GSM网络,注册成功。 [0090] 步 408 :副卡位的网络搜索流程与主卡位的网络搜索流程相同,但是当终端的硬件资源和/或网络资源与卡位的数量存在冲突时,对于 例如主卡槽和副卡槽出现同系统网络冲突,硬件资源和网络资源优先使用主卡槽(或编号较小的卡槽),当主卡槽 将卡槽或编号较小的卡槽恢复到其他系统,解除冲突,可以将新增的卡槽或编号较大的卡槽恢复到冲突前的状态。 [0091] 在步骤 408 ,如果CDMA/GSM双模卡插入主卡槽,卡成功注册到CDMA网络,终端搜网时CDMA网络信号质量低于驻留门限,终端 主卡槽和副卡槽只有一套GSM射频电路,主卡槽的卡最好漫游到GSM网络,而副卡槽的卡只能离线 等待状态。 CDMA网络信号质量恢复正常后,主卡槽恢复注册到CDMA网络,副卡槽以省电模式周期性寻找GSM网络,鉴权成功,入驻 在 GSM 网络中可能被允许。 [0092] 本发明实施例支持终端为单卡槽的情况,也支持双卡槽、三卡槽及更多卡槽的移动终端,卡槽中的卡可以是最简单的单模卡, 也可以是双模卡、多模卡等各种条件的组合。 [0093] 本发明实施例涉及的网络制式包括GSM、CDMA、WCDMA、CDMA2000(1x/EVDO)、TD-SCDMA以及后续的LTE-A等多种制式。 [0094] 综上所述,本发明实施例的技术效果如下:本发明实施例实现逻辑清晰,无需用户手动操作即可自动搜索网络,给用户带来了极大的方便,方便了用户使用。 经验得到改善。 [0095] 以上虽然对本发明进行了详细的说明,但本发明并不限于此,本领域的技术人员可以根据本发明的原理做出各种修改。 因此,凡是依据本发明的原则所做的修改,均应落入本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.815 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN104105166A(String), CN104105166B(String), EP2986059A1(String), EP2986059A4(String), US20160112578A1(String), WO2014166185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN104105166A(String), CN104105166B(String), EP2986059A1(String), EP2986059A4(String), US20160112578A1(String), WO2014166185A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.991 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:20.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20160112578A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN104105166A(String), CN104105166B(String), EP2986059A1(String), EP2986059A4(String), US20160112578A1(String), WO2014166185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.044 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271681(Integer), CN104105166A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.079 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271681(Integer), CN104105166B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.114 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271681(Integer), EP2986059A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.148 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.149 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271681(Integer), EP2986059A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271681(Integer), US20160112578A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.219 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271681(Integer), WO2014166185A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.254 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20160112578A1(String), US20160112578A1(String), 1461168000(Integer), 271681(Integer), 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.289 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 中兴通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.335 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.368 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186012(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.402 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186012(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.470 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186012(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.503 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.504 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 2(Integer), 186012(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.539 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.574 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.642 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.643 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.662 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.813 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.814 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.848 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:21.849 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10638311B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.190 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Communication method for mobile terminal and mobile terminal(String), 移动终端的通信方法及移动终端(String), US10638311B2(String), Embodiments of the present disclosure disclose a secure communication method for a mobile terminal and a mobile terminal. The secure communication method may include: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performing, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and outputting, by using the secure virtual kernel, communication content obtained by performing the preset policy-based processing.(String), 本发明实施例公开了一种移动终端的安全通信方法及移动终端。 所述安全通信方法可以包括:当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序 从访问安全虚拟内核和公共虚拟内核之间的共享内存到访问无线通信连接需要调用的外围设备; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设的基于策略的处理; 使用安全虚拟内核输出经过预设的基于策略的处理得到的通信内容。(String), US15/795491(String), 1509033600(Integer), US10638311B2(String), 1588003200(Integer), 1588003200(Integer), 美国(String), 4(Integer), CN(String), 6(Integer), 29(Integer), CN102045712A | CN102209318A | CN102271191A | CN102307346A | CN102413462A | CN102761409A | CN102857914A | CN103197991A | CN103249036A | CN103457958A | CN103577740A | CN1585539A | EP2648129A1 | KR1020130062219A | US20070270170A1 | US20120216242A1 | US20130145475A1 | US20130179403A1 | US20140007120A1 | US20140045545A1 | US20140148123A1 | US20140281560A1 | US20170011206A1 | US20170220823A1 | US20190104114A1 | US20190166638A1 | WO2014137343A1 | WO2014141206A1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186013(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.373 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\da734a3936854726b46b56c45b277ab1.png(String), 186013(Integer), da734a3936854726b46b56c45b277ab1.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.408 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.425 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.426 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Communication method for mobile terminal and mobile terminal(String), 移动终端的通信方法及移动终端(String), US10638311B2(String), Embodiments of the present disclosure disclose a secure communication method for a mobile terminal and a mobile terminal. The secure communication method may include: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performing, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and outputting, by using the secure virtual kernel, communication content obtained by performing the preset policy-based processing.(String), 本发明实施例公开了一种移动终端的安全通信方法及移动终端。 所述安全通信方法可以包括:当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序 从访问安全虚拟内核和公共虚拟内核之间的共享内存到访问无线通信连接需要调用的外围设备; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设的基于策略的处理; 使用安全虚拟内核输出经过预设的基于策略的处理得到的通信内容。(String), US15/795491(String), 1509033600(Integer), US10638311B2(String), 1588003200(Integer), 1588003200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 6(Integer), 29(Integer), CN102045712A | CN102209318A | CN102271191A | CN102307346A | CN102413462A | CN102761409A | CN102857914A | CN103197991A | CN103249036A | CN103457958A | CN103577740A | CN1585539A | EP2648129A1 | KR1020130062219A | US20070270170A1 | US20120216242A1 | US20130145475A1 | US20130179403A1 | US20140007120A1 | US20140045545A1 | US20140148123A1 | US20140281560A1 | US20170011206A1 | US20170220823A1 | US20190104114A1 | US20190166638A1 | WO2014137343A1 | WO2014141206A1(String), \20230420\da734a3936854726b46b56c45b277ab1.png(String), 12(Integer), 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.496 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 1. A secure communication method for a mobile terminal, wherein an application processor of the mobile terminal comprises a secure virtual kernel and a common virtual kernel which share a central processing unit (CPU), a memory, a bus, and a peripheral that are of the mobile terminal, and wherein a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel, the secure communication method comprising:when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by the mobile terminal, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and from accessing a peripheral used by the wireless communication connection;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing; andwherein before the wireless communication connection is established between the mobile terminal and the other mobile terminal, the secure communication method further comprises:prohibiting, by the mobile terminal, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition.(String), 1.根据权利要求7所述的移动终端,其中:无线通讯连接所使用的外设包括录像装置,通讯内容包括录制的视频信号。处理单元包括:第二加密子单元,用于当通信内容为视频录制设备录制的视频信号时,通过安全虚拟内核对录制的视频信号进行加密处理,第二编码子单元,用于使用安全虚拟内核对加密处理后的视频信号进行编码,得到待发送的视频信号;和输出单元,用于通过安全虚拟内核控制移动终端向另一移动终端发送待发送视频信号。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 2. The method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises an audio recording device, and the communication content comprises a recorded audio signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is an audio signal recorded by the audio recording device, performing, by the mobile terminal, encryption processing on the recorded audio signal by using the secure virtual kernel, andcoding, by the mobile terminal by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal.(String), 12.根据权利要求7所述的移动终端,其中:无线通讯连接所使用的外设包括显示器,通讯内容包括接收到的视频信号。处理单元还包括:第二解码子单元,用于当通信内容为移动终端接收到的视频信号时,使用安全虚拟内核对接收到的视频信号进行解码;第二解密子单元,用于利用安全虚拟内核对解码后的视频信号进行解密处理,得到待播放视频信号;和输出单元用于通过安全虚拟内核控制显示器播放待播放视频信号。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.498 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 3. The method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is an audio signal received by the mobile terminal, decoding, by the mobile terminal, the audio signal by using the secure virtual kernel, andperforming, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by the mobile terminal by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 4. The method according to claim 2, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is an audio signal received by the mobile terminal, decoding, by the mobile terminal, the audio signal by using the secure virtual kernel, andperforming, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by the mobile terminal by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 5. The secure communication method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises a video recording device, and the communication content comprises a recorded video signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is a video signal recorded by the video recording device, performing, by the mobile terminal, encryption processing on the recorded video signal by using the secure virtual kernel, andcoding, by the mobile terminal by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal.(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 6. The secure communication method according to claim 1, wherein:the peripheral to be used by the wireless communication connection comprises a display, and the communication content comprises a received video signal;performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection comprises:when the communication content is a video signal received by the mobile terminal, decoding, by the mobile terminal, the received video signal by using the secure virtual kernel, andperforming, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; andoutputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing comprises:controlling, by the mobile terminal by using the secure virtual kernel, the display to play the to-be-played video signal.(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 7. A mobile terminal, wherein an application processor of the mobile terminal comprises a secure virtual kernel and a common virtual kernel which share a central processing unit (CPU), a memory, a bus, and a peripheral that are of the mobile terminal, and a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel, the mobile terminal comprising:a first setting unit, configured to: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibit, by means of setting, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and accessing a peripheral to be used by the wireless communication connection;a processing unit, configured to perform, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection;an output unit, configured to output, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing; anda second setting unit, configured to prohibit, by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition.(String), 0(Integer), 6(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 8. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises an audio recording device, and the communication content comprises a recorded audio signal;the processing unit comprises:a first encryption subunit, configured to: when the communication content is an audio signal recorded by the audio recording device, perform encryption processing on the recorded audio signal by using the secure virtual kernel, anda first coding subunit, configured to code, by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; andthe output unit is configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal.(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 9. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;the processing unit comprises:a first decoding subunit, configured to: when the communication content is an audio signal received by the mobile terminal, decode the audio signal by using the secure virtual kernel, anda first decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andthe output unit is configured to control, by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 10. The mobile terminal according to claim 8, wherein:the peripheral to be used by the wireless communication connection comprises an audio playing device, and the communication content comprises a received audio signal;the processing unit comprises:a first decoding subunit, configured to: when the communication content is an audio signal received by the mobile terminal, decode the audio signal by using the secure virtual kernel, anda first decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; andthe output unit is configured to control, by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal.(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 11. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises a video recording device, and the communication content comprises a recorded video signal;the processing unit comprises:a second encryption subunit, configured to: when the communication content is a video signal recorded by the video recording device, perform encryption processing on the recorded video signal by using the secure virtual kernel, anda second coding subunit, configured to code, by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; andthe output unit is configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal.(String), 1(Integer), 10(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186013(Integer), 12. The mobile terminal according to claim 7, wherein:the peripheral to be used by the wireless communication connection comprises a display, and the communication content comprises a received video signal;the processing unit further comprises:a second decoding subunit, configured to: when the communication content is a video signal received by the mobile terminal, decode the received video signal by using the secure virtual kernel, anda second decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; andthe output unit is configured to control, by using the secure virtual kernel, the display to play the to-be-played video signal.(String), 1(Integer), 11(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.753 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186013(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]This application is a continuation of International Application No. PCT/CN2015/098761, filed on Dec. 24, 2015, which claims priority to Chinese Patent Application No. 201510217336.8, filed on Apr. 30, 2015. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD [0002]The present application relates to the communications field, and in particular, to a secure communication method for a mobile communications terminal and a mobile communications terminal. BACKGROUND [0003]With development of mobile communications technologies, mobile terminals have been widely popular, and the mobile terminals have become necessities in daily life of a user. When working, shopping, or taking recreation by using a mobile terminal, the user transmits private information. The private information may be eavesdropped on by a criminal, and therefore lead to serious consequences such as privacy disclosure and a property loss of the user. Mobile communication security has been increasingly concerned about by the government, the society, and the user, and network security and information security issues have even risen to a national strategic height. [0004]In the prior art, before a call is initiated or answered by using a mobile terminal, a process that includes a recording module is usually searched and ended, so as to prevent call content from being secretly recorded, thereby preventing a background process from eavesdropping. [0005]In the foregoing method, the background process is prevented from eavesdropping when an operating system of the mobile terminal is trusted. However, nowadays, as functions of mobile terminals are increasingly abundant, architectures of operating systems of the mobile terminals are increasingly complex, and there is a growing quantity of security vulnerabilities. Therefore, a communication security technology that can be used to prevent attacks from the operating systems needs to be urgently developed. SUMMARY [0006]Embodiments of the present disclosure disclose a secure communication method for a mobile terminal and a mobile terminal, to prevent an operating system from eavesdropping on communication content of a user, and improve communication security of the mobile terminal. [0007]A first aspect of the embodiments of the present disclosure discloses a secure communication method for a mobile terminal, where an application processor of the mobile terminal includes a secure virtual kernel and a common virtual kernel, the secure virtual kernel and the common virtual kernel share a central processing unit CPU, a memory, a bus, and a peripheral that are of the mobile terminal, and a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel; and [0008]the secure communication method includes: [0009]when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibiting, by the mobile terminal by means of setting, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; [0010]performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and [0011]outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing. [0012]With reference to the first aspect, in a first feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio recording device, and the communication content includes a recorded audio signal; [0013]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0014]when the communication content is an audio signal recorded by the audio recording device, performing, by the mobile terminal, encryption processing on the recorded audio signal by using the secure virtual kernel; and [0015]coding, by the mobile terminal by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; and [0016]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0017]controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal. [0018]With reference to the first aspect or the first feasible implementation of the first aspect, in a second feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio playing device, and the communication content includes a received audio signal; [0019]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0020]when the communication content is an audio signal received by the mobile terminal, decoding, by the mobile terminal, the audio signal by using the secure virtual kernel; and [0021]performing, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; and [0022]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0023]controlling, by the mobile terminal by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal. [0024]With reference to any one of the first aspect, or the first to the second feasible implementations of the first aspect, in a third feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a video recording device, and the communication content includes a recorded video signal; [0025]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0026]when the communication content is a video signal recorded by the video recording device, performing, by the mobile terminal, encryption processing on the recorded video signal by using the secure virtual kernel; and [0027]coding, by the mobile terminal by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; and [0028]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0029]controlling, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal. [0030]With reference to any one of the first aspect, or the first to the third feasible implementations of the first aspect, in a fourth feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a display, and the communication content includes a received video signal; [0031]the performing, by the mobile terminal by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection specifically includes: [0032]when the communication content is a video signal received by the mobile terminal, decoding, by the mobile terminal, the received video signal by using the secure virtual kernel; and [0033]performing, by the mobile terminal by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; and [0034]the outputting, by the mobile terminal by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing specifically includes: [0035]controlling, by the mobile terminal by using the secure virtual kernel, the display to play the to-be-played video signal. [0036]With reference to any one of the first aspect, or the first to the fourth feasible implementations of the first aspect, in a fifth feasible implementation, before the wireless communication connection is established between the mobile terminal and the another mobile terminal, the secure communication method further includes: [0037]prohibiting, by the mobile terminal by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition. [0038]A second aspect of the embodiments of the present disclosure provides a mobile terminal, where an application processor of the mobile terminal includes a secure virtual kernel and a common virtual kernel, the secure virtual kernel and the common virtual kernel share a central processing unit CPU, a memory, a bus, and a peripheral that are of the mobile terminal, and a program in the common virtual kernel is prohibited from accessing an application processor resource of the secure virtual kernel; and [0039]the mobile terminal includes: [0040]a first setting unit, configured to: when a wireless communication connection is established between the mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, prohibit, by means of setting, the program in the common virtual kernel from accessing a shared memory between the secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; [0041]a processing unit, configured to perform, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and [0042]an output unit, configured to output, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing. [0043]With reference to the second aspect, in a first feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio recording device, and the communication content includes a recorded audio signal; [0044]the processing unit includes: [0045]a first encryption subunit, configured to: when the communication content is an audio signal recorded by the audio recording device, perform encryption processing on the recorded audio signal by using the secure virtual kernel; and [0046]a first coding subunit, configured to code, by using the secure virtual kernel, the audio signal obtained by performing the encryption processing, so as to obtain a to-be-sent audio signal; and [0047]the output unit is specifically configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent audio signal to the another mobile terminal. [0048]With reference to the second aspect or the first feasible implementation of the second aspect, in a second feasible implementation, the peripheral that needs to be called for the wireless communication connection includes an audio playing device, and the communication content includes a received audio signal; [0049]the processing unit includes: [0050]a first decoding subunit, configured to: when the communication content is an audio signal received by the mobile terminal, decode the audio signal by using the secure virtual kernel; and [0051]a first decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded audio signal, so as to obtain a to-be-played audio signal; and [0052]the output unit is specifically configured to control, by using the secure virtual kernel, the audio playing device to play the to-be-played audio signal. [0053]With reference to any one of the second aspect, or the first to the second feasible implementations of the second aspect, in a third feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a video recording device, and the communication content includes a recorded video signal; [0054]the processing unit includes: [0055]a second encryption subunit, configured to: when the communication content is a video signal recorded by the video recording device, perform encryption processing on the recorded video signal by using the secure virtual kernel; and [0056]a second coding subunit, configured to code, by using the secure virtual kernel, the video signal obtained by performing the encryption processing, so as to obtain a to-be-sent video signal; and [0057]the output unit is specifically configured to control, by using the secure virtual kernel, the mobile terminal to send the to-be-sent video signal to the another mobile terminal. [0058]With reference to any one of the second aspect, or the first to the third feasible implementations of the second aspect, in a fourth feasible implementation, the peripheral that needs to be called for the wireless communication connection includes a display, and the communication content includes a received video signal; [0059]the processing unit includes: [0060]a second decoding subunit, configured to: when the communication content is a video signal received by the mobile terminal, decode the received video signal by using the secure virtual kernel; and [0061]a second decryption subunit, configured to perform, by using the secure virtual kernel, decryption processing on the decoded video signal, so as to obtain a to-be-played video signal; and [0062]the output unit is specifically configured to control, by using the secure virtual kernel, the display to play the to-be-played video signal. [0063]With reference to any one of the second aspect, or the first to the fourth feasible implementations of the second aspect, in a fifth feasible implementation, the mobile terminal further includes: [0064]a second setting unit, configured to prohibit, by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection. [0065]In the embodiments of the present disclosure, when a wireless communication connection is established between a mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, the mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performs, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and then outputs, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing, so that an operating system and the program running in the common virtual kernel can be prevented from obtaining unprocessed communication content, and the operating system can also be prevented from eavesdropping on the communication content by using the shared memory or the related peripheral, thereby improving communication security of the mobile terminal. BRIEF DESCRIPTION OF DRAWINGS [0066]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0067]FIG. 1 is a schematic flowchart of an embodiment of a secure communication method for a mobile terminal in the present disclosure; [0068]FIG. 2 is a schematic flowchart of another embodiment of a secure communication method for a mobile terminal in the present disclosure; [0069]FIG. 3 is a schematic flowchart of still another embodiment of a secure communication method for a mobile terminal in the present disclosure; [0070]FIG. 4 is a schematic structural diagram of an embodiment of a mobile terminal in the present disclosure; [0071]FIG. 5 is a schematic structural diagram of another embodiment of a mobile terminal in the present disclosure; [0072]FIG. 6 is a schematic structural diagram of still another embodiment of a mobile terminal in the present disclosure; and [0073]FIG. 7 is a schematic structural diagram of yet another embodiment of a mobile terminal in the present disclosure. DETAILED DESCRIPTION [0074]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0075]With reference to the accompanying drawings, the following describes in detail a secure communication method for a mobile terminal and a mobile terminal that are provided in the embodiments of the present disclosure. In the embodiments of the present disclosure, the mobile terminal includes but is not limited to a terminal that may be used for communication, such as a mobile phone, a personal computer, or a notebook computer. [0076]Referring to FIG. 1, FIG. 1 is a schematic flowchart of an embodiment of a secure communication method for a mobile terminal in the present disclosure. As shown in FIG. 1, in this embodiment, the secure communication method includes the following steps. [0077]S101. When a wireless communication connection is established between a mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, the mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection. [0078]In this embodiment of the present disclosure, a CPU (central processing unit) of the mobile terminal includes at least an application processor. When the mobile terminal is a mobile phone, the CPU of the mobile terminal further includes a baseband processor. The application processor includes a secure virtual kernel and a common virtual kernel, and the secure virtual kernel and the common virtual kernel share a CPU, a memory, a peripheral, and a bus that are of the mobile terminal. In a specific implementation, the secure virtual kernel exclusively occupies some application processor hardware resources, and the program in the common virtual kernel is prohibited from accessing the application processor resources exclusively occupied by the secure virtual kernel. [0079]In a specific implementation, a baseband system of the mobile terminal runs in the baseband processor; some security modules run in the secure virtual kernel; and an operating system of the mobile terminal runs in the common virtual kernel, such as Android, iOS, or Windows Phone. [0080]In a feasible implementation, the mobile terminal may be a mobile terminal that uses an ARM (advanced reduced instruction set computing machine) processor and that is based on a TrustZone technology. [0081]Optionally, the wireless communication connection may include but is not limited to: a common telephone connection, a network voice connection (including a network telephone connection or another voice connection between real-time communications clients), a network video connection, or the like. [0082]In some feasible implementations, in this embodiment of the present disclosure, when short message communication or mail communication may be further performed between the mobile terminal and the another mobile terminal, the program in the common virtual kernel is prohibited, by means of setting, from accessing the shared memory between the secure virtual kernel and the common virtual kernel and assessing the peripheral that needs to be called for the short message communication or the mail communication. The peripheral that needs to be called for the short message communication or the mail communication may include one or more of a push-button, a keyboard, a tablet, or a display. [0083]In some feasible implementations, it may be determined, by detecting some trigger actions of the mobile terminal, that the wireless communication connection is established between the mobile terminal and the another mobile terminal; for example, when it is detected that the mobile terminal performs a dialing operation, or when it is detected that the mobile terminal logs in to a real-time communications client, it may be considered that the wireless communication connection is established between the mobile terminal and the another mobile terminal. [0084]In some feasible implementations, it may be determined, by detecting some interrupt signals related to the wireless communication connection, that the wireless communication connection is established between the mobile terminal and the another mobile terminal; for example, when an incoming call is made by the another mobile terminal, the application processor receives incoming call information interrupt request sent by the baseband processor. [0085]Optionally, that the wireless communication connection meets the preset security processing trigger condition may be: The other mobile terminal that establishes the wireless communication connection to the mobile terminal meets a security condition set by the mobile terminal, for example, the wireless communication connection is a wireless communication connection between the mobile terminal and a buddy in an address book, or may be: A type of the wireless communication connection meets a security type set by the mobile terminal, for example, the wireless communication connection is a telephone connection. [0086]In some feasible implementations, after being powered on, the mobile terminal may prohibit, by means of setting, the program in the common virtual kernel from accessing interrupt information related to the wireless communication connection that meets the preset security processing trigger condition. For example, when detecting any incoming call signal or detecting an incoming call signal of the buddy in the address book, the baseband system sends the incoming call information interrupt request to the application processor. Because the program in the common virtual kernel is prohibited, by means of presetting, from accessing the incoming call information interrupt request, the application processor processes the incoming call information interrupt request by using the secure virtual kernel after receiving the incoming call information interrupt request. [0087]Optionally, when the wireless communication connection relates to a voice call (such as a common telephone call, a network telephone call, or a voice session initiated by using a real-time communications client), the peripheral that needs to be called includes at least an audio recording device and an audio playing device. In a specific implementation, the audio recording device and the audio playing device may be a same device, for example, a microphone of the mobile terminal. [0088]Optionally, when the wireless communication connection relates to a video call, the peripheral that needs to be called includes at least a video recording device, an audio recording device, an audio playing device, and a display, such as a camera, a microphone, and a display that are of the mobile terminal. [0089]In some feasible implementations, the mobile terminal may set, to a security interrupt and by using a GIC (generic interrupt controller) or a TZIC (TrustZone interrupt controller), the interrupt information related to the wireless communication connection, so that the interrupt information is accessed only in the secure virtual kernel. In a specific implementation, the GIC or the TZIC is connected to all interrupt sources of the mobile terminal, and may first intercept an interrupt request of the mobile terminal; and the GIC or the TZIC hands over, to the secure virtual kernel, an interrupt request related to the wireless communication connection for processing. [0090]In some feasible implementations, the mobile terminal divides a physical memory into multiple memory areas by using a TZASC (TrustZone address space controller), and configures, by using software running in the secure virtual kernel, some memory areas to be secure memory areas or non-secure memory areas, and the TZASC may prohibit the program running in the common virtual kernel from accessing the secure memory area. [0091]In some feasible implementations, the mobile terminal configures a security attribute of the peripheral by using a TZPC (TrustZone protection controller), classifies the peripheral as a secure peripheral or a non-secure peripheral, and prohibits the program running in the common virtual kernel from accessing the secure peripheral. [0092]S102. The mobile terminal performs, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection. [0093]Optionally, the communication content corresponding to the wireless communication connection includes communication content to be sent by the mobile terminal and communication content received by the mobile terminal. [0094]Optionally, for the to-be-sent communication content, the preset policy-based processing may include one or more of encryption, analog-to-digital conversion, coding, modulation, or the like. For the received communication content, the preset policy-based processing may include one or more of decryption, demodulation, decoding, digital-to-analog conversion, or the like. The preset policy-based processing is performed by using the secure virtual kernel of the mobile terminal, and the program in the common virtual kernel cannot access communication content obtained before the preset policy-based processing is performed. [0095]In a specific implementation, because there is a large amount of code in an operating system running in a common virtual kernel, there is a relatively large quantity of security vulnerabilities. Because there is a small amount of code in a module running in a secure virtual kernel, security can be easily verified. Preset policy-based processing is performed on communication content by using the secure virtual kernel, so that the operating system running in the common virtual kernel can be prevented from obtaining communication content obtained before the preset policy-based processing is performed, and the operating system can be prevented from eavesdropping on the communication content. [0096]S103. The mobile terminal outputs, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing. [0097]In a specific implementation, after performing the preset policy-based processing on the communication content to be sent by the mobile terminal, the mobile terminal may send the to-be-sent communication content by using a radio frequency module or a wireless network connection module. Communication content of a telephone call or a short message may be sent by using the radio frequency module of the mobile terminal; and communication content of a mail, a network voice call, a video call, or the like may be sent by using the wireless network connection module. In this embodiment of the present disclosure, the network connection module may be a Wi-Fi module, and is configured to enable the mobile terminal to access the Internet. [0098]After performing the preset policy-based processing on the communication content received by the mobile terminal, the mobile terminal may output the received communication content. Optionally, if the received communication content is a voice, the received communication content may be output by using an audio playing device (for example, a microphone); if the received communication content is a video, the received communication content may be output by using a display and an audio playing device; or if the received communication content is a text or a picture, the received communication content may be output by using a display. [0099]In this embodiment of the present disclosure, when a wireless communication connection is established between a mobile terminal and another mobile terminal, and the wireless communication connection meets a preset security processing trigger condition, the mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing a shared memory between a secure virtual kernel and the common virtual kernel and accessing a peripheral that needs to be called for the wireless communication connection; performs, by using the secure virtual kernel, preset policy-based processing on communication content corresponding to the wireless communication connection; and then outputs, by using the secure virtual kernel, the communication content obtained by performing the preset policy-based processing, so that an operating system and the program running in the common virtual kernel can be prevented from obtaining unprocessed communication content, and the operating system can also be prevented from eavesdropping on the communication content by using the shared memory or the related peripheral, thereby improving communication security of the mobile terminal. [0100]Referring to FIG. 2, FIG. 2 is a schematic flowchart of another embodiment of a secure communication method for a mobile terminal in the present disclosure. As shown in FIG. 2, in this embodiment, the secure communication method includes the following steps. [0101]S201. A mobile terminal prohibits, by means of setting, a program in a common virtual kernel from accessing interrupt information related to a wireless communication connection that meets a preset security processing trigger condition. [0102]Optionally, the wireless communication connection may include but is not limited to: a common telephone connection, a network voice connection (including a network telephone connection or another voice connection between real-time communications clients), a network video connection, or the like. [0103]In some feasible implementations, in addition to the interrupt info/Elation related to the wireless communication connection that meets the preset security processing trigger condition, the mobile terminal may further prohibit, by means of setting, the program in the common virtual kernel from accessing some interrupt signals related to a specific type of the wireless communication connection, such as a short message or a mail. [0104]Optionally, that the wireless communication connection meets the preset security processing trigger condition may be: Another mobile terminal that establishes the wireless communication connection to the mobile terminal meets a security condition set by the mobile terminal, for example, the wireless communication connection is a wireless communication connection between the mobile terminal and a buddy in an address book, or may be: A type of the wireless communication connection meets a security type set by the mobile terminal, for example, the wireless communication connection is a telephone connection. [0105]In a specific implementation, after being powered on, the mobile terminal(String), 相关申请的交叉引用 [0001] 本申请是2015年12月24日提交的国际申请号PCT/CN2015/098761的继续申请,该国际申请要求2015年4月30日提交的中国专利申请号201510217336.8的优先权。上述申请的公开内容是 特此通过引用整体并入。 技术领域 [0002] 本申请涉及通信领域,尤其涉及一种移动通信终端的安全通信方法及移动通信终端。 背景 [0003] 随着移动通信技术的发展,移动终端得到了广泛的普及,移动终端已经成为用户日常生活中的必需品。 用户在使用移动终端工作、购物或娱乐时,会传递隐私信息。 隐私信息可能被不法分子窃听,从而导致用户隐私泄露、财产损失等严重后果。 移动通信安全越来越受到政府、社会和用户的关注,网络安全和信息安全问题甚至上升到国家战略高度。 [0004] 现有技术中,在使用移动终端发起或接听电话之前,通常会搜索并结束包含录音模块的进程,以防止通话内容被偷录,从而防止后台进程窃听。 [0005] 上述方法在移动终端操作系统可信的情况下,防止后台进程窃听。 然而,如今,随着移动终端的功能越来越丰富,移动终端的操作系统架构也越来越复杂,安全漏洞也越来越多。 因此,迫切需要开发一种能够防止操作系统攻击的通信安全技术。 概括 [0006] 本发明实施例公开了一种移动终端的安全通信方法及移动终端,以防止操作系统窃听用户的通信内容,提高移动终端的通信安全性。 [0007] 本发明实施例的第一方面公开了一种移动终端的安全通信方法,移动终端的应用处理器包括安全虚拟内核和公共虚拟内核,安全虚拟内核和公共虚拟内核共享一个安全虚拟内核。 禁止移动终端的中央处理器CPU、内存、总线和外设以及公共虚拟内核中的程序访问安全虚拟内核的应用处理器资源。 和 [0008] 安全通信方法包括: [0009] 当移动终端与另一移动终端建立无线通信连接,且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核与普通虚拟内核共享内存,访问无线通信连接需要调用的外设; [0010] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 和 [0011] 移动终端通过安全虚拟内核输出经过预设策略处理得到的通信内容。 [0012] 结合第一方面,在第一种可行的实现方式中,所述无线通信连接需要调用的外设包括录音设备,所述通信内容包括录制的音频信号; [0013]移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0014] 当通信内容为录音设备录制的音频信号时,移动终端利用安全虚拟内核对录制的音频信号进行加密处理。 和 [0015] 移动终端利用安全虚拟内核对加密处理后的音频信号进行编码,得到待发送的音频信号; 和 [0016] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0017] 通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号。 [0018] 结合第一方面或第一方面的第一种可行的实现方式,在第二种可行的实现方式中,所述无线通信连接需要调用的外设包括音频播放设备,所述通信内容包括接收到的音频信号; [0019] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0020] 当通信内容为移动终端接收到的音频信号时,移动终端使用安全虚拟内核对音频信号进行解码; 和 [0021] 移动终端利用安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号; 和 [0022] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0023] 移动终端通过安全虚拟内核控制音频播放设备播放待播放的音频信号。 [0024] 结合第一方面或第一方面的第一种至第二种可行的实现方式中的任一种,在第三种可行的实现方式中,所述无线通信连接需要调用的外设包括录像设备,所述通信 内容包括录制的视频信号; [0025] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0026] 当通信内容为视频录制设备录制的视频信号时,移动终端利用安全虚拟内核对录制的视频信号进行加密处理。 和 [0027] 移动终端利用安全虚拟内核对加密处理后的视频信号进行编码,得到待发送的视频信号; 和 [0028] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0029] 通过安全虚拟内核控制移动终端向另一移动终端发送待发送视频信号。 [0030] 结合第一方面或第一方面的第一种至第三种可行的实现方式中的任一种,在第四种可行的实现方式中,所述无线通信连接需要调用的外设包括显示器,所述通信内容包括: 接收到的视频信号; [0031] 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理,具体包括: [0032]当通信内容为移动终端接收到的视频信号时,移动终端利用安全虚拟内核对接收到的视频信号进行解码; 和 [0033] 移动终端利用安全虚拟内核对解码后的视频信号进行解密处理,得到待播放的视频信号; 和 [0034] 移动终端利用安全虚拟内核输出经过预设策略处理得到的通信内容,具体包括: [0035] 移动终端通过安全虚拟内核控制显示器播放待播放的视频信号。 [0036] 结合第一方面或第一方面的第一种至第四种可行的实现方式中的任一种,在第五种可行的实现方式中,在移动终端与另一移动终端之间建立无线通信连接之前,安全通信方法 进一步包括: [0037] 移动终端通过设置禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0038] 本发明实施例的第二方面提供了一种移动终端,该移动终端的应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享中央处理器CPU, 禁止移动终端的内存、总线和外设以及公共虚拟内核中的程序访问安全虚拟内核的应用处理器资源。 和 [0039] 移动端包括: [0040] 第一设置单元,用于当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟机中的程序 内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; [0041] 处理单元,用于通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 和 [0042] 输出单元,用于通过所述安全虚拟内核输出所述预设策略处理得到的通信内容。 [0043] 结合第二方面,在第一种可行的实现方式中,所述无线通信连接需要调用的外设包括录音设备,所述通信内容包括录制的音频信号; [0044] 处理单元包括: [0045] 第一加密子单元,用于当通信内容为录音设备录制的音频信号时,通过安全虚拟内核对录制的音频信号进行加密处理; 和 [0046] 第一编码子单元,用于使用安全虚拟内核对加密处理后的音频信号进行编码,得到待发送的音频信号; 和 [0047] 输出单元具体用于通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号。 [0048] 结合第二方面或第二方面的第一种可行的实现方式,在第二种可行的实现方式中,所述无线通信连接需要调用的外设包括音频播放设备,所述通信内容包括接收到的音频信号; [0049] 处理单元包括: [0050] 第一解码子单元,用于当所述通信内容为所述移动终端接收到的音频信号时,使用所述安全虚拟内核对所述音频信号进行解码; 和 [0051] 第一解密子单元,用于利用安全虚拟内核对解码后的音频信号进行解密处理,得到待播放音频信号; 和 [0052] 输出单元具体用于通过安全虚拟内核控制音频播放设备播放待播放音频信号。 [0053] 结合第二方面或第二方面的第一种至第二种可行的实现方式中的任一种,在第三种可行的实现方式中,所述无线通信连接需要调用的外设包括录像设备,所述通信 内容包括录制的视频信号; [0054] 处理单元包括: [0055] 第二加密子单元,用于当通信内容为视频录制设备录制的视频信号时,通过安全虚拟内核对录制的视频信号进行加密处理; 和 [0056] 第二编码子单元,用于使用安全虚拟内核对加密处理后的视频信号进行编码,得到待发送的视频信号; 和 [0057] 输出单元具体用于通过安全虚拟内核控制移动终端向另一移动终端发送待发送视频信号。 [0058] 结合第二方面或第二方面的第一种至第三种可行的实现方式中的任一种,在第四种可行的实现方式中,所述无线通信连接需要调用的外设包括显示器,所述通信内容包括: 接收到的视频信号; [0059] 处理单元包括: [0060] 第二解码子单元,用于当通信内容为移动终端接收到的视频信号时,使用安全虚拟内核对接收到的视频信号进行解码; 和 [0061] 第二解密子单元,用于利用安全虚拟内核对解码后的视频信号进行解密处理,得到待播放视频信号; 和 [0062] 输出单元具体用于通过安全虚拟内核控制显示器播放待播放视频信号。 [0063] 结合第二方面或第二方面的第一种至第四种可行的实现方式中的任一种,在第五种可行的实现方式中,所述移动终端还包括: [0064] 第二设置单元,用于通过设置禁止公共虚拟内核中的程序访问与无线通信连接相关的中断信息。 [0065] 本发明实施例中,当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止程序在 普通虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 然后通过安全虚拟内核输出经过预设的基于策略的处理得到的通信内容,从而可以防止操作系统和运行在普通虚拟内核中的程序获得未经处理的通信内容,并且操作 还可以防止系统通过共享内存或相关外设窃听通信内容,提高移动终端的通信安全性。 附图说明 [0066]为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简要说明。 显然,以下描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有做出创造性劳动的情况下,仍然可以从这些附图中获得其他附图。 [0067] 图1为本发明移动终端安全通信方法一个实施例的流程示意图; [0068] 图2为本发明移动终端安全通信方法另一实施例的流程示意图; [0069] 图3为本发明移动终端安全通信方法又一实施例的流程示意图; [0070] 图4为本发明移动终端一个实施例的结构示意图; [0071] 图5为本发明移动终端另一实施例的结构示意图; [0072] 图6为本发明移动终端又一实施例的结构示意图; 和 [0073] 图7为本发明移动终端又一实施例的结构示意图。 详细说明 [0074] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 显然,所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0075] 下面结合附图对本发明实施例提供的一种移动终端的安全通信方法及移动终端进行详细说明。 在本发明实施例中,移动终端包括但不限于手机、个人电脑、笔记本电脑等可用于通信的终端。 [0076] 参见图1,图1为本发明移动终端安全通信方法实施例的流程示意图。 如图1所示,在本实施例中,安全通信方法包括以下步骤。 [0077] 小号 101 . 当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问共享 安全虚拟内核和公共虚拟内核之间的内存,以及访问需要为无线通信连接调用的外设。 [0078] 本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0079] 具体实施中,移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0080]在一种可行的实施方式中,移动终端可以是采用ARM(高级精简指令集计算机)处理器的基于TrustZone技术的移动终端。 [0081] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0082] 在一些可行的实施方式中,在本发明实施例中,当移动终端与另一移动终端之间还可以进行短信通信或邮件通信时,通过设置禁止公共虚拟内核中的程序访问。 访问安全虚拟内核和普通虚拟内核之间的共享内存,评估短信通信或邮件通信需要调用的外设。 短信通信或邮件通信需要调用的外设可以包括按键、键盘、平板电脑、显示器中的一种或多种。 [0083] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进行拨号操作时,或者当检测到移动终端登录到实时通信客户端时,可以认为移动终端之间建立了无线通信连接。 和另一个移动终端。 [0084] 在一些可行的实施方式中,可以通过检测与无线通信连接相关的一些中断信号,确定移动终端与另一移动终端建立无线通信连接。 例如,当另一移动终端来电时,应用处理器接收基带处理器发送的来电信息中断请求。 [0085] 可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的其他移动终端满足移动终端设置的安全条件,例如,无线通信连接为a 移动终端与通讯录中的好友之间的无线通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0086] 在一些可行的实施方式中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 例如,当基带系统检测到任何来电信号或检测到通讯录中好友的来电信号时,向应用处理器发送来电信息中断请求。 由于通过预先设置禁止普通虚拟内核中的程序访问来电信息中断请求,应用处理器在接收到来电信息中断请求后,通过安全虚拟内核处理来电信息中断请求。 [0087] 可选地,当无线通信连接涉及语音通话时(如普通电话、网络电话、实时通信客户端发起的语音会话),需要调用的外设至少包括: 录音装置及录音播放装置。 在具体实现中,录音设备和音频播放设备可以为同一设备,例如移动终端的麦克风。 [0088]可选地,当无线通信连接涉及视频通话时,需要通话的外设至少包括视频录制设备、录音设备、音频播放设备和显示器,例如摄像头、麦克风、 以及移动终端的显示器。 [0089] 在一些可行的实施方式中,移动终端可以通过GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息为 只能在安全虚拟内核中访问。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0090] 在一些可行的实施方式中,移动终端通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域或非安全内存区域。 -secure memory areas,TZASC可以禁止运行在common virtual kernel中的程序访问secure memory area。 [0091] 在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0092] 小号 102 . 移动终端通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理。 [0093] 可选的,无线通信连接对应的通信内容包括移动终端要发送的通信内容和移动终端接收的通信内容。 [0094] 可选的,对于待发送的通信内容,预设的基于策略的处理可以包括加密、模数转换、编码、调制等中的一种或多种。 对于接收到的通信内容,预设的基于策略的处理可以包括解密、解调、解码、数模转换等中的一种或多种。 预设策略处理是通过移动终端的安全虚拟内核进行的,普通虚拟内核中的程序无法访问预设策略处理前获取的通信内容。 [0095] 在具体实现中,由于运行在普通虚拟内核中的操作系统代码量较大,因此存在的安全漏洞数量较多。 由于在安全的虚拟内核中运行的模块中的代码量很小,因此可以很容易地验证安全性。 通过安全虚拟内核对通信内容进行预设的策略处理,可以避免运行在普通虚拟内核中的操作系统获取进行预设策略处理前获得的通信内容,操作系统 可以防止窃听通信内容。 [0096] 小号 103 . 移动终端通过安全虚拟内核输出经过预设策略处理得到的通信内容。 [0097]具体实施中,移动终端在对移动终端要发送的通信内容进行预设的策略处理后,可以通过射频模块或无线网络连接模块发送该要发送的通信内容。 . 可以通过移动终端的射频模块发送电话或短信的通信内容; 可以通过无线网络连接模块发送邮件、网络语音通话、视频通话等通信内容。 在本发明实施例中,网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0098] 在对移动终端接收到的通信内容进行预设的基于策略的处理后,移动终端可以输出接收到的通信内容。 可选的,如果接收到的通信内容为语音,则可以通过音频播放设备(例如麦克风)输出接收到的通信内容; 如果接收到的通讯内容为视频,则可以通过显示器和音频播放设备输出接收到的通讯内容。 或者,如果接收到的通信内容为文本或图片,则可以通过显示器输出接收到的通信内容。 [0099] 本发明实施例中,当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,该移动终端通过设置的方式禁止程序在 普通虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 然后通过安全虚拟内核输出经过预设的基于策略的处理得到的通信内容,从而可以防止操作系统和运行在普通虚拟内核中的程序获得未经处理的通信内容,并且操作 还可以防止系统通过共享内存或相关外设窃听通信内容,提高移动终端的通信安全性。 [0100] 参见图2,图2为本发明移动终端安全通信方法另一实施例的流程示意图。 如图2所示,在本实施例中,安全通信方法包括以下步骤。 [0101] 小号 201 . 移动终端通过设置禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0102] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0103] 在一些可行的实施方式中,移动终端除了满足预设安全处理触发条件的与无线通信连接相关的中断信息/Elation外,还可以通过设置的方式禁止公共虚拟内核中的程序访问某些 与特定类型的无线通信连接相关的中断信号,例如短消息或邮件。 [0104]可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的另一移动终端满足移动终端设置的安全条件,例如,无线通信连接是无线的。 移动终端与通讯录中的好友之间的通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0105] 在具体实施中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 当移动终端接收到满足预设安全处理触发条件的与无线通信连接相关的中断信息时,移动终端将中断信息交由安全虚拟内核处理。 [0106] 在一些可行的实施方式中,移动终端可以通过GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息为 只能在安全虚拟内核中访问。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0107] 小号 202 . 当移动终端与另一移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问共享 安全虚拟内核和公共虚拟内核之间的内存,以及访问需要为无线通信连接调用的外设。 [0108] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进行拨号操作时,或者当检测到移动终端进入拨号界面时,可以认为移动终端与另一移动终端建立了电话连接。 [0109] 在一些可行的实施方式中,可以通过检测与无线通信连接相关的一些中断信号,确定移动终端与另一移动终端建立无线通信连接。 例如,当另一移动终端来电时,移动终端的应用处理器接收基带处理器发送的来电信息中断请求。 [0110] 本实施例以无线通信连接为语音连接为例进行说明。 语音连接包括电话连接或网络语音连接,语音连接需要调用的外设至少包括录音设备和音频播放设备。 在具体实现中,录音设备和音频播放设备可以为同一设备,例如移动终端的麦克风。 [0111]本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0112] 具体实施中,移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0113] 在一种可行的实施方式中,移动终端可以是采用ARM处理器的基于TrustZone技术的移动终端。 [0114] 在一些可行的实施方式中,移动终端通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域或非安全内存区域。 -secure memory areas,TZASC可以禁止运行在common virtual kernel中的程序访问secure memory area。 [0115] 在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0116] 小号 203 . 当无线通信连接对应的通信内容为录音设备录制的音频信号时,移动终端通过安全虚拟内核对录制的音频信号进行加密处理。 [0117] 在本发明实施例中,当无线通信连接为语音连接时,无线通信连接对应的通信内容包括移动终端录制的音频信号和移动终端接收的音频信号。 移动终端录制的音频信号是本移动终端用户在通话过程中要传达给另一移动终端用户的通话内容,移动终端接收到的音频信号是本移动终端用户要传达给另一移动终端用户的通话内容。 另一移动终端的用户在通话过程中与移动终端的用户通话。 具体地,录制的音频信号由移动终端的录音设备(例如麦克风)录制。 安全虚拟内核在从录音设备中获取到录制的音频信号后,可以对录制的音频信号进行加密处理,以防止移动通信链路受到窃听攻击时通话内容泄露。 [0118] 小号 204 . 移动终端通过安全虚拟内核对加密处理得到的音频信号进行编码,得到待发送的音频信号。 [0119] 在一些可行的实施方式中,当无线通信连接为电话连接时,利用安全虚拟内核对加密处理得到的音频信号进行编码可以包括:利用安全虚拟内核指示基带处理器。 移动终端对加密处理后的音频信号进行模数转换、语音编码、信道编码、物理层加密调制。 可选地,为了提高通话质量,还可以指示基带处理器对录制的音频信号进行交织、均衡、滤波等其他处理。 [0120]在一些可行的实施方式中,当所述无线通信连接为网络语音连接时,所述利用安全虚拟内核对加密处理得到的音频信号进行编码具体可以包括: 利用硬件资源或者软件资源进行 对加密处理得到的音频信号进行安全虚拟内核的构建、模数转换、语音编码、信道编码、物理层加密。 可选地,为了提高网络语音通话质量,还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0121] 小号 205 . 通过安全虚拟内核控制移动终端向另一移动终端发送待发送的音频信号。 [0122] 在一些可行的实施方式中,当无线通信连接为电话连接时,通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号可以包括:控制通过使用 安全虚拟内核,移动终端的射频模块,用于将待发送的音频信号发送给另一移动终端。 [0123] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号可以包括: 利用安全虚拟内核,移动终端的无线网络连接模块(例如Wi-Fi模块)将待发送的音频信号发送至另一移动终端。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 安全虚拟内核在获取到待发送音频信号后,可以将待发送音频信号发送给普通虚拟内核,并指示普通虚拟内核将待发送音频信号发送给其他虚拟内核。 移动终端通过使用无线网络连接模块。 [0124] 小号 206 . 当无线通信连接对应的通信内容为移动终端接收到的音频信号时,移动终端通过安全虚拟内核对音频信号进行解码。 [0125] 在一些可行的实施方式中,当无线通信连接为电话连接时,移动终端通过射频模块接收另一移动终端通过手机网络发送的音频信号。 此时,通过安全虚拟内核对音频信号进行解码可以包括:通过安全虚拟内核指示基带处理器进行解调、声道解码、物理层解密、语音解码、数字解码等处理。 对接收到的音频信号进行模拟转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0126] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,移动终端通过无线网络连接模块接收另一移动终端通过互联网发送的音频信号。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 普通虚拟内核控制无线网络连接模块接收另一移动终端发送的音频信号,并将接收到的音频信号传输给安全虚拟内核进行处理。 此时,利用安全虚拟内核对音频信号进行解码可以包括:利用安全虚拟内核对接收到的音频信号进行声道解码、物理层解密、语音解码和数模转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0127] 小号 207. 移动终端通过安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号。 [0128] 在一些可行的实施方式中,另一移动终端在对接收到的音频信号进行编码发送之前,首先对接收到的音频信号进行上层加密,以防止移动通信链路受到窃听攻击时通话内容泄露。 移动终端接收上层加密处理后的音频信号。 移动终端在对音频信号进行解码后,还需要对音频信号进行解密处理。 [0129] 小号 208 . 移动终端通过安全虚拟内核控制音频播放设备播放待播放的音频信号。 [0130] 安全虚拟内核对接收到的音频信号进行一系列处理后,安全虚拟内核可以控制移动终端的音频播放设备播放待播放的音频信号。 移动终端的音频播放设备可以是麦克风。 [0131] 本发明实施例中,当一个移动终端与另一个移动终端之间建立语音连接,并且该语音连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共节目。 虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问相关的外设,如录音设备或音频播放设备; 通过安全虚拟内核对移动终端录制的音频信号和移动终端接收的音频信号进行处理; 然后使用安全虚拟内核输出处理后的通信内容,可以防止操作系统和运行在普通虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听通信内容 通过共享内存或相关外设读取内容,提高了移动终端的通信安全性。 [0132] 参见图3,图3为本发明移动终端安全通信方法的又一实施例的流程示意图。 如图3所示,在本实施例中,安全通信方法包括以下步骤。 [0133] 小号 301 . 移动终端通过设置禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0134] 在具体实现中,对于S的具体实现 301 ,参考步骤S中描述的实现 201 在图2所示的实施例中,在此不再赘述。 [0135] 小号 302 . 当移动终端与另一移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共虚拟内核中的程序访问共享 安全虚拟内核和公共虚拟内核之间的内存,以及访问需要为无线通信连接调用的外设。 [0136] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进入网络电话程序画面,或者当检测到移动终端选择了实时通信客户端的视频通话选项时,可以认为是视频通话连接。 在移动终端和另一个移动终端之间建立。 [0137]在一些可行的实施方式中,可以通过检测一些与网络语音连接相关的中断信号,确定移动终端与另一移动终端之间建立了电话连接。 例如,当另一移动终端发送视频通话连接请求时,应用处理器检测到视频通话连接中断请求。 [0138] 本实施例以无线通信连接为视频通话连接为例进行说明。 视频通话连接需要调用的外设包括视频录制设备、录音设备、音频播放设备和显示器。 在具体实现中,视频录制设备可以是移动终端的摄像头,录音设备和音频播放设备可以是同一设备,例如移动终端的麦克风。 [0139] 本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0140] 具体实施中,移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0141] 在一种可行的实施方式中,移动终端可以是采用ARM处理器的基于TrustZone技术的移动终端。 [0142] 在一些可行的实施方式中,移动终端可以通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域,或者 非安全内存区,TZASC可以禁止公共虚拟内核中运行的程序访问安全内存区。 [0143] 在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0144] 小号 303 . 当无线通信连接对应的通信内容为移动终端录制的音视频信号时,移动终端通过安全虚拟内核对录制的音视频信号进行加密处理。 [0145] 在本发明实施例中,当无线通信连接为视频通话连接时,无线通信连接对应的通信内容包括移动终端录制的音视频信号和移动终端接收的音视频信号。 移动终端录制的音视频信号包括移动终端的录像设备录制的视频信号和移动终端的录音设备录制的音频信号。 [0146] 在移动终端与另一移动终端进行视频通话过程中,移动终端通过安全虚拟内核从录像设备和录音设备获取录制的音视频信号后,可以进行加密处理 在录制的音频和视频信号上,以防止在对移动通信链路进行窃听攻击时泄露通话内容。 [0147] 小号 304. 移动终端通过安全虚拟内核对加密处理后的音视频信号进行编码,得到待发送的音视频信号。 [0148] 在一些可行的实施方式中,所述利用安全虚拟内核对加密处理后的音视频信号进行编码,可以包括: 利用安全虚拟内核对加密后的视频信号进行编码和物理层加密,并进行处理 利用安全虚拟内核对加密后的音频信号进行模数转换、语音编码、信道编码、物理层加密等。 视频信号的编码标准可以根据视频通话连接的分辨率要求或压缩率要求来选择,例如H.261、H.262、H.263、H.264、MPEG-2或MPEG -4。 本发明对此不作限制。 可选地,为了提高视频通话质量,还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0149] 小号 305 . 通过安全虚拟内核控制移动终端向其他移动终端发送待发送的音视频信号。 [0150] 在一些可行的实施方式中,为了节省移动终端用户的开销,通过移动终端的无线网络连接模块将待发送的音视频信号发送给其他移动终端。 [0151] 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 此时,安全虚拟内核可以将待发送的音视频信号发送至普通虚拟内核,并指示普通虚拟内核将待发送的音视频信号发送至另一移动终端。 使用无线网络连接模块和互联网。 无线网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0152] 小号 306 . 当无线通信连接对应的通信内容为移动终端接收到的音视频信号时,移动终端通过安全虚拟内核对接收到的音视频信号进行解码。 [0153] 在一些可行的实施方式中,为了节省移动终端用户的开销,移动终端通过无线网络连接模块接收另一移动终端发送的音视频信号。 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 此时,普通虚拟内核控制无线网络连接模块接收其他移动终端发送的音视频信号,并将接收到的音视频信号传输给安全虚拟内核进行处理。 接收到的音频和视频信号可以包括视频信号和音频信号。 [0154] 在一种可行的实施方式中,利用安全虚拟内核对接收到的音视频信号进行解码可以包括: 利用安全虚拟内核对接收到的视频信号进行解码具体如下: 对视频信号进行物理层解密和视频解码。 在接收到的音频和视频信号中; 所述安全虚拟内核对接收到的音频信号进行解码具体为:对接收到的音视频信号中的音频信号进行物理层解密、信道解码、语音解码、数模转换等处理。 . 视频信号的解码标准可以包括H.261、H.262、H.263、H.264、MPEG-2、MPEG-4等,具体根据视频播放时选择的编码标准确定。 被编码。 可选地,为了提高视频通话质量,还可以对接收到的音视频信号中的音频信号进行均衡、声道分离、解交织等其他处理。 [0155]在具体实现中,移动终端可以通过安全虚拟内核分别对接收到的音频信号和视频信号进行解码,得到解码后的音频信号和解码后的视频信号。 [0156] 小号 307 . 移动终端通过安全虚拟内核对解码后的音视频信号进行解密处理,得到待播放的音视频信号。 [0157] 在一些可行的实施方式中,在对移动终端接收到的音视频信号进行编码压缩发送之前,另一移动终端首先对接收到的音视频信号进行上层加密,以防止窃听攻击时通话内容泄露 在移动通信链路上。 移动终端接收经过上层加密处理后的音视频信号。 在使用安全虚拟内核对音视频信号进行解码后,移动终端还需要使用安全虚拟内核对音视频信号进行解密处理。 [0158] 在具体实现中,移动终端可以通过安全虚拟内核分别对解码后的音频信号和解码后的视频信号进行解密处理,得到待播放的音频信号和待播放的视频。 信号。 [0159] 小号 308 . 移动终端通过安全虚拟内核控制音频播放设备和显示器播放待播放的音视频信号。 [0160] 安全虚拟内核对接收到的音视频信号进行一系列处理得到待播放的音视频信号后,安全虚拟内核可以控制移动终端的音频播放设备和显示器进行播放。 播放待播放的音视频信号。 待播放音视频信号中的待播放音频信号可以通过移动终端的音频播放设备(例如麦克风)进行播放,待播放视频信号在 可以通过移动终端的显示器播放待播放的音视频信号。 [0161] 本发明实施例中,当一个移动终端与另一个移动终端之间建立视频通话连接,并且该视频通话连接满足预设的安全处理触发条件时,移动终端通过设置禁止节目在 通用虚拟内核访问安全虚拟内核和通用虚拟内核之间的共享内存,访问相关的外围设备,如视频录制设备、录音设备、音频播放设备或显示器; 利用安全虚拟内核对移动终端录制的音视频信号和移动终端接收的音视频信号进行处理; 然后使用安全虚拟内核输出处理后的通信内容,可以防止操作系统和运行在普通虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听通信内容 通过共享内存或相关外设读取内容,提高了移动终端的通信安全性。 [0162] 参见图4,图4为本发明移动终端一个实施例的结构示意图。 如图4所示,本实施例中,移动终端包括第一设置单元 401 , 一个处理单元 402 , 和一个输出单元 403 . [0163] 第一设定单位 401 用于当所述移动终端与另一移动终端建立无线通信连接,且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核和公共虚拟内核之间的共享内存以及访问需要为无线通信连接调用的外设。 [0164]本发明实施例中,移动终端的CPU(Central Processing Unit)至少包括应用处理器。 当移动终端为手机时,移动终端的CPU还包括基带处理器。 应用处理器包括安全虚拟内核和普通虚拟内核,安全虚拟内核和普通虚拟内核共享移动终端的CPU、内存、外设和总线。 在具体实现中,安全虚拟内核独占部分应用处理器硬件资源,禁止普通虚拟内核中的程序访问安全虚拟内核独占的应用处理器资源。 [0165] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0166] 在一些可行的实施方式中,在本发明实施例中,当移动终端与另一移动终端之间还可以进行短信通信或邮件通信时,通过设置禁止公共虚拟内核中的程序访问。 访问安全虚拟内核和普通虚拟内核之间的共享内存,评估短信通信或邮件通信需要调用的外设。 短信通信或邮件通信需要调用的外设可以包括按键、键盘、平板电脑、显示器中的一种或多种。 [0167] 在一些可行的实施方式中,可以通过检测移动终端的一些触发动作,确定移动终端与另一移动终端建立无线通信连接。 例如,当检测到移动终端进行拨号操作时,或者当检测到移动终端登录到实时通信客户端时,可以认为移动终端之间建立了无线通信连接。 和另一个移动终端。 [0168] 在一些可行的实施方式中,可以通过检测与无线通信连接相关的一些中断信号,确定移动终端与另一移动终端建立无线通信连接。 例如,当另一移动终端来电时,应用处理器接收基带处理器发送的来电信息中断请求。 [0169] 可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的其他移动终端满足移动终端设置的安全条件,例如,无线通信连接为a 移动终端与通讯录中的好友之间的无线通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0170] 在一些可行的实施方式中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 例如,当基带系统检测到任何来电信号或检测到通讯录中好友的来电信号时,向应用处理器发送来电信息中断请求。 由于通过预先设置禁止普通虚拟内核中的程序访问来电信息中断请求,应用处理器在接收到来电信息中断请求后,通过安全虚拟内核处理来电信息中断请求。 [0171]参见图5,该移动终端可以是采用ARM处理器的基于TrustZone技术的移动终端。 移动终端的片上系统(SoC)集成了CPU、直接存储器存取(DMA)、安全随机存取存储器(RAM)、安全启动只读存储器(ROM)、中断控制器( GIC或TZIC)、TZASC、TZPC、动态存储控制器(DMC)、动态随机存取存储器(DRAM)等。 [0172] SoC 中的组件通过使用高级可扩展接口 (AXI) 总线连接。 安全RAM和安全ROM分别通过软件或硬件机制隔离,用于存储运行在安全虚拟内核中的模块。 TZASC被配置为对共享内存(即DRAM)的安全属性进行分类,可以被配置为将DRAM的一部分设置为安全内存区域,而将DRAM的其余部分设置为非安全内存区域 内存区域。 当普通虚拟内核发起对安全内存区域的访问请求时,该访问请求被拒绝。 SoC通过TZPC配置外设的安全属性,通过AXI-to-APB桥与外设进行通信。 AXI-to-APB桥可以感知当前被事务访问的外设的安全属性,并且当公共虚拟内核的事务访问安全外设时,AXI-to-APB拒绝访问。 SoC可以通过使用GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息仅在安全虚拟机中被访问 核心。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0173] 在一些可行的实施方式中,当移动终端为手机时,移动终端包括应用处理器和基带处理器,应用处理器包括安全虚拟内核S和通用虚拟内核NS,安全虚拟内核和通用虚拟内核 虚拟内核共享移动终端的CPU、内存、外设和总线。 禁止普通虚拟内核中的程序访问安全虚拟内核的硬件资源。 移动终端的基带系统运行在基带处理器中; 一些安全模块运行在安全虚拟内核中; 移动终端的操作系统运行在通用的虚拟内核中,如Android、iOS、Windows Phone等。 [0174] 可选地,当无线通信连接涉及语音通话时(如普通电话、网络电话、或其他通过实时通信客户端发起的语音会话),需要调用的外设至少包括 录音装置及录音播放装置。 在具体实现中,录音设备和音频播放设备可以为同一设备,例如移动终端的麦克风。 [0175] 可选地,当无线通信连接涉及视频通话时,需要通话的外设至少包括视频录制设备、录音设备、音频播放设备和显示器,例如摄像头、麦克风、 以及移动终端的显示器。 [0176] 在一些可行的实施方式中,移动终端通过TZASC(TrustZone address space controller)将物理内存划分为多个内存区域,并通过运行在安全虚拟内核中的软件将部分内存区域配置为安全内存区域或非安全内存区域。 -secure memory areas,TZASC可以禁止运行在common virtual kernel中的程序访问secure memory area。 [0177]在一些可行的实施方式中,移动终端通过TZPC(TrustZone protection controller)配置外设的安全属性,将外设分类为安全外设或非安全外设,并禁止运行在公共虚拟内核中的程序访问。 访问安全外围设备。 [0178] 处理单元 402 用于通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理。 [0179] 可选的,无线通信连接对应的通信内容包括移动终端要发送的通信内容和移动终端接收的通信内容。 [0180] 可选的,对于待发送的通信内容,预设的基于策略的处理可以包括加密、模数转换、编码、调制等中的一种或多种。 对于接收到的通信内容,预设的基于策略的处理可以包括解密、解调、解码、数模转换等中的一种或多种。 预设策略处理是通过移动终端的安全虚拟内核进行的,普通虚拟内核中的程序无法访问预设策略处理前获取的通信内容。 [0181] 在具体实现中,由于运行在普通虚拟内核中的操作系统代码量较大,因此存在的安全漏洞数量较多。 由于在安全的虚拟内核中运行的模块中的代码量很小,因此可以很容易地验证安全性。 通过安全虚拟内核或基带处理器对通信内容进行预设的策略处理,可以避免运行在普通虚拟内核中的操作系统获取进行预设策略处理前的通信内容, 可以防止操作系统窃听通信内容。 [0182] 输出单元 403 用于通过安全虚拟内核输出经过预设策略处理得到的通信内容。 [0183] 具体实施中,移动终端在对移动终端要发送的通信内容进行预设的策略处理后,可以通过射频模块或无线网络连接模块发送该要发送的通信内容。 . 可以通过移动终端的射频模块发送电话或短信的通信内容; 可以通过网络连接模块发送邮件、网络语音通话、视频通话等通信内容。 在本发明实施例中,网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0184] 在对移动终端接收到的通信内容进行预设的基于策略的处理后,移动终端可以输出接收到的通信内容。 可选的,如果接收到的通信内容为语音,则可以通过音频播放设备(例如麦克风)输出接收到的通信内容; 如果接收到的通讯内容为视频,则可以通过显示器和音频播放设备输出接收到的通讯内容。 或者,如果接收到的通信内容为文本或图片,则可以通过显示器输出接收到的通信内容。 [0185]本发明实施例中,当一个移动终端与另一个移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,该移动终端通过设置的方式禁止程序在 普通虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问无线通信连接需要调用的外设; 通过安全虚拟内核对无线通信连接对应的通信内容进行预设策略处理; 然后通过安全虚拟内核输出经过预设的基于策略的处理得到的通信内容,从而可以防止操作系统和运行在普通虚拟内核中的程序获得未经处理的通信内容,并且操作 还可以防止系统通过共享内存或相关外设窃听通信内容,提高移动终端的通信安全性。 [0186] 参见图6,图6为本发明移动终端又一实施例的结构示意图。 如图6所示,本实施例中,移动终端包括第一设置单元 601 , 一个处理单元 602 , 一个输出单元 603 , 和第二个设定单位 604 . [0187] 第二设定单位 604 用于通过设置禁止普通虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0188] 可选的,无线通信连接可以包括但不限于:普通电话连接、网络语音连接(包括实时通信客户端之间的网络电话连接或其他语音连接)、网络视频连接等。 [0189] 在一些可行的实施方式中,移动终端除了满足预设的安全处理触发条件的与无线通信连接相关的中断信息外,还可以通过设置的方式,禁止公共虚拟内核中的程序访问一些中断信号。 与特定类型的无线通信连接有关,例如短消息或邮件。 [0190] 可选地,无线通信连接满足预设的安全处理触发条件可以为: 与移动终端建立无线通信连接的另一移动终端满足移动终端设置的安全条件,例如,无线通信连接是无线的。 移动终端与通讯录中的好友之间的通信连接,或者可以是: 无线通信连接的类型满足移动终端设置的安全类型,例如,无线通信连接为电话连接。 [0191] 在具体实施中,移动终端在开机后,可以通过设置的方式,禁止公共虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 当移动终端接收到满足预设安全处理触发条件的与无线通信连接相关的中断信息时,移动终端将中断信息交由安全虚拟内核处理。 [0192] 在一些可行的实施方式中,第二设置单元 604可以通过GIC(通用中断控制器)或TZIC(TrustZone中断控制器)将与无线通信连接相关的中断信息设置为安全中断,使得中断信息仅在安全虚拟内核中被访问。 具体实现中,GIC或TZIC连接移动终端的所有中断源,可以先拦截移动终端的中断请求; GIC或TZIC将与无线通信连接相关的中断请求交由安全虚拟内核处理。 [0193] 第一设定单位 601 用于当移动终端与另一移动终端之间建立无线通信连接,并且该无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核和普通虚拟内核之间的共享内存,以及访问无线通信连接需要调用的外设。 [0194] 在一些可行的实现中,第一个设置单元 601 可以执行第一设置单元执行的实现 401 如图4所示实施例所述。在本实施例中,无线通信连接为语音连接,包括电话连接或网络语音连接。 此时,无线通信连接需要调用的外设包括录音设备和音频播放设备,第一设置单元 601 可以具体用于通过设置禁止公共虚拟内核中的程序访问安全虚拟内核和公共虚拟内核之间的共享内存以及访问移动设备的录音设备和音频播放设备。 终端。 判断移动终端与其他移动终端建立语音连接的具体实现参见步骤S的相关描述 202 在图2所示的实施例中。 [0195] 在一些可行的实现中,处理单元 602 可以执行由处理单元执行的实现 402 描述在图4所示的实施例中。在该实施例中,处理单元 602 可能包括第一加密子单元 6021 , 第一个编码亚单位 6022 , 第一个解码子单元 6023 , 和第一个解密子单元 6024 . [0196] 第一加密子单元 6021 用于当通信内容为录音设备录制的音频信号时,通过安全虚拟内核对录制的音频信号进行加密处理。 [0197] 在本发明实施例中,当无线通信连接为语音连接时,无线通信连接对应的通信内容包括移动终端录制的音频信号和移动终端接收的音频信号。 移动终端录制的音频信号是本移动终端用户在通话过程中要传达给另一移动终端用户的通话内容,移动终端接收到的音频信号是本移动终端用户要传达给另一移动终端用户的通话内容。 另一移动终端的用户在通话过程中与移动终端的用户通话。 [0198] 具体地,录制的音频信号由移动终端的录音设备(例如麦克风)录制。 安全虚拟内核从录音设备获取录制的音频信号后,可以通过第一加密子单元对录制的音频信号进行加密处理 6021 ,以防止在对移动通信链路进行窃听攻击时泄露通话内容。 [0199] 第一编码亚单位 6022 用于通过安全虚拟内核对加密处理得到的音频信号进行编码,得到待发送的音频信号。 [0200]在一些可行的实施方式中,当无线通信连接为电话连接时,利用安全虚拟内核对加密处理得到的音频信号进行编码可以包括:利用安全虚拟内核指示基带处理器: 移动终端对加密处理后的音频信号进行模数转换、语音编码、信道编码、物理层加密调制。 可选地,为了提高通话质量,还可以指示基带处理器对录制的音频信号进行交织、均衡、滤波等其他处理。 [0201] 在一些可行的实施方式中,当所述无线通信连接为网络语音连接时,所述利用安全虚拟内核对加密处理得到的音频信号进行编码具体可以包括: 利用硬件资源或者软件资源进行 对加密处理得到的音频信号进行安全虚拟内核的构建、模数转换、语音编码、信道编码、物理层加密。 可选地,为了提高网络语音通话质量,还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0202] 第一解码子单元 6023 用于当通信内容为移动终端接收到的音频信号时,通过安全虚拟内核对音频信号进行解码。 [0203] 在一些可行的实施方式中,当无线通信连接为电话连接时,移动终端通过射频模块接收另一移动终端通过手机网络发送的音频信号。 此时,通过安全虚拟内核对音频信号进行解码可以包括:通过安全虚拟内核指示基带处理器进行解调、声道解码、物理层解密、语音解码、数字解码等处理。 对接收到的音频信号进行模拟转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0204] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,移动终端通过无线网络连接模块接收其他移动终端通过互联网发送的音频信号。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 普通虚拟内核控制无线网络连接模块接收其他移动终端发送的音频信号,并将接收到的音频信号传输给安全虚拟内核进行处理。 此时,利用安全虚拟内核对音频信号进行解码可以包括:利用安全虚拟内核对接收到的音频信号进行声道解码、物理层解密、语音解码和数模转换。 可选地,为了提高通话质量,还可以对接收到的音频信号进行均衡、声道分离、解交织等其他处理。 [0205] 第一解密子单元 6024 用于通过安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号。 [0206] 在一些可行的实施方式中,另一移动终端在对接收到的音频信号进行编码发送之前,首先对接收到的音频信号进行上层加密,以防止移动通信链路受到窃听攻击时通话内容泄露。 移动终端接收上层加密处理后的音频信号。 解码音频信号后,第一个解密子单元 6024 对音频信号进行解密处理。 [0207] 在一些可行的实现中,输出单元 603 可以执行由输出单元执行的实现 403在图4所示的实施例中描述。在本发明实施例中,输出单元 603 还可以具体用于: 通过安全虚拟内核控制移动终端向其他移动终端发送待发送音频信号。 或者,通过安全虚拟内核控制音频播放设备播放待播放的音频信号。 [0208] 在一些可行的实施方式中,当无线通信连接为电话连接时,通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号可以包括:控制通过使用 安全虚拟内核,移动终端的射频模块,用于将待发送的音频信号发送给其他移动终端。 [0209] 在一些可行的实施方式中,当无线通信连接为网络语音连接时,通过安全虚拟内核控制移动终端向其他移动终端发送待发送音频信号可以包括: 利用安全虚拟内核,移动终端的无线网络连接模块(例如Wi-Fi模块)将待发送的音频信号发送给其他移动终端。 具体地,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 安全虚拟内核在获取到待发送音频信号后,可以将待发送音频信号发送给普通虚拟内核,并指示普通虚拟内核将待发送音频信号发送给其他虚拟内核。 移动终端通过使用无线网络连接模块。 [0210] 安全虚拟内核对接收到的音频信号进行一系列处理后,安全虚拟内核可以控制移动终端的音频播放设备播放待播放的音频信号。 移动终端的音频播放设备可以是麦克风。 本发明实施例中,当一个移动终端与另一个移动终端之间建立语音连接,并且该语音连接满足预设的安全处理触发条件时,移动终端通过设置禁止公共节目。 虚拟内核访问安全虚拟内核和普通虚拟内核之间的共享内存,访问相关的外设,如录音设备或音频播放设备; 利用移动终端的安全虚拟内核和基带处理器获取并处理音频信号; 然后将处理后的音频信号发送或输出给其他移动终端,可以防止操作系统和运行在公共虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听。 通过共享内存或相关外设获取通信内容,提高移动终端的通信安全性。 [0211] 参见图7,图7为本发明移动终端又一实施例的结构示意图。 如图7所示,本实施例中,移动终端包括第一设置单元 701 , 一个处理单元 702 , 一个输出单元 703 , 和第二个设定单位 704 . [0212] 第二设定单位 704 用于通过设置禁止普通虚拟内核中的程序访问满足预设安全处理触发条件的无线通信连接相关的中断信息。 [0213] 在一些可行的实施方式中,第二设置单元 704 可以执行第二设置单元执行的实现 604 在图6所示的实施例中描述。 [0214] 第一设定单位 701用于当所述移动终端与另一移动终端之间建立无线通信连接,并且所述无线通信连接满足预设的安全处理触发条件时,通过设置禁止公共虚拟内核中的程序访问 安全虚拟内核和公共虚拟内核之间的共享内存以及访问需要为无线通信连接调用的外设。 [0215] 在一些可行的实现中,第一个设置单元 701 可以执行第一设置单元执行的实现 401 如图4所示的实施例所述。在本实施例中,无线通信连接为视频通话连接,无线通信连接需要调用的外设包括视频录制设备、录音设备、音频播放设备 设备和显示器。 在这种情况下,第一个设置单元 701 可以具体用于通过设置禁止公共虚拟内核中的程序访问安全虚拟内核和公共虚拟内核之间的共享内存以及访问视频录制设备、音频录制设备、音频播放设备 , 以及移动终端的显示。 确定移动终端与其他移动终端建立视频通话连接的具体实现参见步骤S的相关描述 302 在图3所示的实施例中。 [0216] 在一些可行的实现中,处理单元 702 可以执行由处理单元执行的实现 402 描述在图4所示的实施例中。在该实施例中,处理单元 702 可能包括第一加密子单元 7021 , 第二个加密子单元 7022 , 第一个编码亚单位 7023 , 第二个编码亚基 7024 , 第一个解码子单元 7025 , 第二个解码子单元 7026 , 第一个解密子单元 7027 , 和第二个解密子单元 7028 . [0217] 第一加密子单元 7021 用于当通信内容为录音设备录制的音频信号时,通过安全虚拟内核对录制的音频信号进行加密处理。 [0218] 第二个加密子单元 7021 用于当通信内容为视频录制设备录制的视频信号时,通过安全虚拟内核对录制的视频信号进行加密处理。 [0219] 在本发明实施例中,当无线通信连接为视频通话连接时,无线通信连接对应的通信内容包括移动终端录制的音频信号、移动终端录制的视频信号、音频信号。 移动终端接收到的视频信号,以及移动终端接收到的视频信号。 [0220] 在移动终端与另一移动终端进行视频通话过程中,移动终端通过安全虚拟内核从视频录制设备和音频录制设备获取录制的音频信号和录制的视频信号后,可以执行 对录制的音频信号和录制的视频信号进行加密处理,以防止在移动通信链路被窃听攻击时泄露通话内容。 [0221] 在一种可行的实现方式中,可以通过第一加密子单元进行加密处理 7021 , 对移动终端录制的音视频信号中的音频信号进行加密处理, 采用第二加密子单元 7022 ,关于移动终端录制的音视频信号中的视频信号。 [0222] 第一编码亚单位 7023 用于通过安全虚拟内核对加密处理得到的音频信号进行编码,得到待发送的音频信号。 [0223] 第二编码亚基 7024用于通过安全虚拟内核对加密处理得到的视频信号进行编码,得到待发送的视频信号。 [0224] 在一些可行的实现中,第一个编码子单元 7023 可以具体用于对加密后的音频信号进行模数转换、语音编码、信道编码、物理层加密等处理。 可选地,为了提高视频通话质量,第一编码子单元 7023 还可以对录制的音频信号进行交织、均衡、滤波等其他处理。 [0225] 在一些可行的实现中,第二个编码子单元 7024 可以具体用于对加密后的视频信号进行编码和物理层加密。 视频信号的编码标准可以根据视频通话连接的分辨率要求或压缩率要求来选择,例如H.261、H.262、H.263、H.264、MPEG-2或MPEG -4。 本发明对此不作限制。 [0226] 第一解码子单元 7025 用于当通信内容为移动终端接收到的音频信号时,通过安全虚拟内核对音频信号进行解码。 [0227] 第二解码子单元 7026 用于当通信内容为移动终端接收到的视频信号时,通过安全虚拟内核对接收到的视频信号进行解码。 [0228] 在一些可行的实施方式中,为了节省移动终端用户的开销,移动终端通过无线网络连接模块接收其他移动终端发送的音频信号和视频信号。 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 在这种情况下,普通虚拟内核控制无线网络连接模块接收其他移动终端发送的音频信号和视频信号,然后将接收到的音频信号和视频信号传输给安全虚拟内核用于 加工。 [0229] 在一个可行的实现中,第一个解码子单元 7025 可以具体用于对接收到的音频信号进行物理层解密、通道解码、语音解码、数模转换等处理。 可选地,为了提高视频通话质量,第一解码子单元 7025 还可以对接收到的音视频信号中的音频信号进行均衡、声道分离、解交织等其他处理。 [0230] 在一个可行的实现中,第二解码子单元 7026 可以具体用于对接收到的视频信号进行物理层解密和视频解码。 视频信号的解码标准可以包括H.261、H.262、H.263、H.264、MPEG-2、MPEG-4等,具体根据视频播放时选择的编码标准确定。 被编码。 [0231] 第一解密子单元 7027 用于通过安全虚拟内核对解码后的音频信号进行解密处理,得到待播放的音频信号。 [0232] 第二解密子单元 7028 用于通过安全虚拟内核对解码后的视频信号进行解密处理,得到待播放的视频信号。 [0233]在一些可行的实施方式中,在对移动终端接收到的音频信号和视频信号进行编码压缩发送之前,另一移动终端首先对接收到的音频信号和视频信号进行上层加密以防止泄露。 对移动通信链路的窃听攻击期间的通话内容。 移动终端接收经过上层加密处理后的音频信号和视频信号。 在使用安全虚拟内核对音频信号和视频信号进行解码后,移动终端还需要使用安全虚拟内核对音频信号和视频信号进行解密处理。 [0234] 在一种可行的实现方式中,可以通过第一解密子单元进行解密处理 7027 , 对移动终端接收到的音频信号进行解密处理, 利用第二解密子单元 7028 ,关于移动终端接收到的视频信号。 [0235] 在一些可行的实现中,输出单元 703 可以执行由输出单元执行的实现 403 如图4所示的实施例中描述的。在本实施例中,无线通信连接为视频通话连接,输出单元 703 可以具体用于: 通过安全虚拟内核控制移动终端向另一移动终端发送待发送音频信号和待发送视频信号。 或者,通过安全虚拟内核控制音频播放设备播放待播放的音频信号,通过安全虚拟内核控制显示器播放待播放的视频信号。 [0236] 在一些可行的实施方式中,为了节省移动终端用户的开销,可以通过移动终端的无线网络连接模块将待发送的音频信号和待发送的视频信号发送至另一移动终端。 . 在具体实现中,为了保证安全虚拟内核的安全环境,无线网络连接模块可以运行在移动终端的通用虚拟内核中。 此时,移动终端的安全虚拟内核可以将待发送的音频信号和待发送的视频信号发送给普通虚拟内核,并指示普通虚拟内核发送待发送的视频信号。 通过无线网络连接模块和互联网将音频信号和待发送的视频信号发送给其他移动终端。 无线网络连接模块可以为Wi-Fi模块,用于实现移动终端上网。 [0237] 安全虚拟内核对接收到的音频信号和视频信号进行一系列处理得到待播放的音频信号和待播放的视频信号后,安全虚拟内核就可以控制音频播放设备 移动终端的显示器,用于播放待播放的音频信号和待播放的视频信号。 待播放的音频信号可以通过移动终端的音频播放设备(例如麦克风)进行播放,待播放的视频信号可以通过移动终端的显示器进行播放。 [0238]本发明实施例中,当一个移动终端与另一个移动终端之间建立视频通话连接,并且该视频通话连接满足预设的安全处理触发条件时,移动终端通过设置禁止节目在 通用虚拟内核访问安全虚拟内核和通用虚拟内核之间的共享内存,访问相关的外围设备,如视频录制设备、录音设备、音频播放设备或显示器; 利用安全虚拟内核对移动终端录制的音视频信号和移动终端接收的音视频信号进行处理; 然后使用安全虚拟内核输出处理后的通信内容,可以防止操作系统和运行在普通虚拟内核中的程序获取未处理的通信内容,也可以防止操作系统窃听通信内容 通过共享内存或相关外设读取内容,提高了移动终端的通信安全性。 [0239] 需要说明的是,为便于描述,上述方法实施例均以一系列动作来表示。 然而,本领域的技术人员应该理解,本申请不限于所描述的动作顺序,因为根据本申请,一些步骤可以以其他顺序或同时执行。 本领域技术人员还应该理解,说明书中所描述的实施例仅为示例,所涉及的动作和模块并不一定是本申请所必须的。 [0240] 在上述实施例中,对各个实施例的描述都各有侧重。 一个实施例中没有详述的部分,可以参见其他实施例的相关描述。 [0241] 本领域普通技术人员可以理解,实施例中方法的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中。 存储介质可以包括闪存、只读存储器(ROM)、随机存取存储器(RAM)、磁盘和光盘。 [0242] 以上对本申请实施例提供的一种移动终端的安全通信方法及移动终端进行了详细描述。 本文通过具体的例子描述了本申请的原理和实现方式,以上对实施例的描述仅仅为了帮助理解本申请的方法和核心思想。 另外,本领域的普通技术人员可以根据本申请的思想,在具体实施方式和适用范围上对本申请作出变更和修改。 总之,本说明书的内容不应理解为对本申请的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106211144A(String), CN106211144B(String), EP3282735A1(String), EP3282735A4(String), IN201737039680A(String), IN426841B(String), KR101940164B1(String), KR1020170140344A(String), US10638311B2(String), US20180054732A1(String), WO2016173284A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.974 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.975 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106211144A(String), CN106211144B(String), EP3282735A1(String), EP3282735A4(String), IN201737039680A(String), IN426841B(String), KR101940164B1(String), KR1020170140344A(String), US10638311B2(String), US20180054732A1(String), WO2016173284A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.992 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:22.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10638311B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.028 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106211144A(String), CN106211144B(String), EP3282735A1(String), EP3282735A4(String), IN201737039680A(String), IN426841B(String), KR101940164B1(String), KR1020170140344A(String), US10638311B2(String), US20180054732A1(String), WO2016173284A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.045 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), CN106211144A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.080 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), CN106211144B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), EP3282735A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), EP3282735A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), IN201737039680A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), IN426841B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), KR101940164B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.290 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), KR1020170140344A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), US10638311B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.359 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), US20180054732A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271682(Integer), WO2016173284A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10638311B2(String), US10638311B2(String), 1588003200(Integer), 271682(Integer), 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.465 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.468 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186013(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 186013(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.648 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186013(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 186013(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.754 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.754 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.772 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.789 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.823 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.841 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:23.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186013(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10291756B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.386 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.387 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal, receiver for a mobile terminal, receiver and camera assembly for a mobile terminal(String), 移动终端、移动终端的接收器、移动终端的接收器和摄像头组件(String), US10291756B2(String), The embodiments of the present disclosure provide a mobile terminal, including a housing, a display screen, a camera and a receiver. The display screen is mounted to the housing and has a first aperture. The camera is mounted in the housing and is aligned with the first aperture. The receiver is mounted between the display screen and the camera and transmits a sound signal through the first aperture. The received has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture. In the solution, as the camera is disposed below the receiver along the thickness direction of the mobile terminal, it is unnecessary to provide independent apertures for the camera and the receiver in the display screen.(String), 本发明实施例提供一种移动终端,包括外壳、显示屏、摄像头和接收器。 显示屏安装在外壳上并具有第一孔。 相机安装在外壳中并与第一光圈对齐。 接收器安装在显示屏和摄像头之间,通过第一孔传输声音信号。 接收器具有光信号通道,摄像头通过光信号通道和第一光圈获取外界光信号。 在该方案中,由于摄像头沿移动终端的厚度方向设置在接收器下方,因此无需在显示屏中为摄像头和接收器设置独立的开孔。(String), US15/867256(String), 1515513600(Integer), US10291756B2(String), 1557763200(Integer), 1557763200(Integer), 美国(String), 4(Integer), CN(String), 13(Integer), 12(Integer), CN101652980A | CN105991807A | CN106453722A | CN106453726A | CN106936954A | CN1914900A | CN204119279U | CN205610701U | US20100165182A1 | US20100315570A1 | US20130094126A1 | US20170019512A1(String), 11(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.423 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.424 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186014(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.570 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.572 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\73422c19677441e1a89b682bcd0439d9.png(String), 186014(Integer), 73422c19677441e1a89b682bcd0439d9.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.607 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.608 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal, receiver for a mobile terminal, receiver and camera assembly for a mobile terminal(String), 移动终端、移动终端的接收器、移动终端的接收器和摄像头组件(String), US10291756B2(String), The embodiments of the present disclosure provide a mobile terminal, including a housing, a display screen, a camera and a receiver. The display screen is mounted to the housing and has a first aperture. The camera is mounted in the housing and is aligned with the first aperture. The receiver is mounted between the display screen and the camera and transmits a sound signal through the first aperture. The received has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture. In the solution, as the camera is disposed below the receiver along the thickness direction of the mobile terminal, it is unnecessary to provide independent apertures for the camera and the receiver in the display screen.(String), 本发明实施例提供一种移动终端,包括外壳、显示屏、摄像头和接收器。 显示屏安装在外壳上并具有第一孔。 相机安装在外壳中并与第一光圈对齐。 接收器安装在显示屏和摄像头之间,通过第一孔传输声音信号。 接收器具有光信号通道,摄像头通过光信号通道和第一光圈获取外界光信号。 在该方案中,由于摄像头沿移动终端的厚度方向设置在接收器下方,因此无需在显示屏中为摄像头和接收器设置独立的开孔。(String), US15/867256(String), 1515513600(Integer), US10291756B2(String), 1557763200(Integer), 1557763200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 13(Integer), 12(Integer), CN101652980A | CN105991807A | CN106453722A | CN106453726A | CN106936954A | CN1914900A | CN204119279U | CN205610701U | US20100165182A1 | US20100315570A1 | US20130094126A1 | US20170019512A1(String), \20230420\73422c19677441e1a89b682bcd0439d9.png(String), 11(Integer), 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.680 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.681 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.759 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 1. A mobile terminal, comprising:a housing;a display screen mounted to the housing and having a first aperture;a camera mounted in the housing and being aligned with the first aperture;a receiver mounted between the display screen and the camera and configured to transmit a sound signal through the first aperture;wherein the receiver has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture.(String), 1.移动终端,包括:住房;显示屏安装于外壳并具有第一孔径;安装在外壳内并对准第一光圈的摄像头;接收器,安装在显示屏和摄像头之间,用于通过第一孔径传输声音信号;其中,接收器具有光信号通道,而相机通过光信号通道和第一光圈来获取外部光信号。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 2. The mobile terminal according to claim 1, wherein the receiver comprises a transparent diaphragm, and the transparent diaphragm is aligned with the first aperture.(String), 2.根据权利要求1所述的移动终端,其中接收器包括透明膜片,透明膜片对准第一孔径。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 3. The mobile terminal according to claim 2, wherein the receiver further comprises a permanent magnet, the permanent magnet is disposed at a side of the diaphragm adjacent to the camera, and the permanent magnet has a second aperture aligned with the camera.(String), 3.根据权利要求2所述的移动终端,其中接收器还包括永磁体,永磁体设置在膜片邻近摄像头的一侧,永磁体具有与摄像头对准的第二孔径。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 4. The mobile terminal according to claim 3, wherein the receiver further comprises a magnetically conductive sheet and a magnetically conductive plate, the magnetically conductive sheet and the magnetically conductive plate are disposed at two sides of the permanent magnet respectively, and the magnetically conductive sheet and the magnetically conductive plate are respectively provided with a third aperture and a fourth aperture aligned with the second aperture.(String), 4.根据权利要求3所述的移动终端,其中接收器还包括导磁片和导磁板,导磁片和导磁板分别设置在永磁体的两侧,导磁片和导磁板分别设有第三孔径和与第二孔径对齐的第四孔径。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 5. The mobile terminal according to claim 4, wherein the transparent diaphragm, the third aperture, the second aperture, and the fourth aperture form the light signal passage.(String), 5.根据权利要求4所述的移动终端,其中透明光阑、第三孔径、第二孔径及第四孔径形成光信号通道。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 6. The mobile terminal according to claim 4, wherein the magnetically conductive plate is U-shaped, the permanent magnet and the magnetically conductive sheet are disposed at a bottom of the magnetically conductive plate, extension portions at two sides of the magnetically conductive plate extend upwards to two sides of the permanent magnet and the magnetically conductive sheet.(String), 6.根据权利要求4所述的移动终端,其中导磁板呈U型,永磁体和导磁片设置在导磁板的底部,导磁板两侧的延伸部向上延伸至永磁体和导磁片的两侧导电片。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 7. The mobile terminal according to claim 1, wherein the mobile terminal further comprises a sensor assembly, the sensor assembly is mounted in the housing, and the sensor assembly emits and receives a signal through the light signal passage and the first aperture.(String), 7.根据权利要求1所述的移动终端,其中移动终端还包括传感器组件,传感器组件安装在壳体内,传感器组件通过光信号通道和第一孔径发射和接收信号。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 8. The mobile terminal according to claim 7, wherein the camera is provided with a step, a step surface of the step faces the display screen, and the sensor assembly is mounted onto the step.(String), 8.根据权利要求7所述的移动终端,其中摄像头设有台阶,台阶的台阶面朝向显示屏,传感器组件安装在台阶上。(String), 1(Integer), 7(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 9. The mobile terminal according to claim 7, wherein the sensor assembly comprises a signal emitter and a signal receiver, and the signal emitter and the signal receiver are disposed at two sides of the camera respectively.(String), 9.根据权利要求7所述的移动终端,其中传感器组件包括信号发射器和信号接收器,信号发射器和信号接收器分别设置在摄像头的两侧。(String), 1(Integer), 8(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 10. The mobile terminal according to claim 7, wherein the sensor assembly further comprises an ambient light sensor, and the ambient light sensor receives an ambient light signal through the light signal passage and the first aperture.(String), 10.根据权利要求7所述的移动终端,其中传感器组件还包括环境光传感器,环境光传感器通过光信号通道和第一孔径接收环境光信号。(String), 1(Integer), 9(Integer), 6(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.763 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186014(Integer), 11. The mobile terminal according to claim 1, wherein the first aperture is disposed at a top middle of the display screen.(String), 11.根据权利要求1所述的移动终端,其中第一光圈设置于显示屏幕的顶部中间。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:24.988 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.005 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186014(Integer), CROSS-REFERENCE TO RELATED APPLICATIONS [0001]The application claims priority to and benefits of Chinese Patent Application Serial No. 201710132219.0, filed with the State Intellectual Property Office of P. R. china on Mar. 7, 2017, the entire content of which is incorporated herein by reference. FIELD [0002]The present disclosure relates to a field of communication technology, and particularly to a mobile terminal, a receiver for a mobile terminal, and a receiver and camera assembly for a mobile terminal. BACKGROUND [0003]In a conventional mobile terminal (such as a smartphone), a receiver is mounted in the mobile terminal. An aperture is provided in a top of the receiver, and the receiver sends a sound wave outwardly through the aperture, so as to allow the mobile terminal to transmit a sound signal to a user. [0004]On the other hand, a camera is also mounted in the mobile terminal, and the camera has an aperture at a top as well, so as to enable the camera to acquire an external image through the aperture. [0005]However, in this kind of design solution, it is required to provide a plurality of apertures in a screen, so as to realize functions of the receiver and the camera. The plurality of the apertures needs to occupy a large area of the screen of the mobile terminal, which causes a low ratio of a display area to the screen. SUMMARY [0006]Embodiments of the present disclosure provide a mobile terminal, including a housing, a display screen, a camera and a receiver, in which: the display screen is mounted to the housing and has a first aperture; the camera is mounted in the housing and is aligned with the first aperture; the phone is mounted between the display screen and the camera and transmits a sound signal through the first aperture; the receiver has a light signal passage, and the camera acquires an external light signal through the light signal passage and the first aperture. [0007]Embodiments of the present disclosure further provide a receiver configured to be mounted in a mobile terminal, including a vibration section and a magnetic circuit section, the vibration section including a transparent diaphragm, a through hole being formed in the magnetic circuit section, the transparent diaphragm and the through hole forming a light signal passage. [0008]Embodiments of the present disclosure further provide a receiver and camera assembly configured to be mounted in a mobile terminal, including a receiver, a camera, the receiver having a light signal passage, the camera being aligned with the light signal passage. BRIEF DESCRIPTION OF THE DRAWINGS [0009]To describe the technical solutions in the embodiments of the present disclosure more clearly, the accompanying drawings required for describing the embodiments are briefly introduced in the following. Apparently, the accompanying drawings in the following description illustrate merely some embodiments of the present disclosure, and those ordinarily skilled in the art can also derive other drawings from these accompanying drawings without creative efforts. [0010]FIG. 1 is a schematic view of a mobile terminal provided in an embodiment of the present disclosure. [0011]FIG. 2 is an exploded view of a mobile terminal provided in an embodiment of the present disclosure. [0012]FIG. 3 is a schematic view of a cover plate provided in an embodiment of the present disclosure. [0013]FIG. 4 is a schematic view of a display screen provided in an embodiment of the present disclosure. [0014]FIG. 5 is a first schematic view of a camera provided in an embodiment of the present disclosure. [0015]FIG. 6 is a second schematic view of a camera provided in an embodiment of the present disclosure. [0016]FIG. 7 is a sectional view of a receiver provided in an embodiment of the present disclosure. [0017]FIG. 8 is a schematic view where a receiver, a camera and a sensor assembly are mounted to a circuit board in an embodiment of the present disclosure. [0018]FIG. 9 is a first sectional view of the mobile terminal in FIG. 1 taken along P-P direction. [0019]FIG. 10 is a second sectional view of the mobile terminal in FIG. 1 taken along P-P direction. [0020]FIG. 11 is a third sectional view of the mobile terminal in FIG. 1 taken along P-P direction. [0021]FIG. 12 is a schematic view of a receiver and camera assembly provided in an embodiment of the present disclosure. DETAILED DESCRIPTION [0022]The technical solutions of the embodiments of the present disclosure are clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are only a part instead of all the embodiments of the present disclosure. All of the other embodiments derived by those ordinarily skilled in the art without creative effort based on the embodiments in the present disclosure belong to a protection scope of the present disclosure. [0023]In the specification, it is to be understood that terms such as “central”, “longitudinal”, “lateral”, “length”, “width”, “thickness”, “upper”, “lower”, “front”, “rear”, “left”, “right”, “vertical”, “horizontal”, “top”, “bottom”, “inner”, “outer”, “clockwise” and “counterclockwise”, should be construed to refer to the orientation as then described or as shown in the drawings under discussion. These relative terms are for convenience of description and do not require that the present disclosure be constructed or operated in a particular orientation. In addition, terms such as “first” and “second” are used herein for purposes of description and are not intended to indicate or imply relative importance or significance. Thus, features limited by “first” and “second” are intended to indicate or imply including one or more than one these features. In the description of the present disclosure, the term “a plurality of” means two or more than two, unless specified otherwise. [0024]In the present disclosure, unless specified or limited otherwise, the terms “mounted”, “connected”, “joined”, “fixed” and the like are used broadly, and may be, for example, fixed connections, detachable connections, or integral connections; may also be mechanical or electrical connections; may also be direct connections or indirect connections via intervening structures; may also be inner communications of two elements. The above terms can be understood by those skilled in the art according to specific situations. [0025]In the description of the present disclosure, a structure in which a first feature is “on” a second feature may include an embodiment in which the first feature directly contacts the second feature, and may also include an embodiment in which an additional feature is formed between the first feature and the second feature so that the first feature does not directly contact the second feature, unless otherwise specified. Furthermore, a first feature “on”, “above”, or “on top of” a second feature may include an embodiment in which the first feature is right “on”, “above” or “on top of” the second feature, and may also include an embodiment in which the first feature is not right “on”, “above” or “on top of” the second feature, or just means that the first feature has a sea level elevation larger than the sea level elevation of the second feature. While first feature “beneath”, “below” or “on bottom of” a second feature may include an embodiment in which the first feature is right “beneath”, “below” or “on bottom of” the second feature, and may also include an embodiment in which the first feature is not right “beneath”, “below” or “on bottom of” the second feature, or just means that the first feature has a sea level elevation smaller than the sea level elevation of the second feature. [0026]The following disclosure provides many different embodiments or examples to realize different structures of the present disclosure. To simplify the disclosure of the present disclosure, components and configurations in particular examples are elaborated. Of course, they are illustrative, and are not intended to limit the present disclosure. Moreover, reference numbers and/or letters may be repeated in different examples of the present disclosure for the purpose of simplicity and clarity, which shall not be constructed to indicate the relationships among various embodiments and/or configurations. In addition, the present disclosure provides examples of various specific processes and materials, but applicability of other processes and/or utilization of other materials are conceivable for those skilled in the art. [0027]Referring to FIGS. 1 and 2, a mobile terminal 100 includes a cover plate 10, a display screen 20, a circuit board 30, a battery 40 and a housing 50. The cover plate 10 is mounted to the display screen 20 so as to cover the display screen 20. Referring to FIG. 3, the cover plate 10 has a first through hole 101 and a second through hole 102. The first through hole 101 and the second through hole 102 are disposed at two ends of the cover plate 10 respectively. The first through hole 101 can be configured to enable a receiver in the mobile terminal 100 to transmit a sound signal outwardly through the first through hole. The second through hole 102 can be configured to enable a fingerprint unit in the mobile terminal 100 to acquire use finger information through the second through hole 102. [0028]In some embodiments, the first through hole 101 can be disposed at a top middle of the cover plate 10, and the second through hole 102 can be disposed at a bottom middle of the cover plate 10. [0029]The cover plate 10 can be a transparent glass cover plate. In some embodiments, the cover plate 10 can be a glass cover plate made of a material such as sapphire. [0030]The display screen 20 is mounted to the housing 50 so as to form a display surface of the mobile terminal 100. Referring to FIG. 4, the display screen 20 includes a display area 201 and a non-display area 202. The display area 201 is configured to display information like image and text. The non-display area 202 does not display information. The non-display area 202 can be provided with a functional assembly such as the fingerprint unit and a touch circuit. [0031]The display area 201 is provided with a third through hole 203. The third through hole 203 is aligned with the first through hole 101 in the cover plate 10. The third through hole 203 can be configured so that the camera in the mobile terminal 100 can acquire an external image signal through the third through hole, a proximity sensor in the mobile terminal 100 can emit and receive a signal through the third through hole, and the receiver in the mobile terminal 100 can transmit the sound signal outwardly through the third through hole. [0032]The non-display area 202 is provided with a fourth through hole 204. The fourth through hole 204 is aligned with the second through hole 102 in the cover plate 10. The fourth through hole 204 can be configured so that the fingerprint unit in the mobile terminal 100 can acquire the user fingerprint information through the fourth through hole. In some embodiments, the third through hole 203 can be disposed at a top middle of the display area 201, and the fourth through hole 204 can be disposed at a bottom middle of the non-display area 202. [0033]The circuit board 30 is mounted in the housing 50. The circuit board 30 can be a main board of the mobile terminal 100 and functional assemblies such as the camera, the proximity sensor, and the receiver can be integrated in the circuit board 30. Meanwhile, the display screen 20 can be electrically connected to the circuit board 30. [0034]Referring to FIG. 5, the camera 31 can be integrated in the circuit board 30. The camera 31 includes a base 311 and a camera lens 312. The camera lens 312 is mounted to the base 311. A contour of the base 311 can be rectangular, circular or in other shapes. A contour size of the base 311 is larger than a contour size of the camera lens 312, so that a step 310 can be formed at a mounting face of the camera lens 312 and the base 311. A step surface of the step 310 faces the display screen 20 in the mobile terminal 100. [0035]The sensor assembly 32 is mounted to the step 310. The sensor assembly 32 includes a signal emitter 321 and a signal receiver 322. The signal emitter 321 and the signal receiver 322 can compose the proximity sensor. The signal emitter 321 and the signal receiver 322 are electrically connected to the circuit board 30. [0036]The signal emitter 321 is configured to emit a signal, and the signal receiver 322 is configured to receive a reflected signal formed by reflecting the emitted signal by an external object. The mobile terminal 100 can judge a distance state between the mobile terminal 100 and the external object according to strength of the reflected signal so as to control a display state of the display screen 20. [0037]The above-mentioned signal can be a light signal such as an infrared ray, a laser and the like, and can also be other types of signals. [0038]The signal emitter 321 and the signal receiver 322 can be disposed at different sides of the camera lens 312 along a width direction of the mobile terminal 100. The signal emitter 321 and the signal receiver 322 can also be disposed at different sides of the camera lens 312 along a length direction of the mobile terminal 100. [0039]As the camera 31 is formed with the step 310 and hence the sensor assembly 32 can be mounted on the step 310, it is unnecessary to provide an independent aperture for the sensor assembly 32 in the mobile terminal 100. Thus, occupation of the sensor assembly 32 on the display area in the screen of the mobile terminal 100 is reduced, that is, a ratio of the display area to the screen is increased. [0040]Referring to FIG. 6, the sensor assembly 32 further includes an ambient light sensor 323. The ambient light sensor 323 is disposed around the camera lens 312 and mounted on the step 310. The ambient light sensor 323 is also electrically connected to the circuit board 30. The ambient light sensor 323 is configured to receive an ambient light signal. The mobile terminal 100 can also adjust brightness of the display screen 20 according to strength of the ambient light signal. [0041]Referring to FIG. 7, the receiver 33 can be integrated in the circuit board 30. The receiver 33 can be comprised of a vibration section 33-1, a magnetic circuit section 33-2 and a supporting section 33-3. The supporting section 33-3 is formed as a casing of the receiver 33. The magnetic circuit section 33-2 is mounted in the casing so as to form a magnetic circuit. The vibration section 33-1 is mounted above the magnetic circuit section 33-2 and produces sound through vibration. [0042]The vibration section 33-1 includes a diaphragm 331 and a voice coil 332. The voice coil 332 is disposed at a side of the diaphragm 331 and connected with the diaphragm 331. The connection between the voice coil 332 and the diaphragm 331 can be realized by a plurality of methods. For example, the voice coil 332 can be connected with the diaphragm 331 in an adhesive method. [0043]The diaphragm 331 can be a transparent diaphragm so as to allow a light signal to pass through. A shape of the diaphragm 331 matches a shape of the receiver 33. The shape of the diaphragm 331 can be circular. [0044]The diaphragm 331 can be an elastic diaphragm and can vibrate up and down along a thickness direction of the diaphragm. When the diaphragm 331 vibrates, air at two sides of the diaphragm vibrates therewith so as to produce sound. [0045]The voice coil 332 is formed by winding a conductive wire upon an insulation frame, the wire having an insulating outer layer. The conductive wire on the voice coil 332 is configured to be connected to an audio-frequency circuit inside the mobile terminal 100. [0046]The magnetic circuit section 33-2 includes a permanent magnet 333, a magnetically conductive sheet 334 and a magnetically conductive plate 335. The magnetically conductive sheet 334 can be disposed at a side (N pole) of the permanent magnet 333, and the magnetically conductive plate 335 is disposed at the other side (S pole) of the permanent magnet 333. The magnetically conductive sheet 334 and the magnetically conductive plate 335 are configured to conduct a magnetic induction line emitted by the permanent magnet 333 so as to form a closed magnetic circuit. The magnetic induction line emitted by the N pole of the permanent magnet 333 passes through the magnetically conductive sheet 334, then passes through the magnetically conductive plate 335, and finally enters the S pole of the permanent magnet 333, so as to form a closed loop circuit. The magnetically conductive sheet 334 can be an iron sheet, and the magnetically conductive plate 335 can be a thin iron plate. The shapes of the magnetically conductive sheet 334 and the magnetically conductive plate 335 can be square, rectangular, or circular. The magnetically conductive sheet 334, the permanent magnet 333, and the magnetically conductive plate 335 can be fastened in the adhesive manner. [0047]The permanent magnet 333 has an aperture 330, the magnetically conductive sheet 334 is provided with an aperture 340, and the magnetically conductive plate 335 has an aperture 350. The aperture 340 and the aperture 350 are both aligned with the aperture 330. [0048]The transparent diaphragm 331, the aperture 340, the aperture 330 and the aperture 350 together form a light signal passage so as to allow the light signal to pass through. [0049]In some embodiments, the permanent magnet 333 is a nanometer permanent magnet. That is, permanent magnetic material particles are uniformly coated with a layer of soft magnetic material by nanotechnology, or the permanent magnetic material and the soft magnetic material are combined together by a chemical process such as a replacement reaction, so as to obtain permanent magnetic nanoparticles. Then, the nanometer permanent magnet is manufactured by techniques such as high-pressure molding or high-temperature sintering. The nanometer permanent magnet has higher magnetic induction intensity inside relative to an ordinary Nd—Fe—B permanent magnet. Thus, with the same volume of the permanent magnet, the receiver adopting the nanometer permanent magnet has a higher sound pressure level. [0050]In some embodiments, the magnetically conductive plate 335 is U-shaped. The permanent magnet 333 and the magnetically conductive sheet 334 are disposed at a bottom of the U shape of the magnetically conductive plate 335. Extension portions at two sides of the magnetically conductive plate 335 extend upwards to two sides of the permanent magnet 333 and the magnetically conductive sheet 334. A gap is formed between each of the side extension portions of the magnetically conductive plate 335 and the corresponding side of two sides of the permanent magnet 333 and the magnetically conductive sheet 334, and the voice coil 332 is disposed in the gap. [0051]The supporting section 33-3 includes a support 336 and a protection cover 337. The support 336 is formed in an annular shape. A peripheral protrusion is provided at a periphery of an end of the support 336. The protection cover 337 is formed in an annular shape. An aperture can be provided in a center of the protection cover 337, so that the sound produced by the diaphragm 331 can be transmitted outwardly. A section of the protection cover 337 exhibits a reversed L shape. A periphery of the protection cover 337 is provided with a peripheral recess. With the peripheral protrusion of the support 336 fitted with the peripheral recess of the protection cover 337, the protection cover 337 is mounted to the support 336. The diaphragm 331 is mounted to the support 336 by means of a mounting portion at an edge of the diaphragm. The mounting portion at the edge of the diaphragm 331 can be mounted to the support 336 in the adhesive method. [0052]In some embodiments, the support 336 is made of nanomaterial. The protection cover 337 can also be made of nanomaterial. Both of the support 336 and the protection cover 337 can be integrally formed by the nanomaterial through injection molding. The support 336 and the protection cover 337 made of nanomaterial have higher strength, which can improve mechanical reliability of the receiver 33. [0053]Referring to FIG. 8, in the mobile terminal 100, the camera 31 and the receiver 33 are both mounted to the circuit board 30. The camera 31 is aligned with the light signal passage 34 of the receiver 33. The sensor assembly 32 can be mounted on the step of the camera 31. Meanwhile, a sensor assembly 32 is electrically connected to the circuit board 30. The sensor assembly 32 includes the signal emitter 321 and the signal receiver 322. The signal emitter 321 and the signal receiver 322 can be disposed at two sides of the camera lens of the camera 31 respectively. [0054]Reference is still made to FIGS. 1 and 2. [0055]The battery 40 is mounted inside the housing 50 and configured to provide electrical energy for the mobile terminal 100. [0056]The housing 50 is configured to form an external contour of the mobile terminal 100. The housing 50 can be made of plastic or metal. The housing 50 can be formed integrally. [0057]Referring to FIG. 9, FIG. 9 is a section view of the mobile terminal illustrated in FIG. 1 taken along P-P direction. The cover plate 10 is mounted to the housing 50. The cover plate 10 has an aperture 110. The display screen 20 is also mouthed to the housing 50. The display screen 20 has an aperture 210 (namely the above-mentioned third through hole 203, there is no strict difference between terms “aperture” and “through hole” in the descriptions). The cover plate 10 covers the display screen 20. The aperture 210 is aligned with the aperture 110. The circuit board 30 is mounted in the housing 50. [0058]The camera 31 and the receiver 33 are mounted to the circuit board 30. The receiver 33 is disposed between the camera 31 and the display screen 20. The receiver 33 is aligned with the aperture 210 and the aperture 110 so that the receiver 33 can transmit the sound signal outwardly through the aperture 210 and the aperture 110. The receiver 33 has the light signal passage 34. The camera 31 is aligned with the light signal passage 34 so that the camera 31 can acquire the light signal from the outside through the light signal passage 34, the aperture 210 and the aperture 110. [0059]As the camera 31 is disposed below the receiver 33 along the thickness direction of the mobile terminal 100, it is unnecessary to provide independent apertures for the camera 31 and the receiver 33 in the display screen 20. Thus, occupation of the apertures in the display screen 20 relative to the display area is reduced, and the ratio of the display area to the screen of the mobile terminal 100 is increased. [0060]In some embodiments, as illustrated in FIG. 10, the sensor assembly 32 can be mounted to the circuit board 30. The sensor assembly 32 is aligned with the light signal passage 34 in the receiver 33 so as to allow the sensor assembly 32 to receive and/or emit signals through the light signal passage 34, the aperture 210 and the aperture 110. The sensor assembly 32 includes the signal emitter 321 and the signal receiver 322. The signal emitter 321 and the signal receiver 322 can be disposed at two sides of the camera 31 respectively. In some embodiments, the sensor assembly 32 can further include the ambient light sensor. The ambient light sensor can be disposed around the camera 31. [0061]In some embodiments, as illustrated in FIG. 11, the camera 31 is formed with the step 310. The step surface of the step 310 faces the display screen 20, and the sensor assembly 32 can be disposed on the step 310. The sensor assembly 32 includes the signal emitter 321 and the signal receiver 322. The signal emitter 321 and the signal receiver 322 can be disposed at two sides of the camera lens of the camera 31 respectively. [0062]In some embodiments, the sensor assembly 32 can further include the ambient light sensor. The ambient light sensor can be disposed on the step 310 and around the camera lens of the camera 31. [0063]As illustrated in FIG. 12, a receiver and camera assembly configured to be mounted in a mobile terminal is provided in embodiments of the present disclosure, including a receiver 33, a camera 31. The receiver 33 has a light signal passage 34, and the camera 31 is aligned with the light signal passage 34. The receiver 33 and the camera 31 can be integrated. Specifically, the receiver 33 and the camera 31 can be mounted to a mounting plate 35. The mounting plate 35 can be configured to be connected to a circuit board of the mobile terminal. [0064]The mobile terminal provided by the embodiment of the present disclosure is described in detail above, and specific examples are used herein to describe the principle and embodiments of the present disclosure. The description of the foregoing embodiments is merely intended to help understand the present disclosure. Meanwhile, those skilled in the art can make modifications to the specific embodiments and application scope according to the idea of the present disclosure. To sum up, the contents of the description should not be construed as limiting the present disclosure.(String), 相关申请的交叉引用 [0001] 本申请要求于2017年3月7日向中华人民共和国国家知识产权局提交的申请号为201710132219.0的中国专利申请的优先权,将其全部内容引用于此。 场地 [0002] 本发明涉及通信技术领域,尤其涉及一种移动终端、移动终端接收器、移动终端接收器和摄像头组件。 背景 [0003] 在传统的移动终端(例如智能手机)中,接收器安装在移动终端中。 接收器的顶部设有孔,接收器通过孔向外发出声波,从而使移动终端向用户发送声音信号。 [0004] 另一方面,移动终端中还安装有摄像头,摄像头的顶部也设置有光圈,以实现摄像头通过光圈获取外界图像。 [0005] 然而,在这种设计方案中,需要在屏幕上设置多个开孔,以实现接收器和摄像头的功能。 多个开孔需要占据移动终端屏幕的较大面积,导致显示面积屏占比较低。 概括 [0006] 本发明实施例提供一种移动终端,包括外壳、显示屏、摄像头和听筒,所述显示屏安装在所述外壳上并具有第一开孔; 摄像头安装在外壳内并对准第一光圈; 手机安装于显示屏幕与摄像头之间,并通过第一开孔传送声音信号。 接收器具有光信号通道,摄像头通过光信号通道与第一光圈获取外界光信号。 [0007] 本发明实施例还提供一种接收器,用于安装在移动终端中,包括振动部分和磁路部分,振动部分包括透明振膜,磁路部分上形成有通孔,透明振膜 通孔形成光信号通道。 [0008] 本发明实施例还提供了一种接收器和摄像头组件,用于安装在移动终端中,包括接收器、摄像头,接收器具有光信号通道,摄像头对准光信号通道。 附图的简要说明 [0009] 为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简单介绍。 显然,以下描述中的附图仅仅是本发明的部分实施例,本领域普通技术人员在没有做出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0010] 图1为本发明实施例提供的一种移动终端的示意图。 [0011] 图2为本发明实施例提供的移动终端的分解图。 [0012] 图3为本发明实施例提供的盖板的示意图。 [0013] 图4为本发明实施例提供的显示屏的示意图。 [0014] 图5为本发明实施例提供的摄像头的第一示意图。 [0015] 图6为本发明实施例提供的摄像头的第二示意图。 [0016] 图7为本发明实施例提供的接收器的剖视图。 [0017] 图8为本发明实施例中接收器、摄像头和传感器组件安装到电路板上的示意图。 [0018] 图9为图1中移动终端沿P-P方向的第一剖视图。 [0019]图10为图1中移动终端沿P-P方向的剖视图之二。 [0020] 图11为图1中移动终端沿P-P方向的剖视图之三。 [0021] 图12为本发明实施例提供的接收器和摄像头组件的示意图。 详细说明 [0022] 下面结合本发明实施例中的附图,对本发明实施例的技术方案进行清楚、完整的描述。 显然,所描述的实施例只是本发明的一部分实施例,而不是所有实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0023] 在说明书中,应当理解诸如“中央”、“纵向”、“横向”、“长度”、“宽度”、“厚度”、“上部”、“下部”、“前部”、“ 后”、“左”、“右”、“垂直”、“水平”、“顶部”、“底部”、“内部”、“外部”、“顺时针”和“逆时针”,应解释为指 然后描述的方向或在讨论中的附图中所示的方向。 这些相关术语是为了描述的方便,并不要求本公开在特定方向上被构造或操作。 此外,本文中使用的诸如“第一”和“第二”等术语是为了描述的目的,并不旨在指示或暗示相对重要性或重要性。 因此,由“第一”和“第二”限定的特征旨在指示或暗示包括这些特征中的一个或多个。 在本公开的描述中,除非另有说明,否则术语“多个”是指两个或两个以上。 [0024] 在本发明中,除非另有说明或限制,术语“安装”、“连接”、“接合”、“固定”等具有广泛的使用意义,例如可以是固定连接、可拆卸连接或整体连接 连接; 也可以是机械或电气连接; 也可以是直接连接或通过中间结构的间接连接; 也可能是两个元素的内部通信。 本领域技术人员可以根据具体情况理解上述术语。 [0025] 在本发明的描述中,第一特征在第二特征“之上”的结构可以包括第一特征直接接触第二特征的实施例,也可以包括形成附加特征的实施例 在第一特征和第二特征之间,使得第一特征不直接接触第二特征,除非另有说明。 此外,第一特征“在”第二特征“之上”、“之上”或“之上”可包括其中第一特征恰好在第二特征“之上”、“之上”或“之上”的实施例, 并且还可以包括第一特征不在第二特征“之上”、“上方”或“之上”的实施例,或者仅仅意味着第一特征的海平面高度大于 第二个特点。 虽然第一特征“在”第二特征“下方”、“下方”或“底部”可以包括第一特征正好在第二特征“下方”、“下方”或“底部”的实施例,并且也可以 包括第一个特征不在第二个特征“下方”、“下方”或“底部”的实施例,或者仅表示第一个特征的海平面高度小于第二个特征的海平面高度 . [0026]以下公开提供许多不同的实施例或例子来实现本公开的不同结构。 为了简化本公开的公开,详细说明了特定示例中的组件和配置。 当然,它们是示例性的,并不旨在限制本公开。 此外,为了简单和清楚的目的,在本公开的不同示例中可以重复附图标记和/或字母,其不应被构造为指示各种实施例和/或配置之间的关系。 此外,本公开提供了各种具体工艺和材料的示例,但是本领域技术人员可以想到其他工艺的应用和/或其他材料的利用。 [0027] 参考图1和图2,移动终端 100 包括一个盖板 10 , 显示屏 20 , 电路板 30 , 一块电池 40 和一个住房 50 . 盖板 10 安装在显示屏上 20 以覆盖显示屏 20 . 参见图3,盖板 10 有一个第一通孔 101 和第二个通孔 102 . 第一个通孔 101 和第二个通孔 102 设置于盖板的两端 10 分别。 第一个通孔 101 可以配置为启用移动终端中的接收器 100 通过第一通孔向外传输声音信号。 第二个通孔 102 可配置为启用移动终端中的指纹单元 100 通过第二通孔获取用户手指信息 102 . [0028] 在一些实施例中,第一通孔 101 可以设置在盖板的顶部中间 10 , 和第二个通孔 102 可以设置在盖板的底部中间 10 . [0029] 盖板 10 可以是透明的玻璃盖板。 在一些实施例中,盖板 10 可以是由蓝宝石等材料制成的玻璃盖板。 [0030] 显示屏 20 安装在外壳上 50 从而形成移动终端的显示面 100 . 参考图4,显示屏幕 20 包括一个展示区 201 和非展示区 202 . 展示区 201 用于显示图像和文本等信息。 非展示区 202 不显示信息。 非展示区 202 可设置指纹单元、触摸电路等功能组件。 [0031] 展示区 201 设有第三通孔 203 . 第三个通孔 203 与第一个通孔对齐 101 在盖板 10 . 第三个通孔 203 可以配置让手机端的摄像头 100 可以通过移动终端中的接近传感器第三通孔获取外部图像信号 100 可以通过第三通孔发射和接收信号,移动终端中的接收器 100 可通过第三通孔向外传输声音信号。 [0032] 非展示区 202 设有第四通孔 204 . 第四个通孔 204 与第二个通孔对齐 102 在盖板 10 . 第四个通孔 204 可配置移动终端中的指纹单元 100 可以通过第四通孔获取用户指纹信息。 在一些实施例中,第三通孔 203 可以设置在显示区域的顶部中间 201 , 和第四个通孔 204 可以设置在非显示区域的底部中间 202 . [0033] 电路板 30 安装在外壳中 50 . 电路板 30 可以是移动终端的主板 100摄像头、接近传感器、接收器等功能组件可以集成在电路板上 30 . 同时,显示屏 20 可以电连接到电路板 30 . [0034] 参考图5,相机 31 可以集成在电路板上 30 . 相机 31 包括一个基地 311 和一个相机镜头 312 . 相机镜头 312 安装在底座上 311 . 底座轮廓 311 可以是矩形、圆形或其他形状。 底座轮廓尺寸 311 大于相机镜头的轮廓尺寸 312 , 所以一步 310 可以形成在相机镜头的安装面上 312 和基地 311 . 台阶的台阶面 310 面对显示屏 20 在移动端 100 . [0035] 传感器总成 32 安装在台阶上 310 . 传感器总成 32 包括一个信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可以组成接近传感器。 信号发射器 321 和信号接收器 322 电连接到电路板 30 . [0036] 信号发射器 321 被配置为发射信号,并且信号接收器 322 被配置为接收由外部物体反射发射信号形成的反射信号。 移动端 100 可以判断移动终端之间的距离状态 100 以及外界物体根据反射信号的强弱来控制显示屏的显示状态 20 . [0037] 上述信号可以是红外线、激光等光信号,也可以是其他类型的信号。 [0038] 信号发射器 321 和信号接收器 322 可以设置在相机镜头的不同侧面 312 沿移动终端的宽度方向 100 . 信号发射器 321 和信号接收器 322 也可以设置在相机镜头的不同侧面 312 沿着移动终端的长度方向 100 . [0039] 作为相机 31 是用台阶形成的 310 因此传感器组件 32 可以安装在台阶上 310 ,无需为传感器组件提供独立的孔径 32 在移动端 100 . 因此,传感器组件的占用 32 在移动终端屏幕的显示区域 100 减小,即显示区域与屏幕的比例增大。 [0040] 参考图 6,传感器组件 32 还包括一个环境光传感器 323 . 环境光传感器 323 设置于相机镜头周围 312 并安装在台阶上 310 . 环境光传感器 323 也电连接到电路板 30 . 环境光传感器 323 被配置为接收环境光信号。 移动端 100 还可以调节显示屏的亮度 20 根据环境光信号的强度。 [0041] 参考图7,接收器 33 可以集成在电路板上 30 . 收件人 33 可以由振动部分组成 33 - 1 , 磁路部分 33 - 2 和一个支持部分 33 - 3 . 支撑部分 33 - 3 形成为接收器的外壳 33 . 磁路部分 33 - 2 安装在外壳内形成磁路。 振动部分 33 - 1 安装在磁路部分上方 33 - 2 并通过振动产生声音。 [0042] 振动部分 33 - 1 包括隔膜 331 和一个音圈 332 . 音圈 332位于隔膜的一侧 331 并与隔膜相连 331 . 音圈之间的连接 332 和隔膜 331 可以通过多种方法实现。 例如,音圈 332 可接膜片 331 在粘合方法中。 [0043] 隔膜 331 可以是透明膜片以允许光信号通过。 横膈膜的形状 331 匹配接收器的形状 33 . 隔膜的形状 331 可以是圆形的。 [0044] 隔膜 331 可以是弹性膜片,可以沿膜片的厚度方向上下振动。 当隔膜 331 振动时,振膜两侧的空气随之振动而发出声音。 [0045] 音圈 332 由导线缠绕在绝缘框架上形成,该导线具有绝缘外层。 音圈上的导线 332 用于连接移动终端内部的音频电路 100 . [0046] 磁路部分 33 - 2 包括一个永磁体 333 , 导磁片 334 和导磁板 335 . 导磁片 334 可置于永磁体一侧(N极) 333 , 导磁板 335 设置在永磁体的另一侧(S极) 333 . 导磁片 334 和导磁板 335 被配置为传导由永磁体发出的磁感应线 333 从而形成闭合磁路。 永磁体N极发出的磁感应线 333 穿过导磁片 334 , 然后穿过导磁板 335 ,最后进入永磁体的S极 333 ,从而形成闭环电路。 导磁片 334 可以是铁皮,导磁板 335 可以是薄铁板。 导磁片的形状 334 和导磁板 335 可以是正方形、长方形或圆形。 导磁片 334 , 永磁体 333 , 导磁板 335 可以用粘着的方式固定。 [0047] 永磁体 333 有光圈 330 , 导磁片 334 设有光圈 340 , 导磁板 335 有光圈 350 . 光圈 340 和光圈 350 都与光圈对齐 330 . [0048] 透明隔膜 331 , 孔径 340 , 孔径 330 和光圈 350 共同形成光信号通道,以供光信号通过。 [0049] 在一些实施例中,永磁体 333 是纳米永磁体。 即通过纳米技术在永磁材料颗粒上均匀地包覆一层软磁材料,或者通过置换反应等化学过程将永磁材料与软磁材料结合在一起,从而得到永磁纳米颗粒 . 然后,通过高压成型或高温烧结等工艺制造纳米永磁体。 该纳米永磁体相对于普通的Nd-Fe-B永磁体内部具有更高的磁感应强度。 因此,在永磁体体积相同的情况下,采用纳米永磁体的接收机具有更高的声压级。 [0050] 在一些实施例中,导磁板 335 是U形的。 永磁体 333 和导磁片 334 设置于导磁板的U形底部 335. 导磁板两侧延伸部 335 向上延伸至永磁体两侧 333 和导磁片 334 . 导磁板的各侧延伸部之间形成有间隙 335 和永磁体两侧的对应边 333 和导磁片 334 , 和音圈 332 设置于间隙中。 [0051] 支撑部分 33 - 3 包括支持 336 和保护罩 337 . 支撑 336 形成为环状。 支架一端周边设有一周边凸起 336 . 保护罩 337 形成为环状。 保护盖中央可开孔 337 , 这样振膜发出的声音 331 可以向外传播。 一段保护盖 337 呈倒L形。 保护罩周边 337 设有外围凹槽。 与支架的外围突起 336 与保护盖的周边凹槽相配 337 , 防护罩 337 安装在支架上 336 . 隔膜 331 安装在支架上 336 通过隔膜边缘的安装部分。 膜片边缘的安装部分 331 可以安装到支架上 336 在粘合法中。 [0052] 在一些实施例中,支持 336 由纳米材料制成。 保护罩 337 也可以由纳米材料制成。 两者都支持 336 和保护罩 337 纳米材料可通过注塑成型一体成型。 支撑 336 和保护罩 337 由纳米材料制成,具有更高的强度,可以提高接收器的机械可靠性 33 . [0053] 参见图8,在移动终端中 100 , 相机 31 和接收器 33 都安装在电路板上 30 . 相机 31 与光信号通道对齐 34 接收者的 33 . 传感器总成 32 可以安装在相机的台阶上 31 . 同时,传感器组件 32 与电路板电连接 30 . 传感器总成 32 包括信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可设置于相机镜头两侧 31 分别。 [0054] 仍然参考图1和图2。 [0055] 电池 40 安装在外壳内 50 用于为移动终端提供电能 100 . [0056] 住房 50 用于形成移动终端的外轮廓 100 . 住房 50 可以由塑料或金属制成。 住房 50 可以一体成型。 [0057] 参见图9,图9为图1所示移动终端沿P-P方向的剖视图。 盖板 10 安装在外壳上 50 . 盖板 10 有光圈 110 . 显示屏 20 也被吹到房屋 50 . 显示屏 20 有光圈 210 (即上述第三个通孔 203 , 描述中术语“孔径”和“通孔”之间没有严格区别)。 盖板 10 覆盖显示屏 20 . 光圈 210 与光圈对齐 110 . 电路板 30 安装在外壳中 50 . [0058] 相机 31 和接收器 33 安装在电路板上 30 . 收件人 33 置于相机之间 31 和显示屏 20 . 收件人 33 与光圈对齐210 和光圈 110 以便接收者 33 可以通过孔径向外传输声音信号 210 和光圈 110 . 收件人 33 有光信号通道 34 . 相机 31 与光信号通道对齐 34 这样相机 31 可通过光信号通道从外部获取光信号 34 , 孔径 210 和光圈 110 . [0059] 作为相机 31 置于接收器下方 33 沿移动终端的厚度方向 100 ,不需要为相机提供独立的光圈 31 和接收器 33 在显示屏上 20 . 从而占据显示屏的开孔 20 相对于显示区域缩小,显示区域占移动终端屏幕的比例 100 增加。 [0060] 在一些实施例中,如图 10 所示,传感器组件 32 可以安装到电路板上 30 . 传感器总成 32 与光信号通道对齐 34 在接收器中 33 以便让传感器组装 32 通过光信号通道接收和/或发射信号 34 , 孔径 210 和光圈 110 . 传感器总成 32 包括信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可置于摄像头两侧 31 分别。 在一些实施例中,传感器组件 32 还可以包括环境光传感器。 环境光传感器可以设置在摄像头周围 31 . [0061] 在一些实施例中,如图 11 所示,相机 31 是用台阶形成的 310 . 台阶的台阶面 310 面对显示屏 20 和传感器组件 32 可以放在台阶上 310 . 传感器总成 32 包括信号发射器 321 和信号接收器 322 . 信号发射器 321 和信号接收器 322 可设置于相机镜头两侧 31 分别。 [0062] 在一些实施例中,传感器组件 32 还可以包括环境光传感器。 环境光感测器可设置于台阶上 310 以及相机镜头周围 31 . [0063] 如图12所示,本发明实施例提供了一种用于安装在移动终端中的接收器和摄像头组件,包括: 33 , 相机 31 . 收件人 33 有光信号通道 34 , 和相机 31 与光信号通道对齐 34 . 收件人 33 和相机 31 可以集成。 具体来说,接收方 33 和相机 31 可以安装到安装板上 35 . 安装板 35 可以配置为连接到移动终端的电路板。 [0064] 以上对本发明实施例提供的移动终端进行了详细描述,这里通过具体的例子来说明本发明的原理和实施方式。 上述实施例的描述只是为了帮助理解本发明。 同时,本领域的技术人员可以根据本公开的思想对具体实施例和适用范围进行修改。 综上所述,说明书的内容不应视为对本发明的限制。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.063 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.064 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: AU2018229784A1(String), AU2018229784B2(String), CN106936954A(String), CN106936954B(String), CN111447309A(String), CN111447309B(String), EP3373564A1(String), EP3373564B1(String), ES2790250T3(String), HK1236704A(String), HK1236704A1(String), IN201834001094A(String), JP2020503767A(String), JP6783393B2(String), SG11201906191TA(String), SG11201906191TB(String), TW201834436A(String), TWI658719B(String), US10291756B2(String), US10834245B2(String), US20180262602A1(String), US20190230204A1(String), WO2018161720A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.228 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.229 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: AU2018229784A1(String), AU2018229784B2(String), CN106936954A(String), CN106936954B(String), CN111447309A(String), CN111447309B(String), EP3373564A1(String), EP3373564B1(String), ES2790250T3(String), HK1236704A(String), HK1236704A1(String), IN201834001094A(String), JP2020503767A(String), JP6783393B2(String), SG11201906191TA(String), SG11201906191TB(String), TW201834436A(String), TWI658719B(String), US10291756B2(String), US10834245B2(String), US20180262602A1(String), US20190230204A1(String), WO2018161720A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.248 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US10291756B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), AU2018229784A1(String), AU2018229784B2(String), CN106936954A(String), CN106936954B(String), CN111447309A(String), CN111447309B(String), EP3373564A1(String), EP3373564B1(String), ES2790250T3(String), HK1236704A(String), HK1236704A1(String), IN201834001094A(String), JP2020503767A(String), JP6783393B2(String), SG11201906191TA(String), SG11201906191TB(String), TW201834436A(String), TWI658719B(String), US10291756B2(String), US10834245B2(String), US20180262602A1(String), US20190230204A1(String), WO2018161720A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.307 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), AU2018229784A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.342 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.343 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), AU2018229784B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.378 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.378 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.379 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), CN106936954A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.413 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.414 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), CN106936954B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.449 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.450 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), CN111447309A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.484 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.485 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.485 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), CN111447309B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.520 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.520 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.521 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), EP3373564A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.555 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.556 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), EP3373564B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.590 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.591 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), ES2790250T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.625 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.626 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), HK1236704A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.661 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), HK1236704A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.723 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), IN201834001094A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), JP2020503767A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.792 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.793 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), JP6783393B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.827 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.828 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), SG11201906191TA(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.864 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), SG11201906191TB(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.899 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.900 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), TW201834436A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.935 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), TWI658719B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.969 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:25.970 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), US10291756B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.004 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), US10834245B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), US20180262602A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), US20190230204A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271683(Integer), WO2018161720A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.144 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.145 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US10291756B2(String), US10291756B2(String), 1557763200(Integer), 271683(Integer), 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.181 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), OPPO广东移动通信有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.225 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.257 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.258 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186014(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 1(Integer), 186014(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.(String), OPPO广东移动通信有限公司(String), 255(String), 0(Integer), 1661141128(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.360 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.361 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186014(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.395 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 25100(Integer), 2(Integer), 186014(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.430 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.447 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 25100(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.482 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.499 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.553 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.706 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.706 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.706 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186014(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.765 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:26.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US8731625B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.110 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal and method of write protection for memory card in the mobile terminal(String), 移动终端及移动终端中存储卡的写保护方法(String), US8731625B2(String), A mobile terminal and method to write protect a memory card in the mobile terminal. The mobile terminal comprises a body, a battery and a battery cover. The battery cover has a short-circuit connecting member. A memory card socket accommodates a pluggable memory card. A writing control unit has input and output ports, and when the battery cover is jointed with the body, the input and output ports contact the short-circuit connecting member to form a short-circuit connection therebetween; the writing control unit detects whether the battery cover is removed by outputting a test signal from the output port and detecting for the test signal at the input port; if the battery cover is removed, the test signal is not detected at the input port and data is prohibited from being written into the memory card.(String), 一种移动终端和对移动终端中的存储卡进行写保护的方法。 移动终端包括机身、电池和电池盖。 电池盖具有短路连接件。 存储卡插槽可容纳可插拔存储卡。 写控制单元具有输入输出端口,当电池盖与本体接合时,输入输出端口与短路连接件接触,形成短路连接。 写入控制单元通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除。 如果取下电池盖,则输入端口检测不到测试信号,数据被禁止写入存储卡。(String), US13/409664(String), 1330531200(Integer), US8731625B2(String), 1400515200(Integer), 1400515200(Integer), 美国(String), 4(Integer), CN(String), 3(Integer), 4(Integer), EP1531385A2 | EP2280490A2 | GB2270445A | US20080018541A1(String), 13(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.146 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186015(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.291 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.292 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2f760e408e544dc4bcec7f1c6df2b3ed.png(String), 186015(Integer), 2f760e408e544dc4bcec7f1c6df2b3ed.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.327 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.345 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal and method of write protection for memory card in the mobile terminal(String), 移动终端及移动终端中存储卡的写保护方法(String), US8731625B2(String), A mobile terminal and method to write protect a memory card in the mobile terminal. The mobile terminal comprises a body, a battery and a battery cover. The battery cover has a short-circuit connecting member. A memory card socket accommodates a pluggable memory card. A writing control unit has input and output ports, and when the battery cover is jointed with the body, the input and output ports contact the short-circuit connecting member to form a short-circuit connection therebetween; the writing control unit detects whether the battery cover is removed by outputting a test signal from the output port and detecting for the test signal at the input port; if the battery cover is removed, the test signal is not detected at the input port and data is prohibited from being written into the memory card.(String), 一种移动终端和对移动终端中的存储卡进行写保护的方法。 移动终端包括机身、电池和电池盖。 电池盖具有短路连接件。 存储卡插槽可容纳可插拔存储卡。 写控制单元具有输入输出端口,当电池盖与本体接合时,输入输出端口与短路连接件接触,形成短路连接。 写入控制单元通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除。 如果取下电池盖,则输入端口检测不到测试信号,数据被禁止写入存储卡。(String), US13/409664(String), 1330531200(Integer), US8731625B2(String), 1400515200(Integer), 1400515200(Integer), 美国(String), 2(Integer), 4(Integer), CN(String), 3(Integer), 4(Integer), EP1531385A2 | EP2280490A2 | GB2270445A | US20080018541A1(String), \20230420\2f760e408e544dc4bcec7f1c6df2b3ed.png(String), 13(Integer), 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.380 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.381 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.415 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 1. A mobile terminal comprising a body, a battery and a battery cover, wherein,the battery cover is provided with a short-circuit connecting member;the body comprises:a memory card socket configured to accommodate a pluggable memory card;a writing control unit including an input port and an output port, the writing control unit configured such that, in response to the battery cover being joined with the body, the input port and the output port of the writing control unit both electrically contact the short-circuit connecting member, so as to form a short-circuit connection between the input port and the output port;wherein the writing control unit is configured to detect whether the battery cover is removed by outputting a test signal from the output port and detecting for the test signal at the input port, whereby it is determined that the battery cover is removed when the test signal is not detected at the input port and data is prohibited from being written into the memory card when the battery cover is removed;a communication module, wherein the short-circuit connecting member is an antenna of the communication module; anda state detection unit configured to detect whether the communication module is under a working state, wherein the writing control unit stops a detection of the battery cover and/or allows data to be written into the memory card if the state detection unit detects that the communication module is under the working state.(String), 1.移动端包括本体、电池和电池盖,其中,电池盖设有短路连接件;主体包括:存储卡插槽,用于容纳可插拔的存储卡;写入控制单元,包括输入端口和输出端口,写入控制单元配置成响应于电池盖与主体接合,写入控制单元的输入端口和输出端口均电接触短路-电路连接件,以在输入端口和输出端口之间形成短路连接;其中,写入控制单元被配置为通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除,从而当测试信号是时确定电池盖被移除。取下电池盖时输入口未检测到数据禁止写入存储卡;通信模块,其中短路连接件为通信模块的天线;和状态检测单元,用于检测通信模块是否处于工作状态,其中,如果状态检测单元检测到通信,则写入控制单元停止检测电池盖和/或允许数据写入存储卡模块处于工作状态。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 2. The mobile terminal according to claim 1, wherein,when the test signal is detected at the input port, the writing control unit determines that the battery cover is not removed, and allows data to be written into the memory card.(String), 2.根据权利要求1所述的移动终端,其中,当输入端口检测到测试信号时,写入控制单元判断电池盖未被移除,并允许数据写入存储卡。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 3. The mobile terminal according to claim 1, wherein,the communication module is a Bluetooth module or a Wireless Local Area Network communication module.(String), 3.根据权利要求1所述的移动终端,其中,通信模块为蓝牙模块或无线局域网通信模块。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 4. The mobile terminal according to claim 1, wherein the body further comprises:a state detection unit configured to detect whether the communication module is under an working state.(String), 4.根据权利要求1所述的移动终端,其中该主体还包括:状态检测单元,用于检测通信模块是否处于工作状态。(String), 1(Integer), 3(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.416 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 5. The mobile terminal according to claim 4, wherein, the writing control unit is further configured to detect regularly or at a time when there is data to be stored into the memory card, whether the battery cover is removed, in case the state detection unit detects that the communication module is not under the working state.(String), 5.根据权利要求4所述的移动终端,其中,写入控制单元还用于在状态检测单元检测到通信模块不处于工作状态时,定时或在有数据需要存储到存储卡时检测电池盖是否被取下.6.根据权利要求4所述的移动终端,其中,写入控制单元还用于当状态检测单元检测到通信模块处于工作状态时,停止检测电池盖和/或允许数据写入存储卡。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 6. The mobile terminal according to claim 4, wherein,the writing control unit is further configured to stop a detection of the battery cover and/or allow data to be written into the memory card, in case the state detection unit detects that the communication module is under the working state.(String), 7.根据权利要求1所述的移动终端,其中该主体还包括:切换单元,连接天线、写入控制单元和通信模块,用于将天线的工作模式切换为通信模式或检测模式,使得通信模块在通信模式下连接天线。,而写控制单元的输入端口和输出端口在检测模式下通过天线短路连接。(String), 1(Integer), 5(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 7. The mobile terminal according to claim 1, wherein the body further comprises:a switching unit connected to the antenna, the writing control unit and the communication module, and configured to switch an operation mode of the antenna into a communication mode or a detection mode, so that the communication module is connected to the antenna under the communication mode, while the input port and the output port of the writing control unit are in short-circuit connection via the antenna under the detection mode.(String), 8.根据权利要求1所述的移动终端,其中,写入控制单元还用于当状态检测单元检测到通信模块不处于工作状态时,控制切换电路切换到检测模式。(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 8. The mobile terminal according to claim 1, wherein,the writing control unit is further configured to control the switching circuit to switch into the detection mode, in case the state detection unit detects that the communication module is not under the working state.(String), 9.根据权利要求8所述的移动终端,其中,状态检测单元通过检测天线的信号强度来检测通信模块的工作状态;切换单元还用于当状态检测单元检测到天线的信号强度低于预定阈值或者信号强度的衰减量大于a时,将天线的工作模式切换为检测模式。预定阈值。10、一种移动终端中存储卡写保护的方法、移动终端包含本体、电池和电池盖,本体上设有存储卡座,用于容纳可插拔的存储卡和通信模块,电池盖上设有短路连接件,短路连接件为天线。通信模块,该方法包括:短路形成步骤,当电池盖与本体接合时,通过电池盖上的短路连接件在本体上设置的第一端口和第二端口之间形成短路连接;状态检测步骤,检测通信模块是否处于工作状态;短路检测步骤,通过在第二端口检测第一端口输入的测试信号来判断短路连接是否断开,从而判断电池盖是否脱离本体。和写保护步骤,当确定电池盖被从主体移除时,禁止数据写入存储卡,并且其中,写保护步骤还包括在检测到数据的情况下允许数据写入存储卡通信模块处于工作状态。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 9. The mobile terminal according to claim 8, wherein,the state detection unit detects the working state of the communication module by detecting a signal strength of the antenna;the switching unit is further configured to switch the operation mode of the antenna into the detection mode, in case the state detection unit detects that the signal strength of the antenna is lower than a predetermined threshold or a decrement of the signal strength is larger than a predetermined threshold.(String), 11.根据权利要求10所述的方法,其中写保护步骤还包括:当确定电池盖未从本体上取下时,允许向存储卡写入数据。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 10. A method of write protection for a memory card in a mobile terminal, the mobile terminal comprises a body, a battery and a battery cover, and the body is provided with a memory card socket configured to accommodate a pluggable memory card and a communication module, wherein the battery cover is provided with a short-circuit connecting member that is an antenna of the communication module, the method comprising:a short-circuit forming step that forms a short-circuit connection between a first port and a second port provided on the body, via the short-circuit connecting member on the battery cover when the battery cover is joined with the body;a state detecting step that detects whether the communication module is under a working state;a short-circuit detecting step that determines whether the short-circuit connection is disconnected by detecting at the second port for a test signal input from the first port, so as to determine whether the battery cover is removed from the body; anda write protection step that prohibits data from being written into the memory card when it is determined that the battery cover is removed from the body, and wherein the write protection step further comprises allowing data to be written into the memory card in case it is detected that the communication module is under the working state.(String), 12.根据权利要求1所述的方法,其中,短路检测步骤定期或在存储卡中有数据存储时进行,以防状态检测步骤检测到通信模块不处于工作状态。(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 11. The method according to claim 10, wherein the write protection step further comprises: allowing data to be written into the memory card when it is determined that the battery cover is not removed from the body.(String), 13.根据权利要求12所述的方法,还包括:在通信模块处于工作状态期间,当通信模块的天线信号强度低于预定阈值或天线信号强度衰减时,执行短路检测步骤。大于预定阈值。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.417 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 12. The method according to claim 1, wherein,the short-circuit detecting step is performed regularly or at a time when there is data to be stored into the memory card, in case it is detected in the state detecting step that the communication module is not under the working state.(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.418 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186015(Integer), 13. The method according to claim 12, further comprising:during a period in which the communication module is under the working state, performing the short-circuit detecting step in case a signal strength of the antenna of the communication module is lower than a predetermined threshold or a decrement of the signal strength of the antenna is larger than a predetermined threshold.(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.702 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.703 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186015(Integer), TECHNICAL FIELD [0001]The present invention relates to the field of electronic technology, and particularly, to a mobile terminal, and a method of write protection for a memory card in the mobile terminal. DESCRIPTION OF THE RELATED ART [0002]A smartphone with an independent operating system, used like a personal computer, can support the user to self-install programs such as software and games provided by a third party service provider, and can continually extend the functions of the smartphone through such programs. Thus the smartphone becomes more and more popular. Since various software may be self-installed by the user, the memory capacity of the smartphone per se often does not meet the demand for memory space. For this reason, the smartphone is usually provided with a memory card socket, so as to extend the memory space of the smartphone by inserting a pluggable memory card into the memory card socket. Thus, the memory card is of vital importance to the smartphone. In the current market, conventional memory cards for a smartphone, for example, include Multimedia Card (MMC), Secure Digital Memory Card (SD card) and TransFlash (TF) card, in which the SD card includes standard SD card, Elite Pro high speed card, miniSD card (also called as uSD card) and ultra speed SD card, etc. [0003]In some versions (e.g., Android 2.2 and above) of the operating system of a smartphone, application programs in the internal Flash can be written into the memory card. If the memory card is pulled out when a program is being written into the memory card, at least some data will not be successfully written into the memory card during the process of writing the program into the memory card, and a data loss will be caused, which may cause the memory card to be unusable, i.e., there is a risk of corrupting the memory card, and the return rate of the memory card is increased. SUMMARY OF THE INVENTION [0004]The present invention is proposed with respect to the above problem in the prior art. The present invention is related to a mobile terminal and a method of write protection for a memory card in the mobile terminal capable of stopping writing data into the memory card in time when the memory card is pulled out, so as to effectively provide a protection of the writing operation on the memory card. [0005]According to an aspect of the present invention, a mobile terminal is provided, including a body, a battery and a battery cover, wherein the battery cover is provided with a short-circuit connecting member; the body includes: a memory card socket configured to accommodate a pluggable memory card; and a write control unit, when the battery cover is jointed with the body, an input port and an output port of the writing control unit can both electrically contact the short-circuit connecting member, so as to form a short-circuit connection between the input port and the output port; wherein, the writing control unit detects whether the battery cover is removed by outputting a test signal from the output port and detecting the test signal at the input port; it is determined that the battery cover is removed when the test signal is not detected at the input port, and then data is prohibited from being written into the memory card. [0006]According to another aspect, when the test signal is detected at the input port, the writing control unit determines that the battery cover is not removed, and allows data to be written into the memory card. [0007]According to another aspect, the body further includes a communication module. According to another aspect, the short-circuit connecting member is an antenna of the communication module in the mobile terminal. [0008]According to another aspect, the communication module is a Bluetooth module or a Wireless Local Area Network (WLAN) communication module. [0009]According to another aspect, the body further includes a state detection unit configured to detect whether the communication module is under an working state. [0010]According to another aspect, the writing control unit is further configured to detect regularly or at a time when there is data to be stored into the memory card, whether the battery cover is removed, in case the state detection unit detects that the communication module is not under the working state. [0011]According to another aspect, the writing control unit is further configured to stop a detection of the battery cover and/or allow data to be written into the memory card, in case the state detection unit detects that the communication module is under the working state. [0012]According to another aspect, the body further includes a switching unit connected to the antenna, the writing control unit and the communication module, and configured to switch an operation mode of the antenna into a communication mode or a detection mode, so that the communication module is connected to the antenna under the communication mode, while the input port and the output port of the writing control unit are in short-circuit connection via the antenna under the detection mode. [0013]According to another aspect, the body further includes a state detection unit configured to detect whether the communication module is under an working state. [0014]According to another aspect, the writing control unit is further configured to control the switching circuit to switch into the detection mode, in case the state detection unit detects that the communication module is not under the working state. [0015]According to another aspect, the writing control unit stops a detection of the battery cover and/or allows data to be written into the memory card, in case the state detection unit detects that the communication module is under the working state. According to another aspect, the state detection unit detects the working state of the communication module by detecting a signal strength of the antenna; the switching unit is further configured to switch the operation mode of the antenna into the detection mode, in case the state detection unit detects that the signal strength of the antenna is lower than a predetermined threshold or a decrement of the signal strength is larger than a predetermined threshold. [0016]According to another aspect of the present invention, a method of write protection for a memory card in a mobile terminal is provided, the mobile terminal includes a body, a battery and a battery cover, and the body is provided with a memory card socket configured to accommodate a pluggable memory card, wherein the battery cover is provided with a short-circuit connecting member, the method comprising: a short-circuit forming step that forms a short-circuit connection between a first port and a second port provided on the body, via the short-circuit connecting member on the battery cover when the battery cover is jointed with the body; a short-circuit detecting step that determines whether the short-circuit connection is disconnected by detecting at the second port, a test signal input from the first port, so as to determine whether the battery cover is removed from the body; a write protection step that prohibits data from being written into the memory card when it is determined that the battery cover is removed from the body. [0017]According to another aspect, the write protection step further includes: allowing data to be written into the memory card when it is determined that the battery cover is not removed from the body. [0018]According to another aspect, the body further includes a communication module. According to another aspect, the short-circuit connecting member is an antenna of the communication module. [0019]According to another aspect, the method further includes a state detecting step that detects whether the communication module is under an working state. [0020]According to another aspect, the short-circuit detecting step is performed regularly or at a time when there is data to be stored into the memory card, in case it is detected in the state detecting step that the communication module is not under the working state. [0021]According to another aspect, the method further includes: allowing data to be written into the memory card in case it is detected in the state detecting step that the communication module is under the working state [0022]According to another aspect, the method further includes: during a period in which the communication module is under the working state, performing the short-circuit detecting step in case a signal strength of the antenna of the communication module is lower than a predetermined threshold or a decrement of the signal strength of the antenna is larger than a predetermined threshold. [0023]Features described and/or illustrated with respect to one embodiment can be used in one or more other embodiments in a same or similar way, and/or combine with or replace features in other embodiments. To be noted, the term “include/comprise/have” herein refers to existence of feature, component, step and assembly, not excluding existence or addition of one or more other features, components, steps, assemblies or a combination thereof. [0024]Many aspects of the present invention can be understood better with reference to the following drawings. The constituent parts of the drawings are not necessarily drafted in proportion or to scale, but are presented just for illustrating the present invention more clearly. For the convenience of illustrating and describing some parts of the present invention, and promoting the understanding of the embodiments, some parts of the drawings may be enlarged, e.g., enlarging those parts with respect to other parts in an exemplary apparatus practically manufactured according to the present invention. Elements and features described in a drawing or embodiment of the present invention can be combined with elements and features illustrated in one or more other drawings or embodiments. In addition, same or corresponding reference signs are used to represent same or corresponding constituent parts in all the drawings, and they also can be used to represent same or corresponding constituent parts in more than one of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS [0025]The accompanying drawings constitute a part of the specification, illustrate the embodiments of the present invention and together with the description serve to explain the present invention. The drawings described as follows illustrate several exemplary embodiments of the present invention, and a person skilled in the art can obtain other drawings based on these drawings without paying any creative effort. In the drawings: [0026]FIG. 1 is a schematic diagram of a battery cover provided with a short-circuit connecting member in an embodiment of the present invention; [0027]FIG. 2 is a schematic diagram of a battery cover detection apparatus in an embodiment of the present invention; [0028]FIG. 3 is a block diagram of a cell phone in an embodiment of the present invention; [0029]FIG. 4 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; [0030]FIG. 5 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; [0031]FIG. 6 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; [0032]FIG. 7 is a schematic diagram of a battery cover detection apparatus in another embodiment of the present invention; and [0033]FIG. 8 is a flowchart of a write protection method of a memory card in an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0034]These and further aspects and features of the present invention will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the invention have been disclosed in detail as being indicative of some of the ways in which the principles of the invention may be employed, but it is understood that the invention is not limited correspondingly in scope. Rather, the invention includes all changes, modifications and equivalents coming within the spirit and terms of the appended claims. [0035]To be noted, in order to avoid the present invention from being vague due to unnecessary details, the drawings only illustrate device structure and/or processing step closely associated with the solution of the present invention, and other details not so necessary to understand the present invention are omitted. [0036]In the design of some cell phones, the memory card socket is physically provided on an inner side of the battery cover of the cell phone (i.e., the side closer to the battery). Thus, the battery cover would be removed before the memory card is inserted or pulled out. For such designs of the cell phone, the present invention determines whether the memory card has a risk of being pulled out by detecting whether the battery cover is opened (i.e., removed). If the battery cover is not opened, the memory card will not be pulled out, and a program and/or other data can be safely written into the memory card. If the battery cover is opened, the memory card has a risk of being pulled out and the program and other data will be stopped from being written into the memory card, so as to realize a write protection of the memory card in the cell phone. In the embodiment of the present invention, the memory card may be MMC card, SD card, various memory sticks or any other type of pluggable memory card that can be used in the cell phone. [0037]Next, a cell phone will be taken as an example to describe the solution of the present invention that protects the memory card more detailedly. However, it shall be appreciated that the present invention is applicable to not only a cell phone, but also a [0038]PDA and other mobile terminal using a memory card in configuration that the battery cover of such mobile terminals needs to be opened before the memory card is pushed in or pulled out. [0039]Embodiment 1 [0040]In this embodiment, it is detected whether a battery cover of the cell phone is opened through a short-circuit connecting member provided on the battery cover. In this embodiment, the cell phone includes a body, a battery and a battery cover 1001. The battery cover 1001 is provided with a short-circuit connecting member 1002, as illustrated in FIG. 1. The short-circuit connecting member 1002 may be made of a metal material (including a alloy), or a non-metal conductive material such as carbon fiber. The short-circuit connecting member 1002 is preferably, but not limited to, a strip or strap-shaped sheet. It may be bonded onto the battery cover through an adhesive material, or formed on the battery cover through metal insert molding or deposition. For example, the metal sheet 1002 may be provided on the inner surface, the outer surface or the inside of the battery cover. In case of being provided on the outer surface or the inside of the battery cover, the metal sheet 1002 exposes two connecting contact points (also called as connection pads) 1005 on the inner surface of the battery cover. [0041]In this embodiment, the body of the cell phone includes not only a memory card socket (not illustrated) for accommodating the memory card and conventional components (e.g., processor, display, input unit and communication module), but also a writing control unit 120, as illustrated in FIG. 2. The writing control unit 120 includes an output port A1 and an input port A2. When the battery cover is jointed with (e.g., attached to, connected to) the body of the cell phone, the output port A1 and the input port A2 of the writing control unit 120 electrically contact the short-circuit connecting member 1002, so as to form a short-circuit connection between the output port A1 and the input port A2. The output port A1 and the input port A2 may electrically contact the short-circuit connecting member 1002 through terminals 1004 (e.g., but not limited to, pogo pins or spring fingers). When the battery cover 1001 is removed from the body of the cell phone (as illustrated by the dotted line in FIG. 2), the short-circuit connecting member 1002 no longer contacts the output port A1 or the input port A2, thus the short-circuit connection between the output port A1 and the input port A2 is disconnected. [0042]In this embodiment of the present invention, when it is to be detected whether the battery cover is removed, the writing control unit 120 may output a test signal at the output port A1 and detect (i.e., receive) the test signal at the input port A2. The test signal for example may be, but not limited to, square wave, sine wave, triangular wave or sawtooth wave. When the test signal is detected (i.e., received) at the input port A2, it means that the short-circuit connection between the output port A1 and the input port A2 is not disconnected, and thus the battery cover is not removed. When the test signal is not detected (i.e., received) at the input port A2, it means that the short-circuit connection between the output port A1 and the input port A2 is disconnected, and thus the battery cover is removed. In case the battery cover is removed, the user may pull out the memory card. In order to prevent data loss and memory card corrupting caused by writing data into the memory card during the process of pulling out the memory card, the writing control unit 120 prohibits (including stopping) a program or other data from being written into the memory card when it is determined that the battery cover is removed, and allows the program or other data to be written into the memory card when it is determined that the battery cover is not removed. [0043]In FIG. 2, pull-up resistors R1 and R2 may be used to pull up the levels of the ports A1 and A2. The resistances of the pull-up resistors R1 and R2 may be the same or different from each other. For example, the pull-up resistors R1 and R2 may be 5.2 KΩ, respectively. This value is just exemplary, and other values may be set in practice. [0044]In an embodiment of the present invention, the writing control unit 120 may regularly (e.g., at an interval of 0.1 s, 0.5 s or 1 s; these values are just exemplary, and other values may be adopted) send a test signal through the output port A1, determine whether the battery cover is removed by checking whether the test signal is received at the input port A2, and correspondingly control (prohibits or allows) the data such as a program to be written into the memory card. [0045]In another embodiment of the present invention, the writing control unit 120 may be started only when data (e.g., program, application or other data) is to be written into the memory card. The writing control unit 120 sends a test signal through the output port A1, and determines whether the battery cover is removed by checking whether the test signal is received at the input port A2. The writing control unit 120 allows the data to be written into the memory card when it is determined that the battery cover is not removed, or prohibits (including stopping) the data from being written into the memory card when it is determined that the battery cover is removed. [0046]By detecting the battery cover, the writing control unit 120 as mentioned above effectively provides a write protection when the battery cover is opened. Thus, the corrupting of the memory card and the failure in running of an application program caused by the data writing error can be prevented, the data writing security of the memory card is improved, and the return rate of the memory card is effectively reduced. [0047]FIG. 3 is a block diagram of a cell phone 1 in an embodiment of the present invention, including the aforementioned writing control unit 120. This drawing is exemplary and other types of structures may be used to replace the illustrated structure, so as to realize the telecom function or other functions. As illustrated in FIG. 3, the cell phone 1 includes a CPU 100, a communication module 110, a writing control unit 120, an audio processor 130, a memory 140, a camera 150, a display 160, an input unit 180 and a power supply 170. The CPU 100 (sometimes called as a controller or an operation control, and may include a microprocessor or other processor device and/or logic device) receives an input and controls operations of respective parts of the cell phone 1. The input unit 180 provides an input to the CPU 100. The input unit 180 for example is a key or a touch input device. The camera 150 is configured to take image data and provide it to the CPU 100 for a conventional usage, e.g., storage, transmission, etc. [0048]The power supply 170 is configured to supply power to the cell phone 1. The display 160 is configured to display an object to be displayed, such as images and text. The display 160 for example may be, but not limited to, an LCD display. The input unit 180 for example may be the key itself and/or a signal regulating circuit, a decoding circuit or other appropriate circuit that provides the CPU 100 with information for operating one or more keys in a conventional way. The memory 140 is coupled to the CPU 100. The memory 140 may be a solid state memory, e.g., ROM, RAM, SIM card, etc. The memory 140 also may be such a memory that stores information even when the power is off and can be selectively erased and provided with more data. An example of the memory sometimes is called EPROM. The memory 140 further may be a device of other certain type. The memory 140 includes a buffer memory 141 (sometimes called as buffer). The memory 140 may include an application/function storage section 142 configured to store an application program or a function program, or operation flow of the cell phone 1 to be performed through the CPU 100. The memory 140 may further include a data storage section 143 configured to store data, such as contact list, digital data, picture, sound and/or any other data used by the cell phone 1. Various drive programs for performing the communication function of the cell phone 1 and/or other functions (e.g., message transfer application, address list application, etc.) of the cell phone 1 may be included in a drive program storage section 144 of the memory 140. [0049]The communication module 110 is a transmitter/receiver 110 that transmits and receives signals via an antenna 111. The communication module (transmitter/receiver) 110 is coupled to the CPU 100 to provide an input signal and receive an output signal, which may be the same as the case of a conventional cell phone. Based on different communication technologies, a cell phone may be provided with multiple communication modules 110, e.g., cellular network module, bluetooth module and/or Wireless Local Area Network (WLAN) module, etc. The communication module (transmitter/receiver) 110 is also coupled to a loudspeaker 131 and a microphone 132 via an audio processor 130, so as to provide an audio output via the loudspeaker 131 and receives an audio input from the microphone 132, thus the conventional telecom functions can be realized. The audio processor 130 may include any appropriate buffer, decoder, amplifier, etc. In addition, the audio processor 130 is further coupled to the CPU 100, so that a sound recording can be performed on the cell phone through the microphone 132, and the sound stored in the cell phone can be played through the loudspeaker 131. [0050]Embodiment 2 [0051]In the design of some cell phones, the antenna of a communication module such as the Bluetooth module or the WLAN module is provided on the battery cover of the cell phone. Based on such a design of some cell phones, the antenna of the communication module provided on the battery cover is used as the short-circuit connecting member 1002 in this embodiment. [0052]FIG. 4 is a schematic diagram of a battery cover detection apparatus in this embodiment. As illustrated in FIG. 4, the antenna 1003 of the communication module (e.g. [0053]the Bluetooth module or the WLAN module) provided on the battery cover is used as the short-circuit connecting member to perform a short-circuit connection between the output port A1 and the input port A2 of the writing control unit 120. The communication module 110 may be electrically connected to the antenna 1003 through two terminals 1004 (e.g., but not limited to, pogo pins or spring fingers) which also serve as the terminals for an electrical connection from the output port A1 and the input port A2 of the writing control unit 120 to the antenna. That is, the communication module 110 and the writing control unit 120 are connected to the antenna through the common terminals. [0054]Reference is made to FIGS. 4 and 5. As illustrated in FIG. 4, a switching unit 113 is provided between the antenna 1003 and a matching circuit 112 of the communication module 110, and further is connected to the writing control unit 120, so as to switch the operation mode of the antenna 1003 into a communication mode (in which the antenna 1003 is connected to the matching circuit 112) or a detection mode (in which the antenna 1003 is connected to the input and output ports of the writing control unit 120). When the switching unit 113 switches the operation mode of the antenna into the communication mode (as illustrated in FIG. 4), a detection of the open or closed state of the battery cover cannot be carried out, and then it may be deemed that the battery cover detection function is disabled. When the switching unit 113 switches the operation mode of the antenna into the detection mode (as illustrated in FIG. 5), the detection of the open or closed state of the battery cover can be carried out, and then it may be deemed that the battery cover detection function is enabled. In an embodiment of the present invention, the writing control unit 120 may enable the switching unit 113 through a pin A3, so as to control the switching unit 113 to switch between the communication mode and the detection mode. [0055]In case the communication module is under a working state, the antenna is under the communication mode and is being used. Since the antenna is provided on the battery cover, it can be determined that the battery cover is certainly in a closed state, i.e., jointed with the body of the cell phone. Thus, it is unnecessary to detect the battery cover at that time, and the writing control unit 120 may allow the data such as a program to be written into the memory card when the communication module is under the working state. In order to detect the working state of the communication module, the cell phone is further provided with a state detection unit 121 connected to the communication module and the writing control unit 120 or disposed in any one of the communication module and the writing control unit (FIG. 4 illustrates the case that the state detection unit 121 is disposed in the writing control unit), so as to detect whether the communication module is in the working state. When the state detection unit 121 detects that the communication module is in the working state, the writing control unit 120 no longer detects the state of the battery cover. In an embodiment of the present invention, the state detection unit 121 may detect the working state of the communication module by detecting the antenna signal quality (e.g., antenna signal strength, etc.) in the communication module or other parameter indicating that the antenna is being used. [0056]In an embodiment of the present invention, when the state detection unit 121 detects that the communication module is not in the working state, the writing control unit 120 may control the switching unit 113 through the pin A3 to switch into the detection mode regularly (e.g., at an interval of 1 s (i.e., 1 second), 2 s, 3 s or other value), i.e., to enable the detection function for the battery cover. During a period in which the detection function is enabled, the writing control unit 120 may constantly or regularly (e.g., at an interval of 0.25 s, 0.5 s, 1 s or other value) send a test signal through the output port A1, determine whether the battery cover is removed by checking whether the test signal is received at the input port A2, and correspondingly control (prohibits or allows) the data such as a program to be written into the memory card. [0057]In another embodiment of the present invention, in case the state detection unit 121 detects that the communication module is not in the working state, the writing control unit 120 may control the switching unit 113 through the pin A3 to switch into the detection mode only when data (e.g., program, application or other data) is to be written into the memory card, so that the writing control unit 120 detects whether the battery cover is removed, and correspondingly controls (prohibits or allows) the data such as a program to be written into the memory card. [0058]Further, during a period in which the communication module is under the working state, there is a possibility that the antenna and the communication module may be disconnected from each other when the state detection unit 121 detects that the connection between the communication module and the network suddenly becomes worse, for example the signal quality declines sharply, e.g., the antenna signal strength is lower than a predetermined threshold (for example, but not limited to, −90 dBm) or the is variation of the antenna signal strength (for example the variation (decrement) between two antenna signal strengths detected successively) is larger than a predetermined threshold (for example, but not limited to, 20 dB). In that case, the writing control unit 120 may control the switching unit 113 through the pin A3 to switch into the detection mode, so as to detect whether the battery cover is removed, and correspondingly control (prohibits or allows) the data such as a program to be written into the memory card. [0059]When the communication module 110 is to be used again for a communication, the communication module 110 may send an instruction signal to the writing control unit 120, which enables the switching unit 113 through the pin A3 to switch from the detection mode into the communication mode, so that the communication module 110 performs a communication through the antenna, and the writing control unit 120 stops detecting the battery cover at that time. [0060]This embodiment also provides a write protection for the memory card, so as to prevent the corrupting of the memory card and a failure in running of an application program caused by a data writing error, improve the data writing security of the memory card, and effectively reduce the return rate of the memory card. [0061]In another embodiment of the present invention, alternatively, the communication module 110 and the writing control unit 120 may be connected to the antenna through their respective terminals instead of the common terminals, so as to realize the communication function and the battery cover detection function, respectively, as illustrated in FIG. 6. In that case, the switching unit 113 and the pin A3 of the writing control unit 120 may be omitted. But the working state of the communication module 110 still can be detected through the state detection unit 121. In case the communication module 110 is under the working state, the writing control unit 120 may allow the data such as a program to be written into the memory card; while in case the communication module 110 is not under the working state, the writing control unit 120 may detect regularly (e.g., periodically) or at a time when there is data to be written into the memory card, whether the battery cover is removed and correspondingly control (prohibit or allow) the data such as a program to be written into the memory card. [0062]In another embodiment of the invention, the antenna 111 of the communication module 110 and the short-circuit connecting member 1002, which establishes a short-circuit connection between the output port A1 and the input port A2 of the writing control unit 120, may be separately provided at different positions on the battery cover 1001. In that case, the communication module 110 and the short-circuit connecting member 1002 may independently realize their respective functions, i.e., the communication function and the battery cover detection function, as illustrated in FIG. 7. [0063]Alternatively, the writing control unit 120 may be connected to the communication module 110 through the state detection unit 121, so that the writing control unit 120, according to the detection of the sta(String), 技术领域 [0001] 本发明涉及电子技术领域,具体涉及一种移动终端及移动终端中存储卡的写保护方法。 相关技术的描述 [0002] 具有独立操作系统的智能手机,像个人电脑一样使用,可以支持用户自行安装第三方服务商提供的软件、游戏等程序,并可以通过这些程序不断扩展智能手机的功能。 因此,智能手机变得越来越流行。 由于用户可能会自行安装各种软件,因此智能手机本身的内存容量往往不能满足内存空间的需求。 为此,智能手机通常设置有存储卡插槽,通过在存储卡插槽中插入可插拔的存储卡来扩展智能手机的存储空间。 因此,存储卡对于智能手机来说至关重要。 在目前市场上,传统的智能手机存储卡,例如,包括多媒体卡(MMC)、安全数字存储卡(SD卡)和TransFlash(TF)卡,其中SD卡包括标准SD卡、Elite Pro high speed卡、miniSD卡(也称uSD卡)和超高速SD卡等。 [0003] 在某些版本的智能手机操作系统(如Android 2.2及以上)中,可以将内部Flash中的应用程序写入存储卡中。 如果在向存储卡写入程序的过程中拔出存储卡,在向存储卡写入程序的过程中,至少会有部分数据无法成功写入存储卡,造成数据丢失 ,这可能会导致存储卡无法使用,即存在损坏存储卡的风险,增加了存储卡的退货率。 发明内容 [0004] 本发明是针对现有技术中存在的上述问题而提出的。 本发明涉及一种移动终端及移动终端中存储卡的写保护方法,能够在存储卡被拔出时及时停止向存储卡写入数据,从而有效地提供对存储卡的保护。 对存储卡的写入操作。 [0005] 根据本发明的一个方面,提供了一种移动终端,包括本体、电池和电池盖,所述电池盖上设置有短路连接件; 主体包括:存储卡插槽,用于容纳可插拔的存储卡; 以及写入控制单元,当电池盖与本体接合时,写入控制单元的输入端口和输出端口均能够电接触短路连接件,从而在电池盖与本体之间形成短路连接。 输入端口和输出端口; 其中,写入控制单元通过从输出端口输出测试信号并在输入端口检测测试信号来检测电池盖是否被移除。 当输入端口未检测到测试信号时,判断为取下电池盖,禁止向存储卡写入数据。 [0006] 根据另一方面,当在输入端口检测到测试信号时,写入控制单元确定电池盖未被移除,并允许数据写入存储卡。 [0007] 根据另一方面,主体还包括通信模块。 根据另一方面,短路连接件是移动终端中的通信模块的天线。 [0008] 根据另一方面,通信模块是蓝牙模块或无线局域网(WLAN)通信模块。 [0009] 根据另一方面,本体还包括状态检测单元,用于检测通信模块是否处于工作状态。 [0010]另一方面,所述写入控制单元还用于在所述状态检测单元检测到所述通信模块被关闭时,定期或在有数据需要存储到所述存储卡时检测所述电池盖是否被移除。 不在工作状态。 [0011] 根据另一方面,写入控制单元还用于当状态检测单元检测到通信模块处于工作状态时,停止检测电池盖和/或允许数据写入存储卡。 [0012] 根据另一方面,本体还包括切换单元,连接到天线、写入控制单元和通信模块,用于将天线的工作模式切换为通信模式或检测模式,使得通信模块 在通信模式下,与天线相连,而在检测模式下,写入控制单元的输入端口和输出端口通过天线短接。 [0013] 根据另一方面,本体还包括状态检测单元,用于检测通信模块是否处于工作状态。 [0014] 根据另一方面,写入控制单元还用于当状态检测单元检测到通信模块不处于工作状态时,控制切换电路切换到检测模式。 [0015] 根据另一方面,当状态检测单元检测到通信模块处于工作状态时,写入控制单元停止检测电池盖和/或允许数据写入存储卡。 根据另一方面,状态检测单元通过检测天线的信号强度来检测通信模块的工作状态; 切换单元还用于当状态检测单元检测到天线的信号强度低于预定阈值或者信号强度的衰减量大于a时,将天线的工作模式切换为检测模式。 预定阈值。 [0016] 根据本发明的另一个方面,提供了一种移动终端中存储卡的写保护方法,该移动终端包括本体、电池和电池盖,本体上设置有存储卡插槽,该插槽配置有 容纳可插拔存储卡,其中,电池盖设有短路连接件,该方法包括: 短路形成步骤,在主体上设置的第一端口和第二端口之间形成短路连接 、电池盖与本体接合时通过电池盖上的短路连接件; 短路检测步骤,通过在第二端口检测第一端口输入的测试信号,判断短路连接是否断开,从而判断电池盖是否脱离本体。 写保护步骤,当确定电池盖已从机体上取下时,禁止数据写入存储卡。 [0017] 根据另一个方面,写保护步骤还包括:当确定电池盖未从本体移除时,允许将数据写入存储卡。 [0018] 根据另一方面,主体还包括通信模块。 根据另一方面,短路连接件是通信模块的天线。 [0019] 根据另一方面,该方法还包括状态检测步骤,检测通信模块是否处于工作状态。 [0020] 根据另一方面,短路检测步骤定期或在存储卡中有数据存储时执行,以防状态检测步骤检测到通信模块不处于工作状态 . [0021]另一方面,该方法还包括:当状态检测步骤检测到通信模块处于工作状态时,允许向存储卡写入数据。 [0022] 根据另一个方面,该方法还包括:在通信模块处于工作状态期间,当通信模块的天线的信号强度低于预定阈值时,执行短路检测步骤,或者 天线信号强度的衰减量大于预定阈值。 [0023] 关于一个实施例描述和/或图示的特征可以相同或相似的方式用于一个或多个其他实施例,和/或与其他实施例中的特征组合或替换。 需要说明的是,此处的术语“包括/包含/具有”是指特征、组件、步骤和组件的存在,不排除存在或添加一个或多个其他特征、组件、步骤、组件或其组合。 [0024] 参考以下附图可以更好地理解本发明的许多方面。 附图的组成部分不一定按比例或比例绘制,只是为了更清楚地说明本发明而呈现。 为了便于说明和描述本发明的某些部分,以及促进对实施例的理解,附图中的某些部分可能被放大,例如,相对于根据实施例实际制造的示例性装置中的其他部分放大这些部分 本发明。 本发明的附图或实施例中描述的元素和特征可以与一个或多个其他附图或实施例中所示的元素和特征组合。 另外,在所有附图中,相同或相应的附图标记用于表示相同或相应的组成部分,也可以在一个以上的实施例中使用相同或相应的附图标记来表示相同或相应的组成部分。 附图的简要说明 [0025] 附图构成说明书的一部分,用于说明本发明的实施例,并与说明书一起用于解释本发明。 以下所描述的附图为本发明的几个优选实施例,本领域技术人员在不付出创造性劳动的情况下,基于这些附图所获得的其他附图。 在图纸中: [0026] 图1为本发明实施例中设置有短路连接件的电池盖的示意图; [0027] 图2为本发明实施例的电池盖检测装置的示意图; [0028] 图3是本发明实施例中手机的框图; [0029] 图4为本发明另一实施例的电池盖检测装置的示意图; [0030] 图5为本发明另一实施例的电池盖检测装置的示意图; [0031] 图6为本发明另一实施例的电池盖检测装置的示意图; [0032] 图7为本发明另一实施例的电池盖检测装置的示意图; 和 [0033] 图8为本发明实施例的存储卡写保护方法的流程图。 优选实施例的详细说明 [0034] 参考以下描述和附图,本发明的这些和进一步的方面和特征将是显而易见的。 在描述和附图中,本发明的特定实施例已经被详细地公开为指示可以采用本发明的原理的一些方式,但是应当理解本发明不相应地限制在范围上。 相反,本发明包括落入所附权利要求的精神和条款内的所有变化、修改和等同物。 [0035]需要说明的是,为避免不必要的细节使本发明含糊不清,附图仅说明与本发明方案密切相关的装置结构和/或工艺步骤,其他细节对理解本发明不是必需的。 发明省略。 [0036] 在一些手机的设计中,存储卡插槽物理上设置在手机电池盖的内侧(即靠近电池的一侧)。 因此,在插入或拔出存储卡之前,电池盖将被移除。 对于这样的手机设计,本发明通过检测电池盖是否被打开(即取下)来判断存储卡是否存在被拔出的风险。 如果不打开电池盖,则不会拔出存储卡,可以安全地将程序和/或其他数据写入存储卡。 如果电池盖被打开,存储卡有被拔出的风险,程序和其他数据将停止写入存储卡,从而实现手机中存储卡的写保护。 在本发明实施例中,存储卡可以是MMC卡、SD卡、各种记忆棒或者其他任何一种可以在手机中使用的可插拔存储卡。 [0037] 下面以手机为例,对本发明保护存储卡的方案进行更详细的说明。 然而,应当理解,本发明不仅适用于手机,还适用于 [0038] PDA等使用存储卡的移动终端的配置是,在推入或拔出存储卡之前需要打开电池盖。 [0039] 实施例一 [0040] 在本实施例中,通过设置在电池盖上的短路连接件来检测手机电池盖是否被打开。 在本实施例中,手机包括机身、电池和电池盖。 1001 . 电池盖 1001 设有短路连接件 1002 ,如图1所示。短路连接件 1002 可以由金属材料(包括合金)或碳纤维等非金属导电材料制成。 短路连接件 1002 优选但不限于条状或带状片材。 它可以通过粘合材料粘合到电池盖上,或者通过金属嵌件成型或沉积形成在电池盖上。 例如,金属板 1002 可以设置在电池盖的内表面、外表面或内侧。 如果设置在电池盖的外表面或内侧,金属片 1002 暴露两个连接触点(也称为连接垫) 1005 在电池盖的内表面上。 [0041] 在本实施例中,手机的机身不仅包括用于容纳存储卡和常规部件(例如处理器、显示器、输入单元和通信模块)的存储卡插槽(未示出),还包括写入控制单元。 120 ,如图2所示。写入控制单元 120 包括一个输出端口A 1 和一个输入端口A 2 . 当电池盖与手机机身接合(如贴附、连接)时,输出端口A 1 和输入端口A 2 写控制单元 120 电接触短路连接件 1002 ,从而形成输出端口A之间的短路连接 1 和输入端口A 2 . 输出口A 1 和输入端口A 2 可以电接触短路连接件 1002 通过终端 1004 (例如但不限于弹簧针或弹簧夹)。 当电池盖 1001 从手机机身上取下(如图2中虚线所示),短路连接件 1002 不再接触输出端口A 1 或输入端口A 2 ,因此输出端口A之间的短路连接 1和输入端口A 2 已断开连接。 [0042] 本发明实施例中,当检测电池盖是否被取下时,写入控制单元 120 可在输出端口A输出测试信号 1 检测(即接收)输入端口A的测试信号 2 . 测试信号例如可以是但不限于方波、正弦波、三角波或锯齿波。 当在输入端口 A 检测到(即接收到)测试信号时 2 ,这意味着输出端口A之间的短路连接 1 和输入端口A 2 未断开,因此电池盖未取下。 当在输入端口 A 未检测到(即接收到)测试信号时 2 ,这意味着输出端口A之间的短路连接 1 和输入端口A 2 断开连接,从而取下电池盖。 如果取下电池盖,用户可以拔出存储卡。 为了防止在拔出存储卡的过程中向存储卡写入数据而导致数据丢失和损坏存储卡,写入控制单元 120 禁止(包括停止)在确定电池盖被移除时将程序或其他数据写入存储卡,并在确定电池盖被移除时允许程序或其他数据写入存储卡 没有被删除。 [0043] 图2中,上拉电阻R 1 和R 2 可用于拉高端口 A 的电平 1 和一个 2 . 上拉电阻R的阻值 1 和R 2 可以彼此相同或不同。 例如,上拉电阻 R 1 和R 2 可能分别为 5.2 KΩ。 该值只是示例性的,实际中还可以设置其他值。 [0044] 在本发明的一个实施例中,写入控制单元 120 可以有规律地(例如,以0.1s、0.5s或1s的间隔;这些值只是示例性的,可以采用其他值)通过输出端口A发送测试信号 1 ,通过检查输入端口A是否收到测试信号来判断电池盖是否被取下 2 ,并相应地控制(禁止或允许)将程序等数据写入存储卡。 [0045] 在本发明的另一个实施例中,写入控制单元 120 仅当数据(例如,程序、应用程序或其他数据)要写入存储卡时才可启动。 写入控制单元 120 通过输出端口A发送测试信号 1 ,通过检测输入端口A是否接收到测试信号来判断电池盖是否被移除 2 . 写入控制单元 120 当确定电池盖未被取下时允许数据写入存储卡,或者当确定电池盖被取下时禁止(包括停止)数据写入存储卡。 [0046] 通过检测电池盖,写控制单元 120 如上所述,当电池盖打开时,有效地提供了写保护。 从而可以防止数据写入错误导致存储卡损坏和应用程序无法运行,提高了存储卡数据写入的安全性,有效降低了存储卡的报废率。 [0047] 图3是手机的框图 1 在本发明的一个实施例中,包括上述的写入控制单元 120 . 该图是示例性的,可以用其他类型的结构代替所示结构,以实现电信功能或其他功能。 如图3所示,手机 1 包括一个中央处理器 100 , 通信模块 110 , 一个写控制单元 120 , 音频处理器 130 , 一段记忆 140 , 相机 150 , 一个显示器 160 , 一个输入单元 180 和电源 170 . 中央处理器 100(有时称为控制器或操作控制器,可能包括微处理器或其他处理器设备和/或逻辑设备)接收输入并控制手机各部分的操作 1 . 输入单元 180 向 CPU 提供输入 100 . 输入单元 180 例如是按键或触摸输入设备。 相机 150 配置为获取图像数据并将其提供给 CPU 100 用于常规用途,例如存储、传输等。 [0048] 电源 170 配置为手机供电 1 . 显示器 160 用于显示待显示对象,例如图片、文字等。 显示器 160 例如可以是但不限于LCD显示器。 输入单元 180 例如可以是钥匙本身和/或信号调节电路、解码电路或提供CPU的其他适当电路 100 具有以常规方式操作一个或多个键的信息。 记忆 140 耦合到CPU 100 . 记忆 140 可以是固态存储器,例如 ROM、RAM、SIM 卡等。存储器 140 也可以是这样的存储器,即使在电源关闭时也能存储信息,并且可以选择性地擦除并提供更多数据。 存储器的一个例子有时称为 EPROM。 记忆 140 进一步可能是其他某种类型的设备。 记忆 140 包括一个缓冲存储器 141 (有时称为缓冲区)。 记忆 140 可能包括一个应用程序/功能存储部分 142 用于存储应用程序或功能程序,或手机的操作流程 1 通过CPU执行 100 . 记忆 140 还可以包括数据存储部分 143 配置为存储数据,例如联系人列表、数字数据、图片、声音和/或手机使用的任何其他数据 1 . 执行手机通信功能的各种驱动程序 1 和/或手机的其他功能(例如,消息传输应用程序、地址列表应用程序等) 1 可以包含在驱动程序存储部分中 144 记忆的 140 . [0049] 通信模块 110 是一个发射器/接收器 110 通过天线发送和接收信号 111 . 通信模块(发射器/接收器) 110 耦合到CPU 100 提供输入信号和接收输出信号,可以与传统手机的情况相同。 基于不同的通信技术,一部手机可以配备多个通信模块 110 ,例如,蜂窝网络模块、蓝牙模块和/或无线局域网 (WLAN) 模块等。 通信模块(发射器/接收器) 110 也耦合到扬声器 131 和麦克风 132 通过音频处理器 130 ,以便通过扬声器提供音频输出 131 并接收来自麦克风的音频输入 132 ,从而实现常规的电信功能。 音频处理器 130 可能包括任何适当的缓冲器、解码器、放大器等。此外,音频处理器 130 进一步耦合到CPU 100 ,这样就可以通过麦克风在手机上进行录音 132 ,并且可以通过扬声器播放手机中存储的声音 131 . [0050] 实施例二 [0051] 在一些手机的设计中,蓝牙模块或WLAN模块等通信模块的天线设置在手机的电池盖上。 基于一些手机的这种设计,将设置在电池盖上的通信模块的天线用作短路连接件 1002 在这个实施例中。 [0052] 图4为本实施例的电池盖检测装置的示意图。 如图 4 所示,天线 1003 通信模块(例如 [0053]设置在电池盖上的蓝牙模块或WLAN模块)作为短路连接件,将输出端口A之间进行短路连接 1 和输入端口A 2 写控制单元 120 . 通信模块 110 可以电连接到天线 1003 通过两个终端 1004 (例如,但不限于弹簧针或弹簧夹),它们也用作输出端口 A 的电气连接端子 1 和输入端口A 2 写控制单元 120 到天线。 即通信模块 110 和写控制单元 120 通过公共端子连接到天线。 [0054] 参考图4和图5。如图4所示,切换单元 113 天线之间提供 1003 和匹配电路 112 通信模块 110 ,进一步连接到写控制单元 120 ,从而切换天线的工作模式 1003 进入通信模式(其中天线 1003 连接到匹配电路 112 )或检测模式(其中天线 1003 接写控制单元的输入输出端口 120 ). 当切换单元 113 将天线的工作模式切换为通信模式(如图4所示),则无法进行电池盖开启或关闭状态的检测,则可认为电池盖检测功能被关闭 . 当切换单元 113 将天线的工作模式切换为检测模式(如图5所示),即可进行电池盖打开或关闭状态的检测,则可认为电池盖检测功能已启用 . 在本发明的一个实施例中,写入控制单元 120 可以启用开关单元 113 通过引脚 A 3 ,从而控制开关单元 113 在通信模式和检测模式之间切换。 [0055] 在通信模块处于工作状态的情况下,天线处于通信模式并且正在被使用。 由于天线设置在电池盖上,因此可以确定电池盖肯定处于闭合状态,即与手机机身接合。 因此,此时无需检测电池盖,写入控制单元 120 可以允许通信模块在工作状态下将程序等数据写入存储卡。 为了检测通信模块的工作状态,手机还设置有状态检测单元 121 连接通讯模块和写控制单元 120 或者设置在通信模块和写控制单元中的任一个(图4说明了状态检测单元的情况 121 设置于写入控制单元),以检测通信模块是否处于工作状态。 当状态检测单元 121 检测到通信模块处于工作状态,写入控制单元 120 不再检测电池盖的状态。 在本发明的一个实施例中,状态检测单元 121 可以通过检测通信模块中的天线信号质量(例如,天线信号强度等)或其他指示天线正在使用的参数来检测通信模块的工作状态。 [0056] 在本发明的一个实施例中,当状态检测单元 121 检测到通讯模块不在工作状态,写入控制单元 120 可以控制开关单元 113 通过引脚 A 3 定时切换到检测模式(如间隔1s(即1秒)、2s、3s或其他值),即开启电池盖检测功能。 在启用检测功能期间,写入控制单元 120可以不断地或有规律地(例如,以0.25s、0.5s、1s或其他值的间隔)通过输出端口A发送测试信号 1 ,通过检查输入端口A是否收到测试信号来判断电池盖是否被取下 2 ,并相应地控制(禁止或允许)将程序等数据写入存储卡。 [0057] 在本发明的另一个实施例中,如果状态检测单元 121 检测到通讯模块不在工作状态,写入控制单元 120 可以控制开关单元 113 通过引脚 A 3 只有当数据(例如,程序、应用程序或其他数据)被写入存储卡时才切换到检测模式,使得写入控制单元 120 检测电池盖是否被取下,并相应控制(禁止或允许)向存储卡写入程序等数据。 [0058] 进一步地,在通信模块处于工作状态期间,状态检测单元有可能导致天线与通信模块断开连接。 121 检测到通信模块与网络的连接突然变差,例如信号质量急剧下降,例如天线信号强度低于预定阈值(例如但不限于-90dBm)或 是天线信号强度的变化量(例如连续检测到的两个天线信号强度之间的变化量(减量))大于预定阈值(例如但不限于20dB)。 在这种情况下,写入控制单元 120 可以控制开关单元 113 通过引脚 A 3 切换到检测模式,检测电池盖是否被取下,并相应地控制(禁止或允许)向存储卡写入程序等数据。 [0059] 当通信模块 110 再次用于通信,通信模块 110 可以向写控制单元发送指令信号 120 ,这使得开关单元 113 通过引脚 A 3 从检测模式切换到通信模式,使通信模块 110 通过天线进行通信,写控制单元 120 那时停止检测电池盖。 [0060] 本实施例还对存储卡进行了写保护,以防止数据写入错误导致存储卡损坏和应用程序无法运行,提高了存储卡数据写入的安全性,有效地 降低存储卡的退货率。 [0061] 在本发明的另一个实施例中,可选地,通信模块 110 和写控制单元 120 可以通过各自的端子而不是公共端子连接到天线,从而分别实现通信功能和电池盖检测功能,如图6所示。在这种情况下,切换单元 113 和引脚A 3 写控制单元 120 可以省略。 但通讯模块的工作状态 110 仍然可以通过状态检测单元进行检测 121 . 万一通信模块 110 处于工作状态,写控制单元 120 可以允许将程序等数据写入存储卡; 而万一通信模块 110 不在工作状态下,写控制单元 120 可以定时(例如周期性)或在有数据写入内存卡时检测电池盖是否被取下,并相应地控制(禁止或允许)程序等数据写入内存 卡片。 [0062] 在本发明的另一个实施例中,天线 111 通信模块 110 和短路连接件 1002 ,它建立了输出端口A之间的短路连接1 和输入端口A 2 写控制单元 120 , 可分别设置在电池盖上的不同位置 1001 . 在这种情况下,通信模块 110 和短路连接件 1002 可以独立实现各自的功能,即通信功能和电池盖检测功能,如图7所示。 [0063] 或者,写控制单元 120 可以连接到通信模块 110 通过状态检测单元 121 , 使写控制单元 120 , 根据状态检测单元的检测 121 ,允许将程序等数据写入存储卡中,以防通信模块 110 处于工作状态,而万一通信模块 110 不在工作状态下,写控制单元 120 定时(例如周期性地)或在有数据写入存储卡时,检测电池盖是否被取下,并相应地控制(禁止或允许)向存储卡写入程序等数据 . 状态检测单元 121 可以连接到通信模块 110 和写控制单元 120 ,或设置于任一通讯模块 110 和写控制单元 120 . 或者,当通信模块的天线 110 和短路连接件 1002 单独提供,通信模块的天线 110 可以设置在手机机身上的其他位置,而不是在电池盖上。 下面结合上述手机的结构,对本发明实施例的存储卡的写保护方法进行说明。 如图8所示,存储卡的写保护可以通过以下步骤实现: [0064] 小号 800 :短路形成步骤,在第一端口(例如,输出端口A)之间形成短路连接 1 )和第二个端口(例如,输入端口A 2 ) 设置在手机机身上,当电池盖与机体接合(例如,附接至、连接至)时,通过电池盖上的短路连接件。 [0065] 短路连接件例如可以是金属片或其他导电片。 在本发明的一个实施例中,短路连接件为手机的通信模块(例如蓝牙模块或WLAN通信模块)的天线。 [0066] 小号 804 :短路检测步骤,通过在第二端口检测第一端口输入的测试信号,判断短路连接是否断开,从而判断电池盖是否脱离本体。 当第二端口检测不到来自第一端口的测试信号时,判断短路连接断开; 当第二端口检测到来自第一端口的测试信号时,判断短路连接没有断开,电池盖没有从手机机身上取下。 [0067] 小号 806 :写保护步骤,当短路检测步骤判断为电池盖脱离本体时,禁止(包括停止)向存储卡写入数据。 [0068] 这样可以防止拔出存储卡时数据写入错误导致存储卡损坏和应用程序无法运行,提高了存储卡数据写入的安全性,并且 有效降低存储卡的退货率。 [0069] 该方法还可以包括:S 808 ,当在短路检测步骤中确定电池盖未从机体上移除时,允许将数据写入存储卡。 [0070] 如果短路连接件为手机中通信模块的天线,则在S之前,该方法还可以包括以下步骤: 804 : [0071] 小号 802 :状态检测步骤,检测通信模块是否处于工作状态。 [0072] 例如,可以通过检测天线的信号强度来检测通信模块的工作状态: [0073] 在那种情况下,短路检测步骤S 804 如果在状态检测步骤中确定通信模块不处于工作状态,则定时或在有数据写入存储卡时执行。 [0074] 该方法还可以包括: [0075] 小号 803 :若状态检测步骤判断通信模块处于工作状态,则停止检测电池盖和/或允许数据写入存储卡。 [0076] 在本发明的一个实施例中,该方法还可以包括:步骤S 805 :在通信模块处于工作状态期间,执行短路检测步骤S 804 当通信模块的天线的信号强度低于预定阈值或天线信号强度的衰减量大于预定阈值时。 [0077] 本发明的方法并不局限于按照这里描述的时间顺序执行,可以按照其他时间顺序依次执行、并发执行或独立执行。 因此,此处描述的方法的执行顺序不构成对本发明技术范围的限制。 [0078] 上述描述和附图说明了本发明的各种不同特征。 应当理解,本领域的技术人员可以通过编写适当的计算机代码来实现上述描述和图示的步骤和过程。 [0079] 在此公开了本发明的实施例。 本领域的技术人员很容易认识到本发明在其他环境下还有其他应用。 事实上,还存在许多其他的实施例和实现方式。 所附权利要求并不旨在将本发明的范围限制为上述实施例。 [0080] 关于一个实施例描述和/或图示的特征可以相同或相似的方式用于一个或多个其他实施例,和/或与其他实施例中的特征组合或替换。 [0081] 应当理解,本发明实施例的多个部分可以通过硬件、软件、固件或其组合来实现。 在上述实施例中,多个步骤或方法可以通过存储在存储器中并由适当的指令执行系统执行的软件或固件来实现。 例如,如果通过硬件实现,例如在替代实施例中,可以通过组合以下现有技术中的任何一种或组合来实现:分立逻辑电路,具有用于实现数字信号的逻辑功能的逻辑门电路, 具有适当组合逻辑门电路、可编程门阵列(PGA)、现场可编程门阵列(FPGA)等的专用集成电路(ASIC)。 [0082] 当上述方法中的全部或部分步骤是通过程序指令相关硬件实现时,该程序可以存储在计算机可读取存储介质中,例如ROM/RAM、磁盘、光盘等。 [0083] 流程图或其他方式所描述的任何过程或方法描述或方框,都可以理解为包括一个或多个用于实现特定逻辑功能或过程步骤中可执行指令的代码的模块、段或部分,以及优选实施例的范围 还包括其他实现方式,其中功能可以不同于所示出或讨论的顺序执行,包括基于相关功能的基本同时的方式或相反的顺序,并且这是本领域技术人员应当理解的。 [0084]以上实施例对本发明的目的、技术方案及有益效果进行了进一步详细的说明。 应当理解,以上所述仅为本发明的实施例而已,并不用于限定本发明的保护范围。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.747 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN102682830A(String), CN102682830B(String), US20120231730A1(String), US8731625B2(String), WO2012123792A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.907 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN102682830A(String), CN102682830B(String), US20120231730A1(String), US8731625B2(String), WO2012123792A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.925 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US8731625B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN102682830A(String), CN102682830B(String), US20120231730A1(String), US8731625B2(String), WO2012123792A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:27.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271684(Integer), CN102682830A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271684(Integer), CN102682830B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271684(Integer), US20120231730A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.083 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271684(Integer), US8731625B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.117 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271684(Integer), WO2012123792A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.152 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US8731625B2(String), US8731625B2(String), 1400515200(Integer), 271684(Integer), 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY MOBILE COMMUNICATIONS AB(String), SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼公司(String), 索尼移动通信株式会社(String), 索尼爱立信移动通讯股份有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 7 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: SONY MOBILE COMMUNICATIONS AB(String), 索尼移动通信株式会社(String), 0(Integer), 1681976188(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.268 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.268 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.268 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186015(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.302 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 186015(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.337 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.338 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75864(Integer), 1(Integer), 186015(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.372 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY ERICSSON MOBILE COMMUNICATIONS AB(String), 索尼爱立信移动通讯股份有限公司(String), 255(String), 0(Integer), 1660818391(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.406 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.406 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.406 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186015(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.440 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.441 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 23104(Integer), 2(Integer), 186015(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.476 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.476 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.493 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.494 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.495 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75864(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.512 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.529 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.530 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 23104(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.546 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.547 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.548 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.564 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.565 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.599 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.600 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.617 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.770 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.771 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 未缴年费 | 权利转移(String), 2(Integer), 186015(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:28.806 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US10382204B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.147 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal privacy protection method and protection apparatus, and mobile terminal(String), 移动终端隐私保护方法、保护装置、移动终端(String), US10382204B2(String), A mobile terminal privacy protection method and protection apparatus, and a mobile terminal, where the method includes obtaining an application start instruction, actively obtaining a biometric feature of a user according to the application start instruction, and displaying an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature. The encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. Hence, the present disclosure can protect privacy in the mobile terminal without being easily perceived.(String), 一种移动终端隐私保护方法、保护装置及移动终端,该方法包括:获取应用启动指令,根据应用启动指令主动获取用户的生物特征,显示加密内容列表和未加密内容 如果获取的用户的生物特征与预设的生物特征匹配,则对应的应用程序列表。 应用程序的加密内容列表是根据应用程序中的加密内容生成的,应用程序的未加密内容列表是根据应用程序中的未加密内容生成的,应用程序中的加密内容是获取时未呈现的内容 用户的生物特征与预设的生物特征不匹配。 因此,本公开可以保护移动终端中的隐私而不易被察觉。(String), US15/561344(String), 1427731200(Integer), US10382204B2(String), 1565625600(Integer), 1565625600(Integer), 美国(String), 4(Integer), 10(Integer), 33(Integer), CN102467462A | CN102880560A | CN102902935A | CN103427990A | CN103581417A | CN103605459A | CN104239107A | CN104239778A | EP2713298A1 | JP1995092908A | JP2001051987A | JP2002259081A | JP2010541046A | JP2011509459A | JP2013152641A | JP2014514654A | JP2015021363A | JPWO2014077213A1 | US20070113097A1 | US20090083847A1 | US20090210722A1 | US20110072264A1 | US20120252411A1 | US20120291121A1 | US20130318625A1 | US20140085460A1 | US20140095870A1 | US20140292666A1 | US20140298268A1 | US20160042166A1 | US20160212103A1 | US4775595A(String), 15(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.183 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.183 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.184 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186016(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.329 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.330 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\dc0cf35a4ab3479c9f2f54b7cfd69178.png(String), 186016(Integer), dc0cf35a4ab3479c9f2f54b7cfd69178.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.382 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal privacy protection method and protection apparatus, and mobile terminal(String), 移动终端隐私保护方法、保护装置、移动终端(String), US10382204B2(String), A mobile terminal privacy protection method and protection apparatus, and a mobile terminal, where the method includes obtaining an application start instruction, actively obtaining a biometric feature of a user according to the application start instruction, and displaying an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature. The encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. Hence, the present disclosure can protect privacy in the mobile terminal without being easily perceived.(String), 一种移动终端隐私保护方法、保护装置及移动终端,该方法包括:获取应用启动指令,根据应用启动指令主动获取用户的生物特征,显示加密内容列表和未加密内容 如果获取的用户的生物特征与预设的生物特征匹配,则对应的应用程序列表。 应用程序的加密内容列表是根据应用程序中的加密内容生成的,应用程序的未加密内容列表是根据应用程序中的未加密内容生成的,应用程序中的加密内容是获取时未呈现的内容 用户的生物特征与预设的生物特征不匹配。 因此,本公开可以保护移动终端中的隐私而不易被察觉。(String), US15/561344(String), 1427731200(Integer), US10382204B2(String), 1565625600(Integer), 1565625600(Integer), 美国(String), 3(Integer), 4(Integer), 10(Integer), 33(Integer), CN102467462A | CN102880560A | CN102902935A | CN103427990A | CN103581417A | CN103605459A | CN104239107A | CN104239778A | EP2713298A1 | JP1995092908A | JP2001051987A | JP2002259081A | JP2010541046A | JP2011509459A | JP2013152641A | JP2014514654A | JP2015021363A | JPWO2014077213A1 | US20070113097A1 | US20090083847A1 | US20090210722A1 | US20110072264A1 | US20120252411A1 | US20120291121A1 | US20130318625A1 | US20140085460A1 | US20140095870A1 | US20140292666A1 | US20140298268A1 | US20160042166A1 | US20160212103A1 | US4775595A(String), \20230420\dc0cf35a4ab3479c9f2f54b7cfd69178.png(String), 15(Integer), 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.419 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.452 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 1. A mobile terminal privacy protection method; comprising:obtaining an application start instruction;actively obtaining a biometric feature of a user according to the application start instruction; anddisplaying an encrypted content list and an unencrypted content list of an application when the obtained biometric feature of the user matches a preset biometric feature,wherein the encrypted content list of the application is generated according to encrypted content in the application,wherein the unencrypted content list of the application is generated according to unencrypted content in the application, andwherein the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature,wherein before obtaining the application start instruction, the method further comprises:obtaining an unlock instruction entered by the user on a lock screen interface;actively obtaining the biometric feature of the user according to the unlock instruction;displaying an encrypted application icon and an unencrypted application icon when the obtained biometric feature of the user matches the preset biometric feature; anddisplaying the unencrypted application icon when the biometric feature of the user is not obtained and when the obtained biometric feature of the user does not match the preset biometric feature.(String), 1.根据权利要求10所述的移动终端,其中输入设备还被配置为:主动获取用户的面部特征;输入设备还用于主动获取用户的眼睛虹膜特征;或者输入设备还用于主动获取用户的指纹。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 2. The method according to claim 1, wherein after actively obtaining the biometric feature of the user, the method further comprises:displaying the unencrypted content list of the application when the biometric feature of the user is not obtained; anddisplaying the unencrypted content list of the application when the obtained biometric feature of the user does not match the preset biometric feature.(String), 12.根据权利要求10所述的移动终端,其中输入装置还用于通过移动终端的触摸屏主动获取用户在操作未加密内容列表时输入的指纹,输出装置还用于显示加密内容列表和未加密内容列表当主动获取的指纹与预设的生物特征相​​匹配时,应用程序的应用程序。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.454 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 3. The method according to claim 1, wherein actively obtaining the biometric feature of the user comprises:actively obtaining a facial feature of the user;actively obtaining an eye iris feature of the user; oractively obtaining a fingerprint of the user.(String), 13.根据权利要求10所述的移动终端,其中处理器还用于获取用户输入的打开加密内容列表中的第一条目的第一指令,输出设备还用于根据第一指令呈现第一条目对应的内容,其中,输入装置还用于根据第一指令获取用户输入的生物特征,其中处理器还用于当用户输入的生物特征与预设生物特征匹配时将第一条目设置为未加密状态特征。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 4. The method according to claim 2, wherein after displaying the unencrypted content list of the application, the method further comprises:actively obtaining, using a touchscreen of a mobile terminal, a fingerprint entered by the user when operating the unencrypted content list; anddisplaying the encrypted content list and the unencrypted content list of the application when the actively obtained fingerprint matches the preset biometric feature.(String), 14.根据权利要求10所述的移动终端,其中处理器还用于获取用户输入的第二指令打开未加密内容列表中的第二条目,其中输出设备还用于根据第二指令呈现第二条目对应的内容,其中,输入装置还用于根据第二指令获取用户输入的生物特征,其中处理器还用于当用户输入的生物特征与预设生物特征匹配时将第二条目设置为加密状态特征。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 5. The method according to claim 2, wherein after displaying the encrypted content list and the unencrypted content list of the application, the method further comprises:obtaining a first instruction entered by the user to open a first entry in the encrypted content list;presenting, according to the first instruction, content corresponding to the first entry;obtaining, according to the first instruction, a biometric feature entered by the user; andsetting the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 15.根据权利要求10所述的移动终端,其中输入设备还被配置为:获取移动终端所在的地理位置和环境信息;和当移动终端所在的地理位置信息与预设的地理位置信息匹配时,或当环境信息与预设的环境信息匹配时,根据应用启动指令主动获取用户的生物特征。(String), 1(Integer), 4(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 6. The method according to claim 2, wherein after displaying the encrypted content list and the unencrypted content list of the application, the method further comprises:obtaining a second instruction entered by the user to open a second entry in the unencrypted content list;presenting, according to the second instruction, content corresponding to the second entry;obtaining, according to the second instruction, a biometric feature entered by the user; andsetting the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 1(Integer), 5(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 7. The method according to claim 1, wherein actively obtaining the biometric feature of the user further comprises:obtaining information about a geographic location and an environment in which a mobile terminal is located; andwhen the information about the geographic location in which the mobile terminal is located matches preset geographic location information or when the environment information matches preset environment information.(String), 1(Integer), 6(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 8. A mobile terminal privacy protection method, comprising:obtaining an unlock instruction entered by a user on a lock screen interface;actively obtaining a biometric feature of the user according to the unlock instruction; andpresenting an unlocked first interface when the obtained biometric feature of the user matches a preset biometric feature;presenting a second unlocked interface when the obtained biometric feature of the user does not match the preset biometric feature,wherein an interface element of the unlocked second interface comprises an unencrypted application icon,wherein interface elements of the unlocked first interface comprise an encrypted application icon and the unencrypted application icon, andwherein the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature.(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 9. The mobile terminal privacy protection method according to claim 8, wherein actively obtaining the biometric feature of the user further comprises:obtaining information about a geographic location and an environment in which a mobile terminal is located; andactively obtaining the biometric feature of the user according to an application start instruction when the information about the geographic location in which the mobile terminal is located matches preset geographic location information or when the environment information matches preset environment information.(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 10. A mobile terminal, comprising:a processor configured to obtain an application start instruction;an input device coupled to the processor and configured to actively obtain a biometric feature of a user according to the application start instruction; andan output device coupled to the processor and the input device and configured to display an encrypted content list and an unencrypted content list of an application when the obtained biometric feature of the user matches a preset biometric feature,wherein the encrypted content list of the application is generated according to encrypted content in the application,wherein the unencrypted content list of the application is generated according to unencrypted content in the application, andwherein the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature,wherein the processor is further configured toobtain an unlock instruction entered by the user on a lock screen interface;actively obtain the biometric feature of the user according to the unlock instruction;display an encrypted application icon and an unencrypted application icon when the obtained biometric feature of the user matches the preset biometric feature; anddisplay the unencrypted application icon when the biometric feature of the user is not obtained and when the obtained biometric feature of the user does not match the preset biometric feature.(String), 0(Integer), 9(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 11. The mobile terminal according to claim 10, wherein the input device is further configured to:actively obtain a facial feature of the user;the input device is further configured to actively obtain an eye iris feature of the user; orthe input device is further configured to actively obtain a fingerprint of the user.(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 12. The mobile terminal according to claim 10, wherein the input device is further configured to actively obtain, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and wherein the output device is further configured to display the encrypted content list and the unencrypted content list of the application when the actively obtained fingerprint matches the preset biometric feature.(String), 1(Integer), 11(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 13. The mobile terminal according to claim 10, wherein the processor is further configured to obtain a first instruction entered by the user to open a first entry in the encrypted content list, wherein the output device is further configured to present, according to the first instruction, content corresponding to the first entry, wherein the input device is further configured to obtain, according to the first instruction, a biometric feature entered by the user, and wherein the processor is further configured to set the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 1(Integer), 12(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 14. The mobile terminal according to claim 10, wherein the processor is further configured to obtain a second instruction entered by the user to open a second entry in the unencrypted content list, wherein the output device is further configured to present, according to the second instruction, content corresponding to the second entry, wherein the input device is further configured to obtain, according to the second instruction, a biometric feature entered by the user, and wherein the processor is further configured to set the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature.(String), 1(Integer), 13(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.456 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186016(Integer), 15. The mobile terminal according to claim 10, wherein the input device is further configured to:obtain information about a geographic location and an environment in which the mobile terminal is located; andactively obtain the biometric feature of the user according to the application start instruction when the information about the geographic location in which the mobile terminal is located matches preset geographic location information or when the environment information matches preset environment information.(String), 1(Integer), 14(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.779 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.780 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186016(Integer), CROSS-REFERENCE TO RELATED APPLICATION [0001]This application is a U.S. National Stage of International Patent Application No. PCT/CN2015/075517 filed on Mar. 31, 2015, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD [0002]The present disclosure relates to the terminal field, and in particular, to a mobile terminal privacy protection method and protection apparatus, and a mobile terminal. BACKGROUND [0003]As technologies and interpersonal communication develop, a mobile terminal has become an important means for people's communication. The mobile terminal is generally a personal article, but because of factors such as an interpersonal relationship, hard-to-refuse, or politeness, people cannot totally prevent the mobile terminal from being used by other people. There is lots of people's privacy in the mobile terminal, such as a short message service message, a contact, a call log, a photo, and an instant messaging message. People expect that the privacy can be protected when the mobile terminal is used by the other people. To resolve a mobile terminal privacy protection problem, a privacy protection mode is set in most mobile terminals to ensure that a user other than an owner is hard to obtain privacy in the mobile terminal in the privacy protection mode. [0004]In other approaches, the privacy protection mode may be implemented in multiple manners. One method is returning, when the mobile terminal is in the privacy protection mode, virtual data when an application in the terminal is opened. For example, in the privacy protection mode, an opened album may display a blank or only display a non-private photo set by a user. A defect of the method is that setting of the returned virtual data is relatively complex and tedious, and if there are many applications, the setting is more tedious. In addition, if the virtual data setting is not realistic enough, the method is easily perceived by another user, which causes unnecessary embarrassment. [0005]Another method is entering different modes by setting different authentication manners. For example, a privacy mode and a normal operation mode correspond to different passwords, patterns, personal identification number (PIN) codes, and fingerprints. A setting of the method is relatively convenient, but in the method, a user is generally prompted to enter a password, draw a pattern, or scan a fingerprint, and therefore a used mode is easily perceived by the user. For example, the mobile terminal is set to enter different modes according to different passwords. Generally, the normal mode is entered when a correct password is entered, and the privacy protection mode is entered when an incorrect password is entered. In this case, the mobile terminal prompts the user to enter a password, and a lock screen can be unlocked by the user entering any incorrect password. The user knows that the entered password is an incorrect password but the lock screen is unlocked, and therefore the user perceives that the privacy protection mode is entered. Another defect of the method is that authentication information needs to be entered only when the lock screen is to be unlocked, and after the lock screen is unlocked, privacy protection cannot be implemented when the user operates an application. [0006]It can be seen that, in the other approaches, there is no mobile terminal privacy protection method that is convenient and efficient and further can avoid being easily perceived by a user. SUMMARY [0007]In view of this, an objective of embodiments of the present disclosure is to provide a mobile terminal privacy protection method and protection apparatus, and a mobile terminal in order to resolve problems that a user easily perceives that privacy in the mobile terminal is protected and privacy is not protected when an application is used. [0008]To resolve the foregoing technical problems, the embodiments of the present disclosure disclose the following technical solutions. [0009]According to a first aspect, a mobile terminal privacy protection method is provided, and the method includes obtaining an application start instruction, actively obtaining a biometric feature of a user according to the application start instruction, and displaying an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature, where the encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0010]With reference to the first aspect, in a first possible implementation manner of the first aspect, after the actively obtaining a biometric feature of a user, the method further includes displaying the unencrypted content list of the application if the biometric feature of the user is not obtained, or displaying the unencrypted content list of the application if the obtained biometric feature of the user does not match the preset biometric feature. [0011]With reference to the first aspect and the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, actively obtaining a biometric feature of a user includes actively obtaining a facial feature of the user, actively obtaining an eye iris feature of the user, or actively obtaining a fingerprint of the user. [0012]With reference to the first possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, after displaying the unencrypted content list of the application, the method further includes actively obtaining, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and displaying the encrypted content list and the unencrypted content list of the application if the actively obtained fingerprint matches the preset biometric feature. [0013]With reference to the first possible implementation manner of the first aspect and the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, after displaying the encrypted content list and the unencrypted content list of the application, the method further includes obtaining a first instruction that is entered by the user to open a first entry in the encrypted content list, presenting, according to the first instruction, content corresponding to the first entry, obtaining, according to the first instruction, a biometric feature entered by the user, and setting the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature. [0014]With reference to the first possible implementation manner of the first aspect and the third possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, after displaying the encrypted content list and the unencrypted content list of the application, the method further includes obtaining a second instruction that is entered by the user to open a second entry in the unencrypted content list, presenting, according to the second instruction, content corresponding to the second entry, obtaining, according to the second instruction, a biometric feature entered by the user, and setting the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature. [0015]With reference to any one of the first aspect to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, before obtaining an application start instruction, the method further includes obtaining an unlock instruction entered by the user on a lock screen interface, actively obtaining the biometric feature of the user according to the unlock instruction, and displaying an encrypted application icon and an unencrypted application icon if the obtained biometric feature of the user matches the preset biometric feature, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0016]With reference to the first aspect, in a seventh possible implementation manner of the first aspect, after actively obtaining the biometric feature of the user according to the unlock instruction, the method further includes displaying the unencrypted application icon if the biometric feature of the user is not obtained, or displaying the unencrypted application icon if the obtained biometric feature of the user does not match the preset biometric feature. [0017]With reference to any one of the first aspect to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, actively obtaining a biometric feature of a user according to the application start instruction further includes obtaining information about a geographic location and an environment in which the mobile terminal is located, and actively obtaining the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0018]According to a second aspect, a mobile terminal privacy protection method is provided, and the method includes obtaining an unlock instruction entered by a user on a lock screen interface, actively obtaining a biometric feature of the user according to the unlock instruction, and presenting an unlocked first interface if the obtained biometric feature of the user matches a preset biometric feature, where interface elements of the first interface include an encrypted application icon and an unencrypted application icon, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0019]With reference to the second aspect, in a first possible implementation manner of the second aspect, an unlocked second interface is presented if the obtained biometric feature of the user does not match the preset biometric feature. An interface element of the second interface includes the unencrypted application icon. [0020]With reference to the second aspect and the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, actively obtaining a biometric feature of the user according to the unlock instruction further includes obtaining information about a geographic location and an environment in which the mobile terminal is located, and actively obtaining the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0021]According to a third aspect, a mobile terminal privacy protection apparatus is provided, and the apparatus includes an instruction obtaining unit configured to obtain an application start instruction, a biometric feature obtaining unit configured to actively obtain a biometric feature of a user according to the application start instruction, and a display unit configured to display an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature, where the encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0022]With reference to the third aspect, in a first possible implementation manner of the third aspect, the display unit is further configured to display the unencrypted content list of the application if the biometric feature of the user is not obtained, or the display unit is further configured to display the unencrypted content list of the application if the obtained biometric feature of the user does not match the preset biometric feature. [0023]With reference to the third aspect and the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the biometric feature obtaining unit includes a photography subunit configured to actively obtain a facial feature of the user, the biometric feature obtaining unit includes a photography subunit configured to actively obtain an eye iris feature of the user, or the biometric feature obtaining unit includes a fingerprint obtaining subunit configured to actively obtain a fingerprint of the user. [0024]With reference to the first possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the fingerprint obtaining subunit is further configured to actively obtain, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and the display unit is further configured to display the encrypted content list and the unencrypted content list of the application if the actively obtained fingerprint matches the preset biometric feature. [0025]With reference to the first possible implementation manner of the third aspect and the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the instruction obtaining unit is further configured to obtain a first instruction that is entered by the user to open a first entry in the encrypted content list. The display unit is further configured to present, according to the first instruction, content corresponding to the first entry. The biometric feature obtaining unit is further configured to obtain, according to the first instruction, a biometric feature entered by the user, and the apparatus further includes a setting unit configured to set the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature. [0026]With reference to the first possible implementation manner of the third aspect and the third possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the instruction obtaining unit is further configured to obtain a second instruction that is entered by the user to open a second entry in the unencrypted content list. The display unit is further configured to present, according to the second instruction, content corresponding to the second entry. The biometric feature obtaining unit is further configured to obtain, according to the second instruction, a biometric feature entered by the user, and the setting unit is further configured to set the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature. [0027]With reference to any one of the third aspect to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the instruction obtaining unit is further configured to obtain an unlock instruction entered by the user on a lock screen interface. The biometric feature obtaining unit is further configured to actively obtain the biometric feature of the user according to the unlock instruction, and the display unit is further configured to display an encrypted application icon and an unencrypted application icon if the obtained biometric feature of the user matches the preset biometric feature, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0028]With reference to the third aspect, in a seventh possible implementation manner of the third aspect, the display unit is further configured to display the unencrypted application icon if the biometric feature of the user is not obtained, or the display unit is further configured to display the unencrypted application icon if the obtained biometric feature of the user does not match the preset biometric feature. [0029]With reference to any one of the third aspect to the seventh possible implementation manner of the third aspect, in an eighth possible implementation manner of the third aspect, the apparatus further includes a geographic location and environment information obtaining unit configured to obtain information about a geographic location and an environment in which the mobile terminal is located, where the biometric feature obtaining unit is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0030]According to a fourth aspect, a mobile terminal privacy protection apparatus is provided, and the apparatus includes an instruction obtaining unit configured to obtain an unlock instruction entered by a user on a lock screen interface, a biometric feature obtaining unit configured to actively obtain a biometric feature of the user according to the unlock instruction, and a display unit configured to present an unlocked first interface if the obtained biometric feature of the user matches a preset biometric feature, where interface elements of the first interface include an encrypted application icon and an unencrypted application icon, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0031]With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the display unit is further configured to present an unlocked second interface if the obtained biometric feature of the user does not match the preset biometric feature. An interface element of the second interface includes the unencrypted application icon. [0032]With reference to the fourth aspect and the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the apparatus further includes a geographic location and environment information obtaining unit configured to obtain information about a geographic location and an environment in which the mobile terminal is located, where the biometric feature obtaining unit is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0033]According to a fifth aspect, a mobile terminal is provided, and the mobile terminal includes a processor configured to obtain an application start instruction, an input device configured to actively obtain a biometric feature of a user according to the application start instruction, and an output device configured to display an encrypted content list and an unencrypted content list of a corresponding application if the obtained biometric feature of the user matches a preset biometric feature, where the encrypted content list of the application is generated according to encrypted content in the application, the unencrypted content list of the application is generated according to unencrypted content in the application, and the encrypted content in the application is content that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0034]With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the output device is further configured to display the unencrypted content list of the application if the biometric feature of the user is not obtained, or the output device is further configured to display the unencrypted content list of the application if the obtained biometric feature of the user does not match the preset biometric feature. [0035]With reference to the fifth aspect and the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the input device is further configured to actively obtain a facial feature of the user, the input device is further configured to actively obtain an eye iris feature of the user, or the input device is further configured to actively obtain a fingerprint of the user. [0036]With reference to the first possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the input device is further configured to actively obtain, using a touchscreen of the mobile terminal, a fingerprint entered by the user when operating the unencrypted content list, and the output device is further configured to display the encrypted content list and the unencrypted content list of the application if the actively obtained fingerprint matches the preset biometric feature. [0037]With reference to the first possible implementation manner of the fifth aspect and the third possible implementation manner of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the processor is further configured to obtain a first instruction that is entered by the user to open a first entry in the encrypted content list. The output device is further configured to present, according to the first instruction, content corresponding to the first entry. The input device is further configured to obtain, according to the first instruction, a biometric feature entered by the user, and the processor is further configured to set the first entry to an unencrypted state when the biometric feature entered by the user matches the preset biometric feature. [0038]With reference to the first possible implementation manner of the fifth aspect and the third possible implementation manner of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, the processor is further configured to obtain a second instruction that is entered by the user to open a second entry in the unencrypted content list. The output device is further configured to present, according to the second instruction, content corresponding to the second entry. The input device is further configured to obtain, according to the second instruction, a biometric feature entered by the user, and the processor is further configured to set the second entry to an encrypted state when the biometric feature entered by the user matches the preset biometric feature. [0039]With reference to any one of the fifth aspect to the fifth possible implementation manner of the fifth aspect, in a sixth possible implementation manner of the fifth aspect, the processor is further configured to obtain an unlock instruction entered by the user on a lock screen interface. The input device is further configured to actively obtain the biometric feature of the user according to the unlock instruction, and the output device is further configured to display an encrypted application icon and an unencrypted application icon if the obtained biometric feature of the user matches the preset biometric feature, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0040]With reference to the fifth aspect, in a seventh possible implementation manner of the fifth aspect, the output device is further configured to display the unencrypted application icon if the biometric feature of the user is not obtained, or the output device is further configured to display the unencrypted application icon if the obtained biometric feature of the user does not match the preset biometric feature. [0041]With reference to any one of the fifth aspect to the seventh possible implementation manner of the fifth aspect, in an eighth possible implementation manner of the fifth aspect, the input device is further configured to obtain information about a geographic location and an environment in which the mobile terminal is located, and the input device is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0042]According to a sixth aspect, a mobile terminal is provided, and the mobile terminal includes a processor configured to obtain an unlock instruction entered by a user on a lock screen interface, an input device configured to actively obtain a biometric feature of the user according to the unlock instruction, and an output device configured to present an unlocked first interface if the obtained biometric feature of the user matches a preset biometric feature, where interface elements of the first interface include an encrypted application icon and an unencrypted application icon, where the encrypted application icon is an application icon that is not presented when the obtained biometric feature of the user does not match the preset biometric feature. [0043]With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the output device is further configured to present an unlocked second interface if the obtained biometric feature of the user does not match the preset biometric feature. An interface element of the second interface includes the unencrypted application icon. [0044]With reference to the sixth aspect and the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the input device is further configured to obtain information about a geographic location and an environment in which the mobile terminal is located, and the input device is further configured to actively obtain the biometric feature of the user according to the application start instruction if the information about the geographic location in which the mobile terminal is located matches preset geographic location information and/or if the environment information matches preset environment information. [0045]The embodiments of the present disclosure provide a mobile terminal privacy protection method. A biometric feature of a user is actively obtained after an application start instruction is obtained, and encrypted content and unencrypted content are displayed if the obtained biometric feature matches a preset biometric feature in order to avoid leakage of user privacy in a mobile terminal and protect the user privacy. In addition, a method for actively obtaining the biometric feature cannot be easily perceived by the user. [0046]It should be understood that, the above general descriptions and the following detailed descriptions are merely examples and cannot limit the protection scope of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS [0047]To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. The accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. [0048]FIG. 1 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure, [0049]FIG. 2 shows a schematic diagram of displaying a content list according to an embodiment of the present disclosure, [0050]FIG. 3 shows a schematic diagram of displaying an unencrypted content list according to an embodiment of the present disclosure, [0051]FIG. 4 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure, [0052]FIG. 5 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure, [0053]FIG. 6 shows a schematic diagram of displaying an encrypted content list and an unencrypted content list according to an embodiment of the present disclosure, [0054]FIG. 7 shows a schematic structural diagram of a mobile terminal privacy protection apparatus according to an embodiment of the present disclosure, [0055]FIG. 8 shows a schematic structural diagram of a mobile terminal privacy protection apparatus according to an embodiment of the present disclosure, [0056]FIG. 9 shows a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure, and [0057]FIG. 10 shows a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure. [0058]The specific embodiments of the present disclosure have been shown using the foregoing accompanying drawings, and more detailed descriptions are provided in the following. These accompanying drawings and text descriptions are not intended to limit a conception scope of the present disclosure in any manner, but to describe a concept of the present disclosure for a person skilled in the art with reference to the specific embodiments. DESCRIPTION OF EMBODIMENTS [0059]The following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure. [0060]To completely understand the present disclosure, the following detailed description mentions many specific details. However, a person skilled in the art should understand that the present disclosure may be implemented without these specific details. In other embodiments, detailed descriptions of a well known method, process, component, and circuit are omitted such that the embodiments are described without being unnecessarily blurred. [0061]The embodiments of the present disclosure provide a mobile terminal privacy protection method and protection apparatus, and a mobile terminal, to protect user privacy in the mobile terminal without being easily perceived by another user. [0062]FIG. 1 shows a flowchart of a mobile terminal privacy protection method according to an embodiment of the present disclosure. As shown in FIG. 1, the method includes the following steps. [0063]Step 101: Obtain an application start instruction. [0064]An application unit in a mobile terminal may also be referred to as an application, such as an album, a short message service, and a call log. To start the application, a user may touch an application icon, and after the application icon is touched, the application start instruction is generated. [0065]Step 102: Actively obtain a biometric feature of a user according to the application start instruction. [0066]Further, in an implementation manner of actively obtaining the biometric feature, the user does not need to be prompted, the biometric feature of the user can be obtained without permission of the user, and the biometric feature of the user can be obtained when an input instruction for the biometric feature of the user is not obtained. The manner of active obtaining is relatively covert and is not easily perceived by the user. [0067]Step 10(String), 相关申请的交叉引用 [0001] 本申请是于2015年3月31日提交的美国国家阶段国际专利申请PCT/CN2015/075517,其全部内容通过引用并入本文。 技术领域 [0002] 本发明涉及终端领域,尤其涉及一种移动终端隐私保护方法、保护装置及移动终端。 背景 [0003] 随着科技和人际交往的发展,移动终端已经成为人们交流的重要手段。 移动终端一般是个人物品,但由于人际关系、难以拒绝或礼貌等因素,人们并不能完全阻止移动终端被他人使用。 移动终端中有很多人的隐私,比如短信业务消息、联系人、通话记录、照片、即时通讯消息等。 人们期望移动终端在被他人使用时能够保护隐私。 为了解决移动终端的隐私保护问题,大多数移动终端都设置了隐私保护模式,以保证在隐私保护模式下,除了所有者之外的其他用户很难获得移动终端中的隐私。 [0004] 在其他方式中,隐私保护方式可以有多种实现方式。 一种方法是,当移动终端处于隐私保护模式时,返回终端中打开应用程序时的虚拟数据。 例如,在隐私保护模式下,打开的相册可以显示空白或者只显示用户设置的非隐私照片。 该方法的一个缺陷是返回的虚拟数据的设置比较复杂繁琐,如果应用较多,则设置比较繁琐。 此外,如果虚拟数据设置不够逼真,则该方法容易被其他用户察觉,造成不必要的尴尬。 [0005] 另一种方法是通过设置不同的认证方式进入不同的模式。 例如,隐私模式和正常操作模式对应不同的密码、图案、个人识别码(PIN)码和指纹。 该方法的设置较为方便,但该方法中一般会提示用户输入密码、绘制图案或扫描指纹,因此所使用的方式容易被用户感知。 例如,设置移动终端根据不同的密码进入不同的模式。 一般情况下,密码输入正确时进入正常模式,密码输入错误时进入隐私保护模式。 此时,移动终端提示用户输入密码,用户输入错误的密码即可解锁锁屏。 用户知道输入的密码是错误的,但是锁屏被解锁,用户感知到进入了隐私保护模式。 该方法的另一个缺陷在于,只有在锁屏解锁时才需要输入认证信息,锁屏解锁后,无法实现用户操作应用程序时的隐私保护。 [0006] 可见,在其他方式中,还没有一种既方便、高效又能避免被用户轻易察觉的移动终端隐私保护方法。 概括 [0007] 有鉴于此,本发明实施例的目的在于提供一种移动终端隐私保护方法、保护装置及移动终端,以解决移动终端中用户容易感知到隐私受到保护和隐私保护的问题。 使用应用程序时不受保护。 [0008] 为解决上述技术问题,本发明实施例公开了以下技术方案。 [0009]第一方面,提供了一种移动终端隐私保护方法,该方法包括获取应用启动指令、根据应用启动指令主动获取用户的生物特征、显示加密内容列表和未加密内容 如果获取的用户生物特征与预设生物特征相​​匹配,则对应应用的列表,其中,应用的加密内容列表根据应用中的加密内容生成,应用的未加密内容列表根据未加密的内容生成 在应用程序中,应用程序中的加密内容为当获取的用户生物特征与预设生物特征不匹配时不呈现的内容。 [0010] 结合第一方面,在第一方面的第一种可能的实现方式中,所述主动获取用户的生物特征之后,所述方法还包括:若用户的生物特征未被获取,则显示应用的未加密内容列表。 如果获取的用户生物特征与预设生物特征不匹配,则显示应用的未加密内容列表。 [0011] 结合第一方面及第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,主动获取用户的生物特征包括主动获取用户的面部特征、主动获取眼睛 用户的虹膜特征,或者主动获取用户的指纹。 [0012] 结合第一方面的第一种可能的实现方式,在第一方面的第三种可能的实现方式中,所述显示应用程序的未加密内容列表后,还包括:通过移动终端的触摸屏主动获取: 用户在操作未加密内容列表时输入的指纹,如果主动获取的指纹与预设的生物特征匹配,则显示应用的加密内容列表和未加密内容列表。 [0013] 结合第一方面的第一种可能的实现方式和第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中,在显示应用程序的加密内容列表和未加密内容列表之后, 该方法还包括获取用户输入的打开加密内容列表中的第一条目的第一指令, 根据第一指令呈现第一条目对应的内容, 根据第一指令获取生物特征 当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态。 [0014] 结合第一方面的第一种可能的实现方式和第一方面的第三种可能的实现方式,在第一方面的第五种可能的实现方式中,在显示应用程序的加密内容列表和未加密内容列表之后, 该方法还包括获取用户输入的打开未加密内容列表中第二条目的第二指令, 根据第二指令呈现第二条目对应的内容, 根据第二指令获取生物特征 当用户输入的生物特征与预设生物特征匹配时,将第二条目设置为加密状态。 [0015]结合第一方面至第一方面的第五种可能的实现方式中的任一项,在第一方面的第六种可能的实现方式中,在获取应用启动指令之前,所述方法还包括:获取用户输入的解锁指令 在锁屏界面,根据解锁指令主动获取用户的生物特征,如果获取的用户生物特征与预设生物特征匹配,则显示加密应用图标和未加密应用图标,其中加密应用图标 是当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0016] 结合第一方面,在第一方面的第七种可能的实现方式中,所述方法在根据解锁指令主动获取用户的生物特征后,还包括:若用户的生物特征为非加密状态,则显示未加密的应用程序图标。 如果获取的用户生物特征与预设生物特征不匹配,则显示未加密的应用程序图标。 [0017] 结合第一方面至第一方面的第七种可能的实现方式中的任一项,在第一方面的第八种可能的实现方式中,根据所述应用启动指令主动获取用户的生物特征,还包括:获取有关信息 移动终端所处的地理位置和环境,如果移动终端所处的地理位置信息与预设的地理位置信息匹配,则根据应用启动指令主动获取用户的生物特征和/ 或者环境信息是否与预设环境信息匹配。 [0018] 第二方面,提供了一种移动终端隐私保护方法,该方法包括获取用户在锁屏界面输入的解锁指令,根据解锁指令主动获取用户的生物特征,并呈现 若获取的用户生物特征与预设生物特征相​​匹配,则解锁第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标,加密应用图标为未加密应用图标。 获取的用户生物特征与预设生物特征不匹配。 [0019] 结合第二方面,在第二方面的第一种可能的实现方式中,若获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0020] 结合第二方面及第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,根据解锁指令主动获取用户的生物特征,还包括:获取地理位置信息; 移动终端所处的环境,如果移动终端所处的地理位置信息与预设的地理位置信息相匹配和/或环境是否匹配,则根据应用启动指令主动获取用户的生物特征 信息匹配预设的环境信息。 [0021]第三方面,提供了一种移动终端隐私保护装置,该装置包括:指令获取单元,用于获取应用启动指令;生物特征获取单元,用于根据应用主动获取用户的生物特征 启动指令,显示单元,用于当获取的用户生物特征与预设生物特征匹配时,显示对应应用的加密内容列表和未加密内容列表,应用的加密内容列表是根据加密生成的 应用中的内容,根据应用中的未加密内容生成应用的未加密内容列表,应用中的加密内容为当获取的用户生物特征与预设生物特征不匹配时不呈现的内容 . [0022] 结合第三方面,在第三方面的第一种可能的实现方式中,所述显示单元,还用于若未获取到所述用户的生物特征,则显示所述应用程序的未加密内容列表,或者所述显示单元进一步被检测到。 用于当获取的用户生物特征与预设生物特征不匹配时,显示应用的未加密内容列表。 [0023] 结合第三方面及第三方面的第一种可能的实现方式,在第三方面的第二种可能的实现方式中,所述生物特征获取单元包括:摄像子单元,用于主动获取用户的面部特征,所述生物特征 特征获取单元包括摄像子单元,用于主动获取用户的眼睛虹膜特征,或者生物特征获取单元包括指纹获取子单元,用于主动获取用户的指纹。 [0024] 结合第三方面的第一种可能的实现方式,在第三方面的第三种可能的实现方式中,所述指纹获取子单元,还用于:通过所述移动终端的触摸屏,主动获取用户输入的指纹。 对未加密内容列表进行操作, 显示单元还用于当主动获取的指纹与预设生物特征匹配时,显示应用程序的加密内容列表和未加密内容列表。 [0025] 结合第三方面的第一种可能的实现方式和第三方面的第三种可能的实现方式,在第三方面的第四种可能的实现方式中,所述指令获取单元,还用于获取由输入的第一指令。 用户打开加密内容列表中的第一个条目。 显示单元还用于根据第一指令呈现第一条目对应的内容。 所述生物特征获取单元,还用于根据所述第一指令获取用户输入的生物特征,所述装置还包括设置单元,用于在用户输入生物特征时,将第一条目设置为未加密状态。 用户匹配预设的生物特征。 [0026] 结合第三方面的第一种可能的实现方式和第三方面的第三种可能的实现方式,在第三方面的第五种可能的实现方式中,所述指令获取单元,还用于获取由输入的第二指令。 用户打开未加密内容列表中的第二个条目。 显示单元还用于根据第二指令呈现第二条目对应的内容。 生物特征获取单元还用于根据第二指令获取用户输入的生物特征,设置单元还用于当用户输入的生物特征匹配时将第二条目设置为加密状态 预设的生物特征。 [0027]结合第三方面至第三方面的第五种可能的实现方式中的任一项,在第三方面的第六种可能的实现方式中,所述指令获取单元还用于获取用户在锁上输入的开锁指令 屏幕界面。 生物特征获取单元还用于根据解锁指令主动获取用户的生物特征,显示单元还用于当获取的用户生物特征匹配时显示加密应用图标和未加密应用图标。 预设生物特征,其中加密应用图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0028] 结合第三方面,在第三方面的第七种可能的实现方式中,所述显示单元还用于若未获取到所述用户的生物特征,则显示未加密的应用程序图标,或者所述显示单元还用于显示 如果获取的用户生物特征与预设生物特征不匹配,则未加密的应用程序图标。 [0029] 结合第三方面至第三方面的第七种可能的实现方式中的任一项,在第三方面的第八种可能的实现方式中,所述装置还包括: 地理位置和环境信息获取单元,用于获取地理信息 所述移动终端所处的地理位置和环境, 所述生物特征获取单元还用于如果所述移动终端所处的地理位置信息,则根据所述应用启动指令主动获取用户的生物特征 匹配预设的地理位置信息和/或环境信息是否匹配预设的环境信息。 [0030] 第四方面,提供一种移动终端隐私保护装置,该装置包括:指令获取单元,用于获取用户在锁屏界面输入的解锁指令;生物特征获取单元,用于主动获取生物特征信息。 显示单元根据解锁指令显示用户的特征,显示单元用于在获取的用户的生物特征与预设的生物特征匹配时呈现解锁的第一界面,第一界面的界面元素包括加密的应用图标和未加密的应用图标。 应用程序图标,其中加密应用程序图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0031] 结合第四方面,在第四方面的第一种可能的实现方式中,所述显示单元还用于在获取的用户生物特征与预设生物特征不匹配时,呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0032] 结合第四方面及第四方面的第一种可能的实现方式,在第四方面的第二种可能的实现方式中,所述装置还包括:地理位置和环境信息获取单元,用于获取地理位置和环境信息。 所述移动终端所处的环境,所述生物特征获取单元还用于当所述移动终端所处的地理位置信息与预设地理信息匹配时,根据所述应用启动指令主动获取用户的生物特征 位置信息和/或环境信息是否与预设环境信息匹配。 [0033]第五方面,提供了一种移动终端,该移动终端包括:处理器,用于获取应用启动指令;输入装置,用于根据应用启动指令主动获取用户的生物特征;输出端 装置,用于当获取的用户生物特征与预设生物特征匹配时,显示对应应用程序的加密内容列表和未加密内容列表,其中,应用程序的加密内容列表是根据应用程序中的加密内容生成的, 根据应用程序中的未加密内容生成应用程序的未加密内容列表,应用程序中的加密内容为当获取的用户生物特征与预设生物特征不匹配时不呈现的内容。 [0034] 结合第五方面,在第五方面的第一种可能的实现方式中,所述输出设备还用于若未获取到所述用户的生物特征,则显示所述应用程序的未加密内容列表,或者所述输出设备进一步被检测到。 用于当获取的用户生物特征与预设生物特征不匹配时,显示应用的未加密内容列表。 [0035] 结合第五方面及第五方面的第一种可能的实现方式,在第五方面的第二种可能的实现方式中,所述输入设备,还用于主动获取所述用户的面部特征,所述输入设备还用于 主动获取用户的虹膜特征,或者输入设备还用于主动获取用户的指纹。 [0036] 结合第五方面的第一种可能的实现方式,在第五方面的第三种可能的实现方式中,所述输入设备还用于通过所述移动终端的触摸屏主动获取用户在操作时输入的指纹。 未加密内容列表, 输出装置还用于当主动获取的指纹与预设生物特征匹配时, 显示应用程序的加密内容列表和未加密内容列表。 [0037] 结合第五方面的第一种可能的实现方式和第五方面的第三种可能的实现方式,在第五方面的第四种可能的实现方式中,所述处理器还用于获取用户输入的第一指令 打开加密内容列表中的第一个条目。 输出设备还用于根据第一指令呈现第一条目对应的内容。 输入设备还用于根据第一指令获取用户输入的生物特征,处理器还用于当用户输入的生物特征与预设生物特征匹配时将第一条目设置为未加密状态 特征。 [0038] 结合第五方面的第一种可能的实现方式和第五方面的第三种可能的实现方式,在第五方面的第五种可能的实现方式中,所述处理器还用于获取用户输入的第二指令 打开未加密内容列表中的第二个条目。 输出设备还用于根据第二指令呈现第二条目对应的内容。 输入设备还用于根据第二指令获取用户输入的生物特征,处理器还用于当用户输入的生物特征与预设生物特征匹配时将第二条目设置为加密状态 特征。 [0039]结合第五方面至第五方面任一种可能的实现方式,在第五方面的第六种可能的实现方式中,所述处理器还用于获取用户在锁屏界面输入的解锁指令 . 输入装置还用于根据解锁指令主动获取用户的生物特征,输出装置还用于当获取的用户生物特征与预设匹配时显示加密应用图标和未加密应用图标。 生物特征,其中,加密应用图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0040] 结合第五方面,在第五方面的第七种可能的实现方式中,所述输出设备还用于在未获取到所述用户的生物特征的情况下显示未加密的应用程序图标,或者所述输出设备还用于显示 如果获取的用户生物特征与预设生物特征不匹配,则未加密的应用程序图标。 [0041] 结合第五方面至第五方面的第七种可能的实现方式中的任一项,在第五方面的第八种可能的实现方式中,所述输入设备还用于获取所述输入设备所在的地理位置和环境信息。 所述移动终端, 所述输入装置还用于若所述移动终端所处的地理位置信息与预设的地理位置信息匹配和/或 环境信息与预设环境信息匹配。 [0042] 第六方面,提供了一种移动终端,所述移动终端包括:处理器,用于获取用户在锁屏界面输入的解锁指令;输入装置,用于根据所述输入设备主动获取用户的生物特征。 解锁指令, 输出设备, 用于当获取的用户生物特征与预设生物特征匹配时, 呈现解锁的第一界面, 其中, 第一界面的界面元素包括加密应用图标和未加密应用图标, 其中, 加密应用图标 应用图标为当获取的用户生物特征与预设生物特征不匹配时不呈现的应用图标。 [0043] 结合第六方面,在第六方面的第一种可能的实现方式中,所述输出设备还用于在获取的用户生物特征与预设生物特征不匹配时,呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0044] 结合第六方面及第六方面的第一种可能的实现方式,在第六方面的第二种可能的实现方式中,所述输入设备还用于获取所述移动终端所在的地理位置和环境信息。 定位,输入设备还用于当移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息时,根据应用启动指令主动获取用户的生物特征。 匹配预设的环境信息。 [0045] 本发明实施例提供了一种移动终端隐私保护方法。 获取应用启动指令后,主动获取用户的生物特征,如果获取的生物特征与预设的生物特征匹配,则显示加密内容和未加密内容,以避免移动终端用户隐私泄露,保护用户隐私。 用户隐私。 另外,主动获取生物特征的方法不易被用户感知。 [0046]应当理解,上面的一般描述和下面的详细描述仅仅是示例,并不限制本公开的保护范围。 附图说明 [0047] 为使本发明实施例的技术方案更加清楚,下面对实施例描述所需的附图进行简要说明。 下面描述中的附图仅为本发明的一些实施例,本领域普通技术人员在没有作出创造性劳动的情况下,还可以从这些附图中获得其他附图。 [0048] 图1示出了根据本发明一个实施例的移动终端隐私保护方法的流程图, [0049] 图2示出了根据本发明实施例的显示内容列表的示意图, [0050] 图3示出了根据本发明实施例的显示未加密内容列表的示意图, [0051] 图4示出了根据本发明一个实施例的移动终端隐私保护方法的流程图, [0052] 图5示出了根据本发明一个实施例的移动终端隐私保护方法的流程图, [0053] 图6示出了根据本发明实施例的显示加密内容列表和未加密内容列表的示意图, [0054] 图7示出了根据本发明实施例的移动终端隐私保护装置的结构示意图, [0055] 图8示出了根据本发明实施例的移动终端隐私保护装置的结构示意图, [0056] 图9示出了根据本发明实施例的移动终端的结构示意图,以及 [0057] 图10示出了根据本发明实施例的移动终端的结构示意图。 [0058] 已经利用前述附图示出了本公开的具体实施例,并且在下文中提供更详细的描述。 这些附图和文字说明并不以任何方式限制本发明的构思范围,而是通过具体实施例为本领域技术人员描述本发明的构思。 具体实施方式 [0059] 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚地描述。 所描述的实施例只是本发明的一部分实施例,并不是全部实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。 [0060] 为了完全理解本公开,以下详细描述提及许多具体细节。 然而,本领域技术人员应当理解,没有这些具体细节也可以实施本公开。 在其他实施例中,省略了众所周知的方法、过程、组件和电路的详细描述,使得描述实施例时不会不必要地模糊。 [0061] 本发明实施例提供一种移动终端隐私保护方法、保护装置及移动终端,以保护移动终端中的用户隐私不易被其他用户察觉。 [0062] 图1示出了根据本公开实施例的移动终端隐私保护方法的流程图。 如图1所示,该方法包括以下步骤。 [0063] 步 101 :获取应用启动指令。 [0064]移动终端中的应用单元也可以称为应用,例如相册、短信业务、通话记录等。 为了启动应用,用户可以触摸应用图标,触摸应用图标后,生成应用启动指令。 [0065] 步 102 :根据应用启动指令主动获取用户的生物特征。 [0066] 进一步地,在主动获取生物特征的实施方式中,不需要提示用户,无需用户许可即可获取用户的生物特征,在输入时获取用户的生物特征。 未获取用户生物特征的说明。 主动获取的方式比较隐蔽,不易被用户察觉。 [0067] 步 103 :若获取的用户生物特征与预设生物特征匹配,则显示对应应用程序的加密内容列表和未加密内容列表。 [0068] 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 简言之,加密内容可以是用户不希望其他用户看到的设置了密码的内容。 [0069] 用户可以将应用单元中的具体内容设置为可以包括加密状态或未加密状态的状态。 加密内容是用户不希望其他用户看到的内容。 例如,对于相册中的照片,用户可以为不希望其他用户看到的照片设置密码。 [0070] 当获取的用户生物特征与预设生物特征不匹配时,不呈现的内容包括至少一种元素。 该元素可以是文字、图片、视频等。 通常,一个元素以一个条目的形式呈现。 加密内容列表可以以列表的形式呈现加密内容。 [0071] 在本发明实施例中,可以对列表进行广义的理解。 对于不同的应用,内容列表可以有不同的形式,可以是条列表,也可以是块列表。 例如,如果应用程序是短信服务或即时通讯程序,则内容列表可以是发送方的电话号码列表,如图2所示的条形短信服务消息列表,以及图2所示的列表。 2 仅显示电话号码或发件人姓名。 如果应用是相册,则内容列表可以是图3所示的照片块缩略图列表,两者 301 和 302 图 3 中的是照片缩略图。 如果应用程序是录音软件或音乐播放软件,则内容列表可以是文件名列表。 [0072] 本发明实施例的方法在接收到应用启动指令后,主动获取用户的生物特征,如果获取的生物特征与预设生物特征匹配的结果显示为机密内容且未加密 内容,可以避免移动终端用户隐私泄露,保护用户隐私。 另外,主动获取生物特征的方法不易被用户感知。 [0073] 在本公开的一个实施例中,经过步骤 103 ,在主动获取用户的生物特征之后,还包括若未获取到用户的生物特征,则显示应用程序的未加密内容列表,若获取到生物特征,则显示应用程序的未加密内容列表。 用户的特征与预设的生物特征不匹配。 [0074]在本发明的一个实施例中,主动获取用户的生物特征包括主动获取用户的面部特征、主动获取用户的眼睛虹膜特征或主动获取用户的指纹。 [0075] 可以通过两种方式获得指纹。 一种方式是通过专门的指纹获取器获取指纹,另一种方式是通过移动终端的屏幕获取指纹。 移动终端指纹获取器的位置随着移动终端的型号不同而不同。 例如,iPhone的指纹获取单元在home键处,华为手机的指纹获取单元在手机背面。 [0076] 部分机型的手机屏幕可以作为屏幕指纹获取器,通过用户在移动终端屏幕上的触摸可以直接获取用户的指纹。 通过触摸屏幕获取用户的指纹更加隐蔽。 [0077] 主动获取可以避免所有者以外的用户察觉到获取了生物特征用于后续验证,以保护移动终端中的隐私,避免可能造成的尴尬。 [0078] 在本发明的另一实施例中,生物特征获取单元还可以为音频获取单元,用于获取用户的语音。 [0079] 在本发明的另一个实施例中,在显示应用程序的未加密内容列表之后,还包括通过移动终端的触摸屏主动获取用户在操作未加密内容列表时录入的指纹,并显示加密后的内容。 如果主动获取的指纹与预设的生物特征匹配,则为应用的内容列表和未加密内容列表。 [0080] 如果应用启动时车主没有正对摄像头,或者因为光线问题或距离问题,可能导致摄像头获取的面部特征或虹膜特征模糊或变形,或者主动获取的指纹模糊。 因此,后续的匹配很难成功,从而所有者很难获得所有想要的信息。 本发明实施例中,在因上述问题显示未加密内容列表后,在未加密内容列表中进入时,通过用户在移动终端屏幕上的触摸,主动获取用户的指纹。 选择内容列表是为了避免误判给业主带来的不便。 [0081] 在本发明的一个实施例中,在显示应用程序的加密内容列表和未加密内容列表之后,该方法还包括获取用户输入的打开加密内容列表中的第一条目的第一指令,呈现, 根据第一指令,第一条目对应的内容, 根据第一指令获取用户输入的生物特征,当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态 特征。 [0082] 在本发明的另一个实施例中,在显示应用程序的加密内容列表和未加密内容列表之后,该方法还包括获取用户输入的打开未加密内容列表中的第二条目的第二指令,呈现, 根据第二指令,第二表项对应的内容, 根据第二指令获取用户输入的生物特征,当用户输入的生物特征与预设生物特征匹配时,将第二表项设置为加密状态 特征。 [0083]所有者在查看加密内容和未加密内容后,在列表中选择条目时,可以通过主动输入生物特征改变所选条目的状态,即将加密内容设置为未加密内容或将未加密内容设置为加密内容 内容。 例如,用户在隐私内容列表中打开一张照片,当用户查看该照片时,手指再次触碰home键主动触发指纹采集命令,或者短时间长按屏幕进行指纹采集。 主动触发屏幕指纹采集指令。 指纹比对成功后,可以切换照片的状态,如果照片是加密的,则可以将照片的状态切换为未加密,如果照片未加密,则可以将照片的状态切换为加密 . 本实施例中,通过主动触发生物特征获取命令来切换应用内容的加密状态或非加密状态的方法方便、高效,且相对隐蔽,不易被其他用户察觉。 [0084] 在本发明的一个实施例中,该方法在接收到应用启动指令之前,还包括获取用户在锁屏界面输入的解锁指令,根据解锁指令主动获取用户的生物特征,并显示 如果获取的用户生物特征与预设生物特征匹配,则为加密应用图标,如果为未加密应用图标,则为未加密应用图标。 [0085] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0086] 在根据解锁指令主动获取用户的生物特征后,还包括若未获取到用户的生物特征则显示未加密的应用程序图标,若获取到的用户的生物特征则显示未加密的应用程序图标。 与预设的生物识别特征不匹配。 [0087] 在本发明的一个实施例中,根据应用启动指令主动获取用户的生物特征还包括获取移动终端所在的地理位置和环境信息,主动获取用户的生物特征。 根据应用启动指令,移动终端所在的地理位置信息是否与预设的地理位置信息匹配和/或环境信息是否与预设的环境信息匹配。 [0088] 通常,用户通过在移动终端中触摸应用程序的图标来启动应用程序。 本实施例的方法在接收到解锁指令后主动获取用户的生物特征,并根据是否获取到生物特征以及获取到的生物特征与用户的匹配情况显示不同的应用图标。 预设生物特征。 可以隐藏所有者不希望其他用户看到或使用的应用程序,进一步避免移动终端中用户隐私的泄露,以保护用户隐私。 另外,主动获取的方式不容易被用户感知。 [0089] 图4示出了根据本公开实施例的移动终端隐私保护方法的流程图。 如图4所示,该方法包括以下步骤。 [0090] 步 401 :获取用户在锁屏界面输入的解锁指令。 [0091] 步 402 :根据解锁指令主动获取用户的生物特征。 [0092] 步 403 :若获取的用户生物特征与预设生物特征匹配,则呈现解锁的第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标。 [0093] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0094]如果获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0095] 通常,用户通过在移动终端中触摸应用程序的图标来启动应用程序。 本实施例的方法在接收到解锁指令后主动获取用户的生物特征,根据是否获取到生物特征以及获取到的生物特征与预设生物特征的匹配情况显示不同的界面。 功能,不同的界面显示不同的应用程序图标。 可以隐藏所有者不希望其他用户看到或使用的应用程序,进一步避免移动终端中用户隐私的泄露,以保护用户隐私。 另外,主动获取的方式不容易被用户感知。 [0096] 在本发明的一个实施例中,根据解锁指令主动获取用户的生物特征还包括获取移动终端所处的地理位置和环境信息,根据解锁指令主动获取用户的生物特征。 如果移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则向应用程序启动指令发送消息。 [0097] 为了进一步保护用户隐私,可以根据移动终端的地理位置信息和环境信息来确定显示的内容。 环境信息可以包括温度、湿度、海拔等。 [0098] 图5示出了根据本公开实施例的移动终端隐私保护方法的流程图。 图5所示的方法以指纹采集为例进行说明。 如图5所示,该方法包括以下步骤。 [0099] 步 501 :获取用户在锁屏界面输入的解锁指令。 [0100] 步 502 :根据解锁指令,通过用户在屏幕上的触摸,主动获取用户的指纹。 [0101] 步 503 :判断是否获取到指纹,如果未获取到指纹,执行步骤 504 ,或者如果获取到指纹,执行步骤 505 . [0102] 步 504 :显示未加密内容列表,执行步骤 507 . [0103] 参见图3所示本发明实施例未加密内容列表的显示示意图,图3所示的应用场景以相册为例。 如图3所示,未加密的内容只有两张照片 301 和 302 根据用户设置。 [0104] 步 505 :判断获取到的指纹是否匹配预留指纹,如果获取到的指纹匹配到预留指纹,则执行步骤 506 , 或者获取到的指纹与预留指纹不匹配,执行步骤 507 . [0105] 步 506 :显示加密内容列表和未加密内容列表。 [0106] 图6示出了根据本发明实施例的显示加密内容列表和未加密内容列表的示意图。 图6所示的应用场景与图3所示相同。如图6所示,根据用户设置,未加密的照片被 301 和 302 ,加密的照片是 303 , 304 , 之类的。 [0107] 步 507 :接收用户从未加密列表中选择照片缩略图,通过用户触摸屏幕主动获取指纹,执行步骤 503 . [0108] 本发明实施例提供的移动终端隐私保护方法,能够在移动终端中保护隐私,不易被用户察觉。 [0109] 图7示出了根据本发明实施例的移动终端隐私保护装置的结构示意图。 如图7所示,该装置包括指令获取单元 701 用于获取应用启动指令、生物特征获取单元 702 用于根据应用启动指令主动获取用户的生物特征,显示单元 703 用于当获取的用户生物特征与预设生物特征匹配时,显示相应应用程序的加密内容列表和未加密内容列表。 [0110] 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 [0111] 显示单元 703 还用于如果未获取到用户的生物特征,则显示应用程序的未加密内容列表,或者显示单元 703 还用于若获取的用户生物特征与预设生物特征不匹配,则显示应用的未加密内容列表。 [0112] 在本公开的一个实施例中,生物特征获取单元 702 包括用于主动获取用户面部特征的拍照子单元(未示出),或生物特征获取单元 702 包括用于主动获取用户的眼睛虹膜特征的摄像子单元(未示出),或者生物特征获取单元 702 包括指纹获取子单元(未示出),用于主动获取用户的指纹。 [0113] 在本发明的一个实施例中,指纹获取子单元还用于通过移动终端的触摸屏主动获取用户在操作未加密内容列表时输入的指纹。 [0114] 显示单元 703 还用于若主动获取的指纹与预设生物特征匹配,则显示应用的加密内容列表。 [0115] 在本发明的一个实施例中,指令获取单元 701 还用于获取用户输入的打开加密内容列表中第一项的第一指令。 [0116] 显示单元 703 还用于根据第一指令呈现第一条目对应的内容。 [0117] 生物特征获取单元 702 还用于根据第一指令获取用户输入的生物特征。 [0118] 该装置还包括设置单元(未示出),用于当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态。 [0119] 指令获取单元 701 还用于获取用户输入的打开未加密内容列表中的第二条目的第二指令。 [0120] 显示单元 703 还用于根据第二指令呈现第二条目对应的内容。 [0121] 生物特征获取单元 702 还用于根据第二指令获取用户输入的生物特征。 [0122] 显示单元 703 还用于当用户输入的生物特征与预设生物特征匹配时,将第二条目设置为加密状态。 [0123] 在本发明的一个实施例中,指令获取单元 701 还用于获取用户在锁屏界面输入的解锁指令。 [0124] 生物特征获取单元 702还用于根据解锁指令主动获取用户的生物特征。 [0125] 显示单元 703 还用于若获取的用户生物特征与预设生物特征匹配,则显示加密应用图标和未加密应用图标。 [0126] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0127] 显示单元 703 还用于如果未获取到用户的生物特征,则显示未加密的应用程序图标,或者显示单元 703 还用于若获取的用户生物特征与预设生物特征不匹配,则显示未加密的应用程序图标。 [0128] 该装置还包括地理位置和环境信息获取单元(未示出),用于获取移动终端所在的地理位置和环境信息。 [0129] 生物特征获取单元 702 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0130] 获取地理位置信息和环境信息可以进一步提高本发明实施例的安全性。 [0131] 图8示出了根据本发明实施例的移动终端保护装置的结构示意图。 如图8所示,该装置包括指令获取单元 801 用于获取用户在锁屏界面输入的解锁指令,生物特征获取单元 802 用于根据解锁指令主动获取用户的生物特征,显示单元 803 用于在获取的用户生物特征与预设生物特征匹配时呈现解锁的第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标。 [0132] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0133] 显示单元 803 还用于若获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0134] 在本发明的一个实施例中,该装置还包括地理位置和环境信息获取单元(未示出),用于获取移动终端所在的地理位置和环境信息。 [0135] 生物特征获取单元 802 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0136] 本发明实施例提供的移动终端隐私保护装置可以保护移动终端中的隐私,不易被其他用户察觉,避免尴尬。 [0137] 图9示出了根据本发明实施例的移动终端的结构示意图。 如图9所示,移动终端包括处理器 901 配置为获取应用启动指令、输入设备 902 用于根据应用启动指令主动获取用户的生物特征,以及输出装置 903用于当获取的用户生物特征与预设生物特征匹配时,显示相应应用程序的加密内容列表和未加密内容列表。 移动终端还包括存储器和总线,其中处理器 901 , 输入设备 902 , 输出设备 903 和内存使用总线相互耦合。 [0138] 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 [0139] 在本公开的一个实施例中,输出设备 903 还用于如果未获取到用户的生物特征,则显示应用的未加密内容列表,或者输出设备 903 还用于若获取的用户生物特征与预设生物特征不匹配,则显示应用的未加密内容列表。 [0140] 在本公开的一个实施例中,输入设备 902 还用于主动获取用户的面部特征,输入设备 902 还用于主动获取用户的眼睛虹膜特征,或者输入设备 902 还用于主动获取用户的指纹。 [0141] 在本公开的一个实施例中,输入设备 902 还用于通过移动终端的触摸屏(未示出)主动获取用户在操作未加密内容列表时录入的指纹。 [0142] 输出设备 903 还用于若主动获取的指纹与预设生物特征匹配,则显示应用的加密内容列表。 [0143] 在本公开的一个实施例中,处理器 901 还用于获取用户输入的打开加密内容列表中第一项的第一指令。 [0144] 输出设备 903 还用于根据第一指令呈现第一条目对应的内容。 [0145] 输入设备 902 还用于根据第一指令获取用户输入的生物特征。 [0146] 处理器 901 还用于当用户输入的生物特征与预设生物特征匹配时,将第一条目设置为未加密状态。 [0147] 处理器 901 还用于获取用户输入的打开未加密内容列表中的第二条目的第二指令。 [0148] 输出设备 903 还用于根据第二指令呈现第二条目对应的内容。 [0149] 输入设备 902 还用于根据第二指令获取用户输入的生物特征。 [0150] 处理器 901 还用于当用户输入的生物特征与预设生物特征匹配时,将第二条目设置为加密状态。 [0151] 在本公开的一个实施例中,处理器 901 还用于获取用户在锁屏界面输入的解锁指令。 [0152] 输入设备 902 还用于根据解锁指令主动获取用户的生物特征。 [0153] 输出设备 903 还用于若获取的用户生物特征与预设生物特征匹配,则显示加密应用图标和未加密应用图标。 [0154] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0155]在本公开的一个实施例中,输出设备 903 还用于如果未获取到用户的生物特征,则显示未加密的应用程序图标,或者输出设备 903 还用于若获取的用户生物特征与预设生物特征不匹配,则显示未加密的应用程序图标。 [0156] 在本公开的一个实施例中,输入设备 902 还用于获取移动终端所在的地理位置和环境信息。 [0157] 输入设备 902 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0158] 图10示出了根据本发明实施例的移动终端的结构示意图。 如图10所示,移动终端包括处理器 1001 用于获取用户在锁屏界面输入的解锁指令,输入设备 1002 用于根据解锁指令主动获取用户的生物特征,以及输出装置 1003 用于在获取的用户生物特征与预设生物特征匹配时呈现解锁的第一界面,第一界面的界面元素包括加密应用图标和未加密应用图标。 移动终端还包括存储器和总线,其中处理器 1001 , 输入设备 1002 , 输出设备 1003 和内存使用总线相互耦合。 [0159] 加密的应用程序图标是在获取的用户生物特征与预设生物特征不匹配时不呈现的应用程序图标。 [0160] 在本公开的一个实施例中,输出设备 1003 还用于若获取的用户生物特征与预设生物特征不匹配,则呈现解锁的第二界面。 第二界面的界面元素包括未加密的应用程序图标。 [0161] 在本公开的一个实施例中,输入设备 1002 还用于获取移动终端所在的地理位置和环境信息。 [0162] 输入设备 1002 还用于若移动终端所在的地理位置信息与预设的地理位置信息匹配和/或环境信息与预设的环境信息匹配,则根据应用启动指令主动获取用户的生物特征。 [0163] 根据本公开的移动终端可以保护用户隐私,并且隐私保护不容易被其他用户察觉以避免尴尬。 [0164] 本发明实施例提供一种移动终端隐私保护方法、装置及移动终端。 获取应用启动指令,根据应用启动指令主动获取用户的生物特征,如果获取的用户生物特征与预设匹配,则显示对应应用的加密内容列表和未加密内容列表 生物特征。 应用的加密内容列表是根据应用中的加密内容生成的,应用的未加密的内容列表是根据应用中的未加密的内容生成的,应用中的加密内容是在获取应用时不呈现的内容。 用户的生物特征与预设的生物特征不匹配。 本发明可以保护移动终端中的隐私,不易被察觉,避免不必要的尴尬,提高用户的使用体验。 [0165]系统实施例基本对应于方法实施例。 相关之处参见方法实施例的部分说明即可。 所描述的系统实施例仅仅是示例。 描述为分立部分的单元在物理上可以是独立的也可以不是,作为单元显示的部分可以是物理单元也可以不是物理单元,可以位于一个位置,也可以分布在多个网络单元上。 可以根据实际需要选择其中的部分或者全部模块来实现本实施例方案的目的。 本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。 [0166] 可以在由计算机执行的可执行计算机指令的一般上下文中描述本公开,例如,程序模块。 通常,程序单元包括用于执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等。 本公开还可以在分布式计算环境中实践,在分布式计算环境中任务由通过通信网络连接的远程处理设备执行。 在分布式计算环境中,程序模块可以位于本地和远程计算机存储介质中,包括存储设备。 [0167] 本领域普通技术人员可以理解,上述方法实施例中的全部或部分步骤可以通过程序指令相关硬件来实现。 该程序可以存储在计算机可读存储介质中,例如只读存储器(ROM)、随机存取存储器(RAM)、磁盘或光盘。 [0168] 需要说明的是,在本说明书中,诸如第一和第二等关系术语仅用于区分一个实体或操作与另一个实体或操作,并不一定要求或暗示这些实体或操作之间存在任何实际关系或顺序。 此外,术语“包括”、“包含”或它们的任何其他变体旨在涵盖非排他性的包含,使得包括一系列要素的过程、方法、物品或设备不仅包括那些 元素,但也包括未明确列出的其他元素,或进一步包括此类过程、方法、物品或设备固有的元素。 前面带有“的元素包括一个 . . . ” 在没有更多限制的情况下,不排除在包含该元素的过程、方法、物品或设备中存在其他相同元素。 [0169] 总之,以上所述仅为本发明的实施例而已,并不用于限定本发明的保护范围。 本说明书通过具体示例来说明本发明的原理和实施方式。 以上实施例的描述仅仅用于帮助理解本发明的方法和核心思想。 此外,本领域的技术人员可以根据本发明的思想,对具体的实施方式和适用范围进行修改。 因此,本说明书的内容不应理解为对本发明的限制。 因此,本说明书的内容不应理解为对本发明的限制。 凡在本发明的精神和原则的范围内,所做的任何修改、等同替换、改进等,均属于本发明的保护范围。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.824 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.825 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN106233294A(String), CN106233294B(String), CN112597469A(String), EP3252637A1(String), EP3252637A4(String), EP3252637B1(String), EP4080387A1(String), ES2923905T3(String), JP2018517960A(String), JP6571203B2(String), US10382204B2(String), US11394555B2(String), US20180062846A1(String), US20190334721A1(String), US20220385471A1(String), WO2016154898A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:29.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN106233294A(String), CN106233294B(String), CN112597469A(String), EP3252637A1(String), EP3252637A4(String), EP3252637B1(String), EP4080387A1(String), ES2923905T3(String), JP2018517960A(String), JP6571203B2(String), US10382204B2(String), US11394555B2(String), US20180062846A1(String), US20190334721A1(String), US20220385471A1(String), WO2016154898A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.003 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN106233294A(String), CN106233294B(String), CN112597469A(String), EP3252637A1(String), EP3252637A4(String), EP3252637B1(String), EP4080387A1(String), ES2923905T3(String), JP2018517960A(String), JP6571203B2(String), US10382204B2(String), US11394555B2(String), US20180062846A1(String), US20190334721A1(String), US20220385471A1(String), WO2016154898A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 25 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.026 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.027 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), CN106233294A(String), 183802(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.059 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.060 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), CN106233294B(String), 183803(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.094 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.094 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.094 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), CN112597469A(String), 183804(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.127 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), EP3252637A1(String), 183805(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.161 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), EP3252637A4(String), 183806(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.194 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), EP3252637B1(String), 183807(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.227 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 66873(Integer), EP4080387A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.263 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.264 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 66873(Integer), ES2923905T3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.298 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.299 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), JP2018517960A(String), 183808(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.332 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), JP6571203B2(String), 183809(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), US10382204B2(String), 183810(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.399 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), US11394555B2(String), 346233(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.433 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.434 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.434 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), US20180062846A1(String), 183811(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.466 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.467 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), US20190334721A1(String), 183812(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.500 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 66873(Integer), US20220385471A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.535 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Preparing: UPDATE os_patent_simplefamily_link SET family_id=?, patent_no=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.536 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById ==> Parameters: 66873(Integer), WO2016154898A1(String), 183813(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=?, inpadoc_family=?, patsnap_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: EP3252637B1(String), EP3252637B1(String), 1652198400(Integer), 66873(Integer), 66874(Integer), 59061(Integer), 31166(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily_link WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.602 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete ==> Parameters: 88967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.637 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Preparing: DELETE FROM os_patent_simplefamily WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete ==> Parameters: 88967(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.672 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.delete <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.673 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 华为技术有限公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.719 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.752 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186016(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 1(Integer), 186016(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.822 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: HUAWEI TECHNOLOGIES CO., LTD.(String), 华为技术有限公司(String), 255(String), 0(Integer), 1660811217(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186016(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.889 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19067(Integer), 2(Integer), 186016(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.924 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.959 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19067(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.976 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:30.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.029 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.046 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.199 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.199 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.199 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186016(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.235 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.236 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20120259775A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.577 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Application Method of Mobile Terminal Electronic Wallet and Mobile Terminal(String), 移动终端电子钱包应用方法及移动终端(String), US20120259775A1(String), Disclosed in the present invention is an application method for a mobile terminal electronic wallet, including: monitoring a transaction event carried out by the mobile terminal via the NFC chip; when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; and sending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing the consumption situation of the transaction event to a user. Also disclosed in the present invention is a mobile terminal, wherein, an acquiring module is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after a monitoring module monitors the transaction event; and a sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application but cannot be displayed automatically is solved.(String), 本发明公开了一种移动终端电子钱包的应用方法,包括:通过NFC芯片监听移动终端进行的交易事件; 当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息; 将交易消息发送给JAVA模块,启动相应的JAVA应用程序,将交易事件的消费情况提供给用户。 本发明还公开了一种移动终端,其中,获取模块,用于在监听模块监听到交易事件后,获取UICC通过NFC芯片发送的交易事件的交易消息; 发送模块,用于将交易消息发送给JAVA模块,启动相应的JAVA应用程序,但无法自动显示。(String), US13/513778(String), 1271779200(Integer), US20120259775A1(String), 1349884800(Integer), 美国(String), 2(Integer), CN(String), 4(Integer), 3(Integer), US20080121687A1 | US20100083280A1 | US20100136913A1(String), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.613 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186017(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.760 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\4aca4b0ad86f46ef960362d0b4813cc6.png(String), 186017(Integer), 4aca4b0ad86f46ef960362d0b4813cc6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.798 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.820 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.821 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Application Method of Mobile Terminal Electronic Wallet and Mobile Terminal(String), 移动终端电子钱包应用方法及移动终端(String), US20120259775A1(String), Disclosed in the present invention is an application method for a mobile terminal electronic wallet, including: monitoring a transaction event carried out by the mobile terminal via the NFC chip; when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; and sending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing the consumption situation of the transaction event to a user. Also disclosed in the present invention is a mobile terminal, wherein, an acquiring module is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after a monitoring module monitors the transaction event; and a sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application but cannot be displayed automatically is solved.(String), 本发明公开了一种移动终端电子钱包的应用方法,包括:通过NFC芯片监听移动终端进行的交易事件; 当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息; 将交易消息发送给JAVA模块,启动相应的JAVA应用程序,将交易事件的消费情况提供给用户。 本发明还公开了一种移动终端,其中,获取模块,用于在监听模块监听到交易事件后,获取UICC通过NFC芯片发送的交易事件的交易消息; 发送模块,用于将交易消息发送给JAVA模块,启动相应的JAVA应用程序,但无法自动显示。(String), US13/513778(String), 1271779200(Integer), US20120259775A1(String), 1349884800(Integer), 美国(String), 2(Integer), 2(Integer), CN(String), 4(Integer), 3(Integer), US20080121687A1 | US20100083280A1 | US20100136913A1(String), \20230420\4aca4b0ad86f46ef960362d0b4813cc6.png(String), 6(Integer), 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.857 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.858 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.891 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186017(Integer), 1. An application method for a mobile terminal electronic wallet with a near field communication (NFC) chip being integrated into the mobile terminal, comprising:monitoring a transaction event carried out by the mobile terminal via the NFC chip;when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; andsending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing a consumption situation of the transaction event to a user.(String), 1、一种移动终端集成近场通信(NFC)芯片的移动终端电子钱包的应用方法,包括:通过NFC芯片监测移动终端进行的交易事件;当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息;和将交易消息发送给JAVA模块,启动相应的JAVA应用,向用户提供交易事件的消费情况。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186017(Integer), 2. The method according to claim 1, wherein sending the transaction message to a JAVA module and starting up a corresponding JAVA application further comprises:the JAVA module receiving the transaction message and invoking a PUSH interface to start up the corresponding JAVA application.(String), 2.根据权利要求1所述的方法,其中向JAVA模块发送交易消息并启动相应的JAVA应用程序还包括:JAVA模块接收交易消息,调用PUSH接口启动相应的JAVA应用。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186017(Integer), 3. The method according to claim 2, wherein invoking a PUSH interface to start up the corresponding JAVA application further comprises:acquiring PUSH register information about the application from a set PUSH register information list; andparsing the PUSH register information about the application and starting up the corresponding JAVA application.(String), 3.根据权利要求2所述的方法,其中调用PUSH接口启动对应的JAVA应用还包括:从设置的PUSH注册信息列表中获取应用的PUSH注册信息;和解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186017(Integer), 4. A mobile terminal in which an NFC chip is integrated, comprising a JAVA module and further comprising a monitoring module, an acquiring module, a sending module, and a display module, whereinthe monitoring module is used for monitoring a transaction event carried out by the mobile terminal via the NFC chip;the acquiring module is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after the monitoring module monitors the transaction event;the sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application; andthe display module is used for providing a consumption situation regarding the transaction event to a user.(String), 4.移动端其中集成NFC芯片,包括JAVA模块,还包括监控模块、获取模块、发送模块和显示模块,其中监听模块用于监听移动终端通过NFC芯片进行的交易事件;获取模块,用于在监听模块监听到交易事件后,通过NFC芯片获取UICC发送的交易事件的交易消息;发送模块,用于将交易消息发送给JAVA模块,并启动相应的JAVA应用程序;和显示模块用于向用户提供交易事件的消费情况。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186017(Integer), 5. The mobile terminal according to claim 4, further comprising a JAVA virtual machine, whereinthe JAVA module is further used for receiving the transaction message and starting up the JAVA virtual machine; andthe JAVA virtual machine is used for invoking a PUSH interface to start up the corresponding JAVA application.(String), 5.根据权利要求4所述的移动终端,还包括JAVA虚拟机,其中JAVA模块还用于接收交易消息和启动JAVA虚拟机。和JAVA虚拟机用于调用PUSH接口启动相应的JAVA应用程序。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:31.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186017(Integer), 6. The mobile terminal according to claim 5, wherein the JAVA virtual machine is further used for acquiring PUSH register information about the application from a set PUSH register information list; and parsing the PUSH register information about the application and starting up the corresponding JAVA application.(String), 6.根据权利要求5所述的移动终端,其中JAVA虚拟机还用于从设定的PUSH注册信息列表中获取应用程序的PUSH注册信息;解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.033 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186017(Integer), TECHNICAL FIELD [0001]The present invention relates to the communication field, and particularly, to an application method for a mobile terminal electronic wallet and a mobile terminal. BACKGROUND OF THE RELATED ART [0002]With the development of the near field communication (NFC) technology, the near field consumption also has been significantly changed. The mobile terminal such as mobile phone becomes a secure, convenient, rapid and fashionable contactless payment and ticket tool. The mobile terminal becomes a transportation card and a bank card, so that the mobile phone can be swiped for consumption just as swiping the transportation card and the bank card. People especially like the easy usage, convenience and rapidness of contactless payment of the NFC and wish to no longer carry on a wallet. The transaction can be done only by making the mobile terminal approach the device terminal without presenting the payment card. [0003]The solutions for realizing near field consumption with the NFC technology are mainly as follows: 1. profiled pasting card in which a token is pasted on the mobile phone, such as the Bank in Palm service in Chongqing city; 2. SIMpass, i.e. dual SIM cards, such as Watchdata solution; 3. NFC, wherein an NFC chip is integrated in the mobile phone and the single wire protocol (SWP) SIM card is not supported; 4. eNFC, wherein the chip and SIM card supporting the SWP protocol have to be integrated; 5. 2.4G radio frequency (abbreviated as RF) SIM, wherein a 2.4G communication module is integrated in the SIM card, and the SIM card has to be directly changed. In this case, the chip and SIM card supporting the SWP protocol need to be integrated with eNFC, which currently is a very popular technical solution. [0004]Since NFC has broad market prospect, the mobile operators are positively promoting the development of this industry chain, and the electronic wallet and electronic ticket service are especially valued. Currently, the process of using the NFC electronic wallet to consume is as shown in FIG. 1, after the NFC chip of the mobile phone is activated, micro payment function can be realized by a POS machine when the mobile phone is in the card emulation state. [0005]Referring to FIG. 1, the POS machine initiates a consumption request, the NFC chip forwards the request to the SIM card, the SIM card would respond, and after the transaction is over, the user can check the transaction situation of the mobile phone wallet by opening the JAVA client. [0006]FIG. 2 is a schematic diagram of the working principle of consuming using an NFC electronic wallet, referring to FIG. 2, it includes a universal integrated circuit card (UICC), an NFC radio frequency chip (MicroRead) and a mobile phone processor. The part relevant to the application is totally placed in the smart SIM card, i.e. UICC, and the MicroRead is integrated in the mainboard of the mobile phone. The MicroRead communicates with the mobile phone processor via a UART interface, and communicates with the application part in the UICC via the SWP protocol. After the mobile phone has transacted with the POS machine, the UICC can send message to the mobile phone processor via the MicroRead. [0007]There is a problem in the above operation: assuming that the mobile phone is in the standby interface, after the mobile phone has carries out a transaction, the user will habitually check the balance of the electronic wallet, however, currently, the application carry out a query manually on the market, the user has to enter JAVA and then start up the application, which greatly affects the user experience. [0008]In summary, it can be known that the problem that the balance of the electronic wallet can only be checked manually and cannot be displayed automatically always exists in the related art, therefore, it is necessary to propose an improved technical means to solve this problem. SUMMARY OF THE INVENTION [0009]The present invention is proposed in view of the problem in the related art that the balance of the electronic wallet can only be checked manually and cannot be displayed automatically, for this end, the main object of the present invention is to provide an application method for a mobile terminal electronic wallet and a mobile terminal, wherein[0010]the present invention provides an application method for a mobile terminal electronic wallet with an near field communication (NFC) chip being integrated into the mobile terminal, including: monitoring a transaction event carried out by the mobile terminal via the NFC chip; when the transaction event happens, acquiring transaction message regarding the transaction event sent by a universal integrated circuit card (UICC) via the NFC chip; and sending the transaction message to a JAVA module, starting up a corresponding JAVA application, and providing the consumption situation of the transaction event to a user. [0011]Preferably, sending the transaction message to a JAVA module and starting up a corresponding JAVA application further comprises: the JAVA module receiving the transaction message and invoking a PUSH interface to start up the corresponding JAVA application. [0012]Preferably, invoking a PUSH interface to start up the corresponding JAVA application further comprises: acquiring PUSH register information about the application from a set PUSH register information list; and parsing the PUSH register information about the application and starting up the corresponding JAVA application. [0013]The present invention provides a mobile terminal in which an NFC chip is integrated, comprising a JAVA module and further comprising a monitoring module, an acquiring module, a sending module, and a display module, wherein[0014]the monitoring module is used for monitoring a transaction event carried out by the mobile terminal via the NFC chip; the acquiring module is used for acquiring a transaction message regarding the transaction event sent by a UICC via the NFC chip after the monitoring module monitors the transaction event; the sending module is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application; and the display module is used for providing the consumption situation regarding the transaction event to a user. [0015]Preferably, this mobile terminal further comprises a JAVA virtual machine, wherein[0016]the JAVA module is further used for receiving the transaction message and starting up the JAVA virtual machine; and the JAVA virtual machine is used for invoking a PUSH interface to start up the corresponding JAVA application. [0017]Preferably, the JAVA virtual machine is further used for acquiring PUSH register information about the application from a set PUSH register information list; and parsing the PUSH register information about the application and starting up the corresponding JAVA application. [0018]As compared to the related art, in the above technical solution according to the present invention, the transaction message sent by the UICC via the NFC chip is used to activate the PUSH function of JAVA and start up a relevant JAVA application, thereby realizing the purpose of automatically starting up the application, thus automatically displaying the consumption situation to the user and enhancing user experience. BRIEF DESCRIPTION OF DRAWINGS [0019]FIG. 1 is a schematic diagram of the process of using an NFC electronic wallet application to consume in the related art; [0020]FIG. 2 is a schematic diagram of the working principle of using an NFC electronic wallet application to consume in the related art; [0021]FIG. 3 is a flowchart of an application method for a mobile terminal electronic wallet according to the embodiments of the present invention; [0022]FIG. 4 is a flowchart of starting up PUSH when a mobile terminal carries out a transaction event according to the embodiments of the present invention; [0023]FIG. 5 is a flowchart of the process of starting up an application by PUSH according to the embodiments of the present invention; and [0024]FIG. 6 is a block diagram of a mobile terminal according to the embodiments of the present invention. PREFERRED EMBODIMENTS OF THE PRESENT INVENTION [0025]The main concept of the present invention lies in: when the mobile terminal uses the electronic wallet to consume, the transaction message sent by the UICC via the NFC chip is used to activate the PUSH function of JAVA and start up the relevant JAVA application, so as to realize the purpose of automatically starting up the application. It needs to be noted that a JAVA application to be automatically started up needs to be installed on the mobile terminal according to the embodiments of the present invention, and at the same time, this application is PUSH registered. [0026]In order to make the object, technical solution and advantages of the present invention more clear, the present invention will be further described in detail in conjunction with the accompanying drawings and particular embodiments. [0027]FIG. 3 is a flowchart of an application method for a mobile terminal electronic wallet according to the embodiments of the present invention, and as shown in the figure, this method includes:[0028]in step S302, it is to monitor a transaction event carried out by the mobile terminal via the NFC chip. [0029]In step S304, when a transaction event happens, it is to acquire a transaction message regarding the transaction event sent by the UICC via the NFC chip. [0030]In step S306, it is to send the transaction message to a JAVA module, start up a corresponding JAVA application, and provide the consumption situation of the transaction event to a user. [0031]Hereinafter, the above processing details will be described in detail in conjunction with FIG. 4 and FIG. 5. [0032]FIG. 4 is a flowchart of starting up PUSH when a mobile terminal carries out a transaction event according to the embodiments of the present invention. Hereinafter, a mobile phone is taken as an example for description. As shown in FIG. 4, this processing flow includes:[0033]in step S401, it is to activate the NFC chip. [0034]In step S402, the platform starts to monitor a card swiping event and registers for a callback function A, and A is mainly used for sending message to the upper application, such as transaction message. [0035]In step S403, the POS machine sends a transaction request to carry out a consumption operation. [0036]In step S404, the mobile phone responds and feeds back the information of whether the operation is successful to the POS machine. [0037]In step S405, the UICC sends message to the NFC chip. [0038]In step S406, after having received the message, the NFC chip will start up the callback function A registered in the step S402, and if no message is received, no operation will be performed. [0039]In step S407, it is to start up the virtual machine and application and send the message to the JAVA module. [0040]The above processing corresponds to the steps S302 and S304. [0041]FIG. 5 is a flowchart of the process of starting up an application by PUSH according to the embodiments of the present invention. It needs to be noted that the self-starting application must have been PUSH registered, and the register information is stored into a PUSH register information list in the JAVA module. As shown in FIG. 5, this processing flow includes:[0042]in step S501, the JAVA module receives message. [0043]In step S502, the JAVA module starts up the JAVA virtual machine. [0044]In step S503, the JAVA virtual machine acquires the PUSH register information about the application from the PUSH register information list. [0045]In step S504, the JAVA virtual machine parses the PUSH register information about the application and sets the information about the application to be started up. [0046]In step S505, it is to start up the JAVA client application. [0047]In step S506, it is to provide the consumption situation about the transaction event to the user, for example, it is to prompt the user whether to display the consumption situation on the screen of the mobile terminal, if the user selects displaying, then it is to display the balance of the mobile phone wallet on the screen, etc. [0048]The above processing corresponds to step S306. [0049]After the above processing, the consumption situation can be prompted to the user automatically, enhancing the user experience. [0050]FIG. 6 is a block diagram of a mobile terminal in which an NFC chip is integrated according to the embodiments of the present invention. As shown in FIG. 6, this mobile terminal comprises: a monitoring module 10, an acquiring module 20, a sending module 30, and a display module 40, wherein[0051]the monitoring module 10 is used for monitoring a transaction event carried out by the mobile terminal via the NFC chip. [0052]The acquiring module 20 is used for acquiring transaction message regarding the transaction event sent by a UICC via the NFC chip after the monitoring module 10 monitors the transaction event. [0053]The sending module 30 is used for sending the transaction message to a JAVA module and starting up a corresponding JAVA application. [0054]The display module 40 is used for providing the consumption situation regarding the transaction event to a user. [0055]Moreover, this mobile terminal further comprises: a JAVA module for receiving the transaction message and starting up a JAVA virtual machine; and the JAVA virtual machine for invoking a PUSH interface to start up the corresponding JAVA application. In particular, the JAVA virtual machine acquires PUSH register information about the application from a preset PUSH register information list; and parses the PUSH register information about the application and starts up the corresponding JAVA application. [0056]In summary, in the above technical solution according to the present invention, the transaction message sent by the UICC via the NFC chip is used to activate the PUSH function of JAVA and start up a relevant JAVA application, thereby realizing the purpose of automatically starting up the application, automatically displaying the consumption situation to the user and enhancing user experience. [0057]Above description is only to illustrate the preferred embodiments but not to limit the present invention. Various alternations and changes to the present invention are apparent to those skilled in the art. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the scope defined by the claims of the present invention.(String), 技术领域 [0001] 本发明涉及通信领域,尤其涉及一种移动终端电子钱包的应用方法及移动终端。 相关技术背景 [0002] 随着近场通信(NFC)技术的发展,近场消费也发生了显着变化。 手机等移动终端成为安全、方便、快捷、时尚的非接触式支付购票工具。 移动终端变成交通卡和银行卡,像刷交通卡和银行卡一样刷手机消费。 人们尤其喜欢NFC非接触式支付的易用性、方便性和快捷性,并希望不再随身携带钱包。 无需出示支付卡,只需让移动终端靠近设备终端即可完成交易。 [0003] 利用NFC技术实现近场消费的解决方案主要有: 1.仿形粘贴卡,将令牌粘贴在手机上,如重庆市的掌上银行业务。 2. SIMpass,即双SIM卡,如握奇解决方案; 3、NFC,手机中集成了NFC芯片,不支持单线协议(SWP)SIM卡; 4. eNFC,其中支持SWP协议的芯片和SIM卡必须集成; 5、2.4G射频(简称RF)SIM卡,SIM卡内集成2.4G通信模块,直接换SIM卡即可。 在这种情况下,支持SWP协议的芯片和SIM卡需要集成eNFC,这是目前非常流行的技术方案。 [0004] 由于NFC具有广阔的市场前景,移动运营商正在积极推动这一产业链的发展,电子钱包和电子票务业务尤为看重。 目前使用NFC电子钱包消费的流程如图1所示,激活手机的NFC芯片后,手机处于卡模拟状态时,可以通过POS机实现小额支付功能 . [0005] 参考图1,POS机发起消费请求,NFC芯片将请求转发给SIM卡,SIM卡响应,交易结束后,用户可以通过以下方式查看手机钱包交易情况 打开 JAVA 客户端。 [0006] 图2是使用NFC电子钱包消费的工作原理示意图,参见图2,它包括通用集成电路卡(UICC)、NFC射频芯片(MicroRead)和手机处理器。 与应用相关的部分完全放在智能SIM卡中,即UICC,MicroRead集成在手机主板中。 MicroRead通过UART接口与手机处理器通信,通过SWP协议与UICC中的应用部分通信。 手机与POS机交易完成后,UICC可以通过MicroRead向手机处理器发送消息。 [0007] 上述操作存在一个问题:假设手机处于待机界面,当手机进行交易后,用户会习惯性地查看电子钱包余额,而目前应用执行 市面上的手动查询,用户要先输入JAVA再启动应用,非常影响用户体验。 [0008] 综上所述,可知电子钱包的余额只能人工查询,无法自动显示的问题一直存在于相关技术中,因此,有必要提出一种改进的技术手段来解决该问题。 发明内容 [0009] 本发明是针对相关技术中电子钱包余额只能人工查询,不能自动显示的问题而提出的,为此,本发明的主要目的在于提供一种应用方法 一种移动终端电子钱包及移动终端,其中 [0010]本发明提供了一种移动终端集成近场通信(NFC)芯片的移动终端电子钱包的应用方法,包括:通过NFC芯片监听移动终端进行的交易事件; 当交易事件发生时,通过NFC芯片获取通用集成电路卡(UICC)发送的关于交易事件的交易消息; 将交易消息发送给JAVA模块,启动相应的JAVA应用,将交易事件的消费情况提供给用户。 [0011] 优选地,向JAVA模块发送交易消息并启动相应的JAVA应用还包括: JAVA模块接收交易消息并调用PUSH接口启动相应的JAVA应用。 [0012] 优选地,调用PUSH接口启动对应的JAVA应用还包括: 从设置的PUSH注册信息列表中获取该应用的PUSH注册信息; 解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。 [0013] 本发明提供了一种集成有NFC芯片的移动终端,包括JAVA模块,还包括监控模块、获取模块、发送模块和显示模块,其中, [0014] 监听模块用于监听移动终端通过NFC芯片进行的交易事件; 获取模块,用于在监听模块监听到交易事件后,通过NFC芯片获取UICC发送的交易事件的交易消息; 发送模块,用于将交易消息发送给JAVA模块,并启动相应的JAVA应用程序; 显示模块用于向用户提供交易事件的消费情况。 [0015] 优选地,该移动终端还包括JAVA虚拟机,其中 [0016] JAVA模块还用于接收交易消息和启动JAVA虚拟机。 JAVA虚拟机用于调用PUSH接口启动相应的JAVA应用。 [0017] 优选地,所述JAVA虚拟机还用于从设置的PUSH注册信息列表中获取应用程序的PUSH注册信息; 解析应用程序的PUSH寄存器信息,启动对应的JAVA应用程序。 [0018] 与相关技术相比,本发明的上述技术方案中,利用UICC通过NFC芯片发送的交易消息,来激活JAVA的PUSH功能,启动相关的JAVA应用,从而实现了目的 自动启动应用,自动向用户展示消费情况,提升用户体验。 附图说明 [0019] 图1为相关技术中使用NFC电子钱包应用进行消费的流程示意图; [0020] 图2为相关技术中使用NFC电子钱包应用进行消费的工作原理示意图; [0021] 图3为本发明实施例的移动终端电子钱包的应用方法流程图; [0022] 图4为本发明实施例移动终端进行交易事件时启动PUSH的流程图; [0023] 图5是根据本发明实施例的通过PUSH启动应用程序的过程的流程图; 和 [0024] 图6是根据本发明实施例的移动终端的框图。 本发明的优选实施例 [0025] 本发明的主要思想在于:移动终端使用电子钱包进行消费时,利用UICC通过NFC芯片发送的交易报文,激活JAVA的PUSH功能,启动相关的JAVA应用,从而 从而实现应用自动启动的目的。 需要说明的是,本发明实施例的移动终端需要安装一个自动启动的JAVA应用,同时该应用是PUSH注册的。 [0026] 为使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及具体实施例对本发明进行进一步详细说明。 [0027] 图3为本发明实施例提供的一种移动终端电子钱包的应用方法流程图,如图所示,该方法包括: [0028]在步骤S 302 ,是监听移动终端通过NFC芯片进行的交易事件。 [0029] 在步骤S 304 ,当交易事件发生时,通过NFC芯片获取UICC发送的交易事件的交易消息。 [0030] 在步骤S 306 ,就是将交易消息发送给一个JAVA模块,启动相应的JAVA应用程序,将交易事件的消费情况提供给用户。 [0031] 下面结合图4和图5对上述处理细节进行详细说明。 [0032]图4为本发明实施例移动终端进行交易事件时启动PUSH的流程图。 下面以手机为例进行说明。 如图4所示,该处理流程包括: [0033]在步骤S 401 ,就是激活NFC芯片。 [0034] 在步骤S 402 ,平台开始监听一个刷卡事件,注册一个回调函数A,A主要用于向上层应用发送消息,比如交易消息。 [0035] 在步骤S 403 ,POS机发送交易请求进行消费操作。 [0036] 在步骤S 404 ,手机响应并向POS机反馈操作是否成功信息。 [0037] 在步骤S 405 ,UICC向NFC芯片发送消息。 [0038] 在步骤S 406 ,NFC芯片收到消息后,会启动步骤S中注册的回调函数A 402 , 如果没有收到消息,则不会执行任何操作。 [0039] 在步骤S 407 ,就是启动虚拟机和应用,向JAVA模块发送消息。 [0040] 以上处理对应步骤S 302 和小号 304 . [0041] 图5是根据本发明实施例的通过PUSH启动应用程序的过程的流程图。 需要注意的是,自启动应用必须已经PUSH注册过,注册信息存储在JAVA模块中的一个PUSH注册信息列表中。 如图5所示,该处理流程包括: [0042]在步骤S 501 ,JAVA模块接收消息。 [0043] 在步骤S 502 ,JAVA模块启动JAVA虚拟机。 [0044] 在步骤S 503 ,JAVA虚拟机从PUSH寄存器信息列表中获取应用程序的PUSH寄存器信息。 [0045] 在步骤S 504 ,JAVA虚拟机解析应用程序的PUSH寄存器信息,设置要启动的应用程序信息。 [0046] 在步骤S 505 ,就是启动JAVA客户端应用程序。 [0047] 在步骤S 506 ,就是向用户提供交易事件的消费情况,比如提示用户是否在移动端的屏幕上显示消费情况,如果用户选择显示,则显示 屏幕上的手机钱包余额等。 [0048] 以上处理对应步骤S 306 . [0049] 经过上述处理后,可以自动向用户提示消费情况,提升用户体验。 [0050] 图6是根据本发明实施例的集成有NFC芯片的移动终端的框图。 如图6所示,该移动终端包括: 监控模块 10 , 获取模块 20 , 发送模块 30 , 和一个显示模块 40 , 其中 [0051]监控模块 10 用于监听移动终端通过NFC芯片进行的交易事件。 [0052] 获取模块 20 用于在监控模块之后通过NFC芯片获取UICC发送的交易事件的交易消息 10 监听事务事件。 [0053] 发送模块 30 用于向JAVA模块发送交易消息,并启动相应的JAVA应用程序。 [0054] 显示模组 40 用于向用户提供交易事件的消费情况。 [0055] 进一步地,该移动终端还包括: JAVA模块,用于接收交易消息并启动JAVA虚拟机; JAVA虚拟机调用PUSH接口启动相应的JAVA应用程序。 具体地,JAVA虚拟机从预设的PUSH注册信息列表中获取应用程序的PUSH注册信息; 并解析应用程序的PUSH注册信息,启动对应的JAVA应用程序。 [0056]综上所述,在本发明的上述技术方案中,利用UICC通过NFC芯片发送的交易消息来激活JAVA的PUSH功能,启动相关的JAVA应用,从而实现自动启动的目的 应用,自动向用户展示消费情况,提升用户体验。 [0057] 以上所述仅为本发明的优选实施例而已,并不用于限制本发明。 本发明的各种更改和变化对于本领域的技术人员来说是显而易见的。 凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.093 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.094 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.095 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN101789151A(String), EP2500875A1(String), EP2500875A4(String), US20120259775A1(String), WO2010148737A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.252 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN101789151A(String), EP2500875A1(String), EP2500875A4(String), US20120259775A1(String), WO2010148737A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20120259775A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN101789151A(String), EP2500875A1(String), EP2500875A4(String), US20120259775A1(String), WO2010148737A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.323 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.324 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271685(Integer), CN101789151A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.358 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271685(Integer), EP2500875A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.393 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271685(Integer), EP2500875A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.429 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271685(Integer), US20120259775A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.471 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.471 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.471 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271685(Integer), WO2010148737A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.506 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.507 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.507 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20120259775A1(String), US20120259775A1(String), 1349884800(Integer), 271685(Integer), 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.542 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), GUI, ZUHONG(String), 中兴通讯股份有限公司(String), GUI ZUHONG(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.588 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.621 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186017(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.655 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186017(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.693 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: GUI, ZUHONG(String), GUI ZUHONG(String), 0(Integer), 1681976192(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.728 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.729 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186017(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.761 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.762 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75865(Integer), 2(Integer), 186017(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.799 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.800 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.817 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.817 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.817 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.832 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.833 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.833 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75865(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.855 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.871 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.912 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.913 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:32.931 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.084 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186017(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.119 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.120 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9952741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.475 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.476 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.477 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal application icon management method and mobile terminal(String), 移动终端应用图标管理方法及移动终端(String), US9952741B2(String), Disclosed are a mobile terminal application icon management method and a mobile terminal. The mobile terminal application icon management method comprises: presetting class information about an application, and establishing a mapping relation table among an application class, a screen serial number of a display screen and an application icon; receiving an object moving instruction, obtaining regular pattern information corresponding to a moved object according to the object moving instruction, and displaying the regular pattern information; and after the moved object is successfully moved to the corresponding region of a regular pattern, updating the corresponding mapping relation table among the application class, the screen serial number of a display screen and the application icon. The present invention simplifies the management operation process of an application icon, and achieves batch management and multimodal management of an application icon, thereby greatly facilitating the management operation of a user in respect of an application icon.(String), 本发明公开了一种移动终端应用图标管理方法及移动终端。 移动终端应用图标管理方法,包括:预先设置应用的类信息,建立应用类、显示屏的屏序号和应用图标之间的映射关系表; 接收对象移动指令,根据对象移动指令获取移动对象对应的规则图案信息,并显示规则图案信息; 移动对象成功移动到规则图案的对应区域后,更新应用类、显示屏的屏序号和应用图标之间对应的映射关系表。 本发明简化了应用程序图标的管理操作流程,实现了应用程序图标的批量管理和多模式管理,极大地方便了用户对应用程序图标的管理操作。(String), US14/382592(String), 1336924800(Integer), US9952741B2(String), 1524499200(Integer), 1524499200(Integer), 美国(String), 4(Integer), CN(String), 4(Integer), 15(Integer), CN102236525A | CN102306080A | CN102306084A | CN102360266A | CN102364438A | EP2426898A2 | US20040155907A1 | US20070050811A1 | US20100333030A1 | US20110258582A1 | US20120052918A1 | US5544302A | US7068288B1 | US7350158B2 | US7693877B1(String), 8(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.550 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.552 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186018(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.708 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\2ab163434aca477098f96e0e96436fa6.png(String), 186018(Integer), 2ab163434aca477098f96e0e96436fa6.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal application icon management method and mobile terminal(String), 移动终端应用图标管理方法及移动终端(String), US9952741B2(String), Disclosed are a mobile terminal application icon management method and a mobile terminal. The mobile terminal application icon management method comprises: presetting class information about an application, and establishing a mapping relation table among an application class, a screen serial number of a display screen and an application icon; receiving an object moving instruction, obtaining regular pattern information corresponding to a moved object according to the object moving instruction, and displaying the regular pattern information; and after the moved object is successfully moved to the corresponding region of a regular pattern, updating the corresponding mapping relation table among the application class, the screen serial number of a display screen and the application icon. The present invention simplifies the management operation process of an application icon, and achieves batch management and multimodal management of an application icon, thereby greatly facilitating the management operation of a user in respect of an application icon.(String), 本发明公开了一种移动终端应用图标管理方法及移动终端。 移动终端应用图标管理方法,包括:预先设置应用的类信息,建立应用类、显示屏的屏序号和应用图标之间的映射关系表; 接收对象移动指令,根据对象移动指令获取移动对象对应的规则图案信息,并显示规则图案信息; 移动对象成功移动到规则图案的对应区域后,更新应用类、显示屏的屏序号和应用图标之间对应的映射关系表。 本发明简化了应用程序图标的管理操作流程,实现了应用程序图标的批量管理和多模式管理,极大地方便了用户对应用程序图标的管理操作。(String), US14/382592(String), 1336924800(Integer), US9952741B2(String), 1524499200(Integer), 1524499200(Integer), 美国(String), 3(Integer), 4(Integer), CN(String), 4(Integer), 15(Integer), CN102236525A | CN102306080A | CN102306084A | CN102360266A | CN102364438A | EP2426898A2 | US20040155907A1 | US20070050811A1 | US20100333030A1 | US20110258582A1 | US20120052918A1 | US5544302A | US7068288B1 | US7350158B2 | US7693877B1(String), \20230420\2ab163434aca477098f96e0e96436fa6.png(String), 8(Integer), 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 1. A method for application icon management in a mobile terminal, comprising:presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;receiving an object moving instruction;determining, according to the object moving instruction, an object to be moved to be a class of applications or an icon of an application;acquiring information on a rule graph corresponding to the object to be moved according to the object moving instruction, by:in response to determining the object to be moved to be the class of the applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens;in response to determining the object to be moved to be the icon of the application, acquiring information on a double-layer annular graph marked with the sequence numbers of the screens and classes of applications;calculating space remaining in each of the screens;comparing the space remaining in the each of the screens with space to be occupied by the object to be moved;displaying the information on the rule graph, by:in response to determining the object to be moved to be the class of the applications, displaying the single-layer annular graph marked with the sequence numbers of the screens, by showing a sequence number of a screen in bright yellow when there is enough space remaining in the screen for storing icons of the applications belonging to the class of the applications, and showing the sequence number of the screen in black when the screen does not have sufficient free space for storing the icons of the applications belonging to the class of the applications;in response to determining the object to be moved to be the icon of the application, displaying the double-layer annular graph marked with the sequence numbers of the screens and the classes of applications, by showing a sequence number of a screen and any class of applications in the screen in bright yellow when there is enough space remaining in the screen for storing the icon of the application, and showing the sequence number of the screen and the any class of applications in the screen in black when the screen does not have sufficient free space for storing the icon of the application;after the class of the applications is moved to and released in an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen is shown in bright yellow;or, after the icon of the application is moved to and released in an area containing a sequence number of a target screen or an area containing a target class of applications contained in a target screen in the double-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen or the target class of applications is shown in bright yellow;in response to determining that there is enough space remaining in the target screen for storing the object to be moved, highlighting the area containing the sequence number of the target screen or the area containing the target class of applications, indicating that the object to be moved is moved successfully;updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move;when no object is moved within a preset period of time, cancelling display of the rule graph.(String), 1、一种移动终端应用图标管理方法,包括:预先设置应用所属类别信息,建立应用类别、屏幕、应用之间的映射关系表;接收物体移动指令;根据对象移动指令确定待移动对象为应用类别或应用图标;根据物体移动指令获取待移动物体对应的规则图信息,通过:响应于确定移动对象为应用类别,获取单层环状图信息,该环状图标有屏幕序号;响应于确定移动对象为应用程序的图标,获取标记有应用程序的屏幕序号和类别的双层环形图信息;计算每个屏幕中剩余的空间;将每个屏幕中剩余的空间与要移动的对象占用的空间进行比较;通过以下方式在规则图上显示信息:响应确定移动对象为应用类别,显示单层环状图,标记屏幕序号,当剩余空间足够时,将屏幕序号显示为亮黄色在用于存储属于应用程序类别的应用程序图标的屏幕中,当屏幕没有足够的可用空间用于存储属于应用程序类别的应用程序图标时,以黑色显示屏幕序号;响应于确定待移动对象为应用程序的图标,通过显示屏幕序号和任意类别,显示标记有屏幕序号和应用程序类别的双层环形图当屏幕中有足够的剩余空间用于存储应用程序的图标时,屏幕中的应用程序以亮黄色显示,当屏幕没有足够的空间时,以黑色显示屏幕的序列号和屏幕中的任何类别的应用程序用于存储应用程序图标的可用空间;在单层环形图中将应用类移动到包含目标屏幕序号的区域释放后,判断目标屏幕是否剩余足够的空间用于存储移动对象,通过检测目标屏幕的序号是否显示为亮黄色;或者,应用程序的图标移动到双层环图中包含目标屏幕序号的区域或包含目标屏幕包含的应用程序的目标类的区域并释放后,判断是否有通过检测目标屏幕或目标应用类别的序号是否显示为亮黄色,在目标屏幕中剩余足够的空间用于存储待移动的对象;响应于确定目标屏幕中有足够的剩余空间用于存储待移动对象,突出显示包含目标屏幕序号的区域或包含目标应用类别的区域,指示待移动对象移动成功;在将待移动对象成功移动到规则图上的区域后,根据移动更新应用类、屏幕、应用之间的映射关系表;当在预设时间内没有物体移动时,取消显示规则图。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 2. The method according to claim 1, wherein the establishing a table of mapping relation among a class of applications, a screen, and an application comprises:respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.(String), 2.根据权利要求1所述的方法,其中建立一类应用、屏幕、应用之间的映射关系表包括:分别建立一类应用程序到屏幕的映射表、一类应用程序到一类应用程序的映射表和一类应用程序到屏幕的映射表。屏幕中的应用程序类别。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 3. The method according to claim 2, wherein the updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move comprises:after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on a current screen and application class layout displayed on the target screen; orafter the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen.(String), 3.根据权利要求2所述的方法,其中将待移动对象成功移动到规则图上的区域后,根据移动更新一类应用程序、屏幕、应用程序的映射关系表包括:当待移动类应用成功移动到单层环形图中目标屏幕序号所在区域后,更新类应用到屏幕的映射表。刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局;或者应用的待移动图标被成功移动到双层环图中目标屏幕或目标应用类的序号区域后,更新应用到类应用的映射表,或将应用程序映射到屏幕的表;刷新当前屏幕上显示的应用程序图标布局和目标屏幕上显示的应用程序图标布局。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 4. The method according to claim 2, further comprising: after the presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application,updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application.(String), 4.根据权利要求2所述的方法,还包括:在预先设置应用所属类别的信息,并建立应用类别、屏幕和应用之间的映射关系表之后,根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 5. A mobile terminal, comprising:a processor; andmemory storing instructions executable by the processor,wherein the processor isconfigured for:presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;receiving an object moving instruction;determining, according to the object moving instruction, an object to be moved to be a class of applications or an icon of an application;acquiring information on a rule graph corresponding to the object to be moved according to the object moving instruction, by:in response to determining the object to be moved to be the class of the applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens;in response to determining the object to be moved to be the icon of the application, acquiring information on a double-layer annular graph marked with the sequence numbers of the screens and classes of applications;calculating space remaining in each of the screens;comparing the space remaining in the each of the screens with space to be occupied by the object to be moved;displaying the information on the rule graph, by:in response to determining the object to be moved to be the class of the applications, displaying the single-layer annular graph marked with the sequence numbers of the screens, by showing a sequence number of a screen in bright yellow when there is enough space remaining in the screen for storing icons of the applications belonging to the class of the applications, and showing the sequence number of the screen in black when the screen does not have sufficient free space for storing the icons of the applications belonging to the class of the applications;in response to determining the object to be moved to be the icon of the application, displaying the double-layer annular graph marked with the sequence numbers of the screens and the classes of applications, by showing a sequence number of a screen and any class of applications in the screen in bright yellow when there is enough space remaining in the screen for storing the icon of the application, and showing the sequence number of the screen and the any class of applications in the screen in black when the screen does not have sufficient free space for storing the icon of the application;after the class of the applications is moved to and released in an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen is shown in bright yellow;or, after the icon of the application is moved to and released in an area containing a sequence number of a target screen or an area containing a target class of applications contained in a target screen in the double-layer annular graph, determining whether there is enough space remaining in the target screen for storing the object to be moved, by detecting whether the sequence number of the target screen or the target class of applications is shown in bright yellow;in response to determining that there is enough space remaining in the target screen for storing the object to be moved, highlighting the area containing the sequence number of the target screen or the area containing the target class of applications, indicating that the object to be moved is moved successfully;updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move;when no object is moved within a preset period of time, cancelling display of the rule graph.(String), 5.移动终端,包括:处理器;和存储器存储处理器可执行的指令,其中处理器是配置为:预先设置应用所属类别信息,建立应用类别、屏幕、应用之间的映射关系表;接收物体移动指令;根据对象移动指令确定待移动对象为应用类别或应用图标;根据物体移动指令获取待移动物体对应的规则图信息,通过:响应于确定移动对象为应用类别,获取单层环状图信息,该环状图标有屏幕序号;响应于确定移动对象为应用程序的图标,获取标记有应用程序的屏幕序号和类别的双层环形图信息;计算每个屏幕中剩余的空间;将每个屏幕中剩余的空间与要移动的对象占用的空间进行比较;通过以下方式在规则图上显示信息:响应确定移动对象为应用类别,显示单层环状图,标记屏幕序号,当剩余空间足够时,将屏幕序号显示为亮黄色在用于存储属于应用程序类别的应用程序图标的屏幕中,当屏幕没有足够的可用空间用于存储属于应用程序类别的应用程序图标时,以黑色显示屏幕序号;响应于确定待移动对象为应用程序的图标,通过显示屏幕序号和任意类别,显示标记有屏幕序号和应用程序类别的双层环形图当屏幕中有足够的剩余空间用于存储应用程序的图标时,屏幕中的应用程序以亮黄色显示,当屏幕没有足够的空间时,以黑色显示屏幕的序列号和屏幕中的任何类别的应用程序用于存储应用程序图标的可用空间;在单层环形图中将应用类移动到包含目标屏幕序号的区域释放后,判断目标屏幕是否剩余足够的空间用于存储移动对象,通过检测目标屏幕的序号是否显示为亮黄色;或者,应用程序的图标移动到双层环图中包含目标屏幕序号的区域或包含目标屏幕包含的应用程序的目标类的区域并释放后,判断是否有通过检测目标屏幕或目标应用类别的序号是否显示为亮黄色,在目标屏幕中剩余足够的空间用于存储待移动的对象;响应于确定目标屏幕中有足够的剩余空间用于存储待移动对象,突出显示包含目标屏幕序号的区域或包含目标应用类别的区域,指示待移动对象移动成功;在将待移动对象成功移动到规则图上的区域后,根据移动更新应用类、屏幕、应用之间的映射关系表;当在预设时间内没有物体移动时,取消显示规则图。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 6. The mobile terminal according to claim 5, wherein the establishing a table of mapping relation among a class of applications, a screen, and an application comprises:respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.(String), 6.根据权利要求5所述的移动终端,其中建立一类应用、屏幕、应用之间的映射关系表包括:分别建立一类应用程序到屏幕的映射表、一类应用程序到一类应用程序的映射表和一类应用程序到屏幕的映射表。屏幕中的应用程序类别。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 7. The mobile terminal according to claim 6, wherein the updating, after successfully moving the object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move comprises:after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on a current screen and application class layout displayed on the target screen; orafter the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen.(String), 7.根据权利要求6所述的移动终端,其中将待移动对象成功移动到规则图上的区域后,根据移动更新一类应用程序、屏幕、应用程序的映射关系表包括:当待移动类应用成功移动到单层环形图中目标屏幕序号所在区域后,更新类应用到屏幕的映射表。刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局;或者应用的待移动图标被成功移动到双层环图中目标屏幕或目标应用类的序号区域后,更新应用到类应用的映射表,或将应用程序映射到屏幕的表;刷新当前屏幕上显示的应用程序图标布局和目标屏幕上显示的应用程序图标布局。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:33.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186018(Integer), 8. The mobile terminal according to claim 6, wherein the processor is further configured for: after presetting the information on the class to which the application belongs, and establishing the table of mapping relation among a class of applications, a screen, and an application,updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application.(String), 8.根据权利要求6所述的移动终端,其中处理器还用于:在预先设置应用所属类别的信息,并建立应用类别、屏幕和应用之间的映射关系表之后,根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。(String), 1(Integer), 7(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.013 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.030 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.031 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186018(Integer), TECHNICAL FIELD [0001]The disclosure relates to the field of mobile terminal techniques, and in particular to a method for application icon management in a mobile terminal, and a mobile terminal. BACKGROUND [0002]With the upgrading of communication products, a mobile terminal such as a mobile phone or a Personal Digital Assistant (PDA) has become an indispensable communication tool, and various convenient and recreational applications appear on a mobile terminal. [0003]On an existing mobile terminal, icons of various applications are either displayed all in one screen or displayed in multiple screens. Although icon display by multiple screens can facilitate a user in finding an application to some extent, but an existing method for application icon management in a mobile terminal has the following disadvantages: [0004](1) display of icons of various applications is not managed by class; [0005](2) one application icon management operation can handle only one icon at a time, instead of batch management of multiple icons; [0006](3) the icon of an application can be moved only after the application is installed; [0007](4) a user can complete a move of an icon of an application only after dragging the icon to a target screen. SUMMARY [0008]In view of this, it is desired that embodiments of the disclosure provide a method for application icon management in a mobile terminal, and a mobile terminal, capable of implementing batch management and multi-mode management of icons of applications of a mobile terminal. [0009]To this end, the disclosure provides a method for application icon management in a mobile terminal, including steps of: [0010]presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application; [0011]receiving an icon object moving instruction, acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph; and [0012]updating, after successfully moving the icon object to be moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application according to the move. [0013]In an embodiment, the step of establishing a table of mapping relation among a class of applications, a screen, and an application may include a step of: [0014]respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen. [0015]In an embodiment, the steps of acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph may include steps of: [0016]when it is determined according to the icon object moving instruction that the icon object to be moved is a class of applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens, and displaying the information on the rule graph, wherein [0017]after the class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, it is determined whether there is enough space remaining in the target screen for storing the class of applications to be moved; and [0018]when there is enough space remaining in the target screen for storing the class of applications to be moved, the class of applications to be moved is moved to the area containing the sequence number of the target screen successfully. [0019]In an embodiment, the steps of acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph may include steps of: [0020]when it is determined according to the icon object moving instruction that the icon object to be moved is an icon of an application, acquiring information on a double-layer annular graph marked with sequence numbers of screens and classes of applications, and displaying the information on the rule graph, wherein [0021]after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, it may be determined whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and [0022]when there is enough space remaining in the target screen or the screen containing the target class of applications for storing the to-be-moved icon of the application, the to-be-moved icon of the application is moved to the area containing the sequence number of the target screen or the target class of applications successfully. [0023]In an embodiment, the step of updating, after successfully moving the icon object to be moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application according to the move may include steps of: [0024]after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on the current screen and application class layout displayed on the target screen; or [0025]after the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen. [0026]In an embodiment, the method may further include a step of: after the steps of presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application, [0027]updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application. [0028]The disclosure further provides a mobile terminal, including [0029]a presetting module configured for: presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application; [0030]a managing module configured for: receiving an icon object moving instruction; acquiring information on a single-layer annular graph or a double-layer annular graph according to the icon object moving instruction; and updating, after successfully moving the icon object to be moved to an area on the single-layer annular graph or the double-layer annular graph, a table of mapping relation among a class of applications, a screen, and an application according to the move; and [0031]a displaying module configured for: displaying the information on the rule graph. [0032]In an embodiment, the managing module may be further configured for: [0033]after a class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the class of applications to be moved; [0034]after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, determining whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and [0035]updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application. [0036]In an embodiment, the displaying module may be further configured for: [0037]refreshing application class layout and application icon layout displayed on a current screen and on a target screen according to the table of mapping relation among a class of applications, a screen, and an application updated by the managing module. [0038]In an embodiment, the mobile terminal may further include an installing module configured for: installing a new application; and after the new application is installed successfully, sending the managing module an icon management message corresponding to the installation, wherein [0039]the managing module may be further configured for: updating a table mapping an application to a class of applications according to the icon management message; and [0040]the displaying module may be further configured for: displaying icons of applications by class according to the table mapping an application to a class of applications updated by the managing module. [0041]With the method for application icon management in a mobile terminal according to the disclosure, icons of installed applications are managed rapidly by screen or by class on a respective rule graph, such that with the disclosure, compared with an existing method for application icon management in a mobile terminal, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user. Moreover, with the disclosure, it is possible to set in an installation phase of a new application a class to which the new application belongs, and directly manage display of the icon of the new application by class, thereby saving any icon display management after the new application is installed. BRIEF DESCRIPTION OF THE DRAWINGS [0042]FIG. 1 is a flowchart of a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0043]FIG. 2 is a flowchart of managing icon-display-by-screen by moving a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0044]FIG. 3 is a flowchart of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0045]FIG. 4 is a schematic diagram of a structure of a single-layer annular graph displayed on a current screen in case an icon object to be moved is a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0046]FIG. 5 is a schematic diagram of a structure of a double-layer annular graph displayed on a current screen in case an icon object to be moved is an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0047]FIG. 6 is a flowchart, in installing a new application, of setting a class to which the new application belongs and directly managing display of the icon of the new application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure; [0048]FIG. 7 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure; and [0049]FIG. 8 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure. [0050]Implementation, features, and advantages of the disclosure will be further described with reference to accompanying drawings in combination with embodiments. DETAILED DESCRIPTION [0051]According to embodiments of the disclosure, information on a class to which an application belongs is preset, and a table of mapping relation among a class of applications, a screen, and an application is established; an icon object moving instruction is received, information on a rule graph corresponding to an icon object to be moved is acquired according to the icon object moving instruction, and the information on the rule graph is displayed; and after the icon object to be moved is successfully moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application is updated according to the move. [0052]A technical solution of the disclosure will be further elaborated with reference to the accompanying drawings in combination with specific embodiments. It should be understood that the specific embodiments described herein are only used to interpret the disclosure instead of limiting the disclosure. [0053]FIG. 1 is a flowchart of a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in FIG. 1, the method includes steps as follows. [0054]In Step S101, information on a class to which an application belongs is preset, and a table of mapping relation among a class of applications, a screen, and an application is established. [0055]In an embodiment, in addition to a default class of applications in a mobile terminal, a new class of applications may be added, and an existing class of applications may be modified or deleted through an application class customizing interface. Then, a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen are established respectively in advance according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen. [0056]The table mapping a class of applications to a screen (Class_Screen) indicates mapping relation between a class of applications and a screen of the mobile terminal (i.e., table Class_Screen hereafter). [0057]The table mapping an application to a class of applications (App_Class) indicates mapping relation between an application and a class of applications (i.e., table App_Class hereafter). [0058]The table mapping an application to a screen (App_Screen) indicates mapping relation between an application and a screen of the mobile terminal ((i.e., table App_Screen hereafter), where an application with its icon stored in the screen is not classified. Main fields of the table Class_Screen are as shown in Table 1, main fields of the table App_Class are as shown in Table 2, and main fields of the table App_Screen are as shown in Table 3. [0059]TABLE 1Fielddescriptiona classthe class contained in the screen with the sequencenumbera sequencethe sequence number of a screen in the mobilenumber of aterminalscreen [0060]TABLE 2Fielddescriptionanan application belonging to the class of applicationsapplicationa classa class of applications contained in a screen of themobile terminal [0061]TABLE 3Fielddescriptionan applicationan unclassified applicationa sequencethe sequence number of a screen in the mobilenumber of a screenterminal [0062]In Step S102, an icon object moving instruction is received, information on a rule graph corresponding to an icon object to be moved is acquired according to the icon object moving instruction, and the information on the rule graph is displayed. [0063]In an embodiment, when it is determined according to the icon object moving instruction that the icon object to be moved is a class of applications, information on a single-layer annular graph marked with sequence numbers of screens is acquired, and the single-layer annular graph is displayed on a current screen. When it is determined according to the icon object moving instruction that the icon object to be moved is an icon of an application, information on a double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and the double-layer annular graph is displayed on a current screen. [0064]In Step S103, after the icon object to be moved is moved successfully to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application is updated according to the move. [0065]In an embodiment, after the icon object to be moved is moved successfully to the area on the rule graph, the table mapping a class of applications to a screen, the table mapping an application to a class of applications, or the table mapping an application to a screen may be updated. [0066]With the method for application icon management in a mobile terminal according to the disclosure, icons of installed applications are managed rapidly by screen or by class on a respective rule graph, such that with the disclosure, compared with an existing method for application icon management in a mobile terminal, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user. [0067]FIG. 2 is a flowchart of managing icon-display-by-screen by moving a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in FIG. 2, the flow of managing icon-display-by-screen by moving a class of applications according to the disclosure includes steps as follows. [0068]In Step S201, an icon object is moved. [0069]In an embodiment, after information on a class to which an application belongs is preset in the mobile terminal, and a table of mapping relation among a class of applications, a screen, and an application is established, an icon object of a class of applications or an icon of an application is dragged into a target screen or a target class of applications. [0070]In Step S202, it is determined according to an icon object moving instruction whether the icon object is a class of applications or an icon of an application. [0071]In an embodiment, when the icon object is moved, the type of the icon object (a class of applications or an icon of an application) needs to be determined in the first place according to the icon object moving instruction, and when the icon object is a class of applications, the flow goes to step S203. [0072]In Step S203, information on a single-layer annular graph marked with sequence numbers of screens is acquired; and space remaining in each screen is calculated and compared with space to be occupied by the class of applications. [0073]In an embodiment, when it is determined that the icon object is a class of applications, information on a single-layer annular graph marked with sequence numbers of screens is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the class of applications. Here, the information on the single-layer annular graph may include a total size of the graph, a total number of screens in the mobile terminal, size of an area containing a sequence number of a screen, an identifier of a color of an area, an identifier of a color of storage space occupied by each class of applications and icons of applications belonging to the each class in a screen, and the like. [0074]In Step S204, the single-layer annular graph marked with sequence numbers of screens is displayed on a current screen. [0075]In an embodiment, the single-layer annular graph displayed here, as shown in FIG. 4, includes 4 screens with sequence numbers 1, 2, 3, 4, respectively; and areas containing the sequence numbers of screens may be distinguished from each other by color. When there is enough space remaining in a screen, as calculated by the mobile terminal, for storing icons of all applications belonging to the class of applications, the sequence number of the screen is shown in bright yellow. When the screen does not have sufficient free space, as calculated by the mobile terminal, for storing icons of applications belonging to the class of applications, the sequence number of the screen is shown in black. Here, sequence numbers of screens 1, 3, 4 are shown in bright yellow, indicating that each of screen 1, screen 3, and screen 4 has sufficient free space for storing icons of all applications belonging to the class of applications. The sequence number of screen 2 is shown in black, indicating that the screen 2 has insufficient free space for storing icons of all applications belonging to the class of applications. [0076]In Step S205, the class of applications is moved into an area containing a sequence number of a target screen in the single-layer annular graph, and is then released. [0077]In Step S206, it is determined whether there is enough space remaining in the target screen for storing the class of applications; if there is, the flow goes to step S207; otherwise if there is insufficient space, the flow goes to Step S211. [0078]In an embodiment, it is detected whether the sequence number of the target screen is shown in a bright yellow font. If the sequence number of the target screen is shown in a bright yellow font, it means that there is enough space remaining in the target screen for storing the class of applications. Otherwise if the sequence number of the target screen is not shown in a bright yellow font, it means that space remaining in the target screen is insufficient for storing the class of applications, and a user may be notified that space remaining in the target screen is insufficient for storing the class of applications. [0079]As shown in FIG. 4, sequence numbers of screens 1, 3, 4 are shown in a bright yellow font, and the sequence number of screen 2 is shown in a black font. A class of applications in the screen 1 can be moved to the area containing the sequence number 4 or the area containing the sequence number 3, but can not be moved to the area containing the sequence number 2. [0080]In Step S207, the area containing the sequence number of the target screen in the single-layer annular graph is highlighted. [0081]In an embodiment, for example, as shown in FIG. 4, if a class of applications in the screen with sequence number 1 is moved to the area containing the sequence number 4, then the area containing the sequence number 4 will be highlighted, indicating that the class of applications is moved successfully. [0082]In Step S208, information on the area containing the sequence number of the target screen is recorded, an icon management message corresponding to the move of the class of applications is sent, and a table Class_Screen is updated. [0083]In an embodiment, after the class of applications is moved successfully, information on the area containing the sequence number of the target screen is recorded, and an icon management message is sent to a managing module of the mobile terminal. The icon management message includes an icon management type MsgType 2, indicating that the current moving operation involves move of a class of applications. After receiving the icon management message, the managing module updates the table Class_Screen, that is, updates the mapping relation between a class of applications and a screen. [0084]In Step S209, application class layout displayed on the current screen and application class layout displayed on the target screen are refreshed. [0085]In an embodiment, displayed layout of any class of applications on the current screen and on the target screen, and of icons of applications belonging to the any class of applications, are refreshed according to the table Class_Screen updated in step S208. [0086]In Step S210, display of the single-layer annular graph is cancelled. [0087]In an embodiment, when no class of applications is moved within a preset period of time, display of the single layer annular graph is cancelled. [0088]In Step S211, a user is notified that space remaining in the target screen is insufficient for storing the class of applications. [0089]If it is determined in Step S206 that space remaining in the target screen is insufficient for storing the class of applications, a notification that space remaining in the target screen is insufficient for storing the class of applications is provided on the current screen. [0090]FIG. 3 is a flowchart of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in FIG. 3, the flow of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application according to the disclosure includes steps as follows. [0091]In Step S301, an icon object is moved. [0092]In an embodiment, after information on a class to which an application belongs is preset in the mobile terminal, and a table of mapping relation among a class of applications, a screen, and an application is established, an icon object of a class of applications or an icon of an application is dragged into a target screen or a target class of applications. [0093]In Step S302, it is determined according to an icon object moving instruction whether the icon object is a class of applications or an icon of an application. [0094]In an embodiment, when the icon object is moved, the type of the icon object (a class of applications or an icon of an application) needs to be determined in the first place according to the icon object moving instruction, and when the icon object is an icon of an application, the flow goes to step S303. [0095]In Step S303, information on a double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the icon of the application. [0096]In an embodiment, when it is determined that the icon object is an icon of an application, information on the double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the icon of the application. [0097]Here, the information on the double-layer annular graph may include: a total size of the graph; a total number of screens in the mobile terminal; any class of applications already in each screen, and a number of classes of applications already in each screen; size of an area containing a class of applications; size of an area containing a sequence number of a screen; an identifier of a color of an area, an identifier of a color of storage space occupied by any class of applications and icons of applications belonging to the class in a screen, and the like. [0098]In Step S304, the double-layer annular graph marked with sequence numbers of screens and classes of applications is displayed on a current screen. [0099]In an embodiment, the double-layer annular graph displayed here, as shown in FIG. 5, includes four classes of applications, namely, everyday, office, game and system. Classes of applications displayed in a same screen occupy continuous areas in the double-layer annular graph and the continuous areas are in the same color. In an embodiment, the two classes of everyday and office are located in screen 1, the game is located in screen 2, the system is located in screen 3, and currently no icon of an application belonging to a class of applications is stored in screen 4. When there is enough space remaining in a screen, as calculated by the mobile terminal, for storing the icon of the application, the sequence number of the screen and any class of applications in the screen are shown in bright yellow. When the screen does not have sufficient free space, as calculated by the mobile terminal, for storing the icon of the application, the sequence number of the screen and any class of applications in the screen are shown in black. Here, the classes “everyday” and “office” and the sequence number “1” of the screen containing the classes “everyday” and “office” are in a bright yellow font; the class “system” and the sequence number “3” of the screen containing the class system are in a bright yellow font too; but class “game” and the sequence number “2” of the screen containing class game are in a black font. This indicates that the icon of the application may be stored in either screen 1 or screen 3, but may not be stored in screen 2, as space remaining in screen 2 is insufficient. [0100]In Step S305, the icon of the application is moved into an area containing a sequence number of a target screen or into an area containing a target class of applications in the double-layer annular graph, and is then released. [0101]In Step S306, it is determined whether the area contains the sequence number of a target screen or contains a target class of applications; If the area contains a target class of applications, the flow goes to Step S307; otherwise if the area contains the sequence number of a target screen, the flow goes to Step S313. [0102]In an embodiment, after the icon of the application is moved into an area containing a sequence number of a screen or containing a class of applications in the double-layer annular graph, and is then released, it is detected whether the area is occupied by a class of applications or a sequence number of a screen. If the area is occupied by a class of applications, the flow goes to Step S307. If the area is occupied by a sequence number of a screen, the flow goes to Step S313. [0103]As shown in FIG. 5, the icon of an application belonging to the class “system” in screen 3 may be moved to an area containing the sequence number “1” or “4”, or to an area containing the class “everyday” or “office” in screen 1 (namely, to an area with a bright yellow font); but cannot be moved to an area containing the sequence number “2” or to an area containing the class “game” (namely, cannot be moved to an area with a black font). [0104]In Step S307, it is determined whether there is enough space remaining in a screen containing the target class of applications for storing the icon of the application; if space remaining in the target screen is sufficient for storing the icon of the application, the flow goes to step S308; otherwise if space remaining in the target screen is insufficient for storing the icon of the application, the flow goes to Step S312. [0105]In an embodiment, it is detected whether the target class of applications is shown in a bright yellow font, if the target class of applications is shown in a bright yellow font, it means that there is enough space remaining for storing the icon of the application. Otherwise if the target class of applications is not shown in a bright yellow font, it means that space remaining is insufficient for storing the icon of the application. [0106]In Step S308, the area containing the target class of applications in the double-layer annular graph is highlighted. [0107]In Step S309, information on the area containing the target class of applications is recorded, and an icon management message corresponding to the move of the icon of the application is sent, and a table of mapping relation corresponding to the move of the icon of the application is updated. [0108]In an embodiment, after the icon of the application is moved successfully, the information on the area containing the target class of applications is recorded, and the icon management message corresponding to the move of the icon of the application is sent to a managing module of the mobile terminal. The icon management message includes an icon management type MsgType 3, indicating that the current moving operation involves move of an icon of an application into a target class of applications. After receiving the icon management message, the managing module of the mobile terminal checks the table App_Class to determine whether a mapping relation between the application and a class of applications exist, i.e., checks whether the application has been classified. If the application has not been classified, then the table App_Screen is called, and a mapping relation between the application and a screen in the table App_Screen is deleted; in addition, the table App_Class is called, and a mapping relation between the application and the target (String), 技术领域 [0001] 本发明涉及移动终端技术领域,尤其涉及一种移动终端中应用图标管理的方法及移动终端。 背景 [0002] 随着通讯产品的更新换代,手机、个人数字助理(Personal Digital Assistant,PDA)等移动终端已经成为不可或缺的通讯工具,各种方便、娱乐性的应用也出现在移动终端上。 [0003] 在现有的移动终端上,各种应用程序的图标要么一屏显示,要么多屏显示。 虽然多屏显示图标可以在一定程度上方便用户查找应用,但是现有的移动终端应用图标管理方法存在以下不足: [0004] (1) 各种应用的图标显示不按类管理; [0005] (2)一次应用图标管理操作一次只能处理一个图标,而不是批量管理多个图标; [0006] (3) 应用程序的图标必须在应用程序安装后才能移动; [0007] (4)用户只有将应用程序的图标拖动到目标屏幕后,才能完成对应用程序图标的移动。 概括 [0008] 有鉴于此,本发明实施例期望提供一种移动终端中的应用程序图标管理方法及移动终端,能够实现对移动终端应用程序图标的批量管理和多模式管理。 [0009] 为此,本发明提供了一种移动终端中应用图标的管理方法,包括以下步骤: [0010] 预先设置应用所属类别信息,建立应用类别、屏幕、应用之间的映射关系表; [0011] 接收图标对象移动指令,根据图标对象移动指令获取待移动图标对象对应的规则图信息,并显示规则图信息; 和 [0012] 将待移动图标对象成功移动到规则图上的区域后,根据移动更新应用类、屏幕、应用之间的映射关系表。 [0013] 在一个实施例中,建立一类应用程序、屏幕和应用程序之间的映射关系表的步骤可以包括以下步骤: [0014] 分别建立一类应用程序到屏幕的映射表、一类应用程序到一类应用程序的映射表和一类应用程序到屏幕的映射表。 屏幕中的应用程序类别。 [0015] 在一个实施例中,根据所述图标对象移动指令获取待移动图标对象对应的规则图信息,并显示所述规则图信息的步骤包括: [0016] 当根据图标对象移动指令确定待移动图标对象为一类应用时,获取标记有屏幕序号的单层环形图信息,并在规则图上显示该信息, 其中 [0017] 将待移动类应用移动到单层环形图中包含目标屏幕序号的区域后,判断目标屏幕中是否剩余足够的空间用于存储待移动类应用 感动; 和 [0018] 当目标屏幕剩余足够的空间用于存储待移动应用类别时,成功将待移动应用类别移动到包含目标屏幕序号的区域。 [0019] 在一个实施例中,根据所述图标对象移动指令获取待移动图标对象对应的规则图信息,并显示所述规则图信息的步骤包括: [0020]当根据图标对象移动指令确定待移动的图标对象为应用程序的图标时,获取标记有屏幕序号和应用程序类别的双层环形图信息,并显示该信息。 规则图,其中 [0021] 待移动的应用程序图标移动到双层环形图中包含目标屏幕或目标类应用程序序号的区域后,可以判断是否有足够的剩余空间。 目标屏幕或包含应用程序目标类的屏幕,用于存储应用程序的待移动图标; 和 [0022] 当目标屏幕或包含目标类应用程序的屏幕剩余足够的空间用于存储应用程序的待移动图标时,将该应用程序的待移动图标移动到包含序列的区域 成功的目标屏幕或目标类应用程序的数量。 [0023] 在一个实施例中,在将待移动图标对象成功移动到规则图上的区域后,根据移动更新应用类别、屏幕和应用之间的映射关系表的步骤可以包括以下步骤: 的: [0024] 当待移动类应用成功移动到单层环形图中目标屏幕序号所在区域后,更新类应用到屏幕的映射表。 刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局; 要么 [0025] 应用的待移动图标被成功移动到双层环图中目标屏幕或目标应用类的序号区域后,更新应用到类应用的映射表 ,或将应用程序映射到屏幕的表; 刷新当前屏幕上显示的应用程序图标布局和目标屏幕上显示的应用程序图标布局。 [0026] 在一个实施例中,该方法还可以包括以下步骤:在预先设置应用所属类别的信息,建立应用类别、屏幕和应用之间的映射关系表的步骤之后, [0027] 根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。 [0028] 本发明还提供一种移动终端,包括 [0029] 预设模块,用于预设应用所属类别的信息,建立应用类别、屏幕和应用之间的映射关系表; [0030] 管理模块,用于接收图标对象移动指令; 根据图标对象移动指令获取单层环状图或双层环状图的信息; 在将待移动图标对象成功移动到单层环状图或双层环状图上的区域后,根据 移动; 和 [0031] 显示模块,用于显示规则图的信息。 [0032] 在一个实施例中,管理模块还可以用于: [0033] 在将待移动类应用移动到单层环形图中包含目标屏幕序号的区域后,判断目标屏幕中是否剩余足够的空间用于存储该类待移动应用。 [0034] 待移动的应用程序图标移动到双层环图中包含目标屏幕或目标类应用程序序号的区域后,判断目标屏幕是否有足够的剩余空间或 包含应用程序目标类的屏幕,用于存储应用程序的待移动图标; 和 [0035]根据在安装新应用时预先设置的新应用所属类别的信息更新应用到应用类别的映射表。 [0036] 在一个实施例中,显示模块还可以用于: [0037] 根据管理模块更新的应用类、屏幕、应用的映射关系表,刷新当前屏幕和目标屏幕显示的应用类布局和应用图标布局。 [0038] 在一个实施例中,移动终端还可以包括安装模块,用于安装新的应用程序; 在新应用安装成功后,向管理模块发送安装对应的图标管理消息,其中 [0039] 管理模块还可以用于: 根据图标管理消息更新应用程序到应用程序类别的映射表。 和 [0040] 显示模块还可以用于: 根据管理模块更新的应用程序到应用程序类别的映射表,按类别显示应用程序的图标。 [0041] 本发明的移动终端中的应用图标管理方法,在各自的规则图上对已安装应用的图标进行分屏或分类的快速管理,与现有的应用图标管理方法相比, 通过移动终端,简化了图标管理,实现了应用程序图标的批量管理和多模式管理,大大方便了用户对应用程序图标的管理。 并且,通过本发明,可以在新应用的安装阶段设置新应用所属的类,直接按类管理新应用的图标显示,省去安装后的图标显示管理。 安装了新的应用程序。 附图的简要说明 [0042] 图1是根据本发明实施例的移动终端中应用程序图标管理方法的流程图; [0043] 图2是根据本发明实施例的移动终端中应用图标管理方法中通过移动类应用来管理分屏图标显示的流程图。 [0044] 图3是根据本发明实施例的移动终端中的应用程序图标管理方法中通过移动应用程序的图标来管理分屏显示或分类显示图标的流程图。 [0045] 图4是根据本发明实施例的移动终端应用图标管理方法中待移动图标对象为一类应用时当前屏幕显示的单层环状图的结构示意图。 披露; [0046] 图5为本发明移动终端应用图标管理方法中待移动图标对象为应用图标时当前屏幕显示的双层环状图的结构示意图 披露; [0047] 图6是根据本发明实施例的一种移动终端应用图标管理方法在安装新应用时设置新应用所属类别并直接管理新应用图标显示的流程图。 披露; [0048] 图7是根据本发明实施例的移动终端的模块化结构示意图; 和 [0049] 图8是根据本发明实施例的移动终端的模块化结构示意图。 [0050] 本发明的实施方式、特点和优点将参照附图并结合实施例作进一步说明。 详细说明 [0051]根据本发明实施例,预先设置应用所属类别的信息,建立应用类别、屏幕和应用之间的映射关系表。 接收图标对象移动指令,根据图标对象移动指令获取待移动图标对象对应的规则图信息,并显示规则图信息; 当待移动图标对象成功移动到规则图上的某个区域后,根据移动更新应用类、屏幕、应用之间的映射关系表。 [0052] 下面参照附图并结合具体实施例对本发明的技术方案作进一步详细说明。 应当理解,此处所描述的具体实施例仅仅用于解释本发明,并不用于限制本发明。 [0053] 图1是根据本发明实施例的移动终端中应用程序图标管理方法的流程图。 如图1所示,该方法包括以下步骤。 [0054] 在步骤S 101 ,预先设置应用所属类别的信息,建立应用类别、屏幕、应用之间的映射关系表。 [0055] 在一个实施例中,除了移动终端中默认的应用类之外,还可以通过应用类定制接口来增加新的类应用,以及修改或删除现有的类应用。 然后,在存储应用程序的图标时,根据从属关系,预先分别建立应用程序到屏幕的映射表、应用程序到应用程序类的映射表和应用程序到屏幕的映射表。 屏幕并在屏幕中存储一类应用程序。 [0056] 类别应用到屏幕的映射表(Class_Screen)表示类别应用与移动终端屏幕的映射关系(以下即Class_Screen表)。 [0057] 一个应用到一类应用的映射表(App_Class)表示一个应用和一类应用之间的映射关系(即下文的App_Class表)。 [0058] 应用到屏幕的映射表(App_Screen)表示应用与移动终端屏幕的映射关系(以下简称App_Screen表),其中图标存储在屏幕中的应用不做分类。 主要字段 Class_Screen表如表1所示,App_Class表主要字段如表2所示,App_Screen表主要字段如表3所示。 [0059] 表格1 场地 描述 一类 带有序列的屏幕中包含的类 数字 一个序列 手机屏幕的序号 的数量 终端 屏幕 [0060] 表 2 场地 描述 一个 属于应用程序类别的应用程序 应用 一类 屏幕中包含的一类应用程序 移动端 [0061] 表3 场地 描述 一个应用程序 未分类的申请 一个序列 手机屏幕的序号 屏数 终端 [0062] 在步骤S 102 ,接收图标对象移动指令,根据图标对象移动指令获取待移动图标对象对应的规则图信息,并显示规则图信息。 [0063] 在一个实施例中,当根据图标对象移动指令确定待移动的图标对象为一类应用时,获取标记有屏幕序号的单层环状图信息,并获取单层环状图信息。 当前屏幕显示环状图。 当根据图标对象移动指令确定待移动的图标对象为应用程序图标时,获取标记有屏幕序号和应用程序类别的双层环形图信息,得到双层环形图信息。 在当前屏幕上显示图层环状图。 [0064] 在步骤S 103 待移动图标对象成功移动到规则图上的某个区域后,根据移动更新应用类、屏幕、应用之间的映射关系表。 [0065]在一个实施例中,待移动图标对象被成功移动到规则图上的区域后,一类应用到屏幕的映射表,一应用到一类应用的映射表,或一应用映射表 屏幕可能会更新。 [0066] 本发明的移动终端中的应用图标管理方法,在各自的规则图上对已安装应用的图标进行分屏或分类的快速管理,与现有的应用图标管理方法相比, 通过移动终端,简化了图标管理,实现了应用程序图标的批量管理和多模式管理,大大方便了用户对应用程序图标的管理。 [0067] 图2是根据本发明实施例的移动终端中应用图标管理方法中通过移动类应用来管理分屏图标显示的流程图。 如图2所示,本发明移动类应用管理分屏图标显示的流程包括以下步骤。 [0068] 在步骤S 201 , 图标对象被移动。 [0069] 在一个实施例中,在移动终端中预先设置应用所属类别的信息,并建立类别应用、屏幕和应用之间的映射关系表后,类别应用的图标对象 或者应用程序的图标被拖到目标屏幕或目标应用程序类别中。 [0070] 在步骤S 202 ,根据图标对象移动指令判断图标对象是一类应用还是应用的图标。 [0071] 在一个实施例中,在移动图标对象时,首先需要根据图标对象移动指令确定图标对象的类型(应用程序的类别或应用程序的图标),当图标对象 是一类应用程序,流程转到步骤S 203 . [0072] 在步骤S 203 , 获取单层环状图的信息, 标注有屏幕序号; 计算每个屏幕中剩余的空间,并将其与应用程序类别占用的空间进行比较。 [0073] 在一个实施例中,当确定图标对象为一类应用时,获取标记有屏幕序号的单层环状图信息,计算每个屏幕剩余空间并与待占用空间进行比较 按应用类别。 这里,单层环状图的信息可以包括图的总大小、移动终端的屏幕总数、包含屏幕序号的区域大小、区域颜色标识 、每类应用程序占用的存储空间的颜色标识、属于每类应用程序在屏幕中的图标等。 [0074] 在步骤S 204 ,当前屏幕显示单层环状图,标有屏幕序号。 [0075] 在一个实施例中,这里显示的单层环状图,如图4所示,包括4个带序号的画面 1 , 2 , 3 , 4 , 分别; 包含屏幕序号的区域可以通过颜色相互区分。 当移动终端计算出屏幕剩余空间足够存储属于该应用类别的所有应用的图标时,屏幕序号以亮黄色显示。 当移动终端计算出屏幕没有足够的空闲空间来存储属于应用程序类别的应用程序的图标时,屏幕的序号显示为黑色。 这里,屏幕的序号 1 , 3 , 4 以亮黄色显示,表示每屏 1 , 屏幕 3 , 和屏幕 4 有足够的可用空间来存储属于该应用程序类别的所有应用程序的图标。 屏幕序号 2 显示为黑色,表示该画面2 没有足够的可用空间来存储属于该应用程序类别的所有应用程序的图标。 [0076] 在步骤S 205 ,该类应用被移动到单层环状图中包含目标屏幕序号的区域,然后被释放。 [0077] 在步骤S 206 ,判断目标屏幕是否有足够的剩余空间用于存储应用程序的类别; 如果存在,则流程转到步骤S 207 ; 否则如果空间不足,则流程转到步骤S 211 . [0078] 在一个实施例中,检测目标屏幕的序号是否以亮黄色字体显示。 如果目标屏幕的序列号以亮黄色字体显示,则表示目标屏幕中有足够的剩余空间来存储应用程序的类别。 否则,如果目标屏幕的序号没有以亮黄色字体显示,则表示目标屏幕剩余空间不足以存储应用类别,可以提示用户目标屏幕剩余空间不足。 不足以存储应用程序的类别。 [0079] 如图4所示,屏幕序号 1 , 3 , 4 以亮黄色字体显示,屏幕序号 2 以黑色字体显示。 屏幕中的一类应用 1 可以移动到包含序列号的区域 4 或包含序列号的区域 3 , 但不能移动到包含序号的区域 2 . [0080] 在步骤S 207 , 单层环形图中包含目标屏幕序号的区域高亮显示。 [0081] 在一个实施例中,例如,如图4所示,如果一类应用程序在屏幕中带有序号 1 被移动到包含序列号的区域 4 ,然后是包含序列号的区域 4 会高亮显示,表示该类应用迁移成功。 [0082] 在步骤S 208 ,记录包含目标屏幕序号的区域信息,发送应用类移动对应的图标管理消息,更新表Class_Screen。 [0083] 在一个实施例中,应用类别移动成功后,记录目标屏幕序号所在区域的信息,并向移动终端的管理模块发送图标管理消息。 图标管理消息包括图标管理类型MsgType 2,表示当前移动操作涉及一类应用程序的移动。 管理模块收到图标管理消息后,更新Class_Screen表,即更新一类应用程序与屏幕的映射关系。 [0084] 在步骤S 209 ,刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局。 [0085] 在一个实施例中,根据步骤S更新的表Class_Screen,刷新当前屏幕和目标屏幕上任意类应用程序的显示布局,以及属于任意类应用程序的图标。 208 . [0086] 在步骤S 210 , 取消单层环形图的显示。 [0087] 在一个实施例中,当在预设时间内没有类应用移动时,取消单层环形图的显示。 [0088] 在步骤S 211 ,通知用户目标屏幕中剩余的空间不足以存储应用程序的类别。 [0089] 如果在步骤S中确定 206 当目标屏幕剩余空间不足以存储应用类别时,在当前屏幕提示目标屏幕剩余空间不足以存储应用类别。 [0090]图3是根据本发明实施例的移动终端中应用程序图标管理方法中通过移动应用程序图标来管理分屏显示或分类显示图标的流程图。 如图3所示,本发明通过移动应用程序的图标来管理分屏或分屏图标显示的流程包括以下步骤。 [0091] 在步骤S 301 , 图标对象被移动。 [0092] 在一个实施例中,在移动终端中预先设置应用所属类别的信息,并建立类别应用、屏幕和应用之间的映射关系表后,类别应用的图标对象 或者应用程序的图标被拖到目标屏幕或目标应用程序类别中。 [0093] 在步骤S 302 ,根据图标对象移动指令判断图标对象是一类应用还是应用的图标。 [0094] 在一个实施例中,在移动图标对象时,首先需要根据图标对象移动指令确定图标对象的类型(应用程序的类别或应用程序的图标),当图标对象 为应用程序图标,转步骤S 303 . [0095] 在步骤S 303 ,获取标记有屏幕序号和应用类别的双层环形图信息,计算每个屏幕的剩余空间,并与应用图标占用的空间进行比较。 [0096] 在一个实施例中,当确定图标对象为应用程序的图标时,获取标记有屏幕序号和应用程序类别的双层环形图的信息,计算并比较各屏幕的剩余空间。 应用程序图标占用的空间。 [0097] 这里,双层环形图的信息可以包括: 图的总大小; 移动终端的屏幕总数; 每个屏幕中已有的任何类别的应用程序,以及每个屏幕中已有的多个类别的应用程序; 包含一类应用程序的区域的大小; 包含屏幕序列号的区域的大小; 区域颜色的标识、屏幕中任意类应用程序和属于该类应用程序的图标所占用的存储空间的颜色标识等。 [0098] 在步骤S 304 ,当前屏幕显示双层环状图,标有屏幕序号和应用类别。 [0099] 在一个实施例中,这里显示的双层环形图,如图5所示,包括日常、办公、游戏和系统四类应用。 同屏显示的应用类别在双层环状图中占据连续区域,连续区域颜色相同。 在一个实施例中,日常和办公两个类位于屏幕中 1 , 游戏位于屏幕 2 , 系统位于屏幕 3 , 目前屏幕上没有存储属于一类应用程序的图标 4 . 当移动终端计算出屏幕中有足够的剩余空间用于存储应用程序的图标时,屏幕的序号和屏幕中的任何类别的应用程序都以亮黄色显示。 当移动终端计算出屏幕没有足够的可用空间来存储应用程序的图标时,屏幕的序号和屏幕中的任何类别的应用程序都以黑色显示。 在这里,类别“日常”和“办公室”以及序列号“ 1 包含“日常”和“办公室”类的屏幕的“”为亮黄色字体; 类“系统”和序列号“ 3 包含班级系统的屏幕也是亮黄色字体; 但是类“游戏”和序列号“ 2 包含类游戏的画面为黑色字体。 这表明应用程序的图标可能存储在任一屏幕中 1 或屏幕 3, 但可能不会存储在屏幕中 2 , 作为屏幕剩余空间 2 是不够的。 [0100] 在步骤S 305 ,将应用程序的图标移动到双层环形图中包含目标屏幕序号的区域或包含目标类应用程序的区域,然后释放。 [0101] 在步骤S 306 ,判断该区域是否包含目标屏幕序号或包含目标类应用; 如果该区域包含目标类别的应用程序,则流程转到步骤 S 307 ; 否则,如果该区域包含目标屏幕的序号,则流程转到步骤S 313 . [0102] 在一个实施例中,将应用程序的图标移动到双层环形图中包含屏幕序号或某类应用程序的区域释放后,检测该区域是否被占用 一类应用程序或屏幕的序列号。 如果该区域被一类应用占用,则流程转到步骤S 307 . 如果该区域被屏幕序号占用,则流程进入步骤S 313 . [0103] 如图5所示,属于“系统”类的应用程序在屏幕中的图标 3 可以移动到包含序列号“ 1 “ 要么 ” 4 ”,或屏幕中包含“日常”或“办公室”类的区域 1 (即到亮黄色字体的区域); 但不能移动到包含序列号“ 2 ”或包含类“游戏”的区域(即不能移动到黑色字体的区域)。 [0104] 在步骤S 307 ,判断包含目标类应用程序的屏幕中是否剩余足够的空间用于存储应用程序的图标; 如果目标屏幕剩余空间足以存储应用程序的图标,则流程进入步骤S 308 ; 否则如果目标屏幕剩余空间不足以存储应用程序的图标,则流程进入步骤S 312 . [0105] 在一个实施例中,检测目标类应用程序是否显示为亮黄色字体,如果目标类应用程序显示为亮黄色字体,则表示该应用程序的图标有足够的剩余空间存储。 . 否则,如果目标类别的应用程序没有以亮黄色字体显示,则表示剩余空间不足以存储该应用程序的图标。 [0106] 在步骤S 308 ,双层环形图中包含目标类应用程序的区域被突出显示。 [0107] 在步骤S 309 ,记录目标类应用所在区域的信息,发送应用图标移动对应的图标管理消息,更新应用图标移动对应的映射关系表 . [0108]在一个实施例中,应用程序的图标移动成功后,记录目标类应用程序所在区域的信息,并将应用程序图标移动对应的图标管理消息发送给管理模块。 移动终端。 图标管理消息包括图标管理类型MsgType 3,表示当前移动操作涉及将应用程序的图标移动到目标类应用程序中。 移动终端的管理模块接收到图标管理消息后,查询App_Class表,判断该应用是否存在与应用类别的映射关系,即查询该应用是否已经分类。 如果还没有对应用进行分类,则调用表App_Screen,删除表App_Screen中的应用与屏幕的映射关系; 另外,调用App_Class表,在App_Class表中增加应用程序与应用程序目标类的映射关系。 之前对应用进行分类时,调用表App_Class,更新应用与应用类别的映射关系。 [0109] 在步骤S 310 ,刷新当前屏幕显示的应用程序图标布局和目标屏幕显示的应用程序图标布局。 [0110] 在一个实施例中,根据步骤S更新的表格刷新当前屏幕显示的应用程序图标布局和目标屏幕显示的应用程序图标布局。 309 . [0111] 在步骤S 311 , 取消双层环状图的显示。 [0112] 在一个实施例中,当在预设时间内没有移动应用程序图标时,取消显示双层环形图。 [0113] 在步骤S 312 ,通知用户包含目标类应用程序的屏幕中剩余的空间不足以存储应用程序的图标。 [0114] 在一个实施例中,如果在步骤S中确定 307 包含目标类应用程序的屏幕中剩余空间不足以存储应用程序的图标,则在包含目标类应用程序的屏幕中剩余空间不足以存储应用程序图标的通知被提供在 当前屏幕。 [0115] 在步骤S 313 ,判断目标屏幕是否有足够的剩余空间用于存储应用程序的图标; 如果有足够的空间,则流程转到步骤 S 314 ; 否则如果目标屏幕剩余空间不足以存储应用程序的图标,则流程进入步骤S 316 . [0116] 在一个实施例中,当移动终端检测到释放应用程序图标的区域中包含屏幕序号时,判断目标屏幕中是否剩余足够的空间用于存储应用程序图标。 即检测目标屏幕的序号是否以亮黄色字体显示。 如果目标屏幕的序列号以亮黄色字体显示,则表示目标屏幕中有足够的剩余空间来存储应用程序的图标。 否则,如果目标屏幕的序号没有以亮黄色字体显示,则表示目标屏幕剩余空间不足以存储应用程序的图标。 [0117] 在步骤S 314 , 双层环形图中包含目标屏幕序号的区域被高亮显示。 [0118] 在步骤S 315 ,记录包含目标屏幕序号的区域信息,发送应用程序图标移动对应的图标管理消息,应用程序图标移动对应的映射关系表 已更新。 [0119]在一个实施例中,应用程序的图标移动成功后,记录目标屏幕序号所在区域的信息,并向管理端发送应用程序图标移动对应的图标管理消息。 移动端模块。 图标管理消息包括图标管理类型MsgType 4,表示当前移动操作涉及将应用程序的图标移动到目标屏幕中。 移动终端的管理模块接收到图标管理消息后,查询App_Class表,判断该应用是否存在与应用类别的映射关系,即查询该应用是否已经分类。 如果应用没有分类,则调用表App_Screen,更新应用与屏幕的映射关系; 之前对应用进行分类时,调用表App_Class,删除应用与表App_Class中任意类应用的映射关系,调用表App_Screen增加应用与目标屏幕的映射关系 在表 App_Screen 中。 然后根据更新后的表格刷新屏幕上显示的应用类布局和应用图标布局。 当在预设时间内没有移动应用程序图标时,取消显示双层环形图。 [0120] 在步骤S 316 ,通知用户目标屏幕中剩余的空间不足以存储应用程序的图标。 [0121] 如果在步骤S中确定 313 当目标屏幕剩余空间不足以存储应用程序图标时,在当前屏幕提示目标屏幕剩余空间不足以存储应用程序图标。 [0122] 图6是根据本发明实施例的一种移动终端应用图标管理方法在安装新应用时设置新应用所属类别并直接管理新应用图标显示的流程图。 披露。 如图6所示,在安装新应用时,设置新应用所属类别,直接管理新应用图标显示的流程包括如下步骤。 [0123] 在步骤S 601 ,读取用于安装新应用程序的包文件。 [0124] 在本发明的一个实施例中,移动终端在安装新应用时,会读取用于安装新应用的打包文件,该打包文件可以包括应用的图标、安装应用的包的名称等信息。 安装应用程序所需的硬件环境。 [0125] 在步骤S 602 ,计算每个屏幕中剩余的空间。 [0126] 在步骤S 603 ,判断屏幕中是否有足够的剩余空间用于存储新应用的图标; 如果屏幕中有足够的剩余空间来存储新应用程序的图标,则流程转到步骤S 604 ; 否则,如果没有屏幕有足够的可用空间来存储新应用程序的图标,则流程转到步骤S 610 . [0127] 在步骤S 604 ,具有足够用于存储新应用程序的图标的可用空间的屏幕的序列号,以及包含在具有序列号的屏幕中的一类应用程序,被读取。 [0128] 在一个实施例中,当移动终端检测到屏幕中有足够的剩余空间用于存储新应用的图标时,移动终端将记录并读取具有足够的空闲空间用于存储新应用的图标的屏幕的序号。 应用程序和屏幕中包含的任何类别的应用程序以及序列号。 [0129] 在步骤S 605 ,显示具有足以存储新应用程序图标的可用空间的屏幕的序号,以及包含在具有序号的屏幕中的一类应用程序。 [0130]在一个实施例中,移动终端在当前屏幕上显示具有足以存储新应用程序图标的空闲空间的屏幕序号,以及带有该序号的屏幕包含的应用程序类别,以供用户选择 要安装的新应用程序的类。 [0131] 在步骤S 606 ,根据显示的应用类别选择新应用所属的应用类别,使用打包文件安装新应用。 [0132] 在步骤S 607 ,发送图标管理消息。 [0133] 在一个实施例中,图标管理消息包括安装应用程序的包的文件名、应用程序所属的类、显示应用程序的屏幕的序号和新应用程序的图标管理类型MsgType。 应用所属的类是在安装新应用时选择的类,MsgType为1,表示在安装新应用时,移动终端直接按类管理应用图标的显示。 [0134] 在步骤S 608 ,根据图标管理消息更新表App_Class。 [0135] 在一个实施例中,移动终端的管理模块根据图标管理消息调用App_Class表更新应用程序与应用程序类别的映射关系。 [0136] 在步骤S 609 ,读取App_Class表,刷新显示中属于所选应用类别的应用图标布局。 [0137] 在一个实施例中,移动终端在更新App_Class表后,读取App_Class表,刷新显示中属于所选应用类别的应用的图标布局,实现对新应用图标显示的直接管理。 [0138] 在步骤S 610 ,用户会收到无法安装新应用程序的通知。 [0139] 当检测到没有屏幕有足够的空闲空间来存放新应用的图标时,在当前屏幕提示无法安装新应用。 [0140] 本发明的移动终端中的应用图标管理方法,通过在安装新应用时设置新应用所属的类,可以直接对新应用的图标按类显示进行管理,从而节省了任何费用。 新应用安装后图标显示管理。 [0141] 图7是根据本发明实施例的移动终端的模块化结构示意图。 如图7所示,本实施例的移动终端包括: [0142] 预设模块 701 配置为:预先设置应用所属类别的信息,建立应用类别、屏幕、应用之间的映射关系表。 [0143] 一个管理模块 702 配置为:接收图标对象移动指令; 根据图标对象移动指令获取单层环状图或双层环状图的信息; 在将待移动图标对象成功移动到单层环状图或双层环状图上的区域后,根据 移动; 和 [0144] 显示模块 703 配置为:向管理模块发送图标对象移动指令 702 根据管理模块获取的单层环状图或双层环状图的信息在当前屏幕显示单层环状图或双层环状图 702 . [0145] 预置模块 701可以通过应用类定制界面在移动终端默认类应用的基础上增加新的类应用,修改或删除现有类应用。 然后,在存储应用程序的图标时,根据从属关系,预先分别建立应用程序到屏幕的映射表、应用程序到应用程序类的映射表和应用程序到屏幕的映射表。 屏幕并在屏幕中存储一类应用程序。 [0146] 与现有的移动终端中的应用程序图标管理方法相比,本实施例的移动终端在移动一类应用程序或应用程序的图标时,简化了图标管理,实现了批量管理和多模式管理。 实现了应用程序的图标,极大地方便了用户对应用程序图标的管理。 [0147] 管理模块 702 可以进一步配置为: [0148] 在将待移动类应用移动到单层环形图中包含目标屏幕序号的区域后,判断目标屏幕中是否剩余足够的空间用于存储该类待移动应用。 应用类别成功移动到单层环状图中的区域后,接收显示模块发送的图标管理消息 703 根据图标管理信息更新一类应用程序到屏幕的映射表。 [0149] 显示模块 703 可以进一步配置为: [0150] 类应用成功移动到单层环状图中的区域后,将类应用移动对应的图标管理消息发送给管理模块 702 ,根据管理模块更新的一类应用到屏幕的映射表,刷新当前屏幕显示的应用类布局和目标屏幕显示的应用类布局。 [0151] 管理模块 702 可以进一步配置为: [0152] 待移动的应用程序图标移动到双层环图中包含目标屏幕或目标类应用程序序号的区域后,判断目标屏幕是否有足够的剩余空间或 包含应用程序目标类的屏幕,用于存储应用程序的待移动图标; 将应用程序的图标成功移动到双层环形图中目标类应用程序所在的区域后,接收显示模块发送的图标管理消息 703 根据图标管理消息更新应用程序到应用程序类别的映射表; 和 [0153] 将应用的图标移动到双层环形图中目标屏幕序号所在区域成功后,接收展示模块发送的图标管理消息 703 根据图标管理信息更新应用程序到屏幕的映射表。 [0154] 显示模块 703 可以进一步配置为: [0155] 将应用程序的图标移动到双层环形图中目标类应用程序所在的区域后,向管理模块发送应用程序图标移动对应的图标管理消息 702 ,根据管理模块更新的一个应用到一类应用的映射表,刷新当前屏幕显示的应用图标布局和目标屏幕显示的应用图标布局 702 ; 和 [0156] 将应用程序的图标成功移动到双层环形图中包含目标屏幕序号的区域后,向管理模块发送应用程序图标移动对应的图标管理消息 702,根据管理模块更新的应用到屏幕的映射表,刷新当前屏幕显示的应用图标布局和目标屏幕显示的应用图标布局 702 . [0157] 管理模块 702 可以进一步配置为: [0158] 通知显示模块 703 如果在预设时间内没有检测到图标对象移动操作,则取消单层环状图或双层环状图的显示。 [0159] 图8是根据本发明实施例的移动终端的模块化结构示意图。 如图8所示,在上一实施例的移动终端的基础上,本实施例的移动终端还包括: [0160] 一个安装模块 804 配置为安装新的应用程序。 [0161] 具体来说,安装模块 804 可以进一步配置为: [0162] 安装新应用时,根据预置模块预置的应用所属类别信息,确定新应用所属类别 801 表Class_Screen、表App_Class和表App_Screen,将应用安装对应的图标管理消息发送给管理模块 802 通知管理模块 802 更新表 App_Class。 [0163] 管理模块 802 可以进一步配置为: [0164] 接收安装模块发送的图标管理消息 804 更新App_Class表,即根据新应用安装时预先设置的类信息(选择新应用所属的类)。 [0165] 显示模块 803 可以进一步配置为: [0166] 新应用安装完成后,根据安装时选择的类,按类显示新应用的图标。 [0167] 与现有的移动终端中的应用程序图标管理方法相比,本实施例的移动终端在移动一类应用程序或应用程序的图标时,简化了图标管理,实现了批量管理和多模式管理。 实现了应用程序的图标,极大地方便了用户对应用程序图标的管理。 并且,本实施例的移动终端,可以在新应用的安装阶段设置新应用所属的类,直接按类管理新应用的图标显示,从而节省 新应用安装后任意图标显示管理。 [0168] 所描述的仅为本发明的实施例而已,并不用于限定本发明的保护范围。 凡使用本发明的说明书及附图所做的等效结构和流程改动,或者将本发明直接或间接应用于其他相关技术领域,均应包含在本发明的保护范围之内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.077 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.078 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN103309554A(String), CN103309554B(String), EP2824552A1(String), EP2824552A4(String), EP2824552B1(String), US20150026617A1(String), US9952741B2(String), WO2013131321A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.232 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.233 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN103309554A(String), CN103309554B(String), EP2824552A1(String), EP2824552A4(String), EP2824552B1(String), US20150026617A1(String), US9952741B2(String), WO2013131321A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.250 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9952741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.285 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.286 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN103309554A(String), CN103309554B(String), EP2824552A1(String), EP2824552A4(String), EP2824552B1(String), US20150026617A1(String), US9952741B2(String), WO2013131321A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.304 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.305 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), CN103309554A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.339 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.340 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), CN103309554B(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.375 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), EP2824552A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.410 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), EP2824552A4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.445 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.446 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), EP2824552B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.480 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), US20150026617A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.515 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), US9952741B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.551 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271686(Integer), WO2013131321A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.586 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.587 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9952741B2(String), US9952741B2(String), 1524499200(Integer), 271686(Integer), 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.622 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: ZTE CORPORATION(String), LIANG, XIAOHUI(String), 中兴通讯股份有限公司(String), LIANG XIAOHUI(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.667 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: ZTE CORPORATION(String), 中兴通讯股份有限公司(String), 255(String), 0(Integer), 1660813047(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.701 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186018(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.733 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.734 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 20111(Integer), 1(Integer), 186018(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Preparing: INSERT INTO os_patent_applicant ( name, bname, uid, update_time, type, `merge` ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.769 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert ==> Parameters: LIANG, XIAOHUI(String), LIANG XIAOHUI(String), 0(Integer), 1681976194(Integer), 2(Integer), false(Boolean) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186018(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 75866(Integer), 2(Integer), 186018(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.875 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 20111(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.909 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.910 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75866(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.927 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.928 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.979 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.980 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.997 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:34.998 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186018(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.187 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.188 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.531 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.532 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal having smart card coupled with RFID tag and method for performing RFID function in such mobile terminal(String), 具有与RFID标签耦合的智能卡的移动终端以及在这种移动终端中执行RFID功能的方法(String), US7374100B2(String), Disclosed is a mobile terminal equipped with a smart card coupled with an RFID tag and a method for performing an RFID function in the mobile terminal. The smart card includes a user information processing section for storing user information and generating a user information signal including user information, an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data, and a main calculating section connected to the user information processing section in order to control a generation and a transmission of the user information signal and connected to the RFID information processing section order to command a generation and a transmission of the RFID signal. When the RFID tag detects an approach of an RFID interrogator, the RFID tag requests a CPU of the smart card to perform the RFID function. Thus, the CPU of the smart card transmits a mode transition signal to a processor of the mobile terminal in order to indicate a mode transition into an RFID mode. Then, the RFID function is carried out.(String), 公开了一种配备有与RFID标签耦合的智能卡的移动终端以及在移动终端中执行RFID功能的方法。 智能卡包括:用户信息处理部分,用于存储用户信息并生成包含用户信息的用户信息信号;RFID信息处理部分,用于存储RFID数据并生成包含RFID数据的RFID信号;以及主计算部分,连接到智能卡。 用户信息处理部分为了控制用户信息信号的生成和传输并且连接到RFID信息处理部分以命令RFID信号的生成和传输。 当RFID标签检测到RFID询问器的接近时,RFID标签请求智能卡的CPU执行RFID功能。 因此,智能卡的CPU向移动终端的处理器发送模式转换信号以指示模式转换到RFID模式。 然后,执行RFID功能。(String), US10/970102(String), 1098288000(Integer), US7374100B2(String), 1211212800(Integer), 1211212800(Integer), 美国(String), 4(Integer), KR(String), 5(Integer), 25(Integer), EP1522955A1 | JP1998098542A | JP2002247157A | KR1020020040455A | US20010004236A1 | US20020002534A1 | US20020165780A1 | US20030006280A1 | US20040016796A1 | US20040059884A1 | US20040121793A1 | US20040203352A1 | US4075632A | US4360810A | US4739328A | US4782345A | US4786907A | US4816839A | US4835377A | US4853705A | US5394439A | US5640002A | US5991749A | US6775632B1(String), 20(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.569 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186019(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.713 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.714 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\d1fb907f13bb41a69ee33c8450982b99.png(String), 186019(Integer), d1fb907f13bb41a69ee33c8450982b99.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.749 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.766 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.767 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal having smart card coupled with RFID tag and method for performing RFID function in such mobile terminal(String), 具有与RFID标签耦合的智能卡的移动终端以及在这种移动终端中执行RFID功能的方法(String), US7374100B2(String), Disclosed is a mobile terminal equipped with a smart card coupled with an RFID tag and a method for performing an RFID function in the mobile terminal. The smart card includes a user information processing section for storing user information and generating a user information signal including user information, an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data, and a main calculating section connected to the user information processing section in order to control a generation and a transmission of the user information signal and connected to the RFID information processing section order to command a generation and a transmission of the RFID signal. When the RFID tag detects an approach of an RFID interrogator, the RFID tag requests a CPU of the smart card to perform the RFID function. Thus, the CPU of the smart card transmits a mode transition signal to a processor of the mobile terminal in order to indicate a mode transition into an RFID mode. Then, the RFID function is carried out.(String), 公开了一种配备有与RFID标签耦合的智能卡的移动终端以及在移动终端中执行RFID功能的方法。 智能卡包括:用户信息处理部分,用于存储用户信息并生成包含用户信息的用户信息信号;RFID信息处理部分,用于存储RFID数据并生成包含RFID数据的RFID信号;以及主计算部分,连接到智能卡。 用户信息处理部分为了控制用户信息信号的生成和传输并且连接到RFID信息处理部分以命令RFID信号的生成和传输。 当RFID标签检测到RFID询问器的接近时,RFID标签请求智能卡的CPU执行RFID功能。 因此,智能卡的CPU向移动终端的处理器发送模式转换信号以指示模式转换到RFID模式。 然后,执行RFID功能。(String), US10/970102(String), 1098288000(Integer), US7374100B2(String), 1211212800(Integer), 1211212800(Integer), 美国(String), 3(Integer), 4(Integer), KR(String), 5(Integer), 25(Integer), EP1522955A1 | JP1998098542A | JP2002247157A | KR1020020040455A | US20010004236A1 | US20020002534A1 | US20020165780A1 | US20030006280A1 | US20040016796A1 | US20040059884A1 | US20040121793A1 | US20040203352A1 | US4075632A | US4360810A | US4739328A | US4782345A | US4786907A | US4816839A | US4835377A | US4853705A | US5394439A | US5640002A | US5991749A | US6775632B1(String), \20230420\d1fb907f13bb41a69ee33c8450982b99.png(String), 20(Integer), 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.837 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 1. A smart card mounted on a single SIM card comprising:a user information processing section for storing user information and generating a user information signal including user information;an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data; anda main calculating section connected to the user information processing section in order to control generation and transmission of the user information signal, and connected to the RFID information processing section in order to command generation and transmission of the RFID signal.(String), 1.智能卡安装在单张SIM卡上包括:用户信息处理部分,用于存储用户信息并生成包括用户信息的用户信息信号;RFID信息处理部分,用于存储RFID数据并生成包括RFID数据的RFID信号;和主计算部分连接到用户信息处理部分以控制用户信息信号的产生和传输,并且连接到RFID信息处理部分以命令RFID信号的产生和传输。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 2. The smart card as claimed in claim 1, wherein the user information processing section includes a user information memory section for storing user information and a user program memory section including a program for generating the user information signal.(String), 2.如权利要求1所述的智能卡,其中用户信息处理部分包括用于存储用户信息的用户信息存储部分和包括用于生成用户信息信号的程序的用户程序存储部分。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 3. The smart card as claimed in claim 1, wherein the RFID information processing section includes an RFID information memory section for storing RFID information and an RFID function section for generating the RFID signal.(String), 3.如权利要求1所述的智能卡,其中RFID信息处理部分包括用于存储RFID信息的RFID信息存储部分和用于产生RFID信号的RFID功能部分。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 4. The smart card as claimed in claim 3, wherein the RFID function section includes an RFID CODEC section and an RFID modulation section.(String), 4.如权利要求3所述的智能卡,其中RFID功能部分包括RFIDCODEC部分和RFID调制部分。(String), 1(Integer), 3(Integer), 2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.838 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 5. The smart card as claimed in claim 1, wherein the user information processing section includes a user information memory section for storing user information and a user program memory section for storing a program generating a signal having the user information, and the RFID information processing section includes an RFID information memory section for storing RFID information and an RFID function section for generating the RFID signal.(String), 5.如权利要求1所述的智能卡,其中用户信息处理部分包括用于存储用户信息的用户信息存储部分和用于存储产生具有用户信息的信号的程序的用户程序存储部分,RFID信息处理部分包括用于存储RFID信息的RFID信息存储部分和RFID功能部分,用于产生RFID信号。(String), 1(Integer), 4(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 6. The smart card as claimed in claim 5, wherein the user information memory section includes the RFID information memory section.(String), 6.如权利要求5所述的智能卡,其中用户信息存储部分包括RFID信息存储部分。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 7. The smart card as claimed in claim 6, wherein the user program memory section includes the RFID function section.(String), 7.如权利要求6所述的智能卡,其中用户程序存储部分包括RFID功能部分。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 8. The smart card as claimed in claim 1, further comprising a plurality of external pins, including a power pin, a clock pin, and a data input/output pin.(String), 8.如权利要求1所述的智能卡,还包括多个外部引脚,包括电源引脚、时钟引脚和数据输入/输出引脚。(String), 1(Integer), 7(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 9. The smart card as claimed in claim 8, wherein one of the plurality of external pins is connected to an RFID antenna.(String), 9.如权利要求8所述的智能卡,其中多个外部引脚之一连接到RFID天线。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 10. The smart card as claimed in claim 9, wherein the main calculating section transmits the RFID signal to the RFID antenna connected to the smart card.(String), 10.如权利要求9所述的智能卡,其中主计算部分将RFID信号发送到连接到智能卡的RFID天线。(String), 1(Integer), 9(Integer), 8(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 11. The smart card as claimed in claim 1, further comprising an interrupt section which is connected to the main calculating section and which provides to the main calculating section an interrupt signal to indicate an RFID mode.(String), 11.如权利要求1所述的智能卡,还包括中断部分,连接到主计算部分,并向主计算部分提供中断信号以指示RFID模式。(String), 1(Integer), 10(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 12. The smart card as claimed in claim 1, further comprising a clock generator for providing RFID clocks to the RFID information processing section.(String), 12.如权利要求1所述的智能卡,还包括时钟发生器,用于向RFID信息处理部分提供RFID时钟。(String), 1(Integer), 11(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 13. The smart card as claimed in claim 12, wherein the main calculating section generates a control signal for controlling the clock generator.(String), 13.如权利要求12所述的智能卡,其中主计算部分产生用于控制时钟发生器的控制信号。(String), 1(Integer), 12(Integer), 11(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 14. The smart card as claimed in claim 1, further comprising a clock generator for providing RFID clocks to the main calculating section.(String), 14.如权利要求1所述的智能卡,还包括时钟发生器,用于向主计算部分提供RFID时钟。(String), 1(Integer), 13(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 15. A mobile terminal comprising:a smart card mounted on a single SIM card that includes a user information processing section for generating a user information signal including user information and installed in the mobile terminal for storing user information, the smart card including an RFID tag;a main calculating section connected to the user information processing section in order to control generation and transmission of the user information signal, and connected to the RFID information processing section in order to command generation and transmission of the RFID signal; anda processor in communication with the smart card so as to grant or reject an RFID function of the smart card.(String), 15.移动终端包括:智能卡安装在单个SIM卡上,包括用户信息处理部分,用于生成包含用户信息的用户信息信号,安装在移动终端中用于存储用户信息,该智能卡包括RFID标签;主计算部分,与用户信息处理部分相连,控制用户信息信号的产生和传输;与RFID信息处理部分相连,控制RFID信号的产生和传输;和处理器与智能卡通信以授予或拒绝智能卡的RFID功能。(String), 0(Integer), 14(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 16. A method for performing an RFID function in a mobile terminal equipped with a smart card mounted on a single SIM card and having an RFID tag, the method comprising:detecting an approach of an RFID interrogator by using the RFID tag;requesting a CPU of the smart card to perform the RFID function by utilizing the RFID tag;transmitting a mode transition signal to a processor of the mobile terminal by using the CPU of the smart card to indicate a mode transition into an RFID mode; andperforming the RFID function by using the smart card after transmitting the mode transition signal.(String), 16.一种用于在配备有安装在单个SIM卡上的智能卡的移动终端中执行RFID功能的方法,以及有一种RFID标签,该方法包括:通过使用RFID标签检测RFID询问器的接近;利用RFID标签请求智能卡的CPU执行RFID功能;通过智能卡的CPU向移动终端的处理器发送模式转换信号,指示模式转换为RFID模式;和在传送模式转换信号后,使用智能卡执行射频识别功能。(String), 0(Integer), 15(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 17. The method as claimed in claim 16, wherein the mode transition signal includes a flag representing an execution of the RFID function.(String), 17.如权利要求16所述的方法,其中模式转换信号包括表示RFID功能执行的标志。(String), 1(Integer), 16(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 18. The method as claimed in claim 16, further comprising a step of transmitting a response signal from the mobile terminal to the smart card in response to the mode transition signal.(String), 18.如权利要求16所述的方法,还包括响应于模式转换信号,从移动终端向智能卡发送响应信号的步骤。(String), 1(Integer), 17(Integer), 15(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 19. The method as claimed in claim 18, wherein the response signal includes information representing a grant of the RFID function.(String), 19.如权利要求18所述的方法,其中响应信号包括表示授予RFID功能的信息。(String), 1(Integer), 18(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:35.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186019(Integer), 20. The method as claimed in claim 18, wherein the response signal includes information representing a rejection of the RFID function.(String), 20.如权利要求18所述的方法,其中响应信号包括表示拒绝RFID功能的信息。(String), 1(Integer), 19(Integer), 17(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.218 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.235 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.235 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.235 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186019(Integer), PRIORITY [0001]This application claims priority to an application entitled “Mobile Terminal Having Smart Card Coupled With RFID Tag and Method For Performing RFID Function in Such Mobile Terminal” filed in the Korean Industrial Property Office on Nov. 27, 2003 and assigned Serial No. 2003-85300, the contents of which are hereby incorporated by reference. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a mobile terminal having an RFID (radio frequency identification) tag, the usage and importance of which have increased, and a detachable SIM (subscriber identification module), the usage and importance of which have also increased, and more particularly to a circuit in which an RFID tag is integrally coupled with an SIM, a mobile terminal circuit having the circuit and a method for performing an RFID function in a mobile communication terminal. [0004]2. Description of the Related Art [0005]An RFID transponder or a tag has been developed in an agriculture department of U.S. National Laboratory to identify livestock. The tag having an electric code capable of identifying an animal is inserted into or attached to the animal. In addition, an interrogator capable of interpreting such electrical code is installed in an animal stable, thereby conveniently checking whether the animal has returned to the stable. The interrogator transmits an RF signal to the tag, and the electric code stored in the tag is returned to the interrogator through a modulator of the tag. This is called a backscatter modulation. An RFID tag has an antenna coil through which a modulation signal is transmitted to the interrogator. Such systems are described in U.S. Pat. Nos. 4,075,632 and 4,360,810, the contents of which are incorporated by reference herein. [0006]As RFID techniques make great strides, other techniques for identifying moving objects have been applied to various fields. For example, the techniques have been utilized for vehicles, ocean conveyance containers, or railroad vehicles. Information stored in a tag of such a transportation device is used for a location tracking, a content identification, and so forth. Techniques in relation to such fields are disclosed in U.S. Pat. Nos. 4,739,328, 4,782,345, 4,786,907, 4,816,839, 4,835,377, and 4,853,705, the contents of which are incorporated by reference herein. [0007]Recently, the RFID technique has been tested in many kinds of fields. A communication system used in such fields has come into the spotlight, owing to wide applicability. For instance, since a mobile communication system has many subscribers, in a case where the mobile communication system employing new techniques such as RFID is industrialized, it is possible to easily make profits. Also, since a current mobile communication is stabilized in the aspect of profitability, vendors request to develop applications capable of making supplementary value. [0008]FIG. 1 shows a structure of a passive RFID tag. A tag shown in FIG. 1 is MCRF200 available from Microchip Technology, Inc. [0009]A modulation circuit 209 is a part for connecting antenna coils (not shown) to RFID circuit elements. As an RFID interrogator (not shown) approaches an RFID tag, according to Faraday's law, the antenna coil generates induced electromotive force through an inductive coupling between the RFID interrogator and the RFID tag. Voltage intensity of the antenna coil varies depending on a modulated signal outputted from the modulation circuit 209. [0010]A rectifying section 202 rectifies AC voltage of the induced electromotive force in order to supply DC voltage to other components. A clock generating section 201 generates a system clock by extracting carrier frequency from a signal transferred from the RFID interrogator. The clock generating section 201 supplies other circuit components of the RFID tag with a baud rate, a modulation rate, and a programming rate. A row decoder 204 and a column decoder 207 extract ID data stored in a memory 206 at a clock rate and encode an extracted ID data by means of an NRZ (Non Return to Zero) Direct method, a Differential Biphase method, or a Manchester Biphase method before modulation, thereby generating a serial data stream. [0011]A modulation control section 203 modulates the serial data stream transferred from the decoders 204 and 207 by using a predetermined method, such as an FSK (Frequency Sift keying) method or a PSK (Phase Shift Keying) and the like, and transfers the serial data stream to the modulation circuit 209. A counter 205 counts clocks outputted from the clock generating section 201, so as to provide the clocks to the row decoder 204 and the column decoder 207. [0012]In a case in which a mobile communication system employs an RFID technique, it is expected to provide various supplementary services suitable for cellular systems. In this case, it is absolutely necessary that current RFID equipment are properly combined with current cellular systems. It has already mentioned that an RFID tag (e.g., a card-type RFID tag) is combined with an existing mobile terminal. An example of the RFID tag is disclosed in Korean Patent laid-open publication No. 2002-0090929 entitled “mobile communication terminal apparatus”. [0013]However, since a generally-used RFID tag is only provided for an existing mobile terminal circuit without modifying it or performing an adaptation process, the problem occurs that such an RFID tag is not adaptable for the miniaturization and portability of the existing mobile terminal which are essential features of a mobile terminal. [0014]Meanwhile, a mobile telephone having a GSM (Global System for Mobile telecommunication) mode generally uses a SIM card for identifying subscribers. The SIM card has a small-sized card shape and is used while being set in a slot provided on a rear side of a body of a GSM mode mobile telephone. [0015]FIG. 2 shows a structure of a conventional SIM card for a mobile terminal. [0016]A SIM card used for mobile communication systems, such as GSM systems, is defined in GSM 11.11 Standard, GSM 11.12 Standard, and ISO/IEC 7816. In these standard documents, physical characteristics and electrical signals and transmission protocols of the SIM card and a logical model for the SIM card are explained. The SIM card has 8 external pins. Contact pins C1, C2, C3, C5, and C6 refer to voltage Vcc, a reset RST, a clock CLK, a ground GND, and program voltage Vpp, respectively. A contact pin C7 is an external pin for data input/output I/O and is connected to an antenna for identifying radio frequency. Also, contact pins C4 and C8 RFUs are reserved. [0017]The SIM card internally has a Read Only Memory (ROM) 304 including an operation system operating the SIM card, a Central Processing Unit (CPU) 300 controlling an SIM card operation, a Random Access Memory (RAM) 302 which is a data processing block, and an Electrically Erasable Programmable Read Only Memory (EEPROM) 306 storing identity information of the SIM card. [0018]The SIM card is a kind of a smart card. If an RFID tag having functions of the smart card is separately provided for a mobile communication terminal capable of detaching the SIM card, wasteful factors occur. If the SIM card and the RFID tag are separately provided for the mobile communication, it is difficult to manage the RFID tag for service vendors, who provide various services using the SIM card and pursue added value creation through the various services. Accordingly, it is impossible for the service vendors to acquire the expected advantages resulting from employing the RFID tag, which are namely an increase of profit by means of an RFID service, an increase of the number of subscribers, and an expansion of a service range. [0019]There exists a method in which the SIM card provides additional functions besides a primary function for authenticating mobile terminal users. For instance, a SIM/WIM card which achieves a WIM (Wireless Application Protocol Identify Module) function for providing application services is formulated as WAP Provisioning Smart Card WAP-186-PROVSC-20010710-a Version by the WAP forum. Toolkit applications providing additional services by dynamically using the SIM card are defined in the GSM 11.14 Standard. [0020]The above-mentioned forum or standards only defines file structures and protocols for providing application services, and do not define hardware or software protocols accompanied with combination or connection between the RFID tag and the SIM card. Also, the above-mentioned forum or standards do not solve all existing problems. SUMMARY OF THE INVENTION [0021]Accordingly, the present invention has been made to solve the above-mentioned problems occurring in the prior art, and an object of the present invention is to provide a smart card coupled with an RFID tag. [0022]Another object of the present invention is to provide a mobile terminal capable of mounting a smart card coupled with an RFID tag thereon and a method for performing an identification function in a mobile terminal. [0023]In order to accomplish the above objects, according to a first aspect of the present invention, there is provided a smart card comprising: a user information processing section for storing user information and generating a user information signal including user information; an RFID information processing section for storing RFID data and generating an RFID signal including the RFID data; and a main calculating section connected to the user information processing section, in order to control generation and transmission of the user information signal, and connected to the RFID information processing section in order to command generation and transmission of the RFID signal. [0024]In order to accomplish the above objects, according to a second aspect of the present invention, there is provided a mobile terminal comprising: a smart card installed in the mobile terminal for storing user information, the smart card including an RFID tag; and a processor in communication with the smart card so as to grant or reject an RFID function of the smart card. [0025]In order to accomplish the above objects, according to a third aspect of the present invention, there is provided a method for performing an RFID function in a mobile terminal equipped with a smart card having an RFID tag, the method comprising: detecting an approach of an RFID interrogator by using the RFID tag; requesting a CPU of the smart card to perform the RFID function by utilizing the RFID tag detecting the approach of the RFID interrogator; transmitting a mode transition signal to a processor of the mobile terminal by using the CPU of the smart card to indicate a mode transition into an RFID mode; and performing the RFID function by using the smart card after transmitting the mode transition signal. BRIEF DESCRIPTION OF THE DRAWINGS [0026]The above objects and other features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [0027]FIG. 1 is a block diagram of a conventional radio frequency identification (RFID) tag; [0028]FIG. 2 is a block diagram of a conventional SIM card; [0029]FIG. 3 is a block diagram of an SIM card coupled with an RFID tag according to a first embodiment of the present invention; [0030]FIG. 4 is a block diagram of an SIM card coupled with an RFID tag according to a second embodiment of the present invention; [0031]FIG. 5 is a block view showing a logical structure of an SIM card according to one embodiment of the present invention; [0032]FIG. 6 is a view showing an EF structure for storing RFID data according to one embodiment of the present invention; [0033]FIG. 7 is a view showing a mode transition of an SIM card according to one embodiment of the present invention; [0034]FIG. 8 is a view showing a signal exchange between a mobile terminal and a SIM card according to one embodiment of the present invention; [0035]FIG. 9 is a block view showing a structure of an ATR signal shown in FIG. 8; and [0036]FIG. 10 is a schematic view showing a structure of a mobile terminal equipped with a SIM card having an RFID section. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0037]Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. Although certain functions, such as elements of a specific circuit, are specifically defined in the following description of the present invention, it will be obvious to those skilled in the art that such definitions of functions are merely to improve understanding of the present invention and that the present invention can be carried out without such specific elements. Also, in the following description of the present invention, the same reference numerals are used to designate the same or similar components and a detailed description of known functions and configurations incorporated herein are omitted to avoid making the subject matter of the present invention unclear. [0038]A SIM card coupled with an RFID tag is an improvement of a conventional SIM card in view of hardware configuration, logical structure, and operational procedure. 1) Hardware Configuration [0039]FIGS. 3 and 4 are block diagrams of a SIM card coupled with an RFID tag according to exemplary embodiments of the present invention. [0040]FIG. 3 is a view showing the structure of the SIM card coupled with the RFID tag according to a first embodiment of the present invention. In FIG. 3, several already-known components of the SIM card are not illustrated. In addition, RFID data shown as a dotted-block in FIG. 3 represent that an RFID memory section can be provided in an EEPROM 404 or in an ROM 410. [0041]In a conventional RFID tag, ID (identification) data are generally stored in an EEPROM. However, the SIM card also includes the EEPROM. Thus, a margin space of the EEPROM can be utilized as a storage space of RFID data. That is, the EEPROM 404 stores RFID data as well as intrinsic data of the SIM card. [0042]An RFID CODEC section 406 and an RFID modulation section 408 are provided in the ROM 410 of the SIM card. The ROM 410 of the SIM card is a digital logic circuit for realizing an operating system by using a digital CODEC and a modulation section. [0043]A CPU 402 transfers an order to the ROM 410 such that a required function can be carried out. At this time, since RFID data is stored based on a logical structure of a conventional SIM card, RFID data can be processed as another SIM card data. In other words, functional instruction words, such as SELECTION, STATUS, READ BINARY, and UPDATE BINARY, described in “8. Description of the functions” of GSM 11.11 standard document can be used in software capable of operating RFID functions of the SIM card. [0044]Connection pins C4 and C8, usage of which is now reserved, are connected to an RFID antenna coil (not shown) through a coil connecting section 412 connected to an interrupt section 414. Induced electromotive force is generated from the RFID antenna coil when an RFID interrogator (not shown) approaches the RFID antenna coil and induced electromotive force is transferred to the interrupt section 414 through the coil connecting section 412, thereby creating the interrupt. Upon detecting the interrupt, the CPU 402 recognizes that extracting and processing of RFID data are required. Thus, the CPU 402 reads RFID data stored in a memory section (EEPROM 404 or ROM 410) and stores RFID data in a RAM 400. In addition, the CPU 402 controls the RFID CODEC section 406 and the RFID modulation section 408 so as to process RFID data. An RFID signal outputted from the RFID modulation section 408 is transmitted to the RFID interrogator through the coil connecting section 412 with a predetermined frequency determined by the RFID system. [0045]In addition, the CPU 402 not only detects the creation of interrupt from the interrupt section 414, but also recognizes a time for carrying out the RFID functions through various manners, such as a software timer. [0046]When seeing the first embodiment of the present invention in view of usable power, RFID functional blocks, such as the EEPROM 404, RFID CODEC section 406, and RFID modulation section 408 receive supply voltage Vcc, which is stable voltage of a mobile terminal, through a connection terminal C1 of the SIM card. Thus, a problem caused by a conventional power supply of induced electromotive force, which is unstable depending on peripheral environment, can be solved. [0047]When seeing the first embodiment of the present invention in view of a clock CLK, the clock supplied to a connection pin C3 is typically in a standard range of 1 MHz to 5 MHz from a clock supply of the mobile terminal. When the RFID signal is transferred to the coil connecting section 412, the CPU 402 varies the clock CLK according to the RFID system and transmits the RFID signal by synchronizing the RFID signal with the varied clock CLK. [0048]FIG. 4 is a view showing a structure of the SIM card coupled with the RFID tag according to a second embodiment of the present invention. In FIG. 4, several already-known components of the SIM card are not illustrated. [0049]Referring to FIG. 4, an RFID CODEC section 508 and an RFID modulation section 510 are provided in the SIM card in such a manner that the RFID CODEC section 508 and the RFID modulation section 510 are separate from a memory section. [0050]A clock modulation section 516 modulates a clock CLK transmitted from a mobile terminal through a connection pin C3 of the SIM card, thereby generating an RFID clock signal 518 and a SIM clock signal 520. The RFID clock signal 518 has a frequency required for operating RFID functional blocks, such as the RFID CODEC section 508 and the RFID modulation section 510. The SIM clock signal has a frequency required for operating SIM functional blocks, such as a CPU 500, a RAM 502, a ROM 504, and an EEPROM 506. [0051]Selectively, the RFID clock signal 518 can be used as a reference when the CPU 500 finally generates the RFID signal, without using the RFID clock signal 518 for the operation of the above RFID functional blocks. In this case, the above RFID functional blocks may use the clock signal identical to the clock signal of the SIM functional blocks. That is, the above RFID functional blocks may use the SIM clock signal 520. The clock is generated by means of the clock modulation section 516 and is controlled by means of a control signal 522 applied from the CPU 500. [0052]The CPU 500 reads RFID data stored in the memory section, such as the EEPROM 506 or the ROM 504, and stores RFID data in the RAM 502. In addition, the CPU 500 transfers RFID data to the RFID CODEC section 508 so as to convert RFID data into the RFID signal through the RFID modulation section 510. The RFID signal is transferred to a coil connecting section 514 and is propagated to an exterior through an antenna coil (not shown) connected to the coil connecting section 514. 2) Logical Structure [0053]A logical structure of the SIM card used in a GSM mobile terminal is prescribed in a GSM 11.11 standard document. In order to provide the RFID functions according to the present invention, it is required to vary the logical structure of the SIM card. However, the variation may be carried out within a predetermined range capable of maintaining flexibility. [0054]FIG. 5 is a block view showing the logical structure of the SIM card according to one embodiment of the present invention. [0055]The logical structure of the SIM card includes a master file (MF), a dedicated file (DF), and an elementary file (EF). The MF is selected when the SIM card is initially operated and is designated as a present directory. The DF is used for providing multi-functions required for various business services, such a telecom service, a Global System for Mobile communications (GSM), a Digital Cellular System 1800 (DCS1800) or an Interim Standard 41 (IS41). The DF has the EF, which stores data utilized for each service. [0056]In order to realize the present invention, a new DF and a new EF corresponding to the new DF are added to the conventional SIM logical system. As shown in FIG. 5, the new DF includes a DFRFID for the RFID function. An EF6 stores RFID data for the purpose of the service. [0057]In the SIM logical system, a file ID “7F2X” is allotted to the DF for new services. Thus, by storing RFID data in the EF corresponding to the DF having the file ID of 7F2X, it is possible to store data for the RFID service in the conventional SIM logical structure without using conventional instruction words. Such files for the RFID service are stored in the EEPROM 406 shown in FIG. 3 and the EEPROM 506 shown in FIG. 4. [0058]FIG. 6 is a view showing an EF structure for storing RFID data according to an exemplary embodiment of the present invention. [0059]Since the EF is based on GSM standardization, the EF is realized as an extensible file of the SIM logical structure so that conventional software can be continuously used. [0060]A variable range of an “identifier” may depend on the file ID of the DF. For instance, if the DFRFID has a file ID of 7F2X, the identifier has 6F2X, 6F3X or 6F4X. A “structure” is a file structure of the EF. Transparent type, linear fixed type, and cyclic type EFs are standardized. The transparent type EF is adaptable for a sequence of bytes, such as RF data. [0061]A “file size” is a size of RFID data to be stored (for example, 4 bytes). Software instruction words for controlling RFID data stored in the EF include READ, UPDATE, INVALIDATE, and REHABILITATE, which are based on the standardization of the GSM. In addition, executive conditions for the instruction words include CHV1 (card holder verification 1) and ADM (administration). The CHV1 represents a software task allowing a card holder to access thereto, and the ADM represents a software task allowing an administrator of the SIM card to access thereto. 3) Operation Procedure [0062]By providing the RFID function to the conventional SIM card, a mode of the SIM card and an interface between a mobile terminal and the SIM card are varied. [0063]FIG. 7 is a view showing a mode transition of the SIM card according to one embodiment of the present invention. [0064]A mode of the SIM card can be shifted into a specific mode or a negotiable mode after transmitting an ATR (answer-to-reset) signal in response to a reset request from the mobile terminal. The specific mode is divided into a telecom mode (for example, GSM mode) and an RFID mode. Application software of the mobile terminal requests the negotiable mode through a signal exchange between the mobile terminal and the SIM card. A mode transition of a smart card into the RFID mode according to a request of the mobile terminal is one example of the negotiable mode. [0065]The mode transition is displayed by a specific mode byte TA(2) of the ATR signal, which is prescribed in ISO/IEC 7816-3. The ATR signal is the sequence of bytes transferred to the mobile terminal from the SIM card as an answer for a reset request of the mobile terminal. The ATR signal is an asynchronous transmission. [0066]FIG. 8 is a view showing the signal exchange between the mobile terminal and the SIM card according to one embodiment of the present invention. [0067]When the CPU of the SIM card having the RFID function recognizes an approach of the RFID interrogator, via the interrupt section, the CPU of the SIM card indicates the approach of the RFID interrogator to the CPU of the mobile terminal by using the ATR signal. Upon receiving the ATR signal indicating an operation of the RFID function from the SIM card, the mobile terminal grants the RFID function depending on an application program or an operational state of the mobile terminal, so that the SIM card can perform the RFID function. In addition, if it is required that mobile terminal request a primary function of the SIM card, that is, when it is required to primarily request a user's identification for a communication system or when the mobile terminal cannot perform the RFID function, the mobile terminal may reject the RFID function. In addition, without considering the priority, the mobile terminal can be designed such that the mobile terminal is converted into an RFID mode when the CPU of the mobile terminal recognizes the approach of the RFID interrogator. [0068]FIG. 9 is a block view showing a structure of the ATR signal shown in FIG. 8. [0069]The ATR signal, which is prescribed in ISO/IEC 7816-3, is a combination of bytes transmitted in series. Usage of each byte is prescribed in ISO/IEC 7816-3. In addition, usage of some bytes is reserved. Thus, the SIM card can indicate the start of the RFID function to the mobile terminal by using the ATR signal. For instance, the ATR signal including beats (for example, beats having a lower four-beat value of “1111”) capable of indicating the RFID mode can be made in the specific mode byte TA(2). The specific mode byte TA(2) may be used to indicate that a mode has been already shifted into the RFID mode from the specific mode after a cold reset (that is, when the SIM card having the RFID mode receives a request, which does not relate to the RFID, from the mobile terminal. For example, when the mobile terminal requests the user's ID). In addition, the specific mode byte TA(2) may be used to indicate the start of the RFID mode as the RFID interrogator approaches the SIM card (that is, notifying of a transition into the RFID mode from a communication mode). [0070]According to another embodiment of the present invention, a bit indicating the RFID mode can be added to the lower four-bits of a TD(i), which is an interface byte. According to the standardization of ISO/IEC 7816-3, lower four-bits of the TD(i) and TA(2) are defined as a parameter T, wherein usage of some parameters (T=5 to 13) is reserved to use them in the future. Therefore, usage of some T values for the purpose of the RFID does not violate the standardization of ISO/IEC 7816-3, so that the SIM card can be flexibly used in a conventional system. [0071]FIG. 10 is a schematic view showing a structure of a mobile terminal equipped with an SIM card having an RFID section. [0072]Reference numeral 900 represents a processor of the mobile terminal ME. An example of the processor is a mobile station modem (MSM) chip called “mobile processor” available from the Qualcomm company. [0073]Reference numeral 950 represents the SIM card. The SIM card having the RFID section is installed in the mobile terminal in order to signal a mode transition into an RFID mode. To this end, a CPU 912, a SIM section 914 and an RFID section 916 of the SIM card 950 are only illustrated in FIG. 10. Already-known components of the SIM card 950 are not illustrated in FIG. 10. [0074]The SIM section 914 is a user information processing section for storing user information and generating a user information signal including user information. In addition, the user information processing section includes a user information memory section for storing user information and a user program memory section having a program generating a user information signal. The user information memory section includes the EEPROM 404 and the user program memory section includes the ROM 410, as shown in FIG. 3. In addition, the user information memory section includes the EEPROM 506 and the user program memory section includes the ROM 504 as shown in FIG. 4. [0075]The RFID section 916 is an RFID information processing section capable of storing and processing RFID data and generating an RFID signal including RFID data. In addition, the RFID information processing section includes an RFID information memory section for storing RFID information and an RFID function section for generating the RFID signal. The RFID information memory section can be provided in the EEPROM 404 or ROM 410, and the RFID function section includes the RFID CODEC section 406 and the RFID modulation section 410 as shown in FIG. 3. In addition, the RFID information memory section can be provided in the EEPROM 506 or ROM 504, and the RFID function section includes the RFID CODEC section 508 and the RFID modulation section 510, as shown in FIG. 4. [0076]The CPU 912 is a main calculating section connected to the user information processing section to command the generation of the user information signal so as to transmit the user information signal, and connected to the RFID information processing section to command generation of the RFID signal in order to transmit the RFID signal. The CPU 912 corresponds to the CPU 402 shown in FIG. 3 and the CPU 500 shown in FIG. 4. [0077]When an RFID interrogator (not shown) approaches the mobile terminal MT within a predetermined distance, the RFID section 916 of the SIM card 950 installed in the mobile terminal MT detects the approach of the RFID interrogator. Upon detecting the RFID interrogator, the RFID section 916 transfers detecting data to the CPU 912 of the SIM card 950 so that the SIM card 950 recognizes that the RFID function must be carried out. Accordingly, the CPU 912 of the SIM card 950 transmits a signal to the processor 900 of the mobile terminal so as to convert a mode of the mobile terminal into the RFID mode. In addition, a mode of the SIM card 950 is converted into an RFID function mode for performing the RFID function. [0078]According to the present invention, the mobile terminal can provide stable clocks and a stable power supply to the RFID functional blocks, rather than receiving power from the RFID interrogator or providing clocks to the functional blocks that use the coil connecting section and that extract the clocks from a carrier wave signal transmitted from the RFID interrogator, thereby stabilizing the system. Conventional systems may become unstable depending on RF feeding environment if carrier wave signals and induced electromotive force are deteriorated. [0079]As described above, the present invention performing the RFID function by utilizing the SIM card has advantages that include: [0080]First, the SIM card can be detachably installed in the mobile terminal so as to perform the RFID functions, but the portability and miniaturization of the mobile terminal, which are important matters, are not thereby improved. If the RFID tag is separately fabricated from the SIM card, the mobile terminal may not satisfy the portability and miniaturization requirements. [0081]Second, in a functional aspect, the present invention may upgrade the conventional SIM card, so it is possible to create a new demand for the SIM card. [0082]Third, since an RFID technique is provided through the SIM card, an advanced RFID technique can be applied to the conventional mobile communication system. If the RFID tag is fabricated separate from the SIM card, the RFID tag may be fixed in the mobile terminal, so it is difficult to apply the advanced RFID technique to the mobile terminal. [0083]Fourth, an earning rate of a service provider providing a service to subscribers by managing the SIM card may increase. This is because the RFID technique, which is a basis for new services, is adopted in the SIM card, making it possible to provide additional techniques based on a conventional payment charge system and a conventional user management system. If the RFID tag is fabricated separately from the SIM card, it is difficult to provide new services that utilize the RFID tag, resulting in a decreased earning rate of the service provider. [0084]While the present invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.(String), 优先 [0001] 本申请要求于 2003 年 11 月 27 日在韩国工业产权局提交并转让序列号为 2003-85300 的题为“具有与 RFID 标签耦合的智能卡的移动终端和在这种移动终端中执行 RFID 功能的方法”的申请的优先权 ,其内容通过引用并入本文。 背景技术 [0002] 1. 发明领域 [0003] 本发明涉及具有RFID(射频识别)标签的移动终端,其使用和重要性增加,以及可拆卸的SIM(订户识别模块),其使用和重要性也增加,更具体地讲 本发明涉及一种RFID标签与SIM整体耦合的电路、具有该电路的移动终端电路以及用于在移动通信终端中执行RFID功能的方法。 [0004] 2.相关技术的描述 [0005] 美国国家实验室的一个农业部门已经开发了一种 RFID 应答器或标签来识别牲畜。 具有能够识别动物的电码的标签被插入或附在动物身上。 此外,在畜栏内安装了能够解读这种电码的询问器,从而方便地检查动物是否已经返回畜栏。 读写器向标签发射射频信号,存储在标签中的电码通过标签的调制器返回读写器。 这称为反向散射调制。 RFID标签具有天线线圈,调制信号通过该天线线圈传输到询问器。 此类系统在美国专利 5,500,000 中进行了描述。 美国专利 4,075,632 和 4,360,810,其内容通过引用并入本文。 [0006] 随着 RFID 技术取得长足进步,用于识别移动物体的其他技术已应用于各个领域。 例如,这些技术已用于车辆、海运集装箱或铁路车辆。 存储在这种运输设备的标签中的信息用于位置跟踪、内容识别等。 与这些领域相关的技术在美国专利 5,500,000 中公开。 美国专利 4,739,328、4,782,345、4,786,907、4,816,839、4,835,377 和 4,853,705,其内容通过引用并入本文。 [0007] 近来,RFID技术已经在多种领域进行了测试。 由于广泛的适用性,用于此类领域的通信系统已成为人们关注的焦点。 例如,由于移动通信系统的订户多,因此在采用RFID等新技术的移动通信系统工业化的情况下,可以容易地获利。 此外,由于当前的移动通信在盈利能力方面稳定,厂商要求开发能够产生附加价值的应用程序。 [0008] 如图。 图1示出了无源RFID标签的结构。 图 1 所示的标签。 1 是可从 Microchip Technology, Inc. 获得的 MCRF200。 [0009] 调制电路 209 是用于将天线线圈(未显示)连接到RFID电路元件的部件。 当RFID询问器(未示出)接近RFID标签时,根据法拉第定律,天线线圈通过RFID询问器和RFID标签之间的感应耦合产生感应电动势。 天线线圈的电压强度根据调制电路输出的调制信号而变化 209 . [0010] 整流段 202 对感应电动势的交流电压进行整流,以便为其他部件提供直流电压。 时钟产生部分 201 通过从RFID询问器传输的信号中提取载波频率来生成系统时钟。 时钟生成部分 201 为RFID标签的其他电路组件提供波特率、调制率和编程率。 行解码器 204 和一个列解码器 207 提取存储在内存中的 ID 数据 206以时钟速率,在调制前通过NRZ(不归零)直接法、差分双相法或曼彻斯特双相法对提取的ID数据进行编码,从而产生串行数据流。 [0011] 调制控制部分 203 调制从解码器传输的串行数据流 204 和 207 通过预定的方法,例如FSK(Frequency Sift Keying)方法或PSK(Phase Shift Keying)等,将串行数据流传输到调制电路 209 . 一个柜台 205 对时钟生成部分输出的时钟进行计数 201 ,以便为行解码器提供时钟 204 和列解码器 207 . [0012] 在移动通信系统采用RFID技术的情况下,期望提供适合蜂窝系统的各种补充服务。 在这种情况下,当前的 RFID 设备与当前的蜂窝系统正确结合是绝对必要的。 已经提到RFID标签(例如,卡片式RFID标签)与现有的移动终端相结合。 在题为“移动通信终端设备”的韩国专利公开第2002-0090929号中公开了RFID标签的示例。 [0013] 然而,由于普遍使用的RFID标签只提供给现有的移动终端电路,而没有对其进行修改或适配处理,因此存在这样的RFID标签不适应现有移动终端的小型化和便携性的问题。 移动终端的基本功能。 [0014] 同时,具有GSM(全球移动电信系统)模式的移动电话通常使用SIM卡来识别用户。 SIM卡具有小尺寸的卡片形状,并且被设置在设置在GSM模式移动电话的机身后侧的插槽中使用。 [0015] 如图。 图2示出了传统的用于移动终端的SIM卡的结构。 [0016] GSM 11.11 标准、GSM 11.12 标准和 ISO/IEC 7816 中定义了用于移动通信系统,例如 GSM 系统的 SIM 卡。在这些标准文件中,SIM 卡的物理特性和电信号和传输协议以及 SIM 卡的逻辑模型进行了说明。 SIM 卡有 8 个外部引脚。 触针 C 1 , C 2 , C 3 , C 5 , 和 C 6 分别指电压Vcc、复位RST、时钟CLK、地GND和编程电压Vpp。 A 触针 C 7 是用于数据输入/输出 I/O 的外部引脚,并连接到用于识别射频的天线。 此外,触针 C 4 和 C 8 RFU 被保留。 [0017] SIM 卡内部有一个只读存储器 (ROM) 304 包括操作 SIM 卡的操作系统、中央处理器 (CPU) 300 控制 SIM 卡操作,随机存取存储器 (RAM) 302 这是一个数据处理块和一个电可擦可编程只读存储器(EEPROM) 306 存储SIM卡的身份信息。 [0018] SIM卡是一种智能卡。 如果为能够分离SIM卡的移动通信终端单独设置具有智能卡功能的RFID标签,则会出现浪费的因素。 如果为移动通信分别提供SIM卡和RFID标签,则难以为使用SIM卡提供各种服务并通过各种服务寻求增值创造的服务供应商管理RFID标签。 因此,服务供应商无法获得使用RFID标签所带来的预期优势,即通过RFID服务增加利润、增加用户数量和扩大服务范围。 . [0019]存在一种方法,其中SIM卡提供除了用于认证移动终端用户的主要功能之外的附加功能。 例如,实现WIM(Wireless Application Protocol Identification Module)功能提供应用服务的SIM/WIM卡被WAP论坛制定为WAP Provisioning Smart Card WAP-186-PROVSC-20010710-a版本。 GSM 11.14 标准中定义了通过动态使用 SIM 卡提供附加服务的工具包应用程序。 [0020] 上述论坛或标准仅定义了提供应用服务的文件结构和协议,并未定义RFID标签与SIM卡结合或连接的硬件或软件协议。 此外,上述论坛或标准并不能解决所有现有问题。 发明内容 [0021] 因此,本发明旨在解决现有技术中出现的上述问题,本发明的目的在于提供一种与RFID标签相结合的智能卡。 [0022] 本发明的另一个目的是提供一种能够安装其上耦合有RFID标签的智能卡的移动终端以及用于在移动终端中执行识别功能的方法。 [0023] 为了实现上述目的,根据本发明的第一方面,提供了一种智能卡,包括: 用户信息处理部分,用于存储用户信息并产生包括用户信息的用户信息信号; RFID信息处理部分,用于存储RFID数据并产生包括RFID数据的RFID信号; 主计算部分连接到用户信息处理部分,以控制用户信息信号的生成和传输,并连接到RFID信息处理部分,以命令生成和传输RFID信号。 [0024] 为了实现上述目的,根据本发明的第二方面,提供了一种移动终端,包括: 智能卡,安装在移动终端中,用于存储用户信息,智能卡包括RFID标签; 处理器与智能卡通信,以授予或拒绝智能卡的RFID功能。 [0025] 为了实现上述目的,根据本发明的第三方面,提供了一种在配备有具有RFID标签的智能卡的移动终端中执行RFID功能的方法,该方法包括: 使用RFID标签的RFID读写器; 利用RFID标签检测RFID读写器的接近,请求智能卡的CPU执行RFID功能; 通过智能卡的CPU向移动终端的处理器发送模式转换信号,指示模式转换到RFID模式; 发送模式转换信号后,利用智能卡执行RFID功能。 附图的简要说明 [0026] 本发明的上述目的和其他特征和优点将通过以下结合附图的详细描述而更加明显,其中: [0027] 如图。 附图说明图1是传统射频识别(RFID)标签的框图; [0028] 如图。 图2是现有SIM卡的框图。 [0029] 如图。 图3是根据本发明第一实施例的结合RFID标签的SIM卡的框图。 [0030] 如图。 图4是根据本发明第二实施例的结合RFID标签的SIM卡的框图。 [0031] 如图。 图5是表示本发明一实施方式的SIM卡的逻辑结构的框图。 [0032] 如图。 图6是表示本发明的一实施方式的RFID数据存储用EF结构的图。 [0033] 如图。 图7是表示本发明的一个实施方式的SIM卡的模式转换的图。 [0034]如图。 图8为本发明一实施例的移动终端与SIM卡的信号交换示意图。 [0035] 如图。 图9是表示图8所示的ATR信号的结构的框图。 8个; 和 [0036] 如图。 图10是示出配备有具有RFID部分的SIM卡的移动终端的结构的示意图。 优选实施例的详细说明 [0037] 在下文中,将参照附图描述本发明的优选实施例。 尽管在本发明的以下描述中具体定义了某些功能,例如特定电路的元件,但是对于本领域技术人员来说,这些功能的定义仅仅是为了提高对本发明的理解,并且 本发明可以在没有这些特定元件的情况下实施。 此外,在本发明的以下描述中,相同的附图标记用于表示相同或相似的部件,并且省略了包含在本文中的已知功能和配置的详细描述以避免使本发明的主题不清楚。 [0038] 结合RFID标签的SIM卡是对传统SIM卡的硬件配置、逻辑结构和操作流程的改进。 1) 硬件配置 [0039] 图 图3和4是根据本发明示例性实施例的与RFID标签耦合的SIM卡的框图。 [0040] 如图。 图3为本发明第一实施例的结合RFID标签的SIM卡的结构示意图。 在图。 在图3中,未示出SIM卡的几个已知组件。 此外,RFID数据在图1中以虚线块表示。 图3表示可以在EEPROM中提供RFID存储部分 404 或在 ROM 中 410 . [0041] 在传统的RFID标签中,ID(识别)数据通常存储在EEPROM中。 但是,SIM 卡也包含 EEPROM。 因此,EEPROM的余量空间可以用作RFID​​数据的存储空间。 也就是说,EEPROM 404 存储 RFID 数据以及 SIM 卡的固有数据。 [0042] 一个 RFID CODEC 部分 406 和一个 RFID 调制部分 408 在 ROM 中提供 410 SIM 卡。 只读存储器 410 SIM卡的一个数字逻辑电路是利用数字CODEC和调制部分实现操作系统的数字逻辑电路。 [0043] 一个中央处理器 402 将订单转移到 ROM 410 以便可以执行所需的功能。 此时,由于RFID数据是基于传统SIM卡的逻辑结构存储的,RFID数据可以作为另一个SIM卡数据处理。 换言之,在“8. GSM 11.11标准文档中的“功能描述”可用于能够操作SIM卡RFID功能的软件。 [0044] 连接针 C 4 和 C 8 ,现在保留使用,通过线圈连接部分连接到RFID天线线圈(未显示) 412 连接到中断部分 414 . 当 RFID 询问器(未显示)接近 RFID 天线线圈并将感应电动势传递到中断部分时,RFID 天线线圈会产生感应电动势 414 通过线圈连接部分 412 ,从而产生中断。 在检测到中断时,CPU 402 认识到需要提取和处理 RFID 数据。 因此,CPU 402 读取存储在内存部分(EEPROM 404 或只读存储器 410 ) 并将 RFID 数据存储在 RAM 中 400 . 此外,CPU 402 控制 RFID CODEC 部分 406 和 RFID 调制部分 408 以处理RFID数据。 从 RFID 调制部分输出的 RFID 信号 408 通过线圈连接部分传输到RFID读写器 412 具有由 RFID 系统确定的预定频率。 [0045] 此外,CPU 402 不仅从中断部分检测到中断的创建 414 ,还可以通过软件定时器等多种方式识别执行RFID功能的时间。 [0046] 当从可用功率的角度来看本发明的第一实施例时,RFID功能块,例如EEPROM 404 , RFID CODEC部分 406 , 和 RFID 调制部分 408 通过连接端C接收移动终端的稳定电压Vcc 1 SIM 卡。 因此,可以解决由感应电动势的传统电源引起的问题,该感应电动势取决于周边环境而不稳定。 [0047] 当从时钟 CLK 来看本发明的第一实施例时,提供给连接引脚 C 的时钟 3 典型地在来自移动终端的时钟供应的1MHz到5MHz的标准范围内。 当 RFID 信号传送到线圈连接部分时 412 , 中央处理器 402 根据RFID系统改变时钟CLK并且通过将RFID信号与改变的时钟CLK同步来传输RFID信号。 [0048] 如图。 图4是表示本发明的第二实施方式的与RFID标签结合的SIM卡的结构的图。 在图。 在图4中,未示出SIM卡的几个已知组件。 [0049] 参考图。 4、一个RFID CODEC部分 508 和一个 RFID 调制部分 510 在 SIM 卡中以这样的方式提供,即 RFID CODEC 部分 508 和 RFID 调制部分 510 与内存部分分开。 [0050] 时钟调制部分 516 通过连接引脚 C 调制从移动终端发送的时钟 CLK 3 SIM卡,从而产生RFID时钟信号 518 和一个 SIM 时钟信号 520 . RFID时钟信号 518 具有操作 RFID 功能块所需的频率,例如 RFID CODEC 部分 508 和 RFID 调制部分 510 . SIM 时钟信号具有操作 SIM 功能块(例如 CPU)所需的频率 500 , 一个内存 502 , 一个只读存储器 504 , 和一个 EEPROM 506 . [0051] 选择性地,RFID时钟信号 518 CPU时可以作为参考 500 最后生成RFID信号,不使用RFID时钟信号 518 用于上述 RFID 功能块的操作。 在这种情况下,上述RFID功能块可以使用与SIM功能块的时钟信号相同的时钟信号。 即上述RFID功能块可以使用SIM时钟信号 520 . 时钟由时钟调制部分产生 516 并由控制信号控制 522 从 CPU 应用 500 . [0052] 中央处理器 500 读取存储在内存部分(如 EEPROM)中的 RFID 数据 506 或ROM 504 , 并将 RFID 数据存储在 RAM 中 502 . 此外,CPU 500 将 RFID 数据传输到 RFID CODEC 部分 508 从而通过RFID调制部分将RFID数据转换成RFID信号 510 . RFID信号被传送到线圈连接部分 514 并且通过连接到线圈连接部分的天线线圈(未示出)传播到外部 514 . 2) 逻辑结构 [0053] GSM 11.11标准文档中规定了用于GSM移动终端的SIM卡的逻辑结构。 为了提供根据本发明的RFID功能,需要改变SIM卡的逻辑结构。 然而,可以在能够保持灵活性的预定范围内进行变化。 [0054] 如图。 图5是表示本发明一实施方式的SIM卡的逻辑结构的框图。 [0055]SIM卡的逻辑结构包括主文件(MF)、专用文件(DF)和基本文件(EF)。 MF在SIM卡初始操作时被选择并被指定为当前目录。 DF用于提供各种商业服务所需的多功能,例如电信服务、全球移动通信系统(GSM)、数字蜂窝系统1800(DCS1800)或临时标准41(IS41)。 DF 有 EF,它存储用于每个服务的数据。 [0056] 为了实现本发明,在传统的SIM逻辑系统中增加了新的DF和对应于新DF的新EF。 如图所示。 5、新的DF包括一个DF RFID 用于 RFID 功能。 英孚 6 为服务目的存储 RFID 数据。 [0057] 在SIM逻辑系统中,文件ID“7F2X”被分配给DF用于新服务。 因此,通过将RFID数据存储在与具有7F2X的文件ID的DF对应的EF中,可以在不使用常规指令字的情况下以常规SIM逻辑结构存储用于RFID服务的数据。 RFID 服务的此类文件存储在 EEPROM 中 406 如图所示。 3和EEPROM 506 如图所示。 4. [0058] 如图。 图6是示出根据本发明示例性实施例的用于存储RFID数据的EF结构的视图。 [0059] 由于EF是基于GSM标准化的,所以EF被实现为SIM逻辑结构的可扩展文件,从而可以继续使用常规软件。 [0060] “标识符”的可变范围可能取决于 DF 的文件 ID。 例如,如果 DF RFID 文件 ID 为 7F2X,标识符有 6F2X、6F3X 或 6F4X。 “结构”是 EF 的文件结构。 透明型、线性固定型和循环型 EF 已标准化。 透明类型 EF 适用于一系列字节,例如 RF 数据。 [0061] “文件大小”是要存储的RFID数据的大小(例如,4字节)。 用于控制存储在 EF 中的 RFID 数据的软件指令字包括 READ、UPDATE、INVALIDATE 和 REHABILITATE,它们基于 GSM 的标准化。 此外,指令词的执行条件包括 CHV 1 (持卡人验证 1 ) 和 ADM(管理)。 CHV 1 代表允许持卡人访问的软件任务,并且ADM代表允许SIM卡的管理员访问的软件任务。 3) 操作程序 [0062] 通过为传统的SIM卡提供RFID功能,改变了SIM卡的模式以及移动终端与SIM卡的接口。 [0063] 如图。 图7是表示本发明的一个实施方式的SIM卡的模式转换的图。 [0064] SIM卡的模式可以在响应于来自移动终端的重置请求而发送ATR(重置应答)信号之后转换为特定模式或可协商模式。 具体模式分为电信模式(如GSM模式)和RFID模式。 移动终端的应用软件通过移动终端与SIM卡之间的信号交换请求协商模式。 根据移动终端的请求将智能卡模式转换为RFID模式是可协商模式的一个示例。 [0065] 模式转换由特定模式字节 TA( 2 ) 的 ATR 信号,这是在 ISO/IEC 7816-3 中规定的。 ATR信号是从SIM卡传送到移动终端的字节序列,作为对移动终端复位请求的应答。 ATR 信号是异步传输。 [0066] 如图。 图8为本发明一实施例的移动终端与SIM卡的信号交换示意图。 [0067]当具有RFID功能的SIM卡的CPU通过中断部分识别到RFID询问器的接近时,SIM卡的CPU通过ATR信号向移动终端的CPU指示RFID询问器的接近。 移动终端在从SIM卡接收到指示RFID功能操作的ATR信号后,根据应用程序或移动终端的操作状态授予RFID功能,从而SIM卡可以执行RFID功能。 另外,如果需要移动终端请求SIM卡的主要功能,即需要主要请求用户对通信系统的身份识别或移动终端不能执行RFID功能时,移动终端 可能拒绝 RFID 功能。 此外,在不考虑优先级的情况下,移动终端可以设计成当移动终端的CPU识别到RFID询问器的接近时,将移动终端转换为RFID模式。 [0068] 如图。 图9是表示图8所示的ATR信号的结构的框图。 8. [0069] ISO/IEC 7816-3 中规定的 ATR 信号是串行传输的字节组合。 ISO/IEC 7816-3 中规定了每个字节的使用。 此外,保留了一些字节的使用。 因此,SIM卡可以通过ATR信号向移动终端指示RFID功能的启动。 例如,可以在特定模式字节TA( 2 )。 特定模式字节 TA( 2 )可用于表示在冷复位后(即当具有RFID模式的SIM卡收到与RFID无关的请求时,从特定模式转移到RFID模式) 移动终端。例如,当移动终端请求用户的ID时)。 此外,特定模式字节 TA( 2 ) 可用于在 RFID 询问器接近 SIM 卡时指示 RFID 模式的开始(即,通知从通信模式转换到 RFID 模式)。 [0070] 根据本发明的另一个实施例,可以将指示RFID模式的位添加到作为接口字节的TD(i)的低四位。 根据 ISO/IEC 7816-3 的标准化,TD(i) 和 TA( 2 )被定义为参数T,其中一些参数(T=5到13)的使用被保留以供将来使用。 因此,将一些T值用于RFID的目的并不违反ISO/IEC 7816-3的标准化,因此SIM卡可以灵活地用于常规系统中。 [0071] 如图。 图10是示出配备有具有RFID部分的SIM卡的移动终端的结构的示意图。 [0072] 参考数字 900 代表移动终端ME的处理器。 处理器的一个示例是可从高通公司获得的称为“移动处理器”的移动站调制解调器 (MSM) 芯片。 [0073] 参考数字 950 代表 SIM 卡。 具有RFID部分的SIM卡安装在移动终端中,以便用信号通知模式转换到RFID模式。 为此,一个CPU 912 , SIM 部分 914 和一个 RFID 部分 916 SIM卡的 950 仅在图 1 中说明。 10. SIM卡的已知组件 950 在图 1 中未示出。 10. [0074] SIM 部分 914 是用户信息处理部分,用于存储用户信息并生成包括用户信息的用户信息信号。 此外,用户信息处理部分包括用于存储用户信息的用户信息存储部分和具有生成用户信息信号的程序的用户程序存储部分。 用户信息存储部分包括 EEPROM 404 用户程序存储器部分包括 ROM 410 ,如图所示。 3. 另外,用户信息存储部分包括 EEPROM 506 用户程序存储器部分包括 ROM 504 如图所示。 4. [0075]RFID部分 916 是RFID信息处理部分,能够存储和处理RFID数据并生成包括RFID数据的RFID信号。 此外,RFID信息处理部分包括用于存储RFID信息的RFID信息存储部分和用于生成RFID信号的RFID功能部分。 可在 EEPROM 中提供 RFID 信息存储部分 404 或只读存储器 410 , RFID功能部分包括RFID CODEC部分 406 和 RFID 调制部分 410 如图所示。 3.另外,可在EEPROM中提供RFID信息存储部分 506 或只读存储器 504 , RFID功能部分包括RFID CODEC部分 508 和 RFID 调制部分 510 ,如图所示。 4. [0076] 中央处理器 912 是主计算部分,连接到用户信息处理部分以命令生成用户信息信号以发送用户信息信号,并连接到RFID信息处理部分以命令生成RFID信号以发送 射频识别信号。 中央处理器 912 对应CPU 402 如图所示。 3和CPU 500 如图所示。 4. [0077] 当RFID询问器(未示出)在预定距离内接近移动终端MT时,RFID部分 916 SIM卡的 950 安装在移动终端 MT 中检测到 RFID 询问器的接近。 在检测到 RFID 询问器后,RFID 部分 916 将检测数据传输到 CPU 912 SIM卡的 950 使 SIM 卡 950 认识到必须执行 RFID 功能。 因此,CPU 912 SIM卡的 950 向处理器发送信号 900 将移动终端的模式转换为RFID模式。 另外,SIM卡的一种模式 950 转换成RFID功能模式以执行RFID功能。 [0078] 根据本发明,移动终端可以向RFID功能块提供稳定的时钟和稳定的电源,而不是从RFID询问器接收电力或向使用线圈连接部分并提取时钟的功能块提供时钟 来自 RFID 读写器发送的载波信号,从而稳定系统。 如果载波信号和感应电动势劣化,传统系统可能会因射频馈电环境而变得不稳定。 [0079] 如上所述,本发明利用SIM卡执行RFID功能的优点包括: [0080] 首先,SIM卡可以可拆卸地安装在移动终端中以执行RFID功能,但是作为重要事项的移动终端的便携性和小型化并没有因此得到改善。 如果RFID标签与SIM卡分开制作,移动终端可能无法满足便携性和小型化的要求。 [0081] 其次,在功能方面,本发明可以对传统的SIM卡进行升级,从而可以为SIM卡创造新的需求。 [0082] 第三,由于通过SIM卡提供了RFID技术,先进的RFID技术可以应用于传统的移动通信系统。 如果RFID标签与SIM卡分开制作,RFID标签可能会固定在移动终端中,因此很难将先进的RFID技术应用到移动终端中。 [0083] 第四,通过管理SIM卡向订户提供服务的服务提供商的盈利率可能会增加。 这是因为在SIM卡中采用了作为新服务基础的RFID技术,使得可以提供基于传统支付收费系统和传统用户管理系统的附加技术。 如果RFID标签与SIM卡分开制造,则难以提供利用RFID标签的新服务,导致服务提供商的盈利率下降。 [0084]尽管本发明已经参照其某些优选实施例进行了展示和描述,但本领域技术人员将理解,在不背离所定义的本发明的精神和范围的情况下,可以对其中的形式和细节进行各种改变 根据所附权利要求。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.278 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?,?,?,?,?,?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.279 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: CN100342393C(String), CN1627321A(String), EP1536573A2(String), EP1536573A3(String), EP1536573B1(String), JP2005166047A(String), KR100566260B1(String), KR1020050051508A(String), US20050116050A1(String), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.437 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?,?,?,?,?,?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.438 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: CN100342393C(String), CN1627321A(String), EP1536573A2(String), EP1536573A3(String), EP1536573B1(String), JP2005166047A(String), KR100566260B1(String), KR1020050051508A(String), US20050116050A1(String), US7374100B2(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.455 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.490 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), CN100342393C(String), CN1627321A(String), EP1536573A2(String), EP1536573A3(String), EP1536573B1(String), JP2005166047A(String), KR100566260B1(String), KR1020050051508A(String), US20050116050A1(String), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.509 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), CN100342393C(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.544 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.545 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), CN1627321A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.578 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), EP1536573A2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.614 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.615 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), EP1536573A3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.650 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), EP1536573B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.686 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), JP2005166047A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.720 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.721 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), KR100566260B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.756 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), KR1020050051508A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.791 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), US20050116050A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.826 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271687(Integer), US7374100B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.861 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.862 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US7374100B2(String), US7374100B2(String), 1211212800(Integer), 271687(Integer), 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.897 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.898 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.898 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.944 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.945 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.977 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:36.978 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186019(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.012 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186019(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.047 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.048 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.081 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.082 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186019(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.115 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.116 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 186019(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.150 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.168 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.168 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.168 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.185 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.186 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.203 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.204 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.221 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.255 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.256 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.272 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.273 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186019(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.462 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US9986457B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.804 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, publictodate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.805 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Mobile terminal device, wireless communication method for mobile terminal device, carrier server device, and communication speed control method in carrier server device(String), 移动终端设备、移动终端设备的无线通信方法、运营商服务器设备以及运营商服务器设备中的通信速度控制方法(String), US9986457B2(String), Excellent communication is to be enabled even in a communication environment with poor line quality. A mobile terminal acquires communication state information indicating a state of communication with a base station, and sends this communication state information to a carrier server device through the base station. The carrier server device receives this communication state information, and, based on this communication state information, controls the communication speed of content data to be transmitted from a web server to the mobile terminal device through the base station. The carrier server device sends this content data having the controlled communication speed to the mobile terminal through the base station.(String), 即使在线路质量较差的通信环境中也能实现出色的通信。 移动终端获取表示与基站的通信状态的通信状态信息,并通过基站将该通信状态信息发送给运营商服务器设备。 运营商服务器设备接收该通信状态信息,并且基于该通信状态信息,控制要从网络服务器通过基站发送到移动终端设备的内容数据的通信速度。 运营商服务器设备通过基站将该具有受控通信速度的内容数据发送到移动终端。(String), US14/901691(String), 1402848000(Integer), US9986457B2(String), 1527523200(Integer), 1527523200(Integer), 美国(String), 4(Integer), JP(String), 2(Integer), 19(Integer), JP2010080135A | JP2012151769A | JP2013148182A | JP2014007328A | JP2014083008A | JPWO2012176771A1 | US20020101827A1 | US20030191856A1 | US20060140369A1 | US20070115796A1 | US20100113037A1 | US20120166665A1 | US20130016221A1 | US20130215813A1 | US20140105035A1 | US20140241161A1 | US6185414B1 | US6757245B1 | US8340678B1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.839 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.840 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186020(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:37.986 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\5deb9a43f1624d25b038e36d310ba8c2.png(String), 186020(Integer), 5deb9a43f1624d25b038e36d310ba8c2.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.022 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, publictodate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.039 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Mobile terminal device, wireless communication method for mobile terminal device, carrier server device, and communication speed control method in carrier server device(String), 移动终端设备、移动终端设备的无线通信方法、运营商服务器设备以及运营商服务器设备中的通信速度控制方法(String), US9986457B2(String), Excellent communication is to be enabled even in a communication environment with poor line quality. A mobile terminal acquires communication state information indicating a state of communication with a base station, and sends this communication state information to a carrier server device through the base station. The carrier server device receives this communication state information, and, based on this communication state information, controls the communication speed of content data to be transmitted from a web server to the mobile terminal device through the base station. The carrier server device sends this content data having the controlled communication speed to the mobile terminal through the base station.(String), 即使在线路质量较差的通信环境中也能实现出色的通信。 移动终端获取表示与基站的通信状态的通信状态信息,并通过基站将该通信状态信息发送给运营商服务器设备。 运营商服务器设备接收该通信状态信息,并且基于该通信状态信息,控制要从网络服务器通过基站发送到移动终端设备的内容数据的通信速度。 运营商服务器设备通过基站将该具有受控通信速度的内容数据发送到移动终端。(String), US14/901691(String), 1402848000(Integer), US9986457B2(String), 1527523200(Integer), 1527523200(Integer), 美国(String), 3(Integer), 4(Integer), JP(String), 2(Integer), 19(Integer), JP2010080135A | JP2012151769A | JP2013148182A | JP2014007328A | JP2014083008A | JPWO2012176771A1 | US20020101827A1 | US20030191856A1 | US20060140369A1 | US20070115796A1 | US20100113037A1 | US20120166665A1 | US20130016221A1 | US20130215813A1 | US20140105035A1 | US20140241161A1 | US6185414B1 | US6757245B1 | US8340678B1(String), \20230420\5deb9a43f1624d25b038e36d310ba8c2.png(String), 12(Integer), 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.075 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.076 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.109 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.111 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.111 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 1. A mobile terminal device comprising:processing circuitry configured to acquire communication state information indicating a state of communication with a base station;a transmitter configured to transmit the communication state information to a carrier server device through the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas, off-line areas, or crowd density information; anda receiver configured to receive content data from a provider server through the carrier server device and the base station, while a communication speed is controlled based on the communication state information,wherein the processing circuitry is further configured to receive updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, andwherein when the updated communication speed corresponds to data size reduction, a data size reduction history is generated, wherein the carrier server device calculates a reward for the provider server based on the data size reduction history.(String), 1.移动终端设备包括:处理电路,被配置为获取指示与基站的通信状态的通信状态信息;发送器,被配置为通过基站向运营商服务器设备发送通信状态信息,其中通信状态信息基于由运营商服务器设备提供给移动终端设备的数据库来更新,其中数据库被提供给移动设备终端设备基于移动终端设备的位置,数据库为在线区域、离线区域或人群密度信息的数据库;和接收器被配置为通过运营商服务器设备和基站从提供商服务器接收内容数据,同时基于通信状态信息控制通信速度,其中,处理电路还被配置为基于移动终端设备的特定动作接收更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时隙,和其中,当更新的通信速度对应于数据大小减少时,生成数据大小减少历史,其中运营商服务器设备基于数据大小减少历史计算对提供商服务器的奖励。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.111 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 2. The mobile terminal device according to claim 1, wherein the communication state information is an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value.(String), 2.如权利要求1所述的移动终端装置,其中通信状态信息为根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计线路速度与阈值进行比较得到的线路质量信息。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.111 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 3. The mobile terminal device according to claim 1, wherein the processing circuitry is further configured to set a time-out period related to connection to the provider server or downloading of the content data from the provider server based on the communication state information.(String), 3.根据权利要求1所述的移动终端设备,其中处理电路还被配置为基于通信状态信息设置与连接到提供商服务器或从提供商服务器下载内容数据相关的超时期限。4、一种移动终端设备的无线通信方法,包括:信息获取步骤,获取表示与基站的通信状态的通信状态信息;信息传输步骤,通过基站向运营商服务器设备传输通信状态信息,其中通信状态信息基于运营商服务器设备提供给移动终端设备的数据库进行更新,其中数据库被提供给移动终端设备基于移动终端设备的位置和数据库是在线区域离线区域数据库,或者人群密度信息;和数据接收步骤,通过运营商服务器设备和基站从供应商服务器接收内容数据,同时基于通信状态信息控制通信速度,进一步的信息获取步骤,基于移动终端设备的特定动作接收更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时间段,以及其中,当更新的通信速度对应于数据大小减少时,生成数据大小减少历史,其中运营商服务器设备基于数据大小减少历史计算对提供商服务器的奖励。(String), 1(Integer), 2(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 4. A wireless communication method for a mobile terminal device, comprising:an information acquisition step of acquiring communication state information indicating a state of communication with a base station;an information transmission step of transmitting the communication state information to a carrier server device through the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas off-line areas, or crowd density-information; anda data reception step of receiving content data from a provider server through the carrier server device and the base station, while a communication speed is controlled based on the communication state information,a further information acquisition step of receiving updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, andwherein when the updated communication speed corresponds to data size reduction, a data size reduction history is generated, wherein the carrier server device calculates a reward for the provider server based on the data size reduction history.(String), 5.运营商服务器设备包括:接收器被配置为通过基站从移动终端设备接收通信状态信息,通信状态信息指示与基站的通信状态,其中通信状态信息基于提供给移动终端设备的数据库被更新运营商服务器设备,其中数据库是根据移动终端设备的位置提供给移动终端设备的,数据库是在线区域、离线区域或人群密度信息的数据库。和处理电路,配置为基于通信状态信息控制内容数据的通信速度,内容数据通过基站从供应商服务器发送到移动终端设备,处理电路还被配置为基于移动终端设备的特定动作提供更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时隙,以及其中,当更新的通信速度对应于数据大小减少时,生成数据大小减少历史,其中处理电路基于数据大小减少历史计算提供者服务器的奖励。(String), 0(Integer), 3(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 5. A carrier server device comprising:a receiver configured to receive communication state information from a mobile terminal device through a base station, the communication state information indicating a state of communication with the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas, off-line areas, or crowd density information; andprocessing circuitry configured to control a communication speed of content data based on the communication state information, the content data being transmitted from a provider server to the mobile terminal device through the base station,the processing circuitry further configured to provide updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, andwherein when the updated communication speed corresponds to data size reduction, a data size reduction history is generated, wherein the processing circuitry calculates a reward for the provider server based on the data size reduction history.(String), 6.根据权利要求5所述的运营商服务器设备,其中通信状态信息为根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计线路速度与阈值进行比较得到的线路质量信息。(String), 0(Integer), 4(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 6. The carrier server device according to claim 5, wherein the communication state information is an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value.(String), 7.根据权利要求5所述的运营商服务器设备,其中处理电路还被配置为将通信状态信息所指示的通信状态划分为多个等级,以及根据各个级别控制通信速度。(String), 1(Integer), 5(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 7. The carrier server device according to claim 5, wherein the processing circuitry is further configured todivide the communication state indicated by the communication state information into a plurality of levels, andcontrol the communication speed in accordance with the respective levels.(String), 8.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为根据内容的细节改变通信速度的控制值。(String), 1(Integer), 6(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 8. The carrier server device according to claim 5, wherein the processing circuitry is configured to change a control value for the communication speed in accordance with specifics of content.(String), 9.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为根据移动终端设备的用户的动作的细节改变通信速度的控制值。(String), 1(Integer), 7(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 9. The carrier server device according to claim 5, wherein the processing circuitry is configured to change a control value for the communication speed in accordance with specifics of an action of a user of the mobile terminal device.(String), 10.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为当更新的通信速度对应于数据大小时减小要通过基站发送到移动终端设备的内容数据的大小。(String), 1(Integer), 8(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 10. The carrier server device according to claim 5, wherein the processing circuitry is configured to reduce size of the content data to be transmitted to the mobile terminal device through the base station, when the updated communication speed corresponds to data size reduction.(String), 11.根据权利要求5所述的运营商服务器设备,其中处理电路被配置为根据通信状态信息判断线路质量是否良好,在线路质量好的情况下,将优惠券设置为可用状态,不限制通信速度,以及当线路质量不好时,将优惠券设置为不可用状态,并将通信速度限制在预定值。12、一种运营商服务器设备中的通信速度控制方法,包括:信息接收步骤,通过基站从移动终端设备接收通信状态信息,通信状态信息指示与基站的通信状态,其中通信状态信息基于提供给移动终端设备的数据库被更新由运营商服务器设备,其中数据库是根据移动终端设备的位置提供给移动终端设备的,数据库是在线区域、离线区域或人群密度信息的数据库。和速度控制步骤,控制当内容数据通过基站从供应商服务器发送到移动终端设备时的通信速度,该通信速度基于通信状态信息被控制,通信速度提供步骤,基于移动终端设备的特定动作提供更新的通信速度,其中移动终端设备的特定动作包括经常观看预定类型的内容的位置或时间段,以及奖励计算步骤,当更新的通信速度对应于数据量减少时,生成数据量减少历史,其中基于数据量减少历史计算提供者服务器的奖励。(String), 1(Integer), 9(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.112 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 11. The carrier server device according to claim 5, wherein the processing circuitry is configured todetermine whether line quality is good based on the communication state information,set a coupon into a usable state and not restrict the communication speed when the line quality is good, andset the coupon into an unusable state and restrict the communication speed to a predetermined value when the line quality is not good.(String), 1(Integer), 10(Integer), 4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.113 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186020(Integer), 12. A communication speed control method in a carrier server device, comprising:an information reception step of receiving communication state information from a mobile terminal device through a base station, the communication state information indicating a state of communication with the base station, wherein the communication state information is updated based on a database provided to the mobile terminal device by the carrier server device, wherein the database is provided to the mobile terminal device based on a location of the mobile terminal device and the database is a database of on-line areas, off-line areas, or crowd density information; anda speed control step of controlling a communication speed at a time when content data is transmitted from a provider server to the mobile terminal device through the base station, the communication speed being controlled based on the communication state information,a communication speed providing step of providing updated communication speed based on a specific action of the mobile terminal device, wherein the specific action of the mobile terminal device includes a location or a time slot in which a predetermined type of content is often viewed, anda reward calculating step of, when the updated communication speed corresponds to data size reduction, generating a data size reduction history, wherein a reward is calculated for the provider server based on the data size reduction history.(String), 0(Integer), 11(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.366 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.383 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186020(Integer), TECHNICAL FIELD [0001]The present technology relates to a mobile terminal device, a wireless communication method for a mobile terminal device, a carrier server device, and a communication speed control method in a carrier server device. BACKGROUND ART [0002]In conventional cellular networks or Wireless Local Area Networks (WLANs), service quality is secured by controlling error rates and transmission speeds by varying control parameters in the physical layers (PHY) in accordance with the states of wireless transmission paths, or controlling retransmission and congestion through Medium Access Control (MAC). However, the control is not sufficient. [0003]In a communication environment with poor line quality, throughput is low. For example, Patent Document 1 discloses a method of measuring or estimating line quality. In an environment with low throughput, services are preferably provided at low prices. In an environment with high throughput, services are preferably provided at high prices. [0004]There have been systems with which speed restrictions are lifted upon payment of additional charge (with a coupon). For example, a user pays for the coupon, and manually validates the coupon on the Internet through a personal computer (PC), so that the speed restrictions are lifted. CITATION LIST Patent Document [0005]Patent Document 1: JP 2011-10267 A SUMMARY OF THE INVENTION Problems to be Solved by the Invention [0006]The present technology aims to enable excellent communication even in a communication environment with poor line quality. Solutions to Problems [0007]A concept of the present technology lies in a mobile terminal device that includes: [0008]an information acquiring unit that acquires communication state information indicating a state of communication with a base station; [0009]an information transmitting unit that transmits the communication state information to a carrier server device through the base station; and [0010]a data receiving unit that receives content data from a web server through the carrier server device and the base station, while a communication speed is controlled based on the communication state information. [0011]In the present technology, the information acquiring unit acquires the communication state information indicating a state of communication with the base station. For example, the communication state information may be an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value. The information transmitting unit sends the communication state information to the carrier server device through the base station. While the communication speed is controlled based on the communication state information, the data receiving unit receives content data from the web server through the carrier server device and the base station. [0012]As described above, in the present technology, the communication state information indicating a communication state with the base station is acquired, and is transmitted to the carrier server device. Accordingly, the communication speed of the content data to be transmitted from the web server can be set in accordance with the communication state information, and excellent communication can be conducted even in a communication environment with poor line quality. That is, the wireless resource that can be allotted to other users can be increased, and line load can be reduced, for example. Also, the most basic communication environment is provided, so that a more stable system can be established, for example. [0013]In the present technology, the mobile terminal device may further include a time-out period setting unit that sets a time-out period related to connection to the web server or downloading of the content data from the web server based on the communication state information, for example. In this case, the time-out period is shortened in an environment with poor line quality, for example, and accordingly, unnecessarily long occupation of a wireless line is prevented. [0014]Another concept of the present technology lines in a carrier server device that include: [0015]an information receiving unit that receives communication state information from a mobile terminal device through a base station, the communication state information indicating a state of communication with the base station; and [0016]a speed control unit that controls a communication speed at a time when content data is sent from a web server to the mobile terminal device through the base station, the communication speed being controlled based on the communication state information. [0017]In the present technology, from the mobile terminal device through the base station, the information receiving unit receives the communication state information indicating a state of communication with this base station. For example, the communication state information may be an estimated line speed estimated from a congestion degree and an interference wave intensity, and/or line quality information obtained by comparing the estimated line speed with a threshold value. [0018]Based on the communication state information, the speed control unit controls the communication speed at a time when content data is transmitted from the web server to the mobile terminal device through the base station. For example, the speed control unit may divide the communication state indicated by the communication state information into more than one level, and control the communication speed in accordance with the respective levels. [0019]As described above, in the present technology, the communication speed at a time when content data is sent from the web server to the mobile terminal device through the base station is controlled based on the communication state information indicating a state of communication between the mobile terminal device and the base station. Accordingly, the communication speed of the content data to be transmitted from the web server can be set in accordance with the communication state information, and excellent communication can be conducted even in a communication environment with poor line quality. That is, the wireless resource that can be allotted to other users can be increased, and line load can be reduced, for example. Also, the most basic communication environment is provided, so that a more stable system can be established, for example. [0020]In the present technology, the speed control unit may change the control value for the communication speed in accordance with the specifics of content, for example. Also, the speed control unit may change the control value for the communication speed in accordance with the specifics of an action of the user of the mobile terminal device, for example. With this, the mobile terminal device can acquire content data at the communication speed in accordance with the specifics of the content or the specifics of an action of the user. [0021]In the present technology, the carrier server device may further include a data size control unit that reduces the size of the content data to be transmitted to the mobile terminal device through the base station, when the speed control unit controls the communication speed to become lower, for example. With this, the time required for transmitting content data can be shortened, and long occupation of the wireless resource can be prevented. [0022]In the present technology, the speed control unit may also determine whether line quality is good based on the communication state information, set a coupon into a usable state and not restrict the communication speed when the line quality is good, and set the coupon into an unusable state and restrict the communication speed to a predetermined value when the line quality is not good, for example. In this case, the coupon is automatically put into the unusable state when the communication environment is degraded. Thus, a fee structure that is satisfactory to users can be provided. Effects of the Invention [0023]According to the present technology, excellent communication can be conducted even in a communication environment with poor line quality. That is, the wireless resource that can be allotted to other users can be increased, and line load can be reduced, for example. Also, the most basic communication environment is provided, so that a more stable system can be established, for example. The advantageous effects described in this specification are merely examples, and the advantageous effects of the present technology are not limited to them and may include additional effects. BRIEF DESCRIPTION OF DRAWINGS [0024]FIG. 1 is a block diagram showing an example configuration of a mobile-phone system as an embodiment. [0025]FIG. 2 is a diagram showing an example structure of a mobile terminal. [0026]FIG. 3 is a diagram for explaining the function units at least included in the mobile terminal and the carrier server. [0027]FIG. 4 is a diagram showing an example of a charge screen that is displayed on the mobile terminal when a user performs an operation to increase the remaining amount in a coupon with this mobile terminal. [0028]FIG. 5 is a flowchart showing an example of the procedures in a process of putting the coupon into an on- or off-state. [0029]FIG. 6 is a diagram showing an example of the service parameters that are stored and managed in a parameter management table. [0030]FIG. 7 is a diagram schematically showing an example configuration of a speed control system in the carrier server. [0031]FIG. 8 is a diagram schematically showing an example configuration of a speed control system in a case where a set speed R0 is changed in accordance with the specifics of content (content type, priority, and the like). [0032]FIG. 9 is a diagram schematically showing an example configuration of a speed control system in a case where the set speed R0 is changed in accordance with the specifics of an action of the user. [0033]FIG. 10 is a diagram schematically showing an example configuration of a data size control system. [0034]FIGS. 11(a) to 11(c) are diagrams for explaining a structure for enabling a data size reduction process on the side of the provider server. [0035]FIG. 12 is a diagram for explaining a business model in which a mobile-phone operator pays a reward to a provider. MODES FOR CARRYING OUT THE INVENTION [0036]The following is a description of a mode for carrying out the invention (the mode will be hereinafter referred to as the “embodiment”). Explanation will be made in the following order. [0037]1. Embodiment [0038]2. Modifications 1. Embodiment [0039][Example Configuration of a Mobile-Phone System] [0040]FIG. 1 shows an example configuration of a mobile-phone system 10 as an embodiment. This mobile-phone system 10 includes: a communication network 11 of the telecommunications carrier that runs this mobile-phone system; a base station 12 of the mobile-phone system; and a mobile terminal 13 of each subscriber who subscribes to the mobile-phone system. [0041]This mobile-phone system 10 also includes a carrier server (proxy server) 15 that controls connection between the communication network 11 and the Internet 15. A server (provider server) 16 of an Internet provider to which the user of the mobile terminal 13 subscribe is connected as a web server to the Internet 15, for example. [0042]FIG. 2 shows an example structure of the mobile terminal 13. This mobile terminal 13 includes an antenna 101, a communication interface unit (communication I/F unit) 102, a control unit 103, and a user interface unit (user I/F unit) 104. [0043]The antenna 101 receives radio waves from the base station 12, outputs the received signal to the communication I/F unit 102, and outputs a signal from the communication I/F unit 102 in the form of radio waves. The communication I/F unit 102 is an interface for conducting communication (data communication) with the base station 12, and establishes a link to the base station 12 or cuts off an established link to the base station 12. [0044]The control unit 103 is formed with a CPU, a ROM, a RAM, and the like, and controls operation of the entire device. The user I/F unit 104 is formed with a keyboard, a tablet, an input pen, a display, or a speaker, for example, and receives an information input from the user, supplies the information input to the control unit 103, and, to the user, presents information supplied from the control unit 103. [0045]FIG. 3 shows the function units at least included in the mobile terminal 13 and the carrier server 14. The mobile terminal 13 includes an information acquiring unit 131, an information transmitting unit 132, a data receiving unit 133, and a time-out period setting unit 134. The information acquiring unit 131 acquires communication state information indicating a state of communication with the base station 12. In this embodiment, the communication state information may be an estimated line speed Ro estimated from a congestion degree and an interference wave intensity, and/or a line quality flag Fq obtained by comparing the estimated line speed Ro with a threshold value Rt, for example. [0046]The estimated line speed Ro is now explained. In estimating a line speed, (1) line quality, or a signal-to-interference ratio (SIR) of a signal from the base station 12, is determined, (2) the maximum speed corresponding to this SIR is determined, and (3) an effective communication rate is determined at last. [0047]Here, the line quality is calculated from a congestion degree and an interference wave intensity. The congestion degree is the ratio of the occupied bandwidth to the allowed bandwidth of the base station. The interference waves are signals from other base stations in the neighborhood, and are the interference waves that reach the terminal. Even where the congestion degree is low, if the interference waves are strong, the congestion degree appears to be equivalently high. The maximum speed is determined from a speed table that is specified in accordance with the line quality and the wireless system specifications, for example. The effective communication rate is calculated by applying a certain conversion formula to the maximum speed. This effective communication rate calculation is disclosed in JP 2012-9987 A, for example. The congestion degree Kcong in this publication is a congestion degree in a broad sense including interference waves, and is equivalent to line quality. Further, the SIR indicates the SIR of the reference signal (that is, SIR_CPICH), and reflects the excess bandwidth of the base station, rather than simply reflecting signal intensity. In LTE, a value called Reference Signal Received Quality (RSRQ) may also be used. [0048]Next, the line quality flag Fq is explained. The line quality flag Fq is obtained by comparing the estimated line speed Ro with the threshold value Rt. For example, where Ro>Rt, Fq is set to “1”, and “line quality is good” is displayed. Where Ro≤Rt, on the other hand, Fq is set to “0”, and “line quality is not good” is displayed. [0049]Here, the threshold value Rt is a constant value of 150 kbps, for example. Alternatively, this threshold value Rt may be determined based on a frequency distribution graph of transmission speeds used by the user. For example, in a case where the frequency distribution is polarized, the threshold value Rt is determined to be the intermediate value. Also, the threshold value Rt may be determined to be the standard deviation σ or a value a predetermined number of times larger than the standard deviation σ. Alternatively, frequency distribution graphs may be created for the respective types of content viewed by the user, and threshold values may be determined for the respective types of content. In this case, the line quality flag Fq is obtained for each of the types of content. [0050]Instead of the two-valued line quality flag Fq, a multivalued line quality index Iq may be used. The line quality index Iq is obtained by comparing the estimated line speed Ro with more than one threshold value Rt. [0051]The line quality information (the line quality flag Fq or the line quality index Iq) may be incremented or decremented with the use of a database supplied from the carrier server 14, for example. This database is a database of off-line areas (poor reception areas), on-line areas (good reception areas), or crowd density information. Current location information obtained by a GPS function (not shown) of the mobile terminal 13 is transmitted to the carrier server 14, so that the carrier server 14 can recognize where the user is located, and provide an appropriate database to the mobile terminal 13. [0052]The line quality information varies with time. If there is statistical information indicating that the line is often congested or the line quality is often poor in that area according to statistics, the statistical information can be used as previous knowledge that, even if the line quality information indicates good quality at the moment, the line quality tends to soon deteriorate. In such a location, good line quality cannot be expected to last long, and therefore, the line quality index Iq is downgraded, for example. [0053]The information transmitting unit 132 sends the communication state information acquired by the information acquiring unit 131 to the carrier server 14 through the base station 12. While the communication speed is controlled based on the communication state information, the data receiving unit 133 receives content data from the provider server 16 through the carrier server device 14 and the base station 12. [0054]Based on the communication state information, the time-out period setting unit 134 sets a time-out period related to connection to the provider server 16 (connection time-out period), and a time-out period related to downloading of content data from the provider server 16 (communication completion time-out period). The set value of this time-out period exists in an HTTP module in the mobile terminal 13. [0055]If the communication state is not good in this case, the time-out period is shortened. For example, the time-out period is set at two or more, or three or more levels, so that, as the estimated line speed becomes lower, the time-out period becomes shorter. With this, the time-out period is shortened in an environment with poor line quality, and accordingly, unnecessarily long occupation of the wireless line is prevented. Such a time-out period can also be set in the carrier server 14. [0056]Meanwhile, the carrier server 14 includes an information receiving unit 141, a data transmitting unit 142, a speed control unit 143, a data size control unit 144, and a parameter managing unit 145. From the mobile terminal 13 through the base station 12, the information receiving unit 141 receives the communication state information indicating a state of communication with this base station 12. As described above, this communication state information is the estimated line speed Ro calculated from a congestion degree and an interference wave intensity, and/or the line quality information (the line quality flag Fq or the line quality index Iq) obtained by comparing the estimated line speed Ro with the threshold value Rt. The data transmitting unit 142 transmits content data from the provider server 16 having its communication speed and data size controlled as necessary, to the mobile terminal 13 via the base station 12. [0057]Based on the communication state information received by the information receiving unit 141, the speed control unit 143 controls the communication speed at which content data is transmitted from the provider server 16 to the mobile terminal 13 through the base station 12. The speed control unit 143 determines the line quality information (the line quality flag Fq or the line quality index Iq) from the estimated line speed Ro as the communication state information in the same manner as in the above described mobile terminal 13, and controls the communication speed based on this line quality information. Alternatively, the speed control unit 143 controls the communication speed based on the line quality information (the line quality flag Fq or the line quality index Iq) as the communication state information. [0058]In this case, the communication speed is controlled to be set at two or more, or three or more levels. For example, the communication speed is controlled to be set at two levels depending on whether the estimated line speed Ro is higher than the threshold value Rt. In a case where the threshold value Rt is 150 kbps, for example, the speed control unit 143 restricts the communication speed to 150 kbps when Ro≤Rt and the line quality is not good, but does not restrict the communication speed when Ro>Rt and the line quality is good. [0059]In this case, the coupon is in an off-state (unusable state) when Ro≤Rt, and the coupon is in an on-state (usable state) when Ro>Rt. It should be noted that the coupon can be used only when there is a remaining amount in the coupon. FIG. 4 shows an example of a charge screen that is displayed on the mobile terminal 13 when the user performs an operation to increase the remaining amount in the coupon with this mobile terminal 13, for example. As the user places a check in a desired item in the check column, and presses the charge button, the remaining amount in the coupon is increased. [0060]The flowchart in FIG. 5 shows an example of the procedures in the process of putting the coupon into an on- or off-state. In step ST1, the speed control unit 143 starts the process, and then moves on to the procedure in step ST2. In step ST2, the speed control unit 143 determines whether there is a remaining amount in the coupon. [0061]If there is a remaining amount in the coupon, the speed control unit 143 in step ST3 determines whether Ro>Rt. If Ro>Rt, the speed control unit 143 in step ST4 puts the coupon into the on-state (usable state). In this state, the speed control unit 143 does not restrict the communication speed. After that, the speed control unit 143 in step ST6 ends the process. [0062]If not Ro>Rt, on the other hand, the speed control unit 143 in step ST5 puts the coupon into the off-state (unusable state). In this state, the speed control unit 143 restricts the communication speed to 150 kbps. After that, the speed control unit 143 in step ST6 ends the process. [0063]Even where the coupon is in the on-state (usable state), if all the remaining amount in the coupon is spent on usage of the line, the speed control unit 143 immediately puts the coupon into the off-state (unusable state), and restricts the communication speed to 150 kbps. [0064]The parameter managing unit 145 manages the service parameters of each user, using a parameter management table. FIG. 6 shows an example of the service parameters that are stored and managed in the parameter management table. In this example, the remaining amount in the coupon and the coupon status are managed under the user ID. [0065]FIG. 7 schematically shows an example configuration of a speed control system 150 in the carrier server 14. This speed control system 150 includes a switch 151, a transmission speed measuring unit 152, and a control unit 153. The transmission speed measuring unit 152 measures the number R1 of bytes per second in content data flowing from the provider server 16 into the mobile terminal 13, for example. The control unit 153 compares the measured number R1 of bytes with a set speed R0, and controls switching on and off of the switch 151 based on the comparison result, so that R1 becomes equal to R0. [0066]Although the communication speed is not restricted when the coupon is in the on-state in the above description, the value of the communication speed may be restricted when the coupon is in the on-state. Although the communication speed is restricted to 150 kbps when the coupon is in the off-state in the above description, the speed value may be more finely restricted. [0067]Normally, the set speed R0 is determined by the ratio between a content size and an expected reaction time. The content size and the expected reaction time are determined by the type of the content and the state of the user. For example, the speed control unit 143 may change the set speed R0 in accordance with the specifics of the content (content type or priority). With this, the reaction time corresponding to the content type or priority (the time until web pages become available for access) can be achieved. For example, the data size is normally small in the case of text content, and the data size is normally large in the case of image content. Therefore, the set speed R0 is reduced in the case of text content, and the set speed R0 is increased in the case of image content. Also, as for the same image content, the priority is determined to be higher if the user is more interested in the image content, and the set speed R0 is made higher if the priority is higher, for example. [0068]FIG. 8 schematically shows an example configuration of a speed control system 150A in a case where the set speed R0 is changed in accordance with the specifics of content (content type, priority, and the like). In FIG. 8, the components equivalent to components shown in FIG. 7 are denoted by the same reference numerals as those used in FIG. 7, and detailed explanation of them is not repeated herein. The speed control system 150A includes a switch 151, a transmission speed measuring unit 152, a control unit 153, a speed table 154, and a content analyzing unit 155. [0069]The content analyzing unit 155 identifies the specifics of content (content type, priority, and the like) by analyzing the content data flowing from the provider server 16 into the mobile terminal 13. The content analyzing unit 155 may identify the content type in accordance with the reference URL on the web page, the MIME format information in the http header, the address information in the http header or the IP header, data size information, or the like. Also, the content analyzing unit 155 may identify the content type in accordance with the extension of the reference URL, such as mp4, av, mov, or jpg. [0070]The content analyzing unit 155 may also identify priority by taking the user's situation into consideration. For example, the user often views entertainment information pages when in a residential area, and often view shop information pages when in a commercial area. Alternatively, the specifics of content (content, type, priority, and the like) may be identified on the side of the mobile terminal 13, and be transmitted to the carrier server 14. In that case, the content analyzing unit 155 becomes unnecessary. [0071]The result of the identification of the specifics of the content is supplied to the speed table 154. The speed table 154 outputs the set speed R0 corresponding to the result of the identification of the content specifics and the service status (the remaining amount in the coupon and the coupon status) (see FIG. 6) to the control unit 153. [0072]The speed control unit 143 may also change the set speed R0 in accordance with the specifics of an action of the user. For example, the specifics of an action of the user are identified based on the user information shown below. Specifically, the user information may be a timetable, a memorandum, a log-in ID, a log-in time, a log-in location, a log-out time, a log-out location, a purchase history, an access history, a history of locations of actions, area information (indicating an industrial area, a commercial area, a residential area, or a transportation facility), or the like. [0073]FIG. 9 schematically shows an example configuration of a speed control system 150B in a case where the set speed R0 is changed in accordance with the specifics of an action of the user. In FIG. 9, the components equivalent to components shown in FIG. 7 are denoted by the same reference numerals as those used in FIG. 7, and detailed explanation of them is not repeated herein. The speed control system 150B includes a switch 151, a transmission speed measuring unit 152, a control unit 153, a speed table 156, and a user action identifying unit 157. [0074]The user action identifying unit 157 identifies the specifics of an action of the user based on user information. For example, a place (a poor reception area or a good reception area) to which the user is now heading can be identified from a timetable. Also, a check can be made whether the user is located in a place or a time slot in which image content is often viewed, for example. [0075]The result of the identification of the specifics of an action of the user is supplied to the speed table 156. The speed table 156 outputs the set speed R0 corresponding to the result of the identification of the specifics of the action of the user and the service status (the remaining amount in the coupon and the coupon status) (see FIG. 6) to the control unit 153. [0076]Referring back to FIG. 3, the data size control unit 144 reduces the data size of content data to be transmitted from the provider server 16 to the mobile terminal 13 through the base station 12 based on the communication state information received by the information receiving unit 141. In a case where the estimated line speed Ro is equal to or lower than the threshold value Rt, and the communication speed is restricted to 150 kbps, for example, the data size is reduced. [0077]When web content includes an image or a moving image, for example, the data size control unit 144 performs control to reduce the data size by performing a process to reduce the resolution of the image or the moving image, or performing a process to remove the data of the image or the moving image. Also, the data size control unit 144 performs a process to reduce the data size of moving image content or image (still image) content, but does not perform the process on text content or mail, for example. That is, control is performed to reduce the data size in accordance with the viewing specifics. [0078]As the data size is reduced in the above manner, the time required for content data transmission can be shortened, and long occupation of the wireless resource can be prevented even in a case where the communication speed is restricted to a low value. [0079]FIG. 10 schematically shows an example configuration of a data size control system 160. The data size control system 160 includes a size reduction processing unit 161 and a content analyzing unit 162. The content analyzing unit 162 identifies the specifics of content (content type, content structure, and the like) by analyzing the content data flowing from the provider server 16 into the mobile terminal 13. [0080]In a case where the communication speed is restricted, the size reduction processing unit 161 performs a size reduction process based on the result of the determination on the content specifics. When web content includes an image or a moving image, for example, a process to reduce the resolution of the image or the moving image is performed, or a process to remove the data of the image or the moving image is performed, so that the data size is reduced. [0081]The data size reduction process may not be performed in the carrier server 14. Instead, communication speed restriction information or a data size reduction request may be sent from the carrier server 14 to the provider server 16, and the data size reduction process may be performed on the side of the provider server 16. [0082]FIG. 11(a) shows an example of web content including an image, a moving image, and the like. When there is no data size reduction request, the provider server 16 sends the web content shown in FIG. 11(a) to the mobile terminal 13, as shown in FIG. 11(b). When there is a data size reduction request, however, the provider server 16 sends the web content minus the image, the moving image, and the like of a large data size, to the mobile terminal 13, as shown in FIG. 11(c). [0083]It should be noted that the provider that runs the provider server 16 and the mobile-phone operator may be the same, or may not be the same. In a case where the provider and the mobile-phone operator are not the same, it is also possible to employ a business model that, when the data size reduction process is performed on the side of the provider server 16 as described above, the mobile-phone operator may pay a reward as a token of gratitude to the provider fo(String), 技术领域 [0001] 本 技术涉及移动终端设备、移动终端设备的无线通信方法、运营商服务器设备以及运营商服务器设备中的通信速度控制方法。 背景技术 [0002] 在传统的蜂窝网络或无线局域网 (WLAN) 中,通过根据无线传输路径的状态改变物理层 (PHY) 中的控制参数或控制重传和拥塞来控制错误率和传输速度来确保服务质量 通过媒体访问控制 (MAC)。 然而,控制是不够的。 [0003] 在线路质量较差的通信环境中,吞吐量较低。 例如,专利文献1公开了一种测量或估计线路质量的方法。 在吞吐量低的环境中,最好以低价提供服务。 在具有高吞吐量的环境中,优选地以高价格提供服务。 [0004] 有一些系统可以通过支付额外费用(使用优惠券)取消速度限制。 例如,用户支付优惠券,并通过个人计算机(PC)在互联网上手动验证优惠券,从而取消了速度限制。 引文清单 专利文献 [0005] 专利文献1:JP 2011-10267 A 发明内容 本发明要解决的问题 [0006] 本技术旨在即使在线路质量较差的通信环境中也能实现良好的通信。 问题解决方案 [0007] 本技术的一个概念在于一种移动终端设备,包括: [0008] 信息获取单元,获取指示与基站的通信状态的通信状态信息; [0009] 信息发送单元,通过基站将通信状态信息发送给运营商服务器装置; 和 [0010] 数据接收单元,其通过运营商服务器设备和基站从网络服务器接收内容数据,同时基于通信状态信息控制通信速度。 [0011] 在本技术中,信息获取单元获取指示与基站的通信状态的通信状态信息。 例如,通信状态信息可以是根据拥塞程度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较获得的线路质量信息。 信息发送单元通过基站向运营商服务器设备发送通信状态信息。 在基于通信状态信息控制通信速度的同时,数据接收单元通过运营商服务器设备和基站从网络服务器接收内容数据。 [0012] 如上所述,在本技术中,指示与基站的通信状态的通信状态信息被获取,并且被发送到运营商服务器设备。 因此,可以根据通信状态信息来设置要从网络服务器发送的内容数据的通信速度,并且即使在线路质量差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 [0013] 在本技术中,移动终端设备还可以包括超时时段设置单元,该超时时段设置单元基于通信状态信息设置与连接到网络服务器或从网络服务器下载内容数据相关的超时时间, 例如。 在这种情况下,例如,在线路质量差的环境中,超时周期被缩短,因此,防止了无线线路的不必要的长时间占用。 [0014]运营商服务器设备中的本技术线的另一个概念包括: [0015] 信息接收单元,通过基站从移动终端设备接收通信状态信息,该通信状态信息指示与基站的通信状态; 和 [0016] 速度控制单元,当内容数据通过基站从网络服务器发送到移动终端设备时控制通信速度,通信速度基于通信状态信息来控制。 [0017] 在本技术中,从移动终端装置通过基站,信息接收单元接收指示与该基站的通信状态的通信状态信息。 例如,通信状态信息可以是根据拥塞程度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较获得的线路质量信息。 [0018] 基于通信状态信息,速度控制单元在内容数据通过基站从网络服务器发送到移动终端设备时控制通信速度。 例如,速度控制单元可以将通信状态信息所指示的通信状态划分为多于一个级别,并根据各个级别来控制通信速度。 [0019] 如上所述,在本技术中,基于指示移动终端之间的通信状态的通信状态信息,控制通过基站从网络服务器向移动终端设备发送内容数据时的通信速度。 设备和基站。 因此,可以根据通信状态信息来设置要从网络服务器发送的内容数据的通信速度,并且即使在线路质量差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 [0020] 在本技术中,速度控制单元例如可以根据内容的具体情况改变通信速度的控制值。 此外,例如,速度控制单元可以根据移动终端设备的用户的动作的细节来改变通信速度的控制值。 由此,移动终端装置能够以与内容的内容或用户的动作的内容相应的通信速度来取得内容数据。 [0021] 在本技术中,运营商服务器设备还可以包括数据大小控制单元,当速度控制单元控制通信速度变得更低时,该数据大小控制单元减小要通过基站发送到移动终端设备的内容数据的大小。 , 例如。 由此,可以缩短发送内容数据所需的时间,并且可以防止无线资源的长时间占用。 [0022] 在本技术中,速度控制单元还可以根据通信状态信息判断线路质量是否良好,将优惠券设置为可用状态,在线路质量良好时不限制通讯速度,将优惠券设置为 例如,当线路质量不好时,将通信速度限制在不可用状态并限制在预定值。 在这种情况下,当通信环境恶化时,优惠券会自动进入不可用状态。 因此,可以提供用户满意的费用结构。 本发明的效果 [0023]根据本技术,即使在线路质量较差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 本说明书中描述的有益效果仅仅是示例,并且本技术的有益效果不限于它们并且可以包括附加效果。 附图说明 [0024] 图1是示出作为实施例的移动电话系统的示例配置的框图。 [0025] 图2是表示移动终端的结构例的图。 [0026] 图3是用于说明至少包含在移动终端和运营商服务器中的功能单元的图。 [0027] 图4是示出当用户使用移动终端执行增加优惠券中的剩余金额的操作时在移动终端上显示的收费画面的示例的图。 [0028] 图5是表示将优惠券设为开或关的处理的步骤的一个例子的流程图。 [0029] 图6是示出在参数管理表中存储和管理的服务参数的示例的图。 [0030] 图7是示意性地示出运营商服务器中的速度控制系统的示例配置的图。 [0031] 图8是示意性地表示设定速度R的情况下的速度控制系统的结构例的图。 0 根据内容的具体情况(内容类型、优先级等)改变。 [0032] 图9是示意性地表示设定速度R的情况下的速度控制系统的结构例的图。 0 根据用户动作的具体情况改变。 [0033] 图10是示意性地示出数据大小控制系统的示例配置的图。 [0034] 图11(a)~图11(c)是用于说明在提供者服务器侧能够进行数据大小削减处理的结构的图。 [0035] 图12是用于说明移动电话运营商向提供者支付报酬的商业模式的图。 实施本发明的方式 [0036] 以下是用于实施本发明的模式的描述(该模式将在下文中称为“实施例”)。 将按以下顺序进行说明。 [0037] 一、实施例 [0038] 2. 修改 一、实施例 [0039] [移动电话系统的示例配置] [0040] 图 1 显示了移动电话系统的示例配置 10 作为一个实施例。 这个手机系统 10 包括:通信网络 11 运行该移动电话系统的电信运营商; 一个基站 12 手机系统; 和一个移动终端 13 每个订阅移动电话系统的用户。 [0041] 这个手机系统 10 还包括一个运营商服务器(代理服务器) 15 控制通信网络之间的连接 11 和互联网 15 . 一个服务器(提供者服务器) 16 移动终端用户所在的互联网提供商的 13 subscribe 作为 Web 服务器连接到 Internet 15 , 例如。 [0042] 图2示出了移动终端的示例结构 13 . 这个移动终端 13 包括天线 101 ,一个通讯接口单元(通讯I/F单元) 102 , 一个控制单元 103 , 和一个用户接口单元(用户 I/F 单元) 104 . [0043] 天线 101 从基站接收无线电波 12 , 将接收到的信号输出到通信 I/F 单元 102 , 并从通信 I/F 单元输出信号 102 以无线电波的形式。 通讯接口单元102 是用于与基站进行通信(数据通信)的接口 12 ,并建立到基站的链接 12 或切断与基站的已建立链接 12 . [0044] 控制单元 103 由CPU、ROM、RAM等构成,控制装置整体的动作。 用户接口单元 104 由例如键盘、平板电脑、输入笔、显示器或扬声器构成,并接收来自用户的信息输入,将输入的信息提供给控制单元 103 ,并且,向用户呈现从控制单元提供的信息 103 . [0045] 图3示出了移动终端中至少包括的功能单元 13 和运营商服务器 14 . 移动终端 13 包括信息获取单元 131 , 一个信息传输单元 132 , 一个数据接收单元 133 , 和超时时间设置单元 134 . 信息获取单元 131 获取指示与基站的通信状态的通信状态信息 12 . 在本实施例中,通信状态信息可以是根据拥塞度和干扰波强度估计的估计线路速度Ro,和/或通过将估计的线路速度Ro与阈值Rt进行比较而获得的线路质量标志Fq,例如 . [0046] 现在解释估计的线速度Ro。 在估计线路速度时,(1)线路质量,或来自基站的信号的信干比(SIR) 12 , 确定, (2) 确定该 SIR 对应的最大速度, (3) 最后确定有效通信速率。 [0047] 这里,线路质量是根据拥塞度和干扰波强度计算的。 拥塞度是基站占用带宽与允许带宽之比。 干扰波是来自附近其他基站的信号,是到达终端的干扰波。 即使在拥塞度较低的地方,如果干扰波强,则拥塞度看起来也相当高。 例如,最大速度由根据线路质量和无线系统规范指定的速度表确定。 有效通信速率是通过对最大速度应用一定的换算公式来计算的。 例如,在JP 2012-9987 A中公开了这种有效通信速率计算。 本公报中的拥塞度Kcong是包括干扰波在内的广义的拥塞度,相当于线路质量。 进一步的,SIR表示参考信号的SIR(即SIR_CPICH),反映基站的超额带宽,而不是简单地反映信号强度。 在 LTE 中,也可以使用称为参考信号接收质量 (RSRQ) 的值。 [0048] 接着,说明线路质量标志Fq。 通过将估计的线路速度Ro与阈值Rt进行比较来获得线路质量标志Fq。 例如,在Ro>Rt的情况下,将Fq设置为“1”,并显示“线路质量好”。 另一方面,在Ro≤Rt的情况下,将Fq设为“0”,显示“线路质量不好”。 [0049] 这里,阈值Rt例如是150kbps的恒定值。 或者,该阈值Rt可以基于用户使用的传输速度的频率分布图来确定。 例如,在频率分布被极化的情况下,阈值Rt被确定为中间值。 此外,阈值Rt可以被确定为标准偏差σ或比标准偏差σ大预定倍数的值。 或者,可以针对用户观看的各个类型的内容创建频率分布图,并且可以针对各个类型的内容确定阈值。 在这种情况下,针对每种内容类型获得线路质量标志Fq。 [0050]代替二值线路质量标志Fq,可以使用多值线路质量指标Iq。 通过将估计的线路速度Ro与一个以上的阈值Rt进行比较来获得线路质量指数Iq。 [0051] 线路质量信息(线路质量标志Fq或线路质量指标Iq)可以通过使用从运营商服务器提供的数据库来增加或减少 14 , 例如。 该数据库是离线区域(接收不良区域)、在线区域(接收良好区域)或人群密度信息的数据库。 通过移动终端的GPS功能(未图示)获取的当前位置信息 13 被传送到运营商服务器 14 ,以便运营商服务器 14 可以识别用户所在的位置,并为移动终端提供合适的数据库 13 . [0052] 线路质量信息随时间变化。 如果有统计信息表明该区域的线路经常拥塞或者线路质量经常较差,则该统计信息可以作为先验知识,即使线路质量信息表明当前质量良好, 线路质量往往会很快恶化。 在这样的位置,不能期望良好的线路质量持续很长时间,因此,例如,线路质量指标Iq被降级。 [0053] 信息传递单元 132 发送信息获取单元获取的通信状态信息 131 到运营商服务器 14 通过基站 12 . 在基于通信状态信息控制通信速度的同时,数据接收单元 133 从提供者服务器接收内容数据 16 通过运营商服务器设备 14 和基站 12 . [0054] 基于通信状态信息,超时时间设置单元 134 设置与提供者服务器连接相关的超时时间 16 (连接超时时间),以及与从提供商服务器下载内容数据相关的超时时间 16 (通信完成超时时间)。 该超时时间的设定值存在于移动端的一个HTTP模块中 13 . [0055] 如果在这种情况下通信状态不好,则缩短超时时间。 例如,超时时间被设置为两个或更多,或者三个或更多级别,使得随着估计的线速度变得更低,超时时间变得更短。 由此,在线路质量差的环境中,超时时间被缩短,因此,防止了无线线路的不必要的长时间占用。 这样的超时时间也可以在运营商服务器中设置 14 . [0056] 同时,运营商服务器 14 包括信息接收单元 141 , 一个数据传输单元 142 , 一个速度控制单元 143 , 一个数据大小控制单元 144 , 和一个参数管理单元 145 . 从移动端 13 通过基站 12 ,信息接收单元 141 接收指示与该基站的通信状态的通信状态信息 12 . 如上所述,该通信状态信息是根据拥塞度和干扰波强度计算的估计线路速度Ro,和/或通过比较估计的线路质量信息(线路质量标志Fq或线路质量指标Iq) 线速度 Ro 与阈值 Rt。 数据传输单元 142 从提供者服务器传输内容数据 16 根据需要控制其与移动终端的通信速度和数据大小 13 通过基站 12 . [0057] 基于信息接收单元接收到的通信状态信息 141 , 速度控制单元 143 控制从提供商服务器传输内容数据的通信速度 16 到移动终端 13 通过基站 12 . 速度控制单元 143以与上述移动终端相同的方式,根据估计的线路速度Ro确定线路质量信息(线路质量标志Fq或线路质量指标Iq)作为通信状态信息 13 ,并根据此线路质量信息控制通信速度。 或者,速度控制单元 143 基于作为通信状态信息的线路质量信息(线路质量标志Fq或线路质量指标Iq)控制通信速度。 [0058] 在这种情况下,通信速度被控制为设置为两个或更多,或者三个或更多级别。 例如,根据估计的线路速度Ro是否高于阈值Rt,将通信速度控制为设置为两个级别。 例如,在阈值 Rt 为 150kbps 的情况下,速度控制单元 143 当Ro≤Rt且线路质量不好时将通信速度限制在150 kbps,但在Ro>Rt且线路质量良好时不限制通信速度。 [0059] 在这种情况下,当Ro≤Rt时,优惠券处于关闭状态(不可用状态),而当Ro>Rt时,优惠券处于开启状态(可用状态)。 需要注意的是,优惠券只有在优惠券中有余额时才能使用。 图4示出了在移动终端上显示的充电屏幕的示例 13 当用户使用该移动终端进行增加优惠券余额的操作时 13 , 例如。 当用户在支票栏中勾选想要的项目并按下收费按钮时,优惠券中的剩余金额增加。 [0060] 图5中的流程图示出了将优惠券置于开启或关闭状态的过程中的过程的示例。 在步骤 ST 1 , 速度控制单元 143 开始该过程,然后继续进行步骤 ST 中的过程 2 . 在步骤 ST 2 , 速度控制单元 143 判断优惠券是否有余额。 [0061] 如果优惠券中有剩余金额,则速度控制单元 143 在步骤 ST 3 确定是否 Ro>Rt。 如果 Ro>Rt,则速度控制单元 143 在步骤 ST 4 将优惠券置于开启状态(可用状态)。 在这种状态下,速度控制单元 143 不限制通讯速度。 之后,速度控制单元 143 在步骤 ST 6 结束进程。 [0062] 如果不是 Ro>Rt,另一方面,速度控制单元 143 在步骤 ST 5 将优惠券置于关闭状态(不可用状态)。 在这种状态下,速度控制单元 143 将通信速度限制为 150 kbps。 之后,速度控制单元 143 在步骤 ST 6 结束进程。 [0063] 即使在优惠券处于开启状态(可用状态)的情况下,如果优惠券中的所有剩余金额都用于线路使用,则速度控制单元 143 立即将优惠券置于关闭状态(不可用状态),并将通信速度限制为 150 kbps。 [0064] 参数管理单元 145 使用参数管理表管理每个用户的服务参数。 图6示出了在参数管理表中存储和管理的服务参数的示例。 在本例中,优惠券的剩余金额和优惠券状态在用户ID下进行管理。 [0065] 图7示意性地示出了速度控制系统的示例配置 150 在运营商服务器中 14 . 这种速度控制系统 150 包括一个开关 151 , 一个传输速度测量单元 152 , 和一个控制单元 153 . 传输速度测量单元 152 测量数字 R 1 从提供者服务器流出的内容数据中每秒的字节数 16 进入移动终端 13 , 例如。 控制单元 153 比较实测数 R 1 具有设定速度 R 的字节数 0 , 并控制开关的开启和关闭 151 基于比较结果,使得 R 1 等于 R 0 . [0066]尽管在以上描述中当优惠券处于开启状态时通信速度不受限制,但是当优惠券处于开启状态时可以限制通信速度的值。 尽管在以上描述中当优惠券处于关闭状态时通信速度被限制为150kbps,但是速度值可以被更精细地限制。 [0067] 通常,设定速度 R 0 由内容大小和预期反应时间之间的比率决定。 内容大小和预期反应时间由内容类型和用户状态决定。 例如,速度控制单元 143 可改变设定速度 R 0 根据内容的具体情况(内容类型或优先级)。 这样,可以实现对应于内容类型或优先级的反应时间(直到网页变为可访问的时间)。 例如,文本内容的数据量通常较小,而图​​像内容的数据量通常较大。 因此,设定速度 R 0 在文本内容的情况下减少,设定速度R 0 在图像内容的情况下增加。 并且,对于相同的图像内容,如果用户对图像内容更感兴趣,则确定优先级更高,并且设定速度R 0 例如,如果优先级更高,则设置更高。 [0068] 图8示意性地示出了速度控制系统的示例配置 150 A 在设定速度 R 的情况下 0 根据内容的具体情况(内容类型、优先级等)改变。 在图8中,与图7中所示的部件等效的部件用与图7中使用的相同的附图标记表示,并且在此不再重复对其的详细说明。 速度控制系统 150 A 包括一个开关 151 , 一个传输速度测量单元 152 , 一个控制单元 153 , 速度表 154 和内容分析单元 155 . [0069] 内容分析单元 155 通过分析从提供商服务器流出的内容数据来识别内容的细节(内容类型、优先级等) 16 进入移动终端 13 . 内容分析单元 155 可以根据网页上的引用URL、http头中的MIME格式信息、http头或IP头中的地址信息、数据大小信息等来识别内容类型。 此外,内容分析单元 155 可以根据引用URL的扩展名来识别内容类型,例如mp4、av、mov或jpg。 [0070] 内容分析单元 155 也可以通过考虑用户的情况来确定优先级。 例如,用户在住宅区时常查看娱乐信息页面,而在商业区时常查看商店信息页面。 或者,可以在移动终端侧识别内容的细节(内容、类型、优先级等) 13 ,并传送到运营商服务器 14 . 在这种情况下,内容分析单元 155 变得不必要。 [0071] 将内容细节的识别结果提供给速度表 154 . 速度表 154 输出设定速度R 0 对应于识别内容细节和服务状态的结果(优惠券中的剩余金额和优惠券状态)(见图6)到控制单元 153 . [0072] 速度控制单元 143 也可以改变设定速度R 0 根据用户操作的具体情况。 例如,基于如下所示的用户信息来识别用户的动作的细节。 具体地,用户信息可以是时间表、备忘录、登录ID、登录时间、登录地点、退出时间、退出地点、购买历史、访问历史 、行动位置的历史、区域信息(指示工业区、商业区、住宅区或交通设施)等。 [0073]图9示意性地示出了速度控制系统的示例配置 150 B 在设定速度 R 的情况下 0 根据用户动作的具体情况改变。 在图9中,与图7中所示的部件等效的部件由与图7中使用的相同的附图标记表示,并且在此不再重复对其的详细说明。 速度控制系统 150 B 包括一个开关 151 , 一个传输速度测量单元 152 , 一个控制单元 153 , 速度表 156 ,以及用户动作识别单元 157 . [0074] 用户动作识别单元 157 基于用户信息识别用户动作的细节。 例如,可以从时间表中识别用户现在正前往的地点(差的接待区或好的接待区)。 此外,例如,可以检查用户是否位于经常观看图像内容的地点或时间段。 [0075] 用户动作细节的识别结果被提供给速度表 156 . 速度表 156 输出设定速度R 0 对应于识别用户的动作细节和服务状态(优惠券中的剩余金额和优惠券状态)的结果(见图6)到控制单元 153 . [0076] 返回参考图3,数据大小控制单元 144 减少要从提供商服务器传输的内容数据的数据大小 16 到移动终端 13 通过基站 12 基于信息接收单元接收到的通信状态信息 141 . 在估计线路速度Ro等于或低于阈值Rt并且通信速度被限制为例如150kbps的情况下,数据大小被减小。 [0077] 例如,当网络内容包括图像或运动图像时,数据大小控制单元 144 通过执行降低图像或运动图像的分辨率的处理,或者执行去除图像或运动图像的数据的处理,执行控制以减小数据大小。 此外,数据大小控制单元 144 执行减少运动图像内容或图像(静止图像)内容的数据大小的处理,但不执行例如文本内容或邮件的处理。 即,执行控制以根据观看细节来减小数据大小。 [0078] 通过以上述方式减小数据大小,可以缩短内容数据传输所需的时间,并且即使在通信速度被限制为低值的情况下也可以防止无线资源的长时间占用。 [0079] 图10示意性地示出了数据大小控制系统的示例配置 160 . 数据大小控制系统 160 包括一个尺寸缩小处理单元 161 和内容分析单元 162 . 内容分析单元 162 通过分析从提供商服务器流出的内容数据,识别内容的细节(内容类型、内容结构等) 16 进入移动终端 13 . [0080] 在通信速度受到限制的情况下,尺寸缩减处理单元 161 基于对内容细节的确定结果执行尺寸减小处理。 当网络内容包括图像或运动图像时,例如,执行降低图像或运动图像的分辨率的处理,或者执行去除图像或运动图像的数据的处理,以便 数据大小减小。 [0081] 数据大小缩减过程可能不在运营商服务器中执行 14 . 相反,可以从运营商服务器发送通信速度限制信息或数据大小减少请求 14 到提供者服务器 16 ,并且可以在提供者服务器端执行数据大小缩减处理 16 . [0082]图11(a)示出了包括图像、运动图像等的网络内容的示例。 当没有数据大小缩减请求时,提供者服务器 16 将图11(a)所示的网页内容发送到移动终端 13 , 如图 11(b) 所示。 但是,当有数据大小减少请求时,提供程序服务器 16 将网页内容减去大数据量的图像、动态图像等发送到移动终端 13 , 如图 11(c) 所示。 [0083] 需要注意的是,运行provider server的provider 16 和手机运营商可能相同,也可能不同。 在提供商和移动电话运营商不同的情况下,也可以采用在提供商服务器侧执行数据大小缩减处理的商业模式 16 如上所述,移动电话运营商可以支付奖励作为对解决网络拥塞的提供商的感谢。 [0084] 图12示出了在这种情况下要执行的示例操作。 在这种情况下,提供商(运营商 B)向移动电话运营商(运营商 A)发送有关数据大小缩减处理历史的信息。 移动电话运营商根据历史信息计算奖励金额,并将奖励支付给提供者。 在运营商服务器侧执行数据大小缩减处理的情况下 14 ,也可以支付奖励作为对提供者的感谢。 [0085] 如上所述,在移动电话系统中 10 如图1所示,通信状态信息指示与基站的通信状态 12 被移动端获取 13 ,并将此通信状态信息发送到运营商服务器 14 通过基站 12 . 基于该通信状态信息,运营商服务器 14 控制要从提供商服务器(网络服务器)传输的内容数据的通信速度 16 到移动终端 13 通过基站 12 . 因此,要从提供商服务器发送的内容数据的通信速度 16 到移动终端 13 通过基站 12 例如,可以根据通信状态信息进行设置,即使在线路质量较差的通信环境中也可以进行良好的通信。 即,例如可以增加可以分配给其他用户的无线资源,并且可以减少线路负载。 此外,还提供最基本的通信环境,例如可以建立更稳定的系统。 [0086] 此外,在手机系统中 10 如图1所示,移动终端 13 或运营商服务器 14 设置与提供程序服务器连接相关的超时时间 16 或从提供商服务器下载内容数据 16 基于通信状态信息。 由此,例如,在线路质量差的环境中,超时时间被缩短,因此,防止了无线线路的不必要的长时间占用。 在通信因超时而中断后,进行重传/重连以重新获取信息。 以这种方式,在某些情况下可以更快地获取信息。 [0087] 此外,在手机系统中 10 如图1所示,运营商服务器 14 根据内容的具体情况或用户的动作改变通信速度的控制值。 因此,移动终端 13 可以从提供者服务器获取内容数据 16 例如,以与内容的细节或用户的动作的细节相对应的通信速度,并且即使在通信速度受到限制时也进行相对顺畅的通信。 [0088] 此外,在手机系统中 10 如图1所示,当控制通信速度下降到较低值时,运营商服务器 14 可以减少要传输到移动终端的内容数据的大小 13通过基站 12 . 因此,例如,可以缩短发送内容数据所需的时间,并且可以防止无线资源的长时间占用。 [0089] 此外,在手机系统中 10 如图1所示,运营商服务器 14 根据通讯状态信息,将优惠券置于开启状态(可用状态),线路质量良好时不限制通讯速度,但运营商服务器 14 当线路质量不好时,根据通信状态信息将优惠券置于关闭状态(不可用状态),并将通信速度限制在预定值。 因此,例如,当通信环境恶化时,优惠券自动进入不可用状态。 因此,可以提供用户满意的费用结构。 2. 修改 [0090] 尽管上面已经参照附图描述了本技术的实施例,但是本技术不限于这些示例。 显然,本领域的普通技术人员可以在此处要求保护的技术精神的范围内做出各种变化或修改,并且应该理解,这些变化或修改都在本技术的范围内。 例如,移动终端被描述为移动电话设备,但不一定是移动电话设备,也可以是PDA、游戏机或小型PC等便携式信息处理设备。 [0091] 本技术也可以体现在下面描述的结构中。 [0092] (一)一种移动终端设备,包括: [0093] 信息获取单元,获取指示与基站的通信状态的通信状态信息; [0094] 信息发送单元,通过基站将通信状态信息发送给运营商服务器装置; 和 [0095] 数据接收单元,其通过运营商服务器设备和基站从网络服务器接收内容数据,同时基于通信状态信息控制通信速度。 [0096] (2)根据(1)所述的移动终端装置,其中,所述通信状态信息是根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较而获得的线路质量信息 . [0097] (3)(1)或(2)所述的移动终端设备,还包括: [0098] 超时时间设置单元,其基于通信状态信息设置与连接到网络服务器或从网络服务器下载内容数据相关的超时时间。 [0099] (4)一种移动终端设备的无线通信方法,包括: [0100] 信息获取步骤,获取指示与基站的通信状态的通信状态信息; [0101] 信息传输步骤,通过基站将通信状态信息传输给运营商服务器设备; 和 [0102] 数据接收步骤,通过运营商服务器设备和基站从网络服务器接收内容数据,同时基于通信状态信息控制通信速度。 [0103] (5) 一种运营商服务器设备,包括: [0104] 信息接收单元,通过基站从移动终端设备接收通信状态信息,该通信状态信息指示与基站的通信状态; 和 [0105] 速度控制单元,基于通信状态信息控制内容数据的通信速度,内容数据通过基站从网络服务器发送到移动终端设备。 [0106](6)根据(5)所述的运营商服务器装置,其中,所述通信状态信息是根据拥塞度和干扰波强度估计的估计线路速度,和/或通过将估计的线路速度与阈值进行比较而获得的线路质量信息 . [0107] (7)根据(5)或(6)所述的运营商服务器设备,其中,速度控制单元将由通信状态信息指示的通信状态划分为多个等级,并且根据各个等级控制通信速度。 [0108] (8)根据(5)至(7)中任一项所述的运营商服务器设备,其中,所述速度控制单元根据内容的细节改变用于通信速度的控制值。 [0109] (9)根据(5)至(8)中任一项所述的运营商服务器装置,其中,所述速度控制单元根据所述移动终端装置的用户的动作的细节来改变所述通信速度的控制值。 [0110] (10)如(5)至(9)中任一项所述的运营商服务器设备,进一步包括 [0111] 数据大小控制单元,当速度控制单元控制通信速度变低时,减小要通过基站发送到移动终端设备的内容数据的大小。 [0112] (11)根据(5)至(10)中任一项所述的运营商服务器设备,其中,速度控制单元基于通信状态信息确定线路质量是否良好,将优惠券设置为可用状态并且不限制通信速度 当线路质量良好时,将优惠券设置为不可用状态,并在线路质量不好时将通信速度限制在预定值。 [0113] (12)一种运营商服务器设备中的通信速度控制方法,包括: [0114] 信息接收步骤,通过基站从移动终端装置接收通信状态信息,该通信状态信息指示与基站的通信状态; 和 [0115] 速度控制步骤,在内容数据通过基站从网络服务器发送到移动终端设备时控制通信速度,基于通信状态信息控制通信速度。 参考符号列表 [0116]10 手机系统[0117]11 电信运营商通信网络[0118]12 基站[0119]13 移动端[0120]14 运营商服务器[0121]15 互联网[0122]16 提供者服务器(网络服务器)[0123]101 天线[0124]102 无线接口单元[0125]103 控制单元[0126]104 用户界面单元[0127]131 信息获取单元[0128]132 信息传递单元[0129]133 数据接收单元[0130]134 超时时间设置单位[0131]141 信息接收单位[0132]142 数据传输单元[0133]143 速度控制单元[0134]144 数据大小控制单元[0135]150 , 150 一个, 150 B 速度控制系统[0136]151 转变[0137]152 传输速度测量单元[0138]153 控制单元[0139]154 速度表[0140]155 内容分析单元[0141]156 速度表[0142]157 用户动作识别单元[0143]160 数据大小控制系统[0144]161 小型化处理单元[0145]162 内容分析单元(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.427 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.428 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20160373954A1(String), US9986457B2(String), WO2014208389A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.579 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.580 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: US20160373954A1(String), US9986457B2(String), WO2014208389A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.597 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US9986457B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.632 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.633 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), US20160373954A1(String), US9986457B2(String), WO2014208389A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.651 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.652 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271688(Integer), US20160373954A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.687 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271688(Integer), US9986457B2(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.722 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271688(Integer), WO2014208389A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.757 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US9986457B2(String), US9986457B2(String), 1527523200(Integer), 271688(Integer), 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.794 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.795 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SONY CORPORATION(String), SONY CORPORATION(String), 索尼公司(String), 索尼公司(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.845 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.846 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.879 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.880 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.881 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186020(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.914 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 1(Integer), 186020(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.950 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.951 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SONY CORPORATION(String), 索尼公司(String), 255(String), 0(Integer), 1660814565(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:38.985 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186020(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.019 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 21012(Integer), 2(Integer), 186020(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.053 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.054 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.071 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.088 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 21012(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.106 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.107 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.123 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.124 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.158 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.175 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.328 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 授权(String), 3(Integer), 186020(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.363 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE (patentno = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.365 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.709 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Preparing: INSERT INTO os_patent ( name, nameout, patentno, abstract, abstractout, applicationno, appdate, publicno, publicdate, bureau, type, prioritycountry, simplefamilynum, quoteno, quote, selfcontentnum ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.710 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert ==> Parameters: Method of executing control mode of radio frequency unit in mobile terminal and mobile terminal for performing the same(String), 在移动终端中执行射频单元控制模式的方法及用于执行该方法的移动终端(String), US20080125034A1(String), A method of executing a control mode of a radio frequency (RF) unit in a mobile terminal and a mobile terminal for performing the same are provided. The mobile terminal includes an RF unit to receive electric waves and a controller. The controller compares the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity and the comparison result determines whether the controller turns the RF unit off.(String), 提供了一种在移动终端中执行射频(RF)单元的控制模式的方法以及用于执行该方法的移动终端。 移动终端包括接收电波的RF单元和控制器。 控制器将RF单元中接收到的电波的强度与电波强度的参考值进行比较,比较结果确定控制器是否关闭RF单元。(String), US11/771235(String), 1183046400(Integer), US20080125034A1(String), 1211990400(Integer), 美国(String), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030081694A1 | US20040114737A1 | US20050185737A1 | US20070076137A1 | US20090010367A1 | US4249165A | US4369443A | US4370753A | US4437095A | US4449248A | US5301225A | US5566364A | US5799256A | US6078816A | US7356351B1(String), 12(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.745 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Preparing: DELETE FROM os_patent_img WHERE (pid = ? AND status = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.746 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete ==> Parameters: 186021(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.892 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.893 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Preparing: INSERT INTO os_patent_img ( status, address, pid, file_name ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.894 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert ==> Parameters: 1(Integer), \20230420\05c0fa25fcfc4cc4b5f0dc59807774b9.png(String), 186021(Integer), 05c0fa25fcfc4cc4b5f0dc59807774b9.png(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentImageMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.929 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.930 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET name=?, nameout=?, patentno=?, abstract=?, abstractout=?, applicationno=?, appdate=?, publicno=?, publicdate=?, bureau=?, status=?, type=?, prioritycountry=?, simplefamilynum=?, quoteno=?, quote=?, abstract_path=?, selfcontentnum=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.947 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: Method of executing control mode of radio frequency unit in mobile terminal and mobile terminal for performing the same(String), 在移动终端中执行射频单元控制模式的方法及用于执行该方法的移动终端(String), US20080125034A1(String), A method of executing a control mode of a radio frequency (RF) unit in a mobile terminal and a mobile terminal for performing the same are provided. The mobile terminal includes an RF unit to receive electric waves and a controller. The controller compares the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity and the comparison result determines whether the controller turns the RF unit off.(String), 提供了一种在移动终端中执行射频(RF)单元的控制模式的方法以及用于执行该方法的移动终端。 移动终端包括接收电波的RF单元和控制器。 控制器将RF单元中接收到的电波的强度与电波强度的参考值进行比较,比较结果确定控制器是否关闭RF单元。(String), US11/771235(String), 1183046400(Integer), US20080125034A1(String), 1211990400(Integer), 美国(String), 2(Integer), 2(Integer), KR(String), 2(Integer), 15(Integer), US20030081694A1 | US20040114737A1 | US20050185737A1 | US20070076137A1 | US20090010367A1 | US4249165A | US4369443A | US4370753A | US4437095A | US4449248A | US5301225A | US5566364A | US5799256A | US6078816A | US7356351B1(String), \20230420\05c0fa25fcfc4cc4b5f0dc59807774b9.png(String), 12(Integer), 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.982 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Preparing: DELETE FROM os_patent_right WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:39.983 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete ==> Parameters: 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.016 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Preparing: INSERT INTO os_patent_right ( patent_id, content, content_out, type, sort, parent_sort ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 1. A mobile terminal, comprising:a radio frequency (RF) unit to receive electric waves; anda controller to compare the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity,wherein the comparison result determines whether the controller turns the RF unit off.(String), 1.移动终端,包括:用于接收电波的射频(RF)单元;和控制器将射频单元接收到的电波强度与电波强度参考值进行比较,其中,比较结果决定控制器是否关闭射频单元。(String), 0(Integer), 0(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 2. The mobile terminal of claim 1, wherein the controller comprises:a numerical value comparison unit to compare the intensity of the received electric waves with the reference value of electric wave intensity; anda power controller to turn off the RF unit by not supplying power to the RF unit if the intensity of the received electric waves is less than the reference value of electric wave intensity.(String), 2.如权利要求1所述的移动终端,其中控制器包括:数值比较单元,将接收到的电波强度与电波强度参考值进行比较;和如果接收到的电波的强度小于电波强度的参考值,则功率控制器通过不向RF单元供电来关闭RF单元。(String), 1(Integer), 1(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 3. The mobile terminal of claim 2, wherein the controller further comprises a numerical value conversion unit to convert the intensity of the received electric waves to a numerical value.(String), 3.如权利要求2所述的移动终端,其中控制器还包括数值转换单元,用于将接收到的电波的强度转换为数值。(String), 1(Integer), 2(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 4. The mobile terminal of claim 2, wherein the controller turns on the RF unit if, after turning off the RF unit, it determines that a preset time period from a time at which the RF unit was turned off has elapsed.(String), 4.如权利要求2所述的移动终端,其中如果在关闭RF单元之后,控制器确定从RF单元被关闭的时间起经过预设时间段,则控制器打开RF单元。(String), 1(Integer), 3(Integer), 1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.017 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 5. The mobile terminal of claim 4, wherein the controller controls the RF unit to continuously receive the electric waves by sustaining a turn-on state of the RF unit if the intensity of the received electric waves is greater than or equal to the reference value of electric wave intensity.(String), 5.如权利要求4所述的移动终端,其中当接收到的电波强度大于或等于电波强度参考值时,控制器通过维持射频单元的开启状态来控制射频单元持续接收电波。(String), 1(Integer), 4(Integer), 3(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 6. The mobile terminal of claim 1, further comprising an input unit to input a control mode of the RF unit to turn the RF unit on and off.(String), 6.如权利要求1所述的移动终端,还包括输入单元输入RF单元的控制模式以打开和关闭RF单元。(String), 1(Integer), 5(Integer), 0(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 7. The mobile terminal of claim 6, wherein the controller controls the RF unit to change to a control mode according to the input of the input unit and receive electric waves at a interval during a preset time period.(String), 7.如权利要求6所述的移动终端,其中控制器根据输入单元的输入控制射频单元改变为控制模式,并在预设时间段内每隔一段时间接收电波。(String), 1(Integer), 6(Integer), 5(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 8. A method of executing a control mode of a radio frequency (RF) unit in a mobile terminal, comprising;receiving electric waves in the RF unit;comparing the intensity of the received electric waves with a reference value of electric wave intensity; andturning off the RF unit if the intensity of the received electric waves is less than the reference value of electric wave intensity.(String), 8.一种执行移动终端中射频(RF)单元的控制模式的方法,包括;在RF单元中接收电波;将接收到的电波强度与电波强度参考值进行比较;和如果接收到的电波强度小于电波强度参考值,则关闭射频单元。(String), 0(Integer), 7(Integer), -1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 9. The method of claim 8, further comprising determining whether a control mode of the RF unit is preset if the intensity of the received electric waves is less than the reference value of electric wave intensity.(String), 9.如权利要求8所述的方法,还包括如果接收到的电波强度小于电波强度参考值,则判断射频单元的控制模式是否预设。(String), 1(Integer), 8(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 10. The method of claim 8, further comprising:determining whether a preset time period has elapsed from a time at which the RF unit is turned off;turning on the RF unit if the preset time period has elapsed; andreceiving the electric waves in the RF unit.(String), 10.如权利要求8所述的方法,还包括:判断射频单元关闭后是否经过预设时间;如果预设时间段已经过去,则打开射频单元;和在RF单元中接收电波。(String), 1(Integer), 9(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 11. The method of claim 10, further comprising sustaining a turn-on state of the RF unit if the intensity of the received electric waves is greater than or equal to the reference value of electric wave intensity.(String), 11.如权利要求10所述的方法,还包括如果接收到的电波强度大于或等于电波强度参考值,则维持射频单元开启状态。(String), 1(Integer), 10(Integer), 9(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.018 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentRightMapper.insert ==> Parameters: 186021(Integer), 12. The method of claim 8, further comprising changing a state of receiving the electric waves at an interval during a preset time period to a state of receiving the electric waves at another interval during the preset time period if a control mode of the RF unit is selected; andreceiving the electric waves at the changed interval during the preset time period in the RF unit.(String), 12.如权利要求8所述的方法,还包括如果选择了RF单元的控制模式,则将在预设时间段内以一定间隔接收电波的状态改变为在预设时间段内以另一间隔接收电波的状态;和在RF单元中在预设时间段内以改变的间隔接收电波。(String), 1(Integer), 11(Integer), 7(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.253 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.270 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Preparing: INSERT INTO os_patent_instruction_text ( patent_id, manual, manual_out ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.271 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert ==> Parameters: 186021(Integer), CROSS REFERENCE TO RELATED APPLICATION [0001]This application claims priority from and the benefit of Korean Patent Application No. 10-2006-0116332, filed on Nov. 23, 2006, which is hereby incorporated by reference for all purposes as if fully set forth herein. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]The present invention relates to a method of executing a control mode of a radio frequency (RF) unit in a mobile terminal and a mobile terminal for performing the same, and more particularly, to a method of executing a control mode of an RF unit for receiving electric waves to control consumption of battery power by turning the RF unit on or off according to the intensity of received electric waves, and a mobile terminal for performing the same. [0004]2. Discussion of the Background [0005]A conventional mobile terminal is activated at time slots to set a communication environment to receive electric waves from a base station. The mobile terminal transmits power according to the intensity of received electric waves. That is, the mobile terminal enables the intensity of electric waves transmitted from the mobile terminal to be weak if the intensity of the received electric waves is strong and enables the intensity of electric waves transmitted from the mobile terminal to be strong if the intensity of the received electric waves is weak, whereby reception efficiency of electric waves may improve. [0006]Because transmission power increases in a weak electric wave area, battery power of the mobile terminal may be rapidly consumed in a weak electric wave area, whereby the battery may not be effectively controlled. SUMMARY OF THE INVENTION [0007]The present invention provides a method of controlling an RF unit of a mobile terminal according to the intensity of a signal received in the mobile terminal. [0008]The present invention further provides a method of controlling an RF unit of a mobile terminal in a low electric wave area such that the efficiency of a battery of the mobile terminal may improve. [0009]Additional features of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. [0010]The present invention discloses a mobile terminal including an RF unit to receive electric waves and a controller. The controller compares the intensity of the electric waves received in the RF unit with a reference value of electric wave intensity and the comparison result determines whether the controller turns the RF unit off. [0011]The present invention also discloses a method of executing a control mode of an RF unit in a mobile terminal, including receiving electric waves in the RF unit, comparing the intensity of the received electric waves with a reference value of electric wave intensity, and turning off the RF unit if the intensity of the received electric waves is less than the reference value of electric wave intensity. [0012]It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. [0014]FIG. 1 is a block diagram showing a configuration of a mobile terminal for executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0015]FIG. 2 is a flowchart showing a method of executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0016]FIG. 3 is a flowchart showing a method of executing a control mode of an RF unit according to another exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS [0017]The invention is described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure is thorough, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity. Like reference numerals in the drawings denote like elements. [0018]It will be understood that when an element or layer is referred to as being “on” or “connected to” another element or layer, it can be directly on or directly connected to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on” or “directly connected to” another element or layer, there are no intervening elements or layers present. [0019]A mobile terminal according to exemplary embodiments of the present invention includes information communication devices and multimedia devices such as a mobile communication terminal, a mobile phone, a Personal Digital Assistant (PDA), and a smart phone, and applications thereof. [0020]FIG. 1 is a block diagram showing a configuration of a mobile terminal for executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0021]Referring to FIG. 1, the mobile terminal includes an RF unit 101, an input unit 103, a controller 105, a power controller 107, a numerical value conversion unit 109, a numerical value comparison unit 111, a display unit 113, a memory unit 115, and an audio unit 117. [0022]The RF unit 101 performs wireless communication between the mobile terminal and a mobile communication network. For example, the RF unit 101 transmits and receives voice data, character messages, and multimedia messages through the mobile communication network. The RF unit 101 receives electric waves at an interval that is set by the controller 105 and provides the received electric waves to the controller 105. [0023]The input unit 103 may include a general keypad. Further, the input unit 103 may include a touch screen, a touch pad, and a scroll wheel. The input unit 103 receives a user manipulation signal to control the operation of the mobile terminal and provides the signal to the controller 105. [0024]The controller 105 controls the general operation of units in the mobile terminal. The controller 105 includes a modem and a codec having a transmitter to encode and modulate a signal to be transmitted by the RF unit 101 and a receiver to demodulate and decode the received signal. [0025]Particularly, the controller 105 controls the RF unit 101 to enter a control mode, compares the intensity of electric waves received in the RF unit 101 with a reference value of electric wave intensity, and turns the RF unit 101 on or off according to the compared result. For this, the controller 105 includes a power controller 107, a numerical value conversion unit 109, and a numerical value comparison unit 111. Further, the controller 105 terminates and sustains a control mode of the RF unit 101 in response to an input signal provided by the input unit 103. [0026]The power controller 107 may turn the RF unit 101 off by not supplying power to the RF unit 101 or turn the RF unit 101 on by supplying power to the RF unit 101. [0027]The numerical value conversion unit 109 converts the intensity of electric waves received in the RF unit 101 to a numerical value and provides the numerical value to the numerical value comparison unit 111. [0028]The numerical value comparison unit 111 compares the numerical value, which corresponds to the intensity of received electric waves, with a reference value of electric wave intensity and provides the compared result to the power controller 107. [0029]The display unit 113 displays information relating to the operation state, the operation result, and other information performed in units of the mobile terminal by the f the controller 105. The display unit 113 may include a display device such as a liquid crystal display (LCD), organic light emitting diodes (OLED), or a plasma display panel (PDP). [0030]The controller 105 controls the memory unit 115 to store information (for example, information about a setting state and a menu) related to the operation of the mobile terminal. [0031]The memory unit 115 stores the intensity of received electric waves as a reference value to be referred to when changing to a control mode to turn the RF unit 101 on or off. The memory unit 115 also stores a preset time period and an interval at which electric waves are to be received from a base station in a control mode of the RF unit 101. [0032]The memory unit 115 stores the preset time period as a reference period during which the RF unit 101 is turned on and stores a power saving numerical value of a function, including light brightness and light time, in a power saving mode of the mobile terminal. [0033]The audio unit 117 converts an analog audio signal that is input through a microphone MIC to a digital signal and converts a digital audio signal output from the controller 105 into an analog audio signal and reproduces the signal through a speaker SPK. [0034]FIG. 2 is a flowchart showing a method of executing a control mode of an RF unit according to an exemplary embodiment of the present invention. [0035]Referring to FIG. 2, a control mode of the RF unit 101 is selected by a user (S201), and the mobile terminal enters a power saving mode (S203). The control mode of the RF unit 101 is a mode that is set to reduce battery power consumption when the mobile terminal moves to a weak electric wave area. The power saving mode is a mode that is set to convert a function such as light brightness and/or light time of the mobile terminal to a preset power saving numerical value. [0036]The controller 105 controls the RF unit 101 to receive electric waves at an interval during the preset time period (S205). [0037]Specifically, the controller 105 controls the RF unit 101 to receive electric waves at intervals before entering the control mode of the RF unit 101, and the intervals may be time slots. In the case of time slots, the mobile terminal receives electric waves from a base station at time slots, each of which corresponds to an intrinsic slot cycle index allocated by the base station according to system settings. Thereafter, the controller 105 controls the RF unit 101 to enter the control mode and receive electric waves at the intervals during the preset time period. [0038]For example, if the preset time period is 3 minutes and the interval is 20 seconds, the controller 105 controls the RF unit 101 to receive electric waves 9 times at intervals of 20 seconds over a 3 minute period. The interval may be a receiving interval (for example, every 20 seconds), the receiving number of times (for example, 9 times), or a time slot. [0039]The controller 105 controls the numerical value conversion unit 109 to measure the intensity of the received electric waves and convert the intensity of the received electric waves to a numerical value, and provides the converted numerical value to the numerical value comparison unit 111 (S207). [0040]The controller 105 controls the numerical value comparison unit 111 to determine whether the intensity of the received electric waves is greater than or equal to a reference value of electric wave intensity (S209). If the intensity of the received electric waves is greater than or equal to the reference value of electric wave intensity, the controller 105 determines whether a request to sustain the control mode of the RF unit 101 has been received (S211). If a request to sustain the control mode of the RF unit 101 is received, the controller 105 sustains the control mode of the RF unit 101 (S213) and continues to receive electric waves. The controller 105 repeats the process by returning to step S205 while sustaining a control mode of the RF unit 101 at step S213. [0041]If a request to sustain the control mode of the RF unit 101 is not received at step S211, the controller 105 terminates the control mode of the RF unit 101 (S215) and the process returns to step S205. [0042]In another exemplary embodiment, if the intensity of the received electric waves is greater than or equal to a reference value of electric wave intensity at step S209, steps S211 and S215 may be omitted, and the process may continue at step S213. [0043]If the intensity of the received electric waves is less than the reference value of electric wave intensity at step S209, the controller 105 turns the RF unit 101 off (S217). When a preset time period has elapsed (219), the controller 105 turns the RF unit 101 on (S221). [0044]The controller 105 determines whether a request to terminate the control mode of the RF unit 101 has been received (S223). If a request to terminate the control mode of the RF unit 101 is not received, the process returns to step S205 and the RF unit 101 continues to receive the electric waves controlled by the controller 105. If a request to terminate the control mode of the RF unit 101 is received, the controller 105 terminates the control mode of the RF unit 101 (S225). [0045]For example, if the preset time period is set to 1 hour, the controller 105 turns the RF unit 101 on after 1 hour has elapsed from the time at which the RF unit 101 was turned off and receives electric waves. A turn-off state of the RF unit 101 is a state in which power is blocked from being supplied to the RF unit 101, and a turn-on state of the RF unit 101 is a state in which power is supplied to the RF unit 101 and thus, electric waves are continuously received. [0046]FIG. 3 is a flowchart showing a method of executing a control mode of an RF unit according to another exemplary embodiment of the present invention. [0047]Referring to FIG. 3, the controller 105 controls the RF unit 101 to receive electric waves at intervals (S301). The intervals may be time slots. For example, the mobile terminal may receive electric waves from a base station at time slots, each of which corresponds to an intrinsic slot cycle index allocated by the base station according to system settings. [0048]The controller 105 controls the numerical value conversion unit 109 to measure the intensity of the received electric waves and convert the intensity of the received electric waves to a numerical value (S303). The controller 105 then provides the numerical value to the numerical value comparison unit 111. [0049]The controller 105 controls the numerical value comparison unit 111 to determine whether the numerical value, which corresponds to the intensity of the received electric waves, is greater than or equal to a reference value of electric wave intensity (S305). If the numerical value is greater than or equal to the reference value of electric wave intensity, the controller 105 sustains a control mode of the RF unit 101 (S307), continues to receive the electric waves, and repeats the process by returning to step S301. [0050]If the numerical value is less than the reference value at step S305, the controller 105 determines whether a control mode of the RF unit 101 is set (S309). If a control mode of the RF unit 101 is not set, the process continues at step S307. [0051]If a control mode of the RF unit 101 is set, the controller 105 turns the RF unit 101 off (S311). When the controller 105 determines that a preset time period has elapsed after the RF unit 101 was turned off (S313), the controller 105 turns on the RF unit 101 (S315) and repeats the process by returning to step S301. [0052]As described above, according to exemplary embodiments of the present invention, by controlling the RF unit of the mobile terminal according to the intensity of a received signal, a battery may be effectively managed. [0053]Further, by turning the RF unit off in a weak electric wave area, battery power consumption used to receive electric waves may be reduced. [0054]Further, by turning only the RF unit off in the mobile terminal, another function of the mobile terminal may be used without restriction even when the RF unit of the mobile terminal is turned off. [0055]It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.(String), 相关申请的交叉引用 [0001] 本申请要求于 2006 年 11 月 23 日提交的韩国专利申请第 10-2006-0116332 号的优先权和权益,为了所有目的,该申请通过引用并入本文,就好像在本文中完整阐述一样。 背景技术 [0002] 1. 发明领域 [0003] [0001] 本发明涉及一种在移动终端中执行射频(RF)单元的控制模式的方法以及用于执行该方法的移动终端,更具体地,涉及一种在移动终端中执行射频(RF)单元的控制模式的方法。 接收电波以通过根据接收到的电波的强度打开或关闭RF单元来控制电池电力的消耗,以及用于执行相同操作的移动终端。 [0004] 2. 背景讨论 [0005] 传统的移动终端在时隙被激活以设置通信环境以接收来自基站的电波。 移动终端根据接收到的电波的强度发射功率。 也就是说,如果接收到的电波的强度强,则移动终端使从移动终端发射的电波的强度弱,如果接收到的电波的强度强,则使从移动终端发射的电波的强度强。 接收的电波较弱,由此可以提高电波的接收效率。 [0006] 由于在电波较弱的区域发射功率增加,移动终端的电池电量在电波较弱的区域会快速消耗,从而无法有效控制电池。 发明内容 [0007] 本发明提供一种根据在移动终端中接收到的信号的强度来控制移动终端的RF单元的方法。 [0008] 本发明还提供了一种在低电波区域控制移动终端的RF单元的方法,从而可以提高移动终端的电池效率。 [0009] 本发明的附加特征将在以下描述中阐述,并且部分将从描述中显而易见,或者可以通过本发明的实践来了解。 [0010] 本发明公开了一种移动终端,包括用于接收电波的RF单元和控制器。 控制器将RF单元中接收到的电波的强度与电波强度的参考值进行比较,比较结果确定控制器是否关闭RF单元。 [0011] 本发明还公开了一种在移动终端中执行RF单元的控制模式的方法,包括在RF单元中接收电波,将接收到的电波的强度与电波强度的参考值进行比较,以及关闭 如果接收到的电波的强度小于电波强度的参考值,则 RF 单元。 [0012] 应当理解,前面的一般描述和下面的详细描述都是示例性和解释性的,并且旨在提供对所要求保护的本发明的进一步解释。 附图的简要说明 [0013] 附图被包括在内以提供对本发明的进一步理解并且被并入并构成本说明书的一部分,它们说明了本发明的实施例,并且与描述一起用于解释本发明的原理。 [0014] 图1是示出根据本发明示例性实施例的用于执行RF单元的控制模式的移动终端的配置的框图。 [0015] 图2是示出根据本发明示例性实施例的执行RF单元的控制模式的方法的流程图。 [0016] 图3是示出根据本发明另一示例性实施例的执行RF单元的控制模式的方法的流程图。 图示实施例的详细说明 [0017]下文参照附图更全面地描述本发明,其中示出了本发明的实施例。 然而,本发明可以以许多不同的形式来实施并且不应被解释为限于本文所阐述的实施例。 相反,提供这些实施例是为了使本公开是彻底的,并且将向本领域技术人员充分传达本发明的范围。 在附图中,为了清楚起见,可能夸大了层和区域的尺寸和相对尺寸。 图中相同的附图标记表示相同的元件。 [0018] 应当理解,当一个元件或层被称为“在”或“连接到”另一个元件或层时,它可以直接在另一个元件或层上或直接连接到另一个元件或层,或者中间的元件或层可以是 当下。 相反,当一个元素被称为“直接在”或“直接连接到”另一个元素或层时,不存在中间的元素或层。 [0019] 根据本发明示例性实施例的移动终端包括信息通信设备和多媒体设备,例如移动通信终端、移动电话、个人数字助理(PDA)和智能电话,及其应用。 [0020] 图1是示出根据本发明示例性实施例的用于执行RF单元的控制模式的移动终端的配置的框图。 [0021] 参考图1,移动终端包括RF单元 101 , 一个输入单元 103 , 一个控制器 105 , 电源控制器 107 , 一个数值转换单元 109 , 数值比较单元 111 , 一个显示单元 113 , 一个记忆单元 115 , 和一个音频单元 117 . [0022] 射频单元 101 执行移动终端和移动通信网络之间的无线通信。 例如,射频单元 101 通过移动通信网络发送和接收语音数据、字符消息和多媒体消息。 射频单元 101 以控制器设定的间隔接收电波 105 并将接收到的电波提供给控制器 105 . [0023] 输入单元 103 可能包括一个通用键盘。 此外,输入单元 103 可以包括触摸屏、触摸板和滚轮。 输入单元 103 接收用户操作信号以控制移动终端的操作并将信号提供给控制器 105 . [0024] 控制器 105 控制移动终端中单元的一般操作。 控制器 105 包括调制解调器和编解码器,该编解码器具有发射器以编码和调制要由RF单元发射的信号 101 接收器对接收到的信号进行解调和解码。 [0025] 特别是控制器 105 控制射频单元 101 进入控制模式,比较射频单元接收到的电波强度 101 具有电波强度的参考值,并转动射频单元 101 根据比较结果打开或关闭。 为此,控制器 105 包括一个电源控制器 107 , 一个数值转换单元 109 , 和一个数值比较单元 111 . 此外,控制器 105 终止并维持射频单元的控制模式 101 响应输入单元提供的输入信号 103 . [0026] 电源控制器 107 可以转动射频单元 101 通过不向 RF 单元供电来关闭 101 或转动射频单元 101 通过向 RF 单元供电来开启 101 . [0027] 数值转换单位 109 转换 RF 单元中接收到的电波强度 101 到数值并将数值提供给数值比较单元 111 . [0028] 数值比较单元 111将对应于接收电波强度的数值与电波强度的参考值进行比较,并将比较结果提供给功率控制器 107 . [0029] 显示单元 113 显示与操作状态、操作结果相关的信息,以及由控制器以移动终端为单位执行的其他信息 105 . 显示单元 113 可以包括诸如液晶显示器(LCD)、有机发光二极管(OLED)或等离子显示面板(PDP)的显示装置。 [0030] 控制器 105 控制内存单​​元 115 存储与移动终端的操作相关的信息(例如,关于设置状态和菜单的信息)。 [0031] 记忆单元 115 将接收到的电波强度存储为在切换到控制模式以转动 RF 单元时要参考的参考值 101 打开或关闭。 记忆单元 115 还存储在RF单元的控制模式下要从基站接收电波的预设时间段和间隔 101 . [0032] 记忆单元 115 存储预设时间段作为参考时间段,在此期间RF单元 101 开启并存储移动终端省电模式下功能的省电数值,包括灯光亮度和点亮时间。 [0033] 音频单元 117 将通过麦克风 MIC 输入的模拟音频信号转换为数字信号,并转换从控制器输出的数字音频信号 105 转换成模拟音频信号并通过扬声器 SPK 再现信号。 [0034] 图2是示出根据本发明示例性实施例的执行RF单元的控制模式的方法的流程图。 [0035] 参见图2,射频单元的控制方式 101 由用户选择(S 201 ),移动终端进入省电模式(S 203 )。 射频单元的控制方式 101 是移动终端移动到电波较弱的区域时为降低电池耗电量而设置的模式。 省电模式是设置为将移动终端的光照亮度和/或光照时间等功能转换为预设的省电数值的模式。 [0036] 控制器 105 控制射频单元 101 在预设时间段内以一定间隔接收电波(S 205 )。 [0037] 具体来说,控制器 105 控制射频单元 101 在进入射频单元的控制模式之前每隔一段时间接收电波 101 , 间隔可以是时隙。 在时隙的情况下,移动终端在时隙从基站接收电波,每个时隙对应于基站根据系统设置分配的固有时隙周期索引。 此后,控制器 105 控制射频单元 101 进入控制模式,在预设时间间隔内接收电波。 [0038] 例如,如果预设时间段为 3 分钟,间隔时间为 20 秒,则控制器 105 控制射频单元 101 在 3 分钟内以 20 秒的间隔接收 9 次电波。 该间隔可以是接收间隔(例如每20秒)、接收次数(例如9次)或时隙。 [0039] 控制器 105 控制数值转换单元 109 测量接收电波的强度并将接收电波的强度转换为数值,并将转换后的数值提供给数值比较单元 111 (S 207 )。 [0040] 控制器 105 控制数值比较单元 111 判断接收到的电波强度是否大于或等于电波强度参考值(S 209)。 如果接收到的电波强度大于或等于电波强度参考值,控制器 105 判断请求是否维持射频单元的控制模式 101 已收到(S 211 )。 如果请求维持射频单元的控制模式 101 收到,控制器 105 维持射频单元的控制模式 101 (S 213 ) 并继续接收电波。 控制器 105 通过返回步骤 S 重复该过程 205 同时维持射频单元的控制模式 101 在步骤 S 213 . [0041] 如果请求维持射频单元的控制模式 101 在步骤 S 未收到 211 , 控制器 105 终止射频单元的控制模式 101 (S 215 ) 并且过程返回到步骤 S 205 . [0042] 在另一示例性实施例中,如果在步骤S接收到的电波的强度大于或等于电波强度的参考值 209 , 步骤 S 211 和 S 215 可以省略,该过程可以在步骤S继续 213 . [0043] 如果在步骤S接收电波的强度小于电波强度的参考值 209 , 控制器 105 转动射频单元 101 关(S 217 )。 当预设时间段已过时( 219 ), 控制器 105 转动射频单元 101 上(S 221 )。 [0044] 控制器 105 判断是否请求终止射频单元的控制模式 101 已收到(S 223 )。 如果请求终止 RF 单元的控制模式 101 没有收到,返回步骤S 205 和射频单元 101 继续接收控制器控制的电波 105 . 如果请求终止 RF 单元的控制模式 101 收到,控制器 105 终止射频单元的控制模式 101 (S 225 )。 [0045] 例如,如果预设时间段设置为 1 小时,则控制器 105 转动射频单元 101 从 RF 单元开始经过 1 小时后亮起 101 被关闭并接收电波。 RF单元的关闭状态 101 是阻止向 RF 单元供电的状态 101 ,以及射频单元的开启状态 101 是向 RF 单元供电的状态 101 因此,电波被连续接收。 [0046] 图3是示出根据本发明另一示例性实施例的执行RF单元的控制模式的方法的流程图。 [0047] 参照图3,控制器 105 控制射频单元 101 每隔一段时间接收电波(S 301 )。 间隔可以是时隙。 例如,移动终端可以在时隙从基站接收电波,每个时隙对应于基站根据系统设置分配的固有时隙周期索引。 [0048] 控制器 105 控制数值转换单元 109 测量接收到的电波的强度并将接收到的电波的强度转换为数值(S 303 )。 控制器 105 然后将数值提供给数值比较单元 111 . [0049] 控制器 105 控制数值比较单元 111 判断接收到的电波强度对应的数值是否大于或等于电波强度的参考值(S 305 )。 如果数值大于或等于电波强度参考值,控制器 105 维持射频单元的控制模式 101 (S 307 ),继续接收电波,并返回步骤S重复该过程 301 . [0050] 如果数值小于步骤 S 的参考值305 , 控制器 105 判断射频单元的控制模式是否 101 设置(S 309 )。 如果射频单元的控制模式 101 未设置,该过程在步骤 S 继续 307 . [0051] 如果射频单元的控制模式 101 设置,控制器 105 转动射频单元 101 关(S 311 )。 当控制器 105 确定在 RF 单元之后经过了预设时间段 101 被关闭(S 313 ), 控制器 105 打开射频单元 101 (S 315 ) 并通过返回步骤 S 重复该过程 301 . [0052] 如上所述,根据本发明的示例性实施例,通过根据接收信号的强度控制移动终端的RF单元,可以有效地管理电池。 [0053] 此外,通过在电波较弱的区域关闭RF单元,可以减少用于接收电波的电池功耗。 [0054] 此外,通过仅关闭移动终端中的RF单元,即使当移动终端的RF单元被关闭时,也可以不受限制地使用移动终端的另一功能。 [0055] 对于本领域的技术人员来说,在不脱离本发明的精神或范围的情况下,可以对本发明进行各种修改和变化是显而易见的。 因此,本发明旨在覆盖本发明的修改和变化,只要它们落入所附权利要求及其等同物的范围内。(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentInstructionTextMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.309 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Preparing: SELECT publicdate,patentno,id,publicno,simple_family,inpadoc_family,patsnap_family FROM os_patent WHERE (patentno IN (?,?)) order by appdate, patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.310 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList ==> Parameters: KR100782510B1(String), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.463 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Preparing: SELECT id,type,patent_no FROM os_patent_simplefamily WHERE (patent_no IN (?,?) AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.464 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList ==> Parameters: KR100782510B1(String), US20080125034A1(String), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily ( type, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.481 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert ==> Parameters: 1(Integer), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Preparing: select a.* from os_patent_simplefamily_link a left join os_patent_simplefamily b on a.family_id=b.id where b.type=? and a.patent_no in ( ? , ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.516 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo ==> Parameters: 1(Integer), KR100782510B1(String), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.getPatentFamilyLinkByPatentNo <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.533 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271689(Integer), KR100782510B1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Preparing: INSERT INTO os_patent_simplefamily_link ( family_id, patent_no ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.568 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert ==> Parameters: 271689(Integer), US20080125034A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Preparing: UPDATE os_patent SET patentno=?, publicno=?, publicdate=?, simple_family=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.603 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById ==> Parameters: US20080125034A1(String), US20080125034A1(String), 1211990400(Integer), 271689(Integer), 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.638 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (name IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.639 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 三星电子株式会社(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.683 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.717 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186021(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.751 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 1(Integer), 186021(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.785 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Preparing: UPDATE os_patent_applicant SET name=?, bname=?, remark=?, uid=?, update_time=?, type=?, province_id=?, city_id=?, area_id=?, `merge`=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.786 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById ==> Parameters: SAMSUNG ELECTRONICS CO., LTD.(String), 三星电子株式会社(String), 255(String), 0(Integer), 1660811379(Integer), 2(Integer), 0(Integer), 0(Integer), 0(Integer), false(Boolean), 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Preparing: DELETE FROM os_applicant_attr WHERE (pid = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.819 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete ==> Parameters: 186021(Integer), 2(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.853 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Preparing: INSERT INTO os_applicant_attr ( applicantid, type, pid, `order` ) VALUES ( ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.854 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert ==> Parameters: 19148(Integer), 2(Integer), 186021(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.888 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.905 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.922 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.923 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.923 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 19148(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.940 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ? AND pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.941 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 226(Integer), 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.957 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Preparing: INSERT INTO os_thematic_pid ( zid, pid ) VALUES ( ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.958 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert ==> Parameters: 226(Integer), 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.993 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.ProjectPatentLinkMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.994 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:40.994 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 16 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Preparing: DELETE FROM os_patent_affair WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.011 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete ==> Parameters: 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.168 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.delete <== Updates: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Preparing: INSERT INTO os_patent_affair ( status, simplestatus, pid ) VALUES ( ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.169 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert ==> Parameters: 撤回(String), 2(Integer), 186021(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.210 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.PatentAffairMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Preparing: SELECT id,type,uid AS createBy,ctime AS startTime,tid AS projectId,mfields AS fieldNum,mun AS total,endtime,status,filename,filesize,downexcel AS url,product_id,old_name FROM os_task WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.220 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById ==> Parameters: 1830(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.237 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.240 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Preparing: UPDATE os_task SET type=?, uid=?, ctime=?, tid=?, mfields=?, mun=?, endtime=?, status=?, filename=?, filesize=?, downexcel=?, old_name=? WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.241 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById ==> Parameters: 1(Integer), 103(Integer), 1681975984(Integer), 226(Integer), 0(Integer), 99(Integer), 1681976201(Integer), 2(Integer), 39cf12ffed8b43b1b325f88d7b1ecb49.XLSX(String), 6093542(Long), \20230420\39cf12ffed8b43b1b325f88d7b1ecb49.XLSX(String), 手机-美国.XLSX(String), 1830(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:36:41.275 DEBUG 10820 [singleThreadAsyncTaskExecutor-1] cn.cslg.pas.mapper.TaskMapper.updateById <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.640 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.640 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.660 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.979 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.980 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.995 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.995 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 249(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:02.998 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.015 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.032 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.insert ==> Preparing: INSERT INTO os_patent_keywords_highlight ( name, project_id, user_id, enable, `default`, config ) VALUES ( ?, ?, ?, ?, ?, ? ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.032 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.insert ==> Parameters: 默认模板(String), 249(Integer), 103(Integer), false(Boolean), true(Boolean), [{"color":"#5470c6","keywords":""},{"color":"#91cc75","keywords":""},{"color":"#fac858","keywords":""},{"color":"#ee6666","keywords":""},{"color":"#73c0de","keywords":""}](String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.072 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.463 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.463 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.484 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.484 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.485 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String), COUNTRIES(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.506 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 268 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.506 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.506 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.526 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.527 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.528 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 185041(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.547 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.547 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.548 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.567 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.567 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.568 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75799(Integer), 75766(Integer), 75800(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.587 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.588 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.588 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.677 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.678 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.695 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.745 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.746 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.746 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.768 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.769 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Preparing: SELECT id,datetime,status,simplestatus,content,remark,pid AS patentId FROM os_patent_affair WHERE (pid = ?) ORDER BY datetime DESC [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.770 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.877 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentAffairMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.878 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.878 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_STATUS(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.897 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 56 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.898 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.898 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.918 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.920 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.920 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 185041(Integer), 249(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.940 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.941 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Preparing: SELECT id,patent_id,manual,manual_out FROM os_patent_instruction_text WHERE (patent_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.941 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.964 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInstructionTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.965 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentRightMapper.selectList ==> Preparing: SELECT id,patent_id,content,content_out,type,sort,parent_sort FROM os_patent_right WHERE (patent_id = ?) ORDER BY sort ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.965 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentRightMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.986 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentRightMapper.selectList <== Total: 18 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.987 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentImageMapper.selectList ==> Preparing: SELECT id,status,address AS url,pid AS patentId,file_name FROM os_patent_img WHERE (pid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:03.987 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentImageMapper.selectList ==> Parameters: 185041(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:04.045 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentImageMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:04.052 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInstructionMapper.selectList ==> Preparing: SELECT id,patent_no,url,patent_id,remark,create_by,type,size,file_name,status,create_time,update_time FROM os_patent_instruction WHERE (patent_no = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:04.052 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInstructionMapper.selectList ==> Parameters: CN104101341A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:37:04.130 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentInstructionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.493 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.494 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.529 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.612 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.612 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.630 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.649 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.651 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.669 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.669 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.685 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.686 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.686 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.702 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.703 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.703 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.720 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.720 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.737 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.737 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.738 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.738 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.748 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.748 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.754 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.755 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.755 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.770 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.774 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.775 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.776 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.793 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.794 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.794 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.811 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.811 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.811 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.828 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.828 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.845 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.845 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.846 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.846 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.849 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.849 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.862 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.863 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.863 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.866 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.867 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id,a.product_id,a.structure_id,a.is_category, u.`name` as create_name, (select count(*) from os_thematic_file where zid = a.id and type = 1) as report_num from os_thematic a left join os_distribution u on u.id = a.creat_id order by a.`create_time` desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.867 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Parameters: 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.880 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.880 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.886 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.987 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.987 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:42.999 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.000 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.005 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.006 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.007 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.017 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.024 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.614 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.614 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: QUERY_GROUP(String), ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:48:43.631 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 50 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.031 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.031 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.065 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.469 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.469 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: QUERY_GROUP(String), ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.486 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 50 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.494 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.494 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.506 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.506 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.511 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.524 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.524 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.542 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.542 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.542 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.560 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.560 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.560 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.578 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.578 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.595 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.595 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.595 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.595 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.613 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.614 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.614 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.630 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.631 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.631 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.648 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.648 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.648 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.665 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.666 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.666 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.683 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.683 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.701 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.701 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.702 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.702 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.719 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.720 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.720 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.737 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.738 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.882 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.883 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:37.903 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.011 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.011 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.015 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.016 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.028 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.029 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id,a.product_id,a.structure_id,a.is_category, u.`name` as create_name, (select count(*) from os_thematic_file where zid = a.id and type = 1) as report_num from os_thematic a left join os_distribution u on u.id = a.creat_id order by a.`create_time` desc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.029 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList ==> Parameters: 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.033 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.034 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.034 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.047 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.051 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.104 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.104 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:38.121 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.470 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.470 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.490 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.609 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.609 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.626 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.628 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.629 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.646 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.919 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.919 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.936 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.955 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.955 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 222(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.972 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.972 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.973 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.992 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.992 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:46.992 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 222(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.011 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.012 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.012 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.030 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.030 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.031 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer), 75490(Integer), 75491(Integer), 6659(Integer), 47246(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.049 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.049 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.050 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.218 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.219 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.219 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48577(Integer), 48576(Integer), 48578(Integer), 48579(Integer), 48580(Integer), 48581(Integer), 48582(Integer), 48583(Integer), 48580(Integer), 48579(Integer), 48584(Integer), 48585(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.237 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.237 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.237 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.254 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.255 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.255 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.274 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 64 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.275 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.275 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.296 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.297 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.297 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer), 124(Integer), 117(Integer), 118(Integer), 144(Integer), 145(Integer), 146(Integer), 147(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.314 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.315 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.315 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer), 598(Integer), 599(Integer), 600(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.332 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.333 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.333 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer), 33386(Integer), 33389(Integer), 33392(Integer), 33395(Integer), 33398(Integer), 33401(Integer), 33404(Integer), 33407(Integer), 33410(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.350 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 22 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.351 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.351 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer), 33387(Integer), 33390(Integer), 33393(Integer), 33396(Integer), 33399(Integer), 33402(Integer), 33405(Integer), 33408(Integer), 33411(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.369 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.371 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.371 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer), 33388(Integer), 33391(Integer), 33394(Integer), 33397(Integer), 33400(Integer), 33403(Integer), 33406(Integer), 33409(Integer), 33412(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.389 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.389 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.389 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.408 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.408 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.408 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.426 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.427 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (id IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.427 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.444 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.445 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Preparing: SELECT id,name AS text,cid AS fieldId FROM os_patent_field_text WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.445 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.462 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.463 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.463 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.480 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.480 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid IN (?,?)) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.480 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:47.498 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:48.995 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:48.995 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.015 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.380 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Preparing: SELECT count(0) FROM product p JOIN product_category pc ON p.product_category_id = pc.id WHERE create_person_tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.380 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.397 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.401 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.401 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.418 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.418 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.436 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.436 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.436 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.453 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.454 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.454 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.472 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.472 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.490 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.490 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.490 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.490 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.508 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.508 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.508 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.525 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.525 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.525 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.543 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.544 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.544 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.561 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.561 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.561 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.579 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.579 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.596 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.596 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.596 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.596 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.613 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.613 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.613 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.630 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.631 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.704 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category WHERE tenant_id = ? order by pc_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.704 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.721 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.721 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.739 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.739 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.739 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.757 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.757 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.757 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.774 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:49.774 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductCategoryMapper.query <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.664 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.665 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.684 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.840 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.841 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.862 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.863 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.864 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:53.881 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:54.116 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:54.117 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:54.134 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.406 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.406 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.426 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.456 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.456 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.474 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.474 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.474 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.492 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.494 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.494 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:56.512 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.269 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.269 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.287 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.288 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.288 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.307 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.307 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.308 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.325 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.742 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.742 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.760 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.760 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.760 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.777 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.778 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.778 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:49:58.796 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.125 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.125 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.145 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.461 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.461 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.478 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.479 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.479 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.496 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.497 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.497 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 47(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:04.515 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.512 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.513 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.533 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.866 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.866 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.884 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.884 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.884 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.901 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.902 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.902 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 42(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:08.920 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.524 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.524 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.542 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.542 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.542 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.560 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.560 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.560 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 42(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:10.578 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.834 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.834 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.855 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.877 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.877 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.895 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.895 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.895 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.913 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.914 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.914 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 41(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:15.932 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.562 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.562 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.580 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.580 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.580 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.598 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.599 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.599 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 41(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:17.616 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.545 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.545 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.565 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.881 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.881 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.898 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.899 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.899 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.916 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.917 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.917 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.934 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.948 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.948 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.966 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.966 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.966 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:22.983 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.438 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.countByparentIdAndStructureName ==> Preparing: select count(*) from structure where parent_id = ? and structure_name = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.438 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.countByparentIdAndStructureName ==> Parameters: 0(Integer), 青春(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.456 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.countByparentIdAndStructureName <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.502 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.insert ==> Preparing: insert into structure (parent_id, structure_name, path, remark, product_id, create_person_id, create_person_name) values (?, ?, ?, ?, ?, ?, ?); [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.503 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.insert ==> Parameters: 0(Integer), 青春(String), null, null, 48(Integer), 103(Integer), 管理员(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.538 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.539 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.update ==> Preparing: update structure SET parent_id = ?, structure_name = ?, path = ?, product_id = ? where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.539 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.update ==> Parameters: 0(Integer), 青春(String), 0,179(String), 48(Integer), 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.573 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.update <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.618 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.619 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.636 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.636 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.636 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.654 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 13 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.655 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.655 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.672 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.672 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.690 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.691 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.691 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.707 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.708 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.708 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.708 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:32.726 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:33.063 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:33.063 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:33.081 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:33.082 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:33.083 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:33.100 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.488 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.countByparentIdAndStructureName ==> Preparing: select count(*) from structure where parent_id = ? and structure_name = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.488 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.countByparentIdAndStructureName ==> Parameters: 179(Integer), 青春4(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.506 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.countByparentIdAndStructureName <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.545 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.insert ==> Preparing: insert into structure (parent_id, structure_name, path, remark, product_id, create_person_id, create_person_name) values (?, ?, ?, ?, ?, ?, ?); [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.545 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.insert ==> Parameters: 179(Integer), 青春4(String), null, null, 48(Integer), 103(Integer), 管理员(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.579 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.insert <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.580 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.update ==> Preparing: update structure SET parent_id = ?, structure_name = ?, path = ?, product_id = ? where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.580 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.update ==> Parameters: 179(Integer), 青春4(String), 0,179,180(String), 48(Integer), 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.615 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.StructureMapper.update <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.977 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.977 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.995 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.995 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:44.995 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.013 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.013 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.014 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.031 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.031 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.048 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.049 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.049 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.066 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.066 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.067 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.067 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.084 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.085 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.102 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.102 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.102 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.120 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.120 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.120 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.120 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 180(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.138 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.241 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.241 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.260 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.260 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.260 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:45.277 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.210 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.210 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.230 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.316 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Preparing: SELECT count(0) FROM product p JOIN product_category pc ON p.product_category_id = pc.id WHERE create_person_tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.317 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.334 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.334 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.335 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.352 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.353 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.369 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.369 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.370 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.387 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.387 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.387 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.405 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.405 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.422 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.423 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.423 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.423 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.441 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.441 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.441 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.459 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.459 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.459 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.477 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.477 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.477 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.493 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.494 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.494 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.511 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.512 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.529 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.529 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.529 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.529 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.546 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.547 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.547 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.564 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.564 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.634 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category WHERE tenant_id = ? order by pc_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.634 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.652 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.652 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.670 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.671 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.671 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.688 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.688 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.688 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.706 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:52.706 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductCategoryMapper.query <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.002 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.002 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.022 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.341 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.342 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.359 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.359 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.359 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.377 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.377 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.377 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.395 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.395 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.413 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.413 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.413 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.430 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.431 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.431 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.431 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.450 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.450 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.468 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.468 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.468 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.486 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.486 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.486 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.486 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 180(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:56.504 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.516 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.516 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById ==> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.533 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.533 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.551 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.552 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.552 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.569 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.569 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.569 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.569 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.587 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.587 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.587 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.604 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.604 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.605 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.623 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.623 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.640 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.641 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.641 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.658 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.658 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.658 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.658 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 180(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:50:57.676 DEBUG 10820 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:00.641 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:00.641 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:00.662 DEBUG 10820 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:00.711 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:00.711 DEBUG 10820 [http-nio-8877-exec-8] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:01.013 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:01.013 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:01.047 DEBUG 10820 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.123 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.123 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.143 DEBUG 10820 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.232 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.232 DEBUG 10820 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.303 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.303 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:51:05.339 DEBUG 10820 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.241 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.241 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.264 DEBUG 10820 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.326 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.326 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.344 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.345 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.345 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.362 DEBUG 10820 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.586 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.586 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:53:03.604 DEBUG 10820 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.551 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.569 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.633 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.853 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.854 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.872 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.872 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.873 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.891 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.953 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.954 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:01.972 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.171 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.172 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.210 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.581 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.582 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.588 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.589 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.599 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.606 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.608 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.608 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:19.625 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.814 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.815 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.821 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.822 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 43(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.832 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.840 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.842 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.842 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:30.860 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.739 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.739 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.760 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.819 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_structure_patent t ON t.patent_no = a.patentno WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.820 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.838 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.840 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.840 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:32.858 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:33.120 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:33.121 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:33.138 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.215 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.216 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.251 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.325 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_structure_patent t ON t.patent_no = a.patentno WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.325 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.343 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.345 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.345 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.363 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.385 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.385 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:39.403 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.037 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.037 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.058 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.109 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_structure_patent t ON t.patent_no = a.patentno WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.110 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.128 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.129 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.130 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.147 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.402 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.403 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:55:54.420 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.155 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.156 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.177 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.505 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.505 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.512 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.513 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.523 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.531 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.532 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.532 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:03.550 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.381 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.382 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.401 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.452 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_structure_patent t ON t.patent_no = a.patentno WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.452 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.470 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.471 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.472 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.490 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.755 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.755 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:10.772 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.032 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.032 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.052 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.412 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.413 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.420 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_structure_patent t ON t.patent_no = a.patentno WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.421 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.430 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.439 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.440 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.440 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:22.457 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.360 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.361 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.381 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.443 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.444 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.462 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.464 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.464 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.482 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.736 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.736 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:56:56.754 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.083 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPatentNos ==> Preparing: select DISTINCT a.patentno as patent_no from os_patent a left join asso_product_patent i on i.patent_no=a.patentno left join asso_structure_patent t on t.patent_no =a.patentno WHERE a.patentNo REGEXP ? and (i.product_id !=? or i.product_id is null) and (t.product_id !=? or t.product_id is null) order by a.patentno [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.083 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPatentNos ==> Parameters: (^|,)(US20110256287A1)(,|$)(String), 48(Integer), 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.263 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPatentNos <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.269 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.insertBatch ==> Preparing: insert into asso_product_patent (product_id,patent_no) values (?,?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.270 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.insertBatch ==> Parameters: 48(Integer), US20110256287A1(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.304 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.insertBatch <== Updates: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.363 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_product_patent i ON i.patent_no = a.patentno WHERE i.product_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.363 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.652 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.655 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Preparing: select DISTINCT a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join asso_product_patent i on i.patent_no=a.patentno WHERE i.product_id =? order by a.patentno LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.655 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList ==> Parameters: 48(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.945 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.948 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.948 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 165337(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.966 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.968 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.969 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 75758(Integer), 75759(Integer), 75760(Integer), 75761(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.985 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.988 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:09.988 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 165337(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.145 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.148 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.148 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 211954(Integer), 211955(Integer), 211956(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.166 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.169 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.169 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 165337(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.186 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.188 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.189 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 165337(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.206 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.216 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.216 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 165337(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.237 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.239 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.239 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 239717(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.257 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 12 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.259 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.259 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.276 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.278 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.278 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.296 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.297 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.298 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.315 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.339 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Preparing: SELECT id,datetime,status,simplestatus,content,remark,pid AS patentId FROM os_patent_affair WHERE (pid = ?) ORDER BY datetime DESC [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.339 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAffairMapper.selectList ==> Parameters: 165337(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.446 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAffairMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.447 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.448 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_STATUS(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.465 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 56 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.472 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.selectById ==> Preparing: SELECT id,name,nameout,patentno,abstract AS abstractStr,abstractout,applicationno,appdate AS applicationDate,publicno,publicdate,fpublicdate AS firstPublicDate,publictono AS publicAccreditNo,publictodate AS publicAccreditDate,bureau,status AS simpleStatus,type,code,manual,manualout,page AS docPage,inventornum,num1 AS mainRightNum,num2 AS rightNum,num3 AS selfRightNum,content AS rightContent,selfcontent AS selfRightContent,contentout AS rightContentOut,priorityno,prioritycountry,prioritydate,simplefamilynum,inpadocfamilynum,patsnapfamilynum,quoteno AS quoteNum,quotedno AS quotedNum,quotedno3 AS quotedNum3,quotedno5 AS quotedNum5,nonpatentquoteno AS notPatentQuoteNum,wonational AS wo,agencyid,examiner,assexaminer AS aidExaminer,quote,quoted,nonpatentquote AS notPatentQuote,abstract_path,firstapplicantnum AS applicantNum,selfcontentnum AS selfRightContentNum,simple_family,inpadoc_family,patsnap_family,epcountry AS epStatus FROM os_patent WHERE id=? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.473 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.selectById ==> Parameters: 165337(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.491 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.selectById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.501 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid = ? AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.501 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 165337(Integer), null [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:10.519 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.039 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.040 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.060 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.105 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.105 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.123 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.124 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.124 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.143 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.145 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.146 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.164 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.165 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.182 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.182 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.182 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.200 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.200 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.201 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.201 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.219 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.219 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.236 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.237 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.237 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.254 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.254 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.255 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.255 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 180(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:16.273 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.906 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.906 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById ==> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.924 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.924 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.941 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.942 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.942 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.959 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.959 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.getStandardAndPictureById <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.959 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.960 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.977 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.978 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.978 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.998 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.998 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:17.999 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.016 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.016 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.033 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.033 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.033 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.051 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.051 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.051 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.052 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 180(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:18.069 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.309 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.309 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.330 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 123 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.381 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT DISTINCT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN asso_structure_patent t ON t.patent_no = a.patentno WHERE t.structure_id = ?) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.381 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount ==> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.399 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.asso.AssoProductPatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.400 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.400 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.417 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.689 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.689 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: null [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:20.707 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.465 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.465 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.485 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.576 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Preparing: SELECT count(0) FROM product p JOIN product_category pc ON p.product_category_id = pc.id WHERE create_person_tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.577 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.594 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.596 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.597 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.615 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.615 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.632 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.632 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.633 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.650 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.650 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.650 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.668 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.668 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.686 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.686 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.686 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.686 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.703 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.703 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.703 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.721 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.722 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.722 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.739 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.741 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.742 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.759 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.759 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.759 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.777 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.777 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.794 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.794 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.794 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.794 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.812 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.812 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.812 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.830 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.830 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.899 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category WHERE tenant_id = ? order by pc_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.899 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.917 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.918 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.934 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.935 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.935 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.952 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.952 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.952 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.970 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:24.970 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductCategoryMapper.query <== Total: 3 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.478 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.479 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.499 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.633 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.633 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.650 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.662 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.662 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.673 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.674 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 222(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.680 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.687 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.687 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.692 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:40.704 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.015 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.016 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.033 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.061 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.061 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.088 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.089 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.090 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 222(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.099 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.099 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.109 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.110 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.111 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.117 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.129 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.130 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.130 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer), 75490(Integer), 75491(Integer), 6659(Integer), 47246(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.147 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.149 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.149 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.301 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.302 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.302 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48577(Integer), 48576(Integer), 48578(Integer), 48579(Integer), 48580(Integer), 48581(Integer), 48582(Integer), 48583(Integer), 48580(Integer), 48579(Integer), 48584(Integer), 48585(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.320 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.321 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.321 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.335 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.336 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.338 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.339 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.339 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.354 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 43 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.357 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 64 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.358 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.359 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.379 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.380 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.381 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer), 124(Integer), 117(Integer), 118(Integer), 144(Integer), 145(Integer), 146(Integer), 147(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.397 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.399 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.399 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer), 598(Integer), 599(Integer), 600(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.416 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.417 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.418 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer), 33386(Integer), 33389(Integer), 33392(Integer), 33395(Integer), 33398(Integer), 33401(Integer), 33404(Integer), 33407(Integer), 33410(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.436 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 22 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.438 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.438 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer), 33387(Integer), 33390(Integer), 33393(Integer), 33396(Integer), 33399(Integer), 33402(Integer), 33405(Integer), 33408(Integer), 33411(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.455 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.456 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.456 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer), 33388(Integer), 33391(Integer), 33394(Integer), 33397(Integer), 33400(Integer), 33403(Integer), 33406(Integer), 33409(Integer), 33412(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.473 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.474 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.474 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.492 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.493 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.494 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.510 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.512 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (id IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.512 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.530 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.531 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Preparing: SELECT id,name AS text,cid AS fieldId FROM os_patent_field_text WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.531 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.549 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.554 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.554 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.570 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.572 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid IN (?,?)) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.572 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:41.591 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.451 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.451 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.453 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.453 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.469 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.470 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.470 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.471 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.487 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.488 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.488 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.506 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.725 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.725 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:46.743 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.292 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.292 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.309 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.310 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.310 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.328 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.328 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.328 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.345 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.599 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.599 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.617 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.693 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.693 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:57:56.711 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.126 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.126 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.145 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.467 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.467 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.485 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.485 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.485 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.504 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.507 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.508 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 41(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.525 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.539 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.539 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.556 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.557 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.557 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:04.574 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.127 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.128 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.147 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.469 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.469 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.487 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.487 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.487 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.507 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.509 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.509 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 42(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.526 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.541 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.541 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.558 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.558 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.558 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:09.575 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.245 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.246 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.265 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.581 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.581 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.598 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.599 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.599 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.616 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.616 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.617 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 47(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.636 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.651 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.651 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.667 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.668 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.668 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:13.688 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:19.713 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:19.713 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:19.734 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.051 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.051 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.072 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.072 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectList ==> Preparing: SELECT id,parent_id,structure_name,path,remark,product_id,create_person_id,create_person_name,create_time,modified_time FROM structure [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.072 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.093 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectList <== Total: 14 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.094 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.094 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 0(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.115 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.115 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.132 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.132 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.132 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 179(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.150 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.150 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.150 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.151 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 179(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.167 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Preparing: select id, structure_id, name, suffix, url from asso_structure_picture where structure_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.167 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.185 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.185 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Preparing: select count(*) from asso_structure_patent where structure_id in (select id from structure where find_in_set(?, path)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.185 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 ====> Parameters: 180(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.201 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentId3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.202 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.204 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Preparing: select id s_id, parent_id, structure_name, path, remark, product_id, create_person_name, create_time from structure where parent_id = ? and product_id = ? and id in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) order by s_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.205 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId ==> Parameters: 180(Integer), 48(Integer), 151(Integer), 153(Integer), 154(Integer), 155(Integer), 158(Integer), 161(Integer), 162(Integer), 164(Integer), 165(Integer), 167(Integer), 168(Integer), 170(Integer), 179(Integer), 180(Integer), 0(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.227 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.StructureMapper.selectByParentIdAndProductId <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.249 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.249 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.270 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.270 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Preparing: select id, parent_id, structure_name, path, remark, product_id from structure where product_id = ? order by path [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.271 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId ==> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:20.287 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.StructureMapper.selectAllByProductId <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.184 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.184 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.184 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.184 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.201 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.202 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.202 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.202 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.220 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.220 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.221 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.238 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.275 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.275 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:37.293 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.648 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ? AND type = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.649 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer), 6(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.667 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.668 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.668 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.685 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.948 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.getPatentQuerySourcePageList_mpCount ==> Preparing: SELECT COUNT(*) AS total FROM ((SELECT ifnull(NULL, '未选择') AS label, count(a.id) AS `count`, ifnull(NULL, 'null') AS `value`, GROUP_CONCAT(DISTINCT a.id) AS ids FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? AND a.id NOT IN (SELECT pid FROM os_patent_field_patent_link WHERE cid = ?)) UNION ALL (SELECT ifnull(d.name, '未选择') AS label, count(DISTINCT e.pid) AS `count`, ifnull(d.id, 'null') AS `value`, GROUP_CONCAT(DISTINCT a.id) AS ids FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id LEFT JOIN os_patent_field_patent_link e ON e.pid = b.pid LEFT JOIN os_patent_field c1 ON c1.id = e.cid LEFT JOIN os_patent_field_tree d ON d.cid = e.cid WHERE b.zid = ? AND c1.id = ? AND e.fid IN (SELECT id FROM os_patent_field_tree WHERE cid = c1.id AND find_in_set(d.id, replace(path, '/', ','))) GROUP BY d.id)) AS temp WHERE 1 = 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.948 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.getPatentQuerySourcePageList_mpCount ==> Parameters: 222(Integer), 4685(Integer), 222(Integer), 4685(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.967 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.getPatentQuerySourcePageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.967 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.getPatentQuerySourcePageList ==> Preparing: select temp.* from (( select ifnull(null, '未选择') as label, count(a.id) as `count`, ifnull(null, 'null') as `value`, group_concat(distinct a.id) as ids from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? and a.id not in (select pid from os_patent_field_patent_link where cid = ?) ) union all ( select ifnull(d.name, '未选择') as label, count(distinct e.pid) as `count`, ifnull(d.id, 'null') as `value`, group_concat(distinct a.id) as ids from os_patent a left join os_thematic_pid b on b.pid = a.id left join os_patent_field_patent_link e on e.pid = b.pid left join os_patent_field c1 on c1.id = e.cid left join os_patent_field_tree d on d.cid = e.cid WHERE b.zid = ? and c1.id = ? and e.fid in (select id from os_patent_field_tree where cid = c1.id and find_in_set(d.id , replace(path , '/', ','))) group by d.id )) as temp where 1 = 1 order by `count` desc, `value` asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.968 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.getPatentQuerySourcePageList ==> Parameters: 222(Integer), 4685(Integer), 222(Integer), 4685(Integer), 9999(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:47.986 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentMapper.getPatentQuerySourcePageList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.827 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.827 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.847 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.902 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMarketDataMapper.patentQueryByMonth ==> Preparing: SELECT CONCAT(YEAR(CONCAT(sale_time,'-02')),'-',MONTH(CONCAT(sale_time,'-02'))) AS market_date, sum(sale_money) AS sale_total_money, CAST(sum(custom_license_rate * sale_money) AS DECIMAL (19, 2)) AS custom_license_money FROM product_market_data WHERE product_id IN ( SELECT product_id FROM asso_product_patent WHERE patent_no IN ( ? , ? ) ) GROUP BY market_date [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.902 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMarketDataMapper.patentQueryByMonth ==> Parameters: CN111243486A(String), CN111258141A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.920 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMarketDataMapper.patentQueryByMonth <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.920 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMarketDataMapper.PRDataQueryByMonth ==> Preparing: SELECT CONCAT(CAST(YEAR(STR_TO_DATE(license_time,'%Y-%m')) AS CHAR),'-', CAST(MONTH(STR_TO_DATE(license_time,'%Y-%m')) AS CHAR)) AS market_date, SUM(license_fee) AS license_fee FROM permission_record WHERE PATENT_NO IN ( ? , ? ) GROUP BY market_date [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.921 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMarketDataMapper.PRDataQueryByMonth ==> Parameters: CN111243486A(String), CN111258141A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:52.938 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMarketDataMapper.PRDataQueryByMonth <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:53.026 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductCategoryMapper.getAreaList ==> Preparing: SELECT DISTINCT sale_area FROM product_market_data WHERE product_id IN( SELECT product_id FROM asso_structure_patent WHERE patent_no IN ( ? , ? ) UNION SELECT product_id FROM asso_product_patent WHERE patent_no IN ( ? , ? ) ) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:53.026 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductCategoryMapper.getAreaList ==> Parameters: CN111243486A(String), CN111258141A(String), CN111243486A(String), CN111258141A(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:53.045 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductCategoryMapper.getAreaList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.452 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.452 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.453 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic WHERE (id IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.453 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.471 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.471 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.475 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.476 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.494 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.495 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.495 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.511 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.556 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.557 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:58:58.574 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.371 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.371 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.389 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.389 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.406 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.406 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.406 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.411 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.411 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.423 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.423 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.423 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.432 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.441 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.441 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.458 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.458 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.458 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.459 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.475 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.475 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.475 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.492 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.493 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.493 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.510 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.510 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.510 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.527 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.527 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.527 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.544 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.544 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.561 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.561 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.562 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.562 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.579 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.579 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.579 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.596 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:40.596 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.264 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.264 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.264 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.264 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.284 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.285 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.364 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.364 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.378 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.378 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.381 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.385 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.385 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.395 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.396 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.397 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.402 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:42.414 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.795 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.795 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.813 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.813 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.830 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.831 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.832 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.838 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.839 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.849 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.850 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.850 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.860 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.868 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.868 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.885 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.885 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.886 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.886 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.902 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.903 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.903 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.920 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.920 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.920 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.937 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.937 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.937 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.954 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.954 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.954 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.972 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.972 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.989 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.989 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.989 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:48.989 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.006 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.006 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.006 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.024 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.024 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.723 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.723 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.724 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.724 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.742 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.743 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.815 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.815 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.828 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.828 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.833 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.834 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.835 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.845 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.847 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.847 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.852 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 15:59:49.864 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.019 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.020 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.040 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.155 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.155 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.155 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.156 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.172 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.173 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.173 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.174 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.184 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.184 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 222(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.190 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.203 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.505 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.506 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.507 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.507 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.523 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.524 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.531 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.531 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.549 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.550 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.550 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 222(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.571 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.572 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.572 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.590 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.590 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.591 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer), 75490(Integer), 75491(Integer), 6659(Integer), 47246(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.608 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.609 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.609 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.770 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.771 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.771 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48577(Integer), 48576(Integer), 48578(Integer), 48579(Integer), 48580(Integer), 48581(Integer), 48582(Integer), 48583(Integer), 48580(Integer), 48579(Integer), 48584(Integer), 48585(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.789 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.790 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.790 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.807 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.808 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.808 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.826 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 64 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.826 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.827 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.846 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.846 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.848 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.848 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.849 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer), 124(Integer), 117(Integer), 118(Integer), 144(Integer), 145(Integer), 146(Integer), 147(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.863 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 43 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.865 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.866 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.866 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer), 598(Integer), 599(Integer), 600(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.883 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.883 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.884 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer), 33386(Integer), 33389(Integer), 33392(Integer), 33395(Integer), 33398(Integer), 33401(Integer), 33404(Integer), 33407(Integer), 33410(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.901 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 22 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.902 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.902 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer), 33387(Integer), 33390(Integer), 33393(Integer), 33396(Integer), 33399(Integer), 33402(Integer), 33405(Integer), 33408(Integer), 33411(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.919 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.920 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.920 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer), 33388(Integer), 33391(Integer), 33394(Integer), 33397(Integer), 33400(Integer), 33403(Integer), 33406(Integer), 33409(Integer), 33412(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.937 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.939 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.939 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.956 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.957 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.957 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.975 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.975 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (id IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.975 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.992 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.992 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Preparing: SELECT id,name AS text,cid AS fieldId FROM os_patent_field_text WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:46.993 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.010 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.011 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.011 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.028 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.029 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid IN (?,?)) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.029 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:47.046 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:49.847 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:49.848 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:49.868 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.019 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Preparing: SELECT id,name,pid AS parentId,tid AS projectId,`order`,remark FROM os_portfolio WHERE (tid = ?) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.019 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.037 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.038 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS folderId,pid AS patentId,look,zid AS projectId FROM os_portfolio_link WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.038 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.056 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectFolderPatentLinkMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.158 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.158 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.176 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.341 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Preparing: SELECT id,name,project_id,user_id,enable,`default` AS _default,config FROM os_patent_keywords_highlight WHERE (project_id = ? AND user_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.341 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList ==> Parameters: 222(Integer), 103(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.359 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.PatentKeywordsHighlightMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.367 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.367 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.384 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.510 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (project_id = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.510 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.527 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.689 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Preparing: SELECT COUNT(*) FROM (SELECT a.id, a.`name` AS name, a.nameout AS name_out, a.patentno AS patent_no, a.abstract_path, a.abstract AS abstract_str, a.abstractout AS abstract_out, a.publicno AS public_no, a.publicdate AS public_date, a.simple_family, a.inpadoc_family, a.applicationno AS application_no, a.appdate AS application_date, a.`status` AS simple_status, a.type, a.publictodate AS public_accredit_date, a.fpublicdate AS first_public_date, a.prioritydate AS priority_date, b.look AS `read`, a.agencyid AS agency_id, a.num2 AS right_num, a.quoteno AS quote_num, a.quotedno AS quoted_num, a.patsnap_family AS patSnapFamily, a.patsnapfamilynum AS patSnapFamilyNum FROM os_patent a LEFT JOIN os_thematic_pid b ON b.pid = a.id WHERE b.zid = ? GROUP BY a.id ORDER BY a.id ASC) TOTAL [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.689 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.698 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Preparing: SELECT id,zid AS projectId,pid AS patentId,look FROM os_thematic_pid WHERE (zid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.698 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList ==> Parameters: 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.707 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList_mpCount <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.707 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Preparing: select a.id, a.`name` as name, a.nameout as name_out, a.patentno as patent_no, a.abstract_path, a.abstract as abstract_str, a.abstractout as abstract_out, a.publicno as public_no, a.publicdate as public_date, a.simple_family, a.inpadoc_family, a.applicationno as application_no, a.appdate as application_date, a.`status` as simple_status, a.type, a.publictodate as public_accredit_date, a.fpublicdate as first_public_date, a.prioritydate as priority_date, b.look as `read`, a.agencyid as agency_id, a.num2 as right_num, a.quoteno as quote_num, a.quotedno as quoted_num, a.patsnap_family as patSnapFamily, a.patsnapfamilynum as patSnapFamilyNum from os_patent a left join os_thematic_pid b on b.pid = a.id WHERE b.zid = ? group by a.id order by a.id asc LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.708 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList ==> Parameters: 222(Integer), 10(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.715 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectPatentLinkMapper.selectList <== Total: 43 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.726 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentMapper.getPageList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.727 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Preparing: SELECT id,applicantid,type,pid AS patentId,`order` FROM os_applicant_attr WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.727 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.744 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantLinkMapper.selectList <== Total: 24 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.745 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Preparing: SELECT id,name,bname AS shortName,remark,uid AS createBy,update_time,type,country,address AS addressStr,province_id,city_id,area_id,`merge`,project_id FROM os_patent_applicant WHERE (id IN (?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.746 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList ==> Parameters: 6650(Integer), 75490(Integer), 75491(Integer), 6659(Integer), 47246(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.764 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentApplicantMapper.selectList <== Total: 5 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.765 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,fid AS inventorId,first FROM os_patent_inventor_relation WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.765 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.918 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorLinkMapper.selectList <== Total: 17 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.919 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Preparing: SELECT id,name,address,country,remark,type,project_id,`merge`,updatetime,aid AS createBy FROM os_patent_inventor WHERE (id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.919 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList ==> Parameters: 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48576(Integer), 48577(Integer), 48576(Integer), 48578(Integer), 48579(Integer), 48580(Integer), 48581(Integer), 48582(Integer), 48583(Integer), 48580(Integer), 48579(Integer), 48584(Integer), 48585(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.936 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentInventorMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.937 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Preparing: SELECT id,tagname AS name,pid AS patentId,tid AS projectId FROM os_patent_label WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.937 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.954 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentLabelMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.955 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,main,type,code FROM os_patent_typeno WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.955 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.973 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentClassNumberLinkMapper.selectList <== Total: 64 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.973 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Preparing: SELECT id,pid AS patentId,aid AS agentId FROM os_patent_agent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.974 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.994 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentLinkMapper.selectList <== Total: 10 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.995 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agent WHERE (id IN (?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:50.995 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentMapper.selectList ==> Parameters: 123(Integer), 124(Integer), 117(Integer), 118(Integer), 144(Integer), 145(Integer), 146(Integer), 147(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.011 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgentMapper.selectList <== Total: 8 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.012 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Preparing: SELECT id,name FROM os_patent_agency WHERE (id IN (?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.012 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgencyMapper.selectList ==> Parameters: 594(Integer), 598(Integer), 599(Integer), 600(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.029 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentAgencyMapper.selectList <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.030 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.031 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33383(Integer), 33386(Integer), 33389(Integer), 33392(Integer), 33395(Integer), 33398(Integer), 33401(Integer), 33404(Integer), 33407(Integer), 33410(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.047 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 22 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.048 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.048 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33384(Integer), 33387(Integer), 33390(Integer), 33393(Integer), 33396(Integer), 33399(Integer), 33402(Integer), 33405(Integer), 33408(Integer), 33411(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.066 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.069 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Preparing: SELECT id,family_id,patent_no FROM os_patent_simplefamily_link WHERE (family_id IN (?,?,?,?,?,?,?,?,?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.070 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList ==> Parameters: 33385(Integer), 33388(Integer), 33391(Integer), 33394(Integer), 33397(Integer), 33400(Integer), 33403(Integer), 33406(Integer), 33409(Integer), 33412(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.087 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.PatentSimpleFamilyLinkMapper.selectList <== Total: 23 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.088 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.088 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: PATENT_TYPE(String), PATENT_SIMPLE_STATUS(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.105 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 20 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.106 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Preparing: SELECT id,fid AS optionId,cid AS fieldId,type,pid AS patentId,tid AS projectId,uid AS createBy FROM os_patent_field_patent_link WHERE (pid IN (?,?,?,?,?,?,?,?,?,?) AND tid = ?) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.106 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList ==> Parameters: 18785(Integer), 18786(Integer), 18787(Integer), 18788(Integer), 18789(Integer), 18790(Integer), 18791(Integer), 18792(Integer), 18793(Integer), 18794(Integer), 222(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.123 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldPatentLinkMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.124 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Preparing: SELECT id,name,ptype,type,status,remark,cid AS createBy,createtime,project_id FROM os_patent_field WHERE (id IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.124 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.141 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldMapper.selectList <== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.142 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Preparing: SELECT id,name AS text,cid AS fieldId FROM os_patent_field_text WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.142 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.159 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTextMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.160 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId FROM os_patent_field_multiple WHERE (cid IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.160 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.177 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldOptionMapper.selectList <== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.177 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Preparing: SELECT id,name,cid AS fieldId,sid AS parentId,zid AS treeId,level,`order`,path FROM os_patent_field_tree WHERE (cid IN (?,?)) ORDER BY `order` ASC [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.178 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList ==> Parameters: 4685(Integer), 4690(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:00:51.195 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectFieldTreeMapper.selectList <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.197 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.197 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.204 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber ==> Preparing: select label, value as applicationScenarioValue, ? as tenantId from os_system_dict where type = "ENTERPRISE_APPLICATION_SCENARIO" [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.204 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.215 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.215 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.221 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.221 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 1(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.233 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.233 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.233 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.238 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.238 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.238 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 1(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.250 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.250 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.250 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.256 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.256 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.256 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 2(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.267 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.267 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.273 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.273 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.274 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 2(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.283 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.284 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.284 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.284 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.291 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.291 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.291 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 3(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.301 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.301 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.301 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.308 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.308 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.308 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 3(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.318 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.319 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.320 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.326 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.326 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.326 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 4(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.337 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.337 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.337 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.343 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.343 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.343 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 4(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.354 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.354 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.354 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.361 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.361 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.361 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 5(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.372 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.372 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.378 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.378 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.378 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 5(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.388 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.388 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.389 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.389 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.395 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.395 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.396 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 6(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.406 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.406 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.406 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.413 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.414 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.414 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 6(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.423 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.424 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.431 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.431 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.431 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 7(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.448 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.448 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.448 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 7(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.465 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.466 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.466 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 8(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.483 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.483 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.484 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 8(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.501 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.501 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.501 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 9(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.518 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.519 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.519 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 9(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.536 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:03.536 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.111 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.111 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.120 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT ==> Preparing: SELECT count(0) FROM event WHERE id IN (SELECT id FROM event WHERE find_in_set(?, application_scenario) UNION SELECT even.id FROM os_thematic proj JOIN asso_event_project asso ON proj.id = asso.project_id JOIN event even ON asso.event_id = even.id WHERE find_in_set(?, proj.scenarioid) AND even.application_scenario IS NULL) AND tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.121 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT ==> Parameters: 1(Integer), 1(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.131 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.138 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.138 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents ==> Preparing: select id, question_name, description, application_scenario, event_date, tenant_id, create_person_id, create_person_name, create_time, modified_time from event WHERE id in(select id from event where find_in_set(?, application_scenario) union select even.id from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null ) and tenant_id = ? order by create_time LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.138 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents ==> Parameters: 1(Integer), 1(Integer), 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.156 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.201 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.201 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.219 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.221 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.221 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:04:05.238 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 37 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.258 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.258 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.276 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.276 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.293 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.293 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.293 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.303 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.304 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.310 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.310 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.310 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.324 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.327 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.327 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.344 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.344 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.344 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.344 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.361 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.361 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.362 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.379 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.379 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.379 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.396 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.396 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.397 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.413 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.413 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.413 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.430 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.430 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.447 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.448 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.448 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.448 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.465 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.465 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.465 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.482 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:27.482 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.166 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.166 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.166 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.166 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.186 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.187 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.267 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.267 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.272 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.272 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.285 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.286 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.287 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.289 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.291 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.291 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.304 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:29.307 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.207 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.207 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber ==> Preparing: select label, value as applicationScenarioValue, ? as tenantId from os_system_dict where type = "ENTERPRISE_APPLICATION_SCENARIO" [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.208 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.208 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.225 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.225 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 1(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.225 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.226 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.241 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.242 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.242 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 1(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.242 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.242 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.242 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.259 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.259 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.259 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 2(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.259 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.260 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.260 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.277 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.277 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.277 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 2(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.277 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.277 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 3(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.295 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.312 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.312 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.312 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 3(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.312 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.312 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.312 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.328 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.329 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.329 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 4(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.329 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.330 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.330 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.347 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.348 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.348 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.349 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.349 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 4(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.350 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.367 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.367 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.367 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.367 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.367 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 5(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.367 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.383 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.384 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.384 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.384 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 5(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.384 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 6(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.401 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.418 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.418 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.418 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.418 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.418 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.418 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 6(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.436 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.436 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.436 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.436 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.436 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 7(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.453 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.454 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.454 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 7(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.471 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.471 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.471 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 8(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.488 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.488 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.488 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 8(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.505 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.506 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.506 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 9(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.523 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.523 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.523 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 9(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.541 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:31.541 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.413 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.413 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.421 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT ==> Preparing: SELECT count(0) FROM event WHERE id IN (SELECT id FROM event WHERE find_in_set(?, application_scenario) UNION SELECT even.id FROM os_thematic proj JOIN asso_event_project asso ON proj.id = asso.project_id JOIN event even ON asso.event_id = even.id WHERE find_in_set(?, proj.scenarioid) AND even.application_scenario IS NULL) AND tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.421 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT ==> Parameters: 1(Integer), 1(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.432 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.439 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.439 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents ==> Preparing: select id, question_name, description, application_scenario, event_date, tenant_id, create_person_id, create_person_name, create_time, modified_time from event WHERE id in(select id from event where find_in_set(?, application_scenario) union select even.id from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null ) and tenant_id = ? order by create_time LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.439 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents ==> Parameters: 1(Integer), 1(Integer), 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.457 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.503 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.503 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.521 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.522 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.522 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:32.540 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 37 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.790 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.790 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.808 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.808 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.825 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.825 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.825 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.843 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.844 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.844 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.862 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.863 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.880 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.880 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.880 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.880 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.897 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.898 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.898 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.916 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.916 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.916 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.933 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.933 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.933 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.950 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.951 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.951 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.969 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.969 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.986 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.986 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.987 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:50.987 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.003 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.004 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.004 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.021 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.021 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.147 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.147 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.167 DEBUG 16564 [http-nio-8877-exec-6] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.385 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.386 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.405 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.487 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.487 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.504 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.506 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.506 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.523 DEBUG 16564 [http-nio-8877-exec-5] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.695 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.695 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.715 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.782 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.783 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.800 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.801 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.802 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:51.819 DEBUG 16564 [http-nio-8877-exec-9] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.637 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.638 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.638 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber ==> Preparing: select label, value as applicationScenarioValue, ? as tenantId from os_system_dict where type = "ENTERPRISE_APPLICATION_SCENARIO" [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.638 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.656 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.656 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.656 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 1(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.656 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.672 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.673 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.673 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.673 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.673 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.673 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 1(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.690 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.690 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.691 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.691 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.691 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 2(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.691 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.707 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.707 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.708 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.708 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 2(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.708 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 3(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.725 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.742 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.742 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.743 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.743 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.743 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 3(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.743 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.760 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.760 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.760 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.760 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.760 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 4(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.760 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.777 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.777 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.777 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.777 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.777 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 4(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.777 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.794 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.794 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.795 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.795 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.795 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.795 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 5(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.812 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.812 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.812 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.812 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 5(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.812 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.829 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.829 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.829 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.829 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.829 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.830 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.830 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 6(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.847 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.847 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.847 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.847 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.847 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 6(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.847 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.865 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.865 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.865 DEBUG 16564 [http-nio-8877-exec-1] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.865 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.865 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 7(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.882 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.882 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.882 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 7(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.899 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.899 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.900 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 8(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.916 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.916 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.916 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 8(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.934 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.934 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Preparing: select count(*) from event where find_in_set(?, application_scenario) and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.934 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 ====> Parameters: 9(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.951 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount1 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.951 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Preparing: select count(*) from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null and tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.951 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 ====> Parameters: 9(String), 1(Long) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.968 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.selectEventCount2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:54.968 DEBUG 16564 [http-nio-8877-exec-2] cn.cslg.pas.mapper.EventMapper.queryApplicationScenarioEventNumber <== Total: 9 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.812 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Preparing: select a.id, a.`name`, a.creat_id as create_by, a.technical_theme, a.innerfile as inner_file, a.`update`, a.`status`, a.contract_no, a.`case` as case_date, a.update_time, a.sort, a.clientid as client_id, a.scenarioid as scenario, a.typeid as type, a.remark, a.create_time,a.department_id,a.personnel_id from os_thematic a [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.813 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.getListForCount ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.819 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT ==> Preparing: SELECT count(0) FROM event WHERE id IN (SELECT id FROM event WHERE find_in_set(?, application_scenario) UNION SELECT even.id FROM os_thematic proj JOIN asso_event_project asso ON proj.id = asso.project_id JOIN event even ON asso.event_id = even.id WHERE find_in_set(?, proj.scenarioid) AND even.application_scenario IS NULL) AND tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.819 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT ==> Parameters: 1(Integer), 1(Integer), 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.832 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.ProjectMapper.getListForCount <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.837 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.838 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents ==> Preparing: select id, question_name, description, application_scenario, event_date, tenant_id, create_person_id, create_person_name, create_time, modified_time from event WHERE id in(select id from event where find_in_set(?, application_scenario) union select even.id from os_thematic proj join asso_event_project asso on proj.id = asso.project_id join event even on asso.event_id = even.id where find_in_set(?, proj.scenarioid) and even.application_scenario is null ) and tenant_id = ? order by create_time LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.838 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents ==> Parameters: 1(Integer), 1(Integer), 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.856 DEBUG 16564 [http-nio-8877-exec-7] cn.cslg.pas.mapper.EventMapper.queryEvents <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.904 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?,?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.904 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: ENTERPRISE_APPLICATION_SCENARIO(String), INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.921 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 46 [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.923 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Preparing: SELECT id,label,value,type FROM os_system_dict WHERE (type IN (?)) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.923 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList ==> Parameters: INVESTIGATION_TYPE(String) [pas:0.0.0.0:8877] [,] 2023-04-20 16:05:55.940 DEBUG 16564 [http-nio-8877-exec-3] cn.cslg.pas.mapper.SystemDictMapper.selectList <== Total: 37 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.723 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Preparing: SELECT id,name,creat_id AS createBy,technical_theme,innerfile,`update`,status,contract_no,`case` AS caseDate,update_time,sort,clientid,scenarioid AS scenario,typeid AS type,remark,department_id,personnel_id,tenantId,create_time,product_id,structure_id,is_category FROM os_thematic [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.723 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList ==> Parameters: [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.744 DEBUG 16564 [http-nio-8877-exec-4] cn.cslg.pas.mapper.ProjectMapper.selectList <== Total: 124 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.847 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Preparing: SELECT count(0) FROM product p JOIN product_category pc ON p.product_category_id = pc.id WHERE create_person_tenant_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.847 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query_COUNT ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.864 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query_COUNT <== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.864 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query ==> Preparing: select p.id p_id, product_name, market_time, company_name, p.tenant_id, create_person_tenant_id, product_explain, product_category_id, p.license_rate, p.create_person_name, product_category_name from product p join product_category pc on p.product_category_id = pc.id WHERE create_person_tenant_id = ? order by p_id LIMIT ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.865 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query ==> Parameters: 1(Integer), 10(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.882 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.882 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.899 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.900 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.900 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 41(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.917 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 2 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.917 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.917 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.935 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.935 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.952 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.952 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.952 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.953 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.969 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.970 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.970 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 42(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.987 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.987 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:09.987 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.004 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.004 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.004 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 47(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.022 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.022 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category where id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.022 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.039 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.039 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 ======> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.057 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query41 <====== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.057 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query4 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.057 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Preparing: select id, product_id, name, suffix, url from asso_product_picture where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.057 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.074 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query2 <==== Total: 0 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.074 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Preparing: select patent_no from asso_product_patent where product_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.074 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 ====> Parameters: 48(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.092 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query3 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.092 DEBUG 16564 [http-nio-8877-exec-10] cn.cslg.pas.mapper.ProductMapper.query <== Total: 4 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.154 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Preparing: select id pc_id, product_category_name, remark, license_rate, create_person_name from product_category WHERE tenant_id = ? order by pc_id [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.154 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query ==> Parameters: 1(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.171 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.171 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 22(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.189 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.189 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.189 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 25(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.206 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.206 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Preparing: select id, product_category_id, name, suffix, url from asso_product_category_picture where product_category_id = ? [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.206 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 ====> Parameters: 26(Integer) [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.223 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query2 <==== Total: 1 [pas:0.0.0.0:8877] [,] 2023-04-20 16:07:10.223 DEBUG 16564 [http-nio-8877-exec-8] cn.cslg.pas.mapper.ProductCategoryMapper.query <== Total: 3